QUESTION: 17

You are troubleshooting an IM and Presence problem, and discover all application processes are not running on the Avaya Breeze TM platform.
How can the application processes be started?

SSH to Avaya Breeze TM, and execute the start a command.
SSH to Avaya Breeze TM, and execute the service presence start command.
Accept Service on the cluster using Avaya Aura® System Manager web GUI.
SSH to Avaya Breeze TM, and execute the service ps start command.

Answer(s): C

Reveal Solution Next Question

QUESTION: 18

Which statement about Network Routing Policies in Avaya Aura® Session Manager (SM) is true?

A dial pattern and routing policy are necessary in SM to call from an H323 device to a Basic/Native SIP
device (without an Avaya Aura® Communication Manager profile).
A dial pattern and routing policy are necessary in SM to call from a Basic/Native SIP device (without a CM profile) to an H323 device on Avaya Aura® Communication Manager (CM).
A dial pattern and routing policy are necessary in SM to call from an H323 device to an AST device on the same Avaya Aura® Communication Manager (CM).
A dial pattern and routing policy are necessary in SM to call from an AST device to an H323 device on the same Avaya Aura® Communication Manager (CM).

Answer(s): A

Reveal Solution Next Question

Refer to the exhibit.

Refer to the exhibit.
Avaya Tier 3 support receives a case escalated by Tier 2 where the customer cannot receive incoming calls, but can make calls out successfully. The trace shows that the incoming calls arrive at the Avaya Session Border Controller for Enterprise (SBCE) but fail to get routed into the customer enterprise network.
Based on this information, what is and is not working?

The local area network, Avaya Aura® Communication Manager, and Avaya Aura® Session Manager are working. SBCE is partially working, but routing may be incorrect.
The local area network, Avaya Aura® Communication Manager, and Avaya Aura® Session Manager are working. The public network is not working.
The local area network, Avaya Aura® Communication Manager, and Avaya Aura® Session Manager are working. SBCE is not working.
The local area network and Avaya Aura® Session Manager are working. Avaya Aura® Communication
Manager is not working.

Answer(s): D

Reveal Solution Next Question

QUESTION: 20

Incoming SIP Trunking calls from Service Provider to Session Manager are failing because Avaya Session Border Controller for Enterprise (SBCE) is not sending a domain name in the TO, FROM and REQUEST headers.
What needs to be changed in SBCE to make this happen?

In SBCE GUI, navigate to Global Profiles > Routing. Edit the Session Manager Routing Profile to link to a URI Group, which has the To, From and Request Headers and Replace Action set to Overwrite with
domain name.
In SBCE GUI, navigate to Global Profiles > Server Configuration. Edit the Session Manager server entry to set "Overwrite Domain Name".
In SBCE GUI, navigate to Global Profiles > Topology Hiding. Edit the SessionManager_TH to change the To, From and Request Headers Replace Action, to Overwrite with domain name.
In SBCE GUI, navigate to Device Specific Settings > Endpoint Flows > Server Flows. Edit the Session Manager flow to change the End Point Policy Group to default-low.

Answer(s): C

Reveal Solution Next Question

Free 72300X Exam Braindumps (page: 5)

QUESTION: 17

QUESTION: 18

QUESTION: 19

QUESTION: 20