I have tried every Caller ID program that I can find to try and have Windows 10 display the Caller ID for incoming phone calls on my desktop.
I have tried a Conexant 93010 ACF External USB modem and a LSI PCI-SV92EX Soft Modem. Both support Caller ID and when I send them the Caller ID command using Hyperterminal (which is sadly missing in Win 10) they reply with OK.
They work fine in XP and Windows 7 (haven't tried in Win8) but in Win10 all I get is a N/A instead of the Caller ID info.
Any suggestions for tweaks or software to try will be appreciated. I have tried CallTray, Ascendis Caller ID, Call Clerk, Picture Caller ID, and Audio Caller ID, all with the same results.
Thanks
I use Call Clerk with a Hiro 50113 usb modem works great on Windows 10.I have tried every Caller ID program that I can find to try and have Windows 10 display the Caller ID for incoming phone calls on my desktop.
I have tried a Conexant 93010 ACF External USB modem and a LSI PCI-SV92EX Soft Modem. Both support Caller ID and when I send them the Caller ID command using Hyperterminal (which is sadly missing in Win 10) they reply with OK.
They work fine in XP and Windows 7 (haven't tried in Win8) but in Win10 all I get is a N/A instead of the Caller ID info.
Any suggestions for tweaks or software to try will be appreciated. I have tried CallTray, Ascendis Caller ID, Call Clerk, Picture Caller ID, and Audio Caller ID, all with the same results.
Thanks
I finally got it to work. I used Call Clerk and found that setting it to "Use Modem Directly" instead of "Use Tapi" would get the Caller ID number to display instead of N/A.
I still think there are issues with the TAPI in Windows 10, but at least I have my Caller ID working again.
I finally got it to work. I used Call Clerk and found that setting it to "Use Modem Directly" instead of "Use Tapi" would get the Caller ID number to display instead of N/A.
I still think there are issues with the TAPI in Windows 10, but at least I have my Caller ID working again.
I agree. I am having the same issues.
It seems the windows 10 TAPI fails to initialize! I can not believe how Microsoft could release like that and not fix it yet.
Here is how to reproduce it - download sample code from here. And run the program and see tapi.Initialize() fails to return (forever loop).
Windows 8 TAPI 3 in C# - Get Lines and make a call, see calls incomming sample in C# for Visual Studio 2010
Would appreciate a response from anyone if they have a work around. I need to for a high priority customer issue. Thanks!
This issue first began with Windows 8.1 with an update in late 2014, and as reported here continues with Windows 10.
