Multiline TAPI on terminal server works only after Dialer is started

[King software]

The client of our CRM application has 3CXPhone which works in regular Windows
but has problems in terminal server environment on Windows server 2012 R2.
In terminal server TAPI works only after starting Windows Dialer utility.

What is 3CX missing without the Dialer?

 

[edossantos]

Maybe your client application is not properly initializing TAPI, and then it needs that another app does the job...

TAPI is loaded by a Windows service, so it's available for use by any application. Then TAPI connects to the 3CXPhone for Windows client to make calls and receive notifications.

 

[King software]

Maybe your client application is not properly initializing TAPI, and then it needs that another app does the job...

TAPI is loaded by a Windows service, so it's available for use by any application. Then TAPI connects to the 3CXPhone for Windows client to make calls and receive notifications.

CRM application does TAPI initialization using ITTAPI.Initialize call regardless of Windows version and environment.
It works ok for a regular Windows environment.
There is something special about terminal server environment that creates a problem.

3CX PBX version is 15.5.13103.5 .
3CX (Plugins) Tapi driver version: 15.0.930.636
3CX Phone for Windows version: 15.5.12227.5

 

[King software]

Log attached

 

[King software]

It looks like 3CX TSP behaves slightly differently under terminal server,
namely, it does not properly initialize TAPI3 which our CRM uses.
Not properly initialized TAPI3 device does not show Audio as media capability.
Starting a TAPI2 application does the trick.
A test at the client site will confirm or disprove this.

 

[King software]

Client test confirms, that with 3CX under terminal server after TAPI3 initialization
Audio device property is not set. A possible workaround is to ignore this property as actual call does work.

 

[King software]

Maybe your client application is not properly initializing TAPI, and then it needs that another app does the job...

TAPI is loaded by a Windows service, so it's available for use by any application. Then TAPI connects to the 3CXPhone for Windows client to make calls and receive notifications.