AJA SRT Gateway Workflows with Callaba
Written by Iurii Pakholkov
Founder of Callaba. Building cloud video tools for SRT, RTMP, WebRTC, NDI, live routing, monitoring, recording, and production workflows.
SRT Gateway vendor hub · Last updated: June 30, 2026
AJA SRT gateway workflows connect source-side jobs such as BRIDGE LIVE, HELO Plus, HELO RTMPS, production ingest, hardware contribution to a controlled live video operations layer. AJA workflows often sit at the production edge where a hardware encoder or converter needs a reliable handoff into cloud or private infrastructure. Callaba receives that live path and turns it into a monitored gateway workflow operators can route, record, preview, and recover.
Quick answer: where Callaba fits
Use the AJA device or platform for the source-side job, then use Callaba as the SRT listener, cloud gateway, private gateway, recorder, Multiview surface, playback layer, route controller, and API-controlled operations plane.
AJA guides
Choose the AJA SRT workflow you are building
Each guide focuses on one source or device family. Use this page as the parent hub when you are comparing which AJA workflow belongs in the live path.
Workflow pattern
AJA source to Callaba SRT gateway
Source side
AJA device or platformEncode, contribute, decode, or hand off the live feed from the production edge.
Callaba gateway
Receive, monitor, route, record, recoverUse SRT stats, preview, Multiview, output state, failover, and API control to operate the stream.
Outputs
Multiview, recording, playback, partner output, backup pathTurn one contribution boundary into a workflow the team can inspect and reuse.
Setup checklist for AJA SRT workflows
- Confirm the exact AJA model, firmware, role, output type, and SRT support before the event.
- Create a Callaba SRT server and choose the listener port, latency, stream ID, and passphrase policy.
- Open the required UDP port or port range on the firewall, AWS security group, or private network boundary.
- Configure the AJA source as SRT Caller for most cloud workflows, then point it to the Callaba host and port.
- Verify connection state, incoming bitrate, RTT, packet loss, preview, audio, and recording before relying on the feed.
- Only after ingest is stable, add Multiview, playback, routing, partner output, failover, or API automation.