Deploying caller applications

Deploy the caller application in the voice mail domain.

To use a caller application, it must be present on every MAS in the voice mail domain. Deployment distributes the caller application to all the MASs in a voice mail domain.

Note: This release of Avaya Modular Messaging does not support deployment of caller applications using Terminal Services. We strongly recommend that you deploy caller applications on the MAS itself and not by remote access.

For the procedure, see Deploying caller applications to a voice mail domain.

Create an association.

An association links a deployed caller application and the information used to access the caller application from the TUI. After deploying a caller application, you can create an association. If you do not do this, the caller application cannot be reached by callers unless it has been bound to a subscriber mailbox in the subscriber administration tool.

For the procedure, see About associations.

Adding an MAS

Re-deploying a caller application

Removing a deployed caller application from a voice mail domain

Troubleshooting deployed caller applications

Before you begin

The person using Caller Applications Editor is logged in to the domain as a System Administrator.

The System Administrator list is configured in Voice Mail System Configuration. For more information, see Configuring voice mail domain security.

Caller Applications is installed on every MAS in the voice mail domain.

Caller applications are enabled on all the MASs in the voice mail domain.

For a deployed caller application to run, the caller application feature must be enabled for the voice mail domain using Voice Mail System Configuration. For more information, see Configuring TUI general properties.

No other instances of Caller Applications Editor are deploying applications at the same time.

Considerations

If one or more MASs are not running during deployment, the caller application is transferred to the other MASs in the domain. Although deployment fails, a subsequent attempt to deploy the same caller application skips the transfers already completed and only transfers to the remaining MASs. Once a caller application has been deployed, a repeat deployment appears to be successful, but no data is transferred since the MASs already have this version of the caller application.

If a caller application has changed, it can be deployed again. If deployment succeeds, new callers receive the updated version of the caller application immediately. Callers using the existing version of the caller application continue to interact with that version while 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. For more information about re-deploying caller applications, see Re-deploying a caller application.

Caller applications can be undeployed by Caller Applications Editor. This removes the caller application from each MAS. 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. For more information, see Removing a deployed caller application from a voice mail domain.