Nortel DMS-100 Table DNINV


Table Name

Directory Number Inventory.

Functional Description of Table DNINV

Table DNINV is a read-only table.  This table replaces table DN.  Table DNINV contains data for all assigned Directory Numbers (DN).  The data includes DNs from table DNROUTE.

Table DNINV automatically gathers information when the operating company:

There is no input form for this table.

Attention - Operating Company Personnel:  Do not change any of the line data tables through table control because you may corrupt the internal database.  Use the Service Order System (SERVORD) to update subscriber line data.

The following table describes different selectors for table DNINV.

-----------------------------------------------------------------------------------------
DNINV Features

DN Selector      Use
-----------------------------------------------------------------------------------------
A                Integrated Business Network (IBN) data network address
ACDTK            Automatic Call Distribution (ACD) trunk directory number
C                No longer used
D                Treatment selector
FEAT             Virtual DN
H                POTS line that is part of a hunt group
HC               Hunt group member with call forward option
IHC              Hunt group member IBN line with call forward option
ILC              IBN line with call forward option
IMC              IBN Multiple Directory Number (MDN) line with call forward option
L                Simple POTS line
M                Attendant console
LC               Simple POTS line with call forward option
MDN              Multiple Directory Number (MDN)
MM               Meet-Me conference (datafill table MMCONF)
P                Multi-party POTS line
SC               Series Completion
SCM              Series Completion for the primary of an MDN group
SDN              Secondary Directory Number
-----------------------------------------------------------------------------------------
-End-




ISDN Shared DNs

Different Logical Terminal Identifiers (LTID) can share DNs on ISDN Basic Rate Interface (BRI) lines.  When this relationship occurs, the DNRESULT field of table DNINV of the shared DN shows one LTID only.  The following rules determine the LTID that appears:

Datafill Sequence

There is no requirement to datafill other tables before table DNINV.

Table Size

As determined by the ACTIVE_DN_SYSTEM parameter, computation of the store requirement depends on the use of the DN systems that follow:

For the North American DN system, table DNINV holds up to 1,000,000 DNs.

For the Universal and Enhanced North American DN systems, when many area code and office code combinations are datafilled on the switch, table DNINV holds up to 1,000,000 DNs.

The maximum tuple for table DNINV depends on the criteria that follows:

North American DN System

The North American DN system is the best system to use when:

When Local Number Portability (LNP) and multiple service providers use this system, the system uses a lot of memory.

A TOFCNO (the index for table TOFCNAME or TOFCNAME entry) is a valid area and office code combination from table TOFCNAME.  Calculate the store required for each TOFCNO (in bytes) with the formula that follows:

(100 + 4,000) * (number of thousand groups)


The maximum store requirement for each TOFCNAME is forty 100-bytes.  The maximum store requirement for a thousand group in a TOFCNAME is 4,000-bytes, with a 100-byte overhead for the TOFCNAME.

The North American DN system is the best when the DN structure is tight because it allocates DNs by blocks of 1,000.

Universal DN System

The Universal DN system uses more store when the system allocates all the possible station codes.  If DNs move across many area codes and office codes, table DNINV uses more memory store.

Note:  The Enhanced North American DN system is like the Universal DN system, except that Enhanced North American uses the 3-3-4 format.  Only the APC load uses the Enhanced North American system.

Calculate the store required (in bytes) for each TOFCNO with the formula that follows:

6 * ([tuple count of DNINV] - [tuple count of DNROUTE]) + 44 * (1 + [number of 1-digit prefixes] + [number of 2-digit prefixes] + [number of 3-digit prefixes] + [number of 4-digit prefixes] + [...]) + 6

Note:  In this formula, the tuple count of DNINV is the tuple count of DNINV for the TOFCNAME.  The tuple count of DNROUTE is the tuple count of DNROUTE for the TOFCNAME.

This formula applies to more than the North American industry (for example, more than a 3-digit prefix or 4-digit station code).  Use this formula for station codes of any length.

The maximum store requirement for each TOFCNAME is one hundred eight 890-bytes.  The maximum store requirement for a thousand group in a TOFCNAME is ten 884-bytes.  This requirement includes a 50-byte overhead for the TOFCNAME.

Datafill Example for Table DNINV

The following table is an example of datafill for DNINV for the Universal DN system.  The example datafill is for the TOFCNO 709 333.  TOFCNO 709 333 contains all station codes with the 102x, 104x format, and a half of the 171x range,  These codes are datafilled against lines.

-----------------------------------------------------------------------------------------
Example of a MAP display:

AREACODE  OFCCODE  STNCODE   DNRESULT
______________________________________________
709       333      1020      L HOST 02 0 05 03
709       333      1021      L HOST 02 0 05 04
709       333      1022      L HOST 02 0 13 06
709       333      1023      L HOST 02 0 13 07 
709       333      1024      L REM3 03 0 00 01 
709       333      1025      L REM3 03 0 00 10 
709       333      1026      L REM3 03 0 01 11 (etc.)
709       333      1040      L REM3 03 0 16 15
709       333      1041      L REM3 03 0 13 26
709       333      1042      L REM3 03 0 13 05 (etc.)
______________________________________________

In total, the TOFCNO holds 25 DNs (not any of which are in table DNROUTE).  The number of prefixes follows:

Calculate the memory impact for the TOFCNAME as follows:

6 * 25 + 44 * (1 + 1 + 2 + 3) + 6 = 464-bytes

In the North American DN system, these DNs exist in the same thousand group (1xxx).  The memory impact for the TOFCNAME is:

(100 + 4,000) * 1 = 4,100-bytes

The following datafill example for table DNINV shows:

-----------------------------------------------------------------------------------------
Example of a MAP display:

AREACODE  OFCCODE  STNCODE   DNRESULT
______________________________________________
613       621      5962      MDN SCA 2 0 
613       621      5963      MDN SCA 3 0 
613       621      5964      MDN CACH 55 1 
613       621      5965      MDN CACH 10 1 
613       621      5966      L EKTS 1 
613       621      5966      L EKTS 1 
613       621      5966      L EKTS 1 
613       621      5966      L EKTS 1
613       621      5967      L ISDN 19         (etc.)
______________________________________________