TOC Index Search

 

Enhanced List Administration (ELA)

Overview of Enhanced List Application (ELA)

This section describes the Enhanced List Application (ELA) on an Intuity AUDIX Release�5 system.

Read this section if you are the AUDIX system administrator responsible for the configuration and maintenance of an Intuity AUDIX Release 5 system.

The procedures in this section assume you know basic Intuity AUDIX commands and navigation. If you are not familiar with these system basics, review the Getting Started section before you continue. See features, planning, and security for more information about those aspects of ELA software.

Administering Intuity AUDIX for ELA

To define the ELA server and functionality to Intuity AUDIX:

Activating ELA

ELA installation occurs as part of the Intuity AUDIX Release 5.0 installation or upgrade. After the ELA installation is complete, contact 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 remotely and activate the ELA feature.

When the remote support center has activated the ELA feature, continue with Verifying That ELA Is Enabled.

Verifying That ELA Is Enabled

  1. Log in to the Intuity AUDIX system using sa.

    2. The system displays the Avaya Intuity Main Menu.

  2. If Enhanced-List Manager does not display on the main menu, select:

    3. Feature Options

    The system displays the Feature Options Window.

  3. Ensure that the Enhanced-List Application field is set to ON:
  4. If the field is OFF, and you purchased/installed ELA, call the support center to request that the feature be enabled for your Intuity AUDIX system.
  5. Press F6 (Cancel) to exit the window.

Increasing the Number of Mailing Lists Allowed on the System

The following task contains instructions for the fields that relate directly to ELA. See Defining Basic Features and Parameters for a complete description of the fields in the System-Parameters Limits screen.

To administer AUDIX system limits to support ELA:

  1. Start at the Avaya Intuity Main Menu and select:

    2. AUDIX Administration

    The system displays the AUDIX Command Prompt Screen.

  2. At the enter command: prompt, enter change system-parameters limits

    3. The system displays the System-Parameters Limits screen.

  3. Tab to the Lists, Total Entries: field and enter 200000
  4. Check the Lists/Subscriber field. The default value is 100.
  5. Check the Recipients/Lists field. The default value is 250.
  6. Press F3 (Enter) to save the information in the system database.

    7. The cursor returns to the command line, and the system displays the following message:

    Command Successfully Completed.

  7. Enter exit or another administrative command at the enter command: prompt.

Defining an ELA Class of Service

The following task contains instructions for the fields that directly relate to ELA. The other fields should be administered to support other capabilities that you anticipate using. See Changing Class of Service Options in the Subscriber Administration section for a thorough description of the Class of Service feature.

Before you perform the following tasks, ensure that you have an unused Class of Service that you can define for ELA. We recommend that you use a COS that is between 2 and 11, because customers often use COS 1 as their default Class of Service.


 

Note: The ELA COS can only be used for ELA mailboxes, not for any other type of mailbox or subscriber.

To administer a COS for ELA:

  1. Start at the Avaya Intuity Main Menu and select:

    2. AUDIX Administration

    The system displays the AUDIX Command Prompt Screen.

  2. At the enter command: prompt, enter change cos COS_number, where COS_number is the unique Class of Service you would like to use for ELA. For example, enter change cos 10

    3. The system displays the Class of Service Screen, Page 1.

  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.
  4. Write down the COS number. You will need it later when you administer the ELA server.
  5. If you would like ELA to be able to distribute call answer messages, enter call-answer in the Type: field (under PERMISSIONS:). Otherwise, enter none.


    6.  

    Note: If you administer your system such that ELA mailboxes are to be accessible only by direct addressing and later decide you would like some ELA mailboxes with call answer capability, you do not need to create two Classes of Service. Administer the ELA COS to be call answer, but only administer the ELA mailbox extension as a number on the switch if/when you decide to allow call answer messages to be distributed to the members of that enhanced list.

  6. Enter y in following fields (under PERMISSIONS):
  7. Press F7 (NextPage). The system displays the Subscriber Class of Service Parameters Screen, Page 2.
  8. Enter the following information:
  9. Press F3 (Enter) to save the information in the system database.

    10. The cursor returns to the command line, and the system displays the following message:

    Command Successfully Completed.

  10. Enter exit or another administrative command at the enter command: prompt.

Setting Up ELA and Shadow Mailbox Community IDs

The following task contains instructions that directly relate to ELA. The other fields should be administered to support other capabilities that you anticipate using. See Setting Up Community Sending Restrictions in the Basic Messaging Administration section for a thorough description of Community Sending Restrictions.

Things to Consider

ELA mailing lists are a powerful messaging tool that all subscribers in your AUDIX network can access. However, should your business needs indicate differently, you can control who can use the enhanced lists by administering community sending restrictions. The following figure illustrates a typical application of sending restrictions for ELA and this application of sending restrictions is used as a basis for the following discussion.


 

Note: Although Community IDs and Class of Service sound similar, they have very different purposes. Class of Service is used to quickly and uniformly provide features and mailbox settings to many subscribers. Community IDs are used to restrict message sending and receiving among groups of subscribers.

Figure� 1. Example of Communities Administered for use with ELA

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 subscriber community, Community 9, and administer Community 9 to send to all communities (except the shadow mailbox community). Only subscribers you would like to have access to the enhanced lists are placed into Community 9. All other subscribers would not be able to send a message to the ELA mailbox.

Additionally, you must set up a shadow mailbox community ID, for example Community 11. The shadow mailbox community ID is administered such that messages can be sent to any community, but messages cannot be received from any other community. You do this so replies from pre-Release 4 Intuity AUDIX machines or from DEFINITY AUDIX and AUDIX Release 1 machines do not go to the shadow mailbox.

Also, you will have to administer the rest of your subscriber population to belong to a community restricted from sending messages to the enhanced-list mailbox community, for example, the default Community 1.


 

Note: If your AUDIX system is networked with other Avaya Intuity systems, all enhanced-list mailbox community sending restrictions must be consistently applied throughout the system, that is, the same Community ID numbers administered with the same restrictions. In particular, the shadow mailbox community must not be accessible by any other community on any machine in the network.

See Setting Up Community Sending Restrictions for a thorough description of Community Sending Restrictions.

Before You Begin

Before you begin the following procedure, use the display system-parameters sending restrictions command in AUDIX administration and ensure that you have at least two Communities that you can use for ELA (4 communities are needed if you are going to implement a special community for selected subscribers with access to ELA mailboxes.)

ELA Community ID

To set up sending an ELA Community ID:

  1. Start at the Avaya Intuity Main Menu and select:

    2. AUDIX Administration

    The system displays the AUDIX Command Prompt Screen.

  2. At the enter command: prompt, enter change system-parameters sending-restrictions

    3. The system displays the Sending Restrictions Screen.

  3. Enter y in the Activate Restrictions? field.
  4. Leave all fields blank (horizontally) that correspond to the (sender) Community ID that you've assigned to ELA, and leave all fields blank (vertically) that correspond to the (recipient) Community ID you've assigned for subscribers who will have access to the enhanced lists. (If all subscribers are to have access to enhanced lists, the recipient community will be the default subscriber community — usually community 1.)

    5. Following the example discussed in Things to Consider, Sender Community 9 would be blank (horizontally from left to right) and Recipient Community 10 would be blank (vertically from top to bottom).

  5. If all subscribers are to have access to enhanced lists, skip this step.

    6. Enter an r in the field that corresponds to the intersection between the (recipient) ELA Community ID and the (sender) community to which the rest of the subscriber population belongs. This prevents those who do not have access to enhanced lists from sending a message to an enhanced list.

    Following the example discussed in Things to Consider, there would be an r in the field corresponding to the intersection between Sender Community 1 (the default subscriber community) and Recipient Community 10 (the Enhanced List Mailbox Community).

Shadow Mailbox Community ID

  1. Enter an r in all (recipient community) fields in the column that corresponds to the Community ID that you've assigned to the shadow mailbox. This prevents messages from being sent into the shadow mailbox.

    2. Following the example discussed in Things to Consider, Recipient Community 11 would contain r's (vertically from top to bottom).

  2. Press F3 (Enter) to save the information in the system database.

    3. The cursor returns to the command line, and the system displays the following message:

    Command Successfully Completed.

  3. Continue with the next procedure or enter exit at the enter command: prompt.


    4.  

    Note: You must now use the Change Subscriber or Change COS screen to assign your subscribers to either the community that does not have access to enhanced lists, or to the special community that does have access. If you used your default subscriber community (Community 1) as the community that does not have access, then you only have to administer those selected individuals who will belong to the new special community with access to enhanced lists.

    See Setting Up Community Sending Restrictions for a thorough description of Community Sending Restrictions.

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 write down your system's IP address.

TCP/IP is a set of protocols that links computers across a wide variety of networks. TCP/IP must be administered for the ELA trusted server to communicate with AUDIX.

You will need to know the:

Your PC/LAN system administrator should have this information.

To administer TCP/IP networking:

  1. Start at the Avaya Intuity Main Menu and select:

    2. TCP/IP Administration
    	Network Addressing

    The system displays the Network Addressing Window.


     

    Note: Write this IP address down, as you will need it when you administer the ELA trusted server later in this section.

  2. If the Network Addressing Window is blank, administer TCP/IP for your system.
  3. Continue with the next procedure.

Setting Up IMAPI Sessions for Trusted Server Access

Whenever a trusted server accesses an AUDIX mailbox, it uses an IMAPI session. IMAPI is the software that allows access to Intuity AUDIX mailboxes. Depending on what Intuity model you purchased, there can be up to 96 active sessions simultaneously, some of which you need to set for trusted server use.


 

Note: IMAPI sessions cannot be reserved for use by ELA. The following procedure administers the maximum number of IMAPI sessions you will allow trusted servers to use simultaneously, but does not guarantee that an IMAPI session will be available. You should monitor ELA trusted server activity to see if trusted server requests for IMAPI sessions are frequently being denied because all sessions are in use (see Overview of Reports). If so, you may need to purchase more IMAPI sessions.

To set IMAPI sessions for trusted server use:

  1. Start at the Avaya Intuity Main Menu and select:

    2. AUDIX Administration

    The system displays the AUDIX Command Prompt Screen.

  2. At the enter command: prompt, enter change system-parameters imapi-options

    3. The system displays the System-Parameters IMAPI-Options Screen, Page 1.


     

    Note: The following instructions are for the fields that directly relate to ELA. See Email (Internet Messaging) to understand trusted server implications for Internet Messaging.

  3. In the Maximum Simultaneous Sessions: field enter 2 more than the current value. (For example, if the field currently reads 30, enter 32.)

    4. This number includes sessions for subscribers who are logged into their mailboxes using Message Manager or Internet Messaging, if applicable, and cannot exceed the value in the Total Sessions Purchased field.

  4. In the Simultaneous Sessions Available for Trusted Server Access: field enter 2 more than the current value. (For example, if the field currently reads 2, enter 4.)


    5.  
    Platform
    Maximum Value
    MAP/5P and MAP/40P
    4
    MAP/100P
    6

  5. Enter 5 in the IMAPI Session Timeout: field.
  6. Enter 5 in the Trusted Server Session Timeout: field.
  7. Enter y in the Message Transfer? field.
  8. Press F3 (Enter) to save this information to the system database.

    9. The cursor returns to the command line, and the system displays the following message:

    Command Successfully Completed.

  9. Continue with the next procedure or enter exit at the enter command: prompt.

Defining Two ELA Trusted Servers

The ELA software runs as two separate trusted servers. For the ELA servers to communicate with the Intuity AUDIX server, they must be defined to the Intuity AUDIX system. The installation worksheets you received from your account representative will have the exact names for the ELA trusted servers. However, for the purposes of this document, the first ELA trusted server will be referred to as the administrative server and the second ELA trusted server as the delivery server.

A request from ELA to send a message to an AUDIX mailbox involves invoking an IMAPI session and locking the ELA mailbox. A server that uses IMAPI to access an AUDIX mailbox is known as a trusted server.

The procedures in this section include setting a password the trusted server must use to access AUDIX. There is a secondary layer of security (in addition to a trusted server password) that you can administer. This additional layer of security involves setting a separate IMAPI password that the trusted server must use before the system will allow an IMAPI session to be invoked.

While administration of this additional password is optional, it is strongly recommended. See Setting an IMAPI Password.

Before You Begin

Before adding the ELA trusted server to the system, you will need the following information:

Adding the Trusted Servers

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 Intuity AUDIX server:

  1. Start at the Avaya Intuity Main Menu and select:

    2. AUDIX Administration

    The system displays the AUDIX Command Prompt Screen.

  2. At the enter command: prompt, enter add trusted-server

    3. The system displays the Trusted-Server Profile Screen.


     

    Tip: To see a list of existing trusted servers enter li tr at the command line.

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

    4. 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 Avaya Intuity in the form w.x.y.z, where each letter is a number, 0 to 255. (See Administering TCP/IP for information on 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.

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

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

    10. 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.
  11. Do you want to administer an IMAPI password?

Setting an IMAPI Password

The IMAPI password is an additional layer of security for use with trusted servers. The password is optional until it is administered for one trusted server. It is then required each time any trusted server requests a session with the Intuity AUDIX. Since trusted servers are used by many Intuity AUDIX features, this password might already be established.


 


If the password is already administered and you change it, all uses of the password must be updated to the new password. Otherwise, all other features that use the IMAPI password stop working. Also, a NOEXTSEC event is added to the Administrator's Log.

To set an IMAPI password:

  1. Start at the Avaya Intuity Main Menu and select:

    2. AUDIX Administration

    The system displays the AUDIX Command Prompt Screen.

  2. At the enter command: prompt, enter change imapi-password

    3. The system displays the Change IMAPI-Password Screen.

  3. Complete the Current Password: and New Password: fields.
  4. Press F3 (Enter) to save the change.
  5. Enter exit or another administrative command at the enter command: prompt.

Administering ELA for AUDIX

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:

Defining the AUDIX Server and Administering Access

To allow communication between ELA and AUDIX, you must perform some initial ELA administration.

To administer the ELA server, you need to know the:

To administer the ELA server:

  1. Start at the Avaya Intuity Main Menu and select:

    2. Enhanced-List Manager
    	Set Up Enhanced-List System Data

    The system displays the Set Up Enhanced-List System Data Window.

  2. Complete the fields in this window using the information in the table for Field Definitions: Set Up Enhanced-List System Data.
  3. Press F3 (Save) to save the ELA server information to the system database.

    4. The system displays the message "Successfully Updated!" and asks you to press F1 to acknowledge the message.

  4. Press F1 (Acknowlg Message).

    5. The system displays the Enhanced List Manager menu.

  5. Continue with the next procedure or press F6 (Cancel) repeatedly to return to the Avaya Intuity Main Menu.

Guidelines for Naming Enhanced Lists

We recommend that you use the following guidelines when you name an enhanced list. These guidelines can help prevent subscribers from inadvertently sending their messages to the enhanced list, instead of to a person.

Creating Enhanced Lists

To create an enhanced list and add members:

  1. Start at the Avaya Intuity Main Menu and select:

    2. Enhanced-List Manager
    	Administer Enhanced-Lists

    The system displays the Administer Enhanced-Lists Window.

  2. Press F4 (New E-List).

    3. The system displays the New Enhanced-List Window.

  3. Complete the fields in this window using the information in the table for Field Definitions: New Enhanced List Window.
  4. Press F3 (Save) to save this information in the system database.

    5. 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 with the other lists).

Guidelines for Selecting Enhanced-List Members

The following can be members of an enhanced list:

The following cannot be members of an enhanced list:

Adding Members to Enhanced Lists

To add member names, extensions, and network (email) addresses to a new enhanced list, perform the following tasks. Start on the Administer Enhanced Lists window.

  1. Press F5 (Open E-List).

    2. The system displays the Enhanced-List Membership for Listname Window.

  2. Press F4 (Add Member).

    3. The system displays the Add Member Window.

  3. Enter one of the following:
  4. Press F3 (Save) to save this information in the system database.


    5.  

    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, extensions, and email addresses.


    6.  

    Note: We recommend that you print a copy of the completed list to your system printer, if available. You can use this printout to search multiple lists for duplicate names or potential loops with a networked AUDIX system. Additionally, should you inadvertently delete an enhanced list, you would have a source from which to recreate the enhanced list. (The system's nightly data backup also saves ELA setup data, lists, and memberships.)

  6. Review the Administer Enhanced-Lists window. If you want to change or delete any information you just entered:
      1. Press CANCEL.

        2. The Enhanced List Membership window displays.

      2. Select the member name you want to change or delete.
      3. Press F7 (Delete Member).
      4. Go to Step 2 to re-enter member information, or go to Step 7 to continue.
  7. When you have finished adding member names to this enhanced list, press F6 (Cancel) repeatedly to return to the main menu.
Adding/Deleting Members to an Enhanced List

To change data for a member of an enhanced list, such as the name or telephone extension, make the change in AUDIX as described in Changing Subscriber Data. The change is automatically reflected in all enhanced lists that contain that member.

To add or delete the members of an existing enhanced list:

  1. Start at the Avaya Intuity Main Menu and select:

    2. Enhanced-List Manager
    	Administer Enhanced-Lists

    The system displays the Administer Enhanced-Lists Window. The names of your enhanced lists display in the window (along with other descriptive data).

  2. Using the arrow keys, select the list you would like to add members to. If the list is not on the visible page, select the list by one of the following means:
  3. Press F5 (Open E-List).

    4. The system displays the Enhanced-List Membership for Listname (listextension) Window. The member names of the selected list display in the window. Accompanying each name is an extension number or network (email) address and other descriptive data.

    At this point you can:

Adding a Member
  1. Press F4 (Add Member).

    2. The system displays the Add Member Window.

      1. Enter one of the following:
      2. The subscriber's name as it appears in the AUDIX system
      3. The subscriber's extension
      4. The subscriber's network (email) address in the format dictated by the email system, for example, username@trusted-servername
      5. Press F3 (Save) to save this information in the system database.


        6.  

        Note: If the extension you added is an ELA enhanced list, the system puts yes in the E-list? field.

      6. Continue entering names/extensions/email addresses until all new members have been added.
      7. Press F6 (Cancel) to return to the Administer Enhanced List window or proceed to Step 7 to print a copy of the list.
Finding a Member
  1. To find a member name in a list:
      1. Press F8 (Actions).

        2. An Actions menu displays.

      2. Select Find Member and press ENTER.
      3. Enter the name or extension of the person or list you would like to find and press F3 (Find).

        4. The Enhanced-Lists Membership window re-displays with the specified person or list highlighted.

Deleting a Member
  1. To delete a member:
      1. Locate the member name to be deleted. See Finding a Member.
      2. Press F7 (Delete Member).

        3. The system displays the confirmation message:

        CONFIRM: Deleting

        Name= List - Listname
        Extension/Address= Listextension
        Enter y to continue, n to abort.

      3. Enter y

        4. The Enhanced-List Membership window redisplays.

      4. Continue with Step 7 to print a copy of the list.
Printing an Enhanced List
  1. Press F8 (Actions). An Actions menu displays.
      1. Select Print List Membership and press ENTER.

        2. The system displays the message "Printing List Membership for Listname (listextension)" and sends the list to the system printer.

      2. Press F1 (Acknowlg Message).

        3. The system redisplays the Actions menu.

      3. Proceed to Step 8.
  2. When you have finished, press F6 (Cancel) repeatedly to return to the main menu.

Deleting an Enhanced List

To delete an existing enhanced list:

  1. Start at the Avaya Intuity Main Menu and select:

    2. Enhanced-List Manager
    	Administer Enhanced-Lists

    The system displays the Administer Enhanced-Lists Window.

  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.
  3. Press F7 (Delete E-List).

    4. The system displays the Confirm Deletion of Enhanced-List Window.

  4. Do you want to delete the associated AUDIX mailbox?
  5. Press F3 (Delete) to delete the enhanced list.

    6. AUDIX deletes the mailbox and all information in it, including any enhanced-list members or messages.

    The system displays the message "Deleted Listname (listextension) Enhanced List" and asks you to press F1 acknowledge the message.

  6. Press F1 (Acknowlg Message).

    7. The system redisplays the Administer Enhanced-Lists window.

  7. Press F6 (Cancel) repeatedly to return to the Avaya Intuity Main Menu.

Recording Names for Enhanced Lists

Once you have established an enhanced list, it is a good idea to record a name for the list. That way, subscribers will hear a meaningful name for the list when they use the telephone user interface to address a message to an enhanced-list mailbox for distribution. However, you need to record the name using an administrative recording session.

To record a name for an enhanced list:

  1. From a touch-tone telephone, log in as an administrator.
  2. Press 9.

    3. The system prompts with "To record names, press 4."


     

    Note: If you get an error message, open the Class of Service screen for the administrator's extension and change the Announcement Control? field to y. Then start again.

  3. Press 4.

    4. The system prompts with "Please enter the extension and pound sign."

  4. Enter the extension for the enhanced-list mailbox.

    5. The system prompts with "When finished recording, press pound to approve or 1 to edit your message. Record at the tone."

  5. After the tone, speak the name of the list.
  6. Press #.
  7. Repeat Step 4 through Step 6 to record additional names.


    8.  


    You should also record a name for the Shadow mailbox, using the same procedure. Use a name such as, "Mailing list - Do not reply." That way, anyone who inadvertently enters the Shadow mailbox extension, will not try to send a message to it or to reply to a message from it.

  8. Press *r to return to the main menu.

Testing Enhanced Lists

  1. Perform the administration outlined below, including:

See your installation information if you need help with the following procedures:

  1. Set up two test subscribers and two test telephones.
  2. Create a test list with subscribers test-1 and test-2 as members.
  3. Use the test-1 telephone to create and send a voice mail message to the ELA mailbox. Record the following or a similar test message and then enter the address for the enhanced-list mailbox:

    4. "This is a test ELA message for Intuity AUDIX."

  4. Hang up the test-1 telephone to disconnect.
  5. Verify that the MWIs for the test subscribers' telephones activate and that the test subscribers received the message.
  6. Delete the test messages.
  7. Delete the test subscribers. (Optional)
  8. Delete the test list. (Optional)

Preventive Maintenance and Troubleshooting

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 with ELA by displaying a minor and warning message (Alarms: w or Alarms: m) on the AUDIX Administration status line when it logs an administration event. Check the status line (at the top of the AUDIX Administration screen) at least once a day.

Other events besides those generated by ELA create administrative log entries, but you can view ELA-specific events. You should do this on a regular basis to monitor ELA performance. To view ELA-specific log entries:

  1. Start at the Avaya Intuity Main Menu and select:

    2. AUDIX Administration

    The system displays the AUDIX Command Prompt Screen.

  2. At the enter command: prompt, enter display administrators-log

    3. The system displays the Administrator's Log screen.

  3. Enter the starting date and time.
  4. Enter EL in the Application: field.
  5. Press F3 (Save) to display the alarm entries.
  6. Examine the displayed entries. See Alarms and Events for a list of events and alarms, and associated repair procedures.
  7. Take whatever corrective action is necessary.
  8. Enter exit or another administrative command at the enter command: prompt.

Checking the Delivery Failure Log

The delivery failure log contains entries for all failed deliveries, along with descriptive data regarding cause for the failure and other information. Check this log to monitor ELA and system performance and if a subscriber complains that messages are not being delivered.

To view the delivery failure log:

  1. Start at the Avaya Intuity Main Menu and select:

    2. Enhanced-List Manager
    	View E-List Delivery Failure Log

    The system displays the Enhanced-List Delivery Failure Log Window. See the table for Field Definitions: Enhanced-List Delivery Failure Log .

  2. Press F8 (Print) to send a copy of this report to the system printer, if you have a printer available.
  3. Press F6 (Cancel) repeatedly to return to the Avaya Intuity Main Menu.

Delivery Failure Codes

Delivery failure logs contain the following codes:
 
Table: Delivery Failure Codes
Reason of Failure
Description
Full mailbox
The recipient has a full mailbox.
Could not locate
AUDIX could not locate the recipient. The subscriber may have been deleted from the system since the message was created.
Transmission probs
Transmission difficulties occurred.
Permission denied
Permission to the receiving mailbox is denied. Possible reasons include:
  • Sending a nonbroadcast message to a broadcast mailbox
  • Outgoing AMIS analog networking not turned on
  • Recipient not allowed to receive voice mail
Sending restriction
Delivery denied because of sending restrictions
Login annc exists
The login announcement already exists.
AMIS wrong number
This is the wrong number for this AMIS analog recipient.
Too many AMIS xmits
Too many transmission attempts for AMIS analog resulted in a transmit-attempt exception.
AMIS unknown return
AMIS returned the message without identifying a reason.
misc internal fail
Miscellaneous internal delivery failure
AMIS longer > 8 minutes
The AMIS message is longer than eight minutes.
Unsupported media
The message contains media that AUDIX does not support for this particular system or subscriber.
Pvt to unsup remote
Private messages are not delivered to unsupported remote systems.
Message too large
The voice component of the message is too large for the remote system.
Unrecgnzd fail code
The delivery failed for an unknown reason.

Troubleshooting ELA

The Enhanced List Troubleshooting table lists potential problems and suggested remedies to commonly encountered system problems.


 
Table: Enhanced List Troubleshooting
Problem
Cause
Solutions
During an upgrade failure, installer/administrator cannot differentiate between AUDIX mailboxes and ELA mailboxes.
—
Use the li cos command from AUDIX Administration to determine the ELA Class(es) of Service. Use the li su command and note the extension(s) of all mailboxes with the applicable COS.
Subscribers complain that they cannot reply to messages received from an enhanced list.
Message was sent to an enhanced list that did not permit "Reply to Sender."
  • Administer the enhanced list to allow Reply to Sender, if appropriate.
  • Educate your subscribers about ELA functionality.
Community IDs for the subscriber or recipient incorrectly administered
Administer Community IDs for subscriber or recipient, if appropriate.
Recipient is not on a Avaya Intuity system or is on a pre-R4 system.
Upgrade system to Avaya Intuity R4.1 or higher.
Subscribers complain of getting multiple copies of the same message.
Recipient is on more than one list.
  • ELA does not check nested lists to see if the same name appears in more than one place. Print out a copy of your enhanced lists and remove duplicates, if possible.
  • Educate your subscribers about ELA functionality.
You inadvertently deleted the shadow mailbox.
—
ELA raises a warning alarm. Any messages waiting in the delivery "queue" are lost.
Re-enter the shadow extension on the Set Up Enhanced-List System Data Window and then press F3 (Save).
Recipient claims she or 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 Activity Log to verify that the subscriber did not receive the message.
  • Check the Subscriber screen for the affected subscriber. Look at the Mailbox size. Put subscriber in a COS with a larger mailbox, if necessary.
  • Check the List Measurements Subscriber Day screen for the affected subscriber. Look at the available mailbox space. Advise the subscriber to delete unneeded messages and greetings, if appropriate.
  • Check that Community ID is correct.
  • System delivery failure
System delivery failures can arise from many sources.
Recipient claims she or he did not get an ELA message. (continued)
  • Sending Restrictions not consistent across machines
Administer Community IDs for all Avaya Intuity machines, if appropriate.
The name of an enhanced-list member keeps disappearing from enhanced lists.
System feature to delete non- administered remote subscribers is active.
  • From AUDIX Administration, enter ch�sys�fe. Access page 4 and change the Even if on Mailing List? field to n.
  • Re-administer the remote subscriber.
Subscribers complain that they cannot send a message to an enhanced-list mailbox.
Subscriber belongs to a community with sending restrictions administered.
Consider whether to change this subscriber's community ID to allow her/him to use enhanced lists.
Recipient asks why she or he received the message from the enhanced list much later than other recipients.
Subscriber mailbox full
Check the List Measurements Subscriber Day screen for the affected subscriber. Look at the available mailbox space. Advise the subscriber to delete unneeded messages and greetings, if appropriate or consider putting the subscriber in a COS with a larger mailbox.
Enhanced list was very large.
Remember that ELA `throttles' traffic during periods of heavy user traffic. Inform subscriber that it message delivery to a large recipient population does take time.
Networking problems between originator system and recipient system.
Perform networking troubleshooting. See Diagnostics and Troubleshooting for more information.
You inadvertently delete an enhanced list.

There are two ways to restore an enhanced list:
  • Reenter the names on the list.
  • Restore the data from the previous night's tape backup.


    • There is no way to selectively restore only enhanced lists from the back-up tape. Your system will lose all incremental administration data from the point of backup. Use this method only if you are sure the business can tolerate the loss of recent administration.

Avaya Communication
http://www.avaya.com
Avaya UCS Information Development
TOC Index Search