This chapter:
ISDN is implemented differently around the world. For this reason, NMS provides several versions of its AG ISDN software for different regions. The package for a region contains the software modules you need to allow an AG board to communicate on a T1 or E1 trunk in one or more countries in that region.
The ISDN software package for a given region contains the following:
The sections that follow briefly describe each of these components.
Other components, also included, are only used when AG ISDN is running in its NCC configuration. For more information about these, see the AG ISDN for Natural Call Control Developer's Manual.
The NCC configuration-specific components are:
This file contains released information that does not appear in other documentation. The file is named readme.isd. Consult this file to learn where the AG ISDN software components are located after installation.
This component runs on the host PC. It is used by the application program to interact with the ISDN protocol stacks running on the AG board.
The AG ISDN library is supplied as an extension to the ADI library. It is a dynamic-link library (DLL) under OS/2 and Windows NT, and it is a shared object under UNIX. The library has different names under different operating systems:
|
Operating System |
AG Access Lib Name |
CT Access Lib Name |
|
Windows NT, OS/2 |
||
|
UNIX |
Standard AG ISDN header files are also supplied. These are required by your applications to communicate with the ISDN protocol stack on the board.
The following figure describes the include file structure used by an application using AG ISDN in its ACU configuration:
Figure 7: Header File Usage (ACU Configuration)
The following figure describes the include file structure used by an application using AG ISDN in its LAPD configuration:
Figure 8: Header File Usage (LAPD Configuration)
The runfile is the basic low-level software which an AG board requires to support ISDN. The runfile is transferred from the host into on-board memory by the agmon utility when the board boots.
Different runfiles are supplied for different configurations. The runfile you use depends upon what board type you are using. For more information about the ISDN protocol stack runfile, see the AG ISDN Installation Manual.
This file contains information which agmon reads to determine how to set up your boards for use. This file also contains country-specific information.
This file must be edited to describe your hardware and software setup. For details, see the AG ISDN Installation Manual.
Several demonstration programs are included, with their source code files and makefiles. One of them, isdndemo, is an example of a simple call control application that communicates with the ISDN stack in ACU configuration. For details, see Chapter 9.
In addition to the AG ISDN software, you will need the following components to build an ISDN protocol application:
To perform MVIP switching under AG Access, you will also need NMS switching control software: SwitchPathTM and/or the SW Utility. (This software is not needed with CT Access, since CT Access includes a Switching service - see section 2.3.1.)
Boards in the family of AG Quad products have up to four T1 or E1 trunk interfaces, and up to eight on-board DSPs which provide up to 120 ports of call processing and up to 60 ports of programmable voice processing. Each board occupies a PCI slot in the host computer.
AG Quad boards connect to other boards via the H.100 bus. The H.100 bus allows the boards to share data, signaling, and switching information with boards on the H.100 bus and the MVIP bus (see section 2.3.2). For example, you can connect two or more AG Quad boards for applications that perform trunk-to-trunk switching. You can add additional DSP resources, analog station interfaces, or loop start line interfaces using other AG boards. You can also use compatible products from other manufacturers with AG Quad boards.
For detailed information on AG Quad boards, see the AG Quad Installation and Developer's Manual.
AG-T1 and AG-E1 boards interface one T1 or E1 trunk with the host computer. The boards also have eight on-board DSPs. Each board occupies a standard ISA slot in the host computer.
The AG-T1 and AG-E1 can connect to other boards via the MVIP bus. The MVIP bus is an interoperable subset of the H.100 bus.
For detailed information on the AG-T1 and AG-E1 boards, see the AG-T1 and AG-E1 Installation and Developer's Manual.
Note: ISDN is only supported on AG-T1 and AG-E1 boards revision D-1 and later. If you are using AG-T1 or AG-E1 boards that were not provided with your AG ISDN package, check the revision number.
|
WARNING: |
Natural MicroSystems obtains board-level approvals certificates for supported countries. Some countries require that you obtain system-level approvals before connecting a system to the public network. To learn what approvals you require, contact the appropriate regulatory authority in the target country. |
CT Access is a complete development environment for telephony applications. It provides a standard set of telephony functions grouped into logical services, each of which has a standard API. CT Access provides functions for telephony-related tasks such as call control, tone and DTMF tone generation and detection, and voice playing and recording.
CT Access includes a service which controls switching on MVIP-compliant devices. You can use this service to make or break connections, send patterns, sample data, etc. This service supports both MVIP-95 and MVIP-90 specifications. Alternatively, you can use the swish standalone utility to control switching interactively or in a batch mode.
For general information about installing and using CT Access, see the CT Access documentation.
AG Access is a development environment for controlling telephony operations on AG boards. AG Access provides functions for call control, tone and DTMF tone generation and detection, voice playing and recording, and more.
AG Access provides an MVIP enhanced compliant switching driver. To control switching in AG Access applications, you can use the NMS SwitchPath library of switching functions (sold separately), or the SW Utility.
For general information about installing and using AG Access, see the AG Access documentation.
When you set up your system, you specify configuration information for all boards in the system in an AG configuration file. This information includes: whether a board performs MVIP switching, which board is the MVIP clock master, which software modules to transfer to the board's memory on startup, and other configuration information. To learn how to modify your AG configuration file to set up your AG ISDN software, see the AG ISDN Installation Manual and the AG Runtime Configuration and Developer's Manual
To configure your boards based on the information in the AG configuration file, run the agmon utility. agmon transfers to each board all software modules specified in the file, and performs any other configuration activities needed. It then monitors the boards for errors and other events.
Whenever you make a change to your AG configuration file, restart agmon to make your changes effective.
agmon is installed with CT Access and AG Access. For more information, see the AG Runtime Configuration and Developer's Manual.
DSP files enable the AG board's on-board digital signal processors to perform certain tasks, such as voice recording and playback, etc. DSP files are transferred from the host into on-board memory when agmon runs.
Several DSP files are installed with CT Access and AG Access. Refer to the ADI Service Function Reference Manual or AG Access Function Reference Manual for more general information about DSP files.
DSP files have the extension .dsp. You specify the files to use for your configuration in the AG configuration file. To learn how, see the AG ISDN Installation Manual.
To create an AG ISDN application:
|
Step |
Where Step Is Documented |
|
1. Install AG Quad T, AG Quad E, AG Dual T, AG Dual E, AG Quad Connect T, AG Quad Connect E, AG-T1, or AG-E1 boards in a system, and any other boards you will need in your application. |
The installation manuals for your AG boards |
|
2. Install CT Access or AG Access. |
CT Access Installation Manual, AG Access Installation Manual |
|
3. Install the AG ISDN software for each country or region that your application will be used in. |
AG ISDN Installation Manual |
|
4. Edit your AG configuration file so it describes all boards in your system. |
The AG ISDN Installation Manual, the installation manuals for your AG boards, and the AG Runtime Configuration and Developer's Manual |
|
5. Test your hardware installation. |
The installation manuals for your AG boards |
|
6. Write your application. |
This manual |
Natural MicroSystems, Inc.
100 Crossing Boulevard
Framingham, MA 01702
