ROUTING PROBLEM

[charleshagen]

My local area code is 920. However I have some numbers to call in 920 that require the full area code and phone number be dialed. I have a CO trunk group for local calls.

Here is what happens...

If I dial a 1920723xxxx long distance call, the 1920 gets stripped. I inserted digits 1920 into the route pattern and it seems to insert them on 262-xxx-xxxx calls too.

I need it set up so that if I dial 1920 on a number it goes out as dialed.

How do I sort this out?

 

[Bobg1]

In your ars ana setup a pattern to match the 920723 and route it via the trunk you need it to go to.

 

[charleshagen]

I have only 1 trunk group at this time. all calls go through it and so how am I supposed to get it to identify when it is supposed to strip and not strip the 1920 dialing?

Charles

 

[avayaman]

I don't see why you can't simply define 1920 & 920 in your ars analysis table. You would designate 920 as locl & 1920 as fnpa. Send them to the same route pattern with no inserted digits. I have the same situation here in greater Vancouver where one of the 2 area codes is 604. Whistler which is 100 miles away also has area code 604 and a 1 has to be dialled. Here is my ARS: Note the differences between 604 & 1604. They do route to different route patterns, but the only difference in those is FRL levels.

0 1 1 p4 op n
0 8 8 deny op n
0 11 11 p4 op n
00 2 2 deny op n
01 9 17 deny iop n
011 10 27 p7 intl n
11 2 2 p6 alrt n
12 11 11 p1 fnpa n
13 11 11 p1 fnpa n
14 11 11 p1 fnpa n
15 11 11 p1 fnpa n
16 11 11 p1 fnpa n
1604 11 11 p1 hnpa n
17 11 11 p1 fnpa n
1778 11 11 p1 hnpa n
18 11 11 p1 fnpa n
1800 11 11 p8 pubu n
18005551111 11 11 p8 pubu n
1809 11 11 deny pubu n
1855 11 11 p8 pubu n
1866 11 11 p8 pubu n
1877 11 11 p8 pubu n
1888 11 11 p8 pubu n
18887000400 11 11 deny pubu n
19 11 11 p1 fnpa n
1900 11 11 deny fnpa n
1xxx555 11 11 p1 fnpa n
1xxx976 11 11 deny fnpa n
2 7 7 deny locl n
310 7 7 p3 locl n
3 7 7 deny locl n
4 7 7 deny locl n
411 3 3 p1 svcl n
5 7 7 deny locl n
6 7 7 deny locl n
604 10 10 p3 locl n
611 3 3 p9 svcl n
7 7 7 deny locl n
778 10 10 p3 locl n
8 7 7 deny locl n
9 7 7 deny locl n
911 3 3 p5 alrt n


Paul Beddows
Avaya Implementation
Telus
Vancouver, Canada
E-mail via

http://www.vancouver.hm/email.html

 

[avayaman]

Sorry I mean't 1604 or 1902 should be type hnpa not fnpa.

Paul Beddows
Avaya Implementation
Telus
Vancouver, Canada
E-mail via

http://www.vancouver.hm/email.html

 

[avayaman]

I also forgot to explain that the reason digits 2,3,5,7, etc. are "deny" is because we have 10 digit dialing. Those entries ensure the caller gets turkey tone from the Avaya if they only dial 7 digits rather than the annoying recording from the CO. 18887000400 is a scam number in the Dominican Republic & should always be entered into the ARS with deny. 1800555111 is ATT's new calling card number. I have it in there since this particular ARS is from a hotel switch. Guestrooms are not normally allowed to dial 1800555 numbers in this particular hotel, but this particular one is allowed.

Paul Beddows
Avaya Implementation
Telus
Vancouver, Canada
E-mail via

http://www.vancouver.hm/email.html

 

[Bobg1]

you can set up another routing pattern for the numbers you have trouble with. You can still use the same trunk group.

 

[charleshagen]

created a second route pattern for 1920 and inserted 1920. then added a 920 and selected route patter 1 for that. will try it.

 

[charleshagen]

Not sure why, but this does not seem to be working.

Charles

 

[Bobg1]

Check and see if there is something in your digit analysis table that is interfereing.

 

[charleshagen]

Please elaborate. I have route pattern 1 with 920 as a local call. I set up pattern 2 with 1920 that inserts 1920 into the string. I have a specific number or two for testing but it is not happening. Is there someone out there with a 920 PBX who can cross reference?

Open to suggestions and instructions...

Charles

 

[Bobg1]

I'm in 920
I don't understand what you are doing with the route patterns.

 

[charleshagen]

I think it is the NPA. I pulled it from route pattern 2 and I think that fixed part of it. Also, we are using partition 1,2 etc. I checked the ars ana for 1920 and it was set to fnpa...changed it to locl. now it seems to work...I THINK. need to test it more.