Subject: Inbound SIP trunk returns "404 No trunk found" for all INVITEs — Twilio Elastic Trunk integration Project: scale-desk-ai-nxvkobrt SIP host: scale-desk-ai-nxvkobrt.sip.livekit.cloud Inbound trunk ID: ST_teYSM6uLNDbF Dispatch rule ID: SDR_sofRZG5hk4Rn Issue Every inbound SIP INVITE to my LiveKit Cloud project returns SIP/2.0 404 No trunk found, regardless of the trunk configuration. As a result, no rooms are ever created and the agent worker never receives a job. OPTIONS to the same SIP host returns 200 OK over TLS, so the edge is reachable. Configurations tested (all return 404) LiveKit inbound trunk variations: - numbers=["+16508558750"] only - auth_username + auth_password only - auth_username + auth_password + numbers - allowed_addresses=["<my public IP>/32"] (verified IP via Via: received=…) - allowed_addresses=["0.0.0.0/0"] - Full Twilio published SIP signaling CIDRs in allowed_addresses - Combinations of all of the above Twilio side variations: - <Dial><Sip> TwiML with transport=tls, transport=tcp, with/without username+password attributes - Twilio Elastic SIP Trunk with secure=true + sipshost5061 - Twilio Elastic SIP Trunk with secure=false + sip:host;transport=tcp (exactly per LiveKit's docs) - Twilio Elastic SIP Trunk with embedded credentials in origination URI (sipuserpass@host:5061;transport=tls) Reproducing 404 directly Sending a raw SIP INVITE over TLS from an external host to sip:+16508558750@scale-desk-ai-nxvkobrt.sip.livekit.cloud:5061 consistently returns: SIP/2.0 100 Processing Record-Route: sip:10.244.41.131:40004;sipfe;transport=tcp;lr Record-Route: sip:139.185.54.113:5061;sipfe;transport=tls;lr Via: SIP/2.0/TLS <client-ip>:<port>;branch=<branch>;received=<public-ip>;rport=<port> … SIP/2.0 404 No trunk found Sample Call-IDs from probes: probe-c7fd41f4e4851501@probe.local, probe-dc3200552a345e9d@probe.local. Real Twilio call SIDs failing at 0 seconds: CAf8f5a0bf25b2a6d8a30adaeae5e8d017, CA7dc67a3def476c54f23c6e3c76266df4 (timestamps around 2026-05-09 07:05 UTC). Twilio details - Account type: Full, active - Twilio trunk: TK1c2fccd6ca7df03597b180ed033d4ef4 - Domain: scaledesk-1778310147.pstn.twilio.com - Origination URL: sip:scale-desk-ai-nxvkobrt.sip.livekit.cloud;transport=tcp - Phone number: +16508558750 Question What additional matching criteria does your inbound trunk matcher require beyond the documented auth_username/auth_password, allowed_addresses, and numbers fields? The docs state that setting either auth or allowed_addresses is sufficient, but neither path matches incoming INVITEs on this project. Could you check your edge logs for the timestamps above and tell me why the matcher is returning 404 for these INVITEs?

Hi kutman, ⚠️ This channel will be deleted soon ⚠️ Please use our new community at https://community.livekit.io for technical discussions and to post technical questions. The Slack community is not going away, but we are migrating technical questions to our new forum. Please see full details here.