Call Control API not working in v16

[socnet]

I've read the recent forum posts:
https://www.3cx.com/community/threads/call-control-api-documentation.62740
https://www.3cx.com/community/threads/3cx-call-control-api.64664/

They talk about how the documention for the API has been removed, and the reasons why. Our products integrate with the Call Control API and have over 200 3CX end customers who leverage this integration. We have found that (as well as the missing documentation) the API no longer works in v16, and from what we can see this seems intentional.

Please can you confirm if this is intended? Or if you will support customers who try to get the API working on v16? Please give a definitive answer. We are preparing an email to the customers advising not to upgrade to v16 since it will stop the integration from working. But we would prefer to jointly help these customers instead obviously.

 

[Constantinos Constantinou]

hello @socnet ,

Can you please describe in short the problems that you are facing with Call Control API in a Personal Message?

We have a number of users that use Call Control API on v16 and they are not facing any issues with it.

 

[socnet]

Thank you for the quick reply. Yes, I will gather the information and post it. So to confirm the API is supported on v16, as a minimum for upgrading customers?

 

[Constantinos Constantinou]

That is correct. Call Control API is supported by v16. Please though share with me the use cases, in order to better understand how you are trying to use the Call Control

 

[socnet]

One of the problems that we faced was:

We were told for previous versions to use the SDK DLL from the GAC of the PBX Server. But in v16, it no longer appears to be there (it's missing). So were should we now get the correct file from?

 

[Constantinos Constantinou]

You are referring to a specific DLL? What do you mean with SDK DLL

 

[socnet]

I mean: 3cxpscomcpp2.dll (and it's support files)

 

[Constantinos Constantinou]

You can find the DLL's that you are looking for at the installation directory of the PBX.

Example:
C:\Program Files\3CX Phone System\Bin\

 

[Constantinos Constantinou]

Please verify if this is the case, in order to update accordingly the forum post and avoid the confusion that might created with your statement that is not working with v16.

 

[socnet]

Thank you. We have downloaded a copy of v16 ourselves and installed it. The file is present. Thank you!
The file is not present on the customers' sites that we have been working on, though.
This is odd obviously, and there are several possible explanations.
The versions are not identical in other ways too, but we know that our installation is correct and from the correct source, so as you suggest there does not appear to be a real issue.
We will advise the customer that it does work with a standard v16, after all, and leave them to sort out the issue of the missing files.

 

[Constantinos Constantinou]

Let me clarify something.
So you have customers that have v16 that the files are not present in the Bin directory? Can you please provide some indicative build numbers?
Those customers are fresh installations of v16 or they upgraded somehow from previous versions?