Cisco Cisco TelePresence Management Suite (TMS) Version 15
Limitations
n
On TelePresence Conductor, templates can have related auto-dialed participants. Every time a conference
is created based on that template, one those participants are dialed automatically and join the conference.
Note that if there are auto-dialed participants configured for templates, more resources will be used than are
visible in Cisco TMS.
is created based on that template, one those participants are dialed automatically and join the conference.
Note 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
Call Detail Records (CDRs) from TelePresence Conductor-managed conference bridges will not contain
any ConferenceIDs.
any ConferenceIDs.
n
TelePresence Conductor itself does not feed back any conference CDRs to Cisco TMS.
Note that 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
Cisco TMS 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
If you are using direct-managed bridges, and MCU Failover is enabled, Cisco TMS moves participants to
another bridge if the one hosting the conference fails.
another bridge if the one hosting the conference fails.
When using a TelePresence Conductor to manage conference bridges, the following must be noted:
n
Cisco TMS will poll the TelePresence Conductor, not the bridges, and will have no knowledge of whether a
bridge has failed. MCU failover as described above 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 bridge.
bridge has failed. MCU failover as described above 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 bridge.
n
If you choose the option:
Cisco TMS > Administrative Tools > Configuration > Conference Settings
>
Automatic MCU Failover: If conference start or MCU polling fails, conferences including a
TelePresence Conductor will only failover if conference start fails (Cisco TMS cannot contact the
TelePresence Conductor). Failover will not occur if polling the TelePresence Conductor fails: this is to
avoid disconnection of conferences that are successfully taking place despite Cisco TMS having lost
connection with the TelePresence Conductor.
TelePresence Conductor). Failover will not occur if polling the TelePresence Conductor fails: this is to
avoid disconnection of conferences that are successfully taking place despite Cisco TMS having lost
connection with the TelePresence Conductor.
Cisco TelePresence Conductor with Cisco TMS Deployment Guide (XC3.0 with 14.6)
Page 8 of 25
Limitations