2 ms·
Ouch! That really sucks... Is there a ticket number or blog post or something I can research to learn a bit more about the reasoning behind this change with th
by Klathmon 8y ago
Ouch! That really sucks...
Is there a ticket number or blog post or something I can research to learn a bit more about the reasoning behind this change with them?
- kaoD 8y agoNo ticket that I know of. It's mentioned in https://blog.mozilla.org/webrtc/ice-disconnected-not/ https://blog.mozilla.org/webrtc/ice-disconnected-not/ > So every 5 seconds Firefox (version >= 49) sends another binding request no matter if the ICE transport is in use or not, and it expects the other side to reply with a binding response. If it hasn’t received a binding response for 6 consecutive binding requests, in other words no reply within the last 30 seconds, it will give up and mark the transport as failed. This results in switching the ICE connection state to ‘failed‘ and stop sending any packets over that transport.