15. Overview
About this book
Overview
Avaya Communication Manager is the centerpiece of Avaya applications. Running on a variety
of Avaya S8XXX Servers and DEFINITY Servers, and providing control to Avaya Media
Gateways and Avaya communications devices, Communication Manager can be designed to
operate in either a distributed or networked call processing environment.
Communication Manager carries forward all of a customer’s current DEFINITY capabilities, plus
offers all the enhancements that enable them to take advantage of new distributed
technologies, increased scalability, and redundancy. Communication Manager evolved from
DEFINITY software and delivers no-compromise enterprise IP solutions.
Communication Manager is an open, scalable, highly reliable and secure telephony application.
The software provides user and system management functionality, intelligent call routing,
application integration and extensibility, and enterprise communications networking.
Purpose of this book
This book describes the procedures and screens used in administering the most recent release
of Communication Manager running on any of the following:
●
Avaya S8XXX Servers
- DEFINITY servers
- S8100, S8300, S8400, S8500, or S87XX Servers
●
Avaya S8XXX Servers configured as a Local Survivable Processor (LSP).
●
Avaya media gateways
- MCC1 or SCC1 Media Gateways
- G250, G350, G600, G650, or G700 Media Gateways
Newer releases of Communication Manager contain all the features of prior releases.
Intended audience
This document is intended for system administrators and managers, for users interested in
information about specific features, and Avaya personnel responsible for planning, designing,
configuring, selling, and supporting the system.
Issue 4.0 January 2008
15
16. About this book
Contents
This document includes the following chapters:
●
Chapter 1: System Basics tells you how to log in and log off, set permissions for others
who use the administration terminal, set daylight savings rules, set the system date and
time, post messages, and back up the information you administer.
●
Chapter 2: Planning the System provides information on system-wide functions. It explains
how to read, use, and make simple changes to your dial plan, and how to assign feature
access codes.
●
Chapter 3: Managing Telephones explains how to add, swap, and remove telephones, and
how to customize a telephone, for Communication Manager administrators.
●
Chapter 4: Managing Telephone Features explains how to administer feature buttons for
your users’ telephones.
●
Chapter 5: Managing Attendant Consoles explains attendant console feature buttons, and
tells you how to change, move, or add attendant consoles.
●
Chapter 6: Managing Displays provides information on the messages that appear on the
read-out screen on display telephones.
●
Chapter 7: Handling Incoming Calls shows you how to set up call coverage for incoming
calls to be sure that incoming calls are answered when the called party is unavailable.
●
Chapter 8: Routing Outgoing Calls explains how Avaya Communication Manager handles
outgoing calls and tells you how to modify call restrictions and your routing plan.
●
Chapter 9: Managing Multimedia Calling describes the Multimedia Applications Server
Interface (MASI), and provides instructions on administration, monitoring, and
troubleshooting. This section also provides information on Multimedia Call Handling
(MMCH), which enables users to control voice, video, and data transmissions using a
telephone and PC.
●
Chapter 10: Setting Up Telecommuting provides information on system-wide settings and
individual user administration for telecommuting.
●
Chapter 11: Enhancing System Security provides information on analyzing and setting up
basic system security, preventing toll fraud, using logins and permissions and passwords,
and dealing with security violations.
●
Chapter 12: Managing Trunks contains procedures for working with analog and digital
trunks. Specialized trunks such as APLT, tandem, release-link, DMI-BOS and ISDN trunk
groups are not covered in this manual.
●
Chapter 13: Managing Announcements tells you how to record, save, copy, restore and
delete announcements.
16 Administrator Guide for Avaya Communication Manager
17. Conventions used
●
Chapter 14: Managing Group Communications shows you how to administer your system
so users can page other users or use their telephones as intercoms. You can also give
specific users permission to monitor other users’ calls or to interrupt active calls with
important messages.
●
Chapter 15: Managing Data Calls describes the system features available to enable data
communications.
●
Chapter 16: Administering Avaya Servers describes how to administer an Avaya S87XX
Server and an Avaya G700 Media Gateway and the Avaya S8300 Server.
●
Chapter 17: Collecting Call Information provides information on account codes, and on
tracking and collecting billing information about calls.
●
Chapter 18: Telephone Reference describes many of the telephones that you can connect
to Communication Manager. It also describes the unique features and buttons for each
telephone series to help you administer your user telephones.
●
Chapter 19: Screen Reference provides a brief description and a graphic representation of
the Communication Manager screens used for administration. It also lists the valid values
for fields on the screens, and describes when and why to use each value.
Conventions used
Become familiar with the following terms and conventions. They help you use this book with
Communication Manager.
●
A “screen” is the display of fields and prompts that appear on a terminal monitor.
See the Screen Reference chapter for an example of a screen and how it is shown in this
book.
●
We use the term “telephone” in this book. Other Avaya books might refer to telephones as
phones, voice terminals, stations, or endpoints.
●
Keys and buttons are printed in a bold font: Key.
●
Titles of screens are printed in a bold font: Screen Name.
●
Names of fields are printed in a bold font: Field Name.
●
Text (other than commands) that you need to type into a field are printed in a bold font:
text.
●
Commands are printed in a bold constant width font: command.
●
Variables are printed in a bold constant width italic font: variable.
●
We show complete commands in this book, but you can always use an abbreviated
version of the command. For example, instead of typing list configuration
station, you can type list config sta.
Issue 4.0 January 2008
17
18. About this book
●
If you need help constructing a command or completing a field, remember to use Help.
- When you press Help at any point on the command line, the system displays a list of
available commands.
- When you press Help with your cursor in a field on a screen, the system displays a list of
valid entries for that field.
●
Messages that the system displays are printed in a constant width font: system message.
●
To move to a certain field on a screen, you can use the Tab key, directional arrows, or the
Enter key on your keyboard.
●
If you use terminal emulation software, you need to determine what keys correspond to
Enter, Return, Cancel, Help, and Next Page keys.
●
We show commands and screens from the newest release of Communication Manager. If
your system has an older version of Communication Manager installed, substitute the
appropriate commands for your system and see the manuals you have available.
●
The status line or message line can be found near the bottom of your monitor. This is
where the system displays messages for you. Check the message line to see how the
system responds to your input. Write down the message if you need to call the helpline.
●
When a procedure requires you to press Enter to save your changes, the screen clears.
The cursor returns to the command prompt. The message line shows “command
successfully completed” to indicate that the system accepted your changes.
Admonishments
Admonishments that might appear in this book have the following meanings:
Note:
Note:
Draws attention to information that you must heed.
Tip:
Draws attention to information that you might find helpful.
Tip:
! CAUTION:
Denotes possible harm to software, possible loss of data, or possible service
interruptions.
CAUTION:
!
WARNING:
WARNING:
Denotes possible harm to hardware or equipment.
! DANGER:
DANGER:
Denotes possible harm or injury to your body.
18 Administrator Guide for Avaya Communication Manager
19. Trademarks
!
SECURITY ALERT:
SECURITY ALERT:
Denotes when system administration might leave your system open to toll fraud.
Trademarks
All trademarks identified by ® or ™ are registered trademarks or trademarks, respectively, of
Avaya, Inc. All other trademarks are the property of their respective owners.
Related Resources
The following documents provide additional information.
Administration for Network Connectivity for Avaya Communication Manager, 555-233-504
ATM Installation, Upgrades, and Administration using Avaya Communication Manager,
555-233-124
Avaya Application Solutions -- IP Telephony Deployment Guide, 555-245-600
Avaya Business Advocate User Guide, 07-300653
Avaya Call Center Release 4.0 Automatic Call Distribution (ACD) Guide, 07-600779
Avaya Call Center Release 4.0 Call Vectoring and Expert Agent Selection (EAS) Guide,
07-600780
Avaya Communication Manager Advanced Administration Quick Reference, 03-300364
Avaya Communication Manager Basic Administration Quick Reference, 03-300363
Avaya Communication Manager Basic Diagnostics Quick Reference, 03-300365
Avaya Remote Feature Activation (RFA) User Guide, 03-300149
Avaya Toll Fraud and Security Handbook, 555-025-600
Converged Communications Server Installation and Administration, 555-245-705
DEFINITY Communications Systems Generic 2.2 and Generic 3 Version 2 DS1/CEPT1/ISDN
PRI Reference, 555-025-107
DEFINITY Enterprise Communications Server Release 1.1 Getting Started with the Avaya R300
Remote Office Communicator, 555-233-769
Feature Description and Implementation for Avaya Communication Manager, 555-245-205
Hardware Description and Reference for Avaya Communication Manager, 555-245-207
Installation, Upgrades and Additions for Avaya CMC1 Media Gateways, 555-233-118
Issue 4.0 January 2008
19
20. About this book
Maintenance Alarms for Avaya Communication Manager, Media Gateways and Servers,
03-300430
Maintenance Commands for Avaya Communication Manager, Media Gateways and Servers,
03-300431
Maintenance Procedures for Avaya Communication Manager, Media Gateways and Servers,
03-300432
Overview for Avaya Communication Manager, 03-300468
Reports for Avaya Communication Manager, 555-233-505
System Capacities Table for Avaya Communication Manager on Avaya Media Servers,
03-300511
Using the Avaya Enterprise Survivable Servers (ESS), 03-300428
What’s New in Avaya Communication Manager, 03-300682
For documents not listed here, go to http://www.avaya.com. Select Support and then Product
Documentation.
How to obtain Avaya books on the Web
If you have internet access, you can view and download the latest version of Avaya
documentation products. To view any book, you must have a copy of Adobe Acrobat Reader.
Note:
Note:
If you don’t have Acrobat Reader, you can get a free copy at
http://www.adobe.com.
For example, to access an electronic version of this book:
1. Access the Avaya Web site at http://www.avaya.com/support/.
2. Click Product Documentation.
3. To find a specific book, type the document number (for example, 03-300509 for this book) in
the Search Support text box, and then click GO.
4. In the resulting list, locate the latest version of the document, and then click the document
title to view the latest version of the book.
How to comment on this book
Avaya welcomes your feedback. Contact us through:
20 Administrator Guide for Avaya Communication Manager
21. How to get help
●
e-mail: document@avaya.com
●
fax: 1-303-538-1741
●
Contact your Avaya representative
Mention this document’s name and number, Administrator Guide for Avaya Communication
Manager, 03-300509.
Your comments are of great value and help improve our documentation.
How to get help
If you suspect that you are being victimized by toll fraud and you need technical assistance or
support in the United States and Canada, call the Technical Service Center's Toll Fraud
Intervention Hotline at 1-800-643-2353.
If you need additional help, the following resources are available. You might need to purchase
an extended service agreement to use some of these resources. See your Avaya
representative for more information.
Go to the Avaya Web site at http://www.avaya.com/support:
●
If you are within the United States, click the Escalation Management link. Then click the
appropriate link for the type of support you need.
●
If you are outside the United States, click the Escalation Management link. Then click
International Services, which includes telephone numbers for the international Centers of
Excellence. Or contact your local Avaya authorized dealer for any additional help and
questions.
Issue 4.0 January 2008
21
23. Chapter 1: System Basics
Logging into the System
You must log in before you can administer your system. If you are performing remote
administration, you must establish a remote administration link and possibly assign the remote
administration extension to a hunt group before you log in. The members of this hunt group are
the extensions of the data modules available to connect to the system administration terminal.
For information about setting up remote administration, contact your Avaya technical support
representative. When not using the system, log off for security purposes.
Logging in from a system terminal
This procedure provides instructions for logging in from a system terminal, not a remote
terminal.
To log into the system:
1. Enter your login name. Press Enter.
2. Enter your password. Press Enter.
For security, your password does not display as you type it.
3. Enter the kind of terminal you have or the type your system emulates. Press Enter.
The Command prompt displays.
Note:
Note:
If you enter the wrong terminal type, it can lock up your system. If the system is
not responding to keyboard commands, type newterm. Press Enter. Enter the
correct terminal type on the new screen. Press Enter. If this does not work, turn
the power off only on the terminal and then turn it back on. The terminal reboots
and you can log in again.
Issue 4.0 January 2008
23
24. System Basics
Logging in for remote administration
To log in for remote administration:
1. Dial the Uniform Call Distribution (UCD) group extension number.
Note:
The UCD group extension number is assigned when you set up remote
administration.
Note:
●
If you are off-premises, use the Direct Inward Dialing (DID) number, a Listed Directory
Number (LDN) (you must use a telephone), or the trunk number dedicated to remote
administration.
●
If you are on-premises, use an extension number.
If you dialed a DID number, dedicated trunk number, or extension, you receive data tone
or visually receive answer confirmation.
If an LDN was dialed, the attendant will answer.
a. Ask to be transferred to the UCD group extension number.
You receive data tone or visually receive answer confirmation.
b. Transfer the voice call to your data terminal.
The Login prompt displays.
2. Complete the steps for Logging into the System on page 23.
For information about setting up remote administration, contact your Avaya technical
support representative.
See also Chapter 11: Enhancing System Security. For a complete description of the Security
Violation Notification feature, see "Security Violation Notification" in Feature Description and
Implementation for Avaya Communication Manager, 555-245-205.
Accessing the Avaya S8XXX Server
To administer an Avaya S8XXX Server, you must be able to access it. Personal computers and
services laptop computers equipped with a network PCMCIA card, Avaya Site Administration
(ASA), and a Web browser are the primary support access for system initialization, aftermarket
additions, and continuing maintenance.
You can access an Avaya S8XXX Server in one of three ways:
●
directly
●
remotely over the customer’s local area network (LAN)
●
over a modem
24 Administrator Guide for Avaya Communication Manager
25. Logging into the System
A direct connection and over the customer’s LAN are the preferred methods. Remote access
over a modem is for Avaya maintenance access only.
Accessing the Avaya S8XXX Server Directly
You can access an Avaya S8XXX Server directly by plugging a computer into the services port
which defaults to port 2 (Eth1) on the back of the server. You must use a crossover cable with
an RJ45 connector on each end. Plug the other end into the network connector (NIC card) on
the your computer. You might need a NIC card adapter.
Once connected, you can administer the server using three tools:
●
Web interface for server-specific administration.
●
ASA for various features of Avaya Communication Manager
●
An SSH client, like PuTTY, and an IP address of 192.11.13.6.
Web Interface - You can access the server Web interface either by connecting directly to the
services port on the Avaya S8XXX Server, or by connecting over the customer network.
Connected to the services port - To use the server Web interface:
1. Open either the Netscape or MS Internet Explorer browser.
2. In the Location/Address field, type 192.11.13.6. Press Enter.
3. When prompted, log in to administer the Avaya S8XXX Server and the features of Avaya
Communication Manager.
Connected to the customer network - To use the server Web interface:
1. Open either the Netscape or MS Internet Explorer browser.
2. In the Location/Address field, type the active server name or IP address. Press Enter.
3. When prompted, log in to administer the Avaya S8XXX Server and the features of Avaya
Communication Manager.
You can also connect directly to an individual server using its name or IP address.
Accessing the Avaya S8XXX Server remotely over the network
You can access the Avaya S8XXX Server from any computer connected through the LAN. To
access either server, use the IP address assigned to the server you want to access. You can
also use the active server address to connect automatically to the server that is active. Once
connected, you can administer the server using three tools:
●
Web interface for server-specific administration and call processing features
●
Avaya Site Administration for Communication Manager (Only available on the active
Communication Manager server)
●
An SSH client, like PuTTY, and an IP address of 192.11.13.6.
Issue 4.0 January 2008
25
26. System Basics
Using Avaya Site Administration
Avaya Site Administration features a graphical user interface (GUI) that provides access to SAT
commands as well as wizard-like screens that provide simplified administration for frequently
used features. You can perform most of your day-to-day administration tasks from this interface
such as adding or removing users and telephony devices. You can also schedule tasks to run at
a non-peak usage time. ASA is available in several languages.
The S8300, S8400, or S87XX Server can be used to download Avaya Site Administration. A
downloadable version of this package can be accessed through the S8300, S8400, or S87XX
Server Web Interface. This software must be installed on a computer running a compatible
Microsoft Windows operating system such as Windows 95, 98, NT 4.0, Millennium Edition,
Windows 2000, or Windows XP. Once installed, it can be launched from a desktop icon, from
the P330 Device Manager, or through a link in the S8300 Server Web Interface.
Installing Avaya Site Administration
If you do not have ASA on your computer, make sure your personal computer (PC) or laptop
first meets the following minimum requirements:
Operating systems
Processor/RAM
Windows 2000
Windows XP
2003 (Standard and
Enterprise)
Pentium-class 300 MHz/64 MB
Pentium-class 300 MHz/64 MB
Pentium-class 300 MHz/64 MB
Graphics adapter
SVGA with minimum screen resolution of
800 x 600
Floppy disk drive
3-1/2 in. 1.44-MB floppy disk drive
CD-ROM
CD-ROM drive (required to install ASA
from CD)
Available hard disk space
A minimum of 100-MB free hard disk space
is required. The requirement for disk space
depends on the size and number of
configuration data sets.
Printer port
Standard PC or network printer port is
required for connecting to a printer to
produce station button labels.
26 Administrator Guide for Avaya Communication Manager
27. Logging into the System
Operating systems
Processor/RAM
Network adapter
Required for network access to the S87XX
Server, AUDIX, and other
network-connected systems.
Free serial ports
One free serial port capable of 9600-bps
operation is required for a connection to
each serial device (UPS).
Avaya recommends that PCs have at least
a 16550A UART or 16550A UART
simulator (capable of 56 kbps DTE-speed
connections). USB and internal modems
should emulate this hardware.
A second serial port is required for
simultaneous connection to AUDIX through
a serial connection.
Install ASA on your computer using the Avaya Site Administration CD. Place the ASA CD in the
CD-ROM drive and follow the installation instructions in the install wizard.
ASA supports a terminal emulation mode, which is directly equivalent to using SAT commands
on a dumb terminal or through an SSH session. ASA also supports a whole range of other
features, including the graphically enhanced interface (GEDI) and Data Import. For more
information see the Help, Guided Tour, and Show Me accessed from the ASA Help menu.
Starting Avaya Site Administration
To start ASA:
1. Start up ASA by double-clicking the ASA icon, or click Start>Programs>Avaya Site
Administration.
2. In the Target System field, use the pull-down menu to select the desired system.
3. Click Start GEDI.
You now are connected to the desired system.
Configuring Avaya Site Administration
When Avaya Site Administration is initially installed on a client machine, it needs to be
configured to communicate with Communication Manager on the Avaya S8XXX Server.
When you initially run ASA, you are prompted to create a new entry for the switch connection.
You are also prompted to create a new voice mail system if desired.
Issue 4.0 January 2008
27
28. System Basics
Adding a Switch Administration Item
To add a switch administration item:
1. Click File > New > Voice Mail System.
The system displays the Add Voice Mail System screen.
2. Enter a name in the Voice Mail System Name field.
3. Click Next. The connection type dialog box displays.
4. Click the Network connection radio button.
5. Click Next. The Network Connection dialog box displays.
6. Enter the IP address used to connect to the Avaya S8XXX Server.
7. Click Next. The Network Connection/Port Number dialog box displays.
8. In the TCP/IP Port Number field, enter port 5023.
9. Click Next. The Network Connection/Timeout Parameters dialog box displays. Leave the
default values for the timeout parameters.
10. Click Next. The login type dialog box displays.
11. Click the "I want to login manually each time" radio button.
12. Click Next. The Voice Mail System Summary dialog box displays.
13. Check the information, use the Back button to make corrections if necessary, and click the
Test button to test the connection.
14. When the connection is successfully tested, click Next and then Finish.
Note:
Note:
In order for ASA to work properly with the ASG Guard II, the Write (ms) field on
the Advanced tab of the Connection Properties screen must be set to a value
of 5 (i.e., delay of 5 ms). ASG Guard II is an outboard appliance providing access
security for Avaya products that do not have Access Security Gateway (ASG)
software as a native application. For more information on ASG Guard II, contact
your Avaya technical support representative.
Adding a new voice system
When you initially run ASA, you are prompted to create a new entry for the switch
connection if you have not already done so. To set up the desired system, click the New
VOICE SYSTEM icon (on the left of the toolbar row). Complete the Add Voice System
wizard to build the system record. When completed, the record will be available in the
Target System pull-down list.
28 Administrator Guide for Avaya Communication Manager
29. Logging into the System
Logging in with Access Security Gateway
Access Security Gateway (ASG) is an authentication interface used to protect the system
administration and maintenance ports and logins associated with Avaya Communication
Manager. ASG uses a challenge and response protocol to validate the user and reduce
unauthorized access.
You can administer ASG authentication on either a port type or login ID. If you set ASG
authentication for a specific port, it restricts access to that port for all logins. If you set ASG
authentication for a specific login ID, it restricts access to that login, even when the port is not
administered to support ASG.
Authentication is successful only when Avaya Communication Manager and the ASG
communicate with a compatible key. You must maintain consistency between the Access
Security Gateway Key and the secret key assigned to the Communication Manager login. For
more information about ASG, see Using Access Security Gateway (ASG) on page 459.
Before you can log into the system with ASG authentication, you need an Access Security
Gateway Key, and you need to know your personal identification number (ASG). The Access
Security Gateway Key must be pre-programmed with the same secret key (such as, ASG Key,
ASG Passkey, or ASG Mobile) assigned to the Avaya Communication Manager login.
Verify that the Access Security Gateway (ASG) field on the System-Parameters Customer
Options (Optional Features) screen is set to y. If not, contact your Avaya representative.
Logging in with ASG
To log into the system with ASG:
1. Enter your login ID. Press Enter.
The system displays the challenge number (for example, 555-1234) and system Product ID
number (for example, 1000000000). The Product ID provides Avaya Services with the
specific identifier of your Avaya MultiVantage communications application.
2. Press ON to turn on your Access Security Gateway Key.
3. Type your PIN. Press ON.
The Access Security Gateway Key displays a challenge prompt.
4. At the challenge prompt on the Access Security Gateway Key, type the challenge number
without the "-" character (for example, 5551234) from your screen. Press ON.
The Access Security Gateway Key displays a response number (for example, 999-1234).
5. At the response prompt on your terminal, type the ASG response number without the "-"
character (for example, 9991234). Press Enter.
The Command prompt displays.
Issue 4.0 January 2008
29
30. System Basics
Note:
If you make 3 invalid login attempts, the system terminates the session. For more
information, see the appropriate maintenance book for your system.
Note:
Login messages
Two messages may be displayed to users at the time of login.
●
The Issue of the Day message appears prior to a successful login. In general, use the
Issue of the Day to display warnings to users about unauthorized access. The client that is
used to access the system can affect when, how, and if the user sees the Issue of the Day
message.
●
The Message of the Day (MOTD) appears immediately after a user has successfully
logged in. In general, use the Message of the Day to inform legitimate users about
information such as upcoming outages and impending disk-full conditions.
Using the system default Issue of the Day
The Communication Manager file /etc/issue.avaya contains sample text that may be used for
the Issue of the Day message.
To use the system default Issue of the Day:
1. Log into the Communication Manager server and at the CLI enter
cp /etc/issue.avaya /etc/issue
cp /etc/issue.avaya /etc/issue.net
Setting Issue of the Day and Message of the Day
For more detailed information on setting login messages and interaction with individual access
services, see the See the Communication Manager Administrator Logins White Paper on
http://support.avaya.com/elmodocs2/white_papers/CM_Administrator_Logins.pdf.
In general, to administer the Issue of the Day and the Message of the Day, use
/bin/vi or
/usr/share/emacs to perform the following edits:
1. Configure etc/pam.d/mv-auth to include issue PAM module.
2. Edit /etc.issue and /etc.issue.net (if using telnet) to include the text for the Issue
of the Day.
30 Administrator Guide for Avaya Communication Manager
31. Logging off the System
3. Edit etc/motd to include the text for the Message of the Day.
Strings not permitted in a Message of the Day (case sensitive)
[513]
Software Version
Login:
incorrect login
513]
Password:
ogin
hallenge
]
assword
ogin:
SAT cannot be executed on a
standby server
SAT
Logging off the System
For security, log off any time you leave your terminal. If you use terminal emulation software to
administer Communication Manager, log off the system and exit the emulation application
before switching to another software package.
Instructions
To log off:
1. Type logoff. Press Enter.
If the Facility Test Call or Remote Access features are administered, Alarm origination is
disabled, or if you have busied out resources or active minor or major alarms, a security
screen displays. You might want to take appropriate action (for example, disable these
features or address any alarms) before you log off.
If none of the above special circumstances exist, the system logs you off.
Figure 1: Logoff screen
Facility Test Call Administered
Remote Access Administered
Alarm Origination is currently disabled
Active major/minor alarm detected; be sure to resolve it
Proceed with Logoff? [n]
Issue 4.0 January 2008
31
32. System Basics
2. At the Proceed with Logoff prompt, type y to log off.
If you log off with alarm origination disabled and the system generates an alarm, Avaya
support services will not receive any notification of the alarm. For more information about
alarms, see the maintenance book for your system.
Administering User Profiles and Logins
Authentication, Authorization and Accounting (AAA) Services allows you to store and maintain
administrator account (login) information on a central server. Login authentication and access
authorization is administered on the central server.
For details on administering user profiles and logins, see "AAA Services" in Feature Description
and Implementation for Avaya Communication Manager, 555-245-205, and Maintenance
Commands for Avaya Communication Manager, 03-300431.
Establishing Daylight Savings Rules
Avaya Communication Manager allow you to set the daylight savings time rules so that
features, such as time-of-day routing and call detail recording (CDR), adjust automatically to
daylight savings time. The correct date and time ensure that CDR records are correct. You can
set daylight savings time rules to transition to and from daylight savings time outside of normal
business hours, so the number of affected CDR records is small.
You can set up 15 customized daylight savings time rules. This allows Communication Manager
administrators with servers in several different time zones to set up a rule for each. A daylight
savings time rule specifies the exact time when you want to transition to and from daylight
savings time. It also specifies the increment at which to transition (for example, 1 hour).
32 Administrator Guide for Avaya Communication Manager
33. Establishing Daylight Savings Rules
Instructions
Establishing daylight savings rules
To modify a daylight savings rule:
1. Type change daylight-savings-rules. Press Enter.
The Daylight Savings Rules screen appears.
Figure 2: Daylight Savings Rules screen
change daylight-savings-rules
DAYLIGHT SAVINGS RULES
Rule
Change Day
0:
Start:
Stop:
Start:
Stop:
Start:
Stop:
Start:
Stop:
Start:
Stop:
Start:
Stop:
Start:
Stop:
Month
Date
Time____Increment
No Daylight Savings
1:
Page 1 of 2
2:
3:
4:
5:
6:
7:
first
first
first
first
first
first
first
first
first
first
first
first
first
first
_ Sunday_
_ Sunday_
_________
_________
_________
_________
_________
_________
_________
_________
_________
_________
_________
_________
on
on
on
on
on
on
on
on
on
on
on
on
on
on
or
or
or
or
or
or
or
or
or
or
or
or
or
or
after
after
after
after
after
after
after
after
after
after
after
after
after
after
_March
November
________
________
________
________
________
________
________
________
________
________
________
________
8_
1_
__
__
__
__
__
__
__
__
__
__
__
__
at
at
at
at
at
at
at
at
at
at
at
at
at
at
2:00_
2:00_
__:__
__:__
__:__
__:__
__:__
__:__
__:__
__:__
__:__
__:__
__:__
__:__
01:00__
Rule 1 applies to all time zones in the U.S. and begins on the first Sunday on or after March
8 at 2:00 a.m. with a 01:00 increment. Daylight Savings Time stops on the first Sunday on or
after November 1 at 2:00 a.m., also with a 01:00 increment (used as a decrement when
switching back to Standard time. This is the default.
The increment is added to standard time at the specified start time and the clock time shifts
by that increment (for example, for 01:59:00 to 01:59:59 the clock time shows 01:59 and at
02:00 the clock shows 03:00).
Issue 4.0 January 2008
33
34. System Basics
On the stop date, the increment is subtracted from the specified stop time (for example, for
01:59:00 to 01:59:59 the clock time shows 01:59 and at 02:00 the clock shows 01:00).
Note:
You cannot delete a daylight savings rule if it is in use on either the Locations or
Date and Time screens. However, you can change any rule except rule 0 (zero).
Note:
2. To add a Daylight Savings Time rule, complete the Start and Stop fields with the day,
month, date, and time you want the system clock to transition to Daylight Savings Time and
back to standard time.
3. Press Enter to save your changes.
Note:
Whenever you change the time of day, the time zone, or daylight savings rules,
you must reboot the server for the changes to take effect. See the documentation
for your system for information on rebooting the server.
Note:
Displaying daylight savings time rules
To display daylight savings time rules:
1. Type display daylight-savings-rules. Press Enter.
The Daylight Savings Rules screen appears. Verify the information you entered is correct.
Setting Time of Day Clock Synchronization
Time of Day Clock Synchronization enables a server to synchronize its internal clock to UTC
time provided by Internet time servers. Avaya uses the LINUX platform system clock connected
to an Internet time server to provide time synchronization. The interface for these systems is
web-based.
LINUX is used in:
●
Avaya S8XXX Server IP-PNC
●
Avaya S8XXX Server Fiber-PNC
●
Avaya S8XXX Server
Before you start:
●
A standard TCP/IP LAN connection is required to connect to the Internet time servers. If a
LAN connection is not available, time sync will be done by setting the platform clock
manually through the command line or web interface.
34 Administrator Guide for Avaya Communication Manager
35. Setting Time of Day Clock Synchronization
●
Note:
On the target server running Communication Manager, verify if Daylight Savings Time is
on.
Note:
These instructions are for Avaya DEFINITY CSI servers. For more information,
see Avaya Call Center Automatic Call Distribution (ACD) Guide, 07-600779.
To set Time of Day Clock Synchronization:
1. Activate the Avaya Site Administration screen.
2. Click the Fault & Performance tab.
The Fault & Performance icons display.
Figure 3: Avaya Site Administration menu
3. Click Time Synchronization.
The Time Synchronization - Properties screen displays.
Issue 4.0 January 2008
35
36. System Basics
Figure 4: Time Synchronization - Properties screen
4. Click in the Offset box.
The Plus and Minus radio buttons and the Hours and Minutes fields display.
5. Click Next.
The Time Synchronization - Properties screen displays.
36 Administrator Guide for Avaya Communication Manager
37. Setting Time of Day Clock Synchronization
Figure 5: Time Synchronization - Properties screen
6. Click Plus to add hours to the remote station (located to the west of the system time) or
click Minus to subtract hours to the remote station (located to the east of the system time).
7. In the hours field, enter the number of hours to be added or subtracted to synchronize with
the remote site.
8. Click Next.
The Time Synchronization - Schedule displays.
Issue 4.0 January 2008
37
38. System Basics
Figure 6: Time Synchronization - Schedule screen
9. Select either:
●
Run Now to run this program immediately and click Next.
●
Schedule this task to run and check the field below to determine if the default setting is
satisfactory. If this setting is not satisfactory, click Schedule.
The Scheduler screen displays.
38 Administrator Guide for Avaya Communication Manager
39. Setting Time of Day Clock Synchronization
Figure 7: Scheduler screen
10. In the Date field, highlight each object and use the pull-down menu to select the desired
setting.
11. In the Time field, highlight each item of time and use the pull-down menu to select the
desired time.
12. In the Recurrent Pattern area, select one radio button for the desired frequency. Notice
that each radio button is explained in the area to the immediate right.
13. If there are times to be included, set to the desired frequency.
14. Click OK.
The Time Synchronization - Schedule displays.
15. Click Next.
The Time Synchronization - Summary screen displays.
Issue 4.0 January 2008
39
40. System Basics
Figure 8: Time Synchronization - Summary screen
16. If the time synchronization description is satisfactory, click Finish.
If the time synchronization is not satisfactory, click Back and revise the necessary
information.
Note:
Note:
Whenever you change the time of day, the time zone, or daylight savings rules,
you must reboot the server for the changes to take effect. See the documentation
for your system for information on rebooting the server.
For more information about setting time synchronization, see Avaya Call Center Release 4.0
Automatic Call Distribution (ACD) Guide, 07-600779.
40 Administrator Guide for Avaya Communication Manager
41. Setting the System Date and Time
Setting the System Date and Time
Update the date and time for events such as a leap year, the change to or from daylight savings
time, or a system restart after a power failure. The correct date and time assure that Call Detail
Recording (CDR) records are correct. CDR does not work until the date and time have been
entered.
Note:
Note:
Changing the date and time can modify CDR data by 9 hours and 59 minutes.
Therefore, you should change the date and time after normal business hours.
After you change the date and time, review the time settings for any adjunct
(other than AUDIX) linked to your system that uses the system time.
Before you can set the date and time, you need to know whether it is currently daylight savings
or standard time and know which daylight savings rule number you want to use. Daylight
savings rule numbers are located on the Daylight Savings Rules screen.
In our example, we set the date and time to Tuesday, November 5, 2006 at 8:30 p.m. standard
time.
To set the system date and time:
1. Type set time. Press Enter.
The Date and Time screen displays.
Figure 9: Date and Time screen
set time
DATE AND TIME
DATE
Day of the Week: _______
Day of the Month: __
Month: ________
Year: ____
TIME
Hour: __ Minute: __
________________
Second: __
Type:
Daylight Savings Rule: _
WARNING: Changing the date or time may impact BCMS, CDR, SCHEDULED EVENTS,
and MEASUREMENTS
2. Complete the Date fields.
a. Type Tuesday in the Day of the Week field.
b. Type November in the Month field.
Issue 4.0 January 2008
41
42. System Basics
c. Type 5 in the Day of the Month field.
d. Type 2006 in the Year field.
3. Complete the Time fields.
Use the 24-hour clock to set the hour, so if the current time is 2:00 p.m., you enter 14:00.
You cannot update Second — it automatically resets to 0 when you save your changes.
a. Type 20 in the Hour field.
b. Type 30 in the Minute field (8:30 p.m.).
c. Type standard in the Type field.
d. Type 1 in the Daylight Savings Rule field.
4. Press Enter to save your changes.
Some display telephones might not automatically refresh the display when you change the
date or time. If this occurs, have each user press the date/time button on their telephone to
update the display.
Note:
Note:
Whenever you change the time of day, the time zone, or daylight savings rules,
you must reboot the server for the changes to take effect. See the documentation
for your system for information on rebooting the server.
Displaying the system date and time
To display the system date and time:
1. Type display time. Press Enter.
The Date and Time screen displays. Verify the information you entered is correct.
Related topics
See Establishing Daylight Savings Rules on page 32 for more information about setting system
time.
For additional information, see Avaya Call Center Release 4.0 Automatic Call Distribution
(ACD) Guide, 07-600779.
42 Administrator Guide for Avaya Communication Manager
43. Using the Bulletin Board
Using the Bulletin Board
Avaya Communication Manager allows you to post information to a bulletin board. You can also
display and print messages from other Avaya server administrators and Avaya personnel using
the bulletin board. Anyone with the appropriate permissions can use the bulletin board for
messages. Only one user can post or change a message at a time.
Whenever you log in, the system alerts you if you have any messages on the bulletin board and
the date of the latest message. Also, if Avaya personnel post high-priority messages while you
are logged in, you receive notification the next time you enter a command. This notification
disappears after you enter another command and reoccurs at login until deleted by Avaya
personnel.
You maintain the bulletin board by deleting messages you have already read. You cannot delete
high-priority messages. If the bulletin board is at 80% or more capacity, a message appears at
login indicating how much of its capacity is currently used (for example, 84%). If the bulletin
board reaches maximum capacity, new messages overwrite the oldest messages.
Note:
Note:
The bulletin board does not lose information during a system reset at level 1 or
level 2. If you save translations, the information can be restored if a system reset
occurs at levels 3, 4, or 5.
Instructions
Displaying messages
To display the bulletin board:
1. Type display bulletin-board. Press Enter.
The Bulletin Board screen displays.
Issue 4.0 January 2008
43
44. System Basics
Figure 10: Bulletin Board screen
display bulletin-board
Message (* indicates high-priority)
*Avaya is in the process of
*investigating your trunk lockup problem.
*The Bulletin Board will be updated as
*we find information.
* We have identified the problem.
*The trunk you added does not provide
*disconnect supervision. However, the
*trunk group was administered as such.
*Please call Pat J. for details.
We recently added a new trunk group (14)
and have had many of the members getting
locked up.
We see the error - thanks for checking.
Page 1 of 3
Date
03/02/93
03/02/93
03/02/93
03/02/93
03/04/93
03/04/93
03/04/93
03/04/93
03/04/93
03/02/93
03/02/93
03/02/93
03/05/93
Posting a message
In our example, we post a message to the bulletin board about a problem with a new trunk
group, and an Avaya representative replies to our message.
To post a message to the bulletin board:
1. Type change bulletin-board. Press Enter.
The Bulletin Board screen displays. There are three pages of message space within the
bulletin board. The first page has 19 lines, but you can only enter text on lines 11-19. The
first 10 lines on page 1 are for high-priority messages from Avaya personnel and are noted
with an asterisk (*). The second and third pages each have 20 lines, and you can enter text
on any line. The system automatically enters the date the message was posted or last
changed to the right of each message line.
2. Type your message.
You can enter up to 40 characters of text per line. You also can enter one blank line. If you
enter more than one blank line, the system consolidates them and displays only one. The
system also deletes any blank line if it is line one of any page. You cannot indent text on the
bulletin board. The Tab key moves the cursor to the next line.
3. Press Enter to save your changes.
44 Administrator Guide for Avaya Communication Manager
45. Saving Translations
Deleting messages
To delete a message from the bulletin board:
1. Type change bulletin-board. Press Enter.
The Bulletin Board screen appears.
2. Enter a space as the first character on each line of the message you want to delete. Press
Enter.
3. Press Enter to save your changes.
Saving Translations
Communication Manager retains all translation data in memory while the system is operating. If
it goes down, you lose all this translation data. You must save in-memory translation data to the
memory card (flash ROM), disk, or tape. Saving translation data to memory card or tape is the
same as backing up your system.
Note:
Note:
Save translations on a daily basis. You might want to save translations after
business hours to prevent dial tone delays or during slow business hours if your
business is open 24 hours.
The save translation command writes two time-stamped identical copies of the translation
data to the selected memory card, disk, or tape. The save writes one complete copy first, then
writes the second copy in a different area of the device — both with the same time-stamp.
Failure during a save, including a system crash, usually affects only one copy. The affected
copy is marked "bad" and should not be used for backup.
You can set save translation to be completed automatically as part of regularly scheduled
maintenance or manually, as needed. For more information about saving translations
automatically, see the maintenance book for your system.
Tip:
Tip:
To determine if your system saves translations automatically, type display
system-parameters maintenance to see if you have scheduled
maintenance.
Translation copy protection assigns a number to a specific telephone system and to the flash
card or set of flash cards that belong to that system. For Avaya Communication Manager on a
DEFINITY Server CSI, this number is the same on both the translation storage device (flash
card) and the Flash PROM (Programmable Read Only Memory) of the processor circuit pack. In
a duplicated system, the Flash PROM of each processor circuit pack has a translation ID and
both ID’s are stored on the memory card.
Issue 4.0 January 2008
45
46. System Basics
An attempt to initialize (boot) the system with translations that do not contain the same
identification number as stored in the processor circuit pack raises a major alarm and disables
access to the save translations command for all non-Avaya logins. You also receive a
warning message on the copyright screen notifying you of the mismatch. Contact your Avaya
representative to correct this mismatch and reset the save translations command. You
must correct the mismatch before the end of the specified grace period, otherwise you cannot
access system management commands (such as: add, change, remove, and duplicate) that
modify translation data. Avaya specifies the grace period during a system installation or
following an upgrade.
Before you start
If you are saving translations to a memory card or tape, you must verify the memory card or
tape is in place and clear any active alarms from the alarms panel.
If you have Avaya Communication Manager on a DEFINITY Server CSI, verify the memory card
translation ID matches the translation ID of your server’s Flash PROM.
Instructions
In our example, we save translations to the tapes on both processor A and B.
To save translations manually:
1. Type save translation both tape. Press Enter.
The save process can take up to 10 minutes. You cannot administer your system while the
save is in process. The Save Translation screen displays.
Figure 11: Save Translation screen
SAVE TRANSLATION
Processor
SPE_A
SPE_B
Command Completion Status
Success
Success
Error Code
0
0
2. If there is an error message in the Command Completion Status field and an error code in
the Error Code field, clear the error and repeat the save process.
46 Administrator Guide for Avaya Communication Manager
47. Performing Backups
More information
When mass storage system (MSS) devices on both processors in a duplex system are
specified, translation data is saved from the active processor to the active and standby MSS
devices at the same time. If the save to one device fails or one device is out of service, the other
save continues. You receive the status of each save separately.
Note:
Note:
If you have a duplex system and you save translation data to both MSS devices
one at a time, translation data inconsistencies between the two devices can
occur.
Fixing problems
Note:
Note:
You cannot see whether the translation ID on the flash card corresponds to the
number on the Processor circuit packs. However, if the numbers do not match,
the system issues an error message when you attempt a save translation
operation.
When failures occur, the system responds with the following error codes.
Problem
Possible causes
Solution
1
Save translation cannot
write to the active drive.
Repeat the save translation
process for the active drive.
2
Save translation cannot
write to the standby drive.
Repeat the save translation
process for the standby drive.
For more information about error messages and how to correct them, or backing up or restoring
your system, see the maintenance book for your system.
Performing Backups
Information on performing backups to your system can be found in the Maintenance Procedures
for Avaya Communication Manager, Media Gateways and Servers, 03-300432.
Issue 4.0 January 2008
47
49. Chapter 2: Planning the System
Understanding Your Configuration
At a very basic level, Avaya Communication Manager consists of hardware to perform call
processing, and the software to make it run. You use the administration interface to let the
system know what hardware you have, where it is located, and what you want the software to
do with it.
You can find out which circuit packs are in the system and which ports are available by entering
the command list configuration all. There are variations on this command that display
different types of configuration information. Use the help function to experiment, and see which
command works for you.
To view a list of port boards on your system:
1. Type list configuration port-network. Press Enter.
The System Configuration screen appears.
Figure 12: System Configuration screen
SYSTEM CONFIGURATION
Board
Number
Board Type Code
Vintage
Assigned Ports
u=unassigned t=tti p=psa
01A05
01A06
01B05
DIGITAL LINE
ANALOG LINE
ANALOG LINE
TN754B 000002
TN742 000010
TN746B 000008
01C04
ANALOG LINE
TN746B 000008
01C05
DIGITAL LINE
TN2224 000004
01C06
01C10
HYBRID LINE
DIGITAL LINE
TN762B 000004
TN754 000004
01
01
u
u
u
u
01
u
u
01
u
u
02
u
u
u
u
u
u
u
02
u
03
03
u
u
u
u
u
u
u
u
u
u
04
u
u
u
u
04
u
u
u
u
05
u
u
u
u
u
u
u
u
u
u
u
u
u
u
u
u
u
u
u
u
u
07
u
u
u
u
u
07
u
u
u
u
08
u
u
u
u
u
08
u
u
u
u
The System Configuration screen shows all the boards on your system that are available for
connecting telephones, trunks, data modules and other equipment. You can see the board
number, board type, circuit-pack type, and status of each board’s ports. The u entries on this
screen indicate unused ports that are available for you to administer. These might also appear
as p or t, depending on settings in your system.
Issue 4.0 January 2008
49
50. Planning the System
You will find many places in the administration interface where you are asked to enter a port or
slot. The port or slot is actually an address that describes the physical location of the equipment
you are using.
A port address is made up of four parts:
●
cabinet — the main housing for all the server equipment. Cabinets are numbered starting
with 01.
●
carrier — the rack within the cabinet that holds a row of circuit packs. Each carrier within a
cabinet has a letter, A to E.
●
slot — the space in the carrier that holds an individual circuit pack. Slots are numbered
01-16.
●
port — the wire that is connected to an individual piece of equipment (such as a telephone
or data module). The number of ports on a circuit pack varies depending on the type.
So, if you have a single-carrier cabinet, the circuit pack in slot 06 would have the address
01A06. If you want to attach a telephone to the 3rd port on this board, the port address is
01A0603 (01=cabinet, A=carrier, 06=slot, 03=port).
50 Administrator Guide for Avaya Communication Manager
51. Understanding the Dial Plan
Understanding the Dial Plan
Your dial plan tells your system how to interpret dialed digits. For example, if you dial 9 on your
system to access an outside line, it is actually the dial plan that tells the system to find an
external trunk when a dialed string begins with a 9.
The dial plan also tells the system how many digits to expect for certain calls. For example, the
dial plan might indicate that all internal extensions are 4-digit numbers that start with 1 or 2.
Let us take a look at an example dial plan so you’ll know how to read your system’s dial plan.
The following figure shows an example of a simple dial plan.
Figure 13: Dial Plan Analysis Table screen
display dialplan analysis
Page 1 of x
DIAL PLAN ANALYSIS TABLE
Location: All
Dialed
String
00
1
2
3
3
4
4
5
5
6
7210
8
9
*
#
Total
Length
2
3
4
5
1
1
5
5
7
5
7
7
1
3
3
Call
Type
attd
dac
ext
ext
aar
ars
ext
ext
ext
ext
ext
ext
fac
fac
fac
Dialed
String
Percent Full: 7
Total Call
Length Type
Dialed
String
Total Call
Length Type
The Dial Plan Analysis Table defines the dialing plan for your system.
Note:
Note:
In Communication Manager 5.0 and later, you can administer dial plans
per-location. Typing the command change dialplan analysis displays the
all-locations Dial Plan Analysis screen. To access a per-location screen, type
change dialplan analysis location n, where n represents the number
of a specific location. For details on command options, see online help, or
Maintenance Commands for Avaya Communication Manager, Media Gateways
and Servers, 03-300431.
Issue 4.0 January 2008
51
52. Planning the System
The Call Type column in the Dial Plan Analysis Table indicates what the system does when a
user dials the digit or digits indicated in the Dialed String column. The Total Length column
indicates how long the dialed string will be for each type of call. For example, this dial plan
shows that when users dial a 5-digit number that starts with 3, they are dialing an extension.
The Dial Plan Analysis Table in our example contains the following call types:
●
Attendant (attd) — Defines how users call an attendant. Attendant access numbers can be
any number from 0 to 9 and contain 1 or 2 digits.
In our example figure, the system calls an attendant when users dial 00.
●
Dial access code — Allows you to use trunk access codes (TAC) and feature access
codes (FAC) in the same range. For example, you could define the group 100 to 199,
which would allow both FAC and TAC in that range. Dial access codes can start with any
number from 1 to 9, * and #, and contain up to 4 digits.
In our example figure, dial access codes begin with 1 and must be 3 digits long.
Note:
The Dial Plan Analysis Table does not allow you to enter a range specifically for
trunk access codes. However, the Trunk Group screen still allows you to assign
a TAC to a trunk group. The TAC you enter on the Trunk Group screen must
match the format you have administered for a DAC on the Dial Plan Analysis
Table.
Note:
●
Extensions (ext) — Defines extension ranges that can be used on your system. In our
figure, extensions must be in the ranges 30000 to 39999, 40000 to 49999 and 50000 to
59999.
●
Feature access codes (fac) only — FAC can be any number from 1 to 9 and contain up to
4 digits. You can use * or #, but only as a first digit. In our example, feature access codes
can begin with * or # and are 3-digits long.
The Dial Plan Analysis Table works with the Dial Plan Parameters Table for fully defining
your dial plan. The Dial Plan Parameters Table allows you to set system-wide parameters for
your dial plan, or to define a Dial Plan Parameters Table per-location.
Displaying your dial plan
You might want to take this opportunity to look at and interpret your own dial plan. To display
your system’s dial plan:
1. Type display dialplan analysis or display dialplan analysis location
n, where n represents the number of a specific location. Press Enter.
52 Administrator Guide for Avaya Communication Manager
53. Understanding the Dial Plan
Modifying your dial plan
It is easy to make changes to your dial plan. For example, we will add a new range of dial
access codes to the dial plan. We want to be able to assign both FAC and TAC in the 700 to 799
range.
1. Type change dialplan analysis or change dialplan analysis location n,
where n represents the number of a specific location. Press Enter.
The Dial Plan Analysis Table screen appears.
2. Move the cursor to an empty row.
3. Type 7 in the Dialed String column. Press Tab to move to the next field.
4. Type 3 in the Total Length column. Press Tab to move to the next field.
5. Type dac in the Call Type column.
6. Press Enter to save your changes.
Adding extension ranges
You might find that as your needs grow you want a new set of extensions. Before you can
assign a station to an extension, the extension must belong to a range that is defined in the dial
plan. We will add a new set of extensions that start with 3 and are 4 digits long (3000 to 3999).
To add this set of extensions to the dial plan:
1. Type change dialplan analysis or change dialplan analysis location n,
where n represents the number of a specific location. Press Enter.
The Dial Plan Analysis Table screen appears.
2. Move the cursor to an empty row.
3. Type 3 in the Dialed String column. Press Tab to move to the next field.
4. Type 4 in the Total Length column. Press Tab to move to the next field.
5. Type ext in the Call Type column.
6. Press Enter to save your changes.
Administering a Uniform Dial Plan
You can set up a Uniform Dialing Plan that can be shared among a group of servers. For more
information, see Feature Description and Implementation for Avaya Communication Manager,
555-245-205.
Issue 4.0 January 2008
53
54. Planning the System
Administering a Multi-Location Dial Plan
When a customer migrates from a multiple independent node network to a single distributed
server whose gateways are distributed across a data network, it might initially appear as if some
dial plan functions are no longer available.
The multi-location dial plan feature preserves dial plan uniqueness for extensions and
attendants that were provided in a multiple independent node network, but appear to be
unavailable when customers migrate to a single distributed server. This feature is available
beginning with Communication Manager, release 2.0.
For example, in a department store with many locations, each location might have had its own
switch with a multiple independent node network. The same extension could be used to
represent a unique department in all stores (extension 123 might be the luggage department). If
the customer migrates to a single distributed server, a user could no longer dial 123 to get the
luggage department in their store. The user would have to dial the complete extension to
connect to the proper department.
Instead of having to dial a complete extension, the multi-location dial plan feature allows a user
to dial a shorter version of the extension. For example, a customer can continue to dial 123
instead of having to dial 222-123.
Communication Manager takes leading digits of the location prefix and adds some or all of its
leading digits (specified on the Uniform Dial Plan screen) to the front of the dialed number. The
switch then analyzes the entire dialed string and routes the call based on the administration on
the Dial Plan Parameters and Dial Plan Analysis screens.
Note:
Before you can administer the multi-location dial plan feature, the Multiple
Locations field on the System Parameters Customer-Options (Optional
Features) screen must be enabled. To check if this is enabled, use the display
system-parameters customer-options command. The Multiple
Locations field is on page 3 of the System Parameters Customer-Options
(Optional Features) screen. Ensure that the field is set to y.
Note:
Prepending the location prefix to dialed numbers
Use the Insert Digits field on the Uniform Dial Plan Table screen to assign the location prefix
from the caller’s location on the Locations screen. The system adds some or all of its leading
digits (specified on the Uniform Dial Plan screen) to the front of the dialed number. The switch
then analyzes the entire dialed string and routes the call based on the administration on the Dial
Plan Parameters screen.
●
Non-IP telephones and trunks inherit the location number of the hardware they are
connected to (for example, the cabinet, remote office, or media gateway).
●
IP telephones indirectly obtain their location number.
54 Administrator Guide for Avaya Communication Manager
