WebRTC Client Ice Latency issues

This article original from Http://blog.csdn.net/voipmaker reprint annotated source.

Recently optimizing the WEBRTC client call latency problem because the ice stack is taking a long time to collect the address to the probing negotiation process, which is not tolerated in VoIP, someone directly turns off the ice function, which solves the delay problem, but the NAT traversal fails, the media must go to the server, This is in some WEBRTC and SIP system Interoperability system has application value, but the call between two WEBRTC clients without ice lost the value of WEBRTC, so someone proposed a scheme called Trical-ice, the idea is that the client collects Candidate one side sent to the peer instead of collecting and then sending, in fact, the client collects some invalid candidate, such as multi-NIC case, if you can ignore this part directly in the ice part of the browser engine, the collection and detection time will be greatly reduced, Unfortunately, the browser engine also (Webkit) does not have such an interface.