In this section:
Note
The following section is only applicable to the DSC Platform.
Provisioning Tasks Overview
This section provides a high-level overview about provisioning DSC and PSX to support the NPGW Triggerless ISUP functionality.
Unless otherwise specified, the content of this section applies to both the DSC 8000 and the DSC SWe.
It is recommended that you execute the configuration tasks in the same order as they are described in this section.
Decide which DSC IP network you want to use to connect the DSC slots to the PSX Host
It is recommended that the Routing IP network is configured for this task. For detailed information about configuring this network, see the following:
- DSC 8000 (Configuring Ethernet Interfaces for IP Routing on DSC 8000)
- DSC SWe with a KVM or a VMware hypervisor (Configuring Ethernet Interfaces for IP Routing on DSC SWe)
Construct an IP plan and define the Gateway Name
Plan your IP address allocations and routing for both the DSC slots and the PSX Hosts. This plan should be such that a single failure of either a DSC slot, a PSX Host, or any switch or router in between does not cause more than 50% of the traffic to be affected. For examples of these configurations, refer to Network Topology and Redundancy.
The DSC and PSX communicate over the Ribbon proprietary protocol Diameter Plus (Diameter+) that runs over User Datagram Protocol (UDP). Any network firewall must be configured such that it allows the UDP traffic between each DSC slot and the PSX. Specifically, the DSC firewall requires a module to allow access to the PSX UDP Port. For information about firewall configuration, refer to Firewall Configuration.
The UDP Port in question is configurable on the PSX. Each DSC slot registers with each PSX Host using a string known as the Gateway Name. The gateway names for each DSC slot must be configured on the PSX and DSC. For some recommended configurations of IP addresses and Gateway Names, refer to Network Topology and Redundancy.
Implement the IP Plan, including the routing rules, firewall rules, and so on
Use the appropriate user guide in the Documentation Library to implement your IP plan using the Web User Interface (UI).
Provision the PSX
To provision the PSX, you have to configure all the allowed Gateway Names and all aspects of call processing. When using the PSX with a DSC for this feature, congestion management should be enabled. For more information about provisioning the PSX, see the appropriate user guide in the PSX Documentation Library.Configure the NP Gateway
Configure the NP Gateway as described on this page.Configure Gateway Screening
Configure the appropriate gateway screening tables to send IAM Messages to the NP Gateway. For an example configuration of the Gateway Screening tables, see Configuring the GWST Routing Tables (Example).
When this configuration is completed, if your MTP3 links are aligned, your system should be sending IAM messages to the PSX for Triggerless ISUP handling.
Configuring NPGW System-wide Attributes
You can use the NPGW General Configuration screen to configure system-wide attributes and the Debug Configuration screen to configure system-wide logging.
To configure NPGW system-wide attributes
To configure NPGW system-wide logging
To activate or deactivate NPGW traffic
Configuring an NPGW MTP3 NA
The NPGW MTP3 NA object represents the SS7 connectivity to an MTP3 Network Appearance (NA).
The NPGW MTP3 NA Connection object represents the SS7 connectivity to an MTP3 NA on a per slot basis (see To view an NPGW MTP3 NA Connection).
Before you can create the NPGW MTP3 NA, this NA must be created at MTP3 (refer to To create an NA).
To create an NPGW MTP3 NA
To view an NPGW MTP3 NA
To activate or deactivate traffic on an NPGW MTP3 NA
To view an NPGW MTP3 NA connection
Configuring an MTP3 Registration
The MTP3 Registration object is used to intercept the NPGW SS7 related traffic on the configured NPGW MTP3 NA(s) for a given Application ID.
GWST redirection must be licensed to allow traffic redirection using an App ID.
For more information about Application IDs, refer to Reserved Application IDs for SS7 Applications.
MTP3 Registration objects are automatically created for every NPGW MTP3 NA based on the PSX NP Service.
To view an MTP3 Registration
When the MTP3 NA is CONNECTED and the PSX associated with the PSX NP Service is CONNECTED, the NPGW process registers with MTP3 to receive traffic for the provisioned Application ID (traffic will not arrive to the NPGW until the Application ID is also provisioned in GWST). Under the MTP3 Registrations tab, the NA and Application ID should show a Status of REGISTERED.
Configuring a PSX
The PSX object represent the connectivity information for a given PSX group of Hosts. Each PSX is uniquely identified by its Name.
After you created and configured the PSX and PSX Host objects, you have to activate the PSX and the PSX Host (see Provisioning the NP Gateway#To activate or deactivate a PSX and To activate or deactivate a PSX Host, respectively).
To create a PSX
To activate or deactivate a PSX
Configuring a PSX Host
The PSX Host object represent the connectivity information for a given PSX. Each PSX Host is uniquely identified by its Host and Port.
A maximum of 16 PSX Host objects are supported.
After you created and configured the PSX and PSX Host objects, you have to activate the PSX and the PSX Host (see 325022120 and To activate or deactivate a PSX Host, respectively).
To create a PSX Host
To activate or deactivate a PSX Host
Configuring a PSX Host Connection
The PSX Host object represent the connectivity information for a given PSX. Each PSX Host is uniquely identified by its Host and Port.
If you created a PSX Host object (see 325022120), the DSC automatically creates one PSX Host Connection object for each logical DSC slot, to represent the connection between the logical DSC slot and the configured PSX Host. The Gateway Name actually used for registration with the PSX is the Gateway Name from the PSX Host followed by the logical slot number from which the connection originates.
To view a PSX Host Connection
Configuring PSX NP Service
The PSX NP Service object represent the Number Portability database information for a given PSX. Each PSX NP Service is uniquely identified by its Application ID attribute.
A maximum of 8 PSX NP Services are supported.
To create a PSX NP Service
To configure a PSX NP Service
Overview
Content Tools