Preconfigure the allowed upstream set
Attach multiple routing hosts to an SRT server and keep the selected active route at the front of the reviewed source order.
Primary and backup source control
Callaba Live Video Failover
Keep several SRT upstreams in one reviewed routing set. Let the relay reconnect and cycle through configured sources after a disconnect, or select another configured source manually for an SRT PULL route.
Visible reliability workflow
Primary source, backup source, controlled output
Define the upstreams before the event, keep the active route first, and use automatic relay cycling or an operator-selected switch without inventing a new destination during production.
Verified operating boundary
Failover built from configured SRT upstreams
The product keeps source choice explicit: every automatic or manual transition stays inside the upstream set reviewed by your team.
Reconnect and cycle after a disconnect
The SRT PULL relay can run in loop mode with a reconnect interval and move through the configured upstream list when the active connection is lost.
Switch a configured SRT PULL route manually
An operator or API client can select another existing upstream. The switch is rejected when the target is outside the configured routing hosts.
Use cases
Protect contribution workflows that cannot depend on one source
Use the product where teams can prepare primary and backup SRT contribution paths before going live.
Live events with a backup encoder
Keep primary and backup encoder endpoints in one reviewed source set so the operator has a prepared alternative during production.
Remote contribution over variable networks
Prepare more than one reachable upstream when a remote venue or network path may disconnect during a contribution session.
Long-running channel operations
Use configured source redundancy for continuous workflows that need an explicit recovery path and operator visibility.
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
Launch a Callaba instance near the contribution or delivery region and configure primary and backup SRT upstreams in the web interface.
Launch in the cloudSelf-hosted deployment
Run Callaba Engine on Linux when the routing hosts, network access, and operational data must remain in your infrastructure.
Install on LinuxAPI is the second layer
Read the SRT Servers API referenceAutomate an already reviewed failover plan
Use the SRT Servers API to manage the server and select an existing upstream for an SRT PULL route. Keep source approval in your product workflow.
Live video failover questions
What does Callaba Live Video Failover do?
It keeps multiple configured SRT upstreams available to one routing workflow and supports relay reconnect and cycling plus a bounded manual switch for SRT PULL routes.
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 switch sources manually?
Yes, for a reviewed SRT PULL route. The selected SRT URL must already exist in the server routing-host list.
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.
Can failover selection be automated through the API?
Yes. The SRT Servers API can select a reviewed upstream for an SRT PULL route; it cannot switch to an unconfigured URL.
Prepare before going live
Build a reviewed primary and backup path
Use the live demo to inspect the operator surface, then deploy Callaba in the cloud or on Linux for your own SRT routing plan.