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 compares the contact record fields in the following order:
-
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.
Edit #1:
Also, just saw now in the same document I was talking about this section:
Cisco Directory Integration (CDI)
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.
Edit #2:
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:
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/11_8/cjab_b_planning-guide-jabber-118/cjab_b_planning-guide-jabber-118_chapter_0101.html
Relate to "Scenario 4: If you are upgrading to 11.8 from a mixed EDI/BDI configuration" in the document.
