Solved Available 2 description not updating

[cjt]

If I update the "available 2" description in settings, it doesn't update the description in the webclient or mobile app status list. If I update the "busy 2" description it does update.
Is this a bug or is there something else I can try?
We are running 3CX v16.0.676 on a Windows 10 machine.

 

[YiannisH_3CX]

Just tried this on mine and it works for both statuses. I am also running v16.0.676 on a Windows 10 machine and testing with webclient.
Try clearing your browsers cache and try again. Let us know if that works.

 

[cjt]

Thanks for your reply. I've tried clearing the browser cache (Chrome). I've rebooted the 3cx server. I've changed the description in settings again. Nothing changes, the description for "available 2" still says "Busy" regardless of the description I enter. I can't remember if this is the 3cx default or a description I may have entered in the past. This is on both webclient and android.

Changes to the "busy 2" description show through straight away every time I edit. The 3cx server recognises the new description for "available 2" as it shows in the forwarding settings under an extension. Just doesn't feed through to the clients.

Any other ideas that I could try? I'm only trying to edit the description to try and make the status description usable for the purpose of trying to manage push notifications in android.

 

[YiannisH_3CX]

I have seen something similar before which was related to the soft clients. When a user changed the description for the 2 custom statuses from his windows client or the mobile client, the status would override the status from the PBX for that extension. So check you do not have a custom status set for Available 2. If you do delete if from your clients and upon refresh they should get the status from the PBX.

 

[cjt]

Thank you, this ended up being exactly the issue. The status had been edited on mobile app, but long ago and totally forgotten about, and nothing stands out to warn the user that they've done this. Deleted the status description and now the PBX status shows as expected.

 

[AWS2P]

Congratulations , good finding

 

[YiannisH_3CX]

Glad to see the issue has been resolved and thank you for updating the thread.