SCCP
(→Related actions) |
(→References) |
||
| Line 29: | Line 29: | ||
== References == | == References == | ||
*[http://en.wikipedia.org/wiki/Signalling_Connection_Control_Part Wikipedia article] | *[http://en.wikipedia.org/wiki/Signalling_Connection_Control_Part Wikipedia article] | ||
| − | |||
| − | |||
*[[SCCP:Specification|Supported standards and variants]] | *[[SCCP:Specification|Supported standards and variants]] | ||
| − | *[[SCCP:Alarms|Alarms]] | + | *[[SCCP:Architecture|Software Architecture]] |
| − | *[[SCCP:States|States]] | + | *[[SCCP/API:Configuration|API Configuration steps]] |
| − | *[[SCCP:Statistics|Statistics]] | + | *[[SCCP/API:Alarms|API Alarms]] |
| + | *[[SCCP/API:States|API States]] | ||
| + | *[[SCCP/API:Statistics|API Statistics]] | ||
[[category:Glossary]] | [[category:Glossary]] | ||
Revision as of 11:46, 1 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:
