Skip to main content
BluINFO

What are BluBØX Security's System Port Requirements

Overview

Generally speaking, BluSKY uses a sophisticated network scheme to make networking as easy as possible. However, in some cases where outbound traffic is filtered it is necessary to enable  communication on certain ports and domains. This article discusses the ports and domains that must remain unfiltered to allow BluSKY to communicate with the local hardware.

Network Requirements for BluSKY Access Control

For Access Control we need to send outbound traffic to the following hosts. 

  1.  *.blub0x.com ports 80, 443, 3001, 3010, 3011

( ' * ' means all sub-domains of this domain.)

Network Requirements for BluSKY Video Services

For our Video services we need to send outbound traffic to the following hosts (no ports open for inbound traffic are required):

  1. *.servicebus.windows.net (*means all sub-domains of this domain), ports 443 and 9354
  2. *.blob.core.windows.net, port 443
  3. *.windows.net, port 443, 9354

( ' * ' means all sub-domains of this domain.)

Client Components (outbound connections) XProtect Smart Client, Protect Management Client, Milestone Mobile server
Port Number Protocol Connections to... Purpose
80 HTTP Management server service Authentication
443 HTTPS Management server service Authentication
7563 TCP Recording Server Service Retrieving video and audio streams, PTZ commands
22331 TCP Event Server service Alarms

 

Web Client, Milestone Mobile Client
Port Number Protocol Connection to... Purpose
8081 HTTP Milestone Mobile server Retrieving video and audio streams.
8081 HTTPS Milestone Mobile server Retrieving video and audio streams.

 

Management Server Services and Processes:
Port Number  Protocol Process Connections from Purpose
80 HTTP IIS All XProtect components. Main communication, for example, authentication and configurations
443 HTTP IIS Xprotect Smart Client and the Management Client.

Authentication of basic users.

6473 TCP Management Server service Management Server tray controller, local connection only. Showing status and managing the service.
7475 TCP Management Server service Windows SNMP Service
  • Communication with the SNMP extension agent.
  • Do not use the port for other purposes even if your system does not apply SNMP.
  • In XProtect Advanced VMS 2014 systems or older, the port number was 6475
8080 TCP Management server Local connection only Communication between internal processes on the server.
9993 TCP Management Server service Recording Server services Authentication, configuration, token exchange.
12345 TCP Management Server service XProtect Smart Client
  • Communication between the system and Matrix recipients.
  • You can change the port number in the Management Client

Recording Server Services:
Port Number Protocol Process Connection from... Purpose
25 SMTP Recording Server Service Cameras, encoders, and I/O devices.

Listening for event messages from devices. The port is disabled per default.

5210 TCP Recording Server Service Failover recording servers. Merging of databases after a failover recording server had been running.
5432 TCP Recording Server Service

Cameras, encoders, and I/O devices.

Listening for event messages from devices.
7474 TCP Recording Server Service Windows SNMP service
  • Communications wit the SNMP extension agent.
  • Do not use the port for other purposes even if your system does not apply SNMP.
  • In XProtect Advanced VMS 2014 systems or older, the port number was 6474.
7563 TCP Recording Server Service XProtect Smart Client, Management Client. Retrieving video and audio streams, PTZ commands.
8966 TCP Recording Server Service Recording Server tray controller, local connections only. Show status and managing the service.
11000 TCP Recording Server Service Failover recording servers Polling the state of recording servers.
65101 UDP Recording Server Service Local connection only Listening for event notifications from the drivers.