DMS-100 Directory Number Route (DNROUTE) |
Table Name
Directory Number Route
Functional Description of Table DNROUTE
Table DNROUTE lists information for programmable Directory Numbers (DN) in the switch (such as a DN that identifies a route), rather than Line Equipment Numbers (LEN). Table DNROUTE replaces table WRDN (Write Directory Number).
Table DNROUTE associates a DN with a specific trunk group member. This DN specifies the lowest numbered DS-0 on the Customer Premises Equipment (CPE) on which a wideband call must terminate. Given the lowest numbered DS-0 and the bandwidth, the incoming wideband call is connected to the CPE.
There are many variations of input for table DNROUTE, as shown in the table below. Selectors not described in the table that follows are not valid entries for table DNROUTE.
----------------------------------------------------------------------------------------------
DNROUTE Features
DN Selector Usage
----------------------------------------------------------------------------------------------
D Treatment
DSVC Default Service
M Listed Directory Number
MM Meet-Me Conference
RSDT Restricted Dial Tone
SYN Synonym Directory Number
T Route List
FEAT Automatic Call Distribution (ACD)
FEAT Advanced Intelligent Network (AIN)
FEAT Automatic Set Relocation (ASR)
FEAT Call Forward/Interface Busy
FEAT Direct Inward System Access (DISA)
FEAT Message Center DN (MCDN)
FEAT Message Storage and Retrieval (MSR)
FEAT Meet-Me Conference (MEETME)
FEAT Meridian Offnet Access (MONA)
FEAT Mobile Directory Number Trigger (MTXDNTRIG)
FEAT Simultaneous Ringing (SIMRING) Virtual DN
FEAT Subscriber Programmable Ringing for CFDA (SPRING) - Option RCTL (Ring Control)
FEAT Suppressed Ringing Access (SRA)
FEAT Uniform Call Distribution (UCD)
----------------------------------------------------------------------------------------------
Note 1: The selectors C, H, L, P, HC, LC, A, ILC, IHC, MDN, IMC, SDN, SC, ACDTK,
and SCM are listed in field DN_SEL. These selectors are not valid
entries for table DNROUTE.
----------------------------------------------------------------------------------------------
Note 2: Selector MTXDNTRIG only applies to the DMS-100 Wireless switch.
----------------------------------------------------------------------------------------------
Tuples for feature Meet-Me Conference are no longer applicable to table DNROUTE. The Meet-Me Conference data is datafilled in table MMCONF (Meet-Me Conference), and the Meet-Me DN information is stored in table DNINV (Directory Number Inventory).
Datafill Sequence & Implications
The following tables must be datafilled before table DNROUTE:
During the One Night Process (ONP), table TABXFR (Table Tansfer) detects DNTRIGGER datafill. The detection does not allow transfer of DNTRIGGER datafill to the inactive side.
The following restrictions apply to the Default Service (DSVC) selector, which identifies a DN in table DNROUTE as a Default Service DN:
Table Size
0 to 640,000 tuples
If office parameter ACTIVE_DN_SYSTEM in table OFCENG is set to North American, the maximum size is 640,000 tuples.
If office parameter ACTIVE_DN_SYSTEM in table OFCENG is set to Universal, the maximum size is 500,000 tuples.
Note: Tables DNROUTE and DNINV use the same physical store. The maximum size of table DNROUTE is less than or equal to table DNINV.
The maximum number of Advanced Intelligent Network (AIN) tuples that can be datafilled is 2,048.
Datafill
The following table describes datafill for table DNROUTE:
----------------------------------------------------------------------------------------------
Table DNROUTE Field Descriptions
Field Subfield Entry Explanation and Action
----------------------------------------------------------------------------------------------
AREACODE 0 to 9999999 Area Code
(1 to 7 digits) The area code identifies a major geographical
area served by the switch. If office parameter
ACTIVE_DN_SYSTEM in table OFCENG is set to
"North American," the area code must be three
digits long.
----------------------------------------------------------------------------------------------
OFCCODE 0 to 9999999 Office Code Digit Register
(0 to 7 digits) The office code is a subregion of the area code.
If office parameter ACTIVE_DN_SYSTEM in table
OFCENG is set to "North American," the area code
must be three digits long. The office code must
be specified in table TOFCNAME.
Tuples can be added if the value of field OFCCODE
is "$" as specified in table TOFCNAME.
They cannot contain STNCODEs whose leading digits
are an OFCCODE in the same area code.
----------------------------------------------------------------------------------------------
STNCODE 0 to 99999999 Station Code
(up to 8 digits) The station code identifies a unique station
within the terminating office (TOFC). If office
parameter ACTIVE_DN_SYSTEM in table OFCENG is set
to "North American," the STNCODE code must be one
or four digits in length. If one digit is
entered, it is treated as a D-digit, where the
D-digit represents the fourth digit in the format
ABC-DEFG.
A D-digit is then given the appropriate DN result.
For example, if area code 613 and office code 226
are entered, and if "5" is entered as the station
code, any calls to a number beginning with
6132265 are automatically routed to the specified
treatment. If "5" is the D-digit, and DNROUTE is
datafilled as "613 226 5 D OPRT", any numbers for
6132265 are routed to the operator treatment as
set in table TMTCNTL.
Ambiguity within the STNCODEs of one TOFC is not
permitted. For example, 8594 and 859 cannot be
specified as STNCODEs within one TOFC.
Note: The STNCODE is in DEFG format.
----------------------------------------------------------------------------------------------
XLAPLAN Alphanumeric Translation Plan Index
(up to 16 Enter the index into the XLAPLAN table.
characters)
----------------------------------------------------------------------------------------------
RATEAREA Alphanumeric Area Code
(up to 16 Enter the index into the RATEAREA table.
characters)
----------------------------------------------------------------------------------------------
-End-
Error Messages
The following table explains error messages that can occur when you attempt to datafill table DNROUTE.
Note: You cannot assign a Public Office Directory Number (PODN) when Software Optionality Control option LNP00200 is IDLE.
---------------------------------------------------------------------------------------------- Message Explanation User Action ---------------------------------------------------------------------------------------------- ERROR: PODN may not be SOC option LNP00200 Activate SOC option LNP00200. assigned when Software is in the IDLE state. Assign the PODN again. Optionality Control option LNP00200 is IDLE. ----------------------------------------------------------------------------------------------
Note: When an "Unable To Write New Data" error message is displayed at the MAP terminal, an add or change operation to table DNROUTE was unsuccessful. When the add operation fails, no tuple is written to table DNROUTE. When a change operation fails, the existing tuple in table DNROUTE remains unchanged.