My main use case for Haivision SRT Gateway is primarily for sending links from remote sites back to my production control center. A quick specific example of how I use Haivision SRT Gateway for sending links from remote sites is that because I use the hosted SRT Gateway, I don't have to worry about network configurations for port forwarding or having a public IP address, and I can call into the cloud-based SRT Gateway from a remote location and then pull that content down on my system back in the control room.
Haivision SRT Gateway is used for our live production and contribution backhaul, which helps us to secure the ingest SRT from the field cameras. It also helps us for cloud replication, which reduces the source bandwidth by using AWS as the hub to fan out the streams to multiple broadcast destinations for our organization. The remote monitoring and multi-viewing SRT features give us a listener proxy for diagnostic purposes and enable multi-viewers for our remote production environments. Our live production contribution involves sending field footage to control rooms and studios while also returning studio talkback and graphics, which gives us visibility and good low latency. Haivision SRT Gateway covers multipath redundancy and recovers packets up to 30 to 50 percent. Bandwidth efficiency is significantly lower than UDP and RDP due to the ARQ and FEC. The secure platform includes AES-256 encryption, so no VPNs or tunnels are needed. Haivision SRT Gateway provides multi-protocol conversions including SRT to RTP, RTP to FEC, RTMP, RTSP, HLC, TS, and UDP, which provides us with good real-time statistics and firewall traversal. Path redundancy features simultaneous multipath SRT streaming over primary backup networks for a maximum uptime of 99 percent. Encryption with AES is also available to ensure the content and all data is secured by 128 or 256-bit end-to-end encryption with a key management service.
Find out in this report how the two Live Streaming Platforms solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.
My main use case for Haivision SRT Gateway is primarily for sending links from remote sites back to my production control center. A quick specific example of how I use Haivision SRT Gateway for sending links from remote sites is that because I use the hosted SRT Gateway, I don't have to worry about network configurations for port forwarding or having a public IP address, and I can call into the cloud-based SRT Gateway from a remote location and then pull that content down on my system back in the control room.
Haivision SRT Gateway is used for our live production and contribution backhaul, which helps us to secure the ingest SRT from the field cameras. It also helps us for cloud replication, which reduces the source bandwidth by using AWS as the hub to fan out the streams to multiple broadcast destinations for our organization. The remote monitoring and multi-viewing SRT features give us a listener proxy for diagnostic purposes and enable multi-viewers for our remote production environments. Our live production contribution involves sending field footage to control rooms and studios while also returning studio talkback and graphics, which gives us visibility and good low latency. Haivision SRT Gateway covers multipath redundancy and recovers packets up to 30 to 50 percent. Bandwidth efficiency is significantly lower than UDP and RDP due to the ARQ and FEC. The secure platform includes AES-256 encryption, so no VPNs or tunnels are needed. Haivision SRT Gateway provides multi-protocol conversions including SRT to RTP, RTP to FEC, RTMP, RTSP, HLC, TS, and UDP, which provides us with good real-time statistics and firewall traversal. Path redundancy features simultaneous multipath SRT streaming over primary backup networks for a maximum uptime of 99 percent. Encryption with AES is also available to ensure the content and all data is secured by 128 or 256-bit end-to-end encryption with a key management service.