media server logo
Guia do produto

Rotas SRT

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

Onde encontrar no CallabaStreaming servers → SRT routes
O que este módulo faz

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 começar

  • 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.

Configurações explicadas

Explicamos apenas os controles úteis ao operador. Nomes internos e eventos de implementação são omitidos de propósito.

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.

Primeiro fluxo 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.

Exemplos de fluxo

Use quando

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 do fluxo: Relay an SRT venue feed to a remote production system

Como construir

  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.

Validar o resultado

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

Solução de problemas

The route starts but the destination is silent

Verifique
  • Verify listener/caller direction.
  • Check destination firewall, passphrase and port.
  • Test the source directly.
Depois faça isto

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