SCCP: Difference between revisions
(added references) |
(added links) |
||
| 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 == | |||
=== SCCP === | |||
*[[SCCP:Configuration|SCCP Configuration]] | |||
**[[Toolpack:Create a SCCP stack|General Configuration]] | |||
**[[Toolpack:Create a SCCP network|Network Configuration]] | |||
**[[Toolpack:Create a SCCP LSAP|LSAP Configuration]] | |||
**[[Toolpack:Create a SCCP route|Route Configuration]] | |||
**[[Toolpack:Create a SCCP userpart|Userpart Configuration]] | |||
**[[SCCP:GTT Association Configuration|GTT Association Configuration]] | |||
**[[SCCP:GTT Address Map Configuration|GTT Address Map Configuration]] | |||
== 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 | *[[SCCP:Architecture|Architecture]] (NEED TO REVISE GRAPHIC) | ||
**[[SCCP:Connectionless Service|Connectionless Service]] | |||
**[[SCCP:Management|Management]] | |||
**[[SCCP:Addressing|Addressing]] | |||
**[[SCCP:Global Title Translation Association|Global Title Translation Association]] | |||
**[[SCCP:Routing|Routing]] | |||
**[[SCCP:Traffic Limitation and Congestion Control|Traffic Limitation and Congestion Control]] | |||
**[[SCCP:Interworking|Interworking]] | |||
**[[SCCP:Messages|Messages]] | |||
*[[SCCP:Specification|Supported standards and variants]] | |||
*[[SCCP:Alarms|Alarms]] | |||
*[[SCCP:States|States]] | |||
*[[SCCP:Statistics|Statistics]] | |||
[[category:Glossary]] | [[category:Glossary]] | ||
Revision as of 13:02, 10 September 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.
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
SCCP