As more companies migrate to SIP trunks and use Session Border Controllers (SBC) or CUBE, it becomes increasingly important to include this data in your overall analysis of routing and traffic. A 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 (CDR) data provides a clear picture of how calls are routed in/out and to/from the entire infrastructure. Microcall 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:
- Measure Maximum Concurrent Conversations on SIP trunks and when this occurred.
- Receive automatic alerts when overflow or Disaster Recovery trunks are utilized.
- Follow calls “cradle-to-grave” from the voice platform through the SBC/CUBE to confirm that calls are routed correctly.
- Receive automatic alerts when Call Quality goes below a specified MOS rating.
- Monitor traffic through each Dial Peer.
- Determine Busy times for each trunk.
- Use graphs/charts to analyze historical trends on each trunk.
- Determine Max Peak Usage on each trunk.
- Measure QoS Analytics – Jitter, Packet Loss, Latency, MOS rating, R Factor.
- Discover SIP trunks that are under-utilized.
- 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, and much more.
