Kiloview RE-3 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
For a Kiloview RE-3 SRT setup, use the RE-3 rack encoder card at the venue and send an outbound SRT feed to Callaba in the cloud. Use this setup when RE-3 is at the venue and Callaba is the cloud SRT receiver for monitoring, recording, routing, multiview, or restreaming. The practical default is RE-3 as SRT Caller and Callaba as SRT Listener.
Quick answer
To use Kiloview RE-3 with SRT, set RE-3 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 the event, confirm the installed RE-3 firmware exposes the expected SRT fields.
The RE-3 sends one SRT contribution feed into Callaba. Preview, recording, routing, multiview, and restreaming are parallel downstream uses after ingest, not mandatory sequential steps.
- Kiloview RE-3SRT Caller at venue
- Callaba GatewaySRT Listener in cloud
- Preview
- Record
- Route
- Multiview
- Restream
What this setup does
The RE-3 contributes one encoded feed over Gigabit Ethernet. Callaba receives that feed as SRT and then lets the same source be used in parallel for preview, recording, playback, multiview, routing, restreaming, or API-controlled workflows. You do not need a Kiloview cloud receiver layer for this path.
This is an encoder workflow, not a decoder return-feed workflow. The RE-3 captures HDMI, SDI, USB UVC, or analog audio input and sends IP output; Callaba is the receiver side.
What this model can and cannot do in this workflow
- Confirmed contribution protocols: Kiloview lists SRT, RTMP, RTMPS, RTSP, NDI HX2/HX3, HLS, WHIP, TS over UDP, and RTP for RE-3.
- Inputs: RE-3 is a rack card for RU01/RU03 chassis with HDMI 1.4b up to 3840×2160p30, 3G-SDI up to 1080p60, USB UVC up to 1080p60, and 3.5 mm line-level audio.
- Codecs: official material lists H.264/AVC and H.265/HEVC encoding. Use H.264 plus AAC for the first SRT test unless your full chain is ready for HEVC.
- SRT fields: Kiloview documentation linked from RE-3 support documents Stream ID, AES key, AES-128/192/256 encryption, and Caller/Listener/Rendezvous options. Treat exact UI labels cautiously because that English manual is titled E3.
- Limits: do not plan this model as Full NDI / NDI High Bandwidth or ST 2110. Kiloview lists NDI HX2/HX3 for RE-3.
- Firmware caveats: RE-3 firmware notes mention SRT 1.5.3 and later support, firmware 1.25 updates NDI SDK to 6.3 and expands the SRT Caller port range, firmware 1.24 adds RTMP H.265 modes, and firmware 1.23 adds OPUS audio encoding.
- Close variant note: Kiloview E3 is a related standalone encoder. This guide is for the RE-3 rack card; do not copy assumptions from an E3-titled manual without checking the RE-3 firmware menu.
Recommended workflow
Use RE-3 as SRT Caller and Callaba as SRT Listener. This keeps the venue side outbound, which is usually easier through NAT and venue firewalls. Reversing the roles can work only if the RE-3 side can accept inbound UDP traffic with a public IP, port forwarding, firewall rules, or a tested NAT plan.
If SRT is blocked or unavailable on the installed firmware, use RTMPS or RTMP as the first fallback. Use NDI HX or RTSP through a bridge only when the encoder and bridge are on the same LAN or when the production design deliberately needs a local bridge.
When not to use this setup
- If the switcher, encoder, and operators are all on the same LAN, local SDI/HDMI or NDI HX may be simpler than a cloud contribution path.
- If the only destination is a public platform and monitoring or routing is not important, RTMP/RTMPS may be enough. Use H.264 for widest RTMP compatibility.
- If the job requires Full NDI or ST 2110 from the encoder, choose another device; those are not listed for RE-3.
- If the SRT menu is missing, update RE-3 firmware first or use confirmed RTMPS/RTMP while you resolve the device firmware issue.
Before you start
Confirm the RE-3 firmware version, visible SRT settings, input signal format, uplink bandwidth, and firewall path. I recommend confirming SRT caller/listener direction, Stream ID, passphrase, AES mode, latency/buffer setting if exposed, and codec settings before the event. Stream ID and passphrase are case-sensitive and whitespace-sensitive; a trailing space or copied newline can break the handshake.
For hard SRT failures, compare the RE-3 firmware notes with Callaba server build or support information so both sides use compatible SRT behavior.
Create the Callaba ingest
- In Callaba, create an SRT server/listener and choose a UDP port reachable from the venue.
- Set a Stream ID and passphrase if your workflow uses them. Keep the exact spelling for the device setup.
- Start the listener and confirm it is waiting for input.
- Keep the Callaba host, UDP port, Stream ID, encryption mode, and passphrase available for the RE-3 operator.
Configure the RE-3
Open the RE-3 web interface for the rack card. Select the correct input, confirm embedded or analog audio, and create an SRT output in the streaming area. Set the RE-3 to Caller, enter the Callaba public host and UDP port, paste the Stream ID and passphrase exactly, then start streaming.
For the first test, use H.264 with AAC audio. If the firmware exposes a latency or buffer field, start around 250-500 ms for an internet path and reduce only after packet loss, RTT, and retransmits are stable.
Settings table
| Where | What to do / field to fill | First-test value | Why / check |
|---|---|---|---|
| Callaba SRT server | Create listener and choose UDP port | Any open production port | Callaba should show waiting, then connected |
| Callaba SRT server | Stream ID | re3-main | Must match RE-3 exactly |
| Callaba SRT server | Passphrase and AES mode | AES-128 or AES-256 | Must match RE-3 exactly |
| RE-3 SRT settings | Connection mode | Caller | Default cloud path; confirm the visible firmware label |
| RE-3 SRT settings | Destination host | Callaba public IP or DNS | Outbound from venue to cloud |
| RE-3 SRT settings | Destination port | Callaba UDP port | Firewall must allow UDP |
| RE-3 SRT settings, if exposed | Latency / buffer value | 250-500 ms | Raise for lossy internet links |
| RE-3 video encoder settings | Video codec and bitrate | H.264, 1080p30 at 4-6 Mb/s | Adjust to uplink and production needs |
Monitoring
In Callaba, check connection uptime, incoming bitrate, preview, audio meters, RTT, packet loss, and retransmits. The received bitrate should be close to the RE-3 encoder bitrate after overhead. If preview is stable but downstream output fails, troubleshoot the downstream output separately; ingest, recording, routing, and restreaming are parallel uses of the same source.
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-3 ingest workflow.
Recording and playback
RE-3 documentation lists local USB and NAS recording, but cloud recording in Callaba is independent of device media. After SRT ingest is stable, start Callaba recording and, if needed, create playback or web-player outputs from the received source. Keep device-side recording as a separate backup, not as a requirement for Callaba ingest.
Troubleshooting
| Symptom | Check in Callaba | Check on RE-3 | Likely fix |
|---|---|---|---|
| No connection | Listener running, UDP port open, no incoming bitrate | Caller mode, host, port | Fix DNS/IP, port, firewall, or NAT path |
| Handshake fails | Stream ID and passphrase | Stream ID, AES mode, AES key | Remove trailing spaces and match capitalization |
| Connected but no audio | Audio meters | Input audio source and codec | Use AAC for first test; note firmware notes restrict G.711a/u on several IP protocols |
| Stutter or drops | RTT, loss, retransmits, bitrate | Encoder bitrate and latency/buffer | Lower bitrate or raise latency |
| NDI works locally but not to cloud | No SRT input | NDI HX2/HX3 output selected | Switch to direct SRT or use a LAN bridge intentionally |
Official references
Useful references for confirming the exact firmware and protocol details:
FAQ
Is Kiloview RE-3 the SRT caller or listener?
For cloud contribution, use RE-3 as SRT Caller and Callaba as SRT Listener. Listener and Rendezvous modes are documented in the support-linked manual, but I would verify those fields on the installed RE-3 firmware before relying on them.
Is Callaba the Kiloview RE-3 SRT server?
In this workflow, yes in practical terms: Callaba is the cloud SRT listener/receiver, and RE-3 sends the outbound SRT feed to it.
Can RE-3 use SRT Stream ID and passphrase?
Kiloview documentation linked from RE-3 support documents Stream ID, AES key, and AES-128/192/256 encryption. Match values exactly on both sides.
What if the SRT menu is missing on RE-3?
Check the installed firmware and update if needed. If you cannot update before the event, use confirmed RTMPS/RTMP, or use an RTSP/NDI HX bridge only when that architecture is already tested.
Does RE-3 support NDI?
Kiloview lists NDI HX2 and HX3 for RE-3. Do not plan it as Full NDI / NDI High Bandwidth or ST 2110 unless Kiloview publishes exact RE-3 support.
Should I use H.265 with SRT or RTMP?
RE-3 lists H.265 encoding, but H.264 is safer for first tests and broad playback. RTMP H.265 modes depend on RE-3 firmware 1.24 or later and receiver support.
Next steps
Build one clean RE-3 SRT profile, save the Callaba host, port, Stream ID, passphrase, codec, bitrate, and latency values, and test on the same network type you will use for the event. After the ingest is stable, add recording, multiview, restreaming, and routing as separate downstream tasks.
Try Callaba Gateway with Kiloview RE-3 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.