Stream to Wowza CDN from Wowza Streaming Engine

You can use the Stream Targets feature of Wowza Streaming Engine™ media server software to send a single stream or a group of transcoded renditions of a live stream directly to a Wowza CDN™ endpoint. This allows you to use the edge network to deliver the stream to viewers.

This article explains how to send a stream or a group of transcoded stream renditions to Wowza CDN over HLS.



Video tutorial: Configuring Wowza Streaming Engine to stream to Wowza CDN
Create a stream target to send the stream to Wowza CDN
Enable Stream Targets
Test the connection
More resources

Video tutorial: Configuring Wowza Streaming Engine to stream to Wowza CDN

Create a stream target to send the stream to Wowza CDN

After creating a Live application, configure it to send the stream to the Wowza CDN destination.
Note: Content delivery networks, including Wowza CDN, don't support adaptive bitrate streaming based on SMIL files. To send a set of adaptive bitrate renditions to a CDN endpoint, you must use the Transcoder feature to produce renditions with the same stream name prefix.
  1. In the contents panel, click Stream Targets and then click Add Stream Target.
  2. On the Add Stream Target page under Wowza Target Destinations, click Wowza CDN.
  3. On the Wowza CDN Configuration page, provide the following information:
    • Stream Target Name - A descriptive name for the target. It's good practice to include the destination, protocol, and rendition in the name, for example, myCDNTarget-720p. The name must be unique and can't contain less-than (<), greater-than (>), colon (:), quotation (' and "), forward slash (/), backslash (), pipe (|), question mark (?), asterisk (*), double-dot (..), or tilde (~) characters.
    • Streaming Bitrates - The number of bitrate renditions of the stream that will be sent to the destination. Select Multiple adaptive-bitrate streams to send a group of renditions for adaptive bitrate (ABR) playback or Single bitrate stream to send a single rendition of the stream.
    • Source Stream Name or Source Stream Name Prefix- For a single stream, enter the name of the incoming stream that you specified in Wowza Streaming Engine when you set up the video source (the Stream Name from the Sources (Live) setup). For an adaptive bitrate stream, enter the prefix appended to the beginning of each Encoding preset in the transcoder template used to create the group of renditions.
    • Destination Server - The destination entry point that the stream will be sent to. You can send the stream to the primary entry point, the backup entry point, or to both the primary and backup (redundant) entry points.
    • Email and Password - Enter your account credentials and click Sign In.
  4. Click Add this target.
  • This workflow creates a destination in Wowza Streaming Cloud using Wowza CDN on Akamai.
  • If you delete a Wowza CDN stream target using Wowza Streaming Engine Manager, it is also deleted on Wowza CDN. If you delete it directly from Wowza CDN, however, it will remain visible in Wowza Streaming Engine Manager but won't work.

Enable Stream Targets

Before you stream, you must enable the Stream Targets feature for the Wowza Streaming Engine application or the individual stream target you created.

If you don't see a checkmark next to Stream Targets in the contents panel of the application, click Stream Targets in the contents panel and then click Enable Stream Targets. When prompted, click Restart Now so your change takes effect. When Stream Targets is enabled, a checkmark appears next to Stream Targets in the contents panel and the Stream Targets page shows Status is Enabled.

If the Status of an individual stream target is Disabled, click the Enable icon for the stream in the Actions column.

When a stream target is enabled, its status on the Stream Targets page is one of the following:
  • Waiting. The target is enabled but isn't yet pushing any of the transcoded stream renditions to the Wowza CDN destination for one of the following reasons:
    • The original source stream isn't connected to the Wowza Streaming Engine input, so the transcoded renditions aren't being generated.
    • The target's configured Source Stream Name Prefix doesn't match the beginning of any of the transcoded stream names.
    • Wowza Streaming Engine hasn't completed initialization of the streaming connections to the Wowza CDN destination.
  • Active. Wowza Streaming Engine is successfully sending the stream or transcoded renditions to the Wowza CDN target.
  • Error. Wowza Streaming Engine unsuccessfully tried to retrieve the stream target configuration and initiate streaming to the Wowza CDN target. Errors may be due to an issue with the Wowza Streaming Cloud service, a general connectivity issue, or an invalid target configuration.

The status of each stream target updates automatically if your Wowza Streaming Engine application has fewer than 100 stream targets. If your application has more than 100 stream targets, you can click Refresh to update the status.

Test the connection 

Streams sent directly to Wowza CDN targets for distributed delivery are started and managed entirely from the Wowza Streaming Engine Manager. You can test the stream using the direct playback URLs.
  1. Start the stream in the H.264 camera or encoder that's sending the stream to your live application in Wowza Streaming Engine.

    The application ingests the live stream and sends it to a Wowza CDN endpoint.
  2. Verify that the stream is published by clicking Incoming Streams for your application and then clicking the stream name.

    The stream detail page displays the Status of the stream (Active) as well as details about connections, uptime, and throughput for the published stream.
  3. Get the playback URL by clicking Stream Targets in the contents panel for your application, clicking the stream target name, and then copying the Playback URL displayed on the stream target details page.
  4. Verify that the stream is playing by pasting the playback URL into an HLS player.
  5. Stop the stream in the source camera or encoder to end your test connection.

More resources