Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
Request timed out,
no response
no response
The Cisco TMS server is busy, try again.
Warning: directory
data not retrieved:
404
data not retrieved:
404
■
The endpoint is configured with the IP address of a different web server than the Cisco TMS
server.
server.
■
The corporate directory path on the endpoint is wrong.
Warning: directory
data not retrieved:
401
data not retrieved:
401
■
The "Public" virtual directory on the Cisco TMS server is not configured to allow Anonymous
Access.
Access.
■
The most common problem here is that anonymous access is set, but the account used has
been overwritten by a group policy. The default IUSR user is a part of the guest account,
and typically group policies disable this account.
been overwritten by a group policy. The default IUSR user is a part of the guest account,
and typically group policies disable this account.
Cisco TMS: No
phonebook(s) set
on this system
phonebook(s) set
on this system
■
No phonebook(s) set on this system in Cisco TMS. Configure the endpoint to subscribe to
phonebooks in Cisco TMS.
phonebooks in Cisco TMS.
■
Using NAT on the endpoint can lead to Cisco TMS not recognizing the system and will not
allow it to retrieve any phone books.
allow it to retrieve any phone books.
Request timed out,
no response
no response
The endpoint is configured with the IP address of a non existing web server.
No contact with
server
server
The IIS is restarting or in a state where corrupted messages are received.
Table 175 Possible errors displayed on endpoint due to problems with corporate directory (continued)
Polycom Endpoints do not Get Phone Books
If Polycom endpoints are not receiving phone book data, try the steps below.
Basic Steps
■
■
Check the logs for symptoms or error messages at C:\Program Files\TANDBERG\TMS\data\Logs\TMSDebug\log-
plcmdir.txt on the server.
plcmdir.txt on the server.
■
Restart TMSPLCMDirectoryService. For more information about this Windows service, see
■
Verify that the required ports for the endpoint are open on the Cisco TMS server. For details, see
.
Reporting Scenarios
This section covers troubleshooting scenarios related to Cisco TMS reporting functionality.
Bridge Utilization Report
Data Inconsistencies
Past Data Inconsistencies
A bridge that was replaced with a bridge of a different capacity, or reconfigured in the past, for example from HD to Full
HD, will lead to inaccurate past data and could lead to more than 100% usage being reported.
HD, will lead to inaccurate past data and could lead to more than 100% usage being reported.
279
Cisco TelePresence Management Suite Administrator Guide
Troubleshooting