While it rarely comes up, when one of our users tries to dial a number that contains 011, CallManager cuts the 011 out at the point it's in the number. For instance, one of Cingular's help numbers is 18008011101. When you try to dial it "918008011101" shows as the Dialed Digits and the User Information is correct. But as the call is being processed, the calling number becomes "0000" and the called number becomes "18008101".
I understand that the route pattern 9.011! is going a little nuts here, but does anyone know how to solve it?
There are 3 key Route Patterns that are used in this instance. 9.@, 9.@ with the Toll Free route filter, and 9.011! for routing international calls. I dont think that this is a 1800 issue being as I got the same type of thing on the Dialed number "917183820011". It magically got changed to 17183820.
What also might be important is that the same 9.011! route pattern entry is put in several times for several Departments and locations we have, but they are different Route Groups.
I hope I have elaborated enough information. The company that installed our system is Cisco Gold Certified and I have to assume they knew what they were doing. I am just trying to absorb it all.
so it looks like it's hitting the correct route pattern. When using the analyzer don't use 0000 for calling number. Look in the RL now and see if they are manipulating digits there. I don't believe any filters need to be used for LD or 11 digit dial..Are you guy's trying to do TollBy or anytihng like that. Can you capture the dial-peers on the GWTY....
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...