Server roles

The Messaging system is designed to perform two distinct functions or roles. These roles are:

• Storage role

• Application role

These roles are independent of the server on which the roles reside. Using the Messaging architecture, you can change the role of the server. For example, you can change a single-server system into a two-server system in which the original server plays the storage role and the newly acquired server plays the application role.

Storage role

The storage role stores:

• Voice messages (When using the Avaya message store)

• Directory data in an LDAP directory (users contacts, distribution lists, caller applications)

The storage role also supports nonvoice interaction with users, including:

• IMAP4 access to voice messages (When using the Avaya message store)

• SMTP routing of voice messages, text-message notifications, and email copies

• Connectivity to:

  • The LDAP directory

  • The message store for monitoring Message Waiting Indicator (MWI) and Notify Me (text message notifications, telephone call notification, and e-mail copies)

  • User Preferences

Application role

The application role supports real-time telephony interaction with users and callers, including:

• Integration with your telephony system for voice and MWI

• A telephone user interface for users and callers, including Auto Attendant and Caller Applications

• Local caching for the offline handling of user directory data, greetings, recorded names, and voice messages

  Note

  In the offline mode, IMAP only shows messages that have reached the storage server. Messages that are only in the cache on the application servers are not accessible with IMAP during the offline mode.