Hello again, there is another issue that I've been having for quite some time. We want to deploy Cisco Jabber for windows to our entire company of 250+ users. One feature that everyone likes with their existing IM client ( Spark IM) is their contacts list is prepopulated showing ever user in the organization and they are grouped according to their AD OU. For example we can have an AD OU for Dallas and we have user A,B,C and another OU for Houston showing user X,Y, and Z. They show up in the contact list according to this structure. According to my system admin, Spark IM prepopulates the contact list because the domain is defined as scope when setting up the server for this application.
Now here is my dilemma. With Jabber it would be nice to have a feature like this. I've tried so many things and haven't been able to get anything like this to work. I know about the Bulk import/export contact list method but that only works if you have a csv of every single user in AD and in additional to that you need to add every contact per user. This method is not feasible. I also want this contact list to pull directly from Active directory and to list every user who is presence enabled. My management doesnt like the fact that each end user may need to build their own contact list as they're used to having all of that information from the get-go with their current IM client. Any thoughts or workarounds would be greatly appreciated.
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 ...