An Ip (AST0 user 1011111 and H.323 user 1011711 share a common Communication Manager (Evolution) server. Given the following actions: 1. CM will negotiate the codec for the H.323 endpoint based on…

Question

Options

• A4, 2, 1,3
• B4,3,2,1
• C4,2,3,1
• D3,4,2,1

• A
  6% (2)
• B
  3% (1)
• C
  74% (23)
• D
  16% (5)

Explanation

Option C (4→2→3→1) is correct because of two hard constraints built into the action descriptions themselves: Action 3 explicitly states it occurs "after authenticating the SIP user," so Action 2 (authentication) must precede Action 3 (profile check/routing); and codec negotiation with the H.323 endpoint (Action 1) can only happen last, after CM has received the routed request and can complete the call leg. In Avaya Aura Evolution Server architecture, CM is the anchor/feature server that first receives the call (Action 4 initiates the process), then defers to Session Manager for authentication and routing before finalizing the codec negotiation.

Why the distractors fail:

• A (4,2,1,3): Places codec negotiation (1) before SM routes the call back to CM (3) - CM can't negotiate with the H.323 endpoint before it has full routing control.
• B (4,3,2,1): Puts SM routing (3) before authentication (2) - Action 3 explicitly requires authentication to have already occurred.
• D (3,4,2,1): Has SM routing the request (3) before any authentication (2) has taken place - impossible per Action 3's own prerequisite.

Memory tip: Use the phrase "CM starts, SM checks, SM routes, CM closes" - CM anchors both ends of the call (first and last), while Session Manager handles the middle two steps in strict order (authenticate → route).

No community discussion yet for this question.