chg-gta

4.67 chg-gta

Use this command to change the global title address information (GTA) for applicable global title selectors required to specify a global title entry.

This command changes the routing objects for messages requiring global title translations. The specified point code, subsystem number, MRN set ID, and routing indicator overwrite the existing data values.

When the Intermediate GTT Load Sharing feature and the Flexible GTT Load Sharing feature are both 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 ID and the post-translation PC create a key that is used to perform a lookup in the MRN table. This lookup results in a set of alternate PCs from which a PC is selected, based on relative cost, to route the MSU in most cost-effective way.

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. A GTT set is an entity to which global title addresses and selectors are assigned.

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

acn (optional)

Application context name. The ITU TCAP ACNfield in the incoming MSU.

Range:

0 - 255, *, none

The ACN supports up to 7 subfields separated by a 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

Default:

No change to the current value

actsn (optional)

GTT Action Set Name.

Range:

ayyyyyyyy

1 leading alphabetic character followed by up to 8 alphanumeric characters

none -Action set name does not point to any action set

ccgt (optional)

Cancel called global title indicator.

Range:

yes
no

Default:

No change to the current value

cdselid (optional)

CdPA selector ID.

Range:: 0 - 65534, none
none —deletes the current value of the CDSELID field
Default:: No change to the current value

cdssn (optional)

Starting CdPA subsystem number.

Range:: 0 - 255

cgcnvsn (optional)

Calling party conversion set name.

Range:: ayyyyyyyy
1 leading alphabetic character and up to 8 following alphanumeric characters.
none —deletes the current value of the parameter

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

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

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

cgselid (optional)

Calling party selector ID.

Range:: 0 - 65534, none
none —deletes the current value of the CGSELID field
Default:: No change to the current value

cgssn (optional)

The subsystem number of the starting CgPA.

Range:: 0 - 255

defmapvr (optional)

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

Range:: v1; v2; v3
Default: No change to the current value

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 dash (-).; The asterisk (*) value is not valid for the n 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--225.; 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

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

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

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)

Subsystem number of the ending called party.

Range:: 0 - 255

ecgssn (optional)

Subsystem number of the ending CgPA.

Range:: 0 - 255

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:

Same as the specified gta value

fallback (optional)

Fallback option. The action that is taken if the last translation doesn't match when performing GTT using a FLOBR-specific GTT mode.

Range:

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

Default:

No change to the current value

family (optional)

The ANSI TCAP FAMILY 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

System Default:

none

force (optional)

Check mated application override.

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 leading alphabetic character followed by up to 8 alphanumeric characters

none —removes the association between the translation and the GTMODID

Default:

No change to the current value

loopset (optional)

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

Range:

ayyyyyyy

One leading alphabetic character and up to 7 following 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 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.

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 national 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

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

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

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

opcode (optional)

The TCAP opcode field in the incoming MSU.

Range: 0 - 255, *, none: * —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.

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

none —deletes the current value of the parameter

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.

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 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, 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

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

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

pkgtype (optional)

The ANSI and ITU TCAP package type.

Range:

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

ppmeasreqd (optional)

Per Path Measurement required. This parameter specifies whether to perform per path measurements.

Range:

yes: perform Per Path Measurements
no: do not perform Per Path Measurements

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
ssn

Default:

No change to current value.

saddr (optional)

Start Address (Similar to GTA). 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.

Default

Same as the specified SADDR value

split (optional)

Split or change an existing GTA range.

Range:

yes: Splits the existing GTA range.
no: Changes the existing GTA range.

Default:

yes

ssn (optional)

Subsystem number.

Range:

002 - 255

Default:

If the xlat parameter is not changed to dpcngt —No change to current value

If the xlat parameter is changed to dpcngt —The ssn parameter value is removed.

testmode (optional)

This parameter invokes a Test Tool that is used to debug the FLOBR/TOBR rules.

Caution:

If the testmode=on parameter is specified, then the rule is used only by test messages and 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)

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

xlat (optional)

Translate indicator. This parameter is used to specify translation actions and routing actions.

Range:

dpc
dpcngt
dpcssn
none

Default:

No change to the current value

Example

chg-gta:gttsn=lidb:gta=9195554321:xlat=dpcssn:ri=ssn:pc=001-255-252:ssn=254

chg-gta:gttsn=test:gta=100000:egta=199999:pca=1-1-1:xlat=dpcngt:ri=gt:gtmodid=set1

chg-gta:gttsn=setnat003:gta=987658321198765432102:pcn=s-129

chg-gta:gttsn=itui1:gta=987658321198765432112:pci=s-1-210-1

chg-gta:gttsn=setnat003:gta=987658321198765432122:pcn=s-128-aa

chg-gta:gttsn=setmap:gta=2345678911:egta=3456789022:ri=ssn:pc=2-2-2:ssn=221:mapset=dflt

chg-gta:gttsn=setopcode:pci=3-3-2:opcode=*:pkgtype=bgn:acn=*:prio=1024

In this example, the database contains a GTA range [5556000-5558000], but no part of the GTA range [5558001-5559000] exists. The command deletes the GTA range [5556000-5558000] from the database and adds two new GTA ranges [5556000-5556799] and [5556800-5559000].

chg-gta:gttsn=tst1:gta=5556800:egta=5559000:split=yes

This example deletes the GTA range [5556000-5556799] from the database and adds a new GTA range [5556200-5556500] to the database. All the parameters for the GTA range [5556200-5556500] have the same values as that of the deleted [5556000-5556799] GTA range, except the pc parameter that is has a value of 1.

chg-gta:gttsn=tst1:gta=5556200:egta=5556500:pc=1-1-2:split=no

This example deletes the GTA range [5556200-5556500] from the database and adds two new GTA ranges [5556200-5556400] and [5556401-5556500] to the database.

chg-gta:gttsn=tst1:gta=5556401:egta=5556500

This example specifies the default MRN set.

chg-gta:gttsn=setmrn:gta=1234567880:pc=1-1-2:mrnset=dflt

This example removes the MRN set ID.

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

chg-gta:gttsn=setcdgta:gta=123456789012345678901:egta=223456789012345678901: optsn=cggta1:opcsn=opc1

chg-gta:gttsn=setcdgta:gta=123456789012345678901:egta=223456789012345678901: cgselid=1024:opcsn=opc1

chg-gta:gttsn=setcdgta:gta=123456789012345678901:egta=223456789012345678901: optsn=none

chg-gta:gttsn=setopc:opca=002-001-001:xlat=dpcssn:ri=ssn: pca=001-001-001:ssn=20:optsn=setcgssn

chg-gta:gttsn=setcgpc:cgpca=001-001-001:xlat=dpcssn:ri=ssn: pca=001-001-001:ssn=20:optsn=setcgssn

chg-gta:gttsn=setcgssn:cgssn=100:ecgssn=200:xlat=dpcssn:ri=ssn: pca=001-001-001:ssn=20

chg-gta:gttsn=set1:gta=2543:egta=2943:actsn=actdisc1:ppmeasreqd=yes

chg-gta:gttsn=set2:cgpc=1-2-*:actsn=actudts1

chg-gta:gttsn=set3:opcn=2543:actsn=actudts1

chg-gta:gttsn=set4:cgssn=25:ecgssn=29:actsn=actdup1:xlat=dpc:ri=gt:pc=1-1-1

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

chg-gta:gttsn=set1:gta=abcd:egta=abce

chg-gta:gttsn=setmap:gta=2345678901:egta=3456789012:ri=ssn:pc=1-1-3:ssn=225:mapset=2:loopset=raleigh1

This example specifies that calling party GT modification is required.

chg-gta:gttsn=setans004:cggtmod=yes:gta=981234

This example changes the GTA translations when the FLOBR feature is turned on.

chg-gta:gttsn=setcdgta:gta=1234567890:egta=2234567890: xlat=dpcssn:ri=ssn:pca=001-001-001:ssn=100:fallback=no:testmode=on

This example changes the GTA translations when the OBSR feature is enabled and the FLOBR feature is turned on.

chg-gta:gttsn=setcdgta:gta=1234567890:egta=2234567890: xlat=dpcssn:ri=ssn:pc=2-2-2:ssn=100:fallback=yes:optsn=setcggta:testmode=on

This example changes the GTA translations when the FLOBR feature is turned on.

chg-gta:gttsn=setcdssn:cdssn=15:ecdssn=29:xlat=dpc:pc=1-1-1:ri=gt

This example changes the GTA translations when the TOBR and OBSR features are turned on.

chg-gta:gttsn=setopcode:pkgtype=qwop:opcode=none:family=*:xlat=dpc:ri=gt: pc=2-2-2:opcsn=setopc:optsn=setcdgta

chg-gta:gttsn=setopcode:pkgtype=bgn:opcode=none:acn=1-22-123-43-54-65-76:opcodetag=global: xlat=dpc:ri=gt:pc=2-2-2:opcsn=setopc:optsn=setcdgta

chg-gta:gttsn=setopcode:pkgtype=bgn:opcode=none:family=*:xlat=dpc:ri=gt: pc=2-2-2:optsn=imsi1:defmapvr=v3

chg-gta:saddr=1234567890:eaddr=2234567890:gttsn=setmsisdn

This example changes the GTA translation for a DPC GTT set when the FLOBR feature is turned on.

chg-gta:gttsn=setdpc:dpc=1-1-1:optsn=setc1

chg-gta:gttsn=setcdgta:gta=78901234:xlat=dpc:gtmodid=none

chg-gta:gttsn=setcdgta:gta=123456789012345678901:xlat=none:gtmodid=gttsn1

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

chg-gta:gttsn=setcdgta:gta=123456:xlat=none:mapset=1:mrnset=2

Example for 16 bit PC and CGPCACTION param.

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

cgpcaction=remove

chg-gta:gttsn=imei1:saddr=98765432112:xlat=dpc:ri=gt:pci=1-210-1:transmeasrqd=yes

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 point code that is of a different domain than the GTT set specified by the gttsn parameter can be specified.

At least one optional parameter must be specified.

The gttsn=none parameter cannot be specified.

The point code specified for the pc parameter must be a full point code.

The values of the gta/saddr and egta/eaddr parameters must be the same length.

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.

The length of the specified gta/saddr parameter must match the number of digits provisioned for the specified GTT set when the VGTT feature is turned off. 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 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, an overlap with another range cannot be specified. 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 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 CHG-GTA: MASP A - Command Aborted

If a new or existing xlat=dpcngt parameter is specified, a new or existing ri=gt parameter must be specified.

If the ssn parameter is specified, a new or existing xlat=dpcssn parameter must be specified.

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

If the pc/pca/pci /pcn/pcn24/pcn16 parameter is specified, and the point code is the STP true point code, then the value of the new or existing xlat parameter must be dpcssn, and the new or existing value of the ri parameter must be ssn.

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

If the pc/pca/pci/pcn/pcn24/pcn16 parameter is specified, then it 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) unless the point code is the STP’s true point code.

If new or existing ri=ssn and xlat=dpc parameters are specified, and the pc/pca/pci/pcn/pcn24/pcn16 parameter is not specified, then the existing PC must exist in the Remote Point Code/MAP table, unless the force=yes parameter is specified.

If new or existing ri=ssn, xlat=dpc, and pc/pca/pci/pcn/pcn24/pcn16 parameters are specified, the new point code must exist in the Remote Point Code/MAP table, unless the force=yes parameter is specified.

If a new or existing ccgt=yes parameter is specified, a new or existing ri=ssn parameter must be specified.

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

If new or existing ri=ssn and xlat=dpcssn parameters are specified, a new or existing xlat=dpcssn parameter must exist in the Remote Point Code/MAP table, unless the force=yes parameter is specified.

The GTT table cannot be full.

If the ri=gt parameter is specified, the mrnset parameter must be specified. If the ri=gt parameter is not 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.

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

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

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

The SEAS command can operate only on the default MRN set or the default MAP set.

The MRN table is corrupt or cannot be found.

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.

Note: The mapset parameter can only be specified if the Flexible GTT Load Sharing feature is enabled.

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

The specified MAP set must exist in the database.

The specified or previously provisioned PC/SSN 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.

If the xlat=dpc parameter is specified, and the value of the force parameter is not yes, then the point code and MAP set must exist in the MAP table.

The MAP table is corrupt or cannot be found.

The specified GTA/SADDR must occur within an existing GTA range in the specified GTT Set.

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 FLOBR feature must be turned on before the cgssn, opcsn, optsn, and cgselid parameters can be specified in the same command.

The pc/pca/pci/pcn/pcn24/pcn16, cgpc/cgpca/cgpci/cgpcn/cgpcn24/cgpcn16, opc/opca/opci/opcn/opcn24/opcn16, and dpc/dpca/dpci/dpcn/dpcn24/dpcn16 parameters must have values within the valid range for each subfield.

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

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 OBSR feature must be enabled before the opcsn, 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. 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 cdselid, cgselid, and optsn parameters cannot be specified together in the command. If the GTTSN has a set type of cdgta, cdssn, or opcode (see the ent-gttset command) then the opcsn parameter can be specified if one of the other exclusive parameters is specified.

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

The cgpc/cgpca/cgpci/cgpcn/cgpcn24/cgpcn16 parameter must be specified if the GTTSN set type has a value of cgpc. The cgpc/cgpca/cgpci/cgpcn/cgpcn24/cgpcn16 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. The opc/opca/opci/opcn/opcn24/opcn16 cannot be specified for other set types.

The cgssn parameter must be specified if the GTTSN set type is cgssn. The cgssn parameter cannot be specified for other set types.

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

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

If the specified GTT set is an ANSI set, the cgpc/cgpca, opc/opca, and dpc/dpca parameters must be valid ANSI point codes. If the specified GTT set is an ITU set, the cgpci/cgpcn/cgpcn24/cgpcn16, opci/opcn/opcn24/opcn16, and dpci/dpcn/dpcn24/dpcn16 parameters must be valid ITU point codes.

The set domain of the opcsn parameter must be the same as the set domain of the gttsn parameter. For example, if the set domain of the gttsn parameter is ANSI, then the set domain of the opcsn parameter must be ANSI. If the set domain of the gttsn parameter is ITU, then the set domain of the opcsn parameter must be ITU.

The range specified by the cgssn/ecgssn and cdssn/ecdssn parameters must exist for the specified GTT set in the STP active data base. An exact match is not required.

The translation entry associated with the specified point code (dpc/dpca/dpci/dpcn/dpcn24/dpcn16, pc/pca/pci/pcn/pcn24/pcn16, or opc/opca/opci/opcn/opcn24/opcn16) or opcode must already exist.

The cgpc, cgssn, gta, opc, cdssn, opcode and saddr parameters cannot be specified in the same 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 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 Loopset table is corrupt or cannot be found.

The value specified for the egta/eaddr parameter must be greater than value specified for the gta/saddr parameter.

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, (e)cdssn, 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 same value cannot be specified for the gttsn and optsn parameters.

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 opcode 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 parameters must be specified. These parameters cannot be specified if the GTT set has of any other set type.

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 if the GTT set has any other set type.

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

The value specified for the gttsn parameter must match the name of an existing GTT Set.

A value of none must be specified for the optsn, cgselid, or cdselid parameter before the parameter can be changed to another value.

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.

The value specified for the gttsn parameter cannot be the same as the value specified for the cgcnvsn parameter.

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

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

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

The GTT set name specified in the optsn, opcsn, or cgcnvsn parameters must match an existing GTT set name.

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

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

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

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

The value specified for 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 values specified for the gta and egta parameters must be an exact match to the GTA values referred in GTT Action Path table (see the ent-gttapath command).

If the FGTTLS feature is enabled, and the xlat=none parameter is specified, then the mrnset or mapset parameter must 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 acn and family parameters cannot be specified together in the command.

If the cgssn parameter is specified, then the (e)cdssn parameter cannot be specified. If the cdssn parameter is specified, then the (e)cgssn parameter cannot be specified.

If the opc or dpc parameter is specified, then the (e)gta, (e)cgssn, (e)cdssn, 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 an 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 an ITU opcode entry if the GTT set specified by the optsn parameter is of MBR type (IMEI/IMSI/MSISDN/VLRNB/SMRPOA/SMRPDA).

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

PRIO value should lie between 1-1024 (both inclusive)

If the saddr parameter is specified, then the ecgssn/ecdssn parameters cannot be specified.

Notes

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

If a GTT is being deleted or changed and the point code (DPC or RTE) is not found in the route table (unless the point code is the STP’s true point code), then the following message is displayed in the terminal scroll area:


NOTICE: No DPC and/or RTE found for GTT being deleted or changed.

The above situation may occur if the reference count rules were not enforced and a DPC and/or RTE were deleted while being referenced by a GTT entry. This indicates a software error; contact My Oracle Support (MOS).

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 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 mrnset parameter and the post-translation PC create a key that is used to perform a lookup in the MRN table. This lookup results in a set of alternate PCs, from which a PC is selected, based on relative cost, to route the MSU in most cost-effective way.

When the Flexible GTT Load Sharing feature is turned on, multiple relationships can be defined among a set of PC/SSN pairs 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 enabled, the CdPA GTA entry can be provisioned in addition to the CgPA GTA, CgPA PC, CgPA SSN, and OPC entries. When provisioning, the Advanced CdPA GTA entry can associate with the CgPA GTA set or the CgPA PC set, the SELID and/or OPC set; the CgPA GTA, CgPA PC, or OPC can associate with the CgPA SSN set; the CgPA SSN cannot associate with any other GTT set. The Advanced CdPA GTA entry may contain the selector ID along with CgPA information present in the MSU to search the Selector table again for the CgPA GTA or CgPA PC Set.

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 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/egta parameters retain the original xlat, ri, pc and ssn parameters. A new range is created that is bounded by the gta/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 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 settype (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 types translation entries (IMEI/IMSI/MSISDN/VLRNB/SMRPOA/SMRPDA) can be configured only when the TOBR feature is turned ON. The GTTSets of the types mentioned above are allowed to be provisioned ONLY in GTA entries from a GTTSet of the type OPCODE or one of the other GTT Set types supported by this feature (SS7 Firewall).

Translations 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 OPCSN parameter cannot be configured for DPC translations.

Output


		  chg-gta:gttsn=set2:xlat=dpcssn:ri=ssn:pc=3-3-3:ssn=10:cgpc=1-2-*:actsn=actudts1:ppmeasreqd=yes


    tekelecstp 10-02-15 17:29:06 EST  EAGLE 42.0.0
    CHG-GTA: MASP A - COMPLTD 
;


		  chg-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 
;


		  chg-gta:gttsn=setopcode:pci=3-3-2:opcode=*:pkgtype=bgn:acn=*:
		  prio=1024

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

chg-gta:gttsn=imei1:saddr=98765432112:xlat=dpc:ri=gt:pci=1-210-1:transmeasrqd=yes

tekelecstp 17-05-11 15:20:06 EST  EAGLE 46.6.0
    CHG-GTA: MASP A - COMPLTD 
;

Related Topics