Which statement about making Avaya Aura Communication Manager (CM) work successfully as a feature server for CM SIP Endpoints (AST Endpoints) is true?

Question

Options

• ACM does not support SIP Endpoints in Avaya Aura 10.1.
• BCM must be added as an Application in an Application Sequence.
• CEndpoints must register directly with CM.
• DCM must be added as an Application Sequence assigned to the CM Managed Element.

• A
  11% (4)
• B
  6% (2)
• C
  3% (1)
• D
  80% (28)

Explanation

In Avaya Aura, Session Manager acts as the SIP proxy and registration point - CM functions as a feature server behind it. For CM to provide telephony features to AST/SIP endpoints, an Application Sequence containing CM must be created and explicitly assigned to the CM Managed Element in System Manager; this is what tells Session Manager to invoke CM's features for those endpoints.

Why the distractors are wrong:

• A is false - CM has supported SIP (AST) endpoints across Avaya Aura releases, including 10.1.
• B is incomplete - CM does get added as an Application inside an Application Sequence, but that alone is not enough; the sequence must also be assigned to the CM Managed Element, making D the more precise and complete answer.
• C is backwards - AST endpoints register with Session Manager, not directly with CM; CM only provides the feature layer in the background.

Memory tip: Think of it as a two-step bundle - "Sequence + Assignment." You can't just build the Application Sequence; you must assign it to the CM Managed Element. If you remember "assign the sequence to the element," you'll land on D every time.

No community discussion yet for this question.