brief-evening-79958
12/26/2025, 4:24 AMtall-airline-16756
12/26/2025, 4:24 AMtall-airline-16756
12/26/2025, 4:24 AMagent_name?
4. Is this behavior only for SIP calls, only for frontend, or identical for both? Any differences in error messages?
5. Can you run the connection test (checkWebRTC(), checkTURN(), checkWebSocket()) and share results if possible?
Immediate things you can try while I review your answers:
• Run lk agent status and lk agent logs around a failed attempt to look for timeouts or startup delays.
• Ensure you have multiple agent workers for redundancy and avoid single-worker setups.
• If using LiveKit Cloud and cold starts are enabled, keep at least one warm/pre-warmed instance or upgrade plan to avoid cold starts.
• Verify SIP dispatch rules on your trunk and ensure explicit dispatch is set if you need predictable routing.
Share the answers and any log snippets and I’ll pinpoint the most likely root cause and exact next steps.
Sources: Deploying to production | LiveKit Docs | examples/frontdesk | livekit/livekit_composite | DeepWiki | Agents (Python) | livekit/livekit_composite | DeepWiki | Agents telephony integration | LiveKit docs | Firewall Tips