This topic describes the steps for building 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, create a mapping between the GR303 protocol structures and the data types defined by the layers of the Aztek GR303 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:
|
GR303 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 timeslot 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 |
To configure the GR303 library software to work 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 (as defined by OAM). |
|
trunkNb |
Logical trunk number associated with the DS1 link (as defined by OAM). |
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.
|
You can use Aztek Access303 or Exchange303 software with NMS GR303 library software to develop GR303 compliant RDT-side applications. However, before you can run the application, connect the RDT side of the system to the IDT side of the GR303 protocol with a T1 cable. After you connect the T1 cable to the CG board, boot the CG board and start the application. Follow these steps to verify that the T1 links are synchronized:
|
Step |
Action |
|
1 |
Set up appropriate CT bus clocking for the system. In a single board system with T1 network connectivity, configure the board clocks to slave to a network interface. In a typical multiple-board system, configure one board to derive its clocking from the network and to act as the clock master for the other boards on the system. Configure the remaining boards to slave to the CT bus clock for inter-board synchronization. Refer to the NMS OAM System User's Manual or the appropriate board installation manual for more information about setting up CT bus clocking. |
|
2 |
Boot the board and observe the trunk LEDs on the board's front panel. The LEDs remain briefly in an alarm condition 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. |
|
3 |
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. |
|
4 |
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 with 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.
Use the nms303tool and aim303 programs to test the integration.
To use the nms303tool demonstration program:
|
Step |
Action |
|
1 |
Compile the program from the source code provided with the NMS DLCP software. |
|
2 |
Start nms303tool. |
|
3 |
Start the aim303 utility (the AIM 303 task must be running). |
|
4 |
Enter commands as needed from the nms303tool or aim303 command line. |
Refer to Using the demonstration programs for more information about running nms303tool.
To use the aim303 utility:
|
Step |
Action |
|
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 GR303 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.
After you start the nms303tool and aim303 programs, you can enter the commands at the command line of either program to perform operations on GR303 interfaces. These programs allow you to perform a variety of tasks, such as executing NMS GR303 or Aztek GR303 library functions, configuring and tracking task tracing information, verifying system status integration, and displaying status information about NMS GR303 interfaces.
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 by creating a new application using functions from the NMS GR303 library.
Depending on the GR303 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 GR303 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 Developing GR303 applications.