71300X Online Practice Questions and Answers

Correct Answer: A

SBC states: References: Avaya Aura Session Border Controller Enterprise Implementation and Maintenance (2012), page 201

Correct Answer: A

Commission the SBC--SBC Configuration 3. Click the Toggle link for both the A1 and the B1 interfaces. The Administrative Status for both A1 and B1 changes to Enabled:

References: Avaya Aura Session Border Controller Enterprise Implementation and Maintenance (2012), page 203

Correct Answer: A

Two types of flows need to be defined for the proper routing of SIP messages from and to the endpoints

and the SIP server.

Example, Server Flows:

References: Avaya Aura Session Border Controller Enterprise Implementation and Maintenance (2012), page 540, 546

Correct Answer: C

Stat the tue Tracing Tools, TraceSM, SSH to Session Manager

1. Launch PuTTY (or similar client application) for a SSH session to Session Manager (port 22). Use the

Session Manager IP Address (172.16.255.107).

2. Log in.

3. At the Session Manager command line type traceSM 瓁 and press Enter. Note: The traceSM tool shows

the SIP call flow in Session Manager.

It gives insight into Session Manager's decisions.

Benefit: can filter certain types of SIP messages

References: Avaya Aura Session Border Controller Enterprise Implementation and Maintenance (2012),

page 485

Correct Answer: C

Configuring Messaging in the normal operational mode Before you begin

*

Add both the primary and secondary servers as Trusted Servers in the Messaging system.

*

Update the Login, Password, and Confirm Password fields with the appropriate trusted server defined on the Messaging system. Procedure

1. Log on to the Messaging system that System Manager manages.2. Add the secondary System Manager server as Trusted Servers in the Messaging system.

3. Log on to the secondary System Manager server.

4. On the System Manager web console, click Services > Inventory.

5. In the left navigation pane, click Manage Elements.

6. On the Manage Elements page, select the Messaging system that you want to change to the secondary System Manager server.

7. Click Edit.

8. On the Attributes tab, fill the Login, Password, and Confirm Password fields with the corresponding name and password of the Messaging trusted server.

9. Click Commit.

10. Click Inventory > Synchronization > Messaging System, and select the required Messaging element.

11. Click Now. The secondary System Manager server retrieves all data from Messaging and is now ready to administer and manage Messaging. References: Administering Avaya Aura System Manager for Release 6.3.11 and later, Release 6.3, Issue 8 (November 2016), page 104 https://downloads.avaya.com/css/P8/documents/101008185

Correct Answer: B

Use port 22, not port 21 or port 222. Log in as craft and use the default password. References: Application Enablement Services Installation and Upgrade Guide for a Bundled Server Release 4.0, page 29 https://downloads.avaya.com/elmodocs2/AES/4.0/02_300356_4.pdf

Correct Answer: D

Creating the Avaya Aura Media Server Routing Pattern Procedure

1.

On System Manager, click Elements > Routing > Routing Policies.

2.

Click New.

3.

Type a Name for the Routing Policy.

4.

From the SIP Entity as Destination field, click Select.

5.

Select the Avaya Aura

Media Server SIP Entity that you created.

Select the Local Host Name FQDN SIP Entity if you are using High Availability for the Avaya Aura Media

Server routing.

6.

Click Commit.

7.

Navigate to Home > Elements > Routing > Regular Expressions and click New.

8.

In the Pattern field, type ce-msml@.* This sip-domain value must match:

?The SIP domain that you entered in the Home>; Elements>; Routing>; Domains page. ?The default SIP

domain that you entered on the Avaya BreezeTM Cluster Administration page.

9.

Click Commit https://downloads.avaya.com/css/P8/documents/101014426 References: Deploying Avaya Breeze, Release 3.1, (September 2016), page 55

Correct Answer: C

Correct Answer: B

Verifying that Presence Services snap-in is ready to support Presence and IM Procedure

1.

On the System Manager web console, navigate to Elements > Avaya Breeze> Cluster Administration.

2.

Locate the row for the cluster, and verify that:

* The Cluster Profile field shows Core Platform.

etc.

References: Avaya Aura Presence Services Snap-in Reference. Release 7.0.1 (December 2016), page

https://downloads.avaya.com/css/P8/documents/101013646

Correct Answer: B

See step 8 and step 9 below.

Repairing replication between Avaya BreezeTM 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 BreezeTM.

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 BreezeTM and Presence Services are displayed.

6.

Select Avaya BreezeTM, and click Repair.

7.

After 2?5 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 BreezeTM and Presence Services must be re-administered, because System Manager Enrollment Password was configured during deployment of Avaya BreezeTM. b. Open an SSH session to the Avaya BreezeTM 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 https://downloads.avaya.com/css/P8/documents/101013646