A customer reports that several Remote Worker new hires were trying to call co-workers in the office, but noticed their feature buttons were not working. After running a SIP trace, the administrator…

Question

Options

• APPM is downloaded to the Remote Worker telephone from Avaya Aura® Session Manager (SM)
• BPPM is downloaded to Avaya Aura® Session Manager (SM) from CM.
• CPPM is downloaded to the Remote Worker telephone from Avaya Aura® System Manager
• DPPM is downloaded to the Remote Worker telephone from CM.

• A
  63% (35)
• B
  23% (13)
• C
  5% (3)
• D
  9% (5)

Explanation

When CM is properly added as a sequenced application in the SIP Communication Profile, the call flow goes: Remote Worker phone → Session Manager → CM (via sequencing) → CM sends PPM data back to SM → SM delivers PPM to the Remote Worker phone. Option A identifies this final delivery leg - SM acting as the intermediary that pushes PPM down to the endpoint - which is the step that was absent because CM was never invoked to generate a PPM response in the first place.

Option B is wrong because CM-to-SM is an upstream step in the flow, not the missing one the question targets - and more importantly, without sequencing, neither step B nor A would occur, but A is the observable "last mile" missing from the user's perspective.

Option C is wrong because System Manager is the administrative/management platform (SMGR), not a real-time SIP signaling node; it does not participate in PPM delivery during live call flows.

Option D is wrong because in Avaya Aura SIP architecture, CM never communicates PPM directly to a Remote Worker endpoint - Session Manager always sits between CM and the SIP device as the routing proxy.

Memory tip: Think of Session Manager as a postal hub - CM (the sequenced app) writes the PPM letter and hands it to SM, but SM is always the one that delivers it to the Remote Worker's door. If CM isn't sequenced, the letter never gets written, and the mailbox stays empty.

No community discussion yet for this question.