Viewing Accounting Data and Statistics

This section explains how to view accounting data and statistics. See Admission Control and Quality of Service Reporting in the Oracle Communications Session Border Controller ACLI Configuration Guide for additional details about Quality of Service (QoS). See the Oracle Communications Session Border Controller RADIUS Guide for additional details about Remote Authentication Dial-in User Service (RADIUS).

QoS Reporting

If you are using for the QoS functionality in collecting and calculating the jitter, latency, and loss statistics. QoS reporting provides you with real-time evaluation of network and route performance. It lets you contrast internal domain and external domain performance and facilitates SLA verification and traffic engineering.

QoS metrics are collected and reported on a per-session basis, per call-leg basis for completed calls. These metrics are reported through real-time RADIUS records along with call accounting data. These metrics are the result of the monitoring of the Real-Time Transport Protocol (RTP) and Real-Time Control Protocol (RTCP) traffic for each flow that has QoS enabled.

The following statistics:

• lost packets for RTP and RTCP that indicates the count of packets lost based on comparing the sequence numbers since the beginning of the call or the last context memory flow
• jitter count for RTP and RTCP that indicates the incremental number of packets that have been used to generate total and max jitter since the beginning of the call or the last context memory poll
• jitter total for RTP and RTCP indicates the incremental accumulated jitter (ms) over all the packets received since the beginning of the call or the last context memory poll
• jitter max for RTP and RTCP that indicates the maximum single jitter value (ms) from all the packets since the beginning of the call or the last context memory poll
• latency count for RTCP only indicates the number of RTCP frames over which latency statistics have been accumulated since the beginning of the call or the last context memory poll
• latency total for RTCP only indicates the incremental total of latency values reported since the beginning of the call or the last context memory poll
• latency max for RTCP only indicates the highest single latency value measured since the beginning of the call or the last context memory poll

From these flow context statistics the QoS daemon derives the following statistics that are kept in host memory while the call is active:

• lost packets indicates the total number of RTP and RTCP lost packets for the call
• jitter count indicates the number of RTP and RTCP packets that make up a call
• jitter total indicated the accumulated jitter over all the packets received during the call
• jitter average indicates the total accumulated jitter divided by the total jitter count for the call
• jitter max indicates the maximum single jitter value from all the packets during the call
• latency count for RTCP indicates the number of RTCP frames of which latency statistics have been accumulated during the call
• latency total for RTCP only indicates the incremental total of latency values reported
• latency max for RTCP only indicates the highest latency value reported during the call
• latency average for RTCP only indicates the RTCP latency total divided by the latency count

You can access QoS statistics that provide information about four areas of call performance.