Hello: We have our traditional audio/video conferencing application along with Janus gateway (to provide gateway functionality for WebRTC Clients). Firefox versions upto FF44 were working fine with both of our test setups, but we are getting ICE failure error with FF45 (everything else being the same) in both the test setups - I suspect that the DTLS handshaking process is not happening. We have two different setups - one with the TURN/STUN server (let's say Setup-1) and the other setup without STUN/TURN server (Setup-2). Setup-2 is located inside our corporate net and FF43/FF45 WebRTC clients that we used reside within the same corporate network. We are using Janus Gateway along with our application plugin. As per our application requirement, our FF WebRTC client side application module will try to establish 4 RTP sessions individually with the Janus Gateway. I have upload the following items (about:webrtc capture after the test, WebRTC client side logs which includes out application logs also, the Wireshark capture during the test and the Janus GW logs with ice debug enabled) for both FF43 and FF45: For FF45(Not Working Case): 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 janus_GW_FF45_ICE_Issue_04_13_2016.log For FF43(Working Case): 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 janus_GW_FF43_ICE_Working_04_13_2016.log You may notice one reference about the turn server with IP address "127.0.0.1" - this mean our WebRTC Client side application will ignore the turn server information and will pass an empty turn server array list (which means no turn/stun server configured) to client side Janus during init time.

This looks like bug 1259842 again. This seems to be causing a lot of problems...

We have WebRTC setup with WebRTC clients with only RFC1918 addresses and so we are not able to make any progress with WebRTC testing. This blocks (will delay) our application release. Any idea when this will be fixed???

This is resolved as a duplicate of bug 1259842 which means all activity is happening on 1259842. (Changing the priority of a dup has no impact in our system.) Nils is the owner of 1259842, and you can ask him for status on that bug or in irc (nick: drno).