Jabber Mobile/3rd Party App Contact Names

Stuart McGrath · ‎02-26-2015

Prior to integrating our CUCM solution with LDAP, whenever we added a user account to CUCM it replicated across to CUPs and the users name appeared to people using windows, Iphone and Android apps as Firstname Lastname. Post integration of CUCM to LDAP has resulted in any new users that are created appearing in the Iphone/Android/3rd Party App as userid@domain.co.uk rather than the firtname lastname we were previously getting. NOTE **Its not affecting Windows Desktop Jabber users***

We have noticed that if you log onto the cups user page and look at your contact list <Ipaddress:8443/cupsuser> User Options > contacts those that were created in CUCM prior to integration have an entry in the alternative name field.....those that were created in AD and synced to CUCM then replicated to CUPs do not!

I have pulled the following from a log on the Jabber client on a Mobile device (replaced specifics names etc)

02-25 10:40:14.476 2642 2642 D ContactsAdapter: [ContactListFeatureSet.cpp(359)] [DumpContactListToLogs] - Contact: <0x6be1b928>, name: <Firstname> <Last Name>, jid: userid@domain.co.uk

02-25 10:40:14.476 2642 2642 D ContactsAdapter: [ContactListFeatureSet.cpp(359)] [DumpContactListToLogs] - Contact: <0x6a75e6f0>, name: userid@domain.co.uk, jid: userid@domain.co.uk

Any ideas as to why the Alternate name field doesn't populate for CUPs contacts when users are created in AD, but did when previously created in CUCM?

Is their a Field in AD that will populate this in the background?

Jaime Valencia · ‎02-26-2015

Did you properly configured the BDI integration in the jabber-config.xml file???

HTH

java

if this helps, please rate

Stuart McGrath · ‎02-26-2015

My understanding is : 'EDI is LDAP for Windows Clients and BDI is LDAP for non-windows Clients'. I only have EDI configured. So is it possible to specify both in the jabber-config.xml file?

Jaime Valencia · ‎02-26-2015

That's correct, yes, you can have them both in the same file, just don't mix parameters, make sure all EDI parameters are in the same section, then configure only BDI parameters, or viceversa, the order doesn't matter, but you need to keep them apart in the file.

HTH

java

if this helps, please rate

Stuart McGrath · ‎02-27-2015

Thanks Jaime

EDI still working. Jabber Windows client Fine, however the BDI doesn't appear to be working on Android/Apple devices? Logging appears to show that these devices aren't even trying to access LDAP servers for directory

Is the configuration below valid?

- <Directory>

<PrimaryServerName>IPADDRESS</PrimaryServerName>

<ConnectionUsername>username@domain (UPN)</ConnectionUsername>

<ConnectionPassword>password</ConnectionPassword>

<SearchBase1>OU=users,DC=domain,DC=co,DC=uk</SearchBase1>

<BDIPrimaryServerName>IPADDRESS</BDIPrimaryServerName>

<BDIPresenceDomain>domain.co.uk</BDIPresenceDomain>

<BDIConnectionUsername>username@domain (UPN)</</BDIConnectionUsername>

<BDIConnectionPassword>password</BDIConnectionPassword>

<BDISearchBase1>OU=users,DC=domain,DC=co,DC=uk</BDISearchBase1>

<BDIUseJabberCredentials>false</BDIUseJabberCredentials>

<BDIPhotoSource>thumbnailPhoto</BDIPhotoSource>

<BDIPredictiveSearchFilter>mail , displayName</BDIPredictiveSearchFilter>

</Directory>

Stuart McGrath · ‎03-17-2015

Does this configuration look correct??