Table of Contents Index NMS Glossary Previous Page Next Page Version


Appendix A

Troubleshooting


Introduction
Installation
Using the Windows Event Log
TAPI Functions
lineInitialize/lineInitializeEx
lineOpen
lineMakeCall
WAVE Functions

IntroductionTop of Page

This section addresses some common installation issues.

InstallationTop of Page

The following table provides solutions to installation errors:
Problem

Solution

The NMS TAPI Service Provider is already installed on the system.

An earlier installation of NMS TAPI may not have been removed correctly. Run the uninstall program for the previous version of NMS TAPI and then re-install NMS TAPI 1.4.

Natural MicroSystems Service Provider does not appear in the list of available TSPs.

There was a problem with the installation. Run the uninstall program for NMS TAPI and then re-install NMS TAPI 1.4.

Setup cannot install NMS TAPI service provider. Registry access error.

The user is probably not logged in as Administrator. Log out, and then log back in as Administrator.

Using the Windows Event LogTop of Page

The Windows Event Log may report any of the following errors when it encounters problems during NMS TAPI initialization:
Error Type

Error

Fatal (Installation returns appropriate error code)

· Version negotiation failed

· AG board(s) loading failed

· QX board(s) loading failed

· Configuration data is not available

· CTA initialization failed

· CTA parameter(s) setting failed

· Digital trunk(s) did not sync in time

· Memory allocation failed

· Default connecting failed

· Verification of required Natural Access parameters failed

Non-Fatal

· Audio RPC transport initialization failed

· Fax RPC transport initialization failed

TAPI FunctionsTop of Page

This section describes problems and solutions that apply to the TAPI functions.

lineInitialize/lineInitializeExTop of Page

Problem

Returns 0 (Windows NT) or 5 (Windows 2000) number of line devices.

Solutions

      1. Boards are not configured correctly. Use the NMS Configurator to reconfigure the boards. Use Run Test to check the settings.

        
        
      2. Digital trunks can not get in service. Stop all TAPI applications and launch the NMS Configurator. If digital boards are used and synchronization is expected (for example, back-to-back board connection), set the PRM.TSP.DIGITALTRUNK.WAITTOBEINSERVICE parameter to 0. Check the physical connection of all boards.

        
        
      3. Board drivers are not loaded. Stop all TAPI applications. Launch the NMS Configurator and select the Load Board Drivers checkbox in the Advanced configuration settings. Launch the command prompt and run agmon with no parameters (agmon2000 on Windows 2000).

        
        
      4. Check the NT Event Log for errors against NMS TAPI. The following messages may appear:

        • Version negotiation failed. Check API and extended version parameters.

          
          
        • AG board(s) loading failed. Possible incorrect board settings or board failure.

          
          
        • QX board(s) loading failed. Possible incorrect board settings or board failure.

          
          
        • CTA parameter(s) setting failed. Possible parameter value is out of range.

          
          
        • Digital trunk(s) did not sync in time. No synchronization signal. Possible configuration specific (see case 2 above) or connection failure.

          
          If you receive NMS TAPI error messages other than these, contact NMS Technical Services.

    lineOpenTop of Page

    Problem

    An attempt to open any of the first five lines on Windows 2000 fails.

    Solution

    The first five devices (0 through 4) are reserved for use by Windows 2000. If NMS TSP is the only third party TSP installed in the system, the first line of the first board corresponds to NMS TAPI device number five.

    Problem

    Function returns LINEERR_OPERATIONFAILED.

    Solutions

        1. Check parameter settings in cta.cfg.

          
          
        2. If NaturalFax or NMS ISDN is used, verify that the appropriate Natural Access components are successfully installed.

          
          
        3. Run ctatest to check the configuration.

    lineMakeCallTop of Page

    Problem

    Function returns LINEERR_OPERATIONUNAVAIL.

    Solution

    Verify that the board is not configured for NOCC protocol.

    Problem

    Function returns LINEERR_OPERATIONFAILED.

    Solution

    Verify that the Start Protocol checkbox in the Advanced section is selected or the protocol was successfully started using lineDevSpecific.

    Problem

    A call disconnects immediately after being placed.

    Solution

        1. Check the configuration. If software switching is used, verify that it was done after the boards were initialized by lineInitialize or agmon.

          
          
        2. Check the number of the person you are calling.

    WAVE FunctionsTop of Page

    The following problems and solutions apply to WAVE functions:
    Problem

    Solution

    Play, record, or other WAVE capabilities do not work on NMS hardware.

    You may need to add the NMS WAVE driver to the Windows list of WAVE drivers.

    The corresponding TAPI line may not be in the connected state.

    Windows system sounds, such as dialog box sounds, are audible on the phone line.

    If no other audio devices are installed, Windows attempts to use the NMS WAVE driver as an audio output device for playing system sounds. For example, Windows may attempt to play sounds when programs display message boxes and at start-up or shutdown. If a line is open and a call is connected by the NMS TSP, this output may be heard through the telephone. Install another audio device or disable sounds using the Sounds applet in the Windows Control Panel.



    Table of Contents Index NMS Glossary Previous Page Next Page Version


    Want to send us feedback on our documentation? Email: Tech_Pubs@nmss.com
    Copyright © 2001, Natural MicroSystems, Inc. All rights reserved.