early-needle-49581
12/14/2025, 6:41 PMtall-airline-16756
12/14/2025, 6:41 PMtall-airline-16756
12/14/2025, 6:41 PMearly-needle-49581
12/14/2025, 6:44 PMtall-airline-16756
12/14/2025, 6:44 PMnumbers: ["+234XXXXXXXXXX"] then run lk sip inbound create <file>.json.
1. Make a dispatch rule to route incoming calls
• Create a dispatch rule that determines how calls are mapped to LiveKit rooms (for example, create a unique room per call with a roomPrefix like call-).
• Apply the dispatch rule to the inbound trunk so incoming calls are placed into the correct room or handled by your application/agent.
1. Answer calls inside LiveKit
• When the call arrives LiveKit will create a SIP participant in the target room. Your app (or an agent/AI bot) can join that room to handle the call (play prompts, record, bridge to agents, etc.).
1. Test and secure
• Test from outside Nigeria and from Nigeria (or via VoIP) to confirm media and signaling flow.
• Enable SRTP/TLS if your provider and LiveKit support it, and restrict inbound SIP to provider IPs.
What I need from you to give tailored steps
• Which SIP provider you plan to use (Twilio, Telnyx, Plivo, Wavix, other)?
• Do you have a self-hosted LiveKit or LiveKit Cloud project with SIP enabled?
• Do you need calls routed to a single shared room, unique per call, or to an IVR/AI agent?
Tell me those and I’ll give exact provider-specific settings and the CLI/API payloads you can use.
Sources: https://blog.livekit.io/introducing-livekit-phone-numbers-zero-to-ringing-in-60-seconds/#/portal| | LiveKit Phone Numbers | LiveKit docs | SIP overview | LiveKit docs | Create and configure Telnyx SIP trunk | LiveKit docs | SIP trunk setup | LiveKit docs