phonebook v15 Exchange 2010

[ronecker]

Is there a way to use in v15 the Exchange sync of contacts with an Exchange 2010?
We've been using it since v12 and where quite happy with it, but the latest version seems to dislike our Exchange

Let me guess, it is deemed outdated?

Taken from the 3cxSystemService.log file

2016/11/08 12:48:07.541|3200|0024|Warn|Microsoft.Exchange.WebServices.Data.ServiceVersionException: Exchange Server doesn't support the requested version.
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ProcessWebException(WebException webException)
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ValidateAndEmitRequest(IEwsHttpWebRequest& request)
at Microsoft.Exchange.WebServices.Data.MultiResponseServiceRequest`1.Execute()
at Microsoft.Exchange.WebServices.Data.ExchangeService.FindFolders(FolderId parentFolderId, FolderView view)
at CompanyDirectoryService.Clients.PublicFolderExtensions.GetTopLevelFolder(ExchangeService service, String folderName)
at CompanyDirectoryService.Clients.PublicFolderExtensions.GetPublicFolderByPath(ExchangeService service, String ewsFolderPath)
at CompanyDirectoryService.Clients.PublicFolderExtensions.<GetContactsFromPublicFolder>d__4.MoveNext()
at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at CompanyDirectoryService.SchedulerJob.SynchronizePublicFolderContacts(String FolderName)

 

[agesen]

In parameters of 3CX search for "CDM_EX_VERSION"

Try enter Exchange2010

Regards Nanna

 

[ronecker]

Interesting idea, but no cigar.

It was set at "Exchange2010_SP2", I tried "Exchange2010" and "Exchange2010_SP1" to no avail.
We are at 14.03.0319.002 which translates to Exchange 2010 SP3 RU15 (read, the latest available), so the server supports it.

I have a hunch, since v15 was rewritten, and there is no longer a selection of Exchange version in the corresponding form, they neglected to introduce the EWS schema version in their call. And since the latest version defaults to Exchange2013, this might explain our problems.

Let's see what support has to say about this

 

[agesen]

The FQDN is case sensitive, so be sure thats 100% correct.

 

[ronecker]

The FQDN is case sensitive, so be sure thats 100% correct.

FQDN case sensitive, since when?
Anyways, I am at all lowercases, which worked in the past and is currently working in any browser.

Fiddeling around with settings, I can get an 401 not authorised, so I am guessing Exchange is answering, but does not like the EWS version.

 

[agesen]

Sorry I was mistaken - in 3CX FQDN is case sensitive when integrating with exchange UM, not the phonebook.

 

[DinoMueller]

I got the same problem. 3CX V15 with an older Exchange on a SBS2011.

Did you make it work?

 

[smcore]

I got the same problem.
There are responses by 3CX to this problem?

 

[YiannisH_3CX]

Hello all,

Please note that the supported versions of exchange for v15 are Exchange 2013 SP1, 2016 and Office 365 as stated in the guide below
https://www.3cx.com/docs/manual/pbx-crm-integration/

 

[narkumas]

Hm, would You mind to support Exchange 2010 as well?

 

[nobody]

Hello all,

Please note that the supported versions of exchange for v15 are Exchange 2013 SP1, 2016 and Office 365 as stated in the guide below
https://www.3cx.com/docs/manual/pbx-crm-integration/

Actually I would expect that the 3cx Exchange and Outlook Support works for all Versions which are supported by microsoft. So, it should have work together with Exchange 2007 until April 2017.
I do not understand why functionality that worked is dropped without notice

Well, there is a workaround, which seems to works for me with 3cx V15 to reactivate sync contacts with Exchange 2010:
The first step to do, is to enable basic authentication in the ews subfolder of IIS, without this, you might get an error message with the identical text to "Microsoft.Exchange.WebServices.Data.ServiceVersionException: Exchange Server doesn't support the requested version". Regardless of Exchange 2013 or 2010. Actually I did find this workaround because I still got this Error when I finally installed Exchange 2013, and contact sync did not work.
Now, to solve the real problem:
On the PBX server there are several copies of a file "Microsoft.Exchange.WebServices.NETStandard.dll"
Copy the file to some other location.Open the copy with a hex editor. Search for "Exchange2013_SP1". Replace with "Exchange2010_SP1". Save.
Replace all occurences on the pbx of this file with the patched version
reboot pbx.
Your Contacts will now sync with Exchange 2010 and above.

Question: why did 3cx did not supply a patched version of the Library? Or Why did 3cx not already make a call which is compatible to 2010_sp1 and above?