Setting Up VoIP for Success
A common stumbling block in monitoring VoIP occurs when the network team misconfigures or fails to define the VoIP setup process for their monitoring system. The results can be serious when you investigate a call and it doesn’t appear, it has been misidentified, or mistakenly combined with another call. Here are five steps to ensure your VoIP monitoring solution is set up for success.
Identify call components
Depending upon the VoIP vendor and system, different components may be involved in the call. For example, in Cisco’s® systems, communications occur between phones and the call manager. Avaya® uses multiple components including the phone, control processor (C-LAN), and media processor (MedPro). Before configuration, map out all components involved in the call.
Recognize the call
The first step in configuration is to specify how the monitoring system recognizes a call has been initiated. The option you choose will depend upon the probe's ability to view the call setup packets. Observer offers flexibility dealing with this issue. New calls can either be identified from setup packets or via RTP data packets. Calls can be closed if no packets are identified for a specified time period.
Depending on how calls are communicated and the data involved, the user also needs to specify the traffic type and whether calls occur concurrently. For instance, Avaya systems use MedPro to send RTP data to other MedPro systems and to phones. Multiple calls can be sent and received at the same time.
Program call components
Components involved in the call should be identified and configured. Within Observer® under the Device IP Addresses tab, identify the device IP and type. This is critical for dictating how things are measured and displayed.
Monitor encrypted traffic
If SIP data is encrypted, it can be nearly impossible to identify a call. Depending on your monitoring solutions, you may have the ability to track encrypted traffic. Observer decrypts SIP traffic and provides quality metrics on the fly once it has the appropriate security certificate.
Establish caller ID
The location of caller ID info varies by system and even components. To be sure the caller is properly identified, your network analyzer needs the location of ID details. In Observer, under the Caller ID Determination tab, users can establish a hierarchical set of rules to locate the sources of ID text.