Mikey,
List your ARS ANA tables and print them. Now in the tables you see the route pattern as p(x) the "p" is the Partition "route index", and (x) is the line in the table. In your example above "p1" points all calls to route pattern 8, so therefore all calls with "p1" are routed. "p3" is deny, so all calls are denied.
Of course "disp route-pattern 8" shows you what trunk group is being used, FRL level and digit manipulation is applied, etc.
Now create a new COR called "Night ToD restricted" duplicating the COR permissions of the current stations that you wish to restrict, but change the Time of Day Chart to "2"
Now change Time-of-Day 2.
Leave the start time 00:00 and 2 in the first field alone, in the next fields put 07:00 and 1, and the next put 21:00 and 2. Do this for each day (su-sa). This restricts calls from 9:00 pm. to 7:00 am. to PGN 2, but allows all from 0700 to 2100 as exists in PGN 1. Check all of your existing administered COR's to be sure you are not using ToD 2 for anything else!
Now change Partition-route table 1.
Under PGN 2 put "deny" for each "route index" you wish to block outbound calls. Be careful about "911" if you wish to allow that, being in a Hospital environment you have an internal emergency number, if I remember correctly.
Next you will have to implement this by changing the COR of all stations that you wish to restrict by this method to the new COR. Use a test station first using the new COR, make a test call then change the 07:00 PGN to 2 and retest, calls should be blocked, then change it back to 1.
This should give you what you want for outbound calls and Brett's suggestion using ToD coverage and a remote coverage to a blocked or bogus number should work inbound during restricted times, I hadn't thought about that one long enough.
ARS and AAR analysis tables add a lot of granularity to call routing and Partition routing adds another level to that, it is not hard to understand, it can be complicated and confusing to some though. You have to remember that the switch is a strictly logical device following "if>"but">"then" logic.
The nice thing about this switch is you can build a test sceneario as a seperate entity and play with it to accomplish what you are trying to do. And once you find a solution "make it so".
Now if you could tell me how you accomplish those nice screen shots you post, that would make me happy. I hate the c### that copy and paste produces, otherwise I would have posted some screen shots for you.
