media server logo
PricingAPI docsLaunch SRT server

Haivision Pro360-5G SRT setup: mobile contribution to Callaba Gateway via StreamHub

May 19, 2026
Iurii Pakholkov, founder of Callaba

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 Pro360-5G is a mobile video transmitter for live field contribution over bonded cellular and IP networks. It is useful when a camera team needs to send HD video from a sports venue, street location, live event, vehicle or remote site back to a production workflow.

The important Callaba nuance is this: do not treat Pro360-5G as a normal hardware SRT encoder in every setup. The standard Haivision mobile contribution path is usually Pro360-5G → StreamHub receiver/gateway → SRT output → Callaba Gateway. Use direct Pro360-5G 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 Pro360-5G SRT, Pro360-5G multiview, Pro360-5G recorder, Pro360-5G playback, Haivision mobile transmitter SRT Gateway, StreamHub SRT output and Callaba SRT Gateway.

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

Use Haivision StreamHub as the receiver for the Pro360-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.

Haivision Pro360-5G mobile transmitter to Callaba Gateway SRT workflow Infographic showing Haivision Pro360-5G sending bonded cellular video to Haivision StreamHub, then SRT output from StreamHub to Callaba Gateway for multiview, recording, playback and routing. Pro360-5G + Callaba Gateway Bonded 5G field contribution · StreamHub receiver · SRT into Callaba Pro360-5G bonded cellular field unit SST / bonded links StreamHub receiver / gateway / SRT out SRT output Callaba monitor, record, play, route Field unit StreamHub SRT Callaba ops
The clean workflow is Pro360-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 a live mobile contribution feed from Pro360-5G into Callaba Gateway. The Pro360-5G handles bonded mobile transmission. StreamHub receives that contribution feed and turns it into a production-ready output. Callaba receives the SRT output and becomes the cloud-side control point for monitoring, recording, playback and routing.

  • Pro360-5G: captures and sends live HD video over bonded 3G, 4G, 5G, Ethernet or Wi-Fi paths.
  • StreamHub: receives the Haivision mobile contribution stream and can provide an SRT output.
  • Callaba Gateway: receives the SRT output and provides browser preview, multiview, recording, playback and routing tools.

Important SRT nuance: Pro360-5G is not always a direct SRT-to-Callaba encoder

This article should be honest because the search query can be misleading. A user searching for Pro360-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 assumption.

Haivision positions Pro360-5G as part of a mobile contribution ecosystem where the field unit streams to StreamHub. StreamHub is the receiver/gateway layer that can then distribute the stream to SDI, IP or cloud production workflows.

How to check direct SRT: in the Pro360-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.

Two Pro360-5G to Callaba SRT workflow choices Infographic comparing the recommended StreamHub to Callaba SRT path with a direct Pro360-5G to Callaba SRT path only when firmware and configuration expose direct SRT output. Two ways to think about SRT with Pro360-5G Use the StreamHub path by default. Use direct SRT only if your firmware/profile explicitly supports it. Recommended path Pro360-5G → StreamHub → SRT → Callaba Use Pro360-5G for bonded cellular contribution. Use StreamHub as the receiver/gateway. Send SRT from StreamHub into Callaba Gateway. best for normal operations Conditional path Pro360-5G → SRT → Callaba Use only if the installed firmware and profile expose direct SRT output fields. Do not assume this from the product name alone. verify before writing the guide
Use StreamHub as the reliable default path. Only describe direct SRT if the exact firmware/profile exposes direct SRT output settings.

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.

Pro360-5G state Confirm the field unit is live, has camera input, has power and has bonded network connectivity.
StreamHub receiver Confirm StreamHub receives the Pro360-5G 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.
Codec path Start with H.264 for the first Callaba test if possible, then test HEVC after the preview, recorder and player path are confirmed.
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

  1. Open your Callaba Gateway environment.
  2. Go to SRT Servers and create a new incoming SRT server.
  3. Set the role to Listener if the UI exposes this option.
  4. Choose a UDP port, for example 10700.
  5. Set latency for the StreamHub-to-Callaba SRT path, for example 200–500 ms as a starting point.
  6. Add stream ID and passphrase if your workflow requires them.
  7. Open the selected UDP port in the cloud firewall or security group.
  8. Copy the Callaba SRT publisher URL or copy the host, port and SRT settings for StreamHub.

Testing rule: prove Pro360-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 Pro360-5G feed, configure an SRT output or route from StreamHub to the Callaba SRT listener.

  1. Confirm the Pro360-5G feed is live inside StreamHub.
  2. Create an output route for that feed.
  3. Choose SRT as the output protocol if your StreamHub version exposes this output type.
  4. Set StreamHub as Caller and Callaba as Listener for the simplest cloud ingest model.
  5. Enter the Callaba public IP address or DNS name.
  6. Enter the UDP port that Callaba is listening on.
  7. Match stream ID, latency and passphrase if used.
  8. Start the StreamHub output and check connection state, bitrate, codec, audio and preview in Callaba.
Command 
srt://YOUR_CALLABA_IP:10700?mode=caller&latency=300&streamid=pro360-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. If your production needs confidence video or intercom, treat that as a separate design item and review the video return and intercom note.

Haivision Pro360-5G StreamHub to Callaba SRT settings table Infographic listing settings for StreamHub SRT output to Callaba Gateway after receiving Haivision Pro360-5G bonded cellular contribution, including mode, address, port, latency, stream ID, passphrase, codec, bitrate, audio and return workflow. Settings that matter after StreamHub Pro360-5G handles mobile contribution. StreamHub outputs SRT. Callaba receives and controls the cloud workflow. Field StreamHub / Pro360 side Callaba Gateway Why Receiver pathPro360 to StreamHubSRT from StreamHubworkflow truth SRT modeCaller outputListener inputconnection AddressCallaba IP / DNSpublic endpointreachability Portdestination UDPopen listener portfirewall LatencySRT output buffersame policyjitter Stream IDset on SRT outputroute/access logicidentify feed EncryptionAES/passphrasesame passphrasesecurity CodecH.264 / HEVCreceive + routecompatibility Bitratemobile adaptive outputwatch actual inputquality Audioprogram / intercommonitor received audioops Return feedvia Haivision flowseparate route if neededconfidence
The SRT settings that must match are usually on the StreamHub-to-Callaba leg.
Setting StreamHub / Pro360 side Callaba Gateway Why it matters
Receiver path Pro360-5G to StreamHub SRT from StreamHub Separates mobile contribution from Callaba ingest.
SRT mode Caller output Listener input One side waits, the other connects.
Port Destination UDP port Open listener UDP port Wrong port means no connection.
Stream ID pro360-5g-main Same value if expected Identifies the feed and can drive route logic.
Passphrase Same passphrase if encrypted Same passphrase if encrypted Encryption fails if values do not match.
Bitrate Mobile contribution can adapt Watch actual received bitrate Actual incoming bitrate is more useful than the planned bitrate.
Return feed via Haivision flow separate route if needed confidence / intercom

Pro360-5G multiview workflow with Callaba

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

After Callaba receives SRT from StreamHub for Pro360-5G workflow Infographic showing Callaba browser multiview, recorder, player playback, failover and downstream routing after receiving SRT output from StreamHub for Haivision Pro360-5G field contribution. After ingest: what Callaba adds Once StreamHub sends SRT to Callaba, operators can control the cloud side of the workflow. Multiview browser preview bitrate, codec, audio Recorder cloud proof of received stream Playback web player, HLS or embed link Routing restream failover one mobile SRT output → monitoring, proof, playback and routing
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.

Pro360-5G recorder workflow: field recording vs Callaba cloud recording

Haivision mobile workflows can include recording and forwarding on the mobile 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
Haivision field side That the field source and contribution profile were captured. Use for local contribution-side backup and forwarding workflows.
Callaba cloud recording That the StreamHub SRT output actually reached Callaba. Use when you need cloud-side proof of the received workflow.

Pro360-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.

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

Player or embed page:
https://YOUR_CALLABA_DOMAIN/embed/pro360-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.

Video return and intercom note

Pro360-5G workflows can include video return and two-way audio/intercom coordination inside the Haivision contribution ecosystem. Keep this separate from the Callaba ingest path unless you intentionally design a return route.

In practical terms: use Callaba to receive, monitor, record and route the forward contribution stream. Use the Haivision return/intercom path when the field unit needs confidence video, teleprompting or communication from the production side.

Troubleshooting

Most problems in this setup happen because people debug the wrong layer. Pro360-5G, bonded links, StreamHub, StreamHub SRT output and Callaba are separate checkpoints.

Haivision Pro360-5G StreamHub to Callaba troubleshooting path Troubleshooting path for Haivision Pro360-5G with StreamHub SRT output to Callaba: check field unit, bonded network, StreamHub receiver state, SRT output, Callaba listener, codec, bitrate, audio and recording. Debug the mobile contribution chain in this order Do not start with Callaba only. First prove the field unit and StreamHub receiver state. 1. Field unit camera, profile, battery 2. Bonded links 5G / LTE / Wi-Fi / IP 3. StreamHub receiver state 4. SRT out port, ID, AES 5. Callaba listener + preview 6. Media codec, bitrate, audio 7. Workflow record, play, route
Start from the field unit and StreamHub receiver state, then debug the SRT output to Callaba.

1. Stream does not appear in Callaba

  • Confirm Pro360-5G is live and sending to StreamHub.
  • Confirm StreamHub actually receives the transmitter feed.
  • Confirm StreamHub SRT output is enabled and points to the Callaba public IP or DNS name.
  • 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 camera input is active on the Pro360-5G 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. Direct Pro360-5G 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 Pro360-5G 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 Pro360-5G workflow.

Official references used for this guide

Use these if you need exact Haivision product wording, StreamHub/Pro360 relationship, mobile transmitter behavior or hardware specification details.

FAQ

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

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

Should I connect Pro360-5G directly to Callaba over SRT?

Do not assume direct SRT from the product name alone. For most workflows, use StreamHub as the receiver/gateway and send SRT from StreamHub to Callaba.

Can Callaba record a Pro360-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 Pro360-5G in Callaba multiview?

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

What is the main troubleshooting rule?

Debug in order: field unit, 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 “Pro360-5G sends SRT to Callaba” unless that is exactly how your firmware and profile are configured. The safer production article is: Pro360-5G 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 Pro360-5G workflow

Create an SRT listener in Callaba, send the StreamHub output to the gateway, and monitor the Pro360-5G 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