Octel Aria 1.2 Instruction Manual


Aria 1.2 Release Manual
Edition 2
101–1477–001
Octel Communications Corporation
1001 Murphy Ranch Road
Milpitas, CA 95035-7912
408-321-2000

Your comments about this document are welcome. They can assist us in improving our products.
Please address comments to [email protected] or to the Technical Publications Manager at
Octel Communications Corporation
1001 Murphy Ranch Road
Milpitas, California 95035-7912
U.S.A.
408-321-2000
http://www.octel.com
Copyrighte1996 by Octel Communications Corporation
1001 Murphy Ranch Road
Milpitas, California 95035-7912
All rights reserved. No part of this book may be reproduced in any form without written
permission from Octel Communications Corporation.
All trademarks identified by the tor Rsymbol are trademarks or registered trademarks,
respectively, of Octel Communications Corporation. All other trademarks belong to their
respective owners.
Printed in the United States of America.
PRINTED ON
RECYCLED PAPER

101–1477–001 Edition 2
About This Manual
Aria 1.2 software supports the Octel Overture 250 and Octel Overture 350 message servers.
These servers provide telephone answering and voice messaging to the Global Business Solutions
(GBS) marketplace.
This Aria 1.2 Release Manual describes the capabilities introduced with Aria 1.2 as they affect
service personnel. It consolidates information that historically has been included in a Service
Note and in Service Manual updates for a new software release. Most of the information is
applicable to both the Octel Overture 250 and the Octel Overture 350, but wherever there are
differences in the information for these products, the Release Manual describes those differences.
The four chapters in this manual provide the following:
1. An introduction to Aria 1.2 as it affects system managers and service personnel
2. Procedures to upgrade to Aria 1.2
3. New Aria 1.2 system utilities and procedures for use by service personnel
4. Field-identified Product Change Requests (PCRs) that are addressed by Aria 1.2
A general table of contents is included at the beginning of the manual. An index at the end of the
manual allows you to locate information about specific subjects rapidly and easily.
Compared with the original Aria 1.2 Release Manual, P/N 101–1477–000, this edition includes
the following updates:
-Correction of the part-number level required for the CCF card (Chapter 2)
-More information about using the FLT-A card (Chapter 3)
-Addition of two more PCRs that are corrected in Aria 1.2 (Chapter 4)
Related Publications
This Aria 1.2 Release Manual supplements the following service documents:
-Octel Overture 250 Service Manual, P/N 101–1341–000, which supports only Aria 1.0.
-Octel Overture 250 Service Manual, Addendum I, Aria 1.1 Procedures and Utilities,
P/N 101–1450–000.
-Octel Overture 350 Service Manual, P/N 101–1449–000, which supports Aria 1.0 and
Aria 1.1.

iv Aria 1.2 Release Manual
101–1477–001Edition 2
Appropriate installation instructions are associated with the kits that are used to perform
conversions, upgrade EPROMs, or install certain features. This Release Manual refers to specific
installation instructions by name and part number, as required.
The following documents for Aria 1.2 are of interest to the system manager:
-Aria 1.2 System Manager Manual, Volume I, Implementation, P/N 101–1472–000.
-System Manager Manual,Addendum II for Aria 1.2, P/N 101–1476–000.
-Aria 1.2 Screen and Prompt Summary, P/N 101–1496–000.
A literature kit, P/N 004–0366–000, is available. It includes the following complete set of System
Manager Manual documentation that supports all Aria software releases:
-Aria 1.2 System Manager Manual,Volume I, Implementation, P/N 101–1472–000.
-Aria 1.0 System Manager Manual, Volumes II through IV, P/Ns 101–1381–000,
101–1382–000, and 101–1383–000.
-System Manager Manual,Addendum I for Aria 1.1, P/N 101–1442–000.
-System Manager Manual,Addendum II for Aria 1.2, P/N 101–1476–000.
-Aria 1.2 Screen and Prompt Summary, P/N 101–1496–000.

101–1477–001 Edition 2
Contents
1. INTRODUCTION
Features for Service Personnel 1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Features Administered by System Managers 1-2. . . . . . . . . . . . . . . . . .
Compatibilities With Applications 1-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Administered AMIS 1-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multiline Networking 1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ASCII Name Verification 1-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Control of MWI 1-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Messaging Tutorial 1-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TDD/TTY Support 1-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Application Easy Access 1-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Call Processing Enhancement 1-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Port Traffic Statistics Utilities 1-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Node Expansion 1-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Broadcast Messages Blocked from Application Mailboxes 1-9. . . . . .
Administrative-Options and FaxResponse
Prompt Enhancements 1-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Feature Option 33 Name Changed from “Mitel Limited”
to “Set Emulation” 1-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

vi Aria 1.2 Release Manual
101–1477–001Edition 2
2. ONLINE UPGRADE INSTRUCTIONS
Overview 2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Check The Major Steps 2-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Make Sure that the Correct Equipment is Available 2-4. . . . . . . . . . . .
Hardware and firmware 2-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Software 2-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Have the Engineering Option Enabled 2-6. . . . . . . . . . . . . . . . . . . . . . . .
Clear the AMIS Queue 2-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verify the System Boot Area 2-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connect the PC and the Server 2-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting the PC directly to the server 2-8. . . . . . . . . . . . . . . . . .
Connecting the PC remotely to the server 2-10. . . . . . . . . . . . . . . .
Install the Online Upgrade Tool on the PC Hard Drive 2-12. . . . . . . .
Verify the Values in the PC Setup Menu 2-14. . . . . . . . . . . . . . . . . . . .
Load Software and Phrase Diskettes on the PC Hard Drive 2-15. . .
Perform the Automatic Upgrade 2-19. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verify the Upgrade 2-24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reset AMIS Networking, if Necessary 2-24. . . . . . . . . . . . . . . . . . . . . . .
Reset the Boot Area, and Boot the New Software 2-25. . . . . . . . . . . .
Have the Engineering Option Disabled 2-25. . . . . . . . . . . . . . . . . . . . . .
Make Software and Phrase Areas Redundant 2-26. . . . . . . . . . . . . . . .

Contents vii
101–1477–001 Edition 2
3. SYSTEM UTILITIES AND PROCEDURES
Overview 3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FLT-A Card and its Removal and Replacement 3-2. . . . . . . . . . . . . . .
Conversion of Branch, Aspen, or Maxum to Octel
Overture 250 Using PC Tape 3-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Conversion of Octel Overture 250 to Octel Overture 350 3-6. . . . . . .
Port Traffic Statistics Utilities 3-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mixed 1-GB, 2-GB, and 4-GB Message Drives, and the
Upgrade Message Drive Utility 3-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reset Mirrored Drive Status Utility 3-9. . . . . . . . . . . . . . . . . . . . . . . . . . .
Collapse Nodes Utility 3-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Revised Enable Drive Utility 3-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Revised Replace System Drive Utility 3-12. . . . . . . . . . . . . . . . . . . . . . .
Hot-Plug Replacement of Tape Drive in Octel Overture 250 3-13. . .
Hot-Plug Addition of a Second System Drive in Octel
Overture 250 3-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Flash EPROMs on CCF Card 3-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
New Error Messages for Tape Drive Operations 3-16. . . . . . . . . . . . . .
Feature Option 33 Name Changed from “Mitel Limited”
to “Set Emulation” 3-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
International Code Merge 3-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4. PCR CORRECTIONS 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

viii Aria 1.2 Release Manual
101–1477–001Edition 2
Figures
2-1. PC-to-Octel Overture 250 Direct Connection 2-8. . . . . . . . . . . . . . . . . .
2-2. PC-to-Octel Overture 350 Direct Connection 2-9. . . . . . . . . . . . . . . . . .
2-3. PC-to-Octel Overture 250 Remote Connection 2-10. . . . . . . . . . . . . . .
2-4. PC-to-Octel Overture 350 Remote Connection 2-10. . . . . . . . . . . . . . .
2-5. PC’s ONLINE UPGRADE Installation Program Screen 2-13. . . . . . . .
2-6. Screen Showing End of ONLINE UPGRADE Installation 2-13. . . . . .
2-7. Online Upgrade Main Menu 2-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-8. Example of PC Configuration Screen 2-14. . . . . . . . . . . . . . . . . . . . . . .
2-9. Utilities Menu 2-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-10. Copy/Delete UPG Menu 2-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-11. Screen Prompts for Beginning the File Copy 2-16. . . . . . . . . . . . . . . . .
2-12. Verification Prompt 2-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-13. Example of Status Messages Screen 2-17. . . . . . . . . . . . . . . . . . . . . . .
2-14. Status Messages Screen With File Copy Complete Message 2-18. .
2-15. UPG Directories Menu 2-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-16. Modem Setup Menu 2-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-17. Example of Status Messages Box With Confirmation Prompt 2-21. .
2-18. Example of Status Messages Box With Begin Automatic
Upgrade Prompt 2-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-19. Example of Online Upgrade Status Screen Showing
Upgrade in Process 2-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-20. Example of Online Upgrade Status Screen Showing
Upgrade Complete 2-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-1. Example of Menu 13.11, Review Card Management 3-3. . . . . . . . . . .
3-2. Menu 20.1, Port Testing Utilities, With the Port Traffic
Statistics Option Highlighted 3-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-3. Menu 20.1.5, Port Traffic Statistics Utility 3-7. . . . . . . . . . . . . . . . . . . . .
3-4. Example of the Port Traffic Statistics Utility Screen 3-8. . . . . . . . . . . .
3-5. Example of the Node Collapsing Utility Screen 3-11. . . . . . . . . . . . . . . .

101–1477–001 Edition 2
INTRODUCTION
Aria 1.2 software introduces support for new hardware, features, and utilities that are described in
this Release Manual. Some of these features are used by service personnel, and others are
administered by system managers.
Features for Service Personnel
New Aria 1.2 considerations for service personnel include the following:
-New FLT-A card for Lucent Technologies (formerly AT&T) integration in the Octel
Overturet250 (with new line types)
-Conversion of a Branch, Aspen, or Maxumto an Octel Overture 250 using the tape drive
in a PC
-Conversion of an Octel Overture 250 at Aria 1.2 to an Octel Overture 350 at Aria 1.2
-New Port Traffic Statistics utilities (also used by system managers)
-Mixed 1-GB, 2-GB, and 4-GB message drives and the new Upgrade Message Drive utility.
-New Reset Mirrored Drive Status utility
-New Collapse Nodes utility
-Revised Enable Drive utility
-Revised Replace System Drive utility
-Hot-plug replacement of the tape drive in the Octel Overture 250
1

1-2 Aria 1.2 Release Manual
101–1477–001Edition 2
-Hot-plug addition of a second system drive in the Octel Overture 250
-Flash EPROMs on the CCF card (combination CPU/file card) in the Octel Overture 250
-New error messages for tape operations
-Feature option 33 name changed from “Mitel Limited” to “Set Emulation”
-International code merge
These service-related features, utilities, and procedures are described in detail in Chapter 3.
Features Administered by System Managers
Aria 1.2 features administered by the system manager include the following:
-Administered AMIS (audio-messaging interchange specification)
-Multiline networking
-ASCII name verification
-Control of message-waiting indication (MWI)
-Messaging tutorial
-Telecommunications Device for the Deaf/teletype (TDD/TTY) support
-Application easy access
-Call processing enhancement
-Port Traffic Statistics utilities (also used by service personnel)
Aria 1.2 enhancements that require no system manager action include the following:
-Node expansion
-Broadcast messages blocked from application mailboxes
-Administrative-options and FaxResponse prompt enhancements
-Feature option 33 name changed from “Mitel Limited” to “Set Emulation”
These features are described further in subsequent sections of this chapter. Details are
documented in the System Manager Manual,Addendum II (P/N 101–1476–000).
In addition to English TDD/TTY, Aria 1.2 supports the same languages as Aria 1.0 and Aria 1.1;
namely, American English, American Spanish, British English, and Canadian French.

Introduction 1-3
101–1477–001 Edition 2
Compatibilities With Applications
The latest and minimum required levels of applications that support Aria 1.2 are as follows:
Application Latest Level Required Level
CNM* 1.2 1.2
CSA 1.3 1.3
DecisionPro 2.0 2.0
DMFS 2.1 2.1
DMOS 2.1 2.1
FaxCall 1.11 1.11
Octel Analyst replaced by
DecisionPro 2.0 replaced by DecisionPro 2.0
PC/CDR 2.3 2.3
TransAct 2.2 2.2
* CNM does not support node collapse, nodes that use multiline networking,
administered AMIS, or new nodes 501 through 999.
New events are added to Online CDR in Aria 1.2. Refer to the Online CDR User Reference
Guide, P/N 101–1479–000.
Administered AMIS
Subscribers with mailboxes on an Octel Overture 250 or 350 server can use AMIS analog
networking to exchange messages with subscribers on non-Octel voice-messaging systems.
Messages can be sent to any voice-messaging system that supports the AMIS analog standard.
This optional feature extends voice messaging from the voice processors of one manufacturer to
voice processors at many locations from many manufacturers. AMIS analog networking can be
enabled on any Octel server.
Administered AMIS enhances the standard AMIS analog networking feature. When using
standard AMIS analog networking, subscribers must know the message-addressing sequence
required, the access number of the destination system, and the mailbox number of the recipient.
With administered AMIS, as with OctelNet networking, subscribers need only know the
destination addresses; that is, the node and mailbox numbers of the recipients. Also, a node name
can be recorded for an AMIS node, so address confirmation is reduced from a 10-digit number
string followed by a mailbox number to a short node name followed by the mailbox number. As a
result, administered AMIS is the simplest messaging solution for subscribers to send messages to
non-Octel voice-messaging systems.

1-4 Aria 1.2 Release Manual
101–1477–001Edition 2
With administered AMIS, the system manager can schedule messages for delivery at any
predetermined time. With standard AMIS, messages are queued for immediate transmission.
When an AMIS message comes into an Octel server, it includes a telephone number to which a
reply can be sent. The system manager enters this telephone number in CCITT format in the new
Site ID: field of menu 15.1.3. Whenever the server receives an AMIS message, it compares the
telephone number included with the message to the server’s list of administered AMIS site IDs. If
a match is found, the server recognizes the sending system as an administered AMIS node. In this
case, if a subscriber plays the message’s envelope information, it includes the name that the
system manager recorded on this server for the remote node.
In the Node Phone Number: field, the system manager specifies the number the server calls to
send messages and replies to the AMIS node. Usually, this should be the same number entered in
the Site ID: field. However, dialing-plan irregularities sometimes prevent delivery of replies to
the telephone number that the sending node included with the AMIS message. In this case, the
system manager specifies the correct number for the server to call in the Node Phone Number:
field.
As with standard AMIS, administered AMIS does not support messages more than 8 minutes
long (including any prepended sender’s name), delivery options (urgent, private, future delivery,
confirmation of delivery), operator-assisted networking, line turnaround (allowing remote node
response in the same call), fax messages, NameNet entries, or multiline networking.
When the following actions are attempted, the server plays new prompts to indicate that the
actions are not permitted:
-A subscriber tries to send a fax annotation to an AMIS node.
-A subscriber tries to forward a fax message or fax annotation to an AMIS node or to a
follow-me-forward mailbox that has been forwarded to an AMIS node.
-A caller tries, in telephone-answering mode, to leave a fax message in a mailbox that has
been forwarded to an AMIS node.
For administered AMIS to work, both feature option 44 – Networking and feature option 49 –
AMIS Analog Networking must be enabled.
Multiline Networking
With Aria 1.0 and Aria 1.1, the OctelNet networking feature allows only one telephone
connection to a specific remote node; some customers create multiple alias nodes to permit
multiple, simultaneous transmissions.
The multiline networking feature of Aria 1.2 allows up to 12 simultaneous connections, as
specified in the Node Profile (menu 15.1.3). Before each additional line is seized, criteria for both
the total number of messages to be networked (0–500) and the total duration of these messages
(0–120 minutes), as specified by the system manager, must be met.

Introduction 1-5
101–1477–001 Edition 2
With multiline networking, there is still only one networking queue per node. Messages are
transmitted from that queue one by one, on a line that is currently transmitting, or on a new line if
the multiline thresholds are met. All lines that have been seized for transmission remain dedicated
to networking until all messages are transmitted, even when the remaining numbers of messages
and minutes fall below the criteria by which a new line is seized.
If any ports that are enabled for networking in menu 4 are also used for other tasks such as
accepting incoming calls, outcalling, or paging, heavy use of multiline networking could affect
those tasks. If the system manager expects that multiple lines will be used heavily for networking,
he or she may wish to dedicate particular ports to networking.
In addition to the Maximum Number of Simultaneous Transmissions: field, the actual number
of lines used simultaneously for networking can be limited by whether any ports enabled for
networking in menu 4 are available.
Whenever a line is seized for networking, a CDR event 66 (BN_MULTILINE) is generated. You
can use the Online CDR utility to search for these events and determine whether appropriate
thresholds have been set for each node. Refer to the Online CDR User Reference Guide,
P/N 101–1479–000.
Established message-delivery schedules also apply to multiline networking. That is, multiline
networking takes place only during established delivery windows.
Octel advises against enabling multiline networking to any nodes that do not have Aria 1.2
software, because this could create a traffic imbalance. For example, if many messages were sent
simultaneously by multiple lines from an Octel Overture 250 or Octel Overture 350 to an Aspen
or to a server with Aria 1.1 software, there could be significant delays in transmission of replies
to those messages, because such receiving nodes without Aria 1.2 have only a single line
available for replies.
ASCII Name Verification
When subscribers use NameNet to send messages to a mailbox on a remote node, the server also
sends an ASCII representation of the name of each receiving mailbox owner. As a security
measure, the remote node checks that each destination mailbox exists and verifies that the ASCII
name assigned to that mailbox has remained the same since the last networked message was
delivered. This ASCII name verification adds significant time to network message delivery when
messages are sent to group-distribution-list destinations on a remote node.
With Aria 1.2, the system manager can choose to enable or disable ASCII name verification for
nonprivate messages to personal-group or system distribution lists, at the risk that some of the
destination mailboxes were reassigned to new owners, who would be unintended recipients. The
system manager makes this choice in the Node Profile (menu 15.1.3); the choice could be
different for different nodes. Regardless of the choice, the remote node still checks that each
destination mailbox exists, and the sender is told which messages, if any, cannot be delivered.
ASCII name verification is always performed for private messages and for messages to individual
mailboxes.

1-6 Aria 1.2 Release Manual
101–1477–001Edition 2
Control of MWI
With Aria 1.2, using a new field in menu 1.2, Configuration Parameters, the system manager can
choose to disable or enable subscriber control of the message-waiting indicator (MWI) for all
subscribers on the server. If disabled, subscribers are not prompted with options to turn MWI on
or off. This feature can help isolate problems with message-waiting indication, because
subscriber error can no longer occur if subscribers cannot control the setting.
If the system manager disables subscriber control of MWI, the most recent settings chosen by
each subscriber are retained. If a particular subscriber’s MWI is off and the system manager has
disabled subscriber control, the system manager can use menu 9.1, Change Mailbox Profile, to
turn that subscriber’s MWI on. Refer to the System Manager Manual, Addendum II.
Messaging Tutorial
Many subscribers use the server only for telephone answering, rather than also using it to send
messages and reply to messages. With Aria 1.2, the server has two tutorials, one that describes
sending and copying messages and another that describes replying to messages. The system
manager can configure the server to play the appropriate tutorial to any subscriber automatically,
under the following conditions:
-The subscriber does not use rapid prompting.
-The subscriber’s class of service allows sending messages.
-The subscriber has accessed his or her mailbox a consecutive number of times that the system
manager specifies (up to 100) and has not used the following options:
-The tutorial describing sending and copying messages plays when the subscriber has not
used the send message (2) option, the send copy with introductions (6) option, or the send
copy without introductions (6–6) option.
-The tutorial describing replying to messages plays when the subscriber has not used the
reply (8) option or the call sender (8–8) option.
Whenever one of the tutorials is played, a CDR event 30 (TUT) is generated. You can use the
Online CDR utility to search for these events. Refer to the Online CDR User Reference Guide,
P/N 101–1479–000.

Introduction 1-7
101–1477–001 Edition 2
TDD/TTY Support
TDD/TTY as a mailbox language is supported in Aria 1.2. When this language is installed,
hearing- and speech-impaired subscribers can use voice mail and messaging. They use a
Telecommunications Device for the Deaf (TDD) to display text that is equivalent to voice
prompts and to process messages.
A TDD has a keyboard and a display. Like a TeleType (TTY), a TDD receives Baudot tones sent
to it over standard telephone lines and it translates the tones into the corresponding characters for
display. The TDD also generates and transmits Baudot tones for each character typed on its
keyboard. (Octel does not supply TDDs.)
To communicate by telephone with someone who can speak and hear but does not have a TDD, a
hearing- or speech-impaired person with a TDD works with a special operator who has a TDD
and who serves as an “interpreter.” The text typed by the hearing-impaired person is transmitted
as Baudot tones and displayed on the operator’s TDD; the operator then reads it aloud to the
hearing/speaking person. The operator also types the hearing/speaking person’s speech for
transmission to and display on the hearing-impaired person’s TDD. If both people in the call have
TDDs, the TDDs are connected directly to each other during the call, without using an operator.
Messages in the form of Baudot tones can be stored in voice mailboxes and subsequently
retrieved by hearing-impaired people for display on their TDDs. However, when they call the
server, their hearing impairment can prevent them from hearing its voice prompts. To address this
limitation, Aria 1.2 software supports Baudot tones as a new “language” that the system manager
establishes in the subscriber’s mailbox profile. For this language, all phrases supported by Aria
1.2 are recorded in Baudot tones so that, when hearing-impaired subscribers reach their
TDD/TTY mailboxes or a TDD/TTY application, they see the prompts on their TDD displays.
No operator interaction is required to access the message server.
Aria 1.2 software does not translate voice messages to text or text to voice. Hearing- and
speech-impaired users still need assistance with voice messages recorded in their TDD/TTY
mailboxes.
Some TDD/TTY devices use acoustic couplers that allow users to send touch-tones by pressing
keys on the standard telephone set. Other TDD/TTY devices have a special “tone” key that
determines whether numbers pressed on the TDD keyboard are to be transmitted as part of text
or as touch-tones. Users of TDD/TTY mailboxes need to know that numbers in the body of a
message must be typed as text, and numbers that are responses to server prompts must be sent as
touch-tones in “tone” (DTMF) mode. Users who do not have acoustic couplers might have
difficulty using dial-by-name; they would need to determine and enter the touch-tone digit that
corresponds to each letter in the name.
Language type 24 has been redefined as American English (TDD/TTY) in menus 20.4.1, Phrase
Table Initialization and 20.4.3, Set Language Type.
Servers must have Aria 1.2 software installed before you can add the TDD/TTY language. Use a
master drive to add the TDD/TTY language. If several languages are to be added, add TDD/TTY
last.

1-8 Aria 1.2 Release Manual
101–1477–001Edition 2
Application Easy Access
With the Application Easy Access feature of Aria 1.2, outside callers can access an application by
pressing the 1 key during subscriber greetings. The application must recognize the subscriber as a
valid system user. In their mailbox personal greetings, subscribers should briefly describe the
function of the 1key. For subscribers who have recorded extended-absence greetings, the 1key is
ignored if callers press it.
A new field in menu 1.2 defines the type 40 mailbox number for the application that is accessed
when callers press 1while listening to the personal greetings of subscribers. If the system
manager leaves this field blank, the 1 key is ignored, and normal mailbox functions are available
to the caller.
Depending on the application, subscribers might need to access the application and specify
parameters for it before their callers can use it. For example, the function of the application could
be to transfer outside callers who press 1while listening to a subscriber’s greeting to a telephone
number that the subscriber has specified to the application.
Call Processing Enhancement
With Aria 1.2, leading (first-digit) zeroes are permitted for a variety of call-processing functions
of the telephone interface. For example, when a caller reaches an automated attendant that is
configured for transfer by number, the caller can enter an extension number that begins with a
zero; with previous Aria releases, callers were transferred to an operator as soon as they pressed
zero. Refer to the System Manager Manual,Addendum II for Aria 1.2, P/N 101–1476–000, for
details.
The system manager can now prohibit callers from transferring from an automated attendant to
numbers beginning with 0, by entering a 0in the Block Automated Attendant Transfer: field in
menu 6.1, Transfer, Outcall, and Pager Sequences on the SMT.
Port Traffic Statistics Utilities
The Port Traffic Statistics utilities introduced with Aria 1.2 are part of the Port Testing Utilities
options that are only accessible online, in menu 20. They are available to service personnel and
system managers. Refer to Chapter 3 for details on these utilities.

Introduction 1-9
101–1477–001 Edition 2
Node Expansion
With Aria 1.2, the maximum number of network nodes has been expanded from 500 to 999.
The server can have up to 999 OctelNet or administered AMIS nodes in any combination.
Broadcast Messages Blocked from Application
Mailboxes
With Aria 1.2 software, bulletin-broadcast and system-broadcast messages are not distributed to
application mailboxes. The mailbox types that are affected by this change are types 1–7, 10, 12,
29–35, 40, 45, and 61.
With all Aria releases, bulletin-broadcast messages are blocked from mailbox types 11, 20, 21,
28, and 41; system-broadcast messages are blocked from mailbox types 20, 21, and 41.
Administrative-Options and FaxResponse
Prompt Enhancements
Clarifications have been made to the prompts that subscribers hear for the voice-mail and fax
mailbox administrative options after the subscribers select Personal Options, then Administrative
Options.
When callers access FaxResponse and request that a fax be sent in a separate call, the prompt
they hear to specify a fax-machine telephone number has been clarified (in all languages except
British English).
Refer to the Aria 1.2 Screen and Prompt Summary, P/N 101–1496–000, for details.
Feature Option 33 Name Changed from “Mitel
Limited” to “Set Emulation”
On menu 13.7, Display Software Features Installed, the name of feature option 33 has been
changed from Mitel Limited to Set Emulation. This feature option is required for an Octel
Overture 250 with an FLT-M or FLT-A card.

101–1477–001 Edition 2
ONLINE UPGRADE
INSTRUCTIONS
Overview
An online upgrade uses a PC with Octel-proprietary software and phrases. Equipment required to
perform an online upgrade is listed in this chapter.
Consider the following before beginning an online upgrade:
-You cannot run a tape backup at the same time as an online upgrade. If the online upgrade is
running, a scheduled backup will not begin until the upgrade is complete. If a scheduled tape
backup is running, the online upgrade will remain at the System Manager Terminal (SMT)
Main Menu until the backup is complete.
-The Octel Overture 250 or Octel Overture 350 server must function correctly at its current
release. Resolve any errors in the status log or other problems.
-Octel Overture 250 servers in the United Kingdom and Ireland must be at Aria 1.1 software
to upgrade to Aria 1.2. Elsewhere, customers may upgrade directly from Aria 1.0 or Aria 1.1
to Aria 1.2.
-System drive 0, area A, must be redundant with system drive 1, area A. System drive 0, area
B, must be redundant with system drive 1, area B.
-If any IVR phrases are recorded, make the software and phrase areas A and B redundant prior
to performing the online upgrade.
2

2-2 Aria 1.2 Release Manual
101–1477–001Edition 2
-Servers must have Aria 1.2 software installed before you can add the TDD/TTY language
that is introduced with Aria 1.2. Use a master drive to add the TDD/TTY language. If several
languages are to be added, add TDD/TTY last.
-If you use the PC’s COM 2 port rather than its COM 1 port for the online upgrade, and if and
only if the PC has Windows 95 installed, special utilities described in Product Alert 92 must
be installed. The Octel Technical Assistance Center (TAC) provides the diskette that has these
utilities, along with installation instructions. Do not install the utilities from TAC if the PC
has Windows 3.x installed.
-Online Help is available during the upgrade. Press the F1 key from any screen to access the
online Help.
If you are performing an online upgrade remotely, consider the following limitations:
-You cannot use the RDAC for a remote online upgrade of the Octel Overture 250.
-You can use only Hayes V-series ULTRA Smartmodems, 9600 baud.
-You must use a good-quality telephone line. If the telephone line is too noisy, you might need
to stop and restart the upgrade.
-Transmission problems could occur during error correction (checksum/receipt) between the
PC online tool and the server. For example, the PC and the server might lose synchronization
and require that the connection be reestablished.
-You must use the SMT port on the Octel Overture 250 or 350, an ASYNC port on the Octel
Overture 250, or a flex port on the Octel Overture 350; however, you must reboot the server
when using an ASYNC or flex port, if the port is not already established.
-A service person at the remote site must connect and configure the remote capability.
-The service person performing the upgrade must monitor the upgrade while it is in process.
If transmission or error-checking problems cause the upgrade to stop, the service person must
restart the upgrade manually. However, the upgrade tool will start the procedure where it left
off.

Online Upgrade Instructions 2-3
101–1477–001 Edition 2
Check the Major Steps
The following major steps are required for performing an online upgrade:
1. Make sure that the correct equipment is available.
2. Have the engineering option enabled.
3. Clear the AMIS queue.
4. Verify the system boot area.
5. Disconnect the SMT, and connect the PC to the server.
6. Install the online-upgrade tool on the PC hard drive.
7. Verify the values in the PC Setup Menu.
8. Load software and phrase diskettes on the PC hard drive.
9. Perform the automatic upgrade.
10. Verify the upgrade.
11. Reset AMIS networking, if necessary.
12. Reset the boot area, and boot the new software.
13. Have the engineering option disabled.
14. Make software and phrase areas redundant.
These steps are described in the following sections.
Caution!
If the online upgrade fails at any point during the procedure, call
the Octel Technical Assistance Center (TAC) for assistance. Do
not attempt to resolve problems by yourself.