MVCP and Xlator control port for video servers.

VDCP ports

5250 TCP

These ports are configurable in Config File:

• MVCPServer_Port

• vdcp_controller[n]_port

Tracking Hub communication

3000 UDP

Used by Tracking Hub to communicate with Viz Engine.

These ports are configurable in Config File:

• trackinghub_port

Control Ports

6100 TCP

6700 TCP

6800 TCP

55000-55015 TCP

56000-56015 TCP

Communication ports used by Control Applications (like Media Sequencer) to connect to a Viz Engine program and/or preview channel. Viz Engine’s default program and preview port is 6100.

In a single channel configuration where both program and preview output is on the same machine, the default preview port is set to 6800 to separate the program and preview channels.

In a dual channel configuration, the default program ports are 6100 and 6800 for channel one and channel two, respectively. In a dual channel configuration, when used for stereo production, the default program ports are 6700 and 6800 for channel one (left eye) and channel two (right eye), respectively.

For controlling Graphics Channels and/or Super Channels, ports 55000-55016 and 56000-56007 are used (can be changed in the config).

These ports are configurable via Config GUI.

Viz Engine Unreal Integration

6102 UDP 6104 UDP 6103 UDP

Communication ports from Viz Engine to Unreal Engine.

These ports are configurable via Config GUI.

Viz Artist

6998, ... TCP

Used to communicate with Viz Artist. Every instance opens two ports, starting with 6998 and 6999.

Shared Memory Master Port

freely configureable

These ports are configurable in Config File:

• smm_master_eng_port

Command Feedback Port

7476 UDP

Port to send feedback of commands. This port is configurable in Config File:

• command_feedback_port

Viz Engine REST service

freely configureable TCP

To control Viz Engine via REST commands

This port can be configed via Config GUI.

Extension Plugin Commands via Websockets

6900 TCP

To allow to control Viz Engine via a Websocket.

This port can be changed manually in the JSON file C:\ProgramData\vizrt\VizEngine\extensions\CommandOverWebsocket.json.

Multitouch communication

TUIO

3333 UDP

To connect to a TUIO multitouch service.

This port is configurable in Config File:

• tuio_serv

Graphic Hub

19396-19398

Ports in use when connecting to different Graphic Hub components. Since Graphic Hub version 3.0.0 and Viz Artist/Viz Engine version 3.8.2, a limited number of open network ports is required. These do not require any port exemption rules on the client side firewall configuration. However, for earlier versions, all ports must be open on the client side.

MV Network Service

50000 TCP

responsible for NMOS requests. It might be necessary to manually add this exception to an existing firewall.

netsh advfirewall firewall add rule name=    
"Matrox NMOS API"    
 protocol=TCP dir=in localport=50000 action=allow program=    
"C:\ProgramFiles\Matrox DSX-TopologyUtils\System64\mvNetworkService.exe"    
            

Multiplexer ports

50007 - 50009 TCP

Multiplexing Ports that enable Viz Engine to work on other scenes in sessions that are used for preview purposes.

50007 TCP

MUX Isolated port: All connections to this port get their own session.

50008 TCP

MUX Shared port: All connections from one single host shares one session.

50009 TCP

MUX Fixed port: Same as shared port except that allocated resources are never cleared from memory.

50010 TCP

Still Preview port: Enables a user to request a preview of the next scene to be put On Air while another scene is On Air.

These ports are configurable via Config GUI.

WebRTC Extension Plugin

9092

Can be configured in the config file:
WebrtcOut1.WebsocketPort

or via command:
CONFIGURATION*CHANNELS*WEBRTCOUT_0*PORT SET <port_number>

Mediaftp

21

Used for video transfers from Viz One to Viz Engine.

Viz One

22

TCP and UDP for logging in to the Viz One operating system (Service: SSH).

Viz World Server

102

103

102 (TCP) is a Viz World Server listener port for Viz World Client connections when Server Allocator is not in use or only has one Viz World Server running.

103 (TCP) is a Viz World Server listener port for configuration tool connections to the first Viz World Server instance (as configurations are controlled by the first server instance). See also Vizrt Maps.

Viz One

137

139

Used for SMB file sharing (Service: Netbios)

Viz One, Microsoft Bing and Imagery on Demand

80

8080

Web interface and client software. SOAP port for communication with Viz One. For download of Microsoft Bing and Imagery on Demand images (Service: HTTP).

OpenSLP

427

Service Location Protocol (SLP) based discovery and search (TCP, UDP).

Viz One

443

445

(Service: HTTPS) TCP and UDP used for SMB file sharing (Service: Microsoft-DS).

Viz One Delivery

554

Real-time Streaming Protocol (Service: TCP).

Oracle database

1521

For clients that connect to the Viz Pilot Database.

Viz One

3080

Low resolution video and index files (Service: lighttpd).

Viz Trio

6200

6210

6200 is used for controlling the Viz Trio client over a socket connection.

6210 is used by the Graphics Plug-in to establish a connection to Viz Trio.

Newsroom Component

6220

Used by the Graphics Plug-in to establish a connection to Viz Pilot’s Newsroom client.

Graphics Plugin Editor

6230

Used by the Graphics Plug-in to establish a connection to the Graphics Plug-in Editor (on Mac).

Graphics Plugin Config

6240

Used by the Graphics Plug-in to establish a connection to the Graphics Plug-in Configuration tool (on Mac).

Viz Ticker Service

6300

6301

Viz Ticker handler in the Media Sequencer connects to port 6300 for feedback from Viz Ticker Service.

Viz Ticker handler in the Media Sequencer connect to port 6301 when controlling Viz Ticker via a socket connection.

Viz Pilot

6484

Socket connection used for controlling Viz Pilot using macro commands.

Viz One

6555

Message bus port for communication with Viz One (Service: Message bus).

Preview License server

7452

For the Newsroom Component using an unlicensed Viz Engine for local preview with a connection to the Preview License server (is not the same as the Preview Server).

Viz Pilot Data Server

8177

Used to connect over HTTP with the REST interface.

Media Sequencer

8580

8594

For clients connecting to the Media Sequencer. 8580 is specifically used to connect over HTTP with the REST interface.

Viz One

8080

Used for sending key frames (Service: ardok).

Gateway

10001

10002

10540

10541

For DB notification events. For Gateway controller clients. For MOS object updates.For MOS playlist updates.

Viz World Server

10100

10200

10100 (TCP) is a Server Allocator listener port for Viz World Client connections, and is only used for clients to get connection details about Viz World Server(s). The first client connection is always diverted to port 102. In case of multiple server instances, port numbers are assigned according to a predefined schema (10101, 10102 for server instance two and three and so on). In case there is no Server Allocator, Viz World Server itself switches to port 102.

10100 (UDP) is a Viz World Server listener port for Server Allocator communication.

10200 (UDP) is a Server Allocator listener port for Viz World Server communication. Both UDP ports are internal ports used between the servers. For more information, please see the Viz World Client and Server 11.1 User Guide and later.

Viz Pilot

10640

Used by Gateway to establish a connection to Viz Pilot to send and receive updates on MOS messages (for example, items and playlists).

Graphic Hub

19396-19398

Ports in use when connecting to different Graphic Hub components. Since Graphic Hub version 3.0.0 and Viz Artist/Viz Engine version 3.8.2, a limited number of open network ports is required. These do not require any port exemption rules on the client side firewall configuration. However, for earlier versions, all ports must be open on the client side.

Connection Broker

21098

Connection to the Connection Broker configuration interface (for example, http://localhost:21098/).

Preview Server

54000

Used to connect over HTTP with the REST interface.

Codemeter Webinterface

22352

To configure the Codemeter runtime via WebInterface.