Cisco Cisco TelePresence Management Suite (TMS) Version 15
4. Select which updates to include. The count of eligible meetings will update based on your choices.
5. Click Start.
Meeting Updater will try to add the desired properties to bookings in Cisco TMS.
Bookings that did not include any affected properties will be left untouched by Meeting Updater.
Once the update has completed, Meeting Updater displays a link to a log file containing detail on any
failed attempts. The log is also in .tsv format and can be opened in Excel for ease of sorting and filtering.
Bookings that did not include any affected properties will be left untouched by Meeting Updater.
Once the update has completed, Meeting Updater displays a link to a log file containing detail on any
failed attempts. The log is also in .tsv format and can be opened in Excel for ease of sorting and filtering.
Resolving remaining meeting feature issues
Any remaining feature discrepancies need to be handled directly in Cisco TMS:
1. Using the log obtained from Meeting Updater, identify any meetings that the tool failed to update.
l
If Meeting Updater failed to add one feature failed for all meetings, such as WebEx, correct any
configuration issues and run the tool again. CMR Hybrid must be correctly set up for this feature to
work.
configuration issues and run the tool again. CMR Hybrid must be correctly set up for this feature to
work.
l
Manually address any remaining failures by updating the individual bookings in Cisco TMS.
2. Using the exported meeting data from Cisco TelePresence Manager to identify affected meetings, you can
manually add:
l
Recording: Add a recording participant to affected meetings.
l
Intercompany meetings hosted by another company: Create a dial-out participant for the externally
provided video address. If more than one company-internal participant was booked, create a separate
booking with the same dial-out for each participant.
provided video address. If more than one company-internal participant was booked, create a separate
booking with the same dial-out for each participant.
Task 43: Checking for additional defective meetings
After running Meeting Updater, verify that all meetings are still routable:
1. In Cisco TMS, go to
Administrative Tools > Diagnostics > Conferences Diagnostics
.
2. Select all entries.
3. Click Autocorrect.
Cisco TMS will now attempt to re-save all problematic conferences and series, re-routing any instances
or series as necessary.
or series as necessary.
4. Click Refresh to see an updated status field for each entry. When no more entries are in the Autocorrect
Pending state, go through any remaining entries one by one to determine what caused the booking to be
defective and how to resolve it:
defective and how to resolve it:
a. Click on the conference title to view the conference information page.
b. Click on the
b. Click on the
Event Log
tab on the lower half of the conference information page. The log will display
detail on the routing and/or resource issue.
c. Click Edit and update the booking properties as required to resolve the issue; typically:
o
If the problem is a temporary lack of bridge resources, the conference must be moved or made less
resource intensive (remove participants).
resource intensive (remove participants).
o
If the problem is a permanent lack of bridge resources, the environment needs more resources
before the booking can be resolved.
before the booking can be resolved.
The Cisco TMS booking interface will only allow you to save your changes if the changes resolve all
the booking issues. Meetings cannot be saved as Defective when booking from Cisco TMS itself.
the booking issues. Meetings cannot be saved as Defective when booking from Cisco TMS itself.
Replacing Cisco TelePresence Manager with Cisco TMS and Cisco TMSXE Deployment Guide (14.5 and
4.1)
4.1)
Page 44 of 51
Cutover (downtime)