Diameter Result-Code AVP
o 1xxx (Informational)
o 2xxx (Success)
o 3xxx (Protocol Errors)
o 4xxx (Transient Failures)
o 5xxx (Permanent Failure)
Informational
Errors that fall within this category are used to inform the requester that a request could not be satisfied, and additional action is required on its part before access is granted.
– DIAMETER MULTI ROUND AUTH 1001
This informational error is returned by a Diameter server to inform the access device that the authentication mechanism being used requires multiple round trips, and a subsequent request needs to be issued in order for access to be granted.
Success
Errors that fall within the Success category are used to inform a peer that a request has been successfully completed.
– DIAMETER SUCCESS 2001
The request was successfully completed.
– DIAMETER LIMITED SUCCESS 2002
When returned, the request was successfully completed, but additional processing is required by the application in order to provide service to the user.
Protocol Errors
Errors that fall within the Protocol Error category SHOULD be treated on a per-hop basis, and Diameter proxies MAY attempt to correct the error, if it is possible. Note that these errors MUST only be used in answer messages whose ‘E’ bit is set.
– DIAMETER COMMAND UNSUPPORTED 3001
This error code is used when a Diameter entity receives a message with a Command Code that it does not support.
– DIAMETER UNABLE TO DELIVER 3002
This error is given when Diameter cannot deliver the message to the destination, either because no host within the realm supporting the required application was available to process the request or because the Destination-Host AVP was given without the associated Destination-Realm AVP.
– DIAMETER REALM NOT SERVED 3003
The intended realm of the request is not recognized.
– DIAMETER TOO BUSY 3004
When returned, a Diameter node SHOULD attempt to send the message to an alternate peer. This error MUST only be used when a specific server is requested, and it cannot provide the requested service.
– DIAMETER LOOP DETECTED 3005
An agent detected a loop while trying to get the message to the intended recipient. The message MAY be sent to an alternate peer, if one is available, but the peer reporting the error has identified a configuration problem.
– DIAMETER REDIRECT INDICATION 3006
A redirect agent has determined that the request could not be satisfied locally, and the initiator of the request SHOULD direct the request directly to the server, whose contact information has been added to the response. When set, the Redirect-Host AVP MUST be present.
– DIAMETER APPLICATION UNSUPPORTED 3007
A request was sent for an application that is not supported.
– DIAMETER INVALID HDR BITS 3008
A request was received whose bits in the Diameter header were set either to an invalid combination or to a value that is inconsistent with the Command Code’s definition.
– DIAMETER INVALID AVP BITS 3009
A request was received that included an AVP whose flag bits are set to an unrecognized value or that is inconsistent with the AVP’s definition.
– DIAMETER UNKNOWN PEER 3010
A CER was received from an unknown peer.
Transient Failures
Errors that fall within the transient failures category are used to inform a peer that the request could not be satisfied at the time it was received but MAY be able to satisfy the request in the future. Note that these errors MUST be used in answer messages whose ‘E’ bit is not set.
– DIAMETER AUTHENTICATION REJECTED 4001
The authentication process for the user failed, most likely due to an invalid password used by the user. Further attempts MUST only be tried after prompting the user for a new password.
– DIAMETER OUT OF SPACE 4002
A Diameter node received the accounting request but was unable to commit it to stable storage due to a temporary lack of space.
– ELECTION LOST 4003
The peer has determined that it has lost the election process and has therefore disconnected the transport connection.
Permanent Failures
Errors that fall within the permanent failures category are used to inform the peer that the request failed and should not be attempted again. Note that these errors SHOULD be used in answer messages whose ‘E’ bit is not set. In error conditions where it is not possible or efficient to compose application-specific answer grammar, answer messages with the ‘E’ bit set and which comply to the grammar described in Section 7.2 (rfc6733) MAY also be used for permanent errors.
– DIAMETER AVP UNSUPPORTED 5001
The peer received a message that contained an AVP that is not recognized or supported and was marked with the ‘M’ (Mandatory) bit. A Diameter message with this error MUST contain one or more Failed-AVP AVPs containing the AVPs that caused the failure.
– DIAMETER UNKNOWN SESSION ID 5002
The request contained an unknown Session-Id.
– DIAMETER AUTHORIZATION REJECTED 5003
A request was received for which the user could not be authorized. This error could occur if the service requested is not permitted to the user.
– DIAMETER INVALID AVP VALUE 5004
The request contained an AVP with an invalid value in its data portion. A Diameter message indicating this error MUST include the offending AVPs within a Failed-AVP AVP.
– DIAMETER MISSING AVP 5005
The request did not contain an AVP that is required by the Command Code definition. If this value is sent in the Result-Code AVP, a Failed-AVP AVP SHOULD be included in the message. The Failed-AVP AVP MUST contain an example of the missing AVP complete with the Vendor-Id if applicable. The value field of the missing AVP should be of correct minimum length and contain zeroes.
– DIAMETER RESOURCES EXCEEDED 5006
A request was received that cannot be authorized because the user has already expended allowed resources. An example of this error condition is when a user that is restricted to one dial-up PPP port attempts to establish a second PPP connection.
– DIAMETER CONTRADICTING AVPS 5007
The Home Diameter server has detected AVPs in the request that contradicted each other, and it is not willing to provide service to the user. The Failed-AVP AVP MUST be present, which contain the AVPs that contradicted each other.
– DIAMETER AVP NOT ALLOWED 5008
A message was received with an AVP that MUST NOT be present. The Failed-AVP AVP MUST be included and contain a copy of the offending AVP.
– DIAMETER AVP OCCURS TOO MANY TIMES 5009
A message was received that included an AVP that appeared more often than permitted in the message definition. The Failed-AVP AVP MUST be included and contain a copy of the first instance of the offending AVP that exceeded the maximum number of occurrences.
– DIAMETER NO COMMON APPLICATION 5010
This error is returned by a Diameter node that receives a CER whereby no applications are common between the CER sending peer and the CER receiving peer.
– DIAMETER UNSUPPORTED VERSION 5011
This error is returned when a request was received, whose version number is unsupported.
– DIAMETER UNABLE TO COMPLY 5012
This error is returned when a request is rejected for unspecified reasons.
– DIAMETER INVALID BIT IN HEADER 5013
This error is returned when a reserved bit in the Diameter header is set to one (1) or the bits in the Diameter header are set incorrectly.
– DIAMETER INVALID AVP LENGTH 5014
The request contained an AVP with an invalid length. A Diameter message indicating this error MUST include the offending AVPs within a Failed-AVP AVP. In cases where the erroneous AVP length value exceeds the message length or is less than the minimum AVP header length, it is sufficient to include the offending AVP header and a zero filled payload of the minimum required length for the payloads data type. If the AVP is a Grouped AVP, the Grouped AVP header with an empty payload would be sufficient to indicate the offending AVP. In the case where the offending AVP header cannot be fully decoded when the AVP length is less than the minimum AVP header length, it is sufficient to include an offending AVP header that is formulated by padding the incomplete AVP header with zero up to the minimum AVP header length.
– DIAMETER INVALID MESSAGE LENGTH 5015
This error is returned when a request is received with an invalid message length.
– DIAMETER INVALID AVP BIT COMBO 5016
The request contained an AVP with which is not allowed to have the given value in the AVP Flags field. A Diameter message indicating this error MUST include the offending AVPs within a Failed-AVP AVP.
– DIAMETER NO COMMON SECURITY 5017
This error is returned when a CER message is received, and there are no common security mechanisms supported between the peers. A Capabilities-Exchange-Answer (CEA) message MUST be returned with the Result-Code AVP set to DIAMETER NO COMMON SECURITY.
Reference:
tools.ietf.org/html/rfc6733