Configuring TLNP Gateway Screening Stop Action Sets
This procedure is used to add a gateway screening stop
action set containing the TLNP gateway screening stop action to the database
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.
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. For this procedure only two gateway screening stop actions can be used.
- COPY – copy the MSU for the STPLAN feature
- TLNP – ISUP IAMs that pass gateway screening are
processed either by the ISUP NP with EPAP feature (if the ISUP NP with EPAP
feature is enabled and turned on) or by the Triggerless LNP feature (if the LNP
feature is enabled and the Triggerless LNP feature is turned on). The ISUP NP
with EPAP feature is discussed in more detail in
G-Port User's Guide. The Triggerless LNP
feature is discussed in more detail in
ELAP Administration and LNP Feature Activation
Guide.
The status of the ISUP NP with EPAP feature can be verified with the
rtrv-ctrl-feat
command. The ISUP NP with EPAP feature also requires that the G-Port feature is enabled and that Gateway Screening feature is turned on. The status of the G-Port feature can be verified with thertrv-ctrl-feat
command. The status of the Gateway Screening feature can be verified with thertrv-feat
command. Enabling the G-Port feature is discussed in more detail in G-Port User's Guide.Caution:
When Gateway Screening is in the screen test mode, as defined by the linkset parametersgwsa=off
andgwsm=on
, any action in the gateway screening stop action sets created in this procedure will be performed.
The
chg-gws-actset
command in this
procedure 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. The word
none
cannot be used for the
actname
parameter.
:force
– The
force=yes
parameter must be specified
when changing the gateway screening stop actions of an existing gateway
screening stop action set.
:act1
and
:act2
– Only two gateway screening
stop action sets can be defined with the TLNP gateway screening stop action:
- One set with only the TLNP gateway Screening stop
action (defined with the
act1=tlnp
parameter). - Another set with the COPY and TLNP gateway screening
stop action (defined by the
act1=copy
andact2=tlnp
parameters).
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 into 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.
The
tlnp
gateway screening stop action
cannot be specified with either the
cncf
(calling name conversion
facility) or
rdct
(redirect) gateway screening
actions in the same gateway screening action set.
Table 2-12 Sample TLNP Gateway Screening Stop Action Set Configuration
ACTID | ACTNAME | ACT1 | ACT2 | ACT3 |
---|---|---|---|---|
4 | TLNP | tlnp | — | — |
5 | CPNP | copy | tlnp | — |
Figure 2-20 Configure TLNP Gateway Screening Stop Action Sets - Sheet 1 of 7
Figure 2-21 Configure TLNP Gateway Screening Stop Action Sets - Sheet 2 of 7
Figure 2-22 Configure TLNP Gateway Screening Stop Action Sets - Sheet 3 of 7
Figure 2-23 Configure TLNP Gateway Screening Stop Action Sets - Sheet 4 of 7
Figure 2-24 Configure TLNP Gateway Screening Stop Action Sets - Sheet 5 of 7
Figure 2-25 Configure TLNP Gateway Screening Stop Action Sets - Sheet 6 of 7
Figure 2-26 Configure TLNP Gateway Screening Stop Action Sets - Sheet 7 of 7