1. Virtual Signaling Transfer Point User Guide
  2. GUI Configurations
  3. Configuration
  4. SCCP Map Sets

5.1.17 SCCP Map Sets

A Mated Application Part (MAP) Set is a logical grouping of Remote Signaling Points (/vstp/remotesignalingpoints) referred to as a load sharing group. The Default MAP Set (the MAP Set with mapSetId equal to 0) can have multiple load sharing groups. All other MAP Sets can have only one load sharing group associated with them. A load sharing group can have at most 32 RSPs.

Select the VSTP, and then Configuration, and then SCCP Map Sets page. The page displays the fields on the SCCP Map Sets View, Insert, and Edit pages.

Note:

Data Input Notes apply to the Insert and Edit pages only; the View page is read-only.

Table 5-17 SCCP Map Sets Fields

Fields Description Data Input Notes
Map Set Id Id of this Map Set must be unique across MAP Sets. If a mate RSP is being added to an existing MAP Set, the mapSetId must be the same as assigned to the MAP Set instance containing the primary RSP.

This is a mandatory field.

Range = 1,36000
RSP Name Defines the Remote Signaling Point name associated with this MAP Set.

This is a mandatory field.

SSN Defines the application's subsystem number.

This is a mandatory field.

Range 2,255
Relative Cost Defines the relative cost of the route for the RSP of this MAP Set. For the primary RSP, the default value is 10 and for a mate RSP the default value is 50.

This is a mandatory field.

Range 0,99
Weight Defines the weight assigned to the primary RSP of this MAP Set. Weight is not applicable for solitary and dominant modes. Weight is only valid for load sharing mode and its default is 1. Range 1,99
Threshold Defines the in-service threshold assigned to each combination of RSP and SSN in this MAP Set having the same relativeCost. The Weighted GTT Loadsharing feature must be enabled (using the GTT Feature Control before this parameter can be specified. If this parameter is not specified, a value of 1% is assigned to each RSP in this MAP Set. Range 1,100
Message Route Congest Must be set to Yes if the Class 0 messages to the specified RSP can be routed to the next preferred node/subsystem when that RSP is congested. No otherwise. If domain of RSP is ANSI, Default is equivalent to Yes. If domain of RSP is ITU, Defalut is equivalent to No. If not specified by user the value for messageRouteCongestion is set to Default.
Sub System Routing Message Must be set to Yes if the subsystem routing messages (SBR, SNR) are transmitted between the mated applications, No otherwise. If domain of RSP is ANSI, Default is equivalent to Yes. If domain of RSP is ITU, Defalut is equivalent to No. If not specified by user the value for subsystemRoutingMessage is set to Default.
Sub System Status Option Must be set to Yes if the RSP specified by rspName initiates a subsystem test when a RESUME message is received, No otherwise. Default is equivalent to No. If not specified by user the value for subsystemStatusOption is set to Default.

You can perform add, edit, or delete tasks on VSTP>Configuration>SCCP Map Sets page.

Adding a SCCP Map Set

Perform the following steps to configure a new SCCP Map Set:

  1. Click Insert.

    Note:

    The combination of mapSetId, rspName and ssn must be unique across all MAP Set entries at the SOAM.
  2. Enter the applicable values.
  3. Click OK, Apply, or Cancel

Editing a SCCP Map Set

Use this procedure to change the field values for a selected SCCP Map Set. (The SCCP Map Set Name field cannot be changed.):
  1. Select the SCCP Map Set row to be edited.
  2. Click Edit
  3. Enter the updated values.
  4. Click OK, Apply, or Cancel

Deleting a SCCP Map Set

Use the following procedure to delete a SCCP Map Set.

Note:

If only one RSP is associated with the MAP Set, it is deleted and the groupId and mapSetId assigned to this MAP Set becomes available to configure a new MAP Set.
  1. Select the SCCP Map Set to be deleted.
  2. Click Delete.
  3. Click OK or Cancel.
Map Set Id* Id of this Map Set must be unique across MAP Sets. If a mate RSP is being added to an existing MAP Set, the mapSetId must be the same as assigned to the MAP Set instance containing the primary RSP. Range 1,36000 A value is required.
RSP Name* Defines the Remote Signaling Point name associated with this MAP Set. A value is required.
SSN* Defines the application's subsystem number.Range 2,255 A value is required.
Relative Cost* Defines the relative cost of the route for the RSP of this MAP Set. For the primary RSP, the default value is 10 and for a mate RSP the default value is 50. Range 0,99 A value is required.
Weight Defines the weight assigned to the primary RSP of this MAP Set. Weight is not applicable for solitary and dominant modes. Weight is only valid for load sharing mode and its default is 1. Range 1,99
Threshold Defines the in-service threshold assigned to each combination of RSP and SSN in this MAP Set having the same relativeCost. The Weighted GTT Loadsharing feature must be enabled (using the GTT Feature Control before this parameter can be specified. If this parameter is not specified, a value of 1% is assigned to each RSP in this MAP Set. Range 1,100
Message Route Congest Must be set to Yes if the Class 0 messages to the specified RSP can be routed to the next preferred node/subsystem when that RSP is congested. No otherwise. If domain of RSP is ANSI, Default is equivalent to Yes. If domain of RSP is ITU, Defalut is equivalent to No. If not specified by user the value for messageRouteCongestion is set to Default.This attribute is NOT currently in use. Will be used in future..
Sub System Routing Message Must be set to Yes if the subsystem routing messages (SBR, SNR) are transmitted between the mated applications, No otherwise. If domain of RSP is ANSI, Default is equivalent to Yes. If domain of RSP is ITU, Defalut is equivalent to No. If not specified by user the value for subsystemRoutingMessage is set to Default.This attribute is NOT currently in use. Will be used in future.
Sub System Status Option Must be set to Yes if the RSP specified by rspName initiates a subsystem test when a RESUME message is received, No otherwise. Default is equivalent to No. If not specified by user the value for subsystemStatusOption is set to Default.This attribute is NOT currently in use. Will be used in future.