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 because the customer can make outbound calls successfully. If there were issues with these components, outgoing calls would likely also fail. The problem does not appear to be with the public network, as incoming calls reach the Avaya Session Border Controller for Enterprise (SBCE). This indicates that SBCE is at least partially functional. The issue seems to be with the routing configuration within the SBCE, as it fails to route incoming calls into the customer enterprise network. Therefore, the most accurate conclusion is that SBCE is partially working, but its routing may be incorrect.
"A" Correcta Communication Manager is working because can make calls out successfully, SBCE is partially working * Notice that the FROM header is an IP address instead of a domain name = avava.com. CM needs to see domain name. IP address to domain conversion is performed by Topology Hiding.
No clear answer listed. The possible best answer is "A" where the incoming routing profile of the server flow is broken.
I believe A is the right answer
A is the correct answer. D is not correct, since if there was a problem with CM then outgoing calls would also fail.