Core - Module 02 - Aura - Key - Components

71200V | Integrating Avaya Aura® Core Components
Module 2: Avaya Aura® Key Components
Page 1
© 2018 Avaya Inc. All Rights Reserved.
After completing this session, you will be able to:

• Identify the components of the Avaya Aura® Platform architecture
• Describe the virtualization options available for the Aura applications
• List the supported hardware for the Aura applications
• Describe the role of the Avaya Media Server in the Aura platform
• Describe the role of Avaya Utility Services in the Aura platform
• Describe the deployment options available for the Aura applications
Page 2
Module 2: Avaya Aura® Key Components
Page 3
The Avaya Aura® Platform is the foundation for business collaboration. It brings
together a hardware architecture, a software framework, and application
frameworks that enable the software to run.
Some of the key features that the Avaya Aura® Platform provides are:
Communication Enablement such as “Click to Talk”
Session Management through Session Manager’s SIP protocol
Centralized System Management for multiple Avaya applications
Presence, showing the availability of employees – for example, online, busy, or do
not disturb
Instant Messaging through Presence
Telephony such as the robust Communication Manager
Video through Avaya Scopia
Conferencing through Aura Conferencing
As you can see from these key features, Avaya Aura® is a secure, robust, and
scalable platform, that is able to support the communication and collaboration
needs that a company might require.
Page 4
This slide shows the key components of the Avaya Aura® platform. The diagram
shows the spoke and hub architecture.
Session Manager functions are at the center of this diagram. The other applications
and endpoints are spokes out from the hub.
Page 5
Page 6
Page 7
Page 8
New for Avaya Aura 7.0 – Avaya Aura Media Server can provide another option for
older gateways for IP audio. Previously, Communications Manager relied on
hardware based DSPs that can now be replaced by software-based DSPs, on a
Virtual Machine. AAMS Provides a software based media application platform.
It connects to Communication Manager by SIP and is software only, with no
proprietary hardware. This means gateways are no longer required for media
resources. They might still be required for other reasons such as digital or analog
trunking. Media Gateways are required for analog and digital or TDM scenarios.
Avaya Aura Media Server (AAMS) 7.8 – Media source for Avaya Aura®
Communication Manager 7.1.
Software-based media server – AAMS provides soft DSP/media channel resources
on general-purpose hardware, with multiple deployment options.
Benefits:
Add to existing G650 and G450 DSP resources utilizing smaller footprint.
Possible to replace existing G650/G450 DSP resources, resulting in potentially
massive reduction in hardware footprint.
Same voice announcements can be deployed to AAMS that are already centrally
Page 9
deployed to CM-VAL boards, using the SMGR hosted VAL Management

functionality.
Reduced costs for call recording by reducing gateway footprint.
AAMS provides features not offered by Media Gateways and Port Networks:
Virtualization
High channel density
No playback announcement limits
Additional codecs
Page 9
Lesson 2: Deployment Options – Avaya Virtualized Platform and Virtualized

Environment
Page 10
Page 11
Page 12
Page 13
Avaya supplies the following servers to support Aura solution:

The Avaya Common Servers, Release 1, Release 2, and Release 3, are Dell or HP
servers that support that Avaya applications.
Beginning with Aura 7.1, new installations ship with the HP ProLiant DL360P G9.
Upgrades are supported on either Common Server Release 1, Common Server
Release 2 or Common Server Release 3.
The Avaya Embedded Servers, which function with the Avaya G450 or G430 Media
Gateways, support both new installations and upgrades.
Also with Avaya Aura® 7, the Avaya S8800 and the Avaya S8510 servers are no
longer supported.
Page 14
Out of Band Management or OOBM enables the ability to have a separate

management and non-management network traffic across physical and logical
connections.
It isolates management traffic from public networking traffic.
Examples of System Manager’s management network traffic:
Session Manager database replication.
Element Manager to Communication Manager, Session Manager, and Enterprise
Development Platform, etc.
Solution deployment, upgrades, and updates.
Examples of System Manager’s non-management or public traffic:
End-user self-provisioning.
Client devices getting certificates through Simple Certificate Enrollment Protocol
(SCEP).
Page 15
Out of Band networking is set up differently according to the application.

OOBM Appliance Virtualization Platform – OOBM is already set up and ready for
Avaya Aura® Application deployment.
OOBM for Virtualized Environment – Customer is responsible for the configuration
of the vSwitches and connection to the rest of the network.
• Hypervisor only carries management traffic.
• There is no user traffic to the hypervisor. First management port of the ESXi
hypervisor is present on either:
– OOBM vSwitch
– Public vSwitch
• Services Port VM includes an interface on both:
– OOBM vSwitch
– Public vSwitch
Solution Deployment Manager – Provides the configuration of the OOBM
management IP addresses, vSwtich, and Port Group setup and any static routing
required to route traffic onto the management network.
Page 16
Hypervisor Configuration – Enables customers to set up an OOBM

configuration, such that all control and management traffic is separated onto a
different physical NIC on the servers.
Page 16
Lesson 2: Deployment Options – Avaya Virtualized Platform and Virtualized

Environment
Page 17
Page 18
Page 19
Page 20
Page 21
Page 22
Page 23
The correct answers are: A, B and D.
Page 24
Page 25
The correct answer is A: True.
Page 26
The Avaya Aura® Platform is the foundation for business collaboration. It brings
together a hardware architecture, a software framework, and application
frameworks that enable the software to run.
The Avaya applications are virtualized. The application OVAs can be deployed
using the Virtualized Enviroment method or the Appliance Virtualization Platform
method.
In the Virtualized Environment method, Avaya provides the OVA and the customer
provides the ESXi framework and the servers.
In the Appliance Virtualization Platform method, which is used when customers do
not have their own OVA environment, Avaya provides the servers, the OVA, and the
ESXi enviroment.
With Release 7, System Platform is replaced by the Appliance Virtualized Platform.
Page 27
Page 28

Core - Module 02 - Aura - Key - Components

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Core - Module 02 - Aura - Key - Components

Uploaded by

Copyright:

Available Formats

71200V | Integrating Avaya Aura® Core Components

Module 2: Avaya Aura® Key Components

After completing this session, you will be able to:

Module 2: Avaya Aura® Key Components

deployed to CM-VAL boards, using the SMGR hosted VAL Management

Lesson 2: Deployment Options – Avaya Virtualized Platform and Virtualized

Avaya supplies the following servers to support Aura solution:

Out of Band Management or OOBM enables the ability to have a separate

Out of Band networking is set up differently according to the application.

Hypervisor Configuration – Enables customers to set up an OOBM

Lesson 2: Deployment Options – Avaya Virtualized Platform and Virtualized

The correct answers are: A, B and D.

The correct answer is A: True.

You might also like