Use a RIST-capable encoder or software (e.g., FFmpeg with librist, GStreamer with ristrtpext plugin, or a hardware encoder supporting RIST) on the contribution side.
Configure the RIST sender with the receiver's IP and port; RIST Simple Profile uses MPEG-TS over RTP with an ARQ (automatic repeat request) retransmission channel on a separate port.
On the receiver side, configure the RIST input to listen on the agreed port; both sides negotiate retransmission timing based on configured buffer size and round-trip time estimates.
Enable DTLS 1.2 and pre-shared key (PSK) encryption by providing a matching passphrase on both sender and receiver for secure transmission.
Tune the buffer (latency) parameter to accommodate the expected network round-trip time plus jitter; a buffer too small causes dropped frames, too large adds unnecessary delay.
For broadcast ingest into a cloud platform, terminate RIST at a media server or cloud encoder that bridges to RTMP or HLS for further processing.
Known gotchas
RIST opens two UDP ports per session in Simple Profile (data and retransmission channels); ensure both are reachable through firewalls.
Default RIST settings provide a reasonable starting point but fine-tuning buffer and retransmission parameters requires understanding the specific network path characteristics.
RIST Main Profile adds more features (encryption negotiation, multi-link bonding) but requires both endpoints to support it; verify interoperability before assuming Main Profile.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp