Cisco Cisco TelePresence Management Suite (TMS) Version 15 Installation Guide
1. In Cisco VCS, go to
Status > Logs > Event Log
.
2. If the log contains an error message similar to this, Cisco TMSPE has not been set up with a template for
the device:
provisioning: Level="ERROR" Detail="Failed to provision user" User-URI="
provisioning: Level="ERROR" Detail="Failed to provision user" User-URI="
[user's SIP URI]" Reason="No provisioning template document found" Device-
.
Warning displayed when uploading configuration schema
If a warning appears in the Cisco TMSPE administrative interface when uploading a schema, this may be
due to a web server configuration issue where HTTP PUT requests are stopped by IIS:
due to a web server configuration issue where HTTP PUT requests are stopped by IIS:
1. Open IIS Manager on the Cisco TMSPE server.
2. Select the Cisco TMSPE web application (<machinename>/Sites/Default Web
Site/tmsagent
).
3. In the middle pane, double-click on Request Filtering.
4. In the same pane, select the
HTTP Verbs
tab.
5. Ensure that PUT is set to Allowed=True.
If PUT is already enabled for the web application, check whether server-wide settings are overriding
individual webapp configurations.
individual webapp configurations.
Note that this issue is only seen when WebDAV Publishing is an IIS Role Service.
No phone books received
If one or more provisioning users are not receiving phone books on their devices:
n
.
n
Ensure that phone book requests from provisioned devices are handled by the same Cisco VCS or cluster
that has provisioned the devices in question. If the phone book requests are being sent to a different
provisioning-enabled VCS, the requests will fail, and phone books cannot be made available to the devices.
that has provisioned the devices in question. If the phone book requests are being sent to a different
provisioning-enabled VCS, the requests will fail, and phone books cannot be made available to the devices.
Portal troubleshooting
Cannot access FindMe or Smart Scheduler
Error message: Access denied. Verify that all critical Windows Updates are installed on the server.
Using search history to diagnose FindMe issues
Looking at search history (on the Cisco VCS or Cisco VCS cluster that hosts the relevant user account) is
usually the best place to start diagnosing FindMe-related problems.
usually the best place to start diagnosing FindMe-related problems.
The search history shows the search for the FindMe ID and then how User Policy forks the call to look at all
the devices in the currently active location. The results of the searches for each device are also shown.
the devices in the currently active location. The results of the searches for each device are also shown.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide (1.4)
Page 92 of 96
Troubleshooting