In Avaya Aura System Manager, how is Avaya Aura Messaging (AAM) added to the list of Managed Elements?
In System Manager, element installation sets up the trust between System Manager and its managed elements. . Similarly, UCM has a trust management process to set up the trust between UCM and its managed elements. To enable managed elements of UCM to be in the same trust domain as the System Manager managed elements, you must import the UCM Certificate Authority (CA) certificate to the System Manager managed element's trusted certificate list.
Note: To force a re-initialization of trust management
1. Ensure the enrollment password in the System Manager Security -> Enrollment Password screen is valid and set. Make note of this password as it will be needed when running the trust management initialization command.
2. Log into the Session Manager virtual machine IP address with an ssh client as the craft or customer account login
3. Execute the following shell command once at the shell prompt:
$ initTM --f
This will prompt you for the enrollment password and then initialize trust management and the database replication service of the Session Manager.
References: Administering Avaya Aura System Manager for Release 6.3.11 and later, Release 6.3, Issue 8, November 2016, page 1073
https://downloads.avaya.com/css/P8/documents/101008185
https://downloads.avaya.com/css/P8/documents/100161692
An Avaya Aura Messaging (AAM) server intended to store Voice Messages in Avaya Message Store Mode, and you are configuring that server for integration with an Avaya Aura Core.
In Messaging Administration > Server Settings > Server Role/AxC Address, which Server Role must be chosen at the ''Roles for this server'' field?
In Avaya Aura Messaging (AAM) 6.3, how many Call Answering Ports can one Application Server support?
The Call Answer Ports range is 2--100.
References: Administering Avaya Aura Messaging, page 34
https://downloads.avaya.com/css/P8/documents/100112131
You need to connect Avaya Breeze platform that is hosting Avaya Aura Presence Services Snap-in with Avaya Aura Session Manager (SM).
Which three are needed? (Choose three.)
BD: Administering Entity Link between Presence Services Cluster SIP Entity and Session Manager
Procedure
1. On the System Manager web console, navigate to Elements > Routing > Entity Links.
2. In the Name field, enter a name for Entity Link.
3. In the SIP Entity 1 field, select the Session Manager instance.
4. In the Protocol field, select TLS.
5. In the Port field, type 5062.
Note: Note that this port number cannot be the same as the port number administered in
''Administering Entity Link between Avaya Breeze and Session Manager''.
CD: Administering Entity Link between Avaya Breeze and Session Manager.
About this task
Create an En2tity Link to connect Session Manager to Avaya Breeze. You must administer separate Entity Links for Avaya Breeze servers in order to open SIP listeners on the designated ports.
Session Manager requires a Listen Port with the Listen Port as 5061, Protocol as TLS, and Default Domain as the login domain of endpoint devices. Without this, PPM will fail for SIP endpoints.
References: Avaya Aura Presence Services Snap-in Reference. Release 7.0.1 (December 2016), pages 25-26
https://downloads.avaya.com/css/P8/documents/101013646
What should be verified before running the initTM --f command on the Command Line Interface of Avaya Breeze platform (formerly known as Engagement Development Platform (EDP))?
See step 8 and step 9 below.
Repairing replication between Avaya Breeze and System Manager
Procedure
1. On the System Manager web console, navigate to Services > Replication.
2. In Replica Group column, click CollaborationEnvironment_3.1.
3. In Replica Node Host Name column, locate Avaya Breeze.
4. Verify that the status of the Synchronization Status field is green. If not, go to Step 5.
5. If Presence Services Snap-in has been deployed, in the Product column, verify that both Avaya Breeze and Presence Services are displayed.
6. Select Avaya Breeze, and click Repair.
7. After 2--15 minutes, verify that the status of the Synchronization Status field is green. If not, go to Step 8.
8. Verify that Enrollment Password is not expired.
a. Navigate to Services > Security.
b. In the navigation pane, click Certificates > Enrollment Password.
9. If the Enrollment Password is expired:
a. Enter a password, and click Commit.
It is highly recommended that the same password must be used. Otherwise, Avaya
Breeze and Presence Services must be re-administered, because System Manager
Enrollment Password was configured during deployment of Avaya Breeze.
b. Open an SSH session to the Avaya Breeze Management Module IP address as sroot.
c. On the command line interface, enter initTM -f.
d. When prompted for the enrollment password, enter the password that you provided in Step 9a.
e. Repeat Step 1 to Step 6.
References: Avaya Aura Presence Services Snap-in Reference, Release 7.0.1 (December 2016), page 223
https://downloads.avaya.com/css/P8/documents/101013646
