Administering Avaya Aura™

Communication Manager

03-300509
Issue 5.0
Release 5.2
May 2009
© 2009 Avaya Inc.

All Rights Reserved.

Notice
While reasonable efforts were made to ensure that the information in this
document was complete and accurate at the time of printing, Avaya Inc.
can assume no liability for any errors. Changes and corrections to the
information in this document may be incorporated in future releases.

For full legal page information, please see the complete document,
Avaya Legal Page for Software Documentation,
Document number 03-600758.
To locate this document on the Web site, simply go to
[Link] and search for the document number in
the search box.

Documentation disclaimer
Avaya Inc. is not 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.
Customer and/or 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 the Customer or End User.

Link disclaimer
Avaya Inc. is not responsible for the contents or reliability of any linked
Web sites referenced elsewhere within this documentation, and Avaya
does not necessarily endorse the products, services, or information
described or offered within them. We cannot guarantee that these links
will work all of the time and we have no control over the availability of the
linked pages.

Warranty
Avaya Inc. 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
through the following Web site:
[Link]

Copyright
Except where expressly stated otherwise, the Product is protected by
copyright and other laws respecting proprietary rights. Unauthorized
reproduction, transfer, and or use can be a criminal, as well as a civil,
offense under the applicable law.

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:
[Link]
 Contents

About this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Conventions used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Admonishments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Related Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
How to obtain Avaya books on the Web . . . . . . . . . . . . . . . . . . . . . . . . . . 14
How to comment on this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
How to get help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 1: System Basics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Logging into the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Login messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Logging off the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Administering User Profiles and Logins . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Establishing Daylight Savings Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Setting Time of Day Clock Synchronization . . . . . . . . . . . . . . . . . . . . . . . . 28
Setting the System Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Using the Bulletin Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Saving Translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Performing Backups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Chapter 2: Planning the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Understanding Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Understanding the Dial Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Controlling the features your users can access. . . . . . . . . . . . . . . . . . . . . . 48
System-wide settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Changing system parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Setting WAN bandwidth limits between network regions . . . . . . . . . . . . . . . . . 50
Administering Treatment for Denied or Invalid Calls . . . . . . . . . . . . . . . . . . . 52
Setting up Music-on-Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Receiving Notification in an Emergency . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Notifying a Digital Pager of an Emergency . . . . . . . . . . . . . . . . . . . . . . . . 59
Other Useful Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Controlling the Calls Your Users Can Make and Receive . . . . . . . . . . . . . . . . . 62
Station Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Administering Avaya Aura™ Communication Manager May 2009 3

Contents

Chapter 3: Managing Telephones. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Installing New Telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Adding new telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Duplicating telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Using an alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Customizing your telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Upgrading telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Swapping telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Using ACTR to move telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Using TTI to move telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Removing telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Adding a fax or modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Adding an H.323 Softphone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Adding an IP telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Setting up Remote Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Chapter 4: Managing Telephone Features . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Adding Feature Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Telephone Feature Buttons Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Adding Abbreviated Dialing Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Setting up Bridged Call Appearances . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Setting up Extension to Cellular . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Setting up Terminal Self-Administration . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Setting Up Enterprise Mobility User . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Chapter 5: Managing Attendant Consoles . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Attendant Consoles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Adding an Attendant Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Attendant Console Feature Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Setting Console Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Removing an Attendant Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Providing Backup for an Attendant. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Return Call to (same) Attendant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Chapter 6: Managing Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Displaying Caller Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Displaying ANI Calling Party Information . . . . . . . . . . . . . . . . . . . . . . . . . 167

4 Administering Avaya Aura™ Communication Manager May 2009

 Contents

Displaying ICLID Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Changing the Display Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Setting up Directory Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Making Standard Telephone Features easier to use . . . . . . . . . . . . . . . . . . . 179

Chapter 7: Handling Incoming Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Setting up Basic Call Coverage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Setting up Advanced Call Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Setting up Call Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Setting up Night Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Adding Call Pickup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Managing Hunt Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Managing Vectors and VDNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Understanding Automatic Call Distribution . . . . . . . . . . . . . . . . . . . . . . . . 245
Assigning a Terminating Extension Group . . . . . . . . . . . . . . . . . . . . . . . . 245

Chapter 8: Routing Outgoing Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

World Class Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Managing Calling Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Assigning ARS FAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Displaying ARS Analysis Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Understanding ARS Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Administering Call Type Digit Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Setting up Multiple Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Routing with Multiple Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Modifying Call Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Overriding Call Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Defining ARS Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Setting up Time of Day Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Location by Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

Chapter 9: Managing Multimedia Calling . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

Multimedia Applications Server Interface . . . . . . . . . . . . . . . . . . . . . . . . . 271
Avaya Video Telephony Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Multimedia Call Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Understanding the Multimedia Complex . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Enhanced Mode MM Complex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341

Administering Avaya Aura™ Communication Manager May 2009 5

Contents

Chapter 10: Setting Up Telecommuting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

Configuring Communication
Manager for Telecommuting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Setting up Personal Station Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Creating a Station Security Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Assigning an Extender Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Setting up Call Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Assigning Coverage Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Installing Home Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Setting up Remote Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
Changing Telecommuting Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378

Chapter 11: Enhancing System Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . 383

Basic Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
Preventing Toll Fraud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
Physical Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
System Security Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Administering User Profiles and Logins . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Using Access Security Gateway (ASG) . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Using Busy Verify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Setting up Authorization Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
Setting up Security Violations Notification . . . . . . . . . . . . . . . . . . . . . . . . 395
Enhanced security logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
Using Station Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Dealing with Security Violations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Hot Desking Enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402

Chapter 12: Managing Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405

Tips for working with trunk groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
Adding a CO, FX, or WATS trunk group . . . . . . . . . . . . . . . . . . . . . . . . . . 407
Adding a DID trunk group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
Adding a PCOL trunk group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Adding a Tie or Access trunk group . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
Adding a DIOD trunk group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Setting up digital trunks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Adding trunks to a trunk group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Removing trunk groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421

6 Administering Avaya Aura™ Communication Manager May 2009

 Contents

Resetting trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422

Inserting and absorbing digits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Administering trunks for Listed Directory Numbers . . . . . . . . . . . . . . . . . . . 424
Administering Answer Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Administering ISDN trunk groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427

Chapter 13: Managing Announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433

Getting Started with the VAL or G700 Virtual VAL . . . . . . . . . . . . . . . . . . . . 433

Chapter 14: Managing Group Communications . . . . . . . . . . . . . . . . . . . . . . . . 437

Setting up Voice Paging Over Loudspeakers . . . . . . . . . . . . . . . . . . . . . . . 437
Setting up Chime Paging Over Loudspeakers. . . . . . . . . . . . . . . . . . . . . . . 439
Paging Over Speakerphones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
Paging Users Who are on Active Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
Using Telephones as Intercoms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Setting up Automatic Answer Intercom Calls . . . . . . . . . . . . . . . . . . . . . . . 447
Observing Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448

Chapter 15: Managing Data Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451

Types of Data Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
Data Call Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
Alphanumeric Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
Data Hotline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
Data Privacy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
Default Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
Data Restriction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
Data-Only Off-Premises Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
Data Modules — General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
Administered Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
Modem Pooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
PC Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
Wideband Switching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
CallVisor Adjunct-Switch Applications Interface . . . . . . . . . . . . . . . . . . . . . 490
Setting up CallVisor ASAI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492

Chapter 16: Administering Avaya Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . 493

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
Administering the G700 Media Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . 493

Administering Avaya Aura™ Communication Manager May 2009 7

Contents

Administering the Avaya S8xxx Server . . . . . . . . . . . . . . . . . . . . . . . . . . 498

Setting up Processor Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
Administering the main or LSP split registration . . . . . . . . . . . . . . . . . . . . . 523
Administrable Alternate Gatekeeper List for IP Phones . . . . . . . . . . . . . . . . . 528
Improved Port network recovery from control network outages . . . . . . . . . . . . . 542
Administering Call-processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
Administering Voice or Network Statistics. . . . . . . . . . . . . . . . . . . . . . . . . 559
Administering SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561

Chapter 17: Collecting Call Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579

Collecting Information About Calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
Setting up Intra-switch CDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
Tracking Calls by Account Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
Forcing Users to Enter Account Codes . . . . . . . . . . . . . . . . . . . . . . . . . . 583
Receiving Call-Charge Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
Viewing Call Charge Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
Setting up Survivable CDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588

Chapter 18: Administering LDAP Directory Application . . . . . . . . . . . . . . . . . . . 595

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
Configuring the LDAP Directory Service. . . . . . . . . . . . . . . . . . . . . . . . . . 595
Synchronizing Communication Manager station with the LDAP Directory . . . . . . . 596
Configuring the 46xx and 96xx phones . . . . . . . . . . . . . . . . . . . . . . . . . . 596

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597

8 Administering Avaya Aura™ Communication Manager May 2009

 Overview

About this book

Overview
Avaya Aura™ 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 S8700-Series Server
● 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.

Administering Avaya Aura™ Communication Manager May 2009 9

About this book

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.

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 Aura™ 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.

10 Administering Avaya Aura™ Communication Manager May 2009

 Conventions used

● 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.
● 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
S8700-Series 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.

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.
● 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 an initial capital letter: 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.
● 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.

Administering Avaya Aura™ Communication Manager May 2009 11

About this book

- 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:
Tip: Draws attention to information that you might find helpful.

12 Administering Avaya Aura™ Communication Manager May 2009

 Trademarks

! CAUTION:
CAUTION: Denotes possible harm to software, possible loss of data, or possible service
interruptions.

! WARNING:
WARNING: Denotes possible harm to hardware or equipment.

! DANGER:
DANGER: Denotes possible harm or injury to your body.

! 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
Note:
Note: For information about the screens referenced in this book, see Avaya Aura™
Communication Manager Screen Reference, 03-602878.
The following documents provide additional information.
Administering Network Connectivity on Avaya Aura™ 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 Aura™ Call Center 5.2 Automatic Call Distribution (ACD) Reference, 07-602568
Avaya Aura™ Call Center 5.2 Call Vectoring and Expert Agent selection (EAS) Reference,
07-600780
Avaya Communication Manager Advanced Administration Quick Reference, 03-300364
Avaya Communication Manager Basic Administration Quick Reference, 03-300363

Administering Avaya Aura™ Communication Manager May 2009 13

About this book

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
Avaya Aura™ Communication Manager Feature Description and Implementation, 555-245-205
Avaya Aura™ Communication Manager Hardware Description and Reference, 555-245-207
Installation, Upgrades and Additions for Avaya CMC1 Media Gateways, 555-233-118
Maintenance Alarms for Avaya Aura™ Communication Manager, Media Gateways and
Servers, 03-300430
Maintenance Commands for Avaya Aura™ Communication Manager, Media Gateways and
Servers, 03-300431
Maintenance Procedures for Avaya Aura™ Communication Manager, Media Gateways and
Servers, 03-300432
Avaya Aura™ Communication Manager Overview, 03-300468
Avaya Aura™ Communication Manager Reports, 555-233-505
Avaya Aura™ Communication Manager Screen Reference, 03-602878
Avaya Aura™ Communication Manager System Capacities Table, 03-300511
Using Avaya Enterprise Survivable Servers (ESS), 03-300428
What's New in Avaya Aura™ Communication Manager, SIP Enablement Services, Avaya
Servers and Media Gateways for Release 5.2, 03-300682
For documents not listed here, go to [Link] 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
[Link]

14 Administering Avaya Aura™ Communication Manager May 2009

 How to comment on this book

For example, to access an electronic version of this book:

1. Access the Avaya Web site at [Link]
2. In the Go To: column, click the Documentation link.
3. To find a specific book, type the document number (for example, 03-300509 for this book)
in the Search Avaya text box. 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:
● e-mail: document@[Link]
● fax: 1-303-538-1741
● Contact your Avaya representative
Mention this document’s name and number, Administering Avaya Aura™ 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 [Link]
● 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.

Administering Avaya Aura™ Communication Manager May 2009 15

About this book

16 Administering Avaya Aura™ Communication Manager May 2009

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.

Logging in for remote administration

To log in for remote administration:
1. Dial the Uniform Call Distribution (UCD) group extension number.

Administering Avaya Aura™ Communication Manager May 2009 17

Chapter 1: System Basics

Note:
Note: The UCD group extension number is assigned when you set up remote
administration.
● 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 17.
For information about setting up remote administration, contact your Avaya technical
support representative.
See also Chapter 11: Enhancing System Security on page 383. For a complete description of
the Security Violation Notification feature, see Security Violation Notification in Avaya Aura™
Communication Manager Feature Description and Implementation, 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
A direct connection and over the customer’s LAN are the preferred methods. Remote access
over a modem is for Avaya maintenance access only.

18 Administering Avaya Aura™ Communication Manager May 2009

 Logging into the System

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 Communication Manager
● An SSH client, like PuTTY, and an IP address of [Link].

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 the Microsoft Internet Explorer browser. Microsoft Internet Explorer versions 6.0 and
7.0 are supported.
2. In the Location/Address field, type [Link]. Press Enter.
3. When prompted, log in to administer the Avaya S8XXX Server and the features of
Communication Manager.

Connected to the customer network : To use the server Web interface:

1. Open the Microsoft 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
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 [Link].

Administering Avaya Aura™ Communication Manager May 2009 19

Chapter 1: 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 S8700-Series Server can be used to download Avaya Site
Administration. A downloadable version of this package can be accessed through the S8300,
S8400, or S8700-Series 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 Pentium-class 300 MHz/64 MB

Windows XP Pentium-class 300 MHz/64 MB
2003 (Standard and Pentium-class 300 MHz/64 MB
Enterprise)
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.

20 Administering Avaya Aura™ Communication Manager May 2009

 Logging into the System

Operating systems Processor/RAM

Network adapter Required for network access to the

S8700-Series Server, CM Messaging, 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 CM Messaging
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.

Administering Avaya Aura™ Communication Manager May 2009 21

Chapter 1: 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 (that is, 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.

22 Administering Avaya Aura™ Communication Manager May 2009

 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 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 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 391.
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 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.

Administering Avaya Aura™ Communication Manager May 2009 23

Chapter 1: System Basics

Note:
Note: If you make 3 invalid login attempts, the system terminates the session. For more
information, see the appropriate maintenance book for your system.

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/[Link] 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/[Link] /etc/issue
cp /etc/[Link] /etc/[Link]

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 Communication Manager Administrator Logins White Paper on
[Link]
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 /[Link] and /[Link] (if using telnet) to include the text for the Issue
of the Day.

24 Administering Avaya Aura™ Communication Manager May 2009

 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 SAT cannot be executed on a

standby server
513] Password: ogin hallenge
] assword ogin: 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]

Administering Avaya Aura™ Communication Manager May 2009 25

Chapter 1: 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 Avaya Aura™
Communication Manager Feature Description and Implementation, 555-245-205, and
Maintenance Commands for Avaya Aura™ Communication Manager, Media Gateways and
Servers, 03-300431.

Establishing Daylight Savings Rules

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).

26 Administering Avaya Aura™ Communication Manager May 2009

 Establishing Daylight Savings Rules

Instructions

Establishing daylight savings rules

To modify a daylight savings rule:
1. Type change daylight-savings-rules. Press Enter.
The system displays the Daylight Savings Rules screen.
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 [Link] to [Link] the clock time shows 01:59
and at 02:00 the clock shows 03:00).notepad
On the stop date, the increment is subtracted from the specified stop time (for example, for
[Link] to [Link] the clock time shows 01:59 and at 02:00 the clock shows 01:00).
Note:
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).
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:
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 daylight savings time rules

To display daylight savings time rules:
1. Type display daylight-savings-rules. Press Enter.
The system displays the Daylight Savings Rules screen. Verify the information you
entered is correct.

Administering Avaya Aura™ Communication Manager May 2009 27

Chapter 1: System Basics

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.
● On the target server running Communication Manager, verify if Daylight Savings Time is
on.
Note:
Note: These instructions are for Avaya DEFINITY CSI servers. For more information,
see Avaya Aura™ Call Center 5.2 Automatic Call Distribution (ACD) Reference,
07-602568.
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.

28 Administering Avaya Aura™ Communication Manager May 2009

 Setting Time of Day Clock Synchronization

Figure 2: Avaya Site Administration menu

3. Click Time Synchronization.

The Time Synchronization - Properties screen displays.

Administering Avaya Aura™ Communication Manager May 2009 29

Chapter 1: System Basics

Figure 3: 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.

30 Administering Avaya Aura™ Communication Manager May 2009

 Setting Time of Day Clock Synchronization

Figure 4: 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.

Administering Avaya Aura™ Communication Manager May 2009 31

Chapter 1: System Basics

Figure 5: 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.

32 Administering Avaya Aura™ Communication Manager May 2009

 Setting Time of Day Clock Synchronization

Figure 6: 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.

Administering Avaya Aura™ Communication Manager May 2009 33

Chapter 1: System Basics

Figure 7: 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 Aura™ Call Center 5.2
Automatic Call Distribution (ACD) Reference, 07-602568.

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.

34 Administering Avaya Aura™ Communication Manager May 2009

 Setting the System Date and Time

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 CM Messaging) 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. For information about
this screen, see Avaya Aura™ Communication Manager Screen Reference, 03-602878.
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 system displays the Date and Time screen.
2. Complete the Date fields.
a. Type Tuesday in the Day of the Week field.
b. Type November in the Month field.
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.

Administering Avaya Aura™ Communication Manager May 2009 35

Chapter 1: System Basics

Displaying the system date and time

To display the system date and time:
1. Type display time. Press Enter.
The system displays the Date and Time screen. Verify the information you entered is
correct.

Related topics
See Establishing Daylight Savings Rules on page 26 for more information about setting system
time.
For additional information, see Avaya Aura™ Call Center 5.2 Automatic Call Distribution (ACD)
Reference, 07-602568.

Using the Bulletin Board

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.

36 Administering Avaya Aura™ Communication Manager May 2009

 Using the Bulletin Board

Instructions

Displaying messages
To display the bulletin board:
1. Type display bulletin-board. Press Enter.
The system displays the Bulletin Board screen.

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 system displays the Bulletin Board screen. 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.

Deleting messages
To delete a message from the bulletin board:
1. Type change bulletin-board. Press Enter.
The system displays the Bulletin Board screen.
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.

Administering Avaya Aura™ Communication Manager May 2009 37

Chapter 1: System Basics

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 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.
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.

38 Administering Avaya Aura™ Communication Manager May 2009

 Saving Translations

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 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 (Figure 8) displays.

Figure 8: Save Translation screen

SAVE TRANSLATION

Processor Command Completion StatusError Code

SPE_A Success 0
SPE_B Success 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.

More information
When mass storage system (MSS) devices on both processors in a duplicated server 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.

Administering Avaya Aura™ Communication Manager May 2009 39

Chapter 1: System Basics

Note:
Note: If you have a duplicated server 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 Repeat the save translation

write to the active drive. process for the active drive.
2 Save translation cannot Repeat the save translation
write to the standby drive. 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 Aura™ Communication Manager, Media Gateways and Servers, 03-300432.

40 Administering Avaya Aura™ Communication Manager May 2009

Chapter 2: Planning the System

Understanding Your Configuration

At a very basic level, 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:

Type list configuration port-network. Press Enter.
The system displays the System Configuration screen, which 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.
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:
● media gateway — the main housing for all the server equipment. Media Gateways are
numbered starting with 01.
● carrier — the rack within the media gateway that holds a row of circuit packs. Each carrier
within a media gateway 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 media gateway, 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=media gateway, A=carrier, 06=slot, 03=port).

Administering Avaya Aura™ Communication Manager May 2009 41

Chapter 2: Planning the System

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 9: Dial Plan Analysis Table screen

display dialplan analysis Page 1 of x
DIAL PLAN ANALYSIS TABLE
Location: All Percent Full: 7

Dialed Total Call Dialed Total Call Dialed Total Call

String Length Type String Length Type String Length Type
00 2 attd
1 3 dac
2 4 ext
3 5 ext
3 1 aar
4 1 ars
4 5 ext
5 5 ext
5 7 ext
6 5 ext
7210 7 ext
8 7 ext
9 1 fac
* 3 fac
# 3 fac

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 Aura™ Communication Manager, Media
Gateways and Servers, 03-300431.

42 Administering Avaya Aura™ Communication Manager May 2009

 Understanding the Dial Plan

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:
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.
● 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.

Administering Avaya Aura™ Communication Manager May 2009 43

Chapter 2: Planning the System

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 system displays the Dial Plan Analysis Table screen.
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 system displays the Dial Plan Analysis Table screen.
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 Avaya Aura™ Communication Manager Feature Description and
Implementation, 555-245-205.

44 Administering Avaya Aura™ Communication Manager May 2009

 Understanding the Dial Plan

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:
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.

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 media gateway, remote office, or media gateway).
● IP telephones indirectly obtain their location number.

Administering Avaya Aura™ Communication Manager May 2009 45

Chapter 2: Planning the System

- A location number is administered on the IP Network Region screen that applies to all
telephones in that IP region.
- If a Location field is left blank on an IP Network Region screen, an IP telephone
derives its location from the media gateway where the C-LAN board is that the
telephone registered through.
● IP trunks obtain their location from the location of its associated signaling group. Either
direct administration (only possible for signaling groups for remote offices), or the ways
described for IP telephones, determines the location.
● Extension to Cellular endpoints for any applications obtain their location from the Stations
with Off-PBX Telephone Integration screen.
For more information about setting up multiple locations, refer to Setting up Multiple
Locations on page 256.

Other options for the dial plan

You can establish a dial plan so that users only need to dial one digit to reach another
extension. You can also establish a dial plan that allows users to dial, for example, two digits to
reach one extension, and thee digits to reach another. This is particularly useful in the
hospitality industry, where you want users to be able to simply dial a room number to reach
another guest.
If you have Communication Manager 5.0 or later, you can administer dial plans per-location. 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 Aura™ Communication Manager, Media Gateways and
Servers, 03-300431.

Adding feature access codes

As your needs change, you might want to add a new set of FAC for your system. Before you
can assign a FAC on the Feature Access Code (FAC) screen, it must conform to your dial plan.
In our example, if you want to assign a feature access code of 33 to Last Number Dialed, first
you need to add a new FAC range to the dial plan.
To add a FAC range from 30 to 39:
1. Type change dialplan analysis or change dialplan analysis location n,
where n represents the number of a specific location. Press Enter.
The system displays the Dial Plan Analysis Table screen.
2. Move the cursor to an empty row.
3. Type 3 in the Dialed String column. Press Tab to move to the next field.

46 Administering Avaya Aura™ Communication Manager May 2009

 Understanding the Dial Plan

4. Type 2 in the Total Length column. Press Tab to move to the next field.
5. Type fac in the Call Type column.
6. Press Enter to save your changes.

Changing feature access codes

Feature access codes (FAC) allow users to activate and deactivate features from their
telephones. A user who knows the FAC for a feature does not need a programmed button to
use the feature. For example, if you tell your users that the FAC for the Last Number Dialed is
*33, then users can redial a telephone number by entering the FAC, rather than requiring a Last
Number Dialed button.
Many features already have factory-set feature access codes. You can use these default codes
or you can change them to codes that make more sense to you. However, every FAC must
conform to your dial plan and must be unique. For more information about the dial plan, refer to
Understanding the Dial Plan on page 42.
Let us try an example. If you want to change the feature access code for Call Park to *72:
1. Type change feature-access-codes. Press Enter.
The system displays the Feature Access Code (FAC) screen.
2. Move the cursor to the Call Park Access Code field.
3. Type *72 in the access code field over the old code.
4. Press Enter to save your changes.
If you try to enter a code that is assigned to a feature, the system warns you of the
duplicate code and does not allow you to proceed until you change one of them.

Tip:
Tip: To remove any feature access code, merely delete the existing FAC and leave
the field blank.

Administering Dial Plan Transparency (DPT)

The Dial Plan Transparency (DTP) feature preserves users’ dialing patterns when a media
gateway registers with a local survivable processor (LSP), or when a Port Network requests
service from an Enterprise Survivable Server (ESS). Note that this feature does not provide
alternate routing for calls made between Port Networks connected via networks other than IP
(e.g., ATM or DS1C), and that register to different ESS servers during a network outage.

Administering Avaya Aura™ Communication Manager May 2009 47

Chapter 2: Planning the System

Administration of Dial Plan Transparency (DPT) is similar to setting up Inter-Gateway Alternate

Routing (IGAR). You must first enable the DPT feature, then set up Network Regions and trunk
resources for handling the DPT calls. For ESS servers, you must also assign Port Networks to
communities. The following table show the screens and field used in setting up Dial Plan
Transparency:

Screen name Purpose Fields

Feature-Related System ● Enable the DPT feature for ● Enable Dial Plan
Parameters your system. Transparency in
Survivable Mode?
● Indicate the Class of ● COR to use for DPT
Restriction to use for the
Dial Plan Transparency
feature.
IP Network Region Administer the DPT feature for ● Incoming LDN Extension
Network Regions. ● Dial Plan Transparency in
Survivable Mode?
System Parameters Port Enter the community Community
Network assignments for each Port
Network.

For more information on the Dial Plan Transparency feature, see Dial Plan Transparency in
Avaya Aura™ Communication Manager Feature Description and Implementation, 555-245-205.

Controlling the features your users can access

Communication Manager offers a wide range of features and functions. Some of these you can
administer differently from one user to the next. For example, you can give one user a certain
set of telephone buttons, and the next user a completely different set, depending on what each
person needs to get his/her job done. You decide on these things as you administer the
telephones for these individuals. Refer to Telephone Feature Buttons Table on page 108 for
more information.
You can also establish classes of service (COS) to control the Communication Manager
features that users can access. For example, you can permit users to forward their calls, or
restrict them from placing priority calls. Once you have set permissions for a class of service,
you assign this COS to a user’s telephone or other device.
Classes of service are very similar to classes of restriction. COR and COS do not overlap in the
access or restrictions they control.

48 Administering Avaya Aura™ Communication Manager May 2009

 System-wide settings

Class of service and class of restriction give you great flexibility with what you allow users to do.
If you are in doubt about the potential security risks associated with a particular permission,
contact your Avaya technical support representative.

System-wide settings
There are some settings that you enable or disable for the entire system, and these settings
effect every user. You might want to look over the various System Parameters screens and
decide which settings best meet the needs of your users.
To see a list of the different types of parameters that control your system, type display
system-parameters. Press Help. You can change some of these parameters yourself. Type
change system-parameters. Press Help to see which types of parameters you can
change. In some cases, an Avaya technical support representative is the only person who can
make changes, such as to the System Parameters Customer-Options (Optional Features)
screen. For information about this screen, see Avaya Aura™ Communication Manager Screen
Reference, 03-602878.
Type list usage to see all the instances of an object, such as an extension or ip address, in
your system. This is useful when you attempt to change administration and receive an "in use"
error. See Maintenance Commands for Avaya Aura™ Communication Manager, Media
Gateways and Servers, 03-300431, for more information.
This chapter offers a few examples of how you establish these system-wide settings. Avaya
Aura™ Communication Manager Screen Reference, 03-602878, contains explanations of each
of the system parameters screens, and how to use them.

Changing system parameters

You can modify the system parameters that are associated with some of the system features.
For example, you can use the system parameters to allow music to play if callers are on hold or
to allow trunk-to-trunk transfers on the system.
Generally, Avaya sets your system parameters when your system is installed. However, you
can change these parameters as your organization’s needs change. For example, let us say
that you are told that the number of rings between each point for new coverage paths should
change from 4 to 2 rings.
To change the number of rings:
1. Type change system-parameters coverage/forwarding. Press Enter.
The system displays the System-Parameters Call Coverage/Call Forwarding screen.

Administering Avaya Aura™ Communication Manager May 2009 49

Chapter 2: Planning the System

2. In the Local Coverage Subsequent Redirection/CFWD No Answer Interval field, type

2.
3. Press Enter to save your changes.
Each telephone in a Call Coverage path now rings twice before the call routes to the next
coverage point. The Local Cvg Subsequent Redirection/CFWD No Ans Interval field
also controls the number of rings before the call is forwarded when you use Call
Forwarding for busy/don’t answer calls. This applies only to calls covered or forwarded to
local extensions. Use Off-Net to set the number of rings for calls forwarded to public
network extensions.

Setting WAN bandwidth limits between network regions

Using the Communication Manager Call Admission Control: Bandwidth Limitation (CAC-BL)
feature, you can specify a VOIP bandwidth limit between any pair of IP network regions, and
then deny calls that need to be carried over the WAN link that exceed that bandwidth limit.
Bandwidth limits can be administered in terms of:
● Kbit/sec WAN facilities
● Mbit/sec WAN facilities
● Explicit number of connections
● No limit
It is highly recommended that you have the following design information before setting the
bandwidth limits and mapping the connections:
1. Network topology and WAN link infrastructure.
2. An understanding of the Committed Information Rate (CIR) for the WAN infrastructure.
3. Overlay/design of the Network Regions mapped to the existing topology.
4. Codec sets administered in the system.
5. Bandwidth is assumed to be full duplicated server.

50 Administering Avaya Aura™ Communication Manager May 2009

 Setting WAN bandwidth limits between network regions

The following table can be used to help assess how much bandwidth (in Kbits/sec) is used for
various types of codecs and packet sizes. The values shown assume a 7 byte L2 WAN header
(and are rounded up).

Table 1: Bandwidth usage (in Kbits/sec) based on packet size and codec selection

Packet 10 ms 20 ms 30 ms 40 ms 50 ms 60 ms
Size

G.711 102 83 77 74 72 71
G.729 46 27 21 18 16 15
G.723-6.3 NA NA 19 NA NA 13
G.723-5.3 NA NA 18 NA NA 12

These values, when compared to the actual bandwidth used for 8 byte as well as 10 byte L2
WAN headers are not significantly different. In some cases, the rounded up values shown
above are greater than values used for 10 bytes.
The bandwidth usage numbers shown above assume 6 bytes for Multilink Point-to-Point
Protocol (MP) or Frame Relay Forum (FRF), 12 Layer 2 (L2) header, and 1 byte for the
end-of-frame flag on MP and Frame Relay frames for a total of 7 byte headers only. They do not
account for silence suppression or header compression techniques, which might reduce the
actual bandwidth. For other types of networks (such as Ethernet or ATM) or for cases where
there is a lot of silence suppression or header compression being used, the network might be
better modeled by administering the CAC-BL limits in terms of number of connections rather
than bandwidth used.

Instructions
Note:
Note: All DIRECT links must be administered first, and INDIRECT links administered
last.
To set bandwidth limitations between directly-connected network regions:
1. Type change ip-network region <n>, where n is the region number you want to
administer. Press Enter.
The system displays the IP Network Region screen.
2. Scroll to page 3 of the screen, Inter Network Region Connection Management.
3. In the codec-set field, enter the number (1-7) of the codec set to be used between the two
regions.
4. In the Direct WAN field, enter y.

Administering Avaya Aura™ Communication Manager May 2009 51

Chapter 2: Planning the System

5. In the WAN-BW-limits field, enter the number and unit of measure (Calls, Kbits, Mbits, No
Limit) that you want to use for bandwidth limitation.
6. Press Enter to save your changes.
To set bandwidth limitations between indirectly-connected network regions:
1. Type change ip-network region <n>, where n is the region number you want to
administer. Press Enter.
The system displays the IP Network Region screen.
2. Scroll to page 3 of the screen, Inter Network Region Connection Management.
3. In the codec-set field, enter the number (1-7) of the codec set to be used between the two
regions.
4. In the Direct WAN field, enter n.
5. In the Intervening-regions fields, enter up to four intervening region numbers between
the two indirectly connected regions.
6. In the Dynamic CAC Gateway field, set the gateway that reports the bandwidth limit for
this link. The gateway must be configured to be a CAC gateway.
7. Press Enter to save your changes.
Note:
Note: Type display ip-network region <n> to view the current settings of
inter-network region connections. Type status ip-network region <n> to
view the current status (that is, bandwidth and number of connections being
used) of network-region connections.

Administering Treatment for Denied or Invalid Calls

You can administer your system to reroute denied or invalid calls to an announcement, the
attendant, or to another extension.

Instructions
In this example, we want:
● all outward restricted call attempts to route to an announcement at extension 2040
● all incoming calls that are denied to route to the attendant
● all invalid dialed numbers to route to an announcement at extension 2045

52 Administering Avaya Aura™ Communication Manager May 2009

 Setting up Music-on-Hold

1. Type change system-parameters features. Press Enter.

The system displays the Feature-Related System Parameters screen.
2. In the Controlled Outward Restriction Intercept Treatment field, type
announcement.
Another blank field appears.
3. In this blank field, type 2040.
This is the extension of an announcement you recorded earlier.
4. In the DID/Tie/ISDN Intercept Treatment field, type attd.
This allows the attendant to handle incoming calls that have been denied.
5. In the Invalid Number Dialed Intercept field, type announcement.
Another blank field appears.
6. In this blank field, type 2045.
This is the extension of an announcement you recorded earlier.
7. Press Enter to save your changes.

Setting up Music-on-Hold
Music-on-Hold automatically provides music to a caller placed on hold. Music lets the caller
know that the connection is still active. The system does not provide music to callers in a
multiple-party connection who are in queue, on hold, or parked.
For more information on locally-sourced Music-on-Hold, see the Locally Sourced
Announcements and Music feature in Avaya Aura™ Communication Manager Feature
Description and Implementation, 555-245-205.

Locally sourced announcements and music

The Locally Sourced Announcements and Music feature is based on the concept of audio
source groups. This feature allows announcement and music sources to be located on any or all
of the Voice Announcement with LAN (VAL) boards or on virtual VALs (vVAL) in a media
gateway. The VAL or vVAL boards are assigned to an audio group. The audio group is then
assigned to an announcement or audio extension as a group sourced location. When an
incoming call requires an announcement or Music-on-Hold, the audio source that is closest to
the incoming call trunk plays.

Administering Avaya Aura™ Communication Manager May 2009 53

Chapter 2: Planning the System

Storing audio locally minimizes audio distortion because the audio is located within the same
port network or gateway as the caller. Therefore, this feature improves the quality of
announcements and music on hold. This feature also reduces resource usage, such as VoIP
resources, because the nearest available audio source of an announcement or music is played.
Locally Sourced Announcements and Music also provides a backup for audio sources because
multiple copies of the audio files are stored in multiple locations. Audio sources are assigned
either to an audio group or a Music-on-Hold group.
An audio group is a collection of identical announcement or music recordings stored on one or
more VAL or vVAL boards. The audio group can contain announcements and music. The
nearest recording to a call plays for that call.
A Music-on-Hold (MOH) group is a collection of externally connected and continuously playing
identical music sources. An example of a Music-on-Hold source is a radio station connected to
a media gateway using an analog station port. Multiple Music-on-Hold sources can be used in
the same system. Like the audio group, the nearest music source to a call plays for that call.
As with the Music-on-Hold feature, only one music source is defined for a system or for a tenant
partition. However, you can define a music source as a group of Music-on-Hold sources.
Therefore, both non-tenant and tenant systems can use the group concept to distribute
Music-on-Hold sources throughout a system.

Adding an audio group

To add an audio group:
1. Type add audio-group n, where n is the group number you want to assign to this audio
group, or next to assign the next available audio group number in the system. Press
Enter.
The system displays the Audio Group screen.
2. In the Group Name field, type an identifier name for the group.
3. In the Audio Source Location fields, type in the VAL boards or vVAL location designators
for each audio source in the audio group.
4. Press Enter to save your changes.

Adding a Music-on-Hold group

To add a Music-on-Hold group:
1. Type add moh-analog-group n, where n is the Music-on-Hold group number. Press
Enter.
The system displays the MOH Group screen.
2. In the Group Name field, type in an identifier name for the Music-on-Hold group.
3. In the MOH Source Location numbered fields, type in the Music-on-Hold VAL or vVAL
source locations.

54 Administering Avaya Aura™ Communication Manager May 2009

 Setting up Music-on-Hold

4. Press Enter to save your changes.

Setting system parameters for Music-on-Hold

You must administer the Music-on-Hold (MOH) feature at the system level to allow local callers
and incoming trunk callers to hear music while on hold. Note that if your system uses Tenant
Partitioning, you cannot set up Music on Hold this way. See Providing MOH Service for Multiple
Tenants on page 55 for more information.
To set system parameters for MOH:
1. Type change system-parameters features. Press Enter.
The system displays the Feature-Related System Parameters screen.
2. In the Music/Tone On Hold field, type music.
The system displays the Type field.
3. In the Type field, enter the type of music source you want to utilize for MOH: an extension
(ext), an audio group (group), or a port on a circuit pack (port).
4. In the text field that appears to the right of your Type selection, type the extension number,
the audio group, or the port address of the music source.
5. In the Music (or Silence) on Transferred Trunk Calls, type all.
6. Press Enter to save your changes.
7. Now administer a class of restriction with Hear System Music on Hold set to y, to allow
your local users to hear Music-on-Hold.

Providing MOH Service for Multiple Tenants

If you manage the switching system for an entire office building, you might need to provide
individualized telephone service for each of the firms who are tenants. You can set up your
system so that each tenant can have its own attendant, and can chose to have music or play
special announcements while callers are on hold.
Before you can administer tenants in your system, Tenant Partitioning must be set to y on the
System Parameters Customer-Options (Optional Features) screen. This setting is controlled by
your license file.
The following example illustrates how to administer the system to allow one tenant to play
Country music for callers on hold, and another to play Classical music.
1. Type change music-sources. Press Enter.
The system displays the Music Sources screen.
2. For Source No 1, enter music in the Type column. A Type field appears under the
Source column.
3. In the Type field, enter port. A blank text field appears.

Administering Avaya Aura™ Communication Manager May 2009 55

Chapter 2: Planning the System

4. Enter the port number, 01A1001 in this case, in the text field.
5. In the description field, enter Country.
6. Move to Source 3, and enter music in the Type column, port in the Type field, 01A1003
for the port number, and Classical for the Description.
7. Press Enter to save your changes.
8. Type change tenant 1. Press Enter.
The system displays the Tenant screen.
9. In the Tenant Description field, type Dentist.
This identifies the client in this partition.
10. In the Attendant Group field, type 1.
Note:
Note: The attendant group number must also appear in the Group field of the Attendant
Console screen for this tenant.
11. In the Music Source field, type 1.
Callers to this tenant will now hear country music while on hold.
12. Press Enter to save your changes.
13. To administer the next partition, type change tenant 2. Press Enter.
14. Administer this tenant, Insurance Agent, to use Attendant Group 2 and Music Source 3. Be
sure to change the Attendant Console screen so that this attendant is in group 2.
This tenant’s callers will hear classical music on hold.

More MOH information

If a call with either Data Privacy or Data Restriction activated is placed on hold, the Music/Tone
on Hold is withheld. This is to prevent transmission of a musical tone that a connected data
service might falsely interpret as a data transmission.
If you administer the Music/Tone on Hold field to provide music, the system provides the music
after a hunt group or Automatic Call Distribution (ACD) split delayed announcement.
Music on Hold might sound distorted when played to IP trunks or to IP telephones through
certain codecs, particularly the G.723 codec. You can provide different on-hold materials for
these endpoints. Using the instructions for Providing MOH Service for Multiple Tenants, create
one tenant partition for all endpoints that do not use the G.723 codec and administer Music on
Hold for this tenant. Create another tenant partition for endpoints that use the G.723 codec and
administer silence, news, or other material that does not sound distorted for these endpoints.

56 Administering Avaya Aura™ Communication Manager May 2009

 Receiving Notification in an Emergency

Receiving Notification in an Emergency

If one of your users calls an emergency service such as the police or ambulance, someone,
perhaps the receptionist, security or the front desk, needs to know who made the call. Thus,
when the emergency personnel arrive, they can be directed to the right place.
You can set up Communication Manager to alert the attendant and up to ten other extensions
whenever an end-user dials an emergency number. The display on the notified user’s telephone
shows the name and number of the person who placed the emergency call. The telephones
also ring with a siren-type alarm, which users must acknowledge to cancel.

Before you start

Decide if you want one user to be able to acknowledge an alert, or if all users must respond
before an alert is cancelled.
Verify that the ARS field is y on the System Parameters Customer-Options (Optional Features)
screen. For information about this screen, see Avaya Aura™ Communication Manager Screen
Reference, 03-602878.
Make sure that the extensions you notify belong to physical digital display telephones. Refer to
Telephone Reference documentation for a list of telephone types. When you assign crisis alert
buttons to the telephones, check the Type field on the Station screen to be sure you are not
using a virtual extension.

Instructions
In this example, we will set up the system to notify the attendant and the security guards at all 3
entrances when someone dials the emergency number 5555. All three guards must
acknowledge the alert before it is silent.
1. Type change ars analysis n. Press Enter.
The system displays the ARS Digit Analysis Table screen.
2. In the Dialed String field, type 5555.
This is the number that end-users dial to reach emergency services.
3. In the Total Min and Max fields, type 4.
In this example, the user must dial all 4 digits for the call to be treated as an emergency
call.
4. In the Route Pattern field, type 1.
In this example, we use route pattern 1 for local calls.

Administering Avaya Aura™ Communication Manager May 2009 57

Chapter 2: Planning the System

5. In the Call Type field, type alrt.

This identifies the dialed string 5555 as one that activates emergency notification.
6. Press Enter to save your changes.
Now set up the attendant console to receive emergency notification.
7. Type change attendant 1. Press Enter.
The system displays the Attendant Console screen.
8. In the feature button area, assign a crss-alert button.
9. Press Enter to save your changes.
10. Assign a crss-alert button to each security guard’s telephone.
You cannot assign this button to a soft key. See Adding Feature Buttons on page 105 for
more information.
Finally, we make sure that all security personnel and the attendant will have to acknowledge the
alert.
11. Type change system-parameters crisis-alert. Press Enter.
The system displays the Crisis Alert System Parameters screen.
12. Go to the Every User Responds field and type y.
13. Press Enter to save your changes.

More information
Attendants cancel an alert by pressing the crisis alert button three times. The first button push
turns off the siren, the second stops the lamp from flashing, and the third clears the display.
Digital telephone users cancel the siren by pushing the crisis alert button. If you have set the
system so that only one user needs to respond, this stops the alerting at all telephones. If all
users must respond, each telephone continues to alert until that user presses the crisis alert
button to acknowledge the alarm. The emergency caller’s name and extension remain on the
display at this point. To completely cancel an alert and clear their displays, users press the
Normal button.
Once you administer Crisis Alert, Communication Manager still records each emergency call
and sends a record to the journal printer, if available. If not, you can view the emergency log
with the command list emergency.

58 Administering Avaya Aura™ Communication Manager May 2009

 Notifying a Digital Pager of an Emergency

Related topics
To determine what types of digital telephones have displays, see the Telephone Reference
documentation
For information on setting up Centralized Automatic Message Accounting (CAMA) trunks and
providing Caller’s Emergency Service Identification (CESID) information to your local
community’s Enhanced 911 system, see the CAMA Numbering Format screen,
For information about updating station location information without having to change the USA
911 system’s Automatic Location Identification database, see the Emergency Location
extension field in the Station screen.
For information on how to administer IP telephones to make emergency calls, see Setting up
emergency calls on IP telephones on page 95.
For more information on individual features, see Avaya Aura™ Communication Manager
Feature Description and Implementation, 555-245-205.

Notifying a Digital Pager of an Emergency

You also have the option of having your emergency calls go to a digital pager. When someone
dials an emergency number (for example, 911), the system sends the extension and location
(that originated the emergency call) to the administered pager.

Before you start

● You need to administer a crss-alert button on at least one of the following.
- Attendant Console (use the change attendant command)
- Digital telephone set (use the change station command)
● The ARS Digit Analysis Table must have emergency numbers in the Call Type column set
to alrt (crisis alert).
● You need a digital numeric pager.

Administering Avaya Aura™ Communication Manager May 2009 59

Chapter 2: Planning the System

Instructions
To set up crisis alert to a digital pager:
1. Type change system-parameters crisis-alert. Press Enter.
The system displays the Crisis Alert System Parameters screen.
2. In the Alert Pager field, type y.
This allows you to use the Crisis Alert to a Digital Pager feature and causes additional
crisis alert administration fields to appear.
3. In the Originating Extension field, type a valid unused extension to send the crisis alert
message.
We’ll type 7768.
4. In the Crisis Alert Code field, type 911.
This is the number used to call the crisis alert pager.
5. In the Retries field, type 5.
This is the number of additional times the system tries to send out the alert message in
case of an unsuccessful attempt.
6. In the Retry Interval (sec) field, type 30.
This is length of time between retries.
7. In the Main Number field, type the number that is to be displayed at the end of the pager
message.
We’ll type 303-555-0800.
8. In the Pager Number field, type the number for the pager.
We’ll type 303-555-9001.
9. In the Pin Number field, type pp77614567890.
This is the PIN number, if required, for the pager. Insert any pause digits (pp) as needed to
wait for announcements from the pager service to complete before sending the PIN.
10. In the DTMF Duration - Tone (msec) field, type 100.
This is the length of time the DTMF tone is heard for each digit.
11. In the Pause (msec) field, type 100.
This is the length of time between DTMF tones for each digit.
12. Press Enter to save your changes.

60 Administering Avaya Aura™ Communication Manager May 2009

 Other Useful Settings

Related topics
Refer to the Crisis Alert feature in Avaya Aura™ Communication Manager Feature Description
and Implementation, 555-245-205, for more detailed information.

Other Useful Settings

There are many settings that control how your system operates and how your users telephones
work. Most of these you administer through one of the System Parameters screens. This
section describes a few of the items you can enable in your system to help your users work
more efficiently. See the Feature-Related System Parameters screen for a more detailed
description of the available system settings.

Automatic callback if an extension is busy

You can allow users to request that the system call them back if they call a user whose
telephone is busy. For more information, see Automatic Callback in Avaya Aura™
Communication Manager Feature Description and Implementation, 555-245-205.

Automatic hold
You can set a system-wide parameter that allows your users to initiate a call on a second line
without putting the first call on Hold. This is called Automatic Hold, and you enable it on the
Feature-Related System Parameters screen. If you do not turn this on, the active call drops
when a the user presses the second line button.

Bridging onto a call that has gone to coverage

You can allow users to join (bridge) on to a call that rang at their extension and then went to
coverage before they could answer. For more information, see Temporary Bridged Appearance
in Avaya Aura™ Communication Manager Feature Description and Implementation,
555-245-205.

Administering Avaya Aura™ Communication Manager May 2009 61

Chapter 2: Planning the System

Distinctive ringing
You can establish different ringing patterns for different types of calls. For example, you can
administer your system so that internal calls ring differently from external calls or priority calls.
For more information, see Distinctive Ringing in Avaya Aura™ Communication Manager
Feature Description and Implementation, 555-245-205.

Warning when telephones are off-hook

You can administer the system so that if a telephone remains off-hook for a given length of time,
Communication Manager sends out a warning. This is particularly useful in hospitals, where the
telephone being off-hook might be an indication of trouble with a patient. See the Class of
Service screen for more information.

Warning users if their calls are redirected

You can warn analog telephone users if they have features active that might redirect calls. For
example, if the user has activated send all calls or call forwarding, you can administer the
system to play a special dial tone when the user goes off-hook. See Distinctive Ringing in
Avaya Aura™ Communication Manager Feature Description and Implementation, 555-245-205,
for more information.

Controlling the Calls Your Users Can Make and Receive

Communication Manager provides several ways for you to restrict the types of calls your users
can make, and the features that they can access.
You use class of restriction (COR) to define the types of calls your users can place and receive.
Your system might have only a single COR, a COR with no restrictions, or as many CORs as
necessary to effect the desired restrictions.
You will see the COR field in many different places throughout Communication Manager when
administering telephones, trunks, agent logins, and data modules, to name a few. You must
enter a COR on these screens, although you control the level of restriction the COR provides.

62 Administering Avaya Aura™ Communication Manager May 2009

 Controlling the Calls Your Users Can Make and Receive

Strategies for assigning CORs

The best strategy is to make it as simple as possible for you and your staff to know which COR
to assign when administering your system. You can create a unique COR for each type of user
or facility, for example, call center agents, account executives, administrative assistants, Wide
Area Telecommunications Service (WATS) trunks, paging zones or data modules.
You can also create a unique COR for each type of restriction, for example, toll restriction, or
outward restriction. If you have a number of people who help you administer your system, using
this method would also require the additional step of explaining where you wanted to use each
type of restriction.
Note:
Note: COR-to-COR calling restrictions from a station to a trunk do not apply when
Automatic Alternate Routing (AAR), Automatic Route Selection (ARS), or Uniform
Dial Plan (UDP) is used to place the call. In these cases, use Facility Restriction
Levels to block groups of users from accessing specific trunk [Link] Class
of Restriction and Facility Restriction Levels in Avaya Aura™ Communication
Manager Feature Description and Implementation, 555-245-205, for more
information.
To find out what CORs are administered in your system already, type list cor. You can also
display information for a single COR by typing list cor #.

Allowing users to change CORs

You can allow specific users to change their Class of Restriction (COR) from their telephones
using a Change COR feature access code. You can also limit this feature by insisting that the
user enter a password as well as a feature access code before they can change their COR. The
Station Lock feature also allows users to change their own COR. For more information on the
Station Lock feature, see Station Lock on page 64.
Before you start:
● Be sure that Change COR by FAC field is set to y on the System-Parameters
Customer-Options (Optional Features) screen. Note that you cannot have both Change
COR by FAC and Tenant Partitioning enabled.
● Be sure that each user (who you want to allow to change a COR) has a class of service
with console permissions. For more information about console permissions, see the Class
of Service screen.

Administering Avaya Aura™ Communication Manager May 2009 63

Chapter 2: Planning the System

To allow users to change their own class of restriction, you must define a feature access code
and can, optionally, create a password. For example, we will create a change COR feature
access code of *55 and a password of 12344321.
1. Type change feature-access-codes. Press Enter.
The system displays the Feature Access Code (FAC) screen.
2. Move the cursor to the Change COR Access Code field.
3. Type *55 in the access code field.
4. Press Enter to save your changes.
Now we have to define the password.
5. Type change system-parameters features. Press Enter.
The system displays the Feature-Related System Parameters screen. Press Next Page to
find the Automatic Exclusion Parameters section.
6. Move to the Password to Change COR by FAC field and enter 12344321.
This field determines whether or not Communication Manager requires the user to enter a
password when they try to change their COR. Avaya recommends that you require a
password.
7. Press Enter to save your changes.

Station Lock
Station Lock provides users with the capability to manually lock their stations, using a button or
feature access code, in order to prevent unauthorized external calls from being placed.
Station Lock can prevent unauthorized external calls. Telephones can be remotely locked and
unlocked. Station Lock allows users to:
● change their Class of Restriction (COR); usually the lock COR is set to fewer calling
permissions than the station’s usual COR
● lock their telephones to prevent unauthorized outgoing calls.
● block outgoing calls and still receive incoming calls.
● block all outgoing calls except for emergency calls.
Station Lock is activated by pressing a telephone button, which lights the button indicator, or
dialing a FAC.
Analog and XMOBILE stations must dial a FAC to activate the feature. The user hears a special
dial tone on subsequent origination attempts from the telephone to indicate that the lock feature
is active.

64 Administering Avaya Aura™ Communication Manager May 2009

 Station Lock

Digital stations (including DCP, BRI, IP hardphones and softphones) access Station Lock with a
feature button or via a FAC. If a digital station has a Station Lock button but activates the
feature with the FAC, the LED for the button lights and no special dial tone is provided.
However, if a digital station does not have a Station Lock button and activates the feature with
the FAC, a special dial tone is provided.
A station can be locked or unlocked from any other station if the FAC is used and the Station
Security Code is known. The attendant console can never be locked but can be used to lock or
unlock other stations. A station also can be locked or unlocked via a remote access trunk.

Interactions
● Attendant Console
Station Lock cannot be used for attendant consoles but it can be assigned to regular digital
stations that might also have console permissions. The FAC cannot be used to activate
Station Lock for the attendant console, but the FAC can be dialed from the attendant
console in an attempt to remotely activate or deactivate Station Lock for another station.
● Personal Station Access (PSA)
Station Lock can be used for PSA stations as long as they are associated with an
extension. When stations are disassociated, Station Lock cannot be activated.
● Remote Access
After a remote user dials a valid barrier code, the user receives system dial tone. To
activate/deactivate Station Lock, the user must dial the FAC, then the extension number,
then the security code number.

Station Lock by time of day

Beginning with Communication Manager 4.0 or later, you can you can also lock stations using a
Time of Day (TOD) schedule.
To engage the TOD station lock/unlock you do not have to dial the station lock/unlock FAC, or
use stn-lock button push.
When the TOD feature activates the automatic station lock, the station uses the Class of
Restriction (COR) assigned to the station lock feature for call processing. The COR used is the
same as it is for manual station locks.
The TOD lock/unlock feature does not update displays automatically, because the system
would have to scan through all stations to find the ones to update.

Administering Avaya Aura™ Communication Manager May 2009 65

Chapter 2: Planning the System

The TOD Station Lock feature works as follows:

● If the station is equipped with a display, the display will show “Time of Day Station
Locked”, if the station invokes a transaction which is denied by the Station Lock COR.
Whenever the station is within a TOD Lock interval, the user will hear a special dial tone
instead of the normal dial tone, if the special dial tone is administered.
● For analog stations or without a display, the user hears a special dial tone. The special dial
tone has to be administered and the user hears it when the station is off hook.
After a station is locked by TOD, it can be unlocked from any other station if the Feature Access
Code (FAC) or button is used. You have to also know the Station Security Code, and that the
Manual-unlock allowed? field on the Time of Day Station Lock Table screen is set to y.
Once a station has been unlocked during a TOD lock interval, the station remains unlocked until
next station lock interval becomes effective.
If the station was locked by TOD and by Manual Lock, an unlock procedure will unlock the
Manual Lock as well as the TOD Lock (“Manual-unlock allowed?” field on the Time of Day
Station Lock Table screen is set to y).
The TOD feature does not unlock a manually locked station.
Note:
Note: The attendant console cannot be locked by TOD or manual station lock.

Screens for administering Station Lock

Screen name Purpose Fields

COR Administer a Class of Station Lock COR

Restriction (COR) that
allows the user to activate
Station Lock with a feature
access code (FAC).
Feature Access Code Assign one FAC for Station Station Lock Activation
(FAC) Lock activation, and another Station Lock Deactivation
FAC for Station Lock
Deactivation.
Station Assign the user a COR that COR
allows the user to activate Time of Day Lock Table
Station Lock with an FAC.
Assign a sta-lock feature Any available button field in
button for a user. the BUTTON
ASSIGNMENTS area
Assign a Station Security Security Code
Code (SSC) for a user.

66 Administering Avaya Aura™ Communication Manager May 2009

 Station Lock

Screen name Purpose Fields

Time of Day Station Administer station lock by Table Active?

Lock Table time of day. Manual Unlock Allowed?
Time Intervals

Administering Avaya Aura™ Communication Manager May 2009 67

Chapter 2: Planning the System

68 Administering Avaya Aura™ Communication Manager May 2009

Chapter 3: Managing Telephones

Installing New Telephones

Simple administration allows you to plug a telephone into a jack and dial a sequence to start up
service to the telephone. The dialing sequence sets up an association between the telephone
and the corresponding station administration.

! SECURITY ALERT:
SECURITY ALERT: If you do not manage this feature carefully, its unauthorized use might cause you
security problems. Consult the Avaya Products Security Handbook for
suggestions on how to secure your system and find out about obtaining additional
security information.
For traditional instructions, see Installing New Telephones.

Before you start

On the Feature-Related System Parameters screen, be sure the Customer Telephone
Activation (CTA) Enabled field is y and the TTI Enabled field is y.
Complete the Station screen for the new telephone and type x in the port field. Note that the
telephone type must match the board type. For example, match a two-wire digital telephone
with a port on a two-wire digital circuit pack. Use this procedure with all circuit-switched
telephones except BRI (ISDN) and model 7103A.

Tip:
Tip: See Completing the Station screens for more information. See Duplicating
telephones if you want to add a number of telephones with similar settings.

Administering Avaya Aura™ Communication Manager May 2009 69

Chapter 3: Managing Telephones

Instructions

! CAUTION:
CAUTION: You can destroy your hardware if you attempt to connect an analog telephone to
a digital port.
To associate a telephone with existing x-port station administration, complete the following
steps from the telephone you want to install:
1. Plug the telephone into the wall jack.
2. Lift the receiver and continue if you hear dial tone.
3. Dial #*nnnn, where nnnn is the extension number of the telephone you are installing.
4. Hang up after you receive confirmation tone.
5. Dial a test call to confirm that the telephone is in service.
If possible, call a telephone with a display so the person answering can confirm that you
entered the correct extension number.
6. Repeat the process until all new telephones have been installed.
7. For security reasons, you should disable this feature when you are done. At the system
administration terminal type change system-parameters features to access the
Feature-Related System Parameters screen.
8. Type n in the Customer Telephone Activation (CTA) Enabled field.
9. Press Enter to save your changes.
10. Type save translations. Press Enter to permanently save the changes.
a. Fixing problems
If you misdial and the wrong extension is activated for the telephone you are using,
use the terminal translation initialization (TTI) unmerge feature access code to
"uninstall" the telephone before you try again.

Adding new telephones

When you are asked to add a new telephone to the system, what do you do first? To connect a
new telephone you need to do three things:
● find an available port
● wire the port to the cross-connect field or termination closet
● tell the telephone system what you’re doing

70 Administering Avaya Aura™ Communication Manager May 2009

 Adding new telephones

Before you can determine which port to use for the new telephone, you need to determine what
type of telephone you are installing, what ports are available, and where you want to install the
telephone.
To add an IP telephone, see Adding an IP telephone on page 92.

Gathering necessary information

Gather the following information:
1. Determine whether the telephone is an analog, digital, ISDN, or hybrid set. You can also
administer a virtual telephone, one without hardware at the time of administration.
You need this information to determine the type of port you need, because the port type
and telephone type must match. If you do not know what type of telephone you have, see
the Type field on the Station screen for a list of telephones by model number.
2. Record the room location, jack number, and wire number.
You might find this information on the jack where you want to install the telephone,
recorded in your system records, or from the technician responsible for the physical
installation.
3. Display the available boards (cards) and ports.
To view a list of boards on your system, type list configuration station. Press
Enter.
The system displays the System Configuration screen, which shows all the boards on your
system that are available for connecting telephones. You can see the board number,
board type, circuit-pack type, and status of each board’s ports.
4. Choose an available port and record its port address.
Each port that is available or unassigned is indicated by a ‘u.’ Choose an available port
from a board type that matches your telephone type (such as a port on an analog board for
an analog telephone).
Every telephone must have a valid port assignment, also called a port address. The
combined board number and port number is the port address. So, if you want to attach a
telephone to the 3rd port on the 01C05 board, the port address is 01C0503 (01=cabinet,
C=carrier, 05=slot, 03=port).

Tip:
Tip: If you add several telephones at one time, you might want to print a paper copy of
the System Configuration screen. To print the screen to a printer attached to the
system terminal, type list configuration station print. Press Enter.
To print to the system printer that you use for scheduled reports, type list
configuration station schedule immediate. Press Enter.

Administering Avaya Aura™ Communication Manager May 2009 71

Chapter 3: Managing Telephones

5. Choose an extension number for the new telephone.

The extension you choose must not be assigned and must conform to your dial plan. You
should also determine whether this user needs an extension that can be directly dialed
(DID) or reached via a central telephone number.
Be sure to note your port and extension selections on your system’s paper records.

Physically connecting the telephone

Once you have collected all the information, you are ready to physically wire the port to the
cross-connect field.
If you have an Avaya technical support representative or on-site technician who completes the
physical connections, you need to notify them that you are ready to add the telephone to the
system. To request that Avaya install the new connections, call your Avaya technical support
representative to place an order.
If you are responsible for making the connections yourself and if you have any questions about
connecting the port to the cross-connect field, see your system installation guide.
Now you are ready to configure the system so that it recognizes the new telephone.

Before you start

To download language display labels for telephones, set the Display Language field on the
Station screen to english, spanish, italian, french, user-defined, or unicode.
Note:
Note: Unicode display is only available for Unicode-supported telephones. Currently,
the 4610SW, 4620SW, 4621SW, and 4622SW, 16xx series telephones, and 96xx
series IP Phones support Unicode display. Unicode is also an option for the
2420J telephone when Display Character Set on the System Parameters
Country-Options screen is katakana. For more information on the 2420J, see
2420 Digital Telephone User's Guide, 555-250-701.
For a Eurofont character display for the 2420/2410 telephone, set the Display Character Set
field on the System-Parameters Country-Options screen to Eurofont.
For a Katakana character display for the 2420/2410 telephone, set the Display Character Set
field on the System-Parameters Country-Options screen to Katakana.

72 Administering Avaya Aura™ Communication Manager May 2009

 Adding new telephones

Completing the Station screens

The information that you enter on the Station screen advises the system that the telephone
exists and indicates which features you want to enable on the telephone.
Communication Manager allows customers enter extensions with punctuation on the command
line. Punctuation is limited to dashes (hyphens) and dots (periods). Communication Manager
cannot process a command like add station 431 4875. You must format a command in
one of these ways:
● add station 431-4875
● add station 431.4875
● add station 4314875
Make sure the extension conforms to your dial plan. You can also use the add station next
command to add a telephone to the next available extension.
To access the Station screen for the new telephone:
1. Type add station nnnn, where nnnn is the extension for the new telephone. Press
Enter.
Note:
Note: If you have Terminal Translation Initialization (TTI) enabled, you might receive the
following error message when attempting to add a new station: "No station/TTI
port records available; ‘display capacity’ for their usage." If this occurs, try
one or more of the following:
- Remove any DCP or Analog circuit packs that have no ports administered on
them.
- If you are not using TTI or any related feature (such as PSA or ACTR), set the
Terminal Translation Initialization (TTI) Enabled? field on the
Feature-Related System Parameters screen to n.
- Contact your Avaya technical support representative.
For more information on TTI, see Terminal Translation Initialization in Avaya
Aura™ Communication Manager Feature Description and Implementation,
555-245-205.
For more information on the System Capacity screen, see Maintenance
Commands for Avaya Aura™ Communication Manager, Media Gateways and
Servers, 03-300431.
When the Station screen appears, you see the extension number and some default field
values. For example, the following screen is for a new telephone, displayed by typing add
station next.

Administering Avaya Aura™ Communication Manager May 2009 73

Chapter 3: Managing Telephones

2. Type the model number of the telephone into the Type field.
For example, to install a 6508D+ telephone, type 6480D+ in the Type field. Note that the
displayed fields might change depending on the model you add.
3. Type the port address in the Port field.
Note:
Note: Port 1720 is turned off by default to minimize denial of service situations. This
applies to all IP softphones release 5.2 or later. You can change this setting, if
you have root privileges on the system, by typing the command: /opt/ecs/
sbin ACL 1720 on or off.
4. Type a name to associate with this telephone in the Name field. The name you enter
displays on called telephones that have display capabilities. Some messaging
applications, such as Communication Manager Messaging, recommend that you enter the
user’s name (last name first) and their extension to identify the telephone. The name
entered is also used for the integrated directory.
Note:
Note: To hide a name in the integrated directory, enter two tildes (~~} before the name
when you assign it to the telephone, and set Display Character Set on the
System Parameters Country-Options screen to Roman. This hides the name in
the integrated directory. The tildes are not displayed with Caller ID name. Note
that this is the only method to hide a name in the integrated directory. Also, if a
name is entered with only one tilde (~), the name is converted to Eurofont
characters.
Note:
Note: For 4610SW, 4620SW, 4621SW, and 4622SW, 16xx series telephones, and
96xx series IP Phones, the Name field is supported by Unicode language display.
You must be using ASA or MSA. For more information on Unicode language
display, see Administering Unicode display on page 170. Unicode is also an
option for the 2420J telephone when Display Character Set on the System
Parameters Country-Options screen is katakana. For more information on the
2420J, see 2420 Digital Telephone User's Guide, 555-250-701.
5. Press Enter to save your changes.
To make changes to this new telephone, such as assigning coverage paths or feature buttons,
type change station nnnn, where nnnn is the extension of the new telephone. Press
Enter. See Adding Feature Buttons on page 105 for more information.

74 Administering Avaya Aura™ Communication Manager May 2009

 Duplicating telephones

Duplicating telephones
A quick way to add telephones is to copy the information from an existing telephone and modify
it for each new telephone. For example, you can configure one telephone as a template for an
entire work group. Then, you duplicate the template Station screen to add all the other
extensions in the group.
Note that only telephones of the same model can be duplicated. The duplicate command
copies all the feature settings from the template telephone to the new telephones.
To duplicate an existing telephone:
1. Type display station nnnn, where nnnn is the extension of the Station screen you
want to duplicate to use as a template. Press Enter. Verify that this extension is the one
you want to duplicate.
Press Cancel to return to the command prompt.
2. Type duplicate station nnnn, where nnnn is the extension you want to duplicate.
Press Enter.
The system displays a blank duplicate Station screen.
Alternately, you can duplicate a range of stations by typing duplicate station
<extension> start nnnn count <1-16>, where <extension> represents the
station you want to duplicate, nnnn represents the first extension number in a series, and
count <1-16> represents the number of consecutive extensions after the start
extension to create as duplicates.
Note:
Note: If you want to duplicate the settings of another station, but need to change the
port or station type, you must individually administer each station after creating
the duplicates. If you want to duplicate the station using duplicate station
<extension> start nnnn count <1-16>, you cannot change the station
type and the port.
3. Type the extension, port address, and telephone name for each new telephone you want
to add.
The rest of the fields on the Station screen are optional. You can complete them at any
time.
4. Press Enter to save your changes to system memory.
To make changes to these telephones, such as assigning coverage paths or feature buttons,
type change station nnnn, where nnnn is the extension of the telephone that you want to
modify. Press Enter

Administering Avaya Aura™ Communication Manager May 2009 75

Chapter 3: Managing Telephones

Related topics
You can also add multiple call center agents, all with the same settings based on an agent that
is already administered. Enter command duplicate agent-loginID and the extension of
the agent you want to duplicate, then start and the extension you want to use for the first new
agent, then count and the number of agents you want to add. Fill in the information on the
Agent LoginID screen. For more information, see Avaya Aura™ Call Center 5.2 Automatic Call
Distribution (ACD) Reference, 07-602568.

Using an alias
Not every telephone model or device has a unique Station screen in the system. You might
have to use an available model as an "alias" for another. If you need to enter a telephone type
that the system does not recognize or support, use an alias. Defining aliases is also a useful
method to identify items that act as analog stations on Communication Manager, such as fax
machines, modems, or other analog device.
If you purchase a telephone model that is newer than your system, you can alias this telephone
to an available model type that best matches the features of your new telephone. See your
telephone’s manual to determine which alias to use. If your manual does not have this
information, you can contact the DEFINITY helpline for an appropriate alias.
For example, we will create two aliases: one to add a new 6220 telephone and one to add
modems to our system.
1. See your new telephone’s manual to find the correct alias.
In our example, we find that the 6220 should be administered on an older system as a
2500 telephone.
2. Type change alias station. Press Enter.
The system displays the Alias Station screen.
3. Enter 6220 in the Alias Set Type field.
This is the name or model of the unsupported telephone.
4. Enter 2500 in the Supported Set Type field.
Enter the supported model in this field.
5. Enter modem in the second Alias Set Type field.
You can call the alias set anything you like. Once you define the alias, you can use the
alias set in the Type field on the Station screen.

76 Administering Avaya Aura™ Communication Manager May 2009

 Customizing your telephone

6. Enter 2500 in the second Supported Set Type field.

Entering 2500 indicates to the system that these models are basic analog devices.
7. Press Enter to save your changes.
Now you can follow the instructions for adding a new telephone (or adding a fax or modem).
Communication Manager now recognizes the new type (6220 or modem) that you enter in the
Type field.
Be sure to see your telephone’s manual for instructions on how to set feature buttons and call
appearance buttons. Note that if you need to use an alias for a telephone, you might not be able
to take advantage of all the features of the new telephone.

Customizing your telephone

This section provides recommendations for setting up or enhancing your personal telephone.
You need a telephone that is powerful enough to allow you to use all the features you might give
to other employees. You might want to add feature buttons that allow you to monitor or test the
system, so that you can troubleshoot the system from your telephone.
It will be much easier to monitor and test your system if you have a telephone with:
● a large multi-button display (such as 8434D or 8410D)
● a class of service (cos) that has console permissions
● the following feature buttons
- ACA and Security Violations (assign to lamp buttons)
- Busy verify
- Cover message retrieval button
- Major/minor alarm buttons
- Trunk ID buttons
- Verify button
Once you select a telephone, you’ll want to determine if you want to place this telephone at your
desk or in the server room. If the telephone is in the server room (near the system
administration terminal), you can quickly add or remove feature buttons to test features and
facilities. You might decide that you want a telephone at both your desk and in the server room
— it’s up to you.

Administering Avaya Aura™ Communication Manager May 2009 77

Chapter 3: Managing Telephones

You might also find it handy to set up multiple telephones for testing applications and features
before you provide them to users. You might want to have a telephone that mimics each type of
user telephone in your organization. For example, if you have four basic telephone templates,
one for executives, one for marketing, one for technicians, and one for other employees, you
might want to have examples of each of these telephones so you can test new features or
options. Once you are satisfied that a change works on the test telephone, you can make the
change for all the users in that group.

Upgrading telephones
If you want to change telephone types for a user and do not need to change locations, you can
just access the Station screen for that extension and enter the new model number.

Tip:
Tip: This method can be used only if the new telephone type matches the existing port
type (such as digital telephone with a digital port).
For example, if a user at extension 4556 currently has a 7410+ telephone and you want to
replace it with a new 8411D telephone:
1. Type change station 4556. Press Enter.
The Station screen for 4556 appears. For information about this screen, see Avaya Aura™
Communication Manager Screen Reference, 03-602878.
2. Overwrite 7410+ with 8411D in the Type field.
Now you can access the functions and feature buttons that correspond to an 8411D
telephone.

Swapping telephones
You will often find that you need to move or swap telephones. For example, employees moving
from one office to another might want to bring their telephones. In this case, you can use X ports
to easily swap the telephones.
In general, to swap one telephone (telephone A) with another telephone (B), you change
telephone A’s port assignment to x, change telephone B’s port assignment to A’s old port, and,
finally, change the x for telephone A to B’s old port. Note that these swapping instructions work
only if the two telephones are the same type (both digital or both analog, and so on.).

78 Administering Avaya Aura™ Communication Manager May 2009

 Using ACTR to move telephones

For example, to swap telephones for extension 4567 (port 01C0505) and extension 4575 (port
01C0516), complete the following steps:
1. Type change station 4567. Press Enter.
2. Record the current port address (01C0505) and type x in the Port field.
3. Press Enter to save your changes.
4. Type change station 4575. Press Enter.
5. Record the current port address (01C0516).
6. Type 01C0505 in the Port field.
7. Update the Room and Jack fields.
8. Press Enter to save your changes.
9. Type change station 4567 again. Press Enter.
10. Type 01C0516 in the Port field.
This is the port that used to be assigned to extension 4575.
11. Update the Room and Jack fields.
12. Press Enter to save your changes.
13. Physically unplug the telephones and move them to their new locations.
When you swap telephones, the system keeps the old button assignments. If you are swapping
to a telephone with softkeys, the telephone could have duplicate button assignments, because
softkeys have default assignments. You might want to check your button assignments and
modify them as necessary.

Using ACTR to move telephones

Automatic Customer Telephone Rearrangement (ACTR) allows a telephone to be unplugged
from one location and moved to a new location without additional administration in
Communication Manager. Communication Manager automatically associates the extension to
the new port. ACTR works with 6400 Serialized telephones and with the 2420/2410 telephones.
The 6400 Serialized telephone is stamped with the word "Serialized" on the faceplate for easy
identification. The 6400 Serialized telephone memory electronically stores its own part ID
(comcode) and serial number, as does the 2420/2410 telephone. ACTR uses the stored
information and associates the telephone with new port when the telephone is moved.
ACTR is an enhancement to Terminal Translation Initialization (TTI), Personal Station Access
(PSA), Customer Telephone Activation (CTA). ACTR makes it easy to identify and move
telephones.

Administering Avaya Aura™ Communication Manager May 2009 79

Chapter 3: Managing Telephones

! CAUTION:
CAUTION: When a telephone is unplugged and moved to another physical location, the
Emergency Location Extension field must be changed for that extension or the
USA Automatic Location Identification data base must be manually updated. If
the Emergency Location Extension field is not changed or if the USA Automatic
Location Identification data base is not updated, the DID number sent to the
Public Safety Access Point (PSAP) could send emergency response personnel to
the wrong location.

Detailed description
On the Feature-Related System Parameters screen, set the Terminal Translation
Initialization (TTI) Enabled field to y and the TTI State field to voice.
Note:
Note: When a telephone is moved, if there is any local auxiliary power (a power supply
plugged into a local AC outlet), the telephone must be plugged into an AC outlet
at the telephone’s new location. A telephone with remote auxiliary power must be
supplied remote auxiliary power at its new location. If you do not supply auxiliary
power in either case after a telephone is moved, some optional adjuncts (for
example, an expansion module) do not operate.
When you enter always or once in the Automatic Moves field on the Station screen,
Communication Manager adds the extension to its ACTR Move List database. When the
telephone is plugged in, Communication Manager asks the telephone for its serial number and
records the serial number on the ACTR Move List. If you change the entry in the Automatic
Moves field from always or once to no, Communication Manager removes the extension from
the Move List.

Call processing
When a telephone is unplugged while on a call, and a 6400 Serialized telephone or a 2420/
2410 telephone that is administered for automatic moves is plugged into the port within 60
seconds:
● both extensions are placed in idle state
● active calls on either extension are dropped, unless the call is active on a bridged
appearance at some other telephone
● held calls remain in a hold state
● any calls ringing on either extension instantly proceed to the next point in coverage or
station hunting path, unless the call is ringing on a bridged appearance at some other
telephone

80 Administering Avaya Aura™ Communication Manager May 2009

 Using TTI to move telephones

● user actions that were pending when the new telephone was plugged in are aborted

Design considerations
You can use the list station movable command to keep track of extensions on the move
list. Once you reach the maximum number, Communication Manager does not allow additional
extensions.

Administration
Before you start:
● Be sure the TTI field on the Feature-Related System Parameters screen is set to y.
● Before you move a telephone in your system, set the TTI State field to voice on the
Feature-Related System Parameters screen.

Moving telephones
You can allow a telephone to be unplugged from one location and moved to a new location
without additional administration on Communication Manager.
For example, to allow moves anytime for a telephone at extension 1234:
1. Type change station 1234. Press Enter.
2. Move to the Automatic Moves field.
3. Type always in the Automatic Moves field.
4. Press Enter to save your changes.

Using TTI to move telephones

Terminal Translation Initialization (TTI) allows you to merge an x-ported station to a valid port by
dialing a TTI merge code, a system-wide security code, and the x-port extension from a
telephone connected to that port. TTI also allows you to separate an extension from its port by
dialing a similar separate digit sequence. This action causes the station to revert to an x-port.
TTI can be used for implementing telephone and data module moves from office to office. That
is, you can separate a telephone from its port with TTI, unplug the telephone from the jack, plug
in the telephone in a jack in a different office, and merge the telephone to its new port with TTI.

Administering Avaya Aura™ Communication Manager May 2009 81

Chapter 3: Managing Telephones

If you are moving telephones and concerned about security, you might also want to see Setting
up Personal Station Access on page 365 for more information about setting the security code
for each extension.

! SECURITY ALERT:
SECURITY ALERT: If you do not manage this feature carefully, its unauthorized use might cause you
security problems. For example, someone who knows the TTI security code could
disrupt normal business functions by separating telephones or data terminals.
You can help protect against this action by frequently changing the TTI security
code. You can further enhance system security by removing the feature access
code (FAC) from the system when it does not need to be used (for example, there
are no moves going on at present). Consult the Avaya Products Security
Handbook for additional steps to secure your system and find out about obtaining
information regularly about security developments.

Before you start

Before you can merge a telephone, you must set the TTI State field to voice on the
Feature-Related System-Parameters screen. You also must set the extension to match the port
type of the TTI port making the merge request. For example, a digital telephone type can merge
only to a port on a digital board.

! CAUTION:
CAUTION: When a telephone is unplugged and moved to another physical location, the
Emergency Location Extension field must be changed for that extension or the
USA Automatic Location Identification data base must be manually updated. If
the Emergency Location Extension field is not changed or if the USA Automatic
Location Identification data base is not updated, the DID number sent to the
Public Safety Network could send emergency response personnel to the wrong
location.
Note:
Note: You cannot use TTI to change a virtual extension.

82 Administering Avaya Aura™ Communication Manager May 2009

 Using TTI to move telephones

Instructions

Merging an extension with a TTI telephone

! CAUTION:
CAUTION: You can destroy your hardware if you attempt to connect an analog telephone to
a digital port.
To merge an extension to a telephone with TTI, complete the following steps from the telephone
you want to merge:
1. Dial the TTI merge FAC.
- If the code is correct, you receive dial tone.
- If the code is not correct, you receive intercept tone.
2. Dial the TTI security code from the telephone you want to merge.
- If the code is correct, you receive dial tone.
- If the code is not correct, you receive intercept tone.
3. Dial the extension of the telephone you want to merge.
- If the extension is valid, you receive confirmation tone, which might be followed by dial
tone. (It is possible to receive intercept tone immediately following the confirmation
tone. If this happens, you need to attempt the merge again.)
- If the extension is valid, but the extension is being administered, you receive reorder
tone. Try the merge again later.
- If the extension is invalid, you receive intercept tone.
- If the system is busy and cannot complete the merge, you receive reorder tone. Try
the merge again later.
- If the telephone has a download status of pending, you receive reorder tone. You need
to change the download status to complete to successfully complete the TTI merge.

Separating TTI from a telephone

To complete a TTI separation, complete the following steps from the telephone that needs to be
separated:
1. Dial the TTI separate FAC.
2. Dial the TTI security code.
- If the code is correct, you receive dial tone.
- If the code is not correct, you receive intercept tone.

Administering Avaya Aura™ Communication Manager May 2009 83

Chapter 3: Managing Telephones

3. Dial the extension of the telephone to be separated.

- If you have dialed the extension of the telephone currently merged with this telephone,
you receive confirmation tone.
- If you have dialed the extension of the telephone currently merged with this telephone,
but the extension is being administered, you receive reorder tone. Try the separation
again later.
- If you have not dialed the extension of the telephone currently merged with this
telephone, you receive intercept tone.
- If the system is busy and cannot complete the separation, you receive reorder tone.
Try the separation again later.

Fixing problems
If you are having difficulty using TTI, you might want to review the following system restrictions:
● The TTI Ports field on the System Capacity screen (type display capacity) shows the
number of TTI ports used in a server running Communication Manager. This field shows
only the number of TTI ports being administered. If a TTI exceeds the maximum number of
ports, the port is not administered and cannot be added. In that case, a telephone cannot
be added. For details on the System Capacity screen, see Maintenance Commands for
Avaya Aura™ Communication Manager, Media Gateways and Servers, 03-300431.
BRI endpoints are only counted as one TTI port. For example, for every two BRI
endpoints, one TTI port is counted. As such, you can have two telephones assigned to one
port. If either endpoint is administered, the TTI port count is reduced by 1.
● The total number of translated telephones and Voice TTI ports in a system is limited to the
maximum number of administered telephones supported in the system. The total number
of translated data terminals and Data TTI ports in a system is limited to the maximum
number of administered data modules allowed in the system.
● Set the TTI State field to voice and then set the TTI State field to data. When you use this
order, voice and then data, you reduce the chance of a user trying to use TTI on a
data-only terminal that does not have TTI port translation. This can happen when the
number of telephones allowed by the system is twice the number of data terminals. For
example, if the system limit for telephones is 15,000 and 7,500 for data, then when TTI
was turned on for data first, only the first 7,500 unadministered ports would get TTI port
translations.
● When TTI is activated for the system, the following actions take place:
- If the TTI State field was previously activated but in a different state (such as, a voice
to data state), the old TTI translations are removed and the new ones added on a
board by board basis.
- If the TTI State field is set to voice, then default TTI translations are generated for
every unadministered port on all digital, hybrid, and analog boards.

84 Administering Avaya Aura™ Communication Manager May 2009

 Removing telephones

- If the TTI State field is set to data, then default TTI translations are generated for
every unadministered port on all digital and data line boards in the system.
- Whenever a new digital board is inserted when the system is in TTI Data mode, or
when a digital, hybrid, or analog board is inserted when the system is in TTI Voice
mode, the unadministered ports on the board become TTI ports.
- When TTI is deactivated, all translation for the TTI ports are removed in the system;
the ports return to an unadministered state.

Removing telephones
Before you physically remove a telephone from your system, check the telephone’s status,
remove it from any group or usage lists, and then delete it from the system’s memory.
For example, to remove a telephone at extension 1234:
1. Type status station 1234. Press Enter.
The General Status screen appears.
2. Make sure that the telephone:
● is plugged into the jack
● is idle (not making or receiving calls)
● has no messages waiting
● has no active buttons (such as Send All Calls or Call Forwarding)
3. Type list groups-of-extension 1234. Press Enter.
The Extension Group Membership screen shows whether the extension is a member of
any groups on the system.
4. Press Cancel.
5. If the extension belongs to a group, access the group screen and delete the extension
from that group.
For example, if extension 1234 belongs to pickup group 2, type change pickup group
2 and delete the extension from the list.
6. Type list usage extension 1234. Press Enter.
The Usage screen shows where the extension is used in the system.
7. Press Cancel.

Administering Avaya Aura™ Communication Manager May 2009 85

Chapter 3: Managing Telephones

8. If the extension appears on the Usage screen, access the appropriate feature screen and
delete the extension.
For example, if extension 1234 is bridged onto extension 1235, type change station
1235 and remove the appearances of 1234.
9. Type change station 1234. Press Enter.
10. Delete any bridged appearances or personal abbreviated dialing entries. Press Enter.
11. Type remove station 1234. Press Enter.
The system displays the Station screen for this telephone so you can verify that you are
removing the correct telephone.

Tip:
Tip: Be sure to record the port assignment for this jack in case you want to use it again
later.
12. If this is the correct telephone, press Enter.
If the system responds with an error message, the telephone is busy or still belongs to a
group. Press Cancel to stop the request, correct the problem, and enter remove
station 1234 again.
13. Remove the extension from voice mail service if the extension has a voice mailbox.
14. Type save translations. Press Enter to save your changes.
Note that you do not need to delete the extension from coverage paths. The system
automatically adjusts coverage paths to eliminate the extension.
Now you can unplug the set from the jack and store it for future use. You do not need to
disconnect the wiring at the cross-connect field. The extension and port address remain
available for assignment at a later date.
Once you successfully remove a set, that set is permanently erased from system memory. If
you want to reactivate the set, you have to add it again as though it were a new telephone.

Adding a fax or modem

Connecting a fax machine or modem to your system is similar to adding a telephone, with a few
important exceptions. If you have not added a telephone, you might want to read Adding new
telephones on page 70.
Because the system does recognize the concept of "fax" or "modem," you need to administer
these items as basic analog stations. You can merely use the supported station type 2500
(analog, single line).

86 Administering Avaya Aura™ Communication Manager May 2009

 Adding a fax or modem

Alternatively, you can create aliases to the 2500 for fax machines and modems. If you want to
be able to create reports that indicate which stations are faxes or modem, you should create
aliases for these items. For more information about aliasing, see Using an alias on page 76.
For this example, let us assume that we have already defined an alias for ‘fax’ as a 2500 and
that we now want to add a fax machine to extension 4444.
To add a fax machine as extension 444, complete the following steps:
1. Type add station 4444. Press Enter.
2. In the Type field, type fax.
3. In the Port field, type the port address.
4. In the Name field, type a name to associate with this fax.
5. Move to the Data Restriction field and type y.
Entering y in this field prevents calls to and from this extension from being interrupted by
tone signals. This is important for fax machines and modems as these signals can disrupt
transmissions of data.
6. In the Distinctive Audible Alert field, type n.
This eliminates the distinct 2-burst ring for external calls, which often interferes with the
auto-answer function on fax machines or modems.
7. Press Enter to save your changes.

Enabling transmission over IP networks for modem, TTY, and fax

calls

Prerequisites
The ability to transmit fax, modem, and TTY calls over IP trunks or LANs and WANs assumes
that the endpoints sending and receiving the calls are connected to a private network that uses
H.323 trunking or LAN connections between gateways and/or port networks. This type of
transmission also assumes that calls can either be passed over the public network using
ISDN-PRI trunks or passed over an H.323 private network to Communication Manager switches
that are similarly enabled.
As a result, it is assumed that you have assigned, or will assign, to the network gateways the IP
codec you define in this procedure. For our example, the network region 1 will be assigned
codec set 1, which you are enabling to handle fax, modem, and TTY calls.
To enable transmission over IP networks for modem, TTY, and fax calls:
1. Type change ip-codec-set 1. Press Enter.
The IP Codec Set screen appears.

Administering Avaya Aura™ Communication Manager May 2009 87

Chapter 3: Managing Telephones

Complete the fields as required for each media type you want to enable. Press Enter.
For more information on modem/fax/TTY over IP, see Administering Network Connectivity on
Avaya Aura™ Communication Manager, 555-233-504.

Adding an H.323 Softphone

Avaya IP (h.323) Softphones enable the end user to control telephone calls directly from a
personal computer (PC). An end user can log in remotely to your company’s server running
Communication Manager and then make and receive telephone calls from the telephone
extension.
Avaya IP Softphone supports the following modes:
● Road-Warrior
You typically use this mode for laptop users who are travelling. In this mode, the PC LAN
connection carries both the call control signaling and the voice path. Because the audio
portion of the voice call is handled by the PC, you must have some kind of audio device
(e.g., handset, headset) PC to provide the audio connection.
● Telecommuter or Avaya IP Agent
For the telecommuter or Avaya IP Agent mode, you make two separate connections to the
Avaya DEFINITY server. The signaling path is carried over an IP network and the voice
path is carried over the standard circuit-switched telephone network (PSTN). Since you
are using a telephone for audio, you do not need an H.323 PC audio application.
The telecommuter mode uses the Avaya IP Softphone interface (on the user’s PC) and a
standard telephone. The Avaya IP Agent mode uses the Avaya IP Agent interface (on the
agent’s PC) and a call center telephone.
● Native H.323 (only available with Avaya IP Softphone R2)
The stand-alone H.323 mode enables travelers to use some Communication Manager
features from a remote location. This mode uses a PC running an H.323 v2-compliant
audio application, such as Microsoft NetMeeting. The H.323 mode controls the call
signaling and the voice path. However, since it does not use the IP Softphone interface,
this configuration is capable of operating only as an analog or single-line telephone
making one call at a time without any additional assigned features. You can provide
stand-alone H.323 users only features that can they can activate with dial access codes.

88 Administering Avaya Aura™ Communication Manager May 2009

 Adding an H.323 Softphone

● Control of IP Telephone (only available with IP Softphone R4 and later)

This mode allows you to make and receive calls under the control of the IP Softphone -
just like in the telecommuter or road-warrior mode. The big difference is that you have a
real digital telephone under your control. In the road-warrior mode, there is no telephone.
In the telecommuter mode, the telephone you are using (whether analog, digital, or IP
telephone is brain dead). In this mode (if you have an IP telephone), you get the best of
both worlds.
● Control of DCP Telephone (only available with IP Softphone R5 and later)
This feature provides a registration endpoint configuration that will allow an IP softphone
and a non-softphone telephone to be in service on the same extension at the same time.
In this new configuration, the call control is done by both the softphone and the telephone
endpoint. The audio is done by the telephone endpoint.

Tip:
Tip: Use status station to show the part (product) ID, serial number, and the
audio connection method used by existing stations.
Note:
Note: Beginning with the November 2003 release of Communication Manager, R1 and
R2 IP Softphone and IP Agent, which use a dual connect (two extensions)
architecture, are no longer supported. R3 and R4 IP Softphone and IP Agent,
which use a single-connect (one extension) architecture, continue to be
supported. This applies to the road-warrior and the telecommuter configurations
for the IP Softphone. Native H.323 registrations for R1 and R2 Softphones
continue to be supported.

Before you start

Be sure that your system has been enabled to use IP Softphones. Display the System
Parameters Customer-Options (Optional Features) screen and verify the following field
settings:
● Maximum Concurrently Registered IP Stations is greater than 0
● IP Stations field is y
● Information has been entered in the fields on the Maximum IP Registrations by
Product ID page
Be sure that your DEFINITY CSI has a C-LAN board and an IP Media Processor board.
Once you’re finished administering Communication Manager, you need to install the IP
Softphone software on each user’s PC.

Administering Avaya Aura™ Communication Manager May 2009 89

Chapter 3: Managing Telephones

Adding a single-connect H.323 softphone

You can use the road-warrior mode when you have only a single telephone line available to
access Communication Manager over the IP network.
You also can "take over" an IP telephone. Typically you would not have a different extension for
your softphone. When you log in, the softphone takes over the existing telephone extension
(turn the DCP or IP telephone off). During this time, that DCP or IP telephone is out of service.
This is accomplished if, on the Station screen, the IP Softphone field is y.
Except for single-connect IP telephones, you have to administer two extensions for each
softphone that will be used in road-warrior mode.
Here is a single-connect example. To use extension 3001 with a softphone in road-warrior
mode, you need to administer the telephone (for example, DCP) extension. To do so, complete
the following steps:
1. Type add station 3001. Press Enter.
The system displays the Station screen.
Note that you choose to change an existing DCP extension by using change station
nnnn in this step, where nnnn is the existing DCP extension.
2. In the Type field, enter the model of telephone you want to use, such as 6408D.
3. In the Port field, type x for virtual telephone or enter the port number if there is hardware.
Note:
Note: Port 1720 is turned off by default to minimize denial of service situations. This
applies to all IP softphones release 5.2 or later. You can change this setting, if
you have root privileges on the system, by typing the command: /opt/ecs/
sbin ACL 1720 on or off.
4. In the Security Code field, enter the password for this remote user, such as 1234321.
This password can be 3-8 digits in length.
5. In the IP Softphone field, type y.
6. On page 2, in the Service Link Mode field, type as-needed.
Set this field to permanent only for extremely busy remote telephone users, such as call
center agents.
7. In the Multimedia Mode field, type enhanced.
8. Press Enter to save your work.
Now you can install and configure the software on your PC. In this example, you can login by
entering the DCP extension (3001) and password (1234321).

90 Administering Avaya Aura™ Communication Manager May 2009

 Adding an H.323 Softphone

Adding a softphone to be used in telecommuter mode

Assign this configuration to remote users who have two available telephone lines. For example,
to administer a telecommuter mode softphone for a home user at extension 3010, complete the
following steps:
1. Type add station 3010. Press Enter.
The system displays the Station screen.
Note:
Note: Use the add station command if this is a new DCP extension. Use the
change station command for an existing DCP extension and ignore steps 2
and 3.)
2. In the Port field, type x for virtual telephone or enter the port number if there is hardware.
3. In the Security Code field, enter the password for this remote user, such as 1234321.
This password can be up to 7 digits in length.
4. In the IP Softphone field, type y.
5. On page 2, in the Service Link Mode field, type as-needed.
Set this field to permanent only for extremely busy remote telephone users, such as call
center agents.
6. In the Multimedia Mode field, type enhanced.
7. Press Enter to save your work.
Now you can install and configure the software on your PC. In this example, you can login by
entering the DCP extension (3010) and password (1234321).

Fixing problems

Problem Possible causes Solutions

Display characters on Microsoft Windows is Set the Microsoft Windows

the telephone can not not set to use Eurofont operating system to use
be recognized. characters. Eurofont.

Administering Avaya Aura™ Communication Manager May 2009 91

Chapter 3: Managing Telephones

Related topics
See the online help for assistance, or, on the Avaya IP Softphone CD, refer to Avaya IP
Softphone Overview and Troubleshooting for customer information on Avaya IP Softphone
modes. This is a Portable Document Format (PDF) document that is located in the Overview
Document folder on the Avaya IP Softphone CD.
Also see Getting Started, also located on the Avaya IP Softphone CD for more information on
how to install and configure the IP Softphone software.

Adding an IP telephone
The 4600-series IP Telephones are physical sets that connect to Communication Manager via
TCP/IP.

! CAUTION:
CAUTION: An Avaya IP endpoint can dial emergency calls (for example, 911 calls in the
U.S.). It only reaches the local emergency service in the Public Safety Answering
Point area where the telephone system has local trunks. Please be advised that
an Avaya IP endpoint cannot dial to and connect with local emergency service
when dialing from remote locations that do not have local trunks. You should not
use an Avaya IP endpoint to dial emergency numbers for emergency services
when dialing from remote locations. Avaya Inc. is not responsible or liable for any
damages resulting from misplaced emergency calls made from an Avaya
endpoint. Your use of this product indicates that you have read this advisory and
agree to use an alternative telephone to dial all emergency calls from remote
locations.

Before you start

Verify the system has a:
● TN2302 IP Media Processor circuit pack for audio capability
● TN799 Control-LAN circuit pack for signaling capability (for CSI Servers only)
Be sure that your system has been enabled to use IP Telephones. Display the
System-Parameters Customer-Options (Optional Features) screen and verify the following field
settings:
● Maximum Concurrently Registered IP Stations is greater than 0
● IP Stations field is y

92 Administering Avaya Aura™ Communication Manager May 2009

 Adding an IP telephone

● Information has been entered in the fields on the Maximum IP Registrations by Product ID
page

Instructions
Let us add an IP telephone at extension 4005.
To assign an extension, complete the following steps:
1. Type add station 4005. Press Enter.
The system displays the Station screen.
2. In the Type field, enter the station type, in this case 4620.
Note:
Note: When adding a new 4601 or 4602 IP telephone, you must use the 4601+ or
4602+ station type. This station type enables the Automatic Callback feature.
When making a change to an existing 4601 or 4602, you receive a warning
message, stating that you should upgrade to the 4601+ or 4602+ station type in
order to access the Automatic Callback feature.
3. The Port field is display-only, and IP appears.
4. In the Security Code field, enter a password for the IP telephone user.
Note:
Note: Although the system accepts a null password, the IP telephone will not work
unless you assign a password.
5. Press Enter to save your work.

Changing from dual-connect to single-connect IP telephones

When you have a dual extension telephone and you upgrade to a single extension telephone,
you can remove the connection that is no longer used for that telephone.
To remove the H.323 connection that is no longer needed, first record the media complex
extension number:
1. Type change station nnnn, where nnnn is the extension number of the original
dual-connect telephone that you are replacing with a single-connect telephone.
The system displays the Station screen.
2. Move to the Media Complex Extension field.
3. Write down the number in the Media Complex field, then delete the number from the field.
4. Press Enter to save your changes.

Administering Avaya Aura™ Communication Manager May 2009 93

Chapter 3: Managing Telephones

Now remove the extension you recorded. Before you remove an H.323 extension from your
system, check the status, remove it from any group or usage lists, and then delete it from the
system’s memory.
For example, if you wrote down extension 1234 before you removed it from the Media Complex
field on the Station screen, then remove extension 1234 using these steps:
1. Type status station 1234. Press Enter.
The system displays the General Status screen.
2. Make sure that the extension:
● is idle (not making or receiving calls)
● has no messages waiting
● has no active buttons (such as Send All Calls or Call Forwarding)
3. Type list groups-of-extension 1234. Press Enter.
The Extension Group Membership screen shows whether the extension is a member of
any groups on the system.
4. Press Cancel.
5. If the extension belongs to a group, access the group screen and delete the extension
from that group.
For example, if extension 1234 belongs to pickup group 2, type change pickup group
2 and delete the extension from the list.
6. Type list usage extension 1234. Press Enter.
The Usage screen shows where the extension is used in the system.
7. Press Cancel.
8. If the extension appears on the Usage screen, access the appropriate feature screen and
delete the extension.
For example, if extension 1234 belongs to hunt group 2, type change hunt group 2
and delete the extension from the list.
9. Type change station 1234. Press Enter.
10. Delete any bridged appearances or personal abbreviated dialing entries. Press Enter.
11. Type remove station 1234. Press Enter.
The system displays the Station screen for this telephone so you can verify that you are
removing the correct telephone.
12. If this is the correct telephone, press Enter.
The system responds with the message command successfully completed.
If the system responds with an error message, the telephone is busy or still belongs to a
group. Press Cancel to stop the request, correct the problem, and type remove station
1234 again.

94 Administering Avaya Aura™ Communication Manager May 2009

 Adding an IP telephone

13. Remove the extension from voice mail service if the extension has a voice mailbox.
14. Type save translations. Press Enter to save your changes.
Note that you do not need to delete the extension from coverage paths. The system
automatically adjusts coverage paths to eliminate the extension.
Once you successfully remove the extension, it is permanently erased from system memory. If
you want to reactivate the extension, you have to add it again as though it were new.

Setting up emergency calls on IP telephones

Set up which "calling number" to send to the public safety access point when an emergency call
is placed from an IP telephone.

Instructions
You use the Station screen to set up emergency call handling options for IP telephones. As an
example, we’ll administer the option that prevents emergency calls from an IP telephone.
To prevent an emergency call from an IP telephone:
1. Type change station nnnn, where nnnn is the extension of the telephone you want to
modify. Press Enter.
The system displays the Station screen.
2. Click Next Page to find the Remote Softphone Emergency calls field.
3. Type block in the Remote Softphone Emergency calls field.
4. Press Enter to save your changes.

Administering Avaya Aura™ Communication Manager May 2009 95

Chapter 3: Managing Telephones

! CAUTION:
CAUTION: An Avaya IP endpoint can dial emergency calls (for example, 911 calls in the
U.S.). It only reaches the local emergency service in the Public Safety Answering
Point area where the telephone system has local trunks. Please be advised that
an Avaya IP endpoint cannot dial to and connect with local emergency service
when dialing from remote locations that do not have local trunks. You should not
use an Avaya IP endpoint to dial emergency numbers for emergency services
when dialing from remote locations. Avaya Inc. is not responsible or liable for any
damages resulting from misplaced emergency calls made from an Avaya
endpoint. Your use of this product indicates that you have read this advisory and
agree to use an alternative telephone to dial all emergency calls from remote
locations. Please contact your Avaya representative if you have questions about
emergency calls from IP telephones.

Setting up Remote Office

Avaya Remote Office provides IP processing capabilities to traditional call handling for voice
and data between Communication Manager and offices with Remote Office hardware. You
need to add the information about Remote Office as a node in Communication Manager, add its
extensions, and set up the trunk and signaling groups.

Before you start

Be sure the following fields on the System Parameters Customer-Options (Optional Features)
screen are set to y or completed. If not, contact your Avaya representative.
● Maximum Administered Remote Office Trunks
● Maximum Administered Remote Office Stations
● Product ID registration limit
● Remote Office
● IP station
● ISDN-PRI
Also, be sure your Remote Office hardware is installed and administered at the remote location.
You need the following information from the remote administration:
● IP address
● Password

96 Administering Avaya Aura™ Communication Manager May 2009

 Setting up Remote Office

Adding Remote Office to Communication Manager

In our example, we’ll set up a remote-office location using Avaya R300 Remote Office
Communicator hardware in our branch office in Santa Fe. We’ll add a new node, and set up the
signaling group and trunk group.

Adding a node

Instructions
To add the remote office node to Communication Manager:
1. Type change node-names IP. Press Enter.
The system displays the IP Node Names screen.
2. In the Name field, type in a word to identify the node.
In our example, type Remote 6.
3. In the IP address field, type in the IP address to match the one on the Avaya R300
administration.
4. Press Enter to save your changes.
5. Type add remote office and the number for this remote office. Press Enter.
The system displays the Remote Office screen.
6. Fill in the following fields:
● Node Name - match the name on the IP Node Names screen.
● Network Region - this must match the network region on the IP Interfaces screen for
the circuit packs that connect this remote office. Use display ip-interfaces to
find this information.
● Location - match the one set up on the Location screen for this remote office.
● Site Data - identify the street address or identifier you want to use
7. Press Enter to save your changes.

Tip:
Tip: Use status remote office to verify that your server running Communication
Manager recognizes the Remote Office information. It also displays the
extensions and signaling group you administer next.

Setting up a trunk group

You can modify an existing trunk group or add a new one. In our example, we’ll add trunk group
6. Before you start, perform Setting up a signaling group on page 98.

Administering Avaya Aura™ Communication Manager May 2009 97

Chapter 3: Managing Telephones

To set up the trunk group for your remote office:

1. Type add trunk group 6.
The system displays the Trunk Group screen.
2. In the Group Type field, type ISDN.
ISDN-PRI or ISDN-BRI must be y on the System Parameters Customer-Options
(Optional Features) screen.
3. In the TAC field, type in the trunk access code that conforms to your dial plan.
4. In the Carrier Medium field, type IP (Medpro).
5. In the Dial Access field, type y.
6. In the Service Type field, type tie.
7. In the Signaling Group field, type in the signaling group you created.
8. Press Enter to save your changes.

Setting up a signaling group

Each Remote Office has own listen port and signaling group. Set up a new trunk group, or use
an existing trunk group administered for H.323 signaling.

Instructions
Set up the signaling group for remote office:
1. Type add signaling-group and the number of the group you want to add.
The system displays the Signaling Group screen.
2. In the Group Type field, type H.323.
3. In the Remote Office field, type y.
4. In the Trunk Group for Channel Selection field, type the number of the trunk you set up
for the remote office.
5. In the Near-end Node Name field, identify the node name assigned to the C-LAN that
supports the R300.
6. In the Far-end Node Name field, identify the node name assigned to the C-LAN that
supports the R300.
7. In the Near-end Listen Port field, type a port number in the 5000-9999 range.
8. In the Far-end Listen Port field, type 1720.
9. In the RRQ field, type y.
10. Tab to the Direct IP-IP Audio Connection field on another page of this screen and type y.
11. Press Enter to save your changes.

98 Administering Avaya Aura™ Communication Manager May 2009

 Setting up Remote Office

Setting up Remote Office on network regions

Now we will set up a network region and show the connections between regions.

Instructions
Set up network region 1:
1. Type add ip-network-region 1. Press Enter.
The system displays the IP Network Region screen.
2. In the Name field, describe the region you are setting up.
3. In the Codec Set field, type the codec set you want to use in this region.
4. In the UDP Port Range field, type the range of the UDP port number to be used for audio
transport.
5. In the Intra-region IP-IP Direct Audio field, type y.
6. In the Inter-region IP-IP Direct Audio field, type y.
7. Move to page 3 to set up connections between regions and assign codecs for inter-region
connections.
Note:
Note: Page 2 of the IP Network Region screen shows a list of LSP servers for the
network region, and pages 4 through 19 are duplicates of page 3, providing the
ability to administer up to 250 locations.
The following connections are administered in this example:
● codec-set 2 is used between region 1 and region 4
● codec-set 5 is used between region 1 and region 99
● codec-set 6 is used between region 1 and region 193.
Now you need to assign the region number to the C-LAN circuit pack. All the endpoints
registered with a specific C-LAN circuit pack belong to the C-LAN’s region. See Administering
Network Connectivity on Avaya Aura™ Communication Manager, 555-233-504, for more
information.

Adding telephones to Remote Office

Be sure the extensions you add fit your dialing plan.

Instructions
1. Type add station nnnn, where nnnn is the extension you are adding. Press Enter.
The system displays the Station screen.
2. In the Type field, type in the model of the telephone you are adding.

Administering Avaya Aura™ Communication Manager May 2009 99

Chapter 3: Managing Telephones

3. In the Port field, type x.

This indicates that there is no hardware associated with the port assignment.
4. In the Name field, identify the telephone for your records.
5. In the Security Code field, match the password set up on the Remote Office
administration.
6. In the Remote Office Phone field, type y.
7. Press Enter to save your changes.

Downloading firmware to a 2420 or 2410 DCP telephone

You can copy updated application code into Communication Manager via TFTP over a TCP/IP
connection. This eliminates the need to physically remove the telephone and send it to the
factory for the firmware update. This feature is available on all of the servers running
Communication Manager.
Before you start
1. Type change node-name ip. Press Enter.
The system displays the IP Node Names screen.
2. Administer the TFTP server node name and the local node name (C-LAN) and IP address.
3. Press Enter to save your changes.
4. Type change ip-interfaces. Press Enter.
The IP Interfaces screen appears.
5. Administer the C-LAN Ethernet interface or processor C-LAN.
6. Press Enter to save your changes.

Downloading the firmware file to Communication Manager

1. Place the file on the TFTP server using TFTP, FTP, HTTP or another file transfer program.
2. From the Web Interface menu, click the Set LAN Security link.
3. Click Advanced. A list of settings that can be enabled or disabled through the use of
check boxes appears.
4. Scroll to tftp and check the box enabling inbound tftp traffic.
5. Click Submit.
6. Log into SAT and enter change tftp-server. Press Enter.
The system displays the TFTP Server Configuration screen.

100 Administering Avaya Aura™ Communication Manager May 2009

 Setting up Remote Office

7. In the Local Node Name field, enter the valid local node name from the IP Node Names
screen.
The node must be assigned to a C-LAN ip-interface or procr (processor C-LAN).
8. In the TFTP Server Node Name field, enter the valid TFTP server node name from the IP
Nodes Names screen.
9. In the TFTP Server Port field, enter the TFTP server port number from where the file
download begins.
10. In the File to Retrieve field, enter the name of the file to be retrieved.
11. Press Enter to save your changes.
The file transfer begins.
12. Type display tftp-server. Press Enter to view the status of the file transfer.
A File download successful message appears when the file transfer completes. It
also displays the file size and the file name in memory.

Downloading firmware to a single station

You must have console permissions to download someone else’s telephones.
Note:
Note: Steps 1 through 3 need be done only once to set up the FAC for file downloads.
Thereafter, start at step 4 to download files.
To set up a FAC for file downloads:
1. Type change feature-access-codes. Press Enter.
The system displays the Feature Access Code (FAC) screen.
2. Click Next Page until you see the Station Firmware Download Access Code field.
3. In the Station Firmware Download Access Code field, enter a valid FAC as defined in
the dial plan.
4. Press Enter to save your changes.
5. Take the 2410 or 2420 DCP telephone off-hook.
6. Dial the Station Firmware Download FAC (for instance, *36).
7. Press # if you are dialing from the target station (or dial the telephone’s extension to be
downloaded).
8. Place the telephone on-hook within 4 seconds after the confirmation tone.
The telephone is placed in a busy-out state (not able to make or receive calls) and displays
Firmware Download in Progress, the amount of the file downloaded, and a timer. The
telephone displays error messages and a success message before rebooting.
9. When the download completes, the telephone reboots and is released from the busy-out
state.

Administering Avaya Aura™ Communication Manager May 2009 101

Chapter 3: Managing Telephones

Downloading firmware to multiple stations

You can download firmware to multiple stations of the same type, either 2410 or 2420 DCP
telephones. Download firmware to as many as 1000 stations per download schedule. You can
schedule a specific time for the download, or you can administer the download to run
immediately.
To download 2420 DCP station firmware to multiple stations:
1. Type change firmware station-download. Press Enter.
The system displays the Firmware Station Download screen.

Figure 10: Firmware Station Download screen

change firmware station-download

FIRMWARE STATION DOWNLOAD

Source File:

Schedule Download? y
Start Date/Time:/: Stop Date/Time:/:
Continue Daily Until Completed? y
Download Set Type: 2420

Beginning Station: Ending Station:

2. In the Source File field, enter the name of the file specified in the File to Retrieve field on
the TFTP Server Configuration screen.
3. In the Schedule Download field, type y. The Start Date/Time and Stop Date/Time fields
appear.
4. In the Start Date/Time field, enter the month (mm), day (dd), year (yyyy), and time
(hh:mm) that you want the download to begin.
5. In the Stop Date/Time field, enter the month (mm), day (dd), year (yyyy), and time
(hh:mm) that you want the download to begin.
6. In the Continue Daily Until Completed field, enter y if you want the system to execute
the firmware download each day at the scheduled time until all specified telephones have
received the firmware.
7. In the Beginning Station field, enter the first extension number in the range of telephones
to which you want to download the firmware. Up to 1000 stations can be included in a
scheduled download.

102 Administering Avaya Aura™ Communication Manager May 2009

 Setting up Remote Office

8. In the Ending Station field, enter the last extension number in the range of telephones to
which you want to download firmware. Up to 1000 stations can be included in a scheduled
download.
9. Press Enter to save your changes. The firmware download is set to run at the scheduled
time. If you entered n in the Schedule Download? field, pressing Enter immediately
initiates the download to the specified range of telephones.

Displaying firmware download status

You can use the status firmware download command to display status information for an
active download schedule.
1. Type status firmware download.
2. Press Enter.
The system displays the Status Firmware Station Download screen.

Figure 11: Status Firmware Download screen

status firmware station-download

STATUS FIRMWARE STATION DOWNLOAD

Image file:
Schedule Download? Continue daily until completed?
Start Date/Time: Stop Date/Time:

Terminal type for download:

Extension range: to: Number of stations in range:
Stations completed: Stations unsuccessful:

Note:
Note: If you add the qualifier last to the status firmware download command,
status information on the last download schedule is displayed.

Disabling firmware downloads

You can use the disable firmware download command to disable any active download
schedule.
To disable active downloads:
● Type disable firmware download.
This command disables any active download schedule and the system displays Command
successfully completed at the bottom of the screen.

Administering Avaya Aura™ Communication Manager May 2009 103

Chapter 3: Managing Telephones

104 Administering Avaya Aura™ Communication Manager May 2009

Chapter 4: Managing Telephone Features

Adding Feature Buttons

Once you add a telephone to the system, you can use the Station screen to change the settings
for the telephone, such as adding or changing feature button assignments. The system allows
you to assign features or functionality to each programmable button. It is up to you to decide
which features you want for each telephone and which feature you want to assign to each
button.
If you have 6400-series telephones, your users can administer some of their own feature
buttons. See Setting up Terminal Self-Administration on page 140 for more information.
Note:
Note: An NI-BRI telephone with Communication Manager has only the Conference,
Transfer, Hold, and Drop feature buttons, none of which requires administration.
On an NI-BRI telephone, you can assign additional feature buttons only as call
appearances. As a result, NI-BRI telephone users must access all other features
of Communication Manager using feature access codes.

Additionally, the number of call appearance buttons administered in

Communication Manager (the default is three) must match the number of call
appearances programmed on the telephone.

Finally, Communication Manager does not support bridged call appearances for
NI-BRI telephones.
To assign feature buttons:
1. Type change station nnnn, where nnnn is the extension for the telephone you want
to modify. Press Enter.
2. Press Next Page until you locate the Button Assignment section of the Station screen.
Some telephones have several feature button groups. Make sure that you are changing
the correct button. If you do not know which button on the telephone maps to which
button-assignment field, see your telephone’s manual.
3. Enter the button name that corresponds to the feature you want to assign a feature button.
To determine feature button names, press Help, or refer to Telephone Feature Buttons
Table on page 108.

Administering Avaya Aura™ Communication Manager May 2009 105

Chapter 4: Managing Telephone Features

Note:
Note: For certain newer telephones with expanded text label display capabilities, you
can customize feature button labels to accept up to 13 alphanumeric characters.
For more information about this feature, see Increasing Text Fields for Feature
Buttons on page 106.
4. Press Enter to save your changes.
Some telephones have default assignments for buttons. For example, the 8411D includes
defaults for 12 softkey buttons. It already has assignments for features like Leave Word Calling
and Call Forwarding.
If you do not use an alias, you can easily assign different features to these buttons if you have
different needs.
If you use an alias you must leave the default softkey button assignments. The system allows
you to change the button assignments on the screen and the features work on the alias
telephone, however the labels on the display do not change.
Note:
Note: For various features to work properly, a multiappearance station must have a call
appearance as the first button. If you try to administer the first button as other
than a call-appr (including blank), the station displays the WARNING: For TTI
or PSA to work properly, this button must be a call-appr
warning message on the screen. So, it is a best practice to use the first
appearance as a call-appr.

Increasing Text Fields for Feature Buttons

If you are using certain newer phones with expanded text label display capabilities, the Increase
Text Fields for Feature Buttons feature allows you to program and store up to 13 character
labels for associated feature buttons and call appearances. This feature is available for the
following telephones:
● 2410 (Release 2 or newer)
● 2420 (Release 4 or newer)
● 4610 (IP Telephone Release 2.2 or later)
● 4620 (IP Telephone Release 2.2 or later)
● 4621 (IP Telephone Release 2.2 or later)
● 4622 (IP Telephone Release 2.2 or later)
● 4625 (IP Telephone Release 3.1 or later)

106 Administering Avaya Aura™ Communication Manager May 2009

 Adding Feature Buttons

Enabling extended text fields for feature buttons

To enable extended text fields for feature buttons:
1. Type add station next or change station nnnn, where nnnn is the extension of
the telephone you want to customize feature button labels for.
The system displays the Station screen.
2. Ensure that Customizable Labels is set to y. This allows the user to enter 13-character
labels for all feature buttons and call appearances associated with this station.
3. Press Enter to save your changes.
4. Assign specific feature buttons as described in Adding Feature Buttons on page 105.
Note:
Note: You can also use the existing Abbreviated Dialing (AD) button type (Abr
Program) to program AD labels. However, if you choose to utilize the Abr
Program button to program AD labels, you are limited to 5 upper case
characters. For more information on Abbreviated Dialing, see Adding Abbreviated
Dialing Lists on page 131.

Restricting customization of feature button types

In order to manage the usage of your system’s allocation of customized button labels to ensure
that VIP users have the button label customization resource available to them, you can restrict
button label customization of up to 50 specified button types for users who are not considered to
be VIP users.
To restrict customization of specific feature button types:
1. Type change button-restriction and press Enter.
The system displays the Button Type Customization Restrictions screen.
2. Ensure that the Restrict Customization Of Button Types field is set to y.
3. In the fields under Restrict Customization Of Labels For The Following Button Types,
enter the button type you want to restrict users from customizing.
Note:
Note: When you enter the special button types abr-spchar or abrv-dial, an additional
field appears to the right of the button type. Use this special field to specify the
special character associated with the abr-spchar button type or the Abbreviated
Dialing List associated with the abrv-dial button type.
4. Press Enter to save your changes.

Administering Avaya Aura™ Communication Manager May 2009 107

Chapter 4: Managing Telephone Features

Telephone Feature Buttons Table

The following table provides descriptions of the feature buttons that you can administer on
multiappearance telephones. It also lists the administrable software names and recommended
button label names. Display buttons support telephones equipped with alphanumeric displays.
Note that some buttons might require 1-lamp or 2-lamp buttons. Some buttons are not allowed
on some systems and on some telephones.
Note:
Note: An NI-BRI telephone with Communication Manager has only the Conference,
Transfer, Hold, and Drop feature buttons, none of which requires administration.
On an NI-BRI telephone, you might assign additional feature buttons only as call
appearances. As a result, NI-BRI telephone users must access all other features
of Communication Manager using feature access codes.

Additionally, the number of call appearance buttons administered in

Communication Manager (the default is three) must match the number of call
appearances programmed on the telephone.

Finally, Communication Manager does not support bridged call appearances for
NI-BRI telephones.
Note:
Note: Starting with Communication Manager Release 5.2, Intuity Audix IA770
application is called Communication Manager Messaging.

Table 2: Telephone feature buttons

Button name Button label Description Maximum

# AD You can administer the # button as an 1 per

autodial feature button by entering the station
CM Messaging number in the
BUTTON ASSIGNMENTS field on the
Station screen.
abr-prog Abr Program Abbreviated Dialing Program: allows 1 per
users to program abbreviated dialing station
and autodial buttons or to store or
change numbers in a personal list or
group list associated with the station.
1 of 24

108 Administering Avaya Aura™ Communication Manager May 2009

 Telephone Feature Buttons Table

Table 2: Telephone feature buttons (continued)

Button name Button label Description Maximum

abr-spchar AbrvDial (char) Abbreviated Dialing Special 1 each per

Character: allows users to enter an station
associated special character [~, ~m
(mark), ~p (pause), ~s (suppress), ~w
(wait for dial tone), or ~W (wait
forever)] when programming an
abbreviated dialing list entry.
abrdg-appr (extension) Bridged Appearance of an analog Depends
(Ext: ____) telephone: allows the user to have an on station
appearance of a single-line telephone type
extension. Assign to a 2-lamp
appearance button.
abrv-dial AD Abbreviated Dialing: dials the stored 1 per AD
(List: __ number on the specified abbreviated list per dial
DC: __) dialing list. code
List: specify the list number 1 to 3
where the destination number is
stored
DC: specify the dial code for the
destination number
abrv-ring AbRng Abbreviated and Delayed Ringing:
allows the user to trigger an
abbreviated or delayed transition for
calls alerting at an extension.
ac-alarm AC Alarm Administered Connection alarm 1 per
notification: allows the user to monitor station
when the number of failures for an
administered connection has met the
specified threshold.
aca-halt Auto-Ckt Halt Automatic Circuit Assurance (display 1 per
button): allows users of display system
telephones to identify trunk
malfunctions. The system
automatically initiates a referral call to
the telephone when a possible failure
occurs.
When the user presses ACA Halt, the
system turns off ACA monitoring for
the entire system. The user must
press ACA Halt again to restart
monitoring.
2 of 24

Administering Avaya Aura™ Communication Manager May 2009 109

Chapter 4: Managing Telephone Features

Table 2: Telephone feature buttons (continued)

Button name Button label Description Maximum

account Account Account: allows users to enter Call 1 per

Detail Recording (CDR) account station
codes. CDR account codes allow the
system to associate and track calls
according to a particular project or
account number.
admin Admin Administration: allows a user to 1 per
program the feature buttons on their station
6400-series telephone.
after-call AfterCall After Call Work Mode: allows an agent 1 per split
Grp:___ to temporarily be removed from call group
distribution in order for the agent to
finish ACD-related activities such as
completing paperwork.
Grp: specify the ACD split group
number.
alrt-agchg Alert Agent Alert Agent: indicates to the agent that 1 per
their split/skill hunt group changed station
while active on a call. This button
blinks to notify the agent of the
change.
alt-frl Alternate FRL Alternate Facility Restriction Level 1 per
(FRL): activates or deactivates an system
alternate facility restriction level for the
extension.
ani-requst ANI Request Automatic Number Identification 1 per
Request: allows the user to display the station
calling party’s number from incoming
trunks during the voice state of call.
The trunk must support this
functionality.
assist Assist Supervisory Assistance: used by an 1 per split
(Group: __) ACD agent to place a call to a split group
supervisor.
Group: specify the ACD split group
number.
asvn-halt ASVN Halt Authorization Code Security Violation 1 per
Notification: activates or deactivates system
call referral when an authorization
code security violation is detected.
3 of 24

110 Administering Avaya Aura™ Communication Manager May 2009

 Telephone Feature Buttons Table

Table 2: Telephone feature buttons (continued)

Button name Button label Description Maximum

atd-qcalls AttQueueCall Attendant Queue Calls (display 1 per

button): tracks the number of calls in station
the attendant group’s queue and
displays the queue status. Assign this
button to any user who you want to
backup the attendant.
atd-qtime AttQueueTime Attendant Queue Time (display 1 per
button): tracks the calls in the station
attendant group’s queue according to
the oldest time a call has been
queued, and obtains a display of the
queue status.
audix-rec Audix Record Audix One-Step Recording (display 1 per
button): activates/deactivates station
recording of the current call. A
messaging hunt group extension that
is valid for the user must be entered in
the Ext: field after the name.
aut-msg-wt Msg (name or Automatic Message Waiting: 1 per
(Ext: ___) ext #) associated status lamp automatically aut-mst-ex
lights when an LWC message has t
been stored in the system for the
associated extension (can be a VDN).
This lamp will not light on the
mapped-to physical station for
messages left for virtual extensions.
auto-cback Auto CallBack Automatic Call Back: when activated, 1 per
allows inside user who placed a call to station
a busy or unanswered telephone to be
called back automatically when the
called telephone becomes available to
receive a call.
auto-icom Autoic (name or ext #) Automatic Intercom: places a call to 1 per
(Group: __) the station associated with the button. group per
The called user receives a unique dial code
alerting signal, and a status lamp
associated with a Intercom button
flashes. Grp: Intercom — Auto-Icom
group number. This extension and
destination extension must be in the
same group.
4 of 24

Administering Avaya Aura™ Communication Manager May 2009 111

Chapter 4: Managing Telephone Features

Table 2: Telephone feature buttons (continued)

Button name Button label Description Maximum

auto-in Auto In Auto-In Mode: allows the user to 1 per split

(Group: __) become automatically available for group
new ACD calls upon completion of an
ACD call. Grp: The split group number
for ACD.
auto-wkup Auto Wakeup Automatic Wakeup (display button): 1 per
allows attendants, front-desk users, station
and guests to request a wakeup call to
be placed automatically to a certain
extension (cannot be a VDN
extension) at a later time.
autodial SD Allows a user to dial a number that is
not part of a stored list.
aux-work AuxWork Auxiliary Work Mode: removes agent 1 per split
(RC: __) from ACD call distribution in order to group
(Group: __) complete non-ACD-related activities.
RC: Optional assignment for the 1- or
2-digit Reason Code to be used to
change to Aux Work using this button,
when Reason Codes is active.
Multiple Aux Work buttons, each with
a different RC, can be assigned to the
same station set. Grp: The split group
number for ACD.
brdg-appr (extension) Bridged Call Appearance: provides an Depends
(Btn: __ appearance of another user’s on station
Ext: ___) extension on this telephone. For type
example, an assistant might have a
bridged appearance of their
supervisor’s extension. The bridged
appearance button functions exactly
like the original call appearance, for
instance it indicates when the
appearance is active or ringing.
You can assign brdg-appr buttons
only to 2-lamp appearance buttons.
You must indicate which extension
and which call appearance button the
user wants to monitor at this
telephone.
btn-ring Button Ring Station User Button Ring Control: 1 per
allows users to toggle between station
audible and silent call alerting.
5 of 24

112 Administering Avaya Aura™ Communication Manager May 2009

 Telephone Feature Buttons Table

Table 2: Telephone feature buttons (continued)

Button name Button label Description Maximum

btn-view Button View Button View: allows users to view, on

the telephone’s display, the contents
of any feature button. Button View
does more than the "View" or
"stored-num" feature button; these
only display what is contained in
abbreviated dialing and autodial
buttons.
When the user presses the btn-view
button and then a specific feature
button, they see the feature name and
any auxiliary data for that button. This
allows users to review the
programming of their feature buttons.
You can assign this soft-key button to
any 6400-, 7400-, or 8400-series
display telephone.
busy-ind Busy Busy Indication: indicates the busy or 1 per TAC/
(TAC/Ext: __) idle status of an extension, trunk Ext
group, terminating extension group
(TEG), hunt group, or loudspeaker
paging zone. Users can press the
busy-ind button to dial the specified
extension.
You can assign this button to any lamp
button and must specify which Trunk
or extension the user wants to
monitor.
call-appr extension Call Appearance: originates or Depends
receives calls. Assign to a 2-lamp on station
appearance button. type
call-disp Return Call Call Displayed Number (display 1 per
button): initiates a call to the currently station
displayed number. The number can be
from a leave word calling message or
a number the user retrieved from the
Directory.
call-fwd CFrwd (Ext #) Activates or deactivates Call 64 per
(Ext: ___) Call Forward (no ext #) Forwarding All Calls. extension
call-park Call Park Allows the user to place the current 1 per
call in the call park state so it can be station
retrieved from another telephone.
6 of 24

Administering Avaya Aura™ Communication Manager May 2009 113

Chapter 4: Managing Telephone Features

Table 2: Telephone feature buttons (continued)

Button name Button label Description Maximum

call-pkup Call Pickup Allows the user to answer a call that is 1 per
ringing in the user’s pickup group. station
call-timer Call Timer Used only with some set types. 1 per
station
callr-info Caller Info (display button) Used with Call 1 per
Prompting to allow users to display station
information collected from the
originator.
cas-backup CAS Backup Centralized Attendant Service 1 per
Backup: used to redirect all CAS calls station
to a backup extension in the local
branch if all RLTs are out-of-service or
maintenance busy. The associated
status lamp indicates if CAS is in the
backup mode.
cdr1-alrm CDR 1 Fail CDR Alarm: associated status lamp is 1 per
used to indicate that a failure in the station
interface to the primary CDR output
device has occurred.
cdr2-alrm CDR 2 Fail CDR Alarm: associated status lamp is 1 per
used to indicate that a failure in the station
interface to the secondary CDR output
device has occurred.
cfwd-bsyda CFBDA Call Forward Busy/Don’t Answer: 64 per
activates and deactivates call extension
forwarding for calls when the
extension is busy or the user does not
answer.
cfwd-enh ECFwd (ext #) Call Forwarding - Enhanced allows the
Enhanced Cfwd (no user to specify the destination
ext #) extension for both internal and
external calls.
check-in Check In Check In (display button): changes the 1 per
state of the associated guest room to station
occupied and turns off the outward
calling restriction for the guest room’s
station.
7 of 24

114 Administering Avaya Aura™ Communication Manager May 2009

 Telephone Feature Buttons Table

Table 2: Telephone feature buttons (continued)

Button name Button label Description Maximum

check-out Check Out Check Out (display button): Changes 1 per

the state of the associated guest room station
to vacant and turns on the outward
calling restriction for the guest room’s
station. Also clears (removes) any
wake-up request for the station.
clk-overid ClkOverride Clocked Manual Override (display 1 per
button): Used only by authorized station
attendants and system administrators,
in association with Time of Day
Routing, to override the routing plan in
effect for the system. The override is
in effect for a specified period of time.
This feature can only be assigned to
display telephones.
conf-dsp Conf Display Allows a user to display information 1 per
about each party of a conference call. station
This button can be assigned to
stations and attendant consoles.
consult Consult The Consult button allows a covering 1 per
user, after answering a coverage call, station
to call the principal (called party) for
private consultation.
Activating Consult places the caller on
hold and establishes a private
connection between the principal and
the covering user. The covering user
can then add the caller to the
conversation, transfer the call to the
principal, or return to the caller.
cov-cback CovrCallBack Allows a covering party to store a 1 per
leave word calling message for the station
principal (called party).
cov-msg-rt Covr Msg Ret Coverage Message Retrieval (display 1 per
button): places a covering station into station
the message retrieval mode for the
purposes of retrieving messages for
the group.
cpn-blk CPN Block Blocks the sending of the calling party 1 per
number for a call. station
8 of 24

Administering Avaya Aura™ Communication Manager May 2009 115

Chapter 4: Managing Telephone Features

Table 2: Telephone feature buttons (continued)

Button name Button label Description Maximum

cpn-unblk CPN Unblock Deactivates calling party number 1 per

(CPN) blocking and allows the CPN to station
be sent for a single call.
crss-alert Crisis Alert Crisis Alert (display button): provide 1 per
this button to the telephones or station
consoles that you want to notify when 10 per
any user makes an emergency call. system
(You define which calls are
emergency calls on the AAR/ARS
Analysis screen by setting the Call
Type to alrt.)
After a user receives an alert, they can
press the crss-alert button to disable
the current alert.
If tenant partitioning is active, the
attendants within a partition can
receive emergency notification only
from callers in the same partition.
data-ext Data (data ext #) Data Extension: sets up a data call. 1 per data-
Can be used to pre-indicate a data call extension
or to disconnect a data call. Cannot be group
a VDN or ISDN-BRI extension.
date-time Time/Date Date and Time (display button): 1 per
displays the current date and time. Do station
not assign this button to 6400-series
display telephones as they normally
show the date and time.
delete-msg Delete Msg Delete message (display button): 1 per
deletes a stored LWC message or station
wakeup request.
dial-icom Dial Icom Dial Intercom: accesses the intercom 1 per
(Grp: ___) group assigned to the button. Grp: group
Intercom — Dial (Dial Icom) group
number.
did-remove DID Remove DID Remove (display button): allows 1 per
DID assignments to be removed. station
did-view DID View DID View (display button): allows DID 1 per
assignments to be displayed and station
changed. Allows choice between
XDID and XDIDVIP numbers.
9 of 24

116 Administering Avaya Aura™ Communication Manager May 2009

 Telephone Feature Buttons Table

Table 2: Telephone feature buttons (continued)

Button name Button label Description Maximum

directory Directory Directory (display button): allows 1 per

users with display telephones to station
access the integrated directory, use
the touch-tone buttons to key in a
name, and retrieve an extension from
the directory. The directory contains
the names and extensions that you
have assigned to the telephones
administered in your system.
If you assign a directory button, you
should also assign a Next and
Call-Disp button to the telephone.
These buttons allow the user to
navigate within the integrated directory
and call an extension once they find
the correct one.

Note: Vector Directory Numbers do

not appear in the integrated directory.
Also, if you assign a name beginning
with two tildes (~~} to a telephone, and
Display Character Set on the System
Parameters Country-Options screen is
set to Roman, the name does not
appear in the integrated directory.
Note that this is the only way to hide a
name in the integrated directory.

dir-pkup Dir Pickup Directed call pickup: allows the user to

answer a call ringing at another
extension without having to be a
member of a pickup group.
disp-chrg Disp Charges Provides your display telephone with a 1 per
visual display of accumulated charges station
on your current telephone call. Used
exclusively outside the U.S. and
Canada.
disp-norm Local/ Normal (display button): Toggles 1 per
Normal between LOCAL display mode station
(displays time and date) and NORMAL
mode (displays call-related data). LED
off = LOCAL mode and LED on =
NORMAL.
10 of 24

Administering Avaya Aura™ Communication Manager May 2009 117

Chapter 4: Managing Telephone Features

Table 2: Telephone feature buttons (continued)

Button name Button label Description Maximum

dn-dst DoNotDisturb Places the user in the do not disturb 1 per

mode. station
drop Drop Allows users to drop calls. Users can
drop calls from automatic hold or drop
the last party they added to a
conference call.
ec500 EC500 Administers an Extension to Cellular 1 per
feature button on the office telephone. station
When you enter this value, the Timer
subfield displays, and defaults to n.
Set the optional Timer subfield to y to
include an Extension to Cellular timer
state for the administered feature
button. When the timer state is
included, the Extension to Cellular
user can activate a one-hour timer to
temporarily disable Extension to
Cellular through this administered
feature button. Leaving the default
setting of n excludes the timer state.
exclusion Exclusion Exclusion: allows multiappearance 1 per
telephone users to keep other users station
with appearances of the same
extension from bridging onto an
existing call.
If the user presses the Exclusion
button while other users are already
bridged onto the call, the other users
are dropped.
There are two means of activating
exclusion.
● Manual Exclusion — when the
user presses the Exclusion
button (either before dialing or
during the call).
● Automatic Exclusion — as soon as
the user picks up the handset. To
turn off Automatic Exclusion
during a call, the user presses the
Exclusion button. To use
Automatic Exclusion, set the
Automatic Exclusion by COS
field to y on the Feature-Related
System Parameters screen.
11 of 24

118 Administering Avaya Aura™ Communication Manager May 2009

 Telephone Feature Buttons Table

Table 2: Telephone feature buttons (continued)

Button name Button label Description Maximum

ext-dn-dst ExtDoNotDisturb Extension — Do Not Disturb (display 1 per

button): used by the attendant console station
or hotel front desk display telephone to
activate do not disturb and assign a
corresponding deactivate time to an
extension.
extnd-call Extend Call Allows the user to extend the current 1 per
call to an Off-PBX/Extension to station
Cellular telephone.
fe-mute Far End Mute Allows a user to mute a selected party 1 per
on a conference call. This button can station
be assigned to stations and attendant
consoles.
flash Flash 1) Allows a station on a trunk call with 1 per
Trunk Flash to send a Trunk Flash station
signal to the far end (e.g., Central
Office); 2) allows a station on a CAS
main call to send a Trunk Flash signal
over the connected RLT trunk back to
the branch to conference or transfer
the call.
goto-cover Goto Cover Go To Coverage: sends a call directly 1 per
to coverage instead of waiting for the station
called inside-user to answer. Go to
Cover forces intercom and priority
calls to follow a coverage path.

Note: Go to Cover cannot be activated

for calls placed to a Vector Directory
Number extension. Go to Cover can
be used to force a call to cover to a
VDN if the called principal has a VDN
as a coverage point.
grp-dn-dst GrpDoNotDstrb Group Do Not Disturb (display button): 1 per
places a group of telephones into the station
do not disturb mode.
grp-page GrpPg Allows users to make announcements
(Number:___) to groups of stations by automatically
turning on their speakerphones.
Number: The extension of the page
group.
12 of 24

Administering Avaya Aura™ Communication Manager May 2009 119

Chapter 4: Managing Telephone Features

Table 2: Telephone feature buttons (continued)

Button name Button label Description Maximum

headset Headset Signals onhook/offhook state changes 1 per

to Communication Manager. The station
green LED is on for offhook state and
off (dark) for onhook state.
hunt-ns HuntNS Hunt-Group Night Service: places a 3 per hunt
(Grp: ___) hunt-group into night service. Grp: group
Hunt group number.
in-call-id INCallID (group #, The Coverage Incoming Call 1 per
(Type: __ type, name, or ext #) Identification (ICI) button allows a group-type
Grp: ___) member of a coverage answer group per group
or hunt group to identify an incoming
call to that group even though the
member does not have a display
telephone.
In the Type field, enter c for coverage
answer groups and type of h for a hunt
group. In the Grp field, enter the group
number.
inspect Inspect Inspect (display button): allows users 1 per
on an active call to display the station
identification of an incoming call.
Inspect also allows users to determine
the identification of calls they placed
on Hold.
int-aut-an IntAutoAnswer Internal Automatic Answer: causes 1 per
any hybrid or digital station to station
automatically answer incoming
internal calls.
last-numb LastNumb Dialed Last Number Dialed (redial): originates 1 per
a call to the number last dialed by the station
station.
lic-error License Error License-Error: indicates a major 1 per
License File alarm. Pressing the telephone
button does not make the light go out. 20 per
The button goes out only after the system
error is cleared and Communication (Server
Manager returns to License-Normal CSI)
Mode. You can administer this button
on telephones and attendant
consoles.
13 of 24

120 Administering Avaya Aura™ Communication Manager May 2009

 Telephone Feature Buttons Table

Table 2: Telephone feature buttons (continued)

Button name Button label Description Maximum

limit-call LimitInCalls Limit Number of Concurrent Calls 1 per

feature: allows user to limit the number station
of concurrent calls at a station to one
call, where normally multiple call
appearances can terminate at the
station.
link-alarm Link Fail (link #) Link Alarm: associated status lamp 8 per
(link# ___) indicates that a failure has occurred on station
one of the Processor Interface circuit
pack data links. Link: Link number — 1
to 8 for multi-carrier media gateways
or 1 to 4 for single-carrier media
gateway.
lsvn-halt LSVN Halt Login Security Violation Notification: 1 per
activates or deactivates referral call system
when a login security violation is
detected.
lwc-cancel Cancel LWC Leave Word Calling Cancel: cancels 1 per
the last leave word calling message station
originated by the user.
lwc-lock Lock LWC Leave Word Calling Lock: locks the 1 per
message retrieval capability of the station
display module on the station.
lwc-store Store LWC Leave Word Calling Store: leaves a 1 per
message for the user associated with station
the last number dialed to return the
call to the originator.
major-alrm Major Alarm Major Alarm: assign to a status lamp 1 per
to notify the user when major alarms station
occur. Major alarms usually require
immediate attention.
man-msg-wt Msg Wait (name or Manual Message Waiting: allows a None
(Ext: ___) ext #) multiappearance telephone user to
press a button on their telephone in
order to light the Manual Message
Waiting button at another telephone.
You can administer this feature only to
pairs of telephones, such as an
assistant and an executive. For
example, an assistant can press the
man-msg-wt button to signal the
executive that they have a call.
14 of 24

Administering Avaya Aura™ Communication Manager May 2009 121

Chapter 4: Managing Telephone Features

Table 2: Telephone feature buttons (continued)

Button name Button label Description Maximum

man-overid ManOverid Immediate Manual Override (display 1 per

(TOD: _) button): allows the user (on a system station
with Time of Day Routing) to
temporarily override the routing plan
and use the specified TOD routing
plan.
TOD: specify the routing plan the user
wants to follow in override situations.
manual-in Manual In Manual-In Mode: prevents the user 1 per split
(Group: __) from becoming available for new ACD group
calls upon completion of an ACD call
by automatically placing the agent in
the after call work mode. Grp: The split
group number for ACD.
mct-act MCT Activate Malicious Call Trace Activation: sends 1 per
a message to the MCT control station
extensions that the user wants to trace
a malicious call. MCT activation also
starts recording the call, if your system
has a MCT voice recorder.
mct-contr MCT Control Malicious Call Trace Control: allows 1 per
the user to take control of a malicious station
call trace request. Once the user
becomes the MCT controller, the
system stops notifying other MCT
control extensions of the MCT
request.
NOTE: To add an extension to the
MCT control group, you must also add
the extension on the Extensions
Administered to have an MCT-Control
Button screen. For information about
this screen, see Avaya Aura™
Communication Manager Screen
Reference, 03-602878.
When the user presses the MCT
Control button, the system first
displays the called party information.
Pressing the button again displays the
rest of the trace information.
The MCT controller must dial the MCT
Deactivate feature access code to
release control.
15 of 24

122 Administering Avaya Aura™ Communication Manager May 2009

 Telephone Feature Buttons Table

Table 2: Telephone feature buttons (continued)

Button name Button label Description Maximum

mf-da-intl Directory Assistance Multifrequency Operator International: 1 per

allows users to call Directory station
Assistance.
mf-op-intl CO attendant Multifrequency Operator International: 1 per
allows users to make international station
calls to the CO attendant.
mj/mn-alrm Mj/Mn Alarm Minor Alarm: assign to a status lamp 1 per
to notify the user when minor or major station
alarms occur. Minor alarms usually
indicate that only a few trunks or a few
stations are affected.
mm-basic MM Basic Multimedia Basic: used to place a 1 per
multimedia complex into the "Basic" station
mode or to return it to the "Enhanced"
mode.
mm-call MM Call Multimedia Call: used to indicate a call 1 per
is to be a multimedia call. station
mm-cfwd MM Call Fwd Multimedia Call Forward: used to 1 per
activate forwarding of multimedia calls station
as multimedia calls, not as voice
calls.
mm-datacnf MM Data Cnf Multimedia Data Conference: used to 1 per
initiate a data collaboration session station
between multimedia endpoints;
requires a button with a lamp.
mm-multnbr MM Mult Nbr Indicate that the user wants to place 1 per
calls to 2 different addresses using the station
2 B-channels.
mm-pcaudio MM PC Audio Switches the audio path from the 1 per
telephone (handset or speakerphone) station
to the PC (headset or speakers/
microphone).
msg-retr Msg Retrieve Message Retrieval (display button): 1 per
places the station’s display into the station
message retrieval mode.
mwn-act MsgWaitAct Message Waiting Activation: lights a 1 per
message waiting lamp on an station
associated station.
16 of 24

Administering Avaya Aura™ Communication Manager May 2009 123

Chapter 4: Managing Telephone Features

Table 2: Telephone feature buttons (continued)

Button name Button label Description Maximum

mwn-deact MsgWaitDeact Message Waiting Deactivation: dims a 1 per

message waiting lamp on an station
associated station.
next Next Next (display button): steps to the next 1 per
message when the telephone’s station
display is in Message Retrieval or
Coverage Message Retrieval mode.
Shows the next name when the
telephone’s display is in the Directory
mode.
night-serv Night Service Night Service Activation: toggles the 1 per
system in or out of Night Service station
mode.
noans-alrt NoAnsAlrt Redirection on No Answer Alert: 1 per hunt
indicates a Redirection on No Answer group
timeout has occurred for the split.
no-hld-cnf No Hold Conf No Hold Conference: can 1 per
automatically conference another station
party while continuing the existing call.
normal Normal Mode Normal (display button): places the 1 per
station’s display into normal call station
identification mode.
off-bd-alm OffBoardAlarm Off board Alarm: associated status 1 per
lamp lights if an off-circuit pack major, attendant
minor, or warning alarm is active on a
circuit pack. Off-board alarms (loss of
signal, slips, misframes) relate to
problems on the facility side of the
DS1, ATM, or other interface.
per-COline COLine (line #) Personal CO Line: allows the user to 1 per
(Grp: ___) receive calls directly via a specific group
trunk. Grp: CO line group number.
pms-alarm PMS Failure Property Management System alarm: 1 per
associated status lamp indicates that station
a failure in the PMS link occurred. A
major or minor alarm condition raises
the alarm.
post-msgs Posted MSGs Posted Messages: Allows the user to 1 per
display a specific message to callers. station
17 of 24

124 Administering Avaya Aura™ Communication Manager May 2009

 Telephone Feature Buttons Table

Table 2: Telephone feature buttons (continued)

Button name Button label Description Maximum

pr-awu-alm AutoWakeAlarm Automatic Wakeup Printer Alarm: 1 per

associated status lamp indicates that station
an automatic wakeup printer interface
failure occurred.
pr-pms-alm PMS Ptr Alarm PMS Printer Alarm: associated status 1 per
lamp indicates that a PMS printer station
interface failure occurred.
pr-sys-alm Sys Ptr Alarm System Printer Alarm: associated 1 per
status lamp indicates that a system station
printer failure occurred.
print-msgs Print Msgs Print Messages: allows users to print 1 per
messages for any extension by station
pressing the button and entering the
extension and a security code.
priority Priority Call Priority Calling: allows a user to place 1 per
priority calls or change an existing call station
to a priority call.
q-calls QueueCall Queue Calls: associated status lamp 1 per hunt
(Grp: ___) flashes if a call warning threshold has group per
been reached. Grp: Group number of station
hunt group.
q-time QueueTime Queue Time: associated status lamp 1 per hunt
(Grp: ___) flashes if a time warning threshold has group per
been reached. Grp: Group number of station
hunt group.
release Release Releases an agent from an ACD call. 1 per
station
ring-stat Ringer Status Users can display the ringer status for 1 per
a line or bridged appearance by station
pressing the ring-stat button followed
by a call-appr, brdg-appr or
abrdg-appr button. Depending on the
ringer status, the display shows:
● Ringer On

● Ringer Off

● Ringer Delayed

● Ringer Abbreviated

ringer-off Ringer Off Ringer-Cutoff: silences the alerting 1 per

ringer on the station. station
18 of 24

Administering Avaya Aura™ Communication Manager May 2009 125

Chapter 4: Managing Telephone Features

Table 2: Telephone feature buttons (continued)

Button name Button label Description Maximum

rs-alert ResetAlert The associated status lamp lights if a 1 per

problem escalates beyond a warm station
start.
rsvn-halt RSVN Halt Remote Access Barrier Code Security 1 per
Violation Notification Call: activates or system
deactivates call referral when a
remote access barrier code security
violation is detected.
scroll Scroll Scroll (display button): allows the user 1 per
to select one of the two lines station
(alternates with each press) of the
16-character LCD display. Only one
line displays at a time.
send-calls SAC (ext #) Send All Calls allows users to 64 per
(Ext: ___) temporarily direct all incoming calls to extension
coverage regardless of the assigned
call-coverage redirection criteria.
Assign to a lamp button.
send-term Send TEG Send All Calls For Terminating 1 per TEG
Extension Group: allows the user to
forward all calls directed to a
terminating extension group.
serv-obsrv Service Obsrv Service Observing: activates Service 1 per
Observing. Used to toggle between a station
listen-only and a listen-talk mode.
19 of 24

126 Administering Avaya Aura™ Communication Manager May 2009

 Telephone Feature Buttons Table

Table 2: Telephone feature buttons (continued)

Button name Button label Description Maximum

share-talk Share Talk Share Talk: enables multiple DCP or 1 per

H323 IP endpoints that are registered station
to the same extension to share talk
capability. Normally, when more than
one endpoint requests RTP (Real
Time Transfer Protocol) media, only
one of the endpoints (Base Set) is
capable of talking and listening, while
the other endpoints are connected in
listen-only mode. This button allows all
the endpoints that are associated with
the extension to share the talk
capability. Note that in Communication
Manager 5.0, only AE Server DMCC
(Device, Media, and Call Control)
endpoints are capable of requesting
RTP while they are sharing control of
the extension. For more information
on DMCC, see Avaya MultiVantage®
Application Enablement Services
Administration and Maintenance
Guide, 02-300357.
signal Sgnl (name or Signal: allows the user to use one 1 per
(Ext: ___) ext #) button to manually signal the signal
associated extension. The extension extension
cannot be a VDN extension.
ssvn-halt SSVN Halt Toggle whether or not station security 1 per
code violation referrals are made to station
the referral destination.
sta-lock Station Lock When Station Lock is enabled, the 1 per
only calls that can be made from the station
station are those allowed by the COR
administered in the Station Lock
COR field.
start-bill Start Bill After an ACD agent answers a call, 1 per
the agent can press this button to station
send an ISDN CONNECT message to
the PSTN network to start the PSTN
call–billing for a call at the PSTN
switch.
stored-num Stored Number Enables a display mode that displays 1 per
the numbers stored in buttons. station
20 of 24

Administering Avaya Aura™ Communication Manager May 2009 127

Chapter 4: Managing Telephone Features

Table 2: Telephone feature buttons (continued)

Button name Button label Description Maximum

stroke-cnt Stroke Count Automatic Call Distribution Stroke up to 10

(Code:_) (#) Count # (0, 1, 2, 3, 4, 5, 6, 7, 8, or 9) per station
sends a message to CMS to
increment a stroke count number.
team Team The Team Button has two generic 15 per
functions, a display function and an monitoring
execution function. The display station
function allows any member of a team
(monitoring station) to observe the
station state of other team members
(monitored station). As an execution
function, the Team Button can be used
as Speed Dial Button or Pick-Up
Button where a call to the monitored
station is established directly or a
ringing call is picked from the
monitored station.
Ext: This field appears when you
enter the button type team. Enter the
extension of the principal station of the
virtual "team."
Rg
This field appears when you enter the
button type team. Enter the kind of
audible ringing for the team button.
Valid entries are a(bbreviated),
d(elayed), n(o-ring), and r(ing).
term-x-gr TermGroup (name or Terminating Extension Group: 1 per TEG
(Grp: ___) ext #) provides one or more extensions.
Calls can be received but not
originated with this button. Grp: TEG
number.
timer Timer Used only with some set types. 1 per
station
togle-swap Toggle-Swap Allows a user to toggle between two 1 per
parties before completing a station
conference or a transfer.
trk-ac-alm FTC Alarm Facility Test Call Alarm: associated 1 per
status lamp lights when a successful station
Facility Test Call (FTC) occurs.
21 of 24

128 Administering Avaya Aura™ Communication Manager May 2009

 Telephone Feature Buttons Table

Table 2: Telephone feature buttons (continued)

Button name Button label Description Maximum

trk-id Trunk ID Trunk Identification (display button): 1 per

identifies the tac (trunk access code) station
and trunk member number associated
with a call.
trunk-name Trunk Name (display button) Displays the name of 1 per
the trunk as administered on the CAS station
Main or on a server without CAS.
trunk-ns Trunk NS Trunk-Group Night Service: places a 3 per trunk
(Grp: ___) trunk-group into night service. Grp: group
Trunk group number.
usr-addbsy Add Busy Indicator Adds the busy indicator. 1 per
station
usr-rembsy Remove Busy Removes the busy indicator. 1 per
Indicator station
uui-info UUI-Info Allows users to see up to 32 bytes of 1 per
ASAI-related UUI-IE data. station
verify Verify Busy Verification: allows users to 1 per
make test calls and verify a station or station
a trunk.
vip-chkin VIP Check In VIP Check-in (display button): allows 1 per
user to assign the XDIDVIP number to station
the room extension.
vip-retry VIP Retry VIP Retry: starts to flash when the 1 per
user places a VIP wakeup call and station
continues to flash until the call is
answered. If the VIP wakeup call is not
answered, the user can press the VIP
Retry button to drop the call and
reschedule the VIP wakeup call as a
classic wakeup call.
To assign this button, you must have
both Hospitality and VIP Wakeup
enabled.
vip-wakeup VIP Wakeup VIP Wakeup: flashes when a VIP 1 per
wakeup reminder call is generated. station
The user presses the button to place a
priority (VIP) wakeup call to a guest.
To assign this button, you must have
both Hospitality and VIP Wakeup
enabled.
22 of 24

Administering Avaya Aura™ Communication Manager May 2009 129

Chapter 4: Managing Telephone Features

Table 2: Telephone feature buttons (continued)

Button name Button label Description Maximum

voa-repeat VOA Repeat VDN of Origin Announcement. VDN of 1 per

Origin Announcement must be station
enabled.
voice-mail Message This is not an administrable button, but 1 per
maps to the fixed hard "message" station
button on newer telephones.
vu-display Vu Display # VuStats Display: allows the agent to limited to
(format: __ specify a display format for the the
ID: __) statistics. If you assign a different number of
VuStats display format to each button, feature
the agent can use the buttons to buttons on
access different statistics. You can the
assign this button only to display telephone
telephones.
format: specify the number of the
format you want the button to display
ID (optional): specify a split number,
trunk group number, agent extension,
or VDN extension
whisp-act WhisperAct Whisper Page Activation: allows a 1 per
user to make and receive whisper station
pages. A whisper page is an
announcement sent to another
extension who is active on a call
where only the person on the
extension hears the announcement;
any other parties on the call cannot
hear the announcement.
The user must have a class of
restriction (COR) that allows
intra-switch calling to use whisper
paging.
whisp-anbk WhisperAnbk Whisper Page Answerback: allows a 1 per
user who received a whisper page to station
respond to the user who sent the
page.
23 of 24

130 Administering Avaya Aura™ Communication Manager May 2009

 Adding Abbreviated Dialing Lists

Table 2: Telephone feature buttons (continued)

Button name Button label Description Maximum

whisp-off WhisperOff Deactivate Whisper Paging: blocks 1 per

other users from sending whisper station
pages to this telephone.
work-code Work Code Call Work Code: allows an ACD agent 1 per
after pressing "work-code" to send up station
to 16 digits (using the dial pad) to
CMS.
24 of 24

Adding Abbreviated Dialing Lists

Abbreviated dialing is sometimes called speed dialing. It allows you to dial a short code in place
of an extension or telephone number.
When you dial abbreviated-dialing codes or press abbreviated-dialing buttons, you access
stored numbers from special lists. These lists can be personal (a list of numbers for an
individual telephone), group (a department-wide list), system (a system-wide list), or enhanced
numbers (allows for a longer list of numbers). The version and type of your system determine
which lists are available and how many entries you can have on each list.
Note:
Note: You can designate all group-number lists, system-number lists, and
enhanced-number lists as "privileged." Calls automatically dialed from a
privileged list are completed without class of restriction (COR) or facility restriction
level (FRL) checking. This allows access to selected numbers that some
telephone users might otherwise be restricted from manually dialing. For
example, a user might be restricted from making long-distance calls. However,
you can program the number of a branch office that is long distance into an AD
list as privileged. Then, the user can call this office location using AD, while still
being restricted from making other long-distance calls.

Administering Avaya Aura™ Communication Manager May 2009 131

Chapter 4: Managing Telephone Features

! SECURITY ALERT:
SECURITY ALERT: Privileged group-number, system-number, and enhanced-number lists provide
access to numbers that typically would be restricted.

Instructions
As an example, we will program a new group list:
1. Type add abbreviated-dialing group next. Press Enter.
The system displays the Abbreviated Dialing List screen.
2. Enter a number (in multiples of 5) in the Size field. This number defines the number of
entries on your dialing list.
For example, if you have 8 telephone numbers you want to store in the list, type 10 in the
Size field.
3. If you want another user to be able to add numbers to this list, enter their extension in the
Program Ext field.
For example, if you want the user at 4567 to be able to change group list 3, enter 4567 in
this field.
4. Enter the telephone numbers you want to store, one for each dial code.
Each telephone number can be up to 24 digits long.
5. Press Enter to save your changes.
You can display your new abbreviated-dialing list to verify that the information is correct or print
a copy of the list for your paper records.
Once you define a group list, you need to define which stations can use the list. For example,
we will set up station 4567 so it has access to the new group list.
To give station 4567 access to the group list:
1. Type change station 4567. Press Enter.
The system displays the Abbreviated Dialing List screen.
2. Press Next Page until you see the Abbreviated Dialing List fields.
3. Type group in any of the List fields. Press Enter.
A blank list number field appears.
4. Type 3 in the list number field.
When you assign a group or personal list, you must also specify the personal list number
or group list number.
5. Press Enter to save your changes.

132 Administering Avaya Aura™ Communication Manager May 2009

 Adding Abbreviated Dialing Lists

The user at extension 4567 can now use this list by dialing the feature access code for the list
and the dial code for the number they want to dial. Alternatively, you can assign an abbreviated
dialing button to this station that allows the user press one button to dial a specific stored
number on one of their three assigned abbreviated lists.

Fixing problems

Problem Possible causes Solutions

A user cannot ● The specific list Resolution:

access a dial might not be
list assigned to the 1. Type display station
user’s telephone. nnnn, where nnnn is the user’s
extension. Press Enter.
2. Review the current settings of
the List1, List2, and List3
fields to determine if the list the
user wants to access is
assigned to their telephone.
● If the user Resolution:
attempted to use a
feature access code 3. Type display
to access the list, feature-access-codes.
they might have Press Enter.
dialed the incorrect 4. Verify that the user is dialing
feature access the appropriate feature access
code. code.
● If the user Resolution:
attempted to press
a feature button, 5. Type display station
they might have nnnn, where nnnn is the user’s
pressed the extension. Press Enter.
incorrect feature 6. Review the current feature
button. button assignments to
determine if the user was
pressing the assigned button.
1 of 2

Administering Avaya Aura™ Communication Manager May 2009 133

Chapter 4: Managing Telephone Features

Problem Possible causes Solutions

A user cannot ● If the user Resolution:

access a dial attempted to press
list - continued the correct feature 1. Type display station
button, the button nnnn, where nnnn is the user’s
might not be set up extension. Press Enter.
correctly. 2. Review the current feature
button assignments to see if
the list number and dial code
are correct.
A user ● The user could be Resolution:
complains that using the wrong dial
using an code. 1. Ask the user what number they
abbreviated dialed or button they pressed
● The dial code could to determine which list and dial
dial list dials be defined
the wrong code they attempted to call.
incorrectly.
number. 2. Access the dialing list and
verify that the number stored
for the specific dial code
corresponds to the number the
user wanted to dial. (For
example to access a group list,
type display
abbreviated-dialing
group x. Press Enter, where
x is a group list number.)
3. If the user dialed the wrong
code, give them the correct
code.
4. If the dial code is wrong, press
Cancel and use the
appropriate change command
to re-access the abbreviated
dialing list. Correct the number.
Press Enter.
2 of 2

134 Administering Avaya Aura™ Communication Manager May 2009

 Setting up Bridged Call Appearances

More information
There are limits to the total number of abbreviated dialing list entries, the number of personal
dial lists, and the number of group dial lists that your system can store. Because of these
limitations, you should avoid storing the same number in more than one list. Instead, assign
commonly dialed numbers to the system list or to a group list. You can determine the
abbreviated dialing storage capacity, by referring to the System Capacity screen for the
abbreviated dialing values (type display capacity). For details on the System Capacity
screen, see Maintenance Commands for Avaya Aura™ Communication Manager, Media
Gateways and Servers, 03-300431.

Related topics
For more information, see Abbreviated Dialing in Avaya Aura™ Communication Manager
Feature Description and Implementation, 555-245-205.

Setting up Bridged Call Appearances

Think of a bridged call appearance as a telephone (the primary set) with an extension (the
bridged-to appearance). Both telephones can be used to call in and out and both show when a
line is in use. A call to the primary telephone is bridged to a specific appearance, or button, on
the secondary telephone. The secondary telephone retains all its functions, and a specific
button is dedicated as the bridged-to appearance from the primary telephone.
Bridged call appearances have to be assigned to telephones with double-lamp buttons, or
lights. The telephone types do not need to match, but as much consistency as possible is
recommended for all telephones in a bridged group. When a call comes in on bridged
telephones, the buttons assigned to the bridged appearances flash. You can assign as many
bridged appearances as there are line appearances on the primary telephone, and you can
assign ringing (alerting) to one or more of the telephones.

Instructions
To create a bridged call appearance:
1. Note the extension of the primary telephone.
A call to this telephone lights the button and, if activated, rings at the bridged-to
appearance on the secondary telephone.

Administering Avaya Aura™ Communication Manager May 2009 135

Chapter 4: Managing Telephone Features

2. If you want to use a new telephone for the bridged-to extension, duplicate a station.
For information, see Duplicating telephones on page 75.
3. Type change station and the bridged-to extension. Press Enter.
4. Press Next Page until the Feature Options page of the Station screen appears.
5. For the Per Button Ring Control field (digital sets only):
● If you want to assign ringing separately to each bridged appearance, type y.
● If you want all bridged appearances to either ring or not ring, leave the default n.
6. Move to Bridge Call Alerting.
If you want the bridged appearance to ring when a call arrives at the primary telephone,
type y. Otherwise, leave the default n.
7. Complete the appropriate field for your telephone type.

If. . . Then. . .

your primary telephone is move to the Line Appearance field

analog and enter abrdg-appr
your primary telephone is move to the BUTTON
digital ASSIGNMENTS field and enter
brdg-appr

8. Press Enter.
Btn and Ext fields appear. If Per Button Ring Control is set to y on the Station screen for
the digital set, Btn, Ext, and Ring fields appear.
9. Enter the primary telephone’s button number that you want to assign as the bridged call
appearance.
This button flashes when a call arrives at the primary telephone.
10. Enter the primary telephone extension.
11. If the Ring field appears:
● If you want the bridged appearance to ring when a call arrives at the primary
telephone, type y.
● If you do not want the bridged appearance to ring, leave the default n.
12. Press Enter to save your changes.
To see if an extension has any bridged call appearances assigned, type list bridge and the
extension. Press Enter.

136 Administering Avaya Aura™ Communication Manager May 2009

 Setting up Extension to Cellular

More information
Following are a list of example situations where you might want to use bridged appearances.
● A secretary making or answering calls on an executive’s primary extension
These calls can be placed on hold for later retrieval by the executive, or the executive can
simply bridge onto the call. In all cases, the executive handles the call as if he or she had
placed or answered the call. It is never necessary to transfer the call to the executive.
● Visitor telephones
An executive might have another telephone in their office that is to be used by visitors. It
might be desirable that the visitor be able to bridge onto a call that is active on the
executive’s primary extension number. A bridged call appearance makes this possible.
● Service environments
It might be necessary that several people be able to handle calls to a particular extension
number. For example, several users might be required to answer calls to a hot line number
in addition to their normal functions. Each user might also be required to bridge onto
existing hot line calls. A bridged call appearance provides this capability.
● A user frequently using telephones in different locations
A user might not spend all of their time in the same place. For this type of user, it is
convenient to have their extension number bridged at several different telephones.
Note:
Note: Best practices for bridged appearances:
● Do not add a bridged appearance as line appearance 1 for any station. Doing this
can cause unexpected feature interactions with features like Service Observing
and TTI.

Setting up Extension to Cellular

Use the Extension to Cellular feature to extend your office calls and Communication Manager
features to a cellular telephone. For a detailed description of the Extension to Cellular feature
and how to administer it, see Extension to Cellular in Avaya Aura™ Communication Manager
Feature Description and Implementation, 555-245-205, or Avaya Extension to Cellular User’s
Guide, 210-100-700.

Administering Avaya Aura™ Communication Manager May 2009 137

Chapter 4: Managing Telephone Features

The following table provides a quick reference to the screens and fields used in administering
the Extension to Cellular feature.

Table 3: Screens for administering Extension to Cellular

Screen name Purpose Fields

Stations with Off-PBX Map station extensions to All

Telephone Integration application types and external
telephone numbers.
Off-PBX Telephone Administer CTI feature. Mobile Call (CTI) Extension
Mobile-Feature-
Extension
Feature Access Code Set up access codes for Feature Access Code
(FAC) Communication Manager
features.
Extension to Call Which Map a dialed extension to Extension
Activate Features by activate a feature (FNE) within
Name Communication Manager from
a cell phone. Some FNEs
require FAC administration.
Telecommuting Access Create an Extension to All
Cellular remote access
number.
Security-Related Define a system-wide station Minimum Station Security Code
System Parameters security code length. Length
Station Assign feature buttons and BUTTON ASSIGNMENTS
timers.
Language Translations To review the office telephone All
feature button assignments.
Numbering-Public/ Assign 10-digit caller All
Unknown Format identification.
Coverage Path Set up number of unanswered Number of Rings
rings prior to coverage.
Trunk Group Enable Call Detail Recording CDR Reports
for outgoing trunk.
DS1 Circuit Pack Administer a DS1 Circuit pack Signaling Mode: CAS
for R2MFC for Extension to Interconnect: CO
Cellular use.
1 of 2

138 Administering Avaya Aura™ Communication Manager May 2009

 Setting up Extension to Cellular

Table 3: Screens for administering Extension to Cellular (continued)

Screen name Purpose Fields

Trunk Group Administer a trunk group for Group Type

Extension to Cellular use. Trunk Type
Note: For more information, Outgoing Dial Type
see Extension to Cellular in Incoming Dial Type
Avaya Aura™ Communication Receive Answer Supervision?
Manager Feature Description
and Implementation,
555-245-205.
Multifrequency- Administer MFC parameters Incoming Call Type: group-ii-mfc
signaling-related- needed for Extension to (for MFC signaling)
parameters Cellular. Outgoing Call Type: group-ii-mfc
(for MFC signaling)
Note: For more information,
see Guidelines for Request Incoming ANI (non-AR/
administering Multifrequency ARS)? y
Signaling in Avaya Aura™
Communication Manager
Feature Description and
Implementation, 555-245-205.
System Capacity Verify used, available, and Off-PBX Telephone - Extension
system station limits. to Cellular
Off-PBX Telephone - OPS
Off-PBX Telephone - PBFMC
Off-PBX Telephone - PVFMC
2 of 2

Setting up an Extension to Cellular Feature Access Button

Extension to Cellular provides the capability to administer an Extension to Cellular feature
access button on the user’s office telephone to enable and disable the feature. You can also
configure an optional timer. You administer this feature button on page 3 of the Station screen
for the "host" office extension to which Extension to Cellular is linked.
The process described below explains how to administer an Extension to Cellular feature button
and include the optional Extension to Cellular timer. The Extension to Cellular feature button is
available on telephones which support administrable feature buttons.
To set up an Extension to Cellular feature button with optional timer:
1. Type change station n (where n is the extension of an Extension to Cellular-enabled
station - in this example, 1034). Press Enter.

Administering Avaya Aura™ Communication Manager May 2009 139

Chapter 4: Managing Telephone Features

2. Press the Next Page button till you see the Button Assignments fields.
3. Select an available feature button under the BUTTON ASSIGNMENTS header (button 4
was used in this example) and type ec500 to administer an Extension to Cellular feature
button on the office telephone.
4. Press Enter.
Note:
Note: The Timer subfield displays, and defaults to n. Leaving the default setting of n
excludes the timer state.
5. Set the optional Timer subfield to y to include an Extension to Cellular timer state for the
administered feature button.
When the timer state is included, the Extension to Cellular user can activate a one-hour
timer to temporarily disable Extension to Cellular through this administered feature button.
6. Press Enter.
The corresponding feature button on the office telephone is now administered for
Extension to Cellular.
Note:
Note: The feature status button on the office telephone indicates the current state of
Extension to Cellular regardless of whether the feature was enabled remotely or
directly from the office telephone.
For additional information, see the Avaya Extension to Cellular User’s Guide, 210-100-700.

Setting up Terminal Self-Administration

Terminal self-administration (TSA) allows users to administer some of their own feature buttons
from their telephones. TSA is available for 6400-series, and 4612 and 4624 telephones. Users
are prompted, via the telephone’s display, to choose features to assign to buttons on their
telephones.

140 Administering Avaya Aura™ Communication Manager May 2009

 Setting up Terminal Self-Administration

Before you start

To prevent users from changing another user's telephone administration, you can enable the
system-wide option that requires users to enter a station security code before they can
administer their telephone. To enable this option:
1. Set the Station Security Code for Terminal Self-Administration Required on the
Security-Related System Parameters screen to y.
If you enable this option, the user is prompted for the station security code when they
press the Admin button. The user must enter the security code, followed by the pound (#)
button or the Done softkey.

Instructions
You need to assign a security code to the user’s Station screen for each user you want to
enable access to TSA. You also need to assign the user an Admin feature button.
For example, to assign a security code of 12345678 to extension 4234, complete the following
steps:
1. Type change station 4234. Press Enter.
The system displays the Station screen for extension 4234.
2. In the Security Code field, type 12345678.
You should assign unique security codes for each user. Once you enter the code and
move off the field, the system changes the field to ‘*’ for extra security.
3. In one of feature button fields, type admin.
You can assign this button to a feature button or a softkey.
4. Press Enter to save your changes.

More information
Before a user can enter the TSA Admin mode, their telephone must be completely idle. After a
user presses the Admin button and enters a security code (if necessary), they are prompted,
via the telephone’s display, to choose features to administer to buttons on their telephone.
The user can add, replace, or delete any of the following feature-button types from their
telephone.
● CDR Account Code
● Automatic Dial

Administering Avaya Aura™ Communication Manager May 2009 141

Chapter 4: Managing Telephone Features

● Blank
● Call Forwarding
● Call Park
● Call Pickup
● Directed Call Pickup
● Group Page
● Send All Calls
● Toggle Swap
● Activate Whisper Page
● Answerback for Whisper Page
● Whisper Page Off
End-user button changes are recorded to the Communication Manager server’s history log so
that remote services can know what translations are changed.

Fixing problems
● When a telephone is in the Admin mode, the telephone cannot accept any calls — the
telephone is treated as if it were busy. Also, a user cannot make calls while in the Admin
mode.
● Any button state a telephone is in when the telephone enters the Admin mode stays active
while the telephone is in the Admin mode.
● ACD agents who wish access to the Admin mode of TSA must be logged off before
pressing the Admin button. If they are not logged off when they attempt to enter the Admin
mode, they receive a denial (single-beep) tone.
● Call Forwarding can be active and works correctly in the Admin mode. An active Call
Forwarding button cannot be removed when the telephone is in the Admin mode.
● Since the telephone must be on-hook to go into the Admin mode, the Headset On/Off
button must be in the OFF position.
● A telephone that is in the Admin mode of TSA cannot be remotely unmerged by the PSA
feature.
If a user has Abbreviated and Delayed Ringing active, a call can be silently ringing at a
telephone and the user might not realize it. This ringing prevents the user from entering
the Admin mode of TSA.

142 Administering Avaya Aura™ Communication Manager May 2009

 Setting Up Enterprise Mobility User

Setting Up Enterprise Mobility User

Enterprise Mobility User (EMU) is a software-only feature that provides the ability to associate
the buttons and features of a primary telephone to a telephone of the same type anywhere
within your company’s enterprise.
A home station can be visited by another EMU user while the user is registered as an EMU
visitor elsewhere. A home station can be used as a visited station while the principal user’s
Extension to Cellular or other Off-PBX applications are active. And the principal user can
activate an Off-PBX application even if their home station is being visited by another EMU user.
Note that in this document, any telephone that is not the primary telephone is referred to as the
"visited" telephone and any server that is not the home server of the primary telephone is
referred to as the "visited server."

System Requirements for EMU

The following is a list of requirements that you need for the EMU feature:
● QSIG must be the private networking protocol in the network of Communication Manager
systems. This requirement also includes QSIG MWI.
Note:
Note: All systems in a QSIG network must be upgraded to Communication Manager 4.0
or later in order for the Enterprise Mobility User feature to function properly. If only
some systems are upgraded, and their extensions expanded, the EMU feature
might not work with the systems that have not been upgraded. See your Avaya
technical representative for more information
● Communication Manager Release 3.1 or later software must be running on the home
server and all visited servers.
● All servers must be on a Linux platform. EMU is not supported on DEFINITY servers.
● The visited telephone must be the same model type as the primary telephone to enable a
optimal transfer of the image of the primary telephone. If the visited telephone is not the
same model type, only the call appearance (call-appr) buttons and the message waiting
light are transferred.
● All endpoints must be terminals capable of paperless button label display.
● Uniform Dial Plan (UDP)
To activate the EMU feature, a user enters the EMU activation feature access code (FAC), the
extension number of their primary telephone, and the security code of the primary telephone on
the dial pad of a visited telephone. The visited server sends the extension number, the security