Point Code Formats and Conversion

Many of the commands used for database configuration use point codes. This section describes the point code formats that the system supports. If you need additional information or procedural information, refer to the Database Administration Manual - SS7.

The system supports four different point code formats:

ANSI point codes
ITU International point codes
ITU National point codes
ITU National 24-bit point codes

Each format is described in further detail in the following sections.

ANSI Point Codes

ANSI point codes are made up of three groups of digits called the network indicator (ni), network cluster (nc), and network cluster member (ncm). The values for ANSI point codes depend on the value of the pctype parameter of the chg-sid command, either ansi or other.

If the pctype=ansi command is entered, the range of values for an ANSI point code is as follows:

ni-001-255
nc-001-255 (if ni = 001-005)
-000-255, * (if ni = 006-255)
ncm-000-255

The following rules apply to provisioning ANSI point codes if the pctype=ansi parameter is specified:

An ni value of 0 is not allowed (e.g., dpc=0-1-1 and dpc=0-0-0 are not valid point codes).
If the ni value is 1, 2, 3, 4, or 5, then the nc value cannot be 0 (e.g., dpc=5-0-1 is rejected).
If the ni value is 1, 2, 3, 4, or 5, then network routing point codes are not allowed (e.g., dpc=4-*-* is rejected).

If the pctype=other parameter is specified, the ANSI point codes do not meet ANSI standards. The range of values for these ANSI point codes is as follows:

ni-000-255
nc-000-255, *
ncm -000-255, *

The following rules apply to provisioning ANSI point code if the pctype=other parameter is specified:

An ni value of 0 is allowed, however dpc=0-0-0 is rejected (e.g., dpc=0-1-1 is accepted).
The nc value can be 0 for all values of ni (e.g., dpc=5-0-1 is accepted).
Network routing point codes are allowed for all values of ni (e.g., dpc=4-*-* is accepted).

An ANSI point code containing all zeros (0-0-0) is not a valid point code and cannot be entered into the database.

ANSI point codes support the Private (Internal) Point Code subtype prefix (p-). The prefix can be specified before the point code subfield values to indicate a Private Point Code (i.e p-5-0-1). See Spare and Private Point Code Subtype Prefixes.

Note:

Point codes specified by many commands, including those for site identification, routing keys, and LNP, are required to be full point codes. The asterisk values are not valid in the commands that specify these point codes. The command Dependencies sections identify the point codes that must be full point codes in the commands.

A range of values for a subfield is specified by separating the values that define the range by two ampersands (&&); for example, ni=025&&100 specifies all network indicators for ANSI point codes from 25 - 100.

The asterisk (*) point code value indicates a single cluster address for a cluster point code (e.g., 20-2-*) or a network routing destination (20-*-*). If * is used for the nc subfield, then * must be also be used for the ncm subfield.

A double asterisk (**) and a triple asterisk (***) can also be used for the nc and ncm subfields of the ANSI point code, but only for the rtrv-dstn, rept-stat-dstn, rtrv-rte, and rept-stat-rte commands. If *, **, or *** is used for the nc subfield, then *, **, or *** must be used for the ncm field

For examples of all of these point code values, see the rtrv-dstn command output.

ITU International Point Codes

The ITU international point codes are made up of three groups of digits called zone, area, and id. The range of varnames for ITU International point codes are:

zone-0-7
area-000-255
id-0-7

An ITU international point code containing all zeros (0-000-0) is not a valid point code and cannot be entered into the database.

ITU international point codes support the Spare Point Code subtype prefix (s-). The prefix can be specified before the point code subfield varnames to indicate a Spare Point Code (s-5-222-1, for example). See Spare and Private Point Code Subtype Prefixes.

ITU National Point Codes

The ITU national point code is a 14-bit integer. The point codes can be a single number up to five digits, or two, three, or four numbers (members) separated by dashes.

If the ITU National Duplicate Point Code (ITUDUPPC) feature is on, ITU national point codes can have group codes assigned to them. The point code is a 1- to 5-digit number. The group code is a two-character field ranging from aa to zz that is entered as the last subfield of the point code and is separated by a dash from the rest of the point code. An example is 12345-az.

If the flexible point codes option is enabled (see the chg-stpopts command, :npcfmti parameter), an ITU national point code format consists of 2, 3, or 4 numbers separated by dashes (formatted as m1-m2-m3-m4). When the ITUDUPPC feature is also on, the format is m1-m2-m3-m4-gc with a group code. If one of the m1, m2, m3, m4 members is set to zero bits, no value is entered for that position in the point code. For example, if the npcfmti parameter value is set to 3-8-3-0, valid point codes would be 1-100-1-aa with a group code, or 7-255-7 with no group code. See the tables in the chg-stpopts command description for valid member values and additional examples.

The following ranges of values are valid:

nnnnn016383
nnnnn-gc0-16363; group code is aa-zz (the ITUDUPPC feature must be on)
m1-m2-m3-m4Each member represents the number of bits allowed in the corresponding position for a flexible ITU national point code. The range of each member is from 0 - 14. Each member must be specified; the member value of 0 indicates that the position is not specified in the flexible point code. The sum of the member values must equal 14.
m1-m2-m3-m4-gcEach member represents the number of bits allowed in the corresponding position for a flexible ITU national point code. The range of each member is from 0 to 14. Each member must be specified; the member value of 0 indicates that the position is not specified in the flexible point code. The sum of the member values must equal 14. Group code is aa-zz (the ITUDUPPC feature must be on).

An asterisk value (*) is allowed only for the rtrv-dstn and rtrv-rte commands to retrieve ITU-N DPCs if the ITUDUPPC feature is on (for point codes with group codes). The node and group code cannot both be *. For example, dpcn=12345-* and dpcn=*aa are allowed, but dpcn=*-* is not allowed.

If flexible point codes are also used, all valid m1, m2, m3, and m4 must all be either a number or an *. For example, 1-100-1-aa and *-*-*-aa are allowed, but 1-*-*-aa is not allowed.

ITU national point codes support the Spare Point Code subtype prefix (s-). The prefix can be specified before the point code subfield values to indicate a Spare Point Code (s-12345 or s-1-3-5-5-gc, for example). See Spare and Private Point Code Subtype Prefixes.

Converting ITU National Point Code Formats

Gateway screening only allows ITU national point codes to be provisioned in the database by the enter, delete, or change gateway screening commands, and displayed by the gateway screening retrieve commands as a single number. If a format other than a single number (14-0-0-0) for the ITU national point code has been defined by the npcfmti parameter of the chg-stpopts command, the ITU national point code must be converted into a single number so that it can be used by gateway screening.

For example, the format of the ITU national point code is 4-4-4-2 and you would like to add point code 7-7-7-1 into the allowed OPC screen. The point code 7-7-7-1 would have to be converted to a single number so that the point code can be added to the allowed OPC screen. To determine what multiple-part ITU national point code is represented by the single number ITU national point code in the gateway screening table, the single number point code must be converted to a multiple-part point code.

To convert a single number ITU national point code to a multiple-part point code, go to Converting Single Number ITU National Point Codes.

To convert a multiple-part ITU national point code to a single number point code, go to Converting Multiple-Part ITU National Point Codes.

For a definition of the different formats that can be used for ITU national point codes, see ITU National Point Codes.

When the ITU national point codes are converted from single numbers to multiple-part point codes, the resulting value of the multiple-part point code depends on the point code format specified by the npcfmti parameter of the chg-stpopts command. When converting the single number point code 14781 to the point code format 3-8-3-0, the resulting point code value is 7-55-5. If point code 14781 is converted to the point code format 4-4-4-2, the resulting point code value is 14-6-15-1.

Converting Single Number ITU National Point Codes

To make this conversion, you will need to know the format of the ITU national point code. This can be verified in the NPCFMTI field of the rtrv-stpopts command output. For this example, the ITU national point codes 14781 and 695 are converted to point codes using the 3-8-3-0 format.

Convert a single number ITU national point code to a multiple-part ITU national point code as follows.

Converting a Single Number ITU national point code to a multiple-part ITU national point code

Convert the point code to a binary number. This can be done with most scientific calculators.

The number 14781 converts to the binary number 11100110111101.

The number 695 converts to the binary number 1010110111.

Note:
Make sure the binary number contains 14 digits. If it does not, add leading zeros to the binary number to bring the total number of digits in the number to 14.

In this example, the binary equivalent for the decimal number 695 (1010110111) contains 10 digits; four zeros must be added to the beginning of the binary number. The resulting binary number is now 00001010110111.
Divide the binary number into the number of parts required by the format of the ITU national point code. For this example, the format is 3-8-3-0. Because the last part of the point code format is 0, the point code format contains only three parts. Divide the point code into three parts, the first part of the point code contains the first three digits of the 14-digit binary number, the second part of the point code contains the next eight digits of the 14-digit binary number, and the third part of the point code contains the last three digits of the 14-digit binary number.

For this example, the binary numbers would be divided like this:

11100110111101 = 111 00110111 101

00001010110111 = 000 01010110 111
Convert each part of the point code into a decimal number using the same scientific calculator used in step 1 and separate each part of the point code with dashes. The results are as follows.

111 00110111 101 = 7-55-5

000 01010110 111 = 0-86-7

Converting Multiple-Part ITU National Point Codes

To make this conversion, you will need to know the format of the ITU national point code. This can be verified in the npcfmti field of the rtrv-stpopts command output. For this example, the ITU national point codes 7-55-5 and 0-86-7, using the 3-8-3-0 point code format, are converted into a single number.

Convert multiple-part ITU national point codes to a single number as follows.

Converting Multiple-Part ITU National Point Codes to a Single Number

Convert each part of the point code into a binary number using a scientific calculator. The results are as follows.

7-55-5 = 111 00110111 101

0-86-7 = 000 01010110 111
Combine each part of the point code into a single binary number as follows.

111 00110111 101 = 11100110111101

000 01010110 111 = 00001010110111

Note:
If the binary number has any zeros at the beginning of the number, remove these zeros as they are not necessary.

In this example, the binary equivalent for the point code 0-86-7 (00001010110111) contains four zeros at the beginning of the binary number. When the leading zeros are removed from the binary number, the resulting binary number is now 1010110111.
Convert the binary number to a decimal number using the same scientific calculator used in step 1.

The binary number 11100110111101 converts to the decimal number 14781.

The binary number 1010110111 converts to the decimal number 695.

24-bit ITU-National Point Codes

The 24-bit ITU national point codes are made up of three groups of digits called main signaling area, sub signaling area, and signaling point. The valid values for 24-bit ITU national point codes are:

main signaling area-000-255
sub signaling area-000-255
signaling point-000-255

24-bit ITU national point codes support the Private (Internal) Point Code subtype prefix (p-). The prefix can be specified before the point code field values to indicate a Private Point Code (p-2055-222-2011, for example). See Spare and Private Point Code Subtype Prefixes.

Spare and Private Point Code Subtype Prefixes

The Spare Point Code Support feature and the Internal Point Code Support feature provide optional point code subtype prefixes. The Spare Point Code feature must be enabled before a point code subtype prefix can be specified for a point code.

Note:

The SEAS interface does not support point code subtype prefixes.

The values p-, s-, and ps- are valid point code subtype prefixes. The dash- separates the point code subtype prefix from the remainder of the point code. The prefixes are displayed in lower case. The syntax for the remainder of the point code remains the same.

The Spare Point Code prefix (s-) applies only to ITU-I and ITU-N point code domains (ITU-N24 point codes do not support the Spare Point Code prefix), to allows the EAGLE to fully support ITU National and International Spare Point Codes. Table A-9 lists the commands that support the Spare Point Code subtype prefix.

The Private (Internal) Point Code prefix (p-) applies to all point code domain types (including ITU-N24 point codes), to allow messages destined to the End Office Node to be routed from the inbound LIM to the outbound IPGWx. Table A-10 lists the commands that support the Private Point Code subtype prefix.

The subtype prefix ps- can be specified when the point code parameter supports both the spare and private point code prefixes.

Table A-9 Commands that support the Spare Point Code Prefix

Command	Description	Applicable Point Code Parameters
`alm`	Alarm	dpci and dpcn
`appl-rtkey`	Application Route Key	dpci and dpcn; opci and opcn
`cspc`	Concerned Signaling Point Code	pci and pcn
`dstn`	Destination	spci and spcn; dpci and dpcn; and Alias combinations.
`ent-trace`	Enter Trace	dpci and dpcn; opci and opcn
`gsmmap-scrn`	GSM MAP Screening	npci and npcn
`gsmopts`	GSM Options	ppsmspci1, ppsmspci2, ppsmspcn1, ppsmspcn2
`gsms-opcode`	GSM Short Message Services OP-Code	pci and pcn
`gtt/gta`	Global Title Translation/Global Title Address	pci and pcn
`ls`	Linkset	apci and apcn
`map`	Mated Application	pci and pcn; mpci and mpcn
`mrn`	Mated Relay Node	pci and pcn; pci1 and pcn1; pci2 and pcn2; pci3 and pcn3; pci4 and pcn4
`na`	Network Appearance	type=ituis, type=ituns
`pass`	Pass Commands	Syntax for routing keys
`rmt-appl`	Remote Application	ipci and ipcn
`rte`	Route	dpci and dpcn
`scr-aftpc`	Gateway Screening Allowed Affected Point Code	pcst and pctype
`scr-blkdpc`	Gateway Screening Blocked Destination Point Code	pcst and pctype
`scr-blkopc`	Gateway Screening Blocked Origination Point Code	pcst and pctype
`scr-cdpa`	Gateway Screening Called Party (CDPA PC Destination) Point Code	pcst and pctype
`scr-cgpa`	Gateway Screening Calling Party (Origination) Point Code	pcst and pctype
`scr-destfld`	Gateway Screening Affected Destination (Concerned) Point Code	pcst and pctype
`scr-dpc`	Gateway Screening Destination Point Code	pcst and pctype
`scr-opc`	Gateway Screening Origination Point Code	pcst and pctype
`sid`	Site ID	True pci and pcn; cpci and cpcn; ncpci and ncpcn.
`spc`	Secondary Point Code	spci and spcn

Table A-10 Commands that support the Private Point Code Prefix

Command	Description	Applicable Point Code Parameters
`dstn`	Destination	spci and spcn; dpc, dpca, dpci,, and dpcn Does not apply to Aliases
`ls`	Linkset	If ipgwapc=yes, apc, apcn, apci, and apcn
`gtt/gta`	Global Title Translation	pc, pca, pci, and pcn
`inh/unhb-alm`	Destination alarm inhibit	dpc, dpca, dpci, and dpcn
`rept-stat-cluster`	Report Cluster Status	dpc and dpca
`rept-stat-dstn`	Report Destination Status	dpc, dpca, dpci, and dpcn
`rmt-appl`	Remote Application	ipc, ipca, ipci, and ipcn
`rst-dstn`	Restore Destination	dpc and dpca
`rte`	Route	dpc, dpca, dpci, and dpcn