Adding a Blocked DPC Screen
This procedure is used to add a blocked destination
point code (DPC) screen to the database using the
ent-scr-blkdpc command. The parameters
used by the
ent-scr-blkdpc 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.
The examples in this procedure are used to add the blocked DPC screen data shown in Table 8-1 and based on the example configurations shown in Figure 2-3 and Figure 2-5.
Table 8-1 Example Gateway Screening Blocked DPC Configuration Table
| Screening Reference | NI | NC | NCM | NSFI | NSR |
|---|---|---|---|---|---|
| gws9 | C | C | C | cgpa | gw13 |
| gws9 | 005 | 005 | 005 | fail | ---- |
| gw12 | C | C | C | cgpa | gw14 |
| gw12 | 004 | 004 | 004 | fail | ---- |
Note:
If you using multiple-part ITU national point codes with gateway screening, see the 14-Bit ITU National Point Code Formats section.The blocked DPC screen can reference one of the following screens.
- Allowed Affected Destination Field
- Allowed CGPA
- Allowed ISUP
Verifying Gateway Screening Configuration
Enter the following commands to verify that these screens are in the database.
rtrv-scr-destfld:all=yesrtrv-scr-cgpa:all=yesrtrv-scr-isup:all=yes
Gateway Screening Configuration Procedures
If the desired screen is not in the database, perform one of the following procedures to add the desired screen to the database or change an existing screen in the database.
- Adding an Allowed Affected Destination Field Screen
- Adding an Allowed Calling Party Address Screen
- Adding an Allowed ISUP Message Type Screen
- Changing an Allowed Affected Destination Field Screen
- Changing an Allowed Calling Party Address Screen
- Changing an Allowed ISUP Message Type Screen
For the first entry for a specific screening reference,
the value for the point code must be
c, and the NSFI must be either
stop or
cgpa. If the NSFI is
stop, the screening of the message
will stop at the specified blocked DPC screen. If the NSFI is
cgpa, then any message containing a
point code that is not listed in the blocked DPC screen with a NSFI equal to
fail, will continue to be screened
with the allowed CGPA screen. All subsequent entries for that screening
reference must contain a numeric point code value, the NSFI must be equal to
fail, and the
nsr parameter cannot be specified. Any
message that contains a DPC in the blocked DPC screen with the NSFI equal to
fail will be rejected from the network
and the screening process is stopped.
The
pcst parameter, specifying whether or
not the ITU-I or 14-bit ITU-N point code is a spare point code, cannot be used
with the
zone=c or
npc=c parameters.
Specifying a Range of Values
A range of values can be specified for the point code
parameters
ni,
nc, or
ncm.
If a range of values is specified for any of these parameters, and the value of the other parameters match existing values for the screening reference name, the range of values for the point code parameter cannot include any values for that parameter that are currently provisioned for the screening reference name.
For example, screening reference name
scr1 contains these entries:
SR NI NC NCM NSFI NSR/ACT
SCR1 C C C CGPA cg01
SCR1 240 001 010 FAIL ------
SCR1 241 010 020 FAIL ------Another entry for screening reference
scr1 with the
ni value of 240 and the
nc value of 001 cannot be specified if
the range of values for the
ncm parameter includes the value 010.
The ANSI point code parameter values can be specified as
a single value, a range of values, or with an asterisk (*). The asterisk
specifies all possible values for the
ni,
nc, and
ncm parameters.
Table 8-2
shows the valid combinations of these parameter values.
Table 8-2 Valid Value Combinations for ANSI Point Code Parameters
| NI | NC | NCM |
|---|---|---|
| Single Value | Single Value | Single Value |
| Single Value | Single Value | Range of Values |
| Single Value | Single Value | Asterisk |
| Single Value | Range of Values | Asterisk |
| Single Value | Asterisk | Asterisk |
| Range of Values | Asterisk | Asterisk |
| Asterisk | Asterisk | Asterisk |
A range of values can also be specified for an ITU-I or 24-bit ITU-N point code parameter using a combination of asterisks (*) and single values for the point code parameters. Table 8-3 shows the valid combinations of the ITU-I parameter values. Table 8-4 shows the valid combinations of the 24-bit ITU-N parameter values.
Table 8-3 Valid Value Combinations for ITU-I Point Code Parameters
| ZONE | AREA | ID |
|---|---|---|
| Single Value | Single Value | Single Value |
| Single Value | Single Value | Asterisk |
| Single Value | Asterisk | Asterisk |
| Asterisk | Asterisk | Asterisk |
Table 8-4 Valid Value Combinations for 24-Bit ITU-N Point Code Parameters
| MSA | SSA | SP |
|---|---|---|
| Single Value | Single Value | Single Value |
| Single Value | Single Value | Asterisk |
| Single Value | Asterisk | Asterisk |
| Asterisk | Asterisk | Asterisk |
Figure 8-5 Add a Blocked DPC Screen - Screen 1 of 5
Figure 8-6 Add a Blocked DPC Screen - Screen 2 of 5
Figure 8-7 Add a Blocked DPC Screen - Screen 3 of 5
Figure 8-8 Add a Blocked DPC Screen - Screen 4 of 5
Figure 8-9 Add a Blocked DPC Screen - Screen 5 of 5