media server logo
Guía del producto

Rutas SRT

Move an existing SRT or UDP contribution feed to a defined SRT destination without combining routing with unrelated processing.

Dónde encontrarlo en CallabaStreaming servers → SRT routes
Qué hace este módulo

An SRT route is a transport pipeline. Use it when the media should remain a transport feed; use Restreaming when you also need protocol conversion, transcoding, audio selection or overlays.

Antes de empezar

  • A reachable source URL and destination listener.

  • Known caller/listener mode, port, latency and passphrase requirements at both ends.

  • A maintenance window for changing a live route.

Ajustes explicados

Se explican los controles que necesita el operador. Los nombres internos y eventos de implementación se omiten intencionadamente.

Route identity

Control the lifecycle of the pipeline.

Name

Operator-facing route name including source and destination context.

Active

Start the route after its endpoints are valid.

Source and destination

Describe both ends of the transport path.

Input

Existing SRT or supported UDP contribution endpoint.

Output

SRT destination that will receive the routed media.

Connection options

Mode, latency, passphrase and transport values required by each endpoint.

Primer flujo seguro

  1. 01

    Verify the input feed with a direct receiver before creating the route.

  2. 02

    Create the route and enter the exact input and destination connection details.

  3. 03

    Start the destination listener before starting a route that calls it.

  4. 04

    Start the route and verify both the source session and destination media.

Ejemplos de flujo

Úsalo cuando

Relay an SRT venue feed to a remote production system

A verified SRT feed must be transported to another SRT listener.

Venue encoderSRT contribution
Callaba routeControlled relay
Remote listenerSRT destination
Confidence monitorPlayback
Diagrama animado del flujo: Relay an SRT venue feed to a remote production system

Cómo construirlo

  1. 1

    Test the venue source and remote listener separately.

  2. 2

    Create the route with the endpoint mode and security values expected by each side.

  3. 3

    Start the route and watch both connection states.

  4. 4

    Confirm media at the remote listener before the route becomes production critical.

Verificar el resultado

  • The input source remains connected.
  • The destination reports the expected stream and bitrate.
  • Stopping the route does not delete its saved endpoint configuration.

Solución de problemas

The route starts but the destination is silent

Comprobar
  • Verify listener/caller direction.
  • Check destination firewall, passphrase and port.
  • Test the source directly.
Después, haz esto

Correct the failing endpoint before changing route-wide transport values.