Avaya Cm 10.2 Feature Buttons Do Not Toggle

[Gus1972]

I am deploying an Avaya Aura Solution (SMGR, SM, CM, SBC). R10.2 with J100 series SIP phones.
I have test sets working. PPM is working in a sense the asssigned features "work", but there appears to be something going on with button functionality.

Ex. I can set call-fwd using the button assigned. However, I cannot deactivate using the button. I have to use the feature access code to deactivate.

I actually have two J179 sets on my desk. Both have call forward button activated. 1 sets has a red button, the other set has a green. Neither toggles on / off. Any suggestion on what I may be missing?

 

[Instructor of Avaya]

My first suggestion is that you force a reload of the PPM information. (i.e. Reload Complete, or Reload Config). That would help ensure the phone has the correct/current configuration.



My second thought is that perhaps you have made a very common administration mistake. Many administrators assume when adding the Call-Forward button that they can prefill the intended call forwarding destination in the Extension field. This is wrong. In the screen capture, they would assume that if I were to hit the second Call-Forward button it would automatically forward calls to this phone (x1004) to Extension 1000.

The correct understanding is that this feature delegates to this user (x1004) the ability to enable/disable Call Forwarding of x1000. Typically, this is used in a Boss/Secretary relationship where the Boss (x1000) would want their Secretary (x1004) to be able to Call Forward the Boss' phone calls from the convenience of the Secretary's phone. This is especially useful if the Boss and Secretary were distant from each other (e.g. the Boss is in the Executive Suite on the 14th floor and the Secretaries are relegated to desks in the basement.)

 

[kyle555]

Look at the subscribes and notifys in a trace and check the registration details for what feature packages are subscribed to.

Get all endpoint configuration all in PPM gives you the button, but the subscription to the feature package is what gets the SIP notify from CM to the phone to tell it the lamp should be on.

 

[Gus1972]

Thanks for the help. I ran a trace and filtered PPM and reloaded config on one of the SIP stations.
I am seeing "Fault: Challenge" message (below) throughout the trace from SM to the sip endpoint.

<SOAP-ENV:Fault xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> │
<faultcode xmlns:ns0="http://xml.apache.org/axis/">ns0:Server.Unauthenticated</faultcode> │
<faultstring>challenge</faultstring> │
</SOAP-ENV:Fault>

Aside from TLS, what authentication is occuring? Is there a log with a little more detail?

 

[kyle555]

How are your network regions setup and sip domains setup?
Network map should have subnets pointing to a network region. CM procr should be region 250. Subnets in other regions should be directly connected to procr. The authoritative domain of the region should be the root sip domain as should the authoritative domain of region 250.

And then theres the domain in the sig group youre going in and out on for SIP station traffic.

I'd check to make sure that all lines up. You've got a basic SIP setup problem somewhere...I'm thinking it might be domain related.