early-needle-49581
12/15/2025, 10:27 AMtall-airline-16756
12/15/2025, 10:27 AMtall-airline-16756
12/15/2025, 10:27 AMsip:<your-subdomain>.sip.livekit.cloud).
• If Vonage requires authentication, provision the username/password they will use to register or authenticate to LiveKit.
1. Create an inbound trunk in LiveKit
• Create an inbound trunk in LiveKit that includes the Vonage number(s). Example CLI flow:
a. Prepare a JSON trunk definition with the number(s).
b. Run lk sip inbound create <file>.json to create the trunk.
• This makes LiveKit accept calls for those numbers.
1. Add a dispatch rule to route calls into rooms
• Create a dispatch rule that maps incoming calls on that trunk to LiveKit rooms (for example, using a roomPrefix like call- or a rule that maps to a specific room).
• Use the CLI/API to create the dispatch rule (e.g., lk sip dispatch create <rule>.json).
1. (Optional) Attach an agent or room config
• If you want calls answered by an AI voice agent or a specific config, include roomConfig in the dispatch rule so the agent or room settings load when calls arrive.
1. Test the setup
• Place a call to the Vonage number and confirm it reaches the LiveKit room/agent.
• Verify audio, authentication, and any SIP headers required by Vonage.
If you’d like, tell me:
• Whether you prefer CLI or API instructions,
• The Vonage SIP URI/auth method you plan to use, and
• Whether you want calls routed to a specific room, a room per caller (prefix), or an AI agent.
I can then provide the exact example JSON and CLI/API commands to use.
Sources: SIP inbound trunk | LiveKit docs | SIP APIs | LiveKit docs | Inbound calls with Twilio Voice | LiveKit docs | Agents telephony integration | LiveKit docs | SIP overview | LiveKit docs