Dial-Up Networking Cannot Dial Local Area Code

Last reviewed: February 12, 1998
Article ID: Q180906
The information in this article applies to:
  • Microsoft Windows 95
  • Microsoft Windows 95 OEM Service Release versions 2, 2.1

SYMPTOMS

When you install TAPI (Telephony Application Programming Interface) 2.1 and configure a Dial-Up Networking connection to use the local area code when you dial a phone number, the 10-digit phone number to be dialed may be changed to contain random or unintelligible characters.

CAUSE

This behavior occurs because the Tapi32.dll file that is installed with the TAPI 2.1 software cannot correctly handle the 10-digit local area code and phone number.

RESOLUTION

This issue is resolved by the following updated file:

   Tapi32.dll version 4.10.1688, dated 02/11/98 05:28pm, 109,056 bytes

To work around this issue, follow these steps:

  1. Double-click the Dial-Up Networking connection you want to use, and then click Dial Properties.

  2. Type "000" (without quotation marks) in the Area Code box, and then click OK.

When you type "000" in the Area Code box, the correct local area code is dialed, but the number to be dialed does not contain any invalid characters.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft TAPI 2.1. An update to address this problem is now available, but is not fully regression tested and should be applied only to computers experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft does not recommend implementing this update at this time. Contact Microsoft Technical Support for additional information about the availability of this update.


Additional query words: string corrupt
Keywords : osr2 win95 wintapi kbtool
Version : WINDOWS:95
Platform : WINDOWS
Issue type : kbprb


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 12, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.