Cisco Cisco TelePresence Management Suite (TMS) Version 15
Migrating from and reverting to standalone MCUs
This section covers the scenario where you already have MCUs in Cisco TMS which you have scheduled in
future conferences, and how to move those conferences onto the TelePresence Conductor. It also covers
the scenario where you want to remove TelePresence Conductor and go back to using individual MCUs for
your future booked conferences.
future conferences, and how to move those conferences onto the TelePresence Conductor. It also covers
the scenario where you want to remove TelePresence Conductor and go back to using individual MCUs for
your future booked conferences.
Migrating from stand-alone MCUs
If you have MCUs which are already added to your TelePresence Conductor in Cisco TMS, they will
probably have been booked in future conferences, and call history will have been stored for these MCUs in
Cisco TMS.
probably have been booked in future conferences, and call history will have been stored for these MCUs in
Cisco TMS.
When you transition to TelePresence Conductor scheduling, Cisco TMS and TelePresence Conductor will
have no knowledge of the resources which have already been booked on these MCUs, which may lead to
double-bookings, failed calls, and erroneous monitoring data. To avoid this, follow the migration strategy
presented below:
have no knowledge of the resources which have already been booked on these MCUs, which may lead to
double-bookings, failed calls, and erroneous monitoring data. To avoid this, follow the migration strategy
presented below:
1. Once the TelePresence Conductor has been set up, add it to Cisco TMS and configure the aliases.
In the IP Address or FQDN field, make sure to match the MCU's connection setting in Cisco TMS as
described in
described in
3. Go to
Systems > Navigator
and select the TelePresence Conductor.
a. Open the
Settings
tab.
b. Click Force Refresh.
Cisco TMS will now know that the MCUs are part of the TelePresence Conductor's Conference
bridge pools.
bridge pools.
5. For each MCU:
a. Go to
Systems > Navigator
and select the MCU.
b. Open the
Settings
tab.
c. Click Force Refresh.
This will stop the MCUs from being directly bookable.
6. Go to
Booking > List Conferences
.
7. Filter on all the MCUs and select the date range that covers all your future bookings. Click Search.
8. Edit each conference:
a. Click on each conference to launch the
View Conference
window, then click Edit.
If the booking is part of a recurrent series and you have made changes to individual instances, select
Edit this occurrence to make the necessary changes to each individual instance. Updating an entire
series at once will re-book the conference series and cancel any changes to individual instances.
Edit this occurrence to make the necessary changes to each individual instance. Updating an entire
series at once will re-book the conference series and cancel any changes to individual instances.
b. Remove the MCU as a participant, then click Save.
This will generate a new route using the TelePresence Conductor.
Any changes that were made when booking the initial conference, such as call direction, must be
made again. Distribution will be handled automatically.
Any changes that were made when booking the initial conference, such as call direction, must be
made again. Distribution will be handled automatically.
c. As all dial-in participants will now have a new dial-in number, forward the new conference confirmation
email to the participants to make them aware of the change.
d. Repeat the above steps for each conference.
Cisco TelePresence Conductor with Cisco TMS Deployment Guide
Page 18 of 21
Migrating from and reverting to standalone MCUs