How do Classes Of Restriction Work?
Product Area:
SX2000 All
Product Release: All
Topic:
Class Of Restriction \\ Restr. Groups \\ Restr. Numbers Last Update:
Document Number:
Circulation:
Public – Faxable
Overview:
This document provides information about how callers are restricted from using specific Routes. It illustrates graphically how a call flows through the checking process to determine if a caller can make a particular call.
Summary:
Callers and trunks are restricted from using specific routes by Class Of Restriction Numbers and Class Of Restriction Groups. COR Numbers are assigned to Stations in Station Service Assignment and Trunks in Trunk Service Assignment. COR Groups contain COR Numbers and are assigned to Routes. COR Numbers are used by trunks on Incoming Trunk Calls only when the call tandems across the SX2000 and attempts to use ARS to exit the switch again.
Description:
Here is a sample of how we assign CORs and COR Groups in the SX2000.
Select particular COR NUMBERS for particular types of phones, eg. toll block, normal customer.
A COR number is assigned to a station in Station Service Assignment.
A COR can also be assigned on a Trunk in the Trunk Service
Assignment view for use by incoming trunk
Calls. The COR Number used by an Incoming Trunk follows the call as it progresses through the switch and the call proceeds through the restricting process just like a station.
COR Numbers are placed into COR Groups to be used to restrict devices (sets, trunks) from particular Routes.
COR Numbers must be entered in COR Groups in ascending order.
COR Numbers used by trunks must not be used by any stations.
A COR Group can be assigned to one or more Routes. The COR Group is used to restrict stations or Incoming Trunk calls from using its’ outgoing Route.
Simple COR Example:
Route 1 might use COR Group 1. COR Group 1 might restrict any station or incoming trunk that has
COR Number 2, 4, 9, 12, or 16 from using Route 1.
Nested COR Example
ARS can also take a call through a Route List when Restricting (filtering) is desired.
Here is a chart of how a 1+ call might proceed using these restrictions (this may not be how your system is programmed):
Station (COR Number 2) dials 9 1 613 592 2122
ARS for 9 1 613 592 2122 picks Route List 1
|
-->Route List 1 has 3 members
|
|
-->Route 1
| |
| -->COR Group 1 (restricts COR # 2, 4, 9, 12, 16)
|
-->Route 8
| |
| --> COR Group 8 (restricts COR # 1, 3-9, 12-13, 16)
|
-->Route 21
|
--> COR Group 16 (restricts COR # 1-15, 17-64)
You can see COR Number 2 DOES show up in COR Group 1 and 16, but DOES NOT appear in COR Group 8. As a result, the station CANNOT USE Route 1 and 21, but CAN USE Route 8. Note that COR Groups 8 and 16 have restriction RANGES (eg. 3-9, 12-13, 1-15, 17-64). These are valid entries in the COR Groups to restrict a range of COR Numbers.
If the trunk group that is used in Route 8 is busy, the person making the call will get reorder tone because there are no
other Routes that will accept his call. If all three Routes contained COR Groups that included COR Number 2, the call would
not be allowed to proceed out to the telephone network. Normal Intercept Handling applies, and depending on the intercept may be sent to a tone or directory number.