Will not re-establish a connection with a previously known peer (same signaller id)

[DamonOehlman]

The current implementation of quickconnect doesn't acknowledge a connection attempt with a previously known peer (or so it seems).

Steps to reproduce:

• Create a connection between two quickconnect instances
• On one side complete the following:
  • End calls and leave the current room (announce in an empty room)
  • Announce again in the room that you were previously connected to

The expected behaviour of the above is that a new peer connection is created between the two peers...

[DamonOehlman]

This has been partially fixed, and will now restablish a connection with a known peer as long when a peer recognises that a peer has disconnected and then reconnected in that order. The edge case where a peer disconnects, and the reconnects instantly causes an issue as the disconnection timer is fired after the reconnection occurs.

Need to come up with some way of dealing with this nicely, which may involve uniquely identifying the peer connections as well as peers.

[DamonOehlman]

Fixed in 29fdc13 - if a peer:update event is and an active call is not detected with that peer, then we create a new connection to that peer and also send the peer a /reconnect message to ensure they also attempt to reconnect.