Viz Engine
Version 3.10 | Published April 03, 2018 ©
Ports and Connections
This section contains information on the following topics:
Port Numbers
The table below lists all default server and listening port numbers that are used. It is, if possible, recommended to run the system on a network without a firewall.
|
Listener |
Port(s) |
Descriptions and comments |
|
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) |
|
Viz One |
443 445 |
(service: HTTPS)TCP & 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. |
|
Sentinel HASP Run-time Environment |
1947 |
The Sentinel HASP Run-time Environment uses port 1947 to communicate with local and remote components. This relates to Hardlock dongles used with Viz Curious Maps. |
|
Viz One |
3080 |
Low resolution video and index files (service: lighttpd). |
|
Video servers |
5250 |
MVCP and Xlator control port for video servers. Note: this port is only necessary in combination with the video server extension (service: AVCP). |
|
Viz Engine |
6100 6700 6800 55001-55016 56000-56007 |
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 in order to separate the program and preview channels. For controlling Graphics Channels and/or Superchannels, ports 55000-550016 and 56000-56007 are used. (can be changed in the config)
|
|
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). |
|
Ticker Service |
6300 6301 |
Ticker handler in the Media Sequencer connects to port 6300 for feedback from Ticker Service.Ticker handler in the Media Sequencer connect to port 6301 when controlling the 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 in order for clients to get connection details about Viz World Server(s). The first client connection will always be diverted to port 102. In case of multiple server instances port numbers are assigned according to a predefined schema (i.e. 10101, 10102 for server instance 2 and 3 and so on). In case there is no Server Allocator, Viz World Server will itself switch 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’s Guide and later. See also Vizrt Maps. |
|
Viz Pilot |
10640 |
Used by Gateway to establish a connection to Viz Pilot in order to send and receive updates on MOS messages (e.g. items and playlists). |
|
Viz Engine |
14300 |
Alternative port used to avoid conflicts with port 6100 (e.g. when using Viz Multiplexer). Port 6100 is normally used by renderers that are on air, hence, it is (e.g. when running Viz Pilot version 4 or Graphics Plugin towards Viz Artist/Engine 2.x) recommended to use another port.Port 14300 is an optional port. The default 6100 may also be used if the renderer is not used on air. |
|
Graphic Hub |
19392-19396 |
Ports in use when connecting to different Graphic Hub components. |
|
Connection Broker |
21098 |
Connection to the Connection Broker configuration interface (e.g. http://localhost:21098/) |
|
Viz Engine |
|
Ports 50007 - 50009 are all Multiplexing Ports that enable Viz Engine to work on other scenes in sessions that are used for preview purposes: |
|
|
50007 |
MUX Isolated port: All connections to this port get its own session. |
|
|
50008 |
MUX Shared port: All connections from one single host shares one session. |
|
|
50009 |
MUX Fixed port: Same as shared port except that allocated resources are never cleared from memory. |
|
|
50010 |
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. |
|
Preview Server |
54000 |
Used to connect over http with the REST interface. |
Multiplexing Ports
|
Ports |
Viz Engine |
|
All other ports |
|
|
Still Preview Port |
|
|
MUX Isolated PortMUX Shared PortMUX Fixed Port |
|
The multiplexer functionality is an integral part of Viz Engine. When using Viz Engine a session management takes place internally, with one default session for the GUI and internal/external commands, and additional sessions created on-demand for the multiplexing ports or the preview port.
With multiplex ports, other than the MUX Still Preview port, the Viz Engine state is only switched when a command is received, which means a new session is created; hence, ten consecutive commands from a client will only result in one state switch on the first command.
With the MUX Still Preview port the state is switched when a command is received and immediately switched back to the main session such that on air rendering will not be hindered in any way.
The MUX Fixed port is traditionally used by Viz Pilot Newsroom Client, and is the same as the MUX Shared Port, except that allocated resources are never cleared from memory. To avoid memory overload, it is recommended to clean up the Viz Engine regularly when this port is used.
The MUX Shared Port is a shared port where all connections from one single host shares one session. It is most often used by Viz Trio and the Newsroom Client to show preview frames.
The MUX Isolated Port is an isolated port where all connections get their own session. It is used, for example in an NLE configuration, to deliver frames to the host NLE-system when rendering or scrubbing video clips with graphics. Using this port will also suppress bounding box commands.
Note: The MUX Isolated Port cannot be used by the Newsroom Component.
All multiplexing ports are supported by all Viz Engine versions.