TOC Index Search

 

Planning an Upgrade to Intuity AUDIX Release 5

Overview

An upgrade involves replacing a previous release of an Intuity AUDIX system with a new system and copying all customer data to the new system.

Upgrade Planning covers upgrade planning considerations and tasks to implement a successful upgrade to an Intuity AUDIX Release 5 system. The information in this section is intended for the sales team, including account executives and project managers who are responsible for coordinating the upgrade with the customer and the technician.
 

Important! This section references other sections of the Intuity Messaging Solutions Release 5 documentation CD. If you print this section out and use it without the CD, you will not be able to access some of the features and upgrade information referenced here.


 

Note: If you are migrating to Intuity AUDIX Release 5 from an Avaya voice messaging product other than Intuity AUDIX, see Planning a Migration for more information.

This section includes information about:

Use the Planning Checklist at the end of this section to help track these upgrade tasks.

Upgrade Versions

You can upgrade from an earlier Avaya Intuity AUDIX release to a new Release 5 system or upgrade within Release 5 as you move to a larger system. The following tables show upgrade possibilities.


 
Table: Upgrades Possible from Release 3 IP55, 4.3-6, 4.4-5, or 4.4-7 to Release 5
Upgrading from
To Map/5P*
To MAP/40P
To MAP/100P
MAP/5
X
X
X
MAP/40S
X
X

MAP/40

X
X
MAP/40P

X
X
MAP/100


X
MAP/100P


X

*This upgrade is to MAP/5P, version 3 (V3) only.


 
Table: Upgrades within Release 5
Upgrading from
To Map/5P
To MAP/40P
To MAP/100P
MAP/5P

X
X
MAP/40P


X

Upgrade Planning

An upgrade to an Intuity AUDIX Release 5 system involves replacing the computer and copying customer data from a previous release to the new Release 5 system. The new system is powered up and placed in service. The old system is then returned to the factory.

Before the actual upgrade, the sales team is responsible for working with the correct domestic or international sales support teams. Planning procedures are different for domestic or international customers:

See the Planning Checklist for a sequential list of tasks.

Pre-Upgrade Analysis - Domestic

The pre-upgrade analysis consists of determining the customer's specific requirements. The sales team must request a "SysEval" run on the existing Intuity AUDIX system. You can find the form one of two ways:

Follow the directions on the form to submit the information to the SDSC.

The results of the SysEval test are sent to the Sales team. The Sales Team must use this information to compare the results to the configurator. Any required changes should then be made to the configuration.
 

Note: The new Intuity AUDIX system must have at least the same features and capacity as the old Intuity AUDIX system.

Download and complete a Reusable Upgrade Kit (RUK) request form. Find the form one of two ways:

The RUK form must be completed, signed, and returned to the MMISC center before the RUK can be scheduled for the upgrade. The RUK must be ordered at least 20 days in advance of the upgrade and is sent to the project manager two days before the scheduled upgrade date.

Pre-Upgrade Analysis - International

The pre-upgrade analysis consists of determining the customer's specific requirements. The Center of Excellence completes the analysis to ensure the technical accuracy and correct implementation of a customer's upgrade.

Once the analysis is complete, the configuration is verified using OMNI. The upgrade request is uploaded from OMNI to IAS2. The local project manager requests the RUK from COE. The Center of Excellence coordinates and ships the Reusable Upgrade kit to the project manager.

Upgrade Issues

Several issues should be considered when planning an upgrade to an Intuity AUDIX Release 5 system.

Upgrade Implementation

To ensure a successful upgrade, verify the following before proceeding with the upgrade:

Upgrade Components

Verify that the new system was shipped with all the necessary components. Before starting the upgrade, the technician should verify the following:

The following documentation is useful during the upgrade and should be available.

See New System Install, Installation Prerequisites for detailed information.

The RUK is sent 2 days before the upgrade. Verify that the RUK contains the following:

See the Upgrade Procedures documentation for a detailed description of the contents of the RUK.

Site Planning

The new Intuity AUDIX Release 5 system is shipped to the site prior to the upgrade. The technician unpacks and assembles the system on the day of the upgrade.
 

Note: If time permits, the new system could be assembled and powered up earlier to verify that it was not damaged in shipment. This helps to ensure a smooth upgrade.

When only one monitor is available during the upgrade, the monitor is shared between the existing system and the new system. Adequate space and power must be available for both systems. Typically, video cables are 10 feet long. Therefore, if one monitor is used, the new and existing systems can be no more than 20 feet apart. The monitor is connected to both systems through an A/B switchbox that is part of the RUK.

Additionally, the new Release 5 system must be located so that the cables from the existing system can be swung to the new system once the upgrade is complete.

Space and Power Requirements

The site must have adequate space and power for the new system. See Preparing the Site for the physical requirements for the installation site including weight and space considerations and power requirements.

In addition to the power requirements outlined in Preparing the Site, the following requirements apply:

Running the Upgrade

The data is transferred from the existing system to the new system while the existing system is out of service. Both the existing and new system's voice services are stopped while all data files are transferred. Service is restored on the new system after the transfer is complete.

The following is an overview of the upgrade sequence that the technician performs:

The following table shows estimates of the time required for upgrades. The difference between the minimum and maximum time required depends on the amount of data to be transferred. These are estimates only and may not reflect the exact time it takes to upgrade an individual system.
 
Table: Upgrade Time Estimates From One Release to a New Release
Type of Upgrade
Time Out of Service
Total Time Required for the Upgrade

Maximum
Minimum
Maximum
Minimum
MAP/5 to MAP/5P
5
2
6
4
MAP/5 to MAP/40P
4
2
6
4
MAP/5 to MAP/100P
4
2
6
4
MAP/5P to MAP/40P
4
2
6
4
MAP/40 to MAP/40P
4.5
2
6
4
MAP/40P to MAP/100P
5
2
6
4
MAP/100 to MAP/100P
7
3.5
10
4.5

Table: Upgrade Within the Same Release Time Estimates
 
Type of Upgrade
Time Out of Service
Total Time Required for the Upgrade

Maximum
Minimum
Maximum
Minimum
MAP/5P to MAP/40P
5
2
6
4
MAP/5P to MAP/100P
5
2
6
4
MAP/40P to MAP/100P
4
2
5
3

Custom Announcements and Fragments

Custom announcements are transferred during the upgrade but might not be activated at that time. The system administrator might have to readminister custom announcements as part of the upgrade procedure. Depending on the complexity and the number of customized fragments, readministering the custom announcements could add an additional 30 minutes to the time required to perform the upgrade.

The project manager should work with the customer to determine how to address custom announcements during the upgrade.

The custom announcements from the old system might not be applicable on the new system because new announcements are added, changed, or reserved when an Avaya Intuity Messaging Solutions Release 5 system replaces a previous system. To find the names of the active announcement set, check page 3 the System Parameters Features screen.

The project manger should work with the system administrator to make a list of announcements the customer has customized or recorded. The system administrator should understand how each fragment was customized. For example, whether it was re-recorded as a fragment, replaced a fragment with silence, or a blank. This list will help identify announcements that need to be reinstated after the upgrade. How the customized announcements are reinstated depends on two things:

NetCare Consulting Service must be involved if the announcement set was modified. Schedule any work with NetCare Consulting Services in advance of the upgrade.

See Customizing Announcements for detailed information about creating, customizing, and activating an announcement set.

Release 5 Features

Intuity AUDIX Release 5 offers new features that enhance maintainability, availability, reliability, and serviceability. These features are listed in the table for Intuity AUDIX Release 5 New Features. For a description of these features, see What's New with Release 5 and What's New in Release 5.1. For a description of all of the supported features, see Supported Features.


Table: Intuity AUDIX Release 5 New Features
 
User Features
Announce name on transfer
Fax Extended Dialing
Aria telephone interface
Removed Forced Annotation when forwarding a message from the TUI
Email status messages
Speech recognition capabilities
Email text-to-speech preprocessing filter

Administration and System Changes
Administration history log
Alarm strategy improvements
AMIS networking activation
New installation/update utility
Backup/restore improvements
Nightly disk tests
Network configuration improvements
RAID disk management
Replacement of the AUDIX file system
Subscriber database conversion
Subscriber and system improvements
Enterprise Directory Gateway
Software version management
Reboot improvements
Feature activation improvements

Security Enhancements
Access Security Gateway (ASG)
Automatic termination
Identification suppression
Security notification

Pre-Upgrade Administration

The project manager should work with the system administrator to make sure that the necessary administrative tasks are performed before the upgrade. Certain information about the upgrade should be provided to the subscribers at one week and one day prior to the scheduled upgrade. In addition, certain system administration configurations must be verified and the information available.

One Week in Advance

The administrator should:

One Day in Advance

The administrator should:

Post-Upgrade Administration

After the system upgrade is complete, the following administrative tasks must be performed:

Administering Fax Messaging

If the upgrade is from Intuity AUDIX Release 3 or Release 4, Fax Messaging may need to be administered. If Fax Messaging is already administered, skip this section. For complete details about how to administer fax, see Fax Messaging.

Administering the Intuity AUDIX Application for Fax Messaging

To administer the Fax Messaging feature, the Intuity AUDIX system must be administered for fax send-and-receive capabilities using the AUDIX administration screens. This involves

Administering the Intuity AUDIX Platform for Fax Messaging

Once the system is administered for Fax Messaging, the Intuity AUDIX platform must be administered. This involves:

Administering Subscribers for Fax Messaging

Fax Messaging can be administered

Administering Guaranteed Fax

Guaranteed Fax can be administered to provide coverage for busy or out-of service fax print destination machines.

Administering Email (Internet Messaging)

If the upgrade is from Intuity AUDIX Release 3, email is not administered. If the upgrade is from Intuity AUDIX Release 4, email might already be administered for use with the Message Manager feature. If email is already administered, skip this section. For complete details about how to administer email, see Internet Messaging.

Administering the Intuity AUDIX for Integration with Email

The following are required to administer email:

Administering Passwords

After the database is restored on the new system, certain passwords need to be administered. Before the upgrade, record the VM, SA, and IMAPI passwords. After the upgrade, these passwords must be readministered on the new system and, if the Enhanced List Application (ELA) was part of the customer's old system, in the ELA feature.

Administering New Features

If new features were added during the upgrade, these features must be administered. For details about how to administer the following new features, click the feature name in the following list.

Planning Checklist

The following table is a checklist of steps that should be performed before and after an upgrade begins. The sales team can use the checklist to help track upgrade tasks.
 

Note: If the system being upgraded contains custom announcements, Tasks 10, 11, 12, and 21 should be performed. If the system does not contain custom announcements, these tasks can be skipped.


 
Table: Upgrade Planning Checklist for Release 5
Task
Description
Notes
Complete
Preimplementation
The account representative contacts the customer and the customer indicates interest in upgrading to Release 5.


For domestic upgrades, the account representative:
    • Makes SysEval request
    • Compares SysEval results to Intuity AUDIX (Upgrade) configurator and makes any required changes.
    • Completes the RUK request form
For international upgrades, the account representative works with their Center of Excellence (COE) to complete the appropriate forms.


Account representative informs the customer of the presales traffic analysis.


For international upgrades, the project manager requests the RUK from the COE.


Verify that the customer signed the upgrade contract and Customer Notice pre-sales letter.


For domestic upgrades, verify that the Reusable Upgrade Kit form, Form 1495, is faxed to the MMIS center at least 20 days before upgrade.
For international upgrades, check with the Center of Excellence for timing to submit your RUK request.


Implementation
The product manager begins coordination and scheduling of the upgrade, including
    • Customer notification and coordination
    • Coordination of onsite personnel
    • Verification of remote access line for replacement system


The RUK ships to the product manager two days before upgrade.


The factory ships the new equipment.


Upgrade - Pre-Administration
The customer transcribes paper copies of custom announcements.


The customer determines the type of announcement set that has been used.


The project manager contacts Netcare Professional Services if the announcement set needs to be modified.


The customer plans for replacement system site near the existing system.


If the customer uses traffic data on a regular basis, the customer runs the appropriate traffic reports immediately prior to the start of the system upgrade


The customer removes old mailing lists, old messages, and inactive users to reduce the size of the database.


One week before upgrade, the customer distributes information about the upgrade to subscribers


Two days before the upgrade, the project manager calls the remote maintenance center to verify that all required documentation and software has been sent.


One day before the upgrade, the customer distributes information about the upgrade to subscribers.


One day before the upgrade the customer should record the SA, VM, and IMAPI passwords for the technician.


The technician performs the upgrade supported by the MMIS center or the international center.


Post Upgrade

The customer administers any new features.


If necessary, the customer readministers custom announcements.


After readministering the password, the technican returns the password worksheet to the customer.


The technician inventories and returns the RUK to the MMIS center or the designated international center.


The technician returns the old system to the specified Avaya location.


The account team removes the PEC codes for the old equipment to ensure the customer is billed only once for maintenance.


The technician or project manager registers the new Intuity AUDIX system with the Information and Database Services (INADS).



Avaya Communication
http://www.avaya.com
Avaya UCS Information Development
TOC Index Search