ICE failed in Firefox 45.0

[ajm...@cusat.ac.in]

Hi friends,

The following eror occured using janus gateway with firefox 45.0.   The about:webrtc Also shown below.

mozRTCPeerConnection { signalingState: "closed", iceGatheringState: "complete", iceConnectionState: "closed", peerIdentity: Promise, idpLoginUrl: null, onnegotiationneeded: null, onicecandidate: streamsDone/config.pc.onicecandidate(), onsignalingstatechange: null, onaddstream: streamsDone/config.pc.onaddstream(), onaddtrack: null } janus.js:1115:3
Creating offer (iceDone=false) janus.js:1540:3
Object { janus: "hangup", session_id: 1200912820, sender: 3559115736, reason: "ICE failed" }

The application is working , ie ice successfully connected in the chrome. and firefox older versions. Please help me to sort pout the problem.

Thanks

 

[Lorenzo Miniero]

I test regularly with both Firefox 45 and Firefox 48, and it definitely works. Check the Admin API for more info as to what may be causing the ICE issue.

http://www.meetecho.com/blog/understanding-the-janus-admin-api/

L.

[Lorenzo Miniero]

From a quick glance, anyway, it looks like you're using a STUN server with a private address (10.0.0.1), which makes it useless.

L.

[Lorenzo Miniero]

(sorry, meant that 10.0.0.1 is the IP the STUN server sees for you, so the STUN server is probably in your LAN as well).

[Kannan Murali]

Lorenzo:

As Ajmal mentioned, I too have experienced the same issue with FF45. All these time and even now the earlier versions of FF was working fine with the same 

STUN server configuration (which is placed in the internal network). But with FF45, it's not working. 

In fact, I was poking around for FF discussion forum about this issue and I didn't find anything related to ICE connectivity issues related to FF45. Do you know 

any insight about this issue??? 

-KMurali

[Lorenzo Miniero]

Again, FF45 works just fine for us. The problem with the poster is most likely a wrong configuration of a STUN server to us.. Not sure what's wrong with your setup, as you didn't share any information. You may also want to check the admin API for details.

Lorenzo

[Kannan Murali]

Lorenzo:

We had two different setup - one with the TURN/STUN server (let's say Setup-1) and the other setup without STUN/TURN server (Setup-2). 

To isolate the issue, I did the same test in the setup where the Setup-2 and I do see the same issue where in FF43 works fine and 

FF45 doesn't. Setup-2 is located inside our corporate net and FF43 and FF45 WebRTC clients that we used reside with the corporate network.

We are using Janus Gateway along with our application plugin. As per our application requirement, our WebRTC client side application 

module will try to establish 4 RTP sessions individually with the Janus Gateway.

I have attached the following items (Janus GW logs with debug level 7 and ice debug enabled, about:webrtc capture after the test, 

WebRTC client side logs which includes out applicaion logs also, and the wireshark capture during the test) for both FF43 and FF45:

For FF45:

janus_GW_FF45_ICE_Issue_04_13_2016.log

aboutWebrtc_FF45_ICE_Issue_04_13_2016.html

FF45_WebRTC_Client_ICE_Issue_Log_04_13_2016.txt

FF45_WebRTC_Client_ICE_Issue_04_13_2016.pcapng

For FF43:

janus_GW_FF43_ICE_Working_04_13_2016.log

aboutWebrtc_FF43_ICE_Working_04_13_2016.html

FF43_WebRTC_Client_ICE_working_Log_04_13_2016.txt

FF43_WebRTC_Client_ICE_Working_04_13_2016.pcapng

You may notice one reference about the turn server with IP address "127.0.0.1" - this mean our application will ignore the turn server

information and will pass an empty turn server array list (which means no turn/stun server configured) to janus.js file during init time.

-KMurali

[Kannan Murali]

Lorenzo:

Missed to upload the file for FF43. Here you go...

-KMurali

[Lorenzo Miniero]

Sorry, I'm abroad at the moment, so no time to look into this.

I see you've opened a bug on Mozilla's bug tracker though. Can you paste the link here for future reference?

Thanks,

Lorenzo

[Kannan Murali]

Lorenzo:

Yes, this issue seems to be a FF45 issue and I filed the following bug in Mozilla bug tracker:

Bug 1264803 - ICE fails during trickling or connectivity check stage in Firefox 45.

Looks like they have added an optimizing algorithm for ICE candidates trickling as part of the following: 

Bug 1219557 - Only pair addresses from 1918 ranges with others from the same range

and this broke the ICE candidate gathering and connection check for the private IP addresses.

Do you know or do you have any suggestion as a workaround for the condition that I have described here from Janus side???

-KMurali

[Lorenzo Miniero]

Since we can't seem to be able to replicate this (just tried an EchoTest on our demos online again using Firefox 45 and it works), not sure what I can suggest, especially as I don't know what's confusing Firefox in your case.

Lorenzo