Kiloview P1/P2 SRT setup: field bonding encoder 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 P1 and P2 are portable field encoders built for mobile live streaming and bonding workflows.

The practical Callaba path has two options: send a direct SRT stream from P1/P2 to Callaba Gateway for a simple first test, or use KiloLink bonding first and then forward a clean stream into Callaba for browser multiview, cloud recording, playback, routing and delivery.

This guide is written for the search intent behind Kiloview P1 SRT, Kiloview P2 SRT, Kiloview P1/P2 bonding encoder, Kiloview P1/P2 multiview, Kiloview P1/P2 recorder, Kiloview P1/P2 playback, KiloLink Server and Callaba SRT Gateway.

Quick answer: how do I connect Kiloview P1 or P2 to Callaba Gateway?

For the first test, create an SRT server in Callaba Gateway in Listener mode, open the selected UDP port, then configure Kiloview P1 or P2 to send SRT to the Callaba public IP or DNS name. Use P1 for SDI sources and P2 for HDMI sources. If the event depends on unstable mobile links, use KiloLink Server for bonding first, then forward the resulting stream into Callaba.

P1 and P2 are field encoders. Callaba becomes the cloud ingest, monitoring, recording and routing layer after the stream arrives.

What this setup does

This workflow sends a live field stream from a Kiloview P1 or P2 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 P1 is the SDI field encoder path.
Kiloview P2 is the HDMI field encoder path.
Callaba Gateway listens on a public UDP port and accepts the incoming SRT stream.

P1/P2 sends the field source. Callaba turns that source into a monitored and routable cloud workflow.

Kiloview P1 vs P2 workflow notes

The setup logic is almost the same for P1 and P2. The main difference is the physical source connector. Use P1 when the field source is SDI. Use P2 when the field source is HDMI.

The Callaba side stays the same: receive SRT, monitor it, record it, play it back or route it.

Device	Best Callaba angle	Source path
Kiloview P1	SDI field camera or switcher output to Callaba SRT ingest.	SDI input
Kiloview P2	HDMI camera, laptop, small switcher or converter output to Callaba SRT ingest.	HDMI input

Direct SRT vs KiloLink bonding

P1/P2 can be used as a simple SRT field encoder, but the product family also exists for mobile bonding. These are related but different jobs.

Use direct SRT to validate Callaba quickly. Use KiloLink bonding when the field network needs link aggregation and server-side device control.

Bonding path note:

If you use KiloLink, the P1/P2 device registers with the bonding server first. The bonded output can then be forwarded into Callaba or into another production step. If you push a stream directly from the device web page instead of using the bonding platform streaming service, do not assume that every mobile link is being used for that push.

Bonding bitrate note: when KiloLink is used, watch the real incoming bitrate in Callaba, not only the target bitrate configured on the device. A bonding workflow can reduce bitrate when one of the links degrades. That behavior can be useful, but the operator should see it clearly in Callaba preview and statistics.

Recommended SRT mode: Callaba Listener, P1/P2 Caller or push

For the first Callaba test, use the simplest cloud ingest model:

Callaba Gateway: Listener
Kiloview P1/P2: SRT caller or push to the Callaba IP and port

This keeps the public listening port on the Callaba side. The field encoder only needs outbound UDP access to Callaba, which is usually easier than exposing a mobile encoder to inbound internet traffic.

Direct first, bonding second:

Validate one direct SRT path into Callaba first. When that works, decide whether the production needs KiloLink bonding. This keeps troubleshooting clean because you will know whether the issue is the encoder, the SRT route, the bonding server, or the downstream Callaba workflow.

A template SRT URL looks like this:

srt://YOUR_CALLABA_IP:10160?mode=caller&latency=400&streamid=kiloview-p1-main

A filled example for field testing can look like this:

srt://demo.callaba.io:10160?mode=caller&latency=400&streamid=kiloview-p1-main

Use the second example as a template. Replace host, port, stream ID and passphrase with your own Callaba values. For mobile field tests, start with more latency than you would use on a clean wired network.

Before you start

Prepare the SRT connection before changing production settings. P1/P2 is often used in unstable network conditions, so the first test should be intentionally conservative.

Before you start: confirm the exact P1/P2 firmware, whether you are using direct SRT or KiloLink bonding, and which network interfaces are active. On mobile networks, do not start with the highest resolution and bitrate.

Selected input Use P1 for SDI and P2 for HDMI. Confirm the input signal before testing SRT.

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

Resolution first test Start with 720p30 or 1080p30, not 1080p60. This gives more headroom for network changes.

Latency first test Start around 400 ms for mobile contribution. Reduce latency after the route is stable.

Bitrate Keep bitrate below the real uplink capacity. Leave extra headroom if using a single cellular link.

Audio Confirm embedded audio exists and that Callaba detects it after SRT ingest.

Step 1: create the SRT listener in Callaba

In Callaba, create a new incoming SRT server for the Kiloview P1/P2 feed. Callaba opens a UDP port and waits for the field encoder or forwarding server to connect.

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 10160.
Set latency, for example 400 ms as a starting point for mobile contribution.
Add a stream ID if your routing model uses it.
Add the same passphrase that you plan to use on P1/P2, if encryption is needed.
Open the UDP port in your cloud firewall or security group.

Step 2: configure Kiloview P1/P2 SRT output

In the Kiloview web interface, configure the main H.264 stream and send it to the Callaba listener. The exact menu names can differ by firmware, but the practical values are the same: destination address, destination UDP port, latency, stream ID if used, passphrase if used, bitrate and audio.

Field name note: in the P1/P2 web interface, the direct SRT target field can be named Push URL, Server Address, SRT Target or similar. In KiloLink Server, create the output or forwarding channel with SRT as the protocol and use Callaba as the forwarding target.

Confirm the SDI or HDMI input is locked and visible on P1/P2.
Choose direct SRT or KiloLink bonding path.
Use a conservative H.264 profile for the first test.
Set the SRT target to the Callaba public IP address or DNS name.
Enter the same 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 enable every output at once. Start with one SRT output to one Callaba listener. After that works, add KiloLink bonding, additional destinations, recording, multiview, playback or downstream routes.

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 and the same workflow path.

Match SRT transport settings first. Then verify the field network, bonding path, source, bitrate, audio and workflow outputs.

Bitrate note: if the network link bandwidth is not enough, the bonded streaming service can adaptively reduce output bitrate. This is useful in the field, but it also means you should watch the received bitrate and preview in Callaba, not only the device-side target bitrate.

Setting	Callaba Gateway	Kiloview P1/P2	Why it matters
Path	Direct SRT input or post-KiloLink stream	Direct stream or bonding service	The troubleshooting path depends on whether bonding is active.
Mode	Listener	SRT caller or push	One side waits, the other side connects.
Address	Public IP or DNS	Push URL, server address or target address	The encoder or bonding server must send to the reachable Callaba address.
UDP port	Open listener port	Same target port	A wrong or blocked port looks like no connection.
Bonding	Receives the clean direct or bonded output	KiloLink only if the output channel uses bonding	This determines whether you debug the device push or the bonding platform.
Resolution / FPS	Must match what P1/P2 sends	Start with 720p30 or 1080p30	Mobile networks are easier to validate with a conservative profile.
Bitrate	Ingest capacity and received bitrate	Below real uplink capacity	Too much bitrate causes drops before Callaba can help.
Codec	H.264 received by Callaba	H.264 profile selected on P1/P2	H.264 is the expected P1/P2 contribution path.
Audio	Detected audio format and channels	AAC or G.711 audio encoding	Audio must be present before recording, playback or monitoring is trusted.

Kiloview P1/P2 multiview workflow with Callaba

P1/P2 does not need to be your multiview system. It is the field contribution encoder. After Callaba receives the SRT stream, 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. You can also read more about browser multiview. Your real P1/P2 feed would appear as a live input in your own deployment.

Kiloview P1/P2 recorder workflow: field-side proof vs cloud recording

Field contribution and recording should not be treated as the same problem. P1/P2 protects the source side and field uplink path. Callaba adds a different layer: cloud-side recording after SRT ingest.

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

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

Kiloview P1/P2 playback workflow with Callaba

P1/P2 is the field encoder side of the workflow, not the local playback decoder. Playback happens after Callaba receives the stream. That playback can be browser preview, a generated player page, an HLS output, a recording review link or a downstream route to another system.

Typical generated playback links can look like this:

HLS playlist:
https://YOUR_CALLABA_DOMAIN/hls/kiloview-p1-main/playlist.m3u8

Player or embed page:
https://YOUR_CALLABA_DOMAIN/embed/kiloview-p1-main

Use these as URL shape examples only. In production, use the exact player link, HLS playlist URL or output route generated by your Callaba deployment.

Where the links come from: Callaba generates these links after you create a web player or HLS packaging path for the incoming P1/P2 stream. Depending on your configuration, player or HLS links may include temporary tokens or authorization parameters, for example ?token=.... Use the links generated by your own Callaba installation and do not copy the example URL literally.

Troubleshooting

Most P1/P2 to Callaba SRT issues come from input signal, direct-vs-bonding confusion, cellular link quality, bitrate, SRT target, codec profile, audio source or route assignment. Check them in this order.

Start with input and path choice. Then check field network, bitrate, media settings and Callaba preview.

1. No connection in Callaba

Confirm Callaba is listening on the expected UDP port.
Confirm whether the stream is direct from P1/P2 or forwarded after KiloLink bonding.
Check the target address and target port in the Kiloview or KiloLink settings.
Check stream ID and passphrase if either one is enabled.
Check that the field network allows outbound UDP to Callaba.

2. Bonding is active, but Callaba does not receive the expected stream

Confirm the P1/P2 device is registered to the correct KiloLink Server.
Confirm the streaming service is created on the bonding platform if you expect bonded traffic.
Check whether a direct device-side push is bypassing the bonding service.
Check KiloLink device status, link status and output bitrate.
Confirm that the KiloLink output or forwarding channel is set to SRT, not only RTMP or HLS.

3. Connected, but no picture

Confirm the SDI or HDMI input has a valid video signal.
Check codec, profile, resolution, frame rate and audio settings in Callaba.
Start with H.264 Main or Baseline before testing a more aggressive profile.
Confirm you are using the main stream or the intended output from KiloLink.

4. Stream drops or stutters

Lower bitrate and test again.
Start with 720p30 or 1080p30 before testing 1080p60.
Check active cellular, Wi-Fi and Ethernet link status.
Increase SRT latency for mobile contribution.
Watch packet loss, reconnect behavior and received bitrate in Callaba.

5. No audio after ingest

Verify that the selected SDI or HDMI source actually carries audio.
Check the audio encoding settings on P1/P2.
Check Callaba stream metadata and browser preview before troubleshooting the player or recording path.

6. 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 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, protocol support, KiloLink behavior, network setup or SRT mode notes before configuring a production device.

FAQ

Can Kiloview P1 or P2 send SRT to Callaba Gateway?

Yes. P1/P2 supports SRT streaming. In a simple cloud ingest setup, Callaba Gateway listens for the incoming SRT stream and the Kiloview encoder or forwarding server connects to Callaba.

What is the difference between Kiloview P1 and P2?

Use P1 for SDI sources and P2 for HDMI sources. The SRT setup thinking is similar: create a Callaba listener and send the encoder or bonded output to that IP and port.

Should I use direct SRT or KiloLink bonding?

Use direct SRT for the first Callaba test and for simple stable uplinks. Use KiloLink bonding when the field network is unstable and you need multiple cellular, Wi-Fi or Ethernet links to be managed before the stream reaches Callaba.

Can I monitor Kiloview P1/P2 in Callaba multiview?

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

Can Callaba record a Kiloview P1/P2 stream?

Yes. Callaba can record the received SRT stream in the cloud. This records what reached the gateway, which is different from field-side or source-side recording.

Should I test 1080p60 first?

No. For mobile field workflows, start with 720p30 or 1080p30 and a conservative bitrate. Move to 1080p60 only after connection, preview, audio, recording and received bitrate are stable.

Does Callaba replace KiloLink?

No. KiloLink is the bonding and device-management layer for Kiloview field encoders. Callaba is the cloud ingest and workflow layer after the stream is received. In some workflows you can use direct SRT to Callaba; in others you use KiloLink first and then forward the clean stream to Callaba. For KiloLink setup, use the official Kiloview documentation linked in the References section.

Final practical rule

Make the first Kiloview P1/P2 → Callaba SRT connection boring. One selected input, one encoded output, one direct SRT path, one UDP port and one Callaba listener. When that is stable, add KiloLink bonding, recording, multiview, playback, extra destinations or downstream routes.

Last updated: May 16, 2026

Try Callaba Gateway with your Kiloview P1 or P2

Create an SRT listener in Callaba, send a P1 or P2 field 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 Learn browser multiview