SCCP managament: Difference between revisions
(Created page with "SCCP management maintains the status of remote and local SubSystem and SCCP signaling points. It interacts with the SCCP Routing Control (SCRC) to ensure proper routin...") |
No edit summary |
||
| Line 1: | Line 1: | ||
SCCP management maintains the status of remote and local SubSystem and SCCP [[SP|signaling points]]. It interacts with the SCCP Routing Control (SCRC) to ensure proper routing of SCCP traffic. If a remote SubSystem ([[SSN]]) or [[SP|signaling point]] ([[DPC]]) is known to be inaccessible, alternative route will be used. | SCCP management maintains the status of remote and local SubSystem and SCCP [[SP|signaling points]]. It interacts with the SCCP Routing Control (SCRC) to ensure proper routing of SCCP traffic. If a remote SubSystem ([[SSN]]) or [[SP|signaling point]] ([[DPC]]) is known to be inaccessible, alternative route will be used. | ||
The SCCP management uses the concept of [[Parameter: SCCP Concerned Point Code| "Concerned Point Code"]] in order to send/forward immediate notification on status changes of affected SubSystem/[SP|signaling point]]. | The SCCP management uses the concept of [[Parameter: SCCP Concerned Point Code| "Concerned Point Code"]] in order to send/forward immediate notification on status changes of affected SubSystem/[[SP|signaling point]]. | ||
Latest revision as of 14:20, 17 May 2012
SCCP management maintains the status of remote and local SubSystem and SCCP signaling points. It interacts with the SCCP Routing Control (SCRC) to ensure proper routing of SCCP traffic. If a remote SubSystem (SSN) or signaling point (DPC) is known to be inaccessible, alternative route will be used.
The SCCP management uses the concept of "Concerned Point Code" in order to send/forward immediate notification on status changes of affected SubSystem/signaling point.