Specifications

1-19
Cisco Internet Streamer CDS 2.0-2.3 Software Configuration Guide
OL-13493-04
Chapter 1 Product Overview
Content Delivery System Architecture
The Adobe Flash Media Encoder can publish the streams to any Adobe Flash Media Server acting as the
origin server. Clients use the RFQDN to get the live content. The request from the client for
“streamname” is mapped to origin_appinst_streamname internally in the CDS to differentiate between
two streams with the same name in two different delivery services.
Note All RTMP calls for live content in the SWF file must be in the following format:
rtmp://rfqdn/live/path/foo.flv
In this format, rfqdn is the routing domain name of the Service Router, live is the required directory, and
path is the directory path to the content file that conforms to the standard URL specification.
Flash Media Streaming supports live stream splitting. For more information about live stream splitting,
see the “Live Stream Splitting” section on page 1-11.
Interactive Applications
Release 2.3 supports pass-through (proxy) support for interactive applications (non-VOD or non-live).
The interactive applications are hosted on a Flash Media Interactive Server that is external to the CDS.
Direct routing from the Service Engine, acting as the Flash Media Streaming edge server proxy, to the
origin server (the Flash Media Interactive Server) is supported. Using the delivery service framework,
the origin server is abstracted from the client request by using the Service Router Domain Name
(SRDN), which resolves to the Service Engine that accepts the user connection and forwards the request
to the origin server. In Release 2.3, Flash Media Streaming includes the edge server (proxy) mode, and
by default, all non-live and non-VOD applications are proxied by using the edge server. Flash Media
Streaming selectively picks connections for processing in edge server mode and aggregates connections
to the origin servers.
CDS supports implicit URI as the method that allows the client to connect with the edge server without
exposing the origin server. The URI would look like this:
rtmp://edge1.fms.com/ondemand.
Request routing based on SWF files or using RTMP redirection is supported. However, RTMP
redirection requires more changes in the client code. SWF file-based redirection is recommended. SWF
redirection works as follows:
1. SWF files and associated HTML pages are either prefetched or hosted in the origin server.
2. Client uses a web browser to access the HTML page, which also loads the SWF file.
3. The SWF file is accessed using the SRDN.
4. The Service Router redirects the request to a Service Engine.
5. The SWF file is downloaded to the web browser.
6. The ActionScript in the SWF file attempts to connect to the same host from where the SWF file was
downloaded. This is an RTMP connection that reaches the Service Engine.
7. The Service Engine checks for the application type in the URI, if it is not VOD or live, the
processing is moved to the edge server mode and the connection is forwarded to the origin server.
8. The Service Engine tunnels the data between the client and the origin server.
Note Changes to a delivery service do not affect existing connections to the Flash Media Interactive Server
(origin server). Only new connections are affected by changes to a delivery service.