Full TAPI drive needed

[SLSystAdmin]

Searching for a solution for our inbound call notification to our script app and as with other posts, 3CX TAPI does not support the fill TAPI integration. The TAPI is working for placing calls but inbound is not. One of the posts indicated that any further development to implement this (Full TAPI integration) is not going to happen as it an old technology. Has anyone found a solution to this issue or is there any chance that 3CX would consider adding full functionality in to their TAPI driver?

 

[VoIPTools]

Does the application you are trying to integrate with only support TAPI? Because there are other ways we can get 3CX events (3CX Call Control API for example). TAPI was a technology abandoned by Microsoft 20+ years ago, so I would hope you have other options.

 

[SLSystAdmin]

not at this time, we are still using some legacy software for a project

 

[SLSystAdmin]

I was doing some research into the 3CX Call Control API that Matthew mentioned and found that is it no longer available. Possibly replaced by a REST API but where is this and documentation for it? Any help would be appreciated in getting 3CX to notify our app of the inbound call.

 

[VoIPTools]

It is true, the documentation has been withdrawn. Presumably, this is in preparation for the upcoming REST API and Gateway server. The existing 3CX Call Control API still exists and is also in the current V18 alpha. We use the 3CX Call Control API extensively in all our tools. Once 3CX actually releases the new APIs, we will see what they can do and whether they will have feature parity with the existing API.