Import a Vobiz number into ElevenLabs as a SIP trunk number and your agents call out and pick up on real phone lines in 130+ countries, reaching 190. One form for outbound, one SIP URI for inbound, and a carrier underneath that is built to deliver the voice you chose intact.
ElevenLabs does not currently ship a Vobiz-specific provider. You connect the two through its Import from SIP Trunk path, which is how ElevenLabs takes a number from any carrier, and it carries calls in both directions. Both are dashboard work, with a REST API route available for the same setup. One detail to carry with you: the transport is TCP on both sides, not the UDP that SIP defaults to elsewhere.
ElevenLabs exists because how a voice sounds matters. Teams choose it for expressive speech across 70+ languages, and then spend real time picking a voice, tuning a first message and testing how the agent handles being interrupted. All of that work is decided in the last few hundred milliseconds, on the phone network, where jitter, packet loss and a bad codec path can make an excellent voice sound cheap.
That last stretch is the part Vobiz owns. Numbers in 130+ countries, routing that satisfies the rules of the markets you call into, and per-call quality data so that when something does sound wrong you can point at the reason.
Standard SIP on both sides. Nothing here waits on ElevenLabs shipping anything new.
In ElevenLabs, import a number from a SIP trunk, label it, and fill four fields: transport TCP, your Vobiz SIP address, and the trunk username and password from your console. Save, pick an agent, and place the call.
Point your Vobiz trunk at the ElevenLabs SIP endpoint over TCP, import the same number on the ElevenLabs side, and attach it to the agent that should answer. No webhook, no answer URL, no server of yours in the call path.
Local, mobile and toll-free inventory across 130+ countries, with outbound reach to 190, including regulated formats where a market demands them — India's 140-series and 1600-series among them. Buy the number, import it, keep it.
Noise and echo handling on the media path, and a call detail record with 43 fields per call — MOS, jitter, packet loss, hangup attribution. ElevenLabs tells you what the agent said; Vobiz tells you how it sounded getting there, so “that call was rough” becomes a diagnosis rather than an argument.
The same number handles inbound and outbound. Over the API, a single import call sets both flags at once, so there is no second registration and no separate inbound number to manage.
Click through it once to prove the path works, then express the identical configuration as REST calls when you are running campaigns, triggering calls from your own application, or keeping telephony config in version control.
Do outbound first to prove the trunk. Inbound is a second pass over the same number.
Three things to get right. Transport is TCP at both ends — a 408 timeout almost always means the SIP address is wrong, the transport is not TCP, or the trunk is not active. Trunk credentials are case-sensitive, so copy them from the authentication section of your trunk rather than retyping them. And if the call connects but you hear nothing, it is usually the agent rather than the line: check it has a first message set and a valid voice selected, and test that voice in ElevenLabs first.
Every field, every screenshot, the full troubleshooting list and a video walkthrough are in the Vobiz docs.
Read the integration guideNot today. ElevenLabs has a general Import from SIP Trunk path for bringing a number from any carrier, and Vobiz connects through it. It supports inbound and outbound on the same imported number, so nothing is missing for want of a dedicated provider card.
TCP, in both directions. The ElevenLabs SIP endpoint expects it, and the outbound trunk configuration specifies it explicitly. Leaving it on UDP is one of the most common causes of a SIP 408 timeout on this integration.
You can provision numbers in 130+ countries and place outbound calls to 190. Where a market has its own number formats or registration rules, Vobiz issues under them rather than routing around them — India's 140-series and 1600-series numbers, for example, alongside local, mobile and toll-free inventory elsewhere.
No. Both directions can be set up entirely through the ElevenLabs dashboard and the Vobiz Console. A separate API guide covers the same configuration as REST calls, which is the better route for bulk campaigns and calls triggered from your own application.
Yes. The same imported number serves both. Over the API, a single phone-number import sets the inbound and outbound flags together, so there is no second registration to maintain.
Usually not. Silence on an answered call is nearly always agent configuration — no first message, or no valid voice selected. If there is audio but it sounds poor, that is worth checking at the carrier layer: the call detail record carries MOS, jitter and packet loss for exactly this.
Create a Vobiz account, add a number and a trunk, and import it into ElevenLabs. Inbound is a second pass once you have heard the first call work.
ElevenLabs is an AI audio research company whose agents platform is used to build and deploy conversational voice agents. Vobiz is not affiliated with ElevenLabs; this integration uses the platform's SIP trunk import.
Connect 3CX PBX to Vobiz SIP trunking for inbound and outbound calling across 130+ countries - configure a generic SIP trunk in minutes.
Connect an Agora Conversational AI agent to Vobiz SIP trunking - add a Vobiz number to Agora for outbound campaigns and route inbound calls to your agent, including India and 130+ countries.
Bolna ships Vobiz as a built-in telephony provider. Paste two credentials into the Providers screen and your agents place and answer calls on numbers in 130+ countries, reaching 190, with audio streaming rather than a SIP trunk.
We use cookies to run this site and, with your permission, to understand how it's used. Read our Cookie Policy.