Time of day routing

[mikeydidit]

I have been looking for a way to totally restrict some extensions from making or receiving calls. I need this to be done by some sort of time of day. (Lets say off at 9:00 pm and on at 7:00 am) I have been searching for a while now and can't find what i need to program this. Going through what i have found, I guess this can be done by time of day routing charts?

If you have this setup would you mind sharing it?

I would appreciate it.

"A people that values its privileges above its principles soon loses both."
- Dwight D. Eisenhower (1890-1969), Inaugural Address, January 20, 1953

For the best response to a question, read faq690-6594

 

[testLED]

Change time of day....... will open a time of day routing table where you can administer the time against route patterns and then apply them to your ARS tables.

 

[inerguard]

If you want to set this per phone, then create a new COR with a time of day plan, then change this time of day plan to restrict calling during the certain hours.

Look at the COR screen and you'll see time of day.


[Started on Version 3 software 15 years a go]

 

[phonesrus]

Time-of-Day routing can be used for outbound calls, just set the appropiate time of day schedule based on a specific COR to route calls thru an unadministered route pattern or a deny partition route depending on whether you use "r" for route or "p" for partition in your ARS tables.
The ToD tables start at midnight 00:00 and thru 23:59.

The only way to restrict inbound calls would be by using a feature code to change the COR to a restricted one, but that requires that the option is enabled in customer-options. If that is enabled you could set up an Attd to change COR's at specific time day and night, but that is about the only way to do it for inbound calls.

 

[AvayaTier3]

Time of Day can also be used for incoming coverage

display system-parameters customer-options                      Page   5 of  11
                                OPTIONAL FEATURES

                                                         Time of Day Routing? y
--------------------------------------------------------------------------------
list station 1000

                                  STATIONS

         Port/    Name/                       Room/         Cv1/ COR/    Cable/
Ext      Type     Hunt-to             Move    Data Ext      Cv2  COS     Jack

1000     01B0701  Honea, Roger                              t34  1
         7434D                        no                         1
--------------------------------------------------------------------------------
change coverage remote 1                                        Page   1 of  23

                       REMOTE CALL COVERAGE TABLE

01: 97202211111           16:                       31:
--------------------------------------------------------------------------------
change coverage time-of-day 34                                  Page   1 of   1

                        TIME OF DAY COVERAGE TABLE: 34

           Act   Cvg     Act   Cvg     Act   Cvg     Act   Cvg     Act   Cvg
           Time  Path    Time  Path    Time  Path    Time  Path    Time  Path

 Sun       18:00 178     22:00 62        :             :             :
 Mon       18:00 178     22:00 62        :             :             :
 Tue       18:00 178     22:00 62        :             :             :
 Wed       18:00 178     22:00 62        :             :             :
 Thu       18:00 178     22:00 62        :             :             :
 Fri       18:00 178     22:00 62        :             :             :
 Sat       18:00 178     22:00 62        :             :             :
--------------------------------------------------------------------------------
change coverage path 178                                        Page   1 of   1
                                 COVERAGE PATH

                   Coverage Path Number: 178
                                                  Hunt after Coverage? n
                       Next Path Number:          Linkage

COVERAGE CRITERIA

    Station/Group Status    Inside Call     Outside Call
             Active?             n              n
               Busy?             y              y
       Don't Answer?             y              y         Number of Rings: 3
                All?             n              n
 DND/SAC/Goto Cover?             y              y

COVERAGE POINTS

    Terminate to Coverage Pts. with Bridged Appearances? n

      Point1: r1                Point2: h10               Point3:
      Point4:                   Point5:                   Point6:
--------------------------------------------------------------------------------
change coverage path 62                                         Page   1 of   1
                                 COVERAGE PATH

                   Coverage Path Number: 62
                                                  Hunt after Coverage? n
                       Next Path Number:          Linkage

COVERAGE CRITERIA

    Station/Group Status    Inside Call     Outside Call

             Active?             n              n
               Busy?             y              y
       Don't Answer?             y              y         Number of Rings: 3
                All?             n              n
 DND/SAC/Goto Cover?             y              y

COVERAGE POINTS

    Terminate to Coverage Pts. with Bridged Appearances? n

      Point1: 1111              Point2: h10               Point3:
      Point4:                   Point5:                   Point6:
--------------------------------------------------------------------------------

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting

http://bshtele.com

 

[mikeydidit]

I appreciate everyones replies and the time that Brett has spent in trying to help me on the side with this. I guess my understanding of ARS is just not where it needs to be to be comfortable enough to do this. Of course, I have never taken any administration classes so that doesn't help. The maintenance classes I have taken scratched the surface on it, but thats about it.

I guess what I really do not have a grasp on is this.

 change time-of-day 1                                            Page   1 of   1

                           TIME OF DAY ROUTING PLAN 1

          Act  PGN    Act  PGN    Act  PGN    Act  PGN    Act  PGN    Act  PGN
          Time  #     Time  #     Time  #     Time  #     Time  #     Time  #


 Sun      00:00 1       :           :           :           :           :
 Mon      00:00 1       :           :           :           :           :
 Tue      00:00 1       :           :           :           :           :
 Wed      00:00 1       :           :           :           :           :
 Thu      00:00 1       :           :           :           :           :
 Fri      00:00 1       :           :           :           :           :
 Sat      00:00 1       :           :           :           :           :

The PGN number from what Brett has told me, relates back to the tenant partitioning. I am pretty sure we do not use it so everything falls under TN 1. Looking at the partition route 1, everything is listed under 1 and their are 15 entries.

change partition-route-table 1                                  Page   1 of   1
                           PARTITION ROUTING TABLE

                              Routing Patterns
    Route
    Index    PGN 1  PGN 2  PGN 3  PGN 4  PGN 5  PGN 6  PGN 7  PGN 8
    -----    -----  -----  -----  -----  -----  -----  -----  -----
    1        8
    2        5
    3        deny
    4        6
    5        9
    6        4
    7        33
    8        7
    9        1
    10       11
    11       10
    12       640
    13       3
    14
    15       12

Now heres the part that is about as clear as mud. I "think" this all boils down to pointing another COR on the time of day routing. I have a COR 2 that totally restricts all calls out. Thats what I would like to use. But i am not nearly comfortable enough to do this right now.

"A people that values its privileges above its principles soon loses both."
- Dwight D. Eisenhower (1890-1969), Inaugural Address, January 20, 1953

For the best response to a question, read faq690-6594

 

[DontDeleteMeAgain]

Also, depending on what version you have, you can use Station lock COR.

 

[phonesrus]

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.

 

[AvayaTier3]

cut and paste your screen shots, and do a preview and edit.

When you edit, use tags for each side of your text that you cut and paste from your switch screens. Look at the editing tips at the bottom of your screen when you go into edit mode, before you Submit Post

http://bshtele.com/images/edit.html

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting

http://bshtele.com

 

[phonesrus]

Thanks Brett,
I will have to look into that, I have never used it, I guess I have a bit of a learning curve now.
Regards,
Donn

 

[mikeydidit]

Sounds like where I am at on ARS Donn. LOL Never played with it so I am having to learn it.

"A people that values its privileges above its principles soon loses both."
- Dwight D. Eisenhower (1890-1969), Inaugural Address, January 20, 1953

For the best response to a question, read faq690-6594