DMS-100 List of Home Numbering Plan Area Code Subtables Table (HNPACONT) |
Table Name
List of Home Numbering Plan Area Code Subtables Table
Functional Description of Table HNPACONT
The Home Numbering Plan Area (HNPA) code subtables are as follows:
Office parameter MAXSTS in table OFCENG (Office Engineering) sets the maximum number of HNPAs or Serving Numbering Plan Areas (SNPA) and Serving Translation Schemes (STS).
All HNPAs or SNPAs appear as the first 128 entries in the table.
Datafill Sequence & Meaning
Enter data in table SNPANAME (Serving Numbering Plan Area Name) before you enter data in table HNPACONT. If addition of a tuple to HNPACONT occurs when field SNPA is "Y", the system updates SNPANAME with the same tuple. If SNPA is "N", the system does not add the tuple to SNPANAME.
When you delete STS with field SNPA as "Y" from HNPACONT, the system does not delete the equivalent entry in SNPANAME.
CAUTION: Possible service degradation of Direct Inward System Access (DISA) calls. For correct DISA operation, you must enter data in table HNPACONT. Service degradation can occur when DISA calls are attempted and table HNPACONT is empty.
Table Size
0 to 1,000 tuples
Datafill
The following table describes datafill for table HNPACONT:
----------------------------------------------------------------------------------------------
Table HNPACONT Field Descriptions
Field Subfield Entry Explanation and Action
----------------------------------------------------------------------------------------------
NPA or STS 000 to 999 Serving Translation Scheme
Enter a SNPA or a STS code.
----------------------------------------------------------------------------------------------
SNPA Y or N Serving Numbering Plan Area
Enter "Y" or "N" to indicate if a specified STS
in this table maps to a SNPA in table SNPANAME.
A HNPA or SNPA appears in one of the first 128
positions. You can enter these positions at
any time. Use SNPAs in:
* Line data
* POTS
* Virtual Facility Group (VFG) data
* PBX trunk data
* Table DNINV (Directory Number Inventory)
* Table DNROUTE (Directory Number Route)
* Table TOFCNAME (Terminating Office Name)
Enter data in table SNPANAME before table
HNPACONT. If you add a tuple to HNPACONT first
and SNPA is "Y", the system updates the same
tuple in table SNPANAME. If SNPA is "N" the
system does not add the tuple to table SNPANAME.
----------------------------------------------------------------------------------------------
NORTREFS 1 to 1,023 Number of Route References
Enter "2" for the quantity of route reference
numbers. The system extends field NORTREFS to
the highest route index that subtable
HNPACONT.RTEREF uses. An entry outside the range
indicated for this field is incorrect.
----------------------------------------------------------------------------------------------
NOAMBIGC 0 to 1,000 Number of Ambiguous Codes
Enter the number of ambiguous codes required.
An entry outside the range indicated for this
field is incorrect.
----------------------------------------------------------------------------------------------
OPTION ARS Enter option "ARS" to set the Automatic Route
Selection.
----------------------------------------------------------------------------------------------
OPTIONS See Subfield
DMI 1 to 32,766 Digit Manipulation Index
The DMI option enables the called number
characteristics to be manipulated by use of
table DIGMAN. This is an index into table
DIGMAN.
CALLTYPE PUBLIC, PRIVATE Call Type
This subfield allows for switching of routing
call-types on an as-needed basis.
* Enter "PUBLIC" for public routing of calls.
* Enter "PRIVATE" for private routing of calls.
----------------------------------------------------------------------------------------------
RTELIST CND:CNDSEL MIGRATE If the call is transferred to a route list or
element based on the assignment of the MIGRATE
line option to the terminating DN, enter
"MIGRATE".
NOT:CNDSEL MIGRATE If the call is transferred to a route list or
element based on the assignment of the MIGRATE
line option to the terminating DN, enter
"MIGRATE".
----------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------
OPTION = ARS If the entry in field OPTION is "ARS", enter
data in subfields ARS_OPTION and RR.
----------------------------------------------------------------------------------------------
ARS_OPTION DEFAULT_RTEREF Automatic Route Selection Option
Enter DEFAULT_RTEREF to select the default that
subtable HNPACONT.RTEREF defines.
RR 0 to 1,023 Extended Route Reference Index
Enter the extended route reference index.
10DIG Y or N Enter "Y" if the system collects ten-digits
before the system sends the call to the ARS
default route. The ARS default route is an
enforced ten-digit dialing environment.
Enter "N" if user-dialed local calls are dialed
as seven-digits. Calls dialed as 7D do not have
a prefix or an area code. Enter "N" if toll
calls are dialled as 1+10D. Calls dialed as
1+10D have a prefix and a full ten-digits.
The ten-digits include the area code.
----------------------------------------------------------------------------------------------
-End-
Datafill Example
The following example MAP display shows sample datafill for table HNPACONT. A switching unit with two NPAs, 613 and 819, and two STS codes, 001 and 002, appears in this example.
Field NORTREFS is 2. The system extends field NORTREFS to the highest route index that subtable HNPACONT.RTEREF uses. The system allocates memory for 20 ambiguous codes in HNPA 613.
Note: The system labels STS 001 as an ARS STS in the options field. Entry STS 001 does not have an ARS default route set. Entry STS 002 is also an ARS STS. Entry STS 002 has a default route. The default route is entry "5" in HNPACONT 002: RTEREF. The default route does not assume ten-digit digit collection. The 10DIG sub-option is "N".
STS SNPA NORTREFS NOAMBIGC RTEREF HNPACODE ATTRIB RTEMAP OPTIONS _______________________________________________________________________________________________ 001 N 2 2 ( 3) ( 0) ( 0) ( 0) (ARS) $) $ 002 N 15 2 ( 3) ( 0) ( 0) ( 0) (ARS (DEFAULT_RTEREF 5 N) $) $ 613 Y 932 20 ( 427) ( 1) ( 84) ( 0) $ 819 Y 81 3 ( 18) ( 1) ( 91) ( 0) $ |
Additional Information
This section provides information on how to enter data in table HNPACONT for specified applications. This section also provides product description information for table HNPACONT.
Information Messages
If you delete a tuple in table HNPACONT, the system does not delete the same tuple from table SNPANAME.
Deletion of an area code from SNPANAME affects other entries. When deletion of an area code occurs, the system deletes the entry from HNPACONT. The system maintains the route and code references against the deleted tuple. These references are available when a new SNPA replaces the SNPA deleted in SNPANAME.
If you delete a tuple from SNPANAME, the system removes the same tuple from HNPACONT. The following messages appears:
WARNING: Failure to add a new tuple to replace the SNPA just deleted will leave table HNPACONT corrupted. WARNING: Failure to add a new tuple to replace the SNPA just deleted will leave table TOFCNAME corrupted.
If you attempt to replace the STS in HNPACONT after the tuple is deleted, the following message appears:
A SNPANAME tuple referenced by HNPACONT was deleted. Please add tuples back to SNPANAME before entering anything new.
If you attempt to delete a tuple from HNPACONT and the tuple is referenced in any of the screening tables, the delete command is unavailable. The following message appears:
WARNING: DELETING A TUPLE FROM A HEAD TABLE WILL DELETE ALL CORRESPONDING SUBTABLE DATA. SUBTABLE(S) WITH DATA: RTREF HNPACODE RTEMAP DO YOU REALLY WANT TO DELETE (Y/N) >Y SERVING_TRANSLATION_SCHEME ??? IS USED IN OTHER TABLES. USE TABREF TO GET POTENTIAL TABLE LIST. INCONSISTENT DATA DMO REJECTED
If you delete a tuple from HNPACONT and the tuple is not referenced in any of the screening tables, the tuple will be deleted. The following warning message appears:
WARNING: DELETING A TUPLE FROM A HEAD TABLE WILL DELETE ALL CORRESPONDING SUBTABLE DATA. SUBTABLE(S) WITH DATA: RTREF HNPACODE RTEMAP DO YOU REALLY WANT TO DELETE (Y/N) >Y THIS TABLE ATTRIB CAN NOT BE EXTENDED LCA AND CSS SCREENING TABLES DEALLOCATED WARNING: DELETIONS MAY CAUSE PROBLEMS IN OTHER TABLES REFERENCING STS OR SNPA IN PARTICULAR, IT IS IMPERATIVE THAT THE STS DELETED SHOULD NOT BE FOUND IN ANY OF THE FNPASTS SUBTABLES. IF THIS HAPPENS TO BE THE CASE, THEN ALL TUPLES WITH THE DELETED STS M*U*S*T ALSO BE DELETED.
If you add a replacement for the deleted tuple into table SNPANAME, the following message appears:
REPLACEMENT OF KEY ??? IN TABLE HNPACONT WITH KEY ??? SUCCEEDED. TUPLE ADDED
After this message appears, both tables correctly display the new tuple.
The STSs are necessary for Integrated Business Network (IBN) private networks. Table IBNXLA (IBN Translation) defines the STSs.
Each HNPA has the following subtables:
The system assigns each line, incoming trunk group, and two-way trunk group to 1 of the 128 serving home NPA codes.
Table TRKGRP stores the SNPA for a normal trunk group for each incoming and two-way trunk group.
Table LINEATTR stores the SNPA for a line and the line attribute assigned to the line.
Table IBNLINES stores the SNPA for an IBN line.
Table IBNXLA stores the STS code for an IBN line.
Field NPA changes and allows between one and seven-digits instead of the previous three-digit value. When the office parameter ACTIVE_DN_SYSTEM in table OFCENG is "NORTH_AMERICA", expect a three-digit NPA.
For DMS-100 domestic offices, the tuple verification phase that adds to the table allows the entry of only three-digits.
Partitioned Table Editor Feature
In DMS offices with feature BC1459 Partitioned Table Editor (PTE), the operating company can allow a user to edit specified tuples of table HNPACONT. If the user is from outside the operating company, the user edits using PTE. This feature allows an authorized user to edit the tuples of the following subtables at the authorized positions of table HNPACONT.
The user must own the STS to access a tuple in table HNPACONT.
For example, the datafill example for table DATAOWNR can be as follows:
Key Owner ------------------ STS 001 CARLING
In this condition, the authorized user, CARLING, can access the tuples with a key 001. User CARLING cannot view table HNPACONT tuples unless other users own these tables. Table OWNER classifies these tuples as public.
The operating company uses the PTE feature to limit edit access to a table for a specified user to the following restrictions:
Set the PTE access for users outside the operating company. The below table is an example of the PTE access settings:
---------------------------------------------------------------------------------------------- Recommended PTE Access Settings Level Table Name Action ---------------------------------------------------------------------------------------------- Table HNPACONT Change or read-only access. Subtable HNPACONT.HNPACODE Add or delete tuples access. Subtable HNPACONT.ATTRIB Add or delete tuples access. Subtable HNPACONT.RTEREF Add or delete tuples access. Subtable HNPACONT.RTEMAP Add or delete tuples access. ----------------------------------------------------------------------------------------------
See the description of table OWNER for more information on the Customer Data Change (CDC) feature tables.