Configuration

TUP management consists of the following types of configuration functions:

Function type

Description

Init

Fills the configuration structure.

Set

Sends a configuration to the board.

Get

Retrieves the configuration from the board.


Refer to the TUP management function reference section for information about the function calls and the default and possible values for configuration elements.

General configuration

The general configuration must be done before any other configurations. Parameters set up in the general configuration include the number of service access points, the maximum number of circuits and groups allowed, and alarm level. A call to TUPInitGenCfg fills in all of the appropriate elements with default values for the application in a TUPGenCfg structure. A call to TUPSetGenCfg then sends the configuration to the board. TUPGetGenCfg retrieves this configuration from the board.

USAP and NSAP configuration

After the general configuration, configure the service access points above and below the TUP task on the board. Calls to TUPInitUSapCfg and TUPInitNSapCfg fill in the fields in the appropriate structures with default values for the application, which then can call TUPSetUSapCfg and TUPSetNSapCfg to send the configurations to the board. These configurations must  not be changed after initialization of the task. The fields in the user service access point section define switch type (either ITU-T or the China variant) and the user queue congestion onset and abatement levels. The network service access point configuration also defines the MTP network service access point with which to bind this NSAP, as well as the point code. TUPGetUSapCfg and TUPGetNSapCfg retrieve these configurations from the board.

Circuits and groups configuration

After the general configuration and the service access point configurations, configure the circuits for the TUP task to manage. First, calls to TUPInitCircCfg fill in some of the fields with default values for the application. After filling in and adjusting the remaining fields, the application can call TUPSetCircCfg to send the configurations to the board. These configurations can be changed after initialization of the task. The most important fields in circuit and group configuration are:

The remaining circuit identification codes (CIC) are managed and used through the circuit index that correlates to the CIC. For example, if the CIC field is 10 and the first circuit index is 20 in a five circuit set, manage or make a call on CIC 13 by using circuit index 23 in the function calls. If the group ID field in the configuration request is non-zero, the circuit set is treated as a predefined group. TUPGetCircCfg retrieves this configuration from the board.

Use alternate originating point code for this circuit set when configuring the board to act as multiple originating point codes (OPCs). The OPC must be properly configured in MTP for the new TUP OPC to work. By default, configuration uses the TUP general configuration originating point code. For more information on configuring multiple OPCs, see the NMS SS7 Configuration Manual.

Note: TUP supports pre-defined groups that allow applications to send actions to well-known sets of circuits. Confirm that the carrier in which the application will be installed supports pre-defined groups. Otherwise, the application needs to use dynamic groups only.