ARS routing 1

[Jsaunde7]

I have 3 locations in my CM. I have an extension set-up to call forward to my cellphone and I'm getting the below in my trace. I'm using partition-routing-tables in my dial strings. If I change the partition-routing-table to the actual route-pattern I'm using the call goes through. Can any one help?

Dialed Total Route Call Node ANI
String Min Max Pattern Type Num Reqd
1864 11 11 p307 fnpa n


time data

18:06:47 TRACE STARTED 03/16/2020 CM Release String cold-01.0.532.0-24811
18:06:48 Calling party trunk-group 106 member 167 cid 0x25eb
18:06:48 Calling Number & Name 4413 864 3124413
18:06:48 term station 14023 cid 0x25eb
18:06:48 call-forwarding 91864449
18:06:48 denial event 1751: No AAR/ARS route pat/pref D1=0x83006a D2=0x1968449
4
18:06:48 call-forwarding 91864449
18:06:48 term trunk-group 106 cid 0x25eb
18:06:48 idle trunk-group 106 cid 0x25eb
18:06:56 TRACE COMPLETE station 14023 cid 0x0

 

[Jsaunde7]

any assistance out there

 

[joe2938]

the station cor will tell which time of day it is using, so if it's 2 then diaplay partition route table 2 and look at the 2nd entry, they can only be 8 partitions. This is why they went to location based.

ACSS IP Office AIPS IP Office

 

[Jsaunde7]

So here is my Cor below..Time of Day Chart 1...display part route table 1...what am I missing from here on..Am I looking at PGN 1 which is using route pattern 2?

FRL: 6 APLT? y
Can Be Service Observed? y Calling Party Restriction: none
Can Be A Service Observer? y Called Party Restriction: none
Time of Day Chart: 1

change time-of-day 1 Page 1 of 1

TIME OF DAY ROUTING PLAN 1

Act PGN Act PGN Act PGN Act PGN Act PGN Act PGN
Time # Time # Time # Time # Time # Time #


Sun 00:00 1 : : : : :
Mon 00:00 1 : : : : :
Tue 00:00 1 : : : : :
Wed 00:00 1 : : : : :
Thu 00:00 1 : : : : :
Fri 00:00 1 : : : : :
Sat 00:00 1 : : : : :


display partition-route-table 1 Page 1 of 4
PARTITION ROUTING TABLE

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

 

[joe2938]

so on your partition route table look at your pgn 1 entry, so if its says 24 then your route pattern is 24. So if ars says p240, disp partition route table 240 and your route pattern will be the pgn 1 entry. Hopefully you understand what I am saying here.

ACSS IP Office AIPS IP Office

 

[Jsaunde7]

So I confirmed the route pattern for the Partition route table that is being used for dial string. It's using a rout-pattern for LD calls but still getting denial event in my trace

 

[joe2938]

so something is different then from the partition route versus the regular route pattern

ACSS IP Office AIPS IP Office

 

[Jsaunde7]

Where and how would I be able to track this down and fix. Main reason using partition tables is to prevent calls from being made to certain area codes before 8am local time. Any other alternatives than using partition tables.

 

[joe2938]

yes now a days location based ars tables are used, you really should bring in some help as ars tables with partition tables are pretty difficult if you have not worked with them alot, suggest googling avaya world class routing

ACSS IP Office AIPS IP Office