Go to primary content
Oracle® Communications EAGLE Database Administration - GTT User's Guide
Release 46.8
F11880-02
Go To Table Of Contents
Contents

Previous
Previous
Next
Next

Changing Global Title Address Information

This procedure is used to change existing global title address (GTA) information in the database using the chg-gta command.

The chg-gta command uses these parameters.

:gttsn – The GTT set name.

:gta – The start of global title address.

:egta – The end of global title address.

:pc/pca/pci/pcn/pcn24 – The translated point code.

:ssn – The translated subsystem number.

:ri – The routing indicator.

:xlat – The translate indicator.

:ccgt – The cancel called global title indicator.

:force – The check mated application override.

:actsn – The name of the GTT action set that will be assigned to the GTA entry as shown in the rtrv-gttaset output.

:gtmodid – The name of the GT modification identifier that will be assigned to the GTA entry as shown in the rtrv-gtmod output and provisioned in the Adding Global Title Modification Information procedure. The GT modification identifier contains the information to modify the numbering plan, nature of address indicator, and the prefix or suffix digits in the called party address or calling party address portion of outbound MSUs.

:ppmeasreqd – This parameter specifies whether per-path measurements are required for the GTA entry.

:mrnset – The MRN set ID, shown in the rtrv-mrn command. The mrnset parameter can be specified only if the Flexible GTT Load Sharing feature is enabled. If the Flexible GTT Load Sharing feature is enabled and the ri parameter value will be ri=gt when this procedure is completed, and the original global title translation being changed in this procedure did not have an MRN set ID assigned to it, the mrnset parameter must be specified with the chg-gta command. The MRN set ID assigned to the global title translation in this step must contain the point code value that will be assigned to the global title translation being changed in this step.

:mapset – The MAP set ID, shown in the rtrv-mrn command. The mapset parameter can be specified only if the Flexible GTT Load Sharing feature is enabled. If the Flexible GTT Load Sharing feature is enabled and the ri parameter value will be ri=ssn when this procedure is completed, and the original global title translation being changed in this procedure did not have a MAP set ID assigned to it, the mapset parameter must be specified with the chg-gta command. The MAP set ID assigned to the global title translation in this step must contain the point code and SSN values that will be assigned to the global title translation being changed in this step.

The status of the Flexible GTT Load Sharing feature is shown in the rtrv-ctrl-feat output. To enable the Flexible GTT Load Sharing feature, perform Activating the Flexible GTT Load Sharing Feature.

:optsn – The optional GTT set name shown in the rtrv-gttset output. Table 4-38 shows the types of GTT sets that can be specified for the optsn parameter based on the type of GTT set that is specified for the gttsn parameter and the features that are enabled and turned on.

Table 4-38 GTTSN and OPTSN Combinations

GTTSN Set Type OPTSN Set Type
Origin-Based SCCP Routing Feature Enabled Only
CDGTA

CGGTA, CGPC

The OPC GTT set type can be specified with a CDGTA GTT set, but the OPC GTT set is specified with the opcsn parameter.

CGGTA CGSSN
CGPC CGSSN
CGSSN The optsn parameter cannot be specified.
OPC CGSSN
Flexible Linkset Optional Based Routing Enabled and Turned On Only
CDGTA CDGTA, DPC, CDSSN
CDSSN CDSSN, DPC, CDGTA
DPC DPC, CDSSN, CDGTA
Origin-Based SCCP Routing Enabled and Flexible Linkset Optional Based Routing Enabled and Turned On Only
CDGTA

CDGTA, CGGTA, CGPC, CGSSN, CDSSN, DPC, OPC

The OPC GTT set type can be specified with a CDGTA GTT set, but the OPC GTT set is specified with the opcsn parameter.

CGGTA CDGTA, CGGTA, CGPC, CGSSN, OPC, CDSSN, DPC
CGPC CDGTA, CGGTA, CGPC, CGSSN, OPC, CDSSN, DPC
CGSSN CDGTA, CGGTA, CGPC, CGSSN, OPC, CDSSN, DPC
OPC CDGTA, CGGTA, CGPC, CGSSN, CDSSN, DPC, OPC
CDSSN CDGTA, CGGTA, CGPC, CGSSN, OPC, DPC, CDSSN
DPC CDGTA, CGGTA, CGPC, CGSSN, OPC, CDSSN, DPC
Flexible Linkset Optional Based Routing and TCAP Opcode Based Routing Feature Enabled and Turned On Only
CDGTA CDGTA, OPCODE, DPC, CDSSN
CDSSN CDSSN, OPCODE, DPC, CDGTA
OPCODE OPCODE, CDSSN, DPC, CDGTA
DPC DPC, OPCODE, CDSSN, CDGTA
Origin-Based SCCP Routing Enabled, Flexible Linkset Optional Based Routing and TCAP Opcode Based Routing Feature Enabled and Turned On
CDGTA

CDGTA, CGGTA, CGPC, CGSSN, CDSSN, OPCODE, DPC, OPC

The OPC GTT set type can be specified with a CDGTA GTT set, but the OPC GTT set is specified with the opcsn parameter.

CGGTA

CDGTA, CGGTA, CGPC, CGSSN, CDSSN, OPCODE, OPC, DPC

The opcsn parameter cannot be specified.

CGPC

CDGTA, CGGTA, CGPC, CGSSN, CDSSN, OPCODE, OPC, DPC

The opcsn parameter cannot be specified.

CGSSN

CDGTA, CGGTA, CGPC, CGSSN, CDSSN, OPCODE, OPC, DPC

The opcsn parameter cannot be specified.

OPC CDGTA, CGGTA, CGPC, CGSSN, CDSSN, OPCODE, OPC, DPC
CDSSN

CDGTA, CGGTA, CGPC, CGSSN, CDSSN, OPCODE, DPC, OPC

The OPC GTT set type can be specified with a CDSSN GTT set, but the OPC GTT set is specified with the opcsn parameter.

OPCODE

CDGTA, CGGTA, CGPC, CGSSN, CDSSN, OPCODE, DPC, OPC

The OPC GTT set type can be specified with an OPCODE GTT set, but the OPC GTT set is specified with the opcsn parameter.

DPC

CDGTA, CGGTA, CGPC, CGSSN, CDSSN, OPCODE, DPC, OPC

The OPC GTT set type can be specified with a DPC GTT set, but the OPC GTT set is specified with the opcsn parameter.

:opcsn – The OPC GTT set name shown in the rtrv-gttset output.

:cgssn – The CGPA subsystem number or the beginning value of a range of CGPA subsystem numbers

:ecgssn – The end value of a range of CGPA subsystem numbers

:cgpc/cgpca/cgpci/cgpcn/cgpcn24 – The CGPA point code

:opc/opca/opci/opcn/opcn24 – The originating point code

:dpc/dpca/dpci/dpcn/dpcn24 – The destination point code

:cdssn – The CdPA subsystem number or the beginning value of a range of CdPA subsystem numbers

:ecdssn – The end value of a range of CdPA subsystem numbers

:cgselid – The CgPA selector ID

:cdselid – The CdPA selector ID

:fallback – The action to be taken when the final translation does not match while performing global title translation using a FLOBR-specific GTT mode.

:testmode – This parameter invokes a field-safe test tool to debug the rules used for the Flexible Linkset Optional Based Routing or TCAP Opcode Based Routing features.

:cgcnvsn – The CgPA conversion set name

:family – The ANSI TCAP family field in the incoming message

:opcode – The TCAP opcode field in the incoming message

:pkgtype – The TCAP package type. Table 4-46 shows the ANSI and ITU TCAP package types.

:acn – The application context name (ACN) field in the ITU TCAP message

:loopset - The value of this parameter is the name of the loopset that is assigned to the GTA. This parameter can be specified only if the SCCP Loop Detection feature is enabled. Enter the rtrv-loopset command to verify that the SCCP Loop Detection feature is enabled. Perform the Activating the SCCP Loop Detection Feature procedure, if necessary.

:cggtmod - The calling party GT modification indicator. This parameter specifies whether or not calling party global title modification is required. The values for this parameter are yes (calling party global title modification is required) or no (calling party global title modification is not required). This parameter can be specified only if the AMGTT or AMGTT CgPA Upgrade feature is enabled. Enter the rtrv-ctrl-feat command to verify that either the AMGTT or AMGTT CgPA Upgrade feature is enabled. If the AMGTT or AMGTT CgPA Upgrade feature is not enabled, perform the Activating the Advanced GT Modification Feature procedure to enable the required feature.

:split – Split or change the range of global title addresses. If the split=yes parameter is specified, the existing range of global title addresses is split based on the values of the gta and egta parameters. New entries are created in the global title translation table for each new range created by the split parameter. The attributes of each new entry, other than the range of global title addresses, are the same as the original global title translation entry, if these values are not changed when the chg-gta command is executed. If other attributes are changed when the chg-gta command is executed, the changed values are in each new entry created by the split parameter.

If the split=no parameter is specified, the range of global title addresses is replaced with the new range of global title addresses specified by the gta and egta parameters.

The default value for the split parameter is yes.

Caution:

Changes to the range of global title addresses occur only if the both the gta and egta parameters are specified and the values for either of these parameters, or both parameters are different from the original values in the global title translation. If the gta and egta parameters are specified for the global title translation being changed, and you do not wish to change either of these values, make sure the gta and egta values shown in the rtrv-gta output for the global title translation being changed are specified in the chg-gta command.

The following examples illustrate how the split parameter works and ranges of global title addresses can be changed.

A global title translation entry in the database contains this range of global title addresses, 5556000 - 5558000.

rlghncxa03w 10-07-07 00:28:31 GMT EAGLE5 42.0.0
GTTSN     NETDOM  NDGT
tst1      ansi    7
GTA TABLE IS     (17 of 269999)  1 % FULL
START GTA  END GTA    XLAT   RI     PC
5556000    5558000    dpcssn ssn    001-255-252
     MAPSET=1     SSN=254 CCGT=no CGGTMOD=NO
     GTMODID=modid2     TESTMODE=off
     LOOPSET = rtp2     FALLBACK=sysdflt
     OPTSN=--------- CGSELID=----- OPCSN=gttset12
     ACTSN=--------- PPMEASREQD= NO

The global title translation is changed with a new range of global title addresses, 5556800 - 5559000, and with the split=no parameter.

chg-gta:ttn=tst1:gta=5556800:egta=5559000:split=no

The range of global title addresses is changed to 5556800 - 5559000.

rlghncxa03w 10-07-07 00:28:31 GMT EAGLE5 42.0.0
GTTSN     NETDOM  NDGT
tst1      ansi    7
GTA TABLE IS     (17 of 269999)  1 % FULL
START GTA  END GTA    XLAT   RI     PC
5556800    5559000    dpcssn ssn    001-255-252
     MAPSET=1     SSN=254 CCGT=no CGGTMOD=NO
     GTMODID=modid2     TESTMODE=off
     LOOPSET = rtp2     FALLBACK=sysdflt
     OPTSN=--------- CGSELID=----- OPCSN=gttset12
     ACTSN=--------- PPMEASREQD= NO

In this example, the range of global title addresses is made smaller by specifying the range of global title addresses 5556500 - 5557500, and with the split=no parameter.

chg-gta:ttn=tst1:gta=5556500:egta=5557500:split=no

rlghncxa03w 10-07-07 00:28:31 GMT EAGLE5 42.0.0
GTTSN     NETDOM  NDGT
tst1      ansi    7
GTA TABLE IS   1 % FULL  (17 of 269999)
START GTA  END GTA    XLAT   RI     PC
5556500    5557500    dpcssn ssn    001-255-252
     MAPSET=1     SSN=254 CCGT=no CGGTMOD=NO
     GTMODID=modid2     TESTMODE=off
     LOOPSET = rtp2     FALLBACK=sysdflt
     OPTSN=--------- CGSELID=----- OPCSN=gttset12
     ACTSN=--------- PPMEASREQD= NO

In this next example, the range of global title addresses is split with the gta=5556900 and egta=5557000 defining where the splits occur.

chg-gta:ttn=tst1:gta=5556900:egta=5557000

Since the default value for the split parameter is yes, the split=yes parameter does not have to be specified to split the range of global title addresses. When the chg-gta command is entered, three new global title translation entries with the new global title address ranges are created, and the original global title translation entry is removed from the database. Since the gta and egta parameter values specified in this example are within the original range of global title addresses, the original range of global title addresses is split into three new ranges. The START GTA value of the first new range is the original START GTA value and the END GTA value is the gta parameter value minus one. The START GTA value of the second new range is the gta parameter value and the END GTA value is the egta parameter value. The START GTA value of the third new range is the egta parameter value plus 1 and the END GTA value is the original END GTA value.

rlghncxa03w 10-07-07 00:28:31 GMT EAGLE5 42.0.0
GTTSN     NETDOM  NDGT
tst1      ansi    7
GTA TABLE IS   1 % FULL  (17 of 269999)

START GTA  END GTA    XLAT   RI     PC
5556000    5556899    dpcssn ssn    001-255-252
     MAPSET=1     SSN=254 CCGT=no CGGTMOD=NO
     GTMODID=modid2     TESTMODE=off
     LOOPSET = rtp2     FALLBACK=sysdflt
     OPTSN=--------- CGSELID=----- OPCSN=gttset12
     ACTSN=--------- PPMEASREQD= NO

rlghncxa03w 10-07-07 00:28:31 GMT EAGLE5 42.0.0
GTTSN     NETDOM  NDGT
tst1      ansi    7
GTA TABLE IS   1 % FULL  (17 of 269999)

START GTA  END GTA    XLAT   RI     PC
5556900    5557000    dpcssn ssn    001-255-252
     MAPSET=1     SSN=254 CCGT=no CGGTMOD=NO
     GTMODID=modid2     TESTMODE=off
     LOOPSET = rtp2     FALLBACK=sysdflt
     OPTSN=--------- CGSELID=----- OPCSN=gttset12
     ACTSN=--------- PPMEASREQD= NO

rlghncxa03w 10-07-07 00:28:31 GMT EAGLE5 42.0.0
GTTSN     NETDOM  NDGT
tst1      ansi    7
GTA TABLE IS   1 % FULL  (17 of 269999)

START GTA  END GTA    XLAT   RI     PC
5557001    5558000    dpcssn ssn    001-255-252
     MAPSET=1     SSN=254 CCGT=no CGGTMOD=NO
     GTMODID=modid2     TESTMODE=off
     LOOPSET = rtp2     FALLBACK=sysdflt
     OPTSN=--------- CGSELID=----- OPCSN=gttset12
     ACTSN=--------- PPMEASREQD= NO

In this next example, the global title translation containing the range of global title addresses 5557001 - 5558000 is split into two new ranges with the gta=5557501 and egta=5558000 defining where the split occurs.

chg-gta:ttn=tst1:gta=5557501:egta=5558000:split=yes

When the chg-gta command is entered, two new global title translation entries with the new global title address ranges are created, and the original global title translation entry is removed from the database. The START GTA value of the first new range is the original START GTA value and the END GTA value is the gta parameter value minus one. The START GTA value of the second new range is the gta parameter value and the END GTA value is the egta parameter value. In this example, the egta parameter is also the original END GTA value.

rlghncxa03w 10-07-07 00:28:31 GMT EAGLE5 42.0.0
GTTSN     NETDOM  NDGT
tst1      ansi    7
GTA TABLE IS   1 % FULL  (17 of 269999)

START GTA  END GTA    XLAT   RI     PC
5557001    5557500    dpcssn ssn    001-255-252
     MAPSET=1     SSN=254 CCGT=no CGGTMOD=NO
     GTMODID=modid2     TESTMODE=off
     LOOPSET = rtp2     FALLBACK=sysdflt
     OPTSN=--------- CGSELID=----- OPCSN=gttset12
     ACTSN=--------- PPMEASREQD= NO

rlghncxa03w 10-07-07 00:28:31 GMT EAGLE5 42.0.0
GTTSN     NETDOM  NDGT
tst1      ansi    7
GTA TABLE IS   1 % FULL  (17 of 269999)

START GTA  END GTA    XLAT   RI     PC
5557501    5558000    dpcssn ssn    001-255-252
     MAPSET=1     SSN=254 CCGT=no CGGTMOD=NO
     GTMODID=modid2     TESTMODE=off
     LOOPSET = rtp2     FALLBACK=sysdflt
     OPTSN=--------- CGSELID=----- OPCSN=gttset12
     ACTSN=--------- PPMEASREQD= NO

The range of global title addresses can be changed so long as the new range of global title addresses does not overlap an existing range of global title addresses.

For example, using the range of global title addresses from the previous examples, 5556000 - 5558000, you wish to extend the range of global title addresses to 5556000 - 5559000. The range of global title addresses can be extended to 5559000 by specifying the egta=5559000 and split=no parameters with the chg-gta command. However, if another range of global title addresses begins with the value 5558500, the egta=5559000 parameter cannot be specified with the chg-gta command as the new range created with the egta=5559000 parameter would overlap the range of global title addresses beginning with the value 5558500. In this situation, the maximum value for the egta parameter would be 5558499.

Note:

The command line on the terminal can contain up to 150 characters. If the parameters and values specified with the chg-gta command are too long to fit on the chg-gta command line, perform the chg-gta command as many times as necessary to complete the GTA entry.

The GTT set name (gttsn) must be specified and match that of an existing GTT set name. Use the rtrv-gttset command to view the GTT set names. If the specified GTT set is an ANSI set, the pc or pca value must be a valid ANSI point code. If the specified GTT set is an ITU set, the pci, pcn, or pcn24 value must be a valid ITU point code. The point code (PC) must be a full point code and cannot be out of range. If the ANSI/ITU SCCP Conversion feature is enabled, the domain (ANSI or ITU) of the GTT set name and point code do not have to be the same.

Note:

See Chapter 2, Configuring Destination Tables in Database Administration - SS7 User's Guide for a definition of the point code types that are used on the EAGLE and for a definition of the different formats that can be used for ITU national point codes.

If the end of the global title address (EGTA) parameter is specified, GTA and EGTA must have the same number of digits, but EGTA must be larger than GTA. The range, as specified by the start and end global title addresses, must be in the database for the specified translation type. Each range may be contained completely within a previously defined range, in which case splitting is performed. However, if the ranges overlap, splitting cannot occur, and the chg-gta command is rejected with this message.

E2401 Cmd Rej:GTA range overlaps a current range

Along with error message 2401, a list of the overlapped global title addresses is displayed as shown in the following example.

rlghncxa03w 09-05-07 00:28:31 GMT EAGLE5 41.0.0
The following GTA ranges overlap the input GTA range

START GTA               END GTA
8005550000              8005551999
8005552000              8005553999
8005554000              8005555999

CHG-GTA: MASP A - Command Aborted
If a point code is the STP’s True PC, then the value of the XLAT parameter must be set to DPCSSN and the value of the RI parameter must be set to SSN. If the SSN parameter is specified and a point code is the STP’s True PC, then the subsystem number specified must exist in the SS-APPL table. This can be verified with the rtrv-ss-appl command. To execute the rtrv-ss-appl command, these features must be enabled, and turned on if necessary.
  • LNP - shown by the entry LNP TNs with a quantity greater than zero in the rtrv-ctrl-feat command output
  • ATINP - shown by the entry ATINP in the rtrv-ctrl-feat command output with the status set to on
  • EIR - shown by the entry EIR in the rtrv-ctrl-feat command output as being permanently or temporarily enabled and with the status set to on.
  • INP - shown by the entry INP in the rtrv-ctrl-feat command output with the status set to on.
  • V-FLEX - shown by the entry VFLEX in the rtrv-ctrl-feat command output with the status set to on.
  • ANSI-41 INP Query - shown by the entry ANSI-41 INP Query in the rtrv-ctrl-feat command output with the status set to on.
  • ANSI41 AIQ - shown by the entry ANSI41 AIQ in the rtrv-ctrl-feat command output.

Note:

The Local Number Portability (LNP), Equipment Identity Register (EIR), INAP Number Portability (INP), V-Flex, ATINP, ANSI41 AIQ, or ANSI-41 INP Query features must be purchased before you can enable the LNP, ATINP, or ANSI41 AIQ features, or enable and turn on the EIR, INP, V-Flex, or ANSI-41 INP Query features. If you are not sure whether you have purchased the LNP, EIR, or INP, V-Flex, ATINP, or ANSI-41 INP Query feature, contact your Oracle Sales Representative or Account Representative.

Once the LNP, ATINP, or ANSI41 AIQ feature is enabled with the enable-ctrl-feat command, or the EIR, INP, V-Flex, and ANSI-41 INP Query features are turned on with the chg-ctrl-feat command, they cannot be turned off or disabled.

A point code must exist as a destination in the route table or reside in a cluster that exists as a destination in the route table (for global title routing) unless the point code is the STP’s True PC.

If a final GTT is specified (ri=ssn) with the xlat=dpc parameter, and the value of the force parameter is no, the point code must be in the Remote Point Code/Mated Application table. Verify this by entering the rtrv-map command. If this point code and subsystem number is not defined as a mated application, perform one of these procedures to add the point code and subsystem number to the database as a mated application:

The point code and subsystem number do not have to be in the mated application table when the chg-gta command is executed when these parameters are specified with the chg-gta command.

  • ri=gt
  • xlat=dpcssn and ri=ssn (provided the point code value is not the STP’s true point code)

If the point code and subsystem are not in the mated application table when either of these parameters are specified with the chg-gta command, the EAGLE creates a solitary mated application in the mated application table using the point code and subsystem values specified in the chg-gta command.

If the xlat=none parameter is specified for a global title translation, the global title translation entry can contain any data except for the routing data defined by these parameters.
  • pc/pca/pci/pcn/pcn24
  • ssn
  • ri
  • force=yes

The GTA Entries with the XLAT=NONE Parameter part of the GTT Actions section described the behavior of the xlat=none parameter.

The following tables show the valid parameter combinations that can be used with the chg-gta command.

The GTT table may not be full.

The values specified for the gta and egta parameters can be decimal digits (0-9) or hexadecimal digits (0-9, a-f, A-F). Hexadecimal digits can be specified only if the Hex Digit Support for GTT feature is enabled. Verify the status of the Hex Digit Support for GTT feature with the rtrv-ctrl-feat command. Refer to the Hex Digit Support for GTT section for more information on this feature. If the Hex Digit Support for GTT feature is not enabled, perform the Activating the Hex Digit Support for GTT Feature procedure to enable the Hex Digit Support for GTT feature.

Canceling the RTRV-GTA Command

Because the rtrv-gta command used in this procedure can output information for a long period of time, the rtrv-gta command can be canceled and the output to the terminal stopped. There are three ways that the rtrv-gta command can be canceled.

  • Press the F9 function key on the keyboard at the terminal where the rtrv-gta command was entered.
  • Enter the canc-cmd without the trm parameter at the terminal where the rtrv-gta command was entered.
  • Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-gta command was entered, from another terminal other that the terminal where the rtrv-gta 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.

For more information about the canc-cmd command, go to Commands User's Guide.

Table 4-39 GTA Parameter Combinations - No SETTYPE Column in RTRV-GTTSET Output

Mandatory Parameters
GTTSN – The GTT set name from the GTTSN column of the rtrv-gttset output and from the GTTSN column of the rtrv-gta output.
GTA – The GTA value assigned to the GTTSN value in the rtrv-gta output.
If only the EGTT feature is on, the SETTYPE column is not shown in the rtrv-gttset output.
Optional Parameters

EGTA – 1 - 21 digits or 1 - 21 hexadecimal digits.

Default = same as the GTA value.

Hexadecimal digits (0-9, a-f, A-F) can be specified for the egta parameters only if the Hex Digit support for GTT feature is enabled.

The length of the EGTA value must be the same as the GTA value.

There are other optional parameters that can be used with this entry. Refer to Table 4-48 for these parameters. At least one optional parameter must be specified with the chg-gta command. Unless a default value is shown for a parameter in Table 4-48, the value of any optional parameter that is not specified with the chg-gta command is not changed.

Table 4-40 GTTSN = CDGTA GTT Set Parameter Combinations

XLAT=DPCNGT, DPCSSN, or DPC XLAT=NONE
Mandatory Parameters
GTTSN – The GTT set name from the GTTSN column of the rtrv-gttset output containing the value CDGTA in the SETTYPE column and from the GTTSN column of the rtrv-gta output. GTTSN – The GTT set name from the GTTSN column of the rtrv-gttset output containing the value CDGTA in the SETTYPE column and from the GTTSN column of the rtrv-gta output.
GTA – The GTA value assigned to the GTTSN value in the rtrv-gta output. GTA – The GTA value assigned to the GTTSN value in the rtrv-gta output.
Optional Parameters

EGTA – 1 - 21 digits or 1 - 21 hexadecimal digits.

Default = same as the GTA value.

Hexadecimal digits (0-9, a-f, A-F) can be specified for the egta parameters only if the Hex Digit support for GTT feature is enabled.

The length of the EGTA value must be the same as the GTA value.

EGTA – 1 - 21 digits or 1 - 21 hexadecimal digits.

Default = same as the GTA value.

Hexadecimal digits (0-9, a-f, A-F) can be specified for the egta parameters only if the Hex Digit support for GTT feature is enabled.

The length of the EGTA value must be the same as the GTA value. These parameters cannot be specified with the xlat=none parameter.
  • pc/pca/pci/pcn/pcn24
  • ssn
  • ri
  • force=yes

OPTSN – The GTT set name from the GTTSN column of the rtrv-gttset output, or the value none. The value none removes the OPTSN value from the GTA entry. Refer to Table 4-38 for the valid GTT set types that can be specified.

The current value of this parameter must be changed to the value none before the parameter value can be changed to another value that is not none. The new value for this parameter cannot be the gttsn value specified with the chg-gta command.

 

OPCSN – The GTT set name from the GTTSN column of the rtrv-gttset output containing the value OPC in the SETTYPE column, or the value none. The value none removes the OPCSN value from the GTA entry.

 
There are other optional parameters that can be used with this entry. Refer to Table 4-48 for these parameters. At least one optional parameter must be specified with the chg-gta command. Unless a default value is shown for a parameter in Table 4-48, the value of any optional parameter that is not specified with the chg-gta command is not changed.
Note: When the xlat parameter value is changed from dpcngt, dpcssn, or dpc, to none, all the optional parameter values that are not specified with the chg-gta command are not changed. However, these changes are made.
  • The PC and SSN values are removed from the GTA entry.
  • The CCGT value is removed from the GTA entry and the CCGT field is not shown in the rtrv-gta output.
  • If the original RI value for the GTA entry was SSN and a MAP set was assigned to the GTA entry, the MAPSET value is not changed and the MRNSET=DFLT entry is assigned to the GTA entry. The MRNSET=DFLT entry is shown in the rtrv-gta output.
  • If the original RI value for the GTA entry was GT and an MRN set was assigned to the GTA entry, the MRNSET value is not changed and the MAPSET=DFLT entry is assigned to the GTA entry. The MAPSET=DFLT entry is shown in the rtrv-gta output.

Table 4-41 GTTSN = CGGTA GTT Set Parameter Combinations

XLAT=DPCNGT, DPCSSN, or DPC XLAT=NONE
Mandatory Parameters
GTTSN – The GTT set name from the GTTSN column of the rtrv-gttset output containing the value CGGTA in the SETTYPE column and from the GTTSN column of the rtrv-gta output. GTTSN – The GTT set name from the GTTSN column of the rtrv-gttset output containing the value CGGTA in the SETTYPE column and from the GTTSN column of the rtrv-gta output.
GTA – The GTA value assigned to the GTTSN value in the rtrv-gta output. GTA – The GTA value assigned to the GTTSN value in the rtrv-gta output.
Optional Parameters

EGTA – 1 - 21 digits or 1 - 21 hexadecimal digits.

Default = same as the GTA value.

Hexadecimal digits (0-9, a-f, A-F) can be specified for the egta parameters only if the Hex Digit support for GTT feature is enabled.

The length of the EGTA value must be the same as the GTA value.

EGTA – 1 - 21 digits or 1 - 21 hexadecimal digits.

Default = same as the GTA value.

Hexadecimal digits (0-9, a-f, A-F) can be specified for the egta parameters only if the Hex Digit support for GTT feature is enabled.

The length of the EGTA value must be the same as the GTA value. These parameters cannot be specified with the xlat=none parameter.
  • pc/pca/pci/pcn/pcn24
  • ssn
  • ri
  • force=yes

OPTSN – The GTT set name from the GTTSN column of the rtrv-gttset output, or the value none. The value none removes the OPTSN value from the GTA entry. Refer to Table 4-38 for the valid GTT set types that can be specified.

The current value of this parameter must be changed to the value none before the parameter value can be changed to another value that is not none. The new value for this parameter cannot be the gttsn value specified with the chg-gta command.

 
There are other optional parameters that can be used with this entry. Refer to Table 4-48 for these parameters. At least one optional parameter must be specified with the chg-gta command. Unless a default value is shown for a parameter in Table 4-48, the value of any optional parameter that is not specified with the chg-gta command is not changed.
Note: When the xlat parameter value is changed from dpcngt, dpcssn, or dpc, to none, all the optional parameter values that are not specified with the chg-gta command are not changed. However, these changes are made.
  • The PC and SSN values are removed from the GTA entry.
  • The CCGT value is removed from the GTA entry and the CCGT field is not shown in the rtrv-gta output.
  • If the original RI value for the GTA entry was SSN and a MAP set was assigned to the GTA entry, the MAPSET value is not changed and the MRNSET=DFLT entry is assigned to the GTA entry. The MRNSET=DFLT entry is shown in the rtrv-gta output.
  • If the original RI value for the GTA entry was GT and an MRN set was assigned to the GTA entry, the MRNSET value is not changed and the MAPSET=DFLT entry is assigned to the GTA entry. The MAPSET=DFLT entry is shown in the rtrv-gta output.

Table 4-42 GTTSN = CGPC GTT Set Parameter Combinations

XLAT=DPCNGT, DPCSSN, or DPC XLAT=NONE
Mandatory Parameters
GTTSN – The GTT set name from the GTTSN column of the rtrv-gttset output containing the value CGPC in the SETTYPE column and from the GTTSN column of the rtrv-gta output. GTTSN – The GTT set name from the GTTSN column of the rtrv-gttset output containing the value CGPC in the SETTYPE column and from the GTTSN column of the rtrv-gta output.
CGPC/CGPCA/CGPCI/CGPCN/CGPCN24 – The CGPC value assigned to the GTTSN value in the rtrv-gta output. (See Note 1) CGPC/CGPCA/CGPCI/CGPCN/CGPCN24 – The CGPC value assigned to the GTTSN value in the rtrv-gta output. (See Note 1)
Optional Parameters

OPTSN – The GTT set name from the GTTSN column of the rtrv-gttset output, or the value none. The value none removes the OPTSN value from the GTA entry. Refer to Table 4-38 for the valid GTT set types that can be specified.

The current value of this parameter must be changed to the value none before the parameter value can be changed to another value that is not none. The new value for this parameter cannot be the gttsn value specified with the chg-gta command.

These parameters cannot be specified with the xlat=none parameter.
  • pc/pca/pci/pcn/pcn24
  • ssn
  • ri
  • force=yes

There are other optional parameters that can be used with this entry. Refer to Table 4-48 for these parameters. At least one optional parameter must be specified with the chg-gta command. Unless a default value is shown for a parameter in Table 4-48, the value of any optional parameter that is not specified with the chg-gta command is not changed.

The egta and split parameters cannot be specified with this entry.

Note:
  1. The cgpc/cgpca/cgpci/cgpcn/cgpcn24 parameters are used to assign either ANSI, ITU-I, ITU-I spare, 14-bit ITU-N, 14-bit ITU-N spare, or 24-bit ITU-N point codes as the CGPC parameter values.
    • cgpc/cgpca = ANSI point code
    • cgpci = ITU-I or ITU-I spare point code
    • cgpcn = 14-bit ITU-N or 14-bit ITU-N spare point code
    • cgpcn24 = 24-bit ITU-N point code.
  2. When the xlat parameter value is changed from dpcngt, dpcssn, or dpc, to none, all the optional parameter values that are not specified with the chg-gta command are not changed. However, these changes are made.
    • The PC and SSN values are removed from the GTA entry.
    • The CCGT value is removed from the GTA entry and the CCGT field is not shown in the rtrv-gta output.
    • If the original RI value for the GTA entry was SSN and a MAP set was assigned to the GTA entry, the MAPSET value is not changed and the MRNSET=DFLT entry is assigned to the GTA entry. The MRNSET=DFLT entry is shown in the rtrv-gta output.
    • If the original RI value for the GTA entry was GT and an MRN set was assigned to the GTA entry, the MRNSET value is not changed and the MAPSET=DFLT entry is assigned to the GTA entry. The MAPSET=DFLT entry is shown in the rtrv-gta output.

Table 4-43 GTTSN = CGSSN GTT Set Parameter Combinations

XLAT=DPCNGT, DPCSSN, or DPC XLAT=NONE
Mandatory Parameters
GTTSN – The GTT set name from the GTTSN column of the rtrv-gttset output containing the value CGSSN in the SETTYPE column and from the GTTSN column of the rtrv-gta output. GTTSN – The GTT set name from the GTTSN column of the rtrv-gttset output containing the value CGSSN in the SETTYPE column and from the GTTSN column of the rtrv-gta output.
CGSSN – The CGSSN value assigned to the GTTSN value in the rtrv-gta output. CGSSN – The CGSSN value assigned to the GTTSN value in the rtrv-gta output.
Optional Parameters
ECGSSN – 0 - 255. The ECGSSN value must be greater than the CGSSN value.

ECGSSN – 0 - 255. Default value – no ECGSSN value is specified. The ECGSSN value must be greater than the CGSSN value.

These parameters cannot be specified with the xlat=none parameter.
  • pc/pca/pci/pcn/pcn24
  • ssn
  • ri
  • force=yes

OPTSN – The GTT set name from the GTTSN column of the rtrv-gttset output, or the value none. The value none removes the OPTSN value from the GTA entry. Refer to Table 4-38 for the valid GTT set types that can be specified.

The current value of this parameter must be changed to the value none before the parameter value can be changed to another value that is not none. The new value for this parameter cannot be the gttsn value specified with the chg-gta command.

 

There are other optional parameters that can be used with this entry. Refer to Table 4-48 for these parameters. At least one optional parameter must be specified with the chg-gta command. Unless a default value is shown for a parameter in Table 4-48, the value of any optional parameter that is not specified with the chg-gta command is not changed.

The egta and split parameters cannot be specified with this entry.

Note: When the xlat parameter value is changed from dpcngt, dpcssn, or dpc, to none, all the optional parameter values that are not specified with the chg-gta command are not changed. However, these changes are made.
  • The PC and SSN values are removed from the GTA entry.
  • The CCGT value is removed from the GTA entry and the CCGT field is not shown in the rtrv-gta output.
  • If the original RI value for the GTA entry was SSN and a MAP set was assigned to the GTA entry, the MAPSET value is not changed and the MRNSET=DFLT entry is assigned to the GTA entry. The MRNSET=DFLT entry is shown in the rtrv-gta output.
  • If the original RI value for the GTA entry was GT and an MRN set was assigned to the GTA entry, the MRNSET value is not changed and the MAPSET=DFLT entry is assigned to the GTA entry. The MAPSET=DFLT entry is shown in the rtrv-gta output.

Table 4-44 GTTSN = OPC GTT Set Parameter Combinations

XLAT=DPCNGT, DPCSSN, or DPC XLAT=NONE
Mandatory Parameters
GTTSN – The GTT set name from the GTTSN column of the rtrv-gttset output containing the value OPC in the SETTYPE column and from the GTTSN column of the rtrv-gta output. GTTSN – The GTT set name from the GTTSN column of the rtrv-gttset output containing the value OPC in the SETTYPE column and from the GTTSN column of the rtrv-gta output.
OPC/OPCA/OPCI/OPCN/OPCN24 – The OPC value assigned to the GTTSN value in the rtrv-gta output. (See Note 1) OPC/OPCA/OPCI/OPCN/OPCN24 – The OPC value assigned to the GTTSN value in the rtrv-gta output. (See Note 1)
Optional Parameters

OPTSN – The GTT set name from the GTTSN column of the rtrv-gttset output, or the value none. The value none removes the OPTSN value from the GTA entry. Refer to Table 4-38 for the valid GTT set types that can be specified.

The current value of this parameter must be changed to the value none before the parameter value can be changed to another value that is not none. The new value for this parameter cannot be the gttsn value specified with the chg-gta command.

These parameters cannot be specified with the xlat=none parameter.
  • pc/pca/pci/pcn/pcn24
  • ssn
  • ri
  • force=yes

There are other optional parameters that can be used with this entry. Refer to Table 4-48 for these parameters. At least one optional parameter must be specified with the chg-gta command. Unless a default value is shown for a parameter in Table 4-48, the value of any optional parameter that is not specified with the chg-gta command is not changed.

The egta and split parameters cannot be specified with this entry.

Note:
  1. The opc/opca/opci/opcn/opcn24 parameters are used to assign either ANSI, ITU-I, ITU-I spare, 14-bit ITU-N, 14-bit ITU-N spare, or 24-bit ITU-N point codes as the OPC parameter values.
    • opc/opca = ANSI point code
    • opci = ITU-I or ITU-I spare point code
    • opcn = 14-bit ITU-N or 14-bit ITU-N spare point code
    • opcn24 = 24-bit ITU-N point code.
  2. When the xlat parameter value is changed from dpcngt, dpcssn, or dpc, to none, all the optional parameter values that are not specified with the chg-gta command are not changed. However, these changes are made.
    • The PC and SSN values are removed from the GTA entry.
    • The CCGT value is removed from the GTA entry and the CCGT field is not shown in the rtrv-gta output.
    • If the original RI value for the GTA entry was SSN and a MAP set was assigned to the GTA entry, the MAPSET value is not changed and the MRNSET=DFLT entry is assigned to the GTA entry. The MRNSET=DFLT entry is shown in the rtrv-gta output.
    • If the original RI value for the GTA entry was GT and an MRN set was assigned to the GTA entry, the MRNSET value is not changed and the MAPSET=DFLT entry is assigned to the GTA entry. The MAPSET=DFLT entry is shown in the rtrv-gta output.

Table 4-45 GTTSN = CDSSN GTT Set Parameter Combinations

XLAT=DPCNGT, DPCSSN, or DPC XLAT=NONE
Mandatory Parameters
GTTSN – The GTT set name from the GTTSN column of the rtrv-gttset output containing the value CDSSN in the SETTYPE column and from the GTTSN column of the rtrv-gta output. GTTSN – The GTT set name from the GTTSN column of the rtrv-gttset output containing the value CDSSN in the SETTYPE column and from the GTTSN column of the rtrv-gta output.
CDSSN – The CDSSN value assigned to the GTTSN value in the rtrv-gta output. CDSSN – The CDSSN value assigned to the GTTSN value in the rtrv-gta output.
Optional Parameters
ECDSSN – 0 - 255. The ECDSSN value must be greater than the CDSSN value.

ECDSSN – 0 - 255. Default value – no ECDSSN value is specified. The ECDSSN value must be greater than the CDSSN value.

These parameters cannot be specified with the xlat=none parameter.
  • pc/pca/pci/pcn/pcn24
  • ssn
  • ri
  • force=yes

OPTSN – The GTT set name from the GTTSN column of the rtrv-gttset output, or the value none. The value none removes the OPTSN value from the GTA entry. Refer to Table 4-38 for the valid GTT set types that can be specified.

The current value of this parameter must be changed to the value none before the parameter value can be changed to another value that is not none. The new value for this parameter cannot be the gttsn value specified with the chg-gta command.

 
OPCSN – The GTT set name from the GTTSN column of the rtrv-gttset output containing the value OPC in the SETTYPE column, or the value none. The value none removes the OPCSN value from the GTA entry.  

There are other optional parameters that can be used with this entry. Refer to Table 4-48 for these parameters. At least one optional parameter must be specified with the chg-gta command. Unless a default value is shown for a parameter in Table 4-48, the value of any optional parameter that is not specified with the chg-gta command is not changed.

The egta and split parameters cannot be specified with this entry.

Note: When the xlat parameter value is changed from dpcngt, dpcssn, or dpc, to none, all the optional parameter values that are not specified with the chg-gta command are not changed. However, these changes are made.
  • The PC and SSN values are removed from the GTA entry.
  • The CCGT value is removed from the GTA entry and the CCGT field is not shown in the rtrv-gta output.
  • If the original RI value for the GTA entry was SSN and a MAP set was assigned to the GTA entry, the MAPSET value is not changed and the MRNSET=DFLT entry is assigned to the GTA entry. The MRNSET=DFLT entry is shown in the rtrv-gta output.
  • If the original RI value for the GTA entry was GT and an MRN set was assigned to the GTA entry, the MRNSET value is not changed and the MAPSET=DFLT entry is assigned to the GTA entry. The MAPSET=DFLT entry is shown in the rtrv-gta output.

Table 4-46 GTTSN = OPCODE GTT Set Parameter Combinations

XLAT=DPCNGT, DPCSSN, or DPC XLAT=NONE
Mandatory Parameters
GTTSN – The GTT set name from the GTTSN column of the rtrv-gttset output containing the value OPCODE in the SETTYPE column and from the GTTSN column of the rtrv-gta output. GTTSN – The GTT set name from the GTTSN column of the rtrv-gttset output containing the value OPCODE in the SETTYPE column and from the GTTSN column of the rtrv-gta output.
OPCODE – The OPCODE value assigned to the GTTSN value in the rtrv-gta output. (See Note 4) OPCODE – The OPCODE value assigned to the GTTSN value in the rtrv-gta output.
ANSI TCAP Translation ITU TCAP Translation ANSI TCAP Translation ITU TCAP Translation
FAMILY – The FAMILY value assigned to the GTTSN and OPCODE values in the rtrv-gta output. ACN – The application context name assigned to the GTTSN and OPCODE values in the rtrv-gta output. FAMILY – The FAMILY value assigned to the GTTSN and OPCODE values in the rtrv-gta output. ACN – The application context name assigned to the GTTSN and OPCODE values in the rtrv-gta output.
PKGTYPE – The PKGTYPE context name assigned to the GTTSN, FAMILY, and OPCODE values in the rtrv-gta output. PKGTYPE – PKGTYPE – The PKGTYPE context name assigned to the GTTSN, ACN, and OPCODE values in the rtrv-gta output. PKGTYPE – The PKGTYPE context name assigned to the GTTSN, FAMILY, and OPCODE values in the rtrv-gta output. PKGTYPE – PKGTYPE – The PKGTYPE context name assigned to the GTTSN, ACN, and OPCODE values in the rtrv-gta output.
Optional Parameters

OPTSN – The GTT set name from the GTTSN column of the rtrv-gttset output, or the value none. The value none removes the OPTSN value from the GTA entry. Refer to Table 4-38 for the valid GTT set types that can be specified.

The current value of this parameter must be changed to the value none before the parameter value can be changed to another value that is not none. The new value for this parameter cannot be the gttsn value specified with the chg-gta command.

These parameters cannot be specified with the xlat=none parameter.
  • pc/pca/pci/pcn/pcn24
  • ssn
  • ri
  • force=yes
OPCSN – The GTT set name from the GTTSN column of the rtrv-gttset output containing the value OPC in the SETTYPE column. Default value – no OPC GTT set is specified.  

There are other optional parameters that can be used with this entry. Refer to Table 4-48 for these parameters. At least one optional parameter must be specified with the chg-gta command. Unless a default value is shown for a parameter in Table 4-48, the value of any optional parameter that is not specified with the chg-gta command is not changed.

The egta and split parameters cannot be specified with this entry.

Note: When the xlat parameter value is changed from dpcngt, dpcssn, or dpc, to none, all the optional parameter values that are not specified with the chg-gta command are not changed. However, these changes are made.
  • The PC and SSN values are removed from the GTA entry.
  • The CCGT value is removed from the GTA entry and the CCGT field is not shown in the rtrv-gta output.
  • If the original RI value for the GTA entry was SSN and a MAP set was assigned to the GTA entry, the MAPSET value is not changed and the MRNSET=DFLT entry is assigned to the GTA entry. The MRNSET=DFLT entry is shown in the rtrv-gta output.
  • If the original RI value for the GTA entry was GT and an MRN set was assigned to the GTA entry, the MRNSET value is not changed and the MAPSET=DFLT entry is assigned to the GTA entry. The MAPSET=DFLT entry is shown in the rtrv-gta output.

Table 4-47 GTTSN = DPC GTT Set Parameter Combinations

XLAT=DPCNGT, DPCSSN, or DPC XLAT=NONE
Mandatory Parameters
GTTSN – The GTT set name from the GTTSN column of the rtrv-gttset output containing the value DPC in the SETTYPE column. GTTSN – The GTT set name from the GTTSN column of the rtrv-gttset output containing the value DPC in the SETTYPE column.
DPC/DPCA/DPCI/DPCN/DPCN24 (See Notes 1, 2, and 3) DPC/DPCA/DPCI/DPCN/DPCN24 (See Notes 1, 2, and 3)
Optional Parameters

OPTSN – The GTT set name from the GTTSN column of the rtrv-gttset output, or the value none. The value none removes the OPTSN value from the GTA entry. Refer to Table 4-38 for the valid GTT set types that can be specified.

The current value of this parameter must be changed to the value none before the parameter value can be changed to another value that is not none. The new value for this parameter cannot be the gttsn value specified with the chg-gta command.

These parameters cannot be specified with the xlat=none parameter.
  • pc/pca/pci/pcn/pcn24
  • ssn
  • ri
  • force=yes
OPCSN – The GTT set name from the GTTSN column of the rtrv-gttset output containing the value OPC in the SETTYPE column, or the value none. The value none removes the OPCSN value from the GTA entry.  
There are other optional parameters that can be used with this entry. Refer to Table 4-48 for these parameters. The egta and split parameters cannot be specified with this entry.
Note: When the xlat parameter value is changed from dpcngt, dpcssn, or dpc, to none, all the optional parameter values that are not specified with the chg-gta command are not changed. However, these changes are made.
  • The PC and SSN values are removed from the GTA entry.
  • The CCGT value is removed from the GTA entry and the CCGT field is not shown in the rtrv-gta output.
  • If the original RI value for the GTA entry was SSN and a MAP set was assigned to the GTA entry, the MAPSET value is not changed and the MRNSET=DFLT entry is assigned to the GTA entry. The MRNSET=DFLT entry is shown in the rtrv-gta output.
  • If the original RI value for the GTA entry was GT and an MRN set was assigned to the GTA entry, the MRNSET value is not changed and the MAPSET=DFLT entry is assigned to the GTA entry. The MAPSET=DFLT entry is shown in the rtrv-gta output.

Table 4-48 Optional GTA Parameters

XLAT=DPCNGT, DPCSSN, or DPC XLAT=NONE
PC/PCA/PCI/PCN/PCN24 (See Notes 1, 2, and 3) MRNSET – MRN set ID from the rtrv-mrn output or none (See Note 4)
SSN – 0 - 255 (See Note 3) LOOPSET – Loopset name from the rtrv-loopset output (See Note 8)
RI – GT, SSN (See Notes 3, 4, 7) CGGTMOD – yes, no. Default = no (See Note 9)
MRNSET – MRN set ID from the rtrv-mrn output or none (See Note 4) MAPSET – MAP set ID from the rtrv-map output or none (See Note 7)
LOOPSET – Loopset name from the rtrv-loopset output (See Note 8) SPLIT – yes, no. Default = yes (See Note 10)
CGGTMOD – yes, no. Default = no (See Note 9) TESTMODE – on, off. Default = off.
CCGT – yes, no. (See Note 5) FALLBACK – sysdflt, yes, no. The Flexible Linkset Optional Based Routing feature must be enabled and turned on to use this parameter.
MAPSET – MAP set ID from the rtrv-map output or none (See Note 8) CGSELID – 0 - 65534 or none. The Origin-Based SCCP Routing feature must be enabled to use this parameter. (See Note 12)
FORCE – yes, no. Default = no (See Note 6) CDSELID – 0 - 65534 or none. The Flexible Linkset Optional Based Routing feature must be enabled and turned on to use this parameter. (See Note 12)
SPLIT – yes, no. Default = yes (See Note 10) CGCNVSN – GTT set name shown in the rtrv-gttset output or none. (See Note 13)
TESTMODE – on, off. Default = off. ACTSN – The name of the GTT action set name shown in the rtrv-gttaset output or none. (See Note 11)
FALLBACK – sysdflt, yes, no. The Flexible Linkset Optional Based Routing feature must be enabled and turned on to use this parameter. GTMODID – The name of the GT modification identifier shown in the rtrv-gtmod output or none. The value none removes the GT modification identifier assignment from the GTA entry. If the NGTI value in the global title modification entry is 4, the point code that is assigned to the GTA entry must be an ITU point code.
CGSELID – 0 - 65534 or none. The Origin-Based SCCP Routing feature must be enabled to use this parameter. (See Note 12) PPMEASREQD – This parameter specifies whether per-path measurements are required for the GTA entry. This parameter has two values.
  • yes - per-path measurements are required for the GTA entry.
  • no - per-path measurements are not required for the GTA entry.
CDSELID – 0 - 65534 or none. The Flexible Linkset Optional Based Routing feature must be enabled and turned on to use this parameter. (See Note 12)  
CGCNVSN – GTT set name shown in the rtrv-gttset output or none. (See Note 13)  
ACTSN – The name of the GTT action set name shown in the rtrv-gttaset output or none. (See Note 11)  
GTMODID – The name of the GT modification identifier shown in the rtrv-gtmod output or none. The value none removes the GT modification identifier assignment from the GTA entry. If the NGTI value in the global title modification entry is 4, the point code that is assigned to the GTA entry must be an ITU point code.  
PPMEASREQD – This parameter specifies whether per-path measurements are required for the GTA entry. This parameter has two values.
  • yes - per-path measurements are required for the GTA entry.
  • no - per-path measurements are not required for the GTA entry.
 
Notes:
  1. The pc/pca/pci/pcn/pcn24 parameters are used to assign either ANSI, ITU-I, ITU-I spare, 14-bit ITU-N, 14-bit ITU-N spare, or 24-bit ITU-N point codes to the global title address (GTA).
    • pc/pca = ANSI point code
    • pci = ITU-I or ITU-I spare point code
    • pcn = 14-bit ITU-N or 14-bit ITU-N spare point code
    • pcn24 = 24-bit ITU-N point code.
  2. The domain (ANSI or ITU) of the point code and GTT set must be the same, unless the ANSI/ITU SCCP Conversion feature is enabled. If the ANSI/ITU SCCP Conversion feature is enabled, a GTA may contain an ANSI point code and an ITU GTT set, or an ITU point code and an ANSI GTT set. The CROSS GTT set, a GTT set containing the NETDOM value CROSS, can be specified with either ANSI or ITU point codes.
  3. If the point code is the EAGLE’s point code, then the xlat parameter value must bedpcssn and the ri parameter value must bessn. The ssn parameter can be specified only if the xlat parameter isdpcssn. If the xlat parameter value is being changed todpcssn, the ssn parameter must be specified.
  4. The mrnset parameter can be specified only, and must be specified, if the Flexible GTT Load Sharing feature is enabled. The mrnset parameter can be specified only if the ri parameter value isgt. Specifying the mrnset=none parameter removes the MRN set ID assignment from the GTA entry.
  5. If the point code is the EAGLE’s point code, then the value of the ccgt parameter must be set tono.
  6. If the pc/pca/pci/pcn/pcn24 parameter value is not shown in the rtrv-map output, and the resulting xlat parameter value is dpc, and the resulting ri parameter value is ssn, the force=yes parameter must be specified with the chg-gta command.
  7. The mapset parameter can be specified only, and must be specified, if the Flexible GTT Load Sharing feature is enabled. The mapset parameter can be specified only if the ri parameter value isssn. Specifying the mapset=none parameter removes the MAP set ID assignment from the GTA entry.
  8. The loopset parameter can be specified only if the SCCP Loop Detection feature is enabled.
  9. The cggtmod parameter can be specified only if the AMGTT or AMGTT CgPA Upgrade feature is enabled.
  10. The range of global title addresses assigned to a global title translation can be extended, reduced, or split to create a new range of global title addresses. See the split parameter description section in this procedure for information on changing the range of global title addresses.
  11. The actsn parameter can be specified only if the GTT Action - DISCARD, GTT Action - DUPLICATE, GTT Action - FORWARD feature is enabled. The value none removes the GTT action set name assignment from the GTA entry.
  12. The current value of this parameter must be changed to the value none before the parameter value can be changed to another value that is not none.
  13. The ANSI/ITU SCCP Conversion feature must be enabled, and the Flexible Linkset Optional Based Routing feature must be enabled and turned on to use this parameter. Specifying the cgcnvsn=none parameter removes the CGCNVSN value from the GTA entry. The current value of this parameter must be changed to the value none before the parameter value can be changed to another value that is not none. The new value for this parameter cannot be the gttsn value specified with the chg-gta command, but must be a GTT set whose set type is either CDGTA or CGGTA..
  1. Display the GTT sets in the database using the rtrv-gttset command.

    This is an example of the possible output.

    rlghncxa03w 09-07-07 00:29:31 GMT EAGLE5 41.1.0
    
    GTTSN      NETDOM  SETTYPE  NDGT
    abcd1234   itu     CGGTA    12
    gttset3    ansi    CGGTA    10
    gttset6    ansi    OPC      -
    gttset7    ansi    CGPC     -
    gttset12   ansi    OPC      -
    imsi       itu     CDGTA    15
    lidb       ansi    CDGTA    10
    t800       ansi    CDGTA    10
    s1000      itu     CDGTA    15
    s2000      itu     CGPC     -
    
    GTT-SET table is (10 of 2000) 1% full.
  2. Display the global title address (GTA) information for the GTT set that contains the global title address entry that is being changed. Use the rtrv-gta command with the gttsn parameter value shown in the output of 1. If the num parameter is specified with the rtrv-gta command, and the value of the num parameter is greater than 1000, the force=yes parameter must be specified with the rtrv-gta command. For this example, enter this command.

    rtrv-gta:gttsn=lidb

    This is an example of the possible output.

    rlghncxa03w 10-07-07 00:27:31 GMT EAGLE5 42.0.0
    
    GTTSN     NETDOM  SETTYPE  NDGT
    lidb      ansi    CDGTA    10
    GTA TABLE IS   1 % FULL  (17 of 269999)
    
    START GTA  END GTA    XLAT   RI     PC
    9195554321 9195554321 DPCNGT GT     001-255-253
         SSN=--- CCGT=no CGGTMOD=NO
         GTMODID=modid2     TESTMODE=off
         LOOPSET = none     FALLBACK=sysdflt
         OPTSN=--------- CGSELID=----- OPCSN=---------
         ACTSN=--------- PPMEASREQD= NO
    
    Command Retrieved 1 Entries
    If any of these conditions are present, this step has been completed.
    • The OPTSN, OPCSN, or CGCNVSN fields are not shown in the rtrv-gta output.
    • The OPTSN, OPCSN, or CGCNVSN fields are shown in the rtrv-gta output and the OPTSN, OPCSN, or CGCNVSN values are not being changed.
    • The OPTSN, OPCSN, or CGCNVSN fields are shown in the rtrv-gta output, the OPTSN, OPCSN, or CGCNVSN values are being changed, and the desired GTT set is shown in the rtrv-gttset output in 1.

    If the OPTSN, OPCSN, or CGCNVSN fields are shown in the rtrv-gta output, the OPTSN, OPCSN, or CGCNVSN values are being changed, and the desired GTT set is not shown in the rtrv-gttset output in 1, perform Adding a GTT Set to add the new GTT set.

    After this step has been completed, continue the procedure by performing one of these steps.
    • If the GTA entry does contains a range of global title addresses, CgPA subsystem numbers, or CdPA subsystem numbers, and this range will be split, continue the procedure with 3.
    • If the GTA entry does contains a range of global title addresses, CgPA subsystem numbers, or CdPA subsystem numbers, and this range will not be split, or if the GTA entry does not contain a range of global title addresses, CgPA subsystem numbers, or CdPA subsystem numbers, continue the procedure with 5.
  3. Splitting a range of global title addresses, CgPA subsystem numbers, or CdPA subsystem numbers creates a new GTA entry.

    If splitting the global title addresses, CgPA subsystem numbers, or CdPA subsystem numbers will increase the number of global title translations in the database beyond the maximum number of global title translations shown in the rtrv-gta output in 2, and the maximum number of global title translations is either 269,999 or 400,000, the maximum number of global title translations must be increased. Perform the Enabling the XGTT Table Expansion Feature procedure to increase the maximum number of global title translations. If the maximum number of global title translations is 1,000,000, the maximum number of global title translations cannot be increased. The range of global title addresses, CgPA subsystem numbers, or CdPA subsystem numbers cannot be split. This new entry cannot be created if the database contains the maximum number of GTA entries.

    Continue the procedure by performing one of these steps.
    • If the GTA entry does not contain a range of global title addresses, or the number of global title translations in the database will not be increased beyond the maximum number of global title translations shown in the rtrv-gta output in 2, continue the procedure with 5.
    • If the GTA entry contains a range of global title addresses that will be split and the number of global title translations in the database will not be increased beyond the maximum number of global title translations shown in the rtrv-gta output in 2, continue the procedure with 4.
  4. Display the GTT path entries by entering the rtrv-gttapath command with these parameters.
    • cdgttsn - the GTTSN value shown in the rtrv-gta output in 2.
    • cdgta - the START GTA value shown in the rtrv-gta output in 2.

    For this example, enter this command.

    rtrv-gttapath:cdgttsn=lidb:cdgta=9195554321

    This is an example of the possible output.

    rlghncxa03w 10-07-25 09:43:31 GMT  EAGLE5 42.0.0
    
    GTTPN   OPGTTSN         CGGTTSN         CDGTTSN
    --------------------------------------------------
    
    path1   ---------       ---------       lidb
        CDGTA = 9195554321                   ECDGTA = 9195554321
    
    
    GTT-PATH table is (5 of 10000) 1% full.

    The range of global title addresses cannot be split if entries containing the GTTSN and the GTA values shown in the rtrv-gttapath output. If entries are displayed in the rtrv-gttapath output, perform the Removing a GTT Action Path Entry procedure to remove the entries shown in the rtrv-gttapath output.

    Continue the procedure with 5 if no entries are shown in this step; error message E3451 is displayed; if the entries in the rtrv-gttapath output will not be removed; or the Removing a GTT Action Path Entry procedure has been performed.

  5. Display the features that are enabled by entering the rtrv-ctrl-feat command.

    The following is an example of the possible output.

    rlghncxa03w 09-05-28 21:15:37 GMT EAGLE5 41.0.0
    The following features have been permanently enabled:
    
    Feature Name              Partnum   Status Quantity
    XGTT Table Expansion      893006101 on     400000
    SCCP Loop Detection       893016501 on     ----
    SCCP Conversion           893012001 off    ----
    HC-MIM SLK Capacity       893012707 on     64
    Origin Based SCCP Routing 893014301 on     ----
    TCAP Opcode Based Routing 893027801 on     ----
    Flex Lset Optnl Based Rtg 893027701 on     ----
    VGTT with 16 GTT lengths  893024801 on     ----
    TOBR Opcode Quantity      893027907 on     1000000
    
    
    The following features have been temporarily enabled:
    
    Feature Name              Partnum   Status Quantity   Trial Period Left
    Zero entries found.
    
    
    The following features have expired temporary keys:
    
    Feature Name              Partnum
    Zero entries found.
  6. Some parameters of the chg-gta command can be specified only when certain features are enabled, and turned on if necessary. Table 4-49 shows the feature requirements for these parameters.found. Some

    Table 4-49 Feature Requirements for CHG-GTA Parameters

    Required Feature Parameters or Values
    Origin-Based SCCP Routing Enabled GTTSN - specifying CGGTA, CGPC, CGSSN, or OPC GTT sets
    OPTSN - specifying CGGTA, CGPC, or CGSSN GTT sets
    OPCSN
    CGPC
    CGSSN
    ECGSSN
    OPC
    CGSELID
    Flexible GTT Load Sharing Enabled MAPSET
    MRNSET
    Flexible Linkset Optional Based Routing Enabled and Turned On GTTSN - specifying CDSSN or DPC GTT sets
    OPTSN - specifying CDSSN or DPC GTT sets
    FALLBACK
    CDSSN
    ECDSSN
    CDSELID
    DPC
    ANSI/ITU SCCP Conversion Enabled and Flexible Linkset Optional Based Routing Enabled and Turned On CGCNVSN
    TCAP Opcode Based Routing Enabled and Turned On GTTSN - specifying OPCODE GTT sets
    OPTSN - specifying OPCODE GTT sets
    TOBR Quantity Enabled ACN
    FAMILY
    OPCODE
    PKGTYPE
    SCCP Loop Detection Enabled LOOPSET
    Advanced GT Modification or AMGTT CgPA Upgrade Enabled CGGTMOD
    ANSI/ITU SCCP Conversion Enabled The domain (ANSI or ITU) of the point code and the GTT set that will be assigned to the GTA entry will be different.
    Hex Digit Support for GTT Enabled Hexadecimal digits will be specified for the gta or egta parameter values.
    GTT Action - DISCARD, GTT Action - DUPLICATE, GTT Action - FORWARD Enabled ACTSN
    To enable, and turn on if necessary, any of these features, perform these procedures.

    If the required feature is enabled, and turned on if required, shown in the rtrv-ctrl-feat output in 5, the procedure for that feature does not need to be performed.

  7. To use either the mrnset parameter (if the routing indicator value for the global title translation is GT) or mapset parameter (if the routing indicator value for the global title translation is SSN), the Flexible GTT Load Sharing feature must be enabled. See 6. The mrnset and mapset parameters can be specified if the xlat=none parameter is specified for the GTA entry.

    If the Flexible GTT Load Sharing feature is enabled, the GTA entry must contain either an MRNSET or MAPSET value, depending on the routing indicator value for the global title translation being changed.

    If the routing indicator for the GTA entry that is being changed will be GT when this procedure is completed, continue the procedure by performing one of these steps.

    • If the Flexible GTT Load Sharing feature is not enabled and the point code value will not be changed, continue the procedure with 19.
    • If the Flexible GTT Load Sharing feature is not enabled, and the point code value will be changed, continue the procedure with 9.
    • If the Flexible GTT Load Sharing feature is enabled and the point code value will be changed, whether or not the MRNSET value will be changed, continue the procedure with 11.
    • If the Flexible GTT Load Sharing feature is enabled and the point code and MRNSET values will not be changed, continue the procedure with 19.

    If the routing indicator for the GTA entry that is being changed will be SSN when this procedure is completed, continue the procedure by performing one of these steps.

    • If the XLAT parameter value will be DPC when this procedure is completed, continue the procedure by performing one of these steps.
      • If the point code value will not be changed and the Flexible GTT Load Sharing feature is not enabled, continue the procedure with 19.
      • If the point code value will not be changed; the Flexible GTT Load Sharing feature is enabled and the MAPSET value will not be changed, continue the procedure with 19.
      • If the point code value will not be changed; the Flexible GTT Load Sharing feature is enabled and the MAPSET value will be changed, continue the procedure with 13.
      • If the point code value will be changed, continue the procedure with 13.
    • If the XLAT parameter value will be DPCSSN when this procedure is completed, continue the procedure by performing one of these steps.
      • If the point code, SSN, and MAPSET value (if the Flexible GTT Load Sharing feature is enabled) will not be changed, continue the procedure with 19.
      • If the point code will be changed, continue the procedure by performing one of these steps.
        • If the new point code value will not be the EAGLE’s point code, continue the procedure with 13.
        • If the new point code value will be the EAGLE’s point code, continue the procedure with 12.
      • If only the SSN value will be changed, continue the procedure with 12.
      • If the Flexible GTT Load Sharing feature is enabled and only the MAPSET value will be changed, continue the procedure with 12.

    If the xlat=none parameter will be specified and the Flexible GTT Load Sharing feature is not enabled, continue the procedure with 18.

    If the xlat=none parameter will be specified and the Flexible GTT Load Sharing feature is enabled, continue the procedure by performing one of these steps. Both the mrnset and mapset parameters can be specified for the GTA entry.

    • If the mrnset parameter will be specified, continue the procedure with 8.
    • If the mapset parameter will be specified, continue the procedure with 13.
  8. The point code and MRN set ID specified with the chg-gta command must be shown in the rtrv-mrn command output. The point code must be assigned to the MRN set that will be specified with the chg-gta command.

    Enter the rtrv-mrn command to verify that the required MRN set is configured in the database, and that the required point code is assigned to the MRN set. The following is an example of the possible output.

    rlghncxa03w 09-05-28 21:15:37 GMT EAGLE5 41.0.0
    
    MRNSET   PC             RC
    DFLT     001-001-001    10
             001-001-002    20
             001-001-003    30
             001-254-255    40
    
    MRNSET   PC             RC
    110      001-001-001    10
             001-001-005    20
             001-001-006    30
             001-001-003    40
             001-001-008    50
    
    MRNSET   PC             RC
    111      001-001-001    30
             001-001-005    30
             001-001-006    30
             001-001-003    30
             001-001-008    30
    
    MRNSET   PC             RC
    112      001-003-001    10
             001-003-002    10
             001-003-003    30
             001-003-004    30
             001-003-006    60
             001-003-007    60
             001-003-008    80
             001-003-009    80
    
    MRNSET   PCN               RC
    113      s-1-1-1-0123-aa   1
             s-1-1-1-0235-aa   2
             s-1-1-1-0235-aa   3

    Note:

    If the Weighted GTT Load Sharing feature is enabled, the WT, %WT, and THR columns are shown in the rtrv-mrn output.

    If the required MRN set is not shown in the rtrv-mrn output, or if the required point code is not assigned to the required MRN set, provision the required MRN set by performing the Provisioning MRN Entries procedure. After provisioning the required MRN set, continue the procedure with 18.

    If the required MRN set is shown in the rtrv-mrn output, or if the required point code is assigned to the required MRN set, continue the procedure with 18.

  9. Display the destination point codes in the database by entering the rtrv-dstn command. This is an example of the possible output.
    rlghncxa03w 10-12-10 11:43:04 GMT EAGLE5 43.0.0
    Extended Processing Time may be Required
    
       DPCA          CLLI        BEI ELEI   ALIASI           ALIASN/N24    DMN
       001-207-000   ----------- no  --- --------------   --------------   SS7
       001-001-001   ----------- no  --- --------------   --------------   SS7
       001-001-002   ----------- no  --- --------------   --------------   SS7
       001-005-000   ----------- no  --- --------------   --------------   SS7
       001-007-000   ----------- no  --- --------------   --------------   SS7
       008-012-003   ----------- no  --- --------------   --------------   SS7
       003-002-004   ----------- no  --- --------------   --------------   SS7
       009-002-003   ----------- no  --- --------------   --------------   SS7
       010-020-005   ----------- no  --- --------------   --------------   SS7
    
       DPCI          CLLI        BEI ELEI   ALIASA           ALIASN/N24    DMN
       1-207-0       ----------- no  --- --------------   --------------   SS7
       0-015-0       ----------- no  --- --------------   --------------   SS7
       0-017-0       ----------- no  --- --------------   --------------   SS7
       1-011-1       ----------- no  --- --------------   --------------   SS7
       1-011-2       ----------- no  --- --------------   --------------   SS7
    
    
    Destination table is (14 of 2000) 1% full
    Alias table is (0 of 12000) 0% full
    PPC table is (1 of 20) 5% full

    If the required point code is not shown in the rtrv-dstn output, perform the "Adding a Destination Point Code" procedure in Database Administration - SS7 User's Guide to add the required point code. A proxy point code cannot be assigned to the point code.

    After the new point code has been added, perform one of the Adding a Route procedures in Database Administration - SS7 User's Guide and add the required route to the database. After the route has been added, continue the procedure with 18.

    If the required point code is shown in the rtrv-dstn output, continue the procedure with 10.

  10. Display the point code that will be assigned to the mated application by using the rtrv-dstn command and specifying the point code. For this example, enter this command.

    rtrv-dstn:dpca=010-020-005

    This is an example of the possible output.

    rlghncxa03w 10-12-10 11:43:04 GMT EAGLE5 43.0.0
    
       DPCA          CLLI        BEI ELEI   ALIASI           ALIASN/N24    DMN
       010-020-005   ----------- no  --- --------------   --------------   SS7
    
       PPCA         NCAI PRX     RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
       009-002-003  ---- no      none   off   none     no     no    none
    
    Destination table is (14 of 2000) 1% full
    Alias table is (0 of 12000) 0% full
    PPC table is (1 of 20) 5% full

    A proxy point code (a point code value is shown in the PPC column) cannot be assigned to the point code. If a proxy point code is shown in this step, choose another point code from the rtrv-dstn output in the previous step and repeat this step.

    After the new point code has been added, perform one of the Adding a Route procedures in Database Administration - SS7 User's Guide and add the required route to the database. After the route has been added, continue the procedure with 18.

    If the point code displayed in this step does not contain a proxy point code, continue the procedure with 11.

  11. The point code specified with the chg-gta command must be the DPC of a route, unless the point code is the EAGLE’s point code.

    Enter the rtrv-rte command with the dpc parameter specifying the point code to be used with the chg-gta command to verify whether or not the point code is the DPC of a route. For this example, enter this command.

    rtrv-rte:dpca=001-255-252

    This is an example of the possible output.

    rlghncxa03w 09-05-07 11:43:04 GMT  EAGLE5 41.0.0
       DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
       001-255-252 ---------- --------------   ls07       10    001-255-252
                                               ls08       30    025-025-150
                                               lsa5       50    066-030-100
                                                   RTX:No  CLLI=ls07clli

    If the point code is not shown in the rtrv-rte output, perform one of the Adding a Route procedures in Database Administration - SS7 User's Guide and add the required route to the database.

    If the point code is shown in the rtrv-rte output, and a new route was added, continue the procedure with 18.

  12. If the ri=ssn and xlat=dpcssn parameters are specified with the chg-gta command, and you wish to use the EAGLE’s point code for the value of the pc parameter of the chg-gta command, the point code value must be in the EAGLE’s self ID table. Display the EAGLE self-identification, using the rtrv-sid command. This is an example of the possible output.
    rlghncxa03w 09-05-10 11:43:04 GMT EAGLE5 41.0.0
       PCA             PCI          PCN                CLLI              PCTYPE
       010-020-030     1-023-1      12-0-14-1          rlghncxa03w       OTHER
                     s-1-023-1    s-12-0-14-1
    
       CPCA
       002-002-002       002-002-003       002-002-004      002-002-005
       002-002-006       002-002-007       002-002-008      002-002-009
       004-002-001       004-003-003       050-060-070
       
    
       CPCI
       1-001-1           1-001-2           1-001-3          1-001-4
       1-002-1           1-002-2           1-002-3          1-002-4
       2-001-1           7-222-7
       
       CPCN
       2-0-10-3          2-0-11-0          2-0-11-2          2-0-12-1
       2-2-3-3           2-2-4-0           10-14-10-1
    Continue the procedure by performing one of these steps.
    • If the point code value will be changed to the EAGLE's point code, continue the procedure with 13.
    • If the SSN value will be changed and the current point code value is the EAGLE's point code, continue the procedure with 13.
    • If the MAPSET value will be changed, continue the procedure with 13.
  13. Enter the rtrv-map command with the pc parameter specifying the required point code to verify that the required data is in the mated application table.

    Note:

    If the Flexible GTT Load Sharing feature is enabled, a MAP set ID must be specified for the final global title translation. The point code and SSN specified for the final global title translation being changed in this procedure must be assigned to the MAP set ID that will be assigned to the final global title translation. Perform this step to verify that the required MAP set is configured in the database.

    If the point code value of the GTA entry is being changed, specify the new point code value of the GTA entry.

    If the point code value of the GTA entry is not being changed, specify the current point code value of the GTA entry.

    If the point code value of the GTA entry will be the EAGLE's point code, specify the EAGLE's point code, shown in 12. The MAP entry that contains the EAGLE's point code must be in the default MAP set.

    If the XLAT value of the GTA entry will be DPCSSN when this procedure is completed, and the SSN or MAPSET value will be changed, specify the new SSN value, if the SSN value will be changed, or the current SSN value, if the SSN value will not be changed, in this step.

    For this example enter this command.

    rtrv-map:pca=001-255-252

    rlghncxa03w 09-07-25 09:42:31  GMT  EAGLE5 41.1.0
    
    PCA          Mate PCA     SSN RC MULT SRM MRC GRP NAME SSO
    MAPSET ID=DFLT
    001-255-252                55  5  DOM YES YES -------- OFF
                 001-001-002   15 15  DOM YES YES -------- ON
                 001-001-003   25 20  DOM YES YES -------- ON
                 001-001-002   40 35  DOM YES YES -------- OFF
    MAPSET ID=1
    001-255-252               254  5  DOM YES YES -------- OFF
                 001-001-002   10 15  DOM YES YES -------- ON
                 001-001-003   20 20  DOM YES YES -------- ON
                 001-001-002   40 35  DOM YES YES -------- OFF
    MAPSET ID=2
    001-255-252                 5 10  SOL *Y  *Y  -------- OFF
    
    MAP TABLE IS    (12 of 36000)   1 % FULL

    Note:

    If the Weighted GTT Load Sharing feature is enabled, the WT, %WT, and THR columns are shown in the rtrv-map output.

    If the parameter values for the ri and xlat parameters will be ri=ssn and xlat=dpc when this procedure is completed, the point code value must be in the mated application table. If the point code is not in the mated application table when the chg-gta command is executed, the force=yes parameter must be specified with the chg-gta command. If the force=yes parameter will be used with the chg-gta command, continue the procedure with 15.

    If the parameter values for the ri and xlat parameters will be ri=ssn and xlat=dpcssn, and the point code and subsystem number values will be the EAGLE’s true point code and the EAGLE’s subsystem number when this procedure is completed, the EAGLE’s true point code and the EAGLE’s subsystem number must be in the mated application table.

    If the required point code, subsystem number, or MAP set ID is not shown in the rtrv-map output, perform one of these procedures to add the required information to the mated application table.

    If the required MAP entry is shown in this step, or a new MAP entry was added in this step, continue the procedure with 18.

    If the point code value is being changed in this procedure to the EAGLE’s point code, continue the procedure with 12.

  14. Enter the rtrv-ss-appl command to verify that either the LNP, EIR, V-Flex, ATINPQ, AIQ, or INP subsystem number (depending on which feature is on) is in the subsystem application table.

    This is an example of the possible output.

    rlghncxa03w 08-09-28 14:42:38 GMT EAGLE5 41.0.0
    APPL       SSN       STAT
    LNP        254       ONLINE
    
    SS-APPL table is 20% FULL (1 of 5)

    If no subsystem number is shown in the rtrv-ss-appl output, or if the rtrv-ss-appl command is rejected, go to one of these user's guides, depending on the type of subsystem you wish to use, to enable and turn on the feature as necessary, and add the subsystem to the subsystem application table.

    • EIR subsystem – go to EIR User's Guide.
    • INP subsystem – go to INP/AINPQ User's Guide.
    • LNP subsystem – go to ELAP Administration and LNP Feature Activation Guide.
    • V-Flex subsystem – go to V-Flex User's Guide.
    • ATINPQ subsystem – go to ATINP.
    • AIQ subsystem – go to Analyzed Information Features User's Guide.

    If the subsystem number is shown in the rtrv-ss-appl output, or the subsystem number has been added in this step, continue the procedure with 18.

  15. Display the destination point codes in the database by entering the rtrv-dstn command. This is an example of the possible output.
    rlghncxa03w 10-12-10 11:43:04 GMT EAGLE5 43.0.0
    Extended Processing Time may be Required
    
       DPCA          CLLI        BEI ELEI   ALIASI           ALIASN/N24    DMN
       001-207-000   ----------- no  --- --------------   --------------   SS7
       001-001-001   ----------- no  --- --------------   --------------   SS7
       001-001-002   ----------- no  --- --------------   --------------   SS7
       001-005-000   ----------- no  --- --------------   --------------   SS7
       001-007-000   ----------- no  --- --------------   --------------   SS7
       008-012-003   ----------- no  --- --------------   --------------   SS7
       003-002-004   ----------- no  --- --------------   --------------   SS7
       009-002-003   ----------- no  --- --------------   --------------   SS7
       010-020-005   ----------- no  --- --------------   --------------   SS7
    
       DPCI          CLLI        BEI ELEI   ALIASA           ALIASN/N24    DMN
       1-207-0       ----------- no  --- --------------   --------------   SS7
       0-015-0       ----------- no  --- --------------   --------------   SS7
       0-017-0       ----------- no  --- --------------   --------------   SS7
       1-011-1       ----------- no  --- --------------   --------------   SS7
       1-011-2       ----------- no  --- --------------   --------------   SS7
    
    
    Destination table is (14 of 2000) 1% full
    Alias table is (0 of 12000) 0% full
    PPC table is (1 of 20) 5% full

    If the required point code is not shown in the rtrv-dstn output, perform the "Adding a Destination Point Code" procedure in Database Administration - SS7 User's Guide to add the required point code. A proxy point code cannot be assigned to the point code.

    After the new point code has been added, perform one of the Adding a Route procedures in Database Administration - SS7 User's Guide to add the required route to the database. After the route has been added, continue the procedure with 18.

    If the required point code is shown in the rtrv-dstn output, continue the procedure with 16.

  16. Display the point code that will be assigned to the mated application by using the rtrv-dstn command and specifying the point code. For this example, enter this command.

    rtrv-dstn:dpca=010-020-005

    This is an example of the possible output.

    rlghncxa03w 10-12-10 11:43:04 GMT EAGLE5 43.0.0
    
       DPCA          CLLI        BEI ELEI   ALIASI           ALIASN/N24    DMN
       010-020-005   ----------- no  --- --------------   --------------   SS7
    
       PPCA         NCAI PRX     RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
       009-002-003  ---- no      none   off   none     no     no    none
    
    Destination table is (14 of 2000) 1% full
    Alias table is (0 of 12000) 0% full
    PPC table is (1 of 20) 5% full

    A proxy point code (a point code value is shown in the PPC column) cannot be assigned to the point code. If a proxy point code is shown in this step, choose another point code from the rtrv-dstn output in the previous step and repeat this step.

    After the new point code has been added, perform one of the Adding a Route procedures in Database Administration - SS7 User's Guide and add the required route to the database. After the route has been added, continue the procedure with 18.

    If the point code displayed in this step does not contain a proxy point code, continue the procedure with 17.

  17. The point code specified with the chg-gta command must be the DPC of a route, unless the point code is the EAGLE’s point code.

    Enter the rtrv-rte command with the dpc parameter specifying the point code to be used with the chg-gta command to verify whether or not the point code is the DPC of a route. For this example, enter this command.

    rtrv-rte:dpca=001-255-252

    This is an example of the possible output.

    rlghncxa03w 09-05-07 11:43:04 GMT  EAGLE5 41.0.0
       DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
       001-255-252 ---------- --------------   ls07       10    001-255-252
                                               ls08       30    025-025-150
                                               lsa5       50    066-030-100
                                                   RTX:No  CLLI=ls07clli

    If the point code is not shown in the rtrv-rte output, perform one of the Adding a Route procedures in Database Administration - SS7 User's Guide and add the required route to the database.

    If the point code is shown in the rtrv-rte output, and a new route was added, continue the procedure with 18.

  18. Continue the procedure by performing one or more of these steps depending on the parameters that will be specified with the ent-gta command.

    If the loopset parameter will be specified for the GTA entry, and the desired LOOPSET value is not shown in the rtrv-gta output, continue the procedure with 19.

    If the gtmodid parameter will be specified for the GTA entry, and the desired GTMODID value is not shown in the rtrv-gta output, continue the procedure with 20.

    If the actsn parameter will be specified for the GTA entry, and the desired ACTSN value is not shown in the rtrv-gta output, continue the procedure with 21.

    If the loopset. gtmodid, and actsn parameters will not be specified for the GTA entry, continue the procedure with 22.

  19. Display all the loopsets in the database by entering this command. rtrv-loopset:num=1000:force=yes

    This is an example of the possible output.

    LoopSet      Mode       Point Codes
    ======================================================================
    cary2       notify      005-015-005      007-007-007      (ANSI)
                            033-004-003      033-007-003
                            005-027-005      007-004-007
    
    cary4       notify      005-012-005      007-026-007      (ANSI)
                            003-049-003      033-002-003
                            005-008-055      007-014-007
    
    apex3       discard     005-017-008      007-017-009      (ANSI)
                            033-005-043      005-014-005
                            005-017-005      007-014-007
                            033-002-043      005-038-005
                            007-009-027      033-003-043
                            005-012-005      007-002-027
    
    apex4       discard     005-007-008      027-007-009      (ANSI)
                            033-005-003      005-004-055
                            027-001-007      033-008-003
                            033-007-003      005-003-055
                            027-008-007
    
    ral5        notify      005-005-005      007-007-007      (ANSI)
                            003-004-003      003-001-003
                            005-007-005      007-004-007
                            003-002-003      005-008-005
                            007-009-007      003-003-003
                            005-002-005      007-002-007
    
    ral6        notify      005-007-008      007-007-009      (ANSI)
                            003-005-003      003-007-003
                            005-007-005
    
    dunn1       discard     005-002-055      007-051-007      (ANSI)
                            003-008-033
    
    rtp9        discard     005-002-005      007-001-007      (ANSI)
                            003-008-003      003-007-003
                            005-003-005      007-008-007
                            005-004-005 
    
    rtp5        discard     005-007-008      007-007-009      (ANSI)
                            003-005-003
    
    rtp1        discard     005-005-005      007-007-007      (ANSI)
                            003-004-003      003-007-003
                            005-007-005      007-004-007
                            005-004-005
    
    rtp2        notify      005-007-008      007-007-009      (ANSI)
                            003-005-003
    
    rlghncxa03w 07-03-07 08:50:15 GMT Rel 35.6.0
    LOOPSET table is (11 of 1000)       1% full
    RTRV-LOOPSET: MASP A - COMPLTD

    Note:

    If the rtrv-loopset command is entered with no other parameters specified, a maximum of 50 entries are displayed. To display more than 50 entries, the force=yes parameter must be specified with the rtrv-loopset command and the num parameter value must be greater than 50. Since there can be a maximum of 1000 loopsets in the database, to display all the loopsets in the database, the force=yes and num=1000 parameters must be specified with the rtrv-loopset command.

    If the required loopset is not shown in the rtrv-loopset output, perform Adding a Loopset to add the required loopset.

    if the required loopset is shown in the rtrv-loopset output, or if a new loopset was added, continue the procedure by performing one of these steps.
    • If the gtmodid parameter will be specified for the GTA entry, and the desired GTMODID value is not shown in the rtrv-gta output, continue the procedure with 20.
    • If the actsn parameter will be specified for the GTA entry, and the desired ACTSN value is not shown in the rtrv-gta output, continue the procedure with 21.
    • If the gtmodid and actsn parameters will not be specified for the GTA entry, continue the procedure with 22.
  20. Display the GT modification information in the database using the rtrv-gtmod command.

    This is an example of the possible output.

    rlghncxa03w 10-07-07 00:29:31 GMT EAGLE5 42.0.0
    
    GTMODID   NTT  NGTI  GT0FILL  NNP  NNAI  NPDD  NSDD  PRECD  CGPASSN
    modid2     --     2       ON   --    --    --    --    PFX       --
          NPDS=                       NSDS=
    modid5     --     2      OFF   --    --    --    --    PFX       --
          NPDS=                       NSDS=
    modid6     --     4       ON    4     5     3     3    SFX       --
          NPDS=123                    NSDS=456
    modid10    --    --      OFF    5     5    --    --    PFX       --
          NPDS=                       NSDS=
    modid11    --    --      OFF    5     5    --    --    PFX       --
          NPDS=                       NSDS=
    
    
    GTMOD table is (5 of 100000) 1% full.

    If the desired GT modification entry is not displayed, perform the Adding Global Title Modification Information procedure to add the desired GT modification entry to the database.

    If the desired GT modification entry is displayed or the Adding Global Title Modification Information procedure was performed, continue the procedure by performing one of these steps.
    • If the actsn parameter will be specified for the GTA entry, and the desired ACTSN value is not shown in the rtrv-gta output, continue the procedure with 21.
    • If the actsn parameter will not be specified for the GTA entry, continue the procedure with 22.
  21. Display the GTT action sets in the database using the rtrv-gttaset command.

    This is an example of the possible output.

    rlghncxa03w 10-07-07 00:29:31 GMT EAGLE5 42.0.0
    
    ACTSN      TEST  ActIds
               MODE
    -------------------------------
    act1       off   action1   (DUP),action4   (DUP),action25  (FWD),
                     ------,------,------
    act10      on    action20  (DUP),action4   (DUP),action21  (DUP),
                     action25  (FWD),------,------
    act3       off   action2   (DISC),------,------,
                     ------,------,------
    act5       on    action1   (DUP),action3   (DUP),action4   (DUP),
                     action20  (DUP),action21  (DUP),action17  (TCAPERR)
    act11      off   action10  (UDTS),------,------,
                     ------,------,------
    
    
    GTT-ASET table is (5 of 20000) 1% full.

    If the desired GTT action set is not displayed, perform the Adding a GTT Action Set procedure to add the desired GT modification entry to the database.

    If the desired GT modification entry is displayed or the Adding a GTT Action Set procedure was performed, continue the procedure with 22.

  22. Change the global title address for GTT set LIDB using the chg-gta command. Use these tables as a guide for the parameters that can be used with the chg-gta command.

    For this example, enter this command:

    chg-gta:gttsn=lidb:gta=9195554321:xlat=dpcssn:ri=ssn:pc=001-255-252:ssn=254 :mapset=1:opcsn=gttset12:loopset=rtp2

    When the command has successfully completed, this message appears.

    rlghncxa03w 09-05-07 00:27:31 GMT EAGLE5 41.0.0
    CHG-GTA: MASP A - COMPLTD

    The command line on the terminal can contain up to 150 characters. If the parameters and values specified with the chg-gta command are too long to fit on the chg-gta command line, perform the chg-gta command as many times as required to complete changing the GTA entry.

  23. Verify the changes to the GTT set using the rtrv-gta command with the gttsn parameter value and one of the following parameters and values specified in 22, depending on what type of GTT set was specified in 22.
    • The gta parameter and value – if the GTT set was a CDGTA or CGGTA GTT set, or if the GTT set had no SETTYPE value.
    • The cgssn parameter and value – if the GTT set was a CGSSN GTT set.
    • The cgpc/cgpca/cgpci/cgpcn/cgpcn24 parameter and value – if the GTT set was a CGPC GTT set.
    • The opc/opca/opci/opcn/opcn24 parameter and value – if the GTT set was an OPC GTT set.
    • The cdssn parameter and value – if the GTT set was a CDSSN GTT set.
    • The opcode parameter and value – if the GTT set was an OPCODE GTT set.
    • The dpc/dpca/dpci/dpcn/dpcn24 parameter and value – if the GTT set was a DPC GTT set.

    If the num parameter is specified with the rtrv-gta command, and the value of the num parameter is greater than 1000, the force=yes parameter must be specified with the rtrv-gta command. For this example, enter this command.

    rtrv-gta:gttsn=lidb:gta=9195554321

    This is an example of the possible output.

    rlghncxa03w 10-07-07 00:27:31 GMT EAGLE5 42.0.0
    
    GTTSN     NETDOM  SETTYPE  NDGT
    lidb      ansi    CDGTA    10
    GTA TABLE IS   1 % FULL  (17 of 269999)
    
    START GTA  END GTA    XLAT   RI     PC
    9195554321 9195554321 DPCSSN SSN    001-255-252
         MAPSET=1     SSN=254 CCGT=no CGGTMOD=NO
         GTMODID=modid2     TESTMODE=off
         LOOPSET = rtp2     FALLBACK=sysdflt
         OPTSN=--------- CGSELID=----- OPCSN=gttset12
         ACTSN=--------- PPMEASREQD= NO
    
    Command Retrieved 1 Entries
  24. Back up the new changes using the chg-db:action=backup:dest=fixed command. These messages should 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.

Figure 4-23 Change Global Title Address Information - Sheet 1 of 15

Figure 4-24 Change Global Title Address Information - Sheet 2 of 15

Figure 4-25 Change Global Title Address Information - Sheet 3 of 15

Figure 4-26 Change Global Title Address Information - Sheet 4 of 15

Figure 4-27 Change Global Title Address Information - Sheet 5 of 15

Figure 4-28 Change Global Title Address Information - Sheet 6 of 15

Figure 4-29 Change Global Title Address Information - Sheet 7 of 15

Figure 4-30 Change Global Title Address Information - Sheet 8 of 15

Figure 4-31 Change Global Title Address Information - Sheet 9 of 15

Figure 4-32 Change Global Title Address Information - Sheet 10 of 15

Figure 4-33 Change Global Title Address Information - Sheet 11 of 15

Figure 4-34 Change Global Title Address Information - Sheet 12 of 15

Figure 4-35 Change Global Title Address Information - Sheet 13 of 15

Figure 4-36 Change Global Title Address Information - Sheet 14 of 15

Figure 4-37 Change Global Title Address Information - Sheet 15 of 15