Cisco Jabber 9.7 not displaying correct informations about contacts
I've recently deployed a CUPS 8.6 in a UC infrastructure. Synchronization & authentication of end users is performed between AD & CUCM 8.5, but LDAP integration is not performed on CUPS server.
When a user logs into the Jabber client, we can browse contacts but we noticed that the phone numbers displayed are incorrect. Indeed, Jabber displays LDAP fields instead of displaying the real DN used in CUCM.
I don't understand why Jabber goes to LDAP to gather some information if I didn't setup the integration between CUPS and AD... Does CUPS get this information via CUCM that is integrated with LDAP? How to fix that kind of issues ?
I don't want to do some sync between AD and CUPS because some AD users in the same OU as end users must not be searchable via Jabber.
CUCM is configured with LDAP custom filters, but CUPS doesn't have this ability...
FYI, there's NO integration between CUPS and LDAP.
CUPS get the users and authentication for them via AXL, from whatever you have in CUCM. So, you do have the authentication for your users to LDAP.
The default configuration is that, you will use the SRV records and bind to LDAP for contact resolution.
No, they don't get the info from what you have on CUCM, nor this is an issue, this is WAD.
If you want to change to what field J4W syncs, or the directory integration, it's all explained in the J4W install and configuration guide under the chapter "Configure Cisco Jabber", modify the jabber-config.xml as required in your environment.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...