avaya admin

Administrators Guide for Avaya Communication Manager

555-233-506 Issue 9 January 2005

Copyright 2005, Avaya Inc. All Rights Reserved This document contains information related to Avaya Communication Manager software (as defined below) and Documentation (Product). Documentation means this document and Avayas information manuals in printed or electronic form containing operating instructions and performance specifications that Avaya or its suppliers generally make available to users of its products, and which Avaya delivers to End User with the Products. End User means any customer of Avaya or its authorized resellers, or any end user of the Product. See the Software and Documentation DVD/CD inserts for additional legal and licensing information. Notice Changes and corrections to the information in this document may be incorporated in future releases. Disclaimer Avaya, its affiliates or subsidiaries (Avaya) are not responsible for any modifications, additions or deletions to the original published version of the Documentation unless such modifications, additions or deletions were performed by Avaya. End User agrees to indemnify and hold harmless Avaya, Avaya's agents, servants, directors, officers, and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to the Documentation to the extent made by the End User. Warranty Avaya provides a limited warranty on the Product. Refer to your customer sales agreement to establish the terms of the limited warranty. In addition, Avayas standard warranty language as well as information regarding support for the Product, while under warranty, is available through the following web site: http://www.avaya.com/support. License USE OR INSTALLATION OF THE PRODUCT INDICATES THE END USERS ACCEPTANCE OF THE GENERAL LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE AT: http://www.avaya.com/ support (GENERAL LICENSE TERMS). DO NOT USE THE PRODUCT IF YOU DO NOT WISH TO BE BOUND BY THE GENERAL LICENSE TERMS. IN ADDITION TO THE GENERAL LICENSE TERMS, THE FOLLOWING LICENSE TERMS AND RESTRICTIONS WILL APPLY TO THE PRODUCT. Avaya grants End User a license within the scope of the license types described below. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the Documentation or other materials available to End User. Designated Processor means a single stand-alone computing device. Server means a Designated Processor that hosts a software application to be accessed by multiple users. Software means the computer programs in object code, originally licensed by Avaya and ultimately utilized by End User, whether as stand-alone products or pre-installed on Hardware. Hardware means the standard hardware products, originally sold by Avaya and ultimately utilized by End User. If your system is running in a TDM environment, the following license restriction applies: Designated System(s) License (DS). End User may install and use each copy of the Software on only one Designated Processor, unless a different number of Designated Processors is indicated in the Documentation or other materials available to End User. Avaya may require the Designated Processor(s) to be identified by type, serial number, feature key, location or other specific designation, or to be provided by End User to Avaya through electronic means established by Avaya specifically for this purpose. If your system is running in an IP environment, the following license restriction applies: Concurrent User License (CU). End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A Unit means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an e-mail or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Product that permits one user to interface with the Software. Units may be linked to a specific, identified Server.

For all systems, the following license restriction applies: Shrinkwrap License (SR). With respect to Software that contains elements provided by third party suppliers, End User may install and use the Software in accordance with the terms and conditions of the shrinkwrap or clickwrap license accompanying the Software (Shrinkwrap License). The text of the Shrinkwrap License will be available from Avaya upon End Users request (see Copyright below for more information). 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. Certain Software programs or portions thereof included in the Product may contain software distributed under third party agreements (Third Party Components), which may contain terms that expand or limit rights to use certain portions of the Product (Third Party Terms). Information identifying Third Party Components and the Third Party Terms that apply to them is available on Avayas web site at http://support.avaya.com/ ThirdPartyLicense/. The disclaimers of warranties and limitations of liability set forth in the Third Party Terms do not affect any express warranty or limitation of liability that may be provided to you by Avaya pursuant to the license terms covering the Product contained in a separate written agreement between you and Avaya. To the extent there is a conflict between the General License Terms or your customer sales agreement and any Third Party Terms, the Third Party Terms shall prevail solely for such Third Party Components. Security and virus disclaimer End User's decision to acquire products from third parties is End User's sole responsibility, even if Avaya helps End User identify, evaluate or select them. Avaya is not responsible for, and will not be liable for, the quality or performance of such third party products or their suppliers. ALL INFORMATION IS BELIEVED TO BE CORRECT AT THE TIME OF PUBLICATION AND IS PROVIDED "AS IS". AVAYA DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND FURTHERMORE, AVAYA MAKES NO REPRESENTATIONS OR WARRANTIES THAT THE STEPS RECOMMENDED WILL ELIMINATE SECURITY OR VIRUS THREATS TO END USER SYSTEMS. IN NO EVENT SHALL AVAYA BE LIABLE FOR ANY DAMAGES WHATSOEVER ARISING OUT OF OR IN CONNECTION WITH THE INFORMATION OR RECOMMENDED ACTIONS PROVIDED HEREIN, INCLUDING DIRECT, INDIRECT, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF AVAYA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Avaya does not warrant that this Product is immune from or will prevent unauthorized use of telecommunication services or facilities accessed through or connected to it. Avaya is not responsible for any damages or charges that result from either unauthorized uses or from incorrect installations of the security patches that are made available from time to time. Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to [email protected]. Trademarks All trademarks identified by and TM are registered trademarks or trademarks of Avaya Inc. All other trademarks are the property of their respective owners.

Contents

About this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conventions used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Admonishments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to obtain Avaya books on the Web . . . . . . . . . . . . . . . . . . . . . . . How to order documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to comment on this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to get help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1313 14 15 16 17 17 18 19 19 19

Chapter 1: System Basics . . . . . . . . . . . . . . . . . . . . . . . . .Logging into the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing the S8700 or S8710 Media Server . . . . . . . . . . . . . . . . . . . . Logging in with Access Security Gateway. . . . . . . . . . . . . . . . . . . . . . Logging off the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Command Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . Establishing Daylight Savings Rules . . . . . . . . . . . . . . . . . . . . . . . . . Setting Time of Day Clock Synchronization . . . . . . . . . . . . . . . . . . . . . Setting the System Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Bulletin Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Saving Translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2121 23 27 28 29 31 34 41 42 44 47

Chapter 2: Planning the System . . . . . . . . . . . . . . . . . . . . . .Understanding Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding the Dial Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Controlling the Features Your Users Can Access . . . . . . . . . . . . . . . . . . System-Wide Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing Feature Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting WAN Bandwidth Limits Between Network Regions . . . . . . . . . . . . Administering Treatment for Denied or Invalid Calls . . . . . . . . . . . . . . . . Setting up Music-on-Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Providing Service for Multiple Tenants. . . . . . . . . . . . . . . . . . . . . . . . Receiving Notification in an Emergency . . . . . . . . . . . . . . . . . . . . . . .

4949 50 56 56 57 58 60 61 63 65

Issue 9 January 2005

3

Contents

Notifying a Digital Pager of an Emergency . . . . . . . . . . . . . . . . . . . . . Other Useful Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Controlling the Calls Your Users Can Make and Receive . . . . . . . . . . . . . . Station Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fiber Link Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

68 70 71 74 75

Chapter 3: Managing Phones . . . . . . . . . . . . . . . . . . . . . . . .Installing New Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding New Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Templates to Add Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . Using an Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Customizing Your telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Swapping Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using ACTR to Move Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using TTI to Move Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a Fax or Modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding an IP Softphone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding an IP Telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up Remote Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2420/2410 DCP telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7777 78 83 84 86 87 87 88 91 95 96 98 103 108 116

Chapter 4: Managing Telephone Features . . . . . . . . . . . . . . . . .Adding Feature Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Telephone feature Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Abbreviated Dialing Lists . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up Bridged Call Appearances . . . . . . . . . . . . . . . . . . . . . . . . Setting up an Extension to Cellular Feature Access Button . . . . . . . . . . . . Setting up Terminal Self Administration . . . . . . . . . . . . . . . . . . . . . . .

121121 123 144 149 153 155

Chapter 5: Managing Attendant Consoles . . . . . . . . . . . . . . . . .Attendant Consoles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding an Attendant Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . Attendant Console Feature Buttons . . . . . . . . . . . . . . . . . . . . . . . . . Setting Console Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

159159 164 166 173

4 Administrators Guide for Avaya Communication Manager

Contents

Removing an Attendant Console . . . . . . . . . . . . . . . . . . . . . . . . . . . Providing Backup for an Attendant. . . . . . . . . . . . . . . . . . . . . . . . . .

174 175

Chapter 6: Managing Displays . . . . . . . . . . . . . . . . . . . . . . . 177Displaying Caller Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying ANI Calling Party Information . . . . . . . . . . . . . . . . . . . . . . Displaying ICLID Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the Display Language . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up Directory Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 177 178 180 190

Chapter 7: Handling Incoming Calls . . . . . . . . . . . . . . . . . . . .Setting up Basic Call Coverage. . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up Advanced Call Coverage . . . . . . . . . . . . . . . . . . . . . . . . . Setting up Call Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up Night Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Call Pickup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Hunt Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Vectors and VDNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding Automatic Call Distribution . . . . . . . . . . . . . . . . . . . . . Assigning a Terminating Extension Group . . . . . . . . . . . . . . . . . . . . .

191191 195 202 207 221 228 235 250 251

Chapter 8: Routing Outgoing Calls. . . . . . . . . . . . . . . . . . . . .World Class Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Calling Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assigning ARS FAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying ARS Analysis Information . . . . . . . . . . . . . . . . . . . . . . . . Understanding ARS Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up Multiple Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Routing with Multiple Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying Call Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overriding Call Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining ARS Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up Time of Day Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . Location by Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

253253 254 255 256 256 265 267 271 275 277 281 284


5

Contents

Chapter 9: Managing MultiMedia Calling . . . . . . . . . . . . . . . . .Multimedia Applications Server Interface . . . . . . . . . . . . . . . . . . . . . . Multimedia Call Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding the Multimedia Complex . . . . . . . . . . . . . . . . . . . . . . . Enhanced Mode MM Complex . . . . . . . . . . . . . . . . . . . . . . . . . . . .

289289 317 334 349

Chapter 10: Setting Up Telecommuting . . . . . . . . . . . . . . . . . .Configuring Avaya Communication Manager for Telecommuting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up Personal Station Access . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Station Security Code . . . . . . . . . . . . . . . . . . . . . . . . . . . Assigning an Extender Password . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up Call Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assigning Coverage Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Home Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up Remote Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Training Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

367367 369 372 374 375 377 378 380 385

Chapter 11: Enhancing System Security. . . . . . . . . . . . . . . . . .Basic Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preventing Toll Fraud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Physical Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Security Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Logins and Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing a Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying a Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing a Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Access Security Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing Login Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Busy Verify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up Authorization Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up Security Violations Notification . . . . . . . . . . . . . . . . . . . . . Using Station Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dealing with Security Violations . . . . . . . . . . . . . . . . . . . . . . . . . . .

389389 390 392 393 397 400 402 402 403 408 409 410 412 415 420 422


Contents

Chapter 12: Managing Trunks . . . . . . . . . . . . . . . . . . . . . . .Tips for Working with Trunk Groups . . . . . . . . . . . . . . . . . . . . . . . . . Adding a CO, FX, or WATS Trunk Group . . . . . . . . . . . . . . . . . . . . . . . Adding a DID Trunk Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a PCOL Trunk Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a Tie or Access Trunk Group. . . . . . . . . . . . . . . . . . . . . . . . . Adding a DIOD Trunk Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up Digital Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Trunks to a Trunk Group . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing Trunk Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inserting and Absorbing Digits . . . . . . . . . . . . . . . . . . . . . . . . . . . . Administering Trunks for Listed Directory Numbers . . . . . . . . . . . . . . . . Administering Answer Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . Administering ISDN Trunk Groups . . . . . . . . . . . . . . . . . . . . . . . . . .

423423 426 429 431 435 437 438 443 445 446 448 450 451

Chapter 13: Managing Announcements . . . . . . . . . . . . . . . . . .Understanding Announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Announcement Data Modules . . . . . . . . . . . . . . . . . . . . . . . . Adding Announcement Extensions . . . . . . . . . . . . . . . . . . . . . . . . . Recording Announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Saving Announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copying Announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoring Announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting and Erasing Announcements . . . . . . . . . . . . . . . . . . . . . . . . Setting up Continuous-Play Announcements . . . . . . . . . . . . . . . . . . . . Getting Started with the TN2501AP or G700 Virtual VAL . . . . . . . . . . . . . . Managing VAL Announcements Using the SAT . . . . . . . . . . . . . . . . . . . Managing VAL Announcements Using FTP . . . . . . . . . . . . . . . . . . . . . VAL Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting VAL Announcements . . . . . . . . . . . . . . . . . . . . . . . Non-Volatile Storage of Announcements on VAL . . . . . . . . . . . . . . . . . .

457457 457 459 461 463 465 466 467 469 470 472 478 485 485 489

Chapter 14: Managing Group Communications . . . . . . . . . . . . . .Setting up Voice Paging Over Loudspeakers . . . . . . . . . . . . . . . . . . . . Setting up Chime Paging Over Loudspeakers. . . . . . . . . . . . . . . . . . . . Paging Over Speakerphones . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

491491 494 498


7

Contents

Paging Users Who are on Active Calls . . . . . . . . . . . . . . . . . . . . . . . . Using Telephones as Intercoms . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up Automatic Answer Intercom Calls . . . . . . . . . . . . . . . . . . . . Observing Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

501 502 505 507

Chapter 15: Managing Data Calls. . . . . . . . . . . . . . . . . . . . . .Types of Data Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Call Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alphanumeric Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Hotline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Privacy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Default Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Restriction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data-Only Off-Premises Extensions . . . . . . . . . . . . . . . . . . . . . . . . . Data Modules General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Administered Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modem Pooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PC Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Wideband Switching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CallVisor Adjunct-Switch Application Interface . . . . . . . . . . . . . . . . . . . Setting up CallVisor ASAI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up DEFINITY LAN Gateway. . . . . . . . . . . . . . . . . . . . . . . . . .

509509 510 517 518 519 520 521 523 524 527 533 535 538 549 551 552

Chapter 16: Administering Media Servers . . . . . . . . . . . . . . . . .Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Administering the G700 Media Gateway . . . . . . . . . . . . . . . . . . . . . . . Administering the Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . Administering Call-processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . SNMP Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

555555 556 561 565 578

Chapter 17: Collecting Billing Information. . . . . . . . . . . . . . . . .Collecting Information About Calls. . . . . . . . . . . . . . . . . . . . . . . . . . Recording Calls Between Users on the Same Server . . . . . . . . . . . . . . . . Tracking Calls by Account Code . . . . . . . . . . . . . . . . . . . . . . . . . . . Forcing Users to Enter Account Codes . . . . . . . . . . . . . . . . . . . . . . . Receiving Call-Charge Information . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Call Charge Information . . . . . . . . . . . . . . . . . . . . . . . . . . .

591591 594 596 597 599 602


Contents

Chapter 18: Command Reference . . . . . . . . . . . . . . . . . . . . .Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

605605

Chapter 19: Telephone Reference . . . . . . . . . . . . . . . . . . . . .500 telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2400 telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2500-series telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4600-series IP telephones 6200-series telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

647648 648 649 649 651 655 659 660 663 668 684 689 689 696 699 703

6400-series telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7100-series telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7300-series telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731x-series hybrid telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7400-series telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISDN telephones (7500s & 8500s) . . . . . . . . . . . . . . . . . . . . . . . . . . 8110 telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8400-series telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CALLMASTER telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cordless telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internet Protocol (IP) Softphones . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 20: Screen Reference . . . . . . . . . . . . . . . . . . . . . . . 709AAR and ARS Digit Analysis Table . . . . . . . . . . . . . . . . . . . . . . . . . . AAR and ARS Digit Conversion Table . . . . . . . . . . . . . . . . . . . . . . . . Abbreviated Dialing List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Access Endpoint. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Administered Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Agent Login ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alias Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alphanumeric Dialing Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Announcements/Audio Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . ARS Toll Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Attendant Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audix-MSA Node Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Authorization Code COR Mapping . . . . . . . . . . . . . . . . . . . . . . . . Best Service Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709 715 719 730 735 741 746 748 750 758 759 779 780 782


9

Contents

Bulletin Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Vector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAMA Numbering Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CDR System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Change Station Extension. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class of Restriction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Code Calling IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Permission Categories . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Console Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Coverage Answer Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Coverage Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Crisis Alert System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . CTI Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Daylight Savings Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DCS to QSIG TSC Gateway screen . . . . . . . . . . . . . . . . . . . . . . . . . . Dial Plan Analysis Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dial Plan Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Digit Absorption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DLG Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DS1 Circuit Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extended Pickup Group

785 788 795 797 810 813 830 834 835 840 843 857 859 864 868 873 908 911 914 916 921 925 926 928 953 955 956 975 1052 1055 1057 1059 1077 1111 1113

Extensions Administered to have an MCT-Control Button . . . . . . . . . . . . . . . . . . . . . . . . . . . Feature Access Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Feature-Related System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . Firmware Station Download. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Group Paging Using Speakerphone . . . . . . . . . . . . . . . . . . . . . . . . . Holiday Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hospitality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hunt Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrated Announcement Boards . . . . . . . . . . . . . . . . . . . . . . . . . . Integrated Announcement Translations . . . . . . . . . . . . . . . . . . . . . . .


Contents

Intercom Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inter-Exchange Carrier (IXC) Codes . . . . . . . . . . . . . . . . . . . . . . . . . Intra-Switch CDR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IP Address Mapping IP Codec Set IP Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1114 1116 1118 1120 1123 1129 1135 1148 1149 1156 1166 1170 1200 1203 1206 1218 1249 1251 1253 1257 1265 1273 1278 1282 1283 1287 1295 1322 1328 1331 1333 1335 1336 1341 1343

IP Network Region

IP Node Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IP-Options System Parameters IP Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISDN Numbering Calling Party Number Conversion for Tandem Calls . . . . . . ISDN Trunk Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISDN Numbering Private . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISDN Numbering Public/ Unknown . . . . . . . . . . . . . . . . . . . . . . . . ISDN-BRI Trunk Circuit Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Language Translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Listed Directory Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Local Survivable Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Login Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loudspeaker Paging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Media-Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Meet-me Vector Directory Numbers . . . . . . . . . . . . . . . . . . . . . . . . . Mode Code Related System Parameters . . . . . . . . . . . . . . . . . . . . . . . Modem Pool Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multifrequency-Signaling-Related Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple Level Precedence & Preemption (MLPP) Parameters . . . . . . . . . . . Music Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Node Number Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet Gateway Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Partition Routing Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Personal CO Line Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pickup Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Precedence Routing Digit Analysis Table . . . . . . . . . . . . . . . . . . . . . .


11

Contents

Precedence Routing Digit Conversion Table . . . . . . . . . . . . . . . . . . . . PRI Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . QSIG to DCS TSC Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote Call Coverage Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RHNPA Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Route Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security-Related System Parameters . . . . . . . . . . . . . . . . . . . . . . . . Signaling Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Site Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Parameters Call Coverage/Call Forwarding . . . . . . . . . . . . . . . . System Parameters Country-Options . . . . . . . . . . . . . . . . . . . . . . . . System-Parameters Customer-Options . . . . . . . . . . . . . . . . . . . . . . . System Parameters OCM Call Classification . . . . . . . . . . . . . . . . . . . . System Parameters - SCCAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Telecommuting Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tenant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminal Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminating Extension Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . TFTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Time of Day Coverage Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Time of Day Routing Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Toll Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tone Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trunk Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uniform Dial Plan Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uniform Dial Plan Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vector Directory Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1345 1348 1353 1355 1361 1363 1365 1367 1378 1386 1408 1409 1456 1465 1469 1497 1501 1503 1504 1508 1515 1519 1521 1523 1525 1529 1534 1622 1623 1626

Index

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1637


Overview

About this book

OverviewAvaya Communication Manager is the centerpiece of Avaya applications. Running on a variety of Avaya Media 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 customers 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 bookThis book describes the procedures and screens used in administering the most recent release of Communication Manager running on any of the following:

Avaya media servers - DEFINITY servers - S8100, S8300, S8500, or S8700 Media Servers

Avaya media servers configured as a Local Survivable Processor (LSP). Avaya media gateways - MCC1 or SCC1 Media Gateways - G350, G600, G650, or G700 Media Gateways

Newer releases of Communication Manager contain all the features of prior releases.

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


13

About this book

ContentsThis 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 Phones explains how to add, swap, and remove phones, and how to customize a telephone, for Communication Manager administrators. Chapter 4: Managing Telephone Features explains how to administer feature buttons for your users phones. 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 phones. Chapter 7: Handling Incoming Calls shows you how to set up call coverage for incoming calls to be sure that incoming calls are answered when the called party is unavailable. Chapter 8: Routing Outgoing Calls explains how Avaya Communication Manager handles outgoing calls and tells you how to modify call restrictions and your routing plan. Chapter 9: Managing MultiMedia Calling describes the Multimedia Applications Server Interface (MASI), and provides instructions on administration, monitoring, and troubleshooting. This section also provides information on Multimedia Call Handling (MMCH), which enables users to control voice, video, and data transmissions using a telephone and PC. Chapter 10: Setting Up Telecommuting provides information on system-wide settings and individual user administration for telecommuting. Chapter 11: Enhancing System Security provides information on analyzing and setting up basic system security, preventing toll fraud, using logins and permissions and passwords, and dealing with security violations. Chapter 12: Managing Trunks contains procedures for working with analog and digital trunks. Specialized trunks such as APLT, tandem, release-link, DMI-BOS and ISDN trunk groups are not covered in this manual. Chapter 13: Managing Announcements tells you how to record, save, copy, restore and delete announcements.


Conventions used

Chapter 14: Managing Group Communications shows you how to administer your system so users can page other users or use their phones 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 Media Servers describes how to administer an Avaya S8700 or S8710 Media Server and an Avaya G700 Media Gateway and the Avaya S8300 Media Server. Chapter 17: Collecting Billing Information provides information on account codes, and on tracking and collecting information about calls. Chapter 18: Command Reference Use the commands in these tables to access each administration screen. Chapter 19: Telephone Reference describes many of the telephones that you can connect to Communication Manager. It also describes the unique features and buttons for each telephone series to help you administer your user phones. Chapter 20: Screen Reference provides a brief description and a graphic representation of the Communication Manager screens used for administration. It also lists the valid values for fields on the screens, and describes when and why to use each value.

Conventions usedBecome familiar with the following terms and conventions. They help you use this book with Communication Manager.

A "screen" is the display of fields and prompts that appear on a terminal monitor. See the Screen Reference chapter for an example of a screen and how it is shown in this book.

We use the term "telephone" in this book. Other Avaya books might refer to telephones as voice terminals, stations, or endpoints. Keys and buttons are printed in a bold font: Key. Titles of screens are printed in a bold font: Screen Name. Names of fields are printed in a bold font: Field Name. Text (other than commands) that you need to type into a field are printed in a bold font: text. Commands are printed in a bold constant width font: command. Variables are printed in a bold constant width italic font: variable.


15

About this book

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. - 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 and see the most current books. 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.

AdmonishmentsAdmonishments that might appear in this book have the following meanings: Note: Draws attention to information that you must heed. Tip:Tip:

Note:

Draws attention to information that you might find helpful.

! CAUTION:CAUTION:

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

!WARNING:

WARNING: Denotes possible harm to hardware or equipment.


Trademarks

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

TrademarksAll trademarks identified by or are registered trademarks or trademarks, respectively, of Avaya, Inc. All other trademarks are the property of their respective owners.

Related SourcesThe following documents provide additional information. Administration for Network Connectivity for Avaya Communication Manager, 555-233-504 ATM Installation, Upgrades, and Administration using Avaya Communication Manager, 555-233-124 Avaya Application Solutions -- IP Telephony Deployment Guide, 555-245-600 Avaya Communication Manager Advanced Administration Quick Reference, 03-300364 Avaya Communication Manager Basic Administration Quick Reference, 03-300363 Avaya Communication Manager Basic Diagnostics Quick Reference, 03-300365 Avaya Licensing Guide, 03-300157 Avaya Toll Fraud and Security Handbook, 555-025-600 Converged Communications Server Installation and Administration, 555-245-705 DEFINITY Communications Systems Generic 2.2 and Generic 3 Version 2 DS1/CEPT1/ISDN PRI Reference, 555-025-107 DEFINITY Enterprise Communications Server Release 1.1 Getting Started with the Avaya R300 Remote Office Communicator, 555-233-769 Feature Description and Implementation for Avaya Communication Manager, 555-245-205 Hardware Guide for Avaya Communication Manager, 555-245-207 Highlights of Avaya Communication Manager, 555-245-704 Installation, Upgrades and Additions for Avaya CMC1 Media Gateways, 555-233-118


17

About this book

Maintenance Alarms for Avaya Communication Manager 2.1, Media Gateways and Servers, 03-300190 Maintenance for Avaya DEFINITY Server R, 555-233-117 Maintenance for Avaya MultiVantage and DEFINITY Server CSI, 555-233-119 Maintenance for Avaya DEFINITY Server SI, 555-233-123 Maintenance Commands for Avaya Communication Manager 2.1, Media Gateways and Servers, 03-300191 Maintenance Procedures for Avaya Communication Manager 2.1, Media Gateways and Servers, 03-300192 Overview for Avaya Communication Manager, 555-233-767 System Capacities Table for Avaya Communication Manager on Avaya Media Servers, 555-245-601 Upgrades and Additions for Avaya DEFINITY Server R, 555-233-115 Reports for Avaya Communication Manager, 555-233-505 For documents not listed here, go to http://www.avaya.com. Select Support and then Product Documentation.

How to obtain Avaya books on the WebIf 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: If you dont have Acrobat Reader, you can get a free copy at http:// www.adobe.com.

Note:

For example, to access an electronic version of this book: 1. Access the Avaya Web site at http://www.avaya.com/support/. 2. Click Product Documentation. 3. To find a specific book, type the document number (for example, 555-233-506 for this book) in the Search Support text box, and then click GO. 4. In the resulting list, locate the latest version of the document, and then click the document title to view the latest version of the book.


How to order documentation

How to order documentationIn addition to this book, other description, installation and test, maintenance, and administration books are available. This document and any other Avaya documentation can be ordered directly from the Avaya Publications Center toll free at 1-800-457-1235 (voice) and 1-800-457-1764 (fax). Customers outside the United States should use +1-410-568-3680 (voice) and +1-410-891-0207 (fax).

How to comment on this bookAvaya welcomes your feedback. Contact us through:

e-mail: [email protected] fax: 1-303-538-1741 Contact your Avaya representative

Mention this documents name and number, Administrators Guide for Avaya Communication Manager, 555-233-506. Your comments are of great value and help improve our documentation.

How to get helpIf 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 Centers Toll Fraud Intervention Hotline at 1-800-643-2353. If you need additional help, the following resources are available. You may need to purchase an extended service agreement to use some of these resources. See your Avaya representative for more information. Go to the Avaya Web site at http://www.avaya.com/support:

If you are within the United States, click the Escalation Management link. Then click the appropriate link for the type of support you need. If you are outside the United States, click the Escalation Management link. Then click International Services, which includes telephone numbers for the international Centers of Excellence. Or contact your local Avaya authorized dealer for any additional help and questions.


19

About this book


Chapter 1: System Basics

Logging into the SystemYou 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. Note: Avaya recommends that you change your password frequently to prevent unauthorized access to your system. For instructions on how to change your password, see Changing Passwords on page 409.

Note:

When not using the system, log off for security purposes.

InstructionsLogging into the systemThis procedure provides instructions for logging in from the system terminal not a remote terminal. To log into the system: 1. Enter your login name and press Enter. 2. Enter your password and 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 and press Enter. The Command prompt displays. 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 and press Enter. Enter the correct terminal type on the new screen and 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.

Note:


21

System Basics

Logging in for remote administrationTo log in for remote administration: 1. Dial the Uniform Call Distribution (UCD) group extension number. Note: The UCD group extension number is assigned when you set up remote administration.

Note:

If you are off-premises, use the Direct Inward Dialing (DID) number, a Listed Directory Number (LDN) (you must use a telephone), or the trunk number dedicated to remote administration. If you are on-premises, use an extension number. If you dialed a DID number, dedicated trunk number, or extension, you receive data tone or visually receive answer confirmation. If an LDN was dialed, the attendant will answer. a. Ask to be transferred to the UCD group extension number. You receive data tone or visually receive answer confirmation. b. Transfer the voice call to your data terminal.

The Login prompt displays. 2. Complete the steps for Logging into the System on page 21. For information about setting up remote administration, contact your Avaya technical support representative.

Failed login attemptsSAT login failureIf you are using the System Access Terminal (SAT), you can use the Security Violations Notification feature to disable a users login if a threshold of failed login attempts is reached within a specified time period. Administer these parameters on the Security-Related System Parameters screen. For instance, if you set the Login Threshold to 3 and the Time Interval to 10 minutes, and there are 3 failed login attempts in 10 minutes or less, that login is disabled. To re-enable a login ID that has been disabled by a security violation, type enable login nnnnn, where nnnnn is the login you want to re-enable. You can view SVN-disabled logins on the "monitor security-violations login" report, or by typing list logins. For more information on setting up SVN for SAT login lockout, see the "Screen Reference" chapter, Login Administration and Security-Related System Parameters sections. See also Chapter 11: Enhancing System Security. For a complete description of the Security Violation Notification feature, see "Security Violation Notification " in Feature Description and Implementation for Avaya Communication Manager, 555-245-205.


Accessing the S8700 or S8710 Media Server

Server login failureCommunication Manager has an automatic lockout mechanism that is activated when there are 4 login failures in 10 minutes or less. The login will be locked out for 5 minutes. An account lockout event is logged to the security log. This type of lockout applies for all shell and Web access logins, including SAT logins.

Accessing the S8700 or S8710 Media ServerTo administer the S8700 or S8710 Media 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 the S8700 or S8710 Media Server in one of three ways:

directly remotely over the customers local area network (LAN) over a modem

A direct connection and over the customers LAN are the preferred methods. Remote access over a modem is for Avaya maintenance access only.

Accessing the S8700 or S8710 Media Server DirectlyYou can access the S8700 or S8710 Media Server directly by plugging a computer into the services port which defaults to port 2 (Eth1) on the back of the media 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 may need a NIC card adapter. Once connected, you can administer the media server using three tools:

Media server web interface for server-specific administration. ASA for various features of Avaya Communication Manager A command line interface in a Telnet window for features of Avaya Communication Manager.

Media Server Web InterfaceYou can access the media server web interface either by connecting directly to the services port on the media server or connecting over the customers network.


23

System Basics

Connected to the services portTo use the media server web interface: 1. Open either the Netscape or MS Internet Explorer browser. 2. In the Location/Address field, type 192.11.13.6 and press Enter. 3. When prompted, log in to administer the S8700 or S8710 Media Server and the features of Avaya Communication Manager.

Connected to the customer networkTo use the media server web interface: 1. Open either the Netscape or MS Internet Explorer browser. 2. In the Location/Address field, type the active server name or IP address and press Enter. 3. When prompted, log in to administer the S8700 or S8710 Media Server and the features of Avaya Communication Manager. You may also connect directly to an individual server using its name or IP address.

Avaya Site AdministrationTo use ASA: 1. You must have a PC or laptop with Avaya Site Administration installed on it. 2. You must be connected over a LAN to either:

a dedicated LAN port for service technicians, or a customer LAN port

Instructions1. 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. If you have not 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. 3. Click Start GEDI. You now are connected to the desired system.


Accessing the S8700 or S8710 Media Server

Installing Avaya Site AdministrationIf you do not have ASA on your computer, make sure your personal computer (PC) or laptop first meets the following minimum requirements: Operating systems Windows 2000 Windows XP 2003 (Standard and Enterprise) Graphics adapter Floppy disk drive CD-ROM Available hard disk space Processor/RAM Pentium-class 300 MHz/64 MB Pentium-class 300 MHz/64 MB Pentium-class 300 MHz/64 MB SVGA with minimum screen resolution of 800 x 600 3-1/2 in. 1.44-MB floppy disk drive CD-ROM drive (required to install ASA from CD) 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. Standard PC or network printer port is required for connecting to a printer to produce station button labels. Required for network access to the S8700 or S8710 Media Server, AUDIX, and other network-connected systems. One free serial port capable of 9600-bps operation is required for a connection to each serial device (UPS). Avaya recommends that PCs have at least a 16550A UART or 16550A UART simulator (capable of 56 kbps DTE-speed connections). USB and internal modems should emulate this hardware. A second serial port is required for simultaneous connection to AUDIX through a serial connection.

Printer port

Network adapter

Free serial ports

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


25

System Basics

Configuring Avaya Site AdministrationWhen Avaya Site Administration is initially installed on a client machine, it needs to be configured to communicate with Communication Manager on the Media Server. When it runs initially, after downloading, you need to create a new entry for the switch connection. To create new entries for the switch, use the following procedure.

Adding a Switch Administration Item1. Click File > New > Voice System. The system displays the Add Voice System screen . 2. Enter a name in the Voice 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 Media Server. 7. Click Next. The Network Connection/Port Number dialog box displays. 8. TCP/IP Port Number: For the port number, 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 switch 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.

Accessing the S8700 or S8710 Media Server Remotely over the networkYou can access the S8700 or S8710 Media 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 media server using three tools:

Media server web interface for server-specific administration and call processing features Avaya Site Administration for Communication Manager (Only available on the active Communication Manager server) A command line interface via a Telnet window for Linux shell commands.


Logging in with Access Security Gateway

Logging in with Access Security GatewayAccess Security Gateway (ASG) is an authentication interface used to protect the system administration and maintenance ports and logins associated with Avaya Communication Manager. ASG uses a challenge and response protocol to validate the user and reduce unauthorized access. You can administer ASG authentication on either a port type or login ID. If you set ASG authentication for a specific port, it restricts access to that port for all logins. If you set ASG authentication for a specific login ID, it restricts access to that login, even when the port is not administered to support ASG. Authentication is successful only when Avaya Communication Manager and the ASG communicate with a compatible key. You must maintain consistency between the Access Security Gateway Key and the secret key assigned to the Communication Manager login. For more information about ASG, see Using Access Security Gateway on page 403.

Before you startBefore you can log into the system with ASG authentication, you need an Access Security Gateway Key, and you need to know your personal identification number (ASG). The Access Security Gateway Key must be pre-programmed with the same secret key (such as, ASG Key, ASG Passkey, or ASG Mobile) assigned to the Avaya Communication Manager login. Verify that the Access Security Gateway (ASG) field on the System-Parameters Customer Options screen is set to y. If not, contact your Avaya representative.

InstructionsTo log into the system with ASG: 1. Enter your login ID and 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 and 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 and press ON. The Access Security Gateway Key displays a response number (for example, 999-1234).


27

System Basics

5. At the response prompt on your terminal, type the ASG response number without the "-" character (for example, 9991234) and press Enter. The Command prompt displays. Note: If you make 3 invalid login attempts, the system terminates the session. For more information, see the appropriate maintenance book for your system.

Note:

Fixing problemsNote:

Note: When logging in failures occur, if you are a super-user, you can use the list asg-history command to determine the cause. The ASG history log contains the last 100 or 250 records depending on your system. This log contains the date and time, the port mnemonic, the login ID entered (correct or incorrect), and the status for each session attempt. For specific information about the ASG history log, see Reports for Avaya Communication Manager.

Logging off the SystemFor 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.

InstructionsTo log off: 1. Type logoff and 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 may 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.


Setting Command Permissions

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]

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.

Setting Command PermissionsAvaya Communication Manager allows you to modify the permissions associated with a login. The system maintains default permissions for each level of login, but you may want to further restrict the login, or at least make sure the defaults are appropriate for the user. The default values for these fields vary based on the login type. When set to y, the permissions on the Command Permission Categories screen apply for any object that is not restricted. The second and third pages of the Command Permission Categories screen allow you to restrict the user from any access to specified objects. If you want to limit a users permissions beyond those on page one, enter the objects in this list. For example, if you want a user to be able to add and change stations, but not VDNs, you can enter y in the Administer Stations field and the Additional Restrictions field. Then on page 2 or 3, enter vdn as a restricted object.

InstructionsIn our example, we set the permissions necessary to allow the user to administer daylight savings time rules.


29

System Basics

To change command permissions: 1. Type change permissions sup3ru and press Enter. The Command Permission Categories screen displays. Figure 2: Command Permission Categories screenCOMMAND PERMISSION CATEGORIES Login Name: sup3ru COMMON COMMANDS Display Admin. and Maint. Data? y System Measurements? y ADMINISTRATION COMMANDS Administer Stations? y Administer Trunks? y Additional Restrictions? n MAINTENANCE COMMANDS Maintain Stations? n Maintain Trunks? n Maintain Systems? n

Administer Features? y Administer Permissions? y

Maintain Switch Circuit Packs? n Maintain Process Circuit Packs? n Maintain Enhanced DS1? n

2. Type y in the Display Admin and Maint Data field. 3. Type y in the Administer Features field. 4. Press Enter to save your work.

More informationThere are 2 types of users superuser and non-superuser.

A superuser provides access to the add, change, display, list, and remove commands for all customer logins and passwords. The superuser can administer any mix of superuser/ non-superuser logins. The superuser can administer between 10 and 19 logins depending on your system. Logins must be 3 to 6 alphabetic/numeric characters, or a combination of both. Note: If several users are logging in and out at the same time, a user may see the message: Transient command conflict detected; please try later. After the users have completed logging in or out, the terminal is available for use.

Note:


Establishing Daylight Savings Rules

Note:

Note: Non-superusers may change their password with permission set by the superuser. However, once a password has been changed, a non-superuser must wait 24 hours before changing the password again.

Establishing Daylight Savings RulesAvaya 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).

InstructionsEstablishing daylight savings rulesIn our example, we set daylight savings time rules. To modify a daylight savings rule: 1. Type change daylight-savings-rules and press Enter. The Daylight Savings Rules screen appears.


31

System Basics

Figure 3: Daylight Savings Rules screenDAYLIGHT SAVINGS RULES Rule Change Day 0: 1: 2: 3: 4: 5: 6: 7: No Daylight Savings Start: Stop: Start: Stop: Start: Stop: Start: Stop: Start: Stop: Start: Stop: Start: Stop: first first first first first first first first first first first first first first Sunday___ Sunday___ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ on on on on on on on on on on on on on on or or or or or or or or or or or or or or after after after after after after after after after after after after after after April___ 1 October_25 ________ __ ________ __ ________ __ ________ __ ________ __ ________ __ ________ __ ________ __ ________ __ ________ __ ________ __ ________ __ at at at at at at at at at at at at at at _2:00 _2:00 __:__ __:__ __:__ __:__ __:__ __:__ __:__ __:__ __:__ __:__ __:__ __:__ 01:00

Month___Date Time____Increment

2. Complete the Start fields for rule 1. Rule 1 applies to all time zones in the U.S. and begins on the first Sunday on or after 1 April at 2:00 a.m. with a 01:00 increment. Daylight Savings Time stops on the first Sunday on or after 25 October at 2:00 a.m. also with a 01:00 increment (used as a decrement when switching back to Standard time. The increment is added to standard time at the specified start time and the clock time shifts by that increment (for example, for 01:59:00 to 01:59:59 the clock time shows 01:59 and at 02:00 the clock shows 03:00). On the stop date, the increment is subtracted from the specified stop time (for example, for 01:59:00 to 01:59:59 the clock time shows 01:59 and at 02:00 the clock shows 01:00). a. Type Sunday in the Change Day field. b. Type April in the Month field. c. Type 1 in the Date field. d. Type 2:00 in the Time field. e. Type 1:00 in the Increment field. This information specifies the day, month, date, and time and increment at which you want the system clock to transition to daylight saving time.


Establishing Daylight Savings Rules

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). 3. Complete the Stop fields for rule 1. a. Type Sunday in the Change Day field. b. Type October in the Month field. c. Type 25 in the Date field. d. Type 2:00 in the Time field. This information specifies the day, month, date, and time you want the system clock to transition back to standard time. 4. Press Enter to save your changes.

Displaying daylight savings time rulesTo display daylight savings time rules: 1. Type display daylight-savings-rules and press Enter. The Daylight Savings Rules screen appears. Verify the information you entered is correct.

Setting the system date and timeUpdate 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 CDR records are correct. CDR does not work until the date and time have been entered. Note: Changing the date and time may modify CDR data by 9 hours and 59 minutes. Therefore, you should change the date and time after normal business hours. After you change the date and time, review the time settings for any adjunct (other than AUDIX) linked to your system that uses the system time.

Note:

Before you startBefore 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.


33

System Basics

Setting Time of Day Clock SynchronizationTime 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:

S8700 or S8710 IP-Connect S8700 or S8710 Multi-Connect S8700 or S8710 Media Server

For additional information, see Avaya Communication Manager Contact Center Guide to ACD Contact Centers. The following systems use Avaya Site Administration (ASA) for time synchronization.

DEFINITY Server R DEFINITY Server CSI DEFINITY Server SI

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.

InstructionsNote:

Note: These instructions are for Avaya DEFINITY R, DEFINITY CSI, and DEFINITY SI servers. For additional information, see Avaya Communication Manager Contact Center Guide to ACD Contact Centers.

To set Time of Day Clock Synchronization: 1. Activate the Avaya Site Administration screen.


Setting Time of Day Clock Synchronization

2. Click the Fault & Performance tab. The Fault & Performance icons display. Figure 4: Avaya Site Administration menu

3. Click Time Synchronization. The Time Synchronization - Properties screen displays.


35

System Basics

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



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


37

System Basics

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



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


39

System Basics

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

Related topicsSee Avaya Communication Manager Contact Center Guide to ACD Contact Centers, for more information about using time of day clock synchronization.


Setting the System Date and Time

Setting the System Date and TimeIn our example, we set the date and time to Tuesday, November 5 at 8:30 p.m. standard time. To set the system date and time: 1. Type set time and press Enter. The Date and Time screen displays. Figure 10: Date and Time screenDATE AND TIME DATE Day of the Week: Tuesday Day of the Month: 5 TIME Hour: 20 Minute: 30 second: XX Daylight Savings Rule: 1 Type: standard Month: November Year: 2002

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 2002 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. Note: When you change the date or time, some display phones may not automatically refresh the display. If this occurs, have each user press the date/time button on their telephone to update the display.

Note:


41

System Basics

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

Related topicsSee Establishing Daylight Savings Rules on page 31 for more information about setting system time. For additional information, see Avaya Communication Manager Contact Center Guide to ACD Contact Centers, 555-230-716.

Using the Bulletin BoardAvaya 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: 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.

Note:


Using the Bulletin Board

InstructionsDisplaying messagesTo display the bulletin board: 1. Type display bulletin-board and press Enter. The Bulletin Board screen displays. Figure 11: Bulletin Board screenMessage (* indicates high-priority) *Avaya is in the process of *investigating your trunk lockup problem. *The Bulletin Board will be updated as *we find information. * * * * * * We recently added a new trunk group (14) and have had many of the members getting locked up. Date 03/02/98 03/02/98 03/02/98 03/02/98

03/02/98 03/02/98 03/02/98

Posting a messageIn 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 and press Enter. The Bulletin Board screen displays. There are three pages of message space within the bulletin board. The first page has 19 lines, but you can only enter text on lines 11-19. The first 10 lines on page 1 are for high-priority messages from Avaya personnel and are noted with an asterisk (*). The second and third pages each have 20 lines, and you can enter text on any line. The system automatically enters the date the message was posted or last changed to the right of each message line.


43

System Basics

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 messagesTo delete a message from the bulletin board: 1. Type change bulletin-board and press Enter. The Bulletin Board screen appears. 2. Enter a space as the first character on each line of the message you want to delete and press Enter. 3. Press Enter to save your changes.

Saving TranslationsCommunication 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: Save translations on a daily basis. You may want to save translations after business hours to prevent dial tone delays or during slow business hours if your business is open 24 hours.

Note:

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.


Saving Translations

Tip:Tip:

To determine if your system saves translations automatically, type display system-parameters maintenance to see if you have scheduled maintenance.

Translation copy protection assigns a number to a specific telephone system and to the flash card or set of flash cards that belong to that system. For Avaya Communication Manager on a DEFINITY Server CSI or Communication Manager on a DEFINITY Server SI, 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 IDs 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.

Before you startIf you are saving translations to a memory card or tape, you must verify the memory card or tape is in place and clear any active alarms from the alarms panel. If you have Avaya Communication Manager on a DEFINITY Server CSI or Communication Manager on a DEFINITY Server SI, verify the memory card translation ID matches the translation ID of your servers Flash PROM.

InstructionsIn our example, we save translations to the tapes on both processor A and B. To save translations manually: 1. Type save translation both tape and press Enter. The save process can take up to 10 minutes. You cannot administer your system while the save is in process. The Save Translation screen displays.


45

System Basics

Figure 12: Save Translation screenSAVE TRANSLATION

Processor SPE_A SPE_B

Command Completion Status Success Success

Error Code 0 0

2. If there is an error message in the Command Completion Status field and an error code in the Error Code field, clear the error and repeat the save process.

More informationWhen mass storage system (MSS) devices on both processors in a duplex system are specified, translation data is saved from the active processor to the active and standby MSS devices at the same time. If the save to one device fails or one device is out of service, the other save continues. You receive the status of each save separately. Note: If you have a duplex system and you save translation data to both MSS devices one at a time, translation data inconsistencies between the two devices can occur.

Note:

Fixing problemsNote: You cannot see whether the translation ID on

avaya admin

Documents

Transcript of avaya admin