TAPI not working with newest Client for Windows (3CX 15.5)

[cwidmer62]

Updating the 3CX client for Windows breaks the TAPI functionality with the 3CX Plugin.
This is a recurring problem: There are only certain combinations of the 3CX Phone Client and the 3CX Plugin that work. In the past I found that 3CX Phone 15.5.7262.3 and 3CX Plugin 15.0.915.607 were working together. After the 3CX Plugin was updated to the Multi-Line TAPI the combination of 3CX Phone 15.5.8801.3 + 3CX Plugin 15.0.930.363 was working also.
After the current updates of the 3CX Phone TAPI is no longer working. Unfortunately I neglected to save a copy of the 3CX Client 15.5.8801.3. I don't think I do anything wrong with the configuration, since it was working in the past - but now I'm really stuck here. BTW: I'm using Windows 10 (1803) 64-bit - but I don't think it is a Windows version issue. I also see this problem on different PC's.
Does someone have any ideas and how did others get that working? Alternatively, could someone provide me with the "old" 3CX Client Version 15.5.8801.3 installer MSI?
Any help would be greatly appreciated.

Thank you

Christoph Widmer

 

[edossantos]

Hello Christoph,

Do you have a PRO license key activated in your 3CX server? As explained here, TAPI is only available in PRO and ENT license keys.

Kind regards.

 

[cwidmer62]

Hello Christoph,

Do you have a PRO license key activated in your 3CX server? As explained here, TAPI is only available in PRO and ENT license keys.

Kind regards.

Dear Ernesto,
Thanks for your reply. In fact, the TAPI-functionality works in all versions, Standard included - the 3CX documentation is actually not correct in this point. Just to double check I have tried with a 3CX Pro version also, alas no change. It has been working with 3CX Phone for Windows 15.5.8801.3, only the updates past this version broke it.

If you wish I can give you remote access to a PC with this problem. As a stop-gap measure you could help me out if you can give me a download access to the 3CX Phone for Windows Version 15.5.8801.3 installer MSI (exactly this version).

Thank you for your consideration and best regards
Christoph

 

[bencrofts]

I am having the exact same issue, and as you say each time they update the pluggin my TAPI stops working. Did you manage to source a version that works ?

 

[cwidmer62]

I am having the exact same issue, and as you say each time they update the pluggin my TAPI stops working. Did you manage to source a version that works ?

Hi,

To make it simpler I will sort of tell the story backwards - Yes I now got TAPI working (again).

You now indeed need a 3CX Pro or Enterprise license, a Standard license no longer works.
You need to download and install the "Multi Line Tapi Extension for Terminal Server", even for a normal PC - the TAPI function in the "3CX CRM V15 Plugin" no longer works. Make sure you follow the installation instructions given by 3CX (next to the download button). The Multi Line TAPI for Terminal Server works with the current version of the "3CX Phone for Windows" - so (at least for now) there is no versioning issue.


And here the history for the records:

3CX provided a single-line TAPI via the "3CX CRM Plugins" which was working in any edition of the 3CX PBX. 3CX changed that to the Multi-Line TAPI which, at first, continued to work in all versions, but you had to be careful to which version of the 3CX Phone for Windows you would pair it up. Not all versions of the CRM Plugin would work with all versions of the 3CX Phone for Windows.
Since the 3CX PBX 15.5 SP3 TAPI is now disabled in the Standard edition. 3CX confirmed to me that TAPI will continue to be supported in the PRO Editions (our national distributor told us that in the future only the ENT Edtion would be supported). 3CX also confirmed that the old single line TAPI is dead for good.
If you have existing customers with Standard Licenses, you will have to tell them that they will have to upgrade to the PRO version in order to continue to use their existing TAPI functionality - well, they are not really amused.

All of this took me a good deal of time to figure out. It would have really much simpler if 3CX actively communicated these facts (at least to the resellers).

I also learned the hard way to keep a version history of the 3CX Phone and Plugins and so on and only to update customer installations when I have thorougly tested everything myself first.

I hope that helps.

Cheers

Christoph

 

[bencrofts]

Thanks so much for the detailed reply.

I did find this the hard way also in 2016. But fortunately i had all the older versions. I am going around in circles here totally uninstalling everything and trying again and cant workout why it was not working. But as you say if i now need PRO, this is total pants. I bought a car that had power windows and now they are telling me they are taking that away and i have to pay extra to get back what i already had.

 

[cwidmer62]

Thanks so much for the detailed reply.

I did find this the hard way also in 2016. But fortunately i had all the older versions. I am going around in circles here totally uninstalling everything and trying again and cant workout why it was not working. But as you say if i now need PRO, this is total pants. I bought a car that had power windows and now they are telling me they are taking that away and i have to pay extra to get back what i already had.

Hi again,

yes, I agree. I can, at least in part, also understand the position of 3CX, but this time we all got into a mess. To keep everything in sync (PBX, PC-clients, handphone clients, plugins across various PC and phone OS) is certainly no easy task but how they handled this one really is sub-optimal.

As for the installation; forgot to mention one thing explicitely: On existing PC client installations you first have to uninstall the 3CX Plugin, then install the Multi-Line TAPI for Terminal Server. Don't forget to restart the Telephony Service (or just reboot the PC). The 3CX Plugin and the TAPI for Terminal Server really don't coexist.

Good luck!

Christoph