PDF(184.4 KB) View with Adobe Reader on a variety of devices
Updated:November 10, 2015
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
– Intel(R) Xeon(R) CPU E5-2680 v3 @2.50GHz 24 cores
– 64 GB RAM
Note This hardware specification is for TCS 7.0 Appliance on M4 only. TCS 7.0 Appliance is not supported on third generation hardware.
TCS 7.0 VM is supported on third-generation, fourth-generation and third party hardware.
New Software Features:
Migration to Windows server 2012 R2
TCS 7.0 is migrated from Windows server 2008 R2 Standard Edition to Windows server 2012 R2 Standard Edition.
Migration to SQL Server 2012
TCS 7.0 is migrated from SQL Server 2005 to SQL Server 2012 in standalone, while in Cluster user can have SQL Server 2008 or SQL server 2012.
TCS 7.0 M3/M4/BE7K/Third Party OVA Specifications
8v CPU (4 Virtual Sockets 2 cores per socket)
550 GB HDD
Note TCS 7.0 VM is supported on Cisco UCS M3, M4 hardware and any Third Party hardware with minimum above specified resources available Processor Type.
TCS 7.0 BE6K OVA Specifications
2 Virtual CPU
Note This hardware specifications for TCS as VM on BE6K hardware.
Tested Third Party Hardware Details
Machine Model No
ProLiant ML350p Gen8
6 CPUs x 2.094 GHz
Intel(R) CPU E5-2620 v2 @ 2.10GHz
Content Server Compatibility Matrix.
Table 1 Cisco Show and Share and Content Server Software Compatibility
Show and Share 5.2.1
Show and Share 5.2.2
Show and Share 5.2.3
Show and Share 5.3 and 5.3 Patch 1
Show and Share 5.5
Content Server 7.0
Table 2 Cisco MXE 3500 and Content Server Software Compatibility
Content Server 7.0
Table 3 VBrick and Content Server Software Compatibility
Content Server 7.0
Limitations and Restrictions.
For TCS 7.0, 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 external streaming server.
Multicast content delivery from Windows media services is not supported on Windows 2012 Standard Edition.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.
During third party hardware certification, it was found that 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 times is 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.0.
PIN Protected calls 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)
Table 4 Browser Issues
WMV and QuickTime recordings may not play in IE 11
To play WMV and QuickTime recordings, the Content Server site must be added to the compatibility view list as show 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? ”.
There are no workarounds.
When using Windows Media player with Firefox in HTTPS mode, the system could return this error message even if you have installed the required plugin “ Windows Media player is not installed on your computer. To play Windows Media in Firefox, you need to install a special plugin ”.
Use IE10 or IE11
Use HTTP instead of HTTPS. For more information about installing the required plugin, see
Table 5, Lists of the supported playback formats with HTTPS.
Table 5 Supported HTTPS Playback Formats
Supported Platforms, Browsers, and Plug-ins:
Content Server 7.0
Mozilla Firefox 38, 39
Internet Explorer 10, 11
Table 6, lists the open caveats in Content Server Release 7.0.
Table 6 Content Server Release 7.0 Open Caveats
Some times is transcoded recording shows blank playback
Recordings are not getting joined in Content Editor
Missing Secure Attribute in Encrypted Session (SSL) Cookie
Several Third Party Software Packages Need Upgrades
Table 7, lists the resolved caveats in Content Server Release 7.0.
Table 7 Content Server Release 7.0 Resolved Caveats
Remove Multicast option from TCS
Need clarification in TCS install guide exactly which UCS are supported
TCS “Playback Feature” doc should indicate Premium Res. Key is required
Documentation should be updated with the information “Audio only recording with SIP is not supported on TCS”.
Unable to play Large recording in quicktime player in tcs
Default protocol is set to H.323, we need SIP to be default
SIP Registration status in TCS 6.3 is incorrect and in red color
no option for email address to be different from recording alias
'H323' is missing in Create recording Page with GateKeeper disabled.
Guidelines and Prerequisites
Before you begin, observe these guidelines and prerequisites:
You must have administrator privileges to perform a software installation.
You should download Release 7.0 software from Cisco.com before you begin the installation procedure.
Release 7.0 software cannot be installed on first- or second-generation Content Server hardware. If you attempt to run the 7.0 installer it will fail.
Release7.0 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
– First-generation serial number: 49A0 xxxx
Troubleshooting and Technical Support
Cisco recommends registering 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 kept 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.
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.
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.