SCCP
(→Related actions) |
(clean up) |
||
| Line 33: | Line 33: | ||
== 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:Architecture|Architecture]] | + | *[[SCCP:Architecture|Architecture]] |
| − | + | *[[SCCP:Configuration|Configuration steps]] | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
*[[SCCP:Specification|Supported standards and variants]] | *[[SCCP:Specification|Supported standards and variants]] | ||
*[[SCCP:Alarms|Alarms]] | *[[SCCP:Alarms|Alarms]] | ||
Revision as of 12:06, 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.
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
- Create a SCCP stack
- Create a SCCP network
- Create a SCCP LSAP
- Create a SCCP route
- [[Toolpack:Create a SCCP userpart|Create a SCCP userpart]
- Configure GTT Association(s)
- Configure GTT Address Map(s)
