Cisco TelePresence Server 4.0(2.8) Software Release Notes Revised July 2014 Contents Product documentation New features in 4.0(2.8) New features introduced in 4.0(1.57) Platform licensing comparison Resolved issues Open issues Limitations Interoperability Upgrading to 4.0(2.
New features in 4.0(2.8) New features in 4.0(2.8) Table 1: New feature support by TelePresence Server platform Feature name 7010 & MSE 8710 Media 310/320 Virtual Machine Yes Yes Yes New platform for TelePresence Server [p.3] Not applicable Not applicable Yes Hypervisor version ESXi 5.5 support [p.3] Not applicable Not applicable Yes User Interface changes [p.3] Not applicable Not applicable Yes Resilience and diagnostics improvements Cisco Call Home support [p.
New features introduced in 4.0(1.57) Cisco TelePresence Server on Virtual Machine improvements New platform for TelePresence Server This release introduces a new platform for the TelePresence Server software: the Cisco Multiparty Media 400v. This gives an increased port capacity of 28 HD ports at 720p30 video + 720p5 content.
New features introduced in 4.0(1.57) Table 2: New feature support by TelePresence Server platform (continued) Feature name 7010 & MSE 8710 Media 310/320 Virtual Machine Increased calls per unit [p.10] Remotely managed only Yes Yes Dynamic resource optimization improvements [p.10] Remotely managed only Yes Yes OVA and specification changes for Cisco TelePresence Server on Virtual Machine [p.15] Not applicable Not Yes applicable Support for cascaded conferences [p.
New features introduced in 4.0(1.57) the loudest speaker is not in the telepresence room, then the TelePresence Server shows no panels from that room in a large pane.
New features introduced in 4.0(1.57) Changes to endpoint group layout When you are using the segment-switched display feature, grouped endpoints are composed differently than they were in the previous release. This change also applies to multi-camera endpoints that cannot reveal which camera is associated with the loudest speaker ("loudest pane information"). Grouped endpoints are now composed into a single pane so as not to disrupt segment-switching.
New features introduced in 4.0(1.57) Endpoint group indicators When a grouped endpoint is shown in the ActivePresence or Prominent layout, the endpoint must be placed in the PiP strip but, because of the lack of loudest pane information, the TelePresence Server cannot determine which pane of the group to place in the PiP strip. Also, now that the group is composed into a single pane, the live video of the group members is too small to be useful in these layouts.
New features introduced in 4.0(1.57) Figure 5: PiP strip showing the active speaker's place (gap) The active speaker gap applies only to the ActivePresence layout. It is also not available on multiscreen endpoints that are in room-switched display mode. Note: Future improvements to the PiP strip feature may include reducing the maximum number of PiPs and increasing their size, to make the feature more consistent across endpoints and to allow for better recognition of changes to facial expression.
New features introduced in 4.0(1.57) Figure 7: The TelePresence Server's "you are muted" icon Participants will see this icon when their audio contributions are muted from the TelePresence Server side. This mute can be applied by the participants themselves, using *6, or by another authorized party. Participants may also see a message about having been muted. This icon does not appear when the participant uses the endpoint's own mute control.
New features introduced in 4.0(1.57) n Reporting on the state of conferences and participants has been improved as follows: l Participant deletions can be requested per conference l Connection state of enumerated participants is reported l Current presenter is reported l A new participant enumeration has been added. The new method returns more detailed information on each connected participant, for example the participant's encryption status and media status.
New features introduced in 4.0(1.57) Cisco TelePresence Conductor allocates screen licenses to calls based on the TelePresence Server's reports of what the endpoints require.
New features introduced in 4.0(1.57) Table 5: Optimization profiles enumerated type (continued) optimizationProfile Description value maximizeExperience Screen licenses are more readily allocated. This value gives the best experience of the four profiles. If you disable the optimization by bandwidth (by setting optimizationProfile to capabilitySetOnly), calls will be capable of higher resolutions at lower bandwidths but the inefficency in allocation could well outweigh the benefit.
New features introduced in 4.0(1.57) How to read the chart: The shading levels on the chart represent the fractions/multiples of screen licenses that the TelePresence Server reports to the managing system for the given bandwidth ranges and content quality limits. The key relates types of calls to each of those levels.
New features introduced in 4.0(1.57) Table 6: Example of how to read this chart On Conductor: Content quality is set to 720p5, Participant quality is set to 1080p30 The endpoint: Requests 1080p30 video with 720p5 content, at 2048kBps. The key shows that this type of call requires 1 screen license. The bandwidth of the call is limited to 2MBps (2048kBps), so we're looking at the region between 1472kBps and 2240kBps on the chart.
New features introduced in 4.0(1.57) 1. Go to Conference configuration > Conference templates and select the appropriate template 2. In the template's Advanced parameters, click Edit 3.
New features introduced in 4.0(1.57) n 2 x Intel Xeon processor E5-2600 series with 2.
New features introduced in 4.0(1.57) Support for cascaded conferences Note: This feature is only available in the remotely managed mode of TelePresence Server operation. It is not available in the locally managed mode. Note: This feature is not supported on Cisco TelePresence Conductor XC2.3. The TelePresence Server software now supports cascading, which is the ability for one TelePresence Server to invite another TelePresence Server into a conference.
New features introduced in 4.0(1.57) For each connection, the netstat list contains the following information about each end: n The IP address or hostname (requires external DNS) n The port or service n Whether the connection uses TCP or UDP, and the associated internet protocol address scheme (4 or 6) Ephemeral port range The TelePresence Server now gives the administrator control over the range of ephemeral ports used for media connections.
New features introduced in 4.0(1.57) Figure 11: The media resource restart notification banner Note: Some participants may experience a loss of media in the unlikely event of a media processor restart, although it should come back after a pause of about 30 seconds. On a virtual machine, a media processor restart will affect all participants but should take less than 5 seconds to recover. If a media processor restarts repeatedly, it may still cause the TelePresence Server to restart.
Platform licensing comparison Platform licensing comparison The following table compares the number of TelePresence Server screen licenses that each of the platforms can accept and how they translate into conferencing capacity. The table does not display information about licensing for the locally managed mode of operation, as this is only possible on the 7010 and MSE 8710 platforms. Refer to the online help or administrator documentation for details of licensing in locally managed mode.
Platform licensing comparison Table 9: TelePresence Server conferencing capacity on various platforms (continued) Call type description Main video Audio Screen licenses required per call Content Maximum calls by hardware type (with licenses to provide 100% of capacity) 8 Cores VM Media 310 or MCU 5310 16 Cores VM Media 320 7010 or MCU 5320 MSE 8710 or Media MCU MSE 8510 400v‡ Biggest appliance Biggest blade cluster (two cluster (four appliances) blades) 4 5 screen screen licenses licenses 8 10
Platform licensing comparison ‡ To achieve the maximum number of calls, Cisco TelePresence Server on Virtual Machine must be the only VM hosted on the Multiparty Media 400v. It cannot be coresident with any other UC application (unlike the 8-core and 16-core VMs that run at 2.4GHz minimum and can be co-resident). Note: The table above assumes that calls of one type are being used to reach these maximum values.
Resolved issues The following issues were found in previous releases and are resolved in 4.0(2.8). Resolved since version 4.0(1.57) Identifier Description CSCup45147 When using a CTS or TX endpoint to connect an audio add-in participant, it was possible that a TelePresence Server could unexpectedly restart. This issue is now resolved. CSCun60259 In some instances it was possible to disable IPv4 over an IPv4 connection, and disable an IPv6 over an IPv6 connection. This issue is now resolved.
Resolved issues Identifier Description CSCup22629 Symptom: The following Cisco products: Cisco TelePresence Server 8710 / 7010 Cisco TelePresence Server on Media 3x0 Cisco TelePresence Server on Virtual Machine include a version of openssl that is affected by the vulnerabilities identified by the Common Vulnerability and Exposures (CVE) IDs: CVE-2014-0195 - DTLS invalid fragment vulnerability CVE-2014-0221 - DTLS recursion flaw CVE-2014-0224 - SSL/TLS MITM vulnerability CVE-2014-3470 - Anonymous ECDH de
Resolved issues Resolved since version 3.1(1.97) Identifier Description CSCuo21468 Symptom: The following Cisco Telepresence products: Cisco TelePresence Server 8710, 7010 Cisco TelePresence Server on Multiparty Media 310, 320 Cisco TelePresence Server on Virtual Machine include a version of openssl that is affected by the vulnerability identified by the Common Vulnerability and Exposures (CVE) ID CVE-2014-0160. This bug has been opened to address the potential impact on this product.
Open issues Identifier Description CSCun70776 The TelePresence Server event log was recording many messages of the form "RTCP : Info : call 1615, RTP session 2: message failed validity checks (invalid payload)". This issue is now resolved by reducing the severity of invalid messages. CSCuj26833 On 7010 and MSE 8710 TelePresence Server platforms, the application's CDR log was not properly recording remote teardown of H.323 calls. This issue is now resolved.
Limitations Identifier Description CSCuo72774 Symptom: If a new trust store is uploaded to a TelePresence Server, it will not take effect until after a system reboot. This means that certificates will continue to be checked and verified against the old trust store and undesired connections may still be established. Conditions: This issue will be encountered any time the trust store is updated without a reboot.
Limitations The following endpoints display significant orange or green flashes when they are using software versions between TX6.0.0 and TX6.0.4 in calls with TelePresence Server 3.1(1.
Limitations Calls from Microsoft Lync which do not use Advanced Media Gateway may fail For direct calls from Microsoft Lync or OCS you must use the VCS B2BUA. Calls may no longer work if configured through a VCS zone with profile "Microsoft Office Communication Server". For more information on configuring the VCS, refer to the VCS Administrator documentation.
Interoperability Interoperability The interoperability test results for this product are posted to http://www.cisco.com/go/tp-interop, where you can also find interoperability test results for other Cisco TelePresence products. Upgrading to 4.0(2.8) Prerequisites and software dependencies Software dependencies In the case of the TelePresence Server MSE 8710 blade(s), the Cisco TelePresence Supervisor MSE 8050 blade must be running Supervisor software version 2.2 or later.
Upgrading to 4.0(2.8) Backing up your configuration 1. In a web browser, navigate to the web interface of the device. 2. Sign in as an administrator. 3. Go to Configuration > Upgrade. 4. In the Back up and restore section, click Save backup file. 5. Copy the resulting configuration.xml file to a secure location. CAUTION: You must remember the administrator user name and password for the configuration backup file in case you ever need to use the backup.
Upgrading to 4.0(2.8) c. Right-click the TelePresence Server virtual machine and select Edit Settings… d. On the Hardware tab, click CPUs e. From the Number of cores per socket list, select the required number of virtual CPUs (vCPUs) Note: 16 vCPUs should map to 16 physical CPUs since oversubscription is not supported. f. Click OK g. Right-click the TelePresence Server virtual machine and select Power > Power On 3. You should also change the memory allocation from 16 GB to 8 GB as follows: a.
Upgrading to 4.0(2.8) Upgrade instructions 1. In a web browser, navigate to the web interface of the device. 2. Sign in as an administrator. The username is admin and there is no password on a new unit. 3. Go to Configuration > Upgrade. 4. In the Main software image section, locate the New image file field. Browse to and select the new image file. 5. Click Upload software image. The web browser uploads the file to the device, which may take a few minutes.
Using the Bug Search Tool Upgrading the font (optional) Note: These instructions apply only to TelePresence Server 7010 and MSE 8710 platforms. The Media 310/320 platforms always have the font pre-installed and there is no way to replace or remove it. Your device may be shipped with the TrueType font pre-installed. You can check this on the Status or Configuration > Upgrade page.
Technical support Technical support If you cannot find the answer you need in the documentation, check the website at www.cisco.com/cisco/web/support/index.html where you will be able to: n Make sure that you are running the most up-to-date software. n Get help from the Cisco Technical Support team. Make sure you have the following information ready before raising a case: n Identifying information for your product, such as model number, firmware version, and software version (where applicable).
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.
