Haivision SRT Gateway Workflows with Callaba
More live video workflow notes and product updates.
Haivision system map
Choose the Haivision role first—and name where the SRT handoff actually begins
Haivision’s portfolio includes fixed encoders and decoders, mobile transmitters, receiver platforms and phone applications. Makito X4, Air, Pro, StreamHub, MoJoPro and Play Pro cannot share one truthful setup. They can share a system map that tells an operator who originates media, who receives it and what Callaba is expected to do next.
Callaba does not impersonate a Haivision appliance or take credit for upstream mobile bonding. It receives an agreed SRT output, makes that boundary visible and uses the accepted program for Multiview, recording, routing, playback or a separately designed backup path.
See the system boundary before choosing a model
direct device output or StreamHub IP output
A mobile workflow may reach StreamHub through a Haivision contribution service before StreamHub creates a separate SRT IP output. In that design, the phone or transmitter is not the Callaba peer. A fixed Makito encoder may instead create the SRT session directly. Write this distinction into the runbook.
Select the detailed guide by role
Receive and mobile apps
StreamHub selects upstream inputs and can expose an SRT output. Play Pro is a viewing app; MoJoPro is a mobile capture path that normally reaches Callaba through StreamHub.
Air and Pro mobile systems
These field systems need their exact model, modem plan, service path and StreamHub handoff verified. Do not describe vendor bonding as Callaba failover.
Makito fixed hardware
The model name is not enough: distinguish encoder, decoder and rugged variants. The sender and return decoder own opposite directions.
Assign evidence to the platform that can prove it
| Did the field source reach the receiver? | Use the transmitter or StreamHub state. Callaba is not authoritative before the SRT handoff exists. |
|---|---|
| Did the intended SRT output start? | Use the Haivision output state and matching Callaba publisher/session evidence. |
| Is the right media present? | Identify the source inside Haivision, then prove the same visual cue and audio in Callaba. |
| Can downstream operators use it? | Use a configured Callaba Multiview tile, sample recording and final route—not a transport badge alone. |
| Which platform recovers a failure? | Interrupt each layer independently and document its actual behavior and operator authority. |
Build one direct or StreamHub handoff
For a direct fixed-encoder workflow, create the Callaba Listener or Caller that matches reachability, then configure the exact Makito output with the corresponding address, UDP port, mode, Stream ID, latency and encryption values. For a mobile or StreamHub workflow, first prove the upstream source inside StreamHub. Create the SRT IP output separately and assign that exact source to it.
Start with one output and one Callaba receiver. A successful output to a different partner does not prove the Callaba branch. Compare both systems over the same time interval when a session reconnects, and use a unique visual or spoken cue to prevent a stale or wrong source from passing acceptance.
Keep four operational rules visible
Record product, encoder/decoder direction, firmware, enabled service and the peer that originates the session.
Confirm sustained bitrate, representative motion, complete audio and any required ancillary behavior.
If StreamHub and Callaba both record, define start conditions, retention, failure domain and which file is the deliverable.
A StreamHub source switch, a restarted SRT output and a Callaba route change are different events.
Diagnose the failing boundary only
If a mobile source never appears in StreamHub, keep the Callaba port out of the diagnosis. If StreamHub sees the source but Callaba is idle, inspect output assignment, SRT mode, destination, firewall, Stream ID and encryption. If Callaba shows transport but no useful program, compare codec, source selection and audio through the decode. If Multiview works but recording fails, preserve the accepted handoff and investigate only recording and storage.
Match official documentation to the installed release
Use Haivision’s versioned Makito X4 SRT configuration and StreamHub IP output profile documentation for those branches. For mobile roles, consult the current Air transmitter, Pro460, MoJoPro and Play Pro product sources. Confirm the current manual, software, license and service for the exact product before production.
