7 digit & 10 digit dial string starting with 4 on NANP ringing without a dial-peer

[nascoentr]

I'm facing a strange problem or maybe its because of my lack of knowledge of the NANP.

I have only one route pattern @# and i dont have any dial-peer in the gateway that matches a number starting with 4 at all... but strangely when i dial any 7 digit or 10 digit number starting with 4 (this happens only if the number i'm dialing starts with a 4), for example

4xxxxxx (7 digit dial string)

or

4xxxxxxxxx (10 digit dial string)

the call goes through and it dials the number and i can hear the rings but none of my physical devices are ringing cause none of the phones have that kind of an extension (they are all 4 digit extension starting with 1, like 1xxx), i'm sure its dialing something within the cluster and is not forwarding the request to the gateway cause i dont have any dial-peer in the gateway for numbers starting with 4.

i dont understand what the callmanager is ringing, is there any specific rule in NANP that explains this issue...

thanks for all the help.

[Jaime Valencia]

Have you tried DNA to find out what pattern you're matching??

HTH

java

If this helps, please rate

www.cisco.com/go/pdihelpdesk

[nascoentr]

thanks... i'll try and get back.

[nascoentr]

Dear Javalenc,

I've attached a screenshot of the DNA result,

just to make things clear, the ext. (1000) I tested the DNA tool for is added to the "Tech-Dir" CSS which consists of the NANP partition that is assigned to the @# route pattern.

Please Note: if i remove the NANP partition from the CSS Tech-Dir then it does not give me this strange behaviour so i'm damn sure its something to do with the @# route-pattern which matches all numbers within the NANP.

appreciate any help.

thanks

[nitsinha]

Hi nascoentr,

The DNA result which you have attached shows that there is no route pattern matched on the CUCM when you dialled that number(4444444444). Since the route pattern has a # at the end it will not be matched till you press the # symbol at the end of the caling number. So my question here is

Everytime when you dial the 7 or 10 digit no., do you press # at the end?

What else(route patterns or DN's) does the NANP partition contain?

What is the gateway type(SIP,H323) you are using?

Regards

Nitesh

[nascoentr]

Hi Nitesh,

Yes I do press the hash at the end of the 10 digit or 7 digit dial string starting with 4 and I hear rings (like as though a device is ringing) but if i dont press the # at the end and wait for the 15 sec interdigit timeout it says "the call cannot be completed" as expected since the # at the end requires the user to press the # after dialing the string to indicate that he is done dialing.... now again if I alter the route pattern to only @ (without the #) and dial the 7 or 10 digit dial string starting with 4 it rings again after the 15 sec interdigit timeout...

The NANP partition is only associated with this one route pattern (@#) and i have just one route pattern in my whole cucm config ( i had many but I removed all of them and just kept the @# pattern to test this problem).

To summarize, the NANP partition is assigned to the @# route patter and is added to the "Tech-Dir" CSS which in turn is added to the line of the ip phone i'm dialing from (Ext. 1003).

I'm certain this has something to do with the NANP Route Pattern because if I remove this pattern and configure specific patterns for local, national, international, mobile, etc... numbers it does not produce this behaviour.....

The NANP is of the format +1 NPA NXX XXXX, where NPA is the Area Code and the first digit can only be 2-9 the Nxx is the Cent. Office Exch Code and the first digit again can only be from 2-9 and the last 4 digits of the subscriber number can be anything, this is my understanding which i believe is right.

i'm stumped at the behaviour of any 7 or 10 digit dial string starting with 4 only, it doesn't happen with a dial string that starts with any other digit other than 4 and again only with the 7 and 10 digit dialstrings starting with 4.

Again, if i remove the NANP route pattern of @# and keep specific route patterns for my dial plan i dont have a problem and things work as they should be.

Gateway type is H.323.

thanks for all the hlep, looking forward to some pointers..

[nitsinha]

Hi,

Your understanding of the NANP dial-plan is absolutely correct. I don't know why you are using a single @# route pattern for routing out all your calls. It is always advisable to create separate route patterns for local,national,international etc. so that later it will be easier for you to assign calling privileges in your network. Anyway do a further DNA, but this time do remember to put a # in the called no. section. Also if possible reproduce the problem and post its Call Manager traces here to further look into this problem.

Regards

Nitesh

PS: Pl rate helpful posts

[nascoentr]

thanks Nitesh,

I'm dont use the @# route pattern only, i do have seperate specific route patterns for local, national, intl, etc.... but its just that i was playing around with route filters on the NANP patterns and i came across this problem that is strange....

i'll get the traces and post again shortly.

[nitsinha]

Ok!! since you already have specific route patterns working in your network, i hope this issue is not affecting your production network . But still to have a better insight into the problem do post the traces.

Regards

Nitesh Sinha

PS: Pl rate helpful posts.