# NMS ISDN software components

ISDN is implemented differently around the world. For this reason, NMS provides versions of its ISDN software for different regions. Each package for a variant contains the software modules needed to allow a board to communicate on a T1, E1, or BRI trunk in one or more countries using that variant.

The NMS ISDN software package for a given region contains the following components that are briefly described in this topic:

- A readme file.

- NMS ISDN function libraries.

- Header files.

- Run modules containing the NMS ISDN protocol stack software and the NMS ISDN management software.

- Board keyword files.

- Demonstration programs and utilities, with their source code files and makefiles.

Other components, also included, are used only when the NMS ISDN protocol stack is running in channelized stack mode.

The channelized stack mode-specific components are:

- A trunk control program (TCP).

- Parameter files (.pf files) containing the complete set of NMS ISDN parameters. Some parameters in these files are set to values specific to a certain country or region.

- An nccxisdn.par file containing the subset of NMS ISDN parameters that can be changed, if desired. Two country-specific parameter files, nccxadi cty.par and nccstart cty.par, contain parameters that should not be changed. These files are used when the protocol stack is in channelized configuration, using the NCC service.

For more information about the channelized stack mode, see the NMS ISDN for Natural Call Control Developer's Manual.

## Readme file

The ASCII text file readme_isdn.txt contains release information that does not appear in other documentation. Consult this file to learn where the NMS ISDN software components are located after installation.

## NMS ISDN function libraries

NMS ISDN function libraries run on the host computer. The application uses them to interact with ISDN protocol stacks running on a board and to communicate with the NCC service. These are dynamic-link libraries (DLL) under Windows, and are shared objects under UNIX. The libraries have different names under different operating systems:

Operating system | Natural Access library name(s)
--- | ---
Windows | isdnapi.lib, isdnapi.dll, nccisdn.lib, nccisdn.lib, imgtapi.lib, imgtapi.dll Note: nccisdn.lib, nccisdn.lib, imgtapi.lib,and imgtapi.dll are not in use for layer 3.
UNIX | libisdnapi.so, libnccisdn.so, libimgtapi.so Note: libnccisdn.so and libimgtapi.so are not in use for layer 3.

Standard NMS ISDN header files, required by your applications to communicate with the ISDN protocol stack on the board, are also supplied.

The following illustration describes the include file structure used by an application using NMS ISDN in the ACU configuration:

The following illustration describes the include file structure used by an application using NMS ISDN in the LAPD configuration:

## Run modules

A run module contains the basic low-level software that a board requires to support ISDN. The module is transferred from the host into on-board memory when the board boots.

Different run modules are supplied for different configurations and are specific to the protocol variant and country. The module you use depends upon what board type you are using. For more information about run modules, see the NMS ISDN Installation Manual.

## Board keyword files

Board keyword files contain information that determines how to set up your boards for use. These files also contain country-specific information, and define what trunks are assigned to which D channels.

Several example files are included, describing ISDN configurations for different boards. Use these files to create a file describing your hardware and software setup. For details, see the NMS OAM System User's Manual.

## Demonstration programs and utilities

The following demonstration programs and utilities are included, with their source code files and makefiles:

Program | Description
--- | ---
isdndemo | Communicates with the ISDN stack in the ACU configuration and performs call control.
lapddemo | Illustrates establishing a LAPD data link on an ISDN trunk.
dectrace | Decodes and displays messages sent or received by the NMS ISDN protocol stack that were previously captured in a log file by the oammon utility.
itrace | Acts as a runtime filter for NMS ISDN messages from the stack being captured by the oammon utility.