Okay, two ways to do it...
1.):
in 8A4005>201xxx>yyyy program every possible dialing combination (where xxx is an office code or portion of an office code, and yyyy is a route plan)
in 8Ayyyy>1> zzzww where yyyy is the route plan from 8A4005, 1=1st choice, zzz is a handle for future reference, and ww is a trunk group.
8Ayyyy>2>zyzwx (2nd choice, reference zyz, trunk gp wx)
Omit "blocked" entries from the table, or assign an invalid route (one without any entries in 8Ayyyy)
2.):
Leave 8A4005 with entries beginning with the office code. Note the route plan.
8A4005>5551212>yyyy (yyyy=route plan)
8Ayyyy>1>xxxzz (xxx=reference #, zz = trunk group)
8A5xxx>100>9xxx (where xxx is reference # from 8Ayyyy, above)
8A9xxx>0>201 (where xxx is from 8A5xxx, and 201 is the digit string to be inserted - max 32 digits)
As with the first method, you can have multiple trunk group choices (8Ayyyy>2>xxxcc, 8Ayyyy>3>xxxdd) but as long as the reference number (xxx) remains the same, 201 will be inserted at the beginning of the string.
Now, obviously, you need to plan this out and consider 1+areacode+7digit (clue: don't put 201 in front -- use a different route plan and reference number), 1 800+, 1 900+, 976+, 011+, 911, 9+911, etc. when planning your routes. Test each one, even the 911s. Especially the 911s.
You'd be a lot better off to hire a professional, I'll tell you that right now. He'll charge even more to straighten it out if you tangle it up.
I also strongly recommend a database backup before you start.
