We are planning to start work on updating the TAPI.

If you have any ideas/requirements/suggestions/demands - now would be a good time to raise them.

What will you be using the TAPI for? Which application? Which OS?

Thanks for starting work on this. In my perfect world the TAPI driver would be:

Compatible with Windows 7 & Windows Vista both 64bit.
It would allow a call directly from Outlook

and here's the cleaver bit:

The autodial command in access 2007 runtime. This actually runs the windows inbuilt command line "autodial".

Essentially windows just needs to think that the TAPI is a voice modem.

Oh and the link posted by Jeffo takes you to a page which includes some open source code for a TAPI which would probably work if the permissions were correctly set.

Thanks Again!

The latest version doesn't seem to work with Outlook 2010, so that would help.

Hi John,

Most of our testing was done against Outlook 2010, so it should work.

First thing to check is on the Dialling Options page (which you can get to from the Contact/Call dialog) - the "Connect Using Line" box should say "Voipfone Callback". If it doesn't, see if it is available in the drop-down list. if not, then the installation has failed.

Outlook likes to play with the phone numbers before passing them on to us. It especially doesn't like numbers that don't have a space after the country code - it treats them as invalid and then refuses to place the call.

You can check what Outlook is going to send us as the phone number by clicking on "Dialling Properties" before making the call. The "massaged" number is shown at the bottom. If the number is blank, Outlook has decided it is invalid (which is annoying since the TAPI callback program is perfectly capable of dialling numbers no matter what the formatting).

If the number on the Dialling Properties page looks good, then we'll need some more info before we can try to reproduce the problem - what version of Windows, and whether it is 32 or 64 bit, and a hint at what the number is like (first few digits and the rest as x's if you like). PM me if you prefer.


Thanks

Mal

We have just uploaded a new version of the TAPI Auto Dialler (2.1).

The update fixes some minor number formatting issues.

32 bit Operating System: http://www.voipfone.co.uk/Software/Voipfone_tapi_32.exe

64 bit Operating System: http://www.voipfone.co.uk/Software/Voipfone_tapi_64.exe

Hi,

The problem seems to have been caused by Microsoft Communicator 2007 R2. I am running Windows 7 64bit, and Outlook 2010. I have uninstalled Communicator and it is working fine.

Prior to uninstalling Communicator I didn't see the Call menu, although Communicator had it's own.

Anyway I hope that is useful for anyone else.

John

Ok I have another suggestion.

We have Microsoft Dynamics Online, which adds a plugin to Outlook. It would be good if the dynamics sections allowed you to right click and phone like the contact cards.

It would be nice to have deeper integration into Outlook and web browsers, much like Skype has, so that you can dial numbers from web pages, and so that in Outlook there is a "Call" button next to each number in the address book, rather than having to use the "Call" dropdown menu, which is a little clumsy.

We've just finished testing the browser dial plug-in and will be releasing it next week for PC (IE, Chrome and Firefox)

Don't know about the dropdown issue. I'll ask an engineer to see if it's possible.

Hi,

Please can you make the TAPI software W2003 Terminal Server compatible if possible. At the moment v2.1 writes its configuration settings into HKLM/Software/Voipfone so only one account can be used. Would it be possible to write it to the current user area instead HKCU/Software/Voipfone so that each Terminal Server user can have their own account settings?

If someone is aware of another way to get multiple extensions working in a Terminal Server environment I would be interested in the details.

hanks,
Mark.