Exchange Integration Changes in v12

[cobaltit]

Since it appears the Exchange Integration has been removed from the 'base' license and is now part of the 'Pro' feature set, perhaps we can include TLS support in the Exchange integration so we can integrate with Office 365? Almost all of my 3CX installs is a customer using Office 365.

 

[yanceyworks]

Ditto this request, we have 90% of our clients using Office365. It would be ideal to see 3CX work with it in some way.

 

[Kevin Attard Compagno]

@cobaltit

How does certificate exchange work in this scenario? Which certificate would the PBX machine need to use for this?

 

[cobaltit]

@kevin

Not sure on the implementation. I guess just an interface like the Secure SIP page where one could upload the certificate and key. It can't be a self-signed certificate, and I believe Microsoft is particular about which CAs they support, although that is not a 3CX issue.

Also, I just noticed in v12 there are two blocks on the Secure SIP tab. One says 'Certificate' and one says 'API key'. Should just be 'Key' or 'Private Key'

I'll see if I can't track down my notes from when I set it up with Asterisk.

 

[Kevin Attard Compagno]

@cobaltit

http://www.3cx.com/blog/voip-howto/secure-sip/

...this link might help clarify.

 

[cobaltit]

@kevin

Sorry I should have been more clear. I meant regarding the integration with the Office 365 Unified Messaging. Although I guess it shouldn't really be necessary as 3CX already integrates with Exchange 2010/2013 UM, the only difference being that Office 365 requires it to be done over TLS.