Cisco Cisco TelePresence Management Suite (TMS) Version 15
Introduction
(D14827).
This document describes how to configure Cisco TelePresence Conductor, Cisco VCS and Cisco
TelePresence MCUs with Cisco TMS. This deployment enables scheduling of conferences with participants
hosted on MCUs behind a TelePresence Conductor.
TelePresence MCUs with Cisco TMS. This deployment enables scheduling of conferences with participants
hosted on MCUs behind a TelePresence Conductor.
You will be shown how to configure the TelePresence Conductor with templates and aliases that are
reserved for scheduling. These templates and aliases can be configured to use bridges that are only used by
scheduled conferences to guarantee availability, or can use bridges shared with Rendezvous conference
calls for optimum bridge utilization.
reserved for scheduling. These templates and aliases can be configured to use bridges that are only used by
scheduled conferences to guarantee availability, or can use bridges shared with Rendezvous conference
calls for optimum bridge utilization.
This document also details how to book and edit conferences with this deployment. A section on limitations
is included at the end.
is included at the end.
For administrators with a Cisco TMS and MCUs already in place who are introducing a TelePresence
Conductor to their environment, the document describes how to migrate so that existing future conferences
are rebooked on the TelePresence Conductor. Reverting back to standalone MCUs is also covered.
Conductor to their environment, the document describes how to migrate so that existing future conferences
are rebooked on the TelePresence Conductor. Reverting back to standalone MCUs is also covered.
Administrators implementing TelePresence Conductor Scheduling with Cisco TMS are assumed to be
familiar with all the infrastructure products included in the deployment.
familiar with all the infrastructure products included in the deployment.
TelePresence Conductor scheduling limitations
Several limitations to TelePresence Conductor scheduling have been discovered since the release of Cisco
TMS 14.1, TelePresence Conductor XC1.2, and this document.
TMS 14.1, TelePresence Conductor XC1.2, and this document.
The following are open TelePresence Conductor issues at the time of XC2.2 release:
n
TelePresence Conductor does not properly load balance multiple scheduled meetings beginning at the
same time across multiple MCUs or TelePresence Servers in a bridge pool. This can lead to situations
where one MCU or TelePresence Server will fill up and calls will be rejected while others in the same bridge
pool are underutilized.
same time across multiple MCUs or TelePresence Servers in a bridge pool. This can lead to situations
where one 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 MCUs, we recommend only adding identical capacity MCUs to a bridge pool and
configuring either a content, chairperson, or cascade port on the Conference Template. Bug toolkit
identifier: CSCui42818.
configuring either a content, chairperson, or cascade port on the Conference Template. Bug toolkit
identifier: CSCui42818.
l
As a workaround for TelePresence Server, we recommend only adding one TelePresence Server to a
bridge pool. Bug toolkit identifier: CSCui42822.
bridge pool. Bug toolkit identifier: CSCui42822.
n
In some situations, Cisco TMS is unable to add more than 30 dial-out participants to TelePresence
Conductor-scheduled meetings, while dial-in participants are still able to join. Bug toolkit identifier:
CSCui59829.
Conductor-scheduled meetings, while dial-in participants are still able to join. Bug toolkit identifier:
CSCui59829.
n
TelePresence Conductor waits 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: CSCuf34880.
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: CSCuf34880.
The above limitations will be addressed in coming releases of TelePresence Conductor and Cisco TMS. An
updated deployment guide for Cisco TMS with TelePresence Conductor will be made available at that time.
updated deployment guide for Cisco TMS with TelePresence Conductor will be made available at that time.
The following issues have been addressed in Cisco TMS 14.3:
n
In some situations, Cisco TMS would not add dial-out participants to conferences scheduled with
TelePresence Conductor due to not determining that the meeting was successfully created. Dial-in
TelePresence Conductor due to not determining that the meeting was successfully created. Dial-in
Cisco TelePresence Conductor with Cisco TMS Deployment Guide
Page 3 of 21
Introduction