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 - LDAP status unknows

Hi

I have CUCM 9.1 and CUPS ver 9.1

Jabber client ver 9.2.6(12639)

It is showing LDAP status as unknown.

Directory - Unhealthy

Status: Unknown

Reason:Unknown

Protocol: LDAP

We are using "Open LDAP"

<?xml version="1.0" encoding="utf-8"?>

<config version="1.0">

<Directory>

<DirectoryServerType>EDI</DirectoryServerType>

<ConnectionType>0</ConnectionType>

<PrimaryServerName>x.x.x.x</PrimaryServerName>

<ServerPort1>3268</ServerPort1>

<UseWindowsCredentials>0</UseWindowsCredentials>

<ConnectionUsername>username</ConnectionUsername>

<ConnectionPassword>xxxx</ConnectionPassword>

  <SearchBase1>DC=xxxx,DC=xx,DC=xx</SearchBase1>

<SearchTimeout>30</SearchTimeout>

I tried with below jabber-config.xml file also.

Jabber clients are downloading this file on local PC during login, but still LDAP status on jabber client shows "unknown"

<CommonName>cn</CommonName>

<PhotoURISubstitutionEnabled>True</PhotoURISubstitutionEnabled>

<PhotoUriSubstitutionToken>sAMAccountName</PhotoUriSubstitutionToken>

<DisplayName>displayName</DisplayName>

<Firstname>givenName</Firstname>

<Lastname>sn</Lastname>

<DomainName>userPrincipalName</DomainName>

<EmailAddress>mail</EmailAddress>

<BusinessPhone>telephoneNumber</BusinessPhone>

<MobilePhone>mobile</MobilePhone>

<HomePhone>homePhone</HomePhone>

<OtherPhone>ipPhone</OtherPhone>

</Directory>

</config>

Pls. suggest.

Everyone's tags (1)
17 REPLIES
New Member

Jabber - LDAP status unknows

Any feedback ?

Cisco Employee

Jabber - LDAP status unknows

There are 2 changes that I would like to suggest in this config file:

1. Try changingthe connection Type to '1'

2. Also, try removing the server port as not too sure if Open LDAP supports 3268.

For more details please find the below document:

http://www.cisco.com/en/US/docs/voice_ip_comm/jabber/Windows/9_2/JABW_BK_C9731738_00_jabber-windows-install-config_chapter_0101.html#JABW_RF_O1D72112_00

New Member

Hi - what was the solution if

Hi - what was the solution if this problem - I get the same error message:

GetDirectorySearcher - failed to get a searcher - COMException [0x8007052e]

(EDI  LDAP from a Windows PC which is not in the Domain.)

kind regards

Cisco Employee

Jabber - LDAP status unknows

Did you try logging in from any other PC's?

can u please clear all your logs from the PC, recreate the issue, and attach the problem report here with the time stamps so that I can take a look at it. The logs can be obtained from the folder:

C:\Users\XXXX\AppData\Local\Cisco\Unified Communications\Jabber\CSF

Cisco Employee

Jabber - LDAP status unknows

also, is the PC a part of same domain?

New Member

Jabber - LDAP status unknows

Dear Nirmal Issac

I tried multiple times with removing files from cache folder. Still LDAP shows unkown.

C:\Users\XXXX\AppData\Local\Cisco\Unified Communications\Jabber\CSF

PC is not part of same domain. Is this is create any issue ?

then what abt. iPhone, IPAD, Android jabber ?

Rgds

Rajesh Kumar

Cisco Employee

Re: Jabber - LDAP status unknows

Ok. Im sorry if  i did not explain clearly.  What i need is

a) Clear all logs

b) Log into jabber, try search, and reproduce the issue

c)collect the PRT. PRT is collected as shown below.

d) attach the logs in this thread, i will have a look

Also, the reason why i asked if the PC is in AD domain is - when the PC is in domain, jabber tries to auto detect the AD and tries to log in to AD using the Windows account credentials.

New Member

Jabber - LDAP status unknows

if the PC is not part of the domain the client is not going to be able to connect to LDAP

create a local config file for this user

jabber-config-user.xml

upload the file to the CSF folder and test

New Member

Re: Jabber - LDAP status unknows

Dear Nirmal

Even PC is part of domain, then also I get LDAP unknown error.

Here I have attached jabber log.

Pls. suggest.

Rgds

Rajesh Kumar

New Member

Re: Jabber - LDAP status unknows

Hi

Uploaded Problem report output from Jabber.

It is open LDAP and ldap port number is 1389

Any feedback ?

Rgds

Rajesh umar

New Member

Re: Jabber - LDAP status unknows

Do you have a screen shoot of CUCM->LDAP ->>Directory and Authentication

New Member

Re: Jabber - LDAP status unknows

yes, attached

New Member

Re: Jabber - LDAP status unknows

Are you able to change the Directory port to 389 and the Authentication port to 3268

As per the doucmentation this are the recommended ports for LDAP binding

http://www.cisco.com/en/US/docs/voice_ip_comm/jabber/Windows/9_2/JABW_BK_C9731738_00_jabber-windows-install-config.pdf

Clear the jabber cache and test again

A reset of the CTI service may be needit

New Member

Re: Jabber - LDAP status unknows

Dear Joscespe

It is openLDAP and using port 1389

It is very hard to covinence and request for change in LDAP port.

There is not supported documrnt from cisco to provide evidence that changing of port is mandatory.

Document simply says openLDAP is supported....!

Do you have any supported document saying " change the Directory port to 389 and the Authentication port to 3268" and it works ? organization dont accept without supportive document.

waiting for your feedback.

Rgds

Rajesh Kumar

Cisco Employee

Jabber - LDAP status unknows

Try connecting to your AD from the PC where you are running jabber with a AD explorer software.

If it does connect then problem is with Jabber and if not then problem with Machine/AD/DC controller/DNS can be anything.

Open a TAC case if possible.

Tapan

New Member

Jabber - LDAP status unknows

Rajesh,

Jabber does support open LDAP ports

but you ned to specify the following:

Cisco Jabber for Windows supports directory integration with OpenLDAP using anonymous
binds.

Directory integration with OpenLDAP requires you to define specific parameters in a Cisco
Jabber for Windows configuration file. At a minimum, you must do the following:

*     Set EDI as the value of the DirectoryServerType parameter. 
*     Specify 1 as the value of the ConnectionType parameter. 
*     Specify 0 as the value of the UseWindowsCredentials parameter. As of this release, Cisco
Jabber for Windows supports directory integration with OpenLDAP using anonymous binds. For
this reason, you must not specify any credentials in your configuration file. 
*     Specify either the root of the directory service or the organizational unit (OU) as the
value of the SearchBase1 parameter. 
*     Specify all appropriate attribute mappings. For example, by default, the value of the
UserAccountName parameter is sAMAccountName. To integrate with OpenLDAP, you must change
this value to the attribute on your directory service that holds usernames; for example,
uid. 
*     Specify a value for the BaseFilter parameter. The value you specify must align to the
object class that your directory service uses; for example, inetOrgPerson. 
*     Specify a value for the PredictiveSearchFilter parameter. 

Logs Jabber LDAP:

COMException [0x8007052e]

ConnectionManager::GetDirectorySearcher - Using custom credentials to connect [LDAP://ds.alghurair.com:1389/ou=systems,dc=alghurair,dc=com] with tokens [1]

2013-12-24 13:42:28,455 DEBUG [0x00002544] [rdsource\ADPersonRecordSourceLog.cpp(50)] [csf.person.adsource] [WriteLogMessage] - ConnectionManager::GetDirectorySearcher - failed to get a searcher - COMException [0x8007052e]

What youc an do to norrwo down the issue is to

Install Jabber on the actual AD server, and test

or try what Tapn told you

New Member

Hi,Did you ever figured out

Hi,

Did you ever figured out the solution to this issue? Thanks

Mason

2448
Views
0
Helpful
17
Replies
CreatePlease login to create content