Haivision Pro360-5G SRT setup: mobile contribution to Callaba Gateway via StreamHub
More live video workflow notes and product updates.
Haivision Pro360-5G contribution boundary
Choose between direct SRT and bonded cellular before configuring Callaba
The Pro360-5G can contribute one HD camera feed in two materially different ways. It can use a Broadcast SRT profile and an SRT Receiver destination on a selected Ethernet interface, or it can aggregate 3G, 4G, 5G, Ethernet, and Wi-Fi links with Haivision’s SST workflow toward StreamHub. Callaba can receive the direct SRT feed or an SRT output created by StreamHub. It does not terminate SST or perform the Pro360’s cellular bonding.
The practical decision
Use direct SRT for a tested Ethernet contribution. Configure Pro360-5G as Caller and Callaba as Listener, select the correct Ethernet port in the Haivision destination profile, and prove the feed end to end. This is the shortest path and the easiest to diagnose.
Use Pro360-5G → StreamHub when the field job depends on bonded mobile links. The Pro360 sends its Haivision SST contribution to StreamHub. StreamHub reconstructs and receives that operation, then an SRT IP Output hands the selected input to Callaba. The extra component is the protocol boundary that preserves the intended bonding design.
The bars are a conceptual network animation, not modem status or a bandwidth measurement. The direct lane does not become bonded because the unit contains several modems. Motion is disabled for reduced-motion users.
What the Pro360-5G contributes
Haivision describes the Pro360-5G as a mobile transmitter with H.265/HEVC and H.264/AVC encoding, six integrated 5G modems, Ethernet, and Wi-Fi. It accepts a single HD contribution source and supports local recording and file forwarding. Its SST path provides Haivision’s multi-network aggregation and bidirectional services. Video return and the Data Bridge remote-control workflow rely on a StreamHub connection.
The official transmitter documentation also exposes Broadcast SRT as a live-profile application and SRT Receiver as a destination type. That destination asks for Caller or Listener mode, host, SRT port, an Ethernet port, latency, optional SRT encryption and passphrase, and a Stream ID in Caller mode. This is why “SRT” and “six-modem bonding” must not be collapsed into a single setup claim.
| Need | Direct SRT | SST via StreamHub | Callaba role |
|---|---|---|---|
| Simple fixed-network ingest | Yes, through the Ethernet interface defined in the SRT destination. | Possible but adds a receiving component. | Run the SRT Listener and expose transport health. |
| Cellular-link aggregation | Do not assume it. | Yes; Pro360 and StreamHub own the SST bond. | Receive the reconstructed program after StreamHub outputs SRT. |
| Video return and remote device tunnel | Not established by a direct Callaba SRT session. | Haivision documents these with StreamHub. | Continue the forward program; do not claim ownership of the Haivision return path. |
| Field recording | The Pro360 can record to its SD card and forward files according to its record and destination profiles. | Optionally make a separate receiver-side recording for contribution evidence. | |
| Monitoring and distribution | Available after an SRT feed reaches Callaba. | Place the input in Multiview, record it, and route it to the approved next workflow. | |
Procedure A: connect Pro360-5G directly over SRT
Prove the camera and audio
Select the actual SDI or HDMI source supported by the deployed unit, confirm input format and motion, and watch the intended audio meters. Choose HEVC or H.264 for compatibility with the complete receiving path, not merely for its presence in the encoder menu.
Create a Callaba listening point
Use the SRT Server user guide to create and start a Listener. Note the reachable hostname or public IP and its unique UDP port. Allow bidirectional SRT UDP traffic in the relevant network policy.
Create the SRT destination
In the Pro360 web interface, open Streaming and Destination, add a profile, select SRT Receiver, and choose Caller. Enter the Callaba host and port, then choose the Ethernet port that is physically connected to the tested network.
Match the connection contract
Set a measured latency budget and the agreed Stream ID. If encryption is enabled, select the compatible option and enter the same passphrase on both ends. Keep the passphrase outside ordinary runbooks and screenshots.
Create and select a Broadcast SRT live profile
Set the codec, bitrate, audio layout, and transport-stream identifiers needed by the receiver. Select this live profile and the new destination on the dashboard. Avoid changing the source, codec, and SRT security simultaneously during diagnosis.
Start Live and accept media
Confirm the Pro360 shows an active transmission and Callaba shows a sustained bitrate, connection state, and plausible RTT/loss behavior. Add the source to Multiview, listen to audio, and play a short receiver-side recording.
Procedure B: keep bonding in Haivision, then hand off SRT
Create a StreamHub destination profile on the Pro360 and configure the StreamHub address, input assignment, and approved credentials according to the matching Haivision guides. Build a Broadcast SST live profile, select the intended source and audio, and start the field transmission. In StreamHub, verify the correct Pro360 input is present and that the constituent links expected by the production are participating.
Next, create an SRT IP Output in StreamHub. Select Caller when Callaba is the Listener, enter the Callaba address, UDP port, and a latency/security contract that matches the receiving server, then assign the active Pro360 input to that output. Start or confirm the StreamHub output and observe the new session in Callaba.
Monitor both hops. StreamHub is where the operator proves SST reception and bonding state. Callaba is where the team proves the SRT handoff, decoded program, Multiview visibility, recording, and onward routing. A healthy Callaba session cannot show whether all intended cellular links are active; a healthy StreamHub input cannot prove the separate SRT output reached Callaba.
Use two recordings to locate a failure
The Pro360-5G can record locally to SD card, and Haivision documents simultaneous record/forward controls. That field file captures what the transmitter recorded before or alongside network delivery. A Callaba recording captures what arrived after either direct SRT or the StreamHub handoff. Enable each only after checking media state, write availability, remaining capacity, record profile, and destination selection.
After a rehearsal, play both files rather than accepting record icons. If the field copy is clean and the Callaba copy breaks at the same time as transport statistics, the contribution path deserves attention. If both copies contain the same source defect, return to camera, input, or encode. Differences in start time, container, or workflow mean the files are evidence points, not guaranteed frame-identical masters.
Troubleshoot at the correct boundary
Direct SRT never connects
Verify the Pro360 is Caller, Callaba is Listener, host and UDP port match, and the selected Ethernet interface has a route. Compare Stream ID, encryption, and passphrase after basic reachability.
The modems are online but Callaba is empty
Determine which architecture is active. In direct SRT, modem state does not prove Ethernet SRT delivery. In bonded mode, first prove Pro360-to-StreamHub SST, then inspect the separate StreamHub SRT output.
StreamHub has video; Callaba does not
Check that the right StreamHub input is assigned to an enabled SRT output. Confirm Caller/Listener roles, destination port, firewall, latency, and encryption at the StreamHub-to-Callaba hop.
Callaba connects but picture breaks up
Correlate receiver bitrate and loss with Pro360 or StreamHub statistics from the same period. Test representative movement, lower the encode load if sustained capacity is inadequate, and retune recovery from measured RTT and jitter.
Video return is missing
Confirm the transmitter is connected to StreamHub and follow Haivision’s video-return configuration. A forward SRT session into Callaba does not establish the documented StreamHub return service.
The local recovery file is absent
Check that an unlocked SD card is inserted, the correct record profile is selected, and remaining time is available. Start, stop, remove, and play a short file before relying on auto-record or auto-forward.
Make Callaba the visible continuation, not the hidden bond
The Callaba SRT Server page covers receiving, transport statistics, recording, Multiview, restreaming, and playback paths. The Haivision integration hub keeps model and architecture choices in one place. Once the chosen direct or StreamHub-assisted workflow is manually accepted, teams can use the SRT Server API reference for reviewed, repeatable provisioning.
Official Haivision references
- Pro360-5G product page — encoding, six 5G modems, aggregated-link SST workflow, recording, return, and StreamHub ecosystem.
- Current Pro3 Series documentation — current firmware family and official operating guides.
- Pro3 destination profile settings — StreamHub and direct SRT Receiver fields, including SRT mode and Ethernet selection.
- StreamHub SRT IP Output procedure — creating an output and assigning a transmitter input for SRT delivery.
- Pro3 recording procedure — SD-card, record, and forward checks.
Pick the transport boundary before the field team goes live
Launch one receiver, label whether it accepts direct Pro360 SRT or a StreamHub output, and rehearse source loss, network loss, recording, and downstream recovery while every operator can see the same map.