Haivision Air320e-5G SRT setup: compact mobile contribution with Callaba Gateway

May 19, 2026

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 Air320e-5G is a compact mobile transmitter for live contribution over bonded cellular and IP networks. Its main role is portable field contribution: a reporter, camera operator, producer or small team sends a live SDI or HDMI source from the field to a production workflow.

The important Callaba nuance is this: do not treat Air320e-5G as a normal direct SRT encoder in every setup. The safer production workflow is Air320e-5G → StreamHub receiver/gateway → SRT output → Callaba Gateway. Use direct Air to Callaba SRT only if your firmware and output profile explicitly expose direct SRT output fields.

This guide is written for the search intent behind Haivision Air320e-5G SRT, Haivision Air multiview, Haivision Air recorder, Haivision Air playback, Haivision mobile transmitter SRT Gateway, StreamHub SRT output and Callaba SRT Gateway.

Quick answer: how do I connect Haivision Air320e-5G to Callaba Gateway?

Use Haivision StreamHub as the receiver for the Air320e-5G mobile transmitter, then create an SRT output from StreamHub to a Callaba SRT listener. In Callaba, create an SRT server/listener, open the selected UDP port, then configure StreamHub to send SRT to the Callaba public IP or DNS name, port, latency, stream ID if used and passphrase if encryption is enabled.

The clean workflow is Air320e-5G to StreamHub first, then StreamHub sends SRT to Callaba Gateway for browser monitoring, recording, playback and routing.

What this setup does

This workflow gets an Air320e-5G contribution feed into Callaba Gateway. The Air unit handles portable mobile contribution. StreamHub receives that contribution and provides an SRT output. Callaba receives that SRT output and becomes the cloud-side control point for monitoring, recording, playback and routing.

Air320e-5G: captures an SDI or HDMI source and transmits over bonded cellular/IP networks.
StreamHub: receives the Haivision mobile contribution stream and can provide an SRT output to Callaba.
Callaba Gateway: receives the SRT output and provides browser preview, multiview, recording, playback and routing tools.

Important SRT nuance: Air320e-5G is usually part of a StreamHub workflow

A user searching for Air320e-5G SRT may expect the same setup as a normal hardware encoder: enter srt://CALLABA_IP:PORT directly on the device and go live. That may not be the right default assumption for a bonded mobile transmitter workflow.

Haivision positions Air as part of a mobile contribution ecosystem where the field unit works with StreamHub. StreamHub is the receiver/gateway layer that can integrate the live feed with SDI, IP, cloud and SRT workflows.

How to check direct SRT: in the Air320e-5G web interface, look for an Output or Streaming section with fields such as SRT URL, Destination Address, Destination Port, or Streaming Protocol: SRT. If those fields are not present in your firmware/profile, use the StreamHub path instead.

Use StreamHub as the reliable default path. Only describe direct SRT if the exact firmware/profile exposes direct SRT output settings.

Recommended workflow: Air320e-5G to StreamHub, then SRT to Callaba

For most portable field production setups, the clean path is:

Camera to Air320e-5G: the mobile transmitter handles SDI or HDMI contribution.
Air320e-5G to StreamHub: Haivision’s mobile contribution layer handles bonded cellular/IP transmission.
Optional local recording: if the production needs a field-side copy, test SD card recording or file forwarding before the live window.
StreamHub to Callaba: StreamHub creates or routes an SRT output to Callaba Gateway.
Callaba operations: operators monitor, record, play back and route the received stream.

The SRT boundary is usually StreamHub to Callaba, not necessarily Air320e-5G directly to Callaba.

Before you start

Prepare both parts of the workflow: the Haivision mobile contribution side and the Callaba ingest side. Do not debug this as a single SRT cable until you know where the SRT output actually starts.

Source input Confirm the SDI or HDMI signal, audio source and expected resolution before debugging cloud ingest.

Local recording If the workflow depends on Air's SD card or file-forwarding recording, test it separately before relying on Callaba cloud recording.

Air unit state Check battery, SIMs, network links, selected encoder profile and whether the transmitter is actually live.

StreamHub receiver Confirm StreamHub receives the Air feed before sending anything to Callaba.

Callaba address Use the public IP address or DNS name of the Callaba instance that will receive the SRT output.

UDP port Choose one UDP port for this input and open it in the cloud firewall or security group.

Actual bitrate Watch the real received bitrate in Callaba. Bonded mobile workflows can adapt based on available network conditions.

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 10900.
Set latency for the StreamHub-to-Callaba SRT path, for example 200–500 ms as a starting point.
Add stream ID and passphrase if your workflow requires them.
Open the selected UDP port in the cloud firewall or security group.
Copy the Callaba SRT publisher URL or copy the host, port and SRT settings for StreamHub.

Testing rule: prove Air320e-5G to StreamHub first. Then prove StreamHub to Callaba over SRT. Do not mix both troubleshooting layers in the first test.

Step 2: configure StreamHub SRT output to Callaba

After StreamHub receives the Air320e-5G feed, configure an SRT output or route from StreamHub to the Callaba SRT listener.

Confirm the Air feed is live inside StreamHub.
Create an output route for that feed.
Choose SRT as the output protocol if your StreamHub version exposes this output type.
Set StreamHub as Caller and Callaba as Listener for the simplest cloud ingest model.
Enter the Callaba public IP address or DNS name.
Enter the UDP port that Callaba is listening on.
Match stream ID, latency and passphrase if used.
Start the StreamHub output and check connection state, bitrate, codec, audio and preview in Callaba.

srt://YOUR_CALLABA_IP:10900?mode=caller&latency=300&streamid=air320e-5g-main

Use this as a field-format example. In StreamHub, these values may be entered as separate fields instead of a single URL.

Settings table

This table keeps the mobile contribution layer and the SRT ingest layer separate. The SRT values that must match are usually on the StreamHub-to-Callaba leg. For the first ingest test, H.264 is usually the safest codec choice before moving to HEVC profiles.

The SRT settings that must match are usually on the StreamHub-to-Callaba leg.

Setting	StreamHub / Air side	Callaba Gateway	Why it matters
Receiver path	Air320e-5G to StreamHub	SRT from StreamHub	Separates mobile contribution from Callaba ingest.
SRT mode	Caller output	Listener input	One side waits, the other connects.
Address	Callaba IP / DNS	Public endpoint	StreamHub must call the reachable Callaba address.
Port	Destination UDP port	Open listener UDP port	Wrong port means no connection.
Latency	SRT output buffer	Same policy	Helps absorb jitter on the StreamHub-to-Callaba path.
Stream ID	`air320e-5g-main`	Same value if expected	Identifies the feed and can drive route logic.
Encryption	AES / passphrase	Same passphrase if encrypted	Encryption fails if values do not match.
Codec	H.264 / HEVC	Receive and route	Use H.264 first if you need the safest ingest test.
Bitrate	Adaptive field link	Watch actual input	Actual incoming bitrate matters more than the planned profile.
Audio	Embedded source	Monitor received audio	Prove audio after ingest, not only at the camera side.
Recording	SD card / file forward	Cloud recording	Local and cloud recordings prove different parts of the workflow.

Air320e-5G multiview workflow with Callaba

The Air and StreamHub side solves compact field contribution. Callaba provides the browser monitoring surface after SRT ingest. This is useful when operators want to compare a field feed with other feeds, watch bitrate changes, verify audio and keep route decisions visible.

After Callaba receives the StreamHub SRT output, the same feed can be monitored, recorded, played back and routed.

Interactive check: open the Callaba multiview demo to see how received sources can look after cloud ingest.

Air320e-5G recorder workflow: SD card recording vs Callaba cloud recording

Air workflows can include local recording and file forwarding on the contribution side. Callaba cloud recording has a different job: it proves that the stream reached the Callaba gateway after StreamHub output.

Layer	What it verifies	Use case
Air local recording	That the field source and local encoded file exist.	Use for source-side backup, highlights, news packages and file forwarding.
Callaba cloud recording	That the StreamHub SRT output actually reached Callaba.	Use when you need cloud-side proof of the received workflow.

Air320e-5G playback workflow with Callaba

Callaba playback means browser player, HLS output, embed link or a cloud route after Callaba receives the StreamHub SRT output. These links are created in Callaba after you set up a web player or HLS path for the incoming stream.

HLS playlist after Callaba ingest:
https://YOUR_CALLABA_DOMAIN/hls/air320e-5g-main/playlist.m3u8

Player or embed page:
https://YOUR_CALLABA_DOMAIN/embed/air320e-5g-main

Where the links come from: these example URLs are not generated automatically for every stream. Callaba creates them after you create a Web Player or HLS packaging path. Depending on your settings, links may include temporary tokens or authorization parameters.

DataBridge and remote control note

Air workflows can include more than a video stream. Haivision describes DataBridge as a way to establish an IP network link together with live video transmission, which can be useful for remote control of connected devices such as PTZ cameras.

Keep this separate from the Callaba ingest path. Use Callaba to receive, monitor, record and route the forward contribution stream. Use the Haivision network/control path when the field team needs remote device access or PTZ control.

For example, if a PTZ camera is connected to the Air unit over Ethernet, DataBridge can let an engineer in the studio control pan, tilt and zoom over the same field connectivity used for the live contribution workflow. Callaba does not participate in that control traffic, but it also does not block it: Callaba receives the SRT media output after StreamHub.

Troubleshooting

Most problems in this setup happen because people debug the wrong layer. Camera input, Air unit state, bonded links, StreamHub, StreamHub SRT output and Callaba are separate checkpoints.

Start from the camera, Air unit and StreamHub receiver state, then debug the SRT output to Callaba.

1. Stream does not appear in Callaba

Confirm Air320e-5G is live and sending to StreamHub.
Confirm StreamHub actually receives the Air feed.
Confirm StreamHub SRT output is enabled and points to the Callaba public IP or DNS name.
Make sure the StreamHub SRT output is set as Caller and the Callaba SRT server is set as Listener.
Check that the Callaba UDP listener port is open.
Check stream ID and passphrase if used.

2. Stream appears, but bitrate or quality changes

Check the mobile network condition and bonded link status on the Haivision side.
Watch actual incoming bitrate in Callaba, not only the planned encoder profile.
Lower the field-side bitrate if the bonded path is unstable.
Avoid testing with the highest quality profile before the contribution path is proven.

3. Connected, but no picture or no audio

Confirm the SDI or HDMI input is active on the Air side.
Start with H.264 for the first Callaba ingest test when possible.
Confirm StreamHub output codec and audio settings are compatible with the Callaba path.
Use Callaba preview or multiview to confirm whether audio exists after ingest.

4. Local recording exists, but Callaba recording is missing

Local recording proves the Air side, not the full cloud ingest path.
Confirm StreamHub received the live feed while the recording was active.
Confirm StreamHub SRT output connected to Callaba during the same time window.
Check time synchronization on Air and StreamHub, preferably through NTP, so local recording timestamps and cloud recording windows can be correlated correctly.
Start a Callaba recording only after the SRT input is visible and stable.

5. Direct Air to Callaba SRT does not work

Check whether your exact firmware and profile actually expose direct SRT output.
Look for fields such as SRT URL, Destination Address, Destination Port, or Streaming Protocol: SRT in the Air output or streaming settings.
Confirm direct SRT support for your exact firmware version through Haivision documentation or Haivision technical support.
If direct SRT is not exposed, use the recommended StreamHub path.
Do not copy settings from a normal SRT encoder guide unless the same fields exist in your Air workflow.

Official references used for this guide

Use these if you need exact Haivision product wording, Air/StreamHub relationship, mobile transmitter behavior or recording details.

FAQ

Can Haivision Air320e-5G send video to Callaba Gateway?

Yes, but the recommended workflow is Air320e-5G to StreamHub, then StreamHub sends an SRT output to Callaba Gateway. Direct Air to Callaba SRT should only be used if the installed firmware and profile explicitly support direct SRT output.

Why use StreamHub between Air320e-5G and Callaba?

StreamHub receives the Haivision mobile contribution feed and acts as the receiver/gateway. It is the clean place to create the SRT output toward Callaba.

Can Callaba record an Air320e-5G workflow?

Yes. After StreamHub sends the SRT output and Callaba receives it, Callaba can record the cloud-side stream as proof that the feed reached the gateway.

Can I monitor Air320e-5G in Callaba multiview?

Yes. After the SRT output reaches Callaba, operators can monitor the received feed in browser preview or multiview depending on deployment and version.

What is the main troubleshooting rule?

Debug in order: camera input, Air unit state, bonded network, StreamHub receiver state, StreamHub SRT output, Callaba listener, then codec, bitrate, audio and downstream workflow.

Final practical rule

Do not collapse the whole workflow into “Air sends SRT to Callaba” unless that is exactly how your firmware and profile are configured. The safer production article is: Air sends mobile contribution to StreamHub; StreamHub sends SRT to Callaba; Callaba handles monitoring, recording, playback and routing.

Last updated: May 19, 2026

Try Callaba Gateway with your Haivision Air workflow

Create an SRT listener in Callaba, send the StreamHub output to the gateway, and monitor the Air field feed before routing it to recording, restreaming, multiview, playback or player delivery.

See SRT server setup Open multiview demo Web Player docs StreamHub docs