Table Name
Terminating Office Name.
Functional Description of Table TOFCNAME
Table TOFCNAME stores the area code and office code for the switch. A Terminating Office Number (TOFCNO) consists of both an area code and an office code. Table HNPACONT or table SNPANAME must define the area code.
Table TOFCNAME replaces table THOUGRP. Table DNROUTE stores all routing information originally stored in table THOUGRP.
Software Optionality Control (SOC) options NPE00001 and NPE00002 implement duplicate office code and table TOFCNAME expansion capabilities. When NPE00001 is active, you can datafill one office code against more than one area code in table TOFCNAME. When NPE00002 is active, you can datafill table TOFCNAME with up to 8,151 entries.
Office parameter ACTIVE_DN_SYSTEM in table OFCENG controls the Directory Number (DN) system in use on the switch. You can set this parameter to the following:
Note: Unless SOC option NPE00001 is active, the DMS-100 switch does not allow two area codes to share the same office code.
Note: When the capacity of table TOFCNAME increases, the capacity of tables DNINV and DNROUTE decreases (from 1,000,000 to 300,000).
Local Number Portability
For Local Number Portability (LNP), it is preferable for the switch to use the Universal DN system with the North American dialing plan.
The DN is "ported-in" if you move the DN from a donor switch to a recipient switch. Option NONNATIVE in field OPTIONS is assigned to area code and office code entries for ported-in DNs.
Note: In North American applications, if table HOMELRN uses the resident area code and office code, you cannot change the resident area code and office code to nonresident.
Datafill Sequence
Datafill one or the other of the following tables before table TOFCNAME:
Table Size
The size of table TOFCNAME depends on:
The following table shows sizes for table TOFCNAME.
-----------------------------------------------------------------------------------------
TOFCNAME Size
Value of ACTIVE_DN_SYSTEM Maximum size of TOFCNAME
-----------------------------------------------------------------------------------------
NORTH_AMERICAN 100 tuples
UNIVERSAL 1,024 tuples if NPE00002 is not active
8,151 tuples if NPE00002 is active
-----------------------------------------------------------------------------------------
Datafill
The following table lists datafill for table TOFCNAME.
-----------------------------------------------------------------------------------------
Field Descriptions for Table TOFCNAME
Field or Subfield Entry Explanation
-----------------------------------------------------------------------------------------
AREACODE 0 to 9999999 Area Code Enter the area code.
(vector of up to
7 digits) The area code (NPA) identifies a geographical area
served by the switch. This field can contain one to
seven digits. In an office that uses the North
American numbering plan, the area code must be three
digits.
Enter an area code defined in table SNPANAME.
-----------------------------------------------------------------------------------------
OFCCODE 0 to 9999999 Office Code Enter the office code.
(vector of up to
7 digits) or $ The area code region consists of a number of
areas. The office code identifies the area served
by the office. An office code can have from zero
to seven digits. For an office that uses the North
American numbering plan, the office code must contain
three digits.
Enter a number that is not used as an area code.
For example, if the area code is 613, the office
code cannot be 613.
-----------------------------------------------------------------------------------------
-continued-
-----------------------------------------------------------------------------------------
Field or Subfield Entry Explanation (continued)
-----------------------------------------------------------------------------------------
Note: Service interruption can occur if you
enter an office code that is an area code. The switch
can route calls to the wrong location because the
switch cannot determine the termination point of the
call.
A tuple (AREACODE plus OFCCODE entry) cannot be an
expansion or reduction of another entry. For example,
if 200 34 (area code 200 plus office code 34) is a
tuple, you cannot add the following tuples to the
table: 20 03, 2003 45, or 20 034.
-----------------------------------------------------------------------------------------
OPTIONS NONNATIVE Ported-In DN
Enter NONNATIVE to identify a ported-in DN.
End the tuple with a $ (dollar sign).
Note: Translations ports in only DNs with
nonnative NPA-NXX that reside on the switch.
CODEHLDR Enter CODEHLDR to indicate that an NPA-NXX is
LERG assigned even though 1,000 blocks may be
pooled out to other switches. To assign the
CODEHLDR option to a tuple the NPE00005 SOC
option must be active.
Note: The CODEHLDR option cannot be
present with the NONNATIVE TOFCNAME option
and vice versa.
-----------------------------------------------------------------------------------------
-End-
Datafill Example
The following example shows typical datafill for table TOFCNAME without ported-in DNs datafilled.
----------------------------------------------------------------------------------------- Example of a MAP display: AREACODE OFCCODE OPTIONS ______________________________________________ 200 234 $ 784 324 $ 201 786 $ 613 621 $ 245 879 $ ______________________________________________
The following MAP display example shows typical datafill for table TOFCNAME with datafilled ported-in DNs.
----------------------------------------------------------------------------------------- Example of a MAP display: AREACODE OFCCODE OPTIONS ______________________________________________ 613 621 $ 819 725 NONNATIVE $ ______________________________________________
In this example, all DNs for:
Supplementary Information
The following explains error messages that can occur when you attempt to datafill table TOFCNAME.
Error Message: This tuple will create an ambiguity with NPA NXX.
Explanation: The area code and office code of the tuple being added is a superset of the area code and office code of a tuple already in table TOFCNAME.
User Action: Enter the tuple again, using a different area code, office code, or both.
Error Message: ERROR: This entry creates an ambiguity with a more precise entry and is not allowed.
Explanation: The area code and office code of the added tuple is a subset of the area code and office code of a tuple already in table TOFCNAME.
User Action: Enter the tuple again, using a different area code, office code, or both.
Error Message: ERROR: Duplicate office codes are not allowed while NPE00001 is idle.
Explanation: The office code of the tuple being added is equal to or a superset of the office code of a tuple already in table TOFCNAME.
User Action: Activate NPE00001. Enter the tuple again.
Error Message: ERROR: This entry creates a duplicate office code with a more precise entry. Duplicate office codes are not allowed while NPE00001 is idle.
Explanation: The office code of the tuple being added is a subset of the office code of a tuple already in table TOFCNAME. Activate NPE00001.
User Action: Enter the tuple again.