our cisco jabber contact resolution has always worked perfectly. From version 11.9.1 onwards we have on the Windows client and mobile phones the problem that he can no longer assign the account. But only show with "@ schnaithmann.de". What has changed with the new Jabber version? and what have to adjust with us? Unfortunately we can find nothing in the release notes. Old Jabber versions work flawlessly
Works fine for me.
I'm guessing you're using Expressway with MRA, right? So... Is the external domain "schnaithmann.de" is also the internal domain, or the internal domain where the Active Directory and CUCM / IM&P resides is difeerent?
yes exactly will use the expressway mra. with the external domain schnaithmann.de. This is how this contact resolution works from external.
from internal it does not work anymore. here is our domain schnaithmannag.local.
but we do not use internally directly on LDAP, we connect via xphone virtual directory. Here we use "jid" as sAMAccountname
this had always been so
Thanks for the info.
Can you please verify / do:
If you have an issue to post those screen shots here publicly, please send it to me privately.
we have configured the external domain everywhere. see screenshots.
in the virtual directory we have no "URI" field. we are working with the parameter: <UserAccountName> jid </ UserAccountName>
jid = sAMAccountName
which field should we add as in the virtual directory and how to fill it? we also need to adjust the jabber-config?
Can't say for 100%, but looks like jabber-config is fine. But, I would try to take a Wireshark capture from the PC running the Cisco Jabber. You should see traffic of TCP/389 that is intended to your VDir, in those packets you can see the filter that the Cisco Jabber applies in order to find those users. Take this filter and try it out on your VDir, and see what is wrong with the filter (if that's the case of course). Update us will the results (or share the capture also with us) so then we'll know better what to modify.
I think I found something, in a "What's New in Cisco Jabber for Windows 11.8.0" document.
Take a look:
Contact Resolution Improvements —Contacts in Jabber can come from different sources. This release includes some changes in the way Jabber compares these contacts and resolves the information to merge the contact records. To view the Contact Resolution data, in the hub window, select Ctrl+ Shift+C.
Jabber ID (JID) – If the records have a JID, the records are matched based on the JIDs and no further comparison is done on the mail or phone number fields.
Mail – If the records have a mail field, then the records are matched based on the mail field and no further comparison is done for phone numbers.
Phone Number – If the records have a phone number, the records are matched based on the phone number. As the records are compared and a match is found, the contact information is merged to create one contact record.
I'm having a feeling that now it tries to look for full JID, for example in your screen shot of VDir you supplied, the JID is "OfficeMaster". So I think it tries now to look for: "OfficeMaster@schnaithmann.de".
Can you please try to change the JID of a few users in the VDir and add the "@schnaithmann.de" as a prefix of their JID? And then try to logout & reset cisco jabber settings and login again, and see if those users you changed their JID are resolved now or not.
If the above still not working, I would defenatly try to do what I wrote in my previous comment - take a Wireshark capture.
Also, just saw now in the same document I was talking about this section:
This release includes changes to the way LDAP is configured. Cisco Directory Integration (CDI) replaced Basic and Enhanced Directory Integration (BDI and EDI). Jabber uses service discovery to automatically detect the directory server and also how to connect to it. You have some optional configuration available if you want to prioritize authentication methods, or define the primary server.
If you want to customize your LDAP configuration, there is now one set of CDI parameters that apply to all clients. The CDI parameters are the same as EDI parameters, and do not require any further action. The BDI parameters are no longer supported, so if you're upgrading from a BDI-only deployment, you must update your LDAP configuration.
For more details on how CDI works, including a detailed description of how to upgrade to 11.8 from a BDI contact source and a complete list of parameters affected by moving from BDI and EDI to CDI, read LDAP Option: Cisco Directory Integration (CDI) in the Planning Guide for Cisco Jabber 11.8.
It looks like they changed all the EDI and BDI support. As they are stating (marked in bold) that if you moving up to this new release you need to upgrade your directory configurations.
By the way, I don't really like to to make directory configurations in the jabber-config, although I'm mostly working with Active Directory servers at my clients. I'm always configuring the Directory services in the Service Profile in the CUCM. Maybe you can try to do the same and it'll catch. But if you do it, of course remove the settings from jabber-config file so it won't collide.
Heh, regarding Edit #1, please also see this document, it describes the changes that need to be done for every parameter in the jabber-config if you're coming from mixed EDI/BDI configurations:
Relate to "Scenario 4: If you are upgrading to 11.8 from a mixed EDI/BDI configuration" in the document.
I have changed jid to email@example.com, but then the contact resolution does not work anymore.
the settings we have made as we moved to version 11.8 / 11.9. this has since then also function, only in the 11.9.1 no more.
It is also comical that in the contact list all contacts are displayed correctly, if you click on profile the contact is so funny with @ schnaithmann.de displayed.
my colleague created a wireshark protocol
Yeah, he resolved it. He sent me the solution in a private message.
He moved the directory settings from the jabber-config.xml file to the Service Profile configurations, like that: