Panasonic AW-UE160 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
Panasonic AW-UE160 SRT setup is a direct camera-to-cloud workflow: send the PTZ camera output to a Callaba SRT Listener. Use this setup when AW-UE160 is at the venue and Callaba is the cloud SRT receiver for monitoring, recording, routing, multiview, or restreaming. Panasonic documents SRT, RTMP, RTMPS, RTSP/RTP, NDI High Bandwidth, NDI HX2, and MPEG2-TS over UDP for this model, so the main path is direct SRT with RTMPS/RTMP and local IP options as fallbacks.
Quick answer
To use Panasonic AW-UE160 with SRT, set AW-UE160 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. Before the event, confirm that the installed camera firmware exposes the expected SRT fields.
The Panasonic AW-UE160 sends one SRT contribution feed into Callaba. After ingest, preview, recording, routing, restreaming, and multiview are parallel downstream uses, not mandatory sequential steps.
- AW-UE160SRT Caller at venue
- Callaba GatewaySRT Listener in cloud
- Preview
- Record
- Route
- Restream
- Multiview
What this setup does
This workflow uses the AW-UE160 as the contribution encoder and Callaba as the internet-facing SRT receiver. The camera normally initiates the connection as SRT Client(Caller), which is easier at venues because the camera only needs outbound UDP access to the Callaba address and port.
After Callaba receives the feed, you can monitor it, record it, restream it, route it to other destinations, or use it in multiview. These are parallel choices after ingest. You do not have to record before routing, and you do not have to restream before monitoring.
What this model can and cannot do in this workflow
- Confirmed direct SRT: Panasonic AW-UE160 documentation lists SRT, and the operating instructions describe SRT Mode values for Client(Caller) and Listener.
- SRT fields to match: the manual describes destination URI and port, Stream ID, latency, encryption Off/AES-128/AES-256, and passphrase.
- Rendezvous is not confirmed: I would design the first test around Caller to Listener, then consider Listener mode only when the network plan supports inbound access to the camera.
- Codecs: Panasonic lists H.264/AVC, H.265/HEVC, JPEG/MJPEG, and AAC-LC audio for IP streaming. Use H.264 first when the downstream player or platform is uncertain.
- Frame-rate caveat: the operating instructions note that SRT H.264/H.265 UHD and non-UHD modes cannot be selected at 24/23.98 Hz frame frequency.
- Other IP paths: RTMP, RTMPS, RTSP/RTP, MPEG2-TS over UDP, NDI High Bandwidth, and NDI HX2 are listed for this model.
- Local outputs: the camera also has HDMI 2.0, 12G-SDI, 3G-SDI outputs, SFP+, XLR audio inputs, LAN, USB tethering support, DC input, and PoE++ power.
- ST 2110 is separate: do not assume SMPTE ST 2110 unless the AW-SFU60 software key is activated.
- No bonded aggregation claim: USB tethering support is useful for a mobile router, but it is not the same as native bonded cellular aggregation.
Recommended workflow
For an AW-UE160 SRT to cloud contribution, I normally start with this order: create a Callaba SRT Listener, set the camera to Client(Caller), send to the Callaba public address and UDP port, then verify bitrate, audio, packet loss, RTT, retransmits, and preview in Callaba.
Use AW-UE160 Listener mode only when you deliberately want Callaba to call the camera. That reverses the network problem: the venue or camera side must accept inbound UDP, usually with port forwarding, firewall rules, or a public address. That is why Caller mode is the practical default for most venue deployments.
When not to use this setup
If the camera and switcher are on the same LAN, local 12G-SDI, HDMI, or NDI may be simpler than sending SRT to the cloud. If the only target is a public platform and you do not need cloud monitoring, recording, routing, or multiview, AW-UE160 RTMP/RTMPS may be enough. If your facility is built around ST 2110, confirm the AW-SFU60 software key and the PTP/network design instead of treating SRT as the facility transport.
Before you start
- Update or confirm the installed AW-UE160 firmware; Panasonic lists System Version 2.45 on the current firmware page for this model.
- Confirm that the camera web interface exposes SRT settings before the show day.
- Choose H.264 for the first internet test unless every downstream decoder and player is configured for H.265/HEVC.
- Prepare the Callaba public hostname or IP, UDP port, optional Stream ID, and optional passphrase.
- Open outbound UDP from the venue network to Callaba. If using camera Listener mode, prepare inbound rules on the venue side.
Create the Callaba ingest
In Callaba, create an SRT server and set it to listen on a UDP port that is reachable from the venue. If you use Stream ID or a passphrase, copy the exact values for the camera. Treat Stream ID and passphrase as case-sensitive and whitespace-sensitive. A trailing space, copied newline, or changed capitalization can break the SRT handshake.
For the first test, keep the path simple: one AW-UE160, one Callaba SRT Listener, H.264 video, and AAC audio. Add recording, restreaming, or additional outputs after the incoming feed is stable.
Configure the AW-UE160
Open the AW-UE160 web interface and go to the streaming or SRT configuration area described in the Panasonic operating instructions. Set SRT Mode to Client(Caller), enter the Callaba address and port, then match Stream ID, latency, encryption, and passphrase if used. Start with 250 to 500 ms latency for an internet test, then lower it only after packet loss, RTT, and retransmits are stable.
Settings table
| Where | What to do / field to fill | First-test value | Why / check |
|---|---|---|---|
| Callaba SRT Servers | Create SRT server and choose UDP port | 9000 or your planned port | Camera must reach this public UDP port |
| Callaba SRT server authentication | Set Stream ID if required | Exact planned Stream ID | Copy exactly; no extra spaces or newline |
| AW-UE160 SRT settings | Mode | Client(Caller) | Camera initiates outbound connection to Callaba |
| AW-UE160 SRT destination | URI and Port | Callaba hostname/IP and UDP port | Must match the Callaba listener |
| AW-UE160 SRT settings | Stream ID | Same as Callaba, if used | Case-sensitive and whitespace-sensitive |
| AW-UE160 SRT settings | Latency | 250-500 ms | Increase for unstable internet links |
| AW-UE160 SRT settings | Encryption and Passphrase | Off for lab test, or AES-128/AES-256 with matching passphrase | Both sides must match exactly |
| AW-UE160 IP video settings | Codec | H.264 first; H.265 only when supported downstream | H.264 is the safer compatibility test |
Monitoring
When the AW-UE160 connects, Callaba should show incoming bitrate and connection uptime. Check preview, audio meters, packet loss, RTT, and retransmits before you add outputs. If video is present but audio is missing, check the camera audio input selection, XLR mic/line/phantom power settings, and the IP audio configuration in the camera.
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-UE160 ingest workflow.
Recording and playback
Once ingest is stable, enable recording or create playback outputs in Callaba as separate downstream tasks. For H.265/HEVC, confirm that every monitoring, playback, and decoder component in the chain is set up for H.265. If a browser player, platform, or hardware decoder is uncertain, switch the camera contribution to H.264 for the event.
Troubleshooting
| Symptom | Check in Callaba | Check on AW-UE160 | Likely fix |
|---|---|---|---|
| No connection | Listener is running on the expected UDP port | Mode is Client(Caller), address and port are correct | Open outbound UDP, correct hostname, test from another network |
| Connects then drops | RTT, packet loss, retransmits, uptime | SRT latency and bitrate | Raise latency, lower bitrate, stabilize uplink |
| Handshake fails with security enabled | Expected Stream ID and passphrase | Stream ID, AES mode, passphrase | Re-type values; remove trailing spaces and copied newlines |
| Video but no audio | Audio meters and received codec | XLR input, mic/line, phantom power, IP audio settings | Correct input level/source and confirm AAC-LC audio |
| Player cannot decode | Received codec and playback target | H.264/H.265 selection | Use H.264 unless all downstream components support H.265 |
| Hard-to-explain SRT failure | Server build/support information | Camera firmware and vendor support notes | Confirm compatible SRT major versions; use Caller/Listener before trying advanced network patterns |
Official references
These are useful reader resources for confirming exact model behavior and protocol details before a production day.
Vendor references
- Panasonic Global AW-UE160 specifications
- Panasonic AW-UE160 operating instructions
- Panasonic Connect Europe AW-UE160 product page
- Panasonic AW-UE160 firmware update page
Protocol references
Callaba resources
FAQ
Does Panasonic AW-UE160 support direct SRT to Callaba?
Yes. Panasonic lists SRT for AW-UE160, and the operating instructions describe SRT settings including Client(Caller), Listener, Stream ID, latency, encryption, and passphrase. Confirm the installed firmware and visible SRT menu on your exact unit before the event.
Should AW-UE160 be SRT Caller or Listener?
Use AW-UE160 as SRT Caller for the normal cloud workflow. Callaba listens in the cloud, and the camera initiates the outbound UDP connection. Listener mode is useful only when you have a tested inbound network path to the camera.
Does AW-UE160 support SRT Stream ID and passphrase?
Yes. Panasonic documents Stream ID, AES-128/AES-256 encryption, and passphrase for the AW-UE160 SRT settings. Stream ID and passphrase must match the Callaba side exactly.
Can I use H.265 over SRT from AW-UE160?
Yes, H.265/HEVC is listed for this camera, including SRT modes. Use it only when Callaba outputs and every decoder or player in the chain are configured for H.265. H.264 is safer for a first test.
Can AW-UE160 use NDI instead of SRT?
Yes, Panasonic lists NDI High Bandwidth and NDI HX2 for AW-UE160. Use NDI when the production stays on a controlled LAN. For public internet contribution to a cloud receiver, SRT is usually the cleaner path.
Is Panasonic AW-UE160 an SRT server?
In this workflow, no. The camera is the SRT Caller and Callaba is the SRT Listener or receiver. The camera also has Listener mode, but that is an advanced network design because the camera side must accept inbound traffic.
Next steps
Build the first test with one camera and one Callaba SRT Listener. After preview, audio, RTT, packet loss, and recording are stable, add the production outputs you need: multiview, restreaming, playback, routing, or API-controlled operations.
Try Callaba Gateway with Panasonic AW-UE160 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.