Overview
From an end-user point of view, transaction capabilities are above the network layer of the OSI seven layer reference model. The provision of network layer services to end-users requires communication between TCAP-users at various network nodes; these intra-network communications may in turn be modeled using the OSI Model.
As illustrated in Structure of TCAP Classes , the TCAP is structured in two interfaces for the TCAP components and TCAP dialogs.
Figure 6-1 Structure of TCAP Classes
This chapter describes the two main classes, TCAP_Component and TCAP_Dialogue, their subclasses, and the methods of each.
Important! SKTAL C++ interface is defined under namespace sktal.
Class TCAP_Invoke : public TCAP_Component
Class TCAP_Result : public TCAP_Component
Class TCAP_Error : public TCAP_Component
Class TCAP_Reject : public TCAP_Component
Class TCAP_Cancel : public TCAP_Component
Class TCAP_ResetTimer : public TCAP_Component
TCAP_Unidirectional : public TCAP_Dialogue class
Class TCAP_Begin : public TCAP_Dialogue
Class TCAP_Continue : public TCAP_Dialogue
Class TCAP_End: public TCAP_Dialogue