# I need urgent help! **URL:** \ **Category:** Telephony\ **Tags:** sip-trunking\ **Created:** [April 10, 2026, 1:52pm UTC](https://community.livekit.io/t/i-need-urgent-help/830 "2026-04-10T13:52:11Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Brad\_van\_Halm](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/brad_van_halm/32/1015_2.png) [@Brad\_van\_Halm](https://community.livekit.io/u/Brad_van_Halm)\ **Post date:** [April 10, 2026, 1:52pm UTC](https://community.livekit.io/t/i-need-urgent-help/830/1 "2026-04-10T13:52:11Z")
**Subject:** SIP Inbound Trunk returns 404 despite correct configuration **Project:** jbsync-voice-agent-096ubv05.livekit.cloud **Trunk ID:** ST\_FkJ9r9HuzUyE **Numbers:** +3197010208583 **Failed call:** 2026-04-10T13:31:38Z **SIP INVITE To:** sip:+3197010208583@jbsync-voice-agent-096ubv05.sip.livekit.cloud;transport=tcp **Issue:** Twilio sends SIP INVITE, LiveKit returns “404 No trunk found”. Trunk has matching numbers, allowed\_addresses includes 0.0.0.0/0, dispatch rule exists. Worker is registered. No room is created, worker never sees the call. **Twilio support confirmed** the 404 comes from LiveKit’s side (ticket #26125899). ---
**Author:** ![CWilson](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/cwilson/32/135_2.png) [@CWilson](https://community.livekit.io/u/CWilson)\ **Post date:** [April 10, 2026, 3:17pm UTC](https://community.livekit.io/t/i-need-urgent-help/830/2 "2026-04-10T15:17:46Z")
Do you have the call-id for that call? But just looking at what you posted this looks quite wrong: \> **SIP INVITE To:** sip:+3197010208583@jbsync-voice-agent-096ubv05.sip.livekit.cloud;transport=tcp That should return a 404 because it is not a valid SIP URI. You need ot use your SIP URI for SIP calls which you can find here [Sign in | LiveKit Cloud](https://cloud.livekit.io/projects/p_/settings/project)