Subject: SIP call rings forever – worker joins room but LiveKit never sends 200 OK Project: appointment-setter-u2gpzvxc SIP domain: 3nbu801ppzl.sip.livekit.cloud Inbound trunk: ST_tMFv42PMxoQ3 Dispatch rule: SDR_niyMA7hanWcc (Direct rule with empty roomConfig) Recent CallSid: CA68d9496511732355b13bbb5152919202 (Dec 4, 2025 ~13:44 UTC) • Symptom:Twilio hits our webhook, we create room inbound-14438600638-e37df121, cache config in Redis, and respond with TwiML pointing at the SIP URI sip:inbound-14438600638-e37df121@3nbu801ppzl.sip.livekit.cloud. • LiveKit dispatches job AJ_ZtN4nBD5G5vX; worker connects to room, loads agent config, and sends the greeting (“hey, thank you for calling…”). • SIP trace shows repeated 180 Ringing from LiveKit, then Twilio CANCELs after ~30s because it never receives 200 OK. • We need LiveKit to accept the INVITE (send 200 OK) once the worker joins; right now SIP ingress never answers even though the job is running. Could you please check the SIP ingress logs for that CallSid / domain and confirm why the SIP leg isn’t being accepted? Happy to provide full worker/Twilio logs if needed

I looked at this. I think you need to change your dispatch rule from

Direct

to

Individual

https://cloud.livekit.io/projects/p_/telephony/dispatch