Mirasys VMS system components can be divided into client applications and servers.
Client applications are used to establish communication with and between the system’s servers and to send connection requests to servers.
Meanwhile, servers accept connection requests from client applications or from other servers.
Communication between the system components is implemented with the TCP/IP protocol through TCP ports 5008-5011.
Signaling And Streaming Protocols
UDP
UDP (User Datagram Protocol) is a transport-layer protocol used to stream the video feeds from the connected cameras.
The protocol is connectionless and lightweight, so it is often used to discover connectivity issues in a network. In the VMS, any connection issues are immediately noticed as a loss in the video feed.
For streaming to function properly, the network for the system needs to be well constructed, and the connections need to be reliable.
RTP
Real-time Transport Protocol (RTP) is a networking protocol used for delivering audio and video over IP networks. RTP normally runs over UDP and is used alongside RTCP.
RTCP
The RTP Control Protocol (RTCP) is a protocol that works alongside RTP. RTCP provides statistics and control information for an RTP session. It doesn’t transport any media data itself, but it partners with RTP in the delivery and packaging of multimedia data.
RTSP
RTSP (Real-Time Streaming Protocol) is used to control video streams over a network. RTSP communications between a client application and a recording VMS server send instructions on playback and play speed.
As with UDP, RTSP is a stateless communication protocol that requires a solid network to function reliably.
Usually, the interaction between the VMS and the camera goes in the following order:
VMS sends a DESCRIBE request to the camera
The camera answers with a DESCRIBE response that contains information about supported video/audio streams in SDP (Session Description Protocol) format
VMS sends a SETUP request to the camera
The camera answers with a SETUP response needed to create a new RTSP session for a specific stream
VMS sends a PLAY request to the camera
Camera answers with a PLAY response after this camera starts sending video/audio to VMS – usually, RTP (Real-Time Protocol) over UDP protocol is used for data sending
Periodically, VMS sends an OPTIONS or GET_PARAMETER request if no camera stops sending the video stream
VMS sends a TEARDOWN request when the video should be stopped
TCP
TCP (Transfer Control Protocol) is used for signaling between the devices and components of the VMS network and the Internet at large. TCP is an ordered, error-checked, and reliable signaling protocol that can function even if there are some minor faults in the network, at the cost of latency.
HTTP
HTTP (Hypertext Transfer Protocol) is used to communicate control signals for IP cameras in the system.
Many drivers use HTTP/HTTPS for setting and retrieving parameters to/from the cameras. In a direct connection, a user contacts the camera GUI with HTTP/HTTPS.
Some drivers may also use HTTP to receive motion detection data and video streams. Some camera drivers traffic PTZ signaling through HTTP.
HTTPS
HTTPS (Hypertext Transfer Protocol over TLS) is a secure version of HTTP. The protocol uses TLS to secure communications.
Other communication systems
NATS (Messaging service)
Port 4222
NATS (Neural Autonomic Transport System) is an open-source messaging system for publishing and listening to messages. The system is designed to provide performance, scalability, and ease of use. Clients connect to the NATS server and subscribe to the events they are interested in. SMServer sends two types of events to the NATS server: system events and recorder-specific events.
Mirasys VMS Ports
In all VMS installations, the following TCP ports must be open on all servers for the applications and servers to function correctly:
Port 53
The default port for the DNS service (Required by Mirasys VMS 8.5 and newer versions)
Port 5008
For signaling between SMServer and client applications, and inbound communications from clients to the SMServer
Port rule: open inbound
Port 5009
For remote connecting between DVRServer and client applications, and signaling between SMServer and DVRServer for time synchronization, settings changes, event information, etc.
Port rule: open inbound
Port 5010
For Watchdog monitoring communication between WDServer, client applications, and DVRServer
Port rule: open inbound
Port 5011
For streaming between the Streaming Service and client applications
Port rule: open inbound
Optional ports:
IP cameras and auxiliary devices may need specific ports opened. Please refer to device-specific documentation for instructions.
WebClient, Spotter Mobile, and GatewayServer specific ports
Ports 9000 and 9999
Between WebClient/Spotter Mobile and GatewayServer.
Port rule: open inbound
AVM-specific ports
Port 8084
Between SMServer and Spotter for Windows client
Port rule: open inbound
IP Camera Ports
Cameras use their own ports to keep in contact with the VMS and transmit data to the recording servers.
Please refer to device-specific documentation for instructions.
If there are firewalls between the cameras and recording VMS servers running DVRServer, the relevant ports need to be open through the firewall.
HTTP
Port 80
The default port for HTTP traffic is used to communicate with a camera’s system
Port 8080
Used by some cameras for PTZ control communications
HTTPS
Port 443
The default port for HTTPS traffic is used to securely communicate with a camera’s system
RTSP
Port 554
The default port used on the VMS to traffic stream control signals
Port 7070
Default stream control port for some camera drivers
UDP
Port 53
The default port for the DNS service (Required by Mirasys VMS 8.5 and newer versions)
Ports 3556-4556
Used on the VMS to receive feeds from the cameras. Each video stream occupies two sequential ports in the port range. To verify device port use, reading the device manufacturer’s driver read me files is highly recommended.