2.0 KiB
Monitoring and reports
TCP report channel
When REPORTS is enabled in the server config, the ADN DMR Peer Server listens on TCP and report clients (typically adn-monitor) connect and receive:
- CONFIG_SND / BRIDGE_SND — pickled snapshots of systems and bridges.
- BRDG_EVENT — text events for calls (
GROUP VOICE,PRIVATE VOICE, etc.).
The monitor decodes these messages, updates its CTABLE / BTABLE, and (when MySQL is configured) persists Last Heard / statistics.
Full stack: ADN Monitor overview (Python monitor, WebSocket, PHP API, optional proxy and self-service).
OpenBridge monitor semantics
GROUP VOICE,INGRESS,RX— first sight of a stream on an OpenBridge leg (debug; full visibility in logs).GROUP VOICE,START,RX— canonical start after loop control (feeds dashboard chips / CTABLE).GROUP VOICE,END,…— call end; RX/TX variants depending on direction.
The dashboard shows operational state from START (canonical); the Monitor log shows INGRESS plus START for troubleshooting mesh duplicates.
Requirements
- Network reachability from the monitor host to the server’s
REPORTS.REPORT_PORT(and the server’sREPORT_CLIENTSallow list must include the monitor if used). - adn-monitor
ADN_CONNECTION.ADN_IP/ADN_PORTmust match the server — see Monitor configuration.
Self-service and hotspots
Operators editing device options from the dashboard use the self-service flow (MySQL Clients, proxy RPTO). That is documented under Self-service; it is not part of the peer server binary alone. For hotspot proxy configuration (PROXY in adn-mon.yaml), how it binds to the peer server UDP port range, and how the process starts, see Hotspot proxy.