Cisco Cisco TelePresence Management Suite (TMS) Version 15
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.
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:
■
.
■
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.
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.
Update CMR templates to Support Multiparty license
When Cisco TMSPE and Conductor are upgraded to support Multiparty license. The CMR templates associated with the
Conductor that support Multiparty license must follow the below mentioned steps:
Conductor that support Multiparty license must follow the below mentioned steps:
1.
Edit CMR templates.
2.
Select the required Multiparty License Mode.
3.
Click the Save button to update the templates.
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.
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.
in the currently active location. The results of the searches for each device are also shown.
Uninstalling Cisco TMSPE
There are two ways to uninstall Cisco TMSPE. The operation will be logged in different locations depending on your
system configuration and the uninstallation method, as described below. No log data is deleted by uninstalling Cisco
TMSPE.
system configuration and the uninstallation method, as described below. No log data is deleted by uninstalling Cisco
TMSPE.
Using the Installer
1.
Run the installer.
2.
Follow the onscreen instructions to uninstall.
90
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide