Diameter Protocol Result Codes

Diameter

1. Types of Diameter Result Codes:
.

Diameter Result Code
Result Code Series	Type
1xxx	Informational
2xxx	Success
3xxx	Protocol errors
4xxx	Transient failures
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.
.
Success :              Errors that fall within the Success category are used to inform a
                              peer that a request has been successfully completed.
.
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 and only these errors MUST
                             only be used in answer messages whose 'E' bit is set.
.
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..
Permanent failure : Errors that fall within the permanent failures category are used
                                     to inform the peer that the request failed, and should not be
                                     attempted again.
.
.
.

2. Diameter Result Code in detail:
.
.

Type	Code	Reason	Details
Informational	1001	DIAMETER_MULTI_ROUND_AUTH	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	2001	DIAMETER_SUCCESS	The Request was successfully completed.
Success	2002	DIAMETER_LIMITED_SUCCESS	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	3001	DIAMETER_COMMAND_UNSUPPORTED	The Request contained a Command-Code that the receiver did not recognize or support.  This MUST be used when a Diameter node receives an experimental command that it does not understand.
Protocol Errors	3002	DIAMETER_UNABLE_TO_DELIVER	This error is given when Diameter can not 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 Destination-Host AVP was given without the associated Destination-Realm AVP.
Protocol Errors	3003	DIAMETER_REALM_NOT_SERVED	The intended realm of the request is not recognized.
Protocol Errors	3004	DIAMETER_TOO_BUSY	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.
Protocol Errors	3005	DIAMETER_LOOP_DETECTED	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.
Protocol Errors	3006	DIAMETER_REDIRECT_INDICATION	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.
Protocol Errors	3007	DIAMETER_APPLICATION_UNSUPPORTED	A request was sent for an application that is not supported.
Protocol Errors	3008	DIAMETER_INVALID_HDR_BITS	A request was received whose bits in the Diameter header were either set to an invalid combination, or to a value that is inconsistent with the command code's definition.
Protocol Errors	3009	DIAMETER_INVALID_AVP_BITS	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.
Protocol Errors	3010	DIAMETER_UNKNOWN_PEER	A CER was received from an unknown peer.
Transient Failures	4001	DIAMETER_AUTHENTICATION_REJECTED	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.
Transient Failures	4002	DIAMETER_OUT_OF_SPACE	A Diameter node received the accounting request but was unable to commit it to stable storage due to a temporary lack of space.
Transient Failures	4003	ELECTION_LOST	The peer has determined that it has lost the election process and  has therefore disconnected the transport connection.
Permanent Failures	5001	DIAMETER_AVP_UNSUPPORTED	The peer received a message that contained an AVP that is not  recognized or supported and was marked with the Mandatory bit.  A  Diameter message with this error MUST contain one or more Failed-  AVP AVP containing the AVPs that caused the failure.
Permanent Failures	5002	DIAMETER_UNKNOWN_SESSION_ID	The request contained an unknown Session-Id.
Permanent Failures	5003	DIAMETER_AUTHORIZATION_REJECTED	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.
Permanent Failures	5004	DIAMETER_INVALID_AVP_VALUE	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.
Permanent Failures	5005	DIAMETER_MISSING_AVP	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.
Permanent Failures	5006	DIAMETER_RESOURCES_EXCEEDED	A request was received that cannot be authorized because the user has already expended allowed resources.  An example of this error condition is a user that is restricted to one dial-up PPP port,  attempts to establish a second PPP connection.
Permanent Failures	5007	DIAMETER_CONTRADICTING_AVPS	The Home Diameter server has detected AVPs in the request that contradicted each other, and is not willing to provide service to  the user.  One or more Failed-AVP AVPs MUST be present, containing the AVPs that contradicted each other.
Permanent Failures	5008	DIAMETER_AVP_NOT_ALLOWED	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.
Permanent Failures	5009	DIAMETER_AVP_OCCURS_TOO_MANY_TIMES	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
Permanent Failures	5010	DIAMETER_NO_COMMON_APPLICATION	This error is returned when a CER message is received, and there are no common applications supported between the peers.
Permanent Failures	5011	DIAMETER_UNSUPPORTED_VERSION	This error is returned when a request was received, whose version number is unsupported.
Permanent Failures	5012	DIAMETER_UNABLE_TO_COMPLY	This error is returned when a request is rejected for unspecifiedreasons.
Permanent Failures	5013	DIAMETER_INVALID_BIT_IN_HEADER	This error is returned when an unrecognized bit in the Diameter  header is set to one
Permanent Failures	5014	DIAMETER_INVALID_AVP_LENGTH	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.
Permanent Failures	5015	DIAMETER_INVALID_MESSAGE_LENGTH	This error is returned when a request is received with an invalid message length.
Permanent Failures	5016	DIAMETER_INVALID_AVP_BIT_COMBO	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.
Permanent Failures	5017	DIAMETER_NO_COMMON_SECURITY	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) MUST be returned with the Result-Code AVP set to DIAMETER_NO_COMMON_SECURITY.