Avaya Aura 8 1 1 Offer Definition2

avaya.
com
Date of Issue: October 2019

ADMS Doc. ID: 191294
_____________________________________________________________________________________
Offer Definition
Avaya Aura® 8.1.1
Includes:
Avaya Aura® Communication Manager 8.1.1
Avaya Aura® Session Manager 8.1.1
Avaya Aura® System Manager 8.1.1
Avaya Aura® Appliance Virtualization Platform 8.1.1
Avaya Aura® Presence Services 8.1.1
Avaya Aura® G430/G450 Media Gateway 8.1.1
Avaya Aura® Application Enablement Services 8.1.1
Avaya WebLM 8.1.1
Avaya Aura® AVP Utilities 8.1.1
Avaya Aura® Media Server 8.0.2
Avaya Aura® Device Services 8.0
Avaya Device Adapter 8.1.1
Avaya Aura® Utility Services (US) (component is removed from the solution as of R8.0
element)
Compatible EOMS application : Avaya Aura® Communication Manager Messaging 7.0.0.1
Avaya Inc. – Proprietary. 1

Use pursuant to the terms of your signed agreement or Avaya policy.
avaya.com
 This Avaya Aura® 8.1.1 Offer Definition is inclusive of all features in the 8.x release stream, it
will continue to be updated over time as needed unless otherwise noted.
Please ensure you have downloaded the latest version (see Change Control)
© 2011 Template Rev 1.0 Avaya Inc. All Rights Reserved.

Avaya and the Avaya Logo are trademarks of Avaya Inc. and are registered in the United States and other countries.
All trademarks identified by ®, TM or SM are registered marks, trademarks, and service marks, respectively, of Avaya Inc.
All other trademarks are the property of their respective owners. Avaya may also have trademark rights in other terms used
herein.
References to Avaya include the Nortel Enterprise business, which was acquired as of December 18, 2009.
02/10
Offer Definition
Product ➔ Avaya Aura® 8.1.1 GA Date ➔ Jun. 10, 2019

Rev # Rev Date
1.0 10/28/19
Avaya Source Prime Channel Partner Target Audience

John Cato Product Management, Order Management, Documentation,
Training, Lab Engineers, Sales Engineers
CHANGE CONTROL RECORD
Date Issue/Version # Prime Summary of Changes
(mm/dd/yy)
10/28/19 1.0 John Cato GA Version

avaya.com
Table of Contents
1.0 ABOUT THIS DOCUMENT .......................................................................................................... 10
1.1. NON-DISCLOSURE ...........................................................................................................................................10
1.2. GLOBALIZATION .............................................................................................................................................10
2.0 TEAM ENGAGEMENT SOLUTIONS ........................................................................................... 10
2.1. AVAYA AURA® PLATFORM ..............................................................................................................................11
Communication Manager Overview ......................................................................................................... 12
Session Manager Overview .................................................................................................................... 13
System Manager Overview .................................................................................................................... 13
Avaya Aura® Media Server (AAMS) Overview ....................................................................................... 14
Avaya Gateways Overview ................................................................................................................... 16
Application Enablement Services Overview ................................................................................................ 17
Presence Services Overview .................................................................................................................... 18
Communication Manager Messaging Overview ............................................................................................ 18
WebLM Overview ............................................................................................................................. 18
Avaya Aura® Device Services Overview ........................................................................................... 19
Avaya Device Adapter Overview .................................................................................................... 20
AVP Utilities .......................................................................................................................... 20
Utility Services .......................................................................................................................... 20
3.0 ABOUT AVAYA AURA® 8.1.1 ......................................................................................................... 20
3.1. WHY UPGRADE TO AVAYA AURA® 8.1.1? ........................................................................................................21
Communication Manager Large Profile capacity increases let you do more with less, simplifying your administration and network design [8.1]
23
5000 SIP branches supported by a single SMGR [8.1] .......................................................................................... 24
1 Million SIP Devices with a single SMGR.[8.1] ................................................................................................ 24
The number of SIP Users is increased from 250K to 300K users [8.1] ........................................................................ 24
Increase in CM TLS Connections and Trunk Members [8.0] .................................................................................. 24
16-Digit Extension [8.0] ............................................................................................................................. 24
Increase SIP Trunks / SIP Agents [8.0] .......................................................................................................... 24
SIP Call Preservation on SM Failures .............................................................................................................. 24
Extended Manufacturer Software Support Release Policy ............................................................................... 29
3.2. SUMMARY OF FEATURES DELIVERED IN AVAYA AURA® 8.1.1, 8.1, 8.0.1 AND 8.0 ............................................31
3.3. AVAYA AURA® 8.1.1 PLATFORM; PRODUCT COMPONENTS .............................................................................34
3.4. AVAYA AURA® 8.1.1 DEPLOYMENT OPTIONS .................................................................................................35
Software deployment options .................................................................................................................. 35
Avaya provided Software & Hardware deployment options ............................................................................. 40
Supported Deployment Options by Application Summary ............................................................................... 42
4.0 AVAYA AURA® 8.1.1 ....................................................................................................................... 43
4.1. OVERVIEW.......................................................................................................................................................43
4.2. BUSINESS PARTNER VALUE PROPOSITION .......................................................................................................43
Current Market Situation .................................................................................................................... 43
Market Needs, Trends and Growth ......................................................................................................... 44
Value Proposition .............................................................................................................................. 44
Competition ..................................................................................................................................... 45
Defensible Differentiators ..................................................................................................................... 46
Partner Business and Strategic Value ....................................................................................................... 46

avaya.com
5.0 AVAYA AURA® 8.1.1 FEATURE DESCRIPTIONS ........................................................................ 47

5.1. AVAYA DEVICE ADAPTER INTRODUCTION TO ENABLE CS 1000 ......................................................................47
What is the Device Adapter snap-in? ....................................................................................................... 47
Benefits of the Device Adapter snap-in with Avaya Aura® ............................................................................ 47
CS 1000 Features Supported ................................................................................................................ 48
Key Features .................................................................................................................................... 49
Avaya Device Adapter Licensing and Deployment ....................................................................................... 49
Device Adapter Languages Supported ...................................................................................................... 50
Supported UNIStim Sets and Add-on Modules supported (8.0) ....................................................................... 50
Support for Digital and Analog sets (8.0.1) ............................................................................................... 50
FIPS 140-2 Support for both Device Adapter and UNIStim devices(8.1) .......................................................... 52
Addition of MDA (Multiple Device Access) feature to Device Adapter (8.1) ............................................... 52
52
52
52
52
52
52
52
52
52
.................................................................................................................................................... 52
Support for the existing CM CFW (Call-Fwd) feature on Device Adapter, where a phone can CFW on behalf of another phone
(BFS) (8.1.1) ........................................................................................................................................... 52
Improve Load Balancer Redundancy Within 1 Breeze Cluster to > 2 Breeze Servers (8.1.1) ............................. 52
Virtual Office (VO) Functionality (8.1.1) ........................................................................................ 52
53
53
53
53
53
53
53
53
53
.................................................................................................................................................... 53
.................................................................................................................................................... 53
.................................................................................................................................................... 53
.................................................................................................................................................... 53
Tool to determine if ADA phone is CFWAC (Call Forward All Calls) or not (8.1.1) .................................. 53
daHelp command can be used to list all available ADA specific commands (8.1.1) ......................................... 53
5.2. INFRASTRUCTURE UPDATES.............................................................................................................................53
AVP Hypervisor Update [8.1] ............................................................................................................. 53
Redhat Enterprise Linux (RHEL) update in Aura applications [8.1] .............................................................. 53
Latest versions of Browsers supported ....................................................................................................... 53
5.3. OPERATING SYSTEM SEPARATION FOR ALL PLATFORM ELEMENTS AND INDEPENDENCE FROM DEPLOYMENT
ENVIRONMENTS & VE UPDATES ..................................................................................................................................53
OS Separation of all AA Platform components [8.0] ................................................................................... 53
Additional platform support : Google Cloud Platform and Microsoft Azure [8.0] .................................................. 56
Additional platform support : Microsoft HyperV [8.0.1] ............................................................................... 57
Additional Software supported in OS Separated environment [8.0.1] ................................................................. 57
VE updates ..................................................................................................................................... 58

avaya.com
5.4. AVAYA AURA® COMMUNICATION MANAGER SPECIFIC FEATURES ..................................................................59

Increase in SIP Trunks / SIP Agents [8.0] .............................................................................................. 59
16 Digit Extension [8.0] ..................................................................................................................... 60
Native support of J-Series endpoints [8.0] .................................................................................................. 60
Configurable default value of LNCC Button for SIP Station [8.0] ................................................................... 60
Manual upgrades tested from earlier CM releases [8.0] .................................................................................. 61
Enhanced SIP Trunk Signaling on Agent Transfer and conference [8.0] ............................................................. 61
61
61
61
61
61
61
Connection Preserving Migration (CPM) with H.248 Link Recovery for BRI Trunks MM720/721/722 [8.0.1] ........ 61
AMS instance sharing by multiple adopter applications – CM and AWG 3.5.1 (once GA) initially can share AMS [8.0.1]61
Increased Capacities [8.1] ..................................................................................................................... 62
Extend more features to 16-digit dial plan extensions [8.1] ..................................................................... 62
Trunk hook flash support from SIP devices (8.1.1) .............................................................................. 62
62
62
62
62
62
62
62
62
62
................................................................................................................................................... 62
.................................................................................................................................................... 62
Skype for Business SIP Trunk Integration Testing (8.1.1)...................................................................... 62
5.5. NEW COMMON SERVERS SUPPORT– ACP (AVAYA COMMON PLATFORM) 100 SERIES [8.0.1] ............................63
5.6. UTILITY SERVICES REMOVAL FROM THE AVAYAAURA® PLATFORM OFFER AND EQUIVALENT FUNCTIONALITY IN
OTHER PLACES [8.0] ......................................................................................................................................................63
Use of US 7.1.3 with AA8.0 to Provide Capabilities Not provided with AA8.0 ................................................. 64
AADS 7.1.3.1 Firmware Download Capability formerly in Utility Services [8.0] ................................................ 64
64
64
Phone Firmware Download and DHCP Server on S8300 in Branch offices [8.1.1] ............................................... 64
AVP Utilities feature formerly in Utility Services [8.0] ................................................................................. 64
ESD (Enterprise System Directory) Capability Moves to SMGR [8.0] ............................................................. 65
MyPhone - no longer available in AA 8.0 [8.0] ......................................................................................... 65
CDR Collection; replaced by 3rd party/DevConnect Solutions [8.0] .................................................................. 65
5.7. AVAYA AURA® SESSION MANAGER SPECIFIC FEATURES .................................................................................65
SIP Call Preservation on SM Failures [8.0] .............................................................................................. 65
Call Preservation on Network Failure [8.0]............................................................................................... 66
Regular Expression based Adaptation Module For SM Interoperability and Troubleshooting Support [8.0.1] ................ 66
Session Manager Digit and Regular Expression Routing [8.0.1] ...................................................................... 67
Session Manager Support for Multiple Customer and Business Partner Logins [8.0.1] ............................................ 67
Session Manager Call Journaling Server HA [8.0.1] .................................................................................... 67
Crisis Alert Support on SIP Endpoint [8.1] .............................................................................................. 67
No Hold Conference for SIP Devices [8.1] ................................................................................................ 67
68
68

avaya.com
68
68
68
68
68
68
SIP Endpoint Adapter to Selta Endpoints [8.1.1] ...................................................................................... 68
Session Manager Source Based Routing Enhancement for Regex Routes [8.1.1] ............................................ 68
Regex Adaptation Creation and Verification [8.1.1] ............................................................................ 68
Group ID on SIP Devices [8.1.1] .................................................................................................. 68
Ability to support multiple set types for a single user [8.1.1] .................................................................... 68
AN END USER CAN NOW HAVE BOTH A 96X1 AND J-SERIES SET. FOR EXAMPLE, ONE ON THEIR DESK AND A DIFFERENT SET
TYPE AT HOME FOR REMOTE WORKER, IN THIS SITUATION, BUTTON ASSIGNMENTS MADE BY THE USER ON ONE SET ARE ALSO
REFLECTED ON THE OTHER SET AND IN SMGR. ...........................................................................................................68
5.8. AVAYA AURA® SYSTEM MANAGER..................................................................................................................68
System Manager JBoss Infrastructure Update to Wildfly [8.0] ......................................................... 68
SMGR Browsers support [8.1] .............................................................................................................. 70
Software Only offer supported by SDM 8.0 (for IaaS) [8.0] ........................................................................... 70
SDM Enhancements [8.0] ................................................................................................................... 70
SMGR Enhancements in the CM Element Manager [8.0] (in support of new 8.0 features in CM) ........................ 71
SMGR Improvements in Deployment and Installation times [8.0] .................................................................... 71
B199 conference phone native support [8.0.1] ............................................................................................. 71
SMGR Geographic Redundancy Support in mixed Deployments [8.0.1] ............................................................ 71
SMGR IP Office support including IP Office Branch (re-introduction of support)[8.1] ............................................. 72
72
72
72
72
72
72
72
72
72
SMGR can now show and configure J100 SIP button configuration [8.1.1] ................................................. 72
72
72
72
72
72
72
72
72
72
................................................................................................................................................... 72
VMware Console Access for Avaya Appliance via SDM UI [8.1.1] ........................................................ 72
SYSTEM MANAGER ADMINISTRATORS NOW HAVE THE ABILITY TO LAUNCH A SECURE VIRTUAL CONSOLE TO ACCESS THE
VIRTUAL MACHINE FOR AN APPLICATION THAT IS RUNNING ON AN AVP HOST. THIS IS AVAILABLE IN THE SMGR-SDM AND
THE SDM-CLIENT TO PERFORM MAINTENANCE AND TROUBLESHOOTING. ..................................................................72
5.9. APPLICATION ENABLEMENT SERVICES SPECIFIC FEATURES ............................................................................72
AES HA based on VMware Fault Tolerance [8.0] ....................................................................... 72
AES Support (Individual Voice Streams) stereo call recording, 2 streams 1 call [8.0.1] .......................................... 72
CTI control of video enpoints [8.1]............................................................................................... 73
G.722 codec support [8.1] ........................................................................................................... 73

avaya.com
Automated configuration of AES for cloud platforms [8.1] .......................................................... 73

‘Clear’ alarm notification [8.1] ...................................................................................................... 73
73
73
73
73
73
73
Ability to use location field in php file [8.1.1] ............................................................................... 73
5.10. PRESENCE SERVICES SPECIFIC FEATURES ........................................................................................................74
Skype user with Aura® phone - PS publish on-a-call into MS [8.0] ......................................................... 74
Increase Presence Roster Size [8.0] .................................................................................................. 74
PS support for ACLs for externally federated [8.0] .............................................................................. 74
Presence Service update to support Enterprise Lync [8.0] ........................................................................ 74
PS and AMM are now one (AMM functionality added to the PS application) [8.0.1] ................................... 74
Pure Lync/S4B users can see Aura voice “in a call” state [8.0.1] ............................................................. 75
SAN or Amazon S3 service enabled off board attachment storagePure Lync/S4B users can see Aura voice “in a call” state [8.0.1]
76
5.11. WEBLM, WEBLG AND US ENHANCEMENTS ....................................................................................................76
There are no WebLM specific features in 8.0. ..................................................................................... 76
5.12. AVAYA AURA® DEVICE SERVICES ...................................................................................................................76
Capacity and Scalability............................................................................................................... 76
Increase in CM TLS Connections and Trunk Members [8.0] ................................................................. 76
16-Digit Extension [8.0] ............................................................................................................. 76
16-Digit Extension (Phase 2) [8.1] ................................................................................................ 76
Increase SIP Trunks / SIP Agents [8.0] ......................................................................................... 77
5000 SIP Branches [8.1] ............................................................................................................ 77
300k SIP Users, 1M SIP Devices with a single SMGR [8.1] ................................................................ 77
.................................................................................................................................................... 77
................................................................................................................................................... 77
................................................................................................................................................... 77
................................................................................................................................................... 77
................................................................................................................................................... 77
................................................................................................................................................... 77
................................................................................................................................................... 77
CM capacity enhancements around media gateways, trunks and routing [8.1]............................................... 77
5.13. SECURITY.........................................................................................................................................................78
Extended Hostname Validation - Endpoint/SoftClient interfaces [8.0] ..................................................... 78
Restricted Customer Root Access [8.0] ............................................................................................. 78
5.14. STAY CURRENT WITH 3RD PARTY TECHNOLOGY ..............................................................................................79
Browsers supported across solution [8.1] ............................................................................................ 79
Browsers supported across solution [8.0 / 8.0.1] .................................................................................. 79
5.15. MIDSIZE ENTERPRISE (ME) EVOLUTION .........................................................................................................79
6.0 UPGRADING TO AVAYA AURA® 8.1.1 ......................................................................................... 82
6.1. SUPPORTED UPGRADE PATHS TO AVAYA AURA® 8.1.1 ...................................................................................82
6.2. ENTITLED UPGRADES FROM SESSION OR SYSTEM MANAGER R6 OR R7 TO R8 ................................................82
Session Manager ................................................................................................................................ 82
System Manager ................................................................................................................................ 83
6.3. RELEASE NEEDED WHEN UPGRADING SMGR AND SM FROM R6 TO R8 ........................................................83
6.4. UPGRADING YOUR SYSTEM MANAGER TO R8.0.1 WHILE KEEPING SESSION MANAGER AT R6 OR R7 .............83
6.5. SUPPORTING MIXED R6/R7/R8 SESSION MANAGER/BRANCH SESSION MANAGER CONFIGURATIONS...........84

avaya.com
6.6. IMPLICATIONS OF DEVICES REGISTERING ON DIFFERENT VERSIONS OF SESSION MANAGER DURING UPGRADES
84
6.7. UPGRADING SESSION MANAGER R6 TO R8 WHEN COMING FROM EC TOOLS (CS1000) ..................................84
6.8. UPGRADING FROM SYSTEM PLATFORM ON 6.X TO AVP ON AVAYA AURA® 8.1.1. ..........................................85
6.9. UPGRADING FROM AVP 7.X TO AVP 8.1.1 ......................................................................................................87
6.10. IMPORTANT NOTE REGARDING CMM AND AVP UPGRADES TO 8.1.1 ..............................................................87
6.11. MIDSIZE ENTERPRISE (ME) UPGRADES TO RELEASE AURA® R8.....................................................................88
ME R6 upgrade/migration to deploy as Aura® R8. ........................................................................... 88
ME R6 upgrade/migration BTC R8 to deploy as Aura® R7. ............................................................... 88
7.0 PRODUCT SPECIFICATIONS ...................................................................................................... 89
7.1. COMPATIBILITY MATRIX ..................................................................................................................................89
7.2. SOLUTION CAPACITIES AND PERFORMANCE ....................................................................................................89
Avaya Aura® 8.0 Overall Capacities ..................................................................................................... 89
System Manager 8.1.1 Capacities ........................................................................................................... 90
Key Communication Manager 8.1.1 Capacities ........................................................................................... 91
Key Session Manager 8.1.1 Capacities ..................................................................................................... 91
Key Branch Session Manager 8.1.1 Capacities ............................................................................................ 92
Presence Services 8.1.1 Capacities ........................................................................................................... 92
Communication Manager Messaging 7.0.0.1 Capacities ................................................................................. 92
Application Enablement Services 8.1.1 Capacities ....................................................................................... 92
7.3. VIRTUALIZATION RESOURCE PROFILES ...........................................................................................................93
Summary Table of Resource Profiles ......................................................................................................... 93
Session Manager Resource Profile Capacity Changes ..................................................................................... 99
Equinox Soft Client Capacities with AADS Per Session Manager................................................................. 100
System Manager Resource Profile and Server Support Information ................................................................... 100
AES Resource Profile Information ........................................................................................................ 101
7.4. SIZING COMMON SERVERS FOR VIRTUAL APPLIANCE DEPLOYMENTS ..........................................................102
7.5. VMWARE ESXI SOFTWARE SUPPORTED FOR VIRTUALIZED ENVIRONMENT..................................................104
7.6. SUPPORTED BROWSERS ..................................................................................................................................105
7.7. SUPPORTED HARDWARE ................................................................................................................................105
Avaya Common Servers Supported for New Orders for Virtual Appliance Deployments ....................................... 105
Avaya Common Servers Supported for Upgrades to Virtual Appliance (CSR2) .................................................. 111
Avaya Servers Supported for Server Appliance Deployments (Not Virtualized) .................................................. 111
Server Requirements For Software Only Deployments (not virtualized).............................................................. 111
Supported Virtualized Environment Hardware: ........................................................................................ 112
Avaya Embedded Servers ................................................................................................................... 112
Gateways ...................................................................................................................................... 112
Network Performance Requirements for Aura® Applications ....................................................................... 113
8.0 PRODUCT DOCUMENTATION ................................................................................................ 113
8.1. RELEASE NOTES ............................................................................................................................................113
8.2. USER AND SYSTEM DOCUMENTATION ...........................................................................................................113
9.0 AVAYA LEARNING ..................................................................................................................... 114
9.1. AVAYA LEARNING CENTER ...........................................................................................................................114
9.2. TECHNICAL/ KNOWLEDGE TRANSFER ..........................................................................................................126
10.0 PRODUCT ORDERING, LICENSING AND PRICING .............................................................. 127
10.1. BUY TO CURRENT ..........................................................................................................................................128
License Adds to a system that is currently deployed as R7 (not buy to current R8) ........................................ 129
For systems deployed as Aura® R6 or CM R5 and earlier, upgrade to Current to Add capacity ...................... 129
10.2. AVAYA AURA® USER LICENSING ..................................................................................................................130

avaya.com
Suite Licensing ........................................................................................................................ 130

Basic User Licensing; Analog, IPT Basic and IPT Telephony ............................................................... 131
Aura® R8 Suite Entitlement Changes and Detail Description ............................................................. 132
License Mixing Compatibility ...................................................................................................... 140
10.3. AVAYA AURA® LICENSING COMPETITIVE POSITION .....................................................................................140
10.4. AURA® R8 LICENSE FORMAT ........................................................................................................................141
10.5. AVAYA AURA® SESSION MANAGER LICENSING CHANGES, STARTING IN AVAYA AURA® R7 ........................142
System License vs. Connection License ............................................................................................ 142
Summary of the Changes ............................................................................................................ 142
10.6. PRESENCE LICENSING IN AVAYA AURA® 8 ...................................................................................................143
10.7. UPGRADE ADVANTAGE WITH AVAYA AURA® 8 ............................................................................................143
10.8. PRODUCT ORDER CODES AND PRICING ........................................................................................................143
Suites Order Codes and Pricing .................................................................................................... 143
Analog and IPT License (specific use) order Codes and Pricing .............................................................. 145
Avaya Aura® Communication Manager Order Codes and Pricing ......................................................... 146
Avaya Aura® Session Manager Order Codes and Pricing ................................................................... 146
Avaya Aura® System Manager Order Codes and Pricing .................................................................... 148
AVP Utilities Order Codes and Pricing ......................................................................................... 148
Avaya Device Adapter Order Codes and Pricing Order Codes and Pricing ................................................ 149
Avaya Aura® Application Enablement Services Order Codes and Pricing ................................................ 149
Avaya Aura® Presence Services Order Codes and Pricing .................................................................... 151
Avaya Aura® WebLM Order Codes and Pricing ............................................................................. 151
Avaya Aura® Media Server Order Codes and Pricing .................................................................... 151
Appliance Virtualization Platform Order Codes and Pricing ............................................................. 152
AWS (Amazon Web Services) Order Codes and Pricing ................................................................. 153
KVM Order Codes and Pricing ............................................................................................... 153
Avaya Common Server Order Codes and Pricing – CSR2 ............................................................... 154
Avaya Common Server Order Codes and Pricing – CSR3 ............................................................... 154
Avaya Embedded Server Order Codes and Pricing ......................................................................... 154
Avaya Aura® Solution for Midsize Enterprise Optional Migration Disk Replacement Kit Order Codes and Pricing155
10.9. AVAYA ONE SOURCE CONFIGURATOR / AVAYA SOLUTION DESIGNER (A1SC/ASD) ...................................155
Deployment Options for New Orders ............................................................................................. 156
Customer Provided AWS : Choose this to select a AWS Deployment New Virtual Appliance Orders with AVP 156
Embedded Server Orders ............................................................................................................ 157
Ordering the Avaya Aura® Media Server ...................................................................................... 159
Ordering Avaya Aura® System Manager ....................................................................................... 163
Ordering Avaya Aura® Application Enablement Services (AES) ......................................................... 164
Entitled (+U) Upgrades to Avaya Aura® R7 Foundation Suite/Core Suite/Power Suite ............................ 167
Upgrading from System Platform To Virtual Appliance (Avaya Provided Server)........................................ 168
Ordering UPGRADES of Avaya Aura® Session Manager via A1SC/ASD ......................................... 168
Ordering UPGRADES of System Manager 8.1.1 via A1SC/ASD ................................................. 169
11.0 PRODUCT LICENSING PROCESS AND POLICIES .................................................................. 170
11.1. TEMPORARY LICENSE REQUESTS ...................................................................................................................171
11.2. LABORATORY TRIALS .....................................................................................................................................172
Session Manager Lab Trials ....................................................................................................... 172
12.0 SERVICES AND SUPPORT ......................................................................................................... 172
12.1. SERVICES SUPPORT OFFERS ...........................................................................................................................172
12.2. PROFESSIONAL SERVICES ...............................................................................................................................173
12.3. PCN/PSN STRATEGY....................................................................................................................................174
Product Correction Notices (PCNs) ............................................................................................... 174
Product Support Notices (PSNs) .................................................................................................. 174

avaya.com
12.4. TECHNICAL CONSULTING SYSTEM SUPPORT ..................................................................................................174

12.5. ENHANCED SERVICES AVAILABLE .................................................................................................................175
Avaya Managed Services – UC Managed Assist and UC Managed Operate ............................................ 175
Remote Configuration Helpline (RCH) .......................................................................................... 175
Remote Access via Secure Access Link Gateway ................................................................................ 176
Remote Diagnostics via Avaya Diagnostic Server ............................................................................... 176
12.6. WARRANTY ....................................................................................................................................................176
Software Warranty ................................................................................................................... 176
Hardware Warranty ................................................................................................................. 177
Post Warranty Support ............................................................................................................. 177
12.7. LAB EVALUATION ..........................................................................................................................................177
Avaya Labs Field Support ......................................................................................................... 177
13.0 AVAYA AURA® DEVCONNECT ................................................................................................. 177
14.0 CONTACT INFORMATION ....................................................................................................... 178
1.0 About this Document

This Offer Definition is intended for Channel Partners, Distributor-Product Managers, Sales, Engineering, Order
Management, Documentation and Training personnel. It provides the necessary information required to
successfully introduce Avaya Aura® 8.1.1 in a network environment.
This document serves as a comprehensive guide for partner and distributor readiness.
This Avaya Aura® 8.1.1 Offer Definition provides an overview of the Product Components including Material
Codes and Specific features provided. It includes details about all features in Avaya Aura® 8.1.1 as well as
information about installing or upgrading to Avaya Aura® 8.1.1.
 Please ensure you have downloaded the latest version (see Change Control).
1.1. Non-Disclosure
The Avaya non-disclosure processes will be followed for any documentation and information being released to
the End Customer or any type of Channel Partner’s personnel not covered by a contract with Avaya prior to GA.
1.2. Globalization
This document is written as a global document. Unless specifically noted, all information applies across all
theatres. Theatre specific information will be identified using the regional designations listed below.
United States (US)
Caribbean and Latin America and Canada: (AI)
Europe, Middle East and Africa (EMEA)
Asia Pacific (APAC)
2.0 Team Engagement Solutions

Avaya has adopted Engagement as its driving principal. With the rise of mobility, omni-channel communications
and the cloud, the world has moved past collaboration to an era of engagement. Engagement is characterized by
active participation, pervasive collaboration and quality experiences. It results in improved business performance
and increases customer lifetime value. The Avaya Aura® Platform is the foundation of Avaya’s team and
customer engagement solutions. It allows our customers to:
• Create communications solutions that deliver the flexibility and agility that businesses need to grow.

avaya.com
• Achieve reduced total cost of ownership—for the entire engagement environment.

• Build an ecosystem that grows in tandem with a customer’s business.
• Modernize existing communications ecosystems by centralizing and simplifying underlying technology
infrastructures.
• Take advantage of cloud-based delivery and new licensing models, and move cost to an efficient
operating expense model.
Updating Unified Communication for an enterprise brings mobility, availability, and better solutions for enhanced
team engagement.
1. Reduce Total Cost of Ownership
Centralization and consolidation means less hardware, less energy, a smaller footprint, and more features per
dollar invested. The future of collaboration does not have to be cost prohibitive. Investment in engagement
offers a return for any business. Avaya provides alternatives—the right financial model for the right business
solution. Choose from Entitled-based payment options, cloud-based applications, and managed private or
hybrid networks and infrastructures. Avaya's open architecture provides feature and investment options for any
enterprise.
2. Simplify Your Business Model
Select OPEX or CAPEX models, or a mixture of both depending on your needs, move to heterogeneous
infrastructure and an open platform, integrate solutions to extend your business capabilities.
3. Build for the Future
Launch flexible architecture and expandable branches, using deployment models that build on enterprise needs
rather than locations. A true business engagement solution offers a flexible architecture that can easily reduce
costs by moving to SIP, or maintain business growth by introducing corporate branches as easily as desktops.
With Avaya, as your business grows, expands, and reaches out, you’ll find the technology to keep moving into
the future.
2.1. Avaya Aura® Platform

The Avaya Aura® Platform is the foundation for business collaboration that customers need to realize the benefits
of Team Engagement. It delivers next generation of unified communications capabilities to medium, large, and
very large enterprises; including branches. It cost effectively delivers engagement capabilities including voice,
video, messaging, conferencing and application development capabilities across the enterprise regardless of a
user’s location or device of choice.
The Avaya Aura® Platform delivers:
• Simplified deployment of multimedia collaboration applications
• Single user experience across headquarters, branch and on the go
• Dynamic allocation of bandwidth across the enterprise
• Intuitive, cross-enterprise management
• Multilayer security from core to end points
• Comprehensive Redundancy and Virtualization options
• Scalability to 350,000 end points
• Integration into business applications and processes

avaya.com
Aura® Platform Diagram
Communication Manager Overview

Avaya Aura® Communication Manager is the feature server for the Avaya Aura® Platform. It provides the
reliable foundation for voice, video, messaging and collaboration capabilities and delivers a robust and extensive
set of communications capabilities on a highly reliable and highly scalable architecture. Communication
Manager’s multi-protocol support enables it to provide flexible support for analog, digital, H.323 and SIP
telephones and clients, and a wide selection of trunk options. Communication Manager also supports advanced

avaya.com
mobility features, built-in conference calling and contact center applications, E911capabilities and a foundation to
add advanced applications for messaging, conferencing and applications development
Session Manager Overview

Enterprises are adopting Team and Customer Engagement solutions to increase revenue and to reduce expenses
by making their employees more productive and efficient and their customer interactions more satisfying. The
evolution to engagement has changed the communication model from voice only calls to multimedia sessions,
with the ability to change media during a session.
At the heart of the Avaya Aura® Platform, Avaya Aura® Session Manager provides a SIP routing core that
enables a single, common, centralized enterprise wide dial plan, normalizes multi-vendor SIP interoperability,
implements enterprise wide least cost, time of day and alternate routing (around network failures and congestion)
all while managing network bandwidth utilization with integrated call admission control. In addition it provides a
flexible architecture in which services and applications can be extended to users based on their individual profile
and needs verses location.
Session Manager is based on the IP Multimedia Subsystem (IMS) standard which allows functions and
capabilities to be modularized and distributed in the network as functional blocks. These functional blocks are
bound operationally by Session Manager and administratively by System Manager.
System Manager Overview

Avaya Aura® System Manager provides consistent, centralized, browser-accessible administration for the Avaya
Aura® core, network and surrounding applications. With its simple, intuitive and consistent interface, System
Manager allows user data to be entered once and then shared across Avaya Aura® applications. It can also be
tightly integrated with the enterprise IT infrastructure, including identity management, trust management and
enterprise directory integration. Other services provided by System Manager include software management;
reporting; web services API for user and dial plan management; application licensing; central logging and alarm
collection; role based access control; and multi-tenant management.
System Manager is the core management component for all solutions that use the Avaya Aura® base, such as
Engagement OnAvaya Aura® - UCaaS/CCaaS (xCaaS), Customer Engagement solutions (aka Contact Center),
POD FX (aka CPOD) and Breeze solutions.
As related to product positioning, Avaya Aura® System Manager is the go forward management solution for
Unified Communications (UC) solutions. Over the past several releases of System Manager, many of the
customer valued functional capabilities of the Avaya Integrated Management (AIM) applications, have been
transitioned into System Manager. The only remaining AIM application currently in transition is Avaya Site
Administration (ASA). The Performance and Administration Offer and the Network Management Offer within
the AIM portfolio, are already End of Sale (EoS).
Moving forward, Avaya’s intends to converge on a single management solution for both UC and Customer
Engagement Solutions. As part of those objectives, Avaya will be working to address the functional overlap
between System Manager and Control Manager. In the near-term, Avaya has established the following
positioning guidelines when to position System Manager and when to position Control Manager:
1) Use System Manager for a Team Engagement (aka Unified Communications) solutions.
2) Use Control Manager as an overlay to System Manager to manage Customer Engagement (aka Contact
Center) and agent management.
3) In an Engagement OnAvaya Aura® - UCaaS/CCaaS (xCaaS) solution, Control Manager will be layered
on top of System Manager to manage the overall Service Provider environment

avaya.com
The following is a summary of the management positioning and if the preferred management solution is
mandatory or optional.
Offer Focus Preferred Management Tool Comments

Team SMGR (mandatory) Beginning in Avaya Aura®
Engagement; 7.0, SMGR is a mandatory
Avaya Aura® rel solution element.
7.x
Team SMGR (optional)

Engagement; SMGR (mandatory w/ SM, Breeze, PS)
Avaya Aura® rel
6.x
Customer ACM (optional) Traditional Elite stack (Elite
Engagement + SMGR (mandatory) with/without EMC, CMS,
(aka Contact one-X Agent, WFO, EP,
Center) based on outbound)
Avaya Aura® rel
7.x SMGR is required with
Avaya Aura® 7
Customer ACM (optional) Traditional Contact Center
Engagement + SMGR (optional) Elite stack (Elite
(aka Contact + SMGR (mandatory w/ SM, Breeze, PS) with/without EMC, CMS,
Center) For one-X Agent, WFO, EP,
TDM/H323 outbound)
deployments based
on Avaya Aura®
rel 6.x or earlier
Engagement ACM + SMGR (both mandatory) Both ACM + SMGR are
OnAvaya Aura® - always included in the
UCaaS/CCaaS solution.
(xCaaS)
Avaya Aura® Media Server (AAMS) Overview

Prior to Avaya Aura® 7.0, Digital Signal Processing (DSP) resources for audio functionality had been provided
via hardware modules contained in Avaya’s portfolio of media gateway (MG) and port network (PN)
solutions. These resources provide the capabilities necessary to transcode various audio codecs, create
connections, create conferences, play DTMF tones, send and collect digits, source Music on Hold, and play and
record announcements.
Avaya Aura® Media Server (AAMS) has been adopted by Avaya Aura® Communication Manager (CM) and
provides media gateway and port network IP audio-equivalent feature capabilities and more. As a software-based

avaya.com
media server, AAMS can be either virtualized with the Avaya Aura® Platform or run directly on an operating
system.
When compared to media gateway and port network environments, AAMS’s flexible deployment options and
adoption by CM provide a number of benefits, including: greater scale and flexibility, removing proprietary
hardware requirements from SIP-only solutions, high soft DSP/media channel density, and lower Total Cost of
Ownership. In addition, the AAMS adoption by CM provides features not available with media gateways and
port networks, such as: transcoding the G.722 codec, high availability (1+1) configuration, no recording time
limits for announcements, and no practical limits to the number of simultaneous announcement playback
channels.
Communication Manager currently utilizes a subset of AAMS capabilities and both the adoption capabilities as
well as the capabilities of AAMS itself will continue to be enhanced through upcoming releases of
Communication Manager and AAMS.
Key AAMS-CM features include:

• PN/MG-equivalent IP audio functionality
• Transcode G.711, G.729, G.726, G.722 codecs.
• Utilization of AAMS OPUS narrow-band codec capability
• Encryption (AES128, AES256)
• Connectivity between AAMS and: AAMS, MG, PN, IP stations, IP trunks
• Conferencing and Connectivity: Ad-hoc, meet-me (CM ad-hoc limited to 6 speakers,) Group Paging,
Service Observing, Call Recording
• Tone Generation: Call Progress Tones, Multi-National, DTMF
• Tone Detection
• DTMF, Answer Machine
• Sourcing of Announcements and Music on Hold
• Runs on general-purpose hardware, virtualized or directly on an OS
• High channel density: Up to 4000 simultaneous soft DSP/media channels per instance when deployed in a
non-virtualized environment
• Virtualization option (OVA)
• High Availability (1+1) option
• Multiple AAMS instances can support multiple CM instances
• No recording time limits for AAMS Announcements (limited only by AAMS HDD)
• No practical playback channel limits for AAMS Announcements (limited only by number of licensed
media channels and AAMS channel capacity)
• Multi-country tone support via a single AAMS instance
• Streaming Music on Hold from an external source
While AAMS-CM provides many of the media resource capabilities of a G-series media gateway, AAMS is not a
direct replacement for MGs. AAMS and MGs will be sold in parallel and offered as media resource options for
Communication Manager 8.X. There are some customer environments better suiter for AAMS and some
customer environments better suited for the G-series gateways.
A high-level comparison of AAMS-CM and G-series media gateways:

avaya.com
Media Function AAMS-CM G Series Gateway
Basic media resource capabilities: connections,

conferences, tones, play and record √ √
announcements, digit collection
45 min or 250 min (G450)
Announcement Total Recording Time Limits None (up to size of HDD) depending on memory kit used.
60 min per VAL board.
Practically unlimited (up to
Announcement Channel Capacity 63 (31 for port networks)
# purchased channels)
Gateway Function
TDM interfaces for digital, analog stations and
N/A √
trunks
V.150.1 (Modem-over-IP) N/A √
T.38 Fax N/A √
Codecs: G711, G729, G726 √ √
Codecs: G722 (ad hoc conferencing) √
Codecs: OPUS √ √
Maximum DSP/channel count per instance 4000* 320
Other capabilities
Share with multiple CM's √
Multiple instances can service one CM √ √
Survivability in CM environment √ √
Virtualization √
Redundancy √
Capacity 250 AAMSs 250 Gateways
* Non-Virtualized deployment options. Codec and feature mix will affect maximum capacity. Please check the
updated capacities with Spectre and Meltdown fixes.
Note : Legacy PN and GW tone detectors support various other call progress or call classification detection modes
which do not exist on AMS. These modes are generally geared towards TDM networks where answer supervision
is not guaranteed. AMS will be operating in pure SIP or H323 IP environments where the trunk signaling
protocols always provide answer supervision.
Avaya Gateways Overview

Designed to extend the power of Avaya Aura® Communication Manager to all users in the enterprise, Avaya
Gateways address the customer’s need for converged solutions that support both TDM and IP telephony
environments by seamlessly integrating traditional circuit-switched and IP-switched interfaces.

avaya.com
This gives enterprise great flexibility to adapt to changing business needs. Avaya Gateways allow a customer’s
organization to evolve easily from TDM-based telephony to the next generation of IP infrastructures, including
those based on the open SIP (Session Initiation Protocol) standard.
Avaya Gateways are available in compact standalone, stackable, and chassis-based configurations that support
analog, digital, IP PoE, LAN, and WAN interfaces. They are optimized for blended TDM/IP and all IP
environments in distributed enterprises, small remote offices and large campus environments with thousands of
users.
Key Features:
 Interoperable with standards-based data networks to provide maximum flexibility and reduce total
cost of ownership
 Survivability features and options that allow gateways to continue operating even if the primary
server fails or in the event a WAN failure affects communications between the gateway and the
server
 Support multi-protocol environments, maximizing investment protection for enterprises that require
concurrent support of TDM and IP-based telephony
 Redundant system and network options that support high-availability configurations for both TDM
and IP-based solutions
 Designed for distributed networked telephony, extending the benefits of Avaya Aura®
Communication Manager to all enterprise users regardless of location
 Connectivity across any public or private network using a variety of interface options over TDM,
ATM, Ethernet, Frame Relay, or PPP
Application Enablement Services Overview

Avaya Aura® Application Enablement Services (AES) provides a set of Application Programming Interfaces
(APIs), protocols and web services that expose the functionality of Avaya communication solutions to corporate
application developers, 3rd party Independent Software Vendors (ISVs) and system integrators. . Application
Enablement Services provides an open platform for supporting existing applications with current APIs, and will
be the catalyst for creating the next generation of applications and business solutions for our customers. The set
of APIs provided in AE Services include: TSAPI (Telephony Server Applications Programming Interface)/JTAPI
(Java Telephony Applications Programming Interface) Device Media and Call Control API – DMCC (formerly
known as CMAPI, Communication Manager Application Programming Interface), Telephony and System
Management Web Services, CVLAN (Call Visor Local Area Network (LAN), and DLG (DEFINITY LAN
Gateway).
TSAPI provides 3rd party call control services and JTAPI is a client side interface to the TSAPI service. For
TSAPI (and JTAPI) two license type are offered. TSAPI Basic is licensed on a per concurrent user basis and is
intended for applications that monitor or control a station. TSAPI Advanced is licensed per AES server and is
required for advanced call control supporting applications that launch or route calls. TSAPI Advanced is offered
as Small, Medium or Large. See section 10.8.6 for TSAPI Advanced ordering guidance.
AES provides two types of High Availability (HA) namely Geo Redundant High Avaiability (GRHA) and
VMWare Fault Tolerance based HA. With AES 6.3.x End of Sale, customers using Machine Preserving High
Availaibility (MPHA) can opt for GRHA or VMWare FT based HA. For more details, please refer AES HA
whitepaper https://downloads.avaya.com/css/P8/documents/101043964
AES provides Enterprise Wide Licensing (EWL). With enterprise-wide licensing, AE Services
customers are able to purchase any number of licenses and then allocate those licenses to various

avaya.com
AE Servers at their own discretion. This means that AE Services customers are able to pool or
share all AE Services server features, and Rights To Use (RTU) among AE Servers. This applies
only to AE Services features licensed in the AE Services license file and not those licensed in the
Communication Manager license file. For more details, please refer AES EWL whitepaper
https://downloads.avaya.com/css/P8/documents/101042040
Further detail on AES is available in the AES specific product offer document on the Sales Portal:
https://sales.avaya.com/en/pss/uc-dp-avaya-Aura®-application-enablement-services?view=collateral
and in the AES Product Overview and Specification document on the Support Portal:
Presence Services Overview

Avaya Aura® Presence Services collects and disseminates rich presence from Avaya and third party sources
across a diverse set of business environments, enabling users throughout the network to view users availability
and reach them as required across a wide array of communications devices and clients.
Communication Manager Messaging Overview

Avaya Aura® Communication Manager Messaging 7.0.0.1 is still supported for upgrades and is compatible with
the Aura 8.1.1 applications, however it is no longer offered for new sales or expansions and it is no longer a
supported application (EoMS was Aug. 29, 2019). Customers cannot install CMM 7.0.0.1 on a new AVP
8.1.1 Host. The only way to keep CMM in the solution is to have it run on a dedicated server, running
on AVP8.0 (or a prior version of AVP that it was supported on).
Avaya Aura® Communication Manager Messaging application includes a broad set of voice messaging features,
including:
 Call Answer Helps ensure that information and messages can be securely left in a user’s voice mailbox
while they are away from their workplace or on the phone.
 Voice Messaging Users can record a message, address it, and send it to other Communication Manager
Messaging network users.
 Email Client Access Standard internet messaging protocols (IMAP4 and SMTP) support the retrieval of
messages using industry standard email clients, consolidated in an email inbox.
 Outcalling (Call Me) Users can administer the application to outcall to another phone to notify them of
new messages, with time of day and priority parameters.
 Automated Attendants Sophisticated capabilities for customer call handling, custom prerecorded
announcements, and call routing based on caller response to menus and prompts.
WebLM Overview
Avaya provides a Web-based License Manager (WebLM) to manage licenses of one or more Avaya software
products for your organization. WebLM facilitates easy tracking and utilization of licenses. To track and manage
licenses in an organization, WebLM requires a license file from the Avaya Product Licensing and Delivery
System (PLDS). The license file contains information regarding the product, the major release, the licensed

avaya.com
features of the product, and the licensed capacities of each feature that you purchase. After you purchase a
licensed Avaya software product, you must activate the license file for the product in PLDS and install the license
file on the WebLM server. License activations in PLDS require the host ID of the WebLM server for inclusion in
the license file. The host ID of the WebLM server is displayed on the Server Properties page of the WebLM
server.
WebLM can be leveraged as an integrated application within System Manager, or as a standalone

application. Although many WebLM licensed products can leverage either deployment, using System Manager
WebLM enables the centralization of license management functions within the enterprise.
Avaya Aura® Device Services Overview

Avaya Aura® Device Services deliviers a new set of services for Avaya’s next generation of clients and
devices. These services provide a single place in the Avaya Aura® architecture where devices (clients and
endpoints) can store and retrieve data that users would want to see or use, on any device, supporting a common
user experience.
Device Services is deployed co-resident or paired with Avaya Aura® Session Manager and is delivered as a
separate OVA. Device Services functionality operates with Session Managers deployed centrally (Data Center)
and it is not required to be deployed on Branch Session Manager.
Avaya Aura® Device Services supports the following services:

• Enterprise login: Users can log on to their Avaya device using their Enterprise credentials and receive all
of the Avaya Aura® services they are entitled to. No need for the users to remember which Aura®
password and PIN or the credentials they need to access services on Avaya Presence Server, Multimedia
Messaging, Avaya Aura® or Scopia Conferencing
• Dynamic Configuration Service: This new configuration service dynamically generates the set of
configuration parameters necessary to enable automatic bootstrapping of Avaya soft clients by searching
the various Avaya databases, where configuration information is stored, and extracting and presenting
relevant information to the Avaya devices
• Contact Service: This new service simplifies the client experience and provides a standard way of
managing, storing and searching users and the enterprise contacts detail, including picture, and making
them available across all of the user’s devices
• Web Deployment Service: This service brings mobile phone deployment services to Microsoft Windows
and Apple Mac OS environments. When a new device update is available within the customers
environment the user is automatically prompted to retrieve this update
Supported Clients and devices

The following Avaya Client Applications and devices will initially utilize Avaya Aura® Device Services
• Avaya Equinox for Windows
• Avaya Equinox for Mac
• Avaya Equinox for Android
• Avaya Equinox for iOS
• Avaya Equinox for Web (Avaya Cloud Application Link)
• Avaya Vantage (All Glass, Android based desk phone)
• Customer and third party applications written using the Avaya Breeze™ Client SDK
• All future Avaya Client and physical devices

avaya.com
Avaya Device Adapter Overview

Avaya Aura® Device Adapter is an Avaya Breeze based snap in that provides terminal Adaptation (from CS
1000 Stimulus to SIP AST [Avaya SIP]). The SIP integrated terminal adaptation layer allows current NES
UNIStim sets to register to Avaya Aura® Session Manager and receive feature support from Avaya Aura®
Communication Manager. TDM devices, both Analog and Digital, are also supported via use of the MG-
XPEC card, which also resides within the same Inteligent Peripheral Equipment (IPE) shelf.
AVP Utilities
Avaya Aura® AVP Utilities provides features that Appliance Virtualization Platform ( AVP ) requires in
order to be a supportable platform environment- these functions are:
– Services Port (IP Forwarding)
– AVP alarming and log harvesting
– Enabling SSH Access to AVP
AVP Utilities supersedes Utility Services which has been deprecated with Aura® 8.0, with its functionalities
distributed between AVP Utilities , SMGR, and AADS. AVP Utilities is only deployable on top of AVP,
and is essentially the same functionality that was part of Utility Services in the 7.x release lineup.
Utility Services
Avaya Aura® Utility Services has been removed from the the Avaya Aura® Platform solution. See chapter 5 for
details about the software components previously using the Utility Services.
3.0 About Avaya Aura® 8.1.1

Avaya Aura® 8.1.1 is a Feature Pack and the next evolution of Avaya’s core platform for team and customer
engagement solutions. By bringing session based communications to the enterprise, Avaya Aura® makes it
possible to unify media, networks, devices, applications and presence across a common infrastructure allowing
individuals, not technology, to define the engagement experience. This creates an environment where users have
on-demand access to advanced collaboration services and applications that deliver enhanced customer access,
improved employee efficiency and lower total cost of ownership
This singular focus on creating the most collaborative, barrier-free business environments is based on the
following principals:
 Ability for customers with CS 1000 solutions to re-use their endpoints (IP Telephony (UNIStim),
Analog, and Digital)
 Industry leading levels of flexibility, scalability and reliability
 Hard dollar cost benefits for customers through simplification and access savings
 A highly secure solution with an easily configurable hardened mode
 Open standards and 3rd Party solutions integration
 A migration path forward for every customer

avaya.com
3.1. Why Upgrade to Avaya Aura® 8.1.1?

Avaya Aura® 8.1.1 is a Feature Pack of the Avaya Aura® Platform solution. There are numerous new features
in this Feature Pack, as outlined in chapter 5, and it offers many benefits to customers, especially those moving
forward from earlier releases.
This Feature Pack includes the simplification of the Presence and Multimedia Messaging part of the solution
through a merge of the two into a single application (completed in Aura 8.0.1).
Updated Hypervisor
• AVP 8.1.1 is on ESXi 6.5
• Aura 8.1.1 on VE supports ESXi 6.0, 6.5, & 6.7
Updated RHEL support 7.6 (for AVP and software only offer)
SIP Feature Parity (Crisis alert watcher and No-hold conference on SIP endpoints)
Aura Capacity Improvements
• 5000 SIP branches supported by a single SMGR
• 1 Million SIP Devices with a single SMGR.
• The number of SIP Users is increased from 250K to 300K users
• Communication Manager Large Profile capacity increases let you do more with less, simplifying your
administration and network design
• 999 Media Gateways (Up from 250)
• 999 LSPs (Up from 250)
• 999 PRI trunks (Up from 522)
• 40k SIP Trunks (Up from 30k)
• 1750 Signaling Groups (Up from 1000)
• Media Resources can now register to a Stub network region expanding network design choices
Updated to latest versions of Browsers supported

- Internet Explorer 11
- Firefox = 65, 66, & 67
Miscellaneous
• CTI control of video endpoints
• G.722 codec support for HD recording
• Automated configuration of AES for cloud environment
Note: The underlying framework for an upcoming new Avaya Aura® Platform enhancement “Avaya Aura
Distributed Architecture” will be seen in some Release 8.1.1 administration screens and deployment options.
This is applicable to Communication Manager, System Manager and Session Manager.
These fields are for future use only.
Reference the Avaya Aura 8.1.1 Release Notes under the “Whats New” section for details for Communication
Manager, System Manager & Session Manager on the new fields and deployment options that will be visible in
8.1.1, but not active/usable.
Key Benefits of Avaya Aura® 8.1.1:

avaya.com
For customers with CS1000 solutions, the Minor Release offers the ability to re-use their CS1000 digital and
analog endpoints as well as the IP Telephony (UNIStim) endpoints support that was introduced in 8.0. This is
achieved in an Aura® solution through an expansion of the Device Adapter snap-in on Breeze.
Key Benefits of Avaya Aura® 8:

Release 8.0 continues Release 7.0’s benefits of delivering significant improvements to this platform that is the
foundation for Avaya’s Team Engagement solutions:
Re-use of CS1000 IP Telephony endpoints in an Aura® Solution.
Ability for customers to install Aura® applications on their own Redhat Linux Operating systems.
Support for Google Cloud Platform and Microsoft Azure deployment environments.
Lower TCO with a software-based alternative to media gateways
High density flexible soft media server for H.323/SIP
Lower TCO with flexible virtualization on Avaya supplied servers
Ability to grow beyond the Midsize Enterprise solution boundaries, and create fit for purpose configurations
Create software only branch
A SIP based solution with Military grade security that is JITC certified – note that as of Aura 7.1.2, the
requirement to engage APS for system hardening is no longer in place. The hardening procedures have been
significantly simplified and the number of steps required to implement the hardening have been significantly
reduced.
Increased Scale: Support for users with multiple SIP devices at full solution scale for mobility and device choice
A single, centralized management tool to deploy Avaya Aura® applications, and deliver feature/service packs. In
the 7.1.2 Feature Pack, the Solution Deployment Manager (SDM) was enhanced to allow remote deployment of
LSP’s in branches. This will allow cost effective upgrade of remote sites with no site visits
A simpler way to keep the Avaya Aura® solution current
Ability to separate management and non-management network traffic
Innovate with Presence Services as a Snap-in on the Avaya Breeze™
The new Avaya Breeze™ based deployment model provides increased scale and a robust active-active High
Availability option as well as the ability for application developers to access Presence information via API’s.
Additional Security and Supportability Improvements
Support of VMware ESXi 6.5
Support for customer provided KVM hypervisors
Solution can be deployed in AWS or IBM Bluemix environments
Support for capabilities needed for NG911 deployments.
Support for Oceana solution’s need to be able to control service observing via CTI
Support for Malicious Call trace trigger on CM for SIP trunks
WebServices API for automatic license installation on webLM
UCID in SM CDR
Numerous other Feature Enhancements
Key Business Needs Addressed in Avaya Aura® 8.x
Customer Business Need How Avaya Aura® 8 Addresses this Need

Leapfrogging M1/CS1000 customers to Avaya Customer investment protection - no Rip & Replace
Aura®™ and cloud environments

avaya.com

Clear migration path for customers • Migrate and auto provision M1/CS1K digital and
UNIStim (IP) sets
• Support M1 R16+ and all releases of CS1K; does
not require upgrade
• Retain M1/CS1K user experience for commonly
used set features
Value added Avaya Aura®™ features & apps for
M1/CS1 1000 customers
• Equinox Audio/video/web conferencing,
Equinox Client, Click to Call, IM and
Presence
• BYOD-Mobility apps: iOS, Android,
Windows mobile clients with twinning
• Avaya Aura®™: Value add snap-ins via
Breeze
Other added benefits
• Move to an OpEx model
• Clear migration path for customers
Operating System Separation – Ability for Customer procures Redhat Linux and controls the
customers to install Aura® Platform environment.
applications on their own Redhat Operating Customer controls OS patching processes (post Avaya
Systems in Aura® 8.0 verification utilized modules).
Customer can install standard corporate OS image (as long
as it meets Avaya’s published requirements).
Customer has Root Access to the OS environment.
AES Testing and support for VMware Fault In this release AES will support VMWare Fault Tolerance.
Tolerance in Aura® 8.0 This is a great step for customers that are currently using
AES MPHA and didn’t have a path forward to AES 7.0.
These customers can now modernize and achieve
comparable resiliency in a VMWare environment.
There are several Capacity Increases in
Aura® 8 Communication Manager Large Profile capacity
increases let you do more with less, simplifying
your administration and network design [8.1]
• Media Resources can now register to a Stub
network region expanding network design choices

avaya.com
5000 SIP branches supported by a single SMGR

[8.1]
1 Million SIP Devices with a single SMGR.[8.1]
The number of SIP Users is increased from 250K

to 300K users [8.1]
Increase in CM TLS Connections and Trunk

Members [8.0]
 CM TLS Connections to SM from 16 to 28
 CM SIP Trunk Members from 255 to 9999
16-Digit Extension [8.0]

CM 8.0 will primarily enable/ its “engine” (i.e.
call processing ) to support this requirement. CM
8.0 will also provide changes to several
administration forms (not all) on CM to support
administering basic UC features/functionalities
with 16 digit dial plan.
Increase SIP Trunks / SIP Agents [8.0]

With 8.0, CM supports increased CC Elite SIP
Agents from 5k to 10k. CM SIP trunks are also
increased from 24k to 30k (to accommodate the
agent capacities above). All 30k trunks can be
active at one time.
SIP Resiliency
SIP Call Preservation on SM Failures
When the SIP signaling path for a call between two
User Agents is severed because one or more SIP
elements [Session Manager in this case] have gone
down or the network becomes unavailable, the SIP
call is reconstructed at the SIP signalling layer. This
enabless mid-call features to be executed by users
after their call has been moved to their secondary
Session Manager.
Call Preservation on Network Failure

avaya.com

Active SIP calls are preserved and mid-call features
remain available when the device loses connection or if a
failure of the network occurs.
This is a very useful fearture to enable VoIP Mobility
since it allows users to move seamlessly between Wi-
Fi<>4G networks and maintain active calls. It supports call
hand off from Wifi to Cellular DATA networks (both
directions) for Equinox Mobile clients (when available in
the Equinox client later this year).
Google Cloud Platform and Azure in Aura® Aura® Platform applications can be installed in Google
8.0 Cloud Platform and Azure environments.
Note that this utilizes the Operating System Separation
version of the applications.
Spectre and Meltdown vulnerability fixes In addition to the new functionality, Aura® 8.0 also
contains remediation of the Spectre and Meltdown
Vulnerabilities. It is CRITICAL to understand what
needs to be done for all customers upgrading to Aura® 8.0
and to confirm that capacities are understood before
upgrading..
Remediation of Spectre and Meltdown Vulnerabilities
An industry-wide issue was found in the way many
modern microprocessor designs have implemented
speculative execution of instructions (a commonly used
performance optimization). There are 3 primary variants of
the issue and the way the exploitation can occur, and these
exploitations/vulnerabilities are commonly referred to as
Meltdown and Spectre.
For Aura® 8.0 all remediations are included and the

calculations reflect the current server capacities
Applications in the Aura® solution have inclusion of

remediation to Operating System, Hypervisor, and Server
BIOS. In some cases the performance of the applications
can be impacted so it is important to include this
consideration in solution design.
Note:
- There are adjustments to capacities and also to server
specifications for the VE offer that should be considered.
- Avaya is reliant on our suppliers to validate the
effectiveness of their respective Meltdown and Spectre
vulnerability patches.

avaya.com

- Avaya’s test effort is targeted towards reaffirming
product/solution functionality and performance associated
with the deployment of these patches.
- The customer is responsible for implementing, and
the results obtained from, such patches.
Military level security (delivered in Aura® 7.1) The following security focus areas are addressed in this
; extremely secure solution that can be initially release, in compliance with military security standards:
set to normal or hardened mode and then - Password and PIN management
further security tuned from there. - Login and Session Management
- Encryption Enhancements for FIPS compliance
- Security Audit
- Audit Management
- Certificate Management
- System and Application files hardening
- Multifactor Authentication ( PIV & CAC support ) for
SMGR
Improved security across the solution Avaya Aura® continues to expand the coverage of security
(delivered in Aura® 7.0.1) features across Communication Manager (CM), Session
Manager (SM), Media Gateways, Avaya Aura® Media
Server (AAMS) and Phone devices/clients.
Specific enhancements include:
Support for SHA2 signed firmware packages
Support for TLS 1.2 and ability to disable TLS 1.0/1.1
End-to-End Encryption Indicator
AES-256 media encryption for bearer channel
Encryption of bearer control channel (SRTCP)
TLS support in media gateways (G450/G430)
Enhanced certificate management
Note: Please see section 4.6 Security for specific
support/interoperability details.
Support for IPv6 across the Platform solution Avaya Aura® Platform will support IPv6 across the
solution as well as hybrid IPv4/IPv6 deployments.
Flexible deployment options include support The solution can now be deployed in distinct
for Amazon Web Services (AWS) as well as environments:
VMWare, KVM (7.1.1), Nutanix AHV(7.1.1), Customer provided VMWare
HyperV (8.0.1), and avaya provided servers Avaya provided Servers
Amazon Web Servces (AWS)
Nutanix AHV (7.1.1)
Customer provided KVM Hypervisor (7.1.1)
Google Cloud Platform(8.0)
Azure (8.0)
HyperV (8.0.1)

avaya.com

Avaya Aura® can also be deployed in a combination of the
above environments to suit a customer’s growth and
various OPEX and CAPEX financial models.
Support for capabilities needed for NG911 Emergency call sequencing (explicit & implicit)
deployments Allows sequenced application (e.g. Breeze) to insert or
examine PIDF-LO (location info) attachment to
message(s).
Implicit user definitions based on regular expressions
Emergency call identification via Resource-Priority header
Verify SM properly proxies PIDF-LO content and MSRP
SDP
Support for Service Observe and Barge-in Communication Manager Release enables Avaya
features using feature access code through Oceana™ Solution to:
ASAI Perform Service Observe and Barge-in operations on a
Support for Channel Type identification over voice channel.
ASAI to CTI application Add a Service Observer to a call by using Feature Access
Support to drop or disconnect Service Codes.
Observer from call using CTI application Toggle between listen-only and barge-in modes through
over ASAI CTI.
Communication Manager Release supports channel type
identification over ASAI to a CTI application. For
incoming SIP trunk calls, Communication Manager
Identifies the channel type as voice, video, or unknown
when the call:
• Enters a monitored Vector Directory Number
(VDN) or hunt group (skill/split).
• Is monitored and is alerting at a deskphone or
Agent.
With Communication Manager, you can drop or

disconnect a Service Observer from a call using a CTI
application over ASAI
Higher density solution for DSP/Media The new Avaya Aura® Media Server delivers a high soft
Channels that scales without the need for DSP/media channel density (up to 4000* channels per
additional hardware. AAMS instance = reduced footprint)
Solution without recorded announcement This provides a solution with no recorded announcement
playback channel or recording time limits. playback channel limits, and no recording time limits.
Reduced hardware footprint and ability to The new flexible Appliance Virtualization that was
create a “fit for purpose” customer defined introduced with Release 7.0 enables customers to create a
solution. fit for purpose solution, consolidating applications and
reducing the H/W footprint. This reduces CAPEX costs,
particularly for customers upgrading from older releases
with outdated hardware.

avaya.com

Ability to grow beyond the capacity of the The new flexible Appliance Virtualization provides an
Avaya Solution for Midsized Enterprise (ME), evolution path for ME customers who want to grow
and support the full Avaya Aura® Feature set beyond ME boundaries and leverage full scope of Aura®
on my ME solution. resiliency and deployment choices.
Ability to separate management and non- The Out of Band Management feature introduces the
management network traffic to simplify ability to separate management and non-management
network planning and isolate privileged network traffic across two physically and/or logically
administrative interactions from public separated connections
networking traffic.
A single, centralized management tool to The Solution Deployment Manager is a merge of the
deploy Avaya Aura® applications, and deliver System Manager Software Update Manager, Avaya Virtual
feature and service packs. Appliance Manager (AVAM) and System Platform’s
software management capabilities. The resulting merge
creates a single environment in System Manager that
provides centralized software management for
deployments and updates to the suite of Avaya Aura®
applications.
A simpler way to upgrade my Avaya Aura® The Solution Deployment Manager provides a centralized,
solution automated upgrade capability for Communication
Manager, Session Manager and Branch Session Manager.
The primary benefits:
To move from a manual step-by-step procedure local to the
application server to an automated migration procedure.
To eliminate time lost waiting for each next step in the
upgrade-migration process, by using an automated
sequencing of tasks with the application upgrade-migration
events running in the background without manual
intervention.
To move from multiple manual tasks that require human
intervention that can be error prone, to reliable integrated
checks that assess and confirm upgrade-migration
readiness
The Solution Deployment Manager is also capable of
performing up to ten simultaneous upgrade jobs at one
time.
When the System Manager’s Scheduler is used in
conjunction with the Solution Deployment Manager’s
ability to run upgrades-migrations in parallel, a significant
reduction in the time to upgrade-migrate Avaya Aura®
elements can be achieved.
Remote deployment of LSP’s in branches (SDM remote
deploy AVP)

avaya.com

Support for users with multiple SIP devices at Avaya Aura® supports 350k SIP devices providing the
full solution scale for mobility and device ability for users to have multiple devices at scale.
choice The limit has been increased to 1 Million SIP Devices
with a single SMGR (Aura 8.1)
Support for more SIP users in my enterprise Avaya Aura® supports up 250,000 SIP users in a single
network. enterprise network. The number of SIP Users is
increased from 250K to 300K users with Aura 8.1.
AES now offers increased scale of 50k ASAI Notification
Requests and 50k Active Controlling Associations.
Deploy a robust and scalable solution that The new innovative Avaya Breeze™(Avaya Breeze™)
delivers core Presence and IM capabilities based deployment model for Presence Services provides
along with the option to integrate these with increased scale and a robust active-active High
other business applications. Availability option. It also allows customers and/or
application developers to integrate Presence information
into business workflows by leveraging a new set of API’s.
This release adds support for federation via Nextplane as
well as Presence support for Skype for Business. It also
includes multimedia messaging client federation for multi-
user chat with Cisco Jabber, Openfire, or Nextplane.
Extended Manufacturer Software Support Release Policy

Avaya Aura® 8.1 is designated as the Extended Manufacturer Software Support release for the 8.x release stream.
Avaya’s Extended Manufacturer Software Support Policy (EMSSP): offers an additional category of support for
certain releases of products allowing those products to be sold and supported for an extended and predictable
period of time.
Once a release has been designated as EMSS, Avaya will
– Continue to sell the EMSS release for a minimum period of two (2) years and
– Support the release for a minimum of three (3) years from its date of first sale.
(Support meaning design service packs, bug fix, security updates)

avaya.com

avaya.com
3.2. Summary of Features Delivered in Avaya Aura® 8.1.1, 8.1, 8.0.1 and 8.0

avaya.com

avaya.com

avaya.com
3.3. Avaya Aura® 8.1.1 Platform; Product Components

The following products and releases are included in the Avaya Aura® 8.1.1 Solution.
Product Component Release

Avaya Aura® Communication Manager (CM) 8.1.1
Avaya Aura® Session Manager (SM) 8.1.1
Avaya Aura® System Manager (SMGR) 8.1.1
Avaya Aura® Appliance Virtualization Platform (AVP) 8.1.1
Avaya Aura® Presence Services (PS) 8.1.1
Avaya Aura® G430/G450 Media Gateway (BGW) 8.1.1
Avaya Aura® Application Enablement Services (AES) 8.1.1
Avaya WebLM 8.1.1
Avaya Aura® Media Server (AAMS) 8.0.0 SP2
Avaya Aura® Communication Manager Messaging 7.0.0.1
Avaya Aura® Device Services (AADS) 8.0
Avaya Aura® AVP Utilities (AVPU) 8.1.1

avaya.com
(added to solution in 8.0)

Avaya Device Adapter 8.1.1
(added to solution in 8.0)
Avaya Aura® Utility Services (US) (removed from solution in 8.0)
3.4. Avaya Aura® 8.1.1 Deployment Options
Besides the new platforms whose support was introduced in Release 7, Avaya Aura® 8.1.1 offers additional
number of deployment options with the flexibility to meet the needs of every customer.
The section below describes all of the deployment options supported for the Aura® application stack as or Aura®
Release 8.1.1.
Software deployment options

Starting with Release 8.0, Avaya Aura® customers now have four main software packaging options to choose
from offering them much greater flexibility in term of platform they can select to run their Avaya Aura® stack on.
3.4.1.1. Virtualized Environment

Avaya Aura® Virtualized Environment (VE) permits a VMware or a KVM customer to install Avaya Aura®
collaboration features directly onto their VMware/vCenter ( supported as of R6.3) or KVM ( supported as of

avaya.com
R7.1.1 ) infrastructure. Virtualized Environment provides the core applications as a software Appliance
compatible with each respective environment.
VE supports:
• Avaya Aura® users wanting to upgrade to latest release with reduced server
infrastructure
• Avaya Aura® customers needing to expand their system utilizing a virtualized server
platform or combining server and virtualized server solutions
• Greenfield customers, with VMware strategy for data center expansion, and requiring the
latest collaboration solutions for mobility and video
• Greenfield customers, with KVM strategy for data center expansion, and requiring the
latest collaboration solutions for mobility and video
• Brownfield customers cutting the cord with VMWare and migrating their environment
onto a KVM based platform ( RHEV, Nutanix AHV or Openstack )
3.4.1.1.1.IBM BlueMix
Since May 2017 (officially starting with Aura® Release 7.1.1), the Avaya Aura® Plarform applications
have been supporting deployment on the IBM BlueMix infrastructure running VMWare as its
hypervisor. The applications are supported with the exact same characteristics as the Virtualization
Environment deployment option. For deployment on IBM Bluemix, the standard software VMW OVA’s
can be used.
3.4.1.1.2.KVM support
The VE (Virtualization Enablement) offer supports customer provided hypervisors, and has been
traditionally associated with VMWare. As of Release 7.1.1, and continuing with release 8.x, the Aure
core applications ) supports deployment into customer provided KVM hypervisors environments
matching the characterisitcs described below :
• Supported hardware:
Server Hardware used must be on the RedHat supported hardware list for the version of the
hypervisor used and must meet the CPU, memory and other requirements from the Avaya
applications
• Hypervisor support based on 3.10 kernels (e.g. RHEL 7.3)
• Supported Hypervisors / Environments
o RHEV based KVM as linux kernel v3.10 ( ie Rhat 7.x)
o OpenStack environment leveraging KVM based on RHEV
o Nutanix Acropolis as of AOS version 5.1.1
3.4.1.1.2.1. What is Kernel-based Virtual Machine (KVM) ?
 Kernel-based Virtual Machine (KVM) is a virtualization infrastructure for the Linux kernel that turns this
Linux Kernel into a hypervisor and it is to be compared with ESXi in the VMWare world .
 Version of KVM is directly linked with the version of the Linux kernel it runs with
3.4.1.1.2.2. What is Nutanix and AHV ?
Nutanix is (one of) the leader in the high growth hyper converged infrastructure space

avaya.com
Nutanix offers is constituted of multiple components , two of particular relevance to Avaya Aura®
virtualization:
– Nutanix appliances
– Nutanix Acropolis hypervisor ( AHV )
Nutanix AHV is a productised version of KVM and is free to Nutanix customers

AA7.1.x adds support for Aura® UC running on top of Nutanix AHV
Nutanix appliances have been supported with Vsphere as the hypervisor as part of the VE offer pre 7.1.x
In AA8.1.1, the following applications have been developed and validated to support the deployment in the KVM
environments as documented above :
Application Version Packaging
Communication Manager ( Simplex and 8.1.1 KVM OVA or SW only package
Duplex)
Session Manager Including BSM 8.1.1 KVM OVA or SW only package
System Manager 8.1.1 KVM OVA or SW only package
WebLM Standalone 8.1.1 KVM OVA or SW only package
Application Enablement Services 8.1.1 SW only package
Session Border Controller for Enterprise 8.0 KVM OVA or SW only package
Aura® Media Server 8.0.2 SW only package
Diagnostics Server 3.0 SW only package
Presence Services 8.1.1 Snap-in installed on Breeze 3.5
(Breeze 3.5 has a KVM OVA)
Detailed information on how to deploy these applications in a KVM environment can be located in the KVM
deployment guide of each respective application.
The dimensioning in term of footprint and application performances are identical to what the applications have
been offering so far with the VMWare deployment model. As a consequence all footprint information, licensing,
pricing and dimensioning rules apply entirely to a deployment in a KVM or Nutanix environment.

avaya.com
Since there is no standard OVA structure per se in the KVM world like there is for VMWare, for any application
which does not have a SW only offer, Avaya is providing an archive type package destined only for KVM
implementation. These “KVM OVAs” will be identified by carrying a KVM tag in their file name.
Inside these KVM packages or “KVM OVAs”, one will find a Qcow2 disk image to be used in conjunction of the
accompanying deployment guide for the respective application and a text file including the relevant footprint
information that needs to be entered as part of this deployment.
This last point is one of the main difference and change compared to a VMWare deployment for which the OVA
structrue includes all of the necessary settings to setup the Virtual machine dimensions ( CPu, disk, mem ). For a
KVM environment, the virtual machines need to be dimensioned using the information included in the txt file
provided as part of the “KVM OVA”.
3.4.1.2. Amazon Web Services
AWS Deployments
Customers can use Infrastructure As A Service (IaaS) to avoid capital expenditure on hardware purchases by
utilizing the pay per use model. This model is effective alternative for customer owned Data Center. Additionally
IaaS helps the customers to save on ongoing electricity charges, staffing to maintain the infrastructure etc. Many
customers already use IaaS environments for deploying web apps, data apps etc. Amazon Web Services is a
leading cloud computing platform that offers IaaS compute model, hence chosen as the first support IaaS
environment.
Customers can deploy Avaya Aura® 8.1.1 applications into Amazon Web Services (AWS) Environment. There
will be no change in licensing or delivery of the software. Entitled based license option will be available for this
offer. Customers will pay Amazon to avail infrastructure from AWS. Then customers will buy Avaya Aura®
applications and deploy into AWS. This offer will support a limited hybrid deployment (more details in the table
below).
Support for third party AES applications in hybrid deployment model will be evaluated case by case based on
customer need.
The support for CM includes operation when deployed in CM Duplex mode.
Customers will need to deploy Avaya Aura® applications into AWS Virtual Private Cloud (VPC). VPC allows
the creation of a private IP addressing. VPC also provides an additional layer of security at the network layer.
VPC can be connected with the branches using AWS Direct Connect or Virtual Private Network.
Both greenfield and existing customers can utilize the offer. SDM cannot be used for upgrades/migration for the
applications deployed into AWS environment. Migration from VE/AVP deployment to AWD deployment will be
a manual process, for more information refer to AWS deployment guide.
Comprehenvive support for hybrid deployment configuraton will be available. Existing network jitter, delay,
latency requirements for VE deployement will also be applicable for AWS deployment. For more information on
hybrid configuration, refer to the deployment guide.
The support for Aura® in AWS infrastructure includes the ability to have Duplex CM applications running in an
AWS environment.
Note that System Manager-SDM will prevent system administrators from accessing and trying to use any SDM
functional areas that are not supported in an IaaS AWS environment.

avaya.com
Products Release
Following Products/Applications are be supported into AWS
environment (for the indicated releases and newer).
Avaya Aura® Communication Manager (CM) 8.1.1
Avaya Aura® Session Manager (SM) 8.1.1
Avaya Aura® System Manager (SMGR) 8.1.1
Avaya Aura® Application Enablement Services (AES) 8.1.1
Avaya Aura® Media Server (AAMS) 8.0.2
Avaya Aura® Session Boarder Controller 8.0
Avaya Diagnostic Server 3.0
Avaya Aura® Presence Services 8.1.1
Avaya Aura® Web License Manager (WebLM) 8.1.1
Following Products/Applications need to be deployed on-

premises because they are not supported in AWS
environment.
Avaya Aura® G430/G450 Media Gateway (BGW) 8.1.1
G650 port network
Migration from non-AWS Deployments to AWS

Customers that have previously deployed Avaya Aura® 7.x applications and would like to move them to
an AWS infrastructure would follow the same process as defined for moving applications to another
phusical location. The key difference is to make sure you download the AWS version of the
application(s) you are moving since there is a version of the OVAs specifically available for AWS
deployment. Here is an example of the process for a CM move:
• Backup your on premises system
• Load the AWS version into the AWS infrastructure
• Restore the system in AWS, or copy XLN from old server to new (AWS).
3.4.1.3. Customer Provided Operating System and Google Cloud Platform & Microsoft
Azure support
Newly introduced in Release, an OS separated packaging referred to as Software only packaging is now
enabling additional deployment options for Avaya customers.

avaya.com
Ideally, this option could offer the customer the opportunity to deploy into in any virtual environment
by providing its own Operating system virtual machine, as long the Operating system VM and the
platform match requirements and operating specifications as defined per each Avaya application
In practice, Avaya R&D group has identified that solution testing was required to confirm proper
support of the environment and has leveraged this new deployment packaging to deliver , test and
approve full support for two additional new platforms in Aura 8.0 and another platfrom in Aura 8.0.1:
• Google Cloud Platform (8.0)
• Microsoft Azure (8.0)
• Microsoft HyperV (8.0.1)
During the testing, a limitation of the Google Cloud Platform was identified preventing Avaya to claim
support for CM duplex in this environment. The table below summarizes the supported applications in
Release 8.0 for these new two new platforms :
Additional and future platforms support will be added to the solution following this model.
More information can be found about the Operating System separation and platform support can be
found in this section.
Avaya provided Software & Hardware deployment options
3.4.2.1. Virtual Appliance( aka AVP )

Avaya Aura® is available to end-users via a set of Avaya supplied common servers. These Avaya appliances are
pre-packaged with the virtualization software, and delivered to customers ready to run.

avaya.com
In Release 6.x, Avaya uses System Platform to provide virtualization in a number of templates for Avaya Aura®
applications. Starting with Avaya Aura® 7.0 & and continuing with Avaya Aura® 8.x, System Platform is
replaced by the VMware based Appliance Virtualization Platform (AVP.)
This change removes the need for fixed templates and provides customers with the ability to run any combination
of supported applications on Avaya supplied servers, providing them with greater flexibility in scaling their
solutions to individual requirements.
Sales tools, and installation tools are offered to size the solutions to the right sized server hardware and
additionally in Release 8.1.1, the option of re-using server hardware ( CSR2 and CSR3 ) and compute the
associated configuration will also be made available in the online sales tools.
3.4.2.2. Avaya Aura® Solution for Midsize Enterprise (ME)

With the introduction of flexible virtualization on Avaya supplied servers starting in Aura® 7, the Avaya Aura®
Solution for Midsized Enterprise (ME) was no longer offered, this also applies to Aura® R8 and future releases.
Existing ME customers have a 2 step path to deploy as Aura® 8.
• Leveraging Buy to Current, Customers will order their Upgrade to Aura® 8.
• If the intent is to deploy and run as Aura® R7, follow the ME to R7 deployment process.
• If planning to deploy and run as Aura® R8
• Using the customers existing server you must first activate the R7 licensing and upgrade the deployed
system to R7 using the R7 deployment process
• Then activate the Aura® R8 licenseing, upgrade and deploy as Aura® R8 per the R8 upgrade from
R7 process.
3.4.2.3. Pod FX (Formerly CPOD (Collaboration Pod))

Finally, Pod FX offers a turnkey hardware solution for Avaya application and solution offerings. It is evolving to
become ACP (Avaya Converged Platform” with the introduction of the next generation of hardware platforms.
For more detail about the ACP offer, please refer to the following link: https://sales.avaya.com/en/pss/avaya-
converged-platform
Questions about ACP can be sent to the following email address: acpprodmgt@avaya.com
3.4.2.4. Server Appliance (not virtualized)

The Avaya Aura® Media Server is also offered as a Server Appliance which is an appliance offer that is not
virtualized to provide a high capacity solution.

avaya.com
Supported Deployment Options by Application Summary
Software deployment Hardware + SW deployment
Application Customer
Customer IaaS IaaS IaaS IaaS
Provided Software HW
Provided
KVM
IBM
Only appliance
AVP Pod FX1
VMware AWS BlueMix Google Azure
/AHV
Communication with Pod
√ √ √ √ √ √ √ x √
Manager FX
Session
√ √ √ √ √ √ √ x √ “
Manager
System
√ √ √ √ √ √ √ x √ “
Manager
Application
Enablement √ √ √ √ √ √ √ x √ “
Services
Presence
Services (on
√ √ √ √ x x x x √ “
Avaya
Breeze™)
Avaya Device
Adapter
√ √ √ √ x x x x √ “
(on Avaya
Breeze™)
AVP Utilities x x x x x x x x √ x
WebLM √ √ √ √ √ √ √ x √ “
Communication
Manager √ x x x x x x x √ “
Messaging
Media Server √ √ √ √ x x x √ √ “
Device Services √ x √ √ x x x x √ √
Note:
1
Pod FX is being transitioned to “Avaya Converged Platform”.
Software Only = Customer-supplied ( server + Redhat Linux OS) +Avaya supplied Application

avaya.com
4.0 Avaya Aura® 8.1.1
4.1. Overview
Avaya Aura® 8.1.1 Platform is the latest Feature Pack of Avaya’s enterprise communications platform and
continues to build on the core values of the overall solution. In this release, key area of enhancments include;
Support for legacy, Communication Server 1000 IP endpoints to reduce the cost of modernization to the Avaya
Aura® Platform.
Support for additional infrastructure as a service environments for customers looking to stop spending upfront for
hardware but instead, use it on a pay as needed basis.
New deployment options that let customers control the patching of the OS components hosting the Avaya
applications giving them tighther control of their security needs.
SIP call re-construction enabling the recovery of calls blocked from network or hardware failures with both media
and feature access to provide enhance reliability and enable improved wifi to celluarl hand-overs.
Increased capacity and elimination of the separate utility server component to streamline the solution and enable
lower total cost of ownership.
Note: The underlying framework for an upcoming new Avaya Aura® Platform enhancement “Avaya Aura
4.2. Business Partner Value Proposition

Current Market Situation
The Avaya Aura® Platform is designed to serve the needs of service providers and enterprise IT organizations
that are looking to provide voice, text, video, web collaboration, and contact center services across a medium to
large group of subscribers or end-users.
Both service provider and enterprise segments of the market area are mature with the service provider segment
experiencing growth at the expense of the contracting enterprise market. The key attributes for the market are:
• Low total cost of ownership for communciations

• Complete UC and CC solution to their subscribers and end-users
• Secureable infrastucure to protect subscriber and end-user data and services
• Customizeable and supporting a broad range of 3rd party product add-ons and integrations

avaya.com
Market Needs, Trends and Growth

As noted above, we are seeing a general shift in the way communctions are consumed. The traditional model of
purchasing hardware and software licensing, housing it onsite, and doing the management in-house is challenged
due to the large up front cash payments required and the need to hire and maintiain specially skilled staff.
Instead, people are more and wanting to consume communications as a pay-as-needed service that is managed
externally. This is causing the shift of the business from enterprises doing their own thing to service provides
using the solution to support down-stream subscribers. Even enterprises that still want total control over their
solution are looking to shift to a pay-as-you go model by leveraging infrastructure as a service hardware and
usage based licensing.
In addition, security is becoming increasingly important in the both government and commercial segments. The
recent high-profile break-ins are driving this to some extent. But more importantly, it is driven by the increased
risk from the proliferation of attachers and attack mecnamisms.
Value Proposition
Avaya Aura® 8.1 is a Feature Pack that will address the following business imperatives
Increased Scale: With Aura 8.1, we are able to support upto 300,000 users and 1 million devices in a single Aura
deployment. A single SMGR can now support upto 5,000 branches.
Modernization from Legacy Solutions: With Avaya Aura® the migration from the legacy Communication Server
1000 to an advanced Avaya Aura® platform has been significantly simplified. This makes it easier to migration
from older PBX architectures into new, unified communications solutions.
OPEX Migration: With this release, the Avaya Aura® Platform is now supported while running on a range of
pay-as-you go infrastructures including Amazon Web Services, Google Cloud, IBM Cloud, and Microsoft’s
Azure providing even more options for customers that want to leverage pay as you go hardware.
Unparalled Session Management Flexibility: Now you can set up routing decisions based on the identity of the
caller, as well called number and callers location. In addition, you can now use regular expressions to match
when making routing decisions, allowing the flexibility to use anything in the SIP messaging as input to routing
choices. This same regular expression capability can be used to manipulate the SIP messaging with a new
Regular Expression Adaptation module.
Lower TCO : With the rapid and consistent increase in adoption of Avaya Media server in Aura deployments, to
further bring down the TCO, we are enabling sharing of AMS instances between multiple applications. With Aura
8.1, Avaya communication manager and Avaya Aura web gateway (AAWG) can share the resources from same
standalone AMS instance.
Cyber-Security: This release builds on the security mechanisms inserted in the Aura® 7 releases with the new
ability for the service provider or end user running the system to control most of the OS component patching.
This gives them tighter security and a consistent enterprise-wide platform.

avaya.com
Note that Avaya Aura® 8.1 & 8.1.1 Platform includes software to remediate the risk of the Spectre and
Meltdown vulnerabilities in microprocessors that feature speculative execution of instructions (a very
common performance enhancement feature).
The software in this release includes remediation in operating system and hypervisor components. In
some cases the performance of the solution can be impacted so it is important to include this
consideration in design.
Note:
There are adjustments to capacities and also to server specifications for the VE offer that should
be considered.
Avaya is reliant on our suppliers to validate the effectiveness of their respective Meltdown and
Spectre vulnerability patches.
The customer is responsible for implementing, and the results obtained from, such patches.
The customer should be aware that implementing Aura® 8.1.1 result in degraded performance
relative to solutions running on earlier releases.
Competition
Primary competitors to the Avaya Aura® Platform include the Cisco Communications Manager Solution and the
Microsoft Skype For Business Solution.
Cisco:
• High TCO, including server proliferation and energy-hungry phones;
• Lack of advanced features and application capabilities;
• High licensing costs; and
• Poor core and contact center migration capabilities as customers grow.
• Attack Plan: ensure your customer understands the full life cycle costs of a Cisco solution including required
upgrades, hardware and licenses.
Microsoft:
• More complex solution to deploy, manage and own: up to 5x number of servers required versus Avaya;
• High Support costs: Customers are required to buy Software Assurance (25% of the list price of the software);
• Limited core functionality and mobility options;
• No survivable branch office solutions; and
• No native Customer Service capabilities: Aspect or others are required for Contact Center solutions causing
integration and support complexities.
• Attack Plan: probe your customer’s detailed requirements carefully to understand the desired call treatment and
networking requirements to uncover gaps in Microsoft’s capabilities.
Detailed competitive analysis of a comprehensive list of competitors is available on the Avaya Sales Portal. From the Avaya
Sales Portal home page link to Competitive Intelligence on the left navigation to see highlights and summaries of available
content.

avaya.com
Defensible Differentiators
Avaya Aura® is the flagship core communications solution and incorporates the following Defensible Differentiators:
High availability and security – The in-depth multi-level redundancy, fail-over and survivability capabilities of
Avaya Aura® Communication Manager remain unequaled in the marketplace, the full active/active Session
Manager design is leading-edge, and the security, encryption, and software “hardening” provided at every level
across all aspects of Avaya Aura® remain a unique differentiator.
Comprehensive communications features – Avaya Aura® provides many hundreds of essential communications
features developed over decades of responding to the needs of customers around the globe.
Unified Communications strength – Avaya Aura® is complimented by innovative market-leading UC products

including Avaya Aura® Conferencing and the Avaya FlareTM Experience.
Contact Center strength – Avaya is the global market share leader in contact centers, powering tens of thousands
of centers and millions of agents worldwide. Communication Manager has been a key foundation for this success,
and the expanded capabilities of Avaya Aura® are now powering innovative new customer service solutions such as
Intelligent Customer Routing (ICR) that allows enterprise to serve customers everywhere
Open and standards-based – Avaya remains committed to true open standards support and multi-vendor
interoperability
Customization – Avaya Aura® includes and development platform that enables rapid integration and customization
DevConnect ecosystem – Avaya has the most comprehensive developer ecosystem in the communications space,
providing a broad range of choices for customers (understanding that Microsoft and IBM do bring very strong
developer capabilities from their spaces that Avaya can complement).
Backed by extensive professional, support and managed services – Avaya and our Business Partners have the
industry’s most extensive array of services focused completely on enterprise communications. We help customers
get it done.
Partner Business and Strategic Value

Avaya Aura® Platform Release 8.1.1 offers new tools to partners to leverage in their ongoing engagements with existing and
new customers.
Release 8 enables new engagements with the Communication Server 1000 base. This release coupled with the Equinox
Clients and Servers give these clusters a clear and cost effective path to move from legacy communications to a complete
multi-modal communications platform. And with Avaya’s contact center offering, it also gives them access to industry
leading customer service technology. Key new capabilities include support for Communication Server 1000 IP terminals,
emulation of the multiple appearance directory number (MADN) feature, emulation of the MobileX feature, and data base
migration tools. This can all be coupled with Avaya’s Software Investment Protection Program (ASIPP) for attractive
business terms.
Release 8 also enables new engagements with customers in the middle of data center transformation projects. Many of these
customers are looking to get out of the data center business by halting the process of buying and managing lots and lots of
servers. For these customers, the new ability to run in the Google Cloud Platform or Microsoft Azure give them a pay as you
go option for the hardware.

avaya.com
With this release, partners can continue and further engagements with customers on security. Built on all the security
enhancements added in the 7.X stream, this release enables customers to take control of their OS strategy by providing their
own OS for application only packages of software from Avaya. The OS, built to Avaya specifications, can then be managed
and patched according to the company specific security policies.
These new engagement strategies, combined with the ongoing unified communications, mobility, and custom
communications conversations help enable partners to leverage the Avaya Aura® Platform for their business growth.
5.0 Avaya Aura® 8.1.1 Feature Descriptions

The following sections describe the features introduced in Avaya Aura® 8.1.1, 8.1, 8.0.1 and 8.0.
In order to distinguish where various features were introduced, the release number for each feature
highlighted after the feature name (Eg. [8.0] ). In future updates to the 8.x.y stream, this will delineate
release vehicles for the various features.
5.1. Avaya Device Adapter Introduction to enable CS 1000

What is the Device Adapter snap-in?
 Software enables CS1000 customers to re-use UNIStim (IP) phones on Avaya Aura®. Terminal
Adaptation (from CS 1000 Stimulus to SIP AST [Avaya SIP]) is implemented within the SIP integrated
terminal adaptation layer that allows current NES sets to register to Avaya Aura® Session Manager and
receive feature support from Avaya Aura® Communication Manager
 Deployed as a Snap-in on Breeze. Premise or cloud based; Can sit in the core or branch location. Device
Adapter can be installed on up to 50 Breeze nodes in any customer’s solution.
 Retains end user experience for top CS1000 features (including MADN) while moving to Avaya Aura®
 MobileX functionality on Communication Manager EC500 feature
 Enables full access to Avaya Aura® and Equinox capabilities including MDA twinning of CS1000 phone
with Equinox soft clients
 Provides several layers of redundancy
 Migration from CS1000 database to Avaya Aura® via automated ProVision tool
 Not applicable to contact center implementations
Benefits of the Device Adapter snap-in with Avaya Aura®

Customer investment protection- no endpoint Rip & Replace
 Migrate and auto provision M1/CS1000 UNIStim (IP) sets, and CS 1000 Digital and Analog sets.
 Support M1 R16+ and all releases of CS1000; does not require upgrade
 Re-utilize media gateways (future), IPE line-side cards; re-use set wiring
 Retain M1/CS1000 user experience for commonly used set features
Value added Avaya Aura® features
& apps for M1/CS1000 customers
 Equinox Audio/video/web conferencing, Equinox Client,
Click to Call, IM and Presence

avaya.com
 BYOD-Mobility apps: iOS, Android, Windows mobile clients with twinning

 Avaya Aura®: Value add Snap-ins via Breeze
Other added benefits
 Enable migration to SIP trunking from PSTN
(in alignment with Carrier roadmap)
 Move to OpEx licensing model, if desired
 MMail/CallPilot migration to OfficeLinx or AAM
CS 1000 Features Supported

Top Features Supported (Equivalent user experience)
 Making, answering and releasing a basic call
 End to end signaling (DTMF)
 Fixed feature key access - not FFC based
 Context sensitive key access –
idle / offhook / dialed / ringing / active call state
 Set Display - time and date, call timer etc.
 Set Display - calling / called / redirecting name and number
 Transfer - blind as well as consultative
 Ad hoc conference – as per CM implementation
 Call Forward - all calls / busy / no answer
 Caller List / Redial List / Personal Directory
 Release key - disconnect a call
 Hold / retrieve
 Make Set Busy
 Message Waiting Indication
Additional Features Supported (Similar user experience)
 Privacy
 Call Pickup (Directed / Group / Ringing Number)
 Speed Dial
 Call Park and Call Pickup
(an Avaya Breeze Snapin will be used)
 Hot Line - multiple types on CS1K
 Message Waiting Key/Indicator for voice mail
 Ring Again
 Last Number Redial

avaya.com
 Autodial
 Call Waiting
 Multiple Appearance Directory Numbers (MADN)
Key Features
Call Park and Page
 Park incoming calls in a queue from which users pickup calls from wherever they are
 Use your existing paging or notification systems
 Use your existing music, announcements
Multiple Appearance Directory Number (MADN)
 Multiple Appearance Directory Number (MADN)
– A phone number that appears on two or more phones
 Available on Device Adapted sets, as well as current CM sets, such as 96x1 or Equinox client
 96x1, Equinox and Adapted Sets can be part of the same MADN group
 Use Cases:
– Several phones ring when a number is dialed
– Visual indicator when a line is in use – receptionist can see someone is busy before transfer
– Multiple phones in a room have the same number – large lab
– Calls ring in multiple places – faculty member has a lab and office
– Multiple phone numbers (two or more) appear on one phone –

– Assistant has director's extension on phone
– Receptionist has many other people's lines on their phones
Mobile-X like User experience on CM EC500
 Allows Communication Manager mobile users using EC500 to invoke enterprise features on an active call
by dialing the feature access code without putting the ongoing call on hold.
 Provides the current CS1000 feature experience
 Available to all Communication Manager users
 But Remember: Migrating customers can reuse existing phones via the Device Adapter Snap-in AND
twin with Avaya Equinox for a true UC experience.
Avaya Device Adapter Licensing and Deployment

 Avaya Device Adapter Snap-in list price per instance - $1000
 First Avaya Breeze instance is a Suite Entitlement, $0
 Additional Breeze instances, as needed, must be purchased

avaya.com
 Device Adaptor instances are deployed as Breeze Snap-Ins and 2 profiles are offered
1. Profile 2 supports upto 1,000 devices
2. Profile 4 supports upto 5,000 devices
 The Avaya Device Adapter Snap-in will be supported on:
– AVP Shared Servers
– Virtualized Environment (VMware)
– KVM
– Nutanix AHV
– Amazon Web Services
– IBM BlueMix
Device Adapter Languages Supported

 English, French, Swedish, Danish, Norwegian, German, Dutch, Traditional Chinese, Simplified Chinese,
Japanese Kanji, Japanese Katakana, Korean, Arabic, Greek, Hebrew, Portuguese, Czech, Finnish,
Hungarian, Italian, Polish, Spanish, Russian, Latvian, and Turkish.
 Some of these languages are Unicode and available only on certain supported sets. No change from
support when used with a CS1000.
 Some Avaya Aura® languages are not supported by the Device Adapter: Spanish (Latin America),
French (Canada). If one of these languages is configured for the user in the SMGR, the snap-in will map
it to Spanish or French respectively.
Supported UNIStim Sets and Add-on Modules supported (8.0)

Unistim phones supported:
• 1110, 1120, 1140, 1150, 1165, 1210, 1220, 1230, 2001, 2002, 2004, 2007, i2050 Softphone, 2033
Add-on Modules supported:
• For IP Sets (UNIStim): KEM.
• For Digital Sets (future): KBA, DBA, AOM
Detailed list of add-on modules supported on various Phone models:
• 11XX endpoints (IP) GEM (Graphic Expansion Module)
18 physical keys (possibility of 2 pages with SHIFT); max 3 modules
• 12XX series endpoints (IP) 12-key LCD KEM
• 12 physical keys (possibility of 2 pages with SHIFT); max 3 modules
• 12XX series endpoints (IP) 18-key LED KEM
• 18 physical keys; max 2 modules; paper labels
• 20xx series endpoints (IP) 24-key LCD KEM
• 24 physical keys; max 2 modules
Support for Digital and Analog sets (8.0.1)

Digital and Analog sets are now supported with Aura 8.0.1.
Supported digital endpoints:

• 2006, 2008, 2216, 2616,

avaya.com
• 3110, 3310, 3820,

• 3901, 3902, 3903, 3904, 3905
Supported expansion modules:
• Aries (2216|2616) 22-key AOM, 22 physical keys, max 2 modules, paper labels
• 39xx Series Digital Phone 22-key KBA, 22 physical keys, max 2 modules
• 39xx series Digital Phone 8-key DBA, 8 physical keys, max 2 modules
Supported analog endpoints:

• All Rotary and Digitone pulsing
Endpoints not supported:

• IP, Digital and Analog Attendant Consoles (will need to use a native Aura solution)
• IP Conference phone 2033 (will need to use a native Aura solution)
• Fax and Modem (will need to use a native Aura solution)
• IPE Analog and Digital Line Cards

• NT5K02 Flexible Analog Line, 16 ports, with high/low voltage Message Waiting lamp
option:
NT5K02AC (Australia), NT5K02DB (France), NT5K02JC(Denmark),
NT5K02KB (Holland, India, Ireland and Portugal), NT5K02LD (New Zealand),
NT5K02MC (Norway), NT5K02NC (Sweden), NT5K02SB (Iceland and
Turkey)
• NT5K96 Flexible Analog Line Card (XFALC) + a number of localized ones
• NT5D49AA Analog Message Waiting Line Card (Brazil)
• NT7K20 Global Analog Line Card (GALC), with high/low voltage Message Waiting
lamp option
• NT8D09, NT8D09BB Analog Message Waiting Line card
• NTRA04AA Flexible Message Waiting Line Card (China)
• NTRA05AA Flexible Analog Line Card (China)
• NTRA08:NTRA08AA, NTRA08AB Flexible Analog Line Card (China)
• NT8D02 Digital Line card, 32 ports, supported in CS1000E, CS1000M, Meridian 1
• NTDK16 Digital Line card, 48 ports, supported in the Chassis system
• MGC (Media Gateway Controller, NTDW60 and NTDW98)

• Provides a gateway controller for MG1000E IP media gateways in a CS 1000E system. Has two
DB expansion sites that can be installed with DB32, DB96 and DB128 boards
• Daughter Boards
• NTDW62 DSP daughter-board with 32 ports
• MG-XPEC (Media Gateway Extended Peripheral Equipment Controller NTDW20)
• MG-XPEC card replaces the NT8D01 controller card in the controller slot of a NT8D37 IPE
module for CS1000M. Has two on-board DSP DB's providing upto 192 channels
Ordering:
• Use ASIPP to move licences for UNIStim and Digital over to Aura Suite i.e. Core
• US $93 each without PASS+
• Analog devices will require NEW licence US $40 each

avaya.com
• New Aura 8.x Analog Licence Material Code 397108

• No support for Fax and/or Modems so you may need one or more Aura gateways i.e. G450
• MGC and MG-XPEC

• It is required that the CS1000/Meridian 1 system, that is being migrated to the Device Adaptor,
has certain hardware in place prior to migration. To support Analog and Digital/TDM set
migration, MGC or MG-XPEC gateways must be in place to drive the Digital Line Cards, and
only IPE Digital Line cards are supported
• To order these components, access Avaya One Source configurator and select the following
options:
• Create > Product > Merchandise Only > Heritage Nortel Parts > Go > HERITAGE NORTEL >
Merchandise Voice
• In the top section titled "Search for order codes within a chosen portfolio" select UNIFIED
COMMUNICATIONS, enter the required Order Code identified in the Offer Definition and
select Search > Add > Enter Product Code and Quantity > select Add Items to Quote.
FIPS 140-2 Support for both Device Adapter and UNIStim devices(8.1)
In this release support has been added for FIPS 140-2 compliant cryptographic modules.
Addition of MDA (Multiple Device Access) feature to Device Adapter (8.1)

In this release the MDA feature is extended to CS1000 endpoints that are connected through the Device Adapter.
Support for the existing CM CFW (Call-Fwd) feature on Device Adapter, where a phone can
CFW on behalf of another phone (BFS) (8.1.1)
This feature is to provide the last of a group of 3 Boss Secretary functions that were available in CS1000.
The functions are as follows:
1. Monitor Boss State
2. Transfer calls to Boss
3. Perform CFWAC (Call fwd all calls) from Boss to Secretary (ie. existing CM CFW feature where a phone can
CFW on behalf of another phone.
Improve Load Balancer Redundancy Within 1 Breeze Cluster to > 2 Breeze Servers
(8.1.1)
The resiliency of the Device Adapter solution has been impoved. Previously, in a Breeze cluster, only 2 of the
servers could have the roles “Active” and “Standby”. Now, more than 2 servers can have those roles.
Virtual Office (VO) Functionality (8.1.1)
The IP Network-wide Virtual Office feature enables users to log into any IP Phone using their own User ID and
password. This redirects the end user telephone calls and other features to the Virtual Office logged-in IP Phone.
The end users can perform most IP Phone functions exactly as if they were using their regular IP Phone.

avaya.com
Upon logon, the IP Phone unregisters with the Call Server and registers to the Call Server associated with the
given User ID. This can be the same Call Server or another Call Server within the network (with a Gatekeeper).
Tool to determine if ADA phone is CFWAC (Call Forward All Calls) or not (8.1.1)
A tool is now available to determine if a phone on ADA is set to CFWAC (Call Forward All Calls). This will
help customers debug issues in the field with the CFWAC feature.
daHelp command can be used to list all available ADA specific commands (8.1.1)
In addition to the commands documented in the ADA REF GUIDE doc, there is now a command that can be used
to get a list of available ADA commands such as tnInfo, tpsShow, isetShow, electShow, etc.
5.2. Infrastructure Updates

AVP Hypervisor Update [8.1]
AVP (Appliance Virtualization Platform) has been updated to use VMWare ESXi release 6.5. This will ensure
longest support from VMWare for the 8.1 Release which is the EMSSP release. Note that this also aligns with the
newest supported release by the VE offer.
Redhat Enterprise Linux (RHEL) update in Aura applications [8.1]
The Aura platform applications have been updated to use Redhat Enterprise Linux (RHEL) release 7.6. This
will ensure longest support from RedHat for the 8.1 Release which is the EMSSP release.
Latest versions of Browsers supported

Internet Explorer 11
Firefox = 65, 66, & 67
5.3. Operating System Separation for all platform elements and Independence
from Deployment Environments & VE Updates
OS Separation of all AA Platform components [8.0]

avaya.com
Aura® core application ( SM, SMGR, CM, & WebLM ) are now be available as a SW only option
besides the black box VMWare OVAs, the AWS OVA and KVM packaging Avaya Aura® has been
providing so far.
AES, ADS & AAMS have already been supporting this type of implementation prior to Aura® Release
8.
This requirement originated from some of our largest and/or most security conscious customers wishing
to take entire control and responsibility of all of the applications operating systems in their environment.
There several value propositions and benefits delivered by this new functionality introduced with
Release 8:
o No more black box OVA - The Operating system is now owned and the responsibility of the
customer meaning that the customer is now having automatic root access on its system and is
able to install additional 3rd party applications on top of this OS to help with its
administration.
o Enables improved security compliance thru faster OS currenry ( Green list / Red list )
independent from Avaya release cycles.
o From a technology point of view, this is a step toward the future of the architecture opening
the door to future potential containerization of the applications
o Additionally , it also enables Avaya to deliver faster and more cost effectively support for new
platform environments without having to create additional packaging and generate massive
testing overhead.

avaya.com
5.3.1.1. Operating System Currency and Security updates

There are a specified set of pre-requisites that the OS needs to meet and that are described in precise
details in the deployment guides for each respective applications ( CM, SM, SMGR, & WebM )that
must be met in order for theinstallation process to be successful and supported. .
Operating system requirements include such things as:

o Operating system Distribution along with release string such as Red Hat Enterprise Linux 7.4
o Network interface configuration requirements
o Disk partitioning requirements
o Firewall configuration requirements
o Etc.
The deployment guides describes the OVA setup and core linux OS required before starting the
application installation.
A RPM file, specific to each OS separated app and included in its package, and containing the list of the
OS libraries dependencies will need to be invoked for the package to fetch all of the dependencies from
the repository ( configurable) and install them onto the OS virtual machine. This last step will complete
preparing the OS to receive the Avaya application and at this stage, SDM can be utilized to deploy the
Avaya application on top of this OS.
Note : even though the steps above are documented, they are required for the customer or partner to follow.
During the application installation process, SDM will ensure that the OS environment has been properly set per the
documented directives prior to deploying and throw errors/warnings when it detects missing requirement(s).
In order to facilitate customers to maintain their OS current and secure, Avaya will maintain a list of OS
RPMs and the versions it tests and supports. Two lists will be created and kept up to date on a monthly
basis.New update in the content of any of these two lists will be communicated via Product Support
Notice (PSN) announcement.

avaya.com
5.3.1.2. 3rd party SW running on the customer provided OS
As stated previously, another benefit for a customer to provide its own operating system for Avaya apps
to run on, is the fact that this environment will allow deployment and runtime of 3rd party software that
is non Avaya on this OS, typically required by the customer to manage the OS environment.
Such 3rd party application includes usually monitoring, backup or Antivirus software.
The following slide captures the list of 3rd party software tested by Avaya QA and supported – this list
will be updated on an ongoing basis based on the field/customer requirements.. Please check the latest
version maintained on the Avaya support portal.
PSN020360u - Avaya Aura® Software-only Environment Supported Third Party Applications
Additional platform support : Google Cloud Platform and Microsoft Azure [8.0]
Leveraging the delivery from the OS separation feature, The Avaya R&D team has delivered two new platform
support starting with Aura® 8.0:
Google Cloud Platform
Microsoft Azure
The following tables tracks the applications and limitations of these implementations in Aura® 8.0

avaya.com
Both of these environments are only supported thru the usage of OS separated packaging meaning that no specific
software packages has been created for these environments and that the customer or partner will have to provide
its own OS virtual machine in these environments and prep these machines as per what has been described in the
previous feature paragraph to enable the deployment of the Avaya apps in these environments thru SDM.
The capacities and performances remains as what is documented in the respective applications deployment and
admin guides.
Additional platform support : Microsoft HyperV [8.0.1]

Leveraging the delivery from the OS separation feature previously released in 8.0, the HyperV environment
(formerly known as Windows Server Virtualization) is now supported as a deployment environment as of Release
8.0.1.
Further detail about the implementation in Aura® 8.0.1:
- HyperV support is based on Windows Server 2012/2016 datacenter version
- CM, SM, SMGR, AES, WebLM Standalone
The HyperV environment is only supported thru the usage of OS separated packaging meaning that no specific
software packages has been created for these environments and that the customer or partner will have to provide
its own OS virtual machine in these environments and prep these machines as per what has been described in the
previous feature paragraph to enable the deployment of the Avaya apps in these environments thru SDM.
The capacities and performances are documented in the respective applications deployment and admin guides.
Additional Software supported in OS Separated environment [8.0.1]

The following 3rd party software packages have been tested and confirmed compatible with the Aura 8.0.1 OS
separated environment on top of what was previously tested in Aura 8.0.

avaya.com
• McAfee Endpoint Security for Linux Threat Prevention

• Splunk - Enterprise
• Supported on CM, SM, SMGR, AES, WebLM Standalone
 The list of all of the latest supported 3rd party software can be found in thePSN reference PSN020360u on
the technical support site under this link
 See below for the total list of supported 3rd party software and the releases in which they were tested
Category of the tool Name and Version of the tool Supported Avaya Aura Application Comments/Exclusion/Workaround if Any
Symantec Endpoint Protection 14.0.1 MP2 Avaya Aura® Application Enablement Services, Release 8.x
Linux Client EN Avaya Aura® Communication Manager, Release 8.x
Avaya Aura® Session Manager, Release 8.x Tested in AA 8.0 Release
Avaya Aura® System Manager, Release 8.x
AvayaAura® WebLM (Standalone), Release 8.x
TrendMicro Deep Security as a Service on AWS Avaya Aura® Application Enablement Services, Release 8.x
Avaya Aura® Communication Manager, Release 8.x
Avaya Aura® Session Manager, Release 8.x Tested in AA 8.0 Release
McAfee Endpoint Security for Linux Threat Avaya Aura® Application Enablement Services, Release 8.x Tested in 8.0.1
Prevention Avaya Aura® Communication Manager, Release 8.x +D5Important Note for CM -
Version : 10.5.0.1485 Avaya Aura® Session Manager, Release 8.x A default Access Protection rule defined for McAfee Endpoint
DAT Version : 9089.0 Avaya Aura® System Manager, Release 8.x Security 10.5 needs to be disabled
Engine Version : 5900.7806 AvayaAura® WebLM (Standalone), Release 8.x “IDS_AP_RULE_PREVENT_MODIFICATION_PASSWORDFILES_LINUX”.
Security It blocks updates to password/shadow files and CM needs to modify

them when adding/updating CM admin users (via SMI or filesync to
standby machine).
User can follow McAfee documentation mentioned in below link to

disable this rule.
https://docs.mcafee.com/bundle/endpoint-security-10.5.0-threat-
prevention-product-guide-linux/page/GUID-94135CD9-4F0B-4E91-
A21A-C4C735DC9D41.html
Important Note for AES -

If the McAfee Endpoint Protection is already installed and enabled,
the AES installation might fail. Before installing AES, you must
disable the McAfee Endpoint Protection application by using the
following command and install AES
isecav -setapstatus disable
Avaya Aura® Application Enablement Services, Release 8.x
SolarWinds SAM (Server & Application Avaya Aura® Session Manager, Release 8.x Tested in AA 8.0 Release
Monitor) 6.6.1 Avaya Aura® System Manager, Release 8.x
Avaya Aura® Session Manager, Release 8.x
NetScout - Netscout mGeniousOne Version AvayaAura® WebLM (Standalone), Release 8.x
Network Monitoring 6.0.1 (Build 270) for reporting and VStream Tested in AA 8.0 Release
6.0.1 (Build 245)

Splunk Enterprise Avaya Aura® Communication Manager, Release 8.x
Version: 7.2.0 Avaya Aura® Session Manager, Release 8.x Tested in 8.0.1
Build: 8c86330ac18 Avaya Aura® System Manager, Release 8.x
VE updates
As part of Release 8.0 , several updates were made to the Avaya Aura Core applications in regard to the
Virtualization Environment offer (AKA 'VE'). These Core applications are Avaya Aura Communication
Manager, Avaya Aura Session Manager, Avaya Aura Application Enablement Services, Avaya Aura
Presence Services, Avaya Aura System Manager, and Avaya Device Adapter

avaya.com
The first updates relate to extending support for additional deployment options for Avaya Aura 8.0 with VE.
• Distributed Virtual Switch is now supported for all of the Avaya Aura Core Applications
• Usage of Virtual SAN or VSAN is also now officially supported as of Release 8.0 – this
technology has matured to the point where modern VSAN performance exceeds traditional
SANs. As long as the SAN ( virtual or not ) is meeting the Avaya applications' required I/O
performance, as described in the respective deployment guides, it is supported.
• Thin provisioning is also now supported for use with Avaya Aura Core applications - until
now, just thick provisioning was supported. R8 extend this support to Thin disk provisioning
when setting up the virtual machines for OVA deployment. Special care needs to be taken to
ensure that these thin drives do not grow beyond the overall capacity of the storage available
(logs, trace files, temp, etc.). When deploying Avaya Aura Core applications on thin disks,
the customer and/or partner are assuming full responsibility to ensure that these disks are
properly managed to prevent running out of storage space, as this could cause severe
service-impacting situations. SMGR is excluded from the Avaya Aura core list of applications
supporting thin provisioning due to the constantly varying/growing and very high usage of the
storage medium.
One of the major update for VE with Release 8.0 is the fact that running the Avaya Aura Core applications
without server-resource reservations is now permitted. However, this is strictly under the scope defined by
Avaya in the “Application Notes on Best Practices for Reservationless Deployment and Monitoring,” issued
by the Avaya Solution & Interoperability Test Lab. It is nonetheless highly recommended for customers or
partners seeking to run their Avaya UC environment following this approach to engage with their Avaya
account manager and Avaya VE Product Management to ensure that what they are attempting is properly
covered under this framework.
Additionally and as a refresher since this change was originally introduced in the Release 7.x stream, all
Avaya OVAs support for the RedHat OS provided VMWare tools and no longer bundles VMWare tools with
its OVAs.
5.4. Avaya Aura® Communication Manager Specific Features

Increase in SIP Trunks / SIP Agents [8.0]
With Rls 8.0, CM has increased its maximum number of administered trunk capacities from 24,000 to
30,000 (Large System Configuration). Enhancements has been made around SIP signaling group
administration , i.e. a SIP signaling group has the ability to point to a ‘Cluster of Session Managers’.
This has enabled increase in CC Elite SIP Agents capacities.
Please refer CC Elite 8.x offer document for more details posted at
https://sales.avaya.com/en/pss/avaya-Aura®-call-center-elite?view=collateral
With Rls 8.0, below CM capacities has been increased too:

 CM TLS Connections to Session Manager from 16 to 28.

avaya.com
 CM SIP Trunk Members from 255 to 9999 in a SIP trunk group.
Please note , rest of the CM capacities remains unchanged. There has been no increase in the maximum
number of simultaneous calls CM can handle. Also, maximum number of supported simultaneous PSTN
trunks on CM stays at 12,000.
Refer CM 8.x Capacities document posted on https://support.avaya.com for details.
16 Digit Extension [8.0]

The CM4.0 increase to 13 digits was sufficient for many countries, but important markets like Germany
have cities and towns where the full E.164 number is 14 or even 15 digits. Therefore, we are taking one
further step in CM8.0, growing CM to support 16-digit extensions.
As part of this phased deliverable to support 16 digit dial plan on Communication manager, CM 8.0 has
primarily enabled its “engine” (i.e. call processing ). It provides changes to several administration forms
(not all) on CM to support administering basic UC features/functionalities with 16 digit dial plan. Related
System manager forms are also changed to adapt 16 digit dial plan. Forms for UDP , Dial plan analysis ,
dial plan parameters are updated along with changes to call/bridged appearance buttons. Basic station
display changes are also provided. Off-hook and on-hook feature invocation has ben changed to accept
longer extension numbers barring few related to hospitality features.
Existing customers will be able to upgrade without needing to reconfigure translations. Most of the
maintenance forms and reports along with few basic administration forms are adjusted or widened in 8.0.
Call center customers (ex: CC elite) needing 16 digit dial plan support , should wait for complete support
of 16 digit dial plan across CM which is planned in next phase.
Native support of J-Series endpoints [8.0]

Avaya has introduced a range of endpoints called the J100 series. Aura® 8.0 brings in native administration
support for these endpoints in CM.
The Native Support of Endpoints includes Models J129, J169, J169CC, J179, & J179CC. These can be used as
standard UC phones (J129/J169/J179) or CC Elite agents (J169CC/J179CC).
The J169 / J179 firmware implements the following additional functionality (no changes needed on CM for
these):
1. Ability to assign up to 120 buttons as favorites
2. Ability to assign personal labels to every button
3. Ability to assign Contact Groups (similar to Lync)
4. Ability to rearrange feature buttons according to personal preference
NOTE: At this time, there are limitations that cause the recommendation to have a user with MDA not be SM
using both a 96x1 and a J-series endpoint.
Configurable default value of LNCC Button for SIP Station [8.0]

When the LNCC button is added to a SIP station, it is now configurable whether the default value for the LNCC
Button on / off. This addresses some requests to have the LNCC Button set to active when it’s provisioned (no
more calls).

avaya.com
Manual upgrades tested from earlier CM releases [8.0]

For upgrading from earlier releases the following upgrade path has been confirmed to work successfully
• take backup from EMSSP release of CM 3 , CM4 and from CM 5.0.x, 5.1.x
• restore it on a CM 8 system.
The limitations of "translation only" upgrades will apply and are documented as part of "UPGRADE" documentation.
Enhanced SIP Trunk Signaling on Agent Transfer and conference [8.0]

Improvements have been made to the way CM operates in full call model in an Elite environment (for
calls anchored in Breeze). This improvement applies in general but is particularly helpful in an Oceana
CC environment. Calls come into CM over a SIP trunk from a Breeze B2B, and are extended out to
predominantly H.323 Elite agents. If those agents transfer or conference in other Elite agents, the B2B
gets REINVITEs and UPDATEs indicating what has gone on, and in this scenario additional
information has been added in the messages indicating the party or parties now on the call.
The additional data is needed when:
• A call has been routed to an agent (including agent ID)
• A call has been transferred (including list of resulting parties in the call)
• A call has been conferenced (including list of resulting parties in the call)
Connection Preserving Migration (CPM) with H.248 Link Recovery for BRI Trunks
MM720/721/722 [8.0.1]
The Connection Preservation Migration (CPM) and Link Recovery features are being extended in Aura
8.0.1 to include BRI Trunks. The CPM features works along with H.248 Link recovery for almost all
TDM / DSP based calls handled from a H.248 gateway. Meaning stable calls do NOT become dropped
when the H.248 gateway fails over to another controller.
Following are the conditions of this added support:
- Now also supported for BRI trunks based on MM720/721/722 media modules.
- Only applies for BRI trunks that keep Layer 2 up (similar to PRI trunks) and not
for any other type of BRI trunk.
AMS instance sharing by multiple adopter applications – CM and AWG 3.5.1 (once GA)
initially can share AMS [8.0.1]
Multiple adopters applications integrate with AMS to offer various features or functionalities. Each
adopter offers the integration independently and requires a dedicated AAMS instance.
Avaya Aura Communication Manager (CM) and Avaya Aura Web Gateway(AAWG) are among those
multiple adopters.
With Aura 8.0.1, we are enabling the sharing of a standalone AAMS instance between CM 8.0.1 and
AAWG 3.5.1 (once it’s generally available).
The common AAMS measuring unit of resources (MPUs) will be used by Avaya One Source tool to
size the AAMS instance(s).
AAMS High availability is not supported while sharing AAMS between CM and AAWG.

avaya.com
Licensing of adopter applications integration with AAMS , stays unchanged.
Increased Capacities [8.1]

Communication Manager Array and Large Profile capacity increases let you do more with less,
simplifying your administration and network design
• Media Resources can now register to a Stub network region expanding network design
choices
Extend more features to 16-digit dial plan extensions [8.1]

• Hunt Groups
• Listed Directory Numbers
• Coverage Answer Groups
• ELIN (on IP Network Map)
• Abbreviated Dial Buttons (8.0.1)
• Measurements
• Station Set Data
• Usage Reports
• Intra-switch CDR
• Security Violations
Trunk hook flash support from SIP devices (8.1.1)

An agent using a SIP device can now activate a trunk hook flash. This is a feature that was already supported on
H.323 agent sets so now the SIP sets support it. This is an important feature for the E911/NG911 customers that
use this feature in PSAPs.
Skype for Business SIP Trunk Integration Testing (8.1.1)

Testing has been completed with Avaya Aura and Skype for Business to confirm that trunk integration is correctly
working. This testing was done with an SBC between the Session Manager and Skype for Business and without
the SBC. Testing included:
1. PSTN call to/from a SfB client through Aura (using Aura as the PSTN gateway)
2. Voice call to/from SfB client to an Equinox client on Aura – Not encrypted
3. Voice call to/from SfB client to an Equinox client on Aura – Encrypted

avaya.com
5.5. New Common Servers support– ACP (Avaya Common Platform) 100 Series
[8.0.1]
ACP (Avaya Common Platform) is the new server hardware platform that will be used for Appliance
solution (ie. Avaya supplied servers). The 110 & 120 versions are supported by the Aura Platform
starting with the 8.0.1 Feature Pack. There is also a ACP 130 version that is supported as part of the
ACP offering. For new purchases, Avaya Aura® 8.0.1 applications will be shipped with this next
generation server hardware.
The three variants of this server that differ only in the way the software is loaded on the server; the
underlying hardware is the same:
• ACP 110 Series - the ACP version for bare metal software applications
• ACP 120 - the ACP version for AVP hosted software applications
• ACP 130 –Standard VMware version (non-customized). Avaya does not provide tools to
install/upgrade the VMware hypervisor. Apps installed and host managed using vSphere
web client or customer provided vCenter server. Remote upgrade of servers is not
supported (ie. Site visit is required for upgrades).
The server hardware is a Dell Gen 10 servers using Intel Skylake processors. This is the 1U Next
Generation Virtualized Server Platform from Dell.
There is no alternate vendor for this offering at this stage (ie. Avaya is not offering servers from HP as
an alternate as was previously done for the Common Server 2 and 3 platforms).
Note that new orders will continue to ship on CSR3 servers until the stock is depleted. In all cases
Avaya Operations will avoid shipping a mix of CSR3 and ACP servers. If there is a preference as to
CSR3 or ACP servers then please contact Avaya Order Management and it may be possible to
accommodate such a request until the CSR3 stock runs out.
For more detail about the ACP 130 offer, please refer to the following link: https://sales.avaya.com/en/pss/avaya-
converged-platform
Questions about ACP hardware and the ACP offer can be sent to the following email address:
acpprodmgt@avaya.com
5.6. Utility Services removal from the AvayaAura® Platform offer and
Equivalent functionality in other places [8.0]
Co-incident with the GA of the AA8.0 program, Utility Services (US) will no longer be offered. As part
of this deprecation of US, each of the applications currently hosted on US has been placed elsewhere or
will no longer be available.
Below are the applications previously provided by Utility Services and a description of what the state of
each will be going forward.

avaya.com
Use of US 7.1.3 with AA8.0 to Provide Capabilities Not provided with AA8.0
We recognize that not all capabilities provided by US and it’s applications are not available yet with
AA8.0 and if one of these functions is mandatory for a customer, note that a supported configuration
when moving to Avaya Aura® 8.0 would be to migrate all your Aura applications to 8.0, but leave one
server with AVP 7.1.3 and US 7.1.3 to provide the capabilities from the additional applications that
reside on US. US 7.1.3 cannot run on AVP 8.0, so it would need to be on its own server that was still
running AVP 7.1.3. You can also provide a VMware environment for the US 7.1.3, either in a VE
environment or by using the new Avaya ACP 130 server that is pre-loaded with VMware, vs. AVP.
AADS 7.1.3.1 Firmware Download Capability formerly in Utility Services [8.0]

The firmware download capability that has been provided by US allows management and storage of IP Phone
Firmware, configuration files, and backup/restore of phones. These capabilities are supported in AADS for our
Equinox soft client portfolio. With AA8.0 and starting with AADS 7.1.3.1, there is one platform to support both
soft and hard endpoints, thus reducing overall complexity. The management approach for endpoints is consistent
with US, thus no changes are required as to how endpoints are currently managed.
The main difference customers will see with the AADS approach is with branch deployments. US could be
deployed in a branch and firmware download to the local US for download to branch endpoints. Since AADS is
not deployed in branches, customers will have to utilize a third party file server in the branch if they want to
continue with that capability. In addition, Settings File Editing will not be supported, so users will need to
manually edit the settings files. Lastly, as with US 7.1.3, scheduled firmware downloads are not supported.
Phone Firmware Download and DHCP Server on S8300 in Branch offices [8.1.1]
New in this release is the ability to locally update phone firmware in branch offices, which means a single box
branch solution. Customer will have to upload the IP Phone firmware to CM, unzip the files to a specified
directory, type a CLI command to enable IP Phone firmware downloads, reboot phones from CM SAT to initiate
firmware download. If the customer doesn’t already have a DHCP server for their phones, they need to set one up
and configure it to point to the CM http:81/https:411 server as described in the Installing and Administering and
Avaya xxxx IP Phone document. NEW with this release is also official support of the DHCP server on the branch
gateway, so customers could also use that if they do not have a DHCP server already.
This feature is only available on the S8300E server.
AVP Utilities feature formerly in Utility Services [8.0]

“Services Port VM” was the original name for a US Variant that offers the necessary features that Appliance
Virtualization Platform ( AVP ) requires but is not able to support itself- these functions are:
• Services Port (IP Forwarding)
• AVP alarming and log harvesting
• Enabling SSH Access to AVP
In 8.0, these functions are migrating to a new component called AVP Utilities which will be only required and
deployable on top of AVP.
Upon upgrade from 7.x to 8.x, US on AVP will be transformed and updated into AVP Utilities. AVP on VE
should be removed as its functions are deprecated.

avaya.com
ESD (Enterprise System Directory) Capability Moves to SMGR [8.0]

The capability in US was a simple LDAP to WML converter that provided a means of accessing, searching, and
displaying directory information on IP Phones. Many still refer to this as the CM Directory as it was originally on
CM but was transferred to US.
Beginning in AA8.0 this will no longer be available. Instead, customers should use the SMGR LDAP integration
for their search needs. Note with SMGR there is currently only the ability on the deskphones (96x1, J1xx) to
search for contacts IF they are a user that is within SMGR database OR they are assigned as a “private” contact to
a user. However there is no ability with AA8.0 to search for ANY contact in an external LDAP source (for SIP
and h323 users). This capability was available with the ESD as it provided a means to search an external LDAP
source.
Note: Reconfiguring of the network may need to take place and the user experience (users on an H.323
phone) may be different.
MyPhone - no longer available in AA 8.0 [8.0]

In the future this will be replaced by an Avaya Aura® Unified Portal (Future development not available today).
CDR Collection; replaced by 3rd party/DevConnect Solutions [8.0]

The CM CDR collection feature will no longer be available and customers will need to use a 3rd party
application for their CDR processing needs. Please visit the Avaya DevConnect site for approved partners.
5.7. Avaya Aura® Session Manager Specific Features

SIP Call Preservation on SM Failures [8.0]
When the SIP signaling path for a call between two User Agents is severed because one or more SIP
elements {Session Manager in this case] have gone down or the network becomes unavailable, the two
ends of the call (i.e., the two User Agents on either end of the call) cannot exchange signaling messages
anymore. If the problem is in the signaling path only, the two ends may continue to exchange the media
stream. In this state after the failover to the secondary, end users cannot invoke any call feature that
requires signaling message exchange. Traditionally, calls in this state are referred as Connection
Preserved calls. Pre-8.0, this is the level of preservation that is supported in Avaya Aura® for SIP
devices. To ensure the signaling path and media stream are restored in case of a switchover to the
secondary Session Manager, AA8.0 has added support for SIP call reconstruction at the SIP signalling
layer. This enabless mid-call features to be executed by users after their call has been moved to their
secondary Session Manager.
Pre-AA8.0, several elements in the UC and CC portfolio support implementation of the approach using
a Fail Over Domain Group Name (FGDN) to accomplish Call Preservation for SIP trunk routed calls.
Notes/Limitations

avaya.com
 This feature can be administratively enabled/disabled via SMGR.

 This feature is relevant to core SM's and not BSM's.
 Device support is needed for this feature, so check each device to see if it is supported.
 Support for CC Agents is not part of this release and will to be addressed in a future development
NOTE: The SIP Resiliency Feature was tested with Aura core components during the Aura 8.0 development
cycles. However, this feature is not useful until a future time when Avaya SIP clients also support SIP Resiliency.
As a result, it is highly recommended that this feature NOT be enabled on Session Managers in the System
Manager > Elements > Session Manager > Global Settings screen. The checkbox for now should remain
unchecked.
Call Preservation on Network Failure [8.0]

This is a very useful fearture to enable VoIP Mobility since it allows users to move seamlessly between Wi-
Fi<>4G networks and maintain active calls. It supports call hand off from Wifi to Cellular DATA networks (both
directions) for Equinox Mobile clients (when available in the Equinox client later this year).
Active SIP calls are preserved and mid-call features remain available when the device loses connection or if a
failure of the network occurs; if the device can establish an alternate path to the secondary Session Manager
server. Without this feature, the alternative is a manual step where the user must click a button to “use Cellular
Voice network” and the call is then moved to the Cellular voice network
 Equinox Mobile example: Without this feature, VoIP calls fail when mobile users walk out of Wi-Fi into
Cellular 4G coverage (or vis-versa). VoIP Mobility will allow users to move between Wi-Fi<>4G networks
and maintain active calls.
Notes:
 This includes remote workers and is also relevant in contact center environments.
 This requirement is relevant to core SM's and not BSM's.
Regular Expression based Adaptation Module For SM Interoperability and

Troubleshooting Support [8.0.1]
With 8.0.1, you can now use a new adaptation called the Regular-Expression Adaptation Module. This is
available from the SMGR GUI and provides the ability to modify SIP signalling for interoperability and
troubleshooting use cases. Regular Expressions are any strings within the SIP messages. For example, you can
• Filter messages using one or more regular expressions
• Define and assign variables using regular expression
• Adapt messages using regular expressions and variables
The operations that can be used for this manipulation are Modify/Add/Delete.
In addition, with this release you can now utilize multiple Adaptations at a time, versus the previous
limit of having only one adaptation available at time.

avaya.com
Session Manager Digit and Regular Expression Routing [8.0.1]

This release adds nparalled Routing Flexibilityto Session Manager. Now you can set up routing
decisions based on the identity of the caller (sourced based routing), as well as the called number and
callers location. In addition, you can now use regular expressions to match when making routing
decisions, allowing the flexibility to use anything in the SIP messaging as input to routing choices.
• Routing now will have two flavors: digit-based and regular-expression-based
• A new digit-based source criteria has been added to Digit Based Routing
• New regular-expression-based criteria as been added for selecting messages to be routed
• Criteria can be virtually any piece of the message – and are not limited to the
source headers only
Session Manager Support for Multiple Customer and Business Partner Logins [8.0.1]
Session Manager now has the ability to add more than one customer account with a new account type.
In addition, SM accounts now take advantage of SMGRs roles based access for greater control over
what each login can access.
Session Manager Call Journaling Server HA [8.0.1]

Session Manager seamless failover to the secondary Session Manager now includes all Call Journal
(Call Log) information stored in the Primary for SIP devices
Crisis Alert Support on SIP Endpoint [8.1]

With AA8.1, SIP devices can now be the monitoring station for an emergency call. It will work as
follows:
▪ A station is designated as the crisis alert station

▪ When an emergency call is initiated within the area this station is assigned to, then it would
display an alert/notification including information about who/where/when the 911 call was
dialed
▪ It is not something you invoke like MCT but something you administer and is “always on” on a
Crisis alert enabled station.
This feature is to reproduce the implementation we have on our H.323 phones onto SIP endpoints. These
SIP endpoints could either be an actual station or soft attendant client.
Given Equinox attendant is a SIP attendant, it would need this feature to be able to receive crisis alerts
on attendant UIs.
No Hold Conference for SIP Devices [8.1]
No Hold Conference is the ability to use a button press to create a conference without having to put the current
call on hold. This is a particularly critical capability in a system used for a Crisis/Suicide Hotline where the agent

avaya.com
wants to stay connected to the caller and may have the need to bring additional resources into the call. In AA8.1,
a SIP device can now perform a No Hold Conference.
SIP Endpoint Adapter to Selta Endpoints [8.1.1]

In SM 8.1.1 there is an additional Selta SIP adaptation added that will strip Avaya specific headers and
make sure the message size is under 2000 bytes. This will enable the use of Selta Endpoints (a 3rd party
endpoint product) with Aura.
Session Manager Source Based Routing Enhancement for Regex Routes [8.1.1]
In this release, SM Source Based Routing is extended from Digit routing to also be applicable for Regex based
routes.
Regex Adaptation Creation and Verification [8.1.1]
The SMGR GUI has been enhanced to allow administrators be able to start writing an adaptation, pause
and then return to where they were, check the syntax, see flow of changes and the final outcome and
then publish the rule for Regex based adaptations. This includes
1. Syntax validation
2. Use case/flow
3. Save/Publish button
Group ID on SIP Devices [8.1.1]

The GROUP ID, which is set up in System Manager, is now sent to the endpoint. This H.323 feature is now
available for SIP.
Ability to support multiple set types for a single user [8.1.1]
An end user can now have both a 96x1 and J-Series set. For example, one on their desk and a different
set type at home for remote worker, In this situation, button assignments made by the user on one set
are also reflected on the other set and in SMGR.
5.8. Avaya Aura® System Manager

System Manager is a key element in delivering a lower Total Cost of Ownership. System Manager is the central
management system that delivers a set of shared management services and provides a common console for Avaya
Aura® applications and systems. System Manager is the primary management solution for Avaya Aura® and is
therefore required with all Avaya Aura® 8.0.1 deployments.
System Manager JBoss Infrastructure Update to Wildfly [8.0]

The JBOSS application server that is part of SMGR is being updated in this release. The new version of this
software is called Firefly and it offers several benefits.
Firefly is new and therefore it is supported and will remain supported for several years.This is important
because it means we will be using a current version that has many quality and security updates relative to the
much older JBOSS. It also means a much better ongoing security stance since many security fixes are included

avaya.com
and it will continue to receive security updates. Customers that want to ensure that all of their software is fully
supported, including embedded components, will be pleased about this update.
A second benefit to Firefly is that it runs more efficiently and reliably than JBOSS. This will result in quicker
processing by SMGR and also it is expected to address several of the issues that have occurred periodically
regarding stability.
A third benefit is a number of changes that have been made to the System Manager User Interface screens, which
include improved useability and performance and responsiveness improvements. In addition, the technology
update has enabled SMGR to utilize UI mobility options (tablet); to improve UI experiences through improved
scroll bar layout, page layout, drag-and-drop options, and implementation of widgets.
The improvements can be seen in the main System Manager landing page ( see screenshot below), and in several
of the “User Management” User Interface pages.
Improved System Manager Landing Page in 8.0
Other Changes due to upgrade to WildFly 10.1

 Logging configuration
– Earlier in log4j.xml
– Now in standalone.xml
 Startup parameters
– Earlier in run.conf
– Now in standalone.conf
 Server Boot logs
– Earlier in boot.log
– Now merged into server.log

avaya.com
 JAR/EAR Libraries now modularized into various Module directories
SMGR Browsers support [8.1]

• Browsers supported: (older versions of FF and IE are no longer supported)
• Internet Explorer 11
• Firefox 65, 66, and 67
Software Only offer supported by SDM 8.0 (for IaaS) [8.0]

 Supported Platforms
– Google Cloud Platform
– Amazon Web Services
– Microsoft Azure
– Nutanix
– OpenStack
– VMware
– RedHat Virtualization (RHV)
– KVM
 Installation methods
– Command Line (CLI) based Installer
– SDM
SDM Enhancements [8.0]

 Deployment of Software Only offers of AA 8 products
 Upgrades from 7.x VE/AVP to AA 8 Software Only
 Upgrades from AA 6.2.x/6.3.x on VE to AA 8 on VE/AVP/Software Only
 Support for “different box option” for VE to AA 8 on VE upgrades and AVP to AA 8 on AVP
upgrades
 CSR1 and S8300D hardware blocked for upgrade to AA8 on AVP
 Automatic upgrade of Utility Services to AVP Utilities during upgrade from AA 7.x on AVP to
AA 8.0 on AVP 8.0
 Existing functionality updated to support AA 8.0
 Deployment of AA 8.0 OVA on VE/AVP
 Upgrades from AA 7.x VE/AVP to AA 8.0 VE/AVP
 Upgrade AVP 7.x to AVP 8.0

avaya.com
 Upgrade from AA 6.x on SP to AA 8.0 on AVP 8.0

 Upgrade from CM 5.2.1 to CM 8.0 on AVP 8.0
SMGR Enhancements in the CM Element Manager [8.0]

(in support of new 8.0 features in CM)
• Support for Increased SIP Trunks / SIP Agents
• Support for 16-Digit Extension
• Support for Avaya Device Adapter
• Support for MADN/MCA
• Native support of Mercury Models (J129, J169, J169CC, J179, & J179CC)
• Support for SIP Attendant Set Type
• Support for Increased SIP Trunks / SIP Agents
SMGR Improvements in Deployment and Installation times [8.0]
Previous Release SMGR 8.0

Deployment of OVA 35 min 7 min
Migration from 7.x 70 min 30 min
Migration from 6.2.x 90 min 50 min
Application Server 12 min 6 min
restart
B199 conference phone native support [8.0.1]

B199 is the new SIP conference phone that will replace B179 in future; once available it can be
provisioned on SMGR to add the new set type (it will map to an existing set on CM).
SMGR Geographic Redundancy Support in mixed Deployments [8.0.1]

The SMGR Geographic Redundancy feature can now be deployed in a mixed deployment model that
includes AVP, Customer VE, (IaaS, and SW only). In addition, SMGR instances no longer need to be
exactly the same from a server specification point of view as long as at least one instance meets the
minimum required specifications for the deployment.
Example:

avaya.com
- Primary System Manager on AVP

- Secondary System Manager on Customer Provided VMware or in AWS
SMGR IP Office support including IP Office Branch (re-introduction of support)[8.1]

Re-introduction of IPO Support into SMGR so that IPOffice and Aura IPO Branch can again be supported.
The equivalent functionality that was previously supported in SMGR in r7.1.3 and earlier is now again supported
in the Aura Patform solution. Solutions can be upgraded from Aura r7.1.3 to 8.1.
SMGR can now show and configure J100 SIP button configuration [8.1.1]
J100 SIP Deskphones allow the end user to modify feature buttons on the phone screen (e.g. add features/contacts
or move features/contacts). The SMGR administrator can now view the actual button configuration of the
deskphone (including customized button labels). This will allow the administrator to assign communication
manager based telephony features within that overall button configuration of the J100 deskphones. The
administrator can also modify the button configuration of the endpoint and changes done on both ends (SMGR,
deskphone) are reflected on the other end.
VMware Console Access for Avaya Appliance via SDM UI [8.1.1]
System Manager administrators now have the ability to launch a secure virtual console to access the Virtual
Machine for an application that is running on an AVP host. This is available in the SMGR-SDM and the SDM-
Client to perform maintenance and troubleshooting.
5.9. Application Enablement Services Specific Features

AES HA based on VMware Fault Tolerance [8.0]
Supporting VMware Fault Tolerance (FT) provides an increased resilence for AES deployments and adds a
variety to High Avaialibility feature. Customers with their own VMware environment can now add VMware Fault
Tolerance and leverage its capability to provide resilience for their AES deployments in line with VMware Fault
Tolerance recommendations. Customers looking to stay current with AES should consider moving from the
appliance to a VE or IaaS environment where this can be supported.
With AES 6.3.x End of Sale, customers using MPHA with AES 6.3.x can opt for Geo Redundant High
Availaibility (GRHA) available with 7.x or HA with VMWare FT now available in AES 8.0.
For more details, please refer AES HA whitepaper https://downloads.avaya.com/css/P8/documents/101043964
AES Support (Individual Voice Streams) stereo call recording, 2 streams 1 call [8.0.1]
Stereo call recording provides audio separation of the speakers in a call. It could be a stream for each
individual speaker or one stream for a specific speaker and one mixed stream for all other participants.
This enhancement intends to meet industry use cases like real time speech analytics and voice
authentication, biometrics where audio sepraration of speakers is the key requirement.

avaya.com
Vendors and recording applications can now leverage on enhancened DMCC APIs to achieve split
stream recording. AES supports recording applications through DMCC and ASAI/CTI APIs which
direct CM to provide a conferenced media stream of all parties involved in a monitored call toward a
specific recording device.
With this feature an enhanced DMCC API is made available which allows external recording
applications to request split stream recording. These application requests drive new connection
capabilities within CM to generate the desired media streams towards one or more recording devices.
CTI control of video enpoints [8.1]

With AES 8.1, CTI applications can request endpoints to send/receive video streams as additional configuration
parameter. Make call, Answer call, Consultation call and Single step transfer call APIs are enhanced to support
this capability.
G.722 codec support [8.1]

AES 8.1 introduces G.722 codec support for call recording via DMCC applications in Client media mode. This
enables DMCC applications to record end-to-end High Definition Media Stream.
Automated configuration of AES for cloud platforms [8.1]

With 8.1 AE Services can be configured in an automated manner through the command line interface, enabling
seamless configuration to integrate with the cloud infrastructure.
Following command line utilities are provided:
• Switch Connection and CTI link
• Licensing
• Security Database
• Networking Configuration
• Certificate Management
• User Management
• SNMP configuration
‘Clear’ alarm notification [8.1]

AES 8.1 now sends a ‘clear’ alarm notification which clears temporary license error alarms, when the license state
changes from grace period to Normal state. This distinguishes license errors generated between transient state and
network fluctuations.
Ability to use location field in php file [8.1.1]

In AES 8.1.1, customers can modify the location field in the php file.

avaya.com
5.10. Presence Services Specific Features

Skype user with Aura® phone - PS publish on-a-call into MS [8.0]
Allows deployments with hybrid S4B users (S4B user has an Aura® phone). This is a one time paid feature that
will enable the users across the whole enterprise.
Increase Presence Roster Size [8.0]

 Increase Presence Roster Size provides better user experience with clients - this has been requested by
customers with GRIP-10285. Support an average of 50 buddies per user for a maximum of 16K users per
VM.
 Provide an error message or alarm to the system administrator when the total number of buddies on the
system exceeds 800K (16K X 50).
 An error message (alarm) will be provided to the system administrator that takes into account the number
of VMs. So if multiple VMs are deployed in a PS cluster. The error message will be generated when the
number of buddies in the roster exceeds the cluster capacity.
 The PS server can accommodate more than 50 buddies for some users as long as the average on the
system remains at 50.
PS support for ACLs for externally federated [8.0]

 The ability for users to “control or allow” externally federated presence per country specific laws.
 This was implement as follows:
1. If the "acl-handling" attribute is "block" on an external presentity - PS should not attempt to subscribe
to the external user and politely block the watcher by sending it an empty presence.
2. If the "acl-handling" attribute is "prompt" on an external presentity - PS should attempt to subscribe to
the external user and follow usual course of action depending on the response of the external user /
system.
 Note: The behavior is not affected by the ACL policy configured for PS.
Presence Service update to support Enterprise Lync [8.0]

 In the first release of PS Lync/S4B we only supported the “standard” versions of the Microsoft Edge
server version.
 To support larger federations we need to support the “Enterprise” Microsoft Edge server version
Why
 To enable S4B users federation with Aura® PS users
added to the REST API. This saves the clients from having to AADS search themselves.
PS and AMM are now one (AMM functionality added to the PS application) [8.0.1]
• The combined application will be a SNAP-IN on Breeze
• One Snap-in to install and deploy
• Uses Breeze 3.5 +
• Customers will only need to administer a single application instead of two in order to
enable P&IM

avaya.com
• Unofficially referred to as PMM (Presence Multimedia Messaging)

• The combined application will significantly reduce install time
• The combined application will have the advantage on cumulative patching
• Considerably larger capacity 250k users & GEO and HA enabled
• Supports Equinox Clients 3.3+
• Requires Aura 8.0 + SMGR for deployment
• AADS is required for Presence Server 8.0.1 deployments
Pure Lync/S4B users can see Aura voice “in a call” state [8.0.1]

avaya.com
SAN or Amazon S3 service enabled off board attachment storagePure Lync/S4B users
can see Aura voice “in a call” state [8.0.1]
Details:
5.11. WebLM, WebLG and US enhancements

There are no WebLM specific features in 8.0.
5.12. Avaya Aura® Device Services

AADS 8.0 is GA’d on July 25 2019 and should be used with Aura 8.x.
Capacity and Scalability
Increase in CM TLS Connections and Trunk Members [8.0]

 CM TLS Connections to SM from 16 to 28
 CM SIP Trunk Members from 255 to 9999
16-Digit Extension [8.0]

CM 8.0 will primarily enable/ its “engine” (i.e. call processing ) to support this requirement. CM 8.0
will also provide changes to several administration forms (not all) on CM to support administering
basic UC features/functionalities with 16 digit dial plan.
16-Digit Extension (Phase 2) [8.1]

Additional features supported for 12 Digit extensions that are added in this release:

avaya.com
▪ hunt groups,
▪ coverage answer groups,
▪ ELIN,
▪ abbr dial buttons
▪ Listed directory Number
Increase SIP Trunks / SIP Agents [8.0]

With 8.0, CM supports increased CC Elite SIP Agents from 5k to 10k. CM SIP trunks are also
increased from 24k to 30k (to accommodate the agent capacities above). All 30k trunks can be
active at one time.
5000 SIP Branches [8.1]

Avaya Aura now supports up to 5000 SIP branches under a single System Manager. This translates to
support of 5000 BSMs. Note that multiple ASD/A1S designs will be needed to order a system that goes above
999 BSMs.
300k SIP Users, 1M SIP Devices with a single SMGR [8.1]
The number of supported SIP devices increases from 350k to 1M and from 250k users to 300k SIP
users. With the move to 300k users, the assumption is that there is one Equinox soft-client per user, with
a maximum of 300k soft-clients in the configuration.
Starting in AA8.1, a single System Manager supports 1M SIP devices. This is an increase from the 350k
previously supported. In the past there has been a one to one ratio of users to endpoints/devices
registered at any one time. But with the introduction of Multiple Device Access, which allows a single
user to have up to 10 SIP devices registered with a single user license, users will typically have two –
three devices associated with their extension. This quickly eats into the device count and large customers
with over150k users have a difficult time keeping within the current single System Manager limits. This
increase will help alleviate those issues.
CM capacity enhancements around media gateways, trunks and routing [8.1]
The following capacity increases are achieved in CM 8.1 (supported in CM's Large footprint):
Media Gateways – Increase to 999 from previous value of 250

LSPs – Increase to 999 from previous value of 250
PRI – Increase to 999 from previous value of 522
Trunks – Increase to 40k from previous value of 30k
Signaling Groups – Increase to 1750 from previous value of 1000
Core Network Regions – Continue to be 250
Stub Network Regions – continue to be 1,750, but Media Resources can register in the Stub network
region
Route pattern – Increase to 4000.

avaya.com
5.13. Security
In addition to all new security feature enhancements brought throughout the Aura® release 7 cycle, Avaya is now
performing Nessus scans prior to each release of Major, minor and feature pack in order to include updated
RPMs in the shipping release.
Extended Hostname Validation - Endpoint/SoftClient interfaces [8.0]
The Avaya Aura® server/products, when involved in establishing a TLS connection with another
server/product, must validate the identity of the other server base on the received server certificate
during TLS negotiation. The server/product must be able to validate the other server's identity, as carried
in the Common Name (CN) field of the Subject Name or the Subject Alternative Name (SAN) of the
received server certificate in either an IP address or FQDN (Fully Qualified Domain Name) format,
against the IPs or FQDNs received prior to the TLS connection setup (e.g. from the SIP controllers list
received from the SIP REGISTER response or via PPM API). If the IP or FQDN does not match with
the IP or FQDN in the SIP controllers list, the TLS connection should fail, with an alarm sent to the
system admin.
In this release, the TLS handshake of Endpoints and SoftClients (e.g. SM, 96x1 client) is now able to
support FQDN validation as well as IP address validation. All Avaya Aura® product components now
have the capability to validate either FQDN or IP address as presented in the received certificate in TLS
hand shake process.
The mechanism used to convey the SIP controllers list (i.e. from the SIP REGISTER response or PPM
API) now contains the domain name 'in addition to' the IP address of each SIP controller. SIP controller
in this context means the SIP call server(s) or a server peer(s) that the client entity wants to connect to.
The new client supporting EHV will include the server’s name in the SNI (Server Name Indication)
extension of the request. The server, before presenting the certificate, will look for the optional SNI
extension in the message. If it is present, the server will present the certificate that matches with what
specified in the SNI extension. Otherwise, it will present the IP address based certificate by default.
Why
 3rd party CA issued certificates contain FQDN in the CN/SAN field only starting October 1st,
2015, per CAB forum ruling. For backward compatibility reasons, SMGR (as the CA) continues
to support generating certificates with IP addresses in CN/SAN fields. SMGR provides a
configuration option for generating the certificate with either IP address or FQDN in the
certificate's CN/SAN field. This also means Avaya Aura® servers have at least two identity
certificates: one with domain name and another with IP address in the CN/SAN field of the
corresponding certificate for backward compatibility.
Restricted Customer Root Access [8.0]
In 7.1.2, specific OVAs with controlled access were designed to circumvent the issues created with the EASG
introduction and its interaction with root access grant processes. In 8.0, the process is streamlined and instead of
having two OVAs per app- one with root access enabled and another without, we have only one OVA which
enables the installer to select whether he/she wants root access enabled during the install process.

avaya.com
 When Yes is selected , a legal must-read message pop up will then be presented , and will need to be
acknowledged and agreed to before proceeding to install. This legal text includes a note indicating that
this, unlike the SW only deployment method, does not give the right to the customer to install any SW or
modify the OS provided by Avaya without Avaya prior written consent, or void their warranty/support if
they were to do so.
 If No is selected, then the install will proceed normally.
Any OVA based system with root access enabled will log this information, specific SNMP trap/alarm and/or
zzovide a notification in SMGR so Avaya support personnel can easily and quickly identify that a system
they are connecting to has root access enabled.
Note:
 This is only applicable for VMW OVA deployment – KVM or AWS customers requiring root access will
require a site visit
5.14. Stay current with 3rd party Technology

Browsers supported across solution [8.1]
• Browsers supported :
• Firefox 65, 66, & 67
Browsers supported across solution [8.0 / 8.0.1]

• Browsers supported:
• Firefox 59, 60, and 61
5.15. Midsize Enterprise (ME) Evolution

Avaya Aura® Solution for Midsize Enterprise (ME) R6 is EoS and EoMS. The ME template offer is not
available on Aura® R7, Aura® R8 or future releases. ME customers can now migrate to standard Avaya Aura®
deployment solutions.
 Migration to Aura® R8 is a 2-step process; first to Aura® R7 and then up to Aura® R8.
The full upgrade to Aura® R8 may require additional server/application distribution to manage the Aura® 8
software and customer business capacity needs
• It may not be possible to fil all the ME applications on a single Servcier for R8 and forward
• Common Server R1 (including ME CSR1) is not supported on R8 so a new server or virtual
application deployement would be required
As with all upgrades, customers will order their upgrade to Aura® R8 but can choose to deploy and run as Aura®
R7 or Aura® R8.

avaya.com
 ME Common Server R1 (CSR1) HP DL360G7 is not supported on R8, this would need to be
replaced by upgrading to a Virtual Environment deployment or purchase of supported application servers
from Avaya.
Benefits of migrating ME installed base customers to Aura® R7/8

 No longer a fixed mix of applications, can support customer selected applications
 Ability to add other servers for applications such as AES, SM
 Ability to scale beyond the current 2400 user/ 1000 CC Elite boundary (this may require
incremental servers and/or redistribution of application to balance capacity to scale)
 Ability to incorporate application level redundancy for the applications that support this such as
Communication Manager, Session Manager, System Manager, Presence Services and AES.
 Uninterrupted / Service Continuity HA for Communication Manager/ CC Elite and Session
Manager and Presence Services Currently ME HA has a minimum 10 minute service interruption
 Full alignment with the overall Aura® roadmap of capabilities and timing
* may require incremental servers and/or redistribution of application to balance capacity to scale and application
deployment choices.
See below for some changes to be aware of when migrating ME / ME HA to R7/8:

• ME HA solutions: As the ME template migrates and the applications are split into individual Avaya Aura®
application instances, they also take on the High Availability options of the individual applications at the
Release 7 level.
In many cases this offers greater resiliency options than the ME FRHA solution. With the exception of CMM
and AES the other application HA solutions are offered to ME HA migrating customers at no additional price.
The specifics for CMM and AES are per below:
- CMM: In Release 6, CMM benefitted inside the ME template from the FRHA capabilities of the
System Platform. CMM, as a standard application offer is available in Simplex (non HA) only and
therefore upon migration to R7, CMM will also revert to standard available Simplex (No HA).
- AES: AES HA offering was simplified in Aura® R7 to the Geo Redundant HA. ME HA customers
migrating to Avaya Aura® 7/8 and wishing to retain their AES HA, will pay the uplift charges to
AES R7 FRHA to GRHA UPG/UPL Large.
• Migration Down Time: There may be considerable migration downtime in the initial step to migration to R7
as the full ME application template is offline during the upgrade. Once migrated to R7, the upgrade to R8
follows the Aura® R8 upgrade timing. To minimize downtime for the first step migration to R7 the following
options are available
• R7 ME Disk Replacement Kit (There is not a R8 ME Migration Disk kit, you would use the R7
kit to take the ME to R7 and then standard R7 to R8 upgrade to move to R8 as the destination
release.) This kit will have 4 ME replacement hard drives pre-loaded with the R7 and AVP. Once
the data on the installed ME is backed up, the existing disks will be replaced with the kit, the R7
applications deployed and the backup’s then restored. This reduces the system downtime.
• ME Systems with HA may leverage the standby server to pre-stage Release 7
Limitation: Customer would need to agree to not having a HA solution until migration was
completed

avaya.com

avaya.com
6.0 Upgrading to Avaya Aura® 8.1.1

6.1. Supported Upgrade Paths to Avaya Aura® 8.1.1
Beginning in release 8.0.1, Avaya Aura® supports new versions of Vsphere and also KVM, so any Avaya Aura®
Core application running in earlier Virtualized Environments will need to apply the following sequence of
upgrade steps in order to install an Avaya Aura® 8.1.1 application:
For a VMWare based environment ( since Vsphere 6.0, 6.5, and 6.7 support predate 8.1.1 ):
1. Step 1 - Upgrade the Avaya Aura® applications in question to 8.1.1
2. Step 2 – Upgrade the VMW underlying Hypervisor from previous version to ESXi6.7
For a KVM based environment ( see the complete list of such environment in the section of this document ) :
1. Step 1 - Manually backup the Avaya Aura® applications involved following the process as
described in the documentation for each application.
2. Step 2 – Deploy Aura® 8.1.1 in your KVM environment following the KVM deployment guides in
for each respective application
3. Step 3 – Restore the application Data into this new Aura® environment
For G4xx, the Gateway hardware will have to be first upgraded to 7.1 at a minimum ( build version 7.1.0.2) prior
to upgrade to 8.1.1. once the proper build is loaded onto the hardware, user will be required to enable/disable
EASG and only after this step, will the system allow for the AA8.1.1 software to be downloaded and installed on
the gateway. In summary there are 3 steps to upgrade a G4XX to AA8.1.1 :
1. G4xx will require first upgrade to 7.1 ( Build version 7.1.0.2)
– Any attempt to upgrade the G4xx straight to 8.1.1 will fail with an “Incompatible
software image for this type of device “
2. Required Confirmation to Enable or Disable Avaya Logins
3. Download and Install R8.1.1 on G4xx
6.2. Entitled Upgrades from Session or System Manager R6 or R7 to R8

Session Manager
For every upgrade from Session Manager R6 or R7 to R8, an upgrade design and order must be
generated in A1SC to make sure the customer has all the required material codes that are needed.

avaya.com
IMPORTANT NOTE: For entitled upgrades from SM R6 or R7 to R8, material code 397951 - SM R8
SYSTEM UPG ENTL will be output. However, since SM R7 did not have Upgrade Advantage codes
created, users may assume that this code will not be able to be upgraded to SM R8. However, if the
customer previously had any Software Support + Upgrades (SSU) OR Upgrade Advantage (UA) for
Aura R6 or R7 on the customer’s contract, then PLDS is set up to allow the entitled upgrade to SM R8.
Additional Information on PLDS (this applies for upgrades from R6 to R7 and R6/R7 to R8): When the
entitled SM material code is on the order (i.e., 397951 - SM R8 SYSTEM UPG ENTL (this is the
equivalent of 380006 - AURA R7 SM SYSTEM UPG ENTL), this code does not flow to PLDS,
because PLDS does not require it for the entitled upgrade (these codes are required mainly for the
customer’s records).
PLDS is set up with Upgrade Advantage entitlements. For example, at the functional location (FL), if
the customer record contains one of these entitlements below they will be able to execute the entitled
(pre-paid) upgrade.
- SM_PP_SA_UPGRADE - Prepaid Upgrade Entitlement for Session Manager OR
- SM_PP_UPGRADE - Prepaid Upgrade Entitlement for Session Manager
NOTE: For customers with Session Manager R6, after the upgrade order has been processed, existing
SIP Connections and/or User licenses may need to be activated and upgraded in PLDS to provide the
Session Manager system license.
System Manager
NOTE: For upgrades from SMGR R7 to SMGR R8, PLDS may not have these SMGR R6 or SMGR R7
licenses on the customer’s records:
389638 - AURA R6 SYSTEM MANAGER R7 LIC
389637 - AURA R7 SYSTEM MANAGER R7 LIC
389687 - SYSTEM MANAGER R7 REDUNDANCY LIC
In these instances, please open an ITSS ticket to have these codes added to the customer’s records by the
Tier 2 PLDS helpdesk.
6.3. Release Needed When Upgrading SMGR and SM from R6 to R8

Prior to upgrading the SMGR to R8, the SM R6 should be upgraded to SM 6.3.22 or above. See PSN:
https://downloads.avaya.com/css/P8/documents/100171014 for details.
6.4. Upgrading Your System Manager to R8.0.1 While Keeping Session Manager
at R6 or R7
It is a supported upgrade path to upgrade the System Manager to R8, potentially to support an Avaya Breeze™
based solution, but keep your Session Manager Core at R6 or R7. Please note in this scenario an R6 or R7 license
file will continue work, but it will have to have be a regenerated R6 or R7 license file since the System Manager
R8 installation/upgrade changes the WebLM Host Id.

avaya.com
6.5. Supporting Mixed R6/R7/R8 Session Manager/Branch Session Manager

Configurations
SM 6.x, SM 7.x, & SM 8.x systems can both be managed by a single System Manager for periods
during a network upgrade. This should be a transient state during the upgrade period, versus a
permanent steady state. To accomplish this, the SMGR will need to be upgraded to SMGR 8.x and the
SM licenses will also have to be SM 8.x licenses (even for the systems that stay at SM 6.x or R7.x for a
period of time). Note the license upgrade for SM from SM R6/R7 to SM R8 is a $0 license charge, so
customers will not incur additional costs during the transition period. See below on the steps needed to
properly load the appropriate licenses.
1. Within A1SC/ASD you must upgrade all the SM/BSMs in the network (even if they will all not be
physically upgraded immediately)
• This will allow an SM 8 license for each SM
2. The SM 8 licenses need to be activated in PLDS for all instances in the network.
3. The resulting SM 8 license file will then need to be installed on SMGR WebLM. SMGR needs to
see a valid SM 8 license for each SM instance in the network (even the ones running SM 6.3). If
an SM 8 license file is not installed on SMGR WebLM, then any SM 6.x or 7.x servers will be
placed in license error mode with a 30-day grace period. If the grace period expires before a valid
SM 8 license file is installed, then the SM servers will be taken out of service and will not be
allowed to return to service until a valid SM8 license file is installed.
6.6. Implications of Devices Registering on Different Versions of Session

Manager During Upgrades
SIP Endpoint device data is not shared between 8.x and prior release realms. Therefore, changes made to
an endpoint registered to an 8.x Session Manager will not be reflected on endpoints registered to a prior
release Session Manager. This issue will be resolved when all SM nodes are updated to 8.x
6.7. Upgrading Session Manager R6 to R8 When Coming from EC Tools

(CS1000)
There is currently no support for ordering Session Manager R 8 from EC tools (Heritage
Nortel blue tools). This is by design as all Avaya Aura® R8 applications are sold only via
the ASD/One Source Configurator (A1SC). CS 1000 customers who need to upgrade their
existing SM to R8 will need to do the following in A1SC/ASD to get the correct materials
needed.

avaya.com
If you are creating an order where SM R8 is needed for a CS 1000 customer, follow the instructions
below to upgrade your SM to R8. This assumes the Session Manager already exists with the CS 1000
system and needs to be upgraded to Session Manager R8.
1. Complete your upgrade design for SM release x to SM R8 in A1SC/ASD
2. Design adjust off (remove) 380006 - AURA® R7 SM SYSTEM UPG ENTL OR 380007 -
AURA® R7 SM SYSTEM UPG LIC – NOTE: the quantity of the material. Replace these
codes with step 3 below:
3. Piece part add one of the following two SM ASIPP materials (in the same quantity that was
design adjusted off above) depending on your support/maintenance contract
a. 382464 – if customer does not have existing support
b. 382465 – if customer has some type of existing support (pass/pass+/etc…)
NOTES:
1. If the Session Manager does not already exist, this process does not apply and the customer can
simply order a new instance of SM in A1SC/ASD as per standard practice.
2. If you have a Session Manager defined in KRS and are moving to the an R8 Session Manager in
PLDS, and once the R8 Session Manager Licenses have been ordered, please contact Avaya
ASIPP team to decommission any existing Aura® Session Manager licenses in the KRS
licensing tool. Send email to asippteam@avaya.com. This will eliminate the need to pay
support of both the licenses in the KRS system and the ones in the PLDS system.
6.8. Upgrading from System Platform on 6.x to AVP on Avaya Aura® 8.1.1.
Material Code Short Desc Long Desc
387760 AURA® R7 DS VE VAPP LIC AURA® R7 DEVICE SERVICES VE VAPPLIANCE SYSTEM LIC:DS;NU;SR
With Avaya Aura® 6.x, many of the Avaya Aura® applications are delivered as part of a template on System
Platform. With Release 8.1.1, customers have the ability to flexibly choose the applications that are installed on a
server. As a result, it is important that when planning a like-for-like upgrade to Release 8.1.1 that the right
applications OVAs are included. In an upgrade, the Avaya Solution Designer (A1SC/ASD) will automatically
provision the OVAs that are needed to run the solution on AVP in Release 8.1.1, plus AVP and the required
license enablement codes.

avaya.com
Note that the Release 8.1.1 Solution requires System Manager (SMGR) to be installed somewhere in the
customer solution in order to manage the Release 8.1.1 Applications.
System Platform Applications Included OVAs needed in Release 8.1.1 Notes

Template in template on system for a Like-for-Like Upgrade
platform 6.x to AVP
CM Duplex CM, with SAL and CM, US 1, SAL Since WebLM is part of SMGR,
WebLM as part of System no separate WebLM OVA is
Platform CDOM required
CM Simplex Main CM, CMM, US, with SAL CM, CMM4, US1, SAL Since WebLM is part of SMGR,
and WebLM as part of no separate WebLM OVA is
System Platform CDOM required
CM Simplex CM, CMM, US, with SAL CM, CMM4, US1, SAL Since WebLM is part of SMGR,
Survivable Core and WebLM as part of no separate WebLM OVA is
Survivable CM, BSM, US, with SAL CM, BSM, US1, SAL Since WebLM is part of SMGR,
Remote and WebLM as part of no separate WebLM OVA is
System Manager SMGR (with WebLM), SMGR, SAL, US1 Since WebLM is part of SMGR,
and SAL as part of System no separate WebLM OVA is
Platform CDOM required
Application AES with SAL and AES, SAL, US1, WebLM2

Enablement WebLM as part of System
Services (AES) Platform CDOM
Midsize CM/CMM, SM, SMGR, CM, CMM4, SM, SMGR, PS, Since WebLM is part of SMGR,
Enterprise PS, AES, US, with SAL Avaya Breeze™3, AES, US1, SAL no separate WebLM OVA is
and WebLM as part of required
System Platform CDOM
Presence Services PS with SAL and WebLM PS, Avaya Breeze™3,US1 Since WebLM is part of SMGR,
(PS) as part of System Platform no separate WebLM OVA is
CDOM required

avaya.com
1
: AVP Utilitiesis required for all deployments with AVP to provide a services port functionality.
2
: A separate instance of WebLM is required for AES to support Enterprise Licensing with allocation mode
which uses a master and local WebLM.
3
: Presence Services is being supported as a snap-in on top of Avaya Breeze™, so that OVA needs to be installed
on the server in Release 8.1.1.
4
: Customers cannot install CMM 7.0.0.1 on a new AVP 8.1.1 Host. The only way to keep CMM in the solution
is to have it run on a dedicated server, running on AVP8.0 (or a prior version of AVP that it was supported on).
As of AA7.1.2, the migration for System Platform to AVP is automated and can be performed
remotely , more precisely 8300E LSP migrations from 5.2.1 and 6.x to 8.1.1 can be peformed
without having to send an expert onsite.
6.9. Upgrading from AVP 7.x to AVP 8.1.1

AVP will require a reinstallation of the AVP application and is therefore service impacting. Like for
any AVP upgrade or update, it can be performed remotely.
All CSR2 , CSR3 and S8300E are supported however memory upgrade may be required for highly
loaded CSR2 configurations.
From a planning point of view, it is highly recommended you follow the instructions in the
PCN/PSN <PSN027060u – Avaya Aura® Appliance Virtualization Platform Release 7.1.2 Memory
Upgrade Instructions to identify whether an add on memory kit will be required.
The following steps need to be followed for upgrading a solution to Release 8.1.1 :
– Update SDM Client to 8.1.1.
– Update System Manager AVP with the SDM Client AVP 8.1.1.
– Update System Manager with SDM Client 8.1.1.
– Use System Manager 8.1.1 to update any other AVPs and applications.
Note: In 8.1.1 (beginning in 7.1.2), AVP now requires a license. After the AVP upgrade or
installation is complete it is necessary to obtain the license file from PLDS and to make availalble to
AVP using WebLM.Note:: If AVP was properly ordered when it was originally installed then there
will be a licence in PLDS that can be used. However if there is no license in PLDS for AVP then
this is likely due to the fact that it was initially installed without being ordered; thus an order must be
placed for the AVP license to appear.
6.10. Important note regarding CMM and AVP Upgrades to 8.1.1

Note that CMM is no longer a supported application so customers should be considering OfficeLynx or
AAM as the path forward. The EoMS (End of Manufacturing Support) date for CMM was Aug. 27,
2019.
Customers cannot install CMM 7.0.0.1 on a new AVP 8.1.1 Host. The only way to keep CMM in the
solution is to have it run on a dedicated server, running on AVP8.0 (or a prior version of AVP that it was

avaya.com
supported on). Noting that CMM has been tested on CSR 2 & 3, but it has not been tested on ACP or
PodFX servers.
6.11. Midsize Enterprise (ME) Upgrades to Release Aura® R8

ME migration to Aura® R8 is a 2-step process; first to Aura® R7 and then up to Aura® R8.
The full upgrade to Aura® R8 may require additional server/application distribution to manage the Aura® 8
software and customer business capacity needs.
An option to leverage the ME R7 Disk Migration kits can be used in either deploymet model as part of migrating
to the R7 level(initially or as the BTC R8 deoplyed as R7 release).
• It may not be possible to fit all the ME applications on a single Server for R8 and forward
• Common Server R1 (including ME CSR1) is not supported on R8 so a new server or virtual
application deployement would be required
ME R6 upgrade/migration to deploy as Aura® R8.

This upgrade technically requires a two stage upgrade of the product. ME must first be migrated to Aura® R7
(per Aura® R7 procedures) and then the R7 must be upgraded to Aura® R8 per standard R7 to R8 upgrade
procedures
To design and order:

This ME upgrade/migration to deploy as R8 can be one with one design.
Set the existing system to MES and the target system The Configuratior will provide the codes needed to do
to R8, deploying as R8 the Interim upgrade to R7 and the final upgrade to R8
The new Installed Hardware Application (IHA)
configurator would be used to determine if the
existing appls can continue to fit, capacity wise, on the
existing servers or if additional resource is required.
This is the same as any system upgrade to Aura® R8
ME R6 upgrade/migration BTC R8 to deploy as Aura® R7.
As with all upgrades Buy to Current is active. A ME customer that wants to upgrade but deploy as R7, will
purchase their upgrade Buy to Current to R8, but can choose to deploy as R7.
Technically they would follow the exising ME R6 to R7 Migration and upgrade process.
To design and order:
This ME upgrade/migration to BTC to R8 but deploy as R7 can be done with one design. As with all BTC
desgins that deploy as the N-1, when the customer decides to take their BTC R8 entitlement, they will process the
second upgrade design to R8, deploy as R8.
Set the existing system to MES and the target system The Configuratior will provide the codes needed to do
to R8, deploying as R7 the upgrade to R7.
In the future when the customer wishes to deploy their As part of this process they will follow the
BTC R8 upgrade, they would do a A1S design setting configurator rules for deploying R8, including running

avaya.com
the existing system as R7 (not ME any longer) and the through the new Installed Hardware Application
target as R8 (IHA) configurator to determin if the existing appls
can continue to fit, capacity wise, on the existing
servers or if additional resource is required.
This is the same as any system upgrade to Aura® R8.
7.0 Product Specifications

7.1. Compatibility Matrix
Supported product releases can be found at the Compatibility Matrix on Support.Avaya.com link below
https://support.avaya.com/CompatibilityMatrix/Index.aspx
WebLM Note: For information presented in the Compatability Matrix on Avaya Support, the WebLM Standalone
application release follows the same intersect points as the System Manager –WebLM release with regard to
WebLM functions. For example, System Manager 8.1.1 and WebLM Standalone 8.1.1 have the same
compatability that is defined in the System Manager 8.1.1 table. In a future release, WebLM Standalone will have
its own entry in the Compatability Matrix on Avaya Support.
7.2. Solution Capacities and Performance

Session Manager, Communications Manager, Presence Services, Application Enablement Services and System
Manager combine to deliver the following capacity and performance. Improvements in this release are noted in
red.
For the full capacity table specification for Communication Manager go to:
https://support.avaya.com/downloads/
Avaya Aura® Communication Manager 8.1.1
Avaya Aura® Communication Manager System Capacities Table
Avaya Aura® 8.0 Overall Capacities

Avaya Aura® Quick Reference Specifications
(capacities across the Avaya Aura® 8.1.1 Solution)
Item
Number of Total administered Users defined in 300,000
System Manager database 1
Number of Total administered endpoints defined in 300,000
the System Manager database 2 (all endpoint types)
1
This is the total number of administered Users which have an ‘Identity’ configured in System Manager, and may or may not
have a communication profile defined. Users are defined in the System Manager’ Users Page: “ Home/Users/Manage Users”
2
This is the total number of administered endpoints defined in the System Manager Endpoints Page:
“Home/Elements/Communication Manager/Endpoints / Manage Endpoints”.

avaya.com
Number of Concurrently Registered SIP Devices3 1 Million

Total Enterprise Presence Users 250,000
SIP Users/CM 4 41,000
SIP Trunks per CM5 24,000
System Manager 8.1.1 Capacities7

Key System Manager Specific Capacities SMGR 8.1.1
Number of administrator logins 250
Number of simultaneous logins 50
Number of Total administered endpoints (all types)8 300,000
Number of Total administered Users defined in System Manager database9 300,000
Number of messaging mailboxes 300,000
Number of contacts per user 250
Number of public contacts 1,000
Number of personal contact lists, per user 1
Number of members in a personal contact list 250
Number of groups 300
Number of members in a group 400
Number of elements 25,000
Number of Communication Managers and/or CS1000s10 500
Number of Session Managers 28
Number of Branch Session Managers 500
Number of IP Offices11 2,000
Number of IP Office Unified Communication Module (UCM) or Application 2,000
servers as part of Branch Deployments
Number of roles 200
Number of roles, per user 20
Number of licensing clients 1,000
12
Number of Concurrent License requests (per WebLM) 300
Number of license requests during any 9 minute window (total, per WebLM) 50, 000
Number of local WebLM servers 22
Number of trust management clients 2,500
Number of Tenants (SMGR Multi-tenant) 250
3
The total number of SIP Devices that can be concurrently registered to Session Manager(s). Note: with Multiple Device
Access (MDA) each User can have up to 10 concurrently registered SIP devices.
4
Administered users
5
Up to 24,000 SIP Trunks and up to 36,000 SIP endpoints can be engineered with assistance of Avaya Engineering. Note the
limit for Evolution Server is 12000 SIP Trunks which supports Call Center environments and must be reviewed by Avaya
Engineering.

avaya.com
7
The table includes supported maximum capacities for each individual element type. Since there is only one System
Manager per Avaya Aura® deployment, it’s essential to understand that the solution number is not a summation of all the
supported Elements listed in the Table.
8
This is the total number of endpoints defined in the System Manager Endpoints Page: “Home/Elements/Communication
Manager/Endpoints / Manage Endpoints”.
9
This is the total number of administered Users which have an ‘Identity’ configured in System Manager, and may or may not
have a communication profile defined. Users are defined in the System Manager’ Users Page: “ Home/Users/Manage Users”
10
Capacity counts against the total number of elements.
1
To support central licensing of 2,000 IP Office 11.x, local WebLM licensing servers that are slaved to System Manager
licensing are required. See the IP Office .x product offer and System Manager WebLM for details.
12
Guidance on determining the number of license requests for any specific product: In general, each feature acquired by each
license client is one request (e.g. license file with 3 feature = 3 license requests per client (product instance). If there are 2
product instances getting licenses from WebLM that would be 6 requests total. SM and Avaya Breeze™ always have a
single license client (the element manager on SMGR) regardless of the number of Avaya Breeze™/SM servers.
Key Communication Manager 8.1.1 Capacities
For detailed Communication Manager capacities , please refer to “CM System capacities ” document posted on
support.avaya.com.
Key Communication Manager Specific Media Capacities; relative to AAMS (& Gx50)
Number of AAMS instances per CM (in 250

addition to the 250 gateways)
Announcements per Avaya Aura® Media “Unlimited,” up to number of licensed channels per AAMS
Server instance.
Note : Maximum number of administered announcements
files for a single CM per AAMS instance is 9000.
Announcement Playback Time with AAMS Unlimited, up to capacity of hard drive on AAMS server.
Announcement Playback Time with Gx50 45 min or 250 min (G450,) depending on memory kit used.
60 mins per VAL board.
Key Session Manager 8.1.1 Capacities

Key Session Manager Specific Capacities
Registrations/Second per SM 800
Advanced SIP Terminal Initializations/Second per SM 10
Locations/Adaptations/SIP Entities /Routing Policies 25,000
SIP Domains 1000
Dial Patterns 300,000

avaya.com
Key Branch Session Manager 8.1.1 Capacities

Key Branch Session Manager Specific Capacities
Sessions Per/Second per Embedded BSM 3600
Sessions Per/Second per Simplex BSM 16,000
Presence Services 8.1.1 Capacities

Capacities PS 7.1
Number of users 250k3
Number of SIP devices 350k
3
For deployments larger than 125k users, Presence services will be deployed by way of two separate clusters that
together provide the required aggregated capacity.
Communication Manager Messaging 7.0.0.1 Capacities

Capacities CMM7.0 CMM7.0 CMM-FM 6.3
Server Type S8300E Avaya Common Avaya Common

Server Server
Subscriber Mailboxes 1000 6000 15000
IP Trunk Call Answer Ports 24 210 210
IP Trunk Total Ports 36 250 250
IMAP4 Sessions 450 6000 6000
MCAPI (Formally known as IMAPI) 128 128 128
Sessions
TTS Sessions 12 30 30
Application Enablement Services 8.1.1 Capacities
Virtual machine footprint size and capacity

Beginning in 7.1.1, AE Services requires more memory and 2 G additional memory is required for all foot prints.
See the “VM foot print sizes” section.
ASAI notification Capacity

ASAI Notificationcapacity is 50K starting in CM 7.1 (increased from 32K).
This capacity is only for CM 7.1 (and greater) so that CM can support up to 50K ASAI event notification and
handle 50K domain control association. However, the limit on AE Services is the same as before and it remains at
32K per CM. Even though one AE Services server is limited to 32K per CM, it is possible to support 50K when

avaya.com
multiple AE Services servers are connect to a CM. Also when multiple CMs are connected to one AE Services
server, One AE Services server can support more than 32K. The 32K limitation is for single AE Services server
per CM.
Active Control Association Capacity

Domain control association is 50K starting in CM 7.1 (increased from 32K).
This capacity is only for CM 7.1 (and greater) so that CM can support up to 50K ASAI event notification and
handle 50K domain control association. However, the limit on AE Service server is the same as before and it
remains at 32K per CM. Even though one AE Services is limited to 32K per CM, it is possible to support 50K
when multiple AE Services servers are connect to a CM. Also when multiple CMs are connected to one AE
Service server, one AE Services server can support more than 32K. The 32K limitation is for single AE Services
server per CM.
The AES capacities referenced above do not yet reflect impact of Spectre/Meltdown fixes and are subject to
change.
7.3. Virtualization Resource Profiles

The following table details the resource profiles that are supported for each application for use in Virtualized
Environment and Virtual Appliance Deployments.
Summary Table of Resource Profiles
Application Name vCPU CPU Memory Hard Min Extra Upgrade

reservation (GB) disk Clock NICs Hard
(MHz) (GB) speed disk
(MHz)3 (GB)1
Application Virtualization 2 2700 5 25 0 4 0
Platform – CSR2 Small
AVP is pre-installed on the
Avaya Provided server
Platform – CSR2 CM High
Duplex
Application Virtualization 2 3277 5.5 25 0 4 0
Platform – CSR2 Medium

avaya.com

(MHz)3 (GB)1
Platform – CSR2 High
Platform – CSR3 V.Small
Platform – CSR3 Small
Platform – CSR3 CM High
Duplex
Platform – CSR3 Medium
Platform – CSR3 Large
Avaya Aura® Appliance 1 0 1 20 0 0 20
Virtualization
Platform Utilities
Avaya Aura® 2 3900 3.5 64 2300 0 14
Communication Manager
CM Main Max users 1000
(Embedded server running as a
Main)
Avaya Aura® 1 1950 3.5 64 2300 0 14
CM Survivable Max users
1000
(Embedded server running as
survivable)

avaya.com

(MHz)3 (GB)1
Avaya Aura® 2 4400 4 64 2200 0 14
CM Simplex1 Max users
2400
(Main only - for Any CM7
simplex design up to 2400 users)
Avaya Aura® 2 4400 4.5 64 2200 0 14
CM Simplex2 Max users
41000
(Can be used as Main or
Survivable)
Avaya Aura® 3 6600 5 64 2200 1 14
CM Duplex Max users
30000
(CM Duplex – Main or
Survivable – up to 30,000 users)
Avaya Aura® 3 7800 5 64 2599 1 14
CM High Duplex Max users
41000
(For Hi-Duplex Servers for Main
or survivable)
Avaya Aura®
CM Simplex Array Max users
300000 ***
(NOT AVAILABLE FOR
8.1.1) FUTURE USE ONLY
Avaya Aura®
CM Duplex Array Max users
300000 ***
(NOT AVAILABLE FOR
Avaya Aura®
CM High Duplex Array Max
users 300000 ***
(NOT AVAILABLE FOR

avaya.com

(MHz)3 (GB)1
Avaya Device Adapter “snap- 4 9600 8 50 2400 0 50
in” on Breeze® Profile 2, 4/8,
1,000 users
Avaya Device Adapter “snap- 8 19200 16 150 2400 0 150
in” on Breeze® Profile 4, 8/16,
5,000 users
Avaya Aura® Application 1 2190 4 30 2300 1 30
Enablement Services
AE Services 8.1.1 Profile 1
Enablement Services
Enablement Services
Avaya Aura® Branch 2 2200 3 35 2200 0 35
Session Manager
BSM Profile 1 Max
Devices 1,000
Avaya Aura® Branch 4 4400 4.5 35 2200 0 35
Session Manager
BSM Profile 2 Max
Devices 5,000
Avaya Aura® Session 3 3300 4.916 90 2200 0 90
Manager
SM Profile 1 Max Devices
2,000
Manager
4,500
Manager
7,000
Manager
10,000

avaya.com

(MHz)3 (GB)1
Manager
23,300
Avaya Aura® Session 53 58300 67584 200 2200 0 200
Manager
66,700
(SEE NOTE 4 at END of
TABLE)
Avaya Aura® Device 6 6900 5.12 150 2300 0 150
Services
AADS Profile 1
Devices 750
Services
AADS Profile 2
Devices 1350
Services
AADS Profile 3
Devices 2100
Services
AADS Profile 4
Devices 3000
Services
AADS Profile 5
Devices 7000
Avaya Secure Access Link - 1 0 1 10 2300 0 10
SAL
Note that Avaya Aura® NA NA NA NA NA NA NA
System Manager Profile 1
is no longer offered
Avaya Aura® System 6 13740 12 105 2300 0 105
Manager
SMGR Profile 2 Max User
250K

avaya.com

(MHz)3 (GB)1
Avaya Aura® System 8 18400 18 250 2300 0 250
Manager
System Manager Hi capicity
OVA
Avaya WebLM 1 2300 1 40 2300 0 40
Avaya Aura® Presence 4 9600 8 50 2400 0 50
Services
Breeze 3.3 Profile 2, 4/8
Services
Services
Services
Avaya 1 2000 2 77 2000 0 64
Aura®Communication
Manager Messaging
1,000 subscribers
Avaya 1 2000 2 94 2000 0 64
Aura®Communication
Manager Messaging
2,400 subscribers
Avaya Aura® 1 2000 2 139 2000 0 64
Messagng
6,000 subscribers
Avaya Aura® 2 4000 2 252 2000 0 64
Messaging
15,000 subscribers
Avaya Aura® Media 4 9176 4.608 50 2294 2 0
Server2
Media Server Profile 1: 4
vCPUs, 4.5GB Memory,
50GB vDisk

avaya.com

(MHz)3 (GB)1
Avaya Aura® Media 8 18352 8.192 50 2294 2 0
Server2
Media Server Profile 3: 8
vCPUs, 8GB Memory,
50GB vDisk
1
Upgrade Hard disk: This value is only used for deployments with Appliance Virtualization Platform (AVP). The upgrade hard disk size
is the hard disk space this application needs to be able to upgrade. The server should have hard disk free equal to the largest required
upgrade space of any of the applications. Example if CM requires 16 GB to upgrade and AES requires 50GB, 50 GB free hard disk space
would be required on the system after the applications are installed.
2 AAMS is a low latency real-time application, guidelines must be followed when deploying an AAMS virtual appliance on a shared
hypervisor. Oversubscribing the hypervisor can result in unpredictable performance due to varying VM scheduling latency. An ordinary
application may not be impacted by this latency, but a real-time application sending and receiving media at very frequent and precise
intervals (<= 10ms) is at greater risk. For these reasons, the total vCPUs utilized by all virtual machines on a shared hypervisor
should not exceed the number of physical cores available. This prevents virtual machines from interfering with each other, and prevents
difficulties with scheduling each VM consistently and predictably.
3 The Clock Speeds in this table are based on Comon Server 2 (CSR2). For CSR3, the clock speeds will be different. Refer to the
application documentation for more detailed information and CSR3 data.
4 SMProfile 6 not not be automatically calculated for AVP sizing with the GA of 8.1.1 in the order tools. It will be greyed out and not
show up at all. You will need to order Profile 5 and if AVP, manual calculation for server size will be needed.
*** Note: The underlying framework for an upcoming new Avaya Aura® Platform enhancement “Avaya Aura
Resource profiles for product’s AWS and KVM deployment options are documented in individual product
specific deployment guides.
Session Manager Resource Profile Capacity Changes

The following are capacity and performance numbers for two Session Manager resource profiles. For
the complete view of all resource profiles, see the Session Manager VMware Deployment Guide.
Session Manager Profile 4 supports:

• 10,000 SIP users during normal operations
• a maximum of 12,000 SIP users in a failover scenario
• 100 sessions per second (360K per hour)
• 90K simultaneous sessions

avaya.com
Session Manager Profile 5 (only supported on CSR2 and forward) supports:

• 23,334 SIP devices during normal operations
• a maximum of 25,000 SIP devices in a failover scenario
• 150 sessions per second (540K sessions per hour)
• 170K simultaneous sessions
Up to 250K SIP users or 350K SIP devices are supported by any N+M sparing Session Manager
configuration consisting of the largest 23.3K Device Footprint (Profile 5). The customer must adequately
distribute devices across primary and secondary servers to accommodate the configuration. For example, the
typical Session Manager solution with N+1 sparing supports 350K SIP devices across 15 Session Managers
for a single Session Manager failure. Similarly, a dual data center (N+N) supports 350K SIP devices across
28 Session Managers (14 in each data center).
Equinox Soft Client Capacities with AADS Per Session Manager

The following table documents the number of soft clients supported per Session Manager when the soft clients are
using AADS:
SM 8.1.1 and AADS 7.1.3 and later.
Session Manager # Devices Device Services # Softclient

Profile Profile Devices
1 2,000 1 1200
2 4,500 2 2700
3 7,000 3 4200
4 10,000 4 6000
5 23,300 5 13,900
Note: There is a One to one relationship between Avaya Aura® Device Services and Session Manager i.e. for
every AADS deployed there must be an equivalent Session Manager. To increase the number of Softclients
devices supported, deploy additional SM / AADS pairs. Beginning with AADS 7.1 and SM 7.1 it is no longer
mandatory that AADS is deployed on the physical same server as SM. For a deployment of AADS that is not on
the same server as SM, the network latency between Avaya Aura® Device Services and the associated Session
Manager must be less than 5 ms.
System Manager Resource Profile and Server Support Information

Resource Profile Max Number of Users Max Number of BSMs Max Number of Session
Managers
Profile 1 is no longer
NA NA NA
available.

avaya.com
SMGR Profile 2 35,000 to 250,000 250 12

SMGR Profile 3 35,000 to 250,000 500 28
The System Manager resource requirements listed below are based on the Profile and applicable for
System Manager deployed on AVP, Customer VMware Environment, AWS or KVM (openstack)
Virtual
# vCPU Min vCPU CSR1 CSR2
Footprint Profile vRAM Hard
Reserved Speed (MHz) Support Support
Disk
Profile 1 is no longer
NA NA NA NA NA NA
available.
Profile-2 (35K-250K
users with up to 250 6 2290 MHz 12GB 105GB No Yes
BSM’s and 12 SM’s)
Profile-3 SMGR High

Capacity (35K-250K
8 2290 MHz 18GB 250GB No Yes
users with up to 500
BSM’s and 28 SM’s
AES Resource Profile Information

The following table provides more detail on the resource profiles that are available for AES. Application
Enablement Services 8.1.1 supports the following resource footprints:
DMCC (Third party call DMCC (First Party call TSAPI/DLG/CVLAN

control :Microsoft control)
OCS/Lync, IBM Sametime,
Avaya Aura® Contact
Center)
Resource Profile Maximum # Maximum #
of users or Maximum of users or Maximum Maximum Messages per
agents BHCC agents BHCC second (MPS) Rate
Profile 1 1K 20K BHCC
1 CPU & 4 GB
RAM 10K 6K BHCC 1K 9K BHCC 1K MPS

avaya.com
DMCC (Third party call DMCC (First Party call TSAPI/DLG/CVLAN

control :Microsoft control)
OCS/Lync, IBM Sametime,
Avaya Aura® Contact
Center)
Profile 2 2.5K 50K BHCC
2 CPU & 4 GB
RAM 12K 12K BHCC 2.4K 18K BHCC 1K MPS
Profile 3
4 CPU & 6 GB
RAM 5K 100K BHCC 8K 36K BHCC 2K MPS
7.4. Sizing Common Servers for Virtual Appliance Deployments

When new orders for Avaya Aura® 8.1.1 applications are processed, the Avaya Solution Designer (A1SC/ASD)
will use factors such as number of users and availability to calculate the appropriately sized AVP server construct.
An industry-wide issue was found in the way many modern microprocessor designs have implemented
speculative execution of instructions (a commonly used performance optimization). There are 3 primary variants
of the issue and the way the exploitation can occur, and these exploitations/vulnerabilities are commonly referred
to as Meltdown and Spectre.
Applications in the 8.1.1 solution have inclusion of remediation to Operating System, Hypervisor, and Server
BIOS. In some cases the performance of the applications can be impacted so it is important to include this
consideration in solution design. The above PSN also points to others for each application, & for upgrade
scenarios instructions are given for investigation of operating metrics on current servers.
Note:
- There are adjustments to capacities and also to server specifications for the VE offer that should be
considered.
- Avaya is reliant on our suppliers to validate the effectiveness of their respective Meltdown and
- The customer is responsible for implementing, and the results obtained from, such patches.
- The customer should be aware that implementing Aura® 8.1.1 may result in degraded performance
relative to running on releases prior to 8.1.

avaya.com
How the Server Calculation works

each application has several resource profiles that are defined in this document. There are different requirements
for CPU, Memory and Hard Disk use, depending on the profile selected. A small system would select a smaller
resource profile, and will therefore require fewer server resources than a large system for example.
In order to determine if a desired mix of applications/scale can be supported on a specific server, the following
steps need to be followed. The Avaya Solution Designer (A1SC/ASD) performs this calculation automatically,
and provisions the appropriate server to support the required applications.
1. Determine the required resoure profiles for the desired applications/scale (see the table in section 6.3)
o The AVP profile must always be included (1/server)
o The Utility Services profile must always be included (1/server)
2. Add up the required resources for each of the profiles for the following:
o vCPU
o CPU reservation (MHz)
o Memory (GB)
o Hard disk(GB)
o Min Clock speed (MHz)
o Extra NICs
o Upgrade Hard disk (GB) (Upgrade hard disk amount is a hard disk pool that applications use
with virtual appliance deployments when upgrading as the old hard disk image is kept during
upgrade or for running snapshots. The server should have hard disk free equal to the largest
required upgrade space of any of the applications. Example if CM requires 16 GB to upgrade and
AES requires 50GB, 50 GB free hard disk space would be required on the system after the
applications are installed.)
3. Determine the available resources for the server
4. Compare this to the available resources on the server
o The available resources must be greater than the required resources to support the configuration
Special Note: Avaya Aura® Media Server (AAMS)

AAMS is a low latency real-time application, guidelines must be followed when deploying an AAMS
virtual appliance on a shared hypervisor. Oversubscribing the hypervisor can result in unpredictable
performance due to varying VM scheduling latency. An ordinary application may not be impacted by this
latency, but a real-time application sending and receiving media at very frequent and precise intervals (<=
10ms) is at greater risk. For these reasons, the total vCPUs utilized by all virtual machines on a
shared hypervisor should not exceed the number of physical cores available. This prevents virtual
machines from interfering with each other, and prevents difficulties with scheduling each VM
consistently and predictably.
For more information, refer to the “Deploying and Updating Avaya Aura® Media Server Appliance”best
practices recommendations.

avaya.com
7.5. VMware ESXi Software Supported for Virtualized Environment

Several substantial VE Enhancements were made with Release 8.0 – please refer to section 5.2.3 of this document
for more details
The following versions of VMware ESXi are supported with the Avaya Aura® 8.1.1 applications.
VMware ESXi Avaya Aura® 8.1.1
VMware ESXi 6.0 √
VMware ESXi 6.5 √
VMware ESXi 6.7 √ (7.1.3 and later)
Note: As of release 8.0, ESXi 5.0, 5.1, & 5.5 are no longer supported.

avaya.com
7.6. Supported Browsers
Avaya Aura® 8.1.1 supports the following browsers:
Avaya Aura® Application Internet Explorer Supported Fire Fox Supported
Session Manager 8.1.1 (SM) IE 11 FF 65, 66, and 67

Branch Session Manager IE 11 FF 65, 66, and 67
8.1.1 (BSM)
System Manager 8.1.1 IE 11 FF 65, 66, and 67
(SMGR)
Application Enablement IE 11 FF 65, 66, and 67
Service 8.1.1 (AES)
Communications Manager via SMGR - IE 11 via SMGR - FF 65, 66, and 67
8.1.1 (CM)
via Local CM EM (SMI) via Local CM EM (SMI)
- IE IE 11 - FF 65, 66, and 67
Avaya Breeze™ (Avaya IE 11 FF 65, 66, and 67
Breeze™) 3.5 (including
Presence)
Avaya Aura® Media Server IE 11 via SMGR - FF 65, 66, and 67
8.0 SP2 (AAMS)
via Local CM EM (SMI)
- FF 65, 66, and 67
WebLM 8.1.1 IE 11 FF 65, 66, and 67
7.7. Supported Hardware

Avaya Common Servers Supported for New Orders for Virtual Appliance Deployments
For new purchases, Avaya Aura® 8.1.1 applications will be shipped with Dell Gen 10 servers using Intel Skylake
processors. This is the 1U Next Generation Virtualized Server Platform from Dell and is named “Avaya Common
Platform” 100 series (ACP 100). There are three variants of this server that differ only in the way the software is
loaded on the server (ie. Underlying hardware is the same):
• ACP 110 Series - the ACP version for bare metal software applications
• ACP 120 - the ACP version for AVP hosted software applications
• ACP 130 –Standard VMware version (non-customized). Avaya does not provide tools to
install/upgrade the VMware hypervisor. Apps installed and host managed using vSphere web
client or customer provided vCenter server. Remote upgrade of servers is not supported (ie. Site
visit is required for upgrades).
There will not be an alternate vendor for this offering (ie. Avaya is not offering servers from HP as an alternate as
was previously done for the Common Server 2 and 3 platforms).

avaya.com
Note that new orders will continue to ship on CSR3 servers until the stock is depleted. In all cases Avaya
Operations will avoid shipping a mix of CSR3 and ACP servers. If there is a preference as to CSR3 or ACP
servers then please contact Avaya Order Management and it may be possible to accommodate such a request.
Existing CSR2/CSR3 and S8300E remain supported in Aura 8.1.1.
When new orders for Avaya Aura® 8.1.1 applications are processed, the A1SC/ASD tool will use factors such as
number of users and availability to calculate the appropriately sized AVP server construct.
Aura® 8.1.1 will go GA on Monday, Oct. 28, 2019. In addition to the new functionality, this release also
contains remediation of the Spectre and Meltdown Vulnerabilities that were initially remediated in Aura® 8.1.
consideration in solution design.
Note:
considered.
- The customer is responsible for implementing, and the results obtained from installing Aua 8.1.1
- The customer should be aware that implementing Aura® 8.1.1 may result in degraded performance
relative to running on previous releases.
7.7.1.1. Common Server Order Codes – CSR2

Note: Common Server 2 servers are no longer provided on new orders.
7.7.1.2. Common Server Order Codes – CSR3
Material Code Description

383529 DL360G9 SRVR VLARGE AVP
383552 R620 SRVR VLARGE AVP

avaya.com
383531 DL360G9 SRVR MEDIUM AVP

383548 R630 SRVR MEDIUM AVP
383521 DL360G9 SRVR SMALL AVP
383540 R630 SRVR SMALL AVP
383515 DL360G9 SRVR VSMALL AVP
383536 R630 SRVR VSMALL AVP
383530 DL360G9 SERVER CM HIGH DUPLX AVP
383551 R630 SERVER CM HIGH DUPLX AVP
Note: if a user selects CM Hi Duplex in a Avaya Provided Server – Shared deployment, the DL360G9 SRVR
VLARGE AVP server will be provisioned, since it has more resource capacity for shared mode. If a user selects
CM Hi Duplex in a Avaya Provided Server – Standalone Mode, the DL360G9 SERVER CM HIGH DUPLX
AVP will be provisioned, since it is tailored for this deployment type.
7.7.1.3. Common Server Specifications Order codes – ACP 120
700514094 ACP 120 DELL SRVR P2 BUNDLE

Equivalences between the CSR3 AVP appliances and the ACP120 bundles different models are listed below:
CSR3 Model ACP 120 Profile

Vsmall AVP P2
Small AVP P3
Medium AVP P4
Vlarge AVP P5
CM High Duplex AVP P4
7.7.1.4. Common Server Specifications – General – CSR2

Server DL360PG8 DL360PG8 SRVR DL360PG8 SRVR DL360PG8
Component SRVR LARGE MEDIUM AVP SMALL AVP SERVER CM
AVP HIGH DUPLX
AVP

avaya.com
Form factor 1U 1U 1U 1U
Processor family Intel (2.9 GHz - Intel (2.3 GHz - Intel (2.3 GHz - E5- Intel (2.9 GHz -
E5-2667) E5-2630) 2630) E5-2667)
Number of processors 2 2 1 1
Memory type 4 GB RDIMM 4 GB RDIMM (8) 4 GB RDIMM (4) 4 GB RDIMM (4)
(16)
Total memory 64GB 32GB 16GB 16GB
Hard Disk Drive 300GB Drives 300GB Drives 300GB Drives 300GB Drives
Number of Hard Disk Drive 4 3 2 2
RAID Level 5 3 1 1
Network interface 4 4 4 4
Optical drive DVD+/-RW, DVD+/-RW, DVD+/-RW, SATA, DVD+/-RW,
SATA, SATA, INTERNAL SATA,
INTERNAL INTERNAL INTERNAL
Power supply 750W AC 460W AC 460W AC 460W AC
Number of power supplies 2 2 1 1
7.7.1.5. Common Server Specifications – General – CSR3 - HP

Server DL360G9 SRVR DL360G9 SRVR DL360G9 SRVR DL360G9 SRVR DL360PG8
Component VLARGE AVP MEDIUM AVP SMALL AVP VSMALL AVP SERVER CM
HIGH DUPLX
AVP
Form factor 1U 1U 1U 1U 1U
Processor family Intel (2.6 GHz - Intel (2.4 GHz - Intel (2.4 GHz - Intel (2.4 GHz - Intel (2.6 GHz -
E5-2640v3) E5-2620v3) E5-2620v3) E5-2620v3) E5-2640v3)
Number of 2 2 1 1 1
processors
Memory type 4 GB RDIMM 4 GB RDIMM 4 GB RDIMM 4 GB RDIMM 4 GB RDIMM
(12) (8) (8) (4) (4)
Total memory 48GB 32GB 32GB 16GB 16GB
Number of Hard 4 3 2 2 2
Disk Drive
RAID Level 5 5 1 1 1
Network interface 6 6 6 6 6
Optical drive DVD+/-RW, DVD+/-RW, DVD+/-RW, DVD+/-RW, DVD+/-RW,
SATA, SATA, SATA, SATA, SATA,
INTERNAL INTERNAL INTERNAL INTERNAL INTERNAL
Power supply 800W AC 800W AC 500W AC 500W AC 800W AC
Number of power 2 2 2 1 2
supplies

avaya.com
7.7.1.6. Common Server Specifications – General – CSR3 - DELL

Server R630 SRVR R630 SRVR R630 SRVR R630 SRVR R630 SERVER
Component VLARGE AVP MEDIUM AVP SMALL AVP VSMALL AVP CM HIGH
DUPLX AVP
Form factor 1U 1U 1U 1U 1U
Processor family Intel (2.6 GHz - Intel (2.4 GHz - Intel (2.4 GHz - Intel (2.4 GHz - Intel (2.6 GHz -
E5-2640v3) E5-2620v3) E5-2620v3) E5-2620v3) E5-2640v3)
Number of 2 2 1 1 1
processors
Memory type 4 GB RDIMM 4 GB RDIMM 4 GB RDIMM 4 GB RDIMM 4 GB RDIMM
(12) (8) (8) (4) (4)
Total memory 48GB 32GB 32GB 16GB 16GB
Number of Hard 4 3 2 2 2
Disk Drive
RAID Level 5 5 1 1 1
Network interface 4 4 4 4 4
Optical drive DVD+/-RW, DVD+/-RW, DVD+/-RW, DVD+/-RW, DVD+/-RW,
SATA, SATA, SATA, SATA, SATA,
INTERNAL INTERNAL INTERNAL INTERNAL INTERNAL
Power supply 750W AC 750W AC 495W AC 495W AC 750W AC
Number of power 2 2 1 1 2
supplies
7.7.1.7. ACP 120 General specifications:
Server ACP 120 Profile 2 ACP 120 Profile 3 ACP 120 Profile 4 ACP 120 Profile 5
Component
Form factor Dell R640XL 1U Dell R640XL 1U Dell R640XL 1U Dell R640XL 1U
server server server server
Processor family Intel Skylake CPU Intel Skylake CPU Intel Skylake CPU Intel Skylake CPU
S-4114 S-4114 G-6132 G-6132
Number of processors 1 2 1 2
Number of Cores / CPU 10 10 14 14
Number of Cores / 10 20 14 28
Server
Total memory 24GB 48GB 96GB 192GB
Hard Disk Drive 600GB Drives 600GB Drives 600GB Drives 600B Drives
Number of Hard Disk 3 4 4 6
Drive
RAID Level 5 6 6 6
Number of 1GB 6 6 6 6
Network interface

avaya.com
Raid Card
LP PCIe 2GB LP PCIe 2GB LP PCIe 2GB LP PCIe 2GB
Cache Cache Cache Cache
Number of power 2 2 2 2
supplies
7.7.1.8. Common Server Specifications – Resource Availability for Virtualization with AVP
Resource Type CPU VCPU CPU reservation Memory HDD Clock NICs
Speed
(GB) (GB)
(Mhz)
DL360PG8 SRVR 12 24 34,800 64 838 2900 8
LARGE AVP
DL360PG8 SRVR 12 24 27,600 32 558 2300 41
MEDIUM AVP1
DL360PG8 SRVR 6 12 13,800 16 278 2300 6
SMALL AVP
DL360PG8 6 12 17,400 16 278 2900 6
SERVER CM
HIGH DUPLX AVP
DL360G9 SRVR 16 32 41,600 48 12002 2600 6
VLARGE AVP
DL360G9 SRVR 12 24 28,800 32 9002 2400 6
MEDIUM AVP
DL360G9 SRVR 6 12 14,400 32 6003 2400 6
SMALL AVP
DL360G9 SRVR 6 12 14,400 16 6003 2400 6
VSMALL AVP
DL360PG8 8 16 20,800 16 6003 2600 6
SERVER CM
HIGH DUPLX AVP
R630 SRVR 16 32 41,600 48 12002 2600 4
VLARGE AVP
R630 SRVR 12 24 28,800 32 9002 2400 4
MEDIUM AVP
R630 SRVR 6 12 14,400 32 6003 2400 4
SMALL AVP
R630 SRVR 6 12 14,400 16 6003 2400 4
VSMALL AVP
R630 SERVER CM 8 16 20,800 16 6003 2600 4
HIGH DUPLX AVP
1
When AES, AAMS or CM Duplex are provisioned with the MEDIUM AVP Server, an extra NIC card is
provisioned with the order, as they require more than 4 NIC ports.
2
This server is setup with RAID level 5 – the HDD capacity number provided is the max raw HDD storage, not
reflecting any impact on the actual capacity available after a RAID 5 implementation.
3
This server is setup with RAID level 1 – the HDD capacity number provided is the max raw HDD storage, not
reflecting any impact on the actual capacity available after a RAID 5 implementation.

avaya.com
Avaya Common Servers Supported for Upgrades to Virtual Appliance (CSR2)

For upgrades to Avaya Aura® 8.1.1, the following servers can be supported. In each case, the A1SC/ASD tools
will support a like-for like upgrade, and will provision an instance of Appliance Virtualization Platform (AVP) for
each server.
Adopting Application # of # of Power
(Main & Alternate if applicable) Server Size Processor (Intel Xeon) CPU Dynamic RAM Hard Disk Drive RAID Ports Supply
Communication Manager Simplex / Mid-Performance CS Rel2 1U E5-2630 2.3 Ghz 6-core 1 16 GB 2 x 300 GB 10K RAID 1 6 1 x 460 WAC
Duplex (303518, Main) HP DL360PG8 Sandy Bridge (4GB RDIMM) 1 x DVD R/W P420i/512MB
Communication Manager Simplex / Mid-Performance CS Rel2 1U E5-2630 2.3 Ghz 6-core 1 16 GB 2 x 300 GB 10K RAID 1 6 1 x 495 WAC
Duplex (303516, Alternate) Dell R620 Sandy Bridge (4GB RDIMM) 1 x DVD R/W H710/512MB
Communication Manager - High Performance Duplex CS Rel2 1U E5-2667 2.9 Ghz 6-core 1 16 GB 2 x 300 GB 10K RAID 1 6 1 x 460 WAC
(303519 - 2 servers, Main) HP DL360PG8 Sandy Bridge (4GB RDIMM) 1 x DVD R/W P420i/512MB
Communication Manager - High Performance Duplex CS Rel2 1U E5-2667 2.9 Ghz 6-core 1 16 GB 2 x 300 GB 10K RAID 1 6 1 x 495 WAC
(303517 - 2 servers, Alternate) Dell R620 Sandy Bridge (4GB RDIMM) 1 x DVD R/W H710/512MB
Session Manager (303564, NTL303564, Main) CS Rel2 1U E5-2630 2.3 Ghz 6-core 2 32 GB 2 x 300 GB 10K RAID 1 4 2 x 460 WAC
HP DL360PG8 Sandy Bridge (4GB RDIMM) 1 x DVD R/W P420i/512MB
Session Manager (303563, NTL303563, Alternate) CS Rel2 1U E5-2630 2.3 Ghz 6-core 2 32 GB 2 x 300 GB 10K RAID 1 4 2 x 495 WAC
Dell R620 Sandy Bridge (4GB RDIMM) 1 x DVD R/W H710/512MB
System Manager (303566, NTL303566, Main) CS Rel2 1U E5-2630 2.3 Ghz 6-core 2 32 GB 2 x 300 GB 10K RAID 1 4 2 x 460 WAC
System Manager (303565, NTL303565, Alternate) CS Rel2 1U E5-2630 2.3 Ghz 6-core 2 32 GB 2 x 300 GB 10K RAID 1 4 2 x 495 WAC
Presence Services (303561, NTL303561, Main) CS Rel2 1U E5-2667 2.9 Ghz 6-core 2 32 GB 3 x 300 GB 10K RAID 5 4 2 x 750 WAC
Presence Services (303562, NTL303562, Alternate) CS Rel2 1U E5-2667 2.9 Ghz 6-core 2 32 GB 3 x 300 GB 10K RAID 5 4 2 x 750 WAC
Application Enablement Services (303580) CS Rel2 1U E5-2630 2.3 Ghz 6-core 1 16 GB 2 x 300 GB 10K RAID 1 4 1 x 495 WAC
Solution for Midsize Enterprise / Collaboration (303560) CS Rel2 1U E5-2667 2.9 Ghz 6-core 2 64 GB 4 x 300 GB 10K RAID 5 8 2 x 750 WAC
Communication Manager Messaging - Federal Market CS Rel2 1U E5-2630 2.3 Ghz 6-core 2 32 GB 3 x 300 GB 10K RAID 5 4 2 x 460 WAC
(304210, Main) HP DL360PG8 Sandy Bridge (4GB RDIMM) 1 x DVD R/W P420i/512MB
Communication Manager Messaging - Federal Market CS Rel2 1U E5-2630 2.3 Ghz 6-core 2 32 GB 3 x 300 GB 10K RAID 5 4 2 x 495 WAC
(304211, Alternate) Dell R620 Sandy Bridge (4GB RDIMM) 1 x DVD R/W H710/512MB
Important Note :
Memory addon kit may be required depending on the configuration running on the CSR2 ( SDM will catch
the insufficient memory upon upgrade )
A procedure describing a script that needs to be run on each server to identify whether the additional
memory is going to be required is documented into the following PSN027060u – “Avaya Aura® Appliance
Virtualization Platform Release 7.1.2 Memory Upgrade Instructions”. This PSN describes how to identify
if the memory upgrade is needed, how to order the proper memory banks and how to install them.
Avaya Servers Supported for Server Appliance Deployments (Not Virtualized)

The Avaya Aura® Media Server is also offered as a Server Appliance which is an appliance offer that is not
virtualized to provide a higher capacity solution.
389797 R230XL SERVER AAMS SMALL
383553 R630 SRVR AAMS
Server Requirements For Software Only Deployments (not virtualized)

The Avaya Aura® Media Server (AAMS) and Application Enablement Services (AES) are both offered as a
software only offer. This offer is also not virtualized, and includes a customer-provided server with an operating
system (e.g. Redhat Linux) and one instance of the application.
Minimum Server Requirements for Software Only Deployment on AES

avaya.com
 2.3 GHz processor with hyper threading enabled or a multi-core processor with equivalent CPU speed
– 2 CPUs for 4k DMCC registrations
– 4 CPUs for 8k DMCC registrations
 2 GB RAM
– 2 GB RAM for customers who support 4K DMCC registrations, 10,000 simultaneous MOC/LCS users or a
sustained processing rate of 720 TSAPI messages per second.
– 4 GB RAM for customers who support 8K DMCC registrations, 20,000 simultaneous MOC/LCS users or a
sustained processing rate of 1,000 TSAPI messages per second.
 10 GB free disk space, after installing Linux
– Hard disk drive with at least 7200 rpm rating
– 512 KB L2 cache
– 100 BaseT Ethernet NIC, which can either be locked to 100M / full or use Auto–Negotiation to achieve
100M / full
 DVD/CD-ROM drive
Server Requirements for Software Only Deployment on AAMS
The server must meet the following hardware requirements to support Avaya Aura® MS functionality. Please
refer AMS product documentation for updated specifications.
Supported operating systems: Install Avaya Aura® MS 8.0 only on the following operating systems:
- Red Hat Enterprise Linux Server 7.x
Supported Virtualized Environment Hardware:
7.7.5.1. Systems & Servers :

All hardware officially supported and certified by VMWare and meeting Avaya Aura® core applications
specifications as described in the respective deployment guides, is supported as part of the Virtualized
Environment offer.
More details can be found in the following KB article on the support site.
https://kb.avaya.com/kb/index?page=content&id=TRNG100391
7.7.5.2. Storage:
Standard SAN technologies And Virtual SAN technologies ( VSAN ) are all supported provided that
they meet the Avaya Aura® core applications specifications as described in the respective deployment
guides.
Avaya Embedded Servers

Only S8300E will be supported on Avaya Aura® 8.1.1.
S8300D is no longer supported.
Gateways
Supported gateways include the following:
• G430
• G450
• G650

avaya.com
Note that MCC and SCC are not supported with Avaya Aura® 8.1.1.
Network Performance Requirements for Aura® Applications

Below are the performance metrics required for Aura® applications to run in a cuustomer’s network. These are
also covered under the NRA (Network Readiness Assessment) policy, available on the Avaya Sales Portal.
https://sales.avaya.com/documents/1399552074828
Metric Recommended Acceptable
One-way Network Delay < 80 milliseconds < 180 milliseconds
Network Jitter < 10 milliseconds < 20 milliseconds
Network Packet Loss (Voice) 1.0% 3.0%
Network Packet Loss (Video) 0.1% 0.2%
QoS Enabled Required Required
8.0 Product Documentation

See http://documentation.avaya.com for documentation for Avaya Aura®
8.1. Release Notes

Release Notes are a valuable asset when updating the system to the next release. This includes any bug fixes and
installation notes to make sure your update goes as smooth as possible. Release Notes are available at the Avaya
support center at http://support.avaya.com. Also see Product Support Notices (PCNs).
8.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
Documents and search by product.
The following are the documents for Avaya Aura® 8.1. Please use the search function available on
http://www.avaya.com/support to find these documents. Search for the application named then click on “Product
Documents”. Release notes may be found under “Downloads” with the software.
Please refer to the Documentation Catalog for a complete list of Avaya Aura® Release 8.1.1 documents:

avaya.com
9.0 Avaya Learning

9.1. Avaya Learning Center
The Avaya Learning Center, www.avaya-learning.com, is the gateway to Avaya training and credential offers.
Avaya Sales and Services authorization requirements are outlined in the Avaya Solutions Authorization Policy
Guide located on the Avaya Connect Program site, www.avaya.com/avayaconnect.
At this time there are no new authorization requirements for Avaya Aura® 8.1.1. Existing Avaya Aura®
authorized partners are highly encouraged to take advantage of the following training offers specifically focused
on providing individuals holding current Avaya Aura® related credentials the information they need to
successfully sell, design and deploy the Avaya Aura® 8.1.1 suite. With total focus on successful deployments,
risk mitigation against needing reactive emergency technical support and to protect and grow customer
satisfaction, Avaya’s expectation is individuals will complete this recommended training PRIOR TO attempting
any sales, design or deployment of the new Avaya Aura® 8.1.1 suite. The “What is New” Delta Training Offers
are available at no charge and include end of course tests where students can check their learning.
Sales Curriculum (No Charge; On Demand) - Available late March 2017

• 4300W Avaya Team Engagement Portfolio Sales Overview (Sales) (planned as 1 hr.)
• 4301W Avaya Team Engagement - Core Components (Sales) (variable based on reading
time)
• 4302W Avaya Team Engagement - Gateways and Endpoints (Sales) (variable based on reading
time)
Services Curriculum (All Technical Audiences; No Charge; vILT and Recorded) – vILT available early August 2015
• 2007W What is New in Avaya Aura® 7.0 (planned as 4 hrs)
• 2008W What is New in Avaya Aura® Application Enablement Services (AES) 7.0 (planned as 2 hrs)
• 2009W What is New in Avaya Aura® Communication Manager 7.0 (planned as 2 hrs)
• 2010W What is New in Avaya Aura® Presence Services 7.0 (planned as 1 hr)
• 2011W What is New in Avaya Aura® System Manager & Session Manager 7.0 (planned as 2 hrs)
Workshops with Labs (Implement and Support Audiences ) – Available late August 2015
• 2012V Migrating and Upgrading to Avaya Aura® Platform 7.0 (planned as 5 day
vILT/ILT)
• Includes topics from all “What is New” deltas and access to end of course tests
• 2013V Avaya Aura® 7.0 Administration (planned as 3-5 day
vILT/ILT)
Individuals new to Avaya Aura® should complete the appropriate credential curriculum below in addition to the
above training PRIOR TO attempting any sales, design or deployment of the new Avaya Aura® 7.1 suite.
The Avaya Learning center at www.avaya-learning.com, provides the gateway to prepare you for the Avaya
professional credentials. The following credentials are relevant for the Avaya Aura® 7 release.
Sales and Design Training
APSS-1100 Avaya Enterprise Team Engagement Solutions
Code Title Updated 7.1
4300W Avaya Team Engagement Portfolio Overview Yes

avaya.com
No
4314W Avaya UC Experience Strategy and Portfolio Overview
4311W Selling Avaya Messaging Solutions Overview No
4521W Selling Avaya Video Conferencing Solutions No
No
4322W Selling Zang - Avaya “Born-in-the-Cloud” Collaboration Services
4312W Avaya Aura® Suites Licensing No
PID01 Core Suite
PID02 Power Suite
PID03 Enterprise Software Entitled Licensing

PID04 Buy to Current
4315W Avaya Equinox Solution No
PID01 Avaya Equinox Solution
PID02 Avaya Equinox for Web
4301W Avaya Team Engagement - Core Components Yes
PID01 Communication Manager
PID02 System Manager
PID03 Session Manager
PID04 Communication Server 1000
PID05 Virtualization
PID06 Avaya Session Border Controller Enterprise (ASBCE)
PID07 Presence
4302W Avaya Team Engagement - Gateways and Endpoints Yes
PID01 Gateways
PID02 Branch Gateways
PID03 Endpoints H.323
PID04 Endpoints SIP
PID05 H100 Series Video Collaboration Station
PID06 Avaya J129 IP Phone
PID07 Avaya Vantage
4303W Avaya Team Engagement – Cloud Yes
PID01 xCaaS
4304W Avaya Team Engagement Soft Clients - Components No
PID01 Avaya one-X Mobile
PID02 Avaya one-X Communicator
PID03 Avaya one-X Portal
PID04 Avaya one-X CES
4305W Avaya Team Engagement Applications Components No

avaya.com
PID01 VDI Communicator

PID02 Avaya Agile Communication Environment (ACE)
PID03 AvayaLive Engage
PID04 Avaya Identity Engines
4306W Avaya Messaging No
PID01 Avaya Aura® Messaging
PID02 Hospitality Messaging Server 400
Real-time Communications Applications: Avaya Breeze and Snap-ins No
4310W (Part 1)
PID01 Avaya Breeze
PID02 Snapp Store 1.0
PID03 Avaya WebRTC
PID04 Avaya Engagement Assistant Snap-ins
PID05 Breeze Client SDK 3.0
Real-time Communications Applications: Avaya Breeze and Snap-ins No
4313W (Part 2)
PID01 Avaya Call Park and Page Snap-ins
PID02 Avaya Engagement Designer
PID03 Avaya Aura® Conferencing
PID04 Avaya Message Recording Snap-in
4511W Avaya Scopia Components: Endpoints No
PID01 Scopia XT Executive 240
PID02 Scopia XT 4300, XT5000, XT7100
PID03 Scopia XT Telepresence
4512W Avaya Scopia Components: MCUs/Gateways & Management No
PID01 MCUs
PID02 Avaya Scopia Gateways
PID03 Avaya Equinox Management Server 9.0 and H3.2.3 Gatekeeper

PID04 Avaya Equinox Media Server 9.0
PID05 Desktop Content
4500W Partner Hosted Video Cloud No
PID01 Scopia Cloud Enablement
4514W Avaya Video Cloud No
PID01 AvayaLive Video
4410T APSS Team Engagement Online Test Yes

avaya.com
APDS 3170 – Avaya Enterprise Team Engagement Solutions

https://www.avaya-learning.com/lms/#/training/learning-maps/31
Course Updated for 8.1
Code Title Duration Availability release
(Hours)
Avaya Aura® Solution Overview Update for Aura® 8
31200W 2 Available
(WBT incl. PIDs) – July 10, 2018
Avaya Aura® Solution Customer Field Update for Aura® 8
31500W 1 Available
Study (WBT) – July 10, 2018
Avaya EquinoxTM Solutions Overview
3140W 2.5 Available
(WBT)
Avaya BreezeTM Overview & Field
3160W 2 Available
Study
Avaya EquinoxTM Solutions Customer
3170W 1 Available
Field Study (WBT)
3175T APDS Avaya BreezeTM Online Test 1.5 Available
APDS Avaya Enterprise Team Update for Aura® 8
3171T 1.5 Available
Engagement Solutions Online Test – July 10, 2018

avaya.com
ACDS 3170 – Avaya Enterprise Team Engagement Solutions

https://www.avaya-learning.com/lms/#/training/learning-maps/33
Course Updated for 8.1
Code Title Duration Availability release
(Hours)
Update for Aura® 8 –
31800W Designing the Avaya Aura® Solution 8 Available
October 2018
Designing Avaya Aura® Update for Aura® 8 –
3181T 1.5 Available
Solutions ACDS Online Test October 2018
3185W - Designing the Avaya
3185W 6 Available
Equinox® Solution
Avaya Enterprise Team Engagement
3185X 2 Available
Solutions Design Exam
Implementation and Maintenance Training

ACIS - Avaya Aura® Communication Manager and CM Messaging - Embedded (R6.x)
Learning
Order in Course Delivery
Folder Name Code Title Center
Folder Duration Type
Deployment
Fundamental skills and capabilities to
AvayaLive
maximize the value of this curriculum 1st Avaya Aura®
1A00234E 13 Engage Now
and improve preparation for course Fundamental Technology
Theory
associated exams:

avaya.com
To earn the ACIS 6002- Avaya Aura®

Communication Manager and CM
Messaging - Embedded (R6.x)
credential:
Virtual Campus Training: Knowledge Access: Avaya
Aura® Communication
1st ALE
4U00030E Manager and CM 54 Now
course License
Messaging - Embedded
Implementation
Knowledge Collection
2nd Access: Avaya Unified ALE
0U00110E 151 Now
course Communications Core License
Implementation
Traditional Training: Avaya Aura®
3rd ILT+Lab
4U00030I and CM Messaging - 40 Now
course Level 1
Embedded Implementation
Instructor Led
Avaya Aura®
4th vILT+Lab
4U00030V and CM Messaging - 40 Now
course Level 1
Embedded Implementation
Virtual Instructor Led
Fast Track: Avaya Aura®
5th and CM Messaging- ILT noLab
9U01000I 80 Now
course Embedded Administration Level 1
and Implementation
Instructor Led
(cont'd) To earn the ACIS 6002- Avaya Aura®
Avaya Aura® Communication Communication Manager Exam
Cred 1 6002 1.75 Now
Manager and CM Messaging - and CM Messaging R6.x (Questions)
Embedded (R6.x) credential: Implementation Exam
Maintaining Your Competency 1st What is New in Avaya On

2007W 4 Aug-15
course Aura® 7.0 Recording Demand
What is New in Avaya
2nd On
2009W Aura® Communication 2 Aug-15
course Demand
Manager 7.0 Recording
What is New in Avaya
Assessment
2009T Aura® Communication 1 Aug-15
(LMS)
Manager 7.0 Online Test
3rd Migrating and Upgrading vILT+Lab
2012V 40 Aug-15
course to Avaya Aura® 7.0 Level 1

avaya.com
4th Avaya Aura® 7 vILT+Lab

2013V 40 Aug-15
course Administration Level 1
ACSS - Avaya Aura® Communication Manager and CM Messaging – Embedded

Learning
Deployment
To earn the ACSS - Avaya Aura®
Communication Manager and CM
Messaging - Embedded credential:
Implementation courses and
exams:
ACIS-6002: ACIS - Avaya ACIS - Avaya Aura®
Aura® Communication Manager and Communication
All
CM Messaging - Embedded (6.X) Manager and CM Now
Courses
Messaging -
Embedded R6.x
(cont'd) Implementation courses Avaya Aura®
and exams: Communication
Manager and CM Exam
Cred 1 6002 1.75 Now
Messaging R6.x (Questions)
Implementation
Exam
Administration courses and
exams:
For Avaya Virtual Campus Knowledge Access:
training, select either the Knowledge Avaya Aura®
ALE
Access or the Knowledge Collection 1st course 5U00051E Communication 24 Now
License
Access bundle: Manager
Administration
Knowledge
Collection Access:
ALE
2nd course 5U00170E Avaya Unified 83 Now
License
Communications
Administration
For Traditional Training: Avaya Aura®
Communication
ILT+Lab
3rd course 5U00051I Manager 40 Now
Level 1
Administration
Instructor Led
Avaya Aura®
vILT+Lab
4th course 5U00051V Communication 40 Now
Level 1
Manager

avaya.com
Administration
Virtual Instructor Led
(cont'd) Administration courses Avaya Aura®
and exams: Communication Exam
Cred 2 3100 1.5 Now
Manager (Questions)
Administration Exam
Maintenance and
Troubleshooting courses and exams:
For Avaya Virtual Campus
training, select either the Knowledge
Access or the Knowledge Collection
Access bundle:
Combined Knowledge Access:
Communication Manager and CM Avaya Aura®
Messaging Virtual Campus Choice Communication ALE
5th course 5U00060E 32 Now
Manager and CM License
Messaging -
Embedded Support
Knowledge
Collection Access:
ALE
6th course 5U00160E Avaya Unfired 127 Now
License
Communications
Core Support
(cont'd) Maintenance and Avaya Aura®
Troubleshooting courses and exams: Communication
Manager and CM
Messaging - Exam
Cred 3 3101 1.75 Now
Embedded (Questions)
Maintenance and
Troubleshooting
Exam
Maintaining Your Competency What is New in

On
1st course 2007W Avaya Aura® 7.0 4 Aug-15
Demand
Recording
What is New in
Avaya Aura®
On
2nd course 2009W Communication 2 Aug-15
Demand
Manager 7.0
Recording
What is New in
Avaya Aura®
Assessment
2009T Communication 1 Aug-15
(LMS)
Manager 7.0 Online
Test

avaya.com
Migrating and
vILT+Lab
3rd course 2012V Upgrading to Avaya 40 Aug-15
Level 1
Aura® 7.0
Avaya Aura® 7 vILT+Lab
4th course 2013V 40 Aug-15
Administration Level 1
Aug-15
ACSS - Avaya Aura® Session Manager and System Manager

Learning
Deployment
Fundamental skills and capabilities to Knowledge Access:
maximize the value of this curriculum Avaya Aura® AvayaLive
and improve preparation for 1st course 1A00236E Session and System 15 Engage Now
associated exams: Manager Theory
Fundamentals
To earn the ACSS - Avaya Aura®

Session Manager and System
Manager credential:
training, select either the Knowledge Avaya Aura®
ALE
Access or the Knowledge Collection 1st course 4U00040E Session Manager and Now
License
Access bundle: System Manager
Implementation
Knowledge
Collection Access:
ALE
License
Communications
Core Implementation
Knowledge Access:
Avaya Aura®
ALE
3rd course 5U00050E Session Manager and Now
License
System Manager
Support
Knowledge
Collection Access:
ALE
4th course 5U00160E Avaya Unfired 127 Now
License
Communications
Core Support
For Traditional Training: Avaya Aura®
Session Manager and
ILT+Lab
5th course 9U01003I System Manager 80 Now
Level 2
Implementation,
Administration, and

avaya.com
Support Instructor
Led
Avaya Aura®
Session Manager and
System Manager
vILT+Lab
6th course 9U01003V Implementation, 80 Now
Level 1
Administration, and
Support Virtual
Instructor Led
(cont'd) To earn the ACSS - Avaya Avaya Aura®
Aura® Session Manager and System Session Manager and
Exam
Manager credential: Cred 1 3102 System Manager 1.75 Now
(Questions)
Implementation and
Maintenance Exam

On
Demand
Recording
What is New in
Avaya Aura® System
Manager 7.0 and On
2nd course 2011W 2 Aug-15
Avaya Aura® Demand
Session Manager 7.0
Recording
What is New in
Avaya Aura® System
Manager 7.0 and Assessment
2011T 1 Aug-15
Avaya Aura® (LMS)
Session Manager 7.0
Online Test
Migrating and
vILT+Lab
Level 1
Aura® 7.0
AIPS - Application Enablement Services (AES)

Learning
Deployment
To earn the AIPS - Application
Enablement Services (AES)
credential:

avaya.com
For Virtual Campus training, Knowledge Access:

select either the Knowledge Access or Avaya Aura® AvayaLive
the Knowledge Collection Access 1st course 10U00030E Application 12 Engage Now
bundle: Enablement Services Theory
Implementation
Knowledge
Collection Access:
ALE
License
Communications
Core Implementation
Online Tests: Avaya Aura®
Application Assessment
Cred 1 4100 1.5 Now
Enablement Services (LMS)
Implementation Test

On
Demand
Recording
What is New in
Avaya Aura®
On
2nd course 2008W Application 2 Aug-15
Demand
Enablement Services
7.0 Recording
What is New in
Avaya Aura®
Application Assessment
2008T 0.5 Aug-15
Enablement Services (LMS)
(AES) 7.0 Online
Test
Migrating and
vILT+Lab
Level 1
Aura® 7.0
ASPS - Avaya Aura® Presence Services
Learning
Deployment
Fundamental skills and capabilities to Knowledge Access:
maximize the value of this curriculum Avaya Aura® AvayaLive
1st course 1A00234E 13 Now
and improve preparation for the Fundamental Engage
associated exams: Technology
To earn the ASPS - 5100 Avaya

Aura® Presence Services credential:

avaya.com
Courses:
training, select either the Knowledge Avaya Aura® AvayaLive
Access or a Knowledge Collection 1st course 8U00170E Presence Services 12 Engage Now
Access bundle: Implementation and Theory
Support
Knowledge
Collection Access:
ALE
License
Communications
Core Implementation
(cont'd) Courses: Knowledge
Collection Access:
ALE
3rd course 5U00160E Avaya Unfired 127 Now
License
Communications
Core Support
For Traditional Training: Fast Track: Avaya
Aura® Presence
Services and Avaya
UC Soft Clients ILT+Lab
4th course 9U01002I 40 Now
Implementation, Level 1
Administration, and
Support Instructor
Led
Fast Track: Avaya
Aura® Presence
Services and Avaya
UC Soft Clients vILT+Lab
5th course 9U01002V 40 Now
Implementation, Level 1
Administration, and
Support Virtual
Instructor Led
Online Tests: Avaya Aura®
Presence Services Assessment
Cred 1 5100 1 Now
Implementation and (LMS)
Maintenance Test

On
Demand
Recording
What is New in
Avaya Presence On
2nd course 2010W 1 Aug-15
Services 7.0 Demand
Recording

avaya.com
What is New in
Avaya Presence Assessment
2010T 0.5 Aug-15
Services 7.0 Online (LMS)
Test
9.2. Technical/ Knowledge Transfer

The Avaya Aura® 8.1.1 Tech Transfer is still in planning at the time of update of this document. The recorded
sessions will be posted after the event.
The Tech Transfer reordings for Aura® 8.0 have been posted at the following link, including the live Q&A from
the event.
Tech Transfer Link:

https://sales.avaya.com/en/events/1399702928660&et=pe
For a period of time the Tech Transfer recorded sessions are still available to view “on demand”.
On Demand Videos:
Day 1 Day One Video
Day 2 Day Two Video
Day 3 Day Three Video
Day 4 Day Four Video

avaya.com
10.0 Product Ordering, Licensing and Pricing

The Avaya Aura® solution is predominately sold and licensed based the service and functionality required by
each user in the solution. This enables flexibly to configure the solution to the needs of the user today and uplift
as the need evolves. Avaya Aura® solution offers user licenses for Analog, Basic and Enhanced IPT (Specific
use cases and device support) and Suites of capabilities targeted to unified communication for the mobile user and
team engagement power users. The solution offers many deployment model choices as well as a la carte options.
See Appendix for Aura® License Transaction Definitions .

avaya.com
Figure 1: Avaya Aura® Licensing Benefits
10.1. Buy to Current

With the introduction of Aura® R8, there are now 2 release levels available, R7 which is the N-1 and R8 which is
the N release. Buy to Current (BTC) order process is in effect. Buy to Current requires customers to always
purchase the most current software release offer (N) for New and Upgrades, including the Support offer. The
customer licensing PLDS record is set to Buy to Current R8 but the customer has the choice on whether to deploy
as the N (R8) or the N-1 (R7). If the customer chooses to deploy as R7, their PLDS license records continue to
have the Aura® R8 licensing available for deployment at a future time.
 BTC process does NOT change the normal software release lifecycle planning. When an N-1 release is
made end of sale (EOS), the tools will be updated and only offer the N release for deployment.
Avaya Aura® Suite Licensing (including all the Suite entitlement products), Session Manager, System Manager,
AES, ASBCE and CC Elite leverage the Buy to Current Process.
Read the Buy to Current Offer Definition for more detail
Buy to Current applies to

• All New system licenses
• All License Upgrade/ASIPP transactions
o Entire system instance is being upgraded
o Partial license upgrade and move to another target system: The upgraded licenses will go
into BTC R8 format, even if they are to be deployed as R7.
This means the target system must also be in BTC R8 record format.
▪ If the target system is R6 or lower, it must be upgraded to R8 but can choose to
deploy as R7
▪ If the target system is R7 (non R8 BTC), it must have a design and order to R8, the
target system can remain deployed as R7. This will put the system records in R8
BTC/deployed as R7 to match the licenses being upgraded and moved to it.

avaya.com
• License ADDs (Capacity expansions) to a system that is in R8 BTC/deployed as R7

o Adds are purchased as R8 BTC but deployed as R7
License Adds to a system that is currently deployed as R7 (not buy to current R8)
Originally order or Deployed Adding User License Capacity

upgraded to as
R7 Aura®
Non Buy to Current R7
Order R7 only (Non BTC R8) Add Licenses
Aura® R7 Aura®
Buy to Current R7
Aura® R7 Aura® 1) Deploy the customers R7 Upgrade 2) Order R7 only (Non
Buy to Current R6 entitlement to system instance BTC R8) Add Licenses
For systems deployed as Aura® R6 or CM R5 and earlier, upgrade to Current to Add

capacity
 Avaya Aura® R6 ADD/Uplift licenses are End of Sale as of July 9, 2018.
 All R5 and previous Add/Uplift license is also End of Sale
To Add Aura® User capacity these systems must be upgraded to current release level.
Originally order or Deployed Adding User License Capacity
upgraded to as
Aura® R7 Aura® 1) Deploy the customers R7 2) Order R7 only
Buy to Current R6 Upgrade entitlement to (Non BTC R8)
system instance Add Licenses
Aura® i. Order upgrade BTC R8 2) Order R8 BTC Add Licenses
Aura® R6
R6
Non Buy to Current And Deploy as R7 Deploy as R7
Or
Or
CM R5 or Or Deploy as R8 Deploy as R8
CM R5 or earlier
earlier
o To Add to a system that is R7 BTC but deployed as R6, the System must deploy its R7
upgrade entitlements (ie deployed and running as R7). Any future Adds to this system are
purchased as R7 (non BTC)
o To Add to a system that is R6 non Buy to Current /deployed as R6, the system must upgrade
to BTC R8, it may deploy as R8 or R7. Adds are ordered as BTC R8 and can be deployed as
R8 or R7.

avaya.com
10.2. Avaya Aura® User Licensing
Avaya offers a wide variety of license types to meet both the current and future customer user needs. Because the
license types can be mixed on the same system instance, the customer can design their licensing needs and costs
to meet their current user needs with the ability to uplift to a higher capable and value licenses in the future to
meet changing business needs.
Avaya does not have a license downgrade offer, however as part of customer migrations, particularly from older
systems there was only one type of license permitted on a single system, it can be beneficial to reconstruct the
customers licenses assets as part of an upgrade design.
See Appendix for Reconstructing License Assets
Suite Licensing
Avaya Aura® Licensing Suites help sell collaboration that addresses business issues, not selling just features but
true business solutions using Avaya collaboration.
Suites offer new customers a very competitive set of features and services, making the decision to move to Avaya
collaboration solutions simpler and the result much more cost effective.
Suites are important to modernization of legacy customers offering them features bundles that provide complete
sets of the features customers are looking for; mobility, video, messaging.
The objectives of Avaya Aura® Suites Licensing are to:

• Further simplify Unified Communications licensing for customers and channels
• Incorporate new products and capabilities in an easily scalable structure
• Spotlight Avaya’s differentiation while accelerating the adoption of new applications
• Offer better price/value for UC solutions than competitors
o Product and ongoing Service/Maintenance.
Avaya Aura® Suite Licensing was simplified in November 2014 from the initial 3 licensing packages
(Foundation, Mobility and Collaboration Suites) to 2 licensing packages (Core and Power Suites).

avaya.com
The Core Suite bundles the Avaya Aura® infrastructure licenses into one SIP core purchase, along with the key
UC applications to support BYOD and the increasingly mobile workforce with secure desktop/mobility user
applications.
✓ Aura® R8 Core Suite is updated to include
• the Enhanced level of Multi Media Messaging
• Equinox for Web
• Messaging choice of either Avaya Aura® Messaging (AAM) or OfficeLinx (OL) Basic.
o Like AAM Basic Entitlement, the OL Basic entitlement of Core Suite can be uplifted to
Mainstream.
The Power Suite bundle includes and builds on the Core Suite extending the value for team engagement Complete
UCC feature set for business solution, offering enterprise user collaboration and secure mobility.
✓ Aura® R8 Power Suite is updated to include
• Messaging choice of either Avaya Aura® Messaging (AAM) or OfficeLinx (OL) Mainstream
The original Foundation Suite, which focused on business telephony, continues to be available as the $0
entitlement upgrade path from older licensing constructs* that carry Upgrade Entitlement (SS+U, Upgrade
Advantage (UA) or SRR Pass+).
* Standard Edition (SE), Enterprise Edition (EE), CS1000 IP/Digital (via ASIPP Avaya Software Investment
Protection Policy)
Basic User Licensing; Analog, IPT Basic and IPT Telephony

Avaya also offers Basic user licenses for common areas, users with more basic communications needs and
verticals such as hotel guest /healthcare patient rooms or manufacturing floor common areas. These use cases
may be more suited to be serviced by an Analog, IP Telephony (IPT) Basic or Enhanced level license. These
licenses provide fit for purpose service now and can be uplifted to Suites as the user needs evolve.
These licenses are not supported for Call Center Agents
The objectives of Avaya Analog, IPT Basic and IPT Enhanced Licensing are to:
• Match the licenses service level to the users current needs
• Easily uplifted in the future as the user needs evolve
• Offer better price/value for basic users as part of the overall UC solution
o Product and ongoing Service/Maintenance.
o Consider aa an option for basic users when upgrading existing SE, EE or Foundation
licenses. See Appendix for Reconstructing License Assets
IPT Basic and Enhanced licenses have been GA available since 2013 with Avaya Aura® R6, however they have
been under password control.
 With Aura® R8 password control has been removed; IPT Licenses will be configurable in the A1S
tools without password.
A1S tools will still enforce the IPT license requirements and restrictions
• 20% of the system user licenses must be Suites (20% of total of Suites, Analog and IPT)
• Do not Support Multiple Device Access (MDA)
o -These are 1 License/1 Device/ 1 User licenses
• IPT licenses have limited a la carte add ons

avaya.com
o Messaging
o EC500
• IPT Licenses requires specific device attach (as part of the design)
 Avaya Devices only; No Device Substitutions
o Basic IPT Supported Devices

▪ 1603, 1603SE_i (H.323), E129 SIP, J129 SIP*, 139 SIP*
o Enhance IPT Supported Devices
▪ 9601 SIP, J129 SIP, J139 SIP*
*For J129 and J139 capabilities vary on IPT License. Security features (SRTP, TLS, encrypted SRTCP,
Certificates) and Geo Redundancy are available with the Enhanced IPT license only.
Avaya devices support on the IPT Licenses is assessed as new devices are brought to market based on use case fit
and function for IPT licensing.
See IPT License Offer Definition for more detail
Aura® R8 Suite Entitlement Changes and Detail Description
Core Suite Entitlements

Product/Application Description Aura® 8 Deltas
& Comments
Aura® CM Avaya Aura® Communication Manager is the
open, highly-reliable and extensible IP
Telephony foundation on which Avaya delivers
Unified Communications solutions to enterprises
large and small.
Avaya Aura® Suites Licensing delivers this IP
Telephony foundation to each user, supporting up
to 10 SIP devices per named user.
System Manager Avaya Aura® System Manager is the central
administration component for Avaya Aura®
Session Manager+ Avaya Aura® Session Manager+, enables a +With Avaya Aura®
distributed system featuring multi-vendor R7 and continuing
integration, centralized dial plans and user forward with Aura®
profiles, easier centralized SIP trunking, easier R8 Suites, the Session
“on-net” call routing, and enhanced scalability Manager is not a
and security. specific entitlement at a
per license basis but is
licensed at the System
level and provided
unlimited SM sessions.
Existing Session
Manager instances
upgrading to R7 and
beyond will be
grandfathered the

avaya.com
unlimited session
Session Manager
System License.
IM and Presence Avaya Aura® Presence Services is a foundational
element utilized by Avaya and third-party
applications to collect and distribute rich
Presence information and Instant Messaging (IM)
capabilities throughout an enterprise.
Breeze™ Platform The Breeze™ Platform provides the
infrastructure for the IM and Presence services.
One Breeze™ instance is entitled on new or
Presence upgrade. The instance is a Closed
instance and is only for use with Avaya Aura®
Presence and IM services and/or Call Park and
Page Snap-in and/or the new Avaya Device
Adapter Snap-in
Breeze™ User The Breeze™User entitlement specifically is a
Right to Use concurrent user license that enables
the Enterprise to deploy the applications
developed internally or by a partner across the
targeted user base.
AES Unified Desktop Unified Desktop is a licensed feature on
Application Enablement Services that provides
TR-87 connectivity for desktop, mobility clients
and other applications that require it.
Avaya Communicator Avaya Communicator for Microsoft Lync
for Microsoft Lync extends Avaya Aura® voice, video, and
telephony presence into the Lync / Skype for
Business experience for both Lync /Skype for
Business on premise and Office 365
deployments.
UC Desktop and Avaya Equinox is a SIP-based unified ✓ Avaya Equinox for
Mobility Clients communications client with real time Web is a new R8
collaboration capabilities that enable business Suite entitlement
users to easily manage their day-to-day including in Core
communications from a single interface. High and Power Suites
performance multimodal sessions; VOIP,
IM/presence, web conferencing and point-to-
point and multiparty video propel users through
buddy and contact centric workflows with
contextual controls.
Equinox clients are available for Desktop
(Window and Mac) and Mobile (iOS and
Android)

avaya.com
Avaya Equinox for Web is the HTML5 based

client that optionally connects to the server
(Cloud Application Link) for desktop phone
control (CTI) and Avaya AADS/ACS (directory
services) and AAWG (required for WebRTC
media and softphone functionality). The browser
extension provides a streamlined, easy to use
experience with a style familiar to customers
using mobile, cloud, and browser-based
applications
Avaya one-X® Client Enablement Services is a

single platform that delivers Avaya Aura®
communication services to one-X® UC clients
including one-X ® Mobile and one-X
®Communicator. It delivers BYOD security
features for confident deployment of enterprise
communications and personal devices.
The powerful Extension to Cellular feature of

Avaya Communication Manager enables users to
remain productive while mobile with one number
and one voicemail capability.
Peer to Peer Video Enables peer to peer video on Avaya Aura® for
the desktop clients
Messaging At Avaya Aura® R8 there is a choice of
Avaya Aura® Messaging (AAM) Basic OR The Basic AAM or OL
OfficeLinx (OL) Basic. Core suite entitlement
Avaya Aura® Messaging (AAM) is Avaya’s can be uplifted to
flagship messaging solution for unified Mainstream level
messaging that leverages industry standards to
flexibly
integrate within the Avaya Aura® architecture in
Linux based server environments. The Core
Suite includes a Basic license entitlement to
Avaya Aura® Messaging.
OfficeLinx (OL) is Avaya’s flagship unified New System Core and

messaging solution that can integrate with any Power Suites will not
telephony environment and offers integration entitle CMM as it is
with 3rd party email solutions like Office 365 or now End of Sale for
Gmail. New systems. R8 Add
See Officelink R10.7 Offer Definition licenses will continue
to entitle CMM.

avaya.com
Communication Manager Messaging is the CM Upgrades will carry

embedded messaging platform that delivers voice forward the CMM
and text messaging to help improve entitlement
communications and simplify information
exchange between enterprises.
Session Border Avaya Session Border Controller for Enterprise 1 HA Remote Worker
Controller – Remote (ASBCE) is the secure pivot point for all SIP entitlement equates to
Worker and SIP communications in and out of Avaya the following license
Trunking implementations. provisioned:
Entitlement is: 1 ASBCE STD
Qty 1: High Availability Remote Worker 1 ASBCE STD HA
Session for every 7 Core and/or Power Suite 1 ASBCE Adv
licenses 1 ASBCE Adv HA
AND 1 HA SIP Trunking
Qty 1: High Availability SIP Trunk for every 7 Session entitlement
Core and/or Power Suite licenses. equates to the
following license
provisioned:
1 ASBCE Std
1 ASBCE Std HA
Avaya Multimedia AMM Provides users with the ability to send & R8 provides Enhanced
Messaging receive all message content types, attach files, AMM entitlement
record and send multimedia messages
Power Suite entitlements

includes all the entitlements in the Core Suite with the following enhancements and additions:
Product/Application Description Aura® 8 Deltas
& Comments
Messaging Avaya Aura® Messaging(AAM) Mainstream
OR OfficeLinx (OL) Mainstream
Avaya Aura® Messaging (AAM) – Mainstream

license – includes all the features of the
Basic license as well as Find Me/Notify Me, one-
X Speech based features, Messaging access
(web).
OfficeLinx Mainstream (OL) includes all the OL Integrated FAX

features of the Basic license as well as entitlement requires a
FindMe/NotifyMe and options to use speech la carte purchase of the
based features like ASR and VTT as well as Fax. associated Fax Ports
Conferencing Avaya Equinox Conferencing extends Note Core License and

multimodal capabilities—for audio conferencing, lower licenses may

avaya.com
web collaboration, video and more—to tens of leverage the Avaya

thousands of workers, virtually anywhere, at a Aura® CM native
fraction of the cost of other solutions. Audio 6 Party
Conference and Meet
Me Conference
or Uplift some or all
users to Power Suite
for the Avaya Equinox
Conferencing advanced
capabilities
10.2.3.1. R8 User License Entitlement Value Comparison Summary
10.2.3.2. Officelinks R10.7 Messaging Option Entitlement

With Officelinks release 10.0 functionality is available as a Suite entitlement as one of the Messaging Options.
Officelinks (OL) functionality for Aura® is licenses in two levels Basic and Mainstream, just like Avaya Aura®
Messaging. The value prop is aligned to be consistent with Avaya Aura® Messaging Basic and Mainstream.
Please see OfficeLinks Offer Definition for full detail and other a la carte Officelinks a la carte options.
(Product Management: Cyril Dowling Dowling, cdowling@avaya.com )
 Officelinks R10.7 GA lags the Aura® 8 GA by 30 days, any Aura® New or Upgrade to Core or Power
will still be provided the option to choose OfficeLinks Messaging option, but this will not be available for
deployment until OL 10.7 achieves GA.
Within the Aura® R8 Suite

• Core Suite will entitle option of AAM or OfficeLinx at the Basic level

avaya.com
o The Core Suite AAM or OL entitlement can be uplifted to Mainstream

• Power Suite will entitle option of AAM or OfficeLinx at the Mainstream level
During A1S design of New or Upgrade you will be offer a choice of AAM or OL for the Suite Messaging
entitlement. You must choose one or other (cannot have a mix).
Customers with existing AAM suite entitlements at upgrade can choose to exchange these for the Aura® R8 Suite
OL entitlement. The AAM entitlements will be removed from customer records and replaced with OL
entitlements.
Note: Suites entitle the user licensing and not the infrastructure to deploy
Below is Matrix of Value of the Mainstream level for either AAM or OL

Feature AAM or OL
Mainstream
Messaging Web Access Y
Speech Recognition for Addressing Y
Speech based Auto Attendant Y
Speech to Text with AMS (Mutare) Y
Detect and transfer to a fax server Y
(for OL Fax ports are a la carte)
Receive and forward fax to an email client Y
Send from desktop fax client Y
Notify Me Y
Text Message and Pager Y
Phone call to telephone or mobile device Y
Email copy Y
Pending deletion of messages Y
Consultative transfers from Call Sender, Call Y
Application and Auto Attendant
Transfer to Mailbox from Caller Applications Y
10.2.3.1. Avaya Aura® R8 Available License Types Summary

Aura® R8 New/ Upgrade from Sales Motion
License Types Add
(Perpetual)
Aura® R8 Y Power Suite • Incentive pricing to UPLIFT to
Power Suite or R6 Suites V1 Collaboration Suite Power at time of Upgrade
Aura® R8 Y Core Suite • Primary License level for UC users
Core Suite Or R6 Suites V1 Mobility Suite • License level for CC Elite Agents
Aura® R8 N Only as $0 landing point for • Consider paid Uplift to Core at time
Foundation Suite Licenses upgrading with Upgrade of Upgrade or post upgrade to take
Entitlement (UA, SS+U ASIPP advantage of Core Suite
SRS PASS) Entitlements such as included

avaya.com
From: Messaging, ASBCE, Equinox

Standard Edition (SE) Clients and Mobility.
Enterprise Edition (EE) • If the customer has a la
R6 or R7 Foundation level carte/competitive messaging/SBC,
consider forfeiting these and
No ADDS in Foundation in R8 leveraging the suite entitlements for
(same as R7) the more favorable Suite bundled
Product and Service Support pricing
Aura® R8 IPT Y IPT Enhanced* • Can be uplifted to Core or Power
Enhanced once upgraded
Aura® R8 IPT Y IPT Basic* • Can be uplifted to IPT Enhanced*,
Basic Core or Power once Upgraded
Aura® R8 Analog Y Analog • Can be uplifted to IPT Basic*, IPT
Enhanced*, Core or Power
*appropriate supported device must be purchased with the IPT Basic and Enhanced Licenses
License Constructs / Transactions not available in Avaya Aura® 8 (same as Aura® R7)
• Legacy Standard Edition (SE) and Enterprise Edition (EE) Licenses;
o On Paid Upgrade the go to R8 Core
o On Entitled Upgrade (SS+U, UA or ASIPP SRS Pass+) will go to R8 Foundation for $0
• Suites Version 1 (V1)
o Mobility Suite: go to Core for both Paid and Entitled Upgrades
o Collaboration Suite: go to Power for both Paid and Entitled Upgrades

avaya.com
10.2.3.2. Propose the Right Mix of Licensing for User Needs
10.2.3.1. Incentive for Uplifting to Power Suites AT time of Upgrade

avaya.com
License Mixing Compatibility

The different Avaya Aura® User license types are generally compatible on the same system instance
records/deployment. This allows the flexibility to match the license to the user need for the best TCO and user
value. As a users need changes the license can be uplifted the a higher value level.
The licenses supported on R8, Analog, IPT Basic, IPT Enhanced and Suites (Foundation, Core and Power) can all
co-reside on the same system instance,
 However, the Suites Version 2 (SV2) offer rules still apply so care must be taken when
upgrade/merge/moving between certain types of systems. See table below
(The target system instance may also include Analog, IPT Basic, IPT Enhanced, the important delineator is the
Suite license type on the Target system vs the Donor license type)
Licenses that
✓ Can
Target R7 / 8
Action to take to make a
System Instance  Cannot Notes
license compatible
Suite License construct be moved to this
Target system
without Uplift
Suites V2 Core and ✓ Suites V2 To move/merge a All New systems are
Power only Core and Power Foundation license to a only being ordered as
Suites V2 only system Suites V2 so any Suite
 NO Foundation
the Foundation license licenses moved to a
✓ IPT Enhanced, must be Uplifted to NEW system must be
IPT Basic, Analog Core or Power as part minimum Core/Power
of the move transaction
Mix of ✓ Suites V2
SuitesV1 Foundation Core and Power
Suites V2 Core Power
✓ Suites V1
Foundation
✓ IPT Enhanced,
IPT Basic, Analog
Suite V1 Foundation ✓ Suites V2
only Core and Power
✓ Suites V1
Foundation
✓ IPT Enhanced,
IPT Basic, Analog
10.3. Avaya Aura® Licensing Competitive Position
Avaya Aura® ® Licensing is simpler and very competitively positioned in value and price. One of the keys is to
ensure you are positioning the license level that maps competitively and position the inclusions of SBC and

avaya.com
messaging vs competitor license add ons, which affect both the product license price but also ongoing
maintenance support costs.
• Avaya Power Suite maps to Cisco CUWL Meeting license

o Avaya Price favorable
o SBC/Remote Users are included
• Avaya Core Suite maps across the more complex Cisco variety of offers, Enhanced UCL, Enhance
Plus UCL and CUWL Standard.
The Avaya Core Suite offers is competitively priced and offers more value
o Includes Messaging (OfficeLinx or Avaya Aura® Messaging) - messaging is a Cisco adder
o Includes SBC/ Remote User – this is a Cisco adder
o Includes MDA (Multi Device Access) - up to 10 SIP devices per licenses - Cisco requires the
CUWL standard license to match.
• Avaya Foundation Suite licenses are not offered for New or ADD on R7/R8 but as available as the
Entitled Upgrade $0 landing point. Foundation roughly maps to Cisco Enhanced UCL/Plus UCL.
• Avaya IPT Licenses map very directly to Cisco basic licenses in functionality, price and type of device
supported.
 Be careful to avoid the Name trap
o Avaya IPT Basic maps to Cisco Essential UCL not the Cisco Basic UCL
o Avaya IPT Enhanced map to Cisco Basic UCL
• Avaya Analog Licenses map directly to Cisco Analog license.
10.4. Aura® R8 License Format

Avaya Aura® R8 will offer Perpetual format licenses only at the initial GA July 9, 2018.
Perpetual licensing is a CAPEX license purchase.
Avaya Aura® R8 will discontinue the OPEX Fixed Term Enterprise Entitled License Offer which was introduced
October 10, 2016. This OPEX offer will be replaced by an OPEX usage Enterprise Pay Per Use (PPU) offer. The

avaya.com
Enterprise PPU solution will only be available to customers deploying at the R8.X level. The timing and details
of the R8.x PPU offer is not at Commit stage and therefore still to be confirmed.
 The Avaya Aura® R7 OPEX fixed term Enterprise Entitled License Offer will continue to be available
for customers that carry Upgrade Advantage or SS+U who Upgrade and deploy on Aura® R7. An
exception approval will be required from Avaya Aura® Product Management to design to this
configuration. Customers choosing this path, when upgrading to Aura® R8 or beyond will be required to
convert this Fixed Term solution into the then available Avaya Aura® Enterprise Pay Per Use offer.
See the Enterprise Entitled Licensing Offer Definition for more details
10.5. Avaya Aura® Session Manager Licensing Changes, starting in Avaya

Aura® R7
The new Session Manager licensing policy makes it easier and more cost effective to position Session Manager
value as customer move to more SIP use in their network. With R7 there are no longer connection license needs
to be calculated. With the Session Manager system license and a suite license, customers have unlimited use of
their Core and Branch Session Managers.
System License vs. Connection License

Starting with the release of Avaya Aura® Session Manager 7, connection licenses are no longer
required. Avaya Aura® Session Manager will now be available with unlimited connection use. A
single system level license is now required for each Session Manager/Branch Session Manager
instance. See the product ordering section for the codes required.
Any instance upgrading from a previous release of Avaya Aura® Session Manager will automatically
have their connection licenses converted to the system license at no charge.
Summary of the Changes

Avaya Aura® Session Manager/Branch SM evolution - Upgrade to Release 8.1 scenario
 Customers on Avaya Aura® Session Manager 6 and earlier that currently have a Session Manager
or Branch Session Manager (BSM) are grandfathered to the new SM System license upon upgrade
to Avaya Aura® 8.1.1.
 Avaya Aura® 8.1.1 Suites Licenses will not show a Session Manager /E entitlement code because
with the System License inclusion there is now unlimited use of Connections/Session.
The Session Manager System License entitlement will be on the order and display in PLDS
entitlements.
 The System License simplifies the Session Manager usage entitlement and prevents issues of
rd
exceeding connection license allotment and incremental cost previously associated with 3 party
connections.
 NOTE: All SM upgrades should be done via A1SC/ASD so the appropriate codes are added to the
customer order/record.
Avaya Aura® Session Manager/BSM evolution - New or Add to Release 8.1.1 scenario
 Customers purchasing NEW or ADDING Session Mangers or Branch Session Manager (BSM)
purchase a Session Manager System license. This is a one-time purchase for the instance and
provides the value of Unlimited Connections/Session.
 Avaya Aura® 8.1.1 Suites Licenses will not show a Session Manager /E entitlement code because
with the System License inclusion there is now unlimited use of Connections/Session.
The Session Manager System License entitlement will be on the order and display in PLDS

avaya.com
entitlements The System License simplifies the Session Manager usage entitlement and prevents
rd
issues of exceeding connection license allotment and incremental cost previously associated with 3
party connections.
 NOTE: All BSM upgrades should be done via A1SC/ASD so the appropriate codes are added to the
10.6. Presence Licensing in Avaya Aura® 8

With the introduction of the Avaya Breeze™ (Avaya Breeze™) based deployment model of Aura® Presence
Services, there are some corresponding licensing changes. In Avaya Aura® 8.1.1 Presence Services are deployed
across one or more instances of a dedicated (Closed) Avaya Breeze™ server plus optionally a set of Open
(general purpose) Avaya Breeze™ server instances which allow Avaya Breeze™ applications to interact with the
PS Connector snap-in.Customers are entitled to a single closed Avaya Breeze™ server instance license – all other
instances of Avaya Breeze™ are paid instances.
The Snap-ins for Presence Services are also licensed but there is no charge associated with these items.
10.7. Upgrade Advantage with Avaya Aura® 8
With Aura® R8 offer introduction the Upgrade Advantage upgrade entitlement is part of the Support Advantage
(SA) Preferred offer and order code.
Per Buy to Current policy, upgrades and New systems will buy to the current Aura® R8 offer, this includes the
R8 SA Preferred offer even if the plan is deploy Aura® R7.
Upgrade Advantage helps customers stay competitive and meet their business objectives by staying up to date
with the latest innovative technologies in a predictable operating expense model. the Aura® R8 SA with upgrade
entitlement enables customers to upgrade their Avaya provided software user/session licenses to the latest Major
Release, if and when available. Upgrade Advantage covers the application software user/session licenses but does
not cover any infrastructure or operating environment software that may be necessary. This policy aligns with
industry practices.
Reference Service Description; Service Agreement Supplement at
UA follow the timelines and conditions of the Maintenance Support Contract Recast Structure See Appendix F.
• Systems doing a Transactional (Paid) upgrade to Avaya Aura® recast their support agreement.at the
time of upgrade. Now of, Upgrade Advantage will be a requirement on the order.
• Systems doing an Entitled upgrade follow the guidelines in Appendix F. When the Maintenance Contract
opens for Recast, Upgrade Advantage is applied/renewed.
10.8. Product Order Codes and Pricing

Suites Order Codes and Pricing
See Appendix for Suite License Entitlements Material Codes

avaya.com
Note 1 Your Avaya Aura® Core and Power Suites entitles you to Avaya Session Border Controller for Enterprise (ASBCE) Licenses. You
are entitled to ASBCE R8 if or when it becomes available. Currently you are entitled to the ASBCE R7 Suite license entitlement. To
design ASBCE R7 in A1S, at the ASBCE deploy as question you will select “R7”.
Note 2 Your Avaya Aura® Core and Power Suites entitles you a Messaging option of either Avaya Aura Messaging (AAM) or OfficeLinx.
OfficeLinx R10.7 is expected to GA slightly after Aura R8. You may select OfficeLinx as your messaging entitlement and can deploy it if
or when it GA’s. You have the option to select the AAM messaging entitlement as an alternative.
Material Description APL Use Scenario
Code
New
396794 AURA® R8 CORE NEW LIC $ 300.00 New Core Lic
396795 AURA® R8 POWER NEW LIC $ 400.00 New Power Lic
Add/Expansion
396798 AURA® R8 CORE ADD LIC $ 300.00 Add Core Lic
396799 AURA® R8 POWER ADD LIC $ 400.00 Add Power Lic
Upgrades: Entitled
397097 $0 Entitled $0 Landing point option; Upgrade
AURA® R8 FND UPG/UPL ENTITLE LIC
to SV1 Foundation
397075 $0
AURA® R8 FND ASIPP SRS LIC
$0 Entitled Move/Uplift – used for entitled
397105
AURA® R8 FND MOVE/UPL ENTL LIC upgrade/move of SE/EE to R8 Foundation
397098 AURA® R8 CORE UPG ENTITLE LIC $0 Subcription upgrade Core to Core
397100 AURA® R8 CORE UPG/UPL UA LIC $ 25.00 Entitled upgrade and uplift to Core
397072 AURA® R8 CORE ASIPP SRS LIC $ 25.00 ASIPP upgrade and uplift to Core
397099 AURA® R8 POWER UPG ENTITLE LIC $0 Subsription upgrade Power to Power
Entitled upgrade and uplift to Power from
397101 and R6 or lower SE/EE, R6 Foundation or
AURA® R8 POWER UPG/UPL UA FRM BASE $ 80.00 R6 Core licenses
Entitled Mobility upgrade and uplift to
397102
AURA® R8 POWER UPG/UPL UA FRM MOB $ 80.00 Power
397074 AURA® R8 POWER ASIPP SRS LIC $ 80.00 ASIPP upgrade and uplift to Power
Upgrades: Transactional (Paid)
397092 AURA® R8 CORE UPG/UPL LIC $ 93.00 Transactional (Paid) upgrade to Core
Transactional (Paid) Upgrade to R7 Power
397094 AURA® R8 POWER UPG FRM CLB/POWER LIC $ 125.00
from R6 Collaboration or Power
Transactional (Paid) Upgrade and uplift to
397093 AURA® R8 POWER UPG/UPL LIC $ 180.00 Power from EE/SE/Foundation, Core,
Mobility
397071 AURA® R8 CORE ASIPP LIC $ 93.00 ASIPP Tranactional (Paid) upgrade to Core
ASIPP Tranactional (Paid) upgrade to
397071 AURA® R8 POWER ASIPP LIC $ 180.00
Power
Move/ Uplift
397103 AURA® R8 CORE MOVE/UPL LIC $ 93.00 Paid upgrade to Core and Move
Entitled move & Uplift Foundation to Core
397106 AURA® R8 CORE MOVE/UPL UA LIC $ 25.00
Uplift

avaya.com
Entitled upgrade, move and uplift to Power

397107 AURA® R8 POWER MOVE/UPL UA LIC $ 80.00 from and R6 or lower SE/EE, R6
Foundation or R6 Core licenses
Transactional (Paid) upgrade move and
397104 AURA® R8 POWER MOVE/UPL LIC $180.00 Uplift to R7 Power from SE, EE,
Foundation, Core or Mobility
Uplift only
Entitled R7.0 Foundation to Core Uplift
397080 AURA® R8 CORE UPL UA FROM FND LIC
$ 25.00 (Entitled Loyalty pricing)
397088 AURA® R8 CORE UPL FROM FND LIC $ 50.00 R7.0 Foundation to Core Uplift
Supscription uplift Foundation to Power
397087
AURA® R8 POWER UPL UA FROM FND LIC $ $125.00 (Entitled Loyalty pricing)
397089 AURA® R8 POWER UPL FROM FND LIC $ 130.00 Uplift Foundation to Power
397085 AURA® R8 POWER UPL FROM CORE LIC $ 100.00 Uplift Core to Power
397078 AURA® R8 CORE UPL FROM ANLG LIC $ 260.00 Uplift Analog to Core
397081 AURA® R8 CORE UPL FROM BASIC IPT LIC $ 260.00 Uplift Basic IPT to Core
397083 AURA® R8 CORE UPL FROM ENH IPT LIC $ 175.00 Uplift Enhanced IPT to Core
397079 AURA® R8 POWER UPL FROM ANLG LIC $ 360.00 Uplift Analog to Power
397082 AURA® R8 POWER UPL FROM BASIC IPT LIC $ 360.00 Uplift Basic IPT to Power
397084 AURA® R8 POWER UPL FROM ENH IPT LIC $ 275.00 Uplift Enhanced IPT to Power
Analog and IPT License (specific use) order Codes and Pricing
IPT Basic and Enhances are specific scenario use licenses. Please consult IPT offer definition
Avaya Aura® IPT Licensing Offer Definition
Code
New
397108 AURA® R8 ANALOG NEW/ADD LIC $ 40.00 New Analog
396792 AURA® R8 BASIC IPT NEW LIC $ 40.00 New Basic IPT
396793 AURA® R8 ENH IPT NEW LIC $ 125.00 New Enhance IPT
Add
397108 For Analog use the NEW Analog Lic code $40.00 Add Analog ; same code as NEW
396796 AURA® R8 BASIC IPT ADD LIC $ 40.00 Add Basic IPT
396797 AURA® R8 ENH IPT ADD LIC $ 125.00 Add Enhance IPT
Upgrade: Entitled
397110 AURA® R8 ANALOG ENTITLE LIC $0 Entitled upgrades for Analog, IPT Basic
397095 AURA® R8 BASIC IPT UPG ENTITLE LIC $0 and Enhanced
397096 AURA® R8 ENH IPT UPG ENTITLE LIC $0
Upgrade: Transactional (Paid)
397109 AURA® R8 ANALOG UPG LIC $ 8.00 Transactional (Paid) upgrades for Analog,
397090 AURA® R8 BASIC IPT UPG LIC $ 8.00 IPT Basic and Enhanced
397091 AURA® R8 ENH IPT UPG LIC $ 25.00
Move and Uplift

avaya.com
397111 AURA® R8 ANALOG MOVE LIC $ 8.00 Upgrade/ Move

397112 AURA® R8 ANALOG MOVE ENTL LIC $0 Entitled Upgrade/ move
Uplift
397076 AURA® R8 BASIC IPT UPL FROM ANLG LIC $0 Uplift Analog to Basic IPT
397077 AURA® R8 ENH IPT UPL FROM ANLG LIC $ 85.00 Uplift Analog to Enhanced IPT
397080 AURA® R8 ENH IPT UPL FROM BASIC LIC $ 85.00 Uplift Basic IPT to Enhanced IPT
Avaya Aura® Communication Manager Order Codes and Pricing
Material Code Description APL

700514751 AURA® CM R8.1 SOFTWARE DVD
700513990 AURA® CM R8 SOFTWARE DVD $50
397174 AURA® R8 CM VE VAPP SYS ENABLE $0
397175 AURA® R8 CM DUP VE VAPP SYS ENABLE $0
397176 AURA® R8 CM AWS AMI ENABLE $0
397177 AURA® R8 CM DUP AWS AMI ENABLE $0
397178 AURA® R8 CM KVM ENABLE $0
397179 AURA® R8 CM DUP KVM ENABLE $0
397182 AURA® R8 CM SFTW ONLY ENABLE $0
397183 AURA® R8 CM DUP SFTW ONLY ENABLE $0
397186 AURA® R8 MLP SFTW LIC $20
397166 AURA® R8 EMBEDDED CM ONLY SOL UPG TRK $0
397167 AURA® R8 EMBEDDED CM ONLY SOL MIG TRK $0
397185 EC500 R9 SM AURA® R8 LIC $80
Avaya Aura® Session Manager Order Codes and Pricing

NOTE: All SM upgrades should be done via A1SC/ASD so the appropriate codes are added to the customer
order/record.
See Session Manager Licensing document on the sales portal for definition and use case of each license.
Material Description APL

Code
700514889 AURA SESSION MGR R8.1 DVD $50
700514890 AURA BRANCH SM R8.1 DVD $50
396695 SM R8 SFTW ONLY LIC $1300

avaya.com
396696 SM BRANCH (BSM) R8 SFTW ONLY LIC $300

397903 SM R8 VE VAPP ENABLE $0
397904 SM R8 AWS AMI ENABLE $0
397905 SM R8 KVM ENABLE $0
397906 SM R8 SFTW ONLY ENABLE $0
397907 SM R8 VE VAPP LAB ENABLE $0
397908 SM R8 AWS AMI LAB ENABLE $0
397909 SM R8 KVM LAB ENABLE $0
397930 SM R8 SFTW ONLY LAB ENABLE $0
397931 SM BRANCH (BSM) R8 VE VAPP ENABLE $0
397932 SM BRANCH (BSM) R8 KVM ENABLE $0
397933 SM BRANCH (BSM) R8 SFTW ONLY ENABLE $0
397934 SM BRANCH (BSM) R8 VEVAPP LAB ENABLE $0
397935 SM BRANCH (BSM) R8 KVM LAB ENABLE $0
397936 SM BRANCH (BSM) R8 SW ONLY LAB ENBLE $0
397941 SM R8 SYSTEM LIC $1300
397942 SM R8 ONLY USER LIC $300
397943 SM R8 ASIPP LIC $1000
397944 SM R8 ASIPP EQUIVALENT LIC $0
397945 SM BRANCH (BSM) R8 SYSTEM LIC $300
397946 SM R8 SYSTEM UPG LIC $0
397947 SM R8 ADDL SYSTEM LIC UPG $0
397948 SM R8 ONLY USER UPG LIC $93
397949 SM BRANCH (BSM) R8 SYSTEM UPG LIC $0
397950 SM BRANCH (BSM) R8 ADDL SYS LIC UPG $0
397951 SM R8 SYSTEM UPG ENTL $0
397952 SM R8 ONLY USER UPG ENTL $0
397953 SM BRANCH (BSM) R8 SYSTEM UPG ENTL $0
398630 SM R8 SYSTEM LICENSE IPO $1300
398631 SM R8 SYSTEM UPG LIC IPO $0
398632 SM R8 SYSTEM UPG ENTL LIC IPO $0
398633 SM R8 ADDITIONAL SYSTEM LIC IPO UPG $0
700514499 AURA SESSION MGR R8.0.1 DVD $50
700514500 AURA BRANCH SM R8.0.1 DVD $50

avaya.com
Avaya Aura® System Manager Order Codes and Pricing

700514891 AURA SMGR R8.1 DVD $60
700514892 AURA SMGR HI-CAPACITY R8.1 DVD $60
397272 AURA® SMGR R8 VE VAPP ENABLE $0
397273 AURA® SMGR R8 AWS AMI ENABLE $0
397274 AURA® SMGR R8 KVM ENABLE $0
397275 AURA® SMGR R8 HI-CAP VE VAPP ENABLE $0
397276 AURA® SMGR R8 HI-CAP AWS AMI ENABLE $0
397277 AURA® SMGR R8 HI-CAP KVM ENABLE $0
397280 AURA® SMGR R8 REDUNDANCY UPG LIC $0
397281 AURA® SMGR R8 REDUNDANCY UPG ENTL $0
397282 AURA® SMGR R8 SFTW ONLY ENABLE $0
397284 AURA® SMGR R8 REDUNDNCY SFTW ONLY LIC $0
397285 SMGR R8 VIRTUAL PLATFORM NEW SYS TRK $0
397286 SMGR R8 VIRTUAL PLATFORM UPG SYS TRK $0
397288 AURA® SMGR R8 REDUNDANCY LIC $0
397289 SYSTEM MANAGER R8 LICENSE $0
397290 SYSTEM MANAGER R8 UPGRADE LICENSE $0
397291 SYSTEM MANAGER R8 WITH IPO $0
397292 SYSTEM MANAGER R8 UPGRADE WITH IPO $0
397293 SYSTEM MANAGER R8 UPG ENTL WITH IPO $0
398130 SYSTEM MANAGER R8 SFTW ONLY LIC $0
398131 SYSTEM MANAGER R8 SFTW ONLY WITH IPO $0
700514501 AURA® SMGR R8 DVD $60
700514502 AURA® SMGR HI-CAPACITY R8 DVD $60
397278 AURA® SMGR R8 UPG LIC $0
397279 AURA® SMGR R8 UPG ENTL $0
397283 AURA® SMGR R8 SFTW ONLY LIC $0
397287 AURA® SMGR R8 LIC $0
AVP Utilities Order Codes and Pricing

700514978 APPLIANCE VRTL PLTFRM R8.1.1 DVD $50
700514753 AVP R8.1 UTILITIES DVD $50
397514 AVP R8 UTILITIES VAPP ENABLE $0

avaya.com
Avaya Device Adapter Order Codes and Pricing Order Codes and Pricing
398136 DEVICE ADPTR R8 VE VAPP ENABLE $0
398137 DEVICE ADPTR R8 AWS AMI ENABLE $0
398138 DEVICE ADPTR R8 KVM ENABLE $0
398139 DEVICE ADPTR R8 1ST BREEZE R3 SRVR $0
398140 DEVICE ADPTR R8 ADDL BREEZE R3 SRVR $3,020
398141 DEVICE ADPTR R8 SYSTEM LICENSE $1,000
Avaya Aura® Application Enablement Services Order Codes and Pricing

700514979 AES R8.1.1 AURA OVA MEDIA $300
700514980 AES R8.1.1 SFTW ONLY MEDIA $30
700514982 AES R8.1.1 AURA KVM MEDIA $30
700514981 AES R8.1.1 TSAPI SDK MEDIA $4000
392037 AES R7 AWS AMI LIC $30
397515 AES R8 BSC TSAPI LIC $40
397516 AES R8 BSC TSAPI UPG LIC $14
397517 AES R8 BSC TSAPI UPG ENTL LIC $0
397518 AES R8 PROPRIETARY TSAPI LIC $28
397519 AES R8 PROPRIETARY BSC TSAPI UPG LIC $10
397520 AES R8 PROP BSC TSAPI UPG ENTL LIC $0
397521 AES R8 PARTNER BSC TSAPI LIC $28
397522 AES R8 PARTNER BSC TSAPI UPG LIC $10
397523 AES R8 PARTNER BSC TSAPI UPG ENTL $0
397524 AES R8 ADV TSAPI SML LIC $3,500
397525 AES R8 ADV TSAPI SML UPG LIC $1,225
397526 AES R8 ADV TSAPI SML UPG ENTL LIC $0
397527 AES R8 ADV TSAPI MED LIC $14,970
397528 AES R8 ADV TSAPI MED UPG $5,250
397529 AES R8 ADV TSAPI MED UPG ENTL LIC $0
397530 AES R8 ADV TSAPI LG LIC $34,935
397531 AES R8 ADV TSAPI LG UPG $12,225
397532 AES R8 ADV TSAPI LG UPG ENTL LIC $0
397533 AES R8 ADV TSAPI SM-MED UPLIFT LIC $11,480
397534 AES R8 ADV TSAPI SM-LG UPLIFT LIC $31,440
397535 AES R8 ADV TSAPI MED-LG UPLIFT LIC $19,965
397536 AES R8 PROP BNDL SML LIC $0
397537 AES R8 PROP BNDL MED LIC $0
397538 AES R8 PROP BNDL LG LIC $0
397539 AES R8 CVLAN LIC $249,540
397540 AES R8 CVLAN UPG LIC $62,385

avaya.com

397541 AES R8 CVLAN UPG ENTL LIC $0
397542 AES R8 CVLAN PROP LINKS FOR AVAYA IC $0
397543 AES R8 DLG LIC $249,540
397544 AES R8 DLG UPG LIC $62,385
397545 AES R8 DLG UPG ENTL LIC $0
397546 AES R8 DMCC FULL LIC $240
397547 AES R8 PARTNER DMCC FULL LIC $168
397548 AES R8 DMCC BASIC LIC $40
397549 AES R8 DMCC UPG LIC $14
397550 AES R8 DMCC UPGRADE ENTITLE LIC $0
397551 AES R8 UNFD DSKTP LIC $40
397552 AES R8 UNFD DSKTP UPG $14
397553 AES R8 UNFD DSKTP UPG ENTITLE LIC $0
397554 AES R8 GRHA SM LIC $9,980
397555 AES R8 GRHA SM UPG LIC $3,500
397556 AES R8 GRHA SM UPG ENTL LIC $0
397557 AES R8 GRHA MED LIC $24,955
397558 AES R8 GRHA MED UPG LIC $8,735
397559 AES R8 GRHA MED UPG ENTL LIC $0
397560 AES R8 GRHA LG LIC $49,910
397561 AES R8 GRHA LG UPG LIC $14,970
397562 AES R8 GRHA LG UPG ENTL LIC $0
397563 AES R8 GRHA SM TO MED UPL LIC $14,970
397564 AES R8 GHRA SM TO LG UPL LIC $39,925
397565 AES R8 GHRA MED TO LG UPL LIC $24,955
397566 AES R8 FRHA TO GRHA UPG/UPL SM LIC $2,000
397567 AES R8 FRHA TO GRHA UPG/UPL MED LIC $5,000
397568 AES R8 FRHA TO GRHA UPG/UPL LG LIC $9,980
397569 AES R8 FRHA TO GRHA SUBSCR/UPG SM $700
397570 AES R8 FRHA TO GRHA SUBSCR/UPG MED $1,750
397571 AES R8 FRHA TO GRHA SUBSCR/UPG LG $3,500
397572 AES R8 MPHA TO GRHA UPG/UPL SM LIC $2,000
397573 AES R8 MPHA TO GRHA UPG/UPL MED LIC $5,000
397574 AES R8 MPHA TO GRHA UPG/UPL LG LIC $9,980
397575 AES R8 MPHA TO GRHA SUBSCR/UPG SM $700
397576 AES R8 MPHA TO GRHA SUBSCR/UPG MED $1,750
397577 AES R8 MPHA TO GRHA SUBSCR/UPG LG $3,500
397578 AES R8 GRHA VM TRACKING $0
397579 AES R8 VE VAPP ENABLE $0
397580 AES R8 NEW SYS TRACKING $0
397581 AES R8 UPG SYS TRACKING $0
380297 CUST SFTW RTU RUSSIA SORM CV AES R7 $9,980
397583 AES R8 PLDS ENABLE FOR APPL LIC $0

avaya.com

397584 AES R8 TSAPI ADV MED TO LG S8510 $0
397585 PLDS BNDL STA TRK FOR CM R8 SYSTEM $0
397586 CM R8 ASAI ALL FEAT FOR AES $49,910
397587 CM R8 UPG ASAI ALLFEAT FOR AES $12,475
397588 CM R8 ASAI ALL FEAT LIC ENABLE AES $0
381322 AES R7 DMCC FULL UPG LIC $14
381323 AES R7 DMCC PAR UPG LIC $14
398476 AES R8 KVM ENABLE $0
398477 AES R8 AWS AMI ENABLE $0
399082 AES R8 SFTW ONLY ENABLE $0
397298 AES R8 BSC TSAPI ASL INTERIM LIC $0
397299 AES R8 DMCC FULL ASL INTERIM LIC $0
Avaya Aura® Presence Services Order Codes and Pricing

398132 AURA® PS R8 VE VAPP ENABLE $0
398133 AURA® PS R8 AWS AMI ENABLE $0
398134 AURA® PS R8 KVM ENABLE $0
398135 AURA® PS R8 GEOREDUNDANCY LIC $15,100
398151 AURA® PS R8 GEOREDUNDANCY UPG LIC $0
398152 AURA® PS R8 GEOREDUNDANCY UPG ENTL $0
398153 AURA® PS R8 RTC ENABLE LIC $1,035
397136 AURA® R8 BREEZE R3 SRVR PS INSTNC /E $0
397113 AURA® R8 PRESENCE SERVICES R8 /E $0
397142 AURA® R8 PRESENCE SERVICES R8 UPG /E $0
397153 AURA® R8 PRESENCE SVCS R8 UPG ENTL /E $0
397135 AURA® R8 BREEZE R3 USER /E $0
397136 AURA® R8 BREEZE R3 SRVR PS INSTNC /E $0
398132 AURA® PS R8 VE VAPP ENABLE $0
Avaya Aura® WebLM Order Codes and Pricing

Code
397927 AURA® R8 WEBLM VE VAPP ENABLE
397928 AURA® R8 WEBLM KVM VIRTUAL ENABLE
397929 AURA® R8 WEBLM AWS AMI ENABLE
398040 AURA® R8 WEBLM SW ONLY ENABLE $0
398041 AURA® R8 WEBLM LICENSE
Avaya Aura® Media Server Order Codes and Pricing

Code

avaya.com
700513744 AAMS R8 MEDIA DVD $80

700513745 AAMS R8 MEDIA LINUX DVD $80
700513746 AAMS R8 MEDIA DVD OVA $80
398025 AAMS R8 SYSTEM UPGRADE ENTITLE
398026 AAMS R8 DSP CHANNEL UPGRADE ENTITLE
401239 AAMS R8 SYSTEM UPGRAD
401240 AAMS R8 DSP CHANNEL UPGRADE
398012 AAMS R8 DSP CHANNEL LICENSE $65
398016 AAMS R8 DSP CHANNEL ASIPP LIC $20
398017 AAMS R8 DSP CHANNEL ASIPP SRS LIC $0
398011 AAMS R8 SYSTEM LICENSE $250
398014 AAMS R8 VAPP OVA ENABLE $0
398015 AAMS R8 PVI(Software Only) $0
398020 AAMS R8 SW ONLY FOR AWS ENABLE $0
398021 AAMS R8 SW ONLY FOR KVM ENABLE $0
398023 AAMS R8 DSP CHANNEL ASIPP UPGRADE $0
398024 AAMS R8 DSP CHANNEL ASIPP SRS UPGR $0
398027 AAMS R8 VAPP OVA UPGRADE ENABLE $0
398028 AAMS R8 PVI UPGRADE $0
389797 R230XL SERVER AAMS SMALL
383553 R630 SRVR AAMS LARGE $23000
382929 DL360G9 SERVER AAMS LARGE $23000
Appliance Virtualization Platform Order Codes and Pricing

Material Code Description APL Use Scenario
The media kit contains the media needed for
AVP installations:
• Appliance Virtualization Platform CD:
• USB Stick: Used to provide the
customer configuration to AVP as it
installs on the server and should be
connected to the server with a ks.cfg file
when AVP is installed
• Rollback CD: A recovery CD if rollback
to system platform is required. The CD
contains the required tools to ready the
APPLIANCE VRTL PLTFRM R8 hard drive for System Platform
700513985 MEDIA KIT 150,00 installation.
APPLIANCE VRTL PLTFRM R8
700513741 DVD 50,00
381275 AVP SNGL CPU CMN LIC 450.00 Required for each instance of AVP with
Small & CM High Duplex AVP Servers, as
well as any single CPU servers being
upgraded to AVP

avaya.com
381276 AVP SNGL CPU EMBD LIC $ 150.00 Required for each instance of AVP with new
or upgraded Embedded Servers.
381277 AVP DUAL CPU CMN LIC $ 900.00 Required for each instance of AVP with
Medium and Large AVP Servers, as well as
any dual CPU servers being upgraded to AVP
389893 AVP R7+ XL SRVR LIC $ 1810.00 Required for any scopia XL server running
with AVP
397514 AVP R8 UTILITIES VAPP $0 1 AVPU instance and license required per
ENABLE AVP instance deployed
AVPU software DVD - 1AVPU required per
700513989 AVP R8 UTILITIES DVD 50,00 AVP instance deployed
Note 1: As of May 14th 2018, the AVP pricing has been adjusted down and has become non discountable.
Note 2 : As of Release AA7.1.2, the AVP licenses have become release agnostics and are valid for all releases
moving forward, starting with R7 and the same is true of AA8.0.
AWS (Amazon Web Services) Order Codes and Pricing

Code
397176 AURA® R8 CM AWS AMI ENABLE $0
397177 AURA® R8 CM DUP AWS AMI ENABLE $0
397904 SM R8 AWS AMI ENABLE $0
397273 AURA® SMGR R8 AWS AMI ENABLE $0
392306 ASBCE R7 AWS AMI ENABLE $400
397276 AURA® SMGR R8 HI-CAP AWS AMI ENABLE $0
398477 AES R8 AWS AMI ENABLE $0
397929 AURA® R8 WEBLM AWS AMI ENABLE $0
392038 DS R2.5 SAL 2.5 SFTW STDALN FOR AWS $0
398020 AAMS R8 SW ONLY FOR AWS ENABLE $0
397938 AADS R8 AWS AMI ENABLE $0
398133 AURA® PS R8 AWS AMI ENABLE $0
398137 DEVICE ADPTR R8 AWS AMI ENABLE $0
Avaya Diagnostic Server $0
700513331
Note : ASBCE R8 are not available at Aura® 8 GA time and will be added to this table when they become available at SBCE
8.0 GA.
KVM Order Codes and Pricing

Code
397178 AURA® R8 CM KVM ENABLE $0
397179 AURA® R8 CM DUP KVM ENABLE $0

avaya.com
398021 AAMS R8 SW ONLY FOR KVM ENABLE $0

397909 SM R8 KVM LAB ENABLE $0
395691 ASBCE R7 KVM LIC* $0
700513708 AES R8.0 AURA® KVM MEDIA $30
398476 AES R8 KVM ENABLE $0
397932 SM BRANCH (BSM) R8 KVM ENABLE $0
397905 SM R8 KVM ENABLE $0
397935 SM BRANCH (BSM) R8 KVM LAB ENABLE $0
398138 DEVICE ADPTR R8 KVM ENABLE $0
398134 AURA® PS R8 KVM ENABLE $0
397939 AADS R8 KVM ENABLE $0
397928 AURA® R8 WEBLM KVM VIRTUAL ENABLE $0
Note : ASBCE R8 are not available at Aura® 8 GA time and will be added to this table when they become available at SBCE
8.0 GA.
Avaya Common Server Order Codes and Pricing – CSR2

Note: Common Server 2 servers are no longer provided on new orders.
Avaya Common Server Order Codes and Pricing – CSR3

Code
383529 DL360G9 SRVR VLARGE AVP Used for
$27,060
383552 R620 SRVR VLARGE AVP deployments with
383531 DL360G9 SRVR MEDIUM AVP AVP. Can be used
$18,040 to run shared or
383548 R630 SRVR MEDIUM AVP
383521 DL360G9 SRVR SMALL AVP standalone
$14,530 applications.
383540 R630 SRVR SMALL AVP
383515 DL360G9 SRVR VSMALL AVP
$13,030
383536 R630 SRVR VSMALL AVP
Used for CM High
383530 DL360G9 SERVER CM HIGH DUPLX AVP
$30,065 Duplex deployments
383551 R630 SERVER CM HIGH DUPLX AVP with AVP.
Avaya Embedded Server Order Codes and Pricing

700508924 S8300E SERVER $3,600
700508955 S8300E SERVER - NON GSA $3,600

avaya.com
Avaya Aura® Solution for Midsize Enterprise Optional Migration Disk

Replacement Kit Order Codes and Pricing
 This is a R7 Disk Migration kit to move the ME to R7 as first step in 2 step migration to Aura® R8.
There is not a kit to go directly to R8, as ME Migration to R8 is a 2 step upgrade and migration.
As an option to mitigate downtime during an Avaya Aura® Solution for Midsize Enterprise (ME) migration to
Aura® R8 (2 step process) or deploying Avaya Aura® 7.0, the following optional disk replacement kits are
available for Common Server 1 or 2.
This kit has 4 ME replacement hard drives (CSR1 or CSR2) pre-loaded with Avaya Aura® Release 7.0
applications. Once the data on the installed ME is backed up, the existing disks will be replaced with the kit and
the backup’s then restored. This reduces the downtime associated with downloading and deploying the Avaya
Aura® 7.0 individual application OVA’s.

382784 AURA® R7 DISK REPLCMT CSR1 FROM ME R6 1,300.00
382785 AURA® R7 DISK REPLCMT CSR2 FROM ME R6 non
discountable
10.9. Avaya One Source Configurator / Avaya Solution Designer (A1SC/ASD)

Avaya Aura® 8.1 will be configured in the Avaya Aura® Communication Manager module of Avaya Solution
Designer (A1SC/ASD).
Aura® 8.1 will go GA on Monday, Jun. 10, 2019. In addition to the new functionality, this release also contains
remediation of the Spectre and Meltdown Vulnerabilities
consideration in solution design
Note:
considered.
- The customer is responsible for implementing, and the results obtained frominstalling or upgrading
Aura® 8.1.1.

avaya.com
- The customer should be aware that implementing these patches may result in degraded performance
relative to running on previous releases.
Deployment Options for New Orders

For new orders, A1SC/ASDsupports the following deployment options for most of the Avaya Aura® 8.1.1
applications.
• Avaya Provided Server – Shared: Choose this option to select a virtual appliance, with multiple applications
running on the same Avaya supplied server.
• Avaya Provided Server – Standalone: Choose this to option to select an appliance with a single application
running on an Avaya supplied server.
• Customer Provided VM : Choose this to select a Virtualized Environment Deployment with customer
supplied server and VMware infrastructure.
Customer Provided AWS : Choose this to select a AWS Deployment New Virtual
Appliance Orders with AVP
In Avaya Aura® 8.1.1, A1SC/ASD will size Virtual Appliance solutions to server hardware. A1SC/ASD allows
customers to select the applications that they want to run in shared mode on a server, and based on the number of
users, and other inputs determine the required resource footprint requirements for the applications, and provide
the smallest server, or smallest number of servers that will accommodate the applications.
The A1SC/ASD algorithm selects the server based on the following criteria:
 The smallest server that can accommodate the applications with the specified resource profiles
 If they cannot all fit on a single server, then the smallest number of servers will be selected
 If multiple servers are required, then the lowest cost mix of servers is chosen

avaya.com
The following applications are supported on the Appliance Virtualization Platform (AVP) for Virtual Appliance
deployments in Avaya Aura® 8.1.1:
• Communication Manager
• Session Manager
• System Manager
• AES
• Utility Services
• ADS ( Diagnostics Server )
• SAL
• Web LM
• Breeze for Presence
• Presence
• AAMS
• AADS
• ProActive Contact
• Equinox Server
• AAWG
• AAM ( Aura Messaging )
• AMM ( Multimedia Messaging )
• ASBCE
• SIP Attendant 5.x
• Device Adapter
Note that CMM is not supported on the shared AVP 8.1.1 server.
Instead, it has to be on a different server running AVP 8.0 or earlier.
Embedded Server Orders

The S8300E embedded servers remain supported with Avaya Aura® 8.1.1. The S8300D servers are no longer
supported.
Important Note: the fixes are enabled by default, so take action if your capacities cannot be met with the fixes
enabled.
The embedded servers are virtualized with Appliance Virtualization Platform (AVP) in Avaya Aura® 8.1.1,
however, because of the limited resources available on this server, flexible virtualization is not permitted. Instead,
these servers support the following deployment options:

avaya.com
1
:BSM is optional and included only if user selects them in A1SC/ASD.
Important Note
System Manager 8.1.1 is the primary management solution for Avaya Aura® 8.1.1 and is therefore
required with all Avaya Aura® 8.1.1 deployments. This may require the addition of a new server in order
to deploy System Manager 8.1.1.
Functionality Required to Support Avaya Aura® 8 that is ONLY Available in System Manager 8
 Patching Avaya Aura® 8 applications
 Upgrade Avaya Aura® 8 applications
 Viewing Status of AVP and Applications
 Virtual Machine Management (Create, Delete, Change, Start, Stop, Reset – Virtual Machines)
 Centralized License Management for hosted Avaya Aura® 8 applications
 Log Collection for AVP and hosted Avaya Aura® 8 applications
 Alarm Collection and Display for AVP and hosed Avaya Aura® 8 applications
 Performance Statistics for AVP
 Interoperability with Avaya PLDS for downloading software entitlements
 Role Based Access Control (RBAC) for administrative access to deployment, update, upgrade
and migration functionality provided by SDM.
NOTE - Some functionality listed above is available in the SDM-Client, but the SDM-Client is not a
persistent application that is part of an Aura® 8 solution, so it is not always there. System Manager
should always be part of an Aura® 8 solution to provide the services listed above.
Other Considerations
 Significant investment has been made in System Manager over the past 8 years to provide
consolidated system management across Avaya Aura®.
 A vast majority of the Communication Manager management functions available in Avaya
Integrated Management (AIM) offerings are now available in System Manager. Avaya has
already started to End Of Sale (EoS) the AIM Applications, which will eventually leave System
Manager as the only Central Management solution offering for CM and other Avaya Aura®
Components.
 With Avaya Aura® 8.1.1 System Manager can be deployed on the same server as other
application, (provided they have sufficient resources), resulting in reduced cost to deploy

avaya.com
System Manager 8.1.1. Note that due to resource constraints, System Manager 0 cannot
be deployed on an S8300E.
Ordering the Avaya Aura® Media Server

Customers should be ordering only Avaya Aura Media server 8 for new installations as well as expansions.
AAMS is a software-based media server, providing soft DSP/media channel resources on general-purpose
hardware, with multiple deployment options. Several deployment options are available in ASD/A1SC for AAMS.
Please check the updated capacities with Spectre and Meltdown fixes, once they are available. The below AAMS
capacities are without S/M fixes
• Avaya Provided Server – Shared 4 vCPU: Choose this to order a new server, with multiple
applications running on the same Avaya-provided virtual appliance.. 4 vCPU is the smallest
(550MPU) of the six OVA footprint options for AAMS 8.0. Both 50GB HDD and 250GB HDD
options are available.
applications running on the same Avaya-provided virtual appliance.. 8 vCPU is the mid-
size(1100MPU) of the six OVA footprint options for AAMS 8.0. Both 50GB HDD and 250GB
HDD options are available.
applications running on the same Avaya-provided virtual appliance.. 16 vCPU is the largest
(2200MPU) of the six OVA footprint options for AAMS 8.0. Both 50GB HDD and 250GB HDD
options are available.
• Small Bare Metal Server: Choose this to order a non-virtualized server for AAMS (Avaya
Provided Server and RHEL Operating System). This is the standard capacity (1700MPU) option
of the two Avaya-provided non-virtualized servers.
• Large Bare Metal Server: Choose this to order a non-virtualized server for AAMS (Avaya
Provided Server and RHEL Operating System). This is the high capacity (4550MPU) option of
the two Avaya-provided non-virtualized servers.
• Customer Provided Bare Metal Server: Choose this to for a non-virtualized deployment of
AAMS, where the customer will be providing the server with a Redhat Linux operating system.
The user must specify the PROCESSOR CPU MARK for the customer-provided server. See
http://www.cpubenchmark.net/cpu_list.php for CPU benchmarks.
• Customer Provided VM 4 vCPU: Choose this for a Virtualized Environment deployment of
AAMS (customer provided VMware and Server). 4 vCPU is the smallest (550MPU) of the three
OVA footprint options for AAMS 8.0. Both 50GB HDD and 250GB HDD options are available.
• Customer Provided VM 8 vCPU: Choose this for a Virtualized Environment deployment of
AAMS (customer provided VMware and Server). 8 vCPU is the mid-size (1100MPU) of the
three OVA footprint options for AAMS 8.0. Both 50GB HDD and 250GB HDD options are
available.Customer Provided VM 8 vCPU: Choose this for a Virtualized Environment
deployment of AAMS (customer provided VMware and Server). 16 vCPU is the largest
(2200MPU) of the three OVA footprint options for AAMS 8.0. Both 50GB HDD and 250GB
HDD options are available.

avaya.com
• Software Only for AWS: The Amazon Web Services deployment of AAMS will be utilizing the
Software Only (.BIN) version of AAMS. For AAMS 8.0, there will be four AWS footprints to
choose from: 4vCPU (200MPU, 7.5GB RAM, 50GB HDD), 8vCPU (800MPU, 15GB RAM,
50GB HDD), and 16vCPU (1600MPU, 30GB RAM, 50GB HDD).
• Software Only for KVM: The KVM deployment of AAMS will be utilizing the Software Only
(.BIN) version of AAMS. For AAMS 8.0, there will be six AWS footprints to choose from:
4vCPU (200MPU, 7.5GB RAM, 50GB & 250GB HDD), 8vCPU (650MPU, 15GB RAM, 50GB
& 250GB HDD), and 16vCPU (1300MPU, 30GB RAM, 50GB & 250GB HDD).
For an explanation of MPU (Media Processing Unit,) see https://sales.avaya.com/en/general/aams-instance-
estimator##Media_Processing_Unit_(MPU).
AAMS licensing and related material codes are ordered primarily in two screens on A1SC/ASD.
First, AAMS media/DSP channels are ordered for an single CM instance on the Software screen. In this example,
the user has entered 1700 AAMS media/DSP channels to be ordered for the CM instance:
Enter the number of AAMS

media channels/DSP licenses
for the CM instance.
Second, the number of AAMS instance licenses and material codes associated with deployment type as well as
DVDs are calculated for a particular logical location (multiple logical locations and comprise a single physical
location) at the Location X, Physical Location Y screen: :

avaya.com
The user will first select AAMS for the MEDIA GATEWAY:
The user next selects the desired deployment option for AAMS DEPLOYMENT. In this example, the user selects
“Avaya Provided Server – Shared 4 vCPU”:

avaya.com
Also note that if the user had selected “Customer Provided Bare Metal Server,” the PROCESSOR CPU MARK
field would be need to be entered. Also note that new for Communication Manager 7.0.1 is utilization of
AAMS’s ability to transcode both Opus Narrowband and Opus Wideband codecs. In this example, the user has
also chosen not to have AAMS instances in HA configuration in this logical location. Also, DVDs will be
ordered for each AAMS instance that is calculated for this logical location:
These are the inputs used by A1SC/ASD to calculate number of AAMS instance licenses (380934). Using the
above screen examples:
1. AAMS DEPLOYMENT = “Avaya Provided Server – Shared 4 vCPU” = 550 MPU capacity per instance
2. AAMS HA = “No” = no additional 0.2 MPU per channel, no doubling of AAMS instances.
3. AAMS CHANNELS = “1700”
4. Avaya Aura® Media Server (AAMS) Codec = 100% G.711 = 1MPU per channel
Conceptually the calculation is:
1 * ( (1700 channels) * (1.0 MPU per channel + 0.0 MPU per channel added for HA ) ) / (550 MPUs per instance)
= 3.09 instances = 4 Rounded Up to nearest integer.
AAMS Instance Estimator can be found on Avaya Sales /Partner portal.
Avaya Aura Media Server (AAMS) has entitlements in two separate license files to complete the solution. The
AAMS instance license exist within the AAMS license file where the AAMS DSP Channel license entitlements are
required to be within the Communication Manager (CM) license file.
Where the ‘AAMS DSP CHANNEL LICENSE’ must be in the CM license file, these license must be at the same
version as the CM license file. Two license versions cannot exist in the same PLDS/WebLM license file.
Options to consider when deploying AAMS:

avaya.com
• New (greenfield) purchases:

o Purchasing Avaya Aura (AA) R8, with AAMS, and deploying the solution as AA R7 (Note: Buy to
Current (BTC) is required when purchasing AA R8):
▪ Since the AAMS DSP CHANNEL LICENSE reside in the CM license file and are required
to be the same version as the CM license file version, the AAMS R7 DSP CHANNEL
LICENSE must be activated in the PLDS
▪ The AAMS R8 SYSTEM LICENSE should always be installed.
o Purchasing Avaya Aura (AA) R8, with AAMS, and deploying the solution as AA R8:
▪ Since the AAMS DSP CHANNEL LICENSE reside in the CM license file and are required
to be the same version as the CM license file version, the AAMS R8 DSP CHANNEL
LICENSE must be activated in the PLDS
▪ The AAMS R8 SYSTEM LICENSE should always be installed.
• Adding AAMS to an existing Avaya Aura / CM solution:
o CM R7 is deployed:
▪ Purchase AAMS R8 and select AA/CM R7 deployment:
• Install the AAMS R7 DSP CHANNEL LICENSE in the CM R7 license file
• AAMS R8 SYSTEM LICENSE should always be installed for AAMS
o CM R8 is deployed:
▪ Purchase AAMS R8 and select AA/CM R8 deployment:
• Install the AAMS R8 DSP CHANNEL LICENSE in the CM R8 license file
• AAMS R8 SYSTEM LICENSE should always be installed for AAMS
Please note the following:

It is important that the AAMS Instance Estimator tool be used only by Avaya employees and business partners
and not shared with customers.
The tool will be periodically updated so for the latest version of the tool, please see the Sales Tools section of the
Sales and Partner Portal.
The AAMS Instance Estimator is an aid for designing a network utilizing AAMS. It is an estimate and not a
commitment to capacity or performance.
Ordering Avaya Aura® System Manager

System Manager 8.1.1 is offered as an entitlement with the Aura® 8 Suite Bundles, as well as with purchases of
CS1000 and IP Office solutions. Although an entitlement, it must be requested as only a single instance of System
Manager is needed per enterprise. By default, System Manager is NOT included in any order.
10.9.5.1. Ordering NEW System Manager 8.1.1 via A1SC/ASD

SMGR 7.1.3 Deployment Options:
 Avaya Provided Server – Shared (SMGR 8.1.1 will be deployed on the same Avaya Provided Server as
other Avaya Aura® applications)
 Avaya Provided Server – Standalone (SMGR 8.1.1 will be deployed on by itself on the Avaya Provided
Server)
 Customer Provided VM – SMGR 8.1.1 will be deployed on customer provided VMware infrastructure
The following is a list of SMGR 8.1.1 questions in A1SC/ASD that are factors in determining what server
construct(s) will be provisioned with an order of System Manager. An instance of Appliance Virtualization

avaya.com
Platform (AVP) and the SMGR application OVA are provided as part of the output of an order of System
Manager.
 Number of total Users System Manager will manage in the Enterprise?
 Number of BSMs? (entered in the Session Manager area)
 Number of SMs? (entered in the Session Manager area)
 Will System Manager R8.1.1 run in a Standalone or Shared configuration?
 Is System Manager Geographic Redundancy Required? If yes, 2 servers will be provided with the server
construct calculated based on the A1SC/ASD responses to the number of Users, SMs and BSMs
questions listed above.
Ordering Solution Deployment Manager Client (SDM-Client)

The Aura® 8.1.1 SDM Client is only available via download from the Avaya Suport portal. The SDM Client is
accessable under Avaya Aura® System Manager from the downloads portal on Avaya Support.Any customer or
partner that orders System Manager or Appliance Virtualization Platform will be entitled to the SDM Client.
10.9.5.2. Additional System Manager Considerations, Rules and Guidelines

1. System Manager is only supported on Avaya Provided Servers when operating as an appliance. System
Manager is supported on Customer Provided VMware hardware and on AWS deployements as well.
2. Starting in System Manager 7.0.1, the same server construct requirement at the Primary and
Secondary sites for the Avaya provided appliance offer has been removed and customers will
now be able to order System Manager in a Geographic Redundancy configuration in a SHARED
or STANDALONE mode. For example, CSR2 ‘Large’ at Primary site with a mix of Avaya
Aura® applications and CSR2 ‘Medium’ at the Secondary site with a different mix of Avaya
Aura® applications. Mixing of Avaya provided servers CSR2 and CSR3 is permitted as well.
Note that the Resource Profile and the System Manager software release must be the same at
both locations. Please consult with the System Manager Admin guide for all the deployment
prerequisites.
3. The SMGR-GR configuration is not supported in a mixed hardware configuration where one SMGR
instance is running on Avaya Provided Appliance and the second SMGR instance is running on Customer
Provided VMware hardware. Testing will be planned for a future release.
4. The SMGR-GR configuration is supported in a mixed hardware configuration where one SMGR instance
is running on Avaya Provided Appliance and the second SMGR instance is running in AWS.
5. The Appliance Virtualization Platform (AVP) will come preloaded on Avaya Provided Common
Servers (CSR3) with all new orders of System Manager.
Ordering Avaya Aura® Application Enablement Services (AES)

Application Specific Licensing for Avaya Applications
Application Enablement Services 4.2 introduced application specific licensing for Avaya Applications
using TSAPI and/or DMCC. Application Specific Licensing allows Avaya to simplify the pricing and
ordering of its applications by bundling in the price of the required TSAPI or DMCC licenses into the
price of the application. Avaya Applications that take advantage of application specific licensing are
granted unlimited TSAPI and DMCC licenses. These TSAPI and DMCC licenses will not appear in the

avaya.com
AES license file and will not be able to be used by other applications. For All implementations that will
use an existing AES to support Application Specific Licensing, the AES 4.x license file must be
refreshed if it was created before November 3, 2008.
For applications that require DMCC licenses, DMCC application specific licensing requires
Communication Manager 5.1 or later.
When ordering Avaya Applications that are using the Application Specific Licensing feature, the Avaya
Solution Designer will automatically include Application Enablement Services in the order. The
following table lists the Avaya Applications that have implemented Application Specific Licensing:
Applications using Application Specific Licensing
Application Release
Call Back Assist 3.1+
Contact Center Express* 4.0.1+
Customer Interaction Express 1.0+
Presence Services 6.1+
Proactive Contact 4.1+
Voice Portal with Dialog Designer/Avaya 5.0+
Aura® Experience Portal
Workforce Optimization 10.0+
Elite Multichannel 6.2.3+

One-X Attendant 3.01+
Avaya ANAV 4.1.1+
Avaya Aura® WFO Select 5.0+
DMCC / CMAPI Double Licensing Reconciliation Process:
When Application Enablement Services (AES) was deployed on Communication Manager (CM) releases prior to 6.x,
DMCC Basic (formerly known as CMAPI Basic) licenses were also included in the CM license file as IP_API_A licenses as
well as in the AES license file for compatibility reasons. This meant Avaya literally doubled the quantity of DMCC Basic
licenses with every order which still continues today (for example AES 6.3.3 deployed on a CM 5.2.x) This is creating a
discrepancy between the customer’s quantities purchased and the actual licenses in place and should be reconciled when the
customer’s CM release is upgraded to 6.x or newer, and or an AES upgrade or SA/UA recast (with existing CM 6+) or a

avaya.com
license move is requested in a CM 6.x (or later) environment. Since CSAT is at risk, every opportunity to reconcile should
be taken.
Account teams are responsible to initiate reconciliations and should perform an analysis of current license quantities. Once
this analysis has been completed, Avaya Product Operations should be engaged to make the actual corrections within
Avaya’s licensing tools. Please reference KM26344 in correspondence with Avaya Product Operations
(productops@avaya.com). The following tasks should be performed by the account team with the customer:
✓ Verify the license quantities in AES, CM, and PLDS

✓ Verify the license quantities purchased
✓ If the customer has licenses that were not purchased, determine the total license quantities along with the quantities
that are in use
o Determine the quantities to be purchased and/or removed
o If licenses will be removed, determine what platform (CM, AES, PLDS) they will be removed from and the
associated quantities
The following additional information will assist in determining an accurate inventory count of the DMCC /
CMAPI Basic licenses:
Note: Some CM releases included a licensing quantity of 4-IP_API_As so the total license count may need to
reflect this quantity
Note: Avaya Self-Service Offers add some additional complexity to determining the total license count because
they use the IP_API_A with Voice Portal and Experience Portal H.323 connections and our Self-Service Offers
support CM 6.x and 7.x (along with pre-PLDS CMs: CM 5.2.x with RFA). This needs to be taken into account in
any reconciliation. Here is a history of all released Avaya Self Service material codes:
228762 VP 5.X PER PORT CONN LIC CM6.X

226823 VP 5.X PER PORT CONN LIC CM5.X
226822 VP 4.x PER PORT CONN LIC UPG CM5.X
193019 VP 4.X PER PORT CONN LIC UPG CM5.X
272717 VP R5 CM PER PRT CONN RFA LIC
272718 VP R5 CM PER PRT CONN PLDS LIC
272719 VP R5 CM PER PRT CONN UPG AUTH LIC
272740 AAEP R6 CM PER PRT CONN RFA LIC
272741 AAEP R6 CM PER PRT CONN PLDS LIC
272742 AAEP R6 CM PER PRT CONN UPG AUTH LIC
302390 AAEP R7 CM PER PRT CONN RFA LIC
302391 AAEP R7 CM PER PRT CONN PLDS LIC
302392 AAEP R7 CM PER PRT CONN UPG AUTH LIC
TSAPI provides 3rd party call control services and JTAPI is a client side interface to the TSAPI service. For
TSAPI (and JTAPI) two license type are offered. TSAPI Basic is licensed on a per concurrent user basis and is
intended for applications that monitor or control a station. TSAPI Advanced is licensed per AES server and is

avaya.com
required for advanced call control supporting applications that launch or route calls. TSAPI Advanced is offered
as Small, Medium or Large. See section 10.8.6 for TSAPI Advanced ordering guidance.
As already stated in Section 2.1.6 TSAPI Advanced is offered as Small, Medium or Large. The correct selection
is based on CM configuration but where the CM is in a virtual environment the TSAPI Advanced required is
always Large. The following table will help:
CM6 Configuration TSAPI Advanced License

CM_Simplex Large
CM_SurvRemote Large
CM_Duplex Large
CMM_Federal Large
Msg_Standard Large
Msg_4x146GB_HDD Large
Midsize Enterprise Medium
CM_only Embed Small
CM_SurvRemoteEmbed Small
CM7.x Configuration TSAPI Advanced License

CM Hi Duplex Max Users 36000 Large
CM Duplex Max Users 30000 Large
CM Main/Survivable Max Users 36000 Large
CM Main Max Users 2400 Medium
CM Main Max Users 1000 Small
CM Survivable Max Users 1000 Small
Entitled (+U) Upgrades to Avaya Aura® R7 Foundation Suite/Core Suite/Power Suite
Important Note: Entitle upgrade codes including the upgrade entitle /e codes in the Suite bundles don't flow to
PLDS: This is standard PLDS pre-paid upgrade procedure.
- Upgrades to Aura® R7 with +U support will have upgrade entitle codes (including upgrade entitle /e
codes for the Suite bundle child entitlements) on the SAP order that are provisioned by A1SC/ASD
but these codes won’t flow to PLDS. After placing the SAP upgrade order in A1SC/ASD, the
customer is still required to perform the entitled upgrade transactions to Aura® R7 in PLDS and the
customer will be able to upgrade their applications to R7 as long as there is +U maintenance coverage
in place but the entitle upgrade /e codes just won’t appear in PLDS.
For example:
Any “UPG ENTL /E code” (i.e 380441 – CORE R7 CMM R7 UPG ENTL /E”) will NOT flow to
PLDS. It only appears on the upgrade order so the customers know what they are entitled to. The
customer is required to complete the upgrade in PLDS.

avaya.com
- A SAP order in A1SC/ASD is mandatory for all +U (or UA) upgrades to Avaya Aura® R7
Foundation Suite/Core Suite/Power Suite to ensure all the necessary license entitlements are
provisioned as per standard business practice.
Upgrading from System Platform To Virtual Appliance (Avaya Provided Server)

A1SC/ASD supports a “like-for-like” upgrade to Release 8.1.1 Virtual Appliance from a Release 6.x server.
This means that as long as the existing server is supported on Release 8.1.1, then A1SC/ASD will provision
Appliance Virtualization Platform (AVP) and the OVAs required to deliver the same applications on the same
server after upgrading.
In A1SC/ASD, customers will select the existing release and platform. Then for each application, they will select
the target release and platform. The following options are available for target platform:
DL360G7* (example platform type: will show existing server type if it is a supported server on R8.1.1): choose
this for a like-for-like upgrade
Avaya Provided Server – Shared: Choose this to order a new server, with multiple applications running on the
same virtual appliance
Avaya Provided Server – Standalone: Choose this to order a new server, with only this application running on the
server
Customer Provided VM : Choose this to move to a Virtualized Environment Deployment
Software Only for Existing Shared Server: Choose this is if there is already a virtual appliance with AVP, and the
customer wants to add the application (OVA) without any hardware. (more details on this option to be provided
prior to GA)
Avaya One Source Configurator / Avaya Solution Designer (A1SC/ASD) will then automatically provision the
OVAs that are needed to run the solution on AVP in Release 8.1.1, plus AVP software and the required license
enablement codes.
* Important Note
Memory addon kit may be required depending on the configuration running on the CSR2 ( SDM will catch
the insufficient memory upon upgrade )
A procedure describing a script that needs to be run on each server to identify whether the additional memory is
going to be required is documented into the following PSN027060u – “Avaya Aura® Appliance Virtualization
Platform Release 7.1.2 Memory Upgrade Instructions”. This PSN describes how to identify if the memory
upgrade is needed, how to order the proper memory banks and how to install them.
Ordering UPGRADES of Avaya Aura® Session Manager via A1SC/ASD

NOTE: All SM/BSM upgrades should be done via A1SC/ASD so the appropriate codes are added to the
Session Manager Upgrades from R6/R7 to R8 -

For every upgrade from R6 or R7 Session Manager to R8, an upgrade design and order must be generated in
A1SC/ASD to make sure the customer has all the required material codes that are needed, per Product Manager
and the Product Offer.

avaya.com
IMPORTANT NOTE: For entitled upgrades from SM R6 or R7 to R8, material code 397951 - SM R8 SYSTEM UPG
ENTL will be output. However, since SM R7 did not have Upgrade Advantage codes created, users may assume
that this code will not be able to be upgraded to SM R8. However, if the customer previously had any Software
Support + Upgrades (SSU) OR Upgrade Advantage (UA) for Aura® R6 or R7 on the customer’s contract, then PLDS
is set up to allow the entitled upgrade to SM R8.
Additional Information on PLDS (this applies for upgrades from R6 to R7 and R6/R7 to R8): When the
entitled SM material code is on the order (i.e., 397951 - SM R8 SYSTEM UPG ENTL (this is the equivalent
of 380006 - AURA® R7 SM SYSTEM UPG ENTL), this code does not flow to PLDS, because PLDS does not
require it for the entitled upgrade (these codes are required mainly for the customer’s records).
PLDS is set up with Upgrade Advantage entitlements. For example, at the functional location (FL), if the
customer record contains one of these entitlements below they will be able to execute the entitled (pre-
paid) upgrade.
- SM_PP_SA_UPGRADE - Prepaid Upgrade Entitlement for Session Manager OR
- SM_PP_UPGRADE - Prepaid Upgrade Entitlement for Session Manager
NOTE: For customers with Session Manager R6, after the upgrade order has been processed, existing SIP
Connections and/or User licenses may need to be activated and upgraded in PLDS to provide the Session
Manager system license.
Ordering UPGRADES of System Manager 8.1.1 via A1SC/ASD

SMGR 8.1.1 Deployment Option Questions:
Defining the Existing SMGR Server in A1SC/ASD
 Question: Specify the number of existing SMGR servers in the Enterprise. Maximum is 4 Servers in the
A1SC/ASD tool for existing solutions that implement a SMGR High Availability (HA) pair and the
SMGR Geographic Redundancy (GR) feature. Please note that since SMGR-HA is not available in
SMGR 8.1.1, the maximum amount of SMGR Servers in this configuration that could be upgraded is
actually 2.
Defining the Target Deployment Model
Specify how System Manager will be deployed
 Use Existing Server: This is what should be selected for upgrading existing SMGR servers from R6/ R7
to 8.1.1. This is referred to as a Like-for-Like upgrade
 If your SMGR hardware server is not supported (i.e S8800), the following options are available:
 Shared (new SMGR Avaya Provided Server with multiple Aura® applications)
 Standalone (new SMGR Avaya Provided Server with only SMGR application)
 Customer Provided VM (OVA and License Entitlement for SMGR to be deployed on customer VMware
infrastructure
 Add to existing Shared Avaya Provided Appliance (based on AVP)
 None (No System Manager 8.1.1 Software is required)

avaya.com
System Manager Upgrades from R6/R7 to R8 -

NOTE: For upgrades from SMGR R7 to SMGR R8, PLDS may not have these Aura® R6 or Aura® R7 SMGR licenses
on the customer’s records:
389638 - AURA® R6 SYSTEM MANAGER R7 LIC

389637 - AURA® R7 SYSTEM MANAGER R7 LIC
389687 - SYSTEM MANAGER R7 REDUNDANCY LIC
In these instances, please open an ITSS ticket to have these codes added to the customer’s records by the Tier 2
PLDS helpdesk.
11.0 Product Licensing Process and Policies

License Description, Policy and Process
Transaction
type:
Suite License Systems that are all Suites V2 (Core /Power) – all Suites licenses moved/merged to these
Mixing systems must be Suites V2 (Core/Power). Any Suites V1 Foundation or Licenses that would
be an Entitled Upgrade to Foundation, must be uplifted to Core or Power before they can be
moved/merged to target system
Suites systems that contain at least one Suites V1 Foundation license can move/merge
Foundation licenses to them and can mix Suites V2 Core and Power on the same system
instance
Buy to Current When there is an available N and N-1 (ie not EoS), All Software for New Systems and
Upgrades are purchased as Buy to Current to the most current release and offer but have
option to deploy the N-1
License The transaction of moving some/all existing licenses from an existing system instance
Portability (Donor) to another system instance (Target); new or existing. Donor licenses must be at or
upgraded to release level of target and be in a License construct supported on the Target
system instance.
Moving licenses internationally (out of country of purchase) may include fees depending on
the country of origin (Donor) and country of receiving (Target)
See License Portability Sale Portal Link
Global License Portablity Procedure
Park/UnPark Avaya does not have a formal “Parking” Policy.

If you feel you valid requirement to park licenses please see the Parking EXCEPTION Policy
and process
License Removal of Licenses from a customers record (at customer request). All entitlements of the
Reduction parent license are removed in the same quantitiy. (example where the parent is a Core licnese

avaya.com
(Forfeit) all the product entitlements associated with each Core license are also forfeit)
It should be noted any reductions exercised do not retain any future residual value. If the
capacity is required in the future Add licenses must be purchased or Move from another
system (based on Move guidelines) License Reduction (forfeit) is a valuable part of
Reconstructing a customers licenses asset pool
For CM R6 and higher PLDS License Removal Process (Avaya) or PLDS License Removal
Process (Partners)
For Pre R6, contact RFA helpdesk for RFA License Reduction Form
For ASIPP : follow ASIPP process https://sales.avaya.com/documents/1399551727937 and
submit the ASSIP form https://sales.avaya.com/documents/1399551727880
Software Re- Avaya Software is not sold to the end-user customer, but remains the property of Avaya or its
Licensing third party suppliers. The end-user is granted a license to use the software subject to payment
of applicable license fees and other terms. When an end-user customer seeks to transfer an
Avaya “System,” which includes equipment and software or stand alone software products to
a new owner, it is necessary for the new owner to obtain a software license from Avaya
before it is authorized to use the software. This software re-licensing policy (“Policy”)
addresses the requirements for re-licensing Avaya software. See Policy at link
11.1. Temporary License Requests

See Avaya Global Temporary License Policy
• Temporary/Emergency licenses up to 30 days for emergency /outages do not require product

management or product operations approval. See Avaya Global Temporary License Policy
• Temporary Licenses are not intended or approved
▪ to manage Sales gaps in customer capacity planning or for seasonality burst
▪ for Demo/Customer Trials, you must go to Try Avaya for these scenarios
▪ Labs (Customer or Partner), customer/partner lab systems must be ordered and purchased
as per standard processes and can leverage the partners MDF funds.
Exception is Session Manager as noted below
• Temporary licenses beyond 90 days are not approved.
• Temporary licenses between 31-90 days require product management or product operations
approval. Please call the Helpdesk (Tier 3) to request a temporary license.
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

avaya.com
11.2. Laboratory Trials

Customer lab systems must be ordered and purchased as per standard processes and can leverage the partners
MDF funds. Exception is Session Manager as noted below:
Session Manager Lab Trials

To encourage early adoption and display the power of application sequencing, laboratory systems for evaluation
may be ordered via A1SC/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.
12.0 Services and Support

12.1. Services Support Offers
Support Advantage is required attach at point of sale or upgrade to Aura® Release 8. Support Advantage
Preferred is a comprehensive services support offer featuring:
• 24x7 remote software and hardware support
• 24x7 Expert Systems proactive remote monitoring
• World-class self-support tool in the Avaya Support Website to include information sources
• Avaya Diagnostic Server 3.0 monitoring and diagnostics
• Optional Parts and Onsite support options
• Upgrade Advantage
o For all new major software releases that become Generally Available beginning at the same time
or after Aura® R8 (July 2018), Preferred Support includes the Upgrade Advantage entitlements.
For all major software releases that were Generally Available prior to Aura® R8, Upgrade
Advantage is a separately orderable offer. With Upgrade Advantage, it enables customers to
upgrade their Avaya provided software user/session licenses to the latest Major Release, if and
when available. Upgrade Advantage covers the application software user/session licenses but
does not cover any infrastructure or operating environment software that may be necessary. This
policy aligns with industry practices.
For additional information on Support Advantage Offers, please see the link below:
https://sales.avaya.com/en/pss/support-advantage
Migration Scenarios requiring recast of current Services Support Contracts
To ensure a smooth migration to the new Aura® Release 8 Suites sales scenarios should be understood. Avaya
Client Services has minimized the number of scenarios requiring a recast of the existing support agreement – see
Appendix F: Associated A1SC/ASD and tools processes are aligned to the scenarios.
Where a recast is not required and the Support Advantage agreement customer is migrating to Core and/or Power
Suite, a transitional Support Advantage charge will be added to the existing Avaya support agreement until
renewal or recast. This increase will be for the associated Support Advantage agreement’s remaining term and
represents the additional Core/Power Suite features. (For pricing details and the most current pricing models
please work with your Avaya account team.) At Avaya agreement renewal or recast, the Support Advantage

avaya.com
agreement will simplify to reflect Support Advantage pricing for the Core and/or Power Suite associated support
level.
12.2. Professional Services

Avaya deployment services are available on all Avaya contact center, unified communications, and data networking
solutions. These services are available in the three bundles:
1. Basic – Avaya will perform the application installation, configuration, integration and testing responsibilities
within the deployment, as well as provide project scheduling services to have Avaya resources available and
engaged with the customer and business partner. Hardware installation and overall project management will be
provided by Avaya’s business partner. Avaya’s project management services are an optional add-on to this
services bundle.
2. Standard – Avaya will perform the hardware and software installation, configuration , integration and testing
responsibilities within the deployment, as well as provide project scheduling services to have Avaya resources
available and engaged with the customer and business partner. Overall project management will be provided
by Avaya’s business partner.
3. All Inclusive – Avaya will perform the hardware, software installation, configuration, integration and testing
responsibilities within the deployment. Overall project management will also be provided by Avaya.
The following table describes which bundles are available for each of the different solution components of the Avaya
Aura® suite:
Basic Standard All

Inclusive
Communication Manager (with
Utility Services and Branch ● ● ●
Gateways)
● ● ●
Messaging
Session Manager ●
System Manager ●
Application Enablement Services ● ● ●
Presence Services ●
Midsize Enterprise ● ● ●
These bundles are applicable to new installations, software upgrades and platform migrations.
The following are links to the APS offer descriptions that provide more details at a product level.
- CM, Utility Services and Branch Gateways https://sales.avaya.com/documents/1399552175537

- Avaya Media Server with CM
- ME evolution (migration to Aura® 7) https://sales.avaya.com/documents/1399552175746

avaya.com
- AES
- Presence Services (can only be deployed on Avaya Breeze™)
- Session Manager https://sales.avaya.com/documents/1399552175575
- System Manager https://sales.avaya.com/documents/1399552175575
- Communication Manager Messaging
12.3. PCN/PSN Strategy

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 or emailed 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
proservices@avaya.com for more information.
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.
12.4. Technical Consulting System Support

Avaya provides help line support. To obtain additional support Please call ATAC Pre-sales, Sales and Technical
support at 720-444-7700 or 888-297-4700 ( US and AI ) , 720-444-7700 (CALA) or 44 183 309078 (EMEA) or
65 6872 2693 (APAC) or send email to atac@avaya.com .

avaya.com
You can also use the interactive support features available online to Open a Service Request, chat with a LIVE
agent and more by selecting the specific link associated with your country.
https://support.avaya.com/contact/
Avaya provides help line/maintenance support to customers that have purchased a Post Warranty Maintenance
agreement.
The Avaya GSS Management Escalation Activity (MEA) Process provides a means to engage our management
team to help manage your open service request issue with the appropriate technical resources and the proper sense
of urgency.
12.5. Enhanced Services Available

Avaya Managed Services – UC Managed Assist and UC Managed Operate
Avaya Managed Services team provides full management services capabilities to customers, allowing them to
focus on their core business. Service capabilities provided in managed services offers include, but are not limited
to:
• Single point of entry for system administration and fault management
• General usability help line support
• 8 x 5 local site time maintenance
• Standard service level agreements
• Performance reporting
• Engagement Manager assigned for the term of the Agreement
• Program management of all communications projects
• Single monthly invoice with multi-level data
Pricing is structured into monthly recurring charges on a per port basis, plus additional charges for services such
as special projects and MACs (moves, additions, and changes). More information on UC Managed Operate and
UC Managed Assist offers can be found at URL https://avaya.my.salesforce.com/069a0000002ifuS
https://avaya.my.salesforce.com/069a0000002ifvV
Remote Configuration Helpline (RCH)

During the applicable service period, Avaya provides helpline support to customers which includes answering any
general usability questions regarding software or products and providing advice to help the customer achieve a
working solution. This includes directing customers to sections of the documentation that may answer their
question(s), clarifying the documentation, or recommending possible training courses. The Remote Configuration
Helpline’s assistance does not include help with design or customer LAN issues. Customer specific programming,
administration, and training support can be provided to the customer at Time and Material rates. Alternately,
support can be purchased through the Block of Time program.
Customers may call one of the phone numbers that follows, 7x24:
United States and Canada +1-800-225-7585
Other countries +1-720-44-GLOBE (45623)
Countries other than U.S., Canada, Caribbean, Latin America, and Asia Pacific:

avaya.com
Other international customers receive help line support from their channel partner under the terms and conditions
established with and by the channel partner. Customers who purchased product directly from Avaya receive help
line support from the in-country call receipt team.
Remote Access via Secure Access Link Gateway

System Manager provides secure, rapid serviceability and Expert Systems alarm handling through Secure Access
Link (SAL) to Avaya. 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) of at least 720 kbps with latency no
greater than 150ms (round trip).
A VMware OVA with SAL Gateway 3.0 (or later) is offered as part of every Appliance Virtualization Platform
(AVP) 7.x. Customers may install the SAL Gateway 3.0 OVA on AVP 7.x to manage up to 15 Avaya products
installed on that AVP and elsewhere in the enterprise. If more than 15 Avaya products are present in the
enterprise, the customer should install a standalone, full-scale SAL Gateway capable of managing up to 1000
Avaya devices. The full-scale SAL Gateway is included in the Avaya Diagnostic Server 3.0 packages.
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.
Remote Diagnostics via Avaya Diagnostic Server

Avaya Diagnostic Server consists of the SAL Gateway and Service Level Agreement Monitor (SLA Mon). The
SAL Gateway is used to provide remote support to all Avaya customers. SLA Mon is a free entitlement to
Support Advantage Preferred customers. The software package and installation utility are designed to install one
or both components, as needed.
SLA Mon is an on premise tool that offers two sets of features: Endpoint Diagnostics and Network Monitoring.
With Endpoint Diagnostics a customer can remotely control and diagnose 9600 Series and J Series IP
Deskphones. With Network Monitoring a customer can use intelligent agents embedded in Avaya products to
monitor up to 250 network paths for packet loss, jitter, delay, and QoS. SLA Mon is not available on the SAL
Gateway 3.0 OVA for AVP 7.x.
SLA Mon entitlement check and license distribution for Support Advantage Preferred customers is handled via a
license request form. A 30-day trial period is offered to customers who currently do not have Support Advantage
Preferred. The 30-day trial is built into the software and begins upon installation of SLA Mon. For more
information on Avaya Diagnostic Server and SLA Mon, go to https://support.avaya.com/ads.
Avaya Diagnostic Server (SAL + SLA Mon) is supported through the Avaya Client Services Backbone team.
Start by opening a web ticket on https://support.avaya.com for assistance.
12.6. Warranty
Software Warranty
Avaya provides a 3 month limited warranty on Avaya Aura® Product Components 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.

avaya.com
Hardware Warranty
Avaya provides a one-year limited warranty on the Avaya Session Aura® 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/
Post Warranty Support

Customers may purchase post-warranty support for the Avaya Aura® product components after the expiration of
the initial warranty. Please see Support Advantage details at
https://avaya.my.salesforce.com/apex/sp_ViewDetailPage?c=a3d30000000L2cpAAC&Id=a3j30000000L3jAAAS
Warranty on parts is available worldwide, but servicing terms and conditions may vary subject to locations where
Avaya service is offered.
12.7. Lab Evaluation

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 through 4
• Compose Product Support Notices (PSNs) and Product Correction Notices (PCNs), when applicable
13.0 Avaya Aura® DevConnect

Avaya Aura® DevConnect for developer community information can be found at the following link.
https://www.devconnectprogram.com/site/global/home/p_home.gsp
Partner testing on 7.0 will continue to be represented/recognized at 7.1.3. However, testing with 7.x.x
will not be recognized with 8.1.1 as a major release. Customers using 3rd party applications should
review DevConnect Compliance Testing status and plans with their selected vendors, and ensure those
vendors review pertinent information related to Avaya Aura 8.1.1 found on the Avaya DevConnect
Portal (www.avaya.com/DevConnect) prior to undertaking migration activities.

avaya.com
14.0 CONTACT INFORMATION

If you have questions regarding the Avaya Aura® Solution, please contact ATAC at North America +1 720 444
7700 EMEA +44 1483 309078 APAC +65 6872 2693 +91 20 3092 6555
Email: ATAC@avaya.com with the product in the subject line (E.g. Communication Manager)
Web: https://atac.avaya.com/Technicenter.asp
(Hours of operation: 9 am EST – 8 pm EST) before contacting the responsible Product Manager(s) below.
For RFA related issues, please contact the RFA help Desk at 866-282-9248.
For a current listing of product managers, the Product Management Directory can be found at:
https://sales.avaya.com/en/general/product-management-directory
Avaya Product Management

John Cato General Queries, jcato@avaya.com
Christine McKenna, Aura® User Licensing, Suites, PPU, & Midsize Enterprise, cmcken@avaya.com
Lisa Marinelli, Session Manager, AWS lmarinelli@avaya.com
Abhishek (Abhi) Gupta, Avaya Aura® Communication Manager, CM Adoption of Avaya Aura® Media Server
abhishek@avaya.com
Bob Close, System Manager and WebLM, rdclose@avaya.com
Kirk Jones, Presence Services, AMM, & Device Services (AADS), AAMS kirkj@avaya.com
Michael Lee, Branch Gateways, lee106@avaya.com
Lajwanti Doshi, Application Enablement Services, ldoshi@avaya.com
Cyril Dowling, Communication Manager Messaging, cdowling@avaya.com
Jerome Joanny, AVP and VE, jmjoanny@avaya.com

avaya.com

avaya.com
Appendix A: 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 Y (as of 7.1)
TCP/IP Y
UDP/IP Y
DHCP Y
TLS Y
Note 1: While many Avaya Aura® components support these codecs, MM does not support G.729,
G.726, G.728, G.729a or G.722

avaya.com
Appendix B: Glossary of Terms and Acronyms

Term Definition
802.1Q/P 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
ASIPP Avaya Software Investment Protection Policy
A1SC Avaya One Source Configurator
ASD Avaya Solution Designer
ASG Access Security Gateway
BCS Business Communication Systems
BSR Best Service Routing
BTC Buy to Current – ordering process to buy to current release but have option to deploy the N-1 (as long as
it is not EoS)
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

avaya.com
Term Definition
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
ASG Access Security Gateway
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.
EMSSP Extended Manufacturer Software Support Policy
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 Gatekeeper to gatekeeper (inter-domain) communications
Annex G
Security and encryption for H-series multimedia terminals
H.235
Control protocol for multimedia communications
H.245

avaya.com
Term Definition
H.323 Real-time fax using T.38
Annex D
H.323 Call connection over UDP
Annex E
H.323 Single-use device
Annex F
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
Call transfer
Diversion
Hold
Park & pickup
Call waiting
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 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

avaya.com
Term Definition
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
SA Support Advantage Preferred – Service Support offer
Preferred
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
SS+U Software Support + Upgrades – R5 and below Service offer including upgrade
entitlement
Suites Aura® Suites are value bundled license that simplify the overall Licensing and ensure
customers have breadth of functionality to meet User Need
SV1 Suites V1 – initial Suite offer including Foundation, Mobility and Power. This was
replaces by Suites V1. SV1 Foundation continues to exist as a path for customer with
entitled upgrades
SV2 Suites V2 – Suite offer of Core and Power
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

avaya.com
Term Definition
TSAPI Telephony Services Application Programming Interface. TSAPI also is a key integration
for Outbound Call Management enabling call generation based on data base prompts.
TSC Technical Service Center
TSC-SS Technical Service Center Support System, replaced by Maestro
UA Upgrade Advantage –Upgrade Entitled entitlement offer
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 1and 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: User License Transaction Definitions
Transaction
Definition Comment
Type
New New Licenses for New system • All new systems are shipped as Suites
instance purchase Version 2
• Suites V1 Foundation licneses must be
uplifted before they can be
moved/merged to this system
Add/Expansion New licenses purchased for an • This is not the same as a Move/Merge
Existing system Instance to Add • ASIPP (Avaya Software Investment
user capacity Protection Policy) licenses are not an
Add.
Upgrade: Paid Upgrade from previous release • This is the case where the licneses do not
Transactional to Avaya Aura® 7 carry Upgrade Entitlement (see below)
(Paid) • All licneses would be Transactional
(Paid) upgrade; you cannot have a mix
of some licenses Paid upgrade and some
covered by Upgrade Entitlement

avaya.com
Upgrade: Entitled Upgrade from previous • All licenses on the system instance must
Entitled release to Avaya Aura® 7 be covered by Upgrade Entitlment; you
with active cannot have a mix of some licneses with
• Upgrade Advantage (UA) with Upgrade Entitlement and some not.
• SS+U Note: you may also see this Entitled Upgrade referenced as a
• Pass+/SRS “Subscritpion” Upgrade. The term Entitled is replaced by
Entitled so as not to confuse with Entitled Licensing
ASIPP Avaya Software Investment • ASIPP is considered an Upgrade
Protection can be used by transaction not an Add.
customers as part of a migration to • ASIPP follows the Upgrade Transaction
Avaya Aura® Platform, that operational offer
protects a customers user licensing o Licenses covered by an Upgrade
invetments Entitlement contract (ie SRS Pass+ for
Example CS1K, CS2100, AS5300 CS1K Licenses) follow the Entitled
license migration to Aura® Upgrade path
o Licenses not covered by an Upgrade
entitlement contract follow the
Transactional (Paid) Upgrade path
• ASSIP license migration is bound by the
same rules for license type compatibility
and Buy to Current format
• ASIPP follows the Upgrade Transaction

lifecycle events
Uplift Uplift license level to a higher one • Example:
in release o Uplift a R8 Core Suite to R8 Power
Suite
o Uplift a R8 Basic IPT to R8 Core
Suite
License Move Move = moving some existing • May be Direct System to System if the
Or Merge licenses from an existing system o Release levels are the same
instance (Donor) to another system ▪ If donor is lower level Release will
instance (Target); new or existing required an upgrade to move it
o Target and Donor License Record Buy
Merge = moving all licenses from to Current (BTC) format are the same
an existing system instance (Donor) ▪ If Donor and Target are not same
to another system instance (Target); BTC format (ie one is BTC and one
new or existing is Not), the system that is not in
BTC must be updated to put records
into BTC before moving the licenses
o License Types are compatible
▪ See Suite License compatiblity

avaya.com
• Move and Merges are not the same as

ADD licneses.
• All Suite Move/Merges must be designed
through A1S business tools to ensure
entitlments are properly re-aligned

avaya.com
Appendix D: Suites License Entitlements

SV1 Foundation Suite SV2 Core Suite SV2 Power Suite
397187 AURA® R8 CMM R7 /E 397187 AURA® R8 CMM R7 /E 397187 AURA® R8 CMM R7 /E
397129 AURA® R8 VIDEO /E 397129 AURA® R8 VIDEO /E 397129 AURA® R8 VIDEO /E
397125 AURA® R8 EQUINOX WIN /E 397125 AURA® R8 EQUINOX WIN /E 397125 AURA® R8 EQUINOX WIN /E
397130 AURA® R8 EQUINOX MAC /E 397130 AURA® R8 EQUINOX MAC /E 397130 AURA® R8 EQUINOX MAC /E
397131 AURA® R8 ONE-X COMM /E 397131 AURA® R8 ONE-X COMM /E 397131 AURA® R8 ONE-X COMM /E
397132 AURA® R8 COMM FOR MS 397132 AURA® R8 COMM FOR MS LYNC 397132 AURA® R8 COMM FOR MS LYNC
LYNC /E /E /E
397134 AURA® R8 INTG MGMT 397134 AURA® R8 INTG MGMT ADMIN 397134 AURA® R8 INTG MGMT ADMIN R6
ADMIN R6 /E R6 /E /E
397113 AURA® R8 PRESENCE 397113 AURA® R8 PRESENCE SERVICES 397113 AURA® R8 PRESENCE SERVICES R8
SERVICES R8 /E R8 /E /E
397136 AURA® R8 BREEZE R3 SRVR PS 397136 AURA® R8 BREEZE R3 SRVR PS 397136 AURA® R8 BREEZE R3 SRVR PS
INSTNC /E INSTNC /E INSTNC /E
397287 AURA® SMGR R8 LIC 397287 AURA® SMGR R8 LIC 397287 AURA® SMGR R8 LIC
397135 AURA® R8 BREEZE R3 USER /E 397135 AURA® R8 BREEZE R3 USER /E
397184 AURA® R8 MSG SEAT BASIC R7 380632 POWER R7 MSG MAINSTREAM R6

/E /E
OR OR OR OR
398771** AURA® R8 OL R10 BASIC SEAT 398772** AURA® R8 OL R10 MAINSTREAM

/E** /E**
397120 AURA® R8 AMM ENH USR /E 397120 AURA® R8 AMM ENH USR /E
397124 AURA® R8 EQUINOX IPAD /E 397124 AURA® R8 EQUINOX IPAD /E
397126 AURA® R8 EQUINOX MOBILE /E 397126 AURA® R8 EQUINOX MOBILE /E
397128 AURA® R8 ONE-X CES /E 397128 AURA® R8 ONE-X CES /E
397114 AURA® R8 AES UNIFIED 397114 AURA® R8 AES UNIFIED DESKTOP

DESKTOP R8 /E R8 /E
397133 AURA® R8 EQUINOX FOR WEB /E 397133 AURA® R8 EQUINOX FOR WEB /E
397127 AURA® R8 EC500 SM /E 397127 AURA® R8 EC500 SM /E
380413 Core R7 ASBCE R7 STD /E – 380628 Power R7 ASBCE R7 STD /E –
397115* Currently GA s/w version 397115* Currently GA s/w version
AURA® R8 ASBCE R8 STD /E * AURA® R8 ASBCE R8 STD /E *
380414 Core R7 ASBCE R7 ADV /E – 380629 Power R7 ASBCE R7 ADV /E –
AURA® R8 ASBCE R8 ADV /E * AURA® R8 ASBCE R8 ADV /E *
380415 Core R7 ASBCE R7 STD HA /E – 380630 Power R7 ASBCE R7 STD HA /E –
AURA® R8 ASBCE R8 STD HA /E * AURA® R8 ASBCE R8 STD HA /E *
380416 Core R7 ASBCE R7 ADV HA /E – 380631 Power R7 ASBCE R7 ADV HA /E –
AURA® R8 ASBCE R8 ADV HA /E AURA® R8 ASBCE R8 ADV HA /E *
*
397121 AURA® R8 CONF MM R8 /E
397122 AURA® R8 EQNX R9 MGMT ED/E
397123 AURA® R8 EQNX R9 MGMT NE/E

avaya.com
Entitled Upgrade Foundation Entitlement

Entitled Upgrade Core Entitlement Codes Entitled Upgrade Power Entitlement Codes
Codes
397158 AURA® R8 CMM R7 UPG ENTL 397158 AURA® R8 CMM R7 397158 AURA® R8 CMM R7 UPG
/E UPG ENTL /E ENTL/E
397153 AURA® R8 PRESENCE SVCS R8 397153 AURA® R8 397153 AURA® R8 PRESENCE
UPG ENTL /E PRESENCE SVCS R8 SVCS R8 UPG ENTL /E
UPG ENTL /E
397279 AURA® SMGR R8 UPG ENTL 397279 AURA® SMGR R8 397279 AURA® SMGR R8 UPG
UPG ENTL ENTL
397152 AURA® R8 AES UNFD 397152 AURA® R8 AES UNFD
DSKTP R8 UPG DSKTP R8 UPG ENTL/E
ENTL/E
397154 AURA® R8 MSG 397155 AURA® R8 MSG
SEAT BASIC R7 UPG MAINSTREAM R7 UPG
ENTL/E** ENTL/E**
397142 AURA® R8 397142 AURA® R8 PRESENCE
PRESENCE SERVICES SERVICES R8 UPG /E
R8 UPG /E
380711 Core R7 ASBCE R7 380719 Power R7 ASBCE R7 STD
397148* STD ENTL/E – 397148* ENTL/E – Currently GA
Currently GA s/w s/w version
version AURA® R8 ASBCE R8
AURA® R8 ASBCE R8 STD UPG ENTL /E*
STD UPG ENTL /E*
380712 Core R7 ASBCE R7 380720 Core R7 ASBCE R7 ADV
397149* ADV ENTL/E – 397149* ENTL/E – Currently GA
AURA® R8 ASBCE R8 ADV UPG ENTL /E*
ADV UPG ENTL /E*
380713 Core R7 ASBCE R7 380721 Core R7 ASBCE R7 STD
397150* STD HA ENTL/E – 397150* HA ENTL/E – Currently
Currently GA s/w GA s/w version
version AURA® R8 ASBCE
AURA® R8 ASBCE R8 STD HA UPG ENTL
R8 STD HA UPG /E*
ENTL /E*
380714 Core R7 ASBCE R7 380722 Core R7 ASBCE R7 ADV
397151* ADV HA ENTL/E – 397151* HA ENTL/E – Currently
AURA® R8 ASBCE R8 ADV HA UPG ENTL
R8 ADV HA UPG /E*
ENTL /E*
397157 AURA® R8 CONF MM R8
UPG ENTL /E
Paid Upgrade Foundation Entitlement Paid Upgrade Core Entitlement Codes Paid Upgrade Power Entitlement Codes
Codes
AURA® SMGR R8 AURA® SMGR R8 UPG
397278 AURA® SMGR R8 UPG LIC 397278 397278
UPG LIC LIC
397147 AURA® R8 CMM R7 397147 AURA® R8 CMM R7 UPG
UPG /E /E
397143 AURA® R8 MSG 397144 AURA® R8 MSG
SEAT BASIC R7 UPG MAINSTREAM R7 UPG
/E** /E**
397141 AURA® R8 AES 397141 AURA® R8 AES UNIFIED
UNIFIED DSKTP R8 DSKTP R8 UPG /E
UPG /E

avaya.com

397137* STD UPG/E – 397137* UPG/E – Currently GA
AURA® R8 ASBCE R8 STD UPG /E*
STD UPG /E*
380708 Core R7 ASBCE R7 Power R7 ASBCE R7
397138* ADV UPG/E – 380716 ADV UPG/E – Currently
Currently GA s/w 397138 GA s/w version
AURA® R8 ASBCE R8 ADV UPG /E*
ADV UPG /E*
397139* STD HA UPG/E – 397139* HA UPG/E – Currently
AURA® R8 ASBCE R8 STD HA UPG /E*
R8 STD HA UPG /E*
380710 Core R7 ASBCE R7 380718 Power R7 ASBCE R7
397140* ADV HA UPG/E – 397140* ADV HA UPG/E –
Currently GA s/w Currently GA s/w
version version
AURA® R8 ASBCE AURA® R8 ASBCE
R8 ADV HA UPG /E* R8 ADV HA UPG /E*
397146 AURA® R8 CONF MM R8
UPG /E
*Note 1 Your Avaya Aura® Core and Power Suites entitles you to Avaya Session Border Controller for Enterprise (ASBCE)
Licenses. You are entitled to ASBCE R8 if or when it becomes available. Currently you are entitled to the ASBCE R7 Suite
license entitlement. To design ASBCE R7 in A1S, at the ASBCE deploy as question you will select “R7”.
**Note 2 Your Avaya Aura® Core and Power Suites entitles you a Messaging option of either Avaya Aura Messaging (AAM) or
OfficeLinx. OfficeLinx R10.7 is expected to GA slightly after Aura R8. You may select OfficeLinx as your messaging
entitlement and can deploy it if or when it GA’s. You have the option to select the AAM messaging entitlement as an alternative.

avaya.com
Appendix E: Reconstructing License Asset Pool to User Need

avaya.com
How to Surrender (Forfeit) Licenses:

For CM R6 and higher PLDS License Removal Process (Avaya) or
PLDS License Removal Process (Partners)
For Pre R6, contact RFA helpdesk for RFA License Reduction Form
For ASIPP : follow ASIPP process https://sales.avaya.com/documents/1399551727937 and submit
the ASSIP form https://sales.avaya.com/documents/1399551727880

avaya.com
Appendix F: Services Guidelines

The table on the following page outlines how Support Advantage treats specific sales migration scenarios
(specific customer scenario dependent). In many scenarios a recast of the existing Support Advantage
agreement is not required. Instead Support Advantage will add an Avaya support delta material code to
the support agreement identifying the additional service features. For the customer’s specific scenario
please work with your Avaya Sales Team. Upon Support Advantage agreement renewal or recast Avaya
will update the support agreement to include the:
1. Primary Support Advantage service material codes
2. Corresponding support price points
Table: Appendix F Release 8 Support Advantage Recast Scenarios
LICENSE TYPE CONTRACT W/O UA CONTRACT WITH UA

ANALOG to ANALOG UPG Recast $0KMAT Until Renewal
ANALOG to ANALOG UPG/MOVE Recast $0KMAT Until Renewal
ANALOG to BASIC IPT UPL $0KMAT $0KMAT Until Renewal
BASIC IPT to BASIC IPT UPG Recast $0KMAT Until Renewal
BASIC IPT to BASIC IPT UPG/MOVE Recast $0KMAT Until Renewal
ANALOG to ENHANCED IPT UPL Delta Priced Support Code Delta Priced Support Code
BASIC IPT to ENHANCED IPT UPL Delta Priced Support Code Delta Priced Support Code
ENHANCED IPT to ENHANCED
UPG
IPT Recast $0KMAT Until Renewal
ENHANCED IPT to ENHANCED
UPG/MOVE
IPT Recast $0KMAT Until Renewal
ASIPP to FND N/A N/A Recast
SE/EE to FND N/A N/A $0KMAT Until Renewal
FND R7 to FND R8 N/A N/A $0KMAT Until Renewal
SE/EE to FND N/A N/A $0KMAT Until Renewal
FND R7 to FND R8 N/A N/A $0KMAT Until Renewal
CORE NEW
ANALOG to CORE UPL Recast Recast
BASIC IPT to CORE UPL Delta Priced Support Code Delta Priced Support Code
ENHANCED IPT to CORE UPL Delta Priced Support Code Delta Priced Support Code
FND to CORE UPL $0KMAT Until Renewal $0KMAT Until Renewal
ASIPP to CORE UPL Recast Recast
SE/EE to CORE UPG Recast $0KMAT Until Renewal
SE/EE to CORE UPG/MOVE Recast $0KMAT Until Renewal
FND to CORE UPG Recast $0KMAT Until Renewal
FND to CORE UPG/MOVE Recast $0KMAT Until Renewal
MOBILITY to CORE UPG Recast $0KMAT Until Renewal
MOBILITY to CORE UPG/MOVE Recast $0KMAT Until Renewal
R7 CORE to R8 CORE UPG Recast $0KMAT Until Renewal

avaya.com
R7 CORE to R8 CORE UPG/MOVE Recast $0KMAT Until Renewal

POWER NEW
ANALOG to POWER UPL Recast Recast
BASIC IPT to POWER UPL Delta Priced Support Code Delta Priced Support Code
ENHANCED IPT to POWER UPL Delta Priced Support Code Delta Priced Support Code
FND to POWER UPL Delta Priced Support Code Delta Priced Support Code
CORE to POWER UPL Delta Priced Support Code Delta Priced Support Code
ASIPP to POWER UPL Recast Recast
SE/EE to POWER UPG Recast Delta Priced Support Code
SE/EE to POWER UPG/MOVE Recast Delta Priced Support Code
FND to POWER UPG Recast Delta Priced Support Code
FND to POWER UPG/MOVE Recast Delta Priced Support Code
MOBILITY to POWER UPG Recast $0KMAT Until Renewal
MOBILITY to POWER UPG/MOVE Recast $0KMAT Until Renewal
CORE to POWER UPG Recast Delta Priced Support Code
CORE to POWER UPG/MOVE Recast Delta Priced Support Code
COLLAB to POWER UPG Recast $0KMAT Until Renewal
COLLAB to POWER UPG/MOVE Recast $0KMAT Until Renewal
R7 POWER to R8 POWER UPG Recast $0KMAT Until Renewal
R7 POWER to R8 POWER UPG/MOVE Recast $0KMAT Until Renewal
Recast- Existing Support Contract is Recast at Upgrade/Uplift
Delta Priced Support Code- Existing Support Contract Retained until time of Renewal, Delta Support Pricing
added
$0 KMAT Until Renewal- Existing Support Contract Retained Until Renewal

avaya.com
Appendix G: Product Reference Information Links

Avaya Aura® Platform Product Page
http://www.avaya.com/usa/product/avaya-Aura®-platform
Sales Collateral, Presentations, Support Notices, Support Documentation, Offer
Definitions, Job Aids , Knowledge Transfer Kits (KTK’s) etc.)
https://avaya.my.salesforce.com/apex/sp_ViewDetailPage?c=a3d30000000L28hAAC&Id
=a3j30000000L2GuAAK
Avaya Aura® Midsize Enterprise Solution Product Page
http://www.avaya.com/usa/product/avaya-Aura®-solution-for-midsize-enterprise
Avaya Aura® Platform Virtualized Environment Product Page
http://www.avaya.com/usa/product/avaya-Aura®-virtualized-environment
Product Compatibility Matrix to determine products release levels compatible with each
Avaya Aura® Product Component is available on support.avaya.com at the link
https://support.avaya.com/CompatibilityMatrix/Index.aspx
Choose the Products you have in your environment to assess compatibilities
Technical Documentation for Avaya Aura® can be found at
https://support.avaya.com/downloads/
Developer Community Information
Avaya Aura® DevConnect for Developer Community Information
https://www.devconnectprogram.com/site/global/home/p_home.gsp
Product Authorization, Credentials and Certifications on Avaya Connect
https://avaya.my.salesforce.com/apex/sp_ViewDetailPage?id=a3j30000000L7mUAAS
License Portability: 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
https://avaya.my.salesforce.com/apex/sp_ViewDetailPage?c=a3d30000000L4U0AAK&I
d=a3j30000000L6p9AAC.
Software 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

avaya.com
https://avaya.my.salesforce.com/apex/sp_ViewDetailPage?c=a3d30000000L4U0AAK&I
d=a3j30000000L6p9AAC
Avaya Product Lifecycle Policy:

https://support.avaya.com/css/P8/documents/100081098
APS Application support team engagement process:
https://confluence.forge.avaya.com/display/EPTADVANCEDAPPS/Advanced+Applicati
on+Support+Process#overview
https://avaya.my.salesforce.com/apex/sp_ContentClassificationListPage?Id=a3j30000000
L2IvAAK&cat=Pre-Sales+Technical


Avaya Aura 8 1 1 Offer Definition2

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Avaya Aura 8 1 1 Offer Definition2

Caricato da

Copyright:

Formati disponibili

avaya.

Date of Issue: October 2019

Avaya Aura® Session Manager 8.1.1

Avaya Aura® System Manager 8.1.1

Avaya Aura® Appliance Virtualization Platform 8.1.1

Avaya Aura® Presence Services 8.1.1

Avaya Aura® G430/G450 Media Gateway 8.1.1

Avaya Aura® Application Enablement Services 8.1.1

Avaya WebLM 8.1.1

Avaya Aura® AVP Utilities 8.1.1

Avaya Aura® Media Server 8.0.2

Avaya Aura® Device Services 8.0

Avaya Device Adapter 8.1.1

Compatible EOMS application : Avaya Aura® Communication Manager Messaging 7.0.0.1

Avaya Inc. – Proprietary. 1

© 2011 Template Rev 1.0 Avaya Inc. All Rights Reserved.

Product ➔ Avaya Aura® 8.1.1 GA Date ➔ Jun. 10, 2019

Avaya Source Prime Channel Partner Target Audience

Avaya Inc. – Proprietary. 2

Avaya Inc. – Proprietary. 3

5.0 AVAYA AURA® 8.1.1 FEATURE DESCRIPTIONS ........................................................................ 47

Avaya Inc. – Proprietary. 4

5.4. AVAYA AURA® COMMUNICATION MANAGER SPECIFIC FEATURES ..................................................................59

Avaya Inc. – Proprietary. 5

Avaya Inc. – Proprietary. 6

Automated configuration of AES for cloud platforms [8.1] .......................................................... 73

Avaya Inc. – Proprietary. 7

Avaya Inc. – Proprietary. 8

Suite Licensing ........................................................................................................................ 130

Avaya Inc. – Proprietary. 9

12.4. TECHNICAL CONSULTING SYSTEM SUPPORT ..................................................................................................174

1.0 About this Document

2.0 Team Engagement Solutions

Avaya Inc. – Proprietary. 10

• Achieve reduced total cost of ownership—for the entire engagement environment.

2.1. Avaya Aura® Platform

Avaya Inc. – Proprietary. 11

Aura® Platform Diagram

Communication Manager Overview

Avaya Inc. – Proprietary. 12

Session Manager Overview

System Manager Overview

Avaya Inc. – Proprietary. 13

Offer Focus Preferred Management Tool Comments

Team SMGR (optional)

Avaya Aura® Media Server (AAMS) Overview

Avaya Inc. – Proprietary. 14

Key AAMS-CM features include:

A high-level comparison of AAMS-CM and G-series media gateways:

Avaya Inc. – Proprietary. 15

Media Function AAMS-CM G Series Gateway

Basic media resource capabilities: connections,

Avaya Gateways Overview

Avaya Inc. – Proprietary. 16

Application Enablement Services Overview

Avaya Inc. – Proprietary. 17

Presence Services Overview

Communication Manager Messaging Overview

Avaya Inc. – Proprietary. 18

WebLM can be leveraged as an integrated application within System Manager, or as a standalone

Avaya Aura® Device Services Overview

Avaya Aura® Device Services supports the following services:

Supported Clients and devices

Avaya Inc. – Proprietary. 19