How to Reduce Call Drop Rates in Your VoIP Setup
Quick answer: To reduce call drop rates in a VoIP environment, work through four areas in order: network bandwidth and QoS, router and firewall configuration, SIP and PBX settings, and finally your SIP provider or ISP connection. In most cases, dropped calls trace back to one of two causes — congested network traffic competing with voice, or a firewall killing SIP sessions it mistakes for idle connections. Fix those two things first and most call drop problems disappear.
This guide walks through every layer of a VoIP setup systematically so you can identify and fix the exact cause of your dropped calls.
Reduce Call Drop Rates VoIP: The Main Causes
Before touching any settings, understand what actually causes VoIP calls to drop. Specifically, dropped calls in a VoIP environment come from six sources — and each one has a different fix.
1. Insufficient bandwidth Too many concurrent calls sharing a limited internet connection causes audio degradation first, then disconnections. In practice, each VoIP call needs roughly 80–100 kbps of upload and download bandwidth. Consequently, a 10Mbps connection struggling to support 80 simultaneous calls while staff also browse and download will drop calls under load.
2. Missing or misconfigured QoS Without QoS (Quality of Service), voice packets compete equally with file downloads and video streams. As a result, voice packets arrive late or out of sequence — which the receiving end interprets as a dropped call rather than late audio.
3. SIP ALG interference SIP ALG (Application Layer Gateway) is a feature built into most consumer and some business routers. It attempts to rewrite SIP packets to help them pass through NAT. However, it frequently corrupts SIP headers instead. Consequently, calls connect but drop after 30 seconds, 60 seconds, or at random intervals.
4. Session timeout from the firewall Firewalls track active connections and drop sessions that appear idle. In practice, VoIP signalling during a call generates less traffic than the firewall expects. Therefore, the firewall closes the connection mid-call — which causes an abrupt disconnection with no warning.
5. NAT traversal problems When your PBX sits behind a NAT router, the SIP server sometimes struggles to route audio back correctly. Specifically, the server sees your internal IP address rather than your public one — and sends audio packets to an address it cannot reach.
6. SIP provider or ISP issues Sometimes the problem sits upstream. Specifically, your SIP trunk provider experiences routing issues, or your ISP throttles VoIP traffic during peak hours. In addition, high latency between your office and the SIP server causes call setup failures and mid-call drops.
Network and Bandwidth Fixes
Start here before checking any router settings. Network capacity is the most common cause of dropped calls at scale.
Calculate your actual bandwidth requirement First, count your maximum concurrent call volume. Next, multiply that number by 100 kbps. Furthermore, add 20% headroom for traffic spikes. Therefore, a call center running 100 simultaneous calls needs at least 12 Mbps of dedicated upload and download bandwidth for voice — separate from general internet traffic.
Separate VoIP traffic from general internet use In practice, the most reliable way to protect voice traffic is to route it through a separate internet connection entirely. Specifically, a dedicated SIP trunk line or a separate broadband circuit for VoIP removes all bandwidth competition at the source. However, if a separate connection isn’t feasible, strict QoS rules on a shared connection achieve most of the same result.
Apply QoS rules that actually work QoS must mark voice packets at the highest priority and strictly limit how much bandwidth other traffic can consume when voice is active. Specifically, configure DSCP markings on your router and apply them to all SIP (UDP 5060) and RTP (UDP 10000–20000) traffic. For a complete walkthrough, see our guide on QoS configuration for VoIP.
Router and Firewall Configuration
Most call drop problems in small and medium-sized offices trace directly to router or firewall settings. Consequently, these fixes resolve the majority of SIP disconnection issues.
Disable SIP ALG immediately This is the single most impactful fix for random call drops in most environments. Specifically, find the SIP ALG or SIP Helper setting in your router and turn it off. Furthermore, some routers hide this setting — on MikroTik, disable it under IP > Firewall > Service Ports by removing the SIP entry. On most consumer routers, it appears under Advanced > NAT or SIP Settings.
Extend firewall session timeouts for VoIP By default, many firewalls time out UDP sessions after 30–180 seconds of apparent inactivity. In practice, SIP calls generate keepalive packets but less frequently than the firewall expects. Therefore, increase the UDP session timeout to at least 300 seconds — and specifically set the SIP session timeout to 3600 seconds or higher on business-grade firewalls.
Configure NAT rules correctly If your PBX sits on a private internal IP, it must advertise your public IP address in SIP headers rather than the internal one. Specifically, set the External IP or External Hostname field in your PBX’s SIP settings to your public IP address. Consequently, the SIP provider sends audio packets to the correct address and one-way or dropped audio disappears.
Open the correct firewall ports Confirm your firewall allows the following traffic inbound and outbound:
- UDP 5060 — SIP signalling
- UDP 5061 — SIP over TLS (if using encrypted SIP)
- UDP 10000–20000 — RTP audio streams (range varies by PBX)
Blocked RTP ports cause calls that connect but carry no audio — which often triggers a disconnection from the PBX after a silence timeout.
For guidance on firewall platforms that handle SIP correctly, see our comparison of Fortinet vs pfSense vs Sophos.
SIP and PBX Settings to Check
After fixing the network and firewall, check these PBX-level settings. In practice, they cause a specific subset of call drop patterns that network fixes alone won’t resolve.
Enable SIP keepalives on your PBX Most PBX platforms send SIP OPTIONS packets at regular intervals to keep the registration and session alive. Specifically, confirm this feature is enabled in your PBX’s SIP trunk settings. As a result, the SIP provider and your firewall both see regular traffic and keep the session open.
Set an appropriate session timer Session timers define how long a call can run before the PBX sends a re-INVITE to confirm both ends are still active. Specifically, if the re-INVITE fails — due to network instability or misconfiguration — the PBX drops the call. Therefore, set your session timer to a generous value (1800 seconds) and confirm your SIP provider supports session timers in the first place.
Check codec compatibility Mismatched codecs between your PBX and SIP provider cause call setup failures and mid-call renegotiation drops. Specifically, confirm your PBX offers G.711 (ulaw/alaw) as a primary codec — this is universally supported. Furthermore, if you use G.729 for bandwidth efficiency, confirm your SIP provider licences and supports it.
Review your PBX registration interval If your PBX re-registers with the SIP provider too infrequently, the provider expires the registration and drops active calls. In practice, set the registration interval to 60–120 seconds. Consequently, the SIP provider always sees an active registration and doesn’t expire your trunk mid-call.
Show Image
How to Reduce Call Drop Rates VoIP: Testing and Monitoring
Fixing settings blindly wastes time. Instead, test and measure before and after each change — so you know exactly what worked.
Run a VoIP quality test to your SIP provider Tools like PingPlotter or a dedicated VoIP test tool measure latency, jitter, and packet loss between your office and the SIP server. Specifically, run the test during peak calling hours — not at 3am when the network is idle. Furthermore, results above 150ms latency, 30ms jitter, or 1% packet loss explain most call drop patterns without any further investigation needed.
Check PBX call logs for the exact drop reason Your PBX logs the SIP reason code when a call drops. Specifically, a 408 code means a timeout — which points to session timer or firewall issues. A 503 means the SIP provider rejected the call — which points to registration or capacity issues. As a result, reading the log codes cuts diagnosis time significantly compared to guessing.
Monitor call quality continuously Set up ongoing monitoring so you catch degradation before it reaches call-drop severity. In addition, monitoring gives you before-and-after data when you make configuration changes — so you can confirm a fix actually worked rather than assuming it did. Our guide on PRTG vs Zabbix covers tools that monitor VoIP metrics continuously alongside your broader network performance.
Test after every configuration change Make one change at a time. Specifically, test thoroughly after each change before moving to the next. Consequently, you know exactly which fix resolved the problem — rather than making five changes simultaneously and not knowing which one worked.
When the Problem Is Your ISP or SIP Provider
Sometimes every local setting is correct and calls still drop. In that case, the problem sits upstream.
Signs the ISP is the issue:
- Calls drop at regular times that match peak internet usage hours
- VoIP tests show good results at off-peak times but degrade during business hours
- Other internet-dependent services also slow down when calls drop
- Your ISP uses CGNAT, which can interfere with SIP registration and audio routing
Signs the SIP provider is the issue:
- Drops happen across different office locations using the same SIP trunk
- Call logs show 503 or 480 SIP error codes consistently
- The provider’s status page shows intermittent incidents
- Switching to a backup SIP provider resolves the drops immediately
In both cases, document the drop times, SIP error codes, and VoIP test results before contacting support. Specifically, providers respond much faster to a report with timestamps and error codes than to a general complaint about bad call quality.
For guidance on SIP trunk selection in Pakistan, see our guide on SIP trunking Pakistan. For call center infrastructure that supports high call volumes reliably, see our post on VPS vs dedicated server hosting.
Not getting anywhere with your current setup? Get in touch with our team — we diagnose and fix VoIP call quality issues for businesses and call centers across Pakistan regularly.
Show Image
Frequently Asked Questions
Why do VoIP calls keep dropping? The most common causes are missing QoS configuration, SIP ALG interference from the router, firewall session timeouts killing active calls, insufficient bandwidth for concurrent call volume, and NAT traversal misconfigurations between the PBX and SIP provider.
How do I stop calls from dropping after 30 or 60 seconds? This specific pattern almost always points to SIP ALG on the router or a firewall session timeout. First, disable SIP ALG on your router. Next, increase the UDP session timeout on your firewall to at least 300 seconds. Specifically, set the SIP session timeout to 3600 seconds if your firewall has a separate SIP setting.
Does QoS fix call drop problems? QoS fixes call drops caused by network congestion — where voice traffic competes with other data for bandwidth. However, it doesn’t fix drops caused by firewall timeouts, SIP ALG, NAT issues, or provider-side problems. Therefore, always diagnose the cause before assuming QoS is the solution.
How much bandwidth does each VoIP call need? Each simultaneous VoIP call needs approximately 80–100 kbps of upload and download bandwidth, depending on the codec used. Consequently, plan for at least 100 kbps per concurrent call plus 20% headroom for traffic spikes.
How do I know if my SIP provider is causing call drops? Check your PBX call logs for SIP error codes — 503 and 480 responses indicate provider-side rejection. In addition, test whether drops happen on a backup SIP provider. If the backup performs reliably, the primary provider is the source of the problem.
Started Today
Want to set up a professional call center?
Contact E Tech Solvers for complete solutions.