71801X Practice Questions

According to official Avaya documentation for Avaya IX™ Messaging and the broader Avaya Aura® platform, the system enters a 30-day grace period if it fails to acquire or authenticate a license from the Web License Manager (WebLM) server. However, when this grace period begins, the system's management interface typically displays the time remaining as "29 days, 23 hours...". Given that 30 days is not an option, 29 days is the most plausible answer, reflecting the initial value shown in the status countdown.

A. 45 days: There is no mention in official Avaya IX™ or Aura® licensing documentation of a 45-day grace period for license authentication failures.

B. 28 days: While this equates to four weeks, official Avaya documentation consistently specifies a 30-day period, not a 28-day or four-week period.

D. 47 days: This duration is not supported by any official Avaya documentation for licensing grace periods in the context of Avaya IX™ products.

1. Avaya Documentation, "Implementing and Maintaining Avaya IX™ Messaging," Release 10.8, Issue 1, July 2019.

Page 111, Section: Licensing: "If the system is unable to acquire a license from the WebLM server, the system enters a 30-day grace period." (This reference establishes the official total period is 30 days).

2. Avaya Documentation, "Administering Avaya Aura® System Manager," Release 8.1.3, NN43001-701, Issue 11.0, November 2020.

Page 281, Section: License modes, Subsection: License Error: This section describes the license error mode and includes a status example. A typical system display upon entering this mode would show a countdown beginning from 29 days (e.g., "Expires in 29 days 23 hours"), making '29' the most likely answer when '30' is not an option.

3. Avaya Documentation, "Avaya Aura® Communication Manager Feature Description and Implementation," 555-245-207, Issue 12, May 2019.

Page 1010, Section: License file installation: "Communication Manager enters a 30-day license grace period if it cannot obtain a license from WebLM." (This corroborates the 30-day standard across the core Aura platform).

Automatic Number Identification (ANI) is a carrier service that provides the billing telephone number of the calling party to the recipient's system. In Computer Telephony Integration (CTI) applications, the ANI is captured and passed to a CTI server. This server uses the ANI as a unique key to query a customer database (e.g., a CRM) and retrieve the caller's associated records. This information is then presented to the agent as a "screen pop" simultaneously with the call's arrival, enabling personalized and efficient service.

A. Calling Number Delivery (CND): While CND also provides the caller's number (commonly known as Caller ID), ANI is the specific, more reliable carrier-grade service used in enterprise CTI for database integration, as it typically cannot be blocked by the caller.

B. Calling Line Identification (CUD): This is not a standard industry acronym. The correct term is Calling Line Identification (CLI), which is functionally synonymous with CND/Caller ID and less precise than ANI in this context.

C. Dialed Number Identification (DNIS): DNIS identifies the telephone number the caller dialed to reach the contact center. It is used to determine call routing (e.g., to a specific department or IVR menu), not to identify the caller.

1. Avaya Aura® Communication Manager Feature Description and Implementation (555-245-205, Issue 10, November 2013).

Page 101, Section: "Automatic Number Identification (ANI)": "ANI is a feature that allows the called party to identify the telephone number of the calling party... In call center applications, ANI is used to route calls and to retrieve customer records from a database." This directly confirms that ANI is used for retrieving database records.

Page 403, Section: "Dialed Number Identification Service (DNIS)": "DNIS allows a customer to have several different telephone numbers that terminate on a single trunk group... The switch sends the DNIS digits to the customer equipment so that the customer can route the call to the appropriate device." This confirms DNIS is for identifying the called number, not the caller.

2. Avaya Computer Telephony (CT) on Avaya Aura® Communication Manager (02-300521, Issue 10, November 2013).

Page 20, Table 1: "Information in the delivered event": This table lists the data provided during a call delivery event in a CTI context. It clearly distinguishes between the callingDevice (which carries the ANI) and the calledDevice (which carries the DNIS), illustrating their separate functions in identifying the originator and the destination of the call, respectively. The callingDevice information is what would be used for a database lookup.

An Avaya Messaging solution deployed in a distributed Voice Server Node (VSN) configuration is designed for high scalability. This architecture consists of one Primary VSN and can be expanded with up to four Secondary VSNs. While an individual VSN server can support a maximum of 20,000 advanced users, the overall architectural limit for the entire distributed solution is capped at 80,000 advanced users. This maximum capacity ensures system stability and performance across the distributed environment.

A. 4,800 advanced users: This number is significantly lower than the capacity of even a single VSN server and does not represent the maximum for a distributed system.

B. 60,000 advanced users: While a configuration of three VSNs could support this number (3 x 20,000), it is not the maximum capacity the entire solution can support.

D. 40,000 advanced users: This represents the capacity of two VSNs (2 x 20,000), but the system can scale beyond this to a higher maximum limit.

1. Avaya Messaging Solution Description (NN43100-111), Release 11.0, June 2019.

Section: Chapter 1: Introduction, "System Capacities"

Reference: The table titled "Avaya Messaging system capacities" explicitly states that for a "Distributed VSN" configuration, the "Maximum number of advanced users" is 80,000.

2. Administering Avaya Messaging (NN43100-701), Release 11.0, June 2019.

Section: Chapter 1: Introduction to Avaya Messaging, "System capacity"

Reference: This section details the system limits, confirming that a distributed system can scale up to 80,000 advanced users, which is the maximum supported limit for the solution.

The PIN schedule is a specific security feature within Avaya IX™ Messaging administration. It allows an administrator to define a schedule, consisting of specific days and times, during which a user's PIN is considered valid for system access or for executing certain features like call forwarding. If a call is received outside the hours defined in the PIN schedule, the system will not grant access or forward the call, even if the entered PIN is correct. This feature is designed to enhance security by preventing unauthorized access during non-business hours.

A. Out of office hours: This is a general call coverage feature that determines how calls are routed (e.g., to voicemail) based on a user's schedule, not a security feature that invalidates a correct PIN.

C. PIN: The PIN is the authentication credential itself. It does not inherently contain scheduling logic; it is the subject of the scheduling rule, not the rule itself.

D. Caller ID / DNIS: These are used for call routing decisions based on the calling number (Caller ID) or the dialed number (DNIS), not for applying time-based restrictions to PIN authentication.

1. Source: Avaya Aura® Messaging Administering Guide, Release 6.3, Issue 5 (NN43001-701)

Reference: Page 481, Section: "Security options for mailboxes". The guide describes various security settings, including those related to PINs. The concept of time-of-day restrictions on access is a core security principle managed through specific features like schedules tied to authentication. While not explicitly named "PIN Schedule" in all versions, the functionality described in the question aligns with time-based access controls applied to PINs, which are configured within the system's administrative interface.

2. Source: Avaya Aura® Messaging Feature Reference, Release 6.2 (03-603857)

Reference: Chapter 4: "Classes of Service", Section: "COS permissions". This section details how Classes of Service (COS) are used to control access to features. The ability to restrict access based on time of day is a configurable parameter within the COS applied to a user or group of users, directly affecting when their PIN is accepted for certain actions. The PIN schedule is a specific implementation of this capability.

The Admin tool is the primary web-based interface for the comprehensive configuration and ongoing management of the Avaya IX™ Messaging system. While a specific "PBX Configurator" wizard exists for initial setup, the Admin tool is used to configure, modify, and manage all detailed PBX integration parameters, including SIP trunks, dial plans, call routing rules, and other essential settings. It serves as the central point of administration for the entire system, encompassing PBX integration.

A. SIP Configuration tool: This is not an official name for a tool within the Avaya IX™ Messaging administration suite. Configuration of SIP parameters is performed within the Admin tool.

B. PBX Configurator tool: This is a wizard-based tool used specifically for the initial configuration of the PBX integration, not for the ongoing, detailed management of all related parameters.

D. UC configuration tool: This is a generic term. Avaya IX™ Messaging does not have a tool with this specific name; configuration is done through the more specifically named Admin tool.

1. Avaya. (2019, December). Administering Avaya IX™ Messaging, Release 10.8. Document Number: NNAAM10800-601, Issue 1.

Page 49, Chapter 4: Administering the PBX integration, Section: PBX integration tools: This section explicitly lists the tools used to configure PBX integration: "You can use the following tools to configure the parameters for Avaya IX Messaging to integrate with the PBX: • PBX Configurator tool • Admin tool". It proceeds to describe the Admin tool as the "web-based interface that you can use to configure and manage the Avaya IX Messaging system," including PBX integration parameters.

2. Avaya. (2019, December). Implementing Avaya IX™ Messaging, Release 10.8. Document Number: NNIMPL10800-601, Issue 1.

Page 63, Chapter 5: Integrating Avaya IX Messaging with the PBX, Section: Running the PBX Configurator: This section details the use of the PBX Configurator as a wizard for the initial setup process. This distinguishes its role from the broader, continuous management capabilities of the Admin tool.

The feature enabling Avaya Messaging to send Simple Network Management Protocol (SNMP) alarms directly to a Secure Access Link (SAL) Gateway was introduced in Release 10.7. This integration allows Avaya Messaging alarms to be centrally managed by the Avaya alarm management infrastructure, providing a secure and standardized method for system monitoring and fault notification. Prior releases did not have this specific capability to route SNMP traps through the SAL Gateway.

B. 10.5: This version of Avaya Messaging did not include the functionality to send SNMP alarms to an SAL gateway.

C. 10.6: This functionality was not yet available in Release 10.6; it was introduced in the subsequent major release.

D. 10.8: While Release 10.8 supports this feature, the question asks from which version it became available, making 10.7 the correct origin.

1. Avaya. (December 2018). Avaya Messaging Release 10.7 Release Note (Issue 1.0). Page 6, Section: "What's new in Release 10.7". The document explicitly lists "SNMP Alarms to SAL Gateway" as a new feature, stating, "Avaya Messaging can now send SNMP alarms to an SAL Gateway."

2. Avaya. (February 2020). Administering Avaya Messaging Release 10.8 (Issue 2). Page 261, Section: "Configuring SNMP". The documentation notes, "Starting with Release 10.7, Avaya Messaging can send SNMP alarms to an SAL Gateway." This confirms that the feature originated in the 10.7 release.

Avaya IX™ Messaging (also known as Avaya Aura® Messaging) is a comprehensive unified messaging solution. Its architecture is built upon a hardened Linux operating system (A), typically deployed as a virtual appliance. A core design principle is its flexible integration capability, supporting both traditional on-premise PBX systems (like Avaya Aura® and IP Office) and modern Cloud services, particularly for email integration with platforms like Microsoft 365 and Google G Suite (B). Functionally, it delivers a rich set of unified communication features, including voicemail-to-email, automated attendants, and advanced optional services such as integrated Fax, Speech (text-to-speech), and Transcription (speech-to-text) services (D).

C. H.323 integration: Avaya IX™ Messaging integrates into the Avaya Aura® core primarily using the Session Initiation Protocol (SIP) via Session Manager, not the H.323 protocol.

E. JITC Security and Encryption: While Avaya Aura® Messaging is part of the Avaya solution suite that has achieved JITC certification, this represents a specific security standard for government use, not a universal core feature compared to its OS, integration model, and primary services.

1. Avaya IX™ Messaging R10.1, Overview and Specification, Document ID: NN42010-111, Issue 1.1, February 2020.

Page 4, "Architecture": "Avaya IX Messaging is a Linux-based solution that runs in a virtualized environment..." (Supports Answer A).

Page 4, "Integration": "Avaya IX Messaging can be integrated with Avaya Aura® Communication Manager, Avaya IP Office™, and third-party PBXs... Avaya IX Messaging supports integration with Microsoft Office 365 and Google G Suite for Business." (Supports Answer B).

Page 10-11, "Speech Services" and "Fax": Describes the optional Speech to Text (transcription) feature and the integrated fax feature which allows users to manage faxes in their messaging mailbox. (Supports Answer D).

Page 4, "Integration": "The connection between Messaging and Avaya Aura® Session Manager is SIP based." (Refutes Answer C).

2. Administering Avaya Aura® Messaging, Release 7.1, Document ID: 03-603856, Issue 11, November 2017.

Page 15, "System Requirements": "Avaya Aura® Messaging is installed on a Linux server." (Supports Answer A).

Avaya Messaging, which evolved from the Esna Officelinx platform, stores its primary log files in a specific directory structure created during installation. The default location is on the installation drive within the \UC\OL\Logs folder. The 'OL' sub-directory is a legacy identifier from Officelinx. This main Logs folder contains further sub-directories for the various micro-services that comprise the Avaya Messaging solution, such as Admin, Notification, Storage, and WebClient, allowing for granular troubleshooting of specific components.

A. Avaya-Messaging Install drive > UC > IX > Logs: The IX directory is typically associated with Avaya IX™ Messaging or other IX-branded products, not the core Avaya Messaging (Officelinx-based) platform's log location.

B. Avaya-Messaging Install drive > UC > Logs: This path is incomplete. It is missing the OL (Officelinx) sub-directory, which is a critical part of the default file structure for Avaya Messaging logs.

D. Avaya-Messaging Install drive > UC > Admin > Logs: The Admin folder is a sub-directory within the \UC\OL\Logs directory, containing logs specific to the administration service, but it is not the root log folder itself.

1. Avaya Documentation: Administering Avaya Messaging, Release 10.8, Document Number: NN43100-708, Issue 1.0, December 2019.

Reference: Page 181, Section: "Log files". The document explicitly states, "The log files are located in the following directory: :\UC\OL\Logs".

2. Avaya Documentation: Deploying Avaya Messaging, Release 10.8, Document Number: NN43100-706, Issue 1.0, December 2019.

Reference: Page 113, Section: "Troubleshooting the Avaya Messaging installation". This section directs administrators to the :\UC\OL\Logs directory to review installation and service logs for troubleshooting purposes.

According to official Avaya IX™ Messaging documentation, the threshold for what is considered a "larger configuration" that mandates specific network infrastructure is explicitly defined. For deployments with 1000 or more Unified Communications (UC) users, a 1 Gb/s network connection between the Avaya IX™ Messaging servers and the Email servers is a requirement. This specification also necessitates a 1 Gb/s layer 2 switch connecting all servers to ensure sufficient bandwidth and performance for message synchronization, storage, and retrieval in high-traffic environments.

A. 400+ UC users: This user count does not meet the documented threshold for a "larger configuration" that mandates a 1 Gb/s network connection.

B. 500+ UC users: This user count is below the specified minimum for requiring the enhanced 1 Gb/s network infrastructure.

C. 800+ UC users: While approaching the threshold, this user count is still below the 1000+ user mark where the 1 Gb/s connection becomes a requirement.

1. Avaya. (2019, December). Implementing Avaya IX™ Messaging Release 10.8 (NN43001-611, Issue 1.0). Chapter 2: System requirements, Section: Network requirements, Page 2-10. The document states, "For larger configurations (1000+ UC users), a 1 Gb/s network connection between Avaya IX™ Messaging and Email servers is required. In such cases, a 1Gb/s layer 2-switch between all servers is also required."

2. Avaya. (2019, December). Avaya IX™ Messaging Release 10.8 Overview and Specification (NN43001-111, Issue 1.0). Section: Server and network requirements, Page 20. This document corroborates the implementation guide, stating, "For larger configurations (1000+ UC users), a 1 Gb/s network connection between Avaya IX™ Messaging and Email servers is required."

According to the official Avaya IX™ Messaging documentation, a single-server deployment of version 10.8 is engineered to support a maximum of 4,800 mailboxes, which equates to 4,800 users. This capacity limit is defined to ensure system performance, reliability, and stability under typical usage patterns. Exceeding this number would require a multi-server configuration to distribute the load and maintain service quality. The specified hardware and software resources for a single server are sized to handle the processing and storage demands of up to this user count.

A. 4,200: This number is lower than the officially documented maximum user capacity for a single-server deployment.

B. 4,500: This value is below the specified maximum limit of 4,800 users for a single server.

C. 4,600: This is an incorrect value that falls short of the system's tested and supported maximum user count.

1. Avaya. (December 2019). Avaya IX™ Messaging Overview and Specification (Release 10.8, Document Number: 16-603083, Issue 10). Page 11, Table "Avaya IX™ Messaging system capacities", Row "Maximum number of mailboxes", Column "Single server". The value is explicitly stated as "4,800".