TCP/IP Port numbers used

Various Rascular products incorporate TCP/IP servers for REST APIs, etc. This document lists the default ‘listening’ port numbers used by the products. Ports used as clients when connecting to third-party systems are not shown here.

If a port number shown here clashes with other installed software an alternative free port number should be chosen.  Tools like netstat allow you to determine which ports are in use. See


RouteMaster uses the following port numbers to allow external router control from client connections. All these port numbers can be changed directly from the RouteMaster UI, and – except for WebSocket API – all other protocols can be disabled.

Protocol TCP Port Notes
BlackMagic VideoHub 9990
Kramer 2000 5002
Kramer 3000 5000
Grass Valley Native 12345
Rascular WebSocket API 81 This protocol must be enabled
Nevion Sublime 4381
Harris LRC 52116
Leitch 23
Network NCB 5020
NVision NV9000 9093
NVision router 5194
Pesa P1N 12000
Pro-bel General Remote 2007
Pro-bel General Switcher 2006
Quartz 2008
Sierra Aspen 10001
Utah RCP 3 5001
VM3000 2009
TSL UMD 40001
WebPanel Server 80

RouteMaster also uses an internal REST API for communication between the backend and frontend. Normally this uses a dynamically allocated port number, but this can be overridden using command-line options.

RouteMaster Lite

RouteMaster Lite uses a subset of the RouteMaster ports, as only Blackmagic and Websocket client protocols are supported.


The CastAway engine REST API uses port 887, and the WebSocket API uses port 886. Both can be changed from the settings file,

ViewMaster VR

ViewMaster’s internal WebServer and REST API operates on port 888 by default. This can be changed from the on-screen UI.

ViewMaster VR Pro

ViewMaster Pro includes the Multi-Head Manager, which allows multiple ViewMaster instances to be launched on each connected monitor.

The Multi-head Manager has it’s own REST API and Webserver, running on port 890 by default.

Because each ViewMaster instance has it’s own REST server, the Multi-Head manager allocates ports for these from 891 upwards, so a four-monitor system would use 891-894.


it’s possible to build Helm panels that incorporate custom HTTP and REST servers, however the port numbers used for these can be directly set in Helm Designer.