TAPI has stopped working since Version 16.3.0.111 update

Status
Not open for further replies.

GrantJ

Customer
Joined
Apr 2, 2020
Messages
6
Reaction score
2
Hi
Anyone else getting an error connecting to the TAPI driver since last nights update (16.3.0.111) ?

Uninstalling and reinstalling an older version of the "3CX Phone App For Windows" solves the problem, but obviously we need a proper fix going forward.

Thanks

Grant
 
Nice, that we don't have an official answer from 3cx yet...:mad:

Downloaded plugins from here:
https://downloads.3cx.com/downloads/3CXPlugins15.exe

Closed our own SW that access the TAPI driver.
Tried to update with .exe first (should remove old and then install new version).
Install hangs -> killed the task after about 40 Minutes in Taskmanager (as cancel and "x" don't work)
Tried again -> error message, that another setup is in progress (what was not true) and I should close the other setup first..
Rebooted PC -> same error (another setup in progress...)
Deleted C:\ProgramData\3CXMultiLineTapi\
Started .exe again...
Setup successful...
TAPI works again now (incoming and outgoing)
 
Doing this at all our medical customers individual workstations... lots of work, really disappointing..
3CX needs an urgent fix for this.
 
Update to my last posting from May 15 above...
After delete and reinstall the TAPI Installation and bring it to work again this way, I have installed a new version (16.3.0.144) to the windows client (since I thought it includes bug fix).
After the update, the TAPI has not worked anymore once again!
So I had to delete and reinstall the TAPI Installation again, to bring it to work.
This is really not nice ans still no official posting from 3CX :mad::mad: !
Where is your customer support... 3CX?
 
This is really not nice ans still no official posting from 3CX :mad::mad: !
Where is your customer support... 3CX?

The only answers I read from 3CX are non-relevant and didn't in any way help to solve this problem.

And I refuse to pay 75 EUR to open a support ticket. I have known the situation in the beginning when support was free for ALL partners, even affiliate ones.
I also have enough experience with support to know how this will work out. You need to do a wireshark trace etc., all not relevant to this issues. The issue is the 3CX Windows client. Not the network, the computer, or whatever.

I've spent hours in the past with support solving problems and reporting bugs. Only when the issue gets high enough in the support chain of 3CX, something seems to happens when it's about bugs.

That's my personal experience, and I don't say that's everyone's experience.

I recall the Fanvill C600 issues, of which I posted about in this forum.
That one has cost me a lot of money, and at that point I really thought about to stop with installing 3CX. But they have some features nobody else has. And for small companies, it's a free and easy manageable solution if you just need a basic PBX without much integration or queues and a decent softphone.

It's hard to believe only the people posting here are having this issue or have customers using TAPI.
IMO 3CX is well aware of the issue, but for one reason or another does not want to acknowledge it, let alone solve it.

I also wonder how much they are still interested in TAPI support, since the last version of the driver is already several years old. To me, it feels they want everybody on the webclient. Much easier to maintain of course then a separate Windows program.

I really don't understand partners have to post here (GaSo is Silver partner, so has free access to support) to bring this to the attention of 3CX and get something done about it.

Just my 2 cents...
 
Is this resolved yet by an updated version or can 3CX confirm if it will be and how soon?
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,990
Messages
590,161
Members
164,926
Latest member
tohoken1