Release Notes

Interoperability
Cisco TelePresence Conductor Release Notes (XC2.3.1) Page 16 of 21
TelePresence Conductor Essentials
(free)
TelePresence
Conductor Select
Full capacity
TelePresence
Conductor
Available as virtual
machine or appliance
Virtual machine only Virtual machine only Virtual machine and
appliance
Release and option
keys required to install
No release or option key required Option key to
support 50
concurrent call
sessions required
Full capacity
TelePresence
Conductor release
key required
Scheduling with Cisco TMS
As the scheduling solution with Cisco TMS has notable limitations at this time, we recommend carefully
considering these limitations and their workarounds prior to deployment. Upcoming releases of TelePresence
Conductor and Cisco TMS will address these limitations, and an updated deployment guide for TelePresence
Conductor with Cisco TMS will be made available at that time.
Current limitations:
n TelePresence Conductor does not properly load balance multiple scheduled meetings beginning at the
same time across multiple TelePresence MCUs or TelePresence Servers in a bridge pool.This can lead to
situations where one TelePresence MCU or TelePresence Server will fill up and calls will be rejected while
others in the same bridge pool are underutilized.
l As a workaround for TelePresence MCUs, we recommend only adding identical capacity TelePresence
MCUs to a bridge pool and configuring either a content, chairperson, or cascade port on the conference
template. Bug toolkit identifier for this issue: CSCui42818 [p.14].
l As a workaround for TelePresence Servers, we recommend only adding one TelePresence Server to a
bridge pool. Bug toolkit identifier for this issue: CSCui42822 [p.14].
n TelePresence Conductor may wait up to 30 seconds before releasing resources between meetings. This
may cause denial of inbound and outbound calls for back-to-back meetings and utilization spikes when
participants repeatedly leave and join a meeting. Bug toolkit identifier for this issue: CSCuf34880 [p.14]
n Cisco TMS scheduling with TelePresence Conductor does not currently support WebEx Enabled
TelePresence.
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.
If using Cisco TMS with TelePresence Conductor XC2.3, we recommend installing Cisco TMS version 14.4
or later. Older versions of Cisco TMS have the following limitations:
n There is an interoperability issue between XC2.3 and Cisco TMS version 14.3.2 (CDETS reference:
CSCun79003).
n Some XC2.3 features are not supported when running Cisco TMS version 14.3.2 or earlier.
Planned changes to future releases
In a future version of TelePresence Conductor the following changes are planned: