Well, here is what I did: first, I ran a "list partition-route-table" and "list partitioned-group" to see what I had in place. Since we do not use time-of-day routing, I was able to keep all of the existing COR settings. Then, I created all new multiple route patterns for each location (local calls, long distance calls, toll-free calls, and 911 calls). My S8700 and ESS locations have PRI/ISDN trunks; all of my other locations have CO trunks. All of the new route patterns (except 911) use all three trunk groups (local, S8700, ESS) as options. 911 calls ONLY route out of the local trunk.
Then, I created/modified the ARS analysis table for each location, using the new route patterns. I put together a list of test numbers (usually time & temperture recordings, or other information recordings), and in the beginning, I had someone in each location dial these test numbers while I monitored the results via a "list trace station xxxx" command, so I could make sure that the calls routed correctly. I would even busy out the different trunks to make sure that the calls would route correctly over trunk choice #2 if trunk choice #1 was busy or unavailable.
Once I was comfortable with the ARS analysis table for a location in a specific area code, I was able create the rest of the tables for the remaining locations in that area code. (Currently, I have 32 locations in three area codes; all in Texas).
If you want, you may contact me via faq690-7157, and I can share the checklist I use when I set up all of my new locations.
Susan
“Before you criticize someone, you should walk a mile in their shoes.
Then, when you criticize them, you are a mile away ...
and you have their shoes.”
