Skip to content
Callaba

What is an RTMP server?

On this page

An RTMP server is the receiving point for a live publisher. An encoder or production application sends an RTMP URL and stream key; the server accepts that session, applies its access policy, and exposes a feed for the next chosen job. It is not automatically a viewer player, CDN, recorder, or production switcher.

What an RTMP server does

A useful mental model is publisher → RTMP server → selected downstream module. The publisher may be OBS, FFmpeg, or an encoder. The published RTMP specification is preserved in a historical specification mirror. The server gives that publisher an address and credentials, then lets an operator see whether the connection and media are active. Recording, routing, monitoring, and viewer delivery each need their own configuration and acceptance check.

LayerQuestion to answer
IngestDid the assigned publisher reach the listener with the intended key?
MediaAre video, audio and bitrate usable at the receiver?
DownstreamWhich separately configured monitor, recording, route, or player should receive it?

Read the publishing address carefully

An RTMP endpoint usually combines a server address or application path with a stream name or key. Treat the key as a credential: copy it from the deployment, do not put it in a public document, and replace it if it is exposed. The port is deployment-specific; do not assume a port is reachable until the listener and firewall policy have been checked.

Choose controlled or Guest access

Controlled mode assigns Publisher and Receiver roles to the same configured stream name; the RTMP URL can therefore be identical for both roles. Guest mode uses no pre-created access rules. It deliberately opens the endpoint: choose a nonempty stream name when publishing, and use that same name to receive.

Verify the handoff in order

  1. In controlled mode, confirm the stream has the Publisher and Receiver roles; in Guest mode, confirm the open endpoint is intentional.
  2. Publish a known source and verify active publisher status plus incoming bitrate.
  3. Check picture and intended audio from the configured receiver or monitoring path.
  4. Only then test the chosen recording, route, or browser-output workflow.

If OBS reports that it is streaming but the server shows no publisher, compare the exact URL and key, then check DNS, the listener port, and the access rule. If a publisher is visible but the downstream path is blank, the ingest check has passed; investigate that downstream module rather than changing the encoder at random.

Operate the received feed

Callaba RTMP Server is the configured listener and operator-control point: create publisher and receiver access, inspect current activity, and hand a selected feed to the next operational job. Browser playback is a separate Web Player or HLS workflow; modern browsers do not natively play an RTMP URL.

Next steps

For a configured ingest workflow, inspect Callaba RTMP Server. Use the OBS RTMP guide for a sender test, RTMP protocol fundamentals for the transport boundary, or RTMP player and browser playback when the next job is viewing the feed.

Sources