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

STUN/TURN error codes #402

Closed
aboba opened this Issue Feb 29, 2016 · 3 comments

Comments

Projects
None yet
2 participants
@aboba
Contributor

aboba commented Feb 29, 2016

If a STUN or TURN error is encountered when gathering, where is the STUN error code returned? Should we reference the error code web page?
http://www.iana.org/assignments/stun-parameters/stun-parameters.xhtml#stun-parameters-6

@aboba

This comment has been minimized.

Show comment
Hide comment
@aboba

aboba Feb 29, 2016

Contributor

Associated WebRTC 1.0 Issue: w3c/webrtc-pc#521

Contributor

aboba commented Feb 29, 2016

Associated WebRTC 1.0 Issue: w3c/webrtc-pc#521

@aboba

This comment has been minimized.

Show comment
Hide comment
@aboba

aboba Mar 1, 2016

Contributor

I would suggest that the onerror event in the RTCIceGatherer be replaced by something like this:
http://w3c.github.io/webrtc-pc/#idl-def-RTCPeerConnectionIceErrorEvent

Contributor

aboba commented Mar 1, 2016

I would suggest that the onerror event in the RTCIceGatherer be replaced by something like this:
http://w3c.github.io/webrtc-pc/#idl-def-RTCPeerConnectionIceErrorEvent

@ibc

This comment has been minimized.

Show comment
Hide comment
@ibc

ibc Mar 1, 2016

Contributor

+1 for the "error" event with steroids. I don't understand why most of the "error" events in W3C provide null information about the error itself.

Contributor

ibc commented Mar 1, 2016

+1 for the "error" event with steroids. I don't understand why most of the "error" events in W3C provide null information about the error itself.

@aboba aboba added the PR exists label Mar 12, 2016

aboba added a commit that referenced this issue Mar 12, 2016

@aboba aboba closed this Mar 13, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment