Panasonic AW-UE50 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 Panasonic AW-UE50 SRT setup, use the camera as an SRT Caller and send the feed to a Callaba SRT Listener in the cloud. Use this setup when AW-UE50 is at the venue and Callaba is the cloud SRT receiver for monitoring, recording, routing, multiview, or restreaming. The main path is direct SRT; I still recommend confirming that the installed firmware exposes the expected SRT streaming modes and fields before the event.
Quick answer
To use Panasonic AW-UE50 with SRT, set AW-UE50 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. If your unit does not show the SRT settings, update or confirm firmware before choosing a fallback path.
The Panasonic AW-UE50 sends one SRT contribution feed into Callaba. After ingest, Callaba can preview, record, route, restream, and feed multiview in parallel, not as mandatory sequential steps.
- AW-UE50SRT Client(Caller)
- Callaba GatewaySRT Listener
- Preview
- Record
- Route
- Restream
- Multiview
What this setup does
The AW-UE50 is a PTZ camera with direct IP streaming. In the normal cloud workflow, the camera originates the connection from the venue, while Callaba waits on a public UDP port as the SRT Listener. This avoids asking the camera to accept inbound internet traffic.
Operator searches such as AW-UE50 SRT caller, AW-UE50 SRT listener, AW-UE50 SRT receiver, AW-UE50 SRT to cloud, and Panasonic AW-UE50 SRT server often describe the same role decision. For cloud contribution, make the camera the caller and Callaba the receiver. The camera also documents Listener mode, but that is usually an advanced network design because the venue side must accept inbound UDP.
What this model can and cannot do in this workflow
Panasonic documentation for AW-UE50W/K confirms SRT, RTMP, RTMPS, RTSP, H.264/AVC, H.265/HEVC, JPEG/MJPEG, AAC-LC audio, and NDI HX2. The operating instructions describe SRT Client(Caller) and Listener roles, Stream ID, passphrase, AES encryption options, destination URI and port, and SRT H.264/H.265 streaming formats.
- The AW-UE50 has HDMI 1.4 output for 4K up to 29.97/25/24/23.98, and 3G-SDI output for HD formats.
- Official IP streaming resolutions are FHD/HD and smaller: 1920x1080, 1280x720, 640x360, and 320x180. Do not treat SRT/IP streaming as the 4K output path.
- SRT(H.264) and SRT(H.265) cannot be set when the frame frequency is 24 or 23.98 Hz in the Panasonic operating instructions.
- NDI is NDI HX2 for this model, not NDI High Bandwidth, NDI HX3, or SMPTE ST 2110.
- NDI HX2 may require current firmware or activation on older units; Panasonic notes standardization from firmware Ver. 2.17.
- The camera has a 3.5 mm MIC/LINE stereo input, LAN with PoE+, RS-422 control, USB Type-C UVC/UAC, HDMI, and 3G-SDI.
- RTMPS is listed for IPv4 support; Panasonic’s IPv6 protocol list includes RTMP and SRT but not RTMPS.
Close-variant note: this guide is for AW-UE50W/K. AW-UE40 is in the same family, but the AW-UE50 is the model in this pair with 3G-SDI output, so do not copy the cable plan without checking the exact unit.
Recommended workflow
Use direct SRT first: AW-UE50 Client(Caller) to Callaba Listener. Choose H.264 for the broadest monitoring and playback compatibility, or H.265 only when every downstream decoder, player, and restream destination supports it. Use RTMPS or RTMP as the first fallback if the event only needs platform-style contribution and the SRT menu is unavailable. Use RTSP or NDI HX2 through a bridge only when the production design needs a LAN capture layer or when direct cloud ingest is not practical.
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 SRT.
- If the only destination is YouTube or another public platform and you do not need cloud monitoring, recording, routing, or multiview, RTMPS may be enough.
- If the production is 24/23.98 Hz and you need the AW-UE50 at that frame frequency, do not plan SRT(H.264) or SRT(H.265) from the camera.
- If you need 4K contribution over IP, confirm a different path. AW-UE50 HDMI is the 4K output path, while documented IP streaming is FHD/HD.
Before you start
Check the installed firmware, confirm that the SRT streaming options are visible, and decide whether the camera will use H.264 or H.265. Prepare the Callaba public hostname or IP, UDP port, Stream ID if used, encryption setting, passphrase, and latency. Stream ID and passphrase are case-sensitive and whitespace-sensitive; a trailing space, copied newline, or changed capitalization can break the SRT handshake.
If difficult SRT handshake failures remain after the fields match, check firmware release notes or Panasonic support for device-side SRT version information, and compare it with the Callaba server build or support information for SRT major-version compatibility.
Create the Callaba ingest
In Callaba, create an SRT server and set it to listen on a UDP port that is open to the venue. If you require Stream ID or a passphrase, enter the exact values you will use on the camera. Keep the listener running before you start the AW-UE50 stream. Success on the Callaba side is visible as connection uptime, incoming bitrate, preview video, and audio activity.
Configure the AW-UE50
In the AW-UE50 web or camera streaming settings, select SRT(H.264) or SRT(H.265), set the connection mode to Client(Caller), enter the Callaba destination URI and UDP port, then match Stream ID, passphrase, encryption, and latency with the Callaba SRT server. Start with conservative bitrate and latency values, then tune after you can see stable RTT, packet loss, retransmits, video, and audio.
Use Listener mode only when the camera must wait for Callaba to call it. That design requires public reachability or tested port forwarding at the venue, so I do not use it as the default AW-UE50 SRT to cloud setup.
Settings table
| Where | What to do / field to fill | First-test value | Why / check |
|---|---|---|---|
| Callaba | Create SRT server and choose listener UDP port | One unused public UDP port | Callaba must be listening before the camera calls. |
| AW-UE50 | Connection mode | Client(Caller) | Best default for venue-to-cloud contribution. |
| AW-UE50 | Destination URI | Callaba public hostname or IP | Use the address reachable from the venue network. |
| AW-UE50 | Destination port | Same UDP port as Callaba | A port mismatch gives no ingest. |
| AW-UE50 and Callaba | Stream ID | Exact matching value, if used | Case and whitespace must match exactly. |
| AW-UE50 and Callaba | Passphrase and AES encryption | Match both sides | A different passphrase or encryption mode stops the handshake. |
| AW-UE50 | SRT latency | 250-500 ms for first internet test | Lower it only after RTT, loss, and retransmits are stable. |
| AW-UE50 | Streaming format | SRT(H.264) for first test | Use H.265 only when downstream monitoring and playback support HEVC. |
Monitoring
Once the camera connects, look at Callaba incoming bitrate, connection uptime, RTT, packet loss, retransmits, preview video, and audio meters. On the AW-UE50 side, check the streaming status and confirm that the selected format, frame frequency, and audio source match the event plan. For a first 1080p30 H.264 test, 4-6 Mb/s is a practical starting range; for 1080p60, start around 6-8 Mb/s if the uplink can sustain it.
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 Panasonic AW-UE50 ingest workflow.
Recording and playback
After ingest is stable, recording and playback are downstream choices in Callaba, not a different camera setup. You can record the received feed, provide browser preview, restream, route to another system, or add it to multiview in parallel. If you use H.265 from the AW-UE50, confirm that the intended player, decoder, or downstream platform supports HEVC before the show.
Troubleshooting
| Symptom | Check in Callaba | Check on device | Likely fix |
|---|---|---|---|
| No connection | Listener running, UDP port open, no firewall block | Client(Caller), destination URI, destination port | Correct address or port; test from the venue network. |
| Handshake fails | Stream ID, passphrase, encryption mode | Same fields, no trailing spaces or copied newline | Retype both values manually and restart the stream. |
| SRT menu missing | None until camera sends | Firmware version and visible streaming menu | Update or confirm firmware; use RTMPS/RTMP fallback if needed. |
| Connected but no stable picture | Incoming bitrate, preview, codec support | SRT(H.264/H.265), resolution, frame frequency | Use H.264, supported FHD/HD resolution, and avoid 24/23.98 Hz SRT. |
| Audio missing | Audio meters and received stream info | MIC/LINE input, audio enabled, AAC-LC settings | Confirm input level and audio routing before encoding. |
| Frequent drops | RTT, packet loss, retransmits, uptime | Bitrate and SRT latency | Increase latency, reduce bitrate, or improve the uplink. |
Official references
Useful reader resources for confirming fields, firmware, and protocol behavior:
Vendor references
- Panasonic AW-UE50/UE40/UE30 specifications
- Panasonic AW-UE50/AW-UE40 operating instructions
- Panasonic AW-UE50 FAQ
- Panasonic NDI upgrade support page
Protocol references
Callaba resources
FAQ
Should AW-UE50 be SRT Caller or Listener?
Use Client(Caller) for the normal AW-UE50 SRT to cloud workflow. Use Listener only if the venue network can accept inbound UDP to the camera.
Is Panasonic AW-UE50 an SRT server or receiver?
In this setup, no. Callaba is the cloud SRT receiver/listener. The AW-UE50 sends the contribution feed as the caller.
Does AW-UE50 support SRT Stream ID and passphrase?
Yes. Panasonic’s operating instructions describe Stream ID, passphrase, and AES encryption options for SRT. Match them exactly on both sides.
Can I use H.265 from AW-UE50 to Callaba?
Panasonic documents SRT(H.265). Use it only when your monitoring, playback, decoder, or downstream platform supports HEVC. H.264 is the safer first test.
Does AW-UE50 support NDI?
Yes, as NDI HX2, with firmware or activation caveats for older units. Do not plan this model as NDI High Bandwidth, NDI HX3, or ST 2110.
What if the SRT menu is missing on AW-UE50?
Confirm firmware and the visible streaming menu before the event. If SRT is still unavailable, use confirmed RTMPS/RTMP, or use RTSP/NDI HX2 through a bridge when that fits the production design.
Next steps
- Create the Callaba SRT listener and note the public address, UDP port, Stream ID, and passphrase.
- Configure AW-UE50 as Client(Caller), start with SRT(H.264), and confirm preview plus audio meters.
- After the feed is stable, add recording, multiview, routing, restreaming, or API automation as needed.
Try Callaba Gateway with Panasonic AW-UE50 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.