Data Collection Tool

Transcription

1 Data Collection Tool June 2009

2

3 Contents Chapter 1: What is the Data Collection Tool?...5 Chapter 2: Use of the DCT Data File in MM Configuration...7 Chapter 3: Obtaining a current version of the Data Collection Tool...9 Chapter 3: Creating and Updating a DCT file...11 Creating a DCT file for a new installation...11 Creating a DCT file for an upgrade...12 Creating a DCT file for adding an MAS to an existing system...14 Updating a DCT file...16 Chapter 5: Backing up a DCT file...19 Chapter 6: DCT page and field status indicators...21 Chapter 7: DCT page and field descriptions...23 Select the DCT configuration to use field descriptions...23 Customer Information...24 Customer details field descriptions...24 Regional settings field descriptions...25 MM servers...25 Modular Messaging configurations...25 Message store field descriptions...26 Voice Mail Domain...27 Voice Mail Domain field descriptions...27 Networking...29 Corporate MM server networking details...29 Corporate network details field descriptions...29 Windows domain field descriptions...31 Corporate MM server networking details field descriptions...32 Aliases and ART nicknames field descriptions...34 Private network field descriptions...34 Message store setup...35 Exchange message store field descriptions...35 Domino message store field descriptions...36 Accounts and passwords...38 MSS passwords field descriptions...38 MAS accounts and passwords field descriptions...39 Logon accounts and passwords...40 Logon accounts and passwords field descriptions...41 MAS service account field descriptions...42 Trusted servers...43 Optional MSS trusted servers field descriptions...43 Additional optional MSS trusted servers field descriptions...45 TTS sessions and languages...46 TTS and announcements field descriptions...46 MAS servers...46 MAS servers and Modular Messaging services...46 Guidelines for configuring Modular Messaging services...48 MM service selection field descriptions...48 Data Collection Tool June

4 Contents Tracing field descriptions...49 Web Subscriber Options server...50 Web Subscriber Options field descriptions...50 Web Client server...51 Web Client server field descriptions...52 Language packs...52 Language packs field descriptions...53 Offline access field descriptions...53 Message networking field descriptions...54 PBX integration...54 Switch integration method field descriptions...54 Switch integration information field descriptions...55 Extensions and switch ports field descriptions...58 Dial Plan...59 Access Telephone Numbers field descriptions...65 Other information for PBX integrations...66 Other information field descriptions...67 Mailbox information...68 System mailboxes field descriptions...68 TUI types and test subscribers field descriptions...70 Extended lists...72 Extended lists field descriptions...73 Classes of service field descriptions...73 Caller applications field descriptions...74 AAA configuration...74 AAA server...74 AAA configuration field descriptions...74 Support and maintenance...77 Product information field descriptions...77 Remote Access IP addresses field descriptions...77 Alarming information...78 Alarming information field descriptions...79 Password guidelines...81 MSS login and PPP information field descriptions...81 Clients...83 Client applications field descriptions...83 Notes...84 Notes field descriptions...84 Index Data Collection Tool June 2009

5 Chapter 1: What is the Data Collection Tool? The Data Collection Tool (DCT) is a standalone application, delivered on the Avaya Modular Messaging Application Server Software DVD and available from the Avaya support Web site. You can enter required data into the DCT or use the DCT to analyze an existing system. The DCT stores the data in the form of a DCT file. You use this file as input to the Modular Messaging Configuration Wizard (MMCW) when you install, upgrade, add, or recover a Messaging Application Server (MAS). Data Collection Tool June

6 What is the Data Collection Tool? 6 Data Collection Tool June 2009

7 Chapter 2: Use of the DCT Data File in MM Configuration The DCT file generated using the Data Collection Tool (DCT) helps in automating the initial administration and configuration of your Modular Messaging system. You can use the DCT file for the following: Install a Modular Messaging system. Analyze a Modular Messaging system. Add an MAS to an existing Modular Messaging system. Upgrade an MAS in an Avaya MSS system. Upgrade an MAS in a Microsoft Exchange system. Upgrade an MAS in an IBM Lotus Domino system. The DCT helps you to store data pertaining to your Modular Messaging system in the form of a DCT file. The technician, project planner, system administrator, or any other designated expert can enter the necessary data into the DCT executable file. Once the necessary data is entered, the DCT saves the data in a DCT file with the file extension *.mmdct. You can later select this DCT file as an input during the Modular Messaging configuration. The Modular Messaging Configuration Wizard (MMCW) uses the data in the DCT file to automatically perform the initial administration and configuration of your Modular Messaging system. Related topics: Obtaining a current version of the Data Collection Tool on page 9 Creating a DCT file for a new installation on page 11 Creating a DCT file for an upgrade on page 12 Creating a DCT file for adding an MAS to an existing system on page 14 Updating a DCT file on page 16 Data Collection Tool June

8 Use of the DCT Data File in MM Configuration 8 Data Collection Tool June 2009

9 Chapter 3: Obtaining a current version of the Data Collection Tool Before creating a Data Collection Tool file for a new installation, upgrade or disk failure recovery, you must download the current version of the Data Collection Tool. 1. Check the Avaya support Web site for the current version of the DCT. 2. Download the MMDCT.exe file to an external USB storage device. 3. Insert the USB storage device into a USB port on the computer that you are using to create or update the DCT file. Related topics: Updating a DCT file on page 16 Creating a DCT file for a new installation on page 11 Creating a DCT file for an upgrade on page 12 Creating a DCT file for adding an MAS to an existing system on page 14 Use of the DCT Data File in MM Configuration on page 7 Data Collection Tool June

10 Obtaining a current version of the Data Collection Tool 10 Data Collection Tool June 2009

11 Chapter 3: Creating and Updating a DCT file Creating a DCT file for a new installation Use this procedure to manually enter information required to install the new Messaging Application Servers (MAS) and message store into the Data Collection Tool. The technician, project planner, system administrator and other designated experts who are responsible for the installation enter required information prior to the installation. Prerequisites Obtain a current version of the Data Collection Tool. Verify that you have inserted the USB storage device with the current DCT in a USB port on the computer you are using. The DCT creates a DCT file with the file extension *.mmdct. Multiple users with different project responsibilities can run the tool and enter data in a common file. Use the following procedure to create a single DCT file for all MASs in the Voice Mail Domain. When creating a DCT file manually, you can run the DCT on any Microsoft Windows computer. Caution: With a Modular Messaging MSS configuration, do not use the same DCT file for multiple systems in a networked environment. The name of the private Windows domain is automatically generated by the DCT. You can modify the name of the private Windows domain. This name must be unique throughout the messaging network and should not be the same as the corporate Windows domain name. If the private Windows domain name is duplicated anywhere in the network, you must reinstall Modular Messaging on all affected servers to correct the problem. 1. Start the DCT by double-clicking the MMDCT.exe file. 2. On the Select the DCT Configuration to use page, do one of the following: To create a new DCT file, select Create a new file and click OK. To update the most recent DCT file, select Use the last file created and click OK. To update a different DCT file, select Choose a file to use and click OK. Browse to the file, select it, and click Open. 3. Enter data on each DCT page. Data Collection Tool June

12 Creating and Updating a DCT file a. Click Next and Back to navigate between pages. b. To check that the values that you entered in a page are valid and error-free, use the Next and Back button to navigate to a different page and then back to the page where you entered the data. DCT page and status indicators display errors and omissions that must be corrected before the file is complete. When data is complete and valid, the Complete button appears at the bottom of the page. c. Click Help on any DCT page for field definitions and valid field values. 4. To save or print the DCT file at any time during data entry, click Save or Print. Multiple users can enter data over multiple sessions. 5. When you are ready, click Complete and follow any instructions to save changes. 6. Copy the DCT file to an external USB storage device and give it a name that uniquely identifies this customer installation. When all information is complete and valid, the technician can take the DCT file to the customer site and this file can be used in conjunction with the Modular Messaging Configuration Wizard for the installation. Related topics: Obtaining a current version of the Data Collection Tool on page 9 Use of the DCT Data File in MM Configuration on page 7 Creating a DCT file for an upgrade Use this procedure to create a DCT file for an upgrade by using the Data Collection Tool to analyze the existing system. Prerequisites Obtain a current version of the Data Collection Tool. Verify that you have inserted the USB storage device with the current DCT in a USB port on the computer you are using. Ensure that the following are in place: The Modular Messaging system is working properly. All MASs, the message store, and the supplementary server, if used, are running. Modular Messaging services are active. Use this procedure only for an Avaya MAS upgrade from a Modular Messaging pre-3.0 release to Release 5.1. An upgrade from Release 3.0 or later to Release 5.1 does not require the DCT. 12 Data Collection Tool June 2009

13 Creating a DCT file for an upgrade 1. Log on to a Messaging Application Server (MAS) that you are upgrading using the Modular Messaging service account that was used to install the Modular Messaging services, such as mmacct. With the MSS configuration, this is the service account. With the Microsoft Exchange and IBM Domino configurations, this is the customer account. Note: With the MSS configuration, it is important that you use the service account. If you use any other account, the DCT cannot collect all required data, specifically, the IMAP, LDAP, and MWI passwords. 2. Start the DCT by double-clicking the MMDCT.exe file. 3. On the Select the DCT configuration to use page, select Analyze existing system and click OK. 4. When the DCT prompts you whether to use an existing DCT file, do one of the following: If you are upgrading a single MAS or analyzing the first MAS in a multiple- MAS system, click No. If you are analyzing subsequent MASs after the first in a multiple-mas system, click Yes. Browse to the file that you created when you analyzed the previous MAS. Select the file and click Open. 5. On the MM System Analysis page, select the MAS that you want to upgrade. Note: In a multiple-mas system, select the MASs in numeric order, first to last. If you are upgrading to an S8730 server, you can choose to decrease the number of MASs in the voice mail domain (VMD). For more information about moving MM services, see Avaya Modular Messaging S8730-Family Hardware Maintenance and Additions. At the completion of the upgrade, all MASs in the voice mail domain (VMD) must be running the same release. If you do not upgrade an MAS, do not include it in the VMD. 6. Click Start. The system displays the progress of the analysis. When analysis on this MAS is complete, it displays the new or updated DCT file. Caution: Do not make changes to the DCT file until you have analyzed all MASs that are to be upgraded. Changes can be overwritten during analysis of subsequent MASs. 7. For a multiple-mas system, return to step 3 and repeat for all MASs in your system. 8. Review the file and add data to the DCT pages as necessary. Data Collection Tool June

14 Creating and Updating a DCT file a. Click Next and Back to navigate between pages. b. To check that the values that you entered in a page are valid and error-free, use the Next and Back button to navigate to a different page and then back to the page where you entered the data. DCT page and status indicators display errors and omissions that must be corrected before the file is complete. When data is complete and valid, the Complete button appears at the bottom of the page. c. Click Help on any DCT page for field definitions and valid field values. Caution: Do not change data that was populated during analysis. However, all account names and passwords must conform to Windows 2003 security rules. If you want to change your Modular Messaging account names or passwords, contact your support organization for more information. 9. To save or print the DCT file at any time during data entry, click Save or Print. 10. When you are ready, click Complete and follow instructions to save changes. Save the DCT file to an external USB storage device. Caution: Do not save the file to the MAS; it will be erased during installation of the Avaya boot image. Related topics: Obtaining a current version of the Data Collection Tool on page 9 Use of the DCT Data File in MM Configuration on page 7 Creating a DCT file for adding an MAS to an existing system Use this procedure to create a DCT file to use when adding an MAS to an existing Modular Messaging system. To add the MAS, you must first create a DCT file by analyzing the existing system. Prerequisites Obtain a current version of the Data Collection Tool. Verify that you have inserted the USB storage device with the current DCT in a USB port on the computer you are using. This procedure applies only to an Avaya MAS. 14 Data Collection Tool June 2009

15 Creating a DCT file for adding an MAS to an existing system For more detailed instructions, including information on adding a customer-provided MAS and moving services after the MAS is added, see Avaya Modular Messaging S8730-Family Hardware Maintenance and Additions. Caution: You cannot complete the addition without a DCT file that was created by analyzing all MASs in the system with all MASs and the message store running normally. 1. Log on to a Messaging Application Server (MAS) of the existing system using the Modular Messaging service account that was used to install the Modular Messaging services, such as mmacct. With the MSS configuration, this is the service account. With the Microsoft Exchange and IBM Domino configurations, this is the customer account. Note: With the MSS configuration, it is important that you use the service account. If you use any other account, the DCT cannot collect all required data, specifically, the IMAP, LDAP, and MWI passwords. 2. Start the DCT by double-clicking the MMDCT.exe file. 3. On the Select the DCT configuration to use page, select Analyze existing system and click OK. 4. When the DCT prompts you whether to use an existing DCT file, click Yes. Browse to the most recent file, select it, and click Open. The MM System Analysis page appears. 5. In the MAS information is being collected from field, select the appropriate MAS. In a multiple-mas system, select the MASs in numeric order, first to last. 6. Click Start. The system displays the progress of the analysis. When analysis on this MAS is complete, it displays the updated DCT file. Caution: Do not make changes to the DCT file until you have analyzed all MASs (step 11). Changes can be overwritten during analysis of subsequent MASs. 7. For a multiple-mas system, return to step 3 and repeat for all MASs in your system. 8. Review the file and add data to the DCT pages as necessary. a. Click Next and Back to navigate between pages. b. To check that the values that you entered in a page are valid and error-free, use the Next and Back button to navigate to a different page and then back to the page where you entered the data. DCT page and status indicators display errors and omissions that must be corrected before the file is complete. Data Collection Tool June

16 Creating and Updating a DCT file When data is complete and valid, the Complete button appears at the bottom of the page. c. Click Help on any DCT page for field definitions and valid field values. 9. Add information about the new MAS on the following pages: a. Message store page: Complete this step only if you are installing a customerprovided supplementary server in a system with Avaya-provided MASs. Select MSS with customer's MAS servers, Microsoft Exchange with customer's MAS servers or IBM Lotus Domino with customer's MAS servers based on the your MM configuration. This selection tells the system that you want to install customer-provided equipment. Customer provided equipment (CPE) can be used for a supplementary server in an MSS, Microsoft Exchange and IBM Lotus Domino systems. b. Voice Mail Domain page: Update the Number of MASs in the VMD to include the new MAS. The system displays a warning that you are changing the number of MASs in the VMD. You must analyze the system at the end of this procedure to ensure that the DCT file reflects the changes you make. You can install a customer provided equipment (CPE) MAS into an existing VMD of MSS, Microsoft Exchange, or IBM Lotus Domino system. c. Corporate MM server networking details page: Enter the full computer name, IP address, and NetBIOS name for the new MAS. d. MAS accounts and passwords page: Enter the local administrator accounts logon name and password for the new MAS. 10. To save or print the DCT file at any time during data entry, click Save or Print. 11. When you are ready, click Complete and follow any instructions to save changes. Related topics: Obtaining a current version of the Data Collection Tool on page 9 Use of the DCT Data File in MM Configuration on page 7 Updating a DCT file Use this procedure to update the Data Collection Tool (DCT) file by using the Data Collection Tool to analyze your system. File updates are particularly important if significant changes are made to the Modular Messaging system. Prerequisites Obtain a current version of the Data Collection Tool. Verify that you have inserted the USB storage device with the current DCT in a USB port on the computer you are using. 16 Data Collection Tool June 2009

17 Updating a DCT file Ensure that you have the Modular Messaging customer account login credentials to log in to the Messaging Application Server. Ensure that the following are in place: The Modular Messaging system is working properly. All MASs, the message store, and the supplementary server, if used, are running. Modular Messaging services are active. Use this procedure only for Modular Messaging systems with Microsoft Exchange or IBM Domino message stores. MSS systems automatically update and backup a DCT file nightly. Caution: It is important that you maintain a valid, updated DCT file. You must have a DCT file created by a DCT analysis to restore an MAS after a catastrophic disk failure. 1. Log on to the Messaging Application Server (MAS) that you are analyzing using the Modular Messaging customer account. (This is the account that was used to install the Modular Messaging services, such as mmacct.) 2. Start the DCT by double-clicking the MMDCT.exe file. 3. On the Select the DCT Configuration to use page, select Analyze existing system and click OK. 4. When asked if you want to use an existing DCT file, do one of the following: If you are creating a new DCT file for a single MAS or the first MAS in a multiple-mas system, click No. If you are updating either an existing DCT file for this MAS or a DCT file for additional MASs after the first in a multiple-mas system, click Yes. Browse to the file, select it, and click Open. 5. On the MM System Analysis page, select the MAS that you want to analyze. Note: In a multiple-mas system, analyze the MASs in numeric order, first to last. Analyze all MASs in the system. 6. Click Start. The system displays the progress of the analysis. When analysis is complete, it displays the updated file. Caution: Do not make changes to the DCT file until you have analyzed all MASs in your system (step 8). Changes can be overwritten during a subsequent analysis. 7. For a multiple-mas system, return to step 3 and repeat for all MASs in the system. When analysis is complete, the DCT displays the newly created or updated file Data Collection Tool June

18 Creating and Updating a DCT file 8. Review the file and add data to the DCT pages as necessary. a. Click Next and Back to navigate between pages. b. To check that the values that you entered in a page are valid and error-free, use the Next and Back button to navigate to a different page and then back to the page where you entered the data. DCT page and status indicators display errors and omissions that must be corrected before the file is complete. When data is complete and valid, the Complete button appears at the bottom of the page. c. Click Help on any DCT page for field definitions and valid field values. Caution: Do not change any data that was populated during analysis, with the following exception: You can change the default account names (on the MAS accounts and passwords page). 9. To save or print the DCT file at any time during data entry, click Save or Print. 10. When you are ready, click Complete and follow any instructions to save changes. Related topics: Obtaining a current version of the Data Collection Tool on page 9 Use of the DCT Data File in MM Configuration on page 7 18 Data Collection Tool June 2009

19 Chapter 5: Backing up a DCT file At the conclusion of a system installation or upgrade, Avaya recommends you to save and backup your data immediately. Use this procedure to back up your DCT file. It is important that you maintain a current version of the Data Collection Tool (DCT) file. This is done by performing regular backups. If a system failure occurs, the backed up DCT file provides data that is required to restore the Messaging Application Server (MAS) and the message store. With a Modular Messaging MSS configuration, the system performs a daily automatic DCT analysis and backup. The MMDCT file is updated on each MAS and is included in the MAS information copied to the MSS as part of the daily backup. However, this is not the case with Modular Messaging Exchange or Domino configurations. Avaya recommends that you also include the DCT file in any regular scheduled backups administered for your site. For all three Modular Messaging configurations, at the conclusion of a system installation or upgrade, do not wait for the automatic daily backup. Save and backup your data immediately. 1. Perform a complete attended (manual) system backup that includes the DCT file. For detailed instructions, see Modular Messaging for the Avaya Message Storage Server (MSS) Release 5.1 Installation and Upgrades, Modular Messaging for IBM Lotus Domino Release 5.1 Installation and Upgrades, or Modular Messaging for Microsoft Exchange Release 5.1 Installation and Upgrades. 2. On a multiple-mas system, after all MAS servers in the voice mail domain have been analyzed, save a copy of your data to the following two locations: For MSS: \\mss1\masbackup directory. Note: You can also perform an MAS attended back up to copy the relevant data files to the MSS. For Modular Messaging for Domino or Exchange: A non-system computer, such as a file server. Insert the external USB storage device into any available USB port on the nonsystem computer and copy the current DCT file from the device to the computer. Data Collection Tool June

20 Backing up a DCT file 20 Data Collection Tool June 2009

21 Chapter 6: DCT page and field status indicators The following tables explain the page and field status indicators displayed by the Data Collection Tool during data entry or system analysis. Table 1: status indicators Indicator Grayed-out field s with red background s with blue background s with yellow background This field is auto-populated because of a previous entry or selection and you cannot modify this. This is a mandatory field; you must enter a valid value in this field to complete the data entry or system analysis. This is an informational field; you can choose to ignore this field and this will not affect the completion of data entry or system analysis. However, Avaya recommends you to specify these values as these can be later referred to for the manual configuration of your Modular Messaging system. Indicates that the value entered in the field is not as per Avaya recommendations. This will not affect the completion of data entry or system analysis. Table 2: Page status indicators Indicator The page data is complete and valid. The page data is incomplete or invalid. Data Collection Tool June

22 DCT page and field status indicators The page has incomplete/missing informational data. The page has not yet been visited. Once you have visited a page and then navigate away, DCT changes the indicator to one of the above three indicators. 22 Data Collection Tool June 2009

23 Chapter 7: DCT page and field descriptions Select the DCT configuration to use field descriptions Use this page: When entering data, to create a new DCT file or to select the DCT file that you want to edit. During installation, upgrade, or disk restore, to select the DCT file that the Modular Messaging Configuration Wizard (MMCW) uses to configure the system. On an ongoing basis, to update your DCT file in case the file is required for a catastrophic disk failure recovery. Use the last file created Choose a file to use Create a new file Analyze existing system Select this option, if the DCT file you want to use is the last file created or edited with this tool. Select this option to browse to a DCT file that was previously created. The choice opens a standard browse dialog box to select a file. If you do not know the location you will need to search for the file. The file might be stored on an external USB storage device, any system hard disk drive, or even a common network drive. By default, the DCT lists files with the DCT file extension, *.mmdct. However, you can choose to list any file type. When MM is installed using the data from the DCT file, the DCT file is copied to the C:\Program Files\Avaya Modular Messaging\Install\MISCM\cfg directory by the Modular Messaging Configuration Wizard (MMCW). Select this option to create a new DCT file. For more information, see Modular Messaging for the Avaya Message Storage Server (MSS) Release 5.1 Installation and Upgrades, Modular Messaging for IBM Lotus Domino Release 5.1 Installation and Upgrades, or Modular Messaging for Microsoft Exchange Release 5.1 Installation and Upgrades. Select this option if you want to perform an upgrade and want the DCT tool to create a new DCT file based on information that it collects automatically from the system. With Microsoft Exchange or IBM Lotus Domino configurations, select this option to create or update a DCT file to use in the event of a catastrophic disk failure recovery. Data Collection Tool June

24 DCT page and field descriptions For more information, see Modular Messaging for the Avaya Message Storage Server (MSS) Release 5.1 Installation and Upgrades, Modular Messaging for IBM Lotus Domino Release 5.1 Installation and Upgrades, or Modular Messaging for Microsoft Exchange Release 5.1 Installation and Upgrades. Customer Information Customer details field descriptions Use this page to enter information about the customer to which this system belongs. This information is entered in the Computer Properties. It shows to whom the system is registered. Company name Organization name Name Phone number Fax number address Address Specifies the name of the company that purchased the voice mail system. The company name becomes the default name of the voice mail domain, though a different voice mail domain can be specified using this tool. The name can be from 1 to 64 characters, including any alphanumeric character and the following characters:, - _ % ^ & * ( ) and spaces. Specifies the name of the organization that maintains the voice mail domain, or that the voice mail system serves. The name can be from 1 to 64 characters, including any alphanumeric character and the following characters:, - _ % ^ & * ( ) and spaces. Specifies the name of the contact person at the customer site. Specifies the telephone number of the contact person at the customer site. Specifies the fax number of the contact person at the customer site. Specifies the address of the contact person at the customer site. The address may include any alphanumeric character and the following characters:, - _ % ^ & * ( ) and. are mandatory for the address. Specifies the mailing address of the contact person at the customer site. 24 Data Collection Tool June 2009

25 MM servers Sold to (FL) Notes Specifies the sold to or FL number for this customer. Specifies additional information about this customer. Regional settings field descriptions Use this page to select the time zone and keyboard input language for the MAS that you are installing or upgrading. Time Zone Keyboard input language Select the time zone in which the Messaging Application Server (MAS) is located. Select the language that matches the keyboard layout of the terminal used to administer the MAS. MM servers Modular Messaging configurations Avaya Modular Messaging Release 5.1 is available in the following configurations: Avaya Modular Messaging for Avaya Message Storage Server (MSS) This configuration contains one or more Avaya MASs and a single Avaya MSS. The MSS and MASs are provided by Avaya. The MAS hardware can also be provided by the customer. Avaya Modular Messaging for Microsoft Exchange This configuration contains one or more MASs connected to one or more Microsoft Exchange servers. The MASs can be provided by Avaya or can be provided by the customer. In either case, the Microsoft Exchange servers are customer provided. Avaya Modular Messaging for IBM Lotus Domino This configuration contains one or more MASs connected to one or more Lotus Domino servers. The MASs can be provided by Avaya or can be provided by the customer. In either case, the Lotus Domino servers are customer provided. Related topics: Message store field descriptions on page 26 Data Collection Tool June

26 DCT page and field descriptions Message store field descriptions Use this page to identify the type of system that you are installing or upgrading, and to specify contact information for the message store administrator. MSS with customer's MAS servers MSS with Avaya MAS servers Microsoft Exchange with customer's MAS servers Microsoft Exchange with Avaya MAS servers IBM Lotus Domino with customer's MAS servers IBM Lotus Domino with Avaya MAS servers Contact information for Message Store administrator Select this option if you are installing or upgrading an Avaya Messaging Application Server (MAS) with MSS on hardware that you did not purchase from Avaya. Select this option if you are installing or upgrading an Avaya Messaging Application Server (MAS) with an Avaya MSS that is Standard Availability (MSS-S) or High Availability (MSS-H). Select this option for a Microsoft Exchange message store if you are installing or upgrading Modular Messaging software on an MAS that you did not purchase from Avaya. Select this option for a Microsoft Exchange message store if you are installing or upgrading Modular Messaging software on an MAS that you purchased from Avaya. Select this option for an IBM Lotus Domino message store if you are installing or upgrading Modular Messaging software on an MAS that you did not purchase from Avaya. Select this option for an IBM Lotus Domino message store if you are installing or upgrading Modular Messaging software on an MAS that you purchased from Avaya. Specify the Name, Telephone number, and address of the person responsible for the administration of the message store the MSS, Exchange, or Domino administrator. When you select the MSS with customer's MAS servers option or the MSS with Avaya MAS servers, you cannot specify a contact name. Specify any additional information in the Notes field. Related topics: Modular Messaging configurations on page Data Collection Tool June 2009

27 MM servers Voice Mail Domain A voice mail domain (VMD) is a group of messaging application servers that: Have a common set of properties. Share one or more message stores. Share common resources such as a Tracing server, Message Waiting Indicator server, Call Me server, Mailbox Monitor server, Directory server and Offline Call Answer store. Regardless of system configuration, each MAS can be a member of only one voice mail domain. How the VMD name is used during installation: When the Modular Messaging Configuration Wizard uses the VMD name specified in the DCT file during the installation of Modular Messaging, the following occurs: If this is the first MAS to be installed and there is no existing VMD, a VMD is created using the name in the DCT file. If this is the first MAS to be installed and there is already a VMD of exactly the same name as that specified in the DCT file, the wizard joins the MAS to the existing VMD rather than creating a new one. The wizard issues an informational event. For Modular Messaging for MSS only, if this is the first MAS to be installed and there is already a VMD in the directory that does not match the VMD name specified in the DCT file, the wizard displays an error and stops the installation. The error includes the name of the existing VMD and the VMD name specified in the DCT file. For the new VMD to be created, the existing VMD must first be removed from the system. Related topics: Voice Mail Domain field descriptions on page 27 Voice Mail Domain field descriptions Use this page to specify the name of the voice mail domain (VMD) that the MASs will join, and the number of MASs that are members of the VMD. Regardless of system configuration, each MAS can be a member of only one VMD. You can also use this page to change the location where the Modular Messaging software is installed. Enable MultiSite VMD name Select this option to enable MultiSite for the voice mail domain. By default, this check box is cleared. Specifies the name of the voice mail domain that all MASs in the Modular Messaging system will join. Data Collection Tool June

28 DCT page and field descriptions Number of MASs in the VMD Software installation path The VMD name can be from 2 to 16 characters, including any alphanumeric character and the following characters:, - _ % ^ & * ( ) and spaces. Select the total number of MASs that are part of this VMD. Include the supplementary server, if one is used. The number entered in this field determines the number of MASs you can administer on the Corporate MM server networking details page and the MM service selection page. The system may have optional servers in addition to the supplementary server. For example, Web Subscriber Options (WSO) can reside on its own server rather than on an MAS. However, these servers are not configured by the DCT and should not be included in the number of MASs entered in this field. The maximum permissible number of MASs in a voice mail domain are: For MSS-S, 2 MASs and 1 optional supplementary server. For MSS-H, 5 MASs and 1 optional supplementary server. For Microsoft Exchange, 10 MASs and 1 optional supplementary server. For IBM Lotus Domino, 10 MASs and 1 optional supplementary server. If you want to install the Modular Messaging software to a drive other than the default (C: drive), edit the drive letter, or browse to where you want to install Modular Messaging. Caution: Change only the drive where the software is installed. Do not alter the installation path. The final path must read <drive>: \Program Files\Avaya Modular Messaging. If you install Modular Messaging to a drive other than the default C: drive, the logging location is not automatically changed. Therefore, you may want to change the location for storing logs to the same drive as the software installation. For more information, see Setting logging location in your installation documentation. Related topics: Voice Mail Domain on page Data Collection Tool June 2009

29 Networking Networking Corporate MM server networking details All Modular Messaging servers must be in the same Windows domain and on the same local area network (LAN) segment. If you chose static IP addressing by selecting Connect to corporate network using specified (static) IP addresses on the Corporate network details page, enter IP addresses for the MSS and MASs. If you chose to obtain IP addresses dynamically by selecting Connect to corporate network and obtain IP addresses automatically using DHCP, enter only the FQDNs for the servers. The exception is the MSS, which must be assigned a static IP address. The number of MASs that can be administered on the Corporate MM server networking details page corresponds to the number of MASs specified on the Voice Mail Domain page. It includes all MASs, including the supplementary server. You can change the number of administrable MASs by changing the value on the Voice Mail Domain page. Related topics: Corporate network details field descriptions on page 29 Corporate network details field descriptions Use this page to specify whether the Modular Messaging system connects to the corporate network or not. If the Modular Messaging system connects to the corporate network, select the type of IP addressing to use to connect to the corporate network. You can also use this page to specify information about the corporate network to allow Modular Messaging to route traffic via the corporate LAN and resolve computer names to IP addresses. You must enter this information even if you are using Dynamic Host Configuration Protocol (DHCP). All information for this page must be obtained from the corporate LAN administrator. Connect to corporate network using specified (static) IP addresses Connect to corporate network and obtain IP Select this option to assign static corporate network IP addresses to each MAS. When you make this selection you can enter IP addresses for each MAS on the Corporate MM server networking details page. You can also enter DNS, WINS and default gateway IP addressing information on the Corporate network details page. Select this option to assign IP addresses dynamically. If you select this option with an IP H.323 or IP SIP integration, you receive a warning, but the installation or upgrade is not Data Collection Tool June

30 DCT page and field descriptions addresses automatically using DHCP Do not connect MM to the corporate network be interrupted. With IP H.323 or IP SIP integrations, DHCP must be configured to reserve a specific IP address for each MAS, because the IP addresses must not change. Select this option if you do not want to connect your Modular Messaging for MSS system to the corporate network. Note: You cannot select this option for a Modular Messaging for Microsoft Exchange or IBM Lotus Domino system. If you are configuring your MSS system to route traffic over an existing corporate Windows domain rather than the MSS private Windows domain, do not select this option. If you are configuring your MSS to route traffic over the private MSS Windows domain, selecting this option will increase voice mail system security and decrease traffic on the corporate network. However, if you do not connect to the network, users can access the voice mail system only through the Telephone User Interface without client applications. If you select this option, you will not have IMAP access to the message store or LDAP access to subscriber data. Therefore you cannot access your voice mail mailbox with any client application. DNS Server addresses, in order of use Append these DNS suffixes (in order) Specifies the IP address of each DNS server used by Modular Messaging MASs. This information is used to resolve computer names to IP addresses. Enter the IP addresses in the order in which an MAS will query subsequent DNS servers if the previous server does not contain the appropriate host record. The search order is from the top of the list down. Leave the DNS blank when connecting a Modular Messaging for MSS system to a private LAN. Specifies the name of each DNS domain to search in order of use. The search order is from the top of the list down. Leave the DNS suffixes blank when connecting a Modular Messaging for MSS system to a private LAN. Name Use this connection s DNS suffix in DNS registration For DHCP only, if the DNS suffix has not previously been registered with the DNS server, select this check box to register the suffix. The DNS suffix is the entire Fully Qualified Domain Name minus the specific host or computer name. 30 Data Collection Tool June 2009

31 Networking Name Register this connection s addresses in DNS WINS For DHCP only, select this check box to register MSS and MAS IP addresses with the DNS server for lookup. For hosts that run NetBIOS over TCP/IP, specify the IP address of the preferred WINS server that resolves NetBIOS computer names to IP addresses. MASs Subnet mask Default gateway When using static IP addressing, specify the subnet mask for the subnet on which the MASs reside. The subnet mask must be in the range to The uppermost bit of the subnet mask must be a 1. The lowest bit must be a 0. For example, is valid, but and are not valid. Specifies the IP address of the default gateway for the LAN or subnet where the MASs reside. MSS Subnet mask Default gateway When using static IP addressing, specify the subnet mask for the subnet on which the MSS resides. The subnet mask must be in the range to The uppermost bit of the subnet mask must be a 1. The lowest bit must be a 0. For example, is valid, but and are not valid. Specifies the IP address of the default gateway for the LAN or subnet where the MSS resides. Leave this field blank when connecting a Modular Messaging for MSS system to a private LAN. Related topics: Corporate MM server networking details on page 29 Windows domain field descriptions Use this page to specify the details of the Corporate Windows domain to which you want to add the Modular Messaging system. You can specify the details of the Corporate Windows domain only if you have not selected Do not connect MM to the corporate network on the Corporate network details page. Data Collection Tool June

32 DCT page and field descriptions Join a private Windows domain Private Windows domain name Join a corporate Windows domain Corporate Windows domain name Domain controller's host name (FQDN) There are several corporate Windows domains Authentication method Kerberos Realm Select this option if you want Modular Messaging to join the private Windows domain. Specifies the name of the private Windows domain that you want Modular Messaging system to join. The name of the private Windows domain is automatically generated by the DCT and you can modify this. This name must be unique throughout the messaging network and should not be the same as the corporate Windows domain name. Select this option if you want Modular Messaging to connect to the corporate Windows domain. Specifies the name of the corporate Windows domain that you want the Modular Messaging system to join. Specifies the host name of the domain controller of the corporate Windows domain that you want the Modular Messaging system to join. Select this check box if there are multiple corporate Windows domains in the customer s network. Select the authentication method for secure communication to the Windows Domain Controller over the Corporate LAN. The authentication method depends on the configuration of Active Directory. Either Kerberos or Winbind are required if anonymous access security is restricted on the domain controller. Kerberos requires the corporate domain administrator account. The default option will use anonymous Winbind access. This field is enabled only if you select the Join corporate windows domain option. Enter the fully qualified name of the Kerberos realm. This field is enabled only if you select Kerberos in the Authentication method field. Use only alpha characters, numbers, and the hyphen character (-), period, or the underscore character (_) in the Kerberos Realm field. Corporate MM server networking details field descriptions For Modular Messaging Message Storage Server (MSS) systems, use this page to identify the MSS and Messaging Application Servers (MASs) to the corporate network. For Modular Messaging Microsoft Exchange and IBM Lotus Domino systems, identify the MASs to the corporate network. Provide the IP addresses and Fully Qualified Domain Names (FQDNs) for each server. Be sure to use only valid TCP/IP addresses. 32 Data Collection Tool June 2009

33 Networking MSS Server information Full computer name IP address NetBIOS name For Modular Messaging for MSS systems only, specify the Fully Qualified Domain Name (FQDN) of the MSS. Avaya recommends that computer names be shorter than 10 characters for ease of data entry. The fully qualified domain name (computer plus domain name) must be 64 or fewer characters. Use only lower-case alpha characters, numbers, and the hyphen character (-). The first character cannot be a number. For Modular Messaging for MSS systems only, you must assign a static IP address to the MSS, even if the system uses DHCP to assign most IP addresses. For Modular Messaging for MSS systems only, specify the NetBIOS name of the MSS. This allows applications on the MASs and the MSS to communicate over the private LAN. The DCT automatically copies the full computer name that you entered for the MSS to this field. However, you can modify this name. Avaya recommends that the NetBIOS name be shorter than 10 characters for ease of data entry. The NetBIOS name can be 1 to 15 characters. Use only lower-case alpha characters, numbers, and the hyphen character (-) or the underscore character (_). The first character cannot be a number. MAS details Full computer name IP address NetBIOS name Specifies the Fully Qualified Domain Name for each MAS that is part of the voice mail domain. For Modular Messaging for MSS only, the first MAS that is installed becomes the domain controller. The name of this domain controller cannot be changed after the installation. Avaya recommends that computer names be shorter than 10 characters for ease of data entry. The fully qualified domain name (computer plus domain name) must be 64 or fewer characters. Use only lower-case alpha characters, numbers, and the hyphen character (-). The first character cannot be a number. When using static IP addressing, specify the IP address of each MAS that is part of the voice mail domain. Specify the NetBIOS name for each MAS that is part of the voice mail domain. This allows applications on the MASs and the MSS to communicate over the private LAN. The DCT automatically copies the full computer name that you entered for the MSS to this field. However, you can modify this name. Data Collection Tool June

34 DCT page and field descriptions Avaya recommends that the NetBIOS name be shorter than 10 characters for ease of data entry. The NetBIOS name can be 1 to 15 characters. Use only lower-case alpha characters, numbers, and the hyphen character (-) or the underscore character (_). The first character cannot be a number. The NetBIOS name of an MAS cannot begin with mas. Aliases and ART nicknames field descriptions Use this page to specify the public aliases that you want to use for the corporate LAN interface. You can specify up to five alias names and an Automatic Registration Tool (ART) nickname for the MSS and each MAS in the Voice Mail Domain. ART is a web-based tool that permits field technicians and TSO Database Administration (DBA) to register servers and other channel products. Alias ART nickname Specifies one or more alias names for the MSS and each MAS in the Voice Mail Domain. The DCT automatically copies the hostname from the Full computer name that you entered for the MSS on the Corporate MM server networking details page to this field. However, you can modify this name. You can specify as many as five aliases. If you specify more than one alias, separate each name with a space. Each name must be unique on the Modular Messaging system and on the network. Specifies the ART nickname generated for the specified MAS. The server that you register with an ART must have switch connectivity through either the INADS line or an IP address. Private network field descriptions For a Modular Messaging for MSS system only, use this page to select the range of IP addresses used on the private LAN. You can also use this page to change these default IP addresses. Important: During installation, the Modular Messaging Configuration Wizard (MMCW) assigns specific private network IP addresses within the selected range to each MAS in the voice mail domain. The MASs use the assigned address to communicate with the MSS. This IP address must match the IP address administered for each MAS during MSS installation. 34 Data Collection Tool June 2009