3Com Nbx 100 And Ss3 Nbx Administration Guide

							Managing Dial Plan Pretranslators71
Removing a
Dial Plan TableThis section describes how to remove a dial plan table. Note that you 
mustnot remove any of the predefined tables (Internal, Incoming, or 
Least Cost).
CAUTION: You cannot remove a dial plan table if a device is using it. 
To remove the table, you must first remove all devices from the Devices 
Using Table list.
To remove a dial plan table:
1In the NBX NetSet – Main Menu window, click Dial Plan. The Dial Plan 
window appears, displaying the Operations tab (Figure 3
).
2Click the Ta b l e s tab (Figure 14
.)
3Select the table you want to remove.
4Click Remove. A dialog box prompts you to confirm the removal.
5Click Ye s.
Managing Dial Plan 
PretranslatorsPretranslators are tables in the dial plan configuration file. Each entry in 
a pretranslator table contains a string of one or more digits that are 
compared to incoming or outgoing digits. When the digits match an 
entry in the table, the NBX system performs the associated pretranslator 
operations.
For more information, see:
■Identifying Devices Using Pretranslators
■Identifying Devices Using Pretranslators for CLI
■Removing a Pretranslator from the Dial Plan
Identifying Devices
Using PretranslatorsTo view a list of devices and their associated pretranslators, or to associate 
a pretranslator with a specific device:
1In the NBX NetSet – Main Menu window, click Dial Plan.
2Click the Pretranslators tab (Figure 16
). 
						

							72CHAPTER 2: DIAL PLAN
Figure 16   Pretranslators Tab
3Select a pretranslator, or (none) for devices that have no pretranslator.
4Click Devices Using. The Devices Using Pretranslator dialog box appears 
(Figure 17
). If you selected (none) in step 3, you see a list of devices that do 
not use a pretranslator. Table 13
 describes each field. The fields are the 
same for the Devices Using Pretranlator for CLI dialog box.
Figure 17   Devices Using Pretranslator Dialog Box
5To move a device to the Devices Using Pretranslator list, select it in the 
Devices Not Using Pretranslator list and click . Then 
6Click Close. 
						

							Managing Dial Plan Pretranslators73
To enable a specific pretranslator, update the dial plan. See “Importing 
and Exporting Dial Plan Configuration Files” earlier in this chapter.
Identifying Devices
Using Pretranslators
for CLITo view a list of devices that use a particular pretranslator to present 
Calling Line ID (CLI) information on outgoing calls:
1In the NBX NetSet – Main Menu window, click Dial Plan.
2Click the Pretranslators tab (Figure 16
) and select a pretranslator from the 
scroll list. For a list of devices that have no pretranslator, select (none).
3Click Devices Using Pretranslator for CLI. The Devices Using Pretranslator 
for CLI dialog box appears (Figure 18
). If you selected (none) in step 3, you 
see a list of devices that do not use a pretranslator for Calling Line ID.
4To move a device to the Devices Using Pretranslator list, select it and click 
. Then click Close. See Table 13
 for field descriptions.
Figure 18   Devices Using Pretranslator for CLI Dialog Box Table 13   Pretranslator Fields
FieldPurpose
Pretranslator IDThe identification number of the pretranslator as 
specified in the dial plan.
Pretranslator NameThe name of the pretranslator as specified in the dial plan.
Devices Using 
PretranslatorDevices currently using the pretranslator.
Devices Not Using 
PretranslatorDevices not using the pretranslator. 
						

							74CHAPTER 2: DIAL PLAN
Removing a
Pretranslator from
the Dial PlanTo remove a pretranslator:
1In the NBX NetSet – Main Menu window, click Dial Plan.
2Click the Pretranslators tab (Figure 16
).
3Select a pretranslator from the scroll list.
4Click Remove.
CAUTION:You cannot remove a pretranslator if any device is currently 
using it. If you want to remove the pretranslator, you must first remove all 
devices from the Devices Using Pretranslator list.
Configuring the 
Dial Plan for the 
4ESS Protocol (T1)The 4ESS protocol, used on T1 Digital Line Cards that are configured for 
PRI operation, requires specific configuration entries in the NBX system 
dial plan. If you purchase the 4ESS protocol and SDN (Software Defined 
Network) service from your long-distance carrier, you must make dial plan 
changes similar to those outlined in “Configuring the Dial Plan for 
Software-Defined Network Calls” later in this section. If you want to 
make long distance calls or international long distance calls using the 
4ESS protocol, you must make dial plan changes similar to those outlined 
in “Configuring the Dial Plan for North American Long Distance”
 and 
“Configuring the Dial Plan for International Long Distance”
 later in this 
section.
Configuring the Dial Plan for Software-Defined Network Calls
In the NBX system dial plan, if you are using the 4ESS protocol and you 
want to make SDN calls, you must configure a unique route to use for 
SDN calls and include the letters SDN at the beginning of the dial string.
Example: The dial plan entry shown in Figure 19
 adds the characters 
SDN (must be capital letters) before the long-distance dialed digits. This 
example assumes that route 4 is used for SDN calls.
Figure 19   Dial Plan Entries for SDN
/                              Route Entry OperID Operation Value
/                              ----- ----- ------ --------- -----
DestinationRouteOperation Create   4      1      1    prepend    SDN 
						

							Configuring the Dial Plan for the 4ESS Protocol (T1)75
Configuring the Dial Plan for North American Long Distance
In the NBX system dial plan, if you are using the 4ESS protocol and you 
want to make long-distance calls, you must remove from the dial string 
any digits that are dialed by users to access the long-distance service. For 
example, if users normally dial 9 and then 1 to obtain a long-distance dial 
tone, and then dial a 10-digit number, the dial plan must remove the 9 
and the 1 and present only the 10-digit number to the long-distance 
carrier. Otherwise, the 4ESS protocol rejects the call.
Example: If you use route 1 in the dial plan for Long Distance, and users 
must dial 91 to make a long-distance call, the dial plan entries shown in 
Figure 20
 remove the first two digits (91) and submit the remaining 10 
digits to the long-distance carrier.
Figure 20   Dial Plan Entries for North American Long Distance
Configuring the Dial Plan for International Long Distance
In the NBX system dial plan, if you are using the 4ESS protocol and you 
want to make international long-distance calls, you must remove from 
the dial string the digits 9011 that are dialed by users to access the 
international long-distance service. For example, if the user dials the 
string 9-011-44-1234-567890, the dial plan must remove the 9011 
before passing the dialed digits to the long-distance carrier or the 4ESS 
protocol rejects the call. See Figure 21
.
Figure 21   Dial Plan Entries for International Long Distance
Table Create 1 Internal 4 Digit Extensions
/                 ID Entry Digits Min Max  Class        Prio Route
/                 -- ----- ------ --- ---  ------------ ---- -----
TableEntry Create  1     2 91      12  12  LongDistance    0     1
/                              Route Entry OperID Operation Value
/                              ----- ----- ------ --------- -----
DestinationRouteOperation Create   1      1      1    stripLead    2
Table Create 1 Internal 4 Digit Extensions
/                 ID Entry Digits Min Max  Class         Prio Route
/                 -- ----- ------ --- ---  ------------  ---- -----
TableEntry Create  1     3 9011    12  64  International    0     1
/                              Route Entry OperID Operation Value
/                              ----- ----- ------ --------- -----
DestinationRouteOperation Create   3      2      1    stripLead    4 
						

							76CHAPTER 2: DIAL PLAN
Overview of Voice 
Profile for Internet 
MailWith Voice Profile for Internet Mail (VPIM), users on one NBX system can 
send voice mail to a user on another NBX or VPIM-compliant system.
To send a voice mail message to a user on another VPIM-compliant 
system, an NBX user first composes the voice mail message, using the 
commands in the user’s voice mailbox. Depending on how the system’s 
dial plan is configured, the user can specify the destination in two ways:
■If the dial plan is configured for site codes, the user specifies the 
destination site code followed by the star key (*) and the extension of 
the person for whom the voice mail message is intended.
■If the dial plan is configured without site codes, the user specifies the 
extension of the person for whom the message is intended. This is 
easier, but requires that each site use a unique extension range for 
telephones.
■A user who knows the IP address of a VPIM-compliant voice mail 
system and the extension of a person who uses that system can 
compose a voice mail message and then send it using these steps:
■Dial the IP address, pressing the * key after each field in the 
address, including the last field.
■Dial the extension of the person followed by #.
The system administrator configures the dial plan and decides whether to 
use site codes or unique extension ranges.
Configuring the 
Dial Plan for VPIMTo fully define a VPIM connection between two NBX systems, you must 
create entries in the dial plan for the following items:
■The digit sequence that a telephone user must dial to access the VPIM 
connection
■The route number that is used to access the other NBX system
■The extension list to which the VPIM route belongs
■The operations that must be performed on the dialed digits in order to 
create the appropriate outgoing digit sequence 
						

							Configuring the Dial Plan for VPIM77
Figure 22 contains sample lines which, when added to an existing dial 
plan, implement VPIM connections to two other NBX systems, one in 
Atlanta and one in Dallas. Table 14
 explains each entry.
Figure 22   Dial Plan with VPIM Implementation Commands
Table Create 1 Internal Extensions
/                  Id Entry  Digits      Min Max Class           Prio Route
/                  -- -----  ----------- --- --- -------------   ---- -----
TableEntry Create   1    45  V82           5   5 WAN                0   532
TableEntry Create   1    46  V83           6   6 WAN                0   533
/                       Route Description
/                       ----- -----------
DestinationRoute Create   532 Atlanta VPIM Connection
DestinationRoute Create   533 Dallas VPIM Connection
/                            Route Entry DestinationExtension
/                            ----- ----- --------------------
DestinationRouteEntry Create   532     1 *0003
DestinationRouteEntry Create   533     1 *0003
/                                Route Entry OperId Operation  Value
/                                ----- ----- ------ ---------  -----
DestinationRouteOperation Create   532     1      1 stripLead  3
DestinationRouteOperation Create   532     1      2 prepend    10*234*101*222*
DestinationRouteOperation Create   533     1      1 stripLead  3
DestinationRouteOperation Create   533     1      2 prepend    10*234*101*100*
Ta b l e 1 4    Explanation of Entries in Figure 22
FieldPurpose
Table Create 1 Internal Extensions
This command is already present in all default dial 
plans, and is included here as a reference point for 
subsequent commands.
TableEntry Create   1    45    V82           5   5 WAN                0   532
TableEntry Create 1 45This portion of the command creates entry 45 in 
dial plan table 1 (the Internal Extensions table). The 
choice of 45 as the entry number depends on how 
many entries exist in table 1. This example assumes 
that the highest number assigned to a previously 
existing entry was 44. 
						

							78CHAPTER 2: DIAL PLAN
V82 (Digits column)The letter V (required, and must be a capital letter) 
indicates that this is a VPIM connection, and the 
82 indicates that the user must dial 82 to access 
the VPIM connection and then dial the extension 
the user wants to reach.
You can select any number of digits for a site 
code. The selected number must not conflict with 
other dial plan entries. This example assumes that 
82 is not used in any other way in the dial plan.
Long digit sequences can annoy telephone users 
and create the opportunity for dialing errors.
Min (5) Max (5)Indicates that the total digit sequence dialed by 
the user is 5 digits. The first two digits are the site 
code (82 in this example) and the remaining 3 
digits are the destination extension.
Class (WAN)Indicates that this call is classified as WAN. All 
VPIM calls have this classification.
Priority (0)This field is unused by the dial plan; the default 
value is zero (0).
Route (532)In this example, the VPIM connection to the other 
NBX system uses route 532. The route number 
must be unique in the dial plan and in the range of 
1–32768. 
DestinationRoute Create   532 Atlanta VPIM Connection
This command creates route number 532 and 
gives it the name Atlanta VPIM Connection.
DestinationRouteEntry Create   532     1 *0003
This command (mandatory for all VPIM routes) 
assigns route 532 to the extension list *0003. 
DestinationRouteOperation Create   532     1     1 stripLead 3
For DestinationRoute 532, entry 1, this command 
creates operation 1, which removes the first three 
digits, including the letter V, from the digit string, 
leaving only the extension that the user dialed.
DestinationRouteOperation Create   532     1     2 prepend    10*234*101*222*
For DestinationRoute 532, entry 1, this command 
creates operation 2, which places the string 
10*234*101*222* in front of the extension. This 
string represents the IP address of the target NBX 
system. You must use the star character (*) to 
separate the fields within the IP address and to 
separate the IP address from the extension field.
Ta b l e 1 4    Explanation of Entries in Figure 22 (continued)
FieldPurpose 
						

							Configuring VPIM Parameters Using the NBX NetSet Utility79
Configuring VPIM 
Parameters Using 
the NBX NetSet 
UtilityUsing the NBX NetSet utility, you can configure several VPIM control 
parameters, check the status of the VPIM queues, and obtain statistics on 
recent VPIM activity.
VPIM Control
ParametersTo set the VPIM control parameters:
1In the NBX NetSet - Main Menu window, click NBX Messaging.
2Click the VPIM tab. See Figure 23
. Table 15 describes the fields.
Figure 23   VPIM Tab
Table 15   VPIM Tab Fields
FieldPurpose
Max message sizeControls the size of incoming messages from other 
sites. If a message is larger than the specified 
value, the NBX system rejects it. The default value 
represents a voice mail message approximately 4 
to 5 minutes in length.
Default: 3000 Kbytes 
						

							80CHAPTER 2: DIAL PLAN
Operations
ManagementTo manage outgoing voice mail messages, click Queue Management. The 
Operations Management dialog box (Figure 24
) appears. See Table 16.
Figure 24   Operations Management Dialog Box
Time between send 
attempts (minutes)For outgoing messages, the NBX system may not 
be able to contact the target system on the first 
attempt. If so, the NBX system attempts to contact 
the target system later. To change the time 
between attempts, change this number.
Default: 15 minutes
Minimum: 1 minute
Maximum: 60 minutes
Max number of send attemptsSpecifies the number of times (Default: 4) that the 
NBX system tries to connect to the target system.
After the specified number of send attempts, the 
message is returned to the sender’s voice mailbox 
with a notice that the message could not be sent.
Table 15   VPIM Tab Fields (continued)
FieldPurpose