You need: an Unpod number on a Bridge, and an ElevenLabs account with a
Conversational AI agent (the agent needs a First Message and a selected voice).
Part 1 - Connect the number in Unpod
Connect your number
In Telephony, select your number (shown as Not Linked) and click Connect
to set up its SIP trunk.

Point the trunk at ElevenLabs (inbound)
In the trunk panel, set the Trunk Origin Endpoint Details to ElevenLabs’ SIP host:
- SIP URI / address -
sip:sip.rtc.elevenlabs.io:5060;transport=tcp(or port5061withtransport=tlsfor TLS). - Port
5060(TCP) /5061(TLS). - Allowed IPs / CIDR - optional source allow-list.
Calls Unpod sends to ElevenLabs use the form
sip:<your-number>@sip.rtc.elevenlabs.io:5060 (identifier + domain).Part 2 - Import the number into ElevenLabs
In the ElevenLabs Agents dashboard, open the Phone Numbers section.Basic configuration
In the Import SIP Trunk panel set:
- Label - a descriptive name.
- Phone Number - your Unpod number in E.164 (e.g.
+918071539111), or a SIP extension / identifier.

Inbound configuration
Under Inbound Configuration (forwards calls to the ElevenLabs SIP server):
- Media Encryption -
Allowed(useRequiredwith TLS for production). - Allowed Numbers (optional) - leave empty to allow all.
- Allowed Source IP Addresses (optional) -
0.0.0.0/0to allow all (TCP/TLS only; restrict in production).
Outbound trunk - point back at Unpod
So ElevenLabs can send calls to Unpod, enter the Unpod origin-endpoint values from Part 1:
- Address - your Unpod address, hostname only, no
sip:prefix (e.g.sip-lb1.unpod.tel). - Transport Type -
TCP(orTLS). - Media Encryption -
Allowed(useRequiredwith TLS for production). - SIP Trunk Username / SIP Trunk Password - the Unpod Username / Password.
Part 3 - Attach your agent
Attach the inbound agent
Open the imported number and attach your Conversational AI agent from the
dropdown. Incoming calls now route through ElevenLabs to that agent.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
SIP 408 timeout | Wrong trunk address or transport | Confirm the Unpod address and TCP transport on both sides |
| Authentication failed | Wrong / mis-cased credentials | Re-copy the Username/Password from the Unpod origin endpoint (case-sensitive) |
| Call connects, silent | Agent missing First Message or voice | Set a First Message and a valid voice on the agent |
| Inbound not arriving | Unpod trunk SIP URI wrong | Set it to sip:sip.rtc.elevenlabs.io:5060 (TCP) |
| Number not reachable | Config not published | Click Publish in the Unpod Studio |
Do it with code
Same flow over the REST API.
All platforms
Back to the integrations overview.

