Skip to main content
Ctrl+K

jiangsheng's docs

  • Homepage
  • Games
  • Blogs
  • Grandma's handbook
  • Homepage
  • Games
  • Blogs
  • Grandma's handbook

Section Navigation

  • 内容:

    • 2026
    • 2025
    • 2024
    • 2023
    • 2022
    • 2021
    • 2020
    • 2019
    • 2018
    • 2017
    • 2016
    • 2015
    • 2013
      • Blogs in January 2013
      • Blogs in February 2013
      • Blogs in July 2013
        • Another breaking change related to 64 bit compatibility, this time in TAPISRV w/Windows 8
        • Howto: Ignoring web browser certificate errors in a webbrowser host
      • Blogs in August 2013
    • 2012
    • 2011
    • 2010
    • 2009
    • 2008
    • 2007
    • 2006
    • 2005
    • 2004
    • 2003
    • 2002
    • 2001

Indices

  • General Index
  • Blogs
  • Blogs in 2013
  • Blogs in July 2013
  • Another breaking change related to 64 bit compatibility, this time in TAPISRV w/Windows 8

Another breaking change related to 64 bit compatibility, this time in TAPISRV w/Windows 8#

The ADO team had to make a breaking change the ADO APIs due to compatibility problem with Microsoft Office. Now it seems to be Tapi’s turn.

In the 64 bit editions of Windows 8 and Windows Server 2012, some TAPI providers would stop getting incoming calls due to implementation changes in the TAPI service (TAPISRV) that had to be done for 64 bit compatibility.

The problem is pretty obvious from the documentation, for example LINE_NEWCALL has this:

htLine = (HTAPILINE) hLineDevice;
htCall = (HTAPICALL) 0;
dwMsg = (DWORD) LINE_NEWCALL;
dwParam1 = (DWORD)(HDRVCALL) hdCall;
dwParam2 = (DWORD)(LPHTAPICALL) &htCall;
dwParam3 = (DWORD) 0;

The parameters can’t really be passed as DWORDs - on a 64 bit build, pointers are 64 bit in size, and a DWORD is 32 bit.

Fortunately this can be corrected fairly easily, just ignore what the documentation said and treat the DWORD parameters as DWORD_PTR, however for the end users they would need updates from TAPI providers to get TAPI working on their Windows 8 /Server 2012 machine. According to TAPI MVP Andreas Marschall, the following TAPI providers are affected (If you got a provider released before 2012,  it is likely also affected)

  • Avaya TAPI

  • Acatel-Lucent TSP

  • NEC TSP (for PBX NEC SL1100)

  • Siemens HiPath TAPI 120/170 (V2 R1.66.0)

Howto: Ignoring web browser certificate errors in a webbrowser host   Book review: Mastering Windows 8 C++ App Development

previous

Blogs in July 2013

next

Howto: Ignoring web browser certificate errors in a webbrowser host

Edit on GitHub

This Page

  • Show Source

Social Media Links

  • twitter (archived): #jiangsheng
  • bluesky: sheng-jiang.bsky.social
  • stackoverflow: Sheng Jiang 蒋晟

© Copyright 2018-, Sheng Jiang.

Created using Sphinx 9.1.0.

Built with the PyData Sphinx Theme 0.17.1.