Adding Global Title Address Information

This procedure is used to add global title address (GTA) information for applicable global title selectors required to specify a global title entry. This command adds the routing object (a destination address and a subsystem number) for messages requiring global title translation. The translation is performed on the basis of the GTA, global title indicator (GTI), numbering plan (NP), nature of address indicator (NAI), and translation type (TT) of each SS7 SCCP message directed to the STP with a routing indicator of 0, indicating that global title translation is required.

The ent-gta command uses these parameters:

:gttsn – The GTT set name

:gta – The global title address or the beginning value of a range of global title addresses

: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 output. This parameter can be specified only, and must be specified, if the Flexible GTT Load Sharing feature is enabled and if the ri=gt parameter is specified with the ent-gta command. If the Flexible GTT Load Sharing feature is enabled, the point code specified with the ent-gta command must be assigned to the MRN set specified by this parameter. 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, performActivating the Flexible GTT Load Sharing Feature.

:mapset – The MAP set ID, shown in the rtrv-map output. This parameter can be specified only, and must be specified, if the Flexible GTT Load Sharing feature is enabled and if the ri=ssn parameter is specified with the ent-gta command. If the Flexible GTT Load Sharing feature is enabled, the point code and SSN specified with the ent-gta command must be assigned to the MAP set specified by this parameter. 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-23 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-23 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, CGSSN, CGPC, OPC, CDSSN, DPC
CGSSN	CDGTA, CGGTA, CGSSN, CGPC, OPC, CDSSN, DPC
OPC	CDGTA, CGGTA, CGPC, CGSSN, OPC, CDSSN, DPC
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, OPC, CDSSN, OPCODE, 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.

:transmeasrqd - GTT Translation Measurement Required. This parameter specifies whether to perform per GTT Translation Measurements.

: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-31 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. By default, the value of the loopset parameter is “none” because no loopset is assigned to the GTA.

: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.

Note:

The command line on the terminal can contain up to 150 characters. If the parameters and values specified with the ent-gta command are too long to fit on the ent-gta command line, perform Changing Global Title Address Information to complete adding the GTA entry.

The Global Title Translation (GTT) feature and the Enhanced Global Title Translation (EGTT) feature must be on before using this command. Use the rtrv-feat command to verify the settings. If the features are off, turn them on using the chg-feat:gtt=on:egtt=on command.

Note:

Once the Global Title Translation (GTT) feature and the Enhanced Global Title Translation (EGTT) feature are turned on with the chg-feat command, they cannot be turned off.

The GTT feature and the EGTT feature must be purchased before you turn these features on. If you are not sure whether you have purchased the GTT feature and/or the EGTT feature, contact your Oracle Sales Representative or Account Representative.

If the Variable-Length Global Title Translation (VGTT) feature is off, shown the entry VGTT = off, the global title address length must be equal to the number of digits specified by the given GTT set name. The length of the global title address can be verified with the rtrv-gttset command.

If the Variable-Length Global Title Translation (VGTT) feature is on, shown the entry VGTT = on, up to 10 different length global title addresses can be assigned to a GTT set. If the Support for 16 GTT Lengths in VGTT feature is enabled and turned on, up to 16 different length global title addresses can be assigned to a GTT set. The length of the global title address is only limited by the range of values for the gta and egta parameters, one to 21 digits, and by the global title addresses already assigned to the GTT set name. The ndgt parameter of the ent-gttset command has no effect on the length of the global title address. As global title addresses of different lengths are assigned to a specific translation type, these lengths are displayed in the NDGT field of the rtrv-gttset command output, as shown in the following example.

rlghncxa03w 09-07-07 00:30:31 GMT EAGLE5 41.1.0

GTTSN     NETDOM  NDGT
lidb      ansi    3, 7, 10
t800      ansi    6
si000     itu     15
imsi      itu     15
abcd1234  itu     12

GTT-SET table is (5 of 2000) 1% full.

In this example of the rtrv-gttset command output, the GTT set lidb contains three different length global title addresses; global title addresses containing three digits, seven digits, and 10 digits.

If the GTT set contains the maximum number of different length global title addresses, and another global title address is specified for the GTT set name, the length of the global title address being added to the GTT set name must be the same as one of the lengths already assigned to the GTT set name. If the length of the global title address does not match one of the lengths already assigned to the GTT set name, the ent-gta command is rejected with this message

E4008 Cmd Rej: Exceeding max GTA Lengths supported per GTTSET

If the GTT set name has less than the maximum number of different length global title addresses assigned to it, and another global title address is specified for the GTT set name, the length of the global title address can be from one to 21 digits and does not have to match the length of the other global title addresses assigned to the GTT set name.

Refer to Variable-length Global Title Translation Feature for more information about this feature.

The range, as specified by the start and end global title addresses, cannot already exist in the global title translation data for the specified translation type. If the ranges overlap, the range of global title addresses cannot be split and the ent-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 06-10-24 08:29:15 GMT EAGLE5 36.0.0
The following GTA ranges overlap the input GTA range

START GTA               END GTA
8005550000              8005551999
8005552000              8005553999
8005554000              8005555999

ENT-GTA: MASP A - Command Aborted

The translate indicator (xlat) must be DPCSSN if the SSN parameter is specified. If the translate indicator is set to DPCNGT, the value of the RI parameter must be GT.

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 point code.

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 ent-gta command is executed when these parameters are specified with the ent-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 ent-gta command, the EAGLE creates a solitary mated application in the mated application table using the point code and subsystem values specified in the ent-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.

These tables show the valid parameter combinations that can be used with the ent-gta command.

The EAGLE can contain 269,999, 400,000, or 1,000,000 global title addresses. The system default is 269,999 global title addresses. This quantity can be increased to 400,000 by enabling the feature access key for part number 893-0061-01, or to 1,000,000 by enabling the feature access key for part number 893-0061-10. For more information on enabling these feature access keys, refer to Enabling the XGTT Table Expansion 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-24 GTA Parameter Combinations - No SETTYPE Column in RTRV-GTTSET Output

RI = GT XLAT=DPCNGT	RI = GT XLAT=DPCSSN	RI = GT XLAT=DPC	RI = SSN XLAT=DPCSSN	RI = SSN XLAT=DPC
Mandatory Parameters
GTTSN	GTTSN	GTTSN	GTTSN	GTTSN
PC/PCA/PCI/ PCN/PCN24 (See Notes 1, 2, and 6)	PC/PCA/PCI/ PCN/PCN24 (See Notes 1, 2, and 6)	PC/PCA/PCI/ PCN/PCN24 (See Notes 1, 2, and 6)	PC/PCA/PCI/ PCN/PCN24 (See Notes 1, 2, and 6)	PC/PCA/PCI/ PCN/PCN24 (See Notes 1, 2, and 6)
GTA (See Notes 3, 4, 5, and 7)	GTA (See Notes 3, 4, 5, and 7)	GTA (See Notes 3, 4, 5, and 7)	GTA (See Notes 3, 4, 5, and 7)	GTA (See Notes 3, 4, 5, and 7)
	SSN		SSN
If only the EGTT feature is on, the `SETTYPE` column is not shown in the `rtrv-gttset` output. There are other optional parameters that can be used with this entry. Refer to Table 4-33 for these parameters.
Parameter Values: GTTSN – The GTT set name from the `GTTSN` column of the `rtrv-gttset` output. GTA – 1 - 21 digits or 1 - 21 hexadecimal digits PC/PCA/PCI/PCN/PCN24 – See Note 1 SSN – 0 - 255
Notes: 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. 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. If the VGTT feature is on, shown by the `VGTT = on` entry in the `rtrv-feat` output, and the GTT set name contains 10 different length GTAs, the length of the GTA must match any existing GTA assigned to the GTT set name. If the Support for 16 GTT Lengths for VGTT feature is enabled and turned on, shown by the `VGTT with 16 GTT lengths` entry in the `rtrv-ctrl-feat` output, and the GTT set name contains 16 different length GTAs, the length of the GTA must match any existing GTA assigned to the GTT set name. If the GTT set name contains less than the maximum number of different length GTAs, the length of the GTA can be from 1 to 21 digits. If the VGTT feature is off, the length of the GTA must contain the number of digits defined by the `NDGT` field of the `rtrv-gttset` output. If the point code is the EAGLE’s point code, then the `xlat` parameter value must be `dpcssn` and the `ri` parameter value must be `ssn`. Hexadecimal digits (0-9, a-f, A-F) can be specified for the `gta` or `egta` parameters only if the Hex Digit support for GTT feature is enabled.

Table 4-25 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.	GTTSN – The GTT set name from the `GTTSN` column of the `rtrv-gttset` output containing the value `CDGTA` in the `SETTYPE` column.
RI – GT, SSN (See Notes 6, 7, 8, and 9)	GTA – 1 - 21 digits or 1 - 21 hexadecimal digits (See Notes 3, 4, 5, and 10)
PC/PCA/PCI/PCN/PCN24 (See Notes 1, 2, and 6)
GTA – 1 - 21 digits or 1 - 21 hexadecimal digits (See Notes 3, 4, 5, and 10)
Optional Parameters
SSN – 0 - 255. Default value – no SSN value is specified. (See Note 9)	EGTA – 1 - 21 digits or 1 - 21 hexadecimal digits. (See Note 10) Default = same as the GTA value. 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. Refer to Table 4-23 for the valid GTT set types that can be specified. Default value – no GTT set is specified.
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-33 for these parameters.
Notes: 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. 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 GTT sets can be specified with the `gttsn`, `optsn`, or `opcsn` parameters. The CROSS GTT set, a GTT set containing the `NETDOM` value `CROSS`, can be specified with either ANSI or ITU point codes, but can be specified only with the `gttsn` parameter. If the VGTT feature is on, shown by the `VGTT = on` entry in the `rtrv-feat` output, and the GTT set name contains 10 different length GTAs, the length of the GTA must match any existing GTA assigned to the GTT set name. If the Support for 16 GTT Lengths for VGTT feature is enabled and turned on, shown by the `VGTT with 16 GTT lengths` entry in the `rtrv-ctrl-feat` output, and the GTT set name contains 16 different length GTAs, the length of the GTA must match any existing GTA assigned to the GTT set name. If the GTT set name contains less than the maximum number of different length GTAs, the length of the GTA can be from 1 to 21 digits. If the VGTT feature is off, the length of the GTA must contain the number of digits defined by the `NDGT` field of the `rtrv-gttset` output. If the point code is the EAGLE’s point code, then the `xlat` parameter value must be `dpcssn` and the `ri` parameter value must be `ssn`. The `force` parameter can be specified only if the `ri` parameter is `ssn` and the `xlat` parameter value is `dpc`. If the `pc`/`pca`/`pci`/`pcn`/`pcn24` parameter value is not shown in the `rtrv-map` output, the `force=yes` parameter must be specified with the `ent-gta` command. If the `ri` parameter value is `gt`, the `xlat` parameter value can be `dpcngt`, `dpcssn`, or `dpc`. If the `ri` parameter value is `ssn`, the `xlat` parameter value can be `dpcssn` or `dpc`. the `ssn` parameter can be specified, and must be specified, only if the `xlat` parameter is `dpcssn`. Hexadecimal digits (0-9, a-f, A-F) can be specified for the `gta` or `egta` parameters only if the Hex Digit support for GTT feature is enabled.

Table 4-26 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.	GTTSN – The GTT set name from the `GTTSN` column of the `rtrv-gttset` output containing the value `CGGTA` in the `SETTYPE` column.
RI – GT, SSN (See Notes 6, 7, 8, and 9)	GTA – 1 - 21 digits or 1 - 21 hexadecimal digits (See Notes 3, 4, 5, and 10)
PC/PCA/PCI/PCN/PCN24 (See Notes 1, 2, and 6)
GTA – 1 - 21 digits or 1 - 21 hexadecimal digits (See Notes 3, 4, 5, and 10)
Optional Parameters
SSN – 0 - 255. Default value – no SSN value is specified. (See Note 9)	EGTA – 1 - 21 digits or 1 - 21 hexadecimal digits. (See Note 10) Default = same as the GTA value. 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. Refer to Table 4-23 for the valid GTT set types that can be specified. Default value – no GTT set is specified.
There are other optional parameters that can be used with this entry. Refer to Table 4-33 for these parameters.
Notes: 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. 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 GTT sets can be specified with the `gttsn`, `optsn`, or `opcsn` parameters. TheCROSS GTT set, a GTT set containing the `NETDOM` value `CROSS`, can be specified with either ANSI or ITU point codes, but can be specified only with the `gttsn` parameter. If the VGTT feature is on, shown by the `VGTT = on` entry in the `rtrv-feat` output, and the GTT set name contains 10 different length GTAs, the length of the GTA must match any existing GTA assigned to the GTT set name. If the Support for 16 GTT Lengths for VGTT feature is enabled and turned on, shown by the `VGTT with 16 GTT lengths` entry in the `rtrv-ctrl-feat` output, and the GTT set name contains 16 different length GTAs, the length of the GTA must match any existing GTA assigned to the GTT set name. If the GTT set name contains less than the maximum number of different length GTAs, the length of the GTA can be from 1 to 21 digits. If the VGTT feature is off, the length of the GTA must contain the number of digits defined by the `NDGT` field of the `rtrv-gttset` output. If the point code is the EAGLE’s point code, then the `xlat` parameter value must be `dpcssn` and the `ri` parameter value must be `ssn`. The `force` parameter can be specified only if the `ri` parameter is `ssn` and the `xlat` parameter value is `dpc`. If the `pc`/`pca`/`pci`/`pcn`/`pcn24` parameter value is not shown in the `rtrv-map` output, the `force=yes` parameter must be specified with the `ent-gta` command. If the `ri` parameter value is `gt`, the `xlat` parameter value can be `dpcngt`, `dpcssn`, or `dpc`. If the `ri` parameter value is `ssn`, the `xlat` parameter value can be `dpcssn` or `dpc`. the `ssn` parameter can be specified, and must be specified, only if the `xlat` parameter is `dpcssn`. Hexadecimal digits (0-9, a-f, A-F) can be specified for the `gta` or `egta` parameters only if the Hex Digit support for GTT feature is enabled.

Table 4-27 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.	GTTSN – The GTT set name from the `GTTSN` column of the `rtrv-gttset` output containing the value `CGPC` in the `SETTYPE` column.
RI – GT, SSN (See Notes 3, 4, 5, and 6)	CGPC/CGPCA/CGPCI/CGPCN/CGPCN24 (See Notes 1, 2, and 3)
PC/PCA/PCI/PCN/PCN24 (See Notes 1, 2, and 3)
CGPC/CGPCA/CGPCI/CGPCN/CGPCN24 (See Notes 1, 2, and 3)
Optional Parameters
SSN – 0 - 255. Default value – no SSN value is specified. (See Note 3)	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. Refer to Table 4-23 for the valid GTT set types that can be specified. Default value – no GTT set is specified.
There are other optional parameters that can be used with this entry. Refer to Table 4-33 for these parameters. The EGTA parameter cannot be specified with this entry.
Notes: 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 as the translated point code. 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. `pc`/`pca` and `cgpc`/`cgpca` = ANSI point code `pci` and `cgpci` = ITU-I or ITU-I spare point code `pcn` and `cgpcn` = 14-bit ITU-N or 14-bit ITU-N spare point code `pcn24` and `cgpcn24` = 24-bit ITU-N point code. 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 GTT sets can be specified with the `gttsn`, `optsn`, or `opcsn` parameters. The CROSS GTT set, a GTT set containing the `NETDOM` value `CROSS`, can be specified with either ANSI or ITU point codes, but can be specified only with the `gttsn` parameter. If the point code is the EAGLE’s point code, then the `xlat` parameter value must be `dpcssn` and the `ri` parameter value must be `ssn`. The `force` parameter can be specified only if the `ri` parameter is `ssn` and the `xlat` parameter value is `dpc`. If the `pc`/`pca`/`pci`/`pcn`/`pcn24` parameter value is not shown in the `rtrv-map` output, the `force=yes` parameter must be specified with the `ent-gta` command. If the `ri` parameter value is `gt`, the `xlat` parameter value can be `dpcngt`, `dpcssn`, or `dpc`. If the `ri` parameter value is `ssn`, the `xlat` parameter value can be `dpcssn` or `dpc`. the `ssn` parameter can be specified, and must be specified, only if the `xlat` parameter is `dpcssn`.

Table 4-28 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.	GTTSN – The GTT set name from the `GTTSN` column of the `rtrv-gttset` output containing the value `CGSSN` in the `SETTYPE` column.
RI = GT, SSN (See Notes 3, 4, 5, and 6)	CGSSN – 0 - 255
PC/PCA/PCI/PCN/PCN24 (See Notes 1, 2, and 3)
CGSSN – 0 - 255
Optional Parameters
SSN – 0 - 255. Default value – no SSN value is specified. (See Note 3)	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`
ECGSSN – 0 - 255. Default value – no ECGSSN value is specified. The ECGSSN value must be greater than the CGSSN value.
OPTSN – The GTT set name from the `GTTSN` column of the `rtrv-gttset` output. Refer to Table 4-23 for the valid GTT set types that can be specified. Default value – no GTT set is specified.
There are other optional parameters that can be used with this entry. Refer to Table 4-33 for these parameters. The EGTA parameter cannot be specified with this entry.
Notes: 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 as the translated point code. `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. 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 GTT sets can be specified with the `gttsn`, `optsn`, or `opcsn` parameters. The CROSS GTT set, a GTT set containing the `NETDOM` value `CROSS`, can be specified with either ANSI or ITU point codes, but can be specified only with the `gttsn` parameter. If the point code is the EAGLE’s point code, then the `xlat` parameter value must be `dpcssn` and the `ri` parameter value must be `ssn`. The `force` parameter can be specified only if the `ri` parameter is `ssn` and the `xlat` parameter value is `dpc`. If the `pc`/`pca`/`pci`/`pcn`/`pcn24`parameter value is not shown in the `rtrv-map` output, the `force=yes` parameter must be specified with the `ent-gta` command. If the `ri` parameter value is `gt`, the `xlat` parameter value can be `dpcngt`, `dpcssn`, or `dpc`. If the `ri` parameter value is `ssn`, the `xlat` parameter value can be `dpcssn` or `dpc`. the `ssn` parameter can be specified, and must be specified, only if the `xlat` parameter is `dpcssn`.

Table 4-29 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.	GTTSN – The GTT set name from the `GTTSN` column of the `rtrv-gttset` output containing the value `OPC` in the `SETTYPE` column.
RI – GT, SSN (See Notes 3, 4, 5, and 6)	OPC/OPCA/OPCI/OPCN/OPCN24 (See Notes 1, 2, and 3)
PC/PCA/PCI/PCN/PCN24 (See Notes 1, 2, and 3)
OPC/OPCA/OPCI/OPCN/OPCN24 (See Notes 1, 2, and 3)
Optional Parameters
SSN – 0 - 255. Default value – no SSN value is specified. (See Note 3)	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. Refer to Table 4-23 for the valid GTT set types that can be specified. Default value – no GTT set is specified.
There are other optional parameters that can be used with this entry. Refer to Table 4-33 for these parameters. The EGTA parameter cannot be specified with this entry.
Notes: 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 as the translated point code. 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. `pc`/`pca` and `opc`/`opca` = ANSI point code `pci` and `opci` = ITU-I or ITU-I spare point code `pcn` and `opcn` = 14-bit ITU-N or 14-bit ITU-N spare point code `pcn24` and `opcn24` = 24-bit ITU-N point code. 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 GTT sets can be specified with the `gttsn`, `optsn`, or `opcsn` parameters. The CROSS GTT set, a GTT set containing the `NETDOM` value `CROSS`, can be specified with either ANSI or ITU point codes, but can be specified only with the `gttsn` parameter. If the point code is the EAGLE’s point code, then the `xlat` parameter value must be `dpcssn` and the `ri` parameter value must be `ssn`. The `force` parameter can be specified only if the `ri` parameter is `ssn` and the `xlat` parameter value is `dpc`. If the `pc`/`pca`/`pci`/`pcn`/`pcn24` parameter value is not shown in the `rtrv-map` output, the `force=yes` parameter must be specified with the `ent-gta` command. If the `ri` parameter value is `gt`, the `xlat` parameter value can be `dpcngt`, `dpcssn`, or `dpc`. If the `ri` parameter value is `ssn`, the `xlat` parameter value can be `dpcssn` or `dpc`. the `ssn` parameter can be specified, and must be specified, only if the `xlat` parameter is `dpcssn`.

Table 4-30 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.	GTTSN – The GTT set name from the `GTTSN` column of the `rtrv-gttset` output containing the value `CDSSN` in the `SETTYPE` column.
RI = GT, SSN (See Notes 3, 4, 5, and 6)	CDSSN – 0 - 255
PC/PCA/PCI/PCN/PCN24 (See Notes 1, 2, and 3)
CDSSN – 0 - 255
Optional Parameters
SSN – 0 - 255. Default value – no SSN value is specified. (See Note 3)	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`
ECDSSN – 0 - 255. Default value – no ECDSSN value is specified. The ECDSSN value must be greater than the CDSSN value.
OPTSN – The GTT set name from the `GTTSN` column of the `rtrv-gttset` output. Refer to Table 4-23 for the valid GTT set types that can be specified. Default value – no GTT set is specified.
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-33 for these parameters. The EGTA parameter cannot be specified with this entry.
Notes: 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 as the translated point code. `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. 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 GTT sets can be specified with the `gttsn`, `optsn`, or `opcsn` parameters. The CROSS GTT set, a GTT set containing the `NETDOM` value `CROSS`, can be specified with either ANSI or ITU point codes, but can be specified only with the `gttsn` parameter. If the point code is the EAGLE’s point code, then the `xlat` parameter value must be `dpcssn` and the `ri` parameter value must be `ssn`. the `force` parameter can be specified only if the `ri` parameter is `ssn` and the `xlat` parameter value is `dpc`. If the `pc`/`pca`/`pci`/`pcn`/`pcn24`parameter value is not shown in the `rtrv-map` output, the `force=yes` parameter must be specified with the `ent-gta` command. If the `ri` parameter value is `gt`, the `xlat` parameter value can be `dpcngt`, `dpcssn`, or `dpc`. If the `ri` parameter value is `ssn`, the `xlat` parameter value can be `dpcssn` or `dpc`. the `ssn` parameter can be specified, and must be specified, only if the `xlat` parameter is `dpcssn`.

Table 4-31 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.		GTTSN – The GTT set name from the `GTTSN` column of the `rtrv-gttset` output containing the value `OPCODE` in the `SETTYPE` column.
RI = GT, SSN (See Notes 3, 4, 5, and 6)		OPCODE – 0 - 255, *, none
PC/PCA/PCI/PCN/PCN24 (See Notes 1, 2, and 3)		ANSI TCAP Translation	ITU TCAP Translation
OPCODE – See Notes 7, 10, and 11		FAMILY – See Notes 8, 10, and 11	ACN – The application context name – See Notes 9 and 10
ANSI TCAP Translation	ITU TCAP Translation	PKGTYPE – ansiabort, ansiumi, any, cwop, cwp, qwop, qwp, resp	PKGTYPE – any, bgn, cnt, end, ituabort, ituumi
FAMILY – See Notes 8, 10, and 11	ACN – The application context name – See Notes 9 and 10
PKGTYPE – ansiabort, ansiumi, any, cwop, cwp, qwop, qwp, resp	PKGTYPE – any, bgn, cnt, end, ituabort, ituumi
Optional Parameters
SSN – 0 - 255. Default value – no SSN value is specified. (See Note 3)		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. Refer to Table 4-23 for the valid GTT set types that can be specified. Default value – no GTT set is specified.
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-33 for these parameters. The EGTA parameter cannot be specified with this entry.
Notes: 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 as the translated point code. `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. 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 GTT sets can be specified with the `gttsn`, `optsn`, or `opcsn` parameters. The CROSS GTT set, a GTT set containing the `NETDOM` value `CROSS`, can be specified with either ANSI or ITU point codes, but can be specified only with the `gttsn` parameter. If the point code is the EAGLE’s point code, then the `xlat` parameter value must be `dpcssn` and the `ri` parameter value must be `ssn`. The `force` parameter can be specified only if the `ri` parameter is `ssn` and the `xlat` parameter value is `dpc`. If the `pc`/`pca`/`pci`/`pcn`/`pcn24`parameter value is not shown in the `rtrv-map` output, the `force=yes` parameter must be specified with the `ent-gta` command. If the `ri` parameter value is `gt`, the `xlat` parameter value can be `dpcngt`, `dpcssn`, or `dpc`. If the `ri` parameter value is `ssn`, the `xlat` parameter value can be `dpcssn` or `dpc`. The `ssn` parameter can be specified, and must be specified, only if the `xlat` parameter is `dpcssn`. The `opcode` parameter value is one of these values. the number 0 to 255 * - any valid value in the TCAP OPCODE field in the incoming MSU none - there is no value in the TCAP OPCODE field in the incoming MSU The `family` parameter value is one of these values. The number 0 to 255 * - any valid value in the ANSI TCAP FAMILY field in the incoming MSU none - there is no value in the ANSI TCAP FAMILY field in the incoming MSU The `acn` parameter value is one of these values. a maximum of 7 subfields containing the numbers 0 to 255 separated by dash (for example, 1-202-33-104-54-26-007) * - any valid value in the ITU TCAP ACN field in the incoming MSU none - there is no value in the ITU TCAP ACN field in the incoming MSU If the `pkgtype=ituabort` parameter is specified, the value `none` must be specified for the `acn` and`opcode` parameters. If the `pkgtype=ansiabort` parameter is specified, the value `none` must be specified for the `family` and`opcode` parameters. If the value `none` is specified for either the `family` or `opcode` parameters, the value none must be specified for both parameters.

Table 4-32 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.
RI – GT, SSN (See Notes 3, 4, 5, and 6)	DPC/DPCA/DPCI/DPCN/DPCN24 (See Notes 1, 2, and 3)
PC/PCA/PCI/PCN/PCN24 (See Notes 1, 2, and 3)
DPC/DPCA/DPCI/DPCN/DPCN24 (See Notes 1, 2, and 3)
Optional Parameters
SSN – 0 - 255. Default value – no SSN value is specified. (See Note 3)	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. Refer to Table 4-23 for the valid GTT set types that can be specified. Default value – no GTT set is specified.
There are other optional parameters that can be used with this entry. Refer to Table 4-33 for these parameters. The EGTA parameter cannot be specified with this entry.
Notes: 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 as the translated point code. the `dpc`/`dpca`/`dpci`/`dpcn`/`dpcn24`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 DPC parameter values. `pc`/`pca` and `dpc`/`dpca` = ANSI point code `pci` and `dpci` = ITU-I or ITU-I spare point code `pcn` and `dpcn` = 14-bit ITU-N or 14-bit ITU-N spare point code `pcn24` and `dpcn24` = 24-bit ITU-N point code. 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 GTT sets can be specified with the `gttsn`, `optsn`, or `opcsn` parameters. The CROSS GTT set, a GTT set containing the `NETDOM` value `CROSS`, can be specified with either ANSI or ITU point codes, but can be specified only with the `gttsn` parameter. If the point code is the EAGLE’s point code, then the `xlat` parameter value must be `dpcssn` and the `ri` parameter value must be `ssn`. the `force` parameter can be specified only if the `ri` parameter is `ssn` and the `xlat` parameter value is `dpc`. If the `pc`/`pca`/`pci`/`pcn`/`pcn24` parameter value is not shown in the `rtrv-map` output, the `force=yes` parameter must be specified with the `ent-gta` command. If the `ri` parameter value is `gt`, the `xlat` parameter value can be `dpcngt`, `dpcssn`, or `dpc`. If the `ri` parameter value is `ssn`, the `xlat` parameter value can be `dpcssn` or `dpc`. the `ssn` parameter can be specified, and must be specified, only if the `xlat` parameter is `dpcssn`.

Table 4-33 Optional GTA 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 parameter only if the Hex Digit support for GTT feature is enabled.

MRNSET – MRN set ID from the rtrv-mrn output. The mrnset parameter can be specified only, and must be specified, if the Flexible GTT Load Sharing feature is enabled.

LOOPSET – Loopset name from the rtrv-loopset output. The loopset parameter can be specified only if the SCCP Loop Detection feature is enabled.

CGGTMOD – yes, no. Default = no. The cggtmod parameter can be specified only if the AMGTT or AMGTT CgPA Upgrade feature is enabled.

CCGT – yes, no. Default = no. If the point code is the EAGLE’s point code, then the value of the ccgt parameter must be set to no.

MAPSET – MAP set ID from the rtrv-map output. The mapset parameter can be specified only, and must be specified, if the Flexible GTT Load Sharing feature is enabled.

FORCE – yes, no. Default = no. If the pc/pca/pci/pcn/pcn24 parameter value is not shown in the rtrv-map output, the force=yes parameter must be specified with the ent-gta command.

TESTMODE – on, off. Default = off.

FALLBACK – sysdflt, yes, no. Default = sysdflt. The Flexible Linkset Optional Based Routing feature must be enabled and turned on to use this parameter.

CGSELID – 0 - 65534. Default = no CGSELID value is specified. The Origin-Based SCCP Routing feature must be enabled or the Flexible Linkset Optional Based Routing feature must be enabled and turned on to use this parameter.

CDSELID – 0 - 65534. Default = no CDSELID value is specified. The Flexible Linkset Optional Based Routing feature must be enabled and turned on to use this parameter

CGCNVSN – GTT set name shown in the rtrv-gttset output. Default = no CGCNVSN value is specified. 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.

ACTSN – The name of the GTT action set name shown in the rtrv-gttaset output. Default = no ACTSN value is specified. The actsn parameter can be specified only if the GTT Action - DISCARD, GTT Action - DUPLICATE, GTT Action - FORWARD feature is enabled.

GTMODID – The name of the GT modification identifier shown in the rtrv-gtmod output. Default = no GTMODID value is specified. If the NGTI value in the global title modification entry is 4, the point code that will be 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.

Display the existing 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
imsi       itu     CDGTA    15
lidb       ansi    CDGTA    10
t800       ansi    CGGTA    6
s1000      itu     CDGTA    15
s2000      itu     CGPC     -

GTT-SET table is (6 of 2000) 1% full.
```
If the desired GTT set name is shown in the rtrv-gttset output, continue the procedure with 2.

If the desired GTT set name is not shown in the rtrv-gttset output, perform Adding a GTT Set to add the required GTT set. After the GTT set has been added, continue the procedure with 3. If the SETTYPE column is not shown in the rtrv-gttset output and you wish to provision the GTA entry for any of these features, Origin-Based SCCP Routing, Flexible Linkset Optional Based Routing, or TCAP Opcode Based Routing, make sure the appropriate feature is enabled, and turned on if necessary, when adding the GTT set. After the GTT set has been added, continue the procedure with 3.

Display the global title address information for the GTT set that the global title address information will be added to using 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=t800

This is an example of the possible output.

rlghncxa03w 10-07-07 00:27:31 GMT EAGLE5 42.0.0

GTTSN     NETDOM  SETTYPE  NDGT
t800      ansi    CDGTA    10
GTA TABLE IS   1 % FULL  (17 of 269999)

START GTA  END GTA    XLAT   RI     PC
8005550000 8005551999 DPCSSN SSN    001-254-255
     SSN=255 CCGT=no CGGTMOD=NO
     GTMODID=---------  TESTMODE=off
     OPTSN=gttset7   CGSELID=----- OPCSN=---------
     ACTSN=--------- PPMEASREQD= NO
8005552000 8005553999 DPC    GT     001-254-255
     SSN=255 CCGT=no CGGTMOD=NO
     GTMODID=---------  TESTMODE=off
     OPTSN=gttset7   CGSELID=----- OPCSN=---------
     ACTSN=--------- PPMEASREQD= NO
8005554000 8005555999 DPCNGT GT     001-254-255
     SSN=255 CCGT=no CGGTMOD=NO
     GTMODID=modid2     TESTMODE=off
     OPTSN=--------- CGSELID=----- OPCSN=gttset12
     ACTSN=--------- PPMEASREQD= NO
8005556000 8005557999 DPCSSN SSN    001-254-255
     SSN=255 CCGT=no CGGTMOD=NO
     GTMODID=---------  TESTMODE=off
     OPTSN=--------- CGSELID=----- OPCSN=gttset6
     ACTSN=--------- PPMEASREQD= NO
8005558000 8005559999 DPCSSN SSN    001-254-255
     SSN=255 CCGT=yes CGGTMOD=NO
     GTMODID=---------  TESTMODE=off
     OPTSN=--------- CGSELID=----- OPCSN=gttset12
     ACTSN=--------- PPMEASREQD= NO
9195551212 9195551212 DPCSSN SSN    008-001-001
     SSN=222 CCGT=no CGGTMOD=NO
     GTMODID=---------  TESTMODE=off
     OPTSN=--------- CGSELID=----- OPCSN=gttset12
     ACTSN=--------- PPMEASREQD= NO
9762428487 9762428487 DPCSSN SSN    001-254-255
     SSN=222 CCGT=no CGGTMOD=NO
     GTMODID=---------  TESTMODE=off
     OPTSN=--------- CGSELID=----- OPCSN=---------
     ACTSN=--------- PPMEASREQD= NO
9766423277 9766423277 DPCSSN SSN    001-254-255
     SSN=222 CCGT=no CGGTMOD=NO
     GTMODID=---------  TESTMODE=off
     OPTSN=--------- CGSELID=----- OPCSN=---------
     ACTSN=--------- PPMEASREQD= NO
9769388928 9769388928 DPCSSN SSN    001-254-255
     SSN=222 CCGT=no CGGTMOD=NO
     GTMODID=---------  TESTMODE=off
     OPTSN=gttset9   CGSELID=----- OPCSN=---------
     ACTSN=--------- PPMEASREQD= NO

Command Retrieved 9 Entries

The global title address entry cannot be added to the database if the database contains the maximum number of global title addresses the EAGLE is allowed to have. The maximum number of global title addresses is shown in the rtrv-ctrl-feat output.
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
IPGWx Signaling TPS       893012814 on     20000
ISUP Normalization        893000201 on     ----
Command Class Management  893005801 on     ----
LNP Short Message Service 893006601 on     ----
Intermed GTT Load Sharing 893006901 on     ----
HC-MIM SLK Capacity       893012707 on     64

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.
```
Note:
If the entryXGTT Table Expansion is not shown in thertrv-ctrl-feat output, the maximum number of global title addresses that the database can contain is 269,999.

If the current number of global title translations that can be provisioned is 400,000, and the global title translation being added increases the number beyond 400,000 (the current number of global title translations that are provisioned is shown in the rtrv-gta output in 2), perform Enabling the XGTT Table Expansion Feature to enable XGTT Table Expansion feature for 1,000,000 global title translations.

If the current number of global title translations that can be provisioned is 269,999, and the global title translations being added increases the number beyond 269,999 (the current number of global title translations that are provisioned is shown in the rtrv-gta output in 2), perform Enabling the XGTT Table Expansion Feature to enable XGTT Table Expansion feature for 400,000 global title translations.

If the maximum number of global title is either 269,999 or 400,000, and the global title translation being added will not increase the number beyond the maximum number of global title translations (shown in the rtrv-gta output in 2), the maximum number of global title translations does not need to be increased. If the maximum number of global title translations is 1,000,000, the maximum number of global title translations cannot be increased.

Some parameters of the ent-gta command can be specified only when certain features are enabled, and turned on if necessary. Table 4-34 shows the feature requirements for these parameters.

Table 4-34 Feature Requirements for ENT-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
Flexible GTT Load Sharing Enabled	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
TCAP Opcode Based Routing Enabled and Turned On	OPTSN - specifying OPCODE GTT sets
TOBR Quantity Enabled	ACN
	FAMILY
	OPCODE
	PKGTYPE
SCCP Loop Detection Enabled	LOOPSET
Advanced GT Modification (AMGTT) 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. Origin-Based SCCP Routing - Activating the Origin-Based SCCP Routing Feature Flexible GTT Load Sharing - Activating the Flexible GTT Load Sharing Feature. After the Flexible GTT Load Sharing feature has been enabled, perform one of these procedures. If the `mrnset` and `ri=gt` parameters will be specified for the GTA entry, perform Provisioning MRN Entries to add the required MRNSET. If the `mapset` and `ri=ssn` parameters will be specified for the GTA entry, perform one of these procedures to add the required MAPSET. Provisioning a Solitary Mated Application Provisioning a Dominant Mated Application Provisioning a Load Shared Mated Application Provisioning a Combined Dominant/Load Shared Mated Application Flexible Linkset Optional Based Routing - Activating the Flexible Linkset Optional Based Routing Feature TCAP Opcode Based Routing - Activating the TCAP Opcode Based Routing Feature TOBR Opcode Quantity - Enabling a TOBR Opcode Quantity SCCP Loop Detection - Activating the SCCP Loop Detection Feature. After the SCCP Loop Detection feature is enabled, perform the Adding a Loopset procedure to add the required loopset. Advanced GT Modification or AMGTT CgPA Upgrade - Activating the Advanced GT Modification Feature. ANSI/ITU SCCP Conversion - Activating the ANSI/ITU SCCP Conversion Feature Hex Digit Support for GTT Enabled - Activating the Hex Digit Support for GTT Feature GTT Action - DISCARD, GTT Action - DUPLICATE, GTT Action - FORWARD - Activating the GTT Actions Features. After the required GTT Actions feature is enabled, perform the Adding a GTT Action Set procedure to add the required GTT action set. If the required feature is enabled, and turned on if required, shown in the `rtrv-ctrl-feat` output in 3, the procedure for that feature does not need to be performed.

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 4. 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, either the mrnset or mapset parameters, depending on the routing indicator value for the global title translation being added in this procedure, must be specified with the ent-gta command.

If the routing indicator for the global title translation being added is GT, there are two actions that can be taken:
- If the Flexible GTT Load Sharing feature is not enabled, continue the procedure with 7.
- If the Flexible GTT Load Sharing feature is enabled, continue the procedure with 6.
If the routing indicator for the global title translation being added is SSN, there are two actions that can be taken:
- If the Flexible GTT Load Sharing feature is not enabled, continue the procedure with one of these steps.
  - If the point code value is the EAGLE’s point code, continue the procedure with 10.
  - If the point code value is a value other than the EAGLE’s point code, the ri parameter value will be ssn, and the xlat parameter value will be dpc, continue the procedure with 11.
  - If the point code value is a value other than the EAGLE’s point code, the ri parameter value will be ssn, and the xlat parameter value will be dpcssn when this procedure is completed, continue the procedure with 12.
- If the Flexible GTT Load Sharing feature is enabled, perform one of these steps.
  - If the point code value is the EAGLE’s point code continue the procedure with 10.
  - If the point code value is a value other than the EAGLE’s point code, or the xlat parameter value will be dpc, continue the procedure with 11.
If the xlat=none parameter will be specified and the Flexible GTT Load Sharing feature is not enabled, continue the procedure with 16.

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 6.
- If the mapset parameter will be specified, continue the procedure with 11.
The point code and MRN set ID specified for the global title translation 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 ent-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, theWT,%WT, andTHR columns are shown in thertrv-mrn output

If the required MRN set is not shown in the rtrv-mrn output, provision the required MRN set by performing the Provisioning MRN Entries procedure.
If the required MRN set is shown in the rtrv-mrn output, or the Provisioning MRN Entries procedure has been performed. continue the procedure by performing one of these steps.
- If the ri=gt parameter will be specified, continue the procedure with 16.
- If the xlat=none parameter will be specified, continue the procedure by performing one of these steps.
  - If the mapset parameter will be specified, continue the procedure with 11.
  - If the mapset parameter will not be specified, continue the procedure with 16.

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         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  ALIASI       ALIASN         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

   DPCN          CLLI        BEI ELEI   ALIASA          ALIASI        DMN

   DPCN24        CLLI        BEI ELEI   ALIASA          ALIASI        DMN

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 5.

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

Display the point code that will be assigned to the GTA entry 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.

If a proxy point code is not assigned to the point code, continue the procedure with 9.

The point code specified with the ent-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 ent-gta command to verify whether or not the point code is the DPC of a route. For this example, enter these commands.

rtrv-rte:dpca=001-255-100

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-100 ---------- --------------   ls03       10    001-255-100
                                           ls02       30    150-150-150
                                           lsa2       50    200-200-200
                                               RTX:No  CLLI=ls03clli

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

rtrv-rte:dpca=001-255-001

This is an example of the possible output.

rlghncxa03w 06-10-07 11:43:04 GMT  EAGLE5 36.0.0
   DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
   001-255-001 ---------- --------------   ls05       10    001-255-001
                                           ls15       30    089-047-123
                                           lsa8       50    077-056-000
                                               RTX:No  CLLI=ls05clli

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

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

If the ri=ssn and xlat=dpcssn parameters are specified with the ent-gta command, and you wish to use the EAGLE’s point code for the value of the pc parameter of the ent-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

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.
For this example enter this command.

rtrv-map:pca=001-255-001
```
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-001                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-001                50  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-001                 5 10  SOL *Y  *Y  -------- OFF

MAP TABLE IS  (12 of 36000)  1 % FULL
```
Note:
If the Weighted GTT Load Sharing feature is enabled, theWT,%WT, andTHR columns are shown in thertrv-map output

If the ri=ssn and xlat=dpc parameters are being specified with the ent-gta command, the point code must be in the mated application table. If the point code is not in the mated application table when the ent-gta command is executed, the force=yes parameter must be specified with the ent-gta command. If the force=yes parameters will be specified with the ent-gta command, continue the procedure with 12.

If the EAGLE’s true point code and the EAGLE’s subsystem number, along with the ri=ssn and xlat=dpcssn parameters are being specified with the ent-gta command, 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.
- Provisioning a Solitary Mated Application
- Provisioning a Dominant Mated Application
- Provisioning a Load Shared Mated Application
- Provisioning a Combined Dominant/Load Shared Mated Application
Continue the procedure by performing one of these steps.
- If the ri=ssn parameter will be specified, continue the procedure by performing one of these steps.
  - if the EAGLE's point code and subsystem number will be specified with the ent-gta command, continue the procedure with 15.
  - if the EAGLE's point code and subsystem number will not be specified with the ent-gta command, and the xlat=dpcssn and ri=ssn parameters will be specified with the ent-gta command, continue the procedure with 16.
  - if the xlat=dpc and ri=ssn parameters will be specified with the ent-gta command, without the force=yes parameter, continue the procedure with 16.
- If the xlat=none parameter will be specified, continue the procedure with 16.

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         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  ALIASI       ALIASN         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

   DPCN          CLLI        BEI ELEI   ALIASA          ALIASI        DMN

   DPCN24        CLLI        BEI ELEI   ALIASA          ALIASI        DMN

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 shown in the rtrv-dstn output, continue the procedure with 13.

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.

If a proxy point code is not assigned to the point code, continue the procedure with 14.

rtrv-rte:dpca=001-255-100

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-100 ---------- --------------   ls03       10    001-255-100
                                           ls02       30    150-150-150
                                           lsa2       50    200-200-200
                                               RTX:No  CLLI=ls03clli

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

rtrv-rte:dpca=001-255-001

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-001 ---------- --------------   ls05       10    001-255-001
                                           ls15       30    089-047-123
                                           lsa8       50    077-056-000
                                               RTX:No  CLLI=ls05clli

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

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 09-05-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 the subsystem number is shown in the rtrv-ss-appl output, continue the procedure with 11. 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 User's Guide.
- INP subsystem – go to INP/AINPQ User's Guide.
- LNP subsystem – go to ELAP Administration and LNP Feature Activation User's Guide.
- V-Flex subsystem – go to V-Flex User's Guide.
- ATINPQ subsystem – go to ATINP User's Guide.
- AIQ subsystem – go to Analyzed Information Features User's Guide.
If the Flexible GTT Load Sharing feature is enabled, shown in 3, 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 added in this procedure must be assigned to the MAP set ID that will be assigned to the final global title translation. Perform 11 to verify that the required MAP set is configured in the database.

If the Flexible GTT Load Sharing feature is not enabled, and the ri=ssn and xlat=dpc parameters are not being specified with the ent-gta command, or if the EAGLE’s true point code and the EAGLE’s subsystem number, along with the ri=ssn and xlat=dpcssn parameters, are not being specified with the ent-gta command, continue the procedure with 16.
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 17.

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 18.

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 19.

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

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 09-05-28 21:15:37 GMT EAGLE5 41.0.0
LOOPSET table is (11 of 1000) 1% full 
RTRV-LOOPSET: MASP A - COMPLTD

Note:

If thertrv-loopset command is entered with no other parameters specified, a maximum of 50 entries are displayed. To display more than 50 entries, theforce=yes parameter must be specified with thertrv-loopset command and thenum 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, theforce=yes andnum=1000 parameters must be specified with thertrv-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 18.
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 19.
If the gtmodid and actsn parameters will not be specified for the GTA entry, continue the procedure with 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 19.
- If the actsn parameter will not be specified for the GTA entry, continue the procedure with 20.

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 20.

Add the global title address to a GTT set using the ent-gta command. Use these tables as a guide for the parameters that can be used with the ent-gta command.
- Table 4-24
- Table 4-25
- Table 4-26
- Table 4-27
- Table 4-28
- Table 4-29
- Table 4-30
- Table 4-31
- Table 4-32
Note:
The command line on the terminal can contain up to 150 characters. If the parameters and values specified with theent-gta command are too long to fit on theent-gta command line, performChanging Global Title Address Informationto complete adding the GTA entry.

For this example, enter these commands.

ent-gta:gttsn=t800:gta=9194605555:xlat=dpcngt:ri=gt:pc=001-255-100:mrnset=114 :opcsn=gttset12:cggtmod=yes:gtmodid=modid2

ent-gta:gttsn=t800:gta=9194610000:egta=9194689999:xlat=dpcssn:ri=ssn :pc=001-255-252:ssn=254:mapset=3:opcsn=gttset12:selid=12:actsn=act5

ent-gta:gttsn=t800:gta=3365840000:egta=3365849999:xlat=dpc :ri=ssn:pc=001-255-001:mapset=1:optsn=gttset3

When each of these commands has successfully completed, this message appears.
```
rlghncxa03w 09-05-07 11:43:04 GMT  EAGLE5 41.0.0
ENT-GTA: MASP A - COMPLTD
```

Verify the changes to the GTT set using the rtrv-gta command with the gttsn parameter value specified in 20 and one of the following parameters and values specified in 20, depending on what type of GTT set was specified in 20.

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 an DPC GTT set.

rtrv-gta:gttsn=t800:gta=9194605555

This is an example of the possible output.

rlghncxa03w 10-07-07 00:27:31 GMT EAGLE5 42.0.0

GTTSN     NETDOM  SETTYPE  NDGT
t800      ansi    CDGTA    10
GTA TABLE IS   1 % FULL  (17 of 269999)

START GTA  END GTA    XLAT   RI     PC
9194605555 9194605555 dpcngt gt     001-255-100
     MRNSET=114  SSN=--- CCGT=no CGGTMOD=YES
     GTMODID=modid2     TESTMODE=off
     OPTSN=--------- CGSELID=----- OPCSN=gttset12
     ACTSN=--------- PPMEASREQD= NO

Command Retrieved 1 Entries

rtrv-gta:gttsn=t800:gta=9194610000

This is an example of the possible output.

rlghncxa03w 10-07-07 00:27:31 GMT EAGLE5 42.0.0

GTTSN     NETDOM  SETTYPE  NDGT
t800      ansi    CDGTA    10
GTA TABLE IS   1 % FULL  (17 of 269999)

START GTA  END GTA    XLAT   RI     PC
9194610000 9194689999 dpcssn ssn    001-255-252
     MAPSET=3    SSN=254 CCGT=no CGGTMOD=NO
     GTMODID=---------  TESTMODE=off
     OPTSN=--------- CGSELID=----- OPCSN=gttset12
     ACTSN=act5      PPMEASREQD= NO

Command Retrieved 1 Entries

rtrv-gta:gttsn=t800:gta=3365840000

This is an example of the possible output.

rlghncxa03w 10-07-07 00:27:31 GMT EAGLE5 42.0.0

GTTSN     NETDOM  SETTYPE  NDGT
t800      ansi    CDGTA    10
GTA TABLE IS   1 % FULL  (17 of 269999)

START GTA  END GTA    XLAT   RI     PC
3365840000 3365849999 dpc    ssn    001-255-001
     MAPSET=1    SSN=--- CCGT=no CGGTMOD=NO
     GTMODID=---------  TESTMODE=off
     OPTSN=gttset3   CGSELID=----- OPCSN=---------
     ACTSN=--------- PPMEASREQD= NO

Command Retrieved 1 Entries

Backup 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-12 Add Global Title Address Information - Sheet 1 of 9