Release Notes

Limitations
Cisco TelePresence Conductor Release Notes (XC2.3.1) Page 15 of 21
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 capacity versions only)
It does not support:
n T3 point to point calls escalated to a conference functionality
n Conference cascading on TelePresence Servers
n Auto-dialed participants that are multiscreen endpoints
n Advanced parameters for auto-dialed participants that are part of conferences hosted on TelePresence
Servers
n Geographic cascading with TelePresence Servers as conference bridges
n Scheduling with Cisco TMS using pools with multiple TelePresence Servers or pools with multiple
TelePresence MCUs of different sizes
n Use of dedicated audio ports on TelePresence MCUs
The following limitations apply to the three different capacity versions of the TelePresence Conductor:
TelePresence Conductor Essentials
(free)
TelePresence
Conductor Select
Full capacity
TelePresence
Conductor
Suitable deployment Small
Recommended for:
n testing and reviewing new releases
n proof of concept demonstrations
Small to medium-
sized
Medium-sized to
large
Total number of
conference bridges
supported
1 (standalone) 30 30
Maximum number of
concurrent call
sessions supported
The number of calls supported by the
conference bridge
50 2400
Clustering of
TelePresence
Conductors supported
for resilience
No Yes (limited to 2
TelePresence
Conductor Select)
Yes (up to 3 full
capacity
TelePresence
Conductors)
Access to
TACsupport
No (for deployment in production
environments we recommend upgrading
to one of the other two capacity versions)
Yes Yes