Immediately after Registration, how does an Avaya SIP telephone learn if any of its Call Forward features are active right now?

Question

Options

• AIt queries the LDAP database for active feature status.
• BIt sends a Subscribe ?avaya-cm-feature-status event package to Aura® Communication Manager
• CIt sends a PPM getDeviceData request to Aura® Session Manager (SM); Aura® Session
• DIt sends a Subscribe ?avaya-ccs-profile event package to Aura® Session Manager (SM); Aura®

• A
  2% (1)
• B
  92% (44)
• C
  4% (2)
• D
  2% (1)

Explanation

After registration, an Avaya SIP telephone immediately sends a SIP SUBSCRIBE message using the avaya-cm-feature-status event package to Communication Manager (CM) - CM is the authoritative source for telephony features like Call Forward, so it notifies the phone of any currently active feature states via a NOTIFY response.

Why the distractors are wrong:

• A (LDAP): LDAP is a directory service used for user/device lookups, not for real-time feature state. Avaya SIP phones don't query LDAP for active call features.
• C (PPM getDeviceData to Session Manager): PPM (Personal Profile Manager) retrieves user preferences and settings (like speed dials), not live feature activation status. The destination is also wrong - CM owns the feature state, not SM.
• D (avaya-ccs-profile to Session Manager): The avaya-ccs-profile event package is related to contact center/agent status, not general Call Forward features, and again SM is not the feature authority.

Memory tip: Think "Forward = Feature = CM" - Call Forward is a telephony Feature owned by Communication Manager, so the phone subscribes to CM using a feature-status package. Session Manager handles routing and registration, but CM holds the feature logic.

No community discussion yet for this question.