By Sagar Shankaran, Founder of CallSphere
Single-carrier dependency is existential risk for real-time AI voice. Here is the production multi-carrier failover architecture using SIP DNS SRV, OPTIONS pings, and SBC-driven retry that keeps an AI voice agent live during a Twilio outage.
Key takeaways
A dropped voice call cannot be retried. An HTTP 502 you retry; a silent AI agent at minute 47 of a healthcare intake is brand damage. Multi-carrier failover for AI voice in 2026 is not a luxury - it is the only architecture that survives a real Twilio, Bandwidth, or Telnyx outage. The pattern: at least two SIP trunks, geo-redundant SBCs, OPTIONS-based health monitoring, and sub-30-second cutover.
The 2024-2025 cycle had three high-profile carrier outages that took down voice for hours. Single-carrier deployments lost every active call and every queued call. Multi-carrier deployments lost the active calls on the failed trunk but kept everything else running.
The standard pattern in 2026 has four layers. First, two or more SIP trunk providers (Twilio + Bandwidth, Telnyx + Sinch, etc.) terminating to your SBC. Second, SBCs in at least two cloud regions with cross-region SIP signaling. Third, SIP DNS SRV records pointing to multiple SBCs with weighted priority. Fourth, OPTIONS pings every 5 to 30 seconds against each trunk to detect failures preemptively, and a control plane that can shift primary within seconds.
The failover trigger is layered: OPTIONS timeout flips the trunk to standby; sustained 5xx error rates flip it to failed; an explicit operator action overrides everything. Active calls on the failed trunk drop (no fix for that without RTP redundancy); new calls land on the standby within seconds.
Hear it before you finish reading
Talk to a live CallSphere AI voice agent in your browser — 60 seconds, no signup.
flowchart TD
A[PSTN] --> B[Twilio SIP Trunk]
A --> C[Bandwidth SIP Trunk]
B --> D[SBC US-East]
B --> E[SBC US-West]
C --> D
C --> E
D --> F[AI Voice Bridge]
E --> F
F --> G[OpenAI Realtime]
H[OPTIONS pings] -.-> B
H -.-> C
H -.-> D
H -.-> E
I[Control Plane] -->|Shift primary| H
OPTIONS pings every 5 to 15 seconds in production; faster cycles cost CPU but cut detection latency. SIP 302 redirect lets the SBC tell the originator to retry on the standby leg without dropping the signaling session.
CallSphere runs Twilio as primary and a secondary carrier (varies by region) as standby across all six verticals. Our /twilio/voice bridge is mirrored at a secondary endpoint that accepts SIP from the standby trunk; both endpoints share a single Postgres state store across our 115+ DB tables, so a call that originates on the primary trunk and routes to the standby endpoint sees the same session state. The control plane (one of our 90+ tools) monitors trunk health every 10 seconds and can shift primary in under 30 seconds. STIR/SHAKEN attestation is preserved across both carriers via the originating-carrier's signing. Healthcare AI tenants on Scale ($1499/mo) get active-active failover by default; Growth ($499/mo) tenants get warm standby. HIPAA + SOC 2 controls cover all SBC traffic and call recordings. The 22% affiliate program credits Scale upgrades.
Can I keep active calls during failover? Generally no. Active RTP streams on a failed trunk drop. Some advanced setups use RTP forking to mirror media to a standby SBC, but the cost and complexity are high and most deployments accept the drop.
Why two SBCs in different regions? A single-region SBC is a single point of failure for the cloud region itself. Cross-region deployment survives an entire AWS or GCP region outage.
Still reading? Stop comparing — try CallSphere live.
CallSphere ships complete AI voice agents per industry — 14 tools for healthcare, 10 agents for real estate, 4 specialists for salons. See how it actually handles a call before you book a demo.
Does multi-carrier hurt MOS scores? Slightly, in pathological cases where the standby carrier has worse routing. In practice the difference is under 0.1 MOS and only matters for very long-haul international.
What about porting numbers across both carriers? Numbers are RespOrg-locked. You can have the number with carrier A and use carrier B as outbound only, or run separate DIDs on each carrier with clever routing. Most setups choose the latter for clarity.
Can CallSphere customers run their own SBC? Yes, on enterprise plans. Most Scale tenants stay on our managed multi-carrier setup; some regulated tenants want their own SBC and we publish the SIP credentials for that.
Start a 14-day trial with managed multi-carrier failover, browse pricing for Scale, or book a demo. Partners earn 22% via the affiliate program; enterprise SBC questions go to contact.
Written by
Sagar Shankaran· Founder, CallSphere
Sagar Shankaran is the founder of CallSphere, where he builds production AI voice and chat agents deployed across healthcare, hospitality, real estate, and home services. He writes about agentic AI, LLM engineering, and shipping voice agents that handle real calls in production.
See how AI voice agents work for your industry. Live demo available -- no signup required.
A founder's guide to the female voice generator landscape: AI female voices, Japanese voices, robot voices, and how CallSphere ships 57+ voices live.
MOS 4.3+ is the band where AI voice feels human. Drop below 3.6 and conversations break. Here is how to measure, improve, and alert on MOS in production AI voice using G.711, Opus, and the underlying packet loss / jitter / latency math.
Your agent's memory, embeddings, and conversation state all live in Postgres. Backups must include vector data and survive a full-region loss. Here's how CallSphere does PITR for 115+ tables.
Where every millisecond goes between caller and AI: PSTN, carrier, STT, LLM, TTS, and back. The component-level targets that ship in 2026 and how to hit them.
Multi-provider failover protects against outages but can drop response quality. The 2026 patterns that preserve both reliability and quality.
Single-region AI voice is one Azure outage from 4 hours of downtime. Real failover crosses cloud boundaries, model providers, and TURN servers, all without dropping a call.
© 2026 CallSphere LLC. All rights reserved.