Vapi connects to carriers over bring-your-own SIP. Point it at a Vobiz trunk and your assistants place and answer calls on numbers you own in India and 130+ countries, with the transferred leg staying on your own carrier.
You can connect a Vobiz number to a Vapi agent using Vapi's bring-your-own SIP trunk support, and it carries calls in both directions. Outbound is entirely dashboard work. Inbound needs one API call to read your Vapi trunk ID, which the Vapi dashboard does not display.
Vapi is API-native and carrier-agnostic. That is a deliberate design choice: it orchestrates the assistant and leaves telephony to whoever you bring. This choice depends on the market your agent has to operate in, the telecom rules governing the routing, and how much control you need when the agent has to transfer to a human.
Vobiz is the carrier you bring. Same assistant, same dashboard, on inventory and routing built for 130 markets that you can call into.
Everything below runs on standard SIP. Nothing here needs Vapi to ship anything new.
140-series, 1600-series, mobile and toll-free Indian numbers, issued under India's telecom rules, imported into Vapi as bring-your-own SIP trunk numbers.
Add a SIP trunk credential in Vapi using your Vobiz SIP domain, username and password. Import your number. Place the call. No code at any point.
Calls to your Vobiz number reach your Vapi assistant over a SIP trunk you configure on both sides. One inbound trunk in Vobiz, one in Vapi, and the number linked to both.
Vapi's Transfer Call tool accepts a SIP destination, so a handoff to a human can route out through your Vobiz trunk rather than an unrelated third-party leg.
Follow the click-through guide, or run the identical setup as REST calls when you would rather keep configuration in code and version control.
Vapi keeps transcripts and call logs for what was said. Vobiz writes a call detail record with 43 fields, including MOS, jitter, packet loss and hangup attribution, for how it was carried.
Outbound and inbound are set up independently. Do one, both, or start with outbound to prove the trunk works.
One thing to keep an eye on. Vobiz sends inbound SIP from any of its signaling IPs, so every one of them needs a gateway entry in Vapi to whitelist them. The list can change, so check it against the docs when you set up and when you troubleshoot.
Every screen, every field, the current signaling IP list and a video walkthrough are in the Vobiz docs.
Read the integration guideNot today. You connect the two through Vapi's bring-your-own SIP trunk support, which is how Vapi handles any carrier it does not integrate directly, and it carries both inbound and outbound calls.
Yes, over a Vobiz SIP trunk. Vobiz issues Indian 140-series, 1600-series, mobile and toll-free numbers, and you import them into Vapi as bring-your-own SIP trunk numbers rather than buying them inside Vapi.
Outbound is entirely dashboard work across both consoles. Inbound needs one API call to Vapi to read your trunk ID, because that value is not exposed in the Vapi dashboard. Everything after it is dashboard again.
Because Vobiz sends inbound SIP from any of its signaling IPs, not a single fixed one. Each needs its own gateway entry in Vapi, or calls arriving from an unlisted IP are rejected. The docs carry the current list.
Yes. Attach Vapi's Transfer Call tool and give it a destination: a plain phone number for a blind PSTN transfer, or a SIP URI on your Vobiz trunk domain to route the transferred leg out over your own trunk.
There is a separate API guide covering the same setup as REST calls, for teams keeping telephony configuration in version control.
Create a Vobiz account, add a trunk and a number, and place a call from your existing Vapi assistant. Inbound can follow once you have heard it work.
Vapi is a voice AI platform for building and deploying conversational agents. Vobiz is not affiliated with Vapi; this integration uses Vapi's public bring-your-own SIP trunk support.
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.