Issue with Teams Sync: Status Changes to “Away” After Calls Despite Correct Settings

[tila]

We have configured our customer systems so that only the “In a call” status is synchronized between 3CX and Microsoft Teams.

This part works correctly. When a meeting is scheduled in the calendar, the 3CX status does not change, which is exactly the behavior we want.

However, we have noticed the following issue:

After the meeting is already in the calendar, if we start a Teams call, the 3CX status switches to “Away.” Once the Teams call ends, the 3CX status remains stuck on “Away” and does not return to the previous status. It only resets once the meeting is removed from the calendar.

Could you please investigate why the 3CX status does not revert after the call ends?

We are experiencing this issue across several systems, all running the latest 3CX version.
We have also completely reconfigured the Teams sync multiple times, but the issue persists.

 

[KyriacosS_3CX]

Hello,

Can you confirm the PBX exact version and deployment type? If you can please provide via Direct Message the FQDN or key for a system that shows this behaviour.

 

[tila]

Hi,

Version: 20.0 Update 7 (Build 1080 Release)
Deployment type: Self hosted

I sent you the FQDN via DM.

 

[tila]

We found out, that the root cause is:

After we hang up the teams call, and there is a calendar entry, the teams status doesn't change back to available but to "in a meeting", so 3CX does nothing.

I sent a video and the logs to the 3CX Support.

 

[tila]

Hi,
any update on this?

 

[Kevin Attard Compagno]

Since you are already talking to 3CX Support about this, it's best you keep the conversation going in that channel.

 

[tila]

Since you are already talking to 3CX Support about this, it's best you keep the conversation going in that channel.

Unfortunately I don't get any reply anymore. Could you please assist us?
Thanks in advance.

 

[Charles_3CX]

Unfortunately I don't get any reply anymore. Could you please assist us?
Thanks in advance.

We have searched our database and cannot find a ticket. Please actually open a ticket to check this and advise.