Callaba routing guide
Receive SRT, hand off UDP, and verify both sides of the route
Use this workflow when a remote encoder contributes over SRT but the next system in your controlled network expects a UDP transport stream. Callaba terminates the SRT connection and creates a named route to the UDP destination. It does not make an unreachable UDP receiver reachable, so test the input and output as separate boundaries.
udp://destination:port inside the intended networkThe moving squares illustrate packets crossing each boundary; they are not live telemetry. Motion is disabled when reduced motion is requested.
Before opening the dashboard
- Reserve the SRT listener port and allow the required UDP traffic through the relevant firewall or security group.
- Confirm the final UDP host and port from the receiving system. A private address works only when Callaba can route to that private network.
- Know the source codec, audio mapping, approximate bitrate, SRT mode, passphrase and expected latency.
- Arrange a way to inspect the UDP result: the destination’s own confidence monitor, a probe, or a player appropriate for that MPEG-TS/UDP feed.
Create the SRT receiving boundary
In Streaming servers → SRT servers, add an SRT server with a clear name and an unused listener port. Size latency for the measured network, configure the required passphrase and access policy, then save and start the server.
When explicit access is enabled, create the intended publisher identity instead of opening the endpoint to every stream key. Copy the publisher address from the server information only after the role and port are correct.
Prove the SRT feed before routing it
Connect the real encoder. Confirm that Callaba shows the expected peer, live bitrate and SRT network RTT. Add the source to a private Multiview board or another decoded confidence surface and listen to the audio.
Expected publisher and stable session state
Moving bitrate, decoded video and correct audio
If the source does not pass this test, stop here. Adding a UDP output only creates a second place to debug.
Create the SRT/UDP route
Open Streaming servers → SRT routes and add a route. Select the verified SRT source or enter the SRT URL required by the current form. For the destination, choose UDP Output URL and enter the address supplied by the downstream system.
Include source and destination, for example
Venue-A-to-MCR-UDPThe verified SRT server or SRT URL
UDP Output URLFor example
udp://10.20.0.15:5000Use the address and port from the real receiver. Example values only show the shape of the field.
Start in receiver-first order
Prepare the UDP listener first, then start the Callaba route, then confirm the SRT publisher remains healthy. This order gives the output somewhere to go and makes the first failed boundary easier to identify.
If the destination expects multicast, a specific local interface, RTP encapsulation, transcoding or remapped audio, confirm that requirement separately. A simple UDP URL does not imply those additional operations.
Verify the UDP result independently
- The SRT server still reports the expected live publisher and healthy media.
- The intended UDP receiver decodes the expected program, audio and timing from the configured destination.
Run the route long enough to expose packet loss, network policy and receiver-buffer problems. Record the stop/start order and the owner of the destination before the path becomes event-critical.
Add primary and backup only after the single path works
Callaba SRT servers support ordered PULL routes and controlled preferred-route changes. Prove each source alone, observe which source is active, and rehearse a failure. Do not describe a reconnect as hitless unless the complete measured workflow demonstrates it.
Continue with the live video failover product and SRT server operator guide when the production needs a recovery path.
When to use Restreaming instead
Use an SRT route for a transport handoff. Use Restreaming when the destination also needs protocol conversion, transcoding, resizing, audio changes, overlays or a broader output choice. Keeping those jobs separate makes the runbook and capacity test more honest.
UI and API references
The SRT routes user guide explains the operator workflow. After the UI path works, the SRT Routes API reference provides create, inspect, start, stop, update and remove operations, including the UDP output preset.
