Hands-on tutorial
Tutorials · Troubleshooting
How to Troubleshoot VoIP Call Quality: Choppy Audio, One-Way Audio and Dropped Calls
Trace bad calls to the real cause, from jitter, loss and missing QoS to NAT and SIP ALG problems, and fix them on the switch, gateway or phone system.
Before you start
- Access to the IP PBX or phone system logs
- Access to switches and the internet gateway
- A test phone and the ability to capture traffic
Step by step
Classify the symptom
Choppy or robotic audio points to jitter or loss. One-way or no audio points to NAT or firewall problems. Calls dropping after 30 seconds or 15 minutes point to SIP timers or NAT timeouts.
Check the local network
Phones should be on a voice VLAN with QoS: DSCP EF for voice and CS3 for signalling, trusted on switch ports and queued with priority.
show mls qos interface gi1/0/10 show interfaces gi1/0/10 counters errors
Check the internet link
Measure latency, jitter and loss to the SIP provider during busy hours. Voice needs jitter under about 30 ms and loss under 1%. Upload congestion is the most common cause.
Shape the upload
Set the gateway's upload limit slightly below the real line speed and give voice priority, so voice packets do not wait behind uploads.
Fix NAT and SIP ALG
Disable SIP ALG on the gateway unless your provider requires it. Configure the PBX with its public address and the RTP port range, and forward or allow those ports only to the PBX.
Capture a bad call
Capture SIP and RTP on the PBX or a mirror port. Wireshark's VoIP analysis shows jitter, loss and which direction lost audio.
tcpdump -i eth0 -w call.pcap port 5060 or portrange 10000-20000
Commands are generic, industry-standard examples. Exact syntax and menu names vary by model and firmware; check your device's manual on the Documentation page.
Pro tips
- Wi-Fi calling needs good roaming and voice-friendly settings.
- Keep phone and PBX firmware current.
- Record the time and number of bad calls; it makes logs much easier to match.
FAQ
Frequently asked questions
Why do calls drop after exactly 30 seconds?
Usually the ACK or re-INVITE does not reach the phone because of NAT or SIP ALG. Fix the NAT settings on the PBX and gateway.
Does VoIP need a lot of bandwidth?
No, about 100 kbit/s per call with G.711, less with other codecs. Quality depends on delay and loss, not bandwidth.
Keep learning
Related guides
Voice VLAN and QoS for IP phones
Read more →Monitor WAN latency and loss
Read more →Provision SIP IP phones
Read more →How to Troubleshoot Network Problems With Ping, Traceroute and MTR
Find where a connection breaks or slows down in minutes. Use ping for reachability and loss, traceroute for the path, and MTR to see loss and latency on every hop at once.
Read more →How to Capture and Read Network Traffic With Wireshark and tcpdump
When logs are not enough, look at the packets. Capture traffic with tcpdump or Wireshark, filter it down to the problem, and spot retransmissions, DNS failures, DHCP issues and TLS errors.
Read more →How to Test Network Speed Between Two Points With iperf3
Internet speed tests do not tell you how fast your LAN, Wi-Fi or site-to-site link really is. iperf3 measures throughput, loss and jitter between two machines you control.
Read more →Stuck on a step?
Ask Navijin technical support or an authorised partner for help with your configuration.