SIP Trunk
Open for Bandwidth
Point a Bandwidth SIP trunk or Voice API application at Open and the AI picks up — on a Tier-1 US carrier with E911 done right.
- Setup time
- Under 15 minutes
- Auth
- IP allowlist or digest credentials
- Directions
- Inbound · Outbound · Call transfer
- Pricing
- Included with Open
01 — Overview
Can I run an AI phone agent on my Bandwidth SIP trunk?
Yes. Bandwidth stays your Tier-1 carrier; Open is a SIP endpoint your Bandwidth Voice API or Duet trunk routes calls to. Numbers, E911 records, and CDRs don't move.
Bandwidth remains the carrier of record — DIDs, toll-frees, E911 provisioning, regulatory compliance, and 911 routing stay exactly where they are. Open is a SIP destination your Bandwidth Voice API application or SIP trunk forwards calls to. When a call should be handled by AI, Bandwidth sends the INVITE to Open, the AI picks up, and the rest of the conversation runs over the same SIP path.
For inbound, the cleanest path is a Bandwidth Voice API application that returns a BXML <Forward> (or <Transfer><SipUri>) to the Open SIP URI on the calls you want AI'd. If you're on Bandwidth Duet (the SIP Trunking product), you point the trunk's outbound termination at Open instead — equivalent result, less code.
For outbound, Open opens a SIP session against your Bandwidth SIP termination URI using IP allowlisting (Bandwidth's preferred auth) or digest credentials. Calls land in your Bandwidth CDRs the same way as human-dialed calls do, presenting whatever caller IDs you've approved.
What the AI does on the call: it listens, reasons over your knowledge base and connected tools, and acts — looking up an order, creating a ticket, scheduling a callback, sending a payment link, or warm-transferring to a human via SIP REFER with the live transcript and detected intent attached. Every call is recorded and trace-logged.
E911 stays where it should: on Bandwidth. The AI won't initiate emergency calls itself; if a customer asks for emergency help, the AI either passes the call straight through to your existing 911 path or warm-transfers to a human, depending on how you've configured the agent.
What stays the same on Bandwidth
Bandwidth numbers and E911
DIDs and E911 provisioning don't move. No porting, no carrier change.
BXML applications
Voice API applications keep working. Open plugs in as a `<Forward>` or `<Transfer>` target.
Approved caller IDs
Outbound presents Bandwidth-approved caller IDs.
CDRs and analytics
Every call leg still lands in Bandwidth Insights.
What's new with Open
A SIP destination on Bandwidth
Open's SIP URI becomes a `<Forward>` target in BXML or a termination URI on Duet.
AI handles the conversation
The AI greets, listens, calls your tools, and replies in natural speech.
Transfers carry context
Human agents receive the live transcript on SIP REFER.
Pricing model
You pay Open per resolved conversation. Carrier minutes stay invoiced by Bandwidth.
02 — Why this works
The native Bandwidth experience
Tier-1 reach kept intact
Bandwidth's US carrier network keeps owning the PSTN leg. Open joins at SIP — no proxy, no extra hops.
E911 stays on Bandwidth
Emergency calls keep using your existing E911 records and routing. AI can pass through or warm-transfer when needed.
BXML + Duet, both work
Whether you script in BXML Voice API or run on Duet SIP Trunking, Open slots in as a destination either way.
IP allowlisting native
Open supports Bandwidth's preferred IP-based auth out of the box, with digest credentials as an alternative.
03 — Setup guide
Wire up Bandwidth in under 15 minutes
Two trunks — one inbound, one outbound. Both configurable from Settings → SIP in the Open dashboard.
- 1
Open Settings → SIP
Open the inbound trunk configuration.
- 2
Pick a SIP region
Choose Global or US (Bandwidth is US-centric).
- 3
Copy the SIP credentials
Grab the SIP endpoint, username, and password.
- 4
Return BXML with a Forward action
In your Bandwidth Voice API application, return `<Bxml><Forward to="sip:open-uri" /></Bxml>` (or `<Transfer><SipUri>...</SipUri></Transfer>`) for calls you want AI to answer.
- 5
Or configure a Duet termination route
In the Bandwidth Dashboard, set Open's SIP endpoint as the outbound termination URI for the inbound DIDs you want AI'd.
- 6
Add your Bandwidth numbers to Open
Register each Bandwidth DID under Phone Number (DID).
- 7
Assign numbers to an AI agent
Channels → Phone → Agents → assign DIDs.
- 8
Place a test call
Dial a Bandwidth number and confirm Open answers.
04 — Configuration
Settings → SIP, at a glance
A real inbound trunk for Bandwidth looks something like this. Yours are generated when you open Settings → SIP.
Inbound trunk · Bandwidth
Sample
- SIP endpoint
- sip.us.opencx.comUS region
- Transport
- TLSrecommended
- Auth
- IP allowlistpreferred
- BXML element
- <Forward to="sip:..." />
- E911
- On Bandwidthno change
05 — Security
Encrypted, audited, refundable
SIP over TLS for signaling, SRTP for media. Every call is logged with full reasoning traces. SOC 2 Type II, GDPR-aligned, HIPAA- and PCI-ready. Backed by the Open $2M Refund Guarantee.
06 — FAQ