Sometimes calls end early with a message saying the caller is leaving the session, and this can happen for a few different reasons: • Server-Initiated Actions: The LiveKit server might disconnect participants if the room gets deleted or if someone is removed on purpose. • Client Disconnects: When a participant chooses to leave the session, this message will show up. • SIP Call End: If SIP participants are part of the call, functions like

closeWithHangup()

or

closeWithTimeout()

might be ending the call. • Inactivity Timeout: Calls can end if there’s been a long period of silence or no activity, depending on your settings. • Programmatic Session Closure: Your code might have logic that explicitly closes the session, which would also cause this. To figure out exactly what’s going on, you could try: 1. Checking the reason given in the disconnection event. 2. Looking through your server logs for any calls to

DeleteRoom

or

RemoveParticipant

APIs. 3. Seeing if your code has any explicit session closure logic. 4. Making sure

Room.disconnect()

is handled properly on the client side. 5. Adjusting the inactivity timeout settings if you think the call is ending due to silence. If you want, I’m here to help you dig into any of these areas — just let me know!