Minimize ARS 4

[dhotep]

Can I just create:
Dialed Min Max Route Type
12 11 11 p9 fnpa

And that will replace all of this in my ARS?

Dialed Min Max Route Type
120 11 11 p9 fnpa
121 11 11 p9 fnpa
122 11 11 p9 fnpa
123 11 11 p9 fnpa
124 11 11 p9 fnpa
125 11 11 p9 fnpa
126 11 11 p9 fnpa
127 11 11 p9 fnpa
128 11 11 p9 fnpa
129 11 11 p9 fnpa

Seeing as how I could do this for any 1xx entry, I can reduce my ARS by a factor of 10 for these entries.

 

[Wibbers]

yes this will work.

 

[phoneguy55]

go nuts and just have one entry.

1 11 11 p9 fnpa

 

[4merAvaya]

If you're not using the Partition Route tables you can also eliminate the pX and just put the Route Pattern number in it's place.

Kevin

 

[dhotep]

Thanks guys, actually it will come down to very few ARS routes, maybe just one for domestic

We are moving to a VOIP solution (when it leaves my PBX) so even local numbers have to be 10 digit dialed. I have to use the partition route table due to the number of DID's we have at this location. We have to balance them between 2 VOIP routers, so I have to use COR and time of day to partition half the building to go out one router and half out the other.

A related question:

While tracing at other sites where the service is already in place, it seems the vendor does not care if it gets the 1 or not, so I was thinking of using PrfMrk 4 to always suppress it. Thoughts?

 

[wmainc]

If you are not needing any special digit manipulation, why not just use natl call type and forget about prefix marks?

 

[dhotep]

So I just leave the PfxMrk blank and set all ARS entries to natl? This will send out the 10 digits?

for instance if a caller dials 14235551212 it will outpulse 4235551212?

 

[4merAvaya]

I would suggest that you set up a'play' Route Pattern and point various test numbers to it and experiment. Call your cell phone, your home phone, the pizza parlor down the street, your family in the next state, etc.. See what works and what doesn't. One reason for multiple Route Patterns is to use the FRL value to control who can call where.

Kevin

 

[jimbojimbo]

Some of the suggestions above are going to potentially open you up to toll fraud. There may also be some significant manipulations to maximize least cost routing. If you are one site with one LD trunk than minimal is good but if you are multi-site, multi-trunk you probably want to take a hard look at where you are sending calls and how you handle fail-over. Also if you only had a 1 or 18 in your ARS you wouldn't be blocking 1809 same for 1900. Do you want your users calling Guam? Can everyone dial USLD? ARS Analysis, Route Patterns, FRL levels, and COR's work together to protect your system. Simple means open which is fine so as long as you are okay with the risk. I had a customer in California that went simple and it cost the company 30K in toll fraud charges in one month.

 

[dhotep]

@ jimbo:

Good points. Question for you:

If I have an ARS entry that states:

18 11 11 p9 fnpa

and another that states

1809 11 11 deny fnpa


Would the call to 1809 be blocked? I am assuming it looks for the most specific route, even when restricting.

 

[wmainc]

Yes, the system will pick the most specific match in the ARS analysis form.

 

[jimbojimbo]

Yes, most likely 1809 is restricted. This assumes that the 1809 is in the "all" table and you are not doing something with a location table that may permit the call for a specific location/site.

For instance if 1809 is restricted in the all table but 18095551212 was enabled in location table 5 then users in location 5 would be able to dial 18095551212. Users at other locations would not.