Avaya IP Office Platform Fundamentals — Question 39

A large enterprise is using an Avaya Aura® Core. An Avaya SIP Endpoint, one-X® Communicator, controlled by Avaya Aura® Communication Manager (CM), has been configured with three feature buttons, but none of the buttons appear on the telephone interface. The telephone shows successful registration with Avaya
Aura® Session Manager (SM) at the SIP Level.
What are two possible causes for this feature button failure? (Choose two.)

Answer options

• A. The SM Server is down.
• B. The SIP Signaling Group between SM and CM is down.
• C. The telephone is pointing to CM instead of SM for registration.
• D. DSP resource has not been reserved specifically for CM features.
• E. The Application Sequence for CM has not been selected for that extension in SM.

Correct answer: B, D

Explanation

The correct answers are B and D. If the SIP Signaling Group between SM and CM is down, feature buttons cannot communicate properly, leading to their failure to appear. Additionally, if the DSP resources have not been reserved for CM features, the necessary resources for those features won't be available, causing the same issue. Options A, C, and E do not directly relate to the feature button visibility issue.