SRT (Secure Reliable Transport)
SRT is Haivision-originated, SRT Alliance-promoted, open-source reliable media/data transport over UDP for contribution and backhaul across unpredictable IP networks. For IT/firewall purposes, the critical answer is that there is no universal well-known SRT port. The listener port is configured by the device, service, or cloud ingest platform, and the firewall schedule must state endpoint role, direction, address/hostname, UDP port, connection mode, and whether rendezvous or a service relay is involved.
Scope: SRT (Secure Reliable Transport) — select the deployed product/version; optional services require separate selection.
protocol · Catalog reviewed 2026-09-27
encrypted-transport-available
Infrastructure Requirements
- Configured UDP listener path
- caller/listener or rendezvous mode
- NAT/firewall policy matched to the selected mode
- measured RTT/jitter/loss/uplink headroom
- latency/recovery budget
- endpoint support for encryption/passphrase, Stream ID, statistics, FEC, or bonding where required
- encoded payload/container compatibility at the receiver or cloud ingest edge.
Network & Physical Requirements
| Port / allocation | Transport | Connection / signal flow | Feature and requirement | Evidence |
|---|---|---|---|---|
| Configured | UDP | Caller / rendezvous peer → Configured listener / rendezvous peer | Profile requirement · Core SRT contribution session SRT caller/listener or rendezvous mode Set the chosen listener/peer address and port. Media direction can differ from handshake initiator. Encryption is optional and must match at both ends. | Source checked 2026-09-27 The Caller-Listener Handshake; The Rendezvous Handshake |
Gotchas & IT Notes
- ⚠No universal SRT service port. Size bitrate, retransmission overhead and latency for loss/RTT; confirm stream ID and encryption settings.
- ⚠HTTPS provisioning or monitoring is a separate application feature.