IAUG Eastern Connect
Avaya Aura Messaging
Vic Kingrey
Solutions Architect – Business Communications Solutions Group
[email protected]
Overview of Avaya Aura Messaging 6.1
Avaya Aura Messaging allows for flexible, centralized and redundant deployments of Unified Messaging,
meeting the needs of legacy installed base and green-field opportunities, while bringing new productivity
enabling features to market.
Release 6.1 delivers:
• Flexible, per-user storage options for increased compatibility, competitiveness, and market differentiation
- Exchange 2007/2010
- Zimbra 7
• Basic/Mainstream mailbox licensing schema for flexibility in matching mailbox price with functionality needs.
- Improves mailbox price-point competitiveness in marketplace
• Audix TUI emulation and data migration utility provides evolutionary path for ~20M seat installed base
• External Directory (AD) data-sourcing for reduced implementation /administrative effort
- when using Exchange storage only (one-way)
• Native Inbound Fax support and other fax improvements
• Expanded interoperability with CS 1000 broadens product reach in portfolio
• Additional E.164 mailbox support for flexibility in customer numbering plans
• Quality improvements for field/lab found issues
• Audio branding
Release 6.1 increases competitiveness and enables evolutionary migration opportunity from our
2nd largest installed base, Intuity Audix.
Avaya – Proprietary. Use pursuant to Avaya policy.
2
Avaya Aura Messaging
►100 % Linux solution
•No Windows Updates
•No Patch Tuesday
►Flexible per-user Message Store
•MMS, Exchange, Zimbra
►Greater per-user Telephony User Interface (TUI)
•Retaining User Interface
•Octel Aria like & Intuity Audix like
►Basic Embedded Speech Auto Attendant
•No Supplementary Servers
►Native Inbound Fax
►Active Directory synchronization
(for Exchange store only)
►Basic / Full Mailbox licensing
► Outlook form support
(no desktop plug-in required)
•IMAP4
•Play on Phone
•Play on PC
•Voice Forward
•Voice Reply
•Call Sender
►New & Improved Web Subscriber Options
•Reach Me
•Notify Me
•My Phone
•Personal Lists
►Single Server or multi-server deployments as
needed for scale and availability
►Improved Locally Survivable options and
Disaster recovery with remote application
servers
•N+1 Application Server Support
Avaya – Proprietary. Use pursuant to Avaya policy.
3
Facilitate Migration For Intuity Systems
 New capabilities improve end user
productivity
 Near identical TUIs and features means no
retraining
 Centralization lowers operating costs
 Single server option lowers capital and
support costs
 Tools enable transparent data/mailbox
migration
 Fully supported system ensures investment
protection
 Migration programs ease transition costs
Avaya – Proprietary. Use pursuant to Avaya policy.
4
Clientless Outlook Toolbar
 Eliminates PC software distribution and management
 No user installation
 No media player required
 Simplifies message manipulation
Outlook 2007/2010
Avaya – Proprietary. Use pursuant to Avaya policy.
5
Fax Support
 3rd party fax server or
 Native inbound fax support
– Detect and forward fax to user email address
– Administrator can choose system wide TIFF or PDF format
Incoming Fax
Messaging
Application
Or
3rd Party
Fax
Server
Avaya – Proprietary. Use pursuant to Avaya policy.
6
Simplified Mobile Access
With Avaya one-X® Mobile
 Visual voicemail
 Call logs
 Corporate directory
Available on
 iPhone
 Android
 BlackBerry
 Windows 7
Avaya – Proprietary. Use pursuant to Avaya policy.
7
Telephone User Interface (TUI)
 Octel Aria and Intuity Audix TUI
 Configured on a per user basis
 Addresses large portion of Avaya installed base
 Aria-like TUI in use by most mobile phone companies
– Provides similar experience for end users with mobile
devices
Press 1 to
hear voice
messages,
press 2 …
Avaya – Proprietary. Use pursuant to Avaya policy.
8
Mobility
 Reach Me
 Notify Me
 one-X Speech
 Benefits
– Improve reach and availability
– Increase awareness
– Hands free message manipulation
Avaya – Proprietary. Use pursuant to Avaya policy.
9
User Self Administration
 Web based access
 Manage personal info,
password, message
playback options, and
more
 Configure Reach Me
and Notify Me
Satisfied users with reduced IT demands
Avaya – Proprietary. Use pursuant to Avaya policy.
10
Reach Me
 Configurable through
web portal
 Sequential ringing of up
to 3 numbers
 Time of day routing
 Call screening
Users control their availability
Avaya – Proprietary. Use pursuant to Avaya policy.
11
Notify Me
 Always know if a message is waiting
 Configurable through web portal
 Notification by
– Text message
– Out-calling
– Email
Avaya – Proprietary. Use pursuant to Avaya policy.
12
Speech Enable Yourself!
 Hands free
Make a
call
 Eyes free
 Any voice capable
device
Read
email
Send a
message
Avaya
one-X®
Speech
View or
change
calenda
r
Setup a
meeting
Play
messages
Avaya – Proprietary. Use pursuant to Avaya policy.
13
Voice Recognition - Just Say It
 Speech-enabled auto attendant
 Speech message addressing
 Enables users to say names instead of keying in
extensions
 No additional servers or 3rd party elements
 Available for supported languages (G13)
Virtual
receptionist
Avaya – Proprietary. Use pursuant to Avaya policy.
14
Caller Applications
 Delivers basic multi-level call redirection capability
 Intuitive web-based design interface
Press 1 for
sales,
press 2 for
billing, …
Avaya – Proprietary. Use pursuant to Avaya policy.
15
Speech To Text
See Who
Called at a
Glance
One Click to
Listen – No
TUI to Call
Jane
Manage your
Messages
with a Mouse
Click
giSTT text
transcription
One-click
callback from
smart phone
Avaya – Proprietary. Use pursuant to Avaya policy.
16
Flexible Message Store
Application
Application +
Storage
Dual
store
Avaya
Storage
Application
Per
user
store
Single
store
OR
3rd Party
Storage
 Single or multi-server
Avayard
3 Partyrd
Storage
3 Party
Storage
Storage
 Mix storage types on same system
 Multiple storage servers increases storage capacity
 Address discovery/compliance
 No email lock-in
Message Stores
• Today - Avaya, Exchange,
Zimbra
Avaya – Proprietary. Use pursuant to Avaya policy.
17
Exchange with Messaging Toolbar
with Messaging Toolbar
Avaya – Proprietary. Use pursuant to Avaya policy.
18
Exchange Design Overview
 Relies on .fwd implementation for delivery of Voice
Messages
 Uses Exchange Web Services (EWS) to retrieve and
manage voicemail messages.
 MWI ( Message Waiting Indicator) is controlled by
‘Push’ Subscription based mechanism offered by
EWS.
 All the messages (Unread/Read/Saved/Notified) are
stored in Inbox.
Avaya – Proprietary. Use pursuant to Avaya policy.
19
Impersonation Account configuration
For Exchange 2010:
Microsoft Exchange Server 2010 uses Role-Based Access Control (RBAC) to assign permissions to
accounts. You can use the New-ManagementRoleAssignment Exchange Management Shell cmdlet to
assign the ApplicationImpersonation role to users in the organization.

Run the New-ManagementRoleAssignment cmdlet to add the permission to impersonate to the specified
user. The following example shows how to configure Exchange Impersonation to enable a service
account to impersonate all other users in an organization:
New-ManagementRoleAssignment -Name:"Avaya Impersonation Role" -Role:ApplicationImpersonation User:AvayaMsgSvcAcct
-OR- To configure Exchange Impersonation for only specific users or groups of users:

Run the New-ManagementScope cmdlet to create a scope to which the impersonation role can be
assigned. If an existing scope is available, you can skip this step. The following example shows how to
create a management scope for a specific group.
New-ManagementScope -Name:"Avaya Aura Scope" -RecipientRestrictionFilter:recipientFilter
Run the New-ManagementRoleAssignment cmdlet to add the permission to impersonate the members of
the specified scope. The following example shows how to configure Exchange Impersonation to
enable a service account to impersonate all users in a scope:
New-ManagementRoleAssignment -Name:"Avaya Impersonation Role" -Role:ApplicationImpersonation User:AvayaMsgSvcAcct -CustomRecipientWriteScope:"Avaya Aura Scope"
For more information on the exact process and additional details and requirements, please see:
http://msdn.microsoft.com/en-us/library/bb204095.aspx
Avaya – Proprietary. Use pursuant to Avaya policy.
20
Autodiscover service
 AAM expects Autodiscover service to be available
“https://autodiscover.<mail domain>/Autodiscover/Autodiscover.xml”
 Achieved in Dev environment through DNS
configuration.
Avaya – Proprietary. Use pursuant to Avaya policy.
21
Storage access setup
Avaya – Proprietary. Use pursuant to Avaya policy.
22
AD user creation
Avaya – Proprietary. Use pursuant to Avaya policy.
23
Subscriber – Voice Mail management
 Exchange Web Services (EWS) is used to retrieve messages.
– A message is identified as a Avaya Voice Message if
– Message-Context : Voice-Message header.
 Greetings continue to be stored in Avaya Message store.
 Voice messages are forwarded to Store Id ( however they are
being addressed ‘TO’ Avaya message store internal id - mail)
 Unread / Read / Saved messages all are stored in INBOX and
are accessible only from INBOX.
 Outlook form continues to work similar to Avaya Message store
users from Outlook.
Avaya – Proprietary. Use pursuant to Avaya policy.
24
Deployment Models
 Single server configuration
– Easy to install
 Multiple server configuration
– Meeting the needs of most enterprises
Single Server
Configuration
Multi-Server
Configuration
Application
Application
+
Storage
Storage
Avaya – Proprietary. Use pursuant to Avaya policy.
25
Clustered Application Servers
 Delivers additional port and mailbox capacity
 Provides N+1 redundancy
 Application servers can be geographically separated
Application
Application
Application
Single site
Application
cluster
…
Storage
Avaya – Proprietary. Use pursuant to Avaya policy.
26
Multi-Site Deployment
Centralized Application and Storage
 Single system, multi-PBX
 Maintain existing dial plans
Site A
Site B
Telephony
Telephony
Server
Server
SM or SES
Application
Storage
Avaya – Proprietary. Use pursuant to Avaya policy.
27
Multi-Site Deployment
Distributed Application, Centralized Storage
 Single system, multi-PBX, multi-application server
 Enables local survivability
Site A
Site B
Telephony
Telephony
Server
Server
Application
Application
Storage
Avaya – Proprietary. Use pursuant to Avaya policy.
28
Why Consolidate?
 Reduce number of messaging systems
 Lower TCO
 Maintain existing dial plans
HQ
Application
 Deliver consistency for end users
Centralized
Storage
HQ
Remote
office
Distributed
HQ
Remote
office
Application
Application
Remote
office
Remote
office
Storage
Application
Avaya – Proprietary. Use pursuant to Avaya policy.
29
Resilience
 N+1 application
Site A
Telephony
Server
redundancy
 Local Survivability
 Benefits
Application
Application
Users
• name,
• greetings
• settings
Messages
–
Integral to solution
–
Ensure messaging is
always available
Cache
Data Center
Storage
• for last n days
Cost effective service continuity
Avaya – Proprietary. Use pursuant to Avaya policy.
30
Servers
 Hardware – System Platform
– Dell (default), HP (by request)
– Linux-based
 Options
– Standard Messaging Server
• Application server
• Storage server
• Combined application and storage server
– High Storage Capacity Messaging Server
 Leverages System Platform virtualization technology
Avaya – Proprietary. Use pursuant to Avaya policy.
31
Avaya Store Capacity Examples
Server Role
Standard
Server
Application + Storage
(Single Server)
Application Only
(dedicated application server)
Storage Only
(dedicated storage server,
Avaya Message Store only)
• 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.
• 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.
• 30-40k max speech auto
attendant names (incl remote
subscriber names)
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)
Avaya – Proprietary. Use pursuant to Avaya policy.
32
E-Mail Store Capacity Examples
Server Type
Standard Server
Capacity Limits
• 100 ports = 6,200 users
@ 62 users/port
• For a single site, up to 3 application servers can be clustered for a
max port size of 300 ports.
• An additional application server can be added to a cluster for N+1
redundancy – as long as active traffic is not exceeding 300 ports.
• 30-40k max speech auto attendant names (incl remote subscriber
names)
Exchange Server(s)
• Maximum of 15,000 users if Exchange is used for some or all
mailboxes.
Zimbra Server(s)
• Maximum of 15,000 users if Zimbra is used for some or all mailboxes.
Avaya – Proprietary. Use pursuant to Avaya policy.
33
Localization
 Languages for Aria and Audix TUIs
– US English, UK English, Brazilian Portuguese, Latin
American Spanish, French Canadian, Chinese Mandarin,
German, Japanese, French, Italian, Korean, Russian
 one-X Speech is English only
Avaya – Proprietary. Use pursuant to Avaya policy.
34
Interoperability
 SIP standard connectivity
 SIP Certification with
– Session Manager (6.0 or higher)
– Communication Manager (5.2 or
higher)
– CS 1000 R6.0
– CS 1000 R7.5 (requires Session
Manager)
– CS 2100 SE13
 Supports wide range of 3rd party
PBX systems via SIP gateways
 Message Networking (5.2 or higher)
Avaya – Proprietary. Use pursuant to Avaya policy.
35
Packaging
 2 feature levels – on a per user basis
– Basic
• Call answering
• Voice messaging
• User Preferences web pages
• Avaya, Exchange, or Zimbra storage
– Mainstream
• Access to all features including Reach Me, Notify
Me, fax, speech-based features, and IMAP
access.
 Optional capabilities
– one-X Speech
• Server extra
• Licenses included with each mainstream
messaging application user license
– Speech to text (Mutare EVM)
Avaya – Proprietary. Use pursuant to Avaya policy.
36
Installed Base Migrations
 TUI support – Aria, Audix
 Migration tools for Intuity Audix
 Programs/promotions/offers
– Refer to Avaya offer documents for full details
– ASIPP
• Upgrade pricing for Modular Messaging and CallPilot systems
on current releases
• Migration pricing for other systems
– Collaborate Your Way
• Reduces cost of upgrades when purchasing applications
– 0% financing through September 30, 2011 (NA only)
Avaya – Proprietary. Use pursuant to Avaya policy.
37
Comparison To Intuity Audix TUI
 Commonly used commands are preserved
 Functionality not included
– Only 2 greeting types supported
– Increase/Decrease volume
– Fax (not supported via TUI)
– Un-delete
– Forward message with comment at end
– Outgoing/Filed messages
– Administrative Settings by TUI
• Mailbox / Distribution Lists (use User Preferences)
• Set Personal Operator via TUI (use Web Preferences)
• Multiple Greetings
– Standard and Temporary Absence Greeting only
• Option to address a message before recording it
Avaya – Proprietary. Use pursuant to Avaya policy.
38
Comparison To Octel Aria TUI
 Maintains familiar Aria menu structure to smooth user transition
 Sending to multiple recipients
– Build recipients list first, then set delivery options and send
 Slightly different message categories (with shortcuts):
– 1.1 Unread, 1.2 Read, 1.3 Saved (archived) messages
 Lesser used or no longer relevant features not included:
– Bulletin broadcast messages
• Use system distribution lists or system broadcast instead
– Extended prompts - standard and rapid prompts are available
– Home/Guest mailbox
– Secretary access
– Delivery confirmation
– Volume control
Avaya – Proprietary. Use pursuant to Avaya policy.
39
Product Positioning
Default Recommendation
Current
Product
Modular
Messaging
CM
Messaging
Recommended Move
 Upgrade to 5.2, apply
latest service update
 Upgrade to CMM 6.0
Why
 Get current
 Qualifies for upgrade pricing to AAM
when ready to move
 Get current
 CMM remains best option for
embedded low cost messaging
 Upgrade to CMM-FM 6.0
CM
Messaging
Federal
Market (FM)
(civilian)
 Upgrade to CMM-FM 4.2
(defense)
 Get current
 Only option for JITC certification
– CMM-FM 6.0 (JITC
planned 2Q11)
 Avaya Aura® Messaging
Avaya legacy
Octel/Intuity
 Modular Messaging
 Best fit for Aria and Audix TUI and
migration tools available
 If Octel Serenade TUI or Web
Client/ROC is important
Avaya – Proprietary. Use pursuant to Avaya policy.
40
Product Positioning
Default Recommendation
Current
Product
Recommended Move
Why
 Get current – provides access to
CallPilot
HMS 400
 Upgrade to 5.0, apply
latest service update
latest capabilities such as geographic
redundancy
 Qualifies for upgrade pricing to AAM
when ready to migrate
 Upgrade to 2.0
 Get current
 Strategic hospitality solution
 Avaya Aura® Messaging
 Meridian Mail is End of Support
 Future proof strategic platform
Meridian Mail
 If TUI, migration tools, and near
 CallPilot
identical feature set important (tools
only for MM11-MM13)
Meridian Mail
HVS
 HMS 400
 Strategic hospitality solution
Greenfield or
competitive
 Avaya Aura® Messaging
 Future proof strategic platform
Avaya – Proprietary. Use pursuant to Avaya policy.
41
Key Differentiators
Differentiator
Value
Speech-based autoattendant and one-X
Speech
Enables callers to say names instead of keying
in an extension
Voice control of messaging, email, calendar, …
100% Linux based
Reduces TCO and provides better security
Deployment flexibility
Adapts to customer environment and
requirements for message store and
consolidation/centralization
Current and planned
redundancy options
Makes messaging highly available consistent
with other voice redundancy
SIP based
Improved interoperability within Avaya
communications environments
Avaya – Proprietary. Use pursuant to Avaya policy.
42
Key Differentiators - cont’d
Differentiator
Value
Per user choice of
message store
Administrator chooses which message store to
use on a per user basis
Flexibility to choose which users are
discoverable
Per user choice of TUI
Administrator chooses which TUI to use on a per
user basis
Users can retain what they are familiar with
Integrated inbound fax
No need for 3rd party fax server or external fax
machines
Self-service web portal
(Reach Me, Notify Me, …)
End users have full control of their availability
and can significantly enhance their reach
Clientless Outlook toolbar
Enables painless deployment to end users
easing IT requirements and user dependence
Avaya – Proprietary. Use pursuant to Avaya policy.
43
References and Resources
 Sales/partner portal general link
http://portal.avaya.com/ptlWeb/products/P0792
 Contacts
– Marketing
• Denis Fortier [email protected]
– Product Management
• Roger Brassard [email protected]
• Mike Wasserburger [email protected]
• Richard Rundstein [email protected]
– Sales
• Vic Kingrey [email protected]
Avaya – Proprietary. Use pursuant to Avaya policy.
44
thank you
Vic Kingrey
[email protected]
408-562-5535
Avaya – Proprietary. Use pursuant to Avaya policy.
45
Descargar

Avaya Internal Template for PowerPoint 2003