SCCP

The SCCP object is a child of the SCCPs object.

The SCCP object contains all of the configuration that is used to allow the TCAP applications to exchange information for a local signaling point in the MetaSwitch NE. In general you will create an SCCP object corresponding to each Signaling Gateway for which SCCP and TCAP function is required.


A TCAP Service Logic Host Route (SLHR) can access any SCCP that has a Local SCCP Access Point object with an SSN ID matching the SLHR's SSN ID. To ensure that the configuration operates correctly when adding SCCP configuration, the Local SCCP Access Point should be the last child object you add to the SCCP (after creating all the other SCCP child objects). This ensures that an existing SLHR cannot attempt to access the SCCP while its configuration is incomplete.


Parameter

Access

Description
Signaling Gateway Change The Signaling Gateway on the NE to which this SCCP corresponds. Select from the drop-down list of Signaling Gateways that are not already associated with an SCCP.
SCCP name Change The name of the SCCP family.
Remote Concerned Area to notify of events Change The SCCP Remote Concerned Area, if any, to be notified when the status of this SCCP changes. Select the appropriate Remote Concerned Area object from the displayed list, or select None. When you first create the SCCP object, this field must be set to None because the Remote Concerned Area is a child of the SCCP and so has not yet been created. After creating a Remote Concerned Area object, you can return to this field and select it.
Initial SST message timer Change This is the initial value of the SST Message Timer. This timer is started when the NE first sends a subsystem-status test (SST) message to a remote SP. If the timer pops before a response is received, the NE starts the timer again using the larger value Maximum SST message timer. This use of two timers allows the NE to send out a couple of test messages quickly, and then move to a more occasional test message. The NE sends a SST periodically to a remote subsystem if it is reported as inactive, until it is reported as active. It is reported as active by a subsystem-available (SSA) message. Range: 5 - 10. The default is 8.
Maximum SST message timer Change Maximum value of the SST Message Timer. This timer is run after an initial subsystem status test times out. It is longer than the initial timer. Range: 600 - 1200. The default is 600.
Initial SCLC reassembly timer Change Initial value of the SCLC reassembly timer. The NE starts this timer when it begins a reassembly, and stops it when the reassembly ends. If the timer expires and the reassembly is not complete, the NE cancels the reassembly and discards the partial message. The NE also uses this timer for segmentations, and cancels any segmentation if it is not able to acquire a buffer in this period. Range: 10 - 20. The default is 10.
SCLC SSN congestion timer Change Initial value of the SCLC SSN congestion timer. If a local application is congested for this period of time, then SCCP removes the application from service until the congestion clears. Range: 1000 - 5000. The default is 2000.
Segmentation in octets - lower limit Change Lower limit for segmentation in octets. If the length of user data is less than this, then the NE does not attempt to segment the message. This value must not be greater than Segmentation in octets - upper limit. Do not change this value without a good knowledge of the SS7 network. Setting a value that is too high will cause MTP3 to discard messages, while setting a value that is too low can cause excessive segmentation, leading to increased network load. Range: 160 - 254. The default is 170.
Segmentation in octets - upper limit Change Upper limit for segmentation in octets. If the length of user data is greater than this, then the NE segments the message. If the length is less than this but not less than Segmentation in octets - lower limit, then the NE may segment the message. This value must not be less than Segmentation in octets - lower limit. Be careful when changing this value. Setting a value which does not match the specifics of the SS7 network could cause messages to be lost, or network load to be increased. Range: 160 - 254. The default is 220.
Maximum user data size accepted from TCAP Read only The maximum user data size which the NE will accept from TCAP. This value is not configurable. Value: 3952 bytes.
Maximum single message data length support for MTP3 Read only The maximum data length supported on a single message. The default is 272.
Deactivation mode Change Specifies how child objects should be deactivated when deactivating this object. Values:
  • Normal (default)
    Shut down child objects normally before deactivating the object.
  • Quiesce
    Deactivating the SCCP object in quiesce mode will wait for all existing child objects using the object to be completed before deactivation. No new child objects using the SCCP object will be accepted during this deactivation period.
  • Abort
    Deactivate the object and all its child objects immediately. (This may result in errors at remote systems.)
Alarm state Read only Specifies whether any alarms are currently raised for this object. Values:
  • Clear
    No alarms are currently raised.
  • Attention Required
    Attention Required - the object is not operating normally, and needs operator intervention.
  • Attend To Dependent
    Attention Required elsewhere - another object on which this object depends is not operating normally.
Alarm log correlator - Attention Required Read only Identifier of the log message for the event that caused the last Attention Required alarm state for this object. This field is reset when Attention Required alarm events is reset to zero.
Attention Required alarm events Read only / Reset Number of times (since the alarm count was reset) that this object's alarm state has gone to Attention Required.
Alarm log correlator - Attend To Dependent Read only Identifier of the log message for the event that caused the last Attend To Dependent alarm state for this object. This field is reset when the Attend To Dependent alarm events field is reset to zero.
Attend To Dependent alarm events Read only / Reset Number of times (since this field was reset) that this object's alarm state has gone to Attend To Dependent.
Alarm state changed timestamp Read only The time at which the Alarm state last changed.
Alarm events reset timestamp Read only The time at which the Attention Required alarm events was last reset to zero.
Child Attention Required alarms Read only The total number of child objects of this object that are in Attention Required state.
Child Attention Required alarm events Read only / Reset The total number of times that the alarm state for a child object has gone to Attention Required.
Child Attend To Dependent alarms Read only The total number of children of this object that are in Attend To Dependent state.
Child Attend To Dependent alarm events Read only / Reset The total number of times that the alarm state for a child object has gone to Attend To Dependent.
Summary child alarm state Read only Summarizes the alarm status for all children of this object. Values:
  • Clear
    No alarms are currently raised.
  • Attention Required
    Attention Required - one or more child objects are not operating normally, and need operator intervention.
  • Attend To Dependent
    Attention Required elsewhere - another object on which one or more child objects depend is not operating normally.
Requested status Read only Specifies whether an administrator has attempted to activate the SCCP. Values:
  • Active
    The object has been activated.
  • Inactive
    The object has not been activated or has been deactivated.
  • Disabled
    The object has been disabled.
Actual status Read only Specifies the current status of the SCCP. Values:
  • Active
    The object is active.
  • Activating
    Activation is in progress.
  • Deactivating
    Deactivation is in progress.
  • Inactive
    The object is inactive.
  • Disabled
    The object has been disabled.
  • Activation Failed
    The object is inactive because an activation attempt has failed.
  • Failed
    The object was active but has failed.
  • Quiescing
    The object is preparing for normal deactivation. It is operating normally but will not accept any new users.
  • Waiting For Parent
    The object cannot be used because its parent object is not yet active.
  • Parent Failed
    The object cannot be used because its parent object has failed.