1.1 Introduction

1.2 CG 6000C Board Features

1.2.1 Universal Ports

1.3 Software Requirements

1.3.1 NMS OAM

CG Board Plug-In

1.3.2 NMS OAM Configuration Files

1.3.3 Runtime Software

1.3.4 Trunk Control Programs (TCPs)

1.3.5 Natural Access

1.4 NMS Fusion and CG 6000C Boards

1.1 Introduction

The CG 6000C Installation and Developer's Manual explains how to:

• Install and configure a CG 6000C board

• Verify that the board has been installed correctly and is operating correctly

• Develop applications that use the board

This manual targets programmers and system integrators who develop IP telephony gateway applications. This manual defines telephony terms where applicable, but assumes that reader are familiar with basic telephony and Internet data communication concepts, switching, and the C programming language.

This chapter describes:

• The CG 6000C board and its capabilities

• The software components needed to build applications that use
  CG 6000C boards

1.2 CG 6000C Board Features

The CG 6000C board is an NMS CompactPCI board. It provides four T1 or E1 digital trunk interfaces and two Ethernet 10/100Base-T interfaces to support, for example, a 120 port voice to IP gateway. For more information about gateways, refer to Section 1.4, NMS Fusion and CG 6000C Boards.

Refer to the NMS web site (www.nmss.com) for a list of available
CG 6000C board configurations, a list of countries where NMS has obtained approval for the CG 6000C board, and product updates.

CG 6000C boards include the following features:

• DSP resources
  Each board has 32 high-performance digital signal processor (DSP) cores contained within 16 Texas Instruments DSPs. Each DSP core executes 100 MIPS and contains 100K words of SRAM. These DSP resources provide board resources for 120 universal IP gateway ports. For more information about universal ports, refer to Section 1.2.1, Universal Ports.

• Compact PCI bus connectivity
  Each CG 6000C board is designed to reside in a single CompactPCI bus slot. Each board contains a 5 volt CompactPCI bus interface compliant with the CompactPCI Specification PICMG 2.0 R2.1. The CompactPCI interface is a 33 MHz, 32-bit master/target device.

• Trunk connectivity
  Each board contains four T1 or E1 (75 Ohm or 120 Ohm) network interfaces for digital trunk connectivity through a rear transition board. You must configure the board for T1 or E1. For more information, refer to NetworkInterface.T1E1[x].Type and to Section 2.4, Installing the Hardware.

• H.110 bus connectivity
  The CG 6000C board fully supports the H.110 bus specification. The H.110 bus allows boards to share data with other boards on the H.110 bus. For example, you can connect two or more CG 6000C boards for applications that perform trunk-to-trunk switching. You can use H.110 compatible products from other manufacturers with the CG 6000C board.

• Telephony bus switching
  Switching for the CG 6000C board offers full support for the H.110 bus within the H.110 architecture. On the CG 6000C board, switch connections are allowed for a total of 256 full duplex connections between local devices and the H.110 bus. Switch connections between local devices are non-blocking.

• Ethernet connectivity
  The CG 6000C board includes two 10/100 Base-T Ethernet connections that provide Fast Ethernet connectivity through a rear transition board. For more information, refer to Section 2.5, Establishing Trunk and Ethernet Connections and Section 3.6, Configuring Ethernet Connections.

• SA 110 Processor
  The processor is a 233 MHz SA110 Intel StrongARM with 32 MB SDRAM.

Figure 1 shows where the major components are located on a CG 6000C board:

Figure 1. CG 6000C Board

Note: Depending on the board revision, the DIP switch can appear on the front or back of the board.

Figure 2 shows where the major components are located on the rear panel I/O transition board:

Figure 2. Rear Panel I/O Transition Board

1.2.1 Universal Ports

CG 6000C boards support up to 120 simultaneous full-duplex universal ports of voice/fax data. A universal port can use any combination of loaded functions, such as voice play, voice record, tone detection, and tone generation as well as fax transmit or fax receive functions. Applications can also switch between these functions within a single phone call.

If configured for NMS Fusion 4.0 (or later), each universal port supports the following functions:

• Up to three complex vocoders (algorithms that perform encoding and decoding for voice algorithms such as G.723.1 and G.729A) and a simple voice vocoder (G.711). All vocoders are loaded, but only one encoder/decoder pair can be active at any given time per channel.

• T.38 fax processing

• Call control processing

• Tone generation and detection

Applications can process either voice and fax data within the scope of a single call without being concerned with the availability of board resources needed to perform the processing activities.

For more information about universal ports, refer to Appendix B.

1.3 Software Requirements

CG 6000C boards require the following software components:

• NMS OAM (Operations, Administration, and Maintenance) software that configures, administers, and maintains telephony resources on the system.

• Configuration files that describe how the board is set up and initialized.

• Runtime software and drivers that control the CG 6000C board.

• One or more trunk control programs (TCPs) that allow applications to communicate with the telephone network using the signaling schemes (protocols) used on the trunk.

• Natural Access development environment that provides services for performing call control, system configuration, voice store and forward, and other functions.
  Note: If you want to run NMS Fusion with the CG 6000C board, refer to the Fusion Installation and Developer's Manual for more information.

1.3.1 NMS OAM

NMS Operations, Administration, and Maintenance (OAM) administers and maintains telephony resources in a system. These resources include hardware components (including CG boards), and low-level board management software modules (such as the Hot Swap process).

Using NMS OAM, you can:

• Create, delete, and query component configurations

• Start (boot), stop (shut down), and test components

• Receive notifications from components

The OAM service maintains a database containing records of configuration information for each component as shown in Figure 3. This information consists of parameters and values.

Figure 3. NMS OAM Components

Each NMS OAM database parameter and value is expressed as a keyword name/value pair (for example, Clocking.HBus.ClockMode). You can use NMS OAM to retrieve and modify configuration parameters.

Note: Before using the NMS OAM, make sure that the Natural Access server (ctdaemon) is running. For more information about the Natural Access server, refer to the Natural Access Developer's Reference Manual. For more information about NMS OAM, refer to the NMS OAM System User's Manual.

CG Board Plug-In

NMS OAM uses the CG 6000C board plug-in module to communicate with CG boards. The name of the CG plug-in is cg6kpi.bpi. In order for NMS OAM to load cg6kpi.bpi, the file must reside in the nms\bin directory (or opt/nms/lib for UNIX).

1.3.2 NMS OAM Configuration Files

NMS OAM uses two types of configuration files:

• System configuration files that contain a list of boards in the system and the name of one or more board keyword files for each board.

• Board keyword files that specify board configuration parameters (see Figure 4). Parameters are expressed as keyword name/value pairs.

CG 6000C software includes several sample board keyword files. Each file configures the board to use a different protocol (for example, Wink Start or Off-Premises Station). You can modify these files according to your system's requirements and reference them in the system configuration file.

Figure 4. NMS OAM Configuration Files

When you run the oamsys utility, it creates NMS OAM database records based on the contents of the specified system configuration file and board keyword files. It then directs NMS OAM to start the boards and configure them according to the specified parameters. Refer to Chapter 3 for more information about configuration files and oamsys.

1.3.3 Runtime Software

CG 6000C runtime software consists of runfiles (also known as Downloadable Modules or DLMs), a core file stored in non-volatile memory (flash memory), and DSP files. The runfile is the basic low-level software which a CG 6000C board requires to operate. DSP files enable a CG 6000C board's on-board DSPs to perform certain tasks, such as DTMF signaling, voice recording, and playback.

Several runfiles and DSP files are installed with Natural Access. You can specify which DSP files to use in each board's keyword file. When NMS OAM boots a board, it transfers the files into the board's on-board memory. Refer to Chapter 3 for more information about NMS OAM board keyword files.

Note: NMS recommends that you run the burnall script after installing the
CG 6000C board. burnall updates the flash memory on all CG 6000C boards in the chassis. If you do not run burnall, the board may return firmware incompatibility errors and recommend that you update the CG 6000C flash memory with a new core file. For more information about burnall, refer to Chapter 2.

1.3.4 Trunk Control Programs (TCPs)

CG 6000C boards are compatible with a variety of PSTN signaling schemes, called protocols. A Trunk Control Program (TCP) performs all of the signaling tasks to interface with the protocol used on a channel.

Several different protocol standards are in use throughout the world. These standards tend to differ considerably from country to country. For these reasons, different TCPs are supplied with Natural Access various protocols and
country-specific variations.

You can load more than one TCP at a time, for applications that support multiple protocols simultaneously. You can specify which TCPs to use in each board's keyword file, and the specified files are downloaded to the board by NMS OAM. TCPs run on the board, relieving the host computer from the task of processing the protocol directly. For more information about the TCPs shipped with Natural Access software, refer to the NMS CAS for Natural Call Control Developer's Manual.

1.3.5 Natural Access

Natural Access is a complete software development environment for voice applications. It provides a standard set of functions grouped into logical services. Each service has a standard programming interface. For more information about standard (base) and optional (domain) Natural Access services, refer to the Natural Access Developer's Reference Manual.

Figure 5. Natural Access Software Environment

1.4 NMS Fusion and CG 6000C Boards

Gateway applications provide a way of transferring data between telephone network and packet network interfaces. NMS Fusion provides software for developing IP telephony gateway applications that run on CG boards. For more information about Fusion software and Fusion CG 6000C board configurations, refer to the Fusion Developer's Manual.

Fusion 4.0 (or later) configurations use CG 6000C boards to receive and transmit data to PSTN and to IP networks. Fusion applications use NCC (Natural Call Control) service functions to place and receive PSTN calls, and MSPP (Media Stream Protocol Processing) service functions to create and configure media channels between PSTN and IP networks. For more information about MSPP service functions, refer to the Fusion MSPP Service Developer's Reference Manual.