SIngle Number Reach Issue with new 9.1 cluster on E-164 Dial-plan.
I have SNR configured as I always have done it. This particular system works fine with SNR as long as the caller is external from PSTN. If an internal IP phone user dials another IP phone user that is SNR enabled, the remote destination doesn't ring.
DNs are all E-164 with four digit dialing (last four of DID) within a site and ten digit dial-plan across sites (full DID minus +1). User A calls User B, both are in the same site. 1001 dials 2002. Translation Pattern converts the number from 2002 to +12125552002, which is the DN on the phone. The remote destination associated with User B never rings. It'll work fine if user B gets a call from external PSTN.
Are all the Translations involved with E-164 killing the external phone mask somehow of the calling party so that call to the mobile device can never go out? It's the only logical thing I can think of.
I figured out the issue. There is an intercluster trunk between new system and old that was causing a problem with the shortened four digit and ten digit dialing. Taking that out of the picture fixed it. The ICT is only temporary during a migration.
If the Calling Party Number is causing the call to not go through, it is most likely through the carrier. I would start with a PSTN debug on the voice gateway the call is going out of. For T1s and SIP circuits, the error message you get will usually give you a sign that the calling party number is the problem. At the same time, you can check whether the call is making it to the voice gateway.
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...