Specifications

4-39
Cisco Internet Streamer CDS 2.0-2.3 Software Configuration Guide
OL-13493-04
Chapter 4 Configuring Devices
Configuring the Service Engine
If the settings are previously configured through the device group, the current configuration is displayed
for view only. New settings must be configured through the associated device group.
If you want to configure settings for this SE only, and override the device group settings on this SE, set
Aggregate Settings to No.
If you remove all device group settings, all device settings displayed with Aggregate Settings enabled
are removed as well.
Note The last configuration submitted for the device, whether it is the device group configuration or
the individual device configuration, is the configuration the device uses.
Step 3 Click the Create New icon in the task bar. The Broadcast Alias page is displayed.
To edit a Broadcast Alias, click the Edit icon next to the name you want to edit.
Step 4 In the Broadcast Alias field, enter an alias for the source URL or station name to be used for the
broadcast.
When a broadcast alias is configured, a client makes a request to the SE as if it were the Windows Media
Server, and the SE checks to see whether the incoming stream is present. If it is, then the SE joins the
stream and splits it to the new client. If the request is the first client request for this stream, the SE sends
the request out to the server and then serves it to the new client.
Step 5 In the Source URL field, enter the URL of the station to be used for the broadcast; for example:
http://172.16.30.21/station.nsc
In this example, the multicast source URL contains the file station.nsc. A source URL in the format
http://server/file.nsc tells the SE that the input source is sending out Windows Media multicast streams.
The following is an example of a unicast-in:
rtsp://wms.company.com/cotv
where wms.company.com is the name of the Windows Media Server, and cotv is the name used when
the broadcast alias is created. The RTSP protocol is used to retrieve the stream.
Step 6 Click Submit to save the settings.
Configuring Windows Media Streaming—Bypass List
Incoming bandwidth refers to the bandwidth between a local SE and the origin server. When the SE is
configured for Windows Media proxy services, incoming bandwidth usage for Video On Demand (VOD)
content is unpredictable. This unpredictability is because the consumption of incoming bandwidth for
VOD content can be triggered arbitrarily by an end user requesting the content. If the VOD content is
not found in the SE cache, a cache miss occurs, and the Windows Media proxy must fetch the content
from the origin server. The SE administrator cannot predict the incoming bandwidth usage for such
events, so a large number of cache-miss VOD requests can consume all of the incoming bandwidth.
The Windows Media incoming bandwidth bypass configuration allows the administrator to configure a
list of hosts that bypass the incoming bandwidth limitation. Content from a source that is listed as a host
in this configuration is allowed to bypass the incoming bandwidth check for broadcast alias or multicast
station content. This feature is particularly useful when the administrator wants to configure a broadcast
alias or multicast station for a mission-critical live event.