Cisco Cisco Internet Streamer Application 릴리즈 노트

to handle WMT; and likewise for HTTP. In such cases, we do not recommended that you mix the 
two traffic types on all CDE servers which could result in suboptimal aggregate performance and 
require more CDE200 servers than usual.

For mixed traffic, turn on the HTTP bitrate pacing feature.

If your deployment must have Streamers handle HTTP and WMT traffic simultaneously, it is best 
that you configure the Streamer to limit each of its HTTP sessions below a certain bitrate (for 
example, 1Mbps, 5Mbps, or the typical speed of your client population). This prevents HTTP 
sessions from running at higher throughput than necessary, and disrupting the concurrent WMT 
streaming sessions on that Streamer. To turn on this pacing feature, use the HTTP bitrate field in the 
CDSM Delivery Service GUI page. 

Please be aware of the side effects of using the following commands for Movie Streamer:

Config# movie-streamer advanced client idle-timeout <30-1800>

Config# movie-streamer advanced client rtp-timeout <30-1800>

These commands are only intended for performance testing when using certain testing tools that do 
not have full support of the RTCP receiver report. Setting these timeouts to high values causes 
inefficient tear down of client connections when the streaming sessions have ended. 

For typical deployments, it is preferable to leave these parameters set to their defaults.

For ASX requests, when the Service Router redirects the request to an alternate domain or to the 
origin server, the Service Router does not strip the .asx extension, this is because the .asx extension 
is part of the original request. If an alternate domain or origin server does not have the requested 
file, the request fails. To ensure requests for asx files do not fail, make sure the .asx files are stored 
on the alternate domain and origin server.

This release contains the following open caveats:

CSCso78725

Symptom:

A low-rate memory leak exists for Flash Media Streaming live streaming when clients connect and 
disconnect. It is currently under investigation by both Adobe and Cisco. The memory leak eventually 
results in a process restart.

Workaround: 

Flash Media Streaming live streaming can be recovered using next-click failover or simply retry 
from the client player.

CSCsr29544

Symptom:

Due to the memory leak issue, which is under investigation by Adobe and Cisco, the FMS core 
process will fail over to a new FMS core process after 24 hours. All new request will go to a new 
FMS core process. The old FMS core process will continue to serve the existing clients until all 
clients have disconnected, at which point the process will end releasing all memory.