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
  72% (33)
• B
  9% (4)
• C
  15% (7)
• D
  4% (2)

Explanation

Option A is correct because in Avaya Aura architecture, when CM is added as a Sequenced Application in the endpoint's SIP Communication Profile, Session Manager (SM) acts as the intermediary that receives PPM data from CM and then pushes it down to the Remote Worker telephone. Without CM being sequenced, SM never obtained the PPM data, so the delivery step from SM to the phone never occurred - which explains why feature buttons were non-functional.

Option B is wrong because while CM does supply PPM data to SM as part of the sequenced application flow, this is an upstream step in the flow, not the one that was missing from the user's perspective - the phone still wasn't receiving anything.

Option C is wrong because System Manager (SMGR) is the administrative/management platform for the Aura suite; it does not participate in delivering PPM to endpoint devices at call time.

Option D is wrong because CM does not communicate PPM directly to SIP phones in this architecture - SM is always the delivery point to the endpoint; CM feeds SM, not the phone directly.

Memory tip: Think of Session Manager as the "last mile" delivery courier - CM packages the PPM, but SM is always the one that knocks on the phone's door. If the phone never gets its package, the courier (SM) never received it from the shipper (CM being sequenced).

No community discussion yet for this question.