XPhone TAPI Server
The XPhone Connect Server can also be operated as a full stand-alone TAPI server.
The TAPI server provides TAPI lines via the XPhone Connect TAPI client, which you can install on a Windows client or terminal server.
On it you can use telephony functions in your company applications and thus optimise your business processes.
Features
- Dial with a mouse click directly from within your application
- Call notification: XPhone TAPI Server notifies your application of incoming calls and transfers the caller's phone number to your application so that it can e.g. open the relevant contact record
- Answer by mouse click directly from within your application
- Provision of telephony states: XPhone TAPI Server transmits information to your application regarding various telephony states, e.g. idle, busy, consultation, etc. and thus supports journaling in your application.
- Security: The special security concept ensures that each user can only use their own TAPI line – the best protection against misuse by unauthorised persons.
Please note: The functions depend on the features of the respective TAPI-enabled application.
Supported TAPI interfaces
- TAPI 1.4
- TAPI 2.0
- TAPI 2.1
- TAPI 3.0
Licensing
- XPhone Connect Server
- XPhone Connect TAPI lines (per user)
Your benefits
- You use powerful CTI functions from within your TAPI-enabled applications regardless of the XPhone front ends.
- No need to install & configure local TAPI drivers
- The client component communicates directly with the XPhone TAPI Server on the network. Configuration and time-consuming set-up of a Microsoft Remote TAPI server (Remote TSP) are not required. The XPhone Server takes over the function of the TAPI server and is connected to the PBX via CSTA or a central TAPI interface.
- Use possible in networked ICT environments even with different phone systems
Drivers
TAPI drivers for 32 Bit and 64 Bit Windows
- Genuine 32-bit/64-bit TAPIService Provider
- Microsoft Windows 10 Pro/Enterprise (32/64 Bit)
- Microsoft Windows 8.1 Pro/Enterprise (32/64 Bit)
- Microsoft Windows 7 SP1 Pro/Enterprise (32/64 Bit)
- Microsoft Windows Server 2019 (64 Bit)
- Microsoft Windows Server 2016 (64 Bit)
- Microsoft Windows Server 2012 R2 / 2012 (64 Bit)
- Supports Terminal Server and Citrix Metaframe environments
- MultiSite-/MultiVendor-compatible
The system requirements for software and hardware of the TAPI server can be found under the following link: System Requirements XPhone Connect
What is TAPI?
TAPI is an interface for Microsoft & Windows operating systems. This interface is an integral part of Windows and is used for the provision of telephony features for Windows applications.
How does a TAPI server work?
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.
What is a TAPI Service Provider (TSP)?
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.
All TAPI functions at a glance
lineAccept | | lineGetAppPriority |
| lineMonitorDigits | | lineSetDevConfig | |
lineAddProvider |
| lineGetCallInfo |
| lineMonitorMedia | | lineSetLineDevStatus | |
lineAnswer |
| lineGetCallStatus |
| lineMonitorTones | | lineSetMediaControl | |
lineBlindTransfer |
| lineGetConfRelatedCalls |
| lineNegotiateAPIVersion |
| lineSetMediaMode | |
lineCallbackFunc |
| lineGetCountry |
| lineNegotiateExtVersion |
| lineSetNumRings | |
lineClose |
| lineGetDevCaps |
| lineOpen |
| lineSetStatusMessages |
|
lineCompleteCall | | lineGetDevConfig | | linePark | | lineSetTerminal | |
lineCompleteTransfer |
| lineSetCallTreatment |
| linePickup | | lineSetTollList | |
lineConfigDialog | | lineGetIcon |
| linePrepareAddToConference | | lineSetupConference |
|
lineConfigDialogEdit | | lineGetID |
| lineRedirect |
| lineSetupTransfer |
|
lineConfigProvider |
| lineGetLineDevStatus |
| lineRegisterRequestRecipient |
| lineShutdown |
|
lineDeallocateCall |
| lineGetMessage |
| lineReleaseUserUserInfo | | lineSwapHold |
|
lineDevSpecific |
| lineGetNewCalls |
| lineRemoveFromConference |
| lineTranslateAddress |
|
lineDevSpecificFeature |
| lineGetNumRings |
| lineRemoveProvider |
| lineTranslateDialog |
|
lineDial |
| lineGetProviderList |
| lineSecureCall | | lineUncompleteCall | |
lineDrop |
| lineGetRequest | | lineSendUserUserInfo | | lineUnhold |
|
lineForward |
| lineGetStatusMessages |
| lineSetAppPriority |
| lineUnpark | |
lineGatherDigits | | lineGetTranslateCaps |
| lineSetAppSpecific |
|
|
|
lineGenerateDigits |
| lineHandoff | | lineSetCallData |
|
|
|
lineGenerateTone | | lineHold |
| lineSetCallParams | |
|
|
lineGetAddressCaps |
| lineInitialize |
| lineSetCallPrivilege |
|
|
|
lineGetAddressID | | lineInitializeEx |
| lineSetCallQualityOfService |
|
|
|
lineGetAddressStatus |
| lineMakeCall |
| lineSetCurrentLocation |
|
|
|
