How to create a live stream without a static IP

When a static IP is not an option

• the provider does not issue a static public IP or the connection goes through CGNAT;
• the organisation's security policies forbid opening inbound ports;
• there is no access to the router settings to configure port mapping;
• the site uses mobile internet or a temporary connection.

All four methods below use an outbound connection: the camera, program or device connects to the server itself, so inbound access from the internet is not needed.

Method 1. RTMP Push — the camera sends the stream itself

Any camera with RTMP Push support will do. The setup takes a few minutes:

1. Open the stream settings on rtsp.me.
2. Switch the RTMP Push toggle on.
3. The service will issue a personal publishing link.
4. Paste this link into the camera settings and click Save.

After saving, the camera will start sending the stream to the server and the broadcast becomes available right away. If the stream drops, the camera automatically restores it by itself.

The step-by-step setup is described on the “RTMP Push without a static IP” page.

Method 2. Software agent — for ordinary RTSP cameras

If the camera only speaks RTSP and does not support RTMP Push, install the free rtsp.me software agent on a computer, mini PC or virtual machine in the same local network as the camera.

The agent picks up the camera's RTSP stream at its local address and sends it to the server itself over an outbound RTMP connection. No static IP, port mapping or open ports are needed, and the camera's credentials stay local — they are never sent to the service.

• builds for Windows, Linux and ARM devices;
• as many streams as you like — limited only by the computer's resources;
• local H.265 to H.264 transcoding and on-demand stream start.

Installation and setup are described on the “Software agent for streaming from an IP camera without a static IP” page.

Method 3. Bridge — for cameras that are already installed

Bridge is a small device that is plugged into the local network, for example into a PoE switch. That is the whole setup: the box includes a card with the device ID, which is used in the RTSP link.

In the link, the local IP address of the camera you need is appended to the Bridge ID after a hyphen. The login and password belong to that local camera:

• admin — example login of the local IP camera;
• dBZp5bOcEtaGP11_ — example password of the local IP camera;
• 447cq4tq4jkzpza4 — example Bridge ID;
• 192.168.1.100 — the camera's local IP address after the hyphen;
• /ch01_sub.264 — example path of its RTSP stream.

Up to eight cameras can be connected through one Bridge. Each one uses its own local IP, login, password and stream path. Technical support will provide the exact connection format.

More about the device on the “Our streaming equipment” page.

Method 4. Ready-made camera with an ID

If the site is not up and running yet, or you simply want to replace the camera used for streaming, the easiest option is to install our camera: plug it into the network — and it is ready to work right away.

Camera link example

The details on the card from the box form the RTSP link. Below is only a structure example:

• admin — example login;
• dBZp5bOcEtaGP11_ — example password;
• 447cq4tq4jkzpza4 — example camera ID;
• /ch01_sub.264 — path of the secondary video stream.

Camera specifications on the “Our streaming equipment” page.

Which method to choose

• RTMP PushYou have, or are ready to buy, a camera with RTMP Push support
• Software agentThe camera only speaks RTSP and there is a computer or mini PC nearby
• BridgeThe cameras are already installed and only speak RTSP — nothing needs replacing
• Ready-made cameraThe site is not launched yet, or the camera needs replacing anyway
• Common to allNo static IP, DDNS, port mapping or open ports required

Frequently asked questions