Turns out this was happening before the move.

Button Features Invalid usually shows up when there are no call appearances assigned - sometimes a User has none, the Call Appearances are assigned through User Rights, and the User has become removed from the rights group, or was hotdesked onto a User without appearances and is now hotdesked out.

Don't know why it would have been OK for you yesterday and not now, but maybe it rebooted overnight, logging out those users, and subsequent reboots won't change that.

Thanks for the come back, Tommy. I tried logging them, but no joy. Anything else I could try?



Quaz

I agree with TouchToneTommy. This is usually shown of the user has no call appearance buttons. Regardless of the reason that led into this situation.

IP Office remote service https://www.fwilke.com/home
Fixed price SIP trunk configuration: https://www.fwilke.com/en/ip-office-sip-trunk-en/
CLI based cale blocking: https://blog.fwilke.com/ip-office-block-calls-from...
SCN fallback over PSTN: https://blog.fwilke.com/ip-office-scn-fallback/

Derfloh,


Wie gehts? I listened to what Tommy said and checked user's rights and the users having the problem to insure that they all had the correct users rights. They did. So since the last service company used user's rights for button mapping, I took user's rights out of the equation and copied and pasted the button map to the 4 phones having the problem. So far so good. What do you think?

Quaz

I'm fine...

I would just try to configure at least two CA buttons for the user and ignore all the user rights.

You can also check in SSA if really the expected user is logged in at the phone.

IP Office remote service https://www.fwilke.com/home
Fixed price SIP trunk configuration: https://www.fwilke.com/en/ip-office-sip-trunk-en/
CLI based cale blocking: https://blog.fwilke.com/ip-office-block-calls-from...
SCN fallback over PSTN: https://blog.fwilke.com/ip-office-scn-fallback/

Thank you for the info, Guys. I appreciate it.!