3Com SuperStack 3 NBX - Page 111

Using a VTL Password 111
If you use unique extension ranges at each site, and therefore do not dial
a site code when placing VTL calls to users at those sites, you can still use
codes to access VTL connections that permit hop-off at the far end.
Figure 43
shows how to configure VTL passwords in a dial plan, using site
codes that permit hop-off and other site codes that do not. Each entry is
explained following the figure.
Figure 43 Dial Plan Entries for VTL Passwords
Table Create 1 Internal 4 Digit Extensions
/ Id Entry Digits Min Max Class Prio Route
/ -- ----- ----------- --- --- ------------- ---- -----
TableEntry Create 1 100 62 6 6 WAN 0 522
TableEntry Create 1 101 63 6 6 WAN 0 523
TableEntry Create 1 102 72 6 32 WAN 0 524
TableEntry Create 1 103 73 6 32 WAN 0 525
/ Route Description
/ ----- -----------
DestinationRoute Create 522 Atlanta VTL Connection
DestinationRoute Create 523 Dallas VTL Connection
DestinationRoute Create 524 Atlanta VTL Connection with password
DestinationRoute Create 525 Dallas VTL Connection with password
/ Route Entry DestinationExtension
/ ----- ----- --------------------
DestinationRouteEntry Create 522 1 *0006
DestinationRouteEntry Create 523 1 *0006
DestinationRouteEntry Create 524 1 *0006
DestinationRouteEntry Create 525 1 *0006
/ Route Entry OperId Operation Value
/ ----- ----- ------ --------- -----
DestinationRouteOperation Create 522 1 1 stripLead 2
DestinationRouteOperation Create 522 1 2 prepend 192*168*25*100*
DestinationRouteOperation Create 523 1 1 stripLead 2
DestinationRouteOperation Create 523 1 2 prepend 192*168*35*100*
DestinationRouteOperation Create 524 1 1 stripLead 2
DestinationRouteOperation Create 524 1 2 prepend192*168*25*100*ATLPassW*
DestinationRouteOperation Create 525 1 1 stripLead 2
DestinationRouteOperation Create 525 1 2 prepend 92*168*35*100*DALPWord*