For each Policy and Charging Site, the Diameter Error Result Code value to send to the Request initiator for policy related errors can be configured according to which condition applies. Each condition can be mapped to a different Result Code for each supported interface. Result Codes can be Diameter IANA defined or experimental.
When PCRF Pooling is enabled, new binding cannot be created unless the binding-capable session initiation request contains a configured APN. If the binding-capable session initiation request arrives with either no APN, or an APN that is not configured in the Access Point Names table, the request is answered by Policy DRA using a configurable error response code. To configure the Diameter response code for this scenario, a new Missing Or Unconfigured APN error condition has been added to the existing SOAM error. This error response applies to all binding capable interfaces (for example, Gx, Gxx, and S9) and can be configured with either an IANA Diameter result code, or an experimental result code and vendor-id.
Three-digit error codes in Diameter Error-Message AVPs indicate exactly why a slave session could not be routed. This provides more robust troubleshooting using Diameter capture tools.
A 3-digit error code is an identifier to uniquely identify a specific error scenario (not error category) encountered in a Diameter Answer message generated by PCA. 3-digit codes are unique across all DSR layers (DSR connection layer, routing layer and application layer) and all DSR applications (PCA, RBAR, FABR, and IDIH, etc.) for errors they represent. The ranges of 500-549 and 850-899 are for the PCA application, while the DSR connection layer, routing layer and other DSR applications uses other non-overlapping ranges. Multiple errors may belong to a same error category and are associated with a same Result-Code. It is the 3-digit code that can distinguish an error from others. Users should search for the 3-digit code when identifying an error if possible and available.
| Error Category | Functionality | Applied Diameter Interface/ Message | Default Result-Code | Error- Message Suffix | Error Text |
|---|---|---|---|---|---|
| Missing or Unconfigured APN | PDRA | Policy-related binding capable session initiation request messages | 3002 | 500 | Missing or Unconfigured APN. Binding capable session initiation request is received with no APN |
| Missing or Unconfigured APN | PDRA | Policy-related binding capable session initiation request messages | 3002 | 501 | Missing or Unconfigured APN. Binding capable session initiation request is received with APN, but the APN is not configured in the APN configuration. |
| Unable To Route | PDRA | Policy-related binding capable and dependent session initiation request messages | 3002 | 502 | Unable To Route. Request message is received and a binding with a PCRF was found. P-DRA can't route the request to PCRF due to DSR queue full error. |
| Unable To Route | PDRA | Policy-related binding capable and dependent session initiation request messages | 3002 | 3-digit error code from DRL | Unable To Route. Request message is received and a binding with a PCRF was found. P-DRA can't route the request to PCRF due to PCRF being unreachable. DRL Text string. |
| No Usable Keys In Binding Dependent Message | PDRA | Policy-related binding dependent session initiation request messages | 3002 | 503 | No Usable Keys In Binding Dependent Message. No binding key in Binding Key Priority GUI can be matched, or no key is included in the binding dependent message. |
| Binding Not Found | PDRA | Policy-related binding dependent session initiation request messages | 3002 | 505 | Binding Not Found. Binding record is not found after examining all configured binding keys in Diameter message. |
| SBR Error | PDRA | Policy-related binding capable and dependent session initiation, update or terminate answer messages, | 3002 | 507 | SBR Error. ComAgent timeout. |
| SBR Error | PDRA | Policy-related binding capable and dependent session initiation, update or terminate answer messages | 3002 | 508 | SBR Error. SBR database error prevents SBR from reading, writing or deleting a record, |
| Session Not Found | PDRA | Policy-related binding capable and dependent session update or terminate request messages | 3002 | 509 | Session Not Found. Session record doesn't exist for given session ID |
| PCA Unavailable Or Degraded | PDRA/ OCDRA | Any Diameter Requests forwarded to PCA | 3002 | 305 | PCA Unavailable or Degraded |
| SBR Error | PDRA | Policy-related binding capable session initiation request messages | 3002 | 520 | SBR Error. Binding capable session initiation request received, but no PCRFs are configured at the site, or PCRF ID is not found in PCRF table. |
| SBR Error | PDRA | Policy-related binding capable session initiation request messages | 3002 | 521 | SBR Error. Maximum number of sessions per binding is exceededthat fails the binding creation for given subscriber's key. |
| Session ID is missing from Request | PDRA | Any Policy-related Diameter Requests forwarded to P-DRA | 5005 | 522 | Session ID is missing from Request |
| CC-Request-Type AVP is missing from CCR message | PDRA | Policy-related binding capable session initiation, update or terminate request messages | 5005 | 523 | CC-Request-Type AVP is missing from CCR message |
| Not In Use | |||||
| Invalid AVP value in request message | PDRA | Any Policy-related Diameter Requests forwarded to P-DRA | 5004 | 525 | Invalid AVP value in request message |
| Destination-Host AVP is missing in in-session request | PDRA | Policy-related binding capable update and terminate request and dependent session initiation update or terminate request messages | 5012 | 506 | Destination-Host AVP is missing in in-session request |
| Unable To Route | PDRA | Policy-related binding capable session initiation request | 3002 | 510 | Unable To Route. A slave session could not be routed because on polling the slave sessionRef was no longer in the binding database. |
| Unable To Route | PDRA | Policy-related binding capable session initiation request | 3002 | 511 | Unable To Route. A slave session could not be routed because on polling the master sessionRef was no longer in the binding database. |
| Unable To Route | PDRA | Policy-related binding capable session initiation request | 3002 | 512 | Unable To Route. A slave session could not be routed because on polling the master sessionRef was early too long. |
| SBR Error | PDRA | Policy-related Requests and Answers | 3002 | 504 | SBR Error. ComAgent unavailable when sending stack event to SBR |
| Unsupported Application ID | PDRA/ OCDRA | Diameter Requests | 3007 | 530 | Application ID unsupported by PCA |
| Command Code and App ID no match | PDRA | Policy-related Requests and Answers | 5019 | 531 | Command Code does not match App ID or not exist |
| Unable To Route | PDRA | Policy-related binding capable session initiation request | 3002 | 513 | Unable To Route. A slave session could not routed because on polling the master session and internal error occurred. |
| PCA Functionality Unavailable or Disabled | PDRA | Policy related binding capable and dependent session update or terminate request messages | 3002 | 532 | PCA Functionality Unavailable or Disabled. Policy DRA Function Disabled. |
| PCA Functionality Unavailable or Disabled | PDRA | Policy related binding capable and dependent session update or terminate request messages | 3002 | 533 | PCA Functionality Unavailable or Disabled. Policy DRA Function Unavailable. |
| PCA Functionality Unavailable or Disabled | OCDRA | Online Charging related binding independent session request messages | 3002 | 534 | PCA Functionality Unavailable or Disabled. Online Charging DRA Function Disabled. |
| PCA Functionality Unavailable or Disabled | OCDRA | Online Charging related binding independent session request messages | 3002 | 535 | PCA Functionality Unavailable or Disabled. Online Charging DRA Function Unavailable |
| Session ID is missing from Request | OCDRA | Any Online Charging -related Diameter Requests forwarded to OC-DRA | 5005 | 536 | Session ID is missing from Request |
| CC-Request-Type AVP is missing from CCR message | OCDRA | Any Online Charging-related Diameter Requests forwarded to OC-DRA | 5005 | 537 | CC-Request-Type AVP is missing from CCR message |
| Invalid AVP value in request message | OCDRA | Any Online Charging-related Diameter Requests forwarded to OC-DRA | 5004 | 538 | Invalid AVP value in request message |
| Not In Use | |||||
| Unable To Route | OCDRA | Online Charging-related binding independent session request messages | 3002 | 540 | Unable To Route. Request message is received, OC-DRA can't route the request to OCS due to DSR queue full error. |
| Unable To Route | OCDRA | Online Charging-related binding independent session initiation request messages | 3002 | 539 | Unable To Route. Request message can not be routed to peernode. DIAM-ERR-XXXX-XXX:DRL Text string. |
| SBR Error | OCDRA | Online Charging-related binding independent session update or terminate answer messages, if session state or topology hiding applies | 5012 | 541 | SBR Error. ComAgent timeout. |
| SBR Error | OCDRA | Online Charging-related binding independent session update or terminate answer messages, if session state or topology hiding applies | 5012 | 542 | SBR Error. SBR database error prevents SBR from reading, writing or deleting a record, |
| SBR Error | OCDRA | Online Charging-related binding independent session update or terminate answer messages, if session state or topology hiding applies | 5012 | 543 | SBR Error . ComAgent unavailable when sending stack event to SBR, |
| Session Not Found | OCDRA | Online Charging-related session update or terminate request messages, if session state or topology hiding applies | 5002 | 544 | Session Not Found. Session record doesn't exist for given session ID |
| Command Code and App ID no match | OCDRA | Online Charging -related Requests. | 3001 | 545 | Command Code does not match App ID or not exist |
The Policy and Charging > Configuration > Error Codes [Edit] page opens. You can edit the selected Error Code. See Editing Error Codes.
The fields are described in Error Codes elements.