LEAST COST ROUTING - 3/6 DIGIT
•Route Pattern Table - Up to 256 Route Advance tables are available, each with 4 entries. If more than 4 entries are required, up to 8 entries can be provided by combining two route pattern tables.
•LCR Pattern Table - Up to 256 tables are available for assignment of digits to be added or deleted. Also, the office code dialed can be checked to determine whether service is available for a specific office code, and whether a prefix 1 should be added. This table can be used in conjunction with toll restriction assignment for combined LCR/toll restriction capability. Refer to the Code Restriction Features and Specifications.
•Tenant Pattern Table - Up to 16 tables are used to select a route pattern table. The programmer can make the system select a route pattern table based on which tenant the caller is associated. This allows sharing of LCR and toll restriction capability among multiple tenants, while providing for the individual needs of each tenant. Each of the 64 tables can be assigned a route pattern table for each of the 64 tenants.
In addition, the special Digit Code Table is used for assigning the same digits as leading one, two or three digits of area code assigned to the Digit Code Tables above (e.g. 00XX.....X: International Call, 0: Operator Call, 0XXX:Toll Operator Call use the special Digit Code Table). The system examines the special Digit Code Table when an ORT timeout has occurred after dialing leading digits.
•Date Pattern Table - Up to 4
•Time Pattern Table - Up to 8
•Office Code Pattern Tables - Up to 50 tables contain office codes to be checked to see if a prefix digit 1 must be added, and to see if the office code dialed is allowed or denied for a specific trunk route (Ser- vice area check).
•Digit Addition Pattern Table - Up to 256 tables are available for assigning digit addition pattern. Up to 32 digits, including pauses, can be added.
5.Assignment of LCR is on an access code basis. All trunk access codes can be assigned for LCR. Up to 3 different LCR access codes can be assigned, per numbering plan, providing flexibility in choosing routes by access code. When LCR is implemented, all stations within the system are subject to the LCR process.
6.To provide a group of stations access to trunks that are not subject to LCR, the associated trunk routes should be given different access codes (not assigned to LCR). Other stations can be restricted from access to these trunk routes.
7.Direct trunk appearances on Multiline Terminals are not subject to the LCR process.
8.If the system is designated as KF registration, this feature is not available.
9.The following flow charts describe LCR system operation.
| NEAX2000 IVS2 |
Page 202 | Business/Hotel/Data Features and Specifications |
