Full Document Is Available Upon Request from Your Avaya Account Team Or Authorized Business

ABSTRACT [Full document is available upon request from your Avaya Account Team or Authorized Business Partner]

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

This paper discusses various concepts related to Avaya messaging products, specifically: Modular Messaging Release 4.0, Octel 250/350, and other related products. 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.

This paper is not intended to replace the product documentation. For precise information on how to plan, use, operate, install, administer, and maintain these products, consult the product documentation available on www.avaya.com/support. For information on products for future releases, please contact your Avaya client executive or authorized Avaya BusinessPartner to discuss the messaging roadmap.

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 R4.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 R4.0.

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, Administration & Management)