You are creating an OPTIM trunk between Avaya Aura Session Manager (SM) and Avaya Aura Communication Manager (CM) to separate the SIP traffic for your Advanced SIP Telephone (AST) users. How would…

Question

Options

• AA second link should not be created as OPTIM traffic must be sent down the existing SIP link.
• BSpecify a new Entity Link on the existing CM SIP Entity but using UDP instead of TLS as the
• CCreate an additional SIP Entity, SIP Entity Link and CM Signaling/Trunk Group using an alternate
• DAssign secondary IP addresses for both SM and CM to create a second SIP link between.

• A
  13% (6)
• B
  4% (2)
• C
  76% (35)
• D
  7% (3)

Explanation

Creating a second SIP trunk between SM and CM requires distinct Avaya objects - a new SIP Entity, a new SIP Entity Link, and a new CM Signaling/Trunk Group configured on an alternate port (e.g., 5062 instead of the default 5060/5061). This gives OPTIM traffic its own logical path through the system, completely independent of the regular trunk, which is exactly what the AST separation model requires.

Why the distractors fail:

• A is wrong by design - the entire point of an OPTIM trunk is to separate AST traffic from regular SIP traffic; sharing one link defeats that purpose.
• B is wrong because changing the transport protocol (UDP vs. TLS) on the existing entity only modifies the current trunk; it doesn't create a second, independent signaling path.
• D is wrong because Avaya SM/CM trunk separation is achieved through logical port-based entity configuration, not by assigning secondary IP addresses to the physical servers.

Memory tip: Think of it as building a second road, not a second lane - option C is the only one that actually constructs a complete new path (Entity + Link + Trunk Group on a new port), while the distractors all try to modify or repurpose the existing road.

No community discussion yet for this question.