avaya aura mbt 521 product definition

Avaya Aura™ for Midsize Enterprises Product Definition

Global Sales and BusinessPartner Channels

Date issued: January 11, 2010

ContentsSummary............................................................................................................................3Avaya Aura for Midsize Enterprise Solution Description...................................................3Avaya Aura System Platform 1.1 Technology...................................................................5Packaging and Pricing Structure.......................................................................................8How to Order Midsize Business Template.......................................................................10MBT Component Details and Capacities.........................................................................16Upgrades and Migrations.................................................................................................21Installation........................................................................................................................22Licensing..........................................................................................................................23Serviceability....................................................................................................................25Software Support and Hardware Maintenance................................................................26

Software Support.........................................................................................................26Hardware Maintenance................................................................................................26Extended Manufacturers Software Support Policy.......................................................26

Training and Documentation............................................................................................27Additional Resources.......................................................................................................27

Product Management Contacts....................................................................................27Appendix A: FAQ on EMSSP..........................................................................................29Appendix B: License Feature Reference.........................................................................31

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

2

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.

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


3

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.

https://portal.avaya.com/ptlWeb/gs/products

https://portal.avaya.com/ptlWeb/gs/products/P0540/AllCollateral

Aura applications all 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 Manager’s robust architecture and Local Survivable Processor (LSP) support, is provided by System Platform’s 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 Avaya’s DevConnect partner CRI, Inc.

For more information, go to http://www.crinj.com/is.php and look for “Integrated Server - UC”.


4

http://www.crinj.com/is.php

OPTIONAL: Avaya Contact Center Express – single server configurationContact 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 configurationA 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 Avaya’s 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 Avaya’s 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 Avaya’s 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 Coordinated software upgrades


5

http://www.crinj.com/is.php

https://enterpriseportal.avaya.com/ptlWeb/gs/products/P0042

mailto:[email protected]

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 Avaya’s customers expect, System Platform is being delivered solely via an “appliance” model, which includes an Avaya Server, System Platform, and the Avaya software applications.

Intelligent Access and Enterprise Application Integration

Intelligent Access and Enterprise Application Integration

Collaboration & InteractionSolutions

Collaboration & InteractionSolutions

Communication InfrastructureCommunication Infrastructure

Perfo

rma

nce A

na

lytics

Perfo

rma

nce A

na

lytics

En

d to

En

d M

an

ag

emen

t S

ecurity a

nd

Service

ab

ilityE

nd

to E

nd

Ma

na

gem

ent

Secu

rity an

d S

erviceab

ility

Mu

ltiven

do

r Integ

ratio

nM

ultive

nd

or In

tegra

tion

Avaya Aura™ System PlatformAvaya Aura™ System Platform

Core Communication Services

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 Avaya’s 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:.


HDD RAM NICHardware

Linux

PlatformConsole

Real-time Virtualization – Hypervisor

Linux

CM andCMM

CPU

SES AES MediaServices

Linux Linux Linux

Utilities

Linux

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

System Platform

6

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 Intel’s 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 Processor (Intel XeonQuad Core Nehalem)

# of CPUs

Dynamic RAM

Hard Disk Drive

Midsize Enterprise solution

1U 5520 2.26 GHz 1 12 GB 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

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 Avaya’s 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

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

StandardEdition

EnterpriseEdition

Avaya Aura™ Communication Manager Standard 5.2.1

Enterprise 5.2.1

Avaya Aura™ SIP Enablement Services

Avaya Aura™ Communication Manager Messaging (Built-in, can also add Modular Messaging)

500 users included

500 users included

Avaya Aura™ Application Enablement Services – CTI

TSAPI Basic

included+ $ licenses

TSAPI Basic

included+ $ licenses

Avaya Aura™ Application Enablement Services – UC

Avaya Aura™ Media Services (new)

+$10,000Only applicable on System Platform

+$10,000

Only applicable on System Platform

Avaya Aura™ System Platform (new)

(Available when configured. Not available separately)

Avaya Aura™ System Platform High Availability option(Available when configured, Not available separately)

+ $2,500 license

+ $2,500 license

Avaya Aura™ Presence Services

Avaya Integrated Management (as appropriate for Edition*)

Avaya one-X® – UC All InclusiveAvaya 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 +$ licenses

+$ licenses

Modular Messaging – single server configurationAvailable with the new System Platform enabled single server configuration

+$ licenses

+$ licenses

- included - available for fee

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

midsize business template

(MBT)


9

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 MPGGlobal List

Price

700472376 AURA FOR MIDSIZE BUSINESS 5.2 DVD A1 $100.00 700475882 AURA SYSTEM PLATFORM 1.1 DVD A1 $100.00


10

Both DVDs are required for a complete install.

Supported Server and Options


Price

228992 S8800 SERVER MBT IG $8,500.00 226432 AURA SYS PLTFRM R5.2 HIGH AVAIL OPT DU $2,500.00226431 AURA MEDIA SERVICES 5.2 SFTW LIC DU $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:


Price

700454135 TWO 1GB DIMM FOR S8510 A1 $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 customer’s needs.


Price

New Standard Edition without Call Center Elite Agents(To be used when not needing Elite agent functionality)

229008 AURA MBT SE R5 1-100 NEW W/O CC LIC DU $240.00 229009 AURA MBT SE R5 101-1000NEW W/OCCLIC DU $210.00 229010 AURA MBT SE R5 1001+ NEW W/O CC LIC DU $205.00

New Enterprise Edition without Call Center Elite Agents(To be used when not needing Elite agent functionality)

229014 AURA MBT EE R5 1-100 NEW W/O CC LIC DU $320.00 229015 AURA MBT EE R5 101-1000NEW W/OCCLIC DU $290.00 229016 AURA MBT EE R5 1001+ NEW W/O CC LIC DU $285.00

New Standard Edition with Call Center Elite Agents(Additional CC codes need to be ordered at the desired quantities)


11

229005 AURA MBT SE R5 1-100 NEW W/CC LIC DU $240.00 229006 AURA MBT SE R5 101-1000 NEWW/CC LIC DU $210.00 229007 AURA MBT SE R5 1001+ NEW W/CC LIC DU $205.00

New Enterprise Edition with Call Center Elite Agents(Additional CC codes need to be ordered at the desired quantities)

229011 AURA MBT EE R5 1-100 NEW W/CC LIC DU $320.00 229012 AURA MBT EE R5 101-1000 NEWW/CC LIC DU $290.00 229013 AURA MBT EE R5 1001+ NEW W/CC LIC DU $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 customer’s 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.


Price

Upgrade Standard Edition without Call Center Elite Agents(To be used when not needing Elite agent functionality)

229020 AURA MBT SE R5 1-100 UPG W/O CC LIC DU $36.00 229021 AURA MBT SE R5 101-1000UPG W/OCCLIC DU $31.00 229022 AURA MBT SE R5 1001+ UPG W/O CC LIC DU $30.00

Upgrade Enterprise Edition without Call Center Elite Agents(To be used when not needing Elite agent functionality)

229026 AURA MBT EE R5 1-100 UPG W/O CC LIC DU $48.00 229027 AURA MBT EE R5 101-1000UPG W/OCCLIC DU $43.00 229028 AURA MBT EE R5 1001+ UPG W/O CC LIC DU $42.00

Upgrade Standard Edition with Call Center Elite Agents(Additional CC codes need to be ordered at the desired quantities)

229017 AURA MBT SE R5 1-100 UPG W/CC LIC DU $36.00 229018 AURA MBT SE R5 101-1000 UPGW/CC LIC DU $31.00 229019 AURA MBT SE R5 1001+ UPG W/CC LIC DU $30.00

Upgrade Enterprise Edition with Call Center Elite Agents(Additional CC codes need to be ordered at the desired quantities)

229023 AURA MBT EE R5 1-100 UPG W/CC LIC DU $48.00 229024 AURA MBT EE R5 101-1000 UPGW/CC LIC DU $43.00 229025 AURA MBT EE R5 1001+ UPG W/CC LIC DU $42.00


12

Migration License Purchase

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 customer’s 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.


Price

Migrate Standard Edition without Call Center Elite Agents(To be used when not needing Elite agent functionality)

229032 AURA MBT SE R5 1-100 MIG W/O CC LIC DU $0 229033 AURA MBT SE R5 101-1000MIG W/OCCLIC DU $0 229034 AURA MBT SE R5 1001+ MIG W/O CC LIC DU $0

Migrate Enterprise Edition without Call Center Elite Agents(To be used when not needing Elite agent functionality)

229038 AURA MBT EE R5 1-100 MIG W/O CC LIC DU $0 229039 AURA MBT EE R5 101-1000MIG W/OCCLIC DU $0 229040 AURA MBT EE R5 1001+ MIG W/O CC LIC DU $0

Migrate Standard Edition with Call Center Elite Agents(Additional CC codes need to be ordered at the desired quantities)

229029 AURA MBT SE R5 1-100 MIG W/CC LIC DU $0 229030 AURA MBT SE R5 101-1000 MIGW/CC LIC DU $0 229031 AURA MBT SE R5 1001+ MIG W/CC LIC DU $0

Migrate Enterprise Edition with Call Center Elite Agents(Additional CC codes need to be ordered at the desired quantities)

229035 AURA MBT EE R5 1-100 MIG W/CC LIC DU $0 229036 AURA MBT EE R5 101-1000 MIGW/CC LIC DU $0 229037 AURA MBT EE R5 1001+ MIG W/CC LIC DU $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.


Price

New226818 AURA MBT ANALOG NEW LIC DU $40.00

Uplift to Universal Station on Standard Edition


13

229041 AURA MBT ANA-SE 1-100 UPLIFT LIC DU $200.00 229042 AURA MBT ANA-SE 101-1000 UPLIFT LIC DU $170.00 229043 AURA MBT ANA-SE 1001+ UPLIFT LIC DU $165.00

Uplift to Universal Station on Enterprise Edition229044 AURA MBT ANA-EE 1-100 UPLIFT LIC DU $280.00 229045 AURA MBT ANA-EE 101-1000 UPLIFT LIC DU $250.00 229046 AURA MBT ANA-EE 1001+ UPLIFT LIC DU $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.


Price

Uplift Standard Edition without Call Center Elite AgentsTo Enterprise Edition without Call Center Elite Agents

Order BOTH codes229370 AURA MBT SE R5 W/O CC TO EE W/O CC LIC DU $0 226881 AURA MBT SE R5 TO EE UPLIFT SW LIC DU $115

Uplift Standard Edition with Call Center Elite AgentsTo Enterprise Edition with Call Center Elite Agents

Order BOTH codes229371 AURA MBT SE R5 W/CC TO EE W/CC LIC DU $0 226881 AURA MBT SE R5 TO EE UPLIFT SW LIC DU $115

Uplift Standard Edition without Call Center Elite AgentsTo Standard Edition with Call Center Elite Agents

229372 AURA MBT SE R5 W/O CC TO SE W/CC LIC DU $0 Uplift Enterprise Edition without Call Center Elite Agents

To Enterprise Edition with Call Center Elite Agents229373 AURA MBT EE R5 W/O CC TO EE W/CC LIC DU $0

Uplift Standard Edition without Call Center Elite AgentsTo Enterprise Edition with Call Center Elite Agents

Order BOTH codes229374 AURA MBT SE R5 W/O CC TO EE W/CC LIC DU $0226881 AURA MBT SE R5 TO EE UPLIFT SW LIC DU $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.


Price

226667 CM MSGING R5.2 MBT NEW/ADD LIC 501+ DU $35.00

UCE All Inclusive


14

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:


Price

New or Add229200 UCE R5.2 STD/W MBT NEW IE $60.00 229201 UCE R5.2 STD/W MBT ADD IE $60.00

Upgrade229341 UCE R5.2 STD/W MBT UPG IE $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.


Price

New and Add licenses229140 AURA MBT CC R5 NEW/ADD ELITE 1-100 DU $680.00 229141 AURA MBT CC R5 NEW/ADD ELITE 101-250 DU $525.00 229142 AURA MBT CC R5 NEW/ADD ELITE 251+ DU $270.00

Single-release upgrades229143 AURA MBT CC R5 ELITE SNGL UPG 1-100 DU $170.00 229144 AURA MBT CCR5 ELITE SNGL UPG 101-250 DU $131.00 229145 AURA MBT CC R5 ELITE SNGL UPG 251+ DU $68.00

Multi-release upgrades229146 AURA MBT CC R5 ELITE MULTI UPG 1-100 DU $238.00 229147 AURA MBT CCR5 ELITE MULTIUPG 101-250 DU $184.00 229148 AURA MBT CC R5 ELITE MULTI UPG 251+ DU $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


15

https://enterpriseportal.avaya.com/ptlWeb/gs/products/P0009/JobAidsTools/003961119

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:

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


16

http://pdocap201.dr.avaya.com:9001/knova/DocContent?DocID=100069074&origFileName=03-300511_5%202%201.pdf






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

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



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 G650 + TN2302BP x 4 Media Services

Codecs G.711, G.723.1, G.729(B) G.711, G.729A(B)

G.711 channels 4 x 64 (10-60 msec) 4 x 64 (10-60 msec)

G.729 channels 4 x 32 4 x 22 channel type IP and legacy TDM IP only

FAX pass-through, relay, T.38

relay N/A

modem pass-through, V.32 relay N/A

TTY pass-through, relay N/A

64kbps unrestricted data clear channel N/A

echo cancellation 32 ms full tail N/A


18

6-party conferencing Yes Yes

media encryption AEA, AES (reduced

channels) No

fw download? Yes S/W Upgradeable

RFC 2833 DTMF Yes Yes

RTCP reporting/VMM Yes No

VLAN tagging Yes No

RSVP Yes No

802.1p/Q Yes No

Announcements/MOH optional TN2501 VAL Yes

Hairpinned channels Yes No

Alarms CM CM

Call progress tone

generation 25 countries (a la TN2312) 25 countries

IP media signaling Processor Ethernet and/or

CLAN Processor Ethernet

Network regions 1-4 1-4

Call classification support Yes No

ESS compatibility Yes N/A

MF signaling Yes N/A

# supported LANs 4 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


19

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.

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.


20

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.

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 reduced-cost 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.


21

In a nutshell, the installation process for a typical solution or template using System Platform:

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.


1Select an Avaya

ServerInstall the System

Platform

SP SP

Select and Install Application Template

2 3

22

On-site or RemotelyInstallabl

e

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.

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:


23

https://plds.avaya.com/

http://support.avaya.com/css/P8/documents/100068119

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) Designer configures MBT design using ASD2) BP or account team converts quote to SAP order3) After the SAP order clears credit-check, it will flow automatically to PLDS4) 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 PLDS6) Customer (or BP or Avaya) uses PLDS to activate purchased licenses and download a license

file7) 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:

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 customer’s 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, Avaya’s 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.


24


http://portal.avaya.com/ptlWeb/licensinganddownloads

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 customer’s 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

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 MaintenanceFor 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 PolicyAvaya Aura MBT is covered by Avaya’s 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 Avaya’s 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.


25

http://enterpriseportal.avaya.com/


https://enterpriseportal.avaya.com/ptlWeb/gs/services/SV0507

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 Contact Email

Avaya Aura

Avaya Aura Communication Manager, Midsize Business Template

Christopher E. Johnson [email protected]

Avaya Aura Beth Smith [email protected]

Avaya Aura Session Manager

Steve Durney [email protected]

Avaya Aura System Manager 1.0

Eran Shapiro [email protected]

Avaya Aura System Manager 2.0

Frank Chang [email protected]

Avaya Aura Communication Manager Branch

Ron Kidd (Global) Michael Zhu (APAC)Andres Ramirez (CALA)Gavin Stewart (EMEA)

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

Avaya Aura SIP Enablement Services

Ron Kidd [email protected]

Avaya Aura Communication Manager Messaging

Paola BenassiMike Wasserburger

[email protected]@avaya.com

Avaya Aura Application Enablement Services – UC (DMCC, Unified Desktop, SMS, servers)

Tom Rowland [email protected]

Avaya Aura Application Enablement Services – CC (CVLAN, DLG, TSAPI, T)

Cathy Smyth [email protected]

Avaya Aura Presence Services

Ira Kucheck [email protected]


26
















http://support.avaya.com/css/Products/P0586

Avaya one-X – UC All Inclusive

Daniel Cardaropoli [email protected]

Avaya Integrated Management

Eran Shapiro [email protected]

Product Contact Email

Related Products & Solutions

Branch Media Gateways Yossi Asyag [email protected]

Call Center Bill Jolicoeur [email protected]

Contact Center Express Girish Vasvani [email protected]

Customer Service Editions Stefan Rueck [email protected]

Solutions for Midsize Enterprises

Bruce Mazza [email protected]

Intelligent Customer Routing

Laura Bassett [email protected]

Meeting Exchange Matt O’Donnell [email protected]

one-X Agent Michael Harwell [email protected]

one-X Mobile, one-X Portal, EC500

Julie Thiesen [email protected]

one-X Communicator, Softphone clients

Phil Klotzkin [email protected]

Servers Cecilia Perez-Benitoa [email protected]

Software Support and Hardware Maintenance

Extended Manufacturers Software Support Policy

Jan Leistikow [email protected]


27











mailto:[email protected]?subject=Contact%20Center%20&%20IP%20Agent




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 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

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 purchased2) VALUE_CM_OFFER: The particular Avaya Edition purchased, as follows

a. 1: Standard Edition, without Call Center Elite agentsb. 2: Standard Edition, with Call Center Elite Agentsc. 3: Enterprise Edition, without Call center Elite agentsd. 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 KeywordFeature Display

NameFeature Keyword

Feature Display Name

FEAT_ACAuthorization

Codes?FEAT_MCHAND

Multiple Call Handling (On

Request)?

FEAT_ACCGAdjunct Call

Control?FEAT_MCT Malicious Call Trace?

FEAT_ACD ACD? FEAT_MEMedia Encryption

Over IP?


30

FEAT_ADEAbbreviated Dialing

Enhanced List?FEAT_MFS

Multifrequency Signaling?

FEAT_ADJLKComputer

Telephony Adjunct Links?

FEAT_MMCHMultimedia Call

Handling (Basic)?

FEAT_ADNA/D Grp/Sys List

Dialing Start at 01?FEAT_MMIP_SIP

Multimedia IP SIP Trunking?

FEAT_AMWAudible Message

Waiting?FEAT_MULTILOC Multiple Locations?

FEAT_ANSAnswer

Supervision by Call Classifier?

FEAT_NETADMINSystem Management

Data Transfer?

FEAT_ANSMDAnswer Machine

DetectFEAT_PART

ARS/AAR Partitioning?

FEAT_ARG Adjunct Routing? FEAT_PASTEPASTE (Display PBX

Data on Phone)?FEAT_ARS ARS? FEAT_PHANTOM Phantom Calls?

FEAT_ASAI*ASAI Link Core

Capabilities?FEAT_PNS

Port Network Support?

FEAT_ASAIPLUS*ASAI Link Plus Capabilities?

FEAT_POMSG Posted Messages?

FEAT_ATDVECAttendant Vectoring?

FEAT_PRETH Processor Ethernet?

FEAT_ATMS ATMS? FEAT_PRTVECVectoring

(Prompting)?

FEAT_BRITRK ISDN-BRI Trunks FEAT_PSAPersonal Station Access (PSA)?

FEAT_BSCVEC Vectoring (Basic)? FEAT_QBCALL Basic Call Setup?

FEAT_CFWDRestrict Call

Forward Off Net?FEAT_QBSS

Basic Supplementary Services?

FEAT_COV_OFFNETCvg Of Calls

Redirected Off-net?FEAT_QCAS

Centralized Attendant?

FEAT_CTI CTI Stations? FEAT_QSSRSupplementary Services with Rerouting?

FEAT_CVM_MCMode Code for

Centralized Voice Mail?

FEAT_QVALUValue-Added

(VALU)?

FEAT_DADMINEnable dadmin

login?FEAT_QVMAIL

Transfer into QSIG Voice Mail?

FEAT_DCG Domain Control? FEAT_R95_CAP R9.5 Capabilities?FEAT_DCS DCS (Basic)? FEAT_REM_OFF Remote Office?

FEAT_DCSCCDCS Call

Coverage?FEAT_RFG

Request Feature Group

FEAT_DCSINWKInterworking with

DCS?FEAT_SCARS

ARS/AAR Dialing without FAC?

FEAT_DCSWRRDCS with

Rerouting?FEAT_SCCPD

Switch Classified Call/Predictive

Dialing

FEAT_DIG_LOSSDigital Loss Plan

Modification?FEAT_SELLIS

[ASAI] Selective Listening

FEAT_DS1_ECHODS1 Echo

Cancellation?FEAT_SL_BCMS

BCMS/VuStats Service Level?

FEAT_DS1MSP DS1 MSP? FEAT_SOService Observing

(Basic)?


31

FEAT_EC500Enhanced EC500?

FEAT_SOFACService Observing (Remote/By FAC)?

FEAT_EHCNFEnhanced

Conferencing?FEAT_STTRKMSP

Station and Trunk MSP?

FEAT_EMMCHMultimedia Call

Handling (Enhanced)?

FEAT_SVG Set Value Group

FEAT_EMREmergency Access

to Attendant?FEAT_SYCCMSP

Processor and System MSP?

FEAT_ENGEvent Notification

Group?FEAT_TACW Timed ACW?

FEAT_ETNPrivate

Networking?FEAT_TOD

Time of Day Routing?

FEAT_EXTALMExternal Device Alarm Admin?

FEAT_TPN Tenant Partitioning?

FEAT_FB Flexible Billing? FEAT_TTITerminal Trans. Init.

(TTI)?

FEAT_FEAForced Entry of Account Codes?

FEAT_UAENHUsage Allocation Enhancements?

FEAT_FMCHMultiple Call

Handling (Forced)?FEAT_UDP

Uniform Dialing Plan?

FEAT_FP_ISDNISDN Feature

Plus?FEAT_V3H_ENH

Hospitality (G3V3 Enhancements)?

FEAT_GCCGlobal Call

Classification?FEAT_V4VUSTATS

VuStats (G3V4 Enhanced)?

FEAT_HM Hospitality (Basic)? FEAT_VALTN2501 VAL

Maximum Capacity?

FEAT_HOLVectoring

(Holidays)?FEAT_VIRT_EXT

Station as Virtual Extension?

FEAT_I2CSecondary Data

Module?FEAT_VUSTATS VuStats?

FEAT_ICLIDAnalog Trunk

Incoming Call ID?FEAT_WIDE

Wideband Switching?

FEAT_IP_ATTNIP Attendent Consoles?

FEAT_WL Wireless?

FEAT_IP_STNS IP Stations? FEAT_XCOV_ADMINExtended Cvg/Fwd

Admin?FEAT_IP_TRNKS IP Trunks? FEAT_XMOB X-Station MobilityFEAT_ISDN_PRI ISDN-PRI?

Features always OFF--- MBT does not support any of these features ---

(cannot be turned ON)


NameFeature Keyword


FEAT_AGTALLOCBusiness

Advocate?FEAT_ESS_SRV

Enterprise Survivable Server?

FEAT_ASGAccess Security Gateway (ASG)?

FEAT_INC_ADJ_RTEIncreased Adjunct Route Capacity?

FEAT_ATMPNCAsync. Transfer

Mode (ATM) PNC?FEAT_LSP

Local Survivable Processor?

FEAT_ATMTRKAsync. Transfer

Mode (ATM) Trunking?

FEAT_MAINCAS CAS Main?

FEAT_CAS CAS Branch? FEAT_MCODE Mode Codes?


32

FEAT_CHGCORChange COR by

FAC? FEAT_MLPPMultiple Level Precedence & Preemption?

FEAT_CVA2 Dynamic Advocate? FEAT_PNC_DUPE PNC Duplication?

FEAT_ESSESS

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)


NameFeature Keyword


FEAT_3EVECVectoring (3.0 Enhanced)?

FEAT_NCR_ISDNISDN/SIP Network Call Redirection?

FEAT_ANIVECVectoring (ANI/II-Digits Routing)?

FEAT_PROPRIETARY* Proprietary?

FEAT_ASDExpert Agent

Selection (EAS)?FEAT_REASON Reason Codes?

FEAT_BCMS BCMS (Basic)? FEAT_SLMService Level Maximizer?

FEAT_BSRVectoring (Best

Service Routing)?FEAT_SOVDN

Service Observing (VDNs)?

FEAT_CINFO Vectoring (CINFO) FEAT_V4ENHVECVectoring (G3V4

Advanced Routing)?

FEAT_CWC Call Work Codes? FEAT_V4VECVectoring (G3V4

Enhanced)?

FEAT_EASPHD EAS-PHD? FEAT_VARVectoring

(Variables)?

FEAT_LILookahead Interflow

(LAI)?FEAT_VDN_RTN

VDN Return Destination?

FEAT_LOALeast Occupied

Agent?FEAT_VOA

VDN of Origin Announcement?

FEAT_LTRMTBSR Local

Treatment for IP & ISDN?

FEAT_VRUDTMF Feedback Signals For VRU?

Features Available only with MBT Enterprise Edition Offers


Name

FEAT_MNTL_LOCMultinational 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.


33

Feature License Keyword

Feature Name WebLM LicenseCM Customer

Options Screen

VALUE_ADVOCATELogged-In Advocate

Agents (CC)none

0 (unchangeable): Not offered with MBT.

Choose LOA and SLM instead.

VALUE_AVC_PORTSMaximum Administered

Ad-hoc Video Conferencing Ports

none12000

(unchangeable)

VALUE_DS1_ECHOMaximum Number of

DS1 Boards with Echo Cancellation

none 522 (unchangeable)

VALUE_EMMC_PORTS*Maximum Number of Expanded Meet-me

Ports

Number separately purchased

300 (unchangeable)

VALUE_IP_ATTD_CONMaximum Concurrently Registered IP eCons

noneNumber of CM

stations purchased

VALUE_IP_STAMaximum Concurrently Registered IP Stations

none18000

(unchangeable)

VALUE_IP_TRKMaximum Administered

IP Trunksnone

12000 (unchangeable)

VALUE_IPALogged-in IP Softphone

Agents (CC)none

Number of CM stations purchased

VALUE_LOGGIN*Logged-In ACD Agents

(CC)Number separately

purchasedNumber of CM

stations purchased

VALUE_MGA_SRCMaximum G700 VAL

Sourcesnone 250 (unchangeable)

VALUE_OPT_EC500*Maximum Off-PBX

Telephones - EC500Number separately


stations purchased

VALUE_OPT_OPS*Maximum off-PBX Telephones - OPS

(EC500)



VALUE_OPT_PBFMC*Maximum off-PBX

Telephones - PBFMC (EC500)



VALUE_OPT_PVFMC*Maximum off-PBX

Telephones - PVFMC (EC500)



VALUE_PCKG

Software Package (not a capacity feature, but

included here for reference)

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

Standard Edition or Enterprise Edition

VALUE_PORT Maximum Ports none48000

(unchangeable)

VALUE_RO_STNMaximum Concurrently

Registered Remote Office Stations

none18000

(unchangeable)

VALUE_RO_TRKMaximum Administered Remote Office Trunks

none12000

(unchangeable)

VALUE_SIP_TRKMaximum Administered

SIP Trunksnone 7000 (unchangeable)

VALUE_SIPEAS*Logged-in SIP EAS

Agents (CC)Number separately


stations purchased


34

VALUE_STA Maximum StationsNumber of CM

stations purchased (2400 max)


VALUE_UNAUTH_EPTMax Concur Registered Unauthenticated H.323

Stationsnone 100 (unchangeable)

VALUE_VALMaximum TN2501 VAL

Boardsnone 128 (unchangeable)

VALUE_VC_H323Maximum Video

Capable H.323 Stationsnone


VALUE_VC_IPSP*Maximum Video

Capable IP SoftphonesNumber separately

purchased100 (unchangeable)

VALUE_XMOB_NUMMaximum XMOBILE

Stations (EC500)none


*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

Feature Name

MBT without

Call Center

MBT with Call

Center

AgentSC*IP Agent

with shared control

not available

Number of stations

purchased

IP_Agent* IP Agentnot

available

Number of stations

purchasedIP_API_A* 2400 2400IP_eCons 2400 414

IP_NonAgt*not

available

Number of stations

purchased

IP_PhoneIP

Telephone2400 2400

IP_ROMax 2400 2400

IP_Soft*IP

Softphone2400 2400

IP_Supv*not

available300

oneX_Comm 2400 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 aura mbt 521 product definition

Documents

multimedia call handling

call detail recording

cc lic du

graphical user interface

cc lic du

proven voip technology

multiple call handling

ibm uc integration