Your internet will go down. The question is not if, but what happens to your phone calls when it does. The answer depends on how much downtime your business can tolerate and how much you are willing to spend to prevent it.
This guide ranks five failover architectures from simplest to most resilient. Each tier is a real, deployable solution with specific cost and complexity tradeoffs. Pick the one that matches your actual business requirements — not every business needs tier 5, and tier 1 is dramatically better than nothing.
For the detailed explanation of what happens to VoIP during an internet outage, see What Happens to Your Phones When the Internet Goes Down. For the broader redundancy discussion, see Redundancy and Failover: When One Connection Isn't Enough.
Tier 1: Call forwarding to mobile
Cost: $0 beyond existing service Switchover time: 30-120 seconds What you keep: Inbound calls answered What you lose: IVR, call routing, extensions, voicemail, outbound calling from business numbers
This is the "something is better than nothing" tier. Configure your VoIP provider or hosted PBX to forward all inbound calls to a designated mobile phone when your phones lose registration. Most providers support this as a failover rule or "find me / follow me" setting.
When the internet goes down, your phones deregister. After a timeout (configurable, typically 30-120 seconds), the provider detects the deregistration and starts forwarding calls to the configured mobile number. Callers hear ringing instead of fast busy. Someone answers.
Setup: Log into your VoIP provider's portal. Find the failover or forwarding settings for your main number. Set a mobile number as the failover destination. Set the timeout to the shortest available (30-60 seconds). Test it by unplugging your router.
Limitations: Only works for inbound calls. Callers who dialed specific extensions or reached your IVR will get forwarded to a single mobile number with no routing. Outbound calls go from your personal mobile number, not your business number. Call recording, voicemail transcription, and other PBX features are unavailable.
This is better than dead phones. For many small businesses, it is sufficient.
Tier 2: Cellular backup connection (LTE/5G)
Cost: $30-100/month for cellular data plan + $100-300 for LTE failover device Switchover time: 10-60 seconds What you keep: Full phone system functionality What you lose: Call quality may degrade; bandwidth is limited; not suitable for high call volumes
Add a cellular modem or an LTE failover router to your network. When the primary internet connection fails, the router switches traffic to cellular. Your phones re-register over the cellular connection, and calls resume.
Setup: Many business routers (Ubiquiti, Fortinet, Cradlepoint, Peplink) support a USB LTE modem or a built-in cellular radio as a WAN failover. Configure the cellular connection as the secondary WAN with automatic failover. Set the failover detection to ping-based (more responsive than waiting for the interface to go down).
Considerations: Cellular bandwidth is shared and variable. A single LTE connection can typically support 5-15 simultaneous VoIP calls depending on conditions. Run our VoIP quality test over the cellular connection to verify quality before you need it in an emergency. Test during business hours, not at midnight when the tower is idle.
Cellular latency is higher than wired (30-80 ms typical), which is fine for VoIP. Jitter can be variable, especially on congested towers. The bandwidth calculator will tell you how many concurrent calls your cellular bandwidth can support.
Important: Some cellular plans deprioritize data after a threshold or during network congestion. Make sure your plan is suitable for business use.
Tier 3: Dual WAN with automatic failover
Cost: Second ISP connection ($50-500/month depending on type) + compatible router Switchover time: 5-30 seconds What you keep: Full phone system, full bandwidth What you lose: Brief interruption during switchover; existing calls may drop
Two independent internet connections from different providers, ideally using different last-mile technology (fiber primary, cable backup, or fiber primary, LTE backup). The router monitors both connections and switches automatically when the primary fails.
Setup: Connect both ISP connections to your dual-WAN router. Configure health checks (ping to a reliable external target every 5 seconds). Set the primary and secondary WAN interfaces. Configure QoS on both connections to prioritize VoIP.
The key word is "independent." Two connections from the same ISP using the same last-mile infrastructure do not give you real redundancy. If the fiber cut that took down your primary also serves your backup, both go down together. Use different providers, different technologies, or both.
The switchover interruption depends on your router and configuration. Some routers (Peplink, Fortinet with SD-WAN) can switch in under 5 seconds. Others take 15-30 seconds. Active calls during the switchover will likely drop because the phone's SIP registration changes IP addresses. Calls established after the switchover work normally.
For critical environments, pair dual WAN with the call forwarding from Tier 1 as an additional safety net. If both connections fail simultaneously (building power outage affecting both ISPs), calls still forward to mobile.
Tier 4: SD-WAN with active-active connections
Cost: $200-800/month for SD-WAN service + two ISP connections Switchover time: Near-zero (sub-second for some platforms) What you keep: Active calls may survive the failover What you lose: Higher cost and complexity
SD-WAN (Software-Defined Wide Area Network) goes beyond simple dual-WAN failover. It actively manages traffic across multiple connections simultaneously, making real-time decisions about which path to use for each packet.
For VoIP, the advantages over traditional dual-WAN:
Per-packet path selection. SD-WAN measures latency, jitter, and packet loss on each connection in real time. VoIP packets are automatically routed over the connection with the best quality, not just the one marked "primary."
Faster failover. Because SD-WAN is already monitoring both paths, it detects degradation before a complete outage. If the primary connection's jitter spikes above acceptable levels, traffic shifts to the backup before calls start sounding bad.
Active calls may survive. Some SD-WAN platforms (Peplink SpeedFusion, Fortinet SD-WAN) can maintain SIP sessions across a path change by managing the session state. This is not guaranteed, and it depends on the VoIP provider and configuration, but it is possible.
Quality-based routing. Even when both connections are working, SD-WAN routes VoIP over the better path. If your fiber has a brief quality issue, voice traffic moves to cable temporarily, then moves back when fiber recovers. This happens without manual intervention and often without users noticing.
Setup: Deploy an SD-WAN appliance (or configure SD-WAN features on a compatible router). Connect both ISP connections. Define application policies that prioritize VoIP traffic and set quality thresholds (maximum acceptable jitter, packet loss) that trigger path switching.
Tier 5: Geo-redundant SIP trunks with DNS failover
Cost: $500-2,000+/month (two trunk providers, potentially two sites) Switchover time: Near-zero for inbound; seconds for outbound What you keep: Everything, including active inbound call paths What you lose: Significant cost and operational complexity
This is the architecture for businesses where a missed call has serious consequences: medical practices, emergency services, financial trading desks, high-volume sales operations.
Inbound: Your phone numbers are configured with multiple SIP trunk providers. DNS SRV records point to both providers. If the primary trunk provider is unreachable, inbound calls route to the secondary. Alternatively, the number provider maintains a failover route that redirects to a backup trunk if the primary does not answer the INVITE within a timeout.
Outbound: Your PBX is configured with two trunk registrations. If the primary trunk fails to register or starts rejecting calls, the PBX falls over to the secondary trunk automatically.
Geographic redundancy: For the most critical deployments, the PBX itself is replicated across two sites (or hosted in two cloud regions). Active-passive or active-active, depending on the platform. If Site A goes down entirely — building fire, regional power grid failure — Site B picks up all traffic.
This is complex to implement and maintain. It requires coordination between multiple providers, careful DNS configuration, and regular testing. But it provides resilience against failures that lower tiers cannot handle: trunk provider outages, regional internet disruptions, and physical site loss.
Choosing the right tier
| Factor | Tier 1 | Tier 2 | Tier 3 | Tier 4 | Tier 5 | |--------|--------|--------|--------|--------|--------| | Monthly cost | $0 | $30-100 | $100-500 | $400-1,300 | $1,000+ | | Switchover time | 30-120s | 10-60s | 5-30s | <5s | Near-zero | | Active calls survive | No | Maybe | No | Maybe | Yes (inbound) | | Protects against ISP outage | Partial | Yes | Yes | Yes | Yes | | Protects against building outage | Yes | No | No | No | Yes | | Protects against trunk provider outage | No | No | No | No | Yes | | Complexity | Minimal | Low | Moderate | Moderate | High |
Most businesses land at Tier 2 or Tier 3. Cellular backup gives you real failover for a modest monthly cost. Dual WAN is better for businesses with consistently high call volumes that need full bandwidth on the backup path.
Tier 1 should be configured regardless of which higher tier you choose. It is free and it covers the worst case (complete site failure) that the network-level failover solutions do not address.
Test your failover
Failover that has never been tested is not failover. It is hope. Once a quarter:
- Disconnect the primary internet connection
- Time the failover — how long until phones re-register and calls work?
- Make inbound and outbound test calls through the backup path
- Run a VoIP quality test over the backup path to verify it can handle your call volume
- Reconnect the primary and verify everything fails back correctly
Document the results. If the failover takes longer than expected or calls do not work over the backup, fix it now — not during an actual outage.
For the detailed technical background on what happens during an outage, see What Happens to Your Phones When the Internet Goes Down. For connection redundancy fundamentals, see Redundancy and Failover: When One Connection Isn't Enough.
Frequently Asked Questions
What happens to VoIP phones when the internet goes down?+
If you have no failover, phones go dead immediately. Inbound calls get a fast busy or go to the carrier's default voicemail (if any). Outbound calls cannot be placed. How quickly service resumes depends entirely on when the internet comes back. With failover in place, calls can be rerouted to mobile phones, a backup connection, or a secondary site within seconds to minutes.
What is the simplest VoIP failover solution?+
Configure your VoIP provider to forward all calls to a mobile phone number if your phones go unregistered for more than 60 seconds. This costs nothing beyond your existing service and ensures inbound calls are answered. You lose IVR menus and call routing, but you do not lose the calls entirely.
Does SD-WAN help with VoIP failover?+
Yes. SD-WAN with dual WAN connections provides automatic failover at the network level. If the primary connection fails, traffic switches to the backup (often LTE/5G) within seconds. VoIP packets are prioritized across both connections. The phones do not lose registration and callers do not notice the switch. Use the bandwidth calculator to verify your backup connection can handle your concurrent call volume. This is the most common failover architecture for businesses that need more than basic forwarding.
How do I test my VoIP failover?+
Simulate an outage by disconnecting the primary internet connection. Time how long it takes for calls to start routing through the failover path. Make test calls through the backup path and verify quality. Run a VoIP quality test over the backup connection to ensure it can support your call volume. Test quarterly -- failover systems that are not tested regularly tend to fail when you actually need them.
Share
Want to know when we publish new articles? Sign up for updates