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 is the cause of this problem?

Question

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 is the cause of this problem?

Prakash Varghese · Accepted Answer

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

Prakash Varghese · Answer

The SM Server is down.

Prakash Varghese · Answer

The SIP Signaling Group between SM and CM is down.

Prakash Varghese · Answer

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

Prakash Varghese · Answer

CM has no DSP Resources available.

Question list

List of questions

Question 1

(0)

Question 2

(0)

Question 3

(0)

Question 4

(0)

Question 5

(0)

Question 6

(0)

Question 7

(0)

Question 8

(0)

Question 9

(0)

Question 10

(0)

Related questions

Question 51 - 7120X discussion

Suggested answer: E

0 comments