You are configuring access rules in a Session Border Controller Peering architecture.
Which configuration step is required to allow access from any User Agent (UA)?
Click on the arrows to vote for the correct answer
A. B. C. D. E.A.
In a Session Border Controller (SBC) peering architecture, access rules need to be configured to allow traffic from User Agents (UAs) to flow through the SBC. If you want to allow access from any UA, then you need to configure the SBC to accept anonymous traffic.
The configuration step required to allow access from any UA is to navigate to the sip-port configuration element and set the allow-anonymous parameter to all (option A).
The sip-port configuration element defines the listening ports on which the SBC accepts SIP traffic. The allow-anonymous parameter specifies whether or not the SBC should accept anonymous SIP traffic. When set to all, the SBC will accept SIP traffic from any UA, regardless of whether or not it is authenticated.
Option B, which suggests navigating to the realm-config configuration element and setting the addr-prefix parameter to the IP subnet of your trusted UA, is incorrect because it restricts access to only UAs within a specific IP subnet.
Option C, which suggests navigating to the sip-port configuration element and setting the allow-anonymous parameter to address-prefix, is incorrect because it allows anonymous SIP traffic only from UAs within a specific IP subnet.
Option D, which suggests navigating to the session-agent configuration element and setting the ip-address parameter to the IP subnet of your trusted UA, is incorrect because it specifies the IP address of a specific UA rather than allowing anonymous traffic from any UA.
Option E, which suggests navigating to the sip-port configuration element and setting the allow-anonymous parameter to agents-only, is incorrect because it restricts access to only UAs that are specifically identified as agents.