Noticeable Changes Document for Moving from Octel to MM? 1

[98Converter]

Avaya creates these documents, but I wasn't able to find one that highlights the key differences, benefits, etc.. for users moving from Octel to MM.

Does anyone have that - or was it even created?

Thanks,
CJH

We are what we repeatedly do. Excellence, then, is not an act but a habit. ARISTOTLE 384-322 B.C.

 

[KenMeans]

Modular Messaging Summary Guide for Octel 250/350 Customers
Key Differences between Octel 250/350 and
Modular Messaging R3.0 with the Avaya Message Storage Server using the Aria TUI
Preface

This summary document highlights the key differences between: Modular Messaging Release 3.0, Octel 250/350. This document attempts to “grade” individual features and characteristics as they apply to actual customer usage and environments, and each of the messaging platforms. The grades are intended to make clear how Modular Messaging can meet customer needs. The relative significance of the differences will vary by customer. For detail explanations of these differences, consult the Modular Messaging Application Guide for Octel 200/300 Customers.

Introduction

Modular Messaging is a standards-based IP messaging solution that offers the robustness that customers expect from traditional voicemail solutions, while providing a migration path to the future. Moving to an IP-architecture allows Avaya to introduce new capabilities and topologies to meet the converged solution needs of our customers. Modular Messaging is intended to co-exist with and ultimately to succeed and replace multiple voice messaging systems currently supported within the Avaya Messaging portfolio including: Octel 250/350 (with the Aria Telephone User Interface – TUI), Octel 200/300 (with the Serenade and Aria TUIs), Intuity AUDIX MAP 5/40/100 platforms (with the AUDIX TUI), and Unified Messenger (with the Aria TUI). With the merger of all these products it is important to note that Modular Messaging will offer a functional replacement for most of the features and applications currently available on these platforms. This means that in some cases the application may operate or be administered differently than it is today on one of the traditional messaging platforms. In other cases, some features or capabilities may not be carried forward. Typically, this is in response to changing business needs, such that those features that have declining use or value for most customers.

This paper identifies key differences between Modular Messaging R3.0 (configured with the Avaya Message Storage Server (MSS), and enabled with the Aria Telephone User Interface (TUI) for Modular Messaging) and Octel 250/350 with Octel Aria software at release R3.1. Modular Messaging R3.0 also supports the Serenade TUI. For differences between Modular Messaging and Octel 200/300, consult the Modular Messaging application guide for Octel 200/300 Customers. Modular Messaging also supports the Intuity AUDIX TUI. For differences between Modular Messaging and Intuity AUDIX, consult the Modular Messaging Application Guide for Intuity AUDIX Customers. For user feature differences between Modular Messaging with Aria, Serenade, and AUDIX TUIs, consult the Modular Messaging TUI guide.

Topics include:
? Caller Care / Responsiveness (Call Flow, Caller Experience)
? Message Flow (Notification, Respond/Create, Message Options, Message Addressing)
? User Features (Message Envelope, Message Management, Fax, Mailbox Management, Desktop Access)
? Applications (Add-On Applications, Mailbox Types, Work Groups, Enterprise Communication, Menus)
? Networking (Networking System Features, Networking User Features, Networking Protocols)
? System Management & Administration (Scalability, System, Reliability & Availability, Mailbox Administration, System Administration, Documentation, Mailbox Security)
? International Considerations (Language Features, Country & Language Availability)
? Modular Messaging Application Interoperability (End User Client, Networking, Admin & Management)


Key Differences Summary:
Modular Messaging R3.0 with MSS and Aria TUI relative to Octel 250/350 R3.1

Legend:
[+++] New with Modular Messaging
[++] Different with Modular Messaging with significant advantages
[+] Different with Modular Messaging with some improvements
[?] Different with Modular Messaging with no significant gain or loss in capability
[-] Available with Modular Messaging with some loss in capability
[- -] Available with Modular Messaging with significant differences in capability
[- - -] Not available with Modular Messaging
[alt] An alternative solution is available for Modular Messaging
[yes] Available with Modular Messaging











Caller Care / Responsiveness
Call Flow
[+++] Calls via Automated Attendant
[+++] Find Me
[+++] Notify Me – Caller Requested
[+++] One Number Connectivity
[+++] One Number Identity
[+++] Transfer to Messaging
Caller Experience
[+] Common Caller Interface
[?] Language - Call Answer
[+++] Private Call Answer Msgs
Message Flow
Notification
[+++] Auto Distribute
[+] Call Me / Outcalling
[++] Desktop Messaging Inbox
[+++] Notify Me – Automatic
[+++] Notify Me – Caller Request
[?] Message Waiting (MWI)
Respond / Create
[++] Call Sender of Call Answer
[+++] Forward Without Comment
[- - -] Forward Removing Intro
[+++] Record On Messaging
[+++] Reply to All
[++] Reply to Call Answer Msgs
[+++] Reply With Original
[+++] Text & File Attachments
Message Options
[?] Delivery Options
[+] Future Delivery
[- - -] Message Delivery Confirmation
[- - -] Message Non-Receipt Notification

Message Addressing
[++] Address by Name
[?] Alias / Express
[++] Directory – Remote Subscribers
[+++] Internet Messaging
[++] Personal Distribution Lists
[?] System Distribution Lists
[- - -] Warnings – Extended Absence & Message Blocking
User Features
Message Envelope
[?] Envelope Playback
[?] Originator Information
[++] Originators Name for Call Answer Messages
[+++] Recipient List
[+++] Subject Line
[+++] TTS Name
Message Management
[++] Archiving & Foldering
[- - -] Auto Delete Warning
[+++] Deleted Messages
[++] Message Format
[++] Message Length
[+++] Print Inbox
[?] Review by Message Status
[+] Review by Message Type
[-] Review Sequence
[- - -] Search for Sent Messages
[+++] Text-to-Speech (TTS)
[+++] Time Zone
Fax Messaging
[- - -] Fax Auto Print
[+++] Fax Delivery Notification
[-] Fax Overflow
[+] Fax Requirements
[- -] Fax Sending

[+] Fax Viewing & Printing
[+++] Print Inbox
[+++] Scanner
[+++] Text-to-Fax
Mailbox Management
[?] Alias Log On
[- - -] Application Access
[?] Follow-Me-Forward
[- -] Force Recording of Greeting
[- - -] Guest, Home, Secretary
[++] Language - Subscriber Mailbox
[+] Mailbox Size
[- -] Message Blocking
[- - -] Prompting Level
[?] Subscriber Controlled Parameters
[++] Telephone User Interface
Desktop Access
[+++] Subscriber Options
[+++] Client Add-ins for Microsoft Outlook and IBM Lotus Notes
[+++] Email Clients
[+++] IBM Lotus Notes Users
[+++] Microsoft Outlook Users
[+] Web Messaging
[alt]

http://www.messenger

[+] Connection Mode
[++] IP Access
Visual Messenger
[++] Audio Playback
[?] Dialer
[++] Mailbox Management
[++] Message Access
[++] Message Addressing
[?] New Message Alert
[++] Notes
[+++] Volume Control

Applications
Work Groups
[+++] Auto Distribute
[++] Multiple Extensions / Mailbox
[- -] Multiple Mailboxes / Extension
[- -] System Partitioning / Communities
Enterprise Communication
[+] Address by Name
[?] Broadcast
[- - -] Bulletin Broadcast
[++] Call Center Integration
[?] ELA / System Distribution Lists
[+++] Internet Messaging
[++] Personal Distribution Lists
[?] System Distribution Lists / ELA
Menus / Caller Applications
[- - -] Add-On Applications
[-] Auto Attendant Directory
[++] Caller Applications Development
[++] Dial by Name
[-] Mailbox Types
[?] Menu Applications
[?] Prompts and Announcements
[?] Speech Attendant
Networking
Networking System Features
[- - -] Analog Fallback for Digital Networking
[- -] Aria Domain
[+] Directory – Remote Subscribers
[?] Remote Subscriber Database Synchronization
[?] Network Dial Plan
Networking User Features
[?] Alternate Addresses
[?] Blind Addressing
[++] Call Sender to Remote Subscriber
[-] End Node Voice Name
[+] Future Deliver Across the Network
[+] Name Verification
[++] Originators Name for call answer messages
[+++] Recipient List for Networked Messages

[++] Reply to Call Answer messages from remote subscriber
[+++] Reply To All for a Networked Message
[- - -] Warning Messages Across the Network
[?] Working with Message Networking
Networking Protocols
[?] AMIS
[?] AUDIX Digital Networking via TCP/IP
[?] Octel Analog Networking
[?] Octel Aria Digital Networking
[?] Octel Serenade Digital Networking
[?] SMTP/MIME
[?] VPIM V2
System Management & Administration
Scalability
[+] Port Capacity
[++] Storage Capacity
[++] Directory
[?] Desktop Access Capacity
System
[++] Converged Solution
[+] Hardware Platform
[++] Lifecycle Status
[++] Operating Systems
[++] RTU / Capacity on Demand
[++] Switch Integrations (SWINS)
[++] UCC Configuration
[?] Voice of the system prompts
Reliability & Availability
[+++] Client Access
[+++] Offline Call Answer
[+++] Offline Access to call answer messages
[+++] Offline Archive
[+] RAID Disks
[+++] Redundancy – Application
[++] System Backup
[+] Server Component Reliability
[+++] Server Monitoring - SNMP
[+++] Server Monitoring – RMB


Mailbox Administration
[- - -] Account Codes
[- - -] Block messages to uninitialized mailbox
[+] Class of Service
[+] Fax Availability
[-] Mailbox Address
[?] Name Fields
System Administration
[++] Administrative Interfaces
[+++] Directory Enabled Mgmt.
[+++] Integrated Management
[+] NANP Support
[++] Private Message Control
[?] Reports & Logs
Documentation
[+++] Documentation Search
[+++] Online Help
Mailbox Security
[- - -] Access Security
[- - -] Disable Access from Caller Interface
[+++] Lock mailbox after “n” invalid logon attempts
[+] Password Recycle
[?] Password Reset
[- - -] Skip Password
International
Language Features
[+] Language - Call Answer
[++] Language - Subscriber Mailbox
[+++] Multi-Byte Character Sets
Country & Language Availability
[++] Country Availability
[++] Languages - Prompts
[++] Languages - GUI
[++] Languages - Networking
Interoperability
[alt] Visual Messenger
[yes] UCC
[alt]

http://www.messenger

[alt] Interchange
[yes] Message Networking
[yes] Avaya Fault and Performance Manager
[yes] Avaya Site Administration
[yes] Avaya Multi-Site Admin
[yes] Directory Enabled Mgmt
[yes] eHealth for Voice
[yes] Mailbox Manager
[alt] mobilePath


Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[KenMeans]

Subject: Primary Differences – Octel 250/350 vs. MM Aria Telephone User Interfaces (TUIs)
Document ID 118838 Date:
From: April 19, 2006
John R. Lothrop
303-538-4486
lothrop@avaya.com


1 Introduction
(NOTE: This document is applicable for MM 2.0 and MM 3.0.)

This document provides a high-level description of the primary differences in the Aria Telephone User Interfaces (TUI) for Octel 250/350 and MM. The Modular Messaging (MM) Aria TUI is based on the Octel 250/350 TUI but there are a number of differences, some of which are obvious while others are subtle. Also note that MM provides a “Common Caller Interface” for Call Answering that is independent of the subscriber TUI for the called mailbox.

These notes focus on the functional differences that will be the most noticeable to customers who are moving from Octel 250/350 to MM with the MM Aria TUI. There are many other differences as detailed in Modular Messaging Application Guide for Octel 250/350 Customers (see Avaya Enterprise Portal >> Modular Messaging >> Sales Collateral and Tools).

In order to make the customer’s transition from the Octel 250/350 Aria TUI to the MM Aria TUI as smooth as possible, these differences should be discussed with the customer well in advance of the actual transition. Advance notice and planning are critical for a smooth transition.
1.1 Terminology
The following terms are used in these notes:
Aria TUI The TUI provided by Octel 250/350 systems.
MM Modular Messaging
MM Aria TUI The Aria-based TUI provided by MM 2.0 (and later).
TUI Telephone User Interface
2 PRIMARY DIFFERENCES
2.1 “Power Keys” and Shortcuts
2.1.1 Help
In Octel 250/350, pressing “0” provides help, more explanation and/or more options. MM supports “0” at selected points in the TUI menu, in which case it repeats the current prompt.
2.1.2 Transfer to Attendant
In Octel 250/350, pressing “00” causes the subscriber to be transferred to an attendant, if one if defined. This capability is not provided by MM.
2.1.3 Skip Message Categories
While listening to messages in Octel 250/350, pressing “##”causes the system to skip to the archived (i.e., saved) message queue. In MM, this allows the subscriber to skip to the next message category, i.e., saved and/or deleted.
2.2 Reviewing Messages
2.2.1 Message Categories
Octel 250/350 supports new (“unheard”) messages, skipped messages, and saved (“old archived”) messages. MM supports new, saved and deleted messages. Deleted messages are available via the MM Aria TUI during the same login session in which the messages were deleted.
2.2.2 Message Types
In addition to voice and fax messages, MM also supports E-mail messages (text and/or file attachments).
2.2.3 End-of-Message Options
2.2.3.1 Forward With or Without Comment
The MM Aria TUI allows a subscriber to forward a message with or without a comment. Octel 250/350 always requires the subscriber to record a comment before forwarding a message.
2.2.3.2 Forward Removing Introductions
In the Octel 250/350, the subscriber can forward a message and remove all the incremental messages that have been added as it has been passed through the local system (this is not supported for networked messages). Thus the forwarded message will contain only the original message and the most recent comment as recorded by the sender. The MM Aria TUI maintains the integrity of the message thread and does not support the ability to remove the introductory messages.
2.2.3.3 Reply to All
When replying to a message, Octel 250/350 subscribers may reply only to the originator of the message. MM Aria TUI subscribers have the option to “Reply to All”, in which case the response is automatically addressed to all the recipients of the original message. In MM, “Reply to All” can be used with or without the original message being attached.
2.2.3.4 Reply to Sender with Original
When replying to a message, Octel 250/350 subscribers may reply to the originator of the message but cannot include the original message(s). The MM Aria TUI allows subscribers to reply to the originator with or without including the original message.
2.2.3.5 Text & File Attachments
Octel 250/350 and MM systems support both voice and fax messages. MM also supports E-mail messages (i.e., text and/or file attachments).
2.2.3.6 Deleted Messages
When a message is deleted in an Octel 250/350, there is no way to retrieve that message. With the MM Aria TUI, the subscriber can listen to, reply to, and forward messages in the deleted message queue. Once the subscriber terminates the login session, the deleted messages are no longer available via the TUI.
2.2.3.7 Date and Time Playback
In neither Octel 250/350 nor MM are message envelopes (a.k.a., headers) played prior to message playback. The subscriber may go to the end of the message and then request envelope playback. The envelope includes the message subject, sender, date and time, etc.

In Octel 250/350 and MM 3.0, the system administrator may define whether or not the message date and time are played prior to the message body. The administrators choices are “always”, “never”, and “subscriber controlled”. Note that this applies only to the date and time the message was received. It does not apply to the other elements of the message envelope.

MM 2.0 did not support date and time playback prior to message playback.
2.2.3.8 Recipient List
For messages “directly” received by MM, MM retains the identification of the originator as well as the complete recipient list. This includes local messages and remote messages from other MM systems and/or SMTP endpoints. This allows MM to provide the “Reply to All” feature as described elsewhere. Note that retention of all recipients does not apply for remote messages received via Message Networking.

Octel 250/350 identifies only the originator of the message.
3 Changes for MM 3.0
This section describes new functionality added in MM 3.0.
3.1 Time Zone per Mailbox
MM 3.0 introduced the “Time Zone per Mailbox” feature. A system-wide default time zone value is set for MM. The system administrator may then define different default time zones for various Classes of Service (COS). Additionally, individual subscribers may use a Subscriber Options client (not a TUI) to define a different time zone for their mailboxes. Timestamps are stored internally within MM using a universal time code. Whenever time is presented to the subscriber (e.g., the time that a message was received or time that a message is scheduled for delivery), the internal timestamp is adjusted by the applicable time zone for the mailbox before being played to the subscriber.
3.2 Multilingual Call Answer
MM 3.0 supports assignment of three Call Answer announcement languages (“primary”, “secondary” and “tertiary”) on a per-mailbox basis using Subscriber Options. The assignment of multilingual Call Answering parameters is not available via the TUIs.

The primary language is used whenever a call is answered for the subscriber. If additional languages have been defined for the called mailbox, the caller will be able to change languages at any time before the record tone (“Beep”) is played.

One of the assigned Call Answer languages may be TTY.
3.3 Support for TTY
MM 3.0 TTY (“45 Baud, US format TTY”) support is provided for the Common Caller Interface, for each TUI and for each message store. A single MM 3.0 mailbox is able to record and store messages in both voice and TTY formats.

Callers to MM 3.0 systems are able to toggle between spoken and TTY announcements by pressing “*1”. For Call Answer using TTY, the prompt “HD” (for “Hold”) is played as soon as the call is answered and the prompt “GA” (for “Go Ahead”) is played immediately prior to the record tone (“BEEP”). The caller is not required to press any Touch Tone keys in order for MM 3.0 to record a TTY message.

NOTE: MM 3.0 support for TTY with IP switch integrations (e.g., SIP and IPNow! for H.323) is dependent on the quality of the in-band audio signals within the customer’s IP network. Most customers using LAN connectivity should have acceptable audio quality in their IP networks to support accurate transmission of TTY, however customers using WAN connectivity within their voice network may experience problems supporting TTY.


Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[98Converter]

Thanks alot Ken!

Thanks,
CJH

We are what we repeatedly do. Excellence, then, is not an act but a habit. ARISTOTLE 384-322 B.C.