Release Notes

New features in XC2
Cisco TelePresence Conductor Release Notes (XC2.3.1) Page 8 of 21
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.
Known and unknown multiscreen endpoint support for TelePresence Server conferences
The TelePresence Conductor supports endpoints with more than one screen in conferences hosted on
TelePresence Servers.
Cisco TelePresence System (CTS) series endpoints, including Cisco TelePresence System T3, can be pre-
configured, in which case they will be allocated the resources defined for the endpoint, or supported without
pre-configuration, in which case they will be allocated the resources defined for the conference template.
Other customized multiscreen endpoints have to be pre-configured if sufficient resources are to be allocated
on the TelePresence Servers used in the relevant conferences.
Support for third-party and customized multiscreen TelePresence systems (i.e. those other than CTS3xxx,
TX9000 or T3) require the optional third-party interop key on the TelePresence Server.
Resource optimization
Resource optimization allows resources that are initially over-allocated on a TelePresence Server to be
recovered and re-allocated for other participants, allowing more participants to be handled by a single
TelePresence Server.
XML-RPCAPI support to communicate between Cisco TMS and TelePresence Server 3.0
The TelePresence Conductor APInow has support added to translate information being sent between Cisco
TelePresence Management Suite and TelePresence Server version 3.0 running in 'Remotely managed'
mode. See Cisco TelePresence Management Suite Release Notes for information on when this support has
been added to the Cisco TMS.
Improvements to logging
Filtered event logs can now be downloaded from the UI.
It is possible to specify the remote syslog server mode as one of the following:
n Legacy BSDformat
n IETF syslog format
n IETF syslog using TLS connection
n Custom
The Configuration Log page provides a list of all changes to the TelePresence Conductor configuration,
providing users with an audit trail of the TelePresence Conductor configuration.
System Administration session timeout and limits
It is now possible to set a session time out, as well as limits for concurrent sessions and concurrent logins
per administrator account for web, SSH and serial sessions.
Certificate signing request (CSR)
The TelePresence Conductor can now generate server certificate signing requests, which removes the need
to use an external mechanism to generate and obtain certificate requests.