What this solves
This procedure gives an operator one controlled path to turn one verified input into stable outputs with the required codec, resolution and bitrate.
When to use it
Use it during initial setup, a planned change or incident recovery when you need to turn one verified input into stable outputs with the required codec, resolution and bitrate.
Dashboard path
/srt-to-socials/list/streams/listPrerequisites
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
- 01
In the dashboard sidebar, follow Quick start → Re-streaming. Open the source-backed route /srt-to-socials/list. In the dashboard sidebar, follow Quick start → Streams. Open the source-backed route /streams/list.
- 02
Before changing Restreaming and transcoding, record these current values: input_stream_url, output_stream_url, output_stream_key, output_video_bitrate, output_audio_bitrate, encoding_profile.
- 03
In Restreaming and transcoding, set input_stream_url, output_stream_url, output_stream_key, output_video_bitrate, output_audio_bitrate, encoding_profile so you can turn one verified input into stable outputs with the required codec, resolution and bitrate. Keep unrelated values unchanged.
- 04
Run Save [creating-form-save]. Wait for the form or listing to settle before testing another variable.
- 05
Use a real source, destination or browser client and confirm these live signals: active, bitrate, fps, input_bitrate_kbps, output_bitrate_kbps.
input_stream_urloutput_stream_urloutput_stream_keyoutput_video_bitrateoutput_audio_bitrateencoding_profile
- Save
creating-form-save
activebitratefpsinput_bitrate_kbpsoutput_bitrate_kbps
Expected result
The runbook is complete when Save [creating-form-save] succeeds and a real workflow reports active, bitrate, fps, input_bitrate_kbps, output_bitrate_kbps.
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.