SIP TRUNKING
Bring your platform. We'll route the calls to it
Already building with ElevenLabs, Vapi, LiveKit Cloud, or any voice AI provider that supports SIP trunking? Connect your stack to Teler and start taking calls.
How it works
Two dashboards. No code in between.
Create your SIP trunk.
Name it, set your domain, and choose your SIP transport (TLS/ TCP/ UDP).
Choose your authentication method.
IP authentication if your platform calls from a fixed address, or credential authentication (username and password) if it doesn’t.
Configure inbound routing.
Point Teler at your platform’s own SIP address. Mirror the same settings on your platform’s side.
Built for SIP-native platforms
No hosting required
Bidirectional on one trunk
Flexible authentication
Built-in encryption
No hosting required
Everything is configured in your Teler dashboard and your platform's own SIP trunk settings. No bridge to deploy, nothing to maintain.
Bidirectional on one trunk
Inbound and outbound calls share a single trunk - no separate setup for each direction.
Flexible authentication
IP authentication or credential authentication, whichever fits your platform's infrastructure.
Built-in encryption
Protect signaling and media with TLS and SRTP whenever your use case requires it.
Works with your favorite tools
Teler connects natively with ElevenLabs, VAPI, LiveKit Cloud, and Bolna - or any standards-compliant SIP system.
What you can build
Build a screening agent for candidate calls
Point an agent you built on VAPI at a Teler trunk, and start taking real candidate calls the same day - no telephony code needed.
Modernize your phone system without rebuilding it
Point your PBX's existing call routing and IVR logic at a Teler trunk for carrier connectivity - none of that logic has to change.
Set different recording rules for different teams
Record sales calls for coaching; skip it for support, per your own policy - two trunks, two recording settings, one Teler account.
Route calls by language
Send Hindi and regional-language calls to Bolna, English calls to ElevenLabs - two platforms underneath.
Keep a backup ready for an outage
Configure a second trunk pointed at a backup platform, so you can manually redirect your number if your primary platform ever goes down.
Keep patient calls separate
Run patient calls on their own trunk with strict retention rules, kept apart from general business calls on a different trunk.
Do I need to write any code for this?
No. Setup is entirely dashboard configuration - your Teler trunk settings and your platform's own SIP trunk settings.
Which platforms have a dedicated setup guide?
ElevenLabs, VAPI, LiveKit Cloud, and Bolna - or any standards-compliant SIP system, which connects using the same trunk configuration principles.
What authentication method should I use?
Credential authentication if your platform's egress IP can change - the case for most cloud platforms. IP authentication only if you've confirmed a fixed, static IP.
What's the difference between a SIP Trunk and a Voice App?
The real difference is who decides what happens on the call. With a Voice App, Teler asks your own server what to do, and you answer with code you host yourself - that's what Media Streaming is built on. With a SIP Trunk, you're connecting to a platform that already knows how to handle the call - ElevenLabs, VAPI, LiveKit, Bolna - so there's no call-handling code to write. You can set up both on the same account, for different use cases.
What's the difference between SIP Trunking and Media Streaming?
SIP Trunking connects a platform that already speaks SIP - no code required. Media Streaming is for building a custom agent from raw audio, which means hosting a small bridge yourself.
Can I set up more than one trunk?
Yes - one per platform or use case, each with its own number and configuration.
Connect your AI platform to
real phone calls today
No code needed - just configure your Teler trunk and match the same settings on your platform.