Panasonic AG-CX350 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
The Panasonic AG-CX350 SRT setup I recommend for remote contribution is: make the camera the SRT caller and send one contribution stream to Callaba running as the cloud SRT listener. Use this setup when AG-CX350 is at the venue and Callaba is the cloud SRT receiver for monitoring, recording, routing, multiview, or restreaming. The same camera also documents RTMP, RTMPS, RTSP/RTP, and NDI|HX1, but direct SRT is the cleanest Callaba Gateway path when the camera firmware exposes SRT CLIENT.
Quick answer
To use Panasonic AG-CX350 with SRT, set AG-CX350 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 preview, recording, routing, multiview, and restreaming are parallel downstream uses, not mandatory sequential setup steps.
- AG-CX350SRT caller
- Callaba GatewaySRT listener
- Preview
- Record
- Route
- Multiview
- Restream
What this setup does
This workflow turns the AG-CX350 into a field contribution camera. The camera initiates the SRT session from the venue, so the venue network usually does not need to expose the camera to the public internet. Callaba receives the feed, shows preview and stream statistics, and can create downstream outputs in parallel.
For searched terms: the normal AG-CX350 SRT caller workflow means Callaba is the SRT listener, receiver, or server. AG-CX350 SRT listener mode is documented, but I would treat it as an advanced fallback because the camera side must accept an inbound connection.
What this model can and cannot do in this workflow
- Confirmed: AG-CX350 documentation lists SRT, RTMP, RTMPS, and RTSP/RTP streaming, plus NDI|HX1 over LAN when enabled.
- Confirmed: the streaming menu includes SRT CLIENT and SRT LISTENER. SRT client mode has DEST URL and STREAM ID. SRT listener mode has a PORT setting and uses a fixed listener Stream ID.
- Confirmed: SRT settings include LATENCY, TTL/HOP LIMIT, AES128, AES192, AES256, and PASSPHRASE.
- Codec notes: the streaming specification lists H.264 with AAC-LC audio. 4K streaming tables include H.264 and H.265 formats, but RTMP(S) does not support H.265, and RTMPS is H.264 only.
- Limits: SRT does not support 23.98/24p on this model, and Panasonic notes that SRT streaming does not support SD video. When SRT encryption is enabled, keep 4K streaming at 25 Mb/s or lower.
- Not confirmed: I found no official AG-CX350 support for SRT rendezvous mode, SMPTE ST 2110, or native bonded cellular contribution.
- I/O context: the camera has LAN RJ-45, SDI OUT, HDMI OUT, XLR audio inputs, built-in stereo microphone, TC IN/OUT, USB host, and USB-C device. It is not an SDI/HDMI input encoder for other cameras.
Some Panasonic manual pages are shared with AJ-UPX360ED. This page is written for AG-CX350 operation; do not assume another CX-series camera has the same streaming table without checking its own manual.
Recommended workflow
Use AG-CX350 SRT CLIENT for public internet contribution. Create a Callaba SRT server in listener mode, open the chosen UDP port to the Callaba instance, then enter that host and port in the camera DEST URL. If you use Stream ID or encryption, type the same values on both sides.
Use AG-CX350 SRT LISTENER only when Callaba must call the camera. That means the venue side needs a reachable IP address, UDP port forwarding, firewall approval, and a tested NAT plan. For live events, this is usually more fragile than outbound SRT from the camera.
When not to use this setup
- If the switcher is beside the camera, SDI or HDMI may be simpler than cloud contribution. HDMI supports UHD output; SDI output is HD/SD on this model.
- If the only destination is YouTube or another public platform and you do not need cloud monitoring, routing, recording, or multiview, AG-CX350 RTMP or RTMPS may be enough.
- If you need LAN production with an NDI switcher, NDI|HX1 is a separate mode. It may require activation or an upgrade, and Panasonic notes that recording, streaming, and 4K output are not available in NDI|HX1 mode.
- If you require ST 2110 or bonded cellular contribution, plan an external converter, encoder, or bonded workflow. Do not treat AG-CX350 as a native ST 2110 or bonded transmitter.
Before you start
- Update or confirm the installed camera recorder software before relying on SRT or 4K streaming.
- Confirm the camera can reach the public internet through wired LAN, supported Wi-Fi module, or USB tethering.
- Choose a UDP port for Callaba SRT ingest and allow it through firewall/security group rules.
- Decide whether to use encryption. If yes, keep the passphrase controlled and identical on both sides.
- If handshake failures are hard to diagnose, confirm compatible SRT major versions from AG-CX350 firmware notes or Panasonic support, and from Callaba release or build information.
Create the Callaba ingest
In Callaba, create an SRT server for this camera and set it to listen on a UDP port. For the first test, use one camera per ingest and give the server a clear name such as ag-cx350-main. If you require Stream ID, create a simple value and paste it exactly into the camera later.
Success on the Callaba side looks like an active connection, incoming bitrate, video preview, audio meters, and stable uptime. If there is no connection, check the UDP port and whether the camera is still in menu or thumbnail conditions that prevent streaming from starting.
Configure the AG-CX350
On the camera, open the network streaming menu, set STREAMING PROTOCOL to SRT CLIENT, select an appropriate STREAMING FORMAT, then fill the SRT SETTING fields. Use H.264 for the first test because it is the safest downstream format for monitoring and browser playback paths. After the feed is stable, you can test H.265 where your full receive, recording, and playback chain supports it.
Set START to ON to begin transmission. For production, I recommend testing with the exact venue network, exact Stream ID, exact passphrase, and the same bitrate you plan to use during the event. A copied newline, trailing space, or changed capitalization in Stream ID or passphrase can break the SRT handshake.
Settings table
| Where | What to do / field to fill | First-test value | Why / check |
|---|---|---|---|
| Callaba SRT server | Create SRT server and choose UDP port | 5000 or your approved port | Port must be reachable from venue internet. |
| AG-CX350 NETWORK → STREAMING | [STREAMING PROTOCOL] | [SRT CLIENT] | Camera initiates the outbound SRT session. |
| AG-CX350 SRT SETTING | [DEST URL] | srt://your-callaba-host:5000 | Use Callaba public host/IP and UDP port. |
| AG-CX350 SRT SETTING | [STREAM ID] | ag-cx350-main | Must match Callaba if Stream ID is enforced; case and whitespace matter. |
| AG-CX350 SRT SETTING | [LATENCY] | 250–500 ms for internet test | Camera default is 120 ms; raise if RTT/loss is unstable. |
| AG-CX350 SRT SETTING | [ENCRYPTION] | OFF for first test, then AES128/192/256 if required | Match Callaba exactly before enabling production encryption. |
| AG-CX350 SRT SETTING | [PASSPHRASE] | Only when encryption is enabled | Case-sensitive and whitespace-sensitive. |
| AG-CX350 STREAMING | [STREAMING FORMAT] and [START] | 1080p30 around 6 Mb/s, then START ON | Confirm preview, audio, bitrate, packet loss, and recording before increasing quality. |
Monitoring
In Callaba, check preview first, then check numbers: incoming bitrate, connection uptime, RTT, packet loss, retransmits, and audio meters. The stream is ready for production only when the preview is stable and the stats remain stable for longer than your expected network variation.
If bitrate is present but preview is black, check the camera streaming format and codec. If audio meters are silent, check the AG-CX350 input selection, XLR line/mic/phantom settings, and whether the streaming format is sending AAC-LC audio.
Recording and playback
Callaba recording is independent of camera card recording. That is useful with AG-CX350 because Panasonic documents restrictions around 4K streaming: recording, thumbnail display, and playback cannot run at the same time during 4K streaming. For HD streaming, test the exact recording mode you plan to use because other camera functions can still affect streaming availability.
For playback, keep the first SRT test in H.264 unless your downstream players and decoders are known to handle HEVC. HEVC may be valid for the camera, but the full chain must support it.
Troubleshooting
| Symptom | Check in Callaba | Check on device | Likely fix |
|---|---|---|---|
| No connection | SRT server is running; UDP port is open; no port conflict. | STREAMING PROTOCOL is SRT CLIENT; DEST URL host and port are correct; START is ON. | Open UDP firewall/security group and retest from venue network. |
| Handshake fails | Stream ID and encryption settings match the camera. | STREAM ID, ENCRYPTION, and PASSPHRASE have no trailing spaces or capitalization changes. | Temporarily disable encryption, reconnect, then re-enable with copied values. |
| Connects but drops | RTT, packet loss, retransmits, and uptime. | LATENCY and bitrate; network link quality. | Raise latency to 500–1000 ms, reduce bitrate, or improve uplink. |
| 4K option unavailable | Ingest is ready for expected bitrate and codec. | NETWORK FUNC, FILE FORMAT, REC FORMAT, super slow, VFR, thumbnail/playback state. | Use a supported 4K streaming state; remember encrypted SRT is limited to 25 Mb/s or lower. |
| NDI workflow blocks streaming | Do not use the same Callaba SRT ingest for NDI mode directly. | NDI|HX1 mode and activation state. | Disable NDI|HX1 for direct SRT, or use a separate LAN bridge workflow. |
Official references
Useful sources for the operator or engineer preparing this workflow:
Vendor references
- Panasonic North America AG-CX350 product page
- Panasonic AG-CX350 specifications
- Panasonic AG-CX350 network menu
- Panasonic protocol setup and streaming start instructions
- Panasonic streaming and 4K streaming format notes
- Panasonic NDI|HX function notes
Protocol references
Callaba resources
FAQ
Does Panasonic AG-CX350 have native SRT?
Yes. Panasonic documents SRT CLIENT and SRT LISTENER in the AG-CX350 streaming menu. For Callaba Gateway, use SRT CLIENT from the camera to a Callaba listener as the normal path.
Should I use AG-CX350 SRT caller or AG-CX350 SRT listener?
Use SRT caller for most remote venues. Listener mode is useful only when Callaba or another receiver must call the camera, and that requires inbound UDP access to the camera network.
What should I enter for AG-CX350 SRT Stream ID?
In SRT CLIENT mode, enter the Stream ID required by the Callaba ingest. It is case-sensitive and whitespace-sensitive. In SRT LISTENER mode, Panasonic documents a fixed listener Stream ID value.
Can I use an AG-CX350 SRT passphrase with Callaba?
Yes. Set encryption on both sides and enter the same passphrase. For a first test, I usually connect without encryption, confirm the stream, then enable AES and passphrase matching.
Can AG-CX350 send RTMP or RTMPS instead of SRT?
Yes. The model documents RTMP and RTMPS. For 4K streaming, Panasonic notes RTMP(S) does not support H.265, and RTMPS is H.264 only.
Does AG-CX350 support NDI, ST 2110, or bonding for this workflow?
NDI|HX1 is documented but is a separate LAN mode with activation and operating restrictions. I found no official AG-CX350 evidence for ST 2110 or native bonded contribution, so do not plan those without external hardware.
Next steps
Build the first test at a conservative bitrate, watch Callaba stats for at least several minutes, then raise resolution or bitrate only after packet loss, retransmits, RTT, preview, and audio remain stable. Before the event, confirm firmware, SRT caller/listener direction, Stream ID, passphrase, codec, and 4K restrictions in the official Panasonic manual for the installed unit.
Try Callaba Gateway with Panasonic AG-CX350 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.