Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
ghost opened this issue Mar 4, 2019 · 0 comments

Comments

@ghost
Copy link

ghost commented Mar 4, 2019

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants