RTCIceGatherer/RTCIceTransport issuesClosed per internal process

External Issue #6842709

Details

Created
Mar 11, 2016
Privacy
This issue is public.
Reports
Reported by 0 people

Sign in to watch or report this issue.

Steps to reproduce

URL:

Repro Steps:

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

or

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:

Yes

Attachments

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” to “External”

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

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

    Sign in