media server logo

Choose a Canon model for your SRT Gateway workflow

Jun 30, 2026
Iurii Pakholkov, founder of 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: July 22, 2026

Choose the exact Canon model before you configure the gateway. This hub owns Canon vendor and model selection; each linked model guide owns only that device's setup procedure. After confirming the production model, firmware, and supported SRT role, use Callaba SRT Server as the product layer for receiving the contribution feed, monitoring connection health, previewing it, recording it, routing it, and adding it to Multiview.

Quick answer: where Callaba fits

Use the Canon 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.

Canon guides

Choose the exact Canon model guide

This hub owns vendor and model selection. Each linked leaf owns only its exact-model setup procedure, so confirm the production unit and firmware before following device-specific fields.

Product next step

Run the selected Canon workflow through Callaba SRT Server

After you choose the exact model guide and confirm its supported SRT role, continue to the Callaba product page to plan monitored ingest, preview, recording, routing, and Multiview. The model guides remain the owners of device-specific setup steps.

Explore Callaba SRT Server

Cloud and self-hosted deployment choices stay secondary to this product decision and follow after the article content.

Workflow pattern

Canon source to Callaba SRT gateway

Source side

Canon device or platform

Encode, contribute, decode, or hand off the live feed from the production edge.

Callaba gateway

Receive, monitor, route, record, recover

Use SRT stats, preview, Multiview, output state, failover, and API control to operate the stream.

Outputs

Multiview, recording, playback, partner output, backup path

Turn one contribution boundary into a workflow the team can inspect and reuse.

Setup checklist for Canon SRT workflows

  1. Confirm the exact Canon model, firmware, role, output type, and SRT support before the event.
  2. Create a Callaba SRT server and choose the listener port, latency, stream ID, and passphrase policy.
  3. Open the required UDP port or port range on the firewall, AWS security group, or private network boundary.
  4. Configure the Canon source as SRT Caller for most cloud workflows, then point it to the Callaba host and port.
  5. Verify connection state, incoming bitrate, RTT, packet loss, preview, audio, and recording before relying on the feed.
  6. Only after ingest is stable, add Multiview, playback, routing, partner output, failover, or API automation.
Typical live workflow

Canon contribution through Callaba SRT Gateway

A compatible Canon source sends a live SRT contribution feed to Callaba, where operators can monitor the connection and route the stream to configured destinations.

Contribution source

  • Canon hardware or source

    A compatible camera, encoder, or field unit sends the live contribution feed.

    SRT source
Callaba SRT Gateway

Receives the SRT feed and provides routing and operational visibility.

Ingest and control

Monitoring and delivery

  • Stream monitoring

    Operators inspect the incoming stream and connection status.

  • Configured delivery

    Callaba routes the feed to the selected production or distribution destination.

Exact SRT modes, stream settings, and available outputs depend on the source device and the configured destination.

Choose where to run Callaba SRT Gateway

Continue with an AWS deployment or review the self-hosted path for your infrastructure.