Cisco Cisco TelePresence Management Suite (TMS) Version 15
Limitations
n
On TelePresence Conductor, templates can have related auto-dialed participants so that every time a
conference is created based on that template, one or more participants are dialed automatically and join the
conference. Administrators must be aware that if there are auto-dialed participants configured for
templates, more resources will be used than are visible in Cisco TMS.
conference is created based on that template, one or more participants are dialed automatically and join the
conference. Administrators must be aware that if there are auto-dialed participants configured for
templates, more resources will be used than are visible in Cisco TMS.
n
If TelePresence Conductor is clustered, Cisco TMS will not take advantage of multiple peers and will only
use a single TelePresence Conductor. For this reason, in a clustered TelePresence Conductor
environment, add only one of the TelePresence Conductor peers to Cisco TMS.
use a single TelePresence Conductor. For this reason, in a clustered TelePresence Conductor
environment, add only one of the TelePresence Conductor peers to Cisco TMS.
n
Cisco TMS cannot change any settings on the TelePresence Conductor. In
Systems > Navigator >
select a TelePresence Conductor
> Settings
tab
> Edit Settings
, the Max Number of Concurrent
Scheduled Calls setting does not influence the TelePresence Conductor in any way. This setting allows
administrators to restrict the resources Cisco TMS will schedule for the TelePresence Conductor. See
administrators to restrict the resources Cisco TMS will schedule for the TelePresence Conductor. See
.
n
Call Detail Records (CDRs) from TelePresence Conductor-managed MCUs will not contain any
ConferenceIDs.
ConferenceIDs.
n
TelePresence Conductor itself does not feed back any conference CDRs to Cisco TMS.
n
IP dialing is not supported when scheduling conferences with a TelePresence Conductor.
The following scheduling options are not supported for TelePresence Conductor in Cisco TMS:
n
Media port reservation—do not enable this on the MCUs.
n
Conference templates
n
Participant templates
n
Distribution
n
TelePresence Conductor conference type Lecture. Only conference templates using the Meeting
conference type are supported.
conference type are supported.
MCU Failover
When using a TelePresence Conductor in front of MCUs, the following must be noted:
n
Cisco TMS will poll the TelePresence Conductor, not the MCUs, so will have no knowledge of whether an
MCU has failed. MCU failover where Cisco TMS moves participants to another MCU if the one hosting the
conference fails is not supported when a TelePresence Conductor is used. Instead if the Cisco TMS
connection to the TelePresence Conductor fails, Cisco TMS will move the conference to another
TelePresence Conductor or available MCU.
MCU has failed. MCU failover where Cisco TMS moves participants to another MCU if the one hosting the
conference fails is not supported when a TelePresence Conductor is used. Instead if the Cisco TMS
connection to the TelePresence Conductor fails, Cisco TMS will move the conference to another
TelePresence Conductor or available MCU.
n
We recommend that the setting:
Cisco TMS > Administrative Tools > Configuration > Conference
Settings >
Automatic MCU Failover: If conference start or MCU polling fails is not used, as it is possible
that Cisco TMS could lose the connection to the TelePresence Conductor but that all the participants and
MCUs are still connected to each other and the conference has not been affected. If you want to use
Automatic MCU Failover we recommend choosing: If conference start fails.
MCUs are still connected to each other and the conference has not been affected. If you want to use
Automatic MCU Failover we recommend choosing: If conference start fails.
Cisco TelePresence Conductor with Cisco TMS Deployment Guide
Page 20 of 21
Limitations