I'm using Cisco UDS for Directory searches for my Jabber users. I have a LDAP directory for the syncronization and authentication of the users.
The reason for me using the UDS is that i want to be able to customize what information is presented to the users in their client. Right now the UDS are getting the mobile(cellphone) number from the users and showing it as an alternative when they press the call button in the Jabber client. The issue is that it is not possible to call the mobile number from the CUCM. Is it in any way possible to limit the different numbers that are imported to the UDS from LDAP or limit the search results in any way?
You only get to choose from which field to sync when you configure the LDAP agreement, we offer no way to modify the data we're importing. You can use filters to configure that those users are not synced, but it seems all you want is to not sync that field. Depending on the field, you may have no option to remove it, or map it to another field.
As for Jabber, you could try to change the mappings via the .xml config file so they look into a blank field.
What I really want to avoid is the "mobileNumber" field as it is called in cucm UDS. Now it's showing as a dial option in the jabber client. The user gets to choose between phone, mobile phone and the email address when they try to call another user and they think it's a little bit confusing. I would really want to only show the email address because it is configured as the directory URI.
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: firstname.lastname@example.org 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 ...