Callaba
Skip to page content

Live ingest for production teams

RTMP server for live production and streaming

Take an OBS or encoder feed at a controlled RTMP endpoint, give your team clear publisher and receiver rules, and see whether the source is live before you monitor, mix, record, route, or deliver it.

Callaba RTMP Server is the ingest and access point. Create a server, copy its publisher URL and key into the source, then use the live activity view to decide what happens next.

Temporary RTMP workspace

Create a source, publish from OBS, and inspect the operator view

RTMP DEMO · 60 MINUTES

Create a temporary RTMP server

Create one temporary RTMP ingest address, publish from OBS, then open Multiview once a publisher connects.
Connection mode

Ready to create a demo

The workflow

From source to the next live-video job

One controlled entry point

Create a named RTMP Server resource and use the assigned publisher URL and stream key in the source. Publisher and receiver rules stay visible to the operator.

Useful live evidence

Review current and recent publisher or receiver activity, bitrate, region, and peer IP before the programme goes live.

More than an endpoint

An accepted feed can enter Multiview, Video Mixer, recording, routing, or a separately configured browser-delivery workflow.

Configuration

OBS or encoder: the first connection

OBS service
Custom
Server
Use the assigned publisher URL
Stream key
Use the assigned publisher key
Before going live
Check activity, bitrate, audio, and picture in the operator workflow
  1. Choose a deployment: Callaba in your AWS account, or a Linux host your team operates.
  2. Create the RTMP Server and set publisher and receiver access.
  3. Paste the assigned publisher URL and stream key into OBS or the encoder.
  4. Use the activity view, then add Multiview, Video Mixer, recording, routing, or browser delivery for the next job.

Connection access

Choose the RTMP connection rule

Both modes use the same non-empty stream name for the publisher and receiver. In controlled mode, the publisher and receiver URLs may be identical; the role rule decides how that name is used.

Controlled stream access

Callaba creates publisher and receiver role records for the stream name you configure. Choose it when the team wants to decide the stream name and who may use it before sharing the endpoint.

Guest mode

Guest mode starts with no pre-created rules. The publisher chooses a non-empty stream name and the receiver uses that same name. Anyone with the open endpoint can publish or read under that policy, so the stream name is not a credential. It is useful for a quick, temporary, or explicitly open handoff.

Continue with the exact job

Questions that change the setup

Does RTMP ingest create a browser player automatically?

No. RTMP ingest and browser delivery are separate jobs. Configure and test a Web Player or another supported delivery path after the feed has been accepted.

Can I use an RTMP Server for OBS?

Use the assigned RTMP publisher URL and key in an OBS Custom streaming configuration, then confirm activity in Callaba before adding downstream work.