PhoneSelectExtVersion Is Not Called When phoneOpen Is Called from a Remote Client

ID: Q217206

The information in this article applies to:

SYMPTOMS

When developing a TAPI 2.1 compliant application and when the application does an open line from the client using the call lineGetID(), it will return an index number based on the server (for example, 24 when only one phone is available to client) and subsequent phoneOpen calls will fail because the client actually has only access to one phone device as indicated by Tsec.ini.


CAUSE

When tracing this from the server, and when entering an extension version in phoneOpen, TAPI is properly calling TSPI_phoneSelectExtVersion but on the client, TAPI does not call TSPI_phoneSelectExtVersion.


RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://support.microsoft.com/support/supportnet/default.asp

The English version of this fix should have the following file attributes or later:


   Date      Time                 Size    File Name     Platform
   -------------------------------------------------------------
   2/12/99   11:48:17 AM          57kb    Remotesp.tsp  (x86)
   2/12/99   12:54:39 PM          108kb   Tapi32.dll    (x86)
   2/12/99   12:54:40 PM          150kb   Tapisrv.exe   (x86)

   2/12/99   12:54:15 PM          101kb   Remotesp.tsp  (Alpha)
   2/12/99   12:54:22 PM          192kb   Tapi32.dll    (Alpha)
   2/12/99   12:54:25 PM          238kb   Tapisrv.exe   (Alpha)

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, a fee may be charged. This fee is refundable if it is determined that you only require the fix you requested. However, this fee is non-refundable if you request additional technical support, if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:
Q154871 Determining If You Are Eligible for No-Charge Technical Support


STATUS

Microsoft has confirmed this to be a problem in Windows NT 4.0.

Additional query words: 4.00 


Keywords          : kbbug4.00 kbfix4.00 
Version           : winnt:4.0
Platform          : winnt 
Issue type        : kbbug

Last Reviewed: April 8, 1999