What is the first thing you should do when you want the Session Border Controller to detect that an endpoint is behind a NAT/firewall device?

Question

Options

• ANavigate to the sip-port configuration element and set the nat-traversal parameter to disabled.
• BNavigate to the sip-interface configuration element and set the nat-traversal parameter to never.
• CNavigate to the sip-interface configuration element and set the nat-traversal parameter to
• DNavigate to the sip-port configuration element and set the nat-traversal parameter to enabled.
• ENavigate to the sip-interface configuration element and set the nat-traversal parameter to

Explanation

It appears the question has formatting issues - the correct answer field is blank, and options C and E have their parameter values cut off. Based on Oracle/Acme Packet SBC documentation, the correct answer is almost certainly C, with the nat-traversal parameter set to always.

Configuring nat-traversal always on the sip-interface element instructs the SBC to always attempt NAT detection and apply traversal techniques (such as latching) for any endpoint communicating through that interface - this is the required first step before the SBC can identify and handle NATted endpoints. Options A and D are wrong because nat-traversal is not a valid or relevant parameter on the sip-port element; NAT behavior is governed at the interface level. Option B is wrong because setting the value to never explicitly disables NAT detection, which is the opposite of what you want. Option E likely contains an insufficient value (such as rport-only), which is a more limited mode that only handles the rport mechanism rather than full NAT detection.

Memory tip: Think "SIP Interface = Always Active" - NAT traversal lives on the sip-interface (not the port), and you set it to always to ensure the SBC actively detects NAT for every endpoint.

No community discussion yet for this question.