Skip to content

Restreaming

Besides viewers with players, a stream often has to deliver itself into other systems: to a social network over RTMP, to a partner over SRT, into the local network as a transport stream. All of it lives on the Egress tab of the stream page and works off the stream's output — with a transcoder configured, what leaves is the processed stream.

The two ways of handing the stream over differ in who establishes the connection:

  • A push — the streamer dials the receiver itself and pushes the stream. Fits social networks and any system that waits for an incoming stream.
  • SRT play — the streamer opens a listener and waits for the partner to come and take the stream.

Pushes

In the Pushes block press + Add push, name the push and pick the protocol:

  • RTMP — the receiver's URL in full, stream key included: rtmp://a.rtmp.youtube.com/live2/<key>. That is how YouTube and the other socials connect.
  • SRT — the Host and Port of the partner's SRT listener, plus Passphrase and Stream ID when needed. The streamer acts as the caller.
  • MPEG-TS/UDP — the receiver's Host and Port. The host may be a multicast group — that is how a stream is handed into an operator's LAN, to a modulator or a neighboring receiver.
  • MPEG-TS/RTP — the same MPEG-TS wrapped in RTP: the same Host and Port, with the encapsulation chosen by the push kind. Needed by receivers that expect RTP rather than bare TS over UDP.

A stream can carry several pushes — each works independently. Do not forget Save.

The Egress tab: three pushes and SRT play

Serving over SRT

The SRT play block: enable Allow SRT pull (play), set the Port and, properly, a Passphrase. The streamer opens an SRT listener on that port, and the partner takes the stream themselves by calling srt://<streamer-address>:<port> from their side.

Handy when the stream is needed by a counterparty with their own schedule and their own equipment: you hand out the address and the key, the rest is theirs.

The segment window

The Segments to keep field sets the length of the stream's live HLS/DASH window — how many recent segments the playlist lists. More segments — steadier buffering for viewers on poor networks, but a longer delay from the live edge for those who start at the window's tail. An empty field is the default.

Worth knowing

  • A push does not affect the stream's status. The status reflects the source; a fallen push receiver does not color the stream. Verify delivery on the receiving side.
  • Restreaming moves with the stream. Pushes and SRT play are part of the stream's configuration: whichever streamer runs the stream does the pushing. For SRT play that means the listener's address changes when the stream moves to another streamer — keep that in mind when handing the address to a partner.