Skip to content
Callaba
SRT contribution gateway

Callaba SRT Gateway

Bring an SRT contribution into Callaba, check it, then choose the next receiver. Relay only when the SRT receiver already accepts the source media; use Restreaming for an RTMP publishing output that needs processing, or the NDI workflow for a production-network handoff.

One controlled SRT path from contribution to delivery
Receive
Authorize
Route
Deliver
Monitor bitrate, RTT, loss, buffers, and connection originProve the feed at the intended destination
SRT contribution gateway

Choose the receiver handoff before you build the route

Start with one source and its next receiver. The paths below keep controlled ingress, transparent relay, RTMP processing and named connections separate; verify the selected destination after the route is live.

Live SRT gateway demo

Test a temporary SRT connection

Create a temporary SRT connection for one hour. Send a source to the publisher address in Caller mode, leaving Stream ID empty. Connect a receiver to the receiver address in Caller mode. After the publisher connects, use the Multiview preview to check picture and audio. This test does not convert the stream or demonstrate failover.

Ready to create

Control who can connect

Choose whenUse an SRT Server when Callaba must admit specific publishers or receivers.

SRT publisher
Access policy
SRT receiver
Set it up
  • Create an SRT Server with its port, latency and optional passphrase.
  • Add the publisher and receiver connections that should be allowed.
  • Connect both sides and check the active stream.

Relay without changing the media

Choose whenUse an SRT Route when the source and SRT receiver already agree on the container, codecs and tracks. It relays transport without changing the media.

SRT or UDP input
Transport route
SRT destination
Set it up
  • Select an SRT listener, SRT URL or supported UDP source.
  • Set the SRT destination and matching transport details.
  • Check decoded picture and programme audio at the destination.

Publish to RTMP when the output needs processing

Choose whenUse Restreaming for an RTMP publishing output that needs conversion, transcoding, resizing, audio changes or overlays. Use the NDI workflow for a production-network handoff.

SRT input
Media processing
RTMP publishing output
Set it up
  • Select the live source and required processing.
  • Add the RTMP destination and its publishing details.
  • Check the produced output at the intended receiver or platform.

Issue a named connection

Choose whenUse an SRT Stream when an existing SRT Server needs a named publisher or receiver connection.

SRT Server
Named SRT Stream
Publisher or receiver
Set it up
  • Select the parent SRT Server.
  • Create the SRT Stream and assign its publisher or receiver identity.
  • Share the right connection details and check the parent server statistics.
SRT contribution gateway

Find the documented handoff for your encoder or camera

After choosing the route, use these compact links to find the documented manufacturer handoff. They are setup starting points, not device certification or a promise of identical firmware behaviour.

SRT gateway setup and technical reference

Choose the next receiver before you build the route

Start with the source, the receiver and the media change the receiver actually needs. An SRT Route is for a transparent SRT-to-SRT relay: it forwards the contribution, so the receiver must already accept its container, codecs, tracks and timestamps. It relays the source media; it does not create a browser output.

If the next job is RTMP publishing, configure a Restream output and enable processing only when that destination needs it. If the next job is an NDI production handoff, configure the NDI output path and validate it on the designed production network. Use an SRT Server for controlled ingress and an SRT Stream for a named connection on an existing server. A connected source is not proof that any downstream receiver accepted the feed.

Use relay when the media already fits; process only when it must change

Incoming SRT jobChooseVerify at the far end
SRT → SRT receiverSRT Route, when both endpoints already accept the source media.Receiver connection, decoded picture and programme audio.
SRT → RTMP publisherRestreaming with the required RTMP destination and only the media processing that output needs.The RTMP receiver or publishing platform accepts the intended programme.
SRT → NDI production handoffThe NDI output workflow for the selected deployment and production network.The intended NDI receiver sees picture and programme audio.

Transcoding, resizing, audio changes and overlays add processing work beyond a relay. Test the planned source, output profile, host capacity and destination together; do not infer the final output from a green ingress connection.

When the publisher connects but the receiver is empty

What you seeCheck next
Publisher is connected; receiver has no bitrateConfirm the route selects the intended input and output, then compare receiver host, port, Caller/Listener role, Stream ID and passphrase.
Receiver has bitrate; no picture or programme audioCheck the container, codecs, tracks and timestamps at the receiver. SRT transport does not make an unsupported payload decodable.
Picture breaks on the event networkCompare RTT, loss, retransmissions and effective latency on the actual path. Test the source, route and receiver together.

Connection

Record the source and destination host, port, roles and access state. Use endpoint logs when the session is denied or reaches the wrong stream.

Transport health

Watch bitrate, RTT, packet loss, connection events and peer details while the source is running. A saved route or running process does not show whether a destination accepted it.

Decoded output

Verify picture and programme audio at the selected receiver, player or Multiview tile. Multiview is the observation handoff; it does not turn a relay into a production switcher.

Keep the route demo separate from a failover test

The temporary gateway demo tests one publisher and one receiver connection, then a Multiview preview after the publisher connects. It does not convert a stream and does not demonstrate protocol conversion or failover.

For a main/backup contribution, select SRT main/backup failover under SRT Routing, choose Pull, and enter the source hosts and routing ports for both contributions. Write the trigger and expected destination behavior into the event plan, then test actual feeds, buffers and destination behaviour before the event. A transport switch can preserve connected receiver and puller sessions, but the picture transition depends on the prepared feeds, buffers, network conditions and destination.

Connect contribution to the broader production path

Run the gateway in AWS or on Linux infrastructure your team controls, choosing the location that fits the media path, firewall policy and operating team. After the SRT path is accepted, use Multiview to observe the selected feed, or evaluate the AV Mixer workflow when the job is to create and take a programme rather than relay a finished feed.

For ports and access settings, use the SRT Server guide. For decoder setup or a black picture, use the SRT Player guide. Automate only the route that has been tested end to end.

Use a route choice before browsing device guides

Choose ingress, transparent relay, RTMP publishing or NDI production handoff first. Then use the device directory as a configuration starting point for the selected encoder or camera. Confirm the installed firmware, SRT mode, port, Stream ID, encryption and payload settings against manufacturer documentation before using a device on an event route.

For a small starting configuration, review the SRT relay preset. It starts with one stream and one Restream job; the actual source, destination and receiver test remain yours to configure.

Next steps

Ask AI