Haivision SRT Gateway to Callaba: pull, record, and route SRT streams
This tutorial shows how to get an SRT stream from Haivision Gateway into Callaba and record it. The same workflow can also be used when you need to pull an SRT feed from another SRT gateway, relay, or media transport system.
The practical workflow is:
Haivision Gateway → SRT destination/listener → Callaba SRT server in Pull mode → recording
Use this setup when Haivision Gateway is already receiving or routing a live feed, and you want Callaba to take that feed into a cloud workflow for recording, restreaming, transcoding, preview, or further routing.
Haivision SRT Gateway and Callaba: what this workflow does
Haivision Gateway works with routes. A route connects a source to one or more destinations. In this guide, Haivision Gateway exposes an SRT destination, and Callaba connects to that destination to pull the stream.
Callaba then treats the pulled SRT stream as an input. After the stream arrives in Callaba, you can use it like any other live input:
- record the stream
- restream it to another destination
- transcode it
- preview it in the browser
- route it to another SRT, RTMP, HLS, WebRTC, or production workflow
This tutorial focuses on recording the stream after Callaba receives it.
SRT gateway vs SRT server
An SRT gateway usually connects streams between systems, networks, or locations. It can receive a stream from one side and send or expose it to another side.
An SRT server is usually the endpoint that receives, sends, or relays an SRT stream inside a specific workflow.
In this tutorial:
- Haivision Gateway prepares and exposes the SRT feed.
- Callaba SRT server pulls that SRT feed from Haivision Gateway.
- Callaba Recording records the received stream.
Push vs pull in this SRT Gateway workflow
There are two common ways to connect SRT systems:
- Push: the sender starts the connection and sends the stream to a listener.
- Pull: the receiver connects to another endpoint and pulls the stream from it.
In this guide, Callaba uses Pull mode. That means Callaba connects to the SRT destination exposed by Haivision Gateway and receives the stream from there.
This is useful when Haivision Gateway already owns the route and Callaba only needs to consume the output from that route.
What you need before you start
- Access to Haivision Gateway or Haivision SRT Gateway.
- An active route or source stream in Haivision Gateway.
- A Callaba instance with access to SRT Servers and Stream Recordings.
- The IP address or hostname of the Haivision Gateway instance.
- The SRT destination port that Callaba will pull from.
- Network access between Callaba and Haivision Gateway over the required UDP port.
If this is your first time using Callaba, start with How to launch Callaba Cloud Live Streaming.
Step 1. Create or open a route in Haivision Gateway
In the Haivision Gateway dashboard, create a new Route or open an existing route that already receives your live stream.
Set the source side of the route.
- Source name: use a clear name for the incoming stream.
- Route name: use a clear name for the full route.
- Protocol: TS over SRT.
- Type: Listener.
- Port: specify the port where Haivision Gateway receives the source stream. In this example, the source port is
1935.
At this point, Haivision Gateway is prepared to receive the original SRT contribution feed.
Step 2. Add an SRT destination in Haivision Gateway
In the same route, click Add Destination.
For this workflow, the destination is the SRT endpoint that Callaba will pull from.
- Protocol: TS over SRT.
- Type: Listener.
- Port: specify the port that Callaba will connect to. In this example, the destination port is
9001.
Click Save.
The Haivision side is now ready. The important value for the next step is the destination port. In this example, Callaba will pull from:
srt://HAIVISION_GATEWAY_IP:9001Step 3. Log in to Callaba
Open your Callaba dashboard.
If you run Callaba on a cloud instance, open it using the public IPv4 address or the domain name attached to your instance.
If you have trouble logging in or launching the instance, use this guide: How to launch Callaba Cloud Live Streaming.
When you are finished testing, stop your cloud instance if you no longer need it. This helps avoid unnecessary cloud charges.
Step 4. Create an SRT server in Callaba
In Callaba, open the SRT Servers section and click Add New.
Create a new SRT server for the stream that will be pulled from Haivision Gateway.
- Name: use a clear name, for example
haivision-pull-recording. - Port: specify the Callaba SRT server port according to your workflow.
Step 5. Set Callaba SRT routing to Pull mode
Scroll down to the Routing Setting section.
Configure Callaba to pull the stream from Haivision Gateway.
- SRT Routing: select Callaba Cloud Live Streaming.
- Routing mode: select Pull.
- Routing Host IP: enter the IP address or hostname of the Haivision Gateway instance.
- Routing SRT Port: enter the Haivision Gateway destination port. In this example, it is
9001. - Source SRT Server name: create a clear name for this pulled source.
Click Save.
Callaba is now configured to pull the SRT stream from Haivision Gateway.
Step 6. Create a recording for the pulled SRT stream
Now that Callaba can receive the stream, you can record it.
Open the Stream Recordings section and click Add New.
- Name: create a clear name for the recording.
- Input type: select SRT Server.
- SRT Server: select the SRT server you created for the Haivision Gateway pull workflow.
- Output format: select the required recording format.
Click Save.
Step 7. Check that the SRT stream is arriving
Go back to the SRT Servers section in Callaba.
Check the stream status and bitrate. If the pull is working, you should see the incoming stream activity.
If you do not see bitrate, check whether a final receiver or workflow is attached to the stream. In this tutorial, the recording task is the receiver.
Step 8. Check the active recording
Open the Stream Recordings section.
You should see that the pulled SRT stream is being recorded.
You can stop the recording at any time by clicking the status icon.
To open the folder with the recorded files, click Files.
In the folder, you can watch, download, or delete your recordings.
What to check if Callaba cannot pull from Haivision Gateway
- Wrong host: make sure the Routing Host IP points to the Haivision Gateway instance.
- Wrong port: use the Haivision destination port, not the original source ingest port.
- Blocked UDP traffic: SRT uses UDP, so the required port must be open between Callaba and Haivision Gateway.
- Wrong SRT mode: in this workflow, Haivision exposes the destination as listener, and Callaba pulls from it.
- No active source: Haivision Gateway must already have a live source feeding the route.
- No receiver in Callaba: attach a recording, restream, or another downstream workflow so the pulled stream is actually consumed.
- Passphrase mismatch: if SRT encryption is enabled, both sides must use matching security settings.
Common Haivision SRT Gateway to Callaba problems
Callaba connects but no bitrate appears
Check that the Haivision route has an active source and that the SRT destination is running. Then confirm that Callaba is pulling from the destination port, not from the source ingest port.
The stream appears in Callaba but recording does not start
Check the recording input type and make sure it is attached to the correct SRT server. Also check the selected output format and storage path.
The stream is unstable or breaks up
Check packet loss, RTT, jitter, and latency on the SRT path. If the path is unstable, increase the SRT latency buffer and make sure both systems have enough bandwidth headroom.
The wrong stream is being recorded
Check the Haivision route, destination port, Callaba routing host, and Callaba SRT server name. Clear naming is important when several SRT routes are active at the same time.
When this workflow is useful
This Haivision Gateway to Callaba workflow is useful when you already use Haivision for live transport but want Callaba to handle the next stage of the workflow.
Use it when you need to:
- record an SRT feed coming from Haivision Gateway
- pull a routed SRT stream into Callaba
- restream a Haivision SRT feed to another platform
- preview or monitor the stream in Callaba
- bridge a Haivision route into cloud workflows
- use Callaba as an additional processing or recording layer
FAQ
What is Haivision SRT Gateway?
Haivision SRT Gateway is used to route live video streams across IP networks. In practical workflows, it can receive a stream from one side and send or expose it to another destination.
What is an SRT gateway?
An SRT gateway is a system that helps move SRT streams between sources, destinations, networks, or production systems. It is often used for contribution, routing, relay, and handoff workflows.
Can Callaba pull an SRT stream from Haivision Gateway?
Yes. Callaba can be configured in Pull mode to connect to an SRT destination exposed by Haivision Gateway. You need the Haivision Gateway IP address or hostname and the SRT destination port.
Which Haivision port should I use in Callaba?
Use the Haivision destination port that exposes the stream for Callaba to pull. Do not confuse it with the source ingest port that Haivision uses to receive the original stream.
Does this workflow use SRT caller or listener mode?
In this workflow, Haivision Gateway exposes the SRT destination as a listener, and Callaba connects to it in Pull mode. The exact mode names can vary by interface, but the practical idea is that Callaba connects to the Haivision destination endpoint.
Can I record Haivision Gateway streams in Callaba?
Yes. After Callaba pulls the SRT stream from Haivision Gateway, create a Stream Recording task and select the Callaba SRT server as the input.
Can I restream a Haivision SRT feed with Callaba?
Yes. Once Callaba receives the pulled SRT stream, you can use it as an input for restreaming to other destinations, including RTMP or RTMPS services.
Why does Callaba show no bitrate from Haivision Gateway?
The most common causes are wrong host, wrong destination port, blocked UDP traffic, inactive Haivision source, wrong SRT mode, passphrase mismatch, or no downstream receiver attached in Callaba.
Can I use the same setup with another SRT gateway?
Yes. The same principle works with other SRT gateways or media transport systems if they expose an SRT endpoint that Callaba can pull from.
What can I do with the stream after Callaba receives it?
You can record it, restream it, transcode it, preview it, route it to another destination, or use it as part of a larger live production workflow.