This appendix describes Oracle Communications Billing and Revenue Management Elastic Charging Engine (ECE) Diameter Gateway result codes. For more information, see the Result-Code AVP section in the IETF web site at:
https://tools.ietf.org/html/rfc3588#section-7.1
Diameter Gateway supports the following categories of result codes:
Success result codes are returned when the request is successfully completed.
Table D-1 lists the success result codes.
Protocol-error result codes are returned at the base protocol level. The diameter proxy agents may attempt to correct these errors.
Table D-2 lists the protocol-error result codes.
Table D-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 timeout period of Elastic Charging Server. Elastic Charging Server (the charging server nodes) may be overloaded. Verify that the charging server nodes have reached the point of saturation. Check the CPU usage on the charging server nodes. |
|
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. |
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 D-3 lists the transient-failure result codes.
Table D-3 Transient-Failure Result Codes
| Result Code | Code | Notes |
|---|---|---|
|
DIAMETER_END_USER_SERVICE_DENIED |
4010 |
The rating function failed with one of the following errors:
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. |
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 D-4 lists the permanent-failure result codes.
Table D-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 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 on 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_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 request specification. 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_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_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 Online Charging System rating function failed because it received one of the following messages:
Check the esc.log file for the rating function failure. |
|
DIAMETER_ERROR_UNKNOWN_POLICY_COUNTERS |
5570 |
The Online Charging System 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. |
|
DIAMETER_ERROR_USER_UNKNOWN |
5001 |
The policy request user is unknown to ECE. Verify that the subscriber exists in ECE. |