1.3. Technical Requirements¶
Probe¶
Supported Formats and Protocols:
¶ Type
URI example
UDP 1
udp://235.0.0.8:1234
rtp://235.0.0.10:4444
http/https (Progressive download) 1
https://storage.streamsample.ru/stream5458993
HLS
https://127.0.0.1:8080/channel25.m3u8
DASH
http://10.10.30.53:8080/channel2.mpd
SRT
srt://10.10.30.242:1010
srt://:7000
srt://user:password@192.168.1.102:7000?id=name&key=AES-128
RTMP
rtmp://182.10.30.53:1010
NDI 3
ndi://10.10.30.242:123
- 1(1,2,3)
Only MPEG-2 TS (SPTS/MPTS) is supported.
- 2
RTP over UDP (multicast) The stream should meet requirements of the specification RTP Payload Format for MPEG1/MPEG2 Video (rfc2250).
- 3
A probe build is available upon request to the technical support team.
¶ Type
URI example
File 4
file://d:/Streams/SPTS/dump45689.ts
HLS from folder
file://c:/HLS/HLS_SD.m3u8
- 4
Only MPEG-2 TS (SPTS/MPTS) is supported.
System Requirements:
Windows 8/8.1/10/11 64 bit, Server 2008/2012 64 bit.
Linux 64bit + glibc-2.17 (December 2012: Ubuntu 13.04, Debian 8, RHEL 7, CentOS 7) and higher.
Attention
Note
If the total traffic of all analyzed streams exceeds 500 Mbps, it is required for the correct probe operation to have RAM at least in the dual-channel mode. However, even with a smaller traffic volume, RAM dual-channel mode is desirable.
53/TCP/UDP (required) — DNS;
443/TCP (required) — used for communication of the probe and the server;
8443/TCP (required, default) — used for probe-server communication for Boro Solution;
3478/UDP, 19302/UDP — used for establishing the connection between the probe and a user’s browser for records downloading. WebRTC Technology;
162/UDP (default) — used for sending SNMP trap messages. Port can be configured on the SNMP notifications settings page.
Working With Server¶
For working with the server, the browser is required.
Supported Browsers:
- Chromium, version 54 and later
- Google Chrome, version 54 and later
- Mozilla Firefox, version 47 and later
For a smooth experience, make sure that your browser is updated to the latest version.