Which additional area may require trouble-shooting for a remote worker connected to a public network, over an office worker connected to the corporate private network?

Question

Options

• ASystem Parameters ip options in Communication Manager
• BSystem Manager SIP User Communication Profile (remote worker settings)
• CSession Border Controller configuration
• DMedia Server (AAMS) Public Network settings

• A
  2% (1)
• B
  5% (2)
• C
  78% (32)
• D
  15% (6)

Explanation

A Session Border Controller (SBC) sits at the boundary between the public internet and the private corporate network, acting as the gatekeeper for all inbound VoIP/SIP traffic from external sources. A remote worker's calls must traverse this SBC - navigating NAT traversal, encryption, and codec negotiation - creating an entire additional layer that simply doesn't exist for an office worker already inside the private network.

Why the distractors are wrong:

• A (System Parameters IP options in CM): These settings apply system-wide and equally affect both office and remote workers; they're not unique to the public network path.
• B (System Manager SIP User Profile): While remote worker settings exist here, this is a provisioning/configuration step, not an additional troubleshooting area introduced specifically by the public network path itself.
• D (AAMS Public Network settings): The Media Server's settings are configured at the system level and don't represent a distinct troubleshooting scope introduced solely by the remote worker's public network connection.

Memory tip: Think of "Border" literally - a remote worker crosses a border (public → private), so the Border Controller is what you check. Office workers never cross that border, so they never hit SBC issues.

No community discussion yet for this question.