Build the caller application(s)

To build the actual caller application, you must use the Caller Applications Editor. The Caller Applications Editor is a GUI software tool provided as part of your Avaya Modular Messaging system. It is designed specifically to allow you to create and deploy your own caller applications.

You can use the Caller Applications Editor either directly on the MAS where you intend to use the caller application or as a standalone tool on a machine outside the voice mail domain. If you choose to develop your applications on a separate machine, you must remember to import the caller application (*.uma) file to the MAS before you can install and deploy it.

Caller applications are built around a “node” concept. That is, you start with a base caller application node that acts as the gateway into the caller application, and then (if required) add nodes under it to perform additional functions. These additional nodes are called application, or action, nodes.

A caller application can consist of many nodes at many levels or a single node. It may provide callers with many options at multiple levels, or it could play a simple greeting and automatically transfer the caller to an extension. It all depends on what you want or need the caller application to do, as determined by your design plan.

Note: What follows is a general description of the process to build a caller application using the Caller Applications Editor. It assumes that you have already planned your caller application design (see Plan carefully!) and created the necessary targets (see Set up your targets). For more specific information about how to use the Caller Applications Editor itself or to perform a specific step in the process, follow the appropriate links in the text.

Open the Caller Applications Editor.

For the procedure, see Starting the Caller Applications Editor.

Create the caller application node and set the properties for the caller application.

For the procedure, see Creating a caller application node.

Add the application action nodes required to enable the caller application to perform all the functions called for in your plan. Be sure to set all the appropriate properties for each action node. Remember too that you can assign only one prompt per node.

For the procedure to add application action nodes and set their properties, see Adding application (action) nodes to a caller application.

For more ideas on how to incorporate and use application action nodes see More on caller applications.

Note: As you are adding nodes, and especially if you find yourself modifying your caller application, we recommend that you also remember to update your list of prompts as you go along.

Save the caller application.

For the procedure, see Saving a caller application.

If you have not been saving your work as you go along, you should save your caller application before recording and assigning your prompts. Once you have saved the application, then you are ready to Record and assign prompts.