// article
How to Troubleshoot Common VoIP Call Quality Issues
A step-by-step guide to diagnosing and fixing VoIP call quality problems: covering bandwidth testing, QoS configuration, SIP ALG, hardware checks, and network optimization.
How to Troubleshoot Common VoIP Call Quality Issues
You’re on a call with a client and your voice sounds like it’s coming through a tin can. Or worse, you can hear them fine, but they can’t hear you at all. Maybe calls drop mid-conversation, or there’s a half-second delay that makes every exchange feel like a satellite interview.
These problems aren’t random. VoIP call quality issues almost always trace back to one of three things: your internet connection, your network configuration, or your equipment. Fix those, and VoIP delivers call quality that matches or beats traditional phone lines.
Here’s how to diagnose and fix the most common issues, step by step.
Identify What You’re Hearing
Before you start changing settings, name the symptom. Each one points to a different root cause.
| Symptom | Likely Cause |
|---|---|
| Choppy or robotic audio | Packet loss or jitter |
| Echo on calls | Hardware issue or network latency |
| One-way audio (you hear them, they don’t hear you) | Firewall/NAT issue or SIP ALG |
| Delay between speaking and being heard | High latency |
| Calls dropping mid-conversation | Bandwidth saturation or connection instability |
| Garbled or distorted voices | Jitter or codec mismatch |
Knowing the symptom narrows the troubleshooting path and prevents you from changing things that aren’t broken.
Step 1: Test Your Internet Connection
VoIP requires stable bandwidth, low latency, and minimal packet loss. Run a speed test during peak office hours, not when the office is empty.
What to check:
- Download and upload speed: Each concurrent call needs roughly 100 Kbps in each direction
- Latency (ping): Should be under 150ms for smooth conversation
- Jitter: Should be under 30ms; high jitter causes choppy audio
- Packet loss: Should be under 1%; even 2% is audible
If your connection falls short on any of these metrics, upgrading to business internet services designed for voice traffic is the most effective single fix.
Step 2: Configure QoS on Your Router
QoS (Quality of Service) tells your router to prioritize voice traffic over everything else. Without it, a large file download or video stream can starve your VoIP calls of bandwidth.
How to set it up:
- Log into your router’s admin panel
- Find QoS or Traffic Management settings
- Create a rule that gives highest priority to VoIP traffic (typically SIP and RTP protocols, or the IP addresses of your VoIP phones)
- Save and reboot the router
This single configuration change fixes the majority of call quality issues in offices where VoIP shares bandwidth with other applications.
Step 3: Disable SIP ALG
SIP ALG (Session Initiation Protocol Application Layer Gateway) is a router feature that modifies VoIP traffic as it passes through. In theory, it helps. In practice, it causes one-way audio, registration failures, and dropped calls more often than it helps anything.
How to disable it:
- Access your router’s admin panel
- Find SIP ALG under firewall, NAT, or advanced settings
- Turn it off
- Save changes and reboot
Most VoIP providers explicitly recommend disabling SIP ALG. If you’re experiencing one-way audio or registration problems, this should be one of the first things you check.
Step 4: Restart Your Network Equipment
A full restart clears cached data, resolves temporary configuration conflicts, and re-establishes connections.
Restart in this order:
- Power off your modem
- Power off your router
- Power off VoIP phones and adapters
- Wait 30 seconds
- Power on the modem first and wait for it to fully connect
- Power on the router
- Power on VoIP devices
Test a call after everything’s back online. If the issue was a temporary glitch in your network stack, a power cycle often resolves it immediately.
Step 5: Check Your Hardware and Cables
Software configuration gets most of the attention, but physical equipment causes more problems than people realize.
What to inspect:
- Ethernet cables: Look for frayed cables, loose connections, and cables that have been bent sharply. Replace any cable you’re not sure about; they’re cheap.
- VoIP phones: Test with a different phone to rule out a hardware defect. Check that firmware is current.
- Headsets: Wireless headsets with low battery produce poor audio. Wired headsets with damaged cables cause intermittent sound issues.
- Power supply: VoIP phones and routers on power strips without surge protection are vulnerable to electrical interference.
- Network switches: Ensure switches support QoS and are rated for your traffic volume. Consumer-grade switches can become bottlenecks.
If you’re running older equipment, business telephone services that include modern IP phones ensure your hardware isn’t the weak link.
Step 6: Update Firmware and Software
Outdated firmware on routers, switches, and VoIP phones can cause compatibility issues, security vulnerabilities, and degraded performance.
Update checklist:
- Router firmware
- Network switch firmware
- VoIP phone firmware
- Softphone application (desktop and mobile)
- Any VoIP adapters connecting analog phones
Many VoIP call quality problems disappear after firmware updates because providers regularly fix bugs and optimize audio codec performance.
Step 7: Separate VoIP Traffic With VLANs
For offices with more than 15-20 people, putting VoIP devices on their own VLAN (Virtual LAN) isolates voice traffic from data traffic. This prevents bandwidth-heavy applications on employee computers from affecting call quality.
How VLANs help:
- Voice packets travel on a dedicated network segment without competing with file transfers, streaming, or web browsing
- QoS settings apply more effectively when voice traffic is isolated
- Network issues in the data VLAN don’t cascade to phone service
This requires a managed switch that supports VLAN configuration, a worthwhile investment for any office where call quality directly affects business operations.
Step 8: Verify Phone Registration
If calls fail to connect or you experience one-way audio on specific phones, the device may not be properly registered with your VoIP provider.
How to check:
- Look at your VoIP phone’s display or settings screen for a “registered” or “online” status
- If it shows “unregistered” or “offline,” re-enter your SIP credentials
- Restart the phone after re-registering
- Contact your provider if registration continues to fail; it may be a firewall or port issue
Step 9: Test the Network Path
If local troubleshooting hasn’t resolved the issue, the problem may be between your network and your VoIP provider’s servers.
Diagnostic tools:
- Ping test: Ping your VoIP provider’s server address to check for packet loss and latency
- Traceroute: Identifies which hop in the network path is introducing delay or packet loss
- Continuous monitoring: Run a ping test over several hours to check for intermittent issues that don’t show up in a quick test
If the problem is on your ISP’s network or between your ISP and the VoIP provider, contact your internet provider with the traceroute data. Tools like 1stConnect include monitoring features that help identify where in the network chain problems occur.
Preventing Future Issues
Troubleshooting solves today’s problem. Prevention keeps it from coming back.
- Schedule quarterly network health checks: Test bandwidth, latency, and packet loss proactively
- Keep all firmware current: Set reminders to check for updates monthly
- Monitor bandwidth usage: Watch for patterns where call quality dips during specific times (indicating bandwidth saturation)
- Document changes: Keep a log of network configuration changes so you can quickly revert if something breaks
- Train staff on basics: Teach employees to avoid starting large downloads during important calls and to report call quality issues immediately
FAQs
Why do my VoIP calls sound robotic?
Robotic or choppy audio is caused by packet loss or jitter: voice data packets arriving out of order or not arriving at all. Check your internet connection for packet loss (should be under 1%) and jitter (should be under 30ms). Enable QoS on your router to prioritize voice traffic.
Why can the other person not hear me on VoIP calls?
One-way audio is typically caused by SIP ALG on your router (disable it), a firewall blocking return audio packets, or a NAT configuration issue. Check SIP ALG first; it’s the most common cause.
How much bandwidth does VoIP actually need?
Each concurrent call uses roughly 100 Kbps in both directions. An office with 10 simultaneous calls needs about 1 Mbps dedicated to VoIP. The bigger concern is bandwidth stability; consistent speed matters more than peak speed.
Should I use wired or wireless connections for VoIP phones?
Wired (Ethernet) whenever possible. Wi-Fi introduces variability in latency and packet loss that can degrade call quality, especially in offices with many wireless devices. If Wi-Fi is necessary, prioritize the 5 GHz band and ensure strong signal coverage at the phone’s location.
When should I call my VoIP provider instead of troubleshooting myself?
Contact your provider when: you’ve completed the steps above and the issue persists, the problem is specific to certain destinations (indicating a routing issue on the provider’s side), or traceroute data shows the problem is beyond your local network.
Still experiencing call quality issues? Start with reliable business internet as your foundation, pair it with business telephone services from a provider that supports your troubleshooting, and keep your team connected with 1stConnect.