Avaya Aura® Messaging (AAM) is a flexible messaging platform that supports various deployment models and configurations. It can be deployed in a virtualized environment using VMware or on Avaya's proprietary System Platform, providing deployment flexibility (B). A core feature of its unified messaging capability is the choice of message store; administrators can select either the integrated Avaya Message Store (AMS) or an external Microsoft Exchange server to store voice messages (C). For scalability and high availability, AAM supports a multi-server (distributed) configuration where the Application Server (handling call processing) is logically and physically separated from the server hosting the Avaya Message Store (D).

A. Port allocation in AAM is configurable and dynamic based on system needs; there is no fixed, mandatory reservation of 20 ports specifically for retrieving messages.

E. An Avaya Aura® Messaging application server supports up to 300 simultaneous SIP or H.323 sessions, not 100. The figure of 100 sessions per server is incorrect.

1. Avaya Aura® Messaging Overview and Specification, Release 7.1 (Document ID: 03-603836, Issue 10, September 2017)

For B: Page 10, Section "Deployment options," states, "Avaya Aura® Messaging can be deployed as a virtualized application on VMware vSphere ESXi... Messaging can also be deployed on System Platform."

For C: Page 12, Section "Message storage," details the two options: "Avaya Message Store (AMS)" and "Microsoft Exchange Server."

For E: Page 15, Table 3 "Avaya Aura® Messaging capacities," specifies "Maximum number of voice ports per application server" as "300."

2. Planning for Avaya Aura® Messaging, Release 7.1 (Document ID: 16-603837, Issue 10, September 2017)

For D: Page 18, Section "Distributed configuration," describes the architecture: "In a distributed configuration, you can have one or more Application servers and one or more Storage servers." This confirms the separation of roles.