Build LiveKit voice agents on enterprise-grade telephony
Enterprise-grade SIP trunking for LiveKit agents in India
Take your LiveKit agent live on Plivo's telephony, self-serve. One inbound trunk, one outbound, secure by default.
Take your LiveKit agent live on India-based telephony, self-serve. In-country routing keeps your calls compliant.
# Inbound trunk: callers reach your agent
Name: livekit-inbound
LiveKit SIP URI: <your-project-sip-uri>;transport=tls
Secure trunking: TLS + SRTP
# Outbound trunk: your agent dials out
Name: livekit-outbound
Termination: {trunk}.zt.plivo.com
Auth: credentials · ip acl
How LiveKit connects to the phone network
One trunk carries calls in, one carries calls out. Both carry two-way audio between the phone network and your LiveKit agent.
Go live in three steps
No tickets, no sales call: create the trunks, connect LiveKit, and take your first call.
- 01
Create your Plivo trunks
In the Plivo console, create an inbound and an outbound trunk. Enable secure trunking, TLS with SRTP.
Create trunksInbound trunk livekit-inbound · LiveKit SIP URIOutbound trunk livekit-outbound · credentialsSecure trunking TLS + SRTP · onCreate trunksconfig / api# Create the trunk pair inbound: livekit-inbound outbound: livekit-outbound transport: tls · srtp - 02
Configure LiveKit to use Plivo's trunks
Point LiveKit's inbound trunk and dispatch rule at Plivo, and outbound calling at your Plivo termination domain.
LiveKit configTermination domain {trunk}.zt.plivo.comCredentials livekit_trunk · ····Dispatch rule → your-voice-agentSave configconfig / api# LiveKit side termination: {trunk}.zt.plivo.com auth: livekit_trunk / ···· dispatch: your-voice-agent - 03
Connect a number, take live calls
Point your Plivo number at the inbound trunk. Callers reach your agent live, and it dials out over the outbound trunk.
Connect numberNumber +1 415 555 0142Trunk livekit-inbound · attachedStatus live call · 0:42Play recordingconfig / api# Live calls number: +1 415 555 0142 trunk: livekit-inbound status: live call · 0:42
Read the full integration guide
Every field, the LiveKit-side config, and the dispatch rule, walked through step by step in the Plivo docs.
Why voice teams run LiveKit on Plivo
Enterprise-grade telephony, a team that knows the trunk layer, and the reach to put your agent on any phone, all self-serve.
15 years of telephony expertise
Plivo has run carrier-grade voice since 2011. The team helps you onboard and debug the trunk layer, the part voice frameworks cannot unblock for you.
Voice infrastructure built to scale
The carrier-grade stack Fortune 500s and startups run on, from a first test call to millions of minutes, backed by a 99.99% uptime SLA.
Flexible trunk authentication
Authenticate trunks with an IP allowlist, username and password credentials, or both, whichever fits how your LiveKit deployment connects.
Warm human handoff, no re-dial
Pass a live caller from your agent to a human mid-call over SIP REFER, with no second dial.
Enterprise-grade and secure
TLS signaling and SRTP media on every call, backed by a 99.99% uptime SLA.
Unlimited concurrent calls
Scale elastically with no per-channel fees and nothing to provision up front.
Deploy it your way
Plivo trunks speak standard SIP, so they work the same whether you self-host LiveKit or run it on LiveKit Cloud.
Self-host LiveKit
Run the open-source LiveKit server and agents on your own infrastructure. Point a Plivo trunk at your SIP endpoint and every call stays inside your network.
LiveKit self-hostingPlivo-LiveKit Gateway
Bridge your LiveKit agents to the phone network with Plivo's open-source gateway. Run it self-hosted or alongside LiveKit Cloud, and the trunk plumbing is handled for you.
View on GitHubHost on LiveKit Cloud
Let LiveKit Cloud run the media and agents. Plivo connects over standard SIP, so the same inbound and outbound trunks work with no changes.
Integration guideTransparent per-minute pricing
Published per-minute SIP rates, shown in your region's currency.
- Inbound calls
- $0.0028/min
- Outbound calls
- $0.0046/min
- Local number
- $0.50/mo
- Secure trunking
- $0.00
local · per minute
local · per minute
rental · per month
tls + srtp · included
- Inbound calls
- ₹0.60/min
- Outbound calls
- ₹0.60/min
- Local number
- ₹250/mo
- Secure trunking
- ₹0.00
local · per minute
local · per minute
rental · per month
tls + srtp · included
- no per-channel fees
- no minimum spend
- no contracts
Rates as of July 2026, see full pricing.
How Plivo compares
Both Plivo and Twilio ship an official LiveKit SIP quickstart. Here is how they compare on price and the trunk capabilities that matter for voice agents.
For India, the choice is a licensed in-country carrier. Plivo and Exotel both originate India calls; Twilio does not. Here is how they compare.
| Capability | ||
|---|---|---|
| US inbound per minute | $0.0028 | $0.0034 |
| US outbound per minute | $0.0046 | $0.007 |
| Outbound calling | ||
| Call recording | ||
| IP and credential trunk auth |
Rates from public provider pricing pages, as of July 2026. Verify current pricing with each provider.
| Capability | |||
|---|---|---|---|
| Local per minute (in / out) | Rs 0.60 / Rs 0.60 | ~Rs 0.65 | Not supported |
| Billed in INR to an India entity | Not supported | ||
| India-based call routing | Not supported | ||
| India numbers with KYC | Not supported | ||
| DLT / DND compliance | Not supported |
Rates as of July 2026. Exotel does not publish per-minute rates; the figure shown is an approximation. Plivo's Rs 0.60/min is a published rate.
Built for India
India adds a regional routing requirement, and Plivo is one of the few trunk providers that documents exactly how to meet it.
We handle India's regional routing requirement. India's voice rules require call media to stay in-country. Plivo keeps it in-country across our India regions, so your agent's India calls connect where other setups quietly fail. The integration guide walks through the LiveKit-side setting.
Complete KYC before renting numbers. India numbers require KYC: an INR account, certificate of incorporation, and GST registration.
- ₹0.60/min inbound · local
- ₹0.60/min outbound · local
Frequently asked questions
LiveKit works with any standards-compliant SIP trunk. Plivo ships an official LiveKit quickstart that covers both inbound and outbound trunks, plus a matching guide in its own docs. Most teams building LiveKit voice agents weigh Plivo against Twilio or LiveKit's own Phone Numbers.
LiveKit works with any standards-compliant SIP trunk, but India needs a licensed in-country carrier. Plivo and Exotel both originate India calls and publish INR rates; a global-only provider like Twilio cannot. Plivo ships an official LiveKit quickstart plus a matching guide in its own docs.
No. LiveKit is not tied to any one carrier. Plivo ships an official LiveKit quickstart, and teams often pick Plivo over Twilio for lower per-minute rates and no per-channel fees.
No, and for India a local carrier serves you better. Plivo keeps call media in-country in India, bills you in INR to an India entity, and supports DLT and DND compliance, which global-only trunks do not.
Yes. The same trunk carries international calls, so your LiveKit agent can take or place calls worldwide, all self-serve, with no extra integrations.
Yes. Plivo keeps call media in-country in India and handles the regional media routing requirement, with local rates of Rs 0.60 per minute inbound and Rs 0.60 per minute outbound. India numbers require KYC: an INR account, certificate of incorporation, and GST registration, and Plivo supports DLT and DND compliance.
Yes. Some countries require call media to stay in-country. Plivo runs regional infrastructure that meets these media anchoring rules; in India, for example, you set your LiveKit region to India and Plivo keeps both call legs in-country. If you are deploying into a market with localization requirements, talk to our team and we will confirm the routing setup.
Yes. Plivo trunks speak standard SIP to the LiveKit SIP service whether it runs on LiveKit Cloud or your own infrastructure. Self-hosted deployments with static egress IPs can authenticate the outbound trunk with an IP ACL instead of credentials.
It is a configuration change, not a rewrite: create the trunk pair in Plivo, update the trunk settings in LiveKit, and the same agents keep working. You can port your numbers with guided onboarding and run both trunks side by side during the cutover.
Put your LiveKit agent on the phone network
Two trunks, one test call, no contracts