Sounds like you have a device with an extension that is very close to your pattern:
The person that pressed 9.@ would have to wait until the inter digit time out had passed. You can test this by pressing 9.# This will force the system to stop looking for the longest match. The pause you are getting is just the system looking for more digits to base it routing decisions on.
Yes, you do have the secondary dialtone after the 4th digit and you will as long as you have any 4-digit DNs that start with a 9. The secondary dialtone is placed in the digit analysis when the only remaining pattern matches are Route Patterns or Translation Patterns that specify the "Provide Outside Dialtone".
The problem is that you have extensions that begin with your outside access code. That's a problem, for a couple reasons. For instance, how do you seperate internal calls from outbound 7-digit dialing or 10-digit local? Probably better in your case to change the outside access code to 8, or translate the incoming DN's.
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...