CTI Mode

[manfer]

Does CTI Mode work on 3CX v16?

I'm testing just now and is doing MakeCall and not CTI. But I don't recall if connected via STUN or SBC should work or not and I can't test locally just now.

What is even worst is that not only is not working as CTI but MakeCall, besides if I refuse the MakeCall without hangup the deskphone the call gets stuck on 3CX server. The 3CX server continues showing the call on ringing state when it is not. The extension stays busy.

 

[manfer]

The call stuck on the Server is because of having Android client installed on smartphone and closed ignoring push. If I open Android client and a refuse the call on deskphone and android client then the call is correctly finished on the server.

Is this by design? If the android client is closed (ignoring push) the Server tries to ring it anyway, not stop?

 

[manfer]

I can reproduce same behavior calling from other extension to the extension that is provisioned on a deskphone and on an android client.

If the android client is closed (ignoring push) and I refuse the call on the deskphone, the call gets stuck on the server in ringing state until the other party hangs up.

Does the android client unregister when closed (ignoring push)? I suppose that would solve this problem.

 

[manfer]

Does CTI Mode work on 3CX v16?

About CTI the deskphone was not marked as provisioned. I reseted the deskphone and provision it again and now CTI from 3cx phone for windows and webclient CSTA are working properly.

The other issue looks just a problem on the android client. I have joined beta and installed android client v16.0.0.21 and same issue when I exit (ignoring push)

 

[YiannisH_3CX]

Hello @manfer

Glad to see you were able to sort the issue with CTI. Regarding the Push functionality, when a client is set to ignore push this is done locally on the device and not on the server. Since the extension is setup to receive Push and the device is registered to Push, the PBX will try to reach the client until the ring timeout ends and the call reaches the destination if no answer of the extensions forwarding rules. So the behaviour you are describing is the expected one.

 

[manfer]

Hello @manfer

Regarding the Push functionality, when a client is set to ignore push this is done locally on the device and not on the server.

Hi @YiannisH_3CX

Thanks for clarification.

I will stop using "exit (ignore push)" them. I will instead go into Options->Accounts and deactivate the account instead. Less usable to have to deactivate and activate account each time but that's the behaviour I want when sharing extension with deskphone.