Cisco Cisco TelePresence Management Suite (TMS) Version 15
Reverting back to standalone MCUs
1. In the TelePresence Conductor's web interface, delete the MCUs from all Conference bridge pools. This
may require deletion of any bridge pools, service preferences, templates and aliases that reference these
MCUs.
It is essential that you delete the MCUs, rather than simply disabling them, as the latter would not
disassociate them from the TelePresence Conductor in Cisco TMS.
MCUs.
It is essential that you delete the MCUs, rather than simply disabling them, as the latter would not
disassociate them from the TelePresence Conductor in Cisco TMS.
2. In the the web interface of each MCU:
a. Go to
Settings > H.323
and enable Allow numeric ID registration for conferences.
b. Go to
Settings > SIP
and enable Allow numeric ID registration for conferences.
3. In Cisco TMS, 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 no longer part of the TelePresence Conductor's
Conference bridge pools.
Conference bridge pools.
4. In Cisco TMS, for each MCU:
a. Go to
Systems > Navigator
and select the MCU.
b. Open the
Settings
tab.
c. Click Force Refresh.
d. Go to
d. Go to
Edit Settings
e. In the
TMS Scheduling Settings
section, enable Allow Booking and the appropriate Allow
incoming... and Allow outgoing... dialing options.
5. Go to
Booking > List Conferences
.
6. Filter on the TelePresence Conductor and select the date range that covers all your future bookings. Click
Search.
7. 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 TelePresence Conductor as a participant, then click Save.
This will generate a new route using one or more MCUs.
Any changes that were made when booking the initial conference, such as call direction, must be
made again.
Any changes that were made when booking the initial conference, such as call direction, must be
made again.
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.
8. Ensure that the Cisco VCS is configured with appropriate neighbor zones and search rules so that it will
route the relevant aliases to the relevant MCUs.
Cisco TelePresence Conductor with Cisco TMS Deployment Guide
Page 19 of 21
Migrating from and reverting to standalone MCUs