Configuring SCCP TCAP

This section describes the SCCP TCAP options that can be configured for a variant of an ANSI or ITU protocol.

Before you can configure other options, you must add a local subsystem and configure how it routes network messages (either to TCAP or to the host). You must use the SS7 SCCP/TCAP Configure message to set the byte for Config Type to 0x01 Local SSN.

Important! When using SS7 PQ cards in either a single node or a multi-node CSP system you may configure a total of 3000 physical and virtual CICs, if both ISUP and SCCP/TCAP are to be configured for this system. It does not matter what combination there is of physical or virtual CICs since both require memory space on the card.

2 Configure MTP for the stack (link sets, links, routes) using the following messages:

3 Configure the local subsystem number using the SS7 SCCP/TCAP Configure message.

Option	Use the SS7 SCCP/TCAP Configure message to...
Adjacent Translator	Set the Config Type byte to 0x02 and configure all Adjacent Translators for a given subsystem. By default, all Adjacent Translators are Concerned Point Codes. See Adjacent Translators Configuration.
Other Concerned Point Code	Set the Config Type byte to 0x03. For an SSP or SCP, Point Codes which must be informed about local (Excel platform) subsystem status changes are referred to as Concerned Point Codes.
SCCP/TCAP Default Parameter Table	Set the Config Type byte to 0x04. This table contains the default parameters used by SCCP and TCAP for all subsystems associated with a stack. These values are used for Mandatory parameters if not included in a primitive. The following parameters are stored by default, according to the ITU white book. • TCAP Dialog_As_ID • TCAP Unidialog_As_ID • TCAP Protocol Version You do not need to configure this table unless you require modifications.
Subsystem (Based on default parameter table)	Configure the default parameter table for a particular sub-system. Set the Config Type byte to 0x05.
TCAP Object Syntax Descriptor (OSD)	Set the Config Type byte to 0x06. You can modify a TCAP object by indicating the TCAP object parameter ID, TCAP identifier, whether or not to update the object syntax and if updated, what the object syntax description is. See SCCP/TCAP Call Flows.
Configure Local SSN	Set the Config Type byte to 0x01. You may route messages to TCAP or the host by configuring the SSN Routing Flag.
Network DPC/SSN	Set the Config Type byte to 0x07 to configure the Destination Point Code (DPC) and remote subsystem number.
SCCP/TCAP host configuration	Set the Config Type byte to 0x08 to configure the SCCP/TCAP host that is used to receive messages from the SCCP/TCAP layer.
Global Title Translation	Set the Config Type byte to 0x0C to configure Global Title Translation using the TLV Format Configuration Contents. See Global Title Translation (GTT) Configuration Samples.

Option

Use the SS7 SCCP/TCAP Configure message to...

Adjacent Translator

Set the Config Type byte to 0x02 and configure all Adjacent Translators for a given subsystem. By default, all Adjacent Translators are Concerned Point Codes.

See Adjacent Translators Configuration.

Other Concerned Point Code

Set the Config Type byte to 0x03. For an SSP or SCP, Point Codes which must be informed about local (Excel platform) subsystem status changes are referred to as Concerned Point Codes.

SCCP/TCAP Default Parameter Table

Set the Config Type byte to 0x04. This table contains the default parameters used by SCCP and TCAP for all subsystems associated with a stack. These values are used for Mandatory parameters if not included in a primitive.

The following parameters are stored by default, according to the ITU white book.

• TCAP Dialog_As_ID

• TCAP Unidialog_As_ID

• TCAP Protocol Version

You do not need to configure this table unless you require modifications.

Subsystem
(Based on default parameter table)

Configure the default parameter table for a particular sub-system. Set the Config Type byte to 0x05.

TCAP Object Syntax Descriptor (OSD)

Set the Config Type byte to 0x06. You can modify a TCAP object by indicating the TCAP object parameter ID, TCAP identifier, whether or not to update the object syntax and if updated, what the object syntax description is.

See SCCP/TCAP Call Flows.

Configure Local SSN

Set the Config Type byte to 0x01. You may route messages to TCAP or the host by configuring the SSN Routing Flag.

Network DPC/SSN

Set the Config Type byte to 0x07 to configure the Destination Point Code (DPC) and remote subsystem number.

SCCP/TCAP host configuration

Set the Config Type byte to 0x08 to configure the SCCP/TCAP host that is used to receive messages from the SCCP/TCAP layer.

Global Title Translation

Set the Config Type byte to 0x0C to configure Global Title Translation using the TLV Format Configuration Contents. See Global Title Translation (GTT) Configuration Samples.

1 Put all SSNs out of service using the N-STATE request. This will abort any active TCAP transactions for the SSN if TCAP TUSI Config Byte 3 is set to "Yes" (default value).

3 Deconfigure MTP for the stack (links, link sets, route) using the following messages:

See Transaction Capability Application Part.

American National Standards Institute. ANSI administers and coordinates the U.S. voluntary standardization and conformity assessment system for the
telecommunications industry. More details on these standards may be
viewed at www.ansi.org.

International Telecommunications Union (UN)

See Signaling System Number Seven.

See Integrated Services Digital Network User Part.

See Message Transfer Part.

Link that connects to the same node

A number that addresses a node in a SS7 network.

SubSystem Prohibited. See also Service Switching Point.

Message delimiter (SS7 bit pattern - 01111110)

Destination Point Code

Tag-Length-Value block. A standardized block that allows data to inserted in a standard way into API messages.