Description
Our implementation contains one on one video call sessions. For following 2 sessions we observed this scenario where one is dropped from the call and the other isn’t. He we know there was some issues because our custom websocket connection was dropped but user was in the call. Can you please help me understand what exactly happened and why user was still in the call even when our custom socket was disconnected due to internet issues.
Instance 1:
Session ID: E7zQ8oJVRjOk55H0lO1/PA==
Instance 2:
Session ID: v08OJu7dQuebC9AJXfQu5Q==
Additionally: If you can please let me know what is the pingTimeout of zoom websocket connection.
Can you please help me understand what exactly happened and why user was still in the call even when our custom socket was disconnected due to internet issues.
We have a heartbeat detection mechanism. If the server does not receive a heartbeat packet from the client within 2–3 minutes, the server will remove that user.
However, when a user disconnects from the server (due to network issues or by closing/refreshing the page), we trigger a user-updated event to the users in the session with a payload containing isInFailover: true.
I have a follow up question here, for this sessions I have mentioned that the user was disconnected. What happened here is a new call was initiated that joined to the same older session, how did that happened can you please let me know ?
In above 2 sessions you must be able to see that when one user was disconnected with zoom session, 2 users joined the same session. But here the signature was unique for new users who joined the session. How did they joined the older session with new signature ?
Under the same account, if the same session name is used and an ongoing session exists, it will join that session; otherwise, a new session will be created.