VoIP.infoThe independent guide to business communications.
VoIP.info Guide

VoIP network failover

Define whether you need new-call recovery, incoming diversion or active-call continuity.

Reviewed 2026-10-20Foundational

Name the desired outcome

A router switching connections may restore new calls without preserving an active call's addresses and state. Incoming carrier diversion is another separate capability. Write an acceptance criterion for each instead of using the single word failover.

Redundancy needs separate failure paths
A PBX uses a primary provider path and an alternate provider path. Shared PBX, power and internet dependencies remain unless the design also separates them.

New-call recovery and active-call survival are different tests. Inbound number failover needs a provider-side routing plan.

Map shared dependencies

List power, circuits, routers, DNS, PBX and carrier delivery. Two trunks on the same failed PBX do not remove that dependency. Two access services may still share local power or physical infrastructure.

Test a bounded interruption

In a planned test, observe active calls, new outgoing calls and incoming delivery separately. Record detection time, registration recovery and manual steps. Verify carrier-side diversion when the PBX is unreachable.

Test return to normal

Failback can trigger another address or state change. Confirm routing, audio and caller identity after the preferred connection returns. Include DNS caching in recovery analysis when service discovery is involved, and keep an independent communications path for incident coordination.

Retest voice identity and media after IP Telecom access failover

A backup circuit can restore IP reachability without preserving SIP source policy, registration, NAT or RTP. The IP Telecom service record requires one authorized new call through each designed path and restoration sequence.

Keep Intermedia provider routing separate from customer-path failover

The Intermedia provider guide distinguishes provider-monitored DID forwarding from customer WAN, power, firewall, PBX and alternate-site continuity.

Prove IntelePeer customer-edge independence

The IntelePeer provider guide does not treat a redundant trunk order as proof of independent access, PBX survival or media continuity.

Prove each BCM One recovery layer independently

The BCM One route diagnostic records provider proxy selection, customer-edge receipt and per-number alternate destinations as different evidence.

Prove which Cox layer selected the alternate leg

The Cox inbound diagnostic correlates the failed primary attempt with the actual new-call continuity transition.

Prove which Comcast layer created the alternate leg

The Comcast diagnostic correlates the primary attempt, selected group or number and subsequent new-call destination.

Prove the Lumen provider leg before inferring recovery

The Lumen diagnostic correlates route-plan selection, each observed trunk leg, edge receipt and the PBX result.

Prove the AT&T provider leg before claiming recovery

The AT&T diagnostic correlates scheme selection, group trunk group, edge receipt and PBX result without inventing trigger behavior.

Do not flatten Verizon continuity layers

The Verizon diagnostic distinguishes provider SBC redundancy, number-group redirection, access, edge receipt and PBX outcome.

Follow Bell recovery across provider and customer layers

The Bell diagnostic distinguishes provider path selection, number forwarding, edge receipt, PBX route and restoration.

Do not confuse Rogers peer choice with physical diversity

The Rogers diagnostic separates provider peer selection, access, route and POP diversity, edge receipt and restoration.

Sources & applicability

Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.

Continue your research

Hub

VoIP networking

Trace signaling and audio through your actual topology before changing ports or prioritization.

Explore topic →
Troubleshooting · Current Asterisk res_pjsip NAT, object-relationship and configuration references plus SIP flow guidance reviewed October 1, 2026; no endpoint, PBX, AoR, Contact, NAT device, firewall, VPN, signaling exchange, call, RTP stream or emergency workflow was tested

Remote extension works locally but fails away from the office

Trace a remote endpoint from DNS and transport through registration, stored Contact, inbound delivery and media without treating one green state as call proof.

Read guide →
Interactive tool

VoIP bandwidth calculator

Estimate IP-layer voice traffic per direction from codec rate, packet duration and concurrent calls.

Open tool →
Guide · Protocol concepts; firewall and endpoint controls vary by release

Dual WAN and SD-WAN for voice

Plan stable call paths and distinguish recovery of new calls from survival of existing calls.

Read guide →
Provider research · Current IP Telecom SIP Trunks, SIP Trunking product terms, Fair Use Policy, Ireland copper-transition and contact pages reviewed October 15, 2026; authentication method, registrar and proxy values, DNS behavior, technical routing, codecs, DTMF, RTP addresses, fax, emergency calling, messaging, exact failover, capacity entitlement, availability, compatibility, pricing and support performance remain order specific, and no account, quote, credential, number, port, PBX, endpoint, access circuit, packet, media stream, failover event, load exercise, message, emergency call or live call was inspected or tested

IP Telecom SIP trunks: Irish service, resilience and demarcation boundaries

Scope IP Telecom channel capacity, number porting, access resilience, optional TLS and SRTP, provider demarcation and unresolved technical handoff to the exact Irish business order.

Read guide →
Provider research · Intermedia's current SIP Trunking product page and the reviewed support pages for HostPilot, failover, PBX guidance, ports, compatibility and 911 were reviewed October 20, 2026. The ordered location, phone numbers, PBX or gateway, trunk profile, monitoring state, failover destinations, emergency identities, media and commercial terms remain account specific. No Intermedia account, quote, order, location, number, PBX, gateway, trunk, route, caller identity, monitor, packet, call history, QoS record, media stream, failover, emergency call, bill, price, availability, compatibility or support response was inspected or tested

Intermedia SIP Trunking: location, DID failover and evidence

Separate the ordered PBX location, assigned DIDs, caller identity, per-number failover, provider monitoring, call history, QoS and emergency identity.

Read guide →
Troubleshooting · Intermedia's current SIP Trunking product page and the reviewed support pages for HostPilot, failover, PBX guidance, ports, compatibility and 911 were reviewed October 20, 2026. The ordered location, phone numbers, PBX or gateway, trunk profile, monitoring state, failover destinations, emergency identities, media and commercial terms remain account specific. No Intermedia account, quote, order, location, number, PBX, gateway, trunk, route, caller identity, monitor, packet, call history, QoS record, media stream, failover, emergency call, bill, price, availability, compatibility or support response was inspected or tested

Intermedia SIP trunk sends a DID to the wrong failover number or location

Trace one inbound DID through HostPilot assignment, provider location monitoring, per-number failover, edge receipt, PBX route, call history and media.

Read guide →
Provider research · Current IntelePeer Customer Portal, package, routing-policy, number-translation, DID API, CDR and Dynamic 911 documentation was reviewed October 20, 2026. Account billing type, packages, trunks, route profiles, translation records, signaling interfaces, timers, CDR availability, capacity, media, emergency configuration and commercial terms remain deployment specific. No IntelePeer account, contract, package, number, trunk, route profile, translation, credential, PBX, SBC, packet, CDR, media stream, failover event, emergency call, price, availability, compatibility or support response was inspected or tested

IntelePeer SIP trunking: package, routing-profile and failover evidence

Separate package membership, bundle and usage routing models, redundant trunks, per-number translations, change timing, CDRs and customer-edge evidence.

Read guide →
Troubleshooting · Current IntelePeer Customer Portal, package, routing-policy, number-translation, DID API, CDR and Dynamic 911 documentation was reviewed October 20, 2026. Account billing type, packages, trunks, route profiles, translation records, signaling interfaces, timers, CDR availability, capacity, media, emergency configuration and commercial terms remain deployment specific. No IntelePeer account, contract, package, number, trunk, route profile, translation, credential, PBX, SBC, packet, CDR, media stream, failover event, emergency call, price, availability, compatibility or support response was inspected or tested

IntelePeer number uses the wrong package, route or failover

Trace one inbound attempt through number inventory, package membership, bundle or usage routing, trunk selection, number translation, CDR and PBX evidence.

Read guide →
Provider research · Current first-party BCM One implementation, portal, legal, SIP SLA, SIP HyperNetwork SLA and E911 service-addendum material was reviewed October 20, 2026. Account type, assigned hosts, DNS answers, registration, number routing, Request-URI translation, disaster-recovery targets, redundancy, timers, capacity, emergency configuration, SLA eligibility and commercial terms remain deployment specific. No BCM One account, contract, trunk, credential, number, route, registration, PBX, SBC, DNS answer, packet, media stream, disaster-recovery event, emergency call, price, availability, compatibility, credit or support response was inspected or tested

BCM One SIP trunking: number routing, Request-URI and recovery evidence

Separate static-address and registered service, per-number delivery, Request-URI translation, provider redundancy, disaster-recovery routing and SLA evidence.

Read guide →
Troubleshooting · Current first-party BCM One implementation, portal, legal, SIP SLA, SIP HyperNetwork SLA and E911 service-addendum material was reviewed October 20, 2026. Account type, assigned hosts, DNS answers, registration, number routing, Request-URI translation, disaster-recovery targets, redundancy, timers, capacity, emergency configuration, SLA eligibility and commercial terms remain deployment specific. No BCM One account, contract, trunk, credential, number, route, registration, PBX, SBC, DNS answer, packet, media stream, disaster-recovery event, emergency call, price, availability, compatibility, credit or support response was inspected or tested

BCM One number uses the wrong route, Request-URI or recovery target

Trace one inbound call through its service model, number route, Request-URI translation, provider proxy, customer edge, PBX and disaster-recovery destination.

Read guide →
Provider research · Current Cox Business Voice Trunking and certified-PBX pages plus Cox-hosted 2011–2012 Asterisk 1.8.7, Avaya IP Office 6.0 and Interactive Intelligence CIC reference guides were reviewed October 20, 2026. The older guides are product-, version- and lab-topology-specific and do not establish current universal settings, certification, continuity behavior or entitlement. No Cox account, quote, contract, service address, trunk, pilot or billing number, DID, credential, E-SBC, PBX, registration, route, packet, media stream, failover event, emergency call, price, availability, compatibility or support response was inspected or tested

Cox Business SIP trunking: pilot identity, DID routing and continuity evidence

Keep the current service description separate from legacy PBX guides while tracing the pilot or BTN, REGISTER, local E-SBC, delivered DID, PBX route and continuity destination.

Read guide →
Troubleshooting · Current Cox Business Voice Trunking and certified-PBX pages plus Cox-hosted 2011–2012 Asterisk 1.8.7, Avaya IP Office 6.0 and Interactive Intelligence CIC reference guides were reviewed October 20, 2026. The older guides are product-, version- and lab-topology-specific and do not establish current universal settings, certification, continuity behavior or entitlement. No Cox account, quote, contract, service address, trunk, pilot or billing number, DID, credential, E-SBC, PBX, registration, route, packet, media stream, failover event, emergency call, price, availability, compatibility or support response was inspected or tested

Cox SIP trunk registers but a DID uses the wrong route or continuity destination

Trace one inbound call through pilot registration, local E-SBC delivery, DID identity, PBX route and any provider-side continuity action.

Read guide →
Provider research · Current Comcast Business SIP Trunks product, enterprise and support pages plus the Trunk Services Version 1.2 attachment were reviewed October 20, 2026. The attachment contains general order, credit, power and emergency terms, while its Schedule A-1 technical specification is PRI-specific and is not a current SIP interface contract. No Comcast account, quote, service order, location, trunk group, number, forward target, access circuit, gateway, PBX, SBC, portal, report, packet, continuity event, emergency call, price, availability, compatibility or support response was inspected or tested

Comcast Business SIP Trunks: group routing, forwarding and evidence

Separate number inventory, trunk groups, Failover/Overflow, Load Balancing, Bursting, Unreachable Destination and Call Forward Not Reachable before changing a PBX route.

Read guide →
Troubleshooting · Current Comcast Business SIP Trunks product, enterprise and support pages plus the Trunk Services Version 1.2 attachment were reviewed October 20, 2026. The attachment contains general order, credit, power and emergency terms, while its Schedule A-1 technical specification is PRI-specific and is not a current SIP interface contract. No Comcast account, quote, service order, location, trunk group, number, forward target, access circuit, gateway, PBX, SBC, portal, report, packet, continuity event, emergency call, price, availability, compatibility or support response was inspected or tested

Comcast SIP Trunks sends an inbound call to the wrong group or forward destination

Trace one inbound call through number inventory, provider group selection, customer-edge receipt, PBX routing and the exact continuity control that selected another leg.

Read guide →
Provider research · Current Lumen SIP Trunking support, route-plan, number and emergency documentation, the 2024 product sheet and the 2026 communication-services end-of-sale FAQ were reviewed October 20, 2026. Lumen says existing contracted voice service continues for now while ordinary new sales have ended and additions, moves, renewals or expansions require individual review; it does not publish one universal decommissioning date. No Lumen account, contract, service ID, location, trunk, route plan, number, portal change, PBX, gateway, packet, call, emergency result, transition date, price, availability, compatibility or support response was inspected or tested

Lumen SIP Trunking: route plans, service transition and evidence

Separate the service ID, phone-number assignment, route plan, sequential or percentage hunt, selected trunk and PBX result while planning around Lumen's documented voice transition.

Read guide →
Troubleshooting · Current Lumen SIP Trunking support, route-plan, number and emergency documentation, the 2024 product sheet and the 2026 communication-services end-of-sale FAQ were reviewed October 20, 2026. Lumen says existing contracted voice service continues for now while ordinary new sales have ended and additions, moves, renewals or expansions require individual review; it does not publish one universal decommissioning date. No Lumen account, contract, service ID, location, trunk, route plan, number, portal change, PBX, gateway, packet, call, emergency result, transition date, price, availability, compatibility or support response was inspected or tested

Lumen SIP Trunking number uses the wrong route plan or trunk

Trace one inbound number through the correct service family, service ID, number-to-route-plan relationship, administrative status, hunt result, customer edge and PBX route.

Read guide →
Provider research · Current AT&T IP Flexible Reach product, implementation and 2026 explanatory pages plus the first-party 2021 product brief and 2019 Group Administrator Guide were reviewed October 20, 2026. The dated guide documents portal concepts and workflows but is not represented as a universal current account interface or entitlement. No AT&T account, enterprise, group, group trunk group, routing scheme, portal role, order, access circuit, PBX, SBC, number, packet, call, emergency result, price, availability, compatibility or support response was inspected or tested

AT&T IP Flexible Reach: trunk groups, routing schemes and evidence

Separate assigned numbers, group trunk groups, routing algorithms, capacity and portal actions from customer-edge and PBX outcomes.

Read guide →
Troubleshooting · Current AT&T IP Flexible Reach product, implementation and 2026 explanatory pages plus the first-party 2021 product brief and 2019 Group Administrator Guide were reviewed October 20, 2026. The dated guide documents portal concepts and workflows but is not represented as a universal current account interface or entitlement. No AT&T account, enterprise, group, group trunk group, routing scheme, portal role, order, access circuit, PBX, SBC, number, packet, call, emergency result, price, availability, compatibility or support response was inspected or tested

AT&T IP Flexible Reach call uses the wrong trunk group or route

Trace one inbound number through its group, routing scheme, algorithm, selected group trunk group, customer edge and PBX route.

Read guide →
Provider research · Verizon public product, implementation, service-document and rates pages reviewed October 20, 2026; the signed order and current implementation record govern, and no Verizon account, order, port, trunk, PBX group, redirect, VARRS design, packet, call, media stream, emergency result, price, availability, compatibility or support response was inspected or tested

Verizon Business IP Trunking: activation, porting and continuity evidence

Separate pre-install testing, native or test DIDs, later port completion, PBX-group handling, unreachable redirection and VARRS continuity.

Read guide →
Troubleshooting · Verizon public product, implementation, service-document and rates pages reviewed October 20, 2026; the signed order and current implementation record govern, and no Verizon account, order, port, trunk, PBX group, redirect, VARRS design, packet, call, media stream, emergency result, price, availability, compatibility or support response was inspected or tested

Verizon IP Trunking ported number reaches the wrong PBX route or redirect

Trace one moved number through cutover state, provider handling, optional group redirection, customer-edge receipt and the first loaded PBX route.

Read guide →
Provider research · Bell Canada public product, portal, reporting, support and emergency-service material reviewed October 20, 2026; no Bell account, order, portal role, number, forwarding rule, schedule, trunk group, report, PBX, edge, packet, call, media stream, emergency result, price, availability, compatibility or support response was inspected or tested

Bell SIP Trunking: forwarding, trunk-group reporting and emergency evidence

Separate per-number forwarding, provider overflow, dual connections, provider reporting, PBX routing and current emergency location.

Read guide →
Troubleshooting · Bell Canada public product, portal, reporting, support and emergency-service material reviewed October 20, 2026; no Bell account, order, portal role, number, forwarding rule, schedule, trunk group, report, PBX, edge, packet, call, media stream, emergency result, price, availability, compatibility or support response was inspected or tested

Bell SIP Trunking number forwards at the wrong time or during an outage

Find whether an unexpected destination came from Remote Call Forwarding, provider overflow, customer-edge handling or the first loaded PBX route.

Read guide →
Provider research · Rogers Business public SIP Trunking material, April 2021 fixed-network terms, branded information sheet and customer case study reviewed October 20, 2026; no Rogers account, agreement, order, Site, access circuit, diversity survey, peer, DID, CDR, PBX, SBC, IAD, packet, call, media stream, continuity event, emergency result, price, availability, compatibility or support response was inspected or tested

Rogers Business SIP Trunking: peers, overflow, diversity and redirect evidence

Separate purchased peer controls, Site access, physical diversity, DID routing, customer-edge receipt, PBX handling and emergency location.

Read guide →
Troubleshooting · Rogers Business public SIP Trunking material, April 2021 fixed-network terms, branded information sheet and customer case study reviewed October 20, 2026; no Rogers account, agreement, order, Site, access circuit, diversity survey, peer, DID, CDR, PBX, SBC, IAD, packet, call, media stream, continuity event, emergency result, price, availability, compatibility or support response was inspected or tested

Rogers SIP Trunking calls use the wrong peer, overflow or emergency redirect

Find whether an unexpected destination came from failover, load balancing, capacity overflow, emergency redirect, access handling or the first loaded PBX route.

Read guide →