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

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

For an introduction to the new site, click here. And see here for current known issues.

New Member

Jabber 9.6 for Windows directory status: last connection not successful

Hey guys, I think I'm just missing something easy here and hoping someone can help. Having an issue where my Jabber clients are unable to connect to LDAP.

Directory - Unhealthy

Status: Last connection not successful.

Protocol: LDAP

Reason:Connection Error

ErrorCannot contact the server

I've setup all the appropriate UC Services and LDAP is configured for directory sync. CUCM, CUC, CUPS, 9.1

I think this has something to do with the jabber-config.xml as I keep seeing in other posts. However, during my setup I haven't had to manually modify that file at all and have done all the setup through CUCM LDAP config and UC / profile configuration. Do I have to edit the xml file for LDAP directory search to work?

Softphone - Healthy

Status: Connected

Protocol: SIP

Address: 172.21.240.10 (CCMCIP)

Device:CSFXXXX

Line:2401

Deskphone - None

Status: Not connected

Protocol: CTI

Address: 172.21.240.10 (CTI)

Deskphone Video - Informational

Status: Unavailable

Reason:Deskphone video is not available in softphone mode.

Voicemail - Healthy

Status: Connected

Address: 172.21.240.11

Port: 443

Protocol: VMREST (HTTPS)

Presence - Healthy

Status: Connected

Address: 172.21.240.12

Protocol: XMPP

Port: 5222

Outlook address book - Healthy

Status: Last connection successful.

Protocol: MAPI

Address: Outlook

Directory - Unhealthy

Status: Last connection not successful.

Protocol: LDAP

Reason:Connection Error

ErrorCannot contact the server

w:defaultTabStop w:val="720"/>

<?xml version="1.0" encoding="utf-8"?><config version="1.0"> <Directory>   <ConnectionType>1</ConnectionType>   <PrimaryServerName>172.20.1.44</PrimaryServerName>   <ServerPort1>389</ServerPort1>   <SecondaryServerName>172.20.1.55</SecondaryServerName>   <ServerPort2>389</ServerPort2>   <ConnectionUsername>cucmldapuser</ConnectionUsername>   <ConnectionPassword>XXXXX</ConnectionPassword>   <OtherPhone>ipPhone</OtherPhone>   <BaseFilter>(ipPhone=*)</BaseFilter>   <SearchBase1>OU=Departments,DC=wn,DC=lc,DC=com</SearchBase1> </Directory> <Policies>   <EnableAccessoriesManager>true</EnableAccessoriesManager> </Policies> <Options>   <Start_Client_On_Start_OS>true</Start_Client_On_Start_OS> </Options></config>

UC Services:

UCservices.jpg

3 REPLIES
New Member

Jabber 9.6 for Windows directory status: last connection not suc

Ok I found some additional information and modified my jabber-config.xml however still no love on connecting via EDI to LDAP.

   CUPS SERVER

   ADSERVER1

   389

   ADSERVER2

   389

   DOMAIN.com

   ADSERVER2

   389

   0

   cucmldapuser

   PASSWORD

   ipPhone

   OU=Departments,DC=wn,DC=lc,DC=com

   false

   mail

   TopRight

Directory - Unhealthy

Status: Last connection not successful.

Protocol: LDAP

Reason:Connection Error

Address: 172.20.1.44

ErrorADSI: 0x80072020L

New Member

Re: Jabber 9.6 for Windows directory status: last connection not

Ended up fixing the problem by going to UDS and downgrading the Jabber clients from 9.6.1 to 9.2.6

Apparently there is a bug with 9.6.1 using UDS where directory search doesn't work.

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

Final jabber-config.xml

  UDS

  http://server_name.domain/%%uid%%.jpg

  true

  false

  true

  .exe;.msi;.rar;.zip;.mp3

  false

Jabber 9.6 for Windows directory status: last connection not suc

2214
Views
0
Helpful
3
Replies
CreatePlease login to create content