When calling a few local numbers we get, "The # you have reached is not in service. This is a recording". The phone number we are calling is 703-412-1XXX. When I dial other numbers in the 703-412 range the call goes through. I know of 3 specific numbers that we can't reach. All of them begin with 703-412-1xxx.
I can reach all of the numbers on a POTS line (same LEC) and I can reach them using a cell phone.
I worked with our LEC last night and was told that the error coming back shows:
Message Type : SCP_X Release MSG
Cause : UNASSIGNED_NUMBER_CSE
Cause Location : USER
Generated locally or remotely : REMOTE
It looks as though our CM thinks this number is internal and unassigned. The technician asked me if the company I was calling is located in our building which it isn't.
I have looked through all of the route patterns and can't find any reason that the call wouldn't go through.
The record message that you are getting is a TELCO message, I'm sure that if you run a debug in the GW you will see the call, if this is the case CCM is doing his job and sending the call. Also if you see that the disconnect reason is from the PSTN the TELCO is the culprit.
You could post the debugs and CCM detailed traces to show you that.
Here's the trace. Looking at the dialing pattern 9.@ looks fine but the next line says Dialing Pattern Regular Expression = (9)([2-9][02-9]X)(XXXX) and I can see the problem there. Is that the culprit? If so, where/how can I change that pattern?
No, that is ok, all of your outbound calls would look the same at this place - what you really want to do is do isdn q931 debug on the router and make sure you are sending the call over to the PSTN - it seems you must be, or they would not be able to tell you the clear - so it is not you who think it is unassigned, the problem would be wherever the telco sends it next on its way to the destination number. We had a problem a lot like this, and the issue turned out to be the receiving side had calls restricted, and we were not sending a valid calling party number. You could try setting a calling party number on your gateway, so all calls look like they are coming from that, make it your main number or something, and see if the calls are accepted then.
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...