A TAPI-enabled program may not initiate a conference call correctly in Windows XP or in Windows 2000 (317877)


The information in this article applies to:

  • Microsoft Windows XP Professional
  • Microsoft Windows XP Home Edition
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Professional
This article was previously published under Q317877

SYMPTOMS

When you use a Telephony API (TAPI)-enabled program to initiate a conference call on a computer that is running Microsoft Windows XP or Microsoft Windows 2000, the conference call may not initialize correctly.

CAUSE

This problem may occur if the following conditions are true:
  • The TAPI-enabled program initiates the conference call.
  • The conference call enters the CONFERENCED state after a call is made to the lineSetupConference function or to the lineAddToConference function. If either of these functions is called, the TAPI-enabled program may receive a LINECALLSTATE_CONFERENCED message, where the dwParam2 parameter has a value of 0 (zero). You expect the dwParam2 parameter to contain the hConfCall parameter.

    In this case, the dwParam2 parameter has a value of 0 (zero) because the conference parent handle is missing in the LINE_CALLSTATE CONFERENCED message.

RESOLUTION

Windows XP service pack information

To resolve this problem, obtain the latest service pack for Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

322389 How to obtain the latest Windows XP service pack

Windows 2000 service pack information

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to obtain the latest Windows 2000 service pack


The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. 
Date         Time   Version            Size    File name
--------------------------------------------------------------
13-Jun-2001  05:05  5.0.2195.3727       3,856  Svcpack1.dll     
08-May-2002  21:00  5.0.2195.5227     173,328  Tapisrv.dll

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

This problem was corrected in Windows XP Service Pack 1.
This problem was corrected in Windows 2000 Service Pack 4.

MORE INFORMATION

The dwParam2 parameter specifies call-state-dependent information.

For more information about TAPI line device functions, visit the following Microsoft Web site:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tapi/tapi2/line_device_functions.asp

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

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

Modification Type:MinorLast Reviewed:9/27/2005
Keywords:kbHotfixServer kbQFE kbWin2kSP4fix kbWinXPsp1fix kbbug kbfix KB317877 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.