3Com Nbx 100 And Ss3 Nbx Administration Guide

							Configuring VPIM Parameters Using the NBX NetSet Utility81
Table 16   Operations Management Dialog Box Fields
FieldPurpose
Operations statusThe status of the queue of outgoing voice mail messages.
Possible values: Starting, Ready, Processing, Stopped.
Number of outgoing 
messagesThe number of messages in the outgoing queue when this 
dialog box was last accessed or refreshed.
Outgoing Messages
Time WaitingThe number of minutes that the voice mail message has 
been waiting in the queue.
# AttemptsThe number of times the NBX system has attempted to 
send the voice mail message.
SenderThe e-mail address of the user who sent the voice mail 
message.
DestinationThe IP address and extension to which the voice mail 
message is to be sent.
RemoveNOTE: You must stop the message queue before you can 
remove any message.
Select a voice mail message in the scroll list and click this 
button to remove the message from the queue. The NBX 
system prompts you to confirm that you want to delete the 
selected message.
Use Shift+Click to select a block of messages, or Ctrl+Click 
to select several messages that are not in a single block.
Apply Buttons
Send all messages nowThe NBX system attempts to send all messages immediately 
and then waits for the required number of minutes (see 
Ta b l e 1 5
) before making another send attempt.
Send all messages now 
and then delete themThe NBX system makes a single attempt to send each 
message on the queue.
Any undelivered messages are returned to sender with 
delivery failure notices, and then deleted from the outgoing 
mail queue.
Delete all messages 
nowThe NBX system deletes all messages from the outgoing 
mail queue. 
These messages are not returned to sender with delivery 
failure notices.
Stop operationsStops the queue if it is currently active.
Start operationsStarts the queue if it is stopped. 
						

							82CHAPTER 2: DIAL PLAN
StatisticsTo view the most recent statics for voice mail messages, click the Statistics 
button. The Statistics window (Figure 25
) appears. Table 17 lists the fields 
in this window and explains their purpose.
Figure 25   Statistics Window
Table 17   Statistics Window Fields
FieldPurpose
Incoming Messages
Total messages received 
by systemThe number of messages received by this NBX system 
from voice mailboxes on other systems
Total messages delivered 
to user mailboxesThe number of voice mail messages delivered to user 
voice mailboxes on this NBX system. If this number is 
smaller than the total number of messages received, 
some messages have not yet been delivered. 
						

							Configuring VPIM Parameters Using the NBX NetSet Utility83
Outgoing Messages
Total messages submitted 
for external deliveryThe number of messages submitted by users of this 
NBX system for delivery to voice mailboxes on other 
systems
Total messages delivered 
to external recipientsThe number of messages for which a confirmation of 
delivery has been received.
Total messages returned 
to sender on failed 
deliveryThe number of messages that have been returned 
because they could not be delivered.
Failed Outgoing Messages
If a message appears in this list, the NBX system has tried to deliver the message and 
has failed. The NBX system attempts to resend the message up to the retry limit. 
Default: 4. Minimum: 1. Maximum: 10.
Date/TimeThe date and time that the message was originally 
submitted for delivery
AttemptsThe number of attempts that the NBX system has made 
to send each message
SenderThe person on the local NBX system who created and 
sent the voice mail message
DestinationThe defined target for the voice mail message
ReasonThe reason for the most recent failure to deliver the 
message
Reset and Reboot Times
Last reset commandThe date and time of the last reset command. Sets all 
VPIM statistics to 0 (zero) and deletes all messages from 
the Failed Outgoing Messages queue.
If this field’s date and time are more recent than Last 
system reboot, then the NBX system began to collect 
the currently displayed statistics at this date and time.
Last system rebootThe date and time of the most recent reboot of the NBX 
system. An NBX system reboot resets all VPIM statistics 
to 0 (zero).
If this field’s date and time are more recent than Last 
reset command, then the NBX system began to collect 
the currently displayed statistics at this date and time.
Table 17   Statistics Window Fields (continued)
FieldPurpose 
						

							84CHAPTER 2: DIAL PLAN
Advanced SettingsThe NBX system transmits VPIM voice mail messages by attaching them 
to e-mail messages that are sent using SMTP (Simple Mail Transfer 
Protocol) or ESMTP (Extended Simple Mail Transfer Protocol).
Click the Advanced Settings button to access the Advanced Settings 
dialog box (Figure 26
). Set the parameters to control the behavior of 
SMTP. Table 18
 describes the fields.
Figure 26   Advanced Settings Dialog Box
Table 18   VPIM Advanced Settings Dialog Box
FieldPurpose
SMTP OK responseDefinition: The amount of time that the local 
system waits for a response from the remote system.
Detail: After the local system attempts to open a 
connection to the remote system, it waits for a 
response giving the status of the connection.
Minimum: 5 minutes
Default: 5 minutes 
						

							Configuring VPIM Parameters Using the NBX NetSet Utility85
SMTP HELO responseDefinition: The amount of time that the local 
system waits for an acknowledgement of a HELO 
message.
Detail: After the greeting, the local system sends 
either a HELO (or EHLO to get ESMTP) message to 
identify itself. The other site then responds with an 
acknowledgement of that message.
Minimum: None defined.
Default: 5 minutes
SMTP EHLO responseDefinition: The amount of time that the local 
system waits for acknowledgement of a EHLO 
message.
Detail: After the greeting, the local system sends 
either a HELO (or EHLO to get ESMTP) message to 
identify itself. The other site then responds with an 
acknowledgement of that message.
Minimum: None defined.
Default: 5 minutes
SMTP MAIL responseDefinition: The amount of time that the local 
system waits for an acknowledgement of a MAIL 
command.
Detail: After the local system sends out a MAIL 
command along with the From information, it waits 
for a response from the other site to indicate that the 
MAIL command was received.
Minimum: 5 minutes
Default: 5 minutes
SMTP RCPT responseDefinition: The time that the local system waits for 
an acknowledgement of a RCPT command.
Detail: After the system sends out a RCPT command 
(one per recipient), it waits for a response from the 
other site indicating acceptance or rejection of the 
recipient.
Minimum: 5 minutes
Default: 5 minutes
Table 18   VPIM Advanced Settings Dialog Box (continued)
FieldPurpose 
						

							86CHAPTER 2: DIAL PLAN
SMTP DATA responseDefinition: The time that the local system waits for 
an acknowledgement of a DATA command.
Detail: After the local system has specified all of the 
recipient information, it sends a DATA command to 
indicate that it is ready to send the mail message 
itself. It then waits for the other site to acknowledge 
the DATA command.
Minimum: 2 minutes
Default: 2 minutes
SMTP DATA END responseDefinition: The time that the local system waits, 
after sending the entire message, for an 
acknowledgement from the other site that the 
message was received.
Detail: After the local system sends the entire 
message, it waits for a response from the other site 
indicating acceptance of the message.
Minimum: 10 minutes
Default: 10 minutes
SMTP RSET responseDefinition: The time that the local system waits for 
an acknowledgement of a RSET command.
Detail: Since the RSET command resets the SMTP 
connection, the local system must wait for the other 
site to reset itself and acknowledge.
Minimum: None defined
Default: 10 minutes
SMTP QUIT responseDefinition: The time that the local system waits for 
an acknowledgement of the QUIT command.
Detail: When the local system is finished 
transmitting a message and wants to break the 
connection, it sends a QUIT command. It then waits 
for the other site to acknowledge the QUIT 
command. When the acknowledgement arrives, or 
when the time-out value is reached, whichever 
comes first, the local system breaks the connection.
Minimum: None defined
Default: 5 minutes
Table 18   VPIM Advanced Settings Dialog Box (continued)
FieldPurpose 
						

							Configuring VPIM Parameters Using the NBX NetSet Utility87
Configuring Domain
Name Server
InformationWhen the SMTP utility attempts to send e-mail, it must be able to resolve 
a host name within an e-mail address and determine the proper IP 
address from that name. Domain Name Servers on the Internet perform 
this function. You can configure up to three DNS entries with the NBX 
NetSet utility. The NBX system uses the second and third entries if the first 
or second cannot be reached. To configure DNS information in the NBX 
NetSet utility:
1In the NBX NetSet - Main Menu window, click System Configuration.
2Click the System Settings tab and the System-wide button. The System 
Settings dialog box (Figure 27
) appears.
Figure 27   System Settings Dialog Box
3In the Primary DNS, Secondary DNS, and Tertiary DNS text boxes, type the 
IP addresses of three Domain Name Servers. If you have the IP address of 
only one server, type it in the Primary DNS text box. If you have the IP 
address of only two servers, type them in the Primary and Secondary DNS 
text boxes. Click OK. 
						

							88CHAPTER 2: DIAL PLAN
Overview of 
Virtual Tie LinesA Virtual Tie Line (VTL) provides a way to make calls between NBX system 
sites that are separated geographically but tied together by a Wide Area 
Network (WAN) connection. An NBX 100 system can support up to 8 
simultaneous VTL connections; a SuperStack 3 NBX system can support 
up to 48. VTLs are a licensed feature of the NBX systems.
On any NBX system, any licensed VTL connection can be used either for 
an incoming VTL call from any site or for an outgoing VTL call to any site. 
A VTL connection is not dedicated in the same way as a physical tie line, 
which always connects the same pair of sites. In the example in Figure 28
, 
the VTLs on the Chicago NBX system can be used for any combination of 
incoming and outgoing VTL calls to either Atlanta or Dallas.
The NBX system can reroute VTL calls that fail to reach their destination 
on the first attempt. For details, see “Call Rerouting for Virtual Tie Lines”
 
later in this chapter.
■You must implement either IP On-the-Fly or Standard IP on an NBX 
system in order to use VTL connections to other NBX systems.
■VTL connections cannot be configured to run through firewalls or NAT 
routers.
■When you calculate the number of devices on an NBX system, do not 
include the number of VTLs.
There are two implementation techniques you can use: unique extension 
ranges or site codes, as described next.
VTL Connections
Using Unique
Extension RangesIf you can restrict the extension ranges on each of the NBX systems so 
that they do not overlap, you can configure the dial plans to route calls 
based only on the extension that is being dialed. The caller does not have 
to dial any digits to specify the site.
Assess your growth plans for each site to verify that, as you add 
telephones, you do not exceed the extension ranges that you have 
defined.
Figure 28
 depicts a configuration that uses unique extension ranges 
						

							Overview of Virtual Tie Lines89
Figure 28   Multi-site network using Virtual Tie Lines
In the sample network shown in Figure 28, each site is set up to use a 
unique range of telephone extensions. The dial plan on each of the 
systems is configured so that whenever a call is made to an extension not 
located at the local site, the NBX system sets up a VTL connection to the 
appropriate site.
To make a call to a user in Dallas, a user in Chicago dials a Dallas 
extension (3000 through 3999). The dial plan on the Chicago NBX system 
is configured to set up the necessary VTL connection to the Dallas NBX 
system, and then to the extension at that site.
See “Dial Plan Configuration”
 later in this chapter for further information 
on how to set up VTLs in the dial plan.
WANChicago
NBX System
Extensions
1000 – 1999Atlanta
NBX System
Extensions
2000 – 2999
Dallas
NBX System
Extensions
3000 – 3999 
						

							90CHAPTER 2: DIAL PLAN
VTL Connections
Using Site CodesThe simpler way to implement VTL connections uses a site code, 
consisting of one or more digits that a user must dial to specify the site 
that is being called. This approach requires no restriction on the 
telephone extension ranges, but does require the caller to dial the site 
code digits as well as the extension.
A site code can by any number of digits you want, but typically, one- or 
two-digit numbers make the most sense. The dial plan at each site must 
include appropriate routing instructions for each of the possible site code.
Figure 29
 shows three sites connected by VTLs. All sites use the same 
range of extension numbers (1000 through 3999). To reach someone on 
another NBX system, a user must dial a site code (61, 62, or 63 in this 
example) followed by an extension.
Figure 29   Virtual Tie Lines Using Site Codes
To call someone in Atlanta, a user in Chicago must dial the site code 62 
and then the appropriate extension (1000 through 3999). To reach a user 
in Dallas, a user in Chicago must dial 63 and then the appropriate 
extension (1000 through 3999). Because the extension is preceded by the 
site code, there is no conflict between the extension dialed and an 
identical extension number at the local site (Chicago). The choice of site 
codes is made by the person who configures the dial plans for the sites.
See “Dial Plan Configuration”
later in this chapter for more information 
on how to set up VTLs in the dial plan.
WANChicago
NBX System
Extensions
1000 – 3999Atlanta
NBX System
Extensions
1000 – 3999
Dallas
NBX System
Extensions
1000–3999 Site Code 61
Site Code 63Site Code 62