Administration¶

The Administration group in the “Node” area covers the node server services, storages, hardware, license and maintenance. The screens of the group are available to the administrator role. Initial node setup is described in First start and activation.

Server Settings¶

General node parameters. The screen combines several settings groups under a single save panel:

Server: Server name, log level (global and separately for the SRT, RIST and FFmpeg libraries), log retention period, database statistics depth and tracing, log database size limit.
Mosaic: Node-wide switch for mosaic generation; the mosaic itself — Mosaic.
Meshwork: Enabling the node participation in Meshwork and its identification: node name, note, Meshwork domain, as well as the public HTTP and HTTPS ports and additional domains — the addresses at which the node is reachable from outside (Nodes behind NAT). The identity model — Node identity.
Meshwork peers: The list of peer nodes and the shared signing secret for secure exchange (Peers and secrets).
Meshwork contact (advanced): Peer polling parameters: the number of worker threads and the contact timeout.

Initial node setup — in Initial settings; Meshwork deployment — in Building a Meshwork network.

Alerter¶

Node alert trigger thresholds and their replication rules. In addition to the global alerter enable, the following are set:

stream thresholds — no-data timeout, minimum bitrate, CC error counters (“warning / error” pairs);
a separate warning on the CPU load of the worker thread that serves a stream or a DVB adapter (as a percentage);
resource thresholds — host CPU and memory, process and transcoder CPU and memory, network load, GPU, disk usage (in percent, “warning / error” pairs);
DVR storage read/write time;
if DVB reception is present — frontend signal quality thresholds (signal level, SNR, bit error rate, uncorrected blocks).

Replication of alerts across the Meshwork domain and, separately, of system hardware alerts is enabled here as well (Domain-wide replication of alerts). External delivery is configured in a separate window (Alert destinations).

The alert model is described in How an alert works, the thresholds — in Alerter settings. Active alerts are viewed on the Alerts screen.

Alert destinations¶

The external alert delivery window is opened from the Alerter screen. The channels are split across tabs; each has its own minimum event severity threshold:

Process: Execution of an external command on an alert event with a specified timeout.
Telegram: Delivery to Telegram: the bot token and the list of chat IDs.
E-mail: Delivery over SMTP: server host and port, TLS mode (STARTTLS, implicit TLS or no encryption), server certificate validation, credentials, sender and recipient addresses.

The delivery rules are described in External alert delivery.

Web server & accounts¶

Configuration of the administration panel web server and of the login accounts. The screen contains the tabs:

Server: HTTP port and host name, HTTPS enable with a separate port and CA store selection, verbose tracing. While HTTPS is disabled, the “HTTPS port” and the CA store selection are greyed out with the note “HTTPS is disabled — enable TLS to use the certificate.”; the fields respond to the toggle itself, without waiting for a save, and the entered values are not lost. Below — the details of the current TLS certificate (subject, issuer, validity period, SAN) with the actions to import the certificate and the private key and to reload TLS; with HTTPS disabled the panel shows the same note instead of the details, but the import remains available.
Accounts: Local panel login accounts and their roles — Admin, Restricted admin, Viewer (Access and roles). For each of them the login, password and role are set; entries can be added, edited and deleted. On creation the password is mandatory; on edit the password field is shown empty, and if it is left blank the password stays unchanged.

Automatic certificate issuance — on the HTTPS certificates screen; reloading TLS without a restart — also in Maintenance. Service ports and initial setup are described in Initial settings.

Streaming HTTP server¶

Configuration of the built-in HTTP server for stream delivery (OTT delivery, HLS/DASH playlists and segments). At the top — the status of the listeners (HTTP, HTTPS, HTTP/3). The following are configured:

Server: HTTP port, host name, verbose tracing.
TLS: HTTPS enable with a separate port and CA store selection. The port and the store are greyed out while HTTPS is disabled.
HTTP/3 (QUIC): HTTP/3 enable on a separate UDP port and permission for 0-RTT early data; the port and 0-RTT are greyed out while HTTP/3 itself is disabled. This block does not depend on HTTPS: HTTP/3 is a separate listener, it takes the certificate files directly and works with HTTPS disabled. The “Status” block shows exactly that: “HTTPS” may stand at “Off” while “HTTP/3” is running.

Below — the panel of the current TLS certificate with import and TLS reload. The panel follows HTTPS only, so with HTTPS disabled it stays silent even when the same certificate is served over HTTP/3. Delivery is described in OTT and DVR, the HTTP/3 transport — in HTTP/3 (QUIC).

EPG server¶

Configuration of the EPG (XMLTV) delivery service for external consumers — middleware and applications. The service enable, the port, the host name and the verbose trace, HTTPS with a separate port and CA store, and the TLS certificate panel are set here. The HTTPS port and the CA store are greyed out while the service is disabled or HTTPS is disabled. EPG access accounts and channel sets are configured separately, on the EPG Settings screen. Middleware integration is described in EPG for OTT middleware.

HTTPS certificates¶

Automatic issuance and renewal of TLS certificates via ACME (Let’s Encrypt). At the top — the status: the issuance state, the time of the last run, the ACME account and the list of issued certificates with their validity periods. The following are configured:

Automatic issuance: Enable and the contact e-mail. Enabling implies acceptance of the certificate authority terms.
Advanced: The ACME directory URL, the HTTP-01 validation port, the advance renewal period and the external account binding (EAB) parameters.

The “Issue / renew now” action starts issuance immediately. Uploading own certificates is performed on the screens of the corresponding services (Web server & accounts, Streaming HTTP server, EPG server). Enabling TLS is described in Initial settings.

DVR storages¶

DVR archive directories. Storages can be added, edited and deleted; for each of them the name, the directory path (immutable after creation), a note and the maximum disk usage are set. A separate group governs the behavior when disk space runs short: the cleanup interval, the delay and the truncation on overflow, the emergency reserve and the cleanup hysteresis. Lowering the usage limit truncates the oldest archive; deleting a storage leaves the files on disk, but the attached streams lose access to VOD. The current disk occupancy is observed on the DVR monitor screen. Archive recording and playback are described in DVR storages and OTT and DVR.

Maintenance¶

Node service operations, grouped into sections:

Node: A graceful node reboot with confirmation — briefly interrupts all streams.
TLS certificates: Re-reading the TLS certificate from disk without a restart — separately for the web server, the streaming HTTP server and the EPG server.
Configuration backup: Download of a gzip snapshot of the node configuration.
Restore: Upload of a previously saved copy: the configuration is replaced, the node is rebooted.

Files and services are described in Files and services.

Hardware¶

The detected reception hardware available to the node (read-only; the refresh button re-reads the list). Two blocks:

DVB adapters: DVB reception frontends: name, supported delivery systems, DVB API version, capabilities, frequency and symbol rate ranges, the busy flag.
CAM modules: CI/CAM slots: the inserted module and its model, the slot type and state, the CA system identifiers and the subscription (descrambling) status per program.

DVB reception is described in DVB receiver and Adapters, working with CAM and descrambling — in Descrambling. The detected transcoding devices are shown on the About screen.

License¶

Node license information: customer, license type, the limits on the number of streams and peers (0 — unlimited), demo mode, the start of validity and the licensed time. When a hardware key is used, the HASP block (key identifier and type) is shown. Permanent activation with SL/HL keys is described in Permanent activation; the behavior on license expiry — in When the annual or trial license expires.

About¶

A system summary, grouped into sections:

License: Brief license information — the details are on the License screen.
Transcoders: The detected transcoding backends: type, executable version, readiness and the list of devices. Installation of the transcoder packages — in Transcoders, backend selection — in Backends and codecs.
Build and libraries: The PSS build version and the versions of the bundled libraries, the build type.
Identification: The server name, the node and its note, the current account, the uptime and the start time, the source IP restriction.

The documentation can also be invoked from the common interface chrome (Common bar).