Which two statements regarding the core architecture in the Avaya Aura® 7 solution are true? (Choose two.)

Question

Options

• ASIP trunks can only be configured on Avaya Aura® Session Manager (SM).
• BSIP user Agents register with Avaya Aura® Session Manager (SM).
• CSIP User Agents can register to Avaya Aura® Communication Manager (CM) or Avaya Aura®
• DAvaya Aura® Media Server (AAMS) cannot connect to Avaya Aura® Communication Manager
• EAvaya Aura® Media Server (AAMS) connects directly to Avaya Aura® Communication Manager

• A
  3% (1)
• B
  95% (36)
• C
  3% (1)

Explanation

In Avaya Aura 7, Session Manager (SM) is the central SIP registrar - all SIP User Agents (phones, softphones, etc.) register with SM, which then acts as the routing hub for the entire solution. This is the fundamental design principle of the Aura architecture (B is correct). Additionally, Avaya Aura Media Server (AAMS) connects directly to Communication Manager (CM) to provide media processing resources such as conferencing, tone detection, and announcements - CM manages these resources through a direct connection (E is correct).

Why the distractors are wrong:

• A is wrong because SIP trunks can be configured on both SM and CM, not exclusively on SM.
• C is wrong because SIP User Agents register only with SM in the Aura 7 architecture - CM handles H.323 and digital/analog endpoints, not SIP registration.
• D is the direct opposite of the truth - AAMS does connect to CM, making D incorrect.

Memory tip: Think of Session Manager as the "front door" for all SIP devices (they must check in with SM), while AAMS is a "resource pool" that plugs directly into CM's engine. The phrase "SIP = SM, Media = CM" can help you remember the registration and media server relationships quickly.

No community discussion yet for this question.