Extensions set to away for no reason

[Michael Moore]

We're having a weird issue with only ONE of our 3CX installs. Extensions randomly set themselves to "AWAY". They then have to be manually put back to in-office for calls to get through. I have already ruled out the following:
1. Users are not accidentally changing their presence via the web client (none of the effected users even login to webclient).
2. There is no BLF key or programmable key on their Yealink phone that's set to change presence to AWAY.
3. They are not setup in the 3CX admin console to go to away and/or available during a set schedule.
It's different extensions, and only happens randomly, and never to more then a few at a time.
The reason this is hard to fix is because we don't notice they are away immediately and so have had a hard time getting the right log file for 3CX support.
Anyone seen this before? We have 5 installs at different customers and only 1 experiences it.
BTW...
15.5 SP6 on Debian, issue has been happening since 15.0 on debian.
Yealink T41 phones

Thanks in advance for people's advice!

 

[craigreilly]

Do you see the info in the activity log? ie: *32 dialed.
(maybe someone playing cruel joke)

 

[Michael Moore]

The problem is we don't know exactly when it's happening so I don't know where in the logs to look. I am able to get a window of time, but am not sure exactly what to search for as well during that window of time.
I'm trying to get an example and a shorter window of time to give to 3CX support, but just wanted to see if anyone else had seen this while I"m waiting for that...

 

[YiannisH_3CX]

The support info bundle should contain all the logs needed for 3CX support to find the issue. Just wait for the issue to occur and when it does generate the support info and mention the affected extension number and an when this might have happened. I believe the best way to look for this is by using the Bin log viewer. https://www.3cx.com/docs/3cx-log-viewer/