https://livekit.io logo
Join Slack
Powered by
Hello <@U08CKJH7C12> <@U09G4AF3NFR> - I have a sup...
# telephony
p
Hello @refined-appointment-81829 @lively-winter-88668 - I have a support ticket open for a week now regarding webrtc issues. Ticket #37530. Is it possible to help fastrack this please?
The issue we are facing is - for certain calls. The livekit webrtc connection is not handled properly
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=- 8579621173113023286 1764595317 IN IP4 0.0.0.0\\r\\ns=-\\r\\nt=0 0\\r\\na=msid-semantic:WMS *\\r\\na=fingerprint:sha-256 00:7C:54:4E:3E:B3:22:34:41:30:32:FF:38:5C:FB:B1:DD:B0:3A:8C:3D:B7:21:6B:CD:FF:BB:D0:6C:28:1E:7A\\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:dpQFMiqrgMpIAMsb\\r\\na=ice-pwd:xPtKRFQNzTgngAeqeeMHupnchOibYOGu\\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:dpQFMiqrgMpIAMsb\\r\\na=ice-pwd:xPtKRFQNzTgngAeqeeMHupnchOibYOGu\\r\\n\", id: 0 })", "level": "ERROR", "name": "livekit", "pid": 2686, "job_id": "AJ_7cpaKiCSf2Tw", "timestamp": "2025-12-01T13:22:07.545982+00:00"}
{"message": "livekit::rtc_engine::rtc_session:960:livekit::rtc_engine::rtc_session - Subscriber pc state failed", "level": "ERROR", "name": "livekit", "pid": 2686, "job_id": "AJ_7cpaKiCSf2Tw", "timestamp": "2025-12-01T13:22:15.342433+00:00"}
{"message": "livekit::rtc_engine:453:livekit::rtc_engine - received session close: \"pc_state failed\" UnknownReason Resume", "level": "WARNING", "name": "livekit", "pid": 2686, "job_id": "AJ_7cpaKiCSf2Tw", "timestamp": "2025-12-01T13:22:15.342606+00:00"}
{"message": "livekit::rtc_engine:729:livekit::rtc_engine - resuming connection... attempt: 0", "level": "ERROR", "name": "livekit", "pid": 2686, "job_id": "AJ_7cpaKiCSf2Tw", "timestamp": "2025-12-01T13:22:15.342712+00:00"}
And we see the above logs.
Copy code
{"message": "process exiting", "level": "INFO", "name": "livekit.agents", "reason": "", "pid": 2686, "job_id": "AJ_7cpaKiCSf2Tw", "timestamp": "2025-12-01T13:23:04.750067+00:00"}
{"message": "process did not exit in time, killing process", "level": "ERROR", "name": "livekit.agents", "pid": 2686, "job_id": "AJ_7cpaKiCSf2Tw", "timestamp": "2025-12-01T13:24:04.749898+00:00"}
{"message": "killing process", "level": "INFO", "name": "livekit.agents", "pid": 2686, "job_id": "AJ_7cpaKiCSf2Tw", "timestamp": "2025-12-01T13:24:04.750106+00:00"}
Follow by process getting killed once the resume connection does not occur. Have also seen a case where the process indefinitely tries to reconnect and we had to manually go into the k8s container to kill the process. Would really appreciate your help here with this weird issue we are seeing 🙏
r
That issue is closed as duplicate if this thread: https://livekit-users.slack.com/archives/C07FY8WHGPM/p1763583292526179
It will be impossible to track an issue if you keep creating many different threads for the same issue. You may find this guide helpful: https://kb.livekit.io/articles/6742638954-slack-etiquette
p
Thanks a lot for responding Wilson. I would appreciate if we can reopen the support ticket as the issue is NOT resolved OR help here in slack on what the issue is and how we can mitigate it 🙏 I apologize again for posting it multiple times on slack and raising a support ticket. I wasn't getting a response on email so thought to post on slack too. Will keep this in mind for future questions.
r
p
Cool - I cross posted on that thread, we can close this thread. Thanks again for bearing with me and apologies for creating a mess here
Open in Slack
PreviousNext
Powered by