Four ways to configure an SRT gateway in Callaba
Choose the path by what the signal must do. Each path is configured in the Callaba UI and has a direct operator guide and API reference.
SRT Server with explicit access
Choose whenChoose this for a managed SRT entry point with explicit publisher and receiver permissions.
- Create an SRT Server and set its port, mode, latency, and optional passphrase.
- Add only the publisher and receiver connections that should be allowed.
- Start the server, connect both sides, and verify transport health.
SRT Route
Choose whenChoose this to forward an SRT or UDP input to an SRT destination without transcoding.
- Select a local SRT listener, SRT URL, or supported UDP source.
- Set the SRT destination and matching transport parameters.
- Start the route and verify the source and destination independently.
Restreaming
Choose whenChoose this when the gateway also needs protocol conversion, transcoding, resizing, audio changes, or overlays.
- Select and verify the incoming live source.
- Add an SRT output and configure its destination and transport settings.
- Start Restreaming and verify the produced output at the receiver.
Stream using the SRT protocol
Choose whenChoose this to issue named publisher or receiver connections for an existing SRT Server.
- Create or select the parent SRT Server.
- Create a Stream, choose SRT, and assign its publisher or receiver role and identity.
- Share the correct connection details and verify it in the parent server statistics.
Live contribution gateway
Bring an SRT feed in once. Decide where it goes next.
An SRT gateway is the controlled handoff between a contribution source and the systems that need the feed. Callaba can accept the connection, show the operator whether media is healthy, route it to another protocol or destination, record it, and keep a recovery path ready.
This is product software, not only an API layer. Build and inspect the path in the Callaba interface; use the API later when the same operation needs automation.
Four ways to build the gateway in Callaba
Choose the module from the job, not from a generic architecture diagram. Each option is useful, but they do not describe the same operation.
SRT Server
Create an SRT server when you need explicit publishers and receivers, connection roles, Stream ID controls, live transport statistics, routing and primary or alternate paths. This is the usual starting point for managed contribution.
SRT Router
Use an SRT route when the task is a deliberate SRT-to-SRT relay. Keep the source and destination roles visible, then confirm the receiving endpoint gets decoded video and audio.
Restreaming
Choose Restreaming when the incoming feed must move to another destination or protocol, such as RTMP distribution, an additional SRT endpoint or a production output.
Stream
Create a Stream when the contribution feed belongs in a playback, packaging or broader media workflow. The transport remains important, but the result is now the audience or production surface.
What an operator should see before routing the feed
Connection
A session is present and the expected publisher or receiver has connected. A saved configuration alone is not proof.
Transport health
Bitrate is arriving; RTT and loss are read over time; recovery is not silently exhausting the latency window.
Decoded output
Picture and audio are checked in Multiview or at the destination. A green socket cannot prove usable media.
Failover belongs beside the live feed
For a recoverable contribution path, prepare the primary and alternate SRT routes before the event. Callaba can cycle through configured PULL routes after a disconnect. A planned manual change uses the same route state but should be rehearsed as a controlled stop, selection and restart—not described as packet-level hitless protection.
The live Multiview demo is the fastest way to see the operator surface used to observe feeds and make a manual decision.
From first test to a maintained gateway
- Create one input and verify it with a real encoder.
- Read connection state and transport statistics while changing the network.
- Add one output, then verify that output independently.
- Add recording, Multiview or recovery only after the primary path is observable.
- Document ports, roles, Stream IDs, ownership and the event-day fallback.
Follow the current SRT server user guide for interface operations. Developers can continue with the SRT contribution gateway API recipe.
Contribution ends where production begins
An SRT contribution path carries the camera, encoder or remote program into the system that will monitor, switch, record, route or package it. That upstream result must be accepted separately from audience delivery: a healthy contribution feed does not prove a player, CDN or participant room.
In Callaba, keep transport state and decoded preview visible before adding outputs. Then verify each route independently so a downstream failure is not misdiagnosed as an SRT ingest problem.