The only way to fix this is to remove the conflict. You need to renumber the extensions that are in the 9XXX range into another spare range. Alternatively move to a 5 digit number plan and prefix with another digit i.e. 29XXX.
the thing with the dial tone is that since CUCM does digit analysis digit-by-digit and creates a 'potential matches' list only when ALL the DNs or patterns on that list have the checkbox for the secondary dial tone CUCM won't generate it. The only elements that have the checkbox are route patterns and translation patterns, so if you have a phone DN in there, until CUCM is sure that there is no chance you're going to dial it and kicks it out from potential matches you won't get the secondary dial tone
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...