In an Avaya IX™ Messaging (now Avaya Aura® Messaging) High Availability (HA) deployment, each Voice Server Node (VSN) is engineered with specific capacity limits to ensure system stability and performance. According to official Avaya technical specifications, a single VSN is designed to support a maximum of 100 SIP ports. This limit is a fundamental design parameter for the VSN component, regardless of whether it is in a standalone or HA configuration. Exceeding this limit can lead to performance degradation and is not a supported configuration.

B. 120: This number exceeds the documented maximum capacity of 100 SIP ports for a single VSN.

C. 150: This value is 50% higher than the specified maximum and would overload the VSN's processing capabilities.

D. 220: This is more than double the supported SIP port limit and is not a valid capacity for a VSN.

1. Avaya Aura® Messaging Documentation Library, "Implementing Avaya Aura® Messaging," Release 10.8, NN43001-615, Issue 1.0, December 2020.

Page 16, Chapter 2: System capacities, Table 2: Avaya Aura® Messaging system capacities. The table explicitly states, "Maximum number of SIP ports per VSN" is "100". This document is the primary implementation guide for the system, which includes the former Avaya IX™ Messaging branding.

According to the official Avaya documentation for Avaya Aura® Messaging 10.8 SP1, the application must be installed on a server running one of three specific Microsoft Windows Server operating systems. These supported platforms are Windows Server 2012 R2, Windows Server 2016, and Windows Server 2019. Both Standard and Datacenter editions of these 64-bit operating systems are supported. The installation process and system prerequisites are explicitly defined for these environments to ensure stability and full feature compatibility.

A. 2008 Standard Edition: This operating system is outdated and is not listed as a supported platform for Avaya Aura® Messaging 10.8 SP1.

C. MAC operating systems: Avaya Aura® Messaging is a server-side application designed exclusively for the Windows Server environment and does not support any macOS versions for installation.

1. Avaya. (2020, December). Installing and Configuring Avaya Aura® Messaging, Release 10.8, Service Pack 1 (Document No. NN43001-618, Issue 1.0). Avaya Inc.

Reference: Chapter 2: Server requirements, Section: "Operating system", Page 13. This section explicitly lists "Microsoft Windows Server 2012 R2 Standard or Datacenter Edition (64-bit)", "Microsoft Windows Server 2016 Standard or Datacenter Edition (64-bit)", and "Microsoft Windows Server 2019 Standard or Datacenter Edition (64-bit)" as the supported operating systems.

2. Avaya. (2020, December). Release Notes for Avaya Aura® Messaging, Release 10.8, Service Pack 1 (Document No. NN43001-118, Issue 1.0). Avaya Inc.

Reference: Chapter 3: System requirements, Section: "Server requirements", Page 10. This document corroborates the installation guide, stating the same supported Windows Server versions (2012 R2, 2016, and 2019).

Basic Unified Messaging (UM) via SMTP Forwarding is a feature designed to consolidate a user's messages into a single location. The Avaya IX™ Messaging server acts as the initial recipient for voice and fax messages. It then forwards these messages, typically as .wav or .tif file attachments, to an external, SMTP-compliant email server. This process populates the user's email inbox with all their communication types (email, voice, fax), creating a single, unified view. Consequently, the corporate email server becomes the primary message store for all these message types, managed through the user's standard email client.

C. All message types are stored on the Messaging server.

This is incorrect. In this model, voice and fax messages are forwarded to and stored on the email server, not retained as the primary copy on the Messaging server.

E. The user is given a multiple view in their email client.

This is incorrect. The fundamental goal of Unified Messaging is to provide a single, consolidated view of all messages within the email client to simplify management.

1. Avaya Aura® Messaging Feature Description and Implementation, Release 7.1 (Document ID: NN43001-514, November 2018)

Section: Unified Messaging, Page 101: "With Basic Unified Messaging (UM) via SMTP Forwarding, Messaging forwards received voice and fax messages to an SMTP-compliant email server." (Supports option B).

Section: Unified Messaging, Page 101: "The user receives all messages (voice, fax, and email) in a single email inbox." (Supports option A and contradicts E).

Section: Unified Messaging, Page 101: "The email server is the message store for all message types." (Supports option D and contradicts C).

2. Administering Avaya Aura® Messaging, Release 7.1 (Document ID: NN43001-700, November 2018)

Section: Chapter 11: Unified Messaging, Page 387: "Basic Unified Messaging (UM) via SMTP Forwarding: Messaging forwards voice and fax messages to an external email server. The email server is the message store for all message types." (Reiterates support for options B and D).

The standard backup procedure for the Avaya Messaging solution, as defined in the official administration guide, specifically targets three critical folders to ensure a complete and successful restoration. These folders are UC\DB, which contains the system configuration and user data; UC\Messages, which stores all user voice, fax, and email messages; and UC\Prompts, which holds the system's audio prompts. Backing up these three directories captures all essential data required to restore the system to its operational state.

A. UC\DBCom: This folder is not specified in the standard backup procedure. The primary database files and configuration are located in the UC\DB folder.

B. UC\Licenses: While license files are critical for system operation, they are not included in the data backup process performed by the standard Avaya Messaging backup utility.

1. Avaya Aura® Messaging, Administering Avaya Messaging, Release 11.0, Document Number 16-603763, Issue 1, November 2017.

Page 169, Chapter 10: Backing up and restoring the system, Section: "Backing up the system": This section explicitly states, "Avaya Messaging provides a backup utility that you can use to back up the following folders: DB, Messages, Prompts." It further details the contents: "The database folder contains the system configuration and user data," "The messages folder contains the voice, fax, and email messages," and "The prompts folder contains the system prompts." This directly supports the selection of C, D, and E.

The "Synchronization Options" tab within the Avaya IX™ Messaging (Avaya Aura® Messaging) mailbox configuration is specifically designed to manage the synchronization of data between the messaging server and an external email server. This includes configuring Message Synchronization and Calendar Synchronization. Option A correctly identifies that this tab is used to connect the mailbox with an email server feature, such as one using the IMAP protocol (like IMAP TSE), by enabling the service and specifying server details. This aligns directly with the documented purpose of this configuration section.

B. This describes a presence feature. Such settings are typically managed through Avaya Aura® Presence Services and System Manager profiles, not the messaging mailbox synchronization tab.

C. Changing a user's location status is a dynamic action performed by the user through a client interface (like a phone or software client), not a static administrative configuration.

D. Voice verification enrollment is a security feature related to the Telephone User Interface (TUI). This setting is configured on the "TUI Options" tab of the mailbox, not the "Synchronization Options" tab.

1. Avaya Aura® Messaging Documentation:

Document: Administering Avaya Aura® Messaging, Release 7.1 (December 2017)

Section/Page: Chapter 6: Administering mailboxes, "Mailbox - Synchronization Options tab", Page 161. This section details the configuration fields for Message Synchronization, explicitly mentioning IMAP as a server type option.

Section/Page: Chapter 6: Administering mailboxes, "Mailbox - TUI Options tab", Page 158. This section shows that "Voice Verification" is a configurable parameter under the TUI login settings, confirming that option D is incorrect.

Official Avaya documentation for Avaya IX™ Messaging release 10.8 specifies that the customer is responsible for providing and licensing the required Microsoft Windows Server operating system; it is not included in the software bundle. The documentation also explicitly recommends that the software be installed on dedicated servers for performance and stability. For high-availability configurations involving multiple servers, there is a critical warning that logging into any server before the initial database synchronization has finished will cause database corruption, which prevents all subsequent logins on all servers in the configuration.

A. The customer must supply the Microsoft Windows operating system. Avaya does not provide it with the IX™ Messaging software.

E. Avaya best practices and official documentation state that Avaya IX™ Messaging should be installed on dedicated, not shared, servers.

1. Avaya IX™ Messaging, Release 10.8, Installing and Upgrading Avaya IX™ Messaging, Document Number: 16-604203, Issue 5, December 2019.

For Answer C: Page 15, Section "Server requirements", lists the supported Windows Server operating systems that must be installed by the customer before installing Avaya IX™ Messaging. This confirms the OS is not provided.

For Answer B: Page 15, Section "Server requirements", states, "Avaya Messaging should be installed on dedicated servers specifically intended for the purpose."

For Answer D: Page 101, Chapter "Installing the secondary server", contains the following warning: "Important: Do not log in to the servers before the synch is complete. Logging in before the synch is complete will corrupt the database, and prevent all logins on all servers."

2. Avaya IX™ Messaging, Release 10.8.1, Overview and Specification, Document Number: NN43100-107, Issue 1.0, November 2019.

For Answer B: Page 10, Section "Server Requirements", explicitly states: "Avaya Messaging should be installed on dedicated servers specifically intended for the purpose."

For Answer C: Page 10, Section "Server Requirements", details the supported operating systems (e.g., Windows Server 2016 Standard/Datacenter), which are prerequisites for installation, implying they are customer-supplied.

Avaya IX™ Messaging (now Avaya Aura® Messaging) is a native Session Initiation Protocol (SIP) application that operates within the Avaya Aura® core architecture. In this architecture, Avaya Aura® Session Manager serves as the central SIP registrar and routing engine. For the integration of legacy CallPilot Contact Center features, Session Manager is essential to manage the SIP signaling between Avaya Aura® Communication Manager, the Contact Center application, and the Avaya IX™ Messaging platform. It acts as the necessary intermediary for call control and feature invocation, making it a general requirement for the integration to function.

A. A standard deployment of Session Manager is sufficient; no specific or special version is mandated for this particular integration.

C. Joint Interoperability Test Command (JITC) certification is a requirement for specific U.S. Department of Defense deployments and is not a general prerequisite for this feature.

D. Session Manager is a fundamental and mandatory component for all SIP-based application integration and call routing within the Avaya Aura® ecosystem.

1. Avaya Aura® Messaging Implementation and Integration, Release 7.1, December 2016 (Document ID: NN42001-701). Chapter 2: "Architecture," section "Avaya Aura® Messaging in the Avaya Aura® environment," pp. 21-23. The architectural diagrams and descriptions consistently show Session Manager as the central SIP entity through which all call-related signaling to and from the messaging servers is routed.

2. Avaya Aura® Solution Description, November 2018. Chapter: "Avaya Aura® Architecture." This document describes Session Manager as the "core of Avaya Aura®" and the primary "SIP routing hub," establishing its non-negotiable role for integrating SIP applications like Avaya IX™ Messaging.

3. Administering Avaya Aura® Session Manager, Release 8.1, November 2020 (Document ID: NN43001-711). Chapter 1: "Session Manager overview," section "Session Manager in the Avaya Aura® network." This section details Session Manager's role in connecting and managing SIP entities, which is the mechanism used for the CallPilot Contact Center feature integration.

An Avaya Aura® Messaging (AAM) consolidated server provides administrators with the ability to manage all aspects of the messaging system. The administrative interface is logically separated into different functions. Core messaging administration includes managing organizational structures like Company for multi-tenancy, configuring individual user Mailbox Settings (e.g., passwords, greetings, notifications), and defining sets of permissions through Feature Groups. These settings directly control the user experience and available features within the messaging application itself.

B. SIP Settings: This is a system-level server configuration for network integration with Session Manager, not a logical messaging object setting like a mailbox or feature group.

E. PBX Settings: These are configured on the PBX (e.g., Avaya Aura® Communication Manager) itself. The AAM server integrates with the PBX but does not administer its settings.

1. Avaya Aura® Messaging Documentation Library, Administering Avaya Aura® Messaging, Release 7.1, 03-603856, Issue 10, May 2018.

Reference for A, C, D: The Table of Contents explicitly groups these functions under "Part 2: Messaging administration". Chapter 5 is "Administering companies," Chapter 6 is "Administering mailboxes," and Chapter 7 is "Administering feature groups." This shows they are primary, related administrative domains.

Reference for B: The same document places SIP configuration under a separate section, "Part 3: Server administration," in Chapter 15, "Administering SIP configuration," distinguishing it from core messaging object administration.

2. Avaya Aura® Messaging Documentation Library, Overview and Specification for Avaya Aura® Messaging, 03-603855, Issue 13, May 2018.

Reference for E: Section "Avaya Aura® Messaging integration with Communication Manager," page 28, describes the integration points. It details how AAM uses information from the PBX but clarifies that administration of the PBX (stations, trunk groups) is performed on the Communication Manager platform, not from the AAM server.

Avaya IX™ Messaging, which is built upon the architecture of its predecessor Avaya Aura® Messaging and the legacy Octel platform, stores its primary application log files in a specific directory structure. The correct path is :\UC\OL\Logs. The "OL" in the path is a remnant of the original "Octel" product name. This directory contains essential logs for troubleshooting core messaging components, such as the Message Transfer Agent (MTA), Message Store, and other critical services.

A. IX-Messaging Install drive > UC > IX > Logs: This path is incorrect. While IX reflects the product branding, it is not used in the actual directory structure for log file storage.

B. IX-Messaging Install drive > UC > Logs: This path is too generic. The core application logs are located within a specific subdirectory, not directly under the UC folder.

D. IX-Messaging Install drive > UC > Admin > Logs: The Admin folder typically contains files related to the administration interface or tools, not the primary system and application logs.

1. Avaya Aura® Messaging Documentation Library, "Troubleshooting Avaya Aura® Messaging", Release 7.1, NN42050-711, Issue 10, November 2018.

Page 31, Chapter 3: Log files, Section: Messaging log files: "The Messaging application logs are located in the :\UC\OL\Logs directory." This section explicitly confirms the correct path for the core application logs.

2. Avaya Aura® Messaging Documentation Library, "Administering Avaya Aura® Messaging", Release 7.1, NN42050-701, Issue 13, November 2018.

Page 587, Chapter 13: Maintenance, Section: Log files: This chapter discusses various log files used for maintenance and troubleshooting, and references to log collection procedures consistently point to the \UC\OL\Logs directory as the source for critical messaging service logs.

In an Avaya IX™ Messaging High Availability (HA) environment, the licensing model is designed for redundancy and failover. The Primary server holds the master license file, making it the central point for license administration (B). This license is automatically replicated to the Secondary server by the system's HA service. However, the license copy on the Secondary server is temporary; it is time-stamped with a grace period (typically 30 days) and will expire if the Primary server remains inactive beyond this period (D). During a failover, the Secondary server uses its local copy of the license file to provide uninterrupted, full functionality, thus maintaining an individual license instance for operational continuity (A).

C. The license file is replicated by the core system's data synchronization service for High Availability, not specifically by the Mobilink application, which handles mobile device synchronization.

E. The license on the Secondary server is explicitly temporary and time-stamped to act as a grace-period license during failover, not a permanent one.

1. Implementing Avaya IX™ Messaging, Release 10.8 (June 2019), Document Issue 4, Chapter 4: Licensing the system, Page 101.

Supporting B & D: "In a High Availability configuration, you must install the license file on the Primary server. The system automatically copies the license file to the Secondary server. The license file on the Secondary server is time-stamped and expires after 30 days. If the Primary server is down for more than 30 days, you must contact your support organization to obtain a new license file for the Secondary server." This text confirms the Primary server is the holder, and the Secondary's license is time-stamped and expires.

2. Avaya IX™ Messaging High Availability and Disaster Recovery, Release 10.8 (June 2019), Document Issue 2, Chapter 2: High Availability, Section: "Licensing", Page 20.

Supporting A, B, D & contradicting C, E: "You install the license on the Primary server. The system automatically replicates the license to the Secondary server. The license on the Secondary server is valid for 30 days." This confirms the Primary holds the license (B), it is replicated (supporting the concept in A of the secondary maintaining a copy), and it is temporary (D), directly contradicting that it is permanent (E). It also attributes replication to "the system," not Mobil