- Joined
- Oct 4, 2017
- Messages
- 18
- Reaction score
- 2
We have installed the TAPI Drivers for using with an ERP Software which is TAPI capable.
Calling out works most of the times but incoming calls are not notified to the application via TAPI.
The application does, when notified, search the internal crm database for the CID and shows the customers record, which it not does with the 3CX TAPI driver.
This is mostly not a application related problem, because it worked with the former used TAPI driver from Ascotel.
Is there any advanced configuration or debugging possibility to the tapi driver?
Calling out does also have the effect, that the number is called correctly but the status change of the call is never notified back to the program; this causes the program constantly think the call is already been prepared. This lets the status window (call in progress) always open and prevents from accessing the main application window.
Its a Windows 8.1 64bit, firewall disabled in the same network as the 3CX.
Calling out works most of the times but incoming calls are not notified to the application via TAPI.
The application does, when notified, search the internal crm database for the CID and shows the customers record, which it not does with the 3CX TAPI driver.
This is mostly not a application related problem, because it worked with the former used TAPI driver from Ascotel.
Is there any advanced configuration or debugging possibility to the tapi driver?
Calling out does also have the effect, that the number is called correctly but the status change of the call is never notified back to the program; this causes the program constantly think the call is already been prepared. This lets the status window (call in progress) always open and prevents from accessing the main application window.
Its a Windows 8.1 64bit, firewall disabled in the same network as the 3CX.