Your customer would like to allow call attempts only from User Agents (UAs) who have previously registered through the Session Border Controller or who are configured as session agents.
How would you accomplish this?
Click on the arrows to vote for the correct answer
A. B. C. D. E.D.
To allow call attempts only from User Agents (UAs) who have previously registered through the Session Border Controller or who are configured as session agents, you would need to set the "allow-anonymous" parameter appropriately.
Here is a detailed explanation of the answers provided:
A. Navigate to the sip-port configuration element and set the allow-anonymous parameter to agents-only. This option is not correct. The "allow-anonymous" parameter set to "agents-only" would only allow anonymous calls from User Agents that are marked as agents, which is not what the customer wants.
B. Navigate to the session-agent configuration element and set the allow-anonymous parameter to prev-registered. This option is not correct. The "allow-anonymous" parameter set to "prev-registered" would only allow anonymous calls from User Agents that have previously registered through the Session Border Controller, but it does not allow calls from session agents that are configured in the system.
C. Navigate to the sip-port configuration element and set the allow-anonymous parameter to realm-prefix. This option is not correct. The "allow-anonymous" parameter set to "realm-prefix" would only allow anonymous calls from User Agents that have the same domain realm as the Session Border Controller, which is not what the customer wants.
D. Navigate to the sip-port configuration element and set the allow-anonymous parameter to registered. This option is correct. The "allow-anonymous" parameter set to "registered" would only allow anonymous calls from User Agents that have previously registered through the Session Border Controller, and it would also allow calls from session agents that are configured in the system. This option fulfills the customer's requirements.
E. Navigate to the session-agent configuration element and set the allow-anonymous parameter to 403-forbidden. This option is not correct. The "allow-anonymous" parameter set to "403-forbidden" would reject any anonymous call attempts with a "403 Forbidden" response, which is not what the customer wants.
Therefore, the correct answer is D. Navigate to the sip-port configuration element and set the allow-anonymous parameter to registered.