4.1 Integrating Platform Support for DLCP with Aztek Protocol Stacks

4.2 Integrating NMS GR303 and Aztek Protocol Software

4.2.1 Specifying T1 Link and HDLC Channel Locations

4.2.2 Verifying T1 Connections

4.2.3 Using nms303tool

4.2.4 Using the aim303 Utility

4.2.5 Testing the Integration

4.2.6 Building a Complete GR-303 Application

4.3 Integrating NMS V5 and Aztek AV5

4.3.1 Specifying E1 Link and HDLC Channel Locations

4.3.2 Verifying E1 Connections

4.3.3 Using nmsv5tool

4.3.4 Using the aimv5 Utility

4.3.5 Testing the Integration

4.3.6 Building a Complete AN Application

4.1 Integrating Platform Support for DLCP with Aztek Protocol Stacks

Platform Support for DLCP software is designed to work with the Aztek's Access303, Exchange303, and AV5 products. Platform Support for DLCP software includes two libraries, the NMS GR303 library and NMS V5 library, that provide physical layer access for the Access303, Exchange303, and AV5 protocol stacks. The Aztek protocol stacks use the NMS libraries to establish connections to and communicate with GR-303 or V5.2 interfaces.

The general rule for integrating different layers of a protocol is that the lower layers should start first and finish last. When integrating the Platform Support for DLCP libraries (the lower layer) with Access303, Exchange303, and AV5 libraries (the upper layer), an application should always follow this rule. That is, applications should initialize the Platform Support for DLCP libraries first, and tear them down last.

This section describes the steps developers need to perform to integrate RDT, IDT, and AN applications. Developers can use the Aztek Integration Menu tool (AIM) in combination with the nms303tool and nmsv5tool demonstration programs to test and troubleshoot the integration of the Aztek and Platform Support for DLCP libraries.

Note: NMS recommends that developers review this section thoroughly before designing RDT, IDT, or AN systems.

4.2 Integrating NMS GR303 and Aztek Protocol Software

This section describes the steps for building an integrated RDT or IDT applications that use the Aztek Access303 or Exchange303 protocol stack library and the NMS GR303 library.

Before integrating the various parts of the RDT or IDT system, you must create a mapping between the GR-303 protocol structures and data types defined by the layers of the Aztek GR-303 stack and the NMS GR303 library. The following table shows mappings for data structures that are common for different functions within the Access303 and Exchange303 libraries and the NMS GR303 libraries:

GR-303 Protocol Data	NMS GR303 Data Types	Access303 Data Types
Interface ID	NMS_GR303_INTERFACE_ID_T	AR303_INTERFACE_ID_T
Primary and standby DS1 locations	N/A	AR303_PATH_LOCATION_T
EOC or TMC protocol channel	N/A	AR303_PROTOCOL_CHANNEL_T
Primary and standby DS1 locations for an EOC or TMC protocol channel	N/A	AR303_CHANNEL_LOCATION_T
TMC and EOC channels for LAPD protocol to send and receive data	NMS_GR303_CHANNEL_LOCATION_T HDLC channel location with respect to hardware.	AR303_CHANNEL_T
TMC protocol: bearer -channel time slot assignment for ports to make connections and process CAS signaling.	Logical timeslot number of a T1 trunk on a CG board.	AR303_CHANNEL_T
DS1 link	NMS_GR303_DS1_LOCATION_T	AR303_DS1_T
DS0 timeslot	Logical timeslot number of a trunk on a CG board.	AR303_DS0_T

4.2.1 Specifying T1 Link and HDLC Channel Locations

To configure the GR303 library software to work in conjunction with CG boards, applications must define a pair of data types to reference common location information for boards, trunks, and HDLC channels.

• The NMS_GR303_INTERFACE_ID_T data type specifies the ID associated with a particular lower level interface.

• The NMS_GR303_DS1_LOCATION_T data type provides information about the specific location of DS1 links. Applications use the following structure to specify the location of a particular DS1 link on a CG board:
  struct {
  DWORD boardNb;
  DWORD trunkNb;
  } CG;
  Where the data type specifies the following information:

  Parameters	Description
  boardNb	Logical board number of the board where the DS1 link resides.
  trunkNb	Logical trunk number associated with the DS1 link.

• The NMS_GR303_CHANNEL_LOCATION_T data type provides information about the specific locations of HDLC channels. Applications use the following structure to specify the location of particular HDLC channels on a CG board:
  struct {
  DWORD boardNb;
  DWORD trunkNb;
  DWORD timeslotNb;
  } CG;
  Where the data type specifies the following information:

  Parameters	Description
  boardNb	Logical board number of the associated board.
  trunkNb	Logical trunk number on which the HDLC channel is located.
  timeslotNb	Physical timeslot number to associate with the HDLC channel in the range 1 to 24. · Set the timeslot number to 12 for EOC data links · Set the timeslot number to 24 for TMC data links

4.2.2 Verifying T1 Connections

You can use Aztek Access303 or Exchange303 software with NMS GR303 library software to develop GR-303 compliant RDT-side applications. However, before you can run the application, you must connect the RDT side of the system to the IDT side of the GR-303 protocol with a T1 cable. After you connect the T1 cable to the CG board, boot the CG board, and start the application, you can verify that T1 links are synchronized by following these steps:

1. Boot the board and observe the trunk LEDs on the board's front panel. The LEDs remain in an alarm condition (either yellow or red) for approximately 15 seconds after the board is booted, until frame synchronization is acquired. When the trunks leave the alarm state and became synchronized, the green LED remains lit for each trunk.

2. Run the trunkmon utility with the -b (board number) argument to monitor alarms and gather performance statistics for the T1 trunks. When all trunks are synchronized, trunkmon displays the alarm status for the board as NONE.

3. If the trunks connected to the external T1 cable link stay in an alarm state, connect a cross-over cable between any two trunks of the CG board. If the LEDs show that the trunks are in frame synchronization, this indicates that there is a problem with the T1 link rather than the board.

For more information about CG board LEDs, the trunkmon utility, and using cross-over cables with CG boards, refer to the CG board documentation.

4.2.3 Using nms303tool

To use the nms303tool demonstration program:

1. Compile the program from the source code provided with the Platform Support for DLCP software.

2. Start nms303tool.

3. Start the aim303 utility (the AIM 303 Task must running).

4. Enter commands as needed from the nmstool303 or aim303 command line.

Refer to Chapter 9 for more information about running nms303tool.

4.2.4 Using the aim303 Utility

To use the aim303 utility:

1. Compile the program from the source code provided with the Access 303 software.

2. Start the Access303 or Exchange303 software (by running nms303tool) and make sure that the Aztek library AIM task is set to listen on the appropriate socket for aim303 messages.

3. Start the aim303 utility by entering the following at the command line:
   aim303 <hostname>
   Where hostname is the name of the machine running the GR-303 application.
   The aim303 program reports when the connection is established and displays a menu of available commands.

4. Enter commands as needed.

Refer to the Aztek Integration Menu AIM-303 User Guide for more information about using the aim303 utility.

4.2.5 Testing the Integration

Once you have started the nms303tool and aim303 programs, you can enter the commands at the command line of either program to perform operations on
GR-303 interfaces. These programs allow you to perform a variety of tasks, such as executing NMS GR303 or Aztek GR-303 library functions, configuring and tracking task tracing information, verifying the status integration stack, and displaying status information about NMS GR303 interfaces.

For more information about using aim303, refer to the Aztek Integration Menu AIM-303 User Guide. For more information about using nms303tool, refer to Chapter 9 of this manual.

4.2.6 Building a Complete GR-303 Application

After completing the basic tasks required to integrate and verify the Aztek and NMS GR303 libraries, you can build an enhanced application by modifying the nms303tool source code to provide additional functionality or creating a new application using functions from the NMS GR303 library.

Depending on the GR-303 application's system requirements, you can use other NMS hardware and software to support specific functionality. For example, you can use the NMS Switching service to connect ports associated with a GR-303 interface to specific CT bus timeslots, or use other NMS software to control robbed-bit signaling or media processing on connected ports.

For more information about the association between Aztek Access303 or Exchange303 library functions and NMS GR303 library functions when performing typical tasks, refer to Chapter 5.

4.3 Integrating NMS V5 and Aztek AV5

This section describes the steps for building an integrated AN application that uses the Aztek AV5 protocol stack library and the NMS V5 library.

Before integrating the various parts of the AN system, you must create a mapping between the V5.2 protocol structures and data types defined by the layers of the AV5 protocol stack and by the NMS V5 library. The following table shows mappings for data structures that are common for different functions within the AV5 and NMS V5 libraries:

V5.2 Protocol Data	NMS V5 Data Types	Aztek AV5 Data Types
Interface ID	NMS_V5_INTERFACE_ID_T	V5_INTERFACE_ID_T
E1 link ID	N/A	V5_LE_LINK_ID_T
E1 location	NMS_V5_E1_LOCATION_T (E1 trunk location on the CG board)	V5_E1_T (AV5 local ID)
Communication Path (C-path) for Control, Link Control, PSTN, BCC, and Protection protocols	N/A	V5_C_PATH_T
Communication Channel (C-channel) to carry a group of one or more C-paths	N/A	V5_LOGICAL_C_CHANNEL_T
	NMS_V5_CHANNEL_LOCATION_T HDLC channel location with respect to hardware.	V5_PHYSICAL_C_CHANNEL_T
Number of logical C-channels	num_channels function parameter when provisioning a variant.	V5_PROVISION_DATA_T (numLogCchan parameter)
Protection group number	N/A	V5_PROTECTION_GRP_NUM_T
Protection group standby channels	N/A	V5_PROTECT_STNDBY_T
	NMS_V5_CHANNEL_LOCATION_T (HDLC channel location with respect to the hardware)	V5_PHYSICAL_C_CHANNEL_T for each standby
Provisioned variant	Capable of provisioning and destroying a standby variant.	V5_VARIANT_ID_T
PSTN or ISDN port on AN side	N/A	V5_AN_PORT_T
BCC protocol: Bearer-channel timeslot on E1	NMS_V5_E1_LOCATION_T and hardware-mapped logical timeslot number.	V5_E1_T and V5_TIME_SLOT_T
C-channels send/receive data	NMS_V5_CHANNEL_LOCATION_T HDLC channel location with respect to the hardware.	V5_E1_T and V5_C_CHANNEL_T
BCC protocol: Bearer-channel port location on AN side	Hardware-mapped logical timeslot number on an E1 trunk on an CG board.	V5_AN_PORT_T

4.3.1 Specifying E1 Link and HDLC Channel Locations

To configure the NMS V5 library software to work in conjunction with CG boards, applications must define a pair of data types to reference common location information for boards, trunks, and HDLC channels.

• The NMS_V5_INTERFACE_ID_T data type specifies the ID associated with a particular lower level interface.

• The NMS_V5_E1_LOCATION_T data type provides information about the specific location of E1 links. Applications use the following structure to specify the location of particular E1 trunks on a CG board:
  struct {
  DWORD boardNb;
  DWORD trunkNb;
  } CG;
  Where the data type specifies the following information:

  Parameters	Description
  boardNb	Logical board number of the board where the E1 link resides.
  trunkNb	Logical trunk number associated with the E1 link.

• The NMS_V5_CHANNEL_LOCATION_T data type provides information about the specific locations of HDLC channels. Applications use the following structure to specify the location of particular HDLC channels on a CG board:
  struct {
  DWORD boardNb;
  DWORD trunkNb;
  DWORD timeslotNb;
  } CG;
  Where the data type specifies the following information:

  Parameters	Description
  boardNb	Logical board number of the associated board.
  trunkNb	Logical trunk number on which the HDLC channel is located.
  timeslotNb	Physical timeslot number to associate with the HDLC channel. Specify timeslots 15, 16, and 31 as needed in accordance with the V5 protocol.

4.3.2 Verifying E1 Connections

Developers can use Aztek AV5 library and NMS V5 library software to develop applications on the AN side of the V5.2 protocol. However, before you can run the application, you must connect the AN side of the system to the local exchange (LE) end of the V5.2 protocol through an E1 cable. After you connect the E1 cable to the CG board, boot the CG board, and start the LE side of the system, you can verify that E1 links are synchronized by following these steps.

1. Boot the board and observe the trunk LEDs on the board's front panel. The LEDs remain in an alarm condition (either yellow or red) for approximately 15 seconds after the board is booted, until frame synchronization is acquired. When the trunks leave the alarm state and are synchronized, the green LED remains lit for each trunk.

2. Run the trunkmon utility with the -b (board number) argument to monitor alarms and gather performance statistics for the E1 trunks. When all trunks are synchronized, trunkmon displays the alarm status for the board as NONE.

3. If the trunks connected to the external E1 link stay in an alarm state, connect a cross-over cable between any two trunks of the CG board. If the LEDs show that the trunks are in frame synchronization, this indicates that there is a problem with the E1 link rather than the board.

For more information about CG board LEDs, the trunkmon utility, and using cross-over cables with CG boards, refer to the CG board documentation.

4.3.3 Using nmsv5tool

To use the nmsv5tool demonstration program:

1. Compile the program as an executable from the source code provided with the Platform Support for DLCP software.

2. Start nmsv5tool.

3. Start the aimv5 utility.

4. Enter commands as needed from the nmstoolv5 or aimv5 command line.

Refer to Chapter 9 of this manual for the more information about running nmsv5tool.

4.3.4 Using the aimv5 Utility

To use the aimv5 utility:

1. Compile the program as an executable from the source code provided with the AV5 software.

2. Initialize the AV5 software (by running nmsv5tool) and make sure that the AV5 library AIM task is to listening on the appropriate socket for the AIM messages.

3. Start aimv5 by entering the following at the command line:
   aimv5 <hostname>
   Where hostname is the name of the machine running the AN application.
   The aimv5 program reports when the connection is established and displays a menu of available commands.

4. Enter commands as needed.

4.3.5 Testing the Integration

Once you have started the nmsv5tool and aimv5 programs, you can enter commands at the command line of either utility to perform operations on V5.2 interfaces. These programs allow you to perform a variety of tasks, such as executing API functions, toggling task tracing, verifying the integration status, and displaying status information.

For more information about using aimv5, refer to the Aztek documentation. For more information about using nmsv5tool, refer to Chapter 9 of this manual.

4.3.6 Building a Complete AN Application

After completing the basic tasks in integrating and verifying the AV5 and NMS V5 libraries, you can build an enhanced application by modifying the nmsv5tool source code to provide additional functionality or creating a new application using functions from the NMS V5 library.

You can use the NMS Switching service to connect ports associated with a V5.2 interface to specific CT bus timeslots. Depending on the AN system requirements, you can also use other NMS software and hardware to provide access to PSTN or IP networks, or to provide Digital Loop Carrier (DLC), Hybrid Fiber Coax (HFC), or Wireless Local Loop (WLL) support.

For more information about the association between Aztek AV5 library functions and NMS V5 library functions when performing typical tasks, refer to Chapter 6.