Adding an Allowed ISUP Message Type Screen
This procedure is used to add an allowed ISUP message
type (ISUP) screen to the database using the
ent-scr-isup
command. The parameters
used by the
ent-scr-isup
command are shown in the
Gateway Screening Attributes
section. The general rules that apply to configuring gateway screening entities
are shown in the
Gateway Screening Configuration
section.
Since both ISUP and TUP messages are
screened by the allowed ISUP message type screen, the
ent-scr-isup
command contains a
parameter for the ISUP message type (isupmt
)
and a parameter for the TUP message type (tupmt
). Only one of these parameters can be specified
for the allowed ISUP screen being entered into the database. The
isupmt
parameter should be specified
in screen sets that contain allowed SIO screens that are screening messages for
the service indicator value of 5 (SI=5). The
tupmt
parameter should be specified in
screen sets that contain allowed SIO screens that are screening messages for
the service indicator value of 4 (SI=4). If you wish to screen for TUP
messages, make sure that the screen set being configured contains an allowed
SIO screen that screens messages for the service indicator value of 4 (SI=4).
If you do not do this, the EAGLE will treat the message as an ISUP message,
even if the message contains the service indicator value of 4.
Table 15-1 Example Gateway Screening Allowed ISUP Configuration Table
Screening Reference | ISUPMT | NSFI | ACTNAME |
---|---|---|---|
isp1 | 135 | stop | CR |
isp2 | 139 | stop | CR |
Screening Reference | TUPMT | NSFI | ACTNAME |
tup1 | 100 | stop | CR |
Figure 15-5 Add an Allowed ISUP Message Type Screen - Sheet 1 of 3
Figure 15-6 Add an Allowed ISUP Message Type Screen - Sheet 2 of 3
Figure 15-7 Add an Allowed ISUP Message Type Screen - Sheet 3 of 3