(Page 1 of 1 in this chapter) Version

Chapter 4

Verifying the Installation

4.1 Introduction
4.2 The Status Indicator LEDs
4.3 Verifying That Your Board is Installed Correctly
4.4 Using CT Access Demonstration Programs

4.1 Introduction

This chapter provides procedures to verify that your QX 2000 board is installed and configured correctly. For additional troubleshooting tips, see Appendix E.

4.2 The Status Indicator LEDs

The QX 2000 boards have four indicators (LEDs) on the end bracket. The location of the indicators is shown in Figure 17.

When you run qxload without starting an application, the LEDs indicate that the board is running and represent the board number in binary format. The board number is assigned during software installation and is used to address a specific board in your application.

Figure 17. QX 2000 LEDs





4.3	 Verifying That Your Board is Installed Correctly





The swish utility is installed with CT Access and allows you to send commands to MVIP switches.



To run swish:


    


  1. Open a command window and enter:
    

       swish


    
The swish utility starts up and displays its prompt.
    

  2. Open the QX 2000 device driver and assign a handle to one of your QX 2000 boards by entering:
    

       swi.OpenSwitch handle=qxsw x


    
where x is the device number of the board you wish to test, and handle is the handle to give to the device. For example, to assign handle qx0 to board 0, enter:
       swi.OpenSwitch qx0=qxsw 0


    
swish opens the driver and assigns handle qx0 to the device.
    

  3. Enter the following command to reset the board:
    

       swi.ResetSwitch qx0


    
If the board is not installed correctly, you will receive a driver error.
    

  4. Repeat this test for each QX 2000 board you have installed in your system.
    

    

  5. When you have finished testing your QX 2000 boards, exit swish by entering:
    

       exit





For more information on swish, see the Switching Service Developer's Reference Manual.







4.4	 Using CT Access Demonstration Programs





The following demonstration programs are provided with CT Access and can be used to verify that your QX 2000 board is operating correctly. For more information about CT Access demonstration programs, see the CT Access Developer's Reference Manual and the Voice Message Service Developer's Reference Manual.





 





 Program



 Description




 ctatest



 Demonstrates CT Access functions.




 incta



 Demonstrates receiving an inbound call.




 nccxfer



 Demonstrates transferring a call to another extension.




 outcta



 Demonstrates placing an outbound call.




 vceplay



 Demonstrates using the Voice Message service to play messages from voice files.




 vcerec



 Demonstrates using the Voice Message service to record one or more messages to a voice file.






















When invoking CT Access demonstration programs for use with QX 2000 boards, the argument -A QDIMGR must be used in order to define the correct ADI manager.



For example:



c:>ctatest -A qdimgr



To run ctatest (with the option -A QDIMGR) select the program folder Natural MicroSystems QX / QX CT Access Test.


Note:  To adapt your configuration to a specific country or installation (e.g., PBXs, network, etc.), you need to use the parameter file provided with your installation software and stored in the installation directory (c:\nms\qx\cfg by default). See Appendix F for more details.










 
    (Page 1 of 1 in this chapter)  Version




 




tech_support@nmss.com



Copyright © 1999, Natural MicroSystems, Inc.   All rights
reserved.