ApsaraVideo Live:SRT stream ingest

Prerequisites

You have configured and associated an ingest domain and a streaming domain. For more information, see Getting started with ApsaraVideo Live.

Enable SRT

1. Log on to the ApsaraVideo Live console.

2. In the left navigation pane, click Domain Names.

3. Find the streaming domain that you want to manage and click Domain Settings in the Actions column.

4. Click Streaming Management > Basic Settings.

5. Click the Stream Ingest Information tab. In the Ingest Protocol section, enable the SRT Protocol switch. The switch is off by default.

SRT stream ingest and playback

SRT stream ingest

After you enable SRT, you can obtain an SRT ingest URL from the URL Generators in the console or by concatenating URL components.

SRT ingest URLs use the following formats:

• Format 1 (Recommended)

  srt://{domain}:1105?streamid=#!::h={domain},r=/{AppName}/{StreamName}?auth_key={access token},m=publish (Recommended)

• Format 2

  srt://{domain}:1105?streamid=push://{domain}/{AppName}/{StreamName}?auth_key={access token}

Custom parameter encoding rules

When the SRT ingest URL contains custom parameters, you must URL-encode the special characters to avoid parsing conflicts. Example:

srt://{domain}:1105?streamid=#!::h={domain},r=/{AppName}/{StreamName}?auth_key%3D1807696811-21613-0fa3597df7f228fbfae37020de3782b70%26sprio%3D6,m=publish

SRT playback

When the SRT protocol is used for stream ingest, the supported playback protocols include RTMP, FLV, HLS, and RTS.

SRT playback is disabled by default. To use SRT playback, contact your account manager or submit a ticket. Alibaba Cloud then adds your specified streaming domain to the allowlist on the backend. You do not need to configure the server or bind an IP address.

After the streaming domain is added to the allowlist, SRT playback initially takes effect only on designated test nodes. Bind a test node and verify playback. After the verification passes, the configuration is deployed globally to all nodes.

The allowlist is processed independently for each streaming domain. Associated domains are not covered by automatic synchronization and therefore do not take effect automatically. Submit a separate request for every streaming domain that requires SRT playback.

If your business requires a lower latency of 200–400 ms, use the RTS (ARTC) protocol instead.

SRT playback URLs support two formats:

• srt://{domain}:1105?streamid=#!::h={domain},r=/{AppName}/{StreamName}?auth_key={access token},m=request

• srt://{domain}:1105?streamid=pull://{domain}/{AppName}/{StreamName}?auth_key={access token}

For more information about parameters and authentication, see Generate streaming URLs.