7.2.13  
LCR Dial Plan 
 
In the case of external calls, the system checks each number dialed up to a total of 25 digits, including field separators and trunk-group access codes. The dial-plan entry is associated with a route group for the destination number and the system assigns this route to the station for setting up the connection.
The dial plan may be separated into unique fields for identification and configuration purposes using the dial rules. The table shows the numbers 4922000 and 14084922000 entered in the dial-plan table.

 Field 1  
   
 Field 2  
   
 Field 3  
   
 Field 4  
   
 Field 5  
 9  
 C  
 492  
 -  
 2000  
   
   
   
   
 9  
 C  
 1  
 -  
 408  
 -  
 492  
 -  
 2000  
 62659321  
Reset boards and port assignments stored in the system.  
 
 
 
 
 
 
 
The following station number entries are valid:
 •   0 . . . 9
Allowed digits  
 •   -
Field separator (maximum of 10 fields per dial-plan entry)  
 •   C
Simulated dial tone (can be entered up to three times). This entry is also interpreted as a field separator.  
 •   X
Any digit from 0 to . . 9  
 •   N
Any digit from 2 to . . 9  
 •   Z
One or more digits follow before end of dialing  
 •   C
Simulated dial tone (can be entered up to three times)  
 
Notes: The character # within a dial string means end of dialing or signaling method changeover. That is why "*" and "#" are invalid entries. Dial rules may be used to insert the * and # in the dial string to the public network.  
Do not confuse the hyphen (-) in the destination field, which functions as a field separator, with the dash in the "Route table" field, which blocks the numbers (see Table 7-1).  
If "automatic line seizure" (Prime Line) is activated to the CO, Least Cost Routing (LCR) is not possible. These two features are mutually exclusive.
For the LCR dial plan to accurately select the route group, the dial-plan entries must be entered as follows.
Entries should be placed in ascending numeric order from 0 to 9. Specific dialed numbers must precede wildcard entries to prevent conflicts in matches with wildcard entries. Table 7-1 is an example of the suggested entry order.

 Table 7-1   Sample Entries in a Dial Plan Table
 Entry No.  
 Dialed Digits
(code + station no.)  
 Route table  
 1  
9C0Z  
 1  
 2  
9C011Z  
   
 3  
9C492-5001  
 1  
 4  
9CNXX-XXXX  
 1  
 5  
9C1-NXX-XXX-XXXX  
 1  
 6  
9C1-900-XXX-XXX  
  -1  
 7  
9C1-976-123-3456  
   -2  
 ...  
 
   
 254  
 
   
1In this example, the dash (-) blocks all 900 numbers from being dialed.
2In this example, the dash (-) blocks only the specific number (976-123-3456) from being dialed.
The fields formed by the field separators "-" and "C" in the dial plan can be addressed selectively to repeat, suppress, exchange, or insert digits.

7.2.13.1  
Rules for Creating LCR Dial Plan Entries 
 •   The first field should contain only a programmed trunk group access code. It must not contain any wildcards.
 •   The wildcards N and X can occur more than once in any field except the first field.
 •   The wildcard Z can occur only in the last field. It represents an undetermined number of suffix digits.
 •   A digit sequence can be divided into a maximum of 10 fields.

HiPath 3000/5000 V8, Feature Description, Issue 10   up Top
Disclaimer & Copyright   ID: P31003H3580F100017618   2011-02-07