The situation we have right now is - whatever comes from the PMX to the CCM has no leading 0 in the calling party information (based on what I see in the routers call debug log). As an example - a call from Netherland looks like this:
Calling Party Number i = 0x1181, '3120xxxxxxx'
Called Party Number i = 0x81, '142'
For national and mobile numbers I used Cisco recommendation to add a leading 0 via translation pattern before the call is routed to the desk phone.
But it only works for national and mobile numbers, not for international incoming calls.
- a call from 160xxxxxxx (mobile) get's transformed to 00160xxxxxxx. If called back, the first 0 get's removed (PreDot) and the call works just fine
- a call from 441xxxxxxx (national) get's transformed to 00441xxxxxxx. If called back, the first 0 get's removed (PreDot) and the call works just fine
- a call from 310xxxxxxx (international, Netherlands) get's transformed to 0031xxxxxxx. If called back, the first 0 get's removed (PreDot) and the call works if the number exists, but as a national call and is not routed to the correct target! Because one 0 is missing!
How can I manage that international calls are also handled correctly by the CCM? (to add three 0 instead of two?) I can't see the solution for now. You may wonder why we add two 0 to those calls instead of just one. That's because in the last 20 years local users had to dial an extra 0 for outside calls.
How to configure prior "0" for international calls?
The funny question is - if I would have decided not to do the translation pattern thing but instead add "00" to the same service parameter mask under "national number prefix" - it would have worked, too. Right? :-)
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...