Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
Phone book scenarios
This section covers troubleshooting scenarios related to Cisco TMS phone books as they may present both
client-side and in Cisco TMS.
client-side and in Cisco TMS.
Phone book (Corporate Directory) errors
You can get the following errors on the endpoint if corporate directory is not working properly:
Message
Explanation or suggested solution
Request timed
out, no response
out, no response
The Cisco TMS server is busy, try again.
Warning: directory
data not retrieved:
404
data not retrieved:
404
n
The endpoint is configured with the IP address of a different web server than the Cisco
TMS server.
TMS server.
n
The corporate directory path on the endpoint is wrong.
Warning: directory
data not retrieved:
401
data not retrieved:
401
n
The "Public" virtual directory on the Cisco TMS server is not configured to allow
Anonymous Access.
Anonymous Access.
n
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.
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.
Cisco TMS: No
phonebook(s) set
on this system
phonebook(s) set
on this system
n
No phonebook(s) set on this system in Cisco TMS. Configure the endpoint to subscribe to
phonebooks in Cisco TMS.
phonebooks in Cisco TMS.
n
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
out, 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.
Polycom endpoints do not get phone books
If Polycom endpoints are not receiving phone book data, try the steps below.
Basic steps
n
n
Check the logs for symptoms or error messages at C:\Program
Files\TANDBERG\TMS\data\Logs\TMSDebug\log-plcmdir.txt on the server.
Files\TANDBERG\TMS\data\Logs\TMSDebug\log-plcmdir.txt on the server.
n
Restart TMSPLCMDirectoryService. For more information about this Windows service, see
.
n
Cisco TMS Administrator Guide (14.3.2)
Page 332 of 342
Troubleshooting
Phone book scenarios