LED	Purpose	Description
D3 - D6	DSPx_RST (4 red LEDs) DSPx_XF (4 green LEDs)	The corresponding DSP is communicating with the NS486. Red = Problem Green = No problem
D9	HMIC (green)	Lit indicates no problem with the HMIC. Not lit indicates a problem with the HMIC.
D9	CLK (red)	Lit indicates no problem with the clock section of the HMIC. Not lit indicates a problem with the clock section of the HMIC.
D10	OWN (green)	Owner of SRAM. Lit indicates idle of host. Not lit indicates coprocessor.
D10	TD (red)	Transfer direction bit. Lit indicates host access to SRAM. Not lit indicates 486 access to SRAM.
D11	BUSY (green)	Lit = SRAM is idle. Not lit = SRAM is in use.
D11	76GO (red)	NS486 out of reset.

4.3 Verifying That the Board is Installed Correctly

Create a configuration file (ag.cfg) for your installation by copying an example file and editing it to match your specific configuration. Use the blocate utility to determine the bus and slot number. Refer to Chapter 3 for more information about the configuration file. Refer to Appendix D for more information about the blocate utility.
To test the AG 2000 in a standalone mode before connecting to a live network, set the ClockRef keyword to OSC in the ag.cfg file. In this configuration, the AG 2000 derives its timing reference from an on-board oscillator.
Use agmon to verify that the AG 2000 board is installed and configured correctly. agmon interprets the AG configuration file and loads the appropriate files to the AG 2000 board(s). If loading and initialization is successful, the program continues to monitor the AG 2000 board(s) for errors.
To run agmon on Windows NT, open a command window and enter: agmon
To run agmon on UnixWare and Solaris: Log in as root (or become the super-user). In a graphical user interface, start a terminal session (shell prompt). Enter: agmon
agmon creates two files in the current directory, ag.rpt and agerror.log.
ag.rpt contains a summary of the board configuration, including names of files which were loaded, and any errors that occurred during loading. You can specify another configuration file using the -f switch.
Errors that occur are displayed in the agmon session and are appended to the error file, agerror.log.
agerror.log contains runtime errors that are not specific to any line or port. You can specify an alternate error file name and path with the -e option to agmon.
For more information on agmon, refer to the AG Runtime Configuration and Developer's Manual. Note: agmon should be left running at all times so errors will be captured.

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 and retrieves the configuration information for up to 16 AG 2000 boards. If an AG 2000 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: Make sure that you have initialized the AG 2000 board(s) by running agmon. Open a command window. Enter: boardinf boardinf displays the configuration information for each AG 2000 board in the system that has been loaded and initialized. If no boards are detected, verify that the AG 2000 board(s) has been loaded and initialized by running agmon and repeat the command. If the AG 2000 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.4, Default Connections.
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-95 switch model for AG 2000 boards.
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. Refer to 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 of swish commands nails up the voice and signaling streams for all 8 line interfaces of an AG 2000 board that has been configured as board 0. The swish commands are expressed in MVIP-95 terms. openswitch ag2000 = agsw 0 resetswitch ag2000 # make voice and signaling connections makeconnection ag2000 local:0:0..7 to local:5:0..7 QUAD closeswitch ag2000 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: Connect the network interface on one board to the MVIP bus. 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 of swish commands connects the DSP resources on an AG-24 board to the line interfaces on an AG 2000 board. The AG 2000 board has been configured as board 0. The AG-24 board's DSPs are nailed up to MVIP-90 bus streams 2 and 3 in the ag.cfg file. The swish commands are expressed in MVIP-95 terms. openswitch ag2000 = agsw 0 resetswitch ag2000 # make transmit and receive voice and signaling connections makeconnection ag2000 local:0:0..7 to mvip:5:0..7 QUAD closeswitch ag2000 exit

4.5.3 Using ctatest with an AG 2000 DID Board

For testing purposes, you can connect a 2500-type telephone to a DID line interface signaling module on an AG 2000 board. This provides a direct audio connection to the AG 2000 board. Use the telephone hook switch to simulate signaling from the network. Ensure that the external power connector is connected to a -48 VDC power supply (refer to Figure 14 in Section 2.7.1, Using 2 Wire Interfaces).
Use the subscriber loop interface for an actual connection to a telephone in the final system setup. (You may use either did0.tcp or did1.tcp.)
To use ctatest: Make sure that the ag.cfg file includes the following statement for the board that you will be using: TCP = did1.tcp If necessary, edit the ag.cfg file and re-start agmon. Start ctatest as described in Section 4.5. The initial ctatest menu appears. Enter OP to create a CTA context and open the ADI service. CTAEVN_OPEN_SERVICES_DONE is displayed on your screen. Start a protocol by entering SP. The following message appears: Enter protocol name ['nocc']: Enter the DID protocol: did1 or wnko. The following message appears: Event: ADIEVN_STARTPROTOCOL_DONE, Finished Lift the receiver and dial 123. The following message appears: Event: ADIEVN_INCOMING_CALL Called number = `123' Initiate answering the call by entering AC. The following message appears: Number of rings [1]: Press Enter. You should hear a single ring tone. The following messages appear: Event: ADIEVN_ANSWERING_CALL Event: ADIEVN_CALL_CONNECTED, Answered Begin recording to memory by entering RM. You should hear a beep on the handset. 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. Play back your voice by entering PM. You should hear "Hello World," and ctatest displays: Event: ADIEVN_PLAY_DONE, Finished, nbytes=15624. Quit the test program by entering Q.

4.5.4 Using ctatest with an AG 2000 Subscriber Loop Board

If the AG 2000 board has a subscriber loop line interface signaling module, connect a 2500 set so you can make a call.
To use ctatest: Make sure that the ag.cfg file includes the following statement for the board that you will be using: TCP = sta0.tcp If necessary, edit the ag.cfg file and re-start agmon. Start ctatest as described in Section 4.5. The initial ctatest menu appears. Enter OP to create a CTA context and open the ADI service. CTAEVN_OPEN_SERVICES_DONE is displayed on your screen. Start a protocol by entering SP. The following message appears: Enter protocol name ['nocc']: Enter the subscriber loop protocol: sta0. The following message appears: Event: ADIEVN_STARTPROTOCOL_DONE, Finished Lift the receiver (you should get a dial tone) and dial 123. The following message appears: Event: ADIEVN_INCOMING_CALL Called number = `123' Initiate answering the call by entering AC. The following message appears: Number of rings [1]: Press Enter. You should hear a single ring tone. The following messages appear: Event: ADIEVN_ANSWERING_CALL Event: ADIEVN_CALL_CONNECTED, Answered Begin recording to memory by entering RM. You should hear a beep on the handset. 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. Play back your voice by entering PM. You should hear "Hello World," and ctatest displays: Event: ADIEVN_PLAY_DONE, Finished, nbytes=15624. Quit the test program by entering Q.

4.5.5 Using ctatest with an AG 2000 Loop Start Board

If the AG 2000 board has loop start line interface signaling module, 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: Make sure that the 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. Start ctatest as described in Section 4.5. The initial ctatest menu appears. Enter OP to create a CTA context and open the ADI service. CTAEVN_OPEN_SERVICES_DONE is displayed on your screen. Start a protocol by entering SP. The following message appears: Enter protocol name ['nocc']: Enter the loop start protocol: lps0. The following message appears: Event: ADIEVN_STARTPROTOCOL_DONE, Finished Place a call to the line connected to the AG 2000 board. The following message appears: Event: ADIEVN_INCOMING_CALL Initiate answering the call by entering AC. The following message appears: Number of rings [1]: Press Enter. You should hear a single ring tone. The following messages appear: Event: ADIEVN_ANSWERING_CALL Event: ADIEVN_CALL_CONNECTED, Answered Begin recording to memory by entering RM. You should hear a beep on the handset. 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. Play back your voice by entering PM. You should hear "Hello World," and ctatest displays: Event: ADIEVN_PLAY_DONE, Finished, nbytes=15624. Quit the test program by entering Q.

4.5.6 Using ctatest with MVIP Connectivity

To verify that MVIP connectivity works in a system with an AG 2000 board: Connect to a line interface on the AG 2000 board, as appropriate for the type of line interface signaling module. Use swish to connect the network interface on the AG 2000 board to DSP resources on the AG-24 board over the MVIP bus. Start up ctatest with the -b n argument, where n is the board number for the AG-24 board. Place a call to the line connected to the AG 2000 board. 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.

4.6 Demonstration Programs

The following demonstration programs are provided with CT Access and may be used to verify that the AG 2000 board is operating correctly: Program Description ctatest Demonstrates CT Access functions. incta Inbound call demonstration. outcta Outbound call demonstration. prt2prt Demonstrates call transfer from an incoming line to an outgoing line and uses the Switching service to make connections and to send patterns. vceplay Demonstrates using the Voice Message service to play messages in voice files. vcerec Records one or more messages to a voice file. Note: Executables for incta, outcta, and prt2prt are in the respective sub-directories under nms\ctaccess\demos.
To run these demonstration programs on the AG 2000 board, specify the MVIP-95 stream and slot number of the local DSP resource on which to run the program. If H.100 connectivity is disabled (EnableMVIP=NO), then default switching connections between the on-board DSP resources and signaling modules are initialized as described in Section 5.4, Default Connections. To run ctatest on DSP port 0, enter: ctatest -s0 To run ctatest on DSP port 2, enter: ctatest -s2
If EnableMVIP=YES, then no default connections are made. Switching connections have to be made between DSP resources and signaling modules using the CT Access Switching service or the swish utility.
Refer to the CT Access documentation for details on CT Access demonstration programs.

Program	Description
`ctatest`	Demonstrates CT Access functions.
`incta`	Inbound call demonstration.
`outcta`	Outbound call demonstration.
`prt2prt`	Demonstrates call transfer from an incoming line to an outgoing line and uses the Switching service to make connections and to send patterns.
`vceplay`	Demonstrates using the Voice Message service to play messages in voice files.
`vcerec`	Records one or more messages to a voice file.

(Page 1 of 1 in this chapter)

tech_support@nmss.com