Which roles must an Avaya Aura® Session Manager fill to support SIP endpoints? (Choose two)

Question

Options

• AMedia resource function
• BRegistrar and proxy server
• CPolicy server
• DBorder element

• A
  12% (6)
• B
  84% (41)
• D
  4% (2)

Explanation

Avaya Aura® Session Manager must act as a SIP Registrar so that SIP endpoints can register their location/availability, and as a SIP Proxy Server to route SIP requests on behalf of those endpoints - both core roles defined in RFC 3261. It also enforces policy (communication profiles, dial plans, routing rules configured in System Manager), qualifying it as a policy server, making B and C correct.

Option A (Media resource function) is wrong because Session Manager handles SIP signaling only - media processing functions like conferencing, transcoding, and tone detection belong to dedicated media servers, not SM.

Option D (Border element) is wrong because the border/edge role belongs to the Avaya Session Border Controller for Enterprise (SBCE), a separate product that sits at the network perimeter - Session Manager lives inside the enterprise core.

Memory tip: Think of Session Manager as the "RPP hub" - Registrar, Proxy, Policy. It's the internal SIP traffic cop: it knows who's registered, routes their calls, and enforces the rules. Anything about media or network edges points away from SM.

No community discussion yet for this question.