Avaya aura 6.x technical overview

© 2011 Avaya Inc. All rights reserved.

Avaya Aura 6.x Overview

1


Market Size, Trends, and Targets

Avaya Aura® Overview

Avaya Aura Architecture

Communication Manager 6.3

Avaya Servers and Gateways

Avaya Endpoints

Redundancy and Resiliency

Capacities

Virtualization and HW Specifications

Session Manager and System Manager 6.3 Overview

Q&A

Agenda

2


MARKET SIZE, TRENDS, AND TARGETS

3


Cloud

Virtualization

Worker Productivity

Device & Application Consumerization

Business Intelligence

Social Networking

Business Challenges Today

“To support today’s business challenges, a new architecture for communications is required”

4


Avaya Aura® is the communications solution for next generation, people-centric collaboration. – Session (SIP) based communications– Unified Communications and Collaboration– Users, not technology, define the experience

The basis for collaborative, barrier-free business environments that drive business results for our customers:– Industry leading levels of flexibility, scalability and

reliability– Hard dollar cost benefits for customers through

simplification and access savings– Open standards and 3rd Party solutions integration– A migration path forward for every customer

What is Avaya Aura®?

5


Events happen. Business intelligence combined with unified

communications & collaboration result

in…

Avaya collaboration solutions bring together theright people with the right informationto deliver business results in real time

…the right people working together from

different locations, applications and

devices…using the right information to get

work done!

6


How does Avaya Aura Facilitate Collaboration?

Integration– Network Normalization– Integration of 3rd party solutions and call servers– Support for SIP applications, devices and presence

Scalability– From 250 to 250,000 users on the same scalable

architectureReliability

– Capacity and redundancy for large scale and / or high availability environments

Simplified Management– Centralized administration of the network and applications– Critical tools to intelligently manage bandwidth and network

resources

7


xxx,000s10,000Small Medium Midsize Large Fortune 1000

Avaya Aura®Designed for Midsize and Large Enterprises,

more advanced communications needs

# of Users/site

5 100 250 1000

Avaya Aura®

Solution for Midsize Enterprise

(Up to 2400 users)

Avaya Aura®

Avaya IP OfficeDesigned for SME Markets,

Simpler communications needs

G430 / 450 Media Gateways

Avaya: Solutions for All Market Segments

8


The Avaya Aura Architecture

Avaya Aura Presence Services

Avaya Aura MessagingAvaya Voice Portal

Avaya Aura Contact CenterAvaya Meeting ExchangeAvaya Aura Conferencing

3 Layers:--Application-Connection-Access

9


Open, scalable, highly reliable and secure telephony application which delivers:

– User and system management functionality.

– Intelligent call routing.

– Application integration and extensibility.

– Enterprise communications networking.

– Communications applications.

CM Overview

10


Avaya Aura™ Communication ManagerTemplates

Communication ManagerAvaya Aura™ Applications

System Platform

Prior to CM 6.0

The Template

Every release of Communication Manager 6.x will be on the Avaya AuraTM System Platform– Provides a set of common services for use by Avaya applications

A template is a configuration of applications running on SP– Simpler and easier to install, configure and manage Hypervisor

11


CM 6.0 Templates

12


In R6.x, Communication Manager is deployed in two modes:– Feature server– Evolution server

Material Code and Price is the same for both – Since they are just administrable options for the same software

Simple to administer – Just a single field in the CM SIP trunk configuration to Avaya

AuraTM Session ManagerMust purchase Session Manager to deploy

Communication Manager as a feature serverMust purchase Session Manager to deploy SIP terminals

with the evolution server option

Communication Manager 6.x Deployment Options Defined

13


History – SIP endpoints with CM and SES

SIP endpoints are connected to the CM via the SES.

SIP endpoints can communicate with all other endpoints, that are connected to CM.

AESH323

DCP

SIP-trunk

PSTN

ISDN trunk

SES

SIP

analog

SIP

CM

<= CM 6.0

14


Different roles of CM in Avaya Aura TM –

CM as Access Element / CM-AE

AESH323

DCP

PSTN

ISDN trunk

analog

SIP-trunk

SES

SIPSIP

SIP-trunk

CM is connected to the SM via a SIP trunk interface.

Calls going outside of CM are routed to the SM, which route them to the responsible destination.

CM-AE

<= CM 6.0

Avaya Aura™Session Manager

SIP SIP15


Different roles of CM in Avaya Aura TM –

CM as Evolution Server / CM-ES

AESH323

DCP

PSTN

ISDN trunk

SIP

analog

CM-ES

>= CM6.0

Avaya Aura™

SIP-ISC

Session Manager

SIP

CM is connected to the SM via a SIP-ISC interface.

Only calls from and to SIP endpoints are routed via the SM.

SIP endpoints can communicate with all other endpoints, that are connected to the CM.

16

17

Avaya Servers

1818

Controls up to 64 Port Networks of 5 X G650s

Avaya G650 Cabinets

Controls up to 250 H.248 Media GWs

G700 MG

Controls up to 50 H.248 Media GWs

Optional Local Survivable Processor

S8700 Media Servers

}S8500 Media Servers

G350 MG

G250 MG

G450 MG

S8300 Media Servers

Distributed Network Options

G430 MG

19

Server Models & Capacities CM 5.x

S8300 B/C/D450/1000 Stations/450/1000 trunks

S85xx 2400 Stations/800 trunks

S87xx36,000 Stations / 12000 trunks

Max. 12,000 IP ports

Stateful Failover

Performance

Scal

abilit

y

S8400/B900 Stations/450 trunks

S8500AS8500B S8500CS8510S8800 Simplex

S8700S8710S8720/XLS8730S8800 Duplex

**For exact capacities, please refer the CM Capacities table on Avaya Support site.

2020

Avaya Common Servers introduced since CM6

S8800 V2228992

HP® ProLiant DL360 G7(Simplex/Mid-Duplex) 263764

HP ProLiant® DL360p G8 (Simplex/Mid-Duplex) 303518

IBM x3550 M2, Intel Xeon 5500 series 2.26 Ghz12 GB RAM3 X 146 10K GB RAID5Introduced in Fall 09, now EoS

Part of Avaya Common Server Release 1E5620 2.4 Ghz 4-core 12 GB RAM2 x 300 GB 10K RAID1Introduced in Nov 11, Will be EoS in March 2014

Part of Avaya Common Server Release 2E5-2630 2.3 Ghz 6-core 16 GB RAM2 x 300 GB 10K RAID 1

2121

Avaya Common Servers for Mid-Size Enterprise (MES)

HP® ProLiant DL360 G7(MES/COL) 263762

Part of Avaya Common Server Release 1X5670 2.93GHz 6-core, 2 CPU48 GB RAM4x300 GB 10K HD, RAID 5, 2x750 PSU

HP® ProLiant DL360PG8 (MES/COL) 303560

Part of Avaya Common Server Release 2E5-2667 2.9 Ghz 6-core, 2 CPU64 GB RAM4x300 GB 10K HD, RAID 5, 2x750 PSU

There is no Media Services (software media gateway) included with ME 6.2. A G430 or G450 must be added to the solution.

The CM/MBT 5.2.1 S8800 server will NOT run ME 6.2 and must be replaced with the HP DLG360 version designed for ME 6.2.


Supported Servers

22


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

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

High-density 19” rack-mountable systems that support high-availability IP Connect upgrades from Avaya DEFINITY® PBX/servers

Avaya Gateways

23


Media Gateway Examples

G350 Media Gateway

G700 Media GatewayG150 Media Gateways

G250 Media GatewayG450 Media Gateway

G430Media Gateway

24


The G430 Gateway is the ideal solution for low and midsize branches, either standalone or networked gateway linked to a central Avaya Server.

It is designed for growth. Additional expansion modules can be deployed in a single site.

Design supports scalability of DSP resources and slots.

Several survivability options, such as LSP or SLS, which maintain operations in the event a WAN failure affects connectivity to the centrally located server.

For mid-sized enterprises, an installed S8300 Server working with single G430 Gateway serves as a primary call controller for call centers up to 80 agents, or as a business communications system for up to 150 users.

G430 Gateway

25


The G450 Gateway is perfect for medium to large branch office locations or campus environments.

Designed for growth. Multiple gateways can be deployed in a single site. The G450 modular design supports scalability of DSP resources and power and delivers superior capacity, availability and serviceability.

Several survivability options, such as LSP or SLS, which maintain operations in the event a WAN failure affects connectivity to the centrally located server.

For mid-sized enterprises, an installed S8300 Server working with the G450 Gateway can support up to 450 users. An external Avaya Aura Solution for Midsize Enterprise, working with G450 gateways, can support up to 2,400

Avaya G450 Gateway

26


The G650 Gateway is the system of choice for large-scale enterprise communications and call centers.

It offers the features, scalability, and system uptime required for mission-critical applications.

The G650 can accommodate a range of analog, digital, ISDN, and IP (over the LAN) phone station configurations, with voice transport options over IP, analog, TDM, or ATM.

Available dual redundant, load- sharing power supplies with AC/DC inputs provide enhanced system reliability.

Up to five G650 Gateways can be combined to form a high-capacity port network that can be integrated into many existing telephony networks, supporting voice connectivity platform.

The G650 is supported by Avaya Aura® as a large enterprise or midmarket solution.

Avaya G650 Gateway

27


G650 Media Gateway Enhanced Maintenance Bus for

better reporting AC/DC Power Supply Supports Redundant Load

Sharing Power Supplies Can Support 14 TN Circuit

Packs Up to five G650s per PN Used in lieu of traditional

cabinets in new systems Used in Conjunction with

traditional cabinets in existing systems

Supports Direct Connect, CSS, ATM, and IP PNC depending on design

28


PORT NETWORKARCHITECTURE

29


PORT NETWORKS - Defined

30


Port Network (PN) G650

FAN OR POWER FAIL

FAN AND POWER OK

AC INPUT

DC INPUT

ACTIVE RING

ESD GROUND JACK

POWER 1 2 3 4 5 6 7 8 9 10 11 1212 13 14 POWER

TN23

12B

PTN

799D

P

TN26

02A

P

TN46

4HP

TN46

4HP

FAN OR POWER FAIL

FAN AND POWER OK

AC INPUT

DC INPUT

ACTIVE RING

FAN OR POWER FAIL

FAN AND POWER OK

AC INPUT

DC INPUT

ACTIVE RING

ESD GROUND JACK

POWER 1 2 3 4 5 6 7 8 9 10 11 1212 13 14 POWER

TN23

12B

PTN

799D

P

TN26

02A

P

TN46

4HP

TN46

4HP

FAN OR POWER FAIL

FAN AND POWER OK

AC INPUT

DC INPUT

ACTIVE RING

PN1B

PN1A

Every G650 PN requires TN2312BP IPSI

1 G650 PN can support up to 5 Carriers

S87xx and S8500 Servers support up to 64 PNs IP Connect and ATM

G650 Carrier

G650 Carrier

MAX Reliability

31


C-LAN MEDPRO

IP Phone

TDMAnalog / Digital

Phone

Gatekeeper ( Control LAN ) - TN799

Manages a zone (collection of H.323 devices).

Call authorization, bandwidth management, supplementary services, directory services, call management services.

Also provides IP Link for Network applications ( reports, admin etc )

Gateway (Media Processor) TN2303/2602

Provides interoperability between different networks, converts signalling and media G.711, G.729, G.723, supports from 32/64/80/320 simultaneous sessions, with resources dynamically allocated

H.323 Terminal Endpoint

Supports real-time, 2-way communications with another H.323 entity.

support voice (audio codecs) and signalling (Q.931, H.245, RAS).

IPSI

SERVER

IPSI ( IP System Interface )

Provides Control Interface for Gateway

Delivers Tone and Call Classifications Resources

Voicemail

App Servers

Admin PC

G650 & Legacy Media Gateway Components

32

© 2011 Avaya Inc. All rights reserved. 33




Avaya Aura® Solution for Midsize Enterprise

36


Avaya Aura® Solution For Midsize Enterprise

Target 250 to 2400 users,10’s of

locations

Utility Server

including Enterprise Directory

Server

Single path

install, fast, less

costly

Secure remote

monitoring (SAL)

Avaya Common Server

Avaya Aura® Solution for Midsize EnterpriseUses System Platform technology

UC Applications “In-a-box”

• Avaya Aura® Session Manager

• Avaya Aura® System Manager

• Avaya Aura® Presence Services

• Avaya Aura® Application Enablement Services

• Communication Manager Utility Services

• Avaya Aura® Communication Manager and Communication Manager Messaging

• Avaya Aura® System Platform

250 – 2400 users Less complex, quicker turn-up, less support needed for system management/expansionCM Messaging1000 agent Contact CenterHigh Availability (New with 6.2)

Basic Configuration

37




MES 6.2.2 Capacity

40


MES 6.2.2 High Availability

41


Because there is no “one size fits all” ...when it comes

to telephones Avaya has the right choice.

Avaya Endpoints

42


Endpoint Set Call Control Component Architecture

43


Avaya Endpoints

44


User Centric Design

45


Avaya IP Deskphones

46


IP

C-LAN (signaling)

Media Processor (voice stream/

DSP farm)

IP Phone

IP Phone

PSTN

PSTN

IP

Integrated C-LAN & Medpro

Sample IP Connectivity and Functions

47


7 Layers of Resiliency

S87xx Server Resiliency / Reliability Options

Standard Local Survivability

Local Survivable Processor

Enterprise Survivability

WAN Resiliency

Survivability & Reliability

48

© 2011 Avaya Inc. All rights reserved.Contact Center

Avaya IP Phones

Media Gateway

Enterprise Survivable

Server

Avaya IP Phones

Contact Center

Avaya IP Phones and IP Agent Softphone

Branch Offices Contact CenterAvaya IP Phones

Avaya Media Gateway/LSP

Datacenter #1 Datacenter #2

IPSI

IPSI

DSP

CLAN

IPSI

CLAN

IPSI

DSP

Voice VLAN Voice VLAN 2

Avaya S8720 Media Server

Avaya S8720 Media Server

Voice VLAN 1

Voice VLAN

IPSI

IPSI

CLAN

IPSI

CLAN

IPSIVoice VLAN Voice VLAN

Enterprise Survivable Server

Enterprise Survivable Server

Voice VLAN 1

Voice VLAN 2

1st Level Stateful Failover

2nd LevelMultiple Interfaces

3nd LevelMultiple Signal& Bearer Channels

7th LevelLocal SurvivableProcessors(ESS/LSP/SLS)

Primary Server Backup ServerAutomatic

Configuration Updates

DSP

DSP

4th LevelBackup Servers(ESS)

6th LevelPro-Active IP WANTraffic Monitor/Redirect Network # 1

Diverse Network # 2

5th Level Redundant

Announcement& Queue Music

DSP

DSP

DSP

DSP

1

ALM

2 3 4 5 6 7 8 9 10 11 12

13 14 15 16 17 18 19 20 21 22 23 24

LNK COL Rx FDX FC LAG

SI

Tx

SI

1 2 3 4 5 6 7 8 9 10 11 12

13 14 15 16 17 18 19 20 21 22 23 24

Hspd PoE

ALMTSTACT

AVAYA

MM 722BRIV1

1 2

ALMTSTACT

1 2 3 4 5 6 7 8

AVAYA

ANALOGMODULE

LINE T RUNK

ALMTSTACT

1 2 3 4 5 6 7 8

AVAYAMM 712DCP

VH3ALMTSTACT

OK TOREMOVE SERVICES

USB 1 USB 2SHUT DOWN

AVAYA

ICCMODULE

ALMTSTACT

AVAYA

E1 /T1MODULESIG

SO EI SM EM SI EO

ETR

ALM

T ST

ACT

T RUNK LINE LINE CCA ETH WAN ETH LAN

1 2 3

MDM

ALM

CPU

PWR

SYST

EM

CONSOLE

USB

RST ASB

Remove before removing or inserting S8300 module

V6

V2

V1

V5

V4

V3

G350

V7

49


• One active call processing server, and the other server memory shadowed

• Servers can be separated by:• Dedicated fiber, up to 10KM

(hardware duplication)

• Gigabit IP network (software duplication)

• Full Call State Preservation upon server failure

LAN/WAN

Resiliency in the S87xx Servers

50


Entry level survivability option for a single branch office– Alternative to Local Survivable Processor if only basic telephony

survivability is required

Survivable call processing integrated in gateway– Build-in software module– Provides call engine and routing functionality for local lines/trunks

when CM or LSP are not reachable

Available in for:– G250 – G350 – G450– G430

Standard Local Survivability (SLS)or Survivable Remote Embedded Overview

Customer benefit: integrated, no-cost

survivability for branch gateways

G350

G250

G700

G350

G250

G450

G430

51


Standard Local Survivability (SLS) Positioning

Standard Local Survivability

(SLS)

Local Survivable Processor (LSP)

Feature set basic call functionality

full CM functionality

Inbound/outbound dialing ✓ ✓Call hold/transfer ✓ ✓Voice mail coverage/access

- ✓

3-way conferencing - ✓High-capacity branches - ✓Business critical branches, applications

- ✓

SLS offers reliable, entry-level survivability for cost-sensitive branch deployments

52


Registration to CM attempted according to the MGC list. If all options fail → enter survivability mode (last option on the MGC list)

In survivability mode:– Internal H.323 Gatekeeper and H.248 Media GW Controller

activated– Configures dial plan tables and gateway’s legacy

stations/trunks– Phones re-register to the internal gatekeeper

– Distinct SLS dial tone– During transition to survivability mode, only local IP-IP calls will be

preserved

Keep trying to re-register to CM, according to the MGC list and recovery timers

SLS Becoming Active

53


3-party conference call

Call forward on busy/don’t answer

Auto-hold

Caller-ID for analog phones

MOH or playback of announcements

Call center features

Voice mail coverage/access

Connection preservation of failure to SLS or fall-back to CM

Features Not Supported in SLS

54


While SLS is enabled and processing, MG continues to re-register with alternative Call Controller (CM), per the MGC list

If CM or LSP accepts the registration, SLS will stop processing new calls– Unregister the legacy station/trunk ports on the gateway– Issue H.323 un-registration to IP phones– IP shuffled calls are preserved between two IP phones– No connection preservation on fallback

The SLS application will go to inactive mode

SLS H.248 Link Recovery & Fallback

55


Local S8300 configured as secondary MGC – prompted to action when primary call controller is

unavailable– provides comprehensive local call processing capabilities

Preserves all features available in normal operation– call center agents– local announcements

Local Survivable Processor (LSP) orSurvivable Remote Server in H.248 Gateways

Customer benefit: complete local network outage protection

G350

G250

G450

G700G430

56


H.248 Local Survivable Processor (LSP)

CommunicationManager

IP Phones

Central Data

Applications

Router

AnalogPhones

DCPPhones

MediaGateways

Digital/AnalogTrunks PSTN

IP

IPPhonesGateway

Central Location Branch Location

Analog, DCPPhones

57


CommunicationManager

IP Phones

Central Data

Applications

Router

AnalogPhones

DCPPhones

MediaGateways

Digital/AnalogTrunks PSTN

IP

IPPhonesGateway

Primary LinkFailure

Central Location Branch Location

Analog, DCPPhones

H248 Registration Attempts

H.248 Local Survivable Processor (LSP)Failover to LSP

58


Connection preserving failover/fall back– existing stable calls where the talk path exists between two or

more parties are not dropped– connection cannot be preserved for:

– calls that are not in stable state (on-hold, ringing, etc.)– calls using IP or ISDN-BRI trunks, or ISDN stations

Configurable auto fall-back to primary connection– gateway will automatically reconnect to the primary server when

available after having failed over to the Local Survivable Processor (LSP) per the MGC list

– automatic reconnect can be administered to allow for orderly return to service without manual intervention

Failover/fall back normally takes ~3 minutes

H.248 Local Survivable Processor (LSP)Transitioning to/from Back-up Modes

59


Direct connectivity of endpoints, gateways, and adjuncts to the server (performing part of the functions of a CLAN)

This approach has always existed on the S8300 servers Extended to the S8500 servers with CM 3.1 Along with it also came support for the S8500 as an LSP

S85xx as an LSP and Processor Ethernet

S8500 server

LAN or WAN

60


StandbyActiveCDR

AE ServicesCMSPMS

S85xx as an LSP

• Supports up to 2,400 IP phones and 800 trunks• Supports adjuncts through new administration that allows

association of different addresses to point to the active LSP• More cost effective to use compared to S85xx ESS

61


Enterprise Survivable Servers allow backup servers to be placed at various places in a network so that communications can continue in the event that the main server(s) fails, or when connectivity to the main server(s) is lost

Enterprise Survivable Servers can be deployed where needed throughout your network to provide increased communications continuity

Enterprise Survivable Servers provides service to IPSI cards which automatically request service from an ESS server(s) if the control signal to the main server is lost

What is ESS or Survivable Core Server?

62


The ESS priorities are administered and maintained in the main server(s) translations– The main server/server pair is always the highest priority

server on the list, if it’s connected– Each entry can consist of an S87xx/S8800 server pair or a

simplex S85xx/S8800 server

The IPSI will detect a failure of any server connection when the “keep alive” from the server fails

When an ESS takes over for a Main Server, communications capability is lost temporarily for affected port networks; this is a non-call preserving failover

The Basics

63


Recovery to the main server can be scheduled or manual– Most customers will prefer manual due to the fact that fail-

back is not connection preserving

The ESS server(s) have full translations

The ESS server(s) synch translations with the primary server (pair)

When an ESS is in control, it will be in a “license error” mode until the main server takes over– Translations can be changed on an ESS, but they cannot be

saved or resynched

Continued…..

64


Enterprise Survivable Servers (ESS)

• The S85xx / S87xx / S8800 Media Servers can act as an ESS

• All ESSs have full translations

• All ESSs connect to all IPSIs advertising their factors

• The IPSIs dynamically create preference lists of backup clusters (based on those supplied factors) that it can communicate with

• The IPSIs will request service from an ESS or the main cluster based on the highest ranked cluster it can communicate with when port network is not being controlled

• The preference list is dynamically changing based on connectivity changes

65


IP Connect – Normal Operation

LAN or WAN

LAN or WAN

Main S87xxCluster

S85xx ESS

Gateway 1

Gateway 2 Gateway

3

Gateway 4

VoIP Path

Port Network Control Link

66


IP Connect - Server Failure

LAN or WAN

LAN or WAN

Main S87xxCluster

S85xx ESSIPSIs request Backup Cluster take over

Gateway 1

Gateway 2 Gateway

3

Gateway 4

VoIP Path


67


IP Connect - Network Failure

LAN or WAN

Main S87xxCluster IPSIs request Backup

Cluster take overS85xx ESS

LAN or WANGateway 1

Gateway 2 Gateway

3

Gateway 4

VoIP Path


68


IP Device with G650/C-LAN

Main ESS

IPSI

C-LAN

G650

IP Address=1.2.3.4

ESS Server in Control

IP Device

IMPORTANT!IP device “sees”the same IP address regardless of which CM is in control.

Failover to ESS

Main ESS

IPSI

C-LAN

G650

IP Address=1.2.3.4

Main Server in Control

IP Device

69


Main SP

H.248GW

PE IP Address1.2.3.4


Survivable Processor in Control

IP Device

IP Device with PE

Main SP

H.248GW



Main Server in Control

IP Device

IMPORTANT: • IP device “sees” two different

IP addresses• IP device must understand

alternate addresses (e.g. Alternate Gatekeeper List, hunting)

• Both main and SP may be active at the same time.

Failover to SP

70


Capacities

Any questions?

71



Compatibility Matrix- CM 6.3.2

Avaya Inc. - Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

Avaya Products Compatible to Communication Manager - 6.3.2 Compatible Release

Avaya Aura® Application Enablement Services 6.3.1Avaya Aura® Conferencing 7Avaya Aura® Contact Center 6.3Avaya Aura® Messaging 6.2Avaya Aura® Presence Services 6.2Avaya Aura® Session Manager 6.3.4Avaya Aura® System Manager 6.3.4Avaya Aura® System Platform 6.3.1Avaya Session Border Controller for Enterprise 6.2/ 6.2.100Avaya one-X® Agent 2.5Avaya one-X® Attendant 4Avaya one-X® Client Enablement Services 6.2Avaya one-X® Communicator 6.1/6.2Avaya one-X® Mobile 5.2Desktop Video Device 1.1G430 Media Gateway 6.3.1G450 Media Gateway 6.3/6.3.1IP Office 9Meeting Exchange 6.2Modular Messaging 5.2

Supported product releases can be found at the Compatibility Matrix on Support.Avaya.com link below https://support.avaya.com/CompatibilityMatrix/Index.aspx

73


Virtualization:-Server Virtualization is developed so that it appears that several servers are running on single server.Advantages:- Less Environmental Needs (Lesser Rack Space, Electricity needs, less Air conditioning) Facilitates Upgrades Reduce LAN TrafficDisadvantages:- Major impact on services during H/W FailureSystem Platform :- System Platform is a virtualization platform supporting multiple operating systems

and applications. Used as the virtualization platform for many Avaya Aura components including CM,

SM, SMGr, MES, AES etc. . Uses templates to deploy Applications on server and provides common look and feel

to applications. It is not a product, so we will not see it in Avaya Aura Architecture System Platform in itself does not requires any licenses but the applications

templates installed on the system platform may require licenses. Utilizes Citrix Xen Hypervisor for virtualization. Easy Installation, Administration and Maintenance.

Virtualization Concept and System Platform

74


Avaya Aura® Virtualized Environment Overview

Avaya Inc. - Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.75


Deploying Avaya CM on Avaya Aura Virtualized Environment (VE)

Introduced with Avaya Aura 6.2

Avaya Aura Virtualized Environment (VE) permits any VMware user to install Avaya Aura collaboration features directly onto their VMware/vCenter infrastructure.

VE provides the core applications as a software vAppliance (virtual appliance) compatible with VMware vCenter. The vAppliances are hosted inside the VMware infrastructure leveraging allocated resources.

Avaya is providing a vAppliance in the form of a downloadable software file from PLDS containing the Application and the Guest Operating System. It is expected that the end customer location will have a VMware Infrastructure, an accessible VMware Certified Professional (VCP) and VMware vSphere 5.0 or 5.1 Licenses. These items will be required for a successful installation.

76


Avaya Communication Manager Virtual Machine Resource Requirements

Please consult individual Application Virtualized Deployment Guides on Avaya Support site for more detailed information on each application’s sizes!!

The following codes are associated with the CM vAppliance in ASD:

271535 AVAYA AURA CM R6 VE VAPP

271841 AVAYA AURA CM R6 DUP VE VAPP

78


Date post:	13-Sep-2014
Category:	Technology
View:	1,358 times
Download:	10 times

Avaya aura 6.x technical overview

Technology