You are here: CSP API Reference > 1 EXS & SwitchKit API Messages > SS7 SCCP/TCAP Configure 0x0077

SS7 SCCP/TCAP Configure 0x0077

SwitchKit Name

SS7SCCPTCAPConfig

Type

EXS API and SwitchKit API message

Description

SS7 SCCP/TCAP Configure 0x0077

This message is sent to configure options for SS7 SCCP/TCAP.

For SwitchKit

Those options include:

• Local SSN

• Adjacent Translator

• Other Concerned Point Code

• SCCP Default Parameter Table

• SSN Default Parameter Table

• Network DPC/SSN

• SCCP/TCAP host configuration

In a SwitchKit environment, this message must be sent by an application or by SwitchManager with ConfigType = 1, Data = [2:1] specifying "SCCP route message to TCAP". Without sending this message first and receiving a positive acknowledgment it is impossible to add or specify a node as a TCAP node.

Sent by

Host (SwitchManager for SwitchKit)

Overview of message

The following table provides an overview of this message. The table following it provides the detail for each byte.

MESSAGE (White) | RESPONSE (Gray)
Byte | Field Description | Byte | Field Description
0 | Frame (0xFE) | 0 | Frame (0xFE)
1, 2 | Length (0xNNNN) | 1, 2 | Length (0x0007)
3, 4 | Message Type (0x0077) | 3, 4 | Message Type (0x0077)
5 | Reserved (0x00) | 5 | Reserved (0x00)
6 | Sequence Number | 6 | Same Sequence Number
7 | Logical Node ID | 7 | Logical Node ID
8 : | AIB Address Method | 8, 9 | Status MSB, LSB
Number of AEs to follow | 10 | Checksum
AEs |
9 | Config Type
10 | Number of TLVs
11 | TLVs
: | Data[0]
: | :
: | Checksum

Configuration

SS7SCCPTCAPConfig (

Node = integer,

StackID = integer,

ConfigType = integer,

Data = byte array);

C Structure

typedef struct {

UBYTE StackID;

UBYTE ConfigType;

UBYTE Data[222];

} XL_SS7SCCPTCAPConfig;

C++ Class

class XLC_SS7SCCPTCAPConfig : public XLC_OutboundMessage {

public:

UBYTE getStackID() const;

void setStackID(UBYTE x);

UBYTE getConfigType() const;

void setConfigType(UBYTE x);

const UBYTE *getData() const;

UBYTE *getData();

void setData(UBYTE *x);

};

EXS API Hex Format - Detailed

MESSAGE (White) | RESPONSE (Gray)
Byte | Field Description | Byte | Field Description
0 | Frame (0xFE) | 0 | Frame (0xFE)
1, 2 | Length (0xNNNN) | 1, 2 | Length (0x0007)
3, 4 | Message Type (0x0077) | 3, 4 | Message Type (0x0077)
5 | Reserved (0x00) | 5 | Reserved (0x00)
6 | Sequence Number | 6 | Same Sequence Number
7 | Logical Node ID | 7 | Logical Node ID
8 : | AIB Address Method 0x00 - Individual AEs | 8, 9 | Status MSB - 0x55 LSB - As follows: 01 - Invalid CFG Type 02 - Subsystem Configured 03 - Subsystem Not Configured 04 - Subsystem Allowed 05 - Subsystem Not Allowed 06 - Invalid Option 07 - Exceed Max SSN Host 08 - Invalid Parameter 09 - Invalid Parameter Length 0A - Parameter Configured 0B - Parameter Not Configured 0C - Invalid SCCP Upper Layer 0D - Exceed Max Active Subsystem 0E - DPC Not Configured 0F - Exceed Max Replicates 10 - Invalid Number of Replicates 11 - Replicate Not Configured 12 - Exceed Max Active SSN 13 - Exceed Max SSN PPC 14 - ESSG Subsystem Not Configured 15 - ESSG SSN PPC Exist 16 - OPR Not Perm for ESSG SSN DPC SSN 17 - Local Host Not Allowed 19 - Invalid Tag Type 1A - SCCP not configured for this stack 1B - GTAI length is out of the range configured for the group 1D - GT Group hasn’t been configured 1E - GT Group ID is already occupied 1F - GT Group with the same stack ID and selector already exists 20 - Group ID exceed maximum group ID 21 - The group parameters are not matched with parameters stored in the CSP. 22 - The minimum/maximum digits number in GT group is illegal. 23 - GT Entry already in Pending DEL state 24 - GT already exists in the group. 25 - GT does not exist. 26 - The memory storing translation result with global title has been used up. 27 - GT Entries have been used up. 28 - GT Entry is found in standby index table. 29 - GT Entry is found in active index table. 2A - GT Group is configured but not for this stack. 2B - Configuration is unreasonable. 1. Translation result is route on GT but DPC is equal to OPC. 2C - CPU load is not suitable to configuration. 2D - Index table needs to be built.
Number of AEs to follow | 10 | Checksum
AE 0x08 SS7 Stack |
: | Config Type 0x01 Local SSN 0x02 Adjacent Translator 0x03 Other Concerned Point Code 0x04 SCCP Default Parameter Table 0x05 SSN Default Parameter Table 0x07 Network DPC/SSN 0x08 SCCP/TCAP host configuration 0x09 SCCP Replicated SSN 0x0C TLV Format Configuration Contents
: | Number of TLVs
: | TLVs The Play File Start (0x011B) supports the following new TLV. 0x09CB Delete Global Title Group 0x09CC Add Global Title Entry 0x09CD Delete Global Title Entry 0x09CE Build Index Table Refer to Chapter 4, Tag Length Blocks in the API Reference. See also, Global Title Translation (GTT) Configuration Samples in the Developer’s Guide: Common Channel Signaling.
: | Data[0] The Data is dependent on the Config Type field (0x01 - 0x09) 0x01 Local SSN Data[0] Subsystem Number Data[1] Option 0x01 Add SSN 0x02 Delete SSN 0x03 Modify SSN Data[2] Routing Flag Bit 0 - Specify the direct upper layer of the SCCP (TCAP or host application.) 0 - SCCP Route network message directly to host 1 - SCCP Route network message to TCAP Bits 1 and 3-7 - Reserved for SASSI and ESSG use. Not used in current release. Default is 0. Bit 2 - Specify whether local GTT function is allowed to use when the message is originated from this SSN. (See note below.) 0 - Disable GTT when message is originated from the local SSN. 1 - Enable GTT when message is originated from the local SSN. Data[3] Reserved Note: Bit 2 only enables/disables GTT when the message is originated from the local SSN. When a message is received from the network and it needs GTT, the GTT function is always triggered. This bit provides backward compatibility to those host applications that do not support GTT.
| 0x02 Adjacent Translator Data[0] Subsystem Number Data[1] Option 0x01 Add Adjacent Translator 0x02 Delete Adjacent Translator Data[2–5] Adjacent Translator 0x03 Other Concerned Point Code Data[0] Subsystem Number Data[1] Option 0x01 Add Other Concerned Point Code 0x02 Delete Other Concerned Point Code Data[2-5] Other Concerned Point Code 0x04 SCCP/TCAP Default Parameter Table Data[0] Option 0x01 Add/Modify SCCP/TCAP Default Parameter 0x02 Delete SCCP/TCAP Default Parameter Data[1-2] Parameter Type Data[3-4] Parameter Length Data[5+] Parameter Value 0x05 SSN Default Parameter Table Data[0] Subsystem Number Data[1] Option 0x01 Add/Modify SSN Default Parameter 0x02 Delete SSN Default Parameter Data[2-3] Parameter Type 0x0066 Default Calling Party Address 0x006A Default Quality of Service 0x0074 Default MTP dpc (used when DPC is not in CDPA) Data[4-5] Parameter Length Data[6+] Parameter Value
| 0x07 Network DPC/SSN Data[0] Local Subsystem Number Data[1] Option 0x01 Add Network DPC/SSN 0x02 Delete Network DPC/SSN Data[2-5] DPC Data[6] Remote SSN Number Use this configuration if a certain subsystem needs to talk to a network DPC/SSN directly (route on DPC/SSN). You do not need to configure this if route on global title. A network DPC/SSN could be a remote or local subsystem. 0x08 SCCP/TCAP host configuration Data[0] Subsystem Number Data[1] Option 0x01 Add a host 0x02 Delete a host Data[2] Local/Matrix host 0xFE Local host 0xFF Matrix host Data[3] Host Port ID (0-5) Port IDs 0-5 correspond to Ports 0x3142-0x3147. NOTE: Only one host can be configured for each stack/subsystem. The default host is the matrix primary host. Also, an SS7 card supports only one port: 0x3142. Note however that it is possible to have an additional direct connection between the second host and the TCAP on the SS7 card using the CCS I/0 card.
| 0x09 SS7 SCAP CFG Replicated SSN Data[0] Subsystem Number Data[1] Option 0x01 Add Replicated SSN 0x02 Delete Replicated SSN Data[2] Number of Replicates Data[3-6] DPC Data[7] Subsystem Number Data[8...] Next DPC and Subsystem Number 0x0C TLV Format Configuration Contents 0x09CB Delete Global Title Group 0x09CC Add Global Title Entry 0x09CD Delete Global Title Entry 0x09CE Build Index Table
: | Checksum

See Signaling System Number Seven.
See Transaction Capability Application Part.
A number that addresses a node in a SS7 network.
Destination Point Code
A computer, attached to the Excel platform through an RS-232 or Ethernet link, from which you run the telecommunications application that controls the Excel platform.
A group of data bits in a specific format, with a flag at each end to indicate the beginning and the end of the frame.
See Address Information Block.
Most Significant Bit
Least Significant Bit
Tag-Length-Value block. A standardized block that allows data to inserted in a standard way into API messages.
CCS. Network architecture using SS7 protocol for the exchange of information between telecommunications nodes and networks on an out-of-band basis.
Message delimiter (SS7 bit pattern - 01111110)
See Message Transfer Part.
The point in the Excel platform where a DS0 connects to a network. Also known as a "socket."
See Common Channel Signaling.