AVAYA CONFIDENTIAL Provided under a Non Disclosure Agreement Avaya Aura ® Architecture and Roadmap...

AVAYA CONFIDENTIAL Provided under a Non Disclosure Agreement

Avaya Aura® Architecture and Roadmap

Conrad UniackeSenior Product ManagerNovember 14, 2012


Material Shared Only Under Non Disclosure Agreement

Certain statements contained in this presentation are forward-looking statements. These statements may be identified by the use of forward-looking terminology such as "anticipate," "believe," "continue," "could," "estimate," "expect," "intend," "may," "might," "plan," "potential," "predict," "should" or "will" or other similar terminology. We have based these forward-looking statements on our current expectations, assumptions, estimates and projections. While we believe these expectations, assumptions, estimates and projections are reasonable, such forward looking statements are only predictions and involve known and unknown risks and uncertainties, many of which are beyond our control. These and other important factors may cause our actual results, performance or achievements to differ materially from any future results, performance or achievements expressed or implied by these forward-looking statements. For a list and description of such risks and uncertainties, please refer to Avaya's filings with the SEC that are available at www.sec.gov/. Avaya disclaims any intention or obligation to update or revise any forward-looking statements, whether as a result of new information, future events or otherwise.

http://www.sec.gov/


What is Avaya Aura®?

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


Strategic Differentiation

Differentiated architecture (scalable, manageable, flexible)

Multimodal Conferencing Innovative User Experience

across all devices

Interoperability legacy,Open platform for 3rd party


5

Avaya Aura® BenefitsAn adaptable communications architecture that: Simplifies network-wide feature deployment and

on-going management driving down OPEX

Centralizes routing, SIP trunking, and applications providing cost effective and customizable services to users across the network

Scales from 250 to 250,000 users on a single software platform providing consistent user services across locations

Offers High availability / geographic redundancy options for critical reliability networks

Provides a secure environment across multiple layers in the network

• Session, Network and Bandwidth Management

• Network Normalization

• Collaboration - Video, Telephony, Conferencing

• Centralization

• Security

• Survivability


Monitor and flexibly optimize bandwidth to meet business needs

Establish and assure voice quality on a location by location basis

Integrate voice and multimedia bandwidth on a single network

Site 1 Site 2

Site 4 Site 3

Allows locationspecific allocation

of bandwidth between voice and multimedia with video down-speeding as

required

Optimized Bandwidth ManagementAvaya Aura® Session Manager


• SIP Feature Server or Evolution Server

Option• 100K Total,

50K SIP users• 6 SM Instances

• Survivable Core and Remote

•Unified network with 3rd party integration• Incremental SIP

Features

Avaya Aura 6.0June 2010

Avaya Aura Evolution: Scalability, Reliability, SIP

• 100K Total100K SIP users

• 10 SM Instances• Call Admission

Control• Integration of

CS1000 into Avaya Aura

• Incremental SIP Features including

SIP E911

Avaya Aura 6.1November 2010 • 250K Total

100K SIP users (From 18K to 36K

per CM)• 10 SM Instances• SMGR Security

Enhancements•Call and Connection

Preservation• Incremental SIP

Features

Avaya Aura 6.2March/July 2012

• 250K Total / SIP users

• 16 SM instances• Geo- Redundancy

for SMGR•Enhanced Reliability

(ex. Survivable Remote SIP

Trunking)• Presence

Enhancements• Incremental SIP

Features

FutureDirection*

* Future Content is not yet committed or scheduled


Lifecycle - Where do the releases line up?

8

CM release

CI GA EOS EOMS EOSS EMSSPrelease

5.2.1 - June 3 2013

June 3 2014

June 3 2019

Y

6.0 - June 7, 2010

6.0.1

6.0.1 - Nov 19, 2010

6.2

6.2 March 2012

July 9, 2012

na

6.2 SP4 (FP1)

Dec 5, 2012*

6.3

6.3 (FP2) May 6 2013*

May 2015*

May 2016*

May 2021*

Y


Lifecycle - What is CI, GA, EOS, EOMS, EOSS, and EMSSP?

CI - Controlled Introduction– Most Products are GA ready, but a component(s) is not ready

for complete Solution

GA - Generally Available– All components and the Solution are ready

EOS - End of Sale

EOMS - End of Manufacturer Support– No new patches are delivered; diagnostic services still

available

EOSS - End of Extended Services Support– Diagnostic services no longer available*

EMSSP - Extended Manufacturer Software Support Policy– Select products/solutions will be sold for minimum of 2 years,

and have software support for minimum of 3 years9


Avaya Aura® EMSSP

• Extended Manufacturer Software Support Policy (EMSSP) offers an additional category of support for certain releases of products allowing those products to be sold and supported for a extended and predictable period of time.

• Permits Partners and Customers to standardize on a longer term product• For designated EMSSP release, Avaya will

• sell the EMSSP release for a minimum period of two (2) years and• support the release for a minimum of three (3) years from its date of first

sale. • Current EMSSP Release 5.2 over 4 years availability – May 2009 -> June

2013*• Communication Manager 5.2.1• Mid-size Business Template 5.2.1*• SIP Enablement Services 5.2.1* • Integrated Management 5.2.1• Call Center Elite 5.2.1• Application Enablement Services 5.x*


Lifecycle – SP, FP, dot and Releases

Release– Software stream with feature content and

corrective content requiring an upgrade and/or migration

dot (dot dot) Release – Updated software image with corrective

content and select feature content within a Release

SP – Service Pack– Software corrective content delivery

FP – Feature Pack– Software feature content delivery*

11


The Feature Pack Concept

In addition to regular major and minor (“dot”) releases, provide a feature release mechanism that:• Supports lightweight deployment:

• Remote installation, no upgrade required• Minimizes time, cost and disruption to the customer’s network• Requires minimal or no customer lab testing

• Allows customer selectable content:• Customer implementation of valuable features, not every feature• Increase deployment confidence• Reduces potential impact of features that are not of interest

• Provides full testing rigor:• System verification• Regression testing • Alpha and Beta as appropriate for content


Feature Pack Content Selection Criteria

No infrastructure / architectural changes

Minimal or no management changes

Minimal number of interdependent components

What if content fails to meet this criteria?

Content will become a candidate for a future major or minor release


Feature Packs – supplementary Steps Along the Path

Modifications to the current Avaya Aura software structure are required to implement the Feature Pack concept

The next two Avaya Aura releases, Feature Pack 1 (FP1) and Feature Pack 2 (FP2), will not meet all criteria, but represent positive steps along the path:• Avaya Aura FP1 will require:

• Upgrades to System Manager (SMGR) and Session Manager (SM) • Patches to Communication Manager (CM) , Presence Services (PS),

System Platform (SP), and Branch Gateway G430/450 (BGW)

• Avaya Aura FP2 will require:• Upgrades to Communication Manager (CM) , Presence Services

(PS), System Platform (SP)• Patches to System Manager (SMGR), Session Manager (SM),

Branch Gateway G430/450 (BGW), and Application enablement Services (AES)

• Thereafter, feature packs will meet FP criteria


Keeping it all straight: Naming and Numbering

To ensure absolute clarity in the field, current naming and numbering of components will continue.

A Feature Pack will be a “bundle” of individual software components. Example:

– Avaya Aura® 6.2 Solution Today consists of • Avaya Aura® Communication Manager 6.2• Avaya Aura® Session Manager 6.2• Avaya Aura® System Manager 6.2• System Platform 6.2• Presence 6.1• Branch Gateway 6.2

– Avaya Aura® 6.2 Feature Pack 1 (commit) December 2012• Avaya Aura® Communication Manager 6.2 SP4• Avaya Aura® Session Manager 6.3• Avaya Aura® System Manager 6.3• System Platform 6.2.2• Presence 6.1 SP4• Branch Gateway 6.2.1


Lifecycle - Avaya Aura® 6.2 Feature Packs

Avaya Aura® 6.2 Feature Pack 1 (commit) December 2012• Avaya Aura® Communication Manager 6.2 SP4• Avaya Aura® Session Manager 6.3• Avaya Aura® System Manager 6.3

Avaya Aura® 6.2 Feature Pack 2 (commit) May 6, 2013• Avaya Aura® Communication Manager 6.3• Avaya Aura® Session Manager 6.3• Avaya Aura® System Manager 6.3

Other components such as clients will be identified as programs align to delivery dates.


Customer Paths Forward

Customers on 6.2:• If FP1 features are of interest => upgrade at GA

• If FP1 features are not of interest => no upgrade required (unless Service Pack fixes are required)

Customers below 6.2:• EMSSP Customers => begin planning for implementation

of Avaya Aura 6.2 Feature Pack 2

• Non-EMSSP Customers =>• If FP1 features are of interest => upgrade at GA• If FP1 features are not of interest => upgrade today to leverage

Avaya Aura Conferencing, the Avaya Flare® Experience, and Radvision video capabilities.


18

Avaya Aura 6.2 Summary

Scale and Reliability

Avaya Aura® for 250,000 Users!

Extension of High Availability Solution to Mid-Sized Enterprise (ME)

Communication Manager Connection Preservation and Session Manager Call Preservation

Security, usability and SNMP enhancements on System Manager

Up to 10 Emergency Numbers for International

Session Initiation Protocol (SIP)

SIP Group PagingSIP Team ButtonSIP Enhanced Call Pick

Up AlertingSIP Enhanced Call

ForwardingSIP AutoDial ButtonsDTMF SIP-H.323

Integration

Business Collaboration

Conferencing – Local GUI and Moderator Controls

International TON supportNative support for 94xx &

96X1 setsGuardian Service Pack

and Dot ReleasesAACC call information

enhancementPresence Services 6.1

SP1 integration of Microsoft OCS

Cisco Phone Support

Continuing to make Avaya Aura® the flagship communications solution for next generation, people-centric collaboration.


Intra-enterprise federation with multiple OCS/ Lync domains

Exchange calendar integration

Supports Video SRTP

Toll Bypass for India

V.150 for Gateways

Expand to 2K Network Regions

Parallel Forking

Extended Manufacturer Software Support Release

Improving Simplicity, Security, and Presence Interoperability

Avaya Aura® CY2012 & CY2013

Avaya Aura R6.2GA July’12

Avaya Aura R6.2 FP1 Dec 3, 2012

Best in class business continuity with the addition of System Manager Geo-Redundancy

Avaya Aura R6.2 FP2

May 6, 2013

Presence enhancements: XMPP Federation with OpenFire & Access Control List (ACL) enhancements

• (SA9120) Automatic Mute for Remote Off-hook Attempts GRIP 3587

• (SA9119) - Exclusion Event Notification to SIP Phones GRIP 4901

• Transmit Agent ID to H.323 phones to support Agent Greeting Feature

• SIP / H.323 Dual Registration (Concurrent Login)


Getting Ready for Release 6.2: Supported Hardware Communication Manager:

– S8300D: Embedded blade for Avaya Aura Gateways (G450/30,350,250,700)

– S8510 Server - not used for duplication

– Use in a simplex migration by adding memory (6 GB) to total of 8 GB

– Most have 250GB HDD but if 146G HDDs, add third 146GB HDD and RAID 5

– Avaya Common Servers and S8800

Session Manager– Avaya Common Servers and S8800

System Manager– System Manager 6.2 (standalone) on the following Avaya Servers:

– Avaya Common Servers and S8800

Avaya Aura® Solution for Midsized Enterprise 6.2 HA Avaya Common Server

MBT 5.x transition to ME 6.x requires a server replacement

Previous Hardware versions not listed above are not supported20


21

Scale and Performance: Avaya Aura Scalability

Avaya Aura– Up to 250,000 Total End Points

– Up to 100,000 Total SIP End Points

Communication Manager 6.2– Up to 36,000 SIP End Points

– Up to 24,000 SIP Trunks

Session Manager 6.2– Up to 12,000 SIP End Points per Session Manager (standalone)

– Up to 10 Session Managers in a single network

– Up to 500 Communication Manager Instances

System Manager 6.2– Up to 250,000 Total End Points

Avaya Aura Solution for Midsized Enterprise– Up to 1000 Total End Points

– Up to 1000 Total SIP End Points

– Up to 350 SIP Trunks


22

Standalone Utility Services 6.2

Seems ASD needs a little more programming. Open a case to have manually added to the quote

material code 266453 is the Utility Services media

material code 263764 is the CSR1 HP server as default

Standalone Utility Services 6.2 provides support for Duplex CM configurations– CDR is not available with this configuration presently


Questions


Thank YouFor more information:

Products and Solutions technical support

Technical documentation

[email protected]


26

Scale and Performance: Call Preservation

Applicable to Session Manager (SM) Cores with Multiple SMs

In the event of a SM failure:– Connections in progress

and Calls in queue are preserved

– Includes calls to AACC as long as they are routed through VP or CM

– G860/M3000 and SBCs Supported

– Customer Admin-able by time of day, immediate or manual

Avaya Aura™ CM

G860

AA SBC

VP

CM

Core

SIPTrunks

TDMTrunks

PSTN

PS

AAM

MX

MM

SMSM

SM

SMSM

SMSM

SMSM

SM

MMCSAACC

Avaya Aura™ CM


27

Scale and Performance:Survivable Core Connection Preservation

Prevention of split registrations of media gateways and H.323 endpoints between the main Communication Manager or Survivable Core or Survivable Remote servers

Controls the registrations to provide the best system functionality in various outage scenarios by preserving the desired connections


28

Scale and Performance: System Manager

Manage 250,000 total users

Common provisioning with single LDAP synchronization for Avaya Aura and CS1000 users

Single authorization (RBAC) for Avaya Aura and CS1000 systems

Central provisioning of B5800 branch gateways including upgrade

Administration of advanced SIP features

Native administration of new 94xx and 96xx endpoints

Support for hospitality solutions by enabling CM to control “endpoint display name”


29

Scale and Performance: System Manager

Real time notification of CM changes

Audit trail of CM changes made by System Manager administrator

Central administration of management parameters for System Manager and its adopters

Trust Management certification management providing simple provisioning of secure UC communication

Hardened System Manager security via OS hardening and password complexity

Section 508 compliance assessment– VPAT (Voluntary Product Accessibility Template)

– Targeted at Federal and State Government


30

Scale and Performance: System Manager product coverage

New products added to System Manager in 6.2:

– Avaya Aura Contact Center Control Manager 7.0

– Avaya one-X Attendant 4.0

– B5800 Branch Gateway 6.2

– HealthCare Applications

– M3K High Density Trunk Gateway 2.0

– Avaya Aura Conferencing 6.2

Supported in System Manager before 6.2

– Avaya Aura Communication Manager

– Avaya Aura Call Center Elite

– Avaya Aura Contact Center

– Avaya Aura Presence Services

– Avaya Aura Session Manager

– Avaya Data Portfolio (e.g. COM, EPM, IPFM, NRM, and VPFM)

– Avaya one-X Client Enablement Services

– Communication Server 1000 7.5

– Solution for Midsize Enterprise

– Avaya Aura Conferencing

– Avaya Aura Messaging

– Avaya One-X Agent

– Media Application Server

– Modular Messaging

System Manager functions available to each product varies by product.


31

Session Initiation Protocol:SIP Call Features

Enhanced Call Forwarding– Supports call forwarding on “Unconditional” “Busy” and “No

Reply”

– Permits user to differentiate between treatment of internal and external calls

– Same operation as on H.323 end points (User receives visual and audio feedback on feature activation and visual guidance on invoking feature)

– Each of the 6 permutations can have a different destination


32

Enhanced Call Pickup Alerting– When any member of a pick up group is called, the

displays of all members of the pickup group are updated with the calling and called party information, enabling a member to decide whether to pick up the call or not.

– The following alerting options are available: Intercom ring, Silent if busy (if the user is busy on another call, the audible alerting is skipped.), half-ring, continuous, single if busy, no ring, single ring.

– The timing of the display and audible notifications are separately administrable.

– Same functionality as on H.323 end points



33

SIP Team Button– The assignment of a team button on a station brings it

automatically into the virtual team, establishing a data relation between the monitored station and the monitoring station.

– The Team Button has two functions:– Display function: Allows any member of a team (monitoring station) to

observe the station state of other team members (monitored station).– Execution function: Allows the Team Button to be used as a Speed

Dial Button or Pick-Up Button. Depending on the state of the monitored station, when the Team Button on the monitoring station is pushed, a call to the monitored station is established directly or a ringing call is picked from the monitored station.

– The number of monitored stations that can be monitored by other stations is limited to a maximum of 15.




Group Paging to SIP Phones– Page groups are created by assigning extensions as

members of the group and an extension number which users dial to page the group.

– When a user dials the extension of the paging group, Communication Manager activates the speakers on all the telephones in the group. Speakerphone paging is one-way communication: Group members hear the person place the page, but cannot respond directly.


SIP Auto Dial Buttons– One-touch access to frequently called numbers


34



AACC Call Information Enhancements– For SIP calls, provides agent with understand of call status

for Hold, Transfer, and Conference

CODEC Support– Enable Support for Codecs G722.2, iLBC, iSAC, and SILK

– Providing wide bandwidth and low bit rate codecs

35

Session Initiation Protocol:SIP Feature Enhancements


DTMF SIP-H.323 Integration– Permits the proper translation of DTMF tones between SIP

and H.323– SIP Networks Use RFC 2833 DTMF– H.323 Networks Use Signaling Messages– DTMF SIP-H.323 Integration allows tones to be converted between

Communication Manager, Avaya Aura Messaging and Voice Portal

36

O O O

SIP NW1

AA Messaging

SM

Loc Z

H.323 PBXCM

Loc A

H.323 PBXCM

H.323 NW 1H.323 GK

H.323 MessagingSIP NW

N

AA Messaging

SM H.323 NW M

H.323 GKH.323 Messaging

O O OO O O

Session Initiation Protocol:SIP Feature Enhancements


37

Business Collaboration Enhancements

Avaya Aura Conferencing Local GUI– Simple local access to participants and their status via

96XX Display

Navigation arrow to get conference details

Telephony Presence (On a call) Instant

Messaging Availability


38

Business Collaboration Enhancements

Avaya Aura Conferencing GUI Enhancements– Provides conference host enhanced interface to control

conferences via a 96XX end point

– All conference participants are visible to the host and controls include:

– Mute– Un mute– Drop– Add

Participants

Controls

Participant has been selectively muted


39

Business Collaboration Enhancements:Presence Services 6.1SP1

Support for Microsoft Office Communicator via Office Communications Server – Enables Avaya Presence Server federation with OCS server and

MOC

System Platform installation improvements– On site simplified initial installation through CLI change of network

parameters:

– PS IP address, Gateway, Domain search list, DNS, Netmask and PS hostname

Presence Services 6.1 is compatible with Avaya Aura 6.2


40

SIP Presence and IM

SIP SIP / TLS

SIP / TLS

Avaya PresenceServer

OCS EdgeOCS R2 Server

enterprise domain e.g. avaya.compresence domain e.g. aps.avaya.com

SIP / TLSXMPP

Avaya Presence Server / Microsoft OCS R2 Topology Overview

Business Collaboration Enhancements:Presence Services 6.1SP1


CM Licensing Functions Release Matrixto Current

Release (XX)from Same

Release (SE)from Same

Release (EE)from Older

Release (SE)from Older

Release (EE)

NEW/ADD (SE) Permitted Not Permitted - -

NEW/ADD (EE) Not Permitted Permitted - -

TRANSFER (SE) Permitted Not Permitted Not Permitted Not Permitted

TRANSFER (EE) Not Permitted Permitted Not Permitted Not Permitted

UPLIFT (EE) Permitted -Permitted with

Upgrade purchase

-

UPGRADE (SE) - - Permitted Not Permitted

UPGRADE (EE) - - Permitted with

Uplift purchase Permitted

MOVE (SE) - - Permitted Not Permitted

MOVE (EE) - - Permitted (+uplift) Permitted

AVAYA CONFIDENTIAL Provided under a Non Disclosure Agreement Avaya Aura ® Architecture and Roadmap...

Documents

Transcript of AVAYA CONFIDENTIAL Provided under a Non Disclosure Agreement Avaya Aura ® Architecture and Roadmap...