Administration Guide - Avaya Support

Caller Applications Editor
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 Deploying Caller Applications
to a VMD on page 6-13.
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.
Note: The following procedures suggest an approach to using the Caller
Applications Editor, when creating associations for deploying caller
applications. This is a procedural overview with links to the topics that
describe each tree node and screen in detail.
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.
Avaya Modular Messaging Release 3.1 with the Avaya MSS
February 2007 MAS Administration Guide
6–17