Remote Site Visibility from NETSCOUT Reduces MTTR for UC&C Problems Affecting Employees
IT teams can learn how packet-level visibility at remote sites helped one global organization find the cause of recurring Voice over Internet Protocol (VoIP) call quality problems between its San Jose office and London headquarters. The use case shows how nGeniusONE call search and Quality of Service (QoS) analysis reduced mean time to restore (MTTR) voice quality.
What causes poor VoIP call quality for remote employees?
Latency, jitter, packet loss, and dropped packets all affect call quality and often result in distorted video, choppy connections, or inaudible conversation. Application traffic now passes through cloud, colocation, SaaS and UCaaS applications, third-party providers, and remote sites, which makes the source of a problem harder to prove, especially when IT works with several WAN vendors.
How did the IT team find the root cause?
InfiniStreamNG appliances at the WAN edge of each remote site and headquarters continuously gathered packet-level data for nGeniusONE. The team then followed this workflow:
• Searched for the affected user's phone number with the nGeniusONE call search function
• Opened the single call view to examine the conversations in question
• Found loss and jitter on calls between San Jose and London in the Call Search Summary view
• Used QoS analysis to compare the QoS class on traffic leaving London with the class on traffic arriving in San Jose
What was the problem and how was it fixed?
QoS analysis showed that traffic leaving London was assigned class 46, which prioritizes voice, while traffic from the WAN provider to San Jose was set to 0, meaning best effort. The team sent nGeniusONE screen captures to the WAN provider to request a correction, then configured alerts for QoS mismatches and a weekly report for the head of IT.
Frequently Asked Questions
Why was remote site instrumentation important in this use case?
Instrumentation at each remote site and WAN provider let IT prove that the misconfiguration came from the WAN provider rather than San Jose equipment, a bandwidth bottleneck, or another cause. Without it, the team likely would have lost hours or days.
How did the team prevent the problem from recurring?
The team configured nGeniusONE alerts that notify them of QoS mismatches and scheduled a weekly trend report to the head of IT.
Asset Type: Use Case