1.1 Overview

1.2 Introduction

1.3 CG 6000C Board Features

1.3.1 Universal Ports

1.4 Software Requirements

1.4.1 OAM

CG Board Plug-In

1.4.2 OAM Configuration Files

1.4.3 Runtime Software

1.4.4 Trunk Control Programs (TCPs)

1.4.5 CT Access

1.5 NMS Fusion and the CG 6000C Board

1.1 Overview

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 an application that uses this board

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

1.2 Introduction

This chapter describes:

• The CG 6000C board and its capabilities

• The software components you need to build an application using a
  CG 6000C board

1.3 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.5, NMS Fusion and the CG 6000C Board.

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 in 16 Texas Instruments DSPs). Each DSP core executes 100 MIPS and contains 100K words of SRAM. This provides board resources for 120 universal IP gateway ports. For more information about universal ports, refer to Section 1.3.1, Universal Ports.

• CPCI 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 supports two 10/100Base-T Ethernet connections, through a rear transition board, for Fast Ethernet connectivity. For more information, refer to Section 2.5, Trunk Connections 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, dip switches may 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.3.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:

• 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. 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

The application 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.4 Software Requirements

CG 6000C boards require the following software components:

• NMS OAM (Operations, Administration, and Maintenance) extension to CT Access which configures, administers, and maintains telephony resources in a system.

• Configuration files which 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.

• CT Access development environment which provides services (APIs) for 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.4.1 OAM

NMS Operations, Administration, and Maintenance (OAM) is an extension to CT Access which performs operations on, administration of, and maintenance of 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 the configuration of a component

• Start (boot), stop (shut down), and test a component

• Receive notifications from components

OAM 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. OAM Components

Each OAM database parameter and value is expressed as a keyword name/value pair (for example, Clocking.HBus.ClockMode). You can query the OAM database for keyword values in any component. Keywords and values can be added, modified or deleted.

Note: Before using OAM or any of its related utilities, make sure that ctdaemon is running. For more information about ctdaemon, refer to the CT Access Developer's Reference Manual. For general information about OAM and its utilities, refer to the OAM System User's Manual.

CG Board Plug-In

The CG 6000C board plug-in module is used by OAM to communicate with CG boards. The name of the CG plug-in is cg6kpi.bpi. This file must reside in the nms\bin directory (or opt/nms/lib for Unix) in order for OAM to load it when it starts up.

1.4.2 OAM Configuration Files

OAM uses two types of configuration files: system configuration files and board keyword files.

An OAM system configuration file file contains:

• A list of boards in the system.

• For each board, the name of one or more board keyword files.

OAM board keyword files contain parameters and values needed to configure the board (see Figure 4). These settings are expressed as keyword name/value pairs.

Several sample keyword files are supplied with your hardware installation. Each of these files configures the board to use a different protocol (for example, wink start or off-premises station). You can reference these files in your system configuration file, or modify them if you wish.

Figure 4. OAM Configuration Files

When you run the oamsys utility, it creates OAM database records based on the contents of the specified system configuration file and board configuration files, and then directs the OAM service to start the boards, configured as specified.

Refer to Chapter 3 for more information about configuration files and oamsys.

1.4.3 Runtime Software

The runtime software consists of runfiles (also known as Downloadable Modules - 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 CT Access. You specify the files to use for your configuration in the board keyword file. When the OAM system boots a board, the runfile and DSP files are transferred from the host into on-board memory. Refer to Chapter 3 for more information about board keyword files.

Note: NMS recommends that you run the program burnall after completing the CG 6000C software installation process. This program updates the flash memory on all CG 6000C boards in the chassis. If you do not run this program, the board may return a notification message at boot time about incompatible firmware in the flash, and recommending that you update the CG 6000C flash memory with a new core file.

1.4.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 specify TCPs in the configuration file and they are downloaded to the board by 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 CT Access, refer to the AG CAS for Natural Call Control Developer's Manual.

1.4.5 CT Access

CT 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 and optional CT Access services, refer to the CT Access Developer's Reference Manual. Figure 5 shows the CT Access software environment as it relates to OAM software and CG 6000C hardware.

Figure 5. CT Access Software Environment

1.5 NMS Fusion and the CG 6000C Board

Gateway applications provide a way of transferring data between telephone network and packet network interfaces. NMS Fusion consists of CG 600OC hardware and software for producing IP telephony gateway applications. For more information about Fusion and Fusion CG 6000C board configuration, refer to the Fusion Developer's Manual.

NMS Fusion 4.0 (or later) configurations use CG 6000C boards to receive and transmit data to PSTN and to IP networks. CT Access call control functions are used to place and receive PSTN calls. Use the MSPP (Media Stream Protocol Processing) service to create and configure media channels between PSTN and IP networks. For more information, refer to the Fusion MSPP Service Developer's Reference Manual.

Note: You must install the Fusion 4.0 CD-ROM to be able to use the Ethernet capability of the CG 6000C board.