Haivision StreamHub SRT setup with Callaba Gateway
Written by Iurii Pakholkov
Founder of Callaba. Building cloud video tools for SRT, RTMP, WebRTC, NDI, live routing, monitoring, recording, and production workflows.
Release: Callaba 8.4
Haivision StreamHub is the receiver and gateway layer in many Haivision contribution workflows. It receives live feeds from field transmitters, mobile apps, rack encoders or IP sources, then can output the selected feed to another workflow over SRT.
The clean Callaba path is simple: receive the contribution feed in StreamHub, create an SRT IP Output, then send that output to a Callaba SRT listener. After Callaba receives the stream, the feed can be monitored in the browser, recorded, routed, played back, restreamed or used in a failover workflow.
This guide is written for the search intent behind Haivision StreamHub SRT, StreamHub SRT output, StreamHub Callaba Gateway, StreamHub multiview, StreamHub recorder, StreamHub playback and Callaba SRT Gateway.
Quick answer: how do I connect Haivision StreamHub to Callaba Gateway?
Create an SRT listener in Callaba Gateway, open the selected UDP port, then create an SRT IP Output in StreamHub and assign the desired input to that output. For the first cloud ingest test, use StreamHub as Caller and Callaba as Listener. Match port, latency, stream ID and passphrase if used.
What this setup does
This workflow sends an active StreamHub feed to Callaba over SRT. StreamHub receives the original contribution source. Callaba receives the SRT output and becomes the browser-based operations layer.
- StreamHub: receives, decodes, records, transcodes or distributes field and IP feeds.
- SRT IP Output: sends the selected StreamHub input to a downstream SRT receiver.
- Callaba Gateway: receives the StreamHub output and provides cloud-side monitoring, recording, playback and routing.
Where StreamHub fits
StreamHub is not just another encoder. In this article, treat it as the receiver/gateway between Haivision contribution sources and Callaba cloud workflows.
| Source side | StreamHub role | Callaba role |
|---|---|---|
| Air / Pro / MoJoPro | Receives mobile contribution and handles Haivision-side workflows. | Receives SRT output for browser monitoring, recording and routing. |
| Makito / Haivision Rack / IP feeds | Receives or transcodes feeds and prepares output profiles. | Works as a cloud ingest and operations endpoint. |
| Third-party SRT / RTMP / RTSP / HLS / NDI sources | Receives and distributes through StreamHub output profiles. | Receives StreamHub SRT output and manages downstream cloud workflow. |
Practical rule: StreamHub protects the Haivision receiver/gateway job. Callaba protects the cloud workflow job after SRT ingest.
Recommended workflow
For the first test, use a simple, debuggable path:
- Confirm the source is live and visible in StreamHub.
- Create an incoming SRT listener in Callaba.
- Create an SRT IP Output profile in StreamHub.
- Set StreamHub to call the Callaba public IP or DNS name.
- Assign the StreamHub input to the SRT output.
- Go live and check Callaba preview, bitrate, codec, audio and recording.
Recommended SRT mode: StreamHub Caller, Callaba Listener
For most public cloud workflows, set StreamHub to send the SRT output as Caller and set Callaba to receive as Listener. This keeps the public listening port on the Callaba side and makes the firewall model easier to understand.
A typical field-format example looks like this:
srt://YOUR_CALLABA_IP:11200?mode=caller&latency=300&streamid=streamhub-mainIn the StreamHub UI, these values may appear as separate fields rather than one URL: protocol, server mode, address, UDP port, latency, stream ID and encryption/passphrase.
Before you start
Prepare the StreamHub and Callaba sides before changing production profiles.
Step 1: create the Callaba SRT listener
- Open your Callaba Gateway environment.
- Go to SRT Servers and create a new incoming SRT server.
- Set the role to Listener if the UI exposes this option.
- Choose a UDP port, for example
11200. - Set latency, for example
300 msas a first internet test value. - Add stream ID and passphrase if your workflow requires them.
- Open the selected UDP port in the cloud firewall or security group.
Step 2: create StreamHub SRT IP Output
In StreamHub, create an IP Output profile that uses SRT. The exact UI labels depend on your StreamHub version, but the practical fields are consistent: protocol, server mode, UDP port, latency and optional encryption.
The StreamHub interface can vary by version. If you do not see a section named IP Output, look for Outputs, Add Output, or a similar output-profile area where the protocol can be set to SRT. The principle is the same: create an SRT output, set mode, address, port, latency, and assign the input that should go to Callaba.
- Open the IP Output or Outputs section in StreamHub.
- Create a new IP Output profile.
- Select SRT as the output protocol.
- Set server mode to Caller for the first Callaba test.
- Enter the Callaba public IP or DNS name.
- Enter the same UDP port that Callaba is listening on.
- Set latency, stream ID and passphrase to match Callaba if used.
- Save the output profile.
Testing rule: do not start with every feature enabled. First prove input → StreamHub → SRT output → Callaba. Then add encryption, additional outputs, recording, multiview and downstream routing.
Step 3: assign the input and go live
Creating an SRT output profile is not always enough. The selected input must be assigned to the output, and the source must actually be live.
- Confirm the source is visible in StreamHub.
- Assign the desired input to the SRT IP Output.
- Start the live source if it is not already live.
- Confirm the StreamHub SRT output is active.
- Open Callaba and check whether the SRT input connects.
- Confirm preview, bitrate, codec, resolution, frame rate and audio in Callaba.
Settings table
Use this table to avoid the common mismatch: the StreamHub output profile exists, but the input is not assigned, the mode is wrong, or Callaba is listening on a different port.
| Setting | StreamHub | Callaba Gateway | Why it matters |
|---|---|---|---|
| Input | Selected live source | Received SRT feed | The output must have a source assigned. |
| Mode | Caller first | Listener first | Simplest cloud ingest pattern. |
| Address | Callaba IP / DNS | Public endpoint | StreamHub must reach Callaba. |
| Port | Destination UDP | Open listener port | Wrong port means no connection. |
| Latency | SRT profile value | Same policy | Too low can break noisy paths. |
| Stream ID | streamhub-main |
Same value if expected | Helps route and identify the feed. |
| Encryption | AES / password if used | Same passphrase | Encryption fails if values do not match. |
| Codec / bitrate / audio | Source profile | Preview and monitor | Proves the stream is production-usable. |
StreamHub multiview workflow with Callaba
StreamHub can handle receiver-side monitoring and outputs. Callaba multiview is useful when the operations team wants to watch StreamHub outputs alongside other Callaba inputs in a browser, with route state, connection visibility, bitrate and audio checks in the same cloud board.
Interactive check: open the Callaba multiview demo to see how received sources can look after cloud ingest.
StreamHub recorder workflow: StreamHub recording vs Callaba recording
StreamHub recording and Callaba recording prove different parts of the chain. StreamHub recording proves the receiver/gateway side. Callaba recording proves the StreamHub SRT output reached the cloud workflow.
If you compare StreamHub recordings with Callaba recordings, make sure both systems use a consistent time source such as NTP. Time differences can make it harder to match recordings, incidents and operator notes across the two systems.
| Layer | What it proves | Use case |
|---|---|---|
| StreamHub recording | The contribution reached StreamHub. | Receiver-side proof and Haivision-side archive. |
| Callaba recording | The StreamHub SRT output reached Callaba. | Cloud-side proof, replay, downstream workflow archive. |
StreamHub playback workflow with Callaba
After Callaba receives the StreamHub SRT output, you can create browser playback or HLS/embed links for people who should not connect directly to StreamHub or to the original field workflow.
HLS playlist after Callaba ingest:
https://YOUR_CALLABA_DOMAIN/hls/streamhub-main/playlist.m3u8
Player or embed page:
https://YOUR_CALLABA_DOMAIN/embed/streamhub-mainWhere browser links come from: HLS or browser playback is not automatic for every SRT session. Callaba creates player or HLS links after you create a Web Player or HLS packaging path for that stream. See the Callaba Web Players API documentation if you need to automate player creation. Depending on your settings, links may include temporary tokens or authorization parameters.
Troubleshooting
Most StreamHub to Callaba issues are not codec problems. They are input assignment, mode, port, firewall, stream ID or passphrase problems.
1. Stream does not appear in Callaba
- Confirm the source is active inside StreamHub.
- Confirm the SRT IP Output profile exists and is enabled.
- Confirm the SRT IP Output status is Started or Enabled. A profile that is only created or displayed may not be actively sending yet.
- Confirm the StreamHub input is assigned to the SRT output.
- Confirm StreamHub is Caller and Callaba is Listener for the first test.
- Check the Callaba public IP or DNS name and UDP port.
- Open the UDP port in the cloud firewall or security group.
2. SRT connects, but picture or audio is missing
- Confirm the source in StreamHub has picture and audio before SRT output.
- Check codec and audio format in the active source profile.
- Use Callaba preview or multiview to confirm what reaches the cloud side.
- Start with the simplest profile before testing HEVC, high bitrate or advanced outputs.
3. Encryption fails
- Enable encryption on both sides or disable it on both sides.
- Use the exact same passphrase.
- Check AES strength if the interface exposes AES-128, AES-192 or AES-256.
- Test without encryption first if the production policy allows it.
4. Callaba recording is missing
- StreamHub recording proves the feed reached StreamHub, not Callaba.
- Confirm the SRT output was connected to Callaba during the same time window.
- Start Callaba recording only after the SRT input is visible and stable.
- Check time synchronization if you compare StreamHub and Callaba recordings.
Official references used for this guide
Use these if you need exact StreamHub wording, IP Output behavior, SRT profile details or Haivision contribution context.
FAQ
Can Haivision StreamHub send SRT to Callaba Gateway?
Yes. Configure an SRT IP Output in StreamHub and send it to a Callaba SRT listener.
Should StreamHub be Caller or Listener?
For most cloud ingest workflows, use StreamHub as Caller and Callaba as Listener. Use StreamHub Listener only when your network design expects the receiver to connect to StreamHub.
Can Callaba record StreamHub output?
Yes. After Callaba receives the StreamHub SRT output, it can record the received stream.
Can I monitor StreamHub output in Callaba multiview?
Yes. After the SRT output reaches Callaba, the feed can be monitored in browser preview or multiview depending on deployment and version.
Does Callaba replace StreamHub?
No. StreamHub remains the Haivision receiver/gateway layer. Callaba is the cloud workflow layer after SRT ingest for monitoring, recording, playback and routing.
Final practical rule
Do not debug StreamHub to Callaba as one black box. First prove the source is active in StreamHub. Then prove the SRT IP Output profile. Then prove input assignment. Only after that should you debug Callaba preview, recording, playback or routing.
Last updated: May 20, 2026
Try Callaba Gateway with StreamHub SRT output
Create an SRT listener in Callaba, send a StreamHub SRT IP Output to the gateway, and monitor the feed before routing it to recording, restreaming, multiview, playback or player delivery.
See SRT server setup Open multiview demo Web Player docs StreamHub SRT output docs