Is there a way to know from which side the call got disconnected?

It seems likely that LiveKit provides events to determine disconnection reasons, but it doesn't explicitly specify which side initiated the disconnection. According to the LiveKit documentation, a

Disconnected

event is fired when a participant is disconnected from a room, and the

DisconnectReason

can be used to understand why the disconnection occurred. However, it does not specify which side initiated the disconnection. If you need to determine which side initiated the disconnection, you might need to implement custom logic on the client-side to track user actions, such as explicitly calling a disconnect function when a user decides to leave the call. This way, you can log or handle the disconnection event with more context. Would you like more detailed information on handling disconnection events in LiveKit? Sources: - LiveKit documentation 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.