Inbound SIP returning 404 from LK Cloud edge before session creation — Telnyx FQDN, 0 dashboard sessions

Telephony
, , ,
1

Hi there! Looking for a sanity check / DM partner on a fairly urgent inbound SIP issue.

Pattern I am seeing:
- Inbound INVITE via Telnyx FQDN connection → LK Cloud
- LK edge returns 404 within ~60–240ms before any session is created
- Dashboard shows 0 SIP sessions over 7 days despite multiple test calls
- Telnyx debugger confirms LK is the one 404’ing (not a Telnyx-side issue)

Already verified via Twirp API:
- Trunk: numbers match the inbound DID, allowedAddresses: 0.0.0.0/0, krispEnabled
- Dispatch rule: room_config.agents properly nested with the agent_name
- Pipecat worker online and registered with that agent_name

Emailed Support yesterday and got auto-reply, no ticket # yet, follow-up sent. I have a demo Thursday so a bit time-sensitive. :grimacing:

Common causes I might be missing? Project tier gate? INVITE Request-URI normalization (Telnyx sending 8175551234 vs trunk holding +18175551234*)? Regional SIP edge routing?*

Happy to share trunk ID / dispatch rule ID / project ID in DM with anyone who has bandwidth to dig in — would rather not paste them publicly. Thanks :folded_hands:

2

Found my own solution! Was pointing at Server URI and not specific SIP URI. made that switch and seems to be working now. :crossed_fingers: