Installation overview

This is an overview for installing or upgrading the Avaya Modular Messaging software in an Avaya Message Storage Server (MSS) configuration. A new installation includes both hardware and software. A Modular Messaging system contains two types of servers: a Message Storage Server (MSS)—either the Message Storage Server Standard configuration (MSS-S) or the Message Storage Server High-availability configuration (MSS-H)—and one or more Messaging Application Servers (MAS). A Modular Messaging system might also include a supplementary server to handle resource-intensive services, such as the Tracing service, or to provide offline access storage space for subscriber messages. Supplementary servers can be provided by Avaya or the customer.

With a new installation you need to obtain the required equipment and information, set up the system, configure it, test it for correct operation, and back up the data when done. Complete installation information is in the MSS Installation and Upgrades guide (pdf) and the Installation and upgrade checklists for Avaya Modular Messaging (pdf).

Note: The MSS Installation and Upgrades guide (pdf) also contains procedures and checklists for upgrading an installed Modular Messaging system from an earlier release. For complete steps on upgrading software, see Chapter 8: Upgrading Modular Messaging software.

Installing Modular Messaging in an MSS configuration requires the following steps:

1. Completing preinstallation requirements (Chapter 1)
• Obtaining the Data Collection Tool (DCT) data file. Usually a person responsible for installation planning uses the Modular Messaging DCT to create a DCT data file in advance of the installation. This person might be the project manager, customer representative, or other responsible party. The DCT data file has the extension mmdct, such as sitefile.mmdct. You will need the DCT data file to configure the MSS and each MAS.
• Downloading required software and documentation. Before going to the customer site you need to download the latest software and documentation from the Avaya Support Web site. The software includes the latest Outlook Client and DCT. Documentation includes the latest configuration notes and installation procedures.
• Reviewing security considerations, test-equipment recommendations, and installation tool requirements.
• Performing initial system setup. This includes some switch and LAN administration and corporate Windows domain setup (if the system will use the corporate Windows domain).
• Verifying site requirements, which include:
• Environmental requirements for the system including temperature, humidity, and heat output in BTUs.
• Weight, space, and installation area considerations such as air flow and access.
• Customer-provided cabinet specifications.
• Power and ground requirements.
• Demarcation points for PBXs (switches) and the corporate LAN.


2. Installing the system hardware (Chapter 2)
• Unpacking instructions and equipment inventory.
• Identifying the servers as either MSS, MAS, or MAS-like servers for handling resource-intensive services or offline storage. Differences between various server models (depending on the motherboard or redundant power supplies used) are described.
• Installing the uninterruptible power system (UPS) and one or more optional extended battery modules (EBMs) in either a rack-mount or stackable configuration.
• Installing the MSS-S or MSS-H and MAS units in a rack-mount or stackable configuration. This includes attaching the front bezel, connecting power cables, and connecting the MAS Dialogic port boards (if present).
• Installing the keyboard, video, and mouse (KVM) switch in a rack-mount or stackable configuration.
• Connecting the servers to the Ethernet switch for the private LAN, and to the corporate LAN.
• Connecting the MAS external modem.
• Connecting the MSS Remote Maintenance Board (RMB) and external modem (required for international sites).
• Turning on the servers.



Note: Procedures for installing a customer-provided server to handle resource-intensive services (such as the Tracing service) or to provide offline access storage space for subscriber messages on large systems, are described in Appendix G.



3. Performing initial MSS administration (Chapter 3)
• Setting up the console and logging into the MSS server. Because the system is not yet administered, you can access the MSS only from the console (monitor) that is connected to the KVM switch.
• Setting the time and date.
• Setting up network addressing for the corporate and private LANs.
• Setting up the MSS local machine profile.
• Setting up trusted servers for each MAS, the Message Waiting Indicator (MWI) server (if present), and a supplementary server that is running the Tracing service (if present).
• Updating the IMAP4 password, and then rebooting the MSS.



Note: Procedures for installing new system software from a disc are provided for the MSS in Appendix D and for the MAS in Appendix E, if needed.



4. Configuring the MAS (Chapter 4)
• Displaying an MAS from the console. Because the system is not yet administered, you can access MASs only from the console (monitor) that is connected to each server via the KVM switch.
• Configuring an MAS using an existing DCT data file. The DCT data file should have been created prior to being on the customer site.
• Preparing the new server, which includes installing anti-virus software, updating Microsoft Windows, changing the default LAN names, changing power management, and entering RAS IP addresses.
• Configuring MAS port boards and switch integration (with or without Dialogic port boards).
• Configuring the voice mail system:
• Configuring required domain-wide features, including languages, verification of services started, TUI and audio setting configurations, PBX type configurations, serviceability settings, and license installation.
• Configuring services and features, including Call Me, Notify Me, Message Waiting Indicator, fax service, languages or text-to-speech, and offline access to messages.
• Configuring Modem Dialout alarming (if applicable), port boards, and switch integration.
• Verifying basic operations, including call-handling capability, alarm setup, and Tracing service operation.



Note: The steps in this chapter must be repeated for every MAS in the system. Procedures identify whether a step applies to the first MAS, or to a subsequent MAS. Installers should do acceptance tests if possible after administering every MAS, if the port boards and switch administration permit it. Some configurations require all MASs to be installed before acceptance tests can be run.



5. Completing initial MSS administration (Chapter 5)
• Updating MAS host information.
• Placing the MSS in a Windows domain. You can place the MSS in either a private or corporate Windows domain, depending upon customer requirements.
• Administering classes of service for required special mailboxes and for test subscribers.
• Setting up special mailboxes for the postmaster and for fax service (if used).
• Controlling system-administration access.
• Adding test subscribers with the appropriate telephone user interface (TUI) for acceptance testing.
• Installing any software updates.
• Installing a supplementary server, if applicable.


6. Performing acceptance tests (Chapter 6)
• Setting up optional monitor tools, including the Operational History Viewer and the port monitor.
• Running acceptance tests:
• Leaving a call answer message.
• Retrieving test messages in integrated mode.
• Creating and sending a test message in nonintegrated mode.
• Testing the outcalling capability.
• Creating and printing a fax message.
• Removing test subscribers.


7. Setting up MSS support and making system backups (Chapter 7)
• Setting up logins and remote access on the MSS, including remote maintenance board and external modem activation, system registration in the Avaya Automatic Registration Tool, login and password administration, and point-to-point protocol server configurations.
• Setting up alarming on the MSS by specifying MSS alarm origination and testing alarm origination.
• Using the DCT to analyze the current configuration and copying the DCT data file for backup.
• Backing up the system.
• Completing the installation and turning over the system to the customer.

Top of page