SIP 404 "No trunk found" — DNS routing mismatch on LiveKit Cloud

John Moelker
Sat, 28 Mar 2026 03:32:42 +0000
Telephony

SIP 404 “No trunk found” — DNS routing mismatch on LiveKit Cloud

We’re getting 404 No trunk found on inbound SIP calls to our LiveKit Cloud project, but only
from certain source IPs (Telnyx). Calls from Twilio work perfectly to the same trunk.

Project: cwa-voice-9x077mph (ID p_5u9xu5ysoly)
Trunk: ST_Xa3Bp9aixRFP — numbers include +14144007103
Agent: CA_pX3Me4NK6qK8

The problem:
Our SIP endpoint cwa-voice-9x077mph.sip.livekit.cloud resolves to 161.115.178.82 and
161.115.178.146 from public DNS (Google, Cloudflare). Twilio connects to these IPs and calls
work.

But when Telnyx sends a SIP INVITE, it arrives at 161.115.181.101 — a different server that
returns 404 No trunk found.

SIP trace (from Telnyx CDR):
INVITE sip:+14144007103@cwa-voice-9x077mph.sip.livekit.cloud SIP/2.0
From: “+12268830526”
To: sip:+14144007103@cwa-voice-9x077mph.sip.livekit.cloud

→ 100 Processing
→ 404 No trunk found

src: 192.76.120.10:5060 (Telnyx)
dst: 161.115.181.101:5060 (NOT our FQDN’s IPs)

Question: Is there GeoDNS, anycast, or SIP routing that sends traffic from certain source IPs
to different SIP servers? Our trunk exists on .178.82/.146 but the call arrives at .181.101
which doesn’t know about it.

2 posts - 2 participants