Error sync Exchange Contacts to 3CX

[wingsoft]

We're tring to configure Debian 3CX based to sync our Public Folder in our OnPremise Exchange 2016 Server.
- We follow the guide provided here
https://www.3cx.com/docs/manual/pbx-crm-integration/#h.5q3i8vyk3vdt
- We create a Impersonated Account follow this guide:
https://www.3cx.com/docs/how-to-create-impersonated-user/
- We install the package apt-get install gss-ntlmssp as required for Debian installations.

IF we enable "Windows Authentication" in OWA IIS and disable FBA Auth everything works fine!

IF we leave "default" settings for OWA (with "Windows Auth" disabled and "Basic Auth" enabled) sync gives this error:

2020/02/12 13:06:34.029|700|0001|Inf|Log is created
2020/02/12 13:06:36.534|700|0001|Info|Log verbosity is set to Low
2020/02/12 13:06:48.597|700|0024|Erro|Error while checking contacts from Public Folder 3CXAddressBook
2020/02/12 13:06:48.637|700|0024|Excpt|System.PlatformNotSupportedException: No support for channel binding on operating systems other than Windows.

We tried to google this error without success.

How can we solve this iusse?

 

[coreybrett81]

I'm having trouble getting this to work also.

Where did you find those log entries?

 

[wingsoft]

In 3CX httpd logs.

 

[owarzecha]

Same problem here (except I have not tried without windows authentication). What is the officially supported way?

 

[alexTakacs]

Is anyone having this working (Debian to Exchange) ?

 

[Mischa Sz.]

Same issue here. Exchange 2013 and 3CX v16.0.504 on Debian with installed gss-ntlmssp.

Any inputs from official side how to fix this?

 

[Frank.Buhse]

Same issue here. Exchange 2019 and 3CX v16.0.4.504 on Debian with installed gss-ntlmssp.
Can someone help me find the necessary logs.

 

[alexTakacs]

Not sure what "necessary logs" you are looking for ?
As far as I understand it this feature simply doesn't work under Linux based instances. Happy to be disproved

 

[ben-xs]

Hi,
same thing here.

gss-ntlmssp installed.

systemservice.log says:
2020/04/01 11:04:19.120|1578|0031|Erro|Error while checking contacts from Public Folder Kontakte/KontakteXS
2020/04/01 11:04:19.121|1578|0031|Excpt|System.PlatformNotSupportedException: No support for channel binding on operating systems other than Windows.
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.Net.WebRequest.<>c.<GetResponseAsync>b__68_2(IAsyncResult iar)
at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)

Exchange IIS authentication for owa Backend is "Windows Authentication" and owa Default Website "Basic Authentication". I've activated also Windows Authentication, but that was not changing the error.

Hope for answers...

 

[alexTakacs]

Did anyone formally open a support case for this ?

 

[mattm121]

Did anyone formally open a support case for this ?

Hello,

I have the same issue on a new install. I opened a case on 4/3/2020. Apparently when running 3CX on Linux there is a know issue that will be fixed with V16sp5 which is currently in beta as of 4/3/2020. Also you will need to install to install run:
apt update
apt install gss-ntlms

then reboot your Linux server.

I have not confirmed this as I don't want to install the beta on my production system.

 

[ben-xs]

Hi mattm121,
please see https://www.3cx.com/blog/change-log/phone-system-change-log/
There is no reference to an issue which would be fixed in V16 Update 5, while it is in Update 3.
Where did you get your information?

 

[mattm121]

Here is the exact reply from 3CX.
"
Thanks for contacting 3CX technical support.

Please note that currently, there is an issue with the sync between the local exchange and Linux based OS for the PBX which does give the error below

Excpt|System.PlatformNotSupportedException: No support for channel binding on operating systems other than Windows.

We have though fund that the issue is resolved in the upcoming sp5 update which will be released shortly and is currently in the Beta stage.

There will also be a requirement to install a package on the Linux OS to allow the syn to work when Sp5 is installed

https://www.3cx.com/docs/manual/pbx-crm-integration/#h.kkqlf5cur2x
"

 

[alexTakacs]

I can confirm that running 16.0.553 on Debian this feature is now working !
As an aside - how often does the sync run and can this be amended ?

 

[StefanW]

it will sync once a day at 4am in the morning. Resync is also triggered on system service start

 

[michelescapini]

Also on my test Debian with the package (gss-ntlmssp) installed and U5 works !!
When will support for Hybrid Environments (on-prem & 365)?
I can finally retire the vm Windows and go back to Debian!

 

[mattm121]

I can confirm as well...just installed v16 update 5 and magically personal contacts now show up. Note I had already configured the integration previously but it was broke. The update just fixed it.

 

[CBX]

Apparently, the sync is also triggered when you make some minimal change in the Advanced\Contacts\Exchange panel.

You can witness this in the log file /var/lib/3cxpbx/Instance1/Data/Logs/3cxSystemService.log:
2020/04/24 13:36:37.360|4413|0038|Info|Sync-Job execution started
2020/04/24 13:36:37.360|4413|0038|Info|ConvertPlusTo: +
2020/04/24 13:36:37.360|4413|0038|Info|Synchronization of GAL started...
2020/04/24 13:36:37.360|4413|0038|Info|Synchronization of public folders started...
2020/04/24 13:36:37.360|4413|0038|Info|Synchronization of Public Folder Adressbuch started...
2020/04/24 13:36:38.261|4413|0014|Info|Synchronization of Public Folder Adressbuch finished(238 contacts)...

The only issue I found was, the e-mail address fields are filled with the LegacyExchangeDN attribute of the Active Directory object instead of the mail attribute, so each contact has a funny e-mail address like this:

/o=COMPANY/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=USERNAME

Outlook actually doesn't have a problem with this because it appears to be an LDAP alias for the account (my guess). If 3CX could use the mail attribute instead, the Exchange contact synchronisation would be virtually perfect.