chg-gsms-opcode

Use this command to change the attributes of the GSM (Global System for Mobile Telecommunication) MAP (mobile application part) screening operation codes. The command allows you to change the default screening action and the operation-code name for a specific operation code.

Parameters

Note:

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

opname (mandatory)

Operation code name. The user-defined name for the operation code.

Range:: ayyyyyyy
1 alphabetic character followed by up to 7 alphanumeric characters

force (optional)

Check Mated Application Override. This parameter is used to complete command execution if the npc/npca/npci/npcn/npcn24 and nssn 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:

no

ndfltact (optional)

New default screening action.

Range:

pass: Route the message as normal to the destination; a UIM will be issued. This is intended to be a test mode and is recommended when setting up GSM Map Screening during the initial phase to assure that no MSUs will be inadvertently thrown away.
discard: Do not route the MSU. The MSU is discarded (thrown away) and an appropriate UIM is issued.
atierr: Do not route the MSU. An ATI (Any Time Interrogation) reject message is generated to the originator. This value is valid only for ATI MAP operation codes.
route: Route the message as normal to the original destination node; no UIM will be generated. The original destination is the node to which normal GTT would be sent if no GSM MAP actions are taken.
forward: Route the original message to the forward node. The original message will not be sent to the original node. If, however, the forward node is not available for routing, the MSU is routed to the original node.
duplicate: Route the message as normal to the original destination and route a copy of the original message to the duplicate node. If the MSU fails to route to the duplicate node, a UIM is generated indicating the duplicate routing failure.
dupdisc: Route the original message to the duplicate node. The original message will not be sent to the original node. If, however, the duplicate node is not available for routing, the MSU is discarded.

Default:

No change to the current value

nmapset (optional)

New MAP set ID.

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

nopname (optional)

New operation code name.

Range:: ayyyyyyy
1 alphabetic character followed by up to 7 alphanumeric characters

Default:: No change to current value

npc (optional)

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

Synonym:

npca

Range:

000-255

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

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.

npc/npca/npci/npcn/npcn24 (optional): New point code. The npc/npca/npci /npcn/npcn24 and nssn parameters are used when the default screening action (dfltact) is forward, duplicate, or dupdisc (duplicate and discard). These parameters allow the user to change the defined node to which the input message will be routed.

npci (optional)

New ITU international 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.

npcn (optional)

New 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 (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

npcn24 (optional)

New 24-bit ITU national 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

nri (optional)

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

Range:

gt
ssn

nssn (optional)

New Subsystem Number.

Range:: 2 - 255
Default:: No change to the existing value

ntt (optional)

New translation type. This parameter specifies the value that the CdPA TT is set to as the result of Enhanced GSM Map Screening.

Range:: 0 - 255
Default:: No change to the existing value

Example

chg-gsms-opcode:opname=ati:ndfltact=atierr

chg-gsms-opcode:opname=ati:ndfltact=forward:npci=1-1-1:nssn=5:force=yes

chg-gsms-opcode:opname=xyz:npca=9-9-9:nssn=3

chg-gsms-opcode:opname=test2:npci=s-1-1-1

chg-gsms-opcode:opname=test2:ndfltact=dupdisc:npci=1-1-1:nssn=5:nmapset=8

chg-gsms-opcode:opname=ts4:ndfltact=forward:npc=1-1-2:nssn=5:nmapset=dflt

chg-gsms-opcode:opname=test:nri=ssn

chg-gsms-opcode:opname=test4:ntt=12

Dependencies

At least one optional parameter must be specified.

If the ndfltact parameter is specified, one of the following values must be specified: pass, discard, atierr, route, forward, duplicate, or dupdisc.

If the ndfltact parameter is specified and its value is forward, duplicate, or dupdisc, the npc/npca/npci /npcn/npcn24 and nssn parameters must be specified.

The word none cannot be specified as a value for the opname or nopname parameter.

If the npc/npca/npcinpcn/npcn24 and nssn parameters are specified with the ndfltact parameter, the ndflact parameter must have a value of forward, duplicate, or dupdisc.

The npc/npca/npci/npcn/npcn24 and nssn parameters must be specified before the force parameter can be specified.

The value specified for the opname parameter must already exist in the GSM Map Op-Code table.

The GSM Map Screening feature must be turned on before this command can be entered.

The EGMS feature must be enabled and turned on before the npc or npca parameters can be specified.

The ndfltact=atierr parameter cannot be specified unless the value of the operation code referenced by the opcode parameter is 71 . The atierr option is valid only for ATI MAP operation codes, and the opcode=71 parameter signifies an ATI MAP operation code.

The value specified for the npc/npca/npci/npcn /npcn24 parameter must be a full point code.

The GSM Map Op-Code table must be accessible.

The Route table must be accessible.

If the npc/npca/npci/npcn/npcn24 parameter and the nssn parameter are specified, and the force parameter is not specified as yes, the PC-SSN must be populated in the SCCP Application entity set (Remote Point Code / Mated Application Table).

If specified, the npc/npca/npci/npcn/npcn24 parameter value must exist as a destination in the Ordered Route entity set or reside in a cluster (ANSI only) that exists as a destination in the Ordered Route entity set (for global title routing).

If the opname parameter is specified, the value must be alphanumeric.

The opname parameter value and the nopname parameter value must be no more than 8 characters long.

The nmapset parameter must be specified if the value of the ndfltact parameter is forward, duplicate, or dupdisc.

If the ndfltact parameter is specified with the nmapset, nri, ntt, pc, or ssn parameter, then the ndfltact parameter must have a value of forward, duplicate, or dupdisc.

The nmapset parameter must be specified before the force parameter can be specified.

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

The specified new MAP set must exist.

If the nmapset=dflt parameter is not specified, or the nmapset=dflt parameter is specified, but the force=yes parameter is not specified, then the new PC and new SSN must exist in the new MAP set.

If the nmapset, nri, or ntt parameter is specified, and the ndfltact parameter is not specified, then the dfltact parameter must have a previously provisioned value of forward, duplicate, or dupdisc .

The MAP table must be accessible.

If the value of the ndfltact parameter is forward, duplicate, or dupdisc, then the value specified for the npc/npca/npci/npcn/npcn24 parameter cannot be associated with a proxy point code.

If the nri=ssn parameter is specified, then the ssn=none parameter cannot be specified.

If the Flexible GTT Load Sharing feature is enabled, and the new or previously provisioned subsystem number has a value of none, then the new or previously provisioned MAP set and point code combination must already exist in the MAP table.

If the Flexible GTT Load Sharing feature is not enabled, and the new or previously provisioned subsystem number has a value of none (the nssn=none parameter is specified in this command, or the ssn=none parameter was specified in the ent-gsms-opcode command), then the point code must already exist in the MAP table.

Notes

In this command, only ITU-international and ITU national point codes support the spare point code subtype prefix (s-).

Output

chg-gsms-opcode:opname=test4:ntt=12


    tekelecstp 08-08-20 19:13:01 EST  EAGLE 39.2.0
    CHG-GSM-OPCODE: MASP A - COMPLTD 
;

4.65 chg-gsms-opcode