Page 1 Administrator Guide for Avaya Communication Manager 03-300509 Issue 1 June 2005...
Page 2 Units are accessing and using the Software at any given time. A “Unit” means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an e-mail or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or...
Page 3: Table Of Contents
Related Sources ........How to obtain Avaya books on the Web ..... . .
Page 4 Removing an Attendant Console ......Providing Backup for an Attendant......4 Administrator Guide for Avaya Communication Manager...
Page 5 Contents Chapter 6: Managing Displays ..... . . 177 Displaying Caller Information ......Displaying ANI Calling Party Information .
Page 6 Chapter 10: Setting Up Telecommuting ....363 Configuring Avaya Communication Manager for Telecommuting ..Setting up Personal Station Access ......
Page 7 Contents Setting up Digital Trunks ....... Adding Trunks to a Trunk Group ......Removing Trunk Groups .
Page 8 7100-series telephones ....... . 8 Administrator Guide for Avaya Communication Manager...
Page 9 Contents 7300-series telephones ....... . 731x-series hybrid telephones ......7400-series telephones .
Page 10 IP Routing ........1132 10 Administrator Guide for Avaya Communication Manager...
Page 11 Contents IP Server Interface (IPSI) Administration ..... . 1137 IP Services ........1141 ISDN Network Facilities .
Page 12 ........1641 12 Administrator Guide for Avaya Communication Manager...
Page 13: 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 14: Contents
Chapter 3: Managing Telephones explains how to add, swap, and remove phones, and ● how to customize a telephone, for Communication Manager administrators. Chapter 4: Managing Telephone Features explains how to administer feature buttons for ● your users’ phones.
Page 15: 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 16: 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 17: Trademarks
® All trademarks identified by or ™ are registered trademarks or trademarks, respectively, of Avaya, Inc. All other trademarks are the property of their respective owners. Related Sources The following documents provide additional information. Administration for Network Connectivity for Avaya Communication Manager, 555-233-504...
Page 18: 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 19: 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 20 About this book 20 Administrator Guide for Avaya Communication Manager...
Page 21: 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 22 The Login prompt displays. 2. Complete the steps for Logging into the System on page 21. For information about setting up remote administration, contact your Avaya technical support representative. Failed login 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 23: Accessing The S8700 Series Media Server
Accessing the S8700 Series Media Server 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.
Page 24 You may also connect directly to an individual server using its name or IP address. Avaya Site Administration To use ASA: 1. You must have a PC or laptop with Avaya Site Administration installed on it. 2. You must be connected over a LAN to either: a dedicated LAN port for service technicians, or ●...
Page 25 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 a Telnet session.
Page 26 System Basics 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 it runs initially, after downloading, you need to create a new entry for the switch connection.
Page 27: 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 399.
Page 28: Logging Off The System
Logging off the System For security, log off any time you leave your terminal. If you use terminal emulation software to administer Communication Manager, log off the system and exit the emulation application before switching to another software package. Instructions To log off: 1.
Page 29: Setting Command Permissions
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 30: More Information
If several users are logging in and out at the same time, a user may see the Note: message: Transient command conflict detected; please try later. After the users have completed logging in or out, the terminal is available for use. 30 Administrator Guide for Avaya Communication Manager...
Page 31: Establishing Daylight Savings Rules
24 hours before changing the password again. 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 32 Type 2:00 in the Time field. e. Type 1:00 in the Increment field. This information specifies the day, month, date, and time and increment at which you want the system clock to transition to daylight saving time. 32 Administrator Guide for Avaya Communication Manager...
Page 33 Establishing Daylight Savings Rules Note: You cannot delete a daylight savings rule if it is in use on either the Locations or Note: Date and Time screens. However, you can change any rule except rule 0 (zero). 3. Complete the Stop fields for rule 1. a.
Page 34: 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 35 Setting Time of Day Clock Synchronization Figure 4: Avaya Site Administration menu 3. Click Time Synchronization. The Time Synchronization - Properties screen displays. Issue 1 June 2005...
Page 36 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. 36 Administrator Guide for Avaya Communication Manager...
Page 37 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 38 Run Now to run this program immediately and click Next. ● Schedule this task to run and check the field below to determine if the default setting is ● satisfactory. If this setting is not satisfactory, click Schedule. The Scheduler screen displays. 38 Administrator Guide for Avaya Communication Manager...
Page 39 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 40 If the time synchronization is not satisfactory, click Back and revise the necessary information. For more information about setting time synchronization, see Avaya Communication Manager Call Center Software Automatic Call Distribution (ACD) Guide, 07-300301. 40 Administrator Guide for Avaya Communication Manager...
Page 41: Setting The System Date And Time
Setting the System Date and Time Setting the System Date and Time In our example, we set the date and time to Tuesday, November 5 at 8:30 p.m. standard time. To set the system date and time: 1. Type set time and press Enter. Date and Time screen displays.
Page 42: Using The Bulletin Board
Call Distribution (ACD) Guide, 07-300301. 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 43 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 44: Saving Translations
3. Press Enter to save your changes. Saving Translations Communication Manager retains all translation data in memory while the system is operating. If it goes down, you lose all this translation data. You must save in-memory translation data to the memory card (flash ROM), disk, or tape.
Page 45: Before You Start
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 46 Save translation cannot Repeat the save translation write to the active drive. process for the active drive. Save translation cannot Repeat the save translation write to the standby drive. process for the standby drive. 46 Administrator Guide for Avaya Communication Manager...
Page 47: Performing Backups
461 for information about restoring announcements to 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-300192. Issue 1 June 2005...
Page 48 System Basics 48 Administrator Guide for Avaya Communication Manager...
Page 49: 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 50: Understanding The Dial Plan
4-digit numbers that start with 1 or 2. Let us take a look at an example dial plan so you’ll know how to read your system’s dial plan. The following figure shows an example of a simple dial plan. 50 Administrator Guide for Avaya Communication Manager...
Page 51 Understanding the Dial Plan Figure 14: Dial Plan Analysis Table screen change dialplan analysis Page 1 of 1 DIAL PLAN ANALYSIS TABLE Percent Full: Dialed Total Call Dialed Total Call String Length Type String Length Type attd ____ ____ ____ ____ ____ ____...
Page 52 3. Type 3 in the Dialed String column. Press Tab to move to the next field. 4. Type 4 in the Total Length column. Press Tab to move to the next field. 5. Type ext in the Call Type column. 6. Press Enter to save your changes. 52 Administrator Guide for Avaya Communication Manager...
Page 53 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 54 1. Type change dialplan analysis and press Enter. Dial Plan Analysis Table screen appears. 2. Move the cursor to an empty row. 3. Type 3 in the Dialed String column. Press Tab to move to the next field. 54 Administrator Guide for Avaya Communication Manager...
Page 55 Understanding the Dial Plan 4. Type 2 in the Total Length column. Press Tab to move to the next field. 5. Type fac in the Call Type column. 6. Press Enter to save your changes. Changing feature access codes Feature access codes (FAC) allow users to activate and deactivate features from their phones. A user who knows the FAC for a feature does not need a programmed button to use the feature.
Page 56: Controlling The Features Your Users Can Access
Planning the System 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 57: 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 58: Setting Wan Bandwidth Limits Between Network Regions
Planning the System 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 59 Setting WAN Bandwidth Limits Between Network Regions The bandwidth usage numbers shown above assume 6 bytes for Multilink Point-to-Point Protocol (MP) or Frame Relay Forum (FRF), 12 Layer 2 (L2) header, and 1 byte for the end-of-frame flag on MP and Frame Relay frames for a total of 7 byte headers only. They do not account for silence suppression or header compression techniques, which might reduce the actual bandwidth.
Page 60: Administering Treatment For Denied Or Invalid Calls
8. In the Invalid Number Dialed Intercept field, type announcement. 9. Another blank field appears. 10. In this blank field, type 2045. 11. This is the extension of an announcement you recorded earlier. 12. Press Enter to save your changes. 60 Administrator Guide for Avaya Communication Manager...
Page 61: Setting Up Music-On-Hold
Setting up Music-on-Hold Setting up Music-on-Hold Music-on-Hold automatically provides music to a caller placed on hold. Providing music lets the caller know that the connection is still active. The system does not provide music to callers in a multiple-party connection who are in queue, on hold, or parked. Locally Sourced Announcements and Music The Locally Sourced Announcements and Music feature is based on the concept of audio source groups.
Page 62 4. Press Enter to save your changes. Adding a Music-on-hold Group To add a music-on-hold group: 1. Type add moh-analog-group n, where n is the music-on-hold group number. Press Enter. The system displays the MOH Group screen. 62 Administrator Guide for Avaya Communication Manager...
Page 63 Setting up Music-on-Hold Figure 17: MOH Group screen change moh-analog-group 2 Page 1 of x MOH Group 2 Group Name: MOH SOURCE LOCATION 2. In the Group Name field, type in an identifier name for the music-on-hold group. 3. In the MOH Source Location numbered fields, type in the music-on-hold VAL or vVAL source locations.
Page 64 Before you can administer tenants in your system, Tenant Partitioning must be set to y on the System-Parameters Customer-Options screen. This setting is controlled by your license file. 64 Administrator Guide for Avaya Communication Manager...
Page 65 Setting up Music-on-Hold The following example illustrates how to administer the system to allow one tenant to play Country music for callers on hold, and another to play Classical music. 1. Type change music-sources and press Enter. Music Sources screen appears. Figure 19: Music Sources screen change music-source Music Sources...
Page 66 G.723 codec and administer Music on Hold for this tenant. Create another tenant partition for endpoints that use the G.723 codec and administer silence, news, or other material that does not sound distorted for these endpoints. 66 Administrator Guide for Avaya Communication Manager...
Page 67: 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 68 Now set up the attendant console to receive emergency notification. 7. Type change attendant 1 and press Enter. Attendant Console screen appears. 8. In the feature button area, assign a crss-alert button. 9. Press Enter to save your changes. 68 Administrator Guide for Avaya Communication Manager...
Page 69 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 70: Notifying A Digital Pager Of An Emergency
This is the number of additional times the system tries to send out the alert message in case of an unsuccessful attempt. 6. In the Retry Interval (sec) field, type 30. This is length of time between retries. 70 Administrator Guide for Avaya Communication Manager...
Page 71 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. Issue 1 June 2005...
Page 72: Other Useful Settings
You can allow users to join (bridge) on to a call that rang at their extension and then went to coverage before they could answer. For more information, see "Temporary Bridged Appearance" in Feature Description and Implementation for Avaya Communication Manager, 555-245-205.
Page 73: Controlling The Calls Your Users Can Make And Receive
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 74 4. Press Enter to save your changes. Now we have to define the password. 5. Type change system-parameters features and press Enter. Feature-Related System Parameters screen appears. Press Next Page to find the Automatic Exclusion Parameters section. 74 Administrator Guide for Avaya Communication Manager...
Page 75: Station Lock
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 76 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. 76 Administrator Guide for Avaya Communication Manager...
Page 77: Chapter 3: Managing Telephones
If you do not manage this feature carefully, its unauthorized use may 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 78 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. 78 Administrator Guide for Avaya Communication Manager...
Page 79: 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 80 (DID) or reached via a central telephone number. Be sure to note your port and extension selections on your system’s paper records. 80 Administrator Guide for Avaya Communication Manager...
Page 81 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 82 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-300191. When the Station screen appears, you see the extension number and some default field values.
Page 83: 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 84 Fill in the information on the Agent LoginID screen. For more information, see Avaya Communication Manager Call Center Software Automatic Call Distribution (ACD) Guide, 07-300301.
Page 85: 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 86: 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 87: Upgrading Phones
Upgrading Phones You may also find it handy to set up multiple phones for testing applications and features before you provide them to users. You may 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 may want to have examples of each of these phones so you can test new features or options.
Page 88: Using Actr To Move Phones
Using ACTR to Move Phones Automatic Customer Telephone Rearrangement (ACTR) allows a telephone to be unplugged from one location and moved to a new location without additional administration in Avaya Communication Manager. Communication Manager automatically associates the extension to the new port. ACTR works with 6400 Serialized phones and with the 2420/2410 phones. The 6400 Serialized telephone is stamped with the word "Serialized"...
Page 89: Detailed Description
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 90: Design Considerations
Managing Telephones 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 91: Using Tti To Move Phones
Using TTI to Move Phones Figure 27: Station screen change station 1234 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 Data Restriction? n...
Page 92 (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 93 Using TTI to Move Phones To merge an extension to a telephone with TTI, complete the following steps from the telephone you want to merge: 1. Dial the TTI merge FAC. - If the code is correct, you receive dial tone. - If the code is not correct, you receive intercept tone.
Page 94 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 95: Removing Phones
Removing Phones Removing Phones Before you physically remove a telephone from your system, check the telephone’s status, remove it from any group or usage lists, and then delete it from the system’s memory. For example, to remove a telephone at extension 1234: 1.
Page 96: Adding A Fax Or Modem
4444. To add a fax machine as extension 444, complete the following steps: 1. Type add station 4444 and press Enter. 2. In the Type field, type fax. 96 Administrator Guide for Avaya Communication Manager...
Page 97 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 98: Adding An Ip Softphone
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 99 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 100 3. Press Enter to save your work. Now, you need to administer the telephone (DCP) extension. To do so, complete the following steps: 1. Type add station 3001 and press Enter. Station screen appears. 100 Administrator Guide for Avaya Communication Manager...
Page 101 Adding an IP Softphone Figure 29: Station screen add station 3001 Page 1 of STATION Extension: 3001 Lock Messages? n BCC: 0 Type: 6408D Security Code: * TN: 1 Port: X Coverage Path 1: COR: 1 Name: Coverage Path 2: COS: 1 Hunt-to Station: STATION OPTIONS...
Page 102 7. 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 (3010) and password (1234321). 102 Administrator Guide for Avaya Communication Manager...
Page 103: Adding An Ip Telephone
Avaya IP Softphone modes. This document is a Portable Document Format (PDF) document that is located in the Overview Document folder on the Avaya IP Softphone Also see Getting Started, located on the Avaya IP Softphone CD for more information on how to install and configure the IP Softphone software.
Page 104 4. In the Security Code field, enter a password for the IP telephone user. Note: Although the system accepts a null password, the IP telephone will not work Note: unless you assign a password. 5. Press Enter to save your work. 104 Administrator Guide for Avaya Communication Manager...
Page 105 Adding an IP Telephone Changing from dual-connect to single-connect IP phones When you have a dual extension telephone and you upgrade to a single extension telephone, you can remove the connection that is no longer used for that telephone. To remove the H.323 connection that is no longer needed, first record the media complex extension number: 1.
Page 106 IP telephone. To prevent an emergency call from an IP telephone: 1. Type change station nnnn, where nnnn is the extension of the telephone you want to modify. Press Enter. The Station screen appears. 106 Administrator Guide for Avaya Communication Manager...
Page 107 2. Type block in the Remote Softphone Emergency calls field and 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 108: 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 109 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 110 Before you start Perform Setting up a signaling group on page 111. To set up the trunk group for your remote office: 1. Type add trunk group 6. The Trunk Group screen appears. 110 Administrator Guide for Avaya Communication Manager...
Page 111 Setting up Remote Office Figure 34: Trunk Group screen add trunk-group next Page 1 of x TRUNK GROUP Group Number: 6___ Group Type: ________ CDR Reports: _ Group Name: ___________________________ COR: __ TN: ___ TAC: __6__ Direction: ________ Outgoing Display? _ Trunk Signaling Type: ____ Dial Access? _ Busy Threshold: ___...
Page 112 R300. 7. In the Near-end Listen Port field, type a port number in the 5000-9999 range. 8. In the Far-end Listen Port field, type 1720. See Getting Started with the Avaya R300 Remote Office Communicator for more details.
Page 113 Setting up Remote Office Setting up Remote Office on network regions Now we will set up a network region and show the connections between regions. Instructions Set up network region 1: 1. Type add ip-network-region 1 and press Enter. IP Network Region screen appears.
Page 114 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. 114 Administrator Guide for Avaya Communication Manager...
Page 115 7. Press Enter to save your changes. Tip: You can set up a telnet session on your remote office administration program to Tip: verify that the telephone is registered. See Getting Started with the Avaya R300 Remote Office Communicator for details. Issue 1 June 2005...
Page 116: 2420/2410 Dcp Telephone
You can copy updated application code into Communication Manager via TFTP over a TCP/IP connection. This eliminates the need to physically remove the telephone and send it to the factory for the firmware update. This feature is available on all of the servers running Avaya Communication Manager.
Page 117 2420/2410 DCP telephone Figure 39: TFTP Server Configuration screen change tftp-server Page 1 of 1 TFTP Server Configuration Local Node Name: TFTP Server Node Name: TFTP Server Port: 69 File to Retrieve: File Status: File Size: Filename in Memory: 7. In the Local Node Name field, enter the valid local node name from the IP Node Names screen.
Page 118 Firmware Download in Progress, the amount of the file downloaded, and a timer. The telephone displays error messages and a success message before rebooting. 8. When the download completes, the telephone reboots and is released from the busy-out state. 118 Administrator Guide for Avaya Communication Manager...
Page 119 2420/2410 DCP telephone Downloading firmware to multiple stations You can download firmware to multiple stations of the same type, either 2410 or 2420 DCP telephones. Download firmware to as many as 1000 stations per download schedule. You can schedule a specific time for the download, or you can administer the download to run immediately.
Page 120 You can use the disable firmware download command to disable any active download schedule. To disable active downloads: Type disable firmware download. ● This command disables any active download schedule and the system displays Command successfully completed at the bottom of the screen. 120 Administrator Guide for Avaya Communication Manager...
Page 121: 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 phones.
Page 122 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. 122 Administrator Guide for Avaya Communication Manager...
Page 123: Telephone Feature Buttons
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 phones.
Page 124 CDR account codes allow the system to associate and track calls according to a particular project or account number. admin Admin Administration: allows a user to program the feature buttons on their 6400-series telephone. 2 of 21 124 Administrator Guide for Avaya Communication Manager...
Page 125 Telephone Feature Buttons Table 2: Telephone feature buttons (continued) Button name Button label Description Maximum after-call After Call After Call Work Mode: allows an agent 1 per split Grp:___ Work to temporarily be removed from call group distribution in order for the agent to finish ACD-related activities such as completing paperwork.
Page 126 Auto-In Mode: allows the user to 1 per split (Group: __) become automatically available for group new ACD calls upon completion of an ACD call. Grp: The split group number for ACD. 4 of 21 126 Administrator Guide for Avaya Communication Manager...
Page 127 Telephone Feature Buttons Table 2: Telephone feature buttons (continued) Button name Button label Description Maximum auto-wkup Auto Wakeup Automatic Wakeup (display button): 1 per allows attendants, front-desk users, station and guests to request a wakeup call to be placed automatically to a certain extension (may not be a VDN extension) at a later time.
Page 128 Caller Info (display button) Used with Call 1 per Prompting to allow users to display station information collected from the originator. 6 of 21 128 Administrator Guide for Avaya Communication Manager...
Page 129 Telephone Feature Buttons Table 2: Telephone feature buttons (continued) Button name Button label Description Maximum cas-backup CAS Backup Centralized Attendant Service 1 per Backup: used to redirect all CAS calls station to a backup extension in the local branch if all RLTs are out-of-service or maintenance busy.
Page 130 Data Extension: sets up a data call. 1 per data- May be used to pre-indicate a data call extension or to disconnect a data call. May not group be a VDN or ISDN-BRI extension. 8 of 21 130 Administrator Guide for Avaya Communication Manager...
Page 131 Telephone Feature Buttons Table 2: Telephone feature buttons (continued) Button name Button label Description Maximum date-time Date Time Date and Time (display button): 1 per displays the current date and time. Do station not assign this button to 6400-series display phones as they normally show the date and time.
Page 132 1 per Disturb mode. station drop Drop Allows users to drop calls. Users can drop calls from automatic hold or drop the last party they added to a conference call. 10 of 21 132 Administrator Guide for Avaya Communication Manager...
Page 133 Telephone Feature Buttons Table 2: Telephone feature buttons (continued) Button name Button label Description Maximum exclusion Exclusion Exclusion: allows multiappearance 1 per telephone users to keep other users station with appearances of the same extension from bridging onto an existing call. If the user presses the Exclusion button while other users are already bridged onto the call, the other users...
Page 134 LED is on for offhook state and off (dark) for onhook state. hunt-ns Hunt Group Hunt-Group Night Service: places a 3 per hunt (Grp: ___) hunt-group into night service. Grp: group Hunt group number. 12 of 21 134 Administrator Guide for Avaya Communication Manager...
Page 135 Telephone Feature Buttons Table 2: Telephone feature buttons (continued) Button name Button label Description Maximum in-call-id Coverage The Coverage Incoming Call 1 per (Type: __ (group #, type, Identification (ICI) button allows a group-type Grp: ___) name, or ext member of a coverage answer group per group or hunt group to identify an incoming call to that group even though the...
Page 136 ACD group calls upon completion of an ACD call by automatically placing the agent in the after call work mode. Grp: The split group number for ACD. 14 of 21 136 Administrator Guide for Avaya Communication Manager...
Page 137 Telephone Feature Buttons Table 2: Telephone feature buttons (continued) Button name Button label Description Maximum mct-act Malicious Call Trace Activation: sends 1 per Activation a message to the MCT control station extensions that the user wants to trace a malicious call. MCT activation also starts recording the call, if your system has a MCT voice recorder.
Page 138 Night Service station mode. noans-alrt RONA Redirection on No Answer Alert: 1 per hunt indicates a Redirection on No Answer group timeout has occurred for the split. 16 of 21 138 Administrator Guide for Avaya Communication Manager...
Page 139 Telephone Feature Buttons Table 2: Telephone feature buttons (continued) Button name Button label Description Maximum no-hld-cnf No Hold No Hold Conference: can 1 per Conference automatically conference another station party while continuing the existing call. normal Normal Mode Normal (display button): places the 1 per station’s display into normal call station...
Page 140 Service Service Observing: activates Service 1 per Observing Observing. Used to toggle between a station listen-only and a listen-talk mode. 18 of 21 140 Administrator Guide for Avaya Communication Manager...
Page 141 Telephone Feature Buttons Table 2: Telephone feature buttons (continued) Button name Button label Description Maximum signal Signal (name Signal: allows the user to use one 1 per (Ext: ___) button to manually signal the signal ext #) associated extension. The extension extension cannot be a VDN extension.
Page 142 ID (optional): specify a split number, trunk group number, agent extension, or VDN extension 20 of 21 142 Administrator Guide for Avaya Communication Manager...
Page 143 Telephone Feature Buttons Table 2: Telephone feature buttons (continued) Button name Button label Description Maximum whisp-act Whisper Page Whisper Page Activation: allows a 1 per Activation user to make and receive whisper station pages. A whisper page is an announcement sent to another extension who is active on a call where only the person on the extension hears the announcement;...
Page 144: Adding Abbreviated Dialing Lists
As an example, we will program a new group list: 1. Type add abbreviated-dialing group next and press Enter. Abbreviated Dialing List screen appears. In our example, the next available group list is group 3. 144 Administrator Guide for Avaya Communication Manager...
Page 145 Adding Abbreviated Dialing Lists Figure 44: Abbreviated Dialing List screen ABBREVIATED DIALING LIST Group List: 3 Size (multiple of 5): ___ Program Ext: ________ Privileged? _ DIAL CODE 01: ________________________ 02: ________________________ 03: ________________________ 04: ________________________ 05: ________________________ 2. Enter a number (in multiples of 5) in the Size field. This number defines the number of entries on your dialing list.
Page 146 Alternatively, you can assign an abbreviated dialing button to this station that allows the user press one button to dial a specific stored number on one of their three assigned abbreviated lists. 146 Administrator Guide for Avaya Communication Manager...
Page 147 Adding Abbreviated Dialing Lists Fixing problems Problem Possible causes Solutions A user cannot The specific list Resolution: ● access a dial may not be 1. Type display station list assigned to the nnnn, where nnnn is the user’s telephone. user’s extension. Press Enter.
Page 148 4. If the dial code is wrong, press Cancel and use the appropriate change command to re-access the abbreviated dialing list. Correct the number and press Enter. 2 of 2 148 Administrator Guide for Avaya Communication Manager...
Page 149: 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-300191. Related topics For more information, see "Abbreviated Dialing"...
Page 150 If you want all bridged appearances to either ring or not ring, leave the default n. ● 5. Move to Bridge Call Alerting. If you want the bridged appearance to ring when a call arrives at the primary telephone, type y. Otherwise, leave the default n. 150 Administrator Guide for Avaya Communication Manager...
Page 151 Setting up Bridged Call Appearances 6. Complete the appropriate field for your telephone type. If. . . Then. . . your primary telephone is move to the Line Appearance field analog and enter abrdg-appr your primary telephone is move to the Button Assignments digital field and enter brdg-appr 7.
Page 152 If you do not want the bridged appearance to ring, leave the default n. ● 11. Press Enter to save your changes. To see if an extension has any bridged call appearances assigned, type list bridge and the extension, and press Enter. 152 Administrator Guide for Avaya Communication Manager...
Page 153: Setting Up An Extension To Cellular Feature Access Button
Setting up an Extension to Cellular Feature Access Button More information Following are a list of example situations where you might want to use bridged appearances. A secretary making or answering calls on an executive’s primary extension ● These calls can be placed on hold for later retrieval by the executive, or the executive can simply bridge onto the call.
Page 154 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 Administrator Guide, 210-100-500. 154 Administrator Guide for Avaya Communication Manager...
Page 155: Setting Up Terminal Self Administration
Setting up Terminal Self Administration Setting up Terminal Self Administration Terminal self-administration (TSA) allows users to administer some of their own feature buttons from their telephones. TSA is available for 6400-series, and 4612 and 4624 telephones. Users are prompted, via the telephone’s display, to choose features to assign to buttons on their telephones.
Page 156 ● 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 157 Setting up Terminal Self Administration Since the telephone must be on-hook to go into the Admin mode, the Headset On/Off ● button must be in the OFF position. A telephone that is in the Admin mode of TSA cannot be remotely unmerged by the PSA ●...
Page 158 Managing Telephone Features 158 Administrator Guide for Avaya Communication Manager...
Page 159: 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 may have a basic or enhanced version of these consoles.
Page 160 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 160 Administrator Guide for Avaya Communication Manager...
Page 161 Attendant Consoles Figure 51: 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 162 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. 162 Administrator Guide for Avaya Communication Manager...
Page 163 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 164: 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 165 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 166: 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 166 Administrator Guide for Avaya Communication Manager...
Page 167 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 168 Busy (trunk or busy-ind (TAC/Ext: _) 1 per Indication [status extension#) TAC/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 168 Administrator Guide for Avaya Communication Manager...
Page 169 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 170 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 170 Administrator Guide for Avaya Communication Manager...
Page 171 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 172 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. 172 Administrator Guide for Avaya Communication Manager...
Page 173: 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 174: 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. 174 Administrator Guide for Avaya Communication Manager...
Page 175: 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 176 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. 176 Administrator Guide for Avaya Communication Manager...
Page 177: 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 may consist of either a billing number that sometimes is referred to as Automatic Number Identification (ANI), or a calling party number.
Page 178: Displaying Iclid Information
3. Press Next Page and type *ANI*DNIS in the Incoming Tone (DTMF) ANI field. 4. Press Enter to save your changes. 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 179 Displaying ICLID Information Instructions We will set up the analog diod trunk group 1 to receive calling party information and display the calling party number on the telephone of the person called. 1. Type change trunk group 1. The Trunk Group screen for trunk group 1 appears. The Group Type field is already set to diod.
Page 180: Changing The Display Language
Local Remote Local Remote 1: 9 2: 82 HUNDREDS SELECT BUTTON ASSIGNMENTS 2. In the Display Language field, enter the display language you want to use. 3. Press Enter to save your changes. 180 Administrator Guide for Avaya Communication Manager...
Page 181 6. Press Enter to save your changes. Administering Unicode display To use Unicode display languages, you must have the appropriate Avaya Unicode Message files loaded on Communication Manager. These files are named avaya_unicode.txt and custom_unicode.txt. As of the January 2005 2.2 Release of Communication Manager, the following languages are available using Unicode display: English, Japanese, Chinese, Russian, German, Hungarian, Dutch, and Czech.
Page 182 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 183 Changing the Display Language The Unicode Hunt Group Name is associated with the name administered in the Group ● Name field on the Hunt Group screen. You must use MSA. The Unicode Station Name is associated with the name administered in the Name field on ●...
Page 184 Taml 00008000 0C00..0C7F Telugu Telu 00010000 0C80..0CFF Kannada Knda 00020000 0D00..0D7F Malayalam Mlym 00040000 0D80..0DFF Sinhala Sinh 00080000 0E00..0E7F Thai Thai 00100000 0E80..0EFF Laoo 0F00..0FFF Tibetan 00200000 1000..109F Myanmar Mymr 2 of 6 184 Administrator Guide for Avaya Communication Manager...
Page 185 Changing the Display Language Script Script tag Start .. End Script or block name SAT screen name (hex) Codes (note 1) 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 16A0..16FF Runic 00800000...
Page 186 CJKV Radicals Supplement 08000000 10000000 20000000 40000000 04000000 2F00..2FDF Kangxi Radicals 08000000 10000000 20000000 40000000 2FF0..2FFF Idographic Description Characters 04000000 3000..303F CJKV Symbols and 08000000 Punctuation 10000000 20000000 40000000 04000000 3040..309F Hiragana 4 of 6 186 Administrator Guide for Avaya Communication Manager...
Page 187 Changing the Display Language Script Script tag Start .. End Script or block name SAT screen name (hex) Codes (note 1) 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 04000000...
Page 188 FE30..FE4F CJK Compatibility Forms 08000000 10000000 20000000 40000000 FE50..FE6F Small Form Variants 00000100 FE70..FEFF Arabic Presentation Forms-B 04000000 FF00..FFEF Halfwidth and Fullwidth 08000000 Forms 10000000 20000000 40000000 80000000 FFF0..FFFF Specials 6 of 6 188 Administrator Guide for Avaya Communication Manager...
Page 189 Related topics See the "Telephone Displays" and the "Administrable Display Languages" feature descriptions in the Feature Description and Implementation for Avay Communication Manager for more information about choosing the language for messages on your display phones and for mapping US English to Cyrillic (for Russian), Katakana (for Japanese), European, or Ukrainian characters.
Page 190: 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 191: Chapter 7: Handling Incoming Calls
● not available or not accepting calls provides the order in which Avaya Communication Manager redirects calls to alternate ● phones or terminals establishes up to 6 alternate termination points for an incoming call ●...
Page 192 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 and press Enter. Coverage Path screen appears. 192 Administrator Guide for Avaya Communication Manager...
Page 193 Setting up Basic Call Coverage Figure 63: Coverage path screen change coverage path 2 Page 1 of COVERAGE PATH Coverage Path Number: 2 Hunt After Coverage: n Next Path Number: ___ Linkage: ___ COVERAGE CRITERIA Station/Group Status Inside Call Outside Call Active? Busy? Don’t Answer?
Page 194 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? 194 Administrator Guide for Avaya Communication Manager...
Page 195: 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 196 Immediate Redirection On Receipt Of PROGRESS Inband Information? n 2. 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 197 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 198 If you do not have the Coverage of Calls Redirected Off-Net feature, the system cannot monitor the call once it leaves the network. The call ends at the remote coverage point. 7. Press Enter to save your changes. 198 Administrator Guide for Avaya Communication Manager...
Page 199 Setting up Advanced Call Coverage Related topics For more information on coverage, see "Call Coverage" in Feature Description and Implementation for Avaya Communication Manager, 555-245-205. 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.
Page 200 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. 200 Administrator Guide for Avaya Communication Manager...
Page 201 Setting up Advanced Call Coverage Creating coverage answer groups You can create a coverage answer group so that up to 8 phones 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 202: 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. 202 Administrator Guide for Avaya Communication Manager...
Page 203 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 204 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. 204 Administrator Guide for Avaya Communication Manager...
Page 205 Setting up Call Forwarding 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. 1.
Page 206 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. 206 Administrator Guide for Avaya Communication Manager...
Page 207: 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 208 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 and press Enter. Listed Directory Numbers screen appears. 208 Administrator Guide for Avaya Communication Manager...
Page 209 Setting up Night Service Figure 74: Listed Directory Number screen Page 1 of LISTED DIRECTORY NUMBERS Night Destination: 51002 Name 1: 51001 Attendant 5. In the Night Destination field, add the night destination on the listed directory telephone. In our example, type 51002. 6.
Page 210 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 211 Setting up Night Service Figure 76: Attendant Console screen ATTENDANT CONSOLE 2 Type: console Name: 27 character attd cons name Extension: 1000 Group: 1 Auto Answer: none Console Type: principal TN: 1 Data Module? n Port: 01C1106 COR: 1 Disp Client Redir? n COS: 1 Display Language: english DIRECT TRUNK GROUP SELECT BUTTON ASSIGNMENTS (Trunk Access Codes)
Page 212 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 and press Enter. Console Parameters screen appears. 212 Administrator Guide for Avaya Communication Manager...
Page 213 You need a ringing device and 1 port on an analog line circuit pack. See the Hardware Guide for Avaya Communication Manager, 555-245-207 for more information on the circuit pack. To set the feature access code for TAAS: 1.
Page 214 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 and press Enter.
Page 215 Setting up Night Service Figure 80: 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): 01A0702 CAS: none Night Service Act.
Page 216 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. 216 Administrator Guide for Avaya Communication Manager...
Page 217 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 218 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. 218 Administrator Guide for Avaya Communication Manager...
Page 219 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 220 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 220 Administrator Guide for Avaya Communication Manager...
Page 221: Adding Call Pickup
Adding Call Pickup Adding Call Pickup To give your users the ability to pickup other users’ calls, you may want to use Call Pickup. To do this, you need to define a call pickup group. Users may want to be able to pick up a call that is ringing at a nearby desk. Call Pickup provides 3 ways to pick up calls ringing at another telephone: With Call Pickup, you create a call pickup group.
Page 222 To set up a telephone so that the user can pick up calls with Directed Call Pickup, you need to determine if directed call pickup is enabled on your system and make sure that the user’s telephone has a COR that allows directed call pickup. 222 Administrator Guide for Avaya Communication Manager...
Page 223 Adding Call Pickup To determine if Directed Call Pickup is enabled on your system: 1. Type change system-parameters features and press Enter. Feature-Related System Parameters screen appears. 2. Move to the Directed Call Pickup? field and enter y. 3. Press Enter to save the changes. Now we will modify extension 4444 to allow directed call pickup.
Page 224 9. Type change extended-pickup-group n, where n is the number of the extended pickup group to change. Press Enter. Extended Pickup Group screen appears. 224 Administrator Guide for Avaya Communication Manager...
Page 225 Adding Call Pickup Figure 88: Extended Pickup Group screen change extended-pickup-group 1 Page 1 of EXTENDED PICKUP GROUP Extended Group Number: 56 Pickup Pickup Group Pickup Pickup Group Number Number Number Number _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____...
Page 226 9. Add extended members as for other pickup features. 10. Type change extended-pickup-group n , where n is the number of the extended pickup group to change, and press Enter. Extended Pickup Group screen appears. 226 Administrator Guide for Avaya Communication Manager...
Page 227 Adding Call Pickup Figure 89: Extended Pickup Group screen change extended-pickup-group 1 Page 1 of EXTENDED PICKUP GROUP Extended Group Number: 56 Pickup Pickup Group Pickup Pickup Group Number Number Number Number _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____...
Page 228: Managing Hunt Groups
So, we’ll set up a helpline hunt group so anyone within the company can call extension 1200 for help with a telephone. We will assign 3 people (agents) and their extensions to our helpline. We want calls to go to the first available person. 228 Administrator Guide for Avaya Communication Manager...
Page 229 Managing Hunt Groups Instructions To set up our helpline hunt group: 1. Type add hunt-group next and press Enter. Hunt Group screen appears. The Group Number field is automatically filled in with the next hunt group number. Figure 90: Hunt Group screen Page 1 of X HUNT GROUP Group Number: 4__...
Page 230 Ext field. The system uses this screen to determine the hunting sequence. 7. Press Enter to save your changes. The Name fields are display-only and do not appear until the next time you access this hunt group. 230 Administrator Guide for Avaya Communication Manager...
Page 231 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 232 In our example, type 10. 4. In the Calls Waiting Threshold field, type the maximum number of calls that can be in the queue before the system flashes the queue status buttons. In our example, type 5. 232 Administrator Guide for Avaya Communication Manager...
Page 233 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 234 Calling Party Number to INTUITY AUDIX? _ LWC Reception: _______ AUDIX Name: _______ Messaging Server Name: _______ First Announcement Extension: 1234 ___ Delay (sec): 20 Second Announcement Extension: ________ Delay (sec): __ Recurring? _ 234 Administrator Guide for Avaya Communication Manager...
Page 235: 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 the Avaya Communication Manager Call Center Software Call Vectoring and Expert Agent Selection (EAS) Guide, 07-300303.
Page 236 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 237 The information in the heading of the Call Vector screen is display only. Use the 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. Issue 1 June 2005...
Page 238 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 239 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 240 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 241 Managing Vectors and VDNs To let callers leave messages, write this vector (step 7): Figure 98: Call Vector screen CALL VECTOR Number: Name: main number calls Attendant Vectoring? n Meet-me Conf? y Lock? n Basic? y EAS? n G3V4 Enhanced? y ANI/II-Digits? y ASAI Routing? n Prompting? y...
Page 242 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 243: Inserting A Step
Managing Vectors and VDNs To let callers connect to an extension, write this kind of vector: Figure 100: Call Vector screen CALL VECTOR Number: Name: main number calls Attendant Vectoring? n Meet-me Conf? y Lock? n Basic? y EAS? n G3V4 Enhanced? y ANI/II-Digits? y ASAI Routing? n...
Page 244 TTY caller to the TTY split (or hunt group). For more information on recording TTY announcements, see Managing Announcements on page 451. In the following example, split 47 (hunt group 47) has already been established and consists of TTY-enabled agents. 244 Administrator Guide for Avaya Communication Manager...
Page 245 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 246 2. To see all current vector events, press Enter. Indicate the events that you want to see by completing the Report Period and Search Option fields. See the Avaya Communication Manager Call Center Software Call Vectoring and Expert Agent Selection (EAS) Guide, 07-300303, for more information.
Page 247 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 248 Meas Annc Adj 1st 2nd 3rd Tech Support 5000 none Customer Serv. 5001 none New Orders 5002 none 2. Each VDN maps to one vector. Several VDNs can map to the same vector. 248 Administrator Guide for Avaya Communication Manager...
Page 249: Understanding Automatic Call Distribution
Understanding Automatic Call Distribution Understanding Automatic Call Distribution Automatic Call Distribution (ACD) is an Avaya Communication Manager feature used in many contact centers. ACD gives you greater flexibility to control call flow and to measure the performance of agents. ACD systems operate differently from non-ACD systems, and they can be much more complex.
Page 250: Assigning A Terminating Extension Group
3. In the Group Name field, type advertising. This is the name of the group. 4. In the Coverage Path field, type 5. This is the number of the call coverage path for this group. 250 Administrator Guide for Avaya Communication Manager...
Page 251: 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 252: Managing Calling Privileges
Class of Restriction screen appears. 4. In the FRL field, type 7 and press Enter to save your changes. Now all users with COR 7 will have the highest level of calling permissions. 252 Administrator Guide for Avaya Communication Manager...
Page 253: 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 254: Displaying Ars Analysis Information
1. Type display ars analysis 1 and 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 255 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 256 Digits may 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 257 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 258 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 259 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 260 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 261 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 262 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 and press Enter. AAR and ARS Digit Analysis Table screen beginning with 4 appears.
Page 263: 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 that the Multinational...
Page 264 10. Type 212 in the NANP field in the Number 2 row. In our example, 212 is the local area code for New York, location 2. 11. Press Enter to save your changes. 264 Administrator Guide for Avaya Communication Manager...
Page 265: 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 266 Routing Outgoing Calls 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 267 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 268: Modifying Call Routing
1. Type list ars route-chosen 14152223333 and 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. 268 Administrator Guide for Avaya Communication Manager...
Page 269 Modifying Call Routing Figure 114: 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 270 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 270 Administrator Guide for Avaya Communication Manager...
Page 271: Overriding Call Restrictions
Overriding Call Restrictions Instructions To prevent callers from placing calls to Colombia (57): 1. Type change ars analysis 01157 and 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 272: Defining Ars Partitions
ARS partitioning allows you to provide different call routing for a group of users or for specific phones. 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 273 Defining ARS Partitions Before you start Ensure that the Tenant Partitioning field on the System Parameters Customer Options ● screen is y. Ensure that the Time of Day Routing field on the System Parameters Customer ● Options screen is n. Setting up partition groups Let us say you allow your employees to make local, long distance, and emergency calls.
Page 274 1800 numbers. Assigning a telephone to a partition group To assign an extension to a partition group, first assign the partition group to a COR, and then assign that COR to the extension. 274 Administrator Guide for Avaya Communication Manager...
Page 275 Defining ARS Partitions Instructions To assign a Class of Restriction (COR) to partition group 2: 1. Type list cor and press Enter. The Class of Restriction Information screen appears. Figure 119: Class of Restriction Information screen CLASS OF RESTRICTION INFORMATION COR Description supervisor telecommuting...
Page 276 Now assign COR 3 to the lobby telephone at extension 1234: 1. Type change station 1234 and press Enter. Station screen for 1234 appears. 2. In the COR field, enter 3. 3. Press Enter to save your changes. 276 Administrator Guide for Avaya Communication Manager...
Page 277: 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 278 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 767 to see where to assign this field. 278 Administrator Guide for Avaya Communication Manager...
Page 279 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 280: 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 281 Location by Region Figure 123: 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 282: Management Screen
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. 282 Administrator Guide for Avaya Communication Manager...
Page 283 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 1 June 2005...
Page 284 Routing Outgoing Calls 284 Administrator Guide for Avaya Communication Manager...
Page 285: 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 286: About This Document
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 287: List Of Terms
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 288 It may 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 289 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 290 Managing MultiMedia Calling Figure 127: 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 290 Administrator Guide for Avaya Communication Manager...
Page 291 Multimedia Applications Server Interface Figure 128: 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 1 June 2005...
Page 292 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 293 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 the Maintenance for Avaya Communication Manager and DEFNITY®/S8000-series Media Server document for your specific model and release.
Page 294 Max Number of NCA TSC - For MASI, this must be 1. ● Max number of CA TSC - Leave the default of 0. ● Trunk Group For NCA TSC - This can be left blank. ● 294 Administrator Guide for Avaya Communication Manager...
Page 295 Enabled - Enter y to enable the administered NCA-TSC. You may 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 may cause your system to alarm, if other administration is not finished.
Page 296 Primary D-Channel — Port location of the Primary D-channel ● TSC Index — The number of the MASI TSC within the signaling group ● Local Ext. — Avaya Communication Manager extension associated with the TSC ● Enabled — Indicates the state of the connection - enabled (y/n) ●...
Page 297 Multimedia Applications Server Interface Step 6 — Administer ISDN-PRI trunk group Use the command add trunk-group xxx to access the Trunk Groups screen. For a more detailed description of the ISDN-PRI trunk group, see Trunk Group on page 1535. Establish an ISDN-PRI trunk group with the following attributes: Page 1 Group Type = isdn-pri ●...
Page 298 (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 299 Multimedia Applications Server Interface Group Number - This field displays the MASI trunk group number. This is the number ● assigned when executing the add masi trunk-group command. CDR Reports - Valid entries are y, n, and r. Default is y. ●...
Page 300 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 301 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 302 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 139: MASI Terminal screen — page 3...
Page 303 How to list and status 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 304 This command displays the extension number and type (attendant, masi-terminal, etc.), as well as other information about the extension. Figure 143: List extension type EXTENSION TYPE Cv1/ Type Name ---- ---- ---- 1234 masi-terminal 4077 term-masi-path-call 304 Administrator Guide for Avaya Communication Manager...
Page 305 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 306 MASI terminals. 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 307 Multimedia Applications Server Interface Call Detail Recording Using the MASI link, Avaya Communication Manager is able to track call detail information for calls made using MMCX terminals and interfaces. CDR records all calls originating from or terminating at a MASI terminal. MASI CDR does not record ineffective call attempts when all MASI paths are busy.
Page 308 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 may drop without affecting the other conferees.
Page 309 MMCX trunks are not monitored by ASAI. It may 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 may 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 310 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 311 Message Retrieval — MMCX users can only retrieve messages through AUDIX ● messaging. Music on Hold — Music on hold will only be available if an Avaya Communication Manager ● station has placed the call on hold. Issue 1 June 2005...
Page 312: Troubleshooting
Do Not Disturb — MASI terminals cannot activate Do Not Disturb. ● Multimedia features Multimedia Call Handling — Avaya MMCH users are not able to make H.320 calls to MASI ● terminals over the MASI link. Calls between MMCX terminals and MMCH terminals are voice only.
Page 313: 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 may happen if the server running Communication Manager is rebooted or if the MASI interface is administered before the MMCX is properly administered.
Page 314 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. 314 Administrator Guide for Avaya Communication Manager...
Page 315 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 145: Enhanced MMCH service link DEFINITY...
Page 316: Feature Description
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 317: Physical Installation
● 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 318 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 may 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 319 Typical Multimedia Call handling ESM Connections page 319 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 320 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 321 Multimedia Call Handling 7. Administer early answer and H.320 flag for stations, the early answer flag for hunt groups, and the multimedia flag for vectors as appropriate. 8. Train end users. 9. Monitor traffic and performance. Related screens System-Parameters Customer-Options ●...
Page 322 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. 322 Administrator Guide for Avaya Communication Manager...
Page 323: Administration Commands
Multimedia Call Handling Administration commands System-Parameters Customer-Options To enable the MMCH feature, you need to purchase a new license file. System-Parameters Features screen The default bandwidth for MMCH calls is defined on the System-Parameters Features screen. Note: Originating a multimedia call with the mm-call button will originate a call Note: according to the Default Multimedia Parameters selected on the System Parameters -Features screen.
Page 324 XID and MIM Support — Valid entries are y (default) and n. These fields must be set to n. ● 324 Administrator Guide for Avaya Communication Manager...
Page 325 Service Link Mode - The service link is the combined hardware and software multimedia ● connection between an Enhanced mode complex’s H.320 DVC system and the Avaya DEFINITY Server which terminates the H.320 protocol. A service link is never used by a Basic mode complex H.320 DVC system.
Page 326 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 327 Multimedia Call Handling All of the multimedia specific feature buttons have a corresponding feature access code except mm-pcaudio and mm-cfwd. The mm-pcaudio feature can only be used via button. ● The mm-cfwd button may be replaced by the standard "call forward" FAC followed by the ●...
Page 328 - 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 329 Multimedia Call Handling ESM T.120 Server Administration Figure 149: DS1 Circuit Pack screen change ds1 1c09 Page 1 of DS1 CIRCUIT PACK Location: 01C09 Name: Bit Rate: 2.048 Line Coding: hdb3 Signaling Mode: isdn-pri Connect: pbx Interface: network Country Protocol: 1 CRC? y Idle Code: 11111111 DCP/Analog Bearer Capability: 3.1kHz...
Page 330 To determine ESM link status, enter the following commands from the system administration terminal: 1.Status esm 2.Status signaling-group 3.List MMI Note: When you move ESM circuit packs, you MUST remove the DS1 and signaling Note: group translations. You cannot use the change circuit pack command. 330 Administrator Guide for Avaya Communication Manager...
Page 331: 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 332 B-channel. Note: The mm-call feature button is generally used by stations that are part of an Note: Enhanced multimedia complex, but may be used by any station to originate a multimedia call. 332 Administrator Guide for Avaya Communication Manager...
Page 333 Understanding the Multimedia Complex 3. Multimedia Call feature access code. For stations that do not have an administered mm-call button, the Multimedia call feature access code may be used instead. The user goes off-hook on the station, waits for dialtone, then dials the MM-call FAC, receives dialtone again and then dials the call normally.
Page 334 Note: The mm-parameter selection FAC is generally used by stations that are part of an Note: Enhanced multimedia complex, but may be used by any station to originate a dual address multimedia call. 334 Administrator Guide for Avaya Communication Manager...
Page 335 Understanding the Multimedia Complex 7. Dialing sequences that include TACs, AAR, ARS, Authorization codes, CDR account codes, FRLs 1. Single address with TAC Dial mm-call button or FAC, Hear dialtone ● Dial TAC, Dial destination digits ● 2. Dual address with TAC Dial mm-multinbr button or FAC, Hear dialtone ●...
Page 336 If an H.320 call is directed to a telephone with H.320 set to n, the system denies the call. You can assign H.320 conversion to any voice station. 336 Administrator Guide for Avaya Communication Manager...
Page 337 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 338 If the principal station’s coverage path include a remote coverage point, the multimedia call will cover off-switch as voice only. If the call is unanswered off-switch and proceeds to the next coverage point on-switch, the multimedia nature of the call is preserved. 338 Administrator Guide for Avaya Communication Manager...
Page 339 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 may participate in a single data conference, and up to 24 parties may use the ESM facilities for data collaboration at any given time.
Page 340 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 may be any combination of Enhanced multimedia complexes, Basic multimedia complexes or stand-alone H.320 DVC systems.
Page 341 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 342 Basic mode complex data extensions or stand-alone data extensions may 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 343 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 344 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. ISDN also provides the bearer capability on a call by call basis which can be used to distinguish voice calls from multimedia calls.
Page 345: Enhanced Mode Mm Complex
The number may 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 or 64K data call, Communication Manager recognizes it as a multimedia call, inserts resources to terminate the H.320 protocol, and alerts the voice station with a multimedia call.
Page 346 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 347 Enhanced Mode MM Complex The user now dials the destination address digits. The destination address may be provided by dialing digits, using abbreviated dial entries, last number dialed, station busy indicators, etc. Originating a multimedia call with the mm-call button will originate a call according to the Default Multimedia Parameters selected on the System Parameters Features screen.
Page 348 56K digital facilities, the MM parameter selection FAC can be used to select a bearer and bandwidth of 2x56 for this specific call. 348 Administrator Guide for Avaya Communication Manager...
Page 349 Enhanced Mode MM Complex The MM parameter selection FAC may be used in conjunction with the mm-multinbr button or FAC to make a single or dual address multimedia call at the desired bearer and bandwidth. The user goes off-hook and dials the MM-parameter selection feature access code.
Page 350 Answering multimedia calls below. 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 351 H.320 DVC system for the answering party is not configured for auto-answer, the H.320 DVC system will alert and must also be answered by the user. Note: Avaya recommends, but does not require, that Enhanced mode complexes place Note: their desktop video system into an auto-answer mode of operation.
Page 352 Additional voice or video parties may be added by repeating these steps. Data Collaboration Once you have established a multi-point video conference, multi-point T.120 data collaboration may be enabled for that call. This will allow all video parties on the current conference to collaborate. 352 Administrator Guide for Avaya Communication Manager...
Page 353 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 may participate in a single data conference, and up to 24 parties may use ESM facilities for data collaboration at any given time.
Page 354 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 may be any combination of Enhanced multimedia complexes, Basic multimedia complexes or stand-alone H.320 DVC systems.
Page 355 Enhanced Mode MM Complex The mm-pcaudio feature button works very much like a speakerphone on/off button. If the station is off-hook and selects mm-pcaudio, audio is directed to the PC DVC system. The switch-hook may be placed on-hook. If the handset is taken off-hook, the audio moves back to the handset.
Page 356 Other considerations CMS measurements may indicate unusually slow ASA, because of the time required for the system to establish early-answer before offering the call to an agent. 356 Administrator Guide for Avaya Communication Manager...
Page 357 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 358 An Enhanced multimedia complex H.320 DVC endpoint may not be used to originate a call for hotline dialing. In order to setup a video hotline function with an Enhanced mode complex, the hotline number administered for the voice station should include the Multimedia call feature access code. 358 Administrator Guide for Avaya Communication Manager...
Page 359 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 360 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 may discuss some of these commands and their output in more detail. Action...
Page 361 Enhanced Mode MM Complex Figure 151: Status Station 1002 — General Status screen status station 1002 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...
Page 362 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 may want to reduce the number of stations that use H.320 conversion. 362 Administrator Guide for Avaya Communication Manager...
Page 363: 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 364 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 Guide for Avaya Communication Manager, 555-245-207.
Page 365: Setting Up Personal Station Access
Setting up Personal Station Access Figure 155: Telecommuting Access screen TELECOMMUTING ACCESS Telecommuting Access Extension: 1234 2. In the Telecommuting Access Extension field, type 1234 and press Enter. This is the extension you are configuring for telecommuting. 3. Type change system-parameters coverage and press Enter. System Parameters Call Coverage/Call Forwarding screen appears.
Page 366 "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 367 Setting up Personal Station Access 6. Complete the following fields and 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 368: Creating A Station Security Code
7 or 8. 5. Type change station 1234 and press Enter. This is the station extension you configured for telecommuting. The Station screen appears. 368 Administrator Guide for Avaya Communication Manager...
Page 369 1391 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 1 June 2005...
Page 370: 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 371: 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 372 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. 372 Administrator Guide for Avaya Communication Manager...
Page 373: 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 374: 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 375 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 376: 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 377 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 378 This is the class of restriction (COR) number associated with the barrier code that defines the call restriction features. 8. Type 1 in the TN field. This is the Tenant Partition (TN) number. 378 Administrator Guide for Avaya Communication Manager...
Page 379 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 380 QSIG to DCS TSC Gateway on page 1337 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. 380 Administrator Guide for Avaya Communication Manager...
Page 381: 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 382 This is the feature access code you set for activating extended call forward. You hear dial tone. 3. Dial 4321 and press #. This is the extension from which you want to forward calls. 382 Administrator Guide for Avaya Communication Manager...
Page 383 Changing Telecommuting Settings 4. Dial 87654321 and 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 384 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. 384 Administrator Guide for Avaya Communication Manager...
Page 385: 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 386: 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. 386 Administrator Guide for Avaya Communication Manager...
Page 387 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 388: 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 389: System Security Checklist
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 390 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 391 You cannot administer loop-start trunks if Call Forwarding Off Net is required. Note: 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 392 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. 392 Administrator Guide for Avaya Communication Manager...
Page 393: Adding Logins And Passwords
Adding Logins and Passwords 17. Administer all fax machines, modems, and answering machines analog voice ports as follows: Set the Switchhook Flash field to n. ● Set the Distinctive Audible Alert field to n. See Station on page 1391 for more ●...
Page 394 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. 394 Administrator Guide for Avaya Communication Manager...
Page 395 Adding Logins and Passwords 9. Type change permissions angi3 and press Enter. Command Permission Categories screen appears. Figure 159: Command Permission Categories screen COMMAND PERMISSION CATEGORIES Login Name: angi3 COMMON COMMANDS Display Admin. and Maint. Data? n System Measurements? n ADMINISTRATION COMMANDS Administer Stations? y Administer Features? n...
Page 396: 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 and press Enter. Login Administration screen appears. 396 Administrator Guide for Avaya Communication Manager...
Page 397 Changing a Login Figure 161: Login Administration screen change login angi3 Page 1 of 2 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 398: Displaying A Login
More information When you remove a login, the Security Measurement reports do not update until the next hour. Related topics For more information on logging in, see Logging into the System on page 21. 398 Administrator Guide for Avaya Communication Manager...
Page 399: 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 400 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 and press Enter. Security-Related System Parameters screen appears. 400 Administrator Guide for Avaya Communication Manager...
Page 401 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 402 1. Type change login xxxx and 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. 3. Press Enter to save your changes. 402 Administrator Guide for Avaya Communication Manager...
Page 403 Using Access Security Gateway Loss of an ASG key If a user loses their Access Security Gateway Key: 1. Modify any logins associated with the lost Access Security Gateway Key. See the Access Security Gateway (ASG) Key Release 1.0 User’s Guide for more information on changing your PIN.
Page 404: Changing Login Permissions
Instructions We will change the login permissions of angi3. To change login permissions: 1. Type change permissions angi3 and press Enter. Command Permission Categories screen appears. 404 Administrator Guide for Avaya Communication Manager...
Page 405 Changing Login Permissions Figure 166: Command Permissions Categories screen COMMAND PERMISSION CATEGORIES Login Name: angi3 COMMON COMMANDS Display Admin. and Maint. Data? n System Measurements? n ADMINISTRATION COMMANDS Administer Stations? y Administer Features? n Administer Trunks? n Administer Permissions? n Additional Restrictions? y MAINTENANCE COMMANDS Maintain Stations? n...
Page 406: 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. 406 Administrator Guide for Avaya Communication Manager...
Page 407: Using Busy Verify
Before you start On the Trunk Group screen, verify the Dial Access field is y. If 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 408: Setting Up Authorization Codes
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. 408 Administrator Guide for Avaya Communication Manager...
Page 409 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 410 Remember, all authorization codes used in the system must be the same length. Note: 10. In the COR field, enter the desired Class of Restriction number from 0 through 95. In our example, type 1. 11. Press Enter to save your changes. 410 Administrator Guide for Avaya Communication Manager...
Page 411: Setting Up Security Violations Notification
Setting up Security Violations Notification 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 for more information on using trunk access codes.
Page 412 More than 3 attempts causes a security violation notification. 6. In the Time Interval field, type 0:03. This the time interval in which the threshold, or number of violations, must occur. 7. Press Enter to save your changes. 412 Administrator Guide for Avaya Communication Manager...
Page 413 Setting up Security Violations Notification 8. (Optional) Type change login nnnn, where nnnn is your login ID. The system displays the Login Administration screen. Figure 173: Login Administration screen change login xxxx Page 1 of 2 LOGIN ADMINISTRATION Password of Login Making Change: LOGIN BEING ADMINISTERED Login’s Name:xxxxxxx Login Type:...
Page 414 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 appears. 414 Administrator Guide for Avaya Communication Manager...
Page 415 Setting up Security Violations Notification Figure 175: Station screen 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: _________ List3: _________...
Page 416: 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 phones 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 417 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 418: Dealing With Security Violations
There may 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, and press Enter.
Page 419: 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 may not apply to your situation): 1. Install the necessary circuit packs and perform any administration the circuit pack requires.
Page 420 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? 420 Administrator Guide for Avaya Communication Manager...
Page 421 Related topics See the Hardware Guide 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 422: 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 423 Adding a CO, FX, or WATS Trunk Group Figure 176: Trunk Group screen TRUNK GROUP Group Number: 5 Group Type: co CDR Reports: y Group Name: Outside calls COR: 85 TN: 1__ TAC: 105 Direction: two-way Outgoing Display? n Dial Access? n Busy Threshold: 99 Night Service: 1234 Queue Length: 0...
Page 424 11. 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 425: 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 426 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 427: Adding A Pcol Trunk Group
Before you can administer any trunk group, you must have one or more circuit packs of the correct type 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 Guide for Avaya Communication Manager, 555-245-207.
Page 428 4. In the TAC field, type 111. This field defines a unique code that you or your users can dial to access this trunk group. The code also identifies this trunk group in call detail reports. 428 Administrator Guide for Avaya Communication Manager...
Page 429 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 430 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. 430 Administrator Guide for Avaya Communication Manager...
Page 431: 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 432 This field defines the direction of traffic flow on this trunk group. 7. In the Night Service field, type 1234. This field assigns an extension to which calls are routed outside of business hours. 432 Administrator Guide for Avaya Communication Manager...
Page 433: Adding A Diod Trunk Group
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 434: Setting Up Digital Trunks
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 Guide for Avaya Communication Manager, 555-245-207.
Page 435 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 436 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 437 Setting up Digital Trunks Enhanced DS1 administration Normally, you can’t change the DS1 Circuit Pack screen unless you remove all related trunks from their trunk group. However, if the DS1 MSP field on the System-Parameters Customer-Options screen is y, and you are assigned the associated login permissions, you can change some of the fields on the DS1 Circuit Pack screen without removing the related trunks from their trunk group.
Page 438 Related topics DS1 Circuit Pack on page 879 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. 438 Administrator Guide for Avaya Communication Manager...
Page 439: 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 440 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. 440 Administrator Guide for Avaya Communication Manager...
Page 441: 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 phones, those buttons must be removed or assigned to another trunk group.
Page 442: Inserting And Absorbing Digits
Disconnect Supervision - In? y 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. 442 Administrator Guide for Avaya Communication Manager...
Page 443 Inserting and Absorbing Digits 3. In the Digits field, type 6. For insertion, this field defines the specific digits to insert. Communication Manager will add a "6" to the front of the digit strings delivered with incoming calls. For example, if the central office delivers the string "4444,"...
Page 444: Administering Trunks For Listed Directory Numbers
Listed directory numbers (LDN) are the telephone numbers given for an organization in public telephone directories. You can administer Avaya Communication Manager so that calls to different listed directory numbers go to the same attendant group. How you administer your system for LDN calls depends on whether the calls are coming in over DID and tie trunks or over CO and FX trunks.
Page 445 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. Related topics Listed Directory Numbers on page 1222 for detailed information about this feature.
Page 446: 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 447: Administering Isdn Trunk Groups
Administering ISDN Trunk Groups 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 448 (if using ISDN-BRI interfaces) or DS1 Circuit Pack screen (if using ISDN-PRI interfaces) ISDN Numbering - Private Route Pattern Hunt Groups ISDN Caller Display Signaling Group (if using ISDN-PRI interfaces) Terminating Extension Group ISDN Caller Display 448 Administrator Guide for Avaya Communication Manager...
Page 449 Administering ISDN Trunk Groups Table Notes System-Parameters Customer-Options — The ISDN-BRI Trunks or ISDN-PRI fields ● must be set to y. For a TN778 and if using ISDN-PRI interfaces, the PRI Over PACCON field must be set to y. If not, a new license file is needed. QSIG Optional Features fields may be enabled to allow appropriate administration for Supplementary Service Protocol.
Page 450 ● 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 451: Chapter 13: Managing Announcements
Chapter 13: Managing Announcements An announcement is a recorded message a caller may hear while the call is in a queue, or if a call receives intercept treatment for some reason. An announcement is often used in conjunction with music. Locally Sourced Announcements and Music The Locally Sourced Announcement and Music feature is based on the concept of audio source groups.
Page 452 4. Press Enter to save your changes. Adding a Music-on-hold Group To add a music-on-hold group: 1. Type add moh-analog-group n, where n is the music-on-hold group number. Press Enter. The system displays the MOH Group screen. 452 Administrator Guide for Avaya Communication Manager...
Page 453: Adding An Announcement Data Module
Adding an Announcement Data Module Figure 186: MOH Group screen change moh-analog-group 2 Page 1 of x MOH Group 2 Group Name: MOH SOURCE LOCATION 2. In the Group Name field, type in an identifier name for the music-on-hold group. 3.
Page 454 3. In the Type field, type announcement and press Enter. The Port field automatically changes to Board. 4. In the Board field, type the board location of the announcement circuit pack. 5. Press Enter to save your changes. 454 Administrator Guide for Avaya Communication Manager...
Page 455: Adding Announcement Extensions
Adding Announcement Extensions Adding Announcement Extensions You need to assign an extension for each announcement that you want to record. After you define an announcement extension, you use it to record and access the announcement. Announcements can be stored on a TN2501AP circuit pack or a TN750 circuit pack. Instructions We will use extension 1234 for an announcement about business hours.
Page 456 You fill the file space when you record an announcement or transfer an announcement file to the circuit pack through a file transfer protocol (FTP) session. To check that the announcement administration is correct: 1. At the SAT, type list integrated-annc-boards and press Enter. 456 Administrator Guide for Avaya Communication Manager...
Page 457: Recording Announcements
2 to play an announcement, or 3 to delete the announcement. If the circuit pack memory is more than 90% full, then Communication Manager gives stutter dial tone when the user gains access to an announcement session. Even if the user hears stutter tone, the user should begin speaking to record the announcement.
Page 458 You can re-record the announcement. Dial the feature access code, dial the extension, and press 2 before the 15-second timer expires. 458 Administrator Guide for Avaya Communication Manager...
Page 459: Saving Announcements
Saving Announcements Saving Announcements Note: This task only applies if you are using a TN750-series announcement circuit Note: pack. If you are using the TN2501AP (VAL) announcement circuit pack or VVAL announcements, see Recording new VAL announcements at a computer page 469.
Page 460: Copying Announcements
To copy announcements between your back-up disk and tape: 1. Type copy announcements and press Enter to save the changes. This process can take up to 40 minutes. You cannot administer your system while it is copying announcements. 460 Administrator Guide for Avaya Communication Manager...
Page 461: Restoring Announcements
Restoring Announcements Restoring Announcements Note: This task only applies if you are using a TN750-series announcement circuit Note: pack. If you are using the TN2501AP (VAL) announcement circuit pack or VVAL announcements, see Moving announcements to a VAL circuit pack or to another LAN device on page 477.
Page 462: Deleting And Erasing Announcements
5. To ensure that an announcement was deleted, dial 1234. You hear a busy signal if the announcement was deleted. 6. Repeat Steps 1-5 for each announcement that you want to delete. You can delete only one announcement at a time. 462 Administrator Guide for Avaya Communication Manager...
Page 463: Setting Up Continuous-Play Announcements
Setting up Continuous-Play Announcements You may also want to remove the announcement extension from the system. To remove the extension, use your system administration terminal to complete the following steps: 1. Type change announcements and press Enter. Announcements/Audio Sources screen appears. 2.
Page 464 2. Type b in the Q field on the same line as extension 1234. 3. Leave business hours in the Name field, or enter a new description for the announcement. 4. Press Enter to save your work. 464 Administrator Guide for Avaya Communication Manager...
Page 465: Getting Started With The Tn2501Ap Or G700 Virtual Val
These instructions are contained in other documents in the Avaya Communication Manager documentation library. For more information about these and other tasks related to using the TN2501AP, see the documents listed in the following table.
Page 466 Network Region fields, and set the Enable Ethernet Pt field to y. Press Enter. 6. Type add data-module next. The system displays the Data Module screen. 7. In the Type field, enter ethernet. The system displays the ethernet-specific fields. 466 Administrator Guide for Avaya Communication Manager...
Page 467: Managing Val Announcements Using The Sat
Managing VAL Announcements Using the SAT 8. In the Port field, enter the cabinet location of the VAL board followed by port number 33. Note: Although the VAL board has only 32 ports, the data module uses 32 +1, or 33 for Note: its port value.
Page 468 Viewing the Denial Events Log on page 481. Announcement file format requirements In order to be compatible with the TN2501AP circuit pack and Avaya Communication Manager, announcement recordings must have the following parameters: CCITT A-Law or CCITT µ-Law companding format (do not use PCM) ●...
Page 469 Announcements. Converting announcement files to VAL format If you are sharing recordings in a multi-site environment with Avaya Communication Manager and CONVERSANT systems, you must convert announcement files for use on either system. If you need to convert an announcement file to the required format, you can use a sound recording utility application to do so.
Page 470 Filenames are case-sensitive and require the .wav file extension. Note: The /annc portion of the command directs the system to the announcement subdirectory on the VAL circuit pack, and /Closed.wav indicates to delete the filename "Closed.wav." 470 Administrator Guide for Avaya Communication Manager...
Page 471 Managing VAL Announcements Using the SAT Deleting all VAL announcements on a circuit pack using the SAT To delete all of the announcement files on the VAL circuit pack: 1. At the SAT, type busyout board board-location and press Enter. Ensure that the command is successful.
Page 472 The Integrated Announcement Boards screen appears. Figure 190: Integrated Announcement Boards screen display integrated-annc-boards Page 1 of x Last Board Loction Saved: Board Time Number of Location Remaining Rate Recordings Checksum ID 1:01D09 047a 2:02817 00db 472 Administrator Guide for Avaya Communication Manager...
Page 473: Managing Val Announcements Using Ftp
Managing VAL Announcements Using FTP Managing VAL Announcements Using FTP This section includes information on setting up and terminating a file transfer protocol (FTP) session and outlines tasks that you can do in an FTP session. There are 3 basic components to an FTP session: Setting up an FTP session ●...
Page 474 When the FTP session on the circuit pack is enabled, the announcement and firmware files are available to anyone who knows the VAL circuit pack’s IP address, the ftp-username, and the ftp-password. SECURITY ALERT: Avaya recommends using a unique ftp-login and ftp-password for each FTP SECURITY ALERT: session. Starting an FTP session If you are unfamiliar with FTP client application software, contact your network administrator for information about access to an FTP session.
Page 475 Managing VAL Announcements Using FTP Instructions 1. At the FTP client, type ftp val-ip-address and press Enter. Note: A Virtual VAL (VVAL) uses the IP address of the media gateway. Type list Note: media-gateway to find this IP address. For a TN2501AP VAL board, use the IP address administered on the IP Node Names screen (change node-names...
Page 476 VVAL. For a TN2501AP VAL board, type list directory board nnnnn/annc (adding the / annc extension) to reach the announcement directory. 476 Administrator Guide for Avaya Communication Manager...
Page 477 Managing VAL Announcements Using FTP Instructions To delete an announcement on a TN2501AP circuit pack through an FTP session: 1. Ensure that the steps in Setting up an FTP session on page 473 are complete. 2. At the computer client, type delete filename.wav and press Enter. Example: delete Closed.wav Note: The announcement file is only removed from volatile RAM memory.
Page 478 .wav file extension. 2. Attempt to play the announcement that was administered first and transferred second. Communication Manager returns a busy signal at the first play attempt. 3. Attempt to play the announcement that was administered first and transferred second in a telephone access session.
Page 479 SAT and press Enter. ● (This clears the ftp-username and ftp-password.) you can effectively terminate the session from the Avaya Communication Manager end by ● letting the system time out (10 minutes of inactivity).
Page 480: Val Manager
However, new FTP session logins are not allowed. VAL Manager VAL Manager is a standalone application that allows you to copy announcement files and Avaya Communication Manager announcement information to and from Avaya Communication Manager over a LAN connection.
Page 481 Troubleshooting VAL Announcements Viewing the Denial Events Log To view the Denial Events Log: 1. At the SAT, type display events and press Enter. The Events Report screen appears. This input screen helps you focus the report on events of a certain type or from a certain time period. Figure 191: Events Report display events Page...
Page 482 If you played an announcement files back in another environment and it sounded great, but when you play it back in an Avaya Communication Manager environment the sound quality is poor, ensure that the file formats are compatible. A good announcement file format must be: 8Kbps sample rate ●...
Page 483 Each of as many as 10 integrated announcement boards (and each G700 virtual VAL source) is limited to 256 announcements. All Avaya G700 Media Gateways in the system can be assigned as VAL sources, for a maximum of 250 G700 VAL sources in a large S8700 Series media server configuration also with up to 10 TN2501 VAL boards, providing an ultimate capacity of 260 sources for the Avaya S8700 Series servers.
Page 484: Non-Volatile Storage Of Announcements On Val
You then could run change announcement again and switch the name back to the old one and the announcement will play fine. The VAL board is completely unaware that you change the change announcement command. 484 Administrator Guide for Avaya Communication Manager...
Page 485 Non-Volatile Storage of Announcements on VAL Changing the name of the announcement To change the name of an announcement you must do two things. 1. Change the administered name (using the change announcement command) 2. Change the name of the file on the VAL board Changing the name of the file on the VAL board There are two ways to accomplish this.
Page 486 Managing Announcements 486 Administrator Guide for Avaya Communication Manager...
Page 487: Chapter 14: Managing Group Communications
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. For information on specific circuit packs, see the Hardware Guide for Avaya Communication Manager, 555-245-207.
Page 488 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. 488 Administrator Guide for Avaya Communication Manager...
Page 489 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 490: 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 491 Setting up Chime Paging Over Loudspeakers Instructions To set up chime paging, you fill out the necessary fields on the Loudspeaker Paging screen and then assign chime codes to individual extensions on the Code Calling IDs screen. As an example, we will set up chime paging for a clothing store with 3 zones. We’ll allow users to page all zones at once, and we will assign a class of restriction of 1 to all zones.
Page 492 3. Assign chime codes to the remaining extensions by typing an extension number on the line following each code Id. You can assign chime codes to as many as 125 extensions. 4. Press Enter to save your changes. 492 Administrator Guide for Avaya Communication Manager...
Page 493 With an appropriate class of restriction, remote callers can also make loudspeaker pages. 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. Issue 1 June 2005...
Page 494: Paging Over Speakerphones
To set up speakerphone paging, you create a paging group and assign phones to it. In the following example, we’ll create paging group 1 and add 4 members. 1. Type add group-page 1 and press Enter. Group Paging Using Speakerphone screen appears. 494 Administrator Guide for Avaya Communication Manager...
Page 495 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 496 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 497: 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 Guide for Avaya Communication Manager, 555-245-207.
Page 498: Using Telephones As Intercoms
Managing Group Communications 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 499 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 500 To give a member of a group the ability to make intercom calls to all the other members, administer a Dial Intercom button on the member’s telephone. Type the number of the intercom group in the Grp field beside the Dial Intercom button. 500 Administrator Guide for Avaya Communication Manager...
Page 501: Setting Up Automatic Answer Intercom Calls
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 502 Remote Softphone Emergency Calls: as-on-local Direct IP-IP Audio Connections? n Emergency Location Ext: 75001 IP Audio Hairpinning? n 2. Move to the Auto Answer field and enter icom. 3. Press Enter to save your changes. 502 Administrator Guide for Avaya Communication Manager...
Page 503: 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 504 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. 504 Administrator Guide for Avaya Communication Manager...
Page 505: 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 506: 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 1262 for more information. 506 Administrator Guide for Avaya Communication Manager...
Page 507 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 508 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 508 Administrator Guide for Avaya Communication Manager...
Page 509: Dcp Data Modules
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 510: Telephone Dialing
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 511 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 512 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. 512 Administrator Guide for Avaya Communication Manager...
Page 513: 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 and press Enter.
Page 514: 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 515: 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 516: 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). 516 Administrator Guide for Avaya Communication Manager...
Page 517: 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 518 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. 518 Administrator Guide for Avaya Communication Manager...
Page 519: 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 520: Data Modules - General
● Ethernet data module. See for more information. ● 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.
Page 521 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 522 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. 522 Administrator Guide for Avaya Communication Manager...
Page 523: 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 524 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 525 ● 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 526 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) ● 526 Administrator Guide for Avaya Communication Manager...
Page 527 Administered Connection 2. On the DS1 Circuit Pack screen, administer all fields. Use with switch node carriers. See DS1 Circuit Pack on page 879 for more information. 3. On the Access Endpoint screen, administer all fields. See Access Endpoint on page 684 for more information.
Page 528 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 529: 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 530 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. 530 Administrator Guide for Avaya Communication Manager...
Page 531: 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 532 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 533 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 534: 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 535: 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 536: 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 537 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 538: 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 Note: doesn’t necessarily mean that data is actually coming across the connection.
Page 539: 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 540 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 may still be placed on that facility; an E1 facility with a D-channel and idle B-channels is considered an idle facility. 540 Administrator Guide for Avaya Communication Manager...
Page 541 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 542 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 543 Floating NxDS0 Preserve idle facilities as first priority Administering Wideband Switching Before you start, you need a DS1 Converter circuit pack. See the Avaya System Description Pocket Reference for more information on the circuit pack. To administer wideband switching: 1. On the Access Endpoint screen, administer all fields.
Page 544 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. 544 Administrator Guide for Avaya Communication Manager...
Page 545: 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 546 CallVisor ASAI is supported by two transport types. These are: 1. Integrated Services Digital Network (ISDN) Basic Rate Interface (BRI) transport (CallVisor ASAI-BRI) 2. LAN Gateway Transmission Control Protocol/Internet Protocol transport (Avaya LAN Gateway). CallVisor ASAI messages and procedures are based on the ITU-T Q.932 international standard for supplementary services.
Page 547: 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 548 ● using the Telephony Services Application Programming Interface (TSAPI). 3. In the Port field, use the port address assigned to the LAN Gateway Interface circuit pack. 4. Press Enter to save your changes. 548 Administrator Guide for Avaya Communication Manager...
Page 549: Chapter 16: Administering Media Servers
Overview Chapter 16: Administering Media Servers This chapter describes how to administer an Avaya S8700 Series Media Server and an Avaya G700 Media Gateway and the Avaya S8300 Media Server. 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 550: Administering The G700 Media Gateway
(For S8300 or S8700 Series Media Servers) 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 551 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 552 IP phones and media gateways that were previously using the primary media server will ● try to register with the standby media server for call processing, provided that they have been administered to do so in the controller list (use the set mgc list command). 552 Administrator Guide for Avaya Communication Manager...
Page 553 Embedded Web Manager, provides a browser-based graphical user interface (GUI) to assist you with ongoing media gateway administration. For complete information on using Device Manager, see the Avaya User’s Guide P330 Manager. (For S8300 or S8700 Series Media Servers) Device Manager allows you to: View the status of different devices on the network.
Page 554 G700 Media Gateway controlled by an Avaya S8300 Media Server or an Avaya S8700 Media Server, 555-234-200. For a list of CLI commands, see the Maintenance for the Avaya G700 Media Gateway ● controlled by an Avaya S8300 Media Server or an Avaya S8700 Media Server, 555-234-101.
Page 555: Administering The Media Server
S8300 or S8700 Series 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 556 If you are certain your connection is secure, accept the server security certificate to ● access the Login 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 557: Backing Up And Restoring Data
7. When you successfully log in to the server, check the top of the left panel. The Avaya media server you are logged into is identified by name and server number. The S8300 Media Server number is always 1.
Page 558 S8700 Series devices, use the Configure Trap Destinations 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 553. 558 Administrator Guide for Avaya Communication Manager...
Page 559: Administering Call-Processing
ASA is available in several languages. The S8300 or S8700 Series Media Server can be used to download Avaya Site Administration. A downloadable version of this package may be accessed through the S8300 or S8700 Series Media Server Web Interface.
Page 560 (possibly V1 through V9), and 05 is the port number. 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 561 ●...
Page 561 Administering Call-processing Using Avaya Terminal Emulator for Modem Connection to Communication Manager ● page 569 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...
Page 562 SFTP is disabled on the circuit pack. Using Telnet over the Customer LAN Note: For ease of administration, it is recommended that you use the Avaya Terminal Note: Emulator, instead of Telnet, whenever possible. To use Telnet over the customer LAN: 1.
Page 563 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. To set up Windows for Modem Connection: 1.
Page 564 1. Return to the Network and Dial-up Connections screen and right-click the connection you just created. 2. Select Connect. 3. Leave the User Name, Password, and Domain fields blank. If the Dial field is blank, enter the appropriate telephone number. 564 Administrator Guide for Avaya Communication Manager...
Page 565 Administering Call-processing 4. Click the Dial button. When the media server’s modem answers, the system displays the After Dial Terminal screen. 5. Log on to the LAN. a. Enter your remote access login name and password. b. When the Start PPP Now! message appears, click Done. c.
Page 566 AT%T19,0,34 Finland AT%T19,0,34 France AT%T19,0,34 Germany AT%T19,0,34 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 1 of 2 566 Administrator Guide for Avaya Communication Manager...
Page 567 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 568 Avaya Communication Manager, 555-233-504. Using Avaya Terminal Emulator for LAN Connection to Communication Manager You can download the Avaya Terminal Emulator from the main menu for the VisAbility Management Suite. Simply click Download next to the Administration menu item and follow the instructions.
Page 569 Administering Call-processing 11. In the TCP/IP port number field, type 5023 to log in directly to the Communication Manager SAT command line. 12. Click OK. The Connection Settings screen disappears. 13. On the Connections screen, double-click the name of the connection you just set up.
Page 570 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 571 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 572 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 573: Snmp Agents
Media Gateway serviceability commands (For S8300 or S8700 Series Media Servers) 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 574 Administering Media Servers Administering log-in permissions for SNMP To set up a Communication Manager SNMP agent (CMSA), you first need the ability to display administration commands and get system measurements. Instructions 1. On the SAT, type change permissions acpsnmp and press Enter.
Page 575 SNMP Agents 7. In the Maintain Switch Circuit Packs field, type y. 8. In the Maintain Process Circuit Packs field, type y. 9. In the Maintain Enhanced DS1 field, type y. 10. Press Enter to save your changes. Adding trap destinations A trap destination is an IP address that needs to receive SNMP alarm traps from the media server.
Page 576 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. 576 Administrator Guide for Avaya Communication Manager...
Page 577 SNMP Agents c. In the Security Model field, type: none — Traps are sent in plain text without a digital signature. authentication — An authentication password must be given. SNMP v3 uses this pass phrase to digitally "sign" v3 traps using MD5 protocol (associate them with the user).
Page 578 Administration of the password for the ACPSNMP login ● Enable SNMP busyout/release of Communication Manager objects and setting QOS ● parameters You can use this page to allow or restrict SNMP services at the application level. (You can use the Firewall page —...
Page 579 SNMP Agents Administering SNMP versions 1, 2c, and 3 CAUTION: On S8700 Series Media Servers, you must administer an SNMP agent exactly CAUTION: the same way in two places — on both the active and duplicated media servers. If you decide to use SNMP Version 3, there are three levels of security provided. 1.
Page 580 SNMP master agent, click Stop. 3. In the Communication Manager SNMP Agent section, check the Enable Agent box. If this box is checked, an SNMP manager can interact with Communication Manager using this CMSA and MIB-II sub-agent within the restrictions administered on this screen.
Page 581 SNMP Agents 5. In the Re-enter Password field, repeat the new password. Note: If these password fields are not administered correctly, all SNMP requests to the Note: CMSA will fail.. 6. In the SNMP Version 1 section, check the Enable SNMP Version 1 box if SNMP Version 1 is needed.
Page 582 On an S8300, S8500, S8300, or S8700 Series Media Server, you must turn on network access for the SNMP ports to allow SNMP access to Communication Manager. To turn on (or turn off) network access for SNMP ports, complete the following steps.
Page 583 SNMP Agents Figure 213: Firewall screen 2. Click the Advanced Setting button. Issue 1 June 2005...
Page 584 When a check appears in the box, the ports are on. CAUTION: All input and output boxes for SNMP ports must be turned on (checked) for CAUTION: SNMP access to Communication Manager to work. 584 Administrator Guide for Avaya Communication Manager...
Page 585: Chapter 17: Collecting Billing Information
Before you start The call accounting system that you use may be sold by Avaya, or it may 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 586 Answer Supervision Timeout: 10 Receive Answer Supervision? n 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 and press Enter.
Page 587 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 588: 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 589 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 590: Tracking Calls By Account Code
121 for more information. 5. Provide your users with a list of account codes to use. 6. You can also assign a Feature Access Code and give this to your users. 590 Administrator Guide for Avaya Communication Manager...
Page 591: 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 592 (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 767 for more information. 592 Administrator Guide for Avaya Communication Manager...
Page 593: 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 594 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 595 See DS1 Circuit Pack on page 879 for more information. Related topics For more information about AOC and PPM, see "Call Charge Information" in Feature Description and Implementation for Avaya Communication Manager, 555-245-205. Issue 1 June 2005...
Page 596: Viewing Call Charge Information
Collecting Billing Information 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 597 Viewing Call Charge Information 6. Type change system-parameters features and press Enter. Feature-Related System Parameters screen appears. 7. In the Charge Display Update Frequency (seconds) field, type 30. Frequent display updates may have considerable performance impact. 8. Press Enter to save your changes. 9.
Page 598 Collecting Billing Information 598 Administrator Guide for Avaya Communication Manager...
Page 599: 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 600: 500 Telephones
A new firmware image first must be downloaded into switch memory from a local trivial file transfer protocol (TFTP) server. Avaya recommends that you administer call appears only on the first 8 call appearance/feature buttons on the 2420 telephone.
Page 601: 2500-Series Telephones
Normal mode, so you do not have to assign a Date/Time button to these phones. 4601 IP telephone The 4601 Telephone is a low-cost VoIP telephone for Avaya. It is based on the 4602, but does not have an LCD display. The telephone supports H.323 Avaya proprietary call processing. It supports two call appearances, and has no speakerphone.
Page 602 Ethernet switch. Both the 4602 and 4602SW can run either the H.323 protocol, for integration with traditional Avaya IP Telephony Servers and Gateways, or the SIP protocol, for support of SIP Communications Servers such as the Avaya Converged Communications Server. In Communication Manager, administer the 4602 as a 4602+ to enable auto callback.
Page 603 4600-series IP telephones 4620SW IP telephone The 4620SW IP Telephone is cost effective and provides a large screen graphic display, paperless button labels, call log, speed dial, 24 programmable feature keys, Web browser, and full duplex speakerphone. The 4620SW also supports Unicode, IRDA, and is the only IP telephone to support the EU24 (expansion module).
Page 604: 6200-Series Telephones
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 605 6200-series telephones Figure 223: The 6210 telephone 6210 Flash PQRS WXYZ WXYZ WXYZ Redial Hold Figure notes: 1. Handset 7. Ringer volume control 2. Handset cord jack 8. Message light 3. Flash button 9. Handset volume control 4. Redial button 10.
Page 606 4. Handset cord jack 12. Pause button 5. Flash button 13. Message light 6. Redial button 14. Handset/speakerphone volume control 7. Hold button 15. Dial pad 8. Data jack 16. LINE jack (on bottom of telephone) 606 Administrator Guide for Avaya Communication Manager...
Page 607 6200-series telephones Figure 225: The 6220 telephone 6220 Program Pause Tel.# Mute Spkr Flash PQRS WXYZ Redial Hold Figure notes: 9. Hold button 1. DATA jack 2. Handset 10. Personalized ring 3. Program button 11. Ringer volume control 4. Mute button 12.
Page 608: 6400-Series Telephones
Telephone Reference 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 609 6400-series telephones 6408/6408D telephones The 6408 is a multi-appearance digital telephone with eight call appearance/feature buttons. The 6408 telephone is available in the following four models: 6408 telephone—includes a 1-way, listen-only speaker, and no display ● 6408+ telephone—includes a 2-way speakerphone, and no display ●...
Page 610 The 6424D+M telephone is similar to the 6424D, 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. 610 Administrator Guide for Avaya Communication Manager...
Page 611 6400-series telephones Figure 226: 6402D+ telephone Tel # Speaker Feature Hold Redial Transfer Conf Test Ring WXYZ PQRS Volume Figure notes: 1. Display 8. Message light 2. Feature button 9. Tray handle (includes reference cards) 3. Hold button 10. Redial button 4.
Page 612 3. Display control buttons 10. Conf/Ring button 4. Hold 11. Redial button 5. Call appearance/feature buttons 12. Transfer/Test button 6. Message light 13. Speaker button 7. Tray handle (includes reference cards) 14. Mute button 612 Administrator Guide for Avaya Communication Manager...
Page 613: 7100-Series Telephones
7100-series telephones 7100-series telephones 7101A telephone The 7101A telephone is a single-line analog model that is equipped with a Message Waiting light and a handy Recall button for activating the system’s special features. It cannot be physically bridged to the same analog line port due to the message waiting and loop current circuitry.
Page 614: 7300-Series Telephones
PEC code 3162 and the appropriate suffix. Administer 7305H telephones (34-Button) as a 7305S model. The system treats the telephone’s 24 feature function buttons (two lamps each) as single (green) lamp function buttons. 614 Administrator Guide for Avaya Communication Manager...
Page 615 7300-series telephones 7305S telephone The 7305S telephone is a multi-appearance hybrid telephone which provides access to 10 line appearances. The 10 line appearance buttons can also be used as programmable feature buttons. The 7305S telephone is also equipped with 24 programmable feature buttons and six fixed feature buttons.
Page 616 Telephone Reference Figure 229: 7305S telephone Figure notes: 1. Handset 3. 10 programmable buttons 2. Dial pad 4. 24 feature buttons 616 Administrator Guide for Avaya Communication Manager...
Page 617: 731X-Series Hybrid Telephones
731x-series hybrid telephones 731x-series hybrid telephones You should note that the following restrictions apply to administering hybrid telephones in the system: Hybrid telephones equipped with displays cannot be used as Automatic Call Distribution ● (ACD) agents and do not allow your end-users to access the Directory. The following fixed feature buttons do not operate on Hybrid telephones: STOP, PAUSE, ●...
Page 618 Telephone Reference Figure 231: 7314H telephone (BIS 22) Figure notes: 1. Handset 3. 10 programmable buttons 2. Dial pad 4. 12 feature buttons 618 Administrator Guide for Avaya Communication Manager...
Page 619 731x-series hybrid telephones Figure 232: 7315H telephone (BIS 22D) Figure notes: 1. Handset 3. 10 programmable buttons 2. Dial pad 4. 12 feature buttons Issue 1 June 2005...
Page 620 Telephone Reference Figure 233: 7316H telephone (BIS 34) Figure notes: 1. Handset 3. 10 programmable buttons 2. Dial pad 4. 24 feature buttons 620 Administrator Guide for Avaya Communication Manager...
Page 621 731x-series hybrid telephones Figure 234: 7317H telephone (BIS 34D) Figure notes:Figure Notes 1. Handset 3. 10 programmable buttons 2. Dial pad 4. 24 feature buttons Issue 1 June 2005...
Page 622: 7400-Series Telephones
The 7405D can also have a function key module which adds 24 feature buttons and a call coverage module (when no display module is used) which adds 20 call appearance/feature buttons. 622 Administrator Guide for Avaya Communication Manager...
Page 623 7400-series telephones 7406 telephones The 7406D telephone (7406D01A, 7406D02A, 7406D03A, and 7406D04A models) has five call appearance/feature buttons, each with a red in-use light and a green status light, seven shiftable (2-level) programmable feature buttons with no lights, four programmable feature buttons with a green light, four fixed feature buttons (CONFERENCE, TRANSFER, DROP, and HOLD), a SHIFT button with a green light, a SPEAKER button, and a green Message light.
Page 624 Message light, personalized ringing, a built-in speakerphone with a reset option, and a built-in 2-line by 40-character display. You can connect this telephone to a digital line port. The 7434D telephone supports an adjunct display module or a call coverage module. 624 Administrator Guide for Avaya Communication Manager...
Page 625 7400-series telephones 7444D telephone The 7444 telephone is a multi-appearance digital telephone that offers 34 call appearance/ feature buttons, each with a red in-use light and a green status light, four standard fixed feature buttons (CONFERENCE, DROP, HOLD, and TRANSFER), three fixed feature buttons with one light each (SELECT, SPEAKER/RESET SPKR, and MUTE), seven display feature buttons with one light each, a Message light, personalized ringing, a built-in speakerphone with a reset option, and a built-in 2-line by 40-character display.
Page 626 Telephone Reference Figure 236: 7404D telephone Figure notes: 1. Handset 3. 6 programmable buttons 2. Dial pad 626 Administrator Guide for Avaya Communication Manager...
Page 627 7400-series telephones Figure 237: 7405D telephone Figure notes: 1. Handset 3. 10 programmable buttons 2. Dial pad 4. 24 feature buttons Issue 1 June 2005...
Page 628 Figure 238: 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 628 Administrator Guide for Avaya Communication Manager...
Page 629 7400-series telephones Figure 239: 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 Issue 1 June 2005...
Page 630 Figure 240: 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 630 Administrator Guide for Avaya Communication Manager...
Page 631 7400-series telephones Figure 241: 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 Issue 1 June 2005...
Page 632 Figure 242: 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) 632 Administrator Guide for Avaya Communication Manager...
Page 633 7400-series telephones Figure 243: 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) Issue 1 June 2005...
Page 634 Telephone Reference Figure 244: 7407D telephone Figure notes: 1. Handset 3. 10 programmable buttons 2. Dial pad 4. 7 display buttons 5. 24 feature buttons 634 Administrator Guide for Avaya Communication Manager...
Page 635 7400-series telephones Figure 245: 7434D telephone Figure notes: 1. Handset 3. 10 programmable buttons 2. Dial pad 4. 24 feature buttons (11 to 34) Issue 1 June 2005...
Page 636 Figure 246: 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) 636 Administrator Guide for Avaya Communication Manager...
Page 637 7400-series telephones Figure 247: 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) Issue 1 June 2005...
Page 638: Isdn Telephones (7500S & 8500S)
Phones that comply with National ISDN (NI-1 and NI-2) BRI standards may serve as phones 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 phones that are...
Page 639 ISDN telephones (7500s & 8500s) 7506D ISDN-BRI telephone The 7506D serves as a telephone if it is equipped with a VOM. As a telephone, it offers programmable buttons, fixed feature buttons, a Message light, touch-tone dialing, and a built-in, programmable speakerphone or SPOKESMAN loudspeaker. The 7506 can be equipped with an optional Asynchronous Data Module that provides the user with simultaneous voice and data capabilities.
Page 640 Directory, a Call Log, the Self-Test feature, and a personalized ringing pattern for the telephone. Figure 248: 8503D telephone Figure notes: 1. Handset 3. 3 programmable buttons 2. Dial pad 640 Administrator Guide for Avaya Communication Manager...
Page 641 ISDN telephones (7500s & 8500s) Figure 249: 8510T telephone Figure notes: 1. Handset 3. 10 programmable buttons 2. Dial pad Issue 1 June 2005...
Page 642 The 8520T telephone supports 20 call appearances. The system maximum of 10 Note: call appearance buttons still applies. You can administer the buttons that are not used as call appearance buttons as bridged appearances. 642 Administrator Guide for Avaya Communication Manager...
Page 643: 8110 Telephones
8110 telephones 8110 telephones The basic 8110 (8110A01A, 8110A01B, and 811A01C) and the modified 8110M (8110A01D) telephones are single-line analog telephones. These telephones are exactly the same in appearance: each contains 12 programmable dialing buttons with PROGRAM and PAUSE buttons, automatic redial, a flashing red Message light, and a Hold button. They also have built-in speakerphones with Mute capability and the Automatic Answer feature.
Page 644 8411D with display can access 12 features with the softkeys and display control buttons. These 12 features can be used in addition to the features on the call appearance/ feature buttons. The 8411 telephone can work in both 4-wire and 2-wire environments. 644 Administrator Guide for Avaya Communication Manager...
Page 645 8400-series telephones 8434D telephone The basic 8434 (8434D01A) and the enhanced 8434DX (8434D02A) telephones are multi-appearance digital telephones which offer 34 call appearance/feature buttons, each with a red light and a green status light, four standard fixed feature buttons (CONFERENCE, DROP, HOLD, and TRANSFER), a MUTE button, a SPEAKER button which accesses either a 2-way speakerphone or a 1-way listen-only speaker, a TEST button, a SHIFT button (some 8434DX telephones will have a RING button instead), a red Message light, personalized ringing, a...
Page 646 Telephone Reference Figure 251: 8403B telephone Figure notes: 1. Handset 3. 3 programmable buttons 2. Dial pad 646 Administrator Guide for Avaya Communication Manager...
Page 647 8400-series telephones Figure 252: 8410B telephone Figure notes: 1. Handset 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. Issue 1 June 2005...
Page 648 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. 648 Administrator Guide for Avaya Communication Manager...
Page 649 8400-series telephones Figure 254: 8434D telephone Figure notes: 1. Handset 3. 10 programmable buttons 2. Dial pad 4. 24 feature buttons Issue 1 June 2005...
Page 650: Callmaster Telephones
(2-lamp) buttons, however, one of these buttons must be administered as a Headset On/Off button and a second one must be administered as a Release button. You can also administer the 12 softkey buttons. 650 Administrator Guide for Avaya Communication Manager...
Page 651 CALLMASTER telephones Figure 255: CALLMASTER II/CALLMASTER III digital telephone Figure notes: 1. Handset 3. 6 programmable buttons 2. Dial pad 4. 18 feature buttons Issue 1 June 2005...
Page 652 Telephone Reference Figure 256: CALLMASTER IV digital telephone Figure notes: 1. Handset 3. 6 programmable buttons 2. Dial pad 4. 15 feature buttons 652 Administrator Guide for Avaya Communication Manager...
Page 653 CALLMASTER telephones Figure 257: CALLMASTER V digital telephone Menu Exit 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 Issue 1 June 2005...
Page 654: Cordless Telephone
The radio module has Power, Pass, and Radio indicator lights, a top hook, card edge, and ● snap lock which connect the radio module to the carrier assembly/backplane, an antenna, and power plug and line connectors. 654 Administrator Guide for Avaya Communication Manager...
Page 655 Cordless telephone Figure 258: MDC9000 and MDW9000 cordless telephones Figure notes: 1. 6 programmable buttons 3. 6 programmable buttons 2. Dial pad 4. Dial pad Issue 1 June 2005...
Page 656 Telephone Reference Figure 259: MDC9000 and MDW9000 cordless telephones Figure notes: 1. 6 programmable buttons 3. 6 programmable buttons 2. Dial pad 4. Dial pad 656 Administrator Guide for Avaya Communication Manager...
Page 657: 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 658 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 659: Telecommuter Mode
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 660 Via IP Via the Telephone server Warrior 2402 2410 2420 2420 w/Expansion Module 4601 4602 4606 4610 4612 4620 4620 w/Expansion Module 4624 6402D 6408D/6408D+ 6416D+ 6416D+ w/Expansion Module 6424D+ 1 of 2 660 Administrator Guide for Avaya Communication Manager...
Page 661 Internet Protocol (IP) Softphones Table 8: Supported Terminals for Control of Terminal/Station (continued) Terminal Type Control of the Terminal/Station "Regular" Control "Shared" Control Road Telecommuter Via IP Via the Telephone server Warrior 6424D+ w/Expansion Module 8405D/8405D+ 8410D 8411D 8434D 8434D w/Expansion Module 6402 6408/6408+ 7403D...
Page 662 For instructions on how to administer an IP Softphone on your system, see Adding an IP Softphone on page 98. You can also find information on the IP Softphone CD (see DEFINITY IP Softphone Overview and Troubleshooting and DEFINITY IP Softphone Getting Started). 662 Administrator Guide for Avaya Communication Manager...
Page 663: Chapter 19: Screen Reference
AAR and ARS Digit Analysis Table Chapter 19: Screen Reference This chapter contains descriptions of Communication Manager screens that are used in performing administrative tasks. These are most often screens that are invoked using commands such as add, change, and remove.
Page 664 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. 664 Administrator Guide for Avaya Communication Manager...
Page 665 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...
Page 666 (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 666 Administrator Guide for Avaya Communication Manager...
Page 667 Valid display 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 668 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 669: Aar And Ars Digit Conversion Table
Digits may 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 670 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. 670 Administrator Guide for Avaya Communication Manager...
Page 671 Matching Pattern Valid entries Usage 0 to 9 Enter the number you want the server running Avaya Communication Manager to match to dialed numbers. (1 to 18 digits) If a Prefix Digit 1 is required for 10-digit direct distance dialing (DDD) numbers, be sure the matching pattern begins with a 1.
Page 672 Enter the digits that replace the deleted portion of the dialed number. Leave this field blank to simply delete (1 to 18 digits) the digits. Use # to indicate end-of-dialing. It must be at the end of the digit-string. blank 672 Administrator Guide for Avaya Communication Manager...
Page 673: 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 674 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 674 Administrator Guide for Avaya Communication Manager...
Page 675: Group List
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 676 Enter the extension that you want to give permission to program the Group List. Size (multiple of 5) Enter the number of abbreviated dialing numbers you want to assign in multiples of 5, up to 100. 676 Administrator Guide for Avaya Communication Manager...
Page 677 Abbreviated Dialing List Personal List This screen establishes a personal dialing list for telephone/data module users. The personal list must first be assigned to the telephone by the System Administrator before the telephone user can add entries in the list. The lists can be accessed by users to place local, long-distance, and international calls;...
Page 678 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. 678 Administrator Guide for Avaya Communication Manager...
Page 679 Abbreviated Dialing List Page 1 of 7 of the screen Figure 267: Abbreviated Dialing System List screen add abbreviated-dialing system Page 1 of 7 ABBREVIATED DIALING LIST SYSTEM LIST Size (multiple of 5): 100 Privileged? n Label Language:english DIAL CODE LABELS FOR 2420/4620 STATIONS 11:************* 12:*************...
Page 680 Abbreviated Dial buttons on the 2420/4620 telephone sets. Valid entries Usage A-Z, a-z, 0-9, Up to 15 alphanumeric characters and ! & * ? ; ’ ^ ( ) , . : - 680 Administrator Guide for Avaya Communication Manager...
Page 681 Abbreviated Dialing List Privileged Valid entries Usage 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.
Page 682 7103A fixed feature phones. Only one 7103A abbreviated dialing list can be implemented in the system and it applies to all 7103A fixed feature phones in the system. This list is controlled by the System Administrator. 682 Administrator Guide for Avaya Communication Manager...
Page 683 Abbreviated Dialing List Pages 1 through 4 of the screen Figure 270: Abbreviated Dialing List — 7103A Button List screen display abbreviated-dialing 7103A-buttons Page 1 of 1 ABBREVIATED DIALING LIST 7103A Button List DIAL CODE (FOR THE 7103A STATION BUTTONS) 1: ________________________ 5.
Page 684: Access Endpoint
Field descriptions for page 1 Figure 271: Access Endpoint screen add access-endpoint next Page 1 of ACCESS ENDPOINT Extension: 30001 (Starting) Port:_______ Communication Type: voice-grade-data Name:_____________ COR: 1 COS: 1 TN: 1 ITC: restricted 684 Administrator Guide for Avaya Communication Manager...
Page 685 Access Endpoint Communication Type Valid entries Usage voice-grade-dat 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 The COR is administered so that only an administered connection (AC) endpoint can be connected to another AC endpoint.
Page 686 (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. 686 Administrator Guide for Avaya Communication Manager...
Page 687 Access Endpoint (Starting) Port Enter the necessary characters. Valid entries Usage 01 to 03 First and second characters are the cabinet (DEFINITY CSI) or number. 1 to 64 (S8700 Series IP-Connect / S8700 Series Multi-Connect / S8300 Media Server) A to E Third character is the carrier.
Page 688 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. 688 Administrator Guide for Avaya Communication Manager...
Page 689: 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 684 for additional information.
Page 690 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 691 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 692: Start Time
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. 692 Administrator Guide for Avaya Communication Manager...
Page 693: Miscellaneous Parameters
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 694 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. 694 Administrator Guide for Avaya Communication Manager...
Page 695: Agent Login Id
Agent Login ID Agent Login ID Use this screen to add or change agent login IDs and skill assignments. If you add or change skills on the media server, the agent must log out and then log in again before the changes take effect.
Page 696 Customer-Options screen must be y. forced Enter forced to force an agent to enter a Reason Code when entering AUX mode. To enter forced, the Reason Codes and EAS on the System-Parameters Customer-Options screen must be y. 696 Administrator Guide for Avaya Communication Manager...
Page 697: Coverage Path
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.
Page 698 Enter y to remove an agent from the MIA queue for all the splits/skills/hunt groups that he or she is available in when the agent answers a call from any of his or her splits/skills/hunt groups. Valid entries are system (default), n, and y. 698 Administrator Guide for Avaya Communication Manager...
Page 699: Security Code
Agent Login ID Name Enter up to a 27-character string naming the agent. Any alpha-numeric character is valid. Default is blank. Password Appears only if both the AAS and AUDIX fields are n. Enter up to nine digits as the password the Agent must enter upon login.
Page 700: Call Handling Preference
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.
Page 701: Service Objective
Agent Login ID Local Call Preference Enter y to indicate that for calls queued in more than one skill for a multi-skilled EAS agent, the system should give preference to matching the location number of the queued call to the location number of the previously-busy agent.
Page 702: Alias Station
When you review the Alias Station screen, you may see alias types that have become native. If the type is now native, the last character of the aliased set type becomes a "#." 702 Administrator Guide for Avaya Communication Manager...
Page 703 Alias Station Field descriptions for page 1 Figure 275: Alias Station screen change alias station Page 1 of 1 ALIAS STATION Alias Set Type Supported Set Type ______ ______ ______ ______ ______ ______ ______ ______ ______ ______ ______ ______ ______ ______ ______ ______...
Page 704: Alphanumeric Dialing Table
______________________ ____________ ______________________ _____________ ______________________ ____________ ______________________ _____________ ______________________ ____________ ______________________ _____________ ______________________ ____________ ______________________ _____________ ______________________ ____________ ______________________ _____________ ______________________ ____________ ______________________ _____________ ______________________ ____________ ______________________ _____________ ______________________ ____________ ______________________ _____________ ______________________ 704 Administrator Guide for Avaya Communication Manager...
Page 705 Alphanumeric Dialing Table Alpha-name All alpha-names in the table must be unique and cannot be referenced in their own "Mapped String." The alpha-names can be used in any other "Mapped String" and multiple times in a "Mapped String." Valid entries Usage From 1 to 8 alphanumeric The entry must start with an alphabetic...
Page 706: Announcements/Audio Sources
__ _____ ________ _________ ________________________ _ _ __ _____ ________ _________ ________________________ _ _ __ _____ Valid entries Usage 0 to 95 Enter the class of restriction (COR) you want associated with this announcement. 706 Administrator Guide for Avaya Communication Manager...
Page 707 Announcements/Audio Sources Valid entries Usage 1 to 8 digits Enter the extension you assign to this announcement. The following screens can reference this extension: Hunt Group, Coverage Path, Trunk Group (Incoming Destination and Night Destination), Vector, Feature-Related System Parameters (DID/ Tie/ISDN Intercept Treatment, Controlled Restriction).
Page 708 Enter n to allow only users with a console permission COS to change or delete an announcement. For VAL the default is n, meaning that the announcement file is read-write. Use this value when you initially administer the announcement. 708 Administrator Guide for Avaya Communication Manager...
Page 709 Announcements/Audio Sources Q (Queue) Valid entries Usage y(es) Enter y to queue calls for the announcement if the Type field is integrated, integ-rep or aux-trunk. The caller is always connected to the beginning of the announcement. Enter y for ACD and vectoring delay announcements. Call centers should always use this option.
Page 710 42 minutes for 10 circuit packs for the TN750; for the ISSPA, there are 60 minutes of storage time). This is the default for VAL. Valid entries Usage 1 to 100 Enter the Tenant Partition number, if any. 710 Administrator Guide for Avaya Communication Manager...
Page 711 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 712: Ars Toll Table
Valid entries Usage Enter n to designate a non-toll CO code. ARS TOLL TABLE Valid entries Usage 2 through 9 Identify the number of the ARS Toll Table. 712 Administrator Guide for Avaya Communication Manager...
Page 713: Attendant Console
Attendant Console OFFICE CODES Valid entries Usage 200 to 299 Identify the block of numbers on this screen. through 900 to 999 Attendant Console This screen assigns an Attendant Console to the system. Field descriptions for page 1 Figure 279: Attendant Console screen change attendant 1 Page 1 of...
Page 714 Will not get night service calls. night-only Handles only night service calls. day/night Handles day or night service calls. Valid entries Usage 0 through 95 Enter the class of restriction that reflects the desired restriction. 714 Administrator Guide for Avaya Communication Manager...
Page 715: Data Module
Attendant Console Valid entries Usage 0 through 15 Enter the class of service (COS) for this attendant console. Data Module Valid entries Usage Enter y if the console is to be connected to a data terminal via 7400B or 8400 Data Module. If y is entered, complete the Data Module screen (page 4).
Page 716 If the blank attendant has a data module, the Extension field cannot be blank. Group Valid entries Usage 1 to 28 Enter the Attendant Group number. 716 Administrator Guide for Avaya Communication Manager...
Page 717 Attendant Console H.320 Conversion Allows H.320 compliant calls made to this telephone to be converted to voice-only. Because the system can handle only a limited number of conversion calls, you may need to limit the number of phones with H.320 conversion. Valid entries Usage Enter y for H.320 compliant calls.
Page 718 Does not apply to S8700 Series IP-Connect. Enter the security code required by the SoftConsole IP attendant. The required security code length is determined by Minimum Security Code Length on the Feature-Related System Parameters screen. Valid entries Usage 1 to 100 Enter the Tenant Partition number. 718 Administrator Guide for Avaya Communication Manager...
Page 719 1 to 3 digits. 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 720 Figure 280: Attendant Console Data Module screen (page 2) change attendant 1 Page 2 of 4 ATTENDANT IP FEATURE OPTIONS Remote Softphone Emergency Calls: as-on-local Direct IP-IP Audio Connections?y Emergency Location Ext: 1001 Always use? n IP Audio Hairpinning?y 720 Administrator Guide for Avaya Communication Manager...
Page 721 Attendant Console IP FEATURE OPTIONS 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 Emegency Calls field is ● hidden. A softphone can register no matter what emergency call handling settings the user has entered into the softphone.
Page 722 Communication Manager TDM bus. 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 723 Attendant Console Valid entries Usage as-on-local Type as-on-local to achieve the following results: If the administrator chooses to leave the Emergency ● Location Extension fields (that correspond to this station's IP address) on the IP Address Mapping screen blank, the value as-on-local sends the extension entered in the Emergency Location Extension field in the Station screen to the Public Safety Answering Point (PSAP).
Page 724 Valid entries Usage 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. Use this entry for IP Softphones with road warrior service that are near enough to the media server or switch that an emergency call routed over the it’s trunk reaches the PSAP that covers the server or...
Page 725 Attendant Console Field descriptions for Attendant Console Data Module screen This page displays if the Data Module field on Page 1 is y. If this is a non-IP attendant console this is page 2 of the Attendant screen. Figure 281: Attendant Console Data Module screen change attendant 1 Page 2 of x ATTENDANT...
Page 726 Name Enter the name of the user associated with the data module. The name is optional; it can be left blank. Enter the Tenant Partitioning number. Valid entries Usage 1 to 100 726 Administrator Guide for Avaya Communication Manager...
Page 727 Attendant Console ABBREVIATED DIALING List1 Valid entries Usage System Group. If g is entered, a group number is also required. Personal. If p is entered, a personal list number also is required. Enhanced SPECIAL DIALING OPTION Valid entries Usage hot-line Enter one of the dialing options that are available.
Page 728 This is the extension number of a previously administered user who has an associated Data Extension button and who will share the use of the module. Name Contains the name assigned to the above extension number. 728 Administrator Guide for Avaya Communication Manager...
Page 729 Attendant Console Field descriptions for page 3 Figure 282: Attendant Console screen change attendant 1 Page 3 of 4 ATTENDANT CONSOLE FEATURE BUTTON ASSIGNMENTS 1: split_____ 13: __________ 2: __________ 14: __________ 3: __________ 15: __________ 4: __________ 16: __________ 5: __________ 17: __________ 6: hold _____ *...
Page 730 (1 per console). dont-split Don’t Split. This button allows the attendant to not split away a call when dialing (1 per console). 2 of 4 730 Administrator Guide for Avaya Communication Manager...
Page 731 The single lamp 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 732 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 733: Audio Group
Audio Group Audio Group Use the Audio Group screen to add, change, or display a specified audio group. An audio group is a collection of recorded audio sources that have been placed in a group to facilitate their selection. Figure 284: Audio Group screen add audio-group next Page 1 of x Audio Group 2...
Page 734: Audix-Msa Node Names
Identifies the name of the MSA node. Valid entries Usage 1 to 7 character Used as a label for the associated IP address. The string MSA names must be unique on each server running Avaya Communication Manager. 734 Administrator Guide for Avaya Communication Manager...
Page 735: 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 736 For details on the System Capacity screen, see Maintenance Commands for Avaya Communication Manager, Media Gateways and Servers, 03-300191. 736 Administrator Guide for Avaya Communication Manager...
Page 737: Best Service Routing
Interflow VDN 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 remote Avaya server in a given application has to have a dedicated interflow server.
Page 738 Enter time in seconds. (DEFINITY CSI) Name Contains the name assigned to the BSR number. Valid entries Usage Up to 15 alphanumeric Assign a descriptive name for the characters. (DEFINITY CSI) physical location. 738 Administrator Guide for Avaya Communication Manager...
Page 739 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 with information on the best of these. Each remote Avaya server in a given application has to have a dedicated status poll vector.
Page 740: 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 741 Field descriptions for page 1 Figure 288: Sample Bulletin Board screen change bulletin-board Page 1 of 3 Message (* indicates high-priority) Date *Avaya is in the process of 03/02/93 *investigating your trunk lockup problem. 03/02/93 *The Bulletin Board will be updated as 03/02/93 *we find information.
Page 742 This display only field contains the date the information was entered or last changed. Lines 1 through 20 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 !@#$%^&*()_+-=[]{}|\’˜;:’,"<.>/? 742 Administrator Guide for Avaya Communication Manager...
Page 743: Call Vector
This screen programs a series of commands that specify how to handle calls directed to a Vector Directory Number (VDN). See the Avaya Communication Manager Call Center Software Call Vectoring and Expert Agent Selection (EAS) Guide, 07-300303, for additional information.
Page 744 Figure 291: Call Vector screen change vector 129 Page 3 of 3 CALL VECTOR 23 ____________ 24 ____________ 25 ____________ 26 ____________ 27 ____________ 28 ____________ 29 ____________ 30 ____________ 31 ____________ 32 ____________ 744 Administrator Guide for Avaya Communication Manager...
Page 745 Call Vector 01 through XX Enter vector commands as required (up to the maximum allowed in your configuration). For more information, see Avaya Communication Manager Call Center Software Call Vectoring and Expert Agent Selection (EAS) Guide, 07-300303. Valid entries Usage...
Page 746: Attendant Vectoring
System-Parameters Customer-Options screen, the Vectoring (Basic) and Vectoring (Prompting) fields are y. Default when, on the System-Parameters Customer-Options screen, the Vectoring (Basic) and Vectoring (Prompting) fields are n. No changes allowed to this field. 746 Administrator Guide for Avaya Communication Manager...
Page 747 Call Vector Basic A display-only field indicating whether, on the System-Parameters Customer-Options screen, the Vectoring (Basic) field is y. A display-only field indicating that on the System-Parameters Customer-Options screen, the Vectoring (Best Service Routing) field is y. Thus, you can use BSR commands and command elements in your vectors.
Page 748 Screen Reference 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). Note: Valid entries Usage You do not want this vector to be accessible to these client programs.
Page 749 Call Vector Multimedia Indicates whether the vector should receive early answer treatment for multimedia calls. This only applies if the Multimedia Call Handling field is y. This field does not appear for S8700 Series IP-Connect. Valid entries Usage If you expect this vector to receive multimedia calls, set this field to y.
Page 750: Cama Numbering Format
_______ ________________ _______ _____________ _______ ________________ _______ _____________ _______ ________________ _______ _____________ _______ ________________ _______ _____________ _______ ________________ _______ _____________ _______ ________________ _______ _____________ _______ ________________ _______ _____________ _______ ________________ _______ _____________ _______ ________________ 750 Administrator Guide for Avaya Communication Manager...
Page 751 CAMA Numbering Format CESID Valid entries Usage 1 to 11 digits or Enter the number that will be used to identify the blank calling terminal within an emergency service system. This field may represent a prefix to an extension or the 1 to 16 digits or entire CESID.
Page 752: Cdr System Parameters
Record Agent ID on Outgoing?n Trk Call Splitting? n Record Non-Call-Assoc TSC? n Record Call-Assoc TSC? n Digits to Record for Outgoing Calls: dialed Privacy - Digits to Hide: 0 CDR Account Code Length: 4 752 Administrator Guide for Avaya Communication Manager...
Page 753 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 754 Enter y to deny all toll calls unless the user dials an account code. Forced Entry of Account Codes must be y on the System-Parameters Customer-Options screen. Enter y to allow calls without an account code. This does not override other calling restrictions. 754 Administrator Guide for Avaya Communication Manager...
Page 755 Usage Enter y to create separate records for each portion of incoming calls that are transferred or conferenced. Interworking Feat-flag See "Call Detail Recording" in Feature Description and Implementation for Avaya Communication Manager, 555-245-205, for more information. Valid entries Usage Enter y if you want the feature flag to indicate interworked outgoing ISDN calls.
Page 756 Enter y to enable separate recording of attendant portions of outgoing calls that are transferred or conferenced. Outg Trk Call Splitting See "Call Splitting" in Feature Description and Implementation for Avaya Communication Manager, 555-245-205, for more information. Valid entries Usage Enter y to create separate records for each portion of outgoing calls that are transferred or conferenced.
Page 757 CDR System Parameters 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 758 Enter y to create records for call-associated temporary signaling connections. If you have a lot of data connections this could increase the number of records. You may want to consider the capacity of your call collection device. 758 Administrator Guide for Avaya Communication Manager...
Page 759 CDR System Parameters Record Called Vector Directory Number Instead of Group or Member If this option is enabled, the called VDN overrides the group or member information that normally appears in the Dialed Number field of the CDR record. If a call is directed through more than one VDN, the first VDN used for the call is stored.
Page 760 Secondary Output Format Controls the format of the call records sent to the secondary output device. CAUTION: Only qualified (Avaya) service personnel should administer a secondary output CAUTION: device. This option may cause loss of data when the buffer contains large amounts of data.
Page 761 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 762 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 auth-code location-from 1 of 2 762 Administrator Guide for Avaya Communication Manager...
Page 763 CDR System Parameters Data Item Length Data Item Length 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 Enter the length of each data item, if different from the default.
Page 764: Change Station Extension
You can change the extension of station B. If you do, the Change Station Extension ● screen displays station A’s extension in the Emergency Location Ext. field under the From Extension header. 764 Administrator Guide for Avaya Communication Manager...
Page 765 Change Station Extension Emergency Location Extension The Emergency Location Extension from the Station screen associated with the current extension is displayed under From Extension. Valid entries for Usage "To Extension" 0 to 9 Type a new extension for the Emergency Location Ext.
Page 766: Station Name
Station Name 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). 766 Administrator Guide for Avaya Communication Manager...
Page 767: Class Of Restriction
Class of Restriction Class of Restriction Use this screen to establish classes of restriction (COR). Classes of restriction control call origination and termination. Your system may use only one COR or as many as necessary to control calling privileges. You can assign up to 96 different CORs (0 to 95). Consider the following to enhance your system security: 1.
Page 768 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 769 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 770 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. 770 Administrator Guide for Avaya Communication Manager...
Page 771 Class of Restriction Can Be Picked Up By Directed Call Pickup Valid entries Usage Enter y to allow this Station’s or EAS agent’s calls to be picked up by using the Directed Call Pickup Up feature. Before you can set this field to y, you must set Directed Call Pickup on the Feature-Related System Parameters screen to y.
Page 772 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 may receive calls directly. 772 Administrator Guide for Avaya Communication Manager...
Page 773 Class of Restriction Facility Access Trunk Test An associated feature button (trk-ac-alm) status lamp lights when a successful test attempt occurs. Pressing one of the alarm buttons (ten maximum) when its associated status lamp is lit turns off all lamps on all buttons whether the access is still in progress or has completed Valid entries Usage Enter y to allow users with this COR to perform Facility...
Page 774 Central Office on request using R2-MFC signaling 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 phones or trunks that use this COR.
Page 775 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 776 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 page 1527). 776 Administrator Guide for Avaya Communication Manager...
Page 777 System-Parameters screen 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.
Page 778 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. 778 Administrator Guide for Avaya Communication Manager...
Page 779 Class of Restriction Field descriptions for page 2 Figure 297: Class of Restriction screen (page 2) change cor 10 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 780 Maximum Precedence Level Assign a maximum precedence level for extensions with this COR for use with the Multiple Level Precedence and Preemption feature. Valid entries Usage Flash Override Flash Immediate Priority Routine (default) 780 Administrator Guide for Avaya Communication Manager...
Page 781: Remote Logout Of Agent
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.
Page 782 93? n 10? n 22? n 34? n 46? n 58? n 70? n 82? n 94? n 11? n 23? n 35? n 47? n 59? n 71? n 83? n 95? n 782 Administrator Guide for Avaya Communication Manager...
Page 783 Class of Restriction CALLING PERMISSION Valid entries Usage A y means an originating facility assigned this COR can be used to call facilities assigned this COR. Enter n for each COR number (0 through 95) that cannot be called by the COR being implemented. Field descriptions for page 4 Figure 299: Class of Restriction screen (page 4) change cor 10...
Page 784: Class Of Service
COS to be implemented. Default values are shown on the screen. CAUTION: Because many hunt groups are set up with COS 1, be careful when you assign CAUTION: restrictions to COS 1. 784 Administrator Guide for Avaya Communication Manager...
Page 785: Automatic Callback
Class of Service 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 786 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 787 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 788: Code Calling Ids
This field assigns extensions to chime codes. Only one extension can be assigned to each chime code. Valid entries Usage An extension Enter a physical extension, not a VDN, to assign number that extension to a code. Otherwise, leave this field blank. 788 Administrator Guide for Avaya Communication Manager...
Page 789: Command Permission Categories
Related topics Setting up Chime Paging Over Loudspeakers on page 490 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 790 Administer Stations Valid entries Usage Enter y to allow a user to add, change, duplicate, or remove stations, data modules and associated features, such as abbreviated dialing, vectors, and routing tables. 790 Administrator Guide for Avaya Communication Manager...
Page 791 Command Permission Categories Administer Trunks Give this permission only to users who are very familiar with these features. Valid entries Usage Enter y to allow a user to administer AAR/ARS, trunk groups, remote access, and route patterns. Display Admin. and Maint. Data Valid entries Usage Enter y to allow a user to use the display, list,...
Page 792 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 trunk maintenance. 792 Administrator Guide for Avaya Communication Manager...
Page 793 Command Permission Categories 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 304: Command Permission Categories—Restricted Object List screen change permissions angi3...
Page 794: Configuration Set
CDR for Calls to EC500 Destination? Fast Connect on Origination? Post Connect Dialing Options? Calling Number Style Determines the format of the caller ID for calls from a local Avaya Communication Manager extension to an EC500 cell telephone. Valid entries Usage network Provides a display of only 10-digit numbers.
Page 795 Up to 20 alphanumeric For example, EC500 handsets. characters or blank Fast Connect on Origination Determines whether some additional processing occurs on the server running Avaya Communication Manager prior to connecting a call. Valid entries Usage Enter y to send CONNECT messages.
Page 796 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 797: Console Parameters
Console Parameters Console Parameters This screen administers attendant console group parameters. This includes basic parameters for Centralized Attendant Service (CAS) and Inter-PBX Attendant Service (IAS). A list of the administered attendant consoles also displays on this screen. Field descriptions for page 1 Figure 306: Console Parameters —...
Page 798 Enter an assigned Attendant VDN extension or blank. extension or blank Backup Alerting Indicates whether or not system users can pick up alerting calls if the attendant queue has reached its warning state. 798 Administrator Guide for Avaya Communication Manager...
Page 799 Console Parameters Calls In Queue Warning Enter the number of incoming calls that can be in the attendant queue before the console’s second Call Waiting lamp lights. The console’s first Call Waiting lamp lights when any incoming calls are waiting to be answered. The second lamp lights when the number of calls waiting equals the value you entered in the Calls in Queue Warning field.
Page 800 1 to 15 Enter a class of service (COS) number that reflects the desired features for all your attendant consoles. You can override this COS, by assigning a different COS on the individual Attendant screen. 800 Administrator Guide for Avaya Communication Manager...
Page 801 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 802 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 803 Console Parameters Field descriptions for page 2 Figure 307: Console Parameters — Default Attendant Group screen change console-parameters Page 2 of x CONSOLE PARAMETERS TIMING Time Reminder on Hold (sec): 10 Return Call Timeout (sec): 10 Time in Queue Warning (sec): INCOMING CALL REMINDERS No Answer Timeout (sec): 20 Alerting (sec): 40...
Page 804 Be sure to allow five seconds for each ring at all points in a coverage path to ensure the entire path is completed before the call returns to the console. Valid entries Usage 10 to 1024 or blank 804 Administrator Guide for Avaya Communication Manager...
Page 805 Console Parameters Secondary Alert on Held Reminder Calls? Valid entries Usage Enter y to begin attendant alerting for Held Reminder Calls with secondary alerting. Enter n to have held reminder calls alert the attendant the same as normal calls. Normal calls start with primary alerting and then switch to secondary alerting when the No Answer Timeout expires.
Page 806 Assistance Call:2_ CO Call:2_ DID to Attendant:2_ Tie Call:2_ Redirected DID Call:2_ Redirected Call:2_ Return Call:2_ Serial Call:2_ Individual Attendant Access:2_ Interpositional:2_ VIP Wakeup Reminder Call:2_ Miscellaneous Call:2_ Call-Type Ordering Within Priority Levels? n 806 Administrator Guide for Avaya Communication Manager...
Page 807 Console Parameters Call-Type Ordering Within Priority Levels? If you use call-type ordering, calls to the attendant are first grouped by the queue priority level, then by call type, and, finally, in the order received. Valid entries Usage Enter y if you want to present calls by call type. You can assign a type-disp button on the Attendant Console...
Page 808 Field descriptions for page 4 Figure 309: Console Parameters — Queue Priorities screen change console-parameters Page 4 of x CONSOLE PARAMETERS QUEUE PRIORITIES MLPP PRECEDENCE CALL Flash Override: 2 Flash: 3 Immediate: 4 Priority: 5 808 Administrator Guide for Avaya Communication Manager...
Page 809 Console Parameters QUEUE PRIORITIES Flash Override Valid entries Usage 1 to 17 Enter the queue priority for Flash Override precedence level calls. Flash Valid entries Usage 1 to 17 Enter the queue priority for Flash precedence level calls. Immediate Valid entries Usage 1 to 17 Enter the queue priority for Immediate precedence level...
Page 810 Display-only field that lists the Attendant Group number. Display-only field that lists the Tenant Partition number. Type Display-only field that shows all attendants in the group. You administer the individual attendant consoles on the Attendant Console screen. 810 Administrator Guide for Avaya Communication Manager...
Page 811: Coverage Answer Group
(alert) simultaneously. Any member of the group can answer the call. Each coverage answer group is identified by a number from 1 through the maximum number allowed by your system configuration (see Hardware Guide for Avaya Communication Manager, 555-245-207. The members of the group are identified by their extension number.
Page 812: Group Name
Group Number A display-only field when the screen is accessed using an administration command such as add or change. Name This display-only field indicates the name assigned when the member’s telephone is administered. 812 Administrator Guide for Avaya Communication Manager...
Page 813: Coverage Path
Coverage Path Coverage Path This screen implements Call Coverage Paths. The screen provides the means to specify the call coverage criteria, the points in the coverage path used to redirect calls, and the number of times a principal’s telephone rings before the call redirects to coverage. Field descriptions for page 1 Figure 312: Coverage Path screen change coverage path 2...
Page 814 Coverage treatment is terminated; the call is left at the last available location (principal or coverage point). Linkage Display-only fields that show the (up to) two additional coverage paths in the coverage path chain. 814 Administrator Guide for Avaya Communication Manager...
Page 815 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 816 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. 816 Administrator Guide for Avaya Communication Manager...
Page 817 Coverage Path COVERAGE POINTS Point1, Point2, Point3, Point4, Point5, Point6 The alternate destinations that comprise a coverage path. Coverage points must be assigned sequentially beginning with Point 1 (do not leave gaps). Each path can have up to six coverage points.
Page 818 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. 818 Administrator Guide for Avaya Communication Manager...
Page 819: 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 313: Crisis Alert System Parameters screen change system-parameters crisis-alert CRISIS ALERT SYSTEM PARAMETERS ALERT STATION Every User Responds? n ALERT PAGER Alert Pager? y...
Page 820: 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 821: 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 822 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. 822 Administrator Guide for Avaya Communication Manager...
Page 823: 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 314: CTI Link screen when Type field is ASAI or ADJLK add cti-link next Page 1 of 2 CTI LINK...
Page 824 Screen Reference CTI Link A display-only field indicating the CTI link number. Valid entries Usage 1 to 8 Avaya Communication Manager on a DEFINITY Server DEFINITY G3i 1 to 16 S8300 Media Server S8700 Series Multi-Connect Extension This field displays the extension for this link.
Page 825 CTI Link Port Appears when the Type field is ASAI or ADJLK. Enter 7 characters to specify a port, or an x. Valid entries Usage 01 to 64 First and second numbers are the cabinet number A to E Third character is the carrier 01 to 20 Fourth and fifth characters are the slot number 01 to 32...
Page 826 Field descriptions for page 2 Figure 316: Link screen when Type field is ASAI-IP or ADJ-IP add cti-link next Page 2 of 2 CTI LINK FEATURE OPTIONS Event Minimization? n Special Character for Restricted Number? n 826 Administrator Guide for Avaya Communication Manager...
Page 827 CTI Link Event Minimization May be used when event reports normally would be sent on multiple associations, but the adjunct does not need to see more than one. Typically, these event reports are identical except for the association they are sent over (for example, call control, domain control, or active notification).
Page 828: 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 828 Administrator Guide for Avaya Communication Manager...
Page 829: Baud Rate
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 830 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. See Administration for Network Connectivity for Avaya Communication Manager, 555-233-504 for more information.
Page 831 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 1 June 2005...
Page 832: Error Logging
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. Appears when the Permanent Virtual Circuit field is y.
Page 833 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 834: Node Name
The name is optional and can be blank. 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. 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.
Page 835 Data Module PDATA Port Used with System Port Data Modules. Enter a seven-digit alphanumeric port location to which the data module is connected. Used to relate the physical PDATA port to which the mode 3 portion of the system port is connected. This entry must be assigned to a port on a PDATA Line Board.
Page 836 01 to 04 (x.25 circuit pack) 01 to 31 (S8700 Series IP-Connect (tdm, pdm) configurations) 01 to 16 (ppp for S8700 Series IP-Connect) 01 to 08 (system-port for S8700 Series IP-Connect) 17/33 (ethernet on S8700 Series IP-Connect) 836 Administrator Guide for Avaya Communication Manager...
Page 837 This is the primary PDM, or if this data module is not used for AUDIX networking. Subnet Mask Used with Point-to-Point data modules (for S8700 Series IP-Connect). See Administration for Network Connectivity for Avaya Communication Manager, 555-233-504, for more information. Issue 1 June 2005...
Page 838 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 838 Administrator Guide for Avaya Communication Manager...
Page 839 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 840 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 840 Administrator Guide for Avaya Communication Manager...
Page 841 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 842 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. 842 Administrator Guide for Avaya Communication Manager...
Page 843 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 1 June 2005...
Page 844 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. 844 Administrator Guide for Avaya Communication Manager...
Page 845 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 846 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. 846 Administrator Guide for Avaya Communication Manager...
Page 847 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 848 Dial Echoing? y Disconnect Sequence: two-breaks Answer Text? y Parity: even Connected Indication? y DLC Option Settings on page 854 for additional information when assigning entries for the remaining fields on the screen. 848 Administrator Guide for Avaya Communication Manager...
Page 849 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 850 DLC prevents it from being sent to the device. This applies to the following messages: INCOMING CALL ● ANSWERED ● DISCONNECTED ● DISCONNECTED OTHER END ● 850 Administrator Guide for Avaya Communication Manager...
Page 851 Data Module 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. Answer Text Appears when the KYBD Dialing field is y.
Page 852 Disconnect Sequence Appears when the KYBD Dialing field is y. Selects the sequence for a disconnect. Valid entries Usage long-break A long-break is greater than 2 seconds. two-breaks Two-breaks is within 1 second. 852 Administrator Guide for Avaya Communication Manager...
Page 853 Data Module Parity Appears when the KYBD Dialing field is y. Select the desired type of parity. The DLC generates the parities when call setup text is sent to the DTE. The DLC does not check the parity when receiving dialing characters. Parity has nothing to do with the far end; it is used by the DLC to terminal communications during call setup.
Page 854 Autoadjust not operates used KYBD Dialing Busy Out If printer is member of Hunt Group Permit No, if printer is low speed Mismatch Parity Don’t care Dial Echoing Don’t care 1 of 2 854 Administrator Guide for Avaya Communication Manager...
Page 855 Data Module Table 9: DLDM screen settings for printer connection (continued) Field on screen Option Comments Disconnect Don’t care Sequence Answer Text Don’t care Connected Don’t care Indication Configuration 2 of 2 Non-intelligent terminals A non-intelligent terminal connected to the DLC usually is assigned as a line. Table 10 lists the option settings for non-intelligent terminals.
Page 856 Dial Echoing These devices can dial in the ASCII stream without human intervention Disconnect Sequence Long <BREAK> Answer Text These devices may not want to see any text Connected Indication Don’t care Configuration 856 Administrator Guide for Avaya Communication Manager...
Page 857 Data Module Host computers A host computer may 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 12 lists option settings for a port that has a terminating connection to a host computer or an originating connection from a host computer.
Page 858 The Country Protocol must match any previously-administered endpoint on the same port. The following table lists the valid protocol entries. Country/Area Protocol Australia ETSI (Europe) etsi Japan Singapore United States (Bellcore National ISDN) 858 Administrator Guide for Avaya Communication Manager...
Page 859 Data Module Endpt ID Used with World Class BRI and NI-BRI data modules. Appears only if the Endpt Init field is y. This field provides for multipoint configuration conformance to the Bellcore Terminal Initialization procedures. In these procedures, a multipoint configuration requires that the last 2 digits of the Service Profile Identifier (SPID) be between 00 and 63 and be binary unique for each endpoint.
Page 860 Assign a Service Profile Identifier (SPID) for this data module. Used with 7500, World Class BRI, and NI-BRI Data Modules. Appears only if the Fixed TEI field is y. Valid entries Usage 0 to 63 Enter a 1 to 2-digit number. 860 Administrator Guide for Avaya Communication Manager...
Page 861: 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 862 0 to 23 Enter the current hour to be used by the system clock. Minute Valid entries Usage 0 to 59 Enter the current minute. The system clock uses this as the current minute. 862 Administrator Guide for Avaya Communication Manager...
Page 863 Date and Time Month Valid entries Usage January through Enter the current month. The system clock December uses this as the current month. Second This display-only field shows the seconds and cannot be modified. It resets to zero when you save the information on this screen.
Page 864: Daylight Savings Rules
Enter the day of the week you want the clock to move Saturday or Day ahead to begin daylight savings. If you enter Day in this field, the clock will change on the exact date entered in the next two fields. 864 Administrator Guide for Avaya Communication Manager...
Page 865 Daylight Savings Rules Change day (Stop) Valid entries Usage Sunday through Enter the day of the week you want the clock to move Saturday or Day back to return to standard time. If you enter Day in this field, the clock will change on the exact date entered in the next two fields.
Page 866 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. 866 Administrator Guide for Avaya Communication Manager...
Page 867: Dcs To Qsig Tsc Gateway Screen
DCS to QSIG TSC Gateway screen DCS to QSIG TSC Gateway screen 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 868 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. 868 Administrator Guide for Avaya Communication Manager...
Page 869: 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 870: Call Type
, 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.) When dialing digits of Call Type aar, as soon as the dialed digits have reached the administered length, the digits are treated as if an AAR feature access code (FAC) was dialed.
Page 871 If a telephone’s COR restricts the user from originating calls, this user cannot access the attendant using this code. Beginning with the November 2003 release of Communication Manager (2.0), you can also administer the attendant access code by entering an...
Page 872 Feature access code only — A FAC can be any number from 1 to 9 and contain up to 4 digits. You can use * or #, but only as a first digit. Avaya recommends that a FAC have the longest total length for a given dialed string when using mixed numbering. Otherwise,...
Page 873 Dial Plan Analysis Table 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 874: Dial Plan Parameters
It also controls the appearance of 6- and 7-digit extensions on station displays. 6- and 7-digit extensions may 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 875 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 876 CDR node number if they are specified. Valid entries Usage 1 to 63 Enter the number of a specific node in a network. blank The field may be left blank if automatic restoration, DCS, and CDR are not used. 876 Administrator Guide for Avaya Communication Manager...
Page 877: Digit Absorption
This screen implements up to 5 digit absorption lists. The screen may 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 878 List Number A display-only field indicating the Digit Absorption List number (0 to 4). The list number is referenced from a field entry on the associated trunk group. 878 Administrator Guide for Avaya Communication Manager...
Page 879: Ds1 Circuit Pack
DS1 Circuit Pack DS1 Circuit Pack Use this screen to administer all DS1 circuit packs. Field descriptions for page 1 Figure 327: DS1 Circuit Pack screen add ds1 xxxxxx Page 1 of 2 DS1 CIRCUIT PACK Location: _____ Name: _______________ Bit Rate: _____ Line Coding: ____ Line Compensation: _...
Page 880 Page 1 of 2 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 880 Administrator Guide for Avaya Communication Manager...
Page 881 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 882 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 883 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 884 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 885 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 886 The entry in this field must match the companding method used by the far-end switch. This field does not appear for all DS1 circuit packs. Valid entries Usage alaw Enter alaw for E-1 service. mulaw Enter mulaw for T-1 service. 886 Administrator Guide for Avaya Communication Manager...
Page 887: Line Coding
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 888 Length: 133 to 266 (ft), 40.5 to 81.0 (m) Length: 266 to 399 (ft), 81.0 to 122 (m) Length: 399 to 533 (ft), 122 to 163 (m) Length: 533 to 655 (ft), 163 to 200 (m) 888 Administrator Guide for Avaya Communication Manager...
Page 889 DS1 Circuit Pack The following table shows the appropriate entries for different lengths of 22-gauge ABAM cable directly connecting to DS1 interfaces. Valid entries Usage Length: 0000 to 0266(ft), 000 to 081(m) Length: 0266 to 0532(ft), 081 to 162(m) Length: 0532 to 0798(ft), 162 to 243(m) Length: 0798 to 1066(ft), 243 to 325(m) Length: 1066 to 1310(ft), 325 to 400(m) Location...
Page 890 Screen Reference 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 891 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 892 Brazil ETS 300 102 Restart Nordic ETS 300 102 Restart South Africa ETS 300 102 Restart ETSI-a Europe, New ETS 300 102 Restart Zealand, etc. ETSI-b ETS 300 102 None 2 of 2 892 Administrator Guide for Avaya Communication Manager...
Page 893 DS1 Circuit Pack Received Digital Metering Pulse Maximum (ms) This field appears only when the Signal Mode field is cas (Channel Associated Signaling), the Interconnect field is co or pbx, and the Country Protocol field is administered for a protocol that uses periodic pulse metering (PPM) as defined in Incoming digital PPM signaling default per Country Protocol code...
Page 894 Country PPM Min (ms) PPM Max (ms) PPM Value null U.S. Australia Japan Italy Netherlands Singapore Mexico Belgium Saudi Arabia Spain France Germany Czech Republic Russia CIS Argentina Greece China 1 of 2 894 Administrator Guide for Avaya Communication Manager...
Page 895 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 896 Look Ahead Routing. Appears when the Group Type field is isdn-pri. Valid entries Usage 2 to 10 Enter a number of seconds between 2 and 10. Default is 4. If Long Timers is enabled, defaults to a read-only value of 13. 896 Administrator Guide for Avaya Communication Manager...
Page 897 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 898: Echo Cancellation
(that is, it can respond to test codes from technician’s equipment and report its status). When you enter integrated, fields for administering options on the ICSU appear on page 2 of the DS1 Circuit Pack screen. 898 Administrator Guide for Avaya Communication Manager...
Page 899 DS1 Circuit Pack Slip Detection Slips — synchronization errors — slow digital transmissions and can result in data loss. The server maintains a slip-count record for each DS1 interface to detect errors and evaluate their severity (the type of alarm). If as many as 50 percent of those spans administered for slip detection are experiencing slips (with respect to the primary), then a decision is made to switch to the secondary.
Page 900 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 901 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 may want to use these reports. INTEGRATED CSU OPTIONS...
Page 902 -22.5db For mid-span repeaters 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 903: Enable File Transfer
Related topics Setting up Digital Trunks on page 434 for instructions. See "DS1 Trunk Service" in Feature Description and Implementation for Avaya Communication Manager, 555-245-205, for more information. Enable File Transfer Use this screen to enable SFTP on TN799BP (C-LAN) and TN2501 (VAL) circuit packs.
Page 904 Password fields. at least one number Secure Valid entries Usage Default is y. Enter y to enable SFTP. If the circuit pack does not support a secure session, no session is enabled. 904 Administrator Guide for Avaya Communication Manager...
Page 905: 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 Figure 332: Extended Pickup Group screen change extended-pickup-group 1...
Page 906 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. 906 Administrator Guide for Avaya Communication Manager...
Page 907: 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 908: Feature Access Code
Abbreviated Dialing List1 Access Code Used to access AD list 1. Abbreviated Dialing List2 Access Code Used to access AD list 2. Abbreviated Dialing List3 Access Code Used to access AD list 3. 908 Administrator Guide for Avaya Communication Manager...
Page 909 Feature Access Code 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 910 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 911 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 912 An extension must have Station Security Codes administered to use the following Note: FACs: Extended Call Forward All Activate ● Extended Call Forward Busy/Don’t Answer Activate ● Extended Call Forward Deactivate ● Change Coverage ● 912 Administrator Guide for Avaya Communication Manager...
Page 913 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 914 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. 914 Administrator Guide for Avaya Communication Manager...
Page 915 PASTE (Display PBX data on telephone) Access Code Allows users to view call center data on display phones. PASTE is used in conjunction with Avaya IP Agent. Personal Station Access (PSA) Associate Code Used to associate a telephone with the telephone features assigned to a user’s extension.
Page 916 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 917 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 918 Trunk Answer Any Station Access Code Enter the access code that station users must dial to answer calls alerting on night bells. 918 Administrator Guide for Avaya Communication Manager...
Page 919 Feature Access Code User Control Restrict Activation/Deactivation Used to change the restriction level for a specific extension. Requires console permissions. Voice Coverage Message Retrieval Access Code Allows users to retrieve voice messages for another user (for whom they are a coverage point) via a digital display module.
Page 920 Enter the code the agent must dial to receive a single, new ACD call upon the completion of an ACD call. Note: The following two fields appear only if Service Observing (Remote/By FAC) on Note: the System Parameters Customer-Options screen is y. 920 Administrator Guide for Avaya Communication Manager...
Page 921 Feature Access Code Remove Agent Skill Access Code Enter the digits an agent must dial to be able to remove a skill from their current skill set. Note: The next field is available only if Vectoring (Basic) and Vectoring (Prompting) Note: have been enabled on the System-Parameters Customer-Options screen.
Page 922 Enter the access code the housekeeper dials from the client’s room to provide room status. These codes are transmitted to the Property Management System (PMS) for processing. You can assign a definition to the six codes on the Hospitality screen. 922 Administrator Guide for Avaya Communication Manager...
Page 923 Feature Access Code Housekeeping Status (Station) Access Code Enter the access code the housekeeper must dial to provide room status. This access code must be dialed from designated telephones. There are four codes. Verify Wakeup Announcement Access Code Enter the access code the user can dial to verify a wakeup announcement. Voice Do Not Disturb Access Code Enter the access code the user must dial to enter or cancel a do not disturb request without using a display - through the use of voice prompting.
Page 924 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 925 Feature Access Code Field descriptions for MLPP features page The feature access codes on this page pertain only to Multiple Precedence and Preemption (MLPP) calls. Figure 342: Feature Access Code (FAC) screen change feature-access-codes Page 8 of FEATURE ACCESS CODE (FAC) MLPP Features Precedence Calling Access Code: 8 WNDP PRECEDENCE ACCESS CODES:...
Page 926 .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. 926 Administrator Guide for Avaya Communication Manager...
Page 927: Feature-Related System Parameters
Feature-Related System Parameters Feature-Related System Parameters This screen implements system parameters associated with various system features. Note: This screen used to contain Call Coverage and Call Forwarding parameters. Note: These fields have been moved to a separate screen, which you can access with the command change system-parameters coverage-forwarding.
Page 928 The remote node number is the same node number as defined on the Dial Plan screen. Also, ACA button status transmits to other servers/ switches when in a DCS network. 928 Administrator Guide for Avaya Communication Manager...
Page 929 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 930 Enter y if ACA measurements will be taken. Otherwise, enter n. Call Park Timeout Interval (minutes) Valid entries Usage 1 to 90 Enter the number of minutes a call remains parked before it cancels. 930 Administrator Guide for Avaya Communication Manager...
Page 931 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 932 You can purchase a Magic OnHold system, which does not require such a license, from Avaya or our business 932 Administrator Guide for Avaya Communication Manager...
Page 933 Feature-Related System Parameters partners. This field does not appear if Tenant Partitioning is y on the System-Parameters Customer-Options screen. In that case, use the Tenant screen to establish Music on Hold. Valid entries Usage music Indicates what a caller hears while on hold. Default is tone none.
Page 934 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. 934 Administrator Guide for Avaya Communication Manager...
Page 935 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 936 Type port and the corresponding location of the ● music-on-hold analog/aux-trunk source. Note: After a valid value is entered, a blank Note: field appears for entry of the appropriate source identifier (extension number, audio group number, or port number). 936 Administrator Guide for Avaya Communication Manager...
Page 937 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...
Page 938 The administrator may not be able to use all entry slots because of system capacity constraints. Valid entries Usage A value of 3 makes 1000 Enhanced List entries available to the administrator A value of 4 makes 10,000 entries available. 938 Administrator Guide for Avaya Communication Manager...
Page 939 Feature-Related System Parameters Prohibit Bridging Onto Calls with Data Privacy Valid entries Usage Enter y to protect calls from bridge-on by any party, including Service 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.
Page 940 Screen Reference 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 941 Feature-Related System Parameters CPN, ANI for Dissociated Sets Appears when the Default COR for Dissociated Sets field is non-blank. Specifies the ISDN calling party number (CPN), R2-MFC ANI, and CAMA CESID applied to calls made from PSA dissociated sets, if no system-wide calling party information has been administered for those protocols on their respective administration screens.
Page 942 Record CTA/PSA/TTI Transaction in History Log Appears when the Terminal Translation Initialization (TTI) Enabled? field is y.Use this field to record when extensions and physical phones move between ports without additional administration from the administrator of Avaya Communication Manager. Valid entries Usage...
Page 943 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 944 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 944 Administrator Guide for Avaya Communication Manager...
Page 945 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 946 Enter the extension number for the extension in an associated field. May not be a VDN extension. tone Provides a siren-type tone to internal calls that cannot be completed as dialed 946 Administrator Guide for Avaya Communication Manager...
Page 947 Feature-Related System Parameters Controlled Station-to-Station Restriction Enter the type of intercept treatment the caller receives when the call is placed to a restricted telephone. Valid entries Usage announcement If announcement is entered, an associated extension number field displays. Enter the extension of the restricted telephone in the field.
Page 948: Directed Call Pickup
Enter n to prevent feature use. Emergency Access Redirection Extension Valid entries Usage An assigned Enter the assigned extension number (can be extension a VDN) where emergency queue overflow will redirect. 948 Administrator Guide for Avaya Communication Manager...
Page 949 Feature-Related System Parameters Extended Group Call Pickup Enables call pickup groups to answer calls directed to another call pickup group. Valid entries Usage flexible Flexible feature version supporting a one-to-n (pickup group-to-extended pickup group) mapping. simple Simple feature version with a one-to-one pickup group-to-extended pickup group mapping supported.
Page 950 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. 950 Administrator Guide for Avaya Communication Manager...
Page 951 (length) in the Authorization Code field. 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 952 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. Enter n if these digits should not display. 952 Administrator Guide for Avaya Communication Manager...
Page 953 Feature-Related System Parameters Field descriptions for page 5 Figure 347: Feature-Related System Parameters screen change system-parameters features page 5 of x FEATURE-RELATED SYSTEM PARAMETERS SYSTEM PRINTER PARAMETERS Endpoint: ____ Lines Per Page: 60 EIA Device Bit Rate: SYSTEM-WIDE PARAMETERS Switch Name: ________________ Emergency Extension Forwarding (min): 10 Enable Inter-Gateway Alternate Routing? n MALICIOUS CALL TRACE PARAMETERS...
Page 954 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. 954 Administrator Guide for Avaya Communication Manager...
Page 955 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.
Page 956 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 group number for S8700 Series IP-Connect blank 956 Administrator Guide for Avaya Communication Manager...
Page 957: Universal Call Id
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 958 Octel Messaging Division voice messaging systems. This numeric display setting sends only numbers, and not names, to the Octel system. 958 Administrator Guide for Avaya Communication Manager...
Page 959 Feature-Related System Parameters 7434ND Valid entries Usage If enabled, this allows you to use 7434ND in the Type field of the Station screen. This is not an actual telephone type, but you can use this to define ports for certain types of Octel Messaging Division systems. Use this value if your voice messaging system operates in Bridged Mode.
Page 960: Auto Start
If the value of the Public Network Trunks on Conference Call field is 0, this field will not appear on the screen. Valid entries Usage 3 to 6 Specify the maximum number of parties allowed in a conference call involving a public network subscriber. 960 Administrator Guide for Avaya Communication Manager...
Page 961 Feature-Related System Parameters Conference Parties without Public Network Trunks Valid entries Usage 3 to 6 Enter a number to specify the maximum number of parties allowed in a conference call involving no public network trunks. Conference Tone Note: Bridging and Conference Tones are not supported by all countries. If these tones Note: are enabled for countries other than Italy, Belgium, United Kingdom, or Australia, the tones will be equivalent to no tone (silence) unless the tone is independently...
Page 962 Enter a number between 0 and 999; 0 deactivates the timer. This value is the number of seconds a call can be on hold before the system re-alerts the user to remind them of the call. 962 Administrator Guide for Avaya Communication Manager...
Page 963 Usage A y entry allows you to use the Mode Code Voice Mail System Interface to connect the server running Communication Manager over a DTMF interface to INTUITY AUDIX or other vendors’ voice-mail systems. Night Service Disconnect Timer (seconds) Valid entries...
Page 964 These features include: Call Forwarding ● Send All Calls ● Do Not Disturb ● Valid entries Usage Enter y to use the Special Dial Tone. You must have a TN2182 circuit pack. 964 Administrator Guide for Avaya Communication Manager...
Page 965 Feature-Related System Parameters Station Call Transfer Recall Timer (seconds) Allows a user-transferred call (station-to-station, a trunk call, or a DCS call) to re-terminate with priority ringing back to the station user who initiates the transfer operation if the transfer-to party does not answer the call within the administered Station Call Transfer Recall timer.
Page 966 This is also known as Distinctive Ringing. Valid entries Usage 1 to 3 Enter the number of rings for internal, external and priority calls. For virtual stations, this applies to the mapped-to physical telephone. 966 Administrator Guide for Avaya Communication Manager...
Page 967 Feature-Related System Parameters DTMF Tone Feedback Signal to VRU - Connection, Disconnection This field appears only if DTMF Feedback Signals for VRU on the Customer-Options System Parameters screen is y. Valid entries Usage 0 to 9, *, #, A, B, Enter the code to connect or disconnect the VRU.
Page 968 VDN basis). This field is hidden if Maximum Number of Expanded Meet-me Conference Ports is 0 on the System Parameters Customer Options screen. Valid entries Usage 3 to 300 Enter the maximum number of parties allowed for each conference on your system. 968 Administrator Guide for Avaya Communication Manager...
Page 969 Feature-Related System Parameters No Dial Tone Conferencing When another line is on hold or alerting, No Dial Tone Conferencing eliminates dial tone while setting up a conference. See GuideBuilder for more information. Valid entries Usage Enter y to activate No Dial Tone Conferencing. No Hold Conference Timeout Controls the timeout of No Hold Conference call setup.
Page 970 Provides automatic callback for analog stations without flashing the hook. It is applied only when the called station is busy and has no other coverage path or call forwarding. The caller can enable the automatic callback without flashing the hook or entering the feature access code. 970 Administrator Guide for Avaya Communication Manager...
Page 971 Feature-Related System Parameters Note: If the Analog Busy Auto Callback Without Flash field is set to y, the Busy Note: Auto Callback without Flash field on the Station screen defaults to y (enabled) for all analog station types that allow Analog Auto Callback. Valid entries Usage Enter y to provide automatic callback for a calling analog...
Page 972 International CPN Prefix: Pass Prefixed CPN to ASAI: Unknown Numbers Considered Internal for AUDIX? UNSI Calling Name for Outgoing Calls? Path Replacement with Measurements? QSIG Path Replacement Extension: Path Replace While in Queue/Vectoring? 972 Administrator Guide for Avaya Communication Manager...
Page 973 Feature Plus signaling. For example, Message Waiting Indication (MWI) requires this extension in order to send the indication to the appropriate server running Communication Manager. Appears only if the ISDN Feature Plus field is y on the System-Parameters Customer-Options screen.
Page 974 Message Center entity. For instance, if the Message Center entity is AUDIX, the value in this field must match the value of the Extension Length field on the Switch Interface Administration screen of AUDIX. 974 Administrator Guide for Avaya Communication Manager...
Page 975 Enter y to allow Path Replacement after queue/vector processing has started. Depending on the version of CMS you are using, some calls can go unrecorded if you enable this capability. Please see your Avaya technical support representative for more information. Issue 1 June 2005...
Page 976 NCA Temporary Signaling Connections (TSCs) (both incoming and outgoing). Send Custom Messages Through QSIG? Valid entries Usage Enter y to provide appropriate display information, for example for the Posted Messages feature, over QSIG links. 976 Administrator Guide for Avaya Communication Manager...
Page 977 Feature-Related System Parameters Send ISDN Trunk Group Name on Tandem Calls Valid entries Usage Enter y to provide consistent display information regardless of trunk type. If set to y, provides only trunk group name. Send Non-ISDN Trunk Group Name as Connected Name Valid entries Usage Enter y to send a name of the non-ISDN trunk group as...
Page 978 Important: Be sure you have validated that your service provider’s central office is capable of accepting calling name information from Communication Manager in this way. For example, if the central office has a 5ESS, it must be a generic 5EXX or later. Failure to validate the central office capability may cause the central office to drop outgoing calls from your media server.
Page 979 Feature-Related System Parameters CPN/ANI/ICLID PARAMETERS CPN/ANI/ICLID Replacement for Restricted Calls Valid entries Usage up to 15 Enter a text string to replace the restricted numbers on characters the display. CPN/ANI/ICLID Replacement for Unavailable Calls Valid entries Usage up to 15 Enter a text string to replace the unavailable numbers on characters the display.
Page 980 This field appears only when Enable Enbloc Dialing without ARS FAC is y. Valid entries Usage 1 to 20 Enter the number of digits before Enbloc Calling Treatment is activated. Default is extension length plus 980 Administrator Guide for Avaya Communication Manager...
Page 981 Feature-Related System Parameters Field descriptions for page 10 Figure 352: Feature-Related System Parameters screen change system-parameters features page 10 of x FEATURE-RELATED SYSTEM PARAMETERS Pull Transfer: n Update Transferred Ring Pattern? n Outpulse Without Tone? y Wait Answer Supervision Timer? n Misoperation Alerting? n Repetitive Call Waiting Tone? y Allow Conference via Flash? y...
Page 982 This field does not effect auto-answer zip tone heard prior to the VOA. Note: Valid entries Usage Enter y to play zip tone following a VDN of Origin Announcement (VOA). Enter n if you do not want zip tone following a VOA. 982 Administrator Guide for Avaya Communication Manager...
Page 983 Valid entries Usage broadband This is the least exact of the levels of tone detection. If Avaya Communication Manager detects any tone at all, it interprets this as dial tone. medium The server running Avaya Communication Manager interprets any tone which has a continuous "on" period of longer than 1 second as dial tone.
Page 984 Enter y to indicate the server will outpulse digits even when a dial tone has not been received. Enter "n" if the calling party should receive intercept tone if no dial tone is detected. 984 Administrator Guide for Avaya Communication Manager...
Page 985 Feature-Related System Parameters Pull Transfer Valid entries Usage Enter y to enable the Pull Transfer feature on a system-wide basis. This allows either the transferring or transferred-to party to press the Transfer button to complete the transfer operation Repetitive Call Waiting Interval (sec) This field appears when the Repetitive Call Waiting Tone field is y.
Page 986 Disconnect Supervision-In or Disconnect Supervision-Out fields on the Trunk Group screen are n. blank Enter blank if you do not want Avaya Communication Manager to initiate a disconnect. 986 Administrator Guide for Avaya Communication Manager...
Page 987 Feature-Related System Parameters Wait Answer Supervision Timer Unanswered DID Call Timer (seconds) for more information. Valid entries Usage Enter y to enable this feature on a systemwide basis. When y is entered in this field, calls to stations unanswered after 50 seconds are dropped. When n is entered in this field, unanswered calls drop only when the calling party goes on-hook.
Page 988 Interflow-qpos EWT Threshold: 2 Reverse Star/Pound Digit For Collect Step? n Available Agent Adjustments for BSR? _ SERVICE OBSERVING Service Observing: Warning Tone? n or Conference Tone? Service Observing Allowed with Exclusion? n 988 Administrator Guide for Avaya Communication Manager...
Page 989 Feature-Related System Parameters CALL CENTER SYSTEM PARAMETERS Direct Agent Announcement Delay Only appears if Expert Agent Selection (EAS) or ASAI Link Core Capabilities on the System-Parameters Customer-Options screen is y. Valid entries Usage 0 to 99 or blank Enter the number of seconds the caller will hear ringback before the Direct Agent Announcement is heard by the calling party.
Page 990 Controls the use of BSR available agent adjustments. The Vectoring (Best Service Routing) field must be y on the System-Parameters Customer-Options screen. Valid entries Usage Enter y to allow adjustments to available agents. 990 Administrator Guide for Avaya Communication Manager...
Page 991 Feature-Related System Parameters Converse First Data Delay/Second Data Delay The First Data Delay prevents data from being outpulsed (as a result of a converse vector step) from the system to CONVERSANT before CONVERSANT is ready. The delay commences when the CONVERSANT port answers the call. The Second Data Delay is used when two groups of digits are being outpulsed (as a result of a converse vector step) from the system to CONVERSANT.
Page 992 "collect" vector step. If set to y, it does not affect any other DEFINITY vector step or other non-ACD DEFINITY feature (such as ARS) in that the "*" and "#" digit-processing is unchanged. 992 Administrator Guide for Avaya Communication Manager...
Page 993: Service Observing
Feature-Related System Parameters SERVICE OBSERVING or Conference Tone Service Observing (Basic) on the System-Parameters Customer-Options screen must be y before this field may be administered. Valid entries Usage Enter y to assign a conference tone to be given to telephone users and calling parties whenever their calls are being monitored using the Service Observing feature.
Page 994: Agent And Call Selection
Enter y to have agents who are in After Call Work included in the Most-Idle Agent queue. This means that ACW is counted as idle time. Enter n to exclude ACW agents from the queue. 994 Administrator Guide for Avaya Communication Manager...
Page 995 Puts an agent on stand-by only for secondary skills. Call Selection Measurement This field determines how Avaya Communication Manager selects a call for an agent when the agent becomes available and there are calls in queue. For information on Business Advocate, please contact your Avaya Account Executive or see the Avaya Business Advocate Release 11 User Guide, 585-210-711.
Page 996 This field determines whether Avaya Communication Manager changes agents’ call handling preferences when a skill using Service Level Supervisor exceeds its Level 1 threshold. For information on Business Advocate, please contact your Avaya Account Executive or see the Avaya Business Advocate Release 3 Version 11 User Guide.
Page 997 Feature-Related System Parameters Send UCID to ASAI Valid entries Usage Enter y to enable transmission of Universal Call ID (UCID) information to ASAI. CALL MANAGEMENT SYSTEM ACD Login Identification Length Enter the number of digits for an ACD Agent Login ID if Expert Agent Selection (EAS) on the System-Parameters Customer-Options screen is n.
Page 998 Clear VuStats Shift Data Valid entries Usage on-login Enter on-login to clear shift data for an agent when the agent logs in. at-midnight Enter at-midnight to clear shift data for all agents at midnight. 998 Administrator Guide for Avaya Communication Manager...
Page 999 Feature-Related System Parameters Remove Inactive BCMS/VuStats Agents Valid entries Usage Agents are removed from reports when they have no staff time during the previous 7 days. Agents remain on the report even if they have no staff time for any period of time. Validate BCMS/VuStats Login IDs Valid entries Usage...
Page 1000 Enter forced to force an agent to enter a Reason Code when entering AUX mode. To enter forced, the Reason Codes and EAS on the System-Parameters Customer-Options screen must be y. 1000 Administrator Guide for Avaya Communication Manager...

Avaya Communication Manager Administrator's Manual

Chapter 1: System Basics

Chapter 2: Planning the System

Chapter 3: Managing Telephones

Chapter 4: Managing Telephone Features

Chapter 5: Managing Attendant Consoles

Chapter 6: Managing Displays

Chapter 7: Handling Incoming Calls

Chapter 8: Routing Outgoing Calls

Chapter 9: Managing Multimedia Calling

Chapter 10: Setting up Telecommuting

Chapter 11: Enhancing System Security

Chapter 12: Managing Trunks

Chapter 13: Managing Announcements

Chapter 14: Managing Group Communications

Chapter 15: Managing Data Calls

Chapter 16: Administering Media Servers

Chapter 17: Collecting Billing Information

Chapter 18: Telephone Reference

Chapter 19: Screen Reference

Quick Links

Troubleshooting

Related Manuals for Avaya Communication Manager

Summary of Contents for Avaya Communication Manager