AA6-2SolutionDefMay2

Solution Definition

Avaya Aura® Release “6.2” Communication Manager (6.2)

Session Manager (6.2)

May 2, 2012

COMPAS ID 154794

ABSTRACT

This document provides a high-level description of the key components of Avaya Aura®: Avaya Aura® Communication Manager 6.2 and Avaya Aura® Session Manager 6.2 as well as the surrounding solution, and the supporting sales offer. This document is for internal and business partner use only and is targeted at Sales and Sales Support organizations. All pricing contained within, while accurate at the time of publication, should be considered as unofficial; associates and business partners are directed to verify the accuracy of all prices cited. NOTE: This Product Definition is a US version and some of the products listed in this document may not be available or applicable to your regions. Please contact your regional Product Management team to obtain the version of this document that is applicable to your region.

Avaya Aura 6.2 Offer Definition COMPAS ID 154794

of 70 Avaya Inc. – Proprietary & Confidential. May 2, 2012 The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

TABLE OF CONTENTS 1. AVAYA AURA® .................................................................................................................... 4

2. SOLUTION DESCRIPTION ............................................................................................... 5

2.1. SERVER OVERVIEW ........................................................................................................ 5 2.2. SOLUTION OVERVIEW ..................................................................................................... 6 2.3. AVAYA AURA 6.2 SOLUTION CAPABILITIES .................................................................... 8 2.4. INTEROPERABILITY ........................................................................................................ 11

3. SESSION MANAGER OFFER DESCRIPTION ............................................................ 15

3.1. SESSION MANAGER APPLIANCE MODEL ...................................................................... 15 3.2. SYSTEM MANAGER SOFTWARE .................................................................................... 16 3.3. PRICING AND MATERIAL CODES ................................................................................... 16 3.4. UPGRADES .................................................................................................................... 20 3.5. IMPLEMENTATION SERVICES ......................................................................................... 20 3.6. AVAILABILITY ................................................................................................................. 20 3.7. SESSION MANAGER REQUIRED HARDWARE ................................................................ 21 3.8. REQUIRED SOFTWARE .................................................................................................. 22 3.9. REQUIRED SYSTEM MANAGER PLATFORM .................................................................. 22 3.10. ORDERING PROCESS WITH ASD .................................................................................. 23

4. COMMUNICATION MANAGER OFFER DESCRIPTION ........................................... 23

4.1. PRICING AND MATERIAL CODES ................................................................................... 24 4.2. SUPPORTED SERVERS .................................................................................................. 24 4.3. COMMUNICATION MANAGER LICENSE FUNCTIONS ...................................................... 27 4.4. AVAYA AURA® FOR SURVIVABLE CORE AND SURVIVABLE REMOTE ............................ 29 4.5. AVAYA AURA® CM BUNDLES FOR THE MID MARKET SOLUTIONS ............................... 29 4.6. ANALOG STATION LICENSES ......................................................................................... 30 4.7. UTILITY SERVICES STANDALONE .................................................................................. 31 4.8. UPGRADES OVERVIEW .................................................................................................. 31 4.9. UPGRADING TO CC 6.X – SOFTWARE .......................................................................... 33 4.10. LICENSING FOR DEMOS, LABS AND TRIALS .................................................................. 34 4.11. ASD CHANGES ............................................................................................................. 35

5. SERVICEABILITY ............................................................................................................. 39

5.1. SOFTWARE SUPPORT AND HARDWARE MAINTENANCE ............................................... 39 5.2. SERVICE ENTITLEMENTS FOR ALL CUSTOMERS .......................................................... 40 5.3. WARRANTY .................................................................................................................... 40 5.4. PRODUCT CORRECTION NOTICES (PCNS) .................................................................. 42 5.5. PRODUCT SUPPORT NOTICES (PSNS) ........................................................................ 43 5.6. TECHNICAL CONSULTING SYSTEM SUPPORT ............................................................... 43 5.7. ENHANCED SERVICES AVAILABLE ................................................................................ 44 5.8. AVAYA LABS FIELD SUPPORT ....................................................................................... 44 5.9. PLDS SOFTWARE DOWNLOAD POLICY........................................................................ 45 5.10. PLDS LICENSES ........................................................................................................... 45 5.11. REMOTE MAINTENANCE ................................................................................................ 45




6. DOCUMENTATION ........................................................................................................... 46

6.1. RELEASE NOTES ........................................................................................................... 46 6.2. USER AND SYSTEM DOCUMENTATION .......................................................................... 46

7. TRAINING ........................................................................................................................... 50

APPENDIX A: AVAYA AURA PACKAGING ....................................................................... 52

APPENDIX B: GLOSSARY OF TERMS AND ACRONYMNS .......................................... 53

APPENDIX C: RELEASE HISTORY LIFECYCLE DATES ............................................... 57

APPENDIX D: ADDITIONS TO CM 4.0 AND EARLIER ................................................... 58

APPENDIX E: SOFTWARE RE-LICENSING POLICY ...................................................... 59

APPENDIX F: CM FEATURES AND RELATED PRODUCTS ......................................... 60

APPENDIX G: MIGRATION AND MERGE OFFERS ........................................................ 61

APPENDIX H: LICENSE MOVES .......................................................................................... 62

APPENDIX I: SURVIVABLE REMOTE AND ICC CONVERSION................................... 63

APPENDIX J: MOVING SURVIVABLE REMOTE AND CORE ....................................... 64

APPENDIX K: UPGRADE PROTECTION PLAN FOR CM 4.0 ......................................... 65

APPENDIX L: ESS CONVERSIONS ..................................................................................... 66

APPENDIX M: RFA LICENSED FEATURES ....................................................................... 67

APPENDIX N: STANDARDS SUPPORTED ........................................................................ 68

NOTES: ....................................................................................................................................... 68

CONTACT INFORMATION ...................................................................................................... 69

PRODUCT MANAGEMENT CONTACTS ....................................................................................... 69




1. AVAYA AURA® Avaya Aura® R6.2 is the flagship product collection for next generation enterprise solutions based on the revolutionary SIP-based Avaya Aura Session Manager (SM). Avaya Aura is enhanced by additional new capabilities of the Avaya Aura core components, the Avaya Aura Session Manager 6.2 and Aura Communication Manager 6.2 (CM). With this release of Avaya Aura the following new capabilities are introduced:

∗ Unprecedented total scale of up to 250,000 total users, and increases in SM capacities and performance

∗ Announcing a new maximum of 36,000 SIP endpoints receiving service from a single CM

∗ An enriched SIP feature set including group call pickup and the “Team” feature set

∗ SIP contact center terminal support ∗ Enterprise Call Admission Control bandwidth usage monitoring, with call

counting, rejected call counts, etc. ∗ Advanced Trunking Flexibility and Features including DTMF interoperability and

Enhanced Type of Network support ∗ Session Manager SIP Call Preservation with Communication Manager, Voice

Portal, M3000 gateway and G860 gateway ∗ System Manager (SMGR) Release 6.2 can manage SM R6.2, SM R6.1, and SM

R6.0 as well as all previous releases of CM since 5.1 For more information see APPENDIX A: Avaya Aura PACKAGING or the Avaya Aura Channel Announcement: http://portal.avaya.com/ptlWeb/products/P0540/AllCollateral Document Update History

Document Date Change Description February 20, 2012 First document release.

May 2, 2012 Added the correct SM DVD Material Codes

http://portal.avaya.com/ptlWeb/products/P0540/AllCollateral�




2. SOLUTION DESCRIPTION This document focuses on the new Avaya Aura 6.2 additions to Avaya Aura Communication Manager (CM) and Avaya Aura Session Manager (SM). Avaya Aura System Manager (SMGR) remains the centralized management vehicle for administering SM and CM. System Manager 6.2 has the capability to administer 250,000 total users in what has become the industry standard “one-stop” centralized enterprise-wide management system. Key customer benefits of Avaya Aura 6.2 are:

• Business continuity assurance driven by the call and connection preservation features built into the 6.2 releases of CM and SM

• Increased customer satisfaction by advanced SIP adaptations with service providers, and the increase in SIP scale

• Lower total cost of ownership from SIP connectivity, decreased management time with SMGR, and improved interoperability with Communication Server 1000 (CS 1000) and 3rd party equipment

• Decreased costs and real convergence with controls for voice, video and data bandwidth allocation over shared resources with new Session Manager call admission control

Additionally, Avaya Aura 6.2 is planned as the Extended Manufacturer Software Support (EMSS) release replacing release 5.2.1 (EMSS). EMSS releases will be sold for a minimum 2 years and will have Tier 4 (new Service Pack) support for a minimum of 3 years from initial sale date.

2.1. Server Overview Avaya Aura 6.2 continues support of the Avaya Common Servers platforms replacing the S8800 servers. Avaya Common Servers enhance the quality and performance of the Avaya Aura applications and solutions. More details on these new servers are included in the respective Session Manager and Communication Manager sections. Note: pricing provided in this document is subject to change with changes initially communicated via Avaya market bulletins. These bulletins and Avaya quoting tools will be considered the authority.

Application Server Type Material Code List Price (USD)

Session Manager HP DL360G7 700501092 $11,500 Dell R610 700501082 $11,500

Communication Manager simplex

HP DL360G7 263764 $8,800 Dell R610 263760 $8,800

Communication HP DL360G7 263765 $21,500




Manager duplex (2 servers are provided)

Dell R610 263761 $21,500

2.2. Solution Overview The unparalleled integration of Avaya Aura CM’s broad and deep feature capabilities with the innovative SIP capabilities of SM deliver the best enterprise solutions ever. New capabilities of the solution include:

• Up to 10 Session Manager instances allowed per SMGR management system with the market–proven active-active N+M reliability first introduced in the SM 1.0 release introduced in 2008

• A new array of SIP endpoint features – Automatic dial buttons, group paging, the team button, enhanced call forwarding, enhanced call pickup alerting, up to 10 emergency numbers, multi-location dial plans, per-button ring control settings, and full contact center functionality

• For the first time, full featured SIP contact center endpoints are now supported. • Increased SM call processing performance of up to 350,000 BHCC per SM • A scale increase for SMGR management for up to 250,000 combined SIP and

non-SIP endpoints (maximum of 100,000 SIP endpoints) • New adaptation module (AM) capabilities to support service providers’

“unscreened ANI” requirements • Support for SIP conferencing resources to be assigned on a per user basis • Support for Cisco SIP handsets registered to SM • Connection preservation for SIP calls with failures and failovers of CM Survivable

Remotes and Survivable Cores • And announcing market leading call preservation where queued calls are not lost

in the face of network or SM failures and existing sessions are actually redirected over the surviving SM network!

In summary, SM, CM and SMGR combine to deliver the following capacity and performance improvements with the advancements in red.




Avaya Aura® Quick Reference Specifications

Item (CM/SM) R6.0.1/R6.1 R6.2/R6.2

Total Enterprise Users 100,000 250,000

Total Enterprise SIP Users 100,000 100,000

SIP Users/CM 18,000 36,000*

SIP Trunks per CM 7,000 24,000*

SIP Users/SM 12,000 12,000

Total Enterprise Presence Users 81,000 81,000

Presence Users/SM 9,000 9,000

SIP Shared Control with SIP Users/SM 7,500 7,500

TLS Connections 100,000 100,000

SM Instances 10 10

BHCC per SM 300,000 350,000

Simultaneous Sessions 80,000 90,000

Registrations/Second per SM Unspecified 800

Advanced SIP Terminal Initializations/Second per SM Unspecified 10**

Survivable Remotes 250 250

Communication Managers/SMGR 500 500

Locations/Adaptations/SIP Entities 25,000 25,000

SIP Domains 1000 1000

Dial Patterns/Routing Policies 300,000 300,000

* Up to 24,000 SIP Trunks or 36,000 SIP endpoints can be engineered with assistance of Avaya Engineering. Note that these capacities are not generally applicable to Call Center solutions. ** Intentionally throttled to work with a single CM




2.3. Avaya Aura 6.2 Solution Capabilities Following is a summary of the capabilities of Avaya Aura Communication Manager 6.2 and Avaya Aura Session Manager 6.2 supported by SMGR 6.2: Unscreened ANI The SM Verizon adaptation module has been augmented with a new capability to match the “unscreened ANI” requirements of service providers. The “screened telephone number” or STN is used to allow any enterprise user to make outgoing calls using any service provider, even if the call is originated from a DID not provided by the service provider. The originating number (PAI) to STN mapping is configured on the adaptation module SMGR screen, using the new column "Adaptation Data".

Figure 1: Unscreened ANI Administration

Cisco Endpoint Support Customers can now use existing Cisco endpoints with the 6.2 release of Session Manager and Communication Manager. SM has made several modifications to handle the standards inconsistencies of Cisco phones.

- SM effectively shortens standard SIP messages so Cisco phones can accept them without degradation functionality

- The unnecessary Accept header is inserted to allow Cisco phones to receive incoming calls

- Cisco phones do not subscribe to the required message waiting feature status package and thus SM detects the Cisco phones and sends out of dialog NOTIFY messages so the MWI indicators will work on Cisco phones.

No special administration for Cisco phones is required as SM detects the Cisco phones and applies the adaptations automatically. Supported and tested Cisco phones are: 7960, with FW version P0S3-8-12-00 and 7961, 7962, 7941, and 794 with FW version 8.5.4. New SIP Endpoint Features Avaya Aura release 6.2 includes the addition of the following features on SIP handsets that are also available on the H.323 versions. These powerful features differentiate




Avaya Aura from our competitors which fall short in providing key business telephony features.

Enhanced Call Forwarding – the user can use the SIP phone displays to set and monitor 6 different types of call forwarding including different numbers for internal and external incoming calls.

Enhanced Call Pickup Alerting – ability to change how the call pickup button alerts with no-ring, delayed ring, ring ping, etc.

Team Button – the popular team feature where calls can be answered for a team by choosing the caller from a display, calling the team by pressing the button, etc.

Group Paging – ability to have SIP phones receive group call Automatic Dial Button Programming – where SIP endpoint users can use SIP endpoint

displays to program the A/D button numbers and the labels for a customized user experience.

Contact Center Functionality – the array of buttons and features most used by contact centers including agent login, logout, aftercall work, aux work, etc.

Local Dial Plans – SM software now downloads the dialplans used for each location so users do not need to wait for dialling timeouts when dialling local extensions in multi-extension length environments. Calls are placed immediately when the dialled digits match the administered dialplan length. As with the market leading centralized Avaya Aura dialplan control, no settings files need be administered and no “send” key is ever needed when placing calls.

Per-Button Ring Control - SMGR can be used to administer the ringing behaviour for each line and bridged line appearance on SIP stations for ring-ping, delayed, abbreviated, etc. ringing.

Multiple Emergency Numbers SM 6.2 allows up to 10 emergency numbers to be administered per location. This allows compatibility with countries with more than one number, allows the integration of the Euro-wide 112 number to be employed along with specific country numbers, and provides adaptation for local regulations. Advanced SIP Conferencing Session Manager 6.2 supports the RFC 4579 style conferencing setup for voice, video and text conferences. Fully compatible with the conferencing capabilities provided by AAC, Meeting Exchange (MX), and CM, conferences are established using a conference “factory” and conference “focus” as per IETF standards. The endpoints do not need to know the conference URI. The conference URI’s are administered using SMGR for each user in a conference set and can be configured for voice, video, or text, with a list of secondary, tertiary and more backups for world-class reliability. This allows users to participate in conferences where user name displays, per-user muting, and more than 6 parties are possible. Advanced SIP Application Sequencing Session Manager now supports sequenced application filtering based on media type. Applications are sequenced based on the type of media requested and any combination of text, voice or video can be selected as shown in this screen shot of the SMGR administration options for each application in a sequence.




Media application sequencing greatly reduces the message traffic needed for sequencing (especially video and text applications), and simplifies application development. Advanced Trunking Flexibility and Features Avaya Aura 6.2 also provides unsurpassed interoperability with non-standards compliant third party equipment. Some H.323/SIP gateways use the non standard “SIP INFO” method to transmit DTMF digits to/from SIP networks. Avaya Aura 6.2 CM, Experience Portal, MX, Avaya Aura Conferencing, and Avaya Aura Messaging now support using the SIP INFO method to allow H.323 network equipment to use common voicemail, IVR, and end-end DTMF operation. This is a good example Avaya’s commitment to the support in interoperability with third party vendor equipment. Applications and users now on different media types will have the assurance of DTMF functionality, such as Modular Messaging, Meeting Exchange, Voice Portal or other customer provided trunk applications. Communication Manager provides further flexibility to Type of Network (TON) functionality to be applied to trunks connecting to 3rd party switches or applications, especially those connected via Q.Sig. Better functionality with such switches and applications provides leading interoperability for customers with unique scenarios.

Figure 2: Heterogeneous H.323 and SIP Network

SIP Connection Preservation The Avaya Aura SIP solution in release 6.2 can fully reconstruct stable calls that involve SIP trunks or SIP stations connected to endpoints on H.248 media gateways when the CM fails over to an administered survivable server or survivable remote (SC, SR), or vice versa. This matches the existing 6.0 capability for non-SIP endpoints. Note that




survivable SIP trunking is not yet available on the SR configurations, and we announce plans for this exciting feature to be delivered in the near future. SIP Call Preservation SIP call preservation goes a step farther than connection preservation to provide the fault tolerant behavior coveted by 24/7 heathcare and contact center architects. Call preservation goes beyond simple connection preservation as it allows the agent or user the ability to hold, unhold, transfer, conference, etc… an existing call after the failure occurs. For a contact center using Experience Portal, ICR, or just CM, it means calls queued for an agent before a failure will remain queued and will be offered to agents without being dropped after SM or network failures. Access Security Gateway Authentication Beginning with the 6.2 release, the following core Session Manager command line services logins are authenticated using Avaya’s Access Security Gateway (ASG) on production systems:

craft sroot init inads

Authentication File Download Support To match a capability currently available on CM 6.0.1, SM has adopted the use of the CLI command “loadpwd”. loadpwd requests the new authentication file from the installing technician, downloads it, validates its authenticity, decrypts it, parses the contents and stores the received data in the appropriate SM locations. SIP Contact Center Elite Agents CM and SM in support of contact center functionality now support SIP agent equipment. In addition to the traditional DCP and H.323 endpoints, agents may now employ SIP terminals for an end-end SIP contact center solution. Avaya Aura Contact Centre Call Information Enhancements Communication Manager in support of Avaya Aura Contact Center (AACC) will provide more context of call state via SIP. Call states such as Hold, Transfer or Conference will be provided to AACC enhancing its capabilities for call routing.

2.4. Interoperability Avaya Aura components connect to any IETF compliant SIP solution. Interoperability with Avaya Aura starts and ends with connectivity with Avaya Aura Session Manager at the core of any enterprise. The following products have been certified to interoperate and connect directly with Avaya Aura Session Manager and detailed design assurance and operation integrity confirmation is available with Avaya.




∗ Avaya Aura Communication Manager 5.1.2, 5.2, 5.2.1, 6.0, 6.0.1 and 6.2 – a new release of Avaya’s flagship IP telephony software that connects seamlessly to the Session Manager core. Specifically with CM feature server configurations, CM releases 5.2.1, 6.0, 6.0.1 and 6.2 are supported with SM 6.2.

∗ Modular Messaging 5.2 ∗ Avaya Aura Messaging 6.0, 6.1 and 6.2 - Avaya’s messaging platform

providing centralized voicemail and centralized messaging for the entire enterprise.

∗ Avaya 96XX Deskphone R2.6.3 – Avaya’s earlier endpoint line running 2.6 SIP firmware

∗ Avaya Aura 96X1 Deskphone R6.2 – Avaya’s flagship endpoint running the latest software, R6.2.

o SIP features (such as Team Button, Group Page, Enhanced Call Pickup Alerting, and Enhanced Call Pick Forwarding) will be available with 96x1 SIP 6.2 (planned for July 2012).

∗ Avaya 10X0 Series Video Conferencing Systems - Avaya video endpoints offer low cost and low bandwidth SIP-based solution to the enterprise users.

∗ Avaya Desktop Video Device with Avaya Flare Experience - Avaya Flare® Experience is a groundbreaking, next-generation workspace that delivers a uniquely compelling unified collaboration experience and makes making high definition video accessible in both cost and performance.

o CM 6.2 Service Pack 1 will support ADVD 1.1 ∗ one-X Communicator (both H.323 and SIP) in addition to Polycom H.323

interop o CM 6.2 Service Pack 1 will be required to support one-X Communicator

∗ Avaya G860 High Density Trunk Gateway R2 – the AudioCodes third party gateway capable of terminating multiple DS3 interfaces to integrate enterprise solutions with the PSTN.

∗ Avaya Aura CS 1000 R5.5, R6.X, R7.X – the CS 1000 communications server ∗ Avaya Voice Portal 5.1, and 5.2 ∗ Avaya Aura Experience Portal 6.2 – the newest innovation for voice, video and

data recognition and processing technology. ∗ Avaya Intelligent Customer Routing - Avaya’s next generation enterprise-wide

contact center innovation. ∗ Avaya Meeting Exchange 6.0 and 5.2 – The leading conferencing and

collaboration engine on the market today. ∗ Avaya Aura Conferencing R6.0 – The newest in a line of Avaya innovative

conferencing solutions that support voice and video downspeeding. ∗ Avaya Session Border Controller– Avaya’s addition to the Avaya solution that

includes the market leading Session Border Controllers for Enterprise and Advanced Enterprise from the Sipera acquisition.

∗ Avaya Aura Session Border Controller – SBC with ACME Packet technology. Communication Manager is also interoperable with IETF compliant SIP devices. The following products have been certified to interoperate and connect with Communication




Manager via Session Manager and detailed design assurance and operation integrity confirmation is also available with Avaya:

∗ Avaya Aura Session Manager 1.1, 5.2, 6.0, 6.1 and 6.2 ∗ Modular Messaging 5.2 and 5.1 – Avaya’s messaging platform providing

centralized voicemail and centralized messaging for the entire enterprise. ∗ Avaya 96XX Handsets R2.6 – Avaya’s flagship endpoint line running 2.6 SIP

firmware ∗ Avaya G860 High Density Trunk Gateway R2 – the AudioCodes third party

gateway capable of terminating multiple DS3 interfaces to integrate enterprise solutions with the PSTN.

∗ Avaya CS 1000 R5.5, R6.0, R7.X – the legacy CS1000 communications server ∗ Avaya Voice Portal 5.1, and 5.2 ∗ Avaya Aura Experience Portal 6.2 – the newest innovation for voice, video and

data recognition and processing technology. ∗ Avaya Intelligent Customer Routing - Avaya’s next generation enterprise-wide

contact center innovation. ∗ Avaya Meeting Exchange 6.0 and 5.2 – The leading conferencing and

collaboration engine on the market today. ∗ Avaya Session Border Controller– Avaya’s addition to the Avaya solution that

includes the market leading Session Border Controllers for Enterprise and Advanced Enterprise from the Sipera acquisition.

∗ Avaya Aura Session Border Controller – SBC with ACME Packet technology. ∗ 9600-Series IP Deskphones – For proper operation of the SIP Survivable

Remote, 9600-Series IP Deskphones should be running SIP Release 2.6.3 or later software.

Session Manager & Communication Manager Compatibility Matrix

SM CM 5.1 AE

CM 5.2 AE

CM 5.2.1 AE

CM 5.2.1 FS

CM 6.0 ES

CM 6.0 FS

CM 6.0.1 ES

CM 6.0.1 FS

CM 6.2 ES

CM 6.2 FS

SM 5.2 Y* Y Y Y** Y N Y N Y N SM 6.0 Y* Y Y Y** Y Y Y Y Y Y SM 6.1 Y* Y Y Y** Y Y Y Y Y Y SM 6.2 Y* Y Y Y** Y Y Y Y Y Y

*Limitations apply – please see the SM 1.1 release notes for details **CM 5.2.1 FS configurations are only supported in non-redundant configurations as with SM 5.2/CM 5.2.1 Session Manager & System Manager Compatibility Matrix




SMGR CM 5.X CM 6.0 CM 6.0.1 CM 6.2 SM 6.0 SM 6.1 SM 6.2 SMGR 5.2 Y N N N N N N SMGR 6.0 Y Y N N Y N N SMGR 6.1 Y Y Y N Y Y N SMGR 6.2 Y Y Y Y Y Y Y




3. SESSION MANAGER OFFER DESCRIPTION NOTE: All pricing contained herein are US Global List Price only. Readers are referred to regional product management for pricing specific to each region. NOTE: All pricing contained within, while accurate at the time of publication, should be considered as unofficial; Readers are directed to verify the accuracy of all prices cited by accessing SAP or ASD after the products become generally available. The components of the offer are the Session Manager software and hardware platform, and the System Manager software. Session Manager is delivered as software pre-installed on a fixed hardware platform (appliance model). System Manager is a software-only offer that is downloaded over the internet by customers and then loaded onto specific server hardware available from Avaya. The downloaded System Manager software includes the System Manager application software and an integrated Linux Red Hat OS with Avaya System Platform software for easy installation.

3.1. Session Manager Appliance Model Session Manager will be offered on a fixed hardware platform (the “appliance model”) to intentionally limit the configurations required to certify and maintain in the field. The server platform is either the Dell or HP platforms. SM is not offered on customer provided hardware. In the Session Manager appliance model, the steps for implementation are the following where “Avaya” means Avaya or Avaya certified business partners:

1. Customer orders the SM from Avaya and chooses the HP or Dell platforms 2. Avaya’s existing staging partner Avnet will install the Red Hat OS on the Dell or

HP platform server, download (from Avaya PLDS) and install the SM SW, and test the configuration as per the instructions on the Avaya support website.

3. Avnet will use the “Kickstart” DVD disk to lock Root and create Services accounts. The Services account passwords will be changed by the password change control system once the server is registered.

4. Customer will rack and stack servers – or alternatively contract with Avaya or an Avaya Business partner services.

5. Customer will configure the SM software – or alternatively contract with Avaya or an Avaya Business Partner services to configure and administer the SM software.

As described above, Session Manager software comes pre-installed on the hardware platform. System Manager 6.2 software is also available for download for entitled customers and Business Partners from the Avaya PLDS website. Session Manager and System Manager software are also optionally delivered using DVDs if ordered.




3.2. System Manager Software System Manager (SMGR) is offered as remotely downloadable software on the new Avaya servers and the software is available for download from the PLDS website. SMGR is not offered on customer-provided hardware.

3.3. Pricing and Material Codes Session Manager and System Manager are ordered for the core of an enterprise that may also contain Avaya Aura Editions and third party SIP equipment including third party PBXs. For more information see APPENDIX A. The following table shows the material codes used for ordering using the ASD design tool. The ASD tool will provide the appropriate codes based on the configuration questions answered as described in section 3.10.

MAT CODE DESCRIPTION MPG GPL

Avaya Aura Session Manager 6.2 Hardware 700501092 DL360G7 SERVER SESSION MANAGER IG $11,500 700501082 R610 SERVER SESSION MANAGER IG $11,500 700501473 AVAYA AURATM SESSION MGR R6.2 DVD A1 $50 700501476 AVAYA AURATM SMR6.2 RH KICKSTRT NEW DVD A1 $50 700501477 AVAYA AURATM SMR6.2 RH KICKSTRT UPG DVD A1 $50 700503264 AVAYA AURATM SESSION MGR 6.2 SP1 DVD A1 $50

Avaya Aura Session Manager 6.2 Software 264231 SM R6.X SIP CONNECTION LIC ENTITLE DU $0 264148 SM R6.X SIP CONNECTION LICENSE DU $150 264232 SM R6.X SIP CONNECTION LAB LICENSE DU $0 264680 SM5.X TO R6.X UPG CONNECTION LIC DU $30 229412 SM R6.X THIRD PARTY USER LICENSE DU $265 229416 SM R5.X TO R6.X UPG THIRD PARTY LIC DU $53




Session Manager Connection Licensing Avaya Aura Session Manager 6.2 is licensed using connection based licensing following the theme of the SIP session-based protocol. Connection based licensing was introduced with the SM 6.1 release and is based upon a session or connection (sometimes known as “trunk”) model that allows customers to purchase licenses based on the number of simultaneous SIP sessions required, rather than the number of users. The following diagram illustrates the various connections to Session Manager and their associated pricing. Note that both types of connection licensing - $0 and $150 connection licensing may be present in the same enterprise, and while the diagram below is constructed of single arrows between SIP entites and SMs, each SIP entity below will normally require multiple simultaneous connections so the licensing will be N * $150/$0 where “N” is the number of simultaneous connections required for each SIP entity to connect to the SM core.

Figure 3: SM Pricing Structure

264148 SM R6.X SIP CONNECTION LICENSE is required for a SIP connection to SM for one of the following reasons: 1. CM Standard Edition server needs connections to the core for the STD CM users controlled by it 2. CS 1000 server needs connections to the core for the Enhanced licensed users controlled by it. 3. A third party application (like Microsoft UM, or Cisco Meeting Place) requires connections to the core 4. A third party PBX (like Cisco UCM or Siemens 4000) needs connections to the core




5. A third party gateway – for example Multi-tech or Cisco - needs connections to the core 6. A third party SBC needs connections to the core In short, anytime a third party piece of equipment is required to connect to the Avaya Aura SIP core, this material code is needed for each simultaneous session needed. 264231 SM R6.X SIP CONNECTION LIC ENTITLE is required for a SIP connection to SM for one of the following reasons:

1. CM Enterprise Edition (EE) server needs connections to the core for the EE CM users controlled by it

2. CS 1000 server needs connections to the core for the Premium licensed users controlled by it

3. Avaya Aura SBC, ACME Packet SBC, Avaya SBCE or Avaya SBCAE are used to connect the SM core to a non-enterprise network like a service provider or business partner or outsourcer network

4. An Avaya application connects to the SIP core like Modular Messaging Avaya Aura Messaging, Voice Portal, Meeting Exchange, etc.

5. Avaya Gateways including the G860, SR/AG2330, SR/AG4134, or the certified AudioCodes gateways (Mediant 3000, Mediant 2000, and Mediant 1000) purchasable from Avaya using Avaya material codes that are available to both direct and indirect channels

6. The Avaya BCM – the legacy small PBX (when the appropriate SIP connection or session licensing is purchased on the BCM)

7. The Avaya B5800 branch solution (when the appropriate SIP connection licensing is purchased on the B5800) with either centralized or distributed configurations

8. IP Office connects to the core (when the appropriate SIP connection licensing is purchased on the IP Office)

9. Avaya Integral equipment connects to the core (when the appropriate SIP connection licensing is purchased on the Integral)

10. CS2100 SE13 needs connections to the core (when the appropriate SIP connection licensing is purchased for the CS2100

This material code is needed for each simultaneous session required. 264232 SM R6.X SIP CONNECTION LAB LICENSE is used when the ASD is run to configure a lab configuration. Note these licenses expire after 120 days. 264680 SM5.X TO R6.X UPG CONNECTION LIC is added to an order when ASD is used to upgrade an SM 5.X to SM 6.1 software for user licenses the customer paid for with 5.X (229061 – SM 5.X USER LICENSE - $20). The user licenses used in SM 5.X will be converted to connection licenses at a 5:1 ratio. This 5:1 conversion must be done manually after the configurator is run. 264679 SM R5.X TO R6.X UPG CONN LIC ENTITLE is used when ASD is used to upgrade an SM 5.X to SM 6.1 software for user licenses the customer had as entitlements (these were provided at no charge in 5.X and thus will be provided at no




charge in the upgrade) with 5.X (229060 – SM R5.X USER LICENSE w/CMEE - $0). The user licenses used in SM 5.X will be converted to connection licenses at a 5:1 ratio. The 5:1 conversion must be done manually after the configurator is run. Entitlements SM connection licenses will be an entitlement for the following:

1. CM Enterprise Edition users. For every 5 CM Enterprise Edition users ordered or upgraded a single SM connection license will be included by ASD.

2. CS1000 Premium users. For every 5 CS1000 Premium users ordered or upgraded a single SM connection license will be entitled.

3. CM Elite Contact Center (CC) agent licenses. For each Elite CC Agent license purchased an SM connection license will be included. If more SM connection licenses are required they must be purchased at the $150 price.

4. Avaya Aura Contact Center (AACC) agent licenses. For each AACC agent license purchased an SM license will be included. If more SM connection licenses are required, they must be purchased at the $150 price.

5. Avaya Aura SBC, Avaya SBCE, and Avaya SBCAE: For every SBC session license ordered an SM connection license will be included.

When ASD is used to configure either CM (Enterprise license) or CS1000 (Premium license) SM connectivity with the Premium or Enterprise licenses, the following license will appear on the order. ASD will configure an SM connection license for use of the users controlled by the connected CM or CS1000 with the code shown below. Additional SM connection licenses can also be ordered for CS1000 and CM in addition to the 1:5 ASD-provided ratio as needed but will be subject to the $150 charge.

264231 SM R6.X SIP CONNECTION LIC ENTITLE When ASD is used to configure either CM (Standard license) or CS1000 (Enhanced license) SM connectivity, the following license will be used for connectivity of the CM/CS1000 to the core SMs.

264148 SM R6.X SIP CONNECTION LICENSE If an enterprise wishes to use the application sequencing capabilities of Session Manager for users registered to Session Manager but have not purchased an Avaya Aura Communication Manager license, additional licenses for these kinds of users must be purchased using ASD. This highly uncommon; in this scenario the customer will have SIP phones registered directly to the Session Manager but will not have an Avaya Aura Communication Manager license for that SIP user. The following is the license that must be purchased for these users (see section 3.10 for ASD details):

229412 SM R6.X THIRD PARTY USER LICENSE

Session Manager Laboratory Trials




To encourage early adoption and display the power of application sequencing, laboratory systems for evaluation may be ordered via ASD with $0 Session Manager software licenses. These licenses expire 120 days after purchase (not installation).These laboratory systems may not be used in any type of production environment, but may be upgraded for production use by purchasing the production software licenses. See section 3.10 for ASD details.

3.4. Upgrades There is a software license charge required to upgrade Session Manager from SM 1.1 or SM 5.2 to SM 6.2. The ASD configurator may be used to design and create an upgrade order. Upgrades to SM 6.2 from SM 6.0 or SM 6.1 require no license charge and the 6.2 software is available for these customers via PLDS at no charge. To upgrade an existing SM 1.1/5.2 system to 6.2, simply place the order for an upgrade using ASD and the software may be downloaded and installed on the existing 1.1/5.2 systems in service. Upgrades may be downloaded and installed by customers.

3.5. Implementation Services Avaya will provide customers with a complete set of implementation services for Session Manager and System Manager. These services are performed by a qualified team of Avaya personnel, including an Advanced Solution Architect. Professional Services include Long Distance (Toll Charges) Savings Design, Trunk Aggregation Savings Design, 3rd Party and Legacy Support Cost Savings Design, as well as Business User Application Segmentation Design. To request implementation pricing and a statement of work, complete the ASM Data Gathering Form located at the link below and attach it to your Siebel resource request for non-packaged implementation services, or, if you are an Avaya Business Partner, to your ORS request for implementation pricing: SM Job Aid Link for Avaya Account Teams: https://enterpriseportal.avaya.com/ptlWeb/gs/products/P0533/JobAidsTools SM Job Aid Link for Avaya Business Partners: https://enterpriseportal.avaya.com/ptlWeb/bp/products/P0533/JobAidsTools

3.6. Availability A global rollout of CM and SM is planned with availability in all countries worldwide where Communication Manager is currently sold.

North America Date TBD

EMEA Date TBD

APAC / Japan Date TBD

CALA Date TBD




Product availability dates may differ for other product components described in this document. Please refer to the corresponding product definition documents for more detailed information.

3.7. Session Manager Required Hardware The Session Manager R6.2 software is supported on the HP DL360G7, Dell R610, S8800 (IBM 3550m2) and the S8510 (Dell 1950) servers. Existing SM 1.1 customer deployments on the S8510 may be upgraded to SM 6.2 by downloading the SM 6.2 software, removing the TLS hardware, and upgrading to release 6.2 using the instructions found in section 3.4. Customers with S8800 hardware on SM 5.2 systems also need only to download the new software to upgrade; no server hardware changes are required. Avaya Business Partner and Professional Services are available for upgrade support. Session Manager ships from the factory on the HP DL360G7, a 1-U high server with 2 – E5620 processor cores and 12 GBytes of memory as shown below.

Component Description

Processor Dual Quad Core Intel Xeon Processors 5620 – 2.4GHz

Memory 12GByte DDR3

Hard Disk Drive 2 – 146GB SATA (RAID 1)

NIC 4 NICs (10/100/1000)

Slots 2 – PCI-e GEN2 slots

Power Supply Redundant Power Supplies

USB Ports 4 USB Ports

Optical Drives DVD +/-R/W

RoHS Compliant Yes

Chassis 30.4” (77.2 cm) D x 16.7” (42.6 cm) W x 1.67” (4.26 cm) H

Alternatively, customers can order SM running on the Dell R610 hardware, which is not the default configuration, but ASD can be used to order the Dell servers if the customer requires.


Processor Dual Quad Core Intel Xeon




Processors 5620 – 2.4GHz

Memory 12 GByte DDR3


NIC 4 NICs (10/100/1000)

Slots standard

Power Supply Redundant Power Supplies (opt)



RoHS Compliant Yes


Upgrades for existing SM 1.1 and SM 5.2 servers will need to remove the SM100 from the chassis to complete the upgrade to SM 6.2. It is important to note that the Avaya System Manager is still required to administer SM; this requires a separate server to host the System Manager software.

3.8. Required Software SM ships from the factory with all the software pre-installed an loaded and includes the Red Hat Linux OS and the SM application software. Proper operation of the Session Manager requires System Manager software running on a separate server.

3.9. Required System Manager Platform System Manager is a software-only solution also running on the HP or Dell servers. Although technically the System Manager will run in a virtual OS environment, it is not offered as such and requires dedicated hardware to run in this release. ASD (see section 3.10) has an option for customers and Business Partners to order the hardware platform for System Manager in either simplex or duplex configurations.




3.10. Ordering Process with ASD The CM Avaya Solution Designer (ASD) configurator will be used to configure and order Session Manager (SM) and System Manager software. ASD will configure the SM from a system point of view – treating SM as an enterprise-wide element for a customer. The single ASD screen used to configure the 6.2 SM is shown below:

Figure 4: SM ASD Configuration

There are no new changes to the ASD configurator for Session Manager for the 6.2 release. The only change is how ASD is used for the Avaya SBCE and Avaya SBCAE session border controllers. Instead of placing the number of SM connections required in the “THIRD PARTY PBX/APPS/SBC” box, the number of connections should be entered in the “AVAYA APPS/SBC” field since the Avaya ABCE and Avaya SBCAE (formerly Sipera) SBCs are now Avaya equipment.

4. COMMUNICATION MANAGER OFFER DESCRIPTION NOTE: All pricing contained herein are US Global List Price only. Readers are referred to regional product management for pricing specific to each region. NOTE: All pricing contained within, while accurate at the time of publication, should be considered as unofficial; Readers are directed to verify the accuracy of all prices cited by accessing SAP or ASD after the products become generally available. The components of the offer are the Communication Manager software and hardware platform. Communication Manager is delivered as software pre-installed on a fixed hardware platform (appliance model).




4.1. Pricing and Material Codes In August 2009, the Communication Manager material code description was changed to Avaya Aura® Edition material codes. Avaya’s 9-tier structure was also simplified to a 3-tier structure. This is reflected in the following sections. Immediately below are the new Software DVD material codes for CM 6.2 Software DVD

MAT CODE DESCRIPTION MPG Global List Price

Avaya Aura® Communication Manager 6.2 Software Media DVDs 700501472 AVAYA AURA(r) R6.2 SFTW DVD A1 $50 700501399 AVAYA AURA(r) SYSTEM PLATFORM 6.2 DVD A1 $50

4.2. Supported Servers Only the following servers are supported by CM 6.0.1: HP DL360G7: The HP DL360G7 was introduced in November 2011. Avaya is leveraging this life cycle event to move away from proprietary hardware designs and towards the use of Commercial Off-The-Shelf (COTS) server platforms. The introduction of this strategy will allow our customers to take advantage of the benefits of next generation servers based on the continued development of Intel® processors.


Processor Dual Quad Core Intel Xeon Processors 5620 – 2.4GHz (simplex) or Dual Six Core Intel Xeon Processors 5670 – 2.93GHz (duplex)

Memory 12 Gbyte DDR3


NIC 4 NICs (10/100/1000)

Slots 2 – PCI-e GEN2 slots




RoHS Compliant Yes





Dell R610: The Dell R610 was introduced in November 2011.


Processor Dual Quad Core Intel Xeon Processors 5620 – 2.4GHz (simplex) or Dual Six Core Intel Xeon Processors 5670 – 2.93GHz (duplex)

Memory 12 Gbyte DDR3


NIC 4 NICs (10/100/1000)

Slots standard




RoHS Compliant Yes


Application Server Type Material Code List Price (USD) Communication Manager simplex (single server provided)

HP DL360G7 263764 $8,800

Dell R610 263760 $8,800

Communication Manager duplex (two servers provided)

HP DL360G7 263765 $21,500

Dell R610 263761 $21,500

S8300D: The Avaya S8300D Server was introduced in August 2009. The S8300D is the latest evolution in Avaya’s series of S8300 embedded servers, and provides additional processing power, memory, and hard disk capacity in support of System Platform R6 as well as Communication Manager R6 and its associated templates. S8300D software compatibilities:

• Supports System Platform R6 • Supports Communication Manager R6 and its associated templates




For more information see the S8300D Server Channel Announcement at: http://portal.avaya.com/ptlWeb/products/P0068/AllCollateral (under Launch Announcements). S8510: The Avaya S8510 server went End of Sale on February 15, 2010. A hardware migration kit is available to support migration to Communication Manager R6.2. This migration kit will be available while our vendor continues to supply the memory. Upgrades for the S8510 may require a different procedure than upgrades for the S8800 and will be described in release notes.

Material Code Description NPL 259270 S8510 Migration Kit $1600

S8800: The Avaya S8800 series common server was introduced in the fall of 2009. The S8800 End of Sale on 6 June 2011was announced 25 October 2010. The S8800 will continue to support CM 6.2 as a new or upgrade platform. Refer to End of Sale reference at https://enterpriseportal.avaya.com/ptlWeb/gs/products/P0584/EndSaleNotices The Avaya S8800 Server is sold in a variety of configurations to suit the specific processor, hard drive and memory needs of each application and a representative sampling of these configuration parameters are shown in the table below. Several new configurations are being introduced to support Avaya Aura® 6.2 applications. Software duplication is the available offer; hardware duplication is not offered. Note: The server construct used with Communication Manager 5.2.1 is different than the server construct used for Communication Manager 6.x. The recommended configuration for Communication Manager 6.2 includes 12GB of memory, an additional HDD with the HDDs configured as RAID 5. A hardware migration kit is available to upgrade the S8800 Server construct used with Communication Manager R.5.2.1 to support Communication Manager 6.2.

Material Code Description NPL 232320 S8800 Migration Kit $1600

For more information on the S8800, including detailed server configurations and software release compatibilities for each application see:

• The Product Transition Notice or other documentation for each adopting application on support.avaya.com as they become generally available

http://portal.avaya.com/ptlWeb/products/P0068/AllCollateral�

https://enterpriseportal.avaya.com/ptlWeb/gs/products/P0584/EndSaleNotices�




S8730: The S8730 server went End of Sale on January 19, 2010 and the last supported release is Communication Manager 5.2.1. Migration to Communication Manager R6 is not supported on the S8730.

4.3. Communication Manager License Functions CM defines license functions or operations as NEW or ADDITIONS, TRANSFER, UPLIFT, UPGRADE, MOVE, PARKING and REDUCTION. With the implementation of PLDS in CM 6.x, license management has been simplified requiring fewer steps. Review the following sections as required for guidance in the license functions

NEW or ADD – New is the purchasing of user licensing for a new CM – Add is the expansion of a deployed CM with incremental user licensing

*Note: US NPL for the following two codes is different than GPL

• 225151 AVAYA AURATM STD ED R6 1001+ NEW LIC = $180 • 225154 AVAYA AURATM ENT ED R6 1001+ NEW LIC = $265

TRANSFERS

– Mobility of licenses between customer CM’s within the same software release and edition (Like for Like)

SAP CODE DESCRIPTION MPG Global List PriceAvaya Aura™ Standard Edition NEW License225149 AVAYA AURATM STD ED R6 1-100 NEW LIC DU 240$ 225150 AVAYA AURATM STD ED R6 101-1000 NEW LIC DU 210$ 225151 AVAYA AURATM STD ED R6 1001+ NEW LIC DU 205$ Avaya Aura™ Enterprise Edition NEW License225152 AVAYA AURATM ENT ED R6 1-100 NEW LIC DU 320$ 225153 AVAYA AURATM ENT ED R6 101-1000 NEW LIC DU 290$ 225154 AVAYA AURATM ENT ED R6 1001+ NEW LIC DU 285$

SAP CODE DESCRIPTION MPG Global List PriceAvaya Aura™ Standard Edition ADD License225167 AVAYA AURATM STD ED R6 1-100 ADD LIC DU 240$ 225168 AVAYA AURATM STD ED R6 101-1000 ADD LIC DU 210$ 225169 AVAYA AURATM STD ED R6 1001+ ADD LIC DU 205$ Avaya Aura™ Enterprise Edition ADD License225170 AVAYA AURATM ENT ED R6 1-100 ADD LIC DU 320$ 225171 AVAYA AURATM ENT ED R6 101-1000 ADD LIC DU 290$ 225172 AVAYA AURATM ENT ED R6 1001+ ADD LIC DU 285$

The following license material codes are used for aftermarket additions to existing Communication Manager 6.x systems.




For CM 6.x, Transfers are managed via the Global Licensing Policy by the use of the online License Move Request Form found at the link below https://enterpriseportal.avaya.com/ptlWeb/bp/so/CS2010105203323127038 Global Licensing Policy is found at https://support.avaya.com/css/appmanager/css/support?_nfpb=true&_pageLabel=WNContent_Private&contentid=C2009223142629795043#Global%20Licensing%20Portability%20%28Avaya%20Products%29 UPLIFT

– Change of software level from Standard Edition to Enterprise Edition New uplift codes when uplifting from the Avaya Aura® Standard Edition to the Avaya Aura® Enterprise Edition.

UPGRADE and MOVE

– Upgrade is the updating of CM software release and licensing to current – Moves are inclusive of both an Upgrade and a Transfer of the licenses

Avaya shifted to the Per User Model with the launch of Avaya Communication Manager (CM) 3.0. With R6.x we are simplifying the upgrade structure by moving to one transactional upgrade path and at a single tier. We no longer have the multi upgrade/ single upgrade distinction.

PARKING

– Placement of unused licensing on a non-operational or virtual server CM 6.x licenses cannot be parked as Avaya Policy requires these licenses to be covered under an Avaya Maintenance Contract. There is no exception to this policy.

SAP CODE DESCRIPTION MPG Global List Price245456 AVAYA AURATM R6 EE 1-100 UPLIFT LIC DU 80$ 225141 AVAYA AURATM R6 EE 101-1000UPLFT LIC DU 80$ 245457 AVAYA AURATM R6 EE 1001+ UPLIFT LIC DU 80$

SAP CODE DESCRIPTION MPG Global List PriceAvaya Aura™ Standard Edition Upgrade/Move229582 AVAYA AURATM R6 STD ED UPG LIC DU 42$ 229586 AVAYA AURATM R6 STD ED MOVE LIC DU 42$ Avaya Aura™ Enterprise Edition Upgrade/Move229583 AVAYA AURATM R6 ENT ED UPG LIC DU 58$ 229587 AVAYA AURATM R6 ENT ED MOVE LIC DU 58$

https://enterpriseportal.avaya.com/ptlWeb/bp/so/CS2010105203323127038�

https://support.avaya.com/css/appmanager/css/support?_nfpb=true&_pageLabel=WNContent_Private&contentid=C2009223142629795043#Global%20Licensing%20Portability%20%28Avaya%20Products%29�






REDUCTION – Removal of unused licenses

For CM 6.x, Reductions are managed via the Global Licensing Policy by the use of the online License Move Request Form found at the link below https://enterpriseportal.avaya.com/ptlWeb/bp/so/CS2010105203323127038

4.4. Avaya Aura® for Survivable Core and Survivable Remote With R6.0 the offer changes for purchasing Avaya Aura for Survivable Core (CM5’s ESS) and Avaya Aura® for Survivable Remote (CM5’s LSP). Previously, they were sold based on the server or gateway size. This did not scale well for small sites when viewed competitively. R6.x uses a simple, per-user price when in use with Avaya Aura® Standard Edition. Similar to R5.0, both Avaya Aura® for Survivable Core and Avaya Aura® for Survivable Remote are available for no additional charge with Avaya Aura® Enterprise Edition. NOTE: The one free survivable server is no longer included with Avaya Aura® Standard Edition R6.x. Customers with existing ESS and LSP server licenses on pre-CM 6.x Standard Edition systems will not be charged to use these servers on a CM 6.0.1 system. However, adding additional Survivable Core or Survivable Remote servers at the time of upgrade or later will be charged the per-user fee per below.

4.5. Avaya Aura® CM Bundles for the Mid Market Solutions Eight (8) Communication Manager Bundles were offered for mid-market solutions. These have not changed from the 5.x releases. These software bundles are priced very competitively and are available on the S8300 platform for initial front market purchase. Note, Release 6.0.1 is not offered on the S8400 server platform. The Enterprise Edition S8300 Communication Manager bundle also includes Communication Manager Messaging software licenses at no additional charge. Communication Manager Messaging is no longer free of charge with Avaya Aura® Standard Edition. Note: these bundles are available to the front market only.

SAP CODE DESCRIPTION MPG Global List Price248250 R6 STD ED SURVIVE REMOTE USER SW LIC DU 25$ 248251 R6 STD ED SURVIVE CORE USER SW LIC DU 25$

https://enterpriseportal.avaya.com/ptlWeb/bp/so/CS2010105203323127038�




For new S8300D system purchase, the following Avaya Aura® Edition 6.X software bundles are available.

NOTE: Only one bundle can appear on a new system purchase order and these bundles cannot be used for aftermarket addition and upgrades. *NOTE: Bundle Pricing shown above is for the US market only.

4.6. Analog Station Licenses These codes are used to purchase new analog station licenses, upgrade from R5 Analog License to R6 Analog License, and also to uplift Analog licenses to either Avaya Aura® Standard or Enterprise Edition.

• Analog station licenses are to be used for analog stations only (analog deskphones, fax machines, etc).

• If at a later date, the station is to be used as a digital or IP station, the Analog station license must be uplifted to either an Avaya Aura® Standard or Enterprise Edition license whichever is applicable to the specific CM system.

• A minimum of one (1) Avaya Aura® R6 Universal license must be purchased for each system (either Standard or Enterprise Edition).

• The upgrade codes listed below are only for upgrades from current R5 Analog Licenses and are not to be used to downgrade an existing Universal license.

SAP CODE DESCRIPTION MPG US Market*Avaya Aura™ Standard Edition for S8300 stand alone sales225132 AVAYA AURATM STD ED R6 50 USER BUNDLE DU 5,000$ 225133 AVAYA AURATM STD ED R6 100 USER BUNDLE DU 10,000$ 225134 AVAYA AURATM STD ED R6 150 USER BUNDLE DU 15,000$ 225135 AVAYA AURATM STD ED R6 200 USER BUNDLE DU 20,000$ Avaya Aura™ Enterprise Edition for S8300 stand alone sales225136 AVAYA AURATM ENT ED R6 50 USER BUNDLE DU 8,000$ 225137 AVAYA AURATM ENT ED R6 100 USER BUNDLE DU 16,000$ 225138 AVAYA AURATM ENT ED R6 150 USER BUNDLE DU 24,000$ 225139 AVAYA AURATM ENT ED R6 200 USER BUNDLE DU 32,000$

SAP CODE DESCRIPTION MPG Global List Price225185 AVAYA AURATM R6 ANALOG NEW LIC DU 40.00$ 225186 AVAYA AURATM R6 ANALOG UPG LIC DU 8.00$ 225187 AVAYA AURATM R6 ANALOG MOVE LIC DU 8.00$ Uplift from Analog to Avaya Aura ™ Standard Edition225188 AVAYA AURATM STD ED ANLG TO UNIV 1-100SW LIC DU 200.00$ 225189 AVAYA AURATM STD ED ANLG UNIV 101-1000SW LIC DU 170.00$ 225190 AVAYA AURATM STD ED ANLG TO UNIV 1001+SW LIC DU 165.00$ Uplift from Analog to Avaya Aura ™ Enterprise Edition225191 AVAYA AURATM ENT ED ANLG TO UNIV 1-100SW LIC DU 280.00$ 225192 AVAYA AURATM ENT ED ANLG UNIV 101-1000SW LIC DU 250.00$ 225193 AVAYA AURATM ENT ED ANLG TO UNIV 1001+SW LIC DU 245.00$




4.7. Utility Services standalone In Communication Manager 6.2, Utility Services is available as a standalone server to support CM duplex deployments. Utility Services is deployed on the CM simplex server. It is ordered via the ASD tool. The following material code will be required to enable the Utility Services

Material Code Description NPL

266453 AVAYA AURATM R6.2 UTILITY SVCS LIC

$0

4.8. Upgrades Overview In order to prepare customer translations and other data sets to be used by Communication Manager 6.2, upgrades to Communication Manager 6.2 from previous releases to 4.0.5 require the installation of Communication Manager 5.2.1 and then a pre-upgrade patch (2 step upgrade). This is required because Communication Manager 6.x uses a different licensing architecture (PLDS and WebLM) than the RFA licensing used previously, and because it runs on Avaya Aura System Platform instead of directly on the server hardware. This new licensing architecture requires more consideration during the upgrade preparation to ensure the appropriate steps are followed. NOTE: For upgrades from a release prior to release 4.0.5, where a 2 step upgrade is required, Avaya will provide the customer with a no-cost license upgrade to Communication Manager 5.2.1 from whatever release they are on, and then will charge normally for the upgrade from Communication Manager 5.2.1 to Communication Manager 6.x. Because Communication Manager has uniform upgrade pricing (as previously announced), this does not affect the ultimate upgrade price charged to the customer. This has now been combined into a single ASD design, with both the upgrade to CM 5.2.1 and CM6.2 codes. NOTE: The manual application of UPPCM or SS+U is NOT required for the upgrade to CM 5.2.1. This is automated in current releases of Avaya Solution Designer (ASD). NOTE: CM 5.2.1 is End Of Sale on March 5, 2012. ASD will provide the CM 5.2.1 quote components automatically regardless of the EOS. The potential scenarios for upgrading to CM 6.2 are

a. Upgrades from Communication Manager Release 5.x b. Upgrades from Communication Manager Release 4.x c. Upgrades from releases Communication Manager Release 3.x and prior with Data

Preservation




d. Upgrades from releases Communication Manager Release 3.x and prior without Data Preservation

Please refer to the following sections for guiding thorough the required steps a. Upgrades from Communication Manager Release 5.x Note: An ASD design is not necessary to upgrade to CM 5.2.1. An ASD design for CM 6.2 is all that is required.

1. Install the PCN upgrade to CM 5.2.1 2. Apply the pre-upgrade patch for CM release 5.2.1 3. Use ASD to configure a CM 6.2 design as usual. 4. Install CM 6.2

b. Upgrades from Communication Manager Release 4.x Note: This process is not applicable to CM Release 4.0.2 (JITC). An ASD design is not necessary to upgrade to CM 4.0.5.

1. Install the PCN upgrade to CM 4.0.5 2. Apply the pre-upgrade patch for CM release 4.0.5 3. Use ASD to configure a CM 6.2 design as usual. 4. Install CM 6.2

c. Upgrades from releases Communication Manager Release 3.x and prior with Data Preservation Note: In this scenario, the customer must perform a 2 step upgrade (i.e. upgrade to CM 5.2.1 and upgrade to CM6.2). ASD has recently been enhanced to allow both the CM 5.2.1 and CM 6.2 upgrade on the same design. ASD must be used to generate the correct single design using the following steps:

1) Use ASD to create the design with CM6.2 as the target, which will include both the CM 5.2.1 and CM6 upgrade codes automatically. Note: The ASD design will generate the necessary UPPCM free upgrade codes automatically so the customer is not charged for the CM 5.2.1 upgrade. Do NOT select the UPPCM option in ASD unless the customer has a valid and active UPPCM contract. Do NOT select the SS+U option in ASD unless the customer has a valid and active SS+U contract. Implementation charges, however, may apply. a. ASD will ensure only 1 set of SSI/SA codes when the target is CM6.

2) Install CM 5.2.1 and the CM 5.2.1 license file, and then the pre-upgrade patch 3) Install CM 6.2

NOTE: When doing the CM 5.2.1 install, it is not necessary to actually install CM 5.2.1 on any ESS or LSP servers. This will save considerable time. These survivable servers will be installed with CM 6.2 just before the main server is upgraded to CM 6.2. However, if the customer will remain on CM 5.2.1 for any length of time and needs ESS or LSP survivability during this time, you will need to install CM 5.2.1 on each of them. d. Upgrades from releases Communication Manager Release 3.x and prior without Data Preservation This manual migration is not supported nor recommended as Customer data WILL be lost and provides little value. This process is provided for informational purposes only for Avaya Business Partners as requested.

1) Use ASD to create the design with CM6 as the target, which will include both the CM 5.2.1 and CM 6.2 upgrade codes automatically. Note: The ASD design will generate the necessary UPPCM free upgrade codes so the customer is not charged for the CM 5.2.1 upgrade. Do NOT select the UPPCM option in ASD unless the customer has a valid and active UPPCM contract. Implementation charges, however, may apply. a. ASD will ensure only 1 set of SSI/SA codes when the target is CM6.2.




b. If you are migrating from R9 and earlier, CM 5.2.1 codes are still required to upgrade the licenses which need to be upgraded to CM5 licenses before converting them from RFA to PLDS. If you are migrating from R10 to CM3, this step is not required since we support direct conversion from any release to PLDS..

2) Capture or record non-translational data. See note *1 below 3) Backup translations (or use TMT) 4) Install new software CM 6.2 5) Restore translations 6) Manually migrate license and user info 7) Manually configure system

*note 1 – following data is not included in the translations files

• CMM translations and message store • Web access masks and logins and passwords • Custom user data such as banners, messages etc. • SNMP alarming, IP address, and associated admin • Administration for scheduled cron jobs such as backup • Authentication, License files and feature bits including customer added users and

custom PAM settings that may have been modified via Root permissions • LDAP Settings/Configuration if SSH is enabled and other customizations

For all upgrades, other licensing must be considered. Ie Call Center Elite

4.9. Upgrading to CC 6.x – Software

Upgrades to Avaya Aura Communication Manager 6.x and CC Elite 6.x require a two step process when the FROM release is 4.0 or earlier. See the above CM Upgrade section for specific detailed steps. Two-Step Upgrade Generalizations • SAP Order for the ACM 5.2.1 upgrade must be applied to RFA and installed on the system to be

upgraded • Pre-upgrade patch must be applied when system is at ACM 5.2.1 or 4.0.5 • Implementation pricing is not covered • Hardware costs are not part of this process • ASD is fully capable of designing ACM 5.2.1 upgrades without issues • Call Center R9 and earlier requires special handling contact channel team or product management

Find your scenario here and follow the steps. Situation 1: Upgrading From ACM5.2.1 or 4.0.5 • No special process required • Design, license and upgrade as needed • Need to install pre-upgrade patch

Situation 1a: Upgrading From CM5.x (any version other than 5.2.1) • Install PCN to get customer to 5.2.1 and install pre-upgrade patch • ASD normal upgrade design to 6.x • Install CM6.x




Situation 1b: Upgrading From CM4.x (except 4.0.2) • Install PCN to get customer to 4.0.5 and install pre-upgrade patch • ASD normal upgrade design to 6.x • Install CM6.x

Situation 2a: Upgrade from all releases of CM 3.x and prior, AND customer • If any release Call Center is on CM1 or CM 2

o Tell ASD None for CC and None for Target, do not add agents at this point. o Remove code 212487 from output design, this prevents a Basic Call Center

• If Call Center is at CM 3 or CM 4 o Tell ASD existing CC R3 for CC R3 or earlier, tell ASD CC R4 for R4 o Do not upgrade Call Center, do not add any agents

• Process design through distribution, SAP, install upgrade, upgrade patches and RFA license • Design ACM 6 Upgrade starting with an ACM 5.2.1 starting point

o From CC 3 and earlier, upgrade to CC 6 from CC 3, ok to add agents here o From CC 4, upgrade to CC 6 (or keep CC R4), ok to add agents here.

• Install CM 6 Situation 2b: Upgrade from CM 1.x through CM 4.x • Upgrade Call Center to R5, customer may opt to keep CC R4 with CM6 • Process design through distribution, SAP, install upgrade, upgrade patches and RFA license • Design CM 6 and CC 6 Upgrade starting with an CM 5.2.1 and CC 5 as a starting point • Install CM 6

Situation 3a: Upgrade from pre CM 1.x • If Call Center is used and on Definity R9 or earlier (pre-RFA) or lower, special conditions apply

o Contact product management via channel team • If any Release Call Center is on Definity R10

o Tell ASD None for CC and None for Target, do not add agents here o Remove code 212847 from output design o Upgrade from CC R3 to CC R6 in CM 6 upgrade

4.10. Licensing for Demos, Labs and Trials

• Beta Trials must go through the Beta Trials Program Manager for the specific release; contact your Avaya Representative else the Program Manager or Product Manager

• For CM and CC Elite, Customer lab systems must be ordered and purchased as per

standard processes; any discounting must go through the Deals Desk

• For CM and CC Elite, Avaya owned Demo equipment on customer premise, or Business Partner Demo equipment must order the 120 day trial license (m/c 245460) or contact the Avaya Help Desk to request a 30 day temporary license

• Temporary License Requests: • Temporary/Emergency licenses up to 30 days do not require product

management or product operations approval. Please call the Helpdesk and have it flagged as “Business Critical”.




• Temporary licenses between 31-90 days with supporting orders such as upgrades, new, moves or orders with errors/corrections do NOT require product management or product operations approval. Please call the Helpdesk (Tier 3) to request a temporary license.

• Temporary licenses between 31-90 days without supporting orders will require review by product manager/product operations and will require business justification (i.e. business case); Call Helpdesk (Tier 3) first, open case and have escalated to product operations /product management.

Avaya Helpdesk

For the USA, please call 1-866-AVAYA IT (+1-866-282-9248) or 303-354-8999 EMEA users should call +44 1483 309800 Canada and CALA users should call +1 720 444 0130 APAC users should call +65 6872 8700 Germany users should call +49 69 7505 1234

4.11. ASD Changes The ASD design tool is modified in two major areas for CM 6.2 designs:

1) Added a choice of System Platform solution templates 2) Changed the licensing of Survivable Core and Survivable Remote servers

System Platform Solution Template Choice The ASD System screen contains three entries for CM 6.2 main server templates as shown below.




Figure 5: Template Choice The three choices map to the following three templates (the other two are Survivable Remotes and the Utility Services Standalone):




Survivable Core and Survivable Remote Screens Choose the Survivable Core option on the Location form. If chosen on Standard Edition there will be a pre-user license code in a quantity equal to the number of CM stations purchased.

Figure 6: Survivable Core and Survivable Remote




Choose the Survivable Remote option on the following form. If chosen on Standard Edition there will be a pre-user license code in a quantity equal to the number of CM stations at the location, not the entire enterprise. Selection of the Survivable Remote option will automatically include the Session Manager instances needed for SIP operation for the Survivable Remote configuration. Note it is required to have core Session Managers installed for proper Survivable Remote SIP operation.

Figure 7: Survivable Remote Option




5. SERVICEABILITY For the purpose of this document, the Service process starts with customer acceptance of the product. This occurs after the Provisioning process ends or, for customer-installed equipment, when the equipment arrives on site. The Service Process ends when the product is taken out of service or when Avaya no longer supports it.

5.1. Software Support and Hardware Maintenance In traditional voice systems, hardware, operating system and features were tightly bonded – an architecture that resulted in maintenance offers that bundled hardware and software support into a single combined service. With the advent of IP Telephony and the rapid migration toward open, “software centric” platforms, customers increasingly want flexible and straightforward maintenance offers where they can separately choose their desired level of software and hardware support. In Avaya’s support structure, software maintenance is available in two offers: Software Support plus Upgrades (SS+U) and Software Support (SS). Both give customers 24x7 remote technical support for major problems, as well as easy access to all minor releases, extensive on-line tools and service packs. Software Support plus Upgrades provides the same entitlements as Software Support, as well as, access to major releases as they become available. For customers who want to keep their applications on the cutting edge, Software Support plus Upgrades ensures immediate access to major releases while also delivering locked-in TCO savings. Software Support plus Upgrades and Software Support will begin billing on Day 1 for all applications and for all channels. Time & Material will no longer be available for software support. For hardware, there are three simplified offers: Remote Hardware Maintenance, Remote Hardware Maintenance with Advance Parts Replacement, and On-Site Hardware Maintenance with a choice of 8x5 or 24x7 Coverage. All offers include Expert SystemsSM diagnostics and 24x7 remote technical support. The Advance Parts and On-Site offers also include equipment replacement. Customers requiring fully comprehensive monitoring will want to combine SS+U with any of the Hardware Maintenance offers. Additional information on Software Support and Hardware Maintenance is available at www.avaya.com under Services Product & IP Support Product Support Offering Software Support and Hardware Maintenance. Available beginning January 2011, Support Advantage becomes the global support offer for all new Enterprise product sales and product upgrades. It provides 24x7 support for both software and hardware, which helps protect customers’ investments in enterprise communications from Avaya. The offer has a simple structure with two base offer choices: 1. Essential Support (minimum level required) 2. Preferred Support

http://www.avaya.com/�




More information about Support Advantage can be found at https://portal.avaya.com/ptlWeb/gs/services/SV0497.

5.2. Service Entitlements for All Customers Web site-based self-help support for Avaya Session and System Manager is available to customers on a 7x24 basis at URL http://www.avaya.com/support/ Web site support includes: • Frequently Asked Questions (FAQs) and trouble isolation procedures related to

Avaya IP products • Technical Articles and white papers • Downloadable firmware upgrades, when applicable • User Guide information • Product Documentation • Product Training Customers will be asked via the web tools to consult with their other vendors before creating an on-line service request (e-ticket) or before calling Avaya when interoperability issues are suspected. Support beyond the web site's self-help information can be obtained via an on-line service request (e-ticket) or phone call requests. Non-service agreement customers will be billed at the Remote Help Desk at prevailing Time and Materials rates. Customers will be required to provide their credit card number or Avaya account number prior to services being rendered. Refer to the warranty contract for the complete terms, conditions, and limitations.

5.3. Warranty Software Warranty Avaya provides a 3 month limited warranty on Session Manager and System Manager software. Detailed terms and conditions are contained in the sales agreement or other applicable documentation and establish the terms of the limited warranty. In addition, Avaya’s standard warranty description and details for support under warranty are available at the Avaya Support Center under “Additional Information for Avaya US Warranty Policy”.

USWarranty_Policy_011603.pdf

https://portal.avaya.com/ptlWeb/gs/services/SV0497�

http://www.avaya.com/support/�




Hardware Warranty Avaya provides a one-year limited warranty on the Avaya Session Manager Appliance hardware. Refer to the sales agreement or other applicable documentation to establish the terms of the limited warranty. In addition, Avaya’s standard warranty language as well as details regarding support, while under warranty, is available through the web site: http://www.avaya.com/support/ or on the Enterprise Portal at https://enterpriseportal.avaya.com/ptlWeb/getfile?docID=MzkyNzg3MQ==. Post Warranty Support Customers may purchase post-warranty software support for the Avaya Session Manager after the expiration of the initial warranty. The customer may purchase support coverage in increments of one (1) year with auto-renew upon renewal, with a maximum contract term of 4 years, limited to 3 years after the product's "last order date." The two types of Maintenance Service Agreement options are the Self-Maintainer option and Full Coverage option. The Self Maintainer option includes Remote Support and Parts plus Remote Support for both 8-5 and 24x7coverage. The Full Coverage option includes 8-5 and 24x7 coverage in which technician dispatch and Tiers of Support are included. Applicable uplifts and downlifts are used to determine the appropriate maintenance price for the offer the customer chooses. These uplifts/downlifts are used against the default reference rate of 8-5 Full Coverage. If the customer chooses not to subscribe to post warranty hardware maintenance, then Avaya bills customers for support on a time and materials basis. Outside the U.S., terms and conditions are determined locally. See http://portal.avaya.com/ptlWeb/services/SV0452 for more details on Software Support and Hardware Maintenance. Whether maintenance is priced via the Utility-based pricing method, or via the maintenance simplification methodology, the following coverage option specifics apply. Table 1: Maintenance Service Agreement Coverage Offer Avaya Maintenance Service Agreement Coverage Parts Plus Remote Remote Only

Parts Plus Remote Support includes: Remote Support (includes Expert Systems remote fault

monitoring on products that support that capability) Parts Replacement, shipped for next-business day arrival. Remote Support includes: Remote Support (includes Expert Systems remote fault monitoring on products that support that capability

Full Coverage 8-5, local time:

Full coverage 8-5 includes: Remote Support (includes Expert Systems remote fault

monitoring on products that support that capability) On-site Parts Replacement On-Site Support

Full Coverage Includes all the standard offer, except on a 7X24, 365 basis,


https://enterpriseportal.avaya.com/ptlWeb/getfile?docID=MzkyNzg3MQ==�

https://enterpriseportal.avaya.com/ptlWeb/getfile?docID=MzkyNzg3MQ==�

http://portal.avaya.com/ptlWeb/services/SV0452�




7x24: including Avaya holidays Other Countries Same as United States, subject to locations where Avaya service is offered. Warranty on parts is available worldwide, but servicing terms and conditions may vary where Avaya direct service is not available.

5.4. Product Correction Notices (PCNs) Product Correction Notice (PCN) and installation support will be provided to all Avaya Session Manager and System Manager customers. Customers with warranty and post warranty coverage will typically receive special consideration for the time and material charges, if applicable, to a specific product and configuration. PCNs are a function of the life cycle of the products. PCN installations will take place between the hours of 8am to 5pm (local time), Monday through Friday, excluding Avaya recognized holidays. Special billing consideration will be given to customers who either have an Avaya Service Agreement or are under warranty, up to but not exceeding an installation absent of labor and material charges. The determination of PCN charges, if any, will be determined on a case-by-case basis by Avaya. Customers who are listed as the technical contact will typically be mailed a letter regarding the PCN notification. Avaya U.S. Direct Customers: U.S. Field Service Organization (FSO) technicians will implement this Change Notice for Avaya U.S. Direct Customers. The Emerging Technologies Solutions Support (ETSS) group and the FSO Change Notice Administration Groups will handle scheduling and coordination. Avaya U.S. BP: Avaya Business Partners who elect to perform the work to implement this Change Notice will be responsible for scheduling and coordinating their customer base. Those who elect to have Avaya perform the work will schedule and coordinate through the Emerging Technologies Solutions Support (ETSS) team. Avaya International: Scheduling of customers requiring a Change Notice will be handled through the Emerging Technologies Solutions Support (ETSS) team. When the need arises for Avaya to replace defective components, Avaya Labs will issue a Product Correction Notice (PCN). The standard PCN process applies for Session Manager and System Manager. Some components can be upgraded without the need for a field dispatch. For a list of active PCNs, go to the Avaya Support Center (http://www.avaya.com/support/) and search under Additional Information for Product Correction Notices. NOTE: The Avaya Network Integration Center may support PSN/PCN’s for a fee. Please contact [email protected] for more information.


mailto:[email protected]�




5.5. Product Support Notices (PSNs) Product Support Notices which replace Service Alerts are issued by Tier 4 Engineers and/or Product Managers to notify the field of technical workarounds, process information, or document corrections/clarifications in addition to software/firmware updates and hardware replacements. For a list of issued PSNs, go to the Avaya Support Center (http://avaya.com/support) and search under Additional Information for Product Support Notices.

5.6. Technical Consulting System Support Avaya provides help line support to U.S. and Canadian business partners and Avaya sales teams through the normal pre-sales support line (888-297-4700 or 720-444- 7700). Avaya provides help line/maintenance support to customers that have purchased a Post Warranty Maintenance agreement during the applicable warranty period through the phone numbers below. This support includes answering questions regarding Avaya Aura Session Manager or System Manager software functionality, providing advice to help customers achieve a working solution, resolving existing system issues and troubleshooting. They will escalate to the Avaya Aura System/Session Manager Tier 4 teams as needed.

Avaya Contact Telephone Numbers

Elite/Premium Customers Please refer to your Avaya Contact numbers

Global Support Services (GSS)-Enterprise 800–242-2121 Global Support Services (GSS)- Business Partners for Enterprise Product

877-295-0099

Canada Customer Care Center 800-387-4268 Caribbean and Latin America 786-331-0860 Europe, Middle East, and Africa 36-1238-8334 Asia/Pacific 65-6872-8686

Avaya Professional Services can provide customer specific configuration, programming and administration support at time and material per incident rates; requests should be sent to the Network Integration Center at [email protected]. Avaya Professional Service’s will assist with customer LAN or design issues as well; requests should be sent to the Advanced Solution Architects at [email protected]. Avaya services can also provide customer specific programming and administration support at time and material per incident rates; customers can call 800-225-7585.

http://avaya.com/support�




Avaya Service’s assistance does not include help with customer LAN or design issues.

5.7. Enhanced Services Available

Avaya Professional Services (APS) APS offers a comprehensive portfolio of professional consulting offers in the areas of Network Consulting, Contact Center, and Unified Communication. APS is a global organization, providing professional consulting to customers and business partners in the US, EMEA, Germany, APAC, CALA, and Japan. More information can be obtained at https://enterpriseportal.avaya.com/ptlWeb/internal/spCP/CS200671318355089067.

Avaya Operations Services (AOS) Avaya Operations Services (AOS) offers provide full management services capabilities to customers allowing them to focus on their core business. Avaya Operations Services offers vary by region and may include, but are not limited to:

• Single point of contact for system administration and fault management • General usability help line support • 8 x 5 local site time maintenance • Standard service level agreements • Engagement Manager assigned for the term of the Agreement • Program management of all communications projects • Single monthly invoice with multi-level data

Avaya Operations Services are delivered through a combination of AOS associates and associates from other Avaya services teams. AOS pricing is structured into monthly recurring charges on a per port basis, plus additional charges for services such as special projects. More information can be found at http://outsourcing.avaya.com/.

5.8. Avaya Labs Field Support The Avaya Labs Field Support organizations (CPE) are responsible for the following activities:

Provide escalation support for the GSS Status all GSS (Backbone) escalations Negotiate with Avaya Labs developers to secure fixes in a time frame necessary to meet customer expectations Assist in the development of procedures for product updates and PCN applications Issue Modification Requests (MRs) against the application, as required Function as a Subject Matter Expert to the product extended team, as necessary Escalation to Avaya’s development team to work with third party development partners such as Dell, GE Fanuc, or Red Hat’s Tier IV, etc., when appropriate Populate NPST Field Support problem / resolution database for use by tiers 2

https://enterpriseportal.avaya.com/ptlWeb/internal/spCP/CS200671318355089067�

http://outsourcing.avaya.com/�




through 4 Compose Product Support Notices (PSNs) and Product Correction Notices (PCNs), when applicable

5.9. PLDS Software Download Policy Warranty or Post-Warranty Maintenance customers will be entitled to free ETSS support should they encounter problems with PLDS software downloads during normal Avaya business hours. Customers (regardless of their PWM structure), who require assistance during non-business ETSS hours, will be billed at prevailing ETSS out-of-hours rates.

A DVD option is now available for Session Manager and System Manager. The DVD is now the default option in ASD for Session Manager. Customers may also download the System Manager and Session Manager Software from PLDS. This software must be kept at the customer site at all times. During remote/onsite installation, troubleshooting and disaster recovery scenarios the customer will be asked to provide the Software downloads. If the software is not on site there may be a delay in support. If the customer would like the technician to download the software, the project manager for the customer site must fill out a Change Request Management Form (CMRA), where the customer will be charged $250.00 per hour for the download. Note: The PLDS download could take several hours and the customer will be charged for the entire time. The software can be downloaded from the PLDS website and must be placed on a DVD. More information on PLDS Software downloads can be found at www.plds.avaya.com.

5.10. PLDS Licenses PLDS Support for License Activation and Entitlement Moves will be done through the NIC team for a fee. Support can be obtained by sending an email to Avaya Professional Services at [email protected]. More information on PLDS Licenses can be found at www.plds.avaya.com.

5.11. Remote Maintenance Avaya provides support for purchased software and hardware components. Support is provided under the “Software Support and Hardware Maintenance” support offer and is priced at normal SSU prices and 15% Hardware Maintenance – 8X5. Business Partners are also trained to support the hardware and software under the Joint Service Delivery program. Please see http://portal.avaya.com/ptlWeb/services/SV0452

for more information about these support programs. Avaya requires remote access to provision and support under the software support maintenance agreement.

Remote Access via Secure Access Link Gateway 1.8

http://www.plds.avaya.com/�


https://enterpriseportal.avaya.com/ptlWeb/internal/so/CS20051215125424913041�

https://enterpriseportal.avaya.com/ptlWeb/internal/so/CS20051215125424913041�

http://portal.avaya.com/ptlWeb/services/SV0452�




System Manager provides secure, rapid serviceability and Expert Systems alarming through Secure Access Link (SAL) to Avaya and participating Business Partners. SAL uses the customer’s existing Internet connectivity to facilitate remote support. All communication is outbound from the customer’s environment using encapsulated Hypertext Transfer Protocol Secure (HTTPS). SAL requires upload bandwidth (customer to Avaya/Partner) of at least 90 KB/s (720 Kbits/s) with latency no greater than 150 ms (round trip). A Secure Access Link 1.8 Gateway will be deployed as part of every System Manager 6.2 via System Platform, and subsequently because every Session Manager 6.2 will be deployed with a System Manager 6.2, all remote access to a customer’s Session Manager will be via this SAL Gateway. Additionally, we can expect that as customers currently running Session Manager 1.1 (supported by System Manager 1.0) migrate to System Manager 6.2, they can move off of the RSIG and inherit the Secure Access Link capabilities afforded them by System Manager 6.2 on System Platform. Session Manager 5.2 and 6.0 already utilizes SAL for remote access. Note – All alarming from Session Manager 5.2 and 6.0 will continue to use the SAL Enterprise components in System Manager and not the alarming components of the SAL Gateway. Business Partners without a SAL Concentrator must provide their own IP-based connectivity (for example, B2B VPN connection) to deliver remote services.

Important: Business Partners and customers must ensure that SAL is always configured and registered with Avaya during installation. Avaya support will be delayed or not possible if SAL is improperly implemented or not operational. Modem connections are not supported.

6. DOCUMENTATION

6.1. Release Notes Release Notes for Session Manager and System Manager are available at the Avaya support center at http://support.avaya.com. Also see Product Support Notices (PCNs).

6.2. User and System Documentation In support of the Avaya-wide Go Green initiative, Avaya no longer provides paper and CD documentation. Avaya online documentation is a free download available from Avaya Support at http://www.avaya.com/support. Click on Find Documentation and Downloads by Product Name, and under Session Manager, Communication Manager or System Manager select View all documents.

http://support.avaya.com/�




The following are the documents relating to Session Manager and all have been updated with new information for R6.2.

Session Manager Documentation Doc ID Title 03-603323 Avaya Aura® Session Manager Overview

03-603473 Installing and Configuring Avaya Aura® Session Manager

03-603324 Administering Avaya Aura® Session Manager

03-603479 Administering Avaya Aura® Communication Manager Server Options

03-603478 Avaya Aura® Session Manager Case Studies

03-603325 Maintaining and Troubleshooting Avaya Aura® Session Manager

03-603518 Upgrading Avaya Aura® Session Manager

NA Installing Service Packs for Avaya Aura® Session Manager

NA Avaya Aura® Session Manager Security Design

NA Installing and Upgrading Avaya Aura® System Manager




The following are the new documentation for the new server platforms for Avaya Aura.

Server Platform Documentation Doc ID Title 03-603793 Installing the Dell™ PowerEdge™ R610 Server

03-603799 Installing the HP ProLiant DL360 G7 Server

03-603804 Maintaining and Troubleshooting the Dell™ PowerEdge™ R610 Server

03-603803 Maintaining and Troubleshooting the HP ProLiant DL360 G7 Server

The following table shows the Communication Manager documentation library with the new documents shown in dark blue print.




Communication Manager Documentation Doc ID Title 03-300468 Avaya Aura® Communication Manager Overview 03-300511 Avaya Aura® Communication Manager Feature Description 03-603558 Installing and Configuring Avaya Aura® Communication Manager 03-603560 Upgrading to Avaya Aura® Communication Manager Release 6.0 03-300509 Administering Avaya Aura® Communication Manager 03-602878 Avaya Aura® Communication Manager Screen Reference

210-100-700 Avaya Extension to Cellular User Guide 555-233-505 Avaya Aura® Communication Manager Reports

03-300430 Maintenance Alarms for Avaya Aura® Communication Manager, Media Gateways and Servers

03-602793 Avaya Aura® Communication Manager Denial Events

03-300431 Maintenance Commands for Avaya Aura® Communication Manager, Media Gateways and Servers

03-300432 Maintenance Procedures for Avaya Aura® Communication Manager, Media Gateways and Servers

03-600759 Avaya Support Notices for Hardware Documentation 555-245-207 Avaya Aura® Communication Manager Hardware Description and Reference 03-300511 Avaya Aura® Communication Manager System Capacities Table 03-601973 Avaya Aura® Communication Manager Security Design

555-025-600 Avaya Toll Fraud Security Guide

03-601818 What’s New in Avaya Aura® Communication Manager, Avaya Servers and Media Gateways for Release 6.0

03-600843 Application Note: Reference Configuration for Software Duplication 03-300428 Avaya Aura® Communication Manager Survivability Options 03-602798 Avaya Aura® Communication Manager Server Alarms 03-603628 Accessing and Managing Utility Servers

555-245-600 Avaya Application Solutions – IP Telephony Deployment Guide 03-600843 Application Note: Reference Configuration for Software Duplication 03-602884 Converting Avaya Servers and Media Gateways 03-300684 Adding New Hardware for Avaya Servers and Media Gateways

555-233-504 Administering Network Connectivity on Avaya Aura® Communication Manager 03-602804 LED Descriptions for Avaya Aura® Communication Manager Hardware Components 03-602803 Gateway Traps for the G250/G350/G450/G700 Avaya Media Gateways 03-602013 Avaya Aura® Communication Manager SNMP Reference Guide 03-602953 Job Aids for Field Replacements (FRUs) for the Avaya S8510-Series Server 03-603446 Maintaining the Avaya S8800 1U Server for Avaya Aura Communication Manager 03-601703 Authentication File System (AFS) User Guide 03-603444 Installing the Avaya S8800 Server for Avaya Aura Communication Manager 03-603723 Avaya Aura® Communication Manager Change Description for Release 6.2 03-603560 Upgrading to Avaya Aura® Communication Manager Release 6.2




7. TRAINING Avaya Aura® Session Manager training is available from the Avaya University website web-based, hands-on and instructor-led courses are available for complete instruction on all aspects of these core Avaya products. Courses may be enrolled via the Avaya Learning Center at:

http://www.avaya-learning.com/logon_form.asp Please reference the Avaya Learning Center for the most up to date information; an initial list of courses follows, with the modified or new courses listed in dark blue print.

SIP Courseware

Quick SIP ATC 01270 WEN SIP Essentials ATC 01290 WEN

Communication Manager 6.0 Courseware CM and System Manager ATC 01842 OEN Avaya Aura® 6.0 Feature Server and User Related Admin ATC 01671 VEN Avaya Aura® Communication Manager Basic Administration AVA 00836 H00 Administering and Maintaining Avaya Aura® System Platform (6.0) ATC 00421 VEN System Platform Installation for CM R6.0 ATI 01445 WEN Licensing for Avaya Aura® Communication Manager ATI 01732 WEN Avaya Aura® Communication Manager Architecture and Features ATU 01730 WEN Avaya Aura® Communication Manager Fundamentals ATI 101672 VEN

Session Manager 6.0 Courseware Session Manager General Overview ATU 00171 OEN Session Manager 6.0 in the Network ATU 00172 OEN Session Manager Network Routing Policy Administration ATI 00176 VEN Session Manager Technical Overview ATU 00170 OEN Session Manager 6.0 Delta: General Overview ATC 01826 OEN Session Manager 6.0 Delta: Technical Overview ATC 01827 OEN Session Manager 6.0 Installation & Initial Setup ATC 00173 OEN Session Manager Rack and Stack ATC 00175 OEN

http://www.avaya-learning.com/logon_form.asp�




Session Manager 6.2 Delta: General Overview ATU 01515 OEN Session Manager 6.2 Delta: Technical Overview ATU 01516 OEN Session Manager 6.2 Installation & Initial Setup ATA 02446 OEN Survivable Remote Session Manager 6.2 Installation & Initial Setup ATA 02447 OEN

Session Manager Instance Administration ATA 01517 VEN Session Manager, CM and other Feature Server Administration ATI 02445 VEN

Survivable Remote Session Manager Administration ATC 01840 OEN

System Manager 6.0 Courseware

Getting Started with System Manager ATC 00182 OEN CM and System Manager ATC 01842 OEN System Manager Administering User Profile Accounts ATC 00184 VEN System Manager 6.0 General Overview ATU 00180 OEN System Manager 6.0 Technical Overview ATU 00183 OEN System Manager 6.0 Delta: General Overview ATC 01825 OEN System Manager 6.0 Delta: Technical Overview ATC 01828 OEN System Manager 6.0 Installation and Setup ATU 01852 OEN Advanced System Manager Administration ATA 02540 VEN System Manager 6.2 Delta: General Overview ATU 02643 OEN System Manager 6.2 Delta: Technical Overview ATI 02642 OEN System Manager 6.2 Installation and Setup ATA 02641 OEN




APPENDIX A: AVAYA AURA PACKAGING Avaya Aura® Editions Avaya Aura is easy to purchase and deploy through Avaya Aura Editions: Branch Edition, Standard Edition and Enterprise Edition. These software Editions bring together all the functionality needed for common customer situations with a simple per user licensing fee. Hardware (servers, gateways, and phones) are flexibly purchased in addition to software licenses and the hardware topology depends on the redundancy, scalability and geographic distribution needs for each customer. Different elements of the software may run on separate hardware servers, or some elements may be combined on the same hardware server. Gateway distribution and configuration will depend on availability and capacity needs. Avaya and BusinessPartner sales engineers assist customers in designing the right hardware configurations to meet their business needs. The software Editions and their functionality remain the same regardless of hardware choices. Avaya Aura® Standard Edition meets the needs of single-site deployments and mid-to-large distributed enterprises requiring comprehensive voice, video, messaging, SIP and Presence communications capabilities with standard survivability at remote locations. Standard Edition has the option to easily add licensing for enterprise-wide SIP session management and Unified Communications applications for targeted users, including Microsoft and IBM UC integration, and mobile worker and teleworker support. Avaya Aura® Enterprise Edition includes everything in Standard Edition and meets the needs of highly distributed, and potentially multinational, mid-to-very-large enterprises requiring the same comprehensive communications capabilities with increased high availability options including 100% feature survivability at remote locations. Enterprise Edition includes, with no additional licensing, enterprise-wide SIP session management and Unified Communications applications for all users, including Microsoft and IBM UC integration, and mobile worker and teleworker support. All Avaya Aura Editions include appropriate management and administration tools. Additional Avaya unified communications and contact center solutions, including rich unified messaging, conferencing and web collaboration, video endpoints and bridges, speech and video self service, and market-leading inbound and outbound multimedia contact center applications, can all be incrementally added to Avaya Aura Editions. An extensive array of certified third-party products is also available through the Avaya DevConnect ecosystem. How to Order Avaya Aura Editions To order Avaya Aura Editions today use the existing material codes for Avaya Aura Communication Manager Standard 6.0, Avaya Aura Communication Manager Enterprise 6.0 or Avaya Aura Communication Manager Branch 2.0 adding codes for each entitlement as appropriate to the Avaya Aura package.




APPENDIX B: GLOSSARY OF TERMS AND ACRONYMNS

Term Definition 802.1p/Q IEEE standard 802.1Q and 802.1p provide the means to specify both a virtual

LAN (VLAN) and a frame priority at layer 2 for use by LAN hubs, or bridges, which can do routing based on MAC addresses. 802.1p/Q provides for 8 levels of priority (3 bits) and a large number (12 bits) of VLAN identifiers. The VLAN identifier at layer 2 permits segregation of traffic to reduce traffic on individual links. Because 802.1p operates at the MAC layer, its presence may vary from LAN segment to LAN segment within a single network region. Flexibility requires that 802.1p/Q options be administered individually for each network interface.

ADC Asian Distribution Center ARS Automatic Route Selection networking software ASA Advanced Solution Architect ASD Avaya Solution Designer ASG Access Security Gateway BCS Business Communication Systems BSR Best Service Routing CAMA Centralized Access Message Accounting CAC Call Admission Control CAS Channel Associated Signaling CIRD Classless Interdomain Routing - CIDR is defined as a redefinition of the subnet

mask, allowing for the aggregation of contiguous classful networks under a single network definition. This allows for more efficient routing table management.

CLI Command Line Interpreter CO Central Office CoE Center of Excellence, part of GSO CoK TSC's College of Knowledge CSA Avaya Customer Software Associate DCP Digital Communications Protocol DCS Distributed Communications System feature of Avaya Communication Manager DHCP Dynamic Host Control Protocol DID Direct Inward Dial DiffServ Differential Services – a method of specifying service requirements for IP

packets at Layer 3. With the DiffServ option the system administrator can administer (by region) and download to the TN2302AP the DiffServ Type-of-Service (TOS) value, thus allowing data networking equipment to prioritize the audio stream at the IP level to promote voice quality. DiffServ makes use of the Type-of-Service (TOS) octet in the existing IP Version 4 header. As such, it may be set by information senders and used by IP (layer 3) routers within the network. Use of DiffServ and/or 802.1p priorities would typically apply to either or both ends of a connection: the TN2302AP interfaces should be configured to use the appropriate values for the network(s) to which they are attached, and the IP end-points should be configured to use the values appropriate for the network(s) to which they are connected. In many cases, the communication devices are “local” and the values are the same; in other cases, the values may be different. This can be accommodated by downloading default values to the endpoint to be used in case the endpoint installer or the user has not provided values.

DSO Data Services Organization DSP Digital Signal Processor




Term Definition ECLIPS Enterprise Class IP Solutions ECS DEFINITY Enterprise Communication System, refers to release 5 and later EDC European Distribution Center EIS Enterprise Internetworking Systems, the Avaya business unit that provides and

supports data networking equipment. ESS Enterprise Survivable Server FSO Avaya Field Services Organization FTSO Field Technical Support Organization (formerly known as the FSO and GSO) FX Foreign Exchange GCF Gatekeeper Confirmation: Avaya Communication Manager sends this to an

endpoint in reply to a GRQ if the registration is proceeding normally. GES Global Enterprise System, Avaya's new infrastructure support system, based on

SAP R/3 GK Gatekeeper GSIO Global Services Information Officer group GSO Global Support Organization GTS Global Technical Services (formerly the RTS and TSO) GUI Graphical User Interface GULLF Graphical User interface Look, Listen, and Feel IST Implementation Support Team H.225.0 Call signaling protocols and media stream packetization for

packet-based multimedia (includes Q.931 and RAS) H.225.0 Annex G

Gatekeeper to gatekeeper (inter-domain) communications

H.235

Security and encryption for H-series multimedia terminals

H.245

Control protocol for multimedia communications

H.323 Annex D

Real-time fax using T.38

H.323 Annex E

Call connection over UDP

H.323 Annex F

Single-use device

H.323 V2 Packet-based multimedia communications systems H.450.x Supplementary services for multimedia.

Generic functional protocol for the support of supplementary services in H.323 2. Call transfer 3. Diversion 4. Hold 5. Park & pickup 6. Call waiting 7. Message waiting indication

IP Internet Protocol, part of the TCP/IP protocol stack ISDN Integrated Services Digital Network IT Information Technology ITAC International Technical Assistance Center, part of GSO JTAPI Java Telephony Application Programming Interface The JTAPI standard is fully

supported by Avaya’s CentreVu Computer Telephony. The Java Telephony API (JTAPI) is a portable, object-oriented Application Programming Interface for Java-based computer-telephony applications. JTAPI serves a broad audience, from call center application developers to Web page designers. JTAPI supports




Term Definition both first-party and third party CTI application needs.

LAN Local Area Network LDAP Lightweight Directory Access Protocol LSP Local Survivable Processor MACS Multimedia Applications Customer Support, a NetCare Data Professional

Services group MAPD Multi-Application Platform — DEFINITY MB Megabytes of memory or hard disk space MC Media Controller MGCP Media Gateway Control Protocol MNC Customers designated as Multinational Customers NAT Network Address Translation, used with Virtual Private Networks NIC Avaya Network Integration Center NT Microsoft New Technology Operating System OSSI Operations Support System Interface, a batch-oriented DEFINITY protocol PCMCIA Personal Computer Memory Card International Association PEC Price Element Code PLDS Product Licensing and Distribution System – the Avaya website tools used to

download licensing and software for Avaya products. PNA Private Network Access networking software PRI Primary Rate ISDN trunk PSO Professional Services Organization PSTN Public Switched Telephone Network RAID Redundant Array of Inexpensive Disks RAS Registration, Authentication, and Status: the overall process of establishing

communication between an endpoint and a switch, in the H.323 protocol. RSIG Remote Secure Intelligent Gateway SAL Secure Access Link SAP This isn’t an acronym, but rather the name of the company that sold an ordering

and tracking system to Avaya. SAT DEFINITY System Access Terminal, replaced by DSA at customer sites SGCP Simple Gateway Control Protocol SI Streamlined Implementation process SIP Session Initiation Protocol SNMP Simple Network Management Protocol SPC Avaya Services Product Connect, which links the RTS / GSO to customer

products via IP SPE Service Price Element; associated with time and materials billing SSP DEFINITY Size Sensitive Ports T&M Time and materials billing T.38 Procedures for real-time group 3 facsimile communications over IP Networks TAC In-country Avaya Technical Assistance Center TCP Transmission Control Protocol is a reliable end-to-end transport-level protocol

which provides error detection and correction, flow control, and sequencing; the Internet standard reliable transport protocol

TFTP Trivial File Transfer Protocol TIEU Technical Instructor - End User TSAPI Telephony Services Application Programming Interface. TSAPI also is a key

integration for Outbound Call Management enabling call generation based on data base prompts.




Term Definition TSC Technical Service Center TSC-SS Technical Service Center Support System, replaced by Maestro UDP Uniform Dial Plan UDP User Datagram Protocol, a connectionless protocol that, like TCP, runs on top of

IP networks. Unlike TCP/IP, UDP/IP provides very few error recovery services, offering instead a direct way to send and receive datagrams over an IP network. It's used primarily for broadcasting messages over a network in real time.

VLSM VLSM is defined as a redefinition of the subnet mask, allowing for a more efficient allocation of IP addresses within a traditional classful block. During administration, the user will input a Network Bits value between 1-30 on the ip-route form which will correspond to a particular subnet mask.

VNMA Voice Network Management Assist offer, previously known as Qualnet VPN Virtual Private Network WAN Wide Area Network




APPENDIX C: RELEASE HISTORY LIFECYCLE DATES This table shows the End of Sale and End of Manufacturer supports dates for the various versions of Avaya Communication Manager and its predecessors. For the lifecycle dates for supporting hardware and servers refer to the respective hardware product definitions and lifecycle announcements.

Release Version Launch Date End of Sale Date

End of Manufacturer Support Date

Additions Still

Allowed?* G3V2 January, 1994 June 7, 2004 No G3V3 March 1995 June 7, 2004 No G3V4 June 1997 June 7, 2004 No ECS R5 November

1997 March 7, 2005 No

ECS R6 February 1999 March 7, 2005 No ECS R7 June 2000 March 7, 2005 No ECS R8 March 2001 March 7, 2005 No ECS R9 March 2002 March 7, 2005 Yes R10 July 2002 March 7, 2005 Yes Communication Manager 1.x

June 5, 2002 February 8, 2004

January 15, 2006 November 5, 2007 (for the DEFINITY Server R only)

Yes

Communication Manager 2.x

December 8, 2003

December 5, 2005

October 10, 2007 December 15, 2008 (for the DEFINITY Server SI only)

Yes


June 13, 2005 December 31, 2007

December 31, 2008

Yes


March 19, 2007 February 7, 2009

February 7, 2010 Yes


January 7, 2008 March 5, 2012 March 5, 2013 Yes


June 7, 2010 Not announced Not announced Yes

*Additions means adding additional users. See Appendix D: Additions to CM4 and Earlier Systems for more details.




APPENDIX D: ADDITIONS TO CM 4.0 AND EARLIER Features and capacity can still be added to older DEFINITY systems and up through Avaya™ Communication Manager 4.x release. The document that outlines the material codes, pricing and policies for additions to these older systems can be found at the Avaya Enterprise Portal-> Product-> Products A-Z-> Communication Manager-> Sales Collateral-> Jobs Aids and Tools (under Tools) -> Appendix D Additions to CM4 and Earlier systems.




APPENDIX E: SOFTWARE RE-LICENSING POLICY A full description of Avaya's licensing policy and approach to re-licensing for Avaya Communication Manager can be found under Global Licensing Policy project Documentation in Business Tools & Processes -> Software Licensing & Fulfillment -> License Portability http://portal.avaya.com/ptlWeb/so/CS2010105203323127038.




APPENDIX F: CM FEATURES AND RELATED PRODUCTS Appendix F is no longer provided as of CM 6.0 For a complete list of the history of changes between Communication Manager Release 1.1 through 6.x, please go to the Avaya Enterprise Portal-> Products ->Products A-Z-> Communication Manager-> Release History. To obtain official documentation covering all Communication Manager features, refer to the above Documentation section of this product definition.




APPENDIX G: MIGRATION AND MERGE OFFERS As a customer’s needs change, Communication Manager servers can be replaced with higher-capacity versions and also several servers can merged into one larger system. Detailed information on License Migrations & Merges is available at the Global License Portability (GLP) Process and found under GLP project Documentation in Business Tools & Processes -> Software Licensing & Fulfillment -> License Portability http://portal.avaya.com/ptlWeb/so/CS2010105203323127038. Appendix G is no longer provided as of CM 6.0.

http://portal.avaya.com/ptlWeb/so/CS2010105203323127038�




APPENDIX H: LICENSE MOVES As of the release of Avaya Aura 6.0, APPENDIX H: License Moves document is no longer required. License moves are now part of the Global License Portability (GLP) Process and found under GLP project Documentation in Business Tools & Processes -> Software Licensing & Fulfillment -> License Portability http://portal.avaya.com/ptlWeb/so/CS2010105203323127038.




APPENDIX I: SURVIVABLE REMOTE AND ICC CONVERSION The process to convert an S8300 or S8500 ICC to LSP or vice versa is detailed at the Avaya Enterprise Portal-> Product-> Products A-Z-> Communication Manager-> Sales Collateral-> Jobs Aids and Tools (under Tools) -> Appendix I ICC and LSP conversion. Appendix I is no longer provided or applicable as of CM 6.0




APPENDIX J: MOVING SURVIVABLE REMOTE AND CORE The process to move S8300 and S8500 LSP and ESS servers between main servers is detailed at the Avaya Enterprise Portal-> Product-> Products A-Z-> Communication Manager-> Sales Collateral-> Jobs Aids and Tools (under Tools) -> Appendix J moving LSP and ESS. Appendix J is no longer provided or applicable as of CM 6.0




APPENDIX K: UPGRADE PROTECTION PLAN FOR CM 4.0 The Upgrade Protection Plan for Communication Manager (UPPCM) is no longer available. With release 5.0 and later, UPPCM has been replaced with Software Support plus Upgrades (SS+U). This appendix is no longer provided or updated.




APPENDIX L: ESS CONVERSIONS The process to convert an S8300 or S8500 Enterprise Survivable Server to Main Server or vice versa is detailed at the Avaya Enterprise Portal-> Product-> Products A-Z-> Communication Manager-> Sales Collateral-> Jobs Aids and Tools (under Tools) -> Appendix L ESS Conversions. Appendix L is no longer provided or applicable as of CM 6.0




APPENDIX M: RFA LICENSED FEATURES This appendix is no longer provided as of CM 6.0.




APPENDIX N: STANDARDS SUPPORTED

RECOMMENDATION SUPPORT

G.711 Y G.726 Y (note 1) G.728 Y (note 1) G.729 Y (note 1) G.729a Y (note 1) G.722 Y (note 1) RFC 3261 Y RFC 3263 Y 802.1p Y 802.1q Y SNMP Y FAX - Group 3 Y FAX - Group 4 N T.37 N T.38 Y IP Precedence Y Differentiated Services Y Weighted Fair Queuing NA (will use routers) CBWFQ NA PQWFQ NA -RED NA Weighted RED NA RTP Y CRTP N RTCP Y RTSP N Policy Based Routing NA Committed Access Rate NA IPv6 N TCP/IP Y UDP/IP Y DHCP Y TLS Y

Notes: 1: While many Avaya Aura® components support these codecs, MM does not support G.729, G.726, G.728, G.729a or G.722




CONTACT INFORMATION NOTE: If you have questions regarding the Avaya Aura Solution, please contact ATAC at 888-297-4700 or 720-444-7700 (Hours of operation: 9 am EST – 8 pm EST) before contacting the responsible Product Manager(s) below.

Product Management Contacts

Product Contact Email

Avaya Aura®

Avaya Aura® Donna Logan [email protected]

Avaya Aura® Session Manager

Stephen Durney [email protected]

Avaya Aura® System Manager

John Cato [email protected]

Avaya Aura® Presence Services

Stephen Durney [email protected]

Avaya Aura® Application Enablement Services – CC (CVLAN, DLG, TSAPI)

Cathy Smyth [email protected]

Avaya Aura® Application Enablement Services – UC (DMCC, Unified Desktop, servers)

Henry Wright [email protected]

Avaya Aura® Communication Manager

Conrad Uniacke [email protected]

Avaya Aura® Communication Manager Messaging

Mike Wasserburger

[email protected]

Avaya Aura® Conferencing Matt O’Donnell [email protected]

Avaya Aura® Messaging Rudi Potze [email protected]

Avaya Aura® Session Border Controller

Michael Dews [email protected]















Product Contact Email

Related Products & Solutions

Agile Communication Environment

Paul Rowe [email protected]

Avaya Integrated Management

Mike Killeen [email protected]

Avaya one-X® – UC All Inclusive

Praveen Mamnani [email protected]

Branch Media Gateways Bruce Lieou [email protected]

Call Center Bill Jolicoeur [email protected]

G860 Gateway Bruce Lieou [email protected]

Intelligent Customer Routing

Jason Hostetter mailto:[email protected]

Meeting Exchange Matt O’Donnell [email protected]

one-X® Agent Michael Harwell [email protected]

one-X® Mobile, one-X® Portal, EC500

Julie Thiesen [email protected]

one-X® Communicator, Softphone clients

Praveen Mamnani [email protected]

one-X® Deskphone SIP for 9600-series phones

Thomas Petsche [email protected]

one-X® Deskphone Value Edition SIP for 1603 phone

Eric Koob [email protected]

Solutions for Midsize Enterprises

David Dubois [email protected]

Software Support and Hardware Maintenance

Extended Manufacturers Software Support Policy

Jan Leistikow [email protected]

© 2012 Avaya Inc. All Rights Reserved.

All trademarks identified by the ® or TM are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their

respective owners.





mailto:[email protected]?subject=Contact%20Center%20&%20IP%20Agent�


mailto:�

mailto:�









AA6-2SolutionDefMay2

Documents

Transcript of AA6-2SolutionDefMay2