Panasonic AW-UE160 contribution workflow
Bring a production PTZ camera into Callaba without flattening its broadcast options
The AW-UE160 can send an SRT contribution directly from the camera while retaining the remote operation expected from a professional PTZ system. It is a useful fit for sports positions, council chambers, studios, performance venues, and remote-production sites where adding a separate encoder would increase cabling and failure points. The important design choice is not simply “turn on streaming.” It is deciding which camera output serves the wide-area contribution, which stays inside the facility, and how the receiving operator proves the result.
Start with one outbound SRT contribution
In the common cloud workflow, configure the AW-UE160 as SRT Caller and Callaba as Listener. The camera initiates the connection to a prepared Callaba address and UDP port. Panasonic also documents SRT Listener operation, so the roles can be reversed on a controlled network where Callaba is intentionally allowed to reach the camera.
Caller and Listener describe connection establishment, not picture direction. In both arrangements the AW-UE160 remains the source and Callaba receives the stream. Choose the roles from the real firewall and NAT boundary, then write that decision into the production runbook.
The animation shows camera movement and a changing receiver meter only to explain operational flow; it is not live telemetry. Reduced-motion preferences stop all movement without removing information.
Choose the output for the network you actually have
The AW-UE160 supports both H.264 and H.265 for SRT. H.264 is the conservative choice when interoperability across decoders, browser-delivery pipelines, and production tools matters most. H.265 can reduce the required bitrate for comparable quality, but every receiving, recording, transcoding, and delivery stage must support the selected profile. Codec capability on the camera is not proof of end-to-end compatibility.
For production inside a managed facility, the camera also supports NDI High Bandwidth and NDI HX2. These are separate local IP production paths, not SRT recovery modes. Native SMPTE ST 2110 operation requires the separately purchased AW-SFU60 software key. A project specification that calls for ST 2110 should include that license and the facility timing/network design rather than assuming the base camera provides an enabled ST 2110 endpoint.
Projects running at 23.98 or 24 Hz need an extra compatibility check. Panasonic documents SRT operating restrictions tied to these system frequencies. Confirm the exact mode and codec combination in the current operating instructions before the event; do not copy a profile proven at 25, 29.97, 50, or 59.94 Hz and assume it behaves identically.
Write down the camera-to-server contract
| Control | Camera decision | Receiving decision | Production check |
|---|---|---|---|
| SRT role | Caller for a normal outbound venue path, or Listener on an intentionally reachable camera network | Complementary Listener or Caller | Roles are opposite and match the firewall design. |
| Address and port | Callaba destination in Caller mode, or the camera listening interface in Listener mode | A running endpoint with a unique approved UDP port | DNS, routing, NAT, and security rules point to the same system. |
| Stream ID | Exact agreed value when identity or routing policy uses it | The same accepted publisher identity | Case, separators, and characters match exactly. |
| Codec | H.264 or H.265 selected for the whole media chain | Decode, record, and route capability for that profile | Representative motion and audio are decoded successfully. |
| Encryption | AES-128 or AES-256 with an approved passphrase | Matching algorithm and secret | Secrets are stored securely and excluded from public screenshots. |
| Latency | Panasonic's factory value is 120 ms; change it only against measured route conditions | A compatible receiving and recovery policy | Jitter recovery and total glass-to-glass delay meet the production target. |
| System frequency | The actual project frequency, with the 23.98/24 Hz caveat checked | All downstream tools accept the resulting stream | No format conversion is being hidden during the first proof. |
The 120 ms factory value is a known starting state, not a promise that every WAN path will recover correctly at 120 ms. Measure the route and validate it under representative load. A longer value may tolerate more jitter at the cost of delay; no latency setting can repair sustained congestion or missing capacity.
Commission one camera before building the wall
- Freeze the project format. Record system frequency, raster, codec, audio, colour requirements, and the installed AW-UE160 software. If the event uses 23.98/24 Hz, resolve the documented SRT limitations now.
- Prove camera operation. Test pan, tilt, zoom, focus, exposure, and local output. Separate a camera-control problem from a transport problem before the remote team joins.
- Create Callaba's SRT endpoint. Start a Listener on a unique host and UDP port for the normal outbound workflow. Apply source restrictions and Stream ID policy appropriate to the production.
- Configure the camera. Select SRT Caller, enter the destination, choose the approved H.264 or H.265 profile, and enter the exact Stream ID and AES settings. Keep the factory latency unless route evidence gives a reason to change it.
- Confirm both session and media. Check that Callaba sees the expected publisher and sustained traffic, then decode the camera in Multiview. Inspect a moving PTZ shot and the intended audio.
- Attach one downstream operation. Make a short recording or route the feed to one controlled output. Verify the result before adding other cameras, destinations, or recovery rules.
Design around real PTZ production jobs
Sports isolation camera
Use the UE160 for a remote angle at a goal, court, commentary position, or mixed zone. Give the feed a role-based Stream ID so an operator can distinguish the camera quickly, then rehearse a full-rate pan rather than validating only a static wide shot.
Council chamber or auditorium
Keep PTZ control and local production on the managed facility network while sending a protected SRT contribution to a central service. Callaba can provide the remote picture proof and an event recording without turning the public WAN into the camera-control plane.
Remote studio
Use H.264 when the signal must pass through a broad set of tools, or approve H.265 only after every downstream stage is tested. A short engineering test should include presenter motion, graphics, audio, and the planned recording path.
ST 2110 facility with remote contribution
Keep the roles explicit: licensed AW-SFU60 enables the facility's ST 2110 side, while SRT can serve the WAN contribution. They solve different network problems and should meet at a documented routing boundary rather than being described as interchangeable.
Acceptance test for the production team
- Move the camera through the fastest pan and most detailed scene expected during the event; inspect the decoded Callaba picture.
- Verify the selected audio, lip-sync, system frequency, codec, and frame continuity.
- Watch the incoming session long enough to include normal venue network activity, not just an empty rehearsal network.
- Create and play back a short recording. Confirm duration, audio, resolution, frame rate, and expected codec handling.
- Disconnect the contribution network, document what the camera and Callaba each report, then restore the path and measure operational recovery.
- If an alternate camera, route, or local output is part of the show, exercise the actual operator procedure and verify every destination after the change.
Troubleshooting by symptom
Callaba never sees the camera
Confirm complementary Caller/Listener roles, the running endpoint, destination host, and UDP port. Trace routing and firewall policy from the camera network itself. A successful browser login from another VLAN does not prove the SRT path.
The endpoint is reachable but rejects the stream
Compare Stream ID, AES-128/AES-256 selection, and passphrase exactly. Retype the values at both ends if they passed through formatted email or a shared document.
A connection exists but media does not decode
Check system frequency, H.264/H.265 profile, and the complete downstream codec chain. For 23.98/24 Hz, return to Panasonic's current compatibility table before changing unrelated network values.
Fast PTZ movement reveals breakup
Test the planned media profile with representative motion, then compare network capacity, loss, jitter, and latency. Do not diagnose a motion-heavy encode with a static colour chart or an idle venue network.
NDI works but remote SRT does not
NDI proves a local IP media path; it does not validate the WAN address, SRT role, firewall, Stream ID, or encryption contract. Keep the local and contribution tests separate.
ST 2110 is missing from the expected workflow
Confirm that the AW-SFU60 software key is purchased, installed, and supported by the deployed camera software. Then validate PTP and the facility network independently from SRT contribution.
Official Panasonic references
Use the documentation that matches the installed camera software and market. Panasonic's official AW-UE160 specifications provide the protocol, codec, NDI, and output baseline. The official AW-UE160 operating instructions contain the current menu behaviour, SRT modes, security controls, latency settings, system-frequency restrictions, and AW-SFU60 requirements. Recheck those sources before changing an event profile instead of relying on a remembered firmware screen.
Make the first AW-UE160 path observable end to end
Receive one camera, prove moving video and audio in Multiview, make a recording, and rehearse the network interruption. That test gives the team a trustworthy baseline before additional PTZ cameras, routes, or facility protocols are introduced.
Explore Callaba SRT Server