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.)

Question

Accepted Answer

B. The SIP Signaling Group between SM and CM is down. D. DSP resource has not been reserved specifically for CM features.

Answer

A. The SM Server is down.

Answer

C. The telephone is pointing to CM instead of SM for registration.

Answer

E. The Application Sequence for CM has not been selected for that extension in SM.

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…

Question

Options

How the community answered

Community Discussion