proud-match-31207
11/24/2025, 2:22 PM1.2.17 . Anyone else facing this issue?
{"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"}proud-match-31207
11/24/2025, 3:21 PMParticipant left (MIGRATION) for these cases - what does this mean?proud-match-31207
11/24/2025, 6:10 PM{
"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"
}lively-winter-88668
11/25/2025, 10:18 AMproud-match-31207
11/25/2025, 10:19 AMproud-match-31207
11/25/2025, 10:21 AMlivekit::rtc_engine::rtc_session:639:livekit::rtc_engine::rtc_session - signal_event taking too much time: Answer(SessionDescriptionproud-match-31207
11/25/2025, 3:30 PMno media node available. What should be done in this case? Should I raise a separate support ticket for this?
{"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"}refined-appointment-81829
11/25/2025, 4:15 PMraise a separate support ticket
proud-match-31207
11/25/2025, 4:17 PMSubscriber 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 ticketrefined-appointment-81829
11/25/2025, 4:17 PMproud-match-31207
11/25/2025, 4:18 PMrefined-appointment-81829
11/25/2025, 4:18 PM1.2.17?proud-match-31207
11/25/2025, 4:18 PMrefined-appointment-81829
11/25/2025, 4:18 PMproud-match-31207
11/25/2025, 4:19 PMrefined-appointment-81829
11/25/2025, 6:06 PMno media node available happening? Was it just a burst or is it still happening?proud-match-31207
11/25/2025, 6:18 PMno media node available occurred for this room Id - RM_bETA8woSrcWV
So far this was the call observedrefined-appointment-81829
11/25/2025, 7:36 PMproud-match-31207
11/25/2025, 7:37 PM