Use Cases

Real-world workflows powered by SipMX Gateway and SipMX Core. All gateway routing follows SIPMX-BCP-009-01.

Live Events

Dante® Console + NDI® Cameras + SRT™ Backhaul → RIST Contribution

A live event venue has a Dante-enabled mixing console for audio, NDI-compatible PTZ cameras for primary video, and SRT-capable bonded cellular encoders for roaming camera backhaul. The production feed needs to reach a remote broadcast center across the internet. SipMX Gateway ingests all three protocols and combines them into RIST MPTS streams — frame-accurate, encrypted, and error-corrected.

  • On-site: Dante-enabled console (AES67 mode) + NDI-compatible cameras + SRT backhaul encoders
  • Gateway: Mux mode — AES67 audio + NDI-compatible video + SRT camera feeds → RIST MPTS
  • Transport: RIST Main profile, AES-256, ARQ error correction
  • Remote: SipMX Core crosspoint, production switching, monitoring
ON-SITE VENUE Dante® Console NDI® Cameras SRT™ Backhaul Gateway Mux Mode RIST ~~~ Internet ~~~ REMOTE BROADCAST CENTER SipMX Core Crosspoint · Production Switching · BCP-008 Monitoring
Houses of Worship

Dante® Audio + IPMX Video → RIST + SRT™ Delivery

A main campus has Dante-enabled audio infrastructure and IPMX video for the sanctuary. Satellite campuses receive the service via RIST over the internet — but some remote locations already have SRT-based decoders. SipMX Gateway muxes the audio and video, outputs RIST for the NMOS-managed backbone, and also delivers SRT to legacy decoders that don't yet support RIST. SipMX Cloud re-streams for the online congregation.

  • Main campus: Dante-enabled DSP (AES67 mode) + IPMX cameras (JPEG XS)
  • Gateway: Mux mode — AES67 audio + IPMX video → RIST MPTS + SRT output to legacy decoders
  • Satellite (RIST): RIST decode, SipMX Core for local routing
  • Satellite (SRT): Existing SRT decoders receive the same feed via SRT output
  • Streaming: Cloud Stream to YouTube and Facebook
MAIN CAMPUS Dante® DSP IPMX Cameras Gateway Mux Mode RIST SRT ~~~ Internet ~~~ Satellite (RIST) SipMX Core · Decode Satellite (SRT) Legacy SRT Decoder Cloud Stream YouTube · Facebook · Online Congregation
Corporate AV

Dante® DSP + Conference Cameras → RIST + SRT™ to Remote Offices

A corporate headquarters has Dante-enabled DSP processors for conference rooms and NDI-compatible conference cameras. Remote offices need to join meetings with synchronized audio and video — some offices have RIST-capable decoders, others have existing SRT-based hardware. SipMX Gateway bridges the source protocols and delivers to both transport types over the corporate WAN.

  • HQ: Dante-enabled DSP (AES67 mode) + NDI-compatible conference cameras
  • Gateway: AES67 audio + NDI-compatible video → RIST + SRT dual output
  • Remote offices (new): RIST decode, local AV output, NMOS managed
  • Remote offices (existing): SRT decode on legacy decoders already deployed
  • Management: SipMX Core federation across all sites
HEADQUARTERS Dante® DSP AES67 NDI® Cams Conference Gateway Mux RIST (Corporate WAN) Remote Office A Decode · Display Remote Office B Decode · Display
REMI Production

NDI® + Dante® + SRT™ Backhaul On-Site → RIST to Remote Truck

A remote production (REMI) setup: NDI-compatible fixed cameras and Dante-enabled audio at the event venue, plus SRT-capable bonded cellular encoders on roaming cameras and reporter positions. SipMX Gateway at the venue ingests all three protocols and outputs RIST streams. At the remote end, SipMX Core provides frame-accurate synchronized switching with decoder sync — regardless of whether the feed came from NDI, Dante, or SRT.

  • Venue: NDI-compatible fixed cameras + Dante-enabled console (AES67) + SRT bonded cellular backhaul
  • Gateway: All three protocols → RIST, with mux mode for combined streams
  • Transport: RIST Main profile with decoder synchronization
  • Remote truck: SipMX Core with sync groups for frame-accurate switching
  • Result: <1ms sync across all feeds, regardless of source protocol or varying RTT
EVENT VENUE NDI 1 NDI 2 Dante® Console (AES67) SRT™ Bonded Cellular Gateway Mux + Sync RIST RIST ~~~ Internet ~~~ REMOTE PRODUCTION TRUCK SipMX Core + Decoder Sync Sync Group <1ms Production SW
Cloud Ingest

SRT™ Encoders from Multiple Locations → Centralized RIST Production

A news organization has field reporters and remote bureaus worldwide, each equipped with SRT-capable encoders (bonded cellular backpacks, satellite uplinks, or broadband-connected rack encoders). These SRT streams push to a cloud-hosted SipMX Gateway cluster that translates every feed to RIST. At the production center, SipMX Core discovers all ingested feeds automatically via NMOS, routes them to production switchers, monitors receiver health, and synchronizes feeds from different time zones with decoder sync — all from a single crosspoint.

  • Field reporters: SRT-capable bonded cellular encoders (4G/5G backpacks)
  • Remote bureaus: SRT rack encoders over broadband or satellite
  • Cloud Gateway: SRT ingest (caller + listener modes) → RIST, NMOS IS-04/05 managed
  • Transport: RIST Main profile with AES-256 encryption and decoder synchronization
  • Production center: SipMX Core crosspoint, frame-accurate sync groups, BCP-008 monitoring
  • Benefit: Field crews use familiar SRT equipment — production gains NMOS routing and monitoring
WORLDWIDE SRT Reporter A 4G Backpack SRT Reporter B Satellite SRT Bureau Rack Encoder Cloud Gateway SRT → RIST Caller + Listener NMOS Node RIST AES-256 Sync ~~~ Internet ~~~ PRODUCTION CENTER SipMX Core Decoder Sync Crosspoint BCP-008 <1ms
SRT Migration

Existing SRT™ Infrastructure → NMOS-Managed Without Rip-and-Replace

A broadcaster has an established SRT-based contribution workflow — SRT encoders at venues, SRT decoders at the facility, point-to-point streams configured manually with IP addresses. They want centralized management, receiver monitoring, and multi-site routing without replacing their existing SRT equipment. SipMX Gateway sits at each end: it receives SRT from existing encoders, provides NMOS discovery and routing via SipMX Core, and delivers SRT to existing decoders on the output side. The SRT devices don't change — they gain an NMOS management layer around them.

  • Existing: SRT encoders and decoders deployed across multiple venues
  • Gateway (ingest): Receives SRT from existing encoders, registers as NMOS senders
  • Core: Centralized crosspoint routing, BCP-008 monitoring, IS-05 connection management
  • Gateway (output): Delivers SRT to existing decoders, or RIST for new infrastructure
  • Migration path: Over time, replace SRT segments with RIST — the NMOS control layer stays the same
VENUE SRT Encoder Existing Device Gateway SRT In · NMOS Tx SipMX Core (NMOS Control Plane) Crosspoint · IS-05 Routing · BCP-008 · Federation FACILITY Gateway NMOS Rx · SRT Out SRT Decoder Existing Device

See your workflow here?

Let's discuss how SipMX Gateway fits your specific environment.

Request Gateway Access Gateway Details

NDI® is a registered trademark of Vizrt Group. Dante® is a registered trademark of Audinate Pty Ltd. SRT™ is a trademark of Haivision Systems Inc. All other trademarks are the property of their respective owners. SipMX is not affiliated with, endorsed by, or sponsored by Vizrt Group, Audinate Pty Ltd, or Haivision Systems Inc. References to third-party products are for informational and interoperability purposes only.