Toolpack:Create a SCCP stack - Revision history

Allyntree at 17:15, 1 May 2018

2018-05-01T17:15:06Z

← Older revision		Revision as of 13:15, 1 May 2018
Line 1:		Line 1:
	~~[[Toolpack Version 2.4, Creating an SCCP Stack]]~~

	[[Toolpack_v2.3:Create_an_SCCP_Stack\|Toolpack Version 2.3, Creating an SCCP Stack]]		[[Toolpack_v2.3:Create_an_SCCP_Stack\|Toolpack Version 2.3, Creating an SCCP Stack]]
Line 88:		Line 87:
	*The '''Array of ISNI mapping entries''' parameter specifies the values of the SS7 format NID to PC configuration. NID to PC configuration serves as a lookup table to select a destination point code corresponding to a network ID.		*The '''Array of ISNI mapping entries''' parameter specifies the values of the SS7 format NID to PC configuration. NID to PC configuration serves as a lookup table to select a destination point code corresponding to a network ID.
	*The '''Array of INS mapping entries''' parameter specifies the values of the Network specific NID to SS7-format NID mapping configuration. This configuration allows to use a NID in network specific format in INS parameter and serves as a lookup table to select an SS7 format NID corresponding to a network specific NID present in INS parameter. The SS7 format NID selected from this database is used to find a destination point code from the table containing SS7-NID to PC mapping.		*The '''Array of INS mapping entries''' parameter specifies the values of the Network specific NID to SS7-format NID mapping configuration. This configuration allows to use a NID in network specific format in INS parameter and serves as a lookup table to select an SS7 format NID corresponding to a network specific NID present in INS parameter. The SS7 format NID selected from this database is used to find a destination point code from the table containing SS7-NID to PC mapping.


	~~[[category:Needs revising]]~~

Allyntree at 00:01, 12 November 2009

2009-11-12T00:01:17Z

← Older revision		Revision as of 20:01, 11 November 2009
Line 1:		Line 1:
	[[Toolpack Version 2.4 Creating an SCCP Stack~~\|Toolpack Version 2.4~~]]		[[Toolpack Version 2.4, Creating an SCCP Stack]]

	[[Toolpack Version 2.3 Creating an SCCP Stack~~\|Toolpack Version 2.3~~]]		[[Toolpack_v2.3:Create_an_SCCP_Stack\|Toolpack Version 2.3, Creating an SCCP Stack]]

Allyntree at 23:59, 11 November 2009

2009-11-11T23:59:11Z

← Older revision		Revision as of 19:59, 11 November 2009
Line 1:		Line 1:
	[[Toolpack Version 2.4 Creating an SCCP Stack\|Toolpack Version 2.4]]		[[Toolpack Version 2.4 Creating an SCCP Stack\|Toolpack Version 2.4]]

	[[Toolpack Version 2.3 Creating an SCCP Stack\|Toolpack Version 2.3]]		[[Toolpack Version 2.3 Creating an SCCP Stack\|Toolpack Version 2.3]]

Allyntree at 23:58, 11 November 2009

2009-11-11T23:58:44Z

← Older revision		Revision as of 19:58, 11 November 2009
Line 1:		Line 1:
	[[Toolpack Version 2.4, Creating an SCCP Stack\|Toolpack Version 2.4]]		[[Toolpack Version 2.4 Creating an SCCP Stack\|Toolpack Version 2.4]]
	[[Toolpack Version 2.3, Creating an SCCP Stack\|Toolpack Version 2.3]]		[[Toolpack Version 2.3 Creating an SCCP Stack\|Toolpack Version 2.3]]

Allyntree at 23:58, 11 November 2009

2009-11-11T23:58:12Z

← Older revision		Revision as of 19:58, 11 November 2009
Line 1:		Line 1:
	~~WALKTHROUGH AND SCREENSHOT CONTENT ARE OUTSTANDING~~		[[Toolpack Version 2.4, Creating an SCCP Stack\|Toolpack Version 2.4]]
			[[Toolpack Version 2.3, Creating an SCCP Stack\|Toolpack Version 2.3]]

Ktrueman: clean up

2009-09-04T16:17:54Z

clean up

← Older revision		Revision as of 12:17, 4 September 2009
Line 4:		Line 4:
	== Description of parameters ==		== Description of parameters ==

	General explanation of the parameters ~~of configuration~~:		General explanation of the configuration parameters:

	*The '''Default status enquiry timer''' parameter specifies the time to send the periodic status request to [[MTP3 Layer\|MTP Level 3]] to enquire of the status of a point code ([[OPC]]/[[DPC]]). Typical value is 1000 milliseconds (1 second).		*The '''Default status enquiry timer''' parameter specifies the time to send the periodic status request to [[MTP3 Layer\|MTP Level 3]] to enquire of the status of a point code ([[OPC]]/[[DPC]]). Typical value is 1000 milliseconds (1 second).

Ktrueman: initial content

2009-09-02T19:27:37Z

initial content

New page

WALKTHROUGH AND SCREENSHOT CONTENT ARE OUTSTANDING

== Description of parameters ==

General explanation of the parameters of configuration:

*The '''Default status enquiry timer''' parameter specifies the time to send the periodic status request to [[MTP3 Layer|MTP Level 3]] to enquire of the status of a point code ([[OPC]]/[[DPC]]). Typical value is 1000 milliseconds (1 second).

'''NOTE:''' A value of 0 will disable the timer

----

*The '''Traffic limitation flag''' parameter. If this flag is set to 'True', then the default traffic limitation is replaced by the new traffic limitation values define in the TRaffic limitation array.

'''NOTE:''' Can be set to 'True' only when using ITU96

----

*The '''Message importance flag''' parameter. If this flag is set to 'True', then the default message importance is replaced by the new message importance values defined in the 'Message Importance' structure.

'''NOTE:''' Can be set to 'True' only when using ITU96

----

*The '''Array of traffic limitation''' parameter specifies the values of the traffic limitation mechanism. As part of traffic limitation mechanism, on the event of remote SCCP congestion and/or underlying network congestion, SCCP discards a portion of traffic on the basis of importance of message and value of restriction level (RL) / restriction sub-level (RSL) for a destination. Each element of the table contains un8RL, un8RSL and un8RIL. RIL is restricted importance level, which is broadcast to SCCP user. SCCP user fills the importance of message on the basis of received RIL. This parameter is reconfigurable. Allowable values include:

{| class="wikitable" border="1"
! width="150" style="background:#efefef;" |Traffic limitation fields
! width="350" style="background:#efefef;" |Description
|-
| RL|| Restriction Level. It can assume a value in the range of 0 to 7
|-
| RSL|| Restriction Sub-Level. It can assume a value in the range of 0 to 3
|-
| RIL|| Restricted Importance Level. It can assume a value in the range of 0 to 7. RIL is passed to user at SPT interface so as user can fill proper value for parameter importance in subsequent messages to avoid message being discarded due to traffic limitation mechanism.
|}

'''NOTE:''' Allowed for ITU96 only

----

*The '''Message importance parameter''' specifies the values of the message importance. These values are used in the 'traffic limitation' mechanism.

'''NOTE:''' Message importance configuration is optional. If the message importance configuration is not performed, then SCCP assumes the default values of message importance as per Q714, ITU-T 1996. If message importance is configured, then the default values are overwritten with those of configured values.

'''NOTE:''' Allowed for ITU96 only

----

*The '''Number of ISNI entries''' parameter specifies the number of ISNI (Intermediate Signaling Network Identification) entries in the ISNI Network ID Map array.

'''NOTE:''' Allowed for ANSI96 and TELCORDIA only

----

*The '''Number of INS entries''' parameter specifies the number of INS (Intermediate Network Selections) entries in the ISNI Network ID Map array.

'''NOTE:''' Allowed for TELCORDIA only

----

*The '''Array of ISNI mapping entries''' parameter specifies the values of the SS7 format NID to PC configuration. NID to PC configuration serves as a lookup table to select a destination point code corresponding to a network ID.
*The '''Array of INS mapping entries''' parameter specifies the values of the Network specific NID to SS7-format NID mapping configuration. This configuration allows to use a NID in network specific format in INS parameter and serves as a lookup table to select an SS7 format NID corresponding to a network specific NID present in INS parameter. The SS7 format NID selected from this database is used to find a destination point code from the table containing SS7-NID to PC mapping.

[[category:Needs revising]]