Canon CR-N500 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
Canon CR-N500 SRT setup means configuring the PTZ camera to send an SRT contribution feed to a receiver, not adding an external encoder. Use this setup when CR-N500 is at the venue and Callaba is the cloud SRT receiver for monitoring, recording, routing, multiview, or restreaming. The normal internet design is CR-N500 as SRT Caller and Callaba Gateway as SRT Listener on a reachable host and UDP port. Before the event, confirm the camera firmware, because Canon added SRT in firmware 1.2.0 and later firmware improves reconnect behavior.
Quick answer
To use Canon CR-N500 with SRT, set CR-N500 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 camera sends one SRT contribution feed into Callaba. After ingest, Callaba can preview, record, route, restream, play back, and show the same source in multiview as parallel downstream uses.
- Canon CR-N500SRT Caller at venue
- Callaba GatewaySRT Listener in cloud
- Preview
- Record
- Route
- Multiview
- Restream
What this setup does
For Canon CR-N500 SRT to cloud, the camera contributes the live feed and Callaba receives it. If you are searching for CR-N500 SRT receiver or Canon CR-N500 SRT server, separate the roles carefully: in the recommended internet workflow, Callaba is the server/listener side, while the camera calls out from the venue network.
After Callaba receives the stream, monitoring, recording, routing, multiview, browser playback, and restreaming are parallel options. You do not need to record before you route, and you do not need to restream before you monitor.
What this model can and cannot do in this workflow
Confirmed for CR-N500
- Canon lists SRT, RTMP/RTMPS, RTSP/RTP, and NDI HX2 among supported CR-N500 protocols.
- Canon firmware 1.2.0 added SRT support for this model.
- The Canon settings guide documents SRT Caller and Listener modes, latency, Stream ID, passphrase, AES-128/AES-192/AES-256 encryption, adaptive bitrate, auto connection, and reconnect behavior.
- The main IP stream can use H.264 or H.265/HEVC, with H.264 as the safer first test for broad downstream compatibility.
- The camera has 3G-SDI and HDMI outputs in addition to IP streaming, plus XLR audio inputs, a 3.5 mm audio input, genlock, LAN, and RS-422 control.
Confirmed limitations and caveats
- Rendezvous mode was not found in the official CR-N500 settings documentation I reviewed. Do not build a Rendezvous plan unless the installed firmware UI clearly shows it.
- Canon notes that RTMP cannot be used when H.265 is selected for the main IP stream.
- Firmware 1.7.0 adds NDI 6 support and SRT/RTMP reconnection improvements; check the installed firmware before production.
- No official ST 2110 or NDI HX3 support was found for CR-N500, so do not plan those paths for this model.
- The shared Canon settings guide also covers CR-N300, but this article is scoped to CR-N500 specs, firmware notes, and I/O.
Recommended workflow
Use CR-N500 SRT Caller mode for remote contribution. Create a Callaba SRT server, open the selected UDP port in the cloud firewall, then enter the Callaba host and port in the camera. This avoids asking the venue network to accept inbound internet traffic.
For a first internet test, I would use H.264, a conservative bitrate, and 250-500 ms of SRT latency. For 1080p30, 4-6 Mb/s is a practical starting range; for 1080p60, 6-8 Mb/s is a reasonable first test if the uplink is stable. If the camera exposes GOP/keyframe interval, start with about two seconds.
When not to use this setup
- If the camera and switcher are on the same LAN, local 3G-SDI, HDMI, or NDI HX2 may be simpler than cloud ingest.
- If the only target is a public platform and you do not need SRT statistics, cloud monitoring, recording, or routing, CR-N500 RTMP/RTMPS may be enough.
- If you need RTSP/RTP, treat it as a LAN pull or bridge workflow, not the cleanest public internet contribution path.
- If you reverse the SRT roles and make the camera the Listener, the venue side must accept inbound UDP traffic. That can require a public IP, port forwarding, firewall rules, or a tested NAT plan.
Before you start
- Update or confirm CR-N500 firmware. SRT requires firmware 1.2.0 or later; firmware 1.7.0 is important for current NDI 6 and reconnection improvements.
- Reserve a UDP port for the Callaba SRT server and allow it in cloud security rules.
- Decide whether you will use a Stream ID and passphrase. Both are case-sensitive and whitespace-sensitive; a trailing space, copied newline, or changed capitalization can break the handshake.
- Confirm audio at the camera. The model supports XLR audio inputs and a 3.5 mm stereo input, but audio routing still needs to be checked in the installed configuration.
Create the Callaba ingest
In Callaba, create an SRT server for the CR-N500 feed. Choose Listener mode, set the UDP port, and configure Stream ID and passphrase if your production policy requires them. Keep the values short and exact for the first test.
Success in Callaba looks like a connected SRT session with incoming bitrate, stable uptime, preview video, and audio meters. If nothing connects, check the cloud firewall before changing camera settings.
Configure the Canon CR-N500
Open the camera web settings and go to the SRT or IP streaming area for your firmware. Select Caller mode, enter the Callaba public host or IP address, enter the UDP port, and match the Stream ID, encryption, and passphrase exactly. Start with H.264 unless you have already confirmed that every downstream decoder, player, and recorder in the chain handles H.265/HEVC.
Canon documents both Caller and Listener modes. For CR-N500 SRT caller setup, use Caller unless there is a specific network reason to do otherwise.
Settings table
| Where | What to do / field to fill | First-test value | Why / check |
|---|---|---|---|
| Callaba | Create SRT server and choose UDP port | One dedicated port per feed | Port must be reachable from the venue internet. |
| Callaba | Set passphrase and encryption policy | Off for lab test, AES with passphrase for production | Must match the camera exactly. |
| Canon CR-N500 SRT settings | Select Caller mode | Caller | Camera initiates outbound connection to Callaba. |
| Canon CR-N500 SRT settings | Destination address | Callaba public host or IP | Use DNS only if venue DNS is reliable. |
| Canon CR-N500 SRT settings | Destination port | Callaba UDP port | Must match the Callaba SRT server port. |
| Canon CR-N500 SRT settings | Latency | 250-500 ms | Lower only after RTT, packet loss, and retransmits are stable. |
| Canon CR-N500 SRT settings | Stream ID | Exact Callaba Stream ID, if used | Case and whitespace must match. |
| Canon CR-N500 IP stream settings | Main stream codec and bitrate | H.264 at a conservative bitrate | H.265 is supported on the main IP stream, but RTMP cannot use it and downstream HEVC support must be confirmed. |
Monitoring
Once connected, watch Callaba receiver statistics before judging picture quality. Check incoming bitrate, connection uptime, RTT, packet loss, retransmits, preview, and audio meters. A stable preview with rising retransmits usually means the network is barely coping; raise latency or lower bitrate before the event starts.
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 Canon CR-N500 ingest workflow.
Recording and playback
After the CR-N500 feed is stable in Callaba, recording and playback are downstream choices. You can record the incoming feed for archive, send a routed output to another system, create browser playback, or restream to a platform. Treat these as parallel outputs from the same ingest, not as required setup steps.
Troubleshooting
| Symptom | Check in Callaba | Check on device | Likely fix |
|---|---|---|---|
| No connection | SRT server running, UDP port open, no firewall drop | Caller mode, host, port | Fix address/port or cloud firewall first. |
| Handshake fails | Stream ID and passphrase policy | Stream ID, passphrase, encryption mode | Remove trailing spaces and match capitalization exactly. |
| Connects then drops | RTT, loss, retransmits, uptime | Firmware version, auto connection/reconnect settings | Update firmware, raise latency, reduce bitrate. |
| Video but no audio | Preview and audio meters | XLR/3.5 mm input selection and audio stream settings | Confirm input routing and audio enabled in the camera. |
| Interoperability is unclear | Callaba build or support information | Canon firmware release notes or vendor support docs | Canon does not publish the SRT library version in the reviewed docs; confirm compatible SRT major-version behavior with support if needed. |
Official references
Vendor references
- Canon Support for CR-N500
- Canon CR-N500 firmware 1.2.0 notice
- Canon CR-N500 firmware 1.7.0 notice
- Canon CR-N500 / CR-N300 Settings Guide
Protocol references
Callaba resources
FAQ
Does Canon CR-N500 support native SRT?
Yes. Canon firmware 1.2.0 added SRT support for CR-N500. Confirm installed firmware before planning the show.
Should CR-N500 be SRT Caller or Listener?
Use CR-N500 SRT Caller for normal cloud contribution. Listener mode is documented, but it usually requires inbound access to the venue network.
Can I use a CR-N500 SRT Stream ID and passphrase?
Yes. Canon documents Stream ID for Caller mode and passphrase/encryption settings. Match Callaba exactly, including capitalization and whitespace.
Can CR-N500 send RTMP or RTMPS instead?
Yes, Canon documents RTMP and RTMPS URLs. Note that RTMP cannot be used when the main IP stream is set to H.265.
Can I use NDI with this model?
Canon lists NDI HX2 for CR-N500, and firmware 1.7.0 adds NDI 6 support. I would use it mainly for LAN production or an NDI-to-SRT bridge, not as the default public internet path.
Does CR-N500 support ST 2110?
No official ST 2110 support was found for this model. Use SDI, HDMI, SRT, RTMP/RTMPS, RTSP/RTP, or NDI HX2 workflows instead.
Next steps
Start with one CR-N500 feed, confirm SRT connection stability in Callaba, then add recording, multiview, routing, playback, or restreaming only after ingest is clean. For multi-camera shows, label each SRT server and Stream ID clearly so operators can diagnose feeds quickly.
Try Callaba Gateway with Canon CR-N500 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.