data collection tool...2. on the select the dct configuration to use page, do one of the following:...

Data Collection Tool

August 2008

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........................................................................11Creating a DCT file for a new installation........................................................................................................11Creating a DCT file for an upgrade................................................................................................................12Creating a DCT file for adding an MAS to an existing system........................................................................14Updating 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........................................................................23Select the DCT configuration to use field descriptions....................................................................................23Customer Information......................................................................................................................................24

Customer details field descriptions........................................................................................................24Regional settings field descriptions........................................................................................................25

MM servers....................................................................................................................................................25Modular Messaging configurations........................................................................................................25Message store field descriptions............................................................................................................26Voice Mail Domain..................................................................................................................................27Voice Mail Domain field descriptions......................................................................................................27

Networking......................................................................................................................................................29Corporate MM server networking details................................................................................................29Corporate network details field descriptions..........................................................................................29Windows domain field descriptions........................................................................................................31Corporate MM server networking details field descriptions....................................................................32Aliases and ART nicknames field descriptions......................................................................................34Private network field descriptions..........................................................................................................34

Message store setup......................................................................................................................................35Exchange message store field descriptions..........................................................................................35Domino message store field descriptions..............................................................................................36

Accounts and passwords................................................................................................................................38MSS passwords field descriptions..........................................................................................................38MAS accounts and passwords field descriptions..................................................................................39Logon accounts and passwords............................................................................................................40Logon accounts and passwords field descriptions................................................................................41MAS service account field descriptions..................................................................................................42Trusted servers......................................................................................................................................43Optional MSS trusted servers field descriptions....................................................................................43Additional optional MSS trusted servers field descriptions....................................................................44

TTS sessions and languages..........................................................................................................................45TTS and announcements field descriptions..........................................................................................45

MAS servers....................................................................................................................................................46MAS servers and Modular Messaging services....................................................................................46Guidelines for configuring Modular Messaging services........................................................................48MM service selection field descriptions..................................................................................................48

Data Collection Tool August 2008 3

Tracing field descriptions........................................................................................................................49Web Subscriber Options server..............................................................................................................50Web Subscriber Options field descriptions............................................................................................50Web Client server..................................................................................................................................51Web Client server field descriptions......................................................................................................51Language packs....................................................................................................................................52Language packs field descriptions........................................................................................................53Offline access field descriptions............................................................................................................53Message networking field descriptions..................................................................................................53

PBX integration..............................................................................................................................................54Switch integration method field descriptions..........................................................................................54Switch integration information field descriptions....................................................................................55Extensions and switch ports field descriptions......................................................................................58Dial Plan................................................................................................................................................58Access Telephone Numbers field descriptions......................................................................................65Other information for PBX integrations..................................................................................................65Other information field descriptions........................................................................................................66

Mailbox information........................................................................................................................................67System mailboxes field descriptions......................................................................................................67TUI types and test subscribers field descriptions..................................................................................69Extended lists........................................................................................................................................72Extended lists field descriptions............................................................................................................72Classes of service field descriptions......................................................................................................73Caller applications field descriptions......................................................................................................73

AAA configuration..........................................................................................................................................73AAA server............................................................................................................................................73AAA configuration field descriptions......................................................................................................74

Support and maintenance..............................................................................................................................76Product information field descriptions....................................................................................................76Remote Access IP addresses field descriptions....................................................................................76Alarming information..............................................................................................................................77Alarming information field descriptions..................................................................................................78Password guidelines..............................................................................................................................80MSS login and PPP information field descriptions................................................................................80

Clients............................................................................................................................................................82Client applications field descriptions......................................................................................................82

Notes..............................................................................................................................................................83Notes field descriptions..........................................................................................................................83

Index.........................................................................................................................................85

Contents

4 Data Collection Tool August 2008

Chapter 1: What is the Data Collection Tool?

The Data Collection Tool (DCT) is a standalone application, delivered on the Avaya ModularMessaging 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. TheDCT stores the data in the form of a DCT file. You use this file as input to the Modular MessagingConfiguration Wizard (MMCW) when you install, upgrade, add, or recover a MessagingApplication Server (MAS).


What is the Data Collection Tool?


Chapter 2: Use of the DCT Data File in MMConfiguration

The DCT file generated using the Data Collection Tool (DCT) helps in automating the initialadministration 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 aDCT file. The technician, project planner, system administrator, or any other designated expertcan 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. TheModular Messaging Configuration Wizard (MMCW) uses the data in the DCT file toautomatically perform the initial administration and configuration of your Modular Messagingsystem.

Related topics:Obtaining a current version of the Data Collection Tool on page 9Creating a DCT file for a new installation on page 11Creating a DCT file for an upgrade on page 12Creating a DCT file for adding an MAS to an existing system on page 14Updating a DCT file on page 16


Use of the DCT Data File in MM Configuration


Chapter 3: Obtaining a current version ofthe Data Collection Tool

Before creating a Data Collection Tool file for a new installation, upgrade or disk failurerecovery, 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 usingto create or update the DCT file.

Related topics:Updating a DCT file on page 16Creating a DCT file for a new installation on page 11Creating a DCT file for an upgrade on page 12Creating a DCT file for adding an MAS to an existing system on page 14Use of the DCT Data File in MM Configuration on page 7


http://www.avaya.com/support

Obtaining a current version of the Data Collection Tool


Chapter 3: Creating and Updating a DCT file

Creating a DCT file for a new installationUse this procedure to manually enter information required to install the new MessagingApplication Servers (MAS) and message store into the Data Collection Tool. The technician,project planner, system administrator and other designated experts who are responsible forthe 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 USBport on the computer you are using.

The DCT creates a DCT file with the file extension *.mmdct. Multiple users with differentproject responsibilities can run the tool and enter data in a common file. Use the followingprocedure to create a single DCT file for all MASs in the Voice Mail Domain. When creating aDCT 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 multiplesystems in a networked environment. The name of the private Windows domain isautomatically generated by the DCT. You can modify the name of the private Windowsdomain . This name must be unique throughout the messaging network and should not bethe same as the corporate Windows domain name. If the private Windows domain name isduplicated anywhere in the network, you must reinstall Modular Messaging on all affectedservers 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 andclick 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.


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, usethe Next and Back button to navigate to a different page and then back to thepage where you entered the data. DCT page and Field status indicators displayerrors and omissions that must be corrected before the file is complete.When data is complete and valid, the Complete button appears at the bottomof 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 uniquelyidentifies this customer installation.

When all information is complete and valid, the technician can take the DCT file to the customersite and this file can be used in conjunction with the Modular Messaging Configuration Wizardfor the installation.

Related topics:Obtaining a current version of the Data Collection Tool on page 9Use of the DCT Data File in MM Configuration on page 7

Creating a DCT file for an upgradeUse this procedure to create a DCT file for an upgrade by using the Data Collection Tool toanalyze the existing system.

Prerequisites



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 releaseto Release 5.0. An upgrade from Release 3.0 or Release 4.0 to Release 5.0 does not requirethe DCT.

Creating and Updating a DCT file


1. Log on to a Messaging Application Server (MAS) that you are upgrading using theModular Messaging service account that was used to install the Modular Messagingservices, such as mmacct.With the MSS configuration, this is the service account. With the MicrosoftExchange and IBM Domino configurations, this is the customer account.

Note:With the MSS configuration, it is important that you use the service account. Ifyou use any other account, the DCT cannot collect all required data, specifically,the IMAP, LDAP, and MWI passwords.


3. On the Select the DCT configuration to use page, select Analyze existing systemand click OK.

4. When the DCT prompts you whether to use an existing DCT file, do one of thefollowing:

• 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-MASsystem, click Yes. Browse to the file that you created when you analyzedthe 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 youare upgrading to an S8730 server, you can choose to decrease the number ofMASs in the voice mail domain (VMD). For more information about moving MMservices, see Avaya Modular Messaging S8730-Family Hardware Maintenanceand Additions. At the completion of the upgrade, all MASs in the voice maildomain (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 iscomplete, it displays the new or updated DCT file.

Caution:Do not make changes to the DCT file until you have analyzed all MASs that areto be upgraded. Changes can be overwritten during analysis of subsequentMASs.

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.

Creating a DCT file for an upgrade





Caution:Do not change data that was populated during analysis. However, all accountnames and passwords must conform to Windows 2003 security rules. If you wantto change your Modular Messaging account names or passwords, contact yoursupport 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. Savethe 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 Avayaboot image.


Creating a DCT file for adding an MAS to an existing systemUse this procedure to create a DCT file to use when adding an MAS to an existing ModularMessaging system. To add the MAS, you must first create a DCT file by analyzing the existingsystem.

Prerequisites



This procedure applies only to an Avaya MAS.



For more detailed instructions, including information on adding a customer-provided MAS andmoving services after the MAS is added, see Avaya Modular Messaging S8730-FamilyHardware Maintenance and Additions.

Caution:You cannot complete the addition without a DCT file that was created by analyzing all MASsin 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 theModular Messaging service account that was used to install the Modular Messagingservices, such as mmacct.With the MSS configuration, this is the service account. With the MicrosoftExchange and IBM Domino configurations, this is the customer account.

Note:With the MSS configuration, it is important that you use the service account. Ifyou use any other account, the DCT cannot collect all required data, specifically,the IMAP, LDAP, and MWI passwords.


3. On the Select the DCT configuration to use page, select Analyze existing systemand click OK.

4. When the DCT prompts you whether to use an existing DCT file, click Yes. Browseto 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 iscomplete, 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.



b. To check that the values that you entered in a page are valid and error-free, usethe Next and Back button to navigate to a different page and then back to thepage where you entered the data. DCT page and Field status indicators displayerrors and omissions that must be corrected before the file is complete.

Creating a DCT file for adding an MAS to an existing system


When data is complete and valid, the Complete button appears at the bottomof the page.


9. Add information about the new MAS on the following pages:

a. Message store page: Complete this step only if you are installing a customer-provided supplementary server in a system with Avaya-provided MASs. SelectMSS with customer's MAS servers, Microsoft Exchange with customer'sMAS servers or IBM Lotus Domino with customer's MAS servers based onthe your MM configuration. This selection tells the system that you want to installcustomer-provided equipment.Customer provided equipment (CPE) can be used for a supplementary serverin an MSS, Microsoft Exchange and IBM Lotus Domino systems.

b. Voice Mail Domain page: Update the Number of MASs in the VMD to includethe new MAS. The system displays a warning that you are changing the numberof MASs in the VMD. You must analyze the system at the end of this procedureto ensure that the DCT file reflects the changes you make.You can install a customer provided equipment (CPE) MAS into an existingVMD 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 accountslogon name and password for the new MAS.




Updating a DCT fileUse this procedure to update the Data Collection Tool (DCT) file by using the Data CollectionTool to analyze your system. File updates are particularly important if significant changes aremade to the Modular Messaging system.

Prerequisites





Ensure that you have the Modular Messaging customer account login credentials to log in tothe 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 IBMDomino 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 createdby 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 theModular Messaging customer account. (This is the account that was used to installthe Modular Messaging services, such as mmacct.)


3. On the Select the DCT Configuration to use page, select Analyze existing systemand 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 amultiple-MAS system, click No.

• If you are updating either an existing DCT file for this MAS or a DCT file foradditional MASs after the first in a multiple-MAS system, click Yes. Browseto 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, itdisplays the updated file.

Caution:Do not make changes to the DCT file until you have analyzed all MASs in yoursystem (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

Updating a DCT file






Caution:Do not change any data that was populated during analysis, with the followingexception: You can change the default account names (on the MAS accountsand passwords page).






Chapter 5: Backing up a DCT file

At the conclusion of a system installation or upgrade, Avaya recommends you to save andbackup 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. Thisis done by performing regular backups. If a system failure occurs, the backed up DCT fileprovides data that is required to restore the Messaging Application Server (MAS) and themessage store.

With a Modular Messaging MSS configuration, the system performs a daily automatic DCTanalysis and backup. The MMDCT file is updated on each MAS and is included in the MASinformation copied to the MSS as part of the daily backup. However, this is not the case withModular Messaging Exchange or Domino configurations. Avaya recommends that you alsoinclude 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 orupgrade, 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 StorageServer (MSS) Release 5.0 Installation and Upgrades, Modular Messaging for IBMLotus Domino Release 5.0 Installation and Upgrades, or Modular Messaging forMicrosoft Exchange Release 5.0 Installation and Upgrades.

2. On a multiple-MAS system, after all MAS servers in the voice mail domain havebeen 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 datafiles 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 non-system computer and copy the current DCT file from the device to the computer.


Backing up a DCT file


Chapter 6: DCT page and field statusindicators

The following tables explain the page and field status indicators displayed by the DataCollection Tool during data entry or system analysis.

Table 1: Field status indicators

Indicator Description

Grayed-out field This field is auto-populated because ofa previous entry or selection and youcannot modify this.

Fields with red background This is a mandatory field; you must entera valid value in this field to complete thedata entry or system analysis.

Fields with blue background This is an informational field; you canchoose to ignore this field and this willnot affect the completion of data entry orsystem analysis. However, Avayarecommends you to specify thesevalues as these can be later referred tofor the manual configuration of yourModular Messaging system.

Fields with yellow background Indicates that the value entered in thefield is not as per Avayarecommendations. This will not affectthe completion of data entry or systemanalysis.

Table 2: Page status indicators

Indicator Description

The page data is complete and valid.

The page data is incomplete or invalid.


The page has incomplete/missinginformational data.

The page has not yet been visited. Onceyou have visited a page and thennavigate away, DCT changes theindicator to one of the above threeindicators.

DCT page and field status indicators


Chapter 7: DCT page and field descriptions

Select the DCT configuration to use field descriptionsUse this page:

• When entering data, to create a new DCT file or to select the DCT file that you wantto edit.

• During installation, upgrade, or disk restore, to select the DCT file that the ModularMessaging Configuration Wizard (MMCW) uses to configure the system.

• On an ongoing basis, to update your DCT file in case the file is required for acatastrophic disk failure recovery.

Field DescriptionUse the lastfile created

Select this option, if the DCT file you want to use is the last file createdor edited with this tool.

Choose afile to use

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 youdo not know the location you will need to search for the file. The filemight be stored on an external USB storage device, any system harddisk 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 fileis copied to the C:\Program Files\Avaya ModularMessaging\Install\MISCM\cfg directory by the ModularMessaging Configuration Wizard (MMCW).

Create anew file

Select this option to create a new DCT file.For more information, see Modular Messaging for the AvayaMessage Storage Server (MSS) Release 5.0 Installation andUpgrades, Modular Messaging for IBM Lotus Domino Release 5.0Installation and Upgrades, or Modular Messaging for MicrosoftExchange Release 5.0 Installation and Upgrades.

Analyzeexistingsystem

Select this option if you want to perform an upgrade and want theDCT tool to create a new DCT file based on information that it collectsautomatically from the system. With Microsoft Exchange or IBMLotus Domino configurations, select this option to create or update aDCT file to use in the event of a catastrophic disk failure recovery.


Field DescriptionFor more information, see Modular Messaging for the AvayaMessage Storage Server (MSS) Release 5.0 Installation andUpgrades, Modular Messaging for IBM Lotus Domino Release 5.0Installation and Upgrades, or Modular Messaging for MicrosoftExchange Release 5.0 Installation and Upgrades.

Customer Information

Customer details field descriptionsUse this page to enter information about the customer to which this system belongs. Thisinformation is entered in the Computer Properties. It shows to whom the system is registered.

Field DescriptionCompany name Specifies the name of the company that purchased the voice

mail system. The company name becomes the default nameof the voice mail domain, though a different voice mail domaincan be specified using this tool.The name can be from 1 to 64 characters, including anyalphanumeric character and the following characters: , - _ % ^& * ( ) ~ @ and spaces.

Organizationname

Specifies the name of the organization that maintains the voicemail domain, or that the voice mail system serves.The name can be from 1 to 64 characters, including anyalphanumeric character and the following characters: , - _ % ^& * ( ) ~ @ and spaces.

Name Specifies the name of the contact person at the customer site.

Phone number Specifies the telephone number of the contact person at thecustomer site.

Fax number Specifies the fax number of the contact person at the customersite.

Email address Specifies the email address of the contact person at thecustomer site.The address may include any alphanumeric character and thefollowing characters: , - _ % ^ & * ( ) ~ and @. @ and . aremandatory for the e-mail address.

Address Specifies the mailing address of the contact person at thecustomer site.

DCT page and field descriptions


Field DescriptionSold to (FL) Specifies the sold to or FL number for this customer.

Notes Specifies additional information about this customer.

Regional settings field descriptionsUse this page to select the time zone and keyboard input language for the MAS that you areinstalling or upgrading.

Field DescriptionTime Zone Select the time zone in which the Messaging Application

Server (MAS) is located.

Keyboard inputlanguage

Select the language that matches the keyboard layout of theterminal used to administer the MAS.

MM servers

Modular Messaging configurationsAvaya Modular Messaging Release 5.0 is available in the following configurations:

• Avaya Modular Messaging for Avaya Message Storage Server (MSS) — Thisconfiguration contains one or more Avaya MASs and a single Avaya MSS. The MSSand MASs are provided by Avaya. The MSS hardware can also be provided by thecustomer.

• Avaya Modular Messaging for Microsoft Exchange — This configuration contains oneor more MASs connected to one or more Microsoft Exchange servers. The MASs canbe provided by Avaya or can be provided by the customer. In either case, the MicrosoftExchange servers are customer provided.

• Avaya Modular Messaging for IBM Lotus Domino — This configuration contains oneor more MASs connected to one or more Lotus Domino servers. The MASs can beprovided by Avaya or can be provided by the customer. In either case, the LotusDomino servers are customer provided.

Related topics:Message store field descriptions on page 26

MM servers


Message store field descriptionsUse this page to identify the type of system that you are installing or upgrading, and to specifycontact information for the message store administrator.

Field DescriptionMSS with customer'sMAS servers

Select this option if you are installing or upgrading anAvaya Messaging Application Server (MAS) with MSS onhardware that you did not purchase from Avaya.

MSS with Avaya MASservers

Select this option if you are installing or upgrading anAvaya Messaging Application Server (MAS) with anAvaya MSS that is Standard Availability (MSS-S) or HighAvailability (MSS-H).

Microsoft Exchangewith customer's MASservers

Select this option for a Microsoft Exchange messagestore if you are installing or upgrading Modular Messagingsoftware on an MAS that you did not purchase fromAvaya.

Microsoft Exchangewith Avaya MASservers

Select this option for a Microsoft Exchange messagestore if you are installing or upgrading Modular Messagingsoftware on an MAS that you purchased from Avaya.

IBM Lotus Dominowith customer's MASservers

Select this option for an IBM Lotus Domino message storeif you are installing or upgrading Modular Messagingsoftware on an MAS that you did not purchase fromAvaya.

IBM Lotus Dominowith Avaya MASservers

Select this option for an IBM Lotus Domino message storeif you are installing or upgrading Modular Messagingsoftware on an MAS that you purchased from Avaya.

Contact informationfor Message Storeadministrator

Specify the Name, Telephone number, and e-mailaddress of the person responsible for the administrationof the message store — the MSS, Exchange, or Dominoadministrator.When you select the MSS using Avaya hardware option,you cannot specify a contact name.Specify any additional information in the Notes field.

Related topics:Modular Messaging configurations on page 25



Voice Mail DomainA 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 maildomain.

How the VMD name is used during installation:

When the Modular Messaging Configuration Wizard uses the VMD name specified in the DCTfile 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 createdusing the name in the DCT file.

• If this is the first MAS to be installed and there is already a VMD of exactly the samename as that specified in the DCT file, the wizard joins the MAS to the existing VMDrather 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 isalready a VMD in the directory that does not match the VMD name specified in theDCT file, the wizard displays an error and stops the installation. The error includes thename of the existing VMD and the VMD name specified in the DCT file. For the newVMD 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 descriptionsUse this page to specify the name of the voice mail domain (VMD) that the MASs will join, andthe number of MASs that are members of the VMD. Regardless of system configuration, eachMAS can be a member of only one VMD. You can also use this page to change the locationwhere the Modular Messaging software is installed.

Field DescriptionEnableMultiSite

Select this option to enable MultiSite for the voice mail domain. Bydefault, this check box is cleared.

VMD name Specifies the name of the voice mail domain that all MASs in theModular Messaging system will join.

MM servers


Field DescriptionThe VMD name can be from 2 to 16 characters, including anyalphanumeric character and the following characters: , - _ % ^ &* ( ) ~ @ and spaces.

Number ofMASs in theVMD

Select the total number of MASs that are part of this VMD. Includethe supplementary server, if one is used.The number entered in this field determines the number of MASsyou can administer on the Corporate MM server networking detailspage and the MM service selection page.The system may have optional servers in addition to thesupplementary 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 shouldnot be included in the number of MASs entered in this field.The maximum permissible number of MASs in a voice mail domainare:

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

Softwareinstallationpath

If you want to install the Modular Messaging software to a driveother than the default (C: drive), edit the drive letter, or browse towhere you want to install Modular Messaging.

Caution:Change only the drive where the software is installed. Do notalter 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 defaultC: drive, the logging location is not automatically changed.Therefore, you may want to change the location for storing logsto the same drive as the software installation. For moreinformation, see Setting logging location in your installationdocumentation.

Related topics:Voice Mail Domain on page 27



Networking

Corporate MM server networking detailsAll Modular Messaging servers must be in the same Windows domain and on the same localarea network (LAN) segment. If you chose static IP addressing by selecting Connect tocorporate network using specified (static) IP addresses on the Corporate network detailspage, enter IP addresses for the MSS and MASs. If you chose to obtain IP addressesdynamically by selecting Connect to corporate network and obtain IP addressesautomatically 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 detailspage corresponds to the number of MASs specified on the Voice Mail Domain page. It includesall MASs, including the supplementary server. You can change the number of administrableMASs by changing the value on the Voice Mail Domain page.

Related topics:Corporate network details field descriptions on page 29

Corporate network details field descriptionsUse this page to specify whether the Modular Messaging system connects to the corporatenetwork or not. If the Modular Messaging system connects to the corporate network, select thetype of IP addressing to use to connect to the corporate network. You can also use this pageto specify information about the corporate network to allow Modular Messaging to route trafficvia the corporate LAN and resolve computer names to IP addresses. You must enter thisinformation even if you are using Dynamic Host Configuration Protocol (DHCP). All informationfor this page must be obtained from the corporate LAN administrator.

Field DescriptionConnect tocorporate networkusing specified(static) IPaddresses

Select this option to assign static corporate network IPaddresses to each MAS.When you make this selection you can enter IP addresses foreach MAS on the Corporate MM server networking detailspage. You can also enter DNS, WINS and default gateway IPaddressing information on the Corporate network detailspage.

Connect tocorporate networkand obtain IP

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

Networking


Field Descriptionaddressesautomaticallyusing DHCP

be interrupted. With IP H.323 or IP SIP integrations, DHCPmust be configured to reserve a specific IP address for eachMAS, because the IP addresses must not change.

Do not connectMM to thecorporate network

Select this option if you do not want to connect your ModularMessaging for MSS system to the corporate network.

Note:You cannot select this option for a Modular Messaging forMicrosoft Exchange or IBM Lotus Domino system.If you are configuring your MSS system to route traffic overan existing corporate Windows domain rather than theMSS private Windows domain, do not select this option.

If you are configuring your MSS to route traffic over the privateMSS Windows domain, selecting this option will increasevoice mail system security and decrease traffic on thecorporate network. However, if you do not connect to thenetwork, users can access the voice mail system only throughthe Telephone User Interface without client applications. Ifyou select this option, you will not have IMAP access to themessage store or LDAP access to subscriber data. Thereforeyou cannot access your voice mail mailbox with any clientapplication.

DNS

Field DescriptionServersaddresses, inorder of use

Specifies the IP address of each DNS server used by ModularMessaging MASs.This information is used to resolve computer names to IPaddresses. Enter the IP addresses in the order in which an MASwill query subsequent DNS servers if the previous server doesnot contain the appropriate host record. The search order isfrom the top of the list down.Leave the DNS blank when connecting a Modular Messagingfor MSS system to a private LAN.

Append theseDNS suffixes (inorder)

Specifies the name of each DNS domain to search in order ofuse. The search order is from the top of the list down.Leave the DNS suffixes blank when connecting a ModularMessaging for MSS system to a private LAN.

Name DescriptionUse this connection’sDNS suffix in DNSregistration

For DHCP only, if the DNS suffix has not previously beenregistered with the DNS server, select this check box toregister the suffix.The DNS suffix is the entire Fully Qualified Domain Nameminus the specific host or computer name.



Name DescriptionRegister thisconnection’saddresses in DNS

For DHCP only, select this check box to register MSS andMAS IP addresses with the DNS server for lookup.

WINS For hosts that run NetBIOS over TCP/IP, specify the IPaddress of the preferred WINS server that resolvesNetBIOS computer names to IP addresses.

MASs

Field DescriptionSubnetmask

When using static IP addressing, specify the subnet mask for thesubnet on which the MASs reside.The subnet mask must be in the range 128.0.0.0 to255.255.255.254. The uppermost bit of the subnet mask must be a1. The lowest bit must be a 0. For example, 255.255.255.0 is valid,but 0.255.255.255 and 255.255.255.255 are not valid.

Defaultgateway

Specifies the IP address of the default gateway for the LAN or subnetwhere the MASs reside.

MSS

Field DescriptionSubnetmask

When using static IP addressing, specify the subnet mask for thesubnet on which the MSS resides.The subnet mask must be in the range 128.0.0.0 to 255.255.255.254.The uppermost bit of the subnet mask must be a 1. The lowest bitmust be a 0. For example, 255.255.255.0 is valid, but 0.255.255.255and 255.255.255.255 are not valid.

Defaultgateway

Specifies the IP address of the default gateway for the LAN or subnetwhere the MSS resides.Leave this field blank when connecting a Modular Messaging forMSS system to a private LAN.

Related topics:Corporate MM server networking details on page 29

Windows domain field descriptionsUse this page to specify the details of the Corporate Windows domain to which you want toadd the Modular Messaging system. You can specify the details of the Corporate Windowsdomain only if you have not selected Do not connect MM to the corporate network on theCorporate network details page.

Networking


Field DescriptionJoin a privateWindows domain

Select this option if you want Modular Messaging to join theprivate Windows domain.

Private Windowsdomain name

Specifies the name of the private Windows domain that youwant Modular Messaging system to join.The name of the private Windows domain is automaticallygenerated by the DCT and you can modify this. This namemust be unique throughout the messaging network andshould not be the same as the corporate Windows domainname.

Join a corporateWindows domain

Select this option if you want Modular Messaging toconnect to the corporate Windows domain.

Corporate Windowsdomain name

Specifies the name of the corporate Windows domain thatyou want the Modular Messaging system to join.

Domain controller'shost name

Specifies the host name of the domain controller of thecorporate Windows domain that you want the ModularMessaging system to join.

There are severalcorporate Windowsdomains

Select this check box if there are multiple corporateWindows domains in the customer’s network.

Authenticationmethod

Select the authentication method for securecommunication to the Windows Domain Controller over theCorporate LAN. The authentication method depends on theconfiguration of Active Directory. Either Kerberos orWinbind are required if anonymous access security isrestricted on the domain controller. Kerberos requires thecorporate domain administrator account. The defaultoption will use anonymous Winbind access.This field is enabled only if you select the Join corporatewindows domain option.

Kerberos Realm Enter the fully qualified name of the Kerberos realm. Thisfield is enabled only if you select Kerberos in theAuthentication method field. Use only alpha characters,numbers, and the hyphen character (-), period, or theunderscore character (_) in the Kerberos Realm field.

Corporate MM server networking details field descriptionsFor Modular Messaging Message Store Server (MSS) systems, use this page to identify theMSS and Messaging Application Servers (MASs) to the corporate network. For ModularMessaging Microsoft Exchange and IBM Lotus Domino systems, identify the MASs to thecorporate network. Provide the IP addresses and Fully Qualified Domain Names (FQDNs) foreach server. Be sure to use only valid TCP/IP addresses.



MSS Server information

Field DescriptionFullcomputername

For Modular Messaging for MSS systems only, specify the FullyQualified Domain Name (FQDN) of the MSS.Avaya recommends that computer names be shorter than 10characters for ease of data entry. The fully qualified domain name(computer plus domain name) must be 64 or fewer characters. Useonly lower-case alpha characters, numbers, and the hyphencharacter (-). The first character cannot be a number.

IP address For Modular Messaging for MSS systems only, you must assign astatic IP address to the MSS, even if the system uses DHCP toassign most IP addresses.

NetBIOSname

For Modular Messaging for MSS systems only, specify the NetBIOSname of the MSS. This allows applications on the MASs and theMSS to communicate over the private LAN.The DCT automatically copies the full computer name that youentered for the MSS to this field. However, you can modify this name.Avaya recommends that the NetBIOS name be shorter than 10characters for ease of data entry. The NetBIOS name can be 1 to 15characters.Use only lower-case alpha characters, numbers, and the hyphencharacter (-) or the underscore character (_). The first charactercannot be a number.

MAS details

Field DescriptionFullcomputername

Specifies the Fully Qualified Domain Name for each MAS that is partof the voice mail domain.For Modular Messaging for MSS only, the first MAS that is installedbecomes the domain controller. The name of this domain controllercannot be changed after the installation.Avaya recommends that computer names be shorter than 10characters for ease of data entry. The fully qualified domain name(computer plus domain name) must be 64 or fewer characters. Useonly lower-case alpha characters, numbers, and the hyphencharacter (-). The first character cannot be a number.

IP address When using static IP addressing, specify the IP address of each MASthat is part of the voice mail domain.

NetBIOSname

Specify the NetBIOS name for each MAS that is part of the voice maildomain.This allows applications on the MASs and the MSS to communicateover the private LAN. The DCT automatically copies the full computername that you entered for the MSS to this field. However, you canmodify this name.

Networking


Field DescriptionAvaya recommends that the NetBIOS name be shorter than 10characters for ease of data entry. The NetBIOS name can be 1 to 15characters.Use only lower-case alpha characters, numbers, and the hyphencharacter (-) or the underscore character (_). The first charactercannot be a number.The NetBIOS name of an MAS cannot begin with mas.

Aliases and ART nicknames field descriptionsUse 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) nicknamefor 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.

Field DescriptionAlias 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 Fullcomputer name that you entered for the MSS on the Corporate MMserver networking details page to this field. However, you can modifythis name.You can specify as many as five aliases. If you specify more thanone alias, separate each name with a space. Each name must beunique on the Modular Messaging system and on the network.

ARTnickname

Specifies the ART nickname generated for the specified MAS.The server that you register with an ART must have switchconnectivity through either the INADS line or an IP address.

Private network field descriptionsFor a Modular Messaging for MSS system only, use this page to select the range of IPaddresses used on the private LAN. You can also use this page to change these default IPaddresses.

Important:During installation, the Modular Messaging Configuration Wizard (MMCW) assigns specificprivate network IP addresses within the selected range to each MAS in the voice maildomain. The MASs use the assigned address to communicate with the MSS. This IP addressmust match the IP address administered for each MAS during MSS installation.



Field DescriptionUse IP addresses in thisrange for the privatenetwork

Select the range of IP addresses to use for the privatenetwork. Select a range of addresses that does notconflict with IP addresses on your corporate network.

Automatically assigned information

Field DescriptionChange defaultinformation

Select this check box if you want to change any of the defaultprivate LAN IP addresses.

Assigned IPaddresses

Use these fields to change the IP addresses that the MSS andMASs use to communicate on the private LAN.The new IP addresses must match the IP addressesadministered for each MAS during MSS installation.If you do not change the IP addresses, this field shows thedefault private LAN addresses that will be used for the MSS andeach MAS within your selected IP address range.

Message store setup

Exchange message store field descriptionsFor Modular Messaging for Microsoft Exchange only, use this page to identify the Exchangemessage store, directory server, Exchange version, the customer account group name, andusers or groups who need administrative access to the Modular Messaging system. If you donot want the Modular Messaging container to be created at the root of the Windows domain,use this page to change the location of the container from its default location to one of yourchoice.

Field DescriptionPeer Exchangeserver

Specifies the host name of the Microsoft Exchange messagestore server.The peer Exchange server is the server from which an MASsends call-answered messages, and where the ExternalCaller mailbox is created.The name can be from 2 to 15 characters, including anyalphanumeric character and the following characters: , - _ %^ & * ( ) ~ @ and spaces.

Peer directoryserver

Specifies the host name of the Active Directory server that willbe used by Modular Messaging.

Message store setup


Field DescriptionThe name can be from 2 to 15 characters, including anyalphanumeric character and the following characters: , - _ %^ & * ( ) ~ @ and spaces.

Use defaultcontainer

By default, the Modular Messaging container, named Octel, iscreated at the root of the Windows domain. This containerstores the directory objects required for the MessagingApplication Server and Mailbox Monitor Server softwarecomponents.Clear this box if you want to use a different location for theModular Messaging container.

Container Specifies the Active Directory container for ModularMessaging service accounts. If you do not want to use thedefault container, specify the name of the active directorycontainer where you want the Octel container created.For example, if you want an Octel container at cn=Octel,ou=whereever, dc=foo, dc=qux, dc=com, you should enterou=whereever, dc=foo, dc=qux, dc=com in thecontainer field.

Exchangeversion

Specifies the version number of Microsoft Exchange that youare using for this Modular Messaging system.

Customeraccount groupname

Specify the name of the group (or click Select to browse forthe name) that was created on the Active Directory server foraccess to the Modular Messaging system.

Systemadministrativeaccess

Right-click to specify the name of the user or group (or clickAdd to browse for the name) that was created on the ActiveDirectory server for system administrative access to theModular Messaging system.

Subscriberadministrativeaccess

Right-click to specify the name of the user or group (or clickAdd to browse for the name) that was created on the ActiveDirectory server for subscriber administrative access to theModular Messaging system.

SeveralExchangeenvironments

Select this check box if you have more than one Exchangeenvironment in the enterprise. If you select this check box, theDCT enables the Details box.

Details Use this field to provide information about the additionalMicrosoft Exchange environments.

Domino message store field descriptionsFor Modular Messaging for IBM Lotus Domino only, use this page to identify the Dominoservers, Notes ID information, Windows domain, and other information unique to the Dominoconfiguration.



Field DescriptionDominodirectorydatabase

Specifies the name of the Domino directory database.The Domino directory database stores subscriber information aswell as voice mail domain documents.This field defaults to names.nsf.

Primarydirectoryserver

Specifies the host name of the primary directory server.The Domino directory database resides on the primary directoryserver. Modular Messaging software regularly checks theDomino directory to obtain subscriber addresses and updatePerson documents.The name can be from 2 to 15 characters, including anyalphanumeric character and the following characters: , - _ % ̂ & *( ) ~ @ and spaces.

Peer mailserver

Specifies the host name of the peer mail server.The peer mail server is the Domino server that the MASs use tosubmit messages for delivery.Leave this field blank if your primary directory server will alsofunction as your peer mail server.The name can be from 2 to 15 characters, including anyalphanumeric character and the following characters: , - _ % ̂ & *( ) ~ @ and spaces.

Secondarydirectoryserver

Specifies the host name of any required secondary directoryservers.You must enter secondary directory server names when theMASs in the VMD support subscribers with Notes mail files in twoor more Domino domains.The name can be from 2 to 15 characters, including anyalphanumeric character and the following characters: , - _ % ̂ & *( ) ~ @ and spaces.

Use differentcredentials perMAS

Select this check box to enter a different Notes ID, Notespassword, and mail file for each MAS.Leave the box clear to use the same Notes ID, Notes password,and mail file for all MASs in the VMD.

MAS#, NotesID, Passwordand Mail file

If the Use different credentials per MAS box is not checked,ALL appears in the MAS# column. In the ALL row, enter the NotesID, Notes password, and mail file that will be used by all MASs inthe VMD.If the Use different credentials per MAS box is checked, foreach MAS in the VMD, enter the Notes ID, Notes password, andMail file.The Notes ID, Notes password, and mail file are created whenthe Domino administrator registers each MAS as a Notes user.

MAS ACLgroup name

For Modular Messaging for IBM Lotus Domino only, specify thename of the MAS Access Control group.The MAS access control group is created during systeminstallation when setting up Domino as part of preparing to installModular Messaging software. The group is then added to the

Message store setup


Field DescriptionDomino directory in each Domino domain that the MASs mustaccess.

Accounts and passwords

MSS passwords field descriptionsUse this page to specify the LDAP, IMAP, and Message Waiting Indicator (MWI) passwords tobe set up during installation. The MSS is configured to allow access only by those computersthat are identified as trusted servers. During installation, each MAS is identified to the MSSas a trusted server and is assigned the same LDAP password. Likewise, the Message WaitingIndicator server (also known to the MSS as the VVSTS server) is identified as a trusted serverand assigned a password. The IMAP password (known to the MSS as the IMAP4 TUIPassword) is also updated.

Note:If you are analyzing a system in preparation for an upgrade, you can start with the originalDCT file used to install the system. The LDAP, MWI, and IMAP passwords will be retainedwhen analyzing the system. Alternatively you can manually enter the passwords into theDCT file, after the analysis is complete.

Trusted Server passwordsThe LDAP password must differ from the IMAP and MWI passwords.

Field DescriptionLDAP Specifies the LDAP password.

The LDAP password must not be identical to the IMAP or MWI password. Itmust match the LDAP password assigned to each MAS during MSStrusted server administration. The password allows the MASs to set andretrieve directory information.The password can be from 5 to 10 characters, including any alphanumericcharacter and the following characters: # % ( ) + -_ / . ? @ [ ] { } and ~ .Avaya recommends that a password contain at least three of the followingfour entry classes: lowercase character, uppercase character, number, andpunctuation mark or symbol.

IMAPI Specifies the IMAPI (MWI) password.The IMAPI password must not be identical to the LDAP password. It mustmatch the password assigned to the VVSTS or Message Waiting Indicator(MWI) server during MSS trusted server administration. The MailboxMonitor monitors subscriber mailboxes on the MSS to determine when newmessages match MWI or Call Me rules.



Field DescriptionThe password can be from 5 to 10 characters, including any alphanumericcharacter and the following characters: # % ( ) + -_ / . ? @ [ ] { } and ~ .Avaya recommends that a password contain at least three of the followingfour entry classes: lowercase character, uppercase character, number, andpunctuation mark or symbol.

IMAP4 Specifies the IMAP password.The IMAP password must not be identical to the LDAP password. It mustmatch the IMAP4 TUI password updated during MSS installation. IMAPallows the MASs to access subscriber messages on the MSS.The password can be from 5 to 10 characters, including any alphanumericcharacter and the following characters: # % ( ) + -_ / . ? @ [ ] { } and ~ .Avaya recommends that a password contain at least three of the followingfour entry classes: lowercase character, uppercase character, number, andpunctuation mark or symbol.

Field DescriptionMSS LocalMachine

Specifies the password for the MSS local machine. This passwordis used for networking with other messaging servers.The password can be from 5 to 10 characters, including anyalphanumeric character and the following characters: # % ( ) + -_ / . ?@ [ ] { } and ~ .Avaya recommends that a password contain at least three of thefollowing four entry classes: lowercase character, uppercasecharacter, number, and punctuation mark or symbol.

Related topics:Password guidelines on page 80

MAS accounts and passwords field descriptionsUse this page to specify the name and password of the local administrator account for eachMAS in the VMD. The number of accounts that can be administered on this page correspondsto the number of MASs entered on the Voice Mail Domain page. You can change the number ofadministrable accounts by changing the value on the Voice Mail Domain page.

Caution:The Modular Messaging Configuration Wizard (MMCW) renames the MAS localadministrator account to the Logon name specified on this page for each MAS. Whenconfiguring a Modular Messaging for Microsoft Exchange or IBM Lotus Domino system withcustomer-provided equipment (CPE) MAS, you might not want to rename the MAS localmachine administrator account. Check with your customer administrator to verify if they wantthe MAS local machine administrator account name and password to be changed. To avoidrenaming the MAS local machine name and password, enter the current local machine nameand password on this page.



Field DescriptionLogonname

For each MAS, specify the name of the account used for local MASadministration.For MSS configurations, if you chose to create the private Windowsdomain on the MSS message store page, the account name andpassword that you choose for MAS 1 will become the DomainAdministrator account (dom-admin) when MAS1 is promoted to be adomain controller. However, if you join the corporate Windowsdomain, the account on MAS1 remains a local administrator.When you join the MSS to the appropriate Windows domain using theMSS message store page, the dom-admin account is used for privatedomains and the customer account is used for corporate domains.This is the account that is used for system backups.The name can be from 4 to 32 characters, including any alphanumericcharacter and the following characters: . - and _ .Do not include the abbreviation admin in the logon name or a warningis issued. If no value is entered, the DCT supplies a default logonname. You can modify this later, if required.

Password Specifies the password for each MAS account.The password can be from 7 to 32 characters, including anyalphanumeric character and the following characters: # % = + -_ ( ), . / ? @ [ ] { } and ~ .Avaya recommends that a password contain at least three of thefollowing four entry classes: lowercase character, uppercasecharacter, number, and punctuation mark or symbol. The DCT doesnot accept a password that contains the associated account name. Ifno value is entered, the DCT supplies a default password. You canmodify this later, if required.All passwords are encrypted before being stored in the DCT file.

Logon accounts and passwordsFor Modular Messaging for MSS systems, if the system is installed with a private Windowsdomain, logon accounts are created when the Modular Messaging Configuration Wizard runs.For any Modular Messaging system that is installed into the corporate Windows domain, logonaccounts must be created on the corporate Windows domain controller prior to configuring theMAS. For more information about creating logon accounts, see the Installation and Upgradesguide for your configuration.

Technical support accountRemote support personnel use the technical support account to access the system and providetechnical support. In a Modular Messaging for Microsoft Exchange system, the technicalsupport account is part of the Domain Users group and has associated permissions.

Customer accountThe customer account is used by customers to monitor the system. For a Modular Messagingfor Microsoft Exchange or IBM Lotus Domino system, the customer account is used to installand administer the Modular Messaging system. For a Modular Messaging with Microsoft



Exchange system, the customer account is part of a Modular Messaging security group thatis created during the installation process. During an installation, permissions are assigned tothis group.

For an explanation of permissions required for the Modular Messaging security group, see theAdministrator reference appendix of Modular Messaging for Microsoft Exchange Installationand Upgrades Guide. For the procedures to create the customer account, create the customeraccount security group, and assign permissions to the group, see the installation chapters ofthe same book. For more information about creating the customer account for IBM LotusDomino systems, see Modular Messaging for IBM Lotus Domino Installation and UpgradesGuide. For Microsoft Exchange and IBM Lotus Domino systems, the customer account isequivalent to the service account, for example, mmacct. In a Modular Messaging for MSSsystem, the customer account is not used to install Modular Messaging services.

Related topics:Logon accounts and passwords field descriptions on page 41

Logon accounts and passwords field descriptionsUse this page to specify the name and password of the technical support and customeraccounts. These accounts are domain-wide.

Technical support


Specifies the name of the logon account used by support personnelfor remote system administration.The name can be from 4 to 32 characters. Do not include theabbreviation craft in the logon name or a warning is issued. If no valueis entered, the DCT supplies a default logon name. You can modifythis later, if required.

Password Specifies the password for the logon account used by supportpersonnel for remote system administration.The password can be from 8 to 32 characters, including anyalphanumeric character and the following characters: # % = + -_ ( ), . / ? @ [ ] { } and ~ .Avaya recommends that a password contain at least three of thefollowing four entry classes: lowercase character, uppercasecharacter, number, and punctuation mark or symbol. The DCT doesnot accept a password that contains the logon name. If no value isentered, the DCT supplies a default password. You can modify thislater, if required.



Field DescriptionAll passwords are encrypted before being stored in the DCT file.

Customer account


Specifies the name of the logon account used by the customer forsystem administration.The name can be from 4 to 32 characters. Do not include theabbreviation cust in the logon name or a warning is issued. If no valueis entered, the DCT supplies a default logon name. You can modifythis later, if required.

Password Specifies the password for the logon account used by the customerfor system administration.The password can be from 7 to 32 characters, including anyalphanumeric character and the following characters: # % = + - _( ) , . / ? @ [ ] { } and ~ .Avaya recommends that a password contain at least three of thefollowing four entry classes: lowercase character, uppercasecharacter, number, and punctuation mark or symbol. The DCT doesnot accept a password that contains the logon name. If no value isentered, the DCT supplies a default password. You can modify thislater, if required.All passwords are encrypted before being stored in the DCT file.

Related topics:Logon accounts and passwords on page 40

MAS service account field descriptionsYour Modular Messaging system configuration determines the selections on this page.

Field DescriptionRun MAS servicesusing LocalSystem

For Modular Messaging for MSS, you must run MASservices as LocalSystem. The DCT automaticallyselects this option.

Run MAS servicesusing this account

For Modular Messaging for Exchange or IBM LotusDomino systems, the DCT selects this optionautomatically.

Logon name andPassword

For Modular Messaging for Microsoft Exchange and IBMLotus Domino systems, the logon name and passwordthat you specified for the customer account on the Logonaccounts and passwords page are displayed. Thesevalues cannot be changed on the MAS service accountpage.



Field DescriptionRequired non-defaultadministrative roles

Modular messaging provides some RBAC roles bydefault during installation. If you want additional roles,specify the roles and the required permissions in thisfield.

Trusted serversTrusted servers are clients that have permission to read data from and write data to the LDAPdirectory on the MSS. The following applications can be configured as trusted servers:

• Directory Enabled Management (DEM) — An application that uses Avaya DirectoryServer to facilitate administration of Modular Messaging for MSS systems from acentralized location

• Mailbox Manager — MSS administrators can use the Mailbox Manager application toadminister subscriber data and for other Avaya voice mail products in an enterprise

• ProVision — An application that is used to provision users on Avaya CommunicationManager, DEFINITY switches, and Modular Messaging systems

• Avaya Site Administrator — Avaya Site Administrator Release 2 or later and AvayaMultiSite Administrator Release 2.1 or later support the administration of ModularMessaging subscriber data

If your MSS system will hasmore than one server that hosts either the Mailbox Managerapplication or the Avaya Site Administrator application, specify the details for the additionalservers on the Additional optional MSS trusted servers page.

Related topics:Optional MSS trusted servers field descriptions on page 43Additional optional MSS trusted servers field descriptions on page 44

Optional MSS trusted servers field descriptionsUse this page to specify information about trusted servers including the server name, fullcomputer name, IP address, and the password of the server where you want to install theapplication. The DCT uses this information to set up trusted servers for the selectedapplications during Modular Messaging configuration.

Field DescriptionDirectoryEnabledManagementserver

Select this check box and specify the trusted server details ifyou want a Directory Enabled Management (DEM)server setup during system configuration.



Field DescriptionMailbox Manager Select this check box and specify the trusted server details if

you want Mailbox Manager set up during system configuration.You must use lowercase for the Mailbox Manager servername.

ProVision Select this check box and specify the trusted server details ifyou want ProVision set up during system configuration.You must use lowercase for the ProVision server name.

SiteAdministrator

Select this check box and specify the trusted server details ifyou want Avaya Site Administrator set up during systemconfiguration.You must use lowercase for the Avaya Site Administratorserver name.

Trusted servername

Specifies the name that you want to use to add the optionalserver to the list of trusted servers.

Full computername

Specifies the full computer name of the server where you wantto install the selected application.

IP Address Specifies the IP address of the server where you want to installthe selected application.It is mandatory to specify a valid IP address, if your ModularMessaging system does not use a DHCP server. If yourModular Messaging system uses a DHCP server, you can skipthis field.

Password Specifies the password to access the server where theapplication is installed.For security reasons, ensure that account names andpasswords are site-specific. Also, be sure to file records ofpasswords securely.The password can be from 5 to 10 characters, including anyalphanumeric character and the following characters: # % ( )+ - _ / . ? @ [ ] { } and ~ .Avaya recommends that a password contain at least three ofthe following four entry classes: lowercase character,uppercase character, number, and punctuation mark orsymbol.

Related topics:Trusted servers on page 43

Additional optional MSS trusted servers field descriptionsIf your Modular Messaging for MSS system will have more than one server that hosts theMailbox Manager application or the Avaya Site Administrator application, use this page tospecify the details for these additional servers. You can leave the IP address field blank if youare planning to use a DHCP server for the MSS system. However, the Mailbox Managerapplication does not work with dynamic IP addresses.



Select a check box and specify the trusted server details for each additional optional trustedserver that you want set up during system configuration.

Field DescriptionTrustedserver name

Specifies the name of the trusted server where you want to installthe selected application.Use lowercase for all server names.

Fullcomputername

Specifies the full computer name of the server where you want toinstall the selected application.If your Modular Messaging system uses a DHCP server, you mustspecify the full computer name.

IP Address Specifies the IP address of the server where you want to install theselected application.You must specify a valid IP address, if your Modular Messagingsystem does not use a DHCP server. If your Modular Messagingsystem uses a DHCP server, you can skip this field.

Password Specifies the password to access the server where the applicationis installed.For security reasons, ensure that account names and passwordsare site-specific.The password can be from 5 to 10 characters, including anyalphanumeric character and the following characters: # % ( ) + -_ / . ? @ [ ] { } and ~ .Avaya recommends that a password contain at least three of thefollowing four entry classes: lowercase character, uppercasecharacter, number, and punctuation mark or symbol.

Related topics:Trusted servers on page 43

TTS sessions and languages

TTS and announcements field descriptionsUse this page to select the languages used for Telephone User Interface (TUI) announcementsand Text-to-Speech conversion. This page is also used to administer the number of TTSsessions that run on each MAS.

TTS sessions and languages


Field DescriptionAnnouncementlanguages

Select at least one language that the system uses to play allTUI prompts. To select multiple languages, hold down thecontrol key as you select each additional language.

TTS languages Select at least one language that the system uses to converttext into speech. To select multiple languages, hold down thecontrol key as you select each additional language.TTS is required for playing subscriber names (when notrecorded), fax header information, and text messages.When selecting TTS languages, be sure to include alllanguages that were selected for announcements.

TTS sessions Specifies the number of TTS sessions that run on each MASin the voice mail domain.Modular Messaging for MSS comes with twelve TTS sessionlicenses per MAS. For Modular Messaging for MicrosoftExchange or IBM Lotus Domino, you can purchase additionallicenses up to a maximum of twelve times the number of MASsin the VMD. The TTS sessions for these configurations canalso be distributed in any way across the MASs as long as thetotal number of twelve sessions per MAS is not exceeded.Configure MASs that do not handle calls with 0 TTS sessions.

MAS servers

MAS servers and Modular Messaging servicesMAS serversWith Modular Messaging for Exchange and Domino, you can have ten MASs to handle calls,whereas with Modular Messaging for MSS, you can have a maximum of five MASs to handlecalls. The Modular Messaging configuration program automatically installs the CallerApplications Editor on each MAS.

An additional supplementary server can provide special services such as the Tracing service.Although the supplementary server is sometimes called an MAS, it cannot handle calls. Asupplementary server can use Avaya-provided hardware or customer-provided hardware.

If the customer rather than Avaya provides the hardware for the supplementary server, seeAvaya Modular Messaging Installation and Upgrades, specific to your Modular Messagingconfiguration. Any customer-provided supplementary server must meet the requirementsdefined in the Avaya Modular Messaging Concepts and Planning Guide.

The Modular Messaging system may have optional servers in addition to the supplementaryserver. For example, Web Subscriber Options (WSO) can reside on its own server rather thanon an MAS. Or, there may be a separate Offline Access (OLA) server for offline access to



messages. Using OLA, subscribers can access new Call Answer messages even when themessage store is offline (not available). If a message store server is not available, the MAScontinues to queue any new Call Answer messages in a local store until the message storeserver is available. These optional servers are not configured by the DCT and should not beincluded in the number of MASs entered on the Voice Mail Domain page.

The Modular Messaging Web Client must always be on its own server. This application cannotreside on any MAS or on the supplementary server.

Modular Messaging servicesMessage Waiting Indicator (MWI):

The MWI service alerts subscribers when messages meeting specified criteria arrive in theirmailbox. The MWI service uses the Mailbox Monitor to check when new messages arrive anddetermines when the indicator on a subscriber telephone must be set or reset.

Call Me:

The Call Me service makes calls to subscribers when messages meeting specified criteriaarrive in their mailbox. The Call Me service uses the Mailbox Monitor to check when newmessages arrive.

Fax Sender:

The Fax Sender service supports fax messaging for the Modular Messaging system.

Web Subscriber Options (WSO) server:

Web Subscriber Options (WSO) provides a Web user interface that enables ModularMessaging subscribers to change their mailbox settings. The WSO server application canreside on an MAS or on a stand-alone server. For a Modular Messaging for MSS configuration,the WSO server can also reside on a Modular Messaging web server.

Tracing:

The Tracing service maintains a connection with all MASs in a voice mail domain. It recordsall events of diagnostic importance to the operation history database. The Tracing service canbe used by experienced system administrators or technical support personnel to diagnosecommon problems with the software. The Tracing service can also gather data to generatereports.

Auditing:

The Auditing service allows customers to audit administrative configuration changesperformed on an MM system. Whenever an administrator makes a significant change to theconfiguration of an MM system, the key information specific to the change is logged to the MASthat runs the Auditing service. Passwords and similar sensitive data are never logged. Theaudit logs will be stored within the MM system for a specified period before they are deletedor overwritten.

Related topics:MM service selection field descriptions on page 48Tracing field descriptions on page 49Web Subscriber Options field descriptions on page 50

MAS servers


Guidelines for configuring Modular Messaging servicesThis topic provides guidelines for configuring Modular Messaging services.

Use the following guidelines to configure Modular Messaging services:

• If only one MAS is installed, put all required services on that computer.

• If you enable Call Me, MWI service, or both, the system automatically enables MailboxMonitor service. If you enable both services, do so on the same MAS.

• If more than one MAS is installed, see the Avaya Modular Messaging Concepts andPlanning Guide for the recommended load balancing of services between multipleservers.

• If the Modular Messaging system uses a supplementary server, you can place CallMe, MWI, Mailbox Monitor, and Tracing services on it.

• Due to the higher traffic associated with the Tracing service, install the Tracing serviceon an MAS without other services. Or, install the Tracing service on an MAS with few orno ports.

Related topics:MM service selection field descriptions on page 48Tracing field descriptions on page 49Web Subscriber Options field descriptions on page 50

MM service selection field descriptionsUse this page to select the Modular Messaging services you want to run on each MAS in thevoice mail domain. The number of MASs that you can administer on this page corresponds tothe number of MASs entered on the Voice Mail Domain page. This number includes all MASs,including the supplementary server. You can change the number of administrable MASs bychanging the value on the Voice Mail Domain page.

To enable a service, select the check box next to the name of the service and select the buttonfor that service under the number for the appropriate MAS. If you select Tracing or WebSubscriber Options (WSO) services, specify the details of these services on the Tracing andWeb Subscriber Options pages respectively.

Field DescriptionMessageApplication

Select the check box directly under each MAS that handlesmessaging calls.

MessageWaitingIndicator (MWI)

Select this check box to enable the MWI service on the specifiedMAS.It is recommended that the MWI and Call Me services shouldnot be run on a server that runs the Tracing service.



Field DescriptionCall Me Select this check box to enable the Call Me service on the

specified MAS.It is recommended that the MWI and Call Me services shouldnot be run on a server that runs the Tracing service.

Fax Sender Select this check box to enable the Fax Sender service on thespecified MAS.

Web subscriberoptions server

Select this check box to enable the Web Subscriber Optionsserver application on the specified MAS.

Caution:If the WSO server runs on a separate server or is co-resident on the Web Client server, do not activate the WSOserver on any MAS in the VMD. For more information aboutinstalling the WSO server on a non-MAS server, see WebSubscriber Options for Modular Messaging ServerInstallation.

Tracing Select this check box to enable the Tracing service on thespecified MAS.

Auditing Select this check box to enable auditing on the specified MAS.

Related topics:MAS servers and Modular Messaging services on page 46Guidelines for configuring Modular Messaging services on page 48

Tracing field descriptionsUse this page to provide information about the Tracing service.

Field DescriptionNone Select this option if you do not want to install the Tracing

service.

On a MAS orsupplementaryserver

Select this option if you want to install the Tracing serviceon an Avaya-provided supplementary server.

On customer-provided equipment

Select this option if you want to install the Tracing serviceon customer-provided equipment.

Server name Specifies the name of the server where the Tracing serviceis installed.Avaya recommends that computer names be shorter than10 characters for ease of data entry.The fully qualified domain name (computer plus domainname) can be from 1 to 64 characters, including lower

MAS servers


Field Descriptioncase alpha characters, numeric characters, and thehyphen (-). The first character cannot be a number.

Server IP address Specifies the IP address of the server where the Tracingservice is installed.

Software installationpath

Specifies the location where you want to install the Tracingservice. Enter the full path or click the button next to thebox and browse to the location where you want to installthe Tracing service.

Logon account name Specifies the name to use to log on to the server.

Password Specifies the password associated with the Logon accountname.

Related topics:MAS servers and Modular Messaging services on page 46Guidelines for configuring Modular Messaging services on page 48

Web Subscriber Options serverThe Web Subscriber Options (WSO) server is a Modular Messaging service that can beinstalled on a supplementary server or on an MAS. A supplementary server can use Avaya-provided or customer-provided hardware. WSO provides a Web user interface that enablesModular Messaging subscribers to change their mailbox settings.

Related topics:Web Subscriber Options field descriptions on page 50

Web Subscriber Options field descriptionsUse this page to provide information about the WSO server.

Field DescriptionNone Select this option if you do not want to install the WSO

server.

On a MAS orsupplementary server

Select this option if you want to install the WSO server ona MAS or supplementary server.

On an Avaya optionalserver or customerprovided equipment

Select this option if you want to install the WSO server onan Avaya optional server or on customer-providedequipment.

Server name Specifies the name of the server where the WSO serveris installed.



Field DescriptionAvaya recommends that computer names be shorter than10 characters for ease of data entry.The fully qualified domain name (computer plus domainname) can be from 1 to 64 characters, including lowercase alpha characters, numeric characters, and thehyphen (-). The first character cannot be a number.

Server IP address Specifies the IP address of the server where the WSOserver is installed.

Software installationpath

Specifies the location where you want to install the WSOserver. Enter the full path or click the button next to thebox and browse to the location where you want to installthe WSO server.

Logon account name Specifies the name to use to log on to the server.

Password Specifies the password associated with the Logonaccount name.

Related topics:MAS servers and Modular Messaging services on page 46Guidelines for configuring Modular Messaging services on page 48Web Subscriber Options server on page 50

Web Client serverThe Modular Messaging Web Client enables subscribers to access, create, send, and managevoice, text, fax, and corporate e-mail messages using a Web browser. The Web Client issupported only for the Modular Messaging for MSS configuration. The Modular MessagingWeb Client server uses IMAP4 client connections to communicate with the MSS.

Related topics:Web Client server field descriptions on page 51

Web Client server field descriptionsUse this page to specify information about the Modular Messaging Web Client server.

Important:The Modular Messaging Web Client must always be on its own server. This applicationcannot reside on any MAS or on the supplementary server.

MAS servers


Field DescriptionNone Select this option if you do not want to install the Web Client

server.

On an Avayaoptional server

Select this option if you want to install the Web Client serveron an Avaya-provided supplementary server.

On customer-providedequipment

Select this option if you want to install the Web Client serveron an Avaya optional server or on customer-providedequipment.

Server name Specifies the name of the Web server where the Web Clientserver will be installed.Avaya recommends that computer names be shorter than 10characters for ease of data entry.The fully qualified domain name (computer plus domain name)can be from 1 to 64 characters, including lower case alphacharacters, numeric characters, and the hyphen (-). The firstcharacter cannot be a number.

Server IPaddress

Specifies the IP address of the server where the Web Clientserver is installed.

Softwareinstallation path

Specifies the location where you want to install the Web Clientserver. Enter the full path or click the button next to the box andbrowse to the location where you want to install the Web Clientserver.

Logon accountname

Specifies the name to use to log on to the server.

Password Specifies the password associated with the Logon accountname.

Related topics:Web Client server on page 51

Language packsThe languages that you specify on the Language packs page are installed in addition to USEnglish, which is installed by default. You can select one or more language packs. Thelanguage packs that you select on the Language packs page are not installed automaticallyon Modular Messaging client applications. This information is used as a reference whileinstalling the client applications.

If you are not running the Modular Messaging client application installation in silent mode, theinstaller prompts you to specify any additional languages that you want to install, other thanUS English. After installing additional language packs, if you want to install more languages,you can manually do so from the Install\Language Packs directory on the ModularMessaging Applications DVD.



Related topics:Language packs field descriptions on page 53

Language packs field descriptionsUse this page to select the language packs that you want to include while installing ModularMessaging client applications such as Outlook Client and Subscriber Options.

Field DescriptionChooselanguagepacks

Select the language packs that you want to include whileinstalling any of the Modular Messaging client applications suchas Subscriber Options.To select multiple language packs, press and hold the Ctrl keywhile you select the language packs.

Related topics:Language packs on page 52

Offline access field descriptionsUse this page to specify the location of the offline message store, if you want to use the ModularMessaging Offline Access (OLA) feature.

Field DescriptionOfflinestorelocation

Specifies the location where you want to install your offline messagestore. The MASs use this as an intermediate storage location formessages, allowing them to be accessed even if the message storeis offline.Enter the full path or click the button adjacent to the box and browse tothe location where you want to install the offline store.

Note:The path that you specify must be a network path that all MASs inthe VMD can access.

Message networking field descriptionsUse this page to provide information about other Modular Messaging services such asMessage Networking (MN). If you want your Modular Messaging system to communicate withan external Modular Messaging for MSS system, you can provide information about the MSSserver of the external system on this page.

MAS servers


Field DescriptionMessage networking typeand details

Specify the types of message networking service thatyou will use with this Modular Messaging system.

PBX integration

Switch integration method field descriptionsUse this page to identify the type of signaling protocol and the switch providing calls to theMASs. Switch integration (SWIN) provides connectivity between the Private Branch Exchange(PBX) and the Messaging Application Server (MAS). Modular Messaging supports multipleSWINs for switches from several major manufacturers. Customers can choose a SWIN thatrequires only minimum changes to the current infrastructure to implement Modular Messaging.

If you select a specific configuration from the list of switch integrations, the Modular MessagingConfiguration Wizard (MMCW) configures most switch settings for the Modular Messagingsystem. If you select Other, you must configure the SWIN with the Voice Mail SystemConfiguration (VMSC) tool as part of the installation.

Note:If the MultiSite feature is enabled for a voice mail domain, the Avaya SIP switch integration isselected by default and the remaining switch integration options will not be available.

Field DescriptionAvaya (QSIG) Select this option for an Avaya Q-Signaling (QSIG) integration.

Cisco (QSIG) Select this option for a Cisco QSIG integration.

Nortel NT M-1(QSIG)

Select this option for a Nortel NT M-1(QSIG) switch integration.

Siemens Hipath(QSIG)

Select this option for a Siemens Hipath (QSIG) switchintegration.

Avaya (IP H323) Select this option to configure Avaya H.323-based IP integration.This integration type is available with Avaya DEFINITY®,MultiVantage, and Communication Manager switches only.

Avaya SIP Select this option to configure Avaya SIP-based IP integration.This integration type is available with Avaya DEFINITY®,MultiVantage, and Communication Manager switches only.If MultiSite is enabled, you can only add SIP switches to the voicemail domain.

Other Select this option if you want to use a SWIN method other thanthe ones listed above. If you select this option, you must



Field Descriptionconfigure the integration using the VMSC after the installation iscomplete.

Configuration note to use for this integration

Field DescriptionIdentifier Specifies the identification number of the configuration note.

Version Specifies the product version of the switch.

Date Specifies the date of the planned switch integration.

Switch integration information field descriptionsUse this page to specify additional information about the type of switch integration that youselected on the Switch integration method page. You can specify the switch trunk, signalgroups, hunt group, and the routing pattern for the selected switch integration method. Youcan also specify the IP address for SES proxy server for the SIP configuration, and the IPaddress for the H.323 configuration.

Field DescriptionIP address Specifies the IP address assigned to the device that is

terminating the H.323 signaling link. This field is enabled andmandatory only if you select the switch integration type aseither SIP or H.323.For a DEFINITYPBX, this is the IP address of the PBX C-LAN card. For a MultiVantage or Communication ManagerPBX, this is the IP address of the PROCR.

Switch Name Enter a name for SIP switch. This is a mandatory field.

Switch trunk Specifies the identification number of the switch trunk for theswitch integration type that you selected.

Signal groups Specifies the identification numbers of signal groups that are tobe created for the switch integration type that you selected. Youmust separate each signal group entry with a comma.

Hunt group Specifies the pilot number for the hunt group that you want touse.

Routing pattern Specifies the identification number of the route pattern that youwant to create.

Gatewayaddress

Enter the IP address or fully qualified domain name (FQDN) ofthe SIP gateway / proxy.

Subnet mask Enter the subnet mask of the SIP gateway / proxy.

PBX integration


Field DescriptionDefault gateway Enter the IP address of the networking gateway that connects

the subnet on which the SIP gateway identified by the previoussetting is hosted, to the wider network.

SIP Domain Enter a fully qualified domain name to assign to the SES Server.

Phone NumberTranslationRules

Click Configure to set incoming and outgoing phone numbertranslation rules. See Phone Number Translation Rules onpage 56 for more details.

Notes Use this field to provide additional information about this switchintegration.

Phone Number Translation RulesYou can set incoming and outgoing phone number translation rules. An MAS uses thetranslation rules to convert numbers in switch-native format to canonical format when receivinginbound calls. Similarly, when making outbound calls the canonical numbers are converted toswitch-native format.

Note:You can configure translation rules irrespective of the MultiSite status; whether it is enabledor not.

Note:Switch-native format: The phone numbers that are sent to and from a switch can only beproperly understood by that switch. For example, a 4 digit extension number from an AvayaCommunication Manager in Denver will not work on a Nortel M1 in London.

Canonical format: The canonical format identifies the components of a phone number. Inorder to make phone numbers useful across switches, MultiSite-enabled ModularMessaging converts them to canonical form before they are stored.

The canonical format is +Country Code(AreaCode)SubscriberNumber.

For example, you would enter a number for a subscriber in the United States of America incanonical address format as +17203564088. The leading ‘+’ indicates that the number is incanonical format; if there is no '+' then the number is in switch-native format.

Regular Expressions are used to create translation rules. For more information on regularexpression, see the MultiSite Feature Description Guide.

Field DescriptionTest Inputs Use to enter different types of phone numbers that you expect the

MAS to handle. These phone numbers are used to test whether theyare successfully matched by an incoming rule to produce a canonicalnumber, and whether canonical number is also successfullymatched by the corresponding outgoing rule. You can add a phonenumber or delete the selected phone number.

Incomingtranslationrule

Use to describe the incoming phone number translation rules forconverting phone numbers from switch-native form to canonicalform. You can add a phone number translation rule or delete the



Field Descriptionselected phone number translation rule. You can also move theselected rule up or down in the list.

• Description: Enter a description of the type of call thetranslation rule will be applied to. For example, local switchextension, national, international, or premium-rate number.

• Match: Enter the regular expression to be used for thetranslation rule.

• Output: Enter the set of characters from the correspondinggroup in the Match part of the rule.

The output of an incoming phone number translation rule falls intoone of the following categories:

• If the rule does not match the input then there is no output,and the next rule is evaluated.

• If the rule produces an output that starts with ‘+’ then it is aterminating rule. No further rules are evaluated because acanonical number is produced. In this case, the output istaken as the final output of the rule set.

• If the rule produces output that does not start with ‘+’ thenit is a transforming rule, and the output becomes the newinput for the next rule. If no output is produced after the finalrule has been evaluated, or the output is not canonical, thenthe input dial string is deemed to be invalid.

Outgoingtranslationrule

Use to describe a matching set of outgoing phone numbertranslation rules for converting from canonical form into switch-native format. You can add a phone number translation rule or deletethe selected phone number translation rule. You can also move theselected rule up or down in the list.

• Description: Enter a description of the type of call thetranslation rule will be applied to. For example, local switchextension, national, international, or premium-rate number.

• Match: Enter the regular expression to be used for thetranslation rule.

• Output: Enter the set of characters from the correspondinggroup in the match part of the rule. If the rule produces anoutput that is recognized by the Private Branch Exchange(PBX) then it is a terminating rule. No further rules areevaluated because a switch-native number is produced. Inthis case, the output is taken as the final output of the ruleset.

• Cost: Enter a number from 0 to 10000 for each translationrule. The cost indicates how expensive it is to dial thenumber that matches a certain rule. When a terminatingoutgoing translation rule produces a switch native phonenumber, the cost associated with that call is validatedagainst the voice-mail domain-wide setting for making

PBX integration


Field Description

outbound calls. The costs specified for outbound callscontrol whether, for example, a subscriber is allowed to calljust the local extensions, or national, international, orpremium rate numbers.

Extensions and switch ports field descriptionsIf your Modular Messaging system has Digital Set Emulation (DSE) integration, use this page tospecify the starting and ending extension numbers and their corresponding switch portnumbers, for each MAS. DSE is a digital protocol that is used to connect digital telephones toswitches in order to emulate digital telephone sets.

Field DescriptionStarting extensionnumber

Specifies the starting extension number for the MAS.

Ending extension number Specifies the ending extension number for the MAS.

Starting switch port Specifies the starting switch port number for the MAS.

Ending switch port Specifies the ending switch port number for the MAS.

Dial Plan

Dial plan field descriptions

Use this page to specify information about the dial plan to be used for the selected switchintegration, including the number of digits in mailbox numbers and the range for subscribermailbox numbers.

Note:If the MultiSite feature is enabled for a voice mail domain, the Mailbox number length,Starting number, Ending number, and Prefix fields are disabled.

Field DescriptionMailbox numberlength

Specifies the number of digits that you want to have for yoursubscriber mailboxes.This field is disabled if you have enabled MultiSite.

Starting number For Modular Messaging for MSS, specifies the starting numberfor subscriber mailboxes.



Field DescriptionMailbox numbers must not start with 0.The DCT displays this number based on the number of digitsthat you have specified in the Mailbox number length field.For example, if you specified the Mailbox number length as 5,the default value for the starting number is 10000. You canmodify this to any 5 digit number.This field is disabled if you have enabled MultiSite.

Ending number For Modular Messaging for MSS, specifies the ending numberof the subscriber mailbox.The DCT displays this number based on the number of digitsthat you have specified in the Mailbox number length field.For example, if you specified the Mailbox number length as 5,the default value for the ending number is 99999. You canmodify this to any 5 digit number; however, the ending numbermust be greater than the starting number.This field is disabled if you have enabled MultiSite.

Prefix required For Modular Messaging for MSS, select this check box if youneed to prefix a number to dial the above mailbox extensions.If you select this check box, the Prefix field is enabled and aprefix must be specified.

Prefix Specifies the number that is to be prefixed to dial the specifiedmailbox extensions.This is a mandatory field if you select the Prefix required checkbox.This field is disabled if you have enabled MultiSite.

SiteConfiguration

Click Configure to configure the site group, and site mailboxnumbering schemes.

Notes Use this field to specify additional information about the dialplan.

Related topics:Site Configuration field descriptions on page 59Options field descriptions on page 61General field descriptions on page 62TUI field descriptions on page 62Auto Attendant field descriptions on page 63Auto Attendant Keys field descriptions on page 64Auto Attendant Holidays field descriptions on page 64

Site Configuration field descriptionsYou can use the Site Configuration dialog box to configure the site group, and site mailboxnumbering schemes. You can add a site or site group and edit an existing site or site group.You can delete an existing site or site group. When you choose to delete a parent site group,all the child site groups and the child sites are deleted. When a site/site group is deleted, thesubscribers of that site/site group are unable to use Modular Messaging system until they have

PBX integration


been moved to another site, or a new site, with an ID that matches the ID of the deleted site,is created.

Note:You can configure multiple sites in the DCT against one switch only. You can configure siteirrespective of the MultiSite status; whether it is enabled or not.

The site configuration data must be valid before you enable MultiSite. When MultiSite isenabled, the site configuration data must remain valid; it would not be possible to save invaliddata.

Adding a site group

Field DescriptionAdd In the Site Configuration dialog box, click the Add drop-down

list or right-click a site group. Select Add site group to open theNew Site Group dialog box.

Parent sitegroup

Select the site-group you want the new site group to be the childof. If you select <Root> as the Parent site group, the new sitegroup appears at the same level as <Root> in the site/group tree.

Site groupname

Enter a name for the site group.

Identifier Enter a unique number, for example, the country code.

Groupcontainer only

If you do not want to assign a site identifier for the site group,select the Group container only check box.

Add Click AddThe new site group appears in the Site/group tree.

Adding a site

Field DescriptionAdd In the Site Configuration dialog box, click the Add drop-down list or

right-click a site group. Select Add site to open the New Site dialogbox.

Parent sitegroup

Select the site-group you want the new site to be the child of. If youselect <Root> as the Parent site group, the new site appears at thesame level as <Root> in the site/group tree.

Site name Enter a name for the site.

Identifier Enter a unique number, for example, the country code and area code.The site identifier is always preceded by the identifier of its parentsite group. You must carefully choose the site identifier, because youcannot change its identifier, once the site is created.

Fullmailboxlength

Enter the length of the full mailbox number. Full mailbox number ofa subscriber in a MultiSite-enabled voice mail domain includes thesite group and site identifiers and the short mailbox number. Forexample, John belongs to the Boston site which is part of the United



Field DescriptionStates site group. If the site identifier is 1617 and John’s shortmailbox number is 3564088, then his full mailbox number is16173564088. If the length of the site identifier is 4 and the length ofthe short mailbox number is 7, then the full mailbox length is 11.However, when the site identifier and the short mailbox numbersoverlap, the last digit of the site identifier is also the first digit of theshort mailbox number. For example, the length of Mary’s full mailboxnumber is set to 8. If the site identifier is 4 digits (8867) and the lengthof the short mailbox number is 5 (74092), then 7, which is the lastdigit of the site identifier and the first digit of the short mailbox number,is common.

Shortmailboxlength

Enter the length of the short mailbox number. The short mailboxnumber is the number from which the site identifier is stripped.Subscribers can use the short mailbox number to send voicemessages to other subscribers in the same site.

Switch Select the switch that handles the incoming and outgoing calls forthe site.

Add Click AddThe new site appears in the Site/group tree.

Options field descriptionsYou can use the Site Configuration dialog box to set media preferences for the site or sitegroup you create. You can select Telephone or Multimedia audio device for recording theprompts.

If you want to use a telephone for composing greetings, voice messages you need to specifyyour telephone details.

Field DescriptionOptions In the Site Configuration dialog box, click the Tools drop-

down list. Select Options to open the Options dialog box.

Promptrecording andplayback

Select Telephone or Multimedia as the audio device forrecording the prompts.

Configure If you select Telephone in the Prompt recording and playbackdrop-down list, the Configure button is enabled. ClickConfigure to open the Telephone Properties dialog box.

Extensionnumber

Type your extension number or telephone number.

MessageApplicationServer name

Select the name of the messaging application server (MAS), thatyou want to connect to. Alternatively, click Browse to open the

PBX integration


Field DescriptionSelect Computer dialog box to select the Messaging Applicationserver.To select a computer, do one of the following and then click OK.

• In the Computer field, type the server name in theformat: \\servername. (Two backslashes followed by theserver name)

• In the Select Computer field, double-click to select acomputer as the server.

Apply On selecting the desired audio device in the Prompt recordingand playback drop-down list, click Apply, and then click OK.

General field descriptionsYou can use the Site Configuration dialog box to configure the site-level properties. In theSite Configuration dialog box, click Properties to open the Properties dialog box, and thenclick General.

Field DescriptionPrimarylanguage

Select the primary language to be used by the TUI. The listcontains all the languages in the voice mail domain.

Timezone Select the time zone of the site instead of the system time Zone.

Hunt group Enter a canonical hunt group number that is used by theAutomated Attendant to determine which site-specific datashould be used when handling an incoming call.

TUI field descriptionsYou can use the Site Configuration dialog box to configure the site-level properties. In theSite Configuration dialog box, click Properties to open the Properties dialog box and thenclick TUI.

Field DescriptionReceptionistMailbox

Open business hours mailbox: Enter the mailbox number towhich callers are transferred, when they require operatorassistance. The default is 0.Out of hours mailbox: Enter the mailbox number to which callersare transferred, when they require operator assistance outside ofbusiness hours. The default is 0.

Greeting starttime

• Morning: Enter the start time for the morning greeting.The default is 09:00.

• Afternoon: Enter the start time for the afternoongreeting. The default is 12:00.

• Evening: Enter the start time for the evening greeting.The default is 18:00.



Field DescriptionBusinesshours

Day: Select the day of the week for which you want to definebusiness hours. For the selected day, you can then select one ofthree options: Open All Day, Closed All Day or Open during.Avaya recommends that you set up business hours for each dayof the week.

• Open All Day: Select to specify that the office is open allday. For any day this is set, the Automated Attendantgreets callers with the appropriate morning, afternoon, orevening greeting. It uses the start times you specify in theMorning start time, Afternoon start time and Evening starttime fields to determine which greeting to play. This is thedefault setting.

• Closed All Day: Select to specify that the office is closedall day. For any day this is set, the Automated Attendantplays the closed greeting to callers. They are thentransferred to the after-hours operator mailbox.

• Open during: Select to specify the business and after-business hours for a particular day. If you select thisoption, you must enter the Open and Close times.

Open time: Enter the time designated as the start of businesshours for the selected day. During business hours, the appropriategreeting (morning, afternoon, or evening) is played. The defaultis 09:00.Close time: Enter the time designated as the end of businesshours for the selected day. After business hours, the closedgreeting is played. The default is 17:00.

Auto Attendant field descriptionsYou can use the Site Configuration dialog box to configure the site-level properties. In theSite Configuration dialog box, click Properties to open the Properties dialog box and thenclick Auto Attendant.

Field DescriptionDay greetings • Morning: Enter the start time for the morning greeting.

The default is 09:00• Afternoon: Enter the start time for the afternoon greeting.

The default is 12:00• Evening: Enter the start time for the evening greeting. The

default is 18:00.

Multilingualgreetings

Languages: Enter a prompt number in this field, if you want toreplace the default system language selection prompt with acustom prompt recorded in Visual Voice Editor. The range is 0through 9999, and the default is 0.

PBX integration


Field DescriptionIf 0 is selected, the system uses the default system languageselection prompt similar to the following: “For English, press one.Pour français, appuyez sur le deux." The prompt for each languageis in that language.Callers can select the desired language by pressing theappropriate key on their touchtone keypads. When they do, theyhear all subsequent prompts in the selected language.

Languages Select the language that you want to configure in each of thesethree fields. You can select any language supported by the TUI.

Auto Attendant Keys field descriptionsYou can use the Site Configuration dialog box to configure the site-level properties. In theSite Configuration dialog box, click Properties to open the Properties dialog box and thenclick Auto Attendant Keys.

Field DescriptionKey Select a touchtone keypad digit to configure, 1 through 9. The keys for *

and # are reserved for system use and cannot be configured.When you have selected a number, use the Action button to configurethe properties for that number. The selection then appears in the grayedout box to the right of the number.

Action Use these option buttons to configure the selected key number above.• Invalid: Select to indicate this key is an invalid option. Use this

setting, if you specifically do not want to associate any actionwith the key press. This is the default.

• Directory: Select to allow the caller to use the Dial By Namefeature, when this key is pressed. The Dial By Name featureallows a caller to search for a subscriber extension or mailboxnumber by “spelling” the person’s name using the telephonekeypad.

• Message: Select to allow a caller to leave a voice message,when this key is pressed and followed by the mailbox number.This feature is called Quick Message.

• Transfer: Select to allow the caller to transfer to the mailboxnumber you enter in the Mailbox field.This option is useful for transferring callers to particulardepartments. For example, “For technical support, press 2”.

Mailbox Enter the number of the mailbox to transfer to.

Auto Attendant Holidays field descriptionsYou can use the Site Configuration dialog box to configure the site-level properties. In theSite Configuration dialog box, click Properties to open the Properties dialog box and thenclick Auto Attendant Holidays.



Field DescriptionDate Enter the date on which an alternate greeting is to be played. The format is

DD/MM. You can specify up to 18 dates as holidays.

Prompt Enter the number of the holiday prompt as recorded in Visual Voice Editor.The range is 0 through 9999, and the default is 0. If 0 is selected, noholiday prompt is played.

Access Telephone Numbers field descriptionsUse this page to specify the Access Telephone numbers for each MAS. Access Telephonenumbers allows callers to dial inside an organization to reach a telephone extension directlywithout going through a receptionist. You can also use this page to specify the identificationnumber for the Modular Messaging hunt group and the port number for MSS alarm reporting.

Field DescriptionAccess numberfor MM huntgroup

Specifies the identification number of the Modular Messaginghunt group for messaging services.A hunt group is a pre-programmed collection of extensionsthat is configured on the switch. A single pilot number presentsa call to one of the available extension numbers within the huntgroup.

MSS Alarm portnumber

Specifies the port number to use as the alarm port on the MSS.

MAS#1 throughMAS#11

Specify the Access Telephone numbers for the MASs, asapplicable.

Other information for PBX integrationsThis topic provides general information about the Web Client server.

Port groups:

You can use the Other information page to create port groups for PC client applications, theTelephone User Interface (TUI), Call Me, outgoing Fax calls, Message Waiting Indicator (MWI),and QSIG Outbound Transfer. You can also specify which ports are members of each group

PBX integration


and configure each port group to be able to receive incoming calls to the MAS, send outgoingcalls, or both.

When creating port groups, follow these guidelines:

• One or more ports on the MAS must be configured in the PC Clients group. Theseports must be configured to allow outgoing calls.

• One or more ports on the MAS must be configured in the Telephone User Interfacegroup. These ports must be configured to allow incoming calls.

• The ports in the Call Me group must also be in the Telephone User Interface port group.

• The ports in the Fax group are used for outgoing faxes. These ports must beconfigured to allow outgoing calls.

Octel Analog Networking:

Octel Analog Networking (OAN) allows Modular Messaging for Exchange systems to send andreceive messages to and from subscribers on the following systems:

• Unified Messenger for Exchange

• Octel 250/350 that use OAN

• Octel 200/300 that use OAN

• Avaya Message Networking server with OAN

Note:OAN is not supported with Modular Messaging for Domino, Modular Messaging forExchange with H.323 switch integrations, and Modular Messaging for Exchange 2007systems. OAN is also not supported with Modular Messaging for MSS, the exception beingwhen using Message Networking.

Audio encoding format:

An MAS can play and record using the GSM, G.711 A-law, and G.711 μ-lawaudio encodingformats. The single format that you specify for the Audio encoding format field is the formatthat will be used to record voice messages, subscriber names, and greetings for the TUI andgraphical user interface (GUI) clients.

The G.711 encoding formats consume approximately five times as much storage space as theGSM format. However, the G.711 format provides better sound quality and is required forTeletypewriter (TTY) support.

Related topics:Other information field descriptions on page 66

Other information field descriptionsUse this page to specify additional information for PBX integrations such as the off site dialingaccess code, port groups details, Octel Analog Networking details, and audio encoding format.



Field DescriptionOffsite dialing accesscode

Specifies the number or the PBX access code that isused for off site dialing.

Port group 1 throughPort group 5

Select a check box for each port group that you want tocreate for this PBX switch integration.

Name Specifies the name of the port group.

Usage Specifies the usage of the port group that you want tocreate. For example, outgoing only or incoming only.

Number of ports Specify the number of the ports that you want to includein this group. For example, 2. The range is 1 through 999.

Use Octel AnalogNetworking

Select this check box if you want to specify the OctelAnalog Networking (OAN) details.

Numeric address forOAN node ID

Specifies the numeric address for the OAN node ID thatyou want to use.

Audio encoding format

Field DescriptionGSM Select this option to specify GSM as the audio encoding format.

Port group 1 is the default port group.

G.711 A-law Select this option to specify G.711 A-law as the audio encodingformat.

G.711 μ-law Select this option to specify G.711 μ-law as the audio encodingformat.

Related topics:Other information for PBX integrations on page 65

Mailbox information

System mailboxes field descriptionsFor a Modular Messaging for MSS configuration only, use this page to specify information aboutsystem mailboxes that you want to set up during installation. You can specify the mailboxnumber, password, and the user’s last name for system mailboxes such as postmaster, systembroadcast, system Enhanced-List application (ELA), and the fax system mailbox.

Mailbox information


The postmaster mailbox is used for administrative purposes and it is mandatory to specifydetails for this mailbox. It is also mandatory to have the last name for this mailbox aspostmaster.

Postmaster

Field DescriptionMailboxnumber

Specifies the number of the postmaster mailbox.This mailbox number is in the mailbox number range that youspecified on the Dial Plan page. You can change this to a numberof your choice, if necessary. However, the modified number mustalso be in the range specified on the Dial Plan page.

Password Specifies the password for the postmaster mailbox.The password can be up to 15 digits and must contain onlynumbers.

Last name Specify the last name of the user.For the postmaster mailbox, the default last name is postmasterand you cannot modify this value.

System ELA


Specifies the number of the system Enhanced List Application(ELA) mailbox.This mailbox number is in the mailbox number range that youspecified on the Dial Plan page. You can change this to a numberof your choice, if necessary. However, the modified number mustalso be in the range specified on the Dial Plan page.

Password Specifies the password for the system ELA mailbox.The password can be up to 15 digits and must contain onlynumbers.

Last name Specify the last name of the user for the system ELA mailbox.For the system ELA mailbox, the default last name is elashadow.You can modify this to a name of your choice.

System broadcast


Specifies the number of the system broadcast mailbox.This mailbox number is in the mailbox number range that youspecified on the Dial Plan page. You can change this to a number ofyour choice, if necessary. However, the modified number must alsobe in the range specified on the Dial Plan page.

Password Specifies the password for the system broadcast mailbox.The password can be up to 15 digits and must contain onlynumbers.



Field DescriptionLast name Specify the last name of the user for the system broadcast mailbox.

For the system broadcast mailbox, the default last name isbroadcast. You can modify this to a name of your choice.

Fax

Note:The Avaya (IP H.323) switch integration does not support fax service.

The extension number of the Fax mailbox should not be a valid phone extension, and shoulddivert directly to Modular Messaging. With the MM Fax mailbox, the incoming faxes areforwarded directly to subscriber extension, and outgoing calls are made by MASs using portsin the Outgoing Fax Calls group.


Specifies the number of the Fax mailbox.This mailbox number is in the mailbox number range that youspecified on the Dial Plan page. You can change this to a numberof your choice, if necessary. However, the modified number mustalso be in the range specified on the Dial Plan page.

Password Specifies the password for the Fax mailbox.The password must contain numbers only.

Last name Specify the last name of the user for the Fax mailbox.For the fax mailbox, the defaultlast name is fax. You can modifythis to a name of your choice.

TUI types and test subscribers field descriptionsUse this page to specify information about test subscribers for the Telephone User Interfaces(TUIs). It is mandatory to specify information about at least one TUI type.

TUI types to be used

Field DescriptionAria Select this check box to set up an Aria test subscriber during

installation.

AUDIX Select this check box to set up an AUDIX test subscriber duringinstallation.

Mailbox information


Field DescriptionSerenade Select this check box to set up a Serenade test subscriber during

installation.

Aria test subscriber

Field DescriptionExtensionnumber totest with DID

Specifies the DID number for the Aria test subscriber.This number should be in canonical form.

Mailboxnumber

Specifies the number of the Aria test subscriber mailbox.The DCT automatically displays a default mailbox number, whichis in the mailbox number range that you specified on the Dial Planpage. You can change this to a number of your choice. However,the modified number must also be in the range specified on the DialPlan page.

Password Specifies the password for the Aria test subscriber mailbox.The default password is 1234. You can change this to a number ofyour choice.

Last name Specifies the last name of the user for the Aria test subscribermailbox.The default last name is testaria. You can modify this value.Enter one of the following based on the Modular Messagingconfiguration that you selected on the Message Store page:

• For Modular Messaging for MSS, specify the logon namefor the Aria test subscriber.

• For Modular Messaging for Microsoft Exchange, specifythe last name for Aria test subscriber.

• For Modular Messaging for IBM Lotus Domino, specify theshort name or notes ID for Aria test subscriber.

Audix test subscriber


Specifies the DID number for the AUDIX test subscriber.This number should be in canonical form.

Mailboxnumber

Specifies the number of the AUDIX test subscriber mailbox.The DCT automatically displays a default mailbox number, whichis in the mailbox number range that you specified on the Dial Planpage. You can change this to a number of your choice, if necessary.However, the modified number must also be in the range specifiedon the Dial Plan page.

Password Specifies the password for the AUDIX test subscriber mailbox.



Field DescriptionThe default password is 1234. You can change this to a number ofyour choice.

Last name Specifies the last name of the user for the AUDIX test subscribermailbox.The default last name is testaudix. You can modify this value.Enter one of the following based on the Modular Messagingconfiguration that you selected on the Message Store page:

• For Modular Messaging for MSS, specify the logon namefor the AUDIX test subscriber.

• For Modular Messaging for Microsoft Exchange, specifythe last name for AUDIX test subscriber.

• For Modular Messaging for IBM Lotus Domino, specify theshort name or notes ID for AUDIX test subscriber.

Serenade test subscriber


Specifies the DID number for the Serenade test subscriber.This number should be in canonical form.

Mailboxnumber

Specifies the number of the Serenade test subscriber mailbox.The DCT automatically displays a default mailbox number, whichis in the mailbox number range that you specified on the Dial Planpage. You can change this to a number of your choice, if necessary.However, the modified number must also be in the range specifiedon the Dial Plan page.

Password Specifies the password for the Serenade test subscriber mailbox.The default password is 1234. You can change this to a number ofyour choice.

Last name Specifies the last name of the user for the Serenade test subscribermailbox.The default last name is testserenade. You can modify this value.Enter one of the following based on the Modular Messagingconfiguration that you selected on the Message Store page:

• For Modular Messaging for MSS, specify the logon namefor the Serenade test subscriber.

• For Modular Messaging for Microsoft Exchange, specifythe last name for Serenade test subscriber.

• For Modular Messaging for IBM Lotus Domino, specify theshort name or notes ID for Serenade test subscriber.

Mailbox information


Extended listsAn Extended List Application (ELA) is a system list that enables subscribers to delivermessages to a large number of recipients. Subscribers can address messages to these listsfrom the Telephone User Interface (TUI) and from a computer, or by calling the extensionassociated with an ELA list.

Broadcasting is a feature in which a message that is received into an appropriately configuredenhanced-list mailbox is sent to all local subscribers and to all list members. Administratorscan designate any ELA system list to be a local broadcast list. When a message is receivedinto an appropriately configured enhanced-list mailbox, the message is sent to all localsubscribers and to all list members.

For the Modular Messaging for MSS configuration, you can have system-wide or enterprise-wide broadcast lists. For example, administrators can create a broadcast list on each ModularMessaging system and then create a broadcast list on one of the Modular Messaging systemsthat has all the previous broadcast lists as its members.

Related topics:Extended lists field descriptions on page 72

Extended lists field descriptionsUse this page to provide information about the broadcast and ELA lists that you want to createon the MSS.

Field DescriptionBroadcast list Select this option to set up a broadcast list during installation.

List name Specifies the name of the broadcast list.

Mailbox number Specifies the number of the broadcast list mailbox.

Password Specifies the password for the broadcast list mailbox.

Field DescriptionELA list Select this option to set up an ELA list during installation.

List name Specifies the name of the ELA list.

Mailbox number Specifies the number of the ELA list mailbox.

Password Specifies the password for the ELA list mailbox.

Related topics:Extended lists on page 72



Classes of service field descriptionsUse this page to specify the classes of service that you want to install for your ModularMessaging system.

A class of service is a set of messaging capabilities that administrators define and assign tosubscribers with similar needs. For example, you might want to set up a class of service tohave the maximum mailbox size or to retain saved messages. The data that you enter in thispage is used for informational purposes only. No classes of services are added automaticallyduring the Modular Messaging configuration.

Field DescriptionClasses of service The classes of service that you want to install for your Modular

Messaging system.

Caller applications field descriptionsIf you want your Modular Messaging system to have any caller applications, then use this pageto specify the caller applications and a description about what the caller application should do.

This data is used for informational purposes only. No caller applications are addedautomatically during the Modular Messaging configuration.

Field DescriptionRequired callerapplications

Specifies the caller applications that you want to usefor your Modular Messaging system.

AAA configuration

AAA serverAn Authentication, Authorization, and Accounting (AAA) server is an optional, customer-provided server that can be used to authenticate the credentials of administrators logging into the MSS. The MSS can be configured to use one or two Remote Authentication Dial-In UserService (RADIUS), Lightweight Directory Access Protocol (LDAP), or Active Directory AAAservers to authenticate logins.

AAA configuration


Related topics:AAA configuration field descriptions on page 74

AAA configuration field descriptionsUse this page to specify information about the AAA server. This page is enabled only for theModular Messaging for MSS configuration.

Server type

Field DescriptionRADIUS Select this option to configure a RADIUS AAA server. If this

option is selected, the LDAP/AD section of this page isdisabled.

LDAP (POSIX) Select this option to configure a LDAP (POSIX) AAA serverthat complies with RFC 2307. If this option is selected, theRADIUS section of this page is disabled.

AD (SFU) Select this option to configure a Active Directory (AD) AAAserver running Services for UNIX (SFU). If this option isselected, the RADIUS section of this page is disabled.

AD (IDMU) Select this option to configure a AD AAA server runningIdentity Management for UNIX (IDMU). If this option isselected, the RADIUS section of this page is disabled.

None (LocalAuthentication)

Select this option if you do not want to configure a AAAserver. If this option is selected, the RADIUS and LDAP/AD sections of this page are disabled.

RADIUSFor each RADIUS AAA server you want to configure, select a check box and enter the Servername, IP address, Port, and Shared secret for that server.

Field DescriptionServername

Specifies the name of the RADIUS AAA server.Avaya recommends that computer names be shorter than 10characters for ease of data entry.The fully qualified domain name (computer plus domain name) canbe from 1 to 64 characters, including lower case alpha characters,numeric characters, and the hyphen (-). The first character cannotbe a number.

IP address Specifies the IP address of the RADIUS AAA server.

Port Specifies the port to be used for communication with the RADIUSAAA server. If this field is left blank, port 1812 will be used.

Sharedsecret

Specifies the shared secret for encryption of the login credentialsthat will be passed to the AAA server for authentication. The shared



Field Descriptionsecret you enter for this field must match the shared secret specifiedon the AAA server.

LDAP / ADFor each LDAP or Active Directory AAA server you want to configure, select a check box andenter the Server name, IP address, and Port for that server.

Field DescriptionServer name Specifies the name of the LDAP or Active Directory AAA server.

For an LDAP server, if the Use TLS/SSL check box is selected,the server name you enter must match the server name on theTLS/SSL security certificate.Avaya recommends that computer names be shorter than 10characters for ease of data entry.The fully qualified domain name (computer plus domain name)can be from 1 to 64 characters, including lower case alphacharacters, numeric characters, and the hyphen (-). The firstcharacter cannot be a number.

IP address Specifies the IP address of the LDAP or Active Directory AAAserver.

Port Specifies the port to be used for communication with the LDAPor Active Directory AAA server. If this field is left blank, port 389will be used.

Base DN Specifies the LDAP base Distinguished Name (DN).

Use TLS/SSL Select this check box to use Transport Layer Security (TLS) orSecure Sockets Layer (SSL) to encrypt the information sent toand from an LDAP Server.

Connectanonymously

Select this check box to enable the client to attempt to connectanonymously to the LDAP server. If you select this check box,the Bind DN and Password fields are disabled.

Bind DN Specifies a Bind DN (also called a User DN). This field isavailable only if the Connect anonymously check box is notselected. To use this feature, you must specify a Bind DN and apassword. Examples of Bind DNs are"uid=joeuser,ou=People,dc=com" for LDAP and "domain\Administrator" for Active Directory types. The Bind DN andpassword you enter in these fields must match exactly the BindDN and password configured on the AAA server.

Password Specifies the password for the Bind DN (also called a User DN).This field is available only if the Connect anonymously checkbox is not selected. To use this feature, you must specify a BindDN and a password. The Bind DN and password you enter inthese fields must match exactly the Bind DN and passwordconfigured on the AAA server.

AAA configuration


Related topics:AAA server on page 73

Support and maintenance

Product information field descriptionsUse this page to specify the unique product identification number for each MAS and for theMSS. This page is also used to specify the Windows product key for each MAS and the serialnumber of the MSS.

The DCT enables the MAS fields on this page according to the value entered in the Numberof MASs in the VMD field on the Voice Mail Domain page.

MAS

Field DescriptionProduct IDnumber

For each MAS, specifies the unique 10-digit number used toidentify each Messaging Application Server. It is assigned atsystem installation. This field may be left blank.

Windowsproduct key

Specifies the product key for the copy of Windows that is installedon the MAS.The product key can be as many as 25 alphanumeric charactersin groups of 5. Each 5 character group is separated with a hyphen(-).

MSSThe DCT disables this section for Modular Messaging with Microsoft Exchange and ModularMessaging with IBM Lotus Domino configurations.

Field DescriptionProduct IDnumber

Specifies the unique 10-digit number used to identify the MessageStorage Server (MSS). It is assigned at system installation.

Serial number Specifies the serial number of the MSS unit.The serial number contains 14 alphanumeric characters. You canfind the serial number on the back of your MSS unit correspondingto a label marked “Avaya S/N”.

Remote Access IP addresses field descriptionsThe Avaya Modular Messaging Configuration Wizard automatically sets up inbound remoteaccess to each MAS modem. Use this page to specify the RAS IP addresses, that the technical



support organization requires, for each MAS in the system. Also, include any supplementaryserver that is part of the VMD. If you do not specify valid IP addresses, Avaya technical supportwill not be able to access the system remotely.

The DCT enables the MAS fields on this page according to the value entered in the Numberof MASs in the VMD field on the Voice Mail Domain page.

MAS

Field DescriptionStarting IPAddress

For each MAS, specify the starting IP address that the technicalsupport organization uses, to connect to the MAS.If Avaya is supporting this system, you must enter the RAS IPaddresses that the Avaya Automatic Registration Tool (ART)provides.

Ending IPaddress

For each MAS, specify the ending IP address that the technicalsupport organization uses, to connect to the MAS.If Avaya is supporting this system, you must enter the RAS IPaddresses that the Avaya Automatic Registration Tool (ART)provides.

Alarming informationThe MAS and the MSS generate logs and notifications related to system errors and alarms.You can configure the serviceability (alarming) settings for the Modular Messaging system sothat alarm notifications are sent to a service organization using any of the following methods:

• A dial-up modem to the Avaya Initialization and Administration System (INADS)

• Simple Network Management Protocol (SNMP) traps

• Both INADS and SNMP traps

Modular Messaging can also use SNMP to send alarm notifications to a customer NetworkManagement Station (NMS).

For SNMP alarm notification, the NMS can be configured not to send an acknowledgementwhen it receives traps, or to use one of the following methods to acknowledge received traps:

• Return trap — This acknowledgement method is better and more reliable than theping surround method. However, it is also more complicated to set up and requiresthat you configure your NMS to generate return traps. When an alarm trap is receivedby your NMS, it sends a trap of its own, back to the MAS, acknowledging that it hasreceived the alarm notification.

• Ping surround — This acknowledgement method is easier to implement but inherentlyless informative than return traps and it makes certain assumptions. When an alarmtrap is ready to be sent to the NMS, a ping command is first generated to the NMS.Only if the MAS receives a ping response, does it send the trap. Then it sends anotherping request. If it receives another ping response from the NMS, the assumption isthat the trap was received on the NMS. If the initial ping response is not received from



the NMS, then the MAS waits 5 minutes before trying again. It keeps trying at 5-minute intervals, until it receives a response from the NMS. If after 16 tries there isstill no response from the NMS, then the MAS stops trying and raises a warning alarmagainst the alarming system. If the first ping is successful and the trap is sent, but thesecond ping is not successful, then the assumption is that the trap was not sentsuccessfully. In this case, the trap is rescheduled to be sent at 5-minute intervals until itis successfully sent. If after 16 tries there is still no response from the NMS, then theMAS stops trying and raises a warning alarm against the alarming system.

Related topics:Alarming information field descriptions on page 78

Alarming information field descriptionsUse this page to specify alarming information and settings that will be applied to the MSS andMAS in the VMD. This page is optional. If you want to specify alarming information later duringthe Modular Messaging configuration, do not make any changes to this page.

Alarming notification to configure

Field DescriptionINADS Select this option if you want to configure INADS alarming.

The MASs must have modems if you want to use INADS alarming. Ifyou select this option, the SNMP section on this page is disabled.

SNMP Select this option if you want to configure SNMP alarming.If you want SNMP alarming for your Modular Messaging system,ensure that the Network Management Station (NMS) is installed, setup, and tested prior to technicians arriving on site for the ModularMessaging installation or upgrade. If you select this option, the INADSsection on this page is disabled.

INADSandSNMP

Select this option if you want to configure both INADS and SNMPalarming.

None This is the default option. Leave this option selected if you do not wantto use alarming for your Modular Messaging system, or if you chooseto specify alarming information during the Modular Messagingconfiguration. If you select this option, the INADS and SNMP sectionson this page are disabled.

INADS

Field DescriptionSerial (COM)modem

Select this option if you want to use a modem connected to aSerial (COM) port on the Modular Messaging system.



Field DescriptionUSB modem Select this option if you want to use a modem connected to a

USB port on the Modular Messaging system.

Modem type Select one of the following modems for INADS alarming:• MT5634ZBA• USR 5686D• ASG GUARD• NIU• DSB-650• Other

Note:Select the DSB-650 modem type only if you want to use aUSB modem.

Port number Specifies the port number that you want the modem to use.

Complete alarmdestinationtelephonenumber

Specifies the INADS alarm destination telephone number.Include any prefix digits, for example 1 or 9, that have to bedialed to make alarm notification calls.You can also use the following characters:

• W to instruct the system to wait for a dial tone• , to create a pause• * or # for signal trunk or feature access codes

Modeminitializationstring

Specifies the modem initialization (setup) string required for themodem to make the alarm notification calls.If you do not know what this is, consult your modemdocumentation or contact your technical service representative.

SNMP

Field DescriptionNMS full name Specifies the fully qualified domain name of the NMS to

which you want to send alarm notification traps.

NMS IP address Specifies the IP address of the NMS to which you wantto send alarm notification traps.

Context community Specifies the name of the context or community to whichthe NMS belongs.For more information about how to configure this field,see the documentation for your SNMP NMS.



Field DescriptionAcknowledgementtype

Select one of the following methods to acknowledgeSNMP traps received by the NMS:

• Return trap• Ping surround• None - This is the default acknowledgement

type. Leave this option selected to disableacknowledgement for SNMP alarming.

Alarming notification to use

Field DescriptionINADS Select this option if you want your Modular Messaging system to use

INADS alarming.

SNMP Select this option if you want your Modular Messaging system to useSNMP alarming.

None Select this option to disable alarm notification.

Related topics:Alarming information on page 77

Password guidelinesUse the following guidelines for creating passwords:

• Use at least 6 alphanumeric and punctuation characters

• Do not use space characters or non-printable characters

• Never use obvious passwords, such as a telephone extension, room number,employee identification number, social security number, or easily guessed numeric orletter combinations (for example, denver or avaya)

• Do not post, share, print, or write down passwords

Related topics:MSS login and PPP information field descriptions on page 80MSS passwords field descriptions on page 38

MSS login and PPP information field descriptionsUse this page to specify the passwords for all the required MSS login. If the login requires apoint-to-point (PPP) remote access connection to the MSS modem, then also specify therequired IP addresses.



Passwords for local access to the MSSThe login and passwords in the top section are for local access to the MSS either from a consoleor from another computer on the customer's LAN.

Field Descriptionsa Specifies the password for the sa login account.

The sa login provides access to most of the Modular Messaging systemWeb-based administration pages.

vm Specifies the password for the vm login account.The vm login provides access to a limited set of administration pages.

Passwords for remote access to the MSSThe login and password in the bottom section are for a point-to-point (PPP) remote accessconnection to the MSS modem.

Field Descriptionsappp Specify the local IP address, remote IP address, and password for the

sappp login account.The sappp login is for use by a customer's system administratorperforming system administration and maintenance from a remotelocation using a dial up connection. The customer must set up the sappppassword to allow the remote administrator to dial in to the system.The local IP address is a customer-provided IP address for PPP accessthrough the MSS modem.The remote IP address is for the remote device that is to connect to thisMSS.This is an optional information and this will be provided either by thecustomer or the remote support organization.

craftppp Specify the local IP address and remote IP address for the craftppp loginaccount.The local IP address is a customer-provided IP address for PPP accessthrough the MSS modem.The remote IP address is for the remote device that is to connect to thisMSS. This information will be provided either by the customer or theremote support organization.

Related topics:Password guidelines on page 80



Clients

Client applications field descriptionsUse this page to provide information about the client applications that you want to install forthis Modular Messaging system. For a Modular Messaging for MSS configuration, you can alsoselect the standard client protocols that you want to use.

Location of installersFor each client application that you want to install, specify the path to the installation program.

Field DescriptionIBM Lotus Notesclient

Specify the path to the installation program or click the buttonadjacent to the location field to browse to the folder that containsthe installation program.

IBM DUC Specify the path to the installation program or click the buttonadjacent to the location field to browse to the folder that containsthe installation program.

MicrosoftOutlook client

Specify the path to the installation program or click the buttonadjacent to the location field to browse to the folder that containsthe installation program.

Standard clientsFor a Modular Messaging for MSS configuration, specify the standard client protocols that youwant to use.

Field DescriptionIMAP Select this check box if you want to use IMAP protocol for communication

with remote clients. If you select this check box, the IMAP protocol isenabled for the Modular Messaging configuration and uses the defaultport number, which is 143. However, you can change this to any otheravailable port using Modular Messaging Web administration.

IMAPSSL

Select this check box if you want to use IMAP4 server for IMAP4 SSLcommunication with remote clients. If you select this check box, theIMAP4 SSL protocol is enabled for the Modular Messaging configurationand uses the default port number, which is 993. However, you canchange this to any other available port using Modular Messaging Webadministration.

POP3 Select this check box if you want to allow the use of POP3 clients foremail messaging. If you select this check box, the POP3 protocol isenabled for the Modular Messaging configuration and uses the default



Field Descriptionport number, which is 110. However, you can change this to any otheravailable port using Modular Messaging Web administration.

POP3SSL

Select this check box if you want to enable POP3 server for POP3 SSLcommunication with remote clients. If you select this check box, thePOP3 SSL protocol is enabled for the Modular Messaging configurationand uses the default port number, which is 995. However, you canchange this to any other available port using Modular Messaging Webadministration.

SMTPSSL

Select this check box if you want to enable SMTP server for SMTP SSLcommunication with remote clients. If you select this check box, theSMTP SSL protocol is enabled for the Modular Messaging configurationand uses the default port number, which is 465. However, you canchange this to any other available port using Modular Messaging Webadministration.

Notes

Notes field descriptionsUse this page to provide additional information about the Modular Messaging system that youare installing or upgrading.

Field DescriptionAdditionalinformation

Use this field to provide additional information about theModular Messaging system that you are installing orupgrading.

Notes


Index

A

AAA configuration field descriptions ...........................74AAA server .................................................................73Access Telephone numbers field descriptions ...........65Additional optional MSS trusted servers field

descriptions ...................................................45Alarming information ..................................................77Alarming information field descriptions .......................78Aliases and ART nicknames field descriptions ...........34Auto Attendant ............................................................63Auto Attendant Holidays .............................................65Auto Attendant Keys ...................................................64

C

Caller applications field descriptions ..........................73Canonical number ......................................................55Classes of service field descriptions ..........................73Client applications field descriptions ..........................82Configuring Modular Messaging services ..................48Corporate MM server networking details ....................29Corporate MM server networking details field

descriptions ...................................................33Corporate network details field descriptions ...............29COS ............................................................................73Customer details field descriptions .............................24

D

Data Collection ToolPage and Field status indicators ..........................21Upgrade ...............................................................12what is it? ...............................................................5

DCT ..............................................................................5DCT file

Adding an MAS ....................................................14Backing up ...........................................................19Creating ................................................................11Obtaining a current version ....................................9Update .................................................................16Uses .......................................................................7

Dial plan field descriptions ..........................................58Domino message store field descriptions ...................37

E

Exchange message store field descriptions ...............35

Extended lists .............................................................72Extended lists field descriptions .................................72Extensions and switch ports field descriptions ...........58

F

Field status indicators .................................................21

L

Language packs .........................................................52Language packs field descriptions .............................53Logon accounts and passwords .................................40Logon accounts and passwords field descriptions .....41

M

MAS accounts and passwords field descriptions .......40MAS servers ...............................................................46MAS service account field descriptions ......................42Media setup ................................................................61Message networking field descriptions .......................54Message store field descriptions ................................26Messaging Application Server ....................................46MM service selection field descriptions ......................48Modular Messaging configurations .............................25Modular Messaging services ......................................46MSS login and PPP information field descriptions .....81MSS passwords field descriptions ..............................38

N

Notes field descriptions ..............................................83

O

Offline access field descriptions .................................53Optional MSS trusted servers field descriptions .........43Other information ........................................................65Other information field descriptions ............................67

P

Page status indicators ................................................21Password guidelines ..................................................80PBX ............................................................................54PBX integrations .........................................................65


Private network field descriptions ...............................35Product information field descriptions ........................76

R

Regional settings field descriptions ............................25Regular expressions ...................................................55Remote Access IP addresses field descriptions ........77

S

Select the DCT configuration to use field descriptions ...23

Site Configuration .......................................................60Switch integration information field descriptions ........55Switch integration method field descriptions ..............54Switch-native number .................................................55System mailboxes field descriptions ..........................68

T

Telephone Properties .................................................61

Telephone User Interface ...........................................69Text to speech ............................................................46Tracing field descriptions ............................................49Translation Rules ........................................................55Trusted servers ...........................................................43TTS and announcements field descriptions ...............46TUI types and test subscribers field descriptions .......69

V

VMD ...........................................................................27Voice Mail Domain ......................................................27Voice Mail Domain field descriptions ..........................27

W

Web Client server .......................................................51Web Client server field descriptions ...........................52Web Subscriber Options field descriptions .................50Web Subscriber Options server .................................50Windows domain field descriptions ............................32WSO ...........................................................................50

Index


data collection tool...2. on the select the dct configuration to use page, do one of the following:...

Documents