[cisco-voip] RESOLVED: Jabber for Windows 10.5 and Preferred Name field in LDAP/AD?

Tue Oct 7 13:25:16 EDT 2014

I’d love to see MRA/Expressway use LDAP. UDS with jabber has no support for filtering too, which can be just as annoying.

Dennis Heim | Collaboration Solutions Architect
World Wide Technology, Inc. | +1 314-212-1814
[cid:image002.png at 01CFE232.22395AA0]<https://twitter.com/CollabSensei>
[cid:image003.png at 01CFE232.22395AA0]<xmpp:dennis.heim at wwt.com>[cid:image004.png at 01CFE232.22395AA0]<tel:+13142121814>[cid:image005.png at 01CFE232.22395AA0]<sip:dennis.heim at wwt.com>

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jason Aarons (AM)
Sent: Tuesday, October 07, 2014 12:32 PM
To: Anthony Holloway
Cc: cisco-voip (cisco-voip at puck.nether.net)
Subject: [cisco-voip] RESOLVED: Jabber for Windows 10.5 and Preferred Name field in LDAP/AD?

So here is the final story. Thanks for your help!   I spent a day looking into this and it’s working now correctly!

I noticed today that in CCMAdmin the Service Profile has checkbox for Use UDS For Resolution.  I unchecked UDS and cleared the client cache in %appdata% and restarted Jabber client.  I then search for the user and find him with the nickname.  Click on his name and View Proifle I see his Display Name already has nickname and the firstname is his legal name.  Problem solved by turning off use UDS for name resolution.

Clearly in CallManager 11 under LDAP Directory and  End User > User Management they need to add displayName/Nickname field for UDS to be able to use……ps can UDS do ANR ?

Side note, when can Expressway/VCS be able to use LDAP?  It has far more details direct to LDAP than UDS (eg Fax Numbers, home address, etc).  CallManager isn’t a very good PIM compared to Outlook 2013/Active Directory.

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jason Aarons (AM)
Sent: Tuesday, October 07, 2014 11:53 AM
To: Anthony Holloway
Cc: cisco-voip (cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>)
Subject: Re: [cisco-voip] Jabber for Windows 10.5 and Preferred Name field in LDAP/AD?

Wondering if I can have only this in my jabber-config.xml?   Really wish I could push this via CallManager setting and not have to touch the jabber-config.xml

<?xml version="1.0" encoding="utf-8"?>
<config version="1.0">
<Directory>
   <Nickname>Nickname</Nickname>
   <BDINickname>Nickname</BDINickname>
</Directory>
</config>

From: avholloway at gmail.com<mailto:avholloway at gmail.com> [mailto:avholloway at gmail.com] On Behalf Of Anthony Holloway
Sent: Tuesday, October 07, 2014 12:05 AM
To: Jason Aarons (AM)
Cc: cisco-voip (cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>)
Subject: Re: [cisco-voip] Jabber for Windows 10.5 and Preferred Name field in LDAP/AD?

I'm not sure how reliable or easy to deploy this will be, but I just used the jabber config file generator and mapped my nickname field, and it showed up.  I can find myself in the directory with either "anthony" or "tony"

For the record, I don't go by Tony.  ;)

[cid:image006.png at 01CFE232.22395AA0]

On Mon, Oct 6, 2014 at 5:12 PM, Jason Aarons (AM) <jason.aarons at dimensiondata.com<mailto:jason.aarons at dimensiondata.com>> wrote:
Is there a way to set the Preferred Name (Active Directory/LDAP) field in Jabber for Windows ?

For example the boss goes by Tim, but in AD he is listed as John.  His birthname is John but goes by Tim.  In AD there is a Preferred Name field.  Not all users have Preferred Name populated.

Can the Jabber client query to LDAP look at Preferred Name first then Firstname?

Jason Aarons, CCIE No 38564
Consultant
Dimension Data
+1-904-338-3245<tel:%2B1-904-338-3245>

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

itevomcid
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20141007/f9a840d1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 3876 bytes
Desc: image002.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20141007/f9a840d1/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 1389 bytes
Desc: image003.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20141007/f9a840d1/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 1292 bytes
Desc: image004.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20141007/f9a840d1/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 1391 bytes
Desc: image005.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20141007/f9a840d1/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 44709 bytes
Desc: image006.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20141007/f9a840d1/attachment-0004.png>