ent-gta

4.301 ent-gta

Use this command to specify the GTA (global title address) 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 a global title translation. The translation is performed on the basis of the global title address (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 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.

gttsn (mandatory)

GTT set name. The entity to which global title addresses and selectors are assigned.

Range:: ayyyyyyyy
1 leading alphabetic and up to 8 following alphanumeric characters

xlat (mandatory)

Translate indicator. This parameter specifies translation actions and routing actions.

Range:

dpc
dpcngt
dpcssn
none

acn (optional)

Application context name. This parameter specifies the ITU TCAP acn field in the incoming MSU.

Range:

0 - 255, *, none

The acn supports up to 7 subfields separated by dash (e.g., 1-202-33-104-54-26-007)

* —any valid value in the ITU TCAP acn field in the incoming MSU

none —there is no ITU TCAP acn field in the incoming MSU

actsn (optional)

GTT Action Set Name.

Range:: ayyyyyyyy
1 leading alphabetic character and up to 8 following alphanumeric characters

ccgt (optional)

Cancel called global title indicator.

Range:

yes
no

Default:

cdselid (optional)

CdPA Selector ID.

Range:: 0 - 65534

cdssn (optional)

Starting CdPA subsystem number.

Range:: 0 - 255

cgcnvsn (optional)

CgPA conversion set name.

Range:: ayyyyyyyy
1 leading alphabetic character and up to 8 following alphanumeric characters

cggtmod (optional)

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

Range:

yes
no

Default:

cgpc (optional)

ANSI CgPA point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).

Synonym:

cgpca

Range:

0-255, *

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

The asterisk (*) value is not valid for the ni subfield.

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.

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

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

cgpcaction (optional)

This parameter is used to provide the required abilities, indicating what any particular translation needs to do with CgPA PC.

Range:: dflt; protocol will be allowed to perform all the required processing/conversion with CGPC.; ignore; CGPC will be left as it was in incoming MSU.; remove; CGPC will be removed from outgoing MSU.
Default:: dflt

cgpci (optional)

ITU international CgPA point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).

Range:

s-, 0-255

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

prefix—s

zone—0-7

area—000-255

id—0-7

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

cgpcn (optional)

ITU national CgPA 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 (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).

Range:

s-, 0-16383, aa-zz

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

prefix—s-

nnnnn—0-16383

gc—aa-zz

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

cgpcn24 (optional)

24-bit ITU national CgPA point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).

Range:

000-255

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

msa—000–255

ssa—000–255

sp—000–255

cgpcn16 (optional)

16-bit ITU national CgPA point code with subfields unit number-sub number area-main number area (un-sna-mna).

Range:: 000--127; Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).; un---000---127; sna---000---15; mna---000---31

cgselid (optional)

CgPA Selector ID.

Range:: 0 - 65534

cgssn (optional)

Starting CgPA subsystem number.

Range:: 0 - 255

defmapvr (optional)

Default MAP version for MBR opcodes. This parameter is used to provide the default MAP version for supported MBR opcodes if Application Context Name (ACN) is not present in an incoming MAP message.

Range:

v1
v2
v3

Default:

dpc (optional)

ANSI destination point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).

Synonym:

dpca

Range:

0-255, *

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

The asterisk (*) value is not valid for the ni subfield.

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.

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

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

dpc/dpca/dpci/dpcn/dpcn24/dpcn16 (optional): Point Code.

dpci (optional)

ITU international destination point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).

Range:

s-, 0-255

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

prefix—s

zone—0-7

area—000-255

id—0-7

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

dpcn (optional)

ITU destination 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 (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).

Range:

s-, 0-16383, aa-zz

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

prefix—s-

nnnnn—0-16383

gc—aa-zz

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

dpcn24 (optional)

24-bit ITU national destination point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).

Range:

000-255

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

msa—000–255

ssa—000–255

sp—000–255

dpcn16 (optional)

16-bit ITU national destination point code with subfields unit number-sub number area-main number area (un-sna-mna).

Range:: 000--127; Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).; un---000---127; sna---000---15; mna---000---31

eaddr (optional)

End Address (similar to EGTA). This parameter specifies the end of a range of MAP digits (IMEI/IMSI/MSISDN/VLRNB/SMRPOA/SMRPDA).

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:

Same as the specified SADDR value

ecdssn (optional)

Ending CdPA subsystem number.

Range:: 0 - 255

ecgssn (optional)

Ending CgPA subsystem number.

Range:: 0 - 255

egta (optional)

End global title address. This parameter specifies 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:

Same as the specified gta value

fallback (optional)

Fallback option. The action taken when the final translation does not match while performing GTT using a FLOBR-specific GTT mode.

Range:

yes: perform GTT based on the last matched entry
no: GTT fails and the MSU is discarded
sysdflt: use the system-wide default fallback option in the SCCPOPTS table

Default:

sysdflt

family (optional)

The ANSI TCAPfamily field in the incoming MSU.

Range:

0 - 255, *, none

* —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

force (optional)

Check mated application override. This parameter must be used to complete command execution if the pci/pcn and ssn parameter combination specified in the command is not already defined in the SCCP Application entity set (Remote Point Code/Mated Application Table).

Range:

yes
no

Default:

gta (optional)

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.

gtmodid (optional)

Global title modification identifier.

Range:: ayyyyyyyy
1 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 leading alphabetic character and up to 7 following alphanumeric characters.

none —There is no association between the translation set and any loopset.

Default:

none

mapset (optional)

MAP set ID. This parameter specifies 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 GTA translation does not participate in any load sharing

opc (optional)

ANSI originating point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).

Synonym:

opca

Range:

0-255, *

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

The asterisk (*) value is not valid for the ni subfield.

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.

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

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

opc/opca/opci/opcn/opcn24/opcn16 (optional): Originating Point Code

opci (optional)

ITU international originating point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).

Range:

s-, 0-255

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

prefix—s

zone—0-7

area—000-255

id—0-7

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

opcn (optional)

ITU originating 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 (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).

Range:

s-, 0-16383, aa-zz

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

prefix—s-

nnnnn—0-16383

gc—aa-zz

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

opcn24 (optional)

24-bit ITU national originating point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).

Range:

000-255

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

msa—000–255

ssa—000–255

sp—000–255

opcn16 (optional)

16-bit ITU national originating point code with subfields unit number-sub number area-main number area (un-sna-mna).

Range:: 000--127; Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).; un---000---127; sna---000---15; mna---000---31

opcodetag (optional)

The ITU TCAP opcodetag field in the incoming MSU.

Range:

none, local, global, any

none —there is no value in the ITU TCAP opcodetag field in the incoming MSU

local —The opcodetag is local in the ITU TCAP opcodetag field in the incoming MSU

global —The opcodetag is global in the ITU TCAP opcodetag field in the incoming MSU

any — any valid value in the ITU TCAP opcodetag field in the incoming MSU

Default:

any

opcsn (optional)

The OPC GTT set name.

Range:: ayyyyyyyy
1 leading alphabetic character and up to 8 following alphanumeric characters

optsn (optional)

Optional gtt set name.

Range:: ayyyyyyyy
1 leading alphabetic character and up to 8 following alphanumeric characters.

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/pcn16 (optional): Point code.

pci (optional)

ITU international destination 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

pcn16 (optional)

16-bit ITU national point code with subfields unit number-sub number area-main number area (un-sna-mna). The prefix subfield indicates a private point code (prefix- un-sna-mna).

Range:: p, 000--127; Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).; prefix---p; un---000---127; sna---000---15; mna---000---31

pkgtype (optional)

The ANSI and ITU TCAP package type.

Range:

ituuni: ITU unidirectional
qwp: Query with Permission
qwop: Query without Permission
resp: Response
cwp: Conversation with Permission
cwop: Conversation without Permission
any: Wildcard value
bgn: Begin
end: End
cnt: Continue
ituabort: ITU abort
ansiabort: ANSI abort
ansiuni: ANSI unidirectional
ANSI TCAP Package Types: ansiuni, qwp, qwop, resp, cwp, cwop, ansiabort, any
ITU TCAP Package Types: bgn, ituabort, ituuni, any, end, cnt

ppmeasreqd (optional)

This parameter specifies whether Per Path measurements are required.

Range:

yes: per path measurements are required
no: per path measurements are not required

Default:

No change to the current value

prio (optional)

This parameter assigns priority to an OPCODE GTTSET based translation.

Range:: 1 - 1024
1 is the highest priority and 1024 the lowest
Default:: 1024

ri (optional)

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

saddr (optional)

Start Address (similar to GTA). This parameter specifies the beginning of a range of MAP digits (IMEI/IMSI/MSISDN/VLRNB/SMRPOA/SMRPDA).

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.

ssn (optional)

New translated subsystem number.

Range:: 002 - 255
Default:: none

testmode (optional)

This parameter is used to invoke a field-safe Test Tool in order to debug the FLOBR/TOBR rules.

Caution:

If the testmode=on parameter is specified, then the rule is used only by test messages. The rule is ignored by 'live' traffic. If the testmode=off parameter is specified, then both test and live messages use the rule. Changing from testmode=off to testmode=on is equivalent to deleting the rule for live traffic.

Range:

on: Process the translation rules defined in the test message
off: Perform standard GTT behavior

Default:

off

transmeasrqd (optional)

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

Range:

yes: perform per GTT Translation Measurements
no: do not perform per GTT Translation Measurements

Default:

Example

The lines in some examples are wrapped for readability:

ent-gta:gttsn=lidb:gta=9195554321:xlat=dpc:ri=gt:pc=001-255-253

ent-gta:gttsn=t800:gta=919460:xlat=dpc:ri=gt:pc=001-255-252

ent-gta:gttsn=t800:gta=919461:egta=919468:

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

ent-gta:gttsn=setint000:gta=391951212000000:

egta=391951212399999:xlat=dpcssn :ri=ssn:pci=1-253-1:ssn=255

ent-gta:gttsn=imsi:gta=591975593000000:

egta=591975593299999:xlat=dpcngt:ri=gt :pci=004-167-25

ent-gta:gttsn=test:gta=100000:egta=199999:

pca=1-1-1:ssn=123:xlat=dpcngt:gtmodid=set1

ent-gta:gttsn=test2:gta=123:egta=321:

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

ent-gta:xlat=dpcssn:ri=ssn:pcn24=8-8-8:gttsn=any:gta=919833:ssn=20

ent-gta:xlat=dpcssn:ri=ssn:ssn=10:gta=12345678901:

egta=23456789012:gtmodid=set3:pcn=s-124: gttsn=setnat003

ent-gta:xlat=dpcssn:ri=ssn:ssn=10:gta=12345688901:

egta=23456889012:pcn=s-128-aa: gttsn=setnat003

ent-gta:gta=987666799012345678901:egta=987667321099765432101

xlat=dpcngt:ri=gt:pcn=s-124-aa:ccgt=no: gttsn=setnat003:gtmodid=set6

ent-gta:xlat=dpcssn:ri=ssn:ssn=10:gta=13345688901:

egta=24456889012:pci=s-1-230-2:gttsn=itui1

ent-gta:gttsn=tbla:xlat=dpc:ri=gt:pc=1-1-1:gta=1234567700:mrnset=dflt

ent-gta:gttsn=tbla:xlat=dpc:ri=gt:pc=1-1-1:gta=1234567890:

egta=2234567890:mrnset=23

ent-gta:gttsn=tbla:xlat=dpcngt:ri=gt:pc=1-1-2:gta=2345678901:

egta=3456789012:mrnset=54

ent-gta:gttsn=tbla:xlat=dpcngt:ri=gt:pc=1-1-3:gta=3456789012:

egta=4567890123:mrnset=none

ent-gta:gttsn=tblx:xlat=dpcssn:ri=ssn:pc=1-1-1:gta=1234567890:

egta=2234567890:ssn=10: mapset=23

ent-gta:gttsn=tblx:xlat=dpc:ri=ssn:pc=2-2-2:gta=2345678911:

egta=3456789022:mapset=dflt

ent-gta:gttsn=t800:gta=919460:xlat=dpc:ri=gt:pc=001-255-252:transmeasrqd=yes

This example provisions GTA translations when TOBR is turned on.

ent-gta:gttsn=setopcode:opcode=*:pkgtype=bgn:acn=*:xlat=dpc:ri=gt:pci=1-1-1:prio=1024:opcodetag=local

This example provisions Advanced CdPA GTA translations.

ent-gta:gttsn=setcdgta:gta=123456789012345678901:egta=223456789012345678901:

xlat=dpcssn:ri=ssn:pca=001-001-001:ssn=100:optsn=setcggta:opcsn=setopc

This example provisions GTA translations when FLOBR is turned on.

ent-gta:gttsn=setcdgta:gta=1234567890:egta=2234567890:

xlat=dpcssn:ri=ssn:pca=001-001-001:ssn=100:fallback=yes:testmode=on

ent-gta:gttsn=setudts1:gta=423456789012345678901:

xlat=dpc:ri=gt:pc=2-2-2:egta=523456789012345678901:actsn=actudts1

ent-gta:gttsn=setcggta:gta=323456789012345678901:egta=423456789012345678901:

xlat=dpcssn:ri=ssn:pca=001-001-001:ssn=20:optsn=setcgssn

ent-gta:gttsn=cggtadsc:gta=623456789012345678901:

egta=623456789012345678901: actsn=actdisc1

ent-gta:gttsn=setcgpc:cgpca=001-001-001:xlat=dpcssn:

ri=ssn: pca=001-001-001:ssn=20:optsn=setcgssn

ent-gta:gttsn=cgpcudt2:xlat=dpc:ri=gt:pc=2-2-2:

cgpca=001-001-009:actsn=actudts2

ent-gta:gttsn=setopc:opca=002-001-001:xlat=dpcssn:

ri=ssn: pca=001-001-001:ssn=20:optsn=setcgssn

ent-gta:gttsn=opcdis3:opca=002-001-001:actsn=actdisc1

ent-gta:gttsn=setcgssn:cgssn=100:ecgssn=200:

xlat=dpcssn:ri=ssn: pca=001-001-001:ssn=20

ent-gta:gttsn=cgssnud3:xlat=dpc:ri=gt:pc=001-002-003:

cgssn=100:ecgssn=200:actsn=actudts1: ppmeasreqd=yes

ent-gta:gttsn=setans004:gta=981817:xlat=dpc:pc=1-1-1:ri=gt:cggtmod=yes

ent-gta:gttsn=tblx:xlat=dpcssn:ri=ssn:pc=1-1-1:

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

The following example provisions the flexible GTA translations when the FLOBR and OBSR features are turned on.

ent-gta:gttsn=setcggta:gta=1234567890:egta=2234567890:

xlat=dpcssn:ri=ssn:pca=001-001-001:ssn=100:fallback=yes:opcsn=setopcsn

ent-gta:gttsn=setopc:opca=2-2-2:xlat=dpcssn:ri=ssn:

pca=001-001-002:ssn=100:optsn=setcgpc:fallback=no

ent-gta:gttsn=setcdgta:gta=567565756552:

xlat=dpc:ri=gt:pc=1-1-2:optsn=setcgpc:fallback=no:opcsn=setopc

This example provisions GTA translation when the FLOBR feature is turned on.

ent-gta:gttsn=setcdssn:cdssn=5:xlat=dpc:ri=gt:pc=1-1-1:opcsn=setopc

These examples provision the GTA translations when the TOBR and OBSR features are turned on.

ent-gta:gttsn=setopcode:pkgtype=qwop:opcode=none:family=*:

xlat=dpc:ri=gt:pc=2-2-2:opcsn=setopc: optsn=setcdgta

ent-gta:gttsn=setopcode:pkgtype=bgn:opcode=none:acn=1-2-3-4-5-6-7:

xlat=dpc:ri=gt:pc=2-2-2:opcsn=setopc: optsn=setcdgta

ent-gta:gttsn=setopcode:pkgtype=bgn:opcode=2:defmapvr=v2:

xlat=dpc:ri=gt:pci=2-2-2:opcsn=setopc:optsn=imsi1

ent-gta:gttsn=imsi1:xlat=dpc:ri=gt:pc=1-1-1:saddr=1234567890:eaddr=2234567890

This example provisions a DPC translation when the FLOBR feature is turned on.

ent-gta:gttsn=setdpc:xlat=dpc:ri=gt:pc=1-1-1:dpc=1-1-2:optsn=setdpc1

ent-gta:gttsn=setcdgta:xlat=none:actsn=asetdisc:ppmeasreqd=yes

ent-gta:gttsn=setopcode:pkgtype=bgn:opcode=none:

acn=1-2-3-4-5-6-8:xlat=none:mapset=1: mrnset=1

Example for 16 bit PC and CGPCACTION param.

ent-gta:gttsn=gtt1:xlat=dpc:ri=ssn:pcn16=1-14-0:cgpcn16=45-1-0:

mapset=dflt:cgpcaction=ignore

Dependencies

The EGTT feature must be turned on before this command can be entered.

The ANSI/ITU SCCP Conversion feature must be enabled before a translated PC that is of a different domain than the GTT set specified by the gttsn parameter can be specified.

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

The gttsn parameter must be specified and must match an existing gttsn.

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

If the egta/eaddr parameter is specified, then the values of the gta/saddr and egta/eaddr parameters must be the same length.

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

The specified gta/egta or saddr/eaddr range must exist for the specified GTT set in the STP active database. While an exact match is not required, you cannot specify an overlap with another range. If the range overlaps, an error is generated that displays a list of overlapped global title addresses. 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 ENT-GTA: MASP A - Command Aborted

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

If the new or existing pc/pca/pci/pcn/pcn24/pcn16 parameter is the STP point code or capability point code, then the ccgt=no parameter must be specified.

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

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

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

If the value specified for the pc/pca/pci/pcn/pcn24/pcn16 parameter is the STP’s true point code, the xlat=dpcssn and ri=ssn parameters must be specified.

If the value specified for the pc/pca/pci/pcn/pcn24/pcn16 parameter is the STP’s true point code and the ssn parameter is specified, the ssn parameter must exist in the SS-APPL table.

Unless the PC is the STP true PC, the value specified for the pc/pca/pci/pcn/pcn24/pcn16 parameter 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 routing).

If a final GTT (the ri=ssn parameter is specified with the xlat=dpc parameter and without the force=yes parameter), then the PC (pc/pca/pci/pcn/pcn24/pcn16) must exist in the Remote Point Code/MAP table. The force=yes parameter can be specified to execute the command when the PC is not in the table; the following warning message is displayed in the scroll area of the terminal:

CAUTION: DPC DOES NOT EXIST IN MATED APPLICATION TABLE.

If the ccgt=yes parameter is specified, then the ri=ssn parameter must be specified.

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

If the pc/pca/pci/pcn/pcn24/pcn16 parameter is any of the STP’s PCs or CPCs, then the ccgt=no parameter must be specified.

If the XGTT feature is enabled, the GTT table can contain 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, the GTT table can contain up to 269,999 user entries. An error message is displayed if a command entry would result in more than the allowed maximum number of entries in the table.

If the egta/eaddr parameter is specified, then the value of the egta/eaddr parameter must be greater than or equal to the value of the gta/saddr parameter.

The GTT Set Name must not be none.

The pc/pca/pci/pcn/pcn24/pcn16 parameter must be a full PC.

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

The GTT Selector table is corrupt or cannot be found.

The GTT Set table is corrupt or cannot be found.

The GTA table is corrupt or cannot be found.

The GTT DBMM table is corrupt or cannot be found.

A severe system fault has occurred, and the command was rejected.

The Site ID table is corrupt or cannot be found.

The SS-APPL table is corrupt or cannot be found.

The Route table is corrupt or cannot be found.

The MRN table is corrupt or cannot be found.

The MAP table is corrupt or cannot be found.

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

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

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

The mrnset parameter can only be specified when the Flexible GTT Load-Sharing feature is enabled.

If the ri=gt parameter is specified, then the mrnset parameter must 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 Flexible GTT Load Sharing feature must be enabled before the mapset parameter can be specified.

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

The specified MAP set must exist in the database.

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

The MAP table is corrupt or cannot be found.

The gta, cgpc/cgpca/cgpci/cgpcn/cgpcn24/cgpcn16, opc/opca/opci/opcn/opcn24/opcn16, cgssn, cdssn, opcode/acn/pkgtype, opcode/family/pkgtype, dpc/dpca/dpci/dpcn/dpcn24/dpcn16, or saddr parameter must be specified.

The cdselid, cgselid, and optsn parameters cannot be specified together in the command. If the GTT set has a set type of cdgta, cdssn, or opcode, then the opcsn parameter can be specified with one of the above parameters.

If the cgssn parameter is specified, then the optsn and cgselid parameters cannot be specified.

The cgpc/cgpca/cgpci/cgpcn/cgpcn24/cgpcn16, opc/opca/opci/opcn/opcn24/opcn16 and dpc/dpca/dpci/dpcn/dpcn24/dpcn16 parameters must have a valid value within the range for each subfield.

The value specified for the ecgssn or ecdssn parameter must be greater than the value specified for the cgssn or cdssn parameter.

The OBSR feature must be enabled before the opcsn, optsn, cgpc/cgpca/cgpci/cgpcn/cgpcn24/cgpcn16, opc/opca/opci/opcn/opcn24/opcn16, or (e)cgssn parameters can be specified.

If the GTT set specified by the gttsn parameter (GTTSN set) has a set type of cdgta (see the ent-gttset command), then the optsn parameter cannot specify a GTT set (OPTSN set) with a set type of cgssn.

If the GTTSN set has a set type of cdgta, then the OPTSN set must have a set type of cggta or cgpc.

The FLOBR feature must be turned on before a GTTSN set with a set type of cgpc, cggta, or opc can be specified with an OPTSN with a set type other than cgssn.

If the FLOBR feature is turned on, and the GTTSN set has a set type of cdgta or cdssn, then the OPTSN set cannot have a set type of opc.

If the TOBR feature is turned on, and the GTTSN set has a set type of opcode, then the OPTSN set cannot have a set type of opc.

If the GTTSN set has a set type of MBR (imei/imsi/vlrnb/msisdn/smrpda/smrpoa), then the OPTSN set type cannot have the same set type as GTTSN.

If the OPTSN set has a set type of MBR (imei/imsi/vlrnb/msisdn/smrpda/smrpoa), then the GTTSET must have a set type of MBR (imei/imsi/vlrnb/msisdn/smrpda/smrpoa) or opcode.

The GTA must be specified if the GTTSN set type has a value of cdgta or cggta. The GTA cannot be specified for other set types.

If the GTTSN set type has a value of cgpc, the cgpc/cgpca/cgpci/cgpcn/cgpcn24/cgpcn16 parameter must be specified. This parameter cannot be specified for other set types.

The opc/opca/opci/opcn/opcn24/opcn16 parameter must be specified if the GTTSN set type has a value of opc. These parameters cannot be specified for other set types.

If the GTTSN set type has a value of cgssn, the cgssn parameter must be specified. The cgssn parameter cannot be specified for GTTSN of other types.

The range specified by the cdssn/ecdssn and cgssn/ecgssn parameters cannot overlap a currently existing range for the specified GTT set.

The GTT set name specified by the opcsn parameter must have a set type of opc (see the ent-gttset command).

The OPC subsystem number set domain must be the same as the GTTSN set domain. If the GTT subsystem number set domain is ANSI, then the OPC subsystem number set domain must be ANSI. If the GTT subsystem number set domain is ITU, then the OPC subsystem number set domain must be ITU.

The translation entry specified by the cgpc, opcode, opc, or dpc parameters cannot already exist.

The cgpc, cgssn, gta, opc, cdssn, opcode, dpc, and saddr parameters cannot be specified together in the command.

If the cgssn and cdssn parameters are both specified in the same command (in any order), then only the value for the last of the two parameters specified is used during processing.

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

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

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

The Loopset table is corrupt or cannot be found.

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 FLOBR feature must be turned on before the fallback, cdselid, cdssn, ecdssn, or dpc parameter can be specified.

The FLOBR feature must be turned on before the gttsn parameter can specify a GTT set with a set type other than cdgta (see the ent-gttset command) in the same command with the cgselid parameter.

The OBSR feature must be enabled or the FLOBR feature must be turned on before the cgselid parameter can be specified.

The ANSI/ITU SCCP Conversion feature must be enabled before the GTT set specified by the optsn parameter can have a different domain than the GTT set specified by the gttsn parameter.

A TOBR quantity feature must be turned on before the opcode, pkgtype, acn, family, saddr, eaddr, or defmapvr parameter can be specified.

The opcode, pkgtype, and family parameters must be specified together for ANSI TCAP translations. The opcode, pkgtype, and acn parameters must be specified together for ITU TCAP translations.

If the opcodetag is specified by opcodetag parameter, then the pkgtype, opcode and acn must be specified.

E3701 Cmd Rej: PkgType, Opcode and ACN must be specified.

If the GTT set specified by the gttsn parameter has a set type of opcode (see the ent-gttset command), then the opcode/acn/pkgtype or opcode/family/pkgtype parameter must be specified. These parameters cannot be specified for GTT sets of any other set types.

If the GTT set specified by the gttsn parameter has a set type of cdssn (see the ent-gttset command), then the cdssn parameter must be specified. This parameter cannot be specified for GTT sets with other set types.

The maximum number of OPCODE translation entries cannot exceed the value that is set by the associated TOBR quantity feature.

The GTT set specified by the gttsn parameter must have a set type of cdgta, opcode, or cdssn (see the ent-gttset command) before the opcsn parameter can be specified.

The same value cannot be specified for the gttsn and optsn parameters.

The ANSI/ITU SCCP conversion feature must be enabled and the FLOBR feature must be turned on before the cgcnvsn parameter can be specified.

The GTT set specified by the gttsn parameter must have a set type of cdgta or cggta (see the ent-gttset command) before the cgcnvsn parameter can be specified.

If the cgssn parameter is specified, then the ecdssn parameter cannot be specified. If the cdssn parameter is specified, then the ecgssn parameter cannot be specified.

The GTT set specified by the gttsn parameter cannot be the same as the GTT set specified by the cgcnvsn parameter.

If the family parameter is specified, then a value of ansiuni, qwp, qwop, resp, cwp, cwop, ansiabort, or any must be specified for the pkgtype parameter.

If the acn parameter is specified, then a value of bgn, ituabort, ituuni, any, end, or cnt must be specified for the pkgtype parameter.

The GTT set specified by the optsn, opcsn, and cgcnvsn parameters must match an existing GTT set.

If the pkgtype=ituabort parameter is specified, then a value of none must be specified for the acn, opcode and opcodetag parameters.

If the pkgtype=ansiabort parameter is specified, then a value of none must be specified for the family and opcode parameters.

E5144 Cmd Rej: PKGTYPE abort requires ACN/FAMILY/OPCODE/OPTAG value none.

If the family and opcode parameters are specified in the command, then either both parameters must have a value of none or neither parameter can have a value of none.

The OBSR feature must be enabled or the FLOBR feature must be turned on before the optsn parameter can be specified.

The specified GTT Action Set must already exist in the database.

Failure while reading GTT Action Set Table.

The actsn=none parameter cannot be specified.

The dpc/dpca/dpci/dpcn/dpcn24/dpcn16 parameter must be specified if the GTTSN set type is dpc (see the ent-gttset command). If the GTT set has a set type other than dpc, then the dpc/dpca/dpci/dpcn/dpcn24/dpcn16 parameter cannot be specified.

If the xlat=none parameter is specified, then the ri, pc/pca/pci/pcn/pcn24/pcn16, force, ssn and ccgt parameters cannot be specified.

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.

If the FGTTLS feature is enabled, and the xlat=none parameter is specified, then the mrnset or mapset parameter must be specified.

The specified GTT set must have a set type of opcode (see the ent-gttset command) before the opcode/acn/pkgtype or opcode/family/pkgtype parameters can be specified. The specified GTT set must have a set type of cdssn, cgssn, cdgta/cgta, opc, or cgpc before the cdssn, cgssn, gta, opc, or cgpc parameter, respectively, can be specified.

The acn and family parameters cannot be specified together in the command.

If the opc or dpc parameter is specified, then the (e)gta, (e)cgssn, (e)cdssn, eaddr, and opcode parameters cannot be specified.

The J7 Support feature must be enabled before the cgpcn16/opcn16/dpcn16 parameters can be specified.

The J7 Support feature must not be enabled before the cgpcn24/opcn24/dpcn24/cgpca/opca/dpca parameters can be specified.

The saddr parameter must be specified if the GTT set specified by the gttsn parameter is of MBR type (IMEI/IMSI/MSISDN/VLRNB/SMRPOA/SMRPDA).

If the GTT set specified by the optsn parameter is of MBR type (IMEI/IMSI/MSISDN/VLRNB/SMRPOA/SMRPDA) in the GTA command for the ITU opcode entry, then the package type specified via the pkgtype parameter must be ITU BGN/CNT/END.

The defmapvr parameter can be specified in the GTA command for the ITU opcode entry if the GTT set specified by the optsn parameter is of MBR type (IMEI/IMSI/MSISDN/VLRNB/SMRPOA/SMRPDA).

The PRIO parameter can be specified with OPCODE GTT set types only.

If the GTA/EGTA parameter is specified, then the EADDR parameter cannot be specified.

If the SADDR parameter is specified, then the ECGSSN/ECDSSN parameter cannot be specified.

If the OPCODE parameter is specified, then the EADDR/EGTA/ ECGSSN/ECDSSN parameter cannot be specified.

If the CGPC parameter is specified, then the EADDR/EGTA/ECGSSN/ECDSSN parameter cannot be specified.

If the ECGSSN/ECDSSN parameter is specified, then the EADDR/EGTA parameter cannot be specified.

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

Notes

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 feature and the Intermediate GTT Load Sharing feature are on, multiple relationships can be defined among set of destination point codes in the MRN table, which already 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 create 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 PC relative cost, to route the MSU in the most cost effective way.

When the Flexible GTT Load Sharing feature is enabled, multiple relationships can be defined among a 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 Origin-based SCCP Routing feature is turned on, the CdPA GTA, CgPA GTA, CgPA PC, CgPA SSN, and OPC entries can be provisioned. When provisioning, the following rules apply:

The Advanced CdPA GTA entry can associate with CgPA GTA set, CgPA PC set, or SELID and OPC set.
The CgPA GTA, CgPA PC, or OPC entry can associate with the CgPA SSN set.
The CgPA SSN entry cannot associate with any other GTT set.
The Advanced CdPA GTA entry may contain SELID, which is (together with the CgPA information) derived from incoming MSU to search the Selector table again for the CgPA GTA or CgPA PC Set.

When the Origin-based SCCP Routing feature is enabled, the GTA and EGTA can be used for the CgPA translation as well as the CdPA GTA translation.

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

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 FLOBR GTT hierarchy is provisioned on a linkset, then translations do not have to be searched in a predetermined manner. If a translation points to another GTTSET/SELID, then database searches continue. The number of searches is limited by the following conditions:

The same GTT set name cannot be referred more than once.
Up to 7 database searches can be performed.
For MBR, the same GTT set type (IMEI/IMSI/MSISDN/VLRNB/SMRPOA/SMRPDA) cannot be referred more than once.

If the FLOBR feature is turned on, then any translation can point to any GTTSETs other than that specified by the GTTSN. The CdPA GTA and CdPA SSN translations can also point to an OPCSN. For CdPA GTA and CdPA SSN translations, if an OPTSN GTTSET/SELID is provisioned apart from an OPCSN, then the OPTSN GTTSET/SELID takes precedence over the OPCSN.

The MBR GTT set type translation entries (IMEI/IMSI/MSISDN/VLRNB/SMRPOA/SMRPDA) can be configured only when the TOBR feature is turned on. The GTT sets of the types mentioned above are allowed to be provisioned ONLY in GTA entries from a GTT set of the type OPCODE or one of the other GTT set types supported by this feature (SS7 Firewall).

Translations, supporting ANSI or ITU opcodes, associated with the TOBR feature:

ANSI Opcode—ANSI opcode specifier, ANSI TCAP Package type, and Family
ITU Opcode—ITU opcode, ITU TCAP Package Type, Opcodetag and ACN

Translations associated with the FLOBR feature:

CdPA SSN Translations—Can be configured with routing and flexible routing data. The provisioning rules for CdPA SSN translations are the same as CgPA SSN translations in OBSR.
DPC Translations—The provisioning rules for DPC translations are the same as OPC translations except that the OPCSN parameter cannot be configured for DPC translations.

Output

ent-gta:gttsn=opcdis3:xlat=dpc:ri=gt:pc=1-1-1:opca=002-001-001:actsn=actdisc1:ppmeasreqd=yes


    tekelecstp 10-02-24 12:09:18 EST  EAGLE 42.0.0
    ENT-GTA: MASP A - COMPLTD 
;

ent-gta:gttsn=imsi1:xlat=dpc:ri=gt:pc=1-1-1:saddr=1234567890:eaddr=2234567890


    tekelecstp 15-05-24 12:09:18 EST  EAGLE 46.3.0
    ENT-GTA: MASP A - COMPLTD 
;


				ent-gta:gttsn=setopcode:opcode=*:pkgtype=bgn:acn=*:xlat=dpc:ri=gt:pci=1-1-1:prio=1024:
				opcodetag=global

 tekelecstp 16-11-07 14:13:13 MST  EAGLE 46.5.0.0.0-70.5.0
    ENT-GTA: MASP A - COMPLTD
;


				ent-gta:gttsn=imsi3:xlat=dpc:ri=gt:pc=1-1-1:saddr=1234567890:transmeasrqd=yes

tekelecstp 17-05-11 15:09:18 EST  EAGLE 46.6.0
    ENT-GTA: MASP A - COMPLTD 
;

Related Topics