State of knowledge

August 2020, ProCall 6 Enterprise and ProCall 7 Enterprise

This article explains the basics of installing ProCall Enterprise in terminal server and Citrix environments. The appendix contains two detailed step-by-step instructions for the use of ProCall in terminal server environments (only in German).

Technically compatible system TAPI drivers (e.g. ECSTA) can also be installed on Terminal Servers (please consider system requirements of the manufacturers), but this is not recommended, since all users of the terminal server then have access to all TAPI lines. Therefore, we recommend installing the TAPI driver and the UCServer on a dedicated application server for use with ProCall Enterprise, because:

  • the terminal server basically functions as a client system
  • the rules of the UCServer can be ignored and lead to incorrect telephony behavior
  • all TAPI-enabled applications use their TAPI functionality without regard to the rules of the UCServer

TAPI-capable applications on the terminal server can be made available to TAPI lines remotely via the Multiline TAPI driver (part of the ProCall Enterprise product package).

  • Please do not use the extended remote TAPI driver of the ProCall Client, as it only provides one extension in the user context for the entire terminal server.

If some users of the terminal server are not supposed to use ProCall, then please distribute the following registry key, which checks for an activated ProCall user account when the ProCall client is started on the UCServer If there is no active account, ProCall will be terminated.

  • Registry key for the conditional program start, depending on an active UCServer user account: 
    • Name: ShutDownByMissingServerUser
    • Type: REG_DWORD
    • Value: 1
    • Infos: 0=Inactive (default) | 1=Active