STUN/TURN error codes #402

aboba opened this Issue Feb 29, 2016 · 3 comments


None yet

2 participants

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?

@aboba aboba added 1.1 1.0 labels Feb 29, 2016
aboba commented Feb 29, 2016

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

aboba commented Mar 1, 2016

I would suggest that the onerror event in the RTCIceGatherer be replaced by something like this:

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 aboba added a commit that referenced this issue Mar 12, 2016
@aboba aboba STUN/TURN error codes
Fix for Issue #402
@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