Lucent Technologies 585-310-575 - Manuals

Issue 1 July 1997 v About This Book Purpose This book contains instructions for installing and administrating the Enhanced-List Application (ELA) on an I NTUITY ™ AUDIX ® R4 system. Intended Audiences This book is intended primarily for the on-site technical personnel who are responsible for install...

About This Book vi Issue 1 July 1997 Trademarks and Service Marks The following trademarked products are mentioned in books in the Lucent I NTUITY document set: ■ AT™ is a trademark of Hayes Microcomputer Products, Inc. ■ AUDIX ® is a registered trademark of Lucent Technologies™. ■ cc:Mail ® is a re...

Trademarks and Service Marks Issue 1 July 1997 vii ■ Novell ® is a registered trademark of Novell, Inc. ■ Paradyne ® is a registered trademark of Lucent Technologies™. ■ Phillips ® is a registered trademark of Phillips Screw Company. ■ Rolm ® is a registered trademark of International Business Machi...

About This Book viii Issue 1 July 1997 Related Resources If you need help with basic administrative procedures, see the I NTUITY ™ Messaging Solutions Release 4 Administration book, 585-310-564. How to Comment on This Book We are always interested in your suggestions for improving this book. Please ...

Issue 1 July 1997 1 1 Enhanced-List Application Overview This chapter describes the Enhanced-List Application (ELA) on an I NTUITY ™ AUDIX ® Release 4 system. Audience Read this book if you are the AUDIX system administrator responsible for the configuration and maintenance of an I NTUITY AUDIX Rele...

Enhanced-List Application 2 Issue 1 July 1997 Enhanced-List Application The Enhanced-List Application (ELA) greatly expands your business’ capability to deliver messages to large numbers of recipients. A single enhanced list can contain 1500 addresses and you – the system administrator – can create ...

ELA Administration Issue 1 July 1997 3 ■ Forward messages to support staff automatically. If you often forward incoming messages, you can create an enhanced-list mailbox that automatically forwards messages to your staff. Your staff can review the messages and then respond to them as they normally w...

ELA Administration Issue 1 July 1997 5 Hardware/Software Requirements ELA runs on the same machine as AUDIX. ■ ELA must be installed on a Lucent I NTUITY R4.2-4 or higher machine. If your site has an earlier release, contact your Lucent service representative to obtain the necessary upgrade. ELA is ...

Enhanced-List Application 6 Issue 1 July 1997 Port Usage Impact Voice port usage increases as recipients retrieve messages sent by ELA. Plan for the increase with Professional Services when you purchase ELA. Refer to the worksheets that were compiled at the time of the purchase to determine the port...

ELA Administration Issue 1 July 1997 7 The IMAPI password is an optional, secondary level of security used to prevent an unauthorized source external to AUDIX from starting an IMAPI session. We strongly recommend that you take advantage of this extra protection. If you choose to administer an IMAPI ...

Enhanced-List Application 8 Issue 1 July 1997 cannot be infected with viruses embedded in these software files, client machines may become infected when a user launches the application associated with the software file. ! CAUTION: ELA does not perform any virus detection. Your company should evaluat...

Issue 1 July 1997 9 2 Installation Overview This chapter describes how to install ELA on a Lucent I NTUITY R4.2 or higher system. Installing the Software The ELA package is provided on a tape labeled Enhanced-List Application . To install ELA on a Lucent I NTUITY R4.2 or higher system: 1. Log in to ...

Rebooting the System Issue 1 July 1997 11 6. Press to select all . The system installs the software and displays several status messages. When the software installation is complete, the system displays the message: Installation of Enhanced List Application Package was successful. Insert a tape into ...

Issue 1 July 1997 13 3 Administering AUDIX for ELA Overview To define the ELA server and functionality to AUDIX: ■ Contact Professional Services (or your account representative, if you did not contract with Professional Services) to have ELA installed. ■ Contact Professional Services (or your accoun...

Administering AUDIX for ELA 14 Issue 1 July 1997 Activating ELA After the ELA installation is complete, contact your Professional Services (or your account representative, if you did not contract with Professional Services). The technician from the remote support center will access your system remot...

Increasing the Number of Mailing Lists Allowed on the System Issue 1 July 1997 15 3. Ensure the following fields are set to ON: ■ Enhanced List Application ■ TCP/IP Administration 4. If either of these fields is OFF, and you purchased/installed ELA, call the support center to request that the featur...

Administering AUDIX for ELA 16 Issue 1 July 1997 6. Press (F3) to save the information in the system database. The cursor returns to the command line, and the system displays the message Command Successfully Completed . 7. Continue with the next procedure or enter exit to leave AUDIX Administration....

Defining an ELA Class of Service Issue 1 July 1997 17 Figure 3-2. Class of Service Screen, Page 1; Defining a Class of Service for ELA 3. Although not required, we recommend that you change the name of the COS to be more descriptive, for example, enter ELA in the Name: field. NOTE: You should write ...

Administering AUDIX for ELA 18 Issue 1 July 1997 Figure 3-3. Subscriber Class of Service Parameters Screen, Page 2; Enabling ELA on a COS Basis 7. Enter the following information: ■ 14 in the Retention Times (days), New: field. (This setting acts as a safety measure, should ELA encounter an operatio...

Setting Up ELA and Shadow Mailbox Community IDs Issue 1 July 1997 19 8. Press (F3) to save the information in the system database. The cursor returns to the command line, and the system displays the message Command Successfully Completed . 9. Continue with the next procedure or enter exit to leave A...

Administering AUDIX for ELA 20 Issue 1 July 1997 Let’s say you set up the enhanced-list mailbox community to be Community 10. Community 10 is given permission to send to all other communities (except the shadow mailbox community). Then, you set up a special user community, Community 9, and administe...

Setting Up ELA and Shadow Mailbox Community IDs Issue 1 July 1997 21 2. At the enter command: prompt, enter either: The system displays the Sending Restrictions screen (Figure 3-5). Figure 3-5. Sending Restrictions Screen 3. Enter y in the Activate Restrictions? field. 4. Leave all fields blank (hor...

Administering AUDIX for ELA 22 Issue 1 July 1997 access to enhanced lists from sending a message to an Enhanced List. Following the example discussed under "Things to Consider" on page 3-19, there would be an r in the field corresponding to the intersection between Sender Community 1 (the de...

Administering TCP/IP Issue 1 July 1997 23 Administering TCP/IP If your system is already connected to the LAN, you can skip this procedure. However, you need to know the IP Address to administer the trusted server, so — even if your system is already networked — perform step 1 of this procedure and ...

Administering TCP/IP Issue 1 July 1997 25 5. Enter the default gateway IP address in the Default Gateway IP Address: field. The default gateway IP address is the address of the gateway router that serves to connect to addresses on other LANs. This field is left blank if the Lucent I NTUITY system wi...

Setting Up IMAPI Sessions for Trusted Server Access Issue 1 July 1997 27 Figure 3-8. System-Parameters IMAPI-Options Screen, Page 1; Setting IMAPI Sessions for Trusted Server Access NOTE: The following contain instructions for the fields that directly relate to ELA. See your I NTUITY Messaging Solut...

Administering AUDIX for ELA 28 Issue 1 July 1997 8. Press (F3) to save this information to the system database. The cursor returns to the command line, and the system displays the message Command Successfully Completed . 9. Continue with the next procedure or enter exit to leave AUDIX Administration...

Defining Two ELA Trusted Servers Issue 1 July 1997 29 ■ The TCP/IP address for the AUDIX server (see page 3-23). You will perform this procedure twice, first for the ELA administrative server, and then for the ELA delivery server. To add the ELA trusted servers to the I NTUITY AUDIX server: 1. Start...

Administering AUDIX for ELA 30 Issue 1 July 1997 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 num...

Defining Two ELA Trusted Servers Issue 1 July 1997 31 11. Do you want to administer an IMAPI password? ■ If yes, follow the procedures for setting the IMAPI password in your I NTUITY Messaging Solutions Release 4 Administration book before proceeding to the next section. ■ If no, go to Chapter 4 to ...

Issue 1 July 1997 33 4 Administering ELA for AUDIX Overview Now that the AUDIX system knows about the ELA trusted servers, you can do the initial administration of the ELA system. To make ELA fully functional, you must: ■ Define the AUDIX server to ELA and administer access ■ Create enhanced lists ■...

Administering ELA for AUDIX 34 Issue 1 July 1997 ■ Enhanced-list mailbox and shadow mailbox Community IDs (see page 3-20) ■ ELA Class of Service (see page 3-16) To administer the ELA server: 1. Starting from the main menu (Figure 3-1 on page 3-14), select: The Set Up Enhanced-List System Data window...

Defining the AUDIX server and Administering Access Issue 1 July 1997 35 Table 4-1. Field Definitions: Set Up Enhanced-List System Data Window Field Name Description/Procedure System Login: Valid Input: sa, vm Enter sa (system administrator login) or vm (voice mail administrator login). NOTE: Adminis...

Administering ELA for AUDIX 36 Issue 1 July 1997 Password: Valid Input: 5- to 10-alphanumeric characters Enter the Administrative trusted server password (see page 3-30). Delivery Trusted-Server Name: Valid Input: 1- to 10-alphanumeric characters Enter the name of the delivery trusted server that yo...

Guidelines for Naming Enhanced Lists Issue 1 July 1997 37 3. Press (F3) to save the ELA server information to the system database. The system displays the message “ Successfully Updated! ” and asks you to press F1 acknowledge the message. 4. Press (F1) . The system redisplays the Enhanced List Manag...

Administering ELA for AUDIX 38 Issue 1 July 1997 ■ Give enhanced lists names that reflect an organization or a function. Include the word list . Examples: — Marketing_Dept_List — Maxfield_List — Western_District_Salesforce_List ■ If you want all enhanced lists to be grouped together, put the word li...

Creating Enhanced Lists Issue 1 July 1997 39 Figure 4-2. Administer Enhanced-Lists Window 2. Press (F4) . The system displays the New Enhanced-List window (Figure 4-3). Figure 4-3. New Enhanced-List Window 3. Complete the fields in this window using the information in Table 4-2. NEW E-LIST

Administering ELA for AUDIX 40 Issue 1 July 1997 4. Press (F3) to save this information in the system database. The cursor displays in the Administer Enhanced Lists window on the line that shows the list you just entered. (If you have more than one list, the new list is placed in line alphabetically...

Administering ELA for AUDIX 42 Issue 1 July 1997 Figure 4-4. Enhanced List Membership for Listname Window 2. Press (F4) . The system displays the Add Member data entry window (Figure 4-5). Figure 4-5. Add Member Window; Adding Members to an Enhanced List 3. Enter one of the following: ■ The user’s n...

Creating Enhanced Lists Issue 1 July 1997 43 4. Press (F3) to save this information in the system database. NOTE: The Entries: field at the top of the Administer Enhanced-Lists window increments each time you add a new member to the list. 5. Repeat Step 3 and Step 4 to continue adding member names, ...

Creating Enhanced Lists Issue 1 July 1997 45 ■ Delete a member from the list (Step 6) ■ Print the list to your system printer (Step 7) Adding a Member 4. Press (F4) . The system displays the Add Member data entry window (Figure 4-5 on page 4-42). a. Enter one of the following: ■ The user’s name as i...

Administering ELA for AUDIX 46 Issue 1 July 1997 Deleting a Member 6. To delete a member: a. Locate the member name to be deleted. See ‘‘Finding a Member’’ above. b. Press (F7) . The system displays the confirmation message: CONFIRM: Deleting Name= List - Listname Extension/Address= Listextension En...

Deleting an Enhanced List Issue 1 July 1997 47 2. Use the arrow keys to highlight the line that represents the list you want to delete. If the list to be deleted does not appear on the visible page, select the list by one of the following means. ■ Press until the desired list displays. Use the arrow...

Administering ELA for AUDIX 48 Issue 1 July 1997 Recording Names for Enhanced Lists Once you have established an enhanced list, is a good idea to record a name for the list. That way, users will hear a meaningful name for the list when they send a message to an enhance- list mailbox for distribution...

Issue 1 July 1997 51 5 Preventative Maintenance and Troubleshooting Overview This section describes how to check for system alarms relating to ELA and how to diagnose common application and end-user problems. Checking the Administrator’s Log The system warns you of potential administrative problems ...

Preventative Maintenance and Troubleshooting 52 Issue 1 July 1997 5. Press (F3) to display the alarm entries . 6. Examine the displayed entries. See the Lucent I NTUITY ™ Messaging Solutions Release 4 Alarm and Log Messages, 585-310-566 for a list of events and alarms, and associated repair procedur...

Checking the Delivery Failure Log Issue 1 July 1997 53 2. Press (F8) to send a copy of this report to the system printer, if you have a printer available. 3. Press (F6) repeatedly to return to the main menu. Table 5-1. Field Definitions: Enhanced-List Delivery Failure Log Window Field Name Descripti...

Preventative Maintenance and Troubleshooting 54 Issue 1 July 1997 Delivery Failure Codes Delivery failure logs contain the following codes: Table 5-2. Delivery Failure Codes Reason of Failure Description Full mailbox The recipient has a full mailbox. Could not locate ELA could not locate the recipie...

Troubleshooting ELA Issue 1 July 1997 55 Troubleshooting ELA Table 5-3 lists questions users ask the system administrator and suggested remedies to commonly encountered system problems. Table 5-3. User Questions or System Functionality Symptoms Question/Symptom Possible Cause Answer/Suggested Remedy...

Preventative Maintenance and Troubleshooting 56 Issue 1 July 1997 Recipient claims s/he did not get an ELA message. ■ Mailing list not current Check the mailing list for the recipient’s name. Administer, if necessary. ■ Subscriber’s mailbox not administered correctly ■ Check the Subscriber screen fo...

Troubleshooting ELA Issue 1 July 1997 57 “Everyone else seemed to have received their enhanced-list message. I got mine much later.” User mailbox full Check the List Measurements Subscriber Day screen for the affected user. Look at the available mailbox space. Advise the user to delete unneeded mess...

Issue 1 July 1997 59 6 Alarms Overview The following alarms are associated with the Enhanced-List Application. DELIVTS Resource Type Alarm Code: 1 Event ID: ELA-delivts01 Alarm Level: Warning Description: Trusted-server data lost, re-enter or restore. Repair Action: There are two recovery methods: ■...

Alarms 60 Issue 1 July 1997 Alarm Code: 2 Event ID: ELA-delivts02 Alarm Level: Warning Description: Trusted-server data partially lost, re-enter or restore. Repair Action: There are two recovery methods: ■ Access the Set Up Enhanced-List System Data window and re-enter all field information. ■ Resto...

REGISTRY Resource Type Issue 1 July 1997 61 2. Verify/administer the screen information, as required. 3. Repeat for the delivery trusted server. 4. Enter ch imapi and verify/administer as required. 5. When complete, enter the correct information in the Set Up Enhanced-List System Data window. REGIST...

Alarms 62 Issue 1 July 1997 SHADOW Resource Type Alarm Code: 1 Event ID: ELA-shadow01 Alarm Level: Warning Description: Shadow mailbox data lost, re-enter or restore. Repair Action: There are two recovery methods: ■ Access the Set Up Enhanced-List System Data window and re-enter the shadow mailbox e...

SHADOW Resource Type Issue 1 July 1997 63 Alarm Code: 3 Event ID: ELA-shadow03 Alarm Level: Warning Description: Shadow mailbox data corrupt, re-enter or restore. Repair Action: There are two recovery methods: ■ Access the Set Up Enhanced-List System Data window and re-enter the shadow mailbox exten...

Alarms 64 Issue 1 July 1997 Repair Action: Access the Set Up Enhanced-List System Data window and re-enter the shadow mailbox extension and community ID. If a shadow mailbox exists at the extension entered, the system displays a system prompt to that effect. If a shadow mailbox does not exist at the...

EL — Enhanced-List Application Issue 1 July 1997 65 If you regularly get this alarm, the following questions can help you evaluate how your business uses ELA: ■ Do your subscribers use large enhanced lists too frequently? Are they being used for trivial or non-business purposes? ■ Are subscriber mai...

Alarms 66 Issue 1 July 1997 Event ID: ELA-lostlock01 through ELA-lostlock10 Description: Messages to an enhanced list could not be delivered because someone was logged into the shadow mailbox. Repair Procedure: No one should ever be logged into the shadow mailbox. However. if someone is, change the ...

EL — Enhanced-List Application Issue 1 July 1997 67 Repair Procedure: Evaluate list membership hierarchy and delete unnecessary nesting so that ELA can handle delivery of the message. See Lucent I NTUITY Messaging Solutions Release 4 Administration, 585-310-564 for procedures. Event ID: ELA-loopviol...

Alarms 68 Issue 1 July 1997 2. Verify that the shadow mailbox belongs to a community that cannot receive messages. NOTE: The sending restrictions must be identical on all machines in the I NTUITY AUDIX network. Check the sending restrictions on all machines. See Lucent I NTUITY Messaging Solutions R...