MAS - CA - Procedure - Deploying Caller Applications to a VMD

Simply creating and saving a caller application does not automatically place it into service and make it available to callers. Once the caller application is finished, you must still deploy (install) it on the voice mail domain before it is considered “live” and available to callers.


Notes: To deploy caller applications, you must be a member of the Avaya Modular Messaging System Administrators ACL. This is configured in the Voice Mail System Configuration application, Security, System Administration ACL dialog box. See VMSC - VMD - Security - System Administration ACL. Deployed Caller Applications which contain schedules must be redeployed, if the Messaging Application Server (MAS) time zone is changed. This is not necessary for daylight savings time changes. The following procedures suggest an approach to using the Caller Applications Editor, when deploying caller applications. This is a procedural overview with links to the topics that describe each tree node and screen in detail.

Procedure 1: Preparing to Deploy Caller Applications

You are logged in to the domain as a System Administrator. These permission are set in the Voice Mail System Configuration window, Security - System Administration ALC. See VMSC - VMD - Security - System Administration ACL.

The Caller Applications software is installed and enabled as described in this procedure MAS - CA - Procedure - Using the Caller Applications Software.

Procedure 2: Connecting to the MAS

It is possible to run the Caller Applications Editor on a stand-alone PC. Because of this you must configure a connection to an MAS, even if the Caller Applications Editor is currently running on that MAS.

In the Modular Messaging Caller Applications window, click on the

Deployed applications node in the tree. See MAS - CA - Deployed Applications Node.

Click the Action > Connect to Message Application Server menu command. The system displays Message Application Server dialog box.

Select the message application server to connect to and click OK. The Caller Applications Editor is then able to determine the voice mail domain(s) available for caller application deployment and they appear in as nodes beneath the Deployed applications node.

Procedure 3: Deploying a Caller Application

Deployment distributes the caller application to all the running MASs in a voice mail domain.

When a new MAS is installed into a voice mail domain where caller applications are already deployed, the system automatically transfers the caller applications deployed in the voice mail domain to the new MAS. This also happens, when an MAS is moved from one domain to another.

Complete “Procedure 2” above.

In the Modular Messaging Caller Applications window, click on a

caller application node.

Note: The caller application must be saved before it can be deployed. For procedures for creating caller applications, see MAS - CA - Procedure - Creating & Editing Caller Applications.

Select the Action > All Tasks > Deploy Caller Application menu command. This launches the Caller Application Deployment Wizard. See MAS - CA - Caller Application Deployment Wizard

You must specify the voice mail domain and press the Next button to move to each of the screens of the wizard, then click Finish.

Click the relevant

voice mail domain node, beneath the

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

The deployed caller application is listed in the right hand pane.


Notes: In cases where the caller application is designed for callers to access it using a key press, you must also create associations. See the procedure for MAS - CA - Procedure - Creating Associations with the TUI. After deploying the caller application, use the Application analysis tool to discover and troubleshoot any problems that may exist. See the procedure for MAS - CA - Procedure - Analyzing Deployed Caller Applications.

Procedure 4: Re-deploying a Caller Application

If you have made changes to a caller application, it can be deployed again, as described in “Procedure 3” above.

When re-deployment succeeds, new callers have access to the updated version of the caller application immediately. Any callers using the existing version of the caller application at the time it is re-deployed continue to interact with the old version as long as they remain connected to the caller application. Temporarily, therefore, more than one version of the caller application can be stored and running on an MAS.

Each caller application contains an embedded identifier and a revision number. The revision number is incremented each time that the caller application is saved. Even if a caller application’s *.UMA file is renamed or copied by Windows Explorer, the application’s embedded identifier does not change. The MAS treats it as the same application.

An MAS that is contacted by the Caller Applications Editor and asked to deploy an application checks to see whether it already has a copy of the application deployed. If the MAS already has an application with the same embedded identifier and the same or a higher version number, it does not accept the re-deployment, regardless of the file name on the application.

If, however, you use the Action > Save As menu option from Caller Applications Editor to rename an application, the new version of the *.UMA file has a new embedded identifier and revision number. The application is then treated as a different application, and you can successfully deploy it.

Procedure 5: Undeploying a Caller Application

If you find you no longer need a deployed caller application, or you want to replace it with a different one, you can remove the caller application from the voice mail domain using the Caller Applications Editor.

Any callers using the caller application at the time of undeployment continue to interact with it for as long as they remain connected to 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 on the

deployed caller application listed in the right hand pane.

Select the

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

Click the Yes button to launch the Caller Application Undeployment Wizard. See MAS - CA - Caller Application Undeployment Wizard.

Press the Next button to move to each of the screens of the wizard, the click Finish. The caller application is removed from the voice mail domain node. Copies of the *.UMA files are deleted from all MASs in the voice mail domain.