Windows Vista Home Premium 64 bit Edition: All “LINE_CALLSTATE” messages do not arrive at an x64-based version of Windows Vista, of Windows Server 2008, of Windows 7 or of Windows Server 2008 R2

SUPPORT SOLUTION:
Consider the following scenario:
You try to make a telephone call from a computer that is running x64-based version of Windows Vista, of Windows Server 2008, of Windows 7 or of Windows Server 2008 R2.The call passes through a remote Telephony API (TAPI) server.The TAPI server uses a private branch exchange (PBX) simulator.In this scenario, all LINE_CALLSTATE messages do not arrive at the computer..This issue occurs because the message is typecasted incorrectly. Therefore, the TAPI message is dropped..Hotfix information
2, ‘resolution’);
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.If the hotfix is available for download, there is a “Hotfix download available” section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The “Hotfix download available” form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.Prerequisites
3, ‘resolution’);
To apply this hotfix, you must be running one of the following operating systems:Windows Vista Service Pack 2 (SP2)Windows Server 2008 Service Pack 2 (SP2)Windows 7Windows Server 2008 R2

For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:

935791 

(http://support.microsoft.com/kb/935791/
)

How to obtain the latest Windows Vista service pack

For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

968849 

(http://support.microsoft.com/kb/968849/
)

How to obtain the latest service pack for Windows Server 2008

Registry information
3, ‘resolution’);
To use the hotfix in this package, you do not have to make any changes to the registry.Restart requirement
3, ‘resolution’);
You must restart the computer after you apply this hotfix.Hotfix replacement information
3, ‘resolution’);
This hotfix does not replace a previously released hotfix.File information
3, ‘resolution’);
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.Windows Vista and Windows Server 2008 file information notes
4, ‘resolution’);
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only “Windows Vista” is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under “Windows Vista” on the page. Always refer to the “Applies To” section in articles to determine the actual operating system that each hotfix applies to.
The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.Collapse this tableExpand this table
VersionProductSR_LevelService branch
6.0.600
2
.
22xxxWindows Vista and Windows Server 2008SP2LDRThe MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the “Additional file information for Windows Server 2008 and for Windows Vista” section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.For all supported x64-based versions of Windows Server 2008 and of Windows Vista
4, ‘resolution’);
Collapse this tableExpand this tableFile nameFile versionFile sizeDateTimePlatformTapisrv.dll6.0.6002.22611318,97613-Mar-201100:12×64Tapisrv.dll6.0.6002.22611243,20013-Mar-201101:54×86Windows 7 and Windows Server 2008 R2 file information notes
4, ‘resolution’);
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under “Windows 7/Windows Server 2008 R2″ on the page. Always refer to the “Applies To” section in articles to determine the actual operating system that each hotfix applies to.Collapse this tableExpand this table
VersionProductSR_LevelService branch
6.1.760
0
.
20xxxWindows 7 and Windows Server 2008 R2RTMLDRThe MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the “Additional file information for Windows Server 2008 R2 and for Windows 7″ section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
4, ‘resolution’);
Collapse this tableExpand this tableFile nameFile versionFile sizeDateTimePlatformTapisrv.dll6.1.7600.20785316,92820-Aug-201005:45×64Tapisrv.dll6.1.7600.20785316,92820-Aug-201005:45×64Tapisrv.dll6.1.7600.20785242,17620-Aug-201004:30×86Tapisrv.dll6.1.7600.20785242,17620-Aug-201004:30×86.Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section..

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 

(http://support.microsoft.com/kb/824684/
)

Description of the standard terminology that is used to describe Microsoft software updates

.Additional file information

Additional file information for Windows Vista and for Windows Server 2008
3,
Additional files for all supported x64-based versions of Windows Vista and of Windows Server 2008
4,
Collapse this tableExpand this tableFile nameAmd64_microsoft-windows-tapiservice_31bf3856ad364e35_6.0.6002.22611_none_41c1c2a0b39b1d23.manifestFile versionNot ApplicableFile size21,011Date (UTC)13-Mar-2011Time (UTC)00:24PlatformNot ApplicableFile nameUpdate.mumFile versionNot ApplicableFile size2,433Date (UTC)14-Mar-2011Time (UTC)09:44PlatformNot ApplicableFile nameX86_microsoft-windows-tapiservice_31bf3856ad364e35_6.0.6002.22611_none_e5a3271cfb3dabed.manifestFile versionNot ApplicableFile size20,967Date (UTC)13-Mar-2011Time (UTC)02:13PlatformNot ApplicableAdditional file information for Windows 7 and for Windows Server 2008 R2
3,
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
4,
Collapse this tableExpand this tableFile nameAmd64_microsoft-windows-tapiservice_31bf3856ad364e35_6.1.7600.20785_none_3fbb6d0017c13665.manifestFile versionNot applicableFile size7,673Date (UTC)20-Aug-2010Time (UTC)06:16PlatformNot applicableFile nameAmd64_microsoft-windows-tapiservice_31bf3856ad364e35_7.1.7600.20785_none_312be945a2a7df34.manifestFile versionNot applicableFile size7,140Date (UTC)20-Aug-2010Time (UTC)06:14PlatformNot applicableFile nameUpdate.mumFile versionNot applicableFile size1,817Date (UTC)20-Aug-2010Time (UTC)11:26PlatformNot applicableFile nameX86_microsoft-windows-tapiservice_31bf3856ad364e35_6.1.7600.20785_none_e39cd17c5f63c52f.manifestFile versionNot applicableFile size7,669Date (UTC)20-Aug-2010Time (UTC)05:19PlatformNot applicableFile nameX86_microsoft-windows-tapiservice_31bf3856ad364e35_7.1.7600.20785_none_d50d4dc1ea4a6dfe.manifestFile versionNot applicableFile size7,136Date (UTC)20-Aug-2010Time (UTC)05:17PlatformNot applicable.

For File Repair and Data Recovery, visit File Repair / Data Recovery