Flussonic Media Server documentation


Flussonic can connect to another Flussonic (peer), take list of running and available ondemand streams and route clients to proper peers using cluster peering mechanism.

Configuration Anchor Anchor x2

You can set Flussonic peer:

# Global settings
http 8080;
cluster_key somekey;

peer peer.example.com;

You need to set same cluster_key on all cluster hosts.

You can set multiple peers:

# Global settings
http 8080;
cluster_key somekey;

peer peer1.example.com;
peer peer2.example.com;
peer peer3.example.com;

All peers can have different streams, Flussonic will route clients to proper peers.

Redirection Anchor Anchor x2

Flussonic will redirect clients to peers when you ask for a stream.

It is a very important difference between peer and source, because source is designed for moving data via a dedicated channel from origin to edge.

Peering is designed for situations when client can take video stream from any server in a group, so servers (peers) in a group talk to each other and tell what streams do they have.

When client connects via HLS, HTTP MPEG-TS, RTSP, RTMP or opens embed.html to any of servers in a group, it may redirect to another server where this stream is really located.

Load balancing Anchor Anchor x2

Plugin iptv can balance users because it can redirect to another server if a stream is launched locally.

It can take a look at load of current and other servers and send users on another server.