06-22-2017 02:04 AM - edited 03-17-2019 06:55 PM
Hi all,
I am currently struggling with a odd Jabber directory integration issue. We currently use Windows Jabber version 11.6 and
have setup an LDAP metadirectory server to provide users with contact data from different sources. Our Jabber config is working
without a problem with Jabber version 11.6.X but when we upgrade the client to 11.8 directory lookups are no longer possible.
We have recognized, that the newer client does not connect to the LDAP server (192.168.12.41) from jabber-config-xml
but instead is connecting to one of our AD servers.
Here the current jabber-config.xml:
<?xml version="1.0" encoding="utf-8"?>
<config version="1.0">
<Presence>
<PresenceServerAddress>192.168.12.31</PresenceServerAddress>
<PresenceServerDomain>example.com</PresenceServerDomain>
</Presence>
<Directory>
<DirectoryServerType>EDI</DirectoryServerType>
<PrimaryServerName>192.168.12.41</PrimaryServerName>
<ServerPort1>3891</ServerPort1>
<ConnectionUsername>username</ConnectionUsername>
<ConnectionPassword>password</ConnectionPassword>
<UseWindowsCredentials>0</UseWindowsCredentials>
<UseSecureConnection>0</UseSecureConnection>
<BaseFilter>(&(objectCategory=*))</BaseFilter>
<SearchBase1>vdir=VDir</SearchBase1>
<UserAccountName>jid</UserAccountName>
<PhotoSource>jpegPhoto</PhotoSource>
</Directory>
<Policies>
<InitialPhoneSelection>deskphone</InitialPhoneSelection>
<UserDefinedRemoteDestinations>true</UserDefinedRemoteDestinations>
<EnableAccessoriesManager>true</EnableAccessoriesManager>
<EnableHuntGroup>true</EnableHuntGroup>
<EnableCallPickup>true</EnableCallPickup>
</Policies>
<Options>
<StartCallWithVideo>false</StartCallWithVideo>
<Start_Client_On_Start_OS>true</Start_Client_On_Start_OS>
<AllowUserCustomTabs>true</AllowUserCustomTabs>
<ShowOfflineContacts>true</ShowOfflineContacts>
</Options>
<CUCM>
<PhoneService_UseCredentialsFrom>presence</PhoneService_UseCredentialsFrom>
</CUCM>
<Voicemail>
<VoiceMailService_UserCredentialsFrom>Phone</VoiceMailService_UserCredentialsFrom>
</Voicemail>
</config>
Does anyone have an idea what could be the cause of this problem and how to solve it ?
Thank you for your kind help.
best regards
Andreas
06-22-2017 06:47 AM
11.8 uses CDI instead of EDI/BDI (this is explained in the RN)
Have you adjusted your configuration accordingly?
06-22-2017 08:11 AM
Hello Jaime,
thank you for your fast reply. I have created a test-xml and assigned it to one of the devices. In this
xml I have changed the directory section as follows:
<Directory>
<DirectoryServerType>CDI</DirectoryServerType>
<PrimaryServerName>192.168.12.41</PrimaryServerName>
<PresenceDomain>example.com</PresenceDomain>
<ServerPort1>3891</ServerPort1>
<UseWindowsCredentials>0</UseWindowsCredentials>
<ConnectionUsername>username</ConnectionUsername>
<ConnectionPassword>password</ConnectionPassword>
<BaseFilter>(&(objectCategory=*))</BaseFilter>
<SearchBase1>vdir=VDir</SearchBase1>
<PhotoSource>jpegPhoto</PhotoSource>
<UserAccountName>jid</UserAccountName>
</Directory>
Unfortunately this did not resolve my issue. The client still uses the AD server as directory source
instead of the LDAP metadirectory (192.168.12.41).
In the jabber log file I have found this error:
2017-06-22 16:50:18,248 WARN [0x00001d00] [in\person-ldap\LdapConfiguration.cpp(99)] [csf.person] [csf::person::ldap::LdapConfiguration::setLdapParameter] - [BaseFilter] syntax error, parentheses mismatch on (&(objectCategory=*))
2017-06-22 16:50:18,248 WARN [0x00001d00] [n\person-ldap\LdapConfiguration.cpp(111)] [csf.person] [csf::person::ldap::LdapConfiguration::setLdapParameter] - [BaseFilter] syntax error corrected - (&(objectCategory=*)
best regards
Andreas
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide