Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Agent Desktop Phone book

Does anyone know if it is possible to allow an agent desktop system to access the DCD for number lookups? This function would be similar to Attendant console number lookup but I can not figure out if the functionality exists?

If not, then what is the name and location of the file that is used for storing the "employee phone book" or is it stored someplace in SQL?



  • Contact Center

Re: Agent Desktop Phone book

Cisco IP Phone Address Book Synchronizer will not allow users to store personal contacts in Outlook Address book then synchronize thier PAB.

Conditions: The Outlook contacts are stored on the Exchange server instead of locally. Workaround: Export Outlook Address Book Contacts to a CSV file, then import the CSV file into the Windows Address Book (*.WAB) on local computer. After Outlook contacts are in the WAB, run IP Phone Address Book Synchronizer to add personal contacts to My Address Book on the IP phone service.

Please let me know if you are trying to synchronize your PAB and we can continue troubleshooting. Otherwise, let me know if you have any questions regarding this limitation.

This urls should help you, it speaks about Creating Users, Phones, and Associations in Cisco CallManager .

New Member

Re: Agent Desktop Phone book

I actually did not word my question properly the first time. I am actually trying to get integration between CM DC Directory and IPCC agent desktop. The problem is that they don't integrate; therefore you have to enter the names manually or be some java/vb scripting guru to write an external directory interface.

I guess I was asking if anyone knew of anyway, aside from the two I just mentioned, to get the names into agent desktop.

This widget could not be displayed.