Feature Configuration

4 Feature Configuration

This chapter describes the prerequisites, considerations, and steps to configure and activate the G-Port feature. This chapter also includes feature activation procedures for these features:

MT-Based GSM SMS NP
MT-Based GSM MMS NP
G-Port SRI Query for Prepaid
GSM MAP SRI Redirect to Serving HLR

4.1 Introduction

This chapter identifies prerequisites for the G-Port feature activation procedure and provides the feature activation procedures for the following features:

G-Port
MT-Based GSM SMS NP
MT-Based GSM MMS NP
G-Port SRI Query for Prepaid
Service Portability support for G-Port SRI Query for Prepaid
GSM MAP SRI Redirect to Serving HLR

These feature activation procedures are performed at the EAGLE.

The G-Port feature and other related features are optional and are purchased from Oracleyou must be entitled to use them in your system. Contact your Oracle Sales or Account Representative to determine whether you have purchasedare entitled to use a specific feature or for additional information. The following features are related to the G-Port feature:

Global Title Translation (GTT)
Enhanced Global Title Translation (EGTT)
Variable-Length Global Title Translation (VGTT)
EAGLE Application Processor (EPAP)
Mobile Number Portability Circular Route Prevention (MNPCRP)

In addition, the following performance-related feature is related to G-Port:

E5-SM4G Throughput Capacity

Note:

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 has been purchased.

Summary of Feature Activation

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

Table 4-1 Feature Activation Summary

Feature Name	Part Number	Permanently On?
GSM Mobile Number Portability (G-Port)	893017201	Yes
MNP Circular Route Prevention (MNPCRP)	893007001	No
MT-Based GSM SMS NP	893020001	Yes
MT-Based GSM MMS NP	893024101	Yes
G-Port SRI Query for Prepaid	893017701	Yes
Service Portability	893034301	No
GSM MAP SRI Redirect to Serving HLR	893014001	Yes

4.2 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.)

4.3 Prerequisites

The G-Port feature activation assumes that the feature 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 G-Port feature activation assumes that the EPAP software is already configured; refer to EPAP Software Configuration in Administration Guide for EPAP.

The G-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 during a maintenance window that allows the reboot of Service Module cards (init-card) one at a time.

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

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

4.4 EAGLE HLR Configuration

This procedure configures the EAGLE system for Home Location Register (HLR) destinations before activating the GSM Mobile Number Portability (G-Port) feature. This procedure assumes that the EAGLE is an existing system in which the G-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. The G-Port feature applies to ITU-I (international), ITU-N (national), and ANSI networks.

Refer to Commands User's Guide for detailed descriptions of the commands used in this procedure.

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 Database Administration - SS7 User's Guide. Useful procedures include:

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

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).
Display the current destination point codes (DPC) in the Destination point code table (dpc/dpca/dpci/dpcn) using the rtrv-dstn command.
Display the current route and linkset configuration using the rtrv-rte command.
If the system point code (pci/pcn) or capability point code (cpc/cpca/cpci/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.
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 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.
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).
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.
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:dpci=2-100-2

ent-dstn:dpcn=21112

where:

:dpc/dpca/dpci/dpcn

Destination point code to add to the database

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

Command examples:

rtrv-dstn:dpci=2-100-2

rtrv-dstn:dpcn=21112

Example of possible output for the DPCI command example:

tekelecstp51 09-08-24 21:16:37 GMT EAGLE 41.0.0

DPCI        CLLI        BEI ELEI  ALIASA       ALIASN/N24  DMN
2-100-2     --------    no  ---   --------     ----------  SS7

Example of possible output for the DPCN command example:

tekelecstp51 09-08-24 21:16:37 GMT EAGLE 41.0.0

DPCN        CLLI        BEI ELEI  ALIASA       ALIASI  DMN
21112       --------    no  ---   --------     ------  SS7

Enter a linkset with the ent-ls command and assign the linkset to the destination point code by network type.

Command examples:

ent-ls:apci=2-200-2:lsn=ls400001:lst=a

ent-ls:apcn=21122:lsn=ls500001:lst=a

where:

:apc/apca/apci/apcn

Adjacent point code - the DPC of the adjacent signaling node at the far end of the linkset

:lsn

Linkset name

:lst

Linkset type

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          APCI   (SS7)  SCRN  SET  SET BEI LST LNKS ACT MES DIS SLSCI NIS
ls400001     2-200-2       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     21122         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

Add the LIM cards to the database using the ent-card command.

Command examples:

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

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

where:

:appl

Specifies that the application is CCS7ITU.

:loc

Specifies the slot number for the card.

:type

Specifies that the card is a LIME1 card.
Enter the E1 interface using the ent-e1 command.

Command examples:

ent-e1:loc=1105:e1port=1

ent-e1:loc=1106:e1port=1

where:

:loc

Card location or slot as stenciled on the shelf

:e1port

E1 card port number

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   LIME1     CCS7ITU   ls400001      A    00  ------------  B    --
1106   LIME1     CCS7ITU   ls500001      A    00  ------------  B    --

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:e1port=1:ts=1

ent-slk:l2tset=1:link=a:loc=1106:lsn=ls500001:slc=0:e1port=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.

e1port

Port for E1 interface on the E1 card to which the signaling link and timeslot are being assigned

ts

E1 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.
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
Add a route for the new DPC by network type using the ent-rte command.

Command examples:

ent-rte:dpci=2-100-2:lsn=ls400001:rc=10

ent-rte:dpcn=21112:lsn=ls500001:rc=10

where:

:dpc/dpca/dpci/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
Verify the changes using the rtrv-rte command and specifying the destination point code of the route.
Add a mated application by network type to the database using the ent-map command.

Command examples:

ent-map:grp=grp03:materc=99:mpci=3-200-1:mssn=50:pci=2-100-1:ssn=12:rc=20

ent-map:grp=grp07:materc=99:mpcn=11114:mssn=250:pcn=11112: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
Verify the changes using the rtrv-map command.
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.
```
Verify In-Service-Normal (IS-NR) state of the cards using the rept-stat-card command.
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
```
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

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   LIME1     CCS7ITU   ls400001      A    00  ------------  B    --
1106   LIME1     CCS7ITU   ls500001      A    00  ------------  B    --

The HLR destinations are now configured and ready for G-Port feature activation.

4.5 G-Port Feature Activation Procedure

Use this procedure to enable, turn on, and configure the GSM Mobile Number Portability (G-Port) feature. Refer to Commands User's Guide for detailed descriptions of the commands that are used in this procedure.

Caution:

Before starting this procedure, contact My Oracle Support (MOS) for assistance in performing the feature activation procedure. Do not proceed without consulting with Technical Services.

Enter the enable-ctrl-feat command to enable the G-Port feature:
enable-ctrl-feat:partnum=893017201:fak=<Feature Access Key>
Enter the chg-ctrl-feat command to turn on the G-Port feature:
chg-ctrl-feat:partnum=893017201:status=on
Enter the default country code and default network destination code to convert the nature of address indicator (NAI) of MSISDNs to the international format (nai=intl) with the chg-stpopts command.

Command example:

chg-stpopts:defcc=1:defndc=38:dsmaud=on:npcfmti=2-9-2-1

where:

:defcc

Default country code

:defndc

Default network destination code

:dsmaud

Service Module card checksum audit running state (on or off)

:npcfmti

ITU National Point Code Format Identifier, which identifies how the ITU national point code is entered into the database and how it is displayed in all EAGLE outputs. The ITU national point code is a 14-bit integer.
Verify the new country code and network destination code using the rtrv-stpopts command.
Change the GSM system options in the database using the chg-gsmopts command.

Command example:

chg-gsmopts:defmapvr=2:msrsndig=ccrndn:srfaddr=23448:srfnai=7:srfnp=15

where:

:defmapvr

Default MAP version

:msrndig

Routing number to be used as is or to be concatenated with the MSISDN

:srfaddr

Entity address of the MNP_SRF node

:srfnai

Nature of address indicator value of the MNP_SRF

:srfnp

Numbering plan value of the MNP_SRF
Verify the changes using the rtrv-gsmopts command to display all GSM system options from the database.
Add routing number prefixes for the operating network using the ent-homern command. Add Home RNs that are prefixed to DNs for incoming INPMR 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).
Verify the changes using the rtrv-homern command to retrieve a list of routing number prefixes that belong to the operating network.
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 1,000 entries.
Enter the G-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:gtii=4:nai=intl:np=e164:serv=gport:snai=intl:snp=e164:ssn=9:tt=1

where:

:gtii

Global title indicator, ITU international

: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
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:gtii=2

rtrv-srvsel:gtii=4

where:

gtii

Global title indicator, ITU international

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.
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.
After In-Service-Normal (IS-NR) state of the Service Module card is restored and verified using the rept-stat-card command, repeat 12 for each Service Module card in the system.
Set the G-Port service state online using chg-sccp-serv:serv=gport:state=online.
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 .

The GSM Mobile Number Portability (G-Port) feature is now enabled, turned on, and operating in the system.

4.6 MT-Based GSM SMS NP Feature Activation Procedure

This procedure is used to activate the MT-Based GSM SMS NP feature.

Before this feature can be enabled, the G-Port feature must be enabled.
Before the MT-Based GSM SMS NP feature can be turned on, the G-Port Feature must be turned on.
The MT-Based GSM SMS NP feature can be enabled before the G-Port feature is turned on.

For details about the commands used in this procedure, refer to Commands User's Guide.

Verify that the G-Port Feature is enabled using the rtrv-ctrl-feat command.
If the G-Port Feature is not enabled, enable it using G-Port Feature Activation Procedure before proceeding.
Enter the enable-ctrl-feat command to enable the MT-Based GSM SMS NP feature.
enable-ctrl-feat:partnum=893020001:fak=<Feature Access Key>
Enter the the chg-stpopts command to set the default country code and, if desired, the default network destination 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:defndc=177

where:

defcc

The default country code.

defndc

The default network destination code.
Verify the new country code and network destination code using the rtrv-stpopts command.
Enter the rtrv-gsmopts command to view the values of the GSMOPTS table options.
Change the value DefMCC in the GSMOPTS table using the chg-gsmopts command. If desired, other GSM system options may also be changed with this command.

Note:
GSMOPTS:DefMCC must be set to a valid value before the MT-Based GSM SMS NP feature can be turned on.

For example, enter this command:

chg-gsmopts:defmcc=253

where:

defmcc

Specifies the E212 default mobile country code.
Verify the changes using the rtrv-gsmopts command.
This command displays GSM system options from the database.
Enter the rtrv-gsmsmsopts command to view the values of the GSMSMSOPTS table options.
If desired, change the GSM SMS options in the database for the MT-Based GSM SMS NP feature using the chg-gsmsmsopts command.

Note:
MTSMSDLTRV must be set to a value other than "NONE" before MTSMSDLTR can be set to either PRERN or POSTRN. For details about all options that can be changed using the chg-gsmsmsopts command, refer to Commands User's Guide.

For example, enter this command:

chg-gsmsmsopts:mtsmsimsi=mccrndn:mtsmstype=rn

where:

mtsmsimsi

Specifies the format of the IMSI parameter of the SRI_SM ACK response.

mtsmstype

Indicates the entity type for which a database lookup is considered successful.
Verify the changes using the rtrv-gsmsmsopts command.
This command displays all GSM SMS options from the database.
If the value of GSMSMSOPTS: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
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.
Verify that the G-Port Feature is turned on using the rtrv-ctrl-feat command.
If the G-Port Feature is not turned on, see G-Port Feature Activation Procedure before proceeding.
Enter the chg-ctrl-feat command to turn on the MT-Based GSM SMS NP feature.
chg-ctrl-feat:partnum=893020001:status=ON

The MT-Based GSM SMS NP feature is now enabled, turned on, and operating in the system.

4.7 MT-Based GSM MMS NP Feature Activation Procedure

This procedure is used to activate the MT-Based GSM MMS NP feature.

Before this feature can be enabled, the MT-Based GSM SMS NP feature must be enabled.
Before the MT-Based GSM MMS NP feature can be turned on, the MT-Based GSM SMS NP feature must be turned on.
The MT-Based GSM MMS NP feature can be enabled before the MT-Based GSM SMS NP feature is turned on.

For details about the commands used in this procedure, refer to Commands User's Guide.

Verify that the MT-Based GSM SMS NP feature is enabled using the rtrv-ctrl-feat command.
If the MT-Based GSM SMS NP feature is not enabled, enable it using MT-Based GSM SMS NP Feature Activation Procedure before proceeding.
Enter the enable-ctrl-feat command to enable the MT-Based GSM MMS NP feature.
enable-ctrl-feat:partnum=893024101:fak=<Feature Access Key>
Enter the rtrv-gsmsmsopts command to view the values of the GSMSMSOPTS table option.
If desired, MT-Based GSM MMS NP feature options may be changed with this command.

For example, enter this command:

chg-gsmsmsopts:mtmmsgta=12345:mtmmsackn=ack:mtmmstype=rn

where:

mtmmsgta

Specifies the GTA that is compared to the SCCP CgPA GTA of an SRI_SM message to determine whether the originator of the messages is a Home MMSC.

mtmmsackn

Specifies the message that is generated in response to a successful RTDB lookup for an SRI_SM message from a Home MMSC.

mtmmstype

Specifies the value of the entity type that indicates that a successful lookup occurred in the RTDB for messages that are modified by the MT-Based GSM MMS NP feature.

Note:
For details about all of the options that can be changed using the chg-gsmsmsopts command, refer to Commands User's Guide.
Verify the changes using the rtrv-gsmsmsopts command.
This command displays the GSM SMS options from the database.
Verify that the MT-Based GSM SMS NP feature is turned on using the rtrv-ctrl-feat command.
If the MT-Based GSM SMS NP feature is not turned on, refer to MT-Based GSM SMS NP Feature Activation Procedure before proceeding.
Enter the chg-ctrl-feat command to turn on the MT-Based GSM MMS NP feature.
chg-ctrl-feat:partnum=893024101:status=ON

The MT-Based GSM MMS NP feature is now enabled, turned on, and operating in the system.

4.8 G-Port SRI Query for Prepaid Feature Activation Procedure

This procedure is used to activate the G-Port SRI Query for Prepaid feature.

Before this feature can be enabled, the G-Port feature must be enabled and turned on.
The G-Port SRI Query for Prepaid feature cannot be enabled with a Tempoarary Feature Access key (FAK).
The G-Port SRI Query for Prepaid feature cannot be turned off after the feature is turned on.
The Service Portability support for G-Port SRI Query for Prepaid feature cannot be enabled with a Tempoarary Feature Access key (FAK).
The Service Portability support for G-Port SRI Query for Prepaid feature can be turned off after it is turned on.

For details about the commands used in this procedure, refer to Commands User's Guide.

Verify that the G-Port Feature is enabled and turned on using the rtrv-ctrl-feat command.
If the G-Port Feature is not enabled and tuned on, enable and turn on the G-Port feature using G-Port Feature Activation Procedure before proceeding.
Enter the enable-ctrl-feat command to enable the G-Port SRI Query for Prepaid feature.
enable-ctrl-feat:partnum=893017701:fak=<feature access key>
Enter the ent-gserv-data command to provision the translation type, originating point code, or global title address data in the GSERV table.
The tt parameter is used to specify a called party (CdPA) translation type, the opc/opca/opci/opcn/opcn24 parameters are used to specify message transfer part (MTP) originating point codes, and the gta parameter is used to specify a calling party (CgPA) global title address. These values determine whether a Send Routing Information (SRI) request receives G-Port SRI Query for Prepaid service or normal G-Port service.

Command example:

ent-gserv-data:tt=77

where:

tt

Translation type
Verify the new values of the GSERV table using the rtrv-gserv-data command.
Provision the default routing number in the GSMOPTS table using the chg-gsmopts command, if required. The default routing number is used to determine the digits to use as the routing number portion of the msrndig parameter.

Command example:

chg-gsmopts:dfltrn=135

where:

dfltrn

Default routing number
Enable Service Portability if Service Portability support for G-Port SRI Query for Prepaid feature is required. If Service Portability support for G-Port SRI Query for Prepaid feature is not required, continue to 10.

Command example:

enable-ctrl-feat:partnum=893034301:fak=<feature access key>
Provision the Service Portability Type in the GSMOPTS table using the chg-gsmopts command.

Command example:

chg-gsmopts:sporttype=all

where:

sporttype

Service Portability Type
Turn on the Service Portability feature using the chg-ctrl-feat command.

Command example:

chg-ctrl-feat:partnum=893034301:status=ON
Turn on the G-Port SRI Query for Prepaid feature using the chg-ctrl-feat command.

Command example:

chg-ctrl-feat:partnum=893017701:status=ON

The G-Port SRI Query for Prepaid feature is now enabled, turned on, and operating in the system. SRI messages received for G-Port SRI Query for Prepaid will receive Service Portability processing only if the optional Service Portability feature is enabled and turned on.

4.9 GSM MAP SRI Redirect to Serving HLR Feature Activation Procedure

This procedure is used to activate the GSM MAP SRI Redirect to Serving HLR feature.

Before this feature can be enabled, the G-Port feature must be enabled and turned on.
The GSM MAP SRI Redirect to Serving HLR feature cannot be enabled with a Temporary Feature Access Key.
The GSM MAP SRI Redirect to Serving HLR feature cannot be turned off after the feature is turned on.

For details about the commands used in this procedure, see Commands User's Guide.

Verify that the G-Port Feature is enabled and turned on using the rtrv-ctrl-feat command.
If the G-Port Feature is not enabled and turned on, enable and turn on the G-Port feature using G-Port Feature Activation Procedure before proceeding.
Enter the enable-ctrl-feat command to enable the GSM MAP SRI Redirect to Serving HLR feature.
enable-ctrl-feat:partnum=893014001:fak=<Feature Access Key>
Enter the chg-prefix-feat command to relate the GSM MAP SRI Redirect to Serving HLR feature to vendor prefix values, and to specify the prefix numbers that associate to entries in the Vendor ID List. A maximum of 128 prefix values can be entered in the Vendor Prefix Table for the GSM MAP SRI Redirect to Serving HLR feature.

Command examples:

chg-prefix:feature="gsm map sri redirect"prefixnum=1:prefix=1004

chg-prefix:feature="gsm map sri redirect"prefixnum=2:prefix=1003

chg-prefix:feature="gsm map sri redirect"prefixnum=3:prefix=1004

where:

feature

Feature Name.

prefixnum

Prefix Number. GSM MAP SRI Redirect to Serving HLR feature uses 1 - 128.

prefix

Prefix Value.
Verify the Vendor Prefix Table entries using the rtrv-prefix command.
Enter Vendor ID Length for the Vendor ID List using the ent-vendid command.

Command example:

ent-vendid:vendidlen=6

where:

vendidlen

Vendor ID Length. All Vendor IDs defined for the GSM MAP SRI Redirect to Serving HLR feature must contain this number of digits.
Enter the Vendor IDs and Vendor Numbers using the ent-vendid command.

Command example:

ent-vendid:vendid=886932:vendnum=1:vendtype=1

ent-vendid:vendid=886936:vendnum=1:vendtype=1

ent-vendid:vendid=886935:vendnum=2:vendtype=2

ent-vendid:vendid=886938:vendnum=3:vendtype=1

where:

vendid

Vendor ID.

vendnum

Vendor Number, used as a reference to the Vendor prefix.

vendtype

Vendor Type.
Verify that all G-Port provisioning information is specified: service selector, HomeRN deletions, default GTT, and GSMOPTS values.
Enter the chg-ctrl-feat command to turn on the GSM MAP SRI Redirect to Serving HLR feature.
chg-ctrl-feat:partnum=893014001:status=ON

The GSM MAP SRI Redirect to Serving HLR feature is now enabled, turned on, and operating in the system.