media server logo
PricingSign inLaunch RTMP server
Operator documentation

RTMP server operations

Use this runbook to operate RTMP ingest with deliberate publisher, receiver and guest access plus live connection visibility. It keeps the UI task, verification and automation path together.

UIStreaming servers → RTMP servers

What this solves

This procedure gives an operator one controlled path to operate RTMP ingest with deliberate publisher, receiver and guest access plus live connection visibility.

When to use it

Use it during initial setup, a planned change or incident recovery when you need to operate RTMP ingest with deliberate publisher, receiver and guest access plus live connection visibility.

Dashboard path

Streaming servers → RTMP serversRoute/rtmp-servers/list

Prerequisites

  • Administrator access to the Callaba instance and permission to change this module.

  • A maintenance window or a non-production resource plus a real test source or client.

  • A record of the current values, allocated ports and credentials before you save changes.

Steps in the Callaba UI

  1. 01

    In the dashboard sidebar, follow Streaming servers → RTMP servers. Open the source-backed route /rtmp-servers/list.

  2. 02

    Before changing RTMP server operations, record these current values: server_port, stream_control_type, stream_id, access_settings.

  3. 03

    In RTMP server operations, set server_port, stream_control_type, stream_id, access_settings so you can operate RTMP ingest with deliberate publisher, receiver and guest access plus live connection visibility. Keep unrelated values unchanged.

  4. 04

    Run Save [creating-form-save] → Start [START]. Wait for the form or listing to settle before testing another variable.

  5. 05

    Use a real source, destination or browser client and confirm these live signals: streams_count, publishers_count, receivers_count, input_bitrate_kbps, output_bitrate_kbps, address, country.

Controls to review
  • server_port
  • stream_control_type
  • stream_id
  • access_settings
Actions to run
  • Savecreating-form-save
  • StartSTART
Signals to verify
  • streams_count
  • publishers_count
  • receivers_count
  • input_bitrate_kbps
  • output_bitrate_kbps
  • address
  • country

Expected result

The runbook is complete when Save [creating-form-save] → Start [START] succeeds and a real workflow reports streams_count, publishers_count, receivers_count, input_bitrate_kbps, output_bitrate_kbps, address, country.

Troubleshooting

The saved change does not appear

Confirm the save response, refresh the module once and compare the visible values with the record made before the change. Correct validation errors before retrying.

The connection or playback path fails

Check the exact host, port, protocol, credentials and firewall path used by the real client. Test one source and one destination before restoring the full workflow.

The module starts but health is unstable

Return to the last known working values, inspect live statistics and process errors, then reintroduce one change at a time.

Product page / Exact API reference

Continue with the commercial product context or automate the same operation from its verified API endpoint.

Product pageCallaba RTMP ServerExact API referenceExact API reference 1 · create-rtmp-serverExact API referenceExact API reference 2 · get-rtmp-server-statistics