Best practices for port ranges and server configuration for corporate grade networks.

[ibc (Iñaki Baz Castillo)]

@vpavlov-prime

Do you have any guidlines how to identify what is blocked (UDP, TURN servers, ports)? At this point we will try using webrtc stats, but for now it doesn’t seem so straightforward.

Honestly never thought about that.

@vpavlov-prime

If the UDP communication is blocked on the client network and the mediasoup transport is created with enableUdp , enableTcp , preferUdp all set to true - does this mean the streams will go through the mediasoup server and we won’t use TURN?

It’s the client who decides which transport use. TURN candidates (just visible for the client) will be selected if the others fail. No magic in mediasoup here. mediasoup just tells the client its candidate preferences (IPs-ports and protocols) given the order of listenIps entries and the values of preferUdp and preferTcp. Nothing else.

@vpavlov-prime

Also if in the same room (router) we have part of the peers using UDP and other using TCP (in mediasoup only, no TURN invoved) should we expect some issues (for example peers using TCP doesn’t see peers using UDP or vice versa)? Currently we see some strange warnings and errors in the mediasoup server logs (similar to ERROR:Worker worker process died unexpectedly). So if you can clear it up a bit what exactly enableUdp , enableTcp , preferUdp are meant to do it might help.

It should work without any issue at al. However it seems there is a bug in TCP we are not (yet) able to determine. Please follow this topic and specially the comment I reference.

From now on, please track this new issue in GitHub and let’s continue there:

Crash due to usage of TcpConnection after deallocated