Configure the Microsoft TAPI server

The TAPI-Server is a free part of every Windows server and is already installed. But it has to be activated. Please activate the telephony service directly on the server as an administrator.

1. Activate the telephony server

    1. At the server under [Start] on [Execute], there the command mmc and click [OK].
    2. In the “Console window, click [File] and there [Snap-Add/Remove… Ctrl+M].
    3. Add the Snap-Ins “Services and “Telephony.
    4. In the “Console Tree you now have the “Services.
    5. Navigate to the “Telephony service”, right click and select [Properties].
    6. In the “Login” tab, check whether data exchange via the local system account is enabled:
      Stop services
  1. If yes, close the properties by clicking on [OK]. Otherwise, please check the box as shown in the screenshot above.
  2. In the "“Console Root" expand the entry "“Telephony" in the tree structure.
  3. As a rule, only the current server is now displayed. If not, select the currently used server.
  4. Right-click the server and click [Properties].
  5. In the “Setup tab you ticked the Enable “telephony server box. This must be set:
    Set up TAPI server
  6. Usually, a user with a password should be entered in the “Account Information” field. If not, please select the user “LocalSystem” via [SelectUser] and input the password. Alternatively, you can also use another administrative user.
  7. Close the properties by clicking on [OK].
  8. Close the console. Saving is not necessary.

With Windows Server 2008 R2 we often received the error message “Es no call available” (“No call appearance available”). This can be remedied by making changes to the AD. We recommend this guide for this https://www.act-computer.de/hilfe-tipps/item/windows-server-telefonie-server-aktivieren

2. Install TAPI driver on the server

Connect the system to the server and install the appropriate one TAPI driver.

3. Restart the server

This is mandatory for the service & #8220; Telephony & #8221; can start correctly.

4. Assign users

  1. At the server under [Start] on [Execute], there the command mmc and click [OK].
  2. In the “Console window, click [File] and there [Snap-Add/Remove… Ctrl+M].
  3. Add the Snap-In “Itelphony”.
  4. In the "“Console Root" expand the entry "“Telephony" in the tree structure.
  5. As a rule, only the current server is now displayed. If not, select the currently used server.
  6. If the installation of the TAPI- driver was successful, you will see the TAPI- driver in the tree structure and your TAPI- lines on the right.
  7. Optionally, a TAPI-Line can be restricted for certain users: Right-click on the respective TAPI-Line and click on [Edit User] to add users there
  8. Close the console. Saving is not required

6. Get the TAPI lines from the server to the client

  • If you have administrative rights: On the client under [Start] on [Run], there the command tcmsetup / c [YOURSERNAME] and click [OK].
  • If you do not have administrative rights: On the client under [Start] on [Run], there the command runas / user: YOURDOMAINNAMEADMINISTATORNAME "tcmsetup / c YOURSERNAME" and click [OK].

Possibly. it is necessary to restart the telephony service on the server so that the TAPI lines appear on the client

Watch out: Since Windows 10 does not shut down properly for the so-called quick start, the lines are available after restarting the client PC, but if Windows is shut down and the PC is then restarted, the lines are missing. To solve this, on Windows 10 go to “>Control Panel\All Control Panel Items\Power Options\System Settings” on each client, click “Some settings are currently unavailable”, uncheck “Turn on fast startup (Recommended)” and confirm with Save changes. After that the problem is fixed:

7. Installation of TAPICall on the clients

Install - if not already done - on the clients TAPICall.

8. Selection of TAPI Lines on the Client

TAPICall must be restarted after TCMSetup. This is done simply by exiting Outlook. Wait until TAPICall is in the waiting state and then restart Outlook.

Click on the TAPICall-Phone icon in the bottom right next to the clock, then on [Settings]. In the tree structure click on [TAPI-Driver Selection] and you should now see the TAPI-Lines from the server. Choose your extensions or TAPI-Line. Click on [Finish] and test by starting a call with F8.

If no TAPI-Lines from the server appear in TAPICall, the TCM-Setup- command has not completed successfully or your firewall is blocked. Call for support please +49 (6422) 89800-50 to or write to support@convergit.de

9. Further information

Source: http://support.microsoft.com/kb/259375/en-us

Please note that for these instructions you need a telephone system whose driver creates several devices. If the driver creates only one device (, such as TAPI 120), only this one device can be distributed in the network.

Suitable plants are, for example:

Auerswald   With / without LAN port
Panasonic   With / without LAN port
older telephone systems   via USB, serial or via S0

10. Error 1079 when starting the telephony service on windows server

The following KB page is available from Microsoft: https://support.microsoft.com/en-us/help/2478117/services-fail-to-start-and-you-receive-an-error-1079-on-a-computer-tha

There is a FixIt tool available there, but in the end it is these two steps that can also be carried out manually, or often have to, because the FixIt does not solve all problems.

10.1 Switch telephony service from “local system to“ local service ”

A possible cause of the error is that the service account assigned to the telephony service is not Local service reads. However, only this account has the necessary rights to start the service, the account Local system rights are missing.

To change it, do the following:

  • start the services console (Windows-R-> services.msc-> Enter)
  • there locate the telephony service and double click
  • on the rider Log In switch to the option This account:
  • specify as username: NT AUTHORITHY \ Local Service (This must always be specified in English regardless of the operating system language)
  • delete both password fields

10.2 Register tapisrv-DIenst as an independent process

The telephony service is usually configured to run in a single svchost process with various other services. Microsoft followed this approach because in the past, systems often could not provide enough resources to run each service as a separate process.

However, since all services that are summarized in this way run under the same account, this is not always the correct procedure for the telephony service. We can only assign our own account safely if the service runs as a separate process. This becomes clear in the registry here

The group netsvcs contains the tapisrv-Entry (tapisrv is the always valid internal service name for the telephony service, which is translated differently depending on the language), ie the telephony service is managed as part of this group. In Task Manager, this can be seen as a single process for all services:

In an admin prompt, you can also determine the status of the telephony service with the following command:

      sc query tapisrv

This outputs part of the service properties:

It stands here as TYPE the value 20 WIN32_SHARE_PROCESS, then the telephony service is not carried out independently.

This can be changed as follows, also with the sc command in the administrative command prompt:

      sc config tapisrv type = own

Warning, the space between type = and own must be specified as s. yellow arrow:

The feedback on the next line should be the word SUCCESS contain.

Another query with sc query tapisrv then results in TYPE the value 10 WIN32_OWN_PROCESS, This means that the telephony service will in future always run as a separate process that can also be seen as such in the Task Manager; unfortunately not as Tapisrv.exe, but as shown in the service properties dialog with the following command line:

In the Task Manager, a telephony service then appears as an independently running process as one of several lines:

When the telephony service is ended, one of the two lines disappears. The PID of the telephony service can only be found via Task Manager by first stopping the service, then remembering the PID of the remaining NetworkService-svchost instance, and then checking which PID is added after the telephony service is restarted is.