Diameter Gy – Abort-Session-Answer (ASA) command
Diameter Gy – ASA message format
This section describes the Diameter Gy ASA message format as defined in RFC 6733. Strikethrough formatted AVPs are not included in ASA.
<ASA> ::= < Diameter Header: 274, PXY >
< Session-Id >
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
[ User-Name ]
[ Origin-State-Id ]
[ Error-Message ]
[ Error-Reporting-Host ]
[ Failed-AVP ]
* [ Redirect-Host ]
[ Redirect-Host-Usage ]
[ Redirect-Max-Cache-Time ]
* [ Proxy-Info ]
* [ AVP ]
Diameter Gy – ASA message top level AVPs
Diameter Gy ASA: top level AVP description provides a detailed description for each top level AVP present in a Diameter Gy ASA message.
AVP code | AVP name | Description |
---|---|---|
263 |
Session-id |
A session is a logical concept at the application layer that exists between the Diameter client and the Diameter server; it is identified via the Session-Id AVP. Format: <DiameterIdentity>;<high 32 bits>;<low 32 bits>
Example: bng.nokia.com;1326398325;1 |
264 |
Origin-Host |
Diameter Identity. As configured in the corresponding diameter-peer-policy Example: bng.nokia.com |
268 |
Result-Code |
Values: 2002 = Diameter Limited Success 5002 = Diameter Unknown Session ID 5012 = Diameter Unable To Comply — AVP parsing errors or message errors |
296 |
Origin-Realm |
Diameter Identity. As configured in the corresponding diameter-peer-policy Example: nokia.com |
AVP code | AVP name | Standard | Data format | Flags |
---|---|---|---|---|
263 |
Session-id |
RFC 6733 |
UTF8 String |
M |
264 |
Origin-Host |
RFC 6733 |
Diameter Identity |
M |
268 |
Result-Code |
RFC 6733/RFC 4006 |
Unsigned 32 |
M |
296 |
Origin-Realm |
RFC 6733 |
Diameter Identity |
M |