Introduction

Migration from AG to QX Boards

Migration From Earlier QX Software

OAM Service vs. qxload

Configuration File Changes

Keyword Changes

Introduction

This chapter describes:

• Migration from AG to QX boards

• Migration from earlier versions of QX software

Migration from AG to QX Boards

When you want to use a program written for AG boards with QX boards, the following modifications must be made in your source code:

1. Change the name of the device manager by replacing the string ADIMGR with QDIMGR in all your source code. This must be done when calling the functions ctaInitialize and ctaOpenServices.

2. Change the name of the switching library by replacing the string agsw with qxsw in your source code. This must be done when calling swiOpenSwitch.

3. Load the country specific parameters file to avoid telephony issues due to different default settings for call control parameters (use the ctdaemon program or the CT Access function ctaLoadParameterFile).

Migration From Earlier QX Software

With the 2000-1 release of Natural Access, some major changes were made in the configuration and monitoring aspects of QX software:

• Introduction of the OAM service

• Configuration file changes

• Keyword changes

OAM Service vs. qxload

Natural Access 2000-1 introduces the CT Access OAM service. This service performs configuration, monitoring, and testing functions across your telephony resources, including your QX boards.

The OAM service manages a central database of configuration information. Every board in the system has a record in the database, describing its configuration. The OAM service can start (boot) boards based on the information in the database.

The OAM service can be controlled programmatically, using its API. It can also be controlled using various utilities. One of these utilities, oamsys, effectively takes the place of qxload's configuration and booting function: it takes a configuration file, loads into the OAM database, and then starts the boards. Another utility, oammon, takes the place of qxload's monitoring function: after running oamsys, you can run oammon to monitor for board errors and other board-level events. For information about using these utilities to configure your QX system, see Chapter 3. For more general information on the OAM service and related utilities, refer to the OAM System User's Manual.

Configuration File Changes

qxload took a single configuration file, qx.cfg, containing configuration information for each board. Each board was referenced using a board number. oamsys takes a system configuration file, which assigns each board:

• A board name, used to refer to the board in software

• A board number, used to refer to the board in legacy software

• A board keyword file, containing the configuration information for the board.

The internal structure of the system configuration file and board keyword files is very different from qxload configuration files. For details on creating a file for your system, see see Chapter 3. For more general information on OAM configuration files, refer to the OAM System User's Manual.

Keyword Changes

The statements used in configuration files have also changed. Most configuration statements are specified in the board keyword file. They are expressed in keyword name/value pairs (for example, Xlaw = MU-LAW). Keywords have type definitions; for example, some keywords can take integer values, whereas others take string values. Some keywords represent arrays of values, or structures of other keywords or arrays.

The following table lists qx.cfg keywords and OAM keyword equivalents. For details on QX-specific keywords and values, refer to Chapter 8. For more general information on OAM keywords, refer to the OAM System User's Manual.

qx.cfg File Keyword	OAM Keyword
Board	Number
ClockRef	Clocking.MVIP.ClockRef for QX 2000/80-4L Clocking.HBus.ClockMode and Clocking.HBus.ClockSource for QX 2000/100-4L
DeviceID	Eeprom.Family
DSP_OS	DSP.C5x[x].Image
EnableMVIP	No longer used
FPGA	FPGA.ConfigFile
IdleCode	Xlaw
Interrupt	No longer used
PCIbus	Location.PCI.Bus
PCIslot	Location.PCI.Slot
QSLAC	NetworkInterface.Analog.ConfigFile[0]
QSLAC_A	NetworkInterface.Analog.ConfigFile[1]
QSLAC_B	NetworkInterface.Analog.ConfigFile[2]
QSLAC_C	NetworkInterface.Analog.ConfigFile[3]
SerialNumber	Eeprom.SerialNum