You are here: CSP Developer’s Guide: Common Channel Signaling > 6 SCCP/TCAP > Configuring SCCP TCAP
Overview
This section describes the SCCP TCAP options that can be configured for a variant of an ANSI or ITU protocol.
Before you begin
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.
Configuring SCCP/TCAP
Use the steps below to configure SCCP/TCAP.
1 Configure the stack using the SS7 Stack Configure message.
2 Configure MTP for the stack (link sets, links, routes) using the following messages:
• SS7 Signaling Route Configure
• SS7 Signaling Link Set Configure
• SS7 Signaling Link Configure
3 Configure the local subsystem number using the SS7 SCCP/TCAP Configure message.
4 Next you can configure SCCP/TCAP options described in the next section.
Procedures for configuring options
You can configure the following SCCP/TCAP options.
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. |
Other Concerned Point Code |
Set the Config Type byte to 0x03. For an SSP or SCP, Point Codes which must be informed about local (CSP) 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 |
Configure the default parameter table for a particular sub-system. Set the Config Type byte to 0x05. |
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. |
Configure Replicated SSN |
Set the Config Type to 0x09 to configure the Replicated Subsystem Number. |
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. |
Querying
Use the SS7 SCCP/TCAP Query message to query the following:
• Local Subsystem Table
• SCCP Default Parameter Table
• Subsystem Default Parameter Table
• TCAP Active Transactions
• TCAP Active Operations
• SCCP Replicated SSN
• Associated subsystems for a stack
• Number of active dialogs and invocations
• TLV Format Configuration Contents
Deconfiguration
To deconfigure an SS7 stack with SCCP/TCAP, do the following:
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).
2 Deconfigure the SSN using the SS7 SCCP/TCAP Configure message.
3 Deconfigure MTP for the stack (links, link sets, route) using the following messages:
• SS7 Signaling Link Configure
• SS7 Signaling Link Set Configure
• SS7 Signaling Route Configure
4 Deconfigure the stack using the SS7 Stack Configure message.