Title: Inbound SIP call creates room but LiveKit Cloud Agent never joins — deployment sleeping

[Webmaster_Webmaster]

Hello LiveKit Team,

We need help diagnosing an inbound SIP-to-Agent dispatch issue.

Project and Agent

• Project: wizard-voice-poc
• Project ID: p_1e8t01a4oc7
• Agent: wizard-voice-agent
• Agent ID: CA_bM6y75BYCwgk
• Production version: m6gZeaA4Hi26
• Agent region: ap-south
• Current Agent status: SLEEPING

Inbound SIP

• SIP Dispatch Rule: SDR_PGF68y5CgnU9
• The rule’s roomConfig.agents contains agentName: wizard-voice-agent
• SIP Call ID: SCL_BhkTNbSdc7Dq
• Room Session ID: RM_QmW9jkj4oR3w
• Test date: October 27, 2026
• Room created at approximately 13:09:18 Thailand time (UTC+7)

Observed behavior

1. The inbound SIP call reaches LiveKit successfully.
2. LiveKit creates the room and the SIP participant becomes active.
3. No AI Agent participant joins the room.
4. The caller hangs up after approximately 43 seconds.
5. Agent Overview shows zero sessions.
6. Runtime logs are unavailable because the deployment has shut down due to inactivity.
7. The production build completed successfully.

Please investigate:

• Was an Agent Dispatch job created for this SIP room?
• If yes, why was it not accepted or started?
• Did the sleeping Cloud Agent fail to wake up?
• Are there worker startup, scheduling, region, or dispatch errors in the server-side logs?

We would appreciate the exact root cause and the recommended fix without redeploying or changing our existing working SIP configuration unnecessarily.

Thank you.

[darryncampbell (Darryn)]

@Webmaster_Webmaster

• RM_QmW9jkj4oR3w

Thanks for providing the room ID.

The server logs show this job was dispatched to your self-hosted agent

The issue is you have two identically named agents in your account, if you delete your self-hosted agent, your cloud agent should receive the dispatch.