Jabber ID as Directory URI fail when searching for contacts, Jabber still returns userID@domain as IM address

[Jiri Solc]

I've got a problem with JID set to Directory URI in CUCM/IMP 10.5. We've set up IMP node to Directory URI as IM Address Scheme in IMP Admin > Presence > Settings > Advanced Configuration. Directory URI is synced from email address in LDAP integration, every user has correct Directory URI value.

Despite this setup client (JfW 10.5) always returns userID@domain as IM address for every LDAP user I try to search. If I add user manually with JID=Directory URI address, user is identified correctly and communication is working. 

IMP Documentation says EDI must be used to get this working. UDS is not supported at this time. Unfortunatelly I can't get contact search working even with EDI and desktop in MS AD domain.

For example:

My JID = email = Directory URI = jiri.solc@domain.cz

My userID = solc

When I search for contacts, Jabber returns solc@domain.cz as IM address every time.

Only workaround is to add a contact manually without searching for one.

Any ideas? Thank you...

[AYBaryshev]

Hi,

 I have the same problem with Jabber 11.8 and CUCM IM&P 11.5.1.

 I tryed UDS and EDI directory integration. Result the same - Directory URI in CUCM and IM&P administration interfaces is correct and equals to email, but when I search contact in Jabber, in view profile I see IM address as AD_username@email_domain.

In jabber-config.xml I have

<Directory>
   <UseSipUriToResolveContacts>true</UseSipUriToResolveContacts>
   <SipUri>mail</SipUri>
   <DirectoryServerType>EDI</DirectoryServerType>
   <ConnectionType>1</ConnectionType>
   <PrimaryServerName>LDAP1</PrimaryServerName>
  <ServerPort1>389</ServerPort1>
  <SecondaryServerName>LDAP2</SecondaryServerName>
  <ServerPort2>389</ServerPort2>
  <UseWindowsCredentials>0</UseWindowsCredentials>
  <ConnectionUsername>AD_RO_user</ConnectionUsername>
  <ConnectionPassword>AD_RO_password</ConnectionPassword>
  <DirectoryURI>mail</DirectoryURI>
  <BDIDirectoryURI>mail</BDIDirectoryURI>
  <UseSIPURIToResolveContacts>true</UseSIPURIToResolveContacts>
  <BDIUseSIPURIToResolveContacts>true</BDIUseSIPURIToResolveContacts>
  <BDIIMAddress>mail</BDIIMAddress>
   <UriPrefix>sip:</UriPrefix>
  <BusinessPhone>ipPhone</BusinessPhone>
  <MobilePhone>mobile</MobilePhone>
  <OtherPhone>otherTelephone</OtherPhone>  
</Directory>

 Can anyone help me, please?

[robert.n.barrett]

I'm not the expert, but it looks like you have a LOT of entries that don't apply to newer versions of Jabber.  I'd suggest that you read through the parameters guide for your version of Jabber and make sure that all of those entries apply.

Here's a bare-bones version of my file that works in our environment (Jabber 11.8 and CUCM/CUC/CUP 11.5.1).  Please note that we do an LDAP-sync from Active Directory to our CUCM user directory, therefore Jabber uses UDS for our directory lookup, and the Service Profile in CUCM specifies all of those settings (not the jabber-config.xml file).

<config version="1.0">
<Client>
<spell_check_enabled>true</spell_check_enabled>
</Client>
<Directory>
<UseSipUriToResolveContacts>true</UseSipUriToResolveContacts>
<UriPrefix>sip:</UriPrefix>
</Directory>
<Options>
<ShowContactPictures>false</ShowContactPictures>
<StartCallWithVideo>false</StartCallWithVideo>
</Options>
<Phone>
<EnableDSCPPacketMarking>true</EnableDSCPPacketMarking>
</Phone>
<Policies>
<DisallowedFileTransferTypes>.exe;.msi;.com</DisallowedFileTransferTypes>
<TelemetryEnabled>FALSE</TelemetryEnabled>
</Policies>
<Presence>
<CalendarWebExMeetingPresence>true</CalendarWebExMeetingPresence>
</Presence>
</config>