show ims-authorization policy-control statistics
| Field | Description | ||
|---|---|---|---|
|
DPCA Session Stats |
|||
|
Total Current Sessions |
The total number of DPCA session currently running on this system. |
||
|
Total IMSA Adds |
The total number of IP multimedia subsystem applications (IMSAs) added to service. |
||
|
Total DPCA Starts |
The total number of Diameter Policy Control Applications (DPCAs) started. |
||
|
Total Fallback Sessions |
The total number of Diameter Policy Control Application (DPCA) sessions successfully fallback to PCRF after being with local-policy. |
||
|
Total Secondary Create |
The total number of secondary contexts created.
|
||
|
Total Secondary Terminate |
The total number of secondary contexts deleted.
|
||
|
Total Session Updates |
The total number of updates applied for session/s.
|
||
|
Total Terminated |
The total number of Diameter Policy Control Application sessions terminated. |
||
|
DPCA Session Failovers |
The total number of Diameter Policy Control Application sessions failed. |
||
|
DPCA Message Stats |
|||
|
Total messages Received |
Total policy control messages received for IMS authorization policy control. |
||
|
Total Messages Sent |
Total messages sent to IMS authorization policy control server. |
||
|
Total CCR |
Total Credit Control Request (CCR) messages received. |
||
|
Total CCA |
Total Credit Control Answer (CCA) messages sent in response to CCRs. |
||
|
CCR-Initial |
Total number of initial CCR messages received. |
||
|
CCA-Initial |
Total number of initial CCA messages sent in response to initial CCR messages. |
||
|
CCA-Initial Accept |
Total number of initial CCA messages accepted in response to initial CCR messages. |
||
|
CCA-Initial Reject |
Total number of initial CCA messages rejected in response to initial CCR messages. |
||
|
CCA-Initial Dropped |
Total number of CCA-I messages which are dropped due to S-GW restoration, DPCA is off or not present or if the IMSA session is in preservation mode. |
||
|
CCA-Initial Timeouts |
Total number of initial CCA messages timed out in response to initial CCR messages. |
||
|
CCR-Update |
Total number of Credit Control Request (CCR) messages received after initial CCR for update. |
||
|
CCA-Update |
Total Credit Control Answer (CCA) messages sent in response to update CCRs. |
||
|
CCA-Update Timeouts |
Total Credit Control Answer (CCA) messages sent in response to update CCRs but timed out. |
||
|
CCA-Update Errors |
Total number of errors in parsing the CCA-Update Message. |
||
|
CCA-Update Dropped |
Total number of CCA-U messages which are dropped due to S-GW restoration, DPCA is off or not present or if the IMSA session is in preservation mode. |
||
|
CCR-Final |
Total number of final CCR messages received to end application. |
||
|
CCA-Final |
Total number of final CCA messages sent in response to final CCR messages to end session/s. |
||
|
CCA-Final Timeouts |
Total number of final CCA messages sent in response to final CCR messages to end session/s but timed out. |
||
|
CCA-Final Errors |
Total number of errors in parsing the CCA-Terminate Message. |
||
|
CCA-Final Dropped |
Total number of CCA-T messages which are dropped due to S-GW restoration, DPCA is off or not present or if the IMSA session is in preservation mode. |
||
|
ASR |
Total number of Abort-Session-Requests (ASRs) received. |
||
|
ASA |
Total number of Abort-Session-Accept (ASA) messages sent in response to Abort-Session-Requests (ASRs). |
||
|
RAR |
Total number of Re-Auth-Requests (RARs) received for re-authorization. |
||
|
RAA |
Total number of Re-Auth-Requests (RARs) answered with Re-Auth-Answer (RAA) message. |
||
|
RAR-CCR collision |
Total number of Re-Auth-Request (RAR) messages received from PCRF when there is any outstanding Credit Control Request (CCR) message. |
||
|
IRAT RAR Reject |
The total number of DPCA Re-Auth-Accept messages sent in response to Re-Auth-Request (RAR) messages received from PCRF during S2b handoff. |
||
|
CCA Parse Failure |
|||
|
CCA-Initial Failure |
This is the counter incremented when failure cb is invoked for CCR-Initial due to parse error at diabase. |
||
|
CCA-Update Failure |
This is the counter incremented when failure cb is invoked for CCR-Update due to parse error at diabase. |
||
|
CCA-Final Failure |
This is the counter incremented when failure cb is invoked for CCR-Final due to parse error at diabase |
||
|
SGW Restoration |
|||
|
RAR Reject |
The total number of RAR messages that were not processed during S-GW restoration. That is, the total number of RAR messages from the PCRF, that were rejected with result-code 5012 (UNABLE_TO_COMPLY). |
||
|
RAR Accepted |
|||
|
Rule Removals |
The total number of times the P-GW accepted RAR with rule removals from the PCRF during S-GW Restoration. |
||
|
Session Release |
The total number of times the P-GW accepted RAR with Session Release Cause from the PCRF during S-GW Restoration. |
||
|
CCA-U Dropped |
The total number of times that the P-GW dropped CCA-U during S-GW Restoration. |
||
|
CCA-U Accepted |
|||
|
Rule Removals |
The total number of times that the P-GW accepted CCA-U with rule removals from the PCRF during S-GW Restoration. |
||
|
Session Release |
The total number of times the P-GW accepted CCA-U with Session Release Cause from the PCRF during S-GW Restoration. |
||
|
Internal Updates Dropped |
|||
|
Revalidation Timeout |
The total number of DPCA messages that were not sent towards PCRF due to the expiry of revalidation timer when S-GW is down. |
||
|
Pending Updates |
The total number of CCR-Us that were dropped when S-GW is down and update is received from SM/ECS. |
||
|
Sync Request |
The total number of messages that were dropped when S-GW is down and the session sync request is received. |
||
|
SGW Restoration Reported |
|||
|
RAA Sent |
The total number of times S-GW restoration reported in RAA to the PCRF during S-GW Restoration. |
||
|
CCR-U Sent |
The total number of times that S-GW restoration reported in CCR-U to the PCRF during S-GW Restoration. |
||
|
DPCA Message Error Stats |
|||
|
Diameter Protocol Errs |
Total number of errors related to Diameter protocol. |
||
|
Bad Answers |
Total number of errors related to invalid response/answers. |
||
|
Unknown Session Reqs |
Total number of errors related to unknown session requests. |
||
|
Unknown Command Code |
Total number of errors related to unknown command codes. |
||
|
Unsupported Command Code |
Total number of errors related to unsupported command codes. |
||
|
Unk Failure Handling |
Total number of errors related to unknown handling of failures. |
||
|
DPCA Termination Cause Stats |
|||
|
Diameter Logout |
Total number of DPCA session termination due to Diameter logout. |
||
|
Service Not Provided |
Total number of DPCA session termination due to unavailability of service. |
||
|
Bad Answer |
Total number of DPCA sessions terminated due to invalid/bad response reason. |
||
|
Administrative |
Total number of DPCA sessions terminated due to administrative reasons. |
||
|
Link Broken |
Total number of DPCA sessions terminated due to link broken. |
||
|
Auth Expired |
Total number of DPCA sessions terminated due to authorization expired. |
||
|
User moved |
Total number of DPCA sessions terminated as subscriber/user moved to unknown/non-service area. |
||
|
Session Timeout |
Total number of DPCA sessions terminated due to timed out reason. |
||
|
Auth Rejected |
Total number of DPCA sessions terminated due to authorization rejected. |
||
|
Other Errors |
Total number of DPCA sessions terminated due to unknown reasons or reasons not listed in this list. |
||
|
DPCA Experimental Result Code Stats: |
Statistics of the number of times the specific Experimental-Result-Code value was received in the Diameter Gx Credit-Control-Answer (CCA) from the PCRF per IMSA service. |
||
|
Error Initial Parameters |
The number of times DIAMETER_ERROR_INITIAL_PARAMETERS (5140) Experimental-Result-Code value was received in the Diameter Gx CCA. |
||
|
Error Trigger Event |
The number of times DIAMETER_ERROR_TRIGGER_EVENT (5141) Experimental-Result-Code value was received in the Diameter Gx CCA. |
||
|
Bearer Not Authorized |
The number of times DIAMETER_ERROR_BEARER_NOT_AUTHORIZED (5143) Experimental-Result-Code value was received in the Diameter Gx CCA. |
||
|
Traffic Mapping Rejected |
The number of times DIAMETER_ERROR_TRAFFIC_MAPPING_INFO_REJECTED (5144) Experimental-Result-Code value was received in the Diameter Gx CCA. |
||
|
PCC Rule Event |
The number of times DIAMETER_PCC_RULE_EVENT (5142) Experimental-Result-Code value was sent in the Diameter Gx Re-Auth-Request (RAR). |
||
|
Conflicting Request |
This error is used when the PCRF cannot accept the UE-initiated resource request as a network-initiated resource allocation is already in progress with packet filters that cover the packet filters in the received UE-initiated resource request. |
||
|
Bearer Event |
This error is used when a PCC rule for some reason cannot be enforced or modified successfully in a network initiated procedure. |
||
|
Bad Exp Result Code |
The number of times an unknown Experimental-Result-Code value (apart form the ones recognized in CCA that are listed above PCC Rule Event) was received in the Diameter CCA. |
||
|
PCRF Too Busy |
This error is used when the PCRF is unable to process the CCR message due to transient failures. |
||
|
Pending-Trans-Sent |
The total number of times the Experimental Result Code DIAMETER_PENDING_TRANSACTION (4198) is sent to the server. |
||
|
Pending-Trans-rcvd |
The total number of times the Experimental Result Code DIAMETER_PENDING_TRANSACTION (4198) is received from the server. |
||
|
Session Recovery Req |
The total number of times the session recovery request experimental result code is received from PCRF. |
||
|
Diameter Overload Control |
The total number of times the Experimental-Result-code (5198 - DIAMETER_OVERLOAD_RETRY_NOT_ALLOWED_TO_ANY) is received from the PCRF. This result code is used to indicate that all the nodes connected behind the Diameter Agent are overloaded and that the client (ePDG and P-GW) should not attempt the message on the alternate connection. |
||
|
Newer Session Detected |
The total number of times the Experimental-Result-code (5199 - DIAMETER_NEWER_SESSION_DETECTED) is received from the PCRF. When the response message is received with 5199 result code, the Diameter application does not retry to a secondary AAA server. If the Experimental Result-Code 5199 is received in Assume Positive mode, then the current call is terminated. |
||
|
Gx APN Change |
The total number of times the Experimental-Result-code (5999 - DIAMETER_GX_APN_CHANGE) is received from the PCRF. This result code is sent when Virtual APN is selected through PCRF. |
||
|
Diameter Overload Control Stats: |
|||
|
CCA-Initial |
The total number of times the Experimental-Result-code (5198 - DIAMETER_OVERLOAD_RETRY_NOT_ALLOWED_TO_ANY) is received in CCA-I. |
||
|
CCA-Update |
The total number of times the Experimental-Result-code (5198 - DIAMETER_OVERLOAD_RETRY_NOT_ALLOWED_TO_ANY) is received in CCA-U. |
||
|
CCA-Terminate |
The total number of times the Experimental-Result-code (5198 - DIAMETER_OVERLOAD_RETRY_NOT_ALLOWED_TO_ANY) is received in CCA-T. |
||
|
Session Sync Request Stats: |
|||
|
RAR |
The total number of times the RARs in which the session sync request is received. |
||
|
CCA |
The total number of times the CCAs in which the session sync request is received. |
||
|
DPCA FH Retry Server On Event
|
|||
|
CCR-Update |
The total number of times the CCR-U is sent out after Failure-Handling action "continue retry-server-on-event " is applied. |
||
|
CCR-Terminate |
The total number of times the CCR-T is sent out after Failure-Handling action "continue retry-server-on-event " is applied. |
||
|
RAR |
The total number of times the RAR is received after Failure-Handling action "continue retry-server-on-event " is applied. |
||
|
Session Release Cause |
|||
|
CCA |
|||
|
Unspecified Reason |
The total number of IP CAN sessions terminated because of Session Release Cause "Unspecified Reason" received in CCA. |
||
|
UE Subscription Changed |
The total number of IP CAN sessions terminated because of Session Release Cause "UE Subscription Changed" received in CCA. |
||
|
Insuffcnt Srvr Resource |
The total number of IP CAN sessions terminated because of Session Release Cause "Insufficient Server Resources" received in CCA. |
||
|
RAR |
|||
|
Unspecified Reason |
The total number of IP CAN sessions terminated because of Session Release Cause "Unspecified Reason" received in RAR. |
||
|
UE Subscription Changed |
The total number of IP CAN sessions terminated because of Session Release Cause "UE Subscription Changed" received in RAR. |
||
|
Insuffcnt Srvr Resource |
The total number of IP CAN sessions terminated because of Session Release Cause "Insufficient Server Resources" received in CCA. |
||
|
DPCA Failure Handling Stats |
|||
|
Connection Based FH |
|||
|
Total FH Triggered |
Total number of times when ims-auth-service Failure Handling is triggered. |
||
|
Total Message Timeouts |
Total number of response message timeouts, i.e. PCRF failed to respond within the configured timeout value. |
||
|
CCA-Initial |
Response to the CCR-I message was timed out. |
||
|
CCA-Update |
Response to the CCR-U message was timed out. |
||
|
CCA-Terminate |
Response to the CCR-T message was timed out. |
||
|
Total Message Send Errs |
Total number of requests failed to be sent due to socket based send errors. |
||
|
CCR-Initial |
CCR-I failed to be sent due to socket based errors. |
||
|
CCR-Update |
CCR-U failed to be sent due to socket based errors. |
||
|
CCR-Terminate |
CCR-T failed to be sent due to socket based errors. |
||
|
Result Code Based FH |
|||
|
Configured Result Code |
Failure handling being undertaken due to configured result code range. |
||
|
CCA-Initial |
Failure handling being undertaken due to configured result code range for CCA-Initial messages. |
||
|
CCA-Update |
Failure handling being undertaken due to configured result code range for CCA-Update messages. |
||
|
CCA-Terminate |
Failure handling being undertaken due to configured result code range for CCA-Terminate messages. |
||
|
Unh and Unk Result Code |
Failure handling being undertaken due to a result code which is neither defined in the diameter or customer specs. |
||
|
CCA-Initial |
Failure handling being undertaken due to unknown result code for CCA-Initial messages. |
||
|
CCA-Update |
Failure handling being undertaken due to unknown result code for CCA-Update messages. |
||
|
CCA-Terminate |
Failure handling being undertaken due to unknown result code for CCA-Terminate messages. |
||
|
FH Behavior |
|||
|
Continue |
Total number of times the failure handling action "continue" has been undertaken. |
||
|
Retry-And-Continue |
Total number of times the failure handling action "retry-and-continue" has been undertaken. |
||
|
CCR on Call Terminate |
Total number of times the failure handling action "continue" has been undertaken and CCR-T has been sent to PCRF on call termination. |
||
|
Continue-Without-Retry |
Total number of times the failure handling action "continue-without-retry" has been undertaken. This failure action implies that the IMSA call will be continued without retrying to the secondary PCRF. |
||
|
Continue-With-Fallback |
Total number of times the failure handling action "continue-with-fallback" has been undertaken. This failure action implies that the IMSA call will be continued with the PCC rules defined in local policy. |
||
|
Continue-With-Fallback Without Retry |
Total number of times the failure handling action "continue-fallback-wo-retry" has been undertaken. This failure action implies that the IMSA call will be continued with the PCC rules defined in local policy without retrying to the secondary PCRF server. |
||
|
Retry Server On Event |
Total number of times the failure-handling action "continue retry-server-on-event" has been undertaken. |
||
|
Retry and Terminate |
|||
|
Retry-And-Terminate |
Total number of times the failure handling action "retry-and-terminate" has been undertaken. |
||
|
Retry Term without CCRT |
Total number of times the failure handling action "retry-and-terminate" has been undertaken without sending CCR-T to PCRF on call termination. |
||
|
Retry same server |
Total number of times the failure handling action "retry-and-terminate" has been applied to retry to the same server within a configurable timer. |
||
|
Termination |
|||
|
Terminate |
Total number of times the failure handling action "terminate" has been undertaken. |
||
|
Terminate without CCRT |
Total number of times the failure handling action "terminate" has been undertaken without sending CCR-T to PCRF on call termination. |
||
|
Local Fallback Cause Stats |
Displays the reason for fallback to local-policy. |
||
|
Tx-expiry |
Total number of the times the OCS server is unreachable due to Tx expiry. |
||
|
Request-timeout |
Total number of the times the OCS server is unreachable due to request timeout. |
||
|
Diabase error |
Total number of the times the OCS server is unreachable due to Diabase error. |
||
|
Result-code error |
Total number of the times the OCS server is unreachable due to Result code errors. |
||
|
Peer Switches |
|||
|
Attempted Switches |
Total number of peer switches attempted. |
||
|
Successful Switches |
Total number of peer switches successful. |
||
|
Switches-Tx timeout |
Total number of peer switches due to timeout expiry. |
||
|
Switches-RAR change |
Total number of peer switches due to RAR from secondary server. |
||
|
CCA Result Code Stats |
|||
|
Result Code 2xxx |
Total number of CCA messages that have been received with result code 2xxx for Gx. |
||
|
Result Code 3xxx |
Total number of CCA messages that have been received with result code 3xxx for Gx. |
||
|
Result Code 4xxx |
Total number of CCA messages that have been received with result code 4xxx for Gx. |
||
|
Result Code 5xxx |
Total number of CCA messages that have been received with result code 5xxx for Gx. |
||
|
Other Result Code |
Total number of CCA messages that have been received with other result codes for Gx. |
||
|
Backpressure Stats |
|||
|
CCR-I Backpressure Stats |
|||
|
Messages |
Total number of CCR-I messages that are in backpressure state. |
||
|
Failures |
Total number of times the application fails to create a CCR-I message due to no TCP connection when the messages are in backpressure state. |
||
|
Sess-Id Recovery Failures |
Total number of times the CCR-I message is sent before recovering the session ID when the call is running in proxy mode and session recovery happens. |
||
|
CCR-U Backpressure Stats |
|||
|
Messages |
Total number of CCR-U messages that are in backpressure state. |
||
|
Failures |
Total number of times the application fails to create a CCR-U message due to no TCP connection when the messages are in backpressure state. |
||
|
Max Retry |
Total number of times the max retries have been attempted when the CCR-U message is in backpressure state. |
||
|
Dropped Messages |
Total number of CCR-U request messages that are dropped when there are already some messages in backpressure state. |
||
|
Sess-Id Recovery Failures |
Total number of times the CCR-U message is sent before recovering the session ID when the call is running in proxy mode and session recovery happens. |
||
|
CCR-T Backpressure Stats |
|||
|
Messages |
Total number of CCR-T messages that are in backpressure state. |
||
|
Failures |
Total number of times the application fails to create a CCR-T message due to no TCP connection when the messages are in backpressure state. |
||
|
Sess-Id Recovery Failures |
Total number of times the CCR-T message is sent before recovering the session ID when the call is running in proxy mode and session recovery happens. |
||
|
RAA Result Code Stats |
|||
|
Result Code 2xxx |
Total number of RAA messages that are received with the result-code between 2000 and 2999 |
||
|
Result Code 3xxx |
Total number of RAA messages that are received with result-code between 3000 to 3999. |
||
|
Result Code 4xxx |
Total number of RAA messages that are received with result-code between 4000 to 4999. |
||
|
Result Code 5xxx |
Total number of RAA messages that are received with result-code between 5000 to 5999. |
||
|
Other Result Code |
Total number of RAA messages that are received with result-code other than the range of 2xxx to 5xxx. |
||
|
Responses in Queue |
|||
|
Current Responses in Queue |
Total number of out of order responses present in queue across all sessions at current time. |
||
|
Purged Responses |
Total number of responses purged without sending to the session manager. |
||
|
Total Response in Queue |
Total number of responses that are buffered in the queue. |
||
|
Requests in Queue for LP |
|||
|
Current Requests in Queue |
Total number of requests present in the queue which are yet to be sent to Local Policy module. |
||
|
Purged Requests |
Total number of requests purged without sending to Local Policy. |
||
|
Total Requests Fwd to LP |
Total number of outstanding requests forwarded to Local Policy. |
||
|
Session Recovery Failure |
|||
|
Resource Limitation |
Total number of times the rule installation failed due to the resource limitation i.e. when received string is more than expected size like redirecturllen more than 512. |
||
|
Unknown Bearer ID |
Total number of times the rule installation failed due to unknown bearer ID. |
||
|
Invalid QCI |
Total number of times the rule installation failed due to invalid QCI. |
||
|
Invalid ARP |
Total number of times the rule installation failed due to invalid ARP. |
||
|
Bearer-Id in QoS |
Total number of times the rule installation failed due to a mismatch in the bearer ID present in QoS flow. |
||
|
Session Recovery Failure |
|||
|
Activate-LP-Rule |
Indicates the total number of times lp-activate-rules session recovery or ICSR recovery failed. |
||

Feedback