Define the failure you intend to survive
A provider outage, local internet failure, PBX failure and a single unreachable destination need different responses. A second trunk on the same PBX and internet circuit does not remove those shared dependencies.
New-call recovery and active-call survival are different tests. Inbound number failover needs a provider-side routing plan.
Design outbound behavior
Specify which failures should trigger an alternate route. An authorization denial or invalid destination may require correction rather than another attempt. Limit retries and verify number formatting, caller identity and permissions on each trunk. Prevent loops between alternate paths.
Design inbound behavior separately
Inbound failover depends on control of the called number and the provider's routing options. Ask where calls go when the primary PBX cannot be reached and whether that behavior uses a timeout or a health signal. A second outbound account alone does not redirect inbound calls to your number.
DIDWW documents DNS SRV for a customer trunk host and trunk groups with selected rerouting disconnect codes, priority and weight. Flowroute documents per-number primary and failover destinations. Neither pattern implies that every SIP error or an already established call will move. Record the triggering response and every attempted destination when you test.
SIP.US documents primary and secondary trunk assignments plus PSTN Backup and Forward options. These have different triggers and channel use; see the SIP.US record rather than treating them as one universal failover mode.
Voxtelesys portal route profiles can prioritize registered-PBX, customer-IP and external-transfer destinations. Review the provider record and validate the actual advance trigger, cost and shared dependencies.
Amazon Chime SDK Voice Connector uses priority and weight for customer SIP hosts, while connector groups can span AWS Regions. Review the provider record and keep provider-region fallback distinct from the customer PBX, access network and active-call state.
Test recovery as well as failure
Use an agreed maintenance exercise. Confirm new calls on the backup path, expected handling of active calls and return to the primary route. Check capacity, billing assumptions and emergency-calling arrangements for the backup. Record the observed recovery time instead of describing the design as seamless without evidence.
Where the provider exposes a separate CDR for each delivery attempt, reconcile attempts by call identifier and time. DIDWW describes that behavior for SRV and trunk-group failover. A single successful final leg can hide a repeatedly failing primary leg.
Model every BYOC-P failure domain
Zoom Phone BYOC-P can use regional trunks, alternate Zoom data-center routing, multiple customer SBCs and Internet or private connectivity. Those controls do not establish one universal route order, timer, access diversity, carrier recovery or established-call behavior; test each accepted boundary separately.
Keep Genesys provider requirements separate from the deployed sequence
For Genesys Cloud BYOC, the provider record distinguishes OPTIONS, 503 and sequential-failover requirements from the selected carrier's actual target order, timers, capacity, restoration and established-call behavior.
Bind ACS Direct Routing failover to route priority and response code
For Azure Communication Services Direct Routing, the provider record preserves regular-expression match, route priority, equal-priority random SBC selection, OPTIONS health and Microsoft's documented 408, 503 and 504 next-SBC failover boundary.
Keep the CCAI Platform BYOC failover owner explicit
Google assigns customers responsibility for high availability and call routing from carrier services to the CCAI Platform media edge. The BYOC record preserves multiple inbound carriers, the single outbound-carrier boundary and requested Google-telephony fallback as different designs.
Trace a peoplefone offline-forwarding path
The peoplefone fallback diagnostic follows registration expiry, provider line state, the offline role, number filtering, alternate delivery and return to primary without representing forwarding as active-call survival.
Keep redundant targets distinguishable from stale branches
The A&A duplicate-ringing diagnostic inventories registration, direct server and Also Ring branches before deciding whether an alternate path is intended resilience or a retired target.
Apply SureVoIP’s timeout-only destination policy
For SureVoIP inbound delivery, use the provider-specific destination diagnostic to preserve the ordered routes and distinguish a timeout from Busy, Unavailable or later PBX failure.
Distinguish Magrathea health probes from call delivery
Use the Magrathea SIP Resilience diagnostic to correlate nominated addresses, provider probes, pool membership, new-call selection and later PBX routing.
Distinguish NFON multi-PBX modes from PSTN backup
Use the NFON backup-PBX diagnostic to correlate the selected mode, endpoint readiness, provider branch, PBX route and restoration.
Prove SIP DNS selection before expecting another target
Use the Voip Unlimited DNS failover diagnostic to trace NAPTR, SRV, address records, cache state, a qualifying failure and the new transaction.
Resolve Broadvoice failover mechanics for the ordered route
Broadvoice publishes built-in redundancy and failover without one public timer or route contract. The Broadvoice provider record keeps targets, health checks, failure responses, detection, restoration, new-call recovery and established-call behavior as separate acceptance evidence.
Qualify SIPcity’s optional peering failover address
SIPcity permits a primary and optional failover IP for peering, but does not publish one trigger or timer contract. The SIPcity provider record requires an approved new-call exercise and keeps active-call survival and restoration as separate evidence.
Separate Toku platform redundancy from customer-trunk failover
Toku describes redundant infrastructure, but the reviewed material does not define one customer trunk trigger, retry path or restoration timer. The Toku provider record requires the selected design and an approved new-call failure and recovery exercise.
Separate LoopUp endpoint distribution from DNS and WAN failover
LoopUp offers round-robin or ordered failover across customer endpoints and separately publishes regional platform FQDNs. The provider record requires each new-call choice and recovery path to be proved.
Separate SIPTRUNK gateway redundancy from call treatment
SIPTRUNK documents multiple gateway registration or SRV behavior separately from PSTN Backup, hard forwarding and voicemail. The mode-mismatch diagnostic keeps provider reachability, inbound destination, treatment trigger and restoration as different observations.
Do not combine SIP.US gateway failover with secondary routing
SIP.US documents provider-gateway redundancy, secondary-trunk DID routing and PSTN Backup as separate mechanisms. Use the SIP.US failover diagnostic to capture the qualifying failure, next attempted path, caller result and restoration.
Keep Flowroute provider-edge selection and number-route failover separate
Flowroute documents current PoP selection separately from per-number primary and failover route relationships. Use the Flowroute diagnostic to record the first delivery result, any second attempt and return to primary without assuming which responses advance.
Keep DIDWW trunk-group and DNS SRV attempts separate
DIDWW can create a new CDR for each trunk-group or DNS SRV attempt. The provider-specific diagnostic binds every attempt to the layer, configured trigger and destination that owned it.
Use every available Twilio edge address without losing trunk identity
Twilio recommends avoiding a single termination IP and preserving the personal trunk domain while edge routing changes. The termination diagnostic separates DNS or address failover from ACL and credential acceptance.
Preserve SIPStation failover precedence
Sangoma documents different behavior when no failover is configured and when account-level or per-DID failover exists. The SIPStation diagnostic records the first server, configured override, next attempt and final route.
Keep IP Telecom access diversity separate from SIP failover
IP Telecom recommends resilient connectivity such as backup broadband or 4G/5G. The provider record keeps access failover, provider SIP routing, alternate inbound delivery, PBX redundancy and established-call survival as separate evidence.
Treat Clearfly forwarding and virtual attendant as routing controls
Clearfly describes personalized forwarding and a virtual attendant for weather or phone-system outages. The provider record keeps those controls separate from SIP target health, access diversity, PBX resilience and established-call survival.
Bind Redcentric failover to the ordered access design
A legacy Redcentric description tied standard failover to provider-supplied circuits and treated third-party access as designed work. The provider record uses that only as a present-day acceptance question for circuits, targets, triggers, recovery and support.
Translate CommPeak redundancy claims into a tested route map
CommPeak publishes geo-redundant routing and failover language. The provider record still requires selected targets, DNS behavior, triggers, established-dialog limits, alternate inbound handling, recovery and rollback evidence.
Require an explicit Voximplant alternate-path design
The reviewed Voximplant pages do not define one universal customer failover sequence. Use the provider record to record targets, DNS dependency, triggers, retry behavior, established-dialog limits, recovery and rollback.
Separate Voip Unlimited DNS routing from portal diversion
The provider profile distinguishes NAPTR or SRV target selection, registered Contact, customer-system diversion and non-registration alerts.
Keep SignalWire resource assignment separate from failover
The reviewed SignalWire material documents number and Resource SIP Address routing but does not establish a redundant PBX retry policy. The provider profile keeps that gap explicit.
Interpret Telnyx failover from the recorded first result
Telnyx documents response-specific advancement for IP and FQDN routes and a separate registered-instance path for credential Connections. Use the Telnyx diagnostic to retain each attempt, response and next destination.
Do not invent Bandwidth failover triggers
Bandwidth Build documents prioritized routes and later failover routes but the reviewed public page does not publish a complete response-code or timer contract. The Bandwidth diagnostic preserves the observed attempt, result and any next route.
Classify Voipfone diverts before calling them failover
Voipfone publishes Always, closed, busy, no-answer and PSTN-failover controls. The Voipfone diagnostic records which rule was enabled, what triggered and which attempt occurred.
Classify the VoIP.ms failover state first
VoIP.ms separates Busy, Unreachable, No Answer and Max Capacity. The VoIP.ms diagnostic records the trigger evidence and alternate attempt for each.
Read the Twilio stopping response before expecting another URI
Twilio publishes response classes that stop Origination URL advancement and a four-second no-response boundary. The Twilio diagnostic preserves each attempt.
Test Plivo fallback only at its documented boundary
The Plivo inbound diagnostic distinguishes an unresponsive primary from a reachable destination that returns a final SIP response.
Test Vonage priority and timeout at their documented boundary
The Vonage inbound diagnostic distinguishes an unreachable URI from a reachable target that returns a final SIP response.
Preserve Voxtelesys destination priority and transfer ownership
Voxtelesys supports prioritized route destinations and a later Transfer using an outbound trunk group. The diagnostic retains the actual attempt and avoids inventing a universal response matrix.
Separate Amazon Chime group fallback from origination routing
Voice Connector group priority and origination-host priority are different selection layers. The Amazon Chime diagnostic traces each without claiming active-call survival.
Test Callcentric Network Down Forward below DID Forward
A direct DID Forward has higher priority than Call Treatments, including a network-down treatment. The Callcentric diagnostic tests precedence, the separate forwarded leg and return to primary.
Scope Anveo Direct failover to the DID add-on
The Failover Add-on can send an inbound DID to a backup SIP URI, while outbound LCR has different controls. The diagnostic records the actual attempts without inventing a trigger matrix.
CarrierX soft failure is not dead-trunk state
CarrierX separates one-call soft failure from thresholded hard-failure state and SIP OPTIONS monitoring. The diagnostic retains each transition and next attempt.
AVOXI terminal codes are explicit stop controls
An AVOXI URI can list 400–699 responses that terminate a call. The diagnostic does not infer universal retry or alternate-target behavior for other outcomes.
Separate Easybell address order from Offline forwarding
A later Trusted IP and an Offline forward to a telephone number are different mechanisms. The diagnostic requires observed attempts instead of an invented universal trigger.
SIP.US Forward, Backup and secondary trunks have different precedence
PSTN Forward bypasses the PBX and prevents conditional Backup from engaging; a secondary trunk is a separate SIP route. The diagnostic requires observed attempts.
Separate Flowroute edge recovery from number-route failover
A preferred PoP can change the Flowroute source edge while the number remains on the same customer route. The Flowroute failover diagnostic records both layers.
ClearlyIP number-level failover has separate precedence
The ClearlyIP workflow keeps per-number rules, Location rules, Smart Routing and observed recovery as different evidence.
Keep Simwood routing controls and observed recovery separate
The Simwood workflow records time-of-day routing, forwarding, failover and the provider attempt as different evidence.
Do not pin one Sinch regional edge
The Sinch diagnostic preserves the regional FQDN, DNS answers, selected address and observed result.
Do not flatten Commio responses into generic failover
The Commio route diagnostic preserves silence, 486, 503 or busy and elapsed time before deciding whether advancement was expected.
Test each Nextiva failover boundary
The Nextiva provider guide keeps portal forwarding, redundant provider servers and a second customer path as different controls.
Treat Intermedia failover as a per-number new-call route
The Intermedia diagnostic correlates the monitored location, configured ten-digit alternate, selected destination and restoration without inventing a trigger matrix.
Explain each Infobip route advance
The Infobip route diagnostic distinguishes priority, weight, time-window eligibility, administrative state, OPTIONS status, connection timing and answer timeout.
Distinguish IntelePeer redundant trunks from number failover
The IntelePeer route diagnostic separates bundle redundancy, usage-profile selection and switched-number Forward or Failover records.
Separate BCM One proxy redundancy from per-number recovery
The BCM One provider guide keeps provider-side proxy behavior distinct from ordered Disaster-Recovery Routing targets.
Keep Cox continuity controls independently observable
The Cox Business provider guide separates always-forward, not-reachable, route-exhaustion, backup-PBX and provider-core layers.
Name the Comcast continuity control precisely
The Comcast provider guide separates Failover/Overflow, Load Balancing, Bursting, Unreachable Destination and Call Forward Not Reachable.
Name the Lumen hunt and failure evidence precisely
The Lumen provider guide distinguishes sequential and percentage allocation from generic failover claims and undocumented timers.
Name the AT&T algorithm and forwarding control
The AT&T provider guide keeps Linear, Round Robin, % Allocation and Most Idle separate from Unreachable Destination and Forward Always.
Name the Verizon continuity mechanism
The Verizon guide separates optional VARRS SBC capacity from PBX Group Unreachable and Call Forward Unreachable redirection.
Name the exact Bell continuity control
The Bell guide separates dual virtual connections, automatic overflow and per-number Remote Call Forwarding modes.
Name the exact Rogers continuity control
The Rogers guide keeps peer failover, active load balancing, capacity overflow and as-needed emergency redirect distinct.
Name the ThinkTel recovery mechanism
The ThinkTel diagnostic keeps secondary-binding selection, response-code-triggered SureCall and all-down forwarding distinct.
Name the Iristel failover layer
The Iristel diagnostic distinguishes provider redundancy, customer access, SIP delivery and backup-line redirection.
Name the TELUS resiliency purpose
The TELUS diagnostic distinguishes provider SBC redundancy, trunk-group selection, customer access, edge receipt and PBX routing.
Do not merge SaskTel overflow with emergency redirection
The SaskTel diagnostic separates RTM overflow, requested emergency redirection, customer access, PBX forwarding and restoration.
Trace Cogeco provider selection before customer changes
The Cogeco diagnostic separates provider geo-redundancy, customer access, eSBC receipt, PBX routing and restoration.
Do not merge Flowroute Edge Strategy with DID failover
The Flowroute diagnostic traces provider PoP attempts separately from the number's primary and failover route relationships.
Version and order AireSpring routing controls
The AireSpring guide preserves dated portal and DTO material without turning it into one universal trigger or restoration sequence.
Keep OnSIP ring-time failover separate from PBX forwarding
The OnSIP guide compares the saved provider timer and external destination with local inbound rules and observed attempts.
Treat DIDforSale gateway diversity as ingress scope, not observed failover
The DIDforSale guide preserves every current provider source, packet receipt and customer route without inventing universal timers or retry order.
Do not convert multiple Zadarma source addresses into inbound failover claims
The Zadarma guide treats confirmed customer egress addresses separately from number-level inbound routing and active-call survival.
Do not turn Voxbeam network redundancy into endpoint-failover rules
The Voxbeam guide leaves destination order, triggers, restoration and active-call behavior open until the account policy proves them.
Keep GoTrunk POP selection separate from customer failover
The GoTrunk guide does not turn provider locations into undocumented destination order, trigger or active-call guarantees.
Distinguish DIDWW DNS SRV from Trunk Group attempts
The DIDWW guide keeps transparent SRV targets in one CDR and member rerouting as separate attempt records.
Treat Exotel proxy retry and destination order as new-call behavior
The Exotel guide does not turn multiple addresses or destinations into proof of health-aware routing or established-call survival.
Do not infer Voximplant recovery from one registration transition
The Voximplant diagnostic retains registration state, callback or status evidence and call outcome separately.
Compare Colt failure detection with recovery
The Colt failover diagnostic distinguishes first-call detection, blacklist state, timer or OPTIONS recovery and later selection.
Separate Gamma trunk rerouting from cloud call control
The Gamma continuity diagnostic distinguishes trunk, Call Manager and Inbound triggers.
Separate Bandwidth route priority from Final Destination URI
The Bandwidth provider record keeps route groups, endpoint weights and number-level failover controls distinct.
Separate Commio destination advancement from DNS and PBX recovery
The Commio provider record preserves ordered attempts, responses, timeouts and later recovery evidence.
Separate LES.NET forwarding from failure-triggered failover
The LES.NET provider record keeps a selected DID destination, telephone forwarding, provider attempt and recovery evidence distinct.
Require the applied Wavix destination policy
The Wavix diagnostic does not convert multiple saved destinations or product language into a universal failover sequence.
Separate Allstream forwarding, overflow, failover and pooling
The Allstream diagnostic distinguishes portal Unavailable forwarding, trunk overflow, multi-endpoint failover, two-endpoint pooling, WAN state and PBX routes.
Keep Cloudli Service Continuity separate from PBX failover
The Cloudli diagnostic preserves the affected number, backup destination, provider attempt, PBX reachability and restoration state.
Use Orange project response policy, not generic SIP assumptions
The Orange Business Talk guide treats guide-specific probing and rerouting rules as project evidence and requires primary restoration proof.
Make Vodafone endpoint diversity and restoration observable
The Vodafone Evolved Voice diagnostic records eligible endpoints, trigger, alternate selection, call result and return to primary.
Distinguish Swisscom continuity options
The Swisscom Enterprise SIP diagnostic keeps core forwarding, Multi SAP, Multi PBX, Multi Server and trunk failover independently observable.
Make Sunrise backup and restoration observable
The Sunrise Business Voice SIP diagnostic records trigger, selected alternate, new-call result and return to primary.
Identify the selected Proximus redundancy mode
The Proximus Business Trunking diagnostic keeps Basic-Single, Single, Basic-Multi and Secure-Multi evidence distinct.
Verify Crazytel continuity at each boundary
The Crazytel SIP trunk diagnostic keeps Divert on Down, network failover, alternate call and primary restoration separate.
Verify MaxoTel Offline diversion as a call path
The MaxoTel SIP Trunking guide keeps configured destination, offline trigger, alternate completion and restoration separate.
Do not infer voice continuity from broadband options
The Aussie Broadband SIP Trunks guide keeps Internet access, alternate routing, restored service and completed calls independently observable.
Prove selected Symbio dual-network routing
The Symbio Enterprise SIP trunk diagnostic verifies entitlement, policy, trigger, selected path, call result and restoration independently.
Name the exact Telstra continuity mechanism
The Telstra SIP Connect diagnostic keeps Shared Capacity, access redundancy, PBX failover, number diversion and BRS+ distinct.
Name the exact Optus continuity feature
The Optus Evolve Voice diagnostic keeps Emergency Diversion, Dual Voice Trunk and Dual Exchange Homing distinct.
Name the One NZ continuity option
The One NZ SIP diagnostic distinguishes Multi-Site diversity, Dual Circuit, dual Diversity and Smart SIP 4G failover Access.
Prove the 2degrees continuity design
The 2degrees SIP diagnostic distinguishes provider rerouting, alternate data paths and PBX mobile redirection.
Prove the Vocus continuity design
The Vocus SIP Voice diagnostic distinguishes whole-trunk diversion, alternate access and PBX routing.
Prove Superloop continuity at each boundary
The Superloop diagnostic distinguishes outage posts, alternate access, provider routing, PBX policy and completed calls.
Prove Enreach continuity rather than assuming it
The Enreach diagnostic checks entitlement, trigger, target, provider action, call result and restoration.
Treat MetTel redundancy as bounded product evidence
The MetTel SIP Trunking guide does not convert a multi-datacenter claim into tested account failover, route diversity or completed calls.
Bound NUSOflex to the eligible inbound path
The NUSO guide does not turn inbound PSTN-impairment claims into universal outbound, access or established-call continuity.
Separate Always, Unreachable and Enterprise Trunking
The Telesystem guide keeps saved forwarding, trigger, delay, alternate route, trunk group and completed call distinct.
Separate TPx forwarding, DTO and SD-WAN continuity
The TPx guide keeps CFNR, Trunk Group Call Forwarding, Standard DTO, Enhanced DTO and active/active access evidence distinct.
Bound Lingo redundancy and automatic-failover claims
The Lingo guide preserves feature, trigger, alternate target, new attempt, answer and restoration as separate evidence.
Do not infer Voyant restoration from redundancy language
The Voyant guide preserves access state, new attempts, status components and verified ordinary-call restoration separately.
Name the exact Windstream DTO option
The Windstream guide distinguishes Trunk to Trunk and Trunk to Number Redirect from access survival and established-call continuity.
Bound Granite DTFO to the ordered design
The Granite guide separates trigger, alternate target and observed delivery from access survival and established-call continuity.
Bind FirstLight redundancy to the accepted order
The FirstLight guide separates redundant access loops, alternate-path evidence and observed calls from established-call continuity.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- IETF RFC 3261 — SIP, including linked updates ↗
- Asterisk res_pjsip configuration ↗
- DIDWW service failover and load balancing ↗
- Flowroute inbound route and failover configuration ↗
- AWS: Managing Voice Connector groups ↗
- AWS: Editing Voice Connector settings ↗
- Zoom Phone BYOC-P architecture ↗
- BYOC-P deployment and connectivity options ↗
- BYOC-P infrastructure requirements ↗
- BYOC-P call processing ↗
- BYOC-P configuration guide ↗
- Zoom Phone BYOC-P dial-plan management ↗
- Zoom Phone emergency addresses ↗
- Zoom Phone emergency-call routing ↗
- Zoom Phone SMS for BYOC numbers ↗
- About Genesys Cloud BYOC Cloud ↗
- Carrier requirements for BYOC Cloud ↗
- Create a BYOC Cloud trunk ↗
- Configure SIP routing for a BYOC Cloud trunk ↗
- Choose a BYOC Cloud trunk transport ↗
- TLS trunk transport specification for BYOC Cloud ↗
- Dynamic Cloud Voice platform overview and migration guide ↗
- Dynamic Cloud Voice future-default announcement ↗
- SIP provider questionnaire for BYOC trunks ↗
- Genesys Cloud sites overview ↗
- Select an inbound Number Plan Site ↗
- Set up emergency services with BYOC ↗
- Genesys Cloud fair use policy ↗
- BYOC Cloud configuration checklist ↗
- Azure Communication Services retirement and breaking-changes guide ↗
- Provision Azure Communication Services Direct Routing ↗
- Azure Direct Routing infrastructure requirements ↗
- Azure Direct Routing SIP protocol specification ↗
- Monitor Azure Communication Services Direct Routing ↗
- Migrate ACS Direct Routing to Teams Phone ↗
- Azure Communication Services emergency-calling scope ↗
- Azure telephony known limitations ↗
- Certified SBCs for Azure Communication Services Direct Routing ↗
- Azure Communication Services pricing scenarios ↗
- Google Cloud CCAI Platform Bring Your Own Carrier ↗
- Google Cloud CCAI Platform BYOC IP allow list ↗
- Google Cloud CCAI Platform locations ↗
- Google Cloud CCAI Platform SIP URIs ↗
- Google Cloud CCAI Platform high availability ↗
- Google Cloud CCAI Platform Interactive Virtual Assistant guide ↗
- Google Cloud CCAI Platform telephony partners ↗
- peoplefone: SIP-TRUNK setup, registration and forwarding ↗
- peoplefone: registration and network troubleshooting ↗
- peoplefone: firewall, NAT keep-alive and service ranges ↗
- A&A: VoIP SIP Trunks ↗
- A&A: multiple inbound targets and Also Ring ↗
- A&A: VoIP technical information ↗
- A&A: VoIP security controls and registration visibility ↗
- SureVoIP number destinations ↗
- SureVoIP SIP traces ↗
- SureVoIP terms and conditions ↗
- Magrathea SIP resilience ↗
- Magrathea Numbering in the UK & Ireland ↗
- Magrathea Voice Connectivity ↗
- NFON SIP Trunk Flexx product page ↗
- NFON SIP Trunk Flexx technical manual v3.1 (DE) ↗
- NFON SIP Trunk Flexx SLA v1 (EN) ↗
- NFON service status ↗
- Voip Unlimited SIP Trunks ↗
- RFC 3263: Locating SIP Servers ↗
- RFC 2782: DNS SRV resource records ↗
- RFC 3403: DDDS DNS database and NAPTR records ↗
- Broadvoice SIP Trunking ↗
- Broadvoice master service agreements ↗
- Broadvoice Elastic SIP Trunking Addendum ↗
- Broadvoice SIP trunking portal ↗
- Broadvoice contact and support ↗
- Broadvoice platform status ↗
- SIPcity SIP Trunking ↗
- SIPcity registration and peering explained ↗
- SIPcity generic SIP registration configuration ↗
- SIPcity 3CX configuration ↗
- SIPcity network ports and IPs ↗
- SIPcity number porting ↗
- SIPcity channel explanation ↗
- SIPcity billing and payments ↗
- SIPcity master service agreement ↗
- Toku Carrier Services ↗
- Toku for Microsoft Teams ↗
- Toku Voice Connectivity help centre ↗
- Toku Singapore Numbers ↗
- Toku Malaysia Numbers ↗
- Toku Indonesia Numbers ↗
- Toku Singapore Subscriber Registration ↗
- Toku Singapore Level3 Number Portability ↗
- Toku Singapore Regulations ↗
- Toku Singapore Level6 Wholesale Services ↗
- LoopUp SIP Trunking Setup Guide ↗
- LoopUp SIP Trunking Public Certificate Chain ↗
- LoopUp SIP Trunking Supported Root Certificate Authorities ↗
- LoopUp SIP Trunking Configuration for AudioCodes Mediant SBCs ↗
- LoopUp SIP Trunking Configuration for Ribbon 1000, 2000, and SWe Edge SBCs ↗
- RFC 5246: TLS 1.2 ↗
- RFC 4568: SDP Security Descriptions for Media Streams ↗
- SIPTRUNK IP authentication setup ↗
- SIPTRUNK registration connection issues ↗
- SIPTRUNK inbound-call troubleshooting ↗
- SIPTRUNK registration status ↗
- SIPTRUNK call failover options ↗
- SIPTRUNK interconnection and gateway addresses ↗
- SIPTRUNK general SIP device configuration ↗
- SIP.US current gateways and interconnection requirements ↗
- SIP.US general device configuration ↗
- SIP.US registration status guide ↗
- SIP.US call failover options ↗
- SIP.US SIP glossary and routing model ↗
- SIP.US IP authentication guide ↗
- SIP.US Asterisk registration guide ↗
- Flowroute current PoP and DNS guidance ↗
- Flowroute interconnection options ↗
- DIDWW inbound trunk groups ↗
- DIDWW inbound SIP trunk configuration ↗
- DIDWW SIP response codes in call logs ↗
- DIDWW Voice IN CDR streaming attributes ↗
- Twilio Elastic SIP Trunking configuration ↗
- Twilio Elastic SIP Trunking troubleshooting ↗
- Twilio sending-SIP best practices ↗
- Twilio CredentialList resource ↗
- Twilio Trunk resource ↗
- Twilio error 32201: source IP address not in ACL ↗
- Sangoma: Troubleshooting SIPStation ↗
- Sangoma: Failover of inbound SIPStation DIDs ↗
- Sangoma: SIPStation notifications and access restrictions ↗
- Sangoma: FreePBX SIPStation module ↗
- Sangoma: SIPStation PJSIP trunk setup ↗
- Sangoma: FreePBX inbound-route user guide ↗
- Sangoma: Configuring a PBX or device with SIPStation ↗
- IP Telecom SIP Trunks ↗
- IP Telecom terms and SIP Trunking product schedule ↗
- IP Telecom Fair Use Policy ↗
- IP Telecom Ireland copper switch-off guidance ↗
- IP Telecom contact and support ↗
- Clearfly voice services and SIP trunking ↗
- Clearfly service FAQs ↗
- Clearfly partner programme and portal ↗
- Clearfly support contacts ↗
- Clearfly legal and regulatory index ↗
- Clearfly Acceptable Use Policy ↗
- Redcentric voice modernisation ↗
- Redcentric communications services ↗
- Redcentric customer support ↗
- Redcentric service status ↗
- Redcentric SIP Trunking Service Description SD032 v2.1 (legacy public PDF) ↗
- Redcentric Hays telephony customer case study ↗
- CommPeak SIP trunking ↗
- CommPeak documentation and developer hub ↗
- CommPeak SIP account configuration ↗
- CommPeak FreePBX SIP trunk guide ↗
- CommPeak Asterisk PBX SIP trunk guide ↗
- CommPeak pricing overview ↗
- CommPeak service status ↗
- Voximplant SIP trunking solution ↗
- Voximplant SIP trunk connection FAQ ↗
- Voximplant SIP phone registration FAQ ↗
- Voximplant processing calls in scenarios ↗
- Voximplant CallSIP parameters ↗
- Voximplant telephony and SIP capabilities FAQ ↗
- Voximplant pricing ↗
- Voximplant service status ↗
- Voip Unlimited voice portfolio ↗
- Voip Unlimited partner operations and support tools ↗
- Voip Unlimited legal and regulatory documents ↗
- Voip Unlimited Master Services Agreement V3.0 ↗
- SignalWire SIP trunking ↗
- SignalWire SIP credentials ↗
- SignalWire Get SIP credential API ↗
- SignalWire Update SIP profile API ↗
- SignalWire FreePBX integration ↗
- SignalWire caller ID and CNAM ↗
- SignalWire rate limits ↗
- SignalWire E911 ↗
- SignalWire rates ↗
- Telnyx SIP trunking service objects ↗
- Telnyx authentication methods ↗
- Telnyx failover and retries ↗
- Telnyx SIP response codes ↗
- Telnyx Outbound Voice Profiles ↗
- Telnyx round-robin routing ↗
- Telnyx current SIP network information ↗
- Telnyx machine-readable voice network data ↗
- Telnyx configuration-guide boundary ↗
- Bandwidth Build SIP trunking setup ↗
- Bandwidth number feature and Final Destination URI management ↗
- Voipfone FreePBX configuration guide ↗
- Voipfone inbound routing control ↗
- Voipfone phone-number routing controls ↗
- Voipfone PBX call-divert and PSTN-failover controls ↗
- Voipfone number porting ↗
- VoIP.ms DID routing, failover, POP and inbound format ↗
- VoIP.ms subaccount authentication and registration ↗
- VoIP.ms server and DID POP selection ↗
- VoIP.ms DID troubleshooting ↗
- VoIP.ms incoming-call troubleshooting ↗
- VoIP.ms registration troubleshooting ↗
- Twilio OriginationUrl resource ↗
- Twilio Programmable Voice failover best practices ↗
- Twilio Elastic SIP Trunking IP addresses ↗
- Plivo Zentrunk quickstart ↗
- Plivo Zentrunk technical specifications ↗
- Plivo SIP Trunking account limits ↗
- Plivo Zentrunk hangup codes ↗
- Plivo Zentrunk debug logs ↗
- Vonage SIP technical details ↗
- Vonage SIP Dashboard guide ↗
- Vonage Asterisk PJSIP configuration ↗
- Vonage FreePBX configuration ↗
- Vonage Voice Logs guide ↗
- Voxtelesys DID and number routing ↗
- Voxtelesys SIP Trunk Registrar ↗
- Voxtelesys portal IP-address routing ↗
- Voxtelesys registration ACL ↗
- Voxtelesys failover transfer ↗
- Voxtelesys call records ↗
- AWS: Managing Amazon Chime SDK Voice Connectors ↗
- AWS: Creating a Voice Connector and encryption scope ↗
- AWS: Amazon Chime SDK endpoints and quotas ↗
- AWS: Voice Connector network and bandwidth requirements ↗
- Callcentric SIP trunking ↗
- Callcentric registration credentials ↗
- Callcentric DID forwarding ↗
- Callcentric DID-forward precedence ↗
- Callcentric network-down forward ↗
- Callcentric forwarded-call billing ↗
- Anveo Direct FAQ ↗
- Anveo Direct inbound DID service ↗
- Anveo Direct call termination ↗
- Anveo Direct network ↗
- Anveo Direct services ↗
- CarrierX trunk-group object ↗
- CarrierX trunk object ↗
- CarrierX SIP trunk quick start ↗
- CarrierX receive and place calls ↗
- CarrierX phone-number model ↗
- AVOXI outbound SIP trunk configuration ↗
- AVOXI inbound SIP URI forwarding ↗
- AVOXI outbound SIP trunk diagnostic ↗
- AVOXI SIP forwarding and trunking overview ↗
- Easybell general VoIP configuration ↗
- Easybell Trusted IP authentication ↗
- Easybell SIP-trunk authentication by trusted FQDN ↗
- Easybell automatic fallback routing ↗
- SIP.US inbound call troubleshooting ↗
- SIP.US channel-limit guidance ↗
- SIP.US E911 information ↗
- Flowroute current PoP interconnection requirements ↗
- Flowroute direct-media firewall requirements ↗
- Flowroute preferred inbound PoP behavior ↗
- Flowroute TLS signaling scope ↗
- Flowroute inbound SRV routing example ↗
- ClearlyIP current SIP trunking product page ↗
- ClearlyIP current documentation destination ↗
- ClearlyIP legacy configuration-guide scope and freshness notice ↗
- ClearlyIP legacy trunk details and regional registrars ↗
- ClearlyIP legacy Location, number routing and failover reference ↗
- ClearlyIP legacy FreePBX automated-module reference ↗
- ClearlyIP legacy FreePBX PJSIP setup reference ↗
- ClearlyIP legacy common SIP issues reference ↗
- Simwood Hosted SIP Trunks ↗
- Simwood hosted trunks interop ↗
- Simwood hosted trunk overview ↗
- Simwood Asterisk 16 hosted trunk example ↗
- Simwood hosted TLS/SRTP settings ↗
- Simwood Partner and Direct IP addresses and whitelisting ↗
- Simwood portal overview ↗
- Simwood Carrier Services API v3 ↗
- Sinch Voice API SIP Trunking reference ↗
- Sinch Voice API callback reference ↗
- Sinch Voice API authentication reference ↗
- Sinch Voice API call headers ↗
- Sinch Voice API call detail records ↗
- Sinch Voice API release notes ↗
- Sinch Elastic SIP Trunking product overview ↗
- Sinch BYOC SIP Trunking overview ↗
- Commio inbound routing profiles ↗
- Commio outbound trunks ↗
- Commio Technical FAQs ↗
- Commio SIP INVITE examples ↗
- Commio outbound routing profiles ↗
- Commio E911 portal workflow ↗
- Commio E911 service overview ↗
- Commio support ticket and escalation guide ↗
- Nextiva SIP Trunking product page ↗
- Set Up your Nextiva Trunking Account ↗
- Nextiva Trunking FAQs ↗
- Nextiva Networking Guidelines ↗
- Nextiva Inbound Call Failure ↗
- Nextiva Outbound Call Failure ↗
- Nextiva Avaya PBX SIP Trunking Setup Guide (legacy reference configuration) ↗
- Intermedia SIP Trunking product page ↗
- Intermedia SIP Trunking overview ↗
- Intermedia SIP Trunking HostPilot overview ↗
- Intermedia SIP Trunking failover routing ↗
- Intermedia PBX configuration guides ↗
- Intermedia service and configuration port information ↗
- Intermedia certified PBX list ↗
- Intermedia emergency 911 policy and information ↗
- Infobip SIP trunking ↗
- Infobip SIP trunk setup ↗
- Infobip Call Routing overview ↗
- Infobip Call Routing route creation ↗
- Infobip inbound route selection ↗
- Infobip route execution and troubleshooting ↗
- Infobip SIP Trunks API ↗
- Infobip Voice reports ↗
- IntelePeer Customer Portal quick-start guide ↗
- IntelePeer Customer Portal FAQs ↗
- IntelePeer call-detail record reference ↗
- IntelePeer number forwarding and failover ↗
- IntelePeer Phone Number DID Management API ↗
- IntelePeer Dynamic 911 integration testing ↗
- BCM One SIP Trunking and Implementation Guide, September 2024 ↗
- BCM One customer portals ↗
- BCM One legal and service documents ↗
- BCM One SIP Service Level Agreement ↗
- BCM One SIP Service E-911 and Service Addendum ↗
- BCM One SIP HyperNetwork Service Level Agreement ↗
- Cox Business Voice Trunking ↗
- Cox Business Asterisk 1.8.7 configuration guide ↗
- Cox Business Avaya IP Office 6.0 configuration guide ↗
- Cox Business Interactive Intelligence CIC configuration guide ↗
- Comcast Business SIP Trunks ↗
- Comcast Business Enterprise SIP Trunks ↗
- Comcast Business Trunks features ↗
- View Comcast Business SIP Trunks numbers ↗
- View Comcast Business Trunks utilization reports ↗
- Comcast Enterprise Trunk Service product-specific attachment ↗
- Lumen SIP Trunking support ↗
- Lumen communication-services end-of-sale FAQ ↗
- Update a Lumen SIP Trunking route plan ↗
- Assign Lumen SIP Trunking numbers and manage 911 information ↗
- Lumen 933 emergency testing FAQ ↗
- AT&T IP Flexible Reach product page ↗
- AT&T IP Flexible Reach Group Administrator Guide ↗
- AT&T: What is IP Flexible Reach? ↗
- AT&T IP Flexible Reach implementation centre ↗
- AT&T cloud-based versus premises phone systems ↗
- Verizon VoIP Services welcome kit ↗
- Verizon Business IP Trunking Services ↗
- Verizon Voice over IP online service document ↗
- Verizon Voice Over IP rates and charges ↗
- Bell voice solutions and SIP Trunking ↗
- Bell SIP Trunking client administration portal guide ↗
- Bell SIP Trunking end user portal guide ↗
- Bell SIP Trunking performance and service reporting user guide ↗
- Bell SIP Trunking support guide ↗
- Bell SIP Trunking emergency-service limitations ↗
- Rogers Business Fixed Network Terms — SIP Services schedule (April 2021) ↗
- Rogers Business SIP Trunking information sheet ↗
- Rogers Business SIP trunking overview ↗
- Rogers SIP Trunking Pizza Pizza case study ↗
- ThinkTel SIP trunk service overview ↗
- ThinkTel SIP authentication ↗
- ThinkTel SIP failover ↗
- ThinkTel SureCall response-code triggers ↗
- ThinkTel SIP trunk IP-binding limit ↗
- ThinkTel CDR download ↗
- ThinkTel 911 testing procedure ↗
- Iristel business SIP Trunking ↗
- Iristel wholesale SIP Trunking ↗
- Iristel SIP trunk failover and redundancy ↗
- Iristel account and Espresso DID portals ↗
- Iristel wholesale E-911 services ↗
- Iristel Reasonable Use Policy ↗
- TELUS Business SIP Trunking ↗
- TELUS SIP Trunking Service R4 eContract service terms ↗
- TELUS Universal Call Blocking support ↗
- TELUS Partner Solutions support ↗
- SaskTel IP Trunking ↗
- SaskTel CRTC 21412 Item 500.23 — IP Trunking Service ↗
- SaskTel index for all tariffs — effective June 17, 2026 ↗
- SaskTel Emergency Voice Local Network Access Redirection — Item 1000.03 ↗
- Cogeco Business SIP Trunking ↗
- Cogeco specific terms — Business Phone, SIP Trunking and Hosted PBX ↗
- Cogeco PBX security guidelines for SIP Trunking customers ↗
- Cogeco Business 911 emergency-service limitations ↗
- Cogeco MLTS 9-1-1 best practices for HPBX and SIP/PRI customers ↗
- Flowroute preferred inbound PoP configuration ↗
- Flowroute host-based routing and DID assignment ↗
- Flowroute connected PoP review ↗
- Flowroute edge proxy and PoP configuration changes ↗
- Flowroute IP-based outbound authentication ↗
- Flowroute TLS requirements ↗
- Flowroute service guide technical specifications ↗
- AireSpring SIP Trunking ↗
- AireSpring SIP Trunking data sheet, revision May 12, 2023 ↗
- AireSpring Master Service Agreement ↗
- AireSpring Long-Distance SIP Trunking ↗
- AireSpring data-sheet index ↗
- AireSpring Top 10 Reasons for SIP Trunking infographic, revision July 5, 2022 ↗
- OnSIP Trunking ↗
- Enabling OnSIP Trunking ↗
- OnSIP Trunking Inbound Call Preferences ↗
- Enable E911 ↗
- Asterisk Configuration for OnSIP Trunking ↗
- Asterisk documentation: Configuring chan_sip ↗
- DIDforSale IP interconnection configuration ↗
- DIDforSale SIP account creation ↗
- DIDforSale FreePBX PJSIP IP-based example ↗
- DIDforSale FreePBX PJSIP SIP-account example ↗
- DIDforSale SIP trunk service ↗
- DIDforSale customer service agreement ↗
- Zadarma SIP trunk connection methods ↗
- Zadarma IP-authorized SIP trunk FAQ ↗
- Zadarma FreePBX PJSIP setup ↗
- Zadarma server delivery by SIP URI ↗
- Zadarma Asterisk IP-authorized trunk setup ↗
- Zadarma P-Asserted-Identity caller-ID guidance ↗
- Zadarma echo-test guidance ↗
- Voxbeam getting-started and outbound routing help ↗
- Voxbeam service and DID FAQ ↗
- Voxbeam DID service and capacity packages ↗
- Voxbeam wholesale voice services ↗
- Voxbeam network overview ↗
- Voxbeam VoIP glossary and codec summary ↗
- Voxbeam Asterisk chan_sip example ↗
- Asterisk PJSIP endpoint-identification troubleshooting ↗
- GoTrunk SIP Endpoints ↗
- GoTrunk FreePBX configuration guide ↗
- GoTrunk Asterisk configuration guide ↗
- GoTrunk Quick Start ↗
- GoTrunk Locations and emergency calling ↗
- GoTrunk call-detail records and traces ↗
- GoTrunk Call Rates ↗
- GoTrunk support-ticket workflow ↗
- Asterisk migration from chan_sip to res_pjsip ↗
- FreePBX 17 chan_sip-to-PJSIP conversion guidance ↗
- DIDWW inbound SIP routing methods ↗
- DIDWW create an inbound SIP trunk ↗
- DIDWW inbound SIP connectivity ↗
- DIDWW SIP connectivity reference ↗
- DIDWW registration history ↗
- DIDWW inbound registration credentials ↗
- DIDWW outbound trunks ↗
- DIDWW outbound authentication and security ↗
- DIDWW outbound SIP information ↗
- DIDWW Caller ID and CNAM OUT ↗
- DIDWW service failover and load balancing ↗
- DIDWW inbound call logs ↗
- DIDWW emergency calling on outbound trunks ↗
- Exotel SIP Trunking overview ↗
- Exotel SIP Trunking quickstart ↗
- Exotel call directions and routing modes ↗
- Exotel Dynamic SIP Trunking API ↗
- Exotel developer network and firewall guidance ↗
- Exotel SIP errors and troubleshooting ↗
- Exotel Connect Applet setup for inbound SIP ↗
- Exotel Dynamic SIP Trunking overview ↗
- Exotel SIP Trunking TCP India ↗
- Exotel SIP Trunking TLS India ↗
- Exotel Network and Firewall Configuration ↗
- Exotel view and manage a trunk ↗
- Voximplant SIP calls and registrations ↗
- Voximplant routing rules ↗
- Voximplant applications ↗
- Voximplant CallEvents reference ↗
- Voximplant AppEvents reference ↗
- Voximplant SIPRegistration Management API ↗
- Voximplant VoxEngine limits ↗
- Colt SIP Trunking data sheet ↗
- Colt SIP Trunking External Technical Guide, version 2.1 ↗
- Colt: how to access your voice applications ↗
- Colt SIP Trunking support catalogue ↗
- Colt Voice Product News ↗
- Colt CLI Presentation archive ↗
- Colt SIP Trunking product page ↗
- Colt Companion service assurance ↗
- Gamma SIP Trunks and Call Management ↗
- Gamma SIP Trunking user support and training ↗
- Gamma help and support ↗
- Gamma service status ↗
- Gamma codes of practice ↗
- Gamma Business Communications Code of Practice ↗
- Gamma disaster-recovery planning article ↗
- Gamma Inbound Call Routing user support and training ↗
- Bandwidth SIP Registrar setup ↗
- Bandwidth Vapi SIP integration ↗
- Bandwidth telephone-number options and features ↗
- Bandwidth voice and E911 IP whitelist ↗
- Bandwidth moving phone numbers ↗
- Bandwidth global SIP trunking ↗
- Commio originating ANI and jurisdiction ↗
- Commio number configuration ↗
- Commio porting guide and best practices ↗
- Commio elastic SIP trunking ↗
- LES.NET voice and SIP trunking ↗
- LES.NET customer portal and public service details ↗
- LES.NET service catalogue ↗
- LES.NET local DID service ↗
- LES.NET outbound SIP termination ↗
- LES.NET outbound rate directory ↗
- LES.NET company and currency information ↗
- LES.NET contact and support ↗
- Wavix business SIP trunk ↗
- Wavix SIP trunk FAQ ↗
- Wavix create-a-SIP-trunk guide ↗
- Wavix SIP Trunks API overview ↗
- Wavix 3CX configuration guide ↗
- Wavix Numbers API overview ↗
- Wavix phone-number record reference ↗
- Wavix call-detail-record guide ↗
- Allstream SIP Trunking Quick Start Guide ↗
- Allstream SIP Portal Overview — Native SIP and PRI-SIP ↗
- Allstream SIP Portal Overview — SIP Extreme and SIP Gateway ↗
- Allstream advisory for 911 access using VoIP services in Canada ↗
- babyTEL rebrands as Cloudli Communications ↗
- Cloudli Support — How do I get my IP-PBX or SIP device registered? ↗
- Cloudli Support — Firewall Considerations ↗
- Cloudli Support — Set up a backup number for an outage ↗
- Cloudli 911 Service Information ↗
- Orange Business — Business Talk and Contact Center Access service documents ↗
- Orange Business assistance — Manage Business Talk IP sites ↗
- Orange Business — Business Talk and BTIP Patton SmartNode eSBC configuration guide ↗
- Orange Business — Business Talk Microsoft Teams Direct Routing guide ↗
- Orange Business — Business Talk Cisco CUCM and Webex Calling guide ↗
- Orange Business — Why cloud is the way forward for enterprise voice ↗
- Vodafone UK — SIP trunking ↗
- Vodafone — Converged Hybrid/Evolved Voice Service Specific Terms v1.4 ↗
- Vodafone — Converged Hybrid Voice data sheet ↗
- Vodafone — Tiered Support Services brochure ↗
- Vodafone storm Service Specific Terms v2.3 ↗
- Swisscom — Enterprise SIP for your private branch exchange ↗
- Swisscom — Enterprise SIP factsheet ↗
- Swisscom — Enterprise SIP compatibility list, July 2026 ↗
- Swisscom — Enterprise Connect getting started ↗
- Swisscom — Enterprise Connect order company services ↗
- Swisscom — Enterprise Connect own-gateway configuration ↗
- Sunrise — Business Voice SIP ↗
- Sunrise — On-premises and hybrid PBX portfolio ↗
- Sunrise — SIP Trunk technical flyer, August 2018 ↗
- Sunrise — Business voice direct flyer, March 2017 ↗
- Sunrise — Business Voice for Microsoft Teams factsheet, June 2021 ↗
- Sunrise — Business support contact ↗
- Proximus — Business Trunking product overview ↗
- Proximus — Business Trunking contractual service description, 15 January 2024 ↗
- Proximus — Professional-customer legal documents ↗
- Proximus — Customer service for large organisations ↗
- Crazytel — Creating a Register Based SIP Trunk, updated 26 October 2026 ↗
- Crazytel — CGNAT setup recommendations, updated 26 October 2026 ↗
- Crazytel — SRTP compatibility, updated 26 October 2026 ↗
- Crazytel — Custom outbound proxy settings, updated 26 October 2026 ↗
- Crazytel — No sound on calls, 30 December 2025 ↗
- Crazytel — Real-time network status ↗
- MaxoTel — 3CX SIP Trunking, last modified 24 May 2023 ↗
- MaxoTel — Portal Guide: PBX Extensions and SIP Trunks, last modified 11 August 2023 ↗
- MaxoTel — 3CX Suddenly Loses SIP Trunk Registration, last modified 21 April 2020 ↗
- MaxoTel — SIP ALG, last modified 19 June 2019 ↗
- MaxoTel — NAT Issues, last modified 20 April 2021 ↗
- MaxoTel — Which codecs are supported?, last modified 19 April 2021 ↗
- MaxoTel — What VoIP Protocols are supported? ↗
- MaxoTel — Outage Communications Policy ↗
- Aussie Broadband — SIP Trunks ↗
- Aussie Broadband — SIP trunks Critical Information Summary, 1 July 2026 ↗
- Aussie Broadband — BYO VoIP settings, updated 14 September 2026 ↗
- Aussie Broadband — Integrated Public Number Database and emergency-service address, updated 26 August 2025 ↗
- Aussie Broadband — phone-number port timing, updated 5 May 2023 ↗
- Aussie Broadband — port forwarding and CGNAT, updated 13 August 2023 ↗
- Aussie Broadband — current, upcoming and past outages ↗
- Aussie Broadband — report a fault in MyAussie, updated 26 February 2024 ↗
- Aussie Broadband — business support and service-delivery contacts ↗
- Symbio — Enterprise SIP Trunking ↗
- Symbio — Australia voice network and carrier services ↗
- Symbio — phone numbers and porting ↗
- Symbio — SIP TLS and SRTP announcement, 24 January 2024 ↗
- Symbio — dual-carrier voice redundancy, 11 November 2025 ↗
- Symbio — security and trust ↗
- Symbio — Major Outage Register ↗
- Symbio — 24x7 Global Service Assurance, 19 December 2023 ↗
- Telstra Enterprise — SIP Connect ↗
- Telstra — Our Customer Terms, SIP Connect section, changed 3 June 2024 ↗
- Telstra — SIP Connect Customer Integration Guide ↗
- Telstra Enterprise — SIP Connect support and accredited CPE ↗
- Telstra Enterprise — Business Resumption Service + ↗
- Telstra — Business SIP Critical Information Summary ↗
- Optus Wholesale — Evolve Voice SIP trunking ↗
- Optus — Evolve Service Description, 1 November 2025 ↗
- Optus Business — Standard Form of Agreement, Evolve ↗
- Optus Business — Standard Form of Agreement ↗
- Optus — Evolve Voice factsheet (historical 2017 context) ↗
- Optus — SIP Trunking technical paper (historical context) ↗
- One NZ — SIP Advanced ↗
- One NZ — SIP Advanced Service Description ↗
- One NZ — Smart SIP ↗
- One NZ — Smart SIP Service Description ↗
- One NZ — Terms, conditions and service descriptions ↗
- One NZ — Metro Access Service Description ↗
- One NZ — About Emergency Services on 111 ↗
- 2degrees Business — SIP Trunks ↗
- 2degrees — Terms and conditions index ↗
- 2degrees — What happens in a power cut ↗
- 2degrees — Vulnerable consumers and calling 111 during a power outage ↗
- 2degrees — Privacy policy ↗
- Vocus — SIP Voice ↗
- Vocus — SIP Trunks data sheet ↗
- Vocus — SIP Voice Connect Service Schedule, 27 April 2026 ↗
- Vocus — Unified Communications Service Schedule, Australia Direct, 27 April 2026 ↗
- Vocus Support — call forwarding and diversions in BroadSoft ↗
- Vocus — Service Level Agreement ↗
- Superloop — Business VoIP and SIP ↗
- Superloop — Voice specifications data sheet ↗
- Superloop — Business Voice Service Schedule, 10 March 2026 ↗
- Superloop — business support contact ↗
- Superloop — outages and service updates ↗
- Enreach — SIP Trunks for businesses ↗
- Enreach — SIP Trunks for resellers ↗
- Enreach — PBX Trunks platform for service providers ↗
- Enreach Service Center — Enreach Trunk (DE), updated 9 April 2026 ↗
- Enreach Swyx 15 — creating a SIP trunk group ↗
- Enreach Swyx 15 — creating a SIP trunk ↗
- Enreach Control Center 15 — forwarding and number substitution ↗
- Enreach Swyx 15 — emergency call detection ↗
- Enreach Service Center — Enreach Trunk FAQ and nomadic-use boundary ↗
- MetTel — SIP Trunking datasheet, © 2025 ↗
- MetTel — VoIP and SIP Trunking terms, including 911 and traffic-policy boundaries ↗
- MetTel — support, activation, ticket and advanced-services contacts ↗
- MetTel — General Terms applicable to MetTel products ↗
- MetTel — Tariffs and product guides ↗
- NUSO — SIP Trunking product page ↗
- NUSO — Platform Services ↗
- NUSO — HIPAA compliance and SIP Trunking security responsibilities ↗
- NUSO — customer support contacts ↗
- NUSO — technical support and network-status path ↗
- NUSO — policies, programme documents and customer-service contact ↗
- Telesystem — SIP Trunks product page ↗
- Telesystem — SIP Trunk Administration for Tenant Admins ↗
- Telesystem — SIP Trunk DID Forwarding quick reference ↗
- Telesystem — E911 compliance guidance ↗
- Telesystem — network status and support paths ↗
- Telesystem — account support and escalation contacts ↗
- TPx — UCx SmartVoice SIP Trunking product page ↗
- TPx — UCx SmartVoice SIP Trunking brochure ↗
- TPx — SmartVoice PRI, CAS and SIP DID Features Guide ↗
- TPx — Introduction to Direct Trunk Overflow ↗
- TPx — 911 for SmartVoice and iPBX SIP Trunking Addendum ↗
- TPx — customer support and escalation paths ↗
- TPx — systems performance status ↗
- Lingo — Cloud SIP and PRI solutions ↗
- Lingo Knowledge Base — Cloud PRI and SIP Trunking ↗
- Lingo — Partner Product Guide 2024 ↗
- Lingo — E911 and California E911 Notice ↗
- Lingo — support resources ↗
- Lingo — service status ↗
- Voyant — communications products and SIP Trunking ↗
- Voyant — Master Services Agreement ↗
- Voyant — SIP Trunking terms and conditions ↗
- Voyant — VoIP 911 information ↗
- Voyant — Canadian 9-1-1 service notification ↗
- Sinch Community — SIP Trunk E911 bulk import in CAP, August 2024 ↗
- Sinch Community — Voyant/ANPI SIP Trunking STIR/SHAKEN caller-ID changes ↗
- Voyant — support contacts ↗
- Voyant — service status ↗
- Windstream Enterprise — SIP Trunking with Dynamic IP ↗
- Windstream Enterprise — Voice & Communications ↗
- Windstream Enterprise — Direct Trunk Overflow fact sheet ↗
- Windstream — Standard Agreement for Service Terms and Conditions ↗
- Windstream Enterprise — Dynamic IP Standard Terms and Conditions ↗
- Windstream Enterprise — Customer Responsibilities Guide ↗
- Windstream Enterprise — Data Products SLA and QoS classes ↗
- Windstream Enterprise / Uniti Solutions — U Connect portal and support ↗
- Granite — VoIP & Cloud Phone Systems ↗
- Granite — SIP Trunking brief (legacy, date-scoped) ↗
- Granite — Legal & Policy ↗
- Granite — General Terms of Service (May 2026) ↗
- Granite — VoIP Services Additional Terms and Conditions of Service ↗
- Granite — VoIP Services Service Level Agreement ↗
- Granite — Canadian VoIP 911 English ↗
- Granite — Resources and customer portals ↗
- FirstLight — Voice and SIP Trunking ↗
- FirstLight — SIP Trunk info sheet ↗
- FirstLight — Service Schedule A, Voice Services, version 4 (August 21, 2026) ↗
- FirstLight — Standard Terms and Conditions, version 5 (June 16, 2025) ↗
- FirstLight — E911 Acknowledgement, version January 14, 2019 ↗
- FirstLight — Legal, Regulatory, Terms and Conditions ↗
- FirstLight — Customer Support ↗
- FirstLight — Prevent Long Distance Fraud and PBX Hacking ↗