Skip to content
Callaba
PricingSign inDeploy failover streaming
Primary and backup source control

Callaba Live Video Failover

Keep an alternate SRT feed ready for a dropped connection. The SRT PULL relay reconnects and cycles through its configured main and backup source set after a disconnect.

Configured recovery path

Keep two prepared SRT sources behind one relay

This is a source-recovery path for a configured SRT PULL relay. It reconnects and cycles through the sources you have prepared after a disconnect.

Keep two prepared SRT sources behind one relay
Main sourceConfigured SRT PULL routing host
Backup sourceConfigured SRT PULL routing host
SRT PULL relayLoop and reconnect across the configured source set
DestinationReceiver or platform checked separately
Set up before the event

Prepare the SRT PULL recovery path

Open Routing settings
Choose SRT Routing, select SRT main/backup failover, set Routing mode to Pull, then add each Routing Host and Routing SRT Port with Add SRT Host.
Match the connection details
Check the SRT mode, port, latency, stream identity, and passphrase where the chosen sources use them.
Plan a preferred-route change
Stop the relay, save a configured Pull route as preferred, then start it again.
Run one controlled test

Check the path your event will actually use

Test with the event encoder, network, relay, and destination. Record what happened on this path instead of assuming another source pair will behave the same way.

  • Interrupt the main sourceDuring a planned window, remove the active source and observe reconnect and cycling only across the configured hosts.
  • Check the destinationConfirm the receiving platform or receiver accepts the recovered feed; a running relay alone does not prove delivery.
  • Keep an operator action availableStop the relay, save a configured Pull route as preferred, then start it again.
Deployment

Use the same failover model in cloud or self-hosted Callaba

Choose where the SRT routing layer runs, then configure the upstream set around your network and production boundary.

Cloud deployment

Deploy a Callaba instance near the contribution or delivery region and configure primary and backup SRT upstreams in the web interface.

Deploy Callaba on AWS

Self-hosted deployment

Run Callaba Engine on Linux when the routing hosts, network access, and operational data must remain in your infrastructure.

Install on Linux

Live video failover questions

What does Callaba Live Video Failover do?

It keeps main and backup SRT Pull routing hosts in one configured workflow and lets the relay reconnect and cycle through that source set after a disconnect.

What happens when the active upstream disconnects?

A relay configured in loop mode can reconnect and move through its existing upstream list. Actual recovery time depends on the connection and the prepared sources.

Can an operator prepare a different preferred source?

For an SRT Pull server with two or more routing hosts, the dashboard's Switch to action saves another configured route as preferred. Stop the relay, save a configured Pull route as preferred, then start it again; the saved preference does not reload a running relay.

Does this promise hitless or zero-downtime switching?

No. The product provides a controlled recovery path, but it does not claim a hitless transition or guaranteed zero downtime. Source readiness and network conditions still matter.

What can the API automate in this workflow?

The SRT Servers API can manage configured routing hosts and persist the preferred active route. It does not turn that configuration update into an immediate live switch of the running relay.

Prepare before going live

Build a primary and backup path you can test

Use the live demo to inspect the operator surface, then deploy Callaba in the cloud or on Linux to test your own primary, alternate, and destination-acceptance plan.