Scheduled Access Restriction is a feature which allows the call restriction parameters of an extension to change according to the time of day. The call restriction parameters can be changed up to 8 times per day. The restriction requirements are put into a SAR (Scheduled Access Restriction) table, and the SAR table is assigned to the extension(s) that are to be restricted in this way. The system potentially has 1000 SAR tables. The diagram below illustrates a SAR group with the following call restrictions:
Monday-Friday between 1800 and 0759 (the next day) totally restricted access except emergency numbers.
Monday-Friday between 0900 and 1259 (busy period) totally restricted from gaining access to any route with a TARG = 2.
Saturday and Sunday between 0000 and 2359 totally restricted access except emergency numbers.
Note: Between the periods 0800 - 0859 and 1300 - 1759 on Monday to Friday call restriction for any extension in this SAR group would be determined by the call restriction parameters of the individual extensions.
Overriding SAR
If SAR is required to be overridden at any time the following Flexible Feature Codes may be used :-
SADS (Disable) + Authorisation Code
SAEN (Enable) + Authorisation Code
SALK (Lock) + Authorisation Code
SAUN (Unlock) + Authorisation Code
SADS enables an authorised extension user to temporarily disable SAR.
SAEN cancels a previous SADS command i.e. re-enables SAR.
SALK enables an authorised extension user to lock extension users into a particular OFFP (off period). This means that until the SAUN (Un-lock) code is entered, extensions would be restricted by COS, TGAR and NCOS as specified against that period. The system administrator determines the Lock period for each SAR group.
SAUN cancels a previous SALK command.
The authorisation codes provide security against misuse and have to be exclusively set up for SAR.
Feature Implementation
SAR groups are set up, changed and printed in Program 88.
The following notes will explain certain prompts in LD 88 concerning SAR:-
SCDR Set this to YES to cause a Call Detail Recording - CDR (Call Logger) output to be generated when a Flexible Feature Code is used to override SAR.
OFFP Specifies the Off Period Number (1 - 8)
STAR Start time for period
STOP Stop time for period
DAYS Days of the week that the period is to apply (1=Sunday, 7= Saturday)
COS, TGAR and NCOS
This is where you specify the call restriction parameters for the period.
ICR Set to YES if incoming calls are to be intercepted and sent to the attendant
Set to NO if incoming calls are not to be restricted.
LOCK Enter the period number that users of this SAR group will be locked into if SAR Lock is activated.
Use Program 10 / 11 to link an extension into a SAR group :-
ITEM SGRP x
(where x is the desired group number. 0 means not in a group)
Example
This example shows a new SAR group 2 being set up to achieve the following
call restriction:-
Monday-Friday 0800-1759 Totally Un-restricted
Monday-Friday 1800-0759 (Next Day) Tree 2 is to apply
Saturday and Sunday 0000-2359 Tree 2 is to apply.
LD 88
Load Program 88.
REQ NEW
TYPE SAR Identify Scheduled Access Restriction
CUST 0
SGRP 2 Group2
SCDR YES Call Detail Recording
OFFP 1
Period1
STAR 00 00 00 00
STOP 00 00 07 59
DAYS 2 3 4 5 6 Indicates Mon-Fri
COS TLD Call Restriction parameters for this period
TGAR 0 Call Restriction parameters for this period
NCOS 2 Call Restriction parameters for this period
OFFP 2
Period 2
STAR 00 00 08 00
STOP 00 00 17 59
DAYS 2 3 4 5 6
COS UNR
TGAR 0
NCOS 0
OFFP 3
Period 3
STAR 00 00 18 00
STOP 00 00 23 59
DAYS 2 3 4 5 6
COS TLD
TGAR 0
NCOS 2
OFFP 4
Period 4
STAR 00 00 00 00
STOP 23 59
DAYS 1 7
COS TLD
TGAR 0
NCOS 2
OFFP
ICR NO Incoming Calls Not Restricted
LOCK 2
REQ END
The example below shows how TN 9 0 has been linked to this new SAR group .
Assign TN 9 0 to SAR group 2.
LD 10
Load Program 10.
REQ CHG Change
TYPE 500
TN 9 0
ECHG YES
ITEM SGRP 2 Restrictions defined by SAR group2 are applied to this extension
ITEM
Colin,
I found your post (which is very helpfull). I set up the following and the only problem I'm having is bypassing the SAR. I can't find clear definitions for the different FFCs. Where does FFC AUTH come in to play? What about SADS, SAEN, SALK, and SAUN? I'm trying to block toll calls during a certain time/days and allowing people to bypass the restrictions with an auth code. Here's my programming:
REQ prt
TYPE aub
CUST 0
SPWD
CUST 00
ALEN 04
ACDR YES
AUTHCOD_ALRM OFF
RANR X
ACLE NO
BRST 03
RTRY NO
AUTO NO
CLAS COS TGAR NCOS CLAS COS TGAR NCOS CLAS COS TGAR NCOS
when you use the same load to print aut, you'll see auth codes asigned to a class, your classes 1 and 3 are both set up to change ncos to 3, no others are used more then likely. if in the cdb, class 2 and below is entered, you will get a auth tone after the number, i would use tod in my rlb, ld 86.. change a class to unr ncos 5 or so, then after 1700 or whenever change the frl to of your rlb used for ld to 5.. then a ncos 4 works during the day for ld after hours use auth to change the class to five, both ways work but this is the fastest for me
I think that's a great way to do it, I just don't know exactly where to start. I've never applied TOD restrictions on the RLI. Here's one of the routes I would want to restrict by TOD.
FEAT rlb
RLI 20
RLI 20
ENTR 0
LTER NO
ROUT 8
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
CNV NO
EXP NO
FRL 2
DMI 0
FCI 0
FSNI 0
SBOC NRR
OHQ NO
CBQ YES
ENTR 1
LTER NO
ROUT 23
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
CNV NO
EXP NO
FRL 2
DMI 0
FCI 0
FSNI 0
SBOC NRR
OHQ NO
CBQ YES
ISET 2
NALT 5
MFRL 0
The NTPs aren't very helpfull. Can you guide me in the right direction?
Thanks,
Fred
"Wise men learn more from fools than fools from wise men
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.