Office 365 Integration - Real Time Notifications to Office 365 changes will not work because it seems that HTTPS port forwarding is not configured.

[Dion Vansevenant]

I have followed the newer instructions on O365 integration here: https://www.3cx.com/docs/office-365-integration/

For the most part, it appears to be successful, except for this message:

"Real Time Notifications to Office 365 changes will not work because it seems that HTTPS port forwarding is not configured. This means that when changes occur, they will not be updated real time. A synchronization will still occur every night.
Code: InvalidRequest Message: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. Inner error "

I've dug around a bit, but have not found anything explaining why this is happening.

The 3CX Firewall test comes back green

The minimal firewall on this GCP-based instance of v16 is allowing HTTP and HTTPS traffic through.

The system ended up being configured to use port 5001 for the admin/web interface. Do I need to adjust port 443 ?

Thanks,

Dion

 

[ZeelIT]

I found that to get it working i had to open 3CX management console up to inbound traffic on 5001 because of how the API is structured off it in order to allow Office365 to talk to my 3CX installation.

I might be wrong here, but I tried blocking out the port again and it stopped Office365 syncing. EDIT: Stopped it syncing realtime

I think the 3CX system will sync every 24 hours without opening up the port though?

 

[Dion Vansevenant]

I found that to get it working i had to open 3CX management console up to inbound traffic on 5001 because of how the API is structured off it in order to allow Office365 to talk to my 3CX installation.

I might be wrong here, but I tried blocking out the port again and it stopped Office365 syncing. EDIT: Stopped it syncing realtime

I think the 3CX system will sync every 24 hours without opening up the port though?

Thanks for the suggestion, but since 5001 is my admin port, it's already allowed through the firewall....at least, TCP is.