This topic presents the SCCP configuration file parameters:
The general parameters define the operational characteristics of the SCCP layer, such as upper bounds for internal data structures (these determine the amount of memory used by the SCCP layer), queue thresholds, and various protocol timer values. It is the first section of the configuration file.
|
Parameter |
Default |
Valid values |
Description |
|
MAX_USERS |
2 |
1 through 255 |
Maximum number of user SAPs. |
|
MAX_NSAPS |
1 |
1 through 255 |
Maximum number of network SAPs. |
|
MAX_SCLI |
20 |
0 through 65535 |
Maximum number of simultaneous sequenced connectionless data transfers. |
|
MAX_ADDRS |
7 |
0 through 65535 |
Maximum number of address translation entries. |
|
MAX_ROUTES |
4 |
0 through 65535 |
Maximum number of route entries. |
|
MAX_ADJDPC |
4 |
0 through 65535 |
Maximum number of point codes that can be specified as adjacent (that are notified directly by this node of status changes). |
|
MAX_MSGDRN |
5 |
0 through 65535 |
Maximum number messages queued to MTP3 to send in one time interval when exiting flow control. |
|
MAX_XUDT |
0 |
0 through 65535 |
Maximum number of control blocks to allocate for reassembling segmented extended unit data. Used only for ITU-92. Should be zero for ANSI operation. |
|
MAX_XUDTXREF |
0 |
0 through 65535 |
Maximum number of local references used to segment extended unit data. Used only for ITU-92. Should be zero for ANSI operation. |
|
MAX_CONN |
512 |
0 through 65535 |
Maximum number of simultaneous connections. |
|
DEF_ROUTING |
FALSE |
TRUE FALSE |
If TRUE, enables default routing. |
|
PC_FORMAT |
DEFAULT |
DFLT INTL JNTT |
Point code format. DFLT = Point codes are interpreted and displayed as 24-bit 8.8.8 values. INTL = Point codes are interpreted and displayed as 14-bit 3.8.3 values. JNTT = Point codes are interpreted and displayed as 16-bit mcode.scode.ucode values with the U-code in the most significant 7 bits, the S-code in the next 4 bits, and the M-code in the least significant 5 bits. |
|
SAVE_CONNS |
FALSE |
TRUE FALSE |
If TRUE, retains connections when destination inaccessible. If FALSE, drops connections when destination inaccessible. |
|
ALARM_LEVEL |
1 |
0 1 2 3 |
Alarm level reporting. 0 = Disable 1 = Default 2 = Debug 3 = Detail |
|
TRACE_DATA |
FALSE |
TRUE FALSE |
If TRUE, enables data tracing. |
|
CONN_THRESH |
3 |
0 through 9 |
Minimum percentage of board memory that must be available before accepting a new connection in either direction. Expressed in units of 10 percent (for example, 3 = 30 percent). |
|
QUEUE_THRESH |
3 |
0 through 32766 |
Maximum number of data messages that can be queued for a connection waiting for the connection window to open. |
|
SOG_THRESH |
1 |
0 through 9 |
Minimum percentage of board memory that must be available before granting a subsystem out-of-service (SOR) request from a backup signaling point. Expressed in units of 10 percent (for example, 3 = 30 percent). |
|
SCLI_TIMER |
2 seconds |
0 through 65535 |
Maximum time that a sequenced connectionless transmission can take before control block is deallocated. |
|
SST_TIMER |
30 seconds |
0 through 65000 |
Time to wait between subsystem status tests. |
|
NSAP_TIMER |
1 second |
0 through 65535 |
Time to wait between draining blocks of queued messages to the MTP 3 layer after exiting flow control. Used to prevent flooding MTP 3 after network congestion abates. See MAX_MSGDRN. |
|
SRT_TIMER |
30 seconds |
0 through 65535 |
Time to wait between subsystem routing tests (ANSI only). |
|
IGNORE_TIMER |
30 seconds |
0 through 65535 |
Time period after local subsystem goes out of service to ignore subsystem test messages. |
|
COORD_TIMER |
30 seconds |
0 through 65535 |
Time to wait for response to coordinated state change request. |
|
XREFFRZ_TIMER |
1 second |
0 through 65535 |
Time to freeze an XUDT local reference before reusing it (ITU-92 only). |
|
ASMB_TIMER |
20 seconds |
0 through 65535 |
Maximum time for reassembling all segments of an XUDT message (ITU-92 only). |
|
FREEZE_TIMER |
1 second |
0 through 65535 |
Time to freeze a connection local reference before reusing it. |
|
CONN_TIMER |
180 seconds |
0 through 65535 |
Time to wait for response to connection request. |
|
TXINACT_TIMER |
600 seconds |
0 through 65535 |
Time to wait with no outgoing packets on a connection before sending an inactivity test message. |
|
RXINACT_TIMER |
900 seconds |
0 through 65535 |
Time to wait with no incoming packets on a connection before clearing connection. Must be greater than TXINACT_TIMER. |
|
REL_TIMER |
4 seconds |
0 through 65535 |
Time to wait for response to release request. |
|
REPREL_TIMER |
4 seconds |
0 through 65535 |
Time to wait for response to second release request (ITU-T 92 only). |
|
INTERVAL_TIMER |
8 seconds |
0 through 65535 |
Time to wait to report abnormal release timer. |
|
GUARD_TIMER |
1 second |
0 through 65535 |
Time to wait after MTP 3 restart before allowing application traffic. |
|
RESET_TIMER |
6 seconds |
0 through 65535 |
Time to wait for response to reset request. |
|
AIC_TIMER |
480 seconds |
0 through 65535 |
Time with no application activity for an active connection before SCCP generates a connection inactivity indication event. Used only if the application inactivity control is enabled for that user SAP. |
|
AIC_RESP_TIMER |
10 seconds |
0 through 65535 |
Time the application gets to respond to a connection inactivity indication event. Use only if the application inactivity control is enabled for that user SAP. |
|
ACR_TIMER |
10 seconds |
0 through 65535 |
Time the application gets to respond to an incoming connection indication with either a connection response or release request before the SCCP layer refuses connection. If the value is zero, no timing for the application response is performed. |
|
SCCP_ALARM_LEVEL |
1 |
1 2 3 |
Desired level of alarms generated by SCCP layer. 1 = (Normal) Normal service impacting alarms. 2 = (Debug) All normal alarms plus all messages in or out. 3 = (Detail) All debug alarms plus detailed events. |
|
MEM_THRESH_1 |
10 |
0 through 99 |
Percentage of board memory available at which memory congestion level 1 starts. |
|
MEM_THRESH_2 |
8 |
0 through 99 |
Percentage of board memory available at which memory congestion level 2 starts. |
|
MEM_THRESH_3 |
5 |
0 through 99 |
Percentage of board memory available at which memory congestion level 3 starts. |
|
END |
N/A |
N/A |
Denotes end of the section. This parameter is required. |
One user service access point (SAP) is defined for each application using SCCP. A user SAP is associated with a single subsystem number and switch type (ANSI88, ANSI92, ANSI96, ITU88, ITU92, ITU96). The user SAP defines whether the application is replicated on another node for reliability purposes, and lists any concerned point codes (nodes that must be notified of any change in the availability of the application).
|
Parameter |
Default |
Valid values |
Description |
|
USER_SAP |
None |
0 through (MAX_USERS-1) |
Marks the start of a user SAP definition. |
|
SWITCH_TYPE |
ANSI92 |
ITU88 ITU92 ITU96 ANSI88 ANSI92 ANSI96 |
Protocol variant employed on this user SAP. |
|
BACKUP_PC |
None |
Use dotted notation (such as 2.45.76) or a hexadecimal number (such as 0x101) |
Point code where this subsystem is backed up. |
|
CONC_PC |
None |
Use dotted notation (such as 2.45.76) or a hexadecimal number (such as 0x101) |
Concerned point code to be notified of changes in the availability of this application. As many as eight CONC_PC entries (on separate lines) are allowed per user SAP. Note: If OPC emulation is used, any concerned point codes must be listed in an ALT_OPC section. |
|
ADDR_MASK |
FFF...F |
N/A |
ASCII string describing which digits of the global title to match when performing global title translation. As many as four ADDR_MASK entries are allowed per user SAP. Note: Address masks are ASCII strings containing a 0 (zero) or F in each character position to determine whether the corresponding global title digit is used in the match. For example, the string 000FFFFFFF ignores the first three digits and compares only the last seven digits when searching the global title table for a match. Similarly, the string FFF compares only the first three digits to determine a match. |
|
MAX_HOPS |
10 |
1 through 15 |
Hop count value to be used on outgoing SCCP messages from this SAP. |
|
INACT_CONTROL |
False |
True/1/Yes False/0/No |
When True, enables SCCP inactivity timing on connections associated with this SAP, enabling SCCP to detect and clear connections of which the application has lost track. The application must handle the connection inactivity indication event and respond with a connection inactivity response if this feature is enabled. |
|
CONG_THRESH_1 |
600 |
1 through 2000 |
Number of messages outstanding to a higher level task (such as TCAP) or a user application at which inbound congestion level 1 starts. |
|
CONG_THRESH_2 |
900 |
1 through 2000 |
Number of messages outstanding to a higher level task (such as TCAP) or a user application at which inbound congestion level 2 starts. |
|
CONG_THRESH_3 |
1200 |
1 through 2000 |
Number of messages outstanding to a higher level task (such as TCAP) or a user application at which inbound congestion level 3 starts. |
|
ALT_OPC |
None |
Use dotted notation (such as 2.45.76) or a hexadecimal number (such as 0x101) |
Denotes the start of an emulated OPC section. All emulated OPC values must be listed in their own ALT_OPC section. A maximum of eight ALT_OPC sections are allowed in a USER_SAP section. |
|
CONC_PC |
None |
Use dotted notation (such as 2.45.76) or a hexadecimal number (such as 0x101) |
Concerned point code to be notified of changes in the availability of this application. As many as eight CONC_PC entries (on separate lines) are allowed in each ALT_OPC section. |
|
END |
N/A |
N/A |
Denotes the end of the ALT_OPC section in the current USER_SAP section. |
|
END |
N/A |
N/A |
Denotes end of the section. This parameter is required. |
The network service access point (SAP) defines the point at which the SCCP layer accesses the network (MTP 3) layer. One network SAP is defined for each supported switch type (ANSI or ITU-T). The NSAP number assigned in this section (NSAP number statement) must match a valid NSAP number defined in the NSAP section (NSAP number statement) of the MTP 3 configuration file.
Note: If both the SCCP and ISUP layers are used on the same board, the SCCP layer cannot be assigned to MTP3 NSAP 0 (zero); ISUP always uses this NSAP.
|
Parameter |
Default |
Valid values |
Description |
|
NSAP |
None |
0 through (MAX_NSAPS - 1) |
Marks start of a network SAP definition. Must match an NSAP number defined in the MTP 3 configuration. |
|
SWITCH_TYPE |
ANSI |
ITU ANSI |
Protocol variant employed on this NSAP. |
|
SSF |
NATL (ANSI) INTL (ITU) |
INTERNATIONAL|INTL SPARE NATIONAL|NATL RESERVED|RES |
Value to be used in the subservice field for this network. |
|
DPC |
None |
Use dotted notation (such as 2.45.76) or a hexadecimal number (such as 0x101) |
Point code of this node on this network interface. If OPC emulation is in use, the default OPC should be listed here. This parameter is required. |
|
DPC_LEN |
24 (ANSI | ITU) 14 (ITU) |
14 24 |
Point code length employed on this network. |
|
ALT_OPC |
None |
Use dotted notation (such as 2.45.76) or a hexadecimal number (such as 0x101) |
List of additional emulated OPC values. |
|
MSG_LEN |
256 |
32 through 1500 |
Maximum length of a message passed to MTP 3 on this SAP. |
|
TXQ_THRESH |
20 |
0 through 32766 |
Maximum number of messages to queue to MTP 3 when flow control is on before discarding. |
|
ADDR_MASK |
FFF...F |
N/A |
ASCII string describing which digits of the global title to match when performing global title translation. Up to four ADDR_MASK entries are allowed per network SAP. Note: The network SAP address mask is used only when providing global translation for incoming messages (those received from the network). For messages originated by an application on this node, the user SAP address mask is used. |
|
MAX_HOPS |
10 |
1 through 15 |
Hop count value to be used when returning undeliverable incoming messages back to the source of the message. |
|
SCCP_NI_IND |
0 (ITU) 1 (ANSI) |
0 1 |
National or international indicator in the called or calling party address parameter of the outgoing SCCP management messages. |
|
END |
N/A |
N/A |
Denotes the end of the section. This parameter is required. |
Address entries define how the SCCP layer translates global titles. A global title can translate into one of the following:
A point code and subsystem number (use GT_FORMAT 0).
Another global title only (in this case the message to be routed must include a destination point code in addition to the incoming global title).
Another global title and point code.
Another global title and subsystem number (in this case the message to be routed must include a destination point code in addition to the incoming global title).
Another global title and point code and subsystem number.
Multiple address translations can be configured, up to the MAX_ADDRS value specified in the general parameters section.
|
Parameter |
Default |
Valid values |
Description |
|
ADDRESS |
None |
N/A |
Incoming global title string, ASCII digits (for example, 0 through 9). |
|
REPLACE_GLT |
FALSE |
TRUE FALSE |
If TRUE, replace the translated global title in the outgoing message. If FALSE, copy the incoming global title, translated point code, and subsystem to the outgoing message. |
|
SWITCH_TYPE |
ANSI |
ITU ANSI |
Format of this address. |
|
NI_IND |
NAT |
NATIONAL|NAT INTERNATIONAL|INTL |
National or international indicator. |
|
ROUTING_IND |
PC_SSN |
PC_SSN GLT |
Routing indicator for the translated address. PC_SSN = Route by PC and SSN GLT = Route by global title |
|
SSN |
None |
0 through 255 |
Translated subsystem number (required for GT_FORMAT 0). |
|
DPC |
None |
Use dotted notation (such as 2.45.76) or a hexadecimal number (such as 0x101) |
Translated destination point code (required for GT_FORMAT 0). |
|
GT_FORMAT |
0 |
0 through 4 |
Structure of the outgoing global title. Use only when REPLACE_GLT parameter is TRUE. 0 = No global title translation. 1 = (ANSI) Outgoing global title includes translation type, numbering plan, and encoding scheme. (ITU) Outgoing global title includes nature of address indicator. 2 = (ANSI and ITU) Outgoing global title includes translation type only. 3 = (ITU only) Outgoing global title includes translation type, numbering plan, and encoding scheme. 4 = (ITU only) Outgoing global title includes translation type, numbering plan, encoding scheme, and nature of address indicator. |
|
GL_TITLE |
None |
N/A |
Outgoing global title string (ASCII digits; such as 0 through 9). Use only when REPLACE_GLT parameter is TRUE. |
|
TRANS_TYPE |
0 |
0 through 255 |
Outgoing global title translation type. Use only when REPLACE_GLT parameter is TRUE. |
|
NAT_ADDR |
3 |
0 through 4 |
Outgoing global title nature of address indicator (ITU only). Use only when REPLACE_GLT parameter is TRUE. |
|
NUM_PLAN |
1 |
0 through 15 |
Outgoing global title numbering plan (ISDN numbering plan). Use only when REPLACE_GLT parameter is TRUE. |
|
END |
N/A |
N/A |
Denotes the end of the section. This parameter is required. |
A route configuration entry defines a point code (and its subsystems) known to this node. Define a route entry for each point code and switch type to which this node can send SCCP messages.
Note: A route definition contains one or more subsystem definitions, each of which spans multiple lines and is terminated with an END statement. Each route definition as a whole is also terminated with an END statement. Mismatched END statements are a common cause of configuration errors and can cause unpredictable results.
|
Parameter |
Default |
Valid values |
Description |
|
ROUTE |
None |
Use dotted notation (such as 2.45.76) or a hexadecimal number (such as 0x101). |
Destination point code. This parameter is required. |
|
SWITCH_TYPE |
ANSI |
ITU ANSI |
Protocol variant for this point code. |
|
TRANSLATOR |
TRUE |
TRUE FALSE |
If TRUE, this signaling point is a translator node. |
|
ADJACENT |
TRUE |
TRUE FALSE |
If TRUE, this signaling point is adjacent for SCCP point code and subsystem management procedures. |
|
BACKUP_PC |
None |
Use dotted notation (such as 2.45.76) or a hexadecimal number (such as 0x101). |
Backup point code. If not present, signaling point is not replicated. |
|
ALT_OPC |
None |
Use dotted notation (such as 2.45.76) or a hexadecimal number (such as 0x101) |
List of any emulated OPC values for this route. This field is not required if OPC emulation is not in use. |
|
SSN |
None |
0 through 255 |
Subsystem number. Also denotes the beginning of the subsystem definition subsection that is terminated by the END statement. As many as eight subsystem definition subsections can be included in each route definition. |
|
SSN_SNR |
TRUE |
TRUE FALSE |
Subsystem routing. TRUE = Normal routed FALSE = Backup routed |
|
SSN_ACC |
TRUE |
TRUE FALSE |
Subsystem accessibility. TRUE = Initially accessible FALSE = Not initially accessible |
|
SSN_BPC |
None |
Use dotted notation (such as 2.45.76) or a hexadecimal number (such as 0x101). |
Subsystem backup point code. If not present, the subsystem is not replicated. |
|
SSN_UP_ON_RESUME |
1 |
1 0 |
1 = Subsystem is immediately put back in service when a point code resume message is received from MTP. The subsystem test procedure is not started. 0 = Disables this functionality. |
|
CONC_PC |
None |
Use dotted notation (such as 2.45.76) or a hexadecimal number (such as 0x101). |
Concerned point code to be notified of changes in the availability of this subsystem. As many as eight CONC_PC entries (on separate lines) are allowed per subsystem per route. |
|
END |
N/A |
N/A |
Required parameter denoting the end of the current subsystem definition subsection. Repeated for each separate SSN section within this route entry. |
|
END |
N/A |
N/A |
Required parameter denoting the end of the current route definition section. |