Windows TAPI CTI integration für web-enabled applications - click-to-dial für SNOM phones and Asterisk. HTTPTAPI allows you to map TAPI requests to HTTP requests, adaptable to every web-enabled application.
HTTPTAPI requires a license to activate the desired number of lines. Request a trial license for HTTPTAPI now!
NEW: Buy HTTPTAPI online and you will receive the license key immediately after the payment.
HTTPTAPI is a TAPI service provider (TSP) für MS Windows. HTTPTAPI enables you to map the dial requests of TAPI applications (e.g. MS Outlook) to HTTP request. The HTTP target (the URL) can be configured flexible, allowing adaption to various web-services.
HTTPTAPI itself does not offer any telephony features but links TAPI requests to HTTP requests as shown in the following Figure:
The web-application can be a proprietary interface to a telephony service (e.g. the web interface of a VoIP provider), an Asterisk PBX (using Asterisk's AJAM web interface) or a SIP phone with an embedded web server like SNOM phones as shown below:
If you still have issues with HTTPTAPI please directly klaus.darilion (at) ipcom.at directly.
HTTPTAPI is a commercial application and requires a license to activate the requested number of lines. To make sure that HTTPTAPI is suitable for you please request a trial license.
We also offer customized and branded versions of HTTPTAPI. This allows VoIP providers to easily give TAPI click-2-dial functionality to their customers. The provider only has to provide a Web-API to initiate phone calls. This API will be used by HTTPTAPI.
For example, HTTPTAPI can be pre-configured with the URL of the Web-API and the customer only has to configure username/password. Furthermore the HTTPTAPI can be branded to your company, e. g. by renaming the TAPI provider and adding logos of your company.
Additional features are HTTPS support with usage of the Windows certificate store and .msi install packages for 32 und 64 bit Windows.
If you are interested in branded versions of HTTPTAPI please contact klaus.darilion (at) ipcom.at.
If you miss a feature in HTTPTAPI please directly contact klaus.darilion (at) ipcom.at. Common useful features with low amount of work are usually implemented promptly.
Complex features or extensions dedicated for your web application can be implemented on time and material basis.
To debug HTTPTAPI problems you have to enable the debug logging of HTTPTAPI. Then HTTPTAPI will write log messages to c:\httptapi.log. If you see such a file, please send the file by email. If you do not see such a file, you have to use the tool DebugView from Microsoft to capture the log messages. Then send the the captured log messages by email. Please follow the step-by-step guide below.
When sending me emails, please always include the Windows version you are using and a screenshot of the HTTPTAPI configuration.
1) Close your dialer application and all other applications
Start the telephony control panel as Administrator. The fastest way to do this without logging in as Administrator is to navigate with Explorer to c:\Windows\system32. There right-click on "telephon.cpl" and select "Run as administrator". Navigate to the settings of HTTPTAPI and set the "Debug Level" to 5. Then click OK.
3) Verify if there is now a file c:\httptapi.log. If yes, proceed. If no, go to step 7)
4) Start your dialer application and perform a call. You should see now plenty of log messages in c:\httptapi.log.
5) Reset the log level of HTTPTAPI to "0" as described in step 2)
6) Send me the file c:\httptapi.log by email. Done!
Download DebugView from https://technet.microsoft.com/en-us/sysinternals/debugview.aspx
Unzip the tool. Then right-click the Dbgview (Dbgview.exe) application and select "Run as administrator". In the DebugView tool go to the menu "Capture" and enable "Capture Global Win32"
8) Start your dialer application and perform a call. You should see plenty of log messages appearing in DebugView which have the prefix "HTTPTAPI". In DebugView use File->Save As to save the log messages to the hard disk (e.g. c:\log.txt). Then send me this file by email.
9) Reset the log level of HTTPTAPI to "0" as described in step 2) Done!