Haivision Air220-5G SRT setup: compact H.264 field contribution with Callaba Gateway
More live video workflow notes and product updates.
Haivision Air220-5G field contribution
Carry an Air220-5G feed through StreamHub and hand one identified SRT output to Callaba
The Haivision Air220-5G is a compact H.264 mobile transmitter with two embedded 5G/4G modems. Its cellular contribution workflow and its SRT handoff are separate parts of the system: the field unit can contribute to StreamHub over Haivision SST, then StreamHub can expose the selected source as an SRT IP output for Callaba to receive, monitor, record, and route.
The architecture in one minute
Use the Air220-5G for camera acquisition, H.264 encoding, and mobile-network contribution. Use StreamHub as the receiver for that field transmission and as the place where an operator selects the intended input. Create a separate SRT IP output from StreamHub to a prepared Callaba SRT Listener. This preserves the bonded field path while giving the downstream team a visible SRT boundary in Callaba.
Haivision also documents an SRT Receiver destination on the Air series, but its published network specification identifies SRT broadcast as Ethernet-only. Do not describe a direct Air-to-Callaba SRT session as bonded 5G contribution. For mobile coverage over aggregated links, keep StreamHub and SST in the path unless the installed product documentation says otherwise.
The moving lanes explain responsibility, not measured bandwidth, link bonding ratios, or automatic failover. The animation stops when reduced motion is requested.
Confirm the exact Air model before copying a profile
“Haivision Air” covers several hardware variants. Haivision’s model table distinguishes the Air220-5G from the Air220 and Air320e-5G. The Air220-5G is documented with H.264/AVC encoding and embedded 3G/4G/5G cellular modems; the Air320e-5G adds HEVC. That difference matters when a profile has been exported from another unit or when a downstream decoder expects HEVC.
| Item | What to verify | Why it matters downstream |
|---|---|---|
| Model label | Air220-5G, not Air220 or Air320e-5G. | It prevents a profile from assuming an encoder option the unit does not provide. |
| Installed firmware | Version shown on the actual transmitter. | Menus and destination capabilities can change between releases. |
| Video source | SDI or HDMI input, expected raster, frame rate, and embedded audio. | A transport can connect successfully while carrying the wrong or absent media. |
| Field destination | Named StreamHub profile and assigned receiver input. | The Callaba branch cannot repair a mistaken upstream assignment. |
| SRT handoff | StreamHub output name, mode, port, identity, latency, and encryption policy. | These values form the contract between StreamHub and Callaba. |
Build the StreamHub-to-Callaba handoff
- Prepare the Callaba receiver. Create an SRT Server in Listener mode, choose a reachable UDP port, and start it. Apply the cloud security group and host firewall rules for that exact path. The current dashboard procedure is in the Callaba SRT Server user guide.
- Choose an identity. Name the publisher for the event and field source. If Stream ID is part of the StreamHub output, allow the same value in Callaba. Keep customer data and secrets out of the identifier.
- Create the StreamHub SRT IP output. In StreamHub, add an IP output profile, select SRT, choose the connection mode, and enter the required port and latency. For the straightforward public-cloud path, StreamHub can call the Callaba listener.
- Match protection settings. When encryption is enabled, configure compatible encryption strength and the same passphrase at both endpoints. Store that value in the production’s secret-management process, not in the page URL or a shared screenshot.
- Assign the Air input. Select the active Air220-5G source and assign it to the SRT output. Creating the output profile alone does not decide which StreamHub input it carries.
- Prove the received media. Confirm an active publisher and sustained bitrate in Callaba, then add a Multiview tile or make a short recording. Inspect motion, picture identity, audio, and sync before attaching onward destinations.
Configure the Air220-5G field side without mixing transports
Create a destination profile for the intended StreamHub and select it on the Air unit. Haivision documents the StreamHub host or IP address, input assignment, and auto-connect option as part of this profile. Create a Broadcast live profile suited to the production’s H.264 and audio requirements, then verify that the correct physical input is locked before going live.
At the venue, inspect every available network interface rather than treating a “connected” icon as proof of useful capacity. Rehearse with the real SIMs and expected coverage. Start the Air contribution and verify the correct source in StreamHub before testing the SRT output to Callaba. This order creates three independent proofs: field encode, StreamHub reception, and downstream SRT handoff.
Accept the workflow with evidence from every boundary
On the Air220-5G, verify source lock, the selected live profile, enabled interfaces, and outbound live state. In StreamHub, confirm the expected transmitter input, audio, and assignment to the correct IP output. In Callaba, confirm publisher identity, connection state, bitrate, and decoded media. Finally, test the actual production branch—recording, restreaming, SRT routing, or browser playback—rather than assuming a healthy Multiview tile proves every output.
Run one controlled interruption during rehearsal. If a cellular interface degrades, observe the Air and StreamHub path. If the StreamHub SRT output is stopped, observe Callaba. The resulting timeline tells operators which alarm belongs to which team and prevents a downstream receiver from being blamed for an upstream source loss.
Troubleshoot the boundary that actually failed
The Air is live, but StreamHub has no input
Check the selected destination profile, StreamHub address, input assignment, credentials, receiver availability, and the Air network interfaces. Keep the Callaba SRT output stopped until the upstream feed exists.
StreamHub has video, but Callaba sees no publisher
Compare the StreamHub SRT mode, Callaba mode, host, UDP port, firewall path, Stream ID, and encryption values. Confirm the IP output has been started and assigned.
Callaba connects without decoded video
Verify the H.264 encode and selected StreamHub source. Inspect audio and video in StreamHub, then test a single Callaba Multiview tile before changing the network settings.
The wrong field source appears
Preserve the working SRT transport and correct the input-to-output assignment in StreamHub. A stable handoff can accurately carry the wrong program.
Mobile quality changes during the event
Inspect the Air contribution interfaces and StreamHub’s incoming evidence. Do not try to solve upstream cellular capacity by increasing an unrelated downstream SRT latency value.
Recording fails while Multiview remains healthy
The field and SRT receiving boundaries have passed. Leave them intact and inspect only the selected Callaba recording or storage workflow.
Official references and next operating layer
Verify the model matrix in Haivision’s Air Series product presentation, the SRT/Ethernet boundary in the official Air network specification, and current profile fields in Adding a Destination Profile. For the second handoff, use Haivision’s StreamHub SRT IP output procedure. Recheck all controls against the firmware installed on the production unit.
For Callaba, use the SRT Server product and operating overview and the SRT Server API reference after the manual workflow has been accepted. The Haivision SRT Gateway hub keeps the neighbouring transmitter and receiver workflows in one device-specific index.
Make the Air220-5G handoff observable
Keep mobile contribution, StreamHub source selection, and Callaba production operations as three visible stages. Then a field problem can be isolated without rebuilding the entire route.