Network configuration
How to make sure everything works in a given network environment.
The following ports are used by VT apps and if you have problems you probably need to open these:
So, basically, Video Transport works like this:
When you start the Video Transport applications they will try to connect to the signaling server, so here you need to open TCP ports 8443 and 8080(for the old versions).
When your apps are connected to the signaling server you can publish the source and receive it on the Receiver locations. So to do that, you have to be sure that UDP traffic is allowed in both locations.
If you have problems with UDP traffic in your network or high-restricted rules, then Video Transport apps will try to connect through SRT Gateways and it will require you to allow outgoing UDP 7777 traffic on your firewall.
In the case of using WebRTC in both native and Web apps, you might need to use the TURN server connection and it will require the opened 3478 TCP port.
VT 2.0 SRT/WebRTC port range customization
You can set your own UDP port range or a single port for both VT Publisher and VT Receiver p2p(ICE) SRT and WebRTC connectivity. This might help you to sort out the network problems with your local IT department in case of a highly restricted firewall or network.
This setting only affects the connections between VT Publisher and VT Receiver and has no effect on Web Preview and Web Guests connections.
To specify the port or port range go to the Global settings menu (gear symbol on the top left in both apps) and fill the field VT2.0/WebRTC Port Range(mix-max).
You can set the single port or port range through dash.
On the image above we specified the port for the Publisher, it means when VT Receiver will connect to Publisher it should be via port 53268 UDP. You can see it in the statistics bottom line.
Last updated