(Page 1 of 1 in this chapter)

Chapter 4

Verifying the Installation

4.1 Introduction
4.2 Verifying That Your Board is Installed Correctly
4.2.1 About agmon
4.2.2 Running agmon
4.3 Verifying That Your Board is Working Correctly
4.3.1 Using swish
4.3.2 Retrieving the AG Board Configuration: boardinf
4.3.3 Interactive Test Program: ctatest

4.1 Introduction

This chapter provides procedures to verify that your AG-24/30/48/60 boards are installed, configured, and operational.

Before you begin, make sure you have created an AG configuration file (ag.cfg) for your installation by copying an example file and editing it to match your configuration, as described in Chapter 3.

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).

4.2.1 About agmon

agmon creates two files, ag.rpt and agerror.log.

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

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 displays errors to the screen as well as recording them to the error log.

If the AG configuration file is specified in the agmon command statement with a path specification, agmon only looks for the specified file in that directory. Otherwise, agmon first looks in the current working directory. For Windows NT, if the file does not exist in the current working directory, agmon looks in the directories specified in the AGLOAD environment variable. For UNIX, if the file does not exist in the current working directory, agmon looks in /opt/nms/ag/load.

If loading and initialization is successful, agmon continues to monitor the AG board(s) for errors.

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

4.2.2 Running agmon

To run agmon under Windows NT:

To run agmon under UNIX:

  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 your AG board is capable of interacting with CT Access and performing telephony functions, run the CT Access demonstration programs boardinf and ctatest. 



To use ctatest as described in Section 4.3.3, your system must have a network interface board with a connection to either a live telephone line or to test equipment which supports call control and voice transmission. The network interface board must be connected to the AG-24/30/48/60 board over the MVIP bus so that the two boards can share voice data, signaling data, and resources. Use the swish utility to make the connection between the network interface board and the MVIP bus. 



The procedures in this chapter use an example system with an AG-8 DID board to provide the line interfaces, and an AG-24 board.



For more information about boardinf and ctatest, see the CT Access Developer's Reference Manual. For more information about MVIP connectivity, see Getting Started With MVIP and the Switching Service Developer's Reference Manual.






4.3.1	 Using swish 





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




See the Switching Service Developer's Reference Manual for information about the swish utility.


 






4.3.2	 Retrieving the AG Board Configuration: boardinf





boardinf is a program that reports the board number, address, type, number of ports, memory, and MVIP stream/timeslot assignment for each AG board.



boardinf opens the AG driver and attempts to retrieve the configuration for up to 16 AG boards. If an AG board exists and is properly initialized, its configuration is displayed and its MVIP assignments are retrieved and displayed as an array of 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 at the prompt.
    

    
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 board numbers, addresses, etc., are not as expected, review your ag.cfg file.
    

    
 
    







4.3.3	 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 for additional information, such as frequencies and amplitudes for tone generators.



You can continue to enter commands while asynchronous functions execute. For example, you can run a tone detector (ET) and record voice (RF) simultaneously. Any of these functions can be aborted by entering the respective "stop" command (DT and RS for tone and record).



To run ctatest:


    


  1. Make sure the system includes a line interface board (such as an AG-8 DID board) connected to the AG-24/30/48/60 board over the MVIP bus, and that the appropriate MVIP switching has been performed.
    

    

  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
    


    
 -?
    

    		
 Display help screen.
    


    
 -b n
    

    		
 Specifies the AG board number n. Default = 0
    


    
 -s n:m
    

    		
 Specifies the DSP stream and timeslot. Default = 0:0
    


    
 -p protocol
    

    		
 Specifies the protocol to run. Default = nocc.
    


    
 -l
    

    		
 Shows low-level events.
    



    


    

    

    

    

    
Make sure boardnumber specifies the AG-24/30/48/60 board number as assigned in the AG configuration file and n:m specifies the MVIP-90 stream/timeslot assignment as set in the ag.cfg file and retrieved by boardinf.
    
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']: 


    
The following message appears:
       Event: ADIEVN_STARTPROTOCOL_DONE, Finished 


    

  5. Begin recording to memory by entering RM.
    

    
You should hear a beep on the handset.
    

  6. Say "Hello World" and wait.
    

    
A message similar to the following example appears on the screen:
       Event: ADIEVN_RECORD_DONE, Voice End, nbytes=15624.


    
Note:  Your system may display a different number for nbytes.


  7. Play back your voice by entering pm.
    

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


    
You should hear "Hello World."
    

  8. Enter CP to destroy the CTA context.
    

    

  9. Exit the test program by entering q.
    












 
    (Page 1 of 1 in this chapter)




 




tech_support@nmss.com



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