SIPTAPI Support

Documentation und Support

SIPTAPI comes with an installation manual and a tutorial which describes the details of SIPTAPI. First you should learn what TAPI is by reading this. Second make sure to read the detailed description in the SIPTAPI-README.pdf file - without understanding how SIPTAPI works you will fail to solve your problems!

  • SIPTAPI does not work with "Sipgate Team" as Sipgate does not support standard-based call transfer using the REFER method (Sipgate Team uses DMTF codes for call transfers)!
  • If you are using Outlook 2007 or Outlook 2010 make sure to read the comments in the file Outlook2007 and Outlook2010 Problems.
  • Do not activate the reverse mode unless you were told to do it!
  • The free version of SIPTAPI does not REGISTER to the SIP server. Thus, your SIP server must be configured to allow calls also without being registered. If your VoIP provider requires registration you may try the "alternative configuration" --> see SIPTAPI-README.pdf!
  • SIPTAPI is known to work with Outlook, Phoner and Windows Dialer (dialer.exe). Thus, if you have a problem with your TAPI application you should try Windows Dialer to find out if the problem is in SIPTAPI or in your TAPI application.
  • On Windows Vista/Win7 you are only allowed to install and configure SIPTAPI as Administrator via control panel!

If you still experience problems please contact klaus.darilion (at) ipcom.at directly - but, I promise to not answer e-mails which miss some information about your setup. Thus, e-mails like "I have a problem, can you help me?" won't be answered!

E-mails should include the following:

  • Detailed description of the problem, e.g.: Does the phone start ringing? does the phone indicate a call transfer?
  • Detailed description of your SIP server: Which software and version (Asterisk 1.4, Kamailio 3.1 ...)? If you use a service providergive me all the details you have about this service provider.
  • Which Operating System are you using? 32bit or 64 bit?
  • Which TAPI Application are you using? Version number? In case of 64bit Windows, is the application a 32bit or 64bit application?
  • A screenshot of the SIPTAPI configuration: open the configuration window and press Alt+PrintScreen (in German: Alt+Druck) to copy the screenshot into your clipboard. Then, if you writing HTML-based e-mails just paste (Ctrl-V) the clipboard into your e-mail.
  • Please do not send me passwords or other serious data.

For detailed analysis I also need:

  • pcap traces. At best, capture directly on the SIP server (tcpdump -i any -s 0 -w siptapi.pcap port 5060). If you do not have access to the SIP server, use Wireshark and capture the SIP signalling between SIPTAPI and the SIP server: use capture filter "port 5060" (or whatever port your SIP server is using) to limit the trace to SIP signaling.
  • Logfiles: SIPTAPI writes a logfile to c:\siptapi-0.2.log (the commercial version logs to siptapi.log). The logging can be intensive, thus it is necessary to have the logfile only inclduing a single scenario. To get a clean logfile close your TAPI application, delete the logfile, start your TAPI application, try to call someone (only 1 time), close the TAPI application and send me the logfile. If you do not find the logfile then SIPTAPI does not have permissions to write to C:\. In this case please use Debugview to capture the log messages manually.