RTCIceGatherer/RTCIceTransport issuesClosed per internal process

Issue #6842709


Mar 11, 2016
This issue is public.
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce


Repro Steps:

new RTCIceGatherer({gatherPolicy: "all", iceServers:[{"url": "stun:stun.l.google.com:19302"}]});


new RTCIceGatherer({gatherPolicy: "all", iceServers:[{"urls": "stun:stun.l.google.com:19302"}]});

Expected Results:

The above methods to either succeed or provide helpful feedback on what went wrong.

Actual Results:

I’ve been playing with the ORTC support in Edge but got a lot of issues.

I can only get a new RTCGatherer to be created if I pass an empty array as iceServers. As soon as I add an ICE server I get a failure, of two different kinds according to whether I use url or urls (should be urls IIUC):

iceServers:[{"url": "stun:stun.l.google.com:19302"}] --> SCRIPT5022: InvalidAccessError

iceServers:[{"urls": "stun:stun.l.google.com:19302"}] --> SCRIPT57345: Could not complete the operation due to error c004e001

That said, even by passing an empty array, I then cannot add remote trickle candidates to the track ICE transport:

mytrack.iceTransport.addRemoteCandidate(candidate) --> SCRIPT5022: InvalidAccessError

These cryptic errors make it really hard to figure out what (if anything) I may be doing wrong. Feedback would be helpful.

Dev Channel specific:



0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Kamen M.”

      Changed Assigned To to “Venkat K.”

      Changed Assigned To from “Venkat K.” to “Frank L.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Frank L.” to “IE S.”

      Changed Status from “Confirmed”

      Changed Title from “RTCIceGatherer/RTCIceTransport issues” to “RTCIceGatherer/RTCIceTransport issuesClosed per internal process”

    • Hello,

      Thank you for providing this information about the issue. WebRTC reported this as a known issue and recommended using a TURN server for the time being. However, this may now be fixed in our latest public build. Please test this behavior in our latest stable version 14393 or the latest insider build 15063.

      Best Wishes,
      The MS Edge Team

    • I tested with stun settings with Edge build 15063, and I’m also getting SCRIPT5022: InvalidAccessError.

    • Edge 40: The issue isn’t fixed yet.
      I’m getting same error with stun+turn valid servers.
      It still happens with stun-only iceOptions or turn-only iceOptions.

      To me, it “works” only with empty array.

    • Any update on this issue ?

      I’m still getting this error with Edge build 16299…

    You need to sign in to your Microsoft account to add a comment.

    Sign in