Troubleshooting call quality issues
When using voice over IP, there are many considerations which can affect the quality of phone calls, and identifying the source of the issue can sometimes be difficult. This topic is designed to describe the different types of call quality issues, the general causes, and a likely solution to each type of issue.
One-way, or No Audio
Improper NATNetwork address translation - A method that remaps IP addresses by changing network address information. settings, or improper handling of SIPSession Initiation Protocol - A communication protocol used for voice and video calls in Internet telephony or private IP telephone systems./RTP by the firewall.
Avoid NAT, Bypass the firewall by connecting Kerio Operator directly to the WAN, and attaching a second network interface to the local network. Otherwise, verify the NAT settings in Kerio Operator and the connected SIP device. Configuration details are available in KB topic Configuring NAT. Also check the kerio forums or other resources for known SIP handling issues with the brand of firewall in front of Kerio Operator. The firewall should be configured to allow TCP/UDPUser Datagram Protocol - Ensures packet transmission. port 5060 and 5061, and UDP ports 10000 ~ 20000
Garbled, or incomprehensible voice transmission.
Identify and remove the bad Codec from the selected codecs in the call route.
Troubleshooting tip: During a call, review Status > Calls and check the used Codec. Compare it to calls that don't have the issue.
Choppy voice quality. Some words or parts of the conversation are lost or cut off.
- Insufficient or jittery Internet bandwidth.
- Local networking issue (bad cable, overloaded switch, bad NIC, overloaded WiFi)
- High CPU usage or insufficient hardware resources
- Set GSM as the only selected Codec on the call route. Research options for allocating more bandwidth or incorporating QoSQuality of service - Network's ability to obtain maximum bandwidth and manage other network performance elements like latency, error rate and uptime..
- Update firmware of the phone, replace the cable to the phone, change the Codec of the extension, replace the phone.
- Upgrade hardware to faster storage device (e.g. SSD) or add RAM
Troubleshooting tips: Enable extension 81 for the echo test. Dial from various locations and phones to isolate the conditions under which the choppiness occurs. From a browser on that network, go to pingtest.net and check the line quality. Check the status > system health to make sure the CPU/Memory is not overloaded. Check settings for call recording and logging to ensure reduced File I/O.
Capturing the network communication (packet capture or packet dump):
If the previously mentioned steps were not helpful, it may be necessary to capture the network communication for analysis. To do this, navigate to Configuration > Network. Select the network interface which is linked to the network where the issue is observed. Click the 'Packet Sniffer...' button to the right of the interfaces dialog. Start the capture, then attempt to reproduce the problem. Once the issue has been observed, stop the capture and download the capture file. If you have an open case with technical support, they may request this file.