Lucent Technologies 585-310-575 manual For the administrative ELA trusted server elaadmin, enter 0

Page 40

Administering AUDIX for ELA

3.In the Trusted-Server Name: field, enter a name for the first ELA trusted server. (See the Note below for tips on trusted server names.)

This name must be a unique 1- to 10-printable character entry. Additionally, this name cannot start with a number and cannot contain any embedded spaces, for example, denver 1 is not allowed, but denver_1 is allowed. (Use the li tr and li ma commands to view existing names and ensure that you are not using a name that is already assigned.)

NOTE:

You must administer two ELA trusted servers. The installation worksheets should have the ELA trusted server names. If not, we recommend that you use names that are descriptive enough that you can tell them apart, for example, enter the first ELA trusted server name as ela_admin and, when you add the second ELA trusted server, use ela_deliv.

4.Enter a 5- to 10-alphanumeric password that the trusted server must use to log on to the AUDIX server. As you type, your keystrokes display, but will appear as a series of asterisks (*) after you save.

5.Enter the TCP/IP address of this Lucent INTUITY in the form w.x.y.z, where each letter is a number, 0 to 255. (See page 3-23for information how to determine your system’s IP address.)

6.Enter Enhanced-List Application in the Service Name: field. Type exactly as listed, including the hyphen and capitalization.

Every ELA server will have the same service name. (For example, if you have two ELA servers, they will have separate trusted server names, but the same service name.)

7.Enter n in the Cross-Domain Delivery? field.

8.For the administrative ELA trusted server (ela_admin), enter 0 in the

Minutes of Inactivity Before Alarm: field.

For the delivery ELA trusted server (ela_deliv), enter 255 in the Minutes of Inactivity Before Alarm: field

9.Press (F3) ENTER to save the information in the system database.

The cursor returns to the command line, and the system displays the message Command Successfully Completed.

10.You must now add the delivery ELA server. Return to step 2, and repeat this procedure, ensuring that you use a unique name for the delivery trusted server, that is, do not use the name of the ELA trusted server you just added.

30Issue 1 July 1997

Image 40

Contents Intuity Messaging Solutions Trademarks Contents Preventative Maintenance and Troubleshooting INIndex Iv Issue 1 July Purpose About This BookIntended Audiences Trademarks and Service Marks Page How to Comment on This Book Related ResourcesEnhanced-List Application OverviewAudience What You Should KnowEnhanced-List Application What ELA Can Do for YouPlanning with Professional Services ELA AdministrationBasic Concepts Things to Consider ELA Message DeliveryLAN Impact Hardware/Software RequirementsRemote Message Impact Security Port Usage ImpactExternal Security Internal Security Imapi Session Requirements Shadow MailboxInstallation Installing the SoftwareSoftware Install Menu Rebooting the System Wait Time WindowMake sure that there is no diskette in the diskette drive Administering Audix for ELA Verifying that ELA is Enabled Activating ELAIncreasing the Number of Mailing Lists Allowed on the System Defining an ELA Class of Service Ch cos COSnumberFax? If you have purchased fax Enter the following information Setting Up ELA and Shadow Mailbox Community IDs Example of Communities Administered for use with ELABefore You Begin ELA Community IDSending Restrictions Screen Shadow Mailbox Community ID Administering TCP/IP Administering Audix for ELA Denver1 Setting Up Imapi Sessions for Trusted Server Access Setting Up Imapi Sessions for Trusted Server Access Defining Two ELA Trusted Servers Security AlertDrmid10 For the administrative ELA trusted server elaadmin, enter 0 Page Administering Audix for ELA Issue 1 July Administering ELA for AUDIX4 Defining the Audix server Administering AccessSet Up Enhanced-List System Data Window On next Administering ELA for Audix Guidelines for Naming Enhanced Lists Mailbox AttributesCreating Enhanced Lists Administer Enhanced-Lists Window On next Guidelines for Selecting Enhanced-List Members Adding Members to Enhanced ListsEnhanced List Membership for Listname Window Adding/Deleting Members to an Enhanced List Enhanced-List Membership for Listname listextension Window Adding a Member Finding a MemberDeleting a Member Deleting an Enhanced ListPrinting an Enhanced List Confirm Deletion of Enhanced-List Window Testing Intuity Enhanced Lists Recording Names for Enhanced ListsPage Administering ELA for Audix Issue 1 July Preventative Maintenance Troubleshooting Checking the Administrator’s LogChecking the Delivery Failure Log Delivery Failure Log WindowOccurred, such as Full Mailbox, Unsupported Media, or Delivery Failure Codes Delivery Failure Codes Reason of Failure DescriptionTroubleshooting ELA Messaging Solutions Release 4 Alarm Log Messages Lucent Intuity Messaging Solutions Digital Preventative Maintenance and Troubleshooting Issue 1 July Alarm Code Event ID ELA-delivts01 AlarmsDelivts Resource Type Alarm Code Event ID ELA-delivts03 Alarm Code Event ID ELA-delivts02Alarm Code Event ID ELA-delivts04 Alarm Code Event ID ELA-registry02 Alarm Code Event ID ELA-registry01Registry Resource Type Alarm Code Event ID ELA-shadow02 Alarm Code Event ID ELA-shadow01Shadow Resource Type Alarm Code Event ID ELA-shadow04 Alarm Code Event ID ELA-shadow03Alarm Code Event ID ELA-shadow05 Alarm Code Event ID ELA-shadow06 EL Enhanced-List Application Event ID ELA-badreca01 through ELA-badreca12Event ID ELA-nomembers Event ID ELA-lostlock01 through ELA-lostlock10Event ID ELA-nestvioltn Event ID ELA-mboxlock01 Event ID ELA-loopvioltnEvent ID ELA-chkrestrct Event ID ELA-shadow07 Event ID ELA-delivts05Index Index