Hi! Hitting SIP/2.0 503 Try again later on every Twilio inbound call to my LiveKit Cloud project — would love a sanity check from anyone who's done Twilio → LiveKit recently. Setup: • LiveKit Cloud inbound URI (from Project Settings): gwmt8ehuoo6.sip.livekit.cloud • Twilio number → TwiML returns <Dial><Sip secure="true">sip:+1XXX...@...sip.livekit.cloud</Sip></Dial> • Inbound trunk has E.164 number in

numbers

, allowed_addresses=['0.0.0.0/0'], dispatch rule → room • Agent worker running, [Router] log confirms tenant mapping • Also tried Twilio Elastic SIP Trunk with Secure Trunking → same 503 What the PCAP shows: • INVITE arrives on UDP:5060 (despite secure="true" in TwiML) • LiveKit → 100 Processing • Then → 503 Try again later Before fixing the URI (was using a wrong subdomain earlier), I got 404 No trunk found. Fixing URI resolved 404 → now 503. Two questions: 1. Does LiveKit Cloud inbound require TLS (port 5061) and reject UDP:5060 with 503? 2. Or is 503 pointing at a downstream dispatch/worker issue I should check? Happy to DM the PCAP + trunk dump. Thanks in advance!

Hi Souvik Guria, ⚠️ 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.