 |
|
|
|
7.1.2 |
Routing Tables |
| Implementing features, see also Manager E Routing Tables |
Definition |
| The routing tables evaluate the digits dialed by the user and determine the station number that the system should dial. In the process, the digits are modified as necessary. This modification can mean that digits are repeated, suppressed, added, or reordered. It is also possible to add a dial pause and change the signaling method. A distinction is made between the following types of routing tables: |
| • | Dialing rules table: This table determines how the digits dialed by the user will be converted and dialed by the system. The following special characters can be defined: |
| A: Repeat remaining fields (transmit). This letter causes all subsequent digit fields to be transmitted. The point of reference is the last field pointer before "A". The combination E1A is permitted only at the beginning of a string. |
| D (n): Dial digit sequence (1 to 25 digits). This letter can be inserted multiple times and at any position in the string. |
| E (n): Repeat field from dial plan (from 1 to 10 times). This letter can be inserted multiple times and at any position in the string. "E" can also appear in any order with relation to (n). A specific field can be addressed multiple times, including in sequence. With the exception of "E1", this letter can be surrounded by any parameter. |
| P (n): Pause (1 to 60 times the system-wide pause unit). This letter can be inserted multiple times and at any position in the string. |
| M (n): Authorization code (1 to 16). This letter must not be in the final position. |
| S: Switch, changes signaling methods from DP to DTMF (with CONNECT, PROGRESS or CALL PROC with PI). This letter can be inserted in the string only once and may not be in the final position. The "C" parameter cannot be used after "S". |
| U: Use subaddress signaling method. This letter can be inserted in the string only once and may not be in the final position. The subsequent characters are again selected in INFO. The "S", "P", and "C" parameters cannot be used after "U". |
| C: Access code. This letter can be inserted in the string only once. The subsequent characters are transmitted without a dial pause and are used for single stage, two-stage, DICS (not for U.S.), BRI, and PRI carrier access. |
| • | Authorization code: The authorization code is divided into the carrier ID and customer ID. The carrier ID is entered as one entry in the authorization code table. The customer ID is entered as another entry in the authorization code table. The authorization code entry in the outdial rule then consists of the two authorization codes. Only a "protected" authorization code is supported (represented by "*****"). |
| • | Class of service: Each station is assigned a class of service (COS). A station can then seize a route only if its COS is greater than or equal to the COS in the route table; for example, a station with a COS 7 cannot seize a route with COS 8. |
| • | Schedule: Up to eight time zones per day can be configured for each day of the week to control LCR. A search is performed based on the schedule ID entered in the route table to determine whether the current time matches the value entered in the schedule. If it does and if the correct class of service is present, dialing is performed as per the outdial rule entered in the route table. |
| • | Route table: Up to 254 route tables with 16 routes each can be created. Each route in a route table is described by a combination of the trunk group, outdial rule, toll restriction, schedule, and an option for warning against a more expensive route. The table is scanned from top to bottom. The system checks to determine whether the trunk group is free and the station has the requisite class of service. If so, the system dials per the outdial rule and schedule entered in the route table. Depending on the entry in the route table, a warning can be issued to the station informing the user that the call is being routed. This warning can be signaled by a warning tone and a display message. The display shows the outdial rule name. |
| • | Dial plan: Each station number dialed for external traffic is checked against the dial plan for up to 30 positions (including field separator and trunk group code). If the number dialed matches an entry in the dial plan, LCR is handled in accordance with the route table in the dial plan. |
| To use all available features (such as callback) in conjunction with LCR, the trunk group code must be separated from the dialed station number by a dash (-) in the dial plan (sample dial plan entry: 0-CZ). |
|
| The following station number entries are valid: |
| 0...9: Allowed digits |
| -: Field separator |
| X: A search is performed based on the schedule ID entered in the route table to determine whether the current time matches the value entered in the schedule. |
| N: Any digit from 2 to 9 |
| Z: One or more digits to follow up to the end of dialing |
| C: Simulated dial tone (can be entered up to three times) |
| To block outgoing external calls, enter a dash (-) in the Routing table field of the dial plan. |
| Example: |
| |
| Do not confuse the hyphen (-) in the "Dialed digits" field, which separates the digit blocks in the number, with the dash in the "Route table" field which blocks the numbers. |
|
| Figure 7-1 | Sample LCR Flow Diagram (not for U.S.)
|
| The dialed call number is used as the criterion for the connection route to be used. The system can evaluate up to 24 digits of the digit sequence plus up to 9 field separators. The digit sequence that can be dialed can consist of up to 32 digits. The evaluation can be carried out both destination dependently and time dependently and in dependence on the station's LCR class of service (COS). |
| The system contains 254 route tables with 16 routes each. The LCR class-of-service is evaluated hierarchically for LCR. |
| The outdial rule is described in the HiPath 3000/5000 Manager E by its name, which consists of not more than 16 characters, and in the System Administration by its index. |
| The station can cancel automatic selection by seizing a line directly (Carrier Select Override - CSO). The LCR class-of-service cannot be transferred between CorNet-N networked systems. |
| General Operating Principle |
| The system analyzes the number dialed to determine if the digits entered are valid. If the digits are recognized, a reference route table is scanned for route group choices. Once the Route group is selected, the availability of the route is checked against the time schedule. If the Route group is available, the LCR COS requirement assigned to the route group is compared to the LCR COS associated with the dialing device. If the LCR COS associated with the dialing station is equal to or greater than the route group COS, the Toll Restriction tables are checked for additional screening information. This process is repeated for every call using the system LCR application. |
|
| Figure 7-2 | General LCR Flow
|
| • | A system-wide flag activates LCR via Manager T or HiPath 3000/5000 Manager E. |
| • | When LCR is activated, the check is performed for every trunk seizure (except when dialing a trunk code). |
| • | If all the least expensive connection routes have been seized, LCR automatically switches to defined more expensive routes. The user can be signaled of this fact both visually and acoustically. |
| • | In the case of outgoing calls on the ISDN network, the dialed number continues to be displayed until the destination number information on the other party is received. |
| • | Digits can be transmitted either individually or en-bloc, depending on the access method and the dial plan. |
| • | Once an account code is entered, it applies to the entire connection setup. |
| • | The allowed and denied lists are also used for LCR. The toll restriction check then refers to the digits dialed on the station without the trunk group code. |
Model-Specific Data |
Dependencies/Restrictions |
|
| HiPath 3000/5000 V8, Feature Description, Issue 10 | up  |
|
|
||
| Disclaimer & Copyright | ID: P31003H3580F100017618 | 2011-02-07 |