Picture this: you pick up the phone Monday morning, dial a client, and get silence. No dial tone. No error message. Just nothing. Or worse — the call connects but you sound like a robot from a 1990s sci-fi movie, cutting in and out while your client asks “can you hear me?” for the fourth time.
Your VoIP phone not working is frustrating, but 90% of VoIP issues come from the same handful of causes. Here are 9 fixes in order of likelihood — start at the top and work down.
Fix 1: Power Cycle Everything (Yes, Really)
The IT cliché exists because it works. Most VoIP registration failures clear themselves after a reboot.
Order matters:
- Unplug your VoIP phone (or close the softphone app)
- Unplug your router — wait 30 seconds
- Unplug your modem — wait 30 seconds
- Plug modem back in — wait for all lights to stabilize (60-90 seconds)
- Plug router back in — wait for it to fully boot (60-90 seconds)
- Plug phone back in (or reopen the app)
Don’t skip the wait times. Half the time people “power cycle” by unplugging for 5 seconds, which doesn’t clear the device’s network state.
This alone fixes about 40% of VoIP issues we see in support tickets.
Fix 2: Check Your Internet Connection
VoIP runs over the internet. No internet = no calls. Obvious, but worth verifying.
Open a browser on the same network as your phone and load any website. If websites work, your internet is up. If they don’t — the problem isn’t VoIP, it’s your ISP.
If websites load but VoIP still doesn’t work, run a VoIP-specific speed test. Regular speed tests only measure bandwidth. VoIP needs low jitter (under 30ms) and low packet loss (under 1%). A connection with 100 Mbps download but 80ms jitter will produce terrible call quality.
For the technical details on what jitter, packet loss, and codec selection actually mean for call quality, we’ve got a deep guide.
Fix 3: Disable SIP ALG on Your Router
This is the single most common cause of VoIP problems that people don’t know about. It deserves its own section.
SIP ALG (Application Layer Gateway) is a router feature that tries to “help” VoIP traffic by modifying SIP packets as they pass through. In theory, it solves NAT traversal issues. In practice, it mangles packets and causes:
- One-way audio (you hear them, they can’t hear you)
- Calls dropping after 30-60 seconds
- Registration failures
- Echo and audio artifacts
It’s enabled by default on most consumer routers — Netgear, Linksys, TP-Link, ASUS, most ISP-provided routers.
How to disable it:
- Log into your router (usually 192.168.1.1 or 192.168.0.1)
- Look under Advanced → NAT → SIP ALG (location varies by manufacturer)
- Uncheck / disable SIP ALG
- Save and reboot the router
Every VoIP provider recommends this. Nextiva, RingCentral, Dialpad, VestaCall — we all tell customers the same thing. Turn off SIP ALG.
Fix 4: Check Your Cables and Hardware
Physical layer problems are boring but common:
- Ethernet cable loose or damaged — swap with a known working cable
- Phone plugged into wrong port — most IP phones have a LAN port and a PC passthrough port. The internet cable goes into the LAN/SW port
- PoE switch not providing power — if your phone is powered over ethernet and the switch port died, the phone won’t turn on. Try a different port
- Headset issue — before assuming it’s VoIP, test with the phone’s built-in speaker. If the speaker works fine, your headset is the problem
Fix 5: Configure QoS (Quality of Service)
Your router treats all internet traffic equally by default. Netflix, file downloads, and VoIP calls all compete for the same bandwidth. During peak usage, VoIP loses because it’s the most sensitive to delays.
QoS tells your router to prioritize voice traffic. Setup varies by router, but the general steps:
- Log into router admin panel
- Find QoS settings (usually under Advanced or Traffic Management)
- Enable QoS
- Set VoIP traffic as highest priority — either by device MAC address or by DSCP marking (set to EF/46 for voice)
- Save and reboot
On a network with 10+ users and heavy internet usage, QoS alone can fix choppy audio and dropped calls.
Fix 6: Check Firewall and Port Settings
Your firewall might be blocking VoIP traffic. VoIP uses two types of traffic:
- SIP (signaling): UDP port 5060 or 5061 (TLS). This sets up and tears down calls
- RTP (media): UDP ports 10000-20000 (varies by provider). This carries the actual voice audio
If SIP ports are blocked, calls won’t connect at all. If RTP ports are blocked, calls connect but you get no audio or one-way audio.
Check your firewall rules and make sure these port ranges are open for outbound UDP traffic. VestaCall uses standard SIP/RTP ports — check our help docs for exact ranges.
Also check: are you on a corporate network with strict firewall rules? VPN? Hotel WiFi with port blocking? All of these can kill VoIP. Try connecting through your phone’s cellular hotspot to test — if VoIP works over cellular but not WiFi, the network firewall is the problem.
Fix 7: Update Phone Firmware
IP desk phones (Yealink, Polycom, Cisco) receive firmware updates from the manufacturer. Outdated firmware can cause:
- Registration failures with newer server configurations
- TLS handshake errors (if the phone’s certificate store is outdated)
- Audio codec incompatibilities
- Random reboots during calls
Check your phone manufacturer’s support site for the latest firmware. Most phones can update through the admin web interface (type the phone’s IP address into a browser).
VestaCall’s provisioning system auto-updates firmware for supported phone models — one less thing to manage.
Fix 8: Check for Network Congestion
VoIP needs consistent, low-latency bandwidth. If your office internet is shared with:
- Video conferencing (50+ Mbps per meeting)
- Cloud backups running during business hours
- Employees streaming music/video
- Large file uploads/downloads
…your VoIP calls will suffer even if you have plenty of total bandwidth.
Solutions:
- Schedule backups for off-hours
- Implement QoS (Fix 5 above)
- Put phones on a separate VLAN — isolates voice traffic from everything else
- Upgrade your internet plan — if you have fewer than 25 Mbps upload, it might genuinely be too little for your office
- Use wired connections for phones — WiFi adds jitter. Ethernet doesn’t.
Fix 9: Contact Your Provider
If you’ve gone through fixes 1-8 and the problem persists — it’s probably on the provider’s side. Possible causes:
- Server-side outage or degradation
- Routing issue affecting specific number ranges
- SIP trunk configuration error
- DNS resolution failure
Your provider’s support team can run server-side diagnostics (call quality traces, SIP ladder diagrams, packet captures) that aren’t possible from your end.
VestaCall’s 24/7 support is available on all plans — phone and live chat. We can see your call quality metrics in real-time and identify whether the issue is on your network, our network, or somewhere in between.
VestaCall’s Approach to Reliability
One thing worth mentioning: most VoIP problems come from the network between your office and the provider. VestaCall can’t fix your router’s SIP ALG or your ISP’s jitter — but we’ve built resilience into the platform to handle imperfect networks.
Automatic mobile failover — if your office internet drops, VestaCall’s mobile app automatically switches to cellular data. Calls keep flowing. No manual intervention. This is why our measured uptime is 99.9993% even when customers’ internet isn’t.
Adaptive codecs — VestaCall dynamically adjusts codec bitrate based on network conditions. If bandwidth drops, the codec adapts before you hear degradation.
15 global data centers — calls route through the nearest data center. If one goes down, traffic fails over automatically. On Black Friday 2025, the platform handled 2.1 million concurrent calls without degradation.
For a deeper look at how codecs and network conditions affect call quality, our VoIP call quality guide covers the technical details. And if you’re evaluating whether VoIP is reliable enough for your business, the VoIP vs landline comparison puts it in perspective.
If you’re still having issues after all 9 fixes — or if you’re troubleshooting a provider that doesn’t give you these resilience features — it might be time to evaluate alternatives. A VoIP security audit is also worth running to make sure your network configuration isn’t creating vulnerabilities alongside call quality issues.
What’s the VoIP issue you’re dealing with right now — and which fix did you try first?
