Cisco TelePresence Conductor XC2.3.1 Release Notes October 2014 Contents Product documentation New features in XC2 Resolved issues Open issues Limitations Interoperability Planned changes to future releases Upgrading to XC2.3.1 Downgrading from XC2.3.
New features in XC2 New features in XC2 New features in XC2.3.1 This is a maintenance release. New features in XC2.3 New Capacity Management API A new API allows management applications (such as Cisco TMS) to obtain information about a conference and its associated resources. The API returns information about the capacity of a conference bridge that will be used for a conference with a given dialed alias.
New features in XC2 Collaboration meeting room information available on the web interface You can use the Collaboration meeting rooms page to search for one or more Collaboration Meeting Rooms (CMRs) that have been configured via the TelePresence Conductor’s Provisioning API using a management tool such as Cisco TMS. For each CMR, details on aliases, auto-dialed participant and other related data can be viewed. The data associated with a CMR is configured via the Provisioning API.
New features in XC2 Encrypted iX passthrough Previously the iX protocol, used for example to support the ActiveControl feature on the TelePresence Server, was passed through the TelePresence Conductor’s B2BUA. Now the B2BUA also allows Encrypted iX to pass through. SIP Remote Party ID (RPID) passthrough The TelePresence Conductor’s B2BUA now supports the passthrough of SIP RPID, which is a SIP header used by Unified CM to convey calling and connected line identity.
New features in XC2 The xconfig and xstatus files are taken at the start of the logging process. n It is now possible to view all matching intrusion protection triggers for a particular category. New features in XC2.2.2 This is a maintenance release. New features in XC2.2.1 New option key supporting up to 50 concurrent call sessions From Cisco TelePresence Conductor version XC2.2.
New features in XC2 Automated intrusion protection An automated intrusion protection feature has been added. It can be used to detect and block malicious traffic and to help protect the TelePresence Conductor from dictionary-based attempts to breach login security. Automated protection should be used in combination with the existing firewall rules feature - use automated protection to temporarily block specific threats and use firewall rules to block permanently a range of known host addresses.
New features in XC2 Administrator authentication source When configuring the source for administrator account authentication, the Remote option is now labeled as Remote only. You can no longer access the TelePresence Conductor via a locally configured admin account if a Remote only authentication source is in use. The Local option has also been renamed to Local only. Improved user interface Changes have been made to improve the TelePresence Conductor user interface. New features in XC2.
New features in XC2 Addition of multiple IP addresses Multiple IP addresses can be added on TelePresence Conductor. A different IP address is needed on the TelePresence Conductor for each ad hoc Unified CM location and each rendezvous Unified CM location. This allows the TelePresence Conductor to mimic Unified CM's expectation that it is connecting to separate conference bridges in each location, for ad hoc and rendezvous calls.
Resolved issues Firewall rules Firewall rules can now be added to the TelePresence Conductor, which provide the ability to configure IP table rules to control access to the TelePresence Conductor at the IP level. Addition of multiple administrator accounts It is now possible to add multiple administrator accounts with pre-determined access level settings. Other changes and improvements Improvements have been made to the TelePresence Conductor web interface. Resolved issues Resolved in XC2.3.
Resolved issues Identifier Description CSCuo20306 Symptom: Cisco Telepresence Conductor includes 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. Conditions: Device with default configuration. The following Cisco Telepresence Conductor versions are affected by this vulnerability: XC2.0 XC2.1 XC2.2 XC2.2.1 Workaround: Not currently available.
Resolved issues Identifier Description CSCuo20306 Symptom: Cisco Telepresence Conductor includes 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. Conditions: Device with default configuration. The following Cisco Telepresence Conductor versions are affected by this vulnerability: XC2.0 XC2.1 XC2.2 XC2.2.1 Workaround: Not currently available.
Resolved issues Identifier Description CSCui21923 The Cisco TelePresence Conductor with Cisco Unified Communications Manager Deployment Guide (XC2.1) detailed steps on how to upload a self-signed server certificate to TelePresence Conductor. Because Unified CM may not support the default TelePresence Conductor server certificate the recommendation has been changed to use an officially signed server certificate instead. CSCuh15866 MCU 4501 running 4.4(3.
Resolved issues Identifier Description CSCue89279 Symptom: FUR (Fast picture update) messages get dropped if they contain a stream ID - this means that no video or blocky video may be seen, especially if the data network drops video packets. TS prior to TS3.0(2.46) did not send stream IDs for main video. Diagnosis: This problem will only be seen if Conductor without this fix in is used with TS >= 3.0 (2.46). Versions affected: XC2.0 and XC2.0.1 Workaround: Avoid upgrading TS to >= 3.0 (2.
Open issues Open issues The following issues apply to this version of the Cisco TelePresence Conductor. Identifier Description CSCun63044 Symptom: The Conductor documentation does not describe in detail how the implementation of syslog works. There is no documentation as to what messages match what facilities. Versions affected: XC1.
Limitations n 30 conference bridges n 30 conference bridge pools n 30 Service Preferences n 1000 conference templates n 1000 conference aliases n Conference bridge types of Cisco TelePresence MCU and Cisco TelePresence Server n Conference cascading on TelePresence MCUs only n Scheduling with Cisco TMS using either a single TelePresence Server, a single TelePresence MCU or a pool of identical sized TelePresence MCUs n Clustering of up to 3 TelePresence Conductors to achieve resilience (full
Interoperability Available as virtual machine or appliance TelePresence Conductor Essentials (free) TelePresence Conductor Select Virtual machine only Virtual machine only Virtual machine and appliance Release and option No release or option key required keys required to install Option key to support 50 concurrent call sessions required Full capacity TelePresence Conductor Full capacity TelePresence Conductor release key required Scheduling with Cisco TMS As the scheduling solution with Cisco TMS
Upgrading to XC2.3.1 n Removal of the following feature: l Support for TelePresence Conductor working as a policy server with the Cisco VCS. In a future release TelePresence Conductor must be deployed using TelePresence Conductor's back-to-back user agent (B2BUA), with a SIP trunk to a Cisco VCS or a Unified CM. n Changes to the minimum supported versions for the following products: l For Cisco VCS: version X7.2 or later l For Unified CM: version 9.1.2 or later Upgrading to XC2.3.
Downgrading from XC2.3.1 2. Log into the web interface. 3. Create a backup of your configuration (under Maintenance > Backup and restore). 4. Upgrade using the Upgrade page (Maintenance > Upgrade) as described in the Cisco TelePresence Conductor Administrator Guide. Downgrading from XC2.3.1 When downgrading from XC2.3.1 to XC2.2 or earlier, it is important that you do not use the same configuration that you had on the system while running XC2.3.1.
Additional information To view a list of Cisco TelePresence products that are no longer being sold and might not be supported, visit: www.cisco.com/en/US/products/prod_end_of_life.html and scroll down to the TelePresence section. Additional information Secure communications For secure communications (HTTPS and SIP/TLS) we recommend that you replace the Cisco TelePresence Conductor default certificate with a certificate generated by a trusted certificate authority.
Document revision history Document revision history Date Revision Description October 2014 12 Release of Cisco TelePresence Conductor XC2.3.1 April 2014 10 Release of Cisco TelePresence Conductor XC2.2.2 April 2014 09 Release of Cisco TelePresence Conductor XC2.0.3 April 2014 08 Release of Cisco TelePresence Conductor XC2.3 February 2014 07 Updated description of minimum version alarm feature October 2013 07 Release of Cisco TelePresence Conductor XC2.2.
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.
