media server logo
PricingSign inLaunch recordings
Operator documentation

Recording and retention

Use this runbook to record a live source to tested storage and assign an explicit retention responsibility. It keeps the UI task, verification and automation path together.

UIQuick start → Recording

What this solves

This procedure gives an operator one controlled path to record a live source to tested storage and assign an explicit retention responsibility.

When to use it

Use it during initial setup, a planned change or incident recovery when you need to record a live source to tested storage and assign an explicit retention responsibility.

Dashboard path

Quick start → RecordingRoute/srt-stream-recordings/list
Quick start → File managerRoute/files/list?type=recording

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 Quick start → Recording. Open the source-backed route /srt-stream-recordings/list. In the dashboard sidebar, follow Quick start → File manager. Open the source-backed route /files/list?type=recording.

  2. 02

    Before changing Recording and retention, record these current values: recording_name, stream_id, output_format, recording_mode, delete_after.

  3. 03

    In Recording and retention, set recording_name, stream_id, output_format, recording_mode, delete_after so you can record a live source to tested storage and assign an explicit retention responsibility. Keep unrelated values unchanged.

  4. 04

    Run Save [creating-form-save]. 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: active, file_id, file_name, storage_type, size.

Controls to review
  • recording_name
  • stream_id
  • output_format
  • recording_mode
  • delete_after
Actions to run
  • Savecreating-form-save
Signals to verify
  • active
  • file_id
  • file_name
  • storage_type
  • size

Expected result

The runbook is complete when Save [creating-form-save] succeeds and a real workflow reports active, file_id, file_name, storage_type, size.

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 pageLive video recording that stays connected to the workflowExact API referenceExact API reference 1 · create-recordingExact API referenceExact API reference 2 · get-all-recordings