The Session Border Controller is not routing calls to a specific SIP endpoint from the backbone realm to the access realm in an Access-Backbone architecture. How can you troubleshoot this routing issue?
A.
by running the notify berpd force command
B.
by running the show sipd endpoint-ip <phone number> command
C.
by checking the sip-manipulation configuration element used for routing from the backbone realm to the access realm
D.
by checking the registration-cache configuration element used for routing from the access realm to the backbone realm
E.
by checking the local-policy configuration element used for routing from the access realm to the backbone realm
Wrong IMO. It says that is not routing calls to a SPECIFIC endpoint, so we should assume other endpoints are working. If so, registration-caching is surely enabled in access realm (so D doesn’t apply). E is wrong because policy is for routing traffic access -> backbone (the question says it’s not working backbone -> access), for me is wrong. Correct answer is B IMO, that command shows registration status of a SPECIFIC endpoint, to me is the best fit answer.
upvoted 6 times
...
...
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
2D
10 months, 2 weeks agoIamrandom
1 month, 3 weeks ago