Flussonic Media Server documentation

Flussonic Agent

Flussonic Agent is a small piece of software that we can install on firmware on a camera to enable it working from NAT-ed network.

Camera will connect directly to Flussonic Watcher to port 80 or 443 bypassing any NAT and will stream video to Flussonic Media Server.

It is a best solution if you want to make a video surveillance service with zero configuration of cameras.

Agent is a competitor to white IP, port forwarding or OpenVPN and it is better than any of these solutions.

How Flussonic Agent works Anchor Anchor x2

When launched, the agent gets connected to the pre-configured server with Flussonic Watcher on it, and reports that it is alive and kicking, and is ready for video transmission.

But this video is not needed on the server with Flussonic Watcher: it’s only the system web-interface and its business logic that work there. This server is a controlling one and is called endpoint in the agent terminology.

If Watcher recognizes the agent (mutual password verification has place), it can tell the agent to connect one of the running Flussonic Media Servers, which the video will be transmitted to. In the agent terminology such Flussonic Media Server is called streampoint. Also the endpoint can cause the agent to quickly switch to another streampoint in order to work over the situation with Flussonic breakdown.

After connecting to Flussonic Media Server (streampoint) the agent waits for the command to open the connection in a similar way it is arranged in SSH tunnel. When Flussonic decides to take video from camera, it refers to the agent with the request to set TCP tunnel. Both video from RTSP and screenshots from camera can be transmitted by this tunnel.

The agent already provides the opportunity to switch between the main and the backup endpoints, as well as between the Flussonic streaming servers.

Important! After installing and configuring Endpoint, we strongly do not recommend changing its address.

Comparison Anchor Anchor x2

There may be following alternatives to Flussonic Agent:

gray IP in local network
it is a very convenient way to connect to IP camera if you have this network. Usually it means that you are building enterprise network or that you are building something like a local city network for Safe City project in a ISP. This is not applicable for OTT providers or when you need to work with routers with NAT.
white IP for camera
it is the worst possible solution. Your camera will become part of Mirai botnet before the end of day.
port forwarding
If you give IP camera to a home user or to a small business, then you need to give instructions to people how to configure router for this. It is enormous amount of work and you really don't want to do explain to a home user how to find IP of camera in DHCP leases.
OpenVPN
Some vendors offer installation of openvpn on the camera to make a cloud service. It is not a best solution, because you will have to pay twice for hardware: OpenVPN is a very CPU consumptive thing, so it will require to install one hardware server per 300-400 cameras and install second server for streaming server. Also it is not very easy to balance users between streamers.

Our Agent is better than any of above solutions because it don't require any configuration and allow to connect camera directly to Flussonic Media Server.