The **SRT-Overlord** is a Linux-deployable application that ingests video from a wide range of sources (across multiple protocols) and forwards those feeds to an **ORBNET Streaming Engine** using **Secure Reliable Transport (SRT)**. The goal is a true **plug & play broadcaster**: it can be pre-provisioned for rapid deployment or configured on-site through a web interface, automatically discovering compatible streams and sending them _“Home”_ with minimal friction. **SRT**, originally developed and open-sourced by **Haivision**, is a modern contribution protocol that has seen rapid adoption due to its ability to deliver high-quality video over real-world networks—without requiring the heavy infrastructure typically associated with low-latency delivery. [[Understanding SRT Video Technology]] ![[z_img/e93e558b1e5ea456b4401444ee27eb0f_MD5.jpg|400]] Our custom SRT implementation is optimized for **low-latency transmission** and **network resilience**. It actively compensates for jitter and packet loss (within the limits of available bandwidth), maintaining stable delivery where traditional streaming protocols often fail or require fragile tuning. We chose SRT for this use case because it is exceptionally well suited as a **push protocol**. Multiple ingested streams can be delivered to an ORBNET Streaming Engine through a **single UDP destination port**, greatly simplifying firewall rules and remote deployments while keeping the transport efficient and predictable. In addition to media delivery, our implementation provides a **bi-directional backchannel** that allows dynamic data exchange between both ends of the connection, without opening additional UDP ports. This channel is used for stream metadata, monitoring/telemetry, and authenticated remote control. Compared to pull-based protocols like **RTSP**, SRT enables a more robust “always-on contribution” model: the edge device actively pushes streams upstream, handles reconnection logic gracefully, and stays reliable across imperfect networks. It also avoids the broader system complexity and overhead of **WebRTC** (signalling, ICE/STUN/TURN, SFUs), while remaining far more efficient for dedicated contribution workflows. Through this backchannel, the ORBNET server-side player can send commands back to the SRT-Overlord to: - control **PTZ** on **ONVIF** devices, - start/stop **local recording** where supported, - and trigger **manufacturer-specific commands** and features depending on device capabilities. <div style="page-break-after: always;"></div> # Pages - [[ORB SRT Overlord/1.0.0/Website/Status page]] - [[ORB SRT Overlord/1.0.0/Website/ONVIF Devices page|ONVIF Devices page]] - [[ORB SRT Overlord/1.0.0/Website/Config page]] - [[ORB SRT Overlord/1.0.0/Website/Open API Documentation page]]