I have a snom D785 phone which works fine.
Then I have installed the 3CX Windows Client on a Windows 10 Client.
Configured the 3CX Client by sending the config email.
Now when I make the very first call (after the first provisioning) from the 3CX Client, the phone makes the right call. Let say calling ext. 10
If I make the next call from the Windows Client to ext. 11, the ext. 10 is called firstly, when canceling the call via CTI, the ext. 11 will be called afterwards.
It could be, that the second "real" call is started delayed. So after some minutes, the phone is then calling the previously entered number.
CTI functions like showing incoming call, transfer, parking… works like it should.
Making a call through the webclient will work, but this is not an option.
CTI Mode for Yealink T46S works like a charm on the same system.
Versions:
snom D785: 10.1.27.1
Windows 10 Pro: 1803 x64
3CX PBX: 15.5.15502.6
3CX Client for 3CX Phone System: 15.5.12227.5
Then I have installed the 3CX Windows Client on a Windows 10 Client.
Configured the 3CX Client by sending the config email.
Now when I make the very first call (after the first provisioning) from the 3CX Client, the phone makes the right call. Let say calling ext. 10
If I make the next call from the Windows Client to ext. 11, the ext. 10 is called firstly, when canceling the call via CTI, the ext. 11 will be called afterwards.
It could be, that the second "real" call is started delayed. So after some minutes, the phone is then calling the previously entered number.
CTI functions like showing incoming call, transfer, parking… works like it should.
Making a call through the webclient will work, but this is not an option.
CTI Mode for Yealink T46S works like a charm on the same system.
Versions:
snom D785: 10.1.27.1
Windows 10 Pro: 1803 x64
3CX PBX: 15.5.15502.6
3CX Client for 3CX Phone System: 15.5.12227.5
