Avaya Aura 5.2.1 Channel Announcement

Avaya Aura 5.2.1 Channel Announcement
Sep 2010 Launch
Avaya Aura™ Messaging 6.0
Offer Announcement
Global Sales, Distributors
and Partners
Date issued: Sep 30, 2010
Summary.........................................................................................................................2
Availability .......................................................................................................................2
Introducing Avaya Aura™ Messaging 6.0........................................................................ 3
Avaya Aura™ Messaging Server Models and Capacities ................................................ 5
Related Products and Solutions - Servers ....................................................................... 6
Avaya S8800 Server ....................................................................................................6
Ordering Avaya Aura™ Messaging 6.0 .................................................................... 7
Pricing Structure..............................................................................................................9
Avaya Aura™ Messaging 6.0 Pricing ........................................................................... 9
Software Support and Hardware Maintenance .............................................................. 10
Software Support ....................................................................................................... 10
Hardware Maintenance .............................................................................................. 10
Additional Resources .................................................................................................... 10
Product Management Contacts.................................................................................. 10
Naming Conventions ................................................................................................. 11
Summary
This announcement covers Avaya Aura™ Messaging 6.0 and is a detailed follow-up to the announcement
from the July launch. The document is being distributed to Avaya Global Sales and Distributors on
September 30th, and AvayaConnect Partners on September 30th.
This document provides a summary of Avaya Aura™ Messaging 6.0 features and capabilities along with
pricing and ordering information. The information provided in this announcement is intentionally kept at a
high level and is in no way a substitute for thoroughly reviewing the product definition or product
documentation.
For more information please visit http://portal.avaya.com/ptlWeb/products/P0792/ProdOverview for Avaya
Aura™ Messaging.
Availability
Avaya Aura Messaging will be available (general availability) on September 30, 2010.
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. Pricing may vary by Theater and country. Please check with your local pricing
contacts.
2
Avaya – Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.
Introducing Avaya Aura™ Messaging 6.0
Avaya Aura™ Messaging 6.0 is Avaya’s next generation messaging product that is flexible, scalable,
resilient and easy to deploy on standard Linux-based servers, while providing end users with familiar and
new features.
The following is a summary describing key aspects of the product.
End User Features
Messaging 6.0 includes the Octel® Aria features that are still relevant in today’s world, maintaining the
familiar menu structure to smooth user transition. In addition, it provides voice recognition for addressing
messages, IMAP access to voice messages, a clientless Outlook toolbar, a browser application for
managing user settings, and Reach Me and Notify Me features.
Basic Speech Auto Attendant
Messaging 6.0 includes a basic speech auto attendant, allowing callers to reach users listed in the auto
attendant directory by saying their name instead of entering an extension. The speech-enabled auto
attendant requires an additional seat license for each name listed in the auto attendant’s directory.
(A standard, keypad based auto attendant is available without requiring additional licenses.)
Flexible
The flexible architecture of Avaya Aura™ Messaging is designed to fit a wide variety of customer
environments – from centralized to decentralized, from unified (integrated with an existing email system
and directory – in future release) to stand-alone (Avaya Message Store – in current release).
Furthermore, it has the flexibility to adapt over time when those environments evolve – in response to
growth, centralization, or increasing High Availability/Disaster Recovery (HA/DR) demands.
Scalable
Avaya Aura™ Messaging is a scalable solution ranging from an easy-to-deploy single server (with
application and storage roles combined on a single virtual server) to a fully scalable front-end/back-end
configuration with dedicated application servers and storage servers.
Resilient
The Avaya Aura™ Messaging architecture provides a range of High Availability/Disaster Recovery
(HA/DR) options – ranging from an N+1 configuration for application servers to locally survivable
application servers that can stay fully operational with locally cached messages and greetings.
Back-End Integration
Avaya Aura™ Messaging introduces the AxC “connector” concept that is designed to enable multiple,
independent integrations with existing enterprise applications. Messaging 6.0 contains the stand-alone
Avaya Message Store (with built-in directory), and includes the corresponding AxC connector for that
store.
As an additional capability, an AxC connector for Exchange and Active Directory will be made available in
a future update. This capability will allow the Messaging application servers to work seamlessly with
Exchange and Active Directory.
Telephony Integration
Messaging 6.0 supports SIP for telephony integration and is certified with Avaya Aura™ Session
Manager, Session Enablement Services (SES) 5.2.1, and Communication Manager (single application
3
Avaya – Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.
server integration only; multiple application server integration certification pending). Avaya
Communication Server 1000 certification is pending. For use with other PBXs, Messaging 6.0 requires
the AudioCodes Mediant 1000 Media Gateway.
Migration and Upgrade Paths
Messaging 6.0 allows a direct migration from Octel Aria systems with optional preservation of key user
data from existing systems. This migration facility will be made available post-GA.
It will not be possible to perform a direct upgrade from Modular Messaging to Avaya Aura™ Messaging
6.0 – this capability is planned for a later release.
Localized Versions
Avaya Aura™ Messaging 6.0 will initially be available in the following localized versions:
• US English
• Brazilian Portuguese
• Canadian French TUI (with French GUI)
• German
• Latin American Spanish
• UK English TUI (with US English GUI)
4
Avaya – Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.
Avaya Aura™ Messaging Server Models and Capacities
Server Models
Two server models are available:
•
A standard server (material code: 244937 MSG S8800 LO CPU/RAM/HDD):
serves as either:
application + storage server (=single server),
application only server, or
storage only server.
•
A high capacity storage server (material code: 244938 MSG S8800 LO CPU/RAM HI HDD):
serves as a storage only server to support a large number of mailboxes.
All server roles (application only, storage only, or single server combining both roles) are handled by the
same Linux based Messaging server running as a single virtual server on top of Avaya’s System Platform.
Capacity Examples
Server
Role→
Application + Storage
(Single Server)
Application Only
(dedicated application
server)
Storage Only
(dedicated storage server)
100 ports =
6,200 users
@ 62 users/port
100 ports =
6,200 users
@ 62 users/port
8,000 mailboxes
@ 20 mins*/mailbox (G.711)
8,000 mailboxes
@ 20 mins*/mailbox (G.711)
For a single site, up to 3
application servers can
be clustered for a max
port size of 300 ports.
Hardware↓
244937
Standard
Server
5,500 mailboxes
@ 30 mins/mailbox (G.711)
5,500 mailboxes
@ 30 mins/mailbox (G.711)
An additional application
server can be added to a
cluster for N+1
redundancy – as long as
active traffic is not
exceeding 300 ports.
244938
High
Capacity
Storage
Server
Same as above.
(Not typical use – this
configuration can be used if
this server is expected to
become a dedicated storage
only server in the future.)
Not applicable.
20,000 mailboxes
@ 20 mins*/mailbox (G.711)
13,500 mailboxes
@ 30 mins/mailbox (G.711)
*Capacities are based on default values in Avaya Solution Designer (ASD) except where noted with an
asterisk. To change the default value for capacity calculations in ASD, edit the values in the Advanced
screen.
5
Avaya – Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.
Related Products and Solutions - Servers
Avaya S8800 Server
The Avaya S8800 series common server was introduced in the fall of 2009. The S8800 is a powerful and
reliable processing platform that is ready to support Avaya Aura™ communications solutions today and in
the future. The Avaya S8800 Server leverages Intel’s latest Xeon E5500 series (Nehalem) processor
technology, and is available in both 1U and 2U form factors. Most Avaya applications will use the S8800
1U server chassis; some applications that require a large number of hard disk drives and / or plug-in
cards will use the 2U version of Avaya S8800 Server.
The Avaya S8800 Server is sold in a variety of configurations to suit the specific processor, hard drive
and memory needs of each application.
Avaya S8800 Server Configurations
Adopting Application
Size
Processor (Intel Xeon
Quad Core Nehalem)
# of
CPUs
Dynamic
RAM
Hard Disk
Drive
Messaging (new)
1U
5520 2.26 GHz
1
12 GB
3-4 x 146 GB
one-X® Speech
2U
5520 2.26 GHz
1
4 GB
2 x 146 GB
Avaya S8800 Server Migration Kits
Note that Avaya Aura Messaging 6.0 is not intended as an upgrade from Modular Messaging 5.x.
However, for those customers that do wish to migrate and re-use existing MM S8800 MAS or MSS
servers for Avaya Aura Messaging 6.0, the following hardware kits are available:
Material
Code
Description
232320
S8800 MIGRATION KIT
229260
S8800 MSS MIGRATION KIT
Notes
Upgrades S8800 MM MAS to
MSG S8800 LO CPU/RAM/HDD
("standard server")
Upgrades existing S8800 MM MSS to
MSG S8800 LO CPU/RAM HI HDD
("high capacity storage server")
NPL
$1,600
$1,600
An MM 5.x S8800 “single server” can be used for Avaya Aura Messaging 6.0 without hardware migration.
(Note: The ASD configurator currently does not provide an option to specify that existing servers will be
used – instead, manually remove the server from the order, and add the appropriate migration kit
instead.)
6
Avaya – Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.
Ordering Avaya Aura™ Messaging 6.0
The Avaya Aura™ Messaging 6.0 ASD Configurator is available. A password will be required for a short
period of time – please contact Product Management for details.
ASD for Avaya Aura Messaging is location based. It requires at a minimum the following input per
location:
Avaya Aura Messaging screen:
• Location type, defining the role of the hardware for the location:
o Application Only (dedicated server for application role)
o Storage Only (dedicated server for storage role)
o Application and Storage (Front and Back End) - this is a configuration with dedicated
servers for application and storage respectively, with both servers in the same physical
location
o Application and Storage (Single) – this is the single server configuration
• Number of users for each location with an application role:
o ASD will ask for both users and future users.
o The sum total of both will be used to determine the hardware (port capacity) needed.
o Only the number of users the system will be used to order seat licenses.
• Number of mailboxes for each location with a storage role:
o ASD will ask for both mailboxes and future mailboxes - the sum total of both will be
used to determine the hardware needed
o The split between mailboxes and future mailbox is done for information and validation
purposes only – the number of seat licenses will be based on the number of users, not
mailboxes.
o (Note that a single Messaging system can only contain one server with a storage role – if
more storage is required, two systems can be ordered and use voicemail networking.)
• For a new system, the number of mailboxes and the number of users across all locations should
match.
About users and mailboxes
Users is used to determine application (telephony) related capacity (in other words, the number of ports
required and thus the number of servers required).
Mailboxes is used to determine storage related capacity (hard disk space).
Note that in an entire system the number of users equals the number of mailboxes. However, since some
locations are "application only" and some locations are "storage only", the ASD questions need to
differentiate between users and mailboxes for each location.
Other options in ASD:
Avaya Aura Messaging screen:
• Speech AA (licensed option):
Determine the number of entries (users and caller applications) at this location that are to be
listed in a speech based Auto Attendant directory. Divide this number by 100 and round up – this
gives the quantity of licenses required.
• Redundancy:
Select N+1 Application Redundancy to add a redundant application server for this location.
7
Avaya – Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.
Only applies to the following location types: Application Only and Application and Storage (Front
and Back End) since these location types have dedicated application servers.
Advanced screen:
The ASD configurator determines the required server types and number based on default assumptions
for:
the storage role:
• required storage (persistent storage in the message store) per user/mailbox
• the used codec for storage and local caching
the application role:
• users per port
• required local caching (local cache in application servers, if applicable) per user
• the used codec for storage and local caching.
The default values for these assumptions are shown in the Advanced screen, and can be altered if
needed.
one-X Speech screen:
one-X Speech seat licenses are an entitlement – on a 1:1 basis for Messaging mailbox seat licenses.
Adding one-X Speech will add the required one-X Speech server to the configuration and generate the
appropriate seat licenses.
SWIN Gateway screen:
For third-party (AudioCodes) gateway – optional for each location. The gateway capacity is determined
based on the entered user quantity.
Speech To Text screen:
Reserved for future use – the Speech to text (or Text conversion) feature will be made available post-GA.
8
Avaya – Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.
Pricing Structure
Avaya Aura™ Messaging 6.0 Pricing
The following table provides a list of Avaya Aura Messaging 6.0 introductory pricing as of the date of
issue of this announcement.
SAP Code
SAP MATERIAL
DESCRIPTION
Notes
GPL
SERVERS
244937
MSG S8800 LO
CPU/RAM/HDD
standard server
244938
MSG S8800 LO
CPU/RAM HI HDD
high storage capacity server
244929
MSG R6.X 1 SEAT
MAINSTRM NEW
seat purchased as part of new system
$46
244933
MSG R6.X 1 SEAT
MAINSTRM MMIP
seat purchased with "migration incentive" pricing
$23
244926
MSG R6.X 100 SEAT
SPEECH AA ENTRY
for 100 entries in Basic Speech Auto Attendant
directory
232320
S8800 MIGRATION KIT
Upgrades S8800 MM MAS to MSG S8800 LO
CPU/RAM/HDD ("standard server")
229260
S8800 MSS MIGRATION
KIT
$7,895
$10,095
SEATS
$150
SERVER
UPGRADE KIT
Upgrades existing S8800 MM MSS to MSG S8800
LO CPU/RAM HI HDD ("high capacity storage
server")
9
Avaya – Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.
$1,600
$1,600
Software Support and Hardware Maintenance
Software Support
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.
Beginning December 2006, Avaya introduced unbundled software and hardware maintenance offers for
most major products. In the new structure, software maintenance is available in two offers: Software
Support plus Upgrades (SS+U) and Software Support (SW Support). Both provide customers 24 x 7
remote technical support for major problems, as well as easy access to all minor releases, extensive online 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 Total Cost of Ownership (TCO) savings.
Software Support plus Upgrades and Software Support will begin billing on Day 1 for all applications and
for all channels. Time & Materials (T&M) is no longer available for Software Support Coverage.
Hardware Maintenance
For hardware, there are three (3) simplified offers: Remote Hardware Maintenance, Remote Hardware
Maintenance with Advance Parts Replacement, and On-Site Hardware Maintenance with a choice of
SM
8 x 5 or 24 x 7 Coverage. All offers include Expert Systems diagnostics and 24 x 7 remote technical
support. The Advance Parts and On-Site offers also include equipment replacement. Customers
requiring fully comprehensive monitoring will want to combine SS+U with any of the Hardware
Maintenance offers.
Complete details on Software Support and Hardware Maintenance are available at
http://portal.avaya.com/ under Services / Product & IP Support / Product Support / Offering / Software
Support and Hardware Maintenance.
Additional Resources
Product Management Contacts
Product
Contact
Email
Avaya Aura™
Avaya Aura™ Messaging
Rudi Potze
rpotze@avaya.com
10
Avaya – Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.
Naming Conventions
Full proper name for
standalone or initial use
where context is not
already established
Avaya Aura™ Messaging
(NEW)
Follow-on and common usage when
context has been established. Unless
shown, “Avaya” cannot be a prefix here.
Messaging
Abbrev. – only to be used in PP /
diagrams
Msg
© 2010 Avaya Inc. All rights reserved. All trademarks identified by the ® or TM are registered trademarks or
trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners.
11
Avaya – Proprietary & Confidential. Use pursuant to the terms of your signed agreement or Avaya policy.
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising