In this section:
SCCP Management (SCMG) services and primitives are used in conjunction with Connectionless primitives to coordinate the transfer of traffic between replicated systems and reports the status of local and remote subsystems and remote point codes. The following table lists and describes the SCMG primitives. Indication, response, and confirmation messages are sent by SCCP and request messages are sent by the SCCP user application.
This primitive registers an SCCP user application with the SCCP. The DSC Platform ensures delivery of messages to the proper registered application-based on the associated application ID string.
Up to 1024 application ID registrations are supported with the DSC Platform on a single socket interface.The following table lists and describes the N-REGISTER-APPID parameters.
The N-DEREGISTER-APPID primitive deregisters an SCCP application ID from the SCCP. The following table lists and describes the N-DEREGISTER- APPID parameters.
This primitive registers an SCCP user application with the SCCP using an associated point code and subsystem number. The DSC Platform ensures delivery of messages to the proper registered application on a point code and subsystem basis.
Up to 1024 PC-SSN registrations are supported with the DSC Platform on a single socket interface. When an SCCP user application successfully registers, the corresponding SCCP procedures are initiated to broadcast the availability of the PC-SSN. The following table lists and describes the N-REGISTER-SSN parameters
In previous versions of the SCCP, the SCCP-REGISTER-USER and SCCP-REGISTER-USER-ACK parameters were used instead of the SCCP-PCSSN-KEY and SCCP-KEY-STATUS. Although these parameters are still available, the parameters are now obsolete.
This primitive deregisters an SCCP user application from the SCCP using an associated point code and subsystem number. Upon deregistration, the proper SCCP procedures are initiated to broadcast the status change of the PC-SSN. The parameters used in this message are the same as those found in the N-REGISTER-SSN message.
In previous versions of the SCCP, the SCCP-DEREGISTER-USER and SCCP-DEREGISTER-USER-ACK parameters were used instead of SCCP-PCSSN-KEY and SCCP-KEY-STATUS. Although these parameters are still available, the parameters are now obsolete.
This primitive informs an SCCP user application about the status of a signaling point. The following table lists and describes the N-PCSTATE parameters.
This primitive informs the SCCP user application about the status of a locally or remotely affected user. The following table lists and describes the N-STATE parameters.
This primitive coordinates the transfer of traffic between replicated systems in the event of failures. The following table lists and describes the N-COORD parameters.
Request and response are currently not supported.
This primitive identifies the version of the interface used. The following table lists and describes the N-VERSION parameter.
This primitive identifies the MTP3 NA Configuration options. The following table lists and describes the N-MTP3-NA-CONFIGURATION parameters.
This primitive identifies the connection setup options. The following table lists and describes the N-CONNECTION-SETUP parameter.Should be sent as soon as the connection is established.
SCCP supports reassembly by default so this message is only required to disable the feature.