MediaConnection close event

[khashayar]

Once I close the Media connection on a peer, the remote peer doesn't receive the "close" event. as the docs says for this event:
"Emitted when either you or the remote peer closes the media connection."

Although once I call the MediaConnection.close() on a peer, the remote peer (Only on Chrome) gets the event "oniceconnectionstatechange" after a few secs and then peer.js' callback calls the connection.close() explicitly, but for remote peers on Firefox nothing happens.

[ericz]

Unfortunately AFAIK there is no way to detect the connection close on Firefox yet.

As you mentioned, oniceconnectionstatechange does not yet work on FF. Neither does the deprecated functions that I tested. I also tested the onended event on media stream, it also does not fire on FF.

Here is the relevant bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=852665

The only other solution would be for PeerJS to send a "leave" message of some sort through PeerServer but that would not work reliably with the user closing the tab etc.

[ericz]

And we don't want to use disconnecting from PeerServer as an indication of leaving because established connections should continue to work even if disconnect from PeerServer

[michelle]

Can't fix for now.

[fraserxu]

I got the similar issue while trying to listen on the close event.

By calling the peer.destroy() method, I could only get the

"PeerJS: iceConnectionState is disconnected..." message. But the peer.on('close', cb) event which listend on the other end of the server can't be fired.

peer.on('close', function() {
    console.log('on close')
})

I'm not sure if is that a good idea to add this to the peer.on('close', cb) event or something else like peer.on('destroy', cb) so that the other end could get the message and do something instead of losing the video stream without knowing what happend.

[cprakash-comtech]

I think this issue is still present in firefox, Is anyone fixing this?

[RamyaAshika]

Any updates?

[bennlich]

Looks like firefox should support the underlying event now: https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection/iceConnectionState#Browser_compatibility

[ericwooley]

This seems to still be an issue, and it's very annoying to deal with. Instead of closing the media connection, I am now having to resort to sending a websocket message that the peer is closing the audio connection.

[jbdemonte]

Still there I guess,
when a user just close its browser, its remote peers are not getting any event to close the media and clean their stuff

same issue here