Caution

It is your responsibility to ensure that no circular routing is generated. Because the DPC is typically not modified, SS7 traffic management is not enforced for the redirected MSUs.

The GWST default screening behavior is to either allow or discard MSUs. The Gateway Redirection (GWR) is a licensed feature to redirect MSUs to a local Ribbon application or remote SS7 destination. This feature provides for a more flexible routing mechanism for the DSC - SP2000 Platform.

Note

The GWR feature has reserved Application IDs. For more information, refer to Reserved Application IDs for SS7 Applications.

The traffic may be redirected to a PC or to an Application ID. The Signaling Gateway (SG) correlates between M3UA and SUA context registration and Application ID registration. Application ID registrations are preformed on all MTP3/SCCP processes.

The Application ID name is defined by a 16 character string which includes the null character. Case insensitive alphanumeric characters, dashes, and underscores are supported.

The redirection tables can define up to four PC or application ID records (see the following figure) per EPR with a cost. Load sharing can be defined by setting identical costs. MTP3 sends the MSU to the lowest cost available Application ID or PC.

Note

On a redirect to PC, the DPC is not modified by default. The redirection PC is only used to determine the outgoing linkset.

Redirect to App ID Configuration (Example)

Traffic redirection only applies to MSUs with SI > = 3. SNM and SLT messages (SI 0 to 2) are processed normally even if redirection is selected. Traffic PC redirection is only  implemented for through traffic. An MSU with a local DPC (LPC or VNode) redirecting to any PC is treated as a successful screening and is handled locally.

 

  • No labels