As opposed to a regular SIP trace, what do SIP messages captured using the traceSM with "a=showSM" option display?

Question

Options

• Athe message flow details from SM100 to the PPM servlet
• Bthe message flow details from the SM100 to Avaya Aura® Communication Manager (CM)
• Cthe message flow details from the network to the SIP container
• Dthe message flow details from the SM100 to the Avaya Aura® Session Manager (SM) Call

• A
  6% (3)
• B
  4% (2)
• C
  2% (1)
• D
  88% (45)

Explanation

Option D is correct because traceSM with the a=showSM option captures SIP messages internal to Session Manager itself - specifically the message flow between the SM100 core component and the SM's own Call processing engine. This gives visibility into the internal SM processing path that a standard network-level SIP trace cannot show.

Why the distractors are wrong:

• A is incorrect because the PPM (Personal Profile Manager) servlet handles user preferences/profiles, not the core call processing flow that traceSM targets.
• B is incorrect because traffic between SM100 and Communication Manager is an external SIP trunk flow, visible in a regular network SIP trace - traceSM's value-add is the internal view.
• C is incorrect because the network-to-SIP-container path is precisely what a standard SIP trace captures; traceSM is differentiated by showing what happens after the SIP container receives the message.

Memory tip: Think of the prefix "SM" in showSM as "Show Me the internal Session Manager path." A regular trace shows the outside world; showSM shows what SM does inside itself once it receives a message - the SM100-to-SM-Call leg is the heart of that internal processing.

No community discussion yet for this question.