In this section:
User Connection
The User Connections object displays the SCCP user connections on all the SCCP peers. An SCCP Process supports multiple user connections. Each user connection manages its associated Registered PC subsystem number (SSN) and Registered User AppID objects for traffic interception. Duplicate PC SSNs and AppIDs cannot be registered on the same SCCP Process.
Note
The SCCP application has reserved Application IDs. For more information, refer to Reserved Application IDs for SS7 Applications.
The SCCP AppID Loadshare Registration feature allows multiple users to register the same AppID on a given SCCP peer. Traffic destined for a load share-based registration is shared between the local user connections using a round-robin implementation. For more information, see Viewing Registered User AppIDs.
Most configuration tasks and management of the user connections are preformed using the SG UI. The User Connection objects in the SCCP UI are only used for informational and troubleshooting purposes.
You can terminate SCCP traffic between a user application and SCCP by using the Terminate action if required. Using this action forces the closure of the IP connection. Because SG and other Ribbon applications always attempt to re-register, automatic re-establishment of this connection is the default behavior.
To view a User connection
To terminate a User connection
Viewing Registered PC SSNs
The Registered PC SSN objects are used to view what PC and SSN combinations are registered by the user applications. These PCs must be provisioned as VNodes at MTP3, unless the PC is the LPC of that NA (refer to the appropriate section in the SS7 Application Guide 1).
Similar to the user connections, the Registered PC SSN objects are only used for informational and troubleshooting purposes.
Note
If an SS7 subsystem status test (SST) message is received concerning a Registered PC SSN, a Subsystem Available (SSA) message is returned for the given SSN.
An SS7 Transfer Allowed (TFA) message is sent on the network regarding this Registered PC when the PC is successfully registered with MTP3.
To view a Registered PC SSN
Viewing Registered User AppIDs
The Registered AppID objects are used to view what Application IDs are registered by the user applications. For example, the SUA Application Server at the SG can register with the SCCP either with a PC-SSN or an Application ID (refer to To create an SUA Application Server).
As mentioned in the overview of this section, SCCP AppID Loadshare Registration feature allows multiple users to register the same AppID on a given SCCP Process. If this feature is enabled, it is the responsibility of the applications to handle the traffic message sequencing. The features should only be enabled for connectionless traffic.
The AppID registration request message contains an optional Registration Mode parameter that is used to determine the registration mode for the given application ID.
The Registration Mode can be set to either UNIQUE or LOADSHARE. If the parameter is not present, the Registration Mode is set to UNIQUE by default.
Similar to the user connections, the Registered User App ID objects are only used for informational and troubleshooting purposes.
To view a Registered User AppID
Overview
Content Tools