a) Installation |
- Run setup.exe via [Start > Settings > Control Panel > Add or Remove Programs > Add].
- Enter the program directory
- On a 64 bit server the CTI Client is installed in the (x86) program folder, because it is 32 bit application.
- In the dialog "users" the option "Install application for all users" is to activated.
- In the next dialog the user's working directory is to be selected.
Hints:- Every user need this own working directory.
- The following variants are possible:
- They declare a variable path with the place holder "%USERNAME %".
Example1: C:\Users\%USERNAME%\Documents and Settings\My Files\xtelsio_CTI_Client_data Example2: C:\Users\%USERNAME%\Documents\xtelsio_CTI_Client_data
- They declare a path to the user's home drive.
Example: Z:\xtelsio_CTI_Client_data
- In the dialog " License Install" you can enter an already available license or you choose the 30 days test mode. You can enter licenses also later in the CTI Client via [Options> License].
- In the dialog "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].
The "CTI Client TAPI-Connector" is not supported in a terminal server enviroment and, hence, should not be installed. Probably, you will not need the ActiveX telephony component.
- In the next dialog the program shortcuts are still to be selected and with [Finish] you have to start the installation.
|
b) Master Configuration |
On first application start you are asked whether you want to carry out a first configuration of the TAPI device and address folders. Hint: They can carry out the settings also later.The settings which you carry out as an administrator are stored in the working directory of the administrator. You can provide these settings later as basic settings for the other users.
The installation under the administrator's account should be used only for the "master configuration", and not for work. |
|
c) Protect/hide configuration for the users |
Problem1: You want to prevent that the users change the basic configuration.- Solution: You can protect the configuraiton via [Options > Customize > Extended Settings > Lock/hide Application].
|
Problem2: You want to disable single menu items or define standard parameters.- Solution: The settings can be carried out in the file "PROG_DIR\cfg\customize.ini".
In addition you find tips in the program directory under "cfg\templates\readme.txt".
|
|
d) Automatic post-configuration |
Problem: Some settings of the master configuration should be overwritten later automatically according to user/terminal. For example, the user has to get his TAPI-Line and not those of the administrator.- Solution: For this exists a file "cfg/auto_config.ini" in the working directory. You find tips for the use of this file under "cfg/auto_config_readme.txt".
- Alternatively you can preconfigure the user-related working directories also by hand. See below.
|
|
f) Manage TAPI Profiles |
Under [Local Profiles / Terminal Server] You can make adjustments to the TAPI profiles. In this dialog you have to select "Terminal Server" or "Terminal Server Farm" as "Environment". You find additional infos at: Terminal Server Options |
Mobile users |
Problem: The users log in according to demand in a terminal and, besides, should get access to the local phone beside this terminal.- Solution: Under [Options > Local Profiles / Terminal Server > Directory name for local TAPI profile] select "%CLIENTNAME%".
|
Terminal Server Farm |
Problem: The users are assigned by load balancing to a terminal server from the server farm.- Solution: In this case set [Options > Local Profiles / Terminal Server > Enviroment] to "Terminal Server Farm".
|
|
g) Provide the Master Configuration as default for other users |
Preparations: In the master installation a TAPI device and the phone books should be configured. => Please run [File > Create Setup...] and then select "Terminal Server". Follow the dialog sequence.
Functionality: A folder "auto_config\workingDir" is created in the CTI Client program directory.As soon as a user runs the CTI Client the first time, the contents from "auto_config\workingDir" are copied in his own user's profile. Which destination path is used, defines the parameter "working_dir" in the file "auto_config\auto_config.ini". For example: working_dir=%MYDOCUMENTS%\xtelsio_CTI_Client_Data\ |
Hints:- The CTI Client stores in the Registry under "HKEY_CURRENT_USER\Software\xtelsio CTI Client" the working directory used last.
- An autoconfiguration is only only carried out if no working directory was found. Criterion is that the directory contains the main configuration file "config.dat".
- At start the CTI Client tries to load the working directory used last. Order:
- If for the program shortcut a working directory is assigned under "Run in", then use it.
- Use directory according to registry.
- Use the directory from "auto_config\auto_config.ini".
- If no working directory was found, is supposed that the settings from "auto_config\workingDir" are to be taken over.
|
|
h) How to create and configure the user-related working directories manually. |
- Create first a master configuration according to point g).
- The preconfigured working directory (template) is created under:
"C:\Program Files\xtelsio_CTI_Client\auto_config\workingDir"
- As an example configuration it is assumed:
- The users use as a Home disk drive Z:\
- As a user-related CTI Client working directory is used "Z:\xtelsio_CTI_Client_Data".
- As a profile folder it is used "local_profiles\TS_ALL" (according to point f).
- The folder "workingDir" is to be copied in the home disk drive of every user and to rename in "xtelsio_CTI_Client_Data".
- To customize the TAPI configuration now, you can edit in the folder " ...\xtelsio_CTI_Client_Data\local_profiles\TS_ALL\" the available INI files.
|
h.1) Example: Customize Settings of "Snom Line1" |
If you use "Snom Line1" as a TAPI device, the following parameters are to be adapted in the file "snom_lines.ini":- Every user needs its own TCP port for "Actions URL". Then the standard port 8080 can be set consecutively with 8081, 8082....
- The existing Snom IP address is to be substituted with the IP of the Snom phone of the user.
- If the access to the Snom needs a username and password, then set the parameters "username=" and "password=".
|
FAQ 1: |
Can one instal the CTI Client locally on the client machine and dial with it a phone number which is shown in the terminal window? |
A: Yes. For this feature you have to activate [Optiones > Interworking > 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. |
FAQ 2: |
Can the CTI Client be used as a SIP-Softphone in a terminal session? |
A: No, under the supposition that the local audio-devices of the client are not available in the terminal session. |
|