The direction of a call leg matters when you are troubleshooting a performance issue. Reported performance is different for each direction of a call, although often the differences are slight. The route that a call takes through your network can be asymmetric, for example, with a longer route, and more delay, in one direction between the conversing parties.
Therefore, consider bi-directional calls and call legs as you interpret the data in reports. And understand which directions are presented in each report.
For example, the Performance by All report contains data from all observed call legs traveling in sending and receiving directions: inbound to the IP network and outbound to the PSTN. When you drill down for more information, the next view usually shows call performance data by Location.
The perspective on the data changes with the Performance by Location report, which presents the call quality data for that Location. No matter which party initiates the call, the call quality perspective is that of the listener. Call quality metrics are from the call legs traveling toward that listener. Call setup metrics are taken only from the calls that originated at that Location.
Monitoring reports generally break out performance for a Location using data from the receiving direction. After you drill down by Location or by media device, the sending Location is also shown, to help you distinguish the performance of calls between pairs of Locations or media devices.
|
Copyright © 2012 CA.
All rights reserved.
|
|