CME international calls failing and using wrong dial-peer
I'm having a problem where international calls will occasionally fail, and the user will get an "invalid number" recording. After doing some debugs on the CME box, I found that international calls are matching against two dial-peers:
DP1: destination pattern 9T
DP2: destination pattern 9011T
For reference, DP1 is in place to allow users to make local calls without having to enter the area code, and it prepends the area code on the dial string. DP2 matches international exit code, and prepends 011 to the dial string.
So it seems like when the call fails, the call is initially going out using DP2, but is getting this message:
Aug 1 09:50:44 10.5.2.20 39205: Cause i = 0x8081 - Unallocated/unassigned number
I'm assuming that there is some variable delay in the call setup process that is causing the occasional failures. Based on that assumption, is there anything I can do to lengthen the amount of time CME will try and build the call using DP2 before it moves to DP1? Any other thoughts?
Re: CME international calls failing and using wrong dial-peer
Thanks for the response. So are you saying that the other end just isn't answering? I would expect it to go to voicemail or something, or at least ring longer than we are waiting before the error message comes back. Also, we can have the call fail on CME, then call with our cell phone and get connected -- so it's not like they aren't there to receive our call.
In regards to the debug -- I don't actually see a SETUP before the first disconnect, I only see a CALL_PROC. I've attached the debug for review.
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...