Articles on: Using Quortex Link

Scheduling my stream delivery

While many contents need to be delivered on a 24/7 basis, other contents (for example, sport games) are typically only delivered during events that last a few hours or a few days.

Quortex Link allows to schedule the distribution of such content only for the duration of the events. This allows to save on cost, or to restrict content availability to the chosen time ranges.

Link Scheduler is available as part of the Premium Plan. Please contact us if you need to activate it for your organization.

Creating a scheduled event

Within a pool, scheduled events can be used to manage the distribution of content from inputs to outputs from the pool.

Creating a scheduled event

A scheduled event applies to one or several inputs of a given pool. At defined times, link from event inputs to their outputs will be set to the required state : at start time, inputs and outputs are enabled, link are created, at end time, link are removed and inputs and outputs are disabled.

You can always manually enable or disable the link from an input to its output, for example to perform some tests, or to adapt to last-minute changes.

Disable or Enable SRT Links in a manual way

If at event start time, link is already enabled for an input, no change will be performed, as content is already streamed.

If an output is manually linked to an input during an event, this output will not be disabled at the end of the event. Input will also remain active as it will be considered as being used by the scheduler.

Managing a scheduled event

A scheduled event is either _scheduled _(start time is in the future), _started _(start time is in the past, end time is in the future), or _finished _(end time is in the past).

The temporal nature of scheduled events adds some restriction on modification possibilities. For example, the start time of a _started _event can't be modified, but its end time can be extended.

List of scheduled events

Scheduled event and connections

Scheduled event allow to manage the delivery of content from inputs to outputs.

On outputs, the connection should be pre-configured and tested with receivers before the event starts. To maximize flexibility, outputs are released at the end of each event, so they can be reused by another event with a different input. As a result, the output's IP address may change between events.

No content will be streamed during a scheduled event if connections are not properly established.

Outputs connectivity

When the scheduler is used, links between inputs and outputs are created at event start and released at event end. This has important implications for how you configure your outputs:

SRT Caller outputs: the source IP can change from one event to the next. If the receiver requires CIDR-based whitelisting, the whitelist must be updated at the start of each event. Otherwise, the receiver should be configured to accept connections without a fixed-IP requirement.
SRT Listener outputs are not recommended. Since the URL/IP changes between events, it cannot be reliably shared with receivers in advance.

For scheduled events, we therefore recommend SRT Caller outputs, with the receiver either accepting connections without fixed-IP filtering, or prepared to update its CIDR whitelist at each event start.

Updated on: 04/05/2026

Was this article helpful?

Thank you!