Rapida ships Vobiz as a built-in telephony provider. Save two credentials, pick a caller ID, and your assistants place and answer calls on numbers in 130+ countries, reaching 190, with audio streaming over a WebSocket rather than a trunk you have to build.
Rapida is open source and runs either on their managed platform or on a deployment of your own, and the Vobiz provider is the same in both. Outbound is configured entirely inside Rapida: save the credential, attach telephony to an assistant, dial. Inbound needs one more thing — a Voice Application in the Vobiz Console pointed at the assistant's inbound webhook, with your number attached to it. Both are dashboard work.
Rapida is built for teams who do not want a platform sitting between them and production: bring your own speech, language and voice models, route between them without touching application code, self-host when a client or a compliance review demands it, and deliver under your own brand with each client in an isolated workspace.
A platform built on that principle should not force a rented phone number either. Vobiz is the carrier relationship you hold directly, with inventory in 130+ countries and outbound reach to 190, and Rapida already has a provider card for it.
Vobiz is already on Rapida's integrations page. Setting up the credential takes a name and two values.
Open your deployment's integrations page, find the Vobiz card, and click Setup Credential. Give it a name, paste your Auth ID and Auth Token, and the card returns a green check and Connected once Rapida verifies them.
Outbound calls are created through the Vobiz REST API and inbound arrives via a Voice Application, with live audio running over a bidirectional WebSocket. There is no SIP trunk to stand up, no termination URI, and no gateway list to keep in sync.
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. Pick any active number in the account as the assistant's caller ID.
Rapida credentials are named, so an agency running client workspaces can point each one at its own Vobiz sub-account: separate number pools, separate billing, separate records. Caller ID has to belong to the same account as the credential, which keeps the separation honest.
Outbound is a provider, a credential and a caller ID inside the assistant's phone deployment. Inbound is a Voice Application pointed at the assistant's webhook with your number attached. Add the call-status webhook as the hangup URL and Rapida sees completion events too.
Rapida holds session traces, transcripts, webhook logs and live call monitoring for what was said. Vobiz writes a call detail record with 43 fields, including MOS, jitter, packet loss and hangup attribution, for how the call was carried.
Outbound lives entirely in Rapida. Inbound adds one application in the Vobiz Console.
Three things to get right. The inbound answer URL carries an API key as a query parameter — treat the whole URL as a secret and keep it out of screenshots, tickets, logs and source control. Caller ID has to belong to the same Vobiz account as the selected credential; if a newly added credential or number is not listed yet, use the refresh control before assuming something is broken. When you are attaching a specific number, leave the default number app, public URI and default endpoint app options switched off.
Every field, every screen, the full troubleshooting table and the streaming reference are in the Vobiz docs.
Read the integration guideYes. Vobiz has its own provider card on Rapida's integrations page. Click Setup Credential, enter your Auth ID and Auth Token, and the card shows Connected. Nothing needs to be built on either side beyond that.
No. This is a WebSocket integration. Outbound calls are created through the Vobiz REST API, inbound arrives through a Vobiz Voice Application, and live audio runs over a bidirectional WebSocket. There are no trunk credentials, no termination URI and no gateway IPs to configure.
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.
Yes. Rapida runs managed or self-hosted and the Vobiz provider is the same either way. On a self-hosted deployment, use your own domain throughout — the integrations page and the inbound webhook URL both live on it.
Yes, and it is worth doing. Rapida credentials are named, so an agency can configure one per client workspace and point each at a separate Vobiz sub-account with its own numbers, billing and records. The caller ID must come from the same account as the credential it is paired with.
Yes, one thing. Outbound is entirely inside Rapida, but inbound needs a Voice Application whose answer URL is the assistant's inbound webhook, with your number attached to it. It is a single screen and no code.
Create a Vobiz account, add a number and some balance, then open the Vobiz card on your Rapida deployment. Outbound works before you touch inbound.
Rapida AI is an open-source voice AI platform for building and operating voice assistants, available managed or self-hosted. Rapida AI and Vobiz are independent companies; Vobiz is available as a built-in telephony provider in Rapida.
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.