3Com Nbx 100 And Ss3 Nbx Administration Guide

							Using a VTL Password111
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* 
						

							112CHAPTER 2: DIAL PLAN
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 
Max = 6) sequence. Entry 101 watches for the 2-digit sequence 63 
followed by a 4-digit extension and specifies route 523 whenever a user 
dials such a 6-digit sequence. The choice of route numbers is made by the 
person configuring the dial plans for the sites.
The next two TableEntry Create commands are set up in a similar manner 
to handle VTL connections with passwords. If a user dials 72 followed by 
a 4-digit extension, the VTL call uses route 524. If a user dials 73 followed 
by a 4-digit extension, the VTL call uses route 525. These two commands 
specify a minimum of 6 digits (for example, if the caller is calling an 
internal extension preceded by the site code) and a maximum of 32 digits 
(for example if the caller is calling a long-distance or international number 
preceded by the site code).
The first two DestinationRoute Create commands create routes 522 and 
523. The Description field contains any text you want to use to describe 
each route.
The second two DestinationRoute Create commands create routes 524 
and 525, the routes that are used with a VTL password.
The four DestinationRouteEntry Create commands specify the extension 
list for routes 522, 523, 524, and 525. Extension list *0006 is the default 
extension list for VTLs.
For the first two DestinationRoutes, two DestinationRouteOperation 
Create commands perform two functions:
■The stripLead command removes the two digits (62 or 63) leaving the 
4-digit extension the user dialed.
■The prepend command adds 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. In the dial plan, you must use an asterisk (*) instead 
of a period (.) to separate the fields within the IP address, and to 
separate the IP address from the destination extension. 
						

							Using a VTL Password113
For the second two DestinationRoutes, two DestinationRouteOperation 
Create commands perform two similar functions.
■The stripLead command removes the two digits (72 or 73) leaving the 
4-digit extension the user dialed.
■The prepend command adds the IP Address of the destination NBX 
system and the password of that system to the extension that the user 
dialed. In this example, the IP address for Atlanta is 192.169.25.100 
and the password is ATLPassW. For Dallas, the IP address is 
192.168.35.100 and the password is DALPWord. In the dial plan, you 
must use an asterisk (*) instead of a period (.) to separate the fields 
within the IP address, and to separate the IP address from the 
destination extension.
To place a hop-off call to 555-1212 in area code 903 through the Atlanta 
system, a user on a remote system would dial 72919035551212. The 72 
code sets up a VTL connection to Atlanta that incudes the Atlanta 
system’s VTL password, and the remaining digits are used to dial the 
number (9 accesses an outside line to obtain dial tone from the local 
carrier, 1 accesses the long-distance carrier, and the remaining digits 
specify the long-distance number).
If the same user used site code 62 to place a call to the Atlanta office, 
only toll-free, emergency, and internal call would be allowed.
Toll Calls Without a
VTL PasswordIf a local user has configured his telephone to forward calls to a 
long-distance number, then an incoming VTL call to that telephone does 
not need to supply the local system’s VTL password in order for the call to 
be forwarded.
Music On HoldIf two users are talking on a VTL connection, and the first user places the 
call on hold, the second user hears Music On Hold only if his local system 
is configured to play it. 
						

							114CHAPTER 2: DIAL PLAN
Troubleshooting VTL
CallsTa b l e 2 1 contains a list of error situations, the possible causes and the 
action to take in each case.
Table 21   VTL Errors and Corrections
Error ConditionPossible CausesActions
Long pause after dialing. Telephone display contains 
“VTL” during the pause. Busy signal is then heard.Remote server does not 
respondTest the connection to the 
remote system using the 
Query Remote function.
After you finish dialing a VTL call, you get a busy 
signal and the message “All ports busy” appears in 
the telephone display panel.1. No VTL license installed.
2. VTL device extensions not 
added to Extension List 
*0006.
3. All local VTL connections 
are currently in use.
4. All VTL connections at the 
remote site are currently in 
use.1. Verify that the licenses 
appear when you access the 
tab.
2. Verify that the *0006 
extension contains the VTL 
device extensions.
3. On the Virtual Tie Line tab, 
verify that there is at least one 
idle VTL connection.
4. Use the Query Remote 
function to verify that there is 
at least one idle VTL 
connection.
After you finish dialing a VTL call, you get a busy 
signal and the message “Invalid Number” appears in 
the telephone display panel.1. Local dial plan is not 
properly configured.
2. Dial plan on the remote 
(target) system in not properly 
configured.
3. You are trying to use 
hop-off without the necessary 
password.1. Examine the local dial plan 
for errors.
2. Examine the dial plan on 
the remote system for errors.
3.Verify that the password for 
the remote system is used in 
both dial plans.
No audio1. Telephones are not 
configured to use either IP 
On-the-Fly or Standard IP.
2. VTL Audio compression is 
supported on only one of the 
two NBX systems.1. Verify that the IP setting in 
the System Settings, 
System-wide dialog box is “IP 
On-the-Fly” or “Standard IP.” 
Install a license and change 
the setting, if necessary.
2. Verify that audio 
compression is enabled on 
both systems.
Caller ID information does not appear correctly in 
the telephone display panel.1. Invalid local pretranslator.
2. VTL extensions are not in 
the VTL pretranslator “Devices 
Using” table.1. Examine the local dial plan 
for pretranslator errors.
2. Verify that VTL extensions 
appear in the left-hand table 
for the pretranslator. 
						

							Dial Plan Configuration File Commands115
Dial Plan 
Configuration File 
CommandsThis section provides the syntax and description of each command used 
to create the information in the dial plan configuration file. In addition, 
Ta b l e 2 2
 categorizes and summarizes all the dial plan commands.
The Alphabetical List of Dial Plan Commands provides a detailed 
description and syntax of each command. See “Dial Plan Command 
Format” for a description of each component of dial plan commands.
To see how these commands are implemented in a dial plan, see “Sample 
Solutions Using Dial Plan Configuration File Commands” later in this 
chapter. You can also open and examine any of the dial plans shipped 
with your NBX system.
Dial Plan Command
SummaryTa b l e 2 2
 provides a brief summary the dial plan commands. These 
commands are listed and categorized in the order that they might 
logically appear in a working dial plan.
See “List of Dial Plan Commands”
 for a complete list and description of 
each dial plan command, including syntax and arguments.
Command syntax is case insensitive. In the sample dial plans (supplied 
with the system), and in this section, commands use upper and lower 
case to make them easier to read.
An entry that begins with “n” for example, nDialPlanID, indicates an 
integer field. Integer IDs are used in many places, and must be within 
the range 1 through 32768. The system reserves dial plan table ID 
numbers 1, 2, and 3 for Internal, Incoming, and Least Cost Routing, 
respectively.
An entry that begins with “sz” (for example, szDescription) indicates a 
field composed of alphanumeric characters. Acceptable characters are 
a through z, A through Z, and 0 through 9.
Each line in the configuration file must contain a complete command. 
The NBX system reads all lines in the configuration file, and ignores only 
those lines containing one or more syntax errors. The system treats any 
line beginning with / (forward slash) as a comment and ignores it.
CAUTION: Do not place comments at the end of a command line. 
						

							116CHAPTER 2: DIAL PLAN
Table 22   Dial Plan Command Summary
Command NameDescription
Ta b l e  C r e a t eCreates a dial plan table.
TableEntry CreateCreates an entry in a dial plan table.
DestinationRoute CreateCreates a route that specifies the primary and 
alternative destination device of a call.
DestinationRouteEntry CreateCreates a destination route entry that 
identifies a single destination device or device 
list.
DestinationRouteOperation CreateCreates a digit manipulation operation for a 
destination route entry.
TimedRoute CreateCreates a timed route (a route that the system 
uses based on defined criteria for time of day 
and day of week).
TimedRouteEntry CreateCreates a timed route entry specifying either a 
time of day or system mode, day of the week 
criteria, and the destination route to use if 
that criteria are met.
TimedRouteOperation CreateCreates a digit manipulation operation for a 
timed route entry.
PreTranslator CreateCreates a pretranslator entry and specifies a 
string of digits that are compared to the 
incoming digits.
PreTranslatorEntry CreateCreates a pretranslator entry and specifies a 
string of digits that are compared to the 
incoming digits.
PreTranslatorEntry DeleteDeletes a pretranslator entry or deletes all 
entries for a particular pretranslator.
PreTranslatorOperation CreateCreates a digit manipulation operation for a 
pretranslator entry.
ExtensionLengthSpecifies the length of extension numbers for 
system devices.
ExtensionRangeSpecifies a range of extensions for each type 
of device.
ExternalSettingsSpecifies settings for several aspects of 
external devices. 
						

							Dial Plan Configuration File Commands117
List of Dial Plan
CommandsThe dial plan commands are described in this section. They are listed in 
alphabetical order:
■DestinationRoute Create
■DestinationRouteEntry Create
■DestinationRouteOperation Create
■ExtensionLength
■ExtensionRange
■ExternalSettings
■PreTranslator Create
■PreTranslatorEntry Create
■PreTranslatorEntry Delete
■PreTranslatorOperation Create
■Table Create
■TableEntry Create
■TimedRoute Create
■TimedRouteEntry Create
■TimedRouteOperation Create
DestinationRoute Create
Syntax
DestinationRoute Create nRouteId szDescription
DescriptionCreates a route that specifies the primary and alternative 
destination device of a call (for example, which CO Line or Digital Line 
Card port over which to route the call). If the destination route already 
exists, this command removes all of its entries and operations, and 
overwrites its description with the new information.
Arguments
nRouteId — An integer in the range 1 – 32768, uniquely identifying this 
destination route.
szDescription — The description or name of the destination route.
Example: This example creates destination route 3 and names it “Voice 
Application”: 
DestinationRoute Create 3 Voice Application 
						

							118CHAPTER 2: DIAL PLAN
DestinationRouteEntry Create
Syntax
DestinationRouteEntry Create nRouteId nEntryId szExtension
Descriptioncreates a destination route entry that identifies a single 
destination device or device list.
If the specified destination route entry already exists, this command 
overwrites it with the new information. During routing, the system 
checks the list of destinations in ascending 
nEntryId order (nEntryId 1 first).
Arguments
nRouteId — An integer in the range 1 through 32768.
nEntryId — An integer in the range 1 through 32768. The system checks 
the list of destinations in ascending nEntryId order, and uses the first 
available one.
szExtension — The extension of the destination device or device list. Note 
that the system does not dial this extension (that is, it neither checks the 
extension against a dial plan nor subjects it to Class of Service restrictions, 
digit manipulation, or routing) but instead uses the extension only to look 
up the device in the internal device directory.
Example: This example command creates, in route table 3, entry 1 
and defines extension list *0003 as the destination for this route entry. 
Extension list *0003 contains the voice mail extensions/ports.
DestinationRouteEntry Create 3 1 *0003
DestinationRouteOperation Create
Syntax
DestinationRouteOperation Create nRouteId nEntryId nOperId 
szOperation szValue
DescriptionCreates a digit manipulation operation for a destination 
route entry. If the specified digit manipulation operation already exists, 
this command overwrites it with the new information. During routing the 
system processes the entire list of operations in ascending nOperId order 
(nOperId 1 first). 
						

							Dial Plan Configuration File Commands119
Arguments
RouteId — An integer in the range 1 through 32768.
nEntryId — An integer in the range 1 through 32768 specifying the 
destination route entry to which this operation applies.
nOperId — An integer in the range 1 through 32768. The system 
processes the list of operations in ascending nOperId order.
szOperation — The name of the digit manipulation operation to perform: 
stripLead, stripTrail, replace, prepend, append.
szValue — A value used by the operation, either the string of digits to 
prepend, append, replace with, or the number of digits to strip.
Example: This example command creates, for destination route 3, 
entry 1, an operation numbered 1, with the associated function 
stripLead, and an argument of 1, indicating that the command removes 
(strips) one leading digit from the dialed number before dialing.
DestinationRouteOperation Create 3 1 1 stripLead 1
ExtensionLength
Syntax
ExtensionLength nExtensionLength
DescriptionThe length of extension numbers for system devices. The 
default is 3 for NBX 100 systems. The default is 4 for SuperStack 3 NBX 
systems.
Arguments
nExtensionLength — specifies either 3 to designate a a 3-digit dial plan, or 
4 to designate a 4-digit dial plan. 
						

							120CHAPTER 2: DIAL PLAN
ExtensionRange
Syntax
ExtensionRange szExtensionType szLowestExtension szHighestExtension
DescriptionA range of extensions for each type of device. When the 
system automatically generates extensions it assigns them from within 
this range. When you manually generate an extension number, verify that 
it is within the valid range. During a dial plan import operation, the 
system does not validate that existing extensions are within the specified 
range. 3Com 
strongly recommends that you configure the dial plan 
before you define any devices in the system.
Arguments
szExtensionType — One of these: Telephone, Park, Auto Attendant, Hunt 
Group, External.
szLowestExtension — The lowest desired extension for this device type.
szHighestExtension — The highest desired extension for this device type.
Example: These commands define the extension range for telephones as 
100 through 449, for call park as 601 through 609, for Auto Attendants 
as 500 through 599, for hunt groups as 450 through 499, and for 
external lines as 600 through 799.
ExtensionRange Telephone 100 449
ExtensionRange Park 601 609
ExtensionRange Autoattendant 500 599
ExtensionRange HuntGroup 450 499
ExtensionRange External 600 799
CAUTION: Do not define extension ranges that overlap. The only 
exception is Park, which must be within the External range.