media server logo
PricingAPI docsLaunch SRT server

Haivision Pro460 SRT setup: multi-camera remote production with Callaba Gateway

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 Pro460 is a 5G mobile video transmitter for remote production over bonded cellular and IP networks. Its strongest angle is not a single-camera field hit. It is synchronized multi-camera contribution for sports, live events and news workflows, with quad-HD or single 4K-class production paths.

The important Callaba nuance is this: do not treat Pro460 as a normal direct SRT encoder in every setup. The safer production workflow is Pro460 → StreamHub receiver/gateway → SRT output → Callaba Gateway. Use direct Pro460 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 Pro460 SRT, Pro460 multiview, Pro460 recorder, Pro460 playback, Haivision multi-camera transmitter SRT Gateway, StreamHub SRT output and Callaba SRT Gateway.

Quick answer: how do I connect Haivision Pro460 to Callaba Gateway?

Use Haivision StreamHub as the receiver for the Pro460 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 Pro460 multi-camera mobile transmitter to Callaba Gateway SRT workflow Infographic showing Haivision Pro460 bonded 5G multi-camera contribution to StreamHub, then SRT output to Callaba Gateway for multiview, recording, playback and routing. Pro460 + Callaba Gateway Multi-camera 5G remote production · StreamHub receiver · SRT into Callaba Pro460 quad-HD or 4K mobile TX bonded 5G / IP StreamHub receiver / decoder / SRT out SRT output Callaba monitor, record, play, route 4 cameras StreamHub SRT Callaba ops
The clean workflow is Pro460 to StreamHub first, then StreamHub sends SRT to Callaba Gateway for browser monitoring, recording, playback and routing.

What this setup does

This workflow gets one or more Pro460 contribution feeds into Callaba Gateway. Pro460 handles multi-camera 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.

  • Pro460: captures quad-HD or 4K-class production video 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: Pro460 is usually part of a StreamHub workflow

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

Haivision positions Pro460 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 IP, SDI, cloud and SRT workflows.

How to check direct SRT: in the Pro460 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 Pro460 to Callaba SRT workflow choices Infographic comparing the recommended StreamHub to Callaba SRT path with a conditional direct Pro460 to Callaba SRT path only when firmware and configuration expose direct SRT output. Two ways to think about SRT with Pro460 Use the StreamHub path by default. Use direct SRT only if your firmware/profile explicitly supports it. Recommended path Pro460 → StreamHub → SRT → Callaba Use Pro460 for bonded multi-camera contribution. Use StreamHub as the receiver/gateway. Send SRT from StreamHub into Callaba Gateway. best for remote production Conditional path Pro460 → SRT → Callaba Use only if the installed firmware and profile expose direct SRT output fields. Do not assume direct SRT from product name alone. verify firmware first
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.

Camera state Confirm all required camera inputs, audio sources and sync/genlock behavior before debugging cloud ingest.
Genlock / sync Confirm that all cameras are frame-synchronized when your workflow requires it. Check genlock, timecode, lip sync and feed order before debugging Callaba.
StreamHub receiver Confirm StreamHub receives the Pro460 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 10800.
  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 Pro460 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 Pro460 feed, configure an SRT output or route from StreamHub to the Callaba SRT listener.

  1. Confirm the Pro460 feed is live inside StreamHub.
  2. Create an output route for that feed or camera group.
  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:10800?mode=caller&latency=300&streamid=pro460-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, intercom or remote camera control, treat that as a separate design item and review the video return, intercom and remote camera control note.

Haivision Pro460 StreamHub to Callaba SRT settings table Infographic listing settings for StreamHub SRT output to Callaba Gateway after receiving Haivision Pro460 bonded multi-camera contribution, including mode, address, port, latency, stream ID, passphrase, codec, bitrate, audio and return workflow. Settings that matter after StreamHub Pro460 handles multi-camera mobile contribution. StreamHub outputs SRT. Callaba receives and controls the cloud workflow. Field StreamHub / Pro460 side Callaba Gateway Why Receiver pathPro460 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 Syncmulti-camera statewatch all feedsremote prod 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 / Pro460 side Callaba Gateway Why it matters
Receiver path Pro460 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 pro460-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.
Sync Multi-camera state Watch all received feeds Remote production depends on source timing.
Audio Program / intercom Monitor received audio Prove audio after ingest, not only at the camera side.
Return feed via Haivision flow separate route if needed confidence video / intercom / control

Pro460 multiview workflow with Callaba

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

After Callaba receives SRT from StreamHub for Pro460 workflow Infographic showing Callaba browser multiview, recorder, player playback, failover and downstream routing after receiving SRT output from StreamHub for Haivision Pro460 multi-camera contribution. After ingest: what Callaba adds Once StreamHub sends SRT to Callaba, operators can control the cloud side of the multi-camera workflow. Multiview browser preview multi-feed board Recorder cloud proof of received feeds Playback web player, HLS or embed link Routing restream failover multi-camera 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.

Pro460 recorder workflow: field recording vs Callaba cloud recording

Haivision mobile workflows can include recording and progressive 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
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.

Pro460 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/pro460-main/playlist.m3u8

Player or embed page:
https://YOUR_CALLABA_DOMAIN/embed/pro460-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, intercom and remote camera control

Pro460 workflows can include video return, two-way intercom and remote camera control inside the Haivision contribution ecosystem. Keep those paths 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/control path when the camera team needs confidence video, teleprompting, IFB or production-side coordination.

For the Haivision side of that workflow, check the official Pro460 product presentation documentation, which describes Video Return and bi-directional audio intercom.

Troubleshooting

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

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

1. Stream does not appear in Callaba

  • Confirm Pro460 is live and sending to StreamHub.
  • Confirm StreamHub actually receives the transmitter feed or camera group.
  • 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. Multi-camera sync or feed order looks wrong

  • Check all camera inputs before debugging Callaba.
  • Confirm genlock or synchronization settings on the Pro460 side if your workflow requires frame-synced feeds.
  • Confirm StreamHub sees the correct feed order before sending output to Callaba.
  • Use clear stream IDs such as pro460-cam-1, pro460-cam-2 or pro460-program.

3. 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 4K/HDR profile before the contribution path is proven.

4. Connected, but no picture or no audio

  • Confirm the camera input is active on the Pro460 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.

5. Direct Pro460 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 Pro460 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 Pro460 workflow.

Official references used for this guide

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

FAQ

Can Haivision Pro460 send video to Callaba Gateway?

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

Why use StreamHub between Pro460 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 a Pro460 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 Pro460 feeds in Callaba multiview?

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

What is the main troubleshooting rule?

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

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

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