SCCP
From TBwiki
(Difference between revisions)
(initial content) |
(Lm Added links) |
||
| (16 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
[[Image:SCCP-OSI model.jpg|thumb|300px|Schematic showing SCCP in the OSI model]] | [[Image:SCCP-OSI model.jpg|thumb|300px|Schematic showing SCCP in the OSI model]] | ||
| − | The Signaling Connection Control Part (SCCP) layer provides connectionless network services and an address translation mechanism, called global title translation (GTT), capability above [[MTP3 Layer|MTP3]]. A global title can translate a string of digits (e.g., a dialled 800 number, calling card number, or mobile subscriber identification number) into a destination point code and/or subsystem number. A subsystem number uniquely identifies an application at the destination signaling point. SCCP provides the transport layer for [[TCAP]]-based services within the OSI model. | + | The Signaling Connection Control Part (SCCP) layer provides connectionless network services and an address translation mechanism, called global title translation (GTT), capability above [[MTP3 Layer|MTP3]]. A global title can translate a string of digits (e.g., a dialled 800 number, calling card number, or mobile subscriber identification number) into a destination point code and/or subsystem number. A subsystem number uniquely identifies an application at the destination signaling point. SCCP provides the transport layer for [[TCAP]]-based services within the [[OSI model]]. |
The schematic on the right show how SCCP fits into the OSI model. | The schematic on the right show how SCCP fits into the OSI model. | ||
| Line 19: | Line 19: | ||
== TelcoBridges and SCCP == | == TelcoBridges and SCCP == | ||
TelcoBridges supports SCCP as part of its SS7 signaling stack. | TelcoBridges supports SCCP as part of its SS7 signaling stack. | ||
| + | |||
| + | |||
| + | |||
| + | == Related actions == | ||
| + | '''Refer to the appropriate Toolpack release:''' | ||
| + | *[[Toolpack:Protocol_Stack_Settings_D#SCCP-TCAP|SCCP and TCAP Configuration Version 3.0]] | ||
| + | *[[Toolpack:Protocol_Stack_Settings_C#SCCP-TCAP|SCCP and TCAP Configuration Version 2.10]] | ||
| + | *[[Toolpack:Protocol_Stack_Settings_B#SCCP-TCAP|SCCP and TCAP Configuration Version 2.9]] | ||
| + | *[[Toolpack:Protocol_Stack_Settings_A#SCCP-TCAP|SCCP and TCAP Configuration Version 2.8]] | ||
| + | <div class="mw-collapsible mw-collapsed" data-collapsetext="other versions" data-expandtext="Click here for other versions" style="width: 400px;"> | ||
| + | *[[Web_Portal_Tutorial_Guide_v2.7#SCCP-TCAP|Web Portal v2.7: TCAP and SCCP Configuration]] | ||
| + | *[[Web_Portal_Tutorial_Guide_v2.6#SCCP-TCAP|Web Portal v2.6: TCAP and SCCP Configuration]] | ||
| + | *[[Web_Portal_Tutorial_Guide_v2.5#Configuring_SS7|Toolpack v2.5: SS7 Signaling : SCCP Configuration steps]] | ||
| + | *[[Web_Portal_Tutorial_Guide_v2.3#SS7_Signaling|Toolpack v2.3: SS7 Signaling : SCCP Configuration steps]] | ||
| + | </div> | ||
| + | |||
| + | == References == | ||
| + | *[http://en.wikipedia.org/wiki/Signalling_Connection_Control_Part Wikipedia article] | ||
| + | *[[SCCP:Specification|Supported standards and variants]] | ||
| + | *[[SCCP:Architecture|Software Architecture]] | ||
| + | *[[Web_Portal_Tutorial_Guide_v2.5#Configuring_SS7|WebPortal Configuration steps]] | ||
| + | *[[SCCP/API:Configuration|API Configuration steps]] | ||
| + | *[[SCCP/API:Alarms|API Alarms]] | ||
| + | *[[SCCP/API:States|API States]] | ||
| + | *[[SCCP/API:Statistics|API Statistics]] | ||
[[category:Glossary]] | [[category:Glossary]] | ||
Latest revision as of 10:49, 20 February 2018
The Signaling Connection Control Part (SCCP) layer provides connectionless network services and an address translation mechanism, called global title translation (GTT), capability above MTP3. A global title can translate a string of digits (e.g., a dialled 800 number, calling card number, or mobile subscriber identification number) into a destination point code and/or subsystem number. A subsystem number uniquely identifies an application at the destination signaling point. SCCP provides the transport layer for TCAP-based services within the OSI model.
The schematic on the right show how SCCP fits into the OSI model.
Contents |
Features
SCCP supports the following features:
- Routing and translation functions.
- Management functions.
- Transfer of data without logical signaling connections.
The SCCP software supports two classes of service, in connectionless mode:
- Class 0: Basic connectionless class.
- Class 1: Sequenced connectionless class.
TelcoBridges and SCCP
TelcoBridges supports SCCP as part of its SS7 signaling stack.
Related actions
Refer to the appropriate Toolpack release:
- SCCP and TCAP Configuration Version 3.0
- SCCP and TCAP Configuration Version 2.10
- SCCP and TCAP Configuration Version 2.9
- SCCP and TCAP Configuration Version 2.8
