Share via

Ugraded to Windows 8 & now TAPI does not work, no telephony connection

Anonymous
2012-11-11T21:52:01+00:00

Always had TAPI working via a MS access application that would register caller ID from incoming phone calls from my PBX NEC SL1100

Use to have Windows XP, upgraded to Windows 8 (full clean install) and it stopped working.

Seems to set line OK but no calls are registered, when you try to close the connection it freezes.

Tried testing with dialer and get "one or more devices are incompatible with tapi.dll"

Uninstalled PBX TAPI driver & reinstalled 20+ times, the phone/modem/advanced says connected to PBX OK.

PBX is pretty current & meant to be compatible with all Windows up to & inc windows 7 64bit so really would have thought 8 should be OK.

Have installed same PBX TAPI software on another window 7 64bit & all works fine so something on WIndows 8 is messing with this. Why!!

Tried running anything .exe & everything else in different compatibility modes.

Switch firewall Off in case something here as I know added security.

restarted a 1000 times

Spent 14 hours solid on this one thing and really frustrated.

Any advise please.

Windows for home | Previous Windows versions | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

7 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2013-07-29T13:37:50+00:00

    I have some doubts on whether to install the 32-bit or 64-bit version for this reason: the application that will call TAPI apis is a 32-bit one, and IIRC a 32-bit app cannot call a 64-bit api.

    Tom,

    on a x64 OS you definitely need to install x64 TSP (TAPI Service Provider = TAPI driver).

    The TAPI apps can be either x86 or x64 (even mixed). The mapping for the apps is done by the OS.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2013-07-29T04:24:41+00:00

    FYI the issue is also discussed in

    This issue can only be solved

    • either by MS undoing the interface changes on TSPI level
    • or by the TSP manufacturers adaption their TSPs to the changed TSPI behaviour

    To sum things up here is the situation as I understand it.

    Problem: Incoming calls are not reported via TAPI

    Affected OS:

    • Windows 8 (x64 version only)
    • Windows Server 2012 (there is only a x64 version)

    Affected TSP (feel free to report addional info, e.g. version, fix available etc.)

    • Avaya TAPI
    • Acatel-Lucent TSP
    • NEC TSP (for PBX NEC SL1100)
    • Siemens HiPath TAPI 120/170 (V2 R1.66.0)

    With the latter TSP I reproduced the issue myself on a MS Surface Pro (with Win8x64).

    The other TSPs have been reported by others.

    Technical background:

    The issue is caused by TAPISRV (Telephony Service) not processing LINE_NEWCALL correctly on the affected OS,

    presumable due to additional parameter type checking for the dwParams in LINEEVENT / PHONEEVENT.

    It is about DWORD vs. DWORD_PTR.

    The issue is only existing on x64 OS because there those two types a different: (unsigned long) vs. (unsigned __int64)

    In x86 they are the same (unsigned long), hence in x86 there is no issue.

    Was this answer helpful?

    0 comments
  3. Tom van Stiphout 40,201 Reputation points MVP Volunteer Moderator
    2012-12-27T21:31:00+00:00

    Me too. We have an Avaya IP Office phone system and we are using TAPI to dial from our in-house CRM. Alas, after installing the driver on Win8-64 (no error messages), this TAPI driver does not show up in Control Panel > Phones and Modems. This is the first step to selecting the driver in Outlook.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2012-12-10T12:00:59+00:00

    I too am having an issue with TAPI and Windows 8.  My app under Windows 7 works fine, but Windows 8 it cannot see any tapi events.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2012-11-12T00:08:51+00:00

    Follow on from my post, 

    I meant to say it seems the tapi dll's are Version 6.2.9200.16384 on 8 and

    6.1.7601.17514 on Windows 7.

    I guess they made some changes. I don't think there is anyway  NEC (even with there resources) are going to bother to write more TAPI drivers when they guessed they had it covered going up to windows 7 64bit.

    I thought TAPI was old style so why on earth should MS change it.

    I am guessing being a DLL there is no way to run this in any sort of compatibility mode.

    Few questions. Is there a way to replace all the likely tapi files with those from WIndows 7.

    Is it likely to work, which files would need to be replaced, I guess more than 1 or 2.

    How can you delete/replace files in the windows directory being locked.

    I am thinking of downgrading but never had 7 before. there is talk that you can downgrade within the licence, any idea if/how this might be possible. Can't download 7 from MS site anymore.

    Started off with such promise & wanted to stick with 8 but this is a real deal breaker & finding more & more things not compatible despite no mention in the pre-upgrade adviser.

    I thought 8 was really meant to be just a polish & interface upgrade on 7 but I am exhausted trying to inch my way to what I had with XP before.

    Was this answer helpful?

    0 comments