Software agent for streaming from an IP camera without a static IP

Install the agent on a Windows, Linux or ARM device. It picks up the camera's RTSP stream in the local network and sends it to rtsp.me over RTMP Push — no static IP, no port forwarding and no exposing the camera to the internet

We built a small program that can be installed on an ordinary computer, a mini PC next to the camera or a virtual machine inside your network. The agent receives the RTSP stream and sends it to rtsp.me on its own.

Builds are available for Windows, Linux and ARM. The agent is provided free of charge.

Go to installation

How to connect an IP camera without a static IP

With an ordinary RTSP connection the server must be able to reach the IP camera over the internet. That usually requires a public IP address and port mapping on the router.

The rtsp.me agent works the other way round. It normally sits in the same local network as the camera: it picks up the camera's RTSP stream at its local address and sends the video to the rtsp.me server itself over an outbound RTMP connection.

So the camera can be connected even with a dynamic IP, CGNAT or mobile internet, without exposing the camera's RTSP port to the internet.

Advantages of the agent

IP camera → local RTSP → agent → outbound RTMP Push → rtsp.me

How the agent differs from a camera's RTMP Push

If your IP camera supports RTMP Push on its own, the agent is not needed — the rtsp.me RTMP link can be entered directly in the camera settings.

The agent is intended first of all for ordinary RTSP cameras that cannot send a stream over RTMP by themselves. It receives the camera's RTSP stream inside the local network and performs the RTMP Push to rtsp.me.

Installing the agent for an IP camera on Windows

  1. Download the agent installer for Windows.
  2. Run the installer.
  3. Follow the standard steps of the setup wizard.
  4. When the installation finishes, open the agent's web interface.
Download the agent for Windows

Installing the agent for an IP camera on Linux and ARM

Download the archive for your computer's architecture:

Unpack the downloaded archive and run the installer:

tar -xzf rtspme_<version>_linux_<arch>.tar.gz
cd rtspme_<version>_linux_<arch>
sudo ./install.sh

If needed, you can change the web interface port or allow access to it from the local network:

sudo ./install.sh --port 9000
sudo ./install.sh --bind lan

Removing the agent:

sudo ./install.sh --uninstall
sudo ./install.sh --uninstall --purge

The --purge option removes the agent together with its settings.

Don't want to keep a computer running? You can buy a compact Orange Pi, install Linux and the agent on it. Choose the ARM64 build for a 64-bit system and ARMv7 for a 32-bit one. Before buying, make sure the model supports a suitable Linux distribution and has a wired or stable wireless network connection.
Installing on a VPS. The agent can also be installed on a rented Linux virtual server — the AMD64 build usually fits. In that case the camera must be reachable from the VPS over RTSP, for example at a public address or through a VPN to the site's local network.

Get the RTMP link

Before configuring the agent, prepare your personal publishing link:

  1. Log in to your rtsp.me account.
  2. Create a new camera or open the settings of an existing one.
  3. Switch the RTMP Push toggle on.
  4. Copy the RTMP link that appears, in full.
The RTMP link contains a personal publishing key. Do not place it on a website and do not share it with anyone.
Getting the RTMP Push link in the rtsp.me account
The RTMP Push link in the camera settings on rtsp.me

First sign-in

All administration of the agent is done through its web interface. On the computer where the agent is installed, open:

http://127.0.0.1:8787

On first sign-in, create a password for accessing the agent. Use a separate strong password and store it in a password manager.

By default the address 127.0.0.1 is reachable only on the computer where the agent is installed. Do not expose the web interface to the internet.

Add a stream

After creating the password, the administration panel opens:

  1. Click the button for adding a new stream.
  2. Choose a clear name for the stream.
  3. Paste the camera's local RTSP link.
  4. Paste the RTMP link you copied earlier from your rtsp.me account.
  5. Save the settings and start the stream.

Make sure the computer running the agent can see the camera at its local address and has a stable internet connection.

You can create as many streams as you like through the agent — the number of streams is limited only by your computer's resources and the bandwidth of your connection.

Adding a stream in the rtsp.me agent's web interface
Setting up a new stream in the agent

Done — the camera is streaming

Go back to your rtsp.me account. If everything is set up correctly, the camera is already streaming — live video appears in the camera list.

All that's left is to embed the player iframe on your website — the embed code is available in the camera settings.

Codec and transcoding

For streaming, we recommend setting the camera to the H.264 codec. It needs no extra transcoding and puts less load on the computer running the agent. See also the recommended IP camera settings.

If the camera outputs only H.265, the agent can transcode the stream to H.264 locally. Keep in mind that transcoding consumes CPU resources. The load depends on the resolution, frame rate and the number of simultaneous streams.

Before running H.265 permanently, check the CPU load and the stability of the stream on the chosen PC or mini PC.
Codec and transcoding settings in the rtsp.me agent
Codec and local transcoding options

Starting an RTSP stream on demand

If the site uses mobile internet or a plan with a traffic cap, enable on-demand stream start.

In this mode the agent sends video only when the stream has active viewers. The first start takes a little longer, but no outbound traffic is used while there are no viewers.

Pricing

The agent itself is distributed free of charge — installing and using it costs nothing.

You only pay for the number of views of our player, according to the rtsp.me tariffs.

Important: for streams delivered over RTMP Push, the free threshold of 100 views does not apply — views are always billed.

Frequently asked questions

Is a static IP needed?
No. The agent connects to rtsp.me itself over an outbound connection.
Do I have to open ports on the router?
No. The camera stays inside the local network, and neither port mapping nor inbound access to the RTSP port is required.
Are the camera's credentials transmitted?
No. The RTSP link, login and password are stored locally in the agent and are not sent to the rtsp.me service.
What can the agent be installed on?
On a computer, mini PC or VPS running Windows, Linux or ARM. The device needs access to the camera's RTSP stream and to the internet.
Does the agent work behind CGNAT?
Yes. The agent establishes an outbound connection to the rtsp.me server, so a public IP address and inbound access to the camera are not required.
Does the agent have to run on a computer next to the camera?
Not necessarily. The agent can run on any computer or mini PC in a local network from which the camera's RTSP stream is reachable, and also on a VPS if the camera is reachable over RTSP — for example, through a VPN.
How many streams can I create?
As many as you like — the agent itself imposes no limits. The number of streams is limited only by your computer's resources and your internet upload bandwidth.
Can I stream H.265?
Yes, but for compatibility the stream has to be transcoded locally to H.264. This can put a noticeable load on the CPU.
How do I save mobile traffic?
Enable on-demand start. The stream will be sent only when there are active viewers, but starting it will take a little longer.
Is the agent free?
Yes, the agent itself is free. You only pay for rtsp.me player views, and for RTMP Push streams the free threshold of 100 views does not apply.

Connect your local camera

Create a camera on rtsp.me, switch RTMP Push on and add the link you receive to the agent.

Open rtsp.me