Jabber Directory Search

[richardpierce]

Hi,

My customer would like directory searches in their Jabber client to return users based on a search of department, company and/or title. Searches are working if the search us based on first name, last name or an entry in the users address. However if for example they search using the word "Engineer" which has been set at some users Job title no matching results are found. It seems as though the LDAP search looks for attributes in the General, Address and Telephones catagories in AD user profile but not for attributes in the Organization catagory. We are using standard windows LDAP integration, no UDS etc.

Any help would be greatly appreciated.

Regards,

Richard.

[A_ · Accepted solution]

Can't you use Predictive Search Filter in Service Profile? Or <PredictiveSearchFilter>[attribute],[attribute2],[attribute3],....</PredictiveSearchFilter> in jabber-config.xml.

If you use ANR then you have to configure your attributes for ANR.

With Search Base 1-5 you can tell Cisco Jabber where to search.

[richardpierce]

Thanks for the advice, i used predictive search with UseANS set to false to enable the search to extend to department. 

[W S H FERNANDO]

Hi Richard 

I'm facing the same issue, I need to search based on "physicalDeliveryOfficeName" attribute or "co" attribute (Country), I'm not much familiar with ANR, can you please explain how you have done this? 

Regds

Sasith Fernando 

[Anthony Holloway]

It sounds like they disabled ANR in Jabber by using the UseANR param set to false, and then used the PredictiveSearch Jabber config param to specify how they want Jabber to lookup directory searches.

You can read more about Jabber parameters here (I linked directly to the UserANR section):

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/12_5/Parameter_Guide/cjab_b_parameters-reference-guide-jabber_125/cjab_b_parameters-reference-guide-jabber_125_chapter_01010.html#reference_2DD20BBF2EE60FA9B5E209DC7AA40D9F

Also, ANR is just short hand for searching in a bunch of fields, without having to specifically ask for that to happen.

E.g., Jabber can just say anr=holloway, and that's it, and then when AD gets the request for the lookup, AD knows to search in a whole bunch of other fields on Jabber's behalf. Therefore, which fields AD searches in, is not configured in Jabber, rather it's configured in AD.

You can read more about ANR here:
https://social.technet.microsoft.com/wiki/contents/articles/22653.active-directory-ambiguous-name-resolution.aspx

So, what it seems like these folks are doing is, they are removing the need to leverage the AD changes to ANR, and just disabling it, and making Jabber supply all of the fields to search in. This is nice and all, but it creates more network traffic, and bypasses a pretty cool feature of AD: ANR. So, choose the one that makes the most sense for you.

Also, as a bonus, what fields you want to search in (which is what we're talking about here) is different from the set of results that will be returned. In order to change that, then you need to also change the BaseFilter in the Jabber params.

E.g., If you also want Jabber to return Users (default) and Contacts (not default) in search results, you would do something like this:
<BaseFilter>(&(objectCategory=Person)(|(objectClass=User)(objectClass=Contact)))</BaseFilter>