1298413 - WebRTC: RTCPeerConnection iceServers "No STUN servers specified in nICEr registry"

Status: RESOLVED INCOMPLETE

(Core :: WebRTC, defect)

Description

[ffbugs]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36

Steps to reproduce:

Create a RTCPeerConnection on Firefox 48.0.1 or 48.0.2. Pass in a single url with stun specified.

Example javascript:

function onIceCandidate(c) {
    if(! c.candidate) {
        return;
    }
    console.log(c.candidate);
};

var iceconfig = {
iceServers: [{urls: ["stun:stun.services.mozilla.com"]}]
};
var pc1 = new RTCPeerConnection(iceconfig);

pc1.onicecandidate = onIceCandidate;
var pc2 = new RTCPeerConnection(iceconfig);

pc1.createDataChannel('chan.for.offer');
pc1.createOffer()
    .then((offer) => pc1.setLocalDescription(offer))
    .then(() => pc2.setRemoteDescription(pc1.localDescription))
    .then(() => pc2.createAnswer())
    .then((answer) => pc2.setLocalDescription(answer))
    .then(() => pc1.setRemoteDescription(pc2.localDescription))
    .then(() => { console.log(pc1.iceConnectionState) })
    .catch((e) => console.log('error=' + e.message))




Actual results:

STUN server configuration is not recognized or attempted from network perspective.

ICE(PC:... (id=53 url=...)): No STUN servers specified in nICEr registry
Couldn't fetch node 'ice.turn.server' ('registry')
ICE(PC:... (id=53 url=...)): No TURN servers specified in nICEr registry
Couldn't fetch node 'ice.forced_interface_name' ('string')
Couldn't fetch node 'ice.stun.server' ('registry')




Expected results:

Ice layer should have started STUN processing against the mozilla stun server url.

Note: This works on nightly and developer version 50.0a2 (2016-08-25). Multiprocess enabled/disabled doesn't seem to make a difference.

Comment 1

[Nils Ohlmeier [:drno]]

I copied your code into a jsfiddle here https://jsfiddle.net/6h62de25/
When I run that in 48.0.1 I get 4 console log lines like expected and one of them contains a server reflexive candidate like this:
  candidate:1 1 UDP 1685921791 98.248.214.163 37226 typ srflx raddr 10.0.1.3 rport 52415

The log message you highlighted:
  No STUN servers specified in nICEr registry
is confusing. But it is actually not harmful. It just complains that no STUN server were not loaded from the nICEr registry. But in Firefox the STUN servers are provisioned through API calls later.

Can I ask you to upload the nICEr log file you got from running this with R_LOG_LEVEL=9?

Comment 2

[Nils Ohlmeier [:drno]]

Nothing actionable here.