damp-apartment-38475
07/28/2025, 10:15 AMtall-airline-16756
07/28/2025, 10:15 AMtall-airline-16756
07/28/2025, 10:17 AMdamp-apartment-38475
07/28/2025, 10:24 AMtall-airline-16756
07/28/2025, 10:25 AM*.turn.livekit.cloud on TCP/443 so your TURN servers can do their job.
• Take a peek at any firewalls that might be blocking UDP or DTLS traffic - these are super important for sending media.
2. Media Timeout Configuration
• Sometimes the default timeout settings can be a bit too quick. Try extending the initial timeout (usually 30 seconds) and ongoing timeout (usually 15 seconds) to give your network some breathing room.
3. Diagnostic Tools
• The LiveKit Connection Tester is your friend here - it'll help you spot any UDP or DTLS hiccups.
• Keep an eye on those call logs for MEDIA_FAILURE disconnect reasons to figure out what's causing the timeouts.
4. SIP Trunk Configuration
• Double-check that your SIP trunk dispatch rules are set up correctly for media traffic.
• Make sure your codecs are speaking the same language between the SIP trunk and LiveKit.
5. Environmental Adjustments
• Turning on jitter buffering can help smooth out any packet loss or network speed bumps.
• If UDP is giving you trouble, switching to TCP might be your best bet.
These tips are specifically for LiveKit Cloud and should help you tackle those media timeout issues. If you're still scratching your head, we might need to dig a bit deeper into your specific setup. But don't worry, we'll get it sorted!
Sources: pkg/sip/outbound.go | Firewall Tips | SIP Integration | livekit/livekit_composite | DeepWiki | protobufs/livekit_models.proto