Which Ports Does TrueConf MCU Use

Inbound Network Ports Table

Here you can find a list of ports that need to be opened for the software-based TrueConf MCU server to work properly. To make the administration and integration of different solutions easier for you, the basic values are similar to the port ranges for TrueConf Server.

To find out how to open the ports, please refer to your OS or network equipment documentation, or contact your company’s system administrator.

Port	Transport	Protocol	Purpose	Is it possible to change?
22	TCP	SSH	To access the OS on which the MCU is installed	No
80	TCP	HTTP	To access the TrueConf MCU web interface	No
443	TCP	HTTPS	To access the TrueConf MCU web interface when using SSL certificate	No
1720	TCP	H.323	For H.323 call signaling via H.225 protocol	No
52000-52499	TCP	H.323	For H.323 call signaling via H.245 protocol	Yes
5060	UDP, TCP	SIP	For SIP call signaling	No
52500-52999	UDP, TCP	BFCP	To display content as a second stream via SIP protocol	Yes
48000-51998	UDP	RTP	To receive RTP traffic after the session is established	Yes

Outgoing Network Ports Table

These ports affect only the outbound traffic from your corporate network, which means that your corporate communications will stay secure even if outbound ports are opened. Normally, the ports for outgoing connections are already open.

Port	Transport	Protocol	Purpose	Is it possible to change?
443	TCP	HTTPS	To the registration server	No
554	TCP	RTSP	To capture a video stream from an RTSP camera	No
1935	TCP	RTMP	Required for the conference streaming	No
5060	UDP, TCP	SIP	For SIP call signaling	Yes
5900-5910	TCP	VNC	To capture a desktop using a VNC server	No
Unknown*	UDP, TCP	RTP	To send RTP traffic after the session is established	No

* The port range is unknown and depends on the opposite side.

How to reassign ports

You can change the ports by opening the Administration → Network section and then selecting the TCP/IP ports tab: