Description
When a call originates from a line, the associated line tables are read and interpreted. The call then enters the screening tables where digit analysis begins. After some general pre-screening, or pre-translation is performed, the call may progress into more detailed screening based on NPA/NXX digits to determine the path into the designated routing tables for defining the final destination or termination of the call.
Operation
Line-to-line translations can be traced using a simplified block diagram representing the major functions within the translation process, as shown in the following figure:
+++++++++ +++++++++++++ +++++++++++ +++++++++ + Lines + ----> + Screening + ----> + Routing + ----> + Lines + +++++++++ +++++++++++++ +++++++++++ +++++++++
The lines tables contain information about the originator of the call in a DMS-100 switch. These tables have three primary functions:
The screening tables contain the information used to analyze the digits that the DMS-100 switch receives. This screening process tests the digits dialed prior to continuing to the next routing stage, to determine, for example, whether this call is local or non-local.
The screening tables establish the call type based on the digits received. The three basic call types are:
The routing tables route the calls to their final destination. The information found in these tables dictates how and where a call will be completed, or if the call will route to a recorded announcement or treatment.
Translations Table Flow for Line-to-Line Translations
As soon as a line goes off-hook, the associated Line Concentrating Module (LCM) informs the switch that the line went off hook and provides the Line Equipment Number (LEN). The originating line has its LEN stored in table LENLINES. From the data stored in table LENLINES, the switch determines the Directory Number (DN), party and options of the line. If there are features associated with the line, the switch accesses table LENFEAT to determine what these features are.
Field LNATTIDX in table LENLINES points to a tuple in table LINEATTR. The entries in this tuple determine the following:
Verification of the call type is done in table LCASCRCN and its subtable LCASCR and table PFXTREAT.
The call then routes to table STDPRTCT and its subtable STDPRT. The pretranslator route selector entered in subfield PRERTSEL determines how call processing progresses. Information on the valid values for this subfield can be located in the table data schema section of this document.
If the entry in this subfield is N, translations proceeds to table HNPACONT and its subtable HNPACODE. The dialed NXX is located and defined.
Table TOFCNAME defines all the terminating offices in the switch and they are identified by area code and office code. Table DNINV contains the data for all assigned and unassigned DNs. If the DN belongs to a hunt group, tables HUNTGRP and HUNTMEM will be accessed.
The line-to-line translations process is shown in the flowchart that follows on the next page.
Table Flow for a Line-to-Line Call
The following table lists the datafill content used in the flowchart for a call routed between DNs (418) 225-2136 and (418) 225-2164. In the example:
Number Planning Area (NPA) = 418
Calling Line DN = 2252136
Called Line DN = 2252164
Standard Pretranslator = P225
-----------------------------------------------------------------------------------------
Datafill Example for Line-to-Line Translations
Datafill Table Example Data
-----------------------------------------------------------------------------------------
LENLINES RCU0 00 0 03 16 S 0 2252136 DT 1 $
LINEATTR 1 1FR NONE NT NSCR 0 418 P225 P225 NONE 0 NIL NILSFC NILLATA 0
NIL NIL 00 Y AINRESGRP 0 0 $
LCASCRCN 418 P225 ( 3) MAND N
subtable LCASCR 225 226
PFXTREAT MAND DD N DD UNDT
STDPRTCT P225 (1) (65021)
subtable STDPRT 418 418 N DD 0 NA
HNPACONT 418 128 0 (68) (1) (2) (0)
subtable HNPACODE 225 225 DN 418 225
TOFCNAME 418 225
DNINV 418 225 2164 H 11 0
HUNTMEM 11 0 N D 2252164 N
HUNTGRP 11 418 2252164 DNH N N N RCVD N N N N N N 4 $
LENLINES RCU0 00 0 14 04 S 0 2252164 DT 1 $
-----------------------------------------------------------------------------------------
-End-
Datafilling Office Parameters
The following table shows the office parameters used by line-to-line translations. For more information about office parameters, refer to the Office Parameters Reference Manual:
-----------------------------------------------------------------------------------------
Office Parameters Used by Line-to-Line Translations
Table Name Parameter Name Explanation and Action
-----------------------------------------------------------------------------------------
OFCENG ACTIVE_DN_SYSTEM This parameter specifies the type of DNs that
can be used in an office. If this parameter is
set to "NORTH_AMERICAN", the directory number
must use the form NPA-NXX-XXXX. If this
parameter is set to "UNIVERSAL", the directory
number may vary in length.
-continued-
-----------------------------------------------------------------------------------------
Office Parameters Used by Line-to-Line Translations (continued)
Table Name Parameter Name Explanation and Action
-----------------------------------------------------------------------------------------
OFCENG AIN_ACTIVE This parameter controls the activation of the
Advanced Intelligent Network (AIN). Enter "Y"
to activeate AIN software. Enter "N" to
deactivate AIN software. If this parameter
is set to "N", parameter AIN_OFFICE_TRIGGRP
in table OFCVAR is disregarded.
-----------------------------------------------------------------------------------------
OFCVAR AIN_OFFICE_TRIGGRP This parameter is used to subscribe trigger
behaviors on an office-wide basis. The entry
in field AINGRP in table TRIGGRP is entered
here. The default value is "NIL".
-----------------------------------------------------------------------------------------
-End-
Table Datafill Sequence
The following table lists the tables that require datafill to implement line-to-line translations for the calling line. The tables are listed in the order in which they are to be datafilled:
-----------------------------------------------------------------------------------------
Datafill Tables Required for Line-to-Line Translations for the Calling Line
Table Purpose of Table
-----------------------------------------------------------------------------------------
HNPACONT The Home Numbering Plan Area Control table lists all the home or
serving area NPAs for a particular area.
subtable HNPACODE The Home Numbering Plan Area Code subtable lists the route
treatment or table to which the translation routes for each of
the assigned NPAs.
-----------------------------------------------------------------------------------------
STDPRTCT The Standard Pretranslator table lists the names of the standard
pretranslator subtables.
subtable STDPRT The Standard Pretranslator subtable determines the next stage of
translation, based on the range of leading digits.
-----------------------------------------------------------------------------------------
LCASCRCN The Local Calling Area Screening Control table lists the NPA code
and Local Calling Area name and its prefix selector.
subtable LCASCR The Local Calling Area Screening Code subtable determines from the
dialed digits if the call is local or non-local.
-----------------------------------------------------------------------------------------
PFXTREAT The Prefix Treatment table determines the call treatment to which a
call is routed.
-----------------------------------------------------------------------------------------
LINEATTR The Line Attribute table provides pointers to screening and billing
tables and assigns line attributes for digit analysis.
-----------------------------------------------------------------------------------------
LENLINES The Line Assignment table contains the DN, hardware location, and
options associated with the calling line.
-----------------------------------------------------------------------------------------
-End-
The following table lists the tables that require datafill to implement line-to-line translations for the called line. The tables are listed in the order in which they are to be datafilled:
-----------------------------------------------------------------------------------------
Datafill Tables Required for Line-to-Line Translations for the Called Line
Table Purpose of Table
-----------------------------------------------------------------------------------------
TOFCNAME The Terminating Office Name table defines all terminating offices in the
switch.
-----------------------------------------------------------------------------------------
DNINV The Directory Number Inventory table is a read-only table that contains data
for all assigned and unassigned DNs.
-----------------------------------------------------------------------------------------
HUNTGRP The Hunt Group table lists data assignments for each hunt group in the
switching unit.
-----------------------------------------------------------------------------------------
HUNTMEM The Hunt Member table lists the members assigned to the hunt groups.
-----------------------------------------------------------------------------------------
-End-
Datafilling Table HNPACONT
The following table shows the datafill specific to line-to-line translations for table HNPACONT. Only those fields that apply directly to line-to-line translations are shown:
-----------------------------------------------------------------------------------------
Datafilling Table HNPACONT
Subfield or
Field Refinement Entry Explanation and Action
-----------------------------------------------------------------------------------------
STS 0 to 9,999,999 Serving Translation Scheme (STS)
Enter a STS or SNPA code.
-----------------------------------------------------------------------------------------
HNPACODE See note Home Numbering Plan Area (HNPA) Code
This field is an index into subtable
HNPACODE.
Note: This field does not accept any input.
-----------------------------------------------------------------------------------------
-End-
Datafill Example for Table HNPACONT
The following example MAP display shows sample datafill for table HNPACONT:
STS NORTREFS NOAMBIGC RTEREF HNPACODE ATTRIB RTEMAP _________________________________________________________ 418 128 0 ( 68) ( 1) ( 2) ( 0) _________________________________________________________
Datafilling Subtable HNPACONT.HNPACODE
The following table shows the datafill specific to line-to-line translations for subtable HNPACONT.HNPACODE. Only those fields that apply directly to line-to-line translations are shown:
-----------------------------------------------------------------------------------------
Datafilling Subtable HNPACONT.HNPACODE
Subfield or
Field Refinement Entry Explanation and Action
-----------------------------------------------------------------------------------------
FROMDIGS Numeric From Digits
(3 digits) Enter the number representing a single code
or the first in a block of consecutive
codes that have the same input data.
-----------------------------------------------------------------------------------------
TODIGS Numeric To Digits
(3 digits) If field FROMDIGS represents a single code,
enter the same single code as in field FROMDIGS.
If field FROMDIGS represents the first number of
a block of consecutive numbers, enter the last
number in the block.
-----------------------------------------------------------------------------------------
CDRRTMT See subfield Code Type, Route Reference or Treatment
This field consists of subfield CD.
CD DN Code Type
Enter "DN" for terminating office code and
datafill refinements SNPA and NXX.
SNPA Numeric Terminating Serving Numbering Plan Area
(3 digits) Enter the SNPA of the called terminating
line DN. If the operating company uses
screening to intraswitch SNPAs, translation
of the dialed digits proceeds to table
TOFCNAME, using SNPA and NXX as the key.
NXX Numeric Terminating NXX
(3 digits) Enter three digits for the NXX code of the
called terminating line DN.
-----------------------------------------------------------------------------------------
-End-
Datafill Example for Subtable HNPACONT.HNPACODE
The following example MAP display shows sample datafill for subtable HNPACONT.HNPACODE:
FROMDIGS TODIGS CDRRTMT _________________________________________________________ 225 225 DN 418 225 _________________________________________________________
Datafilling Table STDPRTCT
The following table shows the datafill specific to line-to-line translations for table STDPRTCT. Only those fields that apply directly to line-to-line translations are shown:
-----------------------------------------------------------------------------------------
Datafilling Table STDPRTCT
Subfield or
Field Refinement Entry Explanation and Action
-----------------------------------------------------------------------------------------
EXPRTNM Alphanumeric External Standard Pretranslator Subtable Name
(up to 8 Enter the name defined by the operating
characters) company to represent the standard pre-
translator.
-----------------------------------------------------------------------------------------
STDPRT See note Standard Pretranslator
The field is an index into subtable STDPRT.
Note: This field does not accept any input.
-----------------------------------------------------------------------------------------
-End-
Datafill Example for Table STDPRTCT
The following example MAP display shows sample datafill for table STDPRTCT:
EXPRTNM STDPRT AMAPRT _________________________________________________________ P225 ( 1) (65021) _________________________________________________________
Datafilling Subtable STDPRTCT.STDPRT
The following table shows the datafill specific to line-to-line translations for subtable STDPRTCT.STDPRT. Only those fields that apply directly to line-to-line translations are shown:
-----------------------------------------------------------------------------------------
Datafilling Subtable STDPRTCT.STDPRT
Subfield or
Field Refinement Entry Explanation and Action
-----------------------------------------------------------------------------------------
FROMDIGS Numeric From Digits
(up to 18 digits) Enter the digit or digits to be translated.
If the entry represents a block of
consecutive numbers, enter the first number
in the block.
-----------------------------------------------------------------------------------------
TODIGS Numeric To Digits
(up to 18 digits) If field FROMDIGS represents a block of
consecutive numbers, enter the last number
in the block.
-----------------------------------------------------------------------------------------
PRETRTE See subfield Pretranslation Route
This field consists of subfield PRERTSEL
and its refinements TYPECALL, NOPREDIG,
TRANSYS, and POS.
-continued-
-----------------------------------------------------------------------------------------
Datafilling Subtable STDPRTCT.STDPRT (continued)
Subfield or
Field Refinement Entry Explanation and Action
-----------------------------------------------------------------------------------------
PRERTSEL N or NT Pretranslator Route Selector
Enter "N" or "NT".
Enter "NT" for DMS-500 switches only.
TYPCALL DD, OA, NP, Type of Call
or NL Enter the type of call:
DD (Direct Dial)
OA (Operated Assisted)
NP (No Prefix)
NL (nil)
For Traffic Operator Position System (TOPS)
calls, there can be a mixture of 0 and 1
(OA and DD) call types. Enter "NL" for these
cases.
NOPREDIG 0 to 7 Number of Prefix Digits
Enter the number of digits that are to be
interpreted as prefix digits.
TRANSYS NA, IN, or IP Translation System
Enter "IN" if the translation routes to
international translations (on a local and
toll combined switching unit only).
Enter "IP" if the translation routes to
international partitioned translations
(DMS-250 only).
Enter "NA" if the translation routes to
national translations.
-----------------------------------------------------------------------------------------
-End-
Datafill Example for Subtable STDPRTCT.STDPRT
The following example MAP display shows sample datafill for subtable STDPRTCT.STDPRT:
FROMDIGS TODIGS PRETRTE _________________________________________________________ 418 418 N DD 0 NA _________________________________________________________
Datafilling Table LCASCRCN
The following table shows the datafill specific to line-to-line translations for table LCASCRCN. Only those fields that apply directly to line-to-line translations are shown:
-----------------------------------------------------------------------------------------
Datafilling Table LCASCRCN
Subfield or
Field Refinement Entry Explanation and Action
-----------------------------------------------------------------------------------------
NPALOCNM See subfields NPA Local Calling Area Subtable Name
This field consists of subfields STS and
LCANAME.
STS Numeric Serving Translation Scheme
(3 digits) Enter a serving NPA code for the trunk group.
LCANAME Alphanumeric Local Calling Area Name
(up to 4 Enter the key to subtable LCASCRCN.LCASCR.
characters)
-----------------------------------------------------------------------------------------
LCASCR See note Local Calling Area Screening
This field is an index into subtable LCASCR.
Note: This field does not accept any input.
-----------------------------------------------------------------------------------------
PFXSELEC OPTL, MAND or Prefix Selector
Alphanumeric Enter the name of the prefix selector that is
(up to 4 assigned to subtable LCASCR.
characters)
-----------------------------------------------------------------------------------------
-End-
Datafill Example for Table LCASCRCN
The following example MAP display shows sample datafill for table LCASCRCN:
NPALOCNM LCASCR PFXSELEC PFSFOR10 _________________________________________________________ 418 P225 ( 3) MAND N _________________________________________________________
Datafilling Subtable LCASCRCN.LCASCR
The following table shows the datafill specific to line-to-line translations for subtable LCASCRCN.LCASCR. Only those fields that apply directly to line-to-line translations are shown:
-----------------------------------------------------------------------------------------
Datafilling Subtable LCASCRCN.LCASCR
Subfield or
Field Refinement Entry Explanation and Action
-----------------------------------------------------------------------------------------
FROMDIGS Numeric From Digits
(3 digits) Enter the three-digit local NNX code.
This number represents a single code or
the first in a block of consecutive local
NNX codes.
-----------------------------------------------------------------------------------------
-continued-
-----------------------------------------------------------------------------------------
Datafilling Subtable LCASCRCN.LCASCR (continued)
Subfield or
Field Refinement Entry Explanation and Action
-----------------------------------------------------------------------------------------
TODIGS Numeric To Digits
(3 digits) If field FROMDIGS represents the first
number of a block of consecutive local NNX
codes, enter the last NNX code in the block.
If field FROMDIGS represents a single local
NNX code, enter the NNX code entered in
FROMDIGS.
-----------------------------------------------------------------------------------------
-End-
Datafill Example for Subtable LCASCRCN.LCASCR
The following example MAP display shows sample datafill for subtable LCASCRCN.LCASCR:
FROMDIGS TODIGS _________________________________________________________ 225 226 _________________________________________________________
Datafilling Table PFXTREAT
The following table shows the datafill specific to line-to-line translations for table PFXTREAT. Only those fields that apply directly to line-to-line translations are shown:
-----------------------------------------------------------------------------------------
Datafilling Table PFXTREAT
Subfield or
Field Refinement Entry Explanation and Action
-----------------------------------------------------------------------------------------
TYPLCLCD See subfields Type of Call and Local Code
This field consists of subfields PFXSELEC,
TYPCALL, and LOCAL.
PFXSELEC OPTL, MAND, Prefix Selector
or Alphanumeric Enter the prefix selector.
(up to 4
characters)
TYPCALL DD, NP, OA, Type of Call
or NL Enter the type of call:
DD (Direct Dial)
OA (Operated Assisted)
NP (No Prefix)
NL (nil)
-----------------------------------------------------------------------------------------
-End-
Datafill Example for Table PFXTREAT
The following example MAP display shows sample datafill for table PFXTREAT:
TYPLCLCD UPDTYPCA TREAT _________________________________________________________ MAND DD N DD UNDT _________________________________________________________
Datafilling Table LINEATTR
The following table shows the datafill specific to line-to-line translations for table LINEATTR. Only those fields that apply directly to line-to-line translations are shown:
-----------------------------------------------------------------------------------------
Datafilling Table LINEATTR
Subfield or
Field Refinement Entry Explanation and Action
-----------------------------------------------------------------------------------------
LNATTIDX 0 to 31,999 Line Attribute Index
Enter the index into table LINEATTR.
-----------------------------------------------------------------------------------------
SCRNCL Alphanumeric Class of Service Screening
(up to 4 If screening by class of service is
characters required, enter the key to the class of
or NSCR) service subtable assigned to the line
attribute index. If screening by class of
service is not required, enter "NSCR".
-----------------------------------------------------------------------------------------
STS Numeric Serving Translation Scheme (STS)
(3 digits) Enter the SNPA assigned to the line
attribute index. The STS of an existing
tuple cannot be changed.
-----------------------------------------------------------------------------------------
PRTNM Alphanumeric Standard Pretranslator Subtable Name
(up to 4 If pretranslation of digits is required,
characters enter the key to the standard pretranslator
or NPRT) subtable assigned to the line attribute index.
If standard pretranslation is not required,
enter "NPRT".
-----------------------------------------------------------------------------------------
LCANAME Alphanumeric Local Calling Area Screening Subtable Name
(up to 4 If screening of local central office codes
characters (NNX) is required, enter the key to the local
or NLCA) calling area subtable assigned to the line
attribute index. If screening of local NNX
codes is not required, enter "NLCA".
-----------------------------------------------------------------------------------------
-End-
Datafill Example for Table LINEATTR
The following example MAP display shows sample datafill for table LINEATTR:
LNATTIDX LCC CHGCLSS COST SCRNCL LTG STS PRTNM LCANAME ZEROMPOS TRAFSNO MRSA SFC LATANM MDI IXNAME DGCLNAME FANIDIGS RESINF OPTIONS __________________________________________________________________________________ 1 1FR NONE NT NSCR 0 418 P225 P225 NONE 0 NIL NILSFC NILLATA 0 NIL NIL 00 Y AINRESGRP 0 0 $ __________________________________________________________________________________
Datafilling Table LENLINES
The following table shows the datafill specific to line-to-line translations for table LENLINES. Only those fields that apply directly to line-to-line translations are shown:
-----------------------------------------------------------------------------------------
Datafilling Table LENLINES
Subfield or
Field Refinement Entry Explanation and Action
-----------------------------------------------------------------------------------------
LEN See subfields Line Equipment Number (LEN)
This field defines the physical location
of the equipment that is connected to a
specific telephone line.
Note: Field LEN consists of
subfields SITE, FRAME, UNIT, DRAWER or LSG,
SHELF, SLOT and CIRCUIT.
-----------------------------------------------------------------------------------------
PTY R1 to R5, T1 Party and Ringing Combination
to T5 or S If the line is assigned to a two-, four-,
eight-, or ten-party line, enter the party,
"R1" to "R5" or "T1" to "T5", of the DN
assigned to the line. If the line is
assigned to an individual line, enter
"S" for single party.
-----------------------------------------------------------------------------------------
LNATTIDX 0 to 4,095 Line Attribute Index
Enter the index into table LINEATTR.
-----------------------------------------------------------------------------------------
-End-
Datafill Example for Table LENLINES
The following example MAP display shows sample datafill for table LENLINES:
LEN PTY RINGCODE DN
SIGTYPE LNATTIDX OPTLIST
_________________________________________________________
RCU0 00 0 03 16 S 0 2252136
DT 1 $
_________________________________________________________
Datafilling Table TOFCNAME
The following table shows the datafill specific to line-to-line translations for table TOFCNAME. Only those fields that apply directly to line-to-line translations are shown:
-----------------------------------------------------------------------------------------
Datafilling Table TOFCNAME
Subfield or
Field Refinement Entry Explanation and Action
-----------------------------------------------------------------------------------------
AREACODE 0 to 9,999,999 Area Code
The area code identifies a major geographical
area served by the switch. This field can
contain one to seven digits. In a North
American office, the area code must be three
digits in length.
Enter an area code that has been defined
in table SNPANAME or table HNPACONT.
-----------------------------------------------------------------------------------------
OFCCODE 0 to 9,999,999 Office Code
or $ The office code is a subregion of the area
code. It can have zero to seven digits.
In a North American office, the office code
must be three digits in length.
-----------------------------------------------------------------------------------------
-End-
Datafill Example for Table TOFCNAME
The following example MAP display shows sample datafill for table TOFCNAME:
AREACODE OFCCODE _________________________________________________________ 418 225 _________________________________________________________
Datafilling Table DNINV
Table DNINV contains the data for all assigned and unassigned DNs. Table DNINV is a read-only table. Information is added to it as DNs are assigned or used in other tables such as LENLINES.
The following table shows the datafill specific to line-to-line translations for table DNINV. Only those fields that apply directly to line-to-line translations are shown:
-----------------------------------------------------------------------------------------
Datafilling Table DNINV
Subfield or
Field Refinement Entry Explanation and Action
-----------------------------------------------------------------------------------------
AREACODE 0 to 9,999,999 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.
-----------------------------------------------------------------------------------------
-continued-
-----------------------------------------------------------------------------------------
Datafilling Table DNINV (continued)
Subfield or
Field Refinement Entry Explanation and Action
-----------------------------------------------------------------------------------------
OFCCODE 0 to 9,999,999 Office Code Digit Register
(1 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.
-----------------------------------------------------------------------------------------
STNCODE 0 to 99,999,999 Station Code
(1 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 area
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.
-----------------------------------------------------------------------------------------
-End-
Datafill Example for Table DNINV
The following example MAP display shows sample datafill for table DNINV:
AREACODE OFCCODE STNCODE DNRESULT _________________________________________________________ 418 225 2164 H 11 0 _________________________________________________________
Datafilling Table HUNTGRP
Table HUNTGRP is datafilled if the called line belongs to a hunt group.
The following table shows the datafill specific to line-to-line translations for table HUNTGRP. Only those fields that apply directly to line-to-line translations are shown:
-----------------------------------------------------------------------------------------
Datafilling Table HUNTGRP
Subfield or
Field Refinement Entry Explanation and Action
-----------------------------------------------------------------------------------------
HTGRP 0 to 8,191 Hunt Group Number
Enter the hunt group number assigned
to the hunt group.
-----------------------------------------------------------------------------------------
DN Numeric Directory Number
(up to 15 digits) Enter the listed DN of the hunt group.
-----------------------------------------------------------------------------------------
-continued-
-----------------------------------------------------------------------------------------
Datafilling Table HUNTGRP
Subfield or
Field Refinement Entry Explanation and Action
-----------------------------------------------------------------------------------------
GRPTYP DNH Hunt Group Type
Enter DNH and datafill refinement TRMOPT.
-----------------------------------------------------------------------------------------
GRPDATA TRMBOPT Y or N Terminating Billing Option
If the optional terminator software package
is provided, and if a record is generated
for each call to a member of the hunt group,
enter "Y". Otherwise, enter "N".
-----------------------------------------------------------------------------------------
-End-
Datafill Example for Table HUNTGRP
The following example MAP display shows sample datafill for table HUNTGRP:
HTGRP SNPA DN GRPTYP GRPDATA _________________________________________________________ 11 418 2252164 DNH N N N RCVD N N N N N N 4 $ _________________________________________________________
Datafilling Table HUNTMEM
Table HUNTMEM is datafilled if the called line belongs to a hunt group.
The following table shows the datafill specific to line-to-line translations for table HUNTMEM. Only those fields that apply directly to line-to-line translations are shown:
-----------------------------------------------------------------------------------------
Datafilling Table HUNTMEM
Subfield or
Field Refinement Entry Explanation and Action
-----------------------------------------------------------------------------------------
HTGRP 0 to 8,191 Hunt Group Number Key
Enter the hunt group number to which
the member belongs.
-----------------------------------------------------------------------------------------
HTMDATA See subfield Hunt Member Data
This field consists of subfield SEL.
SEL B, D, L or P Select Hunt Group Type
Enter one of the following:
B = Bridged Night Number
D = Directory Number
L = Multiline or Distributed Line
P = Multiple Position
If the entry in this field is "D", complete
subfields DN and BNNDAT.
-continued-
-----------------------------------------------------------------------------------------
Datafilling Table HUNTMEM (continued)
Subfield or
Field Refinement Entry Explanation and Action
-----------------------------------------------------------------------------------------
DN Numeric Directory Number
(up to 15 digits) Enter the DN assigned to the hunt
group sequence number.
-----------------------------------------------------------------------------------------
-End-
Datafill Example for Table HUNTMEM
The following example MAP display shows sample datafill for table HUNTMEM:
HTGRP SEQNO INSERT HTMDATA _________________________________________________________ 11 0 N D 2252164 N _________________________________________________________
Translation Verification Tools
The following example shows the output from the TRAVER command when it is used to verify line-to-line translations between DNs (406) 335-0691 to (406) 335-8692:
----------------------------------------------------------------------------------------- >TRAVER l 3350691 3358692 b TABLE LINEATTR 10 1FR NONE NT NSCR 7 406 P329 P329 NONE 0 NIL NILSFC NILLATA 0 NIL NIL 00 N $ LCABILL OFF - BILLING DONE ON BASIS OF CALLTYPE TABLE DNATTRS TUPLE NOT FOUND TABLE DNGRPS TUPLE NOT FOUND TABLE LENFEAT TUPLE NOT FOUND TABLE OFCVAR AIN_OFFICE_TRIGGRP OFCTRIG AIN Orig Attempt TDP: no subscribed trigger. TABLE STDPRTCT P329 ( 1) (65021) 0 . SUBTABLE STDPRT WARNING: CHANGES IN TABLE STDPRT MAY ALTER OFFICE BILLING. CALL TYPE DEFAULT IS NP. PLEASE REFER TO DOCUMENTATION. . 335 336 N NP 0 NA . SUBTABLE AMAPRT . KEY NOT FOUND . DEFAULT VALUE IS: NONE OVRNONE N TABLE HNPACONT 406 128 0 ( 69) ( 1) ( 2) ( 0) 0 . SUBTABLE HNPACODE . 335 335 DN 406 335 AIN Info Collected TDP: no subscribed trigger. TABLE TRIGGRP OFCTRIG INFOANAL . N11 ( DG N11DIG)$ NIL . PODP ( DG PODPDIG)$ NIL AIN Network Busy TDP: trigger criteria met,querying the database if network is busy. TABLE TOFCNAME 406 335 TABLE DNINV 406 335 8692 L HOST 00 0 01 01 AIN Term Attempt TDP: no subscribed trigger. TABLE DNATTRS TUPLE NOT FOUND TABLE DNGRPS TUPLE NOT FOUND TABLE LCASCRCN 406 P329 ( 3) MAND N . SUBTABLE LCASCR . 335 336 TABLE PFXTREAT MAND NP Y NP UNDT +++ TRAVER: SUCCESSFUL CALL TRACE +++ DIGIT TRANSLATION ROUTES 1 LINE 4063358692 ST TREATMENT ROUTES. TREATMENT IS: GNCT 1 *OFLO 2 LKOUT +++ TRAVER: SUCCESSFUL CALL TRACE +++ ----------------------------------------------------------------------------------------- -End-
The following example shows the output from the TRAVER command when it is used to verify line-to-line translations between DNs (418) 225-2136 and (418) 225-2164, where the called number belongs to a hunt group.
----------------------------------------------------------------------------------------- >TRAVER l 2252136 2252164 b TABLE LINEATTR 1 1FR NONE NT NSCR 0 418 P225 P225 NONE 0 NIL NILSFC LATA1 0 NIL NIL 00 Y AINRESGRP 0 0 $ LCABILL OFF - BILLING DONE ON BASIS OF CALLTYPE TABLE DNATTRS TUPLE NOT FOUND TABLE DNGRPS TUPLE NOT FOUND TABLE LENFEAT TUPLE NOT FOUND TABLE OFCVAR AIN_OFFICE_TRIGGRP OFCTRIG AIN Orig Attempt TDP: no subscribed trigger. TABLE STDPRTCT P225 ( 1) (65021) 0 . SUBTABLE STDPRT WARNING: CHANGES IN TABLE STDPRT MAY ALTER OFFICE BILLING. CALL TYPE DEFAULT IS NP. PLEASE REFER TO DOCUMENTATION. . 225 225 L NP 0 418 225 AIN Info Collected TDP: no subscribed trigger. TABLE TRIGGRP OFCTRIG INFOANAL . N11 ( DG N11DIG)$ NIL . PODP ( DG PODPDIG)$ NIL AIN Info Analyzed TDP: trigger criteria not met. TABLE TOFCNAME 418 225 TABLE DNINV 418 225 2164 H 11 0 AIN Term Attempt TDP: no subscribed trigger. TABLE DNATTRS TUPLE NOT FOUND TABLE DNGRPS TUPLE NOT FOUND TABLE HUNTGRP 11 418 2252164 DNH N N N RCVD N N N N N N 4 $ TABLE HUNTMEM 11 0 N D 2252164 N . SUBTABLE AMAPRT . KEY NOT FOUND . DEFAULT VALUE IS: NONE OVRNONE N LATA IS NIL, THEREFORE NOT AN EQUAL ACCESS CALL +++ TRAVER: SUCCESSFUL CALL TRACE +++ AIN Network Busy TDP: trigger criteria met, querying the database if network is busy. DIGIT TRANSLATION ROUTES 1 LINE 4182252164 ST TREATMENT ROUTES. TREATMENT IS: GNCT 1 *OFLO 4 LKOUT +++ TRAVER: SUCCESSFUL CALL TRACE +++ ----------------------------------------------------------------------------------------- -End-