CPaaS · Voice API
Open for Telnyx
Point a Telnyx SIP Connection or Call Control application at Open and the AI picks up — on your numbers, on your private IP backbone.
- Setup time
- Under 10 minutes
- Auth
- Digest credentials, FQDN, or IP allowlist
- Directions
- Inbound · Outbound · Call transfer
- Pricing
- Included with Open
01 — Overview
Can I run AI calls on my Telnyx setup?
Yes. Open is a SIP endpoint Telnyx Mission Control can route to like any other SIP Connection — your numbers, billing, and private backbone don't move.
Telnyx stays the carrier of record. Numbers, regulatory bundles, Mission Control routing, and per-second invoicing are all unchanged. Open is a SIP destination your Telnyx SIP Connection or Call Control app sends call legs to. When a call should be handled by AI, Telnyx forwards the INVITE to Open, the AI picks up in under 200ms, and the conversation runs over the same SIP/RTP path your existing trunks already use.
For inbound, the cleanest setup is a Telnyx SIP Connection of type FQDN or IP, configured to send the inbound leg to Open. You add the Open SIP URI as the destination and assign your DIDs to that connection in Mission Control. If you'd rather keep Telnyx Call Control in front, your Call Control webhook can issue a transfer action to the Open SIP URI at the moment you'd hand off — same outcome.
For outbound, Open opens a SIP session against your Telnyx trunk's authentication endpoint using the digest credentials in your SIP Connection. Calls land in your Telnyx CDRs the same way human-dialed calls do, with the caller IDs Telnyx has approved on the trunk. AI-driven outbound campaigns work the same as Telnyx-originated calls.
What the AI does on the call: it listens, reasons over your knowledge base and the tools you've connected (Salesforce, HubSpot, Zendesk, Shopify, Stripe), and acts — looking up orders, creating tickets, scheduling callbacks, sending payment links, or warm-transferring to a human via SIP REFER with the transcript and detected intent attached. Every call is recorded and trace-logged.
Billing stays predictable. Telnyx invoices carrier minutes per-second, exactly like today; Open never marks them up. Open charges per resolved conversation, not per agent or per seat.
What stays the same on Telnyx
Telnyx numbers and bundles
Your DIDs and regulatory bundles stay on Telnyx — no porting, no carrier change.
Mission Control routing
Outbound voice profiles and inbound routing rules continue to govern call flow.
Telnyx private IP backbone
Calls keep traversing the Telnyx network for the carrier leg — Open joins at SIP, not via the public Internet.
CDRs and per-second billing
Every call leg still lands in Telnyx; per-second pricing is unchanged.
What's new with Open
A new SIP Connection target
Open's SIP URI becomes a destination in your Telnyx SIP Connection or a `transfer` target in Call Control.
AI handles the conversation
The AI greets, listens, calls your tools, and replies in natural speech — instead of an IVR or a queued human.
Transfers carry context
When humans take over via SIP REFER, they receive the live transcript and detected intent.
Pricing model
You pay Open per resolved conversation. Carrier minutes stay invoiced by Telnyx.
02 — Why this works
The native Telnyx experience
Native SIP — keep the Telnyx backbone
Open joins as a SIP destination your Telnyx Mission Control routes to. No proxy, no extra hop, no markup on Telnyx minutes.
Bring your own Telnyx numbers
Keep DIDs on Telnyx with their regulatory bundles. Map any number to a specific AI agent in the Open dashboard.
SIP Connections + Call Control, both work
Whether you live in Telnyx Mission Control or programmatic Call Control, Open slots in as a destination.
Multi-region SIP endpoints
Pick US, EU, APAC, or global auto-route to keep call setup latency low wherever your Telnyx numbers terminate.
03 — Setup guide
Wire up Telnyx in under 10 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 in the OpenCX dashboard.
- 2
Pick a SIP region
Choose Global, US, EU, or APAC.
- 3
Copy the SIP credentials
Grab the generated SIP endpoint, username, and password — Telnyx will use these to route inbound calls to Open.
- 4
Create or update a Telnyx SIP Connection
In Mission Control → SIP Connections, create a Connection of type "FQDN" pointing at the Open SIP endpoint. Set authentication to credentials and enter the username/password from step 3.
- 5
Assign your DIDs
In Mission Control → Numbers, attach the SIP Connection to each Telnyx number that should route to this AI agent.
- 6
Add your Telnyx numbers to Open
Under Phone Number (DID) in OpenCX, register each Telnyx number in the format Telnyx sends in the INVITE.
- 7
Assign numbers to an AI agent
Channels → Phone → Agents → select agent → Telephony & Routing → assign DIDs.
- 8
Place a test call
Dial one of the Telnyx numbers and confirm Open answers. The transcript appears in your Open inbox.
04 — Configuration
Settings → SIP, at a glance
A real inbound trunk for Telnyx looks something like this. Yours are generated when you open Settings → SIP.
Inbound trunk · Telnyx
Sample
- SIP endpoint
- sip.us.opencx.comUS region
- Transport
- TLSrecommended
- Username
- open_inbound_tlnx…
- Password
- ••••••••••••••••
- Connection type
- FQDN
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
