In this section:

Related articles:

This section provides information about routeset types, which you should review before configuring routesets.

Routeset Types

 When routing an MSU to the SS7 network, the DSC - SP2000 Platform looks in its routesets for the best match to the MSU’s Destination Point Code (DPC). The “best match” means that routesets are considered from the most specific to least specific routeset as shown in the following list:

  1. Member routeset (most specific)
  2. Cluster routeset
  3. Network routeset
  4. Default routeset (least specific)

When the best match is found, the associated routeset is used to select the outgoing link for the MSU. If there is no match, the destination is unavailable and the MSU is discarded.

Member, Cluster, and Network Routesets

Routesets have a destination to a specific node with point codes such as 1.2.3 for member routesets, 1.2.* for cluster routesets, and 1.*.* for network routesets. These routeset types do not require that a destination signaling point be directly connected to the originating node, but this signaling point can be several hops away. The node routes the message using the lowest cost starting point.

Default Routesets

Default routesets have a destination to any node. When configuring default routing, you do not have to specify a destination point code. Any message addressed to a location that has not been specified at the member, cluster, or network levels is routed by the default routeset, if one exists.

Exception Routesets

Exception routesets are created when an adjacent node sends a Transfer Prohibited (TFP), a Transfer Restricted (TFR), or a Transfer Controlled (TFC) message to the DSC - SP2000 Platform, concerning a PC which has no member routeset and which is normally accessible through a cluster, network, or default routeset. Exception routesets may also be created if the DSC - SP2000 Platform receives a Transfer Cluster Prohibited (TCP) or Transfer Cluster Restricted (TCR) message from an adjacent node.

These temporary routesets are automatically populated with routes using the same attributes as those already defined in the cluster/network/default routeset and behave as if they are user-defined. If all adjacent nodes defined in the routeset prohibit the point code, the DSC - SP2000 marks the destination as prohibited and invokes the appropriate procedures.

You can see these temporary routesets and routes appear and then disappear from the appropriate screens on the user interface as the system generates and then removes them as required. Exception routesets and their routes are removed from the system when the adjacent node(s) clear all routing restricted conditions for a particular destination.


  • No labels