You’re explaining a proposal to a client and the call cuts out mid-sentence. You dial back, apologize, pick up where you left off—and it drops again three minutes later. By the third callback, the client suggests “maybe just send me an email.”
Dropped calls are the most visible VoIP problem because they’re impossible to ignore. Unlike gradual audio degradation that people tolerate, a disconnected call stops the conversation entirely. And every drop erodes confidence—your client’s confidence in your business, and your team’s confidence in the phone system.
The good news: call drops have identifiable causes, and most are fixable without replacing your entire system. Here’s how to find and fix them systematically.
VoIP converts voice into data packets and streams them over your internet connection in real time. Unlike downloading a file (where a brief interruption just slows things down), a voice call requires continuous, uninterrupted data flow. When that flow breaks—even for a fraction of a second—the call drops.
The most common causes:
The most frequent culprit. VoIP requires consistent connectivity, not just fast speeds. Three metrics determine whether your connection can maintain a call:
When multiple devices compete for bandwidth—file uploads, video streaming, cloud backups, software updates—VoIP traffic gets squeezed. Without QoS configuration telling your router to prioritize voice packets, a large file upload can starve a phone call of the bandwidth it needs.
Firewalls blocking SIP ports (typically 5060/5061) or RTP ports terminate calls mid-conversation. NAT (Network Address Translation) issues cause one-way audio or dropped connections when the router incorrectly handles VoIP traffic.
Loose Ethernet cables, failing power adapters, overheating routers, and aging VoIP phones cause intermittent disconnections that are difficult to diagnose because they don’t follow predictable patterns.
Outdated firmware, incorrect SIP settings, incompatible codecs, or expired registrations can all cause calls to drop. These are especially common after a firmware update that changes default settings.
Run a VoIP-specific speed test during business hours when your network is under real load. Check all four metrics:
| Metric | Good Quality Threshold | Degradation vs. Drop |
|---|---|---|
| Upload speed | 100 Kbps per concurrent call | Calls fail to connect or drop under load |
| Latency | Under 150ms one-way | 150-400ms: audio delays and quality issues. 400ms+: call drops |
| Jitter | Under 30ms | 30-50ms: choppy audio. 50ms+: severe distortion, potential drops |
| Packet loss | Under 1% | 1-5%: choppy audio, missing words. 5%+: call drops |
If any metric fails during peak hours, your connection is the problem—even if it tests fine early in the morning.
Power-cycle your modem, router, and switches in sequence: modem first, wait 30 seconds, then router, then switches. This clears cached data, refreshes network connections, and resolves many temporary issues. If call drops stop after a restart but return within days, the equipment may need firmware updates or replacement.
Inspect every Ethernet cable between your VoIP phones, switches, and router. A loose or damaged cable causes intermittent drops that look like network issues. Push every connector until it clicks. Replace any cable you’re not confident in—a $3 cable eliminates hours of troubleshooting.
Log into your router and enable Quality of Service. Create rules that prioritize SIP and RTP traffic above all other network activity. This ensures voice packets go first even when someone is uploading a large file or streaming video.
Without QoS, your router treats a phone call the same as a Netflix stream. With QoS, calls always get through.
Verify that your firewall allows traffic on SIP ports (5060/5061) and your RTP port range. Check that SIP ALG is disabled on your router—it interferes with VoIP connections more often than it helps.
If you’re behind a NAT, ensure your VoIP phones or PBX have the correct external IP configured for NAT traversal. Incorrect NAT settings are a leading cause of one-way audio and dropped calls.
Check for updates on your VoIP phones, softphone applications, router, and switches. Outdated firmware can contain bugs that cause call drops, and codec incompatibilities between old and new software create connection failures.
Apply updates during off-hours and test a few devices before rolling out broadly.
If call drops persist after working through the basics:
Dedicate bandwidth for VoIP. Set bandwidth limits on non-critical applications or create a separate internet connection for voice traffic. For larger offices, a dedicated VoIP connection eliminates competition entirely.
Replace aging hardware. Routers and switches older than 4-5 years may not handle modern VoIP traffic volumes. VoIP phones with outdated processors struggle with current codecs. Replace equipment that’s past its effective lifespan.
Consider your internet connection type. Cable internet’s shared bandwidth creates congestion during peak hours. DSL’s distance sensitivity causes instability. Business internet services with symmetrical fiber and performance SLAs eliminate the connection-level causes of call drops.
Evaluate your VoIP provider. If your provider’s infrastructure is overloaded or poorly maintained, the problem may be on their end. A traceroute showing high latency at your provider’s servers—rather than at your ISP—indicates it’s time to explore better business telephone services.
Monitor continuously. Set up network monitoring that tracks latency, jitter, and packet loss in real time and alerts you when thresholds are exceeded. Catching degradation before it causes drops prevents the problem entirely.
Schedule bandwidth-heavy activities off-hours. Large file uploads, cloud backups, and software updates competing with VoIP during business hours is the most preventable cause of call drops.
Use wired connections. Every VoIP phone and softphone computer should connect via Ethernet. Wi-Fi adds variable latency and interference that wired connections don’t have.
Test after changes. Any network change—new device, firmware update, ISP modification, new employee—can affect VoIP. Test call quality after every change rather than waiting for complaints.
Build redundancy. A backup internet connection with automatic failover keeps calls flowing when your primary connection has issues. 1stConnect provides unified communication tools with built-in redundancy for businesses that can’t afford dropped calls.
Predictable timing points to network congestion. Something on your network runs at that time—a scheduled backup, a team’s daily video meeting, or peak-hour ISP congestion. Monitor bandwidth usage during the drop window to identify the competing traffic, then either reschedule it or configure QoS to protect VoIP.
Yes. Wi-Fi introduces variable latency, is susceptible to interference from other devices and networks, and can drop connections when signal strength fluctuates. For any device making business calls, wired Ethernet is significantly more reliable.
Run a traceroute to your VoIP provider’s server. If high latency or packet loss appears at hops within your network or ISP, the problem is on your side. If the issue appears at hops belonging to your VoIP provider, contact their support with the traceroute data.
Speed matters less than stability. A 10 Mbps connection with consistent latency and zero packet loss supports VoIP better than a 200 Mbps connection with intermittent congestion. That said, ensure at least 100 Kbps upload per concurrent call with 30% headroom for other traffic.
For businesses with more than 20-30 employees or heavy data usage alongside VoIP, a dedicated connection for voice traffic eliminates bandwidth competition entirely. It’s the most reliable way to prevent congestion-related call drops.
Stop losing calls to preventable problems. Start with reliable business internet that delivers consistent performance, pair it with business telephone services built for call reliability, and keep your team connected with 1stConnect.