muaz-khan / RTCMultiConnection-Server

RTCMultiConnection socket.io server (npm install rtcmulticonnection-server)

Home Page:https://muazkhan.com:9001/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Is this a bug? Signaling Server does not detect for more than 25 seconds that the initiator has gone offline

opened this issue · comments

Hi, Muaz Khan

Thank you for your work. I hope for your help. I ran into a problem that is described below in the script. It is important that in my case the parameter connection.autoCloseEntireSession = true

Scenario:

  1. The Initiator opens the room.
  2. Two Broadcaster join the room.
  3. The Initiator breaks the Internet connection.
  4. For Broadcasters, the connection.onleave event is instantly triggered.
  5. Check on the side of the Broadcaster connection.checkPresence event indicates that the status of the room is open. Although there is no Initiator in it.
  6. Signaling Server does not understand that the initiator has disconnected from the network. We must wait a very long time (half a minute) until the signal server turns off the Initiator and then closes the room.

What should be done so that the signal server quickly learns that the initiator went offline and then signal server closed the room?