The save translation command is a manual administrative action used in Avaya Communication Manager. When an administrator makes changes to the system's configuration (known as translations), these changes are initially applied only to the system's active Random Access Memory (RAM). The save translation command commits these changes from volatile RAM to the system's non-volatile hard drive. This ensures that the new configuration is preserved and will be loaded if the system is rebooted or experiences a power failure.

A. It runs automatically after every SAT command.

This is incorrect. The command must be executed manually by an administrator to prevent the loss of unsaved changes and to control when configuration changes are permanently committed.

B. It writes a copy of the translation data to the FTP Server.

This describes a backup operation, which is performed by a different command, such as backup translations. The save translation command pertains to local storage persistence.

D. It writes a copy of the translation data to RAM memory.

This is incorrect. The translation data being modified already resides in RAM. The purpose of the command is to copy the data from RAM to a persistent storage medium.

1. Avaya Aura® Communication Manager Administrator's Guide (03-300509, Issue 11, November 2013), Chapter 11: Backing up and restoring data, Section: "Saving translations", Page 331. The document states, "When you administer Communication Manager, you change the translations in the Random Access Memory (RAM)... To prevent the loss of data, you must save the translations to the hard disk."

2. Avaya Aura® Communication Manager System Management (03-300510, Issue 10, November 2013), Chapter 4: Server administration and maintenance, Section: "save translations command", Page 128. The command description explicitly states: "Use the save translations command to save the current translations from memory to the hard disk."

The standard and expected behavior for SIP authentication, as implemented by Avaya Aura® Session Manager, follows the RFC 3261 challenge-response mechanism. When a SIP station (User Agent) attempts to register for the first time, it sends a REGISTER request without authentication credentials. The Session Manager, acting as the registrar, challenges this request by responding with a 401 Unauthorized message. This message contains a WWW-Authenticate header with the necessary information (realm and nonce) for the station to build a proper credentialed request. The station then sends a second REGISTER request, this time including an Authorization header with the correct credentials, which then results in a 200 OK if successful.

B. The first registration request is not expected to be successful. It is part of the challenge-response mechanism and is intentionally rejected to prompt the endpoint for credentials.

C. The traceSM utility on Session Manager is a comprehensive diagnostic tool that captures all SIP traffic processed by the server, not just registrations from specific device types like AST.

D. traceSM is used for troubleshooting and analysis; therefore, it displays all SIP messages, including both successful and failed registration attempts, to provide a complete view of the interactions.

1. Avaya Aura® Session Manager Documentation: The troubleshooting guide explicitly shows this sequence. In a sample trace of a successful registration, the first message from the endpoint is a REGISTER, which is immediately followed by a 401 Unauthorized from the Session Manager. The endpoint then sends a second REGISTER with authentication details.

Source: Troubleshooting Avaya Aura® Session Manager, Release 8.1, November 2020, Page 138, "Example of a successful registration trace".

2. IETF RFC 3261 - SIP: Session Initiation Protocol: This foundational document defines the SIP protocol. It specifies that a registrar can challenge a REGISTER request for which it requires authentication by rejecting it with a 401 response.

Source: IETF RFC 3261, Section 10.2.1 "Creating the Initial REGISTER Request" and Section 22.2 "User Agent Authentication".

3. Avaya Aura® Session Manager Administration Guide: The documentation on traceSM confirms its role in capturing all SIP messages for monitoring and troubleshooting, which contradicts the limitations suggested in options C and D.

Source: Administering Avaya Aura® Session Manager, Release 8.1.3, May 2022, Chapter 11: "SIP entity monitoring", Section "Tracing SIP messages with traceSM".

Avaya Aura® Communication Manager (CM) holds active configuration changes, known as translations, in memory. To make these changes persistent so they survive a system restart, they must be written to the server's hard disk. This occurs under two primary circumstances:

1. An administrator explicitly issues the save translations command via the command-line interface (CLI) or System Administration Terminal (SAT). This is the standard manual procedure to commit configuration changes.

2. During a graceful system shutdown or reboot, CM automatically performs a save operation to prevent the loss of any unsaved changes. This ensures data integrity during planned maintenance or restarts.

A. by default, after every SAT command

This is incorrect. Saving to the hard disk after every single command would cause significant performance overhead and is not the standard operational behavior of Communication Manager.

B. automatically every day during CM’s Scheduled Maintenance

This is incorrect. Scheduled maintenance typically runs a backup, which copies the already-saved translation files from the disk to a separate backup location, not saves the live in-memory translations to the disk.

E. automatically during Avaya Aura System Manager (SMGR) synchronization

This is incorrect. While changes synchronized from SMGR must be saved on the CM, this is a result of an external management action, not a fundamental save circumstance of the CM itself. The core mechanisms are the explicit command and system shutdown.

1. Avaya Aura® Communication Manager Administrator Guide (03-300509, Issue 11, November 2018)

Page 118, Section: Saving translations: "Use the save translations command to save the recent translation changes to the hard disk of the active server. Avaya recommends that you save translations after you make a number of translation changes." This directly supports option C.

2. Maintenance Commands for Avaya Aura® Communication Manager, Branch Gateways and Servers (03-300431, Issue 13, November 2018)

Page 1015, Command: save translations: The command description states its purpose is to "Save the translation database from memory to the hard disk." This further validates option C.

Page 987, Command: reset system: The description for a graceful reboot (reset system 4) implies a save operation to ensure a clean restart. The general best practice for any system shutdown is to save the current state, which CM follows during a controlled reboot process. This supports the principle behind option D.

3. Avaya Aura® Communication Manager Server Backup and Restore Guide (03-300433, Issue 9, November 2018)

Page 13, Section: Backup overview: This document describes the backup process as copying specific data sets, including the "xln" (translations) data, from the server's hard drive to a backup destination. This differentiates the backup function from the save translations function, proving option B is incorrect.

The administration of Avaya Aura® Communication Manager (CM) is primarily conducted through two officially sanctioned interfaces. The first is the Avaya Aura® System Manager (SMGR), which offers a centralized, web-based graphical user interface (GUI) for managing various Aura components, including CM endpoints. The second is the System Administration Terminal (SAT), a comprehensive command-line interface (CLI) that allows for direct and granular control over the CM configuration. The SAT is typically accessed via a secure shell (SSH) session to the CM server. Both SMGR and the SAT provide full capabilities to add, change, and remove H.323 endpoints.

B. Avaya Aura Device Services (AADS): This component is designed for managing SIP-based endpoints, particularly for dynamic configuration, firmware downloads, and contact services, not for provisioning H.323 stations within Communication Manager.

C. Linux Command Line at CM Server: The underlying Linux shell is used for server-level operating system tasks, such as file management, patching, and diagnostics, not for application-level administration of Communication Manager features like stations.

E. SMI Web-Interface at CM Server: The Service and Maintenance Interface (SMI) is a web interface on the CM server intended for maintenance tasks like backups, reboots, and software updates, not for routine endpoint administration.

1. Avaya Aura® Communication Manager Documentation, "Administering Avaya Aura® Communication Manager," (03-300509), Issue 13, November 2017.

Page 29, Section: "Communication Manager administration": This section explicitly states, "You can administer Communication Manager by using the following interfaces: • System Manager • System Administration Terminal (SAT)". This directly supports options D and A as the two primary administration interfaces.

2. Avaya Aura® System Manager Documentation, "Administering Avaya Aura® System Manager for Release 8.1.3," (NN43001-701), Issue 1.0, November 2020.

Page 439, Chapter: "Managing Communication Manager endpoints": This chapter details the procedure for using the System Manager GUI to "add, edit, duplicate, and delete Communication Manager endpoints," confirming that SMGR is a correct interface for the task.

3. Avaya Aura® Communication Manager Documentation, "Maintenance for Avaya Aura® Communication Manager...," (03-603578), Issue 1.0, November 2019.

Page 19, Section: "Communication Manager server web interface": This document describes the SMI web interface and its functions, which are centered on server maintenance and troubleshooting. While it provides a link to a web-based SAT (GEDI), its primary purpose is not endpoint administration, making it a less correct answer than the direct SAT interface.

Starting with Avaya Aura® release 10.1, Communication Manager (CM) requires a valid identity certificate for secure communications. The system provides flexibility to align with diverse enterprise security policies. Administrators can either use the Avaya Aura® System Manager as a Certificate Authority (CA) to generate and sign the CM identity certificate or import a certificate signed by a trusted third-party CA. This dual support ensures that CM can integrate seamlessly into environments with an existing Public Key Infrastructure (PKI) or use the built-in Avaya security framework.

B. This is incorrect. While using a System Manager-signed certificate is a valid option, Communication Manager is not restricted to it and fully supports certificates from third-party CAs.

C. This is incorrect. The validity period of an identity certificate is determined by the issuing Certificate Authority's policy and is not fixed at one year for Communication Manager.

D. This is incorrect. Communication Manager is not limited to only third-party certificates; it also fully supports the use of identity certificates signed by the Avaya Aura® System Manager.

1. Avaya Aura® Communication Manager Documentation Library, Release 10.1, "Administering Avaya Aura® Communication Manager", January 2023.

Section: Security > Managing certificates

Content: The documentation explicitly states, "Communication Manager uses identity certificates to establish its identity to other entities. You can use either a System Manager-signed certificate or a third-party CA-signed certificate." This directly supports the correctness of option A and refutes options B and D.

2. Avaya Aura® System Manager Documentation Library, Release 10.1, "Administering Avaya Aura® System Manager", January 2023.

Section: Security > Certificate Authority > Configuring the Certificate Authority

Content: This document details the configuration of System Manager's internal CA, including the default certificate validity period, which is 730 days (2 years), not 1 year. This refutes the claim made in option C.

3. Avaya Aura® Solution Description, Release 10.1, "Avaya Aura® Overview and Specification", January 2023.

Section: Security Architecture > Certificate Management

Content: This document outlines the overall security architecture for Avaya Aura®, emphasizing the requirement for PKI integration and support for both internal (System Manager) and external (third-party) Certificate Authorities for core components like Communication Manager.