Oracle® Communications EAGLE Database Administration - GWS User's Guide Release 46.6 E93314 Revision 1 |
|
![]() Previous |
![]() Next |
This procedure is used to add a gateway screening stop
action set to the database or change an existing gateway screening stop action
set using the
chg-gws-actset
command.
The gateway screening stop action sets define the
actions that are performed on the
MSU when the gateway
screening process has stopped. These gateway screening stop action sets replace
the
copy
and
redirect
parameters that have been
used with the gateway screening commands when the gateway screening process
stops.
The database can contain a maximum of 16 gateway screening stop action sets, with each set containing a maximum of 10 gateway screening stop actions. These are the current gateway screening stop actions.
tinp
,
tif
,
tif2
, or
tif3
stop action is already assigned
to a gateway screening stop action set, or if any of these features are
enabled.
Note:
The MTP Msgs for SCCP Apps feature (part number 893017401) takes precedence over the MTP Routed GWS Stop Action feature. If the MTP Msgs for SCCP Apps feature is enabled and turned on, all MTP routed SCCP messages are forwarded to the service modules for further processing whether or not the SCCP gateway screening stop action is specified.Caution:
When Gateway Screening is in the screen test mode, as defined by the linkset parametersgwsa=off
and
gwsm=on
, any action in the gateway
screening stop action sets created in this procedure will be performed.
The
chg-gws-actset
command uses these
parameters.
:actid
– The
ID number of the gateway
screening stop action set. The value of this parameter is from 4 to 16.
:actname
– The name of
the gateway screening stop action set consisting of 1 alphabetic character
followed by up to 5 alphanumeric characters.
:force
– The
force=yes
parameter must be specified
when changing the gateway screening stop actions of an existing gateway
screening stop action set.
:all=none
– sets the
value of each gateway screening stop action in the gateway screening stop
action set to
none
. Refer to the
procedure
Removing Gateway Screening Stop Action Sets
for information about using this parameter.
:act1
to
:act10
– The ten gateway screening
stop actions for each gateway screening stop action set. Gateway screening stop
action 1 (act1
) is the first stop action to be
performed and gateway screening stop action 10 (act10
) is the last stop action to be performed on the
MSU.
The first three gateway screening stop action sets
(actid=1
,
actid=2
, and
actid=3
) are already defined with the
existing gateway screening stop actions shown in
Table 2-10.
Table 2-10 Gateway Screening Stop Action Definitions If the CNCF Feature Is Off
Gateway Screening Stop Action ID | Gateway Screening Stop Action Set Name | Stop Action 1 | Stop Action 2 | Action Performed by the EAGLE |
---|---|---|---|---|
1 |
copy |
copy |
— |
copy the MSU for the STPLAN feature |
2 |
rdct |
rdct |
— |
redirect the MSU for the DTA feature |
3 |
cr |
copy |
rdct |
copy the MSU for the STPLAN feature and redirect the MSU for the DTA feature |
The word
none
cannot be used for the
actname
parameter.
The
force=yes
parameter must be specified
when changing an existing gateway screening stop action set.
If the
copy
gateway screening action is
specified with the
chg-gws-actset
command, it must be
specified with the
act1
parameter.
A specific gateway screening stop action can only be
specified once in a specific gateway screening stop action set. For example,
the
chg-gws-actset
command cannot be
executed if the
copy
gateway screening stop action is
specified for gateway screening stop action parameters
act1
and
act2
as shown in this command example.
chg-gws-actset:actid=4:act1=copy:act2=copy
The value of the
actname
parameter must be unique. The
value of this parameter is used by the
actname
parameter in the gateway
screening commands and is shown in the
NSR/ACT
field of the outputs of the
retrieve gateway screening commands to define the action that is performed on
the
MSU that passes gateway
screening.
When a gateway screening stop action set is being
entered in to the database for the first time, the name of the gateway
screening stop action set (actname
) must be
added to the database before any gateway screening stop actions are assigned to
the gateway screening stop action set.
Table 2-11
shows the combinations of parameter values that can be specified for
act1
,
act2
, and
act3
parameters for gateway screening
stop action sets 4 through 16.
Table 2-11 Gateway Screening Stop Action Set Parameter Combinations
ACT1 | ACT2 | ACT3 |
---|---|---|
cncf | ||
copy | cncf | |
copy | cncf | rdct |
cncf | rdct | |
tinp | ||
copy | tinp | |
tif | ||
copy | tif | |
copy | cncf | tif |
cncf | tif | |
tif2 | ||
copy | tif2 | |
copy | cncf | tif2 |
cncf | tif2 | |
tif3 | ||
copy | tif3 | |
copy | cncf | tif3 |
cncf | tif3 | |
sccp | ||
copy | sccp | |
A blank entry in this table means that the ACT2 or ACT3 parameter has no value. The cncf stop action can be specified only if the CNCF feature is turned on. The tinp stop action can be specified only if the tinp stop action is assigned to a stop action set. The tif, tif2, or tif3 stop actions can be specified only if
one or more of these features are enabled.
The
|
Figure 2-12 Configuring Gateway Screening Stop Action Sets
Sheet 1 of 4
Sheet 2 of 4
Sheet 3 of 4
Sheet 4 of 4