Documente Academic
Documente Profesional
Documente Cultură
com
Offer Definition
Avaya Aura® 8.1.1
Includes:
Avaya Aura® Communication Manager 8.1.1
Avaya Aura® Utility Services (US) (component is removed from the solution as of R8.0
element)
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)
Offer Definition
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
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
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
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)
mobility features, built-in conference calling and contact center applications, E911capabilities and a foundation to
add advanced applications for messaging, conferencing and applications development
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
The following is a summary of the management positioning and if the preferred management solution is
mandatory or optional.
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
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.
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.
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.
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
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
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:
https://downloads.avaya.com/css/P8/documents/101038581
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
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.
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.
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
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.
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.
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
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]
• 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
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
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)
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.
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.
3.2. Summary of Features Delivered in Avaya Aura® 8.1.1, 8.1, 8.0.1 and 8.0
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.
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
Nutanix offers is constituted of multiple components , two of particular relevance to Avaya Aura®
virtualization:
– Nutanix appliances
– Nutanix Acropolis hypervisor ( AHV )
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.
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”.
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.
Products Release
Following Products/Applications are be supported into AWS
environment (for the indicated releases and newer).
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.
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.
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.
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
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
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.
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:
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.
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.
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.
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.
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.
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
– Calls ring in multiple places – faculty member has a lab and office
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
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.
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.
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.
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.
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.
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.
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]
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.
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.
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
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.
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.
https://docs.mcafee.com/bundle/endpoint-security-10.5.0-threat-
prevention-product-guide-linux/page/GUID-94135CD9-4F0B-4E91-
A21A-C4C735DC9D41.html
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
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.
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
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.
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.
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.
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.
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.
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.
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.
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.
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
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.
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.
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.
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.
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 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
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.
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.
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
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.
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.
Example:
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.
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.
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.
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.
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
Pure Lync/S4B users can see Aura voice “in a call” state [8.0.1]
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:
▪ hunt groups,
▪ coverage answer groups,
▪ ELIN,
▪ abbr dial buttons
▪ Listed directory Number
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.
The following capacity increases are achieved in CM 8.1 (supported in CM's Large footprint):
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.
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.
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.
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.
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
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.
- 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
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 ):
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 :
– Any attempt to upgrade the G4xx straight to 8.1.1 will fail with an “Incompatible
software image for this type of device “
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.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.
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.
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
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.
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.
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.
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
System Platform CDOM required
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 Platform CDOM required
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
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
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.
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.
supported on). Noting that CMM has been tested on CSR 2 & 3, but it has not been tested on ACP or
PodFX servers.
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
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
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.
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”.
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.
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.
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)
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.
The AES capacities referenced above do not yet reflect impact of Spectre/Meltdown fixes and are subject to
change.
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
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.
Resource profiles for product’s AWS and KVM deployment options are documented in individual product
specific deployment guides.
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.
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)
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
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 may result in degraded performance
relative to running on releases prior to 8.1.
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
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.
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).
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.
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.
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 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.
Equivalences between the CSR3 AVP appliances and the ACP120 bundles different models are listed below:
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
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
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.
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.
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
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.
Gateways
Supported gateways include the following:
• G430
• G450
• G650
Note that MCC and SCC are not supported with Avaya Aura® 8.1.1.
Please refer to the Documentation Catalog for a complete list of Avaya Aura® Release 8.1.1 documents:
https://downloads.avaya.com/css/P8/documents/101050513
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.
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
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
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
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
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
Courses:
For Avaya Virtual Campus Knowledge Access:
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
2nd course 0U00110E Avaya Unified 151 Now
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
What is New in
Avaya Presence Assessment
2010T 0.5 Aug-15
Services 7.0 Online (LMS)
Test
The Tech Transfer reordings for Aura® 8.0 have been posted at the following link, including the live Q&A from
the event.
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
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
License Adds to a system that is currently deployed as R7 (not buy to current R8)
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 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 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)
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
o Messaging
o EC500
• IPT Licenses requires specific device attach (as part of the design)
Avaya Devices only; No Device Substitutions
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)
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
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
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
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
messaging vs competitor license add ons, which affect both the product license price but also ongoing
maintenance support costs.
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
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.
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
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
customer order/record.
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
https://sales.avaya.com/documents/1399552204494
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.
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
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
Material Description APL Use Scenario
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
See Session Manager Licensing document on the sales portal for definition and use case of each license.
Avaya Device Adapter Order Codes and Pricing Order Codes and Pricing
Material Code Description APL
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
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.
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.
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.
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
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
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 frominstalling or upgrading
Aura® 8.1.1.
- The customer should be aware that implementing these patches may result in degraded performance
relative to running on previous releases.
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
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.
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
System Manager 8.1.1. Note that due to resource constraints, System Manager 0 cannot
be deployed on an S8300E.
• 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:
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: :
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”:
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.
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.
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.
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+
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
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:
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:
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.
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:
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.
- 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.
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.
In these instances, please open an ITSS ticket to have these codes added to the customer’s records by the Tier 2
PLDS helpdesk.
(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
https://sales.avaya.com/documents/1399549441087
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
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
agreement will simplify to reflect Support Advantage pricing for the Core and/or Power Suite associated support
level.
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:
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.
- 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
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.
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.
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.
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/
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.
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
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
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
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
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
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
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
OR OR OR OR
397120 AURA® R8 AMM ENH USR /E 397120 AURA® R8 AMM ENH USR /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.
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
https://avaya.my.salesforce.com/apex/sp_ViewDetailPage?c=a3d30000000L4U0AAK&I
d=a3j30000000L6p9AAC
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