The XPhone Unified Communications server can also be operated as a full stand-alone TAPI server. This establishes a direct link from your business applications to your PBX. On it you can use telephony functions in your company applications and thus optimise your business processes.
Depending on the features and functions of your TAPI-enabled application, the following functions are supported:
TAPI 1.4
TAPI 2.0
TAPI 2.1
TAPI 3.0
Note:
Note:
Notes:
XPhone Unified Communications in 2011 does not support the following systems and applications:
Note: If you want to upgrade from XPhone UC Server V3 to XPhone UC Server 2011, you have to install at least XPhone UC Server V3 Build 328.
Upgrade to Build 328 available.
The CPU recommendation based on the current Intel Processors classification. XPhone UC Server 2011 contains Microsoft .NET 3.5, Microsoft SQL Express (alternative use of: existing Microsoft SQL Server ) and an integrated Webserver (alternative use of: existing Microsoft IIS Webserver).
The XPhone Unified Communications server can be used as a full TAPI server for connecting third-party applications to the PBX.
For operation you need an XPhone UC server licence and, depending on your solution, possibly also the following other licences:
Of course, both licenses can be combined.
TAPI is an interface for Microsoft's Windows operating system. This interface is an integral part of Windows and is used for the provision of telephony features for Windows applications.
The XPhone TAPI Server is directly connected to the PBX. This communicates with the TAPI driver (TAPI Service Provider - TSP) on each workstation. The XPhone TAPI Service Provider in turn makes phone functions available to Windows applications.
The TAPI Service Provider (TAPI driver) is a software used to control the telephony hardware. Here, the TAPI functions are translated into a language understandable to the terminal.