# DCCA Group Schema Statistics

The Diameter Credit Control Application (DCCA) group schema provides operational statistics per CC group, that can be used for monitoring and troubleshooting Gy interface functionality used by the following products:

- GGSN
- HA
- IPSG
- PDSN
- P-GW

IMPORTANT:

Please note that the DCCA-group related bulk statistics variables are moved from the System schema to the DCCA Group schema. These DCCA group bulk statistics variables are retained in the System schema for backward compatibility.
This schema provides the following types of statistics:

- Counter: A counter records incremental data cumulatively and rolls over when the counter limit is reached. All counter statistics are cumulative and reset only by one of the following methods: roll-over when limit is reached, after a system restart, or after a clear command is performed. The limit depends upon the data type.
- Gauge: A gauge statistic indicates a single value; a snapshot representation of a single point in time within a defined time frame. The gauge changes to a new value with each snapshot though a value may repeat from one period to the next. The limit depends upon the data type.
- Information: This type of statistic provides information, often intended to differentiate sets of statistics; for example, a VPN name or IP address. The type of information provided depends upon the data type.

The data type defines the format of the data for the value provided by the statistic. The following data types are used in statistics for this schema:

- Int32/Int64: An integer, either 32-bit or 64-bit: For statistics with the Int32 data type, the roll-over to zero limit is 4,294,967,295. For statistics with the Int64 data type, the roll-over to zero limit is 18,446,744,073,709,551,615.
- Float: A numeric value that can be represented fractionally; for example, 1.345.
- String: A series of ASCII alphanumeric characters in a single grouping, usually pre-configured.

IMPORTANT:

Unless otherwise indicated, all statistics are counters and all statistics are standards-based.

Key Variables: Every schema has some variables which are typically referred to as 'key variables'. These key variables provide index markers to identify which object the statistics apply to. For example, in the card schema, the card number (variable %card%) uniquely identifies a card. For an HA service, the keys would be "%vpnname%" plus "%servname%", as the combination uniquely identifies an HA service. So, in a given measurement interval, one row of statistics will be generated per unique key. The schema keys are identified in the Description section of the table.
Table 1. Bulk Statistic Variables in the DCCA Group Schema

Variables | Description | Data Type
--- | --- | ---
acs-service | Description: Name of the active charging service This is a key variable. Availability: Per system Type: Information | String
cc-group | Description: Name of the credit control group. This is a key variable. Availability: Per system Type: Information | String
cc-cursess | Description: The total number of Credit Control Application (CCA) sessions currently active. Trigger: Increments when a Gy session is successfully created Decrements when the Gy session is terminated Availability: Per Credit Control Group Type: Gauge | Int64
cc-ttlecsadd | Description: The total number of ECS sessions added to CCA. Trigger: Increments when a new CC session is being created by ECS. Availability: Per Credit Control Group Type: Counter | Int64
cc-ttlstart | Description: The total number of CCA sessions started. Trigger: Increments when CCR-I is successfully sent. Availability: Per Credit Control Group Type: Counter | Int64
cc-ttlsessupd | Description: The total number of CCA sessions updated. Trigger: Increments when a CC session update is sent by ECS to DCCA module Availability: Per Credit Control Group Type: Counter | Int64
cc-ttlterm | Description: The total number of CCA sessions terminated. Trigger: Increments when a CC session terminate is sent by ECS to DCCA module Availability: Per Credit Control Group Type: Counter | Int64
cc-sessfailover | Description: The total number of CCA sessions failed. Trigger: Increments when a CC session message is retried on a secondary server due to session failover Availability: Per Credit Control Group Type: Counter | Int64
cc-msg-recv | Description: The total number of CCA messages received. Trigger: Increments when a CCA message is successfully received Availability: Per Credit Control Group Type: Counter | Int64
cc-msg-sent | Description: The total number of CCA messages sent. Trigger: Increments when a CCA message is successfully sent to the server Availability: Per Credit Control Group Type: Counter | Int64
cc-msg-request | Description: The total number of CCR (Credit Control Request) messages that are sent out from the system to the Diameter Server. The CCR can be Initial/Update or Terminate. Trigger: Increments when CCR (Credit Control Request) message is sent out from system to the Diameter Server Availability: Per Credit Control Group Type: Counter | Int64
cc-msg-answer | Description: The total number of CCA (Credit Control Answer) messages that are received by the system from the Diameter Server. Trigger: Increments when CCA message is received Availability: Per Credit Control Group Type: Counter | Int64
cc-msg-ccrinit | Description: The total number of CCR-Initial (Initial Credit Control Request) messages that are sent out from the system to the Diameter Server. Trigger: Increments when CCR-I message is successfully sent Availability: Per Credit Control Group Type: Counter | Int64
cc-msg-ccainit | Description: The total number of CCA-Initial (Initial Credit Control Answer) messages that are received by the system from the Diameter Server. Trigger: Increments when CCA-I message is successfully received Availability: Per Credit Control Group Type: Counter | Int64
cc-msg-ccainitaccept | Description: The total number of CCA-Initial (Initial Credit Control Answer) messages that are sent from Diameter Server and accepted by the system Trigger: Increments when a CCA-Initial message from Diameter Server is accepted by the system Availability: Per Credit Control Group Type: Counter | Int64
cc-msg-ccainitreject | Description: The total number of CCA-Initial (Initial Credit Control Answer sent) messages that are sent from Diameter Server and rejected by the system Trigger: Increments when a CCA-Initial (Initial Credit Control Answer sent) message from Diameter Server is rejected by system Availability: Per Credit Control Group Type: Counter | Int64
cc-msg-ccainittimeout | Description: The total number of CCA-Initial-Timeouts (CCR-I sent but did not receive CCA till the timer expired) messages that are sent to the system from Diameter Server. Trigger: Increments when CCR-I is sent but CCA-I is not received till Tx timer expiry. Availability: Per Credit Control Group Type: Counter | Int64
cc-msg-ccrupdate | Description: The total number of CCR-Updates (Credit Control Request with Update) messages that are sent out from the system to the Diameter Server. Trigger: Increments whenever a CCR-Update request is successfully sent from the system. Availability: Per Credit Control Group Type: Counter | Int64
cc-msg-ccaupdate | Description: The total number of CCA-Update (Credit Control Answer for update) messages that are received by the system from the Diameter Server. Trigger: Increments whenever an update answer message is received from the server. Availability: Per Credit Control Group Type: Counter | Int64
cc-msg-ccaupdatetimeout | Description: The total number of CCA-Update Timeouts (CCR-U sent but did not receive CCA till the timer expired) messages that are sent to the system from Diameter Server. Trigger: Increments when CCR-U is sent but an answer for this request is not received till Tx timer expiry. Availability: Per Credit Control Group Type: Counter | Int64
cc-msg-ccrfinal | Description: The total number of CCR-Final (Credit Control Request with Final) messages that are sent out from the system to the Diameter Server. Trigger: Increments whenever a CCR-Terminate request for a session is successfully sent from the system Availability: Per Credit Control Group Type: Counter | Int64
cc-msg-ccafinal | Description: The total number of CCA-Final (Credit Control Answer for final update sent) messages that are received by the system from Diameter Server. Trigger: Increments when the system receives answer message (CCA-T) for Terminate request that was sent Availability: Per Credit Control Group Type: Counter | Int64
cc-msg-ccafinaltimeout | Description: The total number of CCA-Final Timeouts (CCR-T sent but did not receive CCA till the timer expired) messages that are received by the system from Diameter Server. Trigger: Increments when CCR-T is sent but an answer for this request is not received till Tx timer expiry. Availability: Per Credit Control Group Type: Counter | Int64
cc-msg-asr | Description: The total number of Abort Session Request messages that are sent from the Diameter Server to the system. Trigger: Increments when the system receives answer message (CCA-T) for Terminate request that was sent Availability: Per Credit Control Group Type: Counter | Int64
cc-msg-asa | Description: The total number of Abort Session Answer messages sent from the system to the Diameter server. This message will be followed by a CCR-Terminate to terminate the session. Trigger: Increments when the system replies with an Abort Session Answer message for the Abort Session Request message sent from Diameter Server Availability: Per Credit Control Group Type: Counter | Int64
cc-msg-rar | Description: The total number of ReAuth Request messages that are sent from the Diameter Server to the system. Trigger: Increments when a Re-Authorization Request message is sent from Diameter Server Availability: Per Credit Control Group Type: Counter | Int64
cc-msg-raa | Description: The total number of ReAuth Answer messages sent from the system to the Diameter server. This message is followed by a CCR-Update to update the Diameter server about the session. Trigger: Increments when the system replies with a Re-auth Answer message for the Re-Auth Request sent from Diameter Server Availability: Per Credit Control Group Type: Counter | Int64
cc-msg-ccadropped | Description: The total number of CCA (Credit Control Answer) messages dropped by the system. Trigger: Increments when the system drops/ignores a CCA message received from the server Availability: Per Credit Control Group Type: Counter | Int64
cc-msgerr-proto | Description: The total message errors due to Diameter protocol. Trigger: Increments whenever a message with result-codes 3xxx- errors due to Diameter protocol is received from the server Availability: Per Credit Control Group Type: Counter | Int64
cc-msgerr-badanswer | Description: The total message errors due to invalid response - CCA Parse error. Trigger: Increments when the system receives an undefined mandatory AVP from the server Availability: Per Credit Control Group Type: Counter | Int64
cc-msgerr-unknownsess | Description: The total message errors due to invalid session requests. Trigger: Increments for every occurrence of invalid session request message Availability: Per Credit Control Group Type: Counter | Int64
cc-msgerr-unknowncomm | Description: The total message errors due to invalid/unknown command code (CCA, ASR, RAR). Trigger: Increments whenever a response is received for a valid request with corrupted Command Code. Availability: Per Credit Control Group Type: Counter | Int64
cc-msgerr-reqtimeout | Description: The total message errors due to request timeout. Trigger: Increments whenever a request message is timed-out Availability: Per Credit Control Group Type: Counter | Int64
cc-msgerr-parse | Description: The total message errors due to parsing errors. Trigger: Increments whenever a message is received with parsing errors Availability: Per Credit Control Group Type: Counter | Int64
cc-msgerr-unkratinggrp | Description: The total message errors due to invalid/unknown Rating Groups. Rating group is used to identify a particular type of traffic. Trigger: Increments when Unknown Rating-Group is preemptively received from server or a preemptive MSCC is received after session abortion Availability: Per Credit Control Group Type: Counter | Int64
cc-msgerr-unkrulebase | Description: The total message errors due to invalid/unknown Rulebase applied. Trigger: Increments when rulebase change is attempted and the system is not able to switch to this because the plan indicated might be unknown/invalid. Availability: Per Credit Control Group Type: Counter | Int64
cc-msgerr-unkfailure | Description: The total number of unknown server -provided session failover actions. This counts the number of unknown server-provided session failover actions. Trigger: Increments when an unknown CCFH action is received from the server (terminate/continue/retry and terminate are considered to be valid CCFH values) Availability: Per Credit Control Group Type: Counter | Int64
cc-msgerr-transfailure | Description: The total number of errors resulting from requests that could not be satisfied at the time they were received. The requests may be satisfied in the future. Trigger: Increments when CCA messages have been received with a Diameter Result-Code=4XXX. Availability: Per Credit Control Group Type: Counter | Int64
cc-msgerr-permfailure | Description: The total number of errors resulting from requests that can never be satistifed. Trigger: Increments when CCA messages have been received with a Diameter Result-Code=5XXX. Availability: Per Credit Control Group Type: Counter | Int64
cc-upd-threshold | Description: For each Rating group, the Diameter server sends a threshold (this is also configurable in the system) after which an update needs to be sent. For example, a subscriber quota of 1000 bytes with 900 as a threshold is sent to CCA. When 900 bytes have been used by the system, an update message is sent for quota. This counter gives the number of updates sent because of the threshold. Trigger: Increments whenever threshold value for a quota-type allocated to any rating-group is reached and an update request is sent to the server to report the usage. Availability: Per Credit Control Group Type: Counter | Int64
cc-upd-qht | Description: The total number of updates sent due to expiry of Quota Hold Timer (QHT). Trigger: Increments when updates are sent due to QHT expiry Availability: Per Credit Control Group Type: Counter | Int64
cc-upd-final | Description: The total number of updates sent due to exhaustion/invalidation/service denial. Trigger: Increments when updates are sent due to quota exhaustion/invalidation/service denial. Availability: Per Credit Control Group Type: Counter | Int64
cc-upd-quotaexhaust | Description: The total number of updates sent due to exhaustion of subscriber quota. Trigger: Increments when updates are sent because the quota for a particular rating-group is exhausted Availability: Per Credit Control Group Type: Counter | Int64
cc-upd-validitytime | Description: The total number of updates sent due to expiry of the session validity time. Trigger: Increments when updates are sent due to validity time expiry for a rating-group Availability: Per Credit Control Group Type: Counter | Int64
cc-upd-otherquota | Description: The total number of updates sent to report the usage of one quota type, while the other quota reached a trigger condition. Trigger: Increments when updates are sent to report the usage of one quota type, while the other quota reached a trigger condition Availability: Per Credit Control Group Type: Counter | Int64
cc-upd-ratingchange | Description: The total number of updates sent due to changes in RAT/QOS/SGSN/CELLID/LAC. Trigger: Increments when updates are sent due to changes in RAT/QOS/SGSN/CELLID/LAC Availability: Per Credit Control Group Type: Counter | Int64
cc-upd-forcedreauth | Description: The total number of updates sent because of RAR. Trigger: Increments when the server asks for forced-reauthorization of the subscriber and sends the update request Availability: Per Credit Control Group Type: Counter | Int64
cc-upd-titsutime | Description: The total number of updates sent due to time interval after tariff switch. This is specific to WiMax prepaid customers. Trigger: Increments when updates are sent due to time interval after tariff switch Availability: Per Credit Control Group Type: Counter | Int64
cc-term-diamlogout | Description: The total number of CCA sessions terminated due to subscriber logout. Trigger: Increments when a subscriber initiates termination of a Diameter session Availability: Per Credit Control Group Type: Counter | Int64
cc-term-servnotprov | Description: The total number of CCA sessions terminated due to unavailability of service. Trigger: Increments when a session is terminated due to unavailability of Diameter service Availability: Per Credit Control Group Type: Counter | Int64
cc-term-badanswer | Description: The total number of CCA sessions terminated due to invalid/unknown response received. Trigger: Increments when a session is terminated due to invalid/unknown/unsuccessful response received Availability: Per Credit Control Group Type: Counter | Int64
cc-term-admin | Description: The total number of CCA sessions terminated by an administrative user. Trigger: Increments when a session termination is done by the system - administrative decision taken by our system in relevant scenarios Availability: Per Credit Control Group Type: Counter | Int64
cc-term-linkbroken | Description: The total number of CCA sessions terminated due to broken uplink/downlink (connection between peers). Trigger: Increments when a session is terminated because the connection between peers is lost - Diameter link is broken. Availability: Per Credit Control Group Type: Counter | Int64
cc-term-authexpired | Description: The total number of CCA sessions terminated due to expiry of subscriber authorization. Trigger: Increments when an update is sent to check for the expiry of lifetime authorization of the subscriber and if the server indicates expiry of authorization, the session will be terminated. Availability: Per Credit Control Group Type: Counter | Int64
cc-term-usermoved | Description: The total number of CCA sessions terminated as subscriber moved out of the service area. Trigger: Increments when session termination happens because the subscriber has moved out of the service area. Availability: Per Credit Control Group Type: Counter | Int64
cc-term-sesstimeout | Description: The total number of CCA sessions terminated due to timeout. Trigger: Increments when a session terminates because the session manager has indicated a session-timeout. Availability: Per Credit Control Group Type: Counter | Int64
cc-badans-auth-appid | Description: The absence or unexpected value in Auth-Application-Id AVP. Trigger: Increments when a session is terminated because of Diameter bad answer due to absence or unexpected value of Auth-Application-Id AVP. Availability: Per Credit Control Group Type: Counter | Int64
cc-badans-sessid | Description: The absence or unexpected value in Session-Id AVP. Trigger: Increments when a session is terminated because of Diameter bad answer due to absence or unexpected value of Session-id AVP Availability: Per Credit Control Group Type: Counter | Int64
cc-badans-cc-req-num | Description: The absence or unexpected value in CC-Request-Number AVP. Trigger: Increments when a session is terminated because of Diameter bad answer due to absence or unexpected value of CC-Request-Number AVP Availability: Per Credit Control Group Type: Counter | Int64
cc-badans-cc-req-type | Description: The absence or unexpected value in CC-Request-Type AVP. Trigger: Increments when a session is terminated because of Diameter bad answer due to absence or unexpected value of CC-Request-Type AVP Availability: Per Credit Control Group Type: Counter | Int64
cc-badans-origin-host | Description: The absence of Origin-Host AVP. Trigger: Increments when a session is terminated because of Diameter bad answer due to absence or unexpected value of Origin-Host AVP Availability: Per Credit Control Group Type: Counter | Int64
cc-badans-origin-realm | Description: The absence of Origin-Realm AVP. Trigger: Increments when a session is terminated because of Diameter bad answer due to absence or unexpected value of Origin-Realm AVP Availability: Per Credit Control Group Type: Counter | Int64
cc-badans-parsemsg-err | Description: The number of parse errors in the message. Trigger: Increments when a session is terminated because of Diameter bad answer due to parsing errors in the message Availability: Per Credit Control Group Type: Counter | Int64
cc-badans-parsemscc-err | Description: The number of parse errors in MSCC AVP. Trigger: Increments when a session is terminated because of Diameter bad answer due to parsing errors detected while processing the Multiple-Services-Credit-Control AVP in the message Availability: Per Credit Control Group Type: Counter | Int64
cc-badans-misc-err | Description: The number of other miscellaneous errors. Trigger: Increments when a session is terminated because of Diameter bad answer due to miscellaneous reasons like failure installing the rulebase change/bandwidth/firewall policy, etc. Availability: Per Credit Control Group Type: Counter | Int64
cc-traf-catcreate | Description: The total traffic categories (MSCC) created. Trigger: Increments when a new MSCC is created Availability: Per Credit Control Group Type: Counter | Int64
cc-traf-catdelete | Description: The total traffic categories (MSCC) deleted. Trigger: Increments whenever an MSCC is deleted in an ongoing session Availability: Per Credit Control Group Type: Counter | Int64
cc-traf-catlookup | Description: The total traffic categories/MSCC lookups failed. Trigger: Increments when a lookup operation is performed in the list of MSCCs Availability: Per Credit Control Group Type: Counter | Int64
cc-traf-hits | Description: The total traffic categories/MSCC lookups successful. Trigger: Increments when a lookup of MSCC is successful Availability: Per Credit Control Group Type: Counter | Int64
cc-traf-misses | Description: The total traffic categories triggered/MSCC lookups failed. Trigger: Increments when a lookup operation for a particular MSCC fails. Availability: Per Credit Control Group Type: Counter | Int64
cc-traf-triggerevent | Description: The total triggers for traffic categories/MSCCs. Trigger: Increments whenever there is a change in certain trigger parameters like RAT, SGSN-IP-ADDRESS, QOS, CELLID, etc. Availability: Per Credit Control Group Type: Counter | Int64
cc-traf-finalunit | Description: The total final-units-actions taken on MSCCs. Trigger: Increments whenever FUI action is imposed on a particular rating group. Availability: Per Credit Control Group Type: Counter | Int64
cc-traf-catsuccess | Description: The total number of successful allocation of credits for traffic category/MSCC (result-code 2001). Trigger: Increments when the server responds with result-code 2001 indicating successful allocation of credits for traffic category Availability: Per Credit Control Group Type: Counter | Int64
cc-traf-ratingfail | Description: The total number of quota retries because of rating failure due to category not recognized (result-code 5031). Trigger: Increments when the server responds with result-code 5031 indicating rating failure due to category not recognized Availability: Per Credit Control Group Type: Counter | Int64
cc-traf-servdenied | Description: The total number of quota retries due to denial of end user service (result-code 4010). Trigger: Increments when the server responds with result-code 4010 indicating end user service denial. Availability: Per Credit Control Group Type: Counter | Int64
cc-traf-limitreached | Description: The total number of retries due to credit limit reached (result-code 4012). Trigger: Increments when the server responds with result-code 4012 indicating that the credit limit has reached Availability: Per Credit Control Group Type: Counter | Int64
cc-traf-authreject | Description: The total number of retries due to authorization rejected (result-code 5003). Trigger: Increments when the server responds with result-code 5003 indicating authorization rejection. Availability: Per Credit Control Group Type: Counter | Int64
cc-traf-othererror | Description: The total number of miscellaneous/unknown errors not specified by the system (Diameter_unable_to_comply [result-code 5012]). Trigger: Increments when the server responds with result-code 5012 indicating miscellaneous/unknown errors not specified by the system Availability: Per Credit Control Group Type: Counter | Int64
cca-init-2001-rc | Description: The total number of CCA-I messages received with a Diameter Result-Code=2001 at command level. Trigger: Increments when a CCA-I is received with Result-Code=2001 Availability: Per Credit Control Group Type: Counter | Int64
cca-init-5003-rc | Description: The total number of CCA-I messages received with a Diameter Result-Code=5003 at command level. Trigger: Increments when a CCA-I is received with Result-Code=5003 Availability: Per Credit Control Group Type: Counter | Int64
cca-init-4011-rc | Description: The total number of CCA-I messages received with a Diameter Result-Code=4011 at command level. Trigger: Increments when a CCA-I is received with Result-Code=4011 Availability: Per Credit Control Group Type: Counter | Int64
cca-init-4012-rc | Description: The total number of CCA-I messages received with a Diameter Result-Code=4012 at command level. Trigger: Increments when a CCA-I is received with Result-Code=4012 Availability: Per Credit Control Group Type: Counter | Int64
cca-updt-2001-rc | Description: The total number of CCA-U messages received with a Diameter Result-Code=2001 at command level. Trigger: Increments when a CCA-U is received with Result-Code=2001 Availability: Per Credit Control Group Type: Counter | Int64
cca-updt-5003-rc | Description: The total number of CCA-U messages received with a Diameter Result-Code=5003 at command level. Trigger: Increments when a CCA-U is received with Result-Code=5003 Availability: Per Credit Control Group Type: Counter | Int64
cca-updt-4011-rc | Description: The total number of CCA-U messages received with a Diameter Result-Code=4011 at command level. Trigger: Increments when a CCA-U is received with Result-Code=4011 Availability: Per Credit Control Group Type: Counter | Int64
cca-updt-4012-rc | Description: The total number of CCA-U messages received with a Diameter Result-Code=4012 at command level. Trigger: Increments when a CCA-U is received with Result-Code=4012 Availability: Per Credit Control Group Type: Counter | Int64
fail-action-term | Description: This variable indicates how many times the DCCA failure handling with action terminate has been invoked in each measurement interval. Trigger: Increments when a call is terminated as a result of failure handling actions Availability: Per Credit Control Group Type: Counter | Int64
fail-action-contd | Description: This variable indicates how many times the DCCA failure handling with action continue has been invoked in each measurement interval. Trigger: Increments when a call is continued as a result of failure handling actions Availability: Per Credit Control Group Type: Counter | Int64
offline-active-sess | Description: The current number of active data sessions that are converted from online to offline charging due to DCCA failure handling Trigger: Increments when a call is converted from online to offline Decrements when a offline call is cleared or terminated Availability: Per Credit Control Group Type: Gauge | Int64
cca-2001-rc | Description: Total number of CCA messages received with a Diameter Result-Code=2001 at command level. Trigger: Increments when a CCA is received with Result Code=2001 Availability: Per Credit Control Group Type: Counter | Int64
cca-2002-rc | Description: Total number of CCA messages received with a Diameter Result-Code=2002 at command level. Trigger: Increments when a CCA is received with Result Code=2002 Availability: Per Credit Control Group Type: Counter | Int64
cca-4001-rc | Description: Total number of CCA messages received with a Diameter Result-Code=4001 at command level. Trigger: Increments when a CCA is received with Result Code=4001 Availability: Per Credit Control Group Type: Counter | Int64
cca-4002-rc | Description: Total number of CCA messages received with a Diameter Result-Code=4002 at command level. Trigger: Increments when a CCA is received with Result Code=4002 Availability: Per Credit Control Group Type: Counter | Int64
cca-4011-rc | Description: Total number of CCA messages received with a Diameter Result-Code=4011 at command level. Trigger: Increments when a CCA is received with Result Code=4011 Availability: Per Credit Control Group Type: Counter | Int64
cca-4012-rc | Description: Total number of CCA messages received with a Diameter Result-Code=4012 at command level. Trigger: Increments when a CCA is received with Result Code=4012 Availability: Per Credit Control Group Type: Counter | Int64
cca-5001-rc | Description: Total number of CCA messages received with a Diameter Result-Code=5001 at command level. Trigger: Increments when a CCA is received with Result Code=5001 Availability: Per Credit Control Group Type: Counter | Int64
cca-5002-rc | Description: Total number of CCA messages received with a Diameter Result-Code=5002 at command level. Trigger: Increments when a CCA is received with Result Code=5002 Availability: Per Credit Control Group Type: Counter | Int64
cca-5003-rc | Description: Total number of CCA messages received with a Diameter Result-Code=5003 at command level. Trigger: Increments when a CCA is received with Result Code=5003 Availability: Per Credit Control Group Type: Counter | Int64
cca-5004-rc | Description: Total number of CCA messages received with a Diameter Result-Code=5004 at command level. Trigger: Increments when a CCA is received with Result Code=5004 Availability: Per Credit Control Group Type: Counter | Int64
cca-5005-rc | Description: Total number of CCA messages received with a Diameter Result-Code=5005 at command level. Trigger: Increments when a CCA is received with Result Code=5005 Availability: Per Credit Control Group Type: Counter | Int64
cca-5006-rc | Description: Total number of CCA messages received with a Diameter Result-Code=5006 at command level. Trigger: Increments when a CCA is received with Result Code=5006 Availability: Per Credit Control Group Type: Counter | Int64
cca-other-rc | Description: Total number of CCA messages received with all other Diameter Result-Codes. Trigger: Increments when a CCA is received with all other result codes Availability: Per Credit Control Group Type: Counter | Int64
cc-ocs-unreachable-txexpiry | Description: Total number of tx-expiry happened in case of OCS unreachable. Trigger: Increments when a Tx expiry occurs in the event of OCS being unreachable Availability: Per Credit Control Group Type: Counter | Int64
cc-ocs-unreachable-rsp-timeout | Description: Total number of response-timeouts happened in case of OCS unreachable. Trigger: Increments when a response-timeout is received when the OCS is unreachable Availability: Per Credit Control Group Type: Counter | Int64
cc-ocs-unreachable-conn-fail | Description: Total number of times the TCP connection is down when the OCS is unreachable. Trigger: Increments whenever the TCP connection is down when OCS is in unreachable state Availability: Per Credit Control Group Type: Counter | Int64
cc-ocs-unreachable-server-retry | Description: Total number of times the Server-Retries are performed when OCS is unreachable. Trigger: Increments whenever a server-retry is performed when the OCS is unreachable Availability: Per Credit Control Group Type: Counter | Int64
cc-ocs-unreachable-action-cont | Description: Total number of times the action “continue” was applied due to OCS unreachable. Trigger: Increments when the action “continue” is applied in OCS unreachable state Availability: Per Credit Control Group Type: Counter | Int64
cc-ocs-unreachable-action-term | Description: Total number of times the action “terminate” was applied due to OCS unreachable. Trigger: Increments when the action “terminate” is applied in OCS unreachable state Availability: Per Credit Control Group Type: Counter | Int64
cc-assume-pos-curr-sess | Description: Total number of current sessions in assume positive state. Trigger: Increments whenever the current session is in assume positive state Availability: Per Credit Control Group Type: Counter | Int64
cc-assume-pos-cumlt-sess | Description: Cumulative number of sessions in assume positive state. Trigger: Increments whenever the cumulative of current sessions is in assume positive state Availability: Per Credit Control Group Type: Counter | Int64
IMPORTANT: For information on statistics that are common to all schema see the Statistics and Counters Overview chapter.