• V20: 3CX Re-engineered. Get V20 for increased security, better call management, a new admin console and Windows softphone. Learn More.

Multiline TAPI on terminal server works only after Dialer is started

Status
Not open for further replies.

King software

Joined
Oct 23, 2018
Messages
6
Reaction score
0
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?
 
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.
 
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
 
Log attached
 

Attachments

  • 3CXPhoneForWindows(1).log
    43 KB · Views: 3
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.
 
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.
 
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.
 
Status
Not open for further replies.

Getting Started - Admin

Latest Posts

Members Online Now

Forum statistics

Threads
141,622
Messages
748,858
Members
144,737
Latest member
damiano giannini
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.