3Com NBX 100 Administrator's Manual page 84

84 C 2: D
HAPTER IAL
Table Create 1 Internal 4 Digit Extensions
/
/
TableEntry Create
TableEntry Create
/
/
DestinationRoute Create
DestinationRoute Create
/
/
DestinationRouteEntry Create
DestinationRouteEntry Create
/
/
DestinationRouteOperation Create
DestinationRouteOperation Create
DestinationRouteOperation Create
DestinationRouteOperation Create
P
LAN
for Dallas, the IP address is 192.168.35.100. You must use the asterisk (*)
character to separate fields within the IP address and to separate the IP
address from the destination extension.
Example: Dial Plan with Site Codes
In Figure 9, each of the three sites uses the same extension range. In the
Internal table in the Chicago system dial plan, the entries shown in
Figure 11 select route 522 and 523 if a user dials the site codes 62 and 63
respectively, and then dials an extension. The dial plans for the Atlanta
and Dallas NBX systems would contain similar, but not identical entries.
An explanation of each line in the dial plan follows
Figure 11 Sample Dial Plan Entries for Chicago Using Site Codes
Id Entry Digits
-- ----- ----------- --- --- -------------
1 100 62
1 101 63
Route Description
----- -----------
522 Atlanta VTL Connection
523 Dallas VTL Connection
Route Entry DestinationExtension
----- ----- --------------------
522
523
Route Entry OperId Operation
----- ----- ------ ---------
The first TableEntry Create command creates entry 100 in Table 1. This
assumes that the highest previous entry in Table 1 was 99 or lower. Entry
100 watches for the 2-digit sequence 62 followed by a 4-digit extension
and specifies route 522 whenever a user dials such a 6-digit (Min = 6 and
Min Max Class
6 6 WAN
6 6 WAN
1 *0006
1 *0006
522 1 1 stripLead
522 1 2 prepend
523 1 1 stripLead
523 1 2 prepend
Figure 11.
Prio Route
---- -----
0 522
0 523
Value
-----
2
192*168*25*100*
2
192*168*35*100*