Kiloview P3 Mini SRT setup: send SRT to Callaba Gateway
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 Mini SRT setup is straightforward: put the P3 Mini at the venue, configure an SRT output, and send it to a Callaba SRT Listener in the cloud. Use this setup when P3 Mini is at the venue and Callaba is the cloud SRT receiver for monitoring, recording, routing, multiview, or restreaming. The main path is direct SRT; KiloLink Server Pro only becomes part of the design when you need the P3 Mini multi-link bonding layer.
Quick answer
To use Kiloview P3 Mini with SRT, set P3 Mini as the SRT Caller and send the stream to a cloud SRT Listener. In this guide, Callaba works as the SRT gateway, receiver, monitor, recorder, and routing layer.
The Kiloview P3 Mini sends one SRT contribution feed into Callaba. After ingest, Callaba can preview, record, route, restream, and feed multiview in parallel; these are downstream options, not mandatory sequential steps.
- Kiloview P3 MiniSRT Caller at venue
- Callaba GatewaySRT Listener in cloud
- Preview
- Record
- Route
- Restream
- Multiview
What this setup does
The P3 Mini is a compact field contribution encoder. Kiloview lists 3G-SDI, HDMI 1.4b, and USB video inputs up to 1080p60, plus embedded audio and a 3.5 mm line input. It can encode H.264, H.265, and MJPEG, with AAC, G.711, and firmware-added OPUS audio support.
For a P3 Mini SRT to cloud workflow, the encoder sends one contribution stream to Callaba. Callaba receives it, shows live status, and can use the same source for preview, recording, routing, multiview, playback, or restreaming without asking the camera operator to create separate device outputs for each downstream use.
What this model can and cannot do in this workflow
- Confirmed direct protocols: SRT, RTMP, RTMPS, RTSP, HLS, WHIP, TS over UDP, and NDI HX are listed for P3 Mini in Kiloview materials.
- SRT fields are documented: the P3/P3 Mini API includes connectionMode, address, listenerPort, latency, payloadSize, encryption, passphrase, and srt_stream_id.
- SRT roles: Listener, Caller, and Rendezvous are documented. For public internet contribution, use P3 Mini as Caller and Callaba as Listener unless you have a reason to reverse the direction.
- Encryption: AES-128, AES-192, and AES-256 options are documented. Passphrase and Stream ID matching must be exact.
- NDI: NDI HX2 is confirmed. Public Kiloview pages are inconsistent about NDI HX3 readiness, so do not plan an HX3 workflow unless the installed firmware and visible settings expose it.
- Bonding: direct SRT to Callaba does not require KiloLink Server Pro. Use KiloLink Server Pro when you need the P3 Mini cellular/Wi-Fi/Ethernet bonding layer.
- Not a decoder: I did not find a confirmed SDI or HDMI program output for using P3 Mini as a return-feed decoder.
- Sibling note: Kiloview documentation sometimes covers P3 and P3 Mini together. This guide is for P3 Mini; do not copy physical I/O or bonding assumptions from the larger P3 without checking that exact unit.
Recommended workflow
The recommended P3 Mini SRT gateway design is: P3 Mini as SRT Caller, Callaba as SRT Listener. This avoids inbound connections at the venue and usually works better with NAT, cellular routers, and production firewalls.
Search terms such as P3 Mini SRT listener, P3 Mini SRT receiver, or Kiloview P3 Mini SRT server can be confusing. The P3 Mini can document listener mode, but in this cloud contribution workflow it is not the receiver. Callaba is the receiver. If you reverse the roles, the venue side must accept inbound UDP, which may require a public IP, port forwarding, and firewall rules.
When not to use this setup
If all equipment is on the same LAN and your production tools already accept NDI HX2, local NDI may be simpler than cloud ingest. If the only target is a public platform and you do not need monitoring, recording, routing, or low-latency contribution, RTMP or RTMPS from P3 Mini may be enough. If the job depends on multi-link cellular bonding, use KiloLink Server Pro in the middle and then hand off an output toward Callaba.
Use RTSP or NDI bridging only when the production design needs a bridge. For direct internet contribution, SRT is the cleaner first choice for this model.
Before you start
- Update or confirm P3 Mini firmware, and check that the SRT streaming settings are visible on the unit.
- Choose H.264 for the first test. H.265 is supported by the encoder, but downstream destinations and players may not accept it.
- Open the Callaba UDP port in the cloud firewall and any upstream security group.
- Decide whether you will use Stream ID and encryption before the operator starts copying values.
- If handshake failures are hard to diagnose, confirm compatible SRT major versions from device firmware notes or vendor support information and from the Callaba server build or support information.
- For best stability, avoid running the bonding stream and local stream services at the same time unless you have tested that exact production load.
Create the Callaba ingest
In Callaba, create an SRT server and set the UDP listening port. Keep the server in Listener mode for this workflow. If the stream will be routed by Stream ID, create or copy the exact Stream ID value that the P3 Mini must send.
Success looks like this: the Callaba SRT server is listening, the cloud firewall allows the selected UDP port, and the server page is ready to show incoming bitrate, uptime, packet loss, RTT, retransmits, preview, and audio activity once the P3 Mini connects.
Configure the P3 Mini
On the P3 Mini, open the streaming output settings or use the documented API fields for the SRT stream. Set connectionMode to Caller. Enter the Callaba public IP address or DNS name in the address field, and enter the Callaba UDP port in listenerPort.
If you use encryption, match the AES option and passphrase on both sides. If you use Stream ID, paste srt_stream_id exactly. Stream ID and passphrase are case-sensitive and whitespace-sensitive; a trailing space, copied newline, or changed capitalization can stop the SRT handshake.
Settings table
| Where | What to do / field to fill | First-test value | Why / check |
|---|---|---|---|
| Callaba | Create SRT server and choose UDP port | Example: 10080/UDP | Server must be listening before P3 Mini calls it. |
| P3 Mini SRT settings | connectionMode | Caller | Best default for P3 Mini SRT to cloud. |
| P3 Mini SRT settings | address | Callaba public IP or DNS | Must resolve from the venue network. |
| P3 Mini SRT settings | listenerPort | Callaba UDP port | Must match the Callaba SRT server port. |
| P3 Mini SRT settings | latency | 250-500 ms | Good first internet test; lower only after loss and RTT are stable. |
| P3 Mini SRT settings | encryption and passphrase | Off for first lab test, then AES with exact passphrase | Mismatch prevents connection or stream acceptance. |
| P3 Mini SRT settings | srt_stream_id | Exact Callaba Stream ID, if used | Whitespace and capitalization must match. |
| P3 Mini encoder settings | Video codec | H.264 | Safest first test; try H.265 only when every receiver supports it. |
For first bitrate tests, I usually start around 2.5-4 Mb/s for 720p, 4-6 Mb/s for 1080p30, and 6-8 Mb/s for 1080p60, then adjust to the real uplink and production quality target.
Monitoring
After the P3 Mini starts streaming, watch Callaba for incoming bitrate, connection uptime, RTT, packet loss, retransmits, preview, and audio meters. On the P3 Mini side, confirm that the selected SDI, HDMI, or USB input is active and that the audio source matches the production feed.
If the stream is stable in Callaba but a downstream platform fails, separate ingest from distribution. First prove that Callaba is receiving a clean feed. Then check the restream target, codec support, keyframe interval, and output credentials.
Failover and local ingest options
For production events, plan what happens if the main encoder, venue uplink, or primary contribution path fails. Callaba can be part of that continuity plan without changing the basic Kiloview P3 Mini ingest workflow.
Recording and playback
Once the SRT ingest is stable, recording and playback are downstream choices in Callaba, not extra work for the P3 Mini operator. You can record the received contribution feed, generate playback access for review, or route the same source to other live outputs while the original SRT contribution continues.
Troubleshooting
| Symptom | Check in Callaba | Check on P3 Mini | Likely fix |
|---|---|---|---|
| No connection | SRT server listening, UDP port open, no incoming packets | connectionMode Caller, address, listenerPort | Fix IP/DNS, UDP firewall, or caller/listener direction. |
| Connects then drops | RTT, packet loss, retransmits, uptime resets | Cellular/Wi-Fi/Ethernet link quality and bitrate | Raise latency, reduce bitrate, or use bonding through KiloLink Server Pro. |
| Handshake fails with encryption | Passphrase, AES mode, Stream ID route | encryption, passphrase, srt_stream_id | Re-type values; remove copied spaces or newlines. |
| Video but no audio | Audio meters and codec details | Embedded audio or 3.5 mm line input selection | Select the correct audio source and test AAC first. |
| Receiver or player rejects the feed | Codec shown on ingest and output logs | H.264/H.265 selection | Use H.264 for widest compatibility. |
Official references
Useful references for this setup:
Vendor references
- Kiloview P3 Mini product page
- P3 Mini Wireless Bonding Encoder User Manual
- P3/P3 Mini WEB API Manual
- P3 Mini firmware download page
Protocol references
Callaba resources
FAQ
Can Kiloview P3 Mini send SRT directly to Callaba?
Yes. Official P3 Mini materials and the P3/P3 Mini API document SRT streaming and SRT fields. Use P3 Mini as Caller and Callaba as Listener for the normal cloud receiver workflow.
Should P3 Mini be SRT Caller or SRT Listener?
Use Caller for most public internet jobs. Listener mode is documented, but it makes the venue side accept inbound UDP, so it needs a tested public IP, forwarding, and firewall plan.
Does P3 Mini support SRT Stream ID and passphrase?
Yes. The documented SRT object includes srt_stream_id, encryption, and passphrase. Match the values exactly on both sides.
Can I use RTMP or RTMPS instead?
Yes. P3 Mini lists RTMP and RTMPS. Use them when the destination is a platform-style ingest or when SRT is not the chosen workflow, but expect less contribution-oriented feedback than SRT.
Does P3 Mini support NDI?
NDI HX2 is confirmed. Public Kiloview pages are inconsistent about HX3, so check the installed firmware and the visible NDI settings before planning HX3.
When do I need KiloLink Server Pro?
Use it when you need the P3 Mini bonding layer across cellular, Wi-Fi, and Ethernet links. For a single direct SRT output to Callaba, it is not required.
Next steps
Build the direct SRT path first, confirm the preview and audio in Callaba, then add recording, routing, multiview, or restreaming as separate downstream tasks. Before the event, confirm firmware, SRT caller/listener direction, Stream ID, passphrase, codec, and the cloud UDP firewall.
Try Callaba Gateway with Kiloview P3 Mini SRT
Create an SRT server in Callaba, send the device feed to the gateway, and check the received stream. After ingest is stable, use Callaba outputs for preview, recording, restreaming, multiview, playback, routing, or API workflows as parallel downstream options.