Milestone XProtect VMS System Architecture Document
Milestone XProtect VMS System Architecture Document
Milestone XProtect VMS System Architecture Document
XProtect Corporate
XProtect Expert
XProtect Professional+
XProtect Express+
XProtect Essential+
System architecture document | XProtect® VMS 2020 R3
Contents
Copyright, trademarks, and disclaimer 4
Introduction 5
Server components 8
Management server 8
Recording server 8
Media database 9
Event server 9
Log server 9
SQL Server 10
Mobile server 10
Client components 11
Encryption 13
Introduction to certificates 13
MIP SDK 16
XProtect Access 17
XProtect Transact 18
XProtect LPR 18
Milestone Interconnect 19
2 | Contents
System architecture document | XProtect® VMS 2020 R3
Server communication 22
Matrix 26
Recording and playback video for XProtect Web Client and XProtect Mobile 32
Video push 33
Log server 42
Event server 43
XProtect Transact 44
XProtect LPR 45
Data collector 48
Evidence lock 50
Move hardware 51
3 | Contents
System architecture document | XProtect® VMS 2020 R3
Trademarks
Microsoft and Windows are registered trademarks of Microsoft Corporation. App Store is a service mark of Apple
Inc. Android is a trademark of Google Inc.
All other trademarks mentioned in this document are trademarks of their respective owners.
Disclaimer
This text is intended for general information purposes only, and due care has been taken in its preparation.
Any risk arising from the use of this information rests with the recipient, and nothing herein should be construed
as constituting any kind of warranty.
Milestone Systems A/S reserves the right to make adjustments without prior notification.
All names of people and organizations used in the examples in this text are fictitious. Any resemblance to any
actual organization or person, living or dead, is purely coincidental and unintended.
This product may make use of third-party software for which specific terms and conditions may apply. When that
is the case, you can find more information in the file 3rd_party_software_terms_and_conditions.txt located in your
Milestone system installation folder.
Introduction
This document was last updated for release 2020 R2.
This document contains illustrations and descriptions of communication and dataflow between the most common
system components in a distributed system.
The document shows a range of scenarios with a supporting illustration and a description of actions supplemented
by information about port numbers, protocols and bandwidth usage.
The illustrations are simplified and primarily focus on the general dataflow between system components. This
means that less important flows may have been omitted in order to reduce the level of complexity.
5 | Introduction
System architecture document | XProtect® VMS 2020 R3
The purpose of the document is to provide insight to the benefits and simplicity of using Milestone XProtect as a
VMS, including an introduction of the system components and the system architecture.
The reader of the document should have general experience with administrating an IT installation.
Depending on hardware and configuration, smaller systems with between 50~100 cameras can run on a single
server.
For systems with more than 100 cameras, Milestone recommends that you use dedicated servers for all or some
of the components.
You do not need all components in all installations. However, you can add them if the functionality they offer is
needed at a later time, for example, failover recording servers or mobile servers for hosting and providing access
to both XProtect Web Client and XProtect Mobile.
Server components
Management server
The management server is the central VMS component. It handles the system configuration, distributes the
system configuration to other system components, such as the recording servers, and facilitates user
authentication.
The system configuration is stored in an SQL database on a standard Microsoft SQL Server installed on either the
management server itself or on a separate dedicated server.
You can get failover support on the management server by installing the management server in a Microsoft
windows cluster. The cluster ensures that another server takes over the management server function in case the
first server fails.
Recording server
The recording server is responsible for all communication, recording, and event handling related to devices such
as cameras, video and audio encoders, I/O modules, and metadata sources. Examples of actions the recording
server handles:
l Retrieve video, audio, metadata and I/O event streams from the devices
l Provide operators with access to live and recorded video, audio and metadata
The recording server is also responsible for communicating with other Milestone products when using the
Milestone Interconnect™ technology. For more information, see Milestone Interconnect on page 19.
The failover recording server is responsible for taking over the recording task in case a recording server fails.
8 | Server components
System architecture document | XProtect® VMS 2020 R3
Media database
The system stores the retrieved video, audio and metadata in the customized high performance Milestone media
database which is optimized for recording and storing audio and video data.
The media database supports various unique features including multistage archiving, video grooming, encryption
and adding a digital signature to the recordings.
Event server
The event server handles the tasks related to events, alarms, maps and third-party integrations via the Milestone
Integration Platform.
Events:
l All system events are consolidated in the event server so there is a single place and interface for partners
to make integrations that use system events
l The event server offers third-party access for sending events to the system via the Generic events or
Analytics events interface
Alarms:
l The event server hosts the alarm feature, alarm logic, alarm state and handling of the alarm database. The
alarm database is stored in the same SQL database as the management server uses
Maps:
l The event server also hosts maps. You configure and use maps in the XProtect Smart Client
l You can install third-party developed plug-ins on the event server and utilize access to system events
You can get failover support on the event server by installing the event server in a Microsoft Windows Cluster. The
cluster ensures that another server takes over the event server function in case the first server fails.
Log server
The log server is responsible for storing all log messages for the entire system. The log server typically uses the
same SQL Server as the management server but has its own SQL database. Log server is also typically installed on
the same server as the management server. If you need to increase the performance of the management server
or log server, you can install the log server on a separate server and use a separate SQL Server.
The system can through the log server write three types of log messages:
9 | Server components
System architecture document | XProtect® VMS 2020 R3
l System logs: the system administrator can choose to log errors, warnings, and information, or a
combination of these. The default is to log errors only
l Audit logs: the system administrator can choose to log user activity in clients in addition to login and
administration logs
l Rule-triggered logs: the system administrator can use the rule log to create logs on specific events
SQL Server
The management server, the event server and the log server use SQL databases on one or two SQL Server
installations to store, for example, configuration, alarms, events and log messages.
The Milestone XProtect installer includes Microsoft SQL Server Express which is free edition of SQL Server.
For very large systems or systems with many transactions to and from the SQL databases, Milestone recommends
that you use a Microsoft® SQL Server® Standard or Microsoft® SQL Server® Enterprise edition of the SQL Server
on a dedicated computer on the network and on a dedicated hard disk drive that is not used for other purposes.
Installing the SQL Server on its own drive improves the entire system performance.
Mobile server
XProtect Mobile server handles logins to the system from XProtect Mobile client or XProtect Web Client.
A XProtect Mobile server distributes video streams from recording servers to XProtect Mobile client or XProtect
Web Client. This offers a secure setup where recording servers are never connected to the Internet. When a
XProtect Mobile server receives video streams from recording servers, it also handles the complex conversion of
codecs and formats allowing streaming of video on the mobile device.
10 | Server components
System architecture document | XProtect® VMS 2020 R3
Client components
The VMS is designed for large-scale operation so the Management Client is designed to run remotely from, for
example, the administrator’s computer.
When you select a function in the node tree, the settings for this node appear, typically in a second tree structure
where you can manage sub items. Once you have selected the correct item, the actual settings appear in the
properties dialog box in the upper right hand corner. The settings are grouped on various tabs if an item has many
settings.
For more information, see the administrator manual for XProtect VMS.
XProtect Smart Client is designed to run remotely from the operators’ computer and supports multiscreen usage
in full screen mode as shown below or in floating windows mode where the user can resize the windows and
move them around freely.
For more information, see the user manual for XProtect Smart Client.
For more information, see the user manual for XProtect Web Client.
On the System Requirements web page, you can find information about compatible browsers under XProtect Web
Client.
You can use the XProtect Mobile client as a remote recording device by using the device's built-in camera and the
Milestone Video Push feature. With Video Push activated, video from the device's camera is streamed back to the
VMS and recorded as if it is a standard camera.
11 | Client components
System architecture document | XProtect® VMS 2020 R3
For more information, see the XProtect Mobilewebpage and user manual.
On the System Requirements web page, you can find information about which operating systems are compatible
with XProtect Mobile.
12 | Client components
System architecture document | XProtect® VMS 2020 R3
Encryption
This section gives you an introduction to encryption and certificates.
From To
Clients, servers, and integrations that retrieve data streams from the recording server Recording server
l Before you install or upgrade to XProtect VMS 2019 R1 or newer, if you want to enable encryption during
the installation
l Before you enable encryption, if you installed XProtect VMS 2019 R1 or newer without encryption
Introduction to certificates
Hypertext Transfer Protocol Secure (HTTPS) is an extension of the Hypertext Transfer Protocol (HTTP) for secure
communication over a computer network. In HTTPS, the communication protocol is encrypted using Transport
Layer Security (TLS), or its predecessor, Secure Sockets Layer (SSL).
In XProtect VMS, the secure communication is obtained by using SSL/TLS with asymmetric encryption (RSA).
SSL/TLS uses a pair of keys—one private, one public—to authenticate, secure, and manage secure connections.
A certificate authority (CA) can issue certificates to web services on servers using a CA certificate. This certificate
contains two keys, a private key and public key. The public key is installed on the clients of a web service (service
clients) by installing a public certificate. The private key is used for signing server certificates that must be installed
on the server. Whenever a service client calls the web service, the web service sends the server certificate
including the public key to the client. The service client can validate the server certificate using the already
installed public CA certificate. The client and the server can now use the public and private server certificate to
exchange a secret key and thereby establish a secure SSL/TLS connection.
13 | Encryption
System architecture document | XProtect® VMS 2020 R3
In XProtect VMS, the following locations are where you can enable SSL/TLS encryption:
l In the communication between the management server and the recording servers
l On the recording server in the communication with clients, servers and integrations that retrieve data
streams from the recording server
Certificate distribution
The graphic illustrates the basic concept of how certificates are signed, trusted, and distributed in XProtect VMS.
A CA certificate acts as a trusted third-party, trusted by both the Subject/owner (server) and by the party that
verifies the certificate (clients) ( see Create CA certificate).
The public CA certificate must be trusted on all client computers. In this way the clients can verify the validity of
the certificates issued by the CA (see Install certificates on the clients).
The CA certificate is used to issue private server authentication certificates to the servers (see Create SSL
certificate).
The created private SSL certificates must be imported to the Windows Certificate Store on all servers (see
Import SSL certificate).
14 | Encryption
System architecture document | XProtect® VMS 2020 R3
l Issued to the server so that the server's host name is included in the certificate, either as subject (owner)
or in the list of DNS names that the certificate is issued to
l Trusted on all computers running services or applications that communicate with the service on the
servers, by trusting the CA certificate that was used to issue the SSL certificate
l The service account that runs the server must have access to the private key of the certificate on the
server.
Certificates have an expiry date. XProtect VMS will not warn you when a certificate is about
to expire. If a certificate expires, the clients will no longer trust the server with the expired
certificate and thus cannot communicate with it.
To renew the certificates, follow the steps in this guide as you did when you created
certificates.
For more information, see the certificates guide about how to secure your XProtect VMS installations.
15 | Encryption
System architecture document | XProtect® VMS 2020 R3
MIP SDK
The Milestone Integration Platform Software Development Kit (MIP SDK) is a comprehensive tool that makes it easy
to create applications, plug-ins or integrations for Milestone’s XProtect products.
MIP
The open platform is integrated in the following Milestone XProtect system components and applications:
l Management Application
l Management Server
l Event Server
MIP SDK
To have a truly open platform and a community around it Milestone provides the SDK that contains:
l A large collection of samples demonstrating different ways of using the MIP SDK
l Libraries
The MIP SDK is also used internally by Milestone software development teams.
For more information, see the MIP SDK and Develop Forum webpages.
For larger installations, the tool makes it easy and fast to remotely upgrade the components that are installed on
servers and client PCs.
For more information, see the XProtect Utilities webpage and administrator manual for Milestone Software
Manager.
XProtect Smart Wall does not require a dedicated XProtect software component itself, nor does it use a dedicated
XProtect client - all the required components are included in the standard XProtect Corporate management server
and XProtect Smart Client. It just needs a PC running XProtect Smart Client to show the Smart Wall views.
XProtect Smart Wall is included in XProtect Corporate. You can be purchase it as an add-on
for XProtect Expert.
For more information, see the XProtect Smart Wallwebpage and administrator manual.
XProtect Access
The access control integration feature introduces new functionality that makes it simple to integrate customers’
access control systems with XProtect. You get:
l A common operator user interface for multiple access control systems in XProtect Smart Client
l Map integration
The use of XProtect Access requires that you have purchased a base license that allows you
to access this feature within your XProtect system. You also need an access control door
license for each door you want to control.
You can use XProtect Access with access control systems from vendors where a vendor-
specific plug-in for XProtect Access exists. You must install this plug-in on the event server
before you can start an integration.
For more information, see the XProtect Accesswebpage and administrator manual.
XProtect Transact
XProtect Transact is an add-on to Milestone's IP video surveillance solutions XProtect VMS and XProtect
Professional VMS.
XProtect Transact is a tool for observing ongoing transactions and investigating transactions in the past. The
transactions are linked with the digital surveillance video monitoring the transactions, for example to help you
prove fraud or provide evidence against a perpetrator. There is a 1-to-1 relationship between the transaction lines
and video images.
The transaction data may originate from different types of transaction sources, typically point of sales (PoS)
systems or automated teller machines (ATM).
For more information, see the XProtect Transactwebpage and administrator manual.
XProtect LPR
XProtect LPR offers video-based content analysis (VCA) and recognition of vehicle license plates that interacts with
your surveillance system and your XProtect Smart Client.
To read the characters on a plate, XProtect LPR uses optical character recognition on images aided by specialized
camera settings.
You can combine LPR (license plate recognition) with other surveillance features such as recording and event-
based activation of outputs.
l Activate alarms
l Open gates
l Switch on lights
For more information, see the XProtect LPRwebpage and administrator manual.
Milestone Interconnect
Milestone Interconnect allows you to integrate several XProtect or Milestone Husky™ installations with one
XProtect Corporate central site. You can also install these sites, called remote sites, on mobile units, for example,
boats, busses or trains. This means that such sites do not need to be permanently connected to a network.
The central site considers the remote site as an advanced camera or multi-channel encoder with edge storage
capabilities.
Each remote site runs independently and can perform surveillance tasks as configured. Depending on the network
connections and appropriate user rights, Milestone Interconnect offers you direct live viewing of remote site
cameras and play back of remote site recordings on the central site.
It also offers you the possibility to transfer remote site recordings to the central site based on either system-
defined events, rules, schedules or by manual requests from XProtect Smart Client users.
The central site can only see and access devices that the user account specified on the remote site has access to.
This allows local system administrators on the remote sites to control which devices should be made available to
the central site and its users.
On the central site, you can view the status for the interconnected cameras, but not the entire status of the
remote site. Instead, to monitor the remote site, you can use remote site events to trigger alarms or other
notifications on the central site.
Only XProtect Corporate systems can work as central sites. All other products can act as remote sites including
XProtect Corporate. How specific the products interact in a Milestone Interconnect setup depends on the version
of the XProtect or Milestone Husky installations, the number of cameras and how devices and events are
configured on the remote site.
It is not possible to add systems with free XProtect installation as remote sites.
Public displays and TVs are often DLNA certified and connected to a network. They are able to scan the network for
media content, connect to the device, and request a media stream to their built-in media player. XProtect DLNA
Server can be discovered by certain DLNA certified devices and deliver live video streams from selected cameras
to DLNA certified devices with a media player.
The DLNA devices have a live video delay of 1-10 seconds. This is caused by different buffer
sizes in the devices.
XProtect DLNA Server must be connected to the same network as the XProtect system and the DLNA device must
be connected to the same network as XProtect DLNA Server.
For more information, see the XProtect DLNA Serverfeature brief and administrator manual.
Milestone Open Network Bridge is compliant with the parts of ONVIF Profile G and Profile S that provide access to
live and recorded video, and the ability to control pan-tilt-zoom cameras:
l Profile G - Provides support for video recording, storage, search, and retrieval. For more information, see
ONVIF Profile G Specification (https://www.onvif.org/profiles/profile-g/).
l Profile S - Provides support for streaming live video using the H.264 codec, audio streaming, and pan-tilt-
zoom (PTZ) controls. For more information, see ONVIF Profile S Specification
(https://www.onvif.org/profiles/profile-s/).
For more information about the ONVIF standard, see the ONVIF® website (https://www.onvif.org/).
ONVIF Profiles support “get” functions that retrieve data, and “set” functions that configure settings. Each function
is either mandatory, conditional, or optional. For security reasons, Milestone Open Network Bridge supports only
the mandatory, conditional, and optional “get” functions that do the following:
l Request video
l Authenticate users
l Stream video
For more information, see the Ecosystem webpage and administator manual for Milestone Open Network Bridge.
Server communication
Configurable.
XProtect Smart Client connects HTTP for an AD
Typically port 80 for an Low
1 to the management server and user and HTTPS
AD user and port 443 1 kbit/call
attempts to log in for a basic user
for a basic user
User-specific configuration is
Depends on
3 retrieved from the SQL 1433 TCP
configuration
database
Configurable. Depends on
Login is granted and the HTTP for an AD
Typically port 80 for an configuration,
4 configuration is sent to user and HTTPS
AD user and port 443 Typically 1-10
XProtect Smart Client for a basic user
for a basic user MByte
Configurable,
Configurable. TCP/IP, UDP Usage dependable, sum
Streams are sent to XProtect
2 The default port Multicast. of camera streams
Smart Client on request
is 7563 The default is viewed
TCP/IP
Device
Configurable.
Live streams from cameras retrieved Configurable. configurable.
1 Typically RTSP,
by the recording server Typically port 80 Typically 1-10
UDP, TCP/IP
Mbit/s
Configurable. Usage
The multicast stream is received by all The default port UDP IGMP dependable,
3
XProtect Smart Clients on request range is 6000- Multicast sum of camera
7000 streams viewed
Matrix
Configurable.
HTTP for AD
Information is sent to management Typically port 80 for Low
2 user and HTTPS
server an AD user and port 1 kbit/call
for basic user
443 a for basic user
Configurable,
Usage
Streams are sent to XProtect Smart Configurable. TCP/IP, UDP
dependable,
4 Client from recording server on The default port is Multicast.
sum of camera
request 7563 The default is
streams viewed
TCP/IP
Configurable.
HTTP for an AD
View updated on XProtect Smart Typically port 80 for an Low
1 user and HTTPS
Client AD user and port 443 1 kbit/call
for a basic user
for a basic user
Configurable. Low
The management server sends HTTP for an AD
Typically port 80 for an 1 kbit/call +
3 notification about view update to user and HTTPS
AD user and port 443 constant low
XProtect Smart Clients for a basic user
for a basic user use
Configurable.
HTTP for an AD
XProtect Smart Clients retrieves Typically port 80 for an Low
4 user and HTTPS
and applies the new view AD user and 443 for a 1 kbit/call
for a basic user
basic user
Configurable. The
An XProtect Smart Client user Low
1 default is 5432 TCP/IP
updates the XProtect Smart Wall view 1 kbit/call
(disabled by default)
Configurable.
The XProtect Smart Client running the HTTP for an AD
Typically 80 for an Low
4 XProtect Smart Wall retrieves and user and HTTPS
AD user and 443 for 1 kbit/call
applies new layout for a basic user
a basic user
Configurable.
Recording stream from cameras Configurable. Device configurable.
1 Typically RTSP,
retrieved by the recording server Typically port 80 Typically 1-10 Mbit/s
UDP, TCP/IP
Configurable.
Login request from XProtect Web
Typically 8081 for Low
1 Client or XProtect Mobile received HTTP or HTTPS
HTTP and 8082 for 1kbit/call
on the mobile server
HTTPS
Configurable.
HTTP for an AD
The mobile server forwards Typically 80 for an Low
2 user and HTTPS
request to the management server AD user and 443 1kbit/call
for a basic user
for a basic user
Configurable. Configuration
The login is granted and
Typically 8081 for dependent,
6 configuration is sent to XProtect HTTP or HTTPS
HTTP and 8082 for typically < 100
Web Client or XProtect Mobile
HTTPS kByte
Multicast.
direct streaming 7563 The default is streams viewed
TCP/IP
Transcoding: typically
Configurable. 50–200 kbit/s
Typically 8081 for Native: device
3 Video is streamed to the clients HTTP or HTTPS
HTTP and 8082 for configurable.
HTTPS Typically 0.05-1
Mbit/s
Recording and playback video for XProtect Web Client and XProtect
Mobile
Typically RTSP,
retrieved on the recording server Typically port 80 Typically 1-10 Mbit/s
UDP, TCP/IP
Configurable.
The stream is recorded in the Configurable. TCP/IP, UDP Usage dependable,
2 recording server database based The default is Multicast. sum of camera
on rules 7563 The default is streams viewed
TCP/IP.
Transcoding:
Configurable. typically 50–200
Recordings are sent to the mobile
Typically 8081 for kbit/s
3 server for transcoding or as HTTP or HTTPS
HTTP and 8082 Native: device
direct streaming
for HTTPS configurable
Typically 1-10 Mbit/s
Video push
Usage dependable,
Video push stream from a Configurable. resolution and frame-
device running XProtect Mobile Typically port 8081 HTTP or rate set up in the
1
is sent instantly to the mobile for HTTP and port HTTPS mobile device.
server 8082 for HTTPS Typically 0.05 – 1
Mbit/s
Usage dependable,
Configurable.
The video push stream is resolution and frame-
Typically port 40001
retrieved by recording server rate set up in the
2 (40002, 40003, if TCP/IP
using the specific video push mobile device.
many devices are
device driver Typically 0.05 – 1
present)
Mbit/s
This illustrates how XProtect Smart Client users, specified for the interconnected system, only need
to log into the management server on the central site to view video
Device
Live stream(s) from the remote site Configurable.
Configurable. configurable.
1 cameras retrieved by the remote site Typically RTSP,
Typically 80 Typically 1-10
recording server UDP, TCP/IP
Mbit/s
Usage
Live streams from the remote site Configurable.
dependable, sum
2 recording server retrieved by the The default is TCP/IP
of camera streams
central site recording server 7563*
viewed
* In XProtect Professional VMS the default port is 80, events 22331, central 1237 must be open.
The recording server on the central site connects to the remote site in the same way as a XProtect
Smart Client
Configurable,
Usage
Configurable. TCP/IP, UDP
Stream(s) are sent to XProtect Smart dependable, sum
3 The default is Multicast.
Client on request of camera streams
7563 The default is
viewed
TCP/IP
This highlights some of the different options when configuring your system recording settings
No recording - - -
These options could also be combined with cameras that have edge storage capabilities
This illustrates when recording is done on both sites. Recordings can be retrieved to the central site based on
schedule, event or request. XProtect Smart Client users, specified for the interconnected system, only need
to log into the management server on the central site to view video
* In XProtect Professional VMS the default port is 80, events 22331, central 1237 must be open. The recording
server on the central site connects to the remote site in the same way as a XProtect Smart Client
Configurable.
The XProtect DLNA Server connects to Typically port 80 HTTP for an AD
Low
1 the management server to authorize for an AD user user and HTTPS
1 kbit/call
itself with the provided credentials and port 443 for for a basic user
a basic user
Usage
XProtect DLNA Server retrieves the Configurable.
dependable,
3 requested camera video stream from The default port TCP/IP
sum of camera
the recording server is 7563
streams viewed
Usage
XProtect DLNA Server sends the live Configurable.
dependable,
4 video stream from the requested The default port HTTP
sum of camera
camera to the DLNA device is 9200
streams viewed
Only H.264 encoded camera streams are supported. If a camera supports multiple streams, only the
default stream is sent. The system administrator manages the entire XProtect DLNA Server
configuration from the Management Client. For example, selecting cameras available
Configurable.
HTTP for an AD
Changes are stored on the Typically 80 for an AD Low
2 user and HTTPS
management server user and 443 for a 10 kbit/call
for a basic user
basic user
Log server
Low
2 The log message is forwarded to the log server 22337 HTTP
1 kbit/call
Event server
Configurable.
Low
Analytics events The default port TCP/IP
1 kbit/call
is 9090
Configurable.
Low
Generic events The default ports TCP/IP, UDP
1 kbit/call
are 1234 and
1235
Low
Recording server 7563 TCP
1 kbit/call
XProtect Transact
XProtect LPR
recording server
Configurable.
The event server sends events and
The default is Low
4 alarms to XProtect Smart Client TCP/IP
22331 1 kbit/call
when there is a match
22333
The system administrator manages the entire XProtect LPR configuration, for example, setting up
events, alarms, and match lists from the Management Client. To be able to configure XProtect LPR
from the Management Client you must install the LPR plug-in on the Management Client computer
Configurable.
XProtect Smart Client requests an alarm list Low
1 The default port TCP/IP
from event server 1 kbit/call
is 22331
Low
4 New state/details stored in the SQL database 1433 TCP
1 kbit/call
Data collector
Low
5 Data returned to clients 80 HTTP
100 kbit/call
Configurable.
Configurable.
Video streamed from the TCP/IP, UDP Sum of camera
1 The default port is
recording server Multicast. streams viewed
7563
Default TCP/IP
Configurable.
HTTP for an AD
Update message distributed to Typically 80 for an Low
6 user and HTTPS for
all clients AD user and 443 for 1 kbit/call
a basic user
a basic user
Configurable.
Configurable.
Video streamed from failover TCP/IP, UDP Sum of camera
7 The default port is
recording server Multicast. streams viewed
7563
Default TCP/IP
Evidence lock
Move hardware
l Server components (services) offer their service on particular ports which is why they need to listen for
client requests on these ports. Therefore, these ports need to be opened in the Windows Firewall for
inbound and outbound connections
l Client components (clients) initiate connections to particular ports on server components. Therefore,
these ports need to be opened for outbound connections. Outbound connections are typically open by
default in the Windows Firewall
If nothing else is mentioned, ports for server components must be opened for inbound connections, and ports for
client components must be opened for outbound connections.
Do keep in mind that server components can act as clients to other server components. These are not explicitly
listed in this doc.
The port numbers are the default numbers, but this can be changed. Contact Milestone support, if you need to
change ports that are not configurable through the Management Client.
Each of the following sections list the ports that need to be opened for a particular service. To figure out which
ports need to be opened on a particular computer, you need to consider all services running on the computer.
Port
Protocol Process Connections from... Purpose
number
Port
Protocol Process Connections from... Purpose
number
Management Server
Management Showing status and managing
6473 TCP Manager tray icon,
Server service the service.
local connection only.
Communication between
Management Local connection
8080 TCP internal processes on the
server only.
server.
Port
Protocol Process Connections from... Purpose
number
1433 TCP SQL Server Event Server service Storing and retrieving events.
1433 TCP SQL Server Log Server service Storing and retrieving log entries.
Port
Protocol Process Connections from... Purpose
number
Port
Protocol Process Connections from... Purpose
number
Port
Protocol Process Connections from... Purpose
number
systems or devices.
service system. Only if the relevant data
source is enabled.
Event
XProtect Smart Client and the Configuration, events,
22331 TCP Server
Management Client alarms, and map data.
service
Event
22333 TCP Server MIP Plug-ins and applications. MIP messaging.
service
Port Connections
Protocol Process Purpose
number from...
Port Connections
Protocol Process Purpose
number from...
Server recording
recording server had been running.
Service servers.
XProtect Smart
Recording
Client, Retrieving video and audio streams,
7563 TCP Server
Management PTZ commands.
Service
Client
Recording
Recording
Server Manager Showing status and managing the
8966 TCP Server
tray icon, local service.
Service
connection only.
Recording Failover
11000 TCP Server recording Polling the state of recording servers.
Service servers
Port Connections
Protocol Process Purpose
number from...
Recording
Local connection Listening for event notifications from
65101 UDP Server
only the drivers.
service
In addition to the inbound connections to the Recording Server service listed above, the
Recording Server service establishes outbound connections to cameras, NVRs and remote
interconnected sites (Milestone Interconnect ICP).
Port
Protocol Process Connections from... Purpose
number
Failover
Merging of databases after a
Recording Failover recording
5210 TCP failover recording server had
Server servers
been running.
Service
Failover
Cameras, encoders, Listening for event messages
5432 TCP Recording
and I/O devices. from devices.
Server
Port
Protocol Process Connections from... Purpose
number
Failover
Recording Retrieving video and audio
7563 TCP XProtect Smart Client
Server streams, PTZ commands.
Service
Failover
Recording Communication between the
8844 UDP Local connection only.
Server servers.
Service
Failover
Management Server Monitoring the status of the
8990 TCP Server
service Failover Server service.
Service
Failover
Web service for internal
9001 HTTP Server Management server
communication between servers.
Service
In addition to the inbound connections to the Failover Server / Failover Recording Server
service listed above, the Failover Server / Failover Recording Server service establishes
outbound connections to the regular recorders, cameras, and for Video Push.
Port
Protocol Process Connections from... Purpose
number
Port
Protocol Process Connections from... Purpose
number
Mobile
Mobile Server Manager tray icon,
8000 TCP Server SysTray application.
local connection only.
service
Mobile
Mobile clients, Web clients, and Sending data streams;
8081 HTTP Server
Management Client. video and audio.
service
Mobile
Sending data streams;
8082 HTTPS Server Mobile clients and Web clients.
video and audio.
service
Port
Protocol Process Connections from... Purpose
number
Port Connections
Protocol Process Purpose
number from...
Milestone Open
Authentication and requests
580 TCP Network Bridge ONVIF clients
for video stream configuration.
Service
Port Connections
Protocol Process Purpose
number from...
Port Connections
Protocol Process Purpose
number from...
Port
Protocol Connections to... Purpose
number
Server service
Port
Protocol Connections to... Purpose
number
443 HTTPS Recording servers and failover Authentication, configuration, and data
Port
Protocol Connections to... Purpose
number
11000 TCP Failover recording servers Polling the state of recording servers.
11000 TCP Failover recording servers Polling the state of recording servers.
Port
Protocol Connections to... Purpose
number
Port
Protocol Connections from... Purpose
number
Port
Protocol Connections to... Purpose
number
Forwarding messages to
22337 HTTP Log server
the log server.
Port
Protocol Connections to... Purpose
number
Management Server
80 HTTP Authentication
service
Management Server
443 HTTPS Authentication of basic users.
service
8081 HTTP XProtect Mobile server Retrieving video and audio streams.
8082 HTTPS XProtect Mobile server Retrieving video and audio streams.
About Milestone
Milestone Systems is a leading provider of open platform video management software; technology that helps
the world see how to ensure safety, protect assets and increase business efficiency. Milestone Systems
enables an open platform community that drives collaboration and innovation in the development and use of
network video technology, with reliable and scalable solutions that are proven in more than 150,000 sites
worldwide. Founded in 1998, Milestone Systems is a stand-alone company in the Canon Group. For more
information, visit https://www.milestonesys.com/.