Client v20 with TAPI and missing events

[toniSanta]

Hi,
first of all, thanks for releasing new client with possibility to control deskphones.

There is still a problem, just present in client v18, that for forwarded attended calls on the destination PC the TAPI events are not fired, when the destination deskphone (or softphone) connects to the external call. So the application controlling the TAPI-line is unaware of the phonenumber of the external caller. With a 3CX-Client v16 with TAPI v15 and connected to the same v20-server this problem is not present , all events are correctly fired. So it seems to be a problem of the client/TAPI and not of the server.
To reproduce: on terminal one respond to an external call, via button on the deskphone call the destination internal, when the user responds pass him the external call by hanging up or pressing the transfer-button of the deskphone. On the destination side TAPI fires events when user responds to the internal caller, but no events are fired when the user (phone) connects to the passed external call, making it impossible for the controlling app to know who is the external caller.
See also the attachment with monitored TAPI-events.

Please, make this behaviour work like in client v16.

best regards
Toni Santa

 

[JohnS_3CX]

Hi Toni,

In the title you mention Client V20 (the Windows Store App).

But in your description you mention the V18 client "3CX Desktop App" (also known as the electron app).

Can you please read out the exact client version so we can check?

 

[toniSanta]

Hi,
sorry if I was not clear. With v18 i only meant that this actual problem of TAPI with client v20 was also just present in the previous v18 (windows client).
My actual version is 20.0.491.0. TAPI I installed with 3CXTAPI.msi.

Toni

 

[JohnS_3CX]

Ah ok so you are saying that it only ever worked with the V16 client, but never in the V18 or V20 clients.

The current TAPI driver is called 3CXTAPI18.msi which is used for V18 and V20.

Are you perhaps using an older TAPI driver that came with the V16 client, but trying to run it on the newer apps that came after V16?

 

[toniSanta]

I installed TAPI with 3CXTAPI18.msi (not 3CXTAPI.msi, sorry), downloaded from the link in the V20 client app.

 

[little ghost]

Hi everyone,

I have just conducted a few tests.
The old TAPI driver (v15) also works with the new v20 Windows client. However, I can reproduce Toni's problem with this version as well. So, the issue definitely seems to be the 3CX client (v18 + v20) and not the TAPI driver. When accepting a call that has been transferred internally in attended/consultative mode, a new TAPI event is generated, but it only shows the internal number and not the number of the external caller.

 

[ThomB_3CX]

@little ghost we have a fix for this in the new beta we released today. Please check it out
https://www.3cx.com/blog/releases/windows-softphone-chat-beta/

 

[little ghost]

Thanks, @ThomB_3CX

I will test it and report back. If it works, that would be great news. Is there already an MSI file for the beta? This way, I could also run tests in an RDS environment.

 

[NicholasP_3CX]

Thanks, @ThomB_3CX

I will test it and report back. If it works, that would be great news. Is there already an MSI file for the beta? This way, I could also run tests in an RDS environment.

The MSIX file will be released when it is a Final Release. In the link posted above by @ThomB_3CX there is a procedure on how to register for the Beta program.

 

[toniSanta]

Hi, I installed the new version 20.0.546.0. There is no new version of the TAPI-installer. The problem of the missing external calling number for calls transfered from one internal to another is still present. See attached screenshot of a TAPI-events-monitor. You see the internal numbers of 210 transfering a call to 212, but when 212 connects to the external call "09.48:26 - OnConnected" the Line.CallerID is empty.
Toni

 

[little ghost]

Hi @toniSanta, @NicholasP_3CX & @ThomB_3CX,
I conducted various tests with the new Windows client and can confirm Toni's results. Even with the new client, the TAPI events are not correctly generated when forwarding a call in attended/consultative mode, and on TAPI only the number of the phone that forwarded the call continues to appear.
Please help...