Haivision Play Pro SRT setup: mobile playback and contribution with Callaba Gateway

May 20, 2026

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 Play Pro is a mobile SRT app for iOS and Android. In a Callaba workflow, it can be useful in two ways: as a phone-based SRT viewer for production monitoring, or as a phone-based SRT source for quick mobile contribution.

The important detail is direction. Playback means Callaba provides a feed that Play Pro watches. Contribution means Play Pro sends the phone camera stream into Callaba. Both can use SRT, but the setup steps and operational checks are different.

This guide is written for the search intent behind Haivision Play Pro SRT, Play Pro SRT setup, Play Pro Callaba Gateway, Play Pro multiview, Play Pro recorder, Play Pro playback and mobile SRT Gateway.

Quick answer: how do I use Haivision Play Pro with Callaba Gateway?

For mobile playback, create or expose an SRT endpoint in Callaba and open it in Play Pro. For phone contribution, create an SRT listener in Callaba and configure Play Pro to Stream to that Callaba public IP or DNS name, UDP port, latency, stream ID if used and passphrase if encryption is enabled.

Play Pro can sit on either side of the workflow: mobile viewer for a Callaba SRT feed or mobile source into Callaba Gateway.

What this setup does

This setup connects Play Pro and Callaba Gateway over SRT. Depending on the job, Play Pro can be the viewer or the source.

Mobile playback: Play Pro watches a live SRT feed coming from Callaba.
Mobile contribution: Play Pro sends a live SRT stream from the phone camera into Callaba.
Callaba operations: Callaba handles browser monitoring, recording, routing, playback and downstream delivery around the SRT feed.

Two workflows: play vs stream

The first decision is not Caller or Listener. The first decision is whether the phone should watch a stream or create a stream.

Keep mobile playback and mobile contribution as separate workflows. They use different operational checks.

Recommended SRT mode

For most phone networks, start with Play Pro as Caller and Callaba as Listener. This avoids exposing an inbound port on the phone, which is usually difficult or impossible on mobile networks.

This can apply to both workflows: Play Pro can connect to a Callaba SRT endpoint to watch a feed, or it can connect to a Callaba SRT listener and send the phone camera feed.

Important: Caller/Listener is the SRT handshake role. It is not the same thing as source/destination. Always check which side is sending video and which side is receiving video.

Play Pro as Caller is usually the most practical mode for phone-based networks.

Before you start

Prepare the phone side and the Callaba side separately. Most errors are caused by mode mismatch, blocked UDP ports, passphrase mismatch, or phone network behavior.

Play or Stream Decide if Play Pro is only watching a Callaba feed or sending a phone camera feed into Callaba.

App version Make sure Play Pro is updated before testing. Older app versions may expose different SRT options, codec behavior, encryption fields or setup flows.

Phone permissions For contribution, confirm camera, microphone, mobile data, notifications and background behavior.

Battery and thermal Use a power bank. Long streams can overheat the phone and cause throttling or shutdown. Test thermal behavior before the live window.

Background app behavior Make sure the phone does not put Play Pro to sleep. On iOS, keep the app in foreground when possible. On Android, disable battery optimization if needed.

Callaba address Use the public IP address or DNS name of the Callaba instance.

UDP port Choose one UDP port, open it in the cloud firewall, and use the same port in Play Pro.

Workflow A: play a Callaba SRT feed on Play Pro

Use this when someone needs to watch a live feed on a phone. Examples: producer confidence monitoring, field return view, remote engineering check, or quick SRT validation.

Prepare the live source inside Callaba.
Create or expose an SRT endpoint for mobile playback.
Use Listener on the Callaba side when Play Pro will connect as Caller.
Open the selected UDP port.
Open Play Pro and choose Play an SRT Stream.
Set SRT mode to Caller, then enter Callaba address, port, latency and encryption values if used.
Tap Play and confirm the stream on the phone.

srt://YOUR_CALLABA_IP:11100?mode=caller&latency=200&streamid=play-pro-return

Workflow B: stream from Play Pro to Callaba

Use this when the phone itself is the source. This can be useful for quick field contribution, backup camera workflows, event checks, engineering tests, or simple mobile reporting.

Create an incoming SRT server/listener in Callaba.
Choose a UDP port, for example 11110, and open it in the firewall.
Set stream ID and passphrase if needed.
Open Play Pro and use the Stream workflow.
Set protocol to SRT.
Set mode to Caller and enter the Callaba public IP or DNS name.
Set port, latency, codec, bitrate, resolution, frame rate and audio bitrate.
Start streaming and check Callaba preview, bitrate, codec, audio and recording.

srt://YOUR_CALLABA_IP:11110?mode=caller&latency=300&streamid=play-pro-phone-main

Testing rule: use H.264, 720p or 1080p, moderate bitrate and a clean Wi‑Fi or 5G connection for the first test. After Callaba sees stable video and audio, tune quality.

Settings table

Use this table to avoid mismatches. The same values must be entered on both sides where relevant.

Start with the simplest SRT configuration. Add encryption and production profiles after the first clean connection.

Setting	Play Pro	Callaba Gateway	Why it matters
Workflow	Play or Stream	Output or listener	Defines media direction.
SRT mode	Caller first	Listener first	Usually easier on phone networks.
Address	Callaba IP / DNS	Public endpoint	Play Pro must reach Callaba.
Port	Destination UDP port	Open listener port	Wrong port means no connection.
Latency	100–500 ms test	Same policy	Too low can break unstable mobile paths.
Stream ID	`play-pro-phone-main`	Same value if expected	Identifies the feed.
Encryption	On or off	Same setting	Must match.
Codec / bitrate / audio	H.264 first, moderate bitrate	Preview and monitor	Proves the stream is usable, not only connected.

Playmaker links and QR codes

For non-technical users, do not ask them to type SRT URLs manually on a phone. Use Playmaker-style setup links or QR codes when possible. This reduces mistakes with ports, passphrases, latency values and encoded URL parameters.

This is useful for return monitoring: you can prepare a Callaba SRT playback endpoint, generate the Play Pro configuration link or QR code, and send it to the person who needs to watch the feed.

Example Play Pro link for mobile SRT playback:

haivisionplaypro://play?url=srt%3A%2F%2FYOUR_CALLABA_IP%3A11100%3Fmode%3Dcaller%26latency%3D200%26streamid%3Dplay-pro-return

The SRT URL is URL-encoded inside the Play Pro link. You can turn this link into a QR code with the official Playmaker tool or with a trusted QR generator.

Play Pro and Callaba multiview

Play Pro is useful for one-person mobile monitoring. Callaba multiview is useful when operators need to compare the Play Pro feed with other live sources, check audio, watch bitrate and keep route state visible in a browser.

Play Pro is the mobile edge. Callaba is the cloud operational layer for monitoring, recording and routing.

Interactive check: open the Callaba multiview demo to see how received sources can look after cloud ingest.

Play Pro recorder workflow

If Play Pro sends a live SRT stream into Callaba, Callaba can record the received stream. That cloud recording proves that the phone stream reached the gateway and was available to the workflow.

A local phone recording and a Callaba recording prove different things. The phone recording proves the source side. The Callaba recording proves the cloud ingest side.

Play Pro can also be used in a store and forward style workflow when video is recorded on the phone and sent later as a file. For live cloud monitoring in Callaba, use the live SRT streaming mode instead. Local phone recording and Callaba cloud recording are different operational proofs.

Play Pro playback workflow with Callaba

There are two playback options in this type of workflow. Play Pro can play SRT directly on a phone. Callaba can also create browser playback or HLS/embed links for viewers who should not use an SRT app.

SRT playback in Play Pro:
srt://YOUR_CALLABA_IP:11100?mode=caller&latency=200&streamid=play-pro-return

Browser/HLS playback after Callaba ingest:
https://YOUR_CALLABA_DOMAIN/hls/play-pro-phone-main/playlist.m3u8

Where browser links come from: HLS or browser playback is not automatic for every SRT session. Callaba creates player or HLS links after you create a Web Player or HLS packaging path for that stream. Depending on your settings, links may include temporary tokens or authorization parameters.

Troubleshooting

Most Play Pro issues are not codec mysteries. They are mode, port, firewall, passphrase, phone network or battery/thermal issues.

Start from the phone and the selected Play Pro workflow, then check SRT mode, UDP port, Callaba listener, stream ID, passphrase and media settings.

1. Play Pro cannot connect

Confirm one side is Caller and the other side is Listener.
Confirm Play Pro is using the correct Callaba public IP or DNS name.
Confirm the UDP port is open in the Callaba firewall or security group.
Check stream ID and passphrase if used.

2. Connected, but no picture or no audio

For contribution, check phone camera and microphone permissions.
Start with H.264 and a moderate bitrate.
Check Callaba preview or multiview to confirm the received codec, bitrate and audio.
If only Play Pro playback fails, test the same SRT endpoint with another known-good receiver.

3. Stream stops after several minutes

Check phone temperature and battery state. Thermal throttling can reduce performance or stop the app.
Keep the phone powered, ventilated and out of direct sun where possible.
Make sure the operating system is not suspending Play Pro in the background.

4. Bitrate changes or stream stutters

Test one network path at a time: Wi‑Fi only, then 4G/5G only.
To isolate whether cellular is the problem, temporarily enable airplane mode, turn on only Wi‑Fi, and compare that result with 4G/5G-only operation.
Increase SRT latency if the network is unstable.
Lower video bitrate, resolution or frame rate for contribution from the phone.
Avoid very low latency values on unstable mobile networks.

Official references used for this guide

Use these if you need exact Play Pro setup wording, QuickPlay behavior, Stream mode behavior, URL schema, or app store details.

FAQ

Can Haivision Play Pro play an SRT stream from Callaba?

Yes. Use Play Pro's SRT playback workflow and configure the matching Callaba SRT endpoint. The simplest remote pattern is usually Play Pro as Caller and Callaba as Listener.

Can Play Pro send an SRT stream to Callaba?

Yes. Play Pro can create a live SRT stream from the mobile device. For a simple contribution test, configure Play Pro as Caller and Callaba as Listener.

Can Callaba record a Play Pro stream?

Yes. If Play Pro sends a live SRT stream to Callaba and the input is visible, Callaba can record the received stream.

Should I use Caller or Listener?

For most phone networks, use Play Pro as Caller and Callaba as Listener. This avoids requiring inbound access to the phone.

Yes. Haivision Playmaker can generate Play Pro setup links and QR codes for non-technical users.

Final practical rule

Decide whether Play Pro is a viewer or a source before you configure SRT. Then match Caller/Listener, address, port, latency, stream ID, encryption and passphrase. Do not debug codec settings before the SRT session itself is proven.

Last updated: May 20, 2026

Try Callaba Gateway with Play Pro

Create an SRT listener in Callaba, test Play Pro as a mobile source or mobile viewer, then monitor the feed in multiview before routing it to recording, restreaming, playback or player delivery.

See SRT server setup Open multiview demo Web Player docs Playmaker tool