4 Feature Configuration

This chapter describes the prerequisites, considerations, and steps to configure and activate the ANSI-41 Mobile Number Portability (A-Port) feature. This chapter also includes feature activation procedures for the following features:

  • MT-Based IS41 SMS NP

  • LOCREQ Query Response
  • Service Portablity

  • MTP Routed Messages for SCCP Applications

Introduction

This chapter identifies prerequisites for the A-Port feature activation procedure and provides the feature activation procedures performed at the EAGLE for the following features and functions:

  • HLR Configuration

  • A-Port

  • MT-Based IS41 SMS NP

  • LOCREQ Query Response

  • Service Portability

  • MTP Routed Messages for SCCP Applications

The A-Port feature and other related features are optional. Contact your Oracle Sales or Account Representative to determine whether you are entitled to use a specific feature or for additional information. The following features are related to the A-Port feature:

  • Global Title Translation (GTT)

  • Enhanced Global Title Translation (EGTT)

  • Variable-Length Global Title Translation (VGTT)

  • Mobile Number Portability Circular Route Prevention (MNPCRP)

  • E5-SM4G Throughput Capacity - Refer to Database Administration - GTT User's Guide for the procedure Activating E5-SM4G/E5-SM8G-B Throughput Capacity.

Refer to Commands User's Guide for complete descriptions of the commands used in these procedures.

Summary of Feature Activation

This table summarizes the feature activation attributes for features in this chapter.

Table 4-1 Feature Activation Summary

Feature Name Part Number Permanently On?

ANSI-41 Mobile Number Portability (A-Port)

893016601

Yes

MT-Based IS41 SMS NP

893019901

Yes

LOCREQ Query Response

893038501

Yes

Service Portability

893034301

No

MTP Msgs for SCCP Apps

893017401

No

1100 TPS/DSM for ITU NP

893018001

No

E5-SM4G Throughput Capacity

893019101

893019102

Yes

MNP Circular Route Prevention

893007001

No

Feature Activation Consideration

  • After a permanently-on feature has been enabled and turned on with the enable-ctrl-feat and chg-ctrl-feat commands, the feature cannot be turned off. Because this feature may affect other features or system databases, confirm that a feature license and technical support from Oracle are available before turning on this feature. Contact your Oracle Sales or Account Representative to verify whether you are entitled to use the feature.

EPAP Entity Provisioning

Oracle recommends that EPAP entity (SP or RN) administration not be performed until after the Point Code and/or Subsystem Number has been entered into the EAGLE MAP table.
  • EPAP-administered entity data can become out-of-sync with the EAGLE MAP table when the creation of Point Codes and/or Subsystem Numbers in the MAP table is performed after EPAP database administration.
  • If this mismatch is discovered in real-time operations, a UIM is sent to the EAGLE maintenance terminal. (Example UIMs: SCCP did not route - DPC not in MAP tbl, SCCP did not route - SS not in MAP tbl.)

Prerequisites

The A-Port feature activation assumes that Global Title Translation (GTT), Enhanced Global Title Translation (EGTT), or Variable-Length Global Title Translation (VGTT) is already provisioned. Refer to Database Administration - GTT User's Guide for provisioning procedures.

The A-Port feature activation assumes that the EPAP software is already configured; refer to EPAP Software Configuration in Administration Guide for EPAP.

The NT serial number (ent-serial-num) must be entered and locked before A-Port can be enabled and turned-on.

The A-Port feature requires a Service Module card running the VSCCP application prior to turning on the A-Port feature. The A-Port feature cannot be turned on if any of the Service Module cards have less than 4 GB of memory installed.

The A-Port feature activation assumes that the Service Module cards to be installed are identified.

  • Note installed Service Module card locations, if any.

  • Note available odd-even card slots for Service Module card installation.

  • Determine Service Module card IP addresses and have the addresses available during the activation procedure.

For in-service systems, schedule Service Module card replacement in a maintenance window that allows the reboot of Service Module cards (init-card:loc=<Service Module card location>) one at a time.

For in-service systems that have another EPAP-related feature enabled, perform only A-Port Feature Activation Procedure to enable and turn on the A-Port feature. With another EPAP-related feature feature enabled, the Service Module cards already contain the Real Time Database (RTDB).

For new systems, Service Module cards may be rebooted all at one time using the init-card:appl=vsccp command. The GTT, EGTT, or VGTT feature must be turned on prior to the reboot of all Service Module cards.

HLR Configuration

This procedure configures the EAGLE system for Home Location Register (HLR) destinations before activating the ANSI-41 Mobile Number Portability (A-Port) feature. This procedure assumes that the EAGLE is an existing system in which the A-Port feature is being activated. The route to the HLR database may already be configured. Perform this procedure to verify that all HLR destinations for the feature are provisioned and to configure changes, as needed.

Procedure Overview

  • Display current PCs, CPCs, DPCs, routes, and linksets using 1 through 6.

  • Change current PCs, CPCs, DPCs, routes, linksets, and LIM cards using 7 through 25 .

For detailed information about specific configuration activities in this procedure, refer to these topics in Database Administration - SS7 User's Guide:

  • Point Code Formats

  • Adding a Point Code to the Self-Identification of the EAGLE

  • Changing the Self-Identification of the EAGLE
  • Adding a Destination Point Code

  • Adding an SS7 Linkset

  • Adding an SS7 Signaling Link

  • Adding a Route Containing an SS7 DPC

  1. Display the current self-identification characteristics (PC and CPC) of the system using the rtrv-sid command.
    The self-identification characteristics of the system displayed by the rtrv-sid command include the point code (PC) assigned to the system, the CLLI code of the system, the capability point code of the STP (CPC), and the type of point codes supported by the system.
    If the ITUDUPPC (ITU national duplicate point code) feature is on, the ITU national point code also contains a group code. The group code is a two-character field from aa to zz that is entered as the last subfield of an ITU national point code, nnnnn-gc (for example, 2112-aa).
  2. Display the current destination point codes (DPC) in the Destination point code table (dpc/dpca/dpcn) using the rtrv-dstn command.
  3. Display the current route and linkset configuration using the rtrv-rte command.
  4. If the system point code (pc/pca/pci/pcn/pcn24) or capability point code (cpc/cpca/cpcn) to be configured in this procedure is shown in 1, 2, or 3, choose another point code to configure with this procedure. If configuring an ITU-N network, continue to 5. If configuring a mated application but not configuring an ITU-N, network proceed to 6. Otherwise, proceed to 7.
  5. Use the rtrv-stpopts command to display the PC or CPC format when configuring the system point code or capability point code (pcn or cpcn) of an ITU-N network.
    The ITU-N point code format option npcfmti to determines the format of the ITU-N point code in the database and how it is displayed in all system outputs. The defined value is shown in the NPCFMTI field displayed in the output of the rtrv-stpopts command.

    To change the format of the ITU-N point code, refer to "Point Code Formats" in Database Administration - SS7 User's Guide.

    Continue to 6 to display mated applications in the database. Otherwise, proceed to 7.

  6. Display the mated applications in the database using the rtrv-map command.
    1. If the point code of the system is displayed in the rtrv-map command output (PCA, PCI, PCN, MPCA, MPCI, or MPCN fields), remove the system point code from the mated application table. Refer to procedure “Removing a Mated Application” in Database Administration - Features User's Guide.
    2. If the point code of the system or capability point code is a destination point code of a route, select a point code that is not in the destination point code table (refer to output in 2) and not the destination point code of a route (refer to output in 3).
  7. Change the point code of the system and capability point code by network type using procedures "Adding a Point Code to the Self-Identification of the EAGLE" and "Changing the Self-Identification of the EAGLE" in Database Administration - SS7 User's Guide.
  8. Enter a destination point code for the HLR location in the Destination table by network type using the ent-dstn command.

    Command examples:

    ent-dstn:dpc=002-100-002

    ent-dstn:dpca=002-111-002

    where:

    :dpc/dpca/dpcn

    Destination point code to add to the database

  9. Verify the changes using the rtrv-dstn command and specifying the DPC entered in 8.

    Command examples:

    rtrv-dstn:dpc=002-100-002

    rtrv-dstn:dpca=002-111-002

    Example of possible output for the DPC command example:

    tekelecstp51 09-08-24 21:16:37 GMT EAGLE 41.0.0
    
    DPC         CLLI        BEI ELEI  ALIASA       ALIASN/N24  DMN
    002-100-002 --------    no  ---   --------     002-111-002  SS7
    

    Example of possible output for the DPCA command example:

    tekelecstp51 09-08-24 21:16:37 GMT EAGLE 41.0.0
    
    DPCN        CLLI        BEI ELEI  ALIASA       ALIASI       DMN
    002-111-002 --------    no  ---   --------     002-100-002  SS7
    
  10. Enter a linkset with the ent-ls command and assign the linkset to the destination point code by network type.

    Command examples:

    ent-ls:apc=002-200-002:lsn=ls400001:lst=c

    ent-ls:apcn=002-112-002:lsn=ls500001:lst=c

    where:

    :apc/apca/apcn
    Adjacent point code - the DPC of the adjacent signaling node at the far end of the linkset
    :lsn
    Linkset name
    :lst

    Linkset type

  11. Verify the changes using the rtrv-ls command and specifying the linkset name.

    Command example:

    rtrv-ls:lsn=ls400001

    rtrv-ls:lsn=ls500001

    Example of possible output for lsn400001 command example:

    tekelecstp51 09-08-24 21:16:37 GMT EAGLE 41.0.0
    
                                     L3T  SLT              GWS GWS GWS
    LSN          APC    (SS7)  SCRN  SET  SET BEI LST LNKS ACT MES DIS SLSCI NIS
    ls400001     002-200-002   scr1  1    2   no  a   0    on  off off no    on
    CLLI         TFATCABMLQ  MTPRSE  ASL8
    RLGHNCXA03W  1           no      no
                         L2T       L1              PCR PCR
    LOC  PORT SLC TYPE   SET BPS   MODE TSET ECM   N1  N2
    

    Example of possible output for lsn500001 command example:

    tekelecstp51 09-08-24 21:16:37 GMT EAGLE 41.0.0
    
                                     L3T SLT              GWS GWS GWS 
    LSN          APCN   (SS7)  SCRN  SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
    ls500001     002-112-002   scr3  1   2  no  a   0 on   off  off no    on
    CLLI         TFATCABMLQ  MTPRSE  ASL8
    RLGHNCXA03W  1           no      no
                         L2T       L1              PCR PCR
    LOC  PORT SLC TYPE   SET BPS   MODE TSET ECM   N1  N2
    
  12. Add the LIM cards to the database using the ent-card command.

    Command examples:

    ent-card:appl=ccs7itu:loc=1105:type=limt1

    ent-card:appl=ccs7itu:loc=1106:type=limt1

    where:

    :appl

    Specifies that the application is CCS7ITU.

    :loc

    Specifies the slot number for the card.

    :type

    Specifies that the card is a LIMT1 card.

  13. Enter the T1 interface using the ent-t1 command.

    Command examples:

    ent-e1:loc=1105:t1port=1

    ent-e1:loc=1106:t1port=1

    where:

    :loc
    Card location or slot as stenciled on the shelf
    :t1port
    T1 card port number
  14. Verify the changes using the rtrv-card command with the card location specified.

    Command examples:

    rtrv-card:loc=1105

    rtrv-card:loc=1106

    Example of possible output for command example:

    tekelecstp51 09-08-24 21:16:37 GMT EAGLE 41.0.0
    
    CARD   TYPE      APPL      LSET NAME     LINK SLC LSET NAME     LINK SLC
    1105   LIMT1     CCS7ITU   ls400001      A    00  ------------  B    --
    1106   LIMT1     CCS7ITU   ls500001      A    00  ------------  B    --
    
  15. Assign signaling links to the LIM cards using the ent-slk command.

    Command example:

    ent-slk:l2tset=1:link=a:loc=1105:lsn=ls400001:slc=0:t1port=1:ts=1

    ent-slk:l2tset=1:link=a:loc=1106:lsn=ls500001:slc=0:t1port=1:ts=1

    where:

    :l2tset

    Level 2 timer set. A signaling link can be assigned to any of the thirty timer sets.

    :link

    Signaling link assigned on the card specified in the loc parameter

    :loc

    Card location to which the signaling link is assigned

    :lsn

    Unique linkset name

    :slc

    Signaling link code. The slc must be unique within the linkset, and must be the same at both the system location and the distant node.

    t1port
    Port for T1 interface on the T1 card to which the signaling link and timeslot are being assigned
    ts
    T1 timeslot for the assigned signaling link

    Signaling links are the only elements in the database supported directly by a hardware device. When a link is added to a linkset, the link remains in Out-of-Service-Maintenance-Disabled (OOS-MT-DSBLD) state until it is activated; see 23.

  16. Verify the changes using the rtrv-slk command, specifying the card location and ID of the signaling link entered in 15.

    Command examples:

    rtrv-slk:loc=1105:link=a

    rtrv-slk:loc=1106:link=a

  17. Add a route for the new DPC by network type using the ent-rte command.

    Command examples:

    ent-rte:dpc=002-100-002:lsn=ls400001:rc=10

    ent-rte:dpca=002-111-002:lsn=ls500001:rc=10

    where:

    :dpc/dpca/dpcn

    Destination point code of the node to which the traffic is bound

    :lsn

    Linkset name associated with this route

    :rc

    Relative cost or priority of this route

  18. Verify the changes using the rtrv-rte command and specifying the destination point code of the route.
  19. Add a mated application by network type to the database using the ent-map command.

    Command examples:

    ent-map:grp=grp03:materc=99:mpc=003-200-001:mssn=50:pc=002-100-001:ssn=12:rc=20

    ent-map:grp=grp07:materc=99:mpca=001-111-004:mssn=250:pca=001-111-002:ssn=12:rc=10

    where:

    :grp

    Concerned point code broadcast list (CSPC) group name. This parameter specifies the name of a group of point codes that should be notified of the subsystem status. A different CSPC group can be assigned to each mated PC/SSN.

    :materc

    Mate relative cost

    :mpc/mpca/mpci/mpcn

    Mate remote point code.

    :mssn

    Mate subsystem number – the subsystem address of the backup point code that is to receive the message

    :pci/pcn

    ITU international/national point code

    :rc

    Relative cost

    :ssn

    Subsystem number – the subsystem address of the primary point code that is to receive the message

  20. Verify the changes using the rtrv-map command.
  21. Allow the LIM cards that were entered in 12 using the alw-card command.

    Command examples:

    alw-card:loc=1105

    alw-card:loc=1106

    This message appears:

    
    tekelecstp51 09-08-24 21:16:37 GMT EAGLE 41.0.0
    Card has been allowed.
    
  22. Verify In-Service-Normal (IS-NR) state of the cards using the rept-stat-card command.
  23. Activate the signaling links entered in 15 using the act-slk command.

    Command examples:

    act-slk:loc=1105:link=a

    act-slk:loc=1106:link=a

    The link changes state from Out-of-Service-Maintenance-Disabled (OOS-MT-DSBLD) to In-Service-Normal (IS-NR). The output confirms the activation.

    
    tekelecstp51 09-08-24 21:16:37 GMT EAGLE 41.0.0
    Activate Link message sent to card
    
  24. Verify In-Service-Normal (IS-NR) state of the signaling link using the rept-stat-slk command.

    Command examples:

    rept-stat-slk:loc=1105

    rept-stat-slk:loc=1106

  25. Display the new LIM cards in the database using the rtrv-card command.

    Example of a possible output:

    tekelecstp51 09-08-24 21:16:37 GMT EAGLE 41.0.0
    CARD   TYPE      APPL      LSET NAME     LINK SLC LSET NAME     LINK SLC
    1105   LIMT1     CCS7ITU   ls400001      A    00  ------------  B    --
    1106   LIMT1     CCS7ITU   ls500001      A    00  ------------  B    --
  26. Back up the database changes using the chg-db:action=backup:dest=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.
The HLR destinations are now configured and ready for A-Port feature activation.

A-Port Feature Activation Procedure

Use this procedure to enable, turn on, and configure the ANSI-41 Mobile Number Portability (A-Port) feature.

Caution:

Before starting this procedure, contact unresolvable-reference.html#GUID-F6B3D647-C34D-4046-83F4-3D37AC9F2F63 for assistance in performing the feature activation procedure. Do not proceed without consulting with Technical Services.
  1. Enter the enable-ctrl-feat command to enable the A-Port feature:
    enable-ctrl-feat:partnum=893016601:fak=<Feature Access Key>
  2. Enter the chg-ctrl-feat command to turn on the A-Port feature:
    chg-ctrl-feat:partnum=893016601:status=on
  3. Change the IS41 system options in the database using the chg-is41opts command.
  4. Verify the changes using the rtrv-is41opts command to display all IS41 system options from the database.
  5. Add routing number prefixes for the operating network using the ent-homern command. Add Home RNs that are prefixed to DNs for incoming messages. Up to 100 routing number prefixes for the operating network can be added to the HOMERN table.

    Command example:

    ent-homern:rn=34

    where:

    :rn

    Home routing number prefix. Parameter value is 1 to 15 hex digits (0-F).

  6. Verify the changes using the rtrv-homern command to retrieve a list of routing number prefixes that belong to the operating network.
  7. Display the list of administered service selector combinations using the rtrv-srvsel command.
    Avoid lengthy output by filtering the list using various parameter combinations. The service selector table can have over 1000 entries.
  8. Enter the A-Port service selectors by network type, if necessary, using the ent-srvsel command.
    This command assigns applicable service selectors required to specify the service entry for Service Module card services.

    Command example:

    ent-srvsel:gtia=2:nai=intl:np=e164:serv=mnp:snai=intl:snp=e164:ssn=9:tt=1

    where:

    :gtia

    Global title indicator, ANSI

    :nai

    Nature of address indicator

    :np

    Numbering plan

    :serv

    Service feature

    :snai

    International Service Nature of Address Indicator

    :snp

    Service numbering plan

    :ssn

    Subsystem number

    :tt

    Translation type

  9. Verify the changes using the rtrv-srvsel command to retrieve the list of administered service selector combinations.
    Avoid lengthy output by filtering the list using various parameter combinations. The service selector table can have over 1,000 entries.

    Command examples:

    rtrv-srvsel:gtia=2

    where:

    gtia
    Global title indicator, ANSI

    Caution:

    GTT, EGTT, and VGTT traffic is routed based on the global titles in the OAM database while G-Flex, G-Port, A-Port, and INP traffic is routed based on the global title in the RTDB. Rebooting a Service Module card running the SCCPHC application causes both the OAM databases and the RTDB on the Service Module card to reload.
  10. Verify that the Service Module card returns to In-Service-Normal (IS-NR) state using the rept-stat-card command.

    warning:

    Do not proceed until In-Service-Normal (IS-NR) state of the Service Module card is restored.
  11. After In-Service-Normal (IS-NR) state of the Service Module card is restored and verified using the rept-stat-card command, repeat feature-configuration.html for each Service Module card in the system.
  12. Set the MNP service state online using chg-sccp-serv:serv=mnp:state=online.
  13. Confirm that the activation steps were successful by performing the following verifications:
    • Verify that all Service Module cards are loaded and are in In-Service-Normal (IS-NR) state using the rept-stat-sccp command.
    • Verify that all Service Module cards and the EPAP are connected and operational using the rept-stat-mps command.
    • Verify that database levels are identical for the EPAP PDB and RTDB. Display the RTDBs on the Service Module cards using rept-stat-db:display=all .
  14. Back up the database changes using the chg-db:action=backup:dest=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.
The ANSI-41 Mobile Number Portability (A-Port) feature is now enabled, turned on, and operating in the system.

MT-Based IS41 SMS NP Feature Activation Procedure

This procedure is used to activate the MT-Based IS41 SMS NP feature.
  • Before this feature can be enabled, the A-Port feature must be enabled.
  • Before the MT-Based IS41 SMS NP feature can be turned on, the A-Port Feature must be turned on.
  • The MT-Based IS41 SMS NP feature can be enabled before the A-Port feature is turned on.
  1. Verify that the A-Port feature is enabled using the rtrv-ctrl-feat command.
  2. If the A-Port feature is not enabled, enable it using A-Port Feature Activation Procedure before proceeding to 3.
  3. Enter the enable-ctrl-feat command to enable the MT-Based IS41 SMS NP feature.
    enable-ctrl-feat:partnum=893019901:fak=<feature access key>
  4. Enter the the chg-stpopts command to set the default country code to convert the nature of address indicator (NAI) of MDNs to the international format (nai=intl).
    The parameters in this command are used for number conditioning.

    For example, enter this command:

    chg-stpopts:defcc=49

    where:
    defcc
    The default country code.
  5. Verify the new country code using the rtrv-stpopts command.
  6. Enter the rtrv-is41smsopts command to view the values of the IS41SMSOPTS options.
  7. If desired, change the IS41 SMS options in the database for the MT-Based IS41 SMS NP feature using the chg-is41smsopts command.

    Note:

    MTSMSDLTRV must be set to a value other than NONE before MTSMSDLTR can be set to either PRERN or POSTRN.

    For example, enter this command:

    chg-is41smsopts:mtsmsdnfmt=rn:mtsmstype=rn

    where:
    mtsmsdnfmt
    Specifies the format of the SMS_Address parameter of the SMSREQ ACK response.
    mtsmstype
    Indicates the entity type for which a database lookup is considered successful.
  8. Verify the changes using the rtrv-is41smsopts command.
    This command displays all IS41 SMS options from the database.

    This is an example of the possible output:

    tekelecstp 08-04-08 19:38:30 EST  EAGLE 39.0.0
       
        IS41 OPTIONS
        -----------------------
        MTSMSDNFMT      = RNDN
        MTSMSTYPE       = RN
        MTSMSPARM       = DIGIT
        MTSMSDLTR       = NO
        MTSMSDLTRV      = NONE
        MTSMSACKN       = ACK
        MTSMSESN        = NO
        MTSMSSSN        = 6
        MTSMSNAKERR     = 5
        MTSMSDIGTYPE    = 6
        MTSMSCHKSRC     = NO
  9. If the value of IS41SMSOPTS:MTSMSCHKSRC=YES, then provision the Home SMSC Table entries using the ent-home-smsc command.

    For example, enter this command:

    ent-home-smsc:smsc=552611646

  10. Verify the SMSC table contents using the rtrv-home-smsc command.
    This command retrieves the HOME SMSC specific addresses currently used to identify Short Message Service Centers in the database.
    This is an example of the possible output:
    rtrv-home-smsc
    
        rlghncxa03w 03-03-28 08:50:12 EST  EAGLE 31.3.0
        SMSC ADDRESS
        
        13214564894498
        55231465465434
        5465455655656456
    
        HOME SMSC ADDRESS TABLE IS   1 % FULL    (3 of 500)
  11. Verify that the A-Port feature is turned on using the rtrv-ctrl-feat command.
  12. If the A-Port feature is not turned on, turn it on using A-Port Feature Activation Procedure before proceeding to 13.
  13. Enter the chg-ctrl-feat command to turn on the MT-Based IS41 SMS NP feature.
    chg-ctrl-feat:partnum=893019901:status=ON
  14. Back up the database changes using the chg-db:action=backup:dest=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.
The MT-Based IS41 SMS NP feature is now enabled, turned on, and operating in the system.

LOCREQ Query Response Activation Procedure

This procedure is used to enable and turn on the LOCREQ Query Response feature in the EAGLE.

Prerequisites

  • A-Port or IS41 GSM Migration (IGM) must be enabled and turn on before the LOCREQ Query Response feature can be enabled.

  • The LOCREQ Query Response feature is optional and must be purchased to receive the Feature Access Key (FAK) that is required to enable the feature. Contact your Sales Representative or Account Representative to determine whether you are entitled to use the LOCREQ Query Response feature has been purchased and for additional information.

The LOCREQ Query Response feature is enabled using part number 893038501 and the Feature Access Key (FAK). The LOCREQ Query Response feature cannot be disabled after it is enabled and cannot be enabled with a temporary FAK. After the LOCREQ Query Response feature is enabled and turned on, the LOCREQ Query Response feature cannot be turned off.

Some parameters and options used with the LOCREQ Query Response feature can be provisioned after the LOCREQ Query Response feature is enabled, but before the LOCREQ Query Response feature is turned on. The locreqrspnd option of the chg-is41opts command can be modified only if the LOCREQ Query Response feature is enabled and turned on. The dfltrn parameter of the chg-is41opts command can be modified only if the LOCREQ Query Response feature is enabled. The sporttype parameter of the chg-is41opts command can be modified only if both the Service Portabilty feature and the LOCREQ Query Response feature are enabled.

LOCREQ Query Response processing cannot occur until:

  • The LOCREQ Query Response feature is enabled and turned on.

  • The locreqrspnd option of the chg-is41opts command is set to on.

  1. Display the status of controlled features controlled by Feature Access Keys (FAKs). The resulting output displays the features that are enabled in the system and the on/off status for each feature.

    Command example:

    rtrv-ctrl-feat

    Output example:

        rlghncxa03w 10-06-29 16:40:40 EST  EAGLE 42.0.0
        The following features have been permanently enabled:
        Feature Name              Partnum    Status  Quantity
        HC-MIM SLK Capacity       893012707  on            64
        APORT                     893016601  on          ----
        Service Portability       893034301  on          ----
    ;

    The output shows the enabled features and the on/off status for each enabled feature in the EAGLE.

    • If the LOCREQ Query Response entry appears in the rtrv-ctrl-feat output with status = on, this procedure does not need to be performed.
    • If an entry for either APORT or IGM with a status of on does not appear in the rtrv-ctrl-feat output, then this procedure cannot be performed until either the A-Port or IS41 GSM Migration (IGM) feature is enabled and turned on.
    • If the LOCREQ Query Response entry appears in the rtrv-ctrl-feat output with status = off, go to 4 to turn on the LOCREQ Query Response feature.
    • To enable and turn on the LOCREQ Query Response feature, continue to 2.
  2. Enable the LOCREQ Query Response feature.

    Command example:

    enable-ctrl-feat:partnum=893038501:fak=<Feature Access Key>
  3. Verify that the LOCREQ Query Response feature is enabled.

    Command example:

    rtrv-ctrl-feat
        rlghncxa03w 09-06-29 16:40:40 EST  EAGLE 41.1.0
        The following features have been permanently enabled:
        Feature Name              Partnum    Status  Quantity
        HC-MIM SLK Capacity       893012707  on            64
        APORT                     893016601  on          ----
        Service Portability       893034301  on          ----
        LOCREQ Query Response     893038501  off         ----
      ;

    Some parameters and options can be provisioned after the feature is enabled but is turned off. LOCREQ Query Response processing cannot occur until the feature is enabled and turned on and thelocreqrspnd option of the chg-is41opts command is set to on.

  4. Turn on the LOCREQ Query Response feature.

    Command example:

    chg-ctrl-feat:partnum=893038501:status=on
  5. Verify that the LOCREQ Query Response is enabled and turned on.

    Command example:

    rtrv-ctrl-feat
        rlghncxa03w 09-06-29 16:40:40 EST  EAGLE 41.1.0
        The following features have been permanently enabled:
        Feature Name              Partnum    Status  Quantity
        HC-MIM SLK Capacity       893012707  on            64
        APORT                     893016601  on          ----
        Service Portability       893034301  on          ----
        LOCREQ Query Response     893038501  on         ----
      ;

    LOCREQ Query Response processing cannot occur until the locreqrspnd option of the chg-is41opts command is set to on.

  6. Specify the parameters dfltrn and sporttype used with LOCREQ Query Response and .Service Portability features

    Command example:

    chg-is41opts:dfltrn=48607:sporttype=is41
  7. Set the locreqrspnd option of the chg-is41opts command to on.

    Command example:

    chg-is41opts:on=locreqrspnd
  8. Verify that the IS41OPTS parameter setting are correct.

    Command example:

    rtrv-is41opts
    The LOCREQ Query Response feature is now enabled, turned on, and operating in the system. The feature cannot be disabled and cannot be turned off. LOCREQ Query Response processing can be halted by setting the locreqrspnd option of the chg-is41opts command to off.
  9. Back up the database changes using the chg-db:action=backup:dest=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.

Service Portability Activation Procedure

This procedure is used to enable and turn on the Service Portability (S-Port) feature in the EAGLE.

The Service Portability feature is optional and must be purchased from Oracle. The feature must be purchased to receive the Feature Access Key (FAK) that is required to enable the feature. Contact your Oracle Sales Representative or Account Representative to determine whether you are entitled to use the Service Portability feature has been purchased and for additional information.

The Service Portability (S-Port) feature is enabled using part number 893034301 and the Feature Access Key (FAK). The S-Port feature cannot be disabled after it is enabled and cannot be enabled with a temporary FAK. After the S-Port feature is enabled and turned on, the S-Port feature can be turned off.

S-Port options can be provisioned after the S-Port feature is enabled and before the S-Port feature is turned on. After the S-Port feature is enabled and provisioning is complete, the S-Port feature must be turned on (status set to on), before S-Port processing will occur.

  1. Display the status of the controlled features that are controlled with Feature Access Keys (FAKs).

    Command example:

    rtrv-ctrl-feat

    The output shows the enabled features and the on/off status for each enabled feature in the EAGLE. If the rtrv-ctrl-feat output shows an LNP ported TNs quantity entry, this procedure cannot be performed. If the Service Portability entry appears in the rtrv-ctrl-feat output with status = on, this procedure does not need to be performed. If the Service Portability entry appears in the rtrv-ctrl-feat output with status = off, go to 4 to turn on the S-Port feature. To enable and turn on the S-Port feature, continue to 2.

  2. Enable the S-Port feature.

    Command example:

    enable-ctrl-feat:partnum=893034301:fak=<Feature Access Key>
  3. Verify that the S-Port feature is enabled.

    Command example:

    rtrv-ctrl-feat
        rlghncxa03w 09-06-29 16:40:40 EST  EAGLE5 41.1.0
        The following features have been permanently enabled:
        Feature Name              Partnum    Status  Quantity
        HC-MIM SLK Capacity       893012707  on            64
        Service Portability       893034301  off         ----
     ;

    S-Port options can be provisioned after the feature is enabled. S-Port processing will not occur until the feature is enabled and turned on.

  4. Turn on the S-Port feature.

    Command example:

    chg-ctrl-feat:partnum=893034301:status=on
  5. Verify that the S-Port feature is enabled and turned on.

    Command example:

    rtrv-ctrl-feat
     rlghncxa03w 09-06-29 16:43:40 EST  EAGLE5 41.1.0
        The following features have been permanently enabled:
        Feature Name              Partnum    Status  Quantity
        HC-MIM SLK Capacity       893012707  on            64
        Service Portability       893034301  on          ----
     ;

    S-Port processing can occur after the feature is enabled and turned on.

  6. Back up the database changes using the chg-db:action=backup:dest=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.
The Service Portability (S-Port) feature is now enabled, turned on, and operating in the system. The feature can be turned off using the chg-ctrl-feat command, but cannot be disabled.

MTP Routed Messages for SCCP Applications Activation Procedure

This procedure is used to enable and turn on the MTP Routed Messages for SCCP Applications (MTP Msgs for SCCP Apps) feature in the EAGLE.

  • Before the MTP Msgs for SCCP Apps feature can be enabled, GTT must be on.

  • The MTP Msgs for SCCP Apps feature is optional and must be purchased from Oracle. The feature must be purchased to receive the Feature Access Key (FAK) that is required to enable the feature. Contact your Oracle Sales Representative or Account Representative to determine whether you are entitled to use the MTP Msgs for SCCP Apps feature has been purchased and for additional information.

The MTP Msgs for SCCP Apps feature is enabled using part number 893017401 and the Feature Access Key (FAK). The MTP Msgs for SCCP Apps feature cannot be disabled after it is enabled and cannot be enabled with a temporary FAK. After the MTP Msgs for SCCP Apps feature is enabled and turned on, the feature can be turned off.

The MTP Msgs for SCCP Apps feature must be enabled and turned on (status set to on) before MTP Msgs for SCCP Apps processing will occur.

  1. Display the status of the controlled features that are controlled with Feature Access Keys (FAKs).

    Command example:

    rtrv-ctrl-feat

    The output shows the enabled features and the on/off status for each enabled feature in the EAGLE.

    • If the MTP Msgs for SCCP Apps entry appears in the rtrv-ctrl-feat output with status = on, this procedure does not need to be performed.
    • If the MTP Msgs for SCCP Apps entry appears in the rtrv-ctrl-feat output with status = off, go to 4 to turn on the MTP Msgs for SCCP Apps feature.
    • If the MTP Msgs for SCCP Apps entry does not appear in the rtrv-ctrl-feat output, continue with 2.
  2. Enable the MTP Msgs for SCCP Apps feature.

    Command example:

    enable-ctrl-feat:partnum=893017401:fak=<Feature Access Key>
  3. Verify that the MTP Msgs for SCCP Apps feature is enabled.

    Command example:

    rtrv-ctrl-feat
        rlghncxa03w 09-06-29 16:40:40 EST  EAGLE5 41.1.0
        The following features have been permanently enabled:
        Feature Name              Partnum    Status  Quantity
        HC-MIM SLK Capacity       893012707  on            64
        MO-based IS41 SMS NP      893019501  on          ----
        MTP Msgs for SCCP Apps    893017401  off         ----
     ;

    MTP Msgs for SCCP Apps processing will not occur until the feature is enabled and turned on.

  4. Turn on the MTP Msgs for SCCP Apps feature.

    Command example:

    chg-ctrl-feat:partnum=893017401:status=on
  5. Verify that the MTP Msgs for SCCP Apps feature is enabled and turned on.

    Command example:

    rtrv-ctrl-feat
     rlghncxa03w 09-06-29 16:43:40 EST  EAGLE5 41.1.0
        The following features have been permanently enabled:
        Feature Name              Partnum    Status  Quantity
        HC-MIM SLK Capacity       893012707  on            64
        MO-based IS41 SMS NP      893019501  on          ----
        MTP Msgs for SCCP Apps    893017401  on          ----
     ;

    MTP Msgs for SCCP Apps processing can occur after the feature is enabled and turned on.

  6. Back up the database changes using the chg-db:action=backup:dest=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.
The MTP Msgs for SCCP feature is now enabled, turned on, and operating in the system. The feature can be turned off using the chg-ctrl-feat command, but cannot be disabled.