Table Of Contents
Cisco TelePresence Content Server Release 5.1 Release Notes
Contents
Introduction
Changes and Improvements in 5.1
Create recording Page
Creator Functionality
BFCP Functionality
Resolved Caveats
System
Video
Interoperability
Localization and Internationalization
Clustering
Open Caveats
Upgrading to 5.1
Prerequisites and Software Dependencies
Upgrade Instructions
Checking for Updates and Getting Help
Related Documentation
Cisco TelePresence Content Server Release 5.1 Release Notes
May 2011
Contents
•
Introduction
•Changes and Improvements in 5.1
•Resolved Caveats
•Open Caveats
•Upgrading to 5.1
•Checking for Updates and Getting Help
•Related Documentation
Introduction
These release notes describe the changes and improvements included in the Cisco TelePresence Content Server (Content Server) software version 5.1.
Changes and Improvements in 5.1
•Create recording Page
•Creator Functionality
•BFCP Functionality
Create recording Page
The Create recording page has been simplified by collapsing the Recording information, Recording permissions, and Play recording on endpoints sections. Configurations in those sections can be accessed by expanding the Full recording information and permissions link.
Creator Functionality
The Create recording page now allows Creators to enter the dial number or address of an endpoint or system to make a recording. The Creator's personal recording alias will be set as the default recording alias. If a Creator has no personal recording alias, the default system alias will be displayed as the default recording alias on the Create recording page.
Personal recording aliases owned by a Creator are now listed on My Recordings> Create recording options page.
BFCP Functionality
In outgoing calls from the Content Server to far end devices (endpoints or MCUs), the Content Server will now offer BFCP over UDP only.
No changes to incoming calls—the Content Server will continue to offer BFCP over UDP or TCP, as signaled by the far end device.
Resolved Caveats
The following issues were found in previous releases and were resolved in 5.1.
System
|
Reference ID
|
Summary
|
88596 |
Corrected an issue where the LDAP server port setting specified in the Authentication section of Site Settings connections was not honored for testing the LDAP connection, adding a group and part of the user authentication process. |
89136 |
Fixed integration issue with Show and Share version 5.2.3 which prevented upload of recordings from the Content Server. Show and Share versions 5.2.1 and 5.2.2 were not affected by this issue. |
89137 |
Fixed issue where changing the Wowza media server live application directory to anything other than 'live' was not honored. |
89138 |
Corrected an issue where offline transcoding would start 2 seconds after the call start. Existing recordings with this issue need to be retranscoded to apply this fix. |
89140 |
Fixed an issue where for outgoing calls from the Content Server to Movi or MXP F9.x, users were unable to open the presentation stream. |
89142 |
Fixed integration issue with Show and Share where content uploaded to Show and Share had the date set to local time instead of UTC time, resulting in Show and Share displaying an incorrect date and time for the added date field. |
89240 |
Corrected an issue where extra information provided in the incoming SIP URI string from a CTS endpoint prevented a correct recording alias match from occurring, resulting in failure to connect calls from CTS. |
89522 |
Fixed an issue where recording thumbnails were not being written to the NAS if the combined NAS path and filename exceeded 127 characters. |
Video
|
Reference ID
|
Summary
|
87274 |
Improved the quality of live streaming with two concurrent live calls on first generation hardware. |
89077 |
Corrected an edge case where the offline transcoder could produce MPEG-4 for QuickTime outputs that would not play in the QuickTime player due to incomplete decoding information in the header. This situation will not occur for new recordings from 5.1 onwards, but existing recordings with this issue need to be retranscoded. |
Interoperability
|
Reference ID
|
Summary
|
89139 |
Corrected an issue with Polycom MGC-25, 9.0.4.3, where a Content Server recording of an MGC conference with an active H.239 content channel would ignore the content channel release message and would display the last frame of the presentation until the recording ended. |
Localization and Internationalization
|
Reference ID
|
Summary
|
72262 |
Fixed an issue which prevented site managers from adding a group with non-ASCII characters in the name on the Add Groups and Users page. |
88366 |
Corrected an issue which prevented users with non-ASCII characters in their Active Directory Full name from logging in when the Content Server was in LDAP authentication mode. |
88706 |
Corrected an issue where dialing in from an endpoint to a recording alias which had Asian multibyte characters in the Name field of the Default recording information, the resulting recording name would contain question marks instead of Asian characters. |
89069, 89237 |
Fixed an issue with garbled characters displayed in the success message after uploading a language pack or a TCB file with non-ASCII characters in the name. |
89071 |
Corrected an issue where after uploading a TCB import file, the recording name and description of uploaded recordings were not displayed correctly if they contained Asian or non-ASCII French characters. |
89074, 89078 |
Fixed an issue where if a user's browser encoding was not set to UTF-8 by default, localized text in the Content Editor and the legacy Windows Media player would not be displayed properly. Unicode (UTF-8) encoding is now enforced for the Content Editor and legacy Windows media player. |
89075, 89076 |
Corrected an issue where names of downloadable recordings and TCB files with non-ASCII characters in the name were not displayed correctly in the browser's 'Save As' dialogue. |
89141 |
Added support for using non-ASCII characters in baseDN, userDN and password fields in the LDAP settings in Site Settings. |
89238 |
Fixed an issue where indexes with non-ASCII and Asian characters were not displayed in the Flash player. |
89790 |
Corrected an issue where non-ASCII characters in recording name or description were not passed correctly to Show and Share, resulting in garbled characters displayed in Show and Share interface. This bug fix addresses integration between Content Server version 5.1 or higher, and Show and Share version 5.2.2 or higher. |
Clustering
|
Reference ID
|
Summary
|
89143 |
A clustered Content Server can now be removed from the cluster database if it has been unresponsive for over 2 hours or is in maintenance mode. Contact TAC for details. |
86543 |
Fixed an edge case where under some circumstances the recording source file of a recording terminated abruptly by power failure or a Content Engine restart would never be copied to its final destination and could be deleted by the Helper service from the temporary folder. |
89144 |
Optimized the way recording thumbnails are written to the NAS during a live streaming call to improve system robustness. |
89145 |
Logging and XML-RPC behavior improvements: •Modified socket behavior so the socket used in the XML-RPC server now only accepts connections from the loopback adapter, to eliminate error messages caused by port scanners connecting to open XML-RPC ports. •Added a timer to XML?RPC request function so a warning is printed if servicing a request that takes longer than 5 seconds. •Improved logging for memory usage (private memory, free RAM, virtual memory used and working set). |
89146 |
Better logging of ports in use by the current process around the time when a call is disconnected due to media time-out. Also added the ability to disconnect a call if media ports failed to set up for some reason. |
Open Caveats
The following issues currently apply to this version of Content Server.
|
Reference ID
|
Summary
|
NA |
The Content Server supports only Microsoft Active Directory Server for LDAP and Domain authentication. |
NA |
When configuring LDAP servers in the Authentication section of the Site Settings page, the Content Server cannot accept the root of an Active Directory domain as the base DN. Instead, you must specify an object that resides inside the root. A common root-level object is 'OU=users.' If your users and groups are distributed between multiple root-level objects, specify each of them in separate LDAP servers. |
56699 |
Internet Explorer security settings may prevent users from accessing the Windows Server administration interface with IE7 or IE8 on Windows XP (Server Pack 3) even if the Content Server has been added to trusted sites in the browser. |
63782 |
It is not possible to register more than 25 SIP aliases on the Content Server. |
77297, 77298 |
QuickTime plug-in v.7.6.6 or higher causes the following issues when playing back MPEG-4 for QuickTime in the viewer: no video displayed in IE/Firefox on PC and Safari/Firefox on Mac when live streaming, and garbled audio when viewing on demand with Firefox/IE on a PC. Content Server users are advised not to upgrade their QuickTime plug-in to version 7.6.6 or higher. |
81835 |
When the camera is turned off while reviewing recordings from a E20 endpoint, the review overlay will be missing, and a 'No incoming video' error message will be displayed. |
81954 |
Live Windows Media multicast streams will not be displayed in the Silverlight player in Firefox 3.6.x on a PC. |
82218 |
When HTTPS is used to view Content Server pages, users will not be able to view content in Silverlight and Flash players. |
83035 |
Progressive download of MPEG-4 for Flash recordings from the Local IIS Web Server will not work in IE7 if the file size of the MPEG-4 for Flash output exceeds 2 GB (KB 298618). |
84626 |
Areas of green pixels may be displayed when starting playback and seeking in a Flash video streaming from a Wowza streaming server on some computers. The workaround is to update video drivers and/or turn off hardware acceleration. Visit the Adobe web site to view minimum hardware requirements for SD and HD video playback and video hardware acceleration support http://www.adobe.com/products/flashplayer/systemreqs/#video |
86461 |
A link to download missing Flash plug-in is not displayed in the new Flash player in Internet Explorer. |
Upgrading to 5.1
Prerequisites and Software Dependencies
The 5.1 installer will upgrade your Content Server from 5.0 version only. If your Content Server is at an earlier version, you will need to upgrade to 5.0 first before running the 5.1 installer.
A release key is not required for upgrading to 5.1.
Caution
You must back up your Content Server and turn off anti-virus applications before upgrading. You will need a full backup for restoring to the previous version or in the unlikely event of an upgrade failure. Follow the instructions on backing up and restoring the Content Server in the online help.
Caution
If you have installed the Feature Pack for Microsoft SQL Server 2005 or any of its components (which is NOT supported for the Cisco TelePresence Content Server), you must remove the following components prior to upgrading, otherwise the upgrade may fail.
Unsupported components which MUST be removed prior to upgrading:
Microsoft SQL Server 2005 Analysis Services 9.0 OLE DB Provider, Microsoft SQL Server 2005 Backward Compatibility Components, Microsoft SQL Server 2005 Command Line Query Utility, Microsoft SQL Server 2005 Data Mining Viewer Controls, Microsoft SQL Server 2005 JDBC Driver, Microsoft SQL Server 2005 Management Objects Collection, Microsoft SQL Server 2005 Compact Edition, Microsoft SQL Server 2005 Notification Services Client Components, Microsoft SQL Server 2005 Upgrade Advisor, Microsoft SQL Server 2005 Reporting Services Add-in for Microsoft SharePoint Technologies, Microsoft SQL Server 2005 Data Mining Add-ins for Microsoft Office 2007.
Upgrade Instructions
The approximate duration of an upgrade is 10-20 minutes.
To upgrade your Content Server to 5.1, do the following:
Step 1 Log in to the Content Server using Windows Remote Desktop Connection or through local console.
Step 2 Transfer the installer and the MD5 file that you downloaded to the Content Server (do not run the installer from a mapped or network drive).
Step 3 Verify the MD5 hash (checksum) of the installer using the provided MD5 file. Cisco recommends that you verify that the installer has not become corrupted as a result of file transfer, disk error or tampering. Any MD5 program can be used for verifying the installer integrity using the provided MD5 file. You need to follow instructions for the MD5 program you are using.
Step 4 If the installer passed the MD5 verification, run the installer by double-clicking on it.
Step 5 Click Next when the Next button is available and Install Shield Wizard is ready to begin installation.
Step 6 At the Content Server prerequisites prompt you need to select the backup option that applies to your Content Server:
•If you select The Content Server is backed up, click Next to proceed with the installation.
•If you select The Content Server is not backed up, clicking Next will display a warning that in case of installation failure there may be no way to recover your data. You may cancel the installation at this point, take a backup of your Content Server and then run the installer again. You may also choose to ignore the warning and proceed with the installation, although this is not recommended.
Step 7 At the second Content Server prerequisites prompt you need to select the antivirus option that applies to your Content Server:
•If you select There is no antivirus software installed, or The antivirus software is stopped, click Next to proceed with the installation.
•If you select The antivirus software is still running, clicking Next will display a warning that this might cause your installation to fail. You may cancel the installation at this point, stop the antivirus software and then run the installer again. You may also choose to ignore the warning and proceed with the installation, although this is not recommended.
Step 8 At the Are you sure you wish to continue? prompt, click Yes if you wish to proceed with the upgrade, or No if you want to cancel the upgrade.
Caution
You must not cancel or interrupt the upgrade process after this point. If you want to revert to the previous version after completing the upgrade to 5.1, you will need to follow the instructions for restoring from backup available in online help.
Step 9 After the installer has configured the Content Server, it will display a message that the upgrade has completed successfully. The installation logs are available in the following locations: E:\logs\Install and E:\logs\SetupUtility.
Checking for Updates and Getting Help
Cisco recommends registering your product at http://www.tandberg.com/services/video-conferencing-product-registration.jsp in order to receive notifications about the latest software and security updates. New feature and maintenance releases are published regularly, and we recommend that your Content Server software is always kept up to date.
If you experience any problems when configuring or using your Cisco TelePresence Content Server, consult the online help (available within the UI) for an explanation of how its individual features and settings work. If you cannot find the answer you need, check on the web site at http://www.tandberg.com/support to make sure that your product is running the most up-to-date software and for further relevant documentation.
You or your reseller can get help from our support team by raising a case at http://www.tandberg.com/support/video-conferencing-online-support.jsp. Make sure you have the following information ready:
•The serial number and product model number of the unit
•The software build number which can be found on the product user interface
•Your contact email address or telephone number
Related Documentation
For more information about the Cisco TelePresence Content Server, see these documents:
•Cisco TelePresence Content Server Release 5.1 Administration and User Guide
•Configuring the Cisco TelePresence Content Server for Streaming from a QuickTime Media Server
•Configuring the Cisco TelePresence Content Server for Streaming Flash from a Wowza Media Server
•Cisco TCS Integration to Cisco Show and Share for Live WMV Streaming
•Cisco TelePresence Content Server API Guide
•Video on Demand Integration for Cisco TCS to Cisco Show and Share
All documents are located here:
http://www.cisco.com/en/US/partner/products/ps11347/tsd_products_support_series_home.html
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED "AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2011 Cisco Systems, Inc. All rights reserved.
Feedback