Control calls and more with the powerful .NET core API.

With V20, we’ve updated the Call Control API for Linux - Windows to follow soon. Just like V18, it requires the application to be installed on an actual 3CX instance. A web version of this API is in the works and will be available soon.

What’s New in the Call Control API for V20

The Call Control API has been improved compared to V18:

  • Developers are now notified of changes to a call leg, there is no need to code this anymore.
  • Implementation has been re-written to be asynchronous awaitable (meaning you ask and it will return the final result of the request).
  • API becomes transactional, which means that now developers execute requests and always get the final result of the action. No need to track call state intermediate - meaning less code is required.
  • Before the Call Manager just responded that it is going to execute a request or reject it and that was it. You would need to inject a lot of code just for tracking each and every state of the call. Now the result will be reported back.

For example:

Previously when transferring a call, the Call manager reported only the initial state of the request (acceptance of the request). In the new api it reports the final result (whether it is delivered to a new destination or not). This means developers now do not need to track intermediate states to understand what really happened with transfer. Call Manager will explicitly specify that transfer was completed or failed.

How to Get It

Call Control API for Linux:

  • Download the Call Control API for Linux here.
  • Read the Linux documentation here.

Call Control API for Windows - Coming Soon:

  • Download the Call Control API for Windows here.
  • Read the Windows documentation here.