Refer to the Exhibits. The SIP call flow made from an Avaya Communicator Remote Worker is on the left, and the call flow made from a 96X1 telephone Remote Worker is on the right. When comparing the…

Question

Exhibits

Options

• AThere is no difference between the two.
• BAvaya Aura® Communication Manager does full call model processing for the SIP-to-SIP call flow
• CThe Communicator does not register to Avaya Aura® Session Manager.
• DThe Communicator registers to Avaya Session Border Controller for Enterprise (SBCE).

• A
  77% (24)
• B
  6% (2)
• C
  3% (1)
• D
  13% (4)

Explanation

Both Avaya Communicator and the 96X1 telephone, when operating as Remote Workers, follow identical SIP call flows: each registers through the Avaya Session Border Controller for Enterprise (SBCE) to reach Avaya Aura Session Manager, making the two paths functionally indistinguishable.

Why the distractors fail:

• B is wrong because Communication Manager does not perform full call model processing for a SIP-to-SIP remote worker call - Session Manager handles SIP routing directly, bypassing CM's full feature processing in this path.
• C is wrong because Avaya Communicator does register to Session Manager; that is its SIP registrar in the Aura architecture.
• D is wrong because both endpoints register to Session Manager - the SBCE is a traversal/security element they pass through, not the SIP registrar they register to.

Memory tip: Think "same road, different car" - whether the remote worker is a softphone (Communicator) or a desk phone (96X1), they both take the exact same highway: SBCE → Session Manager. The vehicle type doesn't change the route.

No community discussion yet for this question.