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.
Before you start
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.
Settings explained
These are the controls an operator needs to understand. Internal field names and implementation events are intentionally omitted.
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.
Safe first workflow
- 01
Verify the input feed with a direct receiver before creating the route.
- 02
Create the route and enter the exact input and destination connection details.
- 03
Start the destination listener before starting a route that calls it.
- 04
Start the route and verify both the source session and destination media.
Workflow examples
Relay an SRT venue feed to a remote production system
A verified SRT feed must be transported to another SRT listener.
How to build it
- 1
Test the venue source and remote listener separately.
- 2
Create the route with the endpoint mode and security values expected by each side.
- 3
Start the route and watch both connection states.
- 4
Confirm media at the remote listener before the route becomes production critical.
Verify the result
- The input source remains connected.
- The destination reports the expected stream and bitrate.
- Stopping the route does not delete its saved endpoint configuration.
Troubleshooting
The route starts but the destination is silent
Check- Verify listener/caller direction.
- Check destination firewall, passphrase and port.
- Test the source directly.
Correct the failing endpoint before changing route-wide transport values.