Skip to main content

Search

Wowza Support

The solution your start with, the partner you scale with.

Why are my Streams Freezing with a Fastly CDN "Pull Stream Target"?

  • Updated

Creating a Fastly CDN Stream Target to pull from a Wowza Streaming Engine source/origin requires a Live HTTP Origin application in Wowza Streaming Engine configuration. Below are the steps on how to convert your current "live" applications to "live HTTP Origin" for the Fastly CDN "pull" workflow. 

You can create a new application or modify your current live application to convert it to a Live HTTP Origin application by manually editing the Application.xml file in [Wowza Engine install directory]/conf/[application name]/ directory.

  1. Change AppType from live to LiveHTTPOrigin <AppType>LiveHTTPOrigin</AppType>
  2. To convert a live application to LiveHTTPOrigin add a set of properties for the LiveHTTPOrigin:
<LiveStreamPacketizer>
 <Properties>
  <Property>
   <Name>httpRandomizeMediaName</Name>
   <Value>true</Value>
   <Type>Boolean</Type>
  </Property>
 </Properties>
</LiveStreamPacketizer>
<HTTPStreamer>
 <Properties>
  <Property>
   <Name>httpOriginMode</Name>
   <Value>on</Value>
   <Type>String</Type>
  </Property>
  <Property>
   <Name>cupertinoCacheControlPlaylist</Name>
   <Value>max-age=1</Value>
   <Type>String</Type>
  </Property>
  <Property>
   <Name>cupertinoCacheControlMediaChunk</Name>
   <Value>max-age=3600</Value>
   <Type>String</Type>
  </Property>
  <Property>
    <Name>mpegdashCacheControlPlaylist</Name>
    <Value>max-age=1</Value>
    <Type>String</Type>
  </Property>
  <Property>
    <Name>mpegdashCacheControlMediaChunk</Name>
    <Value>max-age=3600</Value>
    <Type>String</Type>
  </Property>
 </Properties>
</HTTPStreamer>

Once this is done, save the .xml file and restart the application.

More info on the Live HTTP Origin workflow.