LiveKit connector
Indian phone numbers for teams building on LiveKit.
If your voice app already uses LiveKit, Boni Voice can provide the Indian DID, onboarding, inbound route, logs, and fallback path while your LiveKit stack handles rooms, dispatch, and agents.
LiveKit is a connector path. Boni Voice also works without LiveKit.
Boni DID to LiveKit
Number, route, dispatch, agent
Boni
Indian DID and route control
LiveKit
Trunk, dispatch, room, agent
Fallback
Human, Bow Chat, hosted AI
Events
Call states and evidence
Use this path when LiveKit is your voice app destination.
Boni Voice provides the Indian number and inbound route. Your LiveKit stack can then handle the room, dispatch rule, agent, or caller experience.
You already use LiveKit for rooms, agents, SIP, or realtime voice infrastructure.
You need an Indian business number without taking on telecom provisioning, routing, logs, and support yourself.
You want to test an Indian caller path before expanding the LiveKit side of your application.
Connector path
Keep the India telephony layer hosted. Own your LiveKit app.
Indian DID in front
Boni handles the Indian number, subscription, approval, and inbound call route so your LiveKit app can focus on the caller experience.
LiveKit-specific route
Connect to LiveKit SIP, dispatch, rooms, or agents when your media stack already lives there.
Connector-friendly config
Use a small route object and clear endpoint expectations instead of exposing carrier and gateway details.
AI agent ready
Route to hosted Boni AI or bring your own LiveKit agent path depending on which layer you want to own.
Calling workflow demo
Use LiveKit for media, but keep the call workflow visible.
These Bow Chat videos show the operational layer around a call: route choice, agent readiness, missed-call handling, logs, and AI or human handoff. A LiveKit route should still preserve that visibility.
Inbound call routing demo
A Bow Chat calling demo used as Boni Voice proof: an inbound call reaches the team workspace, keeps caller context visible, and creates a follow-up trail instead of disappearing into one phone.
How it starts
First a working Indian number. Then the LiveKit route.
Get the number
Start through the Boni Voice WhatsApp intake and receive access to panel.boni.one after approval.
Choose LiveKit route
Use the LiveKit connector path when the destination is your LiveKit SIP trunk, dispatch rule, room, or agent.
Keep fallback ready
Attach a human phone, Bow Chat, or hosted AI fallback so test calls do not disappear during setup.
Observe and iterate
Use call events, logs, recordings where enabled, and endpoint health notes to tune the route.
Building a LiveKit agent for India?
Message Boni Voice on WhatsApp. The intake flow keeps access controlled while we set up the right number, route target, and fallback for your test call.
FAQ
Is this a separate product from Boni Voice?
No. Boni Voice is the general Indian DID and routing product. The LiveKit connector is a specialized path for teams that want that number routed into LiveKit.
Do all Boni Voice users need LiveKit?
No. Users can route calls to Bow Chat, a webhook, hosted AI, SIP, a fallback phone, or other supported targets. LiveKit is only for teams choosing that stack.
Can Boni host the AI agent instead?
Yes. Hosted AI uses the Boni-managed voice agent path. BYO LiveKit is best when your own team wants to own the LiveKit runtime, prompts, rooms, and agent lifecycle.
Will there be an open-source connector?
Talk to Boni Voice if you need a reusable connector or starter kit for LiveKit trunk, dispatch, and route validation. Boni keeps the Indian DID, billing, support, and routing layer hosted.