Call Mgr 4.3(1) and AD integration performance

kbyrd · ‎01-18-2008

I am running 4.3(1) SR1, two node cluster. We initially installed with DC Directory, but even before we went production, we did an AD integration (W2003). We noticed that everything works very very slowly. For example, to display a User - to check CTI support or to associate a phone to a users (like for AC for attendant console), it may take 5 to 10 minutes to bring up the screen. It will eventually pop up. Logging in to CAR may take 7 to 10 minutes. Extremely slow.

1) Does anyone have any suggestions for where to look for a problem? Have you seen this behavior before with AD integrations? With 4.3(1)? With W2003?

2) There is a registry edit in the AD integration documentation to change DIRACCESS from false to true. Do I need to do this on a cluster member other than the publisher?

Thanks.

gogasca · ‎01-18-2008

1)When querying Microsoft Active Directory, you can perform lookups against the Global Catalog by pointing the script to a Global Catalog server and specifying port 3268 in the script configuration. This method typically results in faster lookups.

Normally this is because Windows 2003 referrals and DNS issues...

2) Yes

Steellllllllll0 · ‎05-19-2008

Hi there,

I was wondering how i would do the same thing on Linux/CCM5...i have a similar issue see posting http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Unified%20Communications%20and%20Video&topic=IP%20Telephony&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.2cbfdc6b

thanks..

evanrichards · ‎05-20-2008

It also matters where you set your Search Base. If you have a lot of OUs in your AD it will search through all of them when querying. If you point your search base directly to the OU, rather than the root of AD, it will be much quicker.