Microsoft Lync and SIP Trunking

Metrics like the number of active calls and their direction; whether they’re inbound, outbound, internal or in transit allows you to gauge traffic flow. Further information about the type of call – whether it is part of a conference, and comprises just audio, or includes data or video helps you provision sufficient bandwidth.

Voice quality needn’t be an issue with SIP trunking if two key measures are applied – sufficiently provisioned or over-provisioned links, and prioritization of voice traffic. This white paper explains some of the metrics you can use to help provision correctly including insight to peak and average usage, as well as peaks, troughs and spikes.

It’s also important to monitor the connection between the Microsoft Mediation Server and the Session Border Controller and ensure the SBC is not overloaded so it can continue to provide its vital services to the enterprise and the service provider.

Voice prioritization will be a matter for voice and network administrators to agree on and configure data management methods so that the network can accommodate the delay-sensitive, real-time demands of voice.

As you know within Lync Server environments there are multiple servers, each playing its role in delivering enterprise voice and Unified Communications. Issues with server capacity like insufficient CPU cycles for processing can cause inability to place calls, and for calls that are active, audio distortions. You can monitor the call load to identify the busiest hour and other common busy times to identify if servers become overloaded and unable to service user requests and deliver good voice quality.

Monitoring Lync Server pools identifies problems with the pool itself as well as individual servers and intelligent alerts demistify potential issues before they become real problems. For example a Front End Server within the pool may be consistently using over 90 percent of its processing power and available memory. This can cause attempted calls to fail because of time-outs or insufficient resources. Such overloading is easily identified and administrators are alerted so they can investigate and rectify any load balancing or overall pool capacity issues.