Howto:TerminalServer

Applies To

This information applies to

• All PBX installations with CTI

More Information

Problem Details

Terminal Server Installations do create some difficulties with CTI implementation. This is because Windows CTI application are based on the TAPI service provider (TSP), which is a system component shared by all users and thus by all Terminal Server sessions. As a result, user specific TAPI configurations are not possible.

User specific configurations must be implemented by the CTI software residing on top of TAPI

Estos ProCall

The ProCall Enterprise version supports Terminal Server environments.

innovaphone Companion

The innovaphone Companion supports Terminal Server. The Terminal Server version needs to support .Net 2.0.

Running 1st Party Applications, e.g. Outlook, directly on top of TAPI in a Terminal Server Environment

The TAPI services are available to all users in all Terminal Server sessions. TAPI thus can be used uniformly by all users. In an innovaphone environment, you need to make sure that the TSP has access to all lines that may be used by any TAPI application.

The drawback of this approach however is, that all TAPI client applications may potentially use all of the TAPI line ressources (that is, phones). With Outlook for example, each user can have his personal telephone line configured to be used when making calls from Outlook. However, this is a user-specific configuration setting that can be changed by the user itself. So there is the potential risk of an user re-configuring Outlook's TAPI settings and then make calls on behalf of any other user in the system.