SS7 TCAP Developer's Manual
P/N 6469-13
(Page 1 of 1 in this chapter)
About This Manual
Developer Support
1 Introduction
- 1.1 SS7 Architecture
- 1.2 TCAP Layer Services
2 SS7 TCAP API Description
- 2.1 TCAP API Concepts and Terminology
- 2.1.1 TCAP Service Users and Service Access Points
- 2.1.2 Entity and Instance IDs
- 2.1.3 Dialog IDs
- 2.1.4 SCCP Addresses
- 2.1.5 SCCP Quality of Service (QOS)
- 2.1.6 ANSI Transaction Types
- 2.1.7 ITU-T Transaction Types
- 2.1.8 TCAP Components
- 2.1.9 Message Lengths and Segmentation
- 2.2 Asynchronous Communication Model
- 2.2.1 Transaction Requests
- 2.2.2 Receiving Incoming Transactions and Status Indications
- 2.2.3 UnixWare and Solaris Systems
- 2.2.4 Windows NT
- 2.2.5 Multi-threading Considerations
- 2.3 TCAP API Procedures
- 2.3.1 Initialization/Binding
- 2.3.2 Transaction Requests
- 2.3.3 Simple Request/Response Transaction
- 2.3.4 Conversational/Linked Transaction
- 2.3.5 Handling Abnormal Conditions
- 2.3.6 Invalid Transaction Portions
- 2.3.7 Stranded Transactions
- 2.3.8 Invalid Component in a Begin/Query Message
- 2.3.9 Invalid Component in a Continue/Conversation Message
- 2.3.10 Invalid Component in an End/Response Message
- 2.3.11 Invoke Time-outs (ITU_T only)
- 2.3.12 Invalid Component in a Multiple Component Message
- 2.3.13 Status and Notify Indications
- 2.3.14 Signaling Point and Subsystem Status Procedures
- 2.3.15 Coordinated State Change
- 2.3.16 Subsystem State Changes
- 2.3.17 Remote Signaling Point Failures
- 2.4 TCAP Management API
- 2.4.1 TCAP Configuration Primitives
- 2.4.2 Control Requests
- 2.4.3 Statistics Request
- 2.5 Unsolicited Alarms
3 Data Structures
- 3.1 Data Types
- 3.1.1 Primitive Data Types
- 3.1.2 Point Codes
- 3.1.3 TCAP Octet Strings
- 3.1.4 TCAP Component IDs
- 3.1.5 Global Titles
- 3.2 Common Data Structures
- 3.2.1 SCCP Address Structure
- 3.2.2 Default Point Code
- 3.2.3 ITU-T with 24-bit Point Code
- 3.2.4 Global Title Use
- 3.2.5 SCCP Quality of Service (QOS) Structure
- 3.2.6 TCAP Transaction Information Structure
- 3.2.7 TCAP Dialog Section Structure
- 3.3 Component Data Structures
- 3.3.1 ANSI Component Structure
- 3.3.2 ITU-T Component Structure
- 3.4 Incoming Message Event Structures
- 3.4.1 General Receive Information Block Structure
- 3.4.2 TCAP Coord Event Structure
- 3.4.3 Signaling Point Status Event Structure
- 3.4.4 Subsystem Status Event Structure
- 3.4.5 TCAP Notification Event Structure
- 3.4.6 TCAP Status Event Structure
- 3.4.7 TCAP Transaction Data Event Structure
4 TCAP Transaction API Reference
- 4.1 Files
- TCAPAddComp
- TCAPBindReq
- TCAPCoordReq
- TCAPCoordResp
- TCAPGetComp
- TCAPInitAPI
- TCAPInitTrans
- TCAPRetrieveMessage
- TCAPStateReq
- TCAPSyncObj
- TCAPTermAPI
- TCAPTransRqst
- TCAPUnbindReq
5 TCAP Management API
- 5.1 Files
- TCAPAlarmControl
- TCAPGenCfg
- TCAPGetGenCfg
- TCAPGetSapCfg
- TCAPInitGenCfg
- TCAPInitMgmtAPI
- TCAPInitSapCfg
- TCAPSapCfg
- TCAPSapStats
- TCAPTermMgmtAPI
- TCAPTraceControl
6 TCAP Sample Applications
- 6.1 The FIND800 Sample Application
- 6.1.1 Acting as a 800 number server
- 6.1.2 Acting as an 800 number client
- 6.1.3 Troubleshooting
- 6.1.4 Using TCAP ITU-T Protocol
- 6.1.5 Adding Subsystem Numbers
- 6.2 The TCAPCFG Sample Utility
- 6.3 The TCAPMGR Sample Utility
(Page 1 of 1 in this chapter)
tech_support@nmss.com
Copyright © 1999, Natural MicroSystems, Inc. All rights
reserved.