For larger PBX systems, usually a so-called 3rd party TAPI driver is provided. This TAPI driver provides all TAPI lines of the telephone system in the Windows system.
The Windows Server operating systems include a built-in TAPI Server. This can distribute server-side TAPI lines to several client PCs in a Windows domain and set user rights.
Schematic system configuration
TAPI: TAPI Interface Microsoft TAPI service: In Windows Server integrated TAPI service (TAPI server). Hint: On the client PC works in the background and a client TAPI Service too. This was not shown for simplicity. 3rd Party TSP: TAPI driver from the manufacturer of the telephone system. TSP= Telephony Service Provider Microsoft Remote TSP: The Remote TAPI driver belonging to Microsoft TAPI server.
Configuration of the Microsoft TAPI Server
- 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.
- Open the "Telephony" Management Console by: [Start > Settings > Control Panel > Administrative Tools > Computer Management > Services and Applications > Telephony];
or <Execute> "tapimgmt.msc".
- Right click on your server-item and select "Properties".
- 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.
- Click on the driver of the PBX => on the right side the TAPI-Lines (line name) of the driver become visible.
- TAPI Line-set permissions per user:
- In the right window click a "Asterisk 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:
- Hint: Via the command line tool "tsecimp" the assignment of user to TAPI line can also be done via XML file.
Documents of Microsoft®:
- Installation and configuring of a telephony server for the client access
- Help to tcmsetup
- Help for tsecimp
Installation of the client system (Windows)
- Open the DOS-Promt via [Start > Run... > "cmd"].
- Enter the following command (SERVERNAME = computer name of Windows Server):
tcmsetup /c SERVERNAME
runas /user:DOMAIN\Administrator "tcmsetup /c SERVERNAME"Hints:
- They must be logged in with administrator's rights on the client PC.
- the client PC must be registered in the same domain like the server (or an trusted domain).
TAPI Server is also available from alternative providers. These use the TAPI interface like a "normal" TAPI application and make the TAPI lines available in the network. On the client computers a Remote-TSP which belongs to the scope of supply of the TAPI server is to be installed. The Remote-TSP communicates on the local network with the server.
Schematic system configuration
- The Estos TAPI Server is relatively easy to instal and to configure. It do not need a server operating system, so you can install it also on Windows Client operating systms.
- For two clients the server can be used free of charge.