<@U08CKJH7C12> - seeing this new issue happen freq...
# agents
p
@refined-appointment-81829 - seeing this new issue happen frequently in
1.2.17
. Anyone else facing this issue?
Copy code
{"message": "livekit::rtc_engine::rtc_session:639:livekit::rtc_engine::rtc_session - signal_event taking too much time: Answer(SessionDescription { r#type: \"answer\", sdp: \"v=0\\r\\no=- 7371319567061571255 1763993914 IN IP4 0.0.0.0\\r\\ns=-\\r\\nt=0 0\\r\\na=msid-semantic:WMS *\\r\\na=fingerprint:sha-256 40:51:6E:4F:01:91:EE:AD:11:56:E5:97:C7:6F:DA:87:97:6F:E9:31:5E:A9:72:9F:B1:38:0E:0C:3E:2F:F8:0B\\r\\na=ice-lite\\r\\na=extmap-allow-mixed\\r\\na=group:BUNDLE 0 1\\r\\nm=audio 9 UDP/TLS/RTP/SAVPF 63 111 0 8\\r\\nc=IN IP4 0.0.0.0\\r\\na=setup:active\\r\\na=mid:0\\r\\na=ice-ufrag:zjDAQLKNYAEuIRlE\\r\\na=ice-pwd:VZXugqUbZnUHPGXgEbtGIXCfGiUwXAUO\\r\\na=rtcp-mux\\r\\na=rtcp-rsize\\r\\na=rtpmap:63 red/48000/2\\r\\na=fmtp:63 111/111\\r\\na=rtpmap:111 opus/48000/2\\r\\na=fmtp:111 minptime=10;useinbandfec=1;usedtx=1\\r\\na=rtpmap:0 PCMU/8000\\r\\na=rtpmap:8 PCMA/8000\\r\\na=extmap:4 urn:ietf:params:rtp-hdrext:sdes:mid\\r\\na=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level\\r\\na=recvonly\\r\\nm=application 9 UDP/DTLS/SCTP webrtc-datachannel\\r\\nc=IN IP4 0.0.0.0\\r\\na=setup:active\\r\\na=mid:1\\r\\na=sendrecv\\r\\na=sctp-port:5000\\r\\na=max-message-size:65535\\r\\na=ice-ufrag:zjDAQLKNYAEuIRlE\\r\\na=ice-pwd:VZXugqUbZnUHPGXgEbtGIXCfGiUwXAUO\\r\\n\", id: 0 })", "level": "ERROR", "name": "livekit", "pid": 438794, "job_id": "AJ_Lt3aQi3WD7Hv", "timestamp": "2025-11-24T14:18:44.622889+00:00"}

{"message": "livekit::rtc_engine::rtc_session:960:livekit::rtc_engine::rtc_session - Subscriber pc state failed", "level": "ERROR", "name": "livekit", "pid": 438794, "job_id": "AJ_Lt3aQi3WD7Hv", "timestamp": "2025-11-24T14:18:52.936886+00:00"}
Room IDs: 1. RM_apeCy2TJURCg 2. RM_zFJccRL3mKg9 I see
Participant left (MIGRATION)
for these cases - what does this mean?
@refined-appointment-81829 - would appreciate your help here 🙏 . The webrtc issues are happening frequently now where the process doesn't exit properly and goes into an infinite loop with the below log
Copy code
{
  "message": "livekit::rtc_engine::rtc_session:960:livekit::rtc_engine::rtc_session - Subscriber pc state failed",
  "level": "ERROR",
  "name": "livekit",
  "pid": 438794,
  "job_id": "AJ_Lt3aQi3WD7Hv",
  "timestamp": "2025-11-24T14:18:52.936886+00:00"
}
l
I'm not sure what is causing your issue - the MIGRATION indicates that the call was transferred to a different cloud server node but it looks like the client failed to handle the reconnection. I see you have raised a ticket with our support team, 37530 which is in the triage state, and that will be the best way to address your issue.
p
Thanks a lot for the response @lively-winter-88668 🙏 I have been following up with support. No response yet. Any better way to fast track this? This is happening in production and is causing an issue for us.
Also do you happen to know why this is happening -
Copy code
livekit::rtc_engine::rtc_session:639:livekit::rtc_engine::rtc_session - signal_event taking too much time: Answer(SessionDescription
@lively-winter-88668 @refined-appointment-81829 Seeing one more issue today - not allowing to delete room with
no media node available
. What should be done in this case? Should I raise a separate support ticket for this?
Copy code
{"levelname": "ERROR", "name": "agent_orchestrator", "process": 10132, "event": "Delete Room Error", "message": "", "pathname": "/home/app/agent-orchestrator/agent_orchestrator/service/call_service.py", "lineno": 2323, "error": "TwirpError(code=internal, message=no media node available, status=500, metadata={'cause': '*errors.errorString'})", , "tenant_id": "stg_use2_000", "call_id": "call_AJ_L93o7L2Mc8zN", "exc_info": "Traceback (most recent call last):\n  File \"/home/app/agent-orchestrator/agent_orchestrator/service/call_service.py\", line 2309, in delete_room\n    await self.job_ctx.api.room.delete_room(\n  File \"/usr/local/lib/python3.11/site-packages/livekit/api/room_service.py\", line 108, in delete_room\n    return await self._client.request(\n           ^^^^^^^^^^^^^^^^^^^^^^^^^^^\n  File \"/usr/local/lib/python3.11/site-packages/livekit/api/twirp_client.py\", line 129, in request\n    raise TwirpError(\nlivekit.api.twirp_client.TwirpError: TwirpError(code=internal, message=no media node available, status=500, metadata={'cause': '*errors.errorString'})", "timestamp": "2025-11-25T15:10:26.807510+00:00"}
r
What do you mean by:
raise a separate support ticket
p
Thanks for responding CWilson 🙏 . I had raised a support ticket for
Subscriber pc state failed
issue. The delete API error seems like a new issue -
TwirpError(code=internal, message=no media node available, status=500, metadata={'cause': '*errors.errorString'}
- so thought of raising a new support ticket
r
Where di you raise this ticket?
p
Over email - support@livekit.io
r
I see. And that is for version
1.2.17
?
p
Yes
r
why are you using an old version?
p
We haven't migrated to the new version yet. But the issue isn't stemming from the old version right? It is stemming from livekit cloud? For issue 1 - there is some participant migration For issue 2 - delete API is not working
r
How often is this
no media node available
happening? Was it just a burst or is it still happening?
p
The
no media node available
occurred for this room Id -
RM_bETA8woSrcWV
So far this was the call observed
r
So you only saw it once?
p
Yes - only once so far.
👍🏼 1