Vobiz telephony carrier
Vobiz is the telephone carrier Connect's own lines run on. It supplies the business numbers, delivers inbound calls, places outbound ones, and lets the browser softphone register over secure WebSocket. For realtime calls, a Vobiz number is linked to a SIP trunk whose destination is Connect's LiveKit project. Vobiz carries no SMS, so text messages go through another provider.
What it is#
Vobiz is a cloud telephony provider in India offering numbers, voice APIs with an XML call-control language, SIP trunking and a browser WebRTC SDK.
In Connect, a carrier is a set of capabilities rather than a hard-coded dependency. Vobiz's own words appear only in the adapter, voice_carriers.py. Everything above it asks telephony.can(provider, capability). Twilio, Plivo and Exotel adapters exist on the same terms.
- Category
- Telephony carrier (PSTN, SIP, WebRTC)
- Adapter
backend/app/voice_carriers.py(inbound- and outbound-capable)- Browser registrar
wss://registrar.vobiz.ai:5063, as Vobiz's own SDK uses- Official site
- vobiz.ai
Where Connect uses it#
| Place in Connect | What it does there |
|---|---|
| Business numbers | Each line is a channel_routes row, and the carrier is one of its properties |
| Inbound answer URL | /api/voice/vobiz/incoming: signed requests, verified with a nonce |
| SIP trunk to LiveKit | Realtime-engine lines: origination to the LiveKit project's SIP host |
| Browser softphone | A per-person SIP endpoint registered through JsSIP |
How it connects#
- A caller dials the business number
- Vobiz routes it: to the answer URL (turn-based) or the SIP trunk (realtime)
- Connect verifies the signature and nonce on every webhook
- The call record is written once per provider event (a nonce index stops replay)
- Hang-up and status events close the record
Benefits and limits#
What it gives Connect:
- Indian numbers with local presence for Indian businesses.
- SIP trunking lets Connect hold the call itself with the realtime engine.
- Per-person SIP endpoints mean one softphone can be revoked without affecting others.
Where it stops, and what Connect does about it:
- No SMS on Vobiz. Connect falls back to a configured SMS provider.
- Vobiz's written docs named a WebSocket address that answered nothing. The working registrar came from their SDK. Connect records the working one.
- Indian telecom rules (DLT registration for messages, caller identity) apply to the business, not only to the carrier (DLT).
Security and privacy#
- Every webhook is signature-checked, and the nonce index makes a replayed event a no-op (provider webhook signatures).
- Carrier credentials are stored encrypted, and screens show only that they are set.
- Numbers and recordings are personal data, handled under the workspace's retention settings.
Licence, cost and versions#
| Question | Answer |
|---|---|
| Licence | Commercial service under Vobiz's terms |
| Cost | Per Vobiz's rates for numbers and minutes. Connect records each call's carrier cost where the provider reports it |
| Version | HTTP and XML APIs; the browser path uses JsSIP 3.13.8 |
| Compatibility | SIP over TLS or WebSocket; trunks to LiveKit as host:5060 |
Troubleshooting#
- The softphone registers but never rings
- The browser is registered to the wrong address, or the endpoint is revoked. Check the line's health on Needs You.
- Inbound calls get a 403
- The signature check failed: the line's carrier does not match the route, or the signing secret is wrong.
- Realtime calls ring out
- The trunk's origination URI must be the LiveKit project's SIP host exactly, without a
sip:prefix.
Official references#
Questions#
Can a business use another carrier?
The adapter layer supports Twilio, Plivo and Exotel as well, each with its own capabilities. What a line can do is asked of its carrier, never assumed.
Why does an SMS not come from my Vobiz number?
Vobiz does not carry SMS. Messages go through the SMS provider configured for the business, under its registered sender ID.