71301T · Question #64
A customer reports that when using Presence services, the users cannot see the Presence status. Which two tools are used to trace a PUBLISH message. In the Avaya BreezeTM server? (Choose two.)
The correct answer is C. traceSM E. tracePS. Tracing a SIP PUBLISH message on the Avaya Breeze server requires following the message path: traceSM (C) captures the message as it flows through Session Manager, which handles all SIP signaling including PUBLISH requests, while tracePS (E) traces the Presence Services snap-in…
Question
A customer reports that when using Presence services, the users cannot see the Presence status. Which two tools are used to trace a PUBLISH message. In the Avaya BreezeTM server? (Choose two.)
Options
- AtraceSBC
- BtraceCE
- CtraceSM
- DtracePRS
- EtracePS
How the community answered
(41 responses)- B2% (1)
- C95% (39)
- D2% (1)
Explanation
Tracing a SIP PUBLISH message on the Avaya Breeze server requires following the message path: traceSM (C) captures the message as it flows through Session Manager, which handles all SIP signaling including PUBLISH requests, while tracePS (E) traces the Presence Services snap-in directly, where the PUBLISH is processed and presence state is stored. Together, these two tools cover the full end-to-end path of a presence publication event.
Why the distractors are wrong:
- traceSBC (A) is used for the Session Border Controller, which sits at the network edge and is not involved in internal Presence processing on Breeze.
- traceCE (B) targets the Communication/Collaboration Engine, which handles media and call processing - unrelated to Presence PUBLISH flows.
- tracePRS (D) is a fabricated/incorrect tool name; the real Presence Services trace command is
tracePS, nottracePRS.
Memory tip: Think of the PUBLISH message's two-stop journey - it lands in Session Manager first (traceSM), then gets handled by Presence Services (tracePS). If you remember SM + PS = PUBLISH path, you'll lock in both correct answers.
Topics
Community Discussion
No community discussion yet for this question.