Cisco Cisco TelePresence Management Suite (TMS) Version 15
n
All participants will be tentatively booked as Reservation.
n
Failing participants will then be declined, and if no participants can be booked, this meeting will also be a
decline and must be handled as described above.
decline and must be handled as described above.
To correct a downgraded meeting:
1. Identify the downgraded meetings and failing participants using the log.
2. Correct the configuration or license issue for the failing participants.
3. Using Cisco TMS, re-add the corrected participants to the original bookings.
4. For each downgraded meeting, change the Type to One Button To Push.
Defective meetings
About defective meetings
A Defective conference in Cisco TMS has been booked by an external client that encountered a resource
conflict or routing problem.
conflict or routing problem.
A defective conference retains all properties of the booking request without setting up routing or consuming
telepresence resources. Until all issues are resolved, Cisco TMS will not initiate a defective conference or
send it to endpoints.
telepresence resources. Until all issues are resolved, Cisco TMS will not initiate a defective conference or
send it to endpoints.
n
In the case of a routing issue, all endpoints in the booking will be set to Busy for the scheduled time,
keeping the reservation while the administrator or user resolves the issue.
keeping the reservation while the administrator or user resolves the issue.
n
In the rare case of an endpoint reservation conflict, the endpoints will not be set to Busy for the defective
booking.
booking.
Defective conferences can be corrected by the organizer or the administrator:
n
Users who book conferences that are saved as defective will be notified by email and can resolve most
issues by changing their request and rescheduling from their client.
issues by changing their request and rescheduling from their client.
n
Administrators can locate and resolve defective conferences in Cisco TMS by going to
Administrative
Tools > Diagnostics > Conference Diagnostics
or
Booking > List Conferences
.
Conferences that are defective because of configuration errors or a permanent lack of routing resources
must be resolved by an administrator.
must be resolved by an administrator.
When scheduling a series where only some occurrences have a resource conflict or routing issue, Cisco
TMS will only store the problematic occurrences as defective, leaving the remaining occurrences unaffected.
TMS will only store the problematic occurrences as defective, leaving the remaining occurrences unaffected.
Correcting defective meetings
To identify and attempt to correct all bookings saved as Defective during import, we recommend the
following procedure:
following procedure:
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:
Replacing Cisco TelePresence Manager with Cisco TMS and Cisco TMSXE Deployment Guide (14.5 and
4.1)
4.1)
Page 42 of 51
Cutover (downtime)