Specifications

1-15
Cisco Internet Streamer CDS 2.0-2.3 Software Configuration Guide
OL-13493-04
Chapter 1 Product Overview
Content Delivery System Architecture
Accelerated—This method supports only RTP over UDP. Content must be reprocessed by the
Movie Streamer Linear Hinter. The linear hinter process can be initiated manually by the
administrator or dynamically triggered by the first request for the content.
The Movie Streamer Linear Hinter process may take a while, so the first request that triggers this process
is served by means of the non-accelerated method. All subsequent requests are served by the accelerated
method.
The first client request for content that requires proxying or caching experiences a delay, because all
proxying and caching requires the accelerated method.
Live Stream
The Movie Streamer Engine supports multicast reference URLs (Announce URLs) for programs that are
created through the Internet Streaming CDSM. The multicast reference URL, which is in the form of
http://Service Engine IP address/Program ID.sdp, is resolved by the Movie Streamers that are serving
the live program.
QuickTime live typically has a UDP socket pair (for RTP and RTCP) per track, and each client session
typically has two tracks (audio and video).
Note The following rules apply to live splitting:
1. For unicast streaming, the client request must be sent by means of RTSP.
2. For multicast streaming, the client request must be sent by means of HTTP.
Authentication
The Movie Streamer Engine supports the following authentication modes:
Basic
Digest
URL Signing
Support of URL signing for Movie Streamer content requests is a Release 2.2 feature. For more
information see the “URL Signing” subsection, under the “Flash Media Streaming Engine”section on
page 1-17.
Flash Media Streaming Engine
Note Flash Media Streaming is a Release 2.1 and Release 2.2 feature.
The Flash Media Streaming Engine incorporates the Adobe Flash Media Server technology into the CDS
platform. The Flash Media Streaming Engine is capable of hosting Flash Media Server applications,
such as VOD (prefetched content, or dynamic or hybrid ingested content) and live streaming, that are
developed using ActionScripts.
Upon receiving a client request for VOD content, the edge Service Engine does the following:
If the content is present, the edge Service Engine streams it using RTMP.
If the content is not present, the edge Service Engine uses HTTP to fetch the content from the origin
server and serves it using RTMP.