Speeding Up WebRTC Connection Disabling Client Stun Server

We released way to speed up WebRTC connection establishment removing stun_server settings. When we remove stun releated settings, WebRTC implementation does not search external candidates and uses local interfaces as candidates in the created SDP in offer.

In such case SDP created by Chrome browser has local ICE candidiates only and has connection string IN with local IP.

However server is working according ICE specification and it is able to find reflexive candidate received from external user IP. Obviously local candidate pairs are not established. But reflexive candidate is established that’s why WebRTC session is established properly.

So, it’s good idea to remove stun settings at all if you do not use peer-to-peer connection. It speeds up WebRTC connection about 5 times(about 15 seconds with the stun setting and about 3-5 seconds without the stun setting). WCS3 client 423.