Installation overview

An S3400-family Message Server system always 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 Server (MAS) units. A Modular Messaging system might also include one or more supplementary servers to handle resource-intensive services, such as Tracing Server service or the Reporting Tool, or to provide offline access storage space for subscriber messages. Supplementary servers can be provided by Avaya Inc. or the customer. All servers in the system are connected to the corporate LAN and through a private Ethernet LAN to operate as a unified system.

A new S3400-family system installation requires obtaining the required equipment and information, setting up the system, administering it, testing it for correct operation, and backing up the data when done. Complete installation information is in the Installation guide (pdf). An editable Microsoft Word version of the Installation and upgrade checklists for Avaya Modular Messaging is available (Word document or pdf).

Note: The Installation guide (pdf) also contains planning forms, procedures, and checklists for upgrading an installed Modular Messaging system from an earlier release to the most current one. For complete steps on updating software, see Upgrading Modular Messaging R1 software (Chapter 6).

Installing an S3400-family system requires the following steps:

1. Completing the planning worksheets (Appendix A). Requires consultation with the customer and the responsible LAN, switch, and messaging administrators, as noted on the various forms. An editable Microsoft Word version of the planning forms is available for recording required information (see System planning forms for Avaya Modular Messaging Word document or pdf).

Caution! Correct information must be obtained in advance, or damage to the operation of the customer LAN could occur.

• S3400-family system planning form including the host and NetBIOS names for the various MSS and MAS machines, corporate and private fully qualified domain names (FQDN), aliases, voice mail and Windows domain names, IP addresses, WINS information (if required), and DNS server names and search order.
• A password table for trusted servers.
• Logon accounts and password table for the various accounts on the MAS machines including the domain administrator account, local administrator account (for subsequent MASs), messaging services, technical support, customer access, and safe mode login.
• MAS list of services to install including Call Me Server, Message Waiting Indicator Server, Mailbox Monitor Server, Caller Applications Editor, Fax Server, Tracing Server, and Voice Server Prompt Files.
• Switch and messaging information including port board numbers and extensions, direct inward dialing (DID) numbers for the hunt groups and modems, special subscribers for postmaster and fax, and test subscribers.
• Support information including the type of alarming to be used at this site (INADS, SNMP, or none), the product IDs for the MAS VMD and MSS, INADS or SNMP alarming information (if used), required logins for the MSS, and point-to-point (PPP) connection information for the MSS modem.
• For upgrades only, an upgrade planning form. Release 1.0 upgrades also require a license activation request form. Required information varies by region, and whether or not technical support through remote access will be used. Information includes the voice mail domain identification (VMD ID), text-to-speech (TTS) sessions, number of purchased seats, customer contact details, and (if applicable) remote access information.

Note: An editable Microsoft Word version of the planning forms is available. See System planning forms for Avaya Modular Messaging (Word document or pdf) on this CD.

2. Reviewing preinstallation requirements (Chapter 1). This includes:
• Acquiring the required documentation from the Avaya Support Web site (such as the configuration notes) or the documentation CD (such as backup procedures) as needed.
• Reviewing security considerations for the customer, system, physical site, and passwords.
• Verifying initial PBX (or switch) and LAN administration.
• Obtaining required tools and test equipment.
• Verifying site requirements including:
  • 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.
3. Installing the system hardware (Chapter 2). This covers unpacking and assembling the various system components and physically connecting them to the customer's equipment or designated demarcation point. Information includes:
• 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 S3400-family servers (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 S3400-family servers to the Ethernet switch for the private LAN, and to the corporate LAN.
• Attaching ferrites to required cables as needed.
• Connecting the MAS external modem.
• Connecting the MSS Remote Maintenance Board (RMB) and external modem (required for international sites).

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

4. Powering up the system and performing initial MSS administration (Chapter 3). This includes powering up the hardware, logging in to the MSS server, and beginning MSS administration as follows:
• Setting up the monitor.
• 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 Server service (if present).
• Updating the IMAP4 password, and then rebooting the MSS.

Note: Procedures for installing new system software from CD or DVD are provided for the MSS in Appendix D and for the MAS in Appendix E if needed.

5. Administering the MAS (Chapter 4). This includes:
• Setting up the MAS for regional settings, date, and time appropriate for your locale.
• Changing the machine name (the MAS computer name or host name), and the default name for the corporate LAN and private LAN.
• Setting up the MAS modem dial-in information.
• Assigning IP addresses for the corporate and private LANs, including DNS and WINS information if needed, and then testing the connections using ping.
• Setting up the Windows domain for MAS#1 (the first MAS is the domain controller), or adding a subsequent MAS to the Windows domain.
• Installing and administering anti-virus software on the MAS.
• Installing the latest Microsoft Windows system updates, security patches, and hot fixes.
• Changing the names of the corporate and private LANs, and specifying the LAN search order.
• Creating required Modular Messaging accounts for MAS administration, remote technical support, and customer access.
• Selecting and installing Modular Messaging software components for this MAS.
• Running a system upgrade if required.
• Configuring the MAS for the message storage server (MSS), voice mail domain, LDAP and IMAPI service, and offline storage (if required).
• Applying the required software patch for Release 2.
• Disabling unused Windows services (if they are not used on this MAS).
• Setting up remote access for each MAS.
• Configuring the port boards (if present) using the configuration notes and the Intel Dialogic Configuration Manager. Boards can be Dialogic analog, Digital Set Emulation (DSE), or T1- or E1-QSIG boards. Analog boards might require a customized tone set file (TSF) to work correctly (see Appendix C).

Note: The Voice Card Installation Guide used for Unified Messenger is not current for the S3400 system. Relevant information for configuring and testing Dialogic boards is included in the Installation guide (pdf).

• Testing the port boards for incoming call connectivity and outcalling using the Dialogic Line Tester - Line Test Application (or DLTest) program.
• Configuring the voice mail system using the Voice Mail System Configuration (VMSC) program. This includes setting up the features you installed (such as Call Me, Fax, and Message Waiting Indicator Servers), as well as Telephone User Interface (TUI) operation, access (security) permissions, Text-to-Speech (TTS) parameters, offline access, serviceability (INADS or SNMP alarming), licensing activation and setup, PBX type and specific values, Telephony Interface, and PBX Integration using the appropriate configuration notes for your switch or PBX.
• Setting up and starting MAS messaging services and recovery conditions, including the Tracing Server (if installed).
• Verifying the alarming setup if INADS or SNMP alarming is used (requires the alarming destination to be administered and available).

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.)

6. Completing the installation (Chapter 5). This includes:
• On the MSS:
  • Administering Internet messaging options to enable any required protocols and access permissions for desktop clients (such as IMAP4 client access, LDAP and SMTP public LAN access).
  • Updating MAS host information for public (corporate) name, IP address, and any required public and private aliases.
  • Placing the MSS in the Windows domain.
  • Administering classes of service to support subscribers and particular features.
  • Setting up special mailboxes for the postmaster and for fax service (if used).
  • Administering test subscribers with the appropriate telephone user interface (TUI) for acceptance testing.
• On a test telephone: Performing acceptance tests for the system in both integrated and nonintegrated mode. Voice mail, call answer, fax (if installed), and outcalling features should be tested.

Note: For a multiple-MAS system, use the Port Monitor on the MAS to track test calls. Some configurations require all MASs to be installed before acceptance tests can be run, depending on the port boards used and the switch administration.

• On the MSS:
  • Removing any test subscribers you previously set up.
  • Setting up required logins and remote access on the MSS, including administering logins and passwords, specifying local and remote IP addresses as required for point-to-point protocol (PPP) remote access, and activating the RMB modem (required for external modems only).
  • Setting up INADS or SNMP alarming origination as required, and testing alarm origination (requires the alarming destination to be administered and available).
• On the MAS:
  • Setting up scheduled backups and running an attended backup of the MAS system data.
  • Setting up scheduled disk maintenance (Disk Defragmenter tool and chkdsk).
• On the MSS: Setting up scheduled backups and running an attended backup of the MSS system data.

Top of page