To install the CTI Client for multiple users on a terminal server, a few steps in a particular sequence must be executed.
- Install CTI Client
- Configuring CTI Client
- "provide/release" CTI Client configuration for all users
Run setup.exe and follow the dialogs.
If the setup does not automatically recognize the Terminal Server environment, you can set the entry "TerminalServer=1" in the "SETUP.INI".
In the dialog "Terminal Server Mode", the installation mode "Terminal Server" is to select. The following criteria are applied:
- The Terminal Server is automatically placed in the "Installation" mode (change user /install).
- The installation is done automatically for all users.
- As of version 3.0.037, the "CTI Client TAPI Connector (MultiUser)" also works in a Terminal Server environment.More infos...
- The startup of the CTI Client is initially locked for all other users, that is, after the installation initially only the user (administrator) who performed the installation, may start the CTI Client to configure it if necessary. The release for all users is done only after completing configuration via "Setup Generator".
In the dialog "Select Working Directory" you can set the path to the user working directory. Each user needs his own work directory.
Example: "C:\Users\%USERNAME%\Documents and Settings\My Documents\xtelsio_CTI_Client_data"
In the dialog "Optional Components" you can install the Outlook Add-In, when required. The activation of the Add-In is user-related. In the CTI Client the Add-In can be activated/deactivated via [Options > Outlook].
In the dialog "Program Shortcuts" you can set the program shortcuts to be created.
By pressing the "Finish" button the installation is executed.
After successfully completing the installation and before you start the CTI Client for the first time, you should put the terminal server back in "execution mode" (change user /execute).
Before the CTI Client is "enabled" for all users, he should first be configured as it should be run later on the terminal clients.
Then starting the application for first time, a dialog appears, that helps you to configure the TAPI devices and phonebook folder.
Important: To be able to assign every user an individual TAPI device, first a TAPI device must be assigned and configured for the administrator. Guide to TAPI Configuration...
Additional configuration steps that may necessary, are
Set permissions for TAPI lines in the Windows system: If you are using a Multiline TAPI driver in conjunction with the CTI Client, you can set the user authorization for TAPI lines using the Windows Telephony service (TAPI Server). For information, see:Network TAPI.
Protect configuration with administration password: You can password protect the configuration as a whole or partially. It is also possible to block, to disable or hide individual functions, menus or parameters for the user. These settings are available under [Options > Administration / Extended Settings]. For more information on administrator settings...
Enable/disable Components and Plug-ins: In the dialog [Options > Customize > Components and Plugins] you have the option to turn off unneeded components and thus to save resources.
Customize window layout: Determine which dialogs are displayed in the main application window and if so, how they were arranged. In the basic configuration, a Desktop-Sidebar is included which can also be pre-configured or even turned off.
For more information about window management...
Manage TAPI Profiles: Under [Options > Administration > Local Profiles / Terminal Server] you can make settings for the TAPI profiles. In this dialog you have to select "Terminal Server" or "Terminal Server Farm" as "Environment".
More information to local profiles...
For more information to Terminal Server options...
Mobile Users: For mobile users who log on to different terminals and thereby gain access to the local telephone next to this terminal, the option "%CLIENTNAME%" is to select under [Directory name for local TAPI profile].
Terminal Server Farm: For a terminal server farm, where users are assigned to terminal servers depending on the load balance, the value "Terminal Server Farm" is to select for [Environment].
To provide the CTI Client configuration for other users, start the Setup Builder via the main menu [File > Administration > Generate Setup ...].
On the first dialog, select "Terminal Server Configuration" and if you want to provide central telephone books and/or notes, the option "Expanded to a central configuration directory".
For more help on this topic can be found at:
- Create Setup
- Help for using the setup generator dialogs
- Central configuration directory
- Working Directory
Follow the dialog-wizard with the dialogs:
- Central configuration directory
- Setup Settings
- Speed Dial
- Working Directories
- Create Setup
- Adapt existing installation
On the last dialog, the path to the created "working directory template" is displayed. Open this folder, if necessary, make further manual adjustments to the configuration files.
Enable "CTI Client Start" for other terminal user: Use the appropriate prompt when closing the Setup Generator or the "Terminal Server Settings" under [Options > Administration].
To test the configuration, you can unlock it for individual terminal user. Add the appropriate user names in the file "%PROG_DIR%\cfg\admin.xml" under "AllowStartForUsers" separated by a comma.
Example: AllowStartForUsers="Administrator, User1, User2"
1.) Can the CTI Client, installed locally on the client machine, dial a phone number which is shown in the terminal window?
Answer: Yes. For this feature you have to activate [Options > Telephony > Dialing from within other applications > via mouse click on any phone number].
This way can be used if the TAPI devices are available only locally on the client machine.
Restriction: Only dialing is supported. Within the terminal session there is no reaction on incoming calls.
2.) Can the CTI Client be used as a SIP-Softphone in a terminal session?
Answer: In principle, yes. Under the RDP settings / Local resources, the audio recording and playback is to be activated. You would have to test whether the audio quality meets your requirements. Should there be unacceptable speech delays or audio dropouts, a switch to physical SIP telephones would be recommended.
- Call answer on the headset is not supported.
- Call signaling via a second loudspeaker is not supported.