ARS-AAR Capacity Limit with Multiple Sites 1

[GHTROUT]

I'm far less than a year old in CM years. Here is what I have: Multiple sites (like 40+), each with their own PRI(s). When each site dials out, it uses it's own PRI. Yet all sites dial each other over the CM (we are all going to be 11 digit extensions). Each site needs its own ARS table for outgoing, correct?

If there are 800 possible NPAs (1200 to 1999) and 800 possible NXXs (200 to 999) and the system capacity is 12000 entries, does that not mean I can only go up 7 locations before I have to worry about reaching the upper level of system capacity in the ARS-AAR tables?

40 locations - each with their own PRI and dialing rules. How could I do this? What did Avaya intend when they built this?

~~
Gene at www.GHTROUT.com

 

[GHTROUT]

Is this the solution? Just simplify the ARS? What is the solution?

10, CAC_DENY (EXAMPLE, 9,1010288)
11, WOULD BE "911"
12
1262, LOCAL_WI
1274, LOCAL_WI
13
14
1414, LOCAL_WI
15
1534, LOCAL_WI
16
1608, LOCAL_WI
17
1708, LOCAL_WI
1715, LOCAL_WI
18
1800, TFN
1844, TFN
1855, TFN
1866, TFN
1877, TFN
1880, TFN
1881, TFN
1882, TFN
1883, TFN
1884, TFN
1885, TFN
1886, TFN
1887, TFN
1888, TFN
1889, TFN
19
1920, LOCAL_WI
1900, 900_DENY


~~
Gene at www.GHTROUT.com

 

[lopes1211]

Correct, you would not have explicit entries for every number. Most of our sites end up with about 50-100 entries per site. It all depends how restrictive you want to get with COR's and calling permissions.

-CL