In order to tell the user why a connection to a peer could not be established, more information sources need to be watched. The main one will probably be the getStats() function of the PeerConnection object.
It needs to be figured out which browsers support getStats and to which extent and which other webrtc-function can help with getting the state of a connection (e.g. as workarounds when getStats is not or not entirely supported).
Issue by farao Sunday Jan 19, 2014 at 23:45 GMT Originally opened as https://github.com/palavatv/palava-client/issues/3
In order to tell the user why a connection to a peer could not be established, more information sources need to be watched. The main one will probably be the getStats() function of the PeerConnection object.
It needs to be figured out which browsers support getStats and to which extent and which other webrtc-function can help with getting the state of a connection (e.g. as workarounds when getStats is not or not entirely supported).