Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  2. Home
  3. Exams
  4. Avaya
  5. 72301X

Avaya 72301X Exam Questions
Avaya Aura Communication Applications Support Certified Exam (Page 11 )

Updated On: 16-Apr-2026
Page 4 of 20
PDF with 95 Questions

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?

  1. 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.
  2. In Avaya Session Border Controller for Enterprise (SBCE) GUI, navigate to Global Profiles > Server Configuration > Edit the Session Manager server entry to set "Overwrite Domain Name."
  3. 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.
  4. 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



A customer reports that remote worker users cannot see their feature buttons. Their Avaya Session Border Controller for Enterprise (SBCE) was recently damaged and replaced due to a lightning strike. After doing some troubleshooting, support was able to see that PPM was misconfigured in the SBCE. Which tool was used, and which symptoms were visible that pointed to this issue?

  1. List trace; PPM requests were going to Avaya Aura® Session Manager instead of the PPM server
  2. traceSM; SIP requests were going to Avaya Aura® Session Manager instead of SBCE
  3. traceHTTP; all HTTP requests were going to SBCE instead of Avaya Aura® Communication Manager
  4. traceSBC with PPM debugging enabled; PPM requests were seen to be going to the Utility Server instead of Session Manager

Answer(s): D

Explanation:

https://documentation.avaya.com/es-LA/bundle/AdministeringAvayaSBCE_r7.2.2/page/TraceSBC- Command.html



Which tool has an option to debug the TLS handshake between the server and the client?

  1. SIP Trace Config and SIP Trace Viewer
  2. List trace tac 701
  3. traceSM
  4. List trace tac 701/tls

Answer(s): C



Callers hear a fast busy when they dial into Avaya Aura® Messaging (AAM) to retrieve their voicemail messages. After troubleshooting you discover that someone has left trunks in busy-out state on AAM.
How would you restore the trunks to in-service status?

  1. Using AAM web GUI access Administration > Messaging > Diagnostics > Network Connection, and then click on the Release All Trunks button.
  2. SSH to AAM, and execute the release trunks all command.
  3. SSH to AAM, and execute the release trunk command.
  4. Using AAM web GUI access Administration > Messaging > Telephony Diagnostics > Release, type `all' in the Equipment Number field, and then click on the Release button.

Answer(s): D



A customer reports that their Avaya Aura® Communication Manager (CM) enabled SIP telephones (AST) can only see the effect of their telephone being Call Forwarded after they log off and log on again. Also stopping the call forward feature does not show until their endpoint is logged off and logged on again.
What is the cause of the problem?

  1. A coverage path has not been setup.
  2. The Call Forwarding feature has not been assigned to a button.
  3. Data Privacy is enabled in the station's Class of Service.
  4. An entry is missing in the private-numbering System Administration Terminal (SAT) form.

Answer(s): C



Viewing page 11 of 20
Viewing questions 51 - 55 out of 95 questions



Post your Comments and Discuss Avaya 72301X exam dumps with other Community members:

72301X Exam Discussions & Posts

AI Tutor AI Tutor 👋 I’m here to help!