Kiloview P3 field bonding encoder SRT setup to Callaba Gateway

May 16, 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

Kiloview P3 is a wireless bonding encoder for field production, mobile live streaming and unstable uplink environments.

The practical Callaba path is simple: send SRT from P3 to Callaba Gateway, then use the received feed for browser multiview, cloud recording, playback, routing and delivery.

This guide is written for the search intent behind Kiloview P3 SRT, Kiloview P3 bonding encoder, Kiloview P3 multiview, Kiloview P3 recorder, Kiloview P3 playback, Kiloview P3 Mini SRT and Callaba SRT Gateway.

Quick answer: how do I connect Kiloview P3 to Callaba Gateway?

Create an SRT server in Callaba Gateway in Listener mode, open the selected UDP port, then configure the Kiloview P3 SRT service or SRT-TS push, often labeled Push URL, Push Address or Server Address, to send to the Callaba public IP or DNS name. Match the port, latency, stream ID if used, passphrase if used, codec, bitrate and audio settings. After Callaba receives the stream, you can monitor it in multiview, record it, play it back or route it to other destinations.

The recommended first test is direct SRT from Kiloview P3 to a Callaba SRT listener.

What this setup does

This workflow sends a live video feed from a Kiloview P3 encoder to Callaba Gateway over SRT. Callaba receives the stream in the cloud, then the feed can be monitored, recorded, previewed, routed, restreamed, used in a web player or placed into a browser-based multiview board.

Kiloview P3 captures HDMI, SDI or USB source content and sends the encoded stream.
Callaba Gateway listens on a public UDP port and accepts the incoming SRT stream.
Operators use Callaba to check preview, bitrate, codec, packet loss, recording, multiview, playback and route behavior.

P3 sends the field source. Callaba turns that source into a monitored and routable cloud workflow.

Kiloview P3 and P3 Mini workflow notes

The P3 family is built around mobile contribution. The full P3 is a stronger fit when you need 5G bonding and 4K HDMI input. P3 Mini is a smaller 4G bonding option for lighter mobile kits. In both cases, the Callaba workflow starts when an SRT stream reaches the gateway.

Use the P3 model for the field network you actually have. Keep Callaba as the cloud workflow layer after ingest.

Device	Best Callaba angle	Protocol path
Kiloview P3 5G	Field contribution from HDMI, SDI or USB to cloud multiview, recording and playback.	Direct SRT to Callaba, or bonding path through KiloLink before distribution.
Kiloview P3 Mini	Smaller mobile kit contribution where 1080p workflows are enough.	Direct SRT to Callaba when bonding is not required, or bonded workflow when mobile network reliability is the priority.

Direct SRT vs bonding path

Do not mix two different problems. SRT ingest is about sending a reliable contribution stream to Callaba. Bonding is about combining several network links when the field uplink is not reliable enough.

Start with direct SRT if you can. Use bonding when the field network is the main risk.

For the first Callaba test, I would use direct SRT from P3 to Callaba. Once that works, decide whether the production needs KiloLink bonding before the stream reaches downstream workflows.

Bonding path note:

In a bonding workflow, P3 sends aggregated links to KiloLink Server or KiloLink Server Pro, which handles bonding and centralized management. From there, you can forward a clean production stream into Callaba or another downstream workflow. This article focuses on direct SRT to Callaba first because it is the simplest way to validate the gateway connection.

Recommended SRT mode: Callaba Listener, P3 SRT push

For most cloud ingest workflows, the cleanest model is:

Callaba Gateway: Listener
Kiloview P3: SRT push / caller to the Callaba IP and port

This keeps the public listening port on the Callaba side. The field device only needs to send outbound UDP traffic to Callaba. That is usually easier than exposing the P3 to inbound traffic on a venue or mobile network.

A template SRT URL looks like this:

srt://YOUR_CALLABA_IP:10120?mode=caller&latency=300&streamid=kiloview-p3-main

A filled example for field testing can look like this:

srt://demo.callaba.io:10120?mode=caller&latency=300&streamid=kiloview-p3-main

Use the second example as a template. Replace host, port, stream ID and passphrase with your own Callaba values.

Before you start

Prepare the SRT connection before changing production settings. On mobile networks, it is especially important to avoid changing port, bitrate, latency, bonding and codec settings all at once.

For the first mobile test, use a conservative profile such as 720p at 30 fps. This reduces bitrate variation and gives more headroom for cellular network changes. After the link is stable, move to 1080p or higher profiles if the uplink can support them.

Before you start: confirm the exact P3 firmware and module setup you are using. P3 can work with direct protocols and KiloLink bonding, but the field network, firmware and module configuration decide the best practical path.

Callaba public address Use the public IP address or DNS name of the Callaba instance that will receive the SRT stream.

UDP port Choose one UDP port for this P3 input and make sure it is open in the cloud firewall or security group.

Latency Start higher than a studio LAN value. Mobile and venue networks need more room for jitter recovery.

Bitrate Keep bitrate below your real uplink capacity. Leave room for network variation and audio.

Stream ID Use a clear name such as kiloview-p3-main if your workflow uses stream ID routing.

Media profile Confirm H.264 or H.265, resolution, frame rate, bitrate and audio format.

Step 1: create the SRT listener in Callaba

In Callaba, create a new incoming SRT server for the Kiloview P3 feed. The exact module name can differ by UI version, but the operational idea is the same: Callaba opens a UDP port and waits for P3 to push the stream.

Open your Callaba environment.
Create a new SRT input or SRT server.
Set the role to Listener if the UI exposes this option.
Choose a UDP port, for example 10120.
Set latency, for example 300 ms as a mobile-network starting point.
Add a stream ID if your routing model uses it.
Add the same passphrase that you plan to use on P3, if encryption is needed.
Open the UDP port in your cloud firewall or security group.

Step 2: configure Kiloview P3 SRT pushing

In the Kiloview P3 web interface, configure the encoding stream and add an SRT service. Kiloview documentation describes this path as adding SRT-TS pushing under the encoding and stream settings, then filling in the pushing address and port.

Confirm the HDMI, SDI or USB input is locked and visible on P3.
Open the encoding and stream settings.
Choose the main stream first for the first test.
Add an SRT or SRT-TS pushing service.
Enter the Callaba public IP address or DNS name as the push target.
Enter the same destination UDP port that Callaba is listening on.
Set latency, stream ID and passphrase if your Callaba listener expects them.
Start the stream and watch for connection state in Callaba.

For the first test, do not start with the highest bitrate, every stream service enabled and bonding complexity at the same time. Make one direct SRT feed stable first.

Settings table

This table is the fastest way to avoid mismatches. The words in the Kiloview interface can differ, but the values must describe the same SRT connection.

Match SRT transport settings first. Then verify source, codec, bitrate, audio and workflow outputs.

Setting	Callaba Gateway	Kiloview P3	Why it matters
Mode	Listener	SRT push / caller	One side must wait, the other side must send or connect.
Address	Public IP or DNS	Pushing address	P3 must send to the reachable Callaba address.
Port	Open UDP port	Same target port	A wrong or blocked port looks like no connection.
Latency	Start around 300 ms for mobile tests	Same or close value	Mobile networks usually need more jitter room.
Bitrate	Ingest capacity	Below real uplink capacity	Too much bitrate causes drops before Callaba can help.
Codec	H.264 or H.265 received by Callaba	Same codec/profile selected on P3	H.264 is the safer first test for mobile contribution and downstream compatibility.
Audio	AAC or MP3 detected in Callaba	Same audio format selected on P3	AAC is usually the safer first choice for live contribution workflows.

Kiloview P3 multiview workflow with Callaba

P3 does not need to be your multiview system. It can be the field encoder. After Callaba receives the SRT stream from P3, the feed can be placed on a browser-based multiview board with other cameras, backup paths, remote sources or player outputs.

This is useful when the production team wants to see field sources in the browser before deciding what to route, record or deliver.

Interactive check: open the Callaba multiview demo to see how a received field source can look after cloud ingest. Your real P3 feed would appear as a live input in your own deployment.

Kiloview P3 recorder workflow: field-side storage vs cloud recording

P3 can be configured with storage and recording-related modules, but Callaba adds a different layer: cloud-side recording after SRT ingest. These two recordings protect different points in the chain.

Field backup: P3 supports local recording to an SD card or USB storage drive. This gives the field team a source-side backup that is independent from network conditions, while Callaba cloud recording shows what actually reached the gateway.

Recording layer	What it protects	When to use it
P3 field-side storage	The source side, before transport.	Use it when the field team needs a local copy or backup.
Callaba cloud recording	The received workflow side, after SRT reaches the cloud.	Use it when you need proof of what actually arrived at the gateway.

For critical workflows, the best setup can be parallel recording: keep a field-side copy when available and record the received SRT stream in Callaba.

Kiloview P3 playback workflow with Callaba

Playback can mean browser preview in Callaba, a web player for viewers, a review link for operators or a downstream output route. The P3 sends the field stream; Callaba decides how that stream becomes visible and useful after ingest.

A practical playback path usually looks like this:

Kiloview P3 sends the SRT stream to Callaba Gateway.
Callaba receives the stream and confirms preview, codec, audio and bitrate.
Callaba routes the received stream to a browser preview, web player, HLS output, recording path or another destination.
Operators test playback after the SRT connection is stable, not before.

For playback, use the player link or HLS URL generated by your own Callaba deployment. Do not hard-code a path until the output has been created in Callaba.

Use the generated Callaba player link or generated HLS playlist URL

Troubleshooting

Most P3 to Callaba SRT issues fall into a small number of buckets. Check them in this order.

Start with the source signal and SRT service. Then check network, bitrate and Callaba preview.

1. No connection in Callaba

Confirm Callaba is listening on the expected UDP port.
Confirm the P3 SRT service is enabled.
Check the pushing address in P3.
Check that the UDP port is open in the cloud firewall.
Check that the current field network allows outbound UDP.

2. Connected, but no picture

Confirm the HDMI, SDI or USB input has a valid video signal.
Confirm you are using the right main stream or sub stream. Some firmware versions may require enabling the SRT service separately for the selected stream.
Check codec, profile, resolution, frame rate and audio settings in Callaba.
Start with H.264 before testing H.265 in a more complex downstream workflow.

3. Stream drops or stutters

Increase SRT latency.
Lower bitrate and test again.
Check whether cellular links are actually stable enough. Use a network speed test or P3/KiloLink link statistics if available.
Watch packet loss and reconnect behavior in Callaba.
Use bonding if one uplink cannot support the stream reliably.

4. Recording or playback does not work after ingest

Confirm the SRT input is connected and visible in Callaba.
Check that the correct input is assigned to the recording, player or route.
Check codec and audio compatibility with the downstream path.
Use one clean route before adding several destinations.

Official references used for this guide

Use these if you need exact Kiloview model details, input limits, protocol support, firmware behavior or SRT stream settings before configuring a production device.

FAQ

Can Kiloview P3 send SRT to Callaba Gateway?

Yes. P3 supports SRT streaming. In a simple cloud ingest setup, Callaba Gateway listens for the incoming SRT stream and P3 pushes the stream to Callaba.

Should I use direct SRT or KiloLink bonding?

Use direct SRT when the uplink is stable enough. Use bonding when the field network is the main risk and you need to combine multiple cellular, Wi-Fi or Ethernet paths through KiloLink Server before distribution.

Can I monitor Kiloview P3 in Callaba multiview?

Yes. After Callaba receives the SRT stream, you can place the P3 feed on a browser-based multiview board with other live sources.

Can Callaba record a Kiloview P3 stream?

Yes. Callaba can record the received SRT stream in the cloud. This is useful when you need proof of what reached the gateway after field transport.

What bitrate should I use with P3?

Use a bitrate below your real uplink capacity. For the first mobile test, use 720p at 30 fps and leave extra headroom because link quality can change during the event.

Does this guide also apply to P3 Mini?

The SRT idea is similar, but the network module setup and maximum practical source profile can differ. Treat P3 Mini as a smaller mobile contribution workflow and check its exact data sheet before production.

Final practical rule

Make the first Kiloview P3 → Callaba SRT connection boring. One input, one main stream, one UDP port, one Callaba listener and a conservative bitrate. When that is stable, add bonding, multiview, recording, playback and destinations.

Last updated: May 14, 2026

Try Callaba Gateway with your Kiloview P3

Create an SRT listener in Callaba, send a P3 stream to the gateway, and monitor the feed before routing it to recording, restreaming, multiview, playback or player delivery.

See SRT server setup Open multiview demo