AvayaAura6 1ProductDefDec2011 rev1 (2)

Solution Definition

Avaya Aura

Release “6.1”

Communication Manager (6.0.1)

Session Manager (6.1)

October 3, 2011

COMPAS ID 142680

ABSTRACT

This document provides a high-level description of the key components of Avaya
Aura®: Avaya Aura® Communication Manager 6.0.1 and Avaya Aura® Session
Manager 6.1 as well as the surrounding solution, and the supporting sales offer.

This document is for internal and business partner use only and is targeted at Sales and
Sales Support organizations. All pricing contained within, while accurate at the time of
publication, should be considered as unofficial; associates and business partners are
directed to verify the accuracy of all prices cited.

NOTE: This Product Definition is a US version and some of the products listed in this
document may not be available or applicable to your regions. Please contact your
regional Product Management team to obtain the version of this document that is
applicable to your region.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 2 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

TABLE OF CONTENTS

AVAYA AURA® ................................................................................................................... 4

SOLUTION DESCRIPTION ............................................................................................... 6

2.1.

ERVERS

VERVIEW

............................................................................................. 6

2.2.

ESSION

ANAGER

VERVIEW

...................................................................................... 7

2.3.

YSTEM

ANAGER

ANAGEMENT

................................................................................. 7

2.4.

ESSION

ANAGER

6.1

APABILITIES

........................................................................... 8

2.5.

OMMUNICATION

ANAGER

6.0.1

APABILITIES

........................................................ 11

2.6.

NTEROPERABILITY

........................................................................................................ 12

SESSION MANAGER OFFER DESCRIPTION ............................................................ 15

3.1.

ESSION

ANAGER

PPLIANCE

ODEL

...................................................................... 15

3.2.

YSTEM

ANAGER

OFTWARE

.................................................................................... 16

3.3.

RICING AND

ATERIAL

ODES

................................................................................... 16

3.4.

PGRADES

.................................................................................................................... 21

3.5.

MPLEMENTATION

ERVICES

......................................................................................... 21

3.6.

VAILABILITY

................................................................................................................. 22

3.7.

ESSION

ANAGER

EQUIRED

ARDWARE

................................................................ 22

3.8.

EQUIRED

OFTWARE

.................................................................................................. 23

3.9.

EQUIRED

YSTEM

ANAGER

LATFORM

.................................................................. 23

3.10.

RDERING

ROCESS WITH

ASD .................................................................................. 25

3.11.

ASD

LOCATION

CHANGES .................................................................................... 27

3.12.

ASD

UPGRADES ....................................................................................................... 28

COMMUNICATION MANAGER OFFER DESCRIPTION ........................................... 29

4.1.

RICING AND

ATERIAL

ODES

................................................................................... 29

4.2.

UPPORTED

ERVERS

.................................................................................................. 29

4.3.

OMMUNICATION

ANAGER

ICENSE

UNCTIONS

...................................................... 33

4.4.

VAYA

URA

FOR

URVIVABLE

ORE AND

VAYA

URA

FOR

URVIVABLE

EMOTE

4.5.

VAYA

URA

OMMUNICATION

ANAGER

UNDLES FOR THE

ARKET

OLUTIONS

................................................................................................................................ 35

4.6.

NALOG

TATION

ICENSES

......................................................................................... 36

4.7.

PGRADES

VERVIEW

.................................................................................................. 37

4.8.

PGRADING TO

–

OFTWARE

.......................................................................... 39

4.9.

ICENSING FOR

EMOS

ABS AND

RIALS

.................................................................. 40

4.10.

ASD

HANGES

............................................................................................................. 41

SERVICEABILITY ............................................................................................................. 45

5.1.

OFTWARE

UPPORT AND

ARDWARE

AINTENANCE

............................................... 45

5.2.

ERVICE

NTITLEMENTS FOR

USTOMERS

.......................................................... 46

5.3.

ARRANTY

.................................................................................................................... 46

5.4.

RODUCT

ORRECTION

OTICES

(PCN

) .................................................................. 48

5.5.

RODUCT

UPPORT

OTICES

(PSN

) ........................................................................ 49

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 3 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

5.6.

ECHNICAL

ONSULTING

YSTEM

UPPORT

............................................................... 49

5.7.

NHANCED

ERVICES

VAILABLE

................................................................................ 50

5.8.

VAYA

ABS

IELD

UPPORT

....................................................................................... 50

5.9.

PLDS

OFTWARE

OWNLOAD

OLICY

........................................................................ 51

5.10.

PLDS

ICENSES

........................................................................................................... 51

5.11.

EMOTE

AINTENANCE

................................................................................................ 52

DOCUMENTATION ........................................................................................................... 53

6.1.

ELEASE

OTES

........................................................................................................... 53

6.2.

SER AND

YSTEM

OCUMENTATION

.......................................................................... 53

TRAINING ........................................................................................................................... 56

APPENDIX A: AVAYA AURA PACKAGING ....................................................................... 58

APPENDIX B: GLOSSARY OF TERMS AND ACRONYMNS .......................................... 59

APPENDIX C: RELEASE HISTORY LIFECYCLE DATES ............................................... 63

APPENDIX D: ADDITIONS TO COMMUNICATION MANAGER 4.0 AND EARLIER
SYSTEMS ................................................................................................................................... 64

APPENDIX E: SOFTWARE RE-LICENSING POLICY ...................................................... 65

APPENDIX F: SELECTED COMMUNICATION MANAGER FEATURES AND
RELATED PRODUCTS ............................................................................................................ 66

APPENDIX G: MIGRATION AND MERGE OFFERS ........................................................ 67

APPENDIX H: LICENSE MOVES .......................................................................................... 68

APPENDIX I: SURVIVABLE REMOTE AND ICC CONVERSION................................... 69

APPENDIX J: MOVING SURVIVABLE REMOTE AND SURVIVABLE CORE
SERVERS ................................................................................................................................... 70

APPENDIX K: UPGRADE PROTECTION PLAN FOR COMMUNICATION MANAGER
4.0 ................................................................................................................................................. 71

APPENDIX L: SURVIVABLE CORE CONVERSIONS ....................................................... 72

APPENDIX M: RFA LICENSED FEATURES ....................................................................... 73

APPENDIX N: STANDARDS SUPPORTED ........................................................................ 74

NOTES: ....................................................................................................................................... 74

CONTACT INFORMATION ...................................................................................................... 75

RODUCT

ANAGEMENT

ONTACTS

....................................................................................... 75

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 4 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

1. AVAYA AURA®

Avaya Aura® R6.1 is the flagship product collection for next generation enterprise
solutions based on the revolutionary SIP-based architecture. Avaya Aura is enhanced
by additional new capabilities of the Avaya Aura core, the Avaya Aura Session Manager
6.1 and Aura Communication Manager 6.0.1.

With this release of Avaya Aura the following new capabilities are introduced:

∗ Unprecedented total scale of up to 10 Session Managers and 100,000 SIP users

supported in an enterprise

∗ Centralized Avaya Aura core supported converged SIP voice and video call

admission control

∗ Even more SIP features including “desk-level” SIP E911 location reporting
∗ CS 1000 SIP networking and feature transparency
∗ Legacy CS 1000 NRS replacement
∗ Enhanced Session Manager SIP routing adaptations
∗ Introducing System Manager “tab-based” SM and CM management with lightning

quick screen switching

∗ System Manager Release 6.1 can also manage Session Manager 6.1, Session

Manager 6.0, and the transition period where both releases co-exist during an
upgrade.

For more information see

Appendix A

or the Avaya Aura Channel Announcement:

http://portal.avaya.com/ptlWeb/products/P0540/AllCollateral

System Manager 6.0 Courseware

Getting Started with System Manager

ATC 00182

OEN

CM and System Manager

ATC 01842

OEN

System Manager Administering User Profile Accounts

ATC 00184

VEN

System Manager 6.0 General Overview

ATU 00180

OEN

System Manager 6.0 Technical Overview

ATU 00183

OEN

System Manager 6.0 Delta: General Overview

ATC 01825

OEN

System Manager 6.0 Delta: Technical Overview

ATC 01828

OEN

System Manager 6.0 Installation and Setup

ATU 01852

OEN

Advanced System Manager Administration

ATA 02540

VEN

System Manager 6.1 Delta: General Overview

ATU 02643

OEN

System Manager 6.1 Delta: Technical Overview

ATI

02642

OEN

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 5 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

System Manager 6.1 Installation and Setup

ATA 02641

OEN

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 6 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

APPENDIX A: AVAYA AURA PACKAGING

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 7 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

2. SOLUTION DESCRIPTION

This document focuses on the new Avaya Aura 6.1 additions to Avaya Aura
Communication Manager (CM) and Avaya Aura Session Manager (SM).

Avaya Aura System Manager (SMGR) remains the centralized management vehicle for
administering SM and with 6.1 has the capability to administer 100,000 SIP users in
what is becoming the industry standard “one-stop” centralized enterprise-wide
management system. The total scale of SMGR includes up to 25,000 SIP entities with
500 Communication Managers.

Key customer benefits of Avaya Aura 6.1 are:

• Business continuity assurance driven by the new 10 SM maximum running in

an active-active configuration

• Increased customer satisfaction by better SIP adaptations with service

providers, increased scale and the easy to use SMGR tab-based interface

• Lower total cost of ownership from SIP connectivity, decreased management

time with SMGR, and improved interoperability with legacy Nortel equipment

• Decreased costs and real convergence with controls for voice, video and data

bandwidth allocation over shared resources with new Session Manager call
admission control

2.1.

New Servers Overview

Avaya Aura 6.1 introduces two new servers replacing the S8800 servers S8800 servers
are expected to reach end of sale (EOS) status as of June 6, 2011. The following new
servers will enhance the quality and performance of the Avaya Aura® applications and
solutions. More details on these new servers are included in the respective Session
Manager and Communication Manager sections.

Application

Server Type

Material Code

List Price (USD)

Session Manager

HP DL360G7

700501092

$11,500

Dell R610

700501082

$11,500

Communication
Manager simplex

HP DL360G7

263764

$8,800

Dell R610

263760

$8,800

Communication
Manager duplex

HP DL360G7

263765

$21,500

Dell R610

263761

$21,500

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 8 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

2.2.

Session Manager Overview

Avaya Aura Session Manager 6.1 is yet another step in revolutionizing enterprise networks.
It adds the ability to manage video calls along with voice, increases in scale, and increased
support for desk-level emergency calling. The new capabilities of the Avaya Aura Session
Manager 6.1 include:

• Up to 10 Session Manager instances allowed per SMGR management system

with the same market leading active-active N+1 reliability capabilities the SM 1.1
release introduced in 2008

• Increased call processing performance of up to 300,000 BHCC
• A scale increase for up to 100,000 SIP endpoints
• Converged voice and video call admission control
• SIP endpoints can report detailed location down to the “desk level” when making

911 emergency calls with SIP integration through RedSky.

• New adaptation module (AM) capabilities to modify to the “To” and “From” SIP

headers improving interoperability with SIP entities in general and specific
service providers requiring strict SIP header rules

• CS1000 SIP Avaya Aura interoperability and networking
• Legacy CS 1000 NRS replacement
• SIP application sequencing for SIP endpoints on Communication Manager

configured as a Evolution Server

• The new SMGR tab-based interface applies to all SM screens, allowing quick

screen swaps for ease of administration

In summary, Session Manager and System Manager can now handle up to 25,000
locations in a full deployment with up to 3 Million BHCC of inter-location calling.
Deployed in an active-active geo-redundant configuration, session control moves
between Session Manager Instances in less than three seconds after a network or
equipment failure. With 6.1 up to ten SM instances can be deployed in a single
enterprise and support up to 100,000 SIP users including SMGR support. As always,
100% of the SIP entities have their signaling encrypted by TLS from Session Manager,
and point to point media can be encrypted with SRTP.

Both the Avaya Aura Session Border Controller and the ACME Packet SBCs are
supported at the edge of the network for a complete, highly redundant and secure SIP
enterprise solution.

2.3.

System Manager Management

Session Manager and Communication Manager both share the common SMGR
maintenance, monitoring and administration interface for integrated, centralized
management. System Manager’s new tab-based interface provides highly interactive
and lightning-quick screen swaps between different SMGR screens for a much
improved administrator experience.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 9 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

2.4.

Session Manager 6.1 Capabilities

Following is a summary of the capabilities of Avaya Aura Session Manager 6.1:

Increased Scale
Up to 100,000 SIP endpoints may register to the Session Manager in release 6.1 on the
road to expanding to over 250,000. In addition each of the 100,000 endpoints is
simultaneously registered with 2 SMs in the core, and one Survivable Remote at the
branch. Release 6.1 is designed to be another giant leap for large enterprise
deployments that will expand quickly over time. In addition, a single SMGR-managed
“domain” can support up to 10 Session Manager instances in Avaya’s industry leading
active-active N+1 configuration. The list of Avaya SIP endpoints supported is:

• 96XX Family of SIP capable handsets including 9620L, 9620, 9620C, 9630,

9630G, 9640, 9640G, 9650, 9650C

• 96X1 SIP handsets 9601, 9608, 9621 and the 9641
• 46XX SIP-downloadable software handsets with FW load “s10d01b2237.bin”
• 1603SW-I
• Legacy 1100/1200-Series – 1120E, 1140E, 1165E, 1220, 1230 IP Deskphones

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

• One-X Communicator
• The Flare Experience on the Avaya Desktop Video Device
• Avaya 1000 series video endpoints

Increased Performance
Software enhancements allow an unprecedented 300,000 BHCC of inter-location
calling. Complex calls of course will have different characteristics, but this is the
highest performing Avaya Aura core yet, with up to 3 million BHCC possible with 10
SM instances.

Converged Call Admission Control
The newest version of SM supports truly converged voice and video bandwidth
management with SMGR centralized administration and control. The system
administrator can set the bandwidth allocations between voice and multimedia traffic
with an option to allow voice to “steal” bandwidth from the unused video allocations
when network conditions require. No longer are calls “assumed” to require a fixed
bandwidth; SM intercepts every SIP request for service, examines the SIP “SDP” for the
requested bandwidth, and allocates the actual bandwidth requested and accepted. In
addition, SM will automatically “downspeed” video calls to the bandwidth available,
allowing video calls to complete at lower bandwidths that other less-capable systems
might block or (worse) allow all existing video and voice calls to degrade.

In addition, SMGR introduces advanced control of SM video or multi-media bandwidth
allocation. The maximum allowed bandwidth for a multi-media call with separate
controls for inter-location (where resources are naturally scarce) and intra-location
(where more bandwidth is available and higher quality can be allowed) are now possible

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 10 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

on a per-location basis. The minimum “downspeed-able” video bandwidth is also
administrable per location to insure a level of video quality. Administrators can also now
see the number of audio and multi-media calls in real time on a per location basis for
accurate management.

Enhanced Emergency Calling
SIP endpoints can now report their exact location down to the very IP phone jack for
emergency calling. The integration with the RedSky E911 Manager™ allows automatic
updating of the PSAP public database and the ability to report detailed, desk-level
locations for SIP terminals even when SIP terminals or users move locations without
administrator intervention.

Adaptation Module Advancements
Without incurring the overhead required in a full back-to-back-user-agent (B2BUA), SM
allows programmable replacement of the “From” and “To” headers with all the SM
adaptation modules to meet strict SIP entity and service provider requirements. This is
especially useful for enabling the entire user base to participate in alternate and least
cost routing between multiple service providers, insuring the promise of the lower total
cost of ownership of the Avaya Aura core.

More SIP Application Sequencing
Session Manager now supports SIP users running on Communication Managers
configured as Evolution Servers (ESs) by allowing feature sequencing for this type of
users alongside the already supported implicit users.

Avaya Communication Server 1000 Interoperability
The “Nortel” SM SIP Adaptation Module (AM) has been enhanced to increase the
number of CS 1000 features that interoperate with other SIP entities connected to the
Avaya Aura core. SM simplifies the multi-part MIME bodies of CS 1000 SIP messages
which make it compatible with non-CS1000 SIP entities. The new AM is able to
translate the History-Info header from the CS1000 syntax to the Avaya Aura syntax for
the ultimate in interoperability.

In addition, SM allows a new kind of application sequencing for implicit CS 1000 users –
implicit intra-CS application sequencing. A new CS 1000 R7.5 feature “Exposed Local
Calls” allows even intra-CS 1000 calls to be exposed to the SM core. For the first time
ever, this enables calls between users on the same CS 1000 to enjoy application
sequencing.

When CM (R5.1 and greater) and CS 1000 (R4.5 and greater) are connected to the SM
core the following features will work among users connected to different CM/CS 1000
systems:

Basic call - incoming and outgoing
Hold and un-hold
Calling name and number display
Called name and number display

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 11 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

Connected name and number display including when redirected to coverage, call

forwarding, call pickup, etc.

Centralized messaging with Avaya Aura Messaging including MWI
Call forward (all, don’t answer, busy)
Transfer
Ad-Hoc conferencing including Meet-me conferencing and Avaya Aura Conferencing,

users on CM or can initiate conferences or join conferences with parties on other CS
1000s or CMs

Display of the answering party’s name and number when answered by a member of a

hunt group where members of the hunt group are on different CMs or CS 1000s

Calling party privacy (the ability to restrict the called party from seeing the calling party’s

name and number on a call-by-call basis)

Finally, SM passes location information to/from the CS 1000 so that multi-location
bandwidth allocation and call admission control for non-SIP endpoints is enabled.

NRS Replacement
Session Manager can now be used to replace the legacy CS1000 Network Routing
Service (NRS) capabilities of the SIP Proxy Server (SPS) and the Network Connect
Server (NCS). A Routing Data Conversion Tool (RDCT) is provided to migrate NRSM
provisioning data into the Avaya Aura System Manager (SMGR) and is implemented as
a web-based tool for easy access.

Contacts for SIP Users
With Communication Manager and Avaya SIP endpoints, SM provides the ability for
users to search the enterprise-wide user database for contacts for calling, instant
messaging, and presence. A wide variety of search parameters are offered Where
users can input the entire field, or a partial field with wildcard characters) including user
names, phone numbers, login name, SIP handle, SIP domain, video capability, etc. to
quickly identify and communicate with enterprise associates. Both SIP and non-SIP
users are included in the search/display capabilities.

SIP Tracing

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 12 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

The SM SIP tracing capabilities have been enhanced to enable tracing output to an
external Syslog host. This enables Session Manager to send all the (decrypted) SIP
traffic out to an external host. Session Manager uses Syslog protocol for sending the
SIP traffic (as used currently for SIP Tracing) and the link between SM and the Syslog
server can also be encrypted for security (Stunnel).

Administration Performance
The performance for CM and SM administration on SMGR has been increased. Many
operations that used to take several seconds are faster with visibly improved response
times. This is in addition to the new tab-based SMGR administration interface and the
improved home page layouts.

Administration Release Flexibility
SMs may now be administered and maintained using SMGR R6.1 in a “mixed release”
mode of operation. An enterprise with mixed releases of SM R6.0 and R6.1 can be
administered with a single R6.1 SMGR relaxing the requirement for SMs to be held in
“Management Disable” state while the upgrade is in progress.

Security
Session Manager has moved to Red Hat Enterprise release 5.5 with the added security
updates of this newer operating system release.

2.5.

Communication Manager 6.0.1 Capabilities

The following is a summary of the new capabilities for Avaya Aura® Communication
Manager 6.0.1:

Call Detail Record Timezones
CM has added CDR provisions for timezone support of CDR records from CM branches
in different locations. The ability to select CDR to always record the local time, correlate
tenant numbers with locations, and if the call involves multiple locations, location-to,
timezone-to, and country-to-country, record the location of the last party on the call has
been added to the CM 6.0.1 release. This permits easier identification of national and
international prefixes on the CDR output.

Call Pick up Party Extension on Call Detail Records
CM 6.0.1 will display the answering Call Pick up Party extension on CDR records which
will show the extension that actually picked up the call.

SIP Trunk Load Balancing
Communication Manager now allows the administration of multiple signaling groups for
a single trunk group to provide load-balancing for SIP trunks. Customers can set up the
trunk members in the way they require. Either as Blocks: Trunk Members from one
signaling group are kept together; or Interleaved: Trunk Members from each signaling

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 13 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

group are interleaved (i.e. Sig Grp 1, then Sig Grp 2, then Sig Grp 3, then 1, then 2,
then 3, etc.) The interleaved method provides round-robin load-balancing for SIP
trunking. The use of this feature enables customers to connect to SIP applications
directly without SM for some scenarios, such as connecting to SIP-integrated Modular
Messaging (MM).

Support Passing of SIP 3xx Messages
Communication Manager will now support the directive 'no-recurse' if it is received in
the Request-Disposition header field of Invite messages as defined in RFC 3841. The
'no-recurse' option will tell CM to pass SIP 3xx messages like '302 Moved Temporarily'
on to the phone, This function will provide SIP phones access to more features of
applications such as Meeting Exchange and Presence Services now and in the near
future.

Attendant Camp-on Busy
When an attendant extends calls to a multi-appearance phone which is busy on another
call but still has at least one call appearance idle, the extended call can now be
configured to always return to the attendant, if no one answers the call, and the
attendant recall timer expires no matter whether there is a coverage path administered.

2.6.

Interoperability

Session Manager connects to any IETF compliant SIP solution. The following products
have been certified to interoperate and connect directly with Session Manager and
detailed design assurance and operation integrity confirmation is available with Avaya:

∗ Avaya Aura Communication Manager 5.1.2, 5.2, 5.2.1, 6.0 and 6.0.1 – a new

release of Avaya’s flagship IP telephony software that connects seamlessly to
the Session Manager core. Specifically with CM feature server configurations,
CM releases 5.2.1, 6.0 and 6.0.1 are supported with SM 6.1.

∗ Modular Messaging 5.2
∗ Avaya Aura Messaging 6.0 and 6.1 - Avaya’s messaging platform providing

centralized voicemail and centralized messaging for the entire enterprise.

∗ Avaya 96XX Handsets R2.6 – Avaya’s flagship endpoint line running 2.6 SIP

firmware

∗ Avaya G860 High Density Trunk Gateway R2 – the AudioCodes third party

gateway capable of terminating multiple DS3 interfaces to integrate enterprise
solutions with the PSTN.

∗ Avaya CS1000 R5.5, R6.X, R7.X – the legacy CS1000 communications server
∗ Avaya Voice Portal 5.1, and 5.2 – Avaya’s innovative new voice response

solution with powerful SIP capabilities and unprecedented scalability.

∗ Avaya Intelligent Customer Routing - Avaya’s next generation enterprise-wide

contact center innovation.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 14 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

∗ Avaya Meeting Exchange 6.0 and 5.2 – The leading conferencing and

collaboration engine on the market today.

∗ Acme Packet Session Border Controller 2900/3800/4500 – while Session

Manager supports all SIP-compliant SBCs, the Acme Packet family has been
tested and certified by Avaya and Acme Packets to secure the border for all
Session Manager enabled solutions.

∗ Avaya Aura Session Border Controller – Avaya’s addition to the Avaya Aura

solution that includes market leading Session Border Controller functionality.

∗ 9600-Series IP Deskphones

–

For proper operation of the SIP Survivable

Remote, 9600-Series IP Deskphones should be running SIP Release 2.6.3 or
later software.

Communication Manager is also interoperable with IETF compliant SIP devices. The
following products have been certified to interoperate and connect with Communication
Manager via Session Manager and detailed design assurance and operation integrity
confirmation is also available with Avaya:

∗ Avaya Aura Session Manager 1.1, 5.2, 6.0 and 6.1
∗ Modular Messaging 5.2 and 5.1 – Avaya’s messaging platform providing

centralized voicemail and centralized messaging for the entire enterprise.

∗ Avaya 96XX Handsets R2.6 – Avaya’s flagship endpoint line running 2.6 SIP

firmware

∗ Avaya G860 High Density Trunk Gateway R2 – the AudioCodes third party

gateway capable of terminating multiple DS3 interfaces to integrate enterprise
solutions with the PSTN.

∗ Avaya CS1000 R5.5, R6.X, R7.X – the legacy CS1000 communications server
∗ Avaya Voice Portal 5.1, and 5.2 – Avaya’s innovative new voice response

solution with powerful SIP capabilities and unprecedented scalability.

∗ Avaya Intelligent Customer Routing - Avaya’s next generation enterprise-wide

contact center innovation.

∗ Avaya Meeting Exchange 6.0 and 5.2 – The leading conferencing and

collaboration engine on the market today.

∗ Acme Packet Session Border Controller 2600/3800/4500 – while Session

Manager supports all SIP-compliant SBCs, the Acme Packet family has been
tested and certified by Avaya and Acme Packets to secure the border for all
Session Manager enabled solutions.

∗ Avaya Aura 6.0 Session Border Controller – Avaya’s addition to the Avaya

Aura solution that includes market leading Session Border Controller functionality

∗ 9600-Series IP Deskphones

–

For proper operation of the SIP Survivable

Remote, 9600-Series IP Deskphones should be running SIP Release 2.6.3 or
later software.

Session Manager & Communication Manager Compatibility Matrix

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 15 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

5.1
AE

5.2
AE

5.2.1

6.0

6.0.1

SM 5.2

YES*

YES

YES** YES

YES

SM 6.0

YES*

YES

YES** YES YES

YES

SM 6.1

YES*

YES

YES** YES YES

YES

*Limitations apply – please see the SM 1.1 release notes for details
**CM 5.2.1 FS configurations are only supported in non-redundant configurations
only as with SM 5.2/CM 5.2.1

Session Manager & System Manager Compatibility Matrix

SMGR

CM 5.X

CM 6.0

CM 6.0.1

SM 6.0

SM 6.1

SMGR 5.2

YES

SMGR 6.0

YES

SMGR 6.1

YES

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 16 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

3. SESSION MANAGER OFFER DESCRIPTION

NOTE: All pricing contained herein are US Global List Price only. Readers are referred
to regional product management for pricing specific to each region.

NOTE: All pricing contained within, while accurate at the time of publication, should be
considered as unofficial; Readers are directed to verify the accuracy of all prices cited
by accessing SAP or ASD after the products become generally available.

The components of the offer are the Session Manager software and hardware platform,
and the System Manager software. Session Manager is delivered as software pre-
installed on a fixed hardware platform (appliance model). System Manager is a
software-only offer that is downloaded over the internet by customers and then loaded
onto specific server hardware available from Avaya. The downloaded System Manager
software includes the System Manager application software and an integrated Linux
Red Hat OS with Avaya System Platform software for easy installation.

3.1.

Session Manager Appliance Model

Session Manager will be offered on a fixed hardware platform (the “appliance model”) to
intentionally limit the configurations required to certify and maintain in the field. The
server platform is the S8800. SM is not offered on customer provided hardware.

In the Session Manager appliance model, the steps for implementation are the following
where “Avaya” means Avaya or Avaya certified business partners:

1. Customer will order the SM from Avaya

2. Avaya’s existing staging partner Avnet will install the Red Hat OS on the S8800

server download (from Avaya PLDS) and install the SM SW, and test the
configuration as per the instructions on the Avaya support website.

3. Avnet will use the “Kickstart” DVD disk to lock Root and create Services

accounts. The Services account passwords will be changed by the password
change control system once the server is registered.

4. Customer will rack and stack servers – or alternatively contract with Avaya or an

Avaya Business partner services.

5. Customer will administer the SM software – or alternatively contract with Avaya

or an Avaya Business Partner services to administer the SM software.

As described above, Session Manager software comes pre-installed on the hardware
platform. System Manager 6.0 software is also offered as an appliance and the SMGR
software is available for download for entitled customers and Business Partners from
the Avaya PLDS website. Session Manager and System manager software are also
optionally delivered using DVDs if ordered.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 17 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

3.2.

System Manager Software

System Manager (SMGR) is offered as remotely downloadable software on the new
Avaya servers and the software is available for download from the PLDS website.
SMGR is not offered on customer-provided hardware.

3.3.

Pricing and Material Codes

Session Manager and System Manager are ordered for the core of an enterprise that
may also contain Avaya Aura Editions and third party SIP equipment including third
party PBXs. For more information see

appendix A

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.

Avaya is pleased to announce the introduction of a new and simplified Avaya Aura®
Session Manager (SM) price structure, based upon customer and partner requests. The
new price structure was introduced on 7 February 2011 as per announcement ‘Session
Manager Pricing Changes April 14, 2011’ bulletin.

The new pricing structure is based upon a session or connection (sometimes known as
“trunk”) model that allows customers to purchase licenses based on the number of SIP
sessions required, rather than the number of users. This will both simplify and increase
the flexibility of Session Manager licensing, making it easier and more cost effective to
position the value of Session Manager against customer needs.

The new material codes for the session based pricing will go into effect in ASD and SAP
on 7 February 2011. Previous user-based pricing codes will continue to be orderable as
piece-part items from ASD and SAP until 4 April 2011 and Avaya will honor ASD and
SAP quotes that are generated and saved under the Distributor or customer sold-to
prior to 4 April 2011 provided they are ordered by 6 June 2011. The CS 1000 Enterprise
Configurator (EC) also has the new Session Manager simplified pricing structure in
place as of December 2010.

Additional copies and updates to this document can be downloaded at:
https://enterpriseportal.avaya.com/ptlWeb/bp/products/P0533/JobAidsTools

Session Manager 6.X Pricing

As of 7 February 2011, Session Manager introduced the connection model, referred to
as SIP session licensing. The connection model licenses Session Manager connections
to each SIP entity in the network instead of user licenses. This simplifies Session
Manager licensing, making it easier and more cost effective to position Session
Manager value based on actual customer incremental needs. The new material codes
for the connection model are as follows:

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 18 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

The connection model is based on the SIP session, the basic unit of connection in the
SIP protocol. Each “call” or connection between one or more parties is a SIP session,
and will require an SM connection license to connect to the SM. For example, if a SIP
entity like Communication Manager (CM) connects to the SM and can support 5
simultaneous calls or sessions that go through the SM, then 5 connection licenses
should be purchased.

New Material Code Descriptions

The following diagram illustrates the various connections to Session Manager and their
associated pricing. Note that both types of connection licensing - $0 and $150
connection licensing may be present in the same enterprise, and while the arrows below
show a single connection, each SIP entity below will normally require multiple
simultaneous connections so the licensing will be N * $150/$0 where “N” is the number
of simultaneous connections required for each SIP entity.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 19 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

264148 SM R6.X SIP CONNECTION LICENSE is required for a SIP connection to SM
for one of the following reasons:

1. CM Standard Edition server needs connections to the core for the STD CM users

controlled by it

2. CS 1000 server needs connections to the core for the Enhanced licensed users

controlled by it.

3. A third party application (like Microsoft UM, or Cisco Meeting Place) require connections

to the core

4. A third party PBX (like Cisco UCM or Siemens 4000) need connections to the core
5. A third party gateway – for example Multi-tech or Cisco need connections to the core
6. A third party SBC need connections to the core

In short, anytime a third party piece of equipment is required to connect to the Avaya
Aura SIP core, this material code is needed for each simultaneous call needed.

264231 SM R6.X SIP CONNECTION LIC ENTITLE is required for a SIP connection to
SM for one of the following reasons:

1. CM Enterprise Edition (EE) server needs connections to the core for the EE CM users

controlled by it

264148 SM R6.X SIP CONNECTION LICENSE is required for a SIP connection to SM for one
of the following reasons:

1. CM Standard Edition server needs connections to the core for the STD CM users

controlled by it

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 20 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

2. CS 1000 server needs connections to the core for the Enhanced licensed users

controlled by it.

3. A third party application (like Microsoft UM, or Cisco Meeting Place) require connections

to the core

In short, anytime a third party piece of equipment (other than an Acme Packet SBC) is required
to connect to the Avaya Aura SIP core, this material code is needed for each simultaneous call
needed.

264231 SM R6.X SIP CONNECTION LIC ENTITLE is required for a SIP connection to SM for
one of the following reasons:

1. CM Enterprise Edition (EE) server needs connections to the core for the EE CM users

controlled by it

2. CS 1000 server needs connections to the core for the Premium licensed users controlled

by it

3. Avaya Aura SBC used to connect the SM core to a non-enterprise network like a service

provider or business partner or outsourcer network

4. Acme Packet branded SBCs such as the Acme Packet Net-Net 3820 and Net-Net 4500

used to connect the SM core to a non-enterprise network like a service provider or
business partner or outsourcer network

5. An Avaya application connects to the SIP core like Modular Messaging Avaya Aura

Messaging, Voice Portal, Meeting Exchange, etc.

6. Avaya Gateways including the G860, SR/AG2330, SR/AG4134, or the certified

AudioCodes gateways (Mediant 3000, Mediant 2000, and Mediant 1000) purchasable
from Avaya using Avaya material codes that are available to both direct and indirect
channels

7. The Avaya BCM – the legacy small PBX (when the appropriate SIP connection or

session licensing is purchased on the BCM)

8. The Avaya B5800 branch solution (when the appropriate SIP connection licensing is

purchased on the B5800) with either centralized or distributed configurations

9. IP Office connects to the core (when the appropriate SIP connection licensing is

purchased on the IP Office)

10. Avaya Integral equipment connects to the core (when the appropriate SIP connection

licensing is purchased on the Integral)

11. CS 2100 SE13 needs connections to the core (when the appropriate SIP connection

licensing is purchased for the CS2100

This material code is needed for each simultaneous call required.

264232 SM R6.X SIP CONNECTION LAB LICENSE is used when the ASD is run to configure
a lab configuration. Note these licenses expire after 120 days.

264680 SM5.X TO R6.X UPG CONNECTION LIC is added to an order when ASD is used to
upgrade an SM 5.X to SM 6.1 software for user licenses the customer paid for with 5.X (229061
– SM 5.X USER LICENSE - $20). The user licenses used in SM 5.X will be converted to
connection licenses at a 7:1 ratio. This 7:1 conversion must be done manually after the
configurator is run.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 21 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

264679 SM R5.X TO R6.X UPG CONN LIC ENTITLE is used when ASD is used to upgrade an
SM 5.X to SM 6.1 software for user licenses the customer had as entitlements (these were
provided at no charge in 5.X and thus will be provided at no charge in the upgrade) with 5.X
(229060 – SM R5.X USER LICENSE w/CMEE - $0). The user licenses used in SM 5.X will be
converted to connection licenses at a 7:1 ratio. The 7:1 conversion must be done manually after
the configurator is run.

Entitlements

SM connection licenses will be an entitlement for the following:

1. CM Enterprise Edition users. For every 5 CM Enterprise Edition users ordered or

upgraded a single SM connection license will be included by ASD.

2. CS1000 Premium users. For every 5 CS1000 Premium users ordered or upgraded a

single SM connection license will be entitled.

3. CM Elite Contact Center (CC) agent licenses. For each Elite CC Agent license

purchased an SM connection license will be included. If more SM connection licenses
are required they must be purchased at the $150 price.

4. Avaya Aura Contact Center (AACC) agent licenses. For each AACC agent license

purchased an SM license will be included. If more SM connection licenses are required,
they must be purchased at the $150 price.

New Configuration Example

In this first scenario, ASD is used for a new CM/SM order – not an upgrade. The
following describe the situation before the order is placed:

• The customer does not have an SM
• The customer already has 250 CM 6.0 EE user licenses from other systems that are

already in service.

• The customer also has 180 CM 6.0 STD user licenses that are also in service. (Note an

SM core can support many CM systems, some of which may be STD and some EE)

• The new order includes 150 CM 6.1 EE user licenses as part of the order.

The ASD configurator should produce the following result.

The traffic analysis required 10 trunks to the STD CM. Note PLDS had already included
the 250 entitlements to SM user licenses for download. The 30 264231 licenses are an
entitlement for the 150 new EE users at the 5:1 ratio. The resulting license file will have
a combination of SM user and connection licenses – and this is allowed for this kind of
configuration.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 22 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

New SIP Trunking Contact Center Example

In this scenario, the customer is adding 3000 new SIP trunks from a service provider
through SBCs to an existing R6.1 pair of duplicated SMs.

• The SBCs are duplicated, with 3000 trunks capable on one SBC, and 3000 capable on

the other. But at any one time, only 3000 trunks on any SBC will be carrying an active
call.

• Part of the order is also adding 2000 agents with CC Elite contact center licenses. The

CC Elite agents are also on CM STD licenses.

The ASD configurator should produce the following result.

Note if the agents had CM-EE licenses, there would be an extra 286 more licenses
(264231) which are not needed, but added due to the CM-EE licenses. These licenses
may be used with other adjuncts if necessary.

3.4.

Upgrades

There is a software license charge required to upgrade Session Manager from SM 1.1
or SM 5.2 to SM 6.1. The ASD configurator may be used to design and create an
upgrade order. Upgrades to SM 6.1 from SM 6.0 require no license charge and the 6.1
software is available for these customers via PLDS at no charge.

To upgrade an existing SM 1.1/5.2 system to 6.1, simply place the order for an upgrade
using ASD and the software may be downloaded and installed on the existing 1.1/5.2
systems in service. Upgrades may be downloaded and installed by customers.

3.5.

Implementation Services

Avaya will provide customers with a complete set of implementation services for
Session Manager and System Manager. These services are performed by a qualified
team of Avaya personnel, including an Advanced Solution Architect. Professional
Services include Long Distance (Toll Charges) Savings Design, Trunk Aggregation
Savings Design, 3rd Party and Legacy Support Cost Savings Design, as well as
Business User Application Segmentation Design.

To request implementation pricing and a statement of work, complete the ASM Data
Gathering Form located at the link below and attach it to your Siebel resource request
for non-packaged implementation services, or, if you are an Avaya Business Partner, to
your ORS request for implementation pricing:

SM Job Aid Link for Avaya Account Teams:

https://enterpriseportal.avaya.com/ptlWeb/gs/products/P0533/JobAidsTools

SM Job Aid Link for Avaya Business Partners:

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 23 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

https://enterpriseportal.avaya.com/ptlWeb/bp/products/P0533/JobAidsTools

3.6.

Availability

Session Manager 6.1 was launched on November 30, 2010. A global rollout was also
launched on that date, with availability in all countries worldwide where Communication
Manager is currently sold.

North America

November 30, 2010

EMEA

November 30, 2010

APAC / Japan

November 30, 2010

CALA

November 30, 2010

Product availability dates may differ for other product components described in this
document. Please refer to the corresponding product definition documents for more
detailed information.

3.7.

Session Manager Required Hardware

The Session Manager R6.1 software is supported on the HP DL360G7, Dell R610,
S8800 IBM 3550m2, and the Dell 1950 (S8510) servers. Existing SM 1.1 customer
deployments on the Dell 1950 (S8510) may be upgraded to SM 6.1 by simply
downloading the SM 6.1 software and upgrading first to 5.2, then upgrading to SM 6.0,
and then to release 6.1 using the instructions found in section 3.12. Customers with
S8800 hardware on SM 5.2 systems also need only to download the new software to
upgrade; no server hardware changes are required. Avaya Business Partner and
Professional Services are available for upgrade support.

Session Manager ships from the factory on the HP DL360G7, a 1-U high server with 2 –
E5620 processor cores and 12 GBytes of memory as shown below.

Component

Description

Processor

Dual Quad Core Intel Xeon
Processors 5620 – 2.4GHz

Memory

12GByte DDR3

Hard Disk Drive 2 – 146GB SATA (RAID 1)

NIC

4 NICs (10/100/1000)

Slots

2 – PCI-e GEN2 slots

Power Supply

Redundant Power Supplies

USB Ports

4 USB Ports

Optical Drives

DVD +/-R/W

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 24 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

RoHS Compliant Yes

Chassis

30.4” (77.2 cm) D x 16.7” (42.6 cm) W
x 1.67” (4.26 cm) H

Alternatively, customers can order SM running on the Dell R610 hardware, which is not
the default configuration, but ASD can be used to order the Dell servers if the customer
requires.

Component

Description

Processor

Dual Quad Core Intel Xeon
Processors 5620 – 2.4GHz

Memory

12 GByte DDR3

Hard Disk Drive 2 – 146GB SATA (RAID 1)

NIC

4 NICs (10/100/1000)

Slots

standard

Power Supply

Redundant Power Supplies (opt)

USB Ports

4 USB Ports

Optical Drives

DVD +/-R/W

RoHS Compliant Yes

Chassis

30.4” (77.2 cm) D x 18.99” (48.24 cm)
W x 1.67” (4.26 cm) H

Upgrades for existing SM 1.1 and SM 5.2 servers will need to remove the SM100 from
the chassis to complete the upgrade to SM 6.1.

It is important to note that the Avaya System Manager is still required to administer SM;
this requires a separate server to host the System Manager software.

3.8.

Required Software

SM ships from the factory with all the software pre-installed and loaded and includes the
Red Hat Linux OS and the SM application software. Proper operation of the Session
Manager requires System Manager software running on a separate server.

3.9.

Required System Manager Platform

System Manager is a software-only solution also running on the HP or Dell servers.
Although technically the System Manager will run in a virtual OS environment, it is not
offered as such and requires dedicated hardware to run in this release.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 25 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

ASD (see section 3.10) has an option for customers and Business Partners to order the
hardware platform for System Manager in either simplex or duplex configurations.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 26 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

3.10.

Ordering Process with ASD

The CM ASD configurator will be used to configure and order Session Manager (SM)
and System Manager software. ASD will configure the SM from a system point of view
– treating SM as an enterprise-wide element for a customer. The single ASD screen
used to configure the 6.1 SM is shown below:

Figure 1: SM ASD Configuration

The new and changed questions on this screen are as follows:

• Is this a lab trial? Answering “Yes” to this question will cause ASD to configure

a single SM server, add an SM hardware instance to the order (normal HW
charges apply) and also configure a System Manager software license at no
extra charge. In addition, ASD will add 25 user licenses at no charge. Simplex
System Manager hardware will also be configured.

The lab trial license generated will expire in 120 days after the order is placed. If
additional time is required for the trial, an additional order must be placed and the
license file re-downloaded from the PLDS website.

When this question is answered “Yes” – the following will be added to the order:

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 27 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

# Material Code

Description

216899

SMGR 6.X SW LICENSE (Check)

700501092

HP DL360G7 SERVER SESSION MGR

229413

SM R6.X TRIAL USER LICENSE

When this question is answered “Yes” – and the Redundancy question (see
below) is answered as “N+1” the following will be added to the order:

# Material Code

Description

216899

SMGR 6.X SW LICENSE

700501092

HP DL360G7 SERVER SESSION MGR

229413

SM R6.X TRIAL USER LICENSE

Figure 2: SM ASD Redundancy Changes

1. REDUNDANCY What level of redundancy is required? – If “None” is selected

then the total number of SMs configured will be determined by the BHCC and no
“extra” or redundant SMs will be added to the order. If more than N+3
redundancy is required the SMs should be manually added as a piece part order.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 28 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

3.11.

ASD LOCATION CHANGES

The locations of the SM servers will be configured in the location screens and will be
required input for a properly designed and ordered system. One new question appears
on this screen:

Figure 3: SM ASD Configuration

1. SESSION MANAGER SERVERS: How many Session Manager servers are

required at this location [including redundant servers]?

The number answered will not be allowed to exceed the number of SMs already
configured based on the BHCC calculation made earlier on the system screen.

When the ASD design is run, if the correct number of required Session Manager servers
has not been input into a location, the ASD will post an error noting the number of
servers that must still be input to avoid errors.

Finally, a new option in the “Options - 1” screen has been added to allow for DVD media
to ship with an SM order.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 29 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

The “SOFTWARE MEDIA” will have a new default – and the default will be “DVD” to
allow for automatic inclusion of the DVD media for SM, CM and SMGR. When the
DVDs are not available at a customer site, BP and Avaya services must spend extra
time downloading the software when a re-install or recovery process is required. Thus,
the default allows the DVDs to be included in the order at a minimal charge ($50).

If the “SOFTWARE MEDIA” selection is “Download” then the DVDs will not be included
in the order.

3.12.

ASD UPGRADES

• System > Existing System > Existing Session Manager – this is a new

screen that has the same questions as the target system. The existing
SM equipment will be entered here, and then compared with the below
Target fields to see what upgrades are required.

• System > Target System > Target Session Manager – this is an existing

screen for either adding a new SM, adding a Third party license, adding a
SMGR server, adding BHCC capacity, etc.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 30 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

4. COMMUNICATION MANAGER OFFER DESCRIPTION

4.1.

Pricing and Material Codes

In August 2009 the Communication Manager material code description was changed to
Avaya Aura

Edition material codes. Avaya’s 9-tier structure was also simplified to a 3-

tier structure.

Software DVD

MAT CODE

DESCRIPTION

MPG

Global

List Price

Avaya Aura® Communication Manager 6.0 Software Media DVDs

700470065 AVAYA AURATM R6.0 SFTW DVD

$50

700500262 AVAYA AURATM SYSTEM PLATFORM 6.0 DVD

$50

4.2.

Supported Servers

Only the following servers are supported by CM 6.0.1:

HP DL360G7: The HP DL360G7 was introduced in November 2011. Avaya is
leveraging this life cycle event to move away from proprietary hardware designs and
towards the use of Commercial Off-The-Shelf (COTS) server platforms. The introduction
of this strategy will allow our customers to take advantage of the benefits of next
generation servers based on the continued development of Intel® processors. The HP
DL360G7 server supports a minimum software release of Communication Manager
5.2.1.

Component

Description

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 31 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

Processor

Dual Quad Core Intel Xeon Processors 5620 –
2.4GHz (simplex) or Dual Six Core Intel Xeon
Processors 5670 – 2.93GHz (duplex)

Memory

12 Gbyte DDR3

Hard Disk Drive

3 – 146GB SATA (RAID 5)

NIC

4 NICs (10/100/1000)

Slots

2 – PCI-e GEN2 slots

Power Supply

Redundant Power Supplies (opt)

USB Ports

4 USB Ports

Optical Drives

DVD +/-R/W

RoHS Compliant

Yes

Chassis

30.4” (77.2 cm) D x 16.7” (42.6 cm) W x 1.67”
(4.26 cm) H

Dell R610: The Dell R610 was introduced in November 2011. The Dell R610 server
supports a minimum software release of Communication Manager 5.2.1

Component

Description

Processor

Dual Quad Core Intel Xeon
Processors 5620 – 2.4GHz (simplex)
or Dual Six Core Intel Xeon
Processors 5670 – 2.93GHz (duplex)

Memory

12 Gbyte DDR3

Hard Disk Drive

3 – 146GB SATA (RAID 5)

NIC

4 NICs (10/100/1000)

Slots

standard

Power Supply

Redundant Power Supplies (opt)

USB Ports

4 USB Ports

Optical Drives

DVD +/-R/W

RoHS Compliant

Yes

Chassis

30.4” (77.2 cm) D x 18.99” (48.24 cm)
W x 1.67” (4.26 cm) H

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 32 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

Application

Server Type

Material Code List Price (USD)

Communication
Manager simplex

HP DL360G7

263764

$8,800

Dell R610

263760

$8,800

Communication
Manager duplex

HP DL360G7

263765

$21,500

Dell R610

263761

$21,500

S8300D: The Avaya S8300D Server was introduced in August 2009. The S8300D is the
latest evolution in Avaya’s series of S8300 embedded servers, and provides additional
processing power, memory, and hard disk capacity in support of System Platform R6 as
well as Communication Manager R6 and its associated templates. The Avaya S8300D
Server supports a minimum software release of Communication Manager 5.2.1

S8300D software compatibilities:

• Requires Communication Manager software release 5.2 or higher
• Supports versions of Communication Manager Messaging and SIP Enablement

Services which are compatible with Communication Manager 5.2

• Supports System Platform R6
• Supports Communication Manager R6 and its associated templates

For more information see the S8300D Server Channel Announcement at:

http://portal.avaya.com/ptlWeb/products/P0068/AllCollateral

(under Launch

Announcements).

S8510: The Avaya S8510 server went End of Sale on February 15, 2010. A hardware
migration kit is available to support migration to Communication Manager R6.0.1. This
migration kit will be available while our vendor continues to supply the memory.
Upgrades for the S8510 may require a different procedure than upgrades for the S8800
and will be described in release notes.

Material Code

Description

NPL

259270

S8510 Migration Kit

$1600

S8800: The Avaya S8800 series common server was introduced in the fall of 2009. The
S8800 End of Sale on 6 June 2011was announced 25 October 2010. The S8800 will
continue to support CM 6.0.1 as a new or upgrade platform. Refer to End of Sale
reference at

https://enterpriseportal.avaya.com/ptlWeb/gs/products/P0584/EndSaleNotices

The Avaya S8800 Server is sold in a variety of configurations to suit the specific
processor, hard drive and memory needs of each application and a representative

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 33 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

sampling of these configuration parameters are shown in the table below. Several new
configurations are being introduced to support Avaya Aura® 6.0.1 applications.

Software duplication available, hardware duplication is not offered.

Note: The server construct used with Communication Manager 5.2.1 is different than
the server construct used for Communication Manager 6.x. The recommended
configuration for Communication Manager 6.0 includes 12GB of memory, an additional
HDD with the HDDs configured as RAID 5.

A hardware migration kit is available to upgrade the S8800 Server construct used with
Communication Manager R.5.2.1 to support Communication Manager 6.x.

Material Code

Description

NPL

232320

S8800 Migration Kit

$1600

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

• The Product Transition Notice or other documentation for each adopting

application on support.avaya.com as they become generally available

S8800

Material Code

Description

MPG

Global List Price

70050023

S8800 SERVER SM R6

$11,500

248270

S8800 SERVER SES V2

$11,500

228992

S8800 SERVER MBT/CM6

$8,500

Note: to purchase a Communication Manager duplex server, formerly known as the
S87x0 class servers, order two 228992 S8800 SERVER MBT/CM6. The duplication is
done via Software Duplication as Hardware Duplication is not supported on the Avaya
S8800 Server.

Note: the S8800 SERVER SES V2 is new with Avaya Aura R6.1, but SES software is
still at release 5.X and is not compatible with SM 6.1 or CM 6.0.1. Thus, this new
hardware is orderable, but SES must be used with earlier CM versions earlier than CM
6.0.1.

S8730: The S8730 server went End of Sale on January 19, 2010 and the last supported
release is Communication Manager 5.2.1. Migration to Communication Manager R6 is
not supported on the S8730.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 34 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

4.3.

Communication Manager License Functions

CM defines license functions or operations as NEW or ADDITIONS, TRANSFER,
UPLIFT, UPGRADE, MOVE, PARKING and REDUCTION. With the implementation of
PLDS in CM 6.x, license management has been simplified requiring fewer steps.
Review the following sections as required for guidance in the license functions

NEW or ADD

– New is the purchasing of user licensing for a new CM
– Add is the expansion of a deployed CM with incremental user licensing

*Note: US NPL for the following two codes is different than GPL

•

225151 AVAYA AURATM STD ED R6 1001+ NEW LIC = $180

•

225154 AVAYA AURATM ENT ED R6 1001+ NEW LIC = $265

TRANSFERS

– Mobility of licenses between customer CM’s within the same software

release and edition (Like for Like)

For CM 6.x, Transfers are managed via the Global Licensing Policy by the use of the
online License Move Request Form found at the link below

https://enterpriseportal.avaya.com/ptlWeb/bp/so/CS2010105203323127038

Global Licensing Policy is found at

SAP CODE

DESCRIPTION

MPG Global List Price

Avaya Aura™ Standard Edition NEW License
225149

AVAYA AURATM STD ED R6 1-100 NEW LIC

240

225150

AVAYA AURATM STD ED R6 101-1000 NEW LIC

210

225151

AVAYA AURATM STD ED R6 1001+ NEW LIC

205

Avaya Aura™ Enterprise Edition NEW License
225152

AVAYA AURATM ENT ED R6 1-100 NEW LIC

320

225153

AVAYA AURATM ENT ED R6 101-1000 NEW LIC

290

225154

AVAYA AURATM ENT ED R6 1001+ NEW LIC

285

SAP CODE

DESCRIPTION

MPG Global List Price

Avaya Aura™ Standard Edition ADD License
225167

AVAYA AURATM STD ED R6 1-100 ADD LIC

240

225168

AVAYA AURATM STD ED R6 101-1000 ADD LIC

210

225169

AVAYA AURATM STD ED R6 1001+ ADD LIC

205

Avaya Aura™ Enterprise Edition ADD License
225170

AVAYA AURATM ENT ED R6 1-100 ADD LIC

320

225171

AVAYA AURATM ENT ED R6 101-1000 ADD LIC

290

225172

AVAYA AURATM ENT ED R6 1001+ ADD LIC

285

The following license material codes are used for aftermarket additions to existing
Communication Manager 6.x systems.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 35 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

https://support.avaya.com/css/appmanager/css/support?_nfpb=true&_pageLabel=WNC
ontent_Private&contentid=C2009223142629795043#Global%20Licensing%20Portabilit
y%20%28Avaya%20Products%29

UPLIFT

– Change of software level from Standard Edition to Enterprise Edition

New uplift codes when uplifting from the Avaya Aura® Standard Edition to the Avaya
Aura

Enterprise Edition.

UPGRADE and MOVE

– Upgrade is the updating of CM software release and licensing to current
– Moves are inclusive of both an Upgrade and a Transfer of the licenses

Avaya shifted to the Per User Model with the launch of Avaya Communication Manager
(CM) 3.0. With R6.x we are simplifying the upgrade structure by moving to one
transactional upgrade path and at a single tier. We no longer have the multi upgrade/
single upgrade distinction.

PARKING

– Placement of unused licensing on a non-operational or virtual server

CM 6.x licenses cannot be parked as Avaya Policy requires these licenses to be
covered under an Avaya Maintenance Contract. There is no exception policy.

REDUCTION

– Removal of unused licenses

SAP CODE

DESCRIPTION

MPG Global List Price

245456

AVAYA AURATM R6 EE 1-100 UPLIFT LIC

225141

AVAYA AURATM R6 EE 101-1000UPLFT LIC

245457

AVAYA AURATM R6 EE 1001+ UPLIFT LIC

SAP CODE

DESCRIPTION

MPG Global List Price

Avaya Aura™ Standard Edition Upgrade/M ove
229582

AVAYA AURATM R6 STD ED UPG LIC

229586

AVAYA AURATM R6 STD ED MOVE LIC

Avaya Aura™ Enterprise Edition Upgrade/M ove
229583

AVAYA AURATM R6 ENT ED UPG LIC

229587

AVAYA AURATM R6 ENT ED MOVE LIC

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 36 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

4.4.

Avaya Aura

for Survivable Core and Avaya Aura

for

Survivable Remote

With R6.0 the offer changes for purchasing Avaya Aura for Survivable Core (CM5’s
ESS/LSP) and Avaya Aura® for Survivable Remote (CM5’s LSP). Previously they were
sold based on the server or gateway size. This did not scale well for small sites when
viewed competitively. R6.x uses a simple, per-user price when in use with Avaya
Aura® Standard Edition. Similar to R5.0, both Avaya Aura® for Survivable Core and
Avaya Aura® for Survivable Remote are available for no additional charge with Avaya
Aura® Enterprise Edition.

NOTE: The one free survivable server is no longer included with Avaya Aura® Standard
Edition R6.x.

Customers with existing ESS and LSP server licenses on pre-CM 6.x Standard Edition
systems will not be charged to use these servers on a CM 6.0.1 system. However,
adding additional Survivable Core or Survivable Remote servers at the time of upgrade
or later will be charged the per-user fee per below.

4.5.

Avaya Aura® Communication Manager Bundles for the Mid

Market Solutions

Eight (8) Communication Manager Bundles were offered for mid-market solutions.
These have not changed from the 5.x releases. These software bundles are priced very
competitively and are available on the S8300 platform for initial front market purchase.
Note, Release 6.0.1 is not offered on the S8400 server platform.

The Enterprise Edition S8300 Communication Manager bundle also includes
Communication Manager Messaging software licenses at no additional charge.
Communication Manager Messaging is no longer free of charge with Avaya Aura®
Standard Edition.

Note: these bundles are available to the front market only.

For new S8300 system purchase, the following Avaya Aura® Edition 6.X software
bundles are available.

SAP CODE

DESCRIPTION

MPG Global List Price

248250

R6 STD ED SURVIVE REMOTE USER SW LIC

248251

R6 STD ED SURVIVE CORE USER SW LIC

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 37 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

NOTE

: Only one bundle can appear on a new system purchase order and these

bundles cannot be used for aftermarket addition and upgrades.

*NOTE: Bundle Pricing shown above is for the US market only.

4.6.

Analog Station Licenses

These codes are used to purchase new analog station licenses, upgrade from R5
Analog License to R6 Analog License, and also to uplift Analog licenses to either Avaya
Aura® Standard or Enterprise Edition.

• Analog station licenses are to be used for analog stations only (analog

deskphones, fax machines, etc).

• If at a later date, the station is to be used as a digital or IP station, the Analog

station license must be uplifted to either an Avaya Aura® Standard or Enterprise
Edition license.

• A minimum of one (1) Avaya Aura® R6 Universal license must be purchased for

each system (either Standard or Enterprise Edition).

• The upgrade codes listed below are only for upgrades from current R5 Analog

Licenses and are not to be used to downgrade an existing Universal license.

For more information on analog licensing, refer to the Communication Manager 6.0.1
product definition.

SAP CODE

DESCRIPTION

MPG

US Market*

Avaya Aura™ Standard Edition for S8300 stand alone sales
225132

AVAYA AURATM STD ED R6 50 USER BUNDLE

5,000

225133

AVAYA AURATM STD ED R6 100 USER BUNDLE

10,000

225134

AVAYA AURATM STD ED R6 150 USER BUNDLE

15,000

225135

AVAYA AURATM STD ED R6 200 USER BUNDLE

20,000

Avaya Aura™ Enterprise Edition for S8300 stand alone sales
225136

AVAYA AURATM ENT ED R6 50 USER BUNDLE

8,000

225137

AVAYA AURATM ENT ED R6 100 USER BUNDLE

16,000

225138

AVAYA AURATM ENT ED R6 150 USER BUNDLE

24,000

225139

AVAYA AURATM ENT ED R6 200 USER BUNDLE

32,000

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 38 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

4.7.

Upgrades Overview

In order to prepare customer translations and other data sets to be used by
Communication Manager 6.x, upgrades to Communication Manager 6.x from previous
releases to 4.0.5 require the installation of Communication Manager 5.2.1 and then a
pre-upgrade patch (2 step upgrade). This is required because Communication Manager
6.x uses a different licensing architecture (PLDS and WebLM) than the RFA licensing
used previously, and because it runs on Avaya Aura System Platform instead of directly
on the server hardware. This new licensing architecture requires more consideration
during the upgrade preparation to ensure the appropriate steps are followed.

NOTE: For upgrades from a release prior to release 4.0.5, where a 2 step upgrade is
required, Avaya will provide the customer with a no-cost license upgrade to
Communication Manager 5.2.1 from whatever release they are on, and then will charge
normally for the upgrade from Communication Manager 5.2.1 to Communication
Manager 6.x. Because Communication Manager has uniform upgrade pricing (as
previously announced), this does not affect the ultimate upgrade price charged to the
customer. This has now been combined into a single ASD design, with both the
upgrade to CM 5.2.1 and CM6.x codes.
NOTE: The manual application of UPPCM or SS+U is NOT required for the upgrade to
CM 5.2.1. This is automated in current releases of Avaya Solution Designer (ASD).

The potential scenarios for upgrading to CM 6.0.1 are

a. Upgrades from Communication Manager Release 5.x
b. Upgrades from Communication Manager Release 4.x
c. Upgrades from releases Communication Manager Release 3.x and prior with Data

Preservation

d. Upgrades from releases Communication Manager Release 3.x and prior without Data

Preservation

Please refer to the following sections for guiding thorough the required steps

SAP CODE

DESCRIPTION

MPG Global List Price

225185

AVAYA AURATM R6 ANALOG NEW LIC

40.00

225186

AVAYA AURATM R6 ANALOG UPG LIC

8.00

225187

AVAYA AURATM R6 ANALOG MOVE LIC

8.00

Uplift from Analog to Avaya Aura ™ Standard Edition
225188

AVAYA AURATM STD ED ANLG TO UNIV 1-100SW LIC

200.00

225189

AVAYA AURATM STD ED ANLG UNIV 101-1000SW LIC

170.00

225190

AVAYA AURATM STD ED ANLG TO UNIV 1001+SW LIC

165.00

Uplift from Analog to Avaya Aura ™ Enterprise Edition
225191

AVAYA AURATM ENT ED ANLG TO UNIV 1-100SW LIC

280.00

225192

AVAYA AURATM ENT ED ANLG UNIV 101-1000SW LIC

250.00

225193

AVAYA AURATM ENT ED ANLG TO UNIV 1001+SW LIC

245.00

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 39 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

a. Upgrades from Communication Manager Release 5.x

Note: An ASD design is not necessary to upgrade to CM 5.2.1. An ASD design for CM 6.x is all that is
required.

1. Install the PCN upgrade to CM 5.2.1
2. Apply the pre-upgrade patch for CM release 5.2.1
3. Use ASD to configure a CM 6 design as usual.
4. Install CM 6.x

b. Upgrades from Communication Manager Release 4.x

Note: This process is not applicable to CM Release 4.0.2 (JITC). An ASD design is not necessary to
upgrade to CM 4.0.5.

1. Install the PCN upgrade to CM 4.0.5
2. Apply the pre-upgrade patch for CM release 4.0.5
3. Use ASD to configure a CM 6.x design as usual.
4. Install CM 6.x

Upgrades from releases Communication Manager Release 3.x and prior with Data

Preservation

Note:

In this scenario, the customer must perform a 2 step upgrade (i.e. upgrade to CM 5.2.1 and

upgrade to CM6). ASD has recently been enhanced to allow both the CM 5.2.1 and CM6 upgrade on the
same design. ASD must be used to generate the correct single design using the following steps:

Use ASD to create the design with CM6 as the target, which will include both the CM 5.2.1
and CM6 upgrade codes automatically. Note: The ASD design will generate the necessary
UPPCM free upgrade codes automatically so the customer is not charged for the CM 5.2.1
upgrade. Do NOT select the UPPCM option in ASD unless the customer has a valid and
active UPPCM contract. Do NOT select the SS+U option in ASD unless the customer has a
valid and active SS+U contract. Implementation charges, however, may apply.
a. ASD will ensure only 1 set of SSI/SA codes when the target is CM6.

Install CM 5.2.1 and the CM 5.2.1 license file, and then the pre-upgrade patch

Install CM 6.x

NOTE: When doing the CM 5.2.1 install, it is not necessary to actually install CM 5.2.1 on any ESS or
LSP servers. This will save considerable time. These survivable servers will be installed with CM 6.x just
before the main server is upgraded to CM 6.x. However, if the customer will remain on CM 5.2.1 for any
length of time and needs ESS or LSP survivability during this time, you will need to install CM 5.2.1 on
each of them.

d. Upgrades from releases Communication Manager Release 3.x and prior without Data
Preservation
This manual migration is not supported nor recommended as Customer data WILL be lost and
provides little value. This process is provided for informational purposes only for Avaya
Business Partners as requested.

Use ASD to create the design with CM6 as the target, which will include both the CM
5.2.1 and CM6 upgrade codes automatically. Note: The ASD design will generate the
necessary UPPCM free upgrade codes so the customer is not charged for the CM 5.2.1
upgrade. Do NOT select the UPPCM option in ASD unless the customer has a valid and
active UPPCM contract. Implementation charges, however, may apply.
a. ASD will ensure only 1 set of SSI/SA codes when the target is CM6.
b. CM 5.2.1 codes are still required to upgrade the licenses need to be upgraded to

CM5 licenses before converting them from RFA to PLDS.

Capture or record non-translational data. See note *1 below

Backup translations (or use TMT)

Install new software CM 6.x

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 40 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

Restore translations

Manually migrate license and user info

Manually configure system

*note 1 – following data is not included in the translations files

• CMM translations and message store
• Web access masks and logins and passwords
• Custom user data such as banners, messages etc.
• SNMP alarming, IP address, and associated admin
• Administration for scheduled cron jobs such as backup
• Authentication, License files and feature bits including customer added users and

custom PAM settings that may have been modified via Root permissions

• LDAP Settings/Configuration if SSH is enabled and other customizations

For all upgrades, other licensing must be considered. Ie Call Center Elite

4.8.

Upgrading to CC 6.x – Software

Upgrades to Avaya Aura Communication Manager 6.x and CC Elite 6.x require a two step process

when the FROM release is 4.0 or earlier. See the above CM Upgrade section for specific detailed steps.

Two-Step Upgrade Generalizations

• SAP Order for the ACM 5.2.1 upgrade must be applied to RFA and installed on the system to be

upgraded

• Pre-upgrade patch must be applied when system is at ACM 5.2.1 or 4.0.5
• Implementation pricing is not covered
• Hardware costs are not part of this process
• ASD is fully capable of designing ACM 5.2.1 upgrades without issues
• Call Center R9 and earlier requires special handling contact channel team or product management

Find your scenario here and follow the steps.

Situation 1: Upgrading From ACM5.2.1 or 4.0.5

• No special process required
• Design, license and upgrade as needed
• Need to install pre-upgrade patch

Situation 1a: Upgrading From CM5.x
(any version other than 5.2.1)

• Install PCN to get customer to 5.2.1 and install pre-upgrade patch
• ASD normal upgrade design to 6.x
• Install CM6.x

Situation 1b: Upgrading From CM4.x (except 4.0.2)

• Install PCN to get customer to 4.0.5 and install pre-upgrade patch
• ASD normal upgrade design to 6.x
• Install CM6.x

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 41 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

Situation 2a: Upgrade from all releases of CM 3.x and prior,
AND customer

• If any release Call Center is on CM1 or CM 2

Tell ASD None for CC and None for Target, do not add agents at this point.

Remove code 212487 from output design, this prevents a Basic Call Center

• If Call Center is at CM 3 or CM 4

Tell ASD existing CC R3 for CC R3 or earlier, tell ASD CC R4 for R4

Do not upgrade Call Center, do not add any agents

• Process design through distribution, SAP, install upgrade, upgrade patches and RFA license
• Design ACM 6 Upgrade starting with an ACM 5.2.1 starting point

From CC 3 and earlier, upgrade to CC 6 from CC 3, ok to add agents here

From CC 4, upgrade to CC 6 (or keep CC R4), ok to add agents here.

• Install CM 6

Situation 2b: Upgrade from CM 1.x through CM 4.x

• Upgrade Call Center to R5, customer may opt to keep CC R4 with CM6
• Process design through distribution, SAP, install upgrade, upgrade patches and RFA license
• Design CM 6 and CC 6 Upgrade starting with an CM 5.2.1 and CC 5 as a starting point
• Install CM 6

Situation 3a: Upgrade from pre CM 1.x

• If Call Center is used and on Definity R9 or earlier (pre-RFA) or lower, special conditions apply

Contact product management via channel team

• If any Release Call Center is on Definity R10

Tell ASD None for CC and None for Target, do not add agents here

Remove code 212847 from output design

Upgrade from CC R3 to CC R6 in CM 6 upgrade

4.9.

Licensing for Demos, Labs and Trials

• Beta Trials must go through the Beta Trials Program Manager for the specific release;

contact your Avaya Representative else the Program Manager or Product Manager

• For CM and CC Elite, Customer lab systems must be ordered and purchased as per

standard processes; any discounting must go through the Deals Desk

• For CM and CC Elite, Avaya owned Demo equipment on customer premise, or Business

Partner Demo equipment must order the 120 day trial license (m/c 245460) or contact
the Avaya Help Desk to request a 30 day temporary license

• Temporary License Requests:

• Temporary/Emergency licenses up to 30 days do not require product

management or product operations approval. Please call the Helpdesk and
have it flagged as “Business Critical”

• Temporary licenses between 31-90 days with supporting orders such as

upgrades, new, moves or orders with errors/corrections do NOT require product
management or product operations approval. Please call the Helpdesk (Tier 3)
to request a temporary license.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 42 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

• Temporary licenses between 31-90 days without supporting orders will require

review by product manager/product operations and will require business
justification (i.e. business case); Call Helpdesk (Tier 3) first, open case and have
escalated to product operations /product management

Avaya Helpdesk

For the USA, please call 1-866-AVAYA IT (+1-866-282-9248) or 303-354-8999

EMEA users should call +44 1483 309800
Canada and CALA users should call +1 720 444 0130
APAC users should call +65 6872 8700
Germany users should call +49 69 7505 1234

4.10.

ASD Changes

The ASD design tool is modified in two major areas for CM 6.0.1 designs:

1) Added a choice of System Platform solution templates
2) Changed the licensing of Survivable Core and Survivable Remote servers

System Platform Solution Template Choice
The ASD System screen contains three entries for CM 6.0.1 main server templates as
shown below.

Figure 4: Template Choice

Avaya Aura 6.1 Offer Definition

Page 43 of 76

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya In

The three choices map to the following three templates (the other two are Survivable
Remotes):

Definition

COMPAS ID 142680

Avaya Inc. – Proprietary & Confidential.

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

The three choices map to the following three templates (the other two are Survivable

COMPAS ID 142680

Dec 12, 2011

The three choices map to the following three templates (the other two are Survivable

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 44 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

Survivable Core and Survivable Remote Screens
Choose the Survivable Core option on the Location form. If chosen on Standard Edition
there will be a pre-user license code in a quantity equal to the number of CM stations
purchased.

Figure 5: Survivable Core and Survivable Remote

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 45 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

Choose the Survivable Remote option on the following form. If chosen on Standard
Edition there will be a pre-user license code in a quantity equal to the number of CM
stations at the location, not the entire enterprise. Selection of the Survivable Remote
option will automatically include the Session Manager instances needed for SIP
operation for the Survivable Remote configuration. Note it is required to have core
Session Managers installed for proper Survivable Remote SIP operation.

Figure 6: Survivable Remote Option

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 46 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

5. SERVICEABILITY

For the purpose of this document, the Service process starts with customer acceptance
of the product. This occurs after the Provisioning process ends or, for customer-
installed equipment, when the equipment arrives on site. The Service Process ends
when the product is taken out of service or when Avaya no longer supports it.

5.1.

Software Support and Hardware Maintenance

In traditional voice systems, hardware, operating system and features were tightly bonded
– an architecture that resulted in maintenance offers that bundled hardware and software
support into a single combined service. With the advent of IP Telephony and the rapid
migration toward open, “software centric” platforms, customers increasingly want flexible
and straightforward maintenance offers where they can separately choose their desired
level of software and hardware support.

In Avaya’s support structure, software maintenance is available in two offers: Software
Support plus Upgrades (SS+U) and Software Support (SS). Both give customers 24x7
remote technical support for major problems, as well as easy access to all minor releases,
extensive on-line tools and service packs. Software Support plus Upgrades provides the
same entitlements as Software Support, as well as, access to major releases as they
become available. For customers who want to keep their applications on the cutting edge,
Software Support plus Upgrades ensures immediate access to major releases while also
delivering locked-in TCO savings.

Software Support plus Upgrades and Software Support will begin billing on Day 1 for all
applications and for all channels. Time & Material will no longer be available for
software support.

For hardware, there are three simplified offers: Remote Hardware Maintenance, Remote
Hardware Maintenance with Advance Parts Replacement, and On-Site Hardware
Maintenance with a choice of 8x5 or 24x7 Coverage. All offers include Expert Systems

diagnostics and 24x7 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.

Additional information on Software Support and Hardware Maintenance is available at

www.avaya.com

under Services Product & IP Support Product Support Offering

Software Support and Hardware Maintenance.

Available beginning January 2011, Support Advantage becomes the global support
offer for all new Enterprise product sales and product upgrades. It provides 24x7
support for both software and hardware, which helps protect customers’ investments in
enterprise communications from Avaya. The offer has a simple structure with two base
offer choices:
1.

Essential Support (minimum level required)

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 47 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

Preferred Support

More information about Support Advantage can be found at

https://portal.avaya.com/ptlWeb/gs/services/SV0497

5.2.

Service Entitlements for All Customers

Web site-based self-help support for Avaya Session and System Manager is available
to customers on a 7x24 basis at URL

http://www.avaya.com/support/

Web site support includes:
• Frequently Asked Questions (FAQs) and trouble isolation procedures related to

Avaya IP products

• Technical Articles and white papers
• Downloadable firmware upgrades, when applicable
• User Guide information
• Product Documentation
• Product Training

Customers will be asked via the web tools to consult with their other vendors before
creating an on-line service request (e-ticket) or before calling Avaya when
interoperability issues are suspected.

Support beyond the web site's self-help information can be obtained via an on-line
service request (e-ticket) or phone call requests. Non-service agreement customers will
be billed at the Remote Help Desk at prevailing Time and Materials rates. Customers
will be required to provide their credit card number or Avaya account number prior to
services being rendered.

Refer to the warranty contract for the complete terms, conditions, and limitations.

5.3.

Warranty

Software Warranty

Avaya provides a 3 month limited warranty on Session Manager and System Manager
software. Detailed terms and conditions are contained in the sales agreement or other
applicable documentation and establish the terms of the limited warranty.

In addition, Avaya’s standard warranty description and details for support under
warranty are available at the Avaya Support Center under “Additional Information for
Avaya US Warranty Policy”.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 48 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

USWarranty_Policy_

011603.pdf

Hardware Warranty

Avaya provides a one-year limited warranty on the Avaya Session Manager Appliance
hardware. Refer to the sales agreement or other applicable documentation to establish
the terms of the limited warranty. In addition, Avaya’s standard warranty language as
well as details regarding support, while under warranty, is available through the web
site:

http://www.avaya.com/support/

or on the Enterprise Portal at

https://enterpriseportal.avaya.com/ptlWeb/getfile?docID=MzkyNzg3MQ==

Post Warranty Support

Customers may purchase post-warranty software support for the Avaya Session
Manager after the expiration of the initial warranty. The customer may purchase support
coverage in increments of one (1) year with auto-renew upon renewal, with a maximum
contract term of 4 years, limited to 3 years after the product's "last order date." The two
types of Maintenance Service Agreement options are the Self-Maintainer option and
Full Coverage option. The Self Maintainer option includes Remote Support and Parts
plus Remote Support for both 8-5 and 24x7coverage. The Full Coverage option
includes 8-5 and 24x7 coverage in which technician dispatch and Tiers of Support are
included. Applicable uplifts and downlifts are used to determine the appropriate
maintenance price for the offer the customer chooses. These uplifts/downlifts are used
against the default reference rate of 8-5 Full Coverage. If the customer chooses not to
subscribe to post warranty hardware maintenance, then Avaya bills customers for
support on a time and materials basis. Outside the U.S., terms and conditions are
determined locally. See

http://portal.avaya.com/ptlWeb/services/SV0452

for more

details on Software Support and Hardware Maintenance.

Whether maintenance is priced via the Utility-based pricing method, or via the
maintenance simplification methodology, the following coverage option specifics apply.

Table 1: Maintenance Service Agreement Coverage
Offer

Avaya Maintenance Service Agreement Coverage

Parts Plus
Remote

Remote Only

Parts Plus Remote Support includes:

Remote Support (includes Expert Systems remote fault

monitoring on products that support that capability)

Parts Replacement, shipped for next-business day arrival.

Remote Support includes:
Remote Support (includes Expert Systems remote fault monitoring
on products that support that capability

Full Coverage 8-
5, local time:

Full coverage 8-5 includes:

Remote Support (includes Expert Systems remote fault

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 49 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

monitoring on products that support that capability)

On-site Parts Replacement
On-Site Support

Full Coverage
7x24:

Includes all the standard offer, except on a 7X24, 365 basis,
including Avaya holidays

Other Countries
Same as United States, subject to locations where Avaya service is offered. Warranty
on parts is available worldwide, but servicing terms and conditions may vary where
Avaya direct service is not available.

5.4.

Product Correction Notices (PCNs)

Product Correction Notice (PCN) and installation support will be provided to all Avaya
Session Manager and System Manager customers. Customers with warranty and post
warranty coverage will typically receive special consideration for the time and material
charges, if applicable, to a specific product and configuration. PCNs are a function of
the life cycle of the products. PCN installations will take place between the hours of
8am to 5pm (local time), Monday through Friday, excluding Avaya recognized holidays.
Special billing consideration will be given to customers who either have an Avaya
Service Agreement or are under warranty, up to but not exceeding an installation absent
of labor and material charges. The determination of PCN charges, if any, will be
determined on a case-by-case basis by Avaya. Customers who are listed as the
technical contact will typically be mailed a letter regarding the PCN notification.

Avaya U.S. Direct Customers: U.S. Field Service Organization (FSO) technicians will
implement this Change Notice for Avaya U.S. Direct Customers. The Emerging
Technologies Solutions Support (ETSS) group and the FSO Change Notice
Administration Groups will handle scheduling and coordination.

Avaya U.S. BP: Avaya Business Partners who elect to perform the work to implement
this Change Notice will be responsible for scheduling and coordinating their customer
base. Those who elect to have Avaya perform the work will schedule and coordinate
through the Emerging Technologies Solutions Support (ETSS) team.

Avaya International: Scheduling of customers requiring a Change Notice will be handled
through the Emerging Technologies Solutions Support (ETSS) team.

When the need arises for Avaya to replace defective components, Avaya Labs will issue
a Product Correction Notice (PCN). The standard PCN process applies for Session
Manager and System Manager. Some components can be upgraded without the need
for a field dispatch.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 50 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

For a list of active PCNs, go to the Avaya Support Center
(

http://www.avaya.com/support/

) and search under Additional Information for Product

Correction Notices.

NOTE: The Avaya Network Integration Center may support PSN/PCN’s for a fee.
Please contact

proservices@avaya.com

for more information.

5.5.

Product Support Notices (PSNs)

Product Support Notices which replace Service Alerts are issued by Tier 4 Engineers
and/or Product Managers to notify the field of technical workarounds, process
information, or document corrections/clarifications in addition to software/firmware
updates and hardware replacements.

For a list of issued PSNs, go to the Avaya Support Center (

http://avaya.com/support

)

and search under Additional Information for Product Support Notices.

5.6.

Technical Consulting System Support

Avaya provides help line support to U.S. and Canadian business partners and Avaya
sales teams through the normal pre-sales support line (888-297-4700 or 720-444-
7700).

Avaya provides help line/maintenance support to customers that have purchased a Post
Warranty Maintenance agreement during the applicable warranty period through the
phone numbers below. This support includes answering questions regarding Avaya
Aura Session Manager or System Manager software functionality, providing advice to
help customers achieve a working solution, resolving existing system issues and
troubleshooting. They will escalate to the Avaya Aura System/Session Manager Tier 4
teams as needed.

Avaya Contact Telephone Numbers

Elite/Premium Customers

Please refer to your
Avaya Contact
numbers

Global Support Services (GSS)-Enterprise

800–242-2121

Global Support Services (GSS)- Business
Partners for Enterprise Product

877-295-0099

Canada Customer Care Center

800-387-4268

Caribbean and Latin America

786-331-0860

Europe, Middle East, and Africa

36-1238-8334

Asia/Pacific

65-6872-8686

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 51 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

Avaya Professional Services can provide customer specific configuration, programming
and administration support at time and material per incident rates; requests should be
sent to the Network Integration Center at

proservices@avaya.com

. Avaya Professional

Service’s will assist with customer LAN or design issues as well; requests should be
sent to the Advanced Solution Architects at

proservices@avaya.com

Avaya services can also provide customer specific programming and administration
support at time and material per incident rates; customers can call 800-225-7585.
Avaya Service’s assistance does not include help with customer LAN or design issues.

5.7.

Enhanced Services Available

Avaya Professional Services (APS)

APS offers a comprehensive portfolio of professional consulting offers in the areas of
Network Consulting, Contact Center, and Unified Communication. APS is a global
organization, providing professional consulting to customers and business partners in
the US, EMEA, Germany, APAC, CALA, and Japan. More information can be obtained
at

https://enterpriseportal.avaya.com/ptlWeb/internal/spCP/CS200671318355089067

Avaya Operations Services (AOS)

Avaya Operations Services (AOS) offers provide full management services capabilities
to customers allowing them to focus on their core business. Avaya Operations Services
offers vary by region and may include, but are not limited to:

• Single point of contact for system administration and fault management
• General usability help line support
• 8 x 5 local site time maintenance
• Standard service level agreements
• Engagement Manager assigned for the term of the Agreement
• Program management of all communications projects
• Single monthly invoice with multi-level data

Avaya Operations Services are delivered through a combination of AOS associates and
associates from other Avaya services teams. AOS pricing is structured into monthly
recurring charges on a per port basis, plus additional charges for services such as
special projects. More information can be found at

http://outsourcing.avaya.com/

5.8.

Avaya Labs Field Support

The Avaya Labs Field Support organizations (CPE) are responsible for the following
activities:

Provide escalation support for the GSS
Status all GSS (Backbone) escalations
Negotiate with Avaya Labs developers to secure fixes in a time frame

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 52 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

necessary to meet customer expectations

Assist in the development of procedures for product updates and PCN

applications

Issue Modification Requests (MRs) against the application, as required
Function as a Subject Matter Expert to the product extended team, as

necessary

Escalation to Avaya’s development team to work with third party development

partners such as Dell, GE Fanuc, or Red Hat’s Tier IV, etc., when appropriate

Populate NPST Field Support problem / resolution database for use by tiers 2

through 4

Compose Product Support Notices (PSNs) and Product Correction Notices

(PCNs), when applicable

5.9.

PLDS Software Download Policy

Warranty or Post-Warranty Maintenance customers will be entitled to free ETSS support
should they encounter problems with PLDS software downloads during normal Avaya
business hours. Customers (regardless of their PWM structure), who require assistance
during non-business ETSS hours, will be billed at prevailing ETSS out-of-hours rates.

A DVD option is now available for Session Manager and System Manager. The DVD is
now the default option in ASD for Session Manager. Customers may also download the
System Manager and Session Manager Software from PLDS. This software must be
kept at the customer site at all times. During remote/onsite installation, troubleshooting
and disaster recovery scenarios the customer will be asked to provide the Software
downloads. If the software is not on site there may be a delay in support. If the customer
would like the technician to download the software, the project manager for the
customer site must fill out a Change Request Management Form (CMRA), where the
customer will be charged $250.00 per hour for the download. Note: The PLDS
download could take several hours and the customer will be charged for the entire time.
The software can be downloaded from the PLDS website and must be placed on a
DVD. More information on PLDS Software downloads can be found at

www.plds.avaya.com

5.10.

PLDS Licenses

PLDS Support for License Activation and Entitlement Moves will be done through the
NIC team for a fee. Support can be obtained by sending an email to Avaya
Professional Services at

proservices@avaya.com.

More information on PLDS Licenses

can be found at

www.plds.avaya.com

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 53 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

5.11.

Remote Maintenance

Avaya provides support for purchased software and hardware components. Support is
provided under the “Software Support and Hardware Maintenance” support offer and is
priced at normal SSU prices and 15% Hardware Maintenance – 8X5. Business Partners
are also trained to support the hardware and software under the Joint Service Delivery
program.

Please see

http://portal.avaya.com/ptlWeb/services/SV0452

for more information about

these support programs. Avaya requires remote access to provision and support under
the software support maintenance agreement.

Remote Access via Secure Access Link Gateway 1.8

System Manager provides secure, rapid serviceability and Expert Systems alarming
through Secure Access Link (SAL) to Avaya and participating Business Partners. SAL
uses the customer’s existing Internet connectivity to facilitate remote support. All
communication is outbound from the customer’s environment using encapsulated
Hypertext Transfer Protocol Secure (HTTPS). SAL requires upload bandwidth
(customer to Avaya/Partner) of at least 90 KB/s (720 Kbits/s) with latency no greater
than 150 ms (round trip).

A Secure Access Link 1.8 Gateway will be deployed as part of every System Manager
6.1 via System Platform, and subsequently because every Session Manager 6.1 will be
deployed with a System Manager 6.1, all remote access to a customer’s Session
Manager will be via this SAL Gateway.

Additionally, we can expect that as customers currently running Session Manager 1.1
(supported by System Manager 1.0) migrate to System Manager 6.1, they can move off
of the RSIG and inherit the Secure Access Link capabilities afforded them by System
Manager 6.1 on System Platform. Session Manager 5.2 and 6.0 already utilizes SAL for
remote access. Note – All alarming from Session Manager 5.2 and 6.0 will continue to
use the SAL Enterprise components in System Manager and not the alarming
components of the SAL Gateway.

Business Partners without a SAL Concentrator must provide their own IP-based
connectivity (for example, B2B VPN connection) to deliver remote services.

Important: Business Partners and customers must ensure that SAL is always configured
and registered with Avaya during installation. Avaya support will be delayed or not
possible if SAL is improperly implemented or not operational. Modem connections are
not supported.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 54 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

6. DOCUMENTATION

6.1.

Release Notes

Release Notes for Session Manager and System Manager are available at the Avaya
support center at

http://support.avaya.com

. Also see

Product Support Notices

(PCNs).

6.2.

User and System Documentation

In support of the Avaya-wide Go Green initiative, Avaya no longer provides paper and
CD documentation. Avaya online documentation is a free download available from
Avaya Support at

http://www.avaya.com/support

. Click on Find Documentation and

Downloads by Product Name, and under Session Manager, Communication
Manager or System Manager select View all documents.

The following are the documents relating to Session Manager and all have been
updated with new information for R6.1.

Session Manager Documentation

Doc ID

Title

03-603323

Avaya Aura® Session Manager Overview

03-603473

Installing and Configuring Avaya Aura® Session Manager

03-603324

Administering Avaya Aura® Session Manager

03-603479

Administering Avaya Aura® Communication Manager Server Options

03-603478

Avaya Aura® Session Manager Case Studies

03-603325

Maintaining and Troubleshooting Avaya Aura® Session Manager

03-603518

Upgrading Avaya Aura® Session Manager

03-603563

Administering Alarming for Avaya Aura® Components

Installing Service Packs for Avaya Aura® Session Manager

Avaya Aura® Session Manager Security Design

Installing and Upgrading Avaya Aura® System Manager

The following are the new documentation for the new server platforms for Avaya Aura.

Server Platform Documentation

Doc ID

Title

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 55 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

03-603793

Installing the Dell™ PowerEdge™ R610 Server

03-603799

Installing the HP ProLiant DL360 G7 Server

03-603804

Maintaining and Troubleshooting the Dell™ PowerEdge™ R610 Server

03-603803

Maintaining and Troubleshooting the HP ProLiant DL360 G7 Server

The following table shows the Communication Manager documentation library with the
new documents shown in dark blue print.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 56 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

Communication Manager Documentation

Doc ID

Title

03-300468

Avaya Aura® Communication Manager Overview

03-300511

Avaya Aura® Communication Manager Feature Description

03-603558

Installing and Configuring Avaya Aura® Communication Manager

03-603560

Upgrading to Avaya Aura® Communication Manager Release 6.0

03-300509

Administering Avaya Aura® Communication Manager

03-602878

Avaya Aura® Communication Manager Screen Reference

210-100-700 Avaya Extension to Cellular User Guide
555-233-505 Avaya Aura® Communication Manager Reports

03-300430

Maintenance Alarms for Avaya Aura® Communication Manager, Media Gateways and
Servers

03-602793

Avaya Aura® Communication Manager Denial Events

03-300431

Maintenance Commands for Avaya Aura® Communication Manager, Media Gateways
and Servers

03-300432

Maintenance Procedures for Avaya Aura® Communication Manager, Media Gateways
and Servers

03-600759

Avaya Support Notices for Hardware Documentation

555-245-207 Avaya Aura® Communication Manager Hardware Description and Reference

03-300511

Avaya Aura® Communication Manager System Capacities Table

03-601973

Avaya Aura® Communication Manager Security Design

555-025-600 Avaya Toll Fraud Security Guide

03-601818

What’s New in Avaya Aura® Communication Manager, Avaya Servers and Media
Gateways for Release 6.0

03-600843

Application Note: Reference Configuration for Software Duplication

03-300428

Avaya Aura® Communication Manager Survivability Options

03-602798

Avaya Aura® Communication Manager Server Alarms

03-603628

Accessing and Managing Utility Servers

555-245-600 Avaya Application Solutions – IP Telephony Deployment Guide

03-600843

Application Note: Reference Configuration for Software Duplication

03-602884

Converting Avaya Servers and Media Gateways

03-300684

Adding New Hardware for Avaya Servers and Media Gateways

555-233-504 Administering Network Connectivity on Avaya Aura® Communication Manager

03-602804

LED Descriptions for Avaya Aura® Communication Manager Hardware Components

03-602803

Gateway Traps for the G250/G350/G450/G700 Avaya Media Gateways

03-602013

Avaya Aura® Communication Manager SNMP Reference Guide

03-602953

Job Aids for Field Replacements (FRUs) for the Avaya S8510-Series Server

03-603446

Maintaining the Avaya S8800 1U Server for Avaya Aura Communication Manager

03-601703

Authentication File System (AFS) User Guide

03-603444

Installing the Avaya S8800 Server for Avaya Aura Communication Manager

03-603723

Avaya Aura® Communication Manager Change Description for Release 6.0.1

03-603560

Upgrading to Avaya Aura® Communication Manager Release 6.0.1

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 57 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

7. TRAINING

Avaya Aura

Session Manager training is available from the Avaya University website

web-based, hands-on and instructor-led courses are available for complete instruction
on all aspects of these core Avaya products. Courses may be enrolled via the Avaya
Learning Center at:

http://www.avaya-learning.com/logon_form.asp

Please reference the Avaya Learning Center for the most up to date information; an
initial list of courses follows, with the modified or new courses listed in dark blue print.

SIP Courseware

Quick SIP

ATC 01270 WEN

SIP Essentials

ATC 01290 WEN

Communication Manager 6.0 Courseware

CM and System Manager

ATC 01842 OEN

Avaya Aura® 6.0 Feature Server and User Related Admin

ATC 01671 VEN

Avaya Aura® Communication Manager Basic Administration

AVA 00836 H00

Administering and Maintaining Avaya Aura® System Platform (6.0) ATC 00421 VEN

System Platform Installation for CM R6.0

ATI 01445 WEN

Licensing for Avaya Aura® Communication Manager

ATI 01732 WEN

Avaya Aura® Communication Manager Architecture and Features

ATU 01730 WEN

Avaya Aura® Communication Manager Fundamentals

ATI 101672 VEN

Session Manager 6.0 Courseware

Session Manager General Overview

ATU 00171 OEN

Session Manager 6.0 in the Network

ATU 00172 OEN

Session Manager Network Routing Policy Administration

ATI 00176 VEN

Session Manager Technical Overview

ATU 00170 OEN

Session Manager 6.0 Delta: General Overview

ATC 01826 OEN

Session Manager 6.0 Delta: Technical Overview

ATC 01827 OEN

Session Manager 6.0 Installation & Initial Setup

ATC 00173 OEN

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 58 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

Session Manager Rack and Stack

ATC 00175 OEN

Session Manager 6.1 Delta: General Overview

ATU 01515 OEN

Session Manager 6.1 Delta: Technical Overview

ATU 01516 OEN

Session Manager 6.1 Installation & Initial Setup

ATA 02446 OEN

Survivable Remote Session Manager 6.1 Installation &
Initial Setup

ATA 02447 OEN

Session Manager Instance Administration

ATA 01517 VEN

Session Manager, CM and other Feature Server
Administration

ATI 02445 VEN

Survivable Remote Session Manager Administration

ATC 01840 OEN

System Manager 6.0 Courseware

Getting Started with System Manager

ATC 00182

OEN

CM and System Manager

ATC 01842

OEN

System Manager Administering User Profile Accounts

ATC 00184

VEN

System Manager 6.0 General Overview

ATU 00180 OEN

System Manager 6.0 Technical Overview

ATU 00183 OEN

System Manager 6.0 Delta: General Overview

ATC 01825 OEN

System Manager 6.0 Delta: Technical Overview

ATC 01828 OEN

System Manager 6.0 Installation and Setup

ATU 01852 OEN

Advanced System Manager Administration

ATA 02540

VEN

System Manager 6.1 Delta: General Overview

ATU 02643

OEN

System Manager 6.1 Delta: Technical Overview

ATI

02642

OEN

System Manager 6.1 Installation and Setup

ATA 02641

OEN

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 59 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

APPENDIX A: AVAYA AURA PACKAGING

Avaya Aura® Editions
Avaya Aura is easy to purchase and deploy through Avaya Aura Editions: Branch
Edition, Standard Edition and Enterprise Edition. These software Editions bring together
all the functionality needed for common customer situations with a simple per user
licensing fee. Hardware (servers, gateways, and phones) are flexibly purchased in
addition to software licenses and the hardware topology depends on the redundancy,
scalability and geographic distribution needs for each customer. Different elements of
the software may run on separate hardware servers, or some elements may be
combined on the same hardware server. Gateway distribution and configuration will
depend on availability and capacity needs. Avaya and Business Partner sales engineers
assist customers in designing the right hardware configurations to meet their business
needs. The software Editions and their functionality remain the same regardless of
hardware choices.

Avaya Aura® Standard Edition meets the needs of single-site deployments and mid-
to-large distributed enterprises 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, mid-to-very-large
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 licensing, enterprise-wide SIP
session management and Unified Communications applications for all users, including
Microsoft and IBM UC integration, and mobile worker and teleworker support.

All Avaya Aura Editions include appropriate management and administration tools.

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.

How to Order Avaya Aura Editions
To order Avaya Aura Editions today use the existing material codes for Avaya Aura
Communication Manager Standard 6.0, Avaya Aura Communication Manager
Enterprise 6.0 or Avaya Aura Communication Manager Branch 2.0 adding codes for
each entitlement as appropriate to the Avaya Aura package.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 60 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

APPENDIX B: GLOSSARY OF TERMS AND ACRONYMNS

Term

Definition

802.1p/Q

IEEE standard 802.1Q and 802.1p provide the means to specify both a virtual
LAN (VLAN) and a frame priority at layer 2 for use by LAN hubs, or bridges,
which can do routing based on MAC addresses. 802.1p/Q provides for 8 levels
of priority (3 bits) and a large number (12 bits) of VLAN identifiers. The VLAN
identifier at layer 2 permits segregation of traffic to reduce traffic on individual
links. Because 802.1p operates at the MAC layer, its presence may vary from
LAN segment to LAN segment within a single network region. Flexibility requires
that 802.1p/Q options be administered individually for each network interface.

ADC

Asian Distribution Center

ARS

Automatic Route Selection networking software

ASA

Advanced Solution Architect

ASD

Avaya Solution Designer

ASG

Access Security Gateway

BCS

Business Communication Systems

BSR

Best Service Routing

CAMA

Centralized Access Message Accounting

CAC

Call Admission Control

CAS

Channel Associated Signaling

CIRD

Classless Interdomain Routing - CIDR is defined as a redefinition of the subnet
mask, allowing for the aggregation of contiguous classful networks under a
single network definition. This allows for more efficient routing table
management.

CLI

Command Line Interpreter

Central Office

CoE

Center of Excellence, part of GSO

CoK

TSC's College of Knowledge

CSA

Avaya Customer Software Associate

DCP

Digital Communications Protocol

DCS

Distributed Communications System feature of Avaya Communication Manager

DHCP

Dynamic Host Control Protocol

DID

Direct Inward Dial

DiffServ

Differential Services – a method of specifying service requirements for IP
packets at Layer 3. With the DiffServ option the system administrator can
administer (by region) and download to the TN2302AP the DiffServ Type-of-
Service (TOS) value, thus allowing data networking equipment to prioritize the
audio stream at the IP level to promote voice quality. DiffServ makes use of the
Type-of-Service (TOS) octet in the existing IP Version 4 header. As such, it may
be set by information senders and used by IP (layer 3) routers within the
network.

Use of DiffServ and/or 802.1p priorities would typically apply to either or both
ends of a connection: the TN2302AP interfaces should be configured to use the
appropriate values for the network(s) to which they are attached, and the IP
end-points should be configured to use the values appropriate for the network(s)
to which they are connected. In many cases, the communication devices are
“local” and the values are the same; in other cases, the values may be different.
This can be accommodated by downloading default values to the endpoint to be
used in case the endpoint installer or the user has not provided values.

DSO

Data Services Organization

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 61 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

Term

Definition

DSP

Digital Signal Processor

ECLIPS

Enterprise Class IP Solutions

ECS

DEFINITY Enterprise Communication System, refers to release 5 and later

EDC

European Distribution Center

EIS

Enterprise Internetworking Systems, the Avaya business unit that provides and
supports data networking equipment.

ESS

Enterprise Survivable Server

FSO

Avaya Field Services Organization

FTSO

Field Technical Support Organization (formerly known as the FSO and GSO)

Foreign Exchange

GCF

Gatekeeper Confirmation: Avaya Communication Manager sends this to an
endpoint in reply to a GRQ if the registration is proceeding normally.

GES

Global Enterprise System, Avaya's new infrastructure support system, based on
SAP R/3

Gatekeeper

GSIO

Global Services Information Officer group

GSO

Global Support Organization

GTS

Global Technical Services (formerly the RTS and TSO)

GUI

Graphical User Interface

GULLF

Graphical User interface Look, Listen, and Feel

IST

Implementation Support Team

H.225.0

Call signaling protocols and media stream packetization for
packet-based multimedia (includes Q.931 and RAS)

H.225.0
Annex G

Gatekeeper to gatekeeper (inter-domain) communications

H.235

Security and encryption for H-series multimedia terminals

H.245

Control protocol for multimedia communications

H.323
Annex D

Real-time fax using T.38

H.323
Annex E

Call connection over UDP

H.323
Annex F

Single-use device

H.323 V2

Packet-based multimedia communications systems

H.450.x

Supplementary services for multimedia.
Generic functional protocol for the support of supplementary services in H.323
2. Call transfer
3. Diversion
4. Hold
5. Park & pickup
6. Call waiting
7. Message waiting indication

Internet Protocol, part of the TCP/IP protocol stack

ISDN

Integrated Services Digital Network

Information Technology

ITAC

International Technical Assistance Center, part of GSO

JTAPI

Java Telephony Application Programming Interface The JTAPI standard is fully
supported by Avaya’s CentreVu Computer Telephony. The Java Telephony API
(JTAPI) is a portable, object-oriented Application Programming Interface for

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 62 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

Term

Definition

Java-based computer-telephony applications. JTAPI serves a broad audience,
from call center application developers to Web page designers. JTAPI supports
both first-party and third party CTI application needs.

LAN

Local Area Network

LDAP

Lightweight Directory Access Protocol

LSP

Local Survivable Processor

MACS

Multimedia Applications Customer Support, a NetCare Data Professional
Services group

MAPD

Multi-Application Platform — DEFINITY

Megabytes of memory or hard disk space

Media Controller

MGCP

Media Gateway Control Protocol

MNC

Customers designated as Multinational Customers

NAT

Network Address Translation, used with Virtual Private Networks

NIC

Avaya Network Integration Center

Microsoft New Technology Operating System

OSSI

Operations Support System Interface, a batch-oriented DEFINITY protocol

PCMCIA

Personal Computer Memory Card International Association

PEC

Price Element Code

PLDS

Product Licensing and Distribution System – the Avaya website tools used to
download licensing and software for Avaya products.

PNA

Private Network Access networking software

PRI

Primary Rate ISDN trunk

PSO

Professional Services Organization

PSTN

Public Switched Telephone Network

RAID

Redundant Array of Inexpensive Disks

RAS

Registration, Authentication, and Status: the overall process of establishing
communication between an endpoint and a switch, in the H.323 protocol.

RSIG

Remote Secure Intelligent Gateway

SAL

Secure Access Link

SAP

This isn’t an acronym, but rather the name of the company that sold an ordering
and tracking system to Avaya.

SAT

DEFINITY System Access Terminal, replaced by DSA at customer sites

SGCP

Simple Gateway Control Protocol

Streamlined Implementation process

SIP

Session Initiation Protocol

SNMP

Simple Network Management Protocol

SPC

Avaya Services Product Connect, which links the RTS / GSO to customer
products via IP

SPE

Service Price Element; associated with time and materials billing

SSP

DEFINITY Size Sensitive Ports

T&M

Time and materials billing

T.38

Procedures for real-time group 3 facsimile communications over IP Networks

TAC

In-country Avaya Technical Assistance Center

TCP

Transmission Control Protocol is a reliable end-to-end transport-level protocol
which provides error detection and correction, flow control, and sequencing; the
Internet standard reliable transport protocol

TFTP

Trivial File Transfer Protocol

TIEU

Technical Instructor - End User

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 63 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

Term

Definition

TSAPI

Telephony Services Application Programming Interface. TSAPI also is a key
integration for Outbound Call Management enabling call generation based on
data base prompts.

TSC

Technical Service Center

TSC-SS

Technical Service Center Support System, replaced by Maestro

UDP

Uniform Dial Plan

UDP

User Datagram Protocol, a connectionless protocol that, like TCP, runs on top of
IP networks. Unlike TCP/IP, UDP/IP provides very few error recovery services,
offering instead a direct way to send and receive datagrams over an IP network.
It's used primarily for broadcasting messages over a network in real time.

VLSM

VLSM is defined as a redefinition of the subnet mask, allowing for a more
efficient allocation of IP addresses within a traditional classful block. During
administration, the user will input a Network Bits value between 1-30 on the ip-
route form which will correspond to a particular subnet mask.

VNMA

Voice Network Management Assist offer, previously known as Qualnet

VPN

Virtual Private Network

WAN

Wide Area Network

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 64 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

APPENDIX C: Release History Lifecycle Dates

This table shows the End of Sale and End of Manufacturer supports dates for the various
versions of Avaya Communication Manager and its predecessors. For the lifecycle dates for
supporting hardware and servers refer to the respective hardware product definitions and
lifecycle announcements.

Release Version

Launch Date

End of Sale

Date

End of

Manufacturer

Support Date

Additions

Still

Allowed?*

G3V2

January, 1994

June 7, 2004

G3V3

March 1995

June 7, 2004

G3V4

June 1997

June 7, 2004

ECS R5

November
1997

March 7, 2005

ECS R6

February 1999

March 7, 2005

ECS R7

June 2000

March 7, 2005

ECS R8

March 2001

March 7, 2005

ECS R9

March 2002

March 7, 2005

Yes

R10

July 2002

March 7, 2005

Yes

Communication
Manager 1.x

June 5, 2002

February 8,
2004

January 15, 2006
November 5, 2007
(for the DEFINITY
Server R only)

Yes

Communication
Manager 2.x

December 8,
2003

December 5,
2005

October 10, 2007
December 15,
2008 (for the
DEFINITY Server SI
only)

Yes

Communication
Manager 3.x

June 13, 2005

December 31,
2007

December 31,
2008

Yes

Communication
Manager 4.x

March 19, 2007

February 2,
2009

February 2, 2010

Yes

Communication
Manager 5.x

January 7, 2008

November 7,
2011

November 7, 2012

Yes

Communication
Manager 6.x

June 7, 2010

tbd

Yes

*Additions means adding additional users, features, or components such as an LSP or ESS.
See Appendix D: Additions to CM4 and Earlier Systems for more details.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 65 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

APPENDIX D: Additions to Communication Manager 4.0 and
Earlier Systems

Features and capacity can still be added to older DEFINITY systems and up through Avaya™
Communication Manager 4.x release. The document that outlines the material codes,
pricing and policies for additions to these older systems can be found at the Avaya
Enterprise Portal-> Product-> Products A-Z-> Communication Manager-> Sales Collateral-
> Jobs Aids and Tools (under Tools) -> Appendix D Additions to CM4 and Earlier systems

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 66 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

APPENDIX E: Software Re-licensing Policy

A full description of Avaya's licensing policy and approach to re-licensing for Avaya
Communication Manager can be found at the Avaya Enterprise Portal-> Product-> Products
A-Z-> Communication Manager-> Sales Collateral-> Jobs Aids and Tools (under Tools) ->
Appendix E software relicensing.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 67 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

APPENDIX F: Selected Communication Manager Features
and Related Products

A detailed description of selected Communication Manager feature and related applications
can be found at the Avaya Enterprise Portal-> Product-> Products A-Z-> Communication
Manager-> Sales Collateral-> Jobs Aids and Tools (under Tools) -> Appendix F: Selected
Communication Manager Features and Related products.

For a complete list of the history of changes between Communication Manager Release 1.1
through 5.x, please go to the Avaya Enterprise Portal-> Products ->Products A-Z->
Communication Manager-> Release History.

To obtain official documentation covering all Communication Manager features, refer to the
above Documentation section of this product definition.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 68 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

APPENDIX G: Migration and Merge Offers

As a customer’s needs change, Communication Manager servers can be replaced with
higher-capacity versions and also several servers can merged into one larger system.
Detailed information on License Migrations & Merges is available at the Avaya Enterprise
Portal-> Product-> Products A-Z-> Communication Manager-> Sales Collateral-> Jobs Aids
and Tools (under Tools) -> Appendix G license merge and migration.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 69 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

APPENDIX H: License Moves

As of the release of Avaya Aura 6.0, APPENDIX H: License Moves document is no longer
required. License moves are now part of the Global License Portability (GLP) Process and
found under GLP project Documentation in Business Tools & Processes -> Software
Licensing & Fulfillment -> License Portability
http://portal.avaya.com/ptlWeb/so/CS2010105203323127038.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 70 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

APPENDIX I: Survivable Remote and ICC Conversion

The process to convert an S8300 or S8500 ICC to Survivable Remote or vice versa is
detailed at the Avaya Enterprise Portal-> Product-> Products A-Z-> Communication
Manager-> Sales Collateral-> Jobs Aids and Tools (under Tools) -> Appendix I ICC and
Survivable Remote conversion.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 71 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

APPENDIX J: Moving Survivable Remote and Survivable
Core Servers

The process to move S8300 and S8500 Survivable Remote and Survivable Core servers
between main servers is detailed at the Avaya Enterprise Portal-> Product-> Products A-Z-
> Communication Manager-> Sales Collateral-> Jobs Aids and Tools (under Tools) ->
Appendix J moving Survivable Remote and Survivable Core Servers.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 72 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

APPENDIX K: Upgrade Protection Plan for Communication
Manager 4.0

The Upgrade Protection Plan for Communication Manager (UPPCM) is no longer available.
With release 5.0 and later, UPPCM has been replaced with Software Support plus Upgrades
(SS+U).

This appendix is no longer provided or updated.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 73 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

APPENDIX L: Survivable Core Conversions

The process to convert an S8300 or S8500 Survivable Core to Main Server or vice versa is
detailed at the Avaya Enterprise Portal-> Product-> Products A-Z-> Communication
Manager-> Sales Collateral-> Jobs Aids and Tools (under Tools) -> Appendix L Survivable
Core Conversions.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 74 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

APPENDIX M: RFA Licensed Features

This appendix shows screen representations of the SAT system parameters customer-
options form showing the licensed features that are available through Communication
Manager software, and is available at the Avaya Enterprise Portal-> Product-> Products A-
Z-> Communication Manager-> Sales Collateral-> Jobs Aids and Tools (under Tools) ->
Appendix M RFA Licensed Features.

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 75 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

APPENDIX N: STANDARDS SUPPORTED

RECOMMENDATION

SUPPORT

G.711

G.726

Y (note 1)

G.728

Y (note 1)

G.729

Y (note 1)

G.729a

Y (note 1)

G.722

Y (note 1)

RFC 3261

RFC 3263

802.1p

802.1q

SNMP

FAX - Group 3

FAX - Group 4

T.37

T.38

IP Precedence

Differentiated Services

Weighted Fair Queuing

NA (will use routers)

CBWFQ

PQWFQ

-RED

Weighted RED

RTP

CRTP

RTCP

RTSP

Policy Based Routing

Committed Access Rate

IPv6

TCP/IP

UDP/IP

DHCP

TLS

Notes:
1: While many Avaya Aura

components support these codecs, MM does not support G.729,

G.726, G.728, G.729a or G.722

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 76 of 76 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

CONTACT INFORMATION

NOTE: If you have questions regarding the Avaya Aura Solution, please contact ATAC at 888-297-4700
or 720-444-7700 (Hours of operation: 9 am EST – 8 pm EST) before contacting the responsible Product
Manager(s) below.

Product Management Contacts

Product

Contact

Email

Avaya Aura®

Avaya Aura®

Donna Logan

dmlogan@avaya.com

Avaya Aura®
Session Manager

Stephen Durney

srd@avaya.com

Avaya Aura®
System Manager

John Cato

jcato@avaya.com

Avaya Aura®
SIP Enablement Services

Conrad Uniacke

cuniacke@avaya.com

Avaya Aura®
Presence Services

Stephen Durney

srd@avaya.com

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

Cathy Smyth

csmyth@avaya.com

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

Henry Wright

hlwright@avaya.com

Avaya Aura®
Communication Manager

Conrad Uniacke

cuniacke@avaya.com

Avaya Aura®
Communication Manager
Messaging

Mike Wasserburger

wasserburger@avaya.com

Avaya Aura®
Conferencing

Matt O’Donnell

odonnell@avaya.com

Avaya Aura® Messaging

Rudi Potze

rpotze@avaya.com

Avaya Aura® Session
Border Controller

Michael Dews

mdews@avaya.com

Avaya Aura 6.1 Offer Definition

COMPAS ID 142680

Page 77 of 77 Avaya Inc. – Proprietary & Confidential. Dec 12, 2011

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

Product

Contact

Email

Related Products & Solutions

Agile Communication
Environment

Paul Rowe

rowep@avaya.com

Avaya Integrated
Management

Mike Killeen

killeen@avaya.com

Avaya one-X® – UC All
Inclusive

Praveen Mamnani

pmamnani@avaya.com

Branch Media Gateways

Bruce Lieou

blieou@avaya.com

Call Center

Bill Jolicoeur

bjolicoeur@avaya.com

G860 Gateway

Bruce Lieou

blieou@avaya.com

Intelligent Customer
Routing

Jason Hostetter

mailto:

contactj@avaya.com

Meeting Exchange

Matt O’Donnell

odonnell@avaya.com

one-X® Agent

Michael Harwell

mhharwell@avaya.com

one-X® Mobile, one-X®
Portal, EC500

Julie Thiesen

julie@avaya.com

one-X® Communicator,
Softphone clients

Praveen Mamnani

pmamnani@avaya.com

one-X® Deskphone SIP
for 9600-series phones

Thomas Petsche

petsche@avaya.com

one-X® Deskphone Value
Edition SIP for 1603 phone

Eric Koob

koob@avaya.com

Solutions for Midsize
Enterprises

David Dubois

dadubois@avaya.com

Software Support and Hardware Maintenance

Extended Manufacturers
Software Support Policy

Jan Leistikow

jleistikow@avaya.com

All trademarks identified by the ® or

are registered trademarks or

trademarks, respectively, of Avaya Inc. All other trademarks are the property of

their respective owners.

Wyszukiwarka

Podobne podstrony:
generator sinus, rev1 Dolna
OCIMF HVPQ 2009 (newest) Rev1 02Jun09
AvayaAura6 2ProductDefMarch2
new SG1011 rev1
f4 sensor properties rev1 id 16 Nieznany
miernik uipt rev1 1 top mirror
generator sinus, rev1 F SilkS
miernik rev1 1 transfer
biomechanika 3 sem 1 rev1-wersja 2003, fizjoterapia dokumenty, wseit sem 3
AvayaAura CommunicationManagerSpecialApplicationFeatures
miernik uipt rev1 1 bottom nonmirror
generator sinus, rev1 Dolna
C240 REV1 4(061106)
Notes on the downloads rev1
Sony ST26 ST26a ST26i Xperia J Test and Calibration electrical rev1
SGH E810 LCD REV1[1] 9
Orlik PBJ 1H B 25J Wheels Rev1
INSTZ G9 G9E PLUS UK 2016 Rev1

więcej podobnych podstron