I am trying to do the opposite that most people do. I notice that Jabber Windows auto integrates with the Windows PC AD login, is there any way to remove that default integration with Windows AD? It is churning out wrong caller ID due to the AD LDAP object instead of the actual caller ID from the CUCM. I tried using UCD in the jabber XML file and in the CUP server I did not define any LDAP integration.
I already have the UDS line in the jabber XML file. So what happens is that the Jabber automatically integrates with the Windows Domain Log in and there is no way I can find to disable this. I shall wait for 9.7 to come out and see how it goes.
Done that. Does not work as usual, but I tried Jabber 9.2 for Windows, there is no such feature to integrate with LDAP hence the correct user name is shown. Hope that 9.7 we can have the option to do disable that.
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...
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 discusses the bas...