I have reviewed it. Your previous reply stated that BDI is ignored by the windows client.
There is no "Use Jabber Credentials" for EDI
Per the Document:
By default, Cisco Jabber for Windows uses Integrated Windows Authentication when connecting to the directory server. This parameter lets you manually specify a username in scenarios where it is not possible to authenticate with the directory server with the user's Microsoft Windows credentials.
Under the BDI settings you can enable or disable using the Jabber Credentials. Since Integrated Windows Authentication is not available for some of our users, and we do not wish to have a plaintext username and password (read-only access or not); and we do not have the bandwith for UDS; what are the remaining options?
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...