ExamGecko
Search Search Login
Home Home / Avaya / 72301X
Question list
Search
Search

List of questions

Search
Open VPLUS File
Convert VPLUS to PDF

Related questions

After completing Discipline 4, Determining Root Cause, of the 8D Troubleshooting Methodology, what is the next discipline to be completed?
A customer reports that none of their users can IM or see each other’s presence. After troubleshooting you discover that default gateway of the Avaya Breeze ™ SM100 has the wrong IP Address in the configuration. Where would you go to correct this problem?
In which way can you check if the Avaya Aura® Messaging (AAM) server is using the correct certificate?
In which way can you check if the Avaya Session Border Controller (SBC) is using the correct server certificate?
To validate the initial system status of Avaya Breeze ™ with the WebRTC Snap-in, which three components should be checked? (Choose three.)
Refer to the exhibit. In the Cluster Administration screen of a PresenceServices cluster, when you try to change the cluster state to Accept New Service, you receive the error: Servers that are not in License Restricted mode assigned to the cluster are below the Minimum number of required servers. You check that a server has been administered under Breeze > Server Administration which shows green check under License Mode, and a System State of Denying. Which action needs to be taken to solve this problem?
What are two ways to view the ipcs.log file of an Avaya Session Border Controller for Enterprise (SBCE) High Availability (HA) system? (Choose two.)
In Avaya Aura® Messaging (AAM), which Command Line Interface command produces the same output as what is shown on the Process Status Results page in the AAM Web GUI?
Which three statements are true about Avaya Aura® Messaging (AAM)? (Choose three.)
To log on the one-X® Communicator to Avaya Aura® Presence Services server, what do you enter in the IM and Presence / Server field of the one-X® Communicator?

Question 20 - 72301X discussion

Report
Export

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?

A.
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.
Answers
A.
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.
B.
In SBCE GUI, navigate to Global Profiles > Server Configuration. Edit the Session Manager server entry to set “Overwrite Domain Name”.
Answers
B.
In SBCE GUI, navigate to Global Profiles > Server Configuration. Edit the Session Manager server entry to set “Overwrite Domain Name”.
C.
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.
Answers
C.
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.
D.
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.
Answers
D.
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.
Suggested answer: C
Show Answer
asked 16/09/2024
j j
31 questions
PreviousPreviousNextNext
User
Your answer:
0 comments
Sorted by

Leave a comment first

ExamGecko

Copyright @2023 ExamGecko | All right reserved

Mail us: [email protected]
About us
Contact us
Twitter X
Facebook
Medium
Convert VPLUS to PDF
Open VPLUS files Easily and Quickly
Privacy Policy
Disclaimer
Terms