MAS - CA - Procedure - Creating Associations with the TUI

In cases where the caller application is designed for callers to access it using a key press or combination of key presses, you must create an association as part of the deployment process. For the deployment procedure, see MAS - CA - Procedure - Deploying Caller Applications to a VMD.

Associations are the links between a deployed caller application and the information from the Telephone User Interface (TUI) used to access the caller application. Associations enable the system to launch a caller application, if one or both of the following launch conditions are met:

A caller enters an identifying number (ID number), when prompted by the Automated Attendant or another caller application. The ID number appears to the caller as a mailbox number.

A caller dials a specified direct-dial number or extension number (the “called number”).

When you create an association, you must configure at least one of these launch conditions. If you configure both, meeting either condition will launch the caller application. Any given association can launch only one specified caller application. To help identify the association, you assign it a name.

You can re-use a deployed caller application by specifying multiple associations, with different ID numbers, for the same caller application. This means the deployed caller application is the same, but different mailbox numbers or Automated Attendant menu choices can be used to access it. For example, this might be useful, if you wanted to launch multiple bulletin board type applications using different mailbox numbers.

Procedure 1: Planning Association ID Numbers

Association ID numbers can be any length, from one digit up to the maximum number of digits used for mailbox numbers in the voice mail domain.

This means it is possible for you to create an association ID number that is identical to a single-digit Automated Attendant menu option or a valid mailbox number.

If you set up a single-digit association ID number that requires the same key press as an Automated Attendant menu option, the Automated Attendant menu option will always be used. This is because the association ID number is only recognized, if it is followed by a time-out or terminated with a #. For this reason, Avaya recommends that you do not use a single-digit number as the association ID number.

If an association ID number is identical to a valid mailbox number, when a caller enters that number, the association ID number is used and the associated caller application runs. This can be useful, if you want to prevent caller access to a mailbox.

Note: In this scenario, although callers cannot leave messages, subscriber access to the mailbox is not affected.

Procedure 2: Creating an Association in a Deployed Caller Application

Follow “Procedure 1” above.

In the Modular Messaging Caller Applications window, click on the relevant

voice mail domain node, beneath the

Deployed applications node in the tree. See MAS - CA - Voice Mail Domain Node.

Click the

Associations node. See MAS - CA - Associations Node.

Click the

Action > New > Association menu command. The system displays Add Association dialog box. See MAS - CA - Add Association/Association Properties Dialog Box.

Enter the association name, association ID and/or called number.

Select the caller application which will be launched when the conditions are met.

Click OK. The

association is listed in the right hand pane.

If you need to edit the association details, select the association in the right hand pane and click

Action > Properties to launch the Association Properties dialog box.

Procedure 3: Configuring Automated Attendant to Launch a Caller Application

Follow “Procedure 2” above.

Make a note of the Association ID number for the caller application you wish to launch from the TUI.

In the Voice Mail System Configuration window, Automated Attendant dialog, Attendant Main Menu Editor tab, enter the association ID in the Mailbox Number field and click OK. See VMSC - VMD - Auto Attendant - Attendant Main Menu Editor Tab.

Procedure 4: Deleting an Association

If you find you no longer want to use a particular association with a deployed caller application, you can delete the association without removing the caller application from the voice mail domain. This allows you to create and use new associations without having to re-deploy the caller application.

Click on the relevant

voice mail domain node, beneath the

Deployed applications node in the tree. See MAS - CA - Voice Mail Domain Node.

Click the

Associations node. See MAS - CA - Associations Node.

Click on the

association listed in the right hand pane.

Select the

Action > Delete menu command. This prompts you to confirm the action.

The association is then removed from the voice mail domain.