Heartbeat mechanism?

[jadelacruz]

Hi I would like to ask if there is some kind of heartbeat mechanism in antmedia? The idea is that, we keep tracking of the stream's session connectivity through websocket?

I saw that the SDK has some kind of command called ping that constantly sending on the server, can we make an improvement and make it so that this command will also keep track of the stream's connectivity? Like when a certain stream's failed to send ping command for a certain period of time, we should consider that stream as disconnected therefore we have to disconnect to their respective conference room/ application and then the server will then send an event to related websocket channel that this user has been disconnected because of their heartbeat inactivity?

[mekya]

Hi @jadelacruz,
Thank you for this question.

In WebRTC ICE conenction, there is an embedded heartbeat mechanism in UDP packets. The ping/pong messages that we use is generally to keep the connection alive because firewalls or load balancers drop the connection if there is no activity.

So if ICE connection is disconnected for any reason, the connection drops and the user is removed from the conferencing or from the call. I mean even if the solution is not the same as you imagine, we will likely provide a solution that makes you achieve your goal.

Please let me know what exactly you would like to achieve.

Regards
Oz

[mekya]

Hi @jadelacruz,
I see. Thank you.
I can check it for you and share some results in our test server. Thank you for letting me know.

[mekya]

Hi @jadelacruz,
I've checked on my end and unfortunately I could not reproduce it.

I just would like to mention one thing. AMS does not drop connections directly if there is a networking issue because some users my reconnect in a couple of seconds in unstable network conditions. When you disconnect the network directly, AMS thinks that this user does not stop publishing gracefully and waits about 10 seconds to drop the connection fully.
You can configure this value through webRTCClientStartTimeoutMs

So my question is that do you see that user is still broadcasting after 10 seconds?

[jadelacruz]

Hello @mekya
Sad to hear that you can't replicate this behavior. For more information you can check this screenshot.
In this picture:
[No Name] - this is the conference room
Admin User - first user (connected)
Guest - second user (mobile device, disconnected to the wifi)

The Guest user has been disconnected to the internet for 5mins but it is still listed as broadcasting, as you can also see with the blue highlight, the conference room has only 1 substrack, and that is the Admin User who is still connected to the internet.

Do you have any idea where I could start debugging in order to know which causes this weird behavior?

NOTE: This behavior doesn't happen when I just closed the tab or closed the browser. This only happens when I disconnected the user from the internet.

[allevi18]

I can confirm that I have the same problem.
In addition, after reconnect on mobile devices the iceConnectionState is stuck at "new" and dataChannel doesnt open.

[flameop]

did anyone find a way to fix this? i have the same. When i test 5g>wifi switch the stream gets removed ok, but when i go Wifi>5g it doesnt. Wld really like to find a way to detect frozen streams & remove them