We have the same problem as reported by other users here: Our Windows based CRM system can only initialize the 3CX multi line TAPI driver when the Windows dialer has been started before. Then the initialization works in most of the cases. If the dialer is not started (but the 3CX phone), then the CRM reports after about 20 seconds, that it wasn‘t able to initialize TAPI and CTI isn‘t available.
It may be easy to say that this is a problem of the CRM system, but as this behavior has been reported by other customers and our CRM is able to initialize every other TAPI driver we‘ve tried (e.g. estos), to me it looks more like a specific 3CX issue.
So the only solution at the moment is to put the 3CX phone into autostart together with the Windows dialer. This results in several windows popping up when the user logs in and several windows hanging around in the task bar. Not really nice and hard to explain to all users.
If a real solution isn‘t available I would also be happy for workarounds (e.b. some „silent“ tray application which does the TAPI initialization job).
It may be easy to say that this is a problem of the CRM system, but as this behavior has been reported by other customers and our CRM is able to initialize every other TAPI driver we‘ve tried (e.g. estos), to me it looks more like a specific 3CX issue.
So the only solution at the moment is to put the 3CX phone into autostart together with the Windows dialer. This results in several windows popping up when the user logs in and several windows hanging around in the task bar. Not really nice and hard to explain to all users.
If a real solution isn‘t available I would also be happy for workarounds (e.b. some „silent“ tray application which does the TAPI initialization job).
- 3CX Version: 16.0.2.910
- Server OS: Not sure. Hosted version bei 3CX partner matic-tec.de
- TAPI driver (latest version as of today) and CRM installed on Windows Server 2016
