Closed Bug 1534125 Opened 7 years ago Closed 7 years ago

Calling getUserMedia on a page appears to affect whether or not ICE negotiation succeeds

Categories

(Core :: WebRTC: Networking, defect)

65 Branch
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: markandrusroberts, Unassigned)

References

()

Details

(Keywords: parity-chrome, testcase)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:65.0) Gecko/20100101 Firefox/65.0

Steps to reproduce:

See this fiddle: https://jsfiddle.net/h3zmv1bk/

It negotiates two RTCPeerConnections. If "Call getUserMedia first?" is checked, a call to getUserMedia will be made before negotiation; however, the resulting MediaStream and MediaStreamTrack is not added to any RTCPeerConnection. Nevertheless, it seems this affects ICE success/failure.

In Chrome, it works regardless of whether or not "Call getUserMedia first?" is checked. Neither case works in Safari for reasons I am unsure of.

Actual results:

If you just click "Start", the ICE connection will fail. I checked in Wireshark, and Firefox never sends STUN Binding Success Responses. If you check the checkbox labeled "Call getUserMedia first?" and then click "Start", the ICE connection will succeed.

Expected results:

I think ICE connection should succeed regardless of whether or not getUserMedia is called.

Has STR: --- → yes
Component: Untriaged → WebRTC: Networking
Product: Firefox → Core

This is due to https://datatracker.ietf.org/doc/draft-ietf-rtcweb-ip-handling/ When the window has capture permissions, we switch from mode 2 to mode 1, which allows more local interfaces to be used, which can make ICE more reliable.

I am not sure why your machine is unable to send UDP to itself on the default IP address. Perhaps there is some VPN stuff getting in the way?

I'm closing this as invalid as this is not due to a bug on our end, but due to differentiation in browsers allowed by the spec.

Should you find evidence that a bug in Firefox is affecting the modes Byron mentioned, feel free to re-open the bug and we'll take another look.

Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID

I am not sure why your machine is unable to send UDP to itself on the default IP address. Perhaps there is some VPN stuff getting in the way?

Oops, yes, you're right: I had a VPN active when testing. Disabling allows me to connect.

Thanks for taking a look.

You need to log in before you can comment on or make changes to this bug.