JVC GY-HC550 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-HC550 SRT setup, use the camera as the field source and send SRT to a reachable cloud listener. Use this setup when GY-HC550 is at the venue and Callaba is the cloud SRT receiver for monitoring, recording, routing, multiview, or restreaming. The practical default is GY-HC550 as SRT Caller and Callaba Gateway as SRT Listener, because the camera can start the outbound session from the venue network.
Quick answer
To use JVC GY-HC550 with SRT, set GY-HC550 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 contribution feed into Callaba. After ingest, preview, recording, routing, multiview, and restreaming are parallel downstream uses, not mandatory sequential setup steps.
- JVC GY-HC550SRT caller at venue
- Callaba GatewaySRT listener in cloud
- Preview
- Record
- Route
- Multiview
- Restream
What this setup does
The GY-HC550 contributes a live encoded feed over SRT. Callaba receives that feed, shows connection health, and can use the same source for preview, recording, restreaming, routing, playback, API workflows, or multiview. Callaba is not replacing the camera encoder. It is the cloud gateway and receiver side of the contribution path.
The searched phrases can be confusing: for this workflow, GY-HC550 SRT caller means the camera starts the SRT session; GY-HC550 SRT listener means the camera waits for an inbound SRT session; GY-HC550 SRT receiver or JVC GY-HC550 SRT server is usually not what you want for cloud ingest. The simpler internet pattern is camera caller to Callaba listener.
What this model can and cannot do in this workflow
- Confirmed for this camera family: live streaming types include SRT, RTMP, RTMPS, RTSP/RTP, and MPEG2-TS transports in JVC documentation.
- SRT fields are real device settings: JVC lists Connection Mode with Caller, Listener, and Rendezvous, plus Destination Address, Port, Stream ID, Bandwidth Overhead, Latency, Encryption, Passphrase, and SRT FEC.
- Codec starting point: use H.264/AAC first. JVC lists live streaming video as MPEG-4 AVC/H.264 and audio as AAC in the GY-HC550 specifications.
- HEVC caveat: H.265/HEVC streaming is tied to the optional KA-EN200 or KA-EN200G encoder adapter, depending on region and accessory naming. Test HEVC through Callaba preview, recording, and playback before production.
- Network inputs: the camera supports IP streaming through Ethernet RJ-45 1000BASE-T, built-in Wi-Fi, and supported USB Wi-Fi/LTE/Ethernet adapters. A USB cellular adapter is not the same as bonded cellular transmission.
- Baseband outputs: 3G-HD-SDI and HDMI are outputs, not inputs for this SRT workflow. Audio input is available through two XLR mic/line channels with +48 V support.
- NDI distinction: do not plan an unmodified GY-HC550U/E as a native NDI source. JVC documents NDI|HX for GY-HC550UN, GY-HC550EN, GY-HC550ESBN, or officially modified units, and NDI|HX mode disables camera media recording and non-NDI streaming.
- No vendor receiver required for SRT: direct SRT can go to Callaba.
Recommended workflow
Create an SRT listener in Callaba, open the selected UDP port, and configure the GY-HC550 live streaming server preset to call that address. Keep the first test simple: H.264, moderate bitrate, no unnecessary protocol layers, and a latency value that gives SRT time to recover lost packets.
Use Caller mode on the camera unless the network design requires otherwise. Reversing the roles is possible because JVC lists Listener and Rendezvous modes, but it means the venue or camera side must accept inbound traffic. That may require public IP addressing, UDP port forwarding, firewall rules, or a tested NAT plan.
When not to use this setup
- If the camera and switcher are on the same table, SDI or HDMI may be simpler than cloud SRT.
- If the only destination is a public platform and routing, monitoring, and low-latency return are not important, RTMP or RTMPS may be enough.
- If the job is LAN production with NDI, use only a documented NDI|HX variant or a JVC-modified unit. Do not assume every GY-HC550 suffix has NDI|HX.
- If your facility is built around RTSP/RTP, use RTSP as a controlled LAN or bridge workflow. I would not choose RTSP/RTP as the first public-internet contribution path for this camera when SRT is available.
Before you start
Confirm the exact suffix printed on the camera and the installed firmware or protocol package.
Also prepare the Callaba public IP or DNS name, UDP port, Stream ID, latency, encryption mode, and passphrase. Treat Stream ID and passphrase as case-sensitive and whitespace-sensitive. A copied newline, trailing space, or changed capitalization can break the SRT handshake.
Create the Callaba ingest
- Open Callaba and create an SRT server for the camera feed.
- Set the server to Listener mode and choose a UDP port that is open in the cloud firewall and host firewall.
- Add a Stream ID if you use stream-based routing or multiple cameras on one listener.
- If encryption is enabled, set the same passphrase and AES strength that you will enter on the camera.
- Start the server and keep the Callaba stream status page open for bitrate, uptime, packet loss, retransmits, RTT, preview, and audio meters.
Configure the GY-HC550
- Open the camera web interface or the camera menu, then go to the Live Streaming settings.
- Select one of the four streaming server presets, for example Server1, and give it a clear alias such as Callaba Main.
- Set Type to SRT. If SRT is not available where you expect it, stop and confirm the installed SRT protocol package.
- Set Connection Mode to Caller for the default cloud workflow.
- Set Destination Address to the Callaba public IP or DNS name and Port to the UDP port used by the Callaba listener.
- Enter the Stream ID if your Callaba route requires one.
- Use the camera Latency field for SRT latency. The documented default is 500 ms, which is a good first internet test.
- Start Live Streaming. Success means Callaba shows an active connection with stable incoming bitrate and usable preview/audio, not only a connected socket.
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 planned port | The cloud side must be reachable before the camera calls it. |
| Callaba route | Set Stream ID rule if used | event-main | Must match the camera exactly, including capitalization. |
| GY-HC550 Streaming Server | Type | SRT | Enables SRT-only settings such as mode, latency, encryption, and FEC. |
| GY-HC550 SRT settings | Connection Mode | Caller | Best first cloud setup because the camera initiates the session. |
| GY-HC550 SRT settings | Destination Address | Callaba public IP or DNS | Use the listener address without protocol text unless the camera UI asks otherwise. |
| GY-HC550 SRT settings | Port | Same UDP port as Callaba | JVC allows SRT port numbers from 1 to 65535; the camera default is 6504, but your Callaba port must match. |
| GY-HC550 SRT settings | Latency | 500 ms | JVC documents 20 ms to 8000 ms and a 500 ms default. Lower it only after RTT and loss are stable. |
| GY-HC550 SRT settings | Passphrase | Off for first link, then AES with shared passphrase | When encryption is on, match passphrase exactly. JVC documents 10 to 79 characters. |
Monitoring
Watch the Callaba receiver before you trust the feed. The useful checks are incoming bitrate, connection uptime, RTT, packet loss, retransmits, preview frames, and audio meters. On the camera side, confirm that Live Streaming is actually On and that the selected server preset is the Callaba preset.
If the venue uplink is unstable, reduce bitrate before lowering latency. Practical starting points are 720p around 2.5-4 Mb/s, 1080p30 around 4-6 Mb/s, and 1080p60 around 6-8 Mb/s, adjusted to the production frame rate and available uplink.
Recording and playback
Once ingest is stable, Callaba recording and playback are downstream uses of the received source. They do not need to happen before routing or restreaming. For the first production test, record a short clip, play it back, and check audio sync, codec compatibility, and whether the file matches the expected frame rate.
If you use HEVC from the optional KA-EN200/KA-EN200G path, test all downstream targets. Some browsers, players, and decoders accept H.264 more predictably than HEVC.
Troubleshooting
| Symptom | Check in Callaba | Check on device | Likely fix |
|---|---|---|---|
| No connection | Listener is running, UDP port is open, no cloud firewall block. | Connection Mode is Caller, address and port match. | Open the UDP port and remove NAT/firewall ambiguity. |
| Connected but no usable video | Incoming bitrate, preview, codec, and audio meters. | Resolution, frame rate, bitrate, H.264 first-test codec. | Lower bitrate, use H.264/AAC, then test higher settings. |
| Handshake fails with security enabled | Stream ID and passphrase in the Callaba route. | Stream ID, Encryption, Passphrase. | Retype values. Remove trailing spaces and copied newlines. |
| Unstable feed | RTT, packet loss, retransmits, bitrate spikes. | Latency, Bandwidth Overhead, FEC, network adapter. | Raise latency, reduce bitrate, and test a wired Ethernet path. |
| SRT option or behavior differs from this guide | Server build and support information. | Installed firmware and SRT protocol package. | Confirm firmware with JVC support. If handshake errors persist, compare SRT version compatibility through vendor release notes or support channels. |
Official references
These are the most useful resources for confirming the camera side and the receiver side before an event.
Vendor references
- JVC GY-HC550U product page
- JVC GY-HC550 mobile user guide, streaming server settings
- JVC Japan GY-HC550 specifications
- JVC GY-HC550UN NDI|HX variant page
- JVC NDI|HX functions supplement for supported variants
- JVC RTMPS connection guide for GY-HC500 Series
Protocol references
Callaba resources
FAQ
How do I use JVC GY-HC550 with SRT?
Create an SRT listener in Callaba, set the camera Live Streaming Type to SRT, choose Caller mode, and enter the Callaba address, UDP port, Stream ID, latency, and security settings.
Should GY-HC550 be SRT Caller or SRT Listener?
Use Caller for the first cloud setup. Listener and Rendezvous are documented options, but they add network requirements on the venue side.
Is the GY-HC550 an SRT receiver or SRT server?
In this workflow, no. The camera is the SRT source. Callaba is the SRT receiver, listener, gateway, and routing layer.
Can I use RTMP or RTMPS instead?
Yes. JVC documents RTMP and RTMPS live streaming for this camera family. Use RTMPS when the destination is a platform-style ingest and SRT monitoring or routing is not required.
Does every GY-HC550 support NDI?
No. The documented NDI path is NDI|HX on GY-HC550UN, GY-HC550EN, GY-HC550ESBN, or officially modified units. Do not assume NDI|HX on an unmodified GY-HC550U/E.
Can I send H.265 SRT from the camera?
Only plan HEVC after confirming the optional KA-EN200 or KA-EN200G encoder path and downstream compatibility. Use H.264/AAC for the first Callaba ingest test.
Next steps
Build one clean ingest first: GY-HC550 Caller to Callaba Listener, H.264/AAC, stable bitrate, matched Stream ID, and confirmed audio. After that, add recording, multiview, restreaming, routing, or API automation as separate downstream tasks.
Try Callaba Gateway with JVC GY-HC550 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.