| Oracle® Communications EAGLE Database Administration - SS7 User's Guide Release 46.7 E97335 Revision 1 |
|
 Previous |
 Next |
| Oracle® Communications EAGLE Database Administration - SS7 User's Guide Release 46.7 E97335 Revision 1 |
|
|
Previous |
Next |
The EAGLE supports three different point code formats:
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 depends on the value of the pctype parameter of the chg-sid command, either ansi or other. If the pctype parameter is set to ansi, the ANSI rules for the ANSI point code are used to define the point code. The range of values for an ANSI point code with the pctype=ansi parameter are:
The pctype=other parameter specifies that the ANSI point codes do not meet ANSI standards. The range of values for ANSI point codes with the pctype=other parameter are:
The asterisk (*) point code value indicates a single cluster address for a cluster point code (for example, 20-2-*) or a network routing destination (21-*-*). for more information on cluster point codes, see the Cluster Routing and Management Diversity (CRMD) section. For more information on network routing point codes, see the Network Routing section.
A double asterisk (**) and triple asterisk (***) can also be used for the NC and NCM fields of the ANSI point code, but for only the rtrv-dstn, rept-stat-dstn, rtrv-rte, and rept-stat-rte commands.
A double asterisk in the NCM field of a point code (for example, 20-2-**) produces a summary report that shows all point code destinations or routes residing in the given cluster (20-2). This does not include the cluster point code, if the cluster point code (for example, 20-2-*) is provisioned. The following examples (rtrv-dstn and rtrv-rte) are reports generated using two asterisks in the NCM field of a point code.
rtrv-dstn:dpca=20-2-**
rlghncxa03w 09-05-28 21:16:37 GMT EAGLE5 41.0.0
DPCA CLLI BEI ELEI ALIASI ALIASN/N24 DMN
020-002-045 rlghncbb100 no --- ---------- -------------- SS7
020-002-050 rlghncbb100 no --- ---------- -------------- SS7
Destination table is (11 of 2000) 1% full
Alias table is (5 of 8000) 1% full
rtrv-rte:dpca=20-2-**
rlghncxa03w 07-05-28 21:16:37 GMT EAGLE5 37.0.0
DPCA ALIASI ALIASN/N24 LSN RC APCA
020-002-045 ---------- -------------- lsn1 15 020-002-045
lsn2 20 020-003-036
lsn3 25 001-001-002
RTX:No CLLI=-----------
020-002-050 ---------- -------------- lsn4 15 020-002-050
lsn3 20 001-001-002
lsn2 25 020-003-036
RTX:No CLLI=-----------
A double asterisk in the NC field of a network routing point code (for example, 21-**-*) produces a summary report that shows all point code destinations or routes that are members of the given network (network 21). This does not include the specified network routing point code (for example, 21-*-*). The following examples (rtrv-dstn and rtrv-rte) are reports using two asterisks in the NC field of a network routing point code.
rtrv-dstn:dpca=21-**-*
rlghncxa03w 09-05-28 21:16:37 GMT EAGLE5 41.0.0
DPCA CLLI BEI ELEI ALIASI ALIASN/N24 DMN
021-002-045 rlghncbb101 no --- ---------- -------------- SS7
021-002-050 rlghncbb101 no --- ---------- -------------- SS7
Destination table is (11 of 2000) 1% full
Alias table is (5 of 8000) 1% full
rtrv-rte:dpca=21-**-*
rlghncxa03w 07-05-28 21:16:37 GMT EAGLE5 37.0.0
DPCA ALIASI ALIASN/N24 LSN RC APCA
021-002-045 ---------- -------------- lsn10 15 021-002-045
lsn20 20 021-003-036
lsn30 25 010-001-002
RTX:No CLLI=-----------
021-002-050 ---------- -------------- lsn40 15 021-002-050
lsn30 20 010-001-002
lsn20 25 021-003-036
RTX:No CLLI=-----------
021-005-* ---------- -------------- lsn40 15 021-002-050
lsn30 20 010-001-002
lsn20 25 021-003-036
RTX:No CLLI=-----------
Three asterisks in the NCM field of a point code produces a summary report that shows all point code destinations or routes residing in the given network cluster along with the specified cluster point code, if the cluster point code (for example, 20-2-*) is provisioned. The following examples (rtrv-dstn and rtrv-rte) are reports using three asterisks in the NCM field of a point code.
rtrv-dstn:dpca=20-2-***
rlghncxa03w 09-05-17 16:00:32 GMT EAGLE5 41.0.0
DPCA CLLI BEI ELEI ALIASI ALIASN/N24 DMN
020-002-* rlghncbb000 no --- ---------- -------------- SS7
020-002-045 rlghncbb100 no --- ---------- -------------- SS7
020-002-050 rlghncbb100 no --- ---------- -------------- SS7
Destination table is (11 of 2000) 1% full
Alias table is (5 of 8000) 1% full
rtrv-rte:dpca=20-2-***
rlghncxa03w 07-05-28 21:16:37 GMT EAGLE5 37.0.0
DPCA ALIASI ALIASN/N24 LSN RC APCA
020-002-045 ---------- -------------- lsn1 15 020-002-045
lsn2 20 020-003-036
lsn3 25 001-001-002
RTX:No CLLI=-----------
020-002-050 ---------- -------------- lsn4 15 020-002-050
lsn3 20 001-001-002
lsn2 25 020-003-036
RTX:No CLLI=-----------
020-002-* ---------- -------------- lsn4 15 020-002-050
lsn3 20 001-001-002
lsn2 25 020-003-036
RTX:No CLLI=-----------
Three asterisks in the NC field of the point code produces a summary report that shows all point code destinations or routes residing in the given network along with the specified network routing point code. The following examples (rtrv-dstn and rtrv-rte) are reports using three asterisks in the NC field of a network routing point code.
rtrv-dstn:dpca=21-***-*
rlghncxa03w 09-05-17 16:00:32 GMT EAGLE5 41.0.0
DPCA CLLI BEI ELEI ALIASI ALIASN/N24 DMN
021-*-* rlghncbb001 yes yes ---------- -------------- SS7
021-002-045 rlghncbb101 no --- ---------- -------------- SS7
021-002-050 rlghncbb101 no --- ---------- -------------- SS7
Destination table is (11 of 2000) 1% full
Alias table is (5 of 8000) 1% full
rtrv-rte:dpca=21-***-*
rlghncxa03w 07-05-28 21:16:37 GMT EAGLE5 37.0.0
DPCA ALIASI ALIASN/N24 LSN RC APCA
021-002-045 ---------- -------------- lsn10 15 021-002-045
lsn20 20 021-003-036
lsn30 25 010-001-002
RTX:No CLLI=-----------
021-002-050 ---------- -------------- lsn40 15 021-002-050
lsn30 20 010-001-002
lsn20 25 021-003-036
RTX:No CLLI=-----------
021-005-* ---------- -------------- lsn40 15 021-002-050
lsn30 20 010-001-002
lsn20 25 021-003-036
RTX:No CLLI=-----------
021-*-* ---------- -------------- lsn30 20 010-001-002
lsn20 25 021-003-036
lsn40 35 021-002-050
RTX:No CLLI=-----------
The following rules apply to provisioning ANSI point code if the pctype=ansi parameter is specified with the chg-sid command:
dpc=0-1-1 and dpc=0-0-0 are not valid point codes). dpc=5-0-1 is rejected). dpc=4-*-* is rejected). The following rules apply to provisioning ANSI point code if the pctype=other parameter is specified with the chg-sid command:
dpc=0-0-0 is rejected (for example, dpc=0-1-1 is accepted). dpc=5-0-1 is accepted). dpc=4-*-* is accepted). An ANSI point code containing all zeros is not a valid point code and cannot be entered into the database.
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 values for ITU International point codes are:
An ITU international point code containing all zeros is not a valid point code and cannot be entered into the database.
14-Bit ITU National Point Codes
The 14-bit ITU national point code is either a 1- to 5-digit number, or 2, 3, or 4 numbers separated by dashes. 14-bit ITU national point codes can also have group codes assigned to them if the ITU National Duplicate Point Code feature is on. The group code is a two-character field ranging from AA to ZZ that is entered as the last subfield of a 14-bit ITU national point code and is separated by a dash from the rest of the point code. If the ITU National Duplicate Point Code feature is on, the format of a 14-bit ITU national point code is either a 1- to 5-digit number with a group code (for example, 11567-aa), or 2, 3, or 4 numbers separated by dashes with a group code (for example, 5-15-10-3-aa).
For more information on the format of 14-bit ITU national point code formats, see the 14-Bit ITU National Point Code Formats section.
For more information on the ITU National Duplicate Point Code feature and group codes, see the ITU National Duplicate Point Codes section.
24-Bit ITU National Point Codes
A 24-bit ITU national point code is made up of three segments separated by dashes. Each segment contains three digits and corresponds to 8 bits of the point code. The range of values for 24-bit ITU national point codes are:
A 24-bit ITU international point code containing all zeros is not a valid point code and cannot be entered into the database.
Spare Point Codes
The provisioning of spare point codes allows the EAGLE to process messages that contain either the International Spare or National Spare network indicator values. Spare point codes can be provisioned only if the ITU National and International Spare Point Code (PC) Support feature is enabled. Only ITU-I and 14-bit ITU-N point codes can be provisioned as spare point codes.
Spare point codes are shown with the prefix “s-” with the point code value. This allows the destination point code table to contain two point code entries with the same value, one a spare point code and one a non-spare point code. For example, the destination point code table contains these point code entries, 2-034-5 and s-2-034-5. Point code 2-034-5 is a non-spare ITU-I point code and point code s-2-034-5 is a spare ITU-I point code.
Private Point Codes
Private point codes are used for internal routing in the EAGLE 5 ISS. Private point codes can be used for internal point codes for the End Office feature, and for adjacent point codes for IPGWx linksets.
Private point codes are shown with the prefix “p-” with the point code value. This allows the destination point code table to contain two point code entries with the same value, one private and one not private. For example, the destination point code table contains these point code entries, 002-002-002 and p-002-002-002. Point code 002-002-002 is a non-private point code that is used for configuring linksets and routes from the EAGLE 5 ISS to external nodes in the network. Point code p-002-002-002 is a private point code and is not known to the external nodes in the network.
By using private point codes for internal routing, these point code values are not known outside of the EAGLE 5 ISS and do not use a point code value for network configuration.
There can be private point codes for all point code types: ANSI, ITU-I, ITU-I Spare, 14-bit ITU-N, 14-bit ITU-N Spare, and 24-bit ITU-N.
Point Code Usage
The ANSI are used in ANSI networks. The ITU international point codes are used in ITU international networks. The ITU national point codes are used in ITU national networks. ITU national point codes can be either 14-bit ITU national point codes, or 24-bit ITU national point codes. Table 2-1 shows a sample destination point code for each type of network.
Table 2-1 Point Code Format
| Network Type | Point Code Format |
|---|---|
| ANSI |
001-002-003 |
| ITU International |
7-255-7 |
| 14-bit ITU National |
|
| 24-bit ITU National |
001-002-003 |
To enter an ITU international point code, a 14-bit ITU national point code or a 24-bit ITU national point code, either as a DPC or as an alias point code, the self ID of the EAGLE must be defined for these networks. Verify this with the rtrv-sid command. If point code values are shown in the PCI field of the output of the rtrv-sid command, then ITU international point codes can be entered. If point code values are shown in the PCN field of the output of the rtrv-sid command, then the 14-bit ITU national point codes can be entered. If point code values are shown in the PCN24 field of the output of the rtrv-sid command, then 24-bit ITU national point codes can be entered. If a value is shown in the PCN field, then a value cannot be entered in the PCN24 field. If a value is shown in the PCN24 field, then a value cannot be entered in the PCN field.
A destination is defined with a mandatory true point code of one format, and two optional alias point codes that are of the other two formats. Alias point codes are used to provide alternate point codes for a particular destination. The true point code must be of the same format as the point code used for the self ID of the EAGLE and must match the format of the point code used for the destination node. For example, if the destination node uses an ANSI point code, then the true point code must be an ANSI point code.
A destination can have up to two alias point codes. A destination alias point code type must not match that destination's true point code type. If both alias point codes are defined, the point code types of the aliases must not match.
The point code type (ANSI, ITU international, ITU national) is specified by different parameters. A letter that indicates the point code type is appended to the parameter that specifies the point codes. The appended letters are as follows.
“A” – indicates an ANSI point code, for example, dpca
“I” – indicates an ITU international point code, for example, dpci
“N” – indicates a 14-bit ITU national point code, for example, dpcn
“N24” – indicates a 24-bit ITU national point code, for example, dpcn24
The ANSI point codes can also be specified by a point code parameter without the letter “A” appended to it, for example, dpc.
