Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

TAPI to work with Windows 10? Click a tel:// to callto:// link to call from desk phone ? 1

Status
Not open for further replies.

stownsend

Technical User
Aug 11, 2004
355
US
We have been using the TAPI driver that has come with the IPO software and it works great with Windows 7. we have installed a CallTo:// Protocol that Links to a exe that uses the Dialer and makes a call on the IP 56XX desk phones. Its been working well, click a phone number on a website and your desk phone starts ringing.

We have not been able to get the Avaya TAPI driver to work with Windows 10. Is there a newer version or a better method of doing this?

Thank you,
 
I've used v1.0.0.43 of both TAPI2 and TAPI3 on Windows 10.

"Trying is the first step to failure..." - Homer
 
Hmmm okay we have installed TAPI3 on a few older installs of Win10 and it seems to works great. We have a new telemarketer and installed it on a brand spanking new Win10 install and no love what so ever.

We did the admin install, selected the user from drop down list and entered password, reboots, finishes the install, then I load up the dialer.exe App and it complains that I have no telephone or modem device installed. Telephony service is running, set to auto. We are ride different IPO users...

Is there something else that needs to be installed for this to work? The 2 other Win10 machines have no other issues. One is another IT Tech workstation and one is a Visual Studio VM I use.

FWIW R9.1 IPO500v2

Thank you,

 
Shouldn't need anything more, if it works on 2 other clients then there something wrong with the installation on that one, and most probably it's the password.

I only use TAPI on 3rd party mode though.

"Trying is the first step to failure..." - Homer
 
Lastnight I programmed in my Extension and It didn't seem to make a Difference.
Though this morning when I put in the New Extension in my machine It failed with a Different Error.

It did turn out that the Tech that Created the Extension didn't have the Right password in there. )-:

Added in the Correct password and then reconnected and it is working well.

Thank you!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top