SCCP
(→References) |
(→References) |
||
| Line 31: | Line 31: | ||
*[[SCCP:Specification|Supported standards and variants]] | *[[SCCP:Specification|Supported standards and variants]] | ||
*[[SCCP:Architecture|Software Architecture]] | *[[SCCP:Architecture|Software Architecture]] | ||
| + | *[[Web_Portal_Tutorial_Guide_v2.5#Configuring_SS7|WebPortal Configuration steps]] | ||
*[[SCCP/API:Configuration|API Configuration steps]] | *[[SCCP/API:Configuration|API Configuration steps]] | ||
*[[SCCP/API:Alarms|API Alarms]] | *[[SCCP/API:Alarms|API Alarms]] | ||
Revision as of 13:28, 2 May 2012
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:
