14 Calling Name Conversion Facility (CNCF) Configuration
Chapter 14, Calling Name Conversion Facility (CNCF) Configuration, contains a description of the Calling Name Conversion Facility feature the procedure necessary to configure this feature.
Introduction
This feature provides a conversion of ISUP IAM messages using two versions of calling name identification presentation (CNIP) for calling name information delivery. One version of the CNIP uses the non-standard proprietary ISUP party information (PIP) parameter. The other version uses the ANSI standard ISUP generic name (GN) parameter. The conversion will either replace the PIP parameter with the GN parameter or the GN parameter with the PIP parameter in the ISUP IAM message.
The gateway screening feature is used to select the ISUP messages that are converted. The incoming messages are selected based on the OPC and DPC in the routing label of the message, and the message type in the service information octet. The message type is defined by the value of the service indicator (SI) field of the SIO. ISUP messages contain the value 5 in the service indicator field of the SIO. Screening rules for Allowed OPC, Allowed DPC, and the Allowed SIO entities must be configured in the database for this feature.
This feature is an optional feature and must be turned on
with the
chg-feat command and the
cncf=on parameter. The
rtrv-feat command can be used to verify
if this feature is on or not. This feature applies to only ANSI networks.
Figure 14-1 shows an example network which contains these two separate ISUP versions. Based on this example, Table 14-1 shows when the ISUP IAM message conversion by the CNCF feature occurs.
Figure 14-1 PIP/GN Parameter Conversion
Table 14-1 ISUP IAM Message Conversion Examples
| Origination Point Code | Destination Point Code | ISUP IAM Message Conversion |
|---|---|---|
| 001-002-003 | 004-005-006 | Yes |
| 001-002-003 | 007-008-009 | No |
| 004-005-006 | 001-002-003 | Yes |
| 004-005-006 | 007-008-009 | Yes |
| 007-008-009 | 001-002-003 | No |
| 007-008-009 | 004-005-006 | Yes |
Great care must be taken when configuring the gateway screening rules for this feature. The CNCF feature has no way to validate the gateway screening rules to detect errors in converting messages between compatible networks. For example, using the example network in Figure 14-1, the ISUP IAM message traffic from node 001-002-003 to node 007-008-009 does not need to be converted because they are using the same calling name delivery parameter, PIP. If the gateway screening rules are not carefully configured, these messages could be converted when they do not need to be.
No measurements are collected showing the number of MSUs converted by this feature.
If both the COPY and CNCF gateway screening stop actions are specified as the stop actions for
the gateway screening process, the MSU is converted by the CNCF feature.
If both the
RDCT and
CNCF gateway screening stop actions are
specified as the stop actions for the gateway screening process, the MSU is
converted by the CNCF feature, then redirected for the DTA feature.
If there are multiple PIP parameters or GN parameters with calling name information within a single ISUP IAM, only the first occurrence of the parameter in the ISUP IAM message is converted.
Only GN IAM messages containing calling name information (Type of Name = Calling Name, Presentation = Allowed, Parameter Length >1) are converted to PIP IAM messages.
Only PIP IAM messages containing Calling Name Information (Sub-Parameter Code = Name Information, Name Element Indicator = Calling Party) are converted to GN IAM messages.
If the received IAM message contains both a GN and a PIP parameter with calling name information, the GN parameter is retransmitted and the PIP parameter is deleted.
Any MSU that is not converted is simply retransmitted. These MSUs include non-ISUP MSUs, non-IAM MSUs, and any IAM MSU received that does not contain either a GN or PIP parameter.
If the PIP parameter contains other information in addition to the calling party name information, only a GN parameter containing calling party name information is generated.
The linkset being screened for this feature should not
contain C links (lst=c parameter of the
ent-ls and
chg-ls commands). This would result in
the double conversion of the ISUP IAM messages.
Configuring the EAGLE for the CNCF Feature
To configure the EAGLE for the CNCF feature, gateway
screening rules for Allowed OPC, Allowed DPC, and the Allowed SIO entities must
be configured in the database for this feature. The last entity in the
screening process (nsfi=stop) must have a
gateway screening stop action set containing the
CNCF gateway screening stop action.
The allowed OPC screening rules must contain the OPCs that the ISUP IAM messages are being sent from.
The allowed DPC screening rules must contain the DPCs that the ISUP IAM messages are being sent to.
The allowed SIO screening rules must contain the ISUP
message type, defined by the
si=5 parameter.
The CNCF feature must be turned on. Before the CNCF
feature can be turned on, the gateway screening feature must be on. This can be
verified with the
rtrv-feat command.
Figure 14-2 CNCF Gateway Screening Configuration - Example 1
Figure 14-3 CNCF Gateway Screening Configuration - Example 2
Figure 14-4 CNCF Gateway Screening Configuration - Example 3
Figure 14-5 CNCF Gateway Screening Configuration - Example 4
Canceling the
RTRV-LS Command
Because the
rtrv-ls command used in this procedure
can output information for a long period of time, the
rtrv-ls command can be canceled and
the output to the terminal stopped. There are three ways that the
rtrv-ls command can be canceled.
- Press the
F9function key on the keyboard at the terminal where thertrv-lscommand was entered. - Enter the
canc-cmdwithout thetrmparameter at the terminal where thertrv-lscommand was entered. - Enter the
canc-cmd:trm=<xx>, where<xx>is the terminal where thertrv-lscommand was entered, from another terminal other that the terminal where thertrv-lscommand was entered. To enter thecanc-cmd:trm=<xx>command, the terminal must allow Security Administration commands to be entered from it and the user must be allowed to enter Security Administration commands. The terminal’s permissions can be verified with thertrv-secu-trmcommand. The user’s permissions can be verified with thertrv-userorrtrv-secu-usercommands.
For more information about the
canc-cmd command, go to
Commands User's Guide.
Figure 14-6 Calling Name Conversion Facility Configuration - Sheet 1 of 4
Figure 14-7 Calling Name Conversion Facility Configuration - Sheet 2 of 4
Figure 14-8 Calling Name Conversion Facility Configuration - Sheet 3 of 4
Figure 14-9 Calling Name Conversion Facility Configuration - Sheet 4 of 4