7 LNP Feature Configuration
- Triggerless LNP (TLNP)
- LRN and NPANXX Quantities on the EAGLE 5 ISS
- LNP Short Message Service (LNP SMS)
- ITU TCAP LRN Query (LRNQT)
7.1 LNP Feature Prerequisites
Before an LNP quantity feature can be enabled, the following prerequisites are required in the system:
Table 7-1 LNP Feature Prerequisites
Prerequisite | Verification and Provisioning |
---|---|
ELAP 10.0 and LSMS 12.0 or higher must be used with the EAGLE. |
Enter the Verify the LSMS and ELAP versions with your system administrator or account representative. |
All Service Module cards for LNP must be E5-SM4G cards or E5-SM8G-B cards. DSM cards are not supported. |
Enter the If any cards of TYPE DSM are listed as running the VSCCP GPL, use the Removing DSM Cards procedure to remove these DSM cards. If E5-SM4G or E5-SM8G-B Service Module cards need to be added, use the procedure Adding a Service Module in Database Administration - GTT User's Guide to add the cards. |
Oracle recommends that the ELAP is connected to the EAGLE before LNP telephone number data is loaded onto the ELAP and before the LNP telephone number quantity feature is enabled on the EAGLE. |
When the LNP telephone number quantity feature is enabled on the EAGLE, the feature access key and quantity information is sent to the ELAP, resulting in the ELAP database quantity being the same as the LNP quantity on the EAGLE. If the ELAP database quantity is larger than the LNP quantity on the EAGLE, the ELAP RTDB is not loaded onto the entire set of Service Module cards on the EAGLE. Some of the Service Module cards load the ELAP RTDB to provide a restricted level of GTT/LNP service. The remainder of the Service Module cards are put into a restricted state. UIM 1323 is generated at the EAGLE. To avoid this situation, ensure that the LNP quantity to be configured on the EAGLE in this procedure is greater than the ELAP RTDB quantity. Verify the ELAP RTDB quantity by performing the Verifying RTDB Status at the EAGLE Terminal. Verify that the LNP feature quantity to be enabled on the system is greater than the ELAP RTDB quantity. |
7.2 Triggerless LNP Feature Configuration
This procedure is used to configure the Triggerless LNP (TLNP) feature.
Prerequisites and Requirements
- Before the TLNP feature can be turned on, the LNP feature must be enabled in the system.
- The Gateway Screening feature is used to capture the IAM messages that are converted for the TLNP feature. The Gateway Screening (GWS) feature must be turned on and the database must contain a gateway screening screen set that contains the following items:
-
An allowed SIO screen that allows ISUP messages into the EAGLE. ISUP messages are MSUs that contain the value 5 in the Service Indicator field (SI=5) of the Service Information Octet (SIO) of the MSU.
-
The gateway screening stop action
tlnp
. The gateway screening stop actions can be verified with thertrv-gws-actset
command.
-
Steps in the procedure in this section refer to procedures in Database Administration - GWS User's Guide to turn on the GWS feature, and to configure Gateway Screening with the required screen set in the database.
Note:
It is recommended that the screening for ISUP messages allowed into the EAGLE stop at either the Allowed SIO, Allowed DPC, Blocked DPC, or Allowed ISUP screens. Screening on these messages can continue to the Allowed DESTFLD, Allowed CGPA, Allowed TT, Allowed CDPA, or Allowed AFTPC screens, but these screens do not contain any screenable criteria contained in an ISUP message. After these messages are passed on to the Allowed DESTFLD or Allowed CGPA screens, they will continue to be passed during the gateway screening process until the gateway screening process stops.-
The jipprv configuration option value in the LNPOPTS table is set to yes.
-
A valid Calling Party Number exists in the original IAM message.
-
jipprv
– Indicates whether on not a Jurisdiction Information Parameter value is to be added to the IAM. -
jipdigits
– The value of the Jurisdiction Information Parameter as a 6-digit number.
Canceling the RTRV-LS
Command
Because the rtrv-ls
command used in this procedure can display information for a long period of time, the rtrv-ls
command can be canceled and the output to the terminal stopped. There are three ways that the rtrv-ls
command can be canceled.
-
Press the
F9
function key on the keyboard at the terminal where thertrv-ls
command was entered. -
Enter the
canc-cmd
without thetrm
parameter at the terminal where thertrv-ls
command was entered. -
From another terminal other that the terminal where the
rtrv-ls
command was entered, enter thecanc-cmd:trm=<xx>
, where<xx>
is the terminal where thertrv-ls
command was entered. To enter thecanc-cmd:trm=<xx>
command, the terminal must allow Security Administration commands to be entered from it and the user must be allowed to enter Security Administration commands. The terminal’s permissions can be verified with thertrv-secu-trm
command. The user’s permissions can be verified with thertrv-user
orrtrv-secu-user
commands.
Refer to Commands User's Guide for a complete description of the canc-cmd
command, including parameters and valid parameter values, rules for using the command correctly, and output examples.
7.3 Configuring the Service Module Card Ethernet Link to the MPS
This procedure is used to configure the Ethernet link parameters for the Service Module cards using the chg-ip-lnk
command. The chg-ip-card
command is used to connect to the Virtual IP networks.
The chg-ip-link
command uses the following parameters.
:loc
– Card location. The location of the Service Module card.
:port
– The Ethernet interface on the Service Module card, A or B.
:ipaddr
– IP address assigned to the Ethernet interface on the Service Module card. This is an IP address expressed in standard “dot notation.” IP addresses consist of the system’s network number and the machine’s unique host number.
:submask
– The subnet mask of the IP interface. A subnet mask is an IP address with a restricted range of values. The bits in the mask must be a string of one’s followed by a string of zeros. There must be at least two one’s in the mask, and the mask cannot be all one’s. See Table 7-7 to assign the correct parameter values.
:auto
– Tells hardware whether to automatically detect the duplex
and speed
.
:mactype
– This is the Media Access Control Type of the interface.
When a Service Module card is entered into the database, these values are automatically configured in the IP Link table for both Ethernet interfaces on the Service Module. If the values are not configured as listed below, you may need to change them.
-
MACTYPE = DIX
-
AUTO = YES
-
MCAST = NO
The IPADDR and SUBMASK columns in the rtrv-ip-lnk
output are shown as dashes. Each Ethernet link assigned to the Service Module card requires the IP address and submask of the MPS. The MCAST value for both Ethernet links must be no (mcast=no). No other values need to be changed.
A zero ipaddr parameter value (0.0.0.0) indicates the Service Module card Ethernet interface to the MPS is disabled.
The Service Module card must be placed out of service.
If either the ipaddr or submask parameters are specified, then both parameters must be specified. If the ipaddr parameter value is zero (0.0.0.0), the submask parameter is not required.
The A or B interface can be used with the Service Module card.
The value of the IP address specified for the ipaddr parameter is defined as follows:
-
The first two octets of the IP address are 192.168. These are the first two octets for private class C networks as defined in RFC 1597.
-
The third octet is configured, usually to the default value .120 for the main network (port A of the Service Module card) and the default value .121 for the backup network (port B of the Service Module card). These are not visible to any external networks, and should not need to be changed.
-
The fourth octet of the address is selected as follows:
-
If the ELAP is configured as ELAP A, the fourth octet has a value of 100.
-
If the ELAP is configured as ELAP B, the fourth octet has a value of 200.
-
The submask parameter value is based upon the ipaddr
setting. See Table 7-7 for the valid input values for the submask and ipaddr parameter combinations.
Table 7-7 Valid Subnet Mask
Parameter Values
Network Class |
IP Network Address Range |
Valid Subnet Mask Values |
A |
1.0.0.0 to 127.0.0.0 |
255.0.0.0 (the default value for a class A IP address) 255.192.0.0 255.224.0.0 255.240.0.0 255.248.0.0 255.252.0.0 255.254.0.0 255.255.128.1 |
A+B |
128.1.0.0 to 191.255.0.0 |
255.255.0.0 (the default value for a class B IP address) 255.255.192.0 255.255.224.0 255.255.240.0 255.255.248.0 255.255.252.0 255.255.254.0 255.255.255.128 |
A+B+C |
192.0.0.0 to 223.255.255.0 |
255.255.255.0 (the default value for a class C IP address) 255.255.255.192 255.255.255.224 255.255.255.240 255.255.255.248 255.255.255.252 |
The chg-ip-card
command is used to provision IP networking parameters for the Service Module cards. The chg-ip-card
command supports two parameters, :bpipaddr and :bpsubmask, that are allowed only if the Service Module card is in the inhibited state. The :bpipaddr and :bpsubmask parameters are used to implement bonded ports on the Service Module cards, which allow the A and B networks to be used as a single redundant network.
:bpipaddr – Bonded Port IP address. This parameter specifies an IP address for the Service Module card.
:bpsubmask – Bonded Port IP submask. The subnet values are the same as for the chg-ip-link values, shown in Table 7-7.
The :bpsubmask parameter must be specified if :bpipaddr is specified for chg-ip-card
, and :bpipaddr must be specified or already have a valid value if a valid :bpsubmask is specified.
The :bpipaddr IP value must be unique among all IP cards and IP links.
When specifying :bpipaddr with a NULL network address, the chg-ip-card
command will reset both :bpipaddr and :bpsubmask
.
7.4 Removing DSM Cards
This procedure is used to remove DSM cards from the database, using the dlt-card
command. LNP with ELAP 9.0 or higher does not support DSM cards. Any DSM cards must be removed from the system and replaced with E5-SM4G or E5-SM8G-B cards.
Note:
When any Service Module card is removed, the hourly measurements data that has not been collected will be lost. It is important to remove these cards right after hourly collection to minimize measurements data loss.Caution:
If the DSM Service Module card is the last service module card in service, removing this card from the database will cause a Global Title Translation and Local Number Portability traffic to be lost.The examples in this procedure are used to remove the DSM card in card location 1204. Refer to Commands User's Guide for descriptions of the commands used in this procedure, including parameter names, valid parameter values, and output examples.