SCCP/API:Configuration - Revision history

Sylvain Fontaine at 16:49, 1 May 2012

2012-05-01T16:49:16Z

← Older revision		Revision as of 11:49, 1 May 2012
Line 3:		Line 3:
	#The SCCP [[Toolpack:Create a SCCP stack\|general allocation]] (see Note below) (TB640_MSG_ID_SS7_SCCP_OP_ALLOC) must precede all other messages (other configuration SCCP alloc, get, states and stats). The response of this message is a SCCP handle.		#The SCCP [[Toolpack:Create a SCCP stack\|general allocation]] (see Note below) (TB640_MSG_ID_SS7_SCCP_OP_ALLOC) must precede all other messages (other configuration SCCP alloc, get, states and stats). The response of this message is a SCCP handle.
	#The SCCP [[Toolpack:Create a SCCP network\|network allocation]] must be made (with the SCCP handle from step 1) for a particular network identifier with a particular variant, self point code and subservice field type. The response of this message is a SCCP Network handle.		#The SCCP [[Toolpack:Create a SCCP network\|network allocation]] must be made (with the SCCP handle from step 1) for a particular network identifier with a particular variant, self point code and subservice field type. The response of this message is a SCCP Network handle.
	#The SCCP [[Toolpack:Create a SCCP LSAP\|LSAP allocation]] must be made (with the SCCP handle from step 1, network handle from step 2 and the unique identifier of the MTP3 userpart) to connect with the MTP3 userpart		#The SCCP [[Toolpack:Create an SCCP LSAP\|LSAP allocation]] must be made (with the SCCP handle from step 1, network handle from step 2 and the unique identifier of the MTP3 userpart) to connect with the MTP3 userpart
	#The SCCP [[Toolpack:Create a SCCP route\|route allocation]] must be made (with the SCCP handle from step 1 and the lsap handle from step 3 for a particular variant, replicated mode and DPC		#The SCCP [[Toolpack:Create an SCCP route\|route allocation]] must be made (with the SCCP handle from step 1 and the lsap handle from step 3 for a particular variant, replicated mode and DPC
	#The SCCP [[Toolpack:Create a SCCP userpart\|userpart allocation]] must be made (with the SCCP handle from step 1 and the network handle from step 2 for a particular subsystem number		#The SCCP [[Toolpack:Create a SCCP userpart\|userpart allocation]] must be made (with the SCCP handle from step 1 and the network handle from step 2 for a particular subsystem number
	#The SCCP [[SCCP:GTT Association Configuration\|GTT association allocation]] must be made (with the SCCP handle from step 1) for a particular global title association		#The SCCP [[SCCP:GTT Association Configuration\|GTT association allocation]] must be made (with the SCCP handle from step 1) for a particular global title association

Sylvain Fontaine: moved SCCP:Configuration to SCCP/API:Configuration

2012-05-01T16:39:16Z

moved SCCP:Configuration to SCCP/API:Configuration

← Older revision	Revision as of 11:39, 1 May 2012
(No difference)

Ktrueman: content moved from configuration page

2009-09-08T18:27:38Z

content moved from configuration page

New page

General guidelines for configuration of SCCP for proper operation include the following steps:

#The SCCP [[Toolpack:Create a SCCP stack|general allocation]] (see Note below) (TB640_MSG_ID_SS7_SCCP_OP_ALLOC) must precede all other messages (other configuration SCCP alloc, get, states and stats). The response of this message is a SCCP handle.
#The SCCP [[Toolpack:Create a SCCP network|network allocation]] must be made (with the SCCP handle from step 1) for a particular network identifier with a particular variant, self point code and subservice field type. The response of this message is a SCCP Network handle.
#The SCCP [[Toolpack:Create a SCCP LSAP|LSAP allocation]] must be made (with the SCCP handle from step 1, network handle from step 2 and the unique identifier of the MTP3 userpart) to connect with the MTP3 userpart
#The SCCP [[Toolpack:Create a SCCP route|route allocation]] must be made (with the SCCP handle from step 1 and the lsap handle from step 3 for a particular variant, replicated mode and DPC
#The SCCP [[Toolpack:Create a SCCP userpart|userpart allocation]] must be made (with the SCCP handle from step 1 and the network handle from step 2 for a particular subsystem number
#The SCCP [[SCCP:GTT Association Configuration|GTT association allocation]] must be made (with the SCCP handle from step 1) for a particular global title association
#The SCCP [[SCCP:GTT Address Map Configuration|GTT address map allocation]] must be made (with the SCCP handle from step 1 and the Gtt asso handle from step 6) for a particular global title address map

== Configuration notes ==
*Step 2 can be done for 1 to the maximum number of configured Networks
*Step 3 can be done for 1 to the maximum number of configured LSAPs
*Step 4 can be done for 1 to the maximum number of configured Routes
*Step 5 must be done for 1 to the maximum number of configured Userparts
*Step 6 must be done for 1 to the maximum number of configured GTT Asso
*Step 7 must be done for 1 to the maximum number of configured GTT Addrmap