In this section:
This application is only supported on the DSC Platforms. To view which applications apply to the SP2000, refer to SP2000 Supported Applications.
The license-dependent Number Portability Gateway (also referred to as NP Gateway or NPGW) utilizes the DSC Platforms and the Ribbon Policy Server (PSX) to enable Local NP of Triggerless Integrated Services Digital Network (ISDN) User Part (ISUP) messages.
In this document DSC Platforms refer to the DSC 8000 and DSC SWe with KVM or VMWare hypervisors.
The NP Gateway registers an Application ID based on its defined PSX NP Service. The GWST Redirect to AppID table must be provisioned with an associated EPR. The necessary GWST screening tables required to intercept the relevant ISUP IAMs must be provisioned to reach this Redirect to AppID EPR; these must include the following:
Additional screening on the routing label OPC and DPC are optional based on the customer deployment. For more information about using the GWST screening tables for configuring the NPGW, see Configuring the GWST Routing Tables (Example).
Consider the following for this feature:
The Gateway Redirection (GWR) and necessary SS7 and/or IP link licensing are required to enable traffic.
The NP Gateway is a fully distributed application for n-peer deployments, where n>=2.
The NP Gateway supports IPv4 and IPv6 for PSX connectivity.
The Process Event feature that appears in the UI, but is not described in this guide, provides an alarm type which ensures that the applications in all slots function as expected. With this feature, each application defines its own concept of functioning as expected, which means that the configuration/database files are synchronized and loaded, inter-peer connections are correctly established, and the peer applications are ready to process traffic. For more information about this feature, see the appropriate section in the DSC - SP2000 Platform Manager User Guide
In accordance with GR-82-Core, Signaling Transfer Point (STP) Generic Requirements (A Module of FR-CCS-18), Issue 10, December 2006, the DSC Platform supports Memory Space Accounting (MSA). For more information about how this feature applies to NPGW, see the appropriate section in the DSC - SP2000 Platform Manager User Guide.
The NP Gateway supports at least 10K messages per second for each Routing CPU.
For recommended PSX performance requirements, see the appropriate document in the PSX Documentation Library.
This section presents you with some concepts that you should be familiar with to fully understand how to configure the DSC and PSX systems using the DSC Web User Interface (UI). For more information about this UI, see Web UI and Menu UI Guide.
PSX object is a collection of PSX Hosts that can process local number portability queries.
PSX Host objects are the individual systems within a PSX deployment. In some network configurations a PSX system may have multiple local IP addresses and the DSC may connect to this PSX on each of its IP addresses. In this case, the PSX system may be represented in the DSC Web UI by multiple PSX Host objects, one for each IP address and related port to which the DSC should connect.
PSX Host Connection is a connection between a DSC Slot and a PSX Host. A DSC consists of multiple logical slots, each behaving as a separate computer. A DSC connects to a PSX Host from each slot.
GWS and MSU Tracing is the name of the gateway screening (GWS) function in the DSC Web UI. This application performs an enhanced gateway screening function that also allows for enhanced routing using Application IDs. The GWS function is applied to MSUs as part of MTP3 processing.
NP Gateway process receives ISUP IAM messages from MTP3 (based on GWS Application ID routing) and queries a PSX to resolve Number Portability handling.
For more information about the NP Gateway, see the following references.