Terminal Server Installation

On this page
  • Installation
  • Driver Configuration
  • Configure Microsoft TAPI environment
  • TAPI-Test

a) Installation

  1. Download and extract xtelsio_TAPI_for_snom_setup.zip.
  2. Run setup.exe via [Start > Settings > Control Panel > Add or Remove Programs > Add].
  3. Follow the dialog sequence.

Hints: The administrator has to install the TAPI driver only once on the Terminal Server. An installation "per user" is not possible.


b) driver configuration

  1. Basic information for driver configuration.
  2. On a terminal server per user is a TAPI line to add and configure.
    • The settings are stored in the configuration directory of the TAPI driver.

c) Configure Microsoft TAPI environment

  1. Log on as a local administrator on the Windows server.
    Warning: The Domain Admin on a 2008 server has no rights for the "telephony" management.
  2. Open the "Telephony" Management Console by: [Start > Settings > Control Panel > Administrative Tools > Computer Management > Services and Applications > Telephony];
    or <Execute> "tapimgmt.msc".
  3. Right click on your server-item and select "Properties".
  4. In "Properties" dialog you have to "Enable telephony server". This is necessary so that you can set the line privileges for each user.
    To activate the telephony server an Active Directory service is required. If Active Directory is not available, you may see the error message "62 791" or "62 795".
    If the telephony server service is not enabled, all local users see all TAPI lines.
  5. Click on the driver of the PBX => on the right side the TAPI-Lines (line name) of the driver become visible.
  6. TAPI Line-set permissions per user:
    • In the right window click a "snom Line" with the right mouse button and select "Edit User".
    • Add all users that need permissions for this TAPI Line.

Notes about the "tsec.ini" file:

  • The Windows TAPI Server stores the User/TAPI-line mapping under "C:\WINDOWS\TAPI\tsec.ini".
  • Example: Two TAPI lines of the TAPI provider with the ProviderID=5 are assigned to the user "tmiller". The first line has the dwPermanentLineID=2 and the second line the dwPermanentLineID=4. The ProviderID is read from the following registry entry: "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Telephony\ Providers\ ProviderIDX". The dwPermanentLineID provides the TAPI driver via lineGetDevCaps ().
    The corresponding entry in "tsec.ini" would be as follows:
    • [Domain\tmiller]
      FriendlyUserName=Tom Miller
      Lines=5,2,5,4
  • Hint: Via the command line tool "tsecimp" the assignment of user to TAPI line can also be done via XML file.

d) TAPI-Test

  • To test the TAPI driver, you can use the tool "phone.exe".