The network administrator of an aviation business recently deployed VoIP throughout the company network. He now wishes to keep an eye on the VoIP call quality throughout all call paths in the network, especially those with poor quality so as to troubleshoot & rectify at the earliest, before business is affected.
1) The administrator keeps a watch on the 'Top Call Performance by Location' section found in the VoIP Overview dashboard. He finds the top problematic VoIP sites having poor Mean Opinion Scores (MOS), with MOS scores graphically displayed on time-line charts.
2) Just beside the time-line chart, through the jitter, packet loss and latency values displayed, the administrator discovers that the site with the poorest MOS score is hit with high jitter and latency. He clicks on the call path link to find the root cause.
3) Detailed bandwidth graphs from the NetFlow Plug-in shows an inter-site backup process is occupying most of the bandwidth during the performance degradation period
Outcome: Active scrutiny of VoIP QoS values across all call paths, along with respective bandwidth utilization trends helped the administrator pin down the root cause of the VoIP quality degradation. The backup process is scheduled for off-business hours and VoIP quality remains good henceforth.
VoIP infrastructure of an automobile company is suddenly facing serious quality degradation. A network administrator is assigned to investigate the situation and improve the VoIP performance.
1) By looking at the VoIP Overview dashboard in OpManager, the administrator identifies performance degradation (MOS of 1.5) on a particular VoIP site that has been the source of many user complaints. Interestingly, the site also figures in the top calls by jitter and packet loss but does not report high latency.
2) To investigate further, the administrator drills down to the snapshot page of the VoIP site. The voice packets show huge packet loss values and high jitter too. Bandwidth utilization graphs do not show high utilization thus ruling out any causes of degradation due to an over-burdened link.
3) On looking at the Class Based QoS (CBQoS) traffic pattern of the link, pre-policy traffic and post-policy traffic show a lot of dropped packets in the VoIP traffic class.
4) The administrator investigated these trends along with the configuration changes made on QoS policies in the routers. This revealed that recent changes made in QoS policy settings affected voice quality due to huge VoIP packet loss.
Outcome: The administrator allocates higher precedence to the VoIP traffic, which then restores healthy VoIP quality conditions.
Learn more about VoIP Monitoring in OpManager.