Indian numbers on a global platform
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.
Voice AI platform integration
Vapi assistants.
Vobiz numbers.
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.
- 130+
- countries where you can provision numbers
- 190
- countries reachable on outbound
- 2
- ways to set it up: dashboard or REST API
Before you start
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.
Why this pairing
A global agent needs a local number
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.
Vapi owns
- Assistant design, prompts and first message
- Choice of STT, LLM and TTS providers
- Turn-taking, interruptions and tool calls
- The Transfer Call tool and its destinations
- Call logs, transcripts and analytics
- Squads, workflows and orchestration
Vobiz owns
- Phone numbers and instant provisioning
- SIP trunking, inbound and outbound
- Media quality, noise and echo handling
- Call detail records and quality telemetry
- India KYC and telecom compliance
- Sub-accounts for teams and environments
What you get
Your own trunk under someone else's agent
Everything below runs on standard SIP. Nothing here needs Vapi to ship anything new.
Outbound in four dashboard steps
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.
Inbound routed to your assistant
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.
Transfers stay on your carrier
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.
Dashboard or API, same result
Follow the click-through guide, or run the identical setup as REST calls when you would rather keep configuration in code and version control.
Telemetry from both layers
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.
How it works
Two directions, configured separately
Outbound and inbound are set up independently. Do one, both, or start with outbound to prove the trunk works.
Outbound
Dashboard only- 01
In Vapi, add a SIP trunk credential with your Vobiz SIP domain as the gateway URL, then enable outbound calling.
- 02
Take the SIP domain, username and password from your outbound trunk in the Vobiz Console.
- 03
Import your Vobiz number into Vapi as a bring-your-own SIP trunk number, against that credential.
- 04
Place a call, choosing your assistant and the imported number as caller ID.
Inbound
One API call- 01
Create an inbound SIP trunk in Vapi with one gateway per Vobiz SIP signaling IP, each on UDP port 5060.
- 02
Read the trunk ID from Vapi's credential endpoint. It is not shown in the dashboard.
- 03
Create an inbound trunk in the Vobiz Console pointing at your Vapi trunk URI, and link your number to it.
- 04
Import the same number in Vapi against the inbound credential.
- 05
Assign the answering assistant, then dial the number from any phone to test.
Every screen, every field, the current signaling IP list and a video walkthrough are in the Vobiz docs.
Read the integration guide
Get started
Prove the trunk with one outbound call
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.
FAQ
Straight answers
- Not 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.
CRM and helpdesk integrations: Salesforce · ServiceNow · ClickUp · Pipedrive · Expedify · HubSpot · Freshdesk · OpenAI Realtime · LiveKit · Grok Voice · Gemini Live · Pipecat · Ultravox · Smallest AI · Sarvam
Voice AI platforms on Vobiz: Bolna · Vapi · Retell AI · LiveKit · ElevenLabs · See all integrations
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.