cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
648
Views
0
Helpful
4
Replies
Highlighted
Beginner

6945 Corporate Directory very slow

Hi Guys,

Anyone had an issues with 6945 - SCCP6945.9-3-1-3 - we are currently seeing about 30-40 seconds for the corporate directory to show up the search menu and the same to disply search results.

Using a 7945 from the same site is much much quicker - 2-3 seconds for each menu to show.

CUCM 8.6

Any ideas?


4 REPLIES 4
Highlighted
Rising star

Hi David,

Is CUCM is synchronize with LDAP?

Maybe you are matching this bug: Bug CSCtc52904: Corporate Directory Searches Takes a long time to respond (for more than 28000 users)

Otherwise, follow this instruction:

1. From the CUCM OS CLI, I have restarted the Cisco Tomcat Web Service

2. From the CUCM Serviceability, I have also restarted the Cisco Trust Verification Service.

I did that on both the CUCM Publisher and Subscriber.

https://supportforums.cisco.com/thread/2114715

Regards

Please rate all useful posts
Favor calificar todos las respuestas útiles.
_____________________________
LinkedIn Profile: do.linkedin.com/in/leosalcie
MDGDP, CCNA, CCNA Voice certified

__________________________________________________
Please remember to rate useful posts clicking on the stars below.
LinkedIn Profile: do.linkedin.com/in/leosalcie
Highlighted

Thanks for the info. I have restarted the 2 services as above on all 3 x CUCM servers and the problem is still there.

We only have around 3500 users imported from LDAP.

This has only recently started happening, was fine post implementation.

Whats the difference between 69xx and 79xx directory search if any?

Highlighted
Beginner

Hello David,

I faced a simliar issue in 69xx with CME, however 7940 phones were working fine.

solved after upgrading 69xx firmware to the latest 9.3.1

please try this, it may help

Regards,
Mohamed Helmy

Regards, Mohamed Helmy
Highlighted

Issue turned out to be related to the Riverbed Steelhead devices in the network. RiOS v 7.x and http optimisation was the cause of the issue. We bypassed the Riverbed with an in path rule for the IP Phone subnets and the directory is now instant.

Content for Community-Ad