MTP3:Userpart Configuration - Revision history

Allyntree at 15:47, 28 March 2018

2018-03-28T15:47:05Z

Allyntree at 15:46, 28 March 2018

2018-03-28T15:46:24Z

Allyntree at 15:44, 28 March 2018

2018-03-28T15:44:23Z

Allyntree at 15:43, 28 March 2018

2018-03-28T15:43:41Z

Allyntree at 15:43, 28 March 2018

2018-03-28T15:43:06Z

Allyntree: Needs revising edit.

2018-03-28T15:40:45Z

Needs revising edit.

Ktrueman: clean up

2009-09-03T17:56:22Z

clean up

Ktrueman: clean up

2009-08-27T21:53:13Z

clean up

Ktrueman: initial content

2009-08-27T18:49:58Z

initial content

New page

General explanation of the parameters of configuration:

*'MTP3 user part unique ID' is used to configure identical [[MTP3 Layer|MTP3]] userparts in each MTP3 module and to connect [[ISUP]] networks.

*The 'Connection mode' parameter specifies the different modes of connection for an MTP3 userpart. The following values are allowed:

{| class="wikitable" border="1"
! width="150" style="background:#efefef;" |Connection mode
! width="350" style="background:#efefef;" |Description
|-
| SCCP|| MPT3 userpart is used in conjunction with an above local SCCP layer and cannot be controlled by the host application
|-
| SCCP with alarms|| MPT3 userpart is used in conjunction with an above local SCCP layer and cannot be controlled by the host application but the host application will receive ALARM notifications
|-
| ISUP|| MTP3 userpart is used in conjunction with an above local ISUP layer and cannot be controlled by the host application
|-
| ISUP with alarms|| MPT3 userpart is used in conjunction with an above local ISUP layer and cannot be controlled by the host application but the host application will receive ALARM notifications
|-
| Host SCCP|| MTP3 userpart is used as a standalone and communicates with remote SCCP layer (host application)
|-
| Host TUP 5|| MTP3 userpart is used as a standalone and communicates with remote TUP layer (host application)
|-
| Host ISUP|| MTP3 userpart is used as a standalone and communicates with remote ISUP layer (host application)
|}

*The 'Sub-service' field specifies the type of network. If validation is activated in the general MTP3 configuration, all userpart messages will be compared to this sub-service field type. All non-matching messages will be discarded. The following values are allowed:

{| class="wikitable" border="1"
! width="150" style="background:#efefef;" |Sub-service field
! width="350" style="background:#efefef;" |Description
|-
| International|| Messages sent by the layer will concern international traffic
|-
| National|| Messages sent by the layer will concern national traffic
|-
| Reserved|| Reserved for national use

|}

'''NOTE:''' For all national networks (including TTC and NTT), the 'Sub-service' field is configured with 'National'. For international networks, the 'Sub-service' field is configured with 'International'.

'''NOTE:''' For international networks you must have the same values for Prior Message Queue Length 1 to Prior Message Queue Length 1 in a MTP3 Link Configuration.

*The 'Link type' field specifies the MTP3 protocol variant required to provide service to the userpart connected through this upper Service Access Point (SAP). The following values are allowed:

{| class="wikitable" border="1"
! width="150" style="background:#efefef;" |Link type
! width="350" style="background:#efefef;" |Description
|-
| ANSI|| Used for ANSI88 and ANSI92
|-
| ITU|| Used for ITU88, ITU92, ITU97, Q767, SINGAPORE and ETSI
|-
| CHINA|| Used for CHINA
|-
| ANSI96|| Used for ANSI96 and TELCORDIA
|-
| TTC|| Link type not available yet
|-
| NTT|| Link type not available yet
|}

*The 'DPC length' field specifies the length of the DPC for messages communicated through this SAP. For allowable values, see [[MTP2:Destination Point Code]].
*The switch ID parameter specifies a value to regroup linksets and user parts together. Allowable values are from 10 to 255.

← Older revision		Revision as of 15:47, 28 March 2018
Line 84:		Line 84:
	*The '''Switch ID''' parameter specifies a value to regroup linksets and user parts together. Allowable values are from 10 to 255.		*The '''Switch ID''' parameter specifies a value to regroup linksets and user parts together. Allowable values are from 10 to 255.

−	For further configuration information see [[Toolpack:Protocol_Stack_Settings_D]]	+	For further configuration information see [[Toolpack:Protocol_Stack_Settings_D\|Protocol Stack Settings]]

← Older revision		Revision as of 15:46, 28 March 2018
Line 84:		Line 84:
	*The '''Switch ID''' parameter specifies a value to regroup linksets and user parts together. Allowable values are from 10 to 255.		*The '''Switch ID''' parameter specifies a value to regroup linksets and user parts together. Allowable values are from 10 to 255.

−	For further configuration information see ~~the~~ [[~~https://docs.telcobridges.com/tbwiki/~~Toolpack:Protocol_Stack_Settings_D ~~\| Web Portal~~]]	+	For further configuration information see [[Toolpack:Protocol_Stack_Settings_D]]

← Older revision		Revision as of 15:44, 28 March 2018
Line 84:		Line 84:
	*The '''Switch ID''' parameter specifies a value to regroup linksets and user parts together. Allowable values are from 10 to 255.		*The '''Switch ID''' parameter specifies a value to regroup linksets and user parts together. Allowable values are from 10 to 255.

−	For further configuration information see the [[https://docs.telcobridges.com/tbwiki/Toolpack:Protocol_Stack_Settings_D\|Web Portal]]	+	For further configuration information see the [[https://docs.telcobridges.com/tbwiki/Toolpack:Protocol_Stack_Settings_D \| Web Portal]]

← Older revision		Revision as of 15:43, 28 March 2018
Line 84:		Line 84:
	*The '''Switch ID''' parameter specifies a value to regroup linksets and user parts together. Allowable values are from 10 to 255.		*The '''Switch ID''' parameter specifies a value to regroup linksets and user parts together. Allowable values are from 10 to 255.

−	For further configuration information see the [[~~Webportal\|~~https://docs.telcobridges.com/tbwiki/Toolpack:Protocol_Stack_Settings_D]]	+	For further configuration information see the [[https://docs.telcobridges.com/tbwiki/Toolpack:Protocol_Stack_Settings_D\|Web Portal]]

← Older revision		Revision as of 15:43, 28 March 2018
Line 83:		Line 83:
	*The '''DPC length''' field specifies the length of the DPC for messages communicated through this SAP. For allowable values, see [[MTP2:Destination Point Code]].		*The '''DPC length''' field specifies the length of the DPC for messages communicated through this SAP. For allowable values, see [[MTP2:Destination Point Code]].
	*The '''Switch ID''' parameter specifies a value to regroup linksets and user parts together. Allowable values are from 10 to 255.		*The '''Switch ID''' parameter specifies a value to regroup linksets and user parts together. Allowable values are from 10 to 255.
		+
		+	For further configuration information see the [[Webportal\|https://docs.telcobridges.com/tbwiki/Toolpack:Protocol_Stack_Settings_D]]

@@ Line 1: / Line 1: @@
 *'''MTP3 user part unique ID''' is used to configure identical [[MTP3 Layer|MTP3]] userparts in each MTP3 module and to connect [[ISUP]] networks.
@@ Line 93: / Line 83: @@
 *The '''DPC length''' field specifies the length of the DPC for messages communicated through this SAP. For allowable values, see [[MTP2:Destination Point Code]].
 *The '''Switch ID''' parameter specifies a value to regroup linksets and user parts together. Allowable values are from 10 to 255.

@@ Line 1: / Line 1: @@
 General explanation of the parameters of configuration:
 *'''MTP3 user part unique ID''' is used to configure identical [[MTP3 Layer|MTP3]] userparts in each MTP3 module and to connect [[ISUP]] networks.
 *The '''Connection mode''' parameter specifies the different modes of connection for an MTP3 userpart. The following values are allowed:
@@ Line 29: / Line 42: @@
-*The '''Sub-service''' field specifies the type of network. If validation is activated in the general MTP3 configuration, all userpart messages will be compared to this sub-service field type. All non-matching messages will be discarded. The following values are allowed:
+*The '''Sub-service field''' specifies the type of network. If validation is activated in the general MTP3 configuration, all userpart messages will be compared to this sub-service field type. All non-matching messages will be discarded. The following values are allowed:
@@ Line 80: / Line 93: @@
 *The '''DPC length''' field specifies the length of the DPC for messages communicated through this SAP. For allowable values, see [[MTP2:Destination Point Code]].
 *The '''Switch ID''' parameter specifies a value to regroup linksets and user parts together. Allowable values are from 10 to 255.

@@ Line 1: / Line 1: @@
 General explanation of the parameters of configuration:
-*'MTP3 user part unique ID' is used to configure identical [[MTP3 Layer|MTP3]] userparts in each MTP3 module and to connect [[ISUP]] networks.
+*'''MTP3 user part unique ID''' is used to configure identical [[MTP3 Layer|MTP3]] userparts in each MTP3 module and to connect [[ISUP]] networks.
-*The 'Connection mode' parameter specifies the different modes of connection for an MTP3 userpart. The following values are allowed:
+*The '''Connection mode''' parameter specifies the different modes of connection for an MTP3 userpart. The following values are allowed:
@@ Line 26: / Line 26: @@
-*The 'Sub-service' field specifies the type of network. If validation is activated in the general MTP3 configuration, all userpart messages will be compared to this sub-service field type. All non-matching messages will be discarded. The following values are allowed:
+----
@@ Line 43: / Line 46: @@
 '''NOTE:''' For all national networks (including TTC and NTT), the 'Sub-service' field is configured with 'National'. For international networks, the 'Sub-service' field is configured with 'International'.
 '''NOTE:''' For international networks you must have the same values for Prior Message Queue Length 1 to Prior Message Queue Length 1 in a MTP3 Link Configuration.
-*The 'Link type' field specifies the MTP3 protocol variant required to provide service to the userpart connected through this upper Service Access Point (SAP). The following values are allowed:
+----
@@ Line 68: / Line 75: @@
-*The 'DPC length' field specifies the length of the DPC for messages communicated through this SAP. For allowable values, see [[MTP2:Destination Point Code]].
+----
-*The switch ID parameter specifies a value to regroup linksets and user parts together. Allowable values are from 10 to 255.