Kiloview RE-2 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
Use this Kiloview RE-2 SRT setup when the RE-2 is at the venue and Callaba is the cloud SRT receiver for monitoring, recording, routing, multiview, or restreaming. The RE-2 is an HDMI encoding card for a Kiloview Cradle chassis, not a standalone media gateway. In practice, create an SRT listener in Callaba, set the RE-2 SRT output to Caller, and match the port, latency, Stream ID, passphrase, and encryption settings before the show.
Quick answer
To use Kiloview RE-2 with SRT, set RE-2 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. Before production, confirm that your installed RE-2 firmware exposes the SRT settings.
The Kiloview RE-2 sends one SRT contribution feed into Callaba. After ingest, preview, recording, routing, multiview, and restreaming are parallel downstream uses, not mandatory sequential steps.
- Kiloview RE-2HDMI encoder, SRT Caller
- Callaba GatewayCloud SRT Listener
- Preview
- Record
- Route
- Restream
- Multiview
What this setup does
This workflow turns the RE-2 HDMI input into a contribution stream that Callaba receives over SRT. Callaba is the cloud-side SRT server: it accepts the stream, shows transport statistics, gives operators a preview, and can record or route the same source to downstream destinations.
The important role decision is simple: keep the RE-2 at the venue as the outbound SRT Caller. That avoids asking the venue network to accept an inbound internet connection. Use RE-2 Listener mode only if your firmware exposes it and the venue has a tested public IP, UDP forwarding, and firewall rules.
What this model can and cannot do in this workflow
- Confirmed role: RE-2 is an encoding card for Kiloview Cradle systems, with HDMI input, HDMI loop-through, 3.5 mm analog audio input, and 100M Ethernet.
- Confirmed protocols: public Kiloview material lists SRT, RTMP, RTMPS, HLS, TS over UDP, RTP, RTSP, and ONVIF for RE-2.
- SRT details: Kiloview SRT documentation covers Caller, Listener, Rendezvous, encryption, key/passphrase, payload size, latency, and Stream ID behavior. Exact RE-2 UI labels may vary by firmware.
- Codec boundary: RE-2 is documented for H.264/AVC and Motion-JPEG video, with AAC and G.711 audio. I would not plan HEVC/H.265 or 4K/UHD from this model unless your exact unit documentation says otherwise.
- NDI boundary: do not plan Kiloview RE-2 as a native NDI source. Kiloview distinguishes RE-2 from REN-2; REN-2 is the NDI variant in this family.
- Firmware caveat: an exact RE-2 firmware note lists an SRT packet-loss fix. Update and test the installed firmware before relying on SRT in production.
Recommended workflow
For remote contribution, use direct SRT first. Create the Callaba SRT server as Listener, open or map the UDP port on the cloud side, then configure the RE-2 SRT service as Caller. Match Stream ID, passphrase, encryption level, and latency exactly.
If the SRT menu is missing on an older unit, update firmware first. If you cannot change firmware before the event, use the confirmed RTMPS or RTMP output to Callaba or another ingest point. RTSP is better kept as a local pull or bridge path because it usually needs reachable device-side networking.
When not to use this setup
- If the encoder and switcher are in the same rack, the RE-2 HDMI loop-through or local baseband routing may be simpler than cloud ingest.
- If the only destination is a public platform and you do not need cloud monitoring, recording, or routing, RTMP or RTMPS may be enough. Test RTMPS with the destination before the event.
- If the production requires NDI from the card, RE-2 is the wrong model. Use a confirmed NDI model such as the REN-2 or a separate bridge.
- If the installed firmware does not expose SRT and cannot be updated, use RTMP/RTMPS first; use RTSP through a bridge only when that network path is deliberate and tested.
Before you start
- Confirm the RE-2 is installed in a supported Cradle chassis slot and reachable through its web management interface.
- Check the installed firmware and confirm that SRT settings are visible. Public RE-2 material does not publish the SRT library version, so hard handshake problems may require firmware release notes or vendor support.
- Prepare a stable HDMI source and confirm audio, especially if using the 3.5 mm analog input instead of embedded HDMI audio.
- Choose an uplink bitrate below the real venue upload capacity. For a first H.264 internet test, try 4-6 Mb/s for 1080p30 or 6-8 Mb/s for 1080p60, then adjust from Callaba statistics.
Create the Callaba ingest
In Callaba, create an SRT server and choose Listener mode. Assign a UDP port, decide whether Stream ID and passphrase are required, and note the public address or DNS name. Keep the server page open during the first test so you can see connection uptime, bitrate, RTT, packet loss, retransmits, and preview.
If you automate ingest creation, use the SRT servers API. For a manual first test, the web UI is usually faster because the operator can see the received stream immediately.
Configure the RE-2
Open the RE-2 web management interface and add or edit an SRT streaming service. Use Caller mode for the normal cloud workflow. Enter the Callaba public address, UDP port, latency, and optional Stream ID and passphrase. Stream ID and passphrase are case-sensitive and whitespace-sensitive; a trailing space, copied newline, or changed capitalization can stop the SRT handshake.
Set the encoder to H.264 with AAC audio for the first test. If the device exposes GOP or keyframe interval controls, start with a 2-second keyframe interval. After the stream is stable, tune bitrate, latency, and audio source for the production.
Settings table
| Where | What to do / field to fill | First-test value | Why / check |
|---|---|---|---|
| Callaba SRT server | Create listener and choose UDP port | 10080 or your assigned port | RE-2 Caller connects to this port |
| Callaba SRT server | Set Stream ID requirement | Off for first test, or exact value required by routing | Must match RE-2 character for character |
| Callaba SRT server | Set passphrase and encryption policy | Off for first test, then AES with matching passphrase | Encryption mode and key must match both sides |
| RE-2 SRT output configuration | Handshake mode | Caller | Best default for venue-to-cloud contribution |
| RE-2 SRT output configuration | Receiver address | Callaba public IP or DNS name | Do not use a private cloud address from the venue |
| RE-2 SRT output configuration | Receiver port | Same UDP port as Callaba | Wrong port gives no connection |
| RE-2 SRT output configuration | Latency field, in milliseconds | 250-500 ms | Lower only after RTT, packet loss, and retransmits are stable |
| RE-2 encoding settings | Video and audio codec | H.264 video, AAC audio | Matches documented RE-2 capability and common downstream support |
Monitoring
Success is not only a preview image. In Callaba, check incoming bitrate, connection uptime, RTT, packet loss, retransmits, preview, and audio meters. On the RE-2 side, confirm the streaming service is running and that the HDMI source and selected audio input are present.
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 RE-2 ingest workflow.
Recording and playback
After ingest is stable, use Callaba recording and playback as parallel downstream options. Recording does not have to come before routing or restreaming. For operator review, create a web player or multiview output from the same received source while recording continues in the background.
Troubleshooting
| Symptom | Check in Callaba | Check on RE-2 | Likely fix |
|---|---|---|---|
| No connection | Listener running, UDP port open, no address typo | Caller mode, receiver address, receiver port | Correct IP/DNS and port; avoid private cloud IPs |
| Handshake starts then drops | Stream ID and passphrase policy | Stream ID, encryption level, passphrase | Remove copied spaces/newlines; match capitalization and AES mode |
| Preview freezes or retransmits rise | RTT, packet loss, retransmits, incoming bitrate | Configured bitrate and latency | Raise latency to 500 ms, reduce bitrate, check uplink congestion |
| Video without audio | Audio meters and recording audio track | HDMI embedded audio versus 3.5 mm input, AAC setting | Select the intended audio source and use AAC for first test |
| SRT settings unavailable | Use RTMP/RTMPS ingest if needed | Firmware version and streaming service menu | Update firmware or run RTMP/RTMPS fallback for the event |
Official references
Useful resources for checking the exact unit and protocol behavior:
Vendor references
- Kiloview Catalog 2021
- Kiloview RE-2 / REN-2 interface description
- Kiloview Cradle card streaming service documentation
- Kiloview RE-2 firmware 4.7.2512 note
- Kiloview SRT User Manual
- Kiloview SRT Stream ID encoder function
- Kiloview encoder FAQ
Protocol references
Callaba resources
FAQ
Can Kiloview RE-2 send SRT to Callaba?
Yes. Kiloview material lists SRT for RE-2, and an exact RE-2 firmware note references an SRT packet-loss fix. Confirm the installed firmware and visible SRT settings before the event.
Should RE-2 be SRT Caller or SRT Listener?
Use Caller for the normal venue-to-cloud workflow. Listener mode is only practical when the venue side can accept inbound UDP with known firewall and NAT behavior.
Is RE-2 an SRT receiver or gateway?
No. RE-2 is an HDMI encoder card. In this workflow, Callaba is the SRT receiver, gateway, monitor, recorder, and routing layer.
Does Kiloview RE-2 support NDI?
Do not plan RE-2 as a native NDI source. Kiloview distinguishes RE-2 from REN-2, which is the NDI variant in the same card family.
Can I use RTMP or RTMPS instead of SRT?
Yes. RE-2 is documented with RTMP and RTMPS. Use them as a fallback when SRT is unavailable, but test RTMPS with the destination because TLS-related platform behavior can vary.
What usually breaks RE-2 SRT Stream ID or passphrase setup?
Whitespace and capitalization. Copying a newline, adding a trailing space, or changing case can prevent the handshake. Match Stream ID, passphrase, and encryption mode exactly on both sides.
Next steps
For a clean preflight, test the RE-2 with Callaba at the same resolution, bitrate, audio source, Stream ID, passphrase, and latency you plan to use at the event. Let the connection run long enough to see packet loss and retransmit behavior, then make recording and routing decisions after ingest is stable.
Try Callaba Gateway with Kiloview RE-2 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.