[cisco-voip] Cisco Jabber for Windows - EDS directory causing DC to run at 100%

[Aaron Blair]

In TAC terms:

Our action plan is to indexing the below mentioned attributes in AD.

*        sAMAccountName

*        telephoneNumber

Additionally, ensure you index the following attributes for secondary number queries:

*        otherTelephone

*        mobile

*        homePhone

As well as any other custom attributes that are being used, such as ipPhone.

Cheers,
Aaron

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Dana Tong
Sent: Thursday, 2 May 2013 9:03 AM
To: cisco-voip at puck.nether.net (cisco-voip at puck.nether.net)
Subject: Re: [cisco-voip] Cisco Jabber for Windows - EDS directory causing DC to run at 100%

FYI.

The AD forest needs to be indexed for the attributes "telephoneNumber", "mobile", etc that Jabber is searching.

Cheers
Dana


From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Dana Tong
Sent: Monday, 29 April 2013 9:19 PM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net> (cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>)
Subject: [cisco-voip] Cisco Jabber for Windows - EDS directory causing DC to run at 100%

Hi all,

In all of my recent installations of CUPS / CU IM&P I have always used AD Integration and LDAP for directory services.
(ie EDS for directory).

Usually it's fine. However this time, we go live and the Jabber 4 Windows directory lookups / authentication causes the customer DC (Windows Server 2003 R2) to flatline at 100% causing issues with slow lookups (6 - 60 seconds) and other login issues.

Weird. This is the first time I've seen this. They are running CU IM&P 9.1(x) and Jabber for Windows 9.1(5). [not 9.2]

The work-around was to change the directory integration to UDS.

Is there any reason not to continue with UDS?
Is there any reason why LDAP caused their servers to fail?

Cheers
Dana
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130506/a288bfce/attachment.html>