-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Ice connection fails, how can I know what is wrong? #4
Comments
I've faced similar issues whilst testing on the same network. However, (Known Bug) Chrome seems taking first STUN-server for ice-trickling, and it skips all others (in the moment). So, XirSys' STUN server (ports 443/80) is skipped in current chrome builds; and hopefully it'll be fixed in M39. I don't think it is an issue in RTCMultiConnection code, because second try always succeeds for such cases. Remember, connection.onfailed = function(event) {
event.peer.getConnectionStats(function(result) {
// read more here, https://cdn.webrtc-experiment.com/getConnectionStats.js
// result.connectionType
// result.audio --- for audio tracks
// result.video ---- for video tracks
});
// use `redial` method
// it is same as: connection.peers[event.userid].redial();
event.peer.redial();
// you can even use `renegotiate`
// event.peer.renegotiate();
};
// or
// connection.autoReDialOnFailure = true; P.S. Failure in ice-connectivity check isn't the only reason for |
@muaz-khan |
@muaz-khan |
@muaz-khan |
@muaz-khan |
Stop flooding. |
did you solve the problem? |
Hi!
I have an application using the latest version RTCMultiConnection and it works well with most person I test it with.
But with some people, the Ice negotiation just fails, giving me the RTCMultiConnection error "ICE connectivity check is failed. Renegotiating peer connection."
Is there a way to know what is wrong?
Thanks.
EDIT: I have tested some online demo of webrtc with these persons and it works without problem. ;(
The text was updated successfully, but these errors were encountered: