Diameter Gateway Error Codes

E Diameter Gateway Error Codes

This appendix describes Oracle Communications Billing and Revenue Management Elastic Charging Engine (ECE) Diameter Gateway error codes.

Topics in this document:

For more information, see the Result-Code AVP section in the IETF website at: https://tools.ietf.org/html/rfc3588#section-7.1.

Success Result Codes

Success result codes inform the peer that a request has been successfully completed.

Table E-1 lists the success result codes.

Table E-1 Success Result Codes

Result Code	Code	Notes
DIAMETER_SUCCESS	2001	The requests was successfully completed.
DIAMETER_LIMITED_SUCCESS	2002	The request was successfully completed, but additional processing is required by the application to provide service to the user.

Protocol-Error Result Codes

Protocol-error result codes are returned at the base protocol level. The diameter proxy agents may attempt to correct these errors.

Table E-2 lists the protocol-error result codes.

Table E-2 Protocol-Error Result Codes

Result Code	Code	Notes
DIAMETER_COMMAND_UNSUPPORTED	3001	The command-code in the diameter request is not recognized or supported by the diameter node. Verify that the command-code sent by the peer conforms to Gy, Sh, or Sy protocol specifications.
DIAMETER_UNABLE_TO_DELIVER	3002	The origin and destination information in the diameter message header is incorrect. Verify that the targeted diameter peer node is run with the correct realm and Origin-Host names.
DIAMETER_REALM_NOT_SERVED	3003	The destination realm in the diameter message header is not recognized. Verify that the message realm name matches the realm configuration in Diameter Gateway.
DIAMETER_TOO_BUSY	3004	The request cannot be processed within the time-out period of Elastic Charging Server. The charging server nodes may be overloaded. Check the CPU usage on the charging server nodes.
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	The Diameter Gateway server received the diameter request with the Auth-Application-Id other than Gy, Sy, or Sh. Verify that the Auth-Application-Id in the diameter request is either Gy (4), Sy (16777302), or Sh attribute-value pair (16777217).
DIAMETER_INVALID_HDR_BITS	3008	The diameter message header contains bits of unexpected byte size, or it is corrupted. Verify the diameter message header.
DIAMETER_INVALID_AVP_BITS	3009	The diameter message contains the attribute-value pair (AVP) bits of unexpected byte size, or it is corrupted. Verify the diameter message AVP stream.
DIAMETER_UNKNOWN_PEER	3010	A CER message was received from an unknown peer.

Transient-Failure Result Codes

Transient-failure result codes are returned to indicate that the request could not be processed at the time it was received. These requests may be processed in the future.

Table E-3 lists the transient-failure result codes.

Table E-3 Transient-Failure Result Codes

Result Code	Code	Notes
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 lost the election process and has therefore disconnected the transport connection.
DIAMETER_END_USER_SERVICE_DENIED	4010	The rating function failed with one of the following errors: MISSING_SYSTEM_ALTERATION_FOR_DEBIT INCORRECT_IMPACTS_FOR_DEBIT & LIFECYCLE_VALIDATION_FAILED Check the ecs.log file for the rating function failure details.
DIAMETER_CREDIT_LIMIT_REACHED	4012	The subscriber's credit floor or ceiling limit is breached. Update the subscriber's credit.
SPLIT_BRAIN_SUSPECTED	4999	This is a Camiant-specific result code which should be returned server when a primary connection already exists and secondary connection is being attempted.

Permanent-Failure Result Codes

Permanent-failure result codes are returned to indicate that the requests will not be processed and that further requests from the diameter client will not be accepted for processing.

Table E-4 lists the permanent-failure result codes.

Table E-4 Permanent-Failure Result Codes

Result Code	Code	Notes
DIAMETER_AVP_UNSUPPORTED	5001	The Diameter Gateway server received a message with an unknown AVP. Verify that the AVP is present in the dictionary_main.xml file.
DIAMETER_UNKNOWN_SESSION_ID	5002	The Sy request contains an unknown Session-Id. Verify that the Session-Id is the same as in the initial request.
DIAMETER_AUTHORIZATION_REJECTED	5003	The Diameter Gateway authorization failed with the data in the request message AVP. Check the log files for more information about the authorization failure.
DIAMETER_INVALID_AVP_VALUE	5004	The request AVP data cannot be converted to an expected PayloadItem type. Verify that the AVP type in the request is compatible with the PayloadItem type in ECE.
DIAMETER_MISSING_AVP	5005	The Diameter Gateway server received a request without the Gy, Sy, or Sh AVP. Verify that the request contains the required AVPs as per the 3GPP specifications.
DIAMETER_RESOURCES_EXCEEDED	5006	The request cannot be authorized because the user has expended all allowed resources. For example, a user restricted to one dial-up PPP port attempted to establish a second PPP connection.
DIAMETER_CONTRADICTING_AVPS	5007	The Home Diameter server 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.
DIAMETER_AVP_NOT_ALLOWED	5008	A diameter message was received with an AVP that is not allowed as per the dictionary_main.xml file. Check for any AVP cardinality rules violations as defined in the dictionary_main.xml file.
DIAMETER_AVP_OCCURS_TOO_MANY_TIMES	5009	The AVP-to-ECE PayloadItem mapping violated the cardinality mapping rules per the event definition. Check for cardinality rule violations in the AVP-to-PayloadItem mapping.
DIAMETER_NO_COMMON_APPLICATION	5010	The Diameter Gateway server received a Capabilities-Exchange-Request (CER) message requesting applications other than Gy, Sy, or Sh. Check the Diameter Gateway server connection.
DIAMETER_UNSUPPORTED_VERSION	5011	The Diameter Gateway server received a request message with a version number that is not supported. Verify that the Diameter client version is compatible with the Diameter Gateway server version.
DIAMETER_UNABLE_TO_COMPLY	5012	An unexpected system error occurred on the Online Charging System (OCS). Check the ECE and Diameter Gateway log files for details about the error.
DIAMETER_INVALID_BIT_IN_HEADER	5013	This error is returned when an unrecognized bit in the Diameter header is set to one (1).
DIAMETER_INVALID_AVP_LENGTH	5014	The AVP in the request message contains more or fewer bytes than expected by the Diameter Gateway server. Verify that the AVP data types are configured with the correct byte size.
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	A CER message was processed without security mechanism. Verify that security is enabled in Diameter Gateway Communications Layer.
DIAMETER_USER_UNKNOWN	5030	ECE was not able to locate the subscriber ID in the diameter request. Verify that the subscriber exists in ECE.
DIAMETER_RATING_FAILED	5031	The rating function failed because it received one of the following messages: INSUFFICIENT_RATED_QUANTITY NO_QUALIFIED_CHARGE_OFFERS NO_RATED_QUANTITY ZERO_RUM_QUANTITY Check the esc.log file for the rating function failure.
DIAMETER_ERROR_UNKNOWN_POLICY_COUNTERS	5570	ECE does not recognize one or more policy counters specified in the diameter request. Verify that the ECE server is configured for tracking the policy counters requested by the diameter message.
DIAMETER_ERROR_SUBS_DATA_ABSENT	5106	ECE received a request for some profile data that is unknown. Verify that ECE is configured to return the corresponding profile data for the Diameter request.