Make and receive browser-based phone calls with the Vobiz WebRTC Playground using your API credentials and a Vobiz DID.

Use the hosted Vobiz WebRTC Playground to make and receive phone calls directly in your browser.
ℹ️ Info: Choose the correct authentication method:
registrar.vobiz.ai, then authenticate with the endpoint username and password over SIP WebSocket. Use sip:username@registrar.vobiz.ai only when the client asks for the full SIP URI.Before you begin:
⚠️ Warning: Your Auth Token is a secret. Enter it only on Vobiz services such as
rtc-demo.vobiz.ai, and do not share it or include it in screenshots.
ℹ️ Info: Enter every phone number in E.164 format: a leading
+, the country code, and the subscriber number. Do not include spaces or hyphens. Example:+919876543210.
Go to rtc-demo.vobiz.ai.
Enter your Vobiz Auth ID. In API Password, enter your Auth Token.
Copy both values from the API Credentials section in the bottom-left corner of the Vobiz dashboard.
Click Connect.
The first time you connect, Vobiz automatically creates the Vobiz-WebRTC-Playground application in Voice Applications. You will use this application to configure inbound calls.
In Caller ID Override, enter a DID purchased from Vobiz.
Use E.164 format with no spaces or hyphens. For example:
text+919876543210
In Destination Target, enter the phone number you want to call.
Include the country code and do not include spaces or hyphens. For example:
text+919812345678
Click Call. The playground places the outbound call using the DID from Caller ID Override.
✅ Success: The destination rings and the browser displays the active call controls.
Complete the outbound connection steps once before configuring inbound calling. This creates the playground application in your Vobiz account.
Go to Voice Applications and open Vobiz-WebRTC-Playground.
If the application is not listed, return to the playground, connect with your API credentials, and refresh the applications page.
Locate Attach Number in the bottom-right of the application page. Select the Vobiz DID that should receive browser calls, then complete the attachment.
Return to rtc-demo.vobiz.ai and make sure the playground is connected.
In Caller ID Override, enter the DID attached to the playground application. Use E.164 format with no spaces or hyphens.
From another phone, call the attached DID using its full country code. For example:
text+919876543210
When the incoming-call notification appears in the playground, click Accept or Pick Up.
✅ Success: The browser answers the inbound call through the DID attached to
Vobiz-WebRTC-Playground.
| Problem | What to check |
|---|---|
| Connect fails | Confirm that Auth ID contains your Auth ID and API Password contains your Auth Token. Copy the values again from the Vobiz dashboard. |
| Outbound call does not start | Confirm that Caller ID Override is a DID purchased from Vobiz and both numbers use E.164 format. |
| Inbound call does not appear | Confirm that the DID is attached to Vobiz-WebRTC-Playground, the same DID is entered in Caller ID Override, and the playground is connected. |
| The call connects without audio | Allow microphone access for rtc-demo.vobiz.ai in your browser, then reconnect the call. |
| Custom WebRTC SIP client does not register | Set the registrar or server to registrar.vobiz.ai, not sip.vobiz.ai. Authenticate with the SIP endpoint username and password, not your account Auth ID and Auth Token. |
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.