ent-gtt

Use this command to add the routing object, DPC, and subsystem number for messages requiring global title translation. The translation is performed on the basis of the global title address (GTA) and translation type (TT) for each SS7 SCCP message directed to the STP’s self-identity DPC or CPC with a routing indicator of 0, indicating a GTT is required.

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 on, the range is 1 - 21 hexadecimal digits; valid digits are 0-9, a-f, A-F.

pc (mandatory)

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 (mandatory): Point code.

pci (mandatory)

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 (mandatory)

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 (mandatory)

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 (mandatory)

Route indicator. This parameter specifies whether a subsequent global title translation is required.

Range:

gt: Subsequent translation is required.
ssn: Subsequent translation is not required.

xlat (mandatory)

Translate indicator. The type of global title translation to be performed.

Range:

dpc
dpcssn
dpcngt

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)

Global title end 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:

the gta value

force (optional)

When a final GTT is specified, the DPC and subsystem number must be configured in the mated application table (xlat=dpc and ri=ssn). The force=yes parameter overrides this restriction.

Range:

yes
no

Default:

no

gtmodid (optional)

Global title modification identifier.

Range:: ayyyyyyyy
1 leading alphabetic character followed by up to 8 alphanumeric characters
Default:: none

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 —There is no association between the translation set and any loopset

Default:

none

mapset (optional)

MAP set ID.

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

mrnset (optional)

MRN set ID.

Range:

1 - 3000, dflt, none

dflt —Default MRN Set ID

none —Removes the specified MRN Set ID from the MRN table

ssn (optional)

Subsystem number. The subsystem address that will receive the message.

This parameter is required and can only be specified if the xlat=dpcssn parameter is specified.

Range:: 002 - 255

ttn (optional)

Translation type name. The name is of local significance only, and is related to the translation type.

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. This parameter identifies 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/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:: 000 - 255
Default:: No translation type is specified

Example

The lines in the following examples are wrapped for readability:

ent-gtt:type=3:gta=9195551212:egta=9195552000:

xlat=dpcssn:ri=ssn:pc=001-255-255:ssn=255

ent-gtt:ttn=lidb1:gta=9105551212:egta=9105554000:

xlat=dpcngt:ri=gt:pc=001-255-254

ent-gtt:ttn=c800:gta=9195554321:xlat=dpc:ri=gt:pc=001-255-253

ent-gtt:type=4:gta=919460:xlat=dpc:ri=ssn:pc=001-255-252

ent-gtt:type=4:gta=919461:xlat=dpcssn:ri=gt:ssn=254

ent-gtt:typea=210:ttn=test:gta=100000:egta=199999:

pca=1-1-1:ssn=123:xlat=dpcngt:ri=gt: gtmodid=abc1

ent-gtt:type=100:ttn=test2:gta=123:egta=321:

pcn=222:ssn=10:xlat=dpcngt:ri=gt: gtmodid=id1

ent-gtt:pcn24=8-8-8:gta=919833:xlat=dpcssn:ri=ssn:ssn=20:typen24=4

ent-gtt:typea=100:ttn=test2:gta=123:egta=321:

pci=2-2-2:ssn=10:xlat=dpcngt:ri=gt

ent-gtt:xlat=dpcssn:ssn=10:ri=gt:pci=s-1-21-1:gta=123456:typei=3

ent-gtt:xlat=dpcssn:ssn=10:ri=gt:pcn=s-124:gta=123456:typen=3

ent-gtt:xlat=dpcssn:ssn=10:ri=gt:pcn=s-125-aa:gta=123456:typen=3

ent-gtt:type=1:xlat=dpc:ri=gt:pc=1-1-1:

gta=1234567890:egta=2234567890:mrnset=23

ent-gtt:type=1:xlat=dpcngt:ri=gt:pc=1-1-2:

gta=2345678901: egta=3456789012:mrnset=54

ent-gtt:type=1:xlat=dpcngt:ri=gt:pc=1-1-3:

gta=3456789013: egta=3456789019:mrnset=dflt

ent-gtt:type=1:xlat=dpcngt:ri=gt:pc=1-1-3:

gta=3456789012: egta=4567890123:mrnset=none

ent-gtt:type=1:xlat=dpcssn:ri=ssn:pc=1-1-1:

gta=1234567890:egta=2234567890:ssn=10: mapset=23

ent-gtt:type=1:xlat=dpcssn:ri=ssn:pc=2-2-2:

gta=2345678911:egta=3456789022:ssn=25: mapset=dflt

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

ent-gtt:ttn=set1:xlat=dpcssn:ri=ssn:ssn=10:pc=1-1-1:gta=abcd:egta=abce

This example specifies that calling party GT modification is required.

ent-gtt:xlat=dpc:pc=1-1-1:ri=gt:gta=981234:type=4:cggtmod=yes

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

ent-gtt:xlat=dpc:ri=gt:pcn=s-111:gta=123456:typens=5

Dependencies

The end address must be greater than or equal to the start address.

The pcn parameter format must match the format that was assigned with the chg-stpopts:npcfmti parameter.

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

The start global title address length must be equal to the number of digits specified by the given translation type. If the VGTT (variable length GTT) feature is turned on, then up to 10 GTA lengths per translation type can be provisioned. When this command is entered to create entries, the software keeps track of the lengths and allows only 10 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 end global title address is specified, its length must equal the length of the start global title address.

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

If the translation type is specified, then it must already exist and cannot be an alias.

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

When the translated point code is of type ANSI, the ngti parameter of the referred GTMOD cannot have a value of 4. For ANSI PCs, the ngti parameter must have a value of 2.

The range, as specified by the start and end global title addresses, cannot exist in the global title translation data for the specified translation type. Each range may be contained completely within a previously defined range, in which case splitting is performed. However, if the ranges overlap, splitting cannot occur, the command is rejected, and a list of overlapped global title addresses is displayed. 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, error message E2401 is generated displaying 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 ENT-GTT: MASP A - Command Aborted

If a final GTT is specified with the ri=ssn parameter and the xlat=dpc parameter, and if the value of the force parameter is not yes, the point code must be configured in the Remote Point Code/MAP Table.

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

If the xlat=dpcssn parameter is specified, then the ssn parameter must be specified.

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

Table 4-24 Valid ent-gtt Routing Parameter Combinations

XLAT Value	RI Value	Routing Action	SSN Value
DPC	GT	Translate DPC only and route on GT	Cannot specify
DPC	SSN	Translate DPC only and route on SSN	Cannot specify
DPCSSN	GT	Translate DPC and SSN and route on GT	Must specify
DPCSSN	SSN	Translate DPC and SSN and route on SSN	Must specify
DPCNGT	GT	Translate DPC only and route on GT	Cannot specify

If the XGTT feature is enabled, then the GTT table can have up to either 400,000 or 1,000,000 entries, depending on the controlled feature Part Number that is enabled. If XGTT is not enabled, then the GTT table can contain up to 269,999 user entries.

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 specified PC 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.

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

The MRN table is corrupt or cannot be found.

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

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

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.

The specified PC and SSN must exist in the specified MAP set.

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

If the xlat=dpc parameter is specified, and the force parameter is not specified as yes, the specified PC and MAP set must exist in the MAP table.

The MAP table is corrupt or cannot be found.

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

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

The value of the loopset parameter must already exist in the database.

The tt or the ttn parameter must be specified.

The value specified for the pc/pca/pci/pcn/pcn24 parameter must be a valid point code.

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.

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 (for global title routing).

If the VGTT feature is turned on, then up to 10 GTA lengths can exist per translation type. If the Support for 16 GTT Lengths in VGTT feature is turned on, then up to 16 GTA lengths can exist per translation type.

The value of the tt parameter must not be defined as an alias.

If both the translation type (tt) and translation type name (ttn) are specified, the translation type name (ttn) must match that of the specified translation type (tt).

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.

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

The site identification table is corrupt or cannot be found.

The Route table is corrupt or cannot be found.

The Loopset table is corrupt or cannot be found.

The database is corrupt or cannot be found.

The GTT table cannot be full.

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 for the gtmodid parameter must already exist in the GTMOD table.

The GTMOD table is corrupt or cannot be found.

The gtmodid=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 ttn=none parameter cannot be specified.

The length of the specified gta parameter must match the number of digits provisioned for the specified GTT set (gttsn) when the VGTT feature is turned off. If the VGTT feature is turned on, then up to 10 GTA lengths can exist per GTT set. If the Support for 16 GTT Lengths in VGTT feature is turned on, then up to 16 GTA lengths can exist per GTT set.

SSN configured for SFAPP cannot be used in any command for any configuration

Notes

The routing indicator provides routing instructions to the receiving signaling point. If the routing indicator specifies global title, global title translation then needs to be performed at another signaling point.

Up to 200,000 entries are allowed for an individual translation type if all SCCP cards are E5-TSM cards or DSM cards.

The ANSI point code 0 and the ITU-I point code 0-000-0 are not valid point codes.

The EAGLE does not require a MAP table entry to be configured prior to provisioning a GTT entry. The EAGLE assumes that the GTT entry is for a solitary point code/subsystem and automatically creates a MAP entry for the point code/subsystem.

In this command, only ITU-international and ITU national point codes support the spare point code subtype prefix (s-) and the private and spare point code subtype prefix (ps-). All of the point code types support the private (internal) point code subtype prefix (p-).

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

The FGTTLS feature introduces the mrnset parameter. The MRNSET and post-translation PC create a key that is used to perform lookup tasks in the MRN table. This lookup results in a set of alternate PCs, from which one is selected, based on the PCs relative cost, to route the MSU in the most cost-effective way.

When the FGTTLS feature is turned on, multiple relationships can be defined among set of PC/SSNs in the existing MAP table. The relationship used in a particular translation is based on the GTA digits used for translation.

When the FGTTLS feature is ON, the mapset parameter is used. The MAP set and PC/SSN creates a key that is used to perform lookup tasks in the MAP table. The lookup into the MAP table results in a set of mate PC/SSNs, from which one 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.

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.

If the OBSR or FLOBR feature is turned on, then this command can provision only translation entries with a set type of CdGTA.

If the EGTT feature is turned on, then the following occurs:

For ANSI, if the GTT selector of a true entry is deleted using the dlt-gttsel command, then a GTT entry cannot be created for that translation type.
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 a GTT entry cannot be created for that translation type.

Output


		  ent-gtt:xlat=dpc:pc=12-1-11:ri=gt:gta=981234:type=4:cggtmod=yes:gtmodid=set1


    tekelecstp 10-03-09 12:06:11 EST  EAGLE 42.0.0
    ENT-GTT: MASP A - COMPLTD 
;

4.304 ent-gtt