1.1 Manual Overview

1.2 QX 2000 Boards

1.3 Software Components

1.3.1 CT Access

1.3.2 OAM

1.3.3 QX Board Plug-In

1.3.4 Configuration Files

1.3.5 Trunk Control DLLs

1.3.6 QSLAC Files

1.3.7 FPGA Files

1.3.8 DSP Operating System File

1.1 Manual Overview

The QX 2000 Installation and Developer's Manual explains how to configure and install a QX 2000 board, and how to connect it to the telephone network and the MVIP bus.

This manual is targeted to developers of telephony and voice applications who are using the QX 2000 board with CT Access. This document defines telephony terms where applicable, but assumes that the reader is familiar with telephony concepts and switching. It also assumes that the user is familiar with the C programming language.

1.2 QX 2000 Boards

The QX 2000 boards provide four analog telephone ports which can receive incoming calls, place outgoing calls, transfer calls to local phones, and switch calls to other telephony boards.

The QX 2000 resides in a single PCI bus slot and contains an enhanced compliant MVIP interface. Up to eight QX 2000 boards may reside in a single PC chassis.

There are two QX 2000 variants:

QX 2000 Board	Line Interfaces	Processing Capabilities	Telephony Bus
QX 2000/100-4L	4 loop start interfaces	4 ports voice and call processing	H.100 Bus
QX 2000/80-4L	4 loop start interfaces	4 ports voice and call processing	MVIP-90 Bus

The main features of the QX 2000 board are:

• DSP resources
  The QX 2000 board includes a high-performance digital signal processor (DSP) which provides resources for four ports of call and voice processing. The DSP processor supports tasks for voice recording and playback, DTMF detection and generation, and call progress analysis. DSP resource management is transparent to the application. The QX 2000 driver allocates appropriate processing resources as needed.

• PCI bus connectivity
  Each board is designed to reside in a single PCI bus slot.

• Telephone line connectivity
  Each board connects to four analog loop start telephone interfaces.

• Telephony bus connectivity
  The QX 2000/100-4L board provides full support of the H.100 bus specification. The QX 2000/80-4L has an enhanced compliant MVIP interface.

• Telephony bus switching
  The switching for the QX 2000/100-4L board is implemented with the HMIC (H.100/MVIP Integrated Circuit). The HMIC is a single chip that offers full support for the H.100 bus within the MVIP architecture providing access to all 4096 timeslots on the H.100 bus. On the QX 2000/100-4L board, switch connections are allowed for up to 1024 local timeslots and up to 128 full duplex connections to the H.100 bus.
  The switching for the QX 2000/80-4L board is implemented with an FMIC (Flexible MVIP Integrated Circuit). The FMIC is a single chip that provides access to all 512 timeslots on the MVIP-90 bus.

• Audio interface
  Two stereo jacks provide audio input and audio output. The audio interface is compatible with the line input/output interface of a typical sound card. The audio interface can be used to record voice prompts or to monitor a line interface.

• Local phone interface
  The QX 2000 board includes a jack for connecting a local telephone interface. The board provides the current to power the phone. The local phone interface can be used to monitor a line interface.
  .
  
  Figure 1. QX 2000/100-4L Board Components
  Note: Currently, the E&M power supply connector and indicator on the QX 2000/100-4L end bracket are not used.
  
  Figure 2. QX 2000/80-4L Board Components

1.3 Software Components

QX 2000 boards require the following software components:

• The CT Access development environment, which provides services (APIs) for call control, system configuration, voice store and forward, and other functions.

• NMS Operations, Administration, and Monitoring (OAM) software, which performs operations on, administration of, and maintenance of telephony resources in a system. OAM manages a database of configuration information for each telephony resource, including QX 2000 boards.

• The QX board OAM plug-in, included with the OAM software. OAM communicates with QX boards through this software module.

• Configuration files, which describe how each board is set up and initialized. These files are used to initialize the OAM database for the boards.

• One or more trunk control dynamic link libraries (DLLs), that allow your application to communicate with the telephone network using the signaling schemes (protocols) used on the line.

• Quad Subscriber Line Audio Circuit (QSLAC) files, which are downloaded at installation time to configure the audio circuits to comply with country- specific line parameters.

• Field Programmable Gate Array (FPGA) files, which are downloaded at installation time to program the internal logic.

• DSP files, which are downloaded at boot time and contain the DSP software.

Figure 3 illustrates how these software components relate to one another. Each component is described in detail in the following sections.

Figure 3. Software Components for a QX 2000 System

1.3.1 CT Access

CT Access is a complete software development environment for voice applications. It provides a standard set of voice 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.

1.3.2 OAM

NMS Operations, Administration, and Maintenance (OAM) is an extension to CT Access which performs operations on, administration of, and maintenance of resources in a system. These resources include hardware components (including QX 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. This information consists of parameters and values. (See Figure 4.)

Figure 4. OAM Components

Each parameter and value is expressed as a keyword name/value pair (for example, Xlaw = MU-LAW). You can query the OAM database for keyword values for any component. Keywords and values can be added, modified or deleted.

To use OAM or any related utility, ensure 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.

1.3.3 QX Board Plug-In

The QX board plug-in software module is used by OAM to communicate with QX boards. The name of the QX plug-in is qx2kpi.bpi. This file is included with the QX software. It is installed in the \nms\bin directory by default. The file must reside in this directory in order for OAM to load it when it starts up.

1.3.4 Configuration Files

When you set up your system, you create a record in the OAM database for each of your boards, containing configuration information for the board. To do so, supply the information in configuration files, and run the oamsys utility. This utility creates the records, and then directs the OAM service to start the boards, configured as specified.

A set of sample configuration files is shipped with the software. Refer to Chapter 3 for more information about configuration files and oamsys.

1.3.5 Trunk Control DLLs

QX 2000 boards are compatible with a variety of signaling schemes called protocols. The trunk control DLL performs all of the signaling tasks to interface with the protocol used on the telephone line.

Several different protocol standards are in use throughout the world. These standards differ considerably from country to country. For these reasons, different DLLs are supplied with Natural Access for various protocols and country-specific variations. More than one DLL can be loaded at a time for applications that support multiple protocols simultaneously.

1.3.6 QSLAC Files

The QX 2000 board uses Quad Subscriber Line Audio Circuits (QSLACs) which are software-configurable to comply with country-specific line parameters. A QSLAC is programmed by a downloadable file. The QSLAC files are specified by the QX 2000 installation program and are downloaded to the QX 2000 board during board initialization.

1.3.7 FPGA Files

QX 2000 boards use Field Programmable Gate Array (FPGA) circuits. The internal logic of an FPGA is programmed by downloadable files. The files are specified by the QX 2000 installation program and are downloaded to the QX 2000 board during board initialization.

1.3.8 DSP Operating System File

DSP files are loaded to the board to specify the DSP operating system and DSP functions to use on the board. The following table lists the DSP operating system file for each board model:

Board Model	DSP Operating System File
QX 2000/80-4L	qx80.dsp
QX 2000/100-4L	qx100.dsp

Currently, all functions are contained in the operating system file and are not available as overlay files.