(Page 1 of 1 in this chapter)

Chapter 4

Verifying the Installation

4.1 Introduction
4.1.1 About the Status Indicator LEDs
4.2 Verifying That Your Board is Installed Correctly
4.3 Verifying That Your Board is Working Correctly
4.4 Retrieving the AG Board Configuration: boardinf
4.5 Interactive Test Program: ctatest
4.5.1 Using swish for a Standalone Board
4.5.2 Using swish for Multiple Boards
4.5.3 Using ctatest with an AG-8 DID Board
4.5.4 Using ctatest with an AG-8 LS Board
4.5.5 Using ctatest with MVIP Connectivity

4.1 Introduction

This chapter provides procedures to verify that your AG-8 or AG-8/80 board is installed, configured, and operational.

Before you begin, make sure you have created an AG configuration file (ag.cfg) for your installation, as described in Chapter 3.

4.1.1 About the Status Indicator LEDs

The AG-8 and AG-8/80 boards have indicators (LEDs) on the end bracket for visual feedback of proper operation. They are located as shown:

Figure 11. LEDs on the End Bracket



The right-most LED is the external power supply indicator. It is only used on AG-8 or AG-8/80 boards with DID/E&M hybrids. When an external power source is properly connected to an AG board with DID/E&M hybrids, the LED is lit. This LED is not used on any other configurations of AG-8 or AG-8/80 boards.



The left-most LED blinks during board initialization diagnostics.






4.2	 Verifying That Your Board is Installed Correctly





Use agmon to verify that your AG board is installed and configured correctly. agmon interprets your AG configuration file and loads the appropriate files to the AG board(s). If loading and initialization is successful, the program continues to monitor the AG board(s) for errors.



agmon displays any errors that occur to the screen and appends them to an error log. The agerror.log file contains runtime errors that are not specific to any line or port. The default error log file for Windows NT is .\agerror.log. The default error log file for UNIX is /var/opt/nms/ag/agerror.log. 



agmon also creates the ag.rpt file, which contains a summary of the board configuration, including names of files which were loaded, and any errors that occurred in loading. 



For more details about agmon, see the AG Runtime Configuration & Developer's Manual.



To run agmon on Windows NT:


    


  1. Open a command window and enter:
    

    
agmon 



To run agmon on UnixWare or Solaris:


    


  1. Log in as root (or become the super-user). 
    

    

  2. If you have a graphical user interface, start a terminal session (shell prompt). 
    

    

  3. Enter:
    

    
agmon 
    
Note:  We strongly recommend leaving agmon running at all times to monitor the AG board(s) and capture errors.

 
    








4.3	 Verifying That Your Board is Working Correctly





To verify that an AG board is capable of interacting with CT Access and performing telephony functions, run the CT Access demonstration programs boardinf and ctatest. 



To run ctatest, your system needs a connection to either a live telephone line or to test equipment which supports call generation and voice path testing. 



You can run these verification procedures on a system with a standalone AG-8 or AG-8/80 board, or on a system with several MVIP-compatible boards connected by an MVIP bus. 



We recommend testing a newly-installed board as a standalone board before enabling its connection to the MVIP bus. Repeat the ctatest verification procedure after enabling MVIP connectivity for the new board. See Section 2.4 for more information about setting up MVIP connectivity.






4.4	 Retrieving the AG Board Configuration: boardinf





boardinf is a program that reports the board number, address, type, number of ports, memory, and DSP timeslot assignments for each AG board in a system.



boardinf opens the AG driver retrieves the configuration information for up to 16 AG boards. If an AG board exists and is properly initialized, its configuration is displayed and its DSP port addresses are displayed as one or more timeslot ranges.


 



To run boardinf:


    


  1. Make sure that you have initialized the AG board(s) by running agmon.
    

    

  2. Open a command window.
    

    

  3. Enter boardinf.
    

    
boardinf displays the configuration information for each AG board in the system that has been loaded and initialized.
    

  4. If no boards are detected, verify that the AG board(s) has been loaded and initialized by running agmon and repeat the command. If the AG board numbers, addresses, etc., are not as expected, review your ag.cfg file.
    

    
 
    







4.5	 Interactive Test Program: ctatest





ctatest is a menu-driven interactive program. Enter one- and two-letter commands to execute CT Access and ADI service functions. Some commands will prompt the user for additional input. For example, running a tone generator requires the user to specify frequencies and amplitudes. For more information about ctatest, see the CT Access Developer's Reference Manual.



ctatest can execute more than one asynchronous function concurrently. For example, you can run a tone detector (ET) and record voice (RF) simultaneously. You can abort any function by entering the respective "stop" command (DT and RS for tone and record).



If MVIP connectivity is disabled (EnableMVIP=NO in the ag.cfg file), then default local connections between the DSP resources and the line interfaces are nailed up as described in Section 5.6. 



If MVIP connectivity is enabled, no default connections are made. Before you start up ctatest, use the CT Access utility swish to establish the appropriate connections between network interfaces and DSP resources. You can use swish to make connections over the local bus for a standalone board, or over the MVIP bus for two or more boards that have been appropriately configured. 



Keep in mind that there are two naming conventions for the streams on the MVIP bus: the MVIP-90 switch model, and the MVIP-95 switch model. You can only use the MVIP-90 switch model for AG configuration file statements. For more information about using MVIP switching with AG-8 and AG-8/80 boards, and about MVIP switch models, see Chapter 5. 



To experiment with "output" and "input" functions simultaneously, execute two instances of ctatest. Use the swish MakeConnection command to make quad connections between two ports, one bound to each ctatest instance. See the Switching Service Developer's Reference Manual for more information about swish. 



For example, to interactively experiment with tone generation and detection, start a tone detector in the first ctatest instance and a tone generator in the second ctatest instance.






4.5.1	 Using swish for a Standalone Board





No default connections are made for a standalone board if MVIP connectivity is enabled in the AG configuration file. Use swish to connect the local network interface to the local DSP resource. You can use swish interactively, or create a script in a flat text file. 



The following example sequence of swish commands nails up the voice and signaling streams for all 8 line interfaces of an AG-8 board that has been configured as board 0. The swish commands are expressed in MVIP-95 terms.


openswitch ag8 = agsw 0

resetswitch ag8


# make voice connections
makeconnection ag8 local:0:0..7 to local:5:0..7
makeconnection ag8 local:4:0..7 to local:1:0..7

# make signaling connections
makeconnection ag8 local:2:0..7 to local:7:0..7
makeconnection ag8 local:6:0..7 to local:3:0..7

closeswitch ag8

exit

 






4.5.2	 Using swish for Multiple Boards





If MVIP connectivity is enabled, no default connections are made between multiple MVIP compliant boards during system initialization. Use the CT Access utility swish to:


    


  1. Connect the network interface on one board to the MVIP bus. 
    

    

  2. DSP resource on the second board to the MVIP bus.
    




You can use swish interactively, or create a script in a flat text file. 



The following example sequence of swish commands connects the DSP resources on an AG-24 board to the line interfaces on an AG-8 board. The AG-8 board has been configured as board 0. The AG-24 board's DSPs are nailed up to MVIP bus streams 2 and 3 in the ag.cfg file. The swish commands are expressed in MVIP-95 terms.


openswitch ag8 = agsw 0

resetswitch ag8

# make voice connections
makeconnection ag8 local:0:0..7 to mvip:5:0..7   # ag8 transmit voice
makeconnection ag8 mvip:4:0..7 to local:1:0..7   # ag8 receive voice

# make signaling connections
makeconnection ag8 local:2:0..7 to mvip:7:0..7   # ag8 transmit signaling
makeconnection ag8 mvip:6:0..7 to local:3:0..7   # ag8 receive signaling

closeswitch ag8

exit

 






4.5.3	 Using ctatest with an AG-8 DID Board 





You can connect a 2500-type telephone to a DID line interface on an AG-8 board for testing purposes. This provides a direct audio connection to the AG board. Use the telephone hook switch to simulate signaling from the network. Make sure you connect an external power supply to the board, as described in Section 2.6.2.


Note:  If the AG board is connected to a local telephone, make sure the external power supply provides only -24 V to the AG board to avoid overheating the DID hybrids. If the AG board is connected to the telephone network, you must supply -48 V to the board.


To use ctatest:


    


  1. Make sure that your ag.cfg file includes the following statement for the AG board that you will be using:
    

    
TCP = nocc.tcp
    
If necessary, edit the ag.cfg file and re-start agmon.
    

  2. Start ctatest by entering the following at the prompt:
    

    
ctatest -b boardnumber -s [n:]m [-p protocol] [-l]
    
where the command-line arguments are:
    
  

    


    
 Option
    

    		
 Description
    

    		
 Default
    


    
 -?
    

    		
 Displays a help screen.
    

    		
 None.
    


    
 -b n
    

    		
 Specifies the AG board number n.
    

    		
 0
    


    
 -s [n:]m
    

    		
 Assigns the DSP stream and timeslot. 
    

    		
 0
    


    
 -p protocol
    

    		
 Specifies the protocol to run. 
    

    		
 nocc
    


    
 -l
    

    		
 Shows low-level events.
    

    		
 None.
    



    


    

    

    

    

    
ctatest displays a menu of one- and two-letter commands.
    

  3. Enter OP to create a CTA context and open the ADI service.
    

    
CTAEVN_OPEN_SERVICES_DONE is displayed on your screen.
    

  4. Enter SP to start a protocol.
    

    
The following message appears:
       Enter protocol name ['nocc']: 


    

  5. Press Enter.
    

    
The following message appears:
       Event: ADIEVN_STARTPROTOCOL_DONE, Finished 


    

  6. Begin recording to memory by entering RM.
    

    
You should hear a beep on the handset.
    

  7. Say "Hello World" and wait.
    

    
The following message appears on the screen (you may see a different number of bytes):
       Event: ADIEVN_RECORD_DONE, Voice End, nbytes=15624.


    

  8. Play back your voice by entering PM.
    

    
The following message appears:
       Event: ADIEVN_PLAY_DONE, Finished, nbytes=15624.


    

  9. Enter CP to destroy the CTA context.
    

    

  10. Exit the test program by entering Q.
    

    
 
    







4.5.4	 Using ctatest with an AG-8 LS Board 





If your AG board has loop start hybrids, you will need to connect a loop start line as a test line to your system so you can call the test line from a telephone connected to another line. 



To use ctatest:


    


  1. Make sure that your ag.cfg file includes the following statement for the board that you will be using:
    

    
TCP = lps0.tcp
    
If necessary, edit the ag.cfg file and re-start agmon.
    

  2. Start ctatest as described in Section 4.5.
    

    
The initial ctatest menu appears.
    

  3. Enter OP to create a CTA context and open the ADI service.
    

    
CTAEVN_OPEN_SERVICES_DONE is displayed on your screen.
    

  4. Start a protocol by entering SP.
    

    
The following message appears:
    
Enter protocol name ['nocc']: 
    

  5. Enter the loop start protocol: lps0.
    

    
The following message appears:
    
Event: ADIEVN_STARTPROTOCOL_DONE, Finished 
    

  6. Place a call to the line connected to the AG board.
    

    
The following message appears:
    
Event: ADIEVN_INCOMING_CALL
    

  7. Initiate answering the call by entering AC.
    

    
The following message appears:
    
Number of rings [1]: 
    
 
    

    

  8. Press Enter.
    

    
You should hear a single ring tone.
    
The following messages appear:
    
Event: ADIEVN_ANSWERING_CALL
    Event: ADIEVN_CALL_CONNECTED, Answered
    

  9. Begin recording to memory by entering RM.
    

    
You should hear a beep on the handset.
    

  10. Say "Hello World," and wait.
    

    
The following message appears on the screen (you may see a different number of bytes):
    
Event: ADIEVN_RECORD_DONE, Voice End, nbytes=15624.
    

  11. Play back your voice by entering PM.
    

    
You should hear "Hello World," and ctatest displays:
    
Event: ADIEVN_PLAY_DONE, Finished, nbytes=15624.
    

  12. Quit the test program by entering Q.
    







4.5.5	 Using ctatest with MVIP Connectivity





To verify that MVIP connectivity works in a system with an AG-8 board and an AG-24 board:


    


  1. Connect a 2500-type telephone to a line interface on the AG-8 board, as appropriate for the type of line interface hybrid.
    

    

  2. Use swish to connect the network interface on the AG-8 board to DSP resources on the AG-24 board over the MVIP bus.
    

    

  3. Start up ctatest with the -b n argument, where n is the board number for the AG-24 board.
    

    

  4. Make an incoming call from the handset connected to the AG-8 board.
    

    

  5. If MVIP connectivity is working correctly, the AG-24 board should generate messages (displayed by ctatest) that indicate that it is receiving an incoming call.
    









 
    (Page 1 of 1 in this chapter)




 




tech_support@nmss.com



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