Solved Teams Presence Sync

[HamzehZ]

Hello,
it's Sync only not Sync All, Does this affect the presence reflection?

 

[Guillaume Bourgeois]

Hello,
it's Sync only not Sync All, Does this affect the presence reflection?

Yes, add your extension .. and try.

 

[HamzehZ]

Yes, add your extension .. and try.

My extension is already added

 

[Guillaume Bourgeois]

Is it still not working?
On the page: admin > Users, do you see a green checkmark at the far right end of the row for your extension?

If yes, click on your extension and go to the options tab.
Look for “Sync Calendars & Teams Presence.”

Is it checked?

 

[Guillaume Bourgeois]

Even after all that, is the Teams presence sync still not working?

Increase the level to Verbose in Activity Logs > Settings. Purge the logs. Reproduce the problem. Download Support Info zip file and send me privately.


https://www.3cx.com/docs/collecting-logs-for-3cx-support/

 

[HamzehZ]

Even after all that, is the Teams presence sync still not working?

Increase the level to Verbose in Activity Logs > Settings. Purge the logs. Reproduce the problem. Download Support Info zip file and send me privately.


https://www.3cx.com/docs/collecting-logs-for-3cx-support/

Please assist with how to send it to you privately

 

[Guillaume Bourgeois]

Upload the ZIP file to a file-sharing service like OneDrive, Google Drive, or similar, and then send me the private download link.

Start new conversation with me

 

[HamzehZ]

Upload the ZIP file to a file-sharing service like OneDrive, Google Drive, or similar, and then send me the private download link.

Start new conversation with me

The link has been sent

 

[Guillaume Bourgeois]

RESOLVED


Analysis of Logs: I've observed that 3CX wasn't receiving any requests from Microsoft.
I conducted accessibility tests with the following results:

- https://[FQDN]/m365/notifications : Could not reach the page.
- https://[FQDN] : Could not reach this page either.

I suspected a restriction on port 443 in the firewall ahead of the PBX.
After requesting the removal of this restriction, the issue was resolved, and access is now functional and sync working.

→ The devil is in the details. ​