Table of Contents
Cisco TelePresence Content Server Release 7.2 Release Notes
New Hardware and Software Features
TCS 7.2 M3/M4/BE7K/Third Party OVA Specifications
TCS 7.2 BE6K OVA Specifications
Tested Third Party Hardware Details
Content Server Compatibility Matrix
List of the supported playback formats with HTTPS.
Supported Platforms, Browsers, and Plug-ins
Troubleshooting and Technical Support
Obtaining Documentation and Submitting a Service Request
Cisco TelePresence Content Server Release 7.2 Release Notes
This release notes describe the changes and improvements included in the Cisco TelePresence Content Server Software Release 7.2.
Contents
- New Hardware and Software Features
- Install TCS
- Upgrade Path
- Content Server Compatibility Matrix
- Limitations and Restrictions
- Known Issues
- Open Caveats
- Resolved Caveats
- Guidelines and Prerequisites
- Troubleshooting and Technical Support
- Related Documentation
- Obtaining Documentation and Submitting a Service Request
New Hardware and Software Features
New Software Features
1. TLS support to secure SIP signaling:
TCS 7.2 supports SIP TLS over TCP for secure SIP signaling. SIP TLS uses port 5061 for transferring encrypted sip messages. Follow TCS 7.2 administration and user guide for SIP TLS configuration on TCS and CUCM.
2. FTPS support for VBrick DME:
Support for transferring media securely using FTPS to VBrick Distributed Media Engine (DME) is added in TCS 7.2. Now TCS would be supporting both FTP and FTPS as file transfer protocol for transferring media to VBrick DME. The selected default file transfer protocol is ftp on both TCS and DME however user can configure FTP or FTPS for transferring the media files to DME.
Install TCS
There is no change in TCS installation. Follow the below guides for TCS installation:
Upgrade Path
There is a direct upgrade path from TCS 7.0/TCS 7.1 to TCS 7.2. User can copy the TCS 7.2 Setup Utility on TCS Server and upgrade directly from TCS 7.0 or TCS 7.1 to TCS 7.2. There is no direct upgrade path from TCS 6.x to TCS 7.2.
Note 3rd transcoding engine will be available in TCS only with the above specified OVA specification.
If existing TCS box is having less resources, follow one of the below methods to upgrade TCS:
Content Server Compatibility Matrix
Table 1 Cisco Show and Share and Content Server Software Compatibility
Note SNS versions prior to 5.6.2 are supported after installing CSCuy12941 patch on SNS
Limitations and Restrictions
- For TCS 7.2 there is no on-box streaming server as Windows Server 2012 doesn’t support Windows Media Streaming server.For live streaming, TCS needs to be configured with an external streaming server.
- Multicast content delivery from Windows media services is not supported on Windows 2012 Standard Edition. An External Media Server can be used for unicast and multicast streaming.
- The Content Server does not support running Windows services such as Active Directory Domain Services (ADDS), DNS server, or file services. You should configure an external server for all Windows-based services.
- MCU pin protected conference using SIP will not work if MCU is behind Conductor.
- The H.264 codec used in MPEG-4 file format of TCS are not much capable of rendering dense documents (with less whitespaces) in presentation. To improve the quality of the recording, font size in the presentation document can be increased or the recording output size can be reduced to medium in TCS recording template so that the whitespaces can be distributed in the document(CSCvg07146).
Known Issues
- During third party hardware certification, TCS UI didn't show up though TCS is successfully installed and all the services were functioning. To ensure that installation of TCS Software gets installed on third party hardware, please make sure correct date and time are configured. To check, do the following:
– Go to ESXI > Configuration > Time Configuration > Properties. Update the correct date and time (CSCus76714).
- Audio only recording with SIP is not supported in TCS 7.2.
- Pin protected endpoint playback does not work with SIP.
- If you change the domain name of a third-generation Content Server and then run Windows Server Backup , the system could return this error message: “ The Block Level Backup Engine Service has been disabled. Enable the service and then restart Windows Server Backup”.
– The workaround is to start the Windows service called Virtual Disk , and then launch Windows Server Backup . If starting the Virtual Disk service does not resolve the issue, you should uninstall and reinstall the Windows Server Backup feature. (CSCuo29694)
Browser Issues
To play WMV and QuickTime recordings, the Content Server site must be added to the compatibility view list as shown in Figure 1.
- WMV Recordings may not be viewable in the content editor.
- After playing a WMV recording on Firefox, the following error might appear and Firefox stops responding: “ Microsoft Windows Media Player Firefox plugin may be busy or it may have stopped responding. You can stop the plugin now, or you can continue to see if the plugin will complete. Continue or Stop Plugin? ”.
- Use IE10 or IE11
- Use HTTP instead of HTTPS. For more information about installing the required plugin, see
https://support.mozilla.org/en-US/kb/play-windows-media-files-in-firefox?esab=a&s=Windows+Media+Player&r=2&as=s
- Using IE 11 and Silverlight 5.1 plug-in, user can able to play the recording without any issues.
- The recording can be played using FireFox with Windows Media Player plug-in by selecting other formats options in the player window without any issues.
- Using FireFox 3.5x and Silverlight 5.1 plugin, user can able to play the recording without any issues.
Figure 1 Compatibility View Setting
Open Caveats
Following is the list of the open caveats in Content Server Release 7.2.
Resolved Caveats
Following is the list of the resolved caveats in Content Server Release 7.2.
Guidelines and Prerequisites
Before you begin, observe these guidelines and prerequisites:
- You must have an administrator privileges to perform a software installation.
- You should download Release 7.2 software from Cisco.com before you begin the installation procedure.
- Release 7.2 software cannot be installed on first- or second-generation Content Server hardware, if you attempt to run the 7.2 installer, it will fail.
- Release7.2 software can be installed on Third-generation Content Server hardware as VM.
- You can use the Content Server serial number to identify the server hardware version. In the web UI go to Management > Diagnostics > Server overview . You can also check the serial number label on the top right front of the Content Server. These are the device serial number formats:
– Fourth-generation serial number: 49A4 xxxx
– Third-generation serial number: 49A3 xxxx
– Second-generation serial number: 49A2 xxxx
Troubleshooting and Technical Support
Cisco recommends to register your product at http://www.cisco.com/cisco/support/notifications.html 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 up to date.
Using the server logs to help solve a problem
You can use the server logs to produce debugging information to assist customer support in solving issues. From the Management tab, go to Diagnostics > Server logs to access the Content Server logs.
If you experience any problems when configuring or using the Content Server, consult the online help for an explanation of how individual features and settings work. Also, see the Cisco TelePresence Content Server Administration and User Guide for this release on Cisco.com.
When contacting Cisco for support, make sure that you have this information:
Related Documentation
http://www.cisco.com/en/US/products/ps11347/tsd_products_support_series_home.html
http://www.cisco.com/en/US/products/ps10493/tsd_products_support_series_home.html
http://www.cisco.com/en/US/products/ps12130/products_installation_and_configuration_guides_list.html
Information About Accessibility and Cisco Products
For information about the accessibility of this product, contact the Cisco accessibility team at accessibility@cisco.com.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation at: http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html
Subscribe to What’s New in Cisco Product Documentation , which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.
This document is to be used in conjunction with the documents listed in the Related Documentation section.Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: 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. (1110R)
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.