TUP service users

NMS TUP supports applications with service access points, or SAPs. One user service access point is defined for each application that uses the TUP service. At initialization, applications bind to a particular user SAP by specifying the SAP ID. Each user service access point in the TUP configuration file is associated with a switch type (ITU-T or CHINA) that the TUP task uses to associate with its configured network connections. A single user SAP, and hence a single application, for a particular switch type can be defined for outgoing call requests. If an application supports multiple TX boards, it must bind with each board separately.

The TUP task must bind with the MTP task through the use of network service access points (NSAP). The MTP configuration must define the network service access points (only ITU-T switch type) with which TUP can bind to communicate with the MTP task. The TUP configuration file must specify the MTP network service access point to which to bind to communicate with the MTP task. An ANSI TUP does not exist.

Note: The characteristics of each service access point are specified in the TUP configuration file. Refer to the NMS SS7 Configuration Manual for more information.