4.1 Introduction

4.2 Status Indicator LEDs

4.3 Verifying That the Board is Installed Correctly

4.4 Verifying That the Board is Working Correctly

4.5 Demonstration Programs

4.1 Introduction

This chapter provides procedures to verify that the AG Quad board is installed and configured correctly. Before you begin, make sure you have created a system configuration file and a board keyword file. For more information about these files, refer to Chapter 3.

4.2 Status Indicator LEDs

AG Quad boards have indicators (LEDs) for each trunk on the end bracket. The location of the indicators is shown in Figure 20.

LED	Description
Red	Indicates loss of frame, loss of signal, or bit rate error.
Yellow	Indicates remote loss of frame or remote loss of signaling multiframe.
Green	Indicates proper frame SYNC to the trunk: all required framing alignment has been found. This LED is OFF if one or more of the following conditions exist: all ones alarm (AIS), loss of frame, loss of signaling multiframe, or CRC errors (when the board is configured for ESF).

Figure 20. AG Quad LEDs

4.3 Verifying That the Board is Installed Correctly

To verify that you have installed the board correctly:

1. Create a board keyword file to boot the AG Quad board by copying or editing one of the sample board keyword files to match your specific configuration. Refer to Chapter 3 for more information about the board keyword files. You may want to use the qwnkpi.cfg file that configures the board for the Wink Start protocol.

2. Run oammon to monitor the status of all boards.

3. Use the pciscan utility to determine the bus and slot number. For more information about the pciscan utility, refer to the OAM System User's Manual.

4. Edit the oamsys.cfg file to reflect the board locations in your system.

5. Boot the board using the command:
   oamsys

4.4 Verifying That the Board is Working Correctly

To verify that the board is working:

1. Set the Clocking.HBus.ClockSource keyword to NETWORK in the board keyword file.

2. Set the Clocking.HBus.ClockSourceNetwork keyword to n where n is the 1-based number of the trunk (1 - 4) that the board is using as a reference.

3. Set the Clocking.HBus.ClockMode keyword to STANDALONE.

4. Boot the board using the command:
   oamsys

5. Run the digital trunk monitor utility, trunkmon.
   trunkmon monitors alarms and gathers performance statistics for T1 and E1 trunks. On a T1 trunk, an alarm state is entered upon the presence of a Red, Yellow, or Blue alarm. On an E1 trunk, an alarm state is entered upon local or remote loss of frame, or excessive bit errors.
   To run trunkmon, enter the following at the command prompt:

      trunkmon -b<board>
   

   
   If no T1/E1 trunk cables are connected to the AG Quad board, trunkmon shows a loss of frame sync (Frame sync: No Frm) and an alarm state on all trunks. The red alarm LED on the front panel should be lit for all trunks.

6. Connect a cross-over cable between any two trunks of the AG Quad board. The Frame Sync status should immediately change to OK and the green LEDs for those trunks will light. The remote alarm (yellow) LEDs will light to show that the trunk is indicating an alarm state to the other side. About 15 seconds (for T1 trunks, immediately for E1 trunks) after frame sync has been acquired, both trunks leave the alarm state. trunkmon indicates NONE for the alarm status and the red and yellow alarm LEDs go out. The frame sync (green) LEDs remain lit.
   For more information about trunkmon, refer to the OAM System User's Manual.

4.5 Demonstration Programs

The following demonstration programs are provided with CT Access and may be used to verify that the AG Quad 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 the use of the Switching service to make connections, and 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.

Running these demonstration programs requires a connection to either a live T1 or E1 trunk or a connection to T1 or E1 test equipment that supports call generation and voice path testing. It is also possible to use the T1 or E1 cross-over cable to loopback one trunk to another trunk. Calls placed on the first trunk can then be received on the other trunk.

To run these demonstration programs on the AG Quad 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 (Clocking.HBus.ClockMode = STANDALONE), then default switching connections between the on-board DSP resources and T1 or E1 trunks are made, as described in Section 5.5.

For example, on an AG Quad T board with Clocking.HBus.ClockMode = STANDALONE and NetworkInterface.T1E1[x].SignalingType = CAS, the DSP resources on stream 16, timeslots 0..23 are connected to the first trunk. Timeslots 24..47 are connected to the second trunk, and so on.

Because the CT Access demonstration programs use DSP resources such as voice processing in the call connected state, call control resource management cannot be used. To run the CT Access demonstration programs with the AG Quad board, disable call control resource management by setting CCMode = NONE. Limit the number of instances of the demonstration programs to 60 ports or fewer to avoid resource errors.

• To run ctatest on the first channel of the first trunk, enter:

     ctatest -s0
  
  

• To run ctatest on the first channel of the second trunk, enter:

     ctatest -s24
  
  

Switching connections have to be made between DSP resources and T1 or E1 trunks using the CT Access Switching service or the swish utility. Refer to Chapter 5 for more details on AG Quad switching.

Refer to the CT Access Developer's Reference Manual for details on CT Access demonstration programs.