Avaya communication manager инструкция на русском

• Page 1
  Administrator Guide for Avaya Communication Manager 03-300509 Issue 2.1 May 2006…
• Page 2
  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.

• Page 3: Table Of Contents

  Related Resources……..How to obtain Avaya books on the Web ….. . .

• Page 4
  Displaying Caller Information ……Displaying ANI Calling Party Information ….. . 4 Administrator Guide for Avaya Communication Manager…
• Page 5
  Contents Displaying ICLID Information ……Changing the Display Language ……Setting up Directory Buttons .
• Page 6
  Adding a DIOD Trunk Group ……6 Administrator Guide for Avaya Communication Manager…
• Page 7
  Contents Setting up Digital Trunks ……. Adding Trunks to a Trunk Group ……Removing Trunk Groups .
• Page 8
  Cordless telephone ……..Internet Protocol (IP) Softphones ……8 Administrator Guide for Avaya Communication Manager…
• Page 9
  Contents Chapter 19: Screen Reference ….. . . 705 AAR and ARS Digit Analysis Table ……AAR and ARS Digit Conversion Table .
• Page 10
  ……..1184 10 Administrator Guide for Avaya Communication Manager…
• Page 11
  Contents ISDN Network Facilities ……. . 1191 ISDN Numbering Calling Party Number Conversion for Tandem Calls ..1191 ISDN Trunk Group .
• Page 12
  Toll Analysis ……..1590 12 Administrator Guide for Avaya Communication Manager…
• Page 13
  Contents Tone Generation ……..1594 Trunk Group .
• Page 14
  Contents 14 Administrator Guide for Avaya Communication Manager…

• Page 15: About This Book

  About this book Overview Avaya 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.

• Page 16: Contents

  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.

• Page 17: Conventions Used

  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.

• Page 18: Admonishments

  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.

• Page 19: Trademarks

  Avaya Business Advocate User Guide, 07-300653 Avaya Call Center Release Automatic Call Distribution (ACD) Guide, 07-300478 Avaya Call Center Release Call Vectoring and Expert Agent Selection (EAS) Guide, 07-300477 Avaya Communication Manager Advanced Administration Quick Reference, 03-300364 Avaya Communication Manager Basic Administration Quick Reference, 03-300363…

• Page 20: How To Obtain Avaya Books On The Web

  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: If you don’t have Acrobat Reader, you can get a free copy at…

• Page 21: How To Order Documentation

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

• Page 22
  About this book 22 Administrator Guide for Avaya Communication Manager…

• Page 23: Chapter 1: System Basics

  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.

• Page 24
  The Login prompt displays. 2. Complete the steps for Logging into the System on page 23. For information about setting up remote administration, contact your Avaya technical support representative. Failed login attempts SAT login failure If you are using the System Access Terminal (SAT), you can use the Security Violations Notification feature to disable a user’s login if a threshold of failed login attempts is reached…
• Page 25
  Manager, 555-245-205. Server login failure Communication 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.
• Page 26
  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 Media 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 Media Server Web Interface.
• Page 27
  AUDIX through a serial connection. Install ASA on your computer using the Avaya Site Administration CD. Place the ASA CD in the CD-ROM drive and follow the installation instructions in the install wizard. ASA supports a terminal emulation mode, which is directly equivalent to using SAT commands on a dumb terminal or through an SSH session.
• Page 28
  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 Media Server. When you initially run ASA, you are prompted to create a new entry for the switch connection.

• Page 29: Logging In With Access Security Gateway

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

• Page 30
  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.

• Page 31: Logging Off The System

  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.

• Page 32: Setting Command Permissions

  System Basics Setting Command Permissions Avaya Communication Manager allows you to modify the permissions associated with a login. The system maintains default permissions for each level of login, but you might 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.

• Page 33: Establishing Daylight Savings Rules

  Establishing Daylight Savings Rules Avaya Communication Manager allow you to set the daylight savings time rules so that features, such as time-of-day routing and call detail recording (CDR), adjust automatically to daylight savings time. The correct date and time ensure that CDR records are correct. You can set daylight savings time rules to transition to and from daylight savings time outside of normal business hours, so the number of affected CDR records is small.

• Page 34
  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). 34 Administrator Guide for Avaya Communication Manager…
• Page 35
  Establishing Daylight Savings Rules 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.

• Page 36: 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.

• Page 37
  Setting Time of Day Clock Synchronization Figure 4: Avaya Site Administration menu 3. Click Time Synchronization. The Time Synchronization — Properties screen displays. Issue 2.1 May 2006…
• Page 38
  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. 38 Administrator Guide for Avaya Communication Manager…
• Page 39
  Setting Time of Day Clock Synchronization 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.
• Page 40
  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. 40 Administrator Guide for Avaya Communication Manager…
• Page 41
  Setting Time of Day Clock Synchronization 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.
• Page 42
  16. If the time synchronization description is satisfactory, click Finish. If the time synchronization is not satisfactory, click Back and revise the necessary information. For more information about setting time synchronization, see Avaya Call Center Release Automatic Call Distribution (ACD) Guide, 07-300478. 42 Administrator Guide for Avaya Communication Manager…

• Page 43: Setting The System Date And Time

  Setting the System Date and Time Setting the System Date and Time Update the date and time for events such as a leap year, the change to or from daylight savings time, or a system restart after a power failure. The correct date and time assure that Call Detail Recording (CDR) records are correct.

• Page 44
  The Date and Time screen displays. Verify the information you entered is correct. Related topics Establishing Daylight Savings Rules on page 33 for more information about setting system time. For additional information, see Avaya Call Center Release Automatic Call Distribution (ACD) Guide, 07-300478. 44 Administrator Guide for Avaya Communication Manager…

• Page 45: Using The Bulletin Board

  Using the Bulletin Board Using the Bulletin Board Avaya Communication Manager allows you to post information to a bulletin board. You can also display and print messages from other Avaya server administrators and Avaya personnel using the bulletin board. Anyone with the appropriate permissions can use the bulletin board for messages.

• Page 46
  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.

• Page 47: Saving Translations

  Translation copy protection assigns a number to a specific telephone system and to the flash card or set of flash cards that belong to that system. For Avaya Communication Manager on a DEFINITY Server CSI, this number is the same on both the translation storage device (flash card) and the Flash PROM (Programmable Read Only Memory) of the processor circuit pack.

• Page 48: Before You Start

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

• Page 49: Performing Backups

  For more information about error messages and how to correct them, or backing up or restoring your system, see the maintenance book for your system. Performing Backups Information on performing backups to your system can be found in the Maintenance Procedures for Avaya Communication Manager, Media Gateways and Servers, 03-300432. Issue 2.1 May 2006…

• Page 50
  System Basics 50 Administrator Guide for Avaya Communication Manager…

• Page 51: Chapter 2: Planning The System

  Chapter 2: Planning the System Understanding Your Configuration At a very basic level, Avaya Communication Manager consists of hardware to perform call processing, and the software to make it run. You use the administration interface to let the system know what hardware you have, where it is located, and what you want the software to do with it.

• Page 52
  So, if you have a single-carrier cabinet, the circuit pack in slot 06 would have the address 01A06. If you want to attach a telephone to the 3rd port on this board, the port address is 01A0603 (01=cabinet, A=carrier, 06=slot, 03=port). 52 Administrator Guide for Avaya Communication Manager…

• Page 53: Understanding The Dial Plan

  Understanding the Dial Plan Understanding the Dial Plan Your dial plan tells your system how to interpret dialed digits. For example, if you dial 9 on your system to access an outside line, it is actually the dial plan that tells the system to find an external trunk when a dialed string begins with a 9.

• Page 54
  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. 54 Administrator Guide for Avaya Communication Manager…
• Page 55
  Administering a Uniform Dial Plan You can also set up a Uniform Dialing Plan that can be shared among a group of servers. For more information, see Feature Description and Implementation for Avaya Communication Manager, 555-245-205. Administering a Multi-Location Dial Plan…
• Page 56
  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.
• Page 57
  Understanding the Dial Plan reach one extension, and three 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. Adding feature access codes As your needs change, you might want to add a new set of FAC for your system.
• Page 58
  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: To remove any feature access code, merely delete the existing FAC and leave Tip: the field blank. 58 Administrator Guide for Avaya Communication Manager…

• Page 59: Controlling The Features Your Users Can Access

  Controlling the features your users can access Controlling the features your users can access Avaya 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.

• Page 60: Changing System Parameters

  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.

• Page 61: Setting Wan Bandwidth Limits Between Network Regions

  Setting WAN bandwidth limits between network regions 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.

• Page 62
  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. 62 Administrator Guide for Avaya Communication Manager…

• Page 63: Administering Treatment For Denied Or Invalid Calls

  Administering Treatment for Denied or Invalid Calls 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: Type display ip-network region <n>…

• Page 64: Locally Sourced Announcements And Music

  For more information on locally-sourced Music-on-Hold, see the «Locally Sourced Announcements and Music» feature in the Feature Description and Implementation for Avaya Communication Manager, 555-245-205. Locally sourced announcements and music The Locally Sourced Announcements and Music feature is based on the concept of audio source groups.

• Page 65
  Setting up Music-on-Hold 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.
• Page 66
  Partitioning, you cannot set up Music on Hold this way. See Providing MOH Service for Multiple Tenants on page 67 for more information. To set system parameters for MOH: 1. Type change system-parameters features. Press Enter. Feature-Related System Parameters screen appears. 66 Administrator Guide for Avaya Communication Manager…
• Page 67
  Setting up Music-on-Hold Figure 18: Feature-Related System Parameters screen change system-parameters features page 1 of x FEATURE-RELATED SYSTEM PARAMETERS Self Station Display Enabled? n Trunk-to-Trunk Transfer? none Automatic Callback — No Answer Timeout Interval (rings): 4_ Call Park Timeout Interval (minutes): 10 Off-Premises Tone Detect Timeout Interval (seconds): 20_ AAR/ARS Dial Tone Required? y Music/Tone On Hold: music…
• Page 68
  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. Tenant screen appears. 68 Administrator Guide for Avaya Communication Manager…
• Page 69
  Setting up Music-on-Hold Figure 20: Tenant screen change tenant 1 Tenant 1 Tenant Description: ________________________________________ Attendant Group: 1 Ext Alert Port (TAAS): _______ Ext Alert (TAAS) Extension: ____ Night Destination: _____ Music Source: 1 Attendant Vectoring VDN: 9. In the Tenant Description field, type Dentist. This identifies the client in this partition.

• Page 70: Receiving Notification In An Emergency

  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.

• Page 71
  Receiving Notification in an Emergency Figure 21: ARS Digit Analysis Table screen change ars analysis Page 1 of X ARS DIGIT ANALYSIS TABLE Percent Full: Dialed Total Route Call Node String Min Max Pattern Type Reqd _________________ _____ ____ _________________ _____ ____ _________________…

• Page 72: More Information

  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.

• Page 73: Notifying A Digital Pager Of An Emergency

  Notifying a Digital Pager of an Emergency 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.

• Page 74: Other Useful Settings

  This is the length of time between DTMF tones for each digit. 12. Press Enter to save your changes. Related topics Refer to the Crisis Alert feature in Feature Description and Implementation for Avaya Communication Manager, 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.

• Page 75: Distinctive Ringing

  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 Class of Service for more information.

• Page 76: Controlling The Calls Your Users Can Make And Receive

  Planning the System Controlling the Calls Your Users Can Make and Receive The Avaya 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.

• Page 77
  Controlling the Calls Your Users Can Make and Receive 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.
• Page 78
  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.

• Page 79: Station Lock

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

• Page 80
  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. 80 Administrator Guide for Avaya Communication Manager…

• Page 81: Chapter 3: Managing Telephones

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

• Page 82
  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. 82 Administrator Guide for Avaya Communication Manager…

• Page 83: Adding New Telephones

  Adding New Telephones 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 ●…

• Page 84
  (DID) or reached via a central telephone number. Be sure to note your port and extension selections on your system’s paper records. 84 Administrator Guide for Avaya Communication Manager…
• Page 85
  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.
• Page 86
  For more information on TTI, see «Terminal Translation Initialization» in Feature Description and Implementation for Avaya Communication Manager, 555-245-205. For more information on the System Capacity screen, see Maintenance Commands for Avaya Communication Manager, Media Gateways and Servers, 03-300431. When the Station screen appears, you see the extension number and some default field values.

• Page 87: Using Templates To Add Telephones

  Using Templates to Add Telephones 3. Type the port address in the Port field. Note: Port 1720 is turned off by default to minimize denial of service situations. This Note: 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.

• Page 88
  Fill in the information on the Agent LoginID screen. For more information, see Avaya Call Center Release Automatic Call Distribution (ACD) Guide, 07-300478.

• Page 89: Using An Alias

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

• Page 90: Customizing Your Telephone

  7. Press Enter to save your changes. Now you can follow the instructions for adding a new telephone (or adding a fax or modem). Avaya Communication Manager now recognizes the new type (6220 or modem) that you enter in the Type field.

• Page 91: Upgrading Telephones

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

• Page 92: Swapping Telephones

  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. 92 Administrator Guide for Avaya Communication Manager…

• Page 93: Using Actr To Move Telephones

  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.

• Page 94
  ● 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.
• Page 95
  Using ACTR to Move Telephones Figure 27: Station screen change station nnnn Page 2 of X STATION FEATURE OPTIONS LWC Reception? spe Auto Select Any Idle Appearance? n LWC Activation? y Coverage Msg Retrieval? y LWC Log External Calls? n Auto Answer: none CDR Privacy? n…

• Page 96: Using Tti To Move Telephones

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

• Page 97
  Using TTI to Move Telephones Instructions Merging an extension with a TTI telephone CAUTION: You can destroy your hardware if you attempt to connect an analog telephone to CAUTION: a digital port. To merge an extension to a telephone with TTI, complete the following steps from the telephone you want to merge: 1.
• Page 98
  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.

• Page 99: Removing Telephones

  Removing Telephones — 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. — 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.

• Page 100
  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. 100 Administrator Guide for Avaya Communication Manager…

• Page 101: Adding A Fax Or Modem

  Adding a Fax or Modem 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 83.

• Page 102: Adding An Ip Softphone

  Avaya Communication Manager, 555-233-504. Adding an IP Softphone Avaya IP 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 Avaya Communication Manager and then make and receive telephone calls from the telephone extension.

• Page 103
  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.
• Page 104
  Product ID page Be sure that your DEFINITY CSI has a CLAN board and an IP Media Processor board. Once you’re finished administering Avaya Communication Manager, you need to install the IP Softphone software on each user’s PC. Adding a road-warrior mode You can use the road-warrior mode when you have only a single telephone line available to access Avaya Communication Manager over the IP network.
• Page 105
  Adding an IP Softphone To assign an H.323 extension, complete the following steps: 1. Type add station 3000. Press Enter. Station screen appears. Figure 28: Station screen add station next Page 1 of X STATION Extension: Lock Messages? n BCC: 0 Type: Security Code: TN: 1…
• Page 106
  6. In the IP Softphone field, type y. 7. 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. 106 Administrator Guide for Avaya Communication Manager…
• Page 107
  Adding an IP Softphone 8. In the Multimedia Mode field, type enhanced. 9. Press Enter to save your work. Now you can install and configure the software on the user’s PC. In this example, the user will login by entering their DCP extension (3001) and password (1234321). Adding a telecommuter mode Assign this configuration to remote users who have two available telephone lines.

• Page 108: Adding An Ip Telephone

  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.

• Page 109
  Adding an IP Telephone 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. Station screen appears. Figure 30: Station screen add station nnnn Page 1 of X STATION Extension: Lock Messages? n…
• Page 110
  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. 110 Administrator Guide for Avaya Communication Manager…
• Page 111
  Adding an IP Telephone 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.
• Page 112
  3. Type block in the Remote Softphone Emergency calls field. Press Enter to save your changes. CAUTION: An Avaya IP endpoint can dial emergency calls (for example, 911 calls in the CAUTION: U.S.). It only reaches the local emergency service in the Public Safety Answering Point area where the telephone system has local trunks.

• Page 113: Setting Up Remote Office

  Avaya Remote Office provides IP processing capabilities to traditional call handling for voice and data between Avaya 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.

• Page 114: Adding A Node

  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.

• Page 115
  Setting up Remote Office Figure 33: Remote Office screen add remote office n REMOTE OFFICE Node Name: _______________ Network Region: ___ Location: __ Site Data: ______________________________ ______________________________ ______________________________ 6. Fill in the following fields: Node Name — match the name on the IP Node Names screen. ●…
• Page 116
  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. Signaling Group screen appears. 116 Administrator Guide for Avaya Communication Manager…
• Page 117
  Setting up Remote Office Figure 35: Signaling Group screen Page 1 of x SIGNALING GROUP Group Number Group Type: h.323 Remote Office? n Max Number of NCA TSC: ___ SBS? y Max number of CA TSC: IP Video? Trunk Group for NCA TSC: Trunk Group for Channel Selection: Supplementary Service Protocol: _ T303 Timer(sec): 10…
• Page 118
  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. 118 Administrator Guide for Avaya Communication Manager…
• Page 119
  Now you need to assign the region number to the CLAN circuit pack. All the endpoints registered with a specific CLAN circuit pack belong to the CLAN’s region. See Administration for Network Connectivity for Avaya Communication Manager, 555-233-504, for more information. Adding telephones to Remote Office Be sure the extensions you add fit your dialing plan.
• Page 120
  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 Avaya Communication Manager.
• Page 121
  5. Administer the CLAN Ethernet interface or processor CLAN. 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.
• Page 122
  Station Firmware Download Access Code: Station Lock Activation: Deactivation: Station Security Code Change Access Code: Station User Admin of FBI Assign: Remove: Station User Button Ring Control Access Code: Telephone Activation: #* Terminal Dial-up Test Access Code: 122 Administrator Guide for Avaya Communication Manager…
• Page 123
  Setting up Remote Office 2. In the Station Firmware Download Access Code field, enter a valid FAC as defined in the dial plan. 3. Press Enter to save your changes. 4. Take the 2410 or 2420 DCP telephone off-hook. 5. Dial the Station Firmware Download FAC (for instance, *36). 6.
• Page 124
  STATUS FIRMWARE STATION DOWNLOAD Image file: Schedule Download? Continue daily until completed? Start Date/Time: Stop Date/Time: Terminal type for download: Extension range: Number of stations in range: Stations completed: Stations unsuccessful: 124 Administrator Guide for Avaya Communication Manager…
• Page 125
  Setting up Remote Office Note: If you add the qualifier last to the status firmware download command, Note: 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.
• Page 126
  Managing Telephones 126 Administrator Guide for Avaya Communication Manager…

• Page 127: Chapter 4: Managing Telephone Features

  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.

• Page 128
  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. 128 Administrator Guide for Avaya Communication Manager…
• Page 129
  Adding Feature Buttons 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.
• Page 130
  ____________ ____________ ____________ ____________ ____________ ____________ ____________ ____________ ____________ ____________ ____________ ____________ Caution: Adding new button types to this list will cause all button labels associated with that button type to be lost 130 Administrator Guide for Avaya Communication Manager…
• Page 131
  Adding Feature Buttons 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: When you enter the special button types abr-spchar or abrv-dial, an additional Note:…

• Page 132: Telephone Feature Buttons Table

  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.

• Page 133
  Telephone Feature Buttons Table Table 2: Telephone feature buttons (continued) Button name Button label Description Maximum 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.
• Page 134
  Assign this button to any user who you want to backup the attendant. 3 of 21 134 Administrator Guide for Avaya Communication Manager…
• Page 135
  Telephone Feature Buttons Table Table 2: Telephone feature buttons (continued) Button name Button label Description Maximum atd-qtime 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.
• Page 136
  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. 5 of 21 136 Administrator Guide for Avaya Communication Manager…
• Page 137
  Telephone Feature Buttons Table Table 2: Telephone feature buttons (continued) Button name Button label Description Maximum busy-ind Busy Busy Indication: indicates the busy or 1 per TAC/ (TAC/Ext: __) idle status of an extension, trunk group, terminating extension group (TEG), hunt group, or loudspeaker paging zone.
• Page 138
  Conference Allows a user to display information 1 per Display about each party of a conference call. station This button can be assigned to stations and attendant consoles. 7 of 21 138 Administrator Guide for Avaya Communication Manager…
• Page 139
  Telephone Feature Buttons Table Table 2: Telephone feature buttons (continued) Button name Button label Description Maximum 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.
• Page 140
  Directory. dir-pkup dir-pkup Directed call pickup: allows the user to answer a call ringing at another extension without having to be a member of a pickup group. 9 of 21 140 Administrator Guide for Avaya Communication Manager…
• Page 141
  Telephone Feature Buttons Table Table 2: Telephone feature buttons (continued) Button name Button label Description Maximum disp-chrg Display Provides your display telephone with a 1 per Charge visual display of accumulated charges station on your current telephone call. Used exclusively outside the U.S. and Canada.
• Page 142
  Far End Mute Allows a user to mute a selected party 1 per for Conf on a conference call. This button can station be assigned to stations and attendant consoles. 11 of 21 142 Administrator Guide for Avaya Communication Manager…
• Page 143
  Number: The extension of the page group. headset Headset Signals onhook/offhook state changes to Communication Manager. The green LED is on for offhook state and off (dark) for onhook state. hunt-ns Hunt Group Hunt-Group Night Service: places a…
• Page 144
  8 for multi-carrier cabinets or 1 to 4 for single-carrier cabinets. lsvn-halt Login SVN Login Security Violation Notification: 1 per activates or deactivates referral call system when a login security violation is detected. 13 of 21 144 Administrator Guide for Avaya Communication Manager…
• Page 145
  Telephone Feature Buttons Table Table 2: Telephone feature buttons (continued) Button name Button label Description Maximum 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…
• Page 146
  «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 15 of 21 146 Administrator Guide for Avaya Communication Manager…
• Page 147
  Telephone Feature Buttons Table Table 2: Telephone feature buttons (continued) Button name Button label Description Maximum mm-cfwd MM CallFwd Multimedia Call Forward: used to 1 per activate forwarding of multimedia calls station as multimedia calls, not as voice calls. mm-datacnf MM Datacnf Multimedia Data Conference: used to 1 per…
• Page 148
  Priority Call Priority Calling: allows a user to place 1 per priority calls or change an existing call station to a priority call. 17 of 21 148 Administrator Guide for Avaya Communication Manager…
• Page 149
  Telephone Feature Buttons Table Table 2: Telephone feature buttons (continued) Button name Button label Description Maximum q-calls 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.
• Page 150
  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. 19 of 21 150 Administrator Guide for Avaya Communication Manager…
• Page 151
  Telephone Feature Buttons Table Table 2: Telephone feature buttons (continued) Button name Button label Description Maximum trunk-ns Trunk Grp Trunk-Group Night Service: places a 3 per trunk (Grp: ___) trunk-group into night service. Grp: group Trunk group number. uui-info UUI-Info Allows users to see up to 32 bytes of 1 per ASAI-related UUI-IE data.
• Page 152
  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. 21 of 21 152 Administrator Guide for Avaya Communication Manager…

• Page 153: Adding Abbreviated Dialing Lists

  Adding Abbreviated Dialing Lists 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.

• Page 154
  To give station 4567 access to the group list: 1. Type change station 4567. Press Enter. 2. Press Next Page until you see Station screen (page 3), containing the Abbreviated Dialing List fields. 154 Administrator Guide for Avaya Communication Manager…
• Page 155
  Adding Abbreviated Dialing Lists Figure 47: Station screen change station nnnn Page 3 of X STATION SITE DATA Room: _______ Headset? n Jack: ___ Speaker? n Cable: ___ Mounting: d Floor: _______ Cord Length: 0_ Building: _______ Set Color: _____ ABBREVIATED DIALING List1: ________ List2: _________…
• Page 156
  Press have pressed the Enter. incorrect feature 2. Review the current feature button. button assignments to determine if the user was pressing the assigned button. 1 of 2 156 Administrator Guide for Avaya Communication Manager…
• Page 157
  Adding Abbreviated Dialing Lists Problem Possible causes Solutions A user cannot If the user Resolution: ● access a dial attempted to 1. Type display station list — continued press the correct nnnn, where nnnn is the feature button, user’s extension. Press the button might Enter.

• Page 158: Setting Up Bridged Call Appearances

  System Capacity screen for the abbreviated dialing values (type display capacity). For details on the System Capacity screen, see Maintenance Commands for Avaya Communication Manager, Media Gateways and Servers, 03-300431. Related topics For more information, see «Abbreviated Dialing»…

• Page 159
  Setting up Bridged Call Appearances 2. If you want to use a new telephone for the bridged-to extension, duplicate a station. For information, see Using Templates to Add Telephones on page 87. 3. Type change station and the bridged-to extension. Press Enter. 4.
• Page 160
  Cable: ___ Mounting: d Floor: _______ Cord Length: 0_ Building: _______ Set Color: _____ ABBREVIATED DIALING List1: ________ List2: _________ List3: _________ BUTTON ASSIGNMENTS 1: call-appr 2: call-appr 3: call-appr 4: audix-rec Ext: 4000 160 Administrator Guide for Avaya Communication Manager…
• Page 161
  Setting up Bridged Call Appearances Figure 50: Station screen (digital set) add station nnnn Page 3 of X STATION SITE DATA Room: _______ Headset? n Jack: ___ Speaker? n Cable: ___ Mounting: d Floor: _______ Cord Length: 0_ Building: _______ Set Color: _____ ABBREVIATED DIALING List1: ________…

• Page 162: Setting Up An Extension To Cellular Feature Access Button

  1. Type change station n (where n is the extension of an Extension to Cellular-enabled station — in this example, 1034). Press Enter. 2. Press the Next Page button twice to display the Station screen (page 162 Administrator Guide for Avaya Communication Manager…

• Page 163
  The feature status button on the office telephone indicates the current state of Note: 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. Issue 2.1 May 2006…

• Page 164: Setting Up Terminal Self-Administration

  ‘*’ 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. 164 Administrator Guide for Avaya Communication Manager…

• Page 165
  ● 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 ●…

• Page 166: Setting Up Enterprise Mobility User

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

• Page 167
  Setting Up Enterprise Mobility User 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 code, and the set type of the visited telephone to the home server.
• Page 168
  2. Verify that the Personal Station Access (PSA) field is set to y. This field applies to the primary telephone and must be set to y for EMU. 3. Type display feature-access-codes. The system displays the Feature Access Codes screen. 168 Administrator Guide for Avaya Communication Manager…
• Page 169
  EMU. You must enter the FAC of the server in the location from which you are dialing. Note: To avoid confusion, Avaya recommends that all the servers in the network have Note: the same EMU feature access codes.
• Page 170
  The valid entries to this field are y or n, with n as the default. You must set this field to y to allow this telephone to be used as a visited station by an EMU user. 4. Click Enter to save your changes. 170 Administrator Guide for Avaya Communication Manager…
• Page 171
  Setting Up Enterprise Mobility User Defining options for calling party identification To define the options for calling party identification: 1. Type display trunk-group x, where x is the number of the trunk group. The system displays the Trunk Group screen. Figure 55: Trunk Group screen add trunk-group next Page 3 of x…
• Page 172
  If the home server receives a request from a visited server for a telephone that already has an EMU visitor registration active, the old registration is terminated and the new registration is approved. If the primary telephone is in-use when a registration attempt is made, the registration attempt fails. 172 Administrator Guide for Avaya Communication Manager…
• Page 173
  Setting Up Enterprise Mobility User Deactivating EMU Use the following steps to deactivate the visited telephone: 1. At the visited telephone, enter the EMU deactivation FAC. You must enter the EMU deactivation FAC of the server in the location where you are dialing from.
• Page 174
  Managing Telephone Features 174 Administrator Guide for Avaya Communication Manager…

• Page 175: Chapter 5: Managing Attendant Consoles

  ● traffic patterns ● The number of consoles you can have in your organization varies depending on your Avaya solution. 302 attendant consoles Avaya Communication Manager supports the following 302 attendant consoles: the 302A/B, 302C, and 302D consoles. You might have a basic or enhanced version of these consoles.

• Page 176
  10. Console display panel 4. Warning lamps and call waiting lamps 11. Display buttons 5. Call appearance buttons 12. Trunk group select buttons 6. Feature area 13. Lamp Test Switch 7. Trunk group select buttons 176 Administrator Guide for Avaya Communication Manager…
• Page 177
  Attendant Consoles Figure 57: 302C attendant console Ringer Select Volume Date Time Control Control Warning Warning Busy Busy Forced Night Release Busy Calls Waiting Calls Waiting Warning Individual Calls Waiting PRQS WXYZ Alarm Alarm Reported Position Available Split Hold Cancel Start Release phdg302c KLC 031199…
• Page 178
  You can use the push-button on the left side of the console to activate or deactivate the console. A message appears on the console identifying that the button must be pressed to activate the console. 178 Administrator Guide for Avaya Communication Manager…
• Page 179
  Avaya PC consoles The Avaya PC Console is a Microsoft Windows-based call handling application for Avaya Communication Manager attendants. It provides an ideal way to increase your productivity and to better serve your customers. PC Console offers all the call handling capabilities of the hardware-based Avaya 302 attendant console with a DXS module, plus several enhanced features and capabilities.

• Page 180: Adding An Attendant Console

  Managing Attendant Consoles Adding an Attendant Console Usually Avaya connects and administers your primary attendant console during cutover. However, you might find a need for a second attendant console, such as a backup console that is used only at night. Note that these instructions do not apply to adding a PC Console or SoftConsole.

• Page 181
  Adding an Attendant Console 3. If you want this attendant to have its own extension, enter one in the Extension field. Tip: If you assign an extension to the console, the class of restriction (COR) and class Tip: of service (COS) that you assign on this Console screen override the COR and COS you assigned on the Console Parameters screen.

• Page 182: Attendant Console Feature Buttons

  (Code:_) Attendant CW Aud Off cw-ringoff Console (Calls Waiting) Attendant Control Cont Act act-tr-grp of Trunk Group Access (Activate) Attendant Control Cont Deact deact-tr-g of Trunk Group Access (Deactivate) 1 of 7 182 Administrator Guide for Avaya Communication Manager…

• Page 183
  Attendant Console Feature Buttons Table 3: Attendant console feature buttons (continued) Feature or Recommended Name Entered on Maximum Notes Function Button Label Station Screen Allowed Attendant Direct Local TG local-tgs (TAC:__) Trunk Group Remote TG remote-tgs (LT:__) Select (RT:__) Attendant Crisis Crisis Alert crss-alert Alert…
• Page 184
  (TAC/Ext: _) 1 per TAC/ Indication [status extension#) Ext. lamp] Facility Test Calls FTC Alarm trk-ac-alm [status lamp] Far End Mute Far End Mute fe-mute [display button] for Conf 3 of 7 184 Administrator Guide for Avaya Communication Manager…
• Page 185
  Attendant Console Feature Buttons Table 3: Attendant console feature buttons (continued) Feature or Recommended Name Entered on Maximum Notes Function Button Label Station Screen Allowed Group Display Group Display group-disp Group Select Group Select group-sel Hardware Failure Major Hdwe major-alrm 10 per [status lamps] Failure…
• Page 186
  Grp:_) 1 per hunt [status lamps] group Remote Access rsvn-halt rsvn-halt 1 per Security Violation system Ringing In Aud Off in-ringoff Security Violation ssvn-halt ssvn-halt 1 per Notification Halt system 5 of 7 186 Administrator Guide for Avaya Communication Manager…
• Page 187
  Attendant Console Feature Buttons Table 3: Attendant console feature buttons (continued) Feature or Recommended Name Entered on Maximum Notes Function Button Label Station Screen Allowed Serial Call Serial Call serial-cal Split/Swap Split-swap split-swap System Reset System Reset rs-alert Alert Alert [status lamp] Station Security ssvn-halt…
• Page 188
  8. Link: A link number — 1 to 8 for multi-carrier cabinets, 1 to 4 for single-carrier cabinets. 9. Grp: A trunk group number. 10. Grp: Group number of the hunt group. 11. Allows the attendant to alternate between active and split calls. 12. VDN of Origin must be enabled. 188 Administrator Guide for Avaya Communication Manager…

• Page 189: Setting Console Parameters

  Setting Console Parameters Setting Console Parameters You can define system-wide console settings on the Console Parameters screen. For example, if you want to warn your attendants when there are more than 3 calls in queue or if a call waits for more than 20 seconds, complete the following steps: 1.

• Page 190: Removing An Attendant Console

  Now you can unplug the console 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. 190 Administrator Guide for Avaya Communication Manager…

• Page 191: Providing Backup For An Attendant

  Providing Backup for an Attendant Providing Backup for an Attendant Avaya Communication Manager allows you to configure your system so that you have backup positions for your attendant. Attendant Backup Alerting notifies backup telephones that the attendant need assistance in handling calls. The backup telephones are alerted when the attendant queue reaches the queue warning level or when the console is in night service.

• Page 192
  6. Press Enter to save changes. Now you need to train the user how to interpret the backup alerting and give them the TAAS feature access code so that they can answer the attendant calls. 192 Administrator Guide for Avaya Communication Manager…

• Page 193: Chapter 6: Managing Displays

  For more information on the buttons and languages you can set up for the messages that appear on the display, see the «Telephone Displays» feature description in the Feature Description and Implementation for Avaya Communication Manager, 555-245-505. Displaying ANI Calling Party Information Calling party information might consist of either a billing number that sometimes is referred to as Automatic Number Identification (ANI), or a calling party number.

• Page 194
  Receive Answer Supervision? n 2. Type tone in the Incoming Dial Type field. 3. Press Next Page and type *ANI*DNIS in the Incoming Tone (DTMF) ANI field. 4. Press Enter to save your changes. 194 Administrator Guide for Avaya Communication Manager…

• Page 195: Displaying Iclid Information

  Displaying ICLID Information Displaying ICLID Information Communication Manager collects the calling party name and number (Incoming Call Line Identification, or ICLID) received from the central office (CO) on analog trunks. Before you start Be sure the Analog Trunk Incoming Call ID field is set to y on the System-Parameters Customer-Options screen.

• Page 196
  Tone (msec): ____ Pause (msec): 150 OUTPULSING INFORMATION PPS: 10 Make(msec): 40 Break(msec): 60 PPM? y Frequency: 50/12k 5. Type 120 in the Incoming Seizure (msec) field. 6. Press Enter to save your changes. 196 Administrator Guide for Avaya Communication Manager…

• Page 197: Changing The Display Language

  Changing the Display Language Changing the Display Language This section explains how to set or change the display language. Setting the display language To set or change the display language: 1. Type change attendant n, where n is the number of the attendant console that you want to change.

• Page 198
  English: Select line ^ to cancel or another line. Translation: **************************************** 5. In the Translation field, type the translation of the message in the user-defined language. 6. Press Enter to save your changes. 198 Administrator Guide for Avaya Communication Manager…
• Page 199
  4. Transfer the Unicode Message file to an Avaya media server that is running Communication Manager 2.0 or later. You can use the Avaya Web pages, the Avaya Installation Wizard, or ftp to transfer the Unicode Message file.
• Page 200
  6. Load the Unicode message files. After you install the Unicode Message files, you must do a reset 4 to load the Unicode Message files in the Avaya media server that is running Communication Manager 2.0 or later. Starting with Communication Manager 2.1, a reset 4 is no longer required to load the Unicode Message file custom_unicode.txt.
• Page 201
  Changing the Display Language Figure 67: General Status screen status station nnnn page 2 of x GENERAL STATUS CONNECTED STATION INFORMATION Part ID Number: unavailable Serial Number: unavailable Station Lock Active? No UNICODE DISPLAY INFORMATION Native Name Scripts: 0x00000007:Latn;Lat1;LatA Display Messages Scripts: 0x04000007:Latn;Lat1;LatA;Jpan Station Supported Scripts: 0x7c000007:Latn;Lat1;LatA;Jpan;Chis;Chit;Korn «Scripts»…
• Page 202
  Thai Thai 00100000 0E80..0EFF Laoo 0F00..0FFF Tibetan 00200000 1000..109F Myanmar Mymr 00400000 10A0..10FF Georgian Geor 80000000 1100..11FF Hangul Jamo 1200..137F Ethiopic 13A0..13FF Cherokee 1400..167F Unified Canadian Aboriginal Syllabics 1680..169F Ogham 2 of 6 202 Administrator Guide for Avaya Communication Manager…
• Page 203
  Changing the Display Language Script Script tag Start .. End Script or block name SAT screen name (hex) Codes (note 1) 16A0..16FF Runic 00800000 1700..171F Tagalog Tglg 1720..173F Hanunoo 1740..175F Buhid 1760..177F Tagbanwa 01000000 1780..17FF Khmer Khmr 1800..18AF Mongolian 1E00..1EFF Latin Extended Additional 1F00..1FFF Greek Extended…
• Page 204
  08000000 Punctuation 10000000 20000000 40000000 04000000 3040..309F Hiragana 04000000 30A0..31BF Katakana 10000000 3100..312F Bopomofo 80000000 3130..318F Hangul Compatibility Jamo 31‘90..319F Kanbun 10000000 31A0..31BF Bopomofo Extended 04000000 31F0..31FF Katakana Phonetic Extensions 4 of 6 204 Administrator Guide for Avaya Communication Manager…
• Page 205
  Changing the Display Language Script Script tag Start .. End Script or block name SAT screen name (hex) Codes (note 1) 04000000 3200..32FF Enclosed CJK Letters and 08000000 Months 10000000 20000000 40000000 04000000 3300..33FF CJKV Compatibility 08000000 10000000 20000000 40000000 04000000 3400..4DBF CJKV Unified Ideographs…
• Page 206
  Related topics See the «Telephone Displays» and the «Administrable Display Languages» feature descriptions in the Feature Description and Implementation for Avaya Communication Manager, 555-245-205 for more information about choosing the language for messages on your display telephones and for mapping US English to Cyrillic (for Russian), Katakana (for Japanese), European, or Ukrainian characters.
• Page 207
  You entered «~c», and «*» Lower-case «c» has a specific meaning in appears on the display Avaya Communication Manager, and instead. therefore cannot be mapped to any other character. An asterisk «*» appears in its place.

• Page 208: Setting Up Directory Buttons

  Managing Displays Setting up Directory Buttons Your Communication Manager directory contains the names and extensions that are assigned on each station screen. Display-telephone users can use a telephone button to access the directory, use the touch-tone buttons to key in a name, and retrieve an extension from the directory.

• Page 209: Chapter 7: Handling Incoming Calls

  ● not available or not accepting calls provides the order in which Avaya Communication Manager redirects calls to alternate ● telephones or terminals establishes up to 6 alternate termination points for an incoming call ●…

• Page 210
  The hunt group coverage path would be used only for calls coming directly into the hunt group extension. Instructions To create a coverage path: 1. Type add coverage path next. Press Enter. The system displays the Coverage Path screen. 210 Administrator Guide for Avaya Communication Manager…
• Page 211
  Setting up Basic Call Coverage Figure 69: Coverage path screen change coverage path n Page 1 of COVERAGE PATH Coverage Path Number: n Hunt After Coverage: n Next Path Number: ___ Linkage: ___ COVERAGE CRITERIA Station/Group Status Inside Call Outside Call Active? Busy? Don’t Answer?
• Page 212
  Mute button enabled? y Display Language? English Model: Expansion Module? Survivable GK Node Name: Media Complex Ext: Survivable COR: IP Softphone? y Survivable Trunk Dest? Remote Office Phone? y IP Video Softphone? IP Video? 212 Administrator Guide for Avaya Communication Manager…

• Page 213: Setting Up Advanced Call Coverage

  System-Parameters Customer-Options screen, verify the Coverage of Calls ● Redirected Off-Net Enabled field is y. If not, contact your Avaya representative. You need call classifier ports for all situations except ISDN end-to-end signaling, in which ● case the ISDN protocol does the call classification. For all other cases, use one of the following: — Tone Clock with Call Classifier — Tone Detector circuit pack.

• Page 214
  Disable call classifier for CCRON over SIP trunks? 3. In the Coverage of Calls Redirected Off-Net Enabled field, type y. This instructs Avaya Communication Manager to monitor the progress of an off-net coverage or off-net forwarded call and provide further coverage treatment for unanswered calls.
• Page 215
  Setting up Advanced Call Coverage The call will not return to the system if the external number is the last point in the coverage path. To use a remote telephone number as a coverage point, you need to define the number in the Remote Call Coverage Table and then use the remote code in the coverage path.
• Page 216
  The call ends at the remote coverage point. 7. Press Enter to save your changes. Related topics For more information on coverage, see «Call Coverage» in Feature Description and Implementation for Avaya Communication Manager, 555-245-205. 216 Administrator Guide for Avaya Communication Manager…
• Page 217
  Setting up Advanced Call Coverage Defining time-of-day coverage The Time of Day Coverage Table on your system lets you redirect calls to coverage paths according to the time of day and day of the week when the call arrives. You need to define the coverage paths you want to use before you define the time of day coverage plan.
• Page 218
  2. Move your cursors to Coverage Path 1 and type t plus the number of the Time of Day Coverage Table. 3. Press Enter to save your changes. Now calls to extension 2054 redirect to coverage depending on the day and time that each call arrives. 218 Administrator Guide for Avaya Communication Manager…
• Page 219
  Setting up Advanced Call Coverage Creating coverage answer groups You can create a coverage answer group so that up to 8 telephones simultaneously ring when calls cover to the group. Anyone in the answer group can answer the incoming call. Instructions To add a coverage answer group: 1.

• Page 220: Setting Up Call Forwarding

  Note: If you have a V1, V2, or V3 system, you can see if a specific extension is Note: forwarded only by typing status station nnnn, where nnnn is the specific extension. 220 Administrator Guide for Avaya Communication Manager…

• Page 221
  Setting up Call Forwarding Related topics See «Call Forwarding» in Feature Description and Implementation for Avaya Communication Manager, 555-245-205. Setting up call forwarding for users This section shows you how to give your users access to call forwarding. Instructions We will change a call forwarding access code from a local telephone with a Class of Service of 1.
• Page 222
  9. On the Restrict Call Fwd-Off Net line, in the 1 column, type y. This restricts your users from forwarding calls off-site. If you want your users to be able to call off-site, leave this field as n. 222 Administrator Guide for Avaya Communication Manager…
• Page 223
  Setting up Call Forwarding 10. On the Call Forward Busy/DA line, in the 1 column, type y. This forwards a user’s calls when the telephone is busy or doesn’t answer after a programmed number of rings. 11. Press 1 to save your changes. Allowing users to specify a forwarding destination Now that you have set up system-wide call forwarding, have your users use this procedure if they want to change their call forwarding destination from their work (local) station.
• Page 224
  9. In the Coverage Path 1 and Coverage Path 2 fields, verify that both are defined enabling your user to move from one coverage path to another. The t1 and t2 are the numbers of the Time of Day Coverage Tables. 10. Press Enter to save your changes. 224 Administrator Guide for Avaya Communication Manager…

• Page 225: Setting Up Night Service

  Setting up Night Service Setting up Night Service You can use night service to direct calls to an alternate location when the primary answering group is not available. For example, you can administer night service so that anyone in your marketing department can answer incoming calls when the attendant is at lunch or has left for the day.

• Page 226
  If you are using tenant partitioning, the Night Destination field does not appear on the Listed Directory Numbers screen. Instead, it is on the Tenant screen. 4. Type change listed-directory-numbers. Press Enter. The system displays the Listed Directory Numbers screen. 226 Administrator Guide for Avaya Communication Manager…
• Page 227
  Setting up Night Service Figure 80: Listed Directory Number screen change listed-directory-number Page 1 of LISTED DIRECTORY NUMBERS Night Destination: Name 5. In the Night Destination field, add the night destination on the listed directory telephone. In our example, type 51002. 6.
• Page 228
  11. In voice mail, build your auto attendant with the extension of the Listed Directory Number, not the hunt group. The originally dialed number was the LDN. That is what Communication Manager passes to the voice mail. In the case of the INTUITY and newer embedded AUDIX Voice Mail systems, you can use the Auto Attendant routing table to send the calls to a common Auto Attendant mailbox.
• Page 229
  Setting up Night Service Figure 82: Attendant Console screen change attendant n Page 1 of ATTENDANT CONSOLE 1 Type: console Name: 27 character attd cons name Extension: 1000 Group: 1 Auto Answer: none Console Type: principal TN: 1 Data Module? y Port: 01C1106 COR: 1 Disp Client Redir? n…
• Page 230
  The destination can be an extension, a recorded announcement extension, a vector directory number, or a hunt group extension. 3. Press Enter to save your changes. 4. Type change console-parameters. Press Enter. The system displays the Console Parameters screen. 230 Administrator Guide for Avaya Communication Manager…
• Page 231
  We will define a feature access code (we’ll use 71) and configure the alerting device for trunk answer any station. You need a ringing device and 1 port on an analog line circuit pack. See the Hardware Description and Reference for Avaya Communication Manager, 555-245-207, for more information on the circuit pack. Issue 2.1 May 2006…
• Page 232
  3. Press Enter to save your changes. Once you set the feature access code, determine where the external alerting device is connected to the Communication Manager server (we’ll use port 01A0702). To set up external alerting: 1. Type change console-parameters. Press Enter.
• Page 233
  Setting up Night Service Figure 86: Console Parameters screen change console-parameters Page 1 of x CONSOLE PARAMETERS Attendant Group Name: OPERATOR COS: 0 COR: 0 Calls in Queue Warning: 5 Attendant Lockout? y Ext Alert Port (TAAS): CAS: none Night Service Act. Ext.: IAS (Branch)? n IAS Tie Trunk Group No.: IAS Att.
• Page 234
  Backup Alerting? n DID-LDN Only to LDN Night Ext? n Attendant Vectoring VDN: 5. In the EXT Alert Port (TAAS) field, type 01A0702. This is the port address assigned to the external alerting device. 234 Administrator Guide for Avaya Communication Manager…
• Page 235
  Setting up Night Service 6. Press Enter to save your changes. The system is in Night Service. Any calls to extension 2000 now go to extension 3000 (the guard’s desk). Any «0» seeking calls go to extension 3000 (the guard’s desk). To send LDN calls to the attendant during the day and to the TAAS bell at night: 1.
• Page 236
  The destination can be a station extension, a recorded announcement extension, a vector directory number, a hunt group extension, a terminating extension group, or attd if you want to direct the call to the attendant. 3. Press Enter to save your changes. 236 Administrator Guide for Avaya Communication Manager…
• Page 237
  Setting up Night Service Setting up night service for hunt groups You can administer hunt group night service if you want to direct hunt group calls to a night service destination. Let us say your helpline on hunt group 3 does not answer calls after 6:00 p.m. When customers call after hours, you would like them to hear an announcement that asks them to try their call again in the morning.
• Page 238
  An LDN call on a DID trunk extension 3000 A call on trunk group 4 extension 2000 An internal call to ‘0’ extension 3000 A call that redirects to the attendant the attendant queue through a coverage path 238 Administrator Guide for Avaya Communication Manager…

• Page 239: Adding Call Pickup

  Adding Call Pickup Adding Call Pickup Users might need to answer a call that is ringing at a nearby desk. With Communication Manager, a user can answer a call that is ringing at another telephone in three ways: Use Call Pickup. With Call Pickup, you create one or more pickup groups. A pickup group ●…

• Page 240
  Call Pickup, the Call Pickup button status lamp «flutters» for a few seconds. The fluttering status lamp indicates denial of service. The call that the member is currently on is not interrupted. 240 Administrator Guide for Avaya Communication Manager…
• Page 241
  Adding Call Pickup In all scenarios, the call appearance button on the telephone of the called group member: Stays steadily lit if the Temporary Bridged Appearance on Call Pickup? field on the ● Feature-Related System Parameters screen is set to y. (For an example of this field, see Figure 93: Feature-Related System Parameters screen on page 244.) The called group member can join the call in progress by pressing the lit call appearance button.
• Page 242
  1. Type add pickup-group next. Press Enter. The system displays the Pickup Group screen. The system also assigns the next available Group Number for the new pickup group (see Figure 92: Pickup Group screen page 243). 242 Administrator Guide for Avaya Communication Manager…
• Page 243
  Adding Call Pickup Figure 92: Pickup Group screen add pickup-group next Page 1 of 2 PICKUP GROUP Group Number: 11 Group Name: Accounting GROUP MEMBER ASSIGNMENTS Name (first 26 characters) Name (first 26 characters) 1: 5430892 Jane Doe 2: 5439711 Frank Smith 3: 5432783 Bonnie Franklin…
• Page 244
  Authorization Code Cancellation Symbol: # Attendant Time Out Flag? n Display Authorization Code? y Controlled Toll Restriction Replaces: none 3. Set the Call Pickup Alerting field to y. 4. Press Enter to save your changes. 244 Administrator Guide for Avaya Communication Manager…
• Page 245
  Adding Call Pickup Assigning a Call Pickup button to a user telephone After you define one or more pickup groups, assign a Call Pickup button for each extension in each pickup group. Users in a pickup group can press the assigned Call Pickup button to answer calls to any other extension in their pickup group.
• Page 246
  To get a list of all extended pickup groups: 1. Type list extended-pickup-group. Press Enter. The system displays the Extended Pickup Groups screen (see Figure 94: Extended Pickup Groups screen on page 247). 246 Administrator Guide for Avaya Communication Manager…
• Page 247
  Adding Call Pickup Figure 94: Extended Pickup Groups screen EXTENDED PICKUP GROUPS Group Number of Number Members 2. Print this screen or write down the existing Group Numbers so that you can check each extended pickup group. 3. Press Cancel. Removing a pickup group from an extended pickup group You must remove the pickup group from all extended pickup groups.
• Page 248
  2. Click Next until you see the Button Assignments area. 3. Move to the existing call-pkup button. 4. Press Clear or Delete, depending on your system. 5. Press Enter to save your changes. 248 Administrator Guide for Avaya Communication Manager…
• Page 249
  Adding Call Pickup Setting up simple extended pickup groups What if you want to have members in one pickup group be able to answer calls for another pickup group? In our example, what if you want members in the Credit Services pickup group 13 to answer calls in the Delinquency Payments pickup group 14? You can do that by setting up extended pickup groups.
• Page 250
  In this example, type change extended-pickup-group 4. Press Enter. The system displays the Extended Pickup Group screen for extended pickup group 4 (see Figure 95: Extended Pickup Group screen on page 251). 250 Administrator Guide for Avaya Communication Manager…
• Page 251
  Adding Call Pickup Figure 95: Extended Pickup Group screen change extended-pickup-group 4 Page 1 of 1 EXTENDED PICKUP GROUP Extended Group Number: 4 Pickup Pickup Group Pickup Pickup Group Number Number Number Number _____ _____ _____ _____ _____ _____ _____ _____ _____ _____…
• Page 252
  Set up the system for flexible extended pickup groups. ● Assign a FAC so that users can answer calls. ● Add or change pickup groups, and «point» a pickup group to an extended pickup group. ● 252 Administrator Guide for Avaya Communication Manager…
• Page 253
  Adding Call Pickup Creating flexible extended pickup groups To create system-wide flexible extended pickup groups: 1. Type change system-parameters features. Press Enter. The system displays the Feature-Related System Parameters screen. 2. Click Next until you see the Extended Group Call Pickup field. 3.
• Page 254
  In this example, type change extended-pickup-group 4. Press Enter. The system displays the Extended Pickup Group screen for extended pickup group 4 (see Figure 97: Extended Pickup Group screen on page 255). 254 Administrator Guide for Avaya Communication Manager…
• Page 255
  Adding Call Pickup Figure 97: Extended Pickup Group screen change extended-pickup-group 4 Page 1 of EXTENDED PICKUP GROUP Extended Group Number: 4 Pickup Pickup Group Pickup Pickup Group Number Number Number Number _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____…
• Page 256
  Then you can change the extended pickup group from flexible to simple (see Creating simple extended pickup groups on page 249). After that step, you must re-administer all of the extended pickup groups again. 256 Administrator Guide for Avaya Communication Manager…
• Page 257
  Adding Call Pickup Setting up Directed Call Pickup If you do not want to set up pickup groups and extended pickup groups, but still want selected people to answer other telephones, use Directed Call Pickup. Before a person can use this feature, you must enable Directed Call Pickup on your system.
• Page 258
  3. Press Enter to save your changes. For more information on Class of Restriction (COR), see the «Class of Restriction» feature. 258 Administrator Guide for Avaya Communication Manager…
• Page 259
  Adding Call Pickup Assigning a Class of Restriction to a user You must assign a COR to user extensions before anyone can use Directed Call Pickup. To modify an extension to allow Directed Call Pickup: 1. Type change station n, where n is the extension that you want to change. Press Enter. The system displays the Station screen.
• Page 260
  3. Click Next until you see the Button Assignments section. 4. Move to the button number that contains dir-pkup. 5. Click Clear or Delete, depending on your system. 6. Press Enter to save your changes. 260 Administrator Guide for Avaya Communication Manager…

• Page 261: Managing Hunt Groups

  Managing Hunt Groups Managing Hunt Groups This section shows you how to set up hunt groups. This section explains how calls to a hunt group are handled, and shows you different call distribution methods. What are hunt groups? A hunt group is a group of extensions that receive calls according to the call distribution method you choose.

• Page 262
  Class of Service screen changes the COS for all your hunt groups. A COS field does not appear on the Hunt Group screen. 5. Press Next Page to find the Group Member Assignments screen. 262 Administrator Guide for Avaya Communication Manager…
• Page 263
  Managing Hunt Groups Figure 99: Group Member Assignments screen change hunt-group n Page 4 of HUNT GROUP Group Number: 4 Group Extension: 3001 Group Type: ucd Member Range Allowed: 1 — 1500 Administered Members (min/max): 1 /9 Total Administered Members: 9 GROUP MEMBER ASSIGNMENTS Name (24 characters) Name (24…
• Page 264
  The call waits in «queue.» We will tell Communication Manager that as many as 10 calls can wait in the queue, but that you want to be notified if a call waits for more than 30 seconds.
• Page 265
  Managing Hunt Groups Instructions To set up our helpline queue: 1. Type change hunt-group n, where n is the number of the hunt group to change. Press Enter. In our example, type change hunt-group 5. The system displays the Hunt Group screen.
• Page 266
  Although many TTYs can connect directly with the telephone network via analog RJ-11 jacks, Avaya recommends that agents be equipped with TTYs that include an acoustic coupler that can accommodate a standard telephone handset. One reason for this recommendation is that a large proportion of TTY users are hearing impaired, but still speak clearly.
• Page 267
  For more information on how to record an announcement, see «Announcements» in Feature Description and Implementation for Avaya Communication Manager, 555-245-205. Let us add an announcement to our internal helpline. We want the caller to hear an announcement after 20 seconds in the queue, or after approximately 4 or 5 rings.

• Page 268: Managing Vectors And Vdns

  This section references announcements, hunt groups, queues, splits, and skills, which are covered in detail in other sections of this book. You can also find information about these topics in Avaya Call Center Release Call Vectoring and Expert Agent Selection (EAS) Guide, 07-300477.

• Page 269
  Writing vectors Writing vectors is easy, but Avaya recommends that you set up and test your vectors before you use them across the system. We’ll write a vector to handle calls to our main number. It is the first vector so we’ll use number Tip: Use list vector to see a list of existing vectors.
• Page 270
  Tip: display system-parameters customer-options command to see the features that are turned on for your Communication Manager server. 3. Type your vector steps in the numbered column on the left of the screen. 270 Administrator Guide for Avaya Communication Manager…
• Page 271
  Press Tab. This makes it very easy to type in your vector steps. Now that vector 1 is set up, we will add a vector step to it to tell Communication Manager how to handle the calls to our main number.

• Page 272: Playing An Announcement

  This way, if for some reason the call does not queue the first time, Communication Manager can attempt to queue the call again. If the call successfully queued the first time though, it merely skips the queue-to step and plays the announcement.

• Page 273
  10 ____________ 11 ____________ If the goto command in step 5 fails, Communication Manager goes to the next step. The stop in step 6 prevents callers from incorrectly hearing the «office is closed» announcement in step 7. Stop keeps the call in the state it was in before the command failed. In this case, if step 5 fails, the call remains in step 4 and the caller continues to hear music.
• Page 274
  «Today is a holiday, please call back tomorrow.» In our example, we recorded the mailbox greeting for extension 2001. 2. Insert the following bold steps (steps 1, 10, and 11). Inserting a step on page 276 for more information. 274 Administrator Guide for Avaya Communication Manager…
• Page 275
  You can give your callers a list of options when they call. Your vector tells Communication Manager to play an announcement that contains the choices. Communication Manager collects the digits the caller dials in response to the announcement and routes the call accordingly.

• Page 276: Inserting A Step

  When you insert a new vector step, the system automatically renumbers the rest Tip: of the vector steps and all references to the vector steps. Communication Manager inserts a «*» when the numbering needs more attention. 276 Administrator Guide for Avaya Communication Manager…

• Page 277: Deleting A Step

  In either case, an administered variable can be reused in many vectors. For a more detailed description of variable types and purposes, see Avaya Call Center Release Call Vectoring and Expert Agent Selection (EAS) Guide, 07-300477.

• Page 278
  Length — length of the digit string ● Start — digit start position ● Assignment — pre-assigned value ● VAC — Variable Access Code (for value variable type only) ● 4. Press Enter to save your changes. 278 Administrator Guide for Avaya Communication Manager…
• Page 279
  Note: the Screen Reference chapter. For a more detailed description and examples of vectors and vector variables, see Avaya Call Center Release Call Vectoring and Expert Agent Selection (EAS) Guide, 07-300477. Handling TTY calls with vectors Unlike fax machines and computer modems, a Tele-typewriter device (TTY) has no handshake tone and no carrier tone.
• Page 280
  Communication Manager, 555-245-207 for more information on the circuit pack. Fixing vector problems If there is a problem with a vector, Communication Manager records the error as a vector event. Vector events occur for a number of reasons including problems with a trunk, full queue slots, or the vector reaching the maximum 1000 steps allowed.
• Page 281
  Managing Vectors and VDNs 3. Press Enter to view the report. The system displays the Event Report (detail) screen. Figure 111: Event Report screen EVENT REPORT Event Event Event Event First Last Event Type Description Data 1 Data 2 Occur Occur Call not queued 12/5…
• Page 282
  Vector fraud is one of the most common types of toll fraud because vectors route SECURITY ALERT: calls based on the class of restriction (COR) assigned to the VDN. See the Avaya Toll Fraud and Security Handbook, 555-025-600 for more information.
• Page 283
  Managing Vectors and VDNs 2. Type a description for this VDN in the Name field. In our example, type Sales Department. The information in the VDN Name field appears on a display telephone. This allows the agent to recognize the nature of the call and respond accordingly. Tip: The VDN Override on the Vector Directory Number…

• Page 284: Understanding Automatic Call Distribution

  ACD systems can also be more powerful because they allow you to use features and products that are not available in non-ACD systems. See the Avaya Call Center Release Automatic Call Distribution (ACD) Guide, 07-300478, for more information on ACD call centers.

• Page 285: Assigning A Terminating Extension Group

  Assigning a Terminating Extension Group Assigning a Terminating Extension Group A Terminating Extension Group (TEG) allows an incoming call to ring as many as 4 telephones at one time. Any user in the group can answer the call. Once a member of the TEG has answered a group call, the TEG is considered busy. If a second call is directed to the group, it follows a coverage path if one has been assigned.

• Page 286
  Handling Incoming Calls 286 Administrator Guide for Avaya Communication Manager…

• Page 287: Chapter 8: Routing Outgoing Calls

  The FAC for AAR is usually the digit 8. The FAC for ARS is usually the digit 9 in the US and 0 outside of the US. Your Avaya technician or business partner sets up AAR on your server running Communication Manager and usually assigns the AAR FAC at the same time. You can administer your own ARS FAC.

• Page 288: Managing Calling Privileges

  3. To change from FRL 0 to FRL 7, type change cor 7. Press Enter. Class of Restriction screen appears. 4. In the FRL field, type 7. Press Enter to save your changes. Now all users with COR 7 will have the highest level of calling permissions. 288 Administrator Guide for Avaya Communication Manager…

• Page 289: Assigning Ars Fac

  Assigning ARS FAC Assigning ARS FAC Be sure the ARS feature access code (FAC) is set up on your system. In the U.S., 9 is usually the ARS FAC. Users dial 9 to make an outgoing call. When a user dials 9 to access ARS and make an outgoing call, the ARS access code 9 is dropped before digit analysis takes place.

• Page 290: Displaying Ars Analysis Information

  1. Type display ars analysis 1. Press Enter. The ARS Digit Analysis Table for dialed strings that begin with 1 appears. Note that Communication Manager displays only as many dialed strings as can fit on one screen at a time.

• Page 291
  In this example, the dialed string matches the ‘1’. Then Communication Manager matches the length of the entire dialed string (11 digits) to the minimum and maximum length columns. In our example, the 11-digit call that started with 1 follows route pattern 30 as an fnpa call.
• Page 292
  Digits can be inserted or deleted from the dialed number. For instance, you can tell Communication Manager to delete a 1 and an area code on calls to one of your locations, and avoid long-distance charges by routing the call over your private network.
• Page 293
  2 of 2 Defining operator assisted calls Here is an example of how Communication Manager routes an ARS call that begins with 0 and requires operator assistance. The user dials 9 to access ARS, then a 0, then the rest of the number.
• Page 294
  NJ. A user dials 9 0 908 956 1234. ● Communication Manager drops the ARS FAC (9 in our example), looks at the ARS Digit ● Analysis Table for 0, and analyzes the number. Then it:…
• Page 295
  This table shows 5 translations for IXC calls. When you use x in the Dialed String field, Communication Manager recognizes x as a wildcard. The x represents any digit, 0 — 9. If I dial 1010, the next 3 digits will always match the x wild cards in the dialed string.
• Page 296
  A user dials 9 120 plus 8 digits (the first of the 8 digits is not 0). ● Communication Manager drops the ARS FAC (9 in our example), looks at the ARS Digit ● Analysis Table for 120, and analyzes the number. It determines the call is long-distance and sends the call over route pattern 4.
• Page 297
  You can use wild cards to help separate out calls to certain numbers. Remember, when you use the wild card x in the Dialed String field, Communication Manager recognizes x as any digit, 0 — 9. For example, you can restrict users from making calls to a 555 information operator where you might incur charges.
• Page 298
  Routing Outgoing Calls Defining local information calls You can set up Communication Manager to allow calls to local information, or in this example, 411. Instructions To allow 411 service calls: 1. Type change ars analysis 4. Press Enter. The ARS Digit Analysis Table screen beginning with 4 appears.

• Page 299: Setting Up Multiple Locations

  Ensure that the Multiple Locations field on the System-Parameters Customer-Options screen is set to y. If this field is set to n, contact your Avaya representative for more information. If you are setting up locations across international borders, you must ensure that the…

• Page 300
  8. Type -01:00 in the TimeZone Offset field in the Number 2 row. In our example, subtract one hour from the system clock in Chicago to provide the correct time for the location in New York. 300 Administrator Guide for Avaya Communication Manager…

• Page 301: Routing With Multiple Locations

  System-Parameters Customer-Options screen is set to y. If this field is set to n, contact your Avaya representative for more information. AAR or ARS must be administered. For AAR, verify that either the Private Networking field or the Uniform Dialing Plan field ●…

• Page 302
  IP network regions, used by IP stations and IP trunks ● Instructions For example, we will use ARS to set up local call routing for two Communication Manager server locations. Our Chicago server is assigned to location 1, and our New York server is assigned to location 2.
• Page 303
  5. Type in the local HNPA and service call routing information for New York. 6. Press Enter to save your changes. Related topics See «Automatic Routing» in Feature Description and Implementation for Avaya Communication Manager, 555-245-205, for more information on ARS. AAR and ARS Digit Analysis Table…

• Page 304: Modifying Call Routing

  To add this non-local area code: 1. Type list ars route-chosen 14152223333. Press Enter. You can use any 7-digit number after 1 and the old area code (415). We used 222-3333. The ARS Route Chosen Report screen appears. 304 Administrator Guide for Avaya Communication Manager…

• Page 305
  Modifying Call Routing Figure 123: ARS Route Chosen Report screen ARS ROUTE CHOSEN REPORT Location: 1 Partitioned Group Number: Dialed Total Route Call Node Location String Pattern Type Number fnpa 2. Write down the Total Min, Total Max, Route Pattern, and Call Type values from this screen.
• Page 306
  To prevent toll fraud, deny calls to countries where you do not do business. The SECURITY ALERT: following countries are currently concerns for fraudulent calling. country code country code Colombia Pakistan Ivory Coast Peru Mali Senegal Nigeria Yemen 306 Administrator Guide for Avaya Communication Manager…

• Page 307: Overriding Call Restrictions

  Overriding Call Restrictions Instructions To prevent callers from placing calls to Colombia (57): 1. Type change ars analysis 01157. Press Enter. Enter 011 (international access) and the country code (57). The ARS Digit Analysis Table screen appears. 2. Move to a blank Dialed String field. If the dialed string is already defined in your system, the cursor appears in the appropriate Dialed String field.

• Page 308
  _______ __ _______ __ _______ __ _______ __ _______ __ _______ __ _______ __ _______ __ _______ __ _______ __ _______ __ _______ __ _______ __ _______ __ _______ __ _______ __ _______ __ 308 Administrator Guide for Avaya Communication Manager…

• Page 309: Defining Ars Partitions

  ARS partitioning allows you to provide different call routing for a group of users or for specific telephones. Note: If you used partitioning on a prior release of Avaya Communication Manager and Note: you want to continue to use partitioning, please read this section carefully. In this release of Avaya Communication Manager, partition groups are defined on the Partition Route Table.

• Page 310
  3. Press Cancel to return to the command prompt. 4. Type change partition-route-table index 1. Press Enter. Partition Routing Table screen appears. In our example, partition group 1 can make 1800 calls and these calls use route pattern 30. 310 Administrator Guide for Avaya Communication Manager…
• Page 311
  Defining ARS Partitions Figure 127: Partition Routing Table screen change partition route-table Page 1 of X Partition Routing Table Routing Patterns Route Index PGN 1 PGN 2 PGN 3 PGN 4 PGN 5 PGN 6 PGN 7 PGN 8 —— —— —— ——…
• Page 312
  4. Type a name for this COR in the COR Description field. In our example, type lobby. 5. Enter 2 in the Partition Group Number field. 6. Press Enter to save your changes. 312 Administrator Guide for Avaya Communication Manager…

• Page 313: Setting Up Time Of Day Routing

  Before you start AAR or ARS must be administered on Communication Manager before you use Time of Day Routing. For AAR, verify that either the Private Networking field or the Uniform Dialing Plan field ●…

• Page 314
  4. Press Enter to save your changes. Now assign your new Time of Day Routing Plan 2 to the COR assigned to your executives. See Class of Restriction on page 809 to see where to assign this field. 314 Administrator Guide for Avaya Communication Manager…
• Page 315
  Setting up Time of Day Routing Example For this example, assume the following: Jim is the user at extension 1234. ● Extension 1234 is assigned a COR of 2. ● COR 2 is assigned a Time of Day Plan Number of 1. ●…

• Page 316: Location By Region

  ____ ____ __ ____ _______ 2. On line 11, in the Name field, enter the Communication Manager server associated with the location (for instance, Germany). 3. In the first Timezone Offset field, enter + to indicate the time is ahead of the system time.

• Page 317
  Location by Region Figure 132: IP Address Mapping screen change ip-network-map Page 1 of X IP ADDRESS MAPPING Emergency Subnet 802.1Q Location FROM IP Address (TO IP Address or Mask) Region VLAN Extension 1.__2.__3.__0 1.__2.__3.255 ___3 ________ 1.__2.__4.__4 1.__2.__4.__4 ___0 ________ 1.__2.__4.__5 1.__2.__4.__5…
• Page 318
  15. In the Location field, enter the number from the Locations screen. In this example, it was 16. Press Next Page until you get to page 3, the Inter Network Region Connection Management screen. 318 Administrator Guide for Avaya Communication Manager…
• Page 319
  Network Region 3 (Germany) is connected to Network Region 1 (New York) using Codec Set 1. 18. Press Enter to save your changes. Related Topics See Feature Description and Implementation for Avaya Communication Manager, 555-245-205, for more information on the Multiple Locations feature. Issue 2.1 May 2006…
• Page 320
  Routing Outgoing Calls 320 Administrator Guide for Avaya Communication Manager…

• Page 321: Chapter 9: Managing Multimedia Calling

  Multimedia Applications Server Interface The Multimedia Applications Server Interface (MASI) defines a protocol and a set of operations that are used to extend Avaya Communication Manager feature functionality to a Multimedia Communications Exchange (MMCX) system. MASI architecture fits the client/server model, where Avaya Communication Manager functions as a server for MMCX clients.

• Page 322
  MMCX trunking — By assigning trunk access codes to interfaces from the MMCX to other ● MMCXs or the PSTN, Avaya Communication Manager can monitor traffic over those interfaces. Before you start CAUTION:…
• Page 323
  Interserver — Connections between MMCX terminals on different MMCX servers/nodes. ● MASI domain — A MASI domain consists of Avaya Communication Manager and one or ● more MASI nodes that share the same dial plan. That is, the extension numbers on the MMCX are known to Communication Manager, and fit in the Communication Manager dial plan.
• Page 324
  It might help you if you have already determined trunk group and signaling group numbers, unused extensions, and so on. The following are things you need to consider: Establish the dial plan on the MMCX to agree with that of Avaya Communication Manager. ●…
• Page 325
  Trunk 1 — This is any type of trunk connection to the public network. ● Trunk 2 — This is the link between the Avaya Communication Manager solution and the ● MMCX, and requires a TN464C or later DS1 circuit pack. You administer this link as an ISDN-PRI trunk group, a MASI path and an NCA-TSC.
• Page 326
  Managing MultiMedia Calling Figure 136: MASI domain of Avaya Communication Manager running on one DEFINITY Server and two (or more) MMCXs PSTN MMCX Trunk 1 Trunk 3 DEFINITY AUDIX PSTN DEFINITY Trunk 2 MMCX cydfdda2 LJK 071597 326 Administrator Guide for Avaya Communication Manager…
• Page 327
  Multimedia Applications Server Interface Figure 137: Two separate MASI domains DEFINITY AUDIX DEFINITY Trunk 3 MMCX Trunk 4 PSTN PSTN Trunk 1 DEFINITY AUDIX Trunk 2 MMCX DEFINITY cydfdda3 LJK 071897 Issue 2.1 May 2006…
• Page 328
  DEFINITY cydfdda4 LJK 071897 The MASI node must be directly connected to the Avaya DEFINITY Server for MASI features to work. In this configuration, terminals that belong to MMCX 2 (E3 and E4) do not take advantage of MASI capabilities.
• Page 329
  Ensure that on the Maintenance-Related System Parameters screen, the Packet Bus Activated field is y. Using the set options command (Avaya init or inads logins only), set MASI alarming options. For more information, see Maintenance Procedures for Avaya Communication Manager, Media Gateways and Servers, 03-300432.
• Page 330
  Virtual Path Identifier: 0 Virtual Channel Identifier: 0 Signaling Mode: isdn-pri Circuit Type: T1 Idle Code: 11111111 Connect: network Interface Companding: mulaw Country Protocol: 1 Protocol Version: d DCP/Analog Bearer Capability: Interworking Message: 330 Administrator Guide for Avaya Communication Manager…
• Page 331
  Multimedia Applications Server Interface For each link, establish a Non-Call Associated Temporary Signaling Connection (NCA-TSC) with the following attributes: Associated Signaling — MASI requires Facility Associated Signaling, so this field must be ● set to y. Primary D-channel — Enter a 6- to 7-character port number associated with the DS1 ●…
• Page 332
  Enabled — Enter y to enable the administered NCA-TSC. You might want to wait to enable ● this link until all other administration is in place. If this is y, Avaya Communication Manager attempts to establish the connection as soon as you submit the form. This might cause your system to alarm, if other administration is not finished.
• Page 333
  Multimedia Applications Server Interface Local Ext. — Avaya Communication Manager extension associated with the TSC ● Enabled — Indicates the state of the connection — enabled (y/n) ● Established — Value of established flag (as-needed/permanent) ● Dest. Digits — The MMCX extension that indicates the TSC destination ●…
• Page 334
  (signaling group, masi trunk group, and masi terminal screens). Trunk Group — This is the trunk group number in Communication Manager for the ● ISDN-PRI trunk that will be used to establish call paths.
• Page 335
  Multimedia Applications Server Interface PRI trunks from MMCX to Avaya Communication Manager that are used for purposes ● other than MASI LAN interfaces linking MMCX servers ● Use the command add masi trunk-group xxx (or ‘next’) to access the MASI Trunk Group screen.
• Page 336
  Manager dial plan, and for the add command, the extension must not already be in use.The extension of the MASI terminal must match the number of the MASI terminal. Avaya Communication Manager users dial the MASI Terminal Extension to reach MMCX users. Note:…
• Page 337
  Name — The name associated with the terminal. This can be any alphanumeric string up ● to 27 characters. Send Display Info — Indicates whether Avaya Communication Manager should forward ● display information associated with a call. Set to y.
• Page 338
  MASI terminals. CDR Privacy — Indicates whether CDR Privacy is supported for this terminal. See «Call ● Detail Recording» in Feature Description and Implementation for Avaya Communication Manager, 555-245-205 for more information. Figure 148: MASI Terminal screen — page 3…
• Page 339
  Listing MASI terminals To view a list of all the MASI terminals administered on a server, use the command list masi terminals.This command only lists terminals within the domain of the Avaya DEFINITY Server from whose SAT you issue the command.
• Page 340
  This command displays the extension number and type (attendant, masi-terminal, etc.), as well as other information about the extension. Figure 152: List extension type EXTENSION TYPE Cv1/ Type Name —- —- —- 1234 masi-terminal 4077 term-masi-path-call 340 Administrator Guide for Avaya Communication Manager…
• Page 341
  Step 10 — Administer features AAR/ARS 1. AAR/ARS is an optional feature on Avaya Communication Manager, and you need to purchase this option to use it with MMCX. To verify that this feature is enabled, use the command display system-parameters customer-options. If it is not enabled, contact your Avaya representative.

• Page 342: Call Detail Recording

  Managing MultiMedia Calling Step 11 — Verify administration You should make test calls from Avaya Communication Manager to MMCX, to ensure that you can indeed place and receive calls. Call an unattended MASI terminal. Verify that the call goes to AUDIX. Retrieve the call from the MASI terminal.

• Page 343
  Call redirection / Voice-messaging access MMCX users can enter an Avaya Communication Manager extension, including an AUDIX hunt group, Callmaster agent, attendant console or telephone as their coverage point. If AUDIX is established as the MASI terminal’s coverage point, the MASI terminal receives message waiting indication, and dials the AUDIX hunt group extension to retrieve messages.
• Page 344
  If an MMCX user initiates a conference that involves Communication Manager stations, the conference will drop when the initiator drops from the call. If a Communication Manager station initiates the conference, that station can drop without affecting the other conferees.
• Page 345
  MMCX trunks are not monitored by ASAI. It might be possible for a MASI terminal to place a call to a Communication Manager station that is part of an ASAI domain. ASAI will not be blocked from controlling this call, but there can be unpredictable results. The same is true for calls originating from an ASAI domain terminating at MASI terminals, and for ASAI-monitored hunt groups that contain MASI terminals.

• Page 346: Attendant Features

  Pull transfer — MASI terminals cannot perform a pull transfer operation. You must not ● administer this feature on an Avaya DEFINITY Server where MASI is active. This applies only in Italy. Station Hunting — You must not administer a MASI terminal as part of a station hunting ●…

• Page 347
  ● can only retrieve these calls from a Communication Manager station, since MASI terminals cannot dial the Answer Back FAC. Data Call Setup — Avaya Communication Manager users cannot place data calls to MASI ● terminals. Facility Busy Indication — You can use FBI to track the status of MASI terminals. The FBI ●…

• Page 348: Hospitality Features

  Managing MultiMedia Calling Music on Hold — Music on hold will only be available if an Avaya Communication Manager ● station has placed the call on hold. Override — Executive override does not work towards MASI terminals. ● Priority Calling — Priority calling is not supported for calls to or from MASI terminals.

• Page 349: Multimedia Call Handling

  <group number> to force a server heartbeat test, or simply wait 5 to 10 minutes for the link to recover. This situation might occur if the server running Communication Manager is rebooted or if the MASI interface is administered before the MMCX is properly administered.

• Page 350
  PC and, if unanswered, will next alert at the voice station. A Basic multimedia complex provides a loose integration of the voice station and H.320 DVC system. 350 Administrator Guide for Avaya Communication Manager…
• Page 351
  H.320 DVC system. Multimedia endpoint The multimedia endpoint is a user’s PC that has been equipped with an H.320 multimedia package. The PC is physically connected to Avaya Communication Manager with a BRI line. Figure 154: Enhanced MMCH service link DEFINITY…
• Page 352
  Managing MultiMedia Calling Feature Description MMCH’s two levels of functionality for a multimedia complex, Basic and Enhanced mode, are enabled either by administration on Communication Manager or by an mm-basic feature button or FAC. Basic Mode Operation In Basic Mode: All voice-only calls originate at the voice station.
• Page 353
  ● A non-BRI-connected multifunction telephone set. ● The PC and the multifunction telephone are individually wired to the Avaya DEFINITY Server. These two pieces of equipment can be administratively associated to form a Basic or ENHANCED multimedia complex MMCH works with any H.320 system that is fully H.320 compliant and operates at the 2B or 128K rate.
• Page 354
  The MMI and VC circuit packs are resource circuit packs akin to the Tone Detector circuit ● packs. These circuit packs require no administration on Communication Manager and can be ● located in multiple port networks. T.120 Data Collaboration Server The Extended Services Module (ESM) provides T.120 data collaboration capability on a MMCH…
• Page 355
  Typical Multimedia Call handling ESM Connections page 355 to connect to the ESM equipment: 1. Install the TN2207 primary rate interface (PRI) circuit pack and the TN787 multimedia interface (MMI) circuit pack in the port carrier of the server for Avaya Communication Manager. Note:…

• Page 356: Planning The System

  Planning for MMCH The following are some of the tasks you perform in planning and administering MMCH. Planning the system Questions to help you use Avaya Communication Manager for multimedia are: How many MMCH users are you going to have? ●…

• Page 357
  Multimedia Call Handling 12. Administer early answer and H.320 flag for stations, the early answer flag for hunt groups, and the multimedia flag for vectors as appropriate. 13. Train end users. 14. Monitor traffic and performance. Related screens System-Parameters Customer-Options ●…
• Page 358
  DS1 Circuit Pack (ESM Only) ● — Bit Rate=2.048. — Line Coding=hdb3. — Signaling Mode=isdn-pri. — Connect=pbx. — Interface=network. — Country Protocol=1. — CRC=y. — MMI Cabling Board. Signaling group (ESM Only) ● — Primary D-Channel. 358 Administrator Guide for Avaya Communication Manager…
• Page 359
  System-Parameters Customer-Options screen Ensure that the Multimedia Call Handling (Basic) field is y. This feature is provided via license file. To enable this feature, contact your Avaya representative. Feature-Related System Parameters screen The default bandwidth for MMCH calls is defined on the System-Parameters Features screen.
• Page 360
  Multimedia — This field appears on the Data Module screen only if MM is set to y on the ● System-Parameters Customer Options screen. Enter y to enable this data module to be multimedia compliant. 360 Administrator Guide for Avaya Communication Manager…
• Page 361
  Multimedia Call Handling MM Complex Voice Ext: (display only) — This field contains the number of the associated ● telephone in the complex. This is a display-only field, and is blank until you enter the data module extension in the Station screen MM Complex Data Ext field. Once you have done that, these two extensions are associated as two parts of a multimedia complex.
• Page 362
  Avaya DEFINITY Server and the PC. Thus, voice and multimedia calls are originated and received at the telephone set. Voice and multimedia call status are also displayed at the telephone set.
• Page 363
  Multimedia Call Handling The station can then answer by going off-hook and will have immediate audio path. No hourglass tone will be heard by the answering party (see Hourglass Tone on page 372). Example: An administrative assistant who does not have a multimedia PC, but might get multimedia mode calls from forwarding or coverage, might want to set the H.320 flag to y and the early answer flag to y on their voice station.
• Page 364
  — Pressing the mm-datacnf button from any voice station that is participating ● in a multimedia call will light the status lamp and alert the Avaya DEFINITY Server that you want to enable T.120 data collaboration with the other parties on the call. The button status lamp will also light for other participants in the multimedia call who have mm-datacnf buttons.
• Page 365
  Multimedia Call Handling mm-multinbr — The mm-multinbr call button is similar to the mm-call button. It allows ● origination of a multimedia call from any voice station. It is used when the destination being dialed requires a different address for each of the 2 B-channels. An example of this is Central Office provided ISDN-BRI.
• Page 366
  20. The Max Number of CA TSC default is 0. 21. Trunk Group for NCA TSC ____ (leave blank). 22. Trunk Group for Channel Selection____ (leave blank). 23. Logoff the terminal and then log back on the terminal to view your changes. 366 Administrator Guide for Avaya Communication Manager…

• Page 367: Understanding The Multimedia Complex

  If the incoming call is a voice call, Avaya Communication Manager directs it to the telephone. If the incoming call is 56K or 64K data call, Avaya Communication Manager recognizes it as such and sends it to the multimedia endpoint.

• Page 368
  2B call. The section below on the mm-multinbr button/FAC provides information on originating a 2B call where the destination has a different address for each B-channel. 368 Administrator Guide for Avaya Communication Manager…
• Page 369
  Understanding the Multimedia Complex Note: The mm-call feature button is generally used by stations that are part of an Note: Enhanced multimedia complex, but can be used by any station to originate a multimedia call. 3. Multimedia Call feature access code. For stations that do not have an administered mm-call button, the Multimedia call feature access code can be used instead.
• Page 370
  FAC. The user now dials one or two sets of destination address digits. The destination address can be provided by dialing digits, using abbreviated dial entries, last number dialed, etc. 370 Administrator Guide for Avaya Communication Manager…
• Page 371
  Understanding the Multimedia Complex Note: The mm-parameter selection FAC is generally used by stations that are part of an Note: Enhanced multimedia complex, but can be used by any station to originate a dual address multimedia call. 7. Dialing sequences that include TACs, AAR, ARS, Authorization codes, CDR account codes, FRLs 1.
• Page 372
  The combination of special ringback followed by incoming call tone is referred to as «hourglass tone.» Hourglass tone is an indication to the answering party that they should wait for the H.320 call to establish audio. 372 Administrator Guide for Avaya Communication Manager…

• Page 373: Administered Connections

  Calls originated from the PC use the COR/COS of the voice station. Adjunct Switch Applications Interface ASAI is not expected to support call-association for data calls. Therefore Avaya does not recommend that you use ASAI for multimedia.

• Page 374: Bridged Appearances

  Call redirection Calls directed to either member of the Basic multimedia complex are subject to redirection (coverage, forwarding). Avaya Communication Manager converts calls to voice before sending them to coverage. Calls redirected through call forwarding maintain multimedia status if forwarded from the data endpoint.

• Page 375
  Understanding the Multimedia Complex 2. At the appointed time, the conference controller calls his or her telephone from the multimedia endpoint by dialing the 1-number extension. Once this call is established, the controller conferences in other calls as if this were a voice conference. The controller continues to add conferees in this manner until all conferees have joined, or until the number of conferees reaches the administered limit.
• Page 376
  T.120 Data conferencing is made possible through the Extended Services Module (ESM) server, which is an adjunct to Avaya Communication Manager. Up to six parties can participate in a single data conference, and up to 24 parties can use the ESM facilities for data collaboration at any given time.
• Page 377
  When all parties involved in data collaboration conference are located on the same physical Avaya DEFINITY Server or media server, there is no restriction on the type of user. The parties can be any combination of Enhanced multimedia complexes, Basic multimedia complexes, or stand-alone H.320 DVC systems.

• Page 378: Call Park

  The PC multimedia software will probably respond with a message that the call Note: failed, since it does not recognize the FAC. In fact, Avaya Communication Manager does receive the message, and forwards all multimedia calls addressed to the 1-number.

• Page 379: Data Call Setup

  Understanding the Multimedia Complex COR/COS The Class of Restriction and Class of Service for H.320 calls originated from a 1-number complex are the same as those of the telephone in the complex. Data Call Setup Basic complex multimedia endpoints are BRI data endpoints, and can use data call-setup procedures as provided by the software vendor.

• Page 380
  Basic mode complex data extensions or stand-alone data extensions can be used to create simple data hunt groups. Data extensions are not allowed in ACD hunt groups. Avaya recommends that you do not mix voice and data stations in a hunt group.
• Page 381
  If multimedia calls into a hunt group have no ANI information, Communication Manager will never associate pairs of calls and all calls will be treated independently and routed to separate agents. This is not a recommended configuration.

• Page 382: Malicious Call Trace

  Incoming Basic mode data calls follow established night-service processing for data calls. Remote Access Communication Manager does not prevent Basic multimedia complexes from attempting to use remote access. However, these Basic mode endpoints will most likely not be able to dial the necessary codes.

• Page 383: Enhanced Mode Mm Complex

  The number can be the voice station extension or the data module extension. If the incoming call is a voice call, Avaya Communication Manager alerts the station of an incoming voice call. If the incoming call is 56K…

• Page 384
  When the destination answers the call, the originating station’s H.320 desktop video system will be alerted (that is, called by Communication Manager to establish the service link). If the H.320 DVC is not configured for auto-answer, the user must answer the H.320 calls via the DVC GUI.
• Page 385
  Enhanced Mode MM Complex Originating voice calls Voice calls are originated from the voice station of an Enhanced mode complex in the normal manner as for any voice station. Originating multimedia calls Multimedia calls from an Enhanced multimedia complex are originated from the VOICE STATION, NOT the H.320 desktop video system.
• Page 386
  The user now dials the first destination address digits. The destination address can be provided by dialing digits, using abbreviated dial entries, last number dialed, etc. The system will provide dialtone after the first address has been completed. The user now dials 386 Administrator Guide for Avaya Communication Manager…
• Page 387
  Enhanced Mode MM Complex the second destination address digits. The destination address can be provided by dialing digits, using abbreviated dial entries, last number dialed, etc. Originating a multimedia call with the MM-multinbr FAC will originate a call according to the Default Multimedia Parameters selected on the System Parameters Features screen.
• Page 388
  The user actions required to answer voice or multimedia calls at an Enhanced multimedia complex are identical if the H.320 DVC system is configured for auto-answer. If the H.320 DVC system is not configured for auto-answer an additional step is required. See Answering multimedia calls below. 388 Administrator Guide for Avaya Communication Manager…
• Page 389
  Enhanced Mode MM Complex Note: Avaya recommends, but does not require, that Enhanced mode complexes place Note: their desktop video system into an auto-answer mode of operation. Answering voice calls Incoming voice calls will alert at the voice station of the Enhanced multimedia complex in the normal manner.
• Page 390
  The following steps create a multi-party voice/video conference: 1. Enhanced mode complex station A originates a multimedia call to, or receives a multimedia call from, party B. Station A and party B have 2-way voice and video. 390 Administrator Guide for Avaya Communication Manager…
• Page 391
  T.120 Data conferencing is made possible through the Extended Services Module (ESM) server, which is an adjunct to the Avaya DEFINITY Server. Up to six parties can participate in a single data conference, and up to 24 parties can use ESM facilities for data collaboration at any given time.
• Page 392
  Note: collaboration session and retaining voice/video. Some H.320 DVC systems drop the entire call. Avaya recommends that once T.120 data sharing has been enabled for a conference, that it remain active for the duration of the conference call. When all endpoints have dropped from the call, the T.120 resources will be released.
• Page 393
  When all parties involved in data collaboration conference are located on the same physical Avaya DEFINITY Server or media server, there is no restriction on the type of user. The parties can be any combination of Enhanced multimedia complexes, Basic multimedia complexes or stand-alone H.320 DVC systems.
• Page 394
  If a plain voice station or a Basic mode complex is the covering party, the answering voice station will receive audio only. If all voice stations in the coverage path have the Station screen 394 Administrator Guide for Avaya Communication Manager…
• Page 395
  Enhanced Mode MM Complex Early Answer field set to n and the originator of the multimedia call was not a local Enhanced mode complex, the answering station will hear hourglass tone. If an Enhanced mode complex is the covering party, the answering voice station will receive voice and video.
• Page 396
  If multimedia calls into a hunt group have no ANI information, Communication Manager will never associate pairs of calls and all calls will be treated independently and routed to separate agents. This is not a recommended configuration.

• Page 397: Call Forwarding

  Enhanced Mode MM Complex Administered Connections An Enhanced multimedia complex voice station can serve as the origination point or destination of an administered connection. If the Multimedia call feature access code is included in the administration of the administered connection, this will result in a video AC. An Enhanced multimedia complex H.320 DVC system cannot serve as the origination point of an administered connection.

• Page 398
  Data trunk groups can be used to carry H.320 calls of a fixed (administered) bearer capability. ISDN Trunk Groups Avaya highly recommends that you use ISDN trunks for multimedia calls. ISDN PRI trunks allow complete 1-number access for an Enhanced multimedia complex. ANI provided over PRI trunks allows correct routing of multiple bearer channels to the correct destination device.
• Page 399
  Enhanced Mode MM Complex Station Hunting Multimedia calls to Enhanced mode complex voice stations that have an extension administered in the hunt-to-station field hunt based on established hunting criteria. If the hunt-to-station is also an Enhanced mode complex station, a multimedia call will result when the call is answered.
• Page 400
  Managing MultiMedia Calling Monitoring MMCH This section briefly discusses some of the commands you can use to monitor multimedia complexes and conferences. The Maintenance manual for your Avaya server might discuss some of these commands and their output in more detail. Action…
• Page 401
  Enhanced Mode MM Complex Figure 160: General Status screen status station nnnn GENERAL STATUS Type: 7405D Service State: in-service/on-hook Extension: 1002 Maintenance Busy? no Port: 01C0702 SAC Activated? no Call Parked? no User Cntrl Restr: none Ring Cut Off Act? no Group Cntrl Restr: none Active Coverage Option: 1 CF Destination Ext:…
• Page 402
  Also note that there is a limit to the total number of conversion calls the system can handle simultaneously. If you experience traffic problems after installing multimedia, you might want to reduce the number of stations that use H.320 conversion. 402 Administrator Guide for Avaya Communication Manager…

• Page 403: Chapter 10: Setting Up Telecommuting

  Configuring Avaya Communication Manager for Telecommuting Telecommuting emphasizes the ability to perform telephony activities while remote from Avaya Communication Manager. It is a combination of four features which permit you to remotely perform changes to your station’s Coverage and Call Forwarding. Note:…

• Page 404
  Call Classifier — Detector ● 1264-TMx software ● Avaya Communication Manager extender — switching module or standalone rack mount ● (Digital Communications Protocol (DCP) or Integrated Services Digital Network (ISDN)) For more information about this equipment, see the Hardware Description and Reference for Avaya Communication Manager, 555-245-207.

• Page 405: Setting Up Personal Station Access

  Setting up Personal Station Access Figure 164: Telecommuting Access screen add telecommuting-access TELECOMMUTING ACCESS Telecommuting Access Extension: ________ 2. In the Telecommuting Access Extension field, type 1234. Press Enter. This is the extension you are configuring for telecommuting. 3. Type change system-parameters coverage. Press Enter. System Parameters Call Coverage/Call Forwarding screen appears.

• Page 406
  «da» for «don’t answer.» If the coverage point is a voice-messaging system, the messaging system receives an indication from Communication Manager that this call was not answered, and treats the call accordingly. Note:…
• Page 407
  Setting up Personal Station Access 6. Complete the following fields. Press Enter. a. Type #4 in the Personal Station Access (PSA) Associate Code field. This is the feature access code you will use to activate Personal Station Access at a telephone.

• Page 408: Creating A Station Security Code

  7 or 8. 5. Type change station 1234. Press Enter. This is the station extension you configured for telecommuting. The Station screen appears. 408 Administrator Guide for Avaya Communication Manager…

• Page 409
  1433 for information about and field descriptions on the Station screen. See «Station Security Codes» in Feature Description and Implementation for Avaya Communication Manager (555-245-205) for a description of the Station Security Codes feature. Issue 2.1 May 2006…

• Page 410: Assigning An Extender Password

  Setting Up Telecommuting Assigning an Extender Password Avaya Communication Manager allows you assign an extender password to a user. You can assign one password for each Avaya Communication Manager port. Before you start Use the Remote Extender PC in the server room to perform this procedure.

• Page 411: Setting Up Call Forwarding

  14. Type doe.fil in the File field and click OK. The system saves the User01 information. Setting up Call Forwarding Avaya Communication Manager allows you to change your call forwarding from any on-site or off-site location. Instructions In our example, we assign the feature access codes and class of service to set up call forwarding.

• Page 412
  If the FAC is dialed off site, the tenant number of the incoming trunk must have access to the tenant number of the extension administered. 412 Administrator Guide for Avaya Communication Manager…

• Page 413: Assigning Coverage Options

  Tenant Partitioning feature. Assigning Coverage Options Avaya Communication Manager allows you to assign two previously administered coverage paths and/or time of day coverage tables on the Station screen. This allow telecommuters to alternate between the two coverage paths and/or time of day coverage tables administered to better control how their telephone calls are handled.

• Page 414: Installing Home Equipment

  See Feature Description and Implementation for Avaya Communication Manager, 555-245-205, for information about the Extended User Administration of Redirected Calls feature. Installing Home Equipment Avaya Communication Manager allows you to install equipment in your home so that you can utilize system facilities from off-site. Before you start You can also set up telecommuting with an IP (internet protocol) telephone or IP Softphone.

• Page 415
  Installing Home Equipment Instructions Installing home equipment To install your home equipment: 1. Plug the telephone cord into the slot labeled line on the back of the module and into the wall jack. 2. Plug the telephone cord into the slot labeled port on the back of the module and into the slot labeled line on the telephone.

• Page 416: Setting Up Remote Access

  Setting up Remote Access Remote Access permits a caller located outside the system to access the server running Avaya Communication Manager through the public or private network and then use the features and services of the system.

• Page 417
  If you do not intend to use Remote Access now or in the future, you can permanently disable the feature. If you do decide to permanently disable the feature, it will require Avaya Services intervention to activate the feature again.
• Page 418
  This is the 7-digit barrier code you must enter to access the system’s Remote Access facilities. 7. Type 1 in the COR field. This is the class of restriction (COR) number associated with the barrier code that defines the call restriction features. 418 Administrator Guide for Avaya Communication Manager…
• Page 419
  The Remote Access screen appears. 2. Type y in the Permanently Disable field. If you permanently disable this feature, it requires Avaya Services intervention to reactivate the feature. There is a charge for reactivation of this feature. 3. Press Enter to save your work.
• Page 420
  QSIG to DCS TSC Gateway on page 1379 for information about and field descriptions on the Remote Access screen. See Feature Description and Implementation for Avaya Communication Manager, 555-245-205, for a description of the Remote Access feature. 420 Administrator Guide for Avaya Communication Manager…

• Page 421: Changing Telecommuting Settings

  Changing Telecommuting Settings Changing Telecommuting Settings Avaya Communication Manager allows you to associate and disassociate PSA, change the coverage path for your station, change the extension to which you forward your calls, and change your personal station’s security code. Before you start Configure PSA.

• Page 422
  This is the feature access code you set for activating extended call forward. You hear dial tone. 3. Dial 4321. Press #. This is the extension from which you want to forward calls. 422 Administrator Guide for Avaya Communication Manager…
• Page 423
  Changing Telecommuting Settings 4. Dial 87654321. Press #. This is the extension security code. You hear dial tone. 5. Dial 1235. This is the extension to which you want to forward calls. You hear the confirmation tone. Changing your personal station security codes In this example, we change the security code for extension 1235 from 98765432 to 12345678.
• Page 424
  Violations Notification (SVN) feature. This is true even if you attempt to interrupt the change sequence with an asterisk. Related topics See Feature Description and Implementation for Avaya Communication Manager, 555-245-205, for a description of the Security Violations Notification (SVN) feature. 424 Administrator Guide for Avaya Communication Manager…

• Page 425: Chapter 11: Enhancing System Security

  To assist in identifying unauthorized use of the system, the History report lists each time a user logs on or off the system. See the Reports for Avaya Communication Manager, 555-233-505, for more information about this report.

• Page 426: Preventing Toll Fraud

  When international access is required, establish permission groups. Limit access to only the specific destinations required for business. 7. Protect access to information stored as voice Password restrict access to voice mail mailboxes. Use non-trivial passwords and change passwords regularly. 426 Administrator Guide for Avaya Communication Manager…

• Page 427
  11. Monitor access to the dial-up maintenance port. Change the access password regularly and issue it only to authorized personnel. Consider activating Access Security Gateway. See «Access Security Gateway» in Feature Description and Implementation for Avaya Communication Manager, 555-245-205, for more information.

• Page 428: Physical Security

  2. Lock wiring closets and media server rooms. 3. Keep a log book register of technicians and visitors. 4. Shred all Communication Manager information or directories you discard. 5. Always demand verification of a technician or visitor by asking for a valid I.D. badge.

• Page 429
  Note: change remote-access command. If you do permanently disable Remote Access, the code is removed from the software. Avaya charges a fee to restore the Remote Access feature. 3. If you use Remote Access, but only for internal calls, change announcements or remote service observing.
• Page 430
  When a vector collects digits, it processes those digits back to Communication Manager and if the COR of the VDN allows it to complete the call off-net, it will do so. For example, the announcement «If you know your party’s 4-digit extension number, enter it now»…
• Page 431
  System Security Checklist 8. If loop start trunks are administered on Communication Manager and cannot be changed by the Local Exchange Company, block all class of service from forwarding calls off-net. In the Class of Service screen, Restriction Call Fwd-Off Net field, set to y for the 16 (0-15) COS numbers.
• Page 432
  Step 9 and Step 16 as a double layer of security. In the event that the voice mail system becomes unsecured or compromised for any reason, the layer of security on Avaya Communication Manager takes over, and vice versa. 17. Administer all fax machines, modems, and answering machines analog voice ports as follows: Set the Switchhook Flash field to n.

• Page 433: Adding Logins And Passwords

  Adding Logins and Passwords Adding Logins and Passwords This section shows you how to add a user and their password. To add a login, you must be a superuser with authority to administer permissions. When adding logins, remember the following: Type the new login name as part of the add command.

• Page 434
  7. In the Password Aging Cycle Length (Days) field, type 30. This requires the user to change the password every 30 days. 8. Press Enter to save your changes. Now you need to set the permissions for this new login. 434 Administrator Guide for Avaya Communication Manager…
• Page 435
  Adding Logins and Passwords 9. Type change permissions angi3. Press Enter. Command Permission Categories screen appears. Figure 168: Command Permission Categories screen change permissions nnnn Page 1 of x COMMAND PERMISSION CATEGORIES Login Name: nnnn COMMON COMMANDS Display Admin. and Maint. Data? n System Measurements? n System Mgmt Data Transfer Only? n ADMINISTRATION COMMANDS…

• Page 436: Changing A Login

  We will change the login angi3 with the password b3stm0m. We also will require the user to change their password every 30 days. To change logins: 1. Type change login angi3. Press Enter. Login Administration screen appears. 436 Administrator Guide for Avaya Communication Manager…

• Page 437
  Changing a Login Figure 170: Login Administration screen add login Page 1 of x LOGIN ADMINISTRATION Password of Login Making Change: LOGIN BEING ADMINISTERED Login’s Name:xxxxxxx Login Type: Service Level: Disable Following a Security Violation? Days to Disable After Inactivity: Access to INADS Port? LOGIN’S PASSWORD INFORMATION Login’s Password:…

• Page 438: Displaying A Login

  2. Press Enter to remove the login, or press Cancel to leave this screen without removing the login. More information When you remove a login, the Security Measurement reports do not update until the next hour. 438 Administrator Guide for Avaya Communication Manager…

• Page 439: Using Access Security Gateway

  You need an Access Security Gateway Key. On the System-Parameters Customer-Options screen, verify the Access Security Gateway field is y. If not, contact your Avaya representative. Instructions To set up access security gateway: 1. Type change login xxxx, where xxxx is the alphanumeric login ID.

• Page 440
  Be sure to remember your secret key number. 5. All other fields on page 2 are optional. 6. Press Enter to save your changes. 7. Type change system-parameters security. Press Enter. Security-Related System Parameters screen appears. 440 Administrator Guide for Avaya Communication Manager…
• Page 441
  8. In the ACCESS SECURITY GATEWAY PARAMETERS section, you determine which of the following necessary port type fields to set to y. Note: Avaya recommends that you protect the SYSAM-RMT port since it is a dial-up Note: port and therefore is more susceptible to compromise.
• Page 442
  1. Type change login xxxx. Press Enter, where xxxx is the alphanumeric login ID. Login Administration screen appears. 2. On the Access Security Gateway Login Administration page (page 2), set the Blocked field to n. 442 Administrator Guide for Avaya Communication Manager…
• Page 443
  Handling a lost ASG key If a user loses their Access Security Gateway Key: 1. Modify any logins associated with the lost Access Security Gateway Key. See your Avaya technical support representative for more information on changing your PIN. 2. If the login is no longer valid, type remove login xxxx to remove the invalid login from the system, where xxxx is the alphanumeric login ID.

• Page 444: Changing Login Permissions

  Instructions We will change the login permissions of angi3. To change login permissions: 1. Type change permissions angi3. Press Enter. Command Permission Categories screen appears. 444 Administrator Guide for Avaya Communication Manager…

• Page 445
  Changing Login Permissions Figure 175: Command Permissions Categories screen change permissions nnnn Page 1 of x COMMAND PERMISSION CATEGORIES Login Name: nnnn COMMON COMMANDS Display Admin. and Maint. Data? n System Measurements? n System Mgmt Data Transfer Only? n ADMINISTRATION COMMANDS Administer Stations? n Administer Features? n Administer Trunks? n…

• Page 446: Changing Passwords

  Notify the owner of the login to change their password immediately. The password does not appear on the screen as you type. A password must be from 4 to 11 characters in length and contain at least 1 alphabetic and 1 numeric symbol. 446 Administrator Guide for Avaya Communication Manager…

• Page 447: Using Busy Verify

  On the Trunk Group screen — page 1, verify the Dial Access field is y. If it is not, contact your Avaya technical support representative. Instructions To use busy verify: 1. Type change station xxxx, where xxxx is the station to be assigned the busy verify button.

• Page 448
  2. In the BUTTON ASSIGNMENTS area, type verify. 3. Press Enter to save your changes. 4. To activate the feature, press the Verify button on the telephone and then enter the Trunk Access Code and member number to be monitored. 448 Administrator Guide for Avaya Communication Manager…

• Page 449: Setting Up Authorization Codes

  On the System-Parameters Customer-Options screen, verify the Authorization Codes field is y. If not, contact your Avaya representative. This field turns on the feature and permits you to selectively specify levels of calling privileges that override in-place restrictions. Instructions To set up authorization codes: 1.

• Page 450
  3. In the Authorization Code Length field, type 7. This defines the length of the Authorization Codes your users need to enter. To maximize the security of your system, Avaya recommends you make each authorization code the maximum length allowed by the system.
• Page 451
  Setting up Authorization Codes 8. Type change authorization-code nnnn, where nnnn is the authorization code. Press Enter. Authorization Code — COR Mapping screen appears. Figure 180: Authorization Code — COR Mapping screen change authorization-code Page 1 of x Authorization Code — COR Mapping Note: XX codes administered.
• Page 452
  Enhancing System Security Related topics See «Class of Restiction» in Feature Description and Implementation for Avaya Communication Manager, 555-245-205, for more information on setting up dialing out restrictions. See Administration for Network Connectivity for Avaya Communication Manager, 555-233-504, for more information on using trunk access codes.

• Page 453: Setting Up Security Violations Notification

  When a security violation has occurred, there are steps that you can take to be sure that this same attempt is not successful in the future. See the Avaya Toll Fraud and Security Handbook, 555-025-600, for more information.

• Page 454
  This the time interval in which the threshold, or number of violations, must occur. 7. Press Enter to save your changes. 8. (Optional) Type change login nnnn, where nnnn is your login ID. The system displays the Login Administration screen. 454 Administrator Guide for Avaya Communication Manager…
• Page 455
  Setting up Security Violations Notification Figure 182: Login Administration screen add login Page 1 of x LOGIN ADMINISTRATION Password of Login Making Change: LOGIN BEING ADMINISTERED Login’s Name:xxxxxxx Login Type: Service Level: Disable Following a Security Violation? Days to Disable After Inactivity: Access to INADS Port? LOGIN’S PASSWORD INFORMATION Login’s Password:…
• Page 456
  This disables Remote Access following detection of a remote access security violation. 13. (Optional) Press Enter to save your changes. 14. Type change station xxxx, where xxxx is the station to be assigned the notification halt button. Press Enter. Station screen (page 3) appears. 456 Administrator Guide for Avaya Communication Manager…
• Page 457
  Setting up Security Violations Notification Figure 184: Station screen add station nnnn Page 3 of X STATION SITE DATA Room: _______ Headset? n Jack: ___ Speaker? n Cable: ___ Mounting: d Floor: _______ Cord Length: 0_ Building: _______ Set Color: _____ ABBREVIATED DIALING List1: ________ List2: _________…

• Page 458: Using Station Lock

  Using Station Lock Station Lock allows only authorized users to make external telephone calls from a particular station. Note: Avaya recommends digital telephones use a Station Lock button rather than a Note: feature access code. Setting Station Lock We will set Station Lock to allow authorized users to access the system through a particular station.

• Page 459
  Using Station Lock 10. In the Calling Party Restriction field, verify it is outward. 11. Press Enter to save your changes. Now when extension 7262 activates Station Lock, calling restrictions are determined by the Station Lock COR, COR 2. Based on the administration of COR 2, extension 7262 is not allowed to call outside the private network.

• Page 460: Dealing With Security Violations

  There might be occasions when you have to disable a login for one of your users because of a security violation. 1. Log in to Avaya Communication Manager using a login ID with the correct permissions. 2. Type disable login nnnnn, where nnnnn is the login you want to disable. Press Enter.

• Page 461: Chapter 12: Managing Trunks

  Following a process Trunking technology is complex. Following a process can prevent mistakes and save you time. To set up new trunks and trunk groups, Avaya recommends following the process below (some steps might not apply to your situation): 1. Install the necessary circuit packs and perform any administration the circuit pack requires.

• Page 462
  How many digits is your service ● provider sending? Are you inserting any digits? What are ● they? Are you absorbing any digits? How ● many? What range of numbers has your ● service provider assigned you? 462 Administrator Guide for Avaya Communication Manager…
• Page 463
  Related topics See the Hardware Description and Reference for Avaya Communication Manager, 555-245-207, for information on the types of circuit packs available and their capacities. See your server’s Installation manual for circuit-pack installation instructions.

• Page 464: Adding A Co, Fx, Or Wats Trunk Group

  3 in the following procedure. In most cases, Avaya recommends leaving the default settings in fields that aren’t specifically mentioned in the following instructions. Your Avaya representative or network service provider can give you more information.

• Page 465
  Adding a CO, FX, or WATS Trunk Group Figure 185: Trunk Group screen add trunk-group next Page 1 of TRUNK GROUP Group Number: 1 Group Type: co CDR Reports: y Group Name: OUTSIDE CALL COR: 1 TN: 1 TAC: Direction: two-way Outgoing Display? n Dial Access? n Busy Threshold: 255…
• Page 466
  11. Press Next Page until you find the Outgoing Dial Type field. 12. In the Outgoing Dial Type field, type tone. This field tells Communication Manager how digits are to be transmitted for outgoing calls. Entering tone actually allows the trunk group to support both dual-tone multifrequency (DTMF) and rotary signals, so Avaya recommends that you always put tone in this field.

• Page 467: Adding A Did Trunk Group

  Adding a DID Trunk Group Adding a DID Trunk Group In most cases, Avaya recommends leaving the default settings in fields that aren’t specifically mentioned in the following instructions. Your Avaya representative or network service provider can give you more information. For Direct Inward Dialing (DID) trunk groups, settings in the following fields must match your provider’s settings:…

• Page 468
  7. In the Incoming Dial Type field, type tone. This field tells Communication Manager how digits are transmitted for incoming calls. Entering tone actually allows the trunk group to support both DTMF and rotary signals, so Avaya recommends that you always put tone in this field.

• Page 469: Adding A Pcol Trunk Group

  Adding a PCOL Trunk Group Adding a PCOL Trunk Group In most cases, when administering Personal Central Office Line (PCOL) trunk groups, Avaya recommends leaving the default settings in fields that aren’t specifically mentioned in the following instructions. Your Avaya representative or network service provider can give you more information.

• Page 470
  5. In the Trunk Type field, type ground start. This field tells the system what kind of signaling to use on this trunk group. To prevent glare, Avaya recommends ground start signaling for most two-way CO, FX, and WATS trunk groups.
• Page 471
  8. In the Outgoing Dial Type field, type tone. This field tells Communication Manager how digits are to be transmitted for outgoing calls. Entering tone actually allows the trunk group to support both DTMF and rotary signals, so Avaya recommends that you always put tone in this field.
• Page 472
  When a user puts a call on hold on a personal CO line, the status lamp associated with the ● PCOL button does not track the busy/idle status of the line. 472 Administrator Guide for Avaya Communication Manager…

• Page 473: Adding A Tie Or Access Trunk Group

  Adding a Tie or Access Trunk Group Adding a Tie or Access Trunk Group In most cases, Avaya recommends leaving the default settings in fields that aren’t specifically mentioned in the following instructions. Your Avaya representative or network service provider can give you more information.

• Page 474
  10. Type tone in both the Outgoing Dial Type and Incoming Dial Type fields. These fields tell Communication Manager how digits are transmitted for incoming calls. Entering tone actually allows the trunk group to support both DTMF and rotary signals, so Avaya recommends that you always put tone in this field.

• Page 475: Adding A Diod Trunk Group

  DS1 circuit pack and this circuit pack must be administered separately. The example in this section shows you how to do this. In most cases, Avaya recommends leaving the default settings in fields that aren’t specifically mentioned in the following instructions. Your Avaya representative or network service provider can give you more information.

• Page 476
  Before you can administer a digital trunk group, you must have one or more circuit packs that support DS1 with enough open ports to handle the number of trunks you need to add. To find out what circuit packs you need, see the Hardware Description and Reference for Avaya Communication Manager, 555-245-207.
• Page 477
  This is the standard for T1 lines. 4. In the Line Coding field, type b8zs. Avaya recommends you use b8zs whenever your service provider supports it. Since this trunk group only carries voice traffic, you could also use ami-zcs without a problem.
• Page 478
  You can upgrade without reconfiguring external channel service units, and your service provider won’t have to reconfigure your network connection. E1 recommended settings DS1 administration for E1 service varies from country to country. See your local Avaya technical support representative for more information. Note:…
• Page 479
  Setting up Digital Trunks The following enhanced DS1 administration login permissions must be assigned on the Command Permission Categories screen: The Maintain Enhanced DS1 field must be y. ● The Maintain Trunks field must be y. ● The Maintain Switch Circuit Packs field must be y. ●…
• Page 480
  Related topics DS1 Circuit Pack on page 921 for information on administering DS1 service. See «DS1 Trunk Service» in Feature Description and Implementation for Avaya Communication Manager, 555-245-205, for detailed information on DS1 service. 480 Administrator Guide for Avaya Communication Manager…

• Page 481: Adding Trunks To A Trunk Group

  Adding Trunks to a Trunk Group Adding Trunks to a Trunk Group Use this procedure to add new trunks or to change the assignment of existing trunks. To change the assignment of existing trunks, remove them from their current trunk group and add them to the new group.

• Page 482
  7. Repeat steps 3 to 6, as appropriate, for the remaining trunks. Notice that you can assign trunks in the same trunk group to ports on different circuit packs. 8. Press Enter to save your changes. 482 Administrator Guide for Avaya Communication Manager…

• Page 483: Removing Trunk Groups

  Removing Trunk Groups Removing Trunk Groups There’s more to removing a trunk group than just executing the remove trunk-group command. If you’re using Automatic Route Selection (ARS), you must remove an outgoing or two-way trunk group from any route patterns that use it. If you’ve administered Trunk-Group Night Service buttons for the trunk group on any telephones, those buttons must be removed or assigned to another trunk group.

• Page 484: Inserting And Absorbing Digits

  2. In the Digit Treatment field, type insertion. This field tells Communication Manager to add digits to the incoming digit string. These digits are always added at the beginning of the string. 3. In the Digits field, type 6.

• Page 485: Administering Trunks For Listed Directory Numbers

  Manager will remove the first 2 digits from the digit strings delivered with incoming calls. For example, if the central office delivers the string «556-4444,» Avaya Communication Manager will change it to «64444,» an extension that fits your dial plan.

• Page 486
  When you use the Listed Directory Number screen to assign some extensions to the attendant group, or when you enter attd in the Incoming Destination field on the Trunk Group screen for CO or FX trunks, Avaya Communication Manager treats these calls as LDN calls. 486 Administrator Guide for Avaya Communication Manager…

• Page 487: Administering Answer Detection

  If your network does not supply answer supervision, you can set a timer for all calls on that group. When the timer expires, Communication Manager assumes the call has been answered and call detail recording starts (if you are using CDR).

• Page 488: Administering Isdn Trunk Groups

  Managing Trunks Related topics See «Answer Detection» in Feature Description and Implementation for Avaya Communication Manager, 555-245-205, for detailed information about this feature. Administering ISDN Trunk Groups Integrated Services Digital Network (ISDN) trunk groups support the ISDN and Call-by-Call Service Selection service selection features. The trunk group provides end-to-end digital connectivity and supports a wide range of services including voice and non-voice services, to which users have access by a limited set of CCITT-defined, standard multipurpose interfaces.

• Page 489
  Administering ISDN Trunk Groups The D-channel for ISDN-PRI interfaces switches through either the TN765 Processor ● Interface (PI) circuit pack or the TN778 Packet Control (PACCON) circuit pack. The D-channel for ISDN-BRI interfaces only switches through the TN778 Packet Control (PACCON) circuit pack.
• Page 490
  Packet Bus Maint field to y. ISDN Trunk Group — Enter information in all the fields except the trunk group members. ● When using ISDN-PRI interfaces, enter the members after you establish the signaling links. 490 Administrator Guide for Avaya Communication Manager…
• Page 491
  ● numbers 01 to 08 for a multi-carrier cabinet system or links 01 to 04 for a single-carrier cabinet system as required. When first administering this screen for ISDN in Avaya Communication Manager, do not administer the Enable field. Communication Processor Channel Assignment — Use this screen only for a TN765.
• Page 492
  PRI, or vice versa), the cursor positions on the offending member, and the following error message appears: You cannot mix BRI and PRI ports in the same trunk group. 492 Administrator Guide for Avaya Communication Manager…

• Page 493: Chapter 13: Managing Announcements

  Avaya Communication Manager documentation library. For a complete description of Announcement information and procedures, see the ● “Announcements” feature in the Feature Description and Implementation for Avaya Communication Manager, 555-245-205. For a complete description of the related Locally Sourced Announcement feature, see the ●…

• Page 494
  Administering Announcements Feature Description and Implementation for Avaya (recording, copying, deleting, etc.) Communication Manager 2 of 3 494 Administrator Guide for Avaya Communication Manager…
• Page 495
  Getting Started with the VAL or G700 Virtual VAL Task Information source Viewing announcement usage Reports for Avaya Communication Manager and measurements (list measurements Feature Description and Implementation for Avaya announcement command) Communication Manager Troubleshooting announcements Feature Description and Implementation for Avaya Communication Manager.
• Page 496
  Managing Announcements 496 Administrator Guide for Avaya Communication Manager…

• Page 497: Chapter 14: Managing Group Communications

  Use this procedure to allow users to make voice pages over an external loudspeaker system connected to Avaya Communication Manager. If you’re using an external paging system instead of an auxiliary trunk circuit pack, don’t use this procedure. External systems typically connect to a trunk or station port and are not administered through the Loudspeaker Paging screen.

• Page 498
  6. On the Zone 1 row, type Reception area in the Location field. Give each zone a descriptive name so you can easily remember the corresponding physical location. 7. Repeat steps 4 through 6 for zones 2 to 5. 498 Administrator Guide for Avaya Communication Manager…
• Page 499
  Setting up Voice Paging Over Loudspeakers 8. In the ALL row, type 310 in the Voice Paging — TAC field and 1 in the Voice Paging — COR field. By completing this row, you allow users to page all zones at once. You do not have to assign a port to this row.
• Page 500
  Paging Over Speakerphones on page 505 for another way to let users page. See Loudspeaker Paging» in Feature Description and Implementation for Avaya Communication Manager, 555-245-205, for detailed information on voice paging over loudspeakers. 500 Administrator Guide for Avaya Communication Manager…

• Page 501: Setting Up Chime Paging Over Loudspeakers

  This feature is also known as Code Calling Access. Before you start Your server running Communication Manager must have one or more auxiliary trunk circuit packs with enough available ports to support the number of paging zones you define. Each paging zone requires 1 port.

• Page 502
  8. In the ALL row, type 89 in the Code Calling — TAC field and 1 in the Code Calling — COR field. By completing this row, you allow users to page all zones at once. You do not have to assign a port to this row. 9. Press Enter to save your changes. 502 Administrator Guide for Avaya Communication Manager…
• Page 503
  Setting up Chime Paging Over Loudspeakers To assign chime codes to individual extensions: 1. Type change paging code-calling-ids. Press Enter. Code Calling IDs screen appears. Figure 193: Code Calling IDs screen change paging code-calling-ids Page 1 of x CODE CALLING IDs ID ASSIGNMENTS 111: ____ 141: ____…
• Page 504
  Related Topics Paging Over Speakerphones below for another way to let users page. See «Loudpeaker Paging» in Feature Description and Implementation for Avaya Communication Manager, 555-245-205, for detailed information on chime paging over loudspeakers. 504 Administrator Guide for Avaya Communication Manager…

• Page 505: Paging Over Speakerphones

  Paging Over Speakerphones Paging Over Speakerphones Use this procedure to allow users to make an announcement over a group of digital speakerphones. By dialing a single extension that identifies a group, users can page over all the speakerphones in that group. Speakerphone paging is one-way communication: group members hear the person placing the page but cannot respond directly.

• Page 506
  5. In the Ext field in row 1, type 2009. 6. Enter the remaining extensions that are members of this group. Communication Manager fills in the Name fields with the names from the Station screen when you save your changes.
• Page 507
  Disturb activated. order to hear a page. More information You can create up to 32 paging groups on Avaya Communication Manager. ● Each group can have up to 32 extensions in it. ● One telephone can be a member of several paging groups.

• Page 508: Paging Users Who Are On Active Calls

  Before you start Before you administer whisper paging: Your Communication Manager server must have a circuit pack that supports whisper ● paging. For information on specific models, see the Hardware Description and Reference for Avaya Communication Manager, 555-245-207.

• Page 509: Using Telephones As Intercoms

  Using Telephones as Intercoms Related topics See «Whisper Paging» in Feature Description and Implementation for Avaya Communication Manager, 555-245-205, for detailed information on whisper paging. Using Telephones as Intercoms Use this procedure to make communications quicker and easier for users who frequently call each other.

• Page 510
  Length of Dial Code field. 5. Repeat steps 3 and 4 for the remaining extensions. Dial codes don’t have to be in order. Communication Manager fills in the Name field with the name from the Station screen when you save changes.
• Page 511
  Using Telephones as Intercoms To set up automatic intercom between extensions 2010 and 2011: 1. Type change station 2010. Press Enter. Station screen (page 3) appears. Figure 196: Station screen add station nnnn Page 3 of X STATION SITE DATA Room: _______ Headset? n Jack: ___…
• Page 512
  When users are in the same call pickup group, or if Directed Call Pickup is enabled on your server running Communication Manager, one user can answer an intercom call to another user. To allow users to pick up intercom calls to other users, you must enter y in the Call Pickup on…

• Page 513: Setting Up Automatic Answer Intercom Calls

  Setting up Automatic Answer Intercom Calls Setting up Automatic Answer Intercom Calls Automatic Answer Intercom Calls (Auto Answer ICOM) allows a user to answer an intercom call within the intercom group without pressing the intercom button. Auto Answer ICOM works with digital, BRI, and hybrid telephones with built-in speaker, headphones, or adjunct speakerphone.

• Page 514
  Direct IP-IP Audio Connections? n Emergency Location Ext: 75001 Always use? n IP Audio Hairpinning? n Precedence Call Waiting? y 2. Move to the Auto Answer field and enter icom. 3. Press Enter to save your changes. 514 Administrator Guide for Avaya Communication Manager…

• Page 515: Observing Calls

  This capability is often used to monitor service quality in call centers and other environments where employees serve customers over the telephone. On Avaya Communication Manager, this is called «service observing» and the user observing calls is the «observer.»…

• Page 516
  They cannot switch to the other mode without ending the session and beginning another. Note: Feature access codes are required for remote observing. Note: Related topics See «Service Observing» in Feature Description and Implementation for Avaya Communication Manager, 555-245-205, for detailed information on service observing. 516 Administrator Guide for Avaya Communication Manager…

• Page 517: Chapter 15: Managing Data Calls

  Chapter 15: Managing Data Calls Types of Data Connections You can use Avaya Communication Manager to allow the following types of data elements/ devices to communicate to the world: Data Terminals ● Personal computers ● Host Computers (for example, CentreVu CMS or INTUITY AUDIX) ●…

• Page 518: Data Call Setup

  2. Choose one of the following data modules and administer all fields: Processor/Trunk Data Module ● Data Line Data Module ● 3. On the Modem Pool Group screen, administer the Circuit Pack Assignments field. See Modem Pool Group on page 1299 for more information. 518 Administrator Guide for Avaya Communication Manager…

• Page 519
  In addition, the user can dial the following special characters. Table 5: Special characters Character SPACE, -, (, and) improves legibility. Communication Manager ignores these characters during dialing. + character (wait) interrupts or suspends dialing until the user receives dial tone , (pause) inserts a 1.5-second pause…
• Page 520
  Time is exceeded. Call terminates. FORWARDED DCP, BRI Equivalent to redirection-notification signal. Called terminal activates Call Forwarding and receives a call, and call is forwarded. INCOMING DCP, BRI Equivalent to ringing. CALL 1 of 2 520 Administrator Guide for Avaya Communication Manager…
• Page 521
  Data Call Setup Table 6: Call-progress messages (continued) Message Application Meaning INVALID Entered name is not in ADDRESS alphanumeric-dialing table. WRONG Entered name is not in ADDRESS alphanumeric-dialing table. PLEASE ANS- DCP, BRI Originating telephone user transferred call to data module using One-Button Transfer to Data.
• Page 522
  This ensures that a conversion resource, if needed, and the data module are reserved for the call. Avaya recommends the use of Data Call Preindication before 1-button transfer to data for data calls that use toll-network facilities. Data Call Preindication is in effect until the associated data-extension button is pressed again for a 1-button transfer;…
• Page 523
  The system handles all presently defined BRI bearer data-call requests. Some capabilities that are not supported by Avaya terminals are provided by non-Avaya terminals. If Communication Manager does not support a capability, a proper cause value returns to the terminal.
• Page 524
  If the option is not set to precise, and a data call is set up over an analog trunk, messages describing the status of the called endpoint (for example, RINGING, BUSY, TRY AGAIN) change according to which tone-detection option is selected. 524 Administrator Guide for Avaya Communication Manager…

• Page 525: Alphanumeric Dialing

  Invalid Address message (DCP) or a Wrong Address message (ISDN-BRI). Because data terminals access Communication Manager via DCP or ISDN-BRI data modules, dialing procedures vary: For DCP, at the DIAL: prompt users type the alphanumeric name. Press Enter.

• Page 526: Data Hotline

  Administering Data Hotline To administer a data hotline: 1. You can use an abbreviated dialing list for your default ID. See «Abbreviated Dialing» in Feature Description and Implementation for Avaya Communication Manager, 555-245-205, for more information. 2. On the Station screen, administer the following fields.

• Page 527: Data Privacy

  Data Privacy Data Privacy Data Privacy protects analog data calls from being disturbed by any of the system’s overriding or ringing features. Administering Data Privacy To administer data privacy: 1. Choose either of the following: On the Feature Access Code screen, administer the Data Privacy Access Code field.

• Page 528: Default Dialing

  For the AT command interface supported by the 7400A/7400B/8400B data module, to dial the default destination, enter the ATD command (rather than press return). 528 Administrator Guide for Avaya Communication Manager…

• Page 529: Data Restriction

  Administering Default Dialing To administer default dialing: 1. You can use an abbreviated dialing list for your default ID. See «Abbreviated Dialing» in Feature Description and Implementation for Avaya Communication Manager, 555-245-205, for more information. 2. On the Data Module screen, administer the following fields: Special Dialing Option as default.

• Page 530
  Priority Calls are allowed if the analog station is idle. Call Waiting (including Priority Call Waiting) is denied if the station is busy. However, Priority Calls appear on the next available line appearance on multiappearance telephones. Service Observing ● A data-restricted call cannot be service observed. 530 Administrator Guide for Avaya Communication Manager…

• Page 531: Data-Only Off-Premises Extensions

  Data-Only Off-Premises Extensions Data-Only Off-Premises Extensions Data-Only Off-Premises Extensions allows users to make data calls involving data communications equipment (DCE) or digital terminal equipment (DTE) located remotely from the system site. A Data-Only Off-Premises Extension uses an on-premises modular trunk data module (MTDM). The system communicates with remote data equipment through the private-line facility linking the on-premises MTDM and the remote data equipment.

• Page 532: Data Modules — General

  ● Ethernet data module. ● Point-to-Point Protocol (PPP) data module. ● For more information, see Administration for Network Connectivity for Avaya Communication Manager, 555-233-504. Note: The 51X series Business Communications Terminals (BCT) are not administered Note: on the Data Module screen. The 510 BCT (equivalent to a 7405D with a display…

• Page 533
  Data Modules — General Detailed description of data modules TTI allows data modules without hardware translation to merge with an appropriate data module connected to an unadministered port. The unadministered port is given TTI default translation sufficient to allow a terminal connected to the data module (connected to the port) to request a TTI merge with the extension of a data module administered without hardware translation.

• Page 534: Data Modules

  The ADM provides integrated voice and data on the same telephone and supports data rates of 300, 1200, 2400, 4800, 9600, and 19200-bps. This module also supports the Hayes command set, providing compatibility with PC communications packages. 534 Administrator Guide for Avaya Communication Manager…

• Page 535: Administered Connection

  Administered Connection An Administered Connection (AC) is a connection between two access or data endpoints. Avaya Communication Manager automatically establishes and maintains the connection based on the attributes you administer. ACs provides the following capabilities. Support of both permanent and scheduled connections ●…

• Page 536
  The originating server uses the destination address to route the call to the desired endpoint. When the server establishes two or more ACs at the same time, Communication Manager arranges the connections in order of priority. AC attempts can fail for the following reasons: Resources are unavailable to route to the destination.
• Page 537
  ● of the AC. ACs are retried in priority order. ● When you change the time of day on Communication Manager, an attempt is made to ● establish all ACs in the waiting-for-retry state. Dropping Administered Connections An AC remains active until one of the following occurs: The AC is changed, disabled, or removed.
• Page 538
  X.25 Data Module (for more information, see Administration for Network Connectivity for ● Avaya Communication Manager, 555-233-504) 7500 Data Module (use with ISDN Line 12-BRI-S-NT or ISDN Line 12-BRI-U-NT circuit ● pack) World Class Core BRI Data Module (use with wcbri) ● 538 Administrator Guide for Avaya Communication Manager…
• Page 539
  Administered Connection 2. On the DS1 Circuit Pack screen, administer all fields. Use with switch node carriers. See DS1 Circuit Pack on page 921 for more information. 3. On the Access Endpoint screen, administer all fields. See Access Endpoint on page 725 for more information.
• Page 540
  If the time change causes an active AC to be outside its scheduled period, the AC is dropped. If the time change causes an inactive AC to be within its scheduled period, Communication Manager attempts to establish the AC. If any AC (scheduled or continuous) is in retry mode and the system time changes, Communication Manager attempts to establish the AC.

• Page 541: Modem Pooling

  Modem Pooling Modem Pooling Modem Pooling allows switched connections between digital-data endpoints (data modules) and analog-data endpoints via pods of acoustic-coupled modems. The analog-data endpoint is either a trunk or a line circuit. Data transmission between a digital data endpoint and an analog endpoint requires conversion via a modem, because the DCP format used by the data module is not compatible with the modulated signals of an analog modem.

• Page 542
  DS1 Tie Trunk Service ● Connect modems used for Modem Pooling to AVD DS1 tie trunks via Data Terminal Dialing or by dialing the feature-access code for data origination. 542 Administrator Guide for Avaya Communication Manager…

• Page 543: Pc Interface

  The digital telephone plugs into the telephone jack on the PC Interface card. ● The line jack on the card provides a digital port connection to Avaya DEFINITY servers. ● The distance between the PC Interface card and the PBX should be no more than 1524m ●…

• Page 544
  PC. Assign each card a separate extension, and assign each extension one or more appearances. The availability of specific features depends on the COS of the extension and the COS for Communication Manager. Modem Pooling is provided to ensure general availability of off-net data-calling services.
• Page 545
  SECURITY ALERT: users can delete or copy PC files with this feature. You can password-protect this feature. See the Avaya Toll Fraud and Security Handbook, 555-025-600, for additional steps to secure your system and to find out about obtaining information regularly about security developments.

• Page 546: Wideband Switching

  You can combine several narrowband channels into one wideband channel to accommodate the extra bandwidth requirement. Avaya Communication Manager serves as a gateway to many types of high-bandwidth traffic. In addition, DS1 Converter circuit packs are used for wideband switching at DS1 remote EPN locations.

• Page 547: Channel Allocation

  Certain applications, like video conferencing, require greater bandwidth. You can combine several narrowband channels into one wideband channel to accommodate the extra bandwidth requirement. Avaya Communication Manager serves as a gateway to many types of high-bandwidth traffic. In addition, DS1 converters are used for wideband switching at remote locations.

• Page 548: Endpoint Applications

  ISDN-PRI terminal adapters translate standard ISDN signaling into a form that can be used by the endpoint application and vice versa. The terminal adapter also must adhere to the PRI-endpoint boundaries as administered on Avaya Communication Manager when handling both incoming (to the endpoint) applications and outgoing calls.

• Page 549
  Wideband Switching Line-side (T1 or E1) ISDN-PRI facility A line-side ISDN-PRI (T1 or E1) facility is comprised of a group of DS0s (24 for a T1 facility and 32 for an E1 facility). In this context, these DS0s are also called channels. T1 facilities have 23 B-channels and a single D-channel.

• Page 550: Data Backup Connection

  WAEs have no signaling interface to the server or media server. These endpoints simply transmit and receive wideband data when the connection is active. Note: Communication Manager can determine if the connection is active, but this does Note: not necessarily mean that data is actually coming across the connection.

• Page 551: Primary Data Connectivity

  Communication Manager; ISDN endpoints can also establish additional calls when extra bandwidth is needed. Any failures not automatically restored by Avaya Communication Manager are signaled to the endpoint application, which can initiate backup data connections over the same PRI endpoint.

• Page 552
  D-channel always being partially contaminated. On an E1 facility, however, a D-channel is not considered a busy trunk because H11 and H12 calls can still be placed on that facility; an E1 facility with a D-channel and idle B-channels is considered an idle facility. 552 Administrator Guide for Avaya Communication Manager…
• Page 553
  Wideband Switching Since H12 is 1,920 Kbps which is comprised of 30 B-channels, a 1,920-kbps call can only be carried on an E1 facility. As with H11, the hunt algorithm uses a fixed allocation scheme with channel 1 being the fixed starting point. Hence, an H12 call always is carried on B-channels 1 to 15 and 17 to 31 on an E1 facility (as shown in the following table).
• Page 554
  For example, a user side of an interface selects the B-channel for an outgoing call and, before Communication Manager receives and processes the SETUP message, the server also selects the same B-channel for call origination. Since any single wideband call uses more channels, the chances of glare are greater.
• Page 555
  B-channels. Blocking also occurs for wideband calls when bandwidth is not available in the appropriate format (that is, fixed, floating, or flexible). To reduce blocking, Communication Manager selects trunks for both wideband and narrowband calls to maximize availability of idle fixed channels for H0, H11, and H12 calls and idle floating channels for N x DS0 calls that require a contiguous bandwidth.
• Page 556
  Call Vectoring is used by certain applications. When an incoming wideband call hunts for an available wideband endpoint, the call can route to a VDN, that sends the call to the first available PRI endpoint. 556 Administrator Guide for Avaya Communication Manager…
• Page 557
  Wideband Switching Class of Restriction ● COR identifies caller and called-party privileges for PRI endpoints. Administer the COR so that account codes are not required. Forced entry of account codes is turned off for wideband endpoints. Facility Busy Indication ● You can administer a busy-indicator button for a wideband-endpoint extension, but the button does not accurately track endpoint status.

• Page 558: Callvisor Adjunct-Switch Applications Interface

  CallVisor Adjunct-Switch Applications Interface (ASAI) links Avaya Communication Manager and adjunct applications. The interface allows adjunct applications to access switching features and supply routing information to Communication Manager. CallVisor ASAI improves Automatic Call Distribution (ACD) agents’ call handling efficiency by allowing an adjunct to monitor, initiate, control, and terminate calls on the media server.

• Page 559
  4. Switch processing element (SPE) ASAI Capabilities For information concerning the types of associations over which various event reports can be sent, see Avaya Communication Manager ASAI Technical Reference, 555-230-220. Considerations If your system has an expansion cabinet (with or without duplication), ASAI resources ●…

• Page 560: Setting Up Callvisor Asai

  On the System-Parameters Customer-Options screen, verify the: ● — ASAI Link Core Capabilities field is y. If not, contact your Avaya representative. — Computer Telephony Adjunct Links field is y if the adjunct is running the CentreVu Computer Telephony. Instructions To set up CallVisor ASAI: 1.

• Page 561
  Setting up CallVisor ASAI Figure 202: CTI Link screen when Type field is ASAI or ADJLK add cti-link next Page 1 of x CTI LINK CTI Link: 1 Extension: 40001 Type: ASAI Port: 1C0501 COR: 1 Name: ASAI CTI Link 1 BRI OPTIONS XID? y Fixed TEI? n…
• Page 562
  Managing Data Calls 562 Administrator Guide for Avaya Communication Manager…

• Page 563: Chapter 16: Administering Media Servers

  Overview Chapter 16: Administering Media Servers This chapter describes how to administer an Avaya media server and an Avaya G700 Media Gateway. It is targeted for system administrators after the product is installed and tested. In a converged network where voice and data are both sent over a corporate local area network (LAN), this configuration can provide primary or standby telephony and communications-processing capabilities.

• Page 564: Administering The G700 Media Gateway

  Description and Reference for Avaya Communication Manager, 555-245-207. G700 Media Gateway physical design The G700 Media Gateway is a19-inch, rack-mount design similar to other Avaya P330 hardware. The media gateway can be a member of a P330 stack of Layer 2 or 3 devices, reside in a stack of other media gateways, or operate as a standalone unit.

• Page 565
  The LED array on the left indicates when the S8300 is active and when it is safe to power ● it down. The green LED indicates that Avaya Communication Manager is running. A Shut Down button can be used to shut down the server (the S8300 can also be shut ●…
• Page 566
  Survivable Processor (LSP). An LSP can take over call processing if the primary call-processing system (such as another Avaya Media Server) is unavailable for any reason (such as a network failure or server problem). The media server can be either the primary or LSP media server; it is set up to operate as a primary or standby LSP server during the configuration process using the Media Server Web Interface.
• Page 567
  Administering the G700 Media Gateway If the primary call-processing server goes offline and an LSP is available as a standby unit, it will assume call processing as follows: IP telephones and media gateways that were previously using the primary media server ●…
• Page 568
  555-234-101. SNMP alarms are different from server hardware- or software-generated Operations Support System (OSS) alarms that are recorded in the server logs, and might be reported to Avaya’s Initialization and Administration System (INADS) or another services support agency over the server’s optional modem interface or through SNMP notifications.

• Page 569: Administering The Media Server

  Gateway, or through the Services Ethernet interface on the front of the media server connected to a laptop PC using a crossover cable. Details on how to configure a laptop for a direct connection are in the online help and in Welcome to the Avaya S8300 Media Server and Avaya G700 Media Gateway.

• Page 570
  Logon screen. If you plan to use this computer and browser to access this or other Avaya media servers again, click the main menu link to Install Avaya Root Certificate after you log in.
• Page 571
  Administering the Media Server Figure 206: Integrated Management Logon/Password screen 4. Type your password in the Password field, and click Logon or press Enter. Note: If your login is Access Security Gateway (ASG) protected, you will see an ASG Note: challenge screen.
• Page 572
  The Maintenance Web Interface allows you to maintain, troubleshoot, and configure the media server. To access the Maintenance Web Pages: 1. From the Integrated Management SDS home page (see Figure 207), click Launch Maintenance Web Interface. The system displays the Maintenance Web Pages home page. 572 Administrator Guide for Avaya Communication Manager…

• Page 573: Backing Up And Restoring Data

  Media server Web interface tasks Key tasks that administrators typically perform on Avaya media servers are summarized in this section. See online help for more detailed information.

• Page 574: Upgrading Software And Configuration

  To activate SNMP alarm notification for devices, use the SNMP Traps screen to set up SNMP destinations in the corporate NMS. SNMP traps for other devices on the network can be administered using Device Manager. See Using Device Manager to administer G700 Media Gateway components on page 567. 574 Administrator Guide for Avaya Communication Manager…

• Page 575
  Use media gateway commands set snmp trap enable auth and tcp syn-cookies for this. For more information on media gateways, see Maintenance Commands for Avaya Communication Manager, Media Gateways and Servers, 03-300431 and Maintenance Procedures for Avaya Communication Manager, Media Gateways and Servers, 03-300432.

• Page 576: Setting Up Processor Ethernet

  PE interface is the logical appearance of the CE interface within Communication Manager software. The interface that is assigned to the PE can be a control network or a corporate LAN. The interface that is selected determines which physical port the PE uses on the server.

• Page 577
  Consideration should be given to which interface you want the file sync to use. Avaya recommends the use of the customer LAN for file sync. 4. On the Communication Manager System Access Terminal (SAT), enter the name for each ESS server, LSP, and adjunct in the IP Node Names screen.

• Page 578: Defining Network Port Usage

  Telnet firmware monitor 2945 H.248 message TCP incoming and outgoing 5000 to 9999 Processor Ethernet TCP incoming 5010 IPSI/Server control channel 5011 IPSI/Server IPSI version channel 5012 IPSI/Server serial number channel 1 of 2 578 Administrator Guide for Avaya Communication Manager…

• Page 579
  Port Used by: Description 21873 (TCP port) The main server(s) running Prior to an upgrade to Communication Manager 2.0 Communication Manager 3.0 to download translations to the or later, servers running LSP(s). Communication Manager 2.x used port 21873 to download translations to the LSP(s).
• Page 580
  Use the information in this section to configure the PE interface on the server. This section does not contain complete information on how to configure the Communication Manager server. For information on how to configure the Communication Manager server, see the installation documentation for your server type.
• Page 581
  Setting up Processor Ethernet Setting identities Using the Web interface, configure Processor Ethernet on the server as follows: 1. On the Configure server — Set Identities page, select the interface that will be used for Processor Ethernet. The interface you select is based on what the PE interface is used for and the topology of your network.

• Page 582: Configuring An Lsp Or An Ess Server

  Configure LSP or ESS screen in addition to the Set Identities screen. Figure 211 shows an example of the Configure LSP or ESS screen. Figure 211: Configure server — configure an LSP or an ESS server 582 Administrator Guide for Avaya Communication Manager…

• Page 583
  LAN to which the LSP or the ESS server is also connected. The ESS server or the LSP must be able to ping to the address. Consideration should be given to which interface you want the file sync to use. Avaya recommends the use of the customer LAN for file sync.
• Page 584
  PE interface of the ESS server to connect to one of the three supported adjuncts (CMS, CDR, AESVCS). For more information on administering the ESS server on the Survivable Processor screen, see Survivable Processor on page 1494. 584 Administrator Guide for Avaya Communication Manager…
• Page 585
  Setting up Processor Ethernet Starting with Communication Manager 3.1, node names are used in place of IP addresses for ESS servers on pages one through five of the System Parameters ESS screen. When upgrading an ESS configuration to Communication 3.1, the following events occur: When you upgrade an ESS configuration from a release prior to Communication Manager ●…
• Page 586
  Warning level field is the maximum number of connections you want on the interface. A socket represents a connection of an endpoint to the server. As endpoints connect, the load balancing algorithms direct new registrations to interfaces that are less loaded. The current 586 Administrator Guide for Avaya Communication Manager…

• Page 587: Administering Call-Processing

  Communication Manager tries to keep the ratio used by each interface the same. Note that this is a «target» level, and that Communication Manager might use more sockets than specified in the field.

• Page 588: Security Considerations

  567. Command syntax changes for media modules The syntax for using the SAT commands for a G700 Media Gateway or Avaya Media Server has changed. In a traditional DEFINITY system, ports are identified by the cabinet number, carrier, slot, and port. For example: 02A0704 Because this numbering convention does not make sense for media modules, a new convention was developed.

• Page 589
  Administering Call-processing Accessing the Communication Manager SAT CLI You can access the command line interface (CLI) of the Avaya Communication Manager SAT using any of the following methods: Using Secure Shell for remote login on page 589 ● Using Telnet over the Customer LAN on page 591 ●…
• Page 590
  SFTP is enabled on the circuit pack, and the login/password are valid for 5 minutes. To disable a secure FTP (SFTP) session on a CLAN or VAL circuit pack: 1. Type disable filexfr [board location]. Press Enter. SFTP is disabled on the circuit pack. 590 Administrator Guide for Avaya Communication Manager…
• Page 591
  4. Click the Submit button. Setting up Windows for Modem Connection to the Media Server (Windows 2000 or XP) Note: The remote dial-up PC must be configured for PPP access. Also, Avaya Terminal Note: Emulator does not support Windows XP. Issue 2.1 May 2006…
• Page 592
  8. Select Internet Protocol (TCP/IP) and click Properties. 9. Click the Advanced button. 10. Uncheck (clear) the Use default gateway on remote network box. 11. Click OK three times to exit and save the changes. 592 Administrator Guide for Avaya Communication Manager…
• Page 593
  Administering Call-processing Using Windows for PPP modem connection (Windows 2000 or XP) This connection requires you to have a modem on your PC. It also requires you to do the following first: Setting up Windows for Modem Connection to the Media Server (Windows 2000 or on page 591 Configuring the remote PC for PPP modem connection (Windows 2000 or XP, Terminal Emulator, or ASA)
• Page 594
  Result Code (Decimal) (Hexadecimal) Argentina AT%T19,0,34 Australia AT%T19,0,01 Austria AT%T19,0,34 Belgium AT%T19,0,34 Brazil AT%T19,0,34 Canada AT%T19,0,34 China AT%T19,0,34 Cyprus AT%T19,0,34 Czech Republic AT%T19,0,25 Denmark AT%T19,0,34 Finland AT%T19,0,34 France AT%T19,0,34 Germany AT%T19,0,34 1 of 3 594 Administrator Guide for Avaya Communication Manager…
• Page 595
  Administering Call-processing Country AT Command Result Code (Decimal) (Hexadecimal) Greece AT%T19,0,34 Hong Kong AT%T19,0,30 Hungary AT%T19,0,30 Iceland AT%T19,0,34 India AT%T19,0,30 Indonesia AT%T19,0,30 Ireland AT%T19,0,34 Italy AT%T19,0,34 Japan AT%T19,0,10 Korea AT%T19,0,30 Liechtenstein AT%T19,0,34 Luxembourg AT%T19,0,34 Mexico AT%T19,0,34 Netherlands AT%T19,0,34 New Zealand AT%T19,0,09 Norway AT%T19,0,34…
• Page 596
  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.
• Page 597
  The system displays the Network tab. 10. In the IP address field, type the IP address of the Media Server. 11. In the TCP/IP port number field, type 5023 to log in directly to the Communication Manager SAT command line.
• Page 598
  10. In the IP address field, type the IP address of the connection Dialup Status box as noted in Step 9. 11. In the TCP/IP port number field, type 5023 to log in directly to the Communication Manager SAT command line.
• Page 599
  GEDI and Data Import. For more information refer to the Online Help, Guided Tour, and Show Me accessed from the Avaya Site Administration Help menu. To use Avaya Site Administration, open the application and select the switch (media server) you want to access. When prompted, log in.
• Page 600
  The IP Network Region screen also must be administered for QoS monitoring (for details, ● see Administration for Network Connectivity for Avaya Communication Manager, 555-233-504). If the RTCP Enabled field is left at default (y), then be sure to set a valid IP address in the IP-Options System Parameters screen.

• Page 601: Administering Snmp Agents

  Media Gateway serviceability commands Additional commands related to media gateways appear in Maintenance for the Avaya G700 Media Gateway controlled by an Avaya S8300 Media Server or an Avaya S8700 Media Server. These include: The status media-gateways command provides an alarm summary, busyout ●…

• Page 602
  Administer SNMP agents and alarm categories using the Integrated Management Maintenance Web Pages. To access the Maintenance Web Pages: 1. Open your browser and log on to the Avaya Integrated Management Standard Management Solutions system. The system displays the SMS home page.
• Page 603
  Your changes to this interface do not affect services on the other Ethernet interfaces. On an Avaya media server, you must turn on network access for the SNMP ports to allow SNMP access to Communication Manager.
• Page 604
  All input and output boxes for SNMP ports must be turned on (checked) for SNMP access to Communication Manager to work. 4. If necessary, click the Advanced Setting button to adjust the status of a service that is not listed on the first page.
• Page 605
  Administering SNMP Agents Figure 216: Firewall Advanced Setting screen 5. Click Standard Services to return to the first screen of the Firewall page. 6. Click Submit to save your changes. Issue 2.1 May 2006…

• Page 606: Viewing Current Alarms

  To clear an entry from the Current Alarms page: 1. Click in the box to the left of the entry. A checkmark displays in the box. 2. Click Clear. The entry is deleted. 606 Administrator Guide for Avaya Communication Manager…

• Page 607
  Administering SNMP Agents To clear all entries from the Current Alarms page: 1. Click Clear All. All alarm entries are deleted from the page. Checking Agent Status The Agent Status Web page shows the current state of the Master Agent and all of the sub agents.
• Page 608
  1. On the Maintenance Web Pages home page, under Alarms, click SNMP Agents. The system displays the SNMP Agents page. Note: For more information on accessing the Web interface, see Accessing the Media Note: Server Web Interface. 608 Administrator Guide for Avaya Communication Manager…
• Page 609
  Administering SNMP Agents Figure 219: SNMP Agents page The screen is divided into two sections: IP Addresses for SNMP Access — Define a list of IP addresses from which SNMP ● access is allowed, or allow All IP addresses. Issue 2.1 May 2006…
• Page 610
  9. In the Community Name (read-write) field, type the name for this community or user. This community or user can query agents for information (SNMPGETs) and send commands to an agent (SNMPSETs). 610 Administrator Guide for Avaya Communication Manager…
• Page 611
  Communication Manager data for SNMP management. The MIB can be used to interpret SNMP data that is supported by the Communication Manager SNMP Agent. The MIB is most useful when installed on your SNMP trap receiver to translate any SNMP traps received from Communication Manager.
• Page 612
  Administering Media Servers To display the MIB reference document: On the SNMP Agents page, click View G3-Avaya-MIB Data. ● The system displays a text file of the MIB. Figure 221: G3-Avaya-MIB Data screen Administering SNMP trap support Use the SNMP Traps page to specify the alarms to be sent as traps. Some form of corporate network management system (NMS) must be in place to collect the SNMP messages.
• Page 613
  Administering SNMP Agents Adding trap destinations To add a trap destination: 1. On the Maintenance Web Pages home page, under Alarms, click SNMP Traps. The system displays the SNMP Traps page. Any traps that have already been administered are displayed in a Current Settings section. In this case, no trap destinations have been configured.
• Page 614
  5. Select the SNMP version for the destination of the traps. You can select one or more than one version. 6. Complete the fields associated with the version(s) you selected: — SNMP version 1 In the Community name field, enter the SNMP community name. 614 Administrator Guide for Avaya Communication Manager…
• Page 615
  Administering SNMP Agents — SNMP version 2c a. Select the Notification type: trap or inform. b. In the Community name field, enter the SNMP community name. — SNMP version 3 a. Select the Notification type: trap or inform. b. In the User name field, enter an SNMP user name that the destination will recognize. c.
• Page 616
  224). Traps that have already been administered are displayed in the Current Settings section. 2. Click the radio button next to the trap you want to change. 3. Click Change. The system displays the Change Trap Destination page. 616 Administrator Guide for Avaya Communication Manager…
• Page 617
  Administering SNMP Agents Figure 225: Change Trap Destination page 4. Modify the IP address and SNMP data as desired. 5. Click Change. The system displays the SNMP Traps page, showing the updated information for this trap in the Current Settings section. Deleting trap destinations To delete a trap destination: 1.
• Page 618
  The system re-displays the SNMP Traps page, with information for the deleted trap destination removed. 5. To cancel the deletion, click Do Not Delete. The system returns to the SNMP Traps page, with information for the trap destination still displayed. 618 Administrator Guide for Avaya Communication Manager…
• Page 619
  Administering SNMP Agents Administering SNMP Trap Filters Use the Filters page to specify the severity level, alarm category, and maintenance object information for the SNMP agent. In CM 3.1, filters only apply to CM alarms. Server alarms cannot be filtered. Note: If you have Fault and Performance Manager (FPM), then create the filters using Note:…
• Page 620
  To change the Customer Alarm Reporting Options: 2. Click the radio button of the option you prefer, Report Major and Minor Communication Manager alarms only, or Report All Communication Manager alarms. 3. Click Update. The system displays a confirmation of the new setting.
• Page 621
  Administering SNMP Agents Note: For a listing of categories and associated MO types, see online Help. Note: 7. In the MO-Type field, enter the maintenance object types to filter by. In this example, All ATM alarms are included. Alternately, you can choose to filter by MO location in the MO-Location field.
• Page 622
  Filters section. 2. Click the radio button next to the filter you want to change to select it. 3. Click Change. The system displays the Change Filter page. 622 Administrator Guide for Avaya Communication Manager…
• Page 623
  Administering SNMP Agents Figure 232: Change Filter page 4. Modify the filter configuration as desired. 5. Click Change. The system displays a confirmation message that the filter has successfully been changed. Figure 233: Filter changed confirmation screen 6. To review what the information looks like, under Alarms, click on Filters. The system displays the updated Filters page, displaying the changes you made to the filter.
• Page 624
  The system displays a confirmation dialog box. Figure 234: Delete filter confirmation 4. To delete the filter, click OK. The system displays a message confirming that the filter has successfully been deleted. Figure 235: Filter successfully deleted screen 624 Administrator Guide for Avaya Communication Manager…
• Page 625
  Administering SNMP Agents Testing SNMP Traps Use the SNMP Test page to send a test trap to the configured SNMP trap receiver(s). To send a test trap: 1. Under the Alarms section of the Maintenance Web Pages home page, click SNMP Test. The system displays the SNMP Test page.
• Page 626
  Administering Media Servers 626 Administrator Guide for Avaya Communication Manager…

• Page 627: Chapter 17: Collecting Billing Information

  Before you start The call accounting system that you use might be sold by Avaya, or it might come from a different vendor. You need to know how your call accounting system is set up, what type of call accounting system or call detail recording unit you are using, and how it is connected to the server running Communication Manager.

• Page 628
  Toll Restricted? y Trunk Type: 2. In the CDR Reports field, type y. This tells Communication Manager to create call records for calls made over this trunk group. 3. Press Enter to save your changes. 4. Type change system-parameters cdr. Press Enter.
• Page 629
  8. In the Record Outgoing Calls Only field, type n. This tells Communication Manager to create records for both incoming and outgoing calls over all trunk groups that use CDR. 9. In the Outg Trk Call Splitting and Inc Trk Call Splitting fields, type y.

• Page 630: Recording Calls Between Users On The Same Server

  Collecting Billing Information More information You can also administer Communication Manager to produce separate records for calls that are conferenced or transferred. This is called Call Splitting. There are many other variations that you can administer for CDR, and these are described in the screens section of this book.

• Page 631
  5. In the first three available slots, type 5100, 5101, and 5102. 6. Press Enter to save your changes. 7. Communication Manager will now produce call records for all calls to and from these extensions, including those that originated on the local server.

• Page 632: Tracking Calls By Account Code

  2. In the CDR Account Code Length field, type 5. 3. Press Enter to save your changes. 4. Assign an account button on the Station screen for extension 5004. See Adding Feature Buttons on page 127 for more information. 632 Administrator Guide for Avaya Communication Manager…

• Page 633: Forcing Users To Enter Account Codes

  Before you start Before you can administer Forced Entry of Account Codes, it must be enabled on the System Parameters Customer-Options screens. If it is not, please contact your Avaya representative. Instructions In this example, we administer the system to force users in our North American office to enter an account code before making international calls.

• Page 634
  (COR) to trunks or other facilities that you want to restrict. With this method, all users with this COR must enter account codes before making any outgoing trunk calls. See Class of Restriction on page 809 for more information. 634 Administrator Guide for Avaya Communication Manager…

• Page 635: Receiving Call-Charge Information

  Receiving Call-Charge Information Receiving Call-Charge Information Avaya Communication Manager provides two ways to receive information from the public network about the cost of calls. Note that this service is not offered by the public network in some countries, including the US.

• Page 636
  4. In the Supplementary Service Protocol field, type a. 5. The Charge Advice field, type end-on-request. This ensures that Communication Manager will place one request for charge information. This reduces the amount of information passed to Communication Manager and consumes less processor time than other options.

• Page 637: Viewing Call Charge Information

  Description and Implementation for Avaya Communication Manager, 555-245-205. Viewing Call Charge Information Avaya Communication Manager provides two ways for you to view call-charge information: on a telephone display or as part of the Call Detail Recording (CDR) report. From a display, users can see the cost of an outgoing call, both while the call is in progress and at the end of the call.

• Page 638
  If you want call charges to display automatically whenever a user places an outgoing call, you can set Automatic Charge Display to y on the user’s COR screen. 638 Administrator Guide for Avaya Communication Manager…

• Page 639: Chapter 18: Telephone Reference

  Chapter 18: Telephone Reference This reference section describes many of the telephones and adjuncts that you can connect to servers running Avaya Communication Manager. Use this section to: determine where to connect a telephone—is it analog, digital, hybrid, or IP? Is it designed ●…

• Page 640: 500 Telephones

  The firmware for the 2420 can be upgraded over its DCP connection to the switch. A new firmware image first must be downloaded into switch memory from a local trivial file transfer protocol (TFTP) server. 640 Administrator Guide for Avaya Communication Manager…

• Page 641: 2500-Series Telephones

  2500-series telephones Avaya recommends that you administer call appears only on the first 8 call appearance/feature buttons on the 2420 telephone. 2500-series telephones The 2500-series telephones consist of single appearance analog telephones with conventional touch-tone dialing. You can allow 2500-series telephones users to access features by giving them the appropriate feature access codes.

• Page 642
  Telephone Reference 4601 IP telephone The 4601 is a low-cost Avaya VoIP telephone. It is based on the 4602, but does not have an H.323 v2, except for automatic unnamed registration. LCD display. The 4601 supports supports two call appearances, and has no speakerphone. The 4601 looks similar to the 4602, but has some changes to the buttons (no SPKR, no MUTE), LEDs, and bezel.
• Page 643
  4620SW IP telephone Effective December 5, 2005, Avaya will no longer make 4620 IP telephones commercially available. The 4621SW IP telephone is an appropriate replacement. The 4621SW IP telephone, generally available since May 2005, offers the same functionality as the 4620 and adds a backlit display.
• Page 644
  The Avaya 4690 IP Speakerphone provides the convenience and productivity benefits inherent in a purpose-built hands-free conference phone. It also delivers the extensive set of Avaya Communication Manager features directly to the conference room. It offers many of the same features as other Avaya speakerphones (360 degree coverage, two optional extended microphones for expanded coverage, full-duplex operation) and adds to them some additional capabilities.

• Page 645: 6200-Series Telephones

  6200-series telephones 6200-series telephones 6210 telephone The 6210 telephones are single-line analog models. They have fixed Flash, Redial, and Hold feature buttons and a message waiting light. 6218 telephone The 6218 telephones are single-line analog models. They have 10 programmable dialing buttons.

• Page 646
  2. Handset cord jack 8. Message light 3. Flash button 9. Handset volume control 4. Redial button 10. Dial pad 5. Hold button 11. LINE jack (on bottom of telephone) 6. DATA jack 646 Administrator Guide for Avaya Communication Manager…
• Page 647
  6200-series telephones Figure 244: The 6218 telephone 6220 Program Pause Tel.# Mute Spkr Flash PQRS WXYZ Redial Hold Figure notes: 9. Personalized ring 1. Handset parking tab 2. Handset 10. Ringer volume control 3. Program button 11. 10 programmable dialing buttons 4.
• Page 648
  5. Handset cord jack 13. Pause button 6. Handset/speakerphone volume control 14. Message light 7. Flash button 15. Speakerphone button 8. Redial button 16. Dial pad 17. LINE jack (on bottom of telephone) 648 Administrator Guide for Avaya Communication Manager…

• Page 649: 6400-Series Telephones

  6400-series telephones 6400-series telephones The 6400-series telephones are DCP 2-wire telephones that work with Avaya Communication Manager. The last two digits of the 6400-series model number identify the number of call appearances (2-lamp buttons) for that model. For example, the 6424D has 24 call appearances.

• Page 650
  The 6416D+M telephone is similar to the 6416D, but with modular capabilities. You can install a module in the telephone’s desktop stand for increased set functionality. Note that these modules can only be used in the desktop position; they cannot be used if the telephone is wall-mounted. 650 Administrator Guide for Avaya Communication Manager…
• Page 651
  6400-series telephones 6424D+ telephone The 6424D+ telephone is a multi-appearance digital telephone with 24 call appearance/feature buttons. With the 6424D+ telephone the end-user can access 12 features with the softkeys and display control buttons. These 12 features can be used in addition to the features you assign to the call appearance/feature buttons.
• Page 652
  2. Feature button 9. Tray handle (includes reference cards) 3. Hold button 10. Redial button 4. Transfer/Test button 11. Speaker button 5. Conf/Ring button 12. Handset 6. Dial pad 7. Volume control button 652 Administrator Guide for Avaya Communication Manager…
• Page 653
  6400-series telephones Figure 247: 6408D telephone Menu Exit Prev Next Tel # Spkr Mute Hold Redial Trnsfr Conf Test Ring WXYZ PQRS Volume Figure notes: 1. Display 8. Volume control button 2. Softkeys 9. Dial pad 3. Display control buttons 10.

• Page 654: 7100-Series Telephones

  The 7104A telephone is a single-line analog model that is equipped with a display that is used to display stored numbers. It cannot be physically bridged to the same analog line port due to the message waiting and loop current circuitry. 654 Administrator Guide for Avaya Communication Manager…

• Page 655: 7300-Series Telephones

  7300-series telephones 7300-series telephones 7302H MERLIN telephone The 7302H is a 5-button telephone that can be desk or wall mounted. This set can no longer be ordered. Administer 7302H telephones (5-Button) as a 7303S model. 7303H MERLIN telephone The 7303H is a 10-button telephone that can be desk or wall mounted. Administer 7303H telephones (10-Button) as a 7305S model.

• Page 656
  It requires 3-pair wiring for operation. One wire pair is used for analog voice, while the other two pairs are used for digital control and signaling. Figure 248: 7303S telephone Figure notes: 1. Handset 3. 10 programmable buttons 2. Dial pad 656 Administrator Guide for Avaya Communication Manager…
• Page 657
  7300-series telephones Figure 249: 7305S telephone Figure notes: 1. Handset 3. 10 programmable buttons 2. Dial pad 4. 24 feature buttons Issue 2.1 May 2006…

• Page 658: 731X-Series Hybrid Telephones

  These telephones support Leave Word Calling (LWC), but users cannot retrieve messages ● with the display. Figure 250: 7313H telephone (BIS 10) Figure notes: 1. Handset 3. 10 programmable buttons 2. Dial pad 658 Administrator Guide for Avaya Communication Manager…

• Page 659
  731x-series hybrid telephones Figure 251: 7314H telephone (BIS 22) Figure notes: 1. Handset 3. 10 programmable buttons 2. Dial pad 4. 12 feature buttons Issue 2.1 May 2006…
• Page 660
  Telephone Reference Figure 252: 7315H telephone (BIS 22D) Figure notes: 1. Handset 3. 10 programmable buttons 2. Dial pad 4. 12 feature buttons 660 Administrator Guide for Avaya Communication Manager…
• Page 661
  731x-series hybrid telephones Figure 253: 7316H telephone (BIS 34) Figure notes: 1. Handset 3. 10 programmable buttons 2. Dial pad 4. 24 feature buttons Issue 2.1 May 2006…
• Page 662
  Telephone Reference Figure 254: 7317H telephone (BIS 34D) Figure notes:Figure Notes 1. Handset 3. 10 programmable buttons 2. Dial pad 4. 24 feature buttons 662 Administrator Guide for Avaya Communication Manager…

• Page 663: 7400-Series Telephones

  7400-series telephones 7400-series telephones 7401D telephone The 7401D (7401D01A) and the 7401+ (7401D02A) are both single appearance digital telephones which have no call appearance buttons or lights, but have two virtual call appearances. Depending on how the 7401D or the 7401+ telephone is administered, the second call appearance might be restricted to incoming priority calls and outgoing calls only.

• Page 664
  22 programmable feature-only buttons without lights, a Message light, a DISPLAY button that turns the display on and off, personalized ringing, a built-in speakerphone, a 2-line by 40-character liquid crystal display, and a built-in calculator. This set is AC powered. 664 Administrator Guide for Avaya Communication Manager…
• Page 665
  7400-series telephones Enhanced 7407D (the 7407D02C)—offers 10 call appearance buttons, each with a red ● in-use light and green status light, four standard fixed feature buttons (CONFERENCE, DROP, HOLD, and TRANSFER), three fixed feature buttons with an associated light (SELECT RING, SPEAKER, and MUTE), 22 programmable feature-only buttons without lights, nine programmable feature buttons with one light each (the uppermost two buttons can be used for voice or display features, the lower seven for display features), a Message light, personalized ringing, a built-in speakerphone, a connection for an adjunct…
• Page 666
  The 7444 is powered by the switch, however, to use the display, you must Note: connect an auxiliary power supply to the telephone. Figure 255: 7401D telephone Figure notes: 1. Handset 3. Access codes card 2. Dial pad 666 Administrator Guide for Avaya Communication Manager…
• Page 667
  7400-series telephones Figure 256: 7404D telephone Figure notes: 1. Handset 3. 6 programmable buttons 2. Dial pad Issue 2.1 May 2006…
• Page 668
  Telephone Reference Figure 257: 7405D telephone Figure notes: 1. Handset 3. 10 programmable buttons 2. Dial pad 4. 24 feature buttons 668 Administrator Guide for Avaya Communication Manager…
• Page 669
  7400-series telephones Figure 258: 7405D telephone with optional function key module Figure notes: 1. Handset 3. 10 programmable buttons 2. Dial pad 4. 24 feature buttons 5. Function key module with 24 feature module buttons Issue 2.1 May 2006…
• Page 670
  Telephone Reference Figure 259: 7405D telephone with optional digital display module Figure notes: 1. Handset 3. Digital display module with 7 display buttons 2. Dial pad 4. 10 programmable buttons 5. 24 feature buttons 670 Administrator Guide for Avaya Communication Manager…
• Page 671
  7400-series telephones Figure 260: 7405D telephone with optional call coverage module Figure notes: 1. Handset 3. Call coverage module with 20 coverage module buttons and status 2. Dial pad lamps 4. 10 programmable buttons 5. 24 feature buttons Issue 2.1 May 2006…
• Page 672
  Telephone Reference Figure 261: 7405D telephone with optional digital terminal data module Figure notes: 1. Handset 3. 10 programmable buttons 2. Dial pad 4. 24 feature buttons 5. Digital terminal data module 672 Administrator Guide for Avaya Communication Manager…
• Page 673
  7400-series telephones Figure 262: 7406D+ telephone Figure notes: 1. Handset 3. 5 programmable buttons 2. Dial pad 4. 18 feature buttons (feature buttons F2, F4, and F12 to F18 are enabled with the Shift key) Issue 2.1 May 2006…
• Page 674
  Telephone Reference Figure 263: 7406D telephone Figure notes: 1. Handset 3. 5 programmable buttons 2. Dial pad 4. 18 feature buttons (feature buttons F12 to F18 are enabled with the Shift key) 674 Administrator Guide for Avaya Communication Manager…
• Page 675
  7400-series telephones Figure 264: 7407D telephone Figure notes: 1. Handset 3. 10 programmable buttons 2. Dial pad 4. 7 display buttons 5. 24 feature buttons Issue 2.1 May 2006…
• Page 676
  Telephone Reference Figure 265: 7434D telephone Figure notes: 1. Handset 3. 10 programmable buttons 2. Dial pad 4. 24 feature buttons (11 to 34) 676 Administrator Guide for Avaya Communication Manager…
• Page 677
  7400-series telephones Figure 266: 7434D telephone with optional call coverage module Figure notes: 1. Handset 3. Call coverage module with 20 coverage module buttons and 2. Dial pad status lamps 4. 10 programmable buttons 5. 24 feature buttons (11 to 34) Issue 2.1 May 2006…
• Page 678
  Figure 267: 7434D telephone with optional digital display module Figure notes: 1. Handset 3. Digital display module with 7 display buttons 2. Dial pad 4. 10 programmable buttons 5. 24 feature buttons (11 to 34) 678 Administrator Guide for Avaya Communication Manager…

• Page 679: Isdn Telephones (7500S & 8500S)

  National ISDN (NI-1 and NI-2) BRI telephones Telephones that comply with National ISDN (NI-1 and NI-2) BRI standards can serve as telephones on a Communication Manager system if they are programmed in Call Appearance Call Handling — Electronic Key Telephone Service (CACH-EKTS) mode. Examples of NI-BRI…

• Page 680
  Four softkeys and display control buttons below the a 2-line by 24-character display can be used to access such features as a personal Directory, a Call Log, the Self-Test feature, and a personalized ringing pattern for the telephone. 680 Administrator Guide for Avaya Communication Manager…
• Page 681
  ISDN telephones (7500s & 8500s) 8520T ISDN-BRI telephones The 8520T voice/data telephone offers the following: 20 call appearance/feature buttons, each with a red and green status light, buttons for the Mute, Redial, Conference, Drop, Transfer, and Hold features (the MUTE, SPEAKER, CONF, and TRANSFER buttons have a red light next to them), a Speakerphone, a Volume control, and an Adjunct jack.
• Page 682
  Telephone Reference Figure 269: 8510T telephone Figure notes: 1. Handset 3. 10 programmable buttons 2. Dial pad 682 Administrator Guide for Avaya Communication Manager…
• Page 683
  ISDN telephones (7500s & 8500s) Figure 270: 8520T telephone Figure notes: 1. Handset 3. 10 programmable buttons 2. Dial pad 4. 10 programmable buttons (11 to 20) Note: The 8520T telephone supports 20 call appearances. The system maximum of 10 Note: call appearance buttons still applies.

• Page 684: 8110 Telephones

  The 8405D has a 1-way, listen-only speaker and a 2-line by 24-character display. ● The 8405D+ has a 2-way speakerphone and a 2-line by 24-character display. ● The 8405 telephones work in 4-wire or 2-wire environments. 684 Administrator Guide for Avaya Communication Manager…

• Page 685
  8400-series telephones 8410B telephone The 8410 telephone is a multi-appearance digital telephone with 10 call appearance/feature buttons, four standard fixed feature buttons (CONFERENCE, DROP, HOLD, and TRANSFER), a MUTE button, a SPEAKER button which can access either a 2-way speakerphone or a 1-way, listen-only speaker, a TEST button, and a Volume control button.
• Page 686
  8434DX, you must connect an auxiliary power supply to the telephone. You can connect an 801A Expansion Module to the 8434DX telephone to provide 24 additional call appearance/feature buttons. 686 Administrator Guide for Avaya Communication Manager…
• Page 687
  8400-series telephones Figure 271: 8403B telephone Figure notes: 1. Handset 3. 3 programmable buttons 2. Dial pad Issue 2.1 May 2006…
• Page 688
  3. 10 programmable buttons 2. Dial pad Note: The 8405B and 8405B+ look like the 8410B with the exception that the 8405 Note: series do not have the second column of line appearances. 688 Administrator Guide for Avaya Communication Manager…
• Page 689
  8400-series telephones Figure 273: 8410D telephone Figure notes: 1. Handset 3. 10 programmable buttons 2. Dial pad Note: The 8405D and 8405D+ look like the 8410D with the exception that the 8405 Note: series do not have the second column of line appearances. Issue 2.1 May 2006…
• Page 690
  Telephone Reference Figure 274: 8434D telephone Figure notes: 1. Handset 3. 10 programmable buttons 2. Dial pad 4. 24 feature buttons 690 Administrator Guide for Avaya Communication Manager…

• Page 691: Callmaster Telephones

  CALLMASTER telephones CALLMASTER telephones There are several types of CALLMASTER telephones: 602A and 602D CALLMASTER ● The 602 CALLMASTER models have a display, a Message light, a Mute button, and four fixed feature buttons: Conference, Drop, Hold, and Transfer. You can administer its 10 call appearance/feature (2-lamp) buttons and its 17 feature-only (1-lamp) buttons.

• Page 692
  Telephone Reference Figure 275: CALLMASTER II/CALLMASTER III digital telephone Figure notes: 1. Handset 3. 6 programmable buttons 2. Dial pad 4. 18 feature buttons 692 Administrator Guide for Avaya Communication Manager…
• Page 693
  CALLMASTER telephones Figure 276: CALLMASTER IV digital telephone Figure notes: 1. Handset 3. 6 programmable buttons 2. Dial pad 4. 15 feature buttons Issue 2.1 May 2006…
• Page 694
  Prev Next Tel # Mute Hold Speaker Redial Conf Transfer Test Ring PQRS WXYZ CALLMASTER V Volume Figure notes: 1. Dial pad 3. 4 softkey buttons 2. Display 4. 16 call appearance/feature buttons 694 Administrator Guide for Avaya Communication Manager…

• Page 695: Cordless Telephone

  Cordless telephone Cordless telephone MDC9000 cordless telephone The MDC 9000 Cordless Telephone has two basic parts, the handset and the charging base. The handset has line/programmable feature/intercom buttons, Conference, Drop, Hold, ● Transfer, Status, and Feature buttons, Headset On/Off and Handset On/Off buttons, a LCD display, an earpiece volume control switch, battery charging contacts, a directory card, and a headset jack.

• Page 696
  Telephone Reference Figure 278: MDC9000 and MDW9000 cordless telephones Figure notes: 1. 6 programmable buttons 3. 6 programmable buttons 2. Dial pad 4. Dial pad 696 Administrator Guide for Avaya Communication Manager…
• Page 697
  Cordless telephone Figure 279: MDC9000 and MDW9000 cordless telephones Figure notes: 1. 6 programmable buttons 3. 6 programmable buttons 2. Dial pad 4. Dial pad Issue 2.1 May 2006…

• Page 698: Internet Protocol (Ip) Softphones

  (NIC) or the customer has dialed into their network using a dial-up point-to-point (PPP) account. The connection is managed via a registration session with the Avaya server. The call server manages the voice connection directly to a circuit-switched telephone (Telecommuter configuration), directly to an IP Telephone (Control of IP Telephone configuration), directly to a DCP digital telephone (Control of DCP Telephone configuration), or over UDP/RTP to the IP Softphone’s iClarity IP Audio H.323 audio end-point (Road Warrior or…

• Page 699
  IP Softphone software handles the call signaling and an H.323 V2-compliant audio application such as Avaya iClarity, which is installed with Avaya IP Softphone Release 3 and later (or a third-party application, like Microsoft NetMeeting) handles the voice communications.
• Page 700
  The PC user places and takes calls with the IP Softphone interface and uses the telephone handset to speak and listen. You can also use a variation of the telecommuter for call center agents: Avaya IP Agent. This mode uses the Avaya IP Agent interface instead of the IP Softphone interface to emulate a remote CallMaster telephone.
• Page 701
  Internet Protocol (IP) Softphones Control of DCP Telephone 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.
• Page 702
  Via IP Via the Telephone server Warrior 6424D+ w/Expansion Module 8405D/8405D+ 8410D 8411D 8434D 8434D w/Expansion Module 6402 6408/6408+ 7403D 7404D 7405D 7406+/7406D 7407+/7407D 7410+/7410D 7434D 7444D 8403B 8405B/8405B+ 8410B 8411B 2 of 2 702 Administrator Guide for Avaya Communication Manager…
• Page 703
  Internet Protocol (IP) Softphones Related topics For instructions on how to administer an IP Softphone on your system, see Adding an IP Softphone on page 102. On the IP Softphone CD, see IP Softphone Overview and Troubleshooting and IP Softphone Getting Started.
• Page 704
  Telephone Reference 704 Administrator Guide for Avaya Communication Manager…

• Page 705: Chapter 19: Screen Reference

  Maintenance Commands for Avaya Communication Manager, Media Gateways and Servers, 03-300431. AAR and ARS Digit Analysis Table Avaya Communication Manager compares dialed numbers with the dialed strings in this table and determines the route pattern for the number. Field descriptions for page 1…

• Page 706
  Feature Related System Parameters screen is y. Use to drop a call on a Russian Shuttle trunk or Russian Rotary trunk if the ANI request fails. Other types of trunks treat r as y. 706 Administrator Guide for Avaya Communication Manager…
• Page 707
  AAR and ARS Digit Analysis Table Call Type (for AAR only) Enter the call type associated with each dialed string. Call types indicate numbering requirements on different trunk networks. ISDN Protocols are listed in the table below. Valid entries Usage Regular AAR calls intl The Route Index contains public network ISDN trunks that require…
• Page 708
  (E.164)-unknown normal svcl national(2) toll-auto svct national(2) normal svft service call, first party control local svfl service call, first party control toll 708 Administrator Guide for Avaya Communication Manager…
• Page 709
  This is a display-only field on the ARS Digit Analysis Table screen. Valid entries Usage 1 to 64 Defines the location of the server running Avaya Communication Manager that uses this ARS Digit Analysis Table. On the System-Parameters Customer-Options screen, the ARS field and the Multiple Locations field must be set to y for values other than all to appear.

• Page 710: Route Pattern

  Displays the percentage (0 to 100) of the system’s memory resources that have been used by AAR/ARS. If the figure is close to 100%, you can free up memory resources. Route Pattern Enter the route number you want the server running Avaya Communication Manager to use for this dialed string. Valid entries…

• Page 711: Aar And Ars Digit Conversion Table

  Digits can be inserted or deleted from the dialed number. For instance, you can tell the server running Communication Manager to delete a 1 and an area code on calls to one of your locations, and avoid long-distance charges by routing the call over your private network.

• Page 712
  Allowed only if the Allow ANI Restriction on AAR/ARS field is y on the Feature-Related System Parameters screen. Use to drop a call on a Russian Shuttle trunk or Russian Rotary trunk if the ANI request fails. Other types of trunks treat r as y. 712 Administrator Guide for Avaya Communication Manager…
• Page 713
  Valid entries Usage 0 to 9 Enter the number you want the server running Avaya Communication Manager to match to dialed numbers. If a Prefix Digit 1 is required for (1 to 18 digits) 10-digit direct distance dialing (DDD) numbers, be sure the matching pattern begins with a 1.
• Page 714
  Enter the digits that replace the deleted portion of the dialed number. Leave this field blank to simply delete the digits. (1 to 18 digits) Use # to indicate end-of-dialing. It must be at the end of the digit-string. blank 714 Administrator Guide for Avaya Communication Manager…

• Page 715: Abbreviated Dialing List

  Abbreviated Dialing List Abbreviated Dialing List This screen establishes system-wide or personal lists for speed dialing. Enhanced List The Enhanced Abbreviated Dialing List can be accessed by users to place local, long-distance, and international calls; to activate/deactivate features; or to access remote computer equipment.

• Page 716
  Size (multiple of 5) The number of dial code list entries you want in this list. Valid entries Usage 5 to 100, in multiples of 5 Up to 100 entries per screen 716 Administrator Guide for Avaya Communication Manager…
• Page 717
  Abbreviated Dialing List Group List This screen implements the Abbreviated Dialing Group List. The Group Lists are controlled by the System Administrator. Up to 100 numbers can be entered per group list that can be accessed by users to place local, long-distance, and international calls; to activate/deactivate features;…
• Page 718
  System Administrator before the telephone user can add entries in the list. The lists can be accessed by users to place local, long-distance, 718 Administrator Guide for Avaya Communication Manager…
• Page 719
  Abbreviated Dialing List and international calls; to activate/deactivate features; or to access remote computer equipment. Figure 286: Abbreviated Dialing Personal List screen change abbreviated-dialing personal Page 1 of x ABBREVIATED DIALING LIST Personal List: ________ List Number: ___ Size (multiple of 5): 5 DIAL CODE 01: ________________ 02: ________________…
• Page 720
  This screen implements a system abbreviated-dialing list. Only one system list can be assigned and is administered by the System Administrator. The list can be accessed by users to place local, long-distance, and international calls; to activate/deactivate features; or to access remote computer equipment. 720 Administrator Guide for Avaya Communication Manager…
• Page 721
  Abbreviated Dialing List Figure 287: Abbreviated Dialing System List screen add abbreviated-dialing system Page 1 of x ABBREVIATED DIALING LIST SYSTEM LIST Size (multiple of 5): 100 Privileged? n Label Language:english DIAL CODE LABELS FOR 2420/4620 STATIONS 11:************* 12:************* 13:************* 14:************* 15:************* 16:*************…
• Page 722
  Enter y if the originating party’s class of restriction (COR) is never checked and any number in the list can be dialed. Enter n if the COR is to be checked to determine if the number can be dialed. 722 Administrator Guide for Avaya Communication Manager…
• Page 723
  Abbreviated Dialing List Size (multiple of 5) Enter the number of abbreviated dialing numbers you want to assign in multiples of 5, up to 100. Figure 288 shows the last page of the Abbreviated Dialing System screen when, on the System-Parameters Customer-Options screen, the A/D Grp/Sys List Dialing Start at 01 field is n.
• Page 724
  Page 1 of x ABBREVIATED DIALING LIST 7103A Button List DIAL CODE (FOR THE 7103A STATION BUTTONS) 1: ________________________ 5. ________________________ 2: ________________________ 6. ________________________ 3: ________________________ 7. ________________________ 4: ________________________ 8. ________________________ 724 Administrator Guide for Avaya Communication Manager…

• Page 725: Access Endpoint

  Access Endpoint DIAL CODE Enter the number you want to assign to each dial code (button). Any additions or changes apply to all 7103A fixed feature telephones. While the system is waiting, a call progress tone receiver is tied up, and, since there are a limited number of receivers in the system, outgoing calling capability might be impaired.

• Page 726
  Valid entries Usage voice-grade-data For an analog tie trunk access endpoint. 56k-data For a DS1 access endpoint enter as appropriate (64k-data is not allowed for robbed-bit trunks). 64k-data wideband For a Wideband access endpoint 726 Administrator Guide for Avaya Communication Manager…
• Page 727
  Access Endpoint The COR is administered so that only an administered connection (AC) endpoint can be connected to another AC endpoint. Valid entries Usage 0 to 995 Enter the appropriate class of restriction (COR) number. The COS is administered (see Class of Service on page 827) so that the use of the Call Forwarding All Calls feature for access endpoints is prohibited.
• Page 728
  1’s density digital transmission (that is, a sequence of eight digital zeros is converted to a sequence of seven zeros and a digital one) via zcs coding on DS1 circuit pack. Name Enter an name for the endpoint. 728 Administrator Guide for Avaya Communication Manager…
• Page 729
  Access Endpoint Note: Avaya BRI stations support ASCII characters only. They do not support Note: non-ASCII characters, such as Eurofont or Kanafont. Therefore, if you use non-ASCII characters in any Communication Manager Name field, such characters will not display correctly on a BRI station.
• Page 730
  Valid entries Usage 2 to 31 Enter the number of adjacent DS0 ports beginning with the specified Starting Port, that make up the WAE. A width of 6 defines a 384 Kbps WAE. 730 Administrator Guide for Avaya Communication Manager…

• Page 731: Administered Connection

  The AC is established automatically by the system whenever the system restarts or the AC is due to be active. See «Administered Connections» in Feature Description and Implementation for Avaya Communication Manager, 555-245-205, and Access Endpoint on page 725 for additional information.

• Page 732
  This endpoint is the terminating party of the AC and need not be local to the server on which the AC is assigned. The entry must be consistent with the local Communication Manager server’s dial plan (that is, the first digits are assigned as an extension, feature access code, or trunk access code, or DDD Number).
• Page 733
  7404D or 7406D telephone ● 510D personal terminal ● 515 BCT, 615 BCT, or 715 BCT terminal ● Connection between PC and the server running Avaya Communication Manager ● ISDN-BRI Line circuit pack connections, including: 7500 data module ● 7505D/7506D/7507D telephone with ADM ●…
• Page 734
  Valid entries Usage 00:00 through 23:59 Enter the time of the day when an attempt should begin to establish a scheduled AC. The time is specified in two fields separated by a colon. 734 Administrator Guide for Avaya Communication Manager…
• Page 735
  Administered Connection Miscellaneous Parameters Alarm Threshold Only appears if an entry in the Alarm Type field is other than none. Enter the number of times an attempt to establish or reestablish an AC must fail consecutively before an AC alarm generates.
• Page 736
  1 to 8 1 is the highest and 8 the lowest priority. Retry Interval Valid entries Usage 1 to 60 Enter the number of minutes between attempts to establish or reestablish the AC. 736 Administrator Guide for Avaya Communication Manager…

• Page 737: Agent Loginid

  Call Distribution) environments, this screen does not appear at all, and agents are assigned directly on the Hunt Group screen. The agent’s properties are assigned to the physical telephone extension. For more information, see Avaya Call Center Release Automatic Call Distribution (ACD) Guide, 07-300478.

• Page 738
  — all calls terminated to this agent receive an audible ringing treatment. This is the ● default. station — auto answer for the agent is controlled by the auto answer field on the Station ● screen. 738 Administrator Guide for Avaya Communication Manager…
• Page 739
  Handling Preference field. Enter y if you want direct agent calls to override the percent-allocation call selection method and be delivered before other ACD calls. Enter n if you want direct agent calls to be treated like other ACD calls. For more information, see the Avaya Business Advocate User Guide, 07-300336.
• Page 740
  — ACW timeout does not apply to this agent. ● 30-9999 sec — Indicates a specific timeout period. This setting will take precedence over ● the system setting for maximum time in ACW. 740 Administrator Guide for Avaya Communication Manager…
• Page 741
  Administering Unicode display on page 199. Avaya BRI stations support ASCII characters only. They do not support non-ASCII characters, such as Eurofont or Kanafont. Therefore, if you use non-ASCII characters in any Communication Manager Name field, such characters will not display correctly on a BRI station.
• Page 742
  __ _ __ ___ 44: __ _ __ ___ 59: __ _ __ ___ 15. __ _ __ ___ __ _ __ ___ 45: __ _ __ ___ 60: __ _ __ ___ 742 Administrator Guide for Avaya Communication Manager…
• Page 743
  Percent allocation delivers a call from the skill that will otherwise deviate most from its administered allocation. Percent-allocation is available only with Avaya Business Advocate software. For more information, see the Avaya Business Advocate User Guide, 07-300336.
• Page 744
  Assigning a large number of skills to agents can potentially impact system performance. ● Review system designs with the ATAC when a significant number of agents have greater than 20 skills per agent. 744 Administrator Guide for Avaya Communication Manager…

• Page 745: Alias Station

  Alias Station Alias Station This screen allows you to configure the system so that you can administer new telephone types that are not supported by your system software. This screen maps new telephone models to a supported telephone model. This mapping does not guarantee compatibility, but allows nonsupported models to be administered and tracked by their own names.

• Page 746
  Telephones on page 1477. Note: Data Communication Protocol (DCP) telephone types must be aliased to DCP Note: telephone types, hybrid types to hybrid types, and analog to analog types. 746 Administrator Guide for Avaya Communication Manager…

• Page 747: Alphanumeric Dialing Table

  Alphanumeric Dialing Table Alphanumeric Dialing Table This screen associates alpha-names to dialed digit strings. This allows telephone users to place a data call by simply typing the alpha-name. Users need only remember far-end alpha-names instead of the actual digit strings. The screen consists of paired Alpha-name/Mapped String fields.

• Page 748
  Delimiters consisting of both readability and special characters are used to separate tokens of «alpha-names» or numeric sub-strings. For example, «(205) mt-1234+0000» «,» space Each treated as a numeric Treated as a readability character 748 Administrator Guide for Avaya Communication Manager…

• Page 749: Announcements/Audio Sources

  Announcements/Audio Sources Announcements/Audio Sources Use this screen to assign announcements to circuit packs and port locations. Field descriptions for page 1 Figure 297: Announcements/Audio Sources screen change announcements Page 1 of X ANNOUNCEMENTS/AUDIO SOURCES Ann. Group/ Ext. Type Name Q QLen Pr Rt Port ________ _________ ________________________ _ _ __ _____…

• Page 750
  (where aa = the cabinet number, x = the carrier, and ss = the slot number). gggv9 for media gateway vVAL, where ggg is the gateway number of the media gateway ● (up to 250). 750 Administrator Guide for Avaya Communication Manager…
• Page 751
  Names on a single VAL circuit pack must be unique. The system checks for duplicate filenames on the same VAL circuit pack. NOTE: Avaya BRI stations support ASCII characters only. They do not support non-ASCII characters, such as Eurofont or Kanafont.
• Page 752
  Each call remains connected until the requesting feature operation removes the call (for example, wait step times out). Barge-in type announcements never select another port to play the same announcement once it is playing on a specific port. 752 Administrator Guide for Avaya Communication Manager…
• Page 753
  1 hour and 24 minutes for 10 circuit packs for the TN750; for the ISSPA, there are 240 minutes of storage time). This rate does not provide a high-quality recording. Avaya does not recommend this for customer announcements, but it is adequate for VDN of Origin announcements.
• Page 754
  Provides a disconnect to stop playback when the announcement is done. Callers do not hear a click when the device hangs up. integrated Stored internally on the Avaya DEFINITY or media server on a special integrated announcement circuit pack. Use for general announcements and VDN of Origin Announcements.

• Page 755: Ars Toll Table

  ARS Toll Table ARS Toll Table This screen assigns ARS Toll Tables used by Subnet Trunking. Use it to specify whether calls to CO codes listed on the table are toll or non-toll calls. You specify non-toll calls based on the last 2 digits of the distant-end of the trunk group.

• Page 756: Attendant Console

  Security Code: COS: 1 Display Language: english H.320 Conversion? n DIRECT TRUNK GROUP SELECT BUTTON ASSIGNMENTS (Trunk Access Codes) Local Remote Local Remote Local Remote 1: 9 2: 82 HUNDREDS SELECT BUTTON ASSIGNMENTS 756 Administrator Guide for Avaya Communication Manager…

• Page 757
  Attendant Console Attendant Console x This is a display-only field when the screen is accessed using an administration command such as add or change. Auto Answer Valid entries Usage Entering all indicates an incoming call to an idle attendant will be answered automatically without any action (no button presses required) by the attendant.
• Page 758
  Hospitality screen) displays. Display Language Enter the language in which you want console messages displayed. Valid entries Usage English Enter the language in which you want messages to be displayed. French 758 Administrator Guide for Avaya Communication Manager…
• Page 759
  Attendant Console Valid entries Usage Italian Spanish user-defined Unicode Unicode display is only available for Unicode-supported telephones. Currently, only the 4610SW, 4620SW, 4621SW, and 4622SW support Unicode display. Extension (Optional) Enter the extension for the individual attendant console. Individual attendant extensions allow attendants to use features that an attendant group cannot use.
• Page 760
  System-Parameters Customer-Options screen, the IP Attendant Consoles field is y. Indicates that there is no hardware associated with the port assignment. An individual attendant extension must be assigned in the Extension field. 760 Administrator Guide for Avaya Communication Manager…
• Page 761
  If a remote TAC is given, then the local TAC must see a trunk group that connects directly to the remote server running Avaya Communication Manager and is also limited to 1 to 3 digits.
• Page 762
  Screen Reference Avaya recommends a DCS trunk be specified as the local TAC between the local and remote servers. If the TAC specified as local between the local and remote servers is not a DCS trunk, the remote trunk cannot be monitored by the local server running Avaya Communication Manager.
• Page 763
  Attendant Console Always Use This field does not apply to SCCAN wireless telephones, or to extensions administered as type h.323. Valid entries Usage When this field is y: The Remote Softphone Emergency Calls field is hidden. A ● softphone can register no matter what emergency call handling settings the user has entered into the softphone.
• Page 764
  Communication Manager TDM bus. Default is n. Remote Softphone Emergency Calls Use this field to tell Communication Manager how to handle emergency calls from the IP telephone. This field appears when the IP Softphone field is set to y on the Station screen.
• Page 765
  911 from a nearby circuit-switched telephone instead. cesid Enter cesid to allow Communication Manager to send the CESID information supplied by the IP Softphone to the PSAP. The end user enters the emergency information into the IP Softphone.
• Page 766
  The BCC value is used to determine compatibility when non-ISDN facilities are Note: connected to ISDN facilities (ISDN Interworking feature). Valid entries Usage 0 to 995 Enter the desired class of restriction (COR) number. 766 Administrator Guide for Avaya Communication Manager…
• Page 767
  Enter the name of the user associated with the data module. The name is optional; it can be left blank. Note: Avaya BRI stations support ASCII characters only. They do not support Note: non-ASCII characters, such as Eurofont or Kanafont. Therefore, if you use non-ASCII characters in any Communication Manager Name field, such characters will not display correctly on a BRI station.

• Page 768: Abbreviated Dialing

  Group (TEG) extension, or any individual extension within a group can be a Hot Line Service destination. Also, any extension within a DDC group, UDC group, or TEG can have Hot Line Service assigned. 768 Administrator Guide for Avaya Communication Manager…

• Page 769
  Attendant Console Use Hot Line Service when very fast service is required and when you use a telephone only for accessing a certain facility. Loudspeaker Paging Access can be used with Hot Line Service to provide automatic access to paging equipment. Valid entries Usage A dial code…
• Page 770
  Incoming call ringer off; turns on/off the audible tone for incoming call ringer (1 per console). re-ringoff Timed reminder ringer off; turns on/off the audible tone for timer reminder ringer (1 per console). 1 of 4 770 Administrator Guide for Avaya Communication Manager…
• Page 771
  Attendant Console Valid entries Usage alt-frl Alternate FRL. Alternate facility restriction level; allows the attendant to activate or deactivate the AFRL feature. When activated, this allows the originating device (lines or trunks) to use an alternate set of the facility restriction levels to originate a call (1 per console).
• Page 772
  DTGS buttons can be administered as follows: local-tgs Local trunk group select; allows the attendant to access trunk groups on the local server running Avaya Communication Manager (combination of 12 local-tgs/remote-tgs per console). remote-tgs Remote trunk group select; allows the attendant to access trunk groups on a remote server running Avaya Communication Manager (combination of 12 local-tgs/remote-tgs per console).
• Page 773
  VuStats feature button. 4 of 4 If 12 HGS buttons are assigned on field descriptions for page 2, Avaya recommends that ● the night, pos-busy, and hold buttons be reassigned to locations 20, 21, and 3, respectively.

• Page 774: Audio Group

  Figure 304: Audio Group screen add audio-group next Page 1 of x Audio Group 2 Group Name: AUDIO SOURCE LOCATION Audio Source Location Enter the board location for this audio group: cabinet(1-64):carrier(A-E):slot(1-20):OR gateway(1-250):module(V1-V9). 774 Administrator Guide for Avaya Communication Manager…

• Page 775: Audix-Msa Node Names

  Group Name Enter an alpha-numeric name of the audio group for identification. Note: Avaya BRI stations support ASCII characters only. They do not support Note: non-ASCII characters, such as Eurofont or Kanafont. Therefore, if you use non-ASCII characters in any Communication Manager Name field, such characters will not display correctly on a BRI station.

• Page 776: Authorization Code — Cor Mapping

  You use this screen to assign authorization codes and the class of restriction (COR) that is associated with a given authorization code. See «Authorization Codes» and «Class of Restriction» in Feature Description and Implementation for Avaya Communication Manager, 555-245-205, for more information on how Authorization Codes work with COR.

• Page 777
  Authorization Code — COR Mapping Field descriptions for page 1 Figure 306: Authorization Code — COR Mapping screen change authorization-code Page 1 of x Authorization Code — COR Mapping Note: XX codes administered. Use «list» to display all codes. _______ __ _______ __ _______ __ _______ __…

• Page 778: Best Service Routing

  This screen administers the routing numbers for each location associated with a particular application. This allows the Avaya DEFINITY server or media server to compare specified skills, identify the skill that will provide the best service to a call, and deliver the call to that resource.

• Page 779
  0 to 9, *, #, When a given remote Avaya server is the best available, the origin Avaya server interflows the call to this vector on the remote server. Each ~p (pause) remote Avaya server in a given application has to have a dedicated ~w/~W (wait) interflow server.
• Page 780
  This field specifies the AAR or ARS pattern that routes over an IP trunk. The status poll vector on the remote Avaya server compares resources on that server and replies to the origin server 780 Administrator Guide for Avaya Communication Manager…

• Page 781: Bulletin Board

  The first page has 19 lines, but you can only enter text on lines 11 to 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.

• Page 782
  If you have an init or inads login you can enter high-priority information to trigger the high-priority message at login time. Valid entries Usage A to Z Enter any information. a to z Blank 0 to 9 !@#$%^&*()_+-=[]{}|’˜;:’,»<.>/? 782 Administrator Guide for Avaya Communication Manager…
• Page 783
  Bulletin Board Lines 11 through 19 These lines can be used by anyone with access. Valid entries Usage A to Z Enter any information. a to z Blank 0 to 9 !@#$%^&*()_+-=[]{}|’˜;:’,»<.>/? Field descriptions for pages 2 and 3 Date This display only field contains the date the information was entered or last changed.

• Page 784: Button Type Customization Restrictions

  ____________ ____________ ____________ ____________ ____________ ____________ ____________ ____________ ____________ ____________ ____________ ____________ Caution: Adding new button types to this list will cause all button labels associated with that button type to be lost 784 Administrator Guide for Avaya Communication Manager…

• Page 785
  Button Type Customization Restrictions Restrict Customization Of Button Types Use this field to enable/disable restriction of feature button label customization. Valid entries Usage Enter y to enable restriction of feature button label customization. This is the default. When you enter n in this field, users have the capability to customize labels for all buttons on their telephones.

• Page 786: Call Vector

  Call Vector This screen programs a series of commands that specify how to handle calls directed to a Vector Directory Number (VDN). See Avaya Call Center Release Call Vectoring and Expert Agent Selection (EAS) Guide, 07-300477, for additional information. Field descriptions for page 1…

• Page 787
  Voice Response Unit (VRU). disconnect Ends treatment of a call and removes the call from the server running Avaya Communication Manager. Also allows the optional assignment of an announcement that will play immediately before the disconnect. goto Allows conditional or unconditional movement (branching) to a preceding or subsequent step in the vector.
• Page 788
  A display-only field indicating whether, on the System-Parameters Customer-Options screen, the Vectoring (CINFO) field is y. A display-only field indicating whether, on the System-Parameters Customer-Options screen, the Expert Agent Selection (EAS) field is y. 788 Administrator Guide for Avaya Communication Manager…
• Page 789
  Vectoring (Holidays) field is y. A display-only field indicating whether Look-Ahead Interflow is enabled. Lock This field controls access to the vector from Avaya CentreVu products. Note: Always lock vectors that contain secure information (for example, access codes).
• Page 790
  See Managing MultiMedia Calling on page 321 for more information. 790 Administrator Guide for Avaya Communication Manager…
• Page 791
  For more information on Unicode language display, see Administering Unicode display on page 199. Avaya BRI stations support ASCII characters only. They do not support non-ASCII characters, such as Eurofont or Kanafont. Therefore, if you use non-ASCII characters in any Communication Manager Name field, such characters will not display correctly on a BRI station.

• Page 792: Cama Numbering Format

  _______ ________________ _______ _____________ _______ ________________ _______ _____________ _______ ________________ _______ _____________ _______ ________________ _______ _____________ _______ ________________ _______ _____________ _______ ________________ _______ _____________ _______ ________________ _______ _____________ _______ ________________ _______ _____________ _______ ________________ 792 Administrator Guide for Avaya Communication Manager…

• Page 793
  CAMA Numbering Format CESID Valid entries Usage 1 to 11 digits or blank Enter the number that will be used to identify the calling terminal within an emergency service system. This field 1 to 16 digits or blank (S8300 can represent a prefix to an extension or the entire Media Server, S8700 Series CESID.

• Page 794: Capacities

  The System Capacity screen (command display capacity) is described in Maintenance Commands for Avaya Communication Manager, Media Gateways and Servers, 03-300431. Detailed system capacity information can be found in System Capacities Table for Avaya Communication Manager on Avaya Media Servers, 03-300511.

• Page 795
  Condition Code ‘T’ for Redirected Calls You can elect to identify CDR records of calls that have been redirected automatically off the server running Avaya Communication Manager. Valid entries Usage The Condition Code of both CDR records for the call will be ‘T.’…
• Page 796
  Use dialed to record the digits a user actually dials. outpulsed Use outpulsed to record the digits that Communication Manager actually sends out over the trunk, including any additions or deletions that take place during routing. Disconnect Information in Place of FRL…
• Page 797
  Intra-Switch CDR Valid entries Usage Enter y to record calls within Avaya Communication Manager. If you choose this option, you must complete the Intra-switch CDR screen to indicate which extensions should be monitored. Modified Circuit ID Display This affects the «printer,» «teleseer,» and «59-character» output formats.
• Page 798
  Enter y to create separate records for each portion of outgoing calls that are transferred or conferenced. Primary Output Endpoint This field determines where the server running Avaya Communication Manager sends the CDR records, and is required if you specify a Primary Output Format. Valid entries Usage If you use the EIA port to connect the CDR device, enter eia.
• Page 799
  CDR System Parameters Primary Output Format Controls the format of the call records sent to the primary output device. Valid entries Usage customized Use this option if you have special call accounting needs that standard record formats do not accommodate. If you use a customized record format, you need to have call accounting software that is also customized to receive these records.
• Page 800
  Enter y to create records for non-call-associated temporary signaling connections. If you have a lot of data connections this could increase the number of records. You might want to consider the capacity of your record collection device. 800 Administrator Guide for Avaya Communication Manager…
• Page 801
  This is the extension of the data module (if used) that links the secondary number output device to the server running Avaya Communication Manager. CDR1, CDR2 Use this value if the CDR device is connected over a TCP/IP link, and this link is defined as either CDR1 or CDR2 on the IP Services screen.
• Page 802
  ISDN Call-by-Call Service Selection trunks, incoming calls rejected by Communication Manager due to NSF mismatch, and ISDN calls that did not complete at the far end, if a cause value was provided. These calls appear on the CDR record with a condition code «E.»…
• Page 803
  CDR System Parameters Use Enhanced Formats Enhanced formats provide additional information about time in queue and ISDN call charges, where available. This affects the «expanded,» «teleseer,» «lsu,» «printer,» and «unformatted» output formats. Valid entries Usage Enter y to enable the use of the Enhanced version of the specified primary output format.
• Page 804
  The last two data items in a the record must be line-feed and return, in that order. For more information, see «Call Detail Recording» in Feature Description and Implementation for Avaya Communication Manager, 555-245-205. Data Item Length Data Item Length acct-code ixc-code attd-console line-feed 1 of 2 804 Administrator Guide for Avaya Communication Manager…
• Page 805
  CDR System Parameters Data Item Length Data Item Length auth-code location-from bandwidth location-to in-trk-code calling-num ma-uui clg-pty-cat node-num clg-num/in-tac location-to code-dial null code-used out-crt-id cond-code country-from res-flag country-to return dialed-num sec-dur duration space feat-flag time timezone-from in-crt-id timezone-to tsc_ct isdn-cc tsc_flag 2 of 2 Length…

• Page 806: Change Station Extension

  CHANGE STATION EXTENSION Station Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Port: xxxxxx FROM EXTENSION TO EXTENSION ————— ————- Station: xxx-xxxx xxx-xxxx Message Lamp: xxx-xxxx xxx-xxxx Emergency Location Ext.: xxx-xxxx xxx-xxxx IP Parameter Emergency Location: xxx-xxxx See IP-Network Map Form 806 Administrator Guide for Avaya Communication Manager…

• Page 807
  Change Station Extension Note: You cannot use the change extension-station command to change the Note: extension of a station if that station is administered as the emergency location extension for another station. For example, if station A is administered as the emergency location extension for station B, then: You cannot change the extension of station A using the change ●…
• Page 808
  This field is read only, and displays the name of the existing extension (the extension that was typed in the change extension-station xxxxxxx command). Note: Avaya BRI stations support ASCII characters only. They do not support Note: non-ASCII characters, such as Eurofont or Kanafont. Therefore, if you use non-ASCII characters in any Communication Manager Name field, such characters will not display correctly on a BRI station.

• Page 809: Circuit Packs

  Circuit Packs Circuit Packs This screen is described in Maintenance Commands for Avaya Communication Manager, Media Gateways and Servers, 03-300431. Class of Restriction Use this screen to establish classes of restriction (COR). Classes of restriction control call origination and termination. Your system might use only one COR or as many as necessary to control calling privileges.

• Page 810
  Entering n prohibits this user from requesting a malicious call trace, but does not prevent this extension from appearing in the MCT History report, should this extension be the subject of a malicious call trace. 810 Administrator Guide for Avaya Communication Manager…
• Page 811
  If fully restricted service is enabled, set this field to n. Automatic Charge Display Shows the cost of an active outgoing call using Periodic Pulse Metering (PPM) or ISDN Advice of Charge (AOC) on Digital Communications Protocol (DCP) or Avaya BRI stations. Not available in the U.S Valid entries Usage Displays call charges during and at the end of the call.
• Page 812
  Outward Blocks the calling party from calling outside the private network. Users can dial other users on the same server running Avaya Communication Manager or within a private network. To enhance security, Avaya recommends that you use outward restrictions when practical.
• Page 813
  Class of Restriction Note: You cannot enter y in the previous two fields unless Service Observing (Basic) Note: is enabled on the System-Parameters Customer-Options screen. Valid entries Usage Enter y if users with this COR can service observe other users. Can Be Picked Up By Directed Call Pickup Valid entries Usage…
• Page 814
  Department), it will be easier to remember which COR to assign when you add users. COR Number This is a display-only field when the screen is accessed via an administration command such as change or display. Displays the COR number. 814 Administrator Guide for Avaya Communication Manager…
• Page 815
  Class of Restriction Direct Agent Calling Valid entries Usage If this is y, users can dial an ACD agent’s extension directly, rather than anyone in the agent pool. If the system is in Night Service, the call routes to the Night Service extension. If the extension with this COR belongs to an agent, the agent can receive calls directly.
• Page 816
  Valid entries Usage 1 to 10 Enter the value you want the server running Avaya Communication Manager to send as the Calling and/or Called Party Category for telephones or trunks that use this COR. 816 Administrator Guide for Avaya Communication Manager…
• Page 817
  ANI prefix administered on the Multifrequency Signaling screen. This does not apply when ANI is tandemed through the Communication Manager server on tandem calls. This field also applies to the ANI for the server when the originating side is a trunk and there was no ANI.
• Page 818
  RCL, will be denied. Valid entries Usage Enter y to specify that this COR will have access to the system’s Restricted Call List (see Toll Analysis on page 1590). 818 Administrator Guide for Avaya Communication Manager…
• Page 819
  Valid entries Usage Enter y to enable Automatic Number Identification (ANI). When the value is y, Avaya Communication Manager sends the calling party’s number to the public or IBERCOM network so that charges will be broken down by line. If this value is n, charges are not itemized by line, and your company will receive a single bill for the total number of calls made (block charging).
• Page 820
  This field appears only if, on the Multifrequency-Signaling-Related System Parameters screen, the Outgoing Call Type field is group-ii-mfc. Valid entries Usage Entering y allows the COR administered category to be used for both the calling party and called party categories. 820 Administrator Guide for Avaya Communication Manager…
• Page 821
  Class of Restriction Field descriptions for page 2 Figure 316: Class of Restriction screen (page 2) change cor nn Page 2 of x CLASS OF RESTRICTION MF Incoming Call Trace? n Brazil Collect Call Blocking? n Block Transfer Display? n Block Enhanced Conference/Transfer Displays? y Remote Logout of Agent? n Station Lock COR: 10…
• Page 822
  MF Incoming Call Trace Valid entries Usage Enter y to allow assignment of a Call Trace COR to a station. Avaya Communication Manager then generates an MFC backward signal (administered on the System-Parameters Multifrequency-Signaling screen) during call setup instead of the «free» signal. This triggers the central office to collect trace information before releasing the calling party, if the terminating station’s COR has this feature set to y.
• Page 823
  Class of Restriction MLPP Service Domain Valid entries Usage 1 to 16777215 Enter the service domain for users and trunks to which this particular COR is assigned. Preemptable Valid entries Usage An entry of y makes extensions with this COR preemptable for Multiple Level Precedence and Preemption calls.
• Page 824
  30 seconds later. The call is automatically disconnected 30 seconds after the second warning tone. Field descriptions for page 3 to 12 Use pages 3 to 12 to assign up to 995 CORs. 824 Administrator Guide for Avaya Communication Manager…
• Page 825
  Class of Restriction Figure 317: Class of Restriction screen (page 3) change cor nn Page 3 of x CLASS OF RESTRICTION CALLING PERMISSION (Enter y to grant permission to call specified COR) 0? n 15? n 30? n 44? n 58? n 72? n 86? n…
• Page 826
  29? n SERVICE OBSERVING PERMISSION Valid entries Usage A y grants permission to observe specific CORs. Enter n for each COR number (0 through 95) that cannot be observed by the COR being implemented. 826 Administrator Guide for Avaya Communication Manager…

• Page 827: Class Of Service

  Class of Service Class of Service This screen administers access permissions for call processing features that require dial code or feature button access. Note: Class of Service (COS) does not apply to trunk groups except for the Remote Note: Access feature. A COS assignment defines whether or not a telephone user can access or use the following features and functions.

• Page 828: Automatic Callback

  Screen Reference Automatic Callback Allows this user to request Automatic Callback. See «Automatic Callback» in Feature Description and Implementation for Avaya Communication Manager, 555-245-205, for more information. Automatic Exclusion Allows a user to activate automatically Exclusion when they go off hook on a station that has an assigned Exclusion button.

• Page 829: Priority Calling

  Admin on the System Parameters Customer-Options screen is n. Off-Hook Alert See «Emergency Access to the Attendant» in Feature Description and Implementation for Avaya Communication Manager, 555-245-205, for more information. To enable this option, either the Hospitality (Basic) or Emergency Access to Attendant field must be enabled in your license file.

• Page 830
  This restricts users from forwarding calls to the public network. For security reasons, this should be enabled for all classes of service except the ones you use for very special circumstances. See «Call Forwarding Off-net» in Feature Description and Implementation for Avaya Communication Manager, 555-245-205, for more information…

• Page 831: Code Calling Ids

  Code Calling IDs Code Calling IDs On systems with chime paging, use this screen to assign a unique series of chimes (a chime code) to extensions. The chime code assigned to an extension plays over the speakers whenever that extension is paged. You can assign chime codes to up to 125 extensions. Field descriptions for page 1 Figure 321: Code Calling IDs screen change paging code-calling-ids…

• Page 832: Command Permission Categories

  Related topics Setting up Chime Paging Over Loudspeakers on page 501 for instructions. See «Loudpeaker Paging» in Feature Description and Implementation for Avaya Communication Manager, 555-245-205, for more information for a description of the feature. Command Permission Categories Use this screen to administer a user’s permissions associated with their login. When set to y, the permissions on this screen apply for the object that is not restricted.

• Page 833
  Command Permission Categories Additional Restrictions Use page 2 and 3 to add objects (up to 40) that this user cannot manipulate. If an object appears on the Additional Restrictions page, users cannot display, add, change, or do anything else with that object. Valid entries Usage Enter y to create additional restrictions, and to have the second and third…
• Page 834
  You can only enter a value in this field if the Processor and System MSP field is set to y on the System-Parameters Customer-Options screen. Valid entries Usage Enter y to allow a user to perform processor maintenance. 834 Administrator Guide for Avaya Communication Manager…
• Page 835
  Command Permission Categories Maintain Stations You can only enter a value in this field if the Station and Trunk MSP field is set to y on the System-Parameters Customer-Options screen. Valid entries Usage Enter y to allow a user to perform station maintenance. Maintain Switch Circuit Packs You can only enter a value in this field if the Station and Trunk MSP field is set to y on the System-Parameters Customer-Options…
• Page 836
  Screen Reference System Mgmt Data Transfer Only Valid entries Usage Enter y to indicate the server running Avaya Communication Manager is accessible by Network Administration. Field descriptions for page 2 Figure 323: Command Permission Categories screen change permissions nnnn Page 2 of x…

• Page 837: Communication Interface Processor Channels

  Communication Interface Processor Channels Communication Interface Processor Channels Processor Channel Assignment. Configuration Set This screen defines a number of call treatment options for Extension to Cellular cell telephone calls. The Extension to Cellular allows the use of up to 10 Configuration Sets, which are already defined in the system using default values.

• Page 838
  Screen Reference Calling Number Style Determines the format of the caller ID for calls from a local Avaya Communication Manager extension to an Extension to Cellular telephone. Valid entries Usage network Provides a display of only 10-digit numbers. For internal calls, the ISDN numbering tables are used to create the calling number and DCS calls use the ISDN calling number if provided.
• Page 839
  Configuration Set CDR for Calls to EC500 Destination Determines whether a call detail record is generated for any call to the cell telephone. Note: CDR reporting for Extension to Cellular calls relies on the CDR Reports field on Note: the Trunk Group screen. If, on the Trunk Group screen, the CDR Reports field is n, no CDR is generated even if this field is y.
• Page 840
  Communication Manager treats the call as a normal call to the office phone and the call goes to corporate voice mail. You can also set a timer for cellular voice mail detection that sets a time before Cellular Voice Mail Detection investigates a call.
• Page 841
  Determines whether additional capabilities, beyond standard ISDN dialing, are available for those incoming ISDN trunk calls that are mapped into XMOBILE stations. These options come into effect after the call has entered the active state (Communication Manager has sent a CONNECT message back to the network).

• Page 842: Console Parameters

  Valid entries Usage 0 to 9, *, # Enter up to 4 digits. blank Alternate FRL Station This is a display-only field indicating the extension of the alternate facility restriction level (FRL) activation station. 842 Administrator Guide for Avaya Communication Manager…

• Page 843
  Console Parameters Attendant Group Name Valid entries Usage 1 to 27 Enter a name for the attendant group. alphanumeric characters Attendant Lockout Attendant Lockout prevents an attendant from re-entering a multiple-party connection held on the console unless recalled by a telephone user. Attendant Lockout provides privacy for parties on a multiple-party call held on the console.
• Page 844
  Centralized Attendant field is y. Indicates all attendants are located on the main PBX. QSIG-branch Can be used if, on the System-Parameters Customer-Options screen, the Centralized Attendant field is y. Indicates there are no local attendants and routes to the main PBX. 844 Administrator Guide for Avaya Communication Manager…
• Page 845
  For more information about Class of Restriction (COR), see Feature Description and Implementation for Avaya Communication Manager, 555-245-205. Valid entries Usage 0 to 995 Enter the class of restriction (COR) number that reflects the desired features for the attendant.
• Page 846
  IAS Att. Access Code Enter the extension number of the attendant group at the main server running Avaya Communication Manager. This entry is required when IAS Branch is y. Does not appear if, on System-Parameters Customer-Options screen, the Centralized Attendant field is y.
• Page 847
  Appears if the CAS field is QSIG-branch. Contains the complete number of the attendant group at the main server running Avaya Communication Manager, or a vector directory number (VDN) local to the branch server. This field cannot be left blank…
• Page 848
  Time In Queue Warning (sec) Valid entries Usage 9 to 999 or blank Enter the number of seconds a call can remain in the attendant queue before activating an alert. 848 Administrator Guide for Avaya Communication Manager…
• Page 849
  Console Parameters Time Reminder on Hold (sec) Valid entries Usage 10 to 1024 Enter the number of seconds a call can remain on Hold. INCOMING CALL REMINDERS Alerting (sec) Enter the number of seconds after which a held or unanswered call is disconnected from an attendant loop and routed to another attendant or night service No Answer Timeout (sec) Enter the number of seconds a call to the attendant can remain unanswered without invoking a…
• Page 850
  Busy Indicator for Call Parked on Analog Station Without Hardware? Valid entries Usage Enter y to indicate that the Busy Indicator lamp will light for incoming calls parked on AWOH stations. Default is n. 850 Administrator Guide for Avaya Communication Manager…
• Page 851
  Console Parameters Count Enter a number to indicate the number of consecutive extensions, beginning with the Start Extension to be used as common, shared extensions. For example, if you enter a starting extension of 4300 and a count of 3, the system provides three consecutive extension numbers (4300, 4301, and 4302) for parking calls.
• Page 852
  (if applicable), or Number Unobtainable and reroutes to the attendant group. Redirected Call — A call assigned to one attendant, but redirected to the attendant group ● because the attendant is now busy 852 Administrator Guide for Avaya Communication Manager…
• Page 853
  Console Parameters Return Call — A call returned to the attendant after it times out. If the attendant is now ● busy, the call redirects to the attendant group. Serial Call — A call from the Attendant Serial Call feature when an outside trunk call ●…
• Page 854
  Enter the queue priority for Flash precedence level calls. Immediate Valid entries Usage 1 to 17 Enter the queue priority for Immediate precedence level calls. Priority Valid entries Usage 1 to 17 Enter the queue priority for Priority precedence level calls. 854 Administrator Guide for Avaya Communication Manager…
• Page 855
  Console Parameters Field descriptions for page 5 Note: If MLPP is not enabled, the MLPP Queues page does not appear, and the Note: following page appears as page 4. Figure 329: Console Parameters — Default Attendant Group screen change console-parameters Page 5 of x CONSOLE PARAMETERS ASSIGNED MEMBERS ( Installed attendant consoles )

• Page 856: Coverage Answer Group

  Each coverage answer group is identified by a number from 1 through the maximum number allowed by your system configuration (see Hardware Description and Reference for Avaya Communication Manager, 555-245-207). The members of the group are identified by their extension number. Any telephone, including those administered without hardware (X-ported (but not attendants) can be assigned to a coverage answer group.

• Page 857
  This display-only field indicates the name assigned when the member’s telephone is administered. Note: Avaya BRI stations support ASCII characters only. They do not support Note: non-ASCII characters, such as Eurofont or Kanafont. Therefore, if you use non-ASCII characters in any Communication Manager Name field, such characters will not display correctly on a BRI station.

• Page 858: Coverage Path

  COVERAGE POINTS Terminate to Coverage Pts. with Bridged Appearance? n Point1: _________ Point2: _________ Point3: _________ Point4: _________ Point5: _________ Point6: _________ Coverage Path Number A display-only field indicating the coverage path being administered. 858 Administrator Guide for Avaya Communication Manager…

• Page 859: Holiday Table

  Coverage Path Holiday Coverage This field determines when to redirect call to coverage for an inside or outside call. Valid entries Usage Type y to send the call to an announcement. Type n to send the call to the next point in the coverage path. Holiday Table This field determines when to redirect call to coverage for an inside or outside call.

• Page 860
  Enter the next coverage path in a coverage path chain. See «Call Coverage» in Feature Description and Implementation for Avaya Communication Manager, 555-245-205, for more information If the coverage criteria of the current coverage path is not satisfied, the system steps down this chain until it finds a coverage path with redirection criteria that matches the call status.
• Page 861
  Coverage Path Number of Rings Enter the number of rings. Valid entries Usage 1 to 99 This is the number of rings a user’s telephone rings before the system redirects the call to the first point in the coverage path. COVERAGE POINTS Point1, Point2, Point3, Point4, Point5, Point6 The alternate destinations that comprise a coverage path.
• Page 862
  Terminate to Coverage Pts. with Bridged Appearances Valid entries Usage Allows a call to alert as both a bridged call and a redirected call. The call skips the coverage point if it has already alerted as a bridged call. 862 Administrator Guide for Avaya Communication Manager…

• Page 863: Crisis Alert System Parameters

  Crisis Alert System Parameters Crisis Alert System Parameters This screen allows you to define the system parameters associated with sending crisis alert messages. Field descriptions Figure 332: Crisis Alert System Parameters screen change system-parameters crisis-alert page 1 of x CRISIS ALERT SYSTEM PARAMETERS ALERT STATION Every User Responds? n ALERT PAGER…

• Page 864: Alert Station

  1 through 3 digits The numbers in this field are the first 3 digits in the crisis alert pager message. Avaya recommends you enter the numbers used to call the local emergency service or any digits used for an emergency situation (for example, 911).

• Page 865: Dtmf Duration — Tone (Msec)

  Crisis Alert System Parameters DTMF Duration — Tone (msec) The length of time the Dual-Tone Multi-Frequency (DTMF) tone is heard for each digit. Displays when the Alert Pager field is y. Valid entries Usage 20 to 2550 Enter a number in increments of 10. Main Number The main telephone number to the location or a location code.

• Page 866
  Displays when the Alert Pager field is y. This field is not used unless the Retries field is 1 to 10. Valid entries Usage 30 to 60 The administrable time period (in seconds) between retries. If an attempt to call the pager fails, the retry call attempts after the retry interval period. 866 Administrator Guide for Avaya Communication Manager…

• Page 867: Cti Link

  CTI Link CTI Link The cti-link commands are available only if, on the System-Parameters Customer-Options screen, either the ASAI Link Core Capabilities and/or Computer Telephony Adjunct Links field is y. Field descriptions for page 1 Figure 333: CTI Link screen when Type field is ASAI or ADJLK add cti-link next Page 1 of x CTI LINK…

• Page 868
  A display-only field indicating the CTI link number. Valid entries Usage 1 to system max Avaya Communication Manager on a DEFINITY Server CSI, DEFINITY G3i, S8300 Media Server, S8700 Series Multi-Connect Extension This field displays the extension for this link.
• Page 869
  CTI Link Name Enter a name associated with this CTI link. Enter a Class of Restriction (COR) number to select the desired restriction. BRI Options Appears when the Type field is ASAI or ADJLK. Used to identify Layer 2 XID testing capability. MIM Support Management Information Message Support.
• Page 870
  Station screen to change this option. The new option settings take effect the next time the ASAI link is activated. Valid entries Usage Enter y to control the behavior for that particular link. 870 Administrator Guide for Avaya Communication Manager…

• Page 871: Customer Options

  Valid entries Usage Special Character for Restricted Number Enables an ASAI CTI link to indicate the calling number restricted presentation within an event report. For further information, see Avaya Communication Manager ASAI Technical Reference, 555-230-220. Valid entries Usage When set to y and a calling number received in a SETUP message has the presentation indicator set (octet 3a in the calling number), then «*»…

• Page 872: Data Module

  Secondary data module? ITC: restricted__ TN: 1 Connected to: dte ABBREVIATED DIALING List1: SPECIAL DIALING OPTION: ASSIGNED MEMBER (Station with a data extension button for this data module) Name 1: 1002 27 character station name 872 Administrator Guide for Avaya Communication Manager…

• Page 873
  The BCC values must be the same. See «Generalized Route Selection» in Feature Description and Implementation for Avaya Communication Manager, 555-245-205, for a detailed description of Bearer Capability Classes (BCC) and their ability to provide specialized routing for various types of voice and data calls.
• Page 874
  4 to 5 Slot Number or X 0 to 20 Broadcast Address Used with Ethernet data modules. See Administration for Network Connectivity for Avaya Communication Manager, 555-233-504, for more information. Does not appear for S8700 Series IP-Connect. Connected Data Module Used with X.25 and Processor Interface (used with DEFINITY CSI only) data modules.
• Page 875
  Enable Link Used with X.25, Point-to-Point, and Processor Interface data modules. See Administration for Network Connectivity for Avaya Communication Manager, 555-233-504, for more information. This field is in different locations on the screen for different data module types. Issue 2.1 May 2006…
• Page 876
  Establish Connection Used with X.25, Point-to-Point, and Processor Interface (used with DEFINITY CSI only) data modules. See Administration for Network Connectivity for Avaya Communication Manager, 555-233-504, for more information. Highest PVC Logical Channel A display-only field used with X.25 Data Modules.
• Page 877
  Link Used with X.25, Ethernet, Point-to-Point, and Processor Interface (used with DEFINITY CSI only) data modules. See Administration for Network Connectivity for Avaya Communication Manager, 555-233-504, for more information. This field is in different locations on the screen for different data module types.
• Page 878
  Communication Manager Name field, such characters will not display correctly on a BRI station. Network uses 1’s for Broadcast Addresses Used with Ethernet data modules. See Administration for Network Connectivity for Avaya Communication Manager, 555-233-504, for more information. 878 Administrator Guide for Avaya Communication Manager…
• Page 879
  Data Module Node Name Used with Ethernet (not on S8700 Series IP-Connect) and Point-to-Point data modules. See Administration for Network Connectivity for Avaya Communication Manager, 555-233-504, for more information. PDATA Port Used with System Port Data Modules. Enter a seven-digit alphanumeric port location to which the data module is connected.
• Page 880
  (Secondary data module set to y) An x cannot be entered into this field. The port of a primary data module cannot be changed to x if a secondary data module is administered. 880 Administrator Guide for Avaya Communication Manager…

• Page 881: Subnet Mask

  Usage For Processor/Trunk Data Modules, enter y if the data module supports a loop-back test at the EIA interface. In general, Avaya equipment supports this test but it is not required by Level 2 Digital Communications Protocol. Enter n to abort a request for this test.

• Page 882
  Announcement Data Module screen. This data module allows the system to save and restore the recorded announcements file between the announcement circuit pack and the system memory. 1 of 3 882 Administrator Guide for Avaya Communication Manager…
• Page 883
  The DLC appears as a data module to the Digital Terminal Equipment (DTE) and as a digital line port to the server running Avaya Communication Manager. The DLC connects the following EIA 232C equipment to the system: Printers ●…
• Page 884
  Assigns a World Class BRI Data Module. x.25 Assigns an X.25 Data Module. See Administration for Network Connectivity for Avaya Communication Manager, 555-233-504, for more information on X.25 data modules. 3 of 3 884 Administrator Guide for Avaya Communication Manager…
• Page 885
  DESTINATION CHAP Appears when the Type field is ppp. Used with Point-to-Point data modules. See Administration for Network Connectivity for Avaya Communication Manager, 555-233-504, for more information. CHAP Secret Appears when the CHAP field is y. Used with Point-to-Point data modules. See Administration for Network Connectivity for Avaya Communication Manager, 555-233-504, for more information.
• Page 886
  Used with 7500, Data Line, Netcon, Processor/Trunk, Processor Interface, and World Class BRI Data Modules. Identifies the type of dialing for calls when this data module originates calls. Valid entries Usage hot-line default blank For regular (normal) keyboard dialing. 886 Administrator Guide for Avaya Communication Manager…
• Page 887
  These fields have no significance for data modules providing data query [all Avaya -supported ISDN-BRI data modules (7500 and ADM)]. For Avaya ISDN-BRI or World Class ISDN-BRI data modules, use the default settings. Issue 2.1 May 2006…
• Page 888
  Used with Data Line, Announcement, Netcon, Processor/Trunk, Processor Interface, and System Port Data Modules. Displays the extension number and name of the user (previously administered) with associated Data Extension buttons who shares the module. 888 Administrator Guide for Avaya Communication Manager…
• Page 889
  This mode is also used for terminating trunk calls that do not have bearer capability specified or administered connections. See «Generalized Route Selection» in Feature Description and Implementation for Avaya Communication Manager, 555-245-205, for additional information. Valid entries Usage Mode 0.
• Page 890
  The T4 timer is a system parameter that represents the time a DTE allows without frames being exchanged on the data link. Valid entries Usage 0 to 250 Enter the time a DTE allows without frames being exchanged on the data link. 890 Administrator Guide for Avaya Communication Manager…
• Page 891
  Data Module Number of Outstanding Frames (w) Specifies layer 2 window size. Valid entries Usage 1 to 7 If you enter 2, up to 2 frames can be sent without confirmation. Retransmission (T1) Timer (1/10 seconds) The T1 timer is started at the beginning or the end of the transmission of a frame. At the end of this timer, retransmission of a frame is initiated according to the procedures for link set-up and disconnection or information transfer.
• Page 892
  Dial Echoing? y Disconnect Sequence: two-breaks Answer Text? y Parity: even Connected Indication? y DLC Option Settings on page 897 for additional information when assigning entries for the remaining fields on the screen. 892 Administrator Guide for Avaya Communication Manager…
• Page 893
  Data Module CAPABILITIES Busy Out This option should be enabled for DTEs that are members of a hunt group and to allow «busy out» when DTE turns power off so that calls do not terminate on that DTE. Valid entries Usage Enter y to place the DLC port in a busied-out state once the DTE control lead to the DLC is dropped.
• Page 894
  This option usually is disabled when the answering DTE is a computer or an intelligent device. Valid entries Usage Enter y to allow text messages to be delivered to the DTE when a call is being answered. 894 Administrator Guide for Avaya Communication Manager…
• Page 895
  Data Module Answer Text Appears when the KYBD Dialing field is y. This option enables text feedback that is normally delivered to the DTE when a call is answered or disconnected. The Answer Text option applies to DLC-generated text as well as text received from the system. If this option is disabled, the system still generates the text, but the DLC prevents it from being sent to the device.
• Page 896
  Parity has nothing to do with the far end; it is used by the DLC to terminal communications during call setup. Set to match the connected DTE. Valid entries Usage even Set to match the connected DTE. mark space 896 Administrator Guide for Avaya Communication Manager…
• Page 897
  Data Module Permit Mismatch This option allows the EIA interface to operate at a rate different than that agreed to in the data module handshake. (The data module handshake is always the highest compatible rate as determined by the reported speed option of each data module.) Permit Mismatch eliminates the need to change the DTE/DLC speed every time a call is placed to/from an endpoint operating at a different speed.
• Page 898
  If printer is member of Hunt Group Permit No, if printer is low speed Mismatch Parity Don’t care Dial Echoing Don’t care Disconnect Don’t care Sequence Answer Text Don’t care Connected Don’t care Indication Configuration 898 Administrator Guide for Avaya Communication Manager…
• Page 899
  Data Module Non-intelligent terminals A non-intelligent terminal connected to the DLC usually is assigned as a line. Table 11 lists the option settings for non-intelligent terminals. Table 11: DLDM screen settings for connection to non-intelligent terminals Field On screen Option Comments Speed All speeds at…
• Page 900
  Dial Echoing These devices can dial in the ASCII stream without human intervention Disconnect Sequence Long <BREAK> Answer Text These devices might not want to see any text Connected Indication Don’t care Configuration 900 Administrator Guide for Avaya Communication Manager…
• Page 901
  Data Module Host computers A host computer can originate and terminate a data call. For this application, the number of DLCs required depends on the number of ports needed. An MADU can be used (instead of 8 ADUs) to complete the connection. Table 13 lists option settings for a port that has a terminating connection to a host computer or an originating connection from a host computer.
• Page 902
  000123401. The three leading zeros are necessary to create a 9-digit SPID.) Valid entries Usage 00 to 62 Enter a 2-digit number. Each Endpt ID field must have a unique value for each endpoint on the same port. 902 Administrator Guide for Avaya Communication Manager…
• Page 903
  Data Module Endpt Init Used with 7500, World Class BRI, and NI-BRI Data Modules. Endpoint initialization is a procedure, required for multipoint operation, by which User Service Order Profile (USOP) is associated with an endpoint on the ISDN-BRI. This association is made via the Service Profile Identifier (SPID), administered into the system and entered into the ISDN-BRI terminal.
• Page 904
  Enter a 1 to 2-digit number. (Exchange identification) Used with 7500, World Class BRI, and NI-BRI Data Modules. Used to identify layer 2 XID testing capability. Valid entries Usage Avaya recommends setting to n. 904 Administrator Guide for Avaya Communication Manager…

• Page 905: Date And Time

  Settings on this screen affect the internal clock and timestamp of the server running Avaya Communication Manager. You should update the date and time for a leap year or a system restart after a power failure.

• Page 906
  Enter the current minute. The system clock uses this as the current minute. Month Valid entries Usage January through Enter the current month. The system clock uses this as the current month. December 906 Administrator Guide for Avaya Communication Manager…
• Page 907
  Date and Time Second This display-only field shows the seconds and cannot be modified. It resets to zero when you save the information on this screen. Type Valid entries Usage daylight-savings Enter daylight-savings to indicate daylight savings time is in effect. standard Enter standard to indicate standard time is in effect.

• Page 908: Daylight Savings Rules

  Enter the day of the week you want the clock to move ahead to begin Saturday or Day daylight savings. If you enter Day in this field, the clock will change on the exact date entered in the next two fields. 908 Administrator Guide for Avaya Communication Manager…

• Page 909
  Daylight Savings Rules Change day (Stop) Valid entries Usage Sunday through Enter the day of the week you want the clock to move back to return to Saturday or Day standard time. If you enter Day in this field, the clock will change on the exact date entered in the next two fields.
• Page 910
  Enter the hour you want the clock to move back to return to standard time. 0 to 59 Enter the minute you want the clock to move back to return to standard time. 910 Administrator Guide for Avaya Communication Manager…

• Page 911: Dcs To Qsig Tsc Gateway

  DCS to QSIG TSC Gateway DCS to QSIG TSC Gateway Use the DCS to QSIG TSC Gateway screen to determine when and how to convert messages from an administered AUDIX NCA-TSC to a QSIG NCA-TSC. This screen maps the AUDIX NCA-TSC to the appropriate machine ID index to find the QSIG subscriber entry in the QSIG MWI-Prefix screen.

• Page 912
  Enter the assigned signaling group number for qsig-mwi application type on the Signaling Group screen. Voice Mail Number This field can be left blank. Valid entries Usage 0 to 9 Enter the complete Voice Mail Dial Up number up to 15 digits. 912 Administrator Guide for Avaya Communication Manager…

• Page 913: Dial Plan Analysis Table

  Avaya Communication Manager needs to interpret. The Dial Plan Analysis Table and the Dial Plan Parameters screen work together to define your system’s dial plan.

• Page 914
  In order to use this code in your dial plan, the ARS/AAR Dialing without FAC feature must be enabled on the System Parameters Customer Options screen. (Contact your Avaya technical support representative to discuss the ARS/AAR Dialing Without FAC feature before enabling it.)
• Page 915
  DAC entry have Dial Access on the Trunk Group screen set to n. You can use the DAC to activate or deactivate a Communication Manager feature or to seize a trunk from a trunk group, or both. In the first case, the DAC functions as a FAC, in the second as a TAC.
• Page 916
  Screen Reference Dialed String The dialed string contains the digits that Avaya Communication Manager will analyze to determine how to process the call. This field allows you to enter up to four digits, so you can allocate blocks of 1000 numbers even when using a 7-digit dial plan…

• Page 917: Dial Plan Parameters

  It also controls the appearance of 6- and 7-digit extensions on station displays. These 6- and 7-digit extensions can be hard to read as a block. Avaya Communication Manager allows you to select a single system-wide format for all 6-digit extensions and a format for all 7-digit extensions.

• Page 918
  The digits entered in this field are concatenated with the calling or called extension. Appears only if, on the System-Parameters Customer-Options screen, the ARS/AAR Dialing Without FAC field is y. (Contact your Avaya technical support representative to discuss the ARS/AAR Dialing Without FAC feature before enabling it.)
• Page 919
  1 to 640 or blank Avaya DEFINITY ServerCSI. 1 to 999 or blank Avaya S8300 and S8700 Media Servers. Local Node Number Enter a number to identify a specific node in a server network. This entry must match the DCS switch node number and the CDR node number if they are specified.

• Page 920: Digit Absorption

  This screen implements up to 5 digit absorption lists. The screen might be required for each CO and FX trunk group connected to a step-by-step CO. Each outgoing digit string from the server running Communication Manager to the step-by-step CO is treated according to entries in the «Absorption Treatment Assignment» section of the screen.

• Page 921: Ds1 Circuit Pack

  DS1 Circuit Pack Absorption Treatment Information This is a display-only section. It shows how Digit Absorption treats each digit, 0 through 9, depending on the assignment of A through C for Group I, and A, D, E, and F for Group II. Enter the assignment on the next section on the screen.

• Page 922
  Page 1 of x DS1 CIRCUIT PACK Location: 01A13 Name: _______________ Bit Rate: 2.048 Line Coding: cmi Signaling Mode: CAS Interconnect: pbx Country Protocol: 3 Interface Companding: mulaw Idle Code: 11111111 MAINTENANCE PARAMETERS Slip Detection? n 922 Administrator Guide for Avaya Communication Manager…
• Page 923
  The ETSI and ISO QSIG specifications require that B-channels on an E1 be encoded as 1 to 30 in the Channel ID IE. Prior to the existence of this field, Avaya Communication Manager only used this scheme for Country Protocols 2a (Australia) and 13a (Germany 1TR6). This field appears when the Signaling Mode field is isdn-pri, the Bit Rate field is 2.048, the Connect…
• Page 924
  ISDN-PRI interface. Use line-side to connect to Roll About Video equipment. network Enter network when the DS1 link connects Communication Manager to a central office or any other public network switch. host Enter host when the DS1 link connects Communication Manager to a computer.
• Page 925
  DS1 Circuit Pack This field indicates whether a cyclic redundancy check (CRC) will be performed on transmissions that the DS1 circuit pack receives. This field does not display for all circuit packs. Valid entries Usage Enter y when the Signaling Mode field is CAS and the DS1 link is providing E-1 service.
• Page 926
  The DMI/BOS protocol is used for high-speed digital communications between a host computer and Avaya Communication Manager. With this 24-channel protocol, channels 1 to 23 of the DS1 link carry data and channel 24 carries control signaling. DMI/BOS has greater capacity than a robbed-bit 24-channel facility.
• Page 927
  For E-1 service using channel-associated signaling, the entry in this field tells Avaya Communication Manager whether the DS1 circuit pack is using a public or private network protocol. The entry in this field must agree with the entry in the Group Type field on the Trunk Group screen.
• Page 928
  This field controls the T302 and T303 timers. It only appears if the Signaling Mode field is isdn-pri. Valid entries Usage Use if you want to increase the length of the long timers. Leave n if you want to use the default long timers. 928 Administrator Guide for Avaya Communication Manager…
• Page 929
  DS1 facility. For the TTC 2Mb CMI Trunk circuit pack, this is a display-only field showing cmi (coded mark inversion). The following information is for reference. Talk with your network service provider or your Avaya technical support representative to find the appropriate protocol for your application.
• Page 930
  Length: 0798 to 1066(ft), 243 to 325(m) Length: 1066 to 1310(ft), 325 to 400(m) Location This display-only field shows the port address specified in the add command when the circuit pack was first administered. 930 Administrator Guide for Avaya Communication Manager…
• Page 931
  Customer-Options screen and there is a value in the MMI Cabling Board field. Name Use this field to assign a significant, descriptive name to the DS1 link. Avaya recommends putting the vendor’s circuit ID for the link in this field, because that information helps you troubleshoot problems with the link, but you could also use this field to indicate the function or the destination of this DS1 facility.
• Page 932
  Connected Number field to r (restricted) on the ISDN-PRI Trunk Group screen, as this causes display problems. Public network signaling administration for ISDN-PRI Layer 3 The table below shows Avaya Communication Manager public-network access connections for ISDN-PRI Layer 3. Admin…
• Page 933
  DS1 Circuit Pack Admin Country Protocol supported B-channel value mtce msg Australia ETSI ISDN protocol Restart Japan NTT INS-NET Restart Italy ETS 300 102 Restart Netherlands ETS 300 102 Restart Singapore ETS 300 102 Restart Mexico ETS 300 102 Restart Belgium ETS 300 102 Restart…
• Page 934
  Usage 20 to 1000 ms in Work with your network services provider to determine the increments of 10ms. appropriate entry. The entry must be less than the Received Digital Metering Pulse Maximum field. 934 Administrator Guide for Avaya Communication Manager…
• Page 935
  DS1 Circuit Pack Received Digital Metering Pulse Value This field appears when the Signal Mode field is cas (Channel Associated Signaling), the Country Protocol field is 21, and the Interconnect field is co or pbx. Valid entries Usage 0, 1 Work with your network services provider to determine the appropriate entry.
• Page 936
  0, 1 2 of 2 Side This field controls how your server running Communication Manager resolves glare at layer 3 over an ISDN-PRI link in QSIG private networks. It appears if the Interface field is peer-master or peer-slave. The default value of the field changes depending upon which value the Interface field contains.
• Page 937
  DS1 Circuit Pack Signaling Mode This field selects the signaling method used for the DS1 link. This mode must match the method used on the other end of the link, so work with your network services provider to determine the appropriate entry for this field.

• Page 938: Echo Cancellation

  Connect field is line-side. Valid entries Usage Enter y if you want the server running Avaya Communication Manager to generate an alarm when the DS1 board detects a loss of signal (for example, if the video equipment is disconnected).

• Page 939
  DS1 Circuit Pack Near-end CSU Type This field appears only when the DS1 circuit pack is a TN767D or TN464E or later suffix model, the Bit Rate field is 1.544 and the Country Protocol field is 1 (U.S.). This field does not display for all circuit packs.
• Page 940
  CPE LOOPBACK JACK OPTIONS Supply CPE Loopback Jack Power? CAUTION: Customers: Do not change fields on this page without assistance from Avaya or CAUTION: your network service provider. Page 2 does not appear for all DS1 circuit packs. For those circuit packs that support it, this page appears only when the Framing Mode field is esf or the Near-end CSU Type field is integrated.
• Page 941
  This field appears only if the Framing Mode field is esf. It is used only with circuit packs that have an integrated channel service unit (CSU). Valid entries Usage Enter n. Consult your Avaya technical support representative if you think you might want to use these reports. Issue 2.1 May 2006…
• Page 942
  This field reduces the outgoing signal strength by a fixed amount. The appropriate level of loss depends on the distance between your Communication Manager server (measured by cable length from the smart jack) and the nearest repeater. Where another server/switch is at the end of the circuit, as in campus environments, use the cable length between the 2 switches to select the appropriate setting from the table below.
• Page 943
  DS1 Circuit Pack Upon DTE LOS DTE stands for «Data Terminal Equipment.» This field tells Communication Manager what to do if the outgoing signal from the DS1 circuit pack (the data terminal equipment) to the network is lost. Valid entries…

• Page 944: Enable File Transfer

  ENABLE FILE TRANSFER Login:______ Password:___________ Password:___________ Secure? Login Valid entries Usage 3 to 6 Enter your login. alphanumeric characters Password Valid entries Usage 7 to 11 characters, Enter your password. with at least one number 944 Administrator Guide for Avaya Communication Manager…

• Page 945: Enable Session

  Enable Session Password Valid entries Usage 7 to 11 Repeat your password for verification. Entry must be identical in both characters, with at Password fields. least one number Secure Valid entries Usage Enter y to enable SFTP instead of FTP or TFTP. If the circuit pack does not support a secure session, no session is enabled.

• Page 946
  This field appears only if the board in question is a TN2302. Valid entries Usage 0 to 255 Enter the number of minutes allowed for login before the session times out. Default is blank. 946 Administrator Guide for Avaya Communication Manager…

• Page 947: Extended Pickup Group

  Extended Pickup Group Extended Pickup Group This screen allows grouping of pickup groups into extended pickup groups. This allows users to answer calls outside their immediate group. The maximum number of groups that can be added to an extended pickup group is 25. Field descriptions for page 1 Figure 352: Extended Pickup Group screen change extended-pickup-group n…

• Page 948
  This display-only field shows the pickup number assigned to the pickup group number. This is the number users dial after the feature access code (FAC) to pick up calls in their extended pickup group. 948 Administrator Guide for Avaya Communication Manager…

• Page 949: Extensions Administered To Have An Mct-Control Button

  Extensions Administered to have an MCT-Control Button Extensions Administered to have an MCT-Control Button This screen lists the extensions that can take control of a Malicious Call Trace (MCT) request. In order to give a user the ability to take control of such requests, you need to add their extension to this list and assign them a mct-control feature button.

• Page 950: Extensions To Call Which Activate Features By Name

  Administer the FACs on the Feature Access Code (FAC) screen. For more information about individual features, see Feature Description and Implementation for Avaya Communication Manager, 555-245-205. Field descriptions for page 1 Figure 354: Extensions to Call which Activate Features By Name screen…

• Page 951
  Extensions to Call Which Activate Features by Name Extension Each Extension field is an extension that matches your dial plan. A user dials the extension from their Extension to Cellular telephone to activate an FAC administered for that feature. Valid entries Usage 0–9 or blank Type an extension number, up to seven digits, for the Communication…

• Page 952: Feature Access Code

  Contact Closure Open Code: ____ Close Code: ____ Contact Closure Pulse Code: ____ Abbreviated Dialing List1 Access Code Used to access AD list 1. Abbreviated Dialing List2 Access Code Used to access AD list 2. 952 Administrator Guide for Avaya Communication Manager…

• Page 953
  Feature Access Code Abbreviated Dialing List3 Access Code Used to access AD list 3. Abbreviated Dial — Prgm Group List Access Code Used to enter a group list from a telephone. The user’s extension must be entered on the Abbreviated Dial Group List screen in order to program the group list. Announcement Access Code Used to record announcements.
• Page 954
  Used by a Centralized Attendant Service (CAS) attendant to place calls on hold and answer calls held at a remote server running Communication Manager. This FAC can also be used by an analog station. Flashing the switch-hook for the proper interval (between 200 and 1000 ms) while talking on an existing call causes the existing call to be placed on soft hold, allowing the analog user to dial the Answer Hold-Unhold FAC to Hard hold the call.
• Page 955
  Feature Access Code Contact Closure Close Code Used to close a contact closure relay. Must be administered if the Contact Closure Open Code field is administered. Contact Closure Open Code Used to open a contact closure relay. Must be administered if the Contact Closure Close Code field is administered.

• Page 956: Data Origination Access Code

  The user calls the SAFE access code and enters their cell phone number. The administration sequence differs based on what phone is used to access SAFE. For more information, see Feature Description and Implementation for Avaya Communication Manager, 555-245-205 and Avaya Extension to Cellular User’s Guide, 210-100-700.

• Page 957: Enterprise Mobility User Activation

  Feature Access Code Enterprise Mobility User Activation Type a feature access code number to activate the Enterprise Mobility User feature for a particular user, associating the features and permissions of their primary telephone to a telephone of the same type anywhere within the customer’s enterprise. For more information about Enterprise Mobility User, see Setting Up Enterprise Mobility User on page 166.

• Page 958: Facility Test Calls Access Code

  Flash Access Code Used to generate trunk flash. This code ensures that the flash signal is interpreted by the central office switch, rather than by Avaya Communication Manager. Group Control Restrict Activation / Deactivation Used to change the restriction level for all users with a given class of restriction. Requires console permissions.

• Page 959: Leave Word Calling Send A Message

  Feature Access Code Leave Word Calling Send A Message Used to send a leave word calling message. Leave Word Calling Cancel A Message Used to cancel a leave word calling message. Malicious Call Trace Activation Used to activate a trace request on a malicious call. Meet-me Conference Access Code Change Allows the controlling user of a Meet-me Conference VDN to change the access code.

• Page 960: Posted Messages

  Only appears if the Posted Messages field is set to y on the System-Parameters Customer-Options screen. Used to access the Posted Messages feature. See «Posted Messages» in Feature Description and Implementation for Avaya Communication Manager, 555-245-205, for more information Program Access Code Used to program abbreviated dial buttons on an individual telephone.

• Page 961
  Feature Access Code Remote Send All Calls Activation/Deactivation Used to activate or deactivate the Send All Calls feature. Requires console permissions. Self Station Display Activation The Self Station field is not active. If set to a valid FAC, a digital station displays its primary extension number when the FAC is entered.
• Page 962
  Used to perform tests on digital telephones to make sure that the telephone and the buttons are communicating properly with the server running Avaya Communication Manager. To use a Terminal Dial-up Test FAC on a telephone with bridged appearances, add a bridged-appearance of the principal telephone.
• Page 963
  Feature Access Code Transfer to Voice Mail Access Code Enter the digits that must be dialed to allow coverage to transfer the caller to the original call recipient’s AUDIX mail where the caller can leave a message. Do not administer this code to have the same first digit as another feature access code that is longer in length.
• Page 964
  Enter the digit the agent must dial to request assistance from the split supervisor. Auto-In Access Code Enter the code the agent must dial to become automatically available to receive another ACD call each time a call is released. 964 Administrator Guide for Avaya Communication Manager…
• Page 965
  Feature Access Code Aux Work Access Code Enter the code the agent must dial when the agent will be performing non-ACD activities. Login Access Code Enter the code the agent must dial to gain access to the ACD functions. This is a system-wide code for all ACD agents.
• Page 966
  Enter a 1 to 4 digit number (# can be used as the first digit). Entry of the Vector Variable Code FAC allows you to change the variable on the Variables for Vectors screen. 966 Administrator Guide for Avaya Communication Manager…
• Page 967
  Feature Access Code Field descriptions for page 7 The feature access codes on this page pertain only to Hospitality features. Figure 361: Feature Access Code (FAC) screen change feature-access-codes Page 7 of x FEATURE ACCESS CODE (FAC) Hospitality Features Automatic Wakeup Call Access Code: *11 Housekeeping Status (Client Room) Access Code: ______ Housekeeping Status (Client Room) Access Code: ______ Housekeeping Status (Client Room) Access Code: ______…
• Page 968
  Multimedia Call Access Code If you enter this FAC from any voice station, it indicates to Avaya Communication Manager that you are making an Enhanced mode multimedia call. If you originate a multimedia call with the multimedia call access code, it will originate a call according to the Default Multimedia Parameters selected on the Feature Related System Parameters screen.
• Page 969
  System-Parameters screen. Multimedia Parameter Access Code This FAC can be entered by any voice station to indicate to Avaya Communication Manager that you want to initiate a multimedia mode call with a specific bearer capability. This FAC would be followed by a 1 or 2 to indicate the following parameter selections respectively: 2×64 (unrestricted initial system default), 2×56 (restricted).
• Page 970
  Flash Override Access Code Enter a FAC to correspond with the Flash Override preemption level. Flash Access Code Enter a FAC to correspond with the Flash preemption level. 970 Administrator Guide for Avaya Communication Manager…
• Page 971
  Feature Access Code Immediate Access Code .Enter a FAC to correspond with the Immediate preemption level. Priority Access Code .Enter a FAC to correspond with the Priority preemption level. Routine Access Code .Enter a FAC to correspond with the Routine preemption level. Issue 2.1 May 2006…

• Page 972: Feature-Related System Parameters

  ACA Long Holding Time Originating Extension: ______ Abbreviated Dial Programming by Assigned Lists: Auto Abbreviated/Delayed Transition Interval(rings): Protocol for Caller ID Analog Terminals: Bellcore Display Calling Number for Room to Room Caller ID Calls? 972 Administrator Guide for Avaya Communication Manager…

• Page 973
  Feature-Related System Parameters AAR/ARS Dial Tone Required A second dial tone provides feedback to the user that additional dialing can occur. Valid entries Usage Enter y to indicate a second dial tone is to be given to the calling party on a incoming tie or DID trunk call that is to be routed via AAR/ARS.
• Page 974
  The specified extension should be equipped with a display module. This field only appears if ACA Referral Calls is local or primary. Valid entries Usage An extension Enter the extension on a local server running Communication Manager that is to receive the ACA referral call. attd Enter attd for attendant. ACA Remote PBX Identification This field only appears if ACA Referral Calls is remote.
• Page 975
  Feature-Related System Parameters Automatic Callback — No Answer Timeout Interval (rings) Valid entries Usage 2 to 9 Enter the number of times the callback call rings at the calling station before the callback call is canceled. Automatic Circuit Assurance (ACA) Enabled If Automatic Circuit Assurance (ACA) Enabled is n, associated ACA fields will not display.
• Page 976
  For system security, Avaya recommends entering attd in this field. This routes intercept calls to the attendant and, if the attendant receives several of these, they will know a problem exists.
• Page 977
  You can purchase a Magic OnHold system, which does not require such a license, from Avaya or our business partners. This field does not appear if Tenant Partitioning is y on the System-Parameters Customer-Options screen.
• Page 978
  Enter Bellcore for Bellcore protocol with 212 modem protocol tones. Used in the U.S. and similar countries. V23-Bell Enter V23-Bell for Bellcore protocol with V.23 modem tones. Used in Bahrain and similar countries. 978 Administrator Guide for Avaya Communication Manager…
• Page 979
  The primary extension does display when the inspect button is pressed. The extension does not display when the inspect button is pressed. Trunk-to-Trunk Transfer Regulations in some countries control the settings for this field. See your Avaya technical support representative for assistance. Valid entries Usage Enter all to enable all trunk-to-trunk transfers.
• Page 980
  Enhanced Abbreviated Dial Length (3 or 4)? _ Record All Submission Failures in History Log? _ Record PMS/AD Transactions in History Log?_ Record IP Registrations in History Log? Default Multimedia Outgoing Trunk Parameter Selection: 2×64 980 Administrator Guide for Avaya Communication Manager…
• Page 981
  Maximum Number of External Calls Logged Per Station When an external call is not answered, the server running Communication Manager keeps a record of up to 15 calls (provided information on the caller identification is available) and the telephone’s message lamp lights.
• Page 982
  Observing, Intrusion, Verify, and Bridging. Record All Submission Failures in History Log Allows submission failures to be recorded on the history log. Valid entries Usage Enter y to record submission failures on the history log. 982 Administrator Guide for Avaya Communication Manager…
• Page 983
  Stations With System-wide Retrieval Permission (enter extension) An extension must be removed from this list before the station is removed from the system. The server running Communication Manager refers to the extensions on this list as «super-retrievers.» Valid entries…
• Page 984
  Valid entries Usage 1 to 20 digits Enter the calling party number or automatic number identification for calls made from dissociated telephones. 984 Administrator Guide for Avaya Communication Manager…
• Page 985
  Feature-Related System Parameters Customer Telephone Activation (CTA) Enabled Valid entries Usage Enter y if you want the Customer Telephone Activation feature for your system. Enter n if you do not want the Customer Telephone Activation feature for your system. Default COR for Dissociated Sets Appears when the Terminal Translation Initialization (TTI) Enabled? field is y.
• Page 986
  Terminal Translation Initialization (TTI) Enabled For more information on TTI, see «Terminal Translation Initialization» in Feature Description and Implementation for Avaya Communication Manager, 555-245-205. You should contact your Avaya technical support representative before making changes to TTI settings. Valid entries…
• Page 987
  Feature-Related System Parameters TTI State Appears when the Terminal Translation Initialization (TTI) Enabled? field is y. Enter the type of port translation that you want for the system to use for unadministered digital ports. The default is voice. Valid entries Usage data Enter data, if you want a stand-alone data module to the be the TTI port…
• Page 988
  Authorization Code Enabled? y Authorization Code Length: 7 Authorization Code Cancellation Symbol? # Attendant Time Out Flag? n Display Authorization Code? _ Controlled Toll Restriction Replaces: station-station Controlled Toll Restriction Intercept Treatment: extension 3000 988 Administrator Guide for Avaya Communication Manager…
• Page 989
  Feature-Related System Parameters Call Pickup Alerting This provides pickup group members with a visual indication on the Call Pickup status lamp of calls eligible to be answered via Call Pickup Valid entries Usage Enter y to enable Call Pickup Alerting on a system-wide basis. Call Pickup on Intercom Calls Valid entries Usage…
• Page 990
  Redirects intercepted calls to coverage. extension If extension is entered, complete an associated extension number field. Cannot be a VDN extension, tone Provides a siren-type tone to calls that cannot be completed as dialed. 990 Administrator Guide for Avaya Communication Manager…
• Page 991
  Feature-Related System Parameters Deluxe Paging and Call Park Timeout to Originator Paged calls that are to be parked require separate activation of the Call Park feature. All parked calls that time out return to the attendant. Valid entries Usage Enter y to enable the Loudspeaker Paging — Deluxe feature that essentially integrates the Loudspeaker Paging and Call Park features.
• Page 992
  Enter the time in seconds that a telephone with an Off-Hook Alert Class of seconds Service can remain off-hook (after intercept tone has started) before an emergency call is sent to the attendant. 992 Administrator Guide for Avaya Communication Manager…
• Page 993
  Usage Enter the cancellation code # if the main and tandem servers/switches are both of the same type. Enter the cancellation code 1 if an Avaya System 85 or DIMENSION PBX switch is part of the complex/network. Authorization Code Length This field only appears and must be completed if Authorization Codes Enabled is y.
• Page 994
  Screen Reference Authorization Codes Enabled This field cannot be administered if Authorization Codes is not enabled on the System-Parameters Customer-Options screen. SECURITY ALERT: To maintain system security, Avaya recommends that Authorization Codes be SECURITY ALERT: used. Valid entries Usage Enter y to enable Authorization Codes on a systemwide basis.
• Page 995
  Feature-Related System Parameters Display Authorization Code This field applies only to DCP, not to BRI or hybrid sets. SECURITY ALERT: To enhance your system’s security, set Display Authorization Code to n. SECURITY ALERT: Valid entries Usage Enter y to allow authorization code digits to display on the set during the dialing.
• Page 996
  This Emergency Extension Forwarding only applies if the emergency location extension number is an extension on the same PBX as the extension that dialed 911. Customers who have several PBXs in a campus should assign emergency location extensions accordingly. 996 Administrator Guide for Avaya Communication Manager…
• Page 997
  Enable Inter-Gateway Alternate Routing For more information on Inter-Gateway Alternate Routing, see Administration for Network Connectivity for Avaya Communication Manager, 555-233-504. Valid entries Usage Enter y to enable the Inter-Gateway Alternate Routing feature. Default is…
• Page 998
  MCT Voice Recorder Trunk Group Assign the trunk group for MCT voice recorders. Valid entries Usage 1 to 666 or blank group number for DEFINITY CSI 1 to 2000 or blank group number for S8700 Series IP-Connect 998 Administrator Guide for Avaya Communication Manager…
• Page 999
  Feature-Related System Parameters SEND ALL CALLS OPTIONS Auto Inspect on Send All Calls Valid entries Usage If set to y, allows you to be presented automatically with Calling Party information for calls which are silently alerting their station because of the Send-All-Calls feature.
• Page 1000
  Use Trunk COR for Outgoing Trunk Disconnect? _ 7405ND Numeric Terminal Display? n 7434ND? n DISTINCTIVE AUDIBLE ALERTING Internal: 1 External: 2 Priority: 3 Attendant Originated Calls: DTMF Tone Feedback Signal to VRU — Connection: _ Disconnection: _ 1000 Administrator Guide for Avaya Communication Manager…

Помогите с освоением АТС

Сообщение

JRoger » Сб 16 окт 2010, 06:33

support.avaya.com тебе в руки.

Сообщение

sweed » Сб 16 окт 2010, 21:20

Сообщение

VladVN » Вс 17 окт 2010, 13:59

Добрый день!
А может Вам задуматься о посещении курсов, для начала Базовое администрирование. В Москве есть прекрасные пятидневные курсы (фирму здесь не скажу, чтобы не сочли за рекламу). У меня есть кое-какая информация на русском языке, но боюсь Вам будет довольно сложно разобраться самому, если никогда не имели дело с Avaya. Ну а если хорошо владеете английским, то на английском документации валом.

Сообщение

sweed » Вс 17 окт 2010, 22:30

Сообщение

sweed » Вс 17 окт 2010, 22:44

В принципе все что я знаю что это АТС, устанавливали ее до меня, она никогда не требовала вмешательства, но сейчас надо поменять привязки внутренних к внешним линиям, документации и дисков от нее нет! я даже не знаю что это за модель, звонил в суппорт, тоже ничем дельным помочь не смогли, у меня есть консоль, синяя, установленная. Дайте хоть список команд и ключей к ним(если такие есть).

Сообщение

sweed » Вс 17 окт 2010, 22:46

И скажите как она называется(всмысле модель АТС)

Сообщение

vlads7 » Пн 18 окт 2010, 03:59

Сообщение

SpbPavel » Пн 18 окт 2010, 13:43

Сообщение

Ingener » Вт 19 окт 2010, 06:44

Кто *** в дождь и грязь — наша доблестная связь!
Если нет дождя и грязи — нас *** начальник связи!

Сообщение

sweed » Вт 19 окт 2010, 15:11

Огромное спасибо тому кто прислал 4 письма на мыло с инструкциями, это то что надо=)

Сообщение

sweed » Вт 19 окт 2010, 15:15

Я не уверен что это ASA (Avaya Site Administration), данная консоль подписана как Avaya Terminal Emulator. Еще установленна программа Барсум, какое отношение она имеет к атс не знаю но у нее значек иконки — телефон

Сообщение

VladVN » Вт 19 окт 2010, 21:49

Это я отправил тебе 4 письма, я у тебя спрашивал, с какого ты региона, может близко от меня, дело в том, что есть еще кое-какая инфа, но она много весит, почта ее не пережует, раздробить тоже не получится. ответ можно в личную почту.

Сообщение

sweed » Ср 20 окт 2010, 13:59

Сообщение

sweed » Ср 20 окт 2010, 14:02

Сообщение

SpbPavel » Ср 20 окт 2010, 14:17

У меня вроде свежая, 5.2.13.

Сообщение

sweed » Ср 20 окт 2010, 14:40

Сообщение

SpbPavel » Ср 20 окт 2010, 15:02

Так как, меню File-New-Voice system. Дальше оно подскажет.

Сообщение

sweed » Ср 20 окт 2010, 15:38

Login ID и пасс к нему где берем?

Сообщение

SpbPavel » Ср 20 окт 2010, 15:48

Как в АТС назначено, с какими терминалом заходили…
Логин обычно dadmin, ну а пароль надо знать.

Сообщение

sweed » Ср 20 окт 2010, 15:56

Сообщение

SpbPavel » Ср 20 окт 2010, 16:24

Сообщение

sweed » Ср 20 окт 2010, 17:03

Сообщение

SpbPavel » Ср 20 окт 2010, 17:10

Да, СПб.
А кто знает, знакомый знакомого…

Сообщение

sweed » Вт 23 ноя 2010, 18:46

Сообщение

SpbPavel » Вт 23 ноя 2010, 19:03

Сообщение

sweed » Вт 23 ноя 2010, 19:20

С никсами знаком, значит смогу разобраться
А вторая колонка ТАС что означает?

Сообщение

SpbPavel » Вт 23 ноя 2010, 19:33

Всего лишь Trunk Access Code, цифры, указанные в cha tru, служат для доступа к группе СО, если это разрешено.
Наберете #53 — займется СО 2518900.

Сообщение

sweed » Вт 23 ноя 2010, 19:44

клева

Сообщение

Bolshoy » Ср 24 ноя 2010, 08:18

sweed, тебе не столько мануал по ASA нужен (у него есть встроенная справка на крайняк), сколько по администрированию самой станции. собственно документы по Communication Manager можно найти здесь:
http://support.avaya.com/css/Products/P … rogramming
там можно отсортировать документы по интересующему тебя релизу. рекомендую первым посмотреть «Administering Avaya Aura™ Сommunication Manager». в частности там есть раздел «Managing Trunks», который тебя интересовал.

Сообщение

sweed » Сб 27 ноя 2010, 00:41

Сообщение

SpbPavel » Сб 27 ноя 2010, 12:45

1. Ну да, группы, а в них аналоговые города.
2. Приход звонка с группы на 202, если не указано иное. А оно указано ниже.
3,4,5. Не-а, это он и есть — приход звонка. Если не указан, то п.2
6,7,8. Правильно.
9,10. Перед этим смотрите li ars anal. Цифры оттуда ссылаются на Route Pattern, а Pattern — на группу СО. Это и есть исходящее.
11. Да, задается в cha sta.
12. Не, это персональный скоростной набор.
13. Class of Restiction, присваивается внутренним. Кому чего можно, чего нельзя.

Сообщение

sweed » Вт 30 ноя 2010, 15:47

Все равно не выходит=(
Создал новую транк группу 14, скинул туда внешний номер СО из 9 группы
В Coverage answer-group поменял внутренние номера.
сохранил все кнопкой Ф12 позвонил на внешний номер, звонок прошел по старому маршруту=(
где я накосячил?

Сообщение

SpbPavel » Вт 30 ноя 2010, 17:58

В cha tru 14 что указано в поле Night?
Должно приходить туда, у этого ext стоит coverage path XXX, в cha cov pa XXX стоит C<что-то>.
С — это и есть Coverage answer group.

Сообщение

sweed » Вт 30 ноя 2010, 18:14

Спасибо разобрался=)

Сообщение

vatc » Ср 01 дек 2010, 13:49

Уважаемые, день добрый.
Перечитал все доки. Не мог найти ответ на вопрос.
Есть транки PRI, R1.5 через DS1, 4-пров. транки ТЧ, 2-х провод. СО.
Нужна или нет в этом случае плата классификатора вызовов (детектор) -CALL CLASSIFIER TN744D, если есть плата TONE/CLOCK TN2182 B ? Просветите, плиз.

Сообщение

SpbPavel » Ср 01 дек 2010, 14:38

Сообщение

sweed » Ср 01 дек 2010, 14:51

Сегодня вернулся к нам сервер (тот что на первой фотке) из мест не столь отдаленных, на нем установлена программа Барсум(легальная), и судя по всему была завязана с АТС.
Можно ли с помощью нее управлять АТС?

Сообщение

SpbPavel » Ср 01 дек 2010, 14:59

Нет, она предназначена для сбора тарификации, то есть информации о том, кто, куда и на какую сумму назвонил.

Сообщение

vatc » Ср 01 дек 2010, 15:17

tnx es 73!

Сообщение

SpbPavel » Ср 01 дек 2010, 16:30

Ры-полтора я видал живьем больше года назад…
В общем, CALL CLASSIFIER Вам не требуется, если хватает приемников DTMF.

Сообщение

sweed » Вс 05 дек 2010, 22:12

Все бы ничего, но, то ли АТСка не хочет сохранять изменения конфигурации, то ли я не понимаю как оно сохраняется
Перенастроил параметры, спустя пару дней залез опять в настройки, а там все как и было, как будто ничего и не менял

Сообщение

Bolshoy » Пн 06 дек 2010, 08:19

трансляции сохранял (save translation)?
если не сохранить, то при перезагрузке станции все изменения потеряются.

Сообщение

sweed » Пн 06 дек 2010, 10:43

Нет, как это делается?

Сообщение

SpbPavel » Пн 06 дек 2010, 11:10

save translation и долго ждем

Сообщение

Елена » Пн 06 дек 2010, 11:12

В ASA в командной строке набираете save translation и жмете кнопочку рядом send. Результат выполнения команды высветится на экране Successю

Сообщение

sweed » Пн 06 дек 2010, 13:50

Да помогло, спасибо

Сообщение

sweed » Пн 06 дек 2010, 20:49

Сообщение

SpbPavel » Пн 06 дек 2010, 22:20

Не здесь, это исходящие маршруты для всех (или почти всех).
Нужно через COR.

Сообщение

Елена » Вт 07 дек 2010, 15:38

В CORе абонента смотрите строку Time of Day Chart: Х. Далее Display (Change) partition-route table 0, там в столбцах PGN1, PGN2 и т.д. — это Time of Day Chart; Route Index — это p1, p2 (которые прописаны в ARS); на пересечении столбцов (PGN) и строк — номера маршрутов, в которых прописаны транк-группы.

Сообщение

shrike » Ср 08 дек 2010, 07:55

цена топика — 2 килобакса (или сколько нынче курсы администрирования авайи стоят?)

Сообщение

guest_avaya » Ср 08 дек 2010, 08:15

Сообщение

Ingener » Ср 08 дек 2010, 15:00

guest_avaya, полностью поддерживаю)) даже не то что мануал, а можно и на книгу наскрести)

Кто *** в дождь и грязь — наша доблестная связь!
Если нет дождя и грязи — нас *** начальник связи!

Сообщение

BreezeSub » Ср 08 дек 2010, 16:51

Народ всем привет! у меня вопрос по поводу инсталяции ASA, у меня Avaya Definity CSI, скачал нов версию ASA 5.2.17 (раньше была 4.0), начинаю ставить, всё поставилось нормально, запускаю и при первом запуске требуется ввести логин и пасс к АТС, но помимо этого ещё появилось и поле «PIN» (раньше в 4-й версии такого пункта не было), что это за пункт (что за PIN такой)?, без него прога не запускается, пишет «Date Seporator» и «System Templates» и непроходит следующий этап.

Сообщение

guest_avaya » Ср 08 дек 2010, 19:26

Сообщение

BreezeSub » Чт 09 дек 2010, 05:52

Сообщение

guest_avaya » Чт 09 дек 2010, 07:01

Дак вы попробуйте в pin ввести свой пароль а не dadmin 1

Сообщение

BreezeSub » Пн 13 дек 2010, 11:56

Сообщение

sweed » Вт 11 янв 2011, 17:52

Сообщение

sweed » Чт 13 янв 2011, 11:55

Сообщение

choki » Чт 13 янв 2011, 21:11

sweed
Отправил инструкцию на мыло,Помогло?

Сообщение

sweed » Пт 14 янв 2011, 12:33

Да, спасибо! Вот в этой инструкции более понятно, и больше полезной информации:D

Сообщение

man » Пт 28 янв 2011, 19:59

Дорогие Россияне, помогите соеденить АВАЙЮ и DX500 по Е1, имеются следующие платы: TN747B. TN750C, TN798B, TN2793B,TN760B Как с помощью платы TN747B их собрать в одну емкость? если можно то с примерами.

Re:

Сообщение

sweed » Чт 13 окт 2011, 16:48

Re: Помогите с освоением АТС

Сообщение

AlexM » Ср 12 сен 2018, 15:18

Добрый день.
Подскажите пожалуйста. Есть АТС S8500 на неё заходит около 50 городских номеров. После грозы вылетела плата TN747B и 8 номеров перестали работать. Сейчас плату заменили, но номера так и не алё. До самой АТС доходят, а внутри уже не обрабатываются. Странно что номера эти по портам не привязаны к данной плате т.е. плату заменил в слоте 01А09, а номера нерабочие находятся совершенно на других платах например на 01А08, 01А07 и на этих платах не горит аварийной индикации и тест по ним проходит нормально.

Re: Помогите с освоением АТС

Сообщение

Pterodahtil » Чт 13 сен 2018, 09:45

встать телефоном на линию и проверить. У провайдера тоже знаете ли оборудование в грозы горит.
Заменить плату с не работающими СО — аларм и тест это хорошо, но проблемы с физикой разные бывают.

Настрою IP Office и классическую Avaya

Re: Помогите с освоением АТС

Сообщение

AlexM » Чт 13 сен 2018, 10:15

На линию вставал. До плинта АТС доходит 100% с плинта идёт на саму АТС и там уже неизвестно что происходит, но звонок не доходит до тел аппаратов

Re: Помогите с освоением АТС

Сообщение

AlexM » Пт 14 сен 2018, 09:00

Эмммммм… т.е. на виртуальный порт поставить значение «verify»? Дальше по доке написано что на тел аппарате нажать кнопку verify … на данная станция является виртуальной и не привязана к какому-то конкретному аппарату

Re: Помогите с освоением АТС

Сообщение

dsh » Пт 14 сен 2018, 16:39

Какая-то каша получилась, вам надо определить какие номера приходят на какую плату и куда дальше уходят, схема проста: городская линия->СО плата-> транкгруппа->внутренний номер(или группа или что-то еще) В тран-группер прописаны порты СО платы и куда все уходит, тут вариантов много.

Re: Помогите с освоением АТС

Сообщение

AlexM » Пн 17 сен 2018, 12:22

Ну вот например номер с порта уходит на группу.
С определением номеров интересно
они на портах
01А1303
01А1304
01А0804
01А1104
01А1204
А неисправная плата TN 747B была в слоте 01А09
Входящий звонок не распределяется по участникам группы, при звонке на городской простые длинные гудки, на гор линии все ок. Настройки не изменялись, т.е. остались как до грозы.

Вложения

Безымянный.jpg (86.09 КБ) 23432 просмотра

Re: Помогите с освоением АТС

Сообщение

dsh » Пн 17 сен 2018, 14:14

В что-то путаете или другая транк-группа или сгорела другая плата. покажите list conf all и list tru

Re: Помогите с освоением АТС

Сообщение

AlexM » Пн 17 сен 2018, 15:18

Вот

Вложения

List tru.jpg (41.91 КБ) 23420 просмотров

List.png (215.25 КБ) 23420 просмотров

Re: Помогите с освоением АТС

Сообщение

AlexM » Пн 17 сен 2018, 15:58

Re: Помогите с освоением АТС

Сообщение

gosha » Пн 17 сен 2018, 16:08

Re: Помогите с освоением АТС

Сообщение

AlexM » Пн 17 сен 2018, 16:40

Re: Помогите с освоением АТС

Сообщение

gosha » Пн 17 сен 2018, 18:16

Re: Помогите с освоением АТС

Сообщение

AlexM » Вт 18 сен 2018, 08:45

Так, стоп.
Схема такая. Есть городской номер 22-22-22 ему присвоен виртуальный порт (Night) с номером 6200 на вирт присвоен coverage path 50 все это дело включено в транковую группу 1.
Абонентские телефоны подключаются через ch cov ans 50. Там могут быть как и avaya телефоны так и обычные например panasonic kx ts2365.
Verify устанавливается в ch st 6200 в поле button assignements. Так?
Если да, то на телефонах avaya (включенных в 50 ans group которая ссылается на 6200) на экране ничего не отображается помимо стандартных полос (Дата/ время/ номер)