Hello <@U08CKJH7C12> - We closed the agent session...
# telephony
p
Hello @refined-appointment-81829 - We closed the agent session and called the delete room API for the below room ID at
Nov 03 22:18:40.450
UTC. But still the room continued to exist and the agent was resumed after 6 or 7 mins. Can you pls check what happened here on LiveKit side logs? Seeing this issue for the first time, hasn't happened before. Room ID -
RM_VZWDb2iHeZMc
Project ID -
p_3tqm7ro6kbs
r
You should use a unique room name each time
p
Are you saying there are two sessions with same name - I didn;'t find it in the dashboad. Room name is assigned uniquely by livekit - we don't assign it - we do have a template it does -
<inbound_trunk_name>_<caller_number>_<random_string_by_livekit>
. The last part by livekit makes the room name always unique. Apologies if I am missing something here
r
I guess I don't understand your issue
p
I can only see a single room with that room name - sending you a SS in DM.
r
ok, but what is the issue you are having?
p
We called the
delete_room
API at
16:48:40.450345
UTC for the above room Id. But the room was NOT deleted by LiveKit - we did not receive any error for the API call made. After 7 to 8 mins - the agent session was resumed again even though the room was deleted.
r
how was the agent session resumed?
Did you dispatch for that room again?
p
> Did you dispatch for that room again? No Pls see below logs
Copy code
{"levelname": "INFO", "name": "agent_orchestrator", "process": 13117, "event": "Deleting Room", "job_id": "AJ_i6nDQJVFibVo", "timestamp": "2025-11-03T16:48:40.450345+00:00"}
{"message": "livekit::rtc_engine:453:livekit::rtc_engine - received session close: \"signal client closed: \\\"ping timeout\\\"\" UnknownReason Resume", "level": "WARNING", "name": "livekit", "pid": 13117, "job_id": "AJ_i6nDQJVFibVo", "timestamp": "2025-11-03T16:55:08.259809+00:00"}
{"message": "livekit::rtc_engine:729:livekit::rtc_engine - resuming connection... attempt: 0", "level": "ERROR", "name": "livekit", "pid": 13117, "job_id": "AJ_i6nDQJVFibVo", "timestamp": "2025-11-03T16:55:08.260367+00:00"}
{"levelname": "INFO", "name": "agent_orchestrator", "process": 13117, "event": "Participant Disconnected",  "participant": "rtc.RemoteParticipant(sid=PA_hfqkB2nvwqBC, identity=sip_+REDACTED, name=Phone +REDACTED)", "kind": 3, "identity": "sip_+REDACTED", "disconnect_reason": 1, "job_id": "AJ_i6nDQJVFibVo",  "timestamp": "2025-11-03T16:59:25.535332+00:00"}
At
2025-11-03T16:48:40.450345+00:00
- the room deletion API was called, the client closed signal was received but the same agent job was resumed again after 7 mins.
r
The only room delete I see for
RM_VZWDb2iHeZMc
was done after the room already ended.
Room ended because SIP participant left room
p
Yes the room was ended after user left the room which was after the resuming of connection - the first delete room API did NOT do anything which is why I am reaching out here.
r
I am not see an API call to delete room before that one
p
Oh ok - but I do see API being triggered from our logs 😞 . Appreciate your help in looking into this.