Avaya CallPilot Message Networking User Manual
CallPilot Message Networking Set Up and
Operation Guide
Avaya Business Communications Manager
Document Status: Standard
Document Number: NN40090-301
Document Version: 04.02
Date: October 2010
© 2010 Avaya Inc.
All Rights Reserved.
Notices
While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing,
Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document
without the obligation to notify any person or organization of such changes.
Documentation disclaimer
Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of this documentation
unless such modifications, additions, or deletions were performed by Avaya. End User agree to indemnify and hold harmless Avaya,
Avaya’s agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with,
subsequent modifications, additions or deletions to this documentation, to the extent made by End User.
Link disclaimer
Avaya is not responsible for the contents or reliability of any linked Web sites referenced within this site or documentation(s) provided by
Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not
necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links
will work all the time and has no control over the availability of the linked pages.
Warra nty
Avaya provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In
addition, Avaya’s standard warranty language, as well as information regarding support for this product, while under warranty, is
available to Avaya customers and other parties through the Avaya Support Web site: http://www.avaya.com/support
Please note that if you acquired the product from an authorized reseller, the warranty is provided to you by said reseller and not by Avaya.
Licenses
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, HTTP://SUPPORT.AVAYA.COM/
LICENSEINFO/ ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE,
PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER (AS APPLICABLE)
UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESS OTHERWISE
AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED
FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA AUTHORIZED RESELLER, AND AVAYA
RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE
SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING
OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING,
DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS "YOU" AND "END
USER"), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND
AVAYA IN C. OR T HE AP PL I CA BL E AVA YA AF FI LI AT E ( "AVAYA ") .
Copyright
Except where expressly stated otherwise, no use should be made of the Documentation(s) and Product(s) provided by Avaya. All content
in this documentation(s) and the product(s) provided by Avaya including the selection, arrangement and design of the content is owned
either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating
to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any
content, in whole or in part, including any code and software. Unauthorized reproduction, transmission, dissemination, storage, and or
use without the express written consent of Avaya can be a criminal, as well as a civil offense under the applicable law.
Third Party Components
Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements
("Third Party Components"), which may contain terms that expand or limit rights to use certain portions of the Product ("Third Party
Terms"). Information regarding distributed Linux OS source code (for those Products that have distributed the Linux OS source code),
and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply to them is available on the
Avaya Support Web site: http://support.avaya.com/Copyright.
Trademarks
The trademarks, logos and service marks ("Marks") displayed in this site, the documentation(s) and product(s) provided by Avaya are the
registered or unregistered Marks of Avaya, its affiliates, or other third parties. Users are not permitted to use such Marks without prior
written consent from Avaya or such third party which may own the Mark. Nothing contained in this site, the documentation(s) and
product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the
express written permission of Avaya or the applicable third party. Avaya is a registered trademark of Avaya Inc. All non-Avaya
trademarks are the property of their respective owners.
Downloading documents
For the most current versions of documentation, see the Avaya Support. Web site: http://www.avaya.com/support
Contact Avaya Support
Avaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone
number is 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Web site: http://
www.avaya.com/support
Task List
New in this release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Setting up Digital Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
To set the Digital Networking properties........................................................................18
To configure Avaya BCM to use IP addresses ..............................................................20
To check that Avaya BCM is not configured to use DNS ..............................................21
To check that a Host Name is entered on the Avaya BCM ...........................................21
To change your local CallPilot Host name or IP address ..............................................21
Setting up AMIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
To set up AMIS networking properties ..........................................................................24
To set up AMIS Call Blocking times ..............................................................................27
To set the Dialing Translation properties.......................................................................30
To build a Dialing Translation Table ..............................................................................31
To review Dialing Translation Table entries ..................................................................31
To change an entry in the Dialing Translation Table .....................................................32
To delete an entry in the Dialing Translation Table .......................................................33
To send a test network message using the
AMIS Loopback mailbox — Norstar Voice Mail .............................................................36
To send a test network message using the AMIS Loopback mailbox — Avaya CallPilot36
3
Creating network sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
To set the general networking properties ......................................................................39
To create a network site ................................................................................................41
To change the properties of a network site ...................................................................42
For best results, use a telephone that is attached to the same switch as your voice mail system.
Avoid using wireless telephones.To record a site name ...............................................43
To delete a site ..............................................................................................................44
Network Delivery Mailboxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
To create a Network Site mailbox..................................................................................49
To create a Network AMIS mailbox ...............................................................................50
To change Network Delivery Mailbox parameters .........................................................52
To delete a Network Delivery Mailbox ...........................................................................52
Troubleshooting Non-Delivery Notification messages . . . . . . . . . . . . . . . 53
Message Networking programming record . . . . . . . . . . . . . . . . . . . . . . . . 59
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
CallPilot Message Networking Set Up and Operation Guide
4 Task List
NN40090-301NN40090-301
Contents
New in this release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Chapter 1
Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
About CallPilot Message Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Requirements for setting up Message Networking . . . . . . . . . . . . . . . . . . . . . . . . . 9
Digital and AMIS networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Setting up Avaya BCM and M1CallPilot for VPIM broadcast messages . . . . . . . . 11
About AMIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Ways of sending network messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Site-Based Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Network Delivery Mailboxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Direct Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Assigning Message Networking to subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Symbols and text conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Customer Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5
Chapter 2
Setting up Digital Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Setting the Digital Networking properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Configuring your system network properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Configuring your system if you do not use DNS . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Chapter 3
Setting up AMIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Setting up AMIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
AMIS networking properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
About Call Blocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Call Blocking periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Setting up Call Blocking times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
About Dialing Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
How the Dialing Translation Table works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Examples of Dialing Translation Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
CallPilot Message Networking Set Up and Operation Guide
6 Contents
Setting the Dialing Translation properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Building a Dialing Translation Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Reviewing entries in the Dialing Translation Table . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Changing an entry in the Dialing Translation Table . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Deleting a Dialing Translation Table entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Testing network message capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Sending a test network message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Chapter 4
Creating network sites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Setting the general networking properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Creating a network site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Changing the properties of a network site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Recording a site name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Deleting a site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Disabling Network Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Enabling Broadcast and Group List Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Before you test network message capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Chapter 5
Network Delivery Mailboxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
About Network Delivery Mailboxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
About creating Network Delivery Mailboxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Creating a Network Site mailbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Creating a Network AMIS mailbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Changing Network Delivery Mailbox parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Deleting a Network Delivery Mailbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Chapter 6
Troubleshooting Non-Delivery Notification messages . . . . . . . . . . . . . . . 53
Non Delivery Notification messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Chapter 7
Message Networking programming record . . . . . . . . . . . . . . . . . . . . . . . . . 59
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
NN40090-301NN40090-301
New in this release
The following sections detail what’s new in CallPilot Message Networking Set Up and Operation
Guide (NN40090-301).
Other
See the following sections for information about changes that are not feature-related:
Revision history
January 2009
Standard 03.02. This document is up-issued to add a note in the chapter Creating Network Sites.
7
CallPilot Message Networking Set Up and Operation Guide
8 New in this release
NN40090-301NN40090-301
Chapter 1
Getting started
About this Guide
The CallPilot Message Networking Set Up and Operation Guide describes how to set up Message
Networking on an Avaya Business Communications Manager (Avaya BCM).
About CallPilot Message Networking
Message Networking links your voice mail system with voice mail systems at different locations.
Message Networking uses Digital Networking and Audio Message Interchange Specification
(AMIS) to let subscribers exchange messages with subscribers at other locations.
You must apply the Message Networking keycode before your system can receive or send network
messages. Contact your vendor to purchase or trial a keycode for Message Networking.
9
Requirements for setting up Message Networking
To use Message Networking you need to know:
• how to use the telephones on your system. If you use Avaya Business Series Terminals see the
CallPilot Reference Guide, CallPilot Manager Set Up and Operation Guide or the CallPilot
Quick Reference Cards.
• if you use an Avaya BCM, which mailbox interface you use.
See the CallPilot Reference Guide for information on how to check which interface you use.
• how to start CallPilot Manager and use the CallPilot Manager interface.
For information see “Starting CallPilot Manager” and “About the CallPilot Manager
interface” in Chapter 2 of the CallPilot Manager Set Up and Operation Guide.
• if you use a BCM system, how to start Element Manager and use the Business Element
Manager Interface.
Refer to the Avaya Business Communications Manager Administration Guide.
• specific addressing information about Avaya CallPilot and other voice messaging sites on
your network. It is recommend that you work with the Network Administrator when you set up
Message Networking.
Digital and AMIS networking
Message Networking uses two types of networking:
CallPilot Message Networking Set Up and Operation Guide
10 Chapter 1 Getting started
• Digital Networking — transfers messages using an Internet or intranet connection using
Voice Profile for Internet Mail (VPIM) to support interconnection to equipment from Avaya
and other vendors
• AMIS — supports an analog transfer protocol that does not require any formal data
networking arrangements
About Digital Networking
Digital Networking links CallPilot and other voice mail systems at different locations. Digital
Networking lets users at different sites exchange voice messages on a network connected by
Transmission Control Protocol/Internet Protocol (TCP/IP). Digital Networking uses Simple Mail
Transfer Protocol (SMTP) to exchange the messages.
Note: Any voice message that you send over the Internet using Digital Networking can
be subject to interception by unauthorized parties.
How Digital Networking works
Digital Networking provides voice messaging to mailboxes at different sites on a network. Each
Avaya CallPilot site on the network must have Digital Networking installed to send, receive or
reply to network messages.
Network voice messaging occurs between mailboxes at different sites. For example, a message
recorded at an office in Miami, Florida can be transferred directly to the appropriate mailbox in
Vancouver, British Columbia.
Each site on a network is assigned a unique Fully Qualified Domain Name (FQDN). The FQDN
distinguishes a site from every other site on the network. An FQDN is the full name of the site,
including all subdomain and domain names, separated by periods. For example,
arabians.horse.com is an FQDN.
If you use Digital Networking and you do not use DNS to resolve domain names, you can
configure your system and client computers to use an IP address only. How to do this is explained
in Chapter 2.
Note: CallPilot for Avaya BCM will accept network wide and site specific VPIM
broadcast messages from M1 CallPilot. Upon acceptance, CallPilot for BCM
delivers the network wide broadcast message to all local recipients as if the
administrator had used F981, compose and send, to send the message.
NN40090-301NN40090-301
CallPilot also accepts site specific VPIM broadcast messages for delivery, if the
VPIM prefix in the message address matches the local mailbox prefix (defined in
CallPilot Manager Digital Networking Properties Page).
You cannot send network wide or site specific VPIM broadcast messages.
Chapter 1 Getting started 11
Setting up Avaya BCM and M1CallPilot for VPIM broadcast messages
To set up the Avaya BCM so remote M1 Callpilot broadcast messages are accepted and delivered
to BCM's local subscribers:
• Enable Network Receive. If not enabled, the remote M1 site will receive a Service Not
Available (SMTP reply 421) nondelivery notification upon attempting to send a broadcast
message to the BCM.
• Add the M1 site to the site list on the BCM. You need to know the FQDN of the M1 site, and
its site prefix in the network. If you do not add the M1 site to the BCM, the remote M1 site will
receive a Service Not Available (SMTP reply 421) nondelivery notification when attempting
to send a broadcast message to the BCM. Also, the BCM can only receive G726 voice
encoded messages from M1 CallPilot.
To set up M1 CallPilot to send network and site specific broadcast messages:
• Ensure you have M1 Callpilot version 2.0 or above. Versions prior to 2.0 do not support
network wide and site specific broadcast to BCMs. For additional information, see the
CallPilot Network Planning Guide (555-7101-102).
About AMIS
Audio Messaging Interchange Specification (AMIS) provides voice messaging to mailboxes at
different sites on a communication network. A network is a collection of offices, locations or sites
connected by telecommunication links. Each site on the network must have AMIS to send, receive
and reply to network messages. Direct AMIS addressing lets local subscribers send a voice
message to any subscriber inside or outside the company who has an AMIS voice mail address.
Network voice messaging occurs between mailboxes at different sites. For example, a message
recorded at an office in Cleveland, Ohio can be transferred directly to the appropriate mailbox at
an office in Toronto, Ontario.
AMIS networking uses ordinary telephone lines to exchange voice messages. An AMIS address
consists of a telephone number and a mailbox number.
Note: AMIS calls can incur long distance charges.
Ways of sending network messages
With Message Networking subscribers can send network messages to any supported site on the
network. Sites must have Network Receive enabled to receive network messages.
Subscribers can send network messages using:
• Site-Based Addressing
• Network Delivery Mailboxes
CallPilot Message Networking Set Up and Operation Guide
12 Chapter 1 Getting started
• Direct Addressing
Note: For information about sending messages using Site-Based Addressing, Network
Delivery Mailboxes or Direct Addressing see the CallPilot Message Networking User
Guide.
Site-Based Addressing
Use site-based addressing to set up a formal network of sites. Site-Based Addressing lets callers
send a message to other locations. Local subscribers can send messages to subscribers at a remote
site using an address that is the same as the recipient’s phone number. Your site-based addressing
can match your organization’s telephone network addressing.
Network Delivery Mailboxes
Network Delivery Mailboxes let local subscribers send a voice message to another subscriber
using what appears to be a local mailbox. Each Network Delivery Mailbox has a local mailbox
number and the destination site subscriber’s name appears in the local company directory.
When callers send a message to Network Delivery Mailboxes, they record a message and select
the Network Delivery Mailbox number. CallPilot sends the message to the specified network
address and mailbox.
For example, you can set up mailbox 5656 as a Network Delivery Mailbox. You add the Network
Delivery Mailbox to your Avaya CallPilot system and specify the site prefix and destination
mailbox 450 at the destination site. Each time a CallPilot subscriber accesses mailbox 5656 at your
site, CallPilot knows it is a message intended for mailbox 450 at another location and
automatically delivers it.
Network Delivery Mailboxes can also appear in the Company Directory, although only a
subscriber can select a Network Delivery Mailbox. Callers who are not subscribers on your Avaya
CallPilot system cannot access Network Delivery Mailboxes.
Direct Addressing
With Direct Addressing subscribers can send a voice message to a mailbox at a different location
on a network. To use Direct Addressing you must know the destination site’s phone number and
the mailbox number of the person you want to send a message to. Direct Addressing is available
for AMIS only.
Assigning Message Networking to subscribers
You assign Message Networking to subscribers through the mailbox Class of Service. Any
subscriber with an initialized mailbox, and the appropriate Class of Service, can use Message
Networking. For information on Class of Service values see the CallPilot Manager Set Up and
Operation Guide.
NN40090-301NN40090-301
Audience
This is guide is for system administrators you maintain and configure CallPilot on an Avaya
Business Communications Manager. To use this guide you must be an authorized system
administrator.
Acronyms
The following is a list of acronyms used in this guide.
Table 1
Acronym Description
AMIS Audio Messaging Interchange Specification
BCM Avaya Business Communications Manager
CCR Custom Call Routing
DNS Domain Name System
FQDN Fully Qualified Domain Name
SMTP Simple Mail Transfer Protocol
VPIM Voice Profile Internet Mail
Chapter 1 Getting started 13
CallPilot Message Networking Set Up and Operation Guide
14 Chapter 1 Getting started
Symbols and text conventions
These symbols are used to Highlight critical information for the Avaya BCM system:
Caution: Alerts you to conditions where you can damage the equipment.
Danger: Alerts you to conditions where you can get an electrical shock.
Warning: Alerts you to conditions where you can cause the system to fail or work
improperly.
Note: A Note alerts you to important information.
Tip: Alerts you to additional information that can help you perform a task.
Security note: Indicates a point of system security where a default should be changed,
or where the administrator needs to make a decision about the level of security required
!
for the system.
Warning: Alerts you to ground yourself with an antistatic grounding
strap before performing the maintenance procedure.
Warning: Alerts you to remove the BCM main unit and expansion unit
power cords from the ac outlet before performing any maintenance
procedure.
NN40090-301NN40090-301
Chapter 1 Getting started 15
These conventions and symbols are used to represent the Business Series Terminal display and
dialpad.
Convention Example Used for
Word in a special font (shown in
the top line of the display)
Underlined word in capital letters
(shown in the bottom line of a two
line display telephone)
Dialpad buttons
Pswd:
PLAY
£
Command line prompts on display telephones.
Display button option. Available on two-line display
telephones
option on the display to proceed.
Buttons you press on the dialpad to select a
particular option.
. Press the button directly below the
These text conventions are used in this guide to indicate the information described.
Convention Description
bold Courier
text
Indicates command names and options and text that you need to enter.
Example: Use the
Example: Enter
info command.
show ip {alerts|routes}.
italic text Indicates book titles
plain Courier
text
Indicates command syntax and system output (for example, prompts
and system messages).
Example:
Set Trap Monitor Filters
FEATURE
HOLD
RELEASE
Related Publications
This section provides a list of additional documents referred to in this guide.
CallPilot Manager Set Up and Operation Guide (NN40090-300)
CallPilot Reference Guide (NN40090-100)
CallPilot Message Networking User Guide (NN40090-101)
CallPilot Quick Reference Card - CP Interface (NN40090-102)
CallPilot Quick Reference Card - NVM Interface (NN40090-103)
CallPilot Quick Reference Card - Remote Users (CP Interface) (NN40090-104)
CallPilot Quick Reference Card - Remote Users (NVM Interface) (NN40090-105)
Indicates that you press the button with the coordinating icon on
whichever set you are using.
CallPilot Message Networking Set Up and Operation Guide
16 Chapter 1 Getting started
Customer Service
Visit the Avaya Web site to access the complete range of services and support that Avaya
provides. Go to http://www.avaya.com/support or go to one of the pages listed in the following
sections.
Navigation
• “Getting technical documentation” on page 16
• “Getting product training” on page 16
• “Getting help from a distributor or reseller” on page 16
• “Getting technical support from the Avaya Web site” on page 16
Getting technical documentation
To download and print selected technical publications and release notes directly from the Internet,
go to http://www.avaya.com/support.
Getting product training
Ongoing product training is available. For more information or to register, you can access the Web
site at http://www.avaya.com/support. From this Web site, you can locate the Training contacts
link on the left-hand navigation pane.
Getting help from a distributor or reseller
If you purchased a service contract for your Avaya product from a distributor or authorized
reseller, contact the technical support staff for that distributor or reseller for assistance.
Getting technical support from the Avaya Web site
The easiest and most effective way to get technical support for Avaya products is from the Avaya
Technical Support Web site at http://www.avaya.com/support.
NN40090-301NN40090-301
Chapter 2
Setting up Digital Networking
Setting the Digital Networking properties
Setting up Network properties involves entering your site’s:
• SMTP proxy name, if applicable
• local prefix
• Fully Qualified Domain Name (FQDN) or IP address
SMTP proxy name
Before you can use Digital Networking, you must find out from the Network Administrator
whether the network has an SMTP proxy. SMTP proxies restrict access to a company’s internal
network from the Internet. A proxy provides network security and prevents unauthorized access.
If your network has a direct connection to the internet or intranet, it does not have an SMTP proxy
and you do not have to enter an SMTP proxy name. If your network has an SMTP proxy, you must
enter the domain name of the SMTP proxy of your site. Contact your Network Administrator for
more information.
17
The FQDN of the SMTP proxy can be a maximum of 128 alphanumeric characters. The domain
name cannot have any spaces or punctuation except for characters such as periods, dashes or
underscores that are part of the name.
Local prefix
Before your site can receive messages from other sites, you must enter a local prefix for your site.
The local prefix is the sequence of digits that must be prefixed to local mailbox numbers to make
them unique across your network. The prefix is usually the same as your site prefix in the network
numbering plan.
The local prefix is a number from one to nine digits. This prefix can be the same as your site’s area
code and three-digit exchange prefix. For example, if customers dial 403-246-xxxx to reach your
site, 403246 can be your local prefix.
You must give your local prefix number to the Network Administrator and System Administrator
at each digital site. If you change it, give them your new prefix. They can update your local prefix
in their Site Tables.
FQDN
The FQDN is the domain name used for referring to your site, and is added to all outgoing
messages. For example, avaya.com is a domain name.
CallPilot Message Networking Set Up and Operation Guide
18 Chapter 2 Setting up Digital Networking
To set the Digital Networking properties
1 Start Avaya CallPilot Manager.
2 Click the Networking heading.
3 Click the Digital Networking Properties link.
The Digital Networking Properties page appears.
4 In the Local Prefix box type the local prefix.
5 In the SMTP Proxy Name box type the SMTP Proxy Name.
6 The IP Address and Domain Name are read-only. If you use a DNS your system displays the
domain name and IP address. If you do not use a DNS the IP address is displayed.
7 Click Submit.
Configuring your system network properties
Configuring your system network properties involves setting up message networking according to
whether you use a DNS server, host names or IP addresses.
Note: It is recommend that you use a DNS server. If you use an Avaya Business
Communications Manager (Avaya BCM) system and all of the digital sites in your
network use DNS, go to “Creating a network site” on page 40.
When you send a digital networking message, the internet uses the Domain Name System (DNS)
to translate domain names into IP addresses. Domain names, such as www.example.com, are
alphabetic, so they are easy for subscribers to remember. However, the internet is based on IP
addresses, which are numbers such as 198.105.232.4. Every time you use a domain name, a DNS
server translates the name into the corresponding IP address. For example, the domain name
www.example.com can translate to 198.105.232.4.
If you do not use domain names, the internet uses IP addresses. If you use IP addresses your
system does your name mapping for you. Some businesses do not use DNS servers, for example, if
they have a private network.
Configuring your system if you do not use DNS
Digital networking requires consistent name mapping throughout the network of digital sites. The
best way to provide name mapping is by using a DNS server. If you do not use a DNS server you
can use either a hosts file or IP addresses.
If your network contains only Avaya BCM systems you can use IP addresses and do not have to
use hosts files.
If your network contains sites other than BCM digital sites, you must use hosts files if you do not
use a DNS server.
NN40090-301NN40090-301
Chapter 2 Setting up Digital Networking 19
If you use BCM as a gateway to an internet service provider and DNS servers cannot provide name
resolution for the BCM or other digital sites, you must use hosts files to provide consistent name
mapping throughout the network.
You must do your system network configuration before you can add network sites. You can test
your system’s name mapping with ping and nslookup commands.
CallPilot Message Networking Set Up and Operation Guide
20 Chapter 2 Setting up Digital Networking
If DNS is not available you must do one of the following:
• If your digital network contains sites with sites other than BCM, you must use a hosts file to
provide consistent name mapping throughout the VPIM network.
Note: You can use a hosts file in combination with DNS in situations where DNS
is not available in all branch locations.
• If your digital network contains, and will only contain, BCM sites, you can use IP addresses to
create network sites. Refer to “To configure Avaya BCM to use IP addresses” on page 20 to
create network sites using IP addresses.
Note: The DNS servers must provide constant name mapping throughout the network.
Host files can be used to augment DNS if necessary. An instance where both hosts files
and DNS may be required is when a BCM is used as a gateway between a private
network and an ISP.
To configure Avaya BCM to use IP addresses
1 Ensure no DNS servers are currently configured. Refer to “To check that Avaya BCM is not
configured to use DNS” on page 21.
2 Enter the host name on the Avaya Business Communications Manager system. Refer to “To
check that a Host Name is entered on the Avaya BCM” on page 21.
3 Configure computers running Message Networking with the IP address of the Avaya Business
Communications Manager system.
Note: If you are using an Avaya Business Communications Manager system, you can
view the IP addresses of your system in Business Element Manager on the Domain
Name Service screen.
NN40090-301NN40090-301
Chapter 2 Setting up Digital Networking 21
To check that Avaya BCM is not configured to use DNS
Note: Ensure the Avaya BCM is using a static IP address and DHCP is disabled.
1 Start Business Element Manager.
2 On the Configuration tab, choose the Data Services folder.
The system tasks appear.
3 Choose the DNS task.
The Domain Name Service tab appears.
4 Ensure that the Enable DNS box is not selected.
5 Ensure that the Primary (& Sec.) Server IP Addr field is empty. If it is not, delete any
entries.
To check that a Host Name is entered on the Avaya BCM
1 Start Business Element Manager.
2 On the Configuration tab, choose the System folder.
The system tasks appear.
3 Choose the Identification task.
The System Identification tab appears.
4 Enter a system name in the System Name box, if one is not entered.
A system name can be any name (for example, myCompany).
To change your local CallPilot Host name or IP address
1 Make the change to the host name or IP address first.
2 Create a hosts file, making sure that the new host name is the first entry in the hosts file.
3 FTP the hosts file to your Avaya CallPilot’s 7.0/ST directory. You must FTP the file using the
ASCII format, NOT binary. If you use binary the hosts file will not work. The FTP login and
password for CallPilot are as follows:
• FTP user ID: tas
• FTP password: apo A-IV
4 Reboot Avaya CallPilot for the new settings to take effect.
CallPilot Message Networking Set Up and Operation Guide
Loading...