Route - 3Com SuperStack 3 NBX Administrator's Manual

94 C 2: D P
HAPTER IAL LAN
The first TableEntry Create command modifies entry 3 in Table 1. Entry 3
watches for 4-digit sequences (Min = 4, Max = 4) beginning with 2
(extensions 2000 through 2999) and specifies route 522 whenever a
4-digit sequence falls within this range. Entry 4 watches for 4-digit
sequences (Min = 4, Max = 4) beginning with 3 (extension 3000 through
3999) and specifies route 523 whenever a 4-digit sequence falls within
this range. Route numbers 522 and 523 are examples only. The choice of
route numbers is made by the person who configures the dial plans for
the sites.
Two DestinationRoute Create commands create routes 522 and 523. The
Description field contains any text you want to use to describe each

route.

Two DestinationRouteEntry Create commands specify the extension list
for routes 522 and 523. Extension list *0006 is reserved for VTLs.
Two DestinationRouteOperation Create commands prepend the IP
Address of the destination NBX system to the extension that the user
dialed. In this example, the IP address for Atlanta is 192.169.25.100 and
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 29, 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 31 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 31.