Release Notes

New features in XC2
Cisco TelePresence Conductor Release Notes (XC2.3.1) Page 5 of 21
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.1 a new option key is available for the Virtual Machine
TelePresence Conductor which supports up to 50 concurrent call sessions. This option key can be obtained
from your Cisco representative. It provides access to Cisco TAC(Technical Assistance Center) support and
is suitable for small and medium-sized deployments.
See Limitations [p.14] for information on the limitations when running TelePresence Conductor with this
option key installed.
New features in XC2.2
Improved TIP-compliant endpoint support
Multiscreen endpoints that are compliant with the TelePresence Interoperability Protocol (TIP) do not need to
be pre-configured any longer. The TelePresence Conductor is now able to retrieve the number of screens and
the associated resources that are required on the conference bridge via TIP.The TelePresence Conductor no
longer over-allocates resources on the conference bridge for multiscreen endpoints.
However, these improvements are only applicable to deployments where SIP signaling is routed via the
TelePresence Conductor; Cisco VCS deployments using the external policy service continue to work as in
previous releases. Additionally, the TelePresence Conductor still over-allocates resources initially for
reserved chairperson participants and for escalated Unified CMad hoc conferences.
360p video support
The TelePresence Conductor now supports 360p video for TelePresence Servers running software version
3.1 or later. There is a new pre-defined quality level with 360p video and mono audio defined that can be
selected for conference templates and pre-configured endpoint codecs. New quality levels can be added that
use 360p video.
Support for TelePresence Server software on new hardware
The TelePresence Conductor now supports new hardware platforms for the TelePresence Server software
version 3.1. It supports the platforms CiscoMultiparty Media 310 and Cisco Multiparty Media 320, as well as
the Cisco TelePresence Server on Virtual Machine.
Alarm for minimum conference bridge version
The TelePresence Conductor now raises a minimum version alarm when connected to a TelePresence MCU
running version 4.3 or lower, and when connected to a TelePresence Server running version 3.0 in remotely
managed mode. If a TelePresence Server is running version 2.x and/or is in locally managed mode,
TelePresence Conductor will raise an alarm stating that the conference bridge is running in the wrong mode.
These older conference bridge versions do not support some of the new features for XC2.2.