3Com NBX 100 Administrator's Manual page 83

Table Create 1 Internal 4 Digit Extensions
/
/
TableEntry Create
TableEntry Create
/
/
DestinationRoute Create
DestinationRoute Create
/
/
DestinationRouteEntry Create
DestinationRouteEntry Create
/
/
DestinationRouteOperation Create
DestinationRouteOperation Create
Figure 10 Sample Dial Plan Entries for Chicago Using Site-Unique Extensions
Id Entry Digits
-- ----- ----------- --- --- -------------
1 3 2
1 4 3
Route Description
----- -----------
522 Atlanta VTL Connection
523 Dallas VTL Connection
Route Entry DestinationExtension
----- ----- --------------------
522
523
Route Entry OperId Operation
----- ----- ------ ---------
522
523
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
How to Configure a Virtual Tie Line
Min Max Class
4 4 WAN
4 4 WAN
1 *0006
1 *0006
1 1 prepend
1 1 prepend
Prio Route
---- -----
0 522
0 523
Value
-----
192*168*25*100*
192*168*35*100*
83