72301X Avaya Aura Communication Applications Support Certified Exam Questions and Answers

IM is sent/from to a Remote Worker via Session Manager and SBCE; Presence notifications are relayed from Breeze to Remote Worker via SBCE but without passing through Session Manager.

Presence and IM is delivered to SIP Remote Workers without passing through Session Manager.

Presence notifications and IM are sent to a Remote Worker via Session Manager and Avaya SBCE.

Presence notifications are sent to a Remote Worker via Session Manager and SBCE; IM is relayed from Breeze to Remote Worker via SBCE but without passing through Session Manager.

Using an in-directly routed H.323 trunk group between CM and AAM via Session Manager

Using a direct H323 trunk group between CM and AAM.

Using SIP via Avaya Aura® Session Manager (SM), AAM is built as a user with a Communication Profile

and registry routing forwards the calls to AAM.

Using SIP via Avaya Aura® Session Manager (SM), a dial pattern or regular expression forwards the call to AAM.

ICE

SRTCP

TURN

HTTPS

STUN

Change clid-numbering 0 SAT form to send the correct CLID.

Using AAM web GUI access Administration > Messaging > Telephone Integration, write a caller ID

modification rule to correct the incoming CLID format.

In Session Manager, configure a DigitConversionAdapter with ‘fromto=true’ to update the ‘Form’ header as well as the P-asserted-identity, and link it to the AAM SIP Entity.

Having identified the trunk group from Avaya Aura® Communication Manager (CM) to AMM is public,

change public-unknown-numbering 0 SAT form, to send the correct CLID.

traceTURN, traceSTUN, and traceHTTP

traceWEB and traceSM

traceSTUN, traceTURN, and traceCE

traceHTTP and traceCE

Split horizon DNS with FQDN is recommended to allow smartphones to seamlessly register with Avaya

Session Border Controller for Enterprise, when out of range of Wi-Fi over the Mobile network, and register

direct with Avaya Aura® Session Manager when connected to a corporate Wi-Fi.

You must use HTTPS as opposed to HTTP when web browsing to the Element Management System

(EMS).

When ignoring traffic considerations, it is possible to co-reside WebRTC, Remote Worker, and SIP

Trunking applications on the same Avaya Session Border Controller for Enterprise (SBCE).

Remote Worker and SIP Trunking can use the same IP addresses for both services.

You can SSH to Avaya Session Border Controller for Enterprise using PuTTY with standard port 22.

Identify a patch to fix the problem.

Update the Knowledge Management database.

Implement a solution.

Determine the cause.

The certificate is retrieved from SMGR automatically when AAM services are started.

The certificate needs to be manually installed.

The certificate installs as a result of running ‘initTM –f’.

The certificate installs as a result of the enrollment process.

theCallTracecommand on the Session Manager Command Line Interface

thetraceSMcommand on the Session Manager Command Line Interface

Trace Viewer in the System Manager GUI

theList tracecommand on the Session Manager Command Line Interface

Pcap

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.

traceSBC can only be used to view PPM messages if they are transported using HTTP instead HTTPS

traceSBC can trace SIP trunk calls but not Remote Workers calls at the same time

traceSBC command can be used from CLI ipsec user

traceSBC can be used to view STUN/TURN messages.

traceSBC parses Avaya SBCE log files and displays SIP and PPM messages, you can use the tool even in case of TLS and HTTPS