Knowledgebase
CDN Live Streaming Resource Print this Article
The Live Streaming CDN Resource is designed to deliver live streaming content via the CDN. Protocols supported include: RTMP, RTSP(Android OS), MPEG-TS, Microsoft Silverlight(Microsoft smooth streaming), HDS(HTTP Dynamic Streaming), Apple HLS. To add a Live Streaming Resource:
BASIC SETTINGS -
Complete the last two steps for adding a CDN resource (see this guide). NOTE: if you selected Internal publishing in step 2 of the basic settings above, you will need to select your primary and failover internal publishing location using the Publishing Point selectors that are located beneath the Edge Groups list.
- If you have not already done so, order CDN Service (use this guide);
- Navigate to your CDN Service and add a new CDN Resource of the type Live Streaming (use this guide);
BASIC SETTINGS -
- CDN Hostname - specify the name (this will serve as a label only);
- Publishing point – specify the resource's publishing point settings:
- Internal - use publishing points that are part of the CDN (you will be able to select these later in the configuration;
- External - use publishing points outside of the CDN. If you choose this you will need to supply a URL for a primary External publishing location and a Failover external publishing location;
- Country Access - Configure a rule to enable/disable access to the CDN resource’s content for specified countries:
- Default - access is allowed for all countries;
- Allow by Default - access is allowed for all countries, excepting those listed in Except for Countries;
- Block by Default - access is denied for all countries, excepting those listed in Except for Countries;
- Except for Countries - the list of countries to be allowed or blocked, depending upon your setting. To select more than one country, hold Ctrl during selection.
- Secure Wowza - The Live Streaming CDN utilizes the Wowza streaming engine. Tick the box if you wish to protect your stream with Wowza secure token.
- Token for Edge/Flash player - specify the token authentication code. The authentication code will be then saved on the edge server. The token at the player side and the token at the edge server must match in order to make the video available.
- Token for Edge/Flash player - specify the token authentication code. The authentication code will be then saved on the edge server. The token at the player side and the token at the edge server must match in order to make the video available.
- Hotlink Policy - Configure rules for hotlinking by other sites:
- Default - hotlinking is allowed for all sites;
- Block by Default - hotlinking is denied for all sites, excepting those listed in Except for Domains;
- Except for Domains - the list of sites to be allowed for hotlinking when policy is set to Block by Default.
Complete the last two steps for adding a CDN resource (see this guide). NOTE: if you selected Internal publishing in step 2 of the basic settings above, you will need to select your primary and failover internal publishing location using the Publishing Point selectors that are located beneath the Edge Groups list.
Was this answer helpful?
Related Articles
CDN HTTP PULL Resource
HTTP Pull is probably the most frequently used CDN method/protocol. It's recommended for the...
HTTP Pull is probably the most frequently used CDN method/protocol. It's recommended for the...
CDN HTTP PUSH Resource
The HTTP Push Resource can be compared to having a secondary server at your disposal: you upload...
The HTTP Push Resource can be compared to having a secondary server at your disposal: you upload...
CDN Video On Demand (VOD) Resource
A VOD CDN Resource is meant to deliver static video files within the CDN. Supported protocols...
A VOD CDN Resource is meant to deliver static video files within the CDN. Supported protocols...