Plivo is now fully integrated with Vapi via SIP, unlocking a clean path for teams who want to scale voice without compromising flexibility.
If you're already using Plivo for telephony and looking to upgrade your voice stack with real-time LLMs, this is for you.
Let’s break down what this means, technically and strategically.
Why SIP Routing Matters
SIP trunking isn’t new, but its value is often buried under legacy setups. With Vapi, you can now treat SIP as a programmable transport layer.
That means bringing your existing Plivo numbers into Vapi and powering them with real-time, multilingual voice agents built on modern LLMs.
It’s a win-win:
- Developers get full control over routing, logic, and model selection.
- Businesses preserve existing infrastructure while upgrading UX.
This integration supports both inbound and outbound calls, and it takes just a few steps to set up.
How To Setup The Outbound Calls
To place outbound calls from your Vapi assistant through a Plivo-managed trunk:
- Create a SIP trunk in Plivo
- Use the Plivo console to whitelist Vapi's IPs.
- Copy the termination domain provided by Plivo.
- Register that trunk with Vapi
- Call the Vapi API to create a new SIP trunk credential.
- Attach a Plivo phone number to the trunk using Vapi's /phone-number endpoint.
- Make calls programmatically
- Use the /call/phone API with your assistant ID and the phone number you just configured.
This setup gives you full routing control while using Plivo’s global reach for termination.
How To Setup Inbound Calls:
Incoming calls work the same way in reverse:
- Create an IP URI in Plivo
- Set the target URI to sip.vapi.ai;transport=udp.
- Create an inbound SIP trunk
- Assign the URI as the destination for the trunk.
- Attach a phone number
- Any calls to that number now hit Vapi’s SIP endpoint and wake up your assistant.
Just like that, your Plivo number becomes a programmable endpoint powered by real-time voice AI.
Check out our Docs for full setup instructions.
Why It Matters
Telephony shouldn't be the bottleneck in your LLM workflow. With Vapi and Plivo, it's not.
You're free to route, control, and scale voice on your terms without sacrificing quality or speed.
If you already have SIP trunks with another provider, Vapi works with any SIP-compatible carrier. But if you’re already on Plivo, this just made your life a lot easier.
Let’s build voice the way it should be open, programmable, and production ready.
