Cisco Cisco Internet Streamer Application

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.

The following caveats have been resolved since Cisco Internet Streamer CDS Release 2.4.3. Not all the 
resolved issues are mentioned here. The following list highlights the resolved caveats associated with 
customer deployment scenarios.

CSCtd39651 

Symptom:

Because the content is very specific (encrypted flag in ASF file is 1), client sends a request with 
stream-switch-entry=ffff:8001:0 ffff:8002:0. 8001&8002 are flags of ASF file only 0~6 bits are used 
as stream number. This case is not addressed.

CSCtc63215 

Symptom:

DSCP value not set for RTSP.

CSCtc57849

Symptom:

SE marks fast-cache for RTSPT when fast-cache is disabled.

CSCtc33684

Symptom:

Only audio is available when HTTP request is used to playback some of the media files. These media 
files have an audio track == 1 and a video track = 31.

CSCtc21243

Symptom:

SE to send A-record instead of AAAA-record for DNS resolution.

CSCsx58932

Symptom:

Windows Media Streaming core dumps during testing of live streaming.

Conditions:

This happens when a server-side playlist (SSPL) source is used and automation scripts are used as 
clients.