Using Extension Mobility on CUCM6 seems to create problems when using DNA. If you select "Phone" in DNA and search for a user who is a EM and is logged into a handset but not associated to it which is normal for EM then DNA does not allocate the user . It does locate it if you choose analyser but then you have to select the correct CSS but that does not take into account the device CSS which may impact the call routing. Has anyone else seen this? our SI suggests it`s a Cisco "Feature", this Feature only appeared since Cisco has "separated" the DN from the device as now you have to search in a different column - Device and call routing
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...