How to detect participant disconnection or leaving from room #6254

[FarhodKurbonov]

Hi Ant Media Team, we have started implementation of reconnection across all our platforms (Android, iOS, Web) following @mustafaboleken suggestion from here. The way how of TRACK_LIST_UPDATED is being triggered not meeting user expectation. We tested your implementation using the official GitHub repository for the Ant Media Video Conferencing application, both locally and on your deployed Circle App.

We reviewed the AntMedia.js file in the Circle App and noticed that when a participant's internet connection is dropped, the server waits for him (does not close the websocket connection and session). However, TRACK_LIST_UPDATED is not triggered on the side of other participants. It only triggers when a client app (the one who has been having trouble with reconnection) drops the connection (closes a web browser tab or kills the app), which is predictable. In this scenario, the server closes the websocket connection and session with the room participant and triggers TRACK_LIST_UPDATED.

Is there any way for server to notify room participants about those ones who lost connection and tries to get connected?

Here's Steps to reproduce:

• User A joins the room (abc).
• User B joins the same room.
• User A turns off or physically unplugs his internet connection (WiFi/4G, etc.).

Actual Behavior:
When the internet is disconnected on User A's side, the app tries to reconnect and notifies User A which is perfect. Meanwhile, User B is unaware of what is happening on User A's side, and it appears as if User A is still online

Expected Behaviour:
When the internet is disconnected on User A's side, the app should notify User B about it. This is important because User B may continue speaking to User A, not realising that he is offline and trying to reconnect. The app should also display the reconnection status of User A ON User B's side.

Additional Info:

Server Version 2.8.2 Enterprise
Tested version of Circle App: 2.8.2 and the version officially deployed on meet.antmedia.io.

[mustafaboleken]

Hi @FarhodKurbonov,

You are right. In the current implementation, it tooks 10 seconds for server to understand someone's connection is lost.
We are currently working on handling the reconnection scenario, it's in the sprint right now. In terms of this tasks, we will try to implement adding notification for the lost connections and also recovering sceanrio in case of reconnection.

ant-media/conference-call-application#253
ant-media/conference-call-application#252