Avaya Aura for Midsize Enterprises Product Definition Global Sales and BusinessPartner Channels Date issued: January

11, 2010

Contents
Contents...............................................................................................................................2 Summary..............................................................................................................................3 Avaya Aura for Midsize Enterprise Solution Description....................................................3 Avaya Aura System Platform 1.1 Technology.....................................................................5 Packaging and Pricing Structure.........................................................................................8 How to Order Midsize Business Template........................................................................10 MBT Component Details and Capacities..........................................................................15 Upgrades and Migrations..................................................................................................20 Installation..........................................................................................................................21 Licensing............................................................................................................................22 Serviceability......................................................................................................................24 Software Support and Hardware Maintenance.................................................................24 Software Support...........................................................................................................25 Hardware Maintenance..................................................................................................25 Extended Manufacturers Software Support Policy........................................................25 Training and Documentation.............................................................................................25 Additional Resources.........................................................................................................25 Product Management Contacts.....................................................................................25 Appendix A: FAQ on EMSSP............................................................................................28 Appendix B: License Feature Reference..........................................................................30

2 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

Summary
The Avaya Aura for Midsize Enterprises includes a set of products that deliver rich Unified Communications (UC) and Call Center (CC) capabilities for companies between 101 to 2400 users, with up to 250 locations, and up to 2400 agents. New Avaya Aura System Platform virtualization technology provides faster, simpler deployment of Avaya applications. Beyond what is in this offer definition, you can find more information and collateral about this solution and its individual components at https://portal.avaya.com/ptlWeb/gs/products/P0540/AllCollateral Information about all other Avaya products can be found at: http://portal.avaya.com/ptlWeb/gs/products This product definition is a concise offer sheet detailing all pricing, licensing, and positioning, but only summarizing product operation and technical details. Links are provided to product documentation or training when more and better information should be located elsewhere. The channels can use this document to get a high-level product overview and sufficient pricing information to make informal quantitative proposals, but only a real quote from ASD should be used for formal quotes. NOTE: All pricing contained within, while accurate at the time of publication, should be considered as unofficial; the reader is directed to verify the accuracy of all prices cited after the products become generally available. This document contains Avaya-proprietary information and should not be shared with customers.

Avaya Aura for Midsize Enterprise Solution Description

The new Avaya Aura Midsize Enterprise solution consists of:

Avaya Aura Midsize Enterprise single server (aka: Midsize Business Template - MBT) Avaya one-X UC All Inclusive Contact Center Express Modular Messaging

Avaya Aura Midsize Enterprise single server (Midsize Business Template - MBT)
For the November launch, Avaya has packaged four (4) key Avaya Aura applications on one server using System Platform technology (described below). Also included are some key supporting applications and utilities intended to simplify system deployment and reduce ongoing ownership cost. This allows Avaya Aura to be sold and implemented as a complete single server communication system serving from 101 to 2,400 stations. Avaya is bringing to market a simple, single server solution focused on simplifying IP/SIP telephony roll-out to customers having from 101 to 2,400 stations. With this offer, the necessary Avaya Aura applications and utilities are deployed on only one server instead of across four servers and physical gateways are moved into software. Management is also simplified, and energy costs are lowered. Unified Communication can now be put within reach of midsize enterprise customers with the value of Avaya Aura applications all
3 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

installed on one Avaya S8800 or S8510 Server. This packaging of these applications is also referred to as a template. The Midsize Business Template (MBT) contains the following applications: Communication Manager 5.2.1 Communication Manager Messaging 5.2.1 SIP Enablement Services 5.2.1 (In a Home/Edge Combo configuration) Application Enablement Services 5.2 Media Services (software IP media gateway, purchased separately) Utility Services

As deployed on System Platform, each of these applications has the same features and capacities as if running standalone on separate servers. New from Avaya and included in this set of applications is Avaya Aura Media Services, a software IP media gateway built upon proven VoIP technology from our hardware media gateways. For a customer needing only H.323 IP or SIP phones and trunks, it is possible to avoid the cost of purchasing a hardware gateway by utilizing a SIP service provider for connectivity outside the enterprise. Media Services enables a true one-box deployment of Avaya Aura. If analog, TDM, or DCP endpoints and trunks are needed, an external gateway such as the low-cost G430 gateway can be used and is fully interoperable. A new dimension of business continuity and survivability, beyond Communication Managers robust architecture and Local Survivable Processor (LSP) support, is provided by System Platforms High Availability option. All component applications in the list above share this increased survivability. This is implemented by installing a second standby server identical to the first server that will start all the hosted applications in the relatively rare case that the first server should fail. Recovery time is expected to be from 4 to 5 minutes. And finally, the Utility Services component of this Avaya Aura deployment provides key tools and applications useful to support IP telephony in an enterprise:

HTTP and HTTPS fileserver for IP phones Dynamic Host Configuration Protocol (DHCP) server MyPhone (self administration tool for IP phone users) Call Detail Recording (CDR) collection tools Scheduling and control of IP phone firmware upgrades Control of IP phone settings via Graphical User Interface (GUI) settings editor

Avaya Aura Midsize Enterprise single server can be easily extended through the addition of other applications including Avaya one-X UC All Inclusive, Contact Center Express, Modular Messaging and Meeting Exchange, each of which offer a single server configuration either now or in the near future. These additional applications will each reside on separate hardware.

OPTIONAL: Avaya one-X UC All Inclusive single server configuration

A single server configuration for UC All Inclusive is available which enables midsize to large enterprises to deploy one virtual Integrated Server (IS) for up to 500 users for one-X Mobile 1.1, one-X portal 1.1 with Presence Server 1.0, Application Enablement Services for Unified Desktop with Microsoft Office Communication Server and IBM Lotus Sametime. The Integrated Server Solution (virtual appliance) will significantly reduce the cost and complexity of installing and supporting Avaya one-X applications. More information will be provided when this new configuration is formally announced. This solution was developed by Avayas DevConnect partner CRI, Inc. For more information, go to http://www.crinj.com/is.php and look for Integrated Server - UC.
4 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

OPTIONAL: Avaya Contact Center Express single server configuration

Contact Center Express can be deployed on a single blade server running multiple instances of VMware depending upon the hardware capacity and work load. For more information, contact Joachim Beck at [email protected]

OPTIONAL: Avaya Modular Messaging single server configuration

A single server configuration for Modular Messaging is now available enabled by System Platform that reduces the number of servers needed from as many as three (3) down to one (1). The single server configuration of Modular Messaging Release 5.2 will allow midsize enterprises to combine a Message Application Server (MAS), a Message Storage Server (MSS), optional Web Client and Web based Subscriber Options (WSO) servers, and a Secure Access Link (SAL) on a single Avaya Server. This server needs to be running Avaya Aura System Platform software and will be offered only with SIP integration, WebLM/Poetic licensing and the SAL for alarming and Avaya Services remote connectivity. Designed for a sweet spot of 1,000 mailboxes, the server will support up to 2,500 mailboxes with all the functionality of any other new Modular Messaging R5.2 installation, except that it does not support DVD-RAM for backup/restore (LAN based backup/restore is supported instead). For more information, go to https://enterpriseportal.avaya.com/ptlWeb/gs/products/P0042

OPTIONAL: Avaya Meeting Exchange single server configuration

A single server configuration for Avaya Meeting Exchange enables midsize to large enterprises to deploy one virtual Integrated Server (IS) for up to 500 users for Meeting Exchange Enterprise, Conference Reservation System, Web Portal, Avaya Web Conferencing, and Microsoft Live Meeting Adaptor. The Integrated Server Solution (virtual appliance) will significantly reduce the cost and complexity of installing and supporting Avaya Meeting Exchange applications. More information will be provided when this new configuration is formally announced. This solution was developed by Avayas DevConnect partner CRI, Inc. For more information, go to http://www.crinj.com/is.php and look for Integrated Server - Conferencing.

Avaya Aura System Platform 1.1 Technology

System Platform is a new technology that enables simplified deployment of Avayas products and solutions. However, Avaya Aura System Platform is not sold separately a product. It provides a common framework that leverages virtualization technology and common installation, licensing and support infrastructure to deliver and deploy Avayas applications effectively. The benefits of System Platform include: Ability to install pre-defined templates of one or more Avaya software applications on a server in a virtualized environment Simplified and faster installation of software applications and solutions Simplified licensing of applications and solutions Integrated SAL Gateway for remote access and alarming High Availability (HA) option for failover using active / standby server Coordinated backup and restore
5 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

Coordinated software upgrades

System Platform is engineered by Avaya to enable real-time communications solutions to perform effectively in a virtualized environment. System Platform effectively manages the allocation and sharing of server hardware resources, including the CPU, memory, disk storage, and network interfaces. In order to continue delivering the high reliability of real-time communications that Avayas customers expect, System Platform is being delivered solely via an appliance model, which includes an Avaya Server, System Platform, and the Avaya software applications.

Initially Avaya Aura for Midsize Enterprises (described above) will be deployed using System Platform; eventually System Platform will become the de-facto deployment method for many of Avayas software applications and solutions. System platform supports installation of unmodified Avaya products in a virtualized environment. These products are brought together into a pre-defined template that can be installed, managed, and supported in a common way and on shared server hardware. For the Midsize Business Template, the following applications are deployed on System Platform to enable the one-box solution:.

Hardware

End to End Management End to End Management Security and Serviceability Security and Serviceability

Intelligent Access and Enterprise Intelligent Access and Enterprise Application Integration Application Integration Collaboration & Interaction Collaboration & Interaction Solutions Solutions Core Communication Services Avaya Aura System Platform

Multivendor Integration Multivendor Integration

Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

Performance Analytics Performance Analytics

Communication Infrastructure Communication Infrastructure

Platform Console

CM
and CMM

SES

AES

Media Utilities Services

Packaged Avaya Aura application set for midsize deployments (the Template)

Linux

Linux

Linux

Linux

Linux

Linux
System Platform

Real-time Virtualization Hypervisor

HDD RAM
6

NIC

CPU

In summary, Avaya Aura System Platform provides a simplified common framework upon which Avaya solutions will be delivered and supported starting with Avaya Aura for Midsize Enterprises in November 2009

Supported Servers
MBT is supported by both the existing Avaya S8510 server (with RAM expanded to 8 GB, see below in the SAP Material Code section) and the new Avaya S8800 server. The S8800 series common server is a powerful and reliable processing platform that is ready to support Avaya Aura communications solutions today and in the future. The Avaya S8800 Server leverages Intels latest Xeon E5500 series (Nehalem) processor technology, and is available in both 1U and 2U form factors. Most Avaya applications will use the S8800 1U server chassis; some applications that require a large number of hard disk drives and / or plug-in cards will use the 2U version of Avaya S8800 Server. For MBT, the Avaya S8800 Server is sold in a specific configuration suitable for this solution. Size Midsize Enterprise solution 1U Processor (Intel Xeon Quad Core Nehalem) 5520 2.26 GHz # of CPUs 1 Dynamic RAM 12 GB Hard Disk Drive 3 x 146 GB

For more information on the S8800, including detailed server configurations and software release compatibilities for each application see:

The Avaya S8800 Server Channel Announcement on the Avaya Portal after the product becomes
generally available

The Product Transition Notice or other documentation for each adopting application on
support.avaya.com as they become generally available

System Platform High Availability

Avaya Aura System Platform provides an optional High Availability (HA) configuration which provides a uniform, server-level redundancy option for all the applications running on a single server. This two-server active/standby architecture uses disk mirroring technology (DRBD) which keeps the disk data on the standby server continuously synchronized with the disk data on the active server. Combined with running the application processes as virtual machines this makes the failover event indistinguishable from an unexpected reboot of the active server. All application data that has been written to disk is preserved on the failover. All applications on the standby have the same IP addresses as on the active. Any external system must reconnect just as it would following an unexpected reboot, but (other than doing a traceroute) no external system can tell the difference between a reboot of the active vs. a failover from the active to the standby. This configuration requires a physical connection (crossover LAN cable) between the active and standby servers. This cable serves both as a high speed, low latency connection used for disk mirroring and as a redundant communication path between the active and standby, allowing the standby to distinguish communication failures (which do not initiate a failover) from problems with the active server (which do). Because the systems must be physically connected with this cable, the active and standby must be located within 100 meters of each other.
7 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

For Communication Manager, HA provides connection preservation for Communication Manager when an external gateway is used. If the optional internal Media Services software gateway is used, connection preservation is possible only if the call is being shuffled directly between the two endpoints. The following figure shows how the two System Platform servers are deployed for High Availability.

Packaging and Pricing Structure

Avaya Aura MBT is an implementation of the Avaya Aura software offer. As such, the per-seat licensing structure and price is identical to that of Avaya Aura. However, because MBT is licensed using Avayas new licensing system (PLDS), it is necessary to order specific MBT material codes for all software components of MBT. The software editions and their functionality remain the same regardless. NOTE: When assessing the edition choice, keep in mind that the MBT offer is limited to enterprises with 101 2400 users. Avaya Aura Standard Edition meets the needs of single-site deployments requiring comprehensive voice, video, messaging, SIP and Presence communications capabilities with standard survivability at remote locations. Standard Edition has the option to easily add licensing for enterprise-wide SIP session management and Unified Communications applications for targeted users, including Microsoft and IBM UC integration, and mobile worker and teleworker support. Avaya Aura Enterprise Edition includes everything in Standard Edition and meets the needs of highly distributed, and potentially multinational, enterprises requiring the same comprehensive communications capabilities with increased high availability options including 100% feature survivability at remote locations. Enterprise Edition includes, with no additional cost, enterprise-wide SIP session management and Unified Communications applications for all Enterprise users, including Microsoft and IBM UC integration, and mobile worker and teleworker support.
8 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

All Avaya Aura Editions include appropriate management and administration tools. For details on the management applications available with each Edition see the Avaya Integrated Management 5.2 Pricing section below. Additional Avaya unified communications and contact center solutions, including rich unified messaging, conferencing and web collaboration, video endpoints and bridges, speech and video self service, and market-leading inbound and outbound multimedia contact center applications, can all be incrementally added to Avaya Aura Editions. An extensive array of certified third-party products is also available through the Avaya DevConnect ecosystem.

Avaya Aura MBT Packaging

The Avaya Aura MBT solution packages a set of capabilities targeted to enterprises with up to 2,400 stations leveraging the new System Platform technology. This subset of the normal Avaya Aura license offers is shown in the following table.

Avaya Aura
Software all hardware and support is additional

Standard Edition

Standard 5.2.1

Enterprise Edition

Enterprise 5.2.1

Avaya Aura Communication Manager Avaya Aura SIP Enablement Services Avaya Aura Communication Manager Messaging
(Built-in, can also add Modular Messaging)

500 users included

500 users included

TSAPI Basic included + $ licenses

Avaya Aura Application Enablement Services CTI

TSAPI Basic included + $ licenses

midsize business template (MBT)

Avaya Aura Application Enablement Services UC Avaya Aura Media Services

(new)

+$10,000 Only applicable on System Platform

+$10,000 Only applicable on System Platform

Avaya Aura System Platform (new)

(Available when configured. Not available separately)

+ $2,500 license

+ $2,500 license

Avaya Aura System Platform High Availability option

(Available when configured, Not available separately)

Avaya Aura Presence Services Avaya Integrated Management (as appropriate for Edition*) Avaya one-X UC All Inclusive
Avaya one-X Mobile, Avaya one-X Portal, Avaya one-X Communicator, Microsoft OCS and IBM Lotus Sametime integration, Extension to Cellular, VPNremote deskphone license

+$60 / User

Avaya Contact Center Express Modular Messaging single server configuration

Available with the new System Platform enabled single server configuration

+$ licenses

+$ licenses

+$ licenses

+$ licenses

- included - available for fee

* For a list of Integrated Management applications available with each Edition see product documentation

9 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

NOTE: Unless otherwise noted all pricing is shown as global list price in US $. Please refer to regional price lists for country specific pricing. All pricing contained within, while accurate at the time of publication, should be considered as unofficial; the reader is directed to verify the accuracy of all prices cited.

How to Order Midsize Business Template

When using the ASD configurator, a selection of either S8510/System Platform, S8510/System Platform w/High Availability, S8800/System Platform, or S8800/System Platform w/High Availability, must be made to properly design an MBT solution. The relevant field is shown in the screen capture below.

SAP Material Codes Software DVDs

SAP CODE DESCRIPTION MPG A1 A1 Global List Price $100.00 $100.00

700472376 AURA FOR MIDSIZE BUSINESS 5.2 DVD 700475882 AURA SYSTEM PLATFORM 1.1 DVD

10 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

Both DVDs are required for a complete install.

Supported Server and Options

SAP CODE 228992 226432 226431 DESCRIPTION S8800 SERVER MBT AURA SYS PLTFRM R5.2 HIGH AVAIL OPT AURA MEDIA SERVICES 5.2 SFTW LIC MPG IG DU DU Global List Price $8,500.00 $2,500.00 $10,000.00

To purchase the System Platform High Availability (HA) option, order two 228992 and one of 226432. The purchase and use of the software media gateway (Media Services) is optional. MBT fully supports the use of external gateways consistent with CM 5.2. However, H.323 endpoints require at least one of these external Gx50 gateways for call progress tones. Also, SIP endpoints require a Gx50 gateway if announcement-based CM features are needed. Note that the S8510 will be supported by the midsize business template (MBT) if a customer has this server in place, but it must be upgraded to 8GB of RAM and a complete software re-install must be done, including reformatting the hard drive. To re-use an existing S8510 for MBT, additional RAM needs to be purchased and installed to bring the server up to 8GB. Order quantity (3) of the following code from Avaya: SAP CODE 700454135 DESCRIPTION TWO 1GB DIMM FOR S8510 MPG A1 Global List Price $700.00

New License Purchase

These codes are used to add Avaya Aura licenses to a new installation, for either Standard Edition or Enterprise Edition. Choose between with Call Center and without Call Center depending on whether the customer needs to implement Elite Call Center agents. The without Call Center codes below do not entitle the customer to Elite agents. The with Call Center codes do allow the use of Elite agents, and additional Elite agent codes must be purchased to receive Call Center functionality. Refer to the Call Center Elite Agent section for the proper Elite Call Center material codes. Be sure to choose the codes for the MBT offer that meets the customers needs. SAP CODE DESCRIPTION MPG Global List Price

229008 229009 229010

229014 229015 229016

229005

New Standard Edition without Call Center Elite Agents (To be used when not needing Elite agent functionality) AURA MBT SE R5 1-100 NEW W/O CC LIC DU AURA MBT SE R5 101-1000NEW W/OCCLIC DU AURA MBT SE R5 1001+ NEW W/O CC LIC DU New Enterprise Edition without Call Center Elite Agents (To be used when not needing Elite agent functionality) AURA MBT EE R5 1-100 NEW W/O CC LIC DU AURA MBT EE R5 101-1000NEW W/OCCLIC DU AURA MBT EE R5 1001+ NEW W/O CC LIC DU New Standard Edition with Call Center Elite Agents (Additional CC codes need to be ordered at the desired quantities) AURA MBT SE R5 1-100 NEW W/CC LIC DU
11

$240.00 $210.00 $205.00

$320.00 $290.00 $285.00

$240.00

Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

229006 229007

229011 229012 229013

AURA MBT SE R5 101-1000 NEWW/CC LIC DU AURA MBT SE R5 1001+ NEW W/CC LIC DU New Enterprise Edition with Call Center Elite Agents (Additional CC codes need to be ordered at the desired quantities) AURA MBT EE R5 1-100 NEW W/CC LIC DU AURA MBT EE R5 101-1000 NEWW/CC LIC DU AURA MBT EE R5 1001+ NEW W/CC LIC DU

$210.00 $205.00

$320.00 $290.00 $285.00

Upgrade License Purchase

These codes are used to upgrade existing DEFINITY, Communication Manager, MultiVantage Express (MVE), and Communication Manager Express (CME) on any prior release to Avaya Aura 5.2 for midsize Enterprises, for either Standard Edition or Enterprise Edition. Choose between with Call Center and without Call Center depending on whether the customer needs to implement Elite Call Center agents. The without Call Center codes below do not entitle the customer to Elite agents. The with Call Center codes do allow the use of Elite agents, and additional Elite agent codes must be purchased to receive Call Center functionality. Refer to the Call Center Elite Agent section for the proper Elite Call Center material codes. Be sure to choose the codes for the MBT offer that meets the customers needs. NOTE: As mentioned above, MBT will run on the Avaya S8510 Server if the customer has one (with 8 GB of RAM installed), otherwise a new Avaya S8800 Server must be purchased for the upgrade. SAP CODE DESCRIPTION MPG Global List Price

229020 229021 229022

229026 229027 229028

229017 229018 229019

229023 229024 229025

Upgrade Standard Edition without Call Center Elite Agents (To be used when not needing Elite agent functionality) AURA MBT SE R5 1-100 UPG W/O CC LIC DU AURA MBT SE R5 101-1000UPG W/OCCLIC DU AURA MBT SE R5 1001+ UPG W/O CC LIC DU Upgrade Enterprise Edition without Call Center Elite Agents (To be used when not needing Elite agent functionality) AURA MBT EE R5 1-100 UPG W/O CC LIC DU AURA MBT EE R5 101-1000UPG W/OCCLIC DU AURA MBT EE R5 1001+ UPG W/O CC LIC DU Upgrade Standard Edition with Call Center Elite Agents (Additional CC codes need to be ordered at the desired quantities) AURA MBT SE R5 1-100 UPG W/CC LIC DU AURA MBT SE R5 101-1000 UPGW/CC LIC DU AURA MBT SE R5 1001+ UPG W/CC LIC DU Upgrade Enterprise Edition with Call Center Elite Agents (Additional CC codes need to be ordered at the desired quantities) AURA MBT EE R5 1-100 UPG W/CC LIC DU AURA MBT EE R5 101-1000 UPGW/CC LIC DU AURA MBT EE R5 1001+ UPG W/CC LIC DU

$36.00 $31.00 $30.00

$48.00 $43.00 $42.00

$36.00 $31.00 $30.00

$48.00 $43.00 $42.00

Migration License Purchase

12 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

These codes are used to migrate existing Communication Manager 5.0 and 5.1, MultiVantage Express (MVE) 2.0 w/ SS+U, and Communication Manager Express (CME) 5.1 to Avaya Aura 5.2 for Midsize Enterprises, for either Standard Edition or Enterprise Edition. Note there is no license cost for this migration. Choose between with Call Center and without Call Center depending on whether the customer needs to implement Elite Call Center agents. The without Call Center codes below do not entitle the customer to Elite agents. The with Call Center codes do allow the use of Elite agents, and additional Elite agent codes must be purchased to receive Call Center functionality. Refer to the Call Center Elite Agent section for the proper Elite Call Center material codes. Be sure to choose the codes for the MBT offer that meets the customers needs. NOTE: As mentioned above, MBT will run on the Avaya S8510 Server if the customer has one (with 8 GB of RAM installed), otherwise a new Avaya S8800 Server must be purchased for the upgrade. SAP CODE DESCRIPTION MPG Global List Price

229032 229033 229034

229038 229039 229040

229029 229030 229031

229035 229036 229037

Migrate Standard Edition without Call Center Elite Agents (To be used when not needing Elite agent functionality) AURA MBT SE R5 1-100 MIG W/O CC LIC DU AURA MBT SE R5 101-1000MIG W/OCCLIC DU AURA MBT SE R5 1001+ MIG W/O CC LIC DU Migrate Enterprise Edition without Call Center Elite Agents (To be used when not needing Elite agent functionality) AURA MBT EE R5 1-100 MIG W/O CC LIC DU AURA MBT EE R5 101-1000MIG W/OCCLIC DU AURA MBT EE R5 1001+ MIG W/O CC LIC DU Migrate Standard Edition with Call Center Elite Agents (Additional CC codes need to be ordered at the desired quantities) AURA MBT SE R5 1-100 MIG W/CC LIC DU AURA MBT SE R5 101-1000 MIGW/CC LIC DU AURA MBT SE R5 1001+ MIG W/CC LIC DU Migrate Enterprise Edition with Call Center Elite Agents (Additional CC codes need to be ordered at the desired quantities) AURA MBT EE R5 1-100 MIG W/CC LIC DU AURA MBT EE R5 101-1000 MIGW/CC LIC DU AURA MBT EE R5 1001+ MIG W/CC LIC DU

$0 $0 $0

$0 $0 $0

$0 $0 $0

$0 $0 $0

Analog Station Licenses

These codes are use to purchase new analog station licenses and also to uplift them to universal station licenses and parallel the previously-announced codes offered on Communication Manager 5.2. For more information on analog licensing, refer to the Communication Manager 5.2 product definition. SAP CODE 226818 229041 229042 229043 DESCRIPTION MPG Global List Price $40.00 $200.00 $170.00 $165.00

New AURA MBT ANALOG NEW LIC DU Uplift to Universal Station on Standard Edition AURA MBT ANA-SE 1-100 UPLIFT LIC DU AURA MBT ANA-SE 101-1000 UPLIFT LIC DU AURA MBT ANA-SE 1001+ UPLIFT LIC DU
13

Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

229044 229045 229046

Uplift to Universal Station on Enterprise Edition AURA MBT ANA-EE 1-100 UPLIFT LIC DU AURA MBT ANA-EE 101-1000 UPLIFT LIC DU AURA MBT ANA-EE 1001+ UPLIFT LIC DU

$280.00 $250.00 $245.00

Uplift Edition Licenses

After the initial sale of MBT, some customers may want to change the Avaya Aura edition, or may want to begin using Call Center Elite agents. Use the codes below to make these changes. SAP CODE DESCRIPTION MPG Global List Price

229370 226881

229371 226881

229372

229373

229374 226881

Uplift Standard Edition without Call Center Elite Agents To Enterprise Edition without Call Center Elite Agents Order BOTH codes AURA MBT SE R5 W/O CC TO EE W/O CC LIC DU DU AURA MBT SE R5 TO EE UPLIFT SW LIC Uplift Standard Edition with Call Center Elite Agents To Enterprise Edition with Call Center Elite Agents Order BOTH codes DU AURA MBT SE R5 W/CC TO EE W/CC LIC AURA MBT SE R5 TO EE UPLIFT SW LIC DU Uplift Standard Edition without Call Center Elite Agents To Standard Edition with Call Center Elite Agents AURA MBT SE R5 W/O CC TO SE W/CC LIC DU Uplift Enterprise Edition without Call Center Elite Agents To Enterprise Edition with Call Center Elite Agents AURA MBT EE R5 W/O CC TO EE W/CC LIC DU Uplift Standard Edition without Call Center Elite Agents To Enterprise Edition with Call Center Elite Agents Order BOTH codes AURA MBT SE R5 W/O CC TO EE W/CC LIC DU DU AURA MBT SE R5 TO EE UPLIFT SW LIC

$0 $115

$0 $115

$0

$0

$0 $115

CM Messaging Licenses
Avaya Aura includes 500 seats for CM Messaging, formerly known as IA770, for both Standard and Enterprise editions. For more than 500 seats, purchase the addition quantity using the code below. SAP CODE 226667 DESCRIPTION CM MSGING R5.2 MBT NEW/ADD LIC 501+ MPG DU Global List Price $35.00

UCE All Inclusive

Licenses for UC All Inclusive are included in Enterprise Edition for every seat of Avaya Aura purchased. For Standard Edition, order the following codes to purchase UC All Inclusive:
14 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

SAP CODE 229200 229201 229341

DESCRIPTION New or Add UCE R5.2 STD/W MBT NEW UCE R5.2 STD/W MBT ADD Upgrade UCE R5.2 STD/W MBT UPG

MPG IE IE IE

Global List Price $60.00 $60.00 $0

AES Licenses
Avaya Aura Standard and Enterprise editions include a TSAPI Basic license for each purchased seat. Additional TSAPI licenses can be purchased, as well as other AES license types. AES on MBT supports the same features and functionality as standalone AES. Please refer to the AES offer documentation on the Enterprise Portal for more information.

Call Center Elite Agent Licenses

Avaya Aura MBT fully supports Call Center Elite agents. These agents are purchased separately, just as they are with CM running standalone. However, Elite agents requires the with Call Center Avaya Aura license codes listed above, or it will not be possible to administer these agents. SAP CODE 229140 229141 229142 229143 229144 229145 229146 229147 229148 DESCRIPTION New and Add licenses AURA MBT CC R5 NEW/ADD ELITE 1-100 AURA MBT CC R5 NEW/ADD ELITE 101-250 AURA MBT CC R5 NEW/ADD ELITE 251+ Single-release upgrades AURA MBT CC R5 ELITE SNGL UPG 1-100 AURA MBT CCR5 ELITE SNGL UPG 101-250 AURA MBT CC R5 ELITE SNGL UPG 251+ Multi-release upgrades AURA MBT CC R5 ELITE MULTI UPG 1-100 AURA MBT CCR5 ELITE MULTIUPG 101-250 AURA MBT CC R5 ELITE MULTI UPG 251+ MPG DU DU DU DU DU DU DU DU DU Global List Price $680.00 $525.00 $270.00 $170.00 $131.00 $68.00 $238.00 $184.00 $95.00

For more information see the Call Center Product Definition at: http://portal.avaya.com/ptlWeb/gs/products/P0009/JobAidsTools/003961119

MBT Component Details and Capacities

Communication Manager
Communication Manager supports all the features, functions, and capacities of CM 5.2.1 when running standalone on an S8510 or S8800 server, with the following notes and exceptions:

15 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

ESS: It is not possible to connect an external ESS server to the MBT main server. The System Platform High Availability option provides very similar redundant failover as the ESS and should be used instead. LSP: Up to 250 LSP remote gateways are supported. Note: These LSPs will not be implemented on System Platform and should be ordered with the same material codes listed in the Communication Manager 5.2 product definition or as output by the ASD configurator. An LSP operating with MBT is licensed differently than other LSPs. Refer to the Licensing section of this document. A few CM licensed features are not available on MBT. Refer to the table in the Appendix for a complete list of all these features.

Capacities Besides the offer limit of 2400 stations, the capacities for CM in MBT are identical to those of CM 5.2.1 running on either the S810 or S8800 servers. A comprehensive table is here: CM 5.2.1 System Capacities Table

Communication Manager Messaging (CMM)

This is the new term for IA770 embedded messaging. Capacities CMM on MBT have a mailbox limit of 2400. All other capacities for CMM in MBT are identical to those of CM/CMM 5.2.1 running on either the S810 or S8800 servers. A comprehensive table is here: CM 5.2.1 System Capacities Table

Call Center
Call Center supports all the features, functions, and capacities of CC 5.2 when running standalone on an S8510 or S8800 server, with the following notes and exceptions: A few CC licensed features are not available on MBT. Refer to the table in the Appendix for a complete list of all these features.

Capacities CC on MBT has a limit of 2400 elite agents. All other capacities for CC in MBT are identical to those of CC 5.2 running on either the S8510 or S8800 servers. A comprehensive table is here: CM 5.2.1 System Capacities Table

SIP Enablement Services (SES)

SES as deployed on MBT is pre-configured as a home/edge combo with a license quantity matching the number of Avaya Aura licenses purchased. In all other ways, SES functionality is identical to SES running
standalone.

Capacities SES on MBT has a limit of 2400 SIP stations. All other capacities for SES in MBT are identical to those of SES 5.2.1 running on either the S810 or S8800 servers. A comprehensive table is here: CM 5.2.1 System Capacities Table
16 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

Application Enablement Services (AES)

Capacities The capacities for AES in MBT are comparable to those of AES 5.2 running on either the S810 or S8800 servers with the exception that 400 messages per second are achievable with AES on MBT instead of 1000 mps with AES standalone.

Media Services
New from Avaya and included in MBT as an optional application is Avaya Aura Media Services, a software IP media gateway built upon proven VoIP technology from our hardware media gateways. For a customer needing only H.323 IP or SIP phones and trunks, it is possible to avoid the cost of purchasing a hardware gateway by utilizing a SIP service provider for connectivity outside the enterprise. Media Services enables a true one-box deployment of Avaya Aura. If analog, TDM, or DCP endpoints and trunks are needed, an external gateway such as the low-cost G430 Gateway can be used and is fully interoperable. There are 256 DSP channel resources available with Media Services. However since this is a software implementation only, it will not support legacy TDM, DCP, T1/E1, analog or any other non-Ethernet based connections. If connections of this type are needed, simply provision an external gateway, such as the G430, to provide connection to legacy endpoints and trunks. Media Services and external gateways are fully interoperable and complement each other: using Media Services and its complement of 256 channels allows the use of a smaller, less expensive external hardware gateway if needed for legacy support. The Media Services gateway appears to Communication Manager as a G650 equipped with four TN2302 Media Processors, a TN2501 (VAL) announcement board, and one TN2312B IP Server Interface (IPSI). Configuration and administration of the Media Services gateway is identical to this G650 configuration, and in fact CM cannot tell the difference. Capacities Media Services capacity covers the range of users for MBT, 101-2400 with typical call patterns.

Communication Manager View of Media Services

17 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

Supported Features Not all hardware gateway features are provides by Media Services, in particular analog and legacy endpoints as noted above. There are others as shown in the table below.

Major Feature Codecs G.711 channels G.729 channels channel type FAX modem TTY 64kbps unrestricted data echo cancellation

G650 + TN2302BP x 4 G.711, G.723.1, G.729(B) 4 x 64 (10-60 msec) 4 x 32 IP and legacy TDM pass-through, relay, T.38 relay pass-through, V.32 relay pass-through, relay clear channel 32 ms full tail

Media Services G.711, G.729A(B) 4 x 64 (10-60 msec) 4 x 22 IP only N/A N/A N/A N/A N/A

18 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

6-party conferencing media encryption fw download? RFC 2833 DTMF RTCP reporting/VMM VLAN tagging RSVP 802.1p/Q Announcements/MOH Hairpinned channels Alarms Call progress tone generation IP media signaling Network regions Call classification support ESS compatibility MF signaling # supported LANs

Yes AEA, AES (reduced channels) Yes Yes Yes Yes Yes Yes optional TN2501 VAL Yes CM 25 countries (a la TN2312) Processor Ethernet and/or CLAN 1-4 Yes Yes Yes 4

Yes No S/W Upgradeable Yes No No No No Yes No CM 25 countries Processor Ethernet 1-4 No N/A N/A 1

Utility Services
The Utility Services component of MBT provides key tools and applications useful to support IP telephony in an enterprise and enables MBT to be a one-box solution. The use of these components is optional and the customer may choose to use an alternate implementation or process to accomplish any or all of these functions. HTTP and HTTPS fileserver for IP phones Web Server used to provide firmware download to IP phones. Dynamic Host Configuration Protocol (DHCP) server Server used to assign IP addresses to IP phones.
19 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

MyPhone (self administration tool for IP phone users) MyPhone is a web-based user utility which provides self-administration for certain IP phone features. Login authentication to MyPhone is the phone extension number and station security code (PIN). Some of the features provided are:

Manage EC500: Change the off premises phone number, and the phone numbers used for call forwarding Add buttons to their own phones, but administrators can restrict which buttons are available to be added Change station security code (PIN)

Call Detail Recording (CDR) collection tools These tools provide basic CDR recording and report generation for those customers who do not want to purchase external CDR systems from third-party vendors. Features include:

Retrieves call information from CM and places it in a database Reports creation, including longest calls, busiest users and most dialled numbers Database export is possible for use with an external customer database system for more customer specific database queries External access (read only) to database possible for running custom reports via third-party query tools that support access to postgres

Scheduling and control of H.323 IP phone firmware upgrades List all registered IP phones firmware versions Schedule Upgrades based on a time window Upgrade throttling for large numbers of stations Retries for station upgrades during upgrade window Report on station upgrades performed Note: Stations must be registered to CM as extensions and H.323 stations only

Control of IP phone settings via Graphical User Interface (GUI) settings editor Intended for system administrators, this utility provides a GUI interface to create and modify the settings text file which is downloaded to each IP phone. These setting are often considered obscure and this tool provides help text, value verification, and default settings.

Upgrades and Migrations

All designs for MBT systems are done as new. There are no processes in RFA, PLDS, or in Services to migrate an existing CM system to MBT. All MBT installs are done as new systems, a new PLDS license must be obtained, and the CM translations must be built new. However, product management is offering the usual upgrade license discounts for customers currently running a version of Communication Manager and the ASD design tool will put out the correct license codes at the lower price. Keep in mind that an upgrade to MBT 5.2.1 is always also a migration since a new S8800 server (or a reconfigured S8510) is needed.
20 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

When using ASD to design the new MBT system, be sure to include every feature the customer is already using or paid for on his current system. For example, if the customer has CM Express (CME) all the features provided by that offer are also provided by MBT and the customer is entitled to use them. Here are the offer rules regarding upgrades/migrations. The actual material codes are listed in the SAP Material Code section of this document.

Customers running CM 5.0, CM 5.1, CM 5.2, or CME 5.1 (which uses CM 5.1) get a $0 license upgrade Customers running MVE 2.0 (which uses CM 4.0) and who purchased SS+U get a $0 license upgrade Customers running MVE 2.0 (which uses CM 4.0) and who did not purchase SS+U get a reducedcost license upgrade Customers running CM 4.x or earlier or MVE 1.0 (which uses CM 3.x) and who purchased UPPCM which is still valid get a $0 license upgrade Customers running CM 4.x or earlier or MVE 1.0 (which uses CM 3.x) who did not purchase UPPCM get a reduced-cost license upgrade

Installation
Installation Overview
When implementing an Avaya solution, System Platform is first installed on the server hardware, and then the MBT template is installed on System Platform.

SP

On-site or Remotely Installabl e

Select an Avaya Server

Install the System Platform

Select and Install Application Template

In a nutshell, the installation process for a typical solution or template using System Platform:
21 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

Rack mount the server Insert System Platform CD / DVD / USB stick Configure basic IP settings Reboot Log into System Platform Web Console Select required Solution Template from Web download site, DVD or USB stick Template Installation Wizard runs (can be run offline before hardware arrives) Plug in IP phones, configure any gateways, etc.

This process allows the system to be installed and provisioned with users and a basic setup in a target time of 1-2 hours depending on system size.

Licensing
MBT License Design
Communication Manager and Call Center Licensing for Communication Manager in MBT is greatly simplified over that of previous versions of Communication Manager. The total licensed feature set has been reduced from over 300 to around 10:

1. Avaya Aura station licenses: This is the total quantity of stations purchased, with a maximum of
2400.

2. Avaya Aura edition: Avaya Aura is sold in two editions, Standard and Enterprise. For each of these
two editions, Call Center Elite agent licensing is an option, which leads to four type of license codes as seen in the SAP material code tables above. Depending on the edition purchased, and on whether elite agents are used, all the other 300+ CM and CC features are determined and set to known values. A listing of these settings is in the Appendix. It is very important to note that it is not possible to change any of these fixed settings, either though system administration, license file manipulation, or material code purchase. SIP Enablement Services (SES) No license file is required for SES. The MBT implementation of SES includes a default license file set to the maximum number of SIP stations on the platform and the SIP server is pre-configured to be a home/edge combo. It is not possible to change this configuration. Application Enablement Services (AES) AES on MBT is licensed using the same material codes as the standalone AES 5.2. AES 5.2 on MBT includes a TSAPI basic license for each station license purchased for MBT (standard edition and enterprise edition). Additional TSAPI Basic licenses as well as TSAPI Advanced, DMCC, CVLAN and DLG licenses may be purchased for their normal price using the AES 5,2 material codes, Media Services The optional Media Services software gateway requires a purchased license to operate. If Media Services is not purchased, it will not be installed on MBT.
22 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

LSP and ESS MBT fully supports up to 250 LSPs in the same server/gateways configurations as CM 5.2.1. These LSPs do not use System Platform and are exactly the same LSPs as deployed in any CM network. ESS servers are not supported by MBT. You should consider System Platform High Availability (HA) as an alternative. LSPs used with an MBT server are not licensed by PLDS or RFA. A license file is not installed. Instead, during configuration of the LSP a special command is run to allow the LSP to operate without a license. For details, see Appendix D in the Installing and Configuring Avaya Aura Solution for Midsize Enterprises document at http://support.avaya.com/css/P8/documents/100068119.

PLDS
Avaya Aura MBT uses a new system called PLDS (Product Licensing and Delivery System) for Order to License Management. RFA will not be used for MBT licensing. Benefits include improved customer satisfaction, better revenue protection and license term compliance, reduced business costs, and decreased cycle time for servicing and software delivery. PLDS is accessed at the following website: https://plds.avaya.com Customer features and benefits With RFA, customers had no ability to manage their software licenses. With PLDS, customers have full control over licenses and are, in fact, responsible for their own software licensing. For customers not wanting to get involved in licensing, BusinessPartners or Avaya can act on their behalf. The following customer actions are possible with PLDS, and there is no fee associated with any of these: Activate Software Licenses View Software Entitlements View SW and patches available for download Download Software (including full system images) Upgrade Software without an SAP order (if under SSU) Re-host Licenses

Basic Steps from Order to License 1) 2) 3) 4) Designer configures MBT design using ASD BP or account team converts quote to SAP order After the SAP order clears credit-check, it will flow automatically to PLDS PLDS sends out notification to email address(es) on the order. This will be the end user customers and a BusinessPartner or Avaya account team member. 5) Customer (or BP or Avaya) follows links in the email to access PLDS 6) Customer (or BP or Avaya) uses PLDS to activate purchased licenses and download a license file 7) Customer (or BP or Avaya) uses PLDS to download the software Contact Information For more information on how to use PLDS, training and documentation are available at:
23 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

http://portal.avaya.com/ptlWeb/licensinganddownloads NOTE: Product Management is unable to provide support on how to use PLDS. For assistance on how to use the PLDS system and tools, contact 1-866-AVAYA-IT (1-866-282-9248). For general information on PLDS, contact Ammi Marrero at [email protected].

Serviceability
Avaya Aura System Platform provides many simplifications and enhancements to the MBT serviceability model. Most of these are new methods for remote access and alarming, replacing the modem-based SAMP architecture.

Secure Access Link (SAL)

As part of an ongoing effort to improve remote access, service methods, and value-add applications, Avaya is embarking on a new architecture which will significantly change and improve the methods by which customers can receive support through local and remote access. This new concept fundamentally eliminates the requirement for Avaya to have unfettered 24x7-access to equipment located on our customers networks. Furthermore, it places the customer in complete control of when and how Avaya, or any other service provider, can access customer equipment. Finally, with this new concept, Avayas customers can truly achieve channel-neutral support by allowing for complete self-service or enabling business partners to support customers to a level they have never achieved previously. The Secure Access Link architecture is composed of three components; The Software Gateway, Policy Server, and Concentrator Servers. These software only applications will be used in combination to support a customers environment that is composed of legacy, current and future Avaya Solutions. The Secure Access Link Applications are intended to be installed on customer provided hardware or Avaya will optionally provide a server for an additional cost (Server Specifics below). The SAL Applications can be customer or Partner installed and Avaya Global Support Services offers support for the installation of the Secure Access Link Gateway and Policy Server Solutions apart of the Implementation offer portfolio. Support for the installation of a SAL Solution to includes Remote Project Management and Remote Software Configuration with the option to purchase onsite hardware installation separately. The SAL Gateway is installed with the Avaya Aura System Platform, so a separate server is not needed for SAL when purchasing MBT. The customer does not have to install a separate SAL gateway server. More details on SAL can be found on the Enterprise Portal at https://enterpriseportal.avaya.com/ptlWeb/gs/services/SV0507 For more information on SAL, please contact Dan Herrera at [email protected]

Software Support and Hardware Maintenance

24 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

Software Support
Software Support and Upgrade coverage is available for Avaya Aura MBT and the coverage is identical to that offered for Communication Manager 5.x. Please refer to the offer documentation for Communication Manager available on the Enterprise Portal for more information. However, the SAP codes to purchase this coverage are unique to MBT and will be configured by ASD.

Hardware Maintenance
For hardware, there are three (3) simplified offers: Remote Hardware Maintenance, Remote Hardware Maintenance with Advance Parts Replacement, and On-Site Hardware Maintenance with a choice of 8 x 5 or 24 x 7 Coverage. All offers include Expert SystemsSM diagnostics and 24 x 7 remote technical support. The Advance Parts and On-Site offers also include equipment replacement. Customers requiring fully comprehensive monitoring will want to combine SS+U with any of the Hardware Maintenance offers. Complete details on Software Support and Hardware Maintenance, including specifics about upgrades to Communication Manager 5.2, are available at http://portal.avaya.com/ under Services / Product & IP Support / Product Support / Offering / Software Support and Hardware Maintenance.

Extended Manufacturers Software Support Policy

Avaya Aura MBT is covered by Avayas new Extended Manufacturers Software Support Policy (EMSSP), which will provide a longer period of Manufacturers support for selected releases of a product. The policy goes into effect in November 2009 with the introduction of Communication Manager 5.2.1. It will provide Manufacturers Support of named releases for a period of three (3) years from November 2009. In addition, it is Avayas intention to sell these releases for a period of two (2) years to allow customers ample time to deploy the releases in their enterprise. No dot releases are planned on the product software releases covered by this policy (see the Appendix of EMSSP) but the products will offer service packs as necessary to fix issues within the release.

Training and Documentation

A complete list of all training and documentation is available at the following website: http://support.avaya.com/css/Products/P0586

Additional Resources
Product Management Contacts
Product Avaya Aura Avaya Aura Communication Christopher E. Johnson Manager, Midsize Business Template Avaya Aura Beth Smith
25 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

Contact

Email [email protected]

[email protected]

Avaya Aura Session Manager Avaya Aura System Manager 1.0 Avaya Aura System Manager 2.0

Steve Durney Eran Shapiro Frank Chang

[email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]

Avaya Aura Communication Ron Kidd (Global) Manager Branch Michael Zhu (APAC) Andres Ramirez (CALA) Gavin Stewart (EMEA) Avaya Aura SIP Enablement Services Ron Kidd

Avaya Aura Communication Paola Benassi Manager Messaging Mike Wasserburger Avaya Aura Application Enablement Services UC (DMCC, Unified Desktop, SMS, servers) Avaya Aura Application Enablement Services CC (CVLAN, DLG, TSAPI, T) Avaya Aura Presence Services Avaya one-X UC All Inclusive Avaya Integrated Management Tom Rowland

Cathy Smyth

[email protected]

Ira Kucheck Daniel Cardaropoli Eran Shapiro

[email protected] [email protected] [email protected]

Product Related Products & Solutions Branch Media Gateways Call Center Contact Center Express Customer Service Editions Solutions for Midsize Enterprises Intelligent Customer Routing

Contact Yossi Asyag Bill Jolicoeur Girish Vasvani Stefan Rueck Bruce Mazza Laura Bassett

Email [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]

26 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

Meeting Exchange one-X Agent one-X Mobile, one-X Portal, EC500 one-X Communicator, Softphone clients Servers

Matt ODonnell Michael Harwell Julie Thiesen Phil Klotzkin Cecilia Perez-Benitoa

[email protected] [email protected] [email protected] [email protected] [email protected]

Software Support and Hardware Maintenance Extended Manufacturers Software Support Policy Jan Leistikow [email protected]

27 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

Appendix A: FAQ on EMSSP

Frequently Asked Questions on EMSSP

1. What products are covered under the Extended Manufacturer Software Support Policy? Generally the policy covers products that are beyond their first release and are the last update release within a major release. Initially the following components of Avaya Aura will be covered: Avaya Aura Communication Manager 5.2.1 Avaya Aura Communication Manager Messaging 5.2.1 Avaya Aura Application Enablement Services 5.2

Other products included in the policy:

Call Center 5.2.1 Modular Messaging 5.2 Meeting Exchange 5.2

2. What products are not included in the policy? Some components of Avaya Aura are in early releases or are otherwise unsuitable for an extended 3 year support policy. These products are not currently covered: Avaya Aura Session Manager Avaya Aura System Manager Avaya Integrated Management Avaya one-X / UC All-Inclusive bundle Avaya Aura Branch Edition

3. Will other products be added over time? As Avaya Aura components and other products move into maturity they will be considered for coverage under EMSSP. 4. Is EMSSP optional for customers? Yes. Customers are under no obligation to move to EMSSP for those products that are covered under the policy. In addition, customers can choose to move to more recent releases (not covered by EMSSP) as appropriate to their needs. 5. Does this change the Avaya Manufacturers Support Policy? No. Avaya Manufacturers Support Policy continues to exist and is leveraged by most products across the portfolio. EMSSP is incremental to that policy and applies only to certain releases of products being tagged for inclusion under EMSSP. The Extended Manufacturers Software Support Policy is consistent with the terms of the Avaya Manufacturers Support Policy, but provides additional length of support for the included products and components. 6. How does this policy compare to the Avaya Extended Support Policy?
28 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

Avaya Extended Support Policy, also known as Extended Maintenance, provides services support for products that are no longer covered under Manufacturers Support or Extended Manufacturers Support. Extended Maintenance does not provide for escalations into CPE (Tier IV) including patches for newly found problems. 7. How does this affect Software Support and Software Support + Upgrades (SS+U)? Software Support or other forms of software maintenance will be required to leverage EMSSP. SS+U will continue to be of value to many customers that upgrade on a regular basis. The new EMSSP may allow customers to upgrade later in the cycle of support to minimize disruption to their business. 8. Must all components of Avaya Aura adhere to EMSSP? No. Each component can have its own support policy. 9. What if there are extenuating circumstances that force a new dot release? Does that become the EMSSP release? Yes. The new release would become the EMSSP release, but the support period does not start over with the new release. In this situation the Avaya Patch Policy applies, which requires the customer to move to the new dot release within a designated period of time. 10. Does this policy discourage customers from upgrading? Typically, customers upgrade as they see fit based on emerging new functionality that has been created in response to better meeting evolving customer needs. Customers will still be encouraged to buy SS+U since it eliminates the need for capital expense approval, making it easier to purchase. They will still want to upgrade to a newer release as the EMMSP load nears the end of its lifecycle. Keep in mind that customers can always choose to purchase the newest release of software and its dot releases. 11. What type of customer will be interested in EMSSP? Customers that have deployments with multiple adjuncts that require testing against a specific release Customers that want a predictable period of support on the release that they have certified and tested (i.e. 5.2.1) Customers that have long deployment periods many sites that require a common release. Customers that require release maturity over new features

12. Is there an additional charge for EMSSP. No but the customer must have either Software Support (SS) or Software Support plus Upgrades (SS+U), otherwise there is no additional charge.

29 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

Appendix B: License Feature Reference

Licensing for MBT is considerably different from previous versions of Communication Manager and related applications. PLDS, not RFA, is used to keep track of purchased product, issue licenses, and enable software downloads. This is the going-forward strategy for all Avaya licensed software. Although CM feature functionality internally is still controlled by more than 300 individual license features, only about 10 are now exposed in the license file:

1) VALUE_CM_STA: The number of Avaya Aura seats or stations purchased 2) VALUE_CM_OFFER: The particular Avaya Edition purchased, as follows
a. b. c. d. 1: Standard Edition, without Call Center Elite agents 2: Standard Edition, with Call Center Elite Agents 3: Enterprise Edition, without Call center Elite agents 4: Enterprise Edition, with Call center Elite agents

The offer types with Call Center Elite agents require the separate purchase of elite agents using the codes defined above on this document. The offer types without Call Center Elite agents will not allow the administration of elite agents, even if they are purchased separately. All the other CM features previously in the RFA license file are now hidden and are set by the two features above. The tables below show every CM feature and whether it is available or not in the MBT offer. NOTE: It is not possible to change any of the settings in the tables below, neither with an ordered material code, with CM administration, nor by escalating to IT or product management. If you absolutely must use CM with a different setting, MBT will have to be replaced with separate standalone systems running CM 5.2.1and any other application you were using on MBT. In this case, RFA will allow total control of the CM features.

Please do not contact Avaya to get these features changed. It is not possible. Table A1: ON/OFF License Features
Features always ON --- MBT fully supports all these features in all offers --(cannot be turned OFF)
Feature Keyword FEAT_AC FEAT_ACCG FEAT_ACD FEAT_ADE Feature Display Name Authorization Codes? Adjunct Call Control? ACD? Abbreviated Dialing Enhanced List?
30 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

Feature Keyword FEAT_MCHAND FEAT_MCT FEAT_ME FEAT_MFS

Feature Display Name Multiple Call Handling (On Request)? Malicious Call Trace? Media Encryption Over IP? Multifrequency Signaling?

FEAT_ADJLK FEAT_ADN FEAT_AMW FEAT_ANS FEAT_ANSMD FEAT_ARG FEAT_ARS FEAT_ASAI* FEAT_ASAIPLUS* FEAT_ATDVEC FEAT_ATMS FEAT_BRITRK FEAT_BSCVEC FEAT_CFWD FEAT_COV_OFFNET FEAT_CTI FEAT_CVM_MC FEAT_DADMIN FEAT_DCG FEAT_DCS FEAT_DCSCC FEAT_DCSINWK FEAT_DCSWRR FEAT_DIG_LOSS FEAT_DS1_ECHO FEAT_DS1MSP FEAT_EC500 FEAT_EHCNF

Computer Telephony Adjunct Links? A/D Grp/Sys List Dialing Start at 01? Audible Message Waiting? Answer Supervision by Call Classifier? Answer Machine Detect Adjunct Routing? ARS? ASAI Link Core Capabilities? ASAI Link Plus Capabilities? Attendant Vectoring? ATMS? ISDN-BRI Trunks Vectoring (Basic)? Restrict Call Forward Off Net? Cvg Of Calls Redirected Off-net? CTI Stations? Mode Code for Centralized Voice Mail? Enable dadmin login? Domain Control? DCS (Basic)? DCS Call Coverage? Interworking with DCS? DCS with Rerouting? Digital Loss Plan Modification? DS1 Echo Cancellation? DS1 MSP? Enhanced EC500? Enhanced Conferencing?
31

FEAT_MMCH FEAT_MMIP_SIP FEAT_MULTILOC FEAT_NETADMIN FEAT_PART FEAT_PASTE FEAT_PHANTOM FEAT_PNS FEAT_POMSG FEAT_PRETH FEAT_PRTVEC FEAT_PSA FEAT_QBCALL FEAT_QBSS FEAT_QCAS FEAT_QSSR FEAT_QVALU FEAT_QVMAIL FEAT_R95_CAP FEAT_REM_OFF FEAT_RFG FEAT_SCARS FEAT_SCCPD FEAT_SELLIS FEAT_SL_BCMS FEAT_SO FEAT_SOFAC FEAT_STTRKMSP

Multimedia Call Handling (Basic)? Multimedia IP SIP Trunking? Multiple Locations? System Management Data Transfer? ARS/AAR Partitioning? PASTE (Display PBX Data on Phone)? Phantom Calls? Port Network Support? Posted Messages? Processor Ethernet? Vectoring (Prompting)? Personal Station Access (PSA)? Basic Call Setup? Basic Supplementary Services? Centralized Attendant? Supplementary Services with Rerouting? Value-Added (VALU)? Transfer into QSIG Voice Mail? R9.5 Capabilities? Remote Office? Request Feature Group ARS/AAR Dialing without FAC? Switch Classified Call/Predictive Dialing [ASAI] Selective Listening BCMS/VuStats Service Level? Service Observing (Basic)? Service Observing (Remote/By FAC)? Station and Trunk MSP?

Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

FEAT_EMMCH FEAT_EMR FEAT_ENG FEAT_ETN FEAT_EXTALM FEAT_FB FEAT_FEA FEAT_FMCH FEAT_FP_ISDN FEAT_GCC FEAT_HM FEAT_HOL FEAT_I2C FEAT_ICLID FEAT_IP_ATTN FEAT_IP_STNS FEAT_IP_TRNKS FEAT_ISDN_PRI

Multimedia Call Handling (Enhanced)? Emergency Access to Attendant? Event Notification Group? Private Networking? External Device Alarm Admin? Flexible Billing? Forced Entry of Account Codes? Multiple Call Handling (Forced)? ISDN Feature Plus? Global Call Classification? Hospitality (Basic)? Vectoring (Holidays)? Secondary Data Module? Analog Trunk Incoming Call ID? IP Attendent Consoles? IP Stations? IP Trunks? ISDN-PRI?

FEAT_SVG FEAT_SYCCMSP FEAT_TACW FEAT_TOD FEAT_TPN FEAT_TTI FEAT_UAENH FEAT_UDP FEAT_V3H_ENH FEAT_V4VUSTATS FEAT_VAL FEAT_VIRT_EXT FEAT_VUSTATS FEAT_WIDE FEAT_WL FEAT_XCOV_ADMIN FEAT_XMOB

Set Value Group Processor and System MSP? Timed ACW? Time of Day Routing? Tenant Partitioning? Terminal Trans. Init. (TTI)? Usage Allocation Enhancements? Uniform Dialing Plan? Hospitality (G3V3 Enhancements)? VuStats (G3V4 Enhanced)? TN2501 VAL Maximum Capacity? Station as Virtual Extension? VuStats? Wideband Switching? Wireless? Extended Cvg/Fwd Admin? X-Station Mobility

Features always OFF --- MBT does not support any of these features --(cannot be turned ON)
Feature Keyword FEAT_AGTALLOC FEAT_ASG FEAT_ATMPNC FEAT_ATMTRK FEAT_CAS FEAT_CHGCOR FEAT_CVA2 Feature Display Name Business Advocate? Access Security Gateway (ASG)? Async. Transfer Mode (ATM) PNC? Async. Transfer Mode (ATM) Trunking? CAS Branch? Change COR by FAC? Dynamic Advocate? Feature Keyword FEAT_ESS_SRV FEAT_INC_ADJ_RTE FEAT_LSP FEAT_MAINCAS FEAT_MCODE FEAT_MLPP FEAT_PNC_DUPE Feature Display Name Enterprise Survivable Server? Increased Adjunct Route Capacity? Local Survivable Processor? CAS Main? Mode Codes? Multiple Level Precedence & Preemption? PNC Duplication?

32 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

FEAT_ESS

ESS Administration?

FEAT_PNMAX

Five Port Networks Max Per MCC?

Features only available with the MBT Call Center offers (no changes to these features can be made)
Feature Keyword FEAT_3EVEC FEAT_ANIVEC FEAT_ASD FEAT_BCMS FEAT_BSR FEAT_CINFO FEAT_CWC FEAT_EASPHD FEAT_LI FEAT_LOA FEAT_LTRMT Feature Display Name Vectoring (3.0 Enhanced)? Vectoring (ANI/IIDigits Routing)? Expert Agent Selection (EAS)? BCMS (Basic)? Vectoring (Best Service Routing)? Vectoring (CINFO) Call Work Codes? EAS-PHD? Lookahead Interflow (LAI)? Least Occupied Agent? BSR Local Treatment for IP & ISDN? Feature Keyword FEAT_NCR_ISDN FEAT_PROPRIETARY* FEAT_REASON FEAT_SLM FEAT_SOVDN FEAT_V4ENHVEC FEAT_V4VEC FEAT_VAR FEAT_VDN_RTN FEAT_VOA FEAT_VRU Feature Display Name ISDN/SIP Network Call Redirection? Proprietary? Reason Codes? Service Level Maximizer? Service Observing (VDNs)? Vectoring (G3V4 Advanced Routing)? Vectoring (G3V4 Enhanced)? Vectoring (Variables)? VDN Return Destination? VDN of Origin Announcement? DTMF Feedback Signals For VRU?

Features Available only with MBT Enterprise Edition Offers

Feature Keyword FEAT_MNTL_LOC Feature Display Name Multinational Locations? *Separate purchase required for use

Table A2: Capacity License Features

These features determine the capacity limits of the MBT offer. There are only two MBT license features in the WebLM license file, as shown below. The CM Customer Options Screen column is what to CM administrator will see, many of which are set equal to the number of CM stations purchased. There are two features separately purchased which will interoperate with MBT and are noted below. Feature License Keyword CM Customer Options Screen

Feature Name

WebLM License

33 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

VALUE_ADVOCATE

Logged-In Advocate Agents (CC) Maximum Administered Ad-hoc Video Conferencing Ports Maximum Number of DS1 Boards with Echo Cancellation Maximum Number of Expanded Meet-me Ports Maximum Concurrently Registered IP eCons Maximum Concurrently Registered IP Stations Maximum Administered IP Trunks Logged-in IP Softphone Agents (CC) Logged-In ACD Agents (CC) Maximum G700 VAL Sources Maximum Off-PBX Telephones - EC500 Maximum off-PBX Telephones - OPS (EC500) Maximum off-PBX Telephones - PBFMC (EC500) Maximum off-PBX Telephones - PVFMC (EC500) Software Package (not a capacity feature, but included here for reference) Maximum Ports Maximum Concurrently Registered Remote Office Stations Maximum Administered Remote Office Trunks Maximum Administered SIP Trunks Logged-in SIP EAS Agents (CC) Maximum Stations

none

0 (unchangeable): Not offered with MBT. Choose LOA and SLM instead. 12000 (unchangeable) 522 (unchangeable) 300 (unchangeable) Number of CM stations purchased 18000 (unchangeable) 12000 (unchangeable) Number of CM stations purchased Number of CM stations purchased 250 (unchangeable) Number of CM stations purchased Number of CM stations purchased Number of CM stations purchased Number of CM stations purchased

VALUE_AVC_PORTS VALUE_DS1_ECHO VALUE_EMMC_PORTS* VALUE_IP_ATTD_CON VALUE_IP_STA VALUE_IP_TRK VALUE_IPA VALUE_LOGGIN* VALUE_MGA_SRC VALUE_OPT_EC500* VALUE_OPT_OPS* VALUE_OPT_PBFMC* VALUE_OPT_PVFMC*

none none Number separately purchased none none none none Number separately purchased none Number separately purchased Number separately purchased Number separately purchased Number separately purchased 1 = CM SE w/o Call Center 2 = CM SE w/ Call Center 3 = CM EE w/o Call Center 4 = CM EE w/ Call Center none none none none Number separately purchased Number of CM stations purchased (2400 max)

VALUE_PCKG

Standard Edition or Enterprise Edition 48000 (unchangeable) 18000 (unchangeable) 12000 (unchangeable) 7000 (unchangeable) Number of CM stations purchased Number of CM stations purchased

VALUE_PORT VALUE_RO_STN VALUE_RO_TRK VALUE_SIP_TRK VALUE_SIPEAS* VALUE_STA

34 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.

VALUE_UNAUTH_EPT VALUE_VAL VALUE_VC_H323 VALUE_VC_IPSP* VALUE_XMOB_NUM

Max Concur Registered Unauthenticated H.323 Stations Maximum TN2501 VAL Boards Maximum Video Capable H.323 Stations Maximum Video Capable IP Softphones Maximum XMOBILE Stations (EC500)

none none none Number separately purchased none

100 (unchangeable) 128 (unchangeable) Number of CM stations purchased 100 (unchangeable) Number of CM stations purchased

*Separate purchase required for use

Table A3: IP Registration License Features

These features define the type and quantity of IP registrations CM will allow for the specific IP endpoint type. This table shows the maximum allowed for each type, however, in most cases separate purchase is required to use the functionality. Feature Keyword AgentSC* IP_Agent* IP_API_A* IP_eCons IP_NonAgt* IP_Phone IP_ROMax IP_Soft* IP_Supv* oneX_Comm IP Softphone IP Telephone Feature Name IP Agent with shared control IP Agent MBT without Call Center not available not available 2400 2400 not available 2400 2400 2400 not available 2400 MBT with Call Center Number of stations purchased Number of stations purchased 2400 414 Number of stations purchased 2400 2400 2400 300 2400

*Separate purchase required for use.

2009 Avaya Inc. All rights reserved. All trademarks identified by the or TM are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners.

35 Avaya Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.