media server logo

Sony PXW-Z280 SRT setup: send SRT to Callaba Gateway

Jun 03, 2026
Iurii Pakholkov

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

Use this setup when the Sony PXW-Z280 is at the venue and Callaba is the cloud SRT receiver for monitoring, recording, routing, multiview, or restreaming. The practical goal is simple: get one contribution feed out of the camera, confirm that Callaba is receiving stable video and audio, then decide which downstream outputs you need.

There is one important PXW-Z280 caveat. Sony public material for this exact model includes firmware/update evidence for SRT, while the operating instructions more explicitly document RTMP/RTMPS and MPEG-2 TS/UDP streaming. Before the event, confirm the installed firmware and that your unit exposes the SRT settings you plan to use.

Quick answer

To use Sony PXW-Z280 with SRT, first confirm the firmware version and that the camera exposes SRT caller/client settings. With SRT-capable firmware installed, send the PXW-Z280 feed to a Callaba SRT Listener. If the SRT menu is absent, update firmware first or use the confirmed RTMPS/RTMP fallback.

What this setup does

The PXW-Z280 acts as the field camera and encoder. Callaba acts as the public SRT receiver, so the venue does not need to host a public receiver unless you deliberately reverse the SRT direction. After Callaba receives the stream, the same source can be previewed, recorded, routed to another protocol, shown in multiview, or restreamed.

What this model can and cannot do in this workflow

For this exact model, treat the workflow as firmware-dependent. Use direct SRT when the camera firmware exposes SRT settings. If it does not, the documented direct IP fallback is RTMPS/RTMP on firmware V4.00 or later.

  • The PXW-Z280 is a 4K 1/2-type 3CMOS handheld camera with RJ-45 LAN and regional Wi-Fi options for network functions.
  • Physical outputs include 12G/3G/HD/SD-SDI, HDMI Type A, and a switchable monitor BNC, so an external SRT encoder is a practical backup path.
  • Sony documents RTMP/RTMPS setup with Destination URL, Stream Name, and RTMPS certificate handling in the Network > RTMP/RTMPS area.
  • Firmware V4.00 or later is required for RTMP/RTMPS streaming.
  • The manual also documents MPEG-2 TS/UDP streaming with destination address, destination port, audio channel, and format settings.
  • Network Client Mode and QoS workflows are Sony receiver/cloud workflows, not direct Callaba inputs.
  • HEVC/H.265 is documented for Sony QoS streaming added in firmware V2.00; do not assume that means HEVC over SRT or RTMPS to Callaba.
  • Public exact-model material does not clearly confirm NDI, RTSP, or ST 2110 for the PXW-Z280. Do not plan the PXW-Z280 as a native NDI source.
  • SRT Stream ID, passphrase, latency, and caller/listener field names were not clearly shown in the supplied public manual evidence, so confirm them on the installed firmware menu.

Sony support pages may show a regional suffix such as PXW-Z280V. This guide is for the PXW-Z280 support entry and does not assume features from other XDCAM handheld models.

When not to use this setup

  • If the camera and switcher are on the same table or same LAN, SDI or HDMI into the local switcher may be simpler.
  • If the only destination is a public platform and you do not need cloud monitoring, routing, or recording, the confirmed RTMPS/RTMP output may be enough.
  • If the job depends on NDI, choose a device that is officially documented as an NDI source. The PXW-Z280 is not confirmed for native NDI in the public exact-model sources used here.

Before you start

  • Check the camera firmware and confirm the visible SRT menu before booking the path.
  • Open the UDP port selected for the Callaba SRT server.
  • Decide whether Stream ID and passphrase are required. They are case-sensitive and whitespace-sensitive; a trailing space or copied newline can break the handshake.
  • For difficult handshakes, compare SRT compatibility through Sony firmware notes/support information and the Callaba server build or support information.
  • For RTMPS fallback, confirm the camera clock, certificate handling, destination URL, and stream name/key.

Create the Callaba ingest

In Callaba, create an SRT server and set it to listen on a known UDP port. For a first internet test, use a simple Stream ID policy or temporarily disable Stream ID until basic connectivity is proven. After the camera connects, confirm incoming bitrate, connection uptime, RTT, packet loss, retransmits, preview, and audio meters.

Configure the PXW-Z280

On the PXW-Z280, connect wired LAN when possible. In the SRT-capable firmware menu, choose the outgoing caller/client style mode if the firmware offers that terminology, then enter the Callaba public address, UDP port, Stream ID, passphrase, and latency values exactly as configured in Callaba. If those SRT fields are not present, do not hunt for hidden settings during show day; move to RTMPS/RTMP or use an external SRT encoder.

Settings table

WhereWhat to do / field to fillFirst-test valueWhy / check
PXW-Z280 system menuConfirm firmware and visible SRT streaming areaSRT-capable firmware installedUse direct SRT only when the menu exists.
Callaba SRT serverCreate server and choose UDP port10000 or another open UDP portCamera must reach the cloud listener.
Callaba SRT serverSet Stream ID policy if requiredSimple value with no spaces for first testMust match the camera exactly.
Callaba SRT serverSet passphrase/encryption if requiredOff for lab test, 16+ characters for eventMismatch prevents connection.
PXW-Z280 SRT streaming areaEnter destination host/addressCallaba public IP or DNS nameDo not include protocol prefixes unless the camera asks for a URL.
PXW-Z280 SRT streaming areaEnter destination UDP portSame port as CallabaCheck Callaba connection uptime.
PXW-Z280 encoder/format areaChoose a conservative video rate1080p30 at 4-6 Mb/s, 720p at 2.5-4 Mb/sStarting point only; adjust to uplink and packet loss.
PXW-Z280 Network > RTMP/RTMPSFallback: Destination URL, Stream Name, RTMPS certificateUse Callaba RTMP/RTMPS ingest detailsConfirmed fallback on V4.00+ when SRT is not available.

Monitoring

In Callaba, start with the receiver statistics, then preview. A healthy first test shows stable incoming bitrate, increasing uptime, reasonable RTT, low packet loss, and audio meters moving with the camera source. If the preview is delayed but statistics look clean, reduce latency only after retransmits remain stable.

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 Sony PXW-Z280 ingest workflow.

Callaba multiview and failover interface
Preview, multiview and failover Use the demo to check how incoming feeds, multiview monitoring and backup switching look in Callaba before building the live workflow. Open multiview demo

Recording and playback

Once the ingest is stable, enable recording or playback outputs as parallel downstream uses. Do not make recording the first diagnostic step. First prove SRT receive, video preview, and audio levels; then add recording, web playback, multiview, restreaming, or routing as needed.

Troubleshooting

SymptomCheck in CallabaCheck on PXW-Z280Likely fix
No connectionSRT server running, UDP port open, no firewall blockFirmware exposes SRT and destination port matchesOpen UDP, correct host/port, or update firmware.
Handshake failsStream ID and passphrase policyCopied Stream ID/passphrase exactlyRemove trailing spaces, newlines, and capitalization errors.
Unstable videoRTT, packet loss, retransmits, bitrateEncoder bitrate and uplink qualityRaise SRT latency to 250-500 ms for testing or lower bitrate.
No audioAudio meters and recorded file audioXLR input, channel selection, camera audio metersVerify source channel and stream audio settings.
RTMPS fallback failsRTMP/RTMPS ingest URL and stream key/nameClock, certificate, Destination URL, Stream NameLoad/reset certificate as Sony documents and correct the URL.
SRT menu missingNo incoming SRT sessionInstalled firmware and streaming menusUpdate firmware, use RTMPS/RTMP, or use SDI/HDMI to an SRT encoder.

Official references

Useful references for checking firmware, menus, and fallback behavior:

Vendor references

Protocol references

Callaba resources

FAQ

Can the Sony PXW-Z280 send SRT to Callaba?

Use direct SRT when the installed firmware exposes SRT settings. Because public exact-model material is inconsistent, I would confirm firmware and the visible menu before the event.

Should the PXW-Z280 be SRT Caller or Listener?

For cloud contribution, keep the camera as the outgoing sender when that mode is available and make Callaba the SRT Listener. Camera listener mode is harder on the public internet because the venue side must accept inbound UDP.

Where do I put the PXW-Z280 SRT Stream ID?

Use the SRT Stream ID field only if your camera firmware exposes it. Match Callaba exactly, including case and whitespace.

What if the SRT menu is missing on the PXW-Z280?

Update firmware if Sony provides SRT-capable firmware for your unit. If you cannot update, use the confirmed RTMPS/RTMP path or send SDI/HDMI into an external SRT encoder.

Does the PXW-Z280 support native NDI?

Not in the public exact-model sources used for this workflow. Do not plan the PXW-Z280 as a native NDI source.

Can I use HEVC/H.265 for this Callaba ingest?

Sony documents HEVC for its QoS workflow, not as a general direct SRT or RTMPS output in the manual evidence used here. Confirm codec output on the installed firmware and confirm downstream decoder support.

Next steps

Run a short private test before the production call time: create the Callaba SRT server, connect the PXW-Z280, watch statistics for at least a few minutes, check audio, record a sample, and only then add restreaming or routing outputs.

Try Callaba Gateway with Sony PXW-Z280 SRT workflow

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.