Kiloview P1/P2 SRT setup: field bonding encoder to Callaba Gateway
More live video workflow notes and product updates.
Kiloview P1/P2 contribution workflow
Choose the transport path before the camera leaves the venue
Kiloview P1 and P2 are compact field encoders built around the same contribution job. The P1 accepts an SDI source; the P2 accepts HDMI. Both encode H.264 video up to 1080p60 and can send SRT in Caller, Listener, or Rendezvous mode. The operational decision is not simply which address to enter. It is whether one network is dependable enough for direct SRT, or whether several available connections should first be combined by Kiloview's current KiloLink Server Pro workflow.
The short answer
For a fixed position with one proven uplink, use direct SRT. A straightforward baseline is P1/P2 as Caller and Callaba as Listener. It has fewer dependencies and makes transport faults easier to isolate.
For a moving camera or an unpredictable field location, use the KiloLink path. The encoder can make up to five network connections available to KiloLink Server Pro. That Kiloview system receives and reconstructs the bonded contribution, then hands a normal output toward Callaba. Callaba monitors, records, and routes the resulting feed; it does not perform the Kiloview bonding operation.
Direct SRT and KiloLink bonding solve different network problems. The lower path includes an extra system because the proprietary bond must be terminated before Callaba receives the reconstructed program. Motion is disabled when reduced motion is preferred.
Pick the encoder by connector, not by marketing name
| Decision | Use this option | Confirm before the event |
|---|---|---|
| Kiloview P1 | The source provides SDI: a production switcher, professional camera, or other SDI program output. | SDI lock, expected resolution and frame rate, embedded audio, and a stable H.264 encode. |
| Kiloview P2 | The source provides HDMI: a compact camera, presentation switcher, laptop, or other HDMI output. | HDMI handshake, stable video format, correct audio input, and protection against an accidental resolution change. |
| Direct SRT | One venue or field connection has enough sustained upstream capacity and has passed a realistic rehearsal. | The active interface, outbound UDP policy, Callaba address and port, SRT role, and reconnection behavior. |
| KiloLink Server Pro | The production needs Kiloview's multi-network bonding across up to five available connections. | Every intended link, KiloLink authorization and receiving service, reconstructed output, and the separate handoff to Callaba. |
| Local microSD/NAS recording | A field copy is useful alongside the live transmission. | Writable media or reachable NAS, available capacity, expected file duration, and successful playback after the test. |
P1 and P2 share the contribution concept, but their inputs are not interchangeable. Adapters can introduce format negotiation and power dependencies that are harder to diagnose under event pressure. Use the model that matches the source's native output wherever possible.
Direct SRT: establish the simplest end-to-end proof
Caller, Listener, and Rendezvous describe how the SRT peers establish a session. They do not change which device encodes the camera. For most internet-facing deployments, making P1/P2 the Caller and Callaba the Listener provides a clean operational baseline: the field encoder initiates outbound UDP toward a known Callaba endpoint.
Prove the source locally
Connect SDI to the P1 or HDMI to the P2. Confirm stable picture, the intended frame rate, and the correct audio before configuring the network output. Start with H.264 at a rate the tested uplink can sustain; the encoder supports video up to 1080p60, but capability is not the same as available field bandwidth.
Create the receiving endpoint
Create and start one Callaba SRT Server in Listener mode. Record its reachable hostname or public IP and UDP port. Open that same UDP port in the relevant cloud security group, host firewall, and upstream policy.
Configure one direct SRT output
On the Kiloview encoder, select SRT Caller and enter the Callaba address and port. If the chosen SRT configuration uses additional access or encryption values, copy them exactly between both ends and keep secrets out of screenshots and shared runbooks.
Identify the network actually in use
Do not infer the active path from the number of attached modems or cables. Check the encoder's network status and verify which connection is carrying the direct session. Several connected networks do not automatically turn an ordinary SRT output into a bonded stream.
Accept transport and decoded media
In Callaba, confirm that the SRT session remains connected and carries a plausible, sustained bitrate. Then place the source in Multiview or make a short recording. Watch motion, listen to audio, and inspect the result long enough to reveal intermittent loss.
KiloLink Server Pro: terminate the bond before the Callaba handoff
Kiloview documents support for up to five network connections in its bonding workflow. The purpose is to make the field contribution less dependent on any one path. The receiving component is KiloLink Server Pro, which Kiloview now recommends in place of the older KiloLink Bonding product that is no longer being updated.
Prepare and authorize KiloLink Server Pro using Kiloview's current instructions, bind the P1/P2 to that service, and confirm the expected links are present. Then configure the reconstructed output toward Callaba. Treat the workflow as two separately observable boundaries:
- P1/P2 → KiloLink Server Pro: constituent networks, bond health, total usable capacity, and reconstruction.
- KiloLink Server Pro → Callaba: output format, destination address and port, transport continuity, decoded picture, and audio.
A healthy Callaba session does not prove that all field links are participating in the bond. A healthy KiloLink dashboard does not prove that the reconstructed program reached the production workflow. Observe both layers during rehearsal and during a controlled link-loss test.
Use local recording as evidence, not as an invisible safety net
P1/P2 support local recording to microSD or NAS. That copy can protect against a damaged uplink or provide a clean source for later editing, but it has its own failure modes: full media, an unreachable share, unexpected file segmentation, or missing audio. Format and mount the target before the event, calculate capacity from the actual encoded rate and duration, and play a test file from the beginning and near the end.
Local recording and a Callaba recording serve different purposes. The local file shows what the encoder produced before the network. A Callaba-side file shows what survived the contribution path. When diagnosing a fault, comparing those two points is far more useful than simply knowing that both record buttons were enabled.
Acceptance test: make the expected failure happen on purpose
- Input: stable SDI on P1 or HDMI on P2, with representative motion and the correct audio source.
- Encode: H.264 profile, resolution, frame rate, and bitrate recorded in the event runbook.
- Transport: the expected direct interface or KiloLink bonded links are visible and remain stable.
- Callaba: continuous session uptime, plausible bitrate, decoded picture, audio, and a short playable recording.
- Reconnect: stop and restart the encoder output, then verify that the session and downstream uses recover without undocumented operator actions.
- Failure drill: for direct SRT, interrupt the selected uplink; for KiloLink, remove one constituent connection while watching both KiloLink and Callaba.
- Local copy: remove and play the microSD recording, or retrieve and play the NAS file, using the process the production team will actually follow.
Record the observed interruption and recovery time. “Connected” is not the pass condition; usable video and audio at the receiving end are.
Troubleshoot the boundary that failed
No session appears in Callaba
Compare Caller/Listener roles, hostname, UDP port, and any matching security values. Check outbound UDP at the venue and inbound UDP at Callaba. A successful web login does not prove that the media port is reachable.
The session connects but the picture breaks up
Measure usable upstream capacity, not the advertised access speed. Watch transport behavior while representative motion is present. Reduce the encoded bitrate or increase the recovery budget only after confirming that the selected network is the one under test.
Video is present but audio is wrong
Return to the SDI/HDMI input and encoder audio selection. Verify audio before transmission, then again after decode. A local meter cannot prove that the required channels reached Callaba.
Bonding is healthy but Callaba receives nothing
First prove that KiloLink Server Pro has reconstructed an output. Then inspect the separate handoff toward Callaba. Do not troubleshoot carrier participation from the Callaba listener screen.
Removing one connection interrupts the feed
Confirm that the removed connection was participating in the bond and that the remaining links have enough aggregate capacity for the encode. Bonding cannot compensate when the surviving capacity is below the transmitted rate.
The local file is missing or incomplete
Check microSD write status or NAS reachability, available capacity, file segmentation, and clean stop behavior. Repeat the test and play the file outside the encoder before treating it as a recovery asset.
Official Kiloview references
- Kiloview P1/P2 product information — SDI/HDMI model distinction, contribution role, network options, and supported protocols.
- Kiloview P1/P2 parameters — H.264 formats, SRT modes, audio, and local recording capabilities.
- Kiloview P-series encoder datasheet — device inputs, direct SRT Caller/Listener/Rendezvous, and bonding specifications.
- Kiloview KiloLink Server Pro support documentation — current receiving-server path and the notice that the former KiloLink Bonding product is no longer updated.
Confirm menu labels and available controls against the installed P1/P2 firmware and Kiloview's current documentation before the final rehearsal.
Make the receiving end observable
Bring the direct SRT session or the reconstructed KiloLink output into Callaba, then confirm transport health, decoded media, recording, and routing from the same operator view.
Configure a Callaba SRT receiver