JVC GY-HC900 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 JVC GY-HC900 SRT setup, use the camera as the field contribution encoder and send SRT to a cloud listener in Callaba Gateway. Use this setup when GY-HC900 is at the venue and Callaba is the cloud SRT receiver for monitoring, recording, routing, multiview, or restreaming. The default direction I recommend is GY-HC900 as SRT Caller and Callaba as SRT Listener, especially when the camera is behind venue NAT.
Quick answer
To use JVC GY-HC900 with SRT, set GY-HC900 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, and feed multiview in parallel. These are downstream uses, not mandatory sequential setup steps.
- GY-HC900SRT caller
- Callaba GatewaySRT listener
- Preview
- Record
- Route
- Multiview
- Restream
What this setup does
This workflow turns the GY-HC900 into an SRT contribution source for remote production. The camera sends a live encoded feed over the public internet to Callaba. Callaba receives the stream, shows preview and stream statistics, and can make the same source available for recording, multiview, restreaming, routing, or playback outputs.
In search terms, the GY-HC900 is normally the SRT caller, Callaba is the SRT receiver or listener, and the public IP or DNS name belongs to the Callaba-side gateway. If someone says JVC GY-HC900 SRT server in this workflow, they usually mean the receiving SRT server in Callaba, not that the camera must accept inbound internet traffic.
What this model can and cannot do in this workflow
- Confirmed SRT contribution: JVC lists SRT support for the GY-HC900 and describes AES encryption, ARQ recovery, Stream ID behavior, and FEC in its camera and firmware material.
- Confirmed SRT fields: JVC’s API reference for this camera family lists destination address, destination port, Stream ID, ConnectionMode, bandwidth overhead, latency, encryption, FEC, adaptive bitrate, PCR mode, passphrase, and status for SRT streaming settings.
- Caller, Listener, Rendezvous: ConnectionMode values are documented. For venue contribution, start with camera Caller to Callaba Listener. Reversing the roles is an advanced firewall plan, not the normal first setup.
- RTMP, RTMPS, and RTSP/RTP: These are valid fallback paths on this model, but they do not replace the SRT contribution workflow when you need caller/listener control, Stream ID, retransmission behavior, and receiver-side diagnostics.
- Codec caveat: H.264 live streaming up to 20 Mb/s is part of the published live streaming specification. HEVC/H.265 streaming is tied to firmware v0300 and the optional KA-EN200 encoder, so confirm the installed option before planning HEVC.
- Hardware I/O: The camera includes RJ45 Gigabit Ethernet, USB network support, built-in 2.4 GHz and 5 GHz Wi-Fi, two 3G-SDI outputs, a 3G-SDI input for pool feed, HDMI output, XLR audio, genlock, and timecode I/O.
- No required vendor receiver layer: For Callaba ingest, the camera can send SRT directly to the gateway when SRT is enabled and the network path is open. Optional bonding hardware is a network transport choice, not a required cloud receiver.
- Do not plan it as native NDI: Official GY-HC900 camera streaming specifications do not list native NDI output for this model. Use SRT, RTMP/RTMPS, RTSP/RTP, SDI, or HDMI as the confirmed paths.
- Do not plan it as ST 2110: I do not see official GY-HC900 documentation listing this camera as a SMPTE ST 2110 source.
- Variant note: GY-HC900CHU and GY-HC900STU are closely related packages in the same camera family. This page is about the camera’s IP streaming path to Callaba, not base station or studio fiber wiring.
Recommended workflow
Use Callaba as the public SRT listener and the GY-HC900 as the caller. This is the most practical GY-HC900 SRT to cloud pattern because the camera makes the outbound UDP connection from the venue. The venue usually does not need inbound port forwarding to the camera.
Use Listener or Rendezvous on the camera only when your network design requires it. If the camera must receive inbound SRT from the internet, the venue side needs a public IP, UDP port forwarding, firewall rules, or a tested NAT traversal plan. That adds operational risk during a live event.
When not to use this setup
If the camera and production switcher are in the same truck, control room, or studio LAN, SDI or HDMI may be simpler and lower risk. If the only destination is a public platform and you do not need receiver monitoring, cloud recording, multiview, routing, or restreaming, RTMP or RTMPS from the camera may be enough. If the feed is remote contribution over the public internet and you need confidence monitoring and downstream routing, use the SRT gateway workflow.
Do not choose NDI for this exact model unless you are adding an external SDI/HDMI-to-NDI bridge. The GY-HC900 itself should not be planned as a native NDI camera.
Before you start
- Confirm the installed firmware and that SRT is available in the camera’s live streaming server settings.
- Confirm whether the camera is configured for SRT rather than an alternative vendor-specific contribution protocol package.
- Decide the production format: 720p, 1080p30, 1080i, or 1080p60, then choose a bitrate that the venue uplink can sustain.
- For a first internet test, use 250-500 ms SRT latency unless your camera firmware default or engineering plan says otherwise. JVC firmware notes also mention a 500 ms SRT latency default in the V4.00 update.
- Start interoperability tests with SRT FEC off unless the receiver path is already known to accept the selected GY-HC900 FEC mode.
- If encryption is enabled, prepare the exact Stream ID and passphrase. Both are case-sensitive and whitespace-sensitive.
Create the Callaba ingest
- Open Callaba and create a new SRT server.
- Set the server to listen on a known UDP port, then allow that UDP port in the cloud firewall or security group.
- If you use Stream ID routing, enter the Stream ID you want the GY-HC900 to send.
- For the first handshake, you can test without encryption. For production, enable encryption and use the same passphrase on both sides.
- Copy the Callaba public IP or DNS name, UDP port, Stream ID, latency plan, and passphrase into your run sheet.
Success looks like a connected SRT session in Callaba with incoming bitrate, connection uptime, preview video, and audio meters. If Callaba does not show a connection attempt, check firewall and destination address before changing camera codec settings.
Configure the GY-HC900
On the camera, use the Network and Live Streaming areas. JVC firmware notes place SRT-related settings under Network > Live Streaming > Streaming Server > Server 1-4. Select SRT as the streaming type, then fill the Callaba destination address and destination port.
Set ConnectionMode to Caller for the first Callaba test. Enter the Stream ID exactly as it appears in Callaba if you use one. If encryption is enabled, set the same AES mode and passphrase on both sides. A trailing space, copied newline, or changed capitalization in Stream ID or passphrase can break the SRT handshake.
Use H.264 for the first interoperability test. Practical starting bitrates are 2.5-4 Mb/s for 720p, 4-6 Mb/s for 1080p30, and 6-8 Mb/s for 1080p60, then adjust for uplink quality and production expectations. Use HEVC only after confirming the optional KA-EN200 encoder and downstream decoder support.
Settings table
| Where | What to do / field to fill | First-test value | Why / check |
|---|---|---|---|
| Callaba | Create SRT server and choose UDP listening port | Known open UDP port | Callaba must be reachable from the venue internet path. |
| GY-HC900 Streaming Server | DstAddress | Callaba public IP or DNS | The camera calls the cloud listener. |
| GY-HC900 Streaming Server | DstPort | Same UDP port as Callaba | Port mismatch is a common no-connect cause. |
| GY-HC900 SRT settings | ConnectionMode | Caller | Best first choice when the camera is behind NAT. |
| GY-HC900 SRT settings | StreamId | Example: gyhc900-cam1 | Case-sensitive and whitespace-sensitive; JVC firmware notes list up to 63 characters. |
| GY-HC900 SRT settings | Latency | 250-500 ms for internet test | Increase if RTT, packet loss, or retransmits are unstable. |
| GY-HC900 SRT settings | Encryption | Off for handshake test; AES for production | Both sides must use matching encryption behavior. |
| GY-HC900 SRT settings | Passphrase | 10-79 ASCII characters when encryption is on | Must match Callaba exactly; avoid copied spaces or newlines. |
Monitoring checks
After the GY-HC900 starts streaming, check Callaba for connection uptime, incoming bitrate, packet loss, RTT, retransmits, preview video, and audio meters. Watch these values for several minutes before the event, not only for the first connection. If the bitrate is present but preview is black, treat that as a video format or decode check. If preview is present but audio is missing, check camera audio input assignment, audio enable state, and Callaba meters.
Recording and playback
Callaba recording is a downstream use of the received SRT feed. Start recording after the incoming stream is stable, then verify file growth and a short playback test. The GY-HC900 also supports local recording and simultaneous live streaming according to JVC specifications, so decide whether the camera card, Callaba recording, or both are required for the job.
For playback or review, use a Callaba web player or routed output after ingest. Keep this separate from the contribution setup: first stabilize SRT ingest, then enable the downstream outputs needed by the production.
Troubleshooting
| Symptom | Check in Callaba | Check on device | Likely fix |
|---|---|---|---|
| No connection | No incoming session or bitrate on the SRT server | DstAddress, DstPort, ConnectionMode Caller, SRT enabled | Open the UDP port, correct the destination, and confirm SRT activation in installed firmware. |
| Handshake starts then fails | Connection attempt appears but drops | Stream ID, encryption mode, passphrase | Retype Stream ID and passphrase manually; remove trailing spaces and copied newlines. |
| Connects but drops on poor network | RTT, packet loss, retransmits, bitrate graph | Latency, bitrate, FEC, adaptive bitrate setting | Raise latency, lower bitrate, test with FEC off first, then evaluate adaptive bitrate if firmware supports it. |
| Video present, no audio | Audio meters and player audio track | XLR input selection, audio levels, stream audio enable | Verify the camera input assignment and send tone before the show. |
| HEVC does not decode downstream | Preview or player compatibility | KA-EN200 option and codec selection | Use H.264 first; use HEVC only after confirming the camera option and receiver/player support. |
| Hard-to-explain SRT failures | Server build, logs, and support information | Firmware release notes and vendor support information for SRT implementation | Confirm compatible SRT major versions on both sides, especially when encryption, Stream ID, Rendezvous, or FEC is enabled. |
Official references
These are the most useful resources for confirming exact settings before a live job.
Vendor references
- JVC GY-HC900CHU product page
- GY-HC900 Firmware V0400 updated features and instructions
- GY-HC900 Firmware V0410 updated features and instructions
- JVC Camcorder Web API Reference
Protocol references
Callaba resources
FAQ
How do I use JVC GY-HC900 with SRT and Callaba?
Create an SRT listener in Callaba, then configure the GY-HC900 streaming server as SRT Caller with Callaba’s public address and UDP port. Match Stream ID, latency, encryption, and passphrase.
Should the GY-HC900 be SRT Caller or SRT Listener?
Use GY-HC900 SRT Caller for the first cloud workflow. Listener and Rendezvous are documented modes, but they require a more deliberate network plan and may need inbound UDP access to the camera side.
Does the GY-HC900 support SRT Stream ID and passphrase?
Yes. JVC firmware and API references list Stream ID and SRT passphrase behavior. Treat both as exact strings: capitalization, spaces, and copied newlines matter.
Can I use RTMP or RTMPS instead of SRT?
Yes, this model supports RTMP and RTMPS when the appropriate firmware feature is available. Use RTMPS for simple platform delivery. Use SRT when you need a contribution receiver, stats, routing, and monitoring in Callaba.
Is the JVC GY-HC900 a native NDI source?
No. Do not plan the GY-HC900 as a native NDI source. If the production needs NDI, use an external SDI or HDMI bridge and test that bridge separately.
Can the GY-HC900 send HEVC/H.265 to Callaba?
Only plan HEVC after confirming firmware v0300 or later, the optional KA-EN200 encoder, and downstream decoder support. For first tests and mixed receiver environments, H.264 is the safer starting codec.
Next steps
- Create one Callaba SRT server per camera or use Stream ID routing if your workflow is designed for it.
- Run a 20-30 minute venue network test with the same bitrate, latency, and encryption settings planned for the show.
- Check preview, audio meters, packet loss, RTT, retransmits, recording, and a short playback clip before handing the feed to production.
- Document the camera firmware, SRT mode, Stream ID, passphrase, port, bitrate, and codec in the show run sheet.
Try Callaba Gateway with JVC GY-HC900 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.