chg-gtt

Use this command to change the routing objects for messages requiring global title translation. The global title addresses remain unchanged.

Note:

If the EGTT feature is turned on, then the GTT Selector (ent/chg/dlt/rtrvgttsel), GTT Set (ent/dlt/rtrv-gttset), and GTA (ent/chg/dlt/rtrvgta) commands replace the Translation Type (ent/dlt/rtrv-tt) and Global Title Translation (ent/chg/dlt/rtrv-gtt) commands. It is not recommended to run ent/dlt/rtrv-tt & ent/chg/dlt/rtrv-gtt commands as it may cause the advance GTA fields of GTT entry to be reset to the default values.

Parameters

Note:

See Point Code Formats and Conversion for a detailed description of point code formats, rules for specification, and examples.

gta (mandatory)

Global title address. The beginning of a range of global title digits.

Range:

1-21 digits

If the Hex Digit Support for GTT feature is not enabled, the range is 1 - 21 decimal digits; valid digits are 0-9.

If the Hex Digit Support for GTT feature is enabled and on, the range is 1 - 21 hexadecimal digits; valid digits are 0-9, a-f, A-F.

cggtmod (optional)

Calling party GT modification indicator. This parameter specifies whether calling party global title modification is required.

Range:

yes
no

Default:

no

egta (optional)

End global title address. The end of a range of global title digits.

Range:

1-21 digits

If the Hex Digit Support for GTT feature is not enabled, the range is 1 - 21 decimal digits; valid digits are 0-9.

If the Hex Digit Support for GTT feature is enabled and on, the range is 1 - 21 hexadecimal digits; valid digits are 0-9, a-f, A-F.

Default:

egta same as gta

gtmodid (optional)

Global title modification identifier.

Range:: ayyyyyyyy
1 alphabetic followed by up to 8 alphanumeric characters

Default:: No change to the current value

loopset (optional)

SCCP loopset name. This parameter associates a translation set with a loopset.

Range:

ayyyyyyy

1 alphabetic character followed by up to 7 alphanumeric characters.

none —Disassociates the translation set from all loopsets.

mapset (optional)

MAP set ID. The Mated Application set ID.

Range:: 1 - 36000, dflt
dflt —Default MAP set

mrnset (optional)

MRN set ID. The Mated Relay Node set ID.

Range:

1 - 3000, dflt, none

dflt -Default MRN set

none -The GTT translation does not participate in any load sharing

pc (optional)

ANSI point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm). The prefix subfield indicates a private point code (prefix-ni-nc-ncm).

Synonym:: pca

Range:

p-, 000-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—p-

When chg-sid:pctype=ansi is specified, ni = 000 is not valid.

When chg-sid:pctype=ansi is specified, nc = 000 is not valid if ni = 001-005.

When chg-sid:pctype=ansi is specified, nc = 000 is valid if ni = 006-255.

The point code 000-000-000 is not a valid point code.

pc/pca/pci/pcn/pcn24 (optional): Point code.

pci (optional)

ITU international point code with subfields zone-area-id. The prefix subfield indicates a spare point code, private point code, or private and spare point code (prefix-zone-area-id).

Range:

s-, p-, ps-, 0-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s-, p-, ps

zone—0-7

area—000-255

id—0-7

The point code 0-000-0 is not a valid point code.

pcn (optional)

ITU national point code in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the

 chg-stpopts:npcfmti

flexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code, private point code, or private and spare point code (prefix-nnnnn, prefix-nnnnn-gc ,prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).

Range:

s-, p-, ps-, 0-16383, aa-zz

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—s-, p-, ps

nnnnn—0-16383

gc—aa-zz

m1-m2-m3-m4—0-14 for each member; values must sum to 14

pcn24 (optional)

24-bit ITU national point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp). The prefix subfield indicates a private point code (prefix-msa-ssa-sp).

Range:

p-, 000-255

Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).

prefix—p

msa—000–255

ssa—000–255

sp—000–255

ri (optional)

Routing Indicator. This parameter provides routing instructions to the receiving signaling point. In gateway screening, messages may be screened based on the value of the routing indicator.

Range:

gt: Allow a called party address with a routing indicator value of global title.
ssn: Allow a called party address with a routing indicator value of dpc/ssn.

Default:

No change in current value.

split (optional)

Split or change an existing GTA range.

Range:

yes: Split the existing GTA range.
no: Change the existing GTA range.

Default:

yes

ssn (optional)

Subsystem number.

Range:: 002 - 255
Default:: If the xlat=dpcngt parameter is specified, there is no change to the current value.
If the xlat=dpcngt parameter is not specified, the ssn parameter is removed.

ttn (optional)

Translation type name.

Range:: ayyyyyyyy
1 alphabetic character followed by up to 8 alphanumeric characters
Default:: No translation name is given

type/typea/typei/typen/typen24/typeis/typens (optional)

Translation type. The translation type and network type. This parameter is the decimal representation of the 1-byte field used in SS7.

The type and typea parameters specify an ANSI network.

The typei parameter specifies an ITU-international network.

The typen parameter specifies an ITU-national network.

The typen24 parameter specifies a 24-bit ITU-national network.

The typeis parameter specifies an ITU-international spare network.

The typens parameter specifies an ITU-national spare network.

A translation type numeric value may be entered as an ANSI type (type or typea) and as an ITU type (typei/typen/typen24/typeis/typens). However, they are separate entities.

The point code domain translation types for GTT are handled by the EAGLE protocol processing as either ANSI or ITU; therefore, ITU applies to ITU-I, ITU-I spare, ITU-N, ITU-N spare, and ITU-N24.

Range:: 0 - 255
Default:: No translation type is specified

xlat (optional)

Translate indicator. Translation actions and routing actions.

Range:

dpc
dpcssn
dpcngt

Default:

No change in current value.

Example

chg-gtt:type=5:gta=9195551212:egta=9195551999:xlat=dpcssn:ri=ssn: pc=255-002-001 :ssn=255

chg-gtt:ttn=lidb2:gta=9197771212:egta=9197771999:xlat=dpcngt:ri=gt: pc=255-002-001

chg-gtt:ttn=lidb6:gta=910777:pc=255-002-002

chg-gtt: type=10:gta=8005553232:egta=8005554000:gtmodid=sn1

chg-gtt:type=11:gta=8005553232:egta=8005554000:gtmodid=none

chg-gtt:gta=123456:pci=s-1-129-7:typei=41

chg-gtt:gta=223456:pcn=s-128-aa:typen=3

chg-gtt:ttn=setmrn:gta=1234567890:egta=2234567890:pc=1-1-2:mrnset=none

chg-gtt:ttn=setmrn:gta=2234567891:egta=2234567892:pc=1-1-2:mrnset=dflt

chg-gtt:ttn=setmrn:gta=2345678901:egta=3456789012:pc=1-1-3:mrnset=2

chg-gtt:ttn=setmap:gta=2345678911:egta=3456789022:ri=ssn:pc=2-2-2:ssn=6: mapset=dflt

The database contains a GTA range [5556000-5558000], but no part of the GTA range [5558001-5559000] exists. This example deletes the GTA range [5556000-5558000] from the database and adds a new GTA range [5556800-5559000] to the database.

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

This example deletes the GTA range [5556800-5559000] from the database and adds three new GTA ranges [5556800-5556899], [5556900-5557000] and [5557001-5559000] to the database.

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

This example specifies hexadecimal digits for the gta, egta, and nsds parameters.

chg-gtt:type=1:xlat=dpcssn:ri=ssn:ssn=10:pc=1-1-1:gta=df3456789012345678906: egta=df345678901234567890a

chg-gtt:ttn=setmap:gta=2345678901:egta=3456789012:ri=ssn:pc=1-1-3:ssn=10:mapset=2: loopset=none:gtmodid=set6

This example specifies that calling party GT modification is required.

chg-gtt:gta=981234:type=4:cggtmod=yes

chg-gtt:typeis=5:gta=123456:egta=129999:xlat=dpc:ri=gt:pci=s-1-1-4

chg-gtt:typens=5:gta=123456:egta=129999:xlat=dpc:ri=gt:pcn=s-111

Dependencies

If the pcn parameter is specified, its format must match the format that was assigned with chg-stpopts:npcfmti.

The value specified for the tt parameter must correspond to the value specified for the type/typea/typei/typen/typen24/typeis/typens parameter.

The value of the tt parameter must exist in the Translation Type table.

The ANSI/ITU SCCP Conversion feature must be enabled before a translated point code and a translation type in different network types can be specified.

If the xlat=dpc, ri=ssn, and pc/pca/pci/pcn parameters are specified, then the point code must exist in the MAP table.

If the new or existing xlat parameter value is dpc, the new or existing ri parameter value is ssn, and the pc/pca/pci/pcn parameter is not specified, a point code must exist in the Remote Point Code/MAP table.

If the xlat parameter value is changed from dpcssn to dpc or dpcngt, a new ssn parameter value cannot be specified, and the current ssn parameter value must be removed.

If the new xlat parameter value is dpcssn, and the current ssn parameter value has been removed, a new ssn parameter value must be specified.

The start GTA length must equal the number of digits specified by the translation type. If the VGTT (variable length GTT) feature is turned on, then up to 10 GTA lengths per translation type are allowed. When the ent-gtt command is entered to create entries, the software keeps track of the lengths and allows only ten different lengths. The global title address specified for the translation type must then have the same number of digits as an existing GTA.

If the specified or previously provisioned translated point code is of type ANSI, then the ngti value of the referred GT Modification Identifier (see the ent-gtmod command) must be 2.

If the egta parameter is specified, the length must equal the length of the start GTA.

If the egta parameter is specified, the value must be greater than the value specified for the gta parameter.

The range of global title addresses to be changed, as specified by the start and end global title addresses, must match exactly or be contained within an existing range in the global title translation data for the specified translation type.

The new gta - egta range cannot include the GTA or EGTA of an existing range. However, the new GTA range can completely fall within an existing GTA range. If the range overlaps, an error is generated that displays a list of overlapped GTAs. An example follows that shows what happens when the user attempts to enter a global title address range (such as 8005550000 to 8005559999) that overlaps an existing range. The overlapping links must match. If they do not, the error message displays the list of overlapped global title addresses:

The following GTA ranges overlap the input GTA range 
START GTA END GTA 8005550000 8005551999 8005552000 8005553999 8005554000 8005555999 
CHG-GTT: MASP A - Command Aborted

The tt parameter cannot be specified with a value that has been defined as an alias for another translation type.

Either the type or the ttn parameter must be specified.

Point code entries must be full point codes. Partial point codes are not allowed.

Table 4-7 shows the valid combinations for the xlat, ri, and ssn parameters. All other combinations are rejected.

Table 4-7 Valid Parameter Combinations for chg-gtt Routing Parameters

New or Existing XLAT Value	New or Existing RI Value	Routing Action	SSN Value
DPC	GT	Translate DPC only and route on GT	Cannot be specified. The current database entry is removed.
DPC	SSN	Translate DPC only and route on SSN	Cannot be specified. The current database entry is removed.
DPCSSN	GT	Translate DPC and SSN and route on GT	Must be specified
DPCSSN	SSN	Translate DPC and SSN and route on SSN	Must be specified
DPCNGT	GT	Translate DPC only and route on GT	Cannot be specified. The current database entry is removed.

To enter this command, the Remote Point Code table cannot be full.

To enter this command, the subsystem table for primary remote point codes cannot be full.

If the ri=ssn parameter is specified, the mrnset parameter cannot be specified.

If the Flexible GTT Load Sharing feature is enabled, the point code must already exist in the specified MRN set.

The specified MRN set must already exist in the MRN table.

The Flexible GTT Load-Sharing feature must be enabled before the mrnset parameter can be specified.

The SEAS command is not allowed to operate on any other MRN set except the default MRN set.

The MRN table is corrupt or cannot be found.

The mapset parameter can only be specified if the Flexible GTT Load Sharing feature is enabled, and the ri=ssn parameter is specified. If the ri=ssn parameter is specified, the mapset parameter must be specified. If the ri=gt parameter is specified, the mapset parameter cannot be specified.

If the Flexible GTT Load Sharing feature is not enabled, the mapset parameter cannot be specified.

At least one entry must be provisioned in the specified MAP set in the MAP table.

The MAP table is corrupt or cannot be found.

The specified or previously provisioned point code and subsystem number must exist in the specified or previously provisioned MAP set.

The SEAS command cannot operate on any MAP set other than the default MAP set.

The specified GTA must lie within an existing GTA range in the specified GTT Set.

The specified GTA range must not overlap with any other existing GTA range in the specified GTT Set.

If the Flexible GTT Load Sharing feature is enabled, then the specified PC must exist in the MRN set.

If the ri=gt parameter is specified, the mapset parameter cannot be specified.

The Hex Digit Support for GTT feature must be turned on before hexadecimal digits can be specified for the gta or egta parameter.

The Loopset table is corrupt or cannot be found.

The SCCP Loop Detection feature must be enabled before the loopset parameter can be specified.

The value of the loopset parameter must exist in the Loopset table.

The site identification table is corrupt or cannot be found.

The Route table is corrupt or cannot be found.

The database is corrupt or cannot be found. Severe database failure.

The Loopset table is corrupt or cannot be found.

If the ri=gt parameter is specified, the mrnset parameter must be specified.

The GTT table cannot be full.

If the value of the pc/pca/pci/pcn/pcn24 parameter is the True Point Code, then the xlat=dpcssn parameter and the ri=ssn parameter must be specified.

If the ssn parameter is specified, and if the value of the pc/pca/pci/pcn/pcn24 parameter is the True Point Code, then the value of the ssn parameter must exist in the SS-APPL table.

The value of the pc/pca/pci/pcn/pcn24 parameter must exist as a destination in the ordered route entity set or must reside in a cluster (ANSI only) that exists as a destination in the ordered route entity set.

If the xlat=dpcssn and ri=gt parameters are specified, then the ssn parameter must be specified.

The xlat=dpcssn parameter must be specified before the ssn parameter can be specified.

If the xlat=dpcngt parameter is specified, then the ri=gt parameter must be specified.

The gta length is not defined for the specified translation type entity.

If the tt parameter is not specified, then the value of the ttn parameter must match the value of a tt parameter in the STP database.

The value of the pc/pca/pci/pcn/pcn24 parameter cannot be out of range.

At least one optional parameter must be specified.

The value specified for the pc parameter cannot be associated with a proxy point code.

The AMGTT feature or the AMGTT CgPA Upgrade feature must be turned on before the cggtmod parameter can be specified.

The GTT set associated with the translation type specified by the ttn parameter must have a set type of cdgta (see the ent-gttset command).

The value specified by the gtmodid parameter must already exist in the GTMOD table (see the ent-gtmod command).

The GTMOD table is corrupt or cannot be found.

The ttn=none parameter cannot be specified.

The network domain of the translation type specified by the ttn parameter cannot be CROSS (see the ent-gttset command).

The xlat=none parameter cannot be specified.

The values specified for the gta and egta parameters must match the GTA values referred in the GTT Action Path table (see the ent-gttapath command).

Notes

The specified DPC, SSN, relative cost, and routing indicator will overwrite the existing data values in the table.

When the Intermediate GTT Load Sharing feature and the Flexible GTT Load Sharing feature are on, multiple relationships can be defined among a set of destination point codes in the existing MRN table. The relationship used in a particular translation is based on the GTA digits used for translation. The MRN Set and the post-translation PC formulate a key used as a lookup in the MRN table. The MRN table lookup results in a set of alternate PCs, one of which is selected (based on relative cost) to route the MSU in the most cost effective way.

When the Flexible GTT Load Sharing feature is turned on, multiple relationships among a set of PCs and SSNs in the existing MAP table are supported. The relationship used in a particular translation is based on the GTA digits used for translation. The MAP set ID and PC/SSN formulate a key that is used to perform lookup tasks in the MAP table. The lookup results in a set of mate PC/SSNs, one of which is selected to route the MSU in the most cost effective way.

If the AMGTT feature is turned off, then the Default GT Conversion table is used for conversion.

AMGTT feature: The digit manipulation parameters NSDD, NSDS are enabled with the AMGTT feature. NSDD and NSDS (suffix digit manipulation parameters) are mutually exclusive of the NPDD and NPDS (prefix digit manipulations parameters).

Spare Point Code feature (53120): The point code parameters PCI and PCN supports the Spare Point Code subtype prefix (s-). The Point Code domain translation types for GTT are handled by the system protocol processing as ANSI or ITU. ITU applies to ITU-I, ITU-I Spare, ITU-N, and ITU-N Spare. ITU-I includes ITU-I Spare, and ITU-N includes ITU-N Spare.

Flexible GTT Load Sharing feature (74382): The Flexible GTT Load Sharing feature allows a PC or PC/SSN combination to be provisioned in multiple load-sharing relationships for post-GTT load sharing of intermediate and final GTT traffic.

Load sharing for intermediate GTT traffic requires the Intermediate GTT Load Sharing feature, which can be run in conjunction with the Flexible GTT Load Sharing feature. Intermediate GTT load sharing is performed through the MRN table, and the GTT destination is a PC. If both the Intermediate and Flexible GTT Load Sharing features are on, different load-sharing relationships can be defined between the same set of PCs, and different sets of destinations can contain the same PCs.

Load sharing for final GTT traffic is performed through the MAP table, and the GTT destination is a PC/SSN combination. If the Flexible GTT Load Sharing feature is on, different load-sharing relationships can be defined between the same set of PC/SSNs, and different sets of destinations can contain the same PC/SSN combinations.

A loopset consists of a set of point codes that form a routing loop in the network. If the SCCP Loop Detection feature is enabled, then the loopset can be associated with or disassociated from specified translation entries. Loopsets that are associated with translation entries are checked during intermediate and final GTT traffic routing. If a loop exists, then the system can be notified with or without discarding the associated traffic.

The maximum length of the resulting GTA string must not exceed 21 digits when translation is complete.

If the range specified by the gta and egta parameters does not exactly match the existing range, then the existing range is split. All addresses in the existing range that are outside the range specified by the gta and egta parameters retain the original xlat, ri, pc, and ssn parameters.

A new range is created that is bounded by the gta and egta parameters. The new range contains new values for the xlat, ri, pc, and ssn parameters that are present in the command, while retaining parameter values from the previous range that do not have corresponding new values in the command.

If the EGTT feature is turned on, then the following occurs for the chg-gtt command:

For ANSI, if a GTT selector is deleted using the dlt-gttsel command, then the corresponding GTT entry cannot be updated.
For ITU, if a true GTT selector entry (GTI=2 or GTI=4) is deleted using the dlt-gttsel command, or if the GTT set name of an entry is changed using the chg-gttsel command, then the corresponding GTT entry cannot be updated.

Output


		  chg-gtt:gta=981234:type=4:cggtmod=yes:gtmodid=set3


    tekelecstp 10-03-09 17:29:06 EST  EAGLE 42.0.0
    CHG-GTT: MASP A - COMPLTD 
;

4.70 chg-gtt