What's New in Avaya Aura™ Communication Manager, SIP Enablement Services, Avaya Servers and Media Gateways For Release 5.2

Whats New in Avaya Aura Communication Manager, SIP Enablement Services, Avaya Servers and Media Gateways for
Release 5.2
03-601528 Issue 4 May 2009
2010 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes. Documentation disclaimer Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End User. Link disclaimer Avaya is not responsible for the contents or reliability of any linked Websites referenced within this site or documentation(s) provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages. Warranty Avaya provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avayas standard warranty language, as well as information regarding support for this product, while under warranty, is available to Avaya customers and other parties through the Avaya Support Website: http://www.avaya.com/support. Please note that if you acquired the product from an authorized Avaya reseller outside of the United States and Canada, the warranty is provided to you by the said Avaya reseller and not by Avaya. Licenses The software license terms available on the Avaya Website, http://support.avaya.com/licenseinfo/ are applicable to anyone who downloads, uses and/or installs Avaya software, purchased from Avaya Inc., any Avaya affiliate, or an authorized Avaya reseller (as applicable) under a commercial agreement with Avaya or an authorized Avaya reseller. Unless otherwise agreed to by Avaya in writing, Avaya does not extend this license if the software was obtained from anyone other than Avaya, an Avaya affiliate or an Avaya authorized reseller, and Avaya reserves the right to take legal action against you and anyone else using or selling the software without a license. By installing, downloading or using the software, or authorizing others to do so, you, on behalf of yourself and the entity for whom you are installing, downloading or using the software (hereinafter referred to interchangeably as you and end user), agree to these terms and conditions and create a binding contract between you and Avaya Inc. Or the applicable Avaya affiliate (Avaya). Avaya grants End User a license within the scope of the license types described below. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the Documentation or other materials available to End User. Designated Processor means a single stand-alone computing device. Server means a Designated Processor that hosts a software application to be accessed by multiple users. Software means the computer programs in object code, originally licensed by Avaya and ultimately utilized by End User, whether as stand-alone products or pre-installed on Hardware. Hardware means the standard hardware originally sold by Avaya and ultimately utilized by End User. License types Designated System(s) License (DS): End User may install and use each copy of the Software on only one Designated Processor, unless a different number of Designated Processors is indicated in the Documentation or other materials available to End User. Avaya may require the Designated Processor(s) to be identified by type, serial number, feature key, location or other specific designation, or to be provided by End User to Avaya through electronic means established by Avaya specifically for this purpose. Concurrent User License (CU): End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A Unit means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an e-mail or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the
Software that permits one user to interface with the Software. Units may be linked to a specific, identified Server. Named User License (NU): End User may: (i) install and use the Software on a single Designated Processor or Server per authorized Named User (defined below); or (ii) install and use the Software on a Server so long as only authorized Named Users access and use the Software. Named User means a user or device that has been expressly authorized by Avaya to access and use the Software. At Avaya's sole discretion, a Named User may be, without limitation, designated by name, corporate function (for example, webmaster or helpdesk), an e-mail or voice mail account in the name of a person or corporate function, or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Shrinkwrap License (SR): Customer may install and use the Software in accordance with the terms and conditions of the applicable license agreements, such as shrinkwrap or clickthrough license accompanying or applicable to the Software (Shrinkwrap License). (See Third-party Components for more information).
Copyright Except where expressly stated otherwise, no use should be made of materials on this site, the Documentation(s) and Product(s) provided by Avaya. All content on this site, the documentation(s) and the product(s) provided by Avaya including the selection, arrangement and design of the content is owned either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part, including any code and software. Unauthorized reproduction, transmission, dissemination, storage, and or use without the express written consent of Avaya can be a criminal, as well as a civil, offense under the applicable law. Third Party Components Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements (Third Party Components), which may contain terms that expand or limit rights to use certain portions of the Product (Third Party Terms). Information regarding distributed Linux OS source code (for those Products that have distributed the Linux OS source code), and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply to them is available on the Avaya Support Website: http://support.avaya.com/Copyright. Preventing toll fraud Toll fraud is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of toll fraud associated with your system and that, if toll fraud occurs, it can result in substantial additional charges for your telecommunications services. Avaya fraud intervention If you suspect that you are being victimized by toll fraud and you need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at +1-800-643-2353 for the United States and Canada. For additional support telephone numbers, see the Avaya Support Website: http://www.support.avaya.com/. Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to:securityalerts@avaya.com. Trademarks Avaya and Avaya Aura are trademarks of Avaya Inc. The trademarks, logos and service marks (Marks) displayed in this site, the documentation(s) and product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, or other third parties. Users are not permitted to use such Marks without prior written consent from Avaya or such third party which may own the Mark. Nothing contained in this site, the documentation(s) and product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the express written permission of Avaya or the applicable third party. All non-Avaya trademarks are the property of their respective owners. Downloading documents For the most current versions of documentation, see the Avaya Support Website: http://www.avaya.com/support. Contact Avaya Support Avaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Website: http://www.avaya.com/support.
Copyright 2010, Avaya Inc. All Rights Reserved Notice Every effort was made to ensure that the information in this document was complete and accurate at the time of printing. However, information is subject to change. Warranty Avaya Inc. provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avayas standard warranty language as well as information regarding support for this product, while under warranty, is available through the following Web site: http://www.avaya.com/support. Preventing Toll Fraud "Toll fraud" is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there may be a risk of toll fraud associated with your system and that, if toll fraud occurs, it can result in substantial additional charges for your telecommunications services. Avaya Fraud Intervention If you suspect that you are being victimized by toll fraud and you need technical assistance or support, in the United States and Canada, call the Technical Service Center's Toll Fraud Intervention Hotline at 1-800-643-2353. Disclaimer Avaya is not responsible for any modifications, additions or deletions to the original published version of this documentation unless such modifications, additions or deletions were performed by Avaya. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation to the extent made by the Customer or End User. How to Get Help For additional support telephone numbers, go to the Avaya support Web site: http://www.avaya.com/support. If you are: Within the United States, click the Escalation Contacts link that is located under the Support Tools heading. Then click the appropriate link for the type of support that you need. Outside the United States, click the Escalation Contacts link that is located under the Support Tools heading. Then click the International Services link that includes telephone numbers for the international Centers of Excellence. Providing Telecommunications Security Telecommunications security (of voice, data, and/or video communications) is the prevention of any type of intrusion to (that is, either unauthorized or malicious access to or use of) your company's telecommunications equipment by some party. Your company's "telecommunications equipment" includes both this Avaya product and any other voice/data/video equipment that could be accessed via this Avaya product (that is, "networked equipment"). An "outside party" is anyone who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf. Whereas, a "malicious party" is anyone (including someone who may be otherwise authorized) who accesses your telecommunications equipment with either malicious or mischievous intent. Such intrusions may be either to/through synchronous (time-multiplexed and/or circuit-based), or asynchronous (character-, message-, or packet-based) equipment, or interfaces for reasons of: Utilization (of capabilities special to the accessed equipment) Theft (such as, of intellectual property, financial assets, or toll facility access) Eavesdropping (privacy invasions to humans) Mischief (troubling, but apparently innocuous, tampering) Harm (such as harmful tampering, data loss or alteration, regardless of motive or intent) Be aware that there may be a risk of unauthorized intrusions associated with your system and/or its networked equipment. Also realize that, if such an intrusion should occur, it could result in a variety of losses to your company (including but not limited to, human/data privacy, intellectual property, material assets, financial resources, labor costs, and/or legal costs).
Responsibility for Your Companys Telecommunications Security The final responsibility for securing both this system and its networked equipment rests with you - Avayas customer system administrator, your telecommunications peers, and your managers. Base the fulfillment of your responsibility on acquired knowledge and resources from a variety of sources including but not limited to: Installation documents System administration documents Security documents Hardware-/software-based security tools Shared information between you and your peers Telecommunications security experts To prevent intrusions to your telecommunications equipment, you and your peers should carefully program and configure: Your Avaya-provided telecommunications systems and their interfaces Your Avaya-provided software applications, as well as their underlying hardware/software platforms and interfaces Any other equipment networked to your Avaya products TCP/IP Facilities Customers may experience differences in product performance, reliability and security depending upon network configurations/design and topologies, even when the product performs as warranted. Product Safety Standards This product complies with and conforms to the following international Product Safety standards as applicable: IEC 60950 or IEC 60950-1, including all relevant national deviations as listed in the IECEE BulletinProduct Category OFF: IT and Office Equipment. CAN/CSA-C22.2 No. 60950 / UL 60950 or CAN/CSA-C22.2 No. 60950-1 / UL 60950-1. This product may contain Class 1 laser devices. Class 1 Laser Product Luokan 1 Laserlaite Klass 1 Laser Apparat Electromagnetic Compatibility (EMC) Standards This product complies with and conforms to the following international EMC standards, as applicable: CISPR 22, including all national standards based on CISPR 22. CISPR 24, including all national standards based on CISPR 24. IEC 61000-3-2 and IEC 61000-3-3. Avaya Inc. is not responsible for any radio or television interference caused by unauthorized modifications of this equipment or the substitution or attachment of connecting cables and equipment other than those specified by Avaya Inc. The correction of interference caused by such unauthorized modifications, substitution or attachment will be the responsibility of the user. Pursuant to Part 15 of the Federal Communications Commission (FCC) Rules, the user is cautioned that changes or modifications not expressly approved by Avaya Inc. could void the users authority to operate this equipment. Federal Communications Commission Part 15 Statement: For a Class A digital device or peripheral: Note: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense.
For a Class B digital device or peripheral: Note: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. However, there is no quarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures: Reorient or relocate the receiving antenna. Increase the separation between the equipment and reveiver. Connect the equipment into an outlet on a circuit different from that to which the reveiver is connected. Consult the dealer or an experienced radio/TV technician for help. Equipment With Direct Inward Dialing (DID): Allowing this equipment to be operated in such a manner as to not provide proper answer supervision is a violation of Part 68 of the FCCs rules. Proper Answer Supervision is when: A. This equipment returns answer supervision to the public switched telephone network (PSTN) when DID calls are: answered by the called station, answered by the attendant, routed to a recorded announcement that can be administered by the customer premises equipment (CPE) user Routed to a dial prompt B. This equipment returns answer supervision signals on all (DID) calls forwarded back to the PSTN. Permissible exceptions are: A call is unanswered A busy tone is received A reorder tone is received Avaya attests that this registered equipment is capable of providing users access to interstate providers of operator services through the use of access codes. Modification of this equipment by call aggregators to block access dialing codes is a violation of the Telephone Operator Consumers Act of 1990. Automatic Dialers: When programming emergency numbers and (or) making test calls to emergency numbers: Remain on the line and briefly explain to the dispatcher the reason for the call. Perform such activities in the off-peak hours, such as early morning or late evenings. Toll Restriction and least Cost Routing Equipment: The software contained in this equipment to allow user access to the network must be upgraded to recognize newly established network area codes and exchange codes as they are placed into service. Failure to upgrade the premises systems or peripheral equipment to recognize the new codes as they are established will restrict the customer and the customers employees from gaining access to the network and to these codes. For equipment approved prior to July 23, 2001: This equipment complies with Part 68 of the FCC rules. On either the rear or inside the front cover of this equipment is a label that contains, among other information, the FCC registration number, and ringer equivalence number (REN) for this equipment. If requested, this information must be provided to the telephone company. For equipment approved after July 23, 2001: This equipment complies with Part 68 of the FCC rules and the requirements adopted by the Administrative Council on Terminal Attachments (ACTA). On the rear of this equipment is a label that contains, among other information, a product identifier in the format US:AAAEQ##TXXX. If requested, this number must be provided to the telephone company. The REN is used to determine the quantity of devices that may be connected to the telephone line. Excessive RENs on the telephone line may result in devices not ringing in response to an incoming call. In most, but not all areas, the sum of RENs should not exceed 5.0. To be certain of the number of devices that may be connected to a line, as determined by the total RENs, contact the local telephone company. For products
approved after July 23, 2001, the REN for this product is part of the product identifier that has the format US:AAAEQ##TXXX. The digits represented by ## are the REN without a decimal point (for example, 03 is a REN of 0.3). For earlier products, the REN is separately shown on the label. Means of Connection: Connection of this equipment to the telephone network is shown in the following table: Manufacturers FIC Code Port Identifier Off premises OL13C station DID trunk 02RV2.T CO trunk Tie trunk Basic Rate Interface 1.544 digital interface 120A4 channel service unit 02GS2 02LS2 TL31M 02IS5 04DU9.BN 04DU9.1KN 04DU9.1SN 04DU9.DN SOC/ REN/A.S. Network Jacks Code 9.0F RJ2GX, RJ21X, RJ11C AS.2 RJ2GX, RJ21X, RJ11C 0.3A RJ21X, RJ11C 0.3A RJ21X, RJ11C 9.0F RJ2GX 6.0F, 6.0Y RJ49C 6.0F 6.0F 6.0F 6.0Y RJ48C, RJ48M RJ48C, RJ48M RJ48C, RJ48M RJ48C
If this equipment causes harm to the telephone network, the telephone company will notify you in advance that temporary discontinuance of service may be required. But if advance notice is not practical, the telephone company will notify the customer as soon as possible. Also, you will be advised of your right to file a complaint with the FCC if you believe it is necessary. The telephone company may make changes in its facilities, equipment, operations or procedures that could affect the operation of the equipment. If this happens, the telephone company will provide advance notice in order for you to make necessary modifications to maintain uninterrupted service. If trouble is experienced with this equipment, for repair or warranty information, please contact the Technical Service Center at 1-800-242- 2121 or contact your local Avaya representative. If the equipment is causing harm to the telephone network, the telephone company may request that you disconnect the equipment until the problem is resolved. A plug and jack used to connect this equipment to the premises wiring and telephone network must comply with the applicable FCC Part 68 rules and requirements adopted by the ACTA. A compliant telephone cord and modular plug is provided with this product. It is designed to be connected to a compatible modular jack that is also compliant. Connection to party line service is subject to state tariffs. Contact the state public utility commission, public service commission or corporation commission for information. Installation and Repairs Before installing this equipment, users should ensure that it is permissible to be connected to the facilities of the local telecommunications company. The equipment must also be installed using an acceptable method of connection. The customer should be aware that compliance with the above conditions may not prevent degradation of service in some situations. Repairs to certified equipment should be coordinated by a representative designated by the supplier. It is recommended that repairs be performed by Avaya certified technicians. FCC Part 68 Suppliers Declarations of Conformity Avaya Inc. in the United States of America hereby certifies that the equipment described in this document and bearing a TIA TSB-168 label identification number complies with the FCCs Rules and Regulations 47 CFR Part 68, and the Administrative Council on Terminal Attachments (ACTA) adopted technical criteria. Avaya further asserts that Avaya handset-equipped terminal equipment described in this document complies with Paragraph 68.316 of the FCC Rules and Regulations defining Hearing Aid Compatibility and is deemed compatible with hearing aids. Copies of SDoCs signed by the Responsible Party in the U. S. can be obtained by contacting your local sales representative and are available on the following Web site: http://support.avaya.com/DoC. Canadian Conformity Information This Class A (or B) digital apparatus complies with Canadian ICES-003. Cet appareil numrique de la classe A (ou B) est conforme la norme NMB-003 du Canada. This product meets the applicable Industry Canada technical specifications/Le prsent materiel est conforme aux specifications techniques applicables dIndustrie Canada.
European Union Declarations of Conformity
Avaya Inc. declares that the equipment specified in this document bearing the "CE" (Conformit Europenne) mark conforms to the European Union Radio and Telecommunications Terminal Equipment Directive (1999/5/EC), including the Electromagnetic Compatibility Directive (2004/108/EC) and Low Voltage Directive (2006/95/EC). Copies of these Declarations of Conformity (DoCs) can be obtained by contacting your local sales representative and are available on the following Web site: http://support.avaya.com/DoC. European Union Battery Directive
Avaya Inc. supports European Union Battery Directive 2006/66/EC. Certain Avaya Inc. products contain lithium batteries. These batteries are not customer or field replaceable parts. Do not disassemble. Batteries may pose a hazard if mishandled. Japan The power cord set included in the shipment or associated with the product is meant to be used with the said product only. Do not use the cord set for any other purpose. Any non-recommended usage could lead to hazardous incidents like fire disaster, electric shock, and faulty operation. If this is a Class A device: This is a Class A product based on the standard of the Voluntary Control Council for Interference by Information Technology Equipment (VCCI). If this equipment is used in a domestic environment, radio disturbance may occur, in which case, the user may be required to take corrective actions.

If this is a Class B device: This is a Class B product based on the standard of the Voluntary Control Council for Interference from Information Technology Equipment (VCCI). If this is used near a radio or television receiver in a domestic environment, it may cause radio interference. Install and use the equipment according to the instruction manual. Downloading documents For the most current versions of documentation, see the Avaya Support Web site: http://www.avaya.com/support
Contents
Chapter 1: Whats New for Communication Manager . . . . . . . . . . . . . . . . . . . . . Avaya Aura Communication Manager . . . . . . . . . . . . . . . . . . . . . . . . . . Avaya Aura Communication Manager Messaging . . . . . . . . . . . . . . . . . . . Automatic Callback with Called Party Queuing . . . . . . . . . . . . . . . . . . . . . . Avaya Installation Wizard enhancements . . . . . . . . . . . . . . . . . . . . . . . . . Call Log Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Log Forwarded Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chained Call Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Edit Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enhanced Call Pickup Alerting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enhanced Diversion Indication in SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . Enhanced Redirection Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extension to Cellular features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gateway Installation Wizard enhancements . . . . . . . . . . . . . . . . . . . . . . . . Hot Desking Enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Personal Station Access (PSA) . . . . . . . . . . . . . . . . . . . . . . . . . . . Station Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Improved Port Network Recovery from Control Network Outages . . . . . . . . . . . . IP Server Interface (IPSI) administration enhancements . . . . . . . . . . . . . . . . . LDAP Directory Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Limit Number of Concurrent Calls (LNCC) enhancements . . . . . . . . . . . . . . . . Making Standard Phone Features easier to use . . . . . . . . . . . . . . . . . . . . . . New command to handle Main Server and LSP Server split registrations . . . . . . . PIN Checking for Private Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reports . . . . . . . . . . . . . . . . . . . . . . . . . New Malicious Call Trace History Report . . . . New Voice/Network Statistics Reports . . . . . . Modified reports for Voice/Network Statistics . . Modified IP DSP-Resource reports . . . . . . . . Port Network Level DSP-Resource Reports . H.248 Gateway Level DSP-Resource Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 9 9 10 11 12 12 12 13 14 14 15 16 16 17 17 17 18 19 20 21 21 22 22 23 23 24 24 25 25 25 26 26 27 27 27 28
Return Call to (same) Attendant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAC/Call Forwarding Override . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . S8400 as an ESS server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Support for Processor Ethernet on duplicated servers . . . . . . . . . . . . . . . . . .
Whats New for Release 5.2
Issue 4 May 2009
Contents
Enhanced ESS Requirements Configuration. Administration
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
29 29 29 29 30 30 32 32 33 33 35 35 35 37 37 37 38 38 39 39
System Management Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Team Button enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrades and migrations . . . . . . . . . . . . . . Supported upgrade process . . . . . . . . . . Upgrade Tool Eliminated . . . . . . . . . . . . Error resistant download through secure http . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 2: Whats New for SIP Enablement Services (SES) . . . . . . . . . . . . . . . . . Avaya Aura SIP Enablement Services . . . . . . . . . . . . . . . . . . . . . . . . . . Avaya Aura SIP Enablement Services Upgrades . . . . . . . . . . . . . . . . . . . . Chapter 3: Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G430 Media Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G450 Supports 1024 Announcement Files . . . . . . . . . . . . . . . . . . . . . . . . . S8300D Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . US Robotics modem support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Administration and Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . Components included with the US Robotics Modem . . . . . . . . . . . . . . . . .
Whats New for Release 5.2
Issue 4 May 2009
Chapter 1: Whats New for Communication Manager

This chapter presents an overview of the new features and enhancements for Avaya Communication Manager Release 5.2 running on Avaya S8xxx servers with associated Avaya media gateways.
Avaya Aura Communication Manager

Avaya Communication Manager is now known as Avaya Aura Communication Manager. Avaya Aura adds powerful new capabilities to Communication Manager, including session management that enables multi-vendor hardware and software to communicate across the enterprise network. Avaya Aura orchestrates a wide array of communications applications and systems by decoupling applications from the network. As a result, services can be deployed to users depending on what they need rather than by where they work or the capabilities of the system to which they are connected. Avaya Aura supports single cross-enterprise dial plans and centralized administration, reducing operating costs and speeding up rollouts of new applications. New aggregated presence features and the inclusion of Avaya one-X Unified Communications interfaces allow businesses to take full advantage of unified communications application and solutions.
Avaya Aura Communication Manager Messaging

Avaya Aura Communication Manager Messaging (formerly known as Intuity Audix 770) Release 5.2 has the following enhancements:

Full Web Administration Support for the S8500C Server with up to 5,000 mailboxes Support for the S8510 Server with up to 6,000 mailboxes The Communication Manager license includes the Communication Manager Messaging application with up to 500 mailboxes. Communication Manager Messaging enforces licensing for mailboxes in excess of 500 Increase in voice mail port capacities for the S8300 and S8400 Servers
Issue 4 May 2009
Whats New for Communication Manager
S8300 Server supports 12 call answer ports and 450 users S8400 Server supports 20 call answer ports and 900 users
Enhanced List Application feature UDP Centralized Messaging System Extension (CMS) Subscriber Time Zone Class Of Service (COS) Administration IMAP4 enhancements, Server Side Folders CPN/ANI display to 39 digits Support * dial string with Communication Manager Enhanced no cover 0 Mailbox lockout notification Private Message Handling for IMAP4, POP3, and outgoing SMTP Intuity Audix R5.1 migration to Communication Manager Messaging Release 5.2 Intuity Audix R4.4 migration to Communication Manager Messaging Release 5.2 Intuity Audix LX R2.0 migration to Communication Manager Messaging Release 5.2 Intuity Audix LX R1.1 migration to Communication Manager Messaging Release 5.2
Automatic Callback with Called Party Queuing

Automatic Callback (ACB) is enhanced to allow queuing of called parties. This feature works on analog, DCP, IP (H.323), and SIP telephones. Automatic Callback allows:
Multiple active callbacks for an extension, subject to the limitation on the total number of callbacks within the system. Callbacks for softphones, provided the softphone has at least one bridged call appearance on a physical station.
A called telephone can have multiple active automatic callbacks. The callbacks are processed in the order in which they are activated. If a calling station uses multiple call appearances, the number of automatic callbacks depends on the number of Automatic Callback buttons assigned to the station.
10 Whats New for Release 5.2
Avaya Installation Wizard enhancements
Automatic Callback works the same way as it does on a local server, on the following networks:
On a Distributed Communication Server (DCS) network, ACB requests from or to a station located on a different Communication Manager are queued and processed. If your public service network provider supports ISDN Call Completion Busy Subscriber (CCBS), the CCBS requests are queued and processed. On a QSIG network, ACB requests from or to a station located on a different Communication Manager are queued.
Enable the feature using the Automatic Callback With Called Party Queuing field on the Feature-Related System Parameters screen. For more information, see:

Administering Avaya Aura Communication Manager, 03-300509 Avaya Aura Communication Manager Feature Description and Implementation, 555-245-205 Avaya Aura Communication Manager Screen Reference, 03-602878
Avaya Installation Wizard enhancements

Enhancements for the Avaya Installation Wizard include:

Additional Station Parameters Support for 16xx IP Phones Support for 9670G IP Phone (Large Screen Model) Configure S8400 Servers as an ESS server Configure Communication Manager Messaging (formerly called Intuity Audix 770) on S8500-Series Servers Configure S8400 and S8500-Series Servers for Remote Maintenance Board second Ethernet interface Configure S8700-Series Servers using encrypted software-based duplication Configure Memory (Standard or Extra Large) Note: You can no longer use Avaya Installation Wizard to upgrade Communication Manager. Avaya Installation Wizard supports Internet Explorer version 6 and 7.
Note:
Issue 4 May 2009
11
Call Log Enhancements

Log Forwarded Calls
The Log Forwarded Calls operation creates missed call log entry for calls that are redirected by a forwarding feature. Missed call log entry for a redirected call shows the forwarding icon instead of the missed call icon in the display. So the user knows that the missed call is redirected and might have been answered already by another user. The Log Forwarded Calls option applies to the following redirecting features:

Call-Forwardall, busy, and do not answer Enhanced Call Forward all, busy, and do not answer Coverageall, busy, do not answer, DND, and active Goto-Cover Send-all-calls Note: The Log Forwarded Calls feature is available with Communication Manager Release 5.2, firmware version 3.0 and higher. It is available for 96xx H.323 IP series telephones only.
Note:
Administration of the Log Forwarded Calls option is possible only through the LOGUNSEEN parameter in the phone firmware settings file. With the setting of this parameter, the logging of forwarded calls can be switched on and off.
Chained Call Forwarding

This feature allows calls to be forwarded up to 10 hops (each calling station is considered to be one hop), the default value being 3 hops. Chained call forwarding allows mixed use of standard Call forwarding and Enhanced call forwarding. You can use the coverage path of the last forward-to station in the chain for coverage after forwarding.
Edit Dialing
Mixed use of standard call forwarding (including Call Forwarding All Calls and Call Forward Busy/Dont Answer) and enhanced call forwarding (including Enhanced Call Forwarding Unconditional, Enhanced Call Forwarding Busy, and Use Enhanced Call Forwarding No Reply) is allowed on stations in the forwarding chain. Forwarding stops before the chain gets into an infinite loop or before the call gets back to the originating station. Call forwarding override is enabled on any station in the chain, allowing the call to be transferred to the previous station in the chain.
Enable the feature using the Chained Call Forwarding field on the Feature-Related System Parameters screen. You can also specify the maximum number of hops and a coverage path. For more information, see:

Edit Dialing
The Edit Dialing feature allows an end-user to pre-dial a number when the telephone is on-hook. During the pre-dial phase the user can edit the digits of a dialed number. The number is dialed when the user goes off-hook (lifts handset or presses the speaker button) or presses the send soft key. Edit Dialing is supported by the 96xx-Series with the protocol version H.323 (9620 Lite, 9620 Color, 9650 Color). To use this feature, the software version must be 3.0 or later. SIP telephones are not supported by this feature. Administer the Edit Dialing on 96xx H.323 Terminals field on the Feature-Related System Parameters screen to control this feature for all Edit Dial capable telephones. When enabled, a telephone will go into Edit Dial mode in the on-hook state instead of doing on-hook dialing. For more information, see:

Administering Avaya Aura Communication Manager, 03-300509 Avaya Aura Communication Manager Feature Description and Implementation, 555-245-205
Issue 4 May 2009
13
Enhanced Call Pickup Alerting

The Call Pickup Alerting feature allows users to answer calls for one another, provided the users are members of the same pickup group. In Communication Manager Release 5.2 and later, Call Pickup Alerting is enhanced to provide display of calling and called party information for all members of the pickup group and administrable alerting options. This feature works on DCP and IP (H.323) telephones but not on SIP telephones. When Call Pickup is activated, the displays of all members of the pickup group are updated when another group member receives a call. The calling and called party information is displayed, enabling a member to decide whether to pick up the call or not. If a button is configured for call pickup, anytime the call-pkup button is pressed, details of call to be picked are shown. The following alerting options are added:

Intercom ring Silent if busy (if the user is busy on another call, the audible alerting is skipped.)
Enable the feature using the Enhanced Call Pickup Alerting field on the Feature-Related System Parameters screen. You can also administer the timing of the display and audible notifications. For more information, see:

Enhanced Diversion Indication in SIP

The SIP Diversion indication is enhanced as follows:

Enables successful call redirect to a SIP Service Provider (SP) Supports the following features: a. OPTIM applications EC500, one-X , CSP, FMC (PBFMC or SPFMC) b. Call Forwarding c. Call Coverage d. Call Vector Redirect Uses the SIP Diversion Header
Enhanced Redirection Notification
The following fields are added to the Trunk Group screen:

Send Diversion Header? y/n Support Request History? y/n
Enhanced Redirection Notification

The redirection features available in Communication Manager Release 5.2 include Do Not Disturb, Send All Calls, and Call Forwarding. In Communication Manager Release 5.2 and later, the activation of redirection features at a users station is indicated through visual display or through a special dial tone (if the station is not equipped with a display). This feature works on DCP and IP (H.323) telephones, but not on SIP telephones and attendant consoles. Enhanced Redirection Notification allows display of the status of redirection features, selected posted message, and date and time information.

Do Not Disturb Send All Calls Call Forward Selected Posted Message LNCC Enhanced Call Forward Station lock
If there are multiple status messages, the active features are displayed on a scrolling basis, in the order of decreasing priority. The date and time information is displayed at the end of the loop and has the lowest priority, but is displayed for twice as long as any of the other status messages. If Scroll Status messages Timer is set to blank, scrolling is disabled, and only the feature with the highest priority is displayed. When no feature is active, only the date and time information is displayed. To guard against loading the system with status messages, the scrolling is started in a random manner, for example when the user releases the handset for the first time. Note: After activation or deactivation of the feature, the display might remain unchanged until the first user interaction, such as going on-hook.
Note:
Enhanced Redirection Notification applies only when a station is idle and in normal display mode (not displaying a crisis alert or directory.) Enhanced Redirection Notification does not work if ringing is prevented at the station through use of Silent Ringing, Ringing Abbreviated/ Delayed, or Per Button Ring Control. If the redirection number to be displayed does not fit into the display because the number is too long(18 digits or more), the standard scroll applies.
Issue 4 May 2009
15
Enable the feature using the Redirection Notification field on the Feature-Related System Parameters screen. You can enable notification for specific redirection features and administer the time delay between messages. For more information, see:

Extension to Cellular features

Communication Manager Release 5.2 provides the following new Extension to Cellular features:

Conditional Call Extending (controls which type of calls to extend when EC 500 is enabled) Shared Voice Connections (enables two voice calls to share a single trunk connection between the cell phone and the PBX) Sharing Mappings among Communication Manager PBXs (enables the station name and station mapping information to be available across multiple Communication Manager instances) SPFMC OPTIM Application ( enables support for dual-mode cell phones) one-X Mobile Server and Application Support (enables the use of one-X Server to configure and control a set of features; each extension can support four one-X applications)
Gateway Installation Wizard enhancements

Enhancements to the Gateway Installation Wizard include:
A common Electronic Pre-installation Worksheet to collect and import configuration data for all supported media gateways Support for Electronic Pre-installation Worksheet in Microsoft Excel 2007 file format
Hot Desking Enhancement
Hot Desking Enhancement

Hot Desking is a generic term for features that allow end users to lock and unlock their telephones or to move fully customized station profiles to another compatible telephone. Hot Desking enhances the existing features:

IP Login/Logoff PSA Association/Dissociation Station Lock and Time of Day Station Lock
Hot Desking Enhancement (HDE) does not require any special license to be operational. Parts of the enhancement require firmware changes for the telephones. Only the 96xx-Series H.323 IP telephones with the appropriate firmware change support the full range of HDE. HDE is administered on the Feature-Related System Parameters screen.
Personal Station Access (PSA)

You can enable Personal Station Access (PSA) for H.323 IP telephones. When you log off from PSA, the telephone (any telephone type with a display feature) displays a text message informing you how to log in again. The message is shown on all display telephones, not only on the H.323 telephones. Administer the feature using the Hot Desking Enhancement Station Lock field on the Feature-Related System Parameters screen.
Station Lock
While the HDE feature is active and a station is locked, the following restrictions apply:
Access to telephone capabilities (applies to 96xx H.323 IP telephones with firmware changes) Call log Avaya menu Contact list USB access Redial button Bridging on EC500 calls Bridged appearances
Additionally, if HDE is enabled, some telephone capabilities and some Communication Manager capabilities are locked.
Issue 4 May 2009
17
Improved Port Network Recovery from Control Network Outages

When network fail, IP-connected port networks experience disproportionately long outages from short network disruptions. The Improved Port Network Recovery from Control Network Outages feature provides customers using IP-connected Port Networks with less downtime in the face of IP network failures. The feature lessens the impact of network failures by:
Improving TCP recovery times that increase the IPSI-PCD socket bounce coverage time from the current 6-8 seconds range for the actual network outage to something closer to 10 seconds. Results vary based on traffic rates. Modifying the PKTINT recovery action after a network outage to entail a warm interrupt rather than a PKTINT application reset (hardware interrupt)). This prevents H.323 IP telephones from having to re-register and/or have their sockets regenerated. This minimizes recovery time from network outages in the range of 15-60 seconds.
This feature also monitors the IPSI-PCD socket and helps in identifying and troubleshooting network related problems. For more information see:

Administering Avaya Aura Communication Manager, 03-300509 Administering Network Connectivity on Avaya Aura Communication Manager, 555-233-504 Avaya Application Solutions IP Telephony Deployment Guide, 555-245-600 Avaya Aura Communication Manager Feature Description and Implementation, 555-245-205 Avaya Aura Communication Manager Hardware Description and Reference, 555-245-207 Maintenance Commands for Avaya Aura Communication Manager, Media Gateways and Servers, 03-300431 Using the Avaya Enterprise Survivable Server (ESS), 03-300428
IP Server Interface (IPSI) administration enhancements
IP Server Interface (IPSI) administration enhancements

The IP server interface (IPSI) administration for the TN2312 IPSI or the TN8412 SIPI provides support for Communication Manager based SAT administration of IPSI Quality of Service (QoS) and Ethernet interface settings parameters. All further references to IPSI in this document also apply to the TN8412 SIPI. Note: Initial IPSI settings must still be administered using the command line interface. Set the values of QoS parameter fields (DiffServ and 802.1p) on System Parameters IP Server Interface screen Download QoS parameters to all IPSI boards Send QoS parameters or Ethernet interface settings to IPSI boards in the following cases:

Note:
As an administrator, you can administer and manage the following IPSI related parameters:
On submission of Add IP Server Interface or Change IP Server Interface screen Whenever Communication Manager server connects to IPSI
Set the values of Ethernet interface fields (Auto, Speed, or Duplex) on IP Server Interface screen. Speed and Duplex fields appear on IP Server Interface screen, if Auto field is set to n. Change to DHCP address on the System Management Interface Changes to IPSI IP addresses (IP Address, Subnet Mask, Gateway address) on the IP Server Interface screen Note: The initial IPSI IP address must be a static IP address.
Note:
The IPSI and packet control driver (PCD), parts of the Communication Manager system, use capabilities exchange messages to share exchange of QoS, Ethernet settings, and IP address information with each other to support the IPSI administration feature. In this feature, QoS settings are standardized to communicate between the IPSI and Communication Manager. Communication Manager generates a warning alarm if PCD finds any discrepancies in QoS and Ethernet interface settings parameters. The IPSI administration inter-operates with Communication Manager Release 5.0 or earlier by using the pre-existing QoS and administration interface. Note: IPSI firmware version 46 or greater is required to support Communication Manager.
Note:
Issue 4 May 2009
19
For more information, see:
Administering Network Connectivity on Avaya Aura Communication Manager, 555-233-504 Avaya Aura Communication Manager Screen Reference, 03-602878 Maintenance Commands for Avaya Aura Communication Manager, Media Gateways and Servers, 03-300431
LDAP Directory Application

The LDAP Directory Application is available from the Administration menu in the System Management Interface. The LDAP Directory Application is a part of the Communication Manager and is installed with Avaya S8300D, S8500C, S8510, S8720, and S8730 Servers, while installing or upgrading to Communication Manager Release 5.2. You can use the LDAP Directory Application to search an LDAP database using browsers on your compatible 46xx and 96xx phones. You can use the LDAP Directory Application web pages to configure the LDAP Directory Application to connect to an LDAP database and to customize the user search experience.
Customizable search fields - Search by name, number, email address, or any other LDAP field valid for your directory. LDAP Directory Application supports up to 6 fields. You can use multiple fields in one search to refine results. Customizable detailed results view - Allows for up to 6 fields of data to be displayed. You can label the display results or leave them unlabeled if the results are self explanatory. View up to 96 results in one search. Place calls directly from results or export them to the speed dial list. Link results - Allows you to follow up results from one search with another, related search. For example, this feature can be used to quickly list all the people in the same department as the current person being viewed. Easy-to-use administration application - You can complete the entire administration through the web interface. You can also administer the settings for the Directory Server, search fields, detail fields, and softkey links through the web interface. 46xx-Series IP Telephone LAN Administrator Guide Avaya one-X Deskphone SIP for 96xx-Series IP Telephones Administrator Guide
For more information about configuring the WML Browsers, see:

Limit Number of Concurrent Calls (LNCC) enhancements
Limit Number of Concurrent Calls (LNCC) enhancements

A call to a station that is LNCC-busy is treated like a call to a normal busy station. The call follows the call coverage path for status busy if administrated or hunts to the hunt-to station if administered. For more information, see:

Making Standard Phone Features easier to use

Display messages are provided in additional languages for the following standard telephone features:

Station Security Code Personal Station Access Call Pickup Station Lock Extension to Cellular Call Forwarding Call Coverage Call Park
The enhancements and changes apply only to DCP and IP-H.s323 terminals. This feature does not apply to SIP telephones and stations that act as attendant consoles. Enable this feature by administering the User Guidance Display field on the Feature-Related System Parameters screen.
Issue 4 May 2009
21
New command to handle Main Server and LSP Server split registrations
Split registrations occur when resources on one network region are registered to different servers. For example, after an outage activates Local Survivable Processors (LSPs), telephones in a network region register to the main server or Enterprise Survivable Server (ESS), while the LSP registers the gateways. The telephones registered with the main server are isolated from their trunk resources. You can set the media gateway recovery rules to Immediately to handle split registrations. Communication Manager Release 5.2 provides a new option to manage split registrations. Activate the feature by administering the Force Phones and Gateways to Active LSPs field on the System-Parameters Ip-Options screen. You can force telephones and gateways to register with the main server or the LSP. Split registrations occurring between a main server and LSPs or between an ESS and LSPs are managed by this feature. This feature does not handle split registration between a main server and an ESS. For more information, see:

Administering Avaya Aura Communication Manager, 03-300509 Avaya Aura Communication Manager Screen Reference, 03-602878
PIN Checking for Private Calls

This feature has three new Feature Access Codes (FACs) for logging general calls, ARS (External) calls, and AAR (Internal) calls. For example:

General operation: *11 12345 04069204130 External operation: *12 12345 9 04069204130 Internal operation: *13 12345 04069204130
This feature restricts users from making private calls (internal or external) by forcing them to enter a Personal Identification Number (PIN) code after dialing a PIN feature access code. The user can dial the destination digits to make a call only when the PIN is valid. The PIN code used for the call is reported in Call Detail Record (CDR) output with a special character P.
Reports
The PIN code access feature works in the following way: 1. A user dials new Feature Access Code (FAC) administered for this feature. 2. Confirmation tone is played if the FAC dialed by the user is valid. On telephone sets supporting displays, the user is prompted by message ENTER PIN. 3. After the user dials an Assigned PIN Code and, if the code is accepted, then the user gets a recall dial tone on the telephone to enter destination digits. The telephone displays the ENTER NUMBER message (on the phones with display feature). 4. When the feature is invoked by a display equipped DCP or H.323 IP telephones, a character "*" is displayed for each digit of the PIN code dialed. 5. After the user enters destination number the private call can be routed. Note: SIP telephones are currently not supported with these enhancements. Administering Avaya Aura Communication Manager, 03-300509 Avaya Aura Communication Manager Feature Description and Implementation, 555-245-205
Note:

Reports
The new and modified reports are as follows:

New Malicious Call Trace History Report New Voice/Network Statistics Reports Modified reports for Voice/Network Statistics Modified IP DSP-Resource reports
New Malicious Call Trace History Report

The New Malicious Call Identification (MCID) feature enables your server to signal to an ETSI ISDN network when the network should record the source of an incoming call. Use the list mct-history command to display the SAT-administered Malicious Call Trace History Report.
Issue 4 May 2009
23
New Voice/Network Statistics Reports

The Voice/Network Statistics Reports display hourly and summary level measurement data on packet loss, jitter, round trip delay, and data calls. These reports help you to determine the cause of a voice quality impairment and help you to change the IP parameters at a system level as well, to improve your overall network configuration. The commands to display the SAT-administered Voice/Network Statistics Reports are as follows:
list measurements ip voice-stats hourly jitter <network region number> list measurements ip voice-stats hourly rtdelay <network region number> list measurements ip voice-stats hourly pktloss <network region number> list measurements ip voice-stats hourly data <network region number> list measurements ip voice-stats hourly jitter <media processor board location> list measurements ip voice-stats hourly rtdelay <media processor board location> list measurements ip voice-stats hourly pktloss <media processor board location> list measurements ip voice-stats hourly data <media processor board location> list measurements ip voice-stats summary jitter today list measurements ip voice-stats summary rtdelay today list measurements ip voice-stats summary pktloss today list measurements ip voice-stats summary data today
Modified reports for Voice/Network Statistics

The modified System-Parameters Ip-Options form and IP Interfaces form provide information on the Voice/Network Statistics. In the System-Parameters Ip-Options form, a Voice/Network Stats Field is added to the System-Parameters Ip-Options Report and in IP Interfaces form, the VOIP/Network Thresholds Fields are added to the IP-Interfaces Report.
Reports
The commands to display the SAT-administered System-Parameters Ip-Options Report and IP Interfaces Report are as follows:

change system-parameters ip-options change ip-interface
A new page on Voice/Network Statistics is added to the Status Station Report, which allows you to view real time Voice/Network Statistics. Use the status station command to display the SAT-administered Status Station Report.
Modified IP DSP-Resource reports

The IP DSP-Resource Reports show DSP activity on the IP media processors for specific regions and time periods. The modified commands to display the SAT-administered IP DSP-Resource Reports are as follows:
list measurements ip dsp-resource summary report <yesterday-peak/ today-peak/last-hour> list measurements ip dsp-resource hourly <network region number> list measurements ip dsp-resource detail <network region number> <yesterday-peak/today-peak/last-hour> Note: The existing reports for list measurements ip dsp-resource have been improved to include Port Networks and H.248 Gateways.
Note:
Port Network Level DSP-Resource Reports

The Port Network Level DSP-Resource Reports show DSP activity on the IP media processors for relevant fiber and IP port networks. The new commands to display the SAT-administered Port Network Level DSP-Resource Reports are as follows:

list measurements ip dsp-resource pn summary list measurements ip dsp-resource pn hourly
H.248 Gateway Level DSP-Resource Reports

The H.248 Gateway Level DSP-Resource Reports show DSP activity on the IP media processors for relevant gateways.
Issue 4 May 2009
25
The new commands to display the SAT-administered H.248 Gateway Level DSP-Resource Reports are as follows:

list measurements ip dsp-resource gw summary list measurements ip dsp-resource gw hourly
For more information, see Avaya Aura Communication Manager Reports, 555-233-505.
Return Call to (same) Attendant

The attendant features are improved with the Return Call to (same) Attendant feature. Communication Manager provides individual queuing functions for each attendant supporting a multiplicity of waiting calls at a given time. When at least one call is waiting in the above queue, the Individual Calls Waiting Indicator is displayed in red. Calls queue as long as the attendant is busy. When the Return Call to (same) Attendant feature is enabled, a call returning to a busy or now unavailable same attendant is placed into an individual waiting queue for this attendant, instead of it queuing into the attendant group. A waiting Return Call moves from the attendants queue to the attendant groups queue after a certain period of time. Enable the new feature using the Overflow Timer to Group Queue field on the Console Parameters screen.
SAC/Call Forwarding Override

The Send All Calls and Call Forwarding (SAC/CF) Override feature overrides active rerouting. This feature overrides these active rerouting settings:

Send All Calls (SAC) Call Forwarding (CF) all Enhanced Call Forwarding (ECF) unconditional
The SAC/CF override feature depends on call initiation. On enabling SAC/CF override, the call may:

Execute override - ring called station Execute no override Display a message and wait for further input
S8400 as an ESS server
S8400 as an ESS server

You can now use the S8400 Server as an ESS. An S8400 Server configured as an ESS resides in a port network that is controlled by a S8500 or S8700-Series Server as the main server. The capacities of the port network in which the ESS resides must not exceed the published capacities of the S8400 Server.
!
Important:
Important: Before you start implementing an S8400A Server as an ESS server, you must purchase and install a Memory Upgrade Kit (material code 218452).
Hardware requirements
The TN8400 circuit pack requirements must be one of the following:
TN8400AP with 1 GB DRAM and a 4 GB SSD (the material code for the TN8400AP upgrade kit is 218452) TN8400BP
When S8400 Server is used as an ESS server, the TN8412AP Server IP Interface (SIPI) circuit packs are not supported. If the S8400 ESS server is installed in a G650 Media Gateway, the IP Server Interface (IPSI) that it supports must be a TN2312BP IPSI or later. TN799 C-LAN circuit pack or Processor Ethernet is required if H.248 gateways are to be supported by an S8400 ESS server.
Limitations
The S8400 Server has the following limitations when used as an ESS server:
An S8400 ESS server functions only in a local only mode and can only be installed in a G600, G650, or Communication Manager C1 Media Gateway. An S8400 ESS server cannot be used as a survivability option for an S8400 main server. An S8400 main server can support Communication Manager Messaging service. However, the Communication Manager Messaging administration is blocked in an S8400 ESS server. An S8400 main server can support up to five H.248 Media Gateways using either a TN799 C-LAN circuit pack or Processor Ethernet. An S8400 ESS server can support H.248 Media Gateways using a TN799 C-LAN circuit pack. Processor Ethernet is also supported in this configuration if you administer PE to support H.248 Media Gateways using the Survivable Processor screen.
Issue 4 May 2009
27
You must configure a S8400 server as an ESS using the Server Role page under Configure Server in the System Management Interface. To make an ESS successfully register to the main server, you must administer the ESS on the main server using the Survivable Processor screen. For more information, see Using the Avaya Enterprise Survivable Server (ESS), 03-300428.
Support for Processor Ethernet on duplicated servers

The support for Processor Ethernet on duplicated servers is as follows:
Processor Ethernet is supported on duplicated servers for the connection of H.323 devices, H.248 gateways, SIP trunks, and most adjuncts. The capabilities of Enterprise Survivable Servers (ESS servers) are enhanced to support connection of IP devices to the Processor Ethernet interface and to C-LAN interfaces located in G650 (port network) gateways. See Enhanced ESS. When Processor Ethernet is used on duplicated servers, it must be assigned to an IP address, Active Server IP address, that is shared between the servers. This address is known in networking terminology as an IP-alias. The active server is the only server that will respond on the IP-alias. Note: Processor Ethernet on duplicated servers is supported only on S8720 and S8730 Servers. If you have an S8710 Server anywhere in your network, you cannot enable Processor Ethernet on any S8700-Series Server without first upgrading the S8710 Server to an S8720 or S8730 Server.
Note:
Processor Ethernet on duplicated servers enables configurations without any port networks and allows expansion without buying additional C-LANs. If you do not have sufficient capacity in existing port networks and would need to add another port network to accommodate additional C-LANs, you can use PE instead. Note: Avaya recommends that you use the following IP telephone models to ensure optimal system performance when you use Processor Ethernet on duplicated servers:
Note:
9610, 9620, 9630, 9640, and 9650 telephones with firmware 3.0 or later; any future 96xx models that support TTS (Time to Service) will work optimally. 4601+, 4602SW+, 4610SW, 4620SW, 4621SW, 4622SW, and 4625SW Broadcom telephones with firmware R 2.9 SP1 or later, provided the 46xx telephones are not in the same subnet as the servers. All other IP telephone models will re-register in case of server interchange. The 46xx telephones will re-register if they are in the same subnet as the servers.
Support for Processor Ethernet on duplicated servers
Enhanced ESS
An Enterprise Survivable Server (ESS) can use its Processor Ethernet interface to support IP devices such as H.248 Media Gateways, H.323 Media Gateways, IP Adjuncts, IP telephones, IP trunks, and SIP trunks. The ESS can optionally control port networks (G650 Media Gateways) through IPSI at the same time. When there are no port networks in the configuration, ESS may provide the equivalent benefit of an LSP. The ESS can be duplicated, providing additional redundancy to the survivability of the system.
Requirements
You must fulfill the following for the Processor Ethernet on duplicated servers to work effectively:
Assign the Processor Ethernet interface to the Processor Ethernet Active Server IP Address (IP-alias), and not the server unique address. Ensure that the H.248 gateways and IP telephones are on the most current release of firmware.
Configuration
Use the System Management Interface to configure the main server and ESS servers.
Set Identities page: Determine how the Ethernet interfaces on a server will be used. The Processor Ethernet interface must be assigned to the same NIC as the enterprise LAN. Configure Interfaces page: Configure IP addresses for the network interfaces that were assigned in the Set Identities page and to configure special parameters for the Processor Ethernet interface on duplicated servers.
Administration
Administer the ESS servers using the SAT on the main server.
Use the Survivable Processor screen to administer LSPs and ESS servers to control use of the PE interface. Use the Community Assignments for Port Networks and Port Network Recovery Rules screens to assign port networks to communities and to specify recovery rules for port networks to return to the main server. Using the Avaya Enterprise Survivable Server (ESS), 03-300428 Administering Avaya Aura Communication Manager, 03-300509 Avaya Aura Communication Manager Screen Reference, 03-602878 Upgrading Avaya Aura Communication Manager on Avaya S8xxx Servers, 03-602885

Issue 4 May 2009
29
System Management Interface

The System Management Interface (SMI), formerly known as Maintenance Web Interface, enables you to perform all system management tasks. A top navigation menu is provided on all System Management Interface screens. It provides the Help and Log Off options as well as the menu entries for all system management tasks available for the current session/login. Access to other servers, part of the same system setup, may also be available in the top navigation menu if the server is configured to support this. For more information, refer the online help that is available with the System Management Interface. The System Management Interface supports Internet Explorer version 6 and 7.
Team Button enhancements

The enhancements made to the Team Button feature are as follows:
Allowable monitored station types: Analog stations, BRI-stations, SIP-telephones, X-ports, and X-mobiles are allowed as valid monitored stations, but not as monitoring stations. Attendant consoles are not allowed as monitoring stations or monitored stations. Increased number of team buttons: The number of team buttons per station is increased to a maximum of 31. However, the maximum number of stations that can monitor any one station is 15. In effect, the total number of team buttons in a system is not increased. Enhancements to team button display functions - Hunt group calls can be displayed on the monitoring station if the monitored station is a member of the hunt group. Active, idle, and ringing states are displayed. Hunt group calls can also be picked up from the monitored station. - When there is an incoming call on the monitored station, the audible ringing alert on the monitoring station with at least one active call appearance can be suppressed. - Calls from the monitoring station to monitored station, irrespective of whether they are established by pressing the team button or by dialing, are not displayed on the monitoring station.
Team Button enhancements
Enhancements to team button execution functions - Speed dialing
When the monitored station is accessed from the monitoring station through speed dialing, the type of ringing on the monitored station can be configured as priority ringing or intercom ringing. Speed dialing is treated as enbloc dialing (equivalent to pressing # after dialing the digits) to avoid time-outs in case of multi-location and mixed-length dial plans. When the monitoring station is active on a call, pressing the team button puts the call on hold and establishes a connection to the monitored station. The call can be transferred by pressing the transfer button. On such call transfers, any active Send All Calls (SAC), Call Forwarding (CFWD), and Enhanced Call Forwarding ECF) settings on the monitored station are overridden. However, coverage criteria are followed as set. If the overall call state of the monitoring station is idle, call pickup can be handled by pressing the team button on the monitoring station once and then going off hook. The first press of the team button displays details of the call on the monitored station. If more than one call is ringing on the monitored station, details of other calls can be viewed by pressing Next. When two monitoring stations press the team button of the same monitored station, call details are displayed on both the monitoring stations, but the station that first goes off-hook or presses the speaker button gets to answer the call and the display on the other monitoring station is erased. Note: If the overall call status of the monitoring station is any state other than idle, you need to press the team button a second time to get the call redirected and pick up the call.
- Call Pickup
When the monitoring station is active on a call and the monitored station is ringing, pressing the team button twice will first display the extension number of the calling station and then pick the call, putting the active connection on hold, if the Auto Hold? system parameter feature is set to y.
Button labels: You have the option to use the name of the monitored station name instead of its extension.
Enable the enhancements using the Team Btn group of fields on the Class of Restriction screen. For more information, see:

Issue 4 May 2009
31
Upgrades and migrations

Supported upgrade process
To upgrade Communication Manager to Avaya Aura Communication Manager Release 5.2, you need to follow the same upgrade process as done for previous Communication Manager Releases, if those upgrade processes included using the Manage Software or Software Update Manager. The changes for Communication Manager Release 5.2 are as follows:

You can no longer use the Upgrade Tool for the upgrade. You can no longer use Avaya Installation Wizard (AIW) for the upgrade. Changed upgrade procedure, if you are upgrading a system that includes S8700-Series Server
You can upgrade to Communication Manager Release 5.2 software from all previous releases of Communication Manager, provided the upgrade is a software upgrade that does not involve a migration. Communication Manager Release 5.2 is supported on the following server platforms:
S8710 (with DAL2), S8720 (with DAL2 if hardware duplication), S8730 (with DAL2 if hardware duplication) S8500 (B/C), S8510 S8300 (B/C) but with SES only on S8300C S8400 A/B
For Communication Manager Release 5.2, the Processor Ethernet is supported for Duplicated Servers. Customers with releases prior to Communication Manager Release 5.2 can upgrade to Communication Manager Release 5.2 Processor Ethernet on Duplicated Servers (S8720 or S8730 Server). Note: The Processor Ethernet interface supported on S8720 and S8730 Servers is for endpoints, gateways, or adjunct connectivity in Communication Manager Release 5.2 and later. If you have an S8710 Server anywhere in your network, you cannot enable Processor Ethernet on any S87xx-Series Server without first upgrading the S8710 Server to an S8720 or S8730 Server.
Note:
For more information on upgrades and upgrade paths, see Upgrading Avaya Aura Communication Manager on Avaya S8xxx Servers, 03-602885.
Upgrades and migrations
Upgrade Tool Eliminated

You cannot use the Upgrade Tool to upgrade Communication Manager to Release 5.2 or later. After Communication Manager 5.2 is running on the server, the System Management Interface displays a reference to the Upgrade Tool (from Upgrade > Upgrade Tool). Note: The reference to Upgrade Tool is for information only, and if you access the Upgrade Tool link, the system displays the following message: The "Upgrade Tool" (UT) is no longer available. Please use one of the following upgrade tools: - Software Update Manager (SUM). - Manage Software option under Upgrade within the System Management Interface (SMI).
Note:
Error resistant download through secure http

Avaya Aura Communication Manager Release 5.2 implements upgrade improvements to provide a more robust system upgrade experience. These upgrade improvements enable you to:
Reduce copy size from files size (which currently can approach 100MB) to something more granular (for example: block size) such that when remote upgrades are being performed over a bouncing network, much of the copying is done without re-transmittal. Support SCP and HTTPS protocols to allow secure file transfers. View the progress of the upgrade file transfers and processes, specifically that the process is progressing and not hung. The progress is displayed in text only format.
Issue 4 May 2009
33
Chapter 2: Whats New for SIP Enablement Services (SES)

This chapter presents an overview of the features and enhancements of SIP Enablement Services (SES) Release 5.2.
Avaya Aura SIP Enablement Services

SIP Enablement Services is now known as Avaya Aura SIP Enablement Services.
Avaya Aura SIP Enablement Services Upgrades

Cable Duplicated Avaya Aura SIP Enablement Services server pairs, deployed on SIP Enablement Services Releases 5.1.x and earlier, require an upgrade to the Distributed Replicated Block Device (DRBD) when upgrading to Avaya Aura SIP Enablement Services Release 5.2. The Distributed Replicated Block Device (DRBD) is automatically upgraded during the upgrade to SIP Enablement Services Release 5.2. The procedure for upgrading a cable duplicated pair of servers in SIP Enablement Services Release 5.2 has changed from previous releases. For more information on the latest upgrade procedures, see Installing, Administering, Maintaining, and Troubleshooting Avaya Aura SIP Enablement Services document (03-600768, Issue 7.0).
Issue 4 May 2009
35
Whats New for SIP Enablement Services (SES)
Chapter 3: Hardware
This chapter presents an overview of hardware additions to Avaya Aura Communication Manager Release 5.2.
G430 Media Gateways

The G430 Media Gateway is a high-performance converged telephony and networking device that provides all infrastructure needs in one box. The G430 is a multipurpose media gateway, also deployed as a branch gateway in a medium to large size branch, servicing both traditional and IP endpoints. The G430 provides full support for legacy IP, DCP, and analog telephones. The G430 media gateway supports up to 150 users when deployed with the Avaya S8300 Server and Avaya S8500 Server depending on the voip resources installed. Some features of the G430 Media Gateway:

Telephone exchange and data networking Routing data VoIP traffic over WAN PSTN toll bypass A VoIP engine Ethernet LAN connectivity
The G430 media gateway also features:

For more information, see the G430 documentation at www.avaya.com/support.
G450 Supports 1024 Announcement Files

The Avaya G450 introduces a removable external compact flash that supports the backup and restore of 1024 announcement files (up to 4 hours of storage). This requires a memory upgrade to 512MB from the base 256MB.
Issue 4 May 2009
37
Hardware
S8300D Server
!
Important:
Important: The Avaya S8300D Server will be available after May 2009.
This server is the next version of the S8300C Server.

Processor: 1 CPU 0 model: Intel(R) Core 2 Duo CPU U7500 @ 1.06GHz Physical RAM: 8 GIG Internal Solid State Drive (SSD), interface ATA: 8 GB With increased CPU horsepower and memory, the support for multiple co-resident applications (Avaya Aura Communication Manager , Avaya Aura Communication Manager Messaging, Avaya Aura SIP Enablement Services) is enhanced as follows:

Increased support of number of SIP endpoints to 450 users Support of 12 call answer ports and 450 subscribers for the Avaya Aura Communication Manager Messaging application
US Robotics modem support

The US Robotics 5637-OEM (cc700464506) modem works with the following releases of Communication Manager and SIP Enablement Server. This modem does not have backward compatibility with the previous releases.
Communication Manager 4.0.4 Service Pack 2, 5.1.1 Service Pack 2.01, 5.1.2 Service pack1/later and Avaya Aura Communication Manager 5.2 SIP Enablement Services 4.0.1 Service Pack 1, 5.1.1 Service Pack 3, 5.1.2 Service Pack 1 and Avaya Aura SIP Enablement Services 5.2
The US Robotics 5637-OEM (cc700464506) modem supports all Branch Gateways running the following.
G250, G350, and G450
Communication Manager 4.0, Communication Manager 5.1, and Avaya Aura Communication Manager 5.2 Avaya Aura Communication Manager 5.2
G430
US Robotics modem support
Administration and Management

The US Robotics Modem is connected and administered the same way as previous USB modems, for example MultiTech MT5634ZBA-USB (cc700405020) and MT9234ZBA-USB (cc700451172).
Components included with the US Robotics Modem

USR 5637-OEM Modem Telephone cord USB cable Cord management strap Velcro attachment strips
Issue 4 May 2009
39
Hardware

What's New in Avaya Aura™ Communication Manager, SIP Enablement Services, Avaya Servers and Media Gateways For Release 5.2

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

What's New in Avaya Aura™ Communication Manager, SIP Enablement Services, Avaya Servers and Media Gateways For Release 5.2

Uploaded by

Copyright:

Available Formats

Whats New in Avaya Aura Communication Manager, SIP Enablement Services, Avaya Servers and Media Gateways for

03-601528 Issue 4 May 2009

European Union Declarations of Conformity

Whats New for Release 5.2

Issue 4 May 2009

Enhanced ESS Requirements Configuration. Administration

Whats New for Release 5.2

Issue 4 May 2009

Chapter 1: Whats New for Communication Manager

Avaya Aura Communication Manager

Avaya Aura Communication Manager Messaging

Issue 4 May 2009

Whats New for Communication Manager

Automatic Callback with Called Party Queuing

10 Whats New for Release 5.2

Avaya Installation Wizard enhancements

Avaya Installation Wizard enhancements

Issue 4 May 2009

Whats New for Communication Manager

Call Log Enhancements

Chained Call Forwarding

12 Whats New for Release 5.2

Issue 4 May 2009

Whats New for Communication Manager

Enhanced Call Pickup Alerting

Enhanced Diversion Indication in SIP

14 Whats New for Release 5.2

Enhanced Redirection Notification

The following fields are added to the Trunk Group screen:

Send Diversion Header? y/n Support Request History? y/n

Enhanced Redirection Notification

Issue 4 May 2009

Whats New for Communication Manager

Extension to Cellular features

Gateway Installation Wizard enhancements

16 Whats New for Release 5.2

Hot Desking Enhancement

Hot Desking Enhancement

Personal Station Access (PSA)

Issue 4 May 2009

Whats New for Communication Manager

Improved Port Network Recovery from Control Network Outages

18 Whats New for Release 5.2

IP Server Interface (IPSI) administration enhancements

IP Server Interface (IPSI) administration enhancements

Issue 4 May 2009

Whats New for Communication Manager

For more information, see:

LDAP Directory Application

For more information about configuring the WML Browsers, see:

20 Whats New for Release 5.2

Limit Number of Concurrent Calls (LNCC) enhancements

Limit Number of Concurrent Calls (LNCC) enhancements

Making Standard Phone Features easier to use

Issue 4 May 2009

Whats New for Communication Manager

PIN Checking for Private Calls

22 Whats New for Release 5.2

For more information, see:

New Malicious Call Trace History Report

Issue 4 May 2009

Whats New for Communication Manager