Cisco Cisco Internet Streamer Application 릴리즈 노트

This release contains the following open caveats that are not cause by the CDS software:

CSCsr58043

Symptom:

When using a file as the type of source for a live publishing point in Windows Media Server 2008 
Standard, after starting multiple streaming requests from that publishing point, when the first stream 
reaches the end of the source file the second and subsequent streams fail with an error message at 
the same time. If Windows Media Server 2008 Standard is used as the origin server for a delivery 
service in CDS-IS, the second and subsequent streams will not fail, but will repeatedly loop the last 
segment of the stream. 

Workaround:

Publishing points can be created using other source types (for example, playlists) rather than a file 
as the source type with the Windows Media Server 2008 Standard. The symptom described above is 
not seen with windows Media Server 2008 Enterprise used as the origin server. 

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

CSCsv00833

Symptom:

From the Replication Status page, in the Devices Assigned to Delivery Service section, content 
items retrieved using the Get drop-down list, along with the Content Items Using field, are not 
retrieved the Service Engine in the delivery service.

CSCsv16158

Symptom:

The Replication Status summary for the Service Engines that are not acting as the Content Acquirer 
are incorrect.

CSCsv40648

Symptom: When a Flash Media player makes a request using a relative URL for a live stream, the 
FMS core dumps.