This may be a stupid question. I have some users configured in ccm and the attendant console client can connect to the ccm. But, no users are displayed in the Directory pane. Could anyone please help to solve it?
Have you tried logging out of AC, then stopping and starting Cisco TCD (Telephony Call Dispatcher), then logging back in on AC? Have a look at the attached docs;
Q. Why do line states of some directory numbers show unknown state?
A. Telephony Call Dispatcher (TCD) service is not started on all Cisco CallManager servers that have phones homed in. Start TCD services on all CallManager servers that have phones homed in. If this is an upgrade, make sure that you upgrade the TCD server on all Cisco CallManager servers in the cluster.
Q. I just added a user from the Cisco CallManager Administration page, but I do not see that user in the directory window on the client. What should I do?
A. The server extracts the user list from the directory, when one of these conditions is met:
Telephony Call Dispatcher (TCD) service is started and the directory sync interval is not zero.
Directory sync interval expired.
Directory sync interval changed from the Cisco CallManager administration page.
The client loads the user list only at login. You need to re-login after any one of these conditions has been met for the client to see an updated user list from the server. Users without telephone numbers are not displayed on the client. Make sure that all relevant users have phone numbers listed for them in the directory.
Understanding the Cisco CallManager Attendant Console Directory
The attendant console server reads and caches directory entries at startup. After an initial handshake determines whether the directory entries changed since the previous log in, the attendant console downloads the directory user list. The attendant console also downloads the user list when the interval in the Directory Reload Interval field in the Attendant Settings dialog box expires or when the user clicks the Reload button in the Directory window.
AutoGenerated.txt file that is generated by the Cisco TCD service and stored in the userlist directory on the Cisco CallManager Attendant Console server. If the Directory Sync Period service parameter does not equal zero, Cisco TCD generates the AutoGenerated.txt file when the Cisco TCD service starts and when the directory sync period expires.
To modify the Directory Sync Period service parameter, choose Service > Service Parameters. Choose the appropriate server from the Server drop-down list box and choose the Cisco Telephony Call Dispatcher Service from the Service drop-down list box.
Note: Directory entries without telephone numbers do not display in the attendant console Directory window.
Understanding the Cisco Telephony Call Dispatcher
The attendant console application registers with and receives call-dispatching services from the Cisco Telephony Call Dispatcher (TCD). The Cisco TCD, a Cisco CallManager service, provides communication among Cisco CallManager servers, attendant consoles, and the Cisco IP Phones that are used with the attendant consoles.
Note If you use the attendant console in a cluster environment, make sure that all Cisco CallManagers within a cluster have the Cisco TCD service activated and running. You must manually activate the service through Cisco CallManager Serviceability.
Cisco TCD handles attendant console requests for the following items:
User directory information (Cisco TCD stores and periodically updates directory information for fast lookup by the attendant console.)
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...