# Inbound Trunk returning 408 Request Timeout - Livekit Cloud not responding to INIVTE

**URL:** <https://community.livekit.io/t/inbound-trunk-returning-408-request-timeout-livekit-cloud-not-responding-to-inivte/1589>\
**Category:** Telephony\
**Tags:** sip-trunking\
**Created:** [July 9, 2026, 5:11pm UTC](https://community.livekit.io/t/inbound-trunk-returning-408-request-timeout-livekit-cloud-not-responding-to-inivte/1589 "2026-07-09T17:11:00Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Deani\_Hansen](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/deani_hansen/32/507_2.png) [@Deani\_Hansen](https://community.livekit.io/u/Deani_Hansen)\
**Post date:** [July 9, 2026, 5:11pm UTC](https://community.livekit.io/t/inbound-trunk-returning-408-request-timeout-livekit-cloud-not-responding-to-inivte/1589/1 "2026-07-09T17:11:00Z")

</div>

Hi all,

We have a BYO carrier (Danish provider, plain UDP SIP trunk, no TLS) sending INVITEs to our LiveKit Cloud SIP endpoint. Symptom: zero SIP response at all — not even `100 Trying` — across multiple retries to two different resolved edge IPs (both within LiveKit’s documented static SIP range). After ~5s the carrier’s own proxy gives up and returns a `408` on its side. That 408 is self-generated by the carrier, not something LiveKit sent.

We’ve tried various combinations of inbound trunks and dispatch

- filtering on their phone no’s
- Without phone number filtering, allowing using 0.0.0.0

From the Provider-wireshark, it looks like the Invite is never picked up despite hitting the livekit cloud SIP IP.

Happy to share project/trunk IDs with a staff member directly if that helps track this down - didn’t want to post them in the open here.

Wireshark from provider:

 ![Group 11 (2)](https://us1.discourse-cdn.com/flex001/uploads/livekit2/original/2X/9/97ea7cb4d37faffc53b736debc1c13305a5fa682.png)

Any ideas on how to best debug this?

---

<div class="post-metadata">

**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:** [July 9, 2026, 9:49pm UTC](https://community.livekit.io/t/inbound-trunk-returning-408-request-timeout-livekit-cloud-not-responding-to-inivte/1589/2 "2026-07-09T21:49:32Z")

</div>

Do oyu have a call id or PCAP or something I can look at?

---

<div class="post-metadata">

**Author:** ![Deani\_Hansen](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/deani_hansen/32/507_2.png) [@Deani\_Hansen](https://community.livekit.io/u/Deani_Hansen)\
**Post date:** [July 11, 2026, 5:07am UTC](https://community.livekit.io/t/inbound-trunk-returning-408-request-timeout-livekit-cloud-not-responding-to-inivte/1589/3 "2026-07-11T05:07:18Z")

</div>

I found an old Slack thread that pointed to differences in the SIP URI using IP vs FQDN, and asked provider to adjust accordingly and that seem to have done the trick 🙂

---

<div class="post-metadata">

**Author:** ![system](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/system/32/26_2.png) [@system](https://community.livekit.io/u/system)\
**Post date:** [July 13, 2026, 8:53am UTC](https://community.livekit.io/t/inbound-trunk-returning-408-request-timeout-livekit-cloud-not-responding-to-inivte/1589/4 "2026-07-13T08:53:03Z")

</div>

Closed on July 13, 2026, 8:53am UTC

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.