SCCP
(clean up) |
(→Related actions) |
||
Line 23: | Line 23: | ||
== Related actions == | == Related actions == | ||
− | + | '''Refer to the appropriate Toolpack release:''' | |
− | *[[ | + | *[[Web_Portal_Tutorial_Guide_v2.2#SS7_Signaling|Toolpack v2.2: SS7 Signaling]] |
− | + | *[[Web_Portal_Tutorial_Guide_v2.4#SS7_Signaling|Toolpack v2.4: SS7 Signaling]] | |
− | *[[ | + | |
− | + | ||
− | + | ||
− | + | ||
== References == | == References == |
Revision as of 15:26, 18 November 2009
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: