Cisco Cisco Internet Streamer Application
8
Release Notes for Cisco Internet Streamer CDS 2.5.7
OL-20688-02
Open Caveats
3.
For high-volume traffic, separate HTTP and WMT.
The CDE200, CDE205, or CDE220 performance has been optimized for HTTP and WMT bulk
traffic, individually. While it is entirely workable to have mixed HTTP and WMT traffic flowing
through a single CDE200 simultaneously, the aggregate performance may not be as optimal as the
case where the two traffic types are separate, especially when the traffic volume is high. So, if you
have enough client WMT traffic to saturate a full CDE200, CDE205, or CDE220 capacity, we
recommend that you provision a dedicated CDE200 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, CDE205, or CDE220 servers
than usual.
traffic, individually. While it is entirely workable to have mixed HTTP and WMT traffic flowing
through a single CDE200 simultaneously, the aggregate performance may not be as optimal as the
case where the two traffic types are separate, especially when the traffic volume is high. So, if you
have enough client WMT traffic to saturate a full CDE200, CDE205, or CDE220 capacity, we
recommend that you provision a dedicated CDE200 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, CDE205, or CDE220 servers
than usual.
4.
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.
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.
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.
5.
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.
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.
Open Caveats
This release contains the following open caveats:
API
•
CSCth44836
Symptom:
UNS-related errors occur because the program name and reference URL had uppercase and
lowercase characters, but the API only allows lowercase characters for both the program name and
reference URL.
lowercase characters, but the API only allows lowercase characters for both the program name and
reference URL.
Condition:
Live programs with uppercase characters in the program name and reference URL (unicast or
multicast) are not consistent with API calls, which expect only lowercase characters.
multicast) are not consistent with API calls, which expect only lowercase characters.
Workaround: