As more companies migrate to SIP trunks and use Session Border Controllers (SBC’s) or CUBE, it becomes increasingly important to include the this data in your overall analysis of routing and traffic. An SBC/CUBE sits between the company and their service provider, and is typically deployed at the edge of a company’s network (border).
Since all sessions that pass through a company’s network border actually pass through the SBC/CUBE, combining this data with voice platform data provides a clear picture of how calls are routed in/out and to/from the entire infrastructure. Microcall’s integration with SBC’s (CUBE, Avaya SBC, Sonus, Oracle Acme, AudioCodes, etc.), in addition to CDR reporting, provides optimal cradle-to-grave analysis.
SBC/CUBE Reporting Includes:
- Determine Max Peak Usage on each trunk.
- Automatic alerts when overflow or Disaster Recovery trunk is utilized.
- Automatic alerts when call quality goes below a specified MOS rating.
- Busy times for each trunk.
- Graphs/charts to analyze historical trends on each trunk.
- Maximum number of concurrent conversations on SIP trunks and when this occurred.
- Measure QoS Analytics – Jitter, Packet Loss, Latency, MOS rating, R Factor.
- Discover SIP trunks that are under-utilized.
- Follow calls “cradle-to-grave” from the voice platform through the SBC to confirm that calls are routed correctly.
- Analyze Backend SIP calls that route to third party vendors for customer service/help desk calls.
- Review Ingress and Egress paths to better understand how calls are routing.
- Determine which trunks have the capacity to handle new traffic from new locations.
- Confirm if carriers are load balancing correctly.
- Review SIP traffic to verify the accuracy of SIP provider billing statements.
