This article details all prerequisites and network flow configurations required to deploy the Miris station within your infrastructure.
SUMMARY
1/ NUDGIS AND MIRIS MANAGER SERVICES
The diagram below summarizes all required network flows. The following chapters detail their technical specifications:
Nudgis and Miris Manager Services
These rules govern exchanges between the Miris box and management platforms, publishing platforms, or network devices.
-
Miris Manager
-
Outbound:
TCP 22, 443Remote control and downloading system updates. -
Inbound:
UDP 0, 7, 9Reception of the Wake-on-LAN (WoL) magic packet sent locally by Miris Manager to boot the box remotely.
Nudgis
-
Outbound:
TCP 443Uploading recorded media to the publishing platform. -
Outbound:
TCP 1935, 1936Live video streaming via RTMP and RTMPS protocols.
Error Collection Server (34.120.62.213/32, 130.211.36.74/32)
-
Outbound:
TCP 443Automatic reporting of error logs and telemetry data.
-
Outbound:
Network Infrastructure
These rules cover core system services required for the proper functioning of the station.
-
NTP Server
-
Outbound:
UDP 123Internal clock synchronization (essential for proper station operation).
DNS Client Server
-
Outbound:
UDP 53Domain name resolution for local and cloud infrastructure.
-
Outbound:
Video and Audio Sources
These rules define the acquisition of incoming media streams according to the source protocol.
-
RTSP Sources / IP Cameras
-
Outbound:
TCP 554RTSP control session initialization and negotiation by the box. -
Inbound:
TCP/UDP (dynamic port)Reception of raw video/audio streams transported via RTP.
SRT Sources
-
Outbound (Caller Mode):
UDP (configured port)Connection initiated by Miris to an external SRT source. -
Inbound (Listener Mode):
UDP 4343-4353Reception of an SRT connection initiated by remote equipment to Miris.
NDI v4 Sources
-
Inbound:
TCP/UDP 6960-65535Dynamic port range for receiving NDIv4 streams (NDI & NDI|HX).
NDI v5 Sources
-
Inbound:
TCP/UDP 5960-5970Dedicated port range for receiving NDIv5 streams (NDI & NDI|HX).
-
Outbound:
Comments
0 comments
Article is closed for comments.