Agora's Conversational AI Engine takes a phone number you already own through its SIP Trunk vendor option. Point it at Vobiz and the agent that already runs in your app runs on the phone network too, on numbers in 130+ countries with outbound reach to 190.
Agora does not currently ship a Vobiz-specific provider. You connect the two through its SIP Trunk vendor option, which is how Agora takes a number from any carrier, and it carries calls in both directions. The two directions are separate trunks pointing opposite ways, so configure both — outbound authenticates from Agora into Vobiz, and inbound sends calls from Vobiz to an Agora regional endpoint. All of it is console work across the two dashboards.
Agora built a real-time network so that a conversation can happen anywhere a device can: in your app, in a browser, on an embedded board, next to an avatar. Its agents inherit all of that. What none of it provides is a phone number, because the PSTN is not a network you can software-define your way onto — it is licences, interconnects and inventory, market by market.
That is the layer Vobiz provides. Same agent, same conversation engine, one more channel: a real number people can dial, in the markets you operate in.
Standard SIP on both sides. Nothing here waits on Agora shipping anything new.
Agora's SIP Trunk vendor option exists so you are not limited to numbers bought inside the platform. Add a Vobiz number, and the agent you have already built and tested answers and dials on it.
Create a SIP credential in Vobiz, attach it to an outbound trunk, and copy that trunk's own SIP domain into Agora with the username and password. Agora authenticates into your trunk and the call goes out over your carrier.
Point a Vobiz inbound trunk at the Agora endpoint serving your number's region, link the number to it, and set the answering agent on the Agora side. No webhook, no answer URL, no server of yours in the path.
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. Choose the number, then route inbound to the Agora region that serves it.
Agora runs the campaign — agent, contact list, launch timing, call delay, concurrency — and Vobiz carries every call in it. Set the concurrency ceiling to match your account limits and the two stay in step.
Agora holds the agent side of the conversation. Vobiz holds the call: logs for both legs, a detail record with 43 fields including MOS, jitter, packet loss and hangup attribution, and optional recording and transcription configured on the trunk itself.
Create the agent first, then wire the directions. Outbound proves the credential; inbound proves the routing.
Three things that will waste an afternoon. Strip the sip: prefix — Agora presents its endpoint with one, the Vobiz URI field takes a host or a host and port, and pasting the prefix fails on save. The region has to match the number's country, because a number pointed at the wrong regional endpoint can signal correctly and still fail on audio, which looks like a media fault and is a routing one. And a number with no inbound agent assigned in Agora accepts the call and drops it, which reads as a carrier problem and is not one.
Every field, every screen and the full troubleshooting table are in the Vobiz docs.
Read the integration guideNot today. Agora has a SIP Trunk vendor option for bringing a number from any carrier, and Vobiz connects through it. It carries inbound and outbound on the same number, so nothing is missing for want of a dedicated provider entry.
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. For inbound, route the number to the Agora regional endpoint that serves its country; their documentation lists the current set.
Because the directions point opposite ways. Outbound is Agora authenticating into a Vobiz trunk with a username and password. Inbound is a Vobiz trunk sending calls out to an Agora regional endpoint. The same number is used by both, but the routing is configured separately.
Either, or both. A credential is the quicker route and keeps working if Agora changes its IP addresses. Agora publishes its outgoing SIP addresses per region if your security policy wants an allow-list instead, and Vobiz accepts the two together.
No. Both directions are configured in the Agora Console and the Vobiz Console, and outbound campaigns are a contact list upload rather than an API integration.
Almost always one of two things. Either the number is not showing under linked numbers on the inbound trunk, or it has no inbound agent assigned in Agora — an unassigned number will accept the call and then drop it. Check both before looking at the trunk itself.
Create a Vobiz account, buy a number, and wire the outbound trunk. Launch a campaign with a single contact and call your own phone. Inbound is a second trunk once that works.
Agora builds real-time voice, video and conversational AI infrastructure. Vobiz is not affiliated with Agora; this integration uses Agora's SIP Trunk vendor option. Agora's own documentation is authoritative on endpoints and IP addresses.
Connect 3CX PBX to Vobiz SIP trunking for inbound and outbound calling across 130+ countries - configure a generic SIP trunk in minutes.
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.
Build C# and .NET 8 voice apps with the Vobiz SDK - outbound calls, SIP trunks, and VobizXML with native DI for global calling in 130+ countries.
We use cookies to run this site and, with your permission, to understand how it's used. Read our Cookie Policy.