ARS route pattern

[CommoGuy101]

Hi All,
I have a strange one that I can't seem to figure out.
I have an extension 1234.
When a local call is made from this extension it hits route patern 30 and is completed.
When an international call is made it hits route 30 and gets a fast busy.
I was able to solve that problem by deleting digits in the route pattern.
Now local calls can't be completed.
Well I changed that back of course.

When I list ars ana I see that the local calls should use route pattern 1 and international hit route pattern 3 which has the 3 digits deleted.

So here is my question extension 2000 can make these calls without any issues and follows the route patterns I see in the list ars ana.
The only difference I can see is that extension 2000 is TN 1

Extension 1234 is TN 3.
When I list ars ana loc 3 I get no data.
I am not too sure how the calls are using route 30.
If I knew that then I could just build another route for international calls.


Anyone have any clues?

 

[AvayaTier3]

tenant and location routing are not the same thing.

list ars route chosen 011xxxyyyzzzz

should return something like "p3" which is a partition-route-table

PGN 3 column will be the route pattern for tenant 3, while tenant 1 and 2 use route pattern 3

change partition-route-table 3                                  Page   1 of   1
                           PARTITION ROUTING TABLE

                              Routing Patterns
    Route
    Index    PGN 1  PGN 2  PGN 3  PGN 4  PGN 5  PGN 6  PGN 7  PGN 8
    -----    -----  -----  -----  -----  -----  -----  -----  -----
    3        3      3      30

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

37 years Bell, AT&T, Lucent, Avaya
Tier 3 for 27 years and counting

http://bshtele.com

 

[CommoGuy101]

Thank you,

OK... I see that and the PGN is 30.

I was able to make the change and it is working perfectly.

Is there a reason that they would be using different route patternin each partition even though they are using the same trunks within the pattern.

 

[AvayaTier3]

can't imagine why unless they had tenant setup with different trunks at one time, then took them out and it was easier to change than totally reprogram all of the tenant translations.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

37 years Bell, AT&T, Lucent, Avaya
Tier 3 for 27 years and counting

http://bshtele.com

 

[surakmn]

Have you compared the CORs? Sounds like they might be using different routing partitions.