3cx call control api

[flexible3]

Hello,

I heard that the 3cx call control api is only for internal use with V16.
I have created in the past an application for a customer with 3cx V15 that heavily was depending on this api. What do I have to propose to my customer?
Is it safe to migrate to V16? Will my code still work or break?

I have also heard that 3cx will provide a new rest api api with the same features? Is that correct? When will this be available?


Yours faithfully,
Tom Van de Putte

 

[cjewell]

I can tell you that our application utilizing the v15 call control api broke when our client upgraded to v16. We are still trying to figure out if it's just a dependency issue that can be fixed or whether things are worse than that.

 

[flexible3]

Hello Cjewell,

Thank you for your answer. I was afraid that this was the answer.
Can anbody from 3cx answer this question also please? Is there a rest api that will be created later? And if yes, will they have thesame features? What is the expected release date? This is for the moment blocking for us.

Yours faithfully,
Tom Van de Putte

 

[edossantos]

Hello guys,

The Call Control API in v16 has many internal changes, but the public interface has just a few changes. In most of the cases, the app you built for v15.5 will work in v16 without changes, just recompiling it. However, that's not always the case, so you need to test it properly.

For sure, a binary built for v15.5 will not work in v16. There are many changes at the binary level that cause this. For example, what in v15.5 was a public class like ActiveConnection, has been converted to an interface in v16. So, at the binary level, those are totally different types, and if your code is looking for a class named ActiveConnection, it will not find it in v16. However, just re-compiling your code will do the trick, and will cause that your new binary looks for an interface named ActiveConnection instead.

As you know the 3CX Call Control API is for internal use, but the DLLs are there, and you can use them at your own risk... This API will not be removed in the near future as far as I know, as 3CX services completely rely on it.

Regarding the REST API, it's not available yet, and there is no ETA for this. Also, the scope is not fully defined yet, so at the moment I can't tell what it will do or not...

Kind regards.

 

[flexible3]

Thanks Edossantos!

 

[man3000]

Good day

with numerous applications created with the API that have now just stopped working due to underlying changes in V16.

Can you not release the latest API documents to just development partners?

 

[edossantos]

Please post a request in the 3CX Ideas forum:
https://www.3cx.com/community/forums/3cx-ideas/

This way this requirement will get visibility.

Thanks.