Which statement about Interfaces and IP addresses on an Avaya Session Border Controller for Enterprise (SBCE) used for SIP-Trunking and Remote Worker services is true?

Question

Options

• ASIP Trunking and Remote Worker services can use different IP addresses configured on the
• BSIP-Trunking and Remote Worker services can share the same IP address.
• COnly one IP-address should be configured per interface.
• DSIP-Trunking and Remote Worker services cannot run on the same SBCE.

• A
  93% (25)
• C
  4% (1)
• D
  4% (1)

Explanation

Option A is correct because the Avaya SBCE supports multiple interfaces, each of which can be assigned its own IP address - allowing SIP Trunking (carrier-facing) and Remote Worker (internet-facing) traffic to be logically and securely separated onto distinct IP addresses. This separation is a recommended practice because it improves security segmentation, simplifies traffic policy enforcement, and allows different routing rules per service type.

Option B is wrong because while the SBCE supports both services concurrently, they are designed to use separate IP addresses on separate interfaces - sharing a single IP would defeat the purpose of the SBCE's interface-based traffic isolation architecture.

Option C is wrong because multiple IP addresses can be configured on a single physical interface (using logical/sub-interfaces), so "only one IP per interface" is not an accurate constraint.

Option D is wrong because running both SIP Trunking and Remote Worker on the same SBCE appliance is a core use case and a key selling point of the platform.

Memory tip: Think of the SBCE as a border checkpoint with multiple lanes - SIP Trunking gets one lane (IP) for carrier traffic, Remote Workers get another lane (IP) for internet traffic. Same checkpoint, different gates.

No community discussion yet for this question.