Panasonic AW-UE150 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 Panasonic AW-UE150 SRT setup, use the camera at the venue as an SRT source and receive it in Callaba Gateway in the cloud. Use this setup when AW-UE150 is at the venue and Callaba is the cloud SRT receiver for monitoring, recording, routing, multiview, or restreaming. The main path is direct SRT: AW-UE150 sends one contribution feed to Callaba, then Callaba handles downstream uses in parallel. Before the event, confirm that the installed firmware exposes SRT(H.264) or SRT(H.265) in the Video over IP streaming menu.
Quick answer
To use Panasonic AW-UE150 with SRT, set AW-UE150 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. Confirm firmware and the visible SRT menu first; if SRT is absent, update the camera or use the confirmed RTMP/RTMPS fallback.
The camera sends one SRT contribution feed into Callaba. After ingest, Callaba can preview, record, route, restream, and show the same source in multiview as parallel downstream uses, not as mandatory sequential steps.
- AW-UE150SRT Client(Caller)
- Callaba GatewaySRT Listener
- Preview
- Record
- Multiview
- Route
- Restream
What this setup does
This workflow answers the common AW-UE150 SRT to cloud question: the camera contributes the live program feed, and Callaba is the SRT receiver in the cloud. In normal internet contribution, AW-UE150 should be the SRT Client(Caller), because the camera opens the outbound UDP connection to the public Callaba endpoint. That avoids asking the venue network to accept inbound traffic to the camera.
Search terms such as Panasonic AW-UE150 SRT server or AW-UE150 SRT receiver can be confusing. The AW-UE150 operating instructions document both Client(Caller) and Listener modes, but in this guide Callaba is the practical server/listener side. Use AW-UE150 Listener only when you have a tested reason to reverse the roles.
What this model can and cannot do in this workflow
Confirmed for AW-UE150: Panasonic specifications and operating instructions list SRT, RTMP, RTMPS, RTSP, NDI HX version 2, MPEG2-TS over UDP, H.264, H.265/HEVC, JPEG/MJPEG, and AAC-LC audio for IP workflows. The camera also has 12G-SDI, 3G-SDI, monitor SDI, HDMI 2.0, LAN, RS-422, genlock, MIC/LINE audio input, DC 12 V power, and PoE++ power support. For the Callaba cloud workflow, no vendor receiver or vendor cloud layer is required.
Limitations to plan around: AW-UE150 is documented as NDI|HX2, not full-bandwidth NDI, not NDI|HX3, and not SMPTE ST 2110 in the AW-UE150 specifications reviewed for this guide. It is not a bonded cellular transmitter. If the event needs bonded WAN, use a separate bonding appliance or network path before the SRT feed reaches Callaba.
Firmware caveat: Panasonic firmware notes for AW-UE150 W/K P/E added SRT, H.265 FHD, and MPEG2-TS over UDP in Ver.2.62. Later notes added NDI|HX version 2 behavior and expanded SRT addressing, and Ver.3.18 made the previously optional NDI functionality standard for this model family. I would still confirm the exact suffix and firmware on the unit before copying settings. AW-UE150A is a close newer model with different NDI positioning, so do not assume every AW-UE150A detail applies to an AW-UE150W/K class unit.
Recommended workflow
Use direct SRT first. Create an SRT Listener in Callaba, note the public address and UDP port, then configure AW-UE150 as Client(Caller). Start with H.264 unless the job specifically needs H.265/HEVC and all downstream decoders, web players, and recorders in the chain can handle it. H.265 can save bandwidth, but compatibility is usually easier to prove with H.264 during the first test.
Only reverse the SRT roles when required. If AW-UE150 runs as Listener, the camera side must accept an inbound internet connection, so the venue may need a public IP address, UDP port forwarding, firewall rules, or a tested NAT traversal plan.
When not to use this setup
If the camera and switcher are on the same LAN or in the same room, SDI, HDMI, or NDI|HX2 may be simpler than a cloud SRT path. If the only destination is a public platform and you do not need cloud monitoring, recording, routing, or multiview, the AW-UE150 RTMP/RTMPS output may be enough. If SRT is missing from the installed firmware, update the camera first; for a temporary fallback, use RTMPS/RTMP to Callaba when it fits the event requirements, or bridge RTSP/NDI only when the production design needs that bridge.
Before you start
- Confirm the camera model suffix and firmware version.
- Confirm that SRT(H.264) or SRT(H.265) appears in the Video over IP streaming menu.
- Open the UDP port used by the Callaba SRT Listener.
- Decide H.264 or H.265 before rehearsal; use H.264 for the first compatibility test.
- Prepare Stream ID and passphrase values in plain text, without trailing spaces or copied line breaks.
Create the Callaba ingest
In Callaba, create an SRT server and set it to Listener mode. Choose the UDP port, enable a passphrase if the event requires encryption, and define a Stream ID if your ingest policy uses one. Save the public IP address or DNS name, the UDP port, the passphrase, and the Stream ID. These are the values you will enter in the AW-UE150 SRT settings.
Success in Callaba is simple: the SRT server shows a connected session, incoming bitrate, uptime, and transport statistics. If those stay at zero, the problem is still at connection, firewall, address, port, mode, or security matching level.
Configure AW-UE150
On the AW-UE150, open the Video over IP streaming area and choose SRT(H.264) or SRT(H.265). In the SRT settings, set Mode to Client(Caller), enter the Callaba destination IP address or domain name, and enter the UDP port from the Callaba SRT server. Set latency for the network rather than for wishful thinking; 250-500 ms is a practical first internet test, then lower it only after RTT, packet loss, and retransmits are stable.
If you enable encryption, match the AES mode and passphrase on both sides. Stream ID and passphrase are case-sensitive and whitespace-sensitive. A trailing space, copied newline, or changed capitalization can break the SRT handshake even when the address and port are correct.
Settings table
| Where | What to do / field to fill | First-test value | Why / check |
|---|---|---|---|
| Callaba | Create SRT server and choose UDP port | Listener on a known UDP port, for example 5000 | AW-UE150 calls out to this endpoint. |
| AW-UE150 Video over IP streaming | Streaming format | SRT(H.264) | Use H.264 first for broad preview and playback compatibility. |
| AW-UE150 SRT settings | Mode | Client(Caller) | Matches the Callaba Listener role. |
| AW-UE150 SRT settings | Destination IP address | Callaba public IP or DNS name | Use the reachable cloud address, not a private LAN address. |
| AW-UE150 SRT settings | Destination port number | Same UDP port as Callaba | Port mismatch gives no session in Callaba. |
| AW-UE150 SRT settings | Latency | 250-500 ms for first internet test | Raise it for unstable WAN links; lower after stats are clean. |
| AW-UE150 SRT settings | Encryption and passphrase | AES-128 or AES-256, or Off for a lab test | Must match Callaba exactly. |
| AW-UE150 SRT settings | Stream ID | Exact Callaba Stream ID if used | Case and whitespace must match. |
Monitoring
After the camera starts streaming, check Callaba before changing camera settings. Look for connection uptime, incoming bitrate, RTT, packet loss, retransmits, preview video, and audio meters. A stable SRT session with no usable picture usually points to codec, resolution, player compatibility, or audio/video format rather than firewall.
For a first H.264 test, start around 4-6 Mb/s for 1080p30 or 6-8 Mb/s for 1080p60 if the uplink supports it. These are operating starting points, not Panasonic specifications. Adjust bitrate to the available uplink and the production quality target.
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-UE150 ingest workflow.
Recording and playback
Once ingest is stable, use Callaba recording, preview, web playback, restreaming, routing, and multiview as parallel downstream options. Do not treat recording, preview, and restreaming as a required chain. They can all use the same received AW-UE150 source after SRT ingest is healthy.
Troubleshooting
| Symptom | Check in Callaba | Check on AW-UE150 | Likely fix |
|---|---|---|---|
| No connection | No session, no uptime, no bitrate | Mode, destination IP, destination port | Use Client(Caller) to Callaba Listener and open the UDP port. |
| Handshake fails with security enabled | Rejected or repeated short sessions | AES mode, passphrase, Stream ID | Match values exactly; remove hidden spaces and copied newlines. |
| Connects but drops | RTT, loss, retransmits, bitrate spikes | Latency and encoder bitrate | Raise latency, lower bitrate, or improve uplink stability. |
| Video appears but audio is missing | Preview and audio meters | MIC/LINE input and AAC-LC audio settings | Confirm input level, audio enable state, and cable/source. |
| SRT menu is missing | Use RTMPS/RTMP only as fallback | Firmware version and Video over IP menu | Update firmware or use confirmed RTMP/RTMPS until the unit exposes SRT. |
| H.265 does not play everywhere | Preview/player compatibility | SRT(H.265) selection | Switch to SRT(H.264) unless every downstream decoder supports HEVC. |
If a hard-to-diagnose handshake remains after fields match, confirm compatible SRT major versions from firmware release notes, vendor support information, and Callaba server build or support information.
Official references
Useful reader resources for this exact workflow:
Vendor references
- Panasonic Connect Asia AW-UE150 specifications
- Panasonic AW-UE150 operating instructions
- Panasonic AW-UE150 firmware Ver.2.62 note
- Panasonic AW-UE150 firmware Ver.2.94 note
- Panasonic AW-UE150 firmware Ver.3.18 note
Callaba resources
FAQ
Does Panasonic AW-UE150 support SRT?
Yes. Panasonic AW-UE150 documentation and firmware notes confirm SRT support, with firmware caveats on older units. Confirm that SRT(H.264) or SRT(H.265) is visible on the actual camera before the event.
Should AW-UE150 be SRT Caller or Listener?
For cloud contribution, use AW-UE150 as Client(Caller) and Callaba as Listener. AW-UE150 Listener mode is documented, but it usually requires inbound access to the venue camera side.
Is Callaba the AW-UE150 SRT receiver?
In this workflow, yes. The camera contributes the SRT feed and Callaba receives it, then provides monitoring, recording, routing, multiview, playback, or restreaming options.
Can I use AW-UE150 SRT Stream ID and passphrase?
Yes. The AW-UE150 SRT settings include Stream ID, encryption Off/AES-128/AES-256, and passphrase. Match the values exactly on both sides.
What if the SRT menu is missing on AW-UE150?
Check firmware first. If the event cannot wait for an update, use the confirmed RTMP/RTMPS output as the first fallback, or bridge RTSP/NDI|HX2 only when that is part of the production design.
Is AW-UE150 full-bandwidth NDI or ST 2110?
No for this AW-UE150 workflow. The model is documented as NDI|HX2. The checked AW-UE150 specifications do not list full-bandwidth NDI, NDI|HX3, or SMPTE ST 2110 for this exact model.
Next steps
- Create a Callaba SRT Listener and note the public address, UDP port, passphrase, and Stream ID.
- Set AW-UE150 to SRT(H.264) and Client(Caller) for the first rehearsal.
- Confirm connection uptime, bitrate, preview, packet loss, retransmits, and audio meters in Callaba.
- After the feed is stable, add recording, routing, restreaming, multiview, or API control as needed.
Try Callaba Gateway with Panasonic AW-UE150 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.