1. EAGLE LNP Application Processor Administration and LNP Feature Activation Guide
  2. LNP Feature Configuration

7 LNP Feature Configuration

This chapter contains the procedures used to configure the Local Number Portability (LNP) feature and the following LNP-related features.
  • 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 rept-stat-mps command to display the ELAP version.

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 rept-stat-card:type=dsm command.

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

Steps in this procedure explain how to verify that the following prerequisites and requirements are present or how to provide them in the system:
  • 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 the rtrv-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.
When the IAMs are converted, a Jurisdiction Indicator Parameter (JIP) is added to the IAM message after RTDB lookup if the Jurisdiction Information Parameter does not exist in original IAM message and either:

  • The jipprv configuration option value in the LNPOPTS table is set to yes.

  • A valid Calling Party Number exists in the original IAM message.

The following JIP configuration options can be provisioned in the LNPOPTS table after the TLNP feature has been turned on:

  • 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 the rtrv-ls command was entered.

  • Enter the canc-cmd without the trm parameter at the terminal where the rtrv-ls command was entered.

  • From another terminal other that the terminal where the rtrv-ls command was entered, enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-ls command was entered. To enter the canc-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 the rtrv-secu-trm command. The user’s permissions can be verified with the rtrv-user or rtrv-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.

  1. Display the FAK-controlled features that are enabled in the system. Enter the rtrv-ctrl-feat command.
    The LNP feature must be enabled and the ISUP NP with EPAP cannot be enabled before the TLNP feature can be turned on.
    • If the ISUP NP with EPAP feature is enabled, this procedure cannot be performed. Contact your My Oracle Support (MOS) for assistance.
    • If the LNP feature is enabled (an LNP ported TNs entry appears in the output), continue with Step 2.
    • If the LNP feature is not enabled, perform the procedures in LNP Feature Activation Procedure to enable the LNP feature and make it fully operational in the system. Then continue with Step 2.
  2. Display the status of the TLNP feature. Enter the rtrv-feat command.
    • If the TLNP feature is off (tlnp = off appears in the output), continue with Step 3.
    • If the TLNP feature is on (tlnp = on appears in the output), go to Step 5.
  3. Turn on the TLNP feature. Enter the chg-feat:tlnp=on command.

    After the TLNP feature is turned on with the chg-feat command, it cannot be turned off.

    The TLNP feature must be purchased before you turn on the feature with the chg-feat command. If you are not sure if you have purchased the TLNP feature, contact My Oracle Support (MOS).

  4. Verify the status of the TLNP feature. Enter the rtrv-feat command.
    The tlnp=on entry appears in the output when the feature is on.
  5. Display the Jurisdiction Information Parameter configuration option values in the LNPOPTS table. Enter the rtrv-lnpopts command.
    • If the Jurisdiction Information Parameter option values do not need to change, go to Step 7.
    • To change the Jurisdiction Information Parameter option values, enter the chg-lnpopts command with the desired values for the jipprv and jipdigits parameters. Then continue with Step 6.
  6. Verify the LNPOPTS changes. Enter the rtrv-lnpopts command.
  7. Display the status of the Gateway Screening (GWS) feature. Enter the rtrv-feat command.

    After the Gateway Screening feature is turned on with the chg-feat command, it cannot be turned off.

    The Gateway Screening feature must be purchased before you turn the feature on with the chg-feat command. If you are not sure if you have purchased the Gateway Screening feature, contact My Oracle Support (MOS).

    • If the Gateway Screening feature is on (gws = on appears in the output), continue with Step 8.
    • If the Gateway Screening feature is of (gws = off appears in the output), refer to the procedures in Database Administration - GWS User's Guide to verify that the required cards for GWS are equipped and to turn on the GWS feature. Then continue with Step 8.
  8. Display the GWS stop actions that are provisioned in the database. Enter the rtrv-gws-actset command.
    The TLNP feature requires a gateway screening stop action set with the tlnp gateway screening stop action. The tlnp gateway screening stop action is shown by the entry tlnp in the rtrv-gws-actset command output. 
    
rlghncxa03w 07-08-07 00:57:31 GMT EAGLE5 37.0.0
ACT  ACT    ACT  ACT  ACT  ACT  ACT  ACT  ACT  ACT  ACT  ACT
ID   NAME   1    2    3    4    5    6    7    8    9    10
--   ------ ---- ---- ---- ---- ---- ---- ---- ---- ---- ----
1    copy   copy
2    rdct   rdct
3    cr     copy rdct
4    crcncf copy cncf rdct
5    cncf   cncf
6    cfrd   cncf rdct
7    tlnp   tlnp
8    cptlnp copy tlnp
GWS action set table is (8 of 16) 38% full

    There can be only 2 TLNP GWS stop action sets, one with ACT1=TLNP and another with ACT1=COPY and ACT2=TLNP.

    • If 2 TLNP GWS stop actions appear in the output, continue with Step 9.
    • If 1 TLNP GWS stop action appears in the output and a second one is needed, use the "Configuring TLNP Gateway Screening Stop Action Sets" procedure in the Database Administration - GWS User's Guide to configure the second stop action set. Then continue with Step 9.
    • If the chg-feat command was used to turn on the Gateway Screening feature in 4 (no TLNP stop actions appear in the output ), go to Step 13.
  9. Display Allowed SIO screens with SI=5. Enter the rtrv-scr-sio:si=5 command.
    • If no entries are shown, go to Step 13 to create a new screen set.
    • If entries are shown, continue with Step 10.
  10. Display the screen sets that contain the desired Allowed SIO screen. Enter the rtrv-scrset:nsr=<SR value of the Allowed SIO screen> command.
  11. Display all of the screens in one of the screen sets shown in Step 10. Enter the rtrv-scrset:scrn=<SCRN value> command, with the SCRN value shown in Step 10.
    • To use the displayed screen set with all of the screens that are shown, continue with Step 12.
    • If you do not want to use the displayed screen set, display another screen set. until you find the screen set that you want to use. Then continue with Step 12.
  12. Display the last screen in the screen set.

    Enter one of the commands shown in Table 7-2, based on the NSFI value of the last screen, with the name of the screen that is shown in the NSR/ACT column.

    Table 7-2 Commands to Display the Last Screen in a GWS Screen Set

    NSFI Value Command
    OPC rtrv-scr-opc:sr-<screen name>
    BLKOPC rtrv-scr-blkopc:sr-<screen name>
    SIO rtrv-scr-sio:sr-<screen name>
    DPC rtrv-scr-dpc:sr-<screen name>
    BLKDPC rtrv-scr-blkdpc:sr-<screen name>
    DESTFLD rtrv-scr-destfld:sr-<screen name>
    ISUP rtrv-scr-isup:sr-<screen name>
    CGPA rtrv-scr-cgpa:sr-<screen name>
    TT rtrv-scr-tt:sr-<screen name>
    CDPA rtrv-scr-cdpa:sr-<screen name>
    AFTPC rtrv-scr-aftpc:sr-<screen name>
    • If the screen contains the TLNP GWS stop action, go to Step 14.

    • If the screen does not contain the TLNP GWS stop action, go to the in Database Administration - GWS User's Guide and perform the appropriate procedure listed in Table 7-3, to assign the TLNP GWS stop action to the screen. Then go to Step 14.

      Table 7-3 Procedures for Changing GWS Screens to include the TLNP Stop Action

      NSFI Value Procedure
      OPC Changing an Allowed OPC Screen
      BLKOPC Changing an Allowed BLKOPC Screen
      SIO Changing an Allowed SIO Screen
      DPC Changing an Allowed DPC Screen
      BLKDPC Changing an Allowed BLKDPC Screen
      DESTFLD Changing an Allowed DESTFLD Screen
      ISUP Changing an Allowed ISUP Screen
      CGPA Changing an Allowed CGPA Screen
      TT Changing an Allowed TT Screen
      CDPA Changing an Allowed CDPA Screen
      AFTPC Changing an Allowed AFTPC Screen
  13. Create a new screen set.

    Go to Database Administration - GWS User's Guide and perform the procedures listed in Table 7-4 as needed, to create a screen set the contains an Allowed SIO screen with the Service Indicator value 5 (SI=5).

    Then continue with Step 14.

    Table 7-4 Procedures to Create a GWS Screen Set with a TLNP Stop Action

    GWS Entity Procedure
    A screen set Adding a Screen Set
    An Allowed OPC screen Adding an Allowed OPC screen
    A Blocked OPC screen Adding a Blocked OPC screen
    An Allowed SIO screen Adding an Allowed SIO screen
    An Allowed DPC screen Adding an Allowed DPC screen
    A Blocked DPC screen Adding a Blocked DPC screen
    An Allowed ISUP screen Adding an Allowed ISUP screen
    Adding a TLNP GWS Stop Action Configuring TLNP Gateway Screening Stop Action Sets
  14. Display the linksets that are provisioned in the database. Enter the rtrv-ls command.

    • If the linkset that will screen messages for the TLNP feature is shown in the output and the screen set specified in Step 10 is assigned to the linkset, go to last.

    • If the linkset that will screen messages for the TLNP feature is shown in the output and the screen set specified in Step 10 is not assigned to the linkset, go to the indicated manuals and perform the procedures listed in Table 7-5 as required, to assign the screen set to the linkset.

      Then continue with Step 15.

      Table 7-5 Procedures to Assign a Screen Set to a Linkset for TLNP

      Procedure In Manual
      Changing an SS7 Linkset Database Administration - SS7 User's Guide
      Changing an IPGWx Linkset Database Administration - IP7 User's Guide
      Changing an IPSG M3UA Linkset Database Administration - IP7 User's Guide
      Changing an IPSG M2PA Linkset Database Administration - IP7 User's Guide

    • If the linkset that will screen messages for the TLNP Feature is not shown in the output, go to the indicated manuals and perform the required procedures that are listed in Table 7-6, to configure the required linkset and assign the screen set to the linkset.

      Then continue with Step 15.

      Table 7-6 Procedures to Create a Linkset and Assign a Screen Set to the Linkset for TLNP

      Procedure In Manual
      Adding an SS7 Linkset Database Administration - SS7 User's Guide
      Adding an IPSG M2PA Linkset Database Administration - IP7 User's Guide
      Adding an IPSG M3UA Linkset Database Administration - IP7 User's Guide
      Configuring an IPGWx Linkset Database Administration - IP7 User's Guide

      Note:

      When Gateway Screening is in the screen test mode, as defined by the linkset parameters gwsa=off and gwsm=on, the gateway screening action in the gateway screening stop action set specified by the actname parameter of the gateway screening screen set at the end of the gateway screening process will be performed.
  15. Back up the changes using the chg-db:action=backup:deist=fixed command.
    The following messages appear, the active Maintenance and Administration Subsystem Processor (MASP) appears first. 
    
BACKUP (FIXED): MASP A - Backup starts on active MASP.
BACKUP (FIXED): MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED): MASP A - Backup starts on standby MASP.
BACKUP (FIXED): MASP A - Backup on standby MASP to fixed disk complete.

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.

  1. Display the current Ethernet link parameters associated with the Service Module card in the database by entering the rtrv-ip-lnk command.
  2. Verify the status of the Service Module card being configured in this procedure using the rept-stat-card command.
    For example, enter the command rept-stat-card:loc=1301.
    • If the state of the Service Module card being configured in this procedure is in service-normal (IS-NR), continue with Step 3 to inhibit the card.
    • If the state of the Service Module card is out-of-service-maintenance disabled (OOS-MT-DSBLD), go to Step 5 to change the Ethernet link parameters.
  3. Place the Service Module card out of service using the inh-card command.
    For example, enter this command: inh-card:loc=1301. This message should appear. 
    
rlghncxa03w 06-08-01 21:18:37 GMT EAGLE5 35.1.0
Card has been inhibited.
  4. Display the status of the Service Module card to verify that it is out-of-service maintenance-disabled (OOS-MT-DSBLD).
    Enter the command rept-stat-card:loc=1301.
  5. Configure the Ethernet link parameters associated with the Service Module card in the database using the chg-ip-lnk command.
    For this example, enter the following commands:
    chg-ip-lnk:loc=1301:port=a:ipaddr=192.168.120.1:submask=255.255.255.0:auto=yes:mcast=no
    chg-ip-lnk:loc=1301:port=b:ipaddr=192.168.121.1:submask=255.255.255.0:auto=yes:mcast=no.
  6. Verify the new Ethernet link parameters associated with the Service Module card that was changed in Step 5 by entering the rtrv-ip-lnk command with the card location specified in Step 5.
    For example, enter the command rtrv-ip-lnk:loc=1301.

    Note:

    If Step 3 was not performed, go to Step 11.
  7. Configure the Ethernet card parameters associated with the Service Module card in the database using the chg-ip-card command.
    For example, enter the following command:
    chg-ip-card:bpipaddr=128.1.120.1:bpsubmask=255.255.192.0
  8. Verify the parameters associated with the Service Module card that was changed in Step 7 by entering the rtrv-ip-card command with the card location specified in Step 7.
  9. Put the Service Module card that was inhibited in Step 3 back into service by using the alw-card command.
    For example, enter the command alw-card:loc=1301.
  10. Verify the in-service normal (IS-NR) status of the Service Module card using the rept-stat-card command.
    For example, enter the command rept-stat-card:loc=1301.
  11. Repeat this procedure for all other Service Module cards in the EAGLE 5 ISS.
  12. Back up the new changes using the chg-db:action=backup:dest=fixed command.
    These messages appear, the active Maintenance and Administration Subsystem Processor (MASP) appears first. 
    
BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.
    You have now completed this procedure.

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.

  1. Display the Service Module cards (card type DSM) in the system and the status of each card by entering the rept-stat-card:appl=vsccp command.
    The cards that are running the VSCCP GPL are DSM cards (E5-SM4G cards and E5 SM4G-B cards run the SCCPHC GPL).
  2. Remove a DSM card from service using the rmv-card command and specifying the card location that was recorded in Step 1.
    If the card to be removed from service (inhibited) is the only Service Module card in service, the force=yes parameter must also be specified. The cards that are in service are shown by the entry IS-NR in the PST field in the output in Step 1. For this example, enter the following command:
    rmv-card:loc=1204 
    
rlghncxa03w 07-08-01 09:12:36 GMT  EAGLE5 37.0.0
Card has been inhibited.
  3. Remove the card from the database using the dlt-card command with the loc parameter to specify the card location.
    For this example, enter this command.
    dlt-card:loc=1204
  4. Verify the changes using the rtrv-card command and specifying the location of the card that was removed in Step 3. For this example, enter the following command:
    rtrv-card:loc=1204 
    
E2144 Cmd Rej: Location invalid for hardware configuration
  5. Remove the card specified in Step 3 from the shelf.
  6. Repeat this procedure for all other DSM cards in the EAGLE that need to be removed.
  7. Back up the changes using the chg-db:action=backup:dest=fixed command.
    These messages appear. The active Maintenance and Administration Subsystem Processor (MASP) appears first. 
    
BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.