Chapter 11 Quality Monitoring and Statistics Gathering
Billing and Call Detail Records
Billing and Call Detail Records
One main function of SBC is to generate correct billing, call detail and usage records. The DBE supports collecting statistics data and sending the data to the Signaling Border Element (SBE).
The following are some of the methods by which the DBE keeps track of statistics:
•Call statistics
The DBE generates statistics for a given call by collecting information such as packet count and packets dropped. The DBE also snoops into the RTCP packets and reports back to the SBE at the end of the call. The DBE tracks and reports other statistics, such as call duration, media up event, media down event, and invalid source alert, to the SBE for billing and security purposes.
•H.248 Network Quality Alert (nt/qualert) event
The H.248 nt/qualert event offers another method to check whether there are any hung calls. A voice call is considered a hung call when media packets are not present on the active stream and the call is not on hold nor has the hold timer expired. The H.248 nt/qualert feature generates a middlebox pinhole timer expired event when it detects this type of media loss. This feature is enabled by default.
•Discarded Packets Statistics
The DBE tracks dropped packets when incoming packets fail to match the address and port mask specified using the H.248 Gate Management package. With this type of reporting, the DBE collects accurate packet information for a given user and also enhances network security.
congestion-threshold Command
The
DBE Status Notification
The DBE notifies the SBE about critical status changes (for example, resource shortage or performance degradation).
Enhanced Event Notification and Auditing
The Enhanced Event Notification and Auditing features address some of the limitations of H.248 event notification.
Previously, event notification was subject to the following limitations:
•If an H.248 event notification request from the DBE went unacknowledged by the MGC, then details of that event were lost, and the MG and MGC states could diverge as a result. (There is no current H.248 mechanism by which historical event information can be relearned by the MGC.)
|
|
| Cisco IOS XE Integrated Session Border Controller Configuration Guide for the Cisco ASR 1000 Series Aggregation Services Routers | |
|
|
| ||
|
|
|
| |
|
|
| ||
