Overview
edge stream push lets you distribute a live stream to multiple platforms simultaneously, which is useful for geographically dispersed stream sources or for managing many live streams.
Use cases
Third-party platform integration: To distribute a stream to a third-party platform, use the edge stream push feature.
Stream push between domains: You can use edge stream push to distribute a stream across different playback domains you own. For example, you can push a stream that is originally available on playback domain A to also be available on playback domain B.
If your stream push workflow requires video processing such as transcoding, recording, or snapshotting, use the center stream push feature instead. For more information, see Center stream push configuration.
Usage notes
Changes to an edge stream push configuration, such as enabling, modifying, or deleting it, affect only new stream pushes. For example, if you start a stream push before a configuration is enabled, that specific stream will not be pushed to the configured destinations.
Billing
Enabling edge stream push incurs fees. For more information about the billing rules, see Edge stream push fees.
Configure edge stream push
-
Log on to the ApsaraVideo Live console.
-
In the left-side navigation pane, click Domain Names. The Domain Management page appears.
-
Find the target ingest domain and click Domain Configuration in the Actions column. On the domain configuration page, click in the navigation pane on the left.
The Edge Stream Push switch is disabled by default. Enabling this feature pushes live streams to the configured addresses and incurs charges based on the daily peak bandwidth of the stream push.
-
Turn on the Edge Stream Push Configuration switch to add a configuration.
Parameter
Description
Edge stream push type
-
Push to Specified Destinations: Pushes the stream to a specified list of destination domains.
-
Obtain Destinations from HTTPDNS: Retrieves destination addresses by calling a specified HTTPDNS API endpoint.
Push to Specified Destinations
AppName
The application name (AppName) of the source live stream. Supports regular expressions, excluding
^and$. For example,test[1,2,3]matches the AppNamestest1,test2, andtest3.StreamName
The stream name (StreamName) of the source live stream. Supports regular expressions, excluding
^and$. For example,test[1,2,3]matches the StreamNamestest1,test2, andtest3.Edge stream push address
A list of destination domains. Separate multiple domains with commas (,). Example:
example1.aliyundoc.com,example2.aliyundoc.com
Pass through ingest parameters
Specifies whether to pass through parameters from the ingest URL.
Obtain Destinations from HTTPDNS
HTTPDNS API
Access the HTTPDNS interface of the target stream push address. Example:
http://example.aliyundoc.com/?host={<host>}&app={<app>}&name={<name>}{<_ali_user_args>}. When you access the HTTPDNS interface, the following parameters are replaced with the information from the stream push URL:-
{<host>}: The ingest domain.
-
{<app>}: The AppName of the live stream.
-
{<name>}: The StreamName of the live stream.
-
{<_ali_user_args>}: The user-defined parameters from the ingest URL.
Return values:
-
200: Success. The destination domains are retrieved from the returned JSON object. If multiple domains are returned, the source stream is pushed to all of them. For a sample JSON response, see the example below.
-
403: Indicates failure. The stream is not pushed.
Pass through ingest parameters
Specifies whether to pass through parameters from the ingest URL.
JSON example:
{ "cdn_types": [ { "name": "cdnA", "upstream_url": "rtmp://example1.aliyundoc.com/live/testedge****" }, { "name": "cdnB", "upstream_url": "rtmp://example2.aliyundoc.com/live/testedge****" } ] }Parameter
Description
name
A unique, customizable name for the CDN.
upstream_url
The destination URL for the stream push.
-
-
Click OK to save the edge stream push configuration.