Haivision Air320e-5G SRT setup: compact mobile contribution with Callaba Gateway
More live video workflow notes and product updates.
Haivision Air320e-5G contribution workflow
Choose the Air320e-5G codec first, then preserve it through StreamHub and Callaba
The Air320e-5G can encode H.264/AVC or H.265/HEVC and contribute a field feed over its mobile-network workflow. A practical Callaba integration keeps that upstream contribution visible in StreamHub, creates a dedicated SRT output for the selected input, and verifies that the chosen codec remains usable in every downstream branch.
What makes this page specific to the Air320e-5G
Haivision’s Air Series model matrix lists the Air320e-5G with both HEVC and H.264 hardware encoding, two embedded 5G/4G cellular modems, and additional Wi-Fi, Ethernet, and USB links. The codec choice—not the 5G label—is the most important difference at the Callaba boundary. HEVC may reduce contribution bitrate for a given production target, but it must be accepted by the StreamHub output and every Callaba viewing, recording, and delivery path selected for the event.
The normal mobile design is Air320e-5G over SST to StreamHub, then SRT from StreamHub to Callaba. Haivision separately documents an SRT Receiver destination for Air transmitters, while its network specification identifies direct SRT broadcasting as Ethernet-only. Keep those architectures distinct in the runbook.
The moving bands visualize two configuration choices. They do not compare measured picture quality, bitrate savings, or latency. Reduced-motion settings freeze the graphic.
Decide between H.264 and HEVC from the complete chain
| Decision | H.264 path | HEVC path |
|---|---|---|
| Operational priority | Prefer when the widest compatibility with existing decoders and tools is required. | Consider when the production has validated HEVC across every required receiver and output. |
| StreamHub proof | Confirm the selected H.264 source is decoded and assigned to the intended SRT profile. | Confirm the installed StreamHub release can receive, process, and emit the exact HEVC media profile. |
| Callaba proof | Open a Multiview tile and a short recording; verify picture, audio, and sync. | Repeat the same checks and test each onward consumer rather than stopping at connection state. |
| Recovery plan | Keep an approved H.264 profile if compatibility is more important than bandwidth efficiency. | Define whether a codec change is allowed during recovery and what downstream services must restart. |
Do not switch codecs while diagnosing an SRT handshake. Transport identity, codec, bitrate, and source assignment are different variables. Establish one accepted profile, preserve it during network testing, and record it in the event sheet.
Prepare Callaba before the field transmission
- Create a Callaba SRT Server in Listener mode and start it. Choose an externally reachable host and UDP port, then restrict the cloud and host firewalls to the approved source network where practical.
- Define a publisher name that identifies the event and Air320e-5G source. If the StreamHub output sends a Stream ID, permit the same value on the Callaba side.
- Agree on SRT latency and encryption with the StreamHub operator. The negotiated transport setting is only part of end-to-end delay; encoding, decoding, and display add their own time.
- Add one empty Multiview position or prepare a short recording test. This gives the receiving team a media-level proof immediately after the first session arrives.
The current UI steps are documented in the Callaba SRT Server operator guide. Use the SRT Server API only after the visual workflow and access policy have passed rehearsal.
Bring the Air320e-5G source through StreamHub
- Identify the hardware and firmware. Record the exact Air320e-5G model, software version, enabled services, installed SIMs, input cable, and power plan. Do not reuse a generic “Air” checklist without the model name.
- Prove the physical source. Verify SDI or HDMI input detection and expected embedded audio. Choose H.264 or HEVC in the live profile according to the accepted downstream matrix.
- Select the StreamHub destination. Confirm its host, receiver input assignment, and auto-connect behavior. Start the field transmission and inspect the correct program inside StreamHub.
- Create a separate SRT IP output. Choose SRT in StreamHub, configure Caller or Listener according to the firewall contract, enter port and latency, then match the agreed protection settings.
- Assign the exact Air input. Bind the live Air320e-5G source to the new output. Use a name that exposes source, event, and destination rather than a numbered generic label.
- Accept media in Callaba. Confirm publisher state and sustained bitrate, then prove video and audio in Multiview. Start recording or routing only after the base feed is correct.
Use direct SRT only for the architecture Haivision documents
The Air destination profile can target an SRT Receiver with Caller or Listener mode, host, SRT port, Ethernet port, latency, optional encryption, and a Stream ID in Caller mode. Haivision’s Air network table describes this SRT broadcast mode as Ethernet-only. That can be useful when the unit is on a controlled wired network and Callaba is the intended receiver.
It is not a drop-in substitute for the bonded cellular path. When mobile interfaces and SST are carrying the contribution, StreamHub remains the receiver before the SRT output. State the chosen topology in the title of the event profile so an operator does not assume that a working Ethernet test proves field cellular behavior.
Rehearse source loss and output loss separately
Disconnect or disable one field network path and observe the Air-to-StreamHub evidence. Then, in a separate test, stop the StreamHub SRT output and observe the Callaba session. Finally, interrupt the physical camera input. These faults should produce different operator conclusions even if the viewer sees a similar frozen or missing picture.
If a backup profile changes from HEVC to H.264, test that transition explicitly. Record whether the StreamHub output restarts, whether Callaba creates a new session, and whether recording and downstream playback recover without manual intervention. Do not label the result seamless until it has been observed on the actual production chain.
Troubleshooting by evidence
StreamHub never receives the Air source
Verify destination selection, receiver address and input assignment, network interfaces, camera lock, and live state. Do not adjust the Callaba listener until the source exists upstream.
The SRT session will not establish
Compare modes, destination address, UDP port, firewalls, identity, latency, encryption mode, and passphrase. Confirm the StreamHub output was started after it was created.
Transport is active but the tile is black
Inspect the codec and source inside StreamHub. Verify that the SRT output is carrying the intended input and that the selected Callaba media path accepts its codec profile.
HEVC works in Multiview but not at delivery
Keep the contribution unchanged and test the failing restream, player, or destination independently. A successful internal decode does not establish compatibility for an external consumer.
Audio is missing or mapped incorrectly
Return to the physical input and live profile, then inspect StreamHub before Callaba. Match the audio evidence at each stage instead of rebuilding the SRT connection.
Performance changes at the venue
Correlate field interfaces and StreamHub reception with the same time window. Downstream SRT settings cannot create cellular capacity that is unavailable upstream.
Official product evidence
Confirm Air320e-5G codec and connectivity differences in Haivision’s Air Series product presentation and Haivision Air product page. Use the official destination-profile reference and network specification for the installed release. Configure the downstream handoff from Haivision’s StreamHub SRT output procedure.
The Haivision workflow hub connects this model guide to other Haivision contribution designs. Reconfirm every menu and capability on the production system before air.
Turn the Air320e-5G feed into a proven production source
Choose the codec deliberately, make the StreamHub assignment visible, and accept decoded media in Callaba before adding recording or delivery.