Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Call barring when..... 2
- Thread starter mikeyb123
- Start date
-
1
- #2
MikeIn order to implement call barring an extn should have a CLS (class of service) of TLD. Then any outgoing call will be refered to the FCR (flexible code restriction) tables. The NCOS number allocated to the extn TN relates directly to the FCR table number.
The call barring tables are printed and changed in overlay 49, as below
LD 49
REQ prt
TYPE fcr
CUST 0
CRNO enter the table number or
C/R (a carriage return will result in all
tables being printed out)
In order to change a table enter CHG at the REQ prompt and amend the allow/deny digit sequences as applicable.
OCB2 0-MAXT NFCR tree for Outgoing Call Barring level 2. Enter 255 to deactivate. - OCB3 0-MAXT NFCR tree for Outgoing Call Barring level 3. Enter 255 to deactivate. TYPE FFC Gate opener. CUST 0-99 Customer number. - SCPL 0-8 Station Control Password Length. Prompt Response Description REQ NEW Add new data. TYPE FCR Flexible Code Restriction. CUST xx Customer number. CRNO (0)-254 New Flexible Code Restriction tree number. INIT ALOW DENY Allow or deny digit strings not in tree. ALOW xxxx xxxx y...y Digit sequence to be allowed unconditionally. Digit sequence to be conditionally allowed and maximum number of digits that can follow. UPDT (YES), NO Data is correct and NFCR tree can be updated. DENY xxxx xxxx y...y Digit sequence to be denied unconditionally. Digit sequence to be conditionally denied and maximum number of digits that can follow. UPDT (YES) NO Data is correct and NFCR tree can be updated
Colin
The call barring tables are printed and changed in overlay 49, as below
LD 49
REQ prt
TYPE fcr
CUST 0
CRNO enter the table number or
C/R (a carriage return will result in all
tables being printed out)
In order to change a table enter CHG at the REQ prompt and amend the allow/deny digit sequences as applicable.
OCB2 0-MAXT NFCR tree for Outgoing Call Barring level 2. Enter 255 to deactivate. - OCB3 0-MAXT NFCR tree for Outgoing Call Barring level 3. Enter 255 to deactivate. TYPE FFC Gate opener. CUST 0-99 Customer number. - SCPL 0-8 Station Control Password Length. Prompt Response Description REQ NEW Add new data. TYPE FCR Flexible Code Restriction. CUST xx Customer number. CRNO (0)-254 New Flexible Code Restriction tree number. INIT ALOW DENY Allow or deny digit strings not in tree. ALOW xxxx xxxx y...y Digit sequence to be allowed unconditionally. Digit sequence to be conditionally allowed and maximum number of digits that can follow. UPDT (YES), NO Data is correct and NFCR tree can be updated. DENY xxxx xxxx y...y Digit sequence to be denied unconditionally. Digit sequence to be conditionally denied and maximum number of digits that can follow. UPDT (YES) NO Data is correct and NFCR tree can be updated
Colin
More info..
Call Restriction (Barring)
Feature Description
Introduction
The Meridian 1 has comprehensive call barring and restriction facilities which can be implemented in several ways:-
Restriction to Outgoing Routes
Using this process an extension user can be barred from using particular routes out of the system.
Each outgoing route can be assigned to up to 32 TARGs (Trunk Access Restriction Groups) which are simply numbers between 0 and 31. Each extension also has a data item called TGAR (Trunk Group Access Restriction) to which only one number, between 0 and 31, may be defined. The extension user is denied from using the route when the TGAR of that extension matches one of the TARGs of the route.
Restriction by Class of Service
Another method of barring calls is by applying one of seven alternatives in the extension's Class of Service
The seven Class of Service types are:-
UNR - Unrestricted The extension user can dial anywhere they want - literally without restriction.
FRE - Fully Restricted No exchange line access. The extension user can make internal calls, can use privately wired (Tie) lines, however they can have calls using exchange lines transferred to them from another extension user.
FR1 - Fully Restricted 1 Same as FRE, but calls using exchange lines cannot be transferred to them.
FR2 - Fully Restricted 2 This restricts the extension to internal calls only.
SRE - Semi-restricted Allowed outgoing external calls via the attendant console only. Can receive external incoming calls.
TLD - Toll Denied Allowed outgoing calls to certain destinations only. The Meridian 1 monitors the digits that are dialled to determine if the call is to be allowed. This process is called New Flexible Code Restriction.
CTD - Conditionally Toll Like TLD, CTD checks the digits dialled, however CTD Denied only applies when a PSTN route is chosen as an alternative to a private network call.
New Flexible Code Restriction
Each individual extension, that has a Class of Service of TLD, will have a NCOS - Network Class of Service defined. The value assigned to NCOS will ultimately identify a call barring table (TREE), that contain the numbers that are permitted or denied from being dialled. Up to 8 trees can be defined on Meridian 1 and these are identified by NCOS 0 to 7.
Note, the example below simplifies the NCOS to TREE relationship. In reality the relationship may not be linear (ie) 1-1, 2-2 etc.
Feature Implementation
The type of call restriction applied to an extension is configured in the Class of Service using Program 10 (analogue sets) or 11(digital sets). These programs are also used to define the extent of the restriction using the TGAR and NCOS prompts as appropriate.
Example
This example shows three different extensions being set up for the following call restriction:-
TN 9 1 Totally Unrestricted
TN 8 4 Restricted from gaining access to any route with a TARG of 3
TN 7 4 Restricted from dialling international numbers and 0898 numbers as detailed in default TREE 3.
LD 10
Load Program 10.
REQ CHG
TYPE 500
TN 9 1
ECHG YES Easy Change
ITEM TGAR 0 No Trunk Group Access Restriction is applied.
ITEM Carriage return back to the REQ prompt
LD 11
Load Program 11.
REQ CHG
TYPE 2616
ECHG YES
ITEM CLS UNR Class of Service set to unrestricted.
ITEM TGAR 3 Restrict this extension from accessing any route with a TARG of 3.
ITEM Carriage return back to the REQ prompt
LD 11
Load Program 11.
REQ CHG
TYPE 2008
TN 7 4
ECHG YES Easy change
ITEM CLS TLD Toll Denied causes the system to look at the NCOS value for this extension.
ITEM NCOS 3 NCOS 3 causes Code Restriction Tree 3 to be applied to this extension.
ITEM TGAR 0 No trunk group Access Restriction is applied.
ITEM Carriage return back to the REQ prompt
Colin
Call Restriction (Barring)
Feature Description
Introduction
The Meridian 1 has comprehensive call barring and restriction facilities which can be implemented in several ways:-
Restriction to Outgoing Routes
Using this process an extension user can be barred from using particular routes out of the system.
Each outgoing route can be assigned to up to 32 TARGs (Trunk Access Restriction Groups) which are simply numbers between 0 and 31. Each extension also has a data item called TGAR (Trunk Group Access Restriction) to which only one number, between 0 and 31, may be defined. The extension user is denied from using the route when the TGAR of that extension matches one of the TARGs of the route.
Restriction by Class of Service
Another method of barring calls is by applying one of seven alternatives in the extension's Class of Service
The seven Class of Service types are:-
UNR - Unrestricted The extension user can dial anywhere they want - literally without restriction.
FRE - Fully Restricted No exchange line access. The extension user can make internal calls, can use privately wired (Tie) lines, however they can have calls using exchange lines transferred to them from another extension user.
FR1 - Fully Restricted 1 Same as FRE, but calls using exchange lines cannot be transferred to them.
FR2 - Fully Restricted 2 This restricts the extension to internal calls only.
SRE - Semi-restricted Allowed outgoing external calls via the attendant console only. Can receive external incoming calls.
TLD - Toll Denied Allowed outgoing calls to certain destinations only. The Meridian 1 monitors the digits that are dialled to determine if the call is to be allowed. This process is called New Flexible Code Restriction.
CTD - Conditionally Toll Like TLD, CTD checks the digits dialled, however CTD Denied only applies when a PSTN route is chosen as an alternative to a private network call.
New Flexible Code Restriction
Each individual extension, that has a Class of Service of TLD, will have a NCOS - Network Class of Service defined. The value assigned to NCOS will ultimately identify a call barring table (TREE), that contain the numbers that are permitted or denied from being dialled. Up to 8 trees can be defined on Meridian 1 and these are identified by NCOS 0 to 7.
Note, the example below simplifies the NCOS to TREE relationship. In reality the relationship may not be linear (ie) 1-1, 2-2 etc.
Feature Implementation
The type of call restriction applied to an extension is configured in the Class of Service using Program 10 (analogue sets) or 11(digital sets). These programs are also used to define the extent of the restriction using the TGAR and NCOS prompts as appropriate.
Example
This example shows three different extensions being set up for the following call restriction:-
TN 9 1 Totally Unrestricted
TN 8 4 Restricted from gaining access to any route with a TARG of 3
TN 7 4 Restricted from dialling international numbers and 0898 numbers as detailed in default TREE 3.
LD 10
Load Program 10.
REQ CHG
TYPE 500
TN 9 1
ECHG YES Easy Change
ITEM TGAR 0 No Trunk Group Access Restriction is applied.
ITEM Carriage return back to the REQ prompt
LD 11
Load Program 11.
REQ CHG
TYPE 2616
ECHG YES
ITEM CLS UNR Class of Service set to unrestricted.
ITEM TGAR 3 Restrict this extension from accessing any route with a TARG of 3.
ITEM Carriage return back to the REQ prompt
LD 11
Load Program 11.
REQ CHG
TYPE 2008
TN 7 4
ECHG YES Easy change
ITEM CLS TLD Toll Denied causes the system to look at the NCOS value for this extension.
ITEM NCOS 3 NCOS 3 causes Code Restriction Tree 3 to be applied to this extension.
ITEM TGAR 0 No trunk group Access Restriction is applied.
ITEM Carriage return back to the REQ prompt
Colin
-
1
- #4
The easiest way if to use FRL feature- not common in the UK
If you have set CLS UNR are all your extensions allowed to make all calls?
1. list out all the NCOS values for each extension they should all the same say 1 . except TN 10 x ( Voice mail ) they will probably be set to 7
2. Check the NCOS-FRL settings LD 86, REQ PRT, TYPE ESN
Make sure they are all set to FRL-NCOS 1 1
FRL-NCOS 2-2
All the way to FRL-NCOS 7 7- to do this just req chg until you get to FRL-NOCS enter 1 space 1 , 2 ect 2 etc at each prompt
3. Create a SPN of the premium rate number and point it to a RLI. At each entry within the RLI set the FRL to be 2 -3 higher then the NCOS values in LD 81 but at least one below FRL 7- this allows you at a late rdate to allow oterhs access to the prenium rate umber.
4. Test- Make a call on your extension as long as your NCOS is the same as everyones else`s if not change it for the test. you should be barred as your NCOS/FRL is less then teh rli, if it was equal to or higher then you are allowed out. This set up is commom in US and Japen. It works the same way as in Mitels, SX2000 where you barred individual PSTN numbers on the actual route rather then the number if that makes sense
wayne
If you have set CLS UNR are all your extensions allowed to make all calls?
1. list out all the NCOS values for each extension they should all the same say 1 . except TN 10 x ( Voice mail ) they will probably be set to 7
2. Check the NCOS-FRL settings LD 86, REQ PRT, TYPE ESN
Make sure they are all set to FRL-NCOS 1 1
FRL-NCOS 2-2
All the way to FRL-NCOS 7 7- to do this just req chg until you get to FRL-NOCS enter 1 space 1 , 2 ect 2 etc at each prompt
3. Create a SPN of the premium rate number and point it to a RLI. At each entry within the RLI set the FRL to be 2 -3 higher then the NCOS values in LD 81 but at least one below FRL 7- this allows you at a late rdate to allow oterhs access to the prenium rate umber.
4. Test- Make a call on your extension as long as your NCOS is the same as everyones else`s if not change it for the test. you should be barred as your NCOS/FRL is less then teh rli, if it was equal to or higher then you are allowed out. This set up is commom in US and Japen. It works the same way as in Mitels, SX2000 where you barred individual PSTN numbers on the actual route rather then the number if that makes sense
wayne
- Thread starter
- #5
- Status
Similar threads
- Locked
- Question
- Locked
- Question