media server logo
PricingSign inLaunch SRT server
Operator documentation

SRT server operations

Use this runbook to bring an SRT listener, controlled access, live telemetry and primary/backup routing into a known working state. It keeps the UI task, verification and automation path together.

UIStreaming servers → SRT servers

What this solves

This procedure gives an operator one controlled path to bring an SRT listener, controlled access, live telemetry and primary/backup routing into a known working state.

When to use it

Use it during initial setup, a planned change or incident recovery when you need to bring an SRT listener, controlled access, live telemetry and primary/backup routing into a known working state.

Dashboard path

Streaming servers → SRT serversRoute/srt-servers/list
Streaming servers → SRT routesRoute/srt-routes/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 → SRT servers. Open the source-backed route /srt-servers/list. In the dashboard sidebar, follow Streaming servers → SRT routes. Open the source-backed route /srt-routes/list.

  2. 02

    Before changing SRT server operations, record these current values: server_port, server_receiver_port, server_latency, passphrase, access_settings, routing_hosts.

  3. 03

    In SRT server operations, set server_port, server_receiver_port, server_latency, passphrase, access_settings, routing_hosts so you can bring an SRT listener, controlled access, live telemetry and primary/backup routing into a known working state. 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: BITRATE, msRTT, PUSHER, PULLER.

Controls to review
  • server_port
  • server_receiver_port
  • server_latency
  • passphrase
  • access_settings
  • routing_hosts
Actions to run
  • Savecreating-form-save
  • StartSTART
Signals to verify
  • BITRATE
  • msRTT
  • PUSHER
  • PULLER

Expected result

The runbook is complete when Save [creating-form-save] → Start [START] succeeds and a real workflow reports BITRATE, msRTT, PUSHER, PULLER.

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 SRT ServerExact API referenceExact API reference 1 · create-srt-serverExact API referenceExact API reference 2 · switch-srt-pull-route