The Kiloview P3 Mini can reach Callaba in two genuinely different ways. On a stable venue connection, it can call a Callaba SRT listener directly. In a mobile or variable-network job, its cellular, Wi-Fi and Ethernet links can first be combined by KiloLink, with an SRT handoff to Callaba after the bonding stage. Choosing that path before entering any addresses prevents most setup mistakes.
Quick answer
Use direct SRT when one Ethernet, Wi-Fi or 4G connection is dependable enough for the production. Configure the P3 Mini as SRT Caller and Callaba as SRT Listener.
Use the bonded path when the encoder will move, cellular conditions vary, or a single link is not trustworthy. The P3 Mini sends its bonded transport to KiloLink Server Pro or KiloLink Station first. That system terminates the bonded session and then passes the program toward Callaba over SRT. Callaba does not terminate the proprietary KiloLink bond directly.
Local streaming · SRT Caller
KiloLink bonding
Choose the transport before you configure it
Direct SRT over one selected network
This is the right first build for a studio, venue or fixed field position with a stable uplink. It has fewer moving parts and avoids the extra buffer introduced by bonding.
The important detail is that local streaming uses one network interface. With multiple interfaces connected, the P3 Mini normally prefers wired Ethernet, then Wi-Fi, then cellular. That is failover by priority, not bandwidth bonding.
KiloLink bonding before Callaba
Use this for roaming cameras, outdoor sport, news gathering and event locations where any single uplink may fade. The P3 Mini can make 3×4G, Wi-Fi and Gigabit Ethernet available to its KiloLink bonding layer.
KiloLink Server Pro or Station is part of this architecture. It combines and reconstructs the transport before an SRT output is handed to Callaba. Plan for slightly more latency than the direct path.
What the P3 Mini brings to this workflow
P3 Mini is a portable encoder rather than a return-feed decoder. It accepts 3G-SDI, HDMI and USB video up to 1080p60. Its documented video codecs include H.264, H.265 and MJPEG; audio options include AAC and G.711, with Opus present in current firmware documentation. For the first interoperability test, H.264 video with AAC audio is the least surprising choice.
For transport, the device lists SRT alongside RTMP/RTMPS, RTSP, HLS, TS over UDP, WHIP and NDI HX. This guide stays deliberately narrow: it uses SRT for the contribution handoff and lets Callaba turn the received source into monitored, recorded or routed outputs.
Before an event, check the P3 Mini firmware page and confirm that the names and fields visible on the actual unit match the workflow below. Kiloview continues to update the product, so a screenshot from an older firmware build should not be treated as the configuration contract.
Workflow A: send direct SRT from P3 Mini to Callaba
Create the receiver in Callaba
Create an SRT Server in Listener mode. Choose a UDP port, then allow that same UDP port in the cloud security group or firewall. Copy the public hostname or IP, port, and any Stream ID or passphrase you decide to use.
Start with a compatible encode
Connect the camera over SDI, HDMI or USB and confirm picture and audio locally. Select H.264 and AAC for the first test. Once the complete path is stable, change codec or bitrate only when the downstream destination requires it.
Add an SRT local-stream output
In the P3 Mini streaming settings, create an SRT output and select Caller. Enter the Callaba public address and listener port. If encryption or Stream ID is enabled in Callaba, enter exactly the same values on the encoder; capitalization and copied whitespace matter.
Know which uplink is carrying the stream
Local streaming automatically prefers Ethernet over Wi-Fi, and Wi-Fi over 4G. Check the active uplink in the device Network Status or the LCD bonding view. To force a different interface, disable or disconnect the higher-priority interfaces, leaving only the intended network enabled.
Start the stream and verify transport, not just picture
Wait for the P3 Mini session to appear in Callaba. Confirm sustained bitrate, audio activity and an increasing session uptime. Then inspect RTT, loss and retransmission behavior before adding Multiview, recording or downstream routes.
Workflow B: bond the field links, then hand SRT to Callaba
The bonded design solves a different problem. Instead of choosing one active interface, the P3 Mini sends through its KiloLink bonding service across the links you make available. KiloLink Server Pro or KiloLink Station receives that proprietary bonded transport and reconstructs the program.
Prepare the KiloLink receiver
Deploy or select KiloLink Server Pro or Station according to Kiloview's instructions. Confirm its public reachability, bonding port and device authorization before involving Callaba.
Register and test the P3 Mini bond
Bind the encoder to KiloLink and verify that the expected 4G, Wi-Fi and Ethernet links are online. Remove a weak link rather than assuming that every available modem improves the session.
Create the SRT handoff after reconstruction
Configure the KiloLink receiving system to send the reconstructed program as SRT toward a Callaba Listener. This is the protocol boundary: KiloLink handles bonding; Callaba receives the resulting SRT contribution.
Validate the end-to-end path
Check both layers. KiloLink should show healthy constituent links and a stable reconstructed output. Callaba should show a continuous SRT session with expected bitrate, RTT and audio. A green status on only one layer is not an end-to-end test.
Run a controlled link-loss test
Remove one field link while watching the reconstructed program and Callaba's transport data. The purpose is not merely to keep a status indicator online; it is to confirm that the received video and audio remain usable under the failure you expect in production.
First-test settings for the direct SRT path
These values are a conservative starting point, not a universal preset. After a clean test, tune latency and bitrate against measured network behavior.
A 125 ms latency is useful for a controlled first connection, but it is not a promise for cellular contribution. If round-trip time or jitter approaches the configured latency budget, increase latency before blaming the codec. Likewise, overhead creates room for retransmission; it does not create uplink capacity that is not there.
What success looks like in Callaba
Do not stop at “the preview opened.” A production-ready P3 Mini session should pass four checks:
- Transport: the SRT session remains connected and uptime continues to rise.
- Media: bitrate is steady enough for the chosen encode, with both picture and audio present.
- Network: RTT, packet loss and retransmissions stay within a range that the configured SRT latency can absorb.
- Operations: the same received source can be placed in Multiview, recorded, or routed without asking the field encoder to publish a separate copy for each task.
- Access: the intended publisher connects, and any Stream ID or passphrase policy rejects mismatched attempts.
- Recovery: the team knows whether continuity comes from KiloLink bonding, P3 Mini local-network priority, or a separate Callaba failover route. These are not interchangeable.
Once the transport is stable, open the live Multiview and watch the source as an operator would during the event. Add recording or routing one operation at a time so that a downstream mistake cannot be confused with an ingest failure.
Troubleshoot the path you actually built
Direct SRT never connects
Confirm Caller on P3 Mini and Listener in Callaba, then compare hostname, UDP port, Stream ID, AES selection and passphrase character for character. Check the cloud firewall for UDP, not TCP.
The wrong network carries local streaming
The device prefers Ethernet, then Wi-Fi, then cellular. Inspect Network Status. Disable or disconnect higher-priority interfaces if the job must use a specific modem or Wi-Fi uplink.
The session connects, then breaks up
Compare P3 Mini uplink capacity with the encoded bitrate. In Callaba, watch RTT, loss and retransmissions. Reduce bitrate or increase SRT latency. If one field link is inherently unreliable, rebuild the job as a KiloLink bonded workflow rather than pretending local streaming is bonded.
KiloLink is online but Callaba has no feed
Treat this as two boundaries. First verify that KiloLink has reconstructed and can output the program. Then verify the SRT Caller/Listener pair between the KiloLink side and Callaba. Do not troubleshoot cellular bonding from the Callaba port screen.
Video arrives without audio
Confirm the P3 Mini audio source: embedded SDI/HDMI/USB audio or the 3.5 mm input. Test AAC first and look for audio activity at both the encoder and Callaba.
H.265 ingests but a destination fails
The P3 Mini supports H.265, but every player or restream destination may not. Return to H.264 for the interoperability baseline, then introduce H.265 only where the complete downstream path supports it.
Event-day checklist
- Record the installed P3 Mini firmware version and export or screenshot the working configuration.
- Label the chosen path as direct SRT or KiloLink bonded in the runbook.
- Confirm camera input, audio source, H.264/AAC baseline and expected bitrate.
- Confirm the active local network, or all intended bonding links, before leaving the venue setup window.
- Test the Callaba UDP port from the real event network; a studio test does not prove the venue firewall.
- Run at least one failure drill: remove the selected local uplink, a bonded link, or the primary route—whichever reflects the design.
- Verify Multiview and a short recording, including audio playback, before the production starts.
Kiloview P3 Mini and Callaba FAQ
Can the P3 Mini send SRT straight to Callaba?
Yes. Use a local-stream SRT output with P3 Mini as Caller and a Callaba SRT Server as Listener. That direct path uses one selected network interface.
Does connecting Ethernet, Wi-Fi and three 4G modems automatically bond them for direct SRT?
No. Local streaming chooses one interface by priority: Ethernet, then Wi-Fi, then cellular. Multi-link bonding is a KiloLink workflow and needs KiloLink Server Pro or Station to terminate the bond.
Can Callaba replace KiloLink Server Pro for the P3 Mini bonding protocol?
No. Callaba receives the SRT handoff after KiloLink reconstructs the bonded transport. It does not claim to terminate Kiloview's proprietary bonding session.
Should I start with H.264 or H.265?
Start with H.264 and AAC because that combination is easier to validate across players and destinations. Move to H.265 only after confirming the entire downstream path supports it.
Is 125 ms always enough for SRT?
No. It is a useful initial value on a controlled link. Real latency must account for measured RTT and jitter; variable cellular paths often need a larger buffer.
Can I run local streaming and bonding at the same time?
The device may expose both services, but Kiloview does not recommend using both together as the default. Test the exact firmware and workload before relying on simultaneous operation.
Device references
Bring the P3 Mini feed into one operating view
Start with one SRT session, confirm transport and audio, then use the same source for Multiview, recording and routing. Callaba can run in the cloud or on your own Linux infrastructure; the live demo shows the operator view before you deploy.
