404 No trunk found on every inbound SIP call — all configurations tried

Telephony
1

Hi — I’m getting “404 No trunk found” on every inbound SIP call from Twilio Programmable Voice. I’ve exhausted every configuration option over many attempts.

What I’ve tried:

  • Trunk with specific phone number + auth credentials

  • Trunk with empty numbers array (no number restriction)

  • Trunk with allowedAddresses set to Twilio’s SIP CIDR ranges (54.172.60.0/30 etc)

  • With and without ;transport=tcp in the TwiML SIP URI

  • With and without username/password credentials in the TwiML

What the PCAP shows every time: INVITE → 100 Processing → 404 No trunk found

No 407 challenge is ever issued, which means LiveKit is failing at the matching stage before auth is even attempted. The trunk exists in the correct project and is visible in the dashboard.

Key detail: Twilio’s source IP is 54.172.60.2. I created a trunk with allowedAddresses including 54.172.60.0/30 which covers that IP exactly. Still returns 404 immediately.

Is this a known issue with new projects? Could there be a propagation delay or a trunk matching bug on LiveKit Cloud?

2

What is your trunk ID? Do you have a specific Call-ID I can look at?

3

Trunk ID: ST_wTfzhGB3Y9m2

Here are two Call-IDs from recent attempts:

From the PCAP Via headers:

  • branch=z9hG4bKb9ab6f6f-3a89-470b-9149-44c98ef5b92a (latest call)

  • branch=z9hG4bK7e1f.0ebabd53c7a6835255f419fc01f4f32d (previous call)

The SIP Call-ID from the last PCAP is visible in the headers. Every call shows the same pattern: INVITE → 100 Processing (with tag SCL_ assigned) → 404 No trunk found. No 407 challenge is ever issued.

Happy to share the full PCAP file if that helps.

4

ST_wTfzhGB3Y9m2

Looks like that SIP trunk was deleted on March 21st