top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

DIAMETER : What the AVPs are applicable for each diameter request and answer message ?

+4 votes

I have a query related to generic diameter request and answer message.
Please provide the list of all generic AVPs wrt a diameter request and answer message along with the brief description. Thanks in advance.

posted Mar 27, 2014 by Vimal Kumar Mishra

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+1 vote

Actually there can be two kind of messages if you are using Diameter protocol.

  1. Diameter has its own messages ( Like DWR-DWA, CER-CEA and DPR-DPA and so on) This is called Base protocol messages.

  2. Application Specific messages (Eg. for Gx Application CCR-I, U, T and in case of S6A interface ULR-ULA and so on). Here DIAMETER's task is to encapsulate those application messages and carry it further.

Now lets first talk about AVP's which is mandatory for all base protocol messages:

After Diameter Header the AVP's are:
1. Origin-Host
2. Origin-Realm

These two AVP's should be present with all base messages. Addition to that for the first (CER-CEA) Diameter exchange of messages Host-Ip-Address is also must.

Specifically it's difficult to explain what are the mandatory avp's are for all interfaces. So going to tell you those avp's which is mandatory to all messages. Kind of Generic.

After Diameter Header the AVP's are:
1. Session-Id
2. Auth-Application-Id
3. Origin-Host
4. Origin-Realm

In request message Destination-Realm is mandatory but not in Answer message.

answer Apr 14, 2014 by Hiteshwar Thakur
Similar Questions
+1 vote

Few Diameter messages carries
- Destination-Host
- Destination-Realm only
- both Destination-Host and Destination-Realm
- Or none of both
I want to know what to use when.

+1 vote

I am not able to understand the significance of this AVP from rfc3588. Can someone please explain in simple word ?

+3 votes

When SCTP layer itself takes care of heartbeat ack-nack then why does diameter watchdog mechanism is required at the application layer ?