The RTP stream will normally use 2 ports (one for video and one for audio).
The RTCP stream will normally use 2 ports (one to control video and one to control audio).
The SIP signaling will use one port (to 5060 (tcp) or 5061 (tls)).
BTW: Please note if you experience any problems with Movi over VPN, it’s usually a problem with the MTU size. The default MTU for most networks is configured to 1500 bytes. If you have set a lower MTU value than 1500 bytes on the VPN tunnel, Movi can get intermittent problems as the fragments won’t be packed as efficiently as for a network with 1500 bytes set for MTU.
Movi use 1300 MTU + headers (about 1356 bytes in total). You can define your own Movi MTU size in Windows registry, if necessary.
So my plan is to have the Movi client register to the VCS Control. The ephemeral ports in the diagrams you show are not listed in the firewall documents I have been reading. What port range needs to be added to the firewall rules and in what direction to make this work?
The signaling ephemeral port for Movi (from Movi to VCS) could be any port between 1024 and 65535, going to either 5060 (SIP) or 5061 (SIP Secure). The port selection will be determined by the operative system, e.g. Windows.
Normally, these ephemeral ports won’t be needed to be specified in your firewall (as it’s outbound traffic).
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.