This section describes details of the Diameter Base Protocol implementation that you should take into account when working with the Diameter agents.
Limitations
While provides While provides the capability of a Diameter Server and a Diameter Client, it does not provide all the capabilities of a Diameter Agent as defined in the Diameter Base Protocol RFC 6733, chapter 1.2 Terminology.
...
Info | ||||
---|---|---|---|---|
| ||||
On a specific EC/ECSA:
On cell level:
|
Failed-AVP
The AVP Failed-AVP is populated for the following values in the Result-Code AVP:
DIAMETER_INVALID_AVP_VALUE 5004
DIAMETER_MISSING_AVP 5005
DIAMETER_AVP_OCCURS_TOO_MANY_TIMES 5009
DIAMETER_UNABLE_TO_COMPLY 5012
DIAMETER_INVALID_AVP_LENGTH 5014
NAPTR Service Field Format
The Diameter Stack agent uses NAPTR records in DNS for dynamic peer discovery. It is case insensitive to the service-parms
in the NAPTR service fields that are configured in the DNS server. For more information about NAPTR, see RFC 6408.
TWCLOSE Property
The optional Execution Context property TWCLOSE
should be used when connecting to peers that do not send Diameter Watchdog Requests in the REOPEN state. This property enables a timeout timer that is reset for each received message. The specified time value should exceed Watchdog (ms) in the Advanced tab of the Diameter application profile.
Info | ||||
---|---|---|---|---|
| ||||
On a specific EC/ECSA:
On cell level:
|
Scroll ignore | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
Scroll pagebreak |
---|