Cisco Cisco TelePresence Management Suite (TMS) Version 15
Look for the log message INFO ReplicationEngine - No changes on TMS to verify that
replication has completed.
replication has completed.
Task 41: Identifying and correcting declined, downgraded, or
defective meetings
defective meetings
Identify and mitigate booking issues as soon as possible after migration. If there is a large quantity of
meetings to process, you can continue investigation and mitigation after cutover, but note that the logs are
not chronological by meeting date. When dealing with defective meetings through Cisco TMS, we
recommend sorting by date and dealing with shortly upcoming meetings first.
meetings to process, you can continue investigation and mitigation after cutover, but note that the logs are
not chronological by meeting date. When dealing with defective meetings through Cisco TMS, we
recommend sorting by date and dealing with shortly upcoming meetings first.
Declined and downgraded meetings
Reading the logs
Logs for Cisco TMSXE are available in the default location C:\ProgramData\Cisco\Cisco TMSXE\Logs.
An entry will be created in the TMSXE_decline_downgrade_log_file_YYYYMMDD.txt log for each
participant that is declined or downgraded.
participant that is declined or downgraded.
Example log entries for typical decline scenarios:
n
2014-08-19 14:39:50,402 [30] INFO TMSXEBestEffortCommitter - Saving conference as requested was
declined (conference can never be booked): Unexpected recurrence pattern frequency type encountered:
Yearly
declined (conference can never be booked): Unexpected recurrence pattern frequency type encountered:
Yearly
n
2014-08-19 14:39:50,318 [10] INFO TMSXEBestEffortCommitter - Saving conference as requested was
declined (conference can never be booked): Number of occurrences must be between 1 and 100.
declined (conference can never be booked): Number of occurrences must be between 1 and 100.
Re-creating declined meetings
Any meetings that were incompatible with Cisco TMS and not corrected before import, will have been
declined during import. This includes:
declined during import. This includes:
n
meetings outside of the specified booking window.
n
recurrent meetings with more occurrences than Cisco TMS supports.
n
meetings that were booked in the same timeslot as another meeting (double booking).
To resolve declined meetings:
1. Identify the declined meetings using the log.
2. Do one of the following:
l
Re-create these bookings in Cisco TMS on behalf of the organizers at an available time with a
supported recurrence pattern.
supported recurrence pattern.
l
Contact the organizers and ask them to re-create their bookings using Outlook.
Note that declined meetings that are re-created after import will not be processed by Meeting Updater. All
changes to properties must be made directly in Cisco TMS.
changes to properties must be made directly in Cisco TMS.
Correcting downgraded meetings
When one or more participants cannot be scheduled into a meeting due to configuration issues such as
missing software licenses or booking permissions, or scheduling with the endpoint has been disabled, Cisco
TMSXE will try to downgrade the meeting rather than decline:
missing software licenses or booking permissions, or scheduling with the endpoint has been disabled, Cisco
TMSXE will try to downgrade the meeting rather than decline:
Replacing Cisco TelePresence Manager with Cisco TMS and Cisco TMSXE Deployment Guide (14.5 and
4.1)
4.1)
Page 41 of 51
Cutover (downtime)