Oqcqprof Scalltab

Critical Release Notice
Publication number: 297-8021-351

Publication release: Standard 10.05
Attention!
*************************************************************************
The North America DMS-100 Data Schema Reference Manual, 297-8021-351, will
continue to be updated and provided in the North America - DMS NTP collection.
*************************************************************************
The content of this customer NTP supports the SN07 (DMS)

software release.
Bookmarks used in this NTP highlight the changes between the NA015 baseline and the current release.
The bookmarks provided are color-coded to identify release-specific content changes. NTP volumes that
do not contain bookmarks indicate that the NA015 baseline remains unchanged and is valid for the current
release.
Bookmark Color Legend

Black: Applies to content for the NA015 baseline that is valid through the current release.
Red: Applies to new or modified content for NA017 that is valid through the current release.
Blue: Applies to new or modified content for NA018 (SN05 DMS) that is valid through the current
release.
Green: Applies to new or modified content for SN06 (DMS) that is valid through the current
release.
Purple : Applies to new or modified content for SN07 (DMS) that is valid through the current
release.
Attention!
Adobe Acrobat Reader 5.0 or higher is required to view bookmarks in color.
Publication History
Note: Refer to the NA015 baseline document for Publication History prior to the NA017
software release.
January 2006
Standard release 10.05 for software release SN07 (DMS). Updates made in the North
American Data Schema Reference Manual are shown below
Volume 6
Modified data schema IPNETWRK (Q01227402)
Volume12
Deleted the term TBD, which occurred in two places in this volume.
October 2005
Standard release 10.04 for software release SN07 (DMS). Updates made in the North
American Data Schema Reference Manual are shown below
Volume 2
Table BEARNETS description added for CR Q01083765.
Volume 3
Table DESDATA description added for CR Q01083765.
Volume 4
Table DPTRKMEM was created as part of activity A59015739 in an earlier release.
Documentation updated for CR Q01083781.
Volume 5
Table IHEADRR description added for CR Q01083765.
Volume 8
Table NET2NET description added for CR Q01083765
Table NETBRDGE description added for CR Q01083765
Table NETPATH description added for CR Q01083765
Volume 9
Table PCEMENTT was created as part of activity A00007196 in an earlier release.
Table PCEMFEID was created as part of activity A00007196 in an earlier release.

Table PRSUDATA description added for CR Q01083765.

Table PVDNCHAN description modified for CR Q00806759/Q01207784
Volume 10
Table SELDEFS and table SETDEFS descriptions added for CR Q01083765.
December 2004
Standard release 10.03 for software release SN07 (DMS). Updates made in the North America
Data Schema Reference Manual are shown below
Volume 9
Table PECINV amended for CR Q00900178
Volume 1
AINPRESC (new), ACDENLOG, ACDGRP, ACDLOGIN, ANNS
Volume 2
No changes
Volume 3
CMIPADDR, CUSTSTN option AINDENY
Volume 4
No changes
Volume 5
IBNFEAT feature ACD, IBNFEAT feature SUPR
Volume 6
IPAPPL (new), KSETFEAT feature SUPR, KSETFEAT feature IPCLIENT, KSETLINE feature
ACD
Volume 7
No changes
Volume 8
MULTITM (new), OAFUNDEF, OANODINV
Volume 9
PADDATA, QMSMIS
Volume 10
No changes
Volume 11
TOPSFTR, TOPTDROP, TRIGINFO, TRIGITM, TRKAIN
Volume 12
No changes
September 2004
Preliminary release 10.01 for software release SN07 (DMS). Updates made in the North America
Volume 1
ACDENLOG, ACDGRP, ACDLOGIN
Volume 2
AUTHCDE
Volume 3
CUSTN, CUSTN option VOWDN (new)
Volume 4
DIRPOOL2 (new), DIRPPOOL, DNROUTE, DNROUTE feature VOWDN (new)
Volume 5
IBNFEAT feature ECM, IBNXLA
Volume 6
ISUPTRK, KSETFEAT feature ECM
Volume 7
LIUINV, LTCINV, MNHSCARR, MSCIDMAP (new), MSCINMAP (new)
Volume 8
MUMRTAB
Volume 9
RESFEAT
Volume 10
TDBDAOPT, TMTMAP
Volume 11
TOLLTRKS, TOPSFTR, TOPSPARM, TOPSTLDN
Volume 12
TRKOPTS, VOWINV (new), XLABILL (new), XLACLASS (new)
March 2004
Data Schema Reference Manual are shown below.
Volume 1
DCA references changed / made obsolete
Volume 2
CARRMTC, C7UPTMR
Volume 3
DCA references changed / made obsolete
Volume 4
DNROUTE, DNROUTE feature DISA
Volume 5-6
No changes
Volume 7
LNPOPTS, LTDATA
Volume 8
OPTOPT
Volume 9
PADDATA, RDTINV
Volume 10
SUSHELF, SYNCLK, DCA references changed / made obsolete
Volume 11-12
No changes
September 2003
Volume 1
No changes
Volume 2
BCCODES
Volume 3
CSEDPMAP
Volume 4
DSLIMIT, FNPACONT.RTEREF
Volume 5
HNPACONT.RTEREF, IBNFEAT feature MWT, IBNLINES option MDN, IBNLINES option

STN, IBNRTE selector CND, IBNRTE selector NOT, IBNXLA, IBNXLA selector FTR type
LSPKP
Volume 6
ISDNPARM, ISERVOPT, KSETLINE
Volume 7
LENLINES, LTCINV, MNMGPIP
Volume 8
OFRT selector CND, OFRT selector NOT
Volume 9
No changes
Volume 10
STDPRTCT.STDPRT selector E911
Volume 11
TODHEAD, TONES, TRKGRP E911, TRKGRP type IT
Volume 12
TRKOPTS, VFGDATA, VIRGRPS
June 2003
Preliminary release 09.01 for software release SN06 (DMS). Updates made in the North America
Volume 1
ACRTE, ALMSC, ALMSCGRP, ALMSD, ALDSDGRP, ANNAUDID (new), ANNMEMS,
ANNPHLST (new)
Volume 2
No changes
Volume 3
CSEDPMAP (new), CUSTN option CFIND, DEFDATA
Volume 4
FNPACONT
Volume 5
HNPACONT, IBNFEAT feature CFIND, IBNLINES, IBNRTE selector CND, IBNRTE selector
NOT
Volume 6
ISERVOPT, KSETLINE
Volume 7
LRGPINV (new), LTDATA, MNCKTPAK, MNIPPARM (new), MNNODE
Volume 8
OFRT selector CND, OFRT selector NOT
Volume 9
PADDATA, REXSCHED
Volume 10
SERVSINV, SPMECAN, SPMLDVAL (new), STDPRTCT.STDPRT selector E911
Volume 11
TODHEAD, TONES, TRKGRP E911, TRKGRP type IT
Volume 12
TRKMEM, TRKOPTS, TRKSGRP, VFGDATA, VIRTGRPS
This page is intentionally blank.
297-8021-351
DMS-100 Family
North American DMS-100
Customer Data Schema Reference Manual Volume 9 of 12
Data Schema OQCQPROF-SCALLTAB
LET0015 and up Standard 05.02 May 2001

DMS-100 Family

Product release: LET0015 and up
Document release: Standard 05.02
Date: May 2001
Copyright 1996-2001 Nortel Networks,

All Rights Reserved
Printed in the United States of America
NORTEL NETWORKS CONFIDENTIAL: The information contained herein is the property of Nortel Networks and is
strictly confidential. Except as expressly authorized in writing by Nortel Networks, the holder shall keep all information contained
herein confidential, shall disclose the information only to its employees with a need to know, and shall protect the information, in
whole or in part, from disclosure and dissemination to third parties with the same degree of care it uses to protect its own
confidential information, but with no less than reasonable care. Except as expressly authorized in writing by Nortel Networks, the
holder is granted no rights to use the information contained herein.
Information is subject to change without notice. Nortel Networks reserves the right to make changes in design or components as
progress in engineering and manufacturing may warrant. Changes or modification to the DMS-100 without the express consent of
Nortel Networks may void its warranty and void the users authority to operate the equipment.
Nortel Networks, the Nortel Networks logo, the Globemark, How the World Shares Ideas, Unified Networks, DMS, DMS-100,
Helmsman, MAP, Meridian, Nortel, Northern Telecom, NT, SuperNode, and TOPS are trademarks of Nortel Networks.
iii
Contents
NTP Summary Contents vii
1 Data schema tables 1-1

OQCQPROF 1-2
ORIGRC 1-8
OSCVLGRP 1-11
OSIPARMS 1-14
OSIROUTE 1-22
OSNCCAP 1-28
OSSCAT 1-31
OSSPROV 1-40
OVSBILL 1-43
OVSCC 1-46
OVSCCYL 1-48
OVSRS 1-50
OVSRSI 1-53
OWATZONE 1-54
OWNER 1-59
OWNTAB 1-62
PACMAN 1-65
PADDATA 1-69
PADNDEV 1-87
PARSDENY 1-89
PARSMBR 1-91
PATALARM 1-93
PATCHOPT 1-97
PATCTRL 1-100
PATNS 1-105
PATSET 1-108
PCIC 1-113
PECINV 1-115
PFCTRL 1-120
PFXTREAT 1-125
PHDS1 1-128
PHINFO 1-130
DMS-100 Family NA100 Customer Data Schema Reference Manual Volume 9 of 12 LET0015 and up
iv Contents
PHINV 1-157
PICNAME 1-162
PILOTGRP 1-164
PINDATA 1-167
PKTVPROF 1-169
PLATAB 1-172
PMEXCEPT 1-175
PMLOADS 1-177
PMNODES 1-182
PODPATTR 1-187
PORTNUMS 1-191
POSITION 1-194
POSITION route selector C 1-198
POSITION route selector S 1-201
POSITION route selector T 1-203
POSNAME 1-205
PRECONF 1-208
PREFHUNT 1-220
PREPLANS 1-224
PRIPROF 1-234
PRTN2CCD 1-239
PRTTONET 1-241
PS 1-243
PSCNUM 1-247
PSNAILUP 1-249
PSTNTRK 1-257
PTIDTAB 1-259
PTP 1-262
PVCINFO 1-264
PVCTYPE 1-273
PVDNAGEN 1-276
PVDNCHAN 1-288
PVDNCUST 1-290
PVDNCUST.AGENTS 1-292
PVDNCUST.CONNECT 1-294
PXCODE 1-297
PXHEAD 1-298
PXLAMAP 1-299
PXRTE 1-305
QAPLNDEF 1-306
QDEF 1-312
QMSCQDEF 1-314
QMSMIS 1-324
QMSTOPS 1-333
QPROFILE 1-336
QPROP 1-338
QT0-QT5H 1-345
QT0-QT5L 1-347
QTHRESH 1-349
QTTIDXH 1-353
QTTIDXL 1-357
297-8021-351 Standard 05.02 May 2001

Contents v
R2BILSRV 1-358
R2PROT including FDCP 1-362
RADR 1-370
RAO 1-374
RAOCHECK 1-376
RASLAPPL 1-378
RATEAREA 1-387
RATEMOD 1-390
RBKMAP 1-399
RBKMAPI 1-402
RBKSET 1-403
RBKSETI 1-415
RCCINV 1-416
RCCPSINV 1-438
RCFCLI 1-443
RCNAME 1-445
RCSINV 1-448
RCTALM 1-461
RCTINV 1-465
RCUALRMS 1-472
RCUINV 1-477
RDTINV 1-496
RDTLT 1-532
REASONS 1-542
RECEIVER 1-548
REGNUM 1-554
REMNACD 1-556
REMOTLAC 1-558
REPLCODE 1-561
REPLNAME 1-563
REROUTE 1-566
REROUTE.NWMRROUT 1-567
RESFEAT 1-571
RESGROUP 1-596
RESINV 1-599
RESMEM 1-604
RESOFC 1-606
RESTAMA 1-645
RESTBIL 1-647
REXINTEN 1-651
REXSCHED 1-653
RGSIGSYS 1-662
RGSIGSYS type MF3 1-665
RGSIGSYS type MFCR2 1-676
RGSIGSYS type NTRS03 1-685
vi Contents
RLOGCLAS 1-736
RLOGDEV 1-739
RLOGTAB 1-742
RMCONFIG 1-745
RMMINV 1-749
RMPCKT 1-758
RNDING 1-762
ROTLCB 1-766
ROTLSCSD 1-769
ROUND 1-772
ROUNDI 1-776
ROUTEMAP 1-777
RSDTLINE 1-779
RSFOR 1-785
RSLOC 1-787
RSM 1-789
RSNAT 1-791
RSSERV 1-794
RSSERVI 1-797
RTECHAR 1-800
RTSALGO 1-808
RTSNT 1-811
SAAUTO 1-814
SACB 1-819
SACODES 1-823
SAIDOFC 1-825
SAQSIZE 1-827
SASPEC 1-830
SATOVER 1-834
SAUSERS 1-837
SCAICOMS 1-842
SCAIGRP 1-849
SCAILNKS 1-853
SCAIPROF 1-856
SCAISSRV 1-860
SCALLTAB 1-925
297-8021-351 Standard 05.02 May 2001

vii
NTP Summary Contents

Data Schema AABSFILT-ATTSCHED

Data Schema AUDALARM-CCVPARMS

Data Schema CDACCESS-DFINV

Data Schema DGCODE-FTRGMEMS

Data Schema FTRGOPTS-INWTMAP

Data Schema IOC-LENFEAT feature WML

Data Schema LENLINES-MSRTAB

Data Schema MTAHORIZ-OPTOPT


Data Schema SCCPTMR-TMZONE
viii NTP Summary Contents

Data Schema TODHEAD-TRKGRP type NU

Data Schema TRKGRP type OC-ZONEORDR
297-8021-351 Standard 05.02 May 2001

1-1
1 Data schema tables

The following pages contain the data schema tables.
1-2 Data schema tables
OQCQPROF
Table name
Operator Services System Advanced Intelligent Network Queue Management
System Call Queue Profile
Functional description
Table OQCQPROF associates lists of OSSAIN QMS call queues with a call
queue profile number. Session pools can then be associated with one of those
profile numbers in table OASESNPL.
This table is very similar to its TOPS counterpart, table TQCQPROF (TOPS
QMS Call Queue Profiles table). The only difference between the tables is that
table TQCQPROF contains field DLAYCT4Q which is not required for
OSSAIN.
Call queue profiles are specified in one of two ways:

Using office-wide priority and office-wide assignable grade of service
(AGS) values (see field PRIOTYPE set to OFC).
Using profile-specific priority and profile-specific assignable grade of
service (AGS) values (see field PRIOTYPE set to PROF).
Call queue profiles datafilled using office-wide priorities contain a list of up to

255 call queues (field CQLIST). Each call queue is specified as a value in the
range CQ0 to CQ254. The priority and AGS associated with each of the call
queues specified are the office-wide values defined for the queue in table
QMSCQDEF. Office-wide priority call queue profiles result in consistent
office-wide priorities and AGS values being applied to all operators.
If the operating company wishes to override the system priority and AGS
associated with each call queue, the particular profile is datafilled using
priority and AGS values specific to that profile. For each of up to four priority
levels (labeled PRIO3, PRIO2, PRIO1,and PRIO0, with PRIO3 being the
highest priority level), a list of up to 32 call queues along with the desired AGS
for each is specified.
Datafill sequence and implications

Table QAPLNDEF must be datafilled before table OQCQPROF.. Note that the
AGENTQ and CALLQ values in table OQCQPROF are effectively limited by
the datafill for the OSSAIN application in table QAPLNDEF.
Table size
0 to 255 tuples
297-8021-351 Standard 05.02 May 2001

Data schema tables 1-3
OQCQPROF (continued)
Datafill
The following table lists datafill for table OQCQPROF.
Field descriptions (Sheet 1 of 4)
Subfield or
Field refinement Entry Explanation and action
CQPROFNM 0 to 254 Call queue profile number. This number is used in

table OASESNPL.
AGENTQ AQ0 to AQ254 OSSAIN QMS agent queue. Enter the agent
(upper value queue number for operators that are idle and
limited by available to handle calls with this profile number.
AGENTQS in When an agent is requested from the QMS CAM,
QAPLNDEF) the agent queues are searched for an agent that
has the requested call queue in its profile. Any
number of agent queues can be used, but a good
starting point would be to have one agent queue for
each call queue profile datafilled in table
OQCQPROF.
The range of agent queues is limited by the value
datafilled in field AGENTQS of table QAPLNDEF.
For example, if AGENTQS is set to 10, then in
table OQCQPROF only queues AQ0 to AQ9
should be datafilled.
PRIOAREA see subfield Call queue priority type selector. This field consists
PRIOTYPE of subfield PRIOTYPE.
PRIOTYPE OFC or PROF Call queue priority type. Enter OFC for office-wide
call queue and datafill refinement CQLIST.
Enter PROF for profile call queue and datafill
refinements PRIO3, PRIO2, PRIO1, and PRIO0.
Up to four multiples of each specified priority levels
PRIO3 (highest priority), PRIO2, PRIO1, and
PRIO0 (lowest priority) can be datafilled. If less
than four multiples are required, end the list with a
$ (dollar sign).
If PRIOTYPE = OFC, datafill refinement CQLIST. If
PRIOTYPE = PROF, datafill refinements PRIO3,
PRIO2, PRIO1, and PRIO0.
Subfield or
CQLIST CQ0 to Call queue list. If the entry in subfield PRIOTYPE

CQ254 (upper is OFC, datafill this refinement. Enter a value for
value limited each call queue to be included in the profile.
by CALLQS in
No further refinements require datafill.
QAPLNDEF)
The range of call queues is limited by the value
datafilled in field CALLQS of table QAPLNDEF. For
example, if CALLQS is set to 10, then in table
OQCQPROF only queues AQ0 to AQ9 should be
datafilled.
PRIO3 see subfields Priority level 3. If the entry in subfield PRIOTYPE is

CALLQ and PROF, datafill this refinement. This field is the
AGS highest priority level and consists of subfields
CALLQ and AGS.
CALLQ CQ0 to Call queue. If the entry in subfield PRIOTYPE is

CQ254 (upper PROF, datafill this refinement. Enter up to 32 call
value limited queues to be included in the profile. If less than 32
by CALLQS in queues are required, end the list with a $ (dollar
QAPLNDEF) sign).
datafilled.
AGS 10 to 80 Assignable grade of service. If the entry in subfield

PRIOTYPE is PROF, datafill this refinement. Enter
the aging factors from 1.0X to 8.0X for the grade of
service to be applied to the call queue (refinement
CALLQ) for the purposes of this profile. Specify 10
for no aging.
PRIO2 see subfields Priority level 2. If the entry in subfield PRIOTYPE

CALLQ and is PROF, datafill this refinement. This field is the
AGS second highest priority level and consists of
subfields CALLQ and AGS.
297-8021-351 Standard 05.02 May 2001

Subfield or

QAPLNDEF) sign).
datafilled.

for no aging.

AGS third highest priority level and consists of subfields
CALLQ and AGS.

QAPLNDEF) sign).
datafilled.

for no aging.
Subfield or

AGS lowest priority level and consists of subfields
CALLQ and AGS.

QAPLNDEF) sign).
datafilled.

for no aging.
Datafill example
The following example shows sample datafill for table OQCQPROF.
MAP display example for table OQCQPROF
CQPROFNM AGENTQ PRIOAREA

0 AQ0 OFC (CQ0)$
1 AQ1 OFC (CQ1)$
2 AQ3 OFC (CQ0)(CQ1)$
3 AQ4 PROF (CQ0 10)(CQ1 80)$ (CQ2 10)$
In the above example, call queue profile number 0 is used for agents that serve
CQ0. From table OAFUNDEF sample datafill in this section, the BRANDING
function is associated with CQ0. From table OASESNPL, both the
BRAND_NODE1 and BRAND_NODE2 session pools are datafilled as using
call queue profile number 0 (field OCQPROF). Since the MAXSESN field for
297-8021-351 Standard 05.02 May 2001

OQCQPROF (end)
each of those session pools is set to 100, there are 200 agents placed in agent
queue AQ0, waiting to serve calls from CQ0 (the BRANDING function).
Error messages
The following error messages apply to table OQCQPROF..
Error messages for table OQCQPROF
Error message Explanation and action
At least one call queue must be When adding a tuple to table OQCQPROF, at
specified. least one call queue must be provided.
A call queue may not appear in more This message is displayed if an attempt is made
than one priority level. to datafill the same call queue in more than one
priority level.
A call queue has been specified in This message is displayed if an attempt is made
the same priority level with to datafill the same call queue in the same priority
different AGS values. level with different AGS values.
This call queue profile is in use in Tuples may not be deleted in table OQCQPROF
table OASESNPL. until all references to that call queue profile are
removed from table OASESNPL. These error
messages are displayed if an attempt is made to
You must remove all references to delete a call queue profile from table
this profile before you can delete OQCQPROF that is in use in table OASESNPL.
it.
Unable to change call queue profile. This error message can occur when changing a
Check QMS logs and SWERRS. tuple in table OQCQPROF and an error occurs
when trying to update the profile in the QMS
CAM.
Table history
NA011
Removed error message All session pools with this call queue profile must be
OFFLINE before this profile may be changed." since this restriction is
removed. Added error message Unable to change call queue profile. Check
QMS logs and SWERRS."
NA006
Table OQCQPROF was created by functionality Operator Services,
ENSV0014.
ORIGRC
Table name
TOPS Point-to-point Rating Originating Rate Centers Table
Point-to-point rating system tables are used in a switch with the Traffic
Operator Position System (TOPS).
Point-to-point rating is a method of automatic rate step determination by the

DMS rating system using an operating company defined rate step between two
points, each defined by its numbering plan area (NPA) and NXX.
Point-to-point rating is an alternative to the following automatic rate step

determination methods:
vertical and horizontal (V&H) method
single rate area (SRA) method
Point-to-point rating system tables are listed in the table below.

TOPS Point-to-point Rating System Tables
Table name Form number Form title
ORIGRC 2726A, B TOPS Originating Rate Centers Table Record
TERMRC 2727A, B TOPS Terminating Rate Centers Table Record
PTP 2728A, B TOPS Point-to-point Table Record
Information for point-to-point rating is submitted by the operating company in

the following customer data schema tables:
table CLDNPA
table ORIGRC
table TERMRC
table PTP
table OFCENG, office parameters
TOPS_MAX_ORIG_RATE CENTER
TOPS_MAX_TERM_RATE_CENTER
Table ORIGRC is used to divide the serving area which can originate calls to
an area where point-to-point rating applies into originating rate centers. The
297-8021-351 Standard 05.02 May 2001

ORIGRC (continued)
division is done by specifying the originating rate center (ORC) number for
each calling NPA-NXX combination within such a serving area.
For related information, refer to tables TARIFF, CLGTRF, SCHNUM,

CLDNPA, OFCENG, TERMRC, and PTP.

Table HNPACONT must be datafilled before table ORIGRC.
Table ORIGRC interacts with office parameter

TOPS_MAX_ORIG_RATE_CENTER in table OFCENG.
Datafill
The following table lists datafill for table ORIGRC.
Field descriptions
Subfield or
NPANXX See subfields Calling numbering plan area Nxx key for
point-to-point rating This field consists of
subfields CLGNPA and CLGNXX.
CLGNPA N 0/1 X Calling numbering plan area. Enter the

calling numbering plan area (NPA) as
previously datafiled in table HNPACONT
N is any number between 2 and 9, inclusive.
X is any number between 0 and 9, inclusive.
CLGNXX 200 to 999 Calling Nxx. Enter the calling NXX.
ORC 1 to 255 (see Point-to-point originating rate center. Enter

note) the point-to-point originating rate center
number that the calling NPA-NXX
combination belongs to.
The entry in this field cannot exceed the value
of office parameter
TOPS_MAX_ORIG_RATE_CENTER in table
OFCENG.
NOTE: The DMS switch shows the range as
0-255, however, value 0 is a NIL value and
not allowed by table control.
ORIGRC (end)
Datafill example
The following example shows sample datafill for table ORIGRC.
MAP display example for table ORIGRC
NPANXX ORC
________________________________________________________
222 200 3
Table history
NA005
Changed range of field ORC from 0-255 to 1-255. Value 0 is a NIL value and
not allow by table control per PRS UT56251.
297-8021-351 Standard 05.02 May 2001

OSCVLGRP
Table name
Operator Services Systems Advanced Intelligent Network (OSSAIN)
Centralization Voice Link Group
Table OSCVLGRP identifies the voice link groups that are used by an
OSSAIN centralization (OSAC) host to connect to OSAC remote switches. A
tuple is added in this table for each OSAC office that an OSAC host switch
communicates with for OSAC call processing. The most idle selection
sequence is used for selecting a voice link member from the group. This table
is only used in the OSAC host.

The following tables must be datafilled before table OSCVLGRP.
TRKGRP
OANODINV
Table size
0 to 256 tuples
Datafill
The following table lists datafill for table OSCVLGRP.
Field descriptions
Subfield or
NODENAME node name Node name. This is the key into the table. This is the
from table node name of a OSAC remote switch from table
OANODINV OANODINV that the OSAC host communicates.
This node must be datafilled in table OANODINV as
an OSAC switch.
CLLI from table Common language location identifier. This field is

CLLI the voice link group between the OSAC host and
the OSAC switch in field NODENAME.
Datafill example
The following example shows sample datafill for table OSCVLGRP.
OSCVLGRP (continued)
MAP display example for table OSCVLGRP
NODENAME CLLI

OSAC_SW1 OSACVL1
OSAC_SW2 OSACVL2
OSAC_SW3 OSACVL3
OSAC_SW4 OSACVL4
Error messages
The following error messages apply to table OSCVLGRP..
Error messages for table
Only node ids of PM type OSAC can be Table OANODINV must be datafilled with the
datafilled in this table. OSAC node name before being used in table
OSCVLGRP. The node name must be datafilled
as an OSAC switch. This error message is
displayed if the NODEID is not datafilled in table
OANODINV as an OSAC switch.
This CLLI must be datafilled in Table The CLLI must be datafilled in table TRKGRP
TRKGRP before datafilling this table. before being used in this table. This error
message is displayed if the CLLI is not datafilled
in table TRKGRP.
Trunk group type for CLLI must be The trunk group type for the CLLI must be
TOPSVL. TOPSVL since only trunks of that type can be
used for host-remote voice connections. This
error message is displayed if the trunk group is of
another type.
The CLLI name is used in table If a CLLI is referenced in table SNVLGRP, it

XXXXXXXX, it cannot be reused here. cannot be datafilled in table OSCVLGRP. And, if
a CLLI is referenced in table OSCVLGRP, it
cannnot be datafilled in table SNVLGRP. This
error message is displayed when attempting to
datafill table OSCVLGRP with a CLLI that is used
in table SNVLGRP:
In the error message, XXXXXXXX is the name of
the table containing the CLLI; in this case,
SNVLGRP.
297-8021-351 Standard 05.02 May 2001

OSCVLGRP (end)
Table history
TOPS11
An error message is added for a dependency with table SNVLGRP by feature
AF7714 in functionality OSSAIN 11 Enhancements, OSAN0006.
TOPS07
Table OSCVLGRP was introduced by feature AN1536 in functionality
OSSAIN Enhancements, ENSV0020.
OSIPARMS
Table name
Open Systems Interconnect Parameter Table
Table OSIPARMS modifies the parameters within the various layers of the
billing server International Standards Organization (ISO) implementation.
Table OSIPARMS allows the user to alter parameters for the following ISO
protocol specifications:
ISO 8073AD2 (Class 4 Service Over Connectionless Network)
ISO 8073 (Connection Oriented Transport Protocol)
ISO 8327 (Connection Oriented Session Protocol)
ISO 8823 (Connection Oriented Presentation Protocol)
ISO 8649 (Association Control Service Element Protocol)
ISO 8571 (File Transfer Access Management Protocol)
Each tuple in table OSIPARMS corresponds to one OSI protocol stack running
on a specific Ethernet interface unit (EIU).
The local area network controller for Ethernet (LANCE) chip is set to transmit
the most significant byte (MSB) first (byte flipping enabled). This results in
real time-savings (1 ms for each frame) for the Open Systems Interconnect unit
(OSIU) stack. This mode for the LANCE chip is activated only if the OSIU is
in service.

The following tables must be datafilled before table OSIPARMS.
LIUINV
OSIROUTE
Table size
0 to 16 tuples
297-8021-351 Standard 05.02 May 2001

OSIPARMS (continued)
Datafill
The following table lists datafill for table OSIPARMS.
Subfield or
OSIPARMS-KE see subfield Open systems interconnect parameters key

Y
This field consists of subfield TUPLE_KEY.
TUPLE_KEY alphanumeric Tuple key

(up to 8
This is the key field of the table. Enter the
characters)
tuple key.
OSI_HOST-NA see subfields Open systems interconnect host name

ME
This field consists of subfields WORD_NODE
and NODE_RNG.
WORD_NODE EIU Word node

Enter EIU for the Ethernet interface unit.
NODE_RNG 0 to 750 Node range

Enter a node range value.
Subfield or
TRANSPORT INACTMR Transport layers

L4CONNSLA
Enter up to eight transport layers. If less than
CKTMRRETR
eight entries are required, end the list with a $
IES
(dollar sign).
TPCLASS
TPDUSIZE Enter INACTMR (inactivity timer) and datafill
WINSIZE refinement INACTMR_VALUE on the
WINTMR following pages.
Enter L4CONNS (number of connections)
and datafill refinement L4NUMCON_VALUE
on the following pages
Enter LACKTMR (local acknowledgement
delay timer) and datafill refinement
LACKTMR_VALUE on the following pages
Enter RETRIES (retries) and datafill
refinement RETRIES_VALUE on page .
Enter TPCLASS (transport layer class) and
datafill refinement CLASS_VALUE onthe
following pages.
Enter TPDUSIZE (transport layer protocol
disk units [TPDU]) and datafill refinement
TPDUSIZE_VALUE on the following pages.
Enter WINSIZE (window size) and datafill

refinement WINDSIZE_VALUE on the
following pages.
Enter WINTMR (window timer) and datafill
refinement WINTMR_VALUE onthe following
pages.
INACTMR_VAL 2 to 2 Inactivity timer value

UE
Enter the value that defines the maximum
length of time, in minutes, that the transport
layer waits for a transport time-out signal.
The time-out signal indicates that the
transport layer communication handshaking
is inactive.
The default value is 2.
297-8021-351 Standard 05.02 May 2001

Subfield or
LACKTMR_VA 0 to 0 Local acknowledgement delay timer value

LUE
Enter the value that defines the time to delay
acknowledgement of received TPDUs.
The default value is 0 (zero), which means the
timer is disabled.
L4NUMCON_V 48 to 48 Number of connections

ALUE
Enter the value that defines the maximum
number of simultaneous transport layer
connections.
RETRIES_VAL 8 to 8 Retries value

UE
Enter the value to define the maximum
number of times the transport layer
retransmits a single unacknowledged TPDU
before issuing a disconnect.
CLASS_VALUE 0 to 4 Transport layer class value

Enter the value to specify the transport layer
classes of services supported.
Class 0 provides the most simple type of
transport connection.
Class 1 provides a basic transport connection
with minimum overhead.
Class 2 provides multiplexing of several
transport connections into a single network
connection.
Class 3 provides the capabilities of class 2
plus the ability to recover from network
disconnect or reset.
Class 4 provides the capabilities of class 3
plus the ability to detect and recover from
errors as a result of lower layer failure. The
kinds of errors detected by class 4 include
TPDU loss, TPDU delivery out of sequence,
TPDU duplication, and TPDU corruption.
Subfield or
TPDUSIZE_VA T1024 Transport layer protocol disk unit size value

LUE
Enter the value to define the maximum size of
the TPDUs.
The default value is T1024.
WINDSIZE_VA 8 to 8 Window size value

LUE
number of outstanding TPDUs awaiting
acknowledgement.
WINTMR_VAL 15 to 15 Window timer value

UE
Enter the value to define the frequency, in
seconds, with which the transport layer sends
an acknowledgement TPDU, if there is no
activity, to determine if its peer entity is still
active.
297-8021-351 Standard 05.02 May 2001

Subfield or
SESSION EXPEDTRP Session layer

EXTCON-CA
Enter up to seven session layers. If less than
T L5CONNS
seven layers are required, end the list with a
PROTVER
$ (dollar sign).
REUSETRP
SEGMENT Enter EXPEDTRP (expedited transport) and
TSDUSIZE datafill datafill refinement
EXPEDTRP_VALUE on the following pages.
Enter EXCONCAT (extended concatenation)
and datafill refinement EXCONCAT_VALUE
on the following pages.
Enter L5CONNS (number of connectsion)
and datafill refinement L5NUMCON_VALUE
Enter PROTVER (protocol version) and
datafill refinement PROTVER_VALUE on the
following pages.
Enter REUSETRP (reuse existing transport
connections) and datafill refinement
REUSETRP_VALUE on the following pages.
Enter SEGMENT (segmentation) and datafill
refinement SEGMENT_VALUE on the
following pages.
Enter TSDUSIZE (TSDU size) and datafill

refinement TSDUSIZE_VALUE on the
following pages.
EXPEDTRP_V NO Expedited transport value

ALUE
Enter the value to specify whether the
transport layer expedited flow is available to
the session connection.
The default value is NO.
EXCONCAT_V YES Extended concatenation value

ALUE
Enter the value to specify whether extended
concatenation is supported.
The default value is YES.
Subfield or

ALUE
number of simultaneous session layer
connections.
PROTVER_VA VER_1 Protocol version value

LUE VER_2 or
Enter the value to specify the session layer
VER_1_2
protocol version.
The default value is VER_1_2.
REUSETRP_V YES Reuse existing transport connections value

ALUE
Enter the value to enable or disable the
attempt to reuse an existing transport
connection once it has been released by a
closed session connection.
The default value is YES.
SEGMENT_VA NO Segmentation value

LUE
Enter the value to specify whether
segmentation is allowed.
The default value is NO.
TSDUSIZE_VA S4096 Tsdu maximum size

LUE
Enter the value to define the maximum size of
the transport service data unit.
The default value is S4096.
PRESENT-ATI L6CONNS Presentation layer

ON
Enter the presentation layer, L6CONNS
(number of connections) and datafill
refinement L6NUMCON_VALUE.

ALUE
Enter a value to define the maximum number
of simultaneous presentation layer
connections.
297-8021-351 Standard 05.02 May 2001

OSIPARMS (end)
Datafill example
The following example shows sample datafill for table OSIPARMS.
MAP display example for table OSIPARMS
OSIPARMSKEY OSI_HOSTNAME
TRANSPORT
SESSION
PRESENTATION
APPLICATION
_____________________________________________________________________
BNR1 EIU 208
(INACTMR 2) (LACKTMR 0) (L4CONNS 48) (RETRIES 8) (TPCLASS 4)
(TPDUSIZE T1024) (WINSIZE 8) (WINTMR 15) $
(EXPEDTRP NO) (EXTCONCAT YES) (L5CONNS 48) (PROTVER VER_1_2)
(REUSETRP YES)
(SEGMENT NO) (TSDUSIZE S4096) $
(L6CONNS 48)$(ASCECONNS 48) $
Table history
NA008
Reference to FTAM was removed from Table and Map display.
BCS36
Subfields TRANS_VECTOR, SESSION_VECTOR, and APPL_VECTOR
were removed.
BCS35
Table OSIPARMS was introduced.
OSIROUTE
Table name
Open Systems Interconnect Routing Table
Table OSIROUTE describes the open systems interconnect (OSI) static
routing information for the billing server network layer. The routing
information supports the International Organization for Standardization (ISO)
standard ISO 8473, connectionless internet protocol (IP). Table OSIROUTE
functions as a look-up table for static route information to map the network
entity title (NET) portion of the network services access point (NSAP) into the
subnetwork point of attachment (SNPA) in the billing server network layer.
The key field is OSIKEY. Table LIUINV lists the inventory of processor types
and their network addresses.

Table LIUINV must be datafilled after table OSIROUTE.
Table size
2 to 32 tuples
A maximum of 32 network addresses can be entered. The table size is set by

the datafill in table SYSDATA. Each tuple requires 132 bytes of physical store.
The storage requirement is therefore 4224 bytes (32 tuples x 132 bytes/tuple =
4224 bytes).
297-8021-351 Standard 05.02 May 2001

OSIROUTE (continued)
Datafill
The following table lists datafill for table OSIROUTE.
Subfield or
OSIKEY alphanumeric Open system interconnect key

Enter up to a maximum of eight characters for
the network address. Entries must begin with
a letter, not the number. This is the key field
to table OSIROUTE.
AFI 0 to 9 and A to Authority and format identifier

F
Enter the one- to two-character hexadecimal
byte value for the authority and format
identifier (AFI) used for the network address.
DSP 0 to 9 and A to Domain specific part

F
Enter the nine two-character hexadecimal
byte values for the domain specific part (DSP)
of the network address. The first two bytes
are the area address identifying the subnet
within the network. The following six bytes
are the logical node identifier identifying the
node in the specific subnet The last byte is
the NSAP selector identifying the user of the
network service. The default value is
000000000000000001.
Subfield or
SYSSEL see subfields System selector

This field consists of subfield TYPE and its
refinements HOSTNAME, REQ REM SYS,
WORDNODE, NODERNG, PREFNET,
REACHNET, MACADDR, and CONTMARK.
TYPE ESWIOSIU System type

ESWOOSIU
Enter the selector for the type of system.
ISWIOSIU
REM_ES_SY The following selectors apply to the open
S systems interconnect unit (OSIU) on the
REM_IS_SYS SuperNode/DMS billing server:
Enter ESWIOSIU for an end system (ES)
running on the OSIU.
Enter ESWOOSIU for an ES not running
on the OSIU.
Enter ISWIOSIU for an intermediate
system (IS) running on the OSIU.
The following selectors apply to other ESs,
that are not part of the DMS, but are part of
the local area network (LAN) connected to the
DMS:
Enter REM_ES_SYS for an ES.
Enter REM_IS_SYS for an IS.
The default value is ESWIOSIU.
297-8021-351 Standard 05.02 May 2001

TYPE = ESWIOSIU, ESWOOSIU, or ISWIOSIU

If the entry in subfield TYPE is ESWIOSIU, ESWOOSIU, or ISWIOSIU,
datafill refinements HOSTNAME, WORDNODE, and NODERNG.
Field descriptions for conditional datafill
Subfield or
HOSTNAME see subfields Host name

This field consists of subfields WORDNODE
and NODERNG.
WORDNODE APUX, CM, Word node name

EIU, LIU7,
Enter the name for the DMS processor type.
FRIU, XLIU,
The entry must match the entry in field
LCOM, VPU,
LIUTYPE in table LIUINV. Entries outside
or FP
this range are invalid. The default value is
EIU.
NODERNG numeric Node ring identifier

Enter the node ring identifier for the DMS
processor type. The entry must match the
entry in field LIUNO in table LIUINV. The
following are valid entries for the
corresponding values entered in
WORDNODE:
APUX 1 to 98
CM 0 only
EIU 1 to 710
FP 1 to 99
Entries outside this range are invalid.
TYPE = ESWOOSIU
If the entry in subfield TYPE is ESWOOSIU, datafill the additional refinement
PREFNET to complete the datafill for field SYSSEL.
Subfield or
PREFNET alphanumeric Preferred network name

(vector of up
Enter a name vector to define the ES router
to 8
within the DMS. The name must match one
characters)
of the names listed in field OSIKEY.
TYPE = REM_ES_SYS or REM_IS_SYS

If the entry in subfield TYPE is REM_ES_SYS or REM_IS_SYS, datafill
refinements REACHNET and MACADDR.
Subfield or
REACHNET alphanumeric Reachable network names

Enter up to two name vectors of up to eight
characters each to define paths to other
systems in the LAN. Names must match
values in field OSIKEY. A minimum of one
name must be entered.
CONTMARK $ Continuation mark

Enter $ to indicate the end of the vector if only
one value is entered in field REACHNET.
MACADDR 0 to 9 and A to Mac addresses

F
Enter up to two media access control (MAC)
address vectors of up to 12 hexadecimal
characters each to define the physical
addresses of remote systems able to reach
this network address. A minimum of one
address must be entered.
CONTMARK $ Continuation mark

Enter $ to indicate the end of the vector if only
one value is entered in field MACADDR.
297-8021-351 Standard 05.02 May 2001

OSIROUTE (end)
Datafill example
The following example shows sample datafill for table OSIROUTE.
The example consists of two ESs with an OSIU, two ESs without an OSIU, and
two non-DMS remote systems.
1 = HOSTNAME 4 = PREFNET 7 = MACADDR 2 = WORDNODE

5 = CONTMARK 8 = REQREMSYS 3 = NODERNG 6 = REACHNET
9 = REQWOOSIU
MAP display example for table OSIROUTE
OSIKEY AFI DSP

SYSSEL
________________________________________________________
NET1 49 0000000000000000001
ESWIOSIU EIU 07
NETLAST 49 0000000000000000011
ISWIOSIU EIU 08
NET2 49 0000000000000000021
ESWOOSIU FP 01 NET 1
NET3 49 0000000000000000031
ESWOOSIU CM 0 NETLAST
CUST1 49 0000000000000000041
REM_ES_SYS NET1 $
00007 5F00022
CUST2 49 0000000000000000051
REM_IS_SYS NET2 $
00007 5F00023
Table history
BCS36
Table OSIROUTE introduced.
OSNCCAP
Table name
Operator Services Network Capability (OSNC)
Table OSNCCAP allows a set of OSNC capabilities such as connection hold
to be datafilled in up to 254 tuples. Connection hold is the only OSNC
capability that is a possible datafill entry in this table. The T-selector datafilled
in tables HNPACONT, FNPACONT, OFRT, OFR2, OFR3, OFR4 points to the
254 tuples.
Table OSNCCAP controls whether OSNC capabilities are signalled on

outgoing Intertoll (IT) or Access to Carrier (ATC) ISUP trunks.The OSNC
activity provides functionality that allows a variety of services over Integrated
Services Digital Network User Part (ISUP).
Datafill sequence and meaning

Operating company personnel must add tuples into table OSNCCAP before
the OSNC selector datafilled in the OFRT tables or RTEREF subtables can
point to the tuples.
It is not possible to delete tuples from table OSNCCAP. Deletion of the tuples
is blocked in order to ensure that the OFRT and RTEREF tables do not point
to a non-existent OSNCCAP table.
Table size
0 to 254 tuples
297-8021-351 Standard 05.02 May 2001

OSNCCAP (continued)
Datafill
The table that follows lists datafill for table OSNCCAP.
Field descriptions
Field Subfield Entry Explanation and action
OSNCIDX {0 to 254} OSNC Capability index. This field is

the route list index that is set in other
routing tables such as table
HNPACONT:RTEREF
OSNCINFO STATE {OFF, ON} When OFF is selected, OSNC

capabilities are not signalled on
outgoing IT/ATC ISUP trunks. Also,
no other fields follow.
When ON is selected, OSNC
capabilities are signalled on outgoing
IT/ATC ISUP trunks for calls arriving
to TOPS and service nodes with
OSNC capabilities.
OSNCCAP {SAP} When the SAP is selected, the

CONNHOLD field follows. Selection of
the SAP option causes the SAP to be
included in the IAM to establish an
outgoing connection.
CONNHOLD {N, Y} When set to N, connection hold is

unavailable on the outgoing
connection.
When set to Y, connection hold is
available on the outgoing connection.
Datafill example
The figure that follows shows sample datafill for table OSNCCAP.
OSNCCAP (end)
MAP display example for table OSNCCAP
OSNCIDX OSNCINFO
---------------------------------------------------------------------------------
0 OFF
1 ON $
2 ON (SAP Y) $
3 ON (SAP N) $
Table history
TOPS13
The OSNC activity created this table.
Additional information
None
297-8021-351 Standard 05.02 May 2001

OSSCAT
Table name
Operator Services Signaling with CATegory (formerly called ANIID Mapping
for TOPS Trunk Group with OSS Table)
Table OSSCAT allows the operating company to define the following upon
receipt of specified pair of automatic number identification (ANI)
identification (ID) digits over a Traffic Operator Position System (TOPS) trunk
with operator services signaling:
The expected number of digits to be found in the ANI spill as determined
by the entry in field FORMAT.
Field FORMAT is used to set the ANI status of the call by comparing the
digits received to the expected format. If the format is invalid, other data in
table OSSCAT cannot be accessed.
The method of determining the call origination type and the calling service
feature as defined by the entry in field CLGSERV.
Field CLGSERV can set the call origination type or calling service feature
if the call comes over a trunk group that may carry more then one type of
traffic. If the trunk is a dedicated type, this field is ignored.
An inter-LATA (local access and transport area) restriction option (field
REST)
An optional route (field ROUTE)
An optional route that overrides any route specified in the pretranslator can
also be specified. This can route the call to a TOPS or, up to BCS35, to an
Auxiliary Operator Assistance System (AOSS), position under a new call
origination type or out of the office on a different trunk group.
Note: As of BCS32, table OSSCAT is present even if the Equal Access

software package is not ordered.
OSSCAT (continued)
The operator services signaling format is very close to that received from
multifrequency (MF) trunks using standard bell signaling except for the
following differences:
The calling signaling terminal (ST) pulse tells us if the call is to be sent to
an incoming (IC) ST or handled by the BOC (signaling transfer point
[STP]).
The ANI spill has a double identity digit rather than a single identity digit.
OSS can arrive on MF trunks only because dial pulse (DP) trunks expect
the calling ST pulse to indicate call origination or calling service feature
and OSS uses this pulse to indicate a BOC- or an IC-handled call.
ANI information is set in the exact same manner as BELLANI signaling. The
called ST pulses have the same meaning. Since only the ANI signaling type
has changed for the trunk group, groups still have dedicated calling service
features or call origination types.
A pair of ANI ID digits must be received in order to access any information in

table OSSCAT, or else the call is marked as ANI FAIL (failure) and routed to
a TOPS position.
If the ANI format is violated (which means that even though a pair of ANI ID
digits is received, the ANI spill is not one of the valid formats specified in table
OSSCAT), the following information can be used to set the calling service
feature and the call origination type:
Information inherent in the trunk group (dedicated trunks)
ST pulse can be used to set the call origination type if the trunk group is
MF (since CLD ST pulse is used in this case)
If the ANI spill is simply missing the CLG ST pulse, yet the call has a valid
format, table OSSCAT can be used to set the calling service feature and a
route.
The table editor command, REP, to change the default values shown in the
following table.
Table OSSCAT default tuples (Sheet 1 of 2)
ANI ID digits FORM CLGSERV REST ROUTE
00 ANI STATION NONE N
01 ONI STATION NONE N
02 ANIF STATION NONE N
297-8021-351 Standard 05.02 May 2001

OSSCAT (continued)
Table OSSCAT default tuples (Sheet 2 of 2)
ANI ID digits FORM CLGSERV REST ROUTE
06 ANI_ANIF HOTEL NONE N
07 ANI SPECIAL NONE N
08 ANI STATION INTER N
30 ANI BLDNINTC NONE N
31 ANI TRBLINTC NONE N
32 ANI INTC NONE N
20 ANI STATION INTER N
68 ANI_ANIF HOTEL INTER N
78 ANI SPECIAL INTER N

The following tables must be datafilled before table OSSCAT.
OFRT
TOPS
TOPSTOPT
Table size
Memory allocation is static and fixed at 100 entries.
OSSCAT (continued)
Datafill
The following table lists datafill for table OSSCAT.
Subfield or
ANI 00 to 99 Automatic number identification digits. Enter

the automatic number identification (ANI)
identification (ID) digits found in the
multifrequency (MF) ANI spill outpulsed from
the originating office to the end office.
FORMAT ANI, Format. Enter the code to identify the number

ANI_ANIF, of digits expected in a valid format ANI spill:
ANI_ANIID,
Enter ANI if an ANI ID digit, a seven-digit
ANIF, ANIID,
calling number, and a signaling terminal (ST)
or ONI
signal are expected. The call is marked as
ANI SUCCESS.
Enter ANI_ANIF if at least an ANI ID digit and
an ST pulse are expected. If no calling (CLG)
digits are received, an ANI failure was
identified by the originating office. If seven
digits are received, the call is marked as ANI
SUCCESS.
Enter ANI_ANIID if at least an ANI ID digit and
an ST pulse are expected. If no CLG digits
are received, operator identification of the
CLG number is not required. If seven digits
are received, the call is marked as ANI
SUCCESS.
Enter ANIF if an ANI failure is detected at the
originating office, and an ANI ID digit and an
ST pulse are expected. Operator
identification of the CLG number is required.
Enter ANIID if an ANI ID digit and an ST pulse
are expected, no CLG number is expected,
and operator identification of the CLG number
is not required.
Enter ONI if an ANI ID digit and an ST pulse
are expected, and operator identification of
the CLG number is required. The ANI status
is set to ONI_CALL.
297-8021-351 Standard 05.02 May 2001

OSSCAT (continued)
Subfield or
CLGSERV ALM Calling service feature and call origination

BLDNINTC type. If the Traffic Operator Position System
COIN HOTEL (TOPS) trunk group is dedicated (field
INTC MOBILE STATCLAS in table TRKGRP is set to
SPECIAL ALARM, COIN, HOTEL, INTCPT, MOBILE,
STATION NONCOIN, or TOLLSTA) then the calling
TRBLINTC service feature is set from the trunk group
data unless ALM, INTC, or MOBILE is
entered as described below.
The call origination type is set when the TOPS
trunk group is dedicated to mobile, attended
pay station, alarm intercept, toll subscriber, or
toll station.
Otherwise the calling service feature and call
origination are set as follows. Enter the calling
service feature of the call and call origination
using entries described below and the ST
pulse received. Calling service feature is set
from TOPS trunk group data (ALM, INTC, and
MOBILE entries are exceptions)
Enter ALM (alarm) if the calling service
feature is to be set to STATION regardless of
the originating trunk group and the call
origination is to be set to ALM.
Enter BLDNINTC (blank directory number
intercept) if the calling service feature is set to
STATION and the call origination is set to
intercept. For BLDNINTC, the intercept call
type is set to blank number intercept.
Enter COIN if the end office uses the ANI to
signify a coin call and the call origination is to
be set to COIN.
OSSCAT (continued)
Subfield or
CLGSERV Enter HOTEL to indicate that the call

(continued) origination is to be set by looking at the ST
signal and if the TOPS trunk group is
combined or centralized automatic message
accounting (CAMA) tributary (field
STATCLAS in table TRKGRP is set to
COMBINED or CAMATRIB), then the calling
service feature is to be set to HOTEL.
Enter INTC (intercept) if the calling service
feature is to be set to STATION regardless of
the originating trunk group and the call
origination is to be set to INTC.
Enter MOBILE if the calling service feature is
to be set to STATION regardless of the
originating trunk group and the call origination
is to be set to MOBILE.
Enter SPECIAL to indicate that the call
origination is to be set by looking at the ST
signal, and if the trunk is combined (field
STATCLAS in table TRKGRP is set to
COMBINED), then the calling service feature
is set by using the calling number as an index
into table SPLDNID.
297-8021-351 Standard 05.02 May 2001

OSSCAT (continued)
Subfield or
CLGSERV Enter STATION to indicate the following:

(continued)
If the TOPS trunk group is combined or
CAMA tributary (field STATCLAS in table
TRKGRP is set to COMBINED or
CAMATRIB), then the calling service
feature and call origination are set by
looking at the ST signal.
If the TOPS trunk group is class- of-
service lookup (field STATCLAS in table
TRKGRP is set to DNLOOKUP), then the
calling service feature is set by looking in
table SPLDNID using the calling number
as an index and the call origination is set
by looking at the ST signal.
Enter TRBLINTC if the calling service feature
is set to STATION and the call origination is
set to intercept. For TRBLINTC, the intercept
call type is set to trouble or special intercept.
REST INTER or Inter-LATA restricted. Enter INTER to indicate

NONE that inter-LATA (local access and transport
area) calls are restricted.
Otherwise enter NONE.
ROUTE see subfield Automatic number identification route. This

field consists of subfield ROUTEID.
This field overrides any routing information
derived from the called number and it is used
to send the call to a position or an outgoing
trunk.
ROUTEID N or T Selector. Enter N if no route is specified in this

table and any routes previously defined (such
as STDPRTCT) are to remain in effect. No
refinements require datafill.
Enter T if the route is chosen by another
routing table and datafill refinement TABID.
OSSCAT (continued)
Subfield or
TABID AOSS, OFRT, Table name. If the entry in subfield SEL is T,

or TOPS datafill this refinement. Enter the route table
name.
Note: For BCS36 and up, table AOSS is not

a valid entry.
KEY 1 to 1023 or Key. If the entry in refinement TABID is

alphanumeric OFRT, enter the route reference index of the
route list in table OFRT to which translation is
to route.
If the entry in refinement TABID is TOPS or
AOSS, enter a call type code defined in table
TOPS or table AOSS respectively.
Note: If AOSS, intercept calls on all

combined trunk groups route to AOSS.
SCRNIDX 0-100 Screening index. This field is an index into

table RESTBIL (TA call) or DARSTBIL (DA
call). This field supports a check of billing
restrictions based on the incoming ANI ID
digits for OSS signaling. This field is used if
table TOPSTOPT field ANIIDSCR = Y, table
TRKGRP field SIGTYPE = OSS, and no other
restrictions apply to the call.
Datafill example
The following example shows sample datafill for table OSSCAT.
MAP display example for table OSSCAT
ANI FORMAT CLGSERV REST ROUTE SCRNIDX

__________________________________________________________
0 ANI STATION NONE N 10
297-8021-351 Standard 05.02 May 2001

OSSCAT (end)
Table history
TOPS12
The feature Calling Restrictions for Wholesaling (59006832), UNBN0006,
adds field SCRNIDX.
OSSPROV
Table name
Operation System Support Provisioning Table
Table OSSPROV stores all provisioning data for operation systems. Table
OSSPROV contains a base common interface for all operation systems using
table OSSPROV. The base interface contains the fields OSNAME, OSINFO
and OSTYPE.

There is no requirement to datafill other tables prior to table OSSPROV..
Table size
Up to 256 tuples
Table OSSPROV is static with a fixed size of 256 bytes.
The physical store for a tuple with integrated test system (ITS) refinements is
a description (DESC) of the physical tuple which is 40 words in protected
store. This table can be incremented by eight tuples, up to a maximum of 255.
Increasing the table size is allowed as long as the maximum tuples in table
OSSPROV is not exceeded, that is table OSSPROV already has 256 tuples and
not all of them are tuples with ITS OSTYPE. In this case, the physical table
for ITS is not allowed to expand.
Datafill
The following table lists datafill for table OSSPROV.
Subfield or
OSNAME see subfield Operation system name

This field consists of subfield OSKEY.
OSKEY alphanumeric Operation system key

(up to 16
Enter the operation key.
characters)
OSINFO see subfield Operation system information

This field consists of subfield OSTYPE.
297-8021-351 Standard 05.02 May 2001

OSSPROV (continued)
Subfield or
OSTYPE ITS Operation system type

Enter the value ITS (integrated test system).
An entry outside this range is invalid.
LANG TL1 Language

Enter TL1. This field is the language
supported by ITS.
ACTTMR 0 to 6000 Activity timeout

Enter the TL1 link activity timeout in seconds.
ITS uses 75 s. If this value is decreased, both
ITS and DMS operations must agree on the
new TL1 timeout value, otherwise the DMS
may constantly reinitialize the TL1 session.
LOGIN LOGINOPT Login

Enter the login option (LOGINOPT).
LOGINOPT N Login option

Enter the login symbolic range option with no
refinements to the LOGIN area. If N (no) is
entered, ISDN TL1 does not require login
procedures in phase 1.
DCTYPE MPC Data communication type

Enter the data communication peripheral
module (PM) connecting the DMS to the
Operation System (OS). The value for this
field is MPC (multiprotocol controller).
MPCINFO see subfields Multiprotocol controller information

This field consists of up to three multiples of
subfields MPCNO and LINKNO. If less than
three multiples are required, end the list with
a $ (dollar sign). Separate each subfield with
a single space.
MPCNO 0 to 255 Multiprotocol controller number

Enter the MPC number.
OSSPROV (end)
Subfield or
LINKNO 0 to 3 Link number

Enter the link number.
VCTYPE SVC Virtual circuit type

Enter the virtual circuit type.
SVCDNA 0 to 9 Switched virtual circuit data network address

This field contains up to three switched virtual
circuit (SVC) data network addresses (DNA).
The calling OS administrator must supply the
DNA values to DMS site operators so that the
values can be datafilled in table OSSPROV.
If less than three SVC DNAs are required, end
the list with a $ (dollar sign).
Datafill example
The following example shows sample datafill for table OSSPROV.
MAP display example for table OSSPROV
OSNAME
OSINFO
___________________________________________________________
BELLSOUTH
ITS TL1 75 N MPC (0 2) (0 3) $ SVC (7654909) (8375978) $
297-8021-351 Standard 05.02 May 2001

OVSBILL
Table name
TOPS Overseas Billing Restrictions Table
Table OVSBILL contains the following information for each countrty listed in
the table:
If collect calls to the COUNTRY in question are permitted, and if so, if
they are permitted for station to station calls only, or if they are permitted
provided they are handled by the overseas operating center.
If STA is flashed on the operator console if the operator attempts to
complete a station call to the specified country.
If third-number billing is legal for calls to the country.
If terminating call screening is applied for this country on Automatic
Calling Card Service (ACCS) calls from certain coin or restricted
telephone stations.
If terminating call screening is applied for this country on Automated
Alternate Billing Service (AABS) calls from certain coin or restricted
telephone stations.
If a given country is not listed in the table then the following applies:
all collect calls are permitted
station calls to the specified country are not flagged by flashing STA
third-number billing is legal
terminating code screening does not apply
The names of the countries listed in table OVSBILL must first be entered in
table COUNTRY.
Overseas Operating Center

Prior to BCS36, use table OOCBILL instead of table OVSBILL. In BCS36,
the OOC and AOSS tables are no longer supported.

Table COUNTRY must be datafilled before table OVSBILL.
OVSBILL (continued)
Datafill
The following table lists datafill for table OVSBILL.
Subfield or
COUNTRY alphabetic Key country name. Enter the country name

(up to 16 as previously datafilled in table COUNTRY,
characters) where the country is associated with its
country code.
COLLECT ALW, DEN, Collect calls. Enter ALW if collect call to the
OOC, or PER country are allowed. Enter DEN if collect call
to the country are denied. Enter OOC if
collect calls to the country are allowed but
handled by the overseas operating center
(OOC). Enter PER if person-to-person
collects calls only are allowed.
PERONLY Y or N Person-to-person only. Enter Y (yes) to

indicate that STA is to be flashed on
operator's screen if the operator attempts to
complete a station call to the specified
country. Otherwise, enter N (no).
THIRDOK Y or N Third number billing OK. Enter Y to indicate

that third number billing is legal for calls to this
country. Otherwise, enter N.
CCSCRN Y or N Calling card screening. In offices with

features AJ0914 and NC0021 (TOPS:
Terminating Code Screening), enter Y to
indicate that terminating code screening is to
be applied for this country. Terminating code
screening is only applied to Automatic Calling
Card Service (ACCS) calls from coin or
restricted telephone stations listed in table
TERMSCRN. Otherwise, enter N.
297-8021-351 Standard 05.02 May 2001

OVSBILL (end)
Subfield or
COLSCRN Y or N Collect call screening. In offices with features

AJ0914 and NC0021, enter Y to indicate that
terminating code screening is to be applied
against collect calls for this country.
Terminating code screening is only applied to
Automated Alternate Billing Service (AABS)
or ACCS calls from coin or restricted
telephone stations. Otherwise, enter N.
THRDSCRN Y or N Third party billing screening. In offices with

features AJ0914 and NC0021, enter Y to
indicate that terminating code screening is to
be applied for this country, against calls for
this country. Terminating code screening is
only applied to AABS or ACCS calls from coin
or restricted telephone stations. Otherwise,
enter N.
Datafill example
The following example shows sample datafill for table OVSBILL.
MAP display example for table OVSBILL
COUNTRY COLLECT PERONLY THIRDOK CCSCRN COLSCRN THRDSCRN

_________________________________________________________________
FRANCE PER Y N Y Y N
ANDORRA DEN N N N N N
OVSCC
Table name
TOPS Overseas Credit Card Table
For each country listed, table OVSCC gives the following parameters used by
the Traffic Operator Position System (TOPS)-DMS program to check on the
validity of the overseas credit card number:
minimum and maximum number of characters in the credit card number,
including the country code and year letter
day on which a new credit card becomes valid and day on which an old
credit card expires
year letter which relates the credit card with a specific year
For related information, refer to table HOTLIST.

Table COUNTRY must be datafilled before table OVSCC.
Datafill
The following table lists datafill for table OVSCC.
Subfield or
COUNTRY alphabetic Key country name. This field is the key to the
(up to 16 table. Enter the country name as previously
characters) datafilled in table COUNTRY, where the
country is associated with its country code.
MINCHARS 2 to 17 Minimum number of characters. Enter the

minimum number of characters in the credit
card number, including the country code and
year letter.
MAXCHARS 2 to 17 Maximum number of characters. Enter the

maximum number of characters in the credit
card number, including the country code and
year letter.
297-8021-351 Standard 05.02 May 2001

OVSCC (end)
Subfield or
STARTDT DEC1 Start date. Enter DEC1 or JAN1 to indicate

or the day on which the new overseas credit
JAN1 card number becomes valid. The year letter in
the overseas credit card number relates it to a
specific year.
ENDDT DEC31 End date. Enter DEC31 or JAN31 to indicate

or the day on which the old overseas credit card
JAN31 number expires.
Datafill example
The following example shows sample datafill for table OVSCC.
MAP display example for table OVSCC
COUNTRY MINCHARS MAXCHARS STARTDT ENDDT

________________________________________________________
AUSTRALIA 12 12 JAN1 DEC31
TURKEY 12 12 DEC1 JAN31
KUWAIT 13 13 DEC1 DEC31
OVSCCYL
Table name
TOPS Overseas Credit Card Year Letter Table
Table OVSCCYL lists the year letter for the present year and the year letter for
the previous year.
On December 1 of each year, the present year letter is moved to the previous
year letter and the year letter of the coming year is entered as the present year
letter.
Because the information recorded on the form is normally considered

confidential by the operating company, the form is not prepared until
immediately before cutover and at the beginning of each year. The form is
released to persons on a need-to-know basis only.

There is no requirement to datafill other tables prior to table OVSCCYL.
Datafill
The following table lists datafill for table OVSCCYL.
Field descriptions
Subfield or
WHEN PRESENT When. Enter PRESENT or PREV to define

or the year as current or previous respectively.
PREV
LETTER alphabetic Year letter. Enter the year letter for each of
capital the current and previous years. On
(1 character) December 1 of each year the present year
letter replaces the previous year letter, while
the year letter of the coming new year is
entered as the present year letter.
Datafill example
The following example shows sample datafill for table OVSCCYL.
297-8021-351 Standard 05.02 May 2001

OVSCCYL (end)
MAP display example for table OVSCCYL
WHEN LETTER
________________________________________________________
PREV T
PRESENT M
OVSRS
Table name
TOPS Overseas Rate Step Table
Table OVSRS lists the applicable rate schedule name and rate step value for
each combination of tariff and country, both required to index into table
SCHED.
For related information, refer to table COUNTRY.
Tops Mass Table Control

Feature V0178 (TOPS Mass Table Control) permits data changes in table
OVSRS to be mass-table-controlled. In other words, the feature permits the
simultaneous activation of data changes in the table by entering the data
changes for the table into table OVSRSI, and then, when all the required
changes are entered, swap the contents of table OVSRS with table OVSRSI.
For further information on feature V0178, refer to table CHARGEI.
Overseas Operator Center (OOC)

Table OVSRS provides the schedule name and rate step information for each
country based on the calling tariff. The rate step information is provided by
Telecom Canada using the point-to-point method for rate step calculation.

The following tables must be datafilled before table OVSRS.
SCHED
COUNTRY
TARIFF
Table size
0 to 16 384 tuples
297-8021-351 Standard 05.02 May 2001

OVSRS (continued)
Datafill
The following table lists datafill for table OVSRS.
Field descriptions
Subfield or
TRFCTY see subfields Tariff-country key. This field consists of

subfields TARIFF and COUNTRY.
TARIFF alphanumeric Tariff. Enter the tariff associated with the

(up to 32 calling number numbering plan area (NPA)
characters) and NXX as previously defined in table
TARIFF.
COUNTRY alphabetic Country name. Enter the called country name

(up to 16 as previously defined in table COUNTRY.
characters)
SCHNAME alphanumeric Schedule name. Enter the name of the

(up to 17 overseas schedule assigned to this
characters) combination of calling tariff and called country
as previously defined in table SCHED.
RATESTEP 0 to 998 Rate step. Enter the rate step value

associated with this combination of calling
tariff and called country.
Datafill example
The following examples show sample datafill for table OVSRS.
The first example shows datafill for the North American Traffic Operator
Position System (TOPS).
MAP display example for table OVSRS
TRFCTY
SCHNAME RATESTEP
________________________________________________________
BELLONT ANDORRA
OVSH 537
OVSRS (end)
MAP display example for table OVSRS
TRFCTY
SCHNAME RATESTEP
________________________________________________________
STKITTS1 GREATBRITAIN
UK 536
297-8021-351 Standard 05.02 May 2001

OVSRSI
Table name
TOPS Overseas Rate Step Inactive Table
OVSRS to be mass-table-controlled. In other words, the feature permits the
changes for the table into table OVSRSI, and then, when all the required
changes are entered, swap the contents of table OVSRS with table OVSRSI.
Refer to table OVSRS.

Table size
Datafill
Datafill example
OWATZONE
Table name
OUTWATS Zone Table
Outwards wide area telephone service (OUTWATS) is a feature designed to
meet the needs of subscribers who make a substantial number of long distance
calls. This feature is provided in terms of geographical regions called zones,
with the subscriber purchasing as many lines for each zone as required.
The OUTWATS feature supports a total of 13 zones. These zones are referred
to as zones 0 to 9, A, B, and C. Zones A, B, and C are recorded on billing
records as zones 10, 11, and 12 respectively.
The arrangement of the zones, which is dependent on local tariffs, varies

slightly between the U.S. and Canadian systems. Coverage, in accordance
with the digits dialed, is in concentric zones about the home numbering plan
area (NPA). Each zone includes all contained zones of the same type.
In Canada, the zones are typically numbered from 1 to 6, with zone 1 being the
home NPA and zones 2 to 6 covering areas of increasing size.
In the U.S., the zones are typically broken up into two types:
Intrastate zones 8, 9, and 0 are used for areas of increasing size within the
home state.
Interstate zones 1 to 6 cover the U.S. excluding the home state. Zones 1 to
5 cover increasingly large areas of the contiguous 48 states, plus Puerto
Rico and the Virgin Islands. Zone 6 includes zone 5 plus Hawaii and
Alaska.
The zones assigned to non-Integrated Business Network (IBN) lines are

defined in the datafill for the OUTWATS line in table LENFEAT.
The zones assigned to the access codes for IBN OUTWATS lines are defined
in table IBNXLA. A unique access code can be assigned for each zone. Calls
are checked to determine whether they are within the zone assigned to the
access code.
Since zones are ordered by increasing area, with each zone including all
previous zones (within the zone type), it is acceptable to use a number that is
higher than the called number requires. In such a case, the system determines
the appropriate zone based upon the called number. Users can take advantage
297-8021-351 Standard 05.02 May 2001

OWATZONE (continued)
of this by memorizing the access code for the highest (all-encompassing) zone,
which can be assigned to all zones.
Table OWATZONE lists the zone for each set of digits that is assigned an
OUTWATS zone in each home or serving NPA. The key to the table consists
of the home or serving NPA and the digits that define the number assigned to
the zone. The number of digits can be within the range of 1 to 18, but is
normally within the range of 3 to 6.
If the number dialed is a seven-digit number, the table is searched for this
number with a home NPA prefix. If it is not found, the table is searched for the
actual number dialed.
If the number dialed is a ten-digit number, the table is searched for the digits
dialed. Additional digits can be specified if required (for example, situations
where six-digit screening is needed). See the example for the different
methods of assigning numbers.
Table OWATZONE is accessed during call processing to determine the

destination zone (the zone of the called number). The switch, having both the
zone allowed for the calling line and the destination zone, accesses table
ZONEORDR to check whether or not the call is allowed. If the destination
code is included in the zone of the calling line, the call is allowed to complete.
If the number dialed is 800, the originator is routed to misdirected CAMA

(centralized automatic message accounting) call (MSCA) treatment.
If the number dialed is 555 or NPA+555 and the 555 entry is datafilled in table
OWATZONE with the same zone number as the subscriber, the call completes
as dialed.
If the number dialed has not been datafilled or is out of zone and the originator
is a non-IBN OUTWATS line, the call is routed to the treatment specified by
the entry in table LENFEAT for the OUTWATS line. If it is an IBN line, the
call is routed to the flexible intercept number for the route list that is assigned
to the OUTWATS access code in table IBNXLA.
In a local without local automatic message accounting (LAMA) switching unit

and with non-IBN OUTWATS, where local calls are charged, the local codes
must be routed over the CAMA trunk group, through table CSVSCRC, to the
toll office for registration of calls on automatic message accounting (AMA)
tape.
For non-IBN OUTWATS lines that do not require the prefix digit (1+) to be
dialed, the standard pretranslator associated with the OUTWATS lines must
have the type-of-call field (TYPCALL) set to direct dial (DD) so that calls are
recorded on AMA tape.
The standard pretranslator and class of service screening subtable names that
are associated with non-IBN OUTWATS lines are specified in table
LINEATTR.

The SNPAs must be datafilled prior to table OWATZONE.
Table size
4096 tuples (recommended maximum)
Memory is automatically allocated for table OWATZONE.
Datafill
The following table lists datafill for table OWATZONE.
Field descriptions
Subfield or
OWATCODE see subfields OUTWATS code

This field, which is the key to the table,
consists of subfields SVGNPA and DIGITS.
SVGNPA numeric Serving NPA

Enter the serving numbering plan area (NPA).
DIGITS numeric (up to Digits

18 digits)
Enter the digits that further define the zone.
ZONE 0 to 9, A, B, or OUTWATS zone

C
Enter the OUTWATS zone number that is
assigned to the key OWATCODE.
Datafill example
The following descriptions apply to the example of datafill for table
OWATZONE shown below.
Entry a is for home or serving NPA 613 with all codes in zone 1.
Entry b is for a home or serving NPA of 819 with the code specified
individually for numbers starting 819226. This approach uses more store
297-8021-351 Standard 05.02 May 2001

that used by entry a, but more clearly defines the codes. An NPA can have
entry a or b, but not both.
Entry c indicates that code 613225 (zone 3) is not in the same zone as entry
a.
Entry d is for a foreign numbering plan area (FNPA) where all codes are in
the same zone.
Entries e show the case where individual data is specified for each code
within the FNPA. An NPA can have entries of type d or e, but not both.
Entry f shows the case where code 416526 is not in the same zone as
defined in entry d.
Entry g shows the case where all NNX codes in the FNPA, starting with
digit 4, are not in the same zone as defined in entry d.
Entries h and d are examples of ambiguous codes.
MAP display example for table OWATZONE
OWATZONE ZONE
______________________________________________________
613 613 1 a
613 613225 2 c
613 4166325 1 e
613 416326 1 e
819 416 2 d
819 4164 3 g
819 819416 1 h
819 819226 1 b
819 416526 3 f
After items d and g are entered as input, 613416 is defined as follows:

Definition of 613416 (Sheet 1 of 2)
SNPA Digits Zone Remarks
613 4160 2 Default entry for 416
OWATZONE (end)
Definition of 613416 (Sheet 2 of 2)
SNPA Digits Zone Remarks
613 4164 3 Entry for 4164
297-8021-351 Standard 05.02 May 2001

OWNER
Table name
Owner Table
Overview
Seven tables are associated with feature BR0745 (Customer Data Change
Inventory System), and feature BC1459 (Partitioned Table Editor):
CDCDNS - Customer Data Change Directory Number Table
CDCLENS - Customer Data Change Line Equipment Number Table
CDCLOGON - Customer Data Change Logon Table
CDCOPTS - Customer Data Change Options Table
DATAOWNR - Data Owner Table
OWNER - Owner Table
OWNTAB - Ownership Table
These tables are optional and are only provided in switching units provisioned
with the Customer Data Change (CDC) Inventory System and Partitioned
Table Editor (PTE) features. The CDC and PTE features require the Enhanced
Security and Command Screening software features.
The CDC and PTE features enable non-operating-company users to log onto
the switching unit to view and modify certain routing, translation, and line
data. Changes can be made only by using the Service Order System
(SERVORD) or the PTE feature.
Non-operating-company users can have access to a table or subtable only if the

privilege class assigned to the table or subtable (by means of tables
CUSTPROT and SUBPROT) matches the command class of the user.
A list of steps required to set up a CDC user is shown in the following

procedure. These steps must be followed precisely when setting up a CDC
user in the switching unit.
To set up a CDC user in the switching unit:

1. Datafill table TERMDEV for the new CDC user.
2. The following is an example of a file:
ATTACH USERS. OPERATOR PROFILE LOGIN < user profile name >
PROFILE RESTART < user profile name > LOGOUT
OWNER (continued)
3. Edit a second file that is a user's profile read by the command interpreter
(CI).
4. The following is an example of the file:
CDCSETUP < user class >

5. From the operator position enter:
>PERMIT userid pass priority stksize cmdclass
>LOGIN userid pass < first file > sink
The CDC user can now log on and use the CI and SERVORD commands.
One entry is required in this procedure for each name that is assigned as an
owner. One or more customer groups can be assigned to an owner. The data
for each owner specifies whether other owners are allowed to look at the data
belonging to this owner.

There is no requirement to datafill other tables prior to table OWNER.
Table size
1 to 256 tuples
Datafill
The following table lists datafill for table OWNER.
Field descriptions
Subfield or
OWNER alphanumeric Owner

(vector of up
Enter the name assigned to the owner.
to 8
characters)
PUBLIC Y or N Public
Enter Y (yes), if other owners are allowed to
look at this owner's data. Otherwise enter N
(no).
297-8021-351 Standard 05.02 May 2001

OWNER (end)
Datafill example
An example of datafill for table OWNER is shown below. This example shows
an owner of a group of customer groups with the name CARLING. Other
owners are not allowed (PUBLIC = N) to look at data belonging to this owner.
MAP display example for table OWNER
OWNER PUBLIC
________________________________________________________
CARLING N
OWNTAB
Table name
Ownership Table
Table OWNTAB is used with features BR0745 (Customer Data Change
Inventory System) and BC1459 (Partition Table Editor).
Table OWNTAB is an ownership-enforced table and defines the access rights

of various users. Table OWNTAB is a read-only table and is automatically
datafilled during the loadbuild process.
The data in table OWNTAB, in conjunction with the data in table

DATAOWNR, defines which entries in the tables listed in field TABNAME
can be changed or viewed by non-operating-company users.
Table OWNTAB contains ownership information for a table or subtable. The

information is used by the partitioned table editor (PTE) command to check
ownership of a tuple in that table or subtable for a customer data change (CDC)
user.
For related information, see table OWNER.

Table VFGDATA must be datafilled before table OWNTAB.
Table size
1 to 64 tuples
Datafill
The following table lists datafill for table OWNTAB.
Subfield or
TABNAME see subfields Table name

This is the key field. It consists of subfields
TABNAME and SUBNAME.
TABNAME alphanumeric Table name

(up to 16
This subfield contains the table to which
characters)
ownership applies.
297-8021-351 Standard 05.02 May 2001

OWNTAB (continued)
Subfield or
SUBNAME alphanumeric Subtable name

(up to 16
This field contains the subtable to which
characters)
ownership applies. If no subtable exists, this
subtable contains a $.
KEYINDEX INDEX or Index or key

KEY
This field specifies whether KEY (field
TABNAME) or INDEX (field INDEXFS) is
used to map the data into a form that can be
used to read table DATAOWNR.
INDEXFS alphanumeric Index field

(up to 2
If the entry in field KEYINDEX is INDEX, the
vectors of up
field and table name specified in this field are
to 32
used to map the data into a form that can be
characters)
used to read table DATAOWNR.
OWNDATA see subfields Owner data

This field consists of subfields OWNTABID
and FIELD_SPEC.
OWNTABID alphanumeric Owner data

This field contains the table that identifies
data ownership. For the list of available
tables, see the section Datafill example"
contained in this table description.
FIELD_SPEC alphanumeric Field specification

(vector of up
This field is used in conjunction with the data
to 32
in field OWNTABID to determine the
characters)
ownership of the tuple. The resulting type
must match the type that results from the
value of field INDEXFS.
Datafill example
The following example shows sample datafill for table OWNTAB.
OWNTAB (end)
MAP display example for table OWNTAB
TABNAME KEYINDEX
INDEXFS
OWNDATA
_____________________________________________________________________
AUTHPART $ INDEX
( PARTNO)$
(AUTHPART AUTHNAME)$
AUTHCDE $ INDEX
( INDEX$PARTNO)$
(AUTHPART AUTHNAME)$
DIGMAN $ KEY
( DMIKEY)$
( DIGMAN DMIKEY)$
CODEBLK $ KEY
( CRLKEY$CUSTOMER)$
( CUSTGRP CUSTNAME)$
COSMAP $ INDEX
( IX)$
( COSMAP COSNAME)$
COSDATA $ KEY
( KEY$COSNUM)$
( COSMAP COSNAME)$
297-8021-351 Standard 05.02 May 2001

PACMAN
Table name
IBN ESN Protocol Analysis and Code Manipulation Table
Table PACMAN contains the protocol analysis and code manipulation for
electronic switched network (ESN) signaling formats incoming on an
Integrated Business Network (IBN) trunk group type IBNTI or IBNT2.
Table PACMAN is used to interpret the ESN call types and subtypes for
incoming calls.
If feature BC1459 (Partitioned Table Editor) was purchased, the ownership of

each tuple in table PACMAN is defined in tables DATAOWNER and
OWNTAB.
The entries in table DATAOWNR applicable to table PACMAN are those that
have the entry in field TABNAME equal to CUSTGRP and the entry in field
PMI equal to the value of field PMI in table PACMAN.
The entry in table OWNTAB applicable to table PACMAN is the one that has
the entry in field TABNAME equal to PACMAN.

The following tables must be datafilled before table PACMAN.
COSMAP
OWNTAB
Table size
0 to 255 tuples
PACMAN (continued)
Datafill
The following table lists datafill for table PACMAN.
Subfield or
PMI 0 to 255 Protocol manipulation index

Enter the protocol manipulation index to the
protocol analysis and code manipulation
(PACMAN) program.
PGM see subfield Protocol analysis and code manipulation

program vector
This field consists of up to 16 multiples of
subfield CMD and its refinements. If less than
16 multiples are required, end the list with a $
(dollar sign).
CMD END, FLD, or Protocol analysis and code manipulation

SET command
Enter the PACMAN command code.
Enter END if no more program commands are
to be entered. No refinements require datafill.
If translation is to extract a specified number
of leading or trailing digits from incoming
digits and then proceed to tables COSDATA
and COSMAP with the index provided to
screen and map the digits thus extracted to a
network class of service (NCOS) value, enter
FLD and datafill refinement FIELD_DATA.
If the incoming call is associated with the call
characteristics DIGDATA or SAT, enter SET
and datafill refinements CALLCHR and
VALUE.
CALLCHR DIGDATA or Call characteristic

SAT
If the entry in subfield CMD is SET, datafill this
refinement. If the incoming call has a digital
trunk connection to an electronic tandem
network (ETN) or electronic switched network
(ESN), enter the call characteristic DIGDATA.
If incoming call comes through satellite, enter
the call characteristic SAT (satellite).
297-8021-351 Standard 05.02 May 2001

PACMAN (continued)
Subfield or
VALUE Y or N Value
If the entry in subfield CMD is SET, datafill this
refinement. Enter Y (yes) or N (no) as the
value given to the call characteristic.
FIELD_DATA see subfield Field data

If the entry in subfield CMD is FLD, datafill this
refinement. This field consists of subfield
FIELD and refinements NUMDIGS and
COSMAP.
FIELD COS, DCOS, Field to be extracted from inpulsed digits

or TCOS
Enter COS if leading digits are extracted from
the inpulsed digits.
Enter DCOS if the trailing digits extracted
from the inpulsed digits of a digital data call
are compared with the value of parameter
DATACOS in table OFCSTD.
Enter TCOS if trailing digits are extracted
from the inpulsed digits of a non-digital data
call.
NUMDIGS 0 to 15 Number of inpulsed digits to be extracted

Enter the number of digits extracted from the
inpulsed digits.
COSMAP alphanumeric COSMAP index

(1 to 16
Enter the index into tables COSMAP and
characters)
COSDATA, where the extracted inpulsed
digits are screened and mapped to a network
class of service (NCOS).
Datafill example
The following example shows sample datafill for table PACMAN.
PACMAN (end)
MAP display example for table PACMAN
PMI
PGM
________________________________________________________
7
(FLD COS 2 ITCOSMAP) (END )$
297-8021-351 Standard 05.02 May 2001

PADDATA
Table name
Pad Data Table
Table PADDATA contains attenuation and boost settings for connections
through different devices. Pads are applied to devices in order to balance
volume levels across the network.
This document describes how DMS-100 and DMS-100/200 switching units

use table PADDATA. This document does not describe how SL-100 switching
units use this table.
The fixed loss plan uses an index from each party in calls that access table
PADDATA. The data fields of tables TRKGRP, CONF3PR, CONF6PR,
CPOS, and TOPSPOS contain this index. The system stores an index for each
line.
Operating company maintenance personnel use digital pads to equalize

differences between trunk groups. Table PADDATA does not affect the digital
pads currently in use on the trunk modules (TM).
Table PADDATA stores the transmit and receive pad values inserted in this
type of connection. The two-part key contains two pad group names. The
associated data contains the pad values for connections between the specified
pad groups.
Call processing determines where the system implements the pad value. The
subscriber cannot control this process. If the connection involves a line, the
operating company normally sets the pad in the line card in the receive
direction. To set the value of 14L in field PAD1TO2 and field PAD2TO1, you
must use the line and network pads together. The value of 14L indicates a loss
of 14 dB. See the second example in Section Additional information for a
description of this value.
The subscriber can define 21 of the 64 possible pad groups. The 43 pad groups
that remain are reserved pad groups. The names of 38 of these pad groups
appear in table PADDATA. See proposed pad group names.
Of the 38 defined pad groups, 16 pad groups are in table PADDATA when you
enter data in this table. These pad groups appear in the following table. These
pad groups have default values for fields PAD1TO2 and PAD2TO1. These
values appear in the table in Section Default keys and recommended
DMS-100 loss values.
DMS-100 Family Customer Data Schema Reference Volume 9 of 12, SN07 (DMS) and up
PADDATA (continued)
Pad groups at datafill
Pad group Description
STDLN standard line
UNBAL unbalanced line
LRLM remote line module (RLM)
IAO plain ordinary telephone service (POTS) intraoffice trunk
LCO POTS collocated step-by-step (SXS) trunk
ELO POTS interoffice trunk
ETLS POTS end office trunk (short distance)
ETLL POTS end office trunk (long distance)
TLA POTS toll connecting trunk (TCT) to toll trunk
TLD POTS TCT to toll trunk (digital)
PPHON P-phone line
PRAC primary node access (PRA)
DAVLN data above voice line
PKLNL Gateway line that has GRPTYPE set to S in table

LGRPINV
PKNIL Gateway line that has GRPTYPE set to C in table

LGRPINV
CONF conference circuit
CPOS centralized automatic message accounting (CAMA)

position
TPOS Traffic Operator Position System (TOPS) position
A nil pad group (NPDGP) appears in table PADDATA. A tuple that uses the
nil pad group can contain only 0 0 settings. Table PADDATA has to have the
tuple (NPDGP NPDGP 0 0) datafilled for the pad group NPDGP to prevent
echo problems on trunks. The tuple cannot contain other values.
297-8021-351 Standard 10.02 December 2004

PADDATA (continued)
The central control (CC) instructs the connecting peripheral modules (PM) to
use a 0 dB pad level on the line card gain setting. The CC instructs the PMs to
use this level on the line card gain setting for all line connections to
announcements. This value is a default value. You cannot administer this
value.
The reserved 38 pad groups with defined names are as follows:

Nil pad group:
NPDGP, not normally used
Pad groups for POTS lines:
UNBAL (unbalanced line)
STDLN (standard line)
LRLM (line is on a remote line module [RLM] > 80 km)
Pad groups for gateway lines:
PKLNL (gateway line with GRPTYPE S in table LGRPINV
PKNIL (gateway line with GRPTYPE C in table LGRPINV)
Station is a line or attendant console. Pad groups for Integrated Business
Network (IBN) lines:
ONS (on-premises station)
OPS (off-premises station)
Pad group for P-phone lines:
PPHON (P-phone set)
Pad groups for POTS trunks:
IAO (intraoffice trunk)
LCO (collocated-SXS in the same office)
ELO (interoffice trunk, class 5 office)
ELOA (interoffice trunk, analog class 5 office)
ELOD (interoffice trunk, digital class 5 office)
ETLS (end office toll < 320 km between 2 class 5 offices)
ETLL (end office toll > 320 km between 2 class 5 offices)
TLA (TCT to toll office analog [class 4])
TLD (TCT to toll office digital [class 4])
ITTA (intertoll trunk to analog toll office)
PADDATA (continued)
ITTD (intertoll trunk to digital toll office)
Note: ITTD is recommended when trunking to Nortel CDMA sites.
SAT (satellite office)

Pad group for echo suppressors:
DES (digital echo suppressors)
Pad group for conference bridges:
CONF (conference circuit)
Pad groups for CAMA and TOPS positions:
CPOS (CAMA position)
TPOS (TOPS position)
Pad groups for IBN trunks:
ATT (analog trunk interface to analog tie trunk)
DTT (digital trunk interface to digital or combination tie trunk)
CTT (combination tie trunk)
SATT (analog trunk interface to analog satellite private branch
exchange [PBX] tie trunk)
SCTT (digital trunk interface to combination satellite PBX tie trunk)
SDTT (digital trunk interface to digital satellite PBX tie trunk)
ACO (analog trunk interface to analog central office [CO] trunk)
DCO (digital trunk interface to digital or combination CO trunk)
ATO (analog trunk interface to analog toll office [TO] trunk)
DTO (digital trunk interface to digital or combination TO trunk)

PADDATA (continued)
Pad group for receivers:

RCVR, multifrequency [MF] and dual-tone multifrequency [DTMF]
receivers, for selection of network pad values for trunk to receiver
connections
Pad group for PRA:
PRAC (PRA interface)
Pad group for data above voice lines:
DAVLN (data above voice line)
Adding pad groups

You can add pad groups. The operating company can add pad groups to the
proposed pad groups or define pad groups to add. The entry of the proposed
pad groups is not a requirement. You can enter a maximum of 24 pad groups.
To create new pad groups, you can add the groups as keys in fields PADGRP1
and PADGRP2 of table PADDATA. To use pad groups as line or trunk data,
make sure the pad groups are in table PADDATA.
Modifying pad groups

You can change the pad values in table PADDATA. Checks to make sure the
specified values apply for the agent that uses the pad group do not occur.
Deleting pad groups

Deletion of a table entry sets the internal data to represent 0 pad settings. If
you delete all references to a pad group that the subscriber defines from the
table, the system removes the key. The entry NPDGP is the nil pad group entry
in fields PADGRP1 and PADGRP2. This entry replaces references to the
deleted pad group.
Note: Deletion of all entries of a defined pad group removes all table
entries. Deletion of entries does not remove the pad group name from the
key range. Data references can reference the pad group. This action sets the
pads to 0.
Access restriction to table PADDATA

To restrict access to table PADDATA, enter data in table CUSTPROT. You
must use this method to restrict access for United Kingdom operating
companies. Table PADDATA contains the pad group values. Personnel that
are not authorized must not change the values in this table.
PADDATA (continued)
Default keys and recommended DMS-100 loss values

The default values for fields PAD1TO2 and PAD2TO1 appear in the following
table.
PADGRP1 PADGRP2 PAD1TO2 PAD2TO1
STDLN STDLN 0 0
UNBAL STDLN 2L 2L
UNBAL UNBAL 2L 2L
LRLM STDLN 2L 2L
LRLM UNBAL 2L 2L
LRLM LRLM 2L 2L
IAO STDLN 0 0
IAO UNBAL 0 0
IAO LRLM 0 0
IAO IAO 0 0
LCO STDLN 1L 0
LCO UNBAL 1L 0
LCO LRLM 1L 0
LCO IAO 0 0
LCO LCO 0 0
ELO STDLN 3L 0
ELO UNBAL 3L 0
ELO LRLM 3L 0
ELO IAO 0 0
ELO LCO 2L 0
ELO ELO 0 0
Note: The value in field PAD2TO1 is 3 dB less than the accurate loss. A 3 dB
fixed pad in the NT6X21 line card causes this condition.

PADDATA (continued)
ETLS STDLN 3L 0
ETLS UNBAL 3L 0
ETLS LRLM 3L 0
ETLS IAO 0 0
ETLS LCO 2L 0
ETLS ELO 3L 3L
ETLS ETLS 3L 3L
ETLL STDLN 6L 0
ETLL UNBAL 6L 0
ETLL LRLM 6L 0
ETLL IAO 3L 0
ETLL LCO 5L 0
ETLL ELO 3L 0
ETLL ETLS 3L 0
ETLL ETLL 0 0
TLA STDLN 5L 0
TLA UNBAL 5L 0
TLA LRLM 5L 0
TLA IAO 3L 0
TLA LCO 4L 0
TLA ELO 3L 0
TLA ETLS 3L 0
TLA ETLL 0 0
PADDATA (continued)
TLA TLA 0 0
TLD STDLN 6L 0
TLD UNBAL 6L 0
TLD LRLM 6L 0
TLD IAO 3L 0
TLD LCO 5L 0
TLD ELO 3L 0
TLD ETLS 3L 0
TLD ETLL 0 0
TLD TLA 0 0
TLD TLD 0 0
CONF STDLN 6L 0
CONF UNBAL 6L 0
CONF LRLM 6L 0
CONF IAO 3L 0
CONF LCO 5L 0
CONF ELO 3L 0
CONF ETLS 3L 0
CONF ETLL 0 0
CONF TLA 0 0
CONF TLD 0 0
CONF CONF 0 0
CPOS STDLN 6L 0

PADDATA (continued)
CPOS UNBAL 6L 0
CPOS LRLM 6L 0
CPOS IAO 3L 0
CPOS LCO 5L 0
CPOS ELO 3L 0
CPOS ETLS 3L 0
CPOS ETLL 0 0
CPOS TLA 0 0
CPOS TLD 0 0
CPOS CONF 0 0
CPOS CPOS 0 0
TPOS STDLN 6L 0
TPOS UNBAL 6L 0
TPOS LRLM 6L 0
TPOS IAO 3L 0
TPOS LCO 5L 0
TPOS ELO 3L 0
TPOS ETLS 3L 0
TPOS ETLL 0 0
TPOS TLA 0 0
TPOS TLD 0 0
TPOS CONF 0 0
TPOS CPOS 0 0
PADDATA (continued)
TPOS TPOS 0 0
PPHON STDLN 0 0
PPHON UNBAL 2L 0
PPHON LRLM 2L 0
PPHON IAO 0 0
PPHON LCO 0 0
PPHON ELO 0 0
PPHON ETLS 0 0
PPHON ETLL 0 3L
PPHON TLA 0 2L
PPHON TLD 0 3L
PPHON CONF 0 3L
PPHON CPOS 0 3L
PPHON TPOS 0 3L
PPHON PPHON 0 0
DAVLN UNBAL 2L 5L
DAVLN STDLN 0 3L
DAVLN LRLM 2L 5L
DAVLN DAVLN 3L 3L
DAVLN SPPHN 0 3L
DAVLN IAO 0 3L
DAVLN LCO 0 4L
DAVLN ELO 0 6L

PADDATA (continued)
DAVLN ETLS 0 6L
DAVLN ETLL 0 7L
DAVLN TLA 0 6L
DAVLN TLD 0 7L
DAVLN CONF 0 7L
DAVLN CPOS 0 7L
DAVLN TPOS 0 7L
NPDGP NPDGP 0 0
PKLNL NPDGP 0 0
PKLNL UNBAL 6L 6L
PKLNL STDLN 6L 6L
PKLNL LRLM 6L 6L
PKLNL ONS 6L 6L
PKLNL OPS 6L 6L
PKLNL PPHON 6L 6L
PKLNL DAVLN 0 6L
PKLNL SPPHN 0 6L
PKLNL IAO 0 6L
PKLNL LCO 0 6L
PKLNL ELO 0 6L
PKLNL ELOA 0 6L
PKLNL ELOD 0 6L
PKLNL ETLS 0 6L
PADDATA (continued)
PKLNL ETLL 0 6L
PKLNL TLA 0 6L
PKLNL TLD 0 6L
PKLNL ITTA 0 6L
PKLNL ITTD 0 6L
PKLNL SAT 0 6L
PKLNL DES 0 6L
PKLNL CONF 0 6L
PKLNL CPOS 0 6L
PKLNL TPOS 0 6L
PKLNL ATT 0 6L
PKLNL DTT 0 6L
PKLNL CTT 0 6L
PKLNL SATT 0 6L
PKLNL SCTT 0 6L
PKLNL SDTT 0 6L
PKLNL ACO 0 6L
PKLNL DCO 0 6L
PKLNL ATO 0 6L
PKLNL DTO 0 6L
PKLNL RCVR 0 6L
PKLNL PRAC 0 6L
PKLNL PKLNL 3L 3L

PADDATA (continued)
PKNIL NPDGP 0 0
PKNIL UNBAL 6L 6L
PKNIL STDLN 6L 6L
PKNIL LRLM 6L 6L
PKNIL ONS 6L 6L
PKNIL OPS 6L 6L
PKNIL PPHON 0 9L
PKNIL DAVLN 0 9L
PKNIL SPPHN 0 9L
PKNIL IAO 0 9L
PKNIL LCO 0 9L
PKNIL ELO 0 9L
PKNIL ELOA 0 9L
PKNIL ELOD 0 9L
PKNIL ETLS 0 9L
PKNIL ETLL 0 9L
PKNIL TLA 0 9L
PKNIL TLD 0 9L
PKNIL ITTA 0 9L
PKNIL ITTD 0 9L
PKNIL SAT 0 9L
PKNIL DES 0 9L
PKNIL CONF 0 9L
PADDATA (continued)
PKNIL CPOS 0 9L
PKNIL TPOS 0 9L
PKNIL ATT 0 9L
PKNIL DTT 0 9L
PKNIL CTT 0 9L
PKNIL SATT 0 9L
PKNIL SCTT 0 9L
PKNIL SDTT 0 9L
PKNIL ACO 0 9L
PKNIL DCO 0 9L
PKNIL ATO 0 9L
PKNIL DTO 0 9L
PKNIL RCVR 0 9L
PKNIL PRAC 0 9L
PKNIL PKLNL 6L 6L
PKNIL PKNIL 9L 9L
PRAC UNBAL 2L 0
PRAC STDLN 3L 0
PRAC LRLM 3L 0
PRAC PPHON 0 0
PRAC IAO 3L 0
PRAC LCO 3L 0
PRAC ELO 0 0

PADDATA (continued)
PRAC ETLS 0 0
PRAC ETLL 0 0
PRAC TLA 0 0
PRAC TLD 0 0
PRAC CONF 0 0
PRAC CPOS 0 0
PRAC TPOS 0 0
PRAC ATT 3L 0
PRAC DTT 0 0
PRAC PRAC 0 0

You do not need to enter data in other tables before you enter data in table
PADDATA.
You must enter data in table PADDATA before you enter data in the following
tables:
LNINV
TRKGRP
CONF3PR
CONF6PR
CPOS
TOPSPOS
Table size
The system automatically allocates memory for 64 pad groups.
PADDATA (continued)
Datafill
Datafill for table PADDATA appears in the following table.
Field descriptions
Subfield or
PADKEY see subfields Pad data key. This field is the key to table
PADDATA. This field contains subfields
PADGRP1 and PADGRP2.
PADGRP1 alphanumeric Pad group one. Enter the pad group name to
(a maximum enter in field PADGRP of table TRKGRP,
of 5 LNINV, CONF3PR, CONF6PR, CPOS, or
characters) TOPSPOS. The pad group can be one of the
pad groups that the subscriber defines.
PADGRP2 alphanumeric Pad group two. Enter the pad group name to
(a maximum enter in field PADGRP of table TRKGRP,
of 5 LNINV, CONF3PR, CONF6PR, CPOS, or
characters) TOPSPOS. The pad group can be one of the
reserved pad groups or a pad group the user
defines.

PADDATA (continued)
Field descriptions
Subfield or
PAD1TO2 1L to 14L, 0G Pad group one to pad group two. Enter the
to 7G, or 0 value of the network or line pad for the
(zero) connection between the entry in field
PADGRP1 to the entry in field PADGRP2.
Each entry value corresponds to a gain or
loss level. The value G indicates gain and L
indicates loss.
Note: Gain (G) applies to Series 1

peripherals. Series 1 peripherals are trunk
modules (TM), maintenance trunk modules
(MTM), service trunk modules (STM), line
modules (LM), and remote line modules
(RLM). Entry values that are gains cause a
loss of 0.
PAD2TO1 1L to 14L, 0G Pad group two to pad group one. Enter the
to 7G, or 0 value of the network or line pad for connection
(zero) PADGRP2 to PADGRP1. Each entry value
corresponds to a gain or loss level in decibels.
The value G indicates gain and L indicates
loss.
Note: Gain (G) applies to Series 1

peripherals. Series 1 peripherals are TM,
MTM, STM, LM, and RLM. Entry values that
are gains cause a loss of 0.
Datafill example
Sample datafill for table PADDATA appears in the following examples.
MAP example for table PADDATA
PADKEY PAD1TO2 PAD2TO1

________________________________________________________
NPDGP NPDGP 0 0
PADDATA (continued)
MAP example for table PADDATA
PADKEY PAD1TO2 PAD2TO1

________________________________________________________
L1PAD L2PAD 10L 6L
Table history
SN07 (DMS)
Additional tuple datafilled for pad group NPDGP under CR Q00814439.
SN06 (DMS)
Pad groups PKLNL and PKNIL were added by feature 89009298. Pad group
PKLNL is for use only by gateway lines that have GRPTYPE set to S in the
LGRPINV table. Pad group PKNIL is for use only by gateway lines that have
GRPTYPE set to C in the LGRPINV table. Gateway lines are automatically
allocated the correct pad group when they are provisioned.
BCS36
A description of line connections to announcements was added.
Table PADDATA is not used in TRAVER.
Examples of how to enter data in table PADDATA for specified applications

appear in this section.
Example 1
An example of a line-to-line call appears in the following figure.

PADDATA (continued)
Example 1
Transmit loss
TPAD
Line card Line card
Network
Pad = L1PAD Pad = L2PAD
RPAD
Line 1 Line 2
Receive loss
The call shown above has the following data requirements:

Line 1 connects to line 2.
The line equipment number (LEN) of the line 1 line card is LEN1.
The LEN of the line card for line 2 is LEN2.
The network transmit pad is TPAD.
The network receive pad is RPAD.
Perform the following steps to complete the tables:

Step 1 table LNINV
POS LEN1: Add the name of pad group (L1PAD) to field PADGRP.
POS LEN2: Add the name of pad group (L2PAD) to field PADGRP.
Step 2 table PADDATA
POS L1PAD L2PAD: Add the values to fields PAD1TO2 and
PAD2TO1. The same result can occur with POS L2PAD L1PAD if you
enter the PAD1TO2 and PAD2TO1 values in reverse. If you enter
PAD1TO2 and PAD2TO1 values 5 and 6 for POS L1PAD L2PAD,
enter values 6 and 5 for POS L2PAD L1PAD.
The calculation of the values of the line and network pads for loss is as follows:
If the value of PAD2TO1 is less than 7, the line pad in LEN1 is the value
in field PAD2TO1. The network receive pad (RPAD) is 0.
If the value of PAD2TO1 is not less than 7, the line pad in LEN1 is 7. The
network receive pad (RPAD) has the value in field PAD2TO1 minus 7.
PADDATA (continued)
in field PAD1TO2. The network transmit pad (TPAD) is 0.
TPAD has the value in field PAD1TO2 minus 7.
The transmission loss between line 1 and line 2 can be 10 dB. The receive loss
between line 2 and line 1 can be 6 dB. If these conditions occur, the line and
network pads have the following values:
The pad group in line 1 is set to a loss of 6 dB. The RPAD is 0.
The pad group in line 2 is set to a loss of 7 dB. The TPAD is set to a loss
of 3 dB.
Datafill for example 1
Transmit loss = 10 dB
TPAD = 3
Line card Line card
Network
Pad = 6 Pad = 7
RPAD = 0
Line 1 Line 2
Receive loss = 6 dB
See the Datafill example" section for a MAP display Map example for table
PADDATA of the previous example.
Example 2
If one of the agents is a trunk, a network pad is available for the side of the
trunk agent. In this example, the network receive and transmit pad values are
the same as in table PADDATA. The field PADGRP in table TRKGRP indexes
the pad values for the correct common language location identifier (CLLI).
This example has the following data requirements:

Line 1 connects to a trunk.
The line card for line 1 has a LEN of LEN1.

PADDATA (continued)

The calculation of the values of the line and network pads for loss is as follows:
in field PAD2TO1. The RPAD is 0.
RPAD has the value in field PAD2TO1 minus 7.
The TPAD is the value in field PAD1TO2.
Note: The previous algorithms apply for loss.
The transmission loss between line 1 and the trunk can be 10 dB. The receive
loss between the trunk and line 1 can be 6 dB. If these conditions occur, the
line and network pads have the following values:
The pad group in line 1 is set to a loss of 6 dB.
The RPAD is 0.
The TPAD is set to a loss of 10 dB.
Example 2
TPAD = 10
Line card Trunk card
Network
Pad = 6
RPAD = 0
Line 1
Receive loss = 6 dB
Example 3
This example has the following data requirements:
A trunk connects to line 2.
The line card for line 2 has a LEN of LEN2.
PADDATA (end)

The calculation of the values of the line and network pads for loss is as
follows:
If the value of PAD1TO2 is less than 7, the line pad in LEN2 is the
value in field PAD1TO2. The TPAD is 0.
If the value of PAD1TO2 is not less than 7, the line pad in LEN2 is 7.
The TPAD has the value in field PAD1TO2 minus 7.
The RPAD is the value in field PAD2TO1.
The transmission loss between the trunk and line 2 can be 10 dB. The receive
loss between the trunk and line 2 can be 6 dB. If these conditions occur, the
line and network pads have the following values:
The RPAD is set to a loss of 6 dB.
The pad group in line 2 is set to a loss of 7 dB.
The TPAD is 3.
Note: This description does not apply to the use of command PADS at
the trunk test position (TTP) level of the MAP terminal.
Example 3
TPAD = 3
Trunk card Line card
Network
Pad = 7
RPAD = 6
Line 2
Receive loss = 6 dB

PADNDEV
Table name
Patch Administration Device Table
The automatic patching application process uses table PADNDEV. A list of
the devices that contain the patch appears in this table. When the system
activates the automatic patch application process, the system searches table
PADNDEV. The system searches this table for the patches that appear in table
PATCTRL. You can add the store file device (SFDEV) and disk volumes to
this table.
The key field (DEVKEY) and the associated device field (DEVICE) appear in
this table. The automatic patch application process uses the key to select in
sequence the devices that appear in the table. This operation stops when the
system completes the search, or when the search reaches the bottom of the
table.
See table PATCTRL for associated information.

You must enter data in table DDU before you enter data in table PADNDEV.
Datafill
Datafill for table PADNDEV appears in the following table.
Field descriptions
Subfield or
DEVKEY 1, 2, or 3 Device key. Enter the key to the table that

indicates the selection of the associated
device. A key of 1 for the tuple indicates that
the tuple contains the primary device used. A
limit of three devices can appear in this table.
DEVICE alphanumeric Device name. Enter the device name that

(1 to 12 contains a patch. The name SFDEV (store
characters) file device), or a disk volume are correct
device names.
Datafill example
Sample datafill for table PADNDEV appears in the following example.
PADNDEV (end)
MAP example for table PADNDEV
DEVKEY DEVICE
________________________________________________________
1 SFDEV
297-8021-351 Standard 05.02 May 2001

PARSDENY
Table name
TOPS Personal Audio Response System Denial Table
Table PARSDENY specifies which originating trunk groups interface to TOPS
and are not to receive Personal Audio Reponse System (PARS) service. Field
CLLI is the only field in the table.
Field CLLI is the index into the table. It contains the common language
location identifiers (CLLI) of originating trunk groups that are not to receive
PARS service. It can be datafilled with only incoming or two-way trunks
which interface with TOPS. These trunk groups include TOPS, intertoll (IT),
access tandem to carrier (ATC), and remote operator number identification
(RONI).
If a call originates on a trunk group datafilled in this table, PARS service is not
offered for the call. This table is present in TOPS stand-alone, host, and
remote offices.

Table TRKGRP must be datafilled before table PARSDENY.
Table TRKGRP must be datafilled with the CLLI before table PARSDENY
can be datafilled. The CLLI name must be deleted from this table before it can
be deleted from table TRKGRP.
Table PARSDENY should be datafilled before table PARSMBR.
Note: In this table, no deletion of a CLLI name is allowed from table

TRKGRP.
Table size
Table PARSDENY has a maximum of 8191 tuples.
PARSDENY (end)
Datafill
The following table lists datafill for table PARSDENY.
Field descriptions
Subfield or
CLLI alphanumeric Common language location identifier. Field

(16 CLLI is the index for this table. It contains
characters) common language location identifiers (CLLI)
of originating trunk groups. There is no
default.
Datafill example
The following example shows sample datafill for table PARSDENY.
MAP display example for table PARSDENY
CLLI
________________________________________________________
TOPSIC
Supplementary information
This section provides information on dump and restore procedures for table
PARSDENY.
Dump and restore

For dump and restore, current table values are copied.
297-8021-351 Standard 05.02 May 2001

PARSMBR
Table name
TOPS Personal Audio Response System Member Table
Table PARSMBR is present only in stand-alone and host offices. It specifies
which Traffic Operator Position System (TOPS) positions are associated with
Personal Audio Response System (PARS) nodes.
Field TOPSPNUM is the index into the table. It contains the TOPS position
number that receives PARS service. Before this field can be datafilled with a
TOPS position number, field POSNO in table TOPSPOS must first contain the
position number. The position type must be general.
Field PARSNNUM associates the TOPS position with a PARS node. This
node corresponds to a link set defined in table MPCLSET. Before this field
can be datafilled, a link set for multiprotocol controller (MPC) application
TOPSPARS must first be datafilled in table MPCLSET. Field LSETNUM, a
refinement of field LSETKEY of table MPCLSET, must contain the node
number for the link set.
Field APPLNOPT assigns an integer parameter to the TOPS position. This

field associates attributes with the position it is datafilled against.
Note: This field is currently unused. It is present to allow for convenient

expansion of capabilities in the future.
TOPS position numbers datafilled in table PARSMBR cannot be deleted from

table TOPSPOS.

The following tables must be datafilled before table PARSMBR.
TOPSPOS
MPCLSET
PARSMBR (end)
Datafill
The following table lists datafill for table PARSMBR.
Field descriptions
Subfield or
TOPSPNUM 0 to 9999 Traffic operator position system position

number. Enter a value for the Traffic Operator
Position System (TOPS) that receives the
Personal Audio Response System (PARS).
This value must be previously datafilled in
table TOPSPOS, field POSNO.
PARSNNUM 0 to 15 Personal Audio Response System node

number. Enter the number that associates
the TOPS position with a PARS node. A link
set for multiprotocol controller (MPC)
application TOPSPARS must first be
datafilled in table MPCLSET The node
number for the link set must be datafilled in
field LSETNUM of table MPCLSET.
APPLNOPT 0 to 32767 Application option. Effective BCS31, this is

(-BCS31) not an active field.
Datafill example
The following example shows sample datafill for table PARSMBR.
MAP display example for table PARSMBR
TOPSPNUM PARSNNUM APPLNOPT

________________________________________________________
100 0 0
297-8021-351 Standard 05.02 May 2001

PATALARM
Table name
Patch Alarm Table
Table PATALARM sets the alarm type that the system generates for each patch
condition. The alarm type can be no alarm, minor, major, or critical alarm.
These alarms replace the ACTPATCH (active patch) alarm.
You can generate DMS patch status reports manually through Patch Status
Report. The system can generate the reports automatically during the 24-h
patch audit, Patch Status Log Report. The DMS patch status reports include
the following patch conditions:
ACT (active) not applied
ACT not activated
ACT password not activated
DBG applied
DBG (debug) not applied
DNR (do not reapply) not applied
EMG (emergency) not applied
GEN (general purpose) not applied
LTD (limited) not applied
MAN (extended multiprocessor system [XMS-based peripheral module]
XPM operational code) not applied
OBE (obsolete emergency) not removed
OBS (obsolete) not removed
Removed patches
Restart not activated patches
SRC (XPM source code) not applied

PATALARM.
Table size
15 tuples
PATALARM (continued)
The table size does not change. The table size includes an entry for each patch
condition defined. Fifteen patch conditions can be present.
Datafill
Datafill for table PATALARM appears in the following table.
Subfield or
PTCHCOND Patch condition. The defined patch conditions

in the switch appear in this field:
ACT_NOT_ACT ACT_NOT_ACT (active not activated)
ACT_NOT_ ACT_NOT_APPLIED (active not applied)

APPLIED
ACT_PW_ ACT_PW_NOT_APPLIED (active password

NOT_ACT not activated)
DBG_ APPLIED DBG_APPLIED (debug applied)
DBG_NOT_ DBG_NOT_APPLIED (debug not applied)

APPLIED
DNR_NOT_ DNR_NOT_APPLIED (do not reapply not

APPLIED applied)
EMG_NOT_ EMG_NOT_APPLIED (emergency not

APPLIED applied)
GEN_NOT_ GEN_NOT_APPLIED (general purpose not

APPLIED applied)
LTD_NOT_ LTD_NOT_APPLIED (limited not applied)

APPLIED
MAN_NOT_ MAN_NOT_APPLIED (extended

APPLIED multiprocessor system [XMS]-based
peripheral module XPM operational code not
applied)
OBE_NOT_ OBE_NOT_REMOVED (obsolete emergency

REMOVED not removed)
OBS_NOT_ OBS_NOT_REMOVED (obsolete not

REMOVED removed)
297-8021-351 Standard 05.02 May 2001

PATALARM (continued)
Subfield or
REMOVED_ REMOVED_PATCHES (removed patches)

PATCHES
RESTART_ RESTART_NOT_ACT (restart not activated

NOT_ACT patches)
SRC_NOT_ SRC_NOT_APPLIED (XPM source code not

APPLIED applied)
ALARM CR, MJ, MN, NA Alarm. Enter the alarm type for each patch
condition when the patch audit runs.
CR (critical)
MJ (major)
MN (minor)
NA (no alarm)
The default is NA.
Datafill example
Sample datafill for table PATALARM appears in the following example.
PATALARM (end)
MAP example for table PATALARM
PTCHCOND ALARM
________________________________________________________
ACT_NOT_APPLIED MJ
ACT_NOT_ACT NA
ACT_PW_NOT_ACT NA
DBG_APPLIED MN
DBG_NOT_APPLIED NA
DNR_NOT_APPLIED NA
EMG_NOT_APPLIED NA
GEN_NOT_APPLIED NA
LTD_NOT_APPLIED NA
MAN_NOT_APPLIED NA
SRC_NOT_APPLIED NA
OBS_NOT_REMOVED NA
OBE_NOT_REMOVED MJ
REMOVED_PATCHES NA
RESTART_NOT_ACT CR
Table history
BCS36
Table PATALARM was introduced.
Entry GEN_NOT_APPLIED added under field PTCHCOND.
Information on dump and restore procedures for table PATALARM appears in
this section.
Dump and restore

Normal dump and restore procedures apply.
297-8021-351 Standard 05.02 May 2001

PATCHOPT
Table name
Patcher Options Table
Use table PATCHOPT to activate or deactivate PATCHER functions. You can
use this table to schedule optional functions like the patch audit. A patch audit
notifies operating companies of patch errors.
The patch audit scans patchable extended multiprocessor system (XMS)-based

peripheral module (XPM) units. These units include the following:
digital trunk controller (DTC)
line group controller (LGC)
message switch buffer 7 (MSB7)
The patch audit checks nodes and units that are in service (INSV), or in-service
trouble (ISTB). The patch audit compares the status of the patches in the
specified node to the status of the patches according to the central controller
(CC) or computing module (CM).
If the audit detects an error, the audit performs the following procedure:
generates a PCH log report to identify the error
identifies the node or unit as ISTB if the audit detects an error
updates the status of the patch in the CC or CM if the update option is on
You can set the patch audit to automatically update the patch status if the audit
detects an error. If this condition occurs, the audit updates the CC or CM with
the status of the patch in the ISN node or XPM node. The audit does not apply
the patch.
You must not schedule a patch audit to run during a routine exercise (REX)
test. The REX test cancels the patch audit. The office parameter
NODEREXCONTOL in table OFCVAR schedules the REX test. The system
generates the PCH107 log report to indicate this type of cancellation.

PATCHOPT.
Table size
1 tuple
PATCHOPT (continued)
Datafill
Datafill for table PATCHOPT appears in the following table.
Field descriptions
Subfield or
TUPLE see subfield Patcher options key type. This field contains
subfield TUPLE_KEY.
TUPLE_KEY PATCHAUD Key tuple. Enter PATCHAUD to schedule the

patch audit.
ON Y or N On. Enter Y (yes) to turn the patch audit on.

Enter N (no) to turn the patch audit off.
START HHMM (4 Start time. Enter the patch audit start time on
digits) the 24-h clock.
The default start time for the patch audit is
2300, 11:00 p.m., each night.
UPDATE Y or N Update patch status. Enter Y to update the

patch status in the central control or
computing module. Enter N to turn the update
option off.
Note: This audit updates the patch status

only if the update option is on in table
PATCHOPT. The audit does not apply,
remove, or reclaim patches.
Datafill example
Sample datafill for table PATCHOPT appears in the following example.
The first tuple makes the patch audit run at 2300 h each night. This tuple
updates patch status when the audit detects patch errors.
The second tuple turns off the patch audit.
297-8021-351 Standard 05.02 May 2001

PATCHOPT (end)
MAP example for table PATCHOPT
TUPLE ON START UPDATE

________________________________________________________
PATCHAUD Y 2300 Y
PATCHAUD N 0000 N
Table history
CSP02
References to Intelligent Services Node (ISN) in Functional description"
section were removed in CSP02.
PATCTRL
Table name
Patch Control Table
A patch is a piece of code that repairs or improves current software. The
automatic patch application process eliminates the requirement for manual
application of patches to a DMS. When you download the patch to a specified
office, the system can apply the patch to the switch. You can control the
automatic patch application process. The operating company maintains final
scheduling of patch applications.
Table PATCTRL contains a list of patches available to the switch. Table

PATCTRL contains the information to control the automatic patch application
process. This table monitors the patches that the system does not apply. These
patches are on the store file device (SFDEV) in the switch. This table can
monitor the devices that table PADNDEV specifies. At the scheduled time set
in table PATSET, the patch application process applies the patches in table
PATCTRL. Table PATCTRL updates the status of the applied patches and
adds any new patches downloaded to the switch.
Use the command interpreter (CI) command GETPAT to add additional

patches to the table.
Each execution of command GETPAT creates table PATCTRL again.
You cannot cannot add or delete tuples from the table. You can change the
following tuple attributes:
fields DATE and APPROVED for central control (CC) patches
fields DATE, APPROVED, and NSNAME for computing module (CM)
patches
fields DATE, APPROVED, NSNAME, and ACTION for extended
multiprocessor system (XMS)-based peripheral module (XPM) patches

PATCTRL.
Table size
0 to 999 tuples
The number of tuples added determines table size.
297-8021-351 Standard 05.02 May 2001

PATCTRL (continued)
Datafill
Datafill for table PATCTRL appears in the following table.
Subfield or
PATCHID alphanumeric Patch identifier. Enter the patch identifier.

(maximum of The patch file can be on the store file device
8 characters) (SFDEV) in the system. The patch file can be
on one of the devices that table PADNDEV
specifies.
CAT ACT, DBG, Category. Enter the category assigned to the

EMG, GEN, patch. The categories depend on the patch.
LTD, MAN,
ACT (active)
OBE, OBR,
OBS, or SRC DBG (debug)
EMG (emergency release)
GEN (general)
LTD (limited release)
MAN (manual)
OBE (no longer in use emergency)
OBR (no longer in use emergency)
OBS (no longer in use)
SRC (source code)
Any entry outside the range indicated for this
field is not correct.
TARG CC, CM, MS, Target. Enter the type of processor to which
or XPM the system applies the patch.
CC (central control) for NT40 switches
CM (computing module) for DMS
SuperNode switches
MS (message switch) for DMS
SuperNode switches
XPM (extended multiprocessor system
XMS-based peripheral module)
PATCTRL (continued)
Subfield or
APPLY Y or N Safe to apply. Enter Y to indicate that the

system applies the patch. Enter N to stop
automatic patch application. Other table
entries do not affect patch application.
The default value for this field is N.
APPROVED Y or N Operating company approved. Enter Y to

approve the patch for the automatic patch
application process. If you do not want to
approve the patch for this process, enter N.
Note 1: The AUTOPATCH function does

not run the command interpreter (CI)
command GETPAT. You must run command
GETPAT manually.
Note 2: You must set the default value in
field APPROVED of table PATSET.
DATE numeric Date. Enter the date, YYMMDD (year, month,

(maximum of day), the patch applies to.
6 digits)
ACTION APPLY_ALL Action. Enter APPLY_ALL to apply the patch

APPLY_ to all qualified units. The APPLY_ALL
EVEN or defaults to CC patches. Operating company
APPLY_ODD personnel cannot update this entry.
Enter APPLY_EVEN to apply the patch to all
qualified even units (0). Enter APPLY_ODD
to apply the patch to all qualified odd units (1).
297-8021-351 Standard 05.02 May 2001

PATCTRL (continued)
Subfield or
NSNAME alphanumeric Nodeset name. If the entry in field TARG is

(maximum of XPM, enter data in this refinement. Enter the
8 characters) nodeset used for the autopatch process. A
nodeset contains a list of nodes with device
and unit numbers. The autopatcher attempts
to apply patches to the device and unit
numbers. The autopatcher attempts to apply
patches only to the nodes in this field.
ACK APPLY_ Acknowledgement. Enter

MANUALLY APPLY_MANUALLY to indicate that the user
FAILED can apply the patch manually.
FULLY_
Enter FAILED to indicate that the action
APPLIED
requested under field ACTION failed.
MISSING_
NEED Enter FULLY_APPLIED to indicate that patch
OUT_OF_ application is complete.
SEQ
Enter MISSING_NEED to indicate that a
PARTIALLY_
patch is not available before application can
APPLIED or
occur.
PENDING
Enter OUT_OF_SEQ to indicate that the
patch administration number is out of
sequence.
Enter PARTIALLY_APPLIED to indicate that
partial application occurred.
Enter PENDING to indicate that the process
checked the patch (DLCHECKED) and
placed the patch in the table.
The default value for this field is PENDING.
Datafill example
Sample datafill for table PATCTRL appears in the following example.
In this example, operating company personnel download patch AJM02A26 to

the office. The patch is a CM patch and is in the category GEN. The automatic
patch application process does not apply this patch. Field APPLY (N)
confirms that the process does not apply the patch. The system defaults fields
APPLY and APPROVED automatically. Table PATSET describes this default.
The CC patches default to an APPLY_ALL entry in field ACTION. Field
PATCTRL (end)
NSNAME is an ENET nodeset. The value PENDING in field ACK indicates

that the process placed the patch in the table.
MAP example for table PATCTRL
PATCHID CAT TARG APPLY APPROVED DATE ACTION

NSNAME
ACKNOWLEDGE
________________________________________________________
AJM02A26 GEN CM N N 880510 APPLY_ALL

ENETONS
PENDING
Table history
CSP02
References to Intelligent Services Node (ISN) in Functional description"
section and in fields TARG and NSNAME were removed.
BCS35
The refinement NSNAME was added.
297-8021-351 Standard 05.02 May 2001

PATNS
Table name
Patch Nodeset (PATNS) Table
Table PATNS contains the list of default nodesets that the autopatcher nodeset
options use. Each default nodeset contains only one node type. Table PATNS
contains the nodesets for the autopatcher nodes in the switch.

PATNS.
Table size
2 to 64 tuples
The available patchable hardware that resides on the switch determines the size
of the switch.
Datafill
Datafill for table PATNS appears in the following table.
Subfield or
NODESET alphanumeric Nodeset name. Enter the name of the

(eight nodeset used for autopatching.
characters)
NODEDATA see subfields Node data. This field contains the following
subfields:
DEVICE_STR
LWB_STR
UPB_STR
UNIT_STR
DEVICE_STR alphanumeric Device. Enter the name of the node that the
(maximum of nodeset contains.
four
characters)
PATNS (continued)
Subfield or
LWB _STR alphanumeric Lower bound. Enter the lower bound of the
(maximum of device numbers of the nodes that the nodeset
three contains.
characters)
UPB_STR alphanumeric Upper bound. Enter the upper bound of the

(maximum of device numbers of the nodes that the nodeset
three contains.
characters)
UNIT_STR alphanumeric Unit. Enter the unit or plane number of the

(maximum of node or nodes that the nodeset contains.
three
The default value for plane 0 is 0. The default
characters)
value for unit 1 or plane 1 is 1.
AUTOSET Y or N Auto set. Enter Y (yes) if the autoset has the

nodeset included. If the autoset does not
include the nodeset, enter N (no).
The default value is N.
Datafill example
Sample datafill for table PATNS appears in the following example.
MAP example for table PATNS
NODESET NODEDATA AUTOSET

________________________________________________________
MS0NS ( MS NA NA 0)$ N
297-8021-351 Standard 05.02 May 2001

PATNS (end)
Table history
BCS36
The following field names were corrected in BCS36:
DEVICE_STR
LWB_STR
UPB_STR
UNIT_STR
BCS35
Table PATNS was introduced in BCS35.
This section provides information on how to perform dump and restore
procedures when you enter data in table PATNS
Dump and restore

A dump and restore is not a requirement during first application. Normal
dump and restore procedures apply after the first application.
PATSET
Table name
Patch Set (PATSET) Table
The automatic patching application process uses table PATSET to establish
default values for entries in table PATCTRL. An operating company cannot
add or delete tuples from this table. Use an extension (AUTOSUB) file to
establish this single tuple table. All the tuple attributes except field TUPLE
can change.
The monitoring of switch sanity occurs before and after the autopatch process
runs. A snapshot of the log utility (LOGUTIL) log count occurs daily.
Software buffers store the snapshot before and after the autopatch process
runs. A comparison of log count changes against the defined threshold levels
of the operating company occurs. The operating company enters the specified
monitor times in table PATSET, fields PREMON and POSTMON. The
operating company enters the acceptable threshold change that can occur in
table PATSET, field THRSHOLD.
Refer to table PATCTRL for related information.

PATSET.
Table size
1 tuple
Datafill
Datafill for table PATSET appears in the following table.
Subfield or
TUPLE AUTOPTCH Tuple. This field contains AUTOPTCH

(autopatch).
DATE numeric Date. The default date for the start of the
(six digits) automatic application of all patches appears
in this field. The default date appears as
YYMMDD.
297-8021-351 Standard 05.02 May 2001

PATSET (continued)
Subfield or
START numeric Start time. The time for the start of the
(four digits) automatic application of specified patches
appears in this field. The time is based on the
24 h clock.
The default value is 0300 (3:00 a.m.).
END numeric End time. The time that automatic application

(four digits) of specified patches ends appears in this
field. The time is based on the 24 h clock.
The default value is 0600 (6:00 a.m.).
APPROVED Y or N Approved. The default value set for field

APPROVED in table PATCTRL appears in
this field. The default value set is Y (yes) or N
(no). The initial setting is N.
ISUVAL 0 to 100 Incremental software update value. The

accepted failure threshold for applying XPM
patches appears in this field. The accepted
failure threshold appears as a percentage of
all extended multiprocessor system
(XMS)-based peripheral modules (XPM).
An entry in this field establishes the maximum
failure rate for the application of an XPM
patch. The automatic patching application
process attempts the application of this patch.
The specified failure rate can exceed the
maximum. When this action occurs, the
application of the offending patch halts and
the application of other scheduled patches
continues.
AUTO (-BCS35) Y or N Automatic patch application process. A Y

appears in this field if the system allows the
patch application process. An N appears in
this field if the system does not allow the
patch application process.
PATSET (continued)
Subfield or
PREMON T15, T30, Premonitor minutes. The monitor time of a log

T45, T60, count snapshot before the autopatch process
T90, or T120 completes appears in this field. The monitor
time is in minutes.
The default value for this field is T15 (15 min).
POSTMON T15, T30, Postmonitor minutes. The monitor time of a

T45, T60, log count snapshot after the autopatch
T90, or T120 process completes appears in this field. The
monitor time is in minutes.
The default value for this field is T15 (15 min).
THRSHOLD 0 to 100 Threshold. The percentage of acceptable

change in LOGUTIL counts that allows the
autopatch process to occur appears in this
field. If the amount of change is less than the
THRSHOLD percentage, the autopatch
process occurs.
The default value for this field is 15.
APLNSYNC Y or N Apply patch process in-synchronization or

out-of-synchronization. A Y appears in this
field if the autopatch process applies patches
in-synchronization. An N appears if the
autopatch process applies patches
out-of-synchronization. The switch can
already be out-of-synchronization when the
autopatch process attempts to drop
synchronization. In this event, the system
cancels the autopatching session.
The default value for this field is Y.
STOPFAIL Y or N Stop fail. An N appears in this field if the

autopatch process continues to apply patches
after a patch fails to apply. A Y appears if the
autopatch process does not continue to apply
patches after a patch fails to apply.
297-8021-351 Standard 05.02 May 2001

PATSET (continued)
Subfield or
MAXAPPLY 0 to 100 Maximum patches applied. The maximum

number of patches to apply during the
autopatch session appears in this field.
The default value for this field is 15.
AUTOSET Y or N Autoset option. A Y appears in this field if the

autoset option is on. An N appears if the
autoset option is off. The default value for this
field is N.
Note 1: Autoset use causes the system to

ignore the nodeset options. The autopatcher
processes all patches against the autoset as
opposed to separate patches against the
specified nodeset of the patch. An N appears
if the system does not present patches to the
autopatcher.
Note 2: You must download patches through
NOPS.
AUTOGETP Y or N Automatic get patch command. A Y appears

(BCS36-) in this field when the system performs the
command interpreter (CI) command
GETPAT. The system performs this action
immediately following the download of
patches to the DMS. The system enters data
in table PATCTRL. An N appears if the user
must execute the GETPAT command
manually to enter data in table PATCTRL.
DAYOFWK Y or N Day of week. This field replaces field AUTO.

(BCS36-) (7 booleans) Use of this field occurs to selectively run the
Auto Apply utility (Autopatcher) on specified
days during the week.
A Y appears in this field for each day of the
week that the system allows the patch
application process. An N appears for each
day of the week that the system does not
allow the patch application process.
Datafill example
Sample datafill for table PATSET appears in the following example.
PATSET (end)
MAP example for table PATSET
TUPLE DATE START END APPROVED ISUVAL PREMON

POSTMON THRSHOLD APLNSYNC
STOPFAIL MAXAPPLY AUTOSET AUTOGETP DAYOFWK
________________________________________________________
AUTOPTCH 880501 2300 2330 N 0 T15

T15 15 Y
Y 15 N N NNNNNNN
Table history
CSP02
Reference to Intelligent Services Node (ISN) in field ISUVAL was removed in
CSO02.
BCS36
The following changes were made in BCS36:
Field XPMVAL was corrected to field ISUVAL
Field AUTO was removed
Fields AUTOGETP and DAYOFWK were added
297-8021-351 Standard 05.02 May 2001

Copyright 2005, Nortel Networks 1 Nortel Networks Confidential
PCEMENTT
ATTENTION
This table applies to new or modified content for SN07 (DMS)
that is valid through the current release.
Packet Cable Event Messaging

The Packet Cable Event Messaging Entity Cable (PCEMENTT) table
lists the following:
A common set of PCEM data
An Event Messaging Delivery Interface (EMDI) entity
A collection of Record Keeping Server (RKS) entities
A collection of RKS pair entities
A collection of Delivery Function (DF) entities, and
A Time Zone (TIMEZONE) entity.
Datafill sequence and meaning (CM Only)

Before the new OFCENG parameter PCEM_IS _ACTIVE is set to Y:
the COMMON tuple must be datafilled, and
the TIMEZONE tuple must be datafilled.
The COMMON and TIMEZONE tuple cannot be deleted when the new
OFCENG parameter PCEM_IS_ACTIVE is set to Y.
PCEMENTT does not use translation verification tools.
Table size
Abbreviated Minimum Maximum

table name tuples tuples Information on memory
PCEMENTT 0 59 Memory is automatically allocated for 59PCEM

entities.
Datafill
The following table lists fields/OIDs for PCEMENTT.
Table field descriptions
New or Subfield or
Field Changed refinement Entry Explanation and action
KEY NEW See subfields. PCEM Entity and Entry Number.

Enter the name of the entity and its
entry number.
NEW ENTITY COMMON, PCEM Entity. This field specifies the

EMDI, RKS, name of the entity.
RKSPAIR, DF,
TIMEZONE
NEW ENTRYNO 0 to 31 PCEM Entity Entry Number. This

field specifies the entry number of an
entity.
DATA NEW See subfields. PCEM Entity Data. This field consists
of subfields based on the entity.
ENTITY = COMMON
If the ENTITY in KEY is COMMON, datafill tuple as shown below.
COMMON entity field descriptions
New or Subfield or
KEY NEW See subfields. PCEM Entity and Entry Number.

Enter the name of the entity and its
entry number.
NEW ENTITY COMMON PCEM Entity. This field specifies the

name of the entity. Enter COMMON.
NEW ENTRYNO 0 PCEM Entity Entry Number. This field

specifies the entry number of an
entity. Enter 0 for the COMMON entity.
DATA NEW See subfields. PCEM Entity Data. This field consists
of subfields ENTITY, VERSION_ID,
ACCTSENDMODE, ACCOUNTING
and SURVEILLANCE.
297-8021-351 SN08.0 Standard 10.04 October 2005

COMMON entity field descriptions
New or Subfield or
NEW ENTITY COMMON PCEM Entity. Enter COMMON for

common data entity.
NEW ACCTSEN REALTIME, PCEM Accounting Sending Mode.

DMODE BATCH, or Enter the desired sending mode for
FTP accounting Event Messages.
NEW ACCOUNTI Y or N PCEM for Accounting. Enter Y if

NG Accounting Event Messages is to be
generated. Enter N if Accounting
Event Messages is not to be
generated.
NEW SURVEILL Y or N PCEM for Electronic Surveillance

ANCE (ES). Enter Y if ES Event Messages is
to be generated. Enter N if ES Event
Messages is not to be generated.
ENTITY = EMDI
If the ENTITY in KEY is EMDI, datafill tuple as shown below.
EMDI entity field descriptions
New or Subfield or
KEY NEW See subfields. PCEM Entity and Entry Number. Enter
the name of the entity and its entry
number.
NEW ENTITY EMDI PCEM Entity. This field specifies the

name of the entity. Enter EMDI for Event
Messaging Delivery Interface.

specifies the entry number of an entity.
Enter 0 for the EMDI entity.
DATA NEW See subfields. PCEM Entity Data. This field consists of
subfields ENTITY and EMDI_IP.
NEW ENTITY EMDI PCEM Entity. Enter EMDI.
EMDI entity field descriptions
New or Subfield or
NEW EMDI_IP full 4-part EMDI IP Address. Enter the full 4-part IP
Internet address of the EMDI entry. This field
Protocol (IP) specifies the IP address of the Core &
address Billing Manager (CBM).
NEW EMDI_PORT 0 to 65535 EMDI Port Number. Enter the port

number assigned for EMDI in the CBM.
ENTITY = RKS
If the ENTITY in KEY is RKS, datafill tuple as shown below.
RKS entity field descriptions
New or Subfield or
KEY NEW See subfields. PCEM Entity and Entry Number. Enter
the name of the entity and its entry
number.
NEW ENTITY RKS PCEM Entity. This field specifies the

name of the entity. Enter RKS for Record
Keeping Server.
NEW ENTRYNO 0 to 31 PCEM Entity Entry Number. This field

Enter the number desired for an RKS
entity.
subfields ENTITY, RKS_IP and
RKS_PORT.
NEW ENTITY RKS PCEM Entity. Enter RKS.
NEW RKS_IP full 4-part IP RKS IP Address. Enter the full 4-part IP
address address of the RKS entry.
NEW RKS_PORT 0 to 65535 RKS Port Number. Enter the port number
assigned to the RKS entity.
ENTITY = RKSPAIR
297-8021-351 Standard 10.04 October 2005

If the ENTITY in KEY is RKSPAIR, datafill tuple as shown below.
New or Subfield or
KEY NEW See subfields. PCEM Entity and Entry Number. Enter the
name of the entity and its entry number.
NEW ENTITY RKSPAIR PCEM Entity. This field specifies the name
of the entity. Enter RKSPAIR for Record
Keeping Server Pair.

Enter the number desired for an RKSPAIR
entity.
subfields ENTITY, RKS_PRIMARY,
RKS_SECONDARY and ASSOC_EMDI.
NEW ENTITY RKSPAIR PCEM Entity. Enter EMDI.
NEW RKS_PRIM 0 to 31 RKS Primary. Enter the entry number of the

ARY primary RKS in this RKS pair.
NEW RKS_SEC 0 to 31 RKS Secondary. Enter the entry number of

ONDARY the secondary RKS in this RKS pair.
NEW ASSOC_E 0 to 31 Associated EMDI. Enter 0 for the EMDI

MDI associated with this RKS pair. EMDI 0 is
the only one supported.
ENTITY = DF
Note: The DF entity is only required for Electronic Surveillance.
If the ENTITY in KEY is DF, datafill tuple as shown below.
New or Subfield or
NEW ENTITY DF PCEM Entity. This field specifies the name

of the entity. Enter DF for Delivery Function.

Enter the number desired for a DF entity.
subfields ENTITY, CDC_IP, CDC_PORT,
CCC_IP, CCC_PORT and ASSOC_EMDI.
NEW ENTITY DF PCEM Entity. Enter DF.
NEW CDC_IP full 4-part IP Call Data Channel (CDC) IP Address. Enter
address the full 4-part IP address of the DFs CDC.
CDC_POR 0 to 65535 CDC Port Number. Enter the port number

T assigned to the DFs CDC.
CDC_IP full 4-part IP Call Content Channel (CCC) IP Address.

address Enter the full 4-part IP address of the DFs
CCC.
NEW CCC_POR 0 to 65535 CCC Port Number. Enter the port number
T assigned to the DFs CCC.
NEW ASSOC_E 0 to 31 Associated EMDI. Enter 0 for the EMDI

MDI associated with this DF. EMDI 0 is the only
one supported.
ENTITY = TIMEZONE
If the ENTITY in KEY is TIMEZONE, datafill tuple as shown below.

New or Subfield or
NEW ENTITY TIMEZONE PCEM Entity. This field specifies the name of
the entity. Enter TIMEZONE for Time Zone
entity.

specifies the entry number of an entity. Enter
0 for the Time Zone entity.
subfields ENTITY, DST, DIRECTION, and
HHMMSS.
NEW ENTITY TIMEZONE PCEM Entity. Enter TIMEZONE.
NEW DST Y or N Daylight Savings Time (DST) Indicator. Enter

Y for DST and N for Standard TIme.
NEW DIRECTIO PLUS, MINUS Universal Time Coordinated (UTC) Offset

N Direction. Part of the UTC offset, this field is
automatically filled in by the PCEMTIME
process. Initially, enter PLUS.
NEW HHMMSS 000000 to UTC Offset in hours, minutes and seconds.

999999 Part of the UTC offset, this field is
automatically filled in by the PCEMTIME
process. Initially, enter 000000.
Datafill example
The following example shows sample datafill for table PCEMENTT.
MAP display example for table PCEMENTT
>table pcementt
MACHINES NOT IN SYNC - DMOS NOT ALLOWED
JOURNAL FILE UNAVAILABLE - DMOS NOT ALLOWED
TABLE: PCEMENTT
>lis all
TOP
KEY DATA
------------------------------------------------------------------------
COMMON 0 COMMON REALTIME Y N
EMDI 0 EMDI 47 142 128 220 5
RKS 0 RKS 132 131 2 3 1234
RKS 31 RKS 141 226 1 2 2007
RKSPAIR 15 RKSPAIR 31 0 0
DF 7 DF 123 232 15 6 6543 212 131 55 7 3456 0
TIMEZONE 0 TIMEZONE Y MINUS 050000
BOTTOM
>
Note: the DF tuple is only required for Electronic Surveillance.
Table history
SN07 (DMS)
New table PCEMENTT created as part of activity A00007196.
Documentation updated by CR Q01077110.

PCEMFEID
ATTENTION
This table applies to new or modified content for SN07 (DMS)
that is valid through the current release.
Packet Cable Event Messaging Financial Entity Identifier

The Packet Cable Event Messaging Financial Entity Identifier
(PCEMFEID) table lists a tuple of up to 247-character Financial Entity
Identifier (FEID) which consists of an 8-character Multi-System
Operator (MSO) Defined Data and up to 239-character MSO Domain
Name.
Datafill sequence and meaning (CM Only)

The FEID is required to be datafilled before the new OFCENG
parameter PCEM_IS_ACTIVE can be set to Y.
The FEID cannot be deleted when the new OFCENG parameter

PCEM_IS_ACTIVE is set to Y.
Table size
Abbreviated Minimum Maximum

table name tuples tuples Information on memory
PCEMFEID 0 1 Physical tuple memory is allocated for up to 247-character

FEID.
Datafill
The following table lists fields/OIDs for PCEMFEID.
Subfield
New or or
Change refinem
Field d ent Entry Explanation and action
KEY NEW 0 PCEM Financial Entity Identifier Key.

This is the key to the table.
MSODEF NEW 8 ASCII Multi-System Operator (MSO) Defined

character string Data. Enter the MSO Defined Data.
MSODMN NEW Limited to 4 MSO Domain Name. Enter the MSO

64-character Domain Name.
vectors to
accommodate
up to 239 ASCII
characters.
Datafill example
The following example shows sample datafill for table PCEMFEID.
MAP display example for table PCEMFEID
>table pcemfeid
MACHINES NOT IN SYNC - DMOS NOT ALLOWED
JOURBAL FILE UNAVAILABLE - DMOS NOT ALLOWED
TABLE: PCEMFEID
>lis all
TOP
KEY MSODEF
MSODMN
-----------------------------------------------------------------------
0 12345678
( test.field)$
BOTTOM
>
Table history
SN07 (DMS)
New table PCEMFEID created as part of activity A00007196.
Documentation updated by CR Q01077137.

PCIC
Table name
Phantom Carrier Identification Code
Table Phantom Carrier Identification Code (PCIC) is only accessed for
trunk-originated calls using feature group D (FGD) signaling. Phantom carrier
identification codes (CIC) that originate in an equal access end office (EAEO)
are not mapped to a real CIC before routing. If the carrier number is not found
in table OCCINFO, a lookup is performed in table PCIC. If the carrier number
is found in table PCIC, it is mapped to a real national CIC or a real
international CIC.

You can complete table OCCINFO independent of table PCIC. Ensure that the
carriers in table PCIC are not in table OCCINFO.
Table size
0 to 10,000 tuples
Datafill
The following table lists datafill for table PCIC.
Field descriptions
Subfield or
PCICKEY 0000 - 9999 The actual phantom CIC that comes into the
office. This field is not a tuple count.
RNATLNM alphanumeric The real national carrier name used in place

(1 to 16 of the phantom CIC. This field is popluated
characters) using the OCCNAME field in table
OCCNAME.
RINTLNM alphanumeric The real international carrier name used in

(1 to 16 place of the phantom CIC. This field is
characters) populated using the OCCNAME field in table
OCCNAME.
Datafill example
The following example shows sample datafill for table PCIC.
PCIC (end)
MAP display example for table PCIC
PCICKEY RNATLNM RINTLNM

________________________________________________________
9999 CAR1 CAR2
Table history
NA010
This table exists as of NA010.
After the system replaces the phantom CIC with a real CIC, translations begins
at table STDPRTCT using standard datafill.
297-8021-351 Standard 05.02 May 2001

PECINV
Table name
Product Engineering Code Inventory (PECINV) Table
Table PECINV accommodates the baseline datafill of the SuperNode Product
Engineering Codes (PECs).
The baseline datafill is in a separate EXT file. The system picks up this file
during the loadbuild process. The content of this table is shipped with the
software that goes to the operating company.
Changes to the hardware baseline can be necessary for special requirements of

specified operating companies. You can perform changes to the baseline
during hardware upgrades.

PECINV.
Table size
The minimum size is 0 tuples and the maximum size is 200 tuples. This
maximum size is a constant.
There is no office parameter that allows you to change the maximum number
of tuples in Table PECINV.
DMS-100 Customer Data Schema Reference Manual Volume 9 of 12 LET17/SN07 (DMS) and up
PECINV (continued)
Datafill
Datafill for table PECINV appears in the following table.
Field descriptions
Subfield or
Field refinement Entry Description
PEC vector of a Product Engineering Code. This field

maximum of contains correct SuperNode Product
eight Engineering Codes (PECs). This field is the
characters key field.
SSYSBASE vector of a Subsystem baselines. This field contains an

maximum of optional vector of sub-tuples.
nine multiples
Entry SUBSY is the SN_SUBSYSTEM_HW
with
(SuperNode subsystem hardware) type, and
SUBSYS,
contains the range STDHW, CMHW, MSHW,
BASELINE,
ENETHW, LIMHW, LIU7HW, APHW, HSIHW
EXCPTN or $
and LTSHW. The sub-tuple with STDHW
subsystem hardware that applies for
subsystem types does not appear in the tuple.
The BASELINE is a table of two characters.
The EXCPTN is an optional vector, with a
maximum of two characters. These
exception characters must be higher than the
baseline. A $ (dollar sign) terminates the
vector.
Procedure for determining the minimum allowable baseline release

number associated with a Product Engineering Code
1. Access C-SPAN as the C-SCAN Basic User Guide describes.

2. Select the Baseline Reports option.

PECINV (continued)
Procedure for changing the release number associated with a Product

Engineering Code
At the MAP terminal
1. To return to the CI level of the MAP display, type
>QUIT ALL
and press the Enter key.
Example of a MAP response:
NO COMMAND IN LINE
2. To access table PECINV, type

>TABLE PECINV
TABLE: PECINV
3. To identify (position on) the Product Engineering Code (PEC) to change,

type
>POS pec
where
pec
is the Product Engineering Code (like NT9X15AA)
NT9X15AA
( LIMHW40 $) ( MSHW40 $) $
4. To prepare to change the release number for the PEC, type

>CHA
ENTER Y TO CONTINUE PROCESSING OR N TO QUIT
PECINV (continued)
5. To confirm that a change must occur, type

>Y
SSYSBASE: LIMHW 40 $
6. To enter the new release number for the PEC, type

>subsys rel_no $
where
subsys
is the subsystem hardware type (like LIMHW)
rel_no
is the new release number (like 49)
SSYSBASE: LIMHW 49
7. To confirm that the new release number is correct for the PEC, type
>$
NT9X15AA
( LIMHW49 $) $
ENTER Y TO CONFIRM, N TO REJECT OR E TO EDIT.
8. To confirm the change, type

>Y
TUPLE changed
9. To make sure the change to table PECINV occurs, type

PECINV (continued)
>LIST
PEC SSYSBASE

NT9X15AA (LIMHW 49 $) $
10. To quit the table editor and return to the CI level of the MAP display, type
>QUIT ALL
Datafill example
Sample datafill for table PECINV appears in the following example.
MAP example for table PECINV
PEC SSYSBASE
________________________________________________________
NT9X13DA (MSHW 12 (16) (17) $)(LIMHW A8 $) (STDHW 10 $)$
NT9X10AA (ENETHW 11 $) $
Table history
LET17/SN07 (DMS)
Q00900178
Change to text stating that there is no office parameter that allows any change
to the number of tuples in Table PECINV. The maximum table size is amended
to 200 tuples.
CSP08
The procedure to update this table was introduced in CSP08.
BCS34
This table was introduced in BCS34.
PECINV (end)
The system cannot perform Dump and Restore for this table. The content of
this table is in an EXT file. If the system performs a dump and restore, the
system loses the new content of the table.

PFCTRL
Table name
Power Feature Control Table
Table PFCTRL is used to control the availability of features that can be
assigned through feature AJ1240 (Power Features Enhancements I). Table
PFCTRL replaces the existing power feature (PF) terminal management
environment (TME) command interpreter (CI) command. Table PFCTRL has
identical functions to the TME CI command, with the exception that the
datafill associated with the table survives a batch change supplement (BCS)
application switch of activity (SWACT).

Table CUSTENG must be datafilled before table PFCTRL.
Table PFCTRL is automatically datafilled for the default customer group

PFDEFAULT if the table is in the load. All tuples for customer group
PFDEFAULT have field ENABLED set to N (no).
Before assigning option PF to a new customer group, make sure that the
customer group tuple exists in table CUSTNTWK.
Table size
The maximum number of tuples in table PFCTRL depends on the number of
customer groups and the number of power features (PF) options that are
supported.
Maximum number of tuples = (number of customer groups) (number of PF

options)
297-8021-351 Standard 05.02 May 2001

PFCTRL (continued)
Datafill
The following table lists datafill for table PFCTRL.
Subfield or
CUSTGRP alphanumeric Customer group name

(up to 16
This is the first part of the key. Enter the
characters)
name of the customer group to which the data
in this tuple applies. This name must be
previously datafilled in table CUSTENG.
PFOPT alphanumeric Power feature options

(1 to 8
This is the second part of the key. Enter the
characters)
name of a feature that can be assigned as a
power features (PF) option. Each operating
company office has an individualized list of
PF options, depending on the feature
packages loaded into the switch. Refer to
tables IBNFEAT, KSETFEAT, and LENFEAT
for a description of all the options.
Note: If NAME (for Name Programming) had been enabled previously under field PFOPT, then
PUB_NAME and PRIV_NAME are enabled during the dump and restore process. If NAME had not
been enabled previously, then PUB_NAME and PRIV_NAME are not enabled.
PFCTRL (continued)
Subfield or
The list of PF options include the following:

AAB (automatic answer back)
ACB (automatic call back)
ADMIN_CTRL (administrator control)
AUTODISP (auto display)
AUD (auto dial)
BLF (busy lamp field)
CCV (call covering)
CADDON (configure add on)
CPHONE (configure phone)
CFI (call forwarding intragroup)
CFU (call forwarding universal)
CPU (call pickup)
CWT (call waiting)
DCPK (directed call park)
DRING (distinctive ringing)
EMW (executive message waiting)
297-8021-351 Standard 05.02 May 2001

PFCTRL (continued)
Subfield or
PFOPT The list of PF options include the following:

(continued) (continued)
INSPECT (inspect)
LANG (choose language)
LVM (leave message)
MSB (make set busy)
MWT (message waiting)
PF (power feature)
PRK (call park)
PSWD (alter password)
PUB_NAME (public name)
PVT_NAME (private name)
QLEN (query line equipment number)
QTD (query time and date)
RAG (ring again)
SLOCK (security lock)
3WC (three-way calling)
ENABLED Y or N Enabled
Enter Y (yes) to enable the specific feature
datafilled as a PF option in field PFOPT.
Enter N (no) to disable the specific feature.
AUDIT Y or N Audit
Enter Y to generate journal file entries and log
reports to record power feature usage.
Otherwise, enter N.
Datafill example
The following example shows sample datafill for table PFCTRL.
PFCTRL (end)
MAP display example for table PFCTRL
CUSTGRP PFOPT ENABLED AUDIT

__________________________________________________________
PFDEFAULT NAME N N
Table history
NA005
Entry NAME (Name Programming) under field PFOPT was replaced by two
entries, PUB_NAME and PRIV_NAME, to permit the datafill of public and
private name permissions individually in accordance with PF
Robustness-Public and Private Name Programming.
NA003
Field PFOPT was expanded to accommodate new valid inputs for Power
Features.
BCS34
Table PFCTRL was introduced.
297-8021-351 Standard 05.02 May 2001

PFXTREAT
Table name
Prefix Treatment (PFXTREAT) Table
Table PFXTREAT determines the call treatment to which the system routes a
call. The following information determines the treatment:
the prefix selector from table LCASCRCN
the type of call from the standard pretranslator
the local calling area status (local or toll), in subtable
LCASCRCN.LCASCR
The prefix selector allows a maximum of four different routes for each
combination of fields TYPCALL and LOCAL. The prefix selector name can
be a 4-character vector of the two specified prefix selectors mandatory
(MAND) or optional (OPTL). The prefix selector name can also be a
maximum of 14 customer-definable prefix selectors.
One prefix selector can be assigned to a LCASCRCN.LCASCR subtable. The

entries in the table with that prefix selector apply to subtable
LCASCRCN.LCASCR.
If the caller has the option of dialing prefix digits, the system requires field
UPDTYPCA to update the type of call.
The prefix digit can be optional on toll calls. When this event occurs, an entry
must have fields UPDTYPCA and TREAT set to DD and UNDT, in that order.
This entry has fields TYPCALL and LOCAL equal to NP and N, in that order.
The fields must be set in this manner so that the call completes and the
operating company applies charging.
The system can route local calls when the caller dials the prefix digit 1 in error.
When this event occurs, an entry must have fields UPDTYPCA and TREAT
set to NP and UNDT, in that order. This entry has fields TYPCALL and
LOCAL equal to DD and Y, in that order. The fields must contain these entries
so that the call completes and the operating company does not apply charging.
For related information, see table LCASCRCN.

Enter data in Table LCASCRCN after you enter data in table PFXTREAT.
PFXTREAT (continued)
Table size
The system allocates memory for 128 prefix treatments.
Datafill
Datafill for table PFXTREAT appears in the following table.
Subfield or
TYPLCLCD see subfields Type of call and local code. This field
contains subfields PFXSELEC,
TYPCALL, and LOCCODE.
PFXSELEC Four-character vector of Prefix selector. Enter the prefix selector

the two predefined prefix assigned to the prefix treatment.
selectors mandatory
(MAND) or optional
(OPTL), or a maximum of
14 customer-definable
prefix selectors.
TYPCALL DD, NP, OA, or NL Type of call. Enter DD (direct dial), NP

(no prefix), OA (operator assisted), or
NL (nil) for the type of call.
For Traffic Operator Position System
(TOPS) calls, a mixture of 0 and 1 (OA
and DD) call types can be present.
Enter NL for these cases.
LOCCODE Y or N Local code. If the record is for a local

call, enter Y (yes). Enter N (no) if the
prefix treatment record is for a non-local
call.
297-8021-351 Standard 05.02 May 2001

PFXTREAT (end)
Subfield or
UPDTYPCA DD, OA, NP or NL Updated type of call. If the system

updates the type of call, enter this type
of call. The types of calls can be DD
(direct dial), OA (operator assisted), NP
(no prefix), or NL (nil). If the system
does not update the type of call, enter
the value for to field TYPCALL.
For Traffic Operator Position System
(TOPS) calls, a mixture of 0 and 1 (OA
and DD) call types can be present.
Enter NL for these conditions.
TREAT UNDT or TMTCNTL Treatment. If calls that route to the

prefix treatment can complete, enter
UNDT (undefined treatment) as the
treatment. If calls which route to the
prefix treatment are not allowed to
complete, enter TMTCNTL.
Datafill example
Sample datafill for table PFXTREAT appears in the following example.
MAP example for table PFXTREAT
TYPLCLCD UPDTYPCA TREAT

________________________________________________________
OPTL DD N DD UNDT
MNDT OA Y OA TMTCNTL
Table history
NA006
The description of field PFXSELEC changed according to the Dial Plan
Translations Enhancements feature in NA006.
PHDS1
Table name
Packet Handler to DS-1 Connection Table
This table contains the mapping of each DS-1 circuit to a particular T1
Interface Module (TIM) in a Digital Interworking Unit (DIU). PHDS1
provides the following information:
DS1 Endpoint
DIU Number
TIM Number

Table LTCPSINV must be datafilled before table PHDS1.
Table size
0 to 60 tuples
Datafill
The following table lists datafill for table PHDS1.
Subfield or
DS1ENDPT see subfields Data set 1 end point

This field consists of subfields PMTYPENO
and PORT.
PMTYPENO see subfields Peripheral module type number

This field consists of fields PMTYPE and and
PMNO.
PMTYPE LTC or LGC Peripheral module type

Enter the peripheral module type to be used in
this connection.
PMNO 0 to 255 Peripheral module number

Enter the peripheral module number of C-side
peripheral. Any entry outside of this range is
not valid.
297-8021-351 Standard 05.02 May 2001

PHDS1 (end)
Subfield or
PORT 0 to 63 Port
Enter the P-side port number on the C-side
peripheral. An entry outside of this range is
invalid.
DIUENDPT see subfields Digital interworking unit end point

This field consists of subfields DIU and TIM.
DIU 1 to 255 Digital interworking unit

Enter the DIU number. This corresponds to
the DIU agent number.
TIM 2 to 16 T1 interface module

Enter the T1 Interface Module slot number.
Datafill example
The following example shows sample datafill for table PHDS1.
MAP display example for table PHDS1
DS1ENDPT DIUENDPT
________________________________________________________
LTC 19 2 3 2
Table history
NA008
Table PHDS1 has been updated for the NA011 release of this document. This
update was made in response to a Problem Resolution System (PRS) request
for the NA008 timeframe.
NA004
A note was added to subfield PORT regarding BITS and RCC2 P-side links 0
and 8.
PHINFO
Table name
Packet Handler Information Table
Table PHINFO holds the exception packet service information assigned to an
ISDN logical terminal (LT). Information provided by this table consists of the
configuration of X.25 service on each logical terminal that has either D or PB
access privilege.
Table PHINFO contains the following information:

logical terminal identifier (LTID)
index
connection type
status
packet handler (PH) return code
service parameter and data

The following tables must be datafilled before table PHINFO.
LTGRP
LTDEF
Table size
0 to 64 000 tuples
297-8021-351 Standard 05.02 May 2001

PHINFO (continued)
Datafill
The following table lists datafill for table PHINFO.
Subfield or
PHKEY see subfields Packet handler key

This field consists of subfields LTID and
TUPLENUM.
LTID see subfields Logical terminal identification

This subfield consists of subfields LTGRP
and LTNUM.
LTGRP ISDN Logical terminal group

This field identifies the group of logical
terminals. Enter ISDN.
LTNUM 1 to 1022 Logical terminal number

Enter the number of the logical terminal within
a group.
TUPLENUM 0 to 50 Tuple number

Enter the index of packet parameter sets that
are associated with the logical terminal.
CONNTYPE ATT or DET Connection type

Enter whether the logical terminal is attached
(ATT) to a physical location in the packet
handler (PH) or detached (DET).
STATUS OK or SEND Status

Enter the status of the parameter set. Enter
OK if service parameters have been
successfully downloaded to the PH if the
connection type is ATT, or removed from PH
if connection type is DET. Enter SEND if
service parameters for this tuple are waiting
to be transferred to or removed from the PH
through the operation, administration, and
maintenance (OAM) processor.
PHINFO (continued)
Subfield or
PHSRC 0 Packet handler return code

Enter the return code of the last service
request sent down to the PH.
0 (zero) is the only valid entry.
PHPRMVAR see subfield Packet handler parameter variables

This field consists of subfield SERVPARM
and its refinements.
SERVPARM CUG, DC, Service parameter

DNA, LAPB,
Enter the service parameter type.
LAPD, PVC
Enter CUG (closed user group) and datafill
refinements on the following pages.
Enter DC (device controller) and datafill
refinements on the following pages.
Enter DNA (data network address) and
datafill refinements on the following pages.
Enter LAPB (link access procedure balanced)
and datafill refinements on the following
pages.
Enter LAPD (link access procedure on the
D-channel) and datafill refinements on the
following pages.
Enter PVC (permanent virtual circuit) and
datafill refinements on the following pages.
297-8021-351 Standard 05.02 May 2001

PHINFO (continued)
SERVPARM = CUG
If the entry in subfield SERVPARM is CUG, datafill refinements CUGNUM,
CUGINDEX, DNASPEC, and CUGPARMS as described below.
Subfield or
CUGNUM 0 to 65535 Closed user group number

Enter the CUG number.
CUGINDEX 0 to 255 Closed user group index

Enter the CUG index.
DNASPEC 0 to 9 DNASPEC
Enter up to 15 DNA specification multiples.
CUGPARMS see subfield Closed user group parameters

This field consists of subfield CUGSEL.
CUGSEL CUGDNIC Closed user group selectors

CUGTYP
Enter up to eight CUG selectors.
INCCALLS
NPI
OUTCALLS
PCUG
PVCUG
PRIVMEM
BOOLPARM Y or N Boolean parameters

If the entry in subfield CUGSEL is INCALLS,
OUTCALLS, PCUG, or PRIVMEM datafill this
refinement.
CUGDNIC 0 to 9999 CUGDNIC

If the entry in subfield CUGSEL is CUGDNIC,
datafill this refinement.
CUGTYP I or N Closed user group type

If the entry in subfield CUGSEL is CUGTYP,
NPI E164 or X121 If the entry in subfield CUGSEL is NPI, datafill

this refinement.
PHINFO (continued)
SERVPARM = DC
If the entry in subfield SERVPARM is DC, datafill refinements ORIGDNA,
ORIGLCN, RESPDNA, and DCPARMS as described below.
Field descriptions for conditional datafill (Sheet 1 of 3)
Subfield or
ORIGDNA 0 to 9 Originating data network access

Up to 15 multiples can be datafilled.
ORIGLCN 1 to 1024 Originating LCN

Enter the originating LCN.
RESPDNA 0 to 9 RESPDNA
Up to 15 multiples can be entered.
DCPARMS see subfield Device controller parameters

This field consists of subfield DCSEL.
DCSEL CUGFAC Device controller selectors

CUGINDX
Enter up to 23 DC selectors.
FASTSEL
NORMCHRG
ORIGNPI
PKTFAC
PKTRECV
PKTSEND
PRIORITY
RESPNPI
RPOADNIC
PRIORITY
PROCTET1
PROCTET2
PROCTET3
PROCTET4
RPOAFAX
TPTRECV
TPTSEND
TRFFAC
TPTFAC
WDWFAC
WDWRECV
WDWSEND
297-8021-351 Standard 05.02 May 2001

PHINFO (continued)
Subfield or
BOOLPARM Y or N Boolean parameter

If the entry in subfield DCSEL is CUGFAC,
PKTFAC, PRIORITY, RPOAFAX, TPTFAC,
TRFFAC, or WDWFAC, datafill this
refinement.
CUGIDX 0 to 16 Closed user group index

If the entry in subfield DCSEL is CUGINDX,
FASTSEL N, Y, or R FASTSEL
If the entry in subfield DCSEL is FASTSEL,
NORMCHRG N or R NORMCHRG
If the entry in subfield DCSEL is
NORMCHRG, datafill this refinement.
NPI E164orX121 NPI

If the entry in subfield DCSEL is ORIGNPI or
RESPNPI, datafill this refinement.
PKTSZ 128, 256, or PKTSZ

512
If the entry in subfield DCSEL is PKTRECV or
PKTSEND, datafill this refinement.
PROCTET1 0 to 255 PROCTET1

If the entry in subfield DCSEL is PROCTET1,


PHINFO (continued)
Subfield or

RPOADNIC 0 to 9999 RPOADNIC

If the entry in subfield DCSEL is RPOADNIC,
TPTRECV 3 to 12 TPTRECV
If the entry in subfield DCSEL is TPTRECV,
TPTSEND 3 to 12 TPTSEND
If the entry in subfield DCSEL is TPTSEND,
WDWRECV 1 to 7 WDWRECV
If the entry in subfield DCSEL is WDWRECV,
WDWSEND 1 to 7 WDWSEND
If the entry in subfield DCSEL is WDWSEND,
SERVPARM = DNA
If the entry in subfield SERVPARM is DNA, datafill refinements DNAPSPEC,
ACCLASS, GROUP, and DNAPARMS as described below.
Subfield or
DNASPEC 0 to 9 DNASPEC
ACCLASS 1 to 255 AC class

Enter the AC class.
297-8021-351 Standard 05.02 May 2001

PHINFO (continued)
Subfield or
GROUP alphanumeric Customer group name

(1 to 16
Enter the customer group name.
characters)
DNAPARMS see subfield Data network address parameters

This field consists of subfield DNASEL.
DNASEL BNPI Data network address selectors

BLKNUIACC
Enter the DNA selectors.
CHRGAL-LO
W
CHRGSUBS
CUGIDX
EXPLRPOA
EXTCUG
HPRECVPKT
HPSENDPKT
INACCESS
INFAST
INHPRC
INNCINTL
INONLY
INNPRC
INRCINTLNPI
NUIREQ OUT
OUTACCESS
OUTBLKNUIO
UTDP
OUTFASTRO
OUTFASTR
OUTFASTUR
OUTHP
OUTINTL
PHINFO (continued)
Subfield or
DNASEL OUTNPOUTO
(continued) NLY
OUTRCDEF
PCSINDX
PKT16 PKT32
PKT64
PKT128
PKT256
PKT512
PNPIRCFOR
CE
RECVPKTRE
CVTPT
RPOAPDNIC
RXWDW
SECNUI
SENDPKT
SENDTPT
SIGPCUG
SRVEXCH
TXWDW

If the entry in subfield DNASEL is
BLKNUIACC, CHRGALLOW, CHRGSUBS,
CUGIDX, EXPLRPOA, EXTCUG,
INACCESS, INFAST, INHPRC, INNCINTL,
INNPRC, INRCINTL, OUT, OUTBLKNUI,
OUTDP, OUTHP, OUTINTL, OUTNP,
OUTONLY, OUTRC, OUTRCDEF, PKT16,
PKT32, PKT64, PKT128, PKT256, PKT512,
RCFORCE, SECNUI, or SIGPCUG, datafill
this refinement.
NPI E164 or X121 NPI

If the entry in subfield DNASEL is BNPI, NPI,
or PNPI, datafill this refinement.
PCSINDX 0 to 255 PCSINDX

If the entry in subfield DNASEL is PCSINDX,
297-8021-351 Standard 05.02 May 2001

PHINFO (continued)
Subfield or
PKTSZ 16, 32, 64, PKTSZ

128, 256, 512
HPRECVPKT, HPSENDPKT, RECVPKT, or
SENDPKT, datafill this refinement.
RECVTPT 3 to 13 RECVTPT
If the entry in subfield DNASEL is RECVTPT,
RPOADNIC 0 to 9999 RPOADNIC

RPOADNIC, datafill this refinement.
RXDWD 1 to 7 RXDWD
If the entry in subfield DNASEL is RXWDW,
SENDTPT 3 to 13 SENDTPT
If the entry in subfield DNASEL is SENDTPT,
SRVEXCH 0 to 255 SRVEXCH

If the entry in subfield DNASEL is SRVEXCH,
TXDWD 1 to 7 TXDWD
If the entry in subfield DNASEL is TXWDW,
PHINFO (continued)
SERVPARM = LAPB
If the entry in subfield SERVPARM is LAPB, datafill refinement LAPBSEL
as described below.
Subfield or
LAPBSEL AFRMD Link access procedure balanced selectors

AFRMO
Enter up to 65 LAPB selectors and datafill the
AFRMOOS
appropriate refinements.
BADFRMDBA
DFRMO
BADFRMO-O
S CALLCOLL
CCFMT
CLLDDSE
CLLDSRV
CLLGDSE
CLLGSRV
CLRTMR
CPSIGS
CRCERRD
CRCERRO
CRCERRO-O
S CRQTMR
CTARIFDBIT
DCONLY
ENTRTHROT
EXITTHROT
FRMQD
FRMQO
FRMQOOS
FRMWDWKID
LETMR
IDLPBT3
IGNORADD
297-8021-351 Standard 05.02 May 2001

PHINFO (continued)
Subfield or
LAPBSEL IPDIPO
IPOOS
(continued)
IPTMO
LCERRD
LCERRO
LCERROOS
LCNBASE
LCNORD
LNKALARM
LNKPROC
LRCERRDLR
CERRO
LRCERRO-O
SMAXSTC
MULTDNAS
NATLTRF
NOLBUFD
NOLBUFO
NOLBUFO-O
S NORMDLY
NUIDGRD
NUIOSS
NUIOPT
NUMIVC
NUMLCN
NUMOVC
NUMPVCOCT
ETALGN
OCTETONLY
OVERUND
OVERUNO
OVERUNO-O
S
PHINFO (continued)
Subfield or
LAPBSEL PHFMT
(continued) PKTNEG
PMTCALL
PRERRD
PRERRO
PRERROOS
PRIODLY
RECVDIAG
RESETTMR
RESPDTMR
RESPT1
RESPTMR2
RESTRTTMR
RETRAND
RETRANO
RETRANO-O
SRETRYN2
SRVTST
THROT
THROTALRM
TPTNEG
TRANSDIAG
TRFCLASS
UNDRUND
UNDRUNOW
DWCEIL
WDWCLNEG
WDWNEG
X25TYP
AFRM 1 to 14 AFRM
If the entry in subfield LAPBSEL is AFRMD,
AFRMO, or AFRMOOS, datafill this
refinement.
BADFRM 1 to 14 BADFRM
If the entry in subfield LAPBSEL is
BADFRMD, BADFRMO, or BADFRMOOS,
297-8021-351 Standard 05.02 May 2001

PHINFO (continued)
Subfield or

If the entry in subfield LAPBSEL is CCFMT,
CPSIGS, CTARIF, DBIT, DCONLY,
IGNORADD, MULDNAS, NUIOPT,
OCTETONLY, PHFMT, PKTNEG,
PMTCALL, PTNEG, RECVDIAG, SRVTST,
THROT, THROTALRM, TOCTETALGN,
TRANSDIAG, or WDWNEGH, datafill this
refinement.
CALLCOLL EXT, NET, or CALLCOLL

BOTH
CALLCOLL, datafill this refinement.
CLLDDSE 0 to 63 CLLDDSE
If the entry in subfield LAPBSEL is CLLDDSE,
CLLGDSE 0 to 63 CLLGDSE
CLLGDSE, datafill this refinement.
CLLDSRV 0 to 63 CLLDSRV
If the entry in subfield LAPBSEL is CLLDSRV,
CLLGSRV 0 to 63 CLLGSRV
CLLGSRV, datafill this refinement.
CLRTMR 1 to 62 CLRTMR
If the entry in subfield LAPBSEL is CLRTMR,
CRCERR 1 to 14 CRCERR
CRCERRD, CRCERRO, or CRCERROS,
PHINFO (continued)
Subfield or
ENTTHROT 1 to 255 ENTTHROT

ENTRTHROT, datafill this refinement.
EXTTHROT 1 to 255 EXTTHROT

EXITTHROT, datafill this refinement.
FRMQ 1 to 255 FRMQ

If the entry in subfield LAPBSEL is FRMQD,
FRMQO, or FRMQOOS, datafill this
refinement.
FRMWDWK 1 to 127 FRMWDWK

FRMWDWK, datafill this refinement.
IDLETMR 1 to 62 IDLETMR
If the entry in subfield LAPBSEL is IDLETMR,
IDLPBT3 0 to 655 IDLPBT3

If the entry in subfield LAPBSEL is IDLPBT3,
IP 1 to 255 IP
If the entry in subfield LAPBSEL is IPD, IPO,
or IPOOS, datafill this refinement.
IPTMO 0 to 655 IPTMO

If the entry in subfield LAPBSEL is IPTMO,
LCERR 1 to 14 LCERR
If the entry in subfield LAPBSEL is LCERRD,
LCERRO, or LCERROOS, datafill this
refinement.
297-8021-351 Standard 05.02 May 2001

PHINFO (continued)
Subfield or
LCNBASE 1 to 1024 LCNBASE

LCNBASE, datafill this refinement.
LCNORD A or D LCNORD
If the entry in subfield LAPBSEL is LCNORD,
LNKALRM MINORorMAJ LNKALARM

OR
LNKALARM, datafill this refinement.
LNKPROC LAPB_DCE or LNKPROC

LAPBE_DCE
LNKPROC, datafill this refinement.
LRCERR 1 to 255 LRCERR

LRCERRD, LRCERRO, or LRCERROOS,
MAXSTC 1 to 15 MAXSTC
If the entry in subfield LAPBSEL is MAXSTC,
NATLTRF 1 to 255 NATLTRF

If the entry in subfield LAPBSEL is NATLTRF,
NOLBUF 1 to 14 NOLBUF
NOLBUFD, NOLBUFO, or NOLBUFOOS,
NORMDLY 0 to 10000 NORMDLY

NORMDLY, datafill this refinement.
PHINFO (continued)
Subfield or
NUIDGRD 1 to 255 NUIDGRD

NUIDGRD, datafill this refinement.
NUIOOS 1 to 255 NUIOOS

If the entry in subfield LAPBSEL is NUIOOS,
NUMIVC 0 to 1024 NUMIVC

If the entry in subfield LAPBSEL is NUMIVC,
NUMLCN 1 to 1024 NUMLCN

If the entry in subfield LAPBSEL is NUMLCN,
NUMOVC 0 to 1024 NUMOVC

If the entry in subfield LAPBSEL is NUMOVC,
NUMPVC 0 to 1024 NUMPVC

If the entry in subfield LAPBSEL is NUMPVC,
OVERUN 1 to 14 OVERUN
OVERUND, OVERUNO, or OVERUNOOS,
PRERR 1 to 14 PRERR
If the entry in subfield LAPBSEL is PRERRD,
PRERRO, or PRERROOS, datafill this
refinement.
PRIODLY 0 to 10000 PRIODLY

If the entry in subfield LAPBSEL is PRIODLY,
297-8021-351 Standard 05.02 May 2001

PHINFO (continued)
Subfield or
RESETTMR 1 to 62 RESETTMR
If the entry in refinement LAPBSEL is
RESETTMR, datafill this refinement.
RESPDTMR 0 to 10 RESPDTMR
RESPDTMR, datafill this refinement.
RESPT1 1 to 655 RESPT1

RESPT1, datafill this refinement.
RESPTMR2 1 to 62 RESPTMR2
RESPTMR2, datafill this refinement.
RETRAN 1 to 14 RETRAN
RETRAN, datafill this refinement.
RETRYN2 1 to 15 RETRYN2
RETRYN2, datafill this refinement.
TRFCLASS RC, NF, or NO TRFCLASS

TRFCLASS, datafill this refinement.
UNDRUN 1 to 14 UNDRUN
UNDRUND, UNDRUNO, or UNDRUNOOS,
WDWCEIL 1 to 7 WDWCEIL
WDWCEIL, datafill this refinement.
PHINFO (continued)
Subfield or
WDWCLNEG S or D WDWCLNEG
WDWCLNEG, datafill this refinement.
X25TYP DTE, X4D, X25TYP

X80, X84, or
XPL
X25TYP, datafill this refinement.
SERVPARM = LAPD
If the entry in subfield SERVPARM is LAPD, datafill refinement LAPDSEL
as described below.
Subfield or
LAPDSEL BADFRMD Link access procedure on the D-channel

BADFRMO selectors
BADFRMO-O
Enter up to 65 LAPD selectors and datafill the
S CALLCOLL
appropriate refinements.
CCFMT
CHKLRC
CLLDDSE
CLLDSRV
CLLGDSE
CLLGSRVCL
RTMR
CPSIGS
CRQTMR
CTARIF
DBITDCONL
Y FRMQD
FRMQO
FRMQOOS
FRMWDWK
IDLETMR
IDLPBT203
IGNORADD
LCNBASE
297-8021-351 Standard 05.02 May 2001

PHINFO (continued)
Subfield or
LCNORD
LNKALARM
LRCERRD
LRCERRO
LRCERRO-O
SMAXSTC
MSGRELS
MULTDNAS
NATLTRF
NORMDLY
NUIDGRD
NUIOSS
NUIOPT
NUMIVC
NUMLCN
NUMOVC
NUMPVC
OCTETALGN
LAPDSEL PHFMT
(continued) PKTNEG
PMTCALL
PRERRD
PRERRO
PRERROOS
PRIODLYRE
SETTMR
RESPDTMR
RESPT200
RESPTMR
RESTRT-TM
R RETRAND
RETRANO
RETRANO-O
S
RETRYN2SR
VTST
TPTNEG
TRANSDIAG
TRFCLASS
WDWCEIL
WDWCLNEG
WDWNEG
X25TYP
PHINFO (continued)
Subfield or
BADFRM 1 to 14 BADFRM
If the entry in subfield LAPDSEL is
BADFRMD, BADFRMO, or BADFRMOOS,

If the entry in subfield LAPDSEL is CCFMT,
CHKLRC, CPSIGS, CTARIF, DBIT,
DCONLY, IGNORADD, MULDNAS, NUIOPT,
OCTETALGN, PHFMT, PKTNEG, G,
RECVDIAG, SRVTST, TRANSDIAG, or
WDWNEG, datafill this refinement.
CALLCOLL EXT, NET, or CALLCOLL

BOTH
CALLCOLL, datafill this refinement.
CLLDDSE 0 to 63 CLLDDSE
CLLDDSE, datafill this refinement.
CLLGDSE 0 to 63 CLLGDSE
CLLGDSE, datafill this refinement.
CLLDSRV 0 to 63 CLLDSRV
CLLDSRV, datafill this refinement.
CLLGSRV 0 to 63 CLLGSRV
CLLGSRV, datafill this refinement.
CLRTMR 1 to 62 CLRTMR
If the entry in subfield LAPDSEL is CLRTMR,
297-8021-351 Standard 05.02 May 2001

PHINFO (continued)
Subfield or
FRMQ 1 to 255 FRMQ

If the entry in subfield LAPDSEL is FRMQD,
FRMQO, or FRMQOOS, datafill this
refinement.
FRMWDWK 1 to 127 FRMWDWK

FRMWDWK, datafill this refinement.
IDLETMR 1 to 62 IDLETMR
If the entry in subfield LAPDSEL is IDLETMR,
IDLPBT203 0 to 655 IDLPBT203

IDLPBT203, datafill this refinement.
LCNBASE 1 to 1024 LCNBASE

LCNBASE, datafill this refinement.
LCNORD A or D LCNORD
If the entry in subfield LAPDSEL is LCNORD,
LNKALRM MINOR or Link alarm

MAJOR
LNKALARM, datafill this refinement.
LRCERR 1 to 255 LRCERR

LRCERRD, LRCERRO, or LRCERROOS,
MAXSTC 1 to 15 MAXSTC
If the entry in subfield LAPDSEL is MAXSTC,
PHINFO (continued)
Subfield or
NATLTRF 1 to 255 NATLTRF

If the entry in subfield LAPDSEL is NATLTRF,
NORMDLY 0 to 10000 NORMDLY

NORMDLY, datafill this refinement.
NUIDGRD 1 to 255 NUIDGRD

NUIDGRD, datafill this refinement.
NUIOOS 1 to 255 NUIOOS

If the entry in subfield LAPDSEL is NUIOOS,
NUMIVC 0 to 1024 NUMIVC

If the entry in subfield LAPDSEL is NUMIVC,
NUMLCN 1 to 1024 NUMLCN

If the entry in subfield LAPDSEL is NUMLCN,
NUMOVC 0 to 1024 NUMOVC

If the entry in subfield LAPDSEL is NUMOVC,
NUMPVC 0 to 1024 NUMPVC

If the entry in subfield LAPDSEL is NUMPVC,
PRERR 1 to 14 PRERR
If the entry in subfield LAPDSEL is PRERRD,
PRERRO, or PRERROOS, datafill this
refinement.
PRIODLY 0 to 10000 PRIODLY

If the entry in subfield LAPDSEL is PRIODLY,
297-8021-351 Standard 05.02 May 2001

PHINFO (continued)
Subfield or
RESETTMR 1 to 62 RESETTMR
If the entry in refinement LAPDSEL is
RESETTMR, datafill this refinement.
RESPDTMR 0 to 10 RESPDTMR
RESPDTMR, datafill this refinement.
RESPT200 1 to 655 RESPT200

RESPT200, datafill this refinement.
RETRAN 1 to 14 RETRAN
RETRAND, RETRANO, or RETRANOOS,
RETRYN200 1 to 15 RETRYN200
RETRYN200, datafill this refinement.
TRFCLASS RC, NF, or TRFCLASS

NO
TRFCLASS, datafill this refinement.
WDWCEIL 1 to 7 WDWCEIL
WDWCEIL, datafill this refinement.
WDWCLNEG S or D WDWCLNEG
WDWCLNEG, datafill this refinement.
X25TYP DTE, X4D, X25TYP

X80, X84, or
XPL
X25TYP, datafill this refinement.
PHINFO (continued)
SERVPARM = PVC
If the entry in subfield SERVPARM is PVC, datafill refinements ORIGDNA,
ORIGLCN, RESPDNA, RESPLCN, and PVCPARMS as described below.
Subfield or
ORIGDNA 0 to 9 Originating data network address

ORIGLCN 1 to 1024 Originating LCN

Enter the originating LCN.
RESPDNA 0 to 9 Responding data network address

RESPLCN 1 to 1024 Responding LCN

Enter the RESPLCN.
PVCPARMS see subfield PVC parameters

This field consists of subfield PVCSEL.
PVCSEL MRECVPKT PVC selector

MRECVTPT
Enter the PVCSEL.
MRECVWFW
MSENDPKT
MSENDTPT
MSENDWDW
ORIOGNPI
PRIORITY
RESPNPI
SSENDPKT
BOOLPARM Y or N Boolean parameters

If the entry in subfield PVCSEL is
SSENDPKT, datafill this refinement.
PKTSZ 16, 32, 64, PKTSZ

128, 256, 512
MRECVPKT or MSENDPKT, datafill this
refinement.
297-8021-351 Standard 05.02 May 2001

PHINFO (continued)
Subfield or
MRECVTPT 3 to 13 MRECVTPT
MRECVTPT, datafill this refinement.
MRECVWDW 1 to 7 MRECVWDW
MRECVWDW, datafill this refinement.
MSENDTPT 3 to 13 MSENDTPT
MSENDTPT, datafill this refinement.
MSENDWDW 1 to 7 MSENDWDW
MSENDWDW, datafill this refinement.
NPI E164 or X121 NPI

If the entry in subfield PVCSEL is ORIGNPI or
RESPNPI, datafill this refinement.
PRIORITY HIGH or PRIORITY

NORMAL
If the entry in subfield PVCSEL is PRIORITY,
Datafill example
The following example shows sample datafill for table PHINFO.
PHINFO (end)
MAP display example for table PHINFO
PHKEY CONNTYPE STATUS PHSRC

PHPRMVAR
________________________________________________________
ISDN 10 0 ATT SEND 0

LAPB (RETRYN2 10) (X25TYP X84) (NUMPVC 10) $
ISDN 20 1 ATT SEND 0
CUG 20 200 012345678 (INCCALLS Y) $
297-8021-351 Standard 05.02 May 2001

PHINV
Table name
Packet Handler Inventory Table
Table PHINV provides the means to datafill the configuration of ISDN packet
handler (PH) nodes (PHN). The PHNs are maintained at the PH maintenance
and administration position (MAP) levels.
The PH consists of one or more access modules (AM) and resource modules
(RM) connected to the DMS by DS 1 links through one or more digital
interworking units (DIU).
AMs and RMs consist of a duplicated common bus, two independent common
memories, and a number of processing elements (PE) connected to the
common bus. Each PE can have one or more peripheral interface (PI) cards
associated with it.
A PH node refers to an AM, RM, or combined AM and RM (ARM). A PH

component refers to a PE, PI, or port.
Single-shelf ARM can be configured with PE and PI cards in slots 1 through

14. Dual-shelf ARM can also have PE and PI cards in slots 17 to 30 in addition
to 1 through 14. In all maintenance directives, PEs and PIs are identified by
their slot number.
Each tuple in table PHINV represents one AM, RM, or ARM. For each AM,
RM and ARM, table PHINV identifies the physical location of the hardware
plus the configuration of PEs and PIs.
Only link access procedure balanced (LAPB) or link access procedure on the
D-channel (LAPD) PEs can be configured through table PHINV. Other PEs
can be datafilled, but the information is not downloaded to the PH. The
Network Administration System (NAS) must be used to configure non-LAPB
or non-LAPD PEs.

There is no requirement to datafill other tables prior to table PHINV.
Table size
0 to 20 tuples
Table size is dynamically determined by the number of AMs, RMs, and ARMs
datafilled. If an existing tuple is changed or deleted, the PH node must first be
PHINV (continued)
offlined by means of the PH MAP (maintenance and administration position)

CI (command interpreter) command, OFFLN.
Datafill
The following table lists datafill for table PHINV.
Subfield or
PHNODE 0 to 19 Packet handler node

Enter the packet handler (PH) node
number. The PH node number is the key to
the table.
MNEMONIC alphabetic (1 to Packet handler node mnemonic

12 characters)
Enter the customer specified PH node
mnemonic that uniquely identifies this PH
node.
NODETYPE AM, ARM, or Node type

RM,
Enter the node type: AM (access module),
ARM (combined AM and RM), or RM
(resource module).
SHELF1 1 to 3 Shelf position

Enter the position of AM, ARM, or RM shelf
in the PH bay for the first shelf.
FRAME1 0 to 511 Frame number

Enter the frame number of the first shelf
where AM, ARM, or RM are mounted.
SHELF2 0 to 3 Shelf position

Enter the position of the AM, ARM, or RM
shelf in the PH bay for the second shelf. An
entry of 0 (zero) datafilled in this field means
that the node is single shelf.
FRAME2 0 to 511 Frame number

Enter the frame number of the second shelf
where AM, ARM, and RM are mounted.
297-8021-351 Standard 05.02 May 2001

PHINV (continued)
Subfield or
FLOOR 0 to 99 Floor location

Enter the floor location of PH bay.
ROW A to Z, Row location

AA to ZZ, Enter the row location of PH bay.
except I, II,
O, OO
PECONFIG see subfields Peripheral equipment configuration

This field is a vector of up to 30 peripheral
equipments (PE) and consists of subfields
PENUMBER, PETYPE, and PILIST.
Separate each subfield with a single space.
The PE configuration lists the PEs for the
AM, RM, and ARM. If less than 30 PEs are
required, end the list with a $ (dollar sign).
PENUMBER 1 to 14, Peripheral equipment number

17 to 30 Enter the slot of the PE.
Slots 15 and 16 are not valid entries for this
field.
PETYPE LAPB Peripheral equipment type

LAPD Enter the type of the PE.
LINK
MASTER
NETWORK
SERVER
TRUNK
X75
PHINV (continued)
Subfield or
PILIST DMA1 Peripheral interface list

DS30, Enter the appropriate number for the PE
type. Up to five PH peripiheral interface (PI)
V24_4P
types can be configured for a PE depending
V24_8P
on the type of PE as shown below. If less
V35_8P
than five PH PI types are required, end the
or list with a $ (dollar sign).
V35SCSI
PETYPE Number of PIs
LAPB 0 to 2
LAPD 1
LINK 0 to 5
MASTER 0 to 1
NETWORK 0 to 5
SERVER 0
TRUNK 0 to 5
X75 0 to 5
For LAPB and LAPD PEs only the following

PI types are allowed:
V24_4P
V24_8P
V35_8P
For MASTER PEs only the following PI type
is allowed:
V35SCSI
Datafill example
The following example shows sample datafill for table PHINV.
297-8021-351 Standard 05.02 May 2001

PHINV (end)
MAP display example for table PHINV
PHNODE MNEMONIC NODETYPE SHELF1 FRAME1 SHELF2 FRAME2

FLOOR ROW PECONFIG
________________________________________________________
0 A47 AM 2 6 3 6 1
(1 LAPB (V35SCSI) (V35_8P) $)
(2 LAPD ( V35_8P) $)
(3 SERVER $) $
PICNAME
Table name
Primary Inter-LATA Carrier Name Table
Table PICNAME lists the names of all of the carriers serving the DMS.
The first three tuples of table PICNAME are added at initial program load
(IPL) time. The first entry is reserved for system use and is identified
internally with tuple NODATA. The second tuple in table PICNAME is
NOCAR. If this tuple is used in table DNPIC, a subscriber is served but has
not chosen a primary carrier. The third tuple in table PICNAME is NILCAR.
If this tuple is used in table DNPIC, a nil carrier is assigned and no
presubscribed dialing is allowed.

Table OCCNAME must be datafilled before table PICNAME.
Table size
0 to 1000 tuples
Table PICNAME requires less than 1 kbyte of data store.
Datafill
The following table lists datafill for table PICNAME.
Field descriptions
Subfield or
PICNAME alphanumeric Carrier nameyThis field contains the valid

(up to 16 primary inter-LATA (local access and
characters) transport area) carriers found in table
OCCNAME. This is the key field.
Carrier names NOCAR and NILCAR appear
in table PICNAME if feature package
NTX710AA (LATA Equal Access System) is
present. These two carrier names have no
corresponding definition in table OCCNAME.
Datafill example
The following example shows sample datafill for table PICNAME.
297-8021-351 Standard 05.02 May 2001

PICNAME (end)
MAP display example for table PICNAME
PICNAME
________________________________________________________
NODATA
NOCAR
NILCAR
CARR3
CARR1
CARR2
Table history
TOPS10
The table size is increased to 1000 tuples by feature AF7376 in functionality
PICNAME Expansion, OSB00001.
PILOTGRP
Table name
Pilot Groups Table
Table PILOTGRP (Pilot Groups) lists the non-pilot member directory numbers
(NPMDN) for all Simultaneous Ringing (SimRing) groups defined on the
switch.
Note: The operating company cannot use the table editor to add tuples to or
delete tuples from table PILOTGRP. The operating company must use the
Service Order System (SERVORD) to perform these operations. The
operating company can use either the table editor or the SimRing user
interface to modify existing tuples in table PILOTGRP.
The switch blocks simultaneous access to the same SimRing group by

different users through SERVORD, the table editor, or the SimRing user
interface. An error message warns the user that the SimRing group
information is locked.

There is no requirement to datafill other tables prior to table PILOTGRP.
Table size
10 000 tuples
Datafill
The following table lists datafill for table PILOTGRP.
Field descriptions
GRPKEY 0 to 9999 Group key. SERVORD creates a tuple in

table PILOTGRP during provisioning of the
SIMRING line option. The SIMRING line
option uses the associated GRPKEY index
for subsequent references.
MEMBERS Up to 4 List of NPMDNs. This field stores the list of all

members, the NPMDNs of the SimRing group defined by
each ranging this tuple. The list can contain up to 4
from 4 to 30 members.
digits
297-8021-351 Standard 05.02 May 2001

PILOTGRP (continued)
Datafill example
The following example shows sample datafill for table PILOTGRP.
MAP display example for table PILOTGRP
GRPKEY MEMBERS
________________________________________________________
1 6136216076 2558 7236055 $
2 8196246082 $
4 6137217146 8197217164 96211234 $
Table history
NA010
The RES Simultaneous Ringing feature created table PILOTGRP.
The following table lists SimRing table control error and information
messages for table PILOTGRP.
SimRing table control error and information messages (Sheet 1 of 2)
Message Type Explanation
SIMRING FEATURE STATE IS Information This message warns the operating company
NOW INACTIVE that the SimRing feature state will change to
inactive.
This message displays when the operating
company does any of the following:
uses the EST command without entering
any members and tries to change the
SimRing feature state
deletes the last NPMDN from the NPMDN
list
sets the SimRing feature state to active
when the NPMDN list is empty
MEMBER LIST IS CURRENTLY Error This message warns the user that the SimRing
BEING EDITED BY ANOTHER group information is locked. This message
USER displays when another user is already editing
the SimRing group member list.
PILOTGRP (end)
SimRing table control error and information messages (Sheet 2 of 2)
Message Type Explanation
DUPLICATE MEMBER DNs Error This message displays when the operating
company tries to add identical NPMDNs using
the EST, ADD, or DEL command.
MEMBER DN MUST BE AT LEAST Error This message displays when the operating
4 DIGITS company tries to add an NPMDN with fewer
than 4 digits.
Note: If the NPMDN contains more than 30

digits, SERVORD displays a type mismatch
message.
UNSUPPORTED LCC. MEMBER Error This message displays when the operating
DN:NPANXXXXXX company tries to add a member that the
SimRing feature does not support.
NPANXXXXXX" indicates the 10-digit DN of
the unsupported member.
INVALID DIGITS ENTERED Error This message displays when the operating
company enters invalid digits for the SimRing
member or PIN. This error can occur during use
of the ADO, CHF, EST, ADD, or DEL command.
This error can also occur during use of the table
editor.
297-8021-351 Standard 05.02 May 2001

PINDATA
Table name
Personal Identification Number Data
Table PINDATA develops a database to support multiple two-digit and
three-digit validated personal identification numbers (PIN) for each
authorization code (authcode). The database supports 4096 lists of two-digit
PINs (maximum of 100 for each list) and 4096 lists of three-digit PINs
(maximum of 1000 for each list).

There is no requirement to datafill other tables prior to table PINDATA.
Table size
0 to 8192 tuples
Datafill
The following table lists datafill for table PINDATA.
Subfield or
KEY see subfields Key

This field consists of subfields MPIDX and
PINDIGS.
PINDATA (end)
Subfield or
MPIDX 0000 to Personal identification number index

8191(2 or 4
Enter the personal identification number (PIN)
digits)
index. Each index can be associated with 100
PINs or 1000 PINs depending on its index
value.
Indices 0 (zero) to 4095 are allocated for
two-digit PINs, and indices 4096 to 8191 are
allocated for three-digit PINs.
PINDIGS 2 or 3 digits Personal identification number digits

(program-me
Enter the PIN.
d) vector of up
to 3 digits 0 to
9, N, B, C, D,
E, F
(reserved)
Datafill example
The following example shows sample datafill for table PINDATA.
MAP display example for table PINDATA
KEY
_____________________________________________________________________
5553 758
297-8021-351 Standard 05.02 May 2001

PKTVPROF
Table name
Packetized voice profiles
This table defines packetized voice profiles and is indexed from table
TQCQINFO, field PKTVPROF.

There is no requirement to enter datafill into other tables before table
PKTVPROF.
A tuple cannot be deleted if there is an associated index in table TQCQINFO,

field PKTVPROF.
Table size
0 to 64 tuples
Datafill
The following table lists datafill for table PKTVPROF.
Subfield or
PROFNUM 0 to 63 Profile number. This field is the index into the table
and is accessed by table TQCQINFO, field
PKTVPROF.
PKTVFLDS see subfield Packetized voice fields. This field consists of

subfield CODEC.
PKTVPROF (continued)
Subfield or
CODEC G711 or G729 Code C. The field indicates the voice CODEC for
the call queue. The values are as follows:.
G711 - Enter this value for IP or non-IP
communication.
G729 - Enter this value for IP only
communication and datafill refinement SILEN..
SILEN NOSILSUP or Silence suppression. This subfield appears only

SILSUP when CODEC = G729. This subfield determines if
silence suppression is enabled. Silence
suppression discontinues the codec output if it
detects parts of a signal where there is no speech.
The values are as follows:.
SILSUP - Silence suppression. This is
achieved using the G.729AB voice codec
(G.729A protocol with silence suppression per
G.729 Annex B).
NOSILSUP - No silence suppression. This is
achieved using the G.729A voice codec
(G.729A protocol with no silence suppression).
Datafill example
The figure that follows shows sample datafill for table TQCQINFO.
MAP display example for table PKTVPROF
PROFNUM PKTVFLDS
_______________________________________________________________
0 G711
1 G729 NOSILSUP
2 G729 SILSUP
The above example shows default tuples 0 and 1.
297-8021-351 Standard 05.02 May 2001

PKTVPROF (end)
Table history
TOPS15
This table is created by feature 59022288 in functionality OPP Over IP,
OSB00101.
PLATAB
Table name
Physical Link Adapter (PLATAB) Table
Table PLATAB preserves the relationship between integrated link
maintenance (ILM) physical link adapter (PLA) links and pairs of access
identifiers over BCS applications.
Direct access to the table has limits. The customer has read-only access. Data
entry in a device that requires ILM supported resources, or as part of a restore
operation on the N + 1 BCS as part of a BCS application allows indirect access.

Does not apply because the table is write-protected against direct datafill.
Table size
From 0 to 2048 tuples. The number of tuples dynamically determines table
size.
Datafill
Datafill for table PLATAB appears in the following table.
Subfield or
PLAID see subfields Physical link adapter identifier. This tuple is a

unique identifier that ILM uses to identify a
physical link that uses the PLA. The physical
link connects a pair of access identifiers.
An access identifier refines the concept of
access key and access index more. An
access identifier specifies a particular
channel on an access. The PLAID field is
multiple with two parts: EPT_KEY and
INDEX.
EPT_KEY 0 to 255 Physical link adapter endpoint key. This

subfield contains a unique identifier that ILM
uses. The unique identifier identifies a pair of
access keys that connect by ILM transport
resources using PLA.
297-8021-351 Standard 05.02 May 2001

PLATAB (continued)
Subfield or
INDEX 0 to 127 Physical link adapter endpoint index. If more

than one PLA physical link is present between
two access keys, the PLA endpoint index can
differentiate between the links.
ACID1 see subfields Access identifier one. The first of a pair of

access identifiers between which the physical
link runs. This tuple is a multiple with three
parts: KEY, INDEX, and CHANNEL
KEY 0 to 1023 Access key. The access key part of the

access identifier.
INDEX 0 to 1023 Access index. The access index part of the

access identifier.
CHANNEL 0 to 1023 Access channel. The access channel part of

the access identifier.
ACID2 see subfields Access identifier two. The second of a pair of

access identifiers between which the physical
link runs. This tuple is a multiple with three
parts: KEY, INDEX, and CHANNEL
KEY 0 to 1023 Access key. The access key part of the

access identifier.
INDEX 0 to 1023 Access index. The access index part of the

access identifier.
CHANNEL 0 to 1023 Access channel. The access channel part of

the access identifier.
Datafill example
Sample datafill for table PLATAB appears in the following example.
PLATAB (end)
MAP example for table PLATAB
PLAID ACID1 ACID2

________________________________________________________
0 0 0 0 0 1 0 0
1 0 1 0 0 2 0 0
1 1 1 1 0 2 1 0
Table history
BCS26
Table PLATAB was introduced.
You must restore table PLATAB before you restore any of the inventory tables
of the devices that require ILM resources. These tables are APINV, LIMINV,
LIUINV, and NIUINV. This table must immediately follow table AKEYTAB.
297-8021-351 Standard 05.02 May 2001

PMEXCEPT
Table name
Peripheral Modules Excepted Table
Table PMEXCEPT contains peripheral modules (PM) that the PMTYP
operational measurements (OM) group PMTYP does not contain. With this
table, the operating company can exclude PM types from the subtotal for each
PM type in OM group PMTYP. The operating company can exclude PMs that
are in commissioning or under test. This condition does not affect the OM
counts of the subgroup total fields.

PMEXCEPT.
Table size
0 to 4095 tuples
The system statically allocates memory for this table for a maximum of 4096
entries at loadbuild time. The 4096 entries represent 256 words of protected
store.
Datafill
Datafill for table PMEXCEPT appears in the following table.
Field descriptions
Subfield or
NODE 0 to 4095 Node Enter the node number of the

peripheral module. The OM group PMTYP
does not include the OM counts of this
peripheral module.
Datafill example
Sample datafill for table PMEXCEPT appears in the following example.
PMEXCEPT (end)
MAP example for table PMEXCEPT
NODE
________________________________________________________
42
Querying node numbers

You can determine the node number of the PM to exclude from PMTYP
registers. To perform this action, use command OMSHOW at the MAPCI
level of the MAP terminal. Another method to determine this node number is
to use command QUERYPM at the PM level of the MAP terminal.
If the operating company has the command OMSHOW, the node number
appears before the PM name in the information field. To determine the node
number, obtain the device name (DEVNAME) in the information field. When
you have this name, enter the DEVNAME in single quotation marks. This
condition determines the node number. The letters inside the single quotation
marks must be in upper case. An example of this condition follows:
OMSHOW PM ACTIVE `DTC 7'
If the operating company has the command QUERYPM, use the PM-level
command POST. Use this command to identify the PM on which the other
PM-level commands can execute. Issue the command QUERYPM. The node
number appears in the MAP display after the heading NODE_NO.
297-8021-351 Standard 05.02 May 2001

PMLOADS
Table name
Peripheral Module Loads Table
Feature AL0131 (PM AutoloadingPhase II) provides a general autoload
capability for the peripheral module (PM) loader. Extended multiprocessor
system (XMS)-based PM (XPM) maintenance uses this capability to provide
automatic reloads of XPMs that require a new load.
The application of dual-plane loading occurs for first-level XPMs. This

condition reduces the load time of first-level XPMs.
The following node types provide PM autoload:

line trunk controller (LTC)
remote cluster controller (RCC)
message switch and buffer (MSB)
emergency stand-alone (ESA)
The system reloads LTC or RCC PM types that have a load with faults.
Operating company personnel do not have to interrupt when the system
reloads these LTC or RCC PM types. This condition reduces recovery time.
Table PMLOADS stores the device location of every PM load file. This table
stores mapping between the load names and devices on which the loads exist.
This condition permits autoload to locate load files without the interruption of
operating company personnel.
Note: The system does not activate autoloading for tape devices. The
storage of PM loads must occur on a disk device. The system does not check
the tuples the user enters during first entry of data. Every other add
operation checks that the device and files are present.
Office alarms
Use of the autoload option only occurs if a disk contains the load files. If the
system does not locate a PM load on the disk, the system raises a minor alarm.
This condition occurs because the magnetic tape center cannot recover the
PMs that require reloads. The magnetic tape center cannot recover these PMs
because the system cannot locate the load file.
PMLOADS (continued)
A minor alarm also occurs after PMLOADS locates invalid datafill for table
ESRVATTR. The invalid ESRVATTR datafill appears before it can cause an
outage.

The user must enter data in the following tables after table PMLOADS.
LTCINV
RCCINV
XESAINV
MSBINV
An exception to this condition occurs during the following events:

first data entry
dump and restore
In these events, the system adds tuples to table PMLOADS when the addition
of tuples occurs in tables LTCINV and RCCINV.
During first data entry and dump and restore, the system enters data in table
PMLOADS with a dummy entry. This condition occurs if the load name is not
in the table. When this condition applies to a switch, the dummy entry must
include the storage device for the PM load files.
Remove every use of a load name from every PM inventory table before you
can remove the load name from table PMLOADS.
Table size
0 to 255 tuples
297-8021-351 Standard 05.02 May 2001

PMLOADS (continued)
Datafill
The datafill for table PMLOADS appears in the following table.
Subfield or
load name alphanumeric PM loadfile name

(a maximum
Enter the PM load file name. The load file
of 32
name in this field must be the same as the
characters)
load file name specified in the inventory
tables.
ACTFILE alphanumeric Active PM loadfile name

(a maximum
Enter the active PM load file name.
of 32
characters)
Note: The active load file can be the original
load file or a patched load file.
ACTVOL alphanumeric Active loadfile storage device

(a maximum
Specify the device that stores the active load
of 16
file. The range is the set of disk drive unit
characters)
(DDU) volumes and system load module
(SLM) disks available to the computing
module (CM).
BKPFILE alphanumeric Backup PM loadfile name

(a maximum
Enter the backup load file name.
of 32
characters)
Note: In BCS36, the PM load file name is the
shipped load file. The PM load file must be
the same name as the name specified in field
load name.
PMLOADS (continued)
Subfield or
BKPVOL alphanumeric Backup loadfile storage device

(a maximum
Specify the device that stores the backup load
of 16
file. The range is the set of disk drive unit
characters)
(DDU) volumes and system load module
(SLM) disks available to the computing
module (CM).
UPDACT Y or N Automatic loadfile name update

Enter Y (yes) to update field ACTFILE
automatically with the patched load file name.
If you do not require an automatic update of
field ACTFILE, enter N (no).
Note: This field controls the ability of the load

file to receive load file patching.
The modified table PMLOADS stores data for the following:

the names of the active load file name
the backup load file name
the file locations
an update active load file to indicate if the user wants to activate load file
patching
Datafill example
Sample datafill for table PMLOADS appears in the following example.
297-8021-351 Standard 05.02 May 2001

PMLOADS (end)
MAP example for table PMLOADS
load name ACTFILE ACTVOL BKPFILE BKPVOL

UPDACT
________________________________________________________
LTI02C LTI02C S01DVOL1 LTI02C S01DVOL1

N
RMM34C RMM34C S00DVOL2 RMM34C S00DVOL2
N
M7CQA01 M7CQA01 S00DVOL1 M7CQA01 S00DVOL1
N
MPCX33AB MPCX33AB S01DVOL1 MPCX33AB S01DVOL1
N
Table history
BCS36
The following improvements were added to table PMLOADS to simplify
maintenance and office recovery:
field DEV was renamed ACTFILE
fields ACTVOL, BKPFILE, BKPVOL, and UPDACT were added
PMNODES
Table name
Peripheral Module Nodes Table
Table PMNODES contains data that specifies the configuration of the
XMS-based peripheral module (XPM) and subtending nodes connected to its
P-side. Each tuple contains the type of node, type of PM, number of ports,
number of terminals, external node number and other data. Node table data is
sent to the XPM by the computing module (CM) during a bulk download of
configuration data when the XPM is returned to service, and when nodes are
dynamically reconfigured on an in-service XPM.
Table PMNODES is a read-only table that contains data on all nodes resident
in each XPM. Data is added to this table automatically as tuples are datafilled
in the inventory tables, such as LTCINV (Line Trunk Controller Inventory) and
LCMINV (Line Concentrating Module Inventory). Attempts by a user to
change the data in this table are rejected.

There is no requirement to datafill other tables prior to table PMNODES.
However, during a one night process (ONP), table PMNODES must be
transferred before any of the following hardware inventory tables:
LTCINV (Line Trunk Controller Inventory)
RCCINV (Remote Cluster Controller Inventory)
LTCRINV (Line Trunk Controller Remote Inventory)
MSBINV (Message Switch And Buffer Inventory)
LCMINV (Line Concentrating Module Inventory)
RMMINV (Remote Maintenance Module Inventory)
RCUINV (Remote Carrier Urban Inventory)
RCSINV (Remote Concentrator SLC-96 Inventory)
RCTINV (Remote Concentrator Terminal Inventory)
XESAINV (Emergency Stand-alone Inventory)
IPMLINV (Interperipheral Message Link Inventory)
DLMINV (Digital Line Module Inventory)
XPEINV (Extended Peripheral Equipment Inventory)
IRLNKINV (Interlink Inventory)
297-8021-351 Standard 05.02 May 2001

PMNODES (continued)
Table size
The table size is dynamically extended when required. No restart is required
to increase the size. The table has a minimum size of 0 tuples and a maximum
size of 30 000 tuples. Each XPM can have a maximum of 118 tuples.
Datafill
The following table lists the datafill for table PMNODES.
PMNODES field descriptions (Sheet 1 of 3)
Subfield or
TABKEY 0-4095 0-117 The TABKEY field is the KEY field of the
table. It has two parts, they are: the external
node number and the internal node number.
The external node number refers to the
peripheral in which the data resides. The
internal node number references the specific
tuple in that XPM's node table. The default
value for each is 0.
EXTNDNUM 0-4095 This field contains the external node number,

that is assigned by the CM for the node
residing in that XPM's node table. The default
value is 0.
NODETYPE any valid node The node type field identifies the node type of
type the P-side node entry. The default value is
NIL_NODE.
PMTYPE any valid The peripheral module type field identifies the
peripheral peripheral module type in the P-side node
type entry. The default value is NIL_PMTYPE.
LEVEL 0-15 The level field identifies the distance from the
CM; for example, a line concentrating module
(LCM) designated level 2, the remote cluster
controller (RCC) designated level 1, and the
line trunk controller (LTC) that is hosting the
RCC designated level 0. The default value is
0.
MSGHOST 0-4095 The messaging host field contains the node

number of the peripheral responsible for
transferring messages to this specific node in
the node table. The default value is 0.
PMNODES (continued)
Subfield or
PHYSHOST 0-4095 The physical host field identifies which node

the element directly subtends. For example,
the physical host of an LCM is an RCC;
however, the LCM is also present in the LTC's
node table, which is not its physical host.
Although the LCM is not directly connected to
the LTC, the LTC has an entry in its node
table for the LCM and all other subtending
nodes. The default value is 0.
PORTS 0-127 This field indicates the number of ports

required by the node. This field may display
a number greater than zero even if the node
does not reserve ports on the host. The
default value is 0.
STPORT 0-255 This field contains the first port in the XPM
used by this node. If the node does not
reserve any ports on the host, this field is set
to zero. The default value is 0.
TERMS 0-4095 This field identifies the number of terminals

required by the node. This field always shows
a number greater than zero, even if the node
does not reserve terminals in the host. The
default value is 0.
STTERM 0-8675 The start terminal field shows the starting

terminal in the XPM used by the node. If the
node does not reserve terminals on the node,
then this field displays a zero. The default
value is 0.
PROTOCOL any valid The protocol field indicates the messaging

messaging protocol used between the P-side node and
protocol its host. The default value is MNIL (no
messaging protocol entry).
MS M or S This field indicates the master (M) or slave (S)

relationship of the P-side node and its host.
The default value is M.
IPML Y or N This field indicates whether the entry is an

interperipheral message link. The default
value is N.
297-8021-351 Standard 05.02 May 2001

PMNODES (continued)
Subfield or
MODE T or P This field indicates whether the P-side entry is

temporary (T) or permanent (P). The default
value is P.
SLLCON Y or N This field indicates whether the Site Line Load

Control feature is activated. The default value
is N.
NT6X28 Y or N This field indicates whether the XPM has a

NT6X28 card datafilled. The default value is
N.
LCMLGMEM Y or N This field indicates whether the LCM is a large

memory LCM. This field should always show
N for nodes other than LCM_NODE types.
RSVPORTS Y or N This field indicates whether the P-side node

reserves ports on the host node. The default
value is N.
RSVTERMS Y or N This field indicates whether the P-side node

reserves terminals on the host node. The
default value is N.
MATENODE Y or N This field indicates whether the P-side node is

a mate node of the host. this field should be
Y for dual RCCs. The default value is N.
PACKED Y or N This field indicates whether the P-side nodes

are compressed. This field is only valid for the
host node. The default value is N.
SUPPCDM Y or N This field indicates whether each unit of the

XPM supports the new node table format. this
field consists of a boolean value for each unit
of the XPM. The default value is YY.
CMINCTRL Y or N This field indicates whether the XPM is using

the new node table format. The default value
is N.
Datafill example
The following example shows sample datafill for table PMNODES.
PMNODES (end)
MAP display example for table PMNODES
TABKEY EXTNDNUM NODETYPE PMTYPE LEVEL MSGHOST PHYSHOST PORTS

STPORT TERMS STTERM PROTOCOL MS IPML MODE SLLCON NT6X28 LCMLGMEM RSVPORTS
RSVTERMS MATENODE PACKED SUPPCDM CMINCTRL
_________________________________________________________________________
22 1 22 LTC NODE LTC 0 22 22 16
0 641 1 MDS30 S N P N N N Y
Y N Y YY N
Table history
NA005
Table PMNODES was introduced.
297-8021-351 Standard 05.02 May 2001

PODPATTR
Table name
Public Office Dialing Plan Attributes Table
Table PODPATTR allows subscription to line attribute indexes for the AIN 0.1
Public Office Dialing Plan 3 to 10 (PODP) trigger. The table provides post
query processing for the AIN 0.1 PODP trigger based on the PODP number.
This table associates a PODP number with a line attribute index number.
Translation (Analyze_Route response) and normal digit collection
(Send_To_Resource response), and default routing are based on these line
attributes when present. When there is no entry in table PODPATTR for the
PODP directory number, the originator's line attributes are used.
Table PODPATTR digit pattern matching is most specific to least specific.

Fields PIC and LPIC subscription are mandatory fields for the PODP number.
The fields are used when the Analyze_Route response does not include carrier
or trunk group identification.
Note: The PODP trigger and the Specific_Digit_String (SDS) trigger are
one and the same. Datafill for table TRIGITM uses the SDS trigger. Datafill
for table TRIGGRP uses the PODP trigger.
PODPATTR in a multi-NPA office

The SCP can return an Analyze_Route message that contains the following
information:
The message is a seven-digit subscriber number.
The subscriber number is in response to a PODP trigger.
PODPATTR (continued)
When the message matches this information, the following characteristics

apply:
The home serving translations schema (HSTS), as defined by the
XLAPLAN in table PODPATTR, indexes table HNPACONT.
For duplicate NXXs, response translations uses the DN or route connected
with the NPA of the trigger.
Trigger criteria checking for subsequent PODP triggers uses the called
party digits prefixed with the NPA of the trigger.

The following tables must be datafilled before table PODPATTR.
LINEATTR
XLAPLAN
RATEAREA
OCCNAME
OCCINFO
Table size
0 to 8000 tuples
The system dynamically allocates the size of this table size.
Datafill
The following table lists datafill for table PODPATTR.
Subfield or
KEY alphanumeric Key

(N, 0 to 9, B,
Enter a digit string for the most-specific to
C, D, E, or F)
least-specific digit pattern matching for the
(up to 18
PODP DN.
digits)
LINEATTR alphanumeric Line attribute

(1 to 16
Enter a line attribute index corresponding to a
characters)
valid entry in field LNATTIDX in table
LINEATTR.
297-8021-351 Standard 05.02 May 2001

PODPATTR (continued)
Subfield or
PIC alphanumeric Primary inter-LATA carrier

(1 to 16
Enter the carrier name or abbreviation for the
characters)
carrier name corresponding to a valid entry in
field OCCNAME in table OCCNAME. This
subscribes the PODP DN to a PIC.
Enter NILC when no carrier is to be selected.
XLAPLAN alphanumeric Translation plan index

(up to 16
Enter the index into the XLAPLAN table.
characters)
RATEAREA alphanumeric Rate area index

(up to 16
Enter the index into the RATEAREA table.
characters)
PIC alphanumeric (1 Primary inter-LATA carrier

to 16
characters)
subscribes the PODP DN to a PIC.
Enter NILC when no carrier is to be selected.
LPIC alphanumeric Intra-LATA PIC

(1 to 16
characters)
subscribes the PODP DN to an LPIC.
Enter NILC for the PODP DN when no carrier
is to be selected.
Datafill example
The following example shows sample datafill for table PODPATTR.
PODPATTR (end)
MAP display example for table PODPATTR
KEY LINEATTR XLAPLAN RATEAREA PIC LPIC

________________________________________________________
1 1 613_P621_1 L613_NILLA_1 ATT ATT
Table history
NA012
Development activity 59007050 introduces changes to field LINEATTR. This
field now accepts an alphanumeric string instead of an integer string.
Added warning message.
NA011
Added fields XLAPLAN and RATEAREA.
Added information about PODPATTR in a multi-NPA office.
NA008
Increased the range of field LINEATTR index to 31 999.
NA007
Increased the range of field LINEATTR to 4095.
NA006
The table is new for this release.
When the trigger item transition tool has disabled trigger group subscriptions
and adds or changes are blocked, the customer receives the warning message
that follows:
Provisioning for AIN trigger groups has been diSabled.
When the trigger item transition tool is not disabled but the office is subscribed
to trigger items, the customer receives the warning message that follows:
TABLE PODPATTR IS INACTIVE, AS THE OFFICE IS SUBSCRIBED TO

TRIGGER ITEMS. USE LARP OPTION IN TABLE TRIGITM.
297-8021-351 Standard 05.02 May 2001

PORTNUMS
Table name
Portable Numbers
Table PORTNUMS identifies portable numbers served by the TOPS switch.
Before TOPS call processing can launch an LNP query for any number
(calling, called, billing), the number must be within the range found in table
PORTNUMS. Table PORTNUMS also identifies the Global Title Translations
(GTT) name used to route the LNP query.
TOPS call processing needs ten digits to check table PORTNUMS. So, if the
number is only seven digits, the NPA must first be derived using the method
described in the Translations manual under functionality LNP (OSEA0008),
section Operation", subsection DN 7- to 10-digit conversion".
AIN tables TRIGGRP and TRIGDIG are not checked to determine if a DN is

in a portable NPA-NXX.
An NPA-NXX is defined as portable if it is datafilled in table PORTNUMS.
The value in the GTTNAME field must be datafilled in field GTTNAME of

table C7GTTYPE in order to be used in this table. If a GTT is datafilled in table
PORTNUMS, it will not be allowed to be deleted from table C7GTTYPE.
Table PORTNUMS is specific to the TOPS system implementation of LNP.
To avoid unnecessary queries, the following types of numbers should not be

datafilled in table PORTNUMS:
800 numbers and similar service access codes
NPA-555 numbers

Table C7GTTYPE must be datafilled before table PORTNUMS.
Table size
0 to 32K words
PORTNUMS (continued)
Datafill
The following table lists datafill for table PORTNUMS.
Field descriptions
Subfield or
LNPKEY 3 to 10 digits Local number portability key. This is the key

into the table and is a digilator. Enter the
portable number. The range is from 3 to 10
digits and specifies ranges of portable
numbers.
Note: The excessive use of ten-digit datafill

will exhaust table PORTNUMS.
GTTNAME name from Global title translation name. Enter a GTT

table name for use in obtaining portability
C7GTTYPE information from the LNP database.
Datafill example
The following example shows sample datafill for table PORTNUMS.
297-8021-351 Standard 05.02 May 2001

PORTNUMS (end)
MAP display example for table PORTNUMS
LNPKEY GTTNAME

617 LRNGTT
6182201234 LRNGTT
61932 LRNGTT
619330 LRNGTT
619331 LRNGTT
619332 LRNGTT
619333 LRNGTT
619334 OSLRNGT
619335 LRNGTT
619336 LRNGTT
619337 LRNGTT
619338 LRNGTT
6193390 LRNGTT
6193391 LRNGTT
6193392 LRNGTT
6193393 LRNGTT
6193394 LRNGTT
6193395 OSLRNGT
6193396 LRNGTT
6193397 LRNGTT
6193398 LRNGTT
6193399 LRNGTT
Error messages for table PORTNUMS

The following error messages apply to table PORTNUMS.
Error messages for table PORTNUMS
The key must contain 3 to 10 The LNPKEY field identifies a range of

digits. portable numbers. It is a digilator field
which can contain 10 digits. If an
attempt is made to add a number with
an incorrect number of digits, this error
message is displayed.
Table history
TOPS07
Created by feature AF6553 in functionality TOPS LNP, OSEA0008.
POSITION
Table name
Position Table
Overview
Position tables
The two position tables appear in the following table.
Position tables
Table name Title
POSNAME List of Position Names Table
POSITION Position Table
Table POSITION stores the types of positions the switching unit contains. The
table stores the associated routes of these positions.
The position names for the switching unit appear in Table POSNAME.
The switching unit contains a number of fixed pseudo position names. Table
POSNAME allows the operating company to assign additional position names
if necessary. The following names are pseudo fixed position names.
AMAFAIL
A local, toll, or combined local/toll switching unit that has the office parameter
AMA_FAILURE_FREE_CALL set to N (no) requires this position name.
The parameter is in Table OFCENG. This position name specifies the office
route to where the system routes automatic message accounting (AMA) calls
when AMA failure occurs. This failure occurs when the system does not route
AMA calls free of charge.
CAMA
A toll or combined local/toll switching unit arrangement for central AMA
(CAMA) operation requires this position name. The system routes ANIFAIL
or ONI calls on a Super CAMA or AMR 5 trunk group to this position.
LAMA
Enter CAMA in field POS of table POSITION if a local or combined local/toll
switching unit is for local AMA (LAMA). Office parameter LAMA_OFFICE
is Y in table OFCOPT for local AMA (LAMA) operation.
297-8021-351 Standard 05.02 May 2001

POSITION (continued)
OOC
The overseas operator center (OOC) switching unit for incoming calls on type
OOC trunk groups requires position name OOC.
TOPS
A toll or combined local/toll switching unit arranged for Traffic Operator
Position System (TOPS) operation requires this position name. This position
is where the system routes ANIFAIL or ONI calls on an Incoming or two-way
TOPS trunk group.
A toll or combined local/toll switching unit that tandems 0+ or 0- calls to a

TOPS switching unit through a type ZI trunk group requires this position
name.
TSPS
A toll or combined local/toll switching unit that tandems 0+ or 0- calls requires
this position name. The switching unit that receives the tandem calls is
arranged for Traffic Service Position System (TSPS). The calls travel through
a trunk group with trunk group type ZI.
AMRX
A local switching unit arranged for AMR5 type signaling requires this position
name. The system routes a 0- call from a line to this position.
AOSS
A toll or combined local/toll switching unit arranged for Auxiliary Operator
Services System (AOSS) operation requires this position name. The system
routes 411, 555-1212, intercept, and 131 call types route from dedicated AOSS
trunk groups to this position.
The operating company can use the pseudo fixed position names CTOP, RTE1,
RTE2, RTE3, or RTE4. The operating company can specify additional
position names. If the operating company does not require this position name,
the default value is NONE.
Translation proceeds through table POSITION

Translation proceeds through table POSITION in the following occurrences:
In a local or combined local/toll switching unit arranged for 0+ or 0-
dialing, the line attribute table LINEATTR, field ZEROMPOS, specifies
the position to which the system routes 0- calls.
The system can route a code or block of codes for class of service
screening to a position. In this event, the position name the class of service
screening tables CLSVSCRC or CLSVSCRC.CLSVSCR, field POSN
associated with selector N contains the position name.
POSITION (continued)
The standard pretranslator table SDTDPRTCT.STDPRT, field POS with

selectors R, P, T, or S can contain the position name. This table contains
the position name when a code or block of codes routes directly from a
standard pretranslator table to a position.
A seizure (no digits) can occurs on an incoming CAMA call. In this event,
the system routes the call to a position. The definition of the position
appears in the SuperCAMA trunk group table TRKGRP type SC, field
NODIGRTE.
If the arrangement of a PBX is for 0+ or 0- dialing, the system routes a 0-
call to a position. The Two-way PBX DID/DOD or Digital trunk group
table, table TRKGRP types PX or P2, field ZEROMPOS specify this
position.
Translation paths from table POSITION

Translation from table POSITION routes to table CLLI or through table OFRT.
Digits can be prefixed or deleted in table OFRT. This action can occur if
implicit suppression of routing from table POSITION and a leading digit 0
does not occur. Translations paths that relied on the known suppression of
leading digit zero in table POSITION must change. This action makes sure the
clear suppression of leading digit 0 occurs.
Table POSITION stores the types of positions the switching unit contains.
This table also stores the associated routes. There are three different types of
input for this table.
The system uses route selector S when a call proceeds directly to a CLLI. The
CLLI can be a pseudo CLLI for the following:
a CAMA position
a TOPS position
an AOSS position, like CPOS or CAMA
a trunk group CLLI
The implicit deletion leading digit of zero does not occur in table POSITION.
For 0- calls, use selector T and suppress one leading digit explicitly in table
OFRT route selector N, field DELDIGS. CAUTION: This action deletes any
leading digit, not just digit 0. Calls with leading digits that are not 0 must
contain the correct number of outgoing digits.
The system uses route selector T when a call proceeds to the office route table
OFRT at specified route index = KEY.
297-8021-351 Standard 05.02 May 2001

POSITION (end)
The system uses route selector C when a call proceeds to one of two
destinations. The destination depends on the translation system (TRANSYS)
associated with the call. When TRANSYS is NA, the call proceeds as a
national route (NATRTE) specifies. When TRANSYS is IN, the call proceeds
as an international route (INTRTE) specifies.
The NATRTE and INTRTE can specify selector S or T.
For related information, refer to table POSNAME.
Route selectors
A description of the available route selectors appear in the following sections
of table POSITION:
POSTION route selector C
POSTION route selector S
POSTION route selector T
POSITION route selector C
Route selector C
Switching units with TOPS require position route selector C. This
requirement occurs when the digit 1 prefixes to an international call before the
system routes a TOPS position.
Two routes are present. The first route is for calls where the translation system
is national. The second route is for international calls.
Datafill
Data entries for table POSITION route selector C appear in the following
table.
Subfield or
POS AMAFAIL, Type of position. Enter the name assigned to

AMRX, the type of position. Enter CAMA for offices
AOSS, equipped with LAMA.
CAMA,
CTOP,
NONE, OOC,
RTE1, RTE2,
RTE3, RTE4,
TOPS, or
TSPS
PRTE see subfield Position route selector. This field contains

subfield PRTESEL. This field contains
refinements NATRTE and INTRTE.
PRTESEL C Position route selector. Enter the position

route selector C.
NATRTE see subfields National route. This field contains subfield

RTESEL. This field contains refinements
CLLI and EXTRTEID.
If field RTESEL contains S, enter data in
subfield CLLI.
If field RTESEL contains T, enter data in
subfield EXTRTEID.
RTESEL S or T Route selector. If a call routes directly to a

code in the CLLI table, enter S. If a call routes
through the Office Route table, enter T.
297-8021-351 Standard 05.02 May 2001

POSITION route selector C (continued)
Subfield or
CLLI alphanumeric Common language location identifier. If the

(1 to 16 entry in field PRTESEL is S, enter the code for
characters) the trunk group to which the system routes the
call.
If the entry in field POS is CAMA, field CLLI
must contain CPOS.
If the entry in field POS is TOPS, field CLLI
must contain TOPSPOS.
If the entry in field POS is AOSS, field CLLI
must contain AOSSPOS.
EXTREID see subfields External route identifier. If the entry in field

PRTESEL is T, enter data in field EXTRTEID.
This field contains subfields TABID and KEY.
TABID OFRT Table name. If the entry in field PRTESEL is

T, enter office route table OFRT. Any entry
outside the range for this field is incorrect.
KEY 1 to 1023 Key. The entry in field PRTESEL can be T. In

this event, enter the route list route reference
index in the office route table to which the
system routes the translation. Any entry
outside the range for this field is incorrect.
INTRTE see subfield International route. This field contains

subfield RTESEL and RTESEL refinements.
If the entry in field RTESEL is S, enter subfield
CLLI.
If the entry in field RTESEL is T, enter subfield
EXTRTEID.
Datafill example
Sample datafill for table POSITION route selector C appears in the following
example.
The system routes calls with national translation type directly to the TOPS
trunk group. The system routes international calls to the office route table.
The entry in the Office Route table has the N selector and prefix the digit 1.
The entry routes to the TOPS trunk group.
POSITION route selector C (end)
MAP example for table POSITION route selector C
POS PRTE
________________________________________________________
TOPS C S TOPSPOS T OFRT 24
297-8021-351 Standard 05.02 May 2001

POSITION route selector S
Route selector S
A switching unit that is not TOPS with international dialing requires position
selector S. The switching unit requires selector S when calls to the position
route directly to a CLLI code that table CLLI recognizes. International dialing
requires prefix digit 1.
Datafill
The datafill for table POSITION route selector S appears in the following
table.
Field descriptions
Subfield or

AOSS, that have LAMA.
CAMA,
CTOP,
NONE, OOC,
RTE1, RTE2,
RTE3, RTE4,
TOPS, or
TSPS
PRTE see subfields Position route selector. This field contains

subfields PRTESEL and PRTESEL
refinement CLLI.
PRTESEL S Position route selector. When translation

routes to a CLLI, enter selector S.
CLLI alphanumeric Common language location identifier. Enter

the CLLI code assigned to the trunk group to
which the system routes the call.
If field POS contains CAMA, field CLLI must
contain CPOS. If field POS contains TOPS,
field CLLI must contain TOPSPOS. If field
POS contains AOSS, field CLLI must contain
AOSSPOS.
Datafill example
Sample datafill for table POSITION route selector S appears in the following
example.
POSITION route selector S (end)
The system routes all calls to CAMA position to the CAMA position talk
circuits. Table CLLI contains the assignments for these circuits to fixed
pseudo code CPOS.
MAP example for table POSITION route selector S
POS PRTE
________________________________________________________
CAMA S CPOS
297-8021-351 Standard 05.02 May 2001

POSITION route selector T
Route selector T
The system requires this selector when the switching unit is not Traffic
Operator Position System (TOPS) with international dialing. International
dialing requires a prefix digit 1. The system requires this selector with calls
to the position route through table OFRT.
When translation routes to the Office Route table, enter data in fields POS and
FSTRTE as follows.
Datafill
Datafill for table POSITION route selector T appears in the following table.
Field descriptions
Subfield or

AOSS, equipped with LAMA.
CAMA,
CTOP,
NONE, OOC,
RTE1, RTE2,
RTE3, RTE4,
TOPS, or
TSPS
PRTE see subfields Position route selector. This field contains

subfields PRTESEL and PRTESEL
refinement EXTRTEID.
PRTESEL T Position route selector. If translation routes to

the Office Route table, enter selector T.
EXTRTEID see subfields External route identifier. This field contains

subfields TABID and KEY.
TABID OFRT Table name. Enter the office route table

name OFRT. Entries out of the range for this
field are not correct.
KEY 1 to 1023 Key. Enter the route reference index of the

route list in the office route table to which
translation routes. Entries out of the range for
this field are not correct.
POSITION route selector T (end)
Datafill example
Sample datafill for table POSITION route selector T appears in the following
example.
This example is for an entry in table POSITION for a local or combined

local/toll switching unit arranged for TOPS. The position CTOP is the route a
line takes when a 0+/- call occurs.
The route reference index 21 in table OFRT must specify the outgoing trunk
group to TOPS with trunk group type OP.
MAP example for table POSITION route selector T
POS PRTE
________________________________________________________
CTOP T OFRT 21
297-8021-351 Standard 05.02 May 2001

UCS data schema 1-139
POSNAME
Table name
Position Name (POSNAME)
Table POSNAME lists the position names assigned to the switch. The switch
has a number of fixed pseudo position names. Table POSNAME allows the
operating company to assign additional position names, if required.
The pseudo-fixed position names are as follows.

AMAFAIL: This position name is required in a local, toll, or combined
local/toll switch that has the parameter AMA_FAILURE_FREE_CALL
set to N in the OFCENG table. This position name should specify the office
route to which all AMA calls are routed during AMA failure when AMA
calls are not routed free of charge.
CAMA: This position name is required in a toll or combined local/toll
switch arranged for CAMA operation and is the position to which
ANIFAIL or ONI calls on a super CAMA or AMR 5 trunk group are
routed.
TOPS: This position name is required in a toll or combined local/toll
switch arranged for TOPS operation and is the position to which ANIFAIL
or ONI calls on an incoming or two-way TOPS trunk group are routed.
This position name is required in a toll or combined local/toll switch which
tandem 0+ or - calls to a TOPS switch by means of a trunk group with trunk
group type ZI.
TSPS: This position name is required in a toll or combined local/toll
switch which tandem 0+ or - calls to a switch arranged for TSPS by means
of a trunk group with trunk group type ZI.
AMRX: This position name is required in a local switch arranged for
AMR5 type signaling and is the position to which a 0- call from a line is
routed.
AOSS: This position name is required in a toll or combined local/toll
switch arranged for AOSS operation and is the position to which 411,
555-1212, intercept, and 131 types of call route from dedicated AOSS
trunk groups.
The operating company can use pseudo-fixed position names CTOP, RTE1,
RTE2, RTE3, or RTE4, and can specify additional position names, if required.
When a position name is not required, the default value is NONE.
NA DMS-100 Data Schema Reference Manual LET0017

1-140 UCS data schema
POSNAME (continued)
Requirements
The following requirements are for the POSNAME table.
In a local or combined local/toll switch arranged for 0+ or - dialing, the
position to which 0- calls are to be routed is specified in Line Attribute
table.
When a code or block of codes for class of service screening have to route
to a position, the position name is specified in the class of service screening
tables CLSVSCRC or CLSVSCR.
When a code or block of codes routes directly from a standard pretranslator
table to a position, the position name is specified in the standard
pretranslator table STDPRT.
When a seizure (no digits) occurs on an incoming CAMA call, the position
to which the call is routed is defined in the Super CAMA trunk group data.
When a PBX is arranged for 0+ or - dialing, the position to which a 0 - call
is routed is specified in the two-way PBX DID/DOD or digital trunk group
data.
Translation from the position table route directly to the CLLI table or via
the office route table when prefixing or deletion of digits is required.
Each of the position names are assigned a value (0-15) in the POSNAME
table.
Position NONE is assigned the value of 0.
Forward initial input to Northern Telecom for production of an input data
tape.
Table size
Memory is automatically assigned for a maximum of 16 positions.
297-8021-351 Standard 06.02 July 2002

UCS data schema 1-141
POSNAME (end)
Field descriptions
The following table describes field names, subfield names, and valid data
ranges for table POSNAME.
Subfield or
VALUE 0-32 767 VALUE. Enter the numeric value assigned to

the position name.
SYMBOL NONE or NAME. Enter NONE if value is equal to 0;

alphanumeric otherwise, enter the name of the position.
vector of up to
32 characters
Datafill example
The following example shows datafill for table POSNAME. It shows input
data for position names NONE and CAMA, which are assigned values of 0
and 1, respectively.
VALUE SYMBOL

0 NONE
1 CAMA
NA DMS-100 Data Schema Reference Manual LEC0017

PRECONF
Table name
Preset Conference Table
Table PRECONF contains information on Integrated Business Network (IBN)
preset conferences in the office.
For an IBN switch, the only conference type (field CONFTYPE) allowed is
IBN.
This table allows all IBN customer groups to assign 50 conferees for each
conference.
Entries in table PRECONF are sorted by preset conference identifier (field

PRECONF) and conferee identifier (field CONFEREE). The first entry to
appear for each conference is always conferee 0 (zero). This tuple must be the
first one added to a new preset conference, and serves the following purposes:
This tuple contains the conference directory number (DN), and other
fields.
This tuple is always present when data is entered for a particular preset
conference, and can be used to locate that conference in table PRECONF.
If this tuple is not found, no data was entered for a conference.
Conferees are added or deleted from a particular conference one at a time.
The tuple associated with conferee 0 can be used to delete all the conferees
in the conference at once. By deleting this tuple, the entire conference is
deleted from table PRECONF.
A preset conference is initiated by dialing a predefined conference DN. The

conference feature originates calls to a maximum of 50 DNs simultaneously.
For IBN preset conference, the presence of the tone depends on the datafill of
field IMMSTART. This field determines the start of an IBN preset conference.
297-8021-351 Standard 05.02 May 2001

PRECONF (continued)
Termination of the tone or announcement occurs under one of the following

conditions:
All conferees have answered.
A full complement of attempts at call completion has been made.
Originator forces the conference by pressing the # key on a 2w, 12-key dual
tone multifrequency (DTMF) station.
Note: If the originator initiates from a DP station, the conference does

not start until all conferees have either answered or two attempts at both
primary and secondary addresses (DN) have been made.
When the conference is forced, attempts to complete calls to unanswered

conferees continue without audible tone or announcement. Subsequent
answering conferees who join the conference neither hear the tone or
announcement nor provide any indication to the existing conferees that they
have joined the conference. If an announcement circuit is not available, the
notification defaults to tone.
In order to have announcement or notification tone, the following tables must

be datafilled:
CLLI
CLLIMTCE
ANNS
ANNMEMS
STN
PRECONF
To use an announcement for preset conference notification, the standard

notification common language location identifier (CLLI) in table PRECONF
must be the same as in table ANNS.
To use a tone for preset conference notification, the standard notification tone
CLLI is hard-coded as PCNOR in field NOTICILLI. These must be datafilled
in table STN and in table PRECONF.
For IBN preset conference, if the IBN station customer group has used its
maximum number of six-port conference circuits, the originator is routed to
reorder tone unless the preset conference is datafilled as an emergency type
conference.
PRECONF (continued)
An IBN station not permitted to originate a conference must dial 0 (zero) to

access the attendant. The attendant can then dial the preset conference DN and
transfer the call to the station upon hearing ringing tone.
An IBN preset conference can also be originated by a direct-inward-dial (DID)

agent, for example, plain ordinary telephone service (POTS) line or incoming
trunk, depending on the datafill of the preset conference.
Since there can be more than one originator for a conference, when an attempt
is made to originate a conference that has already been initiated, the second
originator is routed to busy tone.
For an IBN preset conference, the customer group and a network class of
service (NCOS) is datafilled for the conference to allow for proper screening
and locating of the appropriate translator.
For an IBN preset conference, there is no requirement for conferees to belong

to the same customer group.
Automatic retrial is provided and one alternate address for each conferee is
also available if required. Automatic retrial is attempted on all conferees that
have not returned answer supervision within an adjustable interval of 15 to 60
s after the call to that conferee was originated. If a call to a primary address
fails to complete within two trials and the conferee has an alternate address,
two call attempts are directed to the alternate address.
Retrials are not attempted on an address that is a secondary conference bridge.
For IBN preset conference, in the case of trunk groups that do not return true
answer supervision (for example, 5X25 and FX on digital carrier module
[DCM] trunks), a tone detector is used to determine answer. As above, if
answer is not detected after two attempts, the alternate address is usedif one
exists.
If answer propagation is interrupted, the feature cannot complete to that

conferee (for example, if conferee has line option FNT or inward wide area
telephone service [INWATS]).
For an IBN preset conference, the conference data can be set so that the
conference starts as soon as the first conferee answers. In this case, the
answer causes audible ringing to the originator to stop and the conference to
begin. Attempts to complete the calls to unanswered conferees continue,
without audible ring. As other conferees answer, they are connected into the
conference after 400 ms of conference warning tone (440Hz + 480Hz) has
been applied.
297-8021-351 Standard 05.02 May 2001

PRECONF (continued)
The conference can also have a delayed start. When the first conferee answers,
a tone or announcement according to datafill is attached to the conference
bridge. The tone or announcement continues as an audible signal to answering
conferees until 2 s after all conferees have answered. The originator can force
the conference by pressing the # key on a 2w, 12-key DTMF set.
Secondary conferencing, which is the ability to interconnect with remote

conference bridges, is permitted. When a conference is activated and one of
the addresses requires a secondary bridge, the address is processed in a normal
manner and directed toward the office serving the secondary equipment. All
conferee DNs that are secondary conferences are identified in table
PRECONF.
All connections are automatically released and equipment is returned to idle

when all the conferees have gone onhook. Individual bridges are released from
multiple bridge conferences as soon as the last conferee connected to them
goes onhook. Whenever a conferee disconnects, a 400-ms burst of conference
exit tone (350Hz + 440Hz) is provided to all other members of the conference.
For IBN preset conference, datafill allows for the originator to be in control of
the conference. In this case, when the originator goes on-hook, the conference
is taken down even if there are conferees still on the bridge. If the originator
does not control the call, when a conferee disconnects from the bridge, a check
is made for the presence of DMS stations or trunks with disconnect
supervision. If no station or trunk of the described type is a conferee, the
conference is taken down (even though there can be active conferees with
no-disconnect type trunks).
If the originator of the preset conference is an IBN line that is a member of the
preset conference customer group, the originator is either allowed to add
additional conferees once the conference is established, or prevented from
adding additional conferees at this time, depending on the value in field
ADDON.
If the value in field ADDON is Y (yes) and the preset conference is established
(all conferees having answered or abandoned or the conference was forced to
start), addon can begin. The originator can add on up to a maximum of 30
conferees, including the originator, the preset conference conferees, and the
addon conferees. Only the originator has the capability of adding on
conferees.
PRECONF (continued)
Feature Interaction for IBN Preset Conference

If conferees that are connected to the switch where the preset conference is
being originated have any of the features listed below, these features remain
active for the incoming conference call:
Call Forwarding No Answer
Call Forwarding Busy
Call Forwarding Intragroup
If the primary address does not answer, call forwarding is attempted if it is

activated.
On origination to a conferee, routing features Expensive Route Warning Tone

and Off-hook Queuing are deactivated.
When a conferee is connected to a preset conference, the following features are

disabled for the duration of the call:
Call Waiting
Three-way Calling
Busy Verification of Lines and Trunks
Flash Recall
Executive Busy Override
The feature does not allow for preemption of the conference bridges since the
use of bridges by a customer group is limited according to datafill.
Station message detail recording (SMDR) may be applicable to one, several or

all of the legs of the conference call. Each leg, once added to the conference
call, is identified as a conference call in the SMDR record though use of the
originating feature code for preset conference.
Each preset conference can contain up to 50 conferees for each conference,

beginning with the number 0 (zero).
297-8021-351 Standard 05.02 May 2001

PRECONF (continued)
An Australian telephone user part (ATUP) trunk can be a conferee in an IBN

preset conference call. The following actions apply to an ATUP conference
call:
After the conferee answers, the receipt of a Clear Back (CBK) message
indicates the immediate disconnect of that party and is handled the same
as a conferee exit.
If the conference is taken down because the originator has exited, a Clear
Forward (CLF) message is sent to clear the trunks.
No ATUP messages are sent to existing conferees when other parties join
or exit the conference. The indications given by the feature are provided
as-inband tones only. If the conference drops down to a single conferee, a
CLF message is sent, disconnecting the remaining conferee from the
conference bridge.

The following tables must be datafilled before table PRECONF.
NCOS
NARDATA
Datafill
0 to 2048 tuples
Memory is dynamically allocated in blocks of 32.

Subfield or
PCNFKEY see subfields Preset conference key

This field consists of subfields PRECONF and
CONFEREE. This field is the key to the table.
PRECONF 0 to 63 Preset conference identifier

Enter the number assigned to the preset
conference by the operating company.
CONFEREE 0 to 49 Conferee identifier

Enter the number assigned to the conferee by
the operating company. Conferee 0, which is
used to hold the conference directory number
(DN), must be entered first.
PRECONF (continued)
Subfield or
CONFADDR numeric (up to Conference address

18 digits)
If the preset conference is for IBN, enter the
conference address.
PCNFVAR see subfields Preset conference variables

This field consists of subfields CLASS,
ALTADDR, TIMEOUT, CONFTYPE,
CUSTGRP, NCOS, ORIGCONT, ADDON,
DIDORIG, EMERG, ATDREQ, IMMSTART,
and NOTICL1I.
CLASS A, C, D, or P Conference class

If an alternate address is required in addition
to the primary address, enter A and datafill
refinements ALTADDR and TIMEOUT on the
following pages.
If the primary address consists of a secondary
conference located on another switch, enter
C and datafill refinement TIMEOUT on the
following pages.Secondary conferencing is
the ability to interconnect with remote
conference bridges.
If the entry is for conferee 0, enter D. This
must be the first entry made for the
conference. Datafill refinements
CONFTYPE, CUSTGRP, NCOS,
ORIGCONT, ADDON, DIDORIG, EMERG,
ATDREQ, and IMMSTART on the following
pages.
If only a primary address is required, enter P
and datafill refinement TIMEOUT on the
following pages.
297-8021-351 Standard 05.02 May 2001

PRECONF (continued)
CLASS = A
If the entry in field CLASS is A, datafill refinement ALTADDR as described
below.
Subfield or
ALTADDR numeric (up to Alternate address

18 digits)
If the preset conference is for IBN, enter an
alternate address.
CLASS = A, C or P
If the entry in field CLASS is A, C, or P, datafill refinement TIMEOUT as
described below.
Subfield or
TIMEOUT 15 to 300 Variable timeout

Enter the variable timeout in seconds.
If the entry in field CLASS is A, the range is 15
to 60. If a call to the conferee's primary
address receives no answer on the second
trial, the call is placed to the alternate
address. If no answer is received before the
timeout (the same timeout is used for the
primary and alternate address) the call is
placed a second time to the alternate address
and if no answer is received before timeout,
the conferee is not included in the
conference.
If the entry in field CLASS is C, the range is 15
to 300.
If the entry in field CLASS is P, the range is 15
to 60. If a call to the conferee's primary
address receives no answer before timeout,
the call is placed a second time to the primary
address and if no answer is received before
timeout, the conferee is not included in the
conference call.
Go to field OPTIONS on the following pages.
PRECONF (continued)
CLASS = D, IBN preset conference

If the value of selector CLASS is D and the preset conference is for IBN,
datafill refinement CONFDATA as described below.
Subfield or
CONFDATA see subfield Conference data

This field consists of subfield CONFTYPE.
CONFTYPE IBN Conference type

Enter IBN to indicate an IBN type of preset
conference and datafill refinements
CUSTGRP, NCOS, ORIGCONT, ADDON,
DIDORIG, EMERG, ATDREQ, and
IMMSTART.
CUSTGRP alphanumeric Enter the name of the customer group as

(1 to 16 assigned in table CUSTHEAD.
characters)
NCOS 0 to 511 Network class of service

Enter the network class of service (NCOS)
number assigned to the preset conference.
ORIGCONT Y or N Originator control

If the preset conference is to be taken down
when the originator of the conference goes on
hook, enter Y (yes). To allow the preset
conference to continue after the originator
goes on hook, enter N (no).
ADDON Y or N Conference add ons

If the originator of this IBN preset conference
is allowed to add additional conferees to the
conference once the conference is
established, enter Y. Otherwise, enter N to
indicate that additional conferees cannot be
added.
DIDORIG Y or N Direct-inward-dial origination allowed

If a direct-inward-dial (DID) party is allowed to
originate a preset conference, enter Y.
Otherwise, enter N.
297-8021-351 Standard 05.02 May 2001

PRECONF (continued)
Subfield or
EMERG Y or N Emergency conference

If a preset conference is allowed to originate
even if the customer group is already using its
maximum number of six-port circuits, enter Y.
Otherwise, enter N.
ATDREQ Y or N Audio tone detector required

An attempt to use a audio tone detector (ATD)
is done for all calls that use trunks that do not
return true answer supervision. If the call
does not continue when ATD is not available,
enter Y. If the call does continue without the
use of an ATD, enter N.
XTRADATA see subfield Extra data

This field consists of subfield IMMSTART.
IMMSTART Y or N Immediate start

If the preset conference starts as soon as the
first conferee answers, enter Y and go to field
OPTIONS on page Section , "CLASS = all
entries" on page -218.
If the preset conference starts only after all
conferees have answered, enter N and
datafill refinement NOTICLLI.
NOTICLLI PCNOR or Standard preset conference notification

alphanumeric
Enter PCNOR for the standard notification
(1 to 16
tone or any announcement common
characters)
language location identifier (CLLI) entered in
table ANNS.
PRECONF (continued)
CLASS = all entries

For all entries in field CLASS for BCS36 and up, datafill field OPTIONS as
described below.
Subfield or
OPTIONS see subfield Options

(BCS36-)
This field consists of subfield PCNFOPTN.
PCNFOPTN NARS Preset conference option

(BCS36-)
Enter up to two options. If less than two
options are required, end the list with a $
(dollar sign).
Enter NARS (network access registers) for
the network access register (NAR) feature
and datafill refinement NARNAME. Feature
NAR is used to throttle (regulate a call's ability
to terminate) incoming calls. If the original
termination of an incoming throttleable call is
unavaiable, the incoming NAR member
associated with the call continues to be
associated with the call. No other incoming
NAR members can be access due to the final
termination.
NARNAME alphanumeric Network access register name

(BCS36-) orNILNAR
Enter the NAR that a call must have access
tugh before terminating on the feature. The
NAR name is datafilled in table NARDATA.
If NILNAR is entered, the default NAR
entered in table CUSTENG is used.
Datafill example
The following example shows sample datafill for table PRECONF.
This example is datafilled for an IBN preset conference with the following
characteristics:
The conference identifier is 3, the conference DN is 226-7432, the
conference type is IBN, the customer group is BNRGRP, the NCOS
number is 126, the originator controls the conference, the originator can
add additional conferees to the conference once the preset conference is
297-8021-351 Standard 05.02 May 2001

PRECONF (end)
established, DID origination is allowed, emergency conference is allowed,

audio tone detector is not required, immediate start is not required and the
standard notification is a tone, PCNOR.
Conferee 1 has a primary address of 514-595-1234, an alternate address of
514-595-9887 and a timeout of 30 s.
Conferee 2 has a primary address of 519-421-6212 and a timeout of 45 s.
Conferee 3 has a primary address of 727-4691 and is the DN of a
secondary conference located on another switch.
No options are defined
MAP display example for table PRECONF
PCNFKEY CONFADDR
PCNFVAR
OPTIONS
_____________________________________________________________________
3 0 2267432
D IBN BNRGRP 126 Y Y Y Y N N PCNOR
$
3 1 5145951234
A 5145959887
$
3 2 5194216212
P 45
$
3 3 7274691
C
$
Table history
BCS36
Field OPTIONS, PCNFOPTN, and NARNAME were added.
PREFHUNT
Table name
Preferential Hunt List Member
The Preferential Hunt (PRH) feature is an optional feature that can be assigned
to one or more of the directory number hunt (DNH) groups.
With this feature, each DNH group can have up to 64 PRH lists. Each PRH
list can contain up to 19 members. Each of the 19 members must be a member
of the DNH group in which the PRH list is based.
Each member of a DNH group can be the pilot of only one PRH list. Each
member can also be a member of any other PRH list that is already defined.
Member number 0 (zero) must always be the pilot number of the PRH list and
must be assigned before other members in the list are assigned.
Options LOD, LOR, BNN, OFR, OFS, SHU, RMB, and CIR are invalid for
PRH lists; however, they can co-exist with PRH on a DNH group.
For calls made directly to a busy directory number (DN) of a PRH list, PRH
hunts over the members of the PRH list before returning to search the DNH
group.
Preferential hunting only occurs if the pilot DN of the PRH list is busy.
Care must be taken when setting up the PRH lists. Having many PRH lists end
on the pilot of the DNH group could lead to the first few members of the DNH
group being extremely busy. Conversely, having many members end at the last
member of the DNH group can result in a large number of overflows, even
though there are free members in the DNH group.
Feature ISDN PKT single DN (AF6872) can be assigned PRH groups on a

hunt group basis. Table PREFHUNT will allow voice information (VI) circuit
mode data (CMD), and shared packet mode (PMD) hunt groups on ISDN
integrated terminals (IT) using the same DN.
297-8021-351 Standard 05.02 May 2001

PREFHUNT (continued)
The following table control rules for shared ISDN terminals apply to table
PREFHUNT:
Add preferences on members of hunt groups provisioned for circuit
switched (CS) and packet switched (PS) call types with DN shared.
Change preferences on members of hunt groups provisioned for CS and PS
call types with DN shared.
Delete preferences on members of hunt groups provisioned for CS and PS
call types with DN shared.
Note: For more information about DN CALLTYPE sharing, see

subfield OPTION in table HUNTGRP and feature AF6782 in the
Feature Description Manual.

The following tables must be datafilled before table PREFHUNT.
HUNTMEM
HUNTGRP
Table size
0 to 32 767 tuples
Datafill
The following table lists datafill for table PREFHUNT.
DNHGRP 0 to 32767 Directory number hunt group number

Enter the group number of the DNH group to
which the member belongs.
PRHLIST 0 to 63 Preferential hunt list number

Enter the PRH list number to which the hunt
member is assigned in the DNH group.
PRHMEM 0 to 18 Preferential hunt list member number

Enter the PRH list member number that is
assigned to the hunt member in the DNH
group.
PREFHUNT (continued)
INSERT Y or N Insert
Enter Y (yes) if an addition to an existing PRH
list is made. The new member is inserted in
the PRH list at a specific location other than
the last. Enter N (no) for initial input, or if
adding a new member to the end of an
existing PRH list.
DN 10-digit DN Directory number

with NPA
The system expects a 10-digit entry which is
(maximum is
the DN assigned to the PRH list member. This
15 digits)
must match the DN of the host DNH group
member. If 7 digits are entered, NPA of the
host DNH group pilot is used with this DN. .
Note: Due to feature 59006893, Provisioning

for Enhanced Multi-NPA, this DN can contain
an NPA different from that of the pilot DN
when this feature is enabled.
Table history
NA012
Field DN is updated for feature 59006893, Provisioning for Enhanced
Multi-NPA.
NA008
The following entries are added or changed for NA008:
Added warning information for table control data corruption errors feature
(AF6777).
Added warning information for call type mismatch in support of feature
(AF6777).
Added supplementary information; modification of preferential hunt list
member attributes of CS ISDN terminals with DN sharing feature
(AF6782).
Datafill example
The following example shows sample datafill for table PREFHUNT.
297-8021-351 Standard 05.02 May 2001

PREFHUNT (end)
In this example
All members are assigned to DNH group number 5.
DN 7252860 is the pilot DN for PRH list 1, member number 2 of PRH list
0 (zero) and 2, and member number 5 of PRH list 4.
DN 7252863 is the pilot DN for PRH list 4.
DN 7252858 is member number 3 of PRH list 2.
MAP display example for table PREFHUNT
DNHGRP PRHLIST PRHMEM INSERT DN

________________________________________________________
5 1 0 N 7252860
5 0 2 N 7252860
5 2 2 N 7252860
5 2 3 N 7252858
5 4 0 N 7252863
5 4 5 N 7252860
If a system error occurs from data corruption, while processing table control
commands with DN call type (DNCT), the following error message will be
issued:
ERROR: FAILED TO READ FROM DNCT PROTECTED DATA.
The recommended action is to reissue the command.
If the CALLTYPE of a member being added or changed in table PREFHUNT

is different from the CALLTYPE of the hunt group, the following error
message will be issued:
ERROR: CALLTYPE MISMATCH BETWEEN HUNT GROUP AND MEMBER.
PREPLANS
Table name
Network Management Preplan Table
Table PREPLANS lists the following information for each network
management preplan:
the short common language location identifier (CLLI) to which the preplan
applies
the type of control that applies to the preplan
The following control types can be applied to the preplan:

directional reservation equipment (DRE)
protective reservation equipment (PRE)
cancel to (CANT)
cancel from (CANF)
skip (SKIP)
incoming trunk busy (ITB)
selective trunk reservation (STR)
flexible reroute (FRR)
international trunk override (ITO)
bearer services skip (BSSKIP)
time alignment speech interpolation (TASI)

Tables POECNM and CLLIMTCE must be datafilled before table
PREPLANS. Table POECNM provides a list of all other licensed operators
(OLO) that are used.
Table size
0 to 8192 tuples
The length of table PREPLANS depends on the value of field NCTRLS in

table NWMPPLN. Each tuple in table PREPLANS requires three words of
protected data store.
297-8021-351 Standard 05.02 May 2001

PREPLANS (continued)
Datafill
The following table lists datafill for table PREPLANS.
Subfield or
PPLN see subfields Preplan

This field consists of subfields PPLNNO and
PPLNCTRL.
PPLNNO 0 to 255 Preplan number

Enter the preplan number.
PPLNCTRL 0 to 31 Preplan control number

Enter the preplan control number.
SCLLI alphanumeric Short common language location identifier

(6 character
(CLLI) name of the trunk group to which the
vector)
preplan control applies. The short CLLI
(SCLLI) is defined in table CLLIMTCE.
Subfield or
CTRL BSSKIP, Control data

CANF, CANT,
This field specifies the trunk group control
DRE, FRR,
parameters.
ITB, ITO,
PRE, SKIP, For the bearer services skip control type,
STR, or TASI enter BKSKIP. No refinements need datafill.
For the cancel from control type, enter CANF
and datafill refinements DRPCT and ARPCT
For the cancel to control type, enter CANT
and datafill refinements DRPCT, ARPCT, and
ANN on the following pages.
For the directional reservation equipment
control type, enter DRE and datafill
refinement LEVEL on the following
pages.DRE is a control (applied to two-way
trunk groups) that gives priority to completing
traffic by reserving a number of idle trunks in
a group for this traffic. Originating traffic is
skip-routed (that is, it overflows to the new
group). Once DRE is enabled and the level
setting is reached, all the traffic (direct and
alternate) offered to the two-way trunk group
is skip-routed. The skip-routing continues
until the number of idle trunks in the group
increases past the trigger (level) threshold.
For the flexible reroute control type, enter
FRR and datafill refinements DRLEV,
ARLEV, CTRLOPT, HTROPT, EAOPT,
CICROPT, and VIARTE on the following
pages.
For the incoming trunk busy control type,
enter ITB and datafill refinement LEVEL on
the following pages.
297-8021-351 Standard 05.02 May 2001

Subfield or
CTRL(continue For the international trunk override, enter ITO.

d) No refinements require datafill.
For the protective reservation equipment
control type, enter PRE and datafill
refinement LEVEL on the following
pages.PRE is a control similar to DRE but
PRE acts only on alternate-routed traffic
offered to a two-way trunk group.
Direct-routed traffic is allowed full access.
Once PRE is enabled and the level setting is
reached, all the alternate-routed traffic offered
to the two-way trunk group is skip-routed.
For the skip control type, enter SKIP and
datafill refinements DRPCT, ARPCT, and
ANN on the following pages.
For the selective reservation control type,
enter STR and datafill refinements LEV1,
LEV2, and LEVEL on the following pages.
For the time alignment speech interpolation
control type, enter TASI. No refinements
require datafill.
CTRL = DRE, ITB, or PRE

If the entry for field CTRL is DRE, ITB, or PRE, datafill refinement LEVEL
as described below.
Subfield or
LEVEL 0 to 100 Level

(DRE, ITB) 0
If a preplan control is assigned to directional
to 63 (PRE)
reservation equipment (DRE), enter the
number of trunks reserved in a two-way final
route in preference to the higher ranking
office (0 to 100).
If a preplan control is assigned to protective
reservation equipment (PRE), enter the
number of trunks reserved in a two-way trunk
for direct routes and incoming trunks (0 to 63).
Enter the percentage of incoming trunks
busied (ITB) in the group (0 to 100). The
trunks must have feature NTX395 (Remote
Make Busy).
CTRL = CANF or CANT

If the entry for field CTRL is CANT, datafill refinements DRPCT, ARPCT, and
ANN as described below.
Subfield or
DRPCT 0 to 100 Direct-routed percentage selector

Enter a number to determine the percentage
of CANF direct-routed (DR) traffic or
controlled DR traffic.
ARPCT 0 to 100 Alternate-routed percentage selector

of CANF alternate-routed (AR) traffic or
controlled AR traffic.
297-8021-351 Standard 05.02 May 2001

Subfield or
Note: Fields DRPCT and ARPCT cannot both be set to 0 (zero). One field must contain a value other
than 0 (zero) to make valid entries possible.
ANN NCA, EA1, or Announcement

EA2
Enter the announcement to which blocked
calls are routed: NCA (no-circuit
announcement), EA1 (emergency
announcement 1), or EA2 (emergency
announcement 2).
CTRL = FRR
If the entry for field CTRL is FRR, datafill refinements DRLEV, ARLEV,
CTRLOPT, HTROPT, EAOPT, CICROPT, and VIARTE as described below.
Subfield or
DRLEV 0 to 100 Direct-routed traffic percentage

of direct-routed (DR) traffic affected by the
FRR control.
ARLEV 0 to 100 Alternate-routed traffic percentage

of alternate-routed (AR) traffic affected by the
FRR control.
CTRLOPT IRR or RRR Control option

Enter the control option used with the FRR
control. To specify an immediate reroute
control option, enter IRR. To specify a regular
reroute control option, enter RRR.
There is no default.
Subfield or
HTROPT Y or N Hard-to-reach option

Enter Y (yes) to specify that only calls
identified as hard-to-reach are affected by the
FRR control. Enter N (no) to specify that all
calls, regardless of hard-to-reach status, are
affected by the FRR control.
EAOPT EA, NEA, or Equal access option

ALL
Enter the type of call affected by the FRR
control.
Equal access (EA) specifies that only EA calls
are affected by the FRR control.
NEA specifies that only non-equal access
calls are affected by the FRR control.
ALL specifies that both EA and NEA calls are
affected by FRR.
CICROPT Y or N Cancel in-chain return option

Enter Y to specify that calls rerouted by the
FRR control must be sent to treatment once
the out-of-chain route list for those calls is
exhausted. Enter N to specify that calls
rerouted by the FRR control must not be sent
to treatment once the out-of-chain route list
for those calls is exhausted. Instead, these
calls are returned to the next route in the
in-chain route list.
VIARTE alphanumeric Out-of-chain common language location

(1 to 16 identifier
characters)
Enter the first out-of-chain route to which calls
affected by the FRR control are directed.
Enter the full or short CLLI name of the trunk
group chosen as the first out-of-chain route.
297-8021-351 Standard 05.02 May 2001

CTRL = SKIP
If the entry for field CTRL is SKIP, datafill refinements DRPCT and ARPCT
as described below.
Subfield or
DRPCT 0 to 100 Direct-routed percentage selector

of controlled by SKIP direct-routed (DR)
traffic.
ARPCT 0 to 100 Alternate-routed percentage selector

of controlled by SKIP alternate-routed (AR)
traffic.
Note: Fields DRPCT and ARPCT cannot both be set to 0 (zero). One field must contain a value other
than 0 (zero) to make valid entries possible.
CTRL = STR
If the entry for field CTRL is STR, datafill refinements LEV1, LEV2, and
LEVEL as described below.
Subfield or
LEV1 0 to 63 Number of trunks

If level 1 is activated, the percentage
specified for field LEVEL of hard-to-reach
traffic is skip-routed. Enter the number of idle
trunks that activate the level 1 control.
Subfield or
LEV2 0 to 63 Number of trunks

If level 2 is activated, 100% of alternate, 75%
of hard-to-reach, and the percentage
specified for field LEVEL of direct-routed
traffic is blocked. Enter the number of idle
trunks that activate the level 2 control.
LEVEL 0 to 100 Percentage of traffic

Enter the percentage of traffic to skip route in
level 1 and to block in level 2.
Datafill example
The following example shows sample datafill for table PREPLANS.
In the first tuple, subfield PPLNNO specifies a preplan number of 0 (zero).

Subfield PPLNCTRL specifies a preplan control number of 0 (zero). Field
SCLLI specifies HULO as the short CLLI name of the trunk group affected by
the control. The control data (CTRLDATA) subfield SELR specifies SKIP as
the control applied to the trunk group HULO. The direct-routed percentage
subfield (DRPCT) specifies that none of the direct-routed traffic on trunk
group HULO is affected by the control. The alternate-routed percentage
subfield (ARPCT) specifies that 75% of the alternate-routed traffic on trunk
group HULO is affected by the control.
In the last tuple, subfield PPLNNO specifies a preplan number of 3. Subfield

PPLNCTRL specifies a preplan control number of 0. Field SCLLI specifies
OTW3 as the short CLLI name of the trunk group affected by the control. The
control data (CTRLDATA) subfield SELR specifies FRR as the control applied
to the trunk group OTW3. Subfields DRLEV and ARLEV respectively
specify that 20% of the direct-routed traffic and 75% of the alternate-routed
traffic on trunk group OTW3 are affected by the control.
The control option used is IRR (immediate reroute), as specified in subfield

CTRLOPT. Only calls identified as hard-to-reach are affected by the control,
as specified in subfield HTROPT. Subfield EAOPT specifies that all equal
access (EA) and non-EA calls are affected by the control. Subfield CICROPT
specifies that calls rerouted by FRR control must be returned to the next
in-chain route list if they exhaust their assigned out-of-chain route lists. CLLI
297-8021-351 Standard 05.02 May 2001

PREPLANS (end)
STGOVFL in subfield VIARTE is the name of the trunk group designated as

the out-of-chain route for calls affected by the FRR control.
MAP display example for table PREPLANS
PPLN SCCLI CTRLDATA

________________________________________________________
0 0 HUL0 SKIP 0 75
3 0 OTW3 FRR 20 75 IRR Y ALL Y STGOVFL
Table history
BCS36
Refinement OLO was removed.
New or changed data schema tables 2-3
PRI1WAY
Table name
Primary Rate Interface (PRI) 1 Way.
New table PRI1WAY provides a mechanism allowing PRI trunks to behave as
outbound trunks. This table carries entries of peripherals like SPM, DTCI,
LTCs on which PRI trunks are required to act as terminators only. ISUP, PTS
and other trunks types are not impacted by entry in this table.
In CM, when PRI call origination messages are received for 1 way PRI trunks
provisioned on peripheral datafilled in the new table, will be rejected with the
cause value of Service or Option not available, unspecified.

Tables MNNODE and LTCPSINV need to be provisioned before datafill for
this table.

Hardware datafill tables MNNODE and LTCPSINV need to be provisioned
before datafill for this table.
Table size
Abbreviated table Minimum Maximum

name tuples tuples Information on memory
PRI1WAY 0 511 2 words per tuple
Field descriptions
The following table lists the fields of table PRI1WAY.
Subfield or
Node Type None Type of Node This entry has type of node e.g. DTCI, LTC,
(PMNAME) SPM.
Node ID None Node Number This has ext pm no.

2-4 New or changed data schema tables
PRI1WAY (end)
Datafill example
All PRI trunks on SPMO, DTCI1, and LTC2 are one way outbound trunks and
all originations on these trunks are rejected.
MAP display example for table control interface for provisioning of PRI1WAY
TABLE: PRI1WAY
SPM 0
DTCI 1
LTC 2
Table history
NA017
Feature A59033985 introduced this table for the enhancement of PRI trunks.
297-8021-351 Standard 06.02 July 2002

PRIPROF
Table name
Primary Rate Interface (PRI) Profile
Table PRIPROF contains the status of function switches that were configured
for a particular issue of a variant.

There is no requirement to datafill other tables prior to table PRIPROF.
Before a tuple in table PRIPROF can be deleted or changed, all references to

the profile name must be removed from table LTDEF. Profile names are stored
in field PROFNAME in both tables.
Table size
256 tuples
Table size for table PRIPROF is statically allocated in accordance with the
maximum number of profiles that can be held in the table, which is currently
256.
Datafill
The following table lists datafill for table PRIPROF.
Subfield or
PROFNAME alphanumeric Profile name

(1 to 8
Enter a character string to represent the
characters)
primary rate interface (PRI) profile name.
VARINFO see subfield Variant information

This field consists of subfield VARIANT and
refinement.
297-8021-351 Standard 05.02 May 2001

PRIPROF (continued)
Subfield or
VARIANT AUSTPRI, Protocol variant

ETSIPRI,
Enter the data for this field to define the PRI
EVN4PRI,
protocol with which the profile name must be
INSPRI,
associated, then datafill refinement ISSUE.
N449PRI,
NTNAPRI, Permitted entry values for this field are
NIPRI, dependent upon the PRI variant packages
QSIGPRI, that are loaded on the switch.
U449PRI, or
U459PRI
When the N449PRI variant is selected, enter

corresponding ISSUE subfield V1.
When the NTNAPRI variant is selected, five

function switches are available. These
switches enable a user to set up interworking
between the DMS switch and an SL-1 private
branch exchange (PBX).
You must select ETSIPRI if you wish to select

SWISS3, SPAIN1, or HOLLAND1 in the
ISSUE field to activate Swiss PRI, Spanish
PRI, or Dutch PRI.
When the NIPRI variant is selected, SWITCH

can be datafilled using the value for an
unknown type of number/numbering plan
identifier (UNTONNPI). When NIPRI is
selected, only the UNTONNPI function switch
is available.
PRIPROF (continued)
Subfield or
ISSUE 1990, Protocol issue

ETSI1993,
Enter the data for this field to define the
ISO1996,
specification issue with which the PRI variant
TS141490,
is associated. Default value is ISO1996.
V1, NI2V1,
NET3, X11, SWISS3, SPAIN1 and HOLLAND1 can only
EVN4V1, be selected if the entry in the VARIANT field
SWISS3, is ETSIPRI. Also, see table LTDEF.
SPAIN1,
HOLLAND1
SWITCH vector of up to Function switch name

64
This field is a vector of up to 64 function
alphanumeric
switch names.
names (1 to 8
characters) Valid entry values for this field are defined by
specific applications. These entry values are
dependent upon the variant and issue
combination.
Enter a function switch name for each
software function that must be associated
with the switch. Separate each entry by a
space and end the vector with $.
Software functions for switch names that are
not datafilled in this field are disabled.
When the NIPRI variant is selected in field
VARIANT, SWITCH can be datafilled using
the value for the unknown type of
number/numbering plan identifier
(UNTONNPI).
Datafill example
The following example shows sample datafill for table PRIPROF.
297-8021-351 Standard 05.02 May 2001

PRIPROF (continued)
MAP display example for table PRIPROF
PROFNAME VARINFO SWITCH

_____________________________________________________
NAPBX NTNAPRI VI (EXMPL1) (EXMPL2) $
ETSIPBX ETSIPRI 1990 (EXMPL3) (EXMPL4) (EXMPL6) $
AUSTPBX AUSTPRI TS14_1990 (EXMPL5) $
NI2UNKNWN NIPRI NI2V1 (UNTONNPI) $
Table history
NA015
Feature A59023416 added subfield N449PRI to option VARIANT.
MMP12
Added option ETSI1993 and deleted options ISO1990 and ISO1994 from
subfield ISSUE.
EUR010
Options SPAIN1 and HOLLAND1 added to subfield ISSUE for activities
AU3208 and AU3209 (Spanish PRI and Dutch PRI).
EUR009
Option SWISS3 added to field ISSUE for feature AU2826.
EUR008 and APC009

Adds value EVNPRI to subfield VARIANT, and values, EVN4V1, NET3, and
X11, to subfield ISSUE.
Option DIALTONE in table PRIPROF can not be provisioned in EUR008 or

APC009. Option DIALTONE is visible. If you attempt to provision option
DIALTONE, the following error message appears:
DIALTONE SWITCH NO LONGER SUPPORTED.USE NET_DIALTONE_ON IN

LTDATA INSTEAD.
Note: Option NET_DIALTONE_ON in table LTDATA and option

DIALTONE in table PRIPROF provide the same functionality.
EUR006
Adds new value, QSIGPRI, to subfield VARIANT and three new values,
ISO1996, ISO1994 and ISO1990, to subfield ISSUE.
XPM08
Add NI2V1 as an option for subfield ISSUE.
PRIPROF (end)
CCM07
Table PRIPROF was modified to include NIPRI as a valid entry in subfield
VARIANT.
BCS36
Table PRIPROF was introduced.
297-8021-351 Standard 05.02 May 2001

PRSUDATA
ATTENTION
This table applies to new or modified content for SN07(DMS) that
is valid through the current release.
PRSUDATA

The table is dynamically datafilled when a PRSU is successfully
validated via the Post Release Software Manager (PRSM).
Table size
The table may contain up to 32000 entries.
Datafill
Datafilling is done dynamically.
Fields and subfields for table PRSUDATA
Field Subfield or refinement
PRSUINDX PRSUDATA_KEY
PRSUID PRSU_CHAR_VECTOR
FLCLASS CLASSID
BCSNO UNSIGNEDINT
CATEGORY PRSU_CATEGORY
ACTINDEX UNSIGNEDINT
CLASS PRSU_CLASS_TYPES
CUSTAPP BOOL
AUTOAPP BOOL
AUTOINST BOOL
INSTREQD BOOL
DMS_100 Family NA100 Data Schema Reference Manual Volume 9 of 12 SN07 (DMS) and up
Fields and subfields for table PRSUDATA
Field Subfield or refinement

SPECIAL BOOL
SRC BOOL
MAN BOOL
CMD BOOL
HOLD BOOL
PROCESOR PRSM_PROCESSOR_TYPE
RESTART RESTART_REQUIRED_TYPE
STATAUD BOOL
STATALRM BOOL
FILEAUD BOOL
FILEALRM BOOL
PERM BOOL
ENTRVALD PRSU_ENTRY_CODE
FIRSTVAL PRSM_TIME_TUPLE
VALDATE PRSM_DATE_TUPLE
FIRSTAPP PRSM_TIME_TUPLE
APPDATE PRSM_DATE_TUPLE
FIRSTREM PRSM_TIME_TUPLE
REMDATE PRSM_DATE_TUPLE
FIRSTINS PRSM_TIME_TUPLE
INSDATE PRSM_DATE_TUPLE
Table history
SN07(DMS)
New table PRSUDATA created as part of activity Q01083765.

PRTN2CCD
Table name
Pretranslator To CC Translator Name Table
This table provides the mapping from the Pretranslator Name to the Country
Code (CT) Translator Name. This mapping is required to maintain the
customer group translations partitioning begun in MDC translations and to
pass this partitioning on to the international partitioned translations.

The following tables must be datafilled before table PRTN2CCD.
LINEATTR
CTHEAD
Table size
Table PRTN2CCD is a static table with 256 tuples. Tuples without datafill do
not display.
Datafill
The following table lists datafill for table PRTN2CCD.
Field descriptions
Subfield or
PRTN alphanumeric Pretranslator name

Lists the pretranslator name from table
LINEATTR.
TRANNAME alphanumeric CT translator name

Lists the translator name from table CTHEAD.
Datafill example
The following example shows sample datafill for table PRTN2CCD.
The example consists of a pretranslator name, CTID, which is mapped to the

CT translator name, CCTID. The pretranslator name is found in table
LINEATTR, field PRTNM. The CT translation name is found in table
CTHEAD, field XLANAME.
PRTN2CCD (end)
MAP display example for table PRTN2CCD
PRTN TRANNAME
________________________________________________________
CTID CCTID
297-8021-351 Standard 05.02 May 2001

PRTTONET
Table name
Partition Number to NETINFO Mapping Table
Table PRTTONET maps partition numbers to NETINFO information for
IVPM calls.

Table NETNAMES must be datafilled before table PRTTONET.
Table size
0 to 1000 tuples
A restart is not required in order to increase the table size.
Datafill
The following table lists datafill for table PRTTONET.
Field descriptions
Subfield or
PARTNO numeric (3 Partition number

digits)
Enter a partition number.
NETNAME alphanumeric Network name

(up to 32
Enter a character string corresponding to a
characters)
NETNAME that exists in table NETNAMES.
NETCGID numeric (0 to Network customer group id

4095)
Enter a number to identify the external
customer group.
NCOS numeric (0 to Network class of service

255)
Enter a number to specify the network class of
service.
Datafill example
The following example shows sample datafill for table PRTTONET.
PRTTONET (end)
This example shows the initial datafill for the following partition number to
NETINFO mapping requirements:
Partition digits 601 are associated with NETWK1 external customer group
50 and a class of service of 25.
MAP display example for table PRTTONET
PRTNO NETNAME NETCGID NCOS

________________________________________________________
601 NETWK1 50 25
602 NETWK2 100 60
603 NETWK3 100 70
297-8021-351 Standard 05.02 May 2001

PS
Table name
Program Store Assignment Table
The following assignment data for each program store (PS) shelf appears in
table PS:
floor, row on floor, frame position in row, and base mounting position for
each PS shelf
frame type and number on which the PS shelf mounts
highest numbered memory card
product engineering code (PEC) of PS shelf
The system allocates memory for planes 0 and 1 for eight PS shelves.
Table 1 contains PS PEC descriptions with the correct references from the
DMS-100 Provisioning Manual, 297-1001-450.
Program store PEC descriptions
PEC Description Reference
NT3X31AA Program store EMR4-01-000
NT3XA31AD 1 Megaword program store EMR4-03-000
NT3X32AA 1 Megaword program store EMR4-05-000
NT3X32BA 1 Megaword program store EMR4-07-000
NT3X41DA 8 Megaword program store Not available
NT3X41EA Central PROC and shelf assembly EMR4-10-000
NT3X4106 Central PROC and shelf assembly EMR4-10-000
NT9X99ZZ Dummy PEC Not available
NT7X31AA Special DMS-100 project Not available
NT7X3102 Special DMS-100 project Not available
PS (continued)

You do not need to enter data in other tables before you enter data in table PS.
Table size
2 to 8 tuples
The table contains 1 tuple for each defined PS memory shelf. Each defined PS
memory shelf is for each central control (CC) plane that can have a maximum
of four PS shelves.
Datafill
Datafill for table PS appears in the following table.
Subfield or
PSNM see subfields Program store number. This field contains

subfields PSSHNO and PLANE.
PSSHNO 0 to 7 Program store shelf number. Enter the

number assigned to the program store (PS)
shelf.
PLANE 0 to 1 Plane. Enter the plane of the PS shelf.
NOMEMCDS 0 to 15 Highest numbered memory card. Enter the

highest numbered memory card on the PS
shelf.
FRTYPE CCC Frame type. Ecabinet core module (MCCM)

MCCM or or memory extension frame (MEX) on which
MEX the PS shelf mounts.
FRNO 0 to 1 Frame number. Enter the frame number of

the CCC or MEX frame on which the PS shelf
mounts.
Entries out of this range are not correct.
SHPOS 18, 32, 51, or Shelf position. Enter the base mounting
65 position of the PS shelf on the CCC or MEX
frame.
Entries out of this range are not correct.
297-8021-351 Standard 05.02 May 2001

PS (continued)
Subfield or
FLOOR 0 to 99 Floor. Enter the floor or remote location

number that indicates the location of the
frame of the PS shelf.
ROW A to Z, Row. Enter the row on the floor that indicates

AA to ZZ, the location of the frame of the PS shelf.
except I, II, O,
and OO
FRPOS 0 to 99 Frame position. Enter the bay position in the

row that indicates the location of the frame of
the PS shelf.
EQPEC 3X31AA Equipment product engineering code. Enter

3X31AD the product engineering code (PEC) of the PS
3X32AA shelf. Do not include the NT prefix.
3X32BA
7X31AA
9X99ZZ
3X41DA
3X41EA
3X4106
or 7X3102
Datafill example
Sample datafill for table PS appears in the following example.
The assignments associated with PS shelf 0, planes 0 and 1 appear in the

following example.
The system provides one record for each plane.
PS (end)
MAP example for table PS
PSNM NOMEMCDS FRTYPE FRNO SHPOS FLOOR ROW FRPOS EQPEC

________________________________________________________
00 0 15 CCC 0 32 05 B 03 3X31AA
00 1 15 CCC 0 32 05 B 04 3X31AA
297-8021-351 Standard 05.02 May 2001

PSCNUM
Table name
Private Speed Call Number Table
Table PSCNUM contains all of the private speed calling (PSC) numbers used
by feature AD2186 (Meridian SuperNode (MSN) Private Speed Calling and
hotline Dialing). Table PSCNUM has a double index, the PSC index that
associates the PSC number with an authorization code (authcode), and the PSC
number that the caller dials. Destination digits are datafilled for each entry.
These digits are the number to which the call is routed when the PSC number
is dialed for the authcode corresponding to the PSC index.

There is no requirement to datafill other tables prior to table PSCNUM.
Table size
0 to 5000 tuples
Datafill
The following table lists datafill for table PSCNUM.
Subfield or
PSCKEY see subfields Private speed calling key

This field consists of subfields PSCIDX and
PSCNUM.
PSCIDX 0 to 4999 Private speed calling index

Enter the number that associates a private
speed calling (PSC) number with a particular
authorization code (authcode).
PSCNUM (end)
Subfield or
PSCNUM 2 digits nn Private speed calling number

(where n is 2
Enter the PSC number in the form nn, where
to 9
nn is a number in the range 2 to 9 that the
[pro-grammed
caller dials. Any combination of numbers
]) or 2 to 99
using 0 (zero) or 1 is invalid. For example, 24
(reserved)
and 35 are valid PSC numbers, but 21 and 30
are invalid.
DESTDIGS 0 to 9 (1 to 18 Destination digits

digits)
Enter the number to which the speed call
terminates.
Datafill example
The following example shows sample datafill for table PSCNUM.
MAP display example for table PSCNUM
PSCKEY DESTDIGS
________________________________________________________
5 22 24231
69 34 8067953323
3378 54 011555364785674
297-8021-351 Standard 05.02 May 2001

PSNAILUP
Table name
P-Side Nail-up Table
Table PSNAILUP contains an inventory of P-side to P-side, nailed-up
cross-connections whose endpoints are either lines on a remote concentrator
SLC-96 (RCS) or channels on a DS-1 line connecting to equipment other than
an RCS or DMS-100 remote peripheral module (PM).

Table PSNAILUP must be datafilled before table <short name of table>.
The following tables must be datafilled before table PSNAILUP.

table LTCPSINV for the DS-1 channel endpoint subtending a subscriber
carrier module-100S (SMS)
table LTCRPINV for the DS-1 channel endpoint subtending a remote SMS
(SMSR)
table LNINV for the RCS line endpoint
Table size
0 to 4600 tuples
Table PSNAILUP requires 14 bytes of memory in protected data store for each
nailed-up cross-connection.
PSNAILUP (continued)
Datafill
The following table lists datafill for table PSNAILUP.
Subfield or
ENDPT1 see subfield Endpoint 1

This field consists of subfield PSSEL. It
consists of the first endpoint of the nailed-up
cross-connection. This endpoint can either
be an remote concentrator SLC-96 (RCS) line
or a DS-1 channel.
PSSEL SMS, SMSR, P-side selector

RCS, or NIL
Enter SMS if the first endpoint is a DS-1
channel subtending a subscriber carrier
module-100S (SMS) and datafill refinements
PMNO, PORT, and CHNL.
Enter SMSR if the first endpoint is a DS-1
channel subtending a remote SMS (SMSR)
and datafill refinements PMNO, PORT, and
CHNL.
Enter RCS if the first endpoint is an RCS line
and datafill refinement LEN.
PMNO 0 to 255 Peripheral module number

or
If the entry in subfield PSSEL is SMS or
0 to 1023
SMSR, datafill this refinement. Enter the
external number of the SMS or SMSR.
If the switch type is an NT40, the range is 0 to
255.
If the switch type is a SuperNode, the range is
0 to 1023.
PORT 0 to 19 SMS P-side port

P-side port number of the SMS or SMSR.
297-8021-351 Standard 05.02 May 2001

Subfield or
CHNL 1 to 24 P-side circuit time slot

DS-1 channel (time slot) of the SMS or
SMSR.
Go to field ENDPT2.
LEN see subfields Line equipment number

This field defines the physical location of the
equipment that is connected to a specific
telephone line.
Because field LEN is common to more than
60 tables, it is documented in a single section
to avoid unnecessary duplication. Refer to
section Common entry field LEN" for a
complete description of field LEN and
associated subfields.
Field LEN consists of subfields SITE,
FRAME, UNIT, DRAWER or LSG, SHELF,
SLOT, and CIRCUIT.
When datafill for field LEN is complete, go to
field ENDPT2.
ENDPT2 see subfield Endpoint 2

This field consists of subfield PSSEL. It
consists of the second endpoint of the
nailed-up cross-connection. This endpoint
can be either an RCS line or a DS-1 channel.
PSSEL SMS, SMSR, P-side selector

RCS, or NIL
Enter SMS if the first endpoint is a DS-1
channel subtending an SMS and datafill
refinements PMNO, PORT, and CHNL.
Subfield or
PMNO 0 to 255 or 0 Peripheral module number

to 1023
external number of the SMS or SMSR.
If the switch type is an NT40, the range is 0 to
255.
If the switch type is a SuperNode, the range is
0 to 1023.
PORT 0 to 19 Sms p-side port

P-side port number of the SMS or SMSR.
CHNL 1 to 24 P-side circuit time slot

DS-1 channel (time slot) of the SMS or
SMSR.
Go to field STATUS.

telephone line.
SLOT, and CIRCUIT.
When datafill for field LEN is complete, go to
field STATUS.
297-8021-351 Standard 05.02 May 2001

Subfield or
STATUS A or P or I Status
or NIL
Enter the status of the connection. Enter A
(active) if the connection is datafilled and set
up. Enter P (pending) if the connection is
datafilled, but the system has not set up the
connection in the PM.
Inactive (I) is a possible status and indicates
that the connection is datafilled, but the DS-1
link is not in service. The switch operator
cannot enter I. The system sets the status to
inactive if it is unable to set up a connection
after the connection was datafilled. The
endpoints remain datafilled in table
PSNAILUP, and the connection is made
active by the system when both endpoints
become in-service.
NIL indicates that there is no physical
hardware connection and that the nonexistent
connection is not datafilled. The system
initializes the STATUS field to NIL.
ABINSERT Y or N A- and b-bits insertion

Enter Y (yes) if A- and B-bits are inserted into
the information stream. Otherwise, enter N
(no).
Digital Dataphone Services (DDS) use DDS
protocol bits in the same position as A and B
signaling bits, so A- and B-bits are not
inserted into the information stream for DDS.
Voice connections normally use A- and
B-bits.
Datafill example
The following example shows sample datafill for table PSNAILUP.
The example shows the two endpoints, the STATUS field of the nailed-up
cross-connection, and whether A and B bits are inserted.
The first endpoint is an RCS line. It has a PSSEL of RCS and a LEN of REM1
00 00 01 03. The second endpoint is a DS-1 channel. It has a PSSEL of SMS.
The SMS is number 0 (zero) and its number 2 P-side port connects to the DS-1
line carrying the DS-1 channel. The DS-1 channel is number 1.
Field STATUS shows the status of the connection. In the example, the status
is active. A- and B-bits are inserted.
MAP display example for table PSNAILUP
ENDPT1 ENDPT2 STATUS ABINSERT

________________________________________________________
RCS REM1 00 0 01 03 SMS 0 2 1 A Y
Table history
CSP04
The following changes take effect in CSP04.
Reference to cold restart removed.
Table size changed to 4600.
This section provides information on error messages that can occur when
datafilling table PSNAILUP.
Datafill conditions and error messages

To enter data on lines and DS-1 channels in table PSNAILUP, the following
criteria must be satisfied:
Both endpoints must be on the same SMS or the same SMSR. If this condition
is not met, one of the following error messages is displayed at the MAP
(maintenance and administration position) terminal:
ENDPOINTS NOT CONFIGURED ON THE SAME SMS
ENDPOINTS NOT CONFIGURED ON THE SAME SMSR
The SMS must be datafilled in table LTCINV. If this condition is not met, one
of the following error messages is displayed at the MAP terminal:
297-8021-351 Standard 05.02 May 2001

SMS NOT DATAFILLED IN LTCINV (for lines)
DS1 NOT PROPERLY CONDIGURED (for DS-1 channels)
Neither endpoint can be part of an existing nailed-up cross-connection. If this

condition is not met, the following error message is displayed at the MAP
terminal:
ENDPOINT PART OF AN EXISTING NAILED-UP CONNECTION
Line endpoints must be datafilled in table LNINV. If this condition is not met,
the following error message is displayed at the MAP terminal:
LINE NOT EQUIPPED
Line endpoints must have card code NAILUP in table LNINV. If this condition
is not met, the following error message is displayed at the MAP terminal:
LINE NOT A SPECIAL SERVICES CIRCUIT
DS-1 channels cannot be on DS-1 lines that are datafilled in table LTCPSINV
for an SMS or table LTCRPINV for an SMSR. If this condition is not met, the
following message is displayed at the MAP terminal:
DS0 NOT ON AN EQUIPPED DS1
DS-1 lines must be properly configured in table LTCPSINV for an SMS or

table LTCRPINV for an SMSR. Otherwise, the following message is displayed
at the MAP terminal:
DS1 NOT PROPERLY CONFIGURED
DS-1 channels cannot be on DS-1 lines that terminate on an RCS. If this

condition is not met, the following message is displayed at the MAP terminal:
DS0 TERMINATES ON A REMOTE PERIPHERAL
The status of the nailed-up cross-connection must be specified as A (active) or

P (pending) only. Specifying the cross-connection status other than A or P
results in the following error message being displayed at the MAP terminal:
MUST SPECIFY ACTIVE OR PENDING STATUS ONLY
The table editor CHANGE command is not allowed when a change is required
to an endpoint in table PSNAILUP. To change an endpoint, the tuple
PSNAILUP (end)
containing the endpoint must be deleted and a new one added. The CHANGE
command can be used only on field STATUS of nailed-up cross-connections.
Attempting to change an endpoint using the CHANGE command results in the
following error message:
CHANGE COMMAND NOT ALLOWED ON ENDPOINTS
If operating company personnel try to change field ABINSERT of table

RCSINV while the status of the nailed-up cross-connection is active or
inactive, the following message appears at the MAP terminal:
CANNOT CHANGE ABINSERT FIELD WHEN STATUS IS ACTIVE OR

INACTIVE
If any company used in a P-side to P-side, nailed-up cross-connection is out of

service (this includes the SMS, SMSR, RCS, and DS-1 link) when the
connection is datafilled is table PSNAILUP, the status is set to inactive, with
the following message displayed at the MAP terminal:
CONNECTION INACTIVE -- ENDPOINTS NOT IN SERVICE
The connection becomes active when the equipment is put into service.
If any DS-1 channels are part of a nailed-up cross-connection, no RSC can be

attached to the DS-1 link holding those channels. No lines with special
services card code NAILUP can be datafilled in table LENLINES.
297-8021-351 Standard 05.02 May 2001

PSTNTRK
Table name
Public Switched Telephone Network Trunk Table
Table PSTNTRK functions as a look-up table to determine if the marked tables
connect to the public switched telephone network (PSTN). The key field is
GRPKEY. Field GRPKEY contains the common language location identifier
(CLLI) from table TRKGRP.
The default setting for field PSTN is N. The treatment of any trunk that does
not have data entry is as PSTN. This process prevents the use of any new trunk
to bypass PSTN restrictions.

Enter data in tables CLLI and TRKGRP before you enter data in table
PSTNTRK.
Table size
1 to 8191 tuples
Datafill
Datafill for table PSTNTRK appears in the following table.
Field descriptions
Subfield or
GRPKEY see subfield Group key. This field contains subfield CLLI.

(1 to 16 the common language location identifier
characters) (CLLI) of the trunk group.
PSTN Y or N Public switched telephone network. Enter Y

(yes) if the trunk group is PSTN. Enter N (no)
if the trunk group is not PSTN. The default
value for this field is N.
Datafill example
Sample datafill for table PSTNTRK appears in the following example.
PSTNTRK (end)
MAP example for table PSTNTRK
GRPKEY PSTN
________________________________________________________
MELPVN N
Table history
BCS35
Table PSTNTRK was introduced in BCS35.
297-8021-351 Standard 05.02 May 2001

PTIDTAB
Table name
Port Identifier Table
Table PTIDTAB is a read-only table. This table preserves the integrated link
maintenance (ILM) ports and ILM access identifiers over software
applications.
An update of this table can occur through the datafill of a device that requires
ILM supported resources. An update of this table can occur as part of a restore
operation on the N + 1 software application as part of a software application.
For this reason, table PTIDTAB is a write-restricted table with a SYSPROT
table protection level.
Note: Table PTIDTAB is for NT use only. This table is not for operating
company use.

You do not have to enter data in other tables before you enter data in table
PTIDTAB.
Table PTIDTAB must appear early in the data entry order. This table must
follow table AKEYTAB immediately, to allow any future cross-checking
between these tables.
Restore table PTIDTAB before you restore inventory tables of devices that
require ILM resources. The use of a restore operation allows data entries in
this table. This table is write-restricted for direct datafill.
Table size
0 to 2048 tuples
The number of tuples added dynamically determines table size.
PTIDTAB (continued)
Datafill
Datafill for table PTIDTAB appears in the following table.
Field descriptions
Subfield or
PTID see subfields Port identifier. This field is a different identifier

that ILM uses to identify a port. This field
contains subfields EPT_KEY and OFFSET.
EPT_KEY 0 to 32767 Port endpoint key. This subfield is a different

identifier that can identify the access key on
which the port resides.
OFFSET 0 to 32767 Port offset. This subfield is a different

identifier that identifies the port on the access
key. If an access key has several ports, use
of the port offset differentiates between the
ports.
ACID see subfields Access identifier. This field is the access

identifier that locates the port. This field
contains subfields KEY, INDEX, and
CHANNEL.
KEY 0 to 32767 Access key. This subfield is the access key

part of the access identifier.
INDEX 0 to 32767 Access index. This subfield is the access

index part of the access identifier.
CHANNEL 0 to 32767 Access channel. This subfield is the access

channel part of the access identifier.
Datafill example
Sample datafill for table PTIDTAB appears in the following example.
297-8021-351 Standard 05.02 May 2001

PTIDTAB (end)
MAP example for table PTIDTAB
PTID ACID

0 0 0 0 0
1 0 1 0 0
1 1 1 1 0
Table history
BCS35
Table PTIDTAB was introduced in BCS35.
PTP
Table name
TOPS Point-to-Point Rating Table
Table PTP lists the schedule name and rate step that apply for each
combination of point-to-point originating rate center and terminating rate
center.
For related information, refer to table ORIGRC.

Table SCHED must be datafilled before table PTP.
Table PTP has direct interaction with office parameter

TOPS_MAX_ORIG_RATE_CENTER in table OFCENG.
Datafill
The following table lists datafill for table PTP.
Subfield or
ORCTRC see subfields Point to point originatingterminating rate

center key. This field consists of subfields
ORC and TRC.
ORC 1 to 255 Point to point originating rate center. Enter

the point-to-point originating rate center.
The entry in this field cannot exceed the entry
in office parameter
OFCENG.
The DMS switch shows the range as 0-255,
however, value 0 is a NIL value and not
allowed by table control.
297-8021-351 Standard 05.02 May 2001

PTP (end)
Subfield or
TRC 1 to 255 Point to point terminating rate center. Enter

the point-to-point terminating rate center.
The entry in this field cannot exceed the entry
in office parameter
OFCENG.
The DMS switch shows the range as 0-255,
however, value 0 is a NIL value and not
allowed by table control.
SCHNAME alphanumeric Rate schedule name. Enter the rate schedule

(up to 17 name.
characters)
The entry in this field must be datafilled in
table SCHED as a domestic termination type
(field TERMTYPE set to DOM).
RATESTEP 0 to 999 Rate step. Enter the rate step that applies to
this combination of point-to-point
originating-terminating rate centers.
The entry in this field must be within the range
of rate steps associated with this rate
schedule name in table SCHED (fields LRS
and HRS).
Datafill example
The following example shows sample datafill for table PTP.
MAP display example for table PTP
ORCTRC SCHNAME RATESTEP

________________________________________________________
1 1 CARIBA 341
Table history
NA005
Changed range of fields TRC and ORC from 0-255 to 1-255. Value 0 is a NIL
value and not allow by table control per PRS UT56251.
PVCINFO
Table name
Permanent Virtual Circuit Information Table
Table PVCINFO functions as a look-up table to determine permanent virtual
circuit (PVC) service parameters for use with the DMS packet handler
(DMS-PH). A PVC is a permanent logical connection between two network
endpoints. One endpoint is designated as the master end and the other
endpoint is designated as the slave end. The key fields KEY and SLVEND
contain a directory number (DN) from table DNCHNL or a common language
location identifier (CLLI) from table X75INFO.
The following rules apply for datafilling an individual PVC:

There is only one set of data (for example, options SENDTC and RECVTC
[send and receive throughput class]) for the PVC, which is defined from
the master end. The slave end does not have independent data.
Slave end send parameters are equal to master end receive parameters.
Slave end receive parameters are equal to master end send parameters.

The following tables must be datafilled before table PVCINFO.
DNCHNL
X75INFO
Table size
0 to 8100 tuples
297-8021-351 Standard 05.02 May 2001

PVCINFO (continued)
Datafill
The following table lists datafill for table PVCINFO.
Subfield or
KEY see subfield Permanent virtual circuit key

This field identifies the master end and
consists of subfield ENDTYPE and its
refinements. This is the first of two key fields.
ENDTYPE X25 or X75 Endpoint type

Enter the network layer protocol for the
permanent virtual circuit (PVC) network
endpoint interface.
Enter X25 and datafill refinements DN, CHNL,
and LCN.
Enter X75 and datafill refinements CLLI,
MEMB, and LCN.
DN numeric (up to Directory number

18 digits)
If the entry in subfield ENDTYPE is X25,
datafill this refinement. Enter the directory
number datafilled in table DNCHNL for the
PVC data terminal equipment (DTE).
CHNL B or D Channel type

datafill this refinement. Enter the PVC
channel type used to identify the PVC on the
X.25 interface.
CLLI alphanumeric Common language location identifier

(1 to 16
characters)
datafill this refinement. Enter the common
language location identifier (CLLI) datafilled in
table X75INFO for the PVC trunk group.
MEMB 0 to 9999 Permanent virtual circuit index number

member number used to identify the PVC on
the X.75 interface.
PVCINFO (continued)
Subfield or
LCN 1 to 4095 Logical channel number

Enter the PVC logical channel number used
to identify the PVC on the X.25 or X.75
interface.
VIRT see subfield Virtual link

This field identifies the LEA link and consists
of subfields LINK_ID and LCN.
LINK_ID 0 to 511 Link identifier

This field identifies the link assigned to the
LEA that is monitoring the data call.

This field identifies the channel assigned to
the LEA that is monitoring the data call.
Note: The LCN is automatically assigned

when the USNBD command CCR ASSOC is
entered.
PVCOPTNS see subfield Permanent virtual circuit options

This field consists of subfield PVCPRM. Up to
eight parameters can be entered. If less than
eight parameters are required, end the list
with a $ (dollar sign).
SLVEND see subfield Slave end

This field identifies the slave end and consists
of subfield ENDTYPE and its refinements.
This is the second of two key fields.
ENDTYPE X25 or X75 Endpoint type

Enter the network layer protocol for the PVC
network endpoint interface.
DN numeric (up to Directory number

18 digits)
datafill this refinement. Enter the directory
number datafilled in table DNCHNL for the
PVC data terminal equipment (DTE).
297-8021-351 Standard 05.02 May 2001

PVCINFO (continued)
Subfield or
CHNL B or D Channel type

channel type used to identify the PVC on the
X.25 interface.

(1 to 16
characters)
datafill this refinement. Enter the common
language location identifier (CLLI) datafilled in
table X75INFO for the PVC trunk group.
MEMB 0 to 9999 Permanent virtual circuit index number

member number used to identify the PVC on
the X.75 interface.
PVCINFO (continued)
Subfield or
PVCOPTNS see subfield Permanent virtual circuit options

This field consists of subfield PVCPRM. Up to
eight parameters can be entered. If less than
eight parameters are required, end the list
with a $ (dollar sign).
PVCPRM BILLING Permanent virtual circuit parameters

LATA
Enter the PVC parameter.
RECVPS
RECVTS Enter BILLING for billing and datafill
RECVWS refinement SCHEME.
SENDPS
Enter LATA for local access and transport
SENDTC
area and datafill refinement LRANGE.
SENDWS
Enter RECVPS for receiving packet size and
datafill refinement PSIZE.
Enter RECVTS for receive throughput class
and datafill refinement TPUCLAS.
Enter RECVWS for receiving window size
and datafill refinement WSIZE.
Enter SENDPS for sending packet size and
datafill refinement PSIZE.
Enter SENDTC for send throughput class and
datafill refinement TPUCLAS.
Enter SENDWS and datafill refinement
WSIZE.
LRANGE INTER or Local access and transport area range

INTRA
If the entry in subfield PVCPRM is LATA,
datafill this refinement. Enter the local access
and transport area (LATA) status for the PVC.
The default value is INTRA.
PSIZE 128 or 256 Packet size

If the entry in subfield PVCPRM is RECVPS
or SENDPS, datafill this refinement. Enter
the packet size for master end packet data
receiving or sending.
The default is 128.
297-8021-351 Standard 05.02 May 2001

PVCINFO (continued)
Subfield or
TPUCLAS 75, 150, 300, Throughput class

600, 1200,
If the entry in subfield PVCPRM is RECVTS
2400, 4800,
or SENDTS, datafill this refinement. Enter the
9600
receiving or sending throughput class
or baudrate value for the master end.
19200, If one of the endpoints is identified as X25 D,
the valid entries are: 75, 150, 300, 600, 1200,
48000,
2400, 4800, and 9600.
56000,
If both endpoints are X25 B or X75, additional
64000
valid entries are: 19200, 48000, 56000, and
64000.
WSIZE 1 to 127 Window size

If the entry in subfield PVCPRM is RECVWS
or SENDWS, datafill this refinement. Enter
the window size for master end packet data
receiving or sending. If one of the endpoints
uses MODULO 8 packet level sequencing
(PLSQ), as defined in table X75INFO, valid
entries are 1 to 7. If both endpoints use
MODULO 128 PLSQ, valid entries are 1 to
127.
PVCINFO (continued)
PVCPRM = BILLING
If the entry in field PVCPRM is BILLING, datafill refinement SCHEME as
described below.
Subfield or
SCHEME see subfield Scheme

This field consists of subfield ENABLE.
ENABLE Y or N Billing enable

Enter Y (yes) to generate a billing record and
datafill refinement BILLOPT. Otherwise,
enter N (no) and datafill no refinements.
The default value is Y (yes).
BILLOPT CHRGDN Billing selection

NORMAL
For BCS36 and up, enter CHRGDN for
orNUI
chargeable DN billing and datafill refinements
ADDRFMT, CHRGDN, CHNLTYP, and LCN.
Note: Entry CHRGDN is only valid if the

master endpoint is X.25 and the slave
endpoint is X.75. For example, an inter-LATA
PVC call.
Enter NUI if billing is charged to the Network
User Identifier (NUI) and datafill refinement
DIGITS.
Note: NUI billing is supported only within a

LATA, that is, field LATA is datafilled as
INTRA.
Otherwise, enter NORMAL. No refinements
require datafill.
The default is NORMAL.
DIGITS numeric (up to Network user identifier digits

15 digits)
If the entry in subfield BILLSEL is NUI, datafill
this refinement. Enter the NUI number that
receives the billing record.
297-8021-351 Standard 05.02 May 2001

PVCINFO (continued)
Subfield or
ADDRFMT E164orX121 Address format

If the entry in subfield BILLSEL is CHRGDN,
datafill this refinement. Enter the address
format of the chargeable DN.
CHRGDN numeric (up to Chargeable directory number

14 digits)
datafill this refinement. Enter the chargeable
DN.
If the entry in field ADDRFMT is E164, the DN
is up to 14 digits.
If the entry in field ADDRFMT is X121, the DN
is 5 to 14 digits.
CHNLTYP B1, B2, or D Channel type

datafill this refinement. Enter the channel
type of the chargeable DN.

datafill this refinement. Enter the PVC logical
channel number used to identify the master
X.25 endpoint of the PVC call.
Datafill example
The following example shows sample datafill for table PVCINFO.
The example consists of master end type X25, DN 7652222, channel B, and
logical channel number 124. The slave end consists of end type X75, CLLI
ISDNX75, PVC index member 2418, and logical channel number 23. Option
SENDTC has a throughput class of 9600. Option BILLING is enabled twice:
in the first option, billing is charged to NUI 14; in the second option, billing is
charged to DN 2581975 using address format E164N on channel B1, and the
logical channel number is 666. Option LATA is INTRA.
PVCINFO (end)
MAP display example for table PVCINFO
KEY SLVEND
PVCOPTNS
________________________________________________________
X25 7652222 B 124 X75 ISDNX75 2418 345

(SENDTC 9600) (BILLING Y NUI 14)
(BILLING Y CHRGDN E164 2581975 B1 666) (LATA INTRA) $
Table history
NA014
Subfields VIRT, LINK_ID, and LCN added to KEY field for USNBD virtual
links..
BCS36
Entry CHRGDN was added to option BILLING.
BCS34
Table PVCINFO was introduced.
297-8021-351 Standard 05.02 May 2001

PVCTYPE
Table name
Permanent Virtual Circuit Type Table
Table PVCTYPE relates a type of permanent virtual circuit (PVC) layout to
each tuple defined in table TMSPVC. Table PVCTYPE is indexed by an
integer value in field VALUE. An identifier is datafilled in field SYMBOL
against each integer value. These identifiers are types used to define the
configuration type of a PVC layout in table TMSPVC.
This table contains six default entries. These entries are added as field VALUE
(0 (zero) to 5) and are TRANS, DMS, STD, CG14, TEG, and CGI_TEG,
respectively. The last five tuples are used to incorporate the numbering scheme
for table TMSPVC. Tuple 0 (zero), TRANS, is used for the Traffic Operator
Position System (TOPS) message switch (TMS) cutover methods.

There is no requirement to datafill other tables prior to table PVCTYPE.
Table TMSPVC must be datafilled after table PVCTYPE.
Table size
6 to 32 tuples
Datafill
The following table lists datafill for table PVCTYPE.
Subfield or
VALUE see subfield Value

This field consists of subfield UNINT.
PVCTYPE (continued)
Subfield or
UNINT 0 to 32 Unit integer

This is the key field of the table. Enter the
integer value.
Indicated values outside this range are not
valid.
SYMBOL alphanumeric Symbol

(1 to 32 Enter a text string to define a name used to
characters) define a permanent virtual circuit (PVC)
configuration type in table TMSPVC.
Datafill example
The following example shows sample datafill for table PVCTYPE.
The example consists of ten tuples. The first six are default entries.
MAP display example for table PVCTYPE
VALUE SYMBOL
________________________________________________________
0 TRANS
1 DMS
2 STD
3 CG14
4 TEG
5 CGI_TEG
6 MPX16
7 CGI16
8 MPX20
9 CGI20
Table history
BCS35
Table PVCTYPE was introduced.
PVCTYPE, and possible error messages when datafilling table PVCTYPE.
297-8021-351 Standard 05.02 May 2001

PVCTYPE (end)
Dump and restore

No dump and restore procedure is needed when the table is first applied.
Normal dump and restore procedures apply after the first application.
Error messages
No method exists for blocking deletions from this table. The following
message is displayed as a deterrent each time a tuple is deleted:
WARNING-STRING RANGE VALUES MAY BE REFERENCED IN OTHER TABLES.

DELETION OF STRING RANGE VALUES MAY LEAVE BLANK FIELDS IN THESE
OTHER TABLES. IF YOU THINK THIS MAY BE THE CASE, RE-ADD THE VALUE
AND ENSURE THE VALUE IS NOT USED IN ANOTHER TABLE BEFORE
DELETING THE VALUE AGAIN.
PVDNAGEN
Table name
Private Virtual Data Network Agent Table
Table PVDNAGEN stores all the FRS (frame relay service) agents in the
private virtual data network (PVDN) database. All the attributes for table FRS
Agents are programmed in table PVDNAGEN.

Table PVDNAGEN is the first table datafilled in the PVDN database. The
agent identifiers are used in the tables PVDNCHAN and PVDNCUST. Table
PVDNAGEN is not dependent on any other tables, although it must be
datafilled before any of the frame relay tables.
The FRS agents must be assigned to a private virtual data network (PVDN)
customer in table PVDNCUST.
Table size
0 to 2201 tuples
Table size can be increased by adding new agents in table PVDNAGEN. The
write routine for table PVDNAGEN allocates the space required.
Datafill
The following table lists datafill for table PVDNAGEN.
Subfield or
AGENTKEY see subfields FRS agent identifier

This field consists of subfield AGENT and is
the key to the table.
AGENT 0 to 2200 Agent

Enter the agent number.
297-8021-351 Standard 05.02 May 2001

PVDNAGEN (continued)
Subfield or
DN 0 to 9(vector Directory number

of up to 15
The directory number (DN) is the full
digits)
complement of digits required to designate a
subscriber's station within a numbering plan
area (NPA).
The NPA cannot be a number that is the same
as a toll-free service access code (SAC)
when the North American Numbering Plan is
used.
Note: For every tuple in PVDNAGEN, if field

DN contains any non-digit (non-numeric)
characters, or is greater than
999999999999999, the whole tuple fails to
restore.
NUMBPLAN(B INTL, NATL, Numbering plan

CS34- ) or X121INTL
The numbering plan adds support to
internetworking with other networks. This
field is based on the Q.931 origination
message type of number and numbering plan
identification fields.
The default value for this field is X121INTL.
AGTTYPE ACCESS or Agent type

T1TRUNK
Enter either ACCESS or T1TRUNK to
indicate the agent type.
DN see subfield Directory number

(BCS35- )
This field consists of subfield DNTYPE.
DNTYPE( NIL or VALID Directory number type

BCS35- )
Enter either NIL or VALID to indicate the DN
type. If the entry in this field is VALID, datafill
refinements DN and NUMBPLAN.
DN (BCS35- ) 0 to 9 Directory number

(vector of up
If the entry in field DNTYPE is VALID, datafill
to 15 digits)
this refinement. Enter the DN.
Subfield or
NUMBPLAN(B INTL, NATL, Numbering plan

CS35- ) or X121INTL
The numbering plan adds support to
internetworking with other networks. This
field is based on the Q.931 origination
message type of number and numbering plan
identification fields.
CUSTOMER alphanumeric Customer name

(BCS35- ) (vector of up
If the entry in field AGTTYPE is ACCESS,
to 20
datafill this refinement. Enter the customer
characters)
name.
CONTMARK + or $ Continuation mark

Enter + if additional information for this tuple
is contained in the next record. Otherwise,
enter $ to indicate the end of the tuple.
SPEED LS_56KBS Speed

LS_64KBS
Enter the speed at which the data is
LS_384KBS
transferred across the medium to which the
LS_1344KBS
agent is connected. LS_1344KBS is used for
or
T1 trunking.
LS_1536KBS
ABSIGN Y or N A/B BIT signaling

Enter Y (yes) or N (no).

CONDEV DDS_LATCH Connected circuit device

_LPBK or NIL
Enter the connected circuit device.
DDS_LATCH_LPBK is a digital data system
modem that supports latching loopback.
When NIL is entered the far-end device is not
specified.
297-8021-351 Standard 05.02 May 2001

Subfield or

TUNING see subfield T1 tuning

This field consists of subfield OPTION.
OPTION WINDOW Option

INVERSION
Enter WINDOW for the window size of the
KEEP
end-to-end protocol running over the link.
BUFFER
This option is used to recover frame loss and
ERAM
to ensure that no misordering of frames
CTRL_IDX
occurs. The default value is 16.
or
FLAG Enter INVERSION to invert the HDLC data
before transmission over the physical T1
circuit. The default value is N.
Enter KEEP to represent the number of
transmit buffers that the channel retains after
a period of heavy traffic. The default value is
5.
Enter BUFFER to represent the maximum
number of transmit buffers that channel can
allocate from the common buffer pool during
periods of heavy traffic. The default value is
75.
Enter FLAG to represent minimum number of
HDLC flags that are inserted between each
frame. The default value is 1.
OPTION = BUFFER, FLAG, KEEP, CTRL_IDX, or WINDOW

If the entry in field OPTION is BUFFER, FLAG, KEEP, CTRL_IDX, or
WINDOW, datafill refinements VALUE and CM as described below.
Subfield or
VALUE 0 to 255 Value

If the entry in subfield OPTION is BUFFER,
FLAG, KEEP, CTRL_IDX, or WINDOW,
datafill this refinement then go to field LMI on
page Section , "If the entry in field LMI is
ANSI, datafill refinement YES_NO as
described below." on page -283 to continue
datafill for table PVDNAGEN.
Enter a number to indicate the window size.
If the entry in field OPTION is BUFFER, the
range is 4 to 100.
If the entry in field OPTION is FLAG, the
range is 1 to 255.
If the entry in field OPTION is KEEP, the
range is 0 to 100.
If the entry in field OPTION is CTRL_IDX, the
range is 0 to 100.
If the entry in field OPTION is WINDOW, the
range is 1 to 128.
CM + or $ Continuation mark
297-8021-351 Standard 05.02 May 2001

OPTION = INVERSION or ERAM

If the entry in subfield OPTION is INVERSION or ERAM, datafill
refinements YES_NO and CM as described below.
Subfield or
YES_NO Y or N Yes or no
If the entry in subfield OPTION is INVERSION
or ERAM, datafill this refinement then go to
field LMI on page Section , "If the entry in field
LMI is ANSI, datafill refinement YES_NO as
described below." on page -283 to continue
datafill for table PVDNAGEN.
Enter either Y (yes) or N (no) to indicate
whether the HDLC inversion occurs.
CM + or $ Continuation mark
All options
For all options, datafill field LMI as described below.
Subfield or
LMI ANSI, Local management interface

BADENV,
Enter the type of local management interface.
BADMSG,
BACKCOMP, Enter ANSI to indicate that ANSI format LMI is
KARXTIME, shared with the CPE and datafill subfield
CCITT YES_NO.
Enter BADENV to define a window for
counting incoming message errors.
Enter BADMSG to define a threshold, applied
within the bounds of the BADENV value, for
the acceptable number of errored incoming
LMI messages before a timeout is declared.
Enter BACKCOMP is the switch being used
provides backwards compatibility for trunking
agents. This entry applies to enhanced trunk
frame relay interface units (FRIU). Datafill
subfield YES_NO.
Enter KARXTIME to control how long the LMI
process waits on a channel in expectation of
a status enquiry message before timing out.
Enter CCITT to indicate that the CCITT format
is shared with CPE. Datafill subfield
YES_NO.
297-8021-351 Standard 05.02 May 2001

LMI = ANSI
If the entry in field LMI is ANSI, datafill refinement YES_NO as described
below.
Subfield or
(BCS35- )
If the entry in field LMI is ANSI, datafill this
refinement. Enter Y to indicate that ANSI
format LMI is shared with the CPE.
Otherwise, enter N.
Go to field ITS, section ITS = KATXTIME to
continue datafill for table PVDNAGEN.
LMI = BADENV, BADMSG, or KARXTIME

If the entry in field LMI is KARXTIME, BADMSG, or BADENV, datafill
refinements VALUE and CONTMARK as described below.
Subfield or
VALUE 0 to 30 or 1 to Value
10
Enter the value for the LMI.
If the entry in field LMI is KARXTIME, the
range is 0 to 30. A value of 0 causes the LMI
process to ignore whatever channel to which
this agent is assigned. The process does not
raise any alarms.
The default values for KARXTIME are 20 or
15.
If the entry in field LMI is BADMSG or
BADENV, the range is 1 to 10. The
BADMSG value cannot be greater than the
BADENV value.
The default values for BADMSG are 2 or 3.
The default value for BADENV is 4.

Enter + if information for this tuple is
contained in the next record. Otherwise,
LMI = BACKCOMP
If the entry in field LMI is BACKCOMP, datafill refinement YES_NO as
described below.
Subfield or
YES_NO Y or N Yes or no. Enter Y to indicate that T1 trunking

is connected to a pre-BCS35 node. Default
value is N.
297-8021-351 Standard 05.02 May 2001

LMI = CCITT
If the entry in field LMI is CCITT, datafill refinement YES_NO as described
below.
Subfield or
YES_NO Y or N Yes or no. Enter Y to indicate that CCITT

format is shared with the CPE. Default value
is N.
All LMI
For all entries in field LMI, datafill field ITS as described below.
Subfield or
ITS KATXTIME Interim trunk signaling

ASYNUPDT
Enter KATXTIME to determine how often a
BIDIR
keep-alive message is transmitted and datafill
refinement VALUE.
Enter ASYNUPDT to indicate that the CPE is
sent asynchronous PVC status messages
and datafill refinement YES_NO.
Enter BIDIR to indicate that bidirectional LMI
procedures are used by the network and
datafill refinement YES_NO.
ITS = ASYNUPDT or BIDIR

If the entry in field ITS is ASYNUPDT or BIDIR, datafill refinement YES_NO
as described below.
Subfield or
(BCS35- )
If the entry in field ITS is ASYNUPDT or
BIDIR, datafill this refinement. Enter Y to
indicate that asynchronous PVC messages
are sent or that bidirectional LMI procedures
are used. Otherwise, enter N.
ITS = KATXTIME
If the entry in field ITS is KATXTIME, datafill refinement VALUE as
described below.
Subfield or
VALUE 0 to 30 Value
(BCS35- )
If the entry in field ITS is KATXTIME, datafill
this refinement. Enter the KATXTIME value.
Datafill example
The following example shows sample datafill for table PVDNAGEN.
MAP display example for table PVDNAGEN
AGENTKEY AGTTYPE
SPEED ABSIGN CONDEV
TUNING
LMI
ITS
__________________________________________________________
5 T1TRUNK VALID 12345677005 NATL

LS_1344KBS Y NIL
(INVERSION N)$
(KARXTIME 20) (KARXTIME 15)$
297-8021-351 Standard 05.02 May 2001

PVDNAGEN (end)
Table history
NA005
Added text to the Explanation column of field DN.
BCS36
Options CTRL_IDX and ERAM were added to field TUNING, range for fields
VALUE and ITS was corrected, and refinement CUSTOMER was added.
PVDNCHAN
ATTENTION
This table applies to new or modified content for SN07 (DMS) that
is valid through the current release.
PVDNCHAN (Private Virtual Data Network Channel Table)

Table PVDNCHAN stores the relationship between the frame relay
service (FRS) agents and the physical frame relay interface unit (FRIU)
channels.

The following tables must be datafilled before table PVDNCHAN.
PVDNAGEN
LIUINV
The FRS agents must be programmed in table PVDNAGEN.
The FRIUs must be programmed in table LIUINV.
During the ONP, if there are CAUs datafilled in table PVDNCHAN, they
will be removed during TABXFER.
Table size
0 to 2201 tuples
The table size can be increased by adding new FRIUs in table LIUINV.
Datafill
The following table lists datafill for table PVDNCHAN.
Field descriptions
Subfield or
CHANKEY see Channel key

subfields This field is the key to table
PVDNCHAN and consists of subfield
AGENT.

Enter an agent number.
DEVAREA see Device area

subfields This field consists of subfields
DEVTYPE, DEVNUM, and
CHANNEL.
DEVTYPE FRIU Device type

Enter the device type FRIU (frame
relay interface unit) on which the
frame relay service (FRS) agent is
associated.
DEVNUM 0 to 750 Device number

Enter a device number that uniquely
identifies which device type the FRS
agent is associated with.
CHANNEL 1 to 24 Channel
Enter a number between 1 and 24 to
represent the channel the FRS agent
is connected to.
Datafill example
The following example shows sample datafill for table PVDNCHAN.

MAP display example for table PVDNCHAN
CHANKEY DEVAREA
________________________________________________________
0 FRIU 102 1
1 FRIU 102 2
2 FRIU 102 3
3 FRIU 102 4
4 FRIU 236 24
Table history
SN07 (DMS)
As part of activity Q01207784 table PVDNCHAN is updated to verify
that during ONP, if there are CAUs datafilled, they are removed during
TABXFER.
PVDNCUST
Table name
Private Virtual Data Network Customer Table
Overview
Table PVDNCUST stores the name of the private virtual data network (PVDN)
customer.
Table PVDNCUST provides the PVDN customer name for table
PVDNAGEN.

Table PVDNCUST must be datafilled before table PVDNAGEN.
Table size
0 to 1000 tuples
Datafill
The following table lists datafill for table PVDNCUST.
Field descriptions
Subfield or
CUSTOMER alphanumeric Customer

(up to 20
Enter the unique customer name.
characters)
Datafill example
The following example shows sample datafill for table PVDNCUST.
MAP display example for table PVDNCUST
CUSTOMER
________________________________________________________
20000
20001
20002
297-8021-351 Standard 05.02 May 2001

PVDNCUST (end)
Table history
NA005
Table PVDNCUST was revised to remove references to subtables that no
longer exist in this table.
PVDNCUST.AGENTS
Table name
Private Virtual Data Network Customer Agents Table
The subtable AGENTS stores the PVDN customer's frame relay service (FRS)
agents.

Table PVDNAGEN must be datafilled before table PVDNCUST.AGENTS.
Note: The FRS agents must be datafilled in the PVDNAGEN table before
they can be datafilled in this subtable.
Table size
0 to 2201 tuples
Datafill
The following table lists datafill for table PVDNCUST.AGENTS.
Field descriptions
Subfield or

represent the agent number.
FRSTYPE SUBSCRIB-E FRS agent type

R
This field determines how the FRS agent is
used in connections. The only valid entry is
SUBSCRIBER.
Datafill example
The following example shows sample datafill for table
PVDNCUST.AGENTS.
297-8021-351 Standard 05.02 May 2001

PVDNCUST.AGENTS (end)
MAP display example for table PVDNCUST.AGENTS
AGENT FRSTYPE
________________________________________________________
12 SUBSCRIBER
14 SUBSCRIBER
15 SUBSCRIBER
16 SUBSCRIBER
PVDNCUST.CONNECT
Table name
Private Virtual Data Network Customer Connect Table
The subtable PVDNCUST.CONNECT stores the Private Virtual Data
Network (PVDN) customer's connections.

Table PVDNAGEN must be datafilled before table PVDNCUST.CONNECT.
Note: The frame relay service (FRS) agents must be datafilled in table
PVDNAGEN before they can be datafilled in this subtable.
Table size
0 to 32 678 tuples
Datafill
The following table lists datafill for table PVDNCUST.CONNECT.
Field descriptions
Subfield or
CONKEY see subfields Connect key

This field is the key to the table. This field
consists of subfields AGENT and DLCI, which
make up a logical endpoint of a data
connection.

Enter a number to represent the agent.
DLCI 0 to 1023 Data link connection identifier

Enter a number to represent the data link
connection identifier (DLCI).
Any entry outside this range is not valid.
CONTYPE PRIVATE Connection type

or NONPRIV-
Enter the connection type: PRIVATE or
ATE
NONPRIVATE.
297-8021-351 Standard 05.02 May 2001

PVDNCUST.CONNECT (continued)
CONTYPE = PRIVATE
If the entry in field CONTYPE is PRIVATE, datafill subfields AGENT and
DLCI.
Subfield or


Enter a number to represent a DLCI.
CONTYPE = NONPRIVATE
If the entry in field CONTYPE is NONPRIVATE, datafill subfields
CUSTOMER, AGENT, and DLCI.
Subfield or
CUSTOMER alphanumeric Customer

(1 to 20
Enter the customer name.
characters)


Enter a number to represent a DLCI.
Datafill example
The following example shows sample datafill for table
PVDNCUST.CONNECT.
PVDNCUST.CONNECT (end)
MAP display example for table PVDNCUST.CONNECT
CONKEY CONTYPE
________________________________________________________
12 247 PRIVATE 14 290
16 908 NONPRIVATE CUSTOMER_X 34 137
297-8021-351 Standard 05.02 May 2001

PXCODE
Table name
Prefix Code Table
Table PXCODE is a member of the universal translation tables. The universal
translation tables are organized to translate the incoming digit string in
segments. Table PXCODE translates the prefix code digit segment, together
with tables PXHEAD and PXCRTE.
For related information, refer to table ACCODE. For a description of the

universal translation tables, see table ACHEAD.

Table PXHEAD must be datafilled before tables PXCODE and PXRTE.
Refer to table ACCODE.
Table size
Datafill
Field names, subfield names, and valid data ranges for table PXCODE are
described in table ACCODE.
Datafill example
Table history
PXHEAD
Table name
Prefix Code Head Table
Table PXHEAD is a member of the universal translation tables. The universal
segments. Table PXHEAD translates the prefix code digit segment, together
with tables PXCODE and PXRTE.
For related information, refer to tables ACCODE and ACRTE. For a

description of the universal translation tables, refer to table ACHEAD.

Refer to table ACHEAD.
Table size
Memory is automatically allocated to a maximum of 2047 tuples. The size is
initially set to 64 and the table extends itself automatically.
Datafill
Field names, subfield names, and valid data ranges for table PXHEAD are
described in table ACHEAD.
Datafill example
Table history
297-8021-351 Standard 05.02 May 2001

PXLAMAP
Table name
ISDN Pretranslation Map Table
Table PXLAMAP associates a pretranslator name and a routing characteristic
name (RCNAME) to obtain either a new pretranslator name, an operator
position (POSITION), or a routing index. This allows the call to translate
differently based on ISDN routing characteristics.
If selector POSITION or ROUTE is not datafilled in table PXLAMAP, and the

called digits are not present, the call is routed to partial dial treatment.
If the tuple is not found in table PXLAMAP, the call proceeds to table
STDPRTCT, using the original pretranslator name.

The following tables must be datafilled before table PXLAMAP.
RCNAME
OFRT
STDPRTCT.STDPRT
POSITION
This table has no restart requirements.
Table size
0 to 262 144 tuples
Data store is dynamically allocated for each tuple.
PXLAMAP (continued)
Datafill
The following table lists datafill for table PXLAMAP.
Subfield or
PXLAKEY see subfields Translation key

This field consists of subfields RCNAME and
XLANAME.
RCNAME alphanumeric Routing characteristic name

(1 to 8
Enter the routing characteristic name required
characters)
for the translation. Valid entries must be
defined in table RCNAME.
XLANAME alphanumeric Translation name

(1 to 4
Enter the required pretranslator name. Valid
characters)
names must be defined in table STDPRTCT.
DATA see subfield Selector and refinement

This field consists of subfield SEL and its
refinements.
297-8021-351 Standard 05.02 May 2001

PXLAMAP (continued)
Subfield or
SEL POSITION, Selector

PREFIX, Enter up to two types of selectors.
ROUTE, Enter POSITION if routing to an operator
position occurs when the called digits are not
XLA
present in the ISDN information element (IE)
and datafill refinement POS. Selector
POSITION can be used in conjunction with
the selector XLA. Selector POSITION is also
used in cases where the Operator System
Access (OSA) IE specifies public or principal
network access and the called digits are not
received. This call resembles a 0- call.
With SOC option AIN00026 in the ON state,
enter PREFIX to activate the AIN response
simplification feature.
Note: Selector PREFIX can only be used in

conjunction with the XLA selector.
Enter ROUTE if required translation proceeds
to a routing table index, if no digits are present
and datafill refinements TABID and KEY.
Selector ROUTE provides a route to follow if
the called digits are not present. It can be
used in conjunction with the selector XLA.
Selector ROUTE is used in cases where the
OAS IE specifies public or private network
access, and no further digits are received.
This call resembles a call to the
interexchange operator.
Enter XLA if pretranslation continues with a
new pretranslator name and datafill
refinement NEWXLA.
PXLAMAP (continued)
Subfield or
POS TOPS, Position

CTOP, If the entry in subfield SEL is POSITION,
CAMA, datafill this refinement. Enter a valid operator
position defined in table POSITION.
TSPS,
AMRX,
RTE1, enter $ to indicate the end of the tuple.
RTE2,
RTE3,
RTE4,
AOSS,
OCC,
NONE
TABID OFRT, Routing table identifier

OFR2, If the entry in subfield SEL is ROUTE, datafill
this refinement. Enter the table to which
OFR3,
translation proceeds if no digits are present.
OFR4,
IBNRTE,
IBNRT2,
IBNRT3,
IBNRT4,
RRTE,
TTL4,
AOSS,
TOPS,
TOPSAMA,
AOSSAMA
297-8021-351 Standard 05.02 May 2001

PXLAMAP (continued)
Subfield or
KEY alphanumeric Routing index key

or 0 to 1023
If the entry in subfield SEL is ROUTE, datafill
this refinement. Enter the required
translation routing index.
The key must be a valid entry in the table
specified in refinement TABID.
If the entry in refinement TABID is AOSS,
AOSSAMA, TOPS, or TOPSAMA, enter the
alphanumeric call origination code previously
datafilled in the appropriate routing table.
If the entry in refinement TABID is any other
than mentioned above, the range is 0 to 1023,
as previously datafilled in the appropriate
routing table.
NEWXLA alphanumeric New pretranslator

(1 to 4
If the entry in subfield SEL is XLA, datafill this
characters)
refinement. If the tuple is present in table
STDPRTCT, translations proceed as
specified by table STDPRTCT. If the tuple is
not present in table STDPRTCT the following
standard default values are used:
The route selector is set to national
translations.
The type of call is set to no prefix.
The number of prefix digits is set to 0
(zero).
The translation system is set to national
translation.

PXLAMAP (end)
Datafill example
The following example shows sample datafill for table PXLAMAP.
MAP display example for table PXLAMAP
PXLAKEY DATA
________________________________________________________
64KNAME P621 ( XLA 64KP621) $
64KPUBP P622 ( XLA 64OPP621) (POSITION TOPS)$
64KPUBA P621 ( XLA 64PAP621) ( ROUTE OFRT 85)$
Table history
NA007
Added entry PREFIX.
297-8021-351 Standard 05.02 May 2001

PXRTE
Table name
Prefix Code Route Table
Table PXRTE is a member of the universal translation tables. The universal
segments. Table PXRTE translates the prefix code digit segment, together
with tables PXHEAD and PXCODE.
For related information, refer to table ACRTE. For a description of the

universal translation tables, see table ACHEAD.

Table PXHEAD must be datafilled before tables PXRTE and PXCODE.
Table size
Refer to table ACRTE.
Datafill
Field names, subfield names, and valid data ranges for table PXRTE are
described in table ACRTE.
Datafill example
Refer to table ACRTE.
Release history
NA017
Feature 59035336 introduces the Supergroup (SG) option.

QAPLNDEF
Table name
Queue Management System Application Definition Table
Table QAPLNDEF specifies the call and agent queueing limits for each
application. These limits are used to allocate internal data store for the
application. The key to this table is an application name. As of BCS33, Traffic
Operator Position System (TOPS) is the only allowable application. Initial
data store for an application is allocated within the upon entry of a tuple
against the application name in table QAPLNDEF, and is deallocated when the
tuple is deleted.
The field values in a QAPLNDEF tuple may be changed at any time for an
application, with the restriction that the following field values may not be
decreased in size:
CALLQS
CQELEMS
AGENTQS
NUMAGNTS
Therefore, decreases in any of these fields sizes (and the associated

deallocation of data store) are possible only if the entire tuple is deleted (which
may be done only after deleting application entries in table QMSCQDEF) and
then re-added with the smaller field sizes. Note, this implies a shutdown of the
application's queueing functionality until the application's QAPLNDEF tuple
and QMSCQDEF entries are reentered. An alternative is to reduce the field
size(s) as part of the dump and restore process, during BCS upgrades.
With respect to increasing the size of these fields via the change command, the
additional data store required by such an increase is allocated immediately; no
restart is required.

There is no requirement to datafill other tables prior to table QAPLNDEF.
Table size
0 or 1 tuple
Datastore is allocated dynamically when an application is added to table

QAPLNDEF. Currently, the TOPS application is the only application defined
297-8021-351 Standard 05.02 May 2001

QAPLNDEF (continued)
for QMS; it enforces the limits shown below at the time an entry is made in
table QAPLNDEF.
TOPS maximum value QAPLNDEF field name
Agents: 1023 NUMAGNTS
Call Queues: 255 CALLQS
Agent Queues: 255 AGENTQS
Call Queue 32767 CQELEMS

Elements:
A TOPS application datafilled to these maximum limits requires

approximately 855K words (1710K bytes) of datastore.
Datafill
The following table lists datafill for table QAPLNDEF.
Subfield or
APLNAME see subfield Application name. This field consists of

subfield APLNAME.
APLNAME TOPS or Application name. This is the key and must

OSSAIN be one of a predefined set of values.
CALLQS 1 to 8191 Call queues. This field specifies the number

of allocated call queues for the application.
The maximum for this field is 8,191 call
queues; however, individual applications may
enforce maximums which are lower. For
TOPS, the maximum allowable value is 255.
For OSSAIN, the maximum is 8191.
Subfield or
CQELEMS 1 to 32767 Call queues elements. This field specifies the

number of call queues elements allocated for
the application. Therefore, this field indicates
the maximum number of calls allowed in
queue at one time.
The CQELEMS field should be datafilled with
a value indicating the maximum number of
calls expected to be waiting in call queues for
an available agent at any single point in time.
This should be a value which an application
expects never to exceed. A conservative
strategy is to sum the values to be datafilled
in the CQMAXSIZ field in table QMSCQDEF
for each call queue defined and enter the
resulting value into the CQELEMS field.
If the CQELEMS threshold is exceeded
during call processing, call queue overflow
occurs, and calls are deflected from all call
queues in the application until the number of
calls in queue application-wide falls below the
CQELEMS threshold.
OM register CQELHIGH in OM Group
QMSDATA allows monitoring of the
maximum number of call queue elements in
use at one time for each QMS application, for
a given OM reporting period. If the
CQELHIGH register indicates the current
CQELEMS maximum is unnecessarily high
during busy hours, the CQELEMS field value
could be reduced.
297-8021-351 Standard 05.02 May 2001

Subfield or
AGENTQS 1 to 2047 Agent queues. This field indicates the number

of queues allocated for agents (operator
positions) that are idle and waiting for a call.
For TOPS, the maximum allowable value is
255. For OSSAIN, the maximum is 2047.
When groups of agents handle different types
of calls, separate agent queues should be
specified for each of the agent groups to
improve search efficiency. Field AGENTQS
should be datafilled with the total number of
agent queues required.
Then, for example, if DA and TA call type
agents are segregated, only the applicable
agent queues (DA or TA) must be checked.
Otherwise, each agent (DA and TA) must be
checked in the one queue.
Subfield or
NUMAGNTS 1 to 16383 Number of agents. This field indicates the

maximum number of agents that may be
logged onto TOPS positions at any one time.
For TOPS, the maximum allowable value is
1023. For OSSAIN, the maximum allowable
value is 16383.
CTSEARCH 0 to 254 Controlled traffic search depth. This field

indicates the Controlled Traffic Agent Queue
maximum search depth for an agent which
serves the call class associated with an
arriving TOPS call. The recommended value
is 10 if Controlled Traffic Profiles are in use by
an application. If not in use, zero should be
specified. For TOPS and OSSAIN, the
maximum allowable value is 254.
Controlled traffic agent profiles are intended
for agent training purposes. Normal call
processing routes different call classes to the
same call queue. However, controlled traffic
routes calls based on call type to controlled
traffic agents. This allows an agent to learn
handling of one call type at a time.
The Controlled Traffic mechanism should be
used sparingly due to the time inefficiency of
an agent in training. Also, for incoming calls,
a controlled traffic agent is considered first
before a normal operator. And calls already in
queue are not considered when a controlled
traffic agent becomes idle.
Field CTSEARCH may not be set to zero if
any agents with a Controlled Traffic profile are
currently defined for the application, since
these agents do not receive calls if the idle
Controlled Traffic agent queue search depth
were zero.
Datafill example
The following example shows sample datafill for table QAPLNDEF.
297-8021-351 Standard 05.02 May 2001

QAPLNDEF (end)
The example consists of the application name TOPS, 255 call queues, 3000
call queue elements, 20 agent queues, with a maximum number of agents of
1023, and a search depth limit of 10.
MAP display example for table QAPLNDEF
APLNAME CALLQS CQELEMS AGENTQS NUMAGNTS CTSEARCH

________________________________________________________
TOPS 255 3000 20 1023 10
Table history
NA006
Field APLNAME value OSSAIN added by functionality Operator Services,
ENSV0014.
BCS36
Subfield APLNAME was added.
BCS34
Table QAPLNDEF was introduced.
QAPLNDEF.
Dump and restore

Copy the data from the previous BCS to the current BCS for the table.
QDEF
Table name
ITOPS ACD Call Queues Table
Table QDEF is used to define the mapping of call classes to call queues. For
each call class that has been defined in table QCLASS, there can be a call
queue containing this call class.
A call queue is a set of call classes. Each one of these call queues is assigned
to an operator.
For related information, refer to table QPROP.

There is no requirement to datafill other tables prior to table QDEF.
Table size
0 to 63 tuples
Datafill
The following table lists datafill for table QDEF.
Subfield or
QNUM 1 to 63 Queue number. Enter the queue number.

Call queue 0 is reserved for any calls with the
default call class of 0 and any other classes
that are not associated with the current
mapping of call classes to call queues.
QPRIORITY 0 to 4 Priority of the queue. Enter the priority of the

queue, where 0 (zero) is the highest priority
and 4 is the lowest priority.
QGRADE 10 to 80 Grade of service. Enter the grade of service.

The length of time a call has been in a queue
is multiplied by the grade of service to
determine the `age' of a call. Calls with the
highest priority are handled first. When
several calls with the same priority are in the
queue, the ones with the highest age are
handled first.
297-8021-351 Standard 05.02 May 2001

QDEF (end)
Subfield or
QCLASSES vector of up to Classes assigned to the queue. Enter the set

256 class of call classes in this call queue. Since each
names call queue must be unique, each call class
defined in can only be entered in one call queue.
table
QCLASS
CONTMARK + or $ Continuation mark . Enter + to indicate that

additional information (QCLASSES) for this
tuple is contained in the next record.
Enter $ to indicate the end of the QCLASSES
set.
Datafill example
The following example shows sample datafill for table QDEF.
MAP display example for table QDEF
QNUM QPRIORTY QGRADE QCLASSES

________________________________________________________________
3 2 30 CLASS1 CLASS5$
9 1 10 CLASS3$
QMSCQDEF
Table name
Queue Management System Call Queue Definition Table
Table QMSCQDEF defines the characteristics of the call queues required by
each application. The table is indexed by a two-part key containing the
application name and a call queue number.
Tuples can be added at any time. They are immediately available for use by
the application specified.
Tuples cam be added or changed at any time; changes take effect immediately.
For example, if an agent with an office-wide call queue priority profile
containing TOPS call queue 0 is handling calls, and the priority of call queue
0 is changed from 20 to 10, then this change in priority takes immediate effect,
and the call selected for the agent from queue the next time the agent becomes
available is based on the updated call queue priorities in the agent's profile.
A tuple cannot be deleted if the call queue being removed is present in the call
queue profile (table TQCQPROF) of any agent (table TQOPROF) or if calls
are currently waiting in the call queue being removed.

Table QAPLNDEF must be datafilled before table QMSCQDEF.
Table size
0 to 8191 tuples
Datafill
The following table lists datafill for table QMSCQDEF.
Subfield or
APPLNCQ see subfields Application name and call queue number.

This field is the key into the table and consists
of the subfields APLNAME and CALLQNUM.
APLNAME TOPS, Application name. Enter one of the listed

OSSAIN valid application names.
297-8021-351 Standard 05.02 May 2001

QMSCQDEF (continued)
Subfield or
CALLQNUM 0 to 8190 Call queue number. The call queue number

must be less than the CALLQS value in table
QAPLNDEF for the application. For example,
if CALLQS = 10, then call queues in the range
0 to 9 may be datafilled in table QMSCQDEF.
CQPRIO 0 to 126 Call queue priority. This field indicates the

priority of the call queue (0 = lowest priority,
126 = highest priority). Calls in queues with a
higher priority are considered first, regardless
of the call age (field CQAGS). Calls in queues
with the same priority are then chosen
according to call age (field CQAGS).
This field provides absolute priority. Whereas,
field CQAGS provides relative priority.
For additional, related information, refer to
table TQCQPROF to the paragraphs about
field PRIOTYPE that follow the datafill
example.
Subfield or
CQAGS 10 to 80 Call queue assignable grade of service aging.

This field allows artificial aging of a call. A
value between 10 and 80 may be selected,
representing aging factors from 1.0X to 8.0X.
The age of the oldest call in a queue is
multiplied by the queue's aging factor, and the
resulting age is used for comparison with the
oldest calls in other served queues. For no
aging, enter 10.
As an example, if a call is 3 seconds old and
CQAGS = 18, its adjusted age is 3 * 1.8 = 5.4
seconds.
Calls in a queue with a higer priority (field
CQPRIO) are served first. Then calls with the
same priority are chosen according to age
(field CQAGS), the oldest being served first.
This field provides relative priority. Whereas,
field CQPRIO provides absolute priority.
For additional, related information, refer to
table TQCQPROF to the paragraphs about
field PRIOTYPE that follow the datafill
example.
297-8021-351 Standard 05.02 May 2001

Subfield or
CQMAXSIZ 0 to 32766 Call queue maximum size. This field defines

the maximum number of calls allowed in the
queue, above which all calls are deflected
due to queue overflow, including calls with a
deflect status of NO DEFLECT (field
ALLOWDEF = N). This usually occurs for a 0
minus call when no operator is available.
Then, the call is deflected and sent to
treatment. On the second attempt, if no
operator is available, the call is given a NO
DEFLECT status.
Since a single pool of call queueing elements
is maintained for each application declared in
table QAPLNDEF, the CQMAXSIZ field
prevents a call queue or a subset of call
queues in a given application from consuming
all of the application's call queueing elements
when those call queues are in an extreme
overload condition. This ensures that other
call queues not in an overload condition can
continue to function normally.
The CQMAXSIZ value should be set so that it
is not exceeded during anticipated peak traffic
conditions. The CQCDTIME field should be
utilized to control the input of calls to the call
queues so that the CQMAXSIZ thresholds are
not reached.
DEFLAREA see subfield Deflect area. This field consists of subfield

ALLOWDEF and refinements.
Subfield or
ALLOWDEF Y or N Allowed deflection. This field indicates

whether a deflection threshold should be
considered before queueing a call.
If this field is set to N, then calls are queued
regardless of the predicted wait time (but still
subject to the CQMAXSIZ limitation and the
limited number of call queue elements
available as determined by the CQELEMS
field size in table QAPLNDEF). No further
refinements require datafill.
If calls marked for this call queue are to be
deflected when the predicted wait for a call
exceeds the threshold specified in field
CQCDTIME, enter Y. Then datafill
refinements CQCDTIME and MINODEFL.
297-8021-351 Standard 05.02 May 2001

Subfield or
CQCDTIME 0 to 32766 Call queue call deflection time. Enter the

predicted call wait time (in tenths of seconds)
before the call is deflected from the queue.
If the predicted wait time for newly arriving
calls exceeds the CQCDTIME value, new
calls are deflected from the queue until the
predicted wait time drops below this
threshold.
An exception to this is a 0 minus call on the
second attempt where the call should not be
deflected (Deflect Status = NO DEFLECT). In
this case, there is an attempt to place the call
in the call queue regardless of the
CQCDTIME threshold (subject to the
CQMAXSIZ and CQELEMS constraints).
The predicted wait time is determined by
monitoring the rate at which calls are being
served from the given queue (for the
preceding 60 seconds, updated every 10
seconds), along with the number of calls in
queue. For example, if 120 calls were served
in the previous 60 seconds (i.e., calls are
being served at the rate of 2 calls per second),
and the queue holds 29 calls, then the
projected wait time for a newly arriving call is
(29 + 1)/2, or 15 seconds.
Calls served include both calls presented to
an operator and calls abandoned.
If no calls have been served for a given call

queue in the preceding 60 seconds, then the
system is unable to predict the wait time of an
arriving call. The system does not consider
deflecting calls from this queue in this case
until a call is served (and the 60-second tally
is updated to reflect it) and a valid predicted
wait time is obtained.
Subfield or
MINODEFL 0 to 32766 Minimum no deflection. Enter the minimum

number of calls in queue below which calls
are not deflected, even if the value in
CQCDTIME is exceeded. This prevents calls
from being prematurely deflected from call
queues with very low or erratic throughput. If
the number of calls in queue would be equal
to or greater than MINODEFL, then
CQCDTIME is applied.
PRAQAREA see subfield Priority agent queue area. This field consists
of subfield PRIOAQ and refinements.
297-8021-351 Standard 05.02 May 2001

Subfield or
PRIOAQ Y or N Priority agent queue. This field indicates

whether a priority agent queue should be
associated with the given call queue
(CALLQNUM).
If this field is set to Y, then the agent queue
specified in field AQNUM is searched first for
an agent to serve incoming calls, even if
agents in other agent queues able to serve
the call have been idle longer.
If no agent able to serve the call is found in the
priority agent queue, then the remaining
agent queues are searched only if the arriving
call's predicted wait time (if it were to be
queued) exceeds the PRTHTIME threshold
specified. If found, the agent's age (that is,
the length of time the agent has been waiting
in the agent queue) is compared to that of the
oldest agent able to serve the call waiting in
other agent queues. The agent which has
been waiting the longest is presented with the
call.
If the predicted wait time does not exceed the
threshold or the system is unable to predict
the wait time, the call is queued.
If this field is set to N, then all agent queues
containing agents able to serve the call are
considered equally with the call being
presented to the most idle agent (if one is
available).
If this field is set to Y, datafill refinements
AQNUM and PRTHTIME. Otherwise, if set to
N, no further refinements require datafill.
Subfield or
Priority agent queues can be used to route

certain types of calls to operators with more
experience or expertise in handling these
types of call. This applies even if less
preferred operators have been waiting longer
for a call.
Priority agent queues should be used with
restraint, since they distort the normal
distribution of calls to operator positions on a
most-idle basis. For example, operators in
priority agent queues could be overworked
while other operators sit idle.
AQNUM 0 to 2046 Agent queue number. Enter the agent queue

to receive priority in the range 0 to x, where x
= AGENTQS - 1, using the agent queue value
specified in table QAPLNDEF.
PRTHTIME 0 to 32766 Priority threshold time. If no agent is waiting

in the priority agent queue to serve the call,
then other agent queues are considered only
if the predicted wait time for the call exceeds
this threshold (in tenths of seconds).
Datafill example
The following example shows sample datafill for table QMSCQDEF.
MAP display example for table QMSCQDEF
APPLNCQ CQPRIO CQAGS CQMAXSIZ DEFLAREA PRAQAREA

________________________________________________________________
TOPS 0 20 18 300 Y 600 5 Y 4 100
TOPS 1 20 10 200 N Y 4 100
TOPS 2 35 18 300 Y 600 5 Y 3 100
TOPS 3 35 10 240 Y 600 5 N
The above example consists of four TOPS applications, call queue numbers 0
to 3. Zero and one are assigned a call queue priority of 20; two and three are
assigned call queue priority of 35. Zero and two are assigned a grade of service
factor of 18 while one and three are assigned a factor of 10. One is not allowed
deflection while zero, two, and three are allowed deflection with a threshold of
297-8021-351 Standard 05.02 May 2001

QMSCQDEF (end)
600 and a minimum value of 5. A priority agent queue of four is associated

with zero and one while three is the priority agent queue associated with two.
Call queue three is not associated with a priority agent queue. A priority
threshold time of 100 is specified for call queue zero and two while a time of
zero is specified for call queue one.
Table history
NA006
Field APLNAME value OSSAIN added by functionality Operator Services,
ENSV0014.
BCS34
Table QMSCQDEF was introduced.
This section provides information on datafilling table QMSCQDEF for
specific applications, and product descriptive information related to table
QMSCQDEF.
Dump and restore procedures

Copy the data from the previous BCS to the current BCS for the table.
Miscellaneous
The call queue number must be less than the CALLQS value datafilled in table
QAPLNDEF. When priority agent queue is specified, AQNUM must be less
than the CALLQS value datafilled in table QAPLNDEF.
QMSMIS
Table name
QMS MIS Link Definition Table
Table QMSMIS defines the links used by a Queue Management System
Management Information System (QMS MIS) application and also defines the
audit frequency for the links.

When field DATALINLK = MPC, datafill the tables that follow in the
indicated order before table QMSMIS:
MPC
MPCLINK
When field DATALINLK = ETHERNET, datafill the tables that follow in the
indicated order before table QMSMIS:
OANODNAM
OANODINV
When field DATALINLK = IP, datafill table IPCOMID before table QMSMIS.
Table size
0 to 2 tuples
QMSMIS (continued)
Datafill
The following table lists datafill for table QMSMIS.
Field descriptions
Subfield or
INDEX see subfield QMS Management Information System index.

This field consists of subfield K.
K TOPS, QMS Management Information System

QMSNILAP, application in use. This is the key field of the
OSSAIN table. The entries are:
TOPS - Traffic Operator Position System.
This entry is used for MIS statistics
accumulated for calls handled by
operators. This entry requires that field
DATALINK is set to MPC or IP.
QMSNILAP - non-TOPS QMS application
OSSAIN - Operator Services System
Advanced Intelligent Network. This entry
is used for MIS statistics accumulated for
calls handled by OSSAIN Service Nodes.
This entry requires that field DATALINK is
set to ETHERNET.
DATALINK see subfield Data link. This field consists of subfield

DATALINK and refinements.

QMSMIS (continued)
Field descriptions
Subfield or
DATALINK MPC, Datalink. This field indicates the type of

ETHERNET datalink used by the application to send MIS
statistics. The values are the following:
IP
MPC - Multiprotocol controller link
conversation list, which uses an X.25
datalink. This link is used by the TOPS
MIS application. This entry requires that
subfield K is set to TOPS or QMSNILAP.
Enter datafill in subfield MLCLIST and
refinements.
ETHERNET - An Ethernet link, which is
used by the OSSAIN MIS application.
This entry requires that subfield K is set to
OSSAIN. Enter datafill in refinements
NODENAME, MISNETID, and
MISPORT.
IP - Internet protocol. Datafill fields
BUFXTIME and CONNLIST.
MLCLIST see subfields Multiprotocol controller link conversation list.

This field consists of subfields M, L, and C.
Up to 16 multiples of the subfields can be
entered. If less than 16 multiples are entered,
end with a $ (dollar sign).
Entries in field MLCLIST must match entries
in tables MPC and MPCLINK.
Only permanent virtual circuits (PVC) are
supported by the Queue Management
System Management Information System
(QMS MIS) application.
At least two links should always be datafilled
for the TOPS application to guarantee that
data is not lost if one link fails. A maximum of
16 links can be entered for the TOPS
application.
When more than one link has datafill against
the TOPS application, the DMS switch shares
the data transmission load, sending buffers
across the least recently used link.
QMSMIS (continued)
Field descriptions
Subfield or
M 0 to 255 Multiprotocol controller number. Enter the

multiprotocol controller (MPC) number. This
entry must first be entered in table MPC.
L 0 to 3 Link number. Enter the link number. This

entry must first be entered in table MPCLINK.
Note: All link numbers must be 2 or 3 for

QMS MIS applications.
C 0 to 255 Conversation number. Enter the

conversation number.
NODENAME name from OSSAIN node name. Enter the source name
table of the MIS data. The node must be entered in
OANODINV tables OANODNAM and OANODINV. For
table OANODINV, set fields ONPMTYPE =
OSNM.
MISNETID 0 to 32,766 Management information system (MIS)

network identification. This field enables a
unique identifier to be specified within the
header of the MIS data stream. Enter a
source identifier for the MIS data. In the
OSAC environment, where multiple Host
nodes may be connected, the MIS network Id
can be used to uniquely identify the source of
the MIS statistics.
MISPORT 1024 to MIS port. This field specifies the port number
32,767 for sending an MIS class message to the
given node.
BUFXTIME 1 to 59 Buffer transfer time. This field indicates the

maximum period before a buffered MIS IP
buffer is sent to the MIS server.
CONNLIST see subfields Connect list. Datafill subfields DESTADDR,

DESTPORT, DESSTAT, and COMID.
DESTADDR 4 numbers Destination address. Enter the destination IP

(0-255, 1-255, address to send the QMS MIS event
0-255, 0-255) message. The entry consists of 4 numbers,
each in the indicated range and separated by
a space.

QMSMIS (continued)
Field descriptions
Subfield or
DESTPORT 1024 to 32767 Destination port. Enter the port number to

send the QMS MIS event message.
DESSTAT INACTIVE or Destination status. The desired status of the

ACTIVE destination server.
COMID number from Communication identifier. Enter an index into

IPCOMID table IPCOMID. This field points to an XPM
and associated port (according to the service
name) to use for IP communication.
Datafill example
The following example shows sample datafill for table QMSMIS.
MAP display example for table QMSMIS
INDEX DATALINK
---------------------------------------------------------
OSSAIN ETHERNET MIS_OSSAIN 24 7001
TOPS MPC (3 3 1) (4 4 2) $
The above example first tuple shows 2 data links for redundancy as
recommended.
This section provides information on dump and restore procedures and error
messages that can occur when datafilling table QMSMIS.
Dump and restore

No dump and restore is needed when first applied. Normal dump and restore
procedures apply after the first application.
QMSMIS (continued)
Error messages
The following error messages apply to table QMSMIS.
Error messages for table QMSMIS
UNABLE TO OBTAIN OWNERSHIP OF If an attempt is made to datafill an MPC

CONVERSATION MPC <mpc or link (field MLCLIST) in table
number>,LINK <link number>, QMSMIS that is not datafilled in tables
CHANNEL <channel number>, AT MPC or MPCLINK, respectively, this
POSITION <position number> IN error message is produced:
MLCLIST.
<Position number> refers to the position
of the particular MLC tuple in the MLC
list. For instance, if the second MLC
element in the MLC list had a link
number that is not datafilled in table
MPCLINK, the position number printed
is 2.
The node specified must be The specified node name must be

datafilled with PMTYPE of datafilled with a PMTYPE of OSNM in
OSNM in Table OANODINV. table OANODINV or this message is
displayed.
You must OFFL the new node The node name can not be changed
before changing the node unless the node specified by node
name. name is off-line. Otherwise, one of
these messages is displayed.
You must OFFL the old node

before changing the node
name.
You must OFFL this node before The MISPORT can not be changed
changing the MISPORT. unless the node specified by
NODENAME is off-line. Otherwise, this
You must OFFL this node before The tuple cannot be deleted unless the
deleting the tuple. node specified by NODENAME is
off-line. Otherwise, this message is
displayed.
You must OFFL this node before The tuple cannot be added unless the
adding the tuple. node specified by NODENAME is
off-line. Otherwise, this message is
displayed.

QMSMIS (continued)
The NODENAME specified is in The specified node name cannot be in

use in Table OASESNPL. use in table OASESNPL. Otherwise,
this error message is displayed.
You must set DATALINK to IP or The index and DATALINK fields must
MPC for TOPS MIS facility. match. If the index is set to TOPS the
DATALINK field must be either IP or
You must set DATALINK to MPC, and if the index is OSSAIN, the
ETHERNET for OSSAIN MIS DATALINK needs to be ETHERNET.
nodes. Failure to do so results in one of these
messages.
Invalid COMID. Make sure The COMID specified must already be

COMID exist in table IPCOMID. datafilled in table IPCOMID before it
can be used in table QMSMIS. Failure
to do so will result in this message.
Error! COMID already in use by If the COMID is already being used by

another application another application, this error message
is displayed.
ERROR ALLOCATING MEMORY FOR If the CM cannot allocate memory when

NEW IP TUPLE. an IP tuple is being added, this error
COMID IS NOT PRESENT IN TABLE When an IP tuple being added to the IP

IPCOMID vector fails to bind to the IP Datacomm
layer due to an invalid comid error this
COMID IS ALREADY IN USE BY When an IP tuple being added to the IP

ANOTHER APPLICATION vector fails to bind to the IP Datacomm
layer because the comid is already in
use by another application, this
PROBLEM WITH THE SERVICE When an IP tuple being added to the IP

BOUND TO THIS COMID vector fails to bind to the IP Datacomm
layer due to a wrong service datafilled
for the comid this message is displayed
COMID FAIL TO BIND TO IP LAYER When an IP tuple being added to the IP

vector fails to bind to the IP Datacomm
layer for any unknown reason, this
QMSMIS (continued)
EMPTY IP VECTOR IS NOT ALLOWED Empty IP vectors are not allowed. This
message is displayed if an attempt is
made to add an empty vector.
DUPLICATE COMIDs ARE NOT An attempt to add duplicate COMIDs to

ALLOWED.USE ONE COMID PER IP an IP vector will result to this message
CONNECTION. being displayed.
ERROR - ONLY COMIDS An attempt to datafill a protocol other

DATAFILLED TO USE TCP than TCP for a COMID used by table
PROTOCOL ARE ALLOWED IN TABLE QMSMIS will result in this message.
QMSMIS.
FAIL TO ALLOCATE MEMORY FOR IP If memory cannot be allocated for the IP

BUFFERS. buffers the first time an IP interface is
added in table QMSMIS, this message
is displayed.
YOU MUST SET THE DESSTAT When an attempt is made to delete a

FIELD(S) TO INACTIVE BEFORE TOPS IP tuple whose DESSTAT
DELETING THE TUPLE. Field(s) are active, this message is
displayed.
YOU MUST SET THE DESSTAT When an attempt is made to change the
FIELD(S) TO INACTIVE BEFORE datalink of a TOPS tuple from IP to
CHANGING THE TUPLE. MPC, this message is displayed if any
of the DESSTAT fields are active.
WARNING!! DATAFILLING A COMID When a non-zero port is datafilled in

WITH A NON-ZERO PORT IN TABLE table IPSVCS for a QMSMIS service, a
IPSVCS FOR TCP, WILL RESULT IN warning is produced when the COMID
TCP/IP CONNECTION that uses that port is datafilled in table
RE-ESTABLISHMENT DELAYS. IT QMSMIS.
IS HIGHLY RECOMMENDED TO
DATAFILL ZERO AS THE PORT
NUMBER IN TABLE IPSVCS FOR THE
QMS MIS IP APPLICATION.
THIS NODE HAS DATAPATH XAETHR When an attempt is made to datafill an

IN TABLE OANODINV. OSSAIN QMS OSSAIN tuple whose node has data
MIS SERVERS MUST USE THE EIU. path XAETHR in table OANODINV, this
XA-CORE ETHERNET DATA PATH IS message is displayed
NOT SUPPORTED FOR OSSAIN QMS
MIS.

QMSMIS (end)
Table history
SN07 (DMS)
Cross-checks are added to enforce that an OSSAIN QMS MIS server cannot
be datafilled in table OANODINV with data path XAETHR. Error messages
description updated. Feature A00005160.
TOPS13
Field DATALINK has new value IP and new error messages are added by
feature A59007458 in functionality MIS Over IP, OSB00001.
TOPS10
Feature AF7439 in functionality OSSAIN 10 Enhancements (OSAN0005)
makes the following changes:
Field INDEX, subfield K has new value OSSAIN.
Field DATALINK is new, which has existing value MPC and new value
ETHERNET plus refinements.
BCS36
Subfield K was added. Notes were added to field MLCLIST and subfield L.
BCS34
Table QMSMIS was introduced.
QMSTOPS
Table name
Queue Management System TOPS Initial Call Type Assignment Table
Table QMSTOPS specifies the initial call type for queuing (CT4Q) for calls
that route Traffic Operator Position System Queue Management System
(TOPS QMS). This table is indexed by the same range of call origination (CO)
types used as a key for table TOPS. Datafilled against each CO type is a
CT4Q.
Like TOPS, QMSTOPS is a fixed table. No tuples can be added or deleted.

Upon initialization, the reserved CT4Q UNSPEC is datafilled against all of the
COs.

Table CT4QNAMS must be datafilled before table QMSTOPS.
Field CT4Q values used in each tuple must be datafilled in table CT4QNAMS.
Table size
63 tuples
Datafill
The following table lists datafill for table QMSTOPS.
Field descriptions
Subfield or
CO alphanumeric Call origination. Enter a call origination type

with the same range as table TOPS.
CT4Q alphanumeric Call type for queuing. Enter an initial CT4Q

(1 to 32 value for call type refinement.
characters)
This entry must first be defined in table
CT4QNAMS.
Datafill example
The following example shows sample datafill for table QMSTOPS.
The example consists of all 60 call originations with the corresponding

CT4Qs.
QMSTOPS (continued)
MAP display example for table QMSTOPS
CO CT4Q
________________________________________________________
UNSPEC UNSPEC
OH 0_MINUS
OA 0_PLUS
DD 1_PLUS
CAMA CAMA
CDIR UNSPEC
RCAMA RCAMA
DELAY DELAY
121 GENERAL
131 GENERAL
141 GENERAL
151 GENERAL
161 GENERAL
171 GENERAL
181 GENERAL
191 GENERAL
555 DA_555
1150 INW_1150
1151 INW_1150
1152 INW_1150
1153 INW_1150
1154 INW_1150
1155 INW_1150
1156 INW_1150
1157 INW_1150
1158 INW_1150
1159 INW_1150
1160 INW_1150
1161 INW_1150
1162 INW_1150
TS GENERAL
TSUB GENERAL
APS GENERAL
ALM GENERAL
297-8021-351 Standard 05.02 May 2001

QMSTOPS (end)
MAP display example for table QMSTOPS (continued)
CO CT4Q
________________________________________________________
INTC GENERAL
211 GENERAL
311 GENERAL
411 GENERAL
511 GENERAL
611 GENERAL
711 GENERAL
811 GENERAL
911 GENERAL
MOBILE GENERAL
999 GENERAL
HOM555 DA_555_HOM
FOR555 DA_555_FOR
SPARE1 GENERAL
SPARE2 GENERAL
SPARE3 GENERAL
SPARE4 GENERAL
SPARE5 GENERAL
OOC141 GENERAL
OOC151 GENERAL
OOCOVS GENERAL
OOCMAN GENERAL
OOC801 GENERAL
OOCDELAY GENERAL
OOCDB GENERAL
INTS GENERAL
Table history
NA005
Added call origination type CDIR per functionality Auto Country Direct,
ENSV0010.
BCS34
Table QMSTOPS introduced
This section provides information on datafilling table QMSTOPS for specific
applications, and product descriptive information related to table QMSTOPS.
No dump and restore is needed when first applied. Normal dump and restore
procedures apply after the first application.
QPROFILE
Table name
ITOPS ACD Operator Call Handling Table
Table QPROFILE is used to map the operator identification (ID) or position
number to call queues.
Different positions can be assigned different call queues since some positions
can be limited in the types of calls they can handle because of hardware
requirements. Operators can also be assigned different call queues as required.
For related information, refer to table QPROP.

Table QDEF must be datafilled before table QPROFILE.
Table size
0 to 4048 tuples
Datafill
The following table lists datafill for table QPROFILE.
Subfield or
QPROFKEY see subfields Key into table QPROFILE. This field consists
of subfields QPROFTYP and QPROFNUM.
QPROFTYP OPR or POS Type of key. Enter OPR for operator or POS
for position.
QPROFNUM 0 to 3099 Operator identification or position number. If

the entry in subfield QPROFTYP is OPR,
enter the operator identification (ID).
If the entry in subfield QPROFTYP is POS,
enter the position number.
QTEAM 0 to 30 Team number. Enter the team the operator or

position belongs to.
297-8021-351 Standard 05.02 May 2001

QPROFILE (end)
Subfield or
QOPTIONS ALL, EXCL, Inclusion of queues. Enter one of the

INCL following:
ENTER ALL to indicate that this operator ID or
position number can handle all queues
defined in table QDEF. No refinements
require datafill.
ENTER EXCL to indicate that this operator ID
or position number can handle all queues
defined in table QDEF except the queues
listed in field QUEUES. Datafill refinement
QUEUES.
ENTER INCL to indicate that this operator ID
or position number can handle only those
queues listed in field QUEUES, of all the
queues defined in table QDEF. Datafill
refinement QUEUES.
QUEUES vector of 0 to Queues. If the entry in field QOPTIONS is

63 queues EXCL enter the set of queues, each queue
known in table QDEF, that this operator ID or
position number cannot handle.
If the entry in field QOPTIONS is INCL enter
the set of queues, each queue known in table
QDEF, that this operator ID or position
number can handle.
If less than 63 queues are required, end the
list with a $ (dollar sign).
Datafill example
The following example shows sample datafill for table QPROFILE.
MAP display example for table QPROFILE
QPROFKEY QTEAM QOPTION

QUEUES
________________________________________________________________
OPR 3099 1 INCL (1 7) $
QPROP
Table name
ITOPS Automatic Call Distribution Call Properties Table
Overview
The ITOPS Automatic Call Distribution system tables in the following table
are available in offices with the ITOPS Enhanced ACD feature.
ITOPS Automatic Call Distribution system tables
QPROP 2921A, B ITOPS ACD Call Properties Table Record
QCLASS 2922A, B ITOPS ACD Call Classes Table Record
QDEF 2923A, B ITOPS ACD Call Queues Table Record
QPROFILE 2924A, B ITOPS ACD Operator Call Handling Table Record
The ITOPS ACD tables for the enhanced call queueing system provide the
operating company with an efficient, flexible, call queueing system that is easy
to use. The design of the enhanced queueing system is based on call
properties, attributes, and classes.
Attributes
Call attributes are the functional or physical details of a call. For example,
physical attributes may be hotel or coin calls, and functional may be calls
booked in the database or calls that are recalled to the operator.
Properties
A call property is a grouping of call attributes in such a way that each property
is independent of the other. The following properties have been defined so far,
each containing attributes used to place calls in appropriate queues. The
properties are as follows:
Call Origination
Service Class
Recall
Foreign
Special
297-8021-351 Standard 05.02 May 2001

QPROP (continued)
An example of the contents of a given property, such as Service Class is as

follows:
Station
Hotel
Coin
Attendant Pay Station
Mobile
Marine
This property defines the physical origination of the call, whether from a hotel,
coin phone, or other. The above attributes are unique to Service Class and
cannot be defined in any of the other properties.
Classes
A call class is a set of attributes from each of the properties which is used to
separate calls into different call queues. When a call is routed to operator
services, the call must first be placed in a call class. The call class is
determined by the attributes in the different properties in the call. For example,
if a call arrives with the attribute OH, this generates a set of call classes that
can accept this call. If the service class attribute is HOTEL, all the call classes
with HOTEL contained in the previously generated set generate a subset of
these sets. This process of getting subsets of subsets continues over all the
defined properties. The resulting set of call classes will contain one call class
or no call classes. If one call class remains, the call is assigned to this call
class. If no class remains, the call is placed into the default call class.
Table QPROP defines the properties and the attributes within each property.
Table QPROP is used in the enhanced queueing system to define attributes that
may be used in call classes. Only attributes defined in this table may be used
to datafill the rest of the queueing tables. This table allows the administration
to limit the number of properties and attributes so that the queueing of calls is
more efficient.
The following rules must be adhered to when mapping attributes to properties

in table QPROP.
1. Though a call may have several attributes, the call can only have one
attribute from each of the defined properties. For example, a call cannot
QPROP (continued)
have both hotel and coin attributes since they are both from the same
property, service class.
2. Only attributes defined in table QPROP can be used in other queueing
tables as queue selection parameters.
3. If an attribute is not defined in table QPROP and a call arrives at a position
with this attribute, the attribute is ignored and the call class is determined
from other attributes of the call.

There is no requirement to datafill other tables prior to table QPROP.
Table size
0 to 8 tuples
Datafill
The following table lists datafill for table QPROP.
Subfield or
QPROPKEY 0 to 7 Key into table QPROP. Enter the numeric

index for a call property.
ATTRIBS see subfield Call attributes. This field consists of subfield

QPROPSEL and a set of attributes related to
the selector value.
See the appropriate field name for its
definition.
297-8021-351 Standard 05.02 May 2001

QPROP (continued)
Subfield or
QPROPSEL CO, Call attributes selector. Enter one of the

FOREIGN, following: CO, FOREIGN, RECALL, SC, or
RECALL, SC, SPECIAL.
or SPECIAL
Enter CO for Call Origination properties and
enter the set of call origination attributes in
field ATTRIB0.
Enter FOREIGN for foreign attributes and
enter the set of foreign attributes in field
ATTRIB3.
Enter RECALL for recall attributes and enter
the set of recall attributes in field ATTRIB2.
Enter SC for Service Class attributes and
enter the set of service class attributes in field
ATTRIB1.
Enter SPECIAL when the attributes cannot be
determined from the information received
from an incoming call. These attributes can
only be added to a call by referencing the
tuple in table ITOPATTR that contains these
attributes. Referencing is done from either
the ITOPS table or the transfer key. Enter the
set of special attributes in field ATTRIB4.
QPROP (continued)
Subfield or
ATTRIB0 ALL, BOOK, Call origination attribute set. Enter NONE,

DA, DD, ALL, or a set of attributes listed below, each
DELAY, EST, attribute separated by a blank, and the last
INT, INW, attribute followed by a $.
NONE, OA,
Enter ALL for the whole set of attributes listed
OH, OPER, or
above.
SPECIAL
Enter BOOK for database booking
Enter DA for directory assistance
Enter DD for direct dialed
Enter DELAY for database originated
Enter EST for estimate charge
Enter INT for forward party intercept
Enter INW for call originated by another
operator
Enter NONE for no attributes.
Enter OA for operator assisted
Enter OH for operator handled
Enter OPER for operator originated
Enter SPECIAL for handle special
requirements, for example repairs
297-8021-351 Standard 05.02 May 2001

QPROP (continued)
Subfield or
ATTRIB1 ALL, APS, Service class attribute set. Enter NONE, ALL,
COIN, or a set of attributes listed below, each
HOTEL, attribute separated by a blank, and the last
MARINE, attribute followed by a $.
MOBILE,
NONE, or
above.
STATION
Enter APS for attendant pay station
Enter COIN for coin
Enter HOTEL for hotel
Enter MARINE for marine
Enter MOBILE for mobile
Enter STATION for station
ATTRIB2 ALL, NFY, Recall attribute set. Enter NONE, ALL, or a

NONE, or set of attributes listed below, each attribute
TAC separated by a blank, and the last attribute
followed by a $.
above.
Enter NFY for notification recall
Enter TAC for time and charges recall
QPROP (end)
Subfield or
ATTRIB3 ALL, FOR, or Foreign attribute set. Enter NONE, ALL, or a

NONE set of attributes listed below, each attribute
separated by a blank, and the last attribute
followed by a $.
above.
Enter FOR for foreign
ATTRIB4 ALL, NONE, Special attribute set. Enter NONE, ALL, or a

or set of attributes listed below, each attribute
SPL1 to separated by a blank, and the last attribute
SPL16 followed by a $.
Enter SPL1 to SPL16 for special.
above.
Datafill example
The following example shows sample datafill for table QPROP.
MAP display example for table QPROP
QPROPKEY
ATTRIBS
________________________________________________________________
1
C OA OH $
2
SC HOTEL COIN $
3
FOREIGN FOR $
Table history
BCS36
Corrected value in field ATTRIB3 (changed FRN to FOR)
297-8021-351 Standard 05.02 May 2001

QT0-QT5H
Table name
ITOPS Queue Length Threshold High Traffic Table
For related information, refer to table QTTIDXH.
Tables QT0H, QT1H, QT2H, QT3H, QT4H, and QT5H contain the queue
length threshold value associated with the related Average Work Time (AWT)
value during the high traffic period.

There is no requirement to datafill other tables prior to table QT0-QT5H.
Table size
0 to 57 tuples
Datafill
The following table lists datafill for table QT0-QT5H.
Subfield or
OPRANGE 0_0 to Occupied positions range. Preprinted on the

585_600 form. For a range above any expected in the
permitted office put a line through the preprinted value
ranges to indicate that it need not be entered,
preprinted on equivalent to setting all the fields associated
form with this range to 0.
Note: Field OPRANGE, representing the

occupied positions range, is preprinted on the
form as the DMS program will only accept the
preprinted values. Ranges that are above the
maximum range expected in the office may
be omitted by putting a line through them
equivalent to setting all the fields associated
with these ranges to 0.
CWOFF 0 to 255 Call Waiting signal OFF threshold. Enter the

number below which the number of calls
waiting in the queue must fall to erase the CW
signal on all CRTs.
QT0-QT5H (end)
Subfield or
CWON 0 to 255 Call Waiting signal ON threshold. Enter the

number which must be reached by the
number of calls waiting in the queue to turn on
the CW signal on all CRTs.
DEFLECT 0 to 255 Deflect calls threshold. Enter the number that

the position of the call in the queue must
reach to result in the call being deflected to
treatment EMR3 or EMR4.
If the entry in this field is 0, calls are deflected
to EMR4.
If the entry in this field is other than 0, calls are
deflected to EMR3 (see ``Functional
description of table TMTCNTL.TREAT" for
more information).
Datafill example
The following example shows sample datafill for table QT0-QT5H.
MAP display example for table QT0-QT5H
OPRANGE CWOFF CWON DEFLECT

________________________________________________________
81_88 51 75 141
297-8021-351 Standard 05.02 May 2001

QT0-QT5L
Table name
ITOPS Queue Length Threshold Low Traffic Table
Tables QT0L, QT1L, QT2L, QT3L, QT4L, and QT5L contain the queue
length threshold value associated with the related average work time (AWT)
value during the low traffic period.

There is no requirement to datafill other tables prior to table QT0-QT5L.
Table size
0 to 57 tuples
Datafill
The following table lists datafill for table QT0-QT5L.
Subfield or
OPRANGE 0_0 to Occupied positions range. Preprinted on the

585_600 form. For a range above any expected in the
permitted office, put a line through the preprinted value
ranges to indicate that it need not be entered,
preprinted on equivalent to setting all the fields associated
form with this range to 0 (zero).
Note: Field OPRANGE, representing the

occupied positions range, is preprinted on the
form as the DMS program will only accept the
preprinted values. Ranges which are above
the maximum range expected in the office
may be omitted by putting a line through them
equivalent to setting all the fields associated
with these ranges to 0.
CWOFF 0 to 2565 Call Waiting signal OFF threshold. Enter the

number below which the number of calls
waiting in the queue must fall to erase the call
waiting (CW) signal on all CRTs.
QT0-QT5L (end)
Subfield or
CWON 0 to 2565 Call Waiting signal ON threshold. Enter the

number that must be reached by the number
of calls waiting in the queue to turn on the CW
signal on all CRTs.
DEFLECT 0 to 255 Deflect calls threshold. Enter the number that

the position of the call in the queue must
reach to result in the call being deflected to
treatment EMR3 or EMR4.
If the entry in this field is 0, calls are deflected
to EMR4.
If the entry in this field is other than 0, calls are
deflected to EMR3 (see ``Functional
description of table TMTCNTL.TREAT" for
more information).
Datafill example
The following example shows sample datafill for table QT0-QT5L.
MAP display example for table QT0-QT5L
OPRANGE CWOFF CWON DEFLECT
________________________________________________________
81_88 51 75 141
297-8021-351 Standard 05.02 May 2001

QTHRESH
Table name
ITOPS Queue Threshold Limits Table
Table QTHRESH is used to define the queue threshold limits for the call
queues.

There is no requirement to datafill other tables prior to table QTHRESH.
It is recommended that table QDEF be datafilled before table QTHRESH, but

this is not mandatory.
Table size
0 to 64 tuples
Datafill
The following table lists datafill for table QTHRESH.
Subfield or
QNUM 0 to 63 Queue number. Enter the queue number.
QCWN1 0 to 1800 Call waiting prompt on time 1. Enter the value

in seconds when the Call Waiting prompt is to
be turned on, which applies in time interval 1
(of a 24 h day) defined in field TIME1.
QCWF1 0 to 1800 Call waiting prompt off time 1. Enter the value
be turned off, which applies in time interval 1
QCD1 0 to 1800 Call deflection time 1. Enter the value in

seconds when calls are to be deflected and
the Calls Deflected prompt is to be turned on,
which applies in time interval 1 (of a 24 h day)
defined in field TIME1.
The value in field QCD1 must be greater than
the value in field QCWN1.
QTHRESH (continued)
Subfield or
TIME1 0 to 2400 End time for interval 1. Enter the time in hours
and minutes (hhmm) when time interval 1
ends.
Time interval 1 starts at 0000.


ends.
Time interval 2 starts at TIME1.

297-8021-351 Standard 05.02 May 2001

QTHRESH (continued)
Subfield or

ends.


TIME4 0 to 2400 End time for interval 4. Enter 2400, the time
in hours and minutes (HHMM) when time
interval 4 ends.
Datafill example
The following example shows sample datafill for table QTHRESH.
QTHRESH (end)
MAP display example for table QTHRESH
QNUM QCWN1 QCWF1 QCD1 TIME1 QCWN2 QCWF2 QCD2 TIME2

QCWN3 QCWF3 QCD3 TIME3 QCWN4 QCWF4 QCD4 TIME4
________________________________________________________
0 20 10 30 0600 15 10 80 1200
12 24 45 1200 24 45 60 2400
Table history
BCS36
A recommendation to datafill table QDEF before table QTHRESH was added.
297-8021-351 Standard 05.02 May 2001

QTTIDXH
Table name
ITOPS Queue Length Threshold High Traffic Table Index Table
Overview
The following table lists the International Traffic Operator Position System
(ITOPS) queue length threshold tables.
ITOPS queue length threshold tables
QTTIDXH 2798 ITOPS Queue Length Threshold High Traffic Table Index
QT0H to 2836A, B, C ITOPS Queue Length Threshold High Traffic Table Record
QT5H
QTTIDXL 2799 ITOPS Queue Length Threshold Low Traffic Table Index
QT0L to 2837A, B, C ITOPS Queue Length Threshold Low Traffic Table Record
QT5L
It is possible that more calls than can be handled by the ITOPS operator work
force is present at a given time in the ITOPS system. If this is the case, those
calls waiting to be processed are queued in an appropriate call waiting queue.
In ITOPS, there are six call waiting queues:

non-transfer queue
transfer 1 queue
transfer 2 queue
non-transfer recall queue
transfer 1 recall queue
transfer 2 recall queue
There is a limit on the total number of calls that can be queued in the ITOPS
system. This limit is controlled by an office parameter. If this limit is
exceeded, the call is deflected to a treatment.
There are also dynamically changing thresholds associated with the queueing
of calls. These thresholds are controlled by the system wide average work time
for the last 15 min period, the number of occupied positions (headset are
seated) in the system, and the number of calls currently queued in the system,
QTTIDXH (continued)
then the new threshold values for the next 15 min period are chosen. There are
four threshold values as follows:
CWONTHRESHOLD
When the number of calls in the call waiting queues is equal to
CWONTHRESHOLD value and a new call comes in, this call is put in the
queue and <CW> appears at the operators screen, at the In-Charge and
assistance positions. This causes the operators to speed up and handle these
waiting calls.
CWOFFTHRESHOLD
When an operator handles a call that was in the call waiting queues, and the
number of the calls in the queue is now equal to CWOFFTHRESHOLD,
<CW> is removed from the screens.
DEFLECTTHRESHOLD
When the number of calls in the call waiting queues is equal to threshold
DEFLECTTHRESHOLD, and a new call comes in, this new call is deflected
to a treatment and <CD> appears at the In-Charge and assistance positions. An
alarm also sounds in the office.
AWTINDEX
This value is used to find out which of the six queue threshold tables is taken
for the next 15 min period, according to the average work time (AWT) value
of the last 15 min period.
The Administration has the capability of setting these queue threshold values
using two sets of queue threshold tables: one for high traffic period and the
other for low traffic period. Each set contains seven tables. These high and
low table sets are required because at low time the customer must be willing to
wait in queue longer, but at high time the customer prefers calls to be handled
faster. Tables explained below are high traffic tables. Low traffic tables are
QTTIDXL, QT0L, QT1L, QT2L, QT3L, QT4L, QT5L and they have the same
ranges as high traffic tables.
At the top is the queue threshold table index table, QTTIDXH, which contains
only six tuples. There is a one-to-one correspondence between each of these
six tuples and each of six remaining tables: QT0H, QT1H, QT2H, QT3H,
QT4H, and QT5H. The only field in table QTTIDXH besides the key (0 to 5)
is the average work time (field AWT).
AWT for the last 15 min is compared with the AWT values in table QTTIDXH.
The index found maps the table that has the appropriate threshold values to be
used for the next 15 min period.
297-8021-351 Standard 05.02 May 2001

QTTIDXH (continued)
Data stored in these queue threshold tables, together with information on

average work time and occupied positions, are used to determine whether a
call arriving at an ITOPS switch is to be queued, or deflected to announcement.
It is also used to turn calls waiting or deflected display on or off.
The Administration also has an overriding control as to which queue threshold

table will be used via input at the FADS device.
The traffic may vary according to the environment that is being served by
DMS.
The following office parameters in table OFCENG are used to specify the start
times for the high and low traffic periods for the office:
ITOPS_HIGH_TRAFFIC_START_TIME
ITOPS_LOW_TRAFFIC_START_TIME
These office parameters represent the start time of the high and low traffic
periods for the office, respectively. The range of these parameters is 0 to 23.
For example, if the current time is the time specified in office parameter
ITOPS_HIGH_TRAFFIC_START_TIME, the queue threshold table set for
the high traffic period is used and vice versa. If only one set of tables is
required, both parameters can be filled as 0 (zero). In this situation, only low
traffic tables are active all the time.
Table QTTIDXH is used to define which one of the six Queue Length
Threshold High Traffic Tables (QT0H, QT1H, QT2H, QT3H, QT4H, or
QT5H) is to be used in the next 15 min based on the AWT in the preceding 15
min.

There is no requirement to datafill other tables prior to table QTTIDXH.
Table size
0 to 6 tuples
QTTIDXH (end)
Datafill
The following table lists datafill for table QTTIDXH.
Field descriptions
Subfield or
QTTBL numeric ITOPS queue length threshold high traffic

(0 to 5) table. Enter the number corresponding to
tables QT0H to QT5H respectively.
AWT numeric Average work time. Enter the length of time,

(1 to 32766) in seconds, used to handle the average call.
The entries for average work time (AWT)
must be entered in table QTTIDXH in
ascending numerical order.
Datafill example
The following example shows sample datafill for table QTTIDXH.
MAP display example for table QTTIDXH
QTTBL AWT
________________________________________________________
0 25
297-8021-351 Standard 05.02 May 2001

QTTIDXL
Table name
ITOPS Queue Length Threshold Low Traffic Table Index Table
Table QTTIDXL is used to define which one of the six queue length threshold
low traffic tables (QT0L, QT1L, QT2L, QT3L, QT4L, or QT5L) is to be used
in the next 15 min based on the average work time (AWT) in the preceding 15
min.

There is no requirement to datafill other tables prior to table QTTIDXL.
Table size
0 to 6 tuples
Datafill
The following table lists datafill for table QTTIDXL.
Field descriptions
Subfield or
QTTBL numeric ITOPS queue length threshold low traffic

(0 to 5) table. Enter the number corresponding to
tables QT0L to QT5L respectively.
AWT numeric Average work time. Enter the length of time

(1 to 32766) in seconds, used to handle the average call.
The entries for average work time (AWT)
must be entered in table QTTIDXL in
ascending numerical order.
Datafill example
The following example shows sample datafill for table QTTIDXL.
MAP display example for table QTTIDXL
QTTBL AWT
________________________________________________________
0 25
R2BILSRV
Table name
R2 Billing Service Table
Table R2BILSRV reroutes Integrated Business Network (IBN) R2 calls during
translations to a Traffic Operator Position System (TOPS) operator based on
the billing category of the call.
The routing of an IBN R2 call is determined from the receiving party digits as
dialed by the calling party. Once a route is identified, a terminating node
requests the calling party digits and the billing category. Once the billing
category is received, table R2BILSRV is checked by the system to determine
if a new route is set for this billing category. If field SEL (selector) is set to
NONE, the route is not changed and the call continues. If field SEL is set to
TOPS, the route is changed to TOPS and the call is sent back to the router to
determine a new terminator.

There is no requirement to datafill other tables prior to table R2BILSRV.
Table size
0 to 19 tuples
Table size is dynamically determined by the number of tuples added in field

BILLCAT.
297-8021-351 Standard 05.02 May 2001

R2BILSRV (continued)
Datafill
The following table lists datafill for table R2BILSRV.
Subfield or
BILLCAT ANI_FAILURE, Billing category. Enter up to 19 types of billing

ATME, COIN, DATA, category. See table TOPS and table SIGACT
FREE_CALL, for further descriptions of the categories. If
LOCAL_COIN less than 19 types are required, end the list
MTC_EQ, OPER, with a $ (dollar sign).
OPER_INTL, PBX,
PRIORITY, Note: All calling categories are ignored when
REGULAR, received by the Traffic Operator Position
REGULAR_INTL, System (TOPS) except the ATME category.
SHARED_1, ATME is not supported by TOPS and must be
SHARED_2, taken down if such a call is routed to TOPS.
SHARED_3,
ANI_FAILURE (automatic number
SPARE_CAT1,
identification [ANI] failure)
SPARE_CAT2,
TIME_AND_CHG, ATME (call originated by automatic test
TOLL_COIN, or and measurement equipment)
UNIT_FEE_COIN
COIN (coin)
(up to 19 entries)
DATA (data call)
Note: The DATA category prevents all

double connections to the call for the call's
duration. Data is being transmitted and
break-in tones or multiple voice connections
cause transmission errors.
FREE_CALL (free call-handled the same
as a REGULAR call but call is marked as
NOAMA)
LOCAL_COIN (call originated from local
public phone)
MTC_EQ (maintenance equipment)
R2BILSRV (continued)
Subfield or
BILLCAT Note: MTC_EQ calls are any calls

(continued) originating from the MAP (maintenance and
administration position) or by test equipment.
OPER (operator)
OPER_INTL (international operator
originated call)
PBX (call from a private branch
exchange)
PRIORITY (priority subscriber)
REGULAR (regular subscriber or
subscriber's category is unknown)
REGULAR_INTL (international direct dial
call)
SHARED_1, SHARED_2, SHARED_3
(first, second, or third subscriber on a
party line)
SPARE_CAT1, SPARE_CAT2 (spare
categories)
TIME_AND_CHG (subscriber requested
time and charge)
TOLL_COIN (call originated from a long
distance public phone)
UNIT_FEE_COIN (unit fee coinbox call)
Note: TOPS does not differentiate between

the regular COIN phone and the
UNIT_FEE_COIN phone.
SEL NONE or TOPS Selector. Enter the type of selector. Enter

NONE if the route remains unchanged and
the call continues. Enter TOPS if the route is
changed to TOPS and the call is sent back to
the router for a new terminator.
Datafill example
The following example shows sample datafill for table R2BILSRV.
297-8021-351 Standard 05.02 May 2001

R2BILSRV (end)
MAP display example for table R2BILSRV
BILLCAT SEL
________________________________________________________
REGULAR NONE
Table history
BCS36
Entries LOCAL_COIN and TOLL_COIN were added to the field descriptions
for field BILLCAT.
BCS35
Table R2BILSERV was introduced.
R2PROT including FDCP
Table name
R2PROT
Register signaling systems number 2 (R2) use register signaling to transfer
information about a call between two ends of a trunk. R2 systems are
multifrequency compelled (MFC) systems that send tones in one direction and
return acknowledgement tones. The information transferred is described
within a protocol specification.
R2 signaling applies to the DMS-100 and DMS-200 international switches.
Table R2PROT is the head table for the R2 datafill. It provides the indexes into
the other R2 tables. Table R2PROT provides the definition of the mappings
and activity controllers for each protocol. Table R2PROT is accessed with the
protocol index from table TRKGRP and table TRKSGRP.
Table R2PROT is maintained and downloaded by central control (CC) and

used in the extended multiprocessor system (XMS)-based peripheral module
(XPM).
Different protocols can use the same indexes into R2 tables. New protocols
can be added using existing mappings of other protocols by adding a new tuple
to table R2PROT.
For related information refer to tables ACTSIG and SIGACT.
Flexible Digital CAS Platform

FDCP is a new value that is specified in the BASEPROT field of table
R2PROT.
The value datafilled in field BASEPROT selects a refinement of the table tuple.
A new refinement for R2PROT is associated with the new BASEPROT value
FDCP. This new FDCP refinement consists of two fields, a CATIDX field and
an OPTIONS field.
CATIDX Field
This field in the new FDCP refinement of R2PROT identifies data in table
CATCLASS. Table CATCLASS handles the billing and calling party category
activities for trunks associated with the tuple (via table TRKSGRP). This field
follows the existing BASEPROT field.
297-8021-351 Standard 05.02 May 2001

R2PROT including FDCP (continued)
OPTIONS Field
The options field is reserved for growth and provides no functionality in this
first release of FDCP. This field follows the new CATIDX field.

The following tables must be datafilled before table R2PROT including FDCP.
ACTCTL
ACTSIG
CATCLASS
SIGACT
For FDCP and NTR2P, the table CATCLASS is datafilled before FDCP tuples
in table R2PROT.
Table size
1 to 16 tuples
One tuple is permanently allocated for the NIL tuple, and a maximum of 15
tuples can be allocated using the table editor.
Each protocol is represented by one tuple.
Datafill
The following table lists datafill for table R2PROT including FDCP.
Subfield or
IDX alphanumeric Index

(1 to 8 Enter the index into table R2PROT.
characters)
PHASES see subfields Protocol phases

This field consists of subfields OGACTSIG,
ICACTSIG, OGSIGACT, and ICSIGACT. It
contains the phase change information for the
protocol.
There are 16 sets of four integers corresponding
to the indexes into tables SIGACT and ACTSIG
for outgoing and incoming trunks. If less than 16
sets are required, end the list of integers with a $
(dollar sign).
Note: 0 (zero) is used by the table software as

the index value NIL.
OGACTSIG 0 to 255 Outgoing actsig table index

Enter the index into table ACTSIG for outgoing
trunks.
ICACTSIG 0 to 255 Incoming actsig table index

Enter the index into table ACTSIG for incoming
trunks.
OGSIGACT 0 to 255 Outgoing sigact table index

Enter the index into table SIGACT for outgoing
trunks.
ICSIGACT 0 to 255 Incoming sigact table index

Enter the index into table SIGACT for incoming
trunks.
OGACTCT alphanumeric Outgoing actctl table index

L (1 to 8 Enter the index into table ACTCTL for outgoing
characters) trunks.
ICACTCTL alphanumeric Incoming actctl table index

(1 to 8 Enter the index into table ACTCTL for incoming
characters) trunks.
297-8021-351 Standard 05.02 May 2001

Subfield or
BASEDATA see subfield Base protocol data

This field consists of subfield BASEPROT and
refinements CATIDX, OPTION, and ACTIVITY.
The refined data required is based on the
BASEPROT entry.
BASEPROT alphanumeric Base protocol value

(1 to 8 Enter the base protocol. Each base protocol is
characters) country specific, except for FDCP.
FDCP
If the entry in subfield BASEPROT is NTR2PI or
NTR2P or FDCP, go to refinement CATIDX.
If the entry in this subfield is other than NTR2PI or
NTR2P or FDCP, no further datafill is required.
CATIDX alphanumeric Catclass index

(1 to 8 If the entry in subfield BASEPROT is NTR2PI or
characters) NTR2P or FDCP, datafill this refinement. Enter
the index name to access table CATCLASS to
obtain class of category information.
OPTIONS see subfields Options

If the entry in subfield BASEPROT is NTR2PI or
NTR2P, datafill this refinement. This field
consists of subfields OPTION and ACTIVITY.
No options are supported in the first release of

FDCP.
Enter $ for an empty options list.

Subfield or
OPTION DIG_B_ACT, Overdecadic-digit activity mappings

DIG_C_ACT, If the entry in subfield BASEPROT is NTR2PI or
DIG_D_ACT, NTR2P, enterl this refinement. Up to seven
DIG_E_ACT, options can be entered. If less than seven options
DIG_F_ACT, are required, end the list with a $ (dollar sign).
NOCLI_PHASE,
Enter NOCLI_PHASE to define categories which
QUICK_REQ,
are CLI request prohibited.
TARIFF_LEN,
or Enter data for QUICK_REQ to request the calling
TBI_ACT, party category (CPC) or digits before the system
collects all called party digits. This field has five
QUEUECHG
refinements. This field is an FDCP option.
Enter the definition used if a digit greater than
zero to nine is encountered. Otherwise, enter
TBI_ACT if a toll break in (TBI) can occur.
Enter TARIFF_LEN for Polish R2 register
signaling and datafill refinement TARIFF_LEN.
Option TARIFF_LEN must be datafilled if activity
RCV_TARIFF is datafilled in table ACTSIG for the
incoming trunk or in table SIGACT for the
outgoing trunk. TARIFF_LEN must be datafilled
when table R2PROT is first datafilled. This option
is only supported by the base protocol NTR2PI.
Enter QUEUECHG to allow the Charge Indicator
to be queued at times when the Charge Indicator
cannot be processed.
ACTIVITY ACC_MTC, Activity

CONGESTIN, Enter the R2 activity.
CONNECT_
If the entry in subfield OPTION is other than
CALL_CHG, or
DIG_B_ACT, DIG_C_ACT, DIG_D_ACT,
SUB_BUSY
DIG_E_ACT, DIG_F_ACT or TBI_ACT, enter
ACC_MTC (access code maintenance).
If the entry in subfield OPTION is TBI_ACT, enter
CONGESTION (congestion in network),
CONNECT_CALL_CHG (connect call charge), or
SUB_BUSY (subscriber line busy).
297-8021-351 Standard 05.02 May 2001

Subfield or
QUICK_REQ ANI_AFTER_1S Quick Request

T_REP,
Enter ANI_AFTER_1_DIG if the sytem requires
ANI_AFTER_1_
the calling number after collecting one
DIG,
called-party digit.
CAT_AFTER_1_
DIG, Enter CAT_AFTER_1_DIG if the system requires
CAT_AFTER_LA the CPC after collecting one called-party digit.
ST_DIG, or
Enter CAT_AFTER_LAST_DIG if the system
CAT_BLNG_IS_
requires the CPC after collecting all called digits.
CLNG
Enter CAT_BLNG_IS_CLNG if the calling and
billing categories are the same. The system can
provide the calling-party category (CPC) on the
billing category request. This refinement applies
to FDCP trunks.
TARIFF_ 1 to 9 Tariff digits

LEN If the entry in subfield OPTION is TARIFF_LEN,
datafill this refinement. Enter the number of tariff
digits that can be received on the outgoing trunk.
Datafill example
The following example shows sample datafill for table R2PROT including
FDCP.

MAP display examples for table R2PROT including FDCP
IDX
PHASES OGACTCTL ICACTCTL
BASEDATA
______________________________________________________________________
ISPRPROT
( 60 50 60 50) ( 61 51 61 51) $
ISRMFCG IRRMFCIC FDCP ISRCAT (QUICK_REQ CAR_ATER_1_DIGIT) $
IDX
PHASES OGACTCTL ICACTCTL
BASEDATA
______________________________________________________________________
ICAS
(200 0 200 0)$
OGFDCP ICFDCP
FDCP NIL $
Table history
MMP14
Added refinement NOCLI_PHASE to subfield OPTION in table R2PROT.
MMP13
Option QUICK_REQ and related refinements added to table R2PROT.
EUR009
Refinement FDCP added to table R2PROT.
APC010
Entry CONNECT_CALL_CHG added to option TBI_ACT.
297-8021-351 Standard 05.02 May 2001

R2PROT including FDCP (end)
BCS36
The following changes were made:
Options TARIFF_LEN and TBI_ACT added to subfield OPTION.
Refinements TARIFF_LEN and subfield ACTIVITY added.
BCS34
Table R2PROT introduced.
This section provides information on dump and restore procedures when
datafilling table R2PROT.
Dump and restore

To download option TARIFF_LEN, the international digital trunk controller
(IDTC), and PCM30 Digital Trunk Controller (PDTC) must be busied (BSY)
and returned to service (RTS) .
The FDCP refinement of table R2PROT requires no reformat actions. All

fields and field values that are valid and supported prior to introduction of
FDCP are valid and supported after the introduction of FDCP. All changes
introduced with FDCP apply only when the BASEPROT field in a R2PROT
tuple is datafilled as FDCP. Since the BASEPROT field cannot be datafilled to
FDCP in a pre-FDCP load, none of the changes introduced with FDCP apply
(to either the old or new sides) during an ONP from a pre-FDCP capable load
to a FDCP-capable load.
There is no requirement to populate new R2PROT tuples for FDCP over an

ONP.
RADR
Table name
Receiver Attachment Delay Recorder Table
The system generates test calls. The tests time the interval from the point of
original request for attachment to a receiver, to the time of connection.
Table RADR stores the number of test calls to originate each hour. The table
stores the two values of delay thresholds (lower and upper) in seconds.
The system displays the percentage of test calls delayed that surpass the lower
delay threshold on the network management MAP terminal.
The system also stores a peg count of the following information:

number of test calls that the system processed
number of test calls delayed that surpass the lower delay threshold
number of test calls delayed that surpass the upper delay threshold
The actual receiver attachment delay call rate is different in some events from
the call rate specified in field RADCALLR. Use the following equation to
calculate the actual rate:
A = [3600 / (b / c)]
where
A
is the actual receiver attachment delay call rate
b
is the lower threshold of 3600
c
is the value in field RADCALLR
If field RADCALLR is 1100 and field RADLDLYT is 3 the following

information is true:
A = [3600 / (3600 / 1100)]
A = 3600 / 3.27 (3.27 rounds to 3)
297-8021-351 Standard 05.02 May 2001

RADR (continued)
A = 1200
This information does not have an effect if the rate is 900, 1200, or 1800.
To disable the RADR test program at any time, set the number of test calls to 0.
Table RADR affects receivers. The table adds a tuple with a non-zero value
for field RADCALLR. This process sets up a competition with call processing
for receivers. The system provides a protection level of ENGPROT for table
RADR. The system cannot turn on the processes when the system a protection
level is present. The operating company can modify table RADR. To modify
the table, the company loads module ENGWRITE from the nonresident tape
and enters the command ENGWRITE ON.

You must enter data in the following tables after you enter data in table RADR:
RECEIVER
REASONS
Table size
0 to 10 tuples
RADR (continued)
Datafill
Datafill for table RADR appears in the following table.
Subfield or
RADKEY ATDRCVR Receiver attachment delay key. Enter a

ATDUKRCVD receiver attachment delay key. Descriptions
GTRCVR of these keys follow. These entries are not
DTUKRCVRD common language location identifiers (CLLI).
T300RCV These entries are keys to operational
KSR2IRCV measurements (OM) group RADR.
KSR2ORCV
ATDRCVR (audio tone detector)
MFRCVR
MF300RCV or ATDUKRCV (A-law audio tone detector
UTRCVR United Kingdom)
DGTRCVR (Digitone)
DTUKRCVR (A-law Digitone receiver
United Kingdom)
DT300RCV (Digitone for gateway
switches)
KSR2IRCV (for licensee use only)
KSR2ORCV (for licensee use only)
MFRCVR (multifrequency)
MF300RCV (multifrequency for gateway
switches)
UTRCVR (universal tone receiver)
Note: You can use UTRCVR as a key to

OMs group RADR. You must not enter
UTRCVR in table RADR.
RADCALLR 0 to 1800 Receiver attachment delay call rate. Enter

the number of test calls that originate each
hour.
297-8021-351 Standard 05.02 May 2001

RADR (end)
Subfield or
RADLDLYT 0 to 19 Receiver attachment delay lower delay

parameter. Enter the time, in seconds, of the
lower delay threshold.
RADUDLYT 0 to 20 Receiver attachment delay higher delay

parameter. Enter the time, in seconds, of the
upper delay threshold.
Datafill example
Sample datafill for table RADR appears in the following example.
The number of test calls to originate each hour is 900. The lower threshold is
the standard value of 3 s. The upper threshold is the standard value of 7 s.
MAP example for table RADR
RADKEY RADCALLR RADLDLYT RADUDLYT

________________________________________________________
MFRCVR 900 3 7
Table history
BCS36
Deleted option ATDARCVR in field RADKEY in BCS36, as table owner
advised.
RAO
Table name
TOPS Domestic RAO Codes Table
Table RAO is used to check the validity of 10-digit special" numbers. Table
RAO cannot be used to check the validity of revenue accounting office (RAO)
codes for the 14-digit calling cards. RAO codes for the calling cards must be
datafilled in table RAOCHECK so that the same RAO code is valid for one
type of number but not the other (that is, the 10-digit numbers but not the
14-digit numbers, or vice-versa). If the RAO code is valid for both types, it
must be datafilled in both table RAO and table RAOCHECK.
Table RAO is prepared by Northern Telecom from a file of valid RAO numbers
without a data form being prepared. At cutover or extension, however, table
RAO must be revised to incorporate recent changes to the master RAO list.

There is no requirement to datafill other tables prior to table RAO.
Table size
0 to 999 tuples
Datafill
The following table lists datafill for table RAO.
Field descriptions
Subfield or
RAOCODE 0 to 9 Revenue accounting office code . Enter the

(3 digits) revenue accounting office (RAO) number.
297-8021-351 Standard 05.02 May 2001

RAO (end)
Datafill example
The following example shows sample datafill for table RAO.
MAP display example for table RAO
RAOCODE
________________________________________________________
321
RAOCHECK
Table name
TOPS RAO Check Table
Table RAOCHECK is used with table NPACHECK to perform special digit
checks on credit card numbers.
Table RAO is used to check the validity of 10-digit special" numbers. Table
RAO cannot be used to check the validity of revenue accounting office (RAO)
codes for 14-digit calling cards. RAO codes for 14-digit calling cards must be
datafilled in table RAOCHECK. The same RAO code is valid for one type of
number but not the other (that is, the 14-digit number but not the 10-digit
number, or vice-versa). If the RAO code is valid for both types, it must be
datafilled in both table RAO and table RAOCHECK.
See table HOTLIST for related information.

The following tables must be datafilled before table RAOCHECK.
HOTLIST
CHKDIGIT
RAO
Table size
0 to 999 tuples
Datafill
The following table lists datafill for table RAOCHECK.
Field descriptions
Subfield or
RAOCODE 0 to 9 Revenue accounting office code . Enter the

(3 digits) revenue accounting office (RAO) code for the
credit card number.
297-8021-351 Standard 05.02 May 2001

RAOCHECK (end)
Datafill example
The following example shows sample datafill for table RAOCHECK.
MAP display example for table RAOCHECK
RAOCODE
________________________________________________________
727
RASLAPPL
Table name
Robust Application Session Layer Application Table
Switching units with feature package NTX347AA (DMS Base Data
Communication CC Software) have table RASLAPPL. Table RASLAPPL
requires feature package NTX273AA (Multi Protocol Controller BX.25) to
function.
Table RASLAPPL provides a generic application layer interface to different

data communications facilities. These facilities include multiprotocol
controller (MPC) X25ORIG or X2580 Northern Telecom X.25 devices.
Table RASLAPPL defines and governs the mapping between different

application network connections (NC) and physical data links. The robust
application session layer (RASL), provides a single interface to support the
network management (NWM) system.
Table RASLAPPL serves as the black box interface between applications or

data communications systems. The system handles events and conditions at
the applications level. The RASL interface reports any errors to the
applications. The application that uses the interface determines the conditions
that use the RASL interface activated utilities.
Table RASLAPPL also defines the RASL network connections that the
automatic file transfer (AFT) uses to transfer files to a remote processor. The
AFT is an application system. This system transfers Device Independent
Recording Package (DIRP) files. The AFT transfers the files through the use
of the following:
data access information system (DAIS)
safe store tap (SST)
the RASL
The AFT can interface with the transport layer interface (TLI) instead of
RASL. The AFT can run over Ethernet local area network (LAN) and X.25.

You must enter data in the following tables before you enter data in table
RASLAPPL.
MPC
NX25
297-8021-351 Standard 05.02 May 2001

RASLAPPL (continued)
MPCLINK
MULTILNK
You must enter one of the following tables before table RASLAPPL. The
entry of the table depends on the type of application that you use.
MPC (configures MPC cards)
MPCLINK (configures MPC links using X250ORG or X2580 cards)
Table GASINFO must be datafilled after table RASLAPPL.
Table size
2 to 30 tuples
Table RASLAPPL requires access to a minimum of two links. You can enter
a maximum of 30 network connections in table RASLAPPL.
Datafill
Datafill for table RASLAPPL appears in the following table.
Subfield or
NETCON see subfield Network connection.

This field contains subfield NETCON.
NETCON alphanumeric Network connection.

(1 to 16 Enter the identifier for the network
characters) connection.
Subfield or
APTYPE ACDIN Application type. Enter the application type.

ACDOUT The correct range of entries for this field
AFT TESTIN depends on the feature package of the
or TESTOUT operating company.
The ACDIN and ACDOUT are Automatic Call
Distribution (ACD) applications that send
ACD reports. The ACD applications are in
feature package NTX494AA (Automatic Call
Distribution).
The AFT provides automatic file transfer of
DIRP files. The AFT provides automatic file
transfer through RASL. The AFT is in feature
package NTXV20AA [DMS-100 Automatic
File Transfer (AFT).
The TESTIN and TESTOUT are test
applications. These applications are for the
use of Northern Telecom only.
BUFFSIZE 2 to 4096 Buffer size.

Enter the maximum number of bytes
expected in a message received from the far
end.
297-8021-351 Standard 05.02 May 2001

Subfield or
NUMBUFFS 1 to 128 Number of buffers.

(increases by Enter the number of buffers allocated. The
power of 2) value must be larger for high traffic
applications.
ACSINFO MPCPVC Access information.

MPCSVC Enter the access information. The correct
RMLP RSLP range of selectors for this field depends on the
SIPC or TLI feature packages of the operating company.
Enter MPCPVC (MPC permanent virtual
circuit [PVC]). Enter data in refinements
MPCNO, LINKNO, and PVCLCN in the
section ACSINFO = MPCPVC.
Enter MPCSVC (MPC switched virtual circuit
[SVC]). Enter data in refinements MPCNO,
LINKNO, DNA, and USERDATA in the
section ACSINFO = MPCSVC.
Enter RMLP (RASLAPPL multilink protocol).
Enter data in refinement MLGID in the section
ACSINFO = RMLP.
Enter RSLP (RASLAPPL single link protocol).
Enter data in refinement LINKID in the section
ACSINFO = RSLP.
Enter SIPC (support operating system [SOS]
interprocess communication). Additional
refinements do not require datafill.
Enter TLI (transport layer interface). Enter
data in refinements COMMODE and
WELLKWNADDR in the section
ACSINFO = TLI.
ACSINFO = MPCPVC
If the entry in field ACSINFO is MPCPVC, enter data in refinements MPCNO,
LINKNO, and PVCLCN. A description of this process appears in the
following table.
Subfield or
MPCNO 0 to 255 Multiprotocol controller number.

Enter the MPC number. Table MPCLINK must
contain a previous entry for the MPC number.
LINKNO 0 to 3 Link number.

Enter the link number. Table MPCLINK must
contain a previous entry.
PVCLCN 0 to 255 Permanent virtual circuit logical channel number.

Enter the PVC logical channel number.
ACSINFO = MPCSVC
If the entry in field ACSINFO is MPCSVC, enter data in refinements MPCNO,
LINKNO, DNA, and USERDATA. A description of this process appears in the
following table.
Subfield or
MPCNO 0 to 255 Multiprotocol controller number.

Enter the MPC number. A previous entry for
this entry must be table MPCLINK.
LINKNO 0 to 3 Link number.

Enter the link number. A previous entry for
this entry must be in table MPCLINK.
297-8021-351 Standard 05.02 May 2001

Subfield or
DNA numeric Data network address.

(0 to 9) Enter the digits that represent data network
(a maximum address (DNA).
of 15
For outgoing applications, field DNA
binary-code)
represents the remote node address of the
decimal digits
location for the connection.
For incoming applications, field DNA
represents the only node address to request,
establish, and accept a connection.
USERDATA alphanumeric User data.

(a maximum Enter the datafill that identifies each
of 32 end-to-end connection. The customer can
characters) configure this data.
Note: For DATAPAC and NTELPAC, there is

a limit of eight digits in field DNA.
ACSINFO = RMLP
If the entry in field ACSINFO is RMLP, enter data in refinement MLGID. A
description of this process appears in the following table.
Subfield or
MLGID 0 to 15 Multilink group.

Enter the multilink group.
ACSINFO = RSLP
If the entry in field ACSINFO is RSLP, enter data in refinement LINKID. A
description of this process appears in the following table.
Subfield or
LINKID 0 to 29 Link identifier.

Enter a link identifier. Table MPCLINK must
contain a previous entry for LINKID.
ACSINFO = TLI
If the entry in field ASCINFO is TLI, enter data in refinements COMMMODE
and WELLKWNADDR. A description of this process appears in the
following table.
Subfield or
COMMMODE C or S Communication mode.

This subfield determines if the enhanced AFT
run over the Ethernet LAN acts as a client or
a server.
The S indicates server and C indicates client.
The S is the default.
For field transfer to the DMS Accounting
Traffic Analysis System (DATAS), AFT must
be a server.
WELLKWNA- see subfields Well-known address.

DDR This field contains subfields PORT and
IPADDR. If AFT is a client, the well-known
address is a completely specified
transmission control protocol address of the
far-end processor.
If AFT is a server, the well-known address is
a completely specified address of the AFT
process in DMS.
PORT 0 to 32767 Port.

The AFT has a maximum of three sessions.
Each session has a different port number.
For file transfer with DATAS, port numbers
are predetermined. For example, 30 000 for
call detail recording (CDR) stream and 30 001
for trunk operational measurement
(TRK_OM) stream.
Use of the port number in table RASLAPPL
can occur only if AFT acts as a client.
PADDR see subfields Internet protocol address.

This refinement contains subfields IPADDR1,
IPADDR2, IPADDR3, and IPADDR4.
297-8021-351 Standard 05.02 May 2001

Subfield or
PADDR1 0 to 255 Internet protocol address 1.

If AFT acts as a server, enter the internet
protocol address of the DMS. If AFT acts as
a client, enter the internet address of the
far-end processor.

far-end processor.

far-end processor.

far-end processor.
Datafill example
Sample datafill for table RASLAPPL appears in the following example.
MAP example for table RASLAPPL
NETCON APTYPE BUFFSIZE NUMBUFFS
ACSINFO
________________________________________________________
PRIMARYCDR AFT 2048 4

MPCPVC 1 3 1
RASLAPPL (end)
This section describes limits that apply to the entry of data in table
RASLAPPL.
Limits
You can delete or change tuples in table RASLAPPL. The use of the MAP
(maintenance and administration position) allows you to perform command
interpreter (CI) commands DELETE and CHANGE. You can perform
commands after you perform the CI command RASLSTOP on the altered
datalink. The command RASLSTOP does not permanently disable the
datalink. You can change or delete the information. After a datalink changes,
you must perform the command RASLSTART to enable the datalink.
The only fields that can change, if the network connection is closed, are
ACSINFO, BUFFSIZE, or NUMBUFFS.
297-8021-351 Standard 05.02 May 2001

RATEAREA
Table name
RATEAREA
Feature AU3279, LINEATTR Servord Enhancements, split table LINEATTR
(Line Attribute) into three tables to make data management easier:
LINEATTR
RATEAREA
XLAPLAN
Table RATEAREA receives initial datafill in a one night process (ONP) from
table LINEATTR. If a specific tuple from table LINEATTR results in a tuple
that exists in table RATEAREA, the tuple is not added to table RATEAREA
and the RATEAREA key copies back to table LINEATTR. If a specific tuple
from table LINEATTR does not result in a tuple that exists in table
RATEAREA, the tuple is added to table RATEAREA and the RATEAREA
key copies back to table LINEATTR.
Note: You can delete tuples in table RATEAREA that other tables do not
reference.
The LINEATTR Compression Tool feature (59017776) checks for duplicate

tuples during the ADD, CHA, and REP commands. A warning message
appears before the confirmation to provide an alert of a duplicate tuple. The
message only generates if table OFCVAR parameter
XLAPLAN_RATEAREA_SERVORD_ENABLED (XRSE) is set to
MANDATORY_PROMPTS. This warning does not prevent datafill validation.

Enter datafill into the tables that follow before you datafill table RATEAREA:
LATANAME
LCASCRN or LCAINFO (if using LCA 6-digit screening)
MRSNAME
LGASCRN (if using LCAINFO)
DPCTSCRN (if using LCAINFO)
Table size
Up to 32 000 tuples
RATEAREA (continued)
Datafill
The following table lists datafill for the RATEAREA table.
RTAIDX alphanumeric (up to Rate area log key. Enter index into table
16 characters) RATEAREA.
LCANAME alphanumeric (up to 8 Local calling area screening name. If you

characters) or NLCA require screening of local central office
codes (NNX), enter the local calling area
screening name assigned to the
LINEATTR key. Enter a local calling area
screening name provisioned in either
table LCASCRCN or LCAINFO. If
screening of local NNX codes is not
required, enter NLCA.
MRSA alphanumeric (up to 8 Message rate service area. If the

characters) or NIL switching unit is equipped to provide
multiunit message rate (MUMR) services
and MUMR billing records are required
for calls to numbers resulting in a type of
call of NP (no prefix), enter a message
rate service area (MRSA) name as
datafilled in table MRSANAME field
MRSA. If MUMR billing records are not
required, enter NIL.
Calls to numbers resulting in a type of call
other than NP result in normal direct dial
(DD) or equal access (EA) billing records
instead of MUMR billing records.
A line does not have to be a message
rate line, as indicated by its LCC, to be a
multiunit message rate line.
297-8021-351 Standard 05.02 May 2001

RATEAREA (end)
LATANM alphanumeric (up to 8 Local access and transport area name.

characters) Enter the name of the local access and
transport area (LATA) assigned to the
LINEATTR key.
ADMININF alphanumeric (up to Administration information. Enter any

32 characters) string containing alphabetic characters,
numeric characters, or underscores up to
32 characters. This entry provides a short
explanation or note regarding the use of
the LINEATTR key. The operating
company defines the content of this
entry.
Datafill example
The figure that follows shows sample datafill for table RATEAREA.
MAP display example for table RATEAREA
RTAIDX LCANAME MRSA LATANM ADMININF

________________________________________________________
L613_LATA1_0 L613 NIL LATA1 $
Table history
NA014
The LINEATTR Compression Tool feature (59017776) checks for duplicate
tuples during the ADD, CHA, and REP commands. A warning message
appears before the confirmation to provide an alert of a duplicate tuple. The
message only generates if table OFCVAR parameter
XLAPLAN_RATEAREA_SERVORD_ENABLED (XRSE) is set to
MANDATORY_PROMPTS.
LWW0006
Feature 59010108, Line Data and SERVORD Fold-in, incorporated table
RATEAREA into DMS-100 Wireless.
NA011
Table RATEAREA was introduced.
RATEMOD
Table name
ITOPS Rating Charge Calculation for Time-Day Discount and Surcharge
Table
Table RATEMOD is used by the international Traffic Operator Position
System (ITOPS) software as a method of defining the discount or surcharge
added to or subtracted from the charges for combinations of schedule name
and charge modification set factors.
For related information, refer to table ATRIMOD.

The following tables must be datafilled before table RATEMOD.
MODSET
SCHNAME
Table size
0 to 64 tuples
Datafill
The following table lists datafill for table RATEMOD.
Subfield or
SCHNAME alphanumeric Schedule name Enter a schedule name that

(1 to 16 is a valid value in field SCHNAME of table
characters) SCHNAME.
297-8021-351 Standard 05.02 May 2001

RATEMOD (continued)
Subfield or
DISCAREA see subfield Discount area This field consists of subfield

MODTYPE and refinements.
MODTYPE PCENT or Rate modification type

QUOTED
Enter PCENT if the values in fields
VALUE1 to VALUE8 are expressed in
percentages and datafill refinements
RPSB, MODINP, SENSE1, VALUE1,
SENSE2, VALUE2, SENSE3, VALUE3,
SENSE8, and VALUE8.
Enter QUOTED to apply the time period
subdivision in table MODSET as an
attribute. The rating system continues to
process the call in the same manner it
would for any other call tagged with an
attribute. Datafill refinement RPSB.
In BCS36, value TIME was removed;
however, the functionality of time
modifications can be achieved with quoted
discounts by datafilling a new rating data set
which contains different initial and
subsequent periods for the desired period.
RATEMOD (continued)
MODTYPE = QUOTED
If the entry in subfield MODTYPE is QUOTED, datafill refinement RRSB as
shown below.
Subfield or
RPSB Y or N Rate period specific billing algorithm Enter Y

(yes) to indicate that the rate period specific
billing algorithm is used in calculating charges
as follows:
A call that starts in one rate period and
ends in another uses the discount
applicable in the first rate period on the
first part of the call, and the discount
applicable in the second rate period on
the second part of the call.
If subfield MODTYPE is QUOTED, RPSB is
set to Y.
Enter N (no) if the rate period specific billing
algorithm is not used and the first discount is
used for the entire call.
MODTYPE = PCENT
If the entry in subfield MODTYPE is PCENT, datafill refinements RPSB,
MODINP, SENSE1, VALUE1, SENSE2, VALUE2, SENSE3, VALUE3,
297-8021-351 Standard 05.02 May 2001

RATEMOD (continued)
SENSE4, VALUE4, SENSE5, VALUE5, SENSE6, VALUE6, SENSE7,

VALUE7, SENSE8, and VALUE8 as shown below.
Subfield or
RPSB Y or N Rate period specific billing algorithm Enter Y

to indicate that the rate period specific billing
algorithm is used in calculating charges as
follows:
A call that starts in one rate period and
ends in another uses the discount
applicable in the first rate period on the
first part of the call, and the discount
applicable in the second rate period on
the second part of the call.
If subfield MODTYPE is PCENT or TIME,
RPSB is set to Y.
Enter N to indicate that the rate period specific
billing algorithm is not used and that the first
discount is used for the entire call.
MODINP Y or N Modify initial periodIf subfield MODTYPE is

TIME, enter Y to indicate that the discount
applies to the combined initial and
subsequent charges.
Enter N to indicate that the discount applies to
the subsequent charges only.
SENSE1 DISC or SUR Rate modification sense 1 This field is used if

field MOD1 to MOD8 in table MODSET is
equal to M1. Enter DISC to indicate a discount
or SUR to indicate a surcharge.
RATEMOD (continued)
Subfield or
VALUE1 0 to 100 Rate modification value 1 This field is used if

equal to M1.
If subfield MODTYPE is PCENT, the entry is
the percentage surcharge or discount.
If subfield MODTYPE is TIME, the entry is the
time in minutes that the recall period is
adjusted.
If field MODINP is Y, the entry is the time in
minutes that the initial period is adjusted.

equal to M2. DISC indicates a discount. SUR
indicates a surcharge.

equal to M2.
adjusted.
If MODINP is Y, the entry is the time in
minutes that the initial period is adjusted.

equal to M3. DISC indicates a discount; SUR
297-8021-351 Standard 05.02 May 2001

RATEMOD (continued)
Subfield or

equal to M3.
adjusted.
If MODINP is Y, the entry is the time the initial
period is adjusted.

VALUE4 0 to 100 Rate modification value 4This field is used if

equal to M4.
adjusted.
period is adjusted.
SENSE5 DISC or SUR Rate modification sense 5

This field is used if field MOD1 to MOD8 in
table MODSET is equal to M5. DISC indicates
a discount; SUR indicates a surcharge.
RATEMOD (continued)
Subfield or

equal to M5.
adjusted.
period is adjusted.

VALUE6 0 to 100 Rate modification value 6This field is used if

equal to M6.
adjusted.
period is adjusted.
SENSE7 DISC or SUR Rate modification sense 7. This field is used if

297-8021-351 Standard 05.02 May 2001

RATEMOD (continued)
Subfield or

equal to M7.
adjusted.
period is adjusted.


equal to M8.
adjusted.
period is adjusted.
Datafill example
The following example shows sample datafill for table RATEMOD.
RATEMOD (end)
MAP display example for table RATEMOD
SCHNAME DISCAREA
MODLTYPE RPSB MODINP SENSE1 VALUE1 SENSE2 VALUE2 SENSE3 VALUE3
SENSE4 VALUE4
SENSE5 VALUE5 SENSE6 VALUE6 SENSE7 VALUE7
SENSE8 VALUE8
_______________________________________________________________________
SCHED3 PCENT Y Y DISC 0 DISC 1 DISC 1

DISC 4 +
DISC 0 DISC 0 DISC 1
DISC 2 $
Table history
BCS36
Removed value TIME in field MODTYPE per feature AJ1901 in functionality
Global Operator Services Rating, GOS00001.
297-8021-351 Standard 05.02 May 2001

RBKMAP
Table name
TOPS Rate Break Map Table
Table RBKMAP is used to list the rate break sets used by each rate schedule.
Datafill form 2750W (Rate Break Set Worksheet) and transfer the appropriate
entries to this form.
RBKMAP to be mass-table-controlled. In other words, the feature permits the
changes for the table into table RBKMAPI, and then, when all the required
changes are entered, swap the contents of table RBKMAP with table
RBKMAPI.
Overseas Operator Center (OOC):

Table RBKMAP provides the rate break number corresponding to the schedule
name for the type of call (station or person) and the call origination day of the
week name.

The following tables must be datafilled after table RBKMAP:
DCOUNT
RBKSET
SCHED
SCHNUM
Table size
The size of table RBKMAP is determined by the value in field SIZE in table
SYSDATA for table RBKMAP.
RBKMAP (continued)
Datafill
The following table lists datafill for table RBKMAP.
Field descriptions
Subfield or
SCHNAME alphanumeric Schedule name. Enter the schedule name as

(1 to 17 previously datafilled in table SCHED.
characters)
SSUN 0 to 63 Rate break set for station-to-station Sunday

calls. Enter the rate break set for
station-to-station Sunday calls for the
schedule (copied from the worksheet).
SSAT 0 to 63 Rate break set for station-to-station Saturday

calls . Enter the rate break set for
station-to-station Saturday calls for the
SWKD 0 to 63 Rate break set for station-to-station weekday

station-to-station weekday calls for the
PSUN 0 to 63 Rate break set for person-to-person Sunday

person-to-person Sunday calls for the
PSAT 0 to 63 Rate break set for person-to-person Saturday

person-to-person Saturday calls for the
PWKD 0 to 63 Rate break set for person-to-person weekday

person-to-person weekday calls for the
297-8021-351 Standard 05.02 May 2001

RBKMAP (end)
Datafill example
The following examples show sample datafill for table RBKMAP.
MAP display example for table RBKMAP
SCHNAME SSUN SSAT SWKD PSUN PSAT PWKD

________________________________________________________
SAMPLESCH 1 1 2 1 3 2
The second example shows datafill for the Caribbean Expansion Plan (CEP)
International TOPS (ITOPS).
The values SSUN, SSAT, and SWKD are for station paid calls on Sunday,
Saturday, and a weekday, respectively. The values PSUN, PSAT, and PWKD
are for person paid calls on Sunday, Saturday, and a weekday, respectively.
As shown in this example, the rate break set to Canada is the same for
Saturdays and weekdays but differs for Sundays. Calls to the USA are subject
to a different rate break set on Saturdays, Sundays, and weekdays, but local
calls only have one rate break set regardless of the day of the week.
MAP display example for table RBKMAP
SCHNAME SSUN SSAT SWKD PSUN PSAT PWKD

________________________________________________________
CANADA 1 9 9 1 9 9
USA 1 3 9 1 3 9
LOCAL 4 4 4 4 4 4
RBKMAPI
Table name
TOPS Rate Break Map Inactive Table
RBKMAP to be mass-table-controlled. In other words, the feature permits the
changes for the table into table RBKMAPI, and then, when all the required
changes are entered, swap the contents of table RBKMAP with table
RBKMAPI.
Refer to table RBKMAP.

Table size
Datafill
Datafill example
297-8021-351 Standard 05.02 May 2001

RBKSET
Table name
TOPS Rate Break Set Table
Overview
The following table lists all the Traffic Operator Position System (TOPS) rate
break tables.
TOPS rate break tables
------ 2750W Rate Break Set Worksheet
RBKSET 2750A, B Rate Break Set Table Record
RBKMAP 2751A, B Rate Break Map Table Record
The 24 h of a day are divided into rate periods, the end of each being specified
by a rate break. The discounts for each rate period, if any, are also specified.
Each set of time division and discounts constitutes a rate break set.
A rate schedule can have up to six different rate break sets: for station-Sunday,
-Saturday, -weekday, and person-Sunday, -Saturday, and -weekday.
Different rate schedules can share the same rate break sets. In DMS, up to 63
different rate break sets are allowed.
One worksheet (2750W) and two forms are provided. Worksheet 2750W is
used by the operating company to identify the unique rate break sets for each
schedule. These unique sets are then listed in form 2750A and B. Forms
2751A and B are then used to list the rate break sets associated with each
schedule. Form 2750W does not need to be submitted to Northern Telecom.
See the section Rate break set worksheeet for further information on the rate
break set worksheet.
Caribbean expansion plan (CEP) International TOPS (ITOPS)

Calls requiring operator assistance result in a charge to the customer that is
calculated by a downstream process using the call information (for example,
call type, destination, answer time, and duration of call).
RBKSET (continued)
There are cases, however, where the charges for a call must be quoted to the
customer. This is true for the following call types:
hotel calls
coin calls
calls requiring time-and-charges quote
In all three cases, the ITOPS system calculates the charges for the call. For
hotel calls, these charges are reported to the hotel billing information center
(HOBIC) for quoting; in the latter two cases, the operator quotes the charges.
CEP dialing plan

The dialing plan for the Caribbean islands is based on the North American plan
(NPA-NXX-XXXX). The islands have numbering plan area (NPA) 809, with
each island having one or more unique NXX associated with it.
CEP ITOPS rating zones

The following terminology is used within this document to define the different
CEP ITOPS rating zones:
Local
Calls completed within the same rate zone as the calling customer (calls within
the same NXX are always considered to be in the local rate zone)
Domestic
Calls completed within NPA 809 but to an NXX in a different rate zone as the
calling customer
North American
Calls completed from NPA 809 to any destination based on the NPA-NXX
dialing plan (other than domestic calls)
International (or Overseas)

Calls completed from NPA 809 to a foreign country not based on the
NPA-NXX dialing plan (outside World Zone 1)
CEP call origination time and day

Both the date and the time of day can have an effect on the charge calculation
for a call.
First the date is checked to see whether it is a holiday. This is done by

verifying whether the date falls on one of the defined holidays in table
HOLDAY. If the date is a holiday, table HOLTRT is accessed to see whether
this holiday affects the rate schedule for this call. If a value is not found in
297-8021-351 Standard 05.02 May 2001

RBKSET (continued)
table HOLDAY, the holiday does not affect charges applicable to the rate
schedule.
If a holiday is found to apply to the rate schedule, the treatment specifies that
the call is treated as if it originated on Saturday or Sunday (as specified).
Once the origination date has been modified to reflect the holiday treatment (if
necessary), table RBKMAP is accessed to determine the rate break set that
applies to the call based on the day of the week (weekday, Saturday, or Sunday)
and the method of billing (station or person). This rate break set is later used
to determine what discount applies to the call. Therefore, a different rate break
set must be associated with any origination day that must be treated differently.
Once a rate break set is determined, the date is no longer needed in the charge
calculation. However, the origination time of the call is used to determine the
actual rate break within the applicable rate break set. The rate breaks are
associated with a rate break set in table RBKSET. A maximum of 63 rate
break sets can exist, with a maximum of 8 rate breaks in a rate break set.
The rate break identifies the discount that applies to the call, based on the
origination time of the call. This discount is an index into another table, table
DCOUNT, that maps the rate schedule to the applicable discounts for that
schedule. A maximum of six discounts can be specified for a schedule. It is
also possible to specify whether discounts apply to the initial period as well as
to the overtime periods (specified discounts always apply to the overtime
periods, but do not always apply to the initial period).
Rate break set worksheet

The rate break set worksheet is used by the operating company to identify
unique rate break sets. The worksheet ties in closely with the two tables in
forms 2750 and 2751. Once this worksheet is completed, the other two forms
can be filled out easily.
The operating company examines its rating structure and lists the rate break set
for the six different categories shown (SSUN, SSAT, SWKD, PSUN, PSAT,
and PWKD [there is no distinction between coin and non-coin calls]). The rate
break sets are then compared, and identical ones are assigned the same rate
break set number. The same procedure is performed for all schedules, but the
comparison must be made with all assigned unique rate break sets.

Table DCOUNT must be completed before completing this worksheet, since
fields RBK1 to RBK8 must be filled with a discount factor.
RBKSET (continued)
Datafill (worksheet)
Field names, subfield names, and valid data ranges for the rate break set
worksheet are described below.
Field descriptions (worksheet) (Sheet 1 of 4)
Subfield or
SCHNAME alphanumeric Schedule name. Enter the name of the rate

(1 to 17 schedule as previously defined in table
characters) SCHNUM.
RBKTYPE PSAT, PSUN, Rate break set type. Enter the rate break set
PWKD, type as follows:
SSAT, SSUN,
PSAT (person-to-person Saturday)
SWKD
PSUN (person-to-person Sunday)
PWKD (person-to-person Weekday)
SSAT (station-to-station Saturday)
SSUN (station-to-station Sunday)
SWKD (station-to-station Weekday)
Each of the above can have a different rate
break set (field RBKSET).
RBK1 ND or D1 to Discount factor. This entry points to fields D1

D6 to D6 in table DCOUNT. If there is no
discount for the rate period, enter ND. If the
discount shown in D1 Quoted table is used in
table CHARGE, enter D1 and so on. When
fields TIME1 to TIME8 = 0, RBK1to RBK8=
ND.
297-8021-351 Standard 05.02 May 2001

RBKSET (continued)
Subfield or
TIME1 0000 to 2400 Rate break time . Enter the time at the end of
a rate break period.
Field TIME1 denotes the end of the first rate
break after midnight. Field TIME2 is the next
and so on. If less than eight rate breaks are
required (for example, only fields TIME1
through TIME3 need to be datafilled for three
rate breaks), the last rate break, (TIME4),
must be entered as 2400. If there are eight
rate periods, the last rate period is assumed
to go from TIME8 to midnight and have a
discount of RBK1; that is, a rate break set
always terminates at midnight.
The entries in fields TIME1 to TIME8 must be
unique values within a rate break set (field
RBKSET).
Enter 0 (zero) for unassigned fields.
Time must be in ascending order.

ND.
TIME2 0000 to 2400 Rate break time. Enter the time at the end of
a rate break period. See additional notes in
field TIME1.

ND.
field TIME1.
RBKSET (continued)
Subfield or

ND.
field TIME1.

ND.
field TIME1.

ND.
field TIME1.

ND.
297-8021-351 Standard 05.02 May 2001

RBKSET (continued)
Subfield or
field TIME1.

ND.
field TIME1.
Datafill example (worksheet)

The following examples show datafill for the rate break set worksheet.
The first example shows datafill for the North American TOPS.
MAP display example for table RBKSET (worksheet)
SCHNAME RBKTYPE RBK1 TIME1 RBK2 TIME2 RBK3 TIME3 RBK4 TIME4
RBK5 TIME5 RBK6 TIME6 RBK7 TIME7 RBK8 TIME8 RBKSET
____________________________________________________________
SAMPLESCH SSUN D2 800 D1 1800 ND 2400 ND 0
ND 0 ND 0 ND 0 ND 0 1
The second example shows datafill for the CEP ITOPS.

MAP display example for table RBKSET (worksheet)
SCHNAME RBKTYPE RBK1 TIME1 RBK2 TIME2 RBK3 TIME3 RBK4 TIME4
RBK5 TIME5 RBK6 TIME6 RBK7 TIME7 RBK8 TIME8 RBKSET
______________________________________________________________
CANADA SSUN D2 800 D1 1800 ND 2400 ND 0
ND 0 ND 0 ND 0 ND 0 1
RBKSET (continued)
Functional description of table RBKSET

Table RBKSET is used to list all the unique rate break sets. The rate break set
worksheet (2750W) is used to identify all the unique rate break sets. This list
is then copied onto forms 2750A and B.
Refer to the Overview section for a detailed description of the rate break tables.
See the section Rate break set worksheet for more information on the rate
break set worksheet.
TOPS Mass Table Control

RBKSET to be mass-table-controlled. In other words, the feature permits the
changes for the table into table RBKSETI, and then, when all the required
changes are entered, swap the contents of table RBKSET with table
RBKSETI.

Table RBKSET provides the applicable discount factor for each rate break
number (obtained from table RBKMAP) over a specific time period within the
24-h period. The type of discount factor obtained is ND (no discount),
QUOTED (quoted), or D1 to D6.
Datafill sequence
Table SYSDATA must be datafilled before table RBKSET. Also, table
DCOUNT must be completed before table RBKSET, since fields RBK1 to
RBK8 must be filled with a discount factor.
Table size
The size of table RBKSET is determined by the value in field SIZE of table
SYSDATA.
297-8021-351 Standard 05.02 May 2001

RBKSET (continued)
Datafill
The following table lists datafill for table RBKSET.
Subfield or
RBKSET 0 to 63 Rate break set. This field is the key to the

table. Enter a number to identify each rate
break set consisting of a unique combination
of field values.
On the worksheet some rate break types
have the same rate break set number.

ND.
a rate break period.
Field TIME1 denotes the end of the first rate
break after midnight. Field TIME2 is the next
and so on. If less than eight rate breaks are
required (for example, only fields TIME1
through TIME3 need to be datafilled for three
rate breaks), the last rate break, (TIME4),
must be entered as 2400. If there are eight
rate periods, the last rate period is assumed
to go from TIME8 to midnight and have a
discount of RBK1; that is, a rate break set
always terminates at midnight.
The entries in fields TIME1 to TIME8 must be
unique values within a rate break set (field
RBKSET).
Enter 0 (zero) for unassigned fields.
Time must be in ascending order.
RBKSET (continued)
Subfield or

ND.
field TIME1.

ND.
field TIME1.

ND.
field TIME1.

ND.
297-8021-351 Standard 05.02 May 2001

RBKSET (continued)
Subfield or
field TIME1.

ND.
field TIME1.

ND.
field TIME1.

ND.
field TIME1.
Datafill example
The following examples show datafill for the rate break set worksheet.
The first example shows datafill for the North American TOPS.
RBKSET (end)
In the example, if a coin call connects at 23:59:30 and RBKSET 2 is used to

determine the discount, discount D3 applies to this call. Since there is a 30 s
start time coin allowance, the system compares discounts D1 and D3 and the
higher discount applies (D3). In this case, the system coin time allowance
pushed the start time of the call into the next RBKSET (D3 2400).
MAP display example for table RBKSET
RBKSET RBK1 TIME1 RBK2 TIME2 RBK3 TIME3 RBK4 TIME4 RBK5 TIME5 RBK6 TIME6
RBK7 TIME7 RBK8 TIME8
________________________________________________________________________
1 D4 2400 ND 0 ND 0 ND 0 ND 0 ND 0
ND 0 ND 0
2 D3 800 ND 1700 D1 2300 D3 2400 ND 0 ND 0

ND 0 ND 0
3 D2 800 D1 1700 D2 2400 ND 0 ND 0 ND 0

ND 0 ND 0
The second example shows datafill for the CEP ITOPS.
In table RBKSET, rate break set has two rate breaks. From 8:00 to 24:00, D1
is in effect; from 24:00 to 8:00, D2 is in effect.
MAP display example for table RBKSET
RBKSET RBK1 TIME1 RBK2 TIME2 RBK3 TIME3 RBK4 TIME4 RBK5 TIME5 RBK6 TIME6
RBK7 TIME7 RBK8 TIME8
________________________________________________________________________
1 D2 800 D1 1800 ND 2400 ND 0 ND 0 ND 0
ND 0 ND 0
2 D3 800 ND 1700 D1 2300 D3 2400 ND 0 ND 0

ND 0 ND 0
3 D2 800 D1 2400 ND 0 ND 0 ND 0 ND 0
ND 0 ND 0
4 D2 800 ND 2400 ND 0 ND 0 ND 0 ND 0
ND 0 ND 0
9 D2 800 ND 2400 ND 0 ND 0 ND 0 ND 0
ND 0 ND 0
297-8021-351 Standard 05.02 May 2001

RBKSETI
Table name
TOPS Rate Break Set Inactive Table
RBKSET to be mass-table-controlled. In other words, the feature permits the
changes for the table into table RBKSETI, and then, when all the required
changes are entered, swap the contents of table RBKSET with table
RBKSETI.
Refer to table RBKSET.

Table size
Datafill
Datafill example
RCCINV
Table name
Remote Cluster Controller Inventory
Overview
Table RCCINV contains the inventory data except the P-side link assignments
for the remote cluster controller (RCC). Table RCCPSINV contains only the
P-side link assignments.
The RCC name (field RCCNAME) is the key for tables RCCINV, RCCPSINV
(RCC P-Side Inventory), IRLNKINV (Interlink Inventory), and SYLNKINV
(Synchronous Link Inventory). Adding a tuple in table RCCINV
automatically creates a corresponding tuple in tables RCCPSINV, IRLNKINV,
and SYLNKINV. Deleting a tuple in table RCCINV automatically deletes the
corresponding tuple in tables RCCPSINV, IRLNKINV, and SYLNKINV.
Table RCCINV is used to maintain a list of RCC types that are datafilled in the
DMS switch. The table information identifies where the RCC is located, the
load and executive (exec) programs required, and the network link
connections. There must be a minimum of three C-side ports datafilled in table
RCCINV to connect the remote center offshore 2 (RCO2) type to the network.
The remote switching center (RSC) with an RCC supports one remote
maintenance module (RMM) and up to eight line concentrating modules
(LCM). An RSC with RCC2 or RCO2 supports two RMMs and up to eight
enhanced LCM(E). All of these components are located at the same site.
Some of the LCM(E)s can be replaced by remote LCMs (RLCM) located apart
from the RSC. The RSC can be placed up to 240 km (l50 miles) from its
DMS-100 host or with extended distance capability (EDC) up to 500 miles.
The RSC and DMS-100 host are interconnected by a DS-1 or PCM30 links.
CAUTION
RCC supports a maximum of nine P-side peripherals RCC2
and RCO2 support a maximum of ten peripherals
The total amount of peripheral nodes, including LCM(E)s,
RLCMs, SMSRs, RMMs, and remote modules configured
on RCCs can not exceed these limits. Attempts to datafill
more than the maximum P-side nodes (peripherals) on
RSCs will be rejected.
297-8021-351 Standard 05.02 May 2001

RCCINV (continued)
The Meridian cabinet remote module (MCRM) is used for the cabinetized
Meridian SL-100 RCC, with product engineering code (PEC) 6X1201.
The RCC2 is an enhanced single-shelf RCC with an MX77 or AX74 processor.

The RCC2 has ports for up to 20 C-side links and 54 P-side ports.
RCCs and RCC2s are remote line trunk controllers (LTC) that connect to a
host LTC on its C-side by DS-1 links. For valid host LTC P-side link
assignment rules, refer to table LTCPSINV (LTC P-Side Inventory). The RCC
is physically similar to an LTC; the major difference is that the LTC has a DS30
interface on its C-side, but the RCC has a DS-1 interface.
The message (MSG) links (first and third entries in field CSLNKTAB) must be
assigned to different line group array (LGA) or line trunk array (LTA) shelf
arrays to ensure that the RSC is not affected by corruption or power failure in
either the LGA or LTA shelf array.
The RCO2 peripheral module type of the DMS-100 Family differs physically
from the RCC. On a functional level, the RCO2 and the RCC perform in the
same manner. The PCM30 line group controller (PLGC) is the host node of
an RCO2 with a maximum of 16 PCM30 links. An RCO2 is a double
processor configuration of extended multiprocessor system (XMS)-based PMs
(XPM) that use PCM30 carriers in their C-side links. The basic differences
between the RCC and RCO2 are summarized in the following table.
Differences between RCC and RCO2 peripheral modules
PM type RCC RCO2
C-side PM type LTC, LGC PLGC
C-side ports DS-1 PCM30
Optional cards UTR14, UTR16, UTR18 UTR14, UTR16, ISP,

RAM6X69
C-side PM type of RMM RCC RCO2
Table RCCINV lists the following data assignment for each bay associated
with an RCC unit:
a three-part key field composed of site name (also datafilled in table SITE),
PM type (ARCC, RCC, RCC2, SRCC, or RCO2) and PM number
an administration number associated with a given PM
RCCINV (continued)
the frame type and frame number on which the PM is physically mounted
the floor, row, frame position, and shelf position for each unit associated
with a line concentrating equipment (LCE) frame
the equipment PEC for the PM
the issue name of the PM software
the terminal types and corresponding executive programs for all the PM
terminals used
the PM type and number to which the RCC is attached
the RCC C-side link assignments
an emergency standalone (ESA) option, if equipped
intra-switching, if allowed
optional cards, if equipped
the TONESET value used in the PM
the PECs of processor cards in units 0 and 1. The PEC entered for each
unit must be the PEC that has the minimum firmware capabilities in the
processor complex.
Optional cards
The following optional cards are supported and are used for various
applications:
CONTINUITY - NT6X70
This is a common channel interoffice signaling (CCIS) card for use with C6 or
N6 applications.
UTR8, UTR9, UTR14, UTR15, UTR16, UTR17, UTR18 - NT6X92

These are universal tone receiver (UTR) cards. If UTR8 is datafilled, it
indicates a UTR card is equipped in slot 8. Both UTR8 and UTR9 are for
international digital trunk controller (IDTC) applications. For LTC, line group
controller (LGC), and DTC applications, two UTR cards can be equipped
either in slot 15, 16, or 17. For RCC applications, two UTR cards can be
equipped in slot 14, 16, or 18.
ISP4, ISP - NTBX01

This is the ISDN signaling preprocessor and is used for common peripheral
modules (CPM). The ISP is equipped in slot 4 for RCO2, RCC2, and SONET
RCC (SRCC) applications. When the ISP is not provisioned, slots 4 and 24
are equipped with 0X50 filler faceplates. The ISP is datafilled as ISP for most
XPM applications prior to NA008. From NA008 on, the ISP is datafilled to
297-8021-351 Standard 05.02 May 2001

RCCINV (continued)
reflect the actual slot number where the ISP resides in unit 0; for example,
ISP4.
MSGMX76
The MSGMX76 is the NTMX76AA messaging interface card. It provides
DMSX and HDLC messaging capability between host and remote peripherals.
DMSX is a half-duplex message protocol implemented on DS30 and DS-1
links. It is used to transfer messages between a remote CPM and an XPM+.
The HDLC protocol is a full-duplex messaging protocol, which is more
efficient than the DMSX messaging protocol. The HDLC protocol is
supported only on an RCC2 with a host LTC+. The HDLC protocol is required
when the round-trip delay between the host and the remote is over 2 ms (EDC).
MSG6X69
The MSG6X69 is the NT6X69 messaging interface card. It provides DMS-X
messaging capability between host and remote peripherals. DMSX is a
half-duplex message protocol implemented on DS30 and DS-1 links. It is used
to transfer messages between a remote CPM and an XPM+.
Note: Only one messaging interface card type is provisioned. Use the
MSGMX76 for HDLC protocol with extended distance capability (EDC),
or the MSG6SX69 for DMS-X protocol without EDC functionality.
NT7X05
The NT7X05 peripheral remote loader (PRL) provides the ability to reduce
XPM simplex time. This is done by allowing XPM software loads to be
transferred to the XPM and stored locally within an XPM unit while the unit
is in-service. Reducing XPM simplex time allows an existing loadfile to be
replaced with a newer loadfile. During the process of replacing a loadfile, the
last image is still available for recovery actions if required. The local storage
mechanism is the NT7X05 circuit pack.
TONE6X79
The initial version of the NT6X69 message card (version AA) requires a tone
generator card, the NT6X79, on the shelf. In this case, TONE6X79 must be
specified in field OPTCARD. The subsequent version of the NT6X69 card
(version AB) has its tone generator chip on the card. As of BCS34, the
NT6X43 message card is no longer supported and MSG6X43 is not specified
in field OPTCARD because the NT6X69 message card is being used.
RAM6X69
If RAM6X69 is specified in field OPTCARD, a downloadable tone set is used
in field TONESET. Card RAM6X69 must be used for the RCO2.
RCCINV (continued)
CMR13, CMR15, CMR16, CMR17, CMR18, CMR19 - NT6X78

This is the CLASS modem resource card that is used to provide the Calling
Number Delivery feature.
ETSBX69
Enhanced time switch (ETS) corresponds to an increase in P-side capacity that
is implemented in a later feature.

Table PMLOADS must be datafilled with the PM load information before
table RCCINV can be datafilled.
Also, the following datafill must exist before RCO2 can be datafilled in table
RCCINV:
The host PLGC is datafilled in table LTCINV and there are enough C-side
links on the PLGC for the additional RCO2.
A template for PLGC D30 carriers is present in table CARRMTC.
At least two D30 carriers on different shelves of the PLGC are datafilled to
connect to the RCO2.
A remote location (for example, REM1) is datafilled in table SITE.
The value DFI that is datafilled in field XPMTYPE of table RCCINV must first
be datafilled in tables LTCINV and LTCPSINV.
The RCC name (field RCCNAME) is the key for tables RCCINV, RCCPSINV,
IRLNKINV, and SYLNKINV. Adding a tuple in table RCCINV automatically
creates a corresponding tuple in tables RCCPSINV, IRLNKINV, and
SYLNKINV. This tuple contains the RCC name, a false value for the BITS
definition boolean, the nilport symbol ($) for the vector of BITS links, and a
false value for the revertive switching boolean. Deleting a tuple in table
RCCINV automatically deletes the corresponding tuple in tables RCCPSINV,
IRLNKINV, and SYLNKINV.
Note: The tuple RCCINV creates in tables RCCPSINV, IRLNKINV, and

SYLNKINV enters a false value for building integrated timing system
(BITS). This value must remain false because BITS is not supported.
Table size
0 to 255 tuples
Memory is dynamically allocated for this table.
297-8021-351 Standard 05.02 May 2001

RCCINV (continued)
Datafill
The following table lists datafill for table RCCINV.
DANGER
Entering incorrect shelf information can result in a valid
unit going out of service
Entering an incorrect shelf position (field SHPOS) results
in log data that incorrectly identifies a faulty XPM shelf.
This error can cause a valid unit to be taken out of service,
and may cause an E1 condition.
Subfield or
RCCNAME see subfields Remote cluster controller name. This field

consists of subfields SITENM, PMTYPE, and
RCCNO.
Note: All RCC nodes entered in this table are

also displayed in tables RCCPSINV,
IRLNKINV, and SYLNKINV.
SITENM alphanumeric Site name. Enter the site name assigned to

the remote location. This entry must also
appear in table SITE.
PMTYPE ARCC, RCC2, Peripheral module type. Enter the type of PM.
RCC, SRCC, ARCC is the Austrian version of the remote
or RCO2 cluster controller.
Note: When datafilling field CSLNKTAB, ensure message links are not assigned to the same
physical interface card. When the interface card supports two or more links, separate the message
links by the number of links on the interface cards. This applies to all interface link types; DS-1, DS30,
DS30A, or PCM-30. Table control will issue a warning if an attempt is made to assign message links
on the same interface card. Assigning message links to the same interface card can cause an E1
outage (failure of all message links) if the card fails.
RCCINV (continued)
Subfield or
RCCNO numeric Remote cluster controller number. Enter the

(0 to 255) PM number.
Note: This number is unique by office and

not by site. Any entry outside this range is
invalid.
ADNUM numeric Administration number. This field contains

(0 to 4095) the external administrative number
associated with a PM. Enter a numerical
value that is unique among all other PMs in an
office.
FRTYPE CRSC, Frame type. Enter the frame type on which

MCRM, the PM equipment is mounted. Frame type
MCRMS, RCE, MCRMS is valid with RCC2 and requires
RCEI datafill of refinement EXTFRTYP with an
entry of MCRMS.
FRNO numeric Frame number. Enter the number of the

(0 to 511) frame on which the PM is mounted.
SHPOS numeric Shelf position. Enter the position of the lower

(0 to 77) of the two shelves on the frame unit, in inches
above the floor (1 in = 25.4 mm). (See
Warning at beginning of table.)
FLOOR numeric Floor. Enter the number of the floor on which

(0 to 99) the PM frame is located.
ROW A to Z and AA Row. Enter the row in which the PM

to ZZ (except I, equipment frame is located.
II, O, and OO)
FRPOS numeric Frame position. Enter the bay position of the

(0 to 99) PM equipment frame.
297-8021-351 Standard 05.02 May 2001

RCCINV (continued)
Subfield or
EQPEC 6X12AA, Equipment product engineering code. Enter

6X1201, the PEC of the PM as follows:
6X12DA,
Enter MX85AA if the entry in field
6X12DB,
PMTYPE is RCC2, RCO2, or SRCC.
6X12GA,
FX17JB, Enter 6112SI if the entry in field PMTYPE
MX85AA, is ARCC.
6112SI
LOAD alphanumeric Load. Enter the name given to the issue of

(vector of up to PM software. Table PMLOADS must be
eight datafilled first with the load used.
characters)
EXECTAB see subfields Executive table. This field consists of

subfields TRMTYPE and EXEC.
Note: More than one field TRMTYPE and

field EXEC combination (up to 8) can be used
for a given PM.
RCCINV (continued)
Subfield or
TRMTYPE AB250, Terminal type. Enter the type of PM terminals

ABTRK, used as follows:
ESALINES,
AB250 for DMS-250 trunks
KEYSET,
M5X09, ABTRK for regular trunks
M5X12,
ESALINES for emergency standalone
POTS,
lines
R1_TERM,
RMM_TERM KSBAEX for ISDN ARCCs
KEYSET for P-phone and data lines
M5X09 and M5X12 for Meridian 9- and
12-button sets
POTS for regular lines
R1_TERM for DTC300 trunks
RMM_TERM for remote lines
297-8021-351 Standard 05.02 May 2001

RCCINV (continued)
Subfield or
EXEC DCM250, Executive programs. Enter the set of

DTC300, executive programs required for the PM
DTCEX, specified in field TRMTYPE as follows:
ESAEX,
Enter DCM250 if the entry in field
FXODTC,
TRMTYPE is AB250.
KSBAEX,
KSETEX, Enter DTC300 if the entry in field
POTSEX, TRMTYPE is R1_TERM.
RSMEX
Enter DTCEX or FXODTC (depending on
type of trunking) if the entry in field
TRMTYPE is ABTRK. (FXODTC is for
RCC types only - not RCC2)
Enter ESAEX if the entry in field
TRMTYPE is ESALINES.
Enter KSETEX if the entry in field
TRMTYPE is KEYSET, M5X09, or
M5X12.
Enter POTSEX if the entry in field
TRMTYPE is POTS.
Enter RSMEX if the entry in field
TRMTYPE is RMM_TERM.
CSPM see subfields C-side peripheral module. This field consists

of subfields XPMTYPE and XPMNO.
XPMTYPE DFI, LGC, Peripheral module type. Enter the type of PM

LTC, PLGC to which the RCC C-side is attached. Only
DFI can be used for SRCC.
Note: Datafill for an LGCO or an LGCOi is

always PLGC.
RCCINV (continued)
Subfield or
XPMNO numeric Peripheral module number. Enter the number

(0 to 255) of the PM to which the RCC C-side is
attached. Entries outside the range 0 to 255
are invalid.
CSLNKTAB numeric C-side link table. This field is a vector of up to

(0 to 19) or 16 entries. Enter the LTC P-side DS-1 links (0
NILPORT to 19) to which the RCC C-side is assigned.
Note: All the links from an RCC must go to

the same LTC.
MSG links (1st and 3rd entries) of the RSC
must be assigned to different LGA or LTA
shelf arrays to ensure that the RSC is not
affected by corruption or power failure in
either the LGA or LTA shelf array.
Field CSLNKTAB can also contain the PLGC
links (0 to 15) on which the RCO2 is assigned.
The PLGC links correspond to the RCO2's
C-side link 0 to 15. The minimum number of
links for an RCO2 is two. The first link entered
for each unit (0 and 1) is used as the
messaging link.
To connect the RCC2 and RCO2 to the
network requires a minimum of three C-side
links.
An entry of NILPORT is used to skip links;
ports 0 and 2 can be equipped and port 1 can
be left unequipped by using the NILPORT
option.
297-8021-351 Standard 05.02 May 2001

RCCINV (continued)
Subfield or
ESA Y or N Emergency stand-alone. Enter Y (yes) and

datafill field WXSWACT if the RSC has the
emergency stand-alone (ESA) option.
Otherwise, enter N (no).
ESA is applicable to non-ISDN lines only in an
RCC2 and is not supported within an RCO2.
WSXWACT Y or N Warm exit switch activity. This field becomes

active only if the entry in field ESA is Y. Enter
Y if RCC type supports warm ESA exit.
INTRASW Y or N Intra-switching. Enter Y if intra-switching on

the RCC or RCC2 is allowed. Otherwise,
enter N.
RCCINV (continued)
Subfield or
ADDLMSGL N Additional message link. Additional message

links are not supported.
Note: When changing the ADDLMSGL field

from Y to N, the RCC2 AML links must be
either manual busy (ManB) or offline (Offl).
OPTCARD CMR5, Optional card. This field is a vector of up to 10

CMR13, entries. Enter the optional card as follows:
CMR15,
Enter CONTINUITY if equipped with
CMR16,
NT6X70 for CCIS C6 or N6 application.
CMR17,
CMR18, Enter UTR8, UTR9, UTR14, UTR15,
CMR19, UTR16, UTR17 or UTR18 if equipped
CONTINUITY, with UTR cards in slots 8, 9, 14, 15, 16, 17
ETSBX69, or 18 respectively.
ISP,
MSGMX76, Note 1: MSGMX76 messaging interface
MSG6X69, card is used for HDLC protocol and EDC.
NT7X05AA, MSG6X69 is used for DMS-X protocol and
RAM6X69, does not allow EDC.
TONE6X79,
UTR6, UTR7,
Note 2: NT7X05AA is a peripheral remote
loader (PRL) card. Refer to subfield
UTR8, UTR9,
SLOT_NUMBER.
UTR14,
UTR15, Note 3: UTR8 and UTR9 are for IDTC
UTR16, applications; UTR15, UTR16, and UTR17 are
UTR17, for LTC, LGC, and DTC applications; and
UTR18 UTR14, UTR16, and UTR18 are for RCC
applications.
297-8021-351 Standard 05.02 May 2001

RCCINV (continued)
OPTCARD = CMRnn
If the entry in field OPTCARD is CMRnn (where nn is equivalent to 8, 9, or
14 to 18), datafill field CMRLOAD.
Subfield or
CMRLOAD alphanumeric Class model resource load. Enter the

(vector of up appropriate CMR software load name.
to eight
characters)
OPTCARD = ISPnn
If the entry in field OPTCARD is ISP, datafill subfield SLOT_NUMBER as
described in the following table. Then, go to field TONESET to continue
datafill for table RCCINV.
Subfield or
SLOT_NUMBER 3 to 19 Slot number. The recommended optional slot

number for most North American XPMs is 16.
OPTCARD = MSGMX76
If the entry in field OPTCARD is MSGMX76, datafill field MX76INFO.
Subfield or
MX76INFO see subfield MX76 information. This field consists of

subfields MX76LOC and PROTOCOL.
MX76LOC HOST or MX76 location. Enter REM if the card is

REM located in a remote peripheral and datafill
field PROTOCOL. Any entry other than REM
is invalid for table RCCINV.
RCCINV (continued)
Subfield or
PROTOCOL DMSX or Protocol. Enter the protocol for

HDLC host-to-remote communication. The default is
DMSX. When changing the messaging
protocol from DMSX to HDLC, the RCC2
C-side links can be InSv. A DMSX to HDLC
dynamic upgrade is not allowed in the inactive
CM.
Note: When changing field PROTOCOL

from DMSX to HDLC, calls may be
established on channels dedicated to HDLC
during a dynamic upgrade. The central
control (CC) checks to see if there are calls on
these channels and sends a warning to the
MAP display that existing calls will be
dropped. The user must confirm with Y
before the protocol can be changed. The PM
state is then changed to in-service trouble
(ISTb) until all HDLC links are synchronized.
OPTCARD = NT7X05AA
If the entry in field OPTCARD is NT7X05AA, datafill subfield
SLOT_NUMBER as described in the following table, then go to field
TONESET to continue datafill for table RCCINV.
Subfield or
SLOT_NUMBER numeric Slot number. If the entry in field PMTYPE is
(3 to 19, see RCC, enter slot number 12. Slot numbers 14,
explanation) 16, and 18 are also allowed if they are not
occupied by other cards.
If the entry in field PMTYPE is RCC2, enter
slot number 5 or 7 (card must be placed in slot
pairs 5 and 23 or 7 and 21).
297-8021-351 Standard 05.02 May 2001

RCCINV (continued)
All cards
For all optional cards, continue datafill for table RCCINV as described in the
following table.
Subfield or
TONESET AUS100, Tone set. Enter the tone set appropriate for
AUS300, the ARCC, RCC, RCC2, SRCC, or RCO2
AUSTRIA, PM.
CEP, CHINA,
Tone sets NORTHAM, TURKEY, UK, MCL,
EIREDTC,
SPAIN, CEP, AUSTRIA, HUNGARY, and
EIRELGC,
CHINA are ROM tone sets.
HUNGARY,
INDIA, JAPAN, The downloadable RAM tone sets are
JAPAN1, JAPAN, MALAYSIA, MALYADSI,
MALAYSIA, MOROCCO, TURK300, AUS300, EIRELGC,
MALYADSI, EIREDTC, AUS100, UK300, UK100,
MCL, UKADSI, NZLGC, NZDTC, PHILADSI,
MOROCCO, PHILTONE, SRILADSI, SRILANKA, INDIA,
NA_RAM, JAPAN1, and NA_RAM (North American
NORTHAA, RAM-based tone set). Entries outside this
NORTHAM, range are invalid.
NZDTC,
The default value for domestic RCC is
NZLGC,
NORTHAM.
PHILADSI,
PHILTONE, Tone set NORTHAA supports the
SPAIN, Bellcore-defined analog display services
SRILANKA, interface (ADSI) tone for the 6X69AD tone
SRILADSI, and messaging card.
TURK300,
Tone set MALYADSI supports the
TURKEY,
Bellcore-defined analog display services
UK, UK100,
interface (ADSI) tone.
UK300,
UKADSI Tone set PHILADSI supports the
Bellcore-defined (ADSI) tone.
Tone set SRILADSI supports the
Bellcore-defined (ADSI) tone.
RCCINV (continued)
Subfield or
PROCPEC 6X45AA, Processor equipment product engineering

6X45AB, code. Enter the PEC of the 6X45 card in unit
6X45AC, 0 and 1 of the RCC. The PEC entered in each
6X45CA, unit must be the card with the minimum
6X45AD, firmware capabilities in the processor
6X45AE, complex of each unit. The PECs listed have
6X45AF, increasing firmware capabilities.
6X45BA,
For RCO2, the 6X45BC card must be used for
6X45BB,
CSP02 and below. For CSP03 and up,
6X45BC,
MX77AA or AX74AA is supported.
MX77AA,
AX74AA, For RCC2, the PEC is MX77AA or AX74AA.
SX05AA
For RCC, the PEC MX77AA can also be used
and is referred to as an RCC plus.
An SX05AA can only be datafilled on an
RCC2 and cannot be datafilled in combination
with a 6X45 processor. When the SX05AA is
datafilled, the corresponding PRL card must
be datafilled as well. Valid values are
$ - for the filler packlet (no functionality)
SX06BA - for 32 Mbyte PRL memory
packlet
SX06CA - for 64 Mbyte PRL memory
packlet
SX06DA - for 128 Mbyte PRL memory
packlet
Note: If an SX05AA processor is datafilled in

both units, an NT7X05AA is not allowed in the
OPTCARD field.
E2LOAD alphanumeric EEPROM load name. Enter the erasable

(vector of up to electronic programming read only memory
eight (EEPROM) load name. If the shelf is
characters) equipped with a processor that is different
from NTMX77, field E2LOAD is automatically
datafilled with the string NILLOAD.
297-8021-351 Standard 05.02 May 2001

RCCINV (continued)
Subfield or
EXTINFO see subfields Extension shelf information. This field

consists of subfields EXTSHELF,
EXTFRTYP, EXTFRNO, EXTSHPOS,
EXTFLOOR, EXTROW, EXTFRPOS,
EXTEQPEC, and EXTSIDE.
EXTSHELF Y or N Extension shelf. Enter Y if the CPM has an

extension shelf and continue datafill for this
table. This is true only for RCC2 or RCO2.
Otherwise, enter N; no other datafill is
required.
EXTFRTYP CEXT, Extension frame type. Enter the type of frame

MCRMS, RCEI in which the extension shelf is located. RCC2
must have an EXTFRTYP of CEXT.
EXTFRNO numeric Extension frame number. Enter the frame

(0 to 511) number of the frame type in which the
extension shelf is placed.
EXTSHPOS numeric Extension shelf position. Enter the shelf

(0 to 77) position in inches above the floor.
EXTFLOOR numeric Extension shelf floor location. Enter the floor

(0 to 99) on which the extension shelf is located.
EXTROW A to Z (except I Extension shelf row location. Enter the row in

and O) which the extension shelf is located.
EXTFRPOS numeric Extension shelf frame position. Enter the

(0 to 99) extension shelf position within the frame.
EXTEQPEQ MX86AA Extension shelf equipment PEC. Enter the

extension shelf equipment PEC.
EXTSIDE L or R Extension shelf side. Enter L (left) or R (right)

to indicate on which half of the physical shelf
the logical extension shelf is located.
Datafill example
The example shows assignments for RCC 1 located at site HOST. This RCC
is controlled by LTC 7 located in the host office. There are eleven DS-1 links
in use between this controller and the host office.
RCCINV (continued)
The RCC does not have the ESA option and intra-switching is not allowed.
Universal tone receiver cards are equipped in slots 15 and 16. The PEC of unit
0 and 1 of the RCC is 6X45AC.
With regard to vectors, note that EXECTAB has two members, CSLNKTAB
has eleven members, and OPTCARD has two members. The $ sign indicates
the end of the vector.
This example has one continuous record.

MAP display example for table RCCINV
RCCNAME
ADNUM FRTYPE FRNO SHPOS FLOOR ROW FRPOS EQPEC LOAD
EXECTAB
CSPM
CSLNKTAB
ESA INTRASW
OPTCARD
TONESET PROCPEC E2LOAD EXTINFO
_____________________________________________________________________RE
M1 RCC 1
2 RCE 2 4 1 B 0 6X12AA ESR06BB $
(POTS POTSEX) ( RMM_TERM RSMEX) (KEYSET KSETEX) ( ABTRK DTCEX)
(ESALINES ESAEX)$
LTC 7
(0)(1)(2)(3)(4)(5)(6)(7)(8)(9)(10)(11)(12)(13)(14)(15)(16)(17)(18)(19)$
Y Y N
( UTR14 ) ( UTR16 ) ( CMR15 CMR03A) ( NT7X05AA 17) ( MSG6X69 )$
NORTHAM MX77AA MX77AA NILLOAD N $
Table history
MMP13
Added new values MALYADSI, PHILADSI, and SRILADSI to field
TONESET.
NA010
Added information supporting 20 DS-1 C-side links.
APC009
Added values INDIA and SRILANKA to field TONESET.
297-8021-351 Standard 05.02 May 2001

RCCINV (continued)
NA008
The following changes were made for NA008 to table RCCINV:
Changed the PEC6X45 field name to PROCPEC to support various
processors including the NTMX77, NTAX74, and NTSX05.
Added datafill options for NTAX74 and NTSX05 in PROCPEC field.
Removed restrictions on support for the NT7X05 PRL card when the
NTAX74 card is datafilled in PROCPEC for an RCC2.
Table RCCINV has been updated for the NA009 release of this document.
This update was made in response to a Problem Resolution System (PRS)
request for the NA008 timeframe.
XPM08
Added message link assignment warnings.
GL03.1
Added datafill to allow for support of an RCO2 hosted by an LGCO+ in China
(without ISDN or EDC).
NA007
Added a warning note to table RCCINV on datafilling field CSLNKTAB. A
message is displayed by table control if an attempt is made to datafill multiple
message links that are assigned to the same interface card.
APC07
Reference to Intra-switching calls not supported within an RCO2" in table
RCCINV was removed.
The options MALAYSIA and PHILTONE were added to field TONESET.
NA005
The following changes were made to table RCCINV:
added information to explanation column of fields ADDLMSGL and
OPTCARD for feature AN1548, InSv Upgrade DMSX to HDLC
added information on the MSGMX76 optional card
NA004
added information under Overview" regarding table interactions between
table RCCINV and table SYLNKINV
added table SYLNKINV to note under field RCCNAME
RCCINV (continued)
added entry NT7X05AA for subfield OPTCARD

added refinement SLOT_NUMBER for subfield OPTCARD entry
NT7X05AA
removed references to PRCC and RCCI PM types that are no longer
supported
NA002
A paragraph was added under Functional description" for the RCC2.
Field ADDLMSGL was added.
The entry NORTHAA (North American ADS-1) was added for field
TONESET.
BCS36
Field ADNUM was added.
When references to data changes affecting RCC link information in table
RCCINV are made, the following warning applies.
WARNING
Call processing to the PLGC and RCO2 can be affected
If the data change affects link information to a PCM30 line
group controller (PLGC) hosting an RCO2, this can result
in static data changes to the PLGC and RCO2. Such
changes can affect call processing to both the PLGC and
RCO2 and must only be done during low traffic periods. If
a static data mismatch condition occurs on the RCO2 (the
RCO2 shows an in-service trouble (ISTb) condition). Two
warm switches of activity (SWACT) must be performed to
update the static data in both units of the RCO2.
Mapping of links from an RCO2 through the PLGC takes precedence over any
requirements for channels for call processing in the PLGC itself. The affect of
any changes to link configuration on call processing of the PLGC and RCO2
must be fully understood before proceeding.
Any change in C-side or P-side links must be made very carefully. Ensure that
enough call processing C-side capacity remains in the PLGC and RCO2.
297-8021-351 Standard 05.02 May 2001

RCCINV (end)
Dynamic C-side link reconfiguration of the RCO2 is not supported. Such an

operation is blocked when there is at least one network special connection
(SPECCONN) going through that particular RCO2. If the user tries to alter a
C-side link in table RCCINV when at least one SPECCONN uses that XPM,
the tuple change is not permitted and the following error message is displayed:
ERROR: Delete Network SPECCONN connections before changing

CSLINKS
Similarly, dynamic C-side link reconfiguration of the RCO2 can corrupt

time-division multiplexing (TDM) connections using the equipped C-side port
to the PLGC. If a Basic Rate Interface (BRI) ISDN TDM connection is using
the port that the user is adding, deleting or changing, then the following
message is printed, and the user is advised to delete the related ISDN lines
before resuming dynamic C-side link reconfiguration on the RCO2:
C-SIDE PORT XXX IS BEING USED FOR ISDN CONNECTIONS. IF FULL

UTILIZATION OF THIS PORT IS DESIRED, THE FOLLOWING LENS
ASSOCIATED WITH WITH THESE ISDN CONNECTIONS MUST BE DELETED AND
RE-DATAFILLED AFTER THIS LINK CHANGE IS COMPLETE.
TDM connections using intraswitching channels are not connected to a host

channel. As a result, they are not affected by an RCO2 C-side link change.
When datafilling message links in RCCINV, separate links by a minimum of

slots equal to the number of links on the interface card. Ensure that both
message links are not assigned to the same interface card. An E1 outage can
occur if both message links are assigned to a card that fails.
Both cside message links assigned to the same XPM

interface card. If this card becomes disabled it
WILL cause an *** OUTAGE ***. Links on the same card
include: {0 1}, {2 3}, {4 5}, {6 7}, {8 9}, {10 11},
{12 13}, {14 15}, {16 17}, {18 19}. Each message
link should be on a different card.
RCCPSINV
Table name
Remote Cluster Controller P-Side Link Inventory Table
Table RCCPSINV contains peripheral-side (P-side) link assignments for
remote cluster controller (RCC) peripheral modules (PM). The table has a
three-part key consisting of a site name (as datafilled in table SITE), PM type,
and PM number.
A corresponding default tuple is automatically added in table RCCPSINV if a

PM is datafilled in table RCCINV. In this default tuple, all P-side links for the
PM are initially defined as NILTYPE. P-side links that do not have hardware
assigned must remain as NILTYPE. Unequipped, software-assigned P-side
links generate service problems.
The following PM types are supported by table RCCPSINV:

ARCC (Austrian remote cluster controller)
RCC (remote cluster controller)
RCC2 (compact RCC)
RCO2 (remote switching center offshore 2)
SRCC (SONET RCC)
The following table shows the sequence in which the RCC P-side ports must
be assigned to ensure correct operation of the remote. This sequence table
does not apply to RCC2 P-side port assignments.
P-side port assignments for RCC
Port number Sequence
0,1 DS30A links to remote maintenance module

(RMM) only
2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, DS-1 links
18, 19
19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, DS30A links for line concentrating modules
4, 3, 2, (LCM)
D-channel handlers (DCH) can reside in odd-numbered ports only.
297-8021-351 Standard 05.02 May 2001

RCCPSINV (continued)
The RCC2 is datafilled with up to 54 (0-53) multiples of P-side link

information. Valid RCC2 link types are DS30A, DS-1, DCH, and NILTYPE.
When an extension shelf is added, there are datafill restrictions for RCC2
P-side links connected to the extension shelf. The DS-1 and DCH links
connected to the extension shelf are datafilled only if the extension shelf is
datafilled in table RCCINV. All links connected to the extension shelf must be
changed in table RCCPSINV from DS-1 or DCH to NILTYPE prior to deleting
the extension shelf from table RCCINV.
Some of the DCH and DS-1 interface cards occupy the same physical slots,
and therefore cannot coexist. The following pairs of links cannot be datafilled
for the same extension shelf:
DCH link 14 and any of the DS-1 links 24 to 31
Up to ten DCH cards can be datafilled in table RCCPSINV for an RCC2.
ATTENTION
ISDN line drawer for remotes (ILDR) is first available for remote
switching center-SONET (RSC-S) and remote switching center (RSC)
configurations in the NA007/XPM08 timeframe. ILDR is first available
for remote line concentrating module (RLCM), outside plant module
(OPM), and outside plant access cabinet (OPAC) configurations in the
NA008/XPM81 timeframe.
When changing the carrier of a link connected to an ILDR-equipped RLCM,

the new carrier must allow 64 kbit/s clear channel.
For related information, refer to tables RCCINV and IRLNKINV.

The following tables must be datafilled before table RCCPSINV:
RCCINV
SITE
CARRMTC
Table size
0 to 255 tuples
Datafill
The following table lists datafill for table RCCPSINV.
Subfield or
RCCNAME see subfields Remote cluster controller name. This field

consists of subfields SITENM, PMTYPE, and
RCCNO.
SITENM alphanumeric Site name. Enter the site name assigned to the
(up to four remote location. This entry must also appear in
characters) table SITE.
PMTYPE ARCC, RCC, Peripheral module type. Enter the type of

RCC2, RCO2, peripheral module (PM) as follows:
or SRCC
ARCC (Austrian remote cluster controller)
RCC (remote cluster controller)
RCC2 (compact RCC)
RCO2 (remote switching center offshore 2)
SRCC (SONET RCC)
RCCNO 0 to 255 Remote cluster controller number. Enter the

RCC number (defined in table RCCINV).
Note: This number is unique by office and not

by site.
PSLNKTAB see subfields P-side link table. This field consists of subfields
PSLINK and PSDATA.
PSLINK 0 to 53 P-side link. Enter the P-side port number of the

remote cluster controller (RCC).
PSDATA see subfield P-side data. This subfield consists of subfield

AREASELCT.
297-8021-351 Standard 05.02 May 2001

Subfield or
AREASELCT D30, DCH, Area selector. Enter D30 for ARCC and RCO2,
DS1, DS30A, and datafill refinements CARRIDX and ACTION.
or NILTYPE
Enter DCH for RCC2, SRCC, and RCO2.
Enter DS1 for links to remotes of a remote and
for RCC, RCC2, and SRCC, and datafill
refinements CARRIDX and ACTION.
Enter DS30A for all links to remote maintenance
modules (RMM) and line concentrating modules
(LCM).
Enter NILTYPE for RCC2 P-side links 0 and 8 if
dual configuration is defined in table IRLNKINV.
Enter NILTYPE for all other unequipped links.
CARRIDX alphanumeric Carrier index. If the entry in subfield

(up to 16 AREASELCT is D30 or DS1, datafill this
characters) refinement. Enter the name to index into table
CARRMTC for maintenance information of the
carrier. Enter DEFAULT for the default template
in table CARRMTC.
ACTION Y or N Action. If the entry in subfield AREASELCT is

D30 or DS1, datafill this refinement. Enter Y
(yes) to remove the carrier from service if the
out-of-service limit (OL) for frame, slip,
errored-second, or severe-errored-second is
exceeded. Otherwise, enter N (no).
Datafill example
An example of datafill for table RCCPSINV follows.
RCCPSINV (end)
MAP display example for table RCCPSINV
RCCNAME
PSLNKTAB
_____________________________________________________________________
REM2 RCC 0
(0 DS30A ) (1 DS30A ) (2 DS30A ) (3 DS30A ) (4 DS30A ) (5 DS30A )
(6 DS30A ) (7 DS1 DEFAULT N) (8 DS1 DEFAULT N) (9 DS1 DEFAULT N)
(10 DS30A ) (11 DS1 DEFAULT N) (12 DS1 DEFAULT N)
(13 DS1 DEFAULT N) (14 DS30A ) (15 DS1 DEFAULT N) (16 DS30A ) (17
DS30A )
(18 DS30A ) (19 DS1 DEFAULT N) $
REM3 RCC 1
(0 DS30A ) (1 DS30A ) (2 DS1 DEFAULT N) (3 DS1 DEFAULT N) (4 DS30A )
(5 DS30A ) (6 DS1 DEFAULT N) (7 DS1 DEFAULT N) (8 DS30A ) (9 DS30A )
(10 DS1 DEFAULT N) (11 DS1 DEFAULT N) (12 DS30A ) (13 DS30A )
(14 DS1 DEFAULT N) (15 DS1 DEFAULT N) (16 DS1 DEFAULT N)
(17 DS1 DEFAULT N) (18 DS1 DEFAULT N) (19 DS1 DEFAULT N) $
Table history
NA008
Table RCCPSINV has been updated for the NA011 release of this document.
This update was made in response to a Problem Resolution System (PRS)
request for the NA008 timeframe.
NA007
New restrictions have been added as a result of the introduction of the ILDR.
NA004
The following changes were made to table RCCPSINV:
added two paragraphs to Functional description" regarding RCC2 P-side
side links 0 and 8
added explanation to subfield AREASELCT, entry NILTYPE
removed references to PRCC and RCCI PM types that are no longer
supported
BCS36
The following changes were made to table RCCPSINV:
added PM type ARCC
added value D30 to and corrected values for field AREASELCT
297-8021-351 Standard 05.02 May 2001

RCFCLI
Table name
Remote Call Forwarding Calling Line Identification Table
This table lists up to a maximum of eight serving numbering plan areas (NPAs)
and directory numbers of the base station for a remote call forwarding line with
the calling line identification option.
The operating company uses the Remote Call Forwarding Calling Line
Identification Table Record (form 2203) to record input data for table
RCFCLI.

There is no requirement to datafill other tables prior to table RCFCLI.
Table size
Memory is automatically allocated for the eight entries.
Datafill
The table that follows lists datafill for table RCFCLI.
Field descriptions
Subfield or
INDEX 1 to 8 Index
Enter the table index. Use RCFINDEX to
find the next available index.
SNPA numeric (3 digits) Serving numbering plan area

Enter the serving NPA assigned to the base
station.
LCLDN numeric (1 to 13 Directory number

digits, 0 to 9)
Enter the directory number assigned to the
base station.
Datafill example
The figure that follows shows datafill for table RCFCLI.
RCFCLI (end)
The example is for directory number 225-4983 in serving NPA 613 assigned
to index number 2.
MAP display example for table RCFCLI
INDEX SNPA LCLDN
________________________________________________________
2 613 2254983
Table history
MMP14
Changed the entry for field LCLDN from (7 digits) to (1 to 13 digits, 0 to
9) for feature E.164 Compliance for Redirection Services (REDIRSRV
ARCHID).
297-8021-351 Standard 05.02 May 2001

RCNAME
Table name
ISDN Routing Characteristic Name Table
The different ISDN routing characteristic names for an ISDN central office
switch appear in table RCNAME. These names appear in other tables used to
process calls with ISDN routing characteristics. Table RCNAME is the first of
a series of tables. The user uses the table series for the installation of Bellcore
TR-448, ISDN Routing and Digit Analysis.
Each routing characteristic-name points to an index in table RTECHAR. This

element is the first step in the ISDN call translation process.
The value of RCNAME determines the translation path of the call. When
RCNAME contains the value NILNAME, the call proceeds. The call proceeds
to Meridian Digital Centrex (MDC) or plain ordinary telephone service
(POTS) translations. Other values of RCNAME indicate that the call proceeds
to ISDN translation.
See table RTECHAR for additional information.

RCNAME.
Enter data in table RCNAME before you enter data in the following tables:
HNPACONT.RTEMAP
FNPACONT.RTEMAP
INBRTE
IBNRT2
IBNRT3
IBNRT4
IBNXLA
INWOMAP
INWTMAP
OFRT
OFR2
OFR3

RCNAME (continued)
OFR4
OFRTMAP
OFRTMA2
OFRTMA3
OFRTMA4
PXLAMAP
RTECHAR
IBNMAP
UNIMAP
XLANAME
Table size
0 to 256 tuples
The system allocates data store for 64 tuples in table RCNAME.
Datafill
Datafill for table RCNAME appears in the following table.
xxxField descriptions
Subfield or
NAMEKEY alphanumeric Routing characteristic name key. Enter the

(1 to 8 routing characteristic name.
characters)
Datafill example
Sample datafill for table RCNAME appears in the following example.
297-8021-351 Standard 06.02 July 2002

RCNAME (end)
MAP example for table RCNAME
NAMEKEY
________________________________________________________
BC64PIRQ
BC64PIPR
BC64PINR
BC31PIRQ
BC31PIPR
Release history
NA016
Feature 59029017 adds table FNPACONT.RTEMAP to the datafill sequence
of this table.

RCSINV
Table name
Remote Concentrator Subscriber Inventory Table
The Remote Concentrator Subscriber, also called the Remote Concentrator
SLC-96 (RCS), is a line peripheral used by the SLC-96 system (a Western
Electric product designed to serve a cluster of up to 96 subscribers in a remote
location).
A Subscriber Module SLC-96 is a peripheral module (PM) that provides a

direct digital interface from the RCS to the DMS-100 host (SMS supports up
to six RCS modules).
Table RCSINV lists the following data assignment for each RCS module:
site name as assigned by the operating company to the remote location
(this entry is not optional and there is no default value assigned to it)
frame/unit combination, which uniquely defines the RCS module number
frame type on which the PM is physically mounted
frame number, is unique by office (when this option applies)
floor, row on floor, frame position in row, and shelf position for each unit
associated with a remote concentrator equipment frame
the issue name of the PM software (for the RCS, this field is always
datafilled as NO_LOAD)
PM type and number to which the RCS attaches
mode of operation of shelf groups AB and CD
SMS P-side and DS-1 lines connectivity information
coded, superimposed, and frequency ringing data
type of alarm control unit
protection line if required
port for the protection line
Scan and signal distribution (SD) group numbers and scan and SD points
used within these groups for the inhibit lead function.
RCS modules on different frames can share a metallic test pair. This is done
by multiplying the tip and ring outputs on the Main Distribution Frame (MDF).
When Central Office terminals are co-located with SMS modules, this method
uses the inhibit lead to indicate busy/idle of the test pair. Field SCSDUSED is
297-8021-351 Standard 05.02 May 2001

RCSINV (continued)
datafilled with Y (yes), and the same SC and SD points are assigned to each
(site) frame multiplied on the MDF. The scan and SD groups are defined in
tables SCGRP and SDGRP respectively. An SD point activates ground on the
inhibit lead associated with a metallic test pair, so that no more than one RCS
or COT accesses a shared metallic test pair at one time. A scan point scans the
inhibit lead to determine if ground exists; if ground exists, other RCS modules
are prevented from accessing the metallic test pair.
whether PCM Looping Test is run for a Mode II RCS
alarm severity and text for power/miscellaneous alarm.
The RCS has four line shelves named A, B, C and D. Shelves A and B make
up the shelf group AB, while shelves C and D make up the shelf group CD.
Each shelf group operates independently of the other and can be operated in
one of the following modes:
Mode1 - Non-concentrated Shelf group, primarily intended for single and
multiparty lines. One or two DS-1 lines connect to a shelf group in this
mode, depending on whether one or two shelves are equipped.
Mode2 - Concentrated Shelf group, where up to 48 lines of each shelf
group are concentrated onto 24 channels. One DS-1 line connects to a
shelf group in this mode.
Mode3 - Non-concentrated Shelf group, where the entire shelf group is
dedicated to coin, data lines, or other special service lines. One DS-1 line
connects to a shelf group in this mode.
The mode of a particular shelf group is dependent upon cards installed in the
SLC-96 system (it cannot be changed under program control).
C-side link information in the RCS is dependent upon the mode of one or two
C-side links for a shelf group while in modes 2 and 3 operation of each of the
two shelf groups. In mode 1 there can be only one C-side link per shelf group.
The RCS has two types of alarm control unit (ACU) cards called WP1 and
WP1B. The difference between the two cards is the format of the alarms
message sent to the office through the Derived Data Link (DDL).
A protection line (PROT LINE) is a standby DS-1 link between the SMS and
RCS. Only one RCS is assigned to a single PROT LINE. Depending on the
mode of operation of the shelf groups, the ratio of PROT LINEs to normal
DS-1 links (normlines) can be 1:2, 1:3, or 1:4. A protection switch preserves
calls in the talking state, and for POTS and coin lines, calls in the ringing state.
If any DS-1 line is part of a nailed-up cross-connection, that DS-1 cannot be
used as a protection line. This impacts datafill for table RCSINV, since the
RCSINV (continued)
SMS P-side port to which a protection line connects is datafilled and cannot be
datafilled as the protection line port.
Before changing the C-side peripheral to which a RCS (SLC96) is attached,

the PROT LINE must be offline. The following error message is generated
depending upon which peripheral (SMS or SMSR) fails the port status check.
If the SMS/SMSR to which the RCS is currently attached has the port that the
PROT LINE uses in an inservice state, the following error message appears at
the MAP:
PROT LINK MUST BE OFFL/MBSY
If the port of the SMS/SMSR that the PROT LINE is moving to is in a state
other than OFFLINE, the following message appears at the MAP:
PROT LINK OF THE RCS MUST BE OFFLINED
If any DS-1 line has channels that are part of a nailed-up cross-connection, that
is, the endpoint in table PSNAILUP is listed as a channel rather than a line, no
RCS can be attached to this line in table RCSINV.
The SMSR specified in the PMT field must already have been datafilled in
tables LTCRINV and LTCRPINV.
Changing the fields ABINFO, CDINFO, or CSPMNO disables call processing

on the associated RCS, even after it is returned to service. When one or more
of these fields are changed, the following message appears at the MAP:
WARNING: STATIC DATA NOT UPDATED FOR SMS (SMS number) YOU MUST
BSY AND RTS THE SMS
To restore call processing on the RCS, the SMS must be busied and returned
to service, the inactive unit of the SMS must be busied and returned to service
followed by two consecutive SWACTs.
Changing other fields in table RCSINV does not disable call processing on the
associated RCS, but if Central Control is not able to communicate with the
SMS because the SMS is busy, static data is not updated, and the following
message appears at the MAP:
WARNING: STATIC DATA NOT UPDATED FOR SMS (SMS number)
Returning the SMS to service properly updates static data.
Some special notes on datafilling the table RCSINV follow:
297-8021-351 Standard 05.02 May 2001

RCSINV (continued)
When an inhibit lead is used, tables SCGRP and SDGRP must be datafilled
before table RCSINV.
If operating company personnel try to add a new peripheral with the same
SITE/FRAME/UNIT information as an existing peripheral, the following error
message appears:
ERROR: KEY has already been used KEY RCSNO of type

LINE_MODULE_KEY must be unique Use different SITE/FRAME/UNIT
An SMS DS-1 interface card has two ports for DS-1 lines. Two DS-1 lines
leading from the same SMS DS-1 card should connect to different RCS
modules. With one DS-1 line connected, an interface card can be removed
without disrupting ongoing calls as the connected DS-1 links are protection
switched.
To reposition a DS-1 link on a RCS, all DS-1 links on the RCS must be
repositioned. The DS-1 links, except the one that needs repositioning, can be
returned to their original positions after the move. When all DS-1 links (SMS
ports) are being used and one link must be repositioned, the RCS must be
deleted, then added to the system.
When the entry for the SCSDUSED field is Y (yes), indicating that a test pair
inhibit lead is used, additional fields must be datafilled. Field INHSCGRP
indicates which scan group of table SCGRP contains the scan point used for
the inhibit lead function. This scan point is datafilled in field INHSCPT. Field
INHSDGRP indicates which SD group in table SDGRP contains the SD point
used for the inhibit lead function. This SD point is datafilled in field
INHSDPT.
SD and scan circuit packs each contain two groups. A group holds seven
points. Previously, if one scan or SD point was used for the inhibit lead
function, all points in that group became dedicated to the inhibit lead function.
With the four fields INHSCGRP, INHSCPT, INHSDGRP, and INHSDPT used
for datafill, entire scan or SD groups need not be dedicated for the inhibit lead
function.
All spaces in the text string entered in field MISCTEXT must be represented
by underscores. The underscores are replaced by blanks before being
displayed. If blanks are used instead of underscores, all text after the blank is
truncated. For example, a text such as DOOR OPEN would appear as DOOR,
while text such as DOOR_OPEN would appear as DOOR OPEN. The text
string must not exceed 16 characters.
RCSINV (continued)
When the alarm occurs to which the text string applies, the DMS switch
generates a PM128 log that contains the text string. Similarly, posting the RCS
on which the alarm has occurred and entering the command string QUERYPM
FLT results in the text appearing at the MAP display.
The MTAOWNER field no longer exists in table RCSINV. Refer to tables

MTAVERT, MTADRVE, and MTAHORIZ for details on configuring a
metallic test access with remote and peripheral modules. Attempting to delete
an RCS that is associated with a vertical in table MTAVERT results in the
following error response:
CANNOT BE DELETED UNTIL UNASSIGNED FROM VERTICAL ON MTA
Frequency selective ringing is supported for single-party, two-party,

four-party, and Meridian Digital Centrex lines. The frequencies used depend
on how an option plug is set on the FSR card.
If the RCS or one of its dependencies failed to register with the system
recovery controller (SRC), the following message appears. The tuple is
rejected because there are no adequate means of recovering nodes that are not
registered with the SRC during restarts and SWACTs.
The message also can be displayed when adding a new RCS or when
attempting a tuple change to reregister an RCS that has been deregistered from
the SRC because of a dependency corruption during a previous node relocation
attempt:
Could not register the RCS to the system recovery controller.
If, while attempting to move an existing RCS to a new C-side peripheral (SMS
or SMSR), corruption of the node's C-side dependency occurs and the node is
deregistered from the SRC, the following error message appears. The tuple is
rejected. Attempt a nil change on the tuple so that an attempt is made to
register the node with the SRC.
Node has been deregistered from the System Recovery Controller.

Attempt a nil change on the tuple to register the node with the
SRC.
If a failure occurs in the SRC while attempting to move an existing RCS to a

new C-side peripheral (SMS or SMSR), the following error message appears.
When this message appears, either the dependency on the old C-side
peripheral could not be deleted or the dependency on the new C-side peripheral
could not be added. The tuple is rejected.
Could not update system recovery dependency.
297-8021-351 Standard 05.02 May 2001

RCSINV (continued)

The following tables must be datafilled before table RCSINV.
SITE
LTCPSINV
An entry in table LTCPSINV is added automatically when an XPM is added

to table RCSINV. All the corresponding P-side links in table LTCPSINV
initially default to NILTYPE. P-side links that do not have hardware assigned
must remain NILTYPE. The existence of unequipped software assigned
P-side links generates service-affecting problems such as no dial tone, cutoff
issues and noisy transmissions.
Table size
Memory is dynamically allocated for up to 255 entries for the NT40 switch and
1000 entries for SuperNode switches.
Datafill
The following table lists datafill for table RCSINV
Subfield or
RCSNO see subfields Remote concentrator module number

This field consists of subfields SITE, FRAME,
and UNIT.
SITE alphanumeric Site

(4 characters)
Enter the location of the RCS. There is no
default value, and the first character of the site
name must be alphabetic.
Note: Valid SITE names are dependent on

the value of parameter
UNIQUE_BY_SITE_NUMBERING in table
OFCENG.
RCSINV (continued)
Subfield or
FRAME 0 to 127or0 to Frame

511
Enter the remote concentrator module frame
number, which is not a physical frame but a
software identity. All RCS modules sharing
the same metallic test pair are assigned the
same frame number. The maximum frame
number is 127 for NT40 switches and 511 for
SuperNode switches.
UNIT 0 to 9 Unit
Enter the remote concentrator module unit
number.
ADNUM 0 to 4095 Administrative number

(BCS35-)
represent the administrative number for an
associated PM.
FRTYPE RCE Frame type

Enter the frame type on which the peripheral
module equipment is mounted.
FRNO 0 to 511 Frame number

Enter the frame number of the RCS. This
number should be unique by office.
SHPOS 0 to 77 Shelf position

Enter the position of the RCS control shelf in
inches above the floor level.
FLOOR 0 to 99 Floor
Enter the floor on which the peripheral
module frame is located.
ROW A to HJ to NP Row
to ZAA to
Enter the row on the floor in which the
HHJJ to
peripheral module equipment frame is
NNPP to ZZ
located.
297-8021-351 Standard 05.02 May 2001

RCSINV (continued)
Subfield or
FRPOS 0 to 99 Frame position

Enter the position in the row of the peripheral
module equipment frame.
LOAD alphanumeric Load

Enter the name given to the issue of
peripheral module software. The RCS does
not require a load, so this field is datafilled as
No_Load.
CSPMNO see subfields C_side peripheral module number

This field consists of subfields PMT and
EXTPMNO.
PMT SMS or Peripheral module type

SMSR
Enter the type of peripheral module to which
the RCS is attached.
EXTPMNO 0 to 127 Peripheral module number

Enter the peripheral module number to which
the RCS is attached.
An entry outside of this range is invalid.
ABINFO see subfields AB shelf group information

This field is composed of subfields
SHLFGRPMODE, XPMPORT and
SHLFGRPMODE(MODE2) refinement field
LOOPTEST.
SHLFGRPMOD MODE1,MOD Mode

E E2, MODE3,
Enter the mode of operation of shelf group
or NILMODE
AB. NILMODE is technically unsupported
and not recommended. If Mode2 is entered,
the LOOPTEST field is prompted for and
must be datafilled.
RCSINV (continued)
Subfield or
XPMPORT vector of up to C-side link information

2 (0 to 19)
Enter the SMS P-side ports to which C-side
entries
links ABLK0 to ABLK1 of the RCS are
assigned. Since this is a vector (at least one
entry or at most two entries), enter $ to
terminate the vector. For MODE2 and
MODE3 use only ABLK0, while for MODE1
use ABLK0 when equipped with one shelf or
ABLK0 and ABLK1 when equipped with two
shelves.
LOOPTEST Y or N PCM looping test

Enter Y (yes) if the PCM Looping Test is run
on a DS-1 channel when it is assigned to
handle a call. Otherwise, enter N (no). This
test consists of the SMS sending known PCM
samples over the DS-1 channel to the RCS,
which returns complemented samples back to
the SMS. The SMS compares the sent and
received samples, and if satisfactory, the test
passes.
If the test fails, a minor alarm is raised, and
the DS-1 channel and associated line card
are locked out from further call processing.
The DS-1 channel and line card are tested
periodically for proper operation and returned
to service if they pass.
If a second PCM Looping Test fails on a shelf
group, a major alarm is raised, and the shelf
group is taken from service. A steady PCM
Looping Test failure on one DS-1
channel/card combination indicates a bad line
card. Failures on multiple channels indicate a
bad TAU card.
CDINFO see subfields CD shelf group information

This field consists of subfields
SHLFGRPMODE, XPMPORT and
SHLFGRPMODE(MODE2) refinement field
LOOPTEST.
297-8021-351 Standard 05.02 May 2001

RCSINV (continued)
Subfield or
SHLFGRPMOD MODE1 Mode

E MODE2MOD
Enter the mode of operation of shelf group
E3orNILMOD
CD. NILMODE is technically unsupported
E
and not recommended as datafill. If MODE2
is entered, the LOOPTEST field is prompted
for and must be datafilled.
XPMPORT vector up to 2 C-side link information

(0 to 19)
Enter the SMS P-side ports to which C-side
entries
links CDLK0 to CDLK1 of the RCS are
assigned. Since this is a vector (at least one
entry or at most two entries), enter $ to
terminate the vector. For MODE2 and
MODE3 use only CDLK0, while for MODE1
use CDLK0 when equipped with one shelf or
CDLK0 and CDLK1 when equipped with two
shelves.
LOOPTEST Y or N PCM looping test

Enter Y (yes) if the PCM Looping Test is run
on a DS-1 channel when it is assigned to
handle a call. This test consists of the SMS
sending known PCM samples over the DS-1
channel to the RCS, which returns
complemented samples back to the SMS.
The SMS compares the sent are received
samples, and if satisfactory, the test passes.
If the test fails, a minor alarm is raised, and
the DS-1 channel and associated line card
are locked out from further call processing.
The DS-1 channel and line card are tested
periodically for proper operation and returned
to service if they pass.
If a second PCM Looping Test fails on a shelf
group, a major alarm is raised, and the shelf
group is taken from service.
A steady PCM Looping Test failure on one
DS-1 channel/card combination indicates a
bad line card. Failures on multiple channels
indicate a bad TAU card.
RCSINV (continued)
Subfield or
RNGTYPE C, F, S, Ring type

UNASSIGNE
Enter the type of ringing assigned to the
D, C30, CSR,
remote concentrator module: coded (C),
or C3D
frequency (F), superimposed (S), unassigned
(UNASSIGNED), C30 or coded
superimposed ringing (CSR). Field
RNGDATA must be datafilled C3D for Japan.
This provides the Japanese ringing scheme
of 1 on and 2 off for a 3 second basic cycle.
The C3D value is only datafillable in loads
containing the NTXZ08AA feature package.
ACU WP1, WP1B Alarm control unitEnter the type of alarm

control unit card.
PROTINFO see subfields Protection information

This field consists of subfield PROT and
PROT(Y) refinement subfield PORT.
PROT Y or N Protection
Enter Y (yes) if the RCS has a protection line.
Otherwise, enter N (no). If the entry for this
field is Y, then enter the PORT number.
PORT 0 to 19 Port
Enter the SMS P-side port of the protection
line.
SCSDINFO see subfields Scan and SD point information

This field consists of subfield SCSDUSED
and SCSDUSED(Y) refinement subfields
INHSCGRP, INHSCPT, INHSDGRP and
INHSDPT.
SCSDUSED Y or N Scan and SD points used

Enter whether an inhibit lead (SD and scan
points used) is required for the RCS. If the
entry for this field is Y (yes), then the
remaining fields in this table must be
datafilled.
297-8021-351 Standard 05.02 May 2001

RCSINV (continued)
Subfield or
INHSCGRP 0 to 511 Inhibit scan group

Enter the number of the scan group, defined
in table SCGRP, that contains the scan point
used for the inhibit lead function.
INHSCPT 0 to 6 Inhibit scan point

Enter the number of the scan point used for
the inhibit lead function.
INHSDGRP 0 to 511 Inhibit signal distribution group

Enter the number of the SD group, defined in
table SDGRP, that contains the SD point
used for the inhibit lead function.
INHSDPT 0 to 6 Inhibit signal distribution point

Enter the number of the SD Point used for the
inhibit lead function.
MISCTEXT alphanumeric Miscellaneous text

(up to 16
Enter the text associated with the
characters)
power/miscellaneous alarm. Use the
underscore (_) in place of blanks, otherwise,
text appearing after the blanks is truncated.
The underscores are converted to blanks
prior to being displayed. The text entered
appears in PM128 logs and in selected MAP
displays when the associated alarm occurs.
ALMSEVER major or minor Alarm severity

Enter the severity associated with the alarm.
LOCATION alphanumeric Location

(up to 32
Identify the remote location, or address, of the
characters)
RCS.
Datafill example
The example shows assignments for RCS module 1, unit 2 located at site
REM2 and linked to the host office by ports 17 and 18 in MODE1 and port 12
in MODE2 of SMS 9. The PCM Looping Test is not enabled for the Mode2
shelf group. SMS 9 has no protection line equipped. The RCS uses an inhibit
RCSINV (end)
lead, and the scan and SD points used for this lead are located in scan group 9
and SD group 8, respectively. The text for the power/miscellaneous alarm is
DOOR OPEN. It is a minor alarm. The remote location , or address of the
RCS is GARB.
Input is shown vertically due to space limitations.
MAP display example for table RCSINV
RCSNO ADNUM FRTYPE FRNO SHPOS FLOOR ROW FRPOS LOAD

CSPMNO ABINFO CDINFO RNGTYPE ACU
PROTINFO SCSDINFO MISCTEXT ALMSEVER
LOCATION
________________________________________________________
REM2 01 2 2 RCE 29 48 2 A 4 NO_LOAD

SMS 9 MODE1 (17) (18)$ MODE2 (12)$ N S
WP1
N Y 9 4 8 0 DOOR_OPEN MINOR
GARB
Table history
NA005
Added several error messages to indicate that a tuple was rejected because
some part of the SRC registration process failed.
BCS36
Added field LOCATION for the purpose of identifying the remote location, or
address, of the RCS, in accordance with feature AF4936.
This section contains dump and restore information for table RCSINV.
Dump and Restore

Prior to BCS35, tuples in peripheral OM groups LMD and UTR were grouped
together by node type and these groups of tuples had a defined order within the
OM group. For upgrades from a BCS less than BCS35 to a BCS35 or greater,
the ADNUMs will be sequentially assigned using this method. Any
subsequent upgrades after the ADNUMs have been assigned will preserve the
currently assigned ADNUM.
297-8021-351 Standard 05.02 May 2001

RCTALM
Table name
Remote Concentrator Terminal Alarm Table
Table RCTALM defines the alarms and their reporting for the remote
concentrator terminal (RCT).
This table is datafilled by default. Changes are needed if the character strings
that are required to be written to the logs and displayed in the top banner of the
MAP display are different from the default form.
Operating-company-defined log and top banner character strings must be

representative of the alarm. Datafill for table RCTALM is only required for
user assignable alarms. Alarms that are supported by table RCTINV are listed
in table Table , "Alarms supported by table RCTALM" on page -461.
Alarms supported by table RCTALM (Sheet 1 of 2)
RCTALM Source Alarm description
AC Rectifier Loss of AC voltage, rectifier failure or shutdown
BAT Battery Battery voltage below 47 volts
CPF 5 to 12v converter Loss of output voltage
DFA A DIGR circuit card Loss of frame synchronization in digroup A
DFB B DIGR circuit card Loss of frame synchronization in digroup B
DOOR Switch on door Door open
FUSE Fuse Defective fuse
LFA A RPTR circuit card Signal loss or high bipolar violation rate on DS-1 line
(see note 1) A
LFB B RPTR circuit card Signal loss or high bipolar violation rate on DS-1 line
(see note 1) B
LFP Protection repeater Signal loss or high bipolar violations on protection

circuit card (note 1) DS-1
Note 1: These alarms are generated only if the repeaters are capable of providing correct
outputs to the RCT's alarm cards.
Note 2: The ring generator excessive load or grounded alarm is available only with QPP430B
generator cards.
RCTALM (continued)
Alarms supported by table RCTALM (Sheet 2 of 2)
RCTALM Source Alarm description
LPF Line power converter Power converter shutdown
RFA Ringing fuse Defective ringing distribution fuse
RMJ Ring generator Loss of ringing voltage or synchronization;

(see note 2 ) grounded or excessive load (major alarm)
RMN Ring generator Failure of one of the two generators (minor alarm)
TEM Thermostats Temperature over 50C or under 0C
SPARE(4) user assignable User assignable
Note 1: These alarms are generated only if the repeaters are capable of providing correct
outputs to the RCT's alarm cards.
Note 2: The ring generator excessive load or grounded alarm is available only with QPP430B
generator cards.

The following tables must be datafilled before table RCTALM.
LTCPSINV
RCTINV
Table size
0 to 255 tuples
Memory for this table is dynamically allocated.
297-8021-351 Standard 05.02 May 2001

RCTALM (continued)
Datafill
The following table lists datafill for table RCTALM.
Field descriptions
Subfield or
RCTALM AC, BAT, Remote concentrator terminal alarm

CPF, DFA,
Enter the key for the alarm to be changed or
DFB, DOOR,
assigned.
FUSE, LFA,
LFB, LFP, See the 1st table, Alarms supported by table
LPF, RFA, RCTALM for a description of each alarm.
RMJ, RMN,
TEM,
SPARE1,
SPARE2,
SPARE3,
SPARE4
LOGDISP alphanumeric Log display

(1 to 32
Enter the log entry character string required
characters)
for the specified alarm key.
MTCDISP alphanumeric Magnetic tape center display

(1 to 6
Enter the top banner display character string
characters)
required for the specified alarm key.
ALMTYPE CR, MJ, MN, Alarm type

or NA
Enter the alarm type as follows: CR (critical
alarm), MJ (major alarm), MN (minor alarm),
or NA (no alarm).
Datafill example
The default datafill for table RCTALM is shown below. Datafill information
other than the RCTALM key field can be modified by the operating company.
RCTALM (end)
MAP display example for table RCTALM
RCTALM LOGDISP MTCDISP ALMTYPE

________________________________________________________
DFA Digroup A failure RCTGIG MJ

DFB Digroup B failure RCTDIG MJ
LFA DS1 line A failure RCTLFA MN
LFB DS1 line prot failure RCTLFB MN
LFP DS1 line prot failure RCTLFP MN
LPF Line power failure RCTLPC MJ
RMJ Ring generator fail RCTRNG MJ
RMN Ring generator fail RCTRNG MN
CPF Power converter fail RCTCPF MJ
AC Power fail RCTAC MN
BAT Battery Failure RCTBAT MJ
TEM Temperature alarm RCTTEM MJ
DOOR Door alarm RCTDOR MN
FUSE Fuse alarm RCTFUS MJ
RFA Ring fuse alarm RCTFUS MJ
SPARE1 * ** **
SPARE2 * ** **
SPARE3 * ** **
SPARE4 * ** **
297-8021-351 Standard 05.02 May 2001

RCTINV
Table name
Remote Concentrator Terminal Inventory Table
Table RCTINV lists information for remote concentrator terminal (RCT) line
peripheral modules (PM). Remote Concentrator Terminals (RCT) are line
PMs used by the DMS-1 system that can handle traffic for up to 256 lines. The
DMS-1 concentrator system consists of an RCT and a control concentrator
terminal (CCT). The subscriber carrier module-100 rural (SMR) PM replaces
the CCT and provides a direct digital interface between RCTs and the
DMS-100 host.
Table RCTINV lists the following assignment data for each RCT unit:
the site name of the remote location as assigned by the operating company
the frame/unit combination that uniquely defines the RCT module number
the administrative number associated with the PM
the frame type on which the PM is physically mounted
the frame number of the RCT
the floor, row on the floor, frame position in the row, and the shelf position
for each unit associated with an RCT equipment frame
the PM type and number to which the RCT attaches
the RCT C-side to SMR P-side link assignments
the coded, superimposed, and frequency ringing data
the type of test capability (digital or metallic)
the protection switching information
Subscriber loop testing is optional. The RCTs are capable of performing

subscriber line test digital (SLTD) tests, subscriber line test access (SLTA)
tests, or no tests.
The SLTD capability is synonymous with RCT card QPP423. It provides test
equipment in the RCT to measure and digitize the standard voltage, resistance,
and capacitance of the subscriber loop.
The SLTA capability is provided by LTA card QPP568A used with a shelf
bypass assembly (ED7208-32G6). This capability enables metallic test access
(MTA) and bridging onto subscriber lines. The SLTA configuration can use a
RCTINV (continued)
line test unit (LTU) and trunk test unit (TTU) as part of subscriber loop and
line card test procedures.
A protection line is a DS-1 line that occupies one DS-1 P-side port of an SMR.
This line connects up to six RCTs in daisy-chain fashion and serves as a spare
DS-1 that can be rapidly switched into use to replace a failed DS-1.
Although a protection line can connect to more than one RCT, no two RCTs
can be simultaneously connected to the same protection line. Field
PRIORITY in table RCTINV indicates which RCT connects to the protection
line if links to more than one RCT fail. The SMR P-side ports must have
access to this protection information to update the node table used for message
routing and to correctly interpret autonomous RCT protection switches.
If connected to the same SMR, RCTs that use frequency selective ringing must
use the same set of frequencies.

The following tables must be datafilled after table RCTINV.
LTCINV
LTCPSINV
Table size
0 to 255 tuples
Datafill
The following table lists datafill for table RCTINV.
Subfield or
RCTNO see subfield Remote concentrator terminal number. This

field consists of subfields SITE, FRAME, and
UNIT.
SITE alphanumeric Site. Enter the site name of the RCT location.
(1 to 4 No default value exists. The first character of
characters) the site name must be alphabetic. The entry
here must also appear in table SITE.
297-8021-351 Standard 05.02 May 2001

RCTINV (continued)
Subfield or
FRAME numeric Frame. Enter the remote concentrator

(0 to 511) terminal frame number. For NT40, the range
is 0 to 127. For SuperNode, the range is 0 to
511.
UNIT numeric Unit. Enter the remote concentrator terminal

(0 to 9) unit number.
ADNUM numeric Administrative number. Enter the

(0 to 4095) administrative number associated with the
PM.
FRTYPE RTR Frame type. Enter the frame type on which

the PM equipment is mounted.
FRNO numeric Frame number. Enter the frame number of

(0 to 511) the RCT. This number must be unique for
each office.
SHPOS numeric Shelf position. Enter the position of the RCT

(0 to 77) control shelf, measured in inches above the
floor level.
FLOOR numeric Floor. Enter the floor on which the PM frame

(0 to 99) is located.
ROW A to A, AA to Row. Enter the row on the floor in which the

ZZ, except I, PM equipment frame is located.
II, O, OO
FRPOS numeric Frame position. Enter the bay position in the

(0 to 99) row of the PM equipment frame.
LOAD alphanumeric Load. Enter the NO_LOAD for all RCTs.

(up to 8
characters)
CSPMNO see subfields C-side peripheral module number. This field

consists of subfields PMT and EXT_PMNO.
PMT SMR, RCC2, Peripheral module type. Enter the type of PM

or SRCC to which the RCT is attached.
RCTINV (continued)
Subfield or
EXT_PMNO numeric Peripheral module number. Enter the PM

(0 TO 63) number to which the RCT is attached. Other
values are not valid.
LKINFO numeric C-side link information. Enter the SMR port

(0 to 19) numbers on which the RCT is assigned (a
(vector of up vector of up to two entries). The SMR port
to 2 entries) numbers correspond to C-side links LK0 to
LK1 of the RCT. Terminate the vector with $.
CONTMARK + or $ Continuation mark. Enter + if additional data

for this tuple is contained in the next record.
Otherwise, enter $ to indicate the end of the
tuple.
RNGDATA see subfields Ring data. This field consists of subfields

RNGTYPE and FRQUENCY.
RNGTYPE C, C30, C3D, Ring type. Specify the type of ringing

CSR, F, S, assigned to the remote concentrator module
UNASSIGN-E (RCM). Enter C (coded at 20 Hz), CSR
D (coded special ringing), C30 (coded at 30 Hz),
C3D, F (frequency) and datafill refinement
FRQUENCY, S (superimposed), or
UNASSIGNED (no ring type assigned).
FRQUENCY numeric Ringing frequencies. If the entry in field

(0 to 255) RNGTYPE is F, enter a vecotr of four values
from 0 to 255. This field consists of subfields
A, B, C, or D. See table LMRNG for the
definition of each frequency. All RCTs that
employ frequency selective ringing and are
connected to the same SMR must use the
same set of frequencies.
SLTINFO see subfield Subscriber loop test information. This field

consists of subfield SLTMODE.
297-8021-351 Standard 05.02 May 2001

RCTINV (continued)
Subfield or
SLTMODE SLTA, SLTD, Subscriber loop test mode. Enter SLTA for
NONE subscriber line test access, SLTD for
subscriber line test digital, or NONE for no
testing capability.
LINEAUDT Y or N Line audit. Enter Y (yes) for a running audit in

the SMR background or manual test mode.
Enter N (no) to disable the background audit
and stop manual requests of the audit.
Note: Manual test mode is invoked by the

command TST at the LTU or TTU levels of the
MAP display.
Datafill example
An example of datafill for table RCTINV follows. The example shows
assignments for an RCT that is located at site REM1. The frame designation
is 01 and the unit number is 2. The PM administrative number is 1. The RCT
links to SMR 9 through SMR ports 17 and 18. The RCT employs frequency
selective ringing and SLTA (metallic test access). RCT 2 does not have
protection switching. An RCT common equipment audit is enabled from the
MAP display with field LINEAUDT.
MAP display example for table RCTINV
RCTNO ADNUM FRTYPE FRNO SHPOS FLOOR ROW FRPOS LOAD

CSPMNO LKINFO RNGDATA SLTINFO
LINEAUDT
_________________________________________________________
REM1 01 2 1 RTR 29 48 2 A 4 NO_LOAD
SMR 9 (17) (18)$ F 20 30 40 50 SLTA
Y
Table history
NA007
Warning message is added to table RCTINV, field LKINFO. The message is
displayed when only two DS-1 message links assigned in table RCTINV and
both DS-1 message links are assigned to the same host DS-1 pack. In table
RCTINV all C-side links can be message links.
RCTINV (continued)
NA005
Error message was added to indicate that a tuple is being rejected because
some part of the SRC registration process failed.
The following errors and warnings can occur in table RCTINV when datafill
protocol is violated.

include: {0 1}, {2 3}, {4 5}, {6 7}, {8 9}, {10 11},
{12 13}, {14 15}, {16 17}, {18 19}. Each message
Action: When datafilling message links in RCTINV, separate the DS-1

message links by a minimum of two slots to ensure that both message links are
not assigned to the same host DS-1 card. An E1 outage occurs if both message
links are assigned to the same faulty card.
CANNOT BE DELETED UNTIL UNASSIGNED FROM VERTICAL ON MTA
Action: Remove an RCT from MTAVERT before adding it to table RCTINV.
WARNING: CHANGING THIS RCT'S SLTMODE REQUIRES IT BE

REMOVED FROM TABLE MTAVERT
Action: If an RCT is associated with a vertical in table MTAVERT, remove the

RCT from table MTAVERT before changing field SLTMODE in table
RCTINV.
ERROR: KEY has already been used KEY RCTNO of type

LINE_MODULE_KEY must be unique Use different
SITE/FRAME/UNIT
Action: Do not add a new peripheral with the same SITE/FRAME/UNIT

information as an existing peripheral.
Node has been deregistered from the System Recovery

Controller.
Attempt a nil change on the tuple to register the node with
the SRC.
Action: While attempting to move an existing RCT to a new C-side peripheral

(SMS or SMSR), if corruption of the node's C-side dependency occurs and the
297-8021-351 Standard 05.02 May 2001

RCTINV (end)
node is deregistered from the system recovery controller (SRC), the tuple is
rejected. Attempt a nil change on the tuple to register the node with the SRC.
RCUALRMS
Table name
Remote Carrier Urban Alarms Table
Table RCUALRMS contains a list of 12 spare alarm codes and text strings for
each remote carrier urban (RCU). The specified text strings appear in log
reports and on MAP displays when the problems they describe occur. The
following information appears in table RCUALRMS:
The site name of the remote location (as assigned by the user) is listed.
This site name, which must also exist as an entry in table SITE, has no
default value and must be datafilled.
The frame number is listed. This is a logical number used to map the RCU
in memory.
The unit number is listed. This is a logical number used to map the RCU
in memory. Each RCU has a unit number.
The spare alarm code is listed. This is a value from 120 to 131 that
corresponds to a particular spare alarm.
The alarm text is listed. Alarm text consists of either a default or
customer-assigned text string that is associated with the alarm. The default
text strings appear in table Table , "Alarm default text strings" on page
-472. Enter the string NIL_TEXT in table RCUALRMS to obtain these
defaults.
Alarm default text strings (Sheet 1 of 2)
Code Category Default text Alarm description
1 20 Major Open door Spare 1 or open door
1 21 Major Low battery voltage Spare 2 or low battery voltage
1 22 Major Temperature alarm Spare 3 or temperature too high or

low
1 23 Major Blown fuse or TSU failed Spare 4, fuse on QPP373 blown, or

timing supply unit failed
1 24 Major Loss of power or AC Spare 1, AC rectifier failed, or loss of

rectifier failed commercial power
297-8021-351 Standard 05.02 May 2001

RCUALRMS (continued)
Alarm default text strings (Sheet 2 of 2)
Code Category Default text Alarm description
1 25 Major Blown fuse or bypass Spare 2, fan or actuator fuse, or

breaker alarm bypass breaker operation alarm
1 26 Major Spare 3 alarm Spare 3
Consider the following when datafilling table RCUALARMS:

Entering a tuple in table RCUINV results in the allocation of a tuple in
table RCUALRMS. Similarly, deletion of a tuple in table RCUINV results
in the deletion of the corresponding tuple (as identified by the RCU) from
table RCUALRMS. Tuples cannot be added to or deleted from table
RCUALRMS directly.
All spaces must be represented by underscores in any text string entered
into table RCUALRMS. The underscores are replaced with spaces before
being displayed. If underscores are not used, the text display is truncated
at the first blank. For example, SMOKE_DETECTED appears as SMOKE
DETECTED, but SMOKE DETECTED appears as SMOKE.
Initially, all spare alarms are set with the text string NIL_TEXT. When
NIL_TEXT is associated with a spare alarm, the default text string is used
for that alarm.
Up to 25 unique text strings can be entered in table RCUALRMS (using
the same unique string for multiple RCU modules counts as one unique
string).
Spare alarm text strings entered in table RCUALRMS must be between 1
and 16 characters in length.
The following errors and warnings can occur when datafill protocol is
violated:
STORE UNAVAILABLE FOR MORE UNIQUE ALARM TEXTS. CHECK EXISTING

TEXTS IN TABLE
The system prevents the assignment of another unique spare alarm text string
in table RCUALRMS when the maximum of 25 have already been assigned.
ADDITIONS/DELETIONS NOT ALLOWED IN RCUALRMS
Tuples cannot be added to or deleted from table RCUALRMS; they can only
be updated.

Table DRCUINV must be datafilled before table RCUALRMS.
Table size
Each RCU spare alarm text string requires eight words of memory. Since 25
unique alarm texts can be entered in table RCUALRMS and two words are
required for a protected text counter and string range type, the maximum store
required for the table is 202 words of memory.
Datafill
The following table lists datafill for table RCUALRMS.
Subfield or
RCUNO see subfields Remote carrier urban number

This is the key field of the table. It uniquely
identifies each RCU entry. This field consists
of subfields SITE, FRAME, and UNIT.

(4 characters)
Enter the site name to indicate the location of
the RCU. The first character of the site name
must be alphabetic, and the site name must
exist in table SITE.
No default value exists for this field.
FRAME 0 to 511 Frame

Enter the logical frame number of the RCU.
UNIT 0 to 9 Unit
Enter the logical unit number of the RCU.
297-8021-351 Standard 05.02 May 2001

Subfield or
RCUSPALM see subfields Remote carrier urban spare alarm

This field is a vector of up to 12 multiples of
subfields ALMCODE and TEXT. Datafill
subfields ALMCODE and TEXT to assign
each spare alarm.
Enter + in the CONTMARK subfield if
additional subfield multiples follow on the next
line. Enter $ in the CONTMARK field
following the last ALMCODE and TEXT
entries.
ALMCODE 120 to 131 Alarm code

Enter the alarm code corresponding to a
spare alarm.
TEXT alphanumeric Alarm text string

(vector of up
Enter a text string for the specified alarm
to 16
code. Use underscores instead of blanks to
characters)or
avoid truncation of the text after the first blank.
NIL_TEXT
To use the default text string, enter
NIL_TEXT.

Enter + if additional information for this vector
enter $ to indicate the end of the vector.
Datafill example
The following is an example datafill for table RCUALRMS.
The RCU is RCU0 00 0.
Two spare alarms are assigned to this RCU.
The first alarm uses the default text string associated with alarm code 120.
The default text string for this code is OPEN DOOR.
The second alarm has the customer-assigned text FLOODING.
RCUALRMS (end)
MAP display example for table RCUALRMS
RCUNO
RCUSPALM
_________________________________________________________
RCU0 00 0
(120 NIL_TEXT) (121 FLOODING)$
297-8021-351 Standard 05.02 May 2001

RCUINV
Table name
Remote Carrier Urban Inventory Table
Table RCUINV contains an inventory of remote carrier urban (RCU) modules
attached to a DMS-100 switch and information on each RCU.

The following tables must be datafilled before table RCUINV.
LTCINV
LTCPSINV
SITE
The subscriber carrier module-100 urban (SMU) to which the RCU attaches
must be datafilled in table LTCINV. P-side ports of the SMU must be datafilled
as DS-1 links in table LTCPSINV. The site name assigned to the host or
remote switching unit must be datafilled in field NAME in table SITE.
Table size
0 to 253 tuples (for NT40)
0 to 1000 tuples (for SuperNode)
Table RCUINV is initially set to 0 (zero) tuples. When the first tuple is
entered, the DMS system automatically allocates memory for 20 entries. Each
RCU requires 96 words of data store. When tuples are changed and data is
added to, or deleted from table RCUINV, static data must be updated in the
SMU.
RCUINV (continued)
Datafill
The following table lists datafill for table RCUINV.
Field descriptions for table RCUINV (Sheet 1 of 8)
Subfield or
RCUNO see subfields Remote carrier urban number. This is the key
field of table RCUINV and uniquely identifies
each RCU entry. This field consists of
subfields SITE, FRAME, and UNIT.
SITE alphanumeric( Site. Enter the site name. Site is the location
4 characters) of the RCU. No default value exists, and the
first character of the site name must be
alphabetic. The site must be entered in table
SITE.
FRAME numeric (0 Frame. Enter the logical frame number (0 to

to 511 or 0 to 511 for DMS SuperNode or 0 to 127 for
127) NT40).
UNIT numeric (0 Unit. Enter the logical unit number of the

to 9) RCU.
ADNUM numeric (0 Administrative number. Enter the

to 4095) administrative number associated with a
given peripheral module (PM).
FRTYPE RUB or RUC Frame type. Enter the frame type of the RCU:
RUB or RUC. RCU modules use either a
bay-type frame (RUB) or a cabinet-type frame
(RUC).
Any other entry is invalid.
FRNO numeric (0 Frame number. Enter the frame number of

to 511) the RCU.
SHPOS numeric (0 Shelf position. Enter the shelf position of the

to 77) RCU.
links by the number of links on the interface cards. This applies to all interface link types: DS-1, DS30,
297-8021-351 Standard 05.02 May 2001

RCUINV (continued)
Subfield or
FLOOR numeric (0 Floor. Enter the floor position of the RCU.

to 99)
ROW A to HJ to NP Row. Enter the row position of the RCU.

to ZAA to
HHJJ to
NNorPP to ZZ
FRPOS numeric (0 Frame position. Enter the RCU position

to 99) within the row.
CSPMNO see subfields C-side peripheral module number. This field

consists of subfields PMTYPE and
EXTPMNO.
PMTYPE SMU Peripheral module type. Enter the type of

peripheral module attached to the RCU: SMU
(subscriber carrier module-100 urban).
EXTPMNO numeric (0 Peripheral module number. Enter the SMU

to 127) number.
CSLNKTAB see subfields C-side link table. This field is a vector of up to

eight multiples of subfields CSLINK and
SMUPORT. If less than eight entries (links)
are entered, enter $ (dollar sign) to indicate
the end of the list. At least one link must be
entered (a message link). If only two links are
added, they must both be message links.
CSLINK numeric (1 C-side port number. Enter the C-side port

to 8) number of the RCU corresponding to links 1
through 8 to which the SMU attaches through
DS-1 links.
SMUPORT numeric (0 SMU P-side port number. Enter the P-side

to 19) port number of the SMU to which DS-1 links
attaches to the RCU.
RCUINV (continued)
Subfield or
RNGDATA see subfield Ring data. This field consists of subfield

RINGTYPE.
RNGTYPE C to F Ring type. Enter the type of ringing employed

by the RCU to ring its attached subscriber
lines. The RCU supports coded ringing and
frequency selective ringing (FSR).
If all subscribers have plain old telephone
service (POTS), enter C or F.
Enter C for coded ringing and go to field LTA.
Enter F for FSR and datafill refinement
FRQUENCY.
Entries outside the range indicated for this
field are invalid.
FRQUENCY 17, 25, 34, 50, Frequencies. If the entry in subfield

67, 20, 30, 42, RNGTYPE is F, datafill this refinement. Enter
54, 66, 16, 30, four frequencies from one of the sets of
42, 54, 66, 20, frequencies (the line card supports four
30, 40, 50, 60 different frequencies). For example, choose
the group containing frequencies 17, 25, 34,
50, and 67. Datafill four frequencies from this
group, for example, 17, 25, 50, and 67.
RCU modules connecting to the same SMU
that use FSR to ring subscriber lines must use
the same frequencies in the same order in
which they were datafilled. For example, if an
RCU module attached to SMU 5 uses FSR
and the datafilled frequencies are 20, 30, 40,
50, all other RCU modules connecting to
SMU 5 that use FSR ringing must also be
datafilled 20, 30, 40, 50 in field
FREQUENCIES.
297-8021-351 Standard 05.02 May 2001

RCUINV (continued)
Subfield or
LTA Y or N Line test access. Enter Y (yes) if a line test

access (LTA) card is present on the power
shelf of the RCU. Otherwise, enter N (no).
RLTP Y or N Remote line test processor. Enter Y if the

card is present in slots 9 and 10 of the RCU's
power shelf. This card allows remote line
testing and fault reporting through the
modem. It also uses the LTA card slot and
contains LTA functionality. Otherwise, enter
N.
RTAC Y or N Remote test access card. Enter Y if the

remote test access card is present.
Otherwise, enter N.
LINESHF1 Y or N Line shelf 1. Enter Y if line shelf 1 is

equipped; otherwise, enter N. If N is entered,
links 1 and 2 cannot be datafilled as
equipped.
CTRLSHF2 Y or N Control shelf 2. Enter Y if control shelf 2 is

equipped; otherwise, enter N. To equip
control shelf 2, line shelf 1 must be equipped.
DS-1 links need not be attached to line shelf
1.
If N is entered, configuration alarms are
suppressed for CE cards (CP extension,
switch, digroup, and supervisory), and links 7
and 8 cannot be datafilled as equipped.
RCUINV (continued)
Subfield or
LINESHF2 Y or N Line shelf 2. Enter Y if line shelf 2 is

equipped. Otherwise, enter N. To equip line
shelf 2, control shelf 2 must be equipped.
DS-1 links need not be attached to control
shelf 2.
If N is entered, configuration alarms for the

digroup cards are suppressed and links 1 and
2 cannot be datafilled as equipped.
SSM1 Y or N Special service module 1. Enter Y if special

service module (SSM) 1 is provisioned. This
SSM occupies shelf 6 and has a
corresponding bus extender equipped to
control shelf 1 in slot 1.
SSM2 Y or N Special service module 2. Enter Y if SSM 2 is

provisioned. This SSM occupies shelf 7 and
has a corresponding bus extender equipped
on control shelf 1 in slot 2.
SYSTMOPT see subfield System options. This field consists of subfield

SYSOPT.
SYSOPT O or S System options. To specify each system

option, enter the letter O and datafill
refinements AUTOTEST, INITALRM,
FAILSEN, and SSPRI.
To select system default values, enter S and
go to field DRTUTEST.
297-8021-351 Standard 05.02 May 2001

RCUINV (continued)
Subfield or
AUTOTEST Y or N Automatic system testing. If the entry in field

SYSOPT is O, datafill this refinement. Enter
Y to enable automatic system testing, which
executes switchover of RCU common
equipment (MP card excluded) and tests
RCU line and associated CE cards.
Enter N to disable automatic system testing.
Only switchover of common equipment
occurs when testing is invoked.
INTALRM Y or N Initialization alarm display. If the entry in field

Y to enable alarm output to the maintenance
card faceplate during initialization. Enter N to
disable alarm output.
FAILSEN Y or N Failure sensitivity level. If the entry in field

Y to enable the display of line card alarms
(types 1 through 4) produced by the
automatic system test.
Note: If field AUTOTEST is set to Y, set field

FAILSEN to Y as well.
RCUINV (continued)
Subfield or
SSPRI Y or N Special services priority. If the entry in field

Y to enable special-service priority. This
allows special-service calls to replace POTS
calls during channel reassignment. If all DS-1
channels are correctly operating DS-1 links
are occupied. Enter N to disable
special-service priority.
DRTUTEST Y or N Digital remote test unit test. If the entry in field

SYSOPT is S, datafill this refinement. Enter
Y to enable the digital remote test unit (DRTU)
test equipment and datafill refinements
DRTURCU and CBCKLEN. Enter N if there is
no DRTU equipped on the RCU and go to
field LOCATION.
DRTURCU see subfields DRTU location. This field identifies the RCU
on which the DRTU is equipped and consists
of subfields SITE, FRAME, and UNIT.
SITE alphanumeric( Site. Enter the site name. Site is the location
4 characters) of the RCU. No default exists and the first
character of the site name must be
alphabetic. Site must be entered in table
SITE.

127) NT40).
UNIT numeric (0 Unit. Enter the logical unit number of the

to 9) RCU.
297-8021-351 Standard 05.02 May 2001

RCUINV (continued)
Subfield or
CBCKLEN see subfields Call back LEN. This field identifies the line
circuit (LC) to which the DRTU connects the
call back path and consists of subfields SITE,
FRAME, UNIT, LSG, and CIRCUIT.
SITE alphanumeric( Site. Enter the site name. No default exists

4 characters) and the first character of the site name must
be alphabetic. Site must be entered in table
SITE.

127) NT40).
UNIT numeric (0 Unit. Enter the logical unit number.

to 9)
LSG numeric (0 Line subgroup. Enter the number of the line

to 23) subgroup.
CIRCUIT numeric (0 Line card circuit number. Enter the line card
to 31) circuit number of the line subgroup where the
card is assigned.
LOCATION alphanumeric Location. Enter the remote location (or

(up to 32 address) of the RCU in the DMS-100 switch.
characters)
Datafill example
An example of RCU assignment in table RCUINV follows.
The first part of the entry is the site, which is not optional in this case because
remotes are involved.
Next in the entry is the frame, which is a number between 0 and 511. This
frame number is logical and does not refer to an actual frame occupied by the
RCUINV (continued)
RCU. In this example, the frame number is 01. Following the frame number
is the unit field. In this example, it is 0 (zero).
The next six entries show the physical location of the RCU: frame type and
number, RCU shelf, floor, row, and row position. This is physical location
information and fields such as row or floor are often not relevant.
Following the location fields, fields PMTYPE and PMNO show that the RCU
connects to the SMU 60.
Field CSLNKTAB shows that RCU links 1 through 8 connect to the SMU.
The SMU P-side ports to which these links connect are shown.
The RCU employs coded ringing and has an LTA card. Line shelves 1 and 2
and control shelf 2 are provisioned. The standard system options are used.
The location is MER.
Note: Except for SSPRI, these system options require the maintenance
card.
The following example shows sample datafill for table RCUINV.
MAP display example for table RCUINV
RCUNO ADNUM FRTYPE FRNO SHPOS FLOOR ROW FRPOS CSPMNO
CSLNKTAB
RNGDATA LTA RLTP RTAC LINESHF1 CTRLSHF2 LINESHF2
SSM1
SSM2 SYSTMOPT DRTUTEST
LOCATION
__________________________________________________________HOST 01 0
0 RUB 0 0 0 A 0
SMU 60
(1 1) (2 2) (3 3) (4 4) (5 5) (6 6) (7 7) (8 8) $
C Y Y Y Y Y Y
N
N S N
MER
297-8021-351 Standard 05.02 May 2001

RCUINV (continued)
Table history
NA007
Added a warning note to table RCUINV on datafilling field CSLNKTAB. A
message is displayed by table control if an attempt is made to datafill multiple
message links that are assigned to the same interface card.
NA005
Error messages were added to indicate that a tuple is being rejected because
some part of the system recovery controller (SRC) registration process failed.
BCS36
Field LOCATION was added to table RCUINV in accordance with feature
AF4935 (TA RCUINV: New Tuple for Equipment Location). Additional error
and system response messages were added in accordance with feature AF4252
(ESMV ISDV SPECCOVV Link Reconfiguration).
This section provides information on datafilling table RCUINV for specific
applications, and product descriptive information related to table RCUINV.
If the RCU or one of its dependencies fails to register with the SRC, the
following error message appears. The tuple is rejected because there are no
adequate means of recovering nodes that are not registered with the SRC
during restarts and SWACTs.
Could not register the RCU to the system recovery controller
If a failure occurs in the SRC while attempting to move an existing RCU to a

new SMU or ESMU, the following error appears. This message implies that
either the dependency on the old SMU could not be deleted or the dependency
on the new SMU could not be added. The tuple is rejected.
Could not update system recovery dependency
The following message appears if a failure occurs in the SRC while attempting
to move an existing RCU to a new SMU or ESMU. This message indicates that
either the dependency on the old SMU could not be deleted or the dependency
on the new SMU could not be added. An attempt was made to restore the old
dependencies, but that attempt failed. The tuple is rejected and the RCU is
deregistered from the SRC because the dependencies are corrupt. Attempt a
nil change on the tuple so that an attempt is made to register with the SRC.
The RCU has been deregistered from the System Recovery

Controller.
RCUINV (continued)
The following error message appears if operating company personnel try to

add a new peripheral with the same SITE/FRAME/UNIT information as an
existing peripheral:
ERROR: KEY has already been used KEY RCUNO of type

LINE_MODULE_KEY must be unique Use different SITE/FRAME/UNIT
The following errors and warnings can occur when datafill protocol is violated:
The following message occurs when a switch operator tries to datafill an SMU
P-side port against an RCU C-side port, but the SMU port was previously
datafilled against another RCU or LDT.
EITHER ANOTHER RCU OR AN LDT IS USING SMU PORT X.
Table LTCPSINV contains DS-1 link information for the RCU. If datafilling
link information in table RCUINV, the information must match the
information in table LTCPSINV. DS-1 links must be datafilled as such in table
LTCPSINV.
ATTEMPT TO ATTACH LINK TO A NON-DS-1 PORT.
The switch operator must datafill at least one message link in table RCUINV.
If not, the following message appears:
AT LEAST ONE MESSAGE LINK MUST BE CONFIGURED.
The first message link added to the RCU cannot be deleted.
CANNOT DELETE MESSAGE LINK XX.
Two C-side RCU ports cannot be datafilled against the same SMU P-side port
in field CSLNKTAB.
CANNOT ATTACH BOTH LINKS TO THE SAME SMU PORT.
When FSR lines are datafilled in table LNINV for an RCU, the switch operator
cannot change the frequencies for that RCU. If an attempt is made to change
the frequencies, the following message appears:
CANNOT CHANGE FREQUENCIES WITH FSR LINES ATTACHED.
When FSR or MPDR lines are datafilled in table LNINV for an RCU, the
switch operator cannot change the ring type for that RCU. If an attempt is
made to change the ring type, the following message appears:
CANNOT CHANGE RNGTYPE WHILE X LINES ARE ATTACHED TO RCU.
297-8021-351 Standard 05.02 May 2001

RCUINV (continued)
Line shelf 1 must be equipped before control shelf 2 can be equipped. DS-1
lines need not be attached to line shelf 1. If an attempt is made to equip control
shelf 2 first, the following error message appears:
CONTROL SHELF 2 MAY BE EQUIPPED ONLY IF GROUP 1 LINE SHELF IS

EQUIPPED.
The DS-1 link must be placed offline using the MAP command OFFL before
adding it to table RCUINV. If not, the following message appears:
DS-1 CARRIER MUST BE OFFLINE TO ADD AN RCU.
The SMU port connected to the first message link (DS-1) added to the RCU
must be offline. If not, the following error message appears:
DS-1 CARRIER MUST BE OFFLINE WHEN UPDATING LINK XX.
If the switch operator tried to add a tuple, but the SMU (C-side PM) does not
exist as identified in the newly added tuple, the following message appears:
FAILED TO GET INDEX TO C-SIDE PM.
The RCU resides either on a bay-type frame (RUB) or a cabinet-type frame

(RUC).
FRAME TYPE MUST BE OF TYPE RUB OR RUC.
Every RCU employing frequency selective ringing and connected to the same
SMU must be datafilled with the same frequencies in the same order. If not,
the following message appears:
FREQUENCY MISMATCH. ALL RCUs ATTACHED TO THE SAME SMU WITH

FREQUENCY RINGING MUST USE THE SAME FREQUENCIES IN THE SAME
ORDER. THE FOLLOWING FREQUENCIES WERE USED INSTEAD OF THE ONES
ENTERED X X X X.
If the key already exists, indicating that the RCU has already been datafilled in
table RCUINV, the following message appears:
KEY ALREADY EXISTS.
The RCU must be placed offline using the MAP command OFFL before
deleting the RCU from table RCUINV. If not, the following message appears:
LINES STILL ATTACHED TO RCU.
RCUINV (continued)
At least one message link must be datafilled in table RCUINV. The first DS-1
channel of physical DS-1 links 3 and 4 contain message channels.
LINK 3 or 4 MUST BE CONFIGURED.
Control shelf 2 must be equipped before line shelf 2 can be equipped. DS-1
lines need not be attached to control shelf 2.
LINE SHELF 2 MAY BE EQUIPPED ONLY IF GROUP 2 CONTROL SHELF IS

EQUIPPED.
The DS-1 links or the RCU module must be manually busied, or the RCU
module must be taken offline before changing or deleting DS-1 links in table
RCUINV. If not, the following message appears:
LINKS THAT ARE BEING DELETED/CHANGED MUST BE MBSY OR THE RCU

OFFLINE/MBSY.
If more than two DS-1 links are datafilled in table RCUINV, both message
links must be datafilled because a backup message link must be present.
MUST CONFIGURE BOTH MESSAGE LINKS 3 AND 4 WHEN CONFIGURING TWO

OR MORE LINKS.
If changing links from an RCU to another SMU, the RCU must be manually
busied or offline, and SMU links (as shown in the table LTCPSINV: P-side
ports) must be offline.
NEW LINKS MUST BE OFFLINE AND RCU OFFL/MBSY TO CHANGE CSPMNO.

ONLY xxx RCUs MAY BE ATTACHED TO A PARTICULAR SMU. COUNT
EXCEEDED ON SMU XX.
Only C or F can be datafilled for the field RNGTYPE in table RCUINV. If an

entry other than C or F is datafilled, the following message appears:
RCU RNGTYPE MUST BE C OR F.
The PMTYPE datafilled in table RCUINV must be SMU. If not, the following
message appears:
RCU CAN BE ADDED TO SMU ONLY.
The RCU must be taken offline using the MAP command OFFL before
deleting it from table RCUINV. If the RCU is not taken offline, the following
message appears:
RCU MUST BE OFFLINE TO DELETE.
297-8021-351 Standard 05.02 May 2001

RCUINV (continued)
The site name must be a remote site name for RCU modules. If not, the
following message appears:
SITE DATA INCONSISTENT.
The RCU to be deleted is still assigned to a vertical in table MTAVERT. The

RCU must first be disassociated from this vertical before it can be deleted from
table MTAVERT. If the RCU is not disassociated from the vertical, the
CANNOT BE DELETED UNTIL UNASSIGNED FROM VERTICAL ON MTA.
An RCU that uses a DS-1 link with channels that are end-points on a
special-service connection cannot be added to table RCUINV.
SMU PORT PART OF NAILED-UP CONNECTION.
The DMS switch displays the next three errors at different times when the
switch operator tries to datafill a tuple in table RCUINV.
The switch operator tries to delete a tuple that was already deleted. If so, the
following error message appears:
TUPLE HAS ALREADY BEEN DELETED.
At least one message link must be datafilled in table RCUINV. If not, the
THERE MUST BE AT LEAST ONE MESSAGE LINK.
Links (X X) cannot be added to a shelf (Y) that is datafilled as unequipped.
Y MUST BE DEQUIPPED IF LINKS X X ARE CONFIGURED.
If field SSPRI is enabled in table RCUINV, then special-service calls have

priority over POTS calls during channel reassignment. Channel reassignment
occurs when faults occur on one or more DS-1 links, and the calls are
reassigned to free DS-1 channels on properly functioning DS-1 links.
Sometimes no free channels exist on properly functioning DS-1 links; when
this occurs, special-service calls replace POTS calls if field SSPRI is enabled.
The replaced POTS calls are dropped.
WARNING: XX CALLS MAY BE DROPPED IF SSPRI IS ENABLED.
RCUINV (continued)
A bus extender cannot be provisioned on an RCU that has lines datafilled in

table LNINV for the slot in which the bus extender is to be equipped.
LINES ALREADY DATAFILLED IN SLOT <1, 2>.
Channel units associated with SSMs must be deleted from table LNINV before
SSMs can be deleted. If channel units are not deleted, the following message
appears:
SSM <1, 2> CHANNEL UNITS MUST BE DELETED IN LNINV.
If operating company personnel datafill fields AUTOTEST and FAILSEN with

Y and RCU firmware is pre-RU30, the RCU can make the entire line card line
module busy (LMB). Some line cards have two lines. When one line fails the
autotest and the card is LMB, both lines will fail. The following FAILSEN
warning alerts the personnel to this possibility.
WARNING**lines may be LMBed if FAILSEN is enabled and the RCU

firmware version is pre-RU30.
The following message indicates that another request to change the RCU tuple
in table RCUINV is currently being processed. The existing request must be
processed before a new request can proceed.
ONLY ONE RECONFIGURATION IS ALLOWED. TRY LATER.
The following message indicates that insufficient DSPROT store could be

allocated. Check DSPROT store to determine if there is enough memory on
the switch. If so, data corruption may have occurred. Collect logs from
previous reconfiguration and inform your NT representative.
FAILED TO ALLOCAT CONFIG TABLES
The following message indicates that at least one logical terminal identifier
(LTID) is datafilled on the RCU when trying to reconfigure it to a different
C-side SMU. In table LTMAP, remove all LTIDs on that RCU.
ALL LTIDS MUST BE REMOVED
The following message indicates that there are insufficient C-side links in the
new configuration. Add more links or delete some time-division multiplexing
(TDM) or B connections. To determine which connections to delete, use
commands QDCH and CTKLOC on the ISDN lines.
NOT ENOUGH RCU CSIDE CAPACITY
297-8021-351 Standard 05.02 May 2001

RCUINV (continued)
The following message indicates that an insufficient number of ISDN

signaling group (ISG) channels on the new C-side SMU are available to
support all existing TDM connections. Create new ISG basic rate access
(BRA) channels on the new C-side SMU.
NOT ENOUGH ISG CHANNELS ARE FREE ON THE NEW SMU
The following messages provide status information to operating company

personnel.
The following message indicates that preliminary checks passed and

reconfiguration started.
RECONFIGURATION IN PROGRESS MAY TAKE A FEW MINUTES
The following message indicates that reconfiguration to a new SMU is

successful. The P-side links of the new SMU must be put into a return to
service (RTS) manual busy (ManB) state to return the RCU to service.
**WARNING: MUST RTS NEW PSIDE LINKS TO THE RCUs**
The following error messages indicate software errors:
COULD NOT GET SMU NODE NUMBER DELETION OF NODE FAILED LADD
NODE FAILED COULD NOT GET LINK STATUS ADD CARRIER FAILED
DELETION OF CARRIER FAILED FAILED TO IDENTIFY C-SIDE PM FAILED
TO ASSIGN OFFICE MODULE NUMBER
Two additional rules follow:

Multiparty divided ringing lines cannot be datafilled on RCU modules that
employ frequency selective ringing.
Lines with FSR cannot be datafilled on RCU modules that employ coded
ringing.
If updating table RCUINV, special guidelines must be followed for six of the
fields.
Field CSPMNO
When changing the SMU to which the RCU attaches in field CSPMNO, the
RCU must be manually busied (ManB) or offline (OFFL). The DS-1 links on
the SMU to which the RCU is being transferred must be datafilled as DS-1
links in table LTCPSINV and they must be OFFL (the state of DS-1 links
connecting other RCU modules to this SMU are not affected). DS-1 links are
placed offline at the PM level of the MAP display. Use command TRNSLT to
list the DS-1 links attached to a module and their states in the MAP display.
RCUINV (continued)
Field CSLNKTAB in table RCUINV needs to be updated after the transfer to

reflect the new P-side ports of the SMU to which DS-1 links now attach. This
is not necessary if both SMU modules used the same P-side port designations.
After the update is complete, the SMU (to which the RCU was moved) is
busied and returned to service. These actions cause the central control (CC) to
send the RCU static data to the SMU. The DS-1 links and the RCU must also
be returned to service.
Field CSLNKTAB
When datafilling message links in RCCINV, separate links by a minimum of
slots equal to the number of links on the interface card. Ensure that both
message links are not assigned to the same interface card. An E1 outage can
occur if both message links are assigned to a card that fails.
The following message indicates that two message links were assigned to the
same interface card. Some interface card types can have four or more links per
card, requiring assignment separations of four or more.

include: {0 1}, {2 3}, {4 5}, {6 7}, {8 9}, {10 11},
{12 13}, {14 15}, {16 17}, {18 19}. Each message
If moving existing DS-1 links within an SMU-RCU subsystem using field

CSLNKTAB of table RCUINV, either the links must be ManB, or the RCU
must be ManB or OFFL. Additionally, the P-side ports of the new SMU to
which the links are being moved must also be OFFL. The shelves to which the
links are being moved must be datafilled as equipped.
If adding DS-1 links to table RCUINV using field CSLNKTAB, these links
must be datafilled in table LTCPSINV as DS-1 links, and they must be OFFL.
The shelves to which the links are added must be datafilled as equipped.
When deleting DS-1 links from table RCUINV, the links to be deleted must be
ManB. The RCU can remain in-service if the update does not require deleting
both message links (DS-1 links 3 and 4); if both message links are deleted, the
links must be ManB and the RCU must be ManB or OFFL.
Fields RNGDATA and FREQUENCIES

RCU modules that employ FSR and are assigned to the same SMU must be
datafilled with the same frequencies in the same order.
297-8021-351 Standard 05.02 May 2001

RCUINV (end)
To change field RNGTYPE in table RCUINV, no lines associated with the

current ringing type can remain datafilled in table LNINV. For example, when
changing field RNGTYPE from F to C, no FSR lines for the RCU can remain
datafilled in table LNINV. Similarly, when changing the FREQUENCIES
field in table RCUINV, no FSR lines can remain datafilled in table LNINV.
Field CTRLSHF2
Control shelf 2 can be equipped only if line shelf 1 is equipped. This does not
mean that links need to be attached to line shelf 1.
Field LINESHF2
Line shelf 2 can be equipped only if control shelf 2 is equipped. This does not
mean that links need to be attached to control shelf 2.
Note 1: To avoid configuration alarms, digroup cards are not needed if the
associated link is not attached to the shelf. This is true even if the shelf is
marked as equipped.
Note 2: If changing fields CSLNKTAB, CSPMNO, RNGDATA, or
FREQUENCIES of table RCUINV, the following message appears at the
MAP terminal after the fields are changed:
WARNING: STATIC DATA NOT UPDATED FOR SMU xx
where
xx
is the number of the SMU
If static data is not updated, the DMS switch cannot use the changed data. This
can impact call processing. To ensure that static data is updated, busy the
inactive unit of the SMU and return it to service, execute a warm switch of
activity (SWACT), then busy the newly inactive unit of the SMU and return it
to service. An alternative is to busy and return to service the entire SMU. A
warm SWACT preserves calls that are in the talking state.
RDTINV
Table name
Remote Digital Terminal Inventory
Table RDTINV is a hardware inventory table that allows the end user to
datafill remote digital terminals (RDT) and their corresponding integrated
digital terminals (IDT) in the DMS-100 switching office. Table RDTINV
contains the central control side (C-side) connectivity information and RDT
configuration information.
The term RDT signifies an intelligent network element that provides an

interface from subscriber terminal devices in homes and office buildings to
digital transmission facilities at a central switching site.
The following types of RDTs are supported by a DMS-100 switching office.

S/DMS AccessNode (AccessNode)a multi-service platform that
supports copper-based and fiber-based services side by side. The
AccessNode network includes remote fiber terminals (RFT) that support
locally switched services, non-locally switched services, and non-switched
services.
multivendor interface (MVI) RDTa network element that uses an
industry-standard TR-303 interface to support copper-based services. This
device is also known as a generic time slot management channel
(GENTMC) RDT.
In addition to the RDTs defined above, the DMS-100 supports a third type of
IDT provisioned in table RDTINV. This IDT is the integrated channel bank
(ICB).
integrated channel bank (ICB)a communications device that
multiplexes voice signals and integrates support of subscriber lines served
by D4 channel banks into the SMA2. The ICB supports one to four DS-1
links that terminate directly to the SMA2.
The AccessNode terminates up to 1344 subscriber lines. The MVI RDT

terminates up to 2048 subscriber lines. The ICB terminates up to 96 subscriber
lines. By using these three IDT connections, traffic on subscriber lines is
carried to and from a DMS-100 switching office.
DMS-100 Family Customer Data Schema Reference Manual Volume 9 of 12, SN06 and up
RDTINV (continued)

The following tables must be datafilled before table RDTINV.
SITE
LTCINV
LTCPSINV
MTAVERT
MTAHORIZ
In addtion, when an SPM hosts IDTs, the following tables must be datafilled
before table RDTINV.
PMLOADS
MNPRTGRP
MNNODE
MNSHELF
MNCKTPAK
MNLINK
MNHSCARR
Table size
The maximum table size is 1000 IDTs. Only 255 of the 1000 can be RFT or
MVI IDTs. Each IDT counts toward the switch limit of 1000 line concentrating
devices (LCD). If an office has 1000 IDTs, that office cannot have any other
type of LCD (line concentrating module, for example). The 1000 LCD limit
applies to devices listed in tables RDTINV, LCMINV, RCSINV, RTCINV,
LMINV, and DLMINV.
An SMA supports RFT and MVI IDTs. The SMA does not support ICBs.
Because the SMA has only 20 P-side DS-1s, operating company personnel
cannot provision an RDT with more than 20 DS-1s.
As SMA2 supports all three types of IDTs. RFT and MVI RDTs support up to
28 DS-1s each. ICB IDTs support one to four DS-1s depending on the value in
the LINK_CAPACITY subfield of the ICB VARTYPE field.
An SMA or SMA2 is limited to 5376 subscriber lines. The SMA and SMA2 is
limited to eight RFT or GENTMC RDTs. The eight RFT or GENTMC limit
decreases to seven if the SMA or SMA2 uses any DCH cards. The SMA2
supports a maximum of 48 ICBs, subject to line capacity and link availability.
297-8021-351 Standard 09.03 March 2004

RDTINV (continued)
Operating company personnel must consider the P-side port capacity of the
SMA2 when engineering the SMA2 with RDTs of type GENTMC, RFT, and
ICB together. Refer to section SMA ICB Links in the XPM Translations
Reference Manual, 297-8321-815.
Signal distribution (SD) points

The operating company specifies a set of eight SD points it prefers to activate
for an RDT or a group of RDTs in field SDPOINTS. By entering the names
of SD point functions (RDTSD1 through RDTSD8), the operating company
dictates the combination of SD points that are activated if an alarm arises on
the RDTs. An RDT alarm causes the associated IDT to have an in-service
trouble (ISTb) status. At this occurrence, a PM128 log is generated.
The eight SD point functions that indicate the RDT raising the alarm and the
three SD point functions that indicate the severity of the alarm being raised
must be datafilled in table ALMSD. The scan point function for RDT alarm
cut-off must be datafilled in table ALMSC. The three software alarms are
datafilled by default by table SFWALARM.
Allowable test head combinations in subfield TSTHDUSR

The following table lists ten allowable test head combinations for metallic test
access (MTA) points in subfield TSTHDUSR. These datafill combinations
apply to MTA points for an integrated remote test unit (IRTU) and for a test
bypass pair (TBP).
External remote test unit (ERTU) is an MTA point that can only be used for no
test trunk (NTT) testing and does not require datafill in subfield TSTHDUSR.
Note: An IRTU cannot be provisioned on an MVI RDT.

Allowable test head combinations for subfield TSTHDUSR (Sheet 1 of 2)
IRTU
Example RTU1 RTU2 TBP ERTU
1 NTTIF MAPIF MAPIF N/A (not

available)
2 BOTH MAPIF MAPIF N/A
Note 1: RTU1 and TBP cannot be used simultaneously because they use the
same internal test bus.
Note 2: Although three test heads can be provisioned, only two can be active.
RDTINV (continued)
Allowable test head combinations for subfield TSTHDUSR (Sheet 2 of 2)
IRTU
Example RTU1 RTU2 TBP ERTU
3 MAPIF NTTIF MAPIF N/A
4 MAPIF BOTH MAPIF N/A
5 MAPIF MAPIF NTTIF N/A
6 MAPIF MAPIF BOTH N/A
7 BOTH or N/A
NTTIF
8 MAPIF Provisioned
(NTT only)
9 MAPIF BOTH or N/A

NTTIF
10 BOTH or MAPIF
NTTIF
Note 1: RTU1 and TBP cannot be used simultaneously because they use the
same internal test bus.
Note 2: Although three test heads can be provisioned, only two can be active.
297-8021-351 Standard 09.03 March 2004

RDTINV (continued)
Datafill
The following table lists datafill for table RDTINV.
Subfield or
RDTNAME see subfields Remote digital terminal name. This is the key to
this table. It is used to uniquely identify the RDT
to the system. This field contains subfields SITE,
FRAME, and UNIT.
Note: If an RDT is added to table RDTINV, a

corresponding IDT is also created by the DMS
switch software. If an RDT is deleted from table
RDTINV, the corresponding IDT is also deleted.
SITE alphanumeric Site. Enter the four-character site name assigned

to the remote location. This entry should also
appear in table SITE.
Note 1: The SITE cannot be HOST.

Note 2: Valid SITE names are dependent on the
value of parameter
UNIQUE_BY_SITE_NUMBERING in table
OFCENG.
FRAME numeric Frame number. Enter the logical frame number of

the SMA to which the RDT is connected.
(0 to 511)
UNIT numeric Unit number. Enter the logical unit number of the
SMA to which the RDT is connected.
(0 to 9)
GROUP numeric Group number. Enter the logical group number of

(0 to 3) the SMA to which the RDT is connected.
ADNUM numeric Administration number. This field contains the

external administrative number associated with a
(0 to 4095)
PM, and remains fixed over dump and restore.
Enter a numerical value that is unique among all
other PMs in an office.
RDTINV (continued)
Subfield or
IDTNAME see subfields Integrated digital terminal name. This field

identifies the SMA and the IDT to which the RDT
is connected. This field contains subfields
XPMNAME and EXTIDNO.
Note: The IDT must be offline to change this

field.
XPMNAME see subfields Extended multiprocessor system-based

peripheral module (PM) name. This subfield
contains subfields XPMTYPE and XPMNO.
XPMTYPE SMA, SMA2, Extended multiprocessor system-based

SPM peripheral module type. This subfield identifies
the type of PM connected to the RDT. Enter SMA
for the subscriber carrier module-100 access.
Enter SMA2 for Expanded SMA.
XPMNO numeric Extended multiprocessor system-based

peripheral module number. This subfield
(0 to 255)
identifies the SMA to which the RDT is connected.
EXTIDTNO numeric External integrated digital terminal number. This

subfield identifies the IDT to which the RDT is
(0 to 999)
connected. Enter a number from 0 to 999.
Note: The IDT cannot be deleted if there are

lines attached to it.
297-8021-351 Standard 09.03 March 2004

RDTINV (continued)
Subfield or
NENAME alphanumeric Network element name. Enter the name of the

(up to 20 external operation support system that identifies
characters) or the RDT. The default value is $.
$
Note 1: This field is datafilled automatically by
the system when a maintenance connection to
the RDT is established if the entry in field
VARTYPE is RFT (remote fiber terminal), and the
entry in field EOC is O or S.
Note 2: Manual datafill is ignored while the
maintenance connection is established. Any
non-nil changes made to this field result in a
warning message. Manual datafill is allowed
while the maintenance connection is not
established, but any changes are overwritten
when the maintenance connection is established.
PRIMOPC alphanumeric Primary operations controller identifier. Enter the

(up to 20 name of the primary operations controller (OPC)
characters) or that controls the RDT. The default value is $ if no
$ OPC controls the RDT.
BACKOPC alphanumeric Backup operations controller identifier. Enter the

(up to 20 name of the backup OPC for the RDT. The
characters) or default value is $ if no backup OPC is available.
$
Note: Datafill is rejected if the backup OPC is
entered without a primary OPC.
RDTINV (continued)
Subfield or
VARTYPE see subfield Integrated digital loop carrier variant type. This
field specifies the type of integrated digital loop
carrier.
RDTVAR RFT, RDT variable.

GENTMC,
RFT refers to AccessNode.
GENCSC,
ICB GENTMC (generic TR-303 timeslot
management channel) refers to MVI RDT.
GENCSC is not used.
ICB refers to integrated channel bank
Note: This field cannot be changed. The tuple

must be deleted and added again.
297-8021-351 Standard 09.03 March 2004

RDTINV (continued)
RDTVAR = RFT
If the entry in subfield RDTVAR is RFT (refers to AccessNode), datafill the
following table.
Field descriptions for conditional datafill RFT
Subfield or
RFT SHELFSLT see subfields Remote digital terminal shelf slot. This field
consists of subfields MINSHELF,
MAX_RDT_SHELF, MINSLOT, and
MAX_RDT_SLOT. These subfields are entered
as one field when adding tuples individually using
the DMS-100 table editor.
Note: A typical value for SHELFSLT is 1 7 1 96

where 1 is MINSHELF, 7 is MAX_RDT_SHELF, 1
is MINSLOT, and 96 is MAX_RDT_SLOT. The
MAX_RDT_SHELF field can be changed to
control the RFT line capacity. The other three
fields are constants and any attempt to change
these fields results in a warning message.
MINSHELF numeric Minimum shelf value. This subfield specifies the

minimum allowable value for the shelf of a line
(0 to 1)
equipment number (LEN). The only allowable
value for AccessNode RDTs is 1.
MAX_RDT_ numeric Maximum shelf value. This subfield specifies the

SHELF maximum allowable value for the shelf of a LEN.
(0 to 31)
The range is 0-31. For the RFT, this range is
1-31. The maximum value for AccessNode is 22.
MINSLOT numeric Minimum slot value. This subfield specifies the

minimum allowable value for the slot of a LEN.
(0 to 1)
The only allowable value for AccessNode RDTs is
1.
MAX_RDT_ numeric Maximum RDT slot value. This subfield specifies

SLOT the maximum allowable value for the slot of a
(0 to 99)
LEN. The only allowable value for AccessNode
RDTs is 96.
Note: For the last shelf, MAX_RDT_SLOT has a

value of 32 because of the maximum line limit on
RDTs/RFTs is 2048.
RDTINV (continued)
RDTVAR = GENTMC
If the entry in subfield RDTVAR is GENTMC (refers to MVI RDT), datafill
the following table.
297-8021-351 Standard 09.03 March 2004

RDTINV (continued)
Field descriptions for conditional datafill GENTMC (Sheet 1 of 2)
Subfield or
GENTMC RDTPPLNK numeric RDT path protection link. This subfield specifies
the RDT path protection link. Enter a number
(0 to 28)
from 1 to 28.
MAXLINES numeric Maximum number of lines. This subfield specifies

the maximum number of lines that an MVI RDT
(0 to 2048)
supports. Enter a number from 1 to 2048. In
addition, existing RDTs can be upsized or
downsized based on engineering requirements.
Up to eight MVI RDTs having line capacities in the
range of 96 to 2048 can be provisioned on an
SMA2, or seven RDTs when supporting ISDN.
When provisioning integrated channel banks
(ICB), up to 48 can be provisioned each having a
line capacity of 24 lines. The total number of lines
for each SMA2 cannot exceed 5376.
Note 1: It is recommended that line size changes

made to RDTs subtending the SMA2 be made in
increments of 96 to preclude fragmentation of the
terminal identifiers (TID) numbers in the TID
table.
Note 2: When increasing the line capacity of an
RDT, refer to the procedure for upsizing an RDT
in the appropriate SMA or SMA2 section of
Extended Peripheral Module Translations
Reference Manual
Note 3: When decreasing the line capacity of an
RDT, verify table LNINV to ensure that the
required number of lines are deleted before
allowing an update to field MAXLINES. Before
deleting a tuple from table LNINV, the lines are
cleared from other tables such as IBNLINES,
KSETLINE, KSETINV, LENLINES, and
SPECCONN. Because of provisioning delays
and the condition of the EOC channels, tuples
deleted from table LNINV may still be present in
table RDTLT, and will need to be checked.
RDTINV (continued)
Field descriptions for conditional datafill GENTMC (Sheet 2 of 2)
Subfield or
INHLINE Y or N Inherent lines. This subfield specifies whether the

MVI RDT supports the creation of the analog and
access side of ISDN line instances by entities
other than the DMS-100 switch. Enter Y if
another entity creates the analog and access side
of line instances at the RDT. Enter N if line
instances are created by the DMS-100 switch.
BRIDGING Y or N Bridging. Indicates if the ChangeToBridged

action is supported by the RDT. The
ChangeToBridged action is optional for TR-303
MBS lines. Default value is N.
RDTVAR = ICB
If the entry in subfield RDTVAR is ICB (refers to integrated channel bank),
datafill the following table.
Field descriptions for conditional datafill ICB
Subfield or
ICB RDT variable. Enter ICB for an integrated

channel bank.
LINK_CAPACITY 1 or 4 Link capacity. This subfield indicates the

maximum number of links available to the ICB.
The number of links provisioned in LINKTAB
cannot exceed LINK_CAPACITY.
297-8021-351 Standard 09.03 March 2004

RDTINV (continued)
VARTYPE = all entries

For all entries in field VARTYPE, datafill the following table.
Subfield or
CLAPDFLT see subfield C-side link access procedure on D-channel

default. This field contains subfield CLAPDDEF.
Note: If N" is chosen, non-default values can be

entered for the TMC LAPD parameters.
However, a warning message is displayed along
with the default values for the CLAPDPAR
subfield when non-default values are entered for
the N201 and T200 parameters. If the RDT is to
support MBS services, the N201 and T200 values
should be changed to the values displayed in the
following warning message.
WARNING: EBS lines will not work on
this RDT. For EBS lines to work on
this RDT N201 parameter must be >= 52
and T200 parameter must be >=25.
CLAPDDEF Y, N, or NA C-side link access procedure on D-channel

default. Enter Y for the use of default access
procedures. Otherwise, enter N, and datafill
subfield CLAPDPAR for non-standard access
procedure parameters. If the ICB variant is
datafilled in VARTYPE, enter NA to indicate that
a choice of default LAPD parameters does not
apply.
RDTINV (continued)
Subfield or
CLAPDPAR alphanumeric C-side link non-standard access procedure

parameters. Enter the selected link access
procedure and complete the refinements
identified in the following by entering:
N201 and a number from 1 to 256. Selector
N201 selects the maximum number of octets
allowed in the information field on an
information frame. The maximum number is
256.
N200 and a number from 1 to 10. Selector
N200 selects the maximum number of
retransmissions of a pulse frame allowed.
The maximum number is 10.
K and a number from 1 to 7. Selector K
selects the maximum number of outstanding
unacknowledged pulse frames allowed. The
maximum number is 7.
T203 and a number from 10 to 300. Selector
T203 selects the maximum time allowed in
minutes without frame pulses being
exchanged at transmission end points before
a transmission time-out occurs. The
maximum time between frame pulses is 300
ms.
T200 and a number from 100 to 350.
Selector T200 selects the maximum time in
milliseconds that a data link layer entity waits
for an acknowledgement of a transmitted
pulse frame. The maximum time is 350 ms.
297-8021-351 Standard 09.03 March 2004

RDTINV (continued)
Subfield or
MTSTACPT TBP, ERTU, Metallic test access point. This field specifies the
IRTU, $ types of MTA points configured on the RDT. A
maximum of six metallic test access points is
available for each RDT (although only three can
be datafilled). The entries for this field include:
TBP (test bypass pair)
ERTU (external remote test unit)
IRTU (integrated remote test unit)
$ (no entry, or stopping)
Note 1: AccessNode supports all three available

MTA points. MVI RDT supports only TBP and
ERTU.
Note 2: MAP terminal testing is provided by TBP
or IRTU. NTT testing can use one of the three
available MTA points.
RDTINV (continued)
Subfield or
It is possible to have two different test heads

accessing the AccessNode at the same time.
(Three test heads can be provisioned, but only
two can be active.) The following combinations
are possible:
TBP individually
MAP terminal and NTT testing are performed
over the TBP.
ERTU individually
Only NTT testing is performed over the
ERTU.
IRTU individually
One or both test heads are defined; only one
test head can be defined for NTT use.
TBP with ERTU
TBP provides MAP terminal testing; ERTU
provides NTT testing.
TBP with IRTU
RTU1 and RTU2 can be used with TBP.
Note: RTU1 and TBP cannot be used

simultaneously because they use the same
internal test bus.
MTSTACPT = TBP
The TBP entry allows the MTA to bypass maintenance trunk module (MTM)
test heads or to connect to NTT access. NTT access requires a horizontal
cross-connection at the MTA.
297-8021-351 Standard 09.03 March 2004

RDTINV (continued)
If the entry in field MTSTACTP is TBP, datafill the following table.

Field descriptions for conditional datafill TBP
Subfield or
TBP see subfields Test bypass pair. This selector identifies the MTA
point that is configured to supply metallic test
bypass for MTM-based test heads or NTT access
that requires a horizontal cross-connect at the
MTA. This selector contains subfields
TSTHDUSR, VERTID, TSTACCPA, and
SCSDUSED.
TSTHDUSR MAPIF, Test head user. This subfield is used to identify

NTTIF, BOTH which test system (MAP, NTT or BOTH) uses the
test head.
Note: Refer to Allowable test head

combinations for subfield TSTHDUSR" earlier in
this section for a listing of the possible test head
combinations for TBP access.
VERTID numeric Vertical identifier. (This subfield replaces the

VERTID section of the prompt
(0 to 1023)
PT_CONNECTION_INFO.) Enter the number
that represents the vertical in the MTA matrix
where the control path is tied.
TSTACCPA TAP1, TAP2, Test access path. For MVI RDT, enter TAP1 (test
TBPP access point 1). For AccessNode, enter TBPP
(test bypass pair point).
Note: TAP1 and TAP2 are four-wire interfaces;

TBPP is a two-wire interface.
SCSDUSED Y or N Scan point/signal distributor (SD/SD) point used.

Enter Y if SD/SD points are used and provide the
multiple containing:
INHSCGRPpoint range of 0 to 511
INHSCPTpoint range of 0 to 6
INHSDGRPpoint range of 0 to 511
INHSDPTpoint range of 0 to 6
Otherwise, enter N.
RDTINV (continued)
MTSTACPT = ERTU
If the entry in field MTSTACTP is ERTU, datafill the following table.
Field descriptions for conditional datafill ERTU
Subfield or
ERTU see subfields External remote test unit. This field identifies an
external metallic test head on the RDT for NTT
testing. This selector is compatible with the TBP
selector, which is used for MAP terminal testing.
This selector contains subfields VERTID,
TSTACCPA, and SCSDUSED.
VERTID numeric Vertical identifier. Enter a number that represents

the vertical identifier in the MTA matrix where the
(0 to 1023)
control path is tied.
TSTACCPA TAP1, TAP2, Test access path. For MVI RDT, enter TAP1. For
TBPP AccessNode, enter TAP1, TAP2, or TBPP.
Note: TAP1 and TAP2 are four-wire interfaces;

TBPP is a two-wire interface.
SCSDUSED Y or N Scan point/signal distributor point used. Enter Y

if SD/SD points are used and provide the multiple
containing:
INHSCGRPrange of 0 to 511
INHSCPTrange of 0 to 6
INHSDGRPrange of 0 to 511
INHSDPTrange of 0 to 6
Otherwise, enter N.
297-8021-351 Standard 09.03 March 2004

RDTINV (continued)
MTSTACPT = IRTU
If the entry in field MTSTACTP is IRTU, datafill the following table.
Field descriptions for conditional datafill IRTU (Sheet 1 of 2)
Subfield or
IRTU see subfields Integrated Remote Test Unit. This selector

identifies an IRTU on the RDT for NTT or MAP
testing. This field contains subfields RTUNUM,
TSTHDUSR, TSTACCPA, and SCSDUSED.
RTUNUM RTU1 or RTU number. This subfield is used to determine

RTU2 which test head on the IRTU is to be defined.
TSTHDUSR NTTIF, Test head user. This subfield identifies which test
MAPIF, BOTH system (MAP, NTT or BOTH) uses the test head.
Depending on which test head user is entered,
subfields ALTUSE and VERTID must be
datafilled.
Note: Refer to Allowable test head

combinations for subfield TSTHDUSR" for a
listing of the possible test head combinations for
IRTU access.
ALTUSE Y or N Automatic line test (ALT) use. Enter Y to use the

IRTU for ALT; otherwise, enter N. ALTUSE is
required if TSTHDUSR is MAPIF or BOTH.
VERTID numeric Vertical identifier. (This subfield replaces the

VERTID section of the prompt
(0 to 1023)
PT_CONNECTION_INFO.) Enter a number that
represents the vertical in the MTA matrix where
the control path is tied. VERTID is required if
TSTHDUSR is NTTIF or BOTH.
RDTINV (continued)
Field descriptions for conditional datafill IRTU (Sheet 2 of 2)
Subfield or
TSTACCPA TAP1 or TAP2 Test access path. RTU1 is connected to TAP1.

RTU2 is connected to TAP2.
Note: TAP1 and TAP2 are four-wire interfaces.
SCSDUSED Y or N Scan point/signal distributor point used. Enter Y

if SD/SD points are used and provide the multiple
containing:
INHSCGRPrange of 0 to 511
INHSCPTrange of 0 to 6
INHSDGRPrange of 0 to 511
INHSDPTrange of 0 to 6
Otherwise, enter N.
297-8021-351 Standard 09.03 March 2004

RDTINV (continued)
MTSTACPT = all entries

For all entries in field MTSTACPT, datafill the following table.
Subfield or
NTTOPT Y or N No test trunk signature option. This field

indicates whether the no test trunk (NTT) direct
current (dc) voltage signature is enabled for a
particular RDT. If the value is Y", then the dc
signature for POTS, coin, and multi-party lines
will be provided; otherwise, the signature will not
be provided for any of the line types.
Note: When the NTTOPT field is datafilled as

N" or changed to N", the following message is
output at the MAP terminal:
NTT signature will not be provided
during line maintenance.
LINKTAB see explanation Link assignment table. This is a vector, with up

to 20 entries, that defines the mapping of the
C-side links of the RDT (logical link) to the
P-side links (physical link) of the SMA. This field
contains subfields RDTLINK and XPMLINK and
is entered as one entry.
If LINK_CAPACITY is equal to four, operating
company personnel can enter up to four entries
for ICBs.
RDTLINK numeric Remote digital terminal link number. Enter an

RDT link number from 1 to 28.
(1 to 28)
Note: When datafilling field LINKTAB, ensure message links are not assigned to the same physical
interface card. When the interface card supports two or more links, separate the message links by the
number of links on the interface cards. Table control will issue a warning if an attempt is made to
assign message links on the same interface card. Assigning message links to the same interface card
can cause an E1 outage (failure of all message links) if the card fails.
RDTINV (continued)
Subfield or
XPMLINK numeric Extended multiprocessor system-based

peripheral module link number. Enter an XPM
(0 to 181)
link number. Up to 20 RDT XPM link pairs can
be datafilled. (However, DCH provisioning in
table LTCPSINV reduces the number of
XPMLINK pairs available.) Use values greater
than 47 only if an SPM hosts the link.
Note: If the P-side DS-1s added to this field do

not have Extended Superframe Format (ESF)
framing, and the entry in field VARTYPE is
GENTMC, an error is displayed.
PROT Y or N Facility protection switching. Specifies whether

protection switching is supported. Enter N. (An
entry of Y is not supported.)
POTSPAD STDLN, UNBAL POTS pad group. The acceptable values are
G UNBAL and STDLN.
EOC see subfields Embedded operations channel. This field

specifies whether EOC is present, and whether
standard or LAPD parameters are used. This
field contains subfields EOCTYPE and
ELAPDPAR.
Note: The IDT and the channel must be offline

to be changed.
297-8021-351 Standard 09.03 March 2004

RDTINV (continued)
Subfield or
EOCTYPE S, O, or N EOC type. This subfield specifies whether EOC

is present, and whether standard or optional
LAPD parameters are used. Enter one of the
following:
S for standard LAPD parameters
O for optional LAPD parameters. Subfield
ELAPDPAR must be datafilled.
N for no EOC channel, as in the case of the
ICB
For ICB configurations, the value of EOC is N".
Note: The LAPD parameters of the EOC/CSC

can be changed when the IDT and the channel
are manually-busied or offline.
ELAPDPAR N201, N200, K, EOC parameters. This subfield appears when

T203, T200 O is entered in subfield EOCTYPE. Specify the
optional LAPD parameters. Enter five values,
with a space between each value.
N201 and a number from 1 to 256
N200 and a number from 1 to 10
K and a number from 1 to 7
T203 and a number from 10 to 300
T200 and a number from 100 to 350
RDTINV (continued)
Subfield or
SDPOINTS RDTSD1, Signal distribution point. Enter the SD point that

RDTSD2, corresponds to this RDT. There is a maximum
RDTSD3, of 255 different combinations of activated SD
RDTSD4, points to indicate that the RDT is raising an
RDTSD5, alarm. This field can be used to group RDTs
RDTSD6, together by assigning the same points to
RDTSD7, multiple RDTs.
RDTSD8
Note: Each of the SD points must first be
datafilled in table ALMSD (Alarm Signal
Distributor Point). If field SDPOINTS is set to $
(nil) to indicate that no SD points for RDT alarms
are datafilled, the SD points that indicate alarm
severity (RDTCRIT, RDTMAJOR, RDTMINOR)
are not activated.
RDTDN see subfields RDT distinguished name. This is a vector of one

to four elements for the RDT_RDN. Each
element represents a relative distinguished
name (RDN) for the RDT.
297-8021-351 Standard 09.03 March 2004

RDTINV (continued)
Subfield or
RDN_TYPE NETWORK_ID, Relative distinguished name. Enter the RDN of

SYSTEM_ID, the RDT. The range of values is as follows:
NETWORK
NETWORK_ID
ELEMENT_ID,
EQUIPMENT_ID SYSTEM_ID
NETWORKELEMENT_ID
EQUIPMENT_ID
For MVI IDTs, use only NETWORK_ID and
NETWORKELEMENT_ID. For RFT RDTs, use
all four types. For ICB IDTs, leave the RDTDN
field empty.
Note 1: For RFT IDTs, make sure that the

NETWORKELEMENT_ID matches the value in
the RDT or the maintenance connection does
not establish.
Note 2: For an AccessNode RDT of type RFT,
the NETWORK_ID, SYSTEM_ID, and
EQUIPMENT_ID values must be set to 1 to
correspond to the values on the RFT. If the
values in this table are not set to 1, a warning
message is displayed and the values are
automatically reset to 1.
Note 3: For MVI IDTs, operating company
personnel can change the NETWORK
ELEMENT_ID with no side effects. For RFT
IDTs, the IDT must be OffL or both EOCs must
be ManB before a change to NETWORK
ELEMENT_ID.
RDN_VAL numeric Relative distinguished name value. Enter the

numerical value for the RDN.
(0 to 32 767)
RDTINV (continued)
Datafill example
The following example shows sample datafill for table RDTINV.
MAP display example for table RDTINV
RDTNAME ADNUM IDTNAME NENAME

PRIMOPC BACKOPC
VARTYPE CLAPDFLT
MTSTACPT
NTTOPT
LINKTAB
PROT POTSPADG EOC
SDPOINTS
RDTDN
_____________________________________________________________________
AN07 00 0 26 SMA 4 7 R07_XTLM OPCM301
$ $
RFT 1 7 1 96 Y
(IRTU RTU1 MAPIF Y TAP1 N) (IRTU RTU2 MAPIF N TAP2 N)$
Y
(1 2) (2 0) (3 3) (4 1) $
N STDLN S
$
(NETWORK ID 1) (SYSTEM_ID 1) (NETWORKELEMENT_ID 304) $
Table history
SN06 (DMS)
Additional error condition statement added by Q00773480.
SP14
The following changes were made for feature 59012232.
Increased from 47 to 181 the maximum value for the XPMLINK field.
Added SPM to the values for the XPMTYPE field.
Added eleven additional error messages to the supplemental information
section.
Added a list of SPM provisioning tables to the datafill sequence and
limitations section.
NA012
Added field LINK_CAPACITY for the integrated channel bank.
297-8021-351 Standard 09.03 March 2004

RDTINV (continued)
NA010
The following changes were made to table RDTINV:
changed the number of lines the S/DMS AccessNode supports
changed the allowable values for subfields MAX_RDT_SHELF and
MAX_RDT_SLOT in field RDTVAR, subfield SHELFSLT
NA008
added information about resizing RDTs and adding ICBs in subfield
MAXLINES
added information about LAPD parameters to support EBS lines in field
CLAPDFLT
added new subfield BRIDGING to indicate RDT ChangedToBridged"
support for MBS lines for MVI RDTs
added new field NTTOPT to enable the no test trunk direct current (dc)
voltage signature
removed reference to system limit of 240 RFTs. The correct limit is 255
RDTs, whether they are MVI RDTs or RFTs.
NA007
Added a warning to table RDTINV, field LINKTAB, subfield XPMLINK to
indicate that an E1 outage can occur when both DS-1 message links are
assigned to the same interface card.
NA005
added error message to indicate that a tuple is being rejected because some
part of the system recovery controller (SRC) registration process failed
removed restriction from subfield ALTUSE (field MTSTACPT) requiring
the entry for the second RTU test head to be N
NA004
added entry SMA2 to subfield XPMTYPE
added refinement GENTMC and its refinements to subfield RDTVAR
expanded range for MAXLINES to include up to 2048 lines for refinement
GENTMC
RDTINV (continued)
increased range of subfield XPMLINK to 47 link numbers

added error and warning messages to Supplementary information section
BCS36
added field ADNUM
deleted field SID and replaced it with field NENAME, and added fields
PRIMOPC and BACKOPC
added field POTSPADG
added note to field XPMLNK
BCS35
Field SDPOINTS was revised.
This section provides information on datafill error messages for table
RDTINV.
Datafill error messages

If the IDTNAME field does not contain either SMA, SMA2, or SPM, the
following error message is displayed:
Error: IDT Host must be of the type SMA, SMA2, or SPM.
If the VERTYPE field is ICB and the IDTNAME field is neither SMA2 nor
SPM, the following message is displayed.
Error: IDT Host must be of type SMA2 or SPM for ICB IDTs.
If table MNHSCARR does not contain entries matching the SPM number in
the IDTNAME field and the XPMLINK number in the LINKTAB field, the
following message is displayed:
Error SPM nn XPMLINK yyy (CCTNO in table MNHSCARR) was NOT

found.
Note: nn and yyy vary depending on actual datafill.
If the IDTNAME field is SPM and the XPMLINK number in the LINKTAB
field is not of the correct type (DS1P), the following message is displayed:
Error: Invalid link. SPM nn XPMLINK yyy (CCTNO in table

MNHSCARR) much have CARRTYPE of DS1P.
297-8021-351 Standard 09.03 March 2004

RDTINV (continued)
Note: nn and yyy vary depending on actual datafill. nn is the SPM

number, and yyy is the link number of the SPM.
If the SPM number (0 to 63) for a given SPM node number (0 to 4095) canot
be found in the SPM OAM database, the following message is displayed:
Error: Inconsistent MNNODE table data found when translating SPM

nn to its internal SPM OAM database index. Consult SWERR Logs.
Note: nn varies depending on actual datafill. nn is the SPM number.
If the number of lines exceeds the allowed maximum value of 21504, the
following message is displayed:
Error: Cannot have more than 21504 lines for this SPM.
If the class type of the SPM cannot be determined, the following message is
displayed:
Error: Could not determine CLASS type for SPM nn.
If the SPM specified in the IDTNAME field does not have a class type of
DMSCP indicated in table MNNODE, the following message is displayed:
Error: Invalid SPM type. SPM nn must have a CLASS type of DMSCP
in table MNNODE to host IDTs.
The following message will be displayed during provisioning if the IDT

cannot be successfully registered with the CPP subsystem. The CPP subsystem
reroutes call processing messages to IDTs subtending SPM nodes.
Error: Failed to register IDT with CPP.
The following message will be displayed during provisioning if the IDT

cannot be successfully de-registered with the CPP subsystem.
Error: Failed to deregister IDT from CPP.
If there is no available protected memory store to allocate for SMALINKMAP

in IDT_INFO_TYPE, the following message is displayed:
Error: NO STORE for IDT HOST LinkMap DATA BLOCK.
RDTINV (continued)
The following warning message is displayed on the MAP (maintenance and

administration position) terminal if field LINKTAB, subfield XPMLINK is a
DS-1 link (0-19) and the first two links (messaging links) are on the same DS-1
pack. An E1 outage occurs if both message links are assigned to the same
faulty card.

include: {0 1}, {2 3}, {4 5}, {6 7}, {8 9}, {10 11},
{12 13}, {14 15}, {16 17}, {18 19}. Each message
The following warning message is displayed on the MAP terminal if the

dynamic static data downloads fail:
Warning: Additional static data not updated for SMA 0
where
SMA
is SMA or SMA2
0
is 0 or 1
The following error message is displayed on the MAP terminal if an attempt is

made to change LAPD parameters or field EOCTYPE while the IDT is system
busy (SysB):
Error: IDT # is SysB
where
#
is an IDT number
SysB
is the IDT state
If the IDT has only one link, and field PROT is set to Y, the following error
message is displayed on the MAP display:
Error: Cannot have PROT link: IDT # has only one link
297-8021-351 Standard 09.03 March 2004

RDTINV (continued)
If dynamic static data updates complete, the following message is displayed on

the MAP display:
Additional Static data updates completed for <PM type>
where
<PM type>
is SMA or SMA2
If static data in the PM is updated on only one SMA unit, or link changes are
attempted while the PM is in service, error messages are displayed on the MAP
terminal as follows:
Static data update required for SMA 0 UNIT 0

Static data update required for SMA 0 UNIT 1
The following warning message is displayed on the MAP terminal if field

ALTUSE is changed from Y to N:
Warning: ALL ALT test streams expecting to use the

previously defined &$ will no longer run. Redefine the
scheduled ALT tests.
where
&$
is RTU1, RTU2 or TBP
The following warning message is displayed on the MAP terminal if field

ALTUSE is changed from N to Y:
Warning: Previously defined ALT tests will not make use of

this LTE until these ALT tests have been redefined.
The following warning message is displayed on the MAP terminal if an

attempt is made to use RTU1 and TBP simultaneously:
Warning: TBP and RTU1 cannot be used to run simultaneous test.
The following error message is displayed on the MAP terminal if adding or

updating the RDTINV entry fails because the request for nail-up of the SMA
DCH channels and the RDT CSC, TMC or EOC channels has failed:
Error: Nailup of CSC/TMC/EOC channels failed
RDTINV (continued)
The following error message is displayed on the MAP terminal if tuple

deletion was performed. Removal of the nail-up connection between the RDT
CSC, TMC, or EOC channels and the SMA DCH channels failed:
Error: CSC/TMC/EOC channel nail-up removal failed
The following warning message is displayed on the MAP terminal if adding or

updating the nail-up connections, and a failure occurs in the addition of a
connection. In restoring the original state of the connections, another failure
occurred and the original connection could not be restored.
Warning: CSC/TMC/EOC channel nail-up corrupt
For NA006 and back, the following error message is displayed if, when adding
tuples, an attempt occurred to datafill subfield MAXLINES with more than
672 lines on an SMA for small capacity-sized RDTs. Datafill is blocked.
Error: Cannot have more than 672 lines for this RDT. Only RDTs
of SMALL size are allowed on this SMA.
For NA006 and back, the following error message is displayed if, when adding
tuples, an attempt occurred to datafill subfield MAXLINES with more than
1344 lines on an SMA for medium capacity-sized RDTs. Datafill is blocked.
of MEDIUM size are allowed on this SMA.
The following error message is displayed if, when adding tuples, an attempt
occurred to datafill a ninth RDT on an SMA for small-sized RDTs. Datafill is
blocked.
Error: Cannot have more than 8 RDTs on this host peripheral.
occurred to datafill a fifth RDT on an SMA for medium capacity-sized RDTs.
Datafill is blocked.
occurred to datafill a third RDT on an SMA for large capacity-sized RDTs.
Datafill is blocked.
297-8021-351 Standard 09.03 March 2004

RDTINV (continued)
The following error message is displayed if, when updating tuples, an attempt
occurred to datafill subfield MAXLINES with more than 672 lines on an SMA
for small capacity-sized RDTs. Datafill is blocked.
of SMALL size are allowed on this SMA.
The following error message is displayed if, when updating tuples, an attempt
occurred to datafill subfield MAXLINES with more than 1344 lines on an
SMA for medium capacity-sized RDTs. Datafill is blocked.
of MEDIUM size are allowed on this SMA.
The following error message is displayed if , when adding a tuple the

maximum number of 32 EISP channels allowed for each SMA2 is exceeded.
Four channels are required for each IDT and 1 channel is required for each
DCH already provisioned on a SMA2. Datafill is blocked.
Error: Cannot add this RDT. Exceeds resources available for the
current number of RDTs and DCHs provisioned.
The following error message is displayed if an attempt occurred to datafill

more than 255 RDTs. Datafill is blocked.
Error: Cannot add this RDT. Only 255 RDTs can be datafilled per
office.
The following error message is displayed if an attempt occurred to datafill

more than 40 RDTs with variant type RFT. Datafill is blocked.
Error: Cannot add this RDT. Only 40 RDTs with RDTVAR=RFT per
office can be datafilled.
The following error message is displayed if an attempt occurred to update a

tuple in table RDTINV that does not exist.
Error: Cannot update a non-existent tuple.
The following warning message is displayed if an attempt occurred to assign

a non-zero number to field ADNUM while adding or updating a tuple when
office parameter USE_OM_ADMIN_NUMBER is set to False. The software
automatically enters 0 in field ADNUM.
Warning: ADNUM is being changed to 0.
The following error message is displayed if an attempt occurred to update a

tuple after the new administration number had been allocated and the old
RDTINV (continued)
administration number could not be retrieved. The old administration number

from the physical store is changed to the value of the new administration
number from the logical tuple.
Error: Failed to restore the old ADNUM.
The following warning message is displayed, along with the default values for
field CLAPDFLT, if an attempt occurred to enter non-default values for
subfield N201. If the RDT is to support electronic business service (EBS), the
values entered for subfield N201 should be changed to the specified values in
the following warning message.
Warning: EBS lines will not work on this RDT.

For EBS lines to work on this RDT, N201 parameter
must be > 52.
The following warning message is displayed on the MAP terminal if an

attempt occurred to assign a value other than 1 7 1 96 in subfield SHELFSLT
for refinement RFT in field VARTYPE. The software automatically corrects
the error.
Warning: SHELFSLT is being changed to 1 7 1 96.
The following error message is displayed during a table audit when a corrupted
tuple is found with non-default values for subfield SHELFSLT:
Error: For RFT the SHELFSLT is 1 7 1 96.
The following warning message is displayed if an attempt occurred to datafill

more than the maximum number of test points:
Warning: Exceeds the maximum limit of Metallic Test Access

Points.
The following error message is displayed if an attempt occurred to change a

field for an RFT tuple when an IDT is not offline. Datafill is blocked:
Error: RDT <IDT_index> must be offline to change <field>.
where
<IDT_index>
0 to 255
<field>
LINKTAB, PPS_ENABLE, IDTNAME, RDTDN
297-8021-351 Standard 09.03 March 2004

RDTINV (continued)
The following error message is displayed if, while attempting to move an

existing RDT to a new C-side peripheral (SMS or SMSR), corruption of the
nodes C-side dependency occurred and the node was deregistered from the
system recovery controller (SRC). The tuple is rejected. Attempt a nil change
on the tuple so that an attempt is made to reregister the node with the SRC.
Node has been deregistered from the System Recovery

Controller.
Attempt a nil change on the tuple to register the
node with the SRC.
The following error message is displayed if an attempt occurred to change

field RDTDN to a non-unique value for an RFT tuple when an IDT is offline.
Datafill is blocked. (However, values that are unique for an RFT tuple but are
not unique for non-RFT tuples are not blocked.)
Error: The specified RDTDN is already assigned to another RDT.
The following warning message is printed if an attempt occurred to change

field RDTDN to a value that is unique to all RFT tuples when an IDT is offline.
Datafill is not blocked. (Use the RDTRROV tool, REPROV <IDT_number>,
to reprovision the lines on this RDT.)
Warning: Use extreme caution when changing the RDTDN field.

This change will cause loss of service on all lines on this
IDT. The REPROV command in the RDTPROV increment must be
used after this change to restore service to the lines.
Changes to the RDTDN field must be accompanied by
corresponding changes to the distinguished name at the RDT.
Failure to match these values will prevent the establishment
of a maintenance connection to another RDT.
The following error message is displayed if an attempt occurred to add or

change an RFT tuple with more than one NETWORK_ID value in subfield
RDN_TYPE of field RDTDN. Datafill is blocked.
Error: Invalid RDT DN - RDNs missing or out of order.
The following error message is displayed if an attempt occurred to datafill an

RDT with more than 20 links when the host peripheral is an SMA. Datafill is
blocked.
Error: Peripheral type SMA only supports 20 links.
RDTINV (continued)

ICB without including a value for LINKTAB. Datafill is blocked.
Error: Linktab field is empty.

ICB with LINKTAB entries greater than LINK_CAPACITY. Datafill is
blocked.
Error: number of LINKTAB entries exceeds link capacity in

VARTYPE field.
Error: Link capacity in VARTYPE field must be 1 or 4.
Error: ICB LINKTAB rdtlink values cannot be greater than the
link capacity.
The following error message is displayed if an attempt occurred to change the

value of LINK_CAPACITY for a previously provisioned ICB. Datafill is
blocked.
Error: Link capacity in the ICB VARTYPE field may not be

changed.
The following error message is displayed if an attempt occured to delete a link

to an ICB with lines on the link. Datafill is blocked.
Error: Link <link_number> cannot be removed, it is associated

with provisioned lines.
The following error message is displayed if an attempt occured to delete a link

to an ICB that is not at the end of the LINKTAB field. Datafill is blocked.
Error: LINKTAB IDT must be MANBsy before RDTLINK <link_number>

can be deleted.
The following error message is displayed if an attempt occured to add a link to

an ICB that is not at the end of the LINKTAB field. Datafill is blocked.
Error: LINKTAB IDT must be MANBsy before RDTLINK <link_number>

can be added.
297-8021-351 Standard 09.03 March 2004

RDTINV (continued)
The following table lists RDT datafill error conditions and error explanations.
RDT datafill error condition and error explanation table (Sheet 1 of 3)
Error condition Error explanation
An RDT must have RDTLINK 1 RDTLINK 1 must be present in

configured. LINKTAB.
The peripheral module (PM) type of the Host XPM must be of type SMA.
C-side XPM is not datafilled.
The C-side XPM is not datafilled. Host XPM is unequipped.
IDT is already used for another RDT. IDT used by RDT <site>
<frame><unit>.
A C-side link specified for the RDT is SMA link <link number> must be DS-1.
not a DS-1.
A C-side link specified for the RDT is SMA link <link number> in use.
already in use by another PM.
A C-side link added to the RDT is not SMA link <link number> must be offline.
offline (Offl).
RDT variant is GENCSC, GENTMC, or Illegal ring type for this PM.
GENRBS, and ring type is not
frequency selective, superimposed, or
coded, or RDT variant is RFT, and ring
type is not frequency selective,
superimposed, coded, or coded
special.
The site field is HOST. Site cannot be HOST.
Maximum number of line controlling Failed to assign office module number.

devices in system exceeded.
C-side link removed from RDT is not SMA link <link number> must be offline
manual busy (ManB) or offline (Offl). to delete.
IDT is not Offl, and an attempt was IDT must be offline to delete.
made to delete its entry in table
RDTINV.
RDTINV (continued)
IDT is not Offl or ManB, and IDT must be ManB or OFFL to change
<field_name>.
an attempt was made to change
field EOC
field PROT
field LINKTAB
field IDTNAME
Field LINKTAB has entries with the Field LINKTAB has duplicate XPMLINK
same XPMLINK. entries.
Field LINKTAB has entries with the Field LINKTAB has duplicate RDTLINK
same RDTLINK. entries.
An attempt was made to add a ninth Too many RDTs for this host XPM.
RDT to an SMA.
An RDT with field RDTVAR equal to IRTU type not allowed for this PM.
GENCSC, GENTMC, or RCU can have
field MTSTACPT equal to TBP, ERTU,
or no entry.
Any RDT cannot have more than one Field MTSTACPT configurations not
external test configuration. allowed.
No duplicate entries of TBP in field Field MTSTACPT has duplicate entry of

MTSTACPT for an RDT. type TBP.
No duplicate entries of ERTU in field Field MTSTACPT has duplicate entry of

MTSTACPT for an RDT. type ERTU.
Any RDT can have a scan point (SC) Invalid scan (SC) group.
datafilled that shares a single vertical
between multiple RDTs including
integrated digital loop carrier (IDLC)
and UDLC type systems.
297-8021-351 Standard 09.03 March 2004

RDTINV (end)
Any RDT can have an SD datafilled that Invalid SD group.

shares a single vertical between
multiple RDTs including IDLC and
UDLC type systems.
Field VERTID must be unique for each Duplicate VERTIDs for field
MTSTACPT of an RDT entry. MTSTACPT configuration.
RDTLT
Table name
Remote Digital Terminal Line Termination Table
Table RDTLT contains information relating to the ongoing operations that are
being performed on a line connected to the remote digital terminal (RDT) by
the object provisioning process.
Table RDTLT is a read-only table. Data cannot be added or deleted by manual

data modification orders (DMO).
A tuple to table RDTLT is added when a new line is datafilled for RDT in table
LNINV. A tuple is deleted from table RDTLT when a line connected to the
RDT is deleted.
Entries in field SITE must match entries in table SITE.
For related information, refer to table RDTINV.

There is no requirement to datafill other tables prior to table RDTLT.
Table size
0 to 262144 tuples
Table RDTLT allows for up to 256 RDTs.
Memory is dynamically allocated for each entry in table RDTLT.
Table RDTLT updates are made through table LNINV software control or
through the line provisioning process software except during the dump and
restore process.
The following message is displayed at the maintenance and administration

position (MAP) video display terminal (VDU) if a manual update to table
RDLT is attempted:
MANUAL UPDATE TO TABLE RDTLT NOT ALLOWED
297-8021-351 Standard 05.02 May 2001

RDTLT (continued)
Datafill
The following table lists datafill for table RDTLT.
Subfield or

telephone line.
For ISDN lines, field LEN consists of subfield
LTID. For non-ISDN lines, field LEN consists
of subfields SITE, FRAME, UNIT, DRAWER
or LSG, SHELF, SLOT, and CIRCUIT.
ACCESS see below Line provisioning process operation

This field identifies the operation performed
by the line provisioning process for an RDT
line.
ACCESS_NIL No operations are required.
I_ACCESS_DONE Line objects provisioning for ISDN line done.
I_CHA_IPTIS_ Waiting for response to message:

CONF
CHANGE PRIMARY STATE OF ISDN PATH
TERMINATION (PT) TO IN SERVICE
I_CHA_IPTIS_ Send message:

REQ
CHANGE PRIMARY STATE OF ISDN PT
OBJECT TO IN SERVICE
I_CHA_IPTOOS_ Waiting for response to message:

CONF
CHANGE PRIMARY STATE OF ISDN PT TO
OUT OF SERVICE
RDTLT (continued)
Subfield or
I_CHA_IPTOOS_ Waiting for response to message:

CONF1
CHANGE PRIMARY STATE OF ISDN PT TO
OUT OF SERVICE
I_CHA_IPTOOS_ Send message:

REQ
OBJECT TO OUT OF SERVICE
I_CHA_IPTOOS_ Send message:

REQ1
I_CHA_LTIS_ Waiting for response to message:

CONF
CHANGE PRIMARY STATE OF ISDN LINE
TERMINATION (LT) TO IN SERVICE
I_CHA_LTIS_REQ Send message:

CHANGE PRIMARY STATE OF ISDN LT
I_CHA_LTO-OS_ Waiting for response to message:

CONF
CHANGE PRIMARY STATE OF ISDN LT TO
OUT OF SERVICE
I_CHA_LTO-OS_ Waiting for response to message:

CONF1
CHANGE PRIMARY STATE OF ISDN LT TO
OUT OF SERVICE
I_CHA_LTO-OS_ Send message:

REQ
I_CHA_LTO-OS_ Send message:

REQ1
I_CRE_A1DCT_ Waiting for response to message:

CONF
CREATE FIRST DS-0 CHANNEL
TERMINATION (CT) OBJECT
297-8021-351 Standard 05.02 May 2001

RDTLT (continued)
Subfield or
I_CRE_A1DCT_ Send message:

REQ
CREATE FIRST DS-0 CT OBJECT
I_CRE_A2DCT_ Waiting for response to message:

CONF
CREATE SECOND DS-0 CT OBJECT
I_CRE_A2DCT_ Send message:

REQ
CREATE SECOND DS-0 CT OBJECT
I_CRE_AQDCT_ Waiting for response to message:

CONF
CREATE QDS-0 CT OBJECT
I_CRE_AQDCT_ Send message:

REQ
I_CRE_ICT_ Waiting for response to message:

CONF
CREATE ISDN CT OBJECT
I_CRE_ICT_REQ Send message:

CREATE ISDN CHANNEL TERMINATION
(CT) OBJECT
I_CRE_IPT_ Waiting for response to message:

CONF
CREATE ISDN PT OBJECT
I_CRE_IPT_REQ Send message:

CREATE ISDN PATH TERMINATION (PT)
OBJECT
I_CRE_LT_CONF Waiting for response to message:

CREATE ISDN LT OBJECT
I_CRE_LT_REQ Send message:

CREATE ISDN LINE TERMINATION (LT)
OBJECT
I_DEL_IPT_CONF Waiting for response to message:

DELETE PT AND ALL SUBTENDING
OBJECTS
RDTLT (continued)
Subfield or
I_DEL_IPT_ Waiting for response to message:

CONF1
OBJECTS
I_DEL_IPT_REQ Send message:

DELETE ISDN PT AND ALL SUBTENDING
OBJECTS
I_DEL_IPT_REQ1 Send message:

OBJECTS
I_DEL_IPT_ Waiting for response to message:

CONF1
OBJECTS
I_DEL_IPT_REQ Send message:

OBJECTS
I_DEL_IPT_REQ1 Send message:

OBJECTS
I_DEL_LT_CONF Waiting for response to message:

DELETE LT AND ALL SUBTENDING
OBJECTS
I_DEL_LT_ Waiting for response to message:

CONF1
OBJECTS
I_DEL_LT_REQ Send message:

DELETE ISDN LT AND ALL SUBTENDING
OBJECTS
I_DEL_LT_REQ1 Send message:

DELETE ISDN LT AND ALL SUBTENDING
OBJECTS
297-8021-351 Standard 05.02 May 2001

RDTLT (continued)
Subfield or
P_ACCESS_ Line objects provisioning for analog or

DONE electronic business set (EBS) line done.
P_CHA_LTIS_ Waiting for response to message:

CONF
CHANGE PRIMARY STATE OF LINE TO IN
SERVICE
P_CHA_LTIS_ Send message:

REQ
CHANGE PRIMARY STATE OF LINE TO IN
SERVICE
P_CHA_LTOOS_ Waiting for response to message:

CONF
CHANGE PRIMARY STATE OF LINE TO
OUT OF SERVICE
P_CHA_LTOOS_ Waiting for response to message:

CONF1
OUT OF SERVICE
P_CHA_LTOOS_ Send message:

REQ
OUT OF SERVICE
P_CHA_LTOOS_ Send message:

REQ1
OUT OF SERVICE
P_CRE_LT_ Waiting for response to message:

CONF
CREATE ANALOG OR EBS LT OBJECT
P_CRE_LT_REQ Send message:

CREATE ANALOG OR EBS LINE
TERMINATION (LT) OBJECT
P_DEL_LT_CONF Waiting for response to message:

OBJECTS
RDTLT (continued)
Subfield or
P_DEL_LT_ Waiting for response to message:

CONF1
OBJECTS
P_DEL_LT_REQ Send message:

DELETE LT AND ALL SUBTENDTING
OBJECTS
P_DEL_LT_REQ1 Send message:

DELETE LT AND ALL SUBTENDTING
OBJECTS
P_MOD_LT_ Waiting for response to message:

CONF
MODIFY LT OBJECTS
P_MOD_LT_REQ Send message:

MODIFY ANALOG OR EBS LINE
TERMINATION OBJECT
Note: The above mentioned values that end with 1 are for delete and create operations.
TRANSP see below Rdt line processor transport states

This field identifies the next operation to be
performed by the line provisioning process for
creating the objects for the transport portion
of the cross-connect.
TRANSP_NIL No operations are required.
TRANSP_DONE All operations complete.
I_ADD_TDPT_ Waiting for response to message:

CONF
UPDATE DS-0 CT OBJECT
I_ADD_TDPT_ Send message:

|REQ
UPDATE TRANSPORT SIDE DS-0 CT
OBJECT TO INCLUDE DS0 PT OBJECT
I_CHA_TDPTIS_ Waiting for response to message:

CONF
CHANGE PRIMARY STATE OF DS-0 PT TO
OUT OF SERVICE
297-8021-351 Standard 05.02 May 2001

RDTLT (continued)
Subfield or
I_CHA_TDPTIS_ Send message:

REQ
CHANGE PRIMARY STATE OF DS-0 PT
I_CHA_XCOOS_ No current use.

CONF1
I_CHA_XCOOS_ No current use.

REQ1
I_CRE_TDPT_ Waiting for response to message:

CONF
CREATE DS-0 PT OBJECT
I_CRE_TDPT_ Send message:

REQ
CREATE TRANSPORT SIDE DS-0 PATH
TERMINATION (PT) OBJECT
I_CRE_TQDCT_ Waiting for response to message:

CONF
I_CRE_TQDCT_ Send message:

REQ
CREATE TRANSPORT SIDE QDS-0 CT
OBJECT
I_CRE_XC_CONF Waiting for response to message:

CROSS CONNECTION OBJECT
I_CRE_XC_REQ Send message:

CREATE TRANSPORT SIDE CROSS
CONNECTION OBJECT
I_DEL_TDPT_ Waiting for response to message:

CONF
DELETE DS-0 PT OBJECT
I_DEL_TDPT_ Send message:

REQ
DELETE DS-0 PT OBJECT
I_DEL_TQDCT_ Waiting for response to message:

CONF
DELETE QDS-0 CT OBJECT
RDTLT (continued)
Subfield or
I_DEL_TQDCT_ Waiting for response to message:

CONF1
I_DEL_TQDCT_ Send message:

REQ
I_DEL_TQDCT_ Send message:

REQ1
I_DEL_XC_CONF Waiting for response to message:

DELETE CROSS CONNECTION OBJECT
I_DEL_XC_ Waiting for response to message:

CONF1
I_DEL_XC_REQ Send message:

I_DEL_XC_REQ1 Send message:

Note: The above mentioned values that end with 1 are for delete and create operations.
CONTMARK + or $ Enter + if additional information for this tuple

REQUESTR see below Requesting process

This field allows table control to display the
process that is using RDTLT resources.
The information below allows the table control
software to determine where the request was
initiated from.
REQUESTOR_ No requestor
NIL
REQUESTOR_ Request initiated from RDTLP process.

RDTLP
297-8021-351 Standard 05.02 May 2001

RDTLT (end)
Subfield or
REQUESTOR_ Request initiated from dump and restore

DUMPREST process.
REQUESTOR_ Request initiated from journal file update

JFILE process.
CRV 0 to 4095 Call reference value range

This field represents the call reference value
range.
LOPDONE Y or N Line object provisioning done

This field is set to Y (yes) when all line object
provisioning is complete.
DELALL Y or N Delete all tuples

This field is set to Y (yes) when a request has
been accepted by the table control software
to delete all entries in table RDTLT.
LTIS Y or N Line termination in-service

This field is set to Y (yes) when the line
termination object (LTO) is in service.
INSMOD Y or N In service modifier

This field is set to Y (yes) to identify if a
request to update the in service attributes of
the LTO is sent.
Datafill example
The following example shows sample datafill for table RDTLT.
MAP display example for table RDTLT
RDTLTKEY ACCESS TRANSP NAILUP1

NAILUP2 REQUESTR CRV LOPDONE DELALL LTIS INSMOD
LTCLASS QDS0INFO XCINFO
________________________________________________________
RDT1 00 0 6 11 P_CRE_LT_REQ TRANSP_NIL

REQUESTER_NIL 2 Y Y Y Y
REASONS
Table name
Business Set Reason Display Table
This table displays feature and call progress information messages on display
electronic telephone sets (ETS).
Different reason sets are available for each customer group. Operating
company personnel can form their own reason sets. To create displays in
different languages, datafill a separate reason set. The maximum number of
reason sets is identical to the maximum number of customer groups (that is,
4095).
Switching units with feature package NTX108AA (IBN Display Features)

contain this table.

The following tables must be datafilled after table REASONS.
KSETINV
CUSTSTN
Table size
58 to 237 568 tuples
297-8021-351 Standard 05.02 May 2001

REASONS (continued)
Datafill
The following table lists datafill for table REASONS.
REASNSET alphanumeric (1 to 16 Reason set

characters)
Enter the name of the reason set.
REASONID ACBARRMSG, Reason identification

AINRSNNAMEP,
Enter the name of the reason. Any
AINRSNNAMEO,
entry outside of the range indicated for
AINRSNNUMBERP,
this field is invalid.
AINRSNNUMBERO,
AUTODSPMSG, Enter ACBARRMSG for Automatic Call
BARGEINMSG, Back/Automatic.
CAMPONMSG,
Enter AINRSNNAMEP for Private
CAMPRLMSG,
Name.
CONFMSG,
CPKRMSG, Enter AINRSNNAMEO for Unknown
CXRMSG, Name.
CXRRMSG,
Enter AINRSNNUMBERP for Private
EMWMSG,
Number.
EXTERNALMSG,
INSPAAB, Enter AINRSNNUMBERO for
INSPACB, Unknown Number.
INSPACTGRP,
Enter AUTODSPMSG for Automatic
INSPAUD,
Display Message.
INSPAUL,
INSPBLF, Enter BARGEINMSG for Barge In.
INSPCALLMWT,
Enter CAMPONMSG for Camp On.
INSPCANTINSP,
INSPCCV, Enter CAMPRLMSG for Camp On
INSPCFW, Recall.
INSPCNFKEY,
Enter CONFMSG for Conference.
NSPCNF6,
INSPCNF10, Enter CPKRMSG for CPK Recall.
INSPCNF14,
Enter CXRMSG for CXR Message.
INSPCNF18,
INSPCNF22, Enter CXRRMSG for CXR Recall.
INSPCNF26,
Enter EMWMSG for Executive
INSPCNF30,
Message Waiting.
INSPCPK,
INSPCPU,
INSPCWT,
INSPEBO,
INSPEMW,
REASONS (continued)
REASONID INSPFXDQCK, Enter EXTERNALMSG for Outside

(continued) INSPFXR, Call.
INSPGIC,
Enter INSPAAB for Auto Answer.
INSPHF,
INSPHFMUTE, Enter INSPACB for Inspect Automatic
INSPICM, Call Back Key.
INSPIHOLD,
Enter INSPACTGRP for Inspect Active
INSPLVM,
Group.
INSPMADN,
INSPMCH, Enter INSPAUD for Inspect Automatic
INSPMMI, Dial.
INSPMODE,
Enter INSPAUL for Inspect Automatic
INSPMRF, INSPMSB,
Line.
INSPMUTE,
INSPMWIDC, Enter INSPBLF for Inspect Busy Lamp
INSPMWQRY, Field.
INSPMWT,
Enter INSPCALLMWT for Inspect NN
INSPNOCALL,
Messages Waiting.
INSPNONAME,
INSPNOMSG, Enter INSPMADN for Inspect Shared
INSPNOTPROVD, Number.
INSPNOTPGMED,
Enter INSPMCH for Malicious Hold.
INSPPGMQCK,
INSPPRESS, Enter INSPMMI for Display Demo.
INSPPRL,
Enter INSPMODE for Inspect Mode.
INSPPRV,
INSPQBS, Enter INSPMRF for Inspect Ring
INSPQTD, Forward.
INSPRAG,
Enter INSPMSB for Inspect Make Set
INSPSCL,
Busy.
INSPSCS,
INSPSCU, Enter INSPMUTE for Inspect Mute
INSPSOFTKEY, Key.
INSPSPMSG,
Enter INSPMWIDC for Inspect
INSPTME,
Message Waiting Indication Key.
INSPTWC,
INSPUHOLD, Enter INSPMWQRY for Inspect
INSPUNASSIGN, Message Waiting Query Key.
INSPWIDC,
Enter INSPMWT for Inspect Message
MBGDISPLAY,
Waiting.
NFAVOICEDIR,
NOCPUMSG, Enter INSPNOCALL for Inspect No
ORIGCPUMSG, Calls.
ORIGFWDMSG,
OUTBOUNDMSG,
297-8021-351 Standard 05.02 May 2001

REASONS (continued)
REASONID TERMCFBMSG, Enter INSPNONAME for Inspect No

(continued) TERMCFDMSG, Name.
TERMCFUMSG,
Enter INSPNOMSG for Inspect No
TERMCPUMSG,
Messages.
UNKNOWNMSG
Enter INSPNOTPOVD for Inspect Not
Provided.
Enter INSPNOTPGMED for Inspect
Not Programmed.
Enter INSPPGMQCK for Inspect
programmable Quick Conference Key.
Enter INSPPRESS for Inspect Press a
Key.
Enter INSPPRL for Inspect Privacy
Release.
Enter INSPPRV for Inspect Privacy
Key.
Enter INSPQBS for Inspect Query
Station.
Enter INSPQTD for Inspect Query
Time/Date.
Enter INSPRAG for Inspect Ring
Again.
Enter INSPSCL for Inspect Speedcall
Long.
Enter INSPSCS for Inspect Speedcall
Short.
Enter INSPSCU for Inspect Speedcall
User.
Enter INSPSOFTKEY for Inspect
Softkey.
Enter INSPSPMSG for Inspect Enter
Cell #.
Enter INSPTME for Power Features.
Enter INSPTWC for Inspect Three Way
Call.
REASONS (continued)
REASONID Enter INSPUHOLD for Inspect On Hold

(continued) - Remote.
Enter INSPUNASSIGN for Inspect
Unassigned Key.
Enter INSPWIDC for Message
Indicator.
Enter MBGDISPLAY for Multi-switch
Business Group Display.
Enter NFAVOICEDIR for NFA Voice
Directory.
Enter NOCPUMSG for Call Pickup
Failure.
Enter ORIGCPUMSG for Picked Up.
Enter ORIGFWDMSG for Forward.
Enter OUTBOUNDMSG for
CompuCall Feature.
Enter TERMCFBMSG for Busy
Forward.
Enter TERMCFDMSG for No Answer
Forward.
Enter TERMCFUMSG for Call
Forward.
Enter TERMCPUMSG for Pick Up.
Enter UNKNOWNMSG for No Call
Information.
MESSAGE alphanumeric (up to Displayed message

15 characters)
Enter a descriptive message to
program the option. Enter an
underscore between words to insert a
blank space between words. The
underscore does not appear on the
display.
Datafill example
The following example shows sample datafill for table REASONS.
297-8021-351 Standard 05.02 May 2001

REASONS (end)
MAP display example for table REASONS
REASNSET REASONID MESSAGE
________________________________________________________
WYLIE EXTERNALMSG OUTSIDE_CALL

FURGIE CONFMSG CONFERENCE
DEFAULTSET MBGDISPLAY NETWORK_CALL
NEWSET AINRSNNAMEP AIN_PRIVATE_NAM
Table history
NA012
Added reason ids: AINRSNNAMEP, AINRSNNAMEO,
AINRSNNUMBERP, and AINRSNNUMBERO.
NA004
Added new entry NFAVOICEDIR to field REASONID, for Speech Activated
Intelligent Dialing (SAID) on Meridian business set (MBS).
RECEIVER
Table name
Receiver Table
Table RECEIVER contains the following information for each audio tone
detector, DIGITONE, multifrequency receiver, and mechanized calling card
service:
the code assigned to the equipment in table CLLI
analog equipment for COMMON or GATEWAY switching
digital switching equipment
the equipment location of the circuit
the product engineering code (PEC) of the receiver
The pseudo fixed codes in table CLLI for these circuits appear in the following
table .
Pseudo fixed codes
Title Code Code applicability
DIGITONE receiver RCVRDGT COMMON switches
multifrequency receiver RCVRMF COMMON switches
mechanized calling card receiver RCVRMCCS COMMON switches
audio tone detector RCVRATD COMMON switches
DMS-300 DIGITONE receiver DGT300 gateway switches only
DMS-300 multifrequency receiver MF300 gateway switches only
R2 signaling KSR2OCVR for licensee use only
R2 signaling KSR2ICVR for licensee use only
automatic toll coin service RCVRCOIN TOPS switches only
A-law automatic tone detector RCVATDUK UK operating companies only
A-law DIGITONE receiver RCVRDTUK UK operating companies only
receiver coin detection circuit RCVRCDC restrictions do not apply
297-8021-351 Standard 05.02 May 2001

RECEIVER (continued)
The audio tone detector contains a trunk card with PEC NT5X29AC. The
detector is an option for IBN switching units. Other types of switches do not
require the detector.
Implementation of RCVRCOIN occurs on the NT3X08 card. Each NT3X08

card supports a maximum of eight RCVRCOIN circuits. For every NT3X08
card in the system, this table can contain a maximum of eight entries. Use card
code 3X08AA for feature package NTX208AA (Automatic Coin Toll
Service). Use card code 3X08AB for feature package NTX208AB.
Field CARDCODE indicates the PEC of the receiver. The different groups of
CARDCODE, CLLI, and RCVRTYPE appear in the following table.
The RCVRKEY field accepts a receiver coin detection circuit in the range of
values. The field accepts the circuit to determine the number of five-cent
deposits collected on each call. Enter data in this field in table CLLI.
CARDCODE, CLLI, and RCVRTYPE correlation
CARDCODE CLLI RCVRTYPE
2X48AA MF300 D
2X48AA RCVRMF D
2X48AB RCVRMCCS D
2X48AB RCVRDGT D
2X48AB DGT300 D
2X48CA RCVRMF D
2X48CB RCVRDGT D
2X48CC RCVRDTUK D
3X08AA RCVRCOIN D
3X08AB RCVRCOIN D
3X80AA RCVRCDC D
5X29AB RCVRATD A
5X29AC RCVRATD D
5X29BA RCVATDUK D
The maximum number of circuits of each type is 1024.
The system allocates memory for the total number of circuits for the following
fixed pseudo codes. Field TRKGRSIZ in table CLLI indicates the total
number of circuits.
code DGT300
code KSR2ICVR
code KSR2OCVR
code MF300
code RCVRATD
code RCVRDGT
code RCVRMCCS
code RCVRMF

RECEIVER.
Table size
You can use data to increase table size. To increase table size, change field
TRKGRSIZ in table CLLI for the following fixed pseudo codes:
code DGT300
code KSR2ICVR
code KSR2OCVR
code MF300
code RCVRATD
code RCVRDGT
code RCVRMCCS
code RCVRMF
297-8021-351 Standard 05.02 May 2001

Activation
To allow datafill changes in table RECEIVER to activate:
you can increase table size without a restart after you change the receiver
data of fixed pseudo codes. A load that depends on CSP02 software (post
BCS36) contains the fixed pseudo codes.
a warm restart is a requirement in BCS36 and earlier versions. Perform the
RESTART to allow the ACTS feature to function. If you do not perform
the RESTART, TRAPs occur for each attempt to attach to a RCVRCOIN.
Datafill
Datafill for table RECEIVER appears in the following table.
Subfield or
RCVRKEY see subfields Receiver key. This field contains subfields

CLLI and NUM. This field is the key to the
table.
CLLI RCVRATD Common language location identifier. This

RCVRDGT field indicates the common language location
RCVRMF identifier (CLLI) for the circuit type.
RCVRMCCS
Enter RCVRATD for an audio tone detector
DGT300
circuit.
MF300
KSR2OCVR Enter RCVRDGT for a DIGITONE digital
KSR2ICVR receiver circuit.
RCVRCOIN
Enter RCVRMF for a multifrequency receiver
RCVATDUK
circuit.
RCVRDTUK
or RCVRCDC Enter RCVRMCCS for a mechanized calling
card receiver circuit.
Enter DGT300 for a DIGITONE circuit for
GATEWAY.
Enter MF300 for a multifrequency receiver
circuit for GATEWAY.
Enter KSR2OCVR or KSR2ICVR for an R2
signaling circuit for licensee use only.
Enter RCVRCOIN for an automatic coin toll
service receiver.
Enter RCVADTUK for an A-Law audio tone
detector circuit acceptable for use in the UK.
Subfield or
Enter RCVRDTUK or an A-Law digitone

receiver circuit acceptable for use in the
United Kingdom.
Enter RCVRCDC for a receiver coin detection
circuit.
Only the entries that appear are correct.
NUM 0 to 1023 Circuit number. Enter the number assigned

to the circuit. Entries out of the 0 to 1023
range are not correct.
RCVRTYPE A or D Receiver type. Enter the type of circuit,

analog (A) for COMMON and GATEWAY, or
digital (D) for switching units.
TMTYPE MTM, T8A, Trunk module type. Enter the type of trunk
TM2, TM4 or module where the circuit mounts. Only the
TM8 entries that appear are correct.
TMNO 0 to 2047 Trunk module number. Enter the number of

the trunk module where the circuit mounts. If
the trunk module type is TM2, TM4, TM8, or
T8A, the range is 0 to 2047. If the trunk
module type is MTM, the range is 0 to 255.
297-8021-351 Standard 05.02 May 2001

RECEIVER (end)
Subfield or
TMCKTNO 0 to 29 Trunk module circuit number. Enter the trunk

module circuit number assigned to the circuit.
For an analog receiver, the range is even
numbers 0 to 28 only. For a digital receiver
mounted on trunk module type TM2, TM4,
TM8 or T8A, the range is 0 to 29. For a digital
receiver or audio tone detector mounted on
an MTM, the range is 0 to 24.
CARDCODE 2X48AA Card code. Enter the PEC of the receiver

2X48AB card. Only the entries are correct.
2X48CA
2X48CB
2X48CC
3X08AA
3X08AB
5X29AB
5X29AC or
5X29BA
Datafill example
Sample datafill for table RECEIVER appears in the following example.
MAP example for table RECEIVER
RCVRKEY RCVRTYPE TMTYPE TMNO TMCKTNO CARDCODE

________________________________________________________
RCVRMF 0 D MTM 11 16 2X88AA

RCVRDGT 0 D MTM 4 14 2X88AA
Table history
CSP02
The system does not require a restart to increase table size after you change the
receiver data of fixed pseudo codes.
REGNUM
Table name
TOPS Region Name Table
Table REGNUM is used to associate domestic region names with third
numbers and credit card numbers. A region is a labelled area within the North
American dialing plan. More than one number can be mapped to a region
name, but the region names in this table must have already existed in table
DOMBILL. If a number does not appear in table REGNUM, its region is
assumed to be the United States or Canada and domestic billing restrictions do
not apply. Table REGNUM is to be used with other regions within the North
American dialing plan, such as Jamaica, Mexico, or the Caribbean.

Table DOMBILL must be datafilled before table REGNUM.
Table size
The table size of table REGNUM is dynamic and is subject to the system's
store requirements for digilators.
Datafill
The following table lists datafill for table REGNUM.
Field descriptions
Subfield or
DOMNUM 0 to 9 Domestic number. Enter the domestic third

(up to 18 number or credit card number to be mapped
digits) to a region. This number consistd of a
numbering plan area (NPA) or revenue
accounting office (RAO) number followed by
three digits in the format NPA Nxx, RAO 0xx,
or RAO 1xx (where N = 2 to 9 and x = 0 to 9).
More than one number can be mapped
against a region name. As of BCS36, the
NPA has a range of 200 to 999.
REGION alphanumeric Region name. Enter the region name as

(1 to 16 previously datafilled in table DOMBILL.
characters)
297-8021-351 Standard 05.02 May 2001

REGNUM (end)
Datafill example
The following example shows sample datafill for table REGNUM.
MAP display example for table REGNUM
DOMNUM REGION
________________________________________________________
234158 CANADA
Table history
BCS36
Range information was added for NPA in field DOMNUM.
REMNACD
Table name
Remote Network Automatic Call Distribution Table
Table REMNACD provides the routing information associated with a network
automatic call distribution (NACD) group on a remote switch.
For related information, refer to table ACDGRP.

There is no requirement to datafill other tables prior to table REMNACD.
Datafill
The following table lists datafill for table REMNACD.
Subfield or
REMGROUP alphanumeric (1 Remote ACD group. Enter the name

to 16 characters) assigned to the remote ACD group.
REMOTEDN 10 digits Remote directory number. Enter the 10-digit

primary directory number of the remote ACD
group.
ROUTE see subfields Route. This field consists of subfields

TABNAME and INDEX.
TABNAME IBNRTE, Table name. Enter the table name (IBNRTE,

IBNRT2, IBNRT3, IBNRT2, IBNRT3, or IBNRT4) to which
IBNRT4 translation routes.
INDEX 1 to 1023 Index. Enter the number assigned to the

route list in table IBNRTE, IBNRT2, IBNRT3,
or IBNRT4 to which translation routes. Any
entry outside of the range indicated for this
field is invalid.
297-8021-351 Standard 05.02 May 2001

REMNACD (end)
Subfield or
OPTIONS NONDMS Options. If the remote NACD group is for a

non-DMS switch, then enter NONDMS and
datafill refinement TRGTRI.
TRGTRI 0 to 255 Target resource index. If the entry in field

OPTIONS is NONDMS, then enter the
hard-coded resource index for the non-DMS
remote NACD group. Any entry outside of the
range indicated for this field is invalid.
Datafill example
The following example shows sample datafill for table REMNACD.
In this example, ACD group RSWB5 has a DN of 6135554500, and routes to

IBNRTE 3 and to a DMS switch.
MAP display example for table REMNACD
REMGROUP REMOTEDN ROUTE OPTIONS

________________________________________________________
RSWB5 6135554500 IBNRTE 3 $
REMOTLAC
Table name
Remote Location Area Code Table
Table REMOTLAC determines the new routeset for a mobile subscriber (MS)
in a different location area. The current visitor location register (VLR) or
mobile switching center (MSC) does not always serve the new location area.
In this event, entry of the new location area does not occur in table LAC. The
system queries table REMOTLAC. The system can request a VLR number to
identify the correct close VLR. The system can request an MSC number that
identifies the correct close MSC.
See table LAC for related information.

REMOTLAC.
You cannot enter a location area code (LAC) entered in table LAC in table
REMOTLAC. You cannot enter a LAC entered in table REMOTLAC in table
LAC.
Table size
0 to 2432 tuples
297-8021-351 Standard 05.02 May 2001

REMOTLAC (continued)
Datafill
Datafill for table REMOTLAC appears in the following table.
Subfield or
LAC 1 to 65 535 Location area code.

This field is the key field that identifies the location
area in which the mobile roams.
VLRNUM see subfields Visitor location register number.

This field contains the VLR address of the old VLR
in ISDN (E.164) format. This field contains
subfields VLRCC, VLRNDC, and VLRSN.
The entry in field VLRNUM can be the same as the
entry in field MSCNUM. Each number must
identify a VLR.
VLRCC 0 to 9 Visitor location register country code.

(one to three Enter the visitor location register country code
digits) (CC). An entry of 0 cannot be the first digit in the
number.
VLRVDC 0 to 9 Visitor location register national destination code.

(a maximum Enter the VLR national destination code (NDC).
of six digits)
VLRSN 0 to 9 Visitor location register subscriber number.

(a maximum Enter the VLR subscriber number (SN).
of 13 digits)
MSCNUM see subfield Mobile switching center number.

This field contains the MSC address of the new
MSC to serve the mobile in ISDN (E.164) format.
This field contains subfields MSCCC, MSCNDC,
and MSCSN. Separate each subfield with a single
space.
The entry in field MSCNUM can be the same as the
entry in field VLRNUM. Each number must identify
a VLR.
MSCCC 0 to 9 Mobile switching center country code.

(1 to 3 digits) Enter the MSC CC. An entry of 0 cannot be the
first digit in the number.
REMOTLAC (end)
Subfield or
MCSNDC 0 to 9 Mobile switching center national destination code.

(a maximum Enter the MSC NDC.
of 6 digits)
MSCSN 0 to 9 Mobile switching center subscriber number.

(a maximum Enter the MSC SN.
of 13 digits)
Datafill example
Sample datafill for table REMOTLAC appears in the following example.
MAP example for table REMOTLAC
LAC VLRNUM MSCNUM

________________________________________________________
3 1 214 6845582 1 214 6845539

783 678 1 1 678 1 129455
Table history
BCS36
Table REMOTLAC was introduced in BCS36.
REMOTLAC.
Dump and restore

297-8021-351 Standard 05.02 May 2001

REPLCODE
Table name
Replace Code Table
Table REPLCODE is used in replacing one-, two-, or three-digit codes with a
sequence of digits for a given feature (presently only number service code
[NSC]).
The dialed cell number is replaced with the actual digits that would have been
dialed if speed calling were not in effect.

The following tables must be datafilled before table REPLCODE.
REPLNAME
COSMAP
Table size
The maximum size of table REPLCODE depends upon the datafill in table
REPLNAME. The memory size for both tables is allocated dynamically.
There can be 0 to 1024 tuples in table REPLNAME, and each tuple can be
referenced 1000 times in table REPLCODE. Consequently, the size of table
REPLCODE can grow to be 1 024 000 tuples.
Datafill
The following table lists datafill for table REPLCODE.
Subfield or
REPLCDKY see subfields Replace code key

This field consists of subfields REPLNAME
and REPLNO.
REPLNAME alphanumeric Replace name

Enter the unique name, predefined in table
REPLNAME, field REPLNMKY.
REPLNO 0 to 999 Replace number

Enter the cell number to be replaced.
REPLCODE (end)
Subfield or
REPLDIGS numeric Replace digits

(vector of up
Enter the actual digits that replace the cell
to 30 digits)
number.
REPLDATA see subfields Replace data

This field consists of subfields REPSEL and
COSMAP.
REPLSEL REPLorNSC Replace selector

Enter the value matching the entry used in
field REPLNAME. This entry must match the
one in field REPLSEL in table REPLNAME.
COSMAP alphanumeric Class-of-service mapping name

If the entry in filed REPLSEL is NSC, enter the
name used to screen and map the network
class of service (NCOS) for a given network
speed call. This name must be datafilled in
table COSMAP.
Datafill example
An example of datafill for table REPLCODE is shown below.
Call processing software takes the cell numbers 14 and 123 and replaces them
with 63674118 and 96225214. It uses the COSMAP1 and COSMAP2
mapping from table COSMAP to validate the current NCOS and possibly
update it, then retranslates using the new NCOS with these replaced digits.
MAP display example for table REPLCODE
REPLCDKY REPLDIGS REPLDATA

________________________________________________________
NSCIBN1 14 63674118 NSC COSMAP1

NSCIBN2 123 96225214 NSC COSMAP2
297-8021-351 Standard 05.02 May 2001

REPLNAME
Table name
Replace Name Table
Overview
For related information, refer to table REPLCODE.
Feature package NTX432AA (Network Speed Calling) permits the customer

to define a list of up to 1000 network speed calling (NSC) numbers for each
customer group on the assumption that all use the new translation selector
devised for NSC. This selector, namely NSC, is defined in table IBNXLA.
NSC numbers have priority and restriction class marks available so that low
priority users can have their calling class upgraded for pre-programmed
business destinations.
Electronic Switched Network (ESN) supports a mixture of two- and three-digit

speed numbers plus access code. A suggested dialing plan for speed numbers
is
IMXX IRX
where M = 1 through 0 R = 1 through 0 while R and M cannot conflict
The two suggested access codes, namely IMXX and IRX, are only a subset of
what is possible.
The access code for network speed call is followed by the cell number to
indicate which speed call number is desired.
Access codes are implemented through Integrated Business Network (IBN)

translation, using table IBNXLA. The speed call cell number itself can be
handled as an access code from the viewpoint of translation.
Different customer groups can have different translators and hence different
access codes.
Access to NSC list can be made available to IBN originators of any kind: lines,
trunks, attendant consoles, directory numbers (DN), and so on. However, it is
possible to restrict the use of particular NSC numbers according to the network
class of service (NCOS) of the originator.
Calls that require retranslation (for example, calls via a Virtual Facility Group)
cannot be routed to make a Network Speed Call.
REPLNAME (continued)
Table REPLNAME is used to predefine all the valid names for particular
access codes that can be used in table REPLCODE. Once a predefined name
is associate with a particular selector, that is, NSC, it forces the user to allocate
each name for only one purpose. Finally, a maximum number of allowable
entries (in table REPLCODE) for each name-selector combination is
identified.
One could look at table REPLNAME as the control or head table and table
REPLCODE as the subtable.

There is no requirement to datafill other tables prior to table REPLNAME.
Table size
1 to 2040 tuples
Datafill
The following table lists datafill for table REPLNAME.
Field descriptions
Subfield or
REPLNMKY alphanumeric Replace name key

(up to 16
Define a unique name to be used in
characters)
conjunction with a particular feature (for
example network speed call) access code.
REPLSEL REPLorNSC Replace selector

Enter the feature that uses the above
REPLNMKY in table REPLCODE.
Enter REPL for features that make use of
replacement digits and have no specific data
requirements.
Enter NSC for network speed call.
NOITEMS 1 to 1000 Number of items

Enter the maximum number of entries to be
datafilled in table REPLCODE for the above
REPLNMKY.
297-8021-351 Standard 05.02 May 2001

REPLNAME (end)
Datafill example
Since this table is used only in conjunction with the NSC feature, verify first
that table IBNXLA has TRSEL = NSC.
An example of datafill for table REPLNAME is shown below.
MAP display example for table REPLNAME
REPLNMKY REPLSEL NOITEMS
________________________________________________________
NSCINB1 NSC 300

NSCINB1 NSC 100
REROUTE
Table name
Network Management Reroute Control Table
Refer to subtable REROUTE.NWMRROUT.

Table size
Datafill
An example of datafill for table REROUTE is shown below.
MAP display example for table REROUTE
RRTNO NWMRROUT
________________________________________________________
0 ( 3)
297-8021-351 Standard 05.02 May 2001

REROUTE.NWMRROUT
Table name
Network Management Reroute Subtable
The following table lists all the network management reroute tables.
Network Management Reroute Tables
REROUTE No form
REROUTE.NWNRROUT 2190 Network Management Reroute Subtable

Record
Subtable REROUTE.NWMRROUT redirects a percentage of traffic on a

normal route to another route.
Table REROUTE and subtable REROUTE.NWMRROUT are accessed during

translation of a call as follows:
1. Translation through a route table, such as table OFRT or subtable
HNPACONT.RTEREF, encounters a route element with field RTESEL set
to T, field TABID set to RRTE3, and field KEY set to the required reroute
number.
2. DMS translation now determines whether the Network Management
Reroute feature for the required reroute number is activated and proceeds
as described in subset a or subset b below.
a. Network Management Reroute feature is not activated for the reroute
number. No calls are redirected, and all calls proceed to the next
route element in the route list of the route table.
b. Network Management Reroute feature is activated for the reroute
number; the Network Management Reroute feature activation
command (at the NWM level of a MAP) has the following form:
REROUT APPLY rrteno rrtesub {level}
where
rrteno
is the reroute number
REROUTE.NWMRROUT (continued)
rrtesub
is the index into subtable REROUTE.NWMRROUT where the
percentage of calls to redirect is found in field LEVEL and the routing
of redirected calls is found in fields TABID and KEY {level} if
specified, it overrides the percentage of calls to redirect specified in field
LEVEL in subtable REROUTE.NWMRROUT
Subtable REROUTE.NWMRROUT lists the routes to which traffic is rerouted

for a given percentage of busy traffic. Only 1 of the 16 entries can be activated
at one time.
For foreign numbering plan area (FNPA) with six-digit translation, subtable
REROUTE.NWMRROUT can only be applied to foreign NPAs with a route
list. An example is FNPAs that are provided with route reference subtables by
datafilling input forms 2432A and B.
The operating company datafills one form 2190 for each reroute subtable up to
a maximum of 1024 tuples.

The following tables must be datafilled before table
REROUTE.NWMRROUT.
IBNRTE
IBNRT2
IBNRT3
IBNRT4
297-8021-351 Standard 05.02 May 2001

REROUTE.NWMRROUT (continued)
Table size
0 to 1024 tuples
Field descriptions
Subfield or
RRTSUB 0 to 15 Reroute subtable index

Enter the index into subtable
REROUTE.NWMRROUT.
NEWROUTE see subfields New route

This field consists of subfields TABID and
KEY.
TABID IBNRTE Table identification

IBNRT2
In a local/toll office enter table OFRT (Office
IBNRT3
Route) or one of the four IBNRTE (Integrated
IBNRT4
Business Network Route) tables to which the
OFRTorOVR
percentage of traffic (level) is redirected if the
0 to OVR9
Reroute feature is activated.
In a DMS-300 office, enter OVR0 to OVR9
(Overseas Route) to which the percentage of
traffic (level) is redirected if the Network
Management Reroute feature is activated.
Any entry outside this range is invalid.
KEY 0 to 1023 Key

Enter the index into table specified in field
TABID.
LEVEL 0 to 100 Level

Enter the percentage of traffic redirected
when the Network Management Reroute
feature is activated.
Datafill example
An example for datafill for subtable REROUTE.NWMRROUT is shown
below.
REROUTE.NWMRROUT (end)
In this example
Memory is internally allocated in table REROUTE.
The input data is for one subtable that is numbered 0 (zero).
Memory is internally allocated for the reroute values in subtable
NWMRROUT 0.
If Network Management Reroute Feature is activated for reroute subtable
0 (RRTSUB 0), 35% of the traffic is rerouted by table OFRT, index 3.
If Network Management Reroute Feature is activated for reroute subtable
1 (RTSUB 1), 40% of the traffic is rerouted by table OFRT, index 3.
If Network Management Reroute Feature is activated for reroute table 2
(RRTSUB 2), 45% of the traffic is rerouted by table OFRT, index 4.
Note 1: In any one reroute subtable, only one RRTSUB can be activated
at any time.
Note 2: For definition of commands see the Basic Translations Tools

Guide.
MAP display example for table REROUTE.NWMRROUT
RRTSUB NEWROUTE LEVEL

________________________________________________________
0 OFRT 3 35
1 OFRT 3 40
2 OFRT 4 45
297-8021-351 Standard 05.02 May 2001

Data shema tables
297-8021-351 Preliminary 10.01 September 2004

Data schema 1-1
RESFEAT
Table name
Residential Line Feature
Table RESFEAT contains the assignment of custom local area signaling
services (CLASS) features for residential lines.
CLASS features are as follows:

Automatic Call Blocking (ACB)
Anonymous Caller Rejection (ACRJ)
Analog Display Services Interface (ADSI)
Automatic Recall (AR)
Call Logging (CALLOG)
CLASS Message Waiting Indicator (CMWI)
Calling Name Delivery Blocking (CNAB)
Calling Name Delivery (CNAMD)
Calling Number Delivery (CND)
Calling Number Delivery Blocking (CNDB)
Customer Originated Trace (COT)
Deluxe Spontaneous Call Waiting Identification (DSCWID)
Dialable Number Delivery (DDN)
Distinctive Ringing Call Waiting (DRCW)
Redirecting Number and Reason Delivery (RND)
Selective Call Acceptance (SCA)
Selective Call Forwarding (SCF)
Selective Call Rejection (SCRJ)
Spontaneous Call Waiting Identification (SCWID)
Note 1: CND and DDN are incompatible features and are mutually
exclusive.
Note 2: Assign Screening List Editing (SLE) features (DRCW, SCA, SCF,
SCRJ) to directory numbers (DNs) on integrated services digital network
(ISDN) sets. SLE features assigned to ISDN sets are in the index by the
DMS-100 Family Customer Data Schema Reference Manual Volume 9 of 12, SN07 (DMS) and up
1-2 Data schema
RESFEAT (continued)
logical terminal identification (LTID). There is one tuple for each DN key
that has the SLE feature.
Note 3: As of BCS36, CLASS features can be assigned to data units.
The following paragraphs describe the CLASS features available for

residential lines.
Automatic Call Back (ACB)

This feature allows a subscriber to place a call to the last station the subscriber
called. If the destination line is busy, ACB monitors the line until it becomes
idle and can accept the call.
Anonymous Caller Rejection (ACRJ)

This feature allows the subscriber to reject incoming calls from callers who
have intentionally blocked their caller identification information.
The ACRJ option requires NT1X77AA and NT1X79AA digital recorded

announcement (DRA) cards for recording customized announcements,
including rejection and activation/deactivation confirming announcements.
ACRJ can be assigned to the pilots and individual members of multiline hunt
(MLH) and distributed line hunt (DLH) groups. ACRJ must be assigned to
directory number hunt (DNH) groups on an individual basis. ACRJ may be
assigned to only the primary member of a multiple access directory group
(MADN).
ACRJ can be used with Meridian Business sets but not with Integrated Voice
and Data Sets or ISDN sets.

This feature is used to distinguish between the audio and visual types of access
for SLE features. When ADSI is assigned to a line with the SLE feature, Visual
Screen List Editing (VSLE) is accessed if the customer premises equipment
(CPE) acknowledges the CPE alerting signal (CAS) or query tone with a
dual-tone multifrequency (DTMF) A tone. The host peripheral module (PM)
on the line must have a unified processor (UP), a universal tone receiver
(UTR), a CLASS modem resource card (CMR), and the 6X69AD tone and
messaging card. Access to the ADSI line option is allowed in table RESOFC
when the ADSI tuple is enabled.
The SLE function allows subscribers to screen specific incoming calls for
special treatment. In a VSLE session, using the ADSI protocol and the
ADSI-compatible display set, the main list editing level is replaced with a

Data schema 1-3
RESFEAT (continued)
visual display of feature status information. The subscriber uses scrolling

softkeys that move through items in the screening list.
The ADSI feature is always assigned with subfield AMA set to NOAMA and
subfield STATUS set to ACT (active).

This feature allows a subscriber to place a call to the last station that called the
subscriber. If the destination line is busy, AR monitors it until it becomes idle
and can accept the call.
AR can also be activated as a two-level procedure featuring three types of

announcements depending on the type of the incoming call: the DN
announcement, the private DN announcement, and the invalid DN
announcement. With the DN announcement, the subscriber hears an
announcement stating the DN of the last incoming call as well as the date and
time of that call. The subscriber is then instructed to dial the digit 1 to activate
AR or hang up to abort AR.

This feature provides the subscriber with information related to busy,
unanswered, or forwarded calls.
The subscriber accesses this feature by dialing an appropriate activation code

and views the information using softkeys on SESAME customer premise
equipment (CPE). Upon viewing, the subscriber receives the following
information for each call:
the DN and name of the calling party, when available
the time and date of the call's arrival
the number of times the calling party called
the status (unanswered, forwarded, or busy) of the subscriber's line when
the call was logged
The CALLOG option is not allowed on an MLH/DLH hunt member.

This feature builds on the Message Waiting (MWT) feature. The MWT feature
allows users to have a list of messages stored against their station in the DMS
switch or at a message center. When a message is queued against the user's
station, the message waiting indicator associated with the station is activated.
When the last message is retrieved by the user, the message waiting indicator
is deactivated.
1-4 Data schema
RESFEAT (continued)
The CMWI feature provides a means of controlling the message waiting

indicator on a CLASS set.
Subscribers must have option MWT assigned to their lines before option
CMWI can be added.
The subscriber must be equipped with a set capable of receiving and

understanding CLASS modem transmissions. The CLASS Modem Resource
(CMR) card is used to transmit the lamp/display information to the set.
The CMWI feature is activated when enabled in the office and assigned to the
line. The CMWI subscribers can activate or deactivate the ringing option by
dialing the CMWIRING activation and deactivation codes from their sets.

This feature allows delivery of the calling name to be blocked.
When feature package NTXE46AA is present, the CNAB options provide the
ability to activate the CNB (Calling Number Blocking), CNNB (Calling Name
Number Blocking), and CNND (Calling Name Number Delivery) options.

This feature delivers the calling party's name, current time, and date to the
terminating line between the first two rings of every incoming call, provided
the host PM on the line has a CMR card and CNAMD is turned on for the
switching unit in table RESOFC.
Feature CNAMD with automatic message accounting (AMA) allows

subscription usage sensitive pricing (SUSP) for CNAMD. An AMA record is
generated for each delivery of calling information on calls terminating to the
line. The user must dial the CNAMD SUSP activation code datafilled in table
IBNXLA to activate CNAMD with AMA. AMA is only available if field
SUSP in table AMAOPTS is set to ON.
For ISDN basic rate interface (BRI) lines, use the Aggregate CND Recording
(ACR) line option to generate ISDN-specific AMA billing records. Option
ACR differentiates between voiceband information (VI) and circuit-mode data
(CMD) calls in the AMA records it produces. Option ACR is an extension of
the CND feature. Option ACR requires that the line has the CND feature and
that CND is enabled for the switch in table RESOFC. Feature CNAMD is
optional for use with the ACR line option.

Data schema 1-5
RESFEAT (continued)
No activation code is required if the line has feature CNAMD with no AMA.
Delivery of calling name information is automatic.
Note: All CLASS display features (CNAMD, CND, and DDN) with AMA
use the same CND SUSP activation or deactivation code datafilled in table
IBNXLA. Dialing the CND SUSP activation code activates all display
features with AMA. The subscriber cannot turn on or off a single display
feature leaving others unaffected.

This feature indicates that the line receives calling information on calls
terminating to the line, provided the host PM on the line has a CMR card and
CND is turned on for the switching unit in table RESOFC.
Table LTCINV or table RCCINV must be datafilled with a CMR card in field
OPTCARD for the host PM of the line.
Note: If table LTCINV or table RCCINV is not datafilled, the CND feature
is still added to the line.
Feature CND with AMA allows SUSP for the feature. An AMA record is
generated for each delivery of calling information on calls terminating to the
line. The user must dial the CND SUSP activation code that is datafilled in
table IBNXLA to activate CND with AMA. AMA is only available if the
SUSP option in table AMAOPTS is set ON.
For ISDN BRI lines, use the ACR line option to generate ISDN-specific AMA
billing records for VI and CMD. Option ACR differentiates between VI and
CMD calls in the AMA records it produces. Option ACR is an extension of the
CND feature. Option ACR requires that the line has the CND feature and that
CND is enabled for the switch in table RESOFC.

This feature allows delivery of the calling number to be blocked.
The CNDB option cannot be assigned to Meridian business sets (MBS).
When feature package NTXE46AA is present, the CNDB options provide the
ability to activate the CNB (Calling Number Blocking), CNNB (Calling Name
Number Blocking), and CNND (Calling Name Number Delivery) options.

This feature allows the recipient of a harassing call to request an automatic
trace of the call.
1-6 Data schema
RESFEAT (continued)
Deluxe Spontaneous Call Waiting Identification (DSCWID)

This feature allows a subscriber to receive calling party information during
Call Waiting (CWT) and control the treatment of incoming calls with a set of
disposition options. The host PM must have a CMR card, and the DSCWID
feature must be turned on for the switching unit in table RESOFC. The
disposition options are available through softkeys on an ADSI-compliant CPE.
The term softkey refers to the context-sensitive keys on the CPE that change
function according to the type of service and the menu levels within the
service.
The DSCWID subscriber receives one of two types of CWT alerting

sequences: subscriber alerting signal (SAS) or a SAS followed by a CPE
alerting signal (CAS). The SAS is the normal CWT tone that a subscriber
hears. The SAS followed by a CAS is necessary to alert the CPE to display the
DSCWID options on the ADSI-compliant CPE as well as to send caller
identification (CID) to the CPE if a CID feature, such as CND, DDN, or
CNAMD, is assigned to the DSCWID subscriber's line.
After the CWT tone indicates to the DSCWID subscriber that a call is waiting,
the CPE displays calling party information (name, number, or both name and
number) and softkey options from which the subscriber can choose a
disposition for the waiting call.
The DSCWID subscriber can choose one of the following options for treating
the second (incoming) call:
Answer the new call and put the existing call on hold.
Disconnect the existing call and answer the new call.
Connect the new call to a busy announcement.
Forward the new call.
Put the new call on hold after connecting to a hold announcement.
Conference the new call with the existing call.
Dialable Number Delivery (DDN)

This feature indicates that the line receives calling information in the form of
a dialable DN on calls terminating to the line. The information is delivered,
provided that the host PM of the line has a CMR card and that feature DDN is
turned on for the switching unit in table RESOFC.
Feature DDN is an enhancement to the CLASS CND feature. The DDN

feature delivers the calling number to the subscriber with the digits the
subscriber dials to reach the calling party. When feature DDN with NOAMA
is assigned to a line, delivery of calling information is automatically activated.

Data schema 1-7
RESFEAT (continued)
No AMA records are generated for delivery of calling information to a DDN

NOAMA line.
Feature DDN with AMA allows SUSP for feature DDN. An activation code
CND SUSP datafilled in table IBNXLA must be dialed in order to activate
delivery of calling information. Once this activation code has been dialed, an
AMA record is generated each time the calling information is delivered to the
line. Feature DDN with the AMA option is also referred to as DDN SUSP.
Table LTCINV or table RCCINV must be datafilled with a CMR card in field
OPTCARD for the host PM of the line.
Note: If table LTCINV or table RCCINV is not datafilled, the CND is still
added to the line.
Distinctive Ringing/Call Waiting (DRCW)

This feature allows a subscriber to identify a list of directory numbers by
receiving distinctive alerting treatment. The DNs, given distinctive alerting
treatment, are built into a list through the SLE facility. These terminating
alerting treatments are different from standard power ringing and call-waiting
tone. The caller only receives standard audible ringing.
The distinctive alerting is given when a call is received from a DN that is on

the list of numbers referred to as the DRCW list. If a call is made to a DRCW
subscriber's line while it is busy, the distinctive call waiting tone is given if the
following conditions apply.
The line has standard call waiting assigned to it.
A call can be waited.
The calling DN is on the operating company's DRCW list. Calling DNs not
on the DRCW list are identified using standard call waiting treatment.
Distinctive call waiting is the same as Call Waiting, except during alerting
treatment. If DNs of the incoming calls cannot be identified or do not exist on
the DRCW screening list, then standard alerting treatment is provided for these
incoming calls.
Feature DCRW supports the lines that are connected to the following PMs:
line concentrating modules (LCM)
remote LCMs (RLCM)
outside plant modules (OPM)
line modules (LM)
1-8 Data schema
RESFEAT (continued)
remote LMs (RLM)

subscriber carrier modules (SCM)
subscriber carrier module urban (SCM-100U/RCU)
subscriber carrier module SLC-96 (SCM-100S/RCS)
subscriber carrier module rural (SCM-100R/RCT)
The ring types supported are coded, superimposed, and frequency selective
ringing, shown in the following table below with the different PMs.
Ring types
PM types Ring type
LCM Coded
LM Coded
OPM Coded
RLCM Coded
RLM Coded
SCM-100S/RCS Frequency selective
SCM-100R/RCT Superimposed
SCM-100U/RCU Coded
DCRW ringing pattern varies according to the ring type. For coded and
superimposed frequencies, the ringing pattern is on-off-on-off as shown in the
figure below.
Ringing pattern for coded and superimposed frequencies
short long short
off off to the end of ring cycle

Data schema 1-9
RESFEAT (continued)
The duration of the ringing components for the coded and superimposed ring
types vary according to the following conditions.
If the subscriber line is connected to an LCM, LM, OPM, RLCM, or RM, then
durations are as shown in the following table.
LCM, LM, OPM, RLCM, RM ringing duration
Ringing type Short ring Long ring Inter-ring silence
Coded 20 Hz 500 ms 1000 ms 500 ms
Coded 30 Hz 450 ms 900 ms 450 ms
Coded 30 Hz 500 ms 1000 ms 500 ms

(see Note)
Superimposed 460 ms 920 ms 460 ms
Note: If the optional package NTX101 (IBN Enhanced Services) is present in the office, Coded 30
Hz is the same as Coded 20 Hz.
If the subscriber line is connected to an SCM, then the durations are as shown
in the following table.
SCM ringing duration
Ringing type Short ring Long ring Inter-ring silence
Coded 20 Hz 500 ms 1000 ms 500 ms
Coded 30 Hz 500 ms 1000 ms 500 ms
Superimposed 500 ms 1000 ms 500 ms
Frequency selective ringing

For frequency selective ringing, the DRCW ring pattern is on-off-on as shown
in the figures below.
If the subscriber line is connected to an LCM, LM, OPM, RLCM, or RLM, the
pattern heard by the subscriber is short-short as shown in the figure below.
1-10 Data schema
RESFEAT (continued)
Ringing pattern for subscriber line connected to LCM, LM, RLCM, RLM
short short
The duration of the ringing components is shown in the following table.

Duration of components
First short Second short Inter-ring silence
Frequency 600 ms 640 ms 700 ms

selective
If the subscriber is connected to an SCM, then the pattern heard by the

subscriber is long-long as shown in the figure below.
Ringing pattern for subscriber line connected to SCM
long long

Data schema 1-11
RESFEAT (continued)
The duration of the ringing components is shown in the following table.

Duration of components for SCM
First long Second long Inter-ring silence
Frequency 1000 ms 1000 ms 500 ms

selective
The distinctive call waiting tone of the DRCW feature consists of different
length bursts of 440 Hz tone. The pattern provided is on-off-on-off-on as
shown in figure below.
Ringing pattern for coded and superimposed frequencies
short long short
off off
The duration for each segment is shown in the following table.

Segment durations
Short tone Long tone Inter-tone silence
100 ms 500 ms 100 ms

This feature allows redirecting number and reason delivery for ISDN call
forwarding. Add option RND to the DN by SERVORD to set RND for an
ISDN line as flat-rate or SUSP. SERVORD automatically updates table
RESFEAT with a tuple for each DN assigned the RND option.
Enter Y in the ENABLED subfield for the RND tuple in table RESOFC to
enable the RND line option Universal access does not apply to RND. Set field
ACCESS to SUBSCR for subscription access only billing.
1-12 Data schema
RESFEAT (continued)

This feature allows a subscriber to selectively accept calls arriving from a set
of DNs as specified in an SCA list that is built using the SLE facility. The
customer activates feature SCA by dialling the SCA access code that is
datafilled in table IBNXLA and enters the SLE session.
Any call that terminates to a line with feature SCA is screened by the SCA
feature before any other terminating feature is enabled. If feature SCA is active
and the incoming calls DN is not on the SCA list, the caller is given SCA
treatment. Any toll call is charged for the call if specified in table RESOFC. If
screening cannot be applied owing to system failure, lack of resources, or the
calling DN is not available, the call is given SCA treatment. Feature SCA only
allows calls that can be screened to terminate.
The exception to SCA screening is any incoming call from an operator no-test
trunk. This provides a limited capability to allow completion of emergency
calls to an SCA line that originates from lines not on the SCA list. The operator
can then inform the SCA user of the emergency call. Handling of the call at
that point is up to the discretion of the SCA user.
When DND_ONLY=Y callers on the SCA list will bypass DND when it is
active, provided RES00102 is active. When DND_ONLY=N, then callers on
the SCA list will not terminate when DND is active. For information on the
Enhanced DND feature, refer to DMS-100 Family NA100 Translation Guide.

This feature allows a subscriber to selectively forward calls arriving from a set
of DNs as specified in an SCF list built using the SLE facility. The subscriber
activates feature SCF by dialing the SCF access code datafilled in table
IBNXLA and entering the SLE sessions.
Feature SCF takes precedence over other kinds of call forwarding. For
example, if a line has both features SCF and CFU active and the calling DN
appears on the line's SCF list, the call is forwarded to both the SCF feature and
the DN.
Tuples for feature SCF in table RESFEAT cannot be added or deleted. Each
tuple can only be modified. Tuples are automatically added or deleted to this
table when feature SCF for the lines is added in table IBNFEAT.

SCRJ allows a subscriber to selectively reject calls arriving from a limited set
of previously identified DNs. The rejected DNs are built into a list by the SLE
facility. Calls that are rejected are given treatment SCRJ.

Data schema 1-13
RESFEAT (continued)
The subscriber initiates an SCRJ SLE session by dialing the SCRJ code. The
access code is specified in table IBNXLA. The subscriber with SCRJ is not
advised, in any way, that calls are being rejected. When the incoming call
screened is a forwarded call, the originating DN, not a forwarding station's
DN, is screened.

This feature allows a subscriber to receive calling party information in
conjunction with a call waiting tone.
To assign SCWID to a line, CWT must be assigned to the line either at the
same time or before SCWID is added. At least one display option (DDN, CND,
or CNAMD) must be assigned to the line either at the same time or before
SCWID is added.
If the CWT option is deleted from a SCWID line, the SCWID option must be
removed first. SCWID must be deleted either at the same time or before the
last display option is removed.
If RES_SO_SIMPLIFICATION is TRUE, the SCWID line option can be

added to lines that have been assigned the RES, 1FR, or 1MR line class code.
With feature package NTXE58AA, SCWID can be assigned to lines with an

LCC of IBN.
With feature package NTXE64AA, SCWID can be assigned to LCCs of OWT,

EOW, INW, 2WW, and ETW.

The following tables must be datafilled before table RESFEAT:
RESOFC
IBNLINES
1-14 Data schema
RESFEAT (continued)
Datafill
The following table lists datafill for table RESFEAT.
Field descriptions
LINE see subfields Line Equipment Number

This field is the key to table RESFEAT. It
is identical to field LEN. Field LEN defines
the physical location of the equipment that
is connected to a specific telephone line.
Because field LEN is common to more
than 60 tables, it is documented in a single
section to avoid unnecessary duplication.
Refer to section Common entry field
LEN" for a complete description of field
LEN and associated subfields.
For ISDN lines, field LEN consists of
subfield LTID. For non-ISDN lines, field
LEN consists of subfields SITE, FRAME,
UNIT, DRAWER or LSG, SHELF, SLOT,
and CIRCUIT.
KEY 0 to 76 Key
This field contains the possible physical
keys for a DN appearance on a Meridian
business set (MBS). A non-MBS set
always has a key of 0 (zero). All keysets
have range of 1 to 69.

Data schema 1-15
RESFEAT (continued)
Field descriptions
FEAT ACB, ACRJ, CLASS feature

ADSI, AR,
Enter ACB for Automatic Call Back.
CALLOG,
CMWI, Enter ACRJ for Anonymous Caller
CNAB, Rejection.
CNAMD,
Enter ADSI for Analog Display Services
CND, CNDB,
Interface.
COT, DDN,
DRCW, Enter AR for Automatic Recall.
DSCWID,
Enter CALLOG for Call Logging.
RND, SCA,
SCF, SCRJ, Enter CMWI for CLASS Message Waiting
SCWID Indicator.
Enter CNAB for Calling Name Delivery
Blocking.
Enter CNAMD for Calling Name Delivery.
Enter CND for Calling Number Delivery.
Enter CNDB for Calling Number Delivery

Blocking.
Enter COT for Customer Originated
Trace.
Enter DDN for Dialable Directory Number.
Enter DRCW for Distinctive Ringing Call
Waiting.
Enter DSCWID for Deluxe Spontaneous
Call Waiting Identification.
Enter RND for Redirecting Number and
Reason Delivery.
Enter SCA for Selective Call Acceptance.
Enter SCF for Selective Call Forwarding.
Enter SCRJ for Selective Call Rejection.
Enter SCWID for Spontaneous Call
Waiting Identification.
1-16 Data schema
RESFEAT (continued)
Field descriptions
VAR see subfields Variable data

This field consists of subfields DF, AMA,
STATUS, FDN, DTYPE, DEFTRMT,
DAMA, CONFPEGS, AVAILDLY,
UNAVAILDLY, CMDAVAILDLY, and
CMDUNAVAILDLY.
DF ACB, ACRJ, CLASS feature

ADSI, AR,
Enter the same value as field FEAT.
CALLOG,
CMWI,
CNAB,
CNAMD,
CND, CNDB,
COT, DDN,
DRCW,
DSCWID,
RND, SCA,
SCF, SCRJ,
SCWID
AMA AMA, Automatic message accounting

NOAMA
Enter AMA if an automatic message
accounting (AMA) record is generated for
the feature. The SUSP (subscriber usage
sensitive pricing) feature in table
AMAOPTS must be set ON for AMA
generation.
Enter NOAMA if no AMA record is
required.
STATUS ACT, Status

INACT,
Enter ACT (active) if the feature is active
UNIVA,
on the line. Otherwise, enter INACT
UNIVI
(inactive).
The entries UNIVA and UNIVI indicate the
feature is activated or inactivated by a
universal user.
Enable the feature for the office in table
RESOFC.

Data schema 1-17
RESFEAT (continued)
Field descriptions
FDN 1 to 30 digits SCF DN

If the entry in subfield DF is SCF, datafill
this refinement. Enter the forward-to DN
for SCF calls when SCF is active.
DTYPE PROPRITY, DSCWID type

ADSITIME,
If the entry in subfield DF is DSCWID,
ADSICID,
datafill this refinement. The DSCWID type
NODATA,
is the name defined in table DSCWDTYP.
NOCIDCW,
COMPLETE, Enter the name of the DSCWID type
DEF, or assigned to the line as follows:
others as
The PROPRITY tuple indicates the
defined
proprietary DSCWID type.
The ADSITIME tuple indicates that
only time data is transmitted and only
standard CWT is available to
non-ADSI sets.
The ADSICID tuple indicates that both
CID and time data are transmitted,
based on the CID features present on
the line, and only standard CWT is
available to non-ADSI sets.
The NODATA tuple indicates that CID
and time data are not transmitted, and
both ADSI and non-ADSI sets have all
DSCWID options.
The NOCIDCW tuple indicates that
only time data is transmitted, and both
ADSI and non-ADSI sets have all
DSCWID options.
The COMPLETE tuple indicates both
CID call waiting (CIDCW) and time
data are transmitted, and both ADSI
and non-ADSI sets have all DSCWID
options.
Note: You cannot use the PROPRITY

value when adding DSCWID to a line.
1-18 Data schema
RESFEAT (continued)
Field descriptions
DEFTRMT RING, FWD, Default treatment

ANNC, or
DEF
datafill this refinement. Enter the default
treatment to be applied when no DSCWID
option is chosen. Enter RING to apply
ringing, ANNC to apply an announcement,
and FWD to forward the call to a valid
CFDA number. Enter DEF to apply the
same treatment datafilled in table
RESOFC.
DAMA NONE, DSCWID AMA

CONF, or
DEF
datafill this refinement. Enter the type of
AMA recording status for DSCWID lines.
Enter CONF to record on use of the
CONFERENCE option, NONE for no AMA
recording, and DEF to apply the same
AMA status datafilled in table RESOFC.
CONFPEGS 0 to 32767 Conference pegs

datafill this refinement. Enter the number
of successful DSCWID conference
attempts made when subfield DAMA is set
to CONF since the last aggregation
interval. This field cannot be changed by
the operating company. It should be reset
at the close of the aggregation interval or
when subfield DAMA is reset to NONE.

Data schema 1-19
RESFEAT (continued)
Field descriptions
AVAILDLY 0 to 32767 Available delivery

If the entry in subfield DF is CNAMD,
CND, DDN, or RND datafill this
refinement. This field holds the
unrecorded counts for voice deliveries
where information was available but not
recorded in a Bellcore AMA format record.
This count only increments when the
feature has AMA enabled in table
RESOFC and option SUSP is ON in table
AMAOPTS.
If the entry in subfield DF is CNAMD, this
field holds the number of times that both a
calling name and a calling number are
delivered.
If the entry in subfield DF is CND or DDN,
this field holds the number of times a
calling name, but not a calling number is
delivered.
If the entry in subfield DF is RND, this field
holds the number of times the redirecting
number is delivered.
The default is 0 (zero).
1-20 Data schema
RESFEAT (continued)
Field descriptions
UNAVAILDLY 0 to 32767 Unavailable delivery

If the entry in subfield DF is CNAMD,
CND, DDN, or RND datafill this
refinement. This field holds the
unrecorded counts for voice deliveries
where information was suppressed,
private, or otherwise unavailable for the
feature. These were not recorded in a
BELLCORE format. This count only
increments when the feature has AMA
enabled in table RESOFC and option
SUSP is ON in table AMAOPTS.
If the entry in subfield DF is CNAMD, this
field holds the number of times that neither
a calling name nor a calling number is
delivered.
If the entry in subfield DF is CND or DDN,
this field holds the number of times a
calling number, but no calling name is
delivered.
If the entry in subfield DF is RND, this field
holds the number of times that no
redirecting number is delivered.

Data schema 1-21
RESFEAT (continued)
Field descriptions
CMDAVAILDLY 0 to 32767 Circuit-mode data (CMD) available

delivery
For ISDN BRI, the Calling Number
Identification Service (CNIS) billing
feature includes the SERVORD option
Aggregate CND Recording (ACR). Option
ACR generates call type-specific AMA
records for CND or CNAMD, or both.
SERVORD option ARR (Aggregate RND
Recording) generates call type-specific
AMA records for the RND feature. If RND
is on the line, ARR is required.
If the entry in subfield DF is CNAMD or
CND, datafill this refinement. This field
holds the unrecorded counts for deliveries
recorded in a BELLCORE AMA format
record. This count only increments when
the feature has AMA enabled in table
AMAOPTS.
This field holds CMD counts for ISDN BRI
only. The AVAILDLY subfield holds all
voice and non-ISDN counts.
If subfield DF contains CNAMD, this field
indicates how often the switch delivered
both a calling name and a calling number.
If subfield DF contains CND, this field

indicates how often the switch delivered a
calling name but not a calling number (that
is, CNAMD-only deliveries).
If subfield DF contains RND, this field
indicates the number of times a
1-22 Data schema
RESFEAT (continued)
Field descriptions
CMDUNAVAILDLY 0 to 32767 Circuit-mode data (CMD) unavailable

delivery
For ISDN BRI, the CNIS billing feature
includes the SERVORD option ACR.
Option ACR generates call type-specific
AMA records for CND or CNAMD, or both.
If the entry in subfield DF is CNAMD or
CND, datafill this refinement. This field
holds the unrecorded counts for deliveries
recorded in a BELLCORE AMA format
record. This count only increments when
the feature has AMA enabled in table
AMAOPTS.
SERVORD option ARR generates call
type-specific AMA records for the RND
feature. If RND is on the line, ARR is
required.
This field holds CMD counts for ISDN BRI
only. The UNAVAILDLY subfield holds all
voice and non-ISDN counts.

Data schema 1-23
RESFEAT (continued)
Field descriptions
If subfield DF contains CNAMD, this field

indicates how often the switch did not
deliver a calling name or a calling number.
If subfield DF contains CND, this field
indicates how often the switch delivered a
calling number but no calling name (that
is, CND-only deliveries).
If subfield DF contains RND, this field
indicates the number of times that no
DND_ONLY DF Refinement {Y, N} Enter Y if SCA applies only when DND is

(DF=SCA) active.
Enter N when using standard SCA.
Do Not Disturb Only
If the entry in subfield DF is SCA, then
enter Y, as SCA applies only when DND is
active.
Enter N when using the standard SCA.
Datafill example
The following example shows sample datafill for table RESFEAT.
MAP display example for table RESFEAT
LINE KEY FEAT

VAR
________________________________________________________
HOST 00 0 11 08 1 SCRJ
SCRJ NOAMA INACT
HOST 00 1 03 15 0 DSCWID DSCWID NOAMA ACT
COMPLETE FWD CONF 5
HOST 01 1 14 22 0 CND CND NOAMA ACT 0000
HOST 00 1 08 05 0 SCA SCA NOAMA ACT Y
1-24 Data schema
RESFEAT (continued)
This section provides information on possible error messages when datafilling
table RESFEAT.
Error messages
For feature CND, table LTCINV or table RCCINV must be datafilled with a
CMR card in field OPTCARD for the host PM of the line. If this is not the case,
then the following warning is output:
***WARNING** CND ASSIGNED TO LINE WITH NO CMR BOARD

ACCESSIBLE.
If the option is added to a line whose host PM is not one of LTC, LGC or RCC,
then the following error message is displayed and the feature is not added to
the line:
CND NOT ALLOWED FOR LINES ON THIS PERIPHERAL TYPE
For feature DDN, table LTCINV or table RCCINV with a CMR card in the
OPTCARD field for the host peripheral module of the line. If this is not the
case then the following warning is output:
***WARNING** CND/DDN ASSIGNED TO LINE WITH NO CMR BOARD

ACCESSIBLE
If the feature is added to a line whose host peripheral module is not one of LTC,
LGC, or RCC types, then the following error message is displayed and the
feature is not added to the line:
CND/DDN NOT ALLOWED FOR LINES ON THIS PERIPHERAL TYPE
The following error message appears if an attempt is made to datafill this table
using the table editor:
Protected table, use SERVORD to change.

Data schema 1-25
RESFEAT (continued)
This error message has been added for the NA005 release in accordance with
feature AN1653 (Enforcement of SERVORD).
All additions, deletions and changes must be entered using the Service Order
System (SERVORD). For information, refer to the SERVORD Reference
Manual.
Table history
SN07 (DMS)
DND_ONLY field added SCA data feature to support A00002196.
NA011
Added option RND for feature AF7736, Redirecting Number and Reason
Delivery for ISDN Call Forwarding.
NA010
Added refinements CMDAVAILDLY and CMDUNAVAILDLY as subfields
of field VAR in accordance with feature AF7454, CNIS Billing without
Intra/Inter BBG Segregation.
NA005
Added error message information to Error messages" section in accordance
with feature AN1653, Enforcement of SERVORD.
NA004
The following changes were made to table RESFEAT:
The Deluxe Spontaneous Call Waiting Identification (DSCWID) feature
was added to the Functional description" section.
The following features were added as new line options assignable to RES
and IBN lines in field FEAT and subfield DF:
ACB
ACRJ
AR
CALLOG
CMWI
CNAB
CNDB
COT
1-26 Data schema
RESFEAT (end)
DSCWID
SCWID
Refinements DTYPE, DEFTRMT, DAMA, CONFPEGS were added as
subfields of field VAR.
Subfield FDN of field VAR was increased to 30 digits.
NA002
The Analog Display Services Interface (ADSI) feature was added to the
Functional description" section. ADSI was added as a new line option
assignable to RES and IBN lines in field FEAT and subfield DF.
BCS36
A paragraph was added to the Functional description" section that data units
can now be datafilled in table RESFEAT. Clarification of fields AVAILDLY
and UNAVAILDLY was added.

RESGROUP
Table name
Resource Group Table
Table RESGROUP contains data that is common to all resource members
within a group. One entry is datafilled in table RESGROUP for each resource
group defined. Currently, the data consists of modem pool and maintenance
modem pool formats.
For related information, refer to table RESINV.

Table CLLI must be datafilled before table RESGROUP.
Table size
0 to 2048 tuples
Datafill
The following table lists datafill for table RESGROUP.
Subfield or
GRPKEY see subfield Resource group key

This field consists of subfield CLLI.

(up to 16
Enter a common language location identifier
characters)
(CLLI) to serve as the key to table
RESGROUP.
GDATA see subfields Resource group data

This field consists of subfields GRPTYP,
TMODE, and SPEED.
GRPTYP MMP or MP Resource group type

Enter MMP for maintenance modem pool or
MP for modem pool.
297-8021-351 Standard 05.02 May 2001

RESGROUP (continued)
Subfield or
TMODE FULL or Transmission mode

HALF
Enter FULL if the modems are full duplex or
HALF if they are half duplex.
SPEED 300, 1200, Modem speed

2400 4800,
Enter the baud rate of the modem in bits per
9600, or
second.
19200
OVFLDATA see subfields Overflow data

This field consists of subfields OVFL and
OVFLCLLI.
OVFL Y or N Group overflow

Enter Y (yes) if an overflow CLLI is required
and datafill subfield OVFLCLLI. Otherwise,
enter N (no) and leave subfield OVFLCLLI
blank.
OVFLCLLI alphanumeric Group overflow CLLI

(up to 16
Enter the CLLI of another resource group to
characters)
which calls overflow if all members in the
current group are busy.
MTCDATA see subfield Maintenance data

This field consists of subfield MTC.
MTC Y or N Maintenance
Enter Y if modem pool maintenance data is
required and datafill refinements MTCCLLI
and MTCMODE. Otherwise, enter N and
leave refinements MTCCLLI and MTCMODE
blank.
RESGROUP (end)
Subfield or
MTCCLLI alphanumeric Maintenance CLLI

(up to 16
Enter the CLLI of the maintenance modem
characters)
pool. This is used as a default for performing
bit error rate tests (BERT).
MTCMODE IN, OUT, or Maintenance test mode

BOTH
This field specifies the direction in which the
modem pool is tested. Enter IN if the modem
pool processes inbound calls. Enter OUT if
the modem pool processes outbound calls.
Enter BOTH if the modem pool handles calls
in both directions.
Datafill example
The following example shows sample datafill for table RESGROUP.
MAP display example for table RESGROUP
GRPKEY GDATA OVFLDATA

MTCDATA
_______________________________________________________________________
OMP1200A MP FULL 1200 Y OMP1200B Y ATTKDKA1

OUT
OMP1200B MP FULL 1200 N Y ATTKDKA1
BOTH
ATTKDKA1 MMP FULL 1200 N Y ATTKDKA1
BOTH
Table history
BCS36
Subfield CLLI was added.
297-8021-351 Standard 05.02 May 2001

RESINV
Table name
Resource Inventory Table
Table RESINV contains the line equipment numbers (LEN) of all the
resources defined in the office, and specifies the type of resources. Any
resource members added to table RESMEM must first be defined as valid
resources in table RESINV.
Table RESMEM is capable of handling many input data formats, but at present
only two exist: one for modem pool modems and one for modem pool data
units.
The network resource selector (NRS) system provides modem pooling for
data unit (DU) data transmission and the capability to select a variety of
modems with different speeds. Modem pools are stored, processed, and
manipulated by the NRS system.
Datapath modem pooling maintenance enables integrated testing of modem

pools to be performed by the operating company, with the bit error rate test
(BERT) commands in the LTPDATA level of the MAP (maintenance and
administrative position).
There are three related resource tables:

table RESINV stores inventory data on all office resources
table RESGROUP stores group data
table RESMEM stores member data

The following tables must be datafilled before table RESINV.
LNINV
KSETINV
Table size
0 to 1000 tuples
RESINV (continued)
Datafill
The following table lists datafill for table RESINV.
Subfield or
RESKEY see subfields Resource key

This field consists of subfield LEN. Currently,
only modems and data units are valid.

telephone line.
SLOT, and CIRCUIT.
RESDATA see subfields Resource data

This field consists of subfields RESSEL and
DETSEL.
RESSEL MPDU or Resource selector

MPMD
This field specifies the type of resource to
which the LEN belongs. Enter MPDU if the
resource is a modem pool data unit. Enter
MPMD if the resource is a modem pool
modem.
297-8021-351 Standard 05.02 May 2001

RESINV (continued)
Subfield or
DETSEL Y or N Detail selector

The entry in this field indicates whether the
resource line has been associated with its
mating resource pair and assigned in table
RESMEM as a member of a resource group.
A value of Y (yes) indicates that the line has
been mated and assigned in a resource
group. This field and fields LEN, GRPCLLI,
and SEQNO are updated by table control
when the resource line is datafilled in table
RESMEM.
A value of N (no) indicates that the resource
line has not been mated yet. Always enter N
in this field if adding a new resource line, and
leave the remaining fields LEN, GRPCLLI,
and SEQNO blank.

telephone line.
Field LEN is the other half of a DU-modem
pair and consists of subfields SITE, FRAME,
UNIT, DRAWER or LSG, SHELF, SLOT, and
CIRCUIT.
RESINV (continued)
Subfield or
GRPCLLI alphanumeric Group CLLI

(up to 16
This field is not datafilled and is shown for
characters)
information only. This field specifies the
common language location identifier (CLLI) of
the resource group to which the member
belongs.
SEQNO 0 to 255 Resource member sequence

This field is not datafilled and is shown for
information only. This field indicates the
position of the member within the group.
Datafill example
The following example shows sample datafill for table RESINV.
The example below contains datafill for a modem pool data unit with LEN 00
0 15 01 and a modem pool modem with LEN 00 0 03 01.
MAP display example for table RESINV
RESKEY RESDATA
_______________________________________________________________________
HOST 00 0 15 01 MPDU N
HOST 00 0 03 01 MPMD N
The example below shows table RESINV after table RESMEM has been
datafilled. Although the headings do not appear, the datafill for fields LEN,
GRPCLLI, and SEQNO are shown since table control updates these fields
after table RESMEM is datafilled. The group CLLI is BELL212A1200 and
the resource member number is 0.
297-8021-351 Standard 05.02 May 2001

RESINV (end)
MAP display example for table RESINV
RESKEY RESDATA
_______________________________________________________________________
HOST 00 0 15 01 MPDU Y HOST 00 0 03 01 BELL212A1200 0

HOST 00 0 03 01 MPMD Y HOST 00 0 15 01 BELL212A1200 0
RESMEM
Table name
Resource Member Table
Table RESMEM contains data for each of the resource members in a resource
group. Table RESMEM is capable of handling many input data formats, but
only a modem pool format currently exists.
For related information, refer to table RESINV.

The following tables must be datafilled before table RESMEM:
CLLI
DPROFILE
RESINV
RESGROUP
Table size
0 to 256 tuples
Datafill
The following table lists datafill for table RESMEM.
Subfield or
MEMKEY see subfields Resource member key

This field consists of subfields CLLI and
SEQNO.
CLLI alphanumeric Resource group CLLI

(up to 16
Enter the common language location
characters)
identifier (CLLI) of the resource group to
which the member belongs.
SEQNO 0 to 255 Resource member sequence number

Enter the position of the member within the
group.
297-8021-351 Standard 05.02 May 2001

RESMEM (end)
Subfield or
MDATA see subfield Resource member data

This field consists of subfield GRPTYP
GRPTYP MP or MMP Group type

This field indicates the type of resource.
Enter MP for modem pool or MMP for
maintenance modem pool.

telephone line.
SLOT, and CIRCUIT.
Datafill example
The following example shows sample datafill for table RESMEM.
MAP display example for table RESMEM
MEMKEY MDATA
_______________________________________________________________________
OMP2400A 0 MP HOST 00 0 01 06 HOST 00 0 01 07

OMP2400B 1 MP HOST 00 0 05 06 HOST 00 0 05 07
RESOFC
Table name
Residential Line CLASS Office Data
Table RESOFC contains data for Custom Local Area Signaling Services
(CLASS) features. CLASS features are public network features targeted for
the residential market.
Note: As of NA008, this table applies to office-wide control of existing

features for Integrated Services Digital Network (ISDN) subscribers.
For each CLASS feature, table RESOFC controls office-wide feature

activation. When you assign and disable a feature, CLASS lines cannot use
that feature. Table RESOFC also controls the attributes associated with each
feature.
The CLASS features that are supported follow:

Automatic Call Back (ACB)
Anonymous Call Rejection (ACRJ)
800 Calling Number Identification (CID)
Note: The CIDSSUP and CIDSDLV features for ISDN BRI lines are
controlled through the CNDB tuple. A value of UNIVER enables UA
for these ISDN features.

Calling Number Delivery Dialable Number (DDN)
800 Dialed Number Identification Delivery (DNID)
Distinctive Ringing/Call Waiting (DRCW)
297-8021-351 Standard 05.02 May 2001

RESOFC (continued)
Deluxe Spontaneous Call Waiting Identification (DSCWID

Note: Changing from pre-NA011 to NA011 or higher adds the CLASS

option RND to table RESOFC. This option is added as RND N
SUBSCR RND $.

Note: The external symbols for options CID and DNID are NTS_CID and
NTS_DNID. Use these external symbols when accessing line options in
SERVORD and entering data in table RESOFC.
For more information on these features, refer to the Feature Description

Reference Manual.
The system adds a default tuple to this table during initialization of the
software package implementing the CLASS feature. Operating companies can
modify tuples only, not add or delete tuples.

The following tables must be datafilled before table RESOFC:
CLLI
ANNS
ANNMEMS
DRAMTRK
The system automatically adds the call logging entry in table RESOFC.
To have repeat announcements for AR two-level activation, you must set fields
BADIGITS and TIMEOUT to a nonzero value.
Table size
The system statically allocates memory for this table. You cannot extend this
table.
RESOFC (continued)
The expanded size of the tuple accommodates a maximum of four new

announcement identifiers. The expanded internal data storage table
accommodates nine more protected data words.
Datafill
The following table lists datafill for table RESOFC.
KEY see Key

subfield
This field consists of subfield FEATNAME.
FEATNAME see below Class feature name

This field is the key to the table. Enter a CLASS
feature as described below:
ACB ACB (Automatic Call Back) (See note.)
ACRJ ACRJ (Anonymous Call Rejection). This entry controls

the ACRJ feature for ISDN BRI subscribers. (See
note.)
ADSI ADSI (Analog Display Services Interface)
AR AR (Automatic Recall) (See note.)
CALLOG CALLOG (Call Logging)
CID CID (800 Calling Number Identification)
CMWI CMWI (CLASS Message Waiting Indicator)
CNAB CNAB (Calling Name Delivery Blocking)
CNAMD CNAMD (Calling Name Delivery). This tuple controls

the CNAMD feature for ISDN BRI subscribers.
CND CND (Calling Number Delivery) (See note.)
CNDB CNDB (Calling Number Delivery Blocking). This tuple

controls the CIDSSUP and CIDSDLV features for
ISDN BRI subscribers. (See note.)
COT COT (Customer Originated Trace)
Note: This tuple controls feature access for ISDN BRI lines.
297-8021-351 Standard 05.02 May 2001

RESOFC (continued)
DDN DDN (Calling Number Delivery Dialable Number)
DNID DNID (800 Dialed Number Identification Delivery)
DRCW DRCW (Distinctive Ringing/Call Waiting)
DSCWID DSCWID (Deluxe Spontaneous Call Waiting

Identification)
NTS_CID (800 Calling Number Identification)

NTS_DNID (800 Dialed Number Identification
Delivery)
The external symbols for options CID and DNID are
NTS_CID and NTS_DNID. Use these symbols when
accessing the line options in SERVORD and entering
data in table RESOFC.
RND RND (Redirecting Number and Reason Delivery).

(See note.)
SCA SCA (Selective Call Acceptance). (See note.)
SCF SCF (Selective Call Forwarding). (See note.)
SCRJ SCRJ (Selective Call Rejection). (See note.)
SCWID SCWID (Spontaneous Call Waiting Identification)
ENABLED Y or N Enabled
Enter Y (yes) to specify that the feature is enabled
within the office. Enter N (no) to indicate the feature
deactivation.
Note: The DSCWID and the BRI in RES features are

available only when you set field ENABLED to Y.
FEATDATA see Feature data

subfield
This field consists of subfield FEATNAME.
FEATNAME see below Class feature name

Enter a CLASS feature and provide datafill for its
subfields as described below:
RESOFC (continued)
ACB Enter ACB and provide datafill for subfields.
ACRJ Enter ACRJ and provide datafill for subfields.
ADSI Enter ADSI and do not provide datafill for subfields.

Field ACCESS is set to SUBSCR.
AR Enter AR and provide datafill for subfields.
CALLOG Enter CALLOG and provide datafill for subfields.
CMWI Enter CMWI and provide datafill for subfields.
CNAB Enter CNAB and provide datafill for subfields.
CNAMD Enter CNAMD. No subfields require datafill.
CND Enter CND and provide datafill for subfields.
CNDB Enter CNDB and provide datafill for subfields.
COT Enter COT and provide datafill for subfields.
DDN Enter DDN. No subfields require datafill.
DRCW Enter DRCW and provide datafill for subfields.
DSCWID Enter DSCWID and provide datafill for subfields.
NTS_CID Enter NTS_CID. No subfields require datafill.
NTS_DNID Enter NTS_DNID. No subfields require datafill.
RND Enter RND and provide datafill for subfield ACCESS.
SCA Enter SCA and provide datafill for subfields.
SCF Enter SCF and provide datafill for subfields.
SCRJ Enter SCRJ and provide datafill for subfields.
297-8021-351 Standard 05.02 May 2001

RESOFC (continued)
SCWID Enter SCWID and provide datafill for subfields.
ACCESS SUBSCR Feature access

or UNIVER
This field determines who can access the feature.
Enter SUBSCR for subscribers only. Enter UNIVER
for all residential (RES) line access to the feature.
Enter SUBSCR only for RND.
Note 1: When you change the SUBSCR and

UNIVER field of a tuple, you change all of data field
ACCESS. Reenter all of the data for these features.
Note 2: This entry controls Universal Access for COT
for IBN lines.
Note 3: This entry controls Universal Access for
ISDN BRI subscribers.
Note 4: The SCWID and DSCWID features are
available when you assign SUBSCR in field ACCESS.
Note 5: The CNAB feature is available when you
assign UNIVER in field ACCESS.
FEATNAME = ACB
If the entry in field FEATNAME is ACB, provide datafill for subfields T2, T4,
T5, T6, T10, TSCAN, N, RINGCYCL, RINGAPPL, TERMSCAN,
RESOFC (continued)
COINLINE, HUNTLINE, PBXLINE, and TCAP_QUERY_ENABLED as

described below. After adding the datafill, go to field FNALANN.
ACB T2 3 to 12 Time 2
If the entry in field FEATNAME is ACB, provide datafill
for this subfield. Enter the length of time (in minutes)
that the originating switch waits between stopping
recall ringing and sending out a message request to
reactivate the queue position.
The default is 5.
T4 0 to 15 Time 4 - Intraswitch guard time

for this subfield. Enter a positive value for T4 to enable
the intraswitch guard time. (For example, set T4 to six
seconds.) Intraswitch guard time is disabled if T4 is set
to zero.
The default is zero.
T5 2 to 10 Time 5
for this subfield. Enter the length of time (in seconds)
that the originating switch allows for a response from
the terminating switch.
The default is 3.
T6 5 to 35 Time 6
that the originating switch scans or waits for a free
notification from the terminating switch.
The default is 30.
T10 60 to 180 Time 10

for the queue sanity timer for the originating and
terminating switches.
The default is 180.
297-8021-351 Standard 05.02 May 2001

RESOFC (continued)
TSCAN 30 to 120 Time scanning

between busy/idle queries when the originator
performs originating scanning.
Note: T11 in the terminating node is set equal to

subfield TSCAN plus 5 s.
The default is 120.
N 0 to 10 N
for this subfield. Enter the tolerance timer for aligning
values of T6 timer and queue entry timer (T7) at the
terminating switch. If the entry in subfield T6 is greater
than the entry in subfield N when the originator
receives a service timeout message from the
terminating switch, the system sends a message to
reset T7 to use what is left of T6.
The default is 5.
RINGCYCL 2 to 7 Ring cycle

for this subfield. Enter the number of 6-s ring cycles
that recall ringing is given.
Note: T8 is set equal to field RINGCYCL X 6 plus 5 s.

The default is 5.
RINGAPPL 1 to 12 Ring apply

for this subfield. Enter the number of times
unanswered recall ringing is given to a calling party.
The default is 2.
RESOFC (continued)
TERMSCAN Y or N Terminating scan

for this subfield. Enter Y if the originating switch
requests terminating scan. Otherwise, enter N if the
switch never requests a terminating scan.
The default is Y.
COINLINE ACCEPT Coin line

or DENY
for this subfield. Enter whether the originating switch
accepts or denies an ACB for a return line type of coin
line and directory number (DN) match or no match.
The default is DENY.
HUNTLINE ACCEPT Hunt line

or DENY
accepts or denies an ACB for a return line type of hunt
line and DN match or no match.
PBXLINE ACCEPT Private branch exchange line

or DENY
accepts or denies an ACB for a return line type of
private branch exchange (PBX) line and DN match or
no match.
TCAP_QUERY Y or N TCAP query enabled

_ENABLED
If the entry in field FEATNAME is ACB, AR, DRCW,
SCA, SCF, or SCRJ, provide datafill for this subfield.
Enter Y to enable TCAP query. Enter N to disable
TCAP query.
The default is Y.
If you change the value of the
TCAP_QUERY_ENABLED field from Y to N and do
not activate the SOC option RES00073, the system
displays the following message: Change will not be
active until SOC option RES00073 is turned ON.
297-8021-351 Standard 05.02 May 2001

RESOFC (continued)
FEATNAME = ACRJ
If the entry in field FEATNAME is ACRJ, provide datafill for subfield
ACRJ_ANSWRSUP as described below. After adding the datafill, then go to
field FNALANN.
ACRJ ACRJ_ Y or N ACRJ answer supervision

ANSWRSUP
If the entry in field FEATNAME is ACRJ,
provide datafill for this subfield. Enter Y when
you need answer supervision. Otherwise,
enter N.
FEATNAME = AR
If the entry in field FEATNAME is AR, provide datafill for subfields
ACTLEVEL, T2, T4, T5, T6, T10, TSCAN, RINGCYCL, RINGAPPL,
TERMSCAN, COINLINE, HUNTLINE, PBXLINE,
TCAP_QUERY_ENABLED, and ACTLEVEL as described below. After
adding the datafill, go to field FNALANN.
AR ACTLEVEL ONELEVEL Activation level

or
If the entry in field FEATNAME is AR, provide datafill
TWOLEVEL
for this subfield. Enter ONELEVEL if the subscriber
can access the feature by dialing the feature access
code. Enter TWOLEVEL if the system prompts the
subscriber to dial 1 after dialing the feature access
code.
The default is ONELEVEL
T2 3 to 12 Time 2
that the originating switch waits between stopping
recall ringing and sending out a message to request
to reactivate the queue position.
The default is 3.
RESOFC (continued)
T4 0 to 15 Time 4 - Intraswitch guard time

for this subfield. Enter a positive value for T4 to enable
the intraswitch guard time. (For example, set T4 to six
seconds.) Intraswitch guard time is disabled if T4 is
set to zero.
The default is zero.
T5 2 to 10 Time 5
that the originating switch allows for a response from
the terminating switch.
The default is 3.
T6 5 to 35 Time 6
that the originating switch scans or wait for a free
notification from the terminating switch.
The default is 30.
T10 60 to 180 Time 10

for the queue sanity timer for the originating and
terminating switches.
The default is 180.
TSCAN 30 to 120 Time scanning

between busy/idle queries when the originator
performs originating scanning.
Note: T11 in the terminating node is set with a value

equal to field TSCAN + seconds.
The default is 120.
297-8021-351 Standard 05.02 May 2001

RESOFC (continued)
N 0 to 10 N
for this subfield. Enter the tolerance timer for aligning
values of T6 timer and queue entry timer (T7) at the
terminating switch. If the entry in subfield T6 is greater
than the entry in subfield N when the originator
receives a service timeout message from the
terminating switch, a message is sent to reset T7 to
use what is left of T6.
The default is 5.
RINGCYCL 2 to 7 Ring cycle

for this subfield. Enter the number of 6-s ring cycles
that recall ringing is given.
Note: T8 is set equal to the entry in RINGCYCL

multiplied by 6 + seconds.
The default is 5.
RINGAPPL 1 to 12 Ring apply

for this subfield. Enter the number of times
unanswered recall ringing is given to a calling party.
The default is 5.
TERMSCAN Y or N Terminating scan

for this subfield. Enter Y if the originating switch
requests a terminating scan. Enter N if a terminating
scan is never requested.
The default is 2.
COINLINE ACCEPT or Coin line

DENY
accepts or denies an AR for a return line type of coin
line and directory number (DN) match or no match.
RESOFC (continued)
HUNTLINE ACCEPT or Hunt line

DENY
accepts or denies an AR for a return line type of hunt
line and DN match or no match.
PBXLINE ACCEPT or Private branch exchange line

DENY
accepts or denies an AR for a return line type of
private branch exchange (PBX) line and DN match or
no match.

_ENABLED
Enter Y to enable TCAP query. Enter N to disable
TCAP query.
The default is Y.
If the value of the TCAP_QUERY_ENABLED field is
changed from Y to N, and the SOC option RES00073
is not on, then the following message will be
displayed: Change will not be active until SOC option
RES00073 is turned ON.
ACTLEVEL ONELEVEL Activation level

or
TWOLEVEL
for this subfield. Enter ONELEVEL if the subscriber
accesses the feature by dialing the feature access
code. Enter TWOLEVEL if the subscriber is prompted
to dial a 1 after dialing the feature access code and
provide datafill for subfields BADIGITS and
TIMEOUT.
297-8021-351 Standard 05.02 May 2001

RESOFC (continued)
BADIGITS 0 to 7 Bad digits

If the entry in field FEATNAME is AR and the entry in
subfield ACTLEVEL is TWOLEVEL, provide datafill
for this subfield. This field is used to determine the
number of times that a subscriber may enter the
wrong input during two-level activation. If this number
is exceeded then the call is routed to NACK treatment.
TIMEOUT 0 to 7 Time out

If the entry in field FEATNAME is AR and the entry in
subfield ACTLEVEL is TWOLEVEL, provide datafill
for this subfield. This field determines the number of
times that a subscriber may allow two-level digit
collection to time out. If this number is exceeded then
the call is routed to NACK (nil acknowledgment)
treatment.
FEATNAME = CALLOG
If the entry in field FEATNAME is CALLOG, provide datafill for subfields
CALLOG_TIMEOUT, and CALLOG_PRIMARY_DATA as described below.
After adding the datafill, then go to field FNALANN.
CALLOG CALLOG_ 2 to 30 Call logging timeout

TIMEOUT
If the entry in field FEATNAME is CALLOG, provide
datafill for this subfield. The values 2 to 30 indicate
how long the call log feature waits for input before
terminating the call log session. The value is in
minutes.
CALLOG_ NAME or Call logging primary data

PRIMARY_ NUMBER
If the entry in field FEATNAME is CALLOG, provide
DATA
datafill for this subfield. This field indicates if the name
or number is displayed in the first field of the call
logging item on the SESAME terminal. If NAME is
entered, the name is displayed in the first field of a call
log item at the SESAME set. Likewise, if NUMBER is
entered, the number is displayed in the first field of the
call log item at the SESAME set.
RESOFC (continued)
FEATNAME = CMWI
If the entry in field FEATNAME is CMWI, provide datafill for subfields
MSGTYPE and RETRSMIT as described below. After adding the datafill,
then go to field FNALANN.
CMWI MSGTYPE SINGLE or Message type

MULTIPLE
If the entry in field FEATNAME is CMWI, provide datafill for
this subfield. Enter either SINGLE or MULTIPLE
depending on how the CMWI subscriber in the office
receives message waiting information.
RETRSMIT 0 to 14 Retransmit
If the entry in field FEATNAME is CMWI, provide datafill for
this refinement. Enter the maximum number of attempts
that are allowed for transmission of the message waiting
information to the subscriber's set.
After reaching the maximum, the CMWI message is
discarded until the next lamp audit process executes and
verifies that the lamp should be turned on. A CMWI
message is then sent to the set by the lamp audit process.
FEATNAME = CNAB
If the entry in field FEATNAME is CNAB, provide datafill for subfields
ANNCS, CNABANNC, and ANNCLLI as described below. After adding the
datafill, then go to field FNALANN.
CNAB ANNCS alphanumeric Announcement

(1 to 16
If the entry in field FEATNAME is CNAB, provide
characters) or
datafill for this subfield. This field is datafilled with a
$
$ (dollar sign) if special dial tone is used for
confirmation of successful CNAB activation.
297-8021-351 Standard 05.02 May 2001

RESOFC (continued)
CNABANNC CNABCONF Calling name delivery blocking announcement

datafill for this subfield. Enter the CNAB
announcement CNABCONF.
ANNCLLI alphanumeric Announcement common language location

(1 to 16 identifier
characters)
datafill for this subfield. Enter the announcement
common language location identifier (CLLI) name.
FEATNAME = CND
If the entry in field FEATNAME is CND, provide datafill for subfield
CND_MSGTYPE as described below. After adding the datafill, then go to field
FNALANN.
CND CND_ SINGLE or CND message type

MSGTYPE MULTIPLE
If the entry in field FEATNAME is CND, provide datafill
for this subfield. Enter whether the data message
format sent to the CPE (customer premises
equipment) is single or multiple.
RESOFC (continued)
FEATNAME = CNDB
If the entry in field FEATNAME is CNDB, provide datafill for subfields
ANNCS, CNDBANNC, and ANNCLLI as described below. After adding the
datafill, then go to field FNALANN.
CNDB ANNCS see subfields Announcement

If the entry in field FEATNAME is CNDB, provide datafill
for this subfield. This field consists of subfields
CNDBANNC and ANNCLLI.
CNDBANNC CNDBCONF CNDB announcement

for this subfield. Enter CNDBCONF for CNDB
confirmation.
ANNCLLI alphanumeric Announcement common language location identifier

(1 to 16
characters)
for this subfield. Enter the announcement CLLI
datafilled in tables CLLI, ANNS, ANNMEMS, and
DRAMTRK for CNDB confirmation.
297-8021-351 Standard 05.02 May 2001

RESOFC (continued)
FEATNAME = COT
If the entry in field FEATNAME is COT, provide datafill for subfields
ACTLEVEL, ANNCS, COTANNID, and COTCLLI as described below. After
adding the datafill, then go to field FNALANN.
COT ACTLEVEL ONELEVEL Activation level

or
If the entry in field FEATNAME is COT, provide datafill
TWOLEVEL
for this subfield. Enter ONELEVEL to allow the
subscriber to access the feature by dialing the feature
access code and provide datafill for subfields
SECLANG, SANNCS, COTANNID, and COTCLLI.
Enter TWOLEVEL if the subscriber is prompted to dial
a 1 after dialing the feature access code to enable the
COT feature and provide datafill for subfields
EXPIRIES, BADIGITS, COTPRMT1, COTPRMTN,
and SECLANG.
ANNCS alphanumeric Announcement

(1 to 16
characters)
for this subfield. Enter up to two announcement
common language location identifiers (CLLI). If less
than two CLLIs are required, end the list with a $ (dollar
sign).
COTANNID COTCONF or Customer originated trace announcement identifier

COTFAIL
for this subfield. Enter COTCONF for a successful
trace. Otherwise, enter COTFAIL for a partial trace.
If COTCONF is not entered, the hard coded feature
confirmation tone (2 beeps) is given for a successful
COT trace. Similarly, if COTFAIL is not entered, then
the feature recorder tone (fast busy tone) for 5 s is
given.
COTCLLI alphanumeric Customer originated trace tone CLLI

(1 to 16
characters)
for this subfield. Enter the announcement CLLI for the
COTCONF and COTFAIL.
Note: The announcement for table CLLI must be

previously datafilled in tables CLLI, ANNS,
ANNMEMS, and DRAMTRK.
RESOFC (continued)
ACTLEVEL = ONELEVEL
If the entry in field FEATNAME is COT and the entry in subfield ACTLEVEL
is ONELEVEL, provide datafill for subfields SECLANG, SANNCS,
COTANNID, and COTCLLI as described below.
ONELEVEL SECLANG Y or N Second language

The field appears on the switch as
SECOND_LANGUAGE. If the entry in field
FEATNAME is COT, and the entry in subfield
ACTLEVEL is ONELEVEL, provide datafill for this
subfield. Enter Y if the secondary language
announcement is available for the COT feature
and provide datafill for subfield SANNCS.
Otherwise, enter N (no) and provide datafill for
subfield COTANNID.
SANNCS alphanumeric Announcement common language location

(1 to 16 identifier
characters)
If the entry in field FEATNAME is COT, the entry
in subfield ACTLEVEL is ONELEVEL, and the
entry in subfield SECLANG is Y, provide datafill
CLLIs. If less than two CLLIs are required, end the
list with a $ (dollar sign).
297-8021-351 Standard 05.02 May 2001

RESOFC (continued)
COTANNID SCOTCONF Customer originated trace announcement

or SCOTFAIL identification
If the entry in field FEATNAME is COT and the
entry in subfield ACTLEVEL is ONELEVEL,
provide datafill for this subfield. Enter SCOTCONF
for a successful trace. Otherwise, enter
SCOTFAIL for a partial trace.
If SCOTCONF is not entered, then the hard coded
feature confirmation tone (2 beeps) is given for a
successful COT trace. Similarly, if SCOTFAIL is
not entered, then the feature recorder tone (fast
busy tone) is given for5 s.
COTCLLI alphanumeric Customer originated trace CLLI

(1 to 16
characters)
FEATNAME is COT, and the entry in subfield
ACTLEVEL is ONELEVEL, provide datafill for this
subfield. Enter the announcement CLLI for the
COTCONF and COTFAIL.
Note: The announcement for table CLLI must be

previously datafilled in table CLLI, ANNS,
RESOFC (continued)
ACTLEVEL = TWOLEVEL
If the entry in field FEATNAME is COT and the entry in subfield ACTLEVEL
is TWOLEVEL, provide datafill for subfields EXPIRIES, BADIGITS,
COTPRMT1, COTPRMTN, and SECLANG as described below.
TWOLEVEL EXPIRIES 0 to 5 Expiries

entry in subfield ACTLEVEL is TWOLEVEL,
provide datafill for this subfield. Enter the number
of times the two level digit collection is allowed to
time-out. If this number is exceeded, the call is
routed to negative acknowledge (NACK)
treatment.
BADIGITS 0 to 5 Bad digits

provide datafill for this subfield. Enter the number
of times two level activation wrong provide
datafill for is allowed. If this number is exceeded,
the call is routed to NACK treatment.
COTPRMT1 alphanumeric Customer originated trace for prompt 1

(1 to 16
characters)
provide datafill for this subfield. Enter the CLLI of
the first prompting announcement provided to the
user during a two level activation. This CLLI must
be previously datafilled in tables CLLI, ANNS,
and ANNMEMS.
COTPRMTN alphanumeric Customer originated trace for prompt n

(1 to 16
characters)
provide datafill for this subfield. Enter the CLLI of
the repeat prompting announcement provided to
the user during a two level activation. This CLLI
must be previously datafilled in tables CLLI,
ANNS, and ANNMEMS.
297-8021-351 Standard 05.02 May 2001

RESOFC (continued)
SECLANG Y or N Second language

FEATNAME is COT and the entry in subfield
ACTLEVEL is TWOLEVEL, provide datafill for
this subfield. Enter Y if the secondary language
announcement is available for the COT feature
and provide datafill for subfields SANNCS,
COTANNID, COTCLLI, SCOTPRMT1, and
SCOTPRMTN.
Otherwise, enter N and provide datafill for
subfields COTANNID and COTCLLI as
described below.
Note: The following five fields are for secondary

language announcement for successful trace
and unsuccessful trace.
They can be datafilled as follows in accordance
with the COT announcements value (field
SANNCS):
For 0 (zero) COT announcements, which is
for the secondary language, both entries of a
vector are empty.
For 1 COT announcement, only one vector
entry is datafilled. It is qualified with
SCOTCONF for successful trace
announcement. Otherwise, it is qualified with
SCOTFAIL for unsuccessful trace
announcement.
For 2 COT announcements, both vector
entries are datafilled. They are qualified with
SCOTCONF for successful trace
announcement and with SCOTFAIL for
unsuccessful trace announcement.
RESOFC (continued)
SANNCS alphanumeric Announcement common language location

(1 to 16 identifiers
characters)
in subfield ACTLEVEL is TWOLEVEL, and the
entry in subfield SECLANG is Y, provide datafill
CLLIs. If less than two CLLIs are required, end
the list with a $ (dollar sign).
COTANNID SCOTCONF Customer originated trace announcement

or SCOTFAIL identification
provide datafill for this subfield. Enter
SCOTCONF for a successful trace. Otherwise,
enter SCOTFAIL for a partial trace.
If SCOTCONF is not entered, then the hard
coded feature confirmation tone (2 beeps) is
given for a successful COT trace. Similarly, if
SCOTFAIL is not entered, then the feature
recorder tone (fast busy tone) is given for5 s.
COTCLLI alphanumeric Customer originated trace CLLI

(1 to 16
characters)
provide datafill for this subfield. Enter the
announcement CLLI for the SCOTCONF and
SCOTFAIL.
Note: The announcement for table CLLI must

be previously datafilled in table CLLI, ANNS,
297-8021-351 Standard 05.02 May 2001

RESOFC (continued)
SCOTPRMT1 alphanumeric Second language COT prompt for feature 1

(1 to 16
characters)
entry in subfield ACTLEVEL is TWOLEVEL, and
the entry in subfield SECLANG is Y, provide
datafill for this subfield.
Enter a secondary language announcement for
initial prompt for two level activation of COT
feature l.
SCOTPRMTN alphanumeric Second language customer originate trace

(1 to 16 prompt for Nth level
characters)
entry in subfield ACTLEVEL is TWOLEVEL, and
the entry in subfield SECLANG is Y, provide
datafill for this subfield.
Enter a secondary language announcement for
Nth level prompt for two level activation of COT
feature.
RESOFC (continued)
FEATNAME = DRCW
If the entry in field FEATNAME is DRCW, provide datafill for subfield
MAXSIZE and TCAP_QUERY_ENABLED as described below. After adding
the datafill, then go to field FNALANN.
MAXSIZE 0 to 8191 Maximum size

If the entry in field FEATNAME is DRCW,
SCA, SCF, or SCRJ, provide datafill for this
subfield. Enter the maximum size of the
selective call list for the office. The
recommended size is 31. The lesser of this
field and parameter
SLE_ITEMS_IN_SEGMENT in table
OFCENG controls the maximum size of the
list.

_ENABLED
If the entry in field FEATNAME is ACB, AR,
DRCW, SCA, SCF, or SCRJ, provide datafill
for this subfield. Enter Y to enable TCAP
query. Enter N to disable TCAP query.
The default is Y.
If you change the value of the
TCAP_QUERY_ENABLED field from Y to N,
and do not activate the SOC option
RES00073, the system displays the following
message: Change will not be active until
SOC option RES00073 is turned ON.
FEATNAME = DSCWID
If the entry in field FEATNAME is DSCWID, provide datafill for subfields
DTYPE, DEFTRMT, AMA, BUSYANNC, BUSYSUPV, DFLTANNC,
DFLTSUPV, HOLDANNC, HOLDSUPV, REMINDER, TFLASH,
TDEFAULT, THOLD, SYNC_CPE, DELETE_CWT, and CFDCHECK, then
go to field FNALANN.
Note 1: Field ENABLED must be datafilled Y to allow delivery of calling

party identification during call waiting for DSCWID subscribers.
297-8021-351 Standard 05.02 May 2001

RESOFC (continued)
Note 2: Subfields WAITANNC, REALERT, and DATETIME are no longer

active.
DSCWID WAITANNC alphanumeric Wait announcement

(-NA003) (1 to 16
If the entry in field FEATNAME is DSCWID,
characters)
announcement CLLI. This is the announcement
received by the waiting party when the WAIT
option is chosen by the DSCWID subscriber.
REALERT Y or N Realert
(-NA003)
provide datafill for this subfield. Enter Y when
you need a realert. Otherwise, enter N.
The default for this field is Y.
DATETIME Y or N Date and time

(NA002-003)
provide datafill for this subfield. Enter Y or N. Y
allows the switch to send date and time
information to the DSCWID subscriber CPE
along with the calling party identification
information.
The default for this field is Y.
RESOFC (continued)
DTYPE PROPRITY, DSCWID type

(NA004-) ADSITIME,
ADSICID,
provide datafill for this subfield. The possible
NODATA,
entries are PROPRITY, ADSITIME, ADSICID,
NOCIDCW,
NODATA, NOCIDCW, and COMPLETE, plus
COMPLETE,
up to 14 other tuples that can be defined by the
or others as
operating company.
defined
Enter the name of the DSCWID type assigned to
the line as follows:
The PROPRITY tuple indicates the
proprietary DSCWID type.
The ADSITIME tuple indicates that only
time data is transmitted and only standard
Call Waiting (CWT) is available to non-ADSI
sets.
The ADSICID tuple indicates that both CID
and time data are transmitted, based on the
CID features present on the line, and only
standard CWT is available to non-ADSI
sets.
The NODATA tuple indicates that CID and
time data are not transmitted, and both
ADSI and non-ADSI sets have all DSCWID
options.
The NOCIDCW tuple indicates that only
time data is transmitted, and both ADSI and
non-ADSI sets have all DSCWID options.
The COMPLETE tuple indicates both CID
call waiting (CIDCW) and time data are
transmitted, and both ADSI and non-ADSI
sets have all DSCWID options.
297-8021-351 Standard 05.02 May 2001

RESOFC (continued)
DEFTRMT RING, FWD, Default treatment.

(NA004-) ANNC
provide datafill for this subfield. Enter the default
treatment to be applied when no DSCWID
option is chosen. Enter RING for the calling
party to hear ringing, FWD to forward the calling
party to another number, or ANNC to apply an
announcement.
The default for this field is RING.
AMA NONE or CONF Automatic message accounting

(NA004-)
provide datafill for this subfield. Enter the type of
AMA recording status for use on the
CONFERENCE option. Enter CONF to allow
recording or NONE to disallow recording.
The default for this field is NONE.
BUSYANNC CLLI Busy announcement

(NA004-) announcement
name or
provide datafill for this subfield. Enter the CLLI
NILWAITANNC
name for the announcement that is applied to
the calling party when the BUSY option is
chosen. If no BUSYANNC CLLI is datafilled,
disconnect (DSCN) treatment is applied.
The default for this field, NILWAITANNC,
indicates that no announcement has been
defined.
BUSYSUPV Y or N Busy supervision

(NA004-)
provide datafill for this subfield. Enter Y to apply
answer supervision when first connecting to the
busy announcement; enter N for no supervision.
The default for this field is N.
RESOFC (continued)
DFLTANNC CLLI Default announcement

name or
provide datafill for this subfield. Enter the default
NILWAITANNC
announcement name defined in table CLLI that
is applied to the calling party when no DSCWID
option is selected and the subscriber's default
treatment is set to ANNC.
defined.
DFLTSUPV Y or N Default supervision

(NA004-)
provide datafill for this subfield. Enter Y to apply
answer supervision when first connecting to the
DEFAULT announcement; enter N for no
supervision.
The default for this field is N.
HOLDANNC CLLI Hold announcement

name or
NILWAITANNC
name of the announcement that is applied to the
calling party when the HOLD option is chosen.
defined.
HOLDSUPV SUPV_BEFORE, Hold supervision

(NA004-) SUPV_AFTER,
NO_SUPV
provide datafill for this subfield. Enter
SUPV_BEFORE to apply answer supervision
before and SUPV_AFTER to apply answer
supervision after connecting to the HOLD
announcement.
The default for this field is NO_SUPV.
297-8021-351 Standard 05.02 May 2001

RESOFC (continued)
REMINDER CLLI Reminder

name or
NILWAITANNC
name of the announcement that is applied to the
calling party when the T-HOLD timer expires.
This announcement is used to remind the caller
to stay on the line.
defined.
TFLASH 10 to 80 Timer flash

(NA004-) (increments of 5
in units of 0.1 s)
number of seconds allowed for the subscriber to
conference a waiting call after a flash. TFLASH
is only used for the HELD call state. TFLASH is
for use with non-ADSI-compliant CPE only.
When TFLASH expires, the RETURN option is
applied
The default for this field is 15 s.
TDEFAULT 0 to 110 Timer default

in units of 1.0 s)
number of seconds (after realert) before the
default treatment type is applied to the calling
party during a DSCWID session.
THOLD 0 to 12 Timer hold

in units of 10 s)
number of seconds between announcements
while a call is on hold due to the HOLD option.
When THOLD expires, the REMINDER
announcement is started and the timer is
reinitialized.
RESOFC (continued)
SYNC_CPE TR_COMP, Synchronize CPE

UPGRADE
This subfield specifies the type of out-of-sync
functionality. Enter TR_COMP for
TR-compliant out-of-sync functionality or
UPGRADE for the proprietary out-of-sync
functionality.
DELETE_CWT Y or N Delete Call Waiting

(NA006)
This subfield provides the option to prevent Call
Waiting from being deleted from a line when
DSCWID is removed. Enter Y to delete CWT
from a line when DSCWID is removed.
Otherwise enter N.
CFDCHECK Y or N Call forward don't answer check

(NA009)
This field indicates whether or not to add
DSCWID to the line using single or dual USOC
method. Enter N to add DSCWID to the line
regardless of CFDA/CFD feature assignment.
Enter Y to assign CFDA/CFD for all types of
DSCWID other than type proprietary, and for
FWD default treatment. The default is Y.
297-8021-351 Standard 05.02 May 2001

RESOFC (continued)
FEATNAME = SCA or SCRJ

If the entry in field FEATNAME is SCA or SCRJ, provide datafill for subfields
MAXSIZE, ANSWRSUP, and TCAP_QUERY_ENABLED as described
below. After adding the datafill, then go to field FNALANN.
SCA or SCRJ MAXSIZE 0 to 8191 Maximum size

If the entry in field FEATNAME is DRCW, SCA,
SCF, or SCRJ, provide datafill for this subfield.
Enter the maximum size of the selective call list for
the office.
The recommended size is 31. The lesser of this
field and parameter SLE_ITEMS_IN_SEGMENT in
table OFCENG controls the maximum size of the
list.
ANSWRSUP Y or N Answer supervision

Enter Y when answer supervision is returned when
a rejected call for SCA goes to SCA treatment or for
SCRJ goes to SCRJ treatment; otherwise, enter N.
This applies long distance charges for the call.

_ENABLED
SCA, SCF, or SCRJ, provide datafill for this
subfield. Enter Y to enable TCAP query. Enter N to
disable TCAP query.
The default is Y.
If the value of the TCAP_QUERY_ENABLED field
is changed from Y to N, and the SOC option
RES00073 is not on, then the following message
will be displayed: Change will not be active until
SOC option RES00073 is turned ON.
FEATNAME = SCF
If the entry in field FEATNAME is SCF, provide datafill for subfields
MAXSIZE, as described below. After adding the datafill, then go to field
FNALANN.
If the entry in field FEATNAME is SCF and ACCESS equals UNIVER,

provide datafill for subfields SCRNCL, RINGMEM, NUMCALLS, and
RESOFC (continued)
TCAP_QUERY_ENABLED as described below. After adding the datafill,

then go to field FNALANN.
SCF MAXSIZE 0 to 8191 Maximum size

If the entry in field FEATNAME is SCF, provide datafill
for this subfield. Enter the maximum size of the
selective call list for the office. The recommended size
is 31. The lesser of this field and parameter
SLE_ITEMS_IN_SEGMENT in table OFCENG controls
the maximum size of the list.
SCRNCL NSCR Screening class

(BCS35-)
If the entry in field FEATNAME is SCF and the entry in
field ACCESS is UNIVER, provide datafill for this
subfield. Enter NSCR for no screening class.
NUMCALLS 1 to 1024 Number of calls

(BCS35-)
subfield. Enter a number to indicate the number of calls.
RINGMEM NORING, Ring member

(BCS35-) RING, NA
subfield. Enter NORING, RING, or NA (not applicable).

_ENABLED
Enter Y to enable TCAP query. Enter N to disable TCAP
query.
The default is Y.
If the value of the TCAP_QUERY_ENABLED field is
changed from Y to N, and the SOC option RES00073 is
not on, then the following message will be displayed:
Change will not be active until SOC option RES00073
is turned ON.
297-8021-351 Standard 05.02 May 2001

RESOFC (continued)
FEATNAME = SCWID
If the entry in field FEATNAME is SCWID, provide datafill for subfields
DATETIME, DELETE_CWT, and ACKTONE as described below. After
adding the datafill, then go to field FNALANN.
SCWID DATETIME Y or N Date and time

(NA002-)
If the entry in field FEATNAME is SCWID, provide datafill for
this subfield. Enter Y or N. Setting the entry to Y will allow
date and time information to be sent from the switch to the
SCWID subscriber's CPE along with the calling party
identification information. The default is Y.
Field ENABLED must be datafilled Y to allow delivery of
calling party identification during call waiting for SCWID
subscribers.
DELETE_C Y or N Delete Call Waiting.

WT (NA006)
This subfield provides the option to prevent Call Waiting from
being deleted from a line when SCWID is removed.
Enter Y to delete CWT from a line when SCWID is removed.
Otherwise enter N.
ACKTONE Y or N Acknowledgment tone

(-NA002)
Enter Y if an acknowledgment tone is desired. Otherwise
enter N.
RESOFC (continued)
FEATNAME = all entries

Datafill the following subfields for all features.
Field descriptions
FEATNAME FNALANN see subfields Feature not allowed announcement

This field consists of subfields POTS_ACCESS
and FNAL_CLLI.
POTS_ 00 to 99 POTS access

ACCESS
Enter the two-digit plain ordinary telephone
service (POTS) access code for activation of the
CLASS feature that is used in POTS translation.
The entry in this subfield must be identical to the
table access code that is datafilled in table
IBNXLA and used by the Meridian Digital
Centrex (MDC) (Integrated Business Network
(IBN) lines.
FNAL_CLLI alphanumeric Announcement common language location

(1 to 16 identifier
characters)
Enter the announcement CLLI for the
announcement given when the subscriber tries
to activate the feature to which the line has not
subscribed. If the feature is disabled, (field
ENABLE is set to N) then POTS lines get PDIL
(Partial Dial) treatment and CLASS lines get
FNAL (Feature Not Allowed) treatment. The
CLLI must first be datafilled in tables CLLI,
ANNS, ANNMEM and DRAMTRK.
Datafill example
The following example shows sample datafill for table RESOFC.
297-8021-351 Standard 05.02 May 2001

RESOFC (continued)
MAP display example for table RESOFC
KEY ENABLED
FEATDATA
FNALANN
_______________________________________________________________________
ACB Y
SUBSCR ACB 5 3 30 180 60 5 5 2 Y DENY DENY DENY N
$
AR Y
SUBSCR AR ONELEVEL 5 3 30 180 60 5 5 2 Y DENY DENY DENY Y
COT Y
UNIVER COT ONELEVEL $ N
$
DSCWID Y
SUBSCR DSCWID COMPLETE FWD NONE DSCWDBUSY N DSCWDDFLT N
DSCWDHOLD SUPV_BEFORE DSCWDREMD 15 15 6 UPGRADE N $
Table history
MMP13
Added value T4 as an intraswitch guard time value to subfields ACB and AR.
NA011
This release affects table RESOFC in the following ways:
The COT feature can be made universally accessible for IBN lines by
changing the ACCESS field from SUBSCR to UNIVER.
Added RND to the list of options for ISDN BRI lines.
NA009
This release affects table RESOFC in the following ways:
The ACRJ option for ISDN BRI subscribers is activated or deactivated in
table RESOFC.
The Universal Access feature for ISDN BRI subscribers is activated if the
ACCESS field is set to UNIVER.
The BRI in RES feature is only available if the ENABLED field is set to Y.
Introduced option CFDCHECK in field DSCWID of subfield
FEATNAME of field FEATDATA.
RESOFC (continued)
NA008
The following changes were made to table RESOFC:
Added note that CNAMD and CND are applicable to ISDN subscribers
and are controlled for an office by the existing CNAMD and CND tuples
in table RESOFC.
Added note that the CIDSSUP and CIDSDLV features for ISDN BRI
subscribers are controlled through the existing CNDB tuple.
NA007
Field TCAP_QUERY_ENABLED was added. If SOC option RES00073 is
turned on, field TCAP_QUERY_ENABLED provides an optional method of
disabling TCAP query for the following features:
ACB
AR
DRCW
SCA
SCF
SCRJ
NA006
Field DELETE_CWT was added to provide the option to delete or not to delete
CWT from a line when DSCWID or SCWID is removed.
NA004
Fields WAITANNC, REALERT, and DATETIME were deleted as
conditional provide datafill for the feature DSCWID.
Fields DTYPE, DEFTRMT, AMA, BUSYANNC, BUSYSUPV,
DFLTANNC, DFLTSUPV, HOLDANNC, HOLDSUPV, REMINDER,
TFLASH, TDEFAULT, THOLD, and SYNC_CPE were added as
conditional provide datafill for the feature DSCWID.
NA003
Features CID and DNID were added to table RESOFC.
297-8021-351 Standard 05.02 May 2001

RESOFC (continued)
NA002
The ADSI line option was added to field FEATNAME and subfield
FEATNAME.
Field ACKTONE was deleted and field DATETIME was added to the
conditional provide datafill for the SCWID feature.
Field DATETIME was added to the conditional provide datafill for the
DSCWID feature.
BCS36
Default values for features ACB and AR were added. Description of field
ACCESS and of subfield FLASHACT for features ACB and AR was clarified.
This section provides information on dump and restore procedures and
announcement CLLIs for table RESOFC.
Dump and restore

If the entry in field FEATNAME is COT, copy all existing fields from the old
tuple to the new tuple. Initialize the new fields added by this feature to their
NIL values in the new tuple. Follow the existing restore table procedure with
the new tuple. Otherwise, copy with existing restore table procedure with old
tuple. For two-level activation, fields BADIGITS and TIMEOUT are datafilled
to 0 (zero) if the old tuple is datafilled two-level.
If a feature AR tuple is previously datafilled as one-level activation, fields

BADIGITS and TIMEOUT do not appear.
The TCAP_QUERY_ENABLED field was introduced in CCM07. It is

initialized to the default value of Y on a restore to CCM07.
For CCM07 and up, the TCAP_QUERY_ENABLED field is restored to the

value from the dump side.
RESOFC (end)
Announcement CLLIs
The following table shows examples of announcement CLLIs.
Announcement CLLIs
CLLI Announcement
cllix primary language trace success
clliy primary language trace failure
cllil primary language initial prompt
cllin primary language nth level prompt
cllia secondary language trace success
cllib secondary language trace failure
cllis1 secondary language initial prompt
cllisn secondary language Nth level prompt
297-8021-351 Standard 05.02 May 2001

RESTAMA
Table name
TOPS Restricted AMA Table
Table RESTAMA allows the operating company to select the entry on
automatic message accounting (AMA) in the calling service class field for any
billing class defined in table RESTBIL. If the billing class is not defined in
table RESTBIL before being entered in table RESTAMA, the entry is rejected.
Since the default AMA class entry (field AMACLASS) is NONCOIN, it is not
necessary to make an entry in table RESTAMA if an entry is made in table
RESTBIL.
No entry can be made in table RESTAMA unless an entry is made in table

RESTBIL for the same billing class.
If the Specifying DA Billing Options by Restricted Billing Class feature is

present, then table RESTAMA is not indexed with the restricted billing class
from tables SPLDNID and RESTBIL. Instead, table RESTAMA is indexed
from field AMARBC in either table RESTBIL or DARSTBIL.
For related information, refer to table RESTBIL.

Table RESTBIL must be datafilled before table RESTAMA.
Table size
0 to 100 tuples
Initially the table is empty and is extended only as the user defines a new
restricted billing class.
RESTAMA (end)
Datafill
The following table lists datafill for table RESTAMA.
Field descriptions
Subfield or
BILCLASS 0 to 100 Billing class. Enter a valid billing class as

previously defined in table RESTBIL.
AMACLASS COIN HOTEL Automatic message accounting class. Enter

or the class of service to be output on AMA for
NONCOIN the given billing class.
RBAMA_NIL
Default value is NONCOIN.
Datafill example
The following example shows sample datafill for table RESTAMA.
MAP display example for table RESTAMA
BILCLASS AMACLASS
________________________________________________________
4 COIN
297-8021-351 Standard 05.02 May 2001

RESTBIL
Table name
TOPS Restricted Billing Table
There is a requirement in DMS Traffic Operator Position System (TOPS) to
apply selective billing to certain types of calls, which implies that certain
origination classes (that is, RSP) must be restricted with respect to the type of
billing (that is, COL [collect]) that can apply to above calls.
Upon reception of an automatic number identification (ANI) identification

(ID) digit 7 on a combined trunk, an entry in table SPLDNID is made in an
attempt to match the calling number with one of the entries in the table. If a
match is found, a customer definable display (field SCRNDISP in table
RESTBIL) will be given at the TOPS position, on call arrival, to warn the
operator of the special treatment of the call.
Upon reception of an ANI ID digit 0 or 7 on a restricted billing (value in field

STATCLAS of table TRKGRP) trunk, an entry in table SPLDNID is made in
an attempt to match the calling number with one of the entries in the table. If
a match is found, a customer-definable display (field SCRNDISP in table
RESTBIL) is given at the TOPS position, on call arrival, to warn the operator
of the special treatment of the call. If the ANI ID digit is 0, then ANI spill is
preserved, while if the ANI ID digit is 7, the call is treated as an ANI failure.
Once at the TOPS position, the call will not be allowed to be floated until a
billing type (field BILTYPES in table RESTBIL) compatible with its restricted
billing class (field BILCLASS in table RESTBIL) is entered by the operator.
Table RESTBIL allows the operating company to activate up to 100 restricted

billing classes, while table RESTAMA is used to specify for each of the
restricted billing classes activated, what calling class is printed on automatic
message accounting (AMA) (that is, noncoin, coin, hotel).
Table RESTBIL is used to define billing classes (up to 100) and to associate
each defined class to a screen display (operating company's choice for the
name) and one or more (up to six) valid billing types.
If the operating company decides not to specify any screen display, the default
is a blank field.
At least one type of billing for any defined call class is recommended,
otherwise the system internally defaults to the restrictions currently applying
to RSP. Default entries are not printed.
RESTBIL (continued)
Table RESTBIL provides the same function for toll and assist (TA) calls as
table DARSTBIL does for directory assistance (DA) calls. The restricted
billing class number assigned to a particular directory number (DN) in table
SPLDNID is used as the index into both table RESTBIL and DARSTBIL.
Having the same index for two tables imposes one of the following
restrictions:
Two DNs that have the same billing restrictions for TA, but different billing
restrictions for DA service must be assigned different restricted billing
class numbers in table SPLDNID.
Two DNs that have the same billing restrictions for DA, but different
billing restrictions for TA service must be assigned different restricted
billing class numbers in table SPLDNID.
Field AMARBC, either in table RESTBIL or DARSTBIL, is used as the index

into table RESTAMA, rather than the actual restricted billing class from table
SPLDNID.

Table SPLDNID must be datafilled before table RESTBIL.
Table size
0 to 505 tuples
Table RESTBIL is a static table, initially empty and extended only when the
user defines restricted billing classes (up to a maximum of 100 entries). If the
Specifying DA Billing Options by Restricted Billing Class feature is present
in the switch, table size is increased from 505 words to 606 words.
Field Descriptions (Sheet 1 of 2)
Subfield or
BILCLASS 0 to 100 Billing class. Enter a valid restricted billing

class as previously defined in table SPLDNID.
AMARBC 0 to 100 Automatic message accounting restricted

billing class. The entry in this field is used as
index into table RESTAMA. Specify the value
to be recorded as the restricted billing class
on AMA for toll and assist (TA) calls.
297-8021-351 Standard 05.02 May 2001

RESTBIL (continued)
Field Descriptions (Sheet 2 of 2)
Subfield or
SCRNDISP alphanumeric Screen display. Enter an arbitrary name to be

(up to 8 displayed on the TOPS screen in the class of
characters) service field for a particular billing class.
BILTYPES 3RD, CC, Billing types. Enter a set of up to six allowable

COL, PD, billing types for a defined billing class. If less
SPLCLD, or than six types are required, end the list with a
SPLCLG $ (dollar sign). The following billing types may
be used to define a billing class:
3RD (calling third number billing)
CC (calling credit card)
COL (collect) (AUTOCOL [automatic
collect])
PD (sent paid)
SPLCLD (called special billing)
SPLCLG (calling special billing)
CCPDTYPS ALL, LOCAL, Call completion paid types. Enter one of the
NONE, TOLL following values required for restrictions
applying to sent DA paid call completions:
Enter ALL to allow all calls to be paid
complete.
Enter LOCAL to allow local calls to be
paid complete.
Enter NONE to disallow all calls to be
paid complete.
Enter TOLL to allow toll calls to be paid
complete.
Note: Field CCPDTYPES can only be set to

NONE or ALL if the Directory Assistance
(DA) Call Completion (CC) feature is not
available in the central office switching
software.
Datafill
The following table lists datafill for table RESTBIL.
RESTBIL (end)
Datafill example
The following example shows sample datafill for table RESTBIL.
MAP display example for table RESTBIL
BILCLASS AMARBC SCRNDISP

BILTYPES CCPDTYPS
________________________________________________________________
1 21 SENTPAID
( COL) ( CC) ( 3RD) (SPLCLG) (SPLCLD)$ LOCAL
297-8021-351 Standard 05.02 May 2001

REXINTEN
Table name
Routine Exercise Intensity Table
Table REXINTEN allows portions of message switch (MS) and link interface
module (LIM) system routine exercise (REX) tests to be bypassed on selected
days of the week. Table REXINTEN provides flexibility in the definition of
REX executions for components of REX tests that cause the temporary
removal of equipment from service.
A full REX test includes busying the node and returning it to service (RTS). A
base REX test only performs in-service testing. It is recommended that a full
REX test be run once a week.
Table REXINTEN only affects MS and LIM REX tests initiated by the system
REX controller in DMS SuperNode and DMS SuperNode SE switches.
Since table REXSCHED also controls which days of the week a REX test is
run, conflict can arise between tables REXINTEN and REXSCHED. Full
conflict between the two tables must be avoided. For example, if the REX test
is turned off for a LIM on Tuesdays in table REXSCHED (field DAYSDSBL
set to TUE), but a full REX test is scheduled for Tuesdays only in table
REXINTEN (field DAYSFURX set to TUE), then neither a base nor a full
REX test runs on Tuesday. Full REX is turned off completely.
For related information, refer to table REXSCHED and office parameter

NODEREXCONTROL in table OFCVAR.

There is no requirement to datafill other tables prior to table REXINTEN.
Tuples corresponding to the MS and LIM node types are added automatically
during system initialization. Additions and deletions to the table are not
allowed.
Table REXINTEN is active by default. To deactivate it for a dump and restore,

enter ALL in field DAYSFURX.
Table size
2 tuples
REXINTEN (end)
Datafill
The following table lists datafill for table REXINTEN.
Field descriptions
Subfield or
NODETYPE LIM or MS Node type Enter the type of node to be

tested, LIM (link interface module) or MS
(message switch).
DAYSFURX MON, TUE, Days of the week Enter the day or days of the
WED, THU, week when a full routine exercise (REX) test
FRI, SAT, is to run.
SUN, ALL, or
Separate each entry with a single space. If no
NONE
further entries are required, end the list with a
$ (dollar sign).
Enter ALL if a full REX test is to run every day
of the week.
Enter NONE if no full REX test is to run.
Enter NONE for STP loads.
The default value for LIM is TUE.
The default values for MS are TUE, WED.
Datafill example
The following example shows sample datafill for table REXINTEN.
In this example, a full REX test is run on the MS on Tuesdays and on the LIM
on Tuesdays and Thursdays.
MAP display example for table REXINTEN
NODETYPE DASFURX
________________________________________________________
MS TUE WED $
LIM TUE $
Table history
BCS35
Table REXINTEN was introduced.
297-8021-351 Standard 05.02 May 2001

Data schema tables 1
REXSCHED
Table name
Routine Exercise Schedule Table
Table REXSCHED contains the information that the system routine exercise
(SREX) controller requires. This table schedules routine exercise (REx) tests
according to the requirements of the operating company. The operating
company requires these tests for spectrum peripheral modules (SPMs),
series-3 peripheral modules (PM), XPM-based peripheral modules (XPS), and
file processors (FP).
The operating company can use table REXSCHED to customize the REx test
schedule to a switch. Table REXSCHED does not force operating companies
to create REx test schedules. This table provides flexibility to operating
companies to schedule REx tests.
For each type of node, operating company personnel can perform the
following actions:
enable or disable individual REx tests
define REx test frequencies
define the maximum number of REx tests that the system can run in
parallel for SPM_REX_TEST. This should not be more than the maximum
number decided by the system. As of feature number A89007516 the
maximum number is one
prevent tests on defined days
Computing module (CM), message switch (MS), and enhanced network

(ENET) REx tests have a critical identification in software design. These tests
are essential. The operating company can use the REXTEST command to
suspend these critical tests for a limited time.
You can use the ENABLE field in table REXSCHED to disable the REx
testing. The REx tests than you can disable include critical tests. This action
can have serious consequences. Northern Telecom does not recommend that
DMS-100 Family NA100 Customer Data Schema Reference Manual Volume 9 of 12, SN06 and up
REXSCHED (continued)
you disable REx critical tests. If you disable critical REx tests, warnings
appear. If you disable CM REx testing, the following conditions occur:
Automated image testing does not occur. This testing includes image
testing that follows patch applications.
Automated activity switch occurs when system diagnostics cause this
activity.
Full CM REx testing does not occur every week.
You can use the DAYSDSBL field to exclude some REx tests from the test
schedule on specified days of the week.
Table REXSCHED must have a minimum of two entries. The CM and MS

REx tests are present in every DMS SuperNode office with series-3 PMs,
applications, and file processors. The number of REx tests that table
REXSCHED defines can increase with the addition of nodes and services.
The operating company cannot add or delete REx tests (from field
REXTSTID). The system automatically defines the entries in this table. This
condition causes entries to occur for the REx tests available in the office. The
operating company can change the other fields.
Refer to the descriptions of table REXINTEN and office parameter

NODEREXCONTROL in table OFCVAR for related information.
LCM and LCMCOV REx tests

In NA004 and later versions, the LCM REX Controller Enhancement feature
has the following function. This feature eliminates the conflict that was
present before between the extended peripheral module (XPM) and line
concentrating module (LCM) REx tests. To eliminate the conflict, the feature
migrates the LCM REx test from the LCM node audit process to the SREX
controller. The feature removes the continuity and voltage (COV) test step that
the system performs on the power converters and ringing generator. The
feature removes the COV step from the LCM REx test and places the step in a
separate test. This separate test is the LCMCOV REx test. This feature adds
the tuples LCM_REX_TEST and LCMCOV_REX_TEST to table
REXSCHED.
LCM, LGC REx test incompatibility with ATT BERT test

Do not schedule the ATT BERT test to run at the same time as the LCM and
LGC REx tests. This ATT BERT test is in table ATTSCHED. These LCM and
LGC REx tests are in table REXSCHED. You can schedule LCM and LGC
REx tests to run at the same time as the ATT BERT test. The trunks that the
system tests cannot operate, and the ATT BERT test fails. The system
297-8021-351 Preliminary 09.01 June 2003

generates log ATT122 when a schedule is present for these tests to run at the
same time.

The system automatically enters data in table REXSCHED.
Office parameter NODEREXCONTROL in table OFCVAR activates the REx

test scheduling mechanism. Field REXON turns the REx test scheduling
mechanism ON or OFF. For additional information on office parameter
NODEREXCONTROL, refer to Office Parameters Reference Manual on
office parameter NODEREXCONTROL.
You can disable the automatic REx test configuration. When this event occurs,
table REXSCHED allows the operating company to configure automatic REx
testing manually for the REx test identifier LGC_REX_TEST. You can enable
the automatic REx test configuration. When this event occurs, the system
does not allow attempts to change fields PARALLEL and PERIOD for
LGC_REX_TEST. These attempts result in an error message.
To manually update fields PARALLEL and PERIOD, you must disable

automatic configuration. To disable automatic configuration, enter the
following command at the command interpreter (CI) level of the MAP display:
>AUTOCONFIG OFF LGC_REX_TEST
Table size
2 to 64 tuples
Normal size is 16 tuples.
Datafill
Datafill for table REXSCHED appears in the following table.
Field descriptions
Subfield or
REXTSTID see subfield Routine exercise test identifier. This field

contains subfield REX_TEST_ID.
REX_TEST_ID alphanumeric Routine exercise test identifier. The system

1 to 16 defines routine exercise (REx) test identifiers
characters (REXTSTID). The REx tests that are available in
the office appear in this table.
Field descriptions
Subfield or
ENABLE Y or N Enable. Enter Y (yes) to enable or N (no) to

disable the REx test. The default value for this
field is Y.
Note: If you disable critical (CM, MS, or ENET)

REx tests, the system generates alarms. These
alarms are CM RExSch, MS RExByp, and Net
RExSch, in that order. The system also
generates, IOAU112, CM179, MS104, and
ENET501 logs.
PERIOD 1 to 7 Period. Enter a value between 1 and 7 included.

This value defines the minimum number of days
between two REx tests that follow on the same
node.
Each REx test must run at least one time every
week.
If you disable automatic REx test configuration,
the default value for this field is 1. This value
indicates that an REx test occurs every day. If
you enabled automatic REx test configuration,
the default value for this field for REx test
identifier LGC_REX_TEST is 7. This value
indicates that an REx test occurs every week.
The system does not allow you to change this
period.
This system sets this field to a default value of 7
for REx test identifiers LCM_REX_TEST,
LCMCOV_REX_TEST, and SPM_REX_TEST.
When this value is 7, an REx test occurs every
week. To change the period of a test, set this
field to a different value.

Field descriptions
Subfield or
PARALLEL 0 to 99 (Note) Parallel. This field limits the number of REx tests
that can occur in parallel for one node type. The
SREX controller can maximize the number of
REx tests run in parallel. The operating company
can limit the number of parallel REx tests in a
node type but cannot increase the number of
parallel REx tests beyond the limit defined for the
application. This value is different for all REx
tests. The resources that each test requires
determine this value.
You can disable automatic REx test
configuration. The default value for this field is
the maximum value that the maintenance
software for each REx test allows. These tests
do not include the LCM REx test and LCMCOV
REx test. For the LCM REx test and LCMCOV
REx test, the default value for this field is the
minimum value.
You can enable automatic REx test
configuration. When the event occurs, the
default value for the REx test identifier
LGC_REX_TEST is the default value that the
system automatically configures. An NA (does
not apply) appears in this field. The system does
not allow you to change the value of this field for
the LGC_REX_TEST tuple.
Note: For the LCM_REX_TEST tuple, this field

can be a value from 1 to 4. For the
LCMCOV_REX_TEST tuple, this field must
contain 1. The LCMCOV REx test does not
execute on more than one LCM at a time. This
field contains a default value of 1 for the
LCM_REX_TEST, LCMCOV_REX_TEST, and
SPM_REX_TEST tuples.
Field descriptions
Subfield or
DAYSDSBL MON, TUE, Days disabled list. Enter the days on which to
WED, THU, disable the REx test. The name day applies to
FRI, SAT, the scheduled start of the REx test. For example,
SUN, ALL, or an REx test can be in a schedule. The test can
NONE run from Monday evening 23:00 to Tuesday
morning 02:00. The test runs at 01:00 Tuesday.
In this condition, the system records as sent that
the test started on Monday.
Each REx test must run at least one time every
week.
Enter ALL to disable an REx test on every day of
the week. This entry can suspend critical REx
tests for a limited time.
The default value for this field is NONE. This
value represents REx test never disabled.
Datafill example
Sample datafill for table REXSCHED appears in the following example.
MAP example for table REXSCHED
REXTSTID ENABLE PERIOD PARALLEL DAYSDSBL

_______________________________________________________________________
MS_REX_TEST Y 1 1 NONE
CM_REX_TEST Y 1 1 NONE
ENET_REX_TEST Y 1 1 NONE
SLM_REX_TEST Y 1 1 NONE
LIM_REX_TEST Y 1 17 NONE
LGC_REX_TEST Y 7 NA NONE
MSB_REX_TEST Y 1 10 NONE
LCM_REX_TEST Y 7 4 NONE
SPM_REX_TEST Y 7 1 NONE
Note: Do not schedule the XLIU_REX_TEST to occur during a full REx of Table REXINTEN.
For offices with spare XLIU and NIU modes, sample datafill for table
REXSCHED appears in the following example.

MAP example for table REXSCHED for spare XLIU and NIU nodes
REXTSTID ENABLE PERIOD PARALLEL DAYSDSBL

_______________________________________________________________________
MS_REX_TEST Y 1 1 NONE
CM_REX_TEST Y 1 1 NONE
SLM_REX_TEST Y 1 1 NONE
ENET_REX_TEST Y 1 1 NONE
XLIU_REX_TEST Y 1 1 MON TUES WED FRI SAT SUN $
LIM_REX_TEST Y 1 1 NONE
LGC_REX_TEST Y 7 NA NONE
RCC_REX_TEST Y 7 1 NONE
SMSR_REX_TEST Y 7 1 NONE
NIU_REX_TEST Y 1 3 THU $
LCMCOV_REX_TEST Y 7 1 NONE
LCM_REX_TEST Y 7 1 NONE
Note: Do not schedule the XLIU_REX_TEST to occur during a full REx of Table REXINTEN.
Table history
SN06 (DMS)
This table was updated for feature number 89007516.
BASE06
Restrictions on how to disable CM, MS, and ENET REx tests were removed
in BASE06.
NA004
The following changes occurred according to feature AF5898, LCM REX
Controller Enhancement:
The LCM and LCMCOV REx tests subsection under Functional
description section was added in NA004.
Information on LCM_REX_TEST and LCMCOV_REX_TEST tuples was
added to Field descriptions table in NA004.
The LCM_REX_TEST and LCMCOV_REX_TEST tuples were added to
MAP example in Datafill example section in NA004.
Supplementary information section was added to document error
messages related to LCM_REX_TEST and LCMCOV_REX_TEST tuples
in NA004.
The following additional changes occurred:

Reference in Functional description section to 16 REx tests defined in
the system was removed in NA004. This removal occurred because this
number can vary.
Note in Functional description section was removed in NA004. This
note states that if REx tests are not available, table REXSCHED is empty.
This condition cannot be present.
Paragraph in Datafill sequence and limits section was removed in
NA004. This paragraph states that you must enter data in table
REXSCHED after all the inventory tables because the table identifies the
actual REx tests available in the office. Removal of this paragraph
occurred because the system automatically enters data in table
REXSCHED.
The spelling of entry TUES for field DAYSDSBL was corrected to read
TUE in NA004.
BCS36
Subfield REX_TEST_ID was added in BCS36.
CSP03
Changes related to the CI command AUTOCONFIG were added in CSP03.
The following error message appears if you attempt to set field PARALLEL to
a value greater than 4 for the LCM_REX_TEST tuple:
The maximum for LCM_REX_TEST is 4 parallel REX

test(s)
The LCMCOV REx test does not execute on more than one LCM at a time.
The following error message appears if you attempt to set field PARALLEL to
a value other than 1 for the LCMCOV_REX_TEST tuple:
The maximum for LCMCOV_REX_TEST is 1 parallel REX

test(s)
The SPM REx test does not execute on more than one LCM at a time. The
following error message appears if you attempt to set field PARALLEL to a
value other than 1 for the SPM_REX_TEST tuple:
The maximum for SPM_REX_TEST is 1 parallel REX

test(s)

SPM_REX_TEST has a dependency on ENET_REX_TEST and

MS_REX_TEST. This means that REX test will not be run on SPM nodes
while ENET REX and MS REX tests are being executed.
You can disable a critical REx test in table REXSCHED. If you attempt to
suspend the REx test with the REXTEST SUSPEND command, the following
error message appears:
REXTEST SUSPEND successful on <REx_test_type>. However,

<REx_test_type> is already disabled in table REXSCHED.
Note: The REx_test_type can be CM_REX_TEST, MS_REX_TEST, or

ENET_REX_TEST.
You can disable a critical REx test in table REXSCHED. If you attempt to
enable the REx test with the REXTEST RESUME command, the following
error message appears:
REXTEST RESUME successful on <REx_test_type> However,

<REx_test_type> is disabled in table REXSCHED.
Note: The REx_test_type can be CM_REX_TEST, MS_REX_TEST, or

ENET_REX_TEST.
An issue affecting offices with spare X.25/X.75/X.75 Link Interface Unit

(XLIU) and Node Interface Unit (NIU) nodes has been discovered. The spare
XLIU nodes begin REx before the NIU node has come back in service (INSV)
from completing its REx test; it remains at in-service trouble (ISTB) status.
The ISTB status of NIU causes the spare XLIU to go into system-busy status
(SYSB). To prevent this conflict, datafill the XLIU and NIU REx in Table
REXSCHED so that the tests occur on separate days. See example datafill in
this section.
Note: Do not schedule the XLIU_REX_TEST to occur during a full REx

of Table REXINTEN.
REXSCHED (end)

RGSIGSYS
Table name
Register Signaling System Table
Table RGSIGSYS contains all the relevant customer variable register signaling
data. This allows the customer to change the register signaling variables on a
trunk subgroup or on a line attribute basis.
There are three fields in table TRKSGRP that indicate the required register
signaling systems: RGICSSI (register incoming signaling system), RGOGSSI
(register outgoing signaling system), and RG2WSSI (register two-way
signaling system). Each of these fields refers to an entry in table RGSIGSYS.
Field RSSINDX in table LINEATTR relates to an entry in table RGSIGSYS.
Each tuple in table RGSIGSYS describes an instance of a register signaling

system. There can be many different instances of register signaling systems of
the same type.
Each tuple in the table has the following layout:
RGSIGIDX RGSIGTYP variable_area
The customer defines the name of a register signaling system index

(RGSIGIDX) by adding a new tuple to table RGSIGSYS. The key to each
entry in the table is field RGSIGIDX.
There are nine register signaling types as described below in the following
table . Each register signaling type is designed to support a generic signaling
system.
Register signaling types (Sheet 1 of 2)
Types Register signaling system
MF3 Three-phase multifrequency (MF) pulse signaling
MFCR2 (MF compelled [MFC] R2 signaling(Used by DMS-300 switching

units.)
NTRS03 MF pulse packet (MFPP) type 2 (MFPP-2)(Used for Confederation

of Independent States (CIS) network for incoming toll calls to a
DMS that is replaced as CIS automatic intercity telephone
exchange (AMTC-2, 3), toll exchanges.
297-8021-351 Standard 05.02 May 2001

RGSIGSYS (continued)
Register signaling types (Sheet 2 of 2)
Types Register signaling system
NTRS04 R1 modified signaling
NTRS05 E and M signaling
NTRS06 see NTRS14
NTRS10 MF pulsed signaling(Used only in China.)
NTRS11 MFC R2 signaling(Used by World Systems DMS-100 and

DMS-200 switching units and switching units using the Chinese
variant of the CCITT R2 signaling system.)
NTRS12 Socotel compelled trunk register signaling(Used by World Systems

DMS-100 and DMS-200 switching units.)
NTRS14 MF pulse packet (MFPP) type 1 (MFPP-1)(Used for CIS network

between local outgoing and toll incoming AMTC-KE (electronic)
tandem DMS-100/200I (international) switches.
RGHYBRID Hybrid register signaling
The name of each subfield is an acronym describing the application of the time
value or variable. The acronyms, in general, begin with one of the following
prefixes:
O (outgoing variables begin with O)
I (incoming variables begin with I)
TM (time)
HD (hold)
RG (register)
MIN or MAX (minimum or maximum digits)
Updating of signaling system data in peripheral modules

The contents of table RGSIGSYS reside in both international line group
controllers (ILGC) and international digital trunk controllers (IDTC)
peripheral modules (PM). These values are downloaded upon the return to
service (RTS) of each PM. Any data that is changed when a PM is in service
is updated when the PMs are RTSed from the PM level of the MAP
(maintenance and administration position). Only the PM containing the line
or trunk with changed signaling data must to be RTSed.
RGSIGSYS (end)
Hybrid signaling
The hybrid signaling (RGHYBRID) supports more than one register signaling
for a trunk in order to provide switching and automatic number identification
(ANI). In field RGSIGTYP, selector RGHYBRID consists of the components
of a hybrid structure. In other words, combinations of signaling types MF3,
MFPP NTRS02, NTRS05, NTRS06, and NTRS03 or NTRS14.
For further information on signaling type RGHYBRID, refer to table

RGHYBRID.

There is no requirement to datafill other tables prior to table RGSIGSYS.
Table size
Memory is allocated for 255 register signaling indexes.
Table history
BCS36
Subfield RSS_CHAR_VECTOR was added. Signaling types NTRS063 and
NTRS14 were added.
This section provides information on error messages that can occur when
datafilling table.
Error messages
If an attempt is made to delete an RGSIGIDX tuple from table RGSIGSYS and
there is a tuple in TRKSGRP, the following error message is output:
CANNOT DELETE THIS TUPLE; IT IS USED BY <the CLLI of the trunk

using the tuple is indicated here>
297-8021-351 Standard 05.02 May 2001

RGSIGSYS type MF3
Three-phase multifrequency (MF) pulse signaling

A description of the customer variable data for register signaling type MF3
appears in this section.
The method by which you add or change RGSIGSYS data appears in the
following section.
Making changes to RGSIGSYS

A user can change signaling system data for many reasons. These reasons
include the following examples:
1. Addition of new trunks with a new register signaling system to the switch
occurs.
2. Separation of one trunk from the trunk group occurs to experiment with
the register signaling variables of the trunk.
3. One or more of the timing variables must change for trunks with a
signaling system.
4. The trunks of a specified signaling system change to a new signaling
system type.
In the first two examples, data entry for new trunks must occur. The rule for
entry for new trunks requires that table RGSIGSYS contain entries before
table TRKSGRP. The creation of a new entry in table TRKSGRP can support
a new trunk that requires a new RGSIGIDX. If this condition occurs, an entry
for that RGSIGIDX must first be in table RGSIGSYS.
The condition in the third example does not require changes to table
TRKSGRP. The appropriate variables can change in table RGSIGSYS. To
implement changes in a tuple in table RGSIGSYS, a download must occur.
The system must download the tuples that change to the peripheral module
(PM).
The fourth example represents an important change to the signaling in use on

a set of trunks. This change requires close control with the switching center at
the far end of these trunks. The RGICSSI, RGOGSSI, or RG2WSSI field of
the trunk subgroup points to the different RGSIGIDX. Busy (BSY) and return
to service (RTS) each trunk in the subgroup from the trunk test position (TTP)
level of the MAP display.
Adding a new RGSIGSYS tuple

In the previous examples and item 2 the , addition of the new signaling system
to RGSIGSYS occurs first.
RGSIGSYS type MF3 (continued)
In table RGSIGSYS, use the ADD command to add a new RGSIGIDX. When
the system prompts you for an entry, enter the specified RGSIGTYP. A prompt
occurs for changes from the displayed default value. To keep the default value,
enter a blank line.
To activate the new tuple in table RGSIGSYS, a download of the data to the
PMs must occur. The PM must be RTSed from the PM level of the MAP
display.
Next, enter the new trunks in the normal way. Field RGICSSI, RGOGSSI, or
RG2WSSI of the new subgroup must refer to the new RGSIGIDX in table
RGSIGSYS. The system does not download data at this point.
To activate this change, manual busy (MBSY) and RTS each trunk in the
subgroup from the TTP level of the MAP display.
Example 1
In the following example, the addition of a new RGSIGIDX entry occurs. This
entry is MYRGSIGIDX of type MF3. The variable values are the same as the
default values for MF3, except for fields OPULSIG and IKPTM. Field
OPULSIG changes from 68 ms to 75 ms and field IKPTM changes from 15 s
to 8 s.
Adding a new tuple to table RGSIGSYS.
At the MAP terminal

1 To access table RGSIGSYS, type
>TABLERGSIGSYS
MAP response:
TABLE RGSIGSYS
2 To add the new signaling index, type

>ADD
MAP response:
ENTER Y TO CONTINUE PROCESSING OR N TO QUIT.
3 To confirm the addition, type

>Y
MAP response:
RGSIGIDX:
297-8021-351 Standard 05.02 May 2001

4 To enter the new signaling index, type

>myrgsigidx
MAP response:
RGSIGTYP
5 To enter the new signaling type, type

>mf3
MAP response:
OKPSIG : 100
6 To leave the outgoing KP signal in the present state, press the Enter key.
MAP response:
OPULSIG : 68
7 To enter the new outgoing pulse signal length, type

>75
MAP response:
ORGHLDTM: 240
8 To leave the outgoing overall register holding time in the present state, press
the Enter key.
MAP response:
OIGDTM: 70
9 To leave the outgoing interdigital time in the present state, press the Enter
key.
MAP response:
IKPTM: 15
10 To enter the new incoming time for KP signal, type

>8
MAP response:
IMINDIG1: 3
11 To leave the incoming minimum number of digits (first phase) in the current
state, press the Enter key.
MAP response:
IMAXDIG1: 3

12 To leave the incoming maximum number of digits (first phase) in the current
MAP response:
IPSHDTM1: 15
13 To leave the incoming phase overall holding time in the current state, press
the Enter key.
MAP response
IMINDID2: 3
14 To leave the incoming minimum number of digits (second phase) in the

current state, press the Enter key.
MAP response:
IMAXDIG2: 3
15 To leave the incoming maximum number of digits (second phase) in the

MAP response:
IPSHDTM2: 15
16 To leave the incoming maximum number of digits (second phase) in the

MAP response:
IPSHDTM2: 15
17 To leave the incoming minimum number of digits (final phase) in the current
MAP response:
IMAXDIG3: 14
18 To leave the incoming maximum number of digits (final phase) in the current
MAP response:
IPSHDTM3: 15
19 To leave the incoming phase overall holding time in the current state, press
the Enter key.
MAP response:
TUPLE TO BE ADDED:
MYRGSIGIDX MF3 100 75 240 70 8 3 3 15 3 3
15 3 14 15
ENTER Y TO CONFIRM, N TO REJECT OR E TO EDIT.
20 To confirm the additional, type

>Y
297-8021-351 Standard 05.02 May 2001

MAP response:
TUPLE ADDED
21 To exit table RGSIGSYS, type

>QUIT
22 To access the MP level of the MAP display, type
>MAPCI;MTC;MP
23 To post the IDTC, type
>POSTIDTCn
where
n
is the number of the IDTC
24 To return the IDTC to service, type
>RTSPM
25 To exit the MP level of the MAP display, type
>QUIT ALL
26 To access table TRKSGRP, type
>TABLE TRKSGRP
27 To position on the trunk, type
>POSITION my trunk0
where
mytrunk
is the name of the trunk
0
is the number of the trunk
MAP response:
MYTRUNK 0 3X04AA
STD
IC DP IM N 30 4 NO SX N N N M UNEQ
28 To change the registered incoming signaling index, type

>CHANGE SGRPVARAREA RGICSSI myrgsigidx

MAP response:
ENTER Y TO CONTINUE PROCESSING OR N TO QUIT.
29 To confirm the addition, type

>Y
30 To exit table TRKSGRP, type
>QUIT
31 To access the TTP level of the MAP display, type
>MAPCI;MTC;TRKS;TTP
32 To post a group of circuits by the common language location identifier (CLLI)
of the trunk, type
>POST my trunk
where
my trunk
is the CLLI name of the trunk
33 To busy every circuit on the trunk, type
>BUSY ALL
34 To return the circuits on the trunk to service, type
>RTS ALL
35 To exit the TTP level of the MAP display, type
>QUIT ALL
Deleting a RGSIGIDX
To delete an RGSIGIDX tuple from table, some fields must not be present in
the table TRKSGRP tuple. These fields are RGSIGSYS, RGICSSI,
RGOGSSI, and RG2WSSI. This tuple points to the tuple to delete. A utility
program uses the register signaling type and the signaling system index to
check each entry in the trunk subgroup data table. If the program finds a
matching index, the system returns the common language location identifier
(CLLI). If the program does not find a matching index, the system returns
NIL_CLLI.
You can activate a change to fields RGICSSI, RGOGSSI, or RG2WSSI of a

tuple in TRKSGRP. To perform this action, MBSY and RTS each trunk in the
subgroup from the TTP level of the MAP display.
297-8021-351 Standard 05.02 May 2001

Making changes to existing RGSIGSYS tuples

The register signaling type (RGSIGTYP) of any tuple cannot change. The
value of fields other than the key, RGSIGIDX, or the selector, RGSIGTYP, can
change in the normal way. See the previous example. If the change involves
large numbers of trunks, testing of the new variables must occur on a small
subgroup first. This event must follow the method for how to define a new
RGSIGIDX.
If the parameters contain the correct values for the test subgroup, the original
RGSIGIDX tuple can change. Busy the members of the test subgroup before
you enter the members again to become members of the original subgroup.
Datafill
Datafill for table RGSIGSYS type MF3 appears in the following table.
Subfield or
RGSIGIDX see subfield Register signaling index. This field contains

subfield RSS_CHAR_VECTOR.
RSS_CHAR alphanumeric Register signaling system index. Enter the register

_ VECTOR 1 to 16 signaling index that the customer defines. This field
characters is the key to table RGSIGSYS.
RSVAR see subfield Register signaling variable area. This field contains
subfield RGSIGTYP.
RGSIGTYP MF3 Register signaling type. Enter the register signaling

type (MF3). Enter data in refinements OKPSIG,
OPULSIG, ORGHLDTM, OIDGTM, IKPTM,
IMINDIG1, IMAXDIG1, IPSHDTM1, IMINDIG2,
IMAXDIG2, IPSHDTM2, IMINDIG3, IMAXDIG3,
and IPSHDTM3.
OKPSIG 90 to 110 Outgoing KP signal duration. Enter the duration in

milliseconds of the outgoing KP signal.
OPULSIG 61 to 75 Outgoing pulse signal length. Enter the duration in

milliseconds of every signal other than KP.
Note: For MMP loads, the range is 10 to 75.

Subfield or
ORGHLDTM 180 to 300 Outgoing overall register holding time. Enter the
time in seconds that the system holds the register
for transmission of the digits.
OIDGTM 70 to 1000 Outgoing interdigital time. Enter the outgoing

interdigital time in milliseconds.
IKPTM 2 to 30 Incoming time for KP signal. Enter the time in

seconds that the trunk waits for reception of the first
digit.
IMINDIG1 1 to 14 Incoming minimum number of digits, first phase.

Enter the minimum number of digits that the trunk
can receive in the first phase.
IMAXDIG1 1 to 14 Incoming maximum number of digits, first phase.

Enter the maximum number of digits that the trunk
can receive in the first phase. The value in this field
must be greater than or equal to the value in field
IMINDIG1.
IPSHDTM1 10 to 20 Incoming phase overall holding time. Enter the

amount of time in seconds that the incoming
register waits. The incoming register waits for
reception of the maximum number of digits in the
first phase.
297-8021-351 Standard 05.02 May 2001

Subfield or
IMINDIG2 1 to 14 Incoming minimum number of digits, second phase.

can receive in the second phase.
IMAXDIG2 1 to 14 Incoming maximum number of digits, second

phase. Enter the maximum number of digits that
the trunk can receive in the second phase. The
value in this field must be greater than or equal to
the value in field IMINDIG1.
IPSHDTM2 10 to 20 Incoming phase overall holding time. Enter the

amount of time in seconds that the incoming
register waits. The incoming register waits for
reception of the maximum number of digits in the
second phase.
IMINDIG3 1 to 14 Incoming minimum number of digits, final phase.

can receive in the final phase.

Subfield or
IMAXDIG3 1 to 14 Incoming maximum number of digits, final phase.

Enter the maximum number of digits that the trunk
can receive in the final phase. The value in this field
must be greater than or equal to the value in field
IMINDIG1.
IPSHDTM3 10 to 20 Incoming phase overall holding time. Enter the time

in seconds that the incoming register waits. The
incoming register waits for reception of the
maximum number of digits in the final phase.
Datafill example
Sample datafill for table RGSIGSYS type MF3 appears in the following
example.
The example uses the following data:

the register signaling indexes are LOCRGSIGDX and TOLRGSIGDX
the register signaling type is MF3
the outgoing KP signal duration is 100 ms
the outgoing pulse signal length is 75 ms
the outgoing overall register holding time is 240 s
the outgoing interdigital time is 70 ms
the incoming time for KP signal is 15 s
the incoming minimum number of digits for the first phase is 4
the incoming maximum number of digits for the first phase is 13
the incoming overall holding time for the first phase is 15 s
the incoming minimum number of digits for the second phase is one
the incoming maximum number of digits for the second phase is three
the incoming overall holding time for the second phase is 15 s
the incoming minimum number of digits for the final phase is one
297-8021-351 Standard 05.02 May 2001

RGSIGSYS type MF3 (end)
the incoming maximum number of digits for the final phase is three
the incoming overall holding time for the final phase is 15 s
MAP example for table RGSIGSYS type MF3
RGSIGIDX
RSVAR
________________________________________________________
LOCRGSIGDX
MF3 100 85 240 80 15 4 13 15 1 3 15 1 3 15
TOLRGSIGDX
MF3 100 85 240 80 15 4 13 15 1 3 15 1 3 15
RGSIGSYS type MFCR2
MF compelled (MFC) R2 signaling

This section describes the customer variable data for register signaling type
MFCR2. The DMS-300 switching units use MFCR2.
MFCR2 interregister signals

The MFCR2 interregister protocol uses the PCM-30 digital trunk as a medium.
The MFCR2 operates at 2048 kbit/s. The MFCR2 protocol uses the PCM-30
speech channels to transmit multifrequency (MF) tones over an R2 link that
connects two international switching units.
These two switching units assign an MFCR2 tone transmitter and an MFCR2
tone receiver to each call. The transmitter sends double-frequency tone groups
that the receiver can recognize and interpret.
See the table description for table RGSIGSYS type NTRS11 for additional
information on compelled signaling.
Timeouts on MFCR2 registers

The MFCR2 registers can limit the holding time of the MFCR2 transmitter and
receiver if interregister signaling experiences an interruption. To limit the
holding time, the incoming and outgoing registers have timeout periods.
These periods are for continuous supervision of the time that the different
phases of interregister signaling take.
Timeout of outgoing MFCR2 registers

The outgoing MFCR2 register has a timeout mechanism that monitors the
following periods:
the holding time of a forward signal without an acknowledgment received
the time the opposite register takes to stop the backward signal
transmission. This transmission follows the termination of the forward
signal.
A timeout mechanism is not a requirement in the time that a sender does not
send an MF group. Allocation of the outgoing MFCR2 register only occurs
after reception of all the address digits of the called party. These digits come
from the previous trunk.
Timeout on arrival of a backward acknowledgment

Timeout supervision starts at the beginning of the transmission of a forward
MF group. The deactivation of the transmitter involved causes the system to
recognize a backward signal. This event resets the timeout supervision.
297-8021-351 Standard 05.02 May 2001

RGSIGSYS type MFCR2 (continued)
Timeout supervision starts again at the beginning of the transmission of each

forward signal.
If a timeout occurs, the switching unit returns a correct signal or audible tone,
or a signal and tone. This signal or tone informs the calling party of the fault
occurrence. The system releases the outgoing trunk and the MFCR2
transmitter or receiver for the trunk. The switching unit outputs a detailed
report over the log utility report program. The report contains information
about the digits the system sent before the timeout occurred.
Timeout on the end of backward signal transmission

The outgoing MFCR2 register has a timeout mechanism that monitors an
interval. This interval is between the end of transmission of a forward signal
and the recognition that the backward signal stopped.
If a timeout occurs, the switching unit returns an correct signal or audible tone,
or a signal and a tone. The signal or tone informs the calling party of the fault
occurrence. The system releases the outgoing trunk and the MFCR2
transmitter and receiver allocated to the trunk. The switching unit outputs a
detailed report over the log utility report program. The report contains
information about the digits sent before the timeout occurred.
Timeout of incoming MFCR2 registers

The incoming MFCR2 register has a timeout mechanism to supervise the
following periods:
the time the register waits to receive the first MFCR2 signal or the
following forward MFCR2 signal
the time that the opposite register takes to end the forward signal
transmission. This transmission follows the start of the backward signal
transmission.
Timeout on arrival of the next forward signal

The incoming MFCR2 register has a timeout mechanism that monitors an
interval. This interval is between the allocation of the incoming MFCR2
register and recognition of the first MFCR2 forward signal. The timeout
mechanism also monitors the interval between the recognition of two forward
signals in succession.
If a timeout occurs, the switching unit sends a congestion signal in a pulse

format and releases the incoming MFCR2 register. The switching unit outputs
a log utility report with detailed information about the digits received before
the timeout occurred.
Timeout on the end of forward signal transmission

The incoming MFCR2 register has a timeout mechanism that monitors an
interval. This interval is between the start of transmission of the backward
signal and the recognition that the forward signal stopped.
If a timeout occurs, the switching unit releases the incoming MFCR2 register
and waits for the Clear Forward signal from the other end. The switching unit
outputs a log utility report with detailed information about the digits the
system received before the timeout occurred.
MFCR2 register release

The system must release an outgoing MFCR2 register if the following
conditions occur:
reception of a Clear Forward line signal from the preceding trunk occurs
a timeout occurs
reception of a backward signal terminating the interregister signaling
protocol occurs
The system must release an incoming MFCR2 register if the following

conditions occur:
reception of a Clear Forward line signal occurred from the trunk that has
allocation of the MFCR2 register
a timeout occurred
transmission of a backward signal terminating the interregister signaling
protocol occurred
The outgoing and incoming switching unit passes the link-to-speech

conditions. This event follows an Address Complete signal or a Subscriber
Line Free signal. The MFCR2 registers at the two ends must disconnect before
the switching units pass to speech condition. For a passage to speech condition
to occur, the following conditions must be present:
The incoming MFCR2 register must disconnect from the link. This event
must occur in 30 ms of the recognition of the end of the last backward
signal.
The outgoing MFCR2 register must disconnect from the link. This event
must occur in 30 ms of the recognition of the end of the last backward
signal.
297-8021-351 Standard 05.02 May 2001

The outgoing switching unit speech conditions must be set up. This event
must occur 30 to 60 ms after recognition of the end of the last backward
signal.
The incoming switching unit speech conditions must be set up. This event
must occur a minimum of 75 ms after the end of transmission of the last
backward signal.
R2 timing for Australia

The register signaling type MFCR2 in table RGSIGSYS for T3MFC
Australian national system has some recommended values. These values
appear in the following table.
R2 timing for Australia (Sheet 1 of 2)
RGSISYS field Description of field Value
RGSIGIDX register signaling index AUST3MFC
RGSIGTYP register signaling type MFCR2
OXMTTM outgoing transmit time 20 s
OIDLTM outgoing idle time 20 s
OPLSTM outgoing pulse-end time 200 ms
OPSPLSTM outgoing post-pulse time 150 ms
OCMPTM outgoing compel time 360 ms
IMXWTTM incoming maximum wait time 16 s
IMXWTTM1 incoming short maximum wait time 4s
IPLSHDTM incoming pulse hold time 150 ms
IPRPLSTM incoming pre-pulse time 100 ms
IPSPLSTM incoming post-pulse time 100 ms
IPSRLSTM incoming post-release time 75 ms
ICMPTM incoming compel time 360 ms
UTRON universal tone Rx on 36 ms
UTROFF universal tone Rx off 36 ms
ICRMTTM incoming reply time 50 s

R2 timing for Australia (Sheet 2 of 2)
RGSISYS field Description of field Value
IFDGWTTM incoming first digit wait time 1s
PROTINDX multifrequency compelled (MFC) protocol 3s

index
Datafill
Datafill for table RGSIGSYS type MFCR2 appears in the following table.
Subfield or


_ VECTOR 1 to 16 signaling index that the customer defines. This key
subfield RGSIGTYP.
RGSIGTYP MFCR2 Register signaling type. Enter the signaling type

(MFCR2). Enter data in refinements OXMTTM,
OIDLTM, OPLSTM, OPSPLSTM, OCMPTM,
IMXWTTM, IMXWTTM1, IPLSHDTM, IPRPLSTM,
IPSPLSTM, IPSRLSTM, ICMPTM, UTRON,
UTROFF, ICRMTTM, and PROTINDX.
OXMTTM 10 to 50 Outgoing transmit time. Enter the maximum time in

seconds that a register waits for a backward signal.
The register waits for a backward signal after the
register sends a forward signal. If the wait time
exceeds this time, the system releases the register.
OIDLTM 15 to 60 Outgoing idle time. Enter the maximum time

between the end of a backward signal, and the start
of the next forward signal. This entry must be in
seconds. If the outgoing register cannot signal
before this time expires, the system releases the
register.
297-8021-351 Standard 05.02 May 2001

Subfield or
OPLSTM 150 to 1500 Outgoing pulse end time. Enter the time in
milliseconds that represents the correct width of a
received pulse signal.
OPSPLSTM 50 to 1000 Outgoing post pulse time. Enter the post-pulse

pause time in milliseconds. This time allows the
incoming register to be ready for the next forward
signal.
OCMPTM 10 to 2500 Outgoing compel time. Enter the outgoing compel

time in milliseconds. This time passes between the
removal of the forward signal and the detection of
the removal of the backward signal.
IMXWTTM 4 to 60 Incoming maximum wait time.. Enter the maximum

time in seconds that the incoming register waits for
reception of the next signal that is not optional. For
digit collection, use of this time occurs before
collection of the minimum number of digits is
complete. Digit analysis determines when the
collection of the minimum number of digits is
complete.
IMXWTTM1 4 to 50 Incoming short maximum wait time. Enter the

maximum time in seconds that the incoming
register waits for reception of the next optional
signal. For digit collection, use of this time occurs
after collection of the minimum number of digits.
Digit analysis determines when collection of the
minimum number of digits is complete. This time
can be less than the time in use in field IMXWTTM.
IPLSHDTM 100 to 1000 Incoming pulse hold time. Enter the duration in
milliseconds of all backward pulsed signals.

Subfield or
IPRPLSTM 100 to 1000 Incoming pre-pulse time. Enter the time in

milliseconds between two events. The first event is
the transmission of the last backward signal of a
compelled sequence. The second event is the start
of transmission of a pulsed signal by the incoming
register.
IPSPLSTM 100 to 1000 Incoming post-pulse time. Enter the time in

milliseconds that follows the transmission of a
pulsed signal. This signal indicates that the system
does not recognize any forward signals.
IPSRLSTM 75 to 500 Incoming post release time. Enter the time in

milliseconds that represents the post-release pause
time before the start of the next compelled signal.
ICMPTM 10 to 2500 Incoming compel time. Enter the time in

milliseconds that represents the period between
two events. The first event is the transmission of
the backward signal by the incoming register. The
second event is the release of the forward signal by
the outgoing register.
UTRON 24 to 180 Universal tone receiver tone on persistence. Enter

the time in milliseconds that the tone must persist
before the universal tone receiver (UTR) reports the
presence of the tone.
UTROFF 24 to 180 Universal tone receiver tone off persistence. Enter

the time in milliseconds that the tone must remain
off before the UTR reports the absence of the tone.
297-8021-351 Standard 05.02 May 2001

Subfield or
ICRMTTM 10 to 50 Incoming reply time. Enter the time after which the
incoming end sends a signal to prevent the timeout
of the outgoing end. This entry must be in seconds.
IFDGWTTM 0 to 40 Incoming first digit wait time. Enter the maximum

time in seconds that the incoming register waits for
the reception of the first digit.
The default value is 0, which means the timer does
not apply.
PROTINDX 1 to 10 Multifrequency compelled protocol index. Enter the

index into the MFCPROT table tuple used for this
protocol.
Datafill example
Sample datafill for table RGSIGSYS type MFCR2 appears in the following
example.

the register signaling index is GWMFC
the register signaling type is MFCR2
the outgoing transmit time is 30 s
the outgoing idle time is 35 s
the outgoing pulse end time is 150 ms
the outgoing post-pulse time is 150 ms
the outgoing compel time is 50 ms
the incoming maximum wait time before collection of the minimum
number of digits is 24 s
the incoming short maximum wait time after collection of the minimum
number of digits is 4 s
the incoming pulse hold time is 150 ms
the incoming pre-pulse time is 100 ms
RGSIGSYS type MFCR2 (end)
the incoming post-pulse time is 100 ms

the incoming post-release time is 75 ms
the incoming compel time is 50 ms
the UTR tone on persistence time is 36 ms
the UTR tone off persistence time is 36 ms
the incoming reply time is 50 s
the wait time for the first incoming digit is 1 s
the multifrequency compel protocol index is 1
MAP example for table RGSIGSYS type MFCR2
RGSIGIDX
RSVAR
_____________________________________________________________________
GWMFC
MFCR2 30 35 150 150 50 24 4 150 100 100 75 50 36 36 50 1 1
297-8021-351 Standard 05.02 May 2001

RGSIGSYS type NTRS03
MF pulse packet (MFPP) type 2 (MFPP-2) signaling

Installation of register signaling MFPP-2 occurs in signaling type NTRS03.
The following four types of register signaling occur in the local CIS network:
decadic
MF shuttle
MFPP-1 (MF11, MF6)
MFPP type 2 (MFPP-2) (700 Hz, 1100 Hz)
The four types of register signaling appear in the following figure.
Register signaling types in local CIS network
Toll Toll Toll

ARM-20 AMTC-2, 3 AMTC-KE (E)
MF shuttle MF shuttle
Decadic MFPP-1 Decadic MFPP-1
Decadic Decadic
Tandem
crossbar or electronic office
Decadic
Decadic MF shuttle MFPP-1 or
MFPP-2
Local Decadic Local Decadic Local Local

step-by- step-by- crossbar or crossbar or
step office step office electronic MF shuttle electronic
office office
The MFPP-2 configuration between local, tandem, and toll switches appears
in the following figure.
RGSIGSYS type NTRS03 (continued)

MFPP-2 configuration
DMS as toll AMTC-KE (E) office
MFPP-2
T1
Tandem electronic or crossbar

office
MFPP-2
T1
Local crossbar or electronic

office
The frequency groups available with NTRS03 signaling appear in the

following table..
Frequency combinations (Sheet 1 of 2)
Signal Frequencies (Hz)
MF1 700 + 900
MF2 700 + 1100
MF3 900 + 1100
MF4 700 + 1300
Note 1: The duration of each frequency group is 50 5 ms.

Note 2: The duration of each pause between MF signals is 60 5 ms.
297-8021-351 Standard 05.02 May 2001

Frequency combinations (Sheet 2 of 2)
MF5 900 + 1300
MF6 1100 + 1300
MF7 700 + 1500
MF8 900 + 1500
MF9 1100 + 1500
MF10 1300 + 1500
MF11 700 + 1500
Note 1: The duration of each frequency group is 50 5 ms.

The meanings of the frequency groups for use in forward and backward
directions are:
Forward
MF1 to MF10
digits
Backward
MF2
request, automatic number identification (ANI)
700 Hz
congestion
1100 Hz
release register or wait for operator answer
Note: For BCS36, the system does not support detection of the
congestion case after the first packet. The system does not send the 700
Hz tone.
Enter the delay in field DLYMFPP2 before you send the first request (MF2)
signal.
Enter the duration of 700 and 1100 Hz in field SGNLTIME.
Datafill
Datafill for table RGSIGSYS type NTRS03 appear in the following table.
Subfield or

RSS_CHAR_ alphanumeric Register signaling system index. Enter the

VECTOR (1 to 16 customer defined register signaling index.
characters) This field is the key to table RGSIGSYS.
RSVAR see subfield Register signaling variable area. This field

contains subfield RGSIGTYP.
297-8021-351 Standard 05.02 May 2001

Subfield or
RGSIGTYP NTRS03 Register signaling type. Enter the signaling

type (NTRS03) and enter data in refinement
DIR.
DIR C or OG Direction. Enter IC for incoming trunks and

enter data in the following refinements:
MF2TIME
MINPAUSE
MAXPAUSE
MINMF
MAXMF
SGNLTIME
REPLTIME
DLYMFPP2
These refinements are in the following section
DIR = IC..
Enter OG for outgoing trunks. Enter data in
the following refinements:
MFTIME
PAUSTIMEF
MINMF2
MAXMF2
MINSGNL
MAXSGNL
REPLTIME
MFWAIT
INTLDGT
These refinements appear in the following
section DIR = OG..
DIR = IC
If the entry in field DIR is IC, enter data in the following refinements:
MF2TIME
MINPAUSE
MAXPAUSE
MINMF
MAXMF
SGNLTIME
REPLTIME
DLYMFPP2
Subfield or
MF2TIME 0 to 31 Signal MF2 time. Enter the duration of signal MF2

for incoming DMS signals. Enter the time in units of
10 ms.
The default is 5 (50 ms).
MINIPAUSE 0 to 15 Minimum pause time. Enter the minimum filtering

time for detection of each pause between MF
signals. Enter the time in units of 10 ms.
MAXPAUSE 0 to 15 Maximum pause time. Enter the maximum filtering

time for detection of each pause between MF
signals. Enter the time in units of 10 ms. The entry
in this field must be greater than the entry in field
MINPAUSE. The pause after an MF signal can
exceed the value in field MAXPAUSE. When
condition occurs this pause indicates the end of the
digits packet.
MINMF 0 to 15 Minimum duration. Enter the minimum filtering time

for detection of MF signals. Enter the line in units of
10 ms.
297-8021-351 Standard 05.02 May 2001

Subfield or
MAXMF 0 to 15 Maximum duration. Enter the maximum filtering

time for detection of MF signals in units of 10 ms.
The entry in this field must be greater than the entry
in field MINMF.
The nominal value is 10.
SGNLTIME 0 to 6000 Signal time. Enter the duration to send 700 Hz or

1100 Hz signals in units of 10 ms.
REPLTIME 0 to 6000 Reply time. Enter the timer value for the extended
multiprocessor system (XMS)-based peripheral
module (XPM). Enter this value to wait for a signal
after you send an MF2 signal in units of 10 ms.
The default is 1000 (10 000 ms).
DLYMFPP2 0 to 100 Delay multifrequency pulse packet type 2. Enter the

timer value for the incoming exchange. Enter this
value to wait before the system sends the first MF2
signal after transmission of a seize (SZA) line signal.
Enter the time in units of 10 ms.
DIR = OG
If the entry in field DIR is OG, enter data in the following refinements:
MFTIME
PAUSETIME
MINMF2
MAXMF2
MINSGNL
MAXSGNL
REPLTIME
MFWAIT
INTLDGT
Subfield or
MFTIME 0 to 10 Minimum signal time. Enter the minimum filtering

time for detection of 700 Hz or 1100 Hz signals.
PAUSETIME 0 to 15 Pause. Enter the duration to send MF2 (request)

signal. Enter the time in units of 10 ms.
The default value is 6 (60 ms).
MINMF2 0 to 31 Minimum time for MF2. Enter the minimum filtering

time for detection of MF2 signals. Enter the time in
units of 10 ms.
MAXMF2 0 to 31 Maximum time for MF2. Enter the maximum filtering

time for detection of MF2 signals. Enter the time in
units of 10 ms. The entry in this field must be greater
than the entry in field MINMF2.
MINSGNL 0 to 15 Minimum signal time. Enter the minimum filtering

MAXSGNL 0 to 15 Maximum signal time. Enter the maximum filtering

Enter the time in units of 10 ms. The entry in this
field must be greater than the entry in field
MINSGNL.
The default is12 (120 ms).
REPLTIME 0 to 6000 Reply time. Enter the timer value for the XPM from
an XMS to wait for an MF2 signal. Enter the time in
units of 10 ms.
The default is 1000 (10 000 ms).
297-8021-351 Standard 05.02 May 2001

RGSIGSYS type NTRS03 (end)
Subfield or
MFWAIT 0 to 100 Multifrequency wait. Enter the duration delay before

the system sends the packet after the system
receives every MF2 signal. Enter the time in units of
10 ms.
INTLDGT 1 to 2 International digit. Enter the code value that

specifies the number of digits for automatic
international call code.
The default is 2, which indicates the current network.
Datafill example
Sample datafill for table RGSIGSYS type NTRS03 appears in the following
example.
MAP example for table RGSIGSYS type NTRS03
RGSIGIDX
RSVAR
_____________________________________________________________________
OGMYMFPP
NTRS03 OG 5 6 0 5 7 12 1000 25 2
R1 modified signaling
NTRS04.
The NTRS04 signaling is a modified R1 register signaling for use in the

Caribbean expansion project. The R1 register signaling is signaling type MF3.
Application of R1 modified signaling can occur for automatic and

semi-automatic operation of one-way and two-way circuits. This condition
occurs for international areas.
Descriptions and functions for R1 modified signals appear in the following

sections:
KP (start of pulsing) signal (sent in forward direction)
The system sends this register signal after the recognition of the Start
Dialing signal. The system uses the KP to prepare the incoming
multi-frequency register for the reception of interregister signals. The KP
indicates that the call is a terminating call.
KP2 (start of pulsing) signal (sent in the forward direction)
The system sends this register signal after the system recognizes the Start
Dialing signal. The system uses the KP2 to prepare the incoming
multi-frequency register for the reception of interregister signals that
follow. The KP2 differs from the KP signal. The KP2 indicates a transit
call that is an intercontinental call.
Address signal (sent in the following direction)
The system sends this register signal to indicate one decimal element of
information for the number of the called party. The range for this
information is 0-9. The system sends a sequence of address signals for
each call.
ST (end of pulsing) signal (sent in the forward direction)
The system sends this register signal to indicate that additional address
signals do not follow.
Code11 signal (sent in the forward direction)
297-8021-351 Standard 05.02 May 2001

The system sends this register signal to indicate that the system routes the
incoming call to an operator at the terminating exchange.
Code12 signal (sent in the forward direction)
The system sends this register signal to indicate that the system routes the
incoming call to a special international operator. These operators handle
special calls, like pre-booked calls.
Digit collection by the incoming register occurs in three phases for R1

modified signaling. Digit collection occurs after the start of pulsing (KP)
signal.
The first phase collects the first set of digits. The second phase collects the
next set of digits. The final phase collects the digits that remain, and the
end-of-pulsing (ST) signal.
The outpulsing signaling format is:
KP (or KP2) + country code + language digit (or discrimination

digit) + Code11 (or Code12) + XXXX (or national number) + ST
where:
XXXX can be 1, 2, 3, or 4 digits.
Datafill
Datafill for table RGSIGSYS type NTRS04 appears in the following table.
Subfield or


_ VECTOR (1 to 16 signaling index that the customer defines. This field
characters) is the key to table RGSIGSYS.
subfield RGSIGTYP.

Subfield or
RGSIGTYP NTRS04 Register signaling type. Enter the signaling type

(NTRS04). Enter data in the following refinements:
OKPSIG
OKP2SIG
OPULSIG
ORGHLDTM
OIDGTM
IKPTM
IMINDIG1
IMAXDIG1
IPSHDTM1
IMINDIG2
IMAXDIG2
IPSHDTM2
IMINDIG3
IMAXDIG3
IPSHDTM3
OKPSIG 90 to 110 Outgoing KP signal duration. Enter the duration of

the outgoing KP signal. Enter the duration in
milliseconds.
OKP2SIG 90 to 110 Outgoing KP2 signal duration. Enter the duration of

the outgoing KP2 signal. Enter the duration in
milliseconds
OPULSIG 61 to 75 Outgoing pulse signal length. Enter the duration of

signals other than KP and KP2. Enter the duration
in milliseconds.
297-8021-351 Standard 05.02 May 2001

Subfield or
ORGHLDTM 180 to 240 Outgoing overall register holding time. Enter the
time that the system holds the register for
transmission of the digits. Enter the time in
seconds.
OIDGTM 61 to 75 Outgoing interdigital time. Enter the outgoing

interdigital time, the time between digits. Enter the
time in milliseconds.
IKPTM 10 to 20 Incoming time for KP signal. Enter the time that the
trunk waits for the reception of the KP, or KP2,
signal. Enter the time in seconds.
IMINDIG1 0 to 13 Incoming minimum number of digits, phase one.

Enter the minimum number of digits that the register
can receive in phase one.
IMAXDIG1 0 to 13 Incoming maximum number of digits phase one.

Enter the maximum number of digits that the
register can receive in phase one. The value in this
field must be greater than or equal to the value in
field IMINDIG1.

Subfield or
IPSHDTM1 10 to 20 Incoming phase overall holding time, phase one.

Enter the time that the incoming register waits to
receive the maximum number of digits in phase
one. Enter the time in seconds.
IMINDIG2 0 to 13 Incoming minimum number of digits, phase two.

can receive in phase two.
IMAXDIG2 0 to 13 Incoming maximum number of digits, phase two.

register can receive in phase two. The value in this
field must be greater than or equal to the value in
field IMINDIG2.
IPSHDTM2 10 to 20 Incoming Phase Overall Holding Time, Phase Two.

two. Enter the time in seconds.
IMINDIG3 0 to 13 Incoming minimum number of digits, phase three.

can receive in phase three.
297-8021-351 Standard 05.02 May 2001

Subfield or
IMAXDIG3 0 to 13 Incoming maximum number of digits, phase three.

register can receive in phase three. The value in
this field must be greater than or equal to the value
in field IMINDIG3.
IPSHDTM3 10 to 20 Incoming phase overall holding time, phase three.

three. Enter the time in seconds.
Datafill example
example.
The following data appears in the example:

the register signaling index is CEP1
the register signaling type is NTRS04
the outgoing KP signal duration is 100 ms
the outgoing KP2 signal duration is 100 ms
the outgoing pulse signal length is 68 ms
the outgoing overall register holding time is 240 s
the outgoing interdigital time is 68 ms
the incoming time for KP signal is 20 s
the incoming minimum number of digits for phase one is 4
the incoming maximum number of digits for phase one is 13
the incoming overall holding time for phase one is 20 s
the incoming minimum number of digits for phase two is 1
the incoming maximum number of digits for phase two is 3
the incoming overall holding time for phase two is 20 s
the incoming minimum number of digits for phase three is 1

the incoming maximum number of digits for phase three is 3
the incoming overall holding time for phase three is 20 s
RGSIGIDX
RSVAR
_____________________________________________________________________
CEP1
NTRS04 100 100 68 240 68 20 4 13 20 1 3 20 1 3 20
297-8021-351 Standard 05.02 May 2001

E and M signaling
NTRS05.
The system uses NTRS05 for incoming, outgoing, and two-way trunks that use
dial pulse signaling. An example of dial pulse signaling is E and M or loop
disconnect signaling.
E and M trunks
For trunks that use E and M signaling, the signals come from on-hook and
off-hook conditions. These conditions are of the telephone set of the
subscriber. The following table provides the conditions for the E and M leads
on the analog side of the multiplexer (channel bank).
E and M leads
Condition M lead E lead
On hook Open Open
Off hook Earth Earth
For trunks that use E and M signaling, the system converts the digital codes in
time slot 16 of the PCM-30 system. The system converts these signals to E and
M signals in the channel bank. The system also converts E and M signals to
loop disconnect for step-by-step exchange by an appropriate converter.
The system digitizes the line signals E and M type. The system encodes these
signals in time slot 16 of the PCM-30 system. The register signals are decadic
dial pulses that the system transmits and receives in time slot 16. The system
transmits the decadic dial pulses on the M lead for outpulsing from DMS. The
system also conveys these pulses on the E lead for reception from the
step-by-step.
The system transmits and receives digital codes through the A-bit of the
ABCD-bit facility. This action occurs in time slot 16 of the PCM-30 system.
The primary multiplexer converts the outgoing digital codes to M-lead analog
signals. The primary multiplexer is the channel bank. The primary
multiplexer also converts the incoming E-lead signals to digital codes for the
DMS switch. The B-, C-, and D-bits do not change. The signaling system
does not use these bits.
Loop disconnect trunks

Loop disconnect transmits supervisory and address information on a trunk
circuit. Use of loop disconnect can occur in the interworking between SXS
equipment and the DMS-100 central office.
Signals come from the on hook and off hook conditions of the telephone set of
the subscriber. This process causes a series of loops and disconnections. When
the subscriber lifts the receiver that is off-hook a loop forms. This loop allows
the current to flow. Each dialed digit causes a sequence of on-hook, (break)
pulses that represent the digit.
The system transmits and receives the digital codes through the A-bit of the
ABCD-bit facility. This action occurs in time slot 16 of a PCM-30 system. A
primary multiplexer converts the outgoing digital codes to analog signals. The
primary multiplexer also converts analog signals to digital codes for incoming
signals. A primary multiplexer is the channel bank. This signaling system
does not change or use B-,C-, and D-bits.
Trunks with other types of dial pulse signaling

Trunks with dial pulse signaling other than E and M or loop disconnect
signaling use the A-bit of the digital codes. These codes are in time slot 16 of
the PCM-30 system. The trunks use the A-bit to convey the line and digit
signals like the signals from the previous description.
Datafill
Subfield or


VECTOR (1 to 16 register signaling index the customer defines.

297-8021-351 Standard 05.02 May 2001

Subfield or

(NTRS05). Enter data in the following
refinements:
IDLEPOL
Direction
SIGDIR
IRMXIDT
IRMXINT
IRMNDGT
OSPCTBRK
OSMNIDP
IDLEPOL 0 to 1 Idle A-bit polarity. Enter the polarity of the A-bit

when idle.
SIGDIR C, OG, 2W Signal direction. If the signal direction is incoming.

Enter IC. Enter data in refinements IRMXIDT,
IRMXINT, IRMNDGT, and FLTRTIME.
If the signal direction is outgoing, enter OG. Enter
data in refinements OSPCTBRK, OSMNIDP,
PPS, and OPLSDLAY.
If the signal direction is two-way, enter 2W. Enter
data in the following refinements:
IRMXIDT
IRMNXINT
IRMNDGT
FLRTIME
OSPCTBRK
OSMNIDP
PPS
OPLSDLAY

Subfield or
IRMXIDT 500 to 30000 Incoming receive maximum initial digit time. If the
entry in field SIGDIR is IC or 2W, enter data in this
refinement. Enter the maximum time that the
register waits for the first digit. Enter the time in 2
ms increments.
The default value is 2000 (4 s).
IRMXINT 500 to 30000 Incoming receive maximum interdigit time. If the

entry in field SIGDIR is IC or 2W, enter data in this
refinement. Enter the maximum time, in 2-ms
increments, that the register waits between digits.
The default value is 2000 (4 s).
IRMNDGT 1 to 14 Incoming receive number of digits. If the entry in

field SIGDIR is IC or 2W, enter data in this
refinement. Enter the expected number of digits to
receive.
FLTRTIME 1 to 20 Filter time. If the entry in field SIGDIR is IC or 2W

enter data in this refinement. Enter the minimum
signal duration time for the detection of make and
break signals. Enter the Time in 2 ms increments.
OSPCTBRK 20 to 75 Outgoing send percent break. If the entry in field

SIGDIR is OG or 2W, enter data in this refinement.
Enter the percentage of break that the system
uses to derive the make break times. This
percentage is the make break ratio.
OSMNIDP 100 to 750 Outgoing send minimum interdigital pause. If the

entry in field SIGDIR is OG or 2W, enter data in
this refinement. Enter the minimum time for the
interdigital pause to separate digits. Enter the
time in 2 ms increments.
297-8021-351 Standard 05.02 May 2001

Subfield or
PPS 7 to 22 Pulse rate in pulses per second. If the entry in

field SIGDIR is OG or 2W, enter data in this
refinement. Enter the pulse rate in pulses for each
second.
OPLSDLAY 0 to 6000 Outpulse delay. If the entry in field SIGDIR is OG

or 2W, enter data in this refinement. Enter the
time delay between the seizure of an outgoing DP
trunk and the start of outpulsing. Enter the time in
units of 10 ms.
The default value is 0 (zero).
Datafill example
Sample datafill for table the RGSIGSYS type NTRS05 feature appear in the
following example.
The following data appear in this example:

the register signaling index is EMSIGNAL
the signaling direction is incoming
the maximum time to wait for an initial digit is 4 s
the maximum time to wait between digits is 2 s
the expected number of digits is 13
the filter time is 8 ms
RGSIGIDX
RSVAR
_____________________________________________________________________
EMSIGNAL
NTRS05 IC 2000 1000 13 8
297-8021-351 Standard 05.02 May 2001

MF pulsed signaling
NTRS10.
Use of NTRS10 occurs for multi-frequency pulsed (MFP) operator trunks for
the Chinese network. The MFP register protocol uses the incoming PCM-30
speech channels. The MFP uses these channels to receive R2 tones over an
MFP link. This link connects an operator board and a DMS-100/200. Use of
NTRS10 occurs over dedicated incoming operator trunks. The NTRS10 is a
non-compelled signaling system that uses R2 frequencies.
The following two types of incoming MFP operator trunks are in use for
signaling type NTRS10:
SF (single frequency)/MFP incoming trunk from a remote semi-automatic
toll operator (CH04)
DC (direct current)/MFP incoming trunk from a local manual toll operator
(CH09)
Datafill
Field descriptions
Subfield or
RGSIGIDX see subfield Register signaling index This field contains

RSS_CHAR_ alphanumeric Register signaling system index Enter the register

VECTOR (1 to 16 signaling index that the customer defines. This
characters) field is the key to table RGSIGSYS.
RSVAR see subfields Register signaling variable area This field

RGSIGTYP NTRS10 Register signaling type Enter the signaling type

(NTRS10).
Datafill example
Sample datafill for table the RGSIGSYS type NTRS10 feature appear in the
following example.
This example uses register signaling index CHINA2.
RGSIGIDX
RSVAR
_____________________________________________________________________
CHINA2 NTRS10
297-8021-351 Standard 05.02 May 2001

MFC R2 signaling
NTRS11.
The NTRS11 provides the timing values for trunks that use R2 signaling in
World Systems DMS-100 and DMS-200 switching units.
China uses this signaling type for the Chinese national variant of the
Consultative Committee on International Telephony and Telegraphy (CCITT)
R2 signaling system.
The R2 is a compelled trunk register signaling system with specifications that

CCITT defines. The primary use of R2 is as an international signaling protocol
between gateway exchanges. Countries can define variants for use in national
networks.
Compelled signaling
Compelled register signaling occurs between a forward register and a
backward register at opposite ends of a link between exchanges. The registers
communicate through a two-out-of-N inband multi-frequency code, where the
value of N is normally six. The frequencies that the register uses in the forward
and backward directions are different. A maximum of 15 separate signals are
available in each direction, where N equals 6. The register uses these signals
to convey information like the number of the called subscriber. These signals
also convey route information, call charges, or the availability of switching
equipment in the network. The correct meaning associated with a signal can
vary according to the position of the signal in the signaling sequence.
Register signaling is complete when the terminating office receives the

information that the office requires to route the call. Register signaling is
complete when a backward signal to connect pulse code modulation (PCM)
informs the originating office. If the terminating office cannot complete the
call, the register sends a backward signal. This signal indicates the reason the
call cannot complete and register signaling terminates.
The compelled cycle takes place in the following order (See the following
figure Compelled signaling sequence).
1. After the seizure of the outgoing link, the forward register sends the first
forward signal (1). The forward register connects a forward
multi-frequency tone.
2. The backward register in the next exchange detects the forward signal (2).
The register determines the meaning. In response, the register connects a
backward multi-frequency tone to send a backward signal (3). The
backward signal acts as an acknowledgment to the forward signal. This

backward signal can provide additional information.
3. The forward register detects the backward signal (4). The register
determines the meaning of the signal. In response, the register
disconnects the forward MF tone to remove the forward signal (5).
297-8021-351 Standard 05.02 May 2001

4. The backward register detects the end of the forward signal (6). In
response, the register disconnects the backward MF tone to remove the
backward signal (7).
5. The forward register detects the end of the backward signal (8). The
register can send the next forward signal (9).
Compelled signaling sequence
Backward register
Tone on
Tone off
2 3 6 7
Forward register
Tone on
Tone off
1 4 5 8 9
1 Forward register sends the first forward signal.
2 Backward register detects the presence of the forward signal.
3 Backward register sends backward acknowledgment signal.
4 Forward register detects backward acknowledgment signal.
5 Forward register removes forward signal.
6 Backward register detects end of forward signal.
7 Backward register removes acknowledgment signal.
8 Forward register detects end of backward signal.
9 Forward register sends the next forward signal.
For some conditions, the backward register must send a fixed duration, or
pulsed, signal. The backward register must send the signal without earlier
reception of forward signal. This action occurs if the backward register
acknowledges the last forward signal and cannot complete the call. This action
occurs if the register does not receive additional forward signals. The pulsed
signal lasts for a specified length of time. The next forward signal
acknowledges this signal.
Compelled signal timing

The timing for compelled signaling appears for the forward and backward
registers in the following figure Timing for compelled signaling.
297-8021-351 Standard 05.02 May 2001

Timing for compelled signaling
Backward register
Tone on
Tone off
T1 T1
Forward register
Tone on
Tone off
T2
T2
T3
T1 This value represents the maximum time interval between two forward signals in succession.
The range that CCITT recommends is 4 to 24 s with a default value of 15 s. Use a minimum timing
value for this interval if digit analysis is not in use. Use a minimum timing value with protocols that
do not have an End of Digits signal.
T2 This value represents the maximum time interval over which a forward signal can connect during
compelled signaling. The system removes a forward signal on the detection of a backward signal.
This timer makes sure that the forward register detects a failure by the backward register to connect
an acknowledgment tone. The recommended range for this interval is 12 to 18 s, with a default
value of 15 s.
T3 This value represents the maximum time interval between the end of a forward signal and the
end of the backward acknowledgement signal. This timing makes sure that the forward register
detects a failure by the backward register to remove the acknowledgment tone. The recommended
value for this interval is greater than or equal to 24 s.
Pulsed signal timing

The timing for the transmission and reception of pulsed signals appears in the
following figure Timing for pulsed signaling.

Timing for pulsed signaling
Backward register
T5
Tone on
Tone off
T4 T6
Forward register
Tone on
Tone off
T7 T8
T4 This time interval represents the minimum delay between two points. The two points are the end
of the last signal of a compelled cycle and the start of a pulsed signal by the backward register. The
recommended minimum value is 100 ms.
T5 This time value represents the duration of a backward pulsed signal. The recommended timing
value is 100 ms to 200 ms, with default value of 150 ms.
T6 This time value represents the duration of the post-pulse pause during which the backward
register recognizes forward signals. The recommended timing value for this interval is T6 >= 300 (
100 ms) - T5. Use a value of 900 ( 180 ms) - T5 if communication is over a satellite link.
T7 This time value places a limit on the duration of a received pulsed signal. The backward register
must remove the pulsed signal. This restriction makes sure that the forward register detects a
failure by the backward register to perform this action. This time interval is in addition to the time
intervals that CCITT recommends. This time interval can be a sanity timer for the forward register
during the reception of pulsed signals. The default value for this interval is 1 s.
T8 This time value represents the length of a post-pulse pause for the outgoing (forward) register
during which the register does not send a forward signal. This timing interval is in addition to the
timing intervals that CCITT specifies. The default value for this interval is 300 ms.
297-8021-351 Standard 05.02 May 2001

Datafill
Datafill for table RGSIGSYS type NTRS11 appear in the following table.
Subfield or


VECTOR (1 to16 register signaling index that the customer defines.


(NTRS11). Enter data in the following
refinements:
OGMXTON
OGMXTOFF
OGRMXPLS
OGPSTPLS
ICMXISIG
ICMXISIG
ICPREPLS
ICPLSTM
ICPSTPLS
ICMXFTON
ICPSTCMP
OGPREPLS

Subfield or
OGMXTON 0 to 12000 Outgoing maximum forward tone on. Enter the

maximum time interval in units of 10 ms between
two events. The first event is the connection of a
forward tone by the outgoing forward register. The
second event is the detection of a backward
acknowledgment tone. This interval applies to a
forward register. The T2 in figure Timing for
compelled signaling, found in this document,
represents this interval.
OGMXTOFF 0 to 12000 Outgoing maximum forward tone off. Enter the

maximum time interval in units of 10 ms between
two points. The first point is the end of the tone
that the forward register sends. The second point
is the end of the backward acknowledgment tone.
The T3 in the figure Timing for compelled
signaling, found in this document, represents this
interval.
OGRMXPLS 0 to 12000 Outgoing received maximum pulse length. Enter

the maximum pulse duration in units of 10 ms of a
received pulsed signal. This interval applies to a
forward register. The T7 in the figure Timing for
pulsed signaling, found in this document,
OGPSTPLS 0 to 12000 Outgoing forward post-pulse pause. Enter the

time interval in units of 10 ms. The forward
register cannot send a forward signal after the
register receives a pulsed signal during the 10 ms
intervals. The T8 in the figure Timing for pulsed
signaling, found in this document, represents this
interval.
297-8021-351 Standard 05.02 May 2001

Subfield or
ICMXISIG 0 to 12000 Incoming maximum intersignal time. Enter the

maximum interval in units of 10 ms between two
points. The first point is the end of a backward
signal. The second point is the detection of the
next forward signal. This interval applies to a
backward register. The T1 in the figure Timing for
compelled signaling, found in this document,
ICPREPLS 0 to 12000 Incoming pre-pulse pause. Enter the interval in

units of 10 ms between two points. The first point
is the end of the last signal of a compelled cycle.
The second point is the start of a pulsed signal.
The register does not recognize a forward signal
during this time. The T4 in the figure Timing for
pulsed signaling, found in this document,
ICPLSTM 0 to 12000 Incoming pulse duration. Enter the duration in

units of 10 ms of a pulsed backward signal. This
interval applies to a backward register. The T5 in
the figure Timing for pulsed signaling, found in
this document, represents this interval.
ICPSTPLS 0 to 12000 Incoming post pulse pause. Enter the time interval
in units of 10 ms. The register does not recognize
forward signals during these intervals. This
interval applies to the backward register. The T6
in the figure Timing for pulsed signaling, found in
this document, represents this interval.

Subfield or
ICMXFTON 0 to 12000 Incoming maximum forward tone on. Enter the

maximum time in units of 10 ms for the register to
receive a forward signal. This process makes
sure that the backward register detects a failure of
the forward register to remove the tone. This
timing is like the timing in field OGMXTON. This
timing applies to a forward register.
ICPSTCMP 0 to 12000 Incoming pause after compelling. Enter the

minimum time in units of 10 ms for the register to
delay after compelling stops before line signaling
can resume.
OGPREPLS 0 to 12000 Outgoing pre-pulse duration. Enter the maximum

time in units of 10 ms that the forward register
waits for a pulse from the backward register after
the end of the last signal of a compelled cycle.
This value controls the time the outgoing register
waits to receive a backward signal. This timing is
like the timing in field ICPREPLS. This timing
applies to a forward register.
Datafill example
example.

the register signaling index is R2TRK
the maximum tone-on signal for a forward signal is 15 s
the maximum tone-off signal for a forward signal is 24 s
the maximum duration of a received pulsed signal is 300 ms
the post pulse pause time is 300 ms
the maximum inter-signal time for a received forward signal is 15 s
297-8021-351 Standard 05.02 May 2001

the delay between the end of transmission of the last signal of a compelled
cycle and the start of transmission of a pulsed signal is 100 ms
the duration of the pulsed backward signal is 150 ms
the duration of the post pulse pause is 200 ms
the maximum time at which a register can receive a forward signal is 60 s
the minimum time after compelling stops before line signaling can resume
is 800 ms
the forward register waits for a pulse from the backward register after
compelling stops for a maximum time of 60 s
RGSIGIDX
RSVAR
_____________________________________________________________________
R2TRK
NTRS11 1500 2400 30 30 1500 10 15 20 6000 80 6000
Socotel compelled trunk register signaling

The customer variable data for register signaling type NTRS12 appears in this
section.
The NTRS12 provides the timing values for trunks through the Socotel register
signaling system. This signaling system is for World Systems DMS-100 and
DMS-200 switching units.
Socotel is a compelled trunk register signaling system. Socotel is a national

signaling system. Each operating company can define variants for the
operating company. The operating company defines these variants so that the
Socotel in one country is not compatible with the Socotel of another country.
Compelled signaling
A compelled register signaling system describes the method to convey
information between registers at each end of a trunk. The signaling is in band
tones that the system selects on a two-out-of-six arrangement. Each
information tone contains two component frequencies of a possible set of six.
The two component frequencies are not the same. Socotel uses the following
frequencies: 700, 900, 1100, 1300, 1500, 1700, and 1900 Hz.
Each defined signal has a assigned meaning based on the use of the signal. To
make sure that information has secure transfer, the system uses compelling. A
single frequency tone is the control or checking frequency (FC). The single
frequency tone cannot be part of the signals. This condition acknowledges
each signal sent in either direction. The basic Socotel compelling cycle
appears in the figure on the following page.
297-8021-351 Standard 05.02 May 2001

Basic Socotel compelling cycle
Tone on
Signal
Tone off
1 4 5 8
Tone on
Check frequency
Tone off
2 3 6 7
Sequence of events:
1 System sends the signal, forward or backward.
2 Receiving register detects signal.
3 System sends check frequency as acknowledgement.
4 System detects check frequency.
5 System removes signal.
6 System detects removal of signal.
7 System removes check frequency.
8 System detects removal of check frequency.
The system must exchange many signals to convey all the address, control, and
status information for call setup. The compelling cycle repeats for each signal.
This cycle repeats forward or backward.
Register signaling ends when the terminating office receives the information
needed to route the call. Register signaling ends when the terminating office
identifies and transmits the status of the calling line to the originating office.
Compelling cycle timing

The timing for compelled cycles in Socotel appears in the following figure.
Socotel compelling timing parameters
MAXCYCLE
ICMXISIG
Tone on
Signal Signal
Tone off
MAXFC
OGMXISIG
Tone on
Check frequency Check frequency
Tone off
Note: See the Field descriptions section for an explanation of

fields MAXCYCLE, ICMXISIG, MAXFC, and OGMXISIG.
Datafill
Subfield or
RGSIGIDX see subfield Register signaling index. This field contains subfield
RSS_CHAR_VECTOR.
RSS_CHAR alphanumeric Register signaling system index. Enter the

_ VECTOR 1 to 16 customer defined register signaling index. This key
Note: The times in fields MAXCYCLE, MAXFC, ICMXISIG and OGMXISIG, do not include the
recognition time that the universal tone receiver (UTR) requires. The system can ignore this value.
297-8021-351 Standard 05.02 May 2001

Subfield or
subfield RGSIGTYP.

(NTRS12) and enter data for refinements
MAXCYCLE, MAXFC, ICMXISIG, OGMXISIG, and
FC.
MAXCYCLE 0 to 6000 Maximum compelled cycle time. Enter the

maximum time interval in units of 10 ms for a
complete compelled cycle, forward or backward.
The switching unit that initiates the cycle uses this
time. The timing starts when the system sends an
information signal. The timing stops when the
system detects the removal of the check frequency
(FC).
MAXFC 0 to 6000 Maximum checking frequency transmission time .

Enter the maximum time interval in units of 10 ms
over which the FC can transmit. The time starts on
reception of an information element, also the start
of transmission of the FC. The time stops on
removal of the signal, and also the removal of the
transmission of the FC.
ICMXISIG 0 to 6000 Incoming maximum time interval for a forward

information signal. Enter the maximum time that an
incoming trunk waits for a forward information
signal from the originating switching unit. Enter this
time in units of 10 ms. This time starts when the
previous compelling cycle ends and represents the
maximum time between signals allowed.

Subfield or
OGMXISIG 0 to 6000 Outgoing maximum time interval for a backward

information signal. Enter the maximum time that an
outgoing trunk waits for a backward information
signal from the terminating switching unit. Enter
this time in units of 10 ms. This time starts when the
previous compelling cycle ends and represents the
maximum time between signals allowed.
FC 1700 or 1900 Check frequency. Enter the frequency in hertz of

the FC used during Socotel register signaling.
Assign this field according to the Socotel signaling
in use. Enter 1900 Hz for Morocco or 1700 Hz for
Spain.
Datafill example
example.
This example uses register signaling type NTRS12, Socotel compelled

signaling for World Systems DMS-100 and DMS-200 switching units.
The register signaling index is SOCTRK1.
The register signaling type is NTRS12.
The maximum compelled cycle time is 5 s.
The maximum transmission time for the check frequency is 5 s.
The maximum time that an incoming trunk waits for a forward information
signal from the originating switch is 10 s.
The maximum time that an outgoing trunk waits for a backward
information signal from the termination switch is 20 s.
The check frequency is 1900 Hz.
297-8021-351 Standard 05.02 May 2001

RGSIGIDX
RSVAR
_____________________________________________________________________
SOCTRK1
NTRS12 500 500 1000 2000 1900
MF pulse packet (MFPP) type 1 (MFPP-1)

Implementation of register signaling MFPP-1 is in signaling type NTRS14.
Another name for signaling type NTRS14 is NTRS06.
Four types of register signaling are in the local CIS network. These four types
appear in the following figure.
Decadic
MF shuttle
MFPP-1 (MF11, MF6)
MFPP type 2 (MFPP-2) (700 Hz, 1100 Hz)
signaling types in local CIS network
Toll Toll Toll

ARM-20 AMTC-2, 3 AMTC-KE (E)
MF shuttle MF shuttle
Decadic MFPP-2 Decadic MFPP-1
Decadic Decadic
Tandem
crossbar or electronic office
Decadic
Decadic MF shuttle MFPP-1 or
MFPP-2
Local Decadic Local Decadic Local Local

step-by- step-by- crossbar or crossbar or
step office step office electronic electronic
MF shuttle
office office
The DMS can be positioned instead of local or toll exchange.
A switch from MF shuttle to MFPP-1 signaling is necessary during the

following call setup. This call setup is from outgoing exchange to the toll
AMTC-KE (E) through the tandem office. The switch is not necessary for
direct calls from local to toll switch.
297-8021-351 Standard 05.02 May 2001

The incoming switch starts the register signaling. The outgoing switch waits
until the switch receives the signal from the incoming switch. The system
sends the called and calling digits with category information. The signaling
starts with MF shuttle register signaling (MFS) between local and tandem
exchanges. Then the signaling switches to MFPP-1 register signaling for local
to toll register signaling.
The MFPP-1 configuration between local, tandem, and toll switches appears
in the following figure MFPP type 1 configuration.
MFPP type 1 configuration
DMS as toll AMTC-KE (E) office

MFPP-1
MFPP-1
MFPP-1
Tandem electronic Tandem electronic or crossbar

office office
MF shuttle MF shuttle MFPP-1
Local DMS office Local crossbar or electronic

office
The frequency combinations available with NTRS14 signaling appear in the

following table Frequency combinations..
Frequency combinations
MF1 700 + 900
MF2 700 + 1100
MF3 900 + 1100
MF4 700 + 1300
MF5 900 + 1300
MF6 1100 + 1300
MF7 700 + 1500
MF8 900 + 1500
MF9 1100 + 1500
MF10 1300 + 1500
MF11 700 + 1500
Note 1: The duration of each frequency combination is 50 5 ms.

297-8021-351 Standard 05.02 May 2001

The following meanings are the meanings of the frequency combinations in

forward and backward directions:
Forward
MF1 to MF10
digits
MF11
end of digits
Backward
MF2
request (digits, category, and automatic number identification
[ANI])
MF6
repeat digits, negative acknowledgement
MF11
positive acknowledgement
The following sequence is the digit sequence in MFPP-1 register signaling:
NB + KA + NA + MF11
where
NA
is the calling directory number (DN)
KA
is the category of the calling subscriber (0 to 9)
NB
is the called DN
The system sends negative acknowledgement one time for a request that
repeats. If the pulse packet that repeated is distorted, the system sends signal
MF6 for negative acknowledgement. If the pulse packet that repeated is not
distorted, the system sends signal MF11.
Switching from MF shuttle to MFPP-1

The local DMS supports switching for the CIS network. The switch can
change from MFS register signaling to decadic, MFPP-2, or MFPP-1.
The MF shuttle switches to MFPP-1 after MF shuttle register signaling

finishes. This action occurs in local electronic to toll AMTC-KE (E), through
tandem E, call sequences for the present CIS network.
The backward signal MF4 informs the outgoing side that register signaling
finishes correctly in MFS. The system sends the signal MF12 to the incoming
side for acknowledgement of the received signal MF4. A special MF
backward signal for switching from the MF shuttle to MFPP-1 in MFS is not
present. The system records received backward signal MF4 like the switching
from MFS to MFPP-1 register signaling. The MFPP-1 register signaling
becomes active with called, calling, and category digits. The signaling
becomes active without a new call attempt after the switch from MFS to
MFPP-1.
The register signaling MFPP-1 becomes active after a delay set in field
MFPPWAIT in field RGSIGSYS. Switching from MFS to MFPP-1 or MFS to
MFPP-2 is not available for the same trunk.
The fourth parameter of the RGHYBRID structure determines the switching

signaling.
The MFPP-1 signaling type uses the present hybrid structure with four
elements. These elements are MF shuttle, decadic, ANI, and MFPP. The
parameters of selector RGHYBRID for NTRS06 can be one of the following
combinations:
NTRS02
NTRS05
MF3
NTRS03 or NTRS14
NTRS02
NTRS05
MF3
nil
nil
NTRS05
MF3
nil
nil
NTRS05
MF3
NTRS03 or NTRS14
nil
nil
nil
NTRS03 or NTRS14
297-8021-351 Standard 05.02 May 2001

The user can enter the fourth parameter with MFPP-2 (NTRS03) or NTRS14.
Datafill in other tables

The user must enter the following tuples in table DEFDATA to support
signaling type NTRS14:
Required datafill for table DEFDATA
DATATYPE DEFAULT
NTRS14IC_VAR_AREA NTRS14IC_VAR_AREA 1000 20 5 0 0 0 0 25
Datafill
The datafill for table RGSIGSYS type NTRS14 appears in the following table.
Field descriptions
Field Subfield or Entry Explanation and action


VECTOR 1 to 16 customer defined register signaling index. This
characters key is the key to table RGSIGSYS.


(NTRS14) and enter data for refinement DIR.
DIR C or OG Direction. Enter IC for incoming trunks and enter

data for refinements. These refinements are
MF2TIME, MFTIME, MINMF, MAXMF,
MINPAUSE, MAXPAUSE, REPLTIME, and
DLYMFPP in the following section..
Enter OG for outgoing trunks and enter data for
refinements. These refinements are MFTIME,
PAUSEMF, MINMF2, MAXMF2, MINMF,
MAXMF, REPLTIME, and MFWAIT in the section
DIR = OG.
DIR = IC
If the entry in field DIR is IC, enter refinements MF2TIME, MFTIME,
MINMF, MAXMF, MINPAUSE, MAXPAUSE, REPLTIME, and DLYMFPP.
This process appears in the following table.
Subfield or
MF2TIME 0 to 31 Signal MF2 time. Enter the duration of signal MF2

for incoming DMS in units of 10 ms.
The nominal value is 50 5 ms.
MFTIME 0 to 10 Multifrequency time. Enter the duration of each

frequency combination for incoming DMS. Perform
this entry if the system sends signal MF6 or MF11 in
units of 10 ms.
The default value is 5, which is 50 ms.
PAUSEMF 0 to 15 Pause multifrequency. Enter the duration of silence

between two signals in units of 10 ms.
MINMF 0 to 15 Minimum duration. Enter the minimum duration of

filtering for receiving each signal in incoming DMS in
units of 10 ms.
The default is 0.
MAXMF 0 to 15 Maximum duration. Enter the maximum duration of

filtering for receiving each signal for incoming DMS
in units of 10 ms. The entry in field MAXMF must be
greater than the entry in field MINMF.
The default is 0.
297-8021-351 Standard 05.02 May 2001

Subfield or
module (XPM) to wait for a reply signal in units of 10
ms.
The default is 100, which is 1000 ms.
DLYMFPP 0 to 100 Delay mulitfrequency pulse packet. Enter the

duration in units of one ms before you send the first
MF2 signal.
DIR = OG
If the entry in field DIR is OG, enter refinements MFTIME, PAUSEMF,
MINMF2, MAXMF2, MINMF, MAXMF, REPLTIME, and MFWAIT. This
process appears in the following table.
Subfield or
MFTIME 0 to 10 Multifrequency time. Enter the duration of each

frequency combination for outgoing DMS if the
system sends MF6 or MF11 in units of 10 ms.
PAUSEMF 0 to 15 Multifrequency pause. Enter the duration of silence

between two signals in units of 10 ms.
MINMF2 0 to 31 Minimum time for MF2. Enter the minimum duration

of filtering for received MF2 signal in outgoing DMS
in units of 10 ms.
The default is 0.

Subfield or
MAXMF2 0 to 31 Maximum time for MF2. Enter the maximum

duration of filtering for received MF2 signal in
outgoing DMS in units of 10 ms. The entry in field
MAXMF2 must be greater than the entry in field
MINMF2.
The default is 0 .
MINMF 0 to 15 Minimum duration. Enter the minimum duration of

filtering for each signal in outgoing MDS. Enter this
value during reception of only signal MF6 or MF11
with the same reason in units of 10 ms.
The default is 0.
MAXMF 0 to 15 Maximum duration. Enter the maximum duration of

filtering for each signal for outgoing DMS. Enter this
value during reception of only signal MF6 or MF11
with the same reason in units of 10 ms. The entry in
field MAXMF must be greater than the entry in field
MINMF.
The default is 0.
module (XPM) to wait for a reply signal in units of 10
ms.
MFWAIT 0 to 100 Multifrequency wait. Enter the duration of delay

before the system sends the packet after receiving
every MF2 signal in units of 10 ms.
The default is 25, which is 250 ms.
297-8021-351 Standard 05.02 May 2001

Datafill example
example.
RGSIGIDX
RSVAR
_____________________________________________________________________
EMSIGNAL
NTRS14 OC 1000 20 5 0 0 0 0 25
RLOGCLAS
Table name
Remote Log Class Table
Table RLOGCLAS contains class, threshold, suppression, and system
information for the log reports that apply to remote nodes.
See table LOGCLASS for more information.

Enter data in table RLOGTAB before you enter data in table RLOGCLAS.
Table size
16 to 512 tuples
The system allocates memory according to the number of additional tuples.
Datafill
The datafill for table RLOGCLAS appears in the following table.
Subfield or
REPNAME see subfields Report name. This field contains subfields

LOGNAME and REPNUM.
LOGNAME alphabetical, Log name. Enter the log name. Refer to the
a maximum of Log Report Reference Manual for a list of log
four names that reside in the log system.
characters
REPNUM -32768 to Report number. Enter the report number. If

32767 all report numbers are a requirement, enter 1.
Note: If a minus (-) report number is in use

for a given report name, perform the following
action. Enter this report number before the
other logs with the same report name.
CLASS 0 to 31 Class. Enter the class number that

associates with the report name.
297-8021-351 Standard 05.02 May 2001

RLOGCLAS (continued)
Subfield or
THRSHOLD 0 to 255 Threshold. Enter the number that specifies

the messages the system prints. Enter 0 to
print all messages.
If the entry is a value from 1 to 255, office
parameter THRESHOLD_IS_SAMPLING in
table OFCVAR controls the action for log
thresholding.
SUPPRESS Y or N Suppress. Enter Y (yes) to indicate that the

system does not generate a report or log. If
the system does generate a report or log,
enter N (no).
If the entry in field THRSHOLD is a value from
1 to 255, and the report is output, the following
condition occurs. Office parameter
BUFFER_THRESHOLDED_REPORTS in
table OFCVAR controls the removal of
reports that do not generate because of log
thresholding.
TUNITS -32768 to Time units. Enter the time, in minutes, when

32767 the register counts associated with a
threshold report is reset to 0. A maximum of
100 different time units can occur. An entry of
0, or a negative value in this field means that
the system generates all reports.
SYSLOG Y or N System log. Enter Y for a system log. All

system logs are put in table LOGCLASS from
the extension (EXT) files at loadbuild. If you
do not want a system log, enter N.
Datafill example
Sample datafill for table RLOGCLAS appears in the following example.
RLOGCLAS (end)
MAP example for table RLOGCLAS
REPNAME CLASS THRSHOLD SUPPRESS TUNITS SYSLOG

________________________________________________________
MSL 1 0 0 N 1 Y
OMPR 200 22 0 N 0 N
Table history
BCS36
Range of report numbers in field REPNUM was changed in BCS36.
297-8021-351 Standard 05.02 May 2001

RLOGDEV
Table name
Remote Log Device Table
The log output message classes for remote nodes appear in table RLOGDEV.
See tables LOGDEV, RLOGCLAS, and RLOGTAB for additional

information.

You must enter data in the following tables before you enter data in table
RLOGDEV.
OFCENG
OFCOPT
Table RLOGTAB uses table RLOGDEV.
Table size
The system allocates memory for 32 terminal devices.
Datafill
Datafill for table RLOGDEV appears in the following table.
1Field descriptions (Sheet 1 of 2)
Subfield or
DEV alphanumeric Device. Enter the name of the terminal device

(a maximum as assigned in table TERMDEV.
of 12
characters)
ALT alphanumeric Alternate. Enter the name assigned in table

(a maximum TERMDEV to the terminal device to which the
of 12 system sends the logs. The system sends the
characters) or logs to this terminal device if the main terminal
NONE device does not operate. If an alternate
device is not a requirement, enter NONE.
RLOGDEV (continued)
Subfield or
CLASSES 0 to 31 Classes. Enter the class numbers assigned

to the terminal device. If the entry is a block
of consecutive classes, enter the first and last
class in the block. Separate each entry by a
space. If classes are 1, 2, 3, 4, and 5, enter
1 5.
FORMAT SCC2 or STD Format. Enter SCC2 for the AT&T #2

switching control center format or STD for the
standard format.
Note: You can set this field to SCC2 if office

parameter SCC2_LOGS in table OFCOPT is
set to Y.
PRIORITY Y or N Critical message prioritization. Enter Y if the

alarm level places the reports in priority. The
system outputs the report with the highest
alarm level at any specified time. Enter N if
prioritization is not a requirement and the
system outputs the reports in a chronological
order.
Note: You can set this field to Y if office

parameter LOG_PRIORITIZATION in table
OFCENG is set to Y.
GUAR Y or N Guaranteed device. Enter Y if the device is

guaranteed. The device continues to run with
the call processing or maintenance load. If
the device is not guaranteed, enter N.
Datafill example
Sample datafill for table RLOGDEV appears in the following example.
297-8021-351 Standard 05.02 May 2001

RLOGDEV (end)
MAP example for table RLOGDEV
DEV ALT CLASSES FORMAT PRIORITY GUAR
________________________________________________________
LP121 NONE 031 STD N N
T0 NONE 10 SCC2 Y N
Table history
BCS36
Continuation marks (CONTMARK) were removed as an option.
RLOGTAB
Table name
Remote Log Table Table
Table RLOGTAB assigns a maximum of three output devices to receive logs
from remote Support Operating System (SOS)-based nodes. Table
NODNMTAB must contain all nodes in table RLOGTAB. To enter data in
table NODNMTAB, add the correct information to the associated inventory
table. The addition of link interface unit (LIU) Common Channel Signaling 7
(CCS7) in table LIUINV is an example of this entry. You must enter any
output device that table RLOGDEV specifies.
The system automatically adds tuples for SOS nodes other than the computer
module (CM), to table RLOGTAB. This condition occurs when the log
subsystem recognizes these nodes. In the BCS32 and later versions, the
operating company cannot add tuples to, or delete tuples from table
RLOGTAB. If operating company personnel attempt this action, the following
error message appears at the MAP terminal:
ONLY DEVICE ASSIGNMENTS CAN BE CHANGED IN TABLE RLOGTAB
The operating company can update any tuple to change a minimum of one of
the three log device assignments in this tuple. New device names must appear
in tables RLOGDEV and LOGDEV. To delete a device for any node,
substitute the value NIL. Substitute this value in the position of the tuple that
contained the device name.
The first tuple in table RLOGTAB is always tuple DEFAULT. This tuple
speeds the entry of data in table RLOGTAB. The operating company uses this
tuple to assign the same log devices to many remote SOS nodes in the switch.
The first setting of tuple DEFAULT occurs before the operating company
enters data. This setting does not assign log devices.
If the log system identifies a new remote SOS node, the log system creates a
tuple for the node in table RLOGTAB. The system obtains device assignments
in this tuple from the assignments in tuple DEFAULT at this time. The system
passes the default tuple settings to the other tuples in the table.
If the operating company changes the datafill for the default tuple, the system
checks all other tuples in the table. The system updates each tuple that had
three device assignments that match in tuple DEFAULT before the change.
The system updates the tuples to contain the default device assignments.
297-8021-351 Standard 05.02 May 2001

RLOGTAB (continued)
At the end of the update operation, the following message appears at the MAP
terminal:
NEW DEFAULT DEVICES PROPOGATED TO nn NODES
The value nn identifies the number of nodes with previous log device
assignments that match the assignments of the old tuple DEFAULT. The
operating company updates these nodes to match the new tuple DEFAULT.

You must enter data in table RLOGDEV before you enter data in table
RLOGTAB.
Table RLOGCLAS uses table RLOGTAB.
Table size
The table size is 0 to 2048 tuples
The number of tuples the system adds dynamically determines the table size.
Datafill
Datafill for table RLOGTAB appears in the following table.
Subfield or
NODENAME alphanumeric Node name. Enter the node name.

(a maximum
of 8
characters)
NODENUM -32768 to Node number. This file is a read-only field.

32767 The logs system enters data in this field. The
operating company cannot enter data in this
field. Refer to the Log Report Reference
Manual for additional information on the logs
system.
DEV1 alphanumeric First output device. Enter the name of the first
(a maximum output device entered before in table
of 12 RLOGDEV.
characters)
RLOGTAB (end)
Subfield or
DEV2 alphanumeric Second output device. Enter the name of the

(a maximum second output device entered before in table
of12 RLOGDEV.
characters)
DEV3 alphanumeric Third output device. Enter the name of the

(a maximum third output device entered before in table
of 12 RLOGDEV.
characters)
Datafill example
Sample datafill for table RLOGTAB appears in the following example.
MAP example for table RLOGTAB
NODENAME NODENUM DEV1 DEV2 DEV3
________________________________________________________
DEFAULT 1 NIL NIL NIL

M21 513 NIL NIL NIL
297-8021-351 Standard 05.02 May 2001

RMCONFIG
Table name
Remote Access Configuration Table
Note: The telnet server software currently does not use this table.
Table RMCONFIG configures the number of available telnet connections on a

DMS. Each telnet connection requires a remote MAP (maintenance and
administration position) (RMAP). The RMAP operates on the computing
module (CM) of the DMS core. Each telnet connection requires a telnet
process that operates on an Ethernet interface unit (EIU). This table specifies
the maximum number of RMAP processes on the CM and the maximum
number of telnet processes on each EIU that connects to the system.
The tuples that you must add to internal table CUSTFLDS for table formatting
appear in Table, CUSTFLDS.
CUSTFLDS
TABFLD FLDNAME FSPEC PRTPOS AREAREF
RMCONFIG 1 INDEX L_KEY 1 N
RMCONFIG 2 NODE L_DATA$NODE 10 S
RMCONFIG 3 SESSIONS L_DATA 16 R
The tuples that you must add to internal table CUSTAREA for table formatting
appear in Table CUSTAREA.
CUSTAREA
REFAREA FLDNAME FSPEC PRTPOS DISPLAY
RMTC_CM_DATA 1 RMAPCONN NUM_RMAPSERVERS 20 TRUE N
RMTC_EIU_DATA 2 EIUINDEX EIU_NUM 15 TRUE N
RMTC_EIU_DATA 3 TELNCONN NUM_RMAPCLIENTS 20 TRUE N

RMCONFIG.
RMCONFIG (continued)
Table size
The table size is 0 to 32 tuples
Datafill
Datafill for table RMCONFIG appears in the following table.
Subfield or
INDEX see subfield Index.

This field contains subfield TABLE_KEY.
TABLE_KEY 0 to 31 Table key.

This field is the key field of the table. Enter the
index to the table.
NODE CM or EIU Node.

Enter the name of the node, CM (computing
module) or EIU (Ethernet interface unit).
Note: If the entry in field NODE is CM, the entry

in field TABLE_KEY must be 0 (zero).
SESSIONS see subfield Sessions.

This field contains subfield NODE_NAME.
NODE_NAME see Node name.

refinements This subfield contains refinements for field NODE.
If the entry in field NODE is CM, enter data in
refinement RMAPCONN.
If the entry in field NODE is EIU, enter data in
refinements EIUINDEX and TELNCONN.
RMAPCONN 0 to 32 Remote MAP connections.

If the entry in field NODE is CM, enter data in this
refinement. Enter a value to specify the maximum
number of remote MAP (maintenance and
administration position) (RMAP) processes.
297-8021-351 Standard 05.02 May 2001

RMCONFIG (continued)
Subfield or
EIUINDEX 0 to 4095 Ethernet interface unit index.

If the entry in field NODE is EIU, enter data in this
refinement. Enter a value to specify the EIU
number.
TELNCONN 0 to 32 Telnet connections.

If the entry in field NODE is EIU, enter data in this
refinement. Enter a value to specify the maximum
number of telnet processes.
Datafill example
Sample datafill for table RMCONFIG appears in the following example.
MAP example for table RMCONFIG
INDEX NODE SESSIONS

________________________________________________________
0 CM 32
1 EIU 107 20
Table history
BCS36
The following changes occurred:
Subfields TABLE_KEY and NODE_NAME were added.
Field names NUM_RMAPSERVERS, EIU_NUM, and
NUM_RMAPCLIENTS were corrected to RMAPCONN, EIUINDEX,
and TELNCONN in order.
A node was added to field NODE.
BCS35
Table RMCONFIG was introduced.
RMCONFIG (end)
This section provides information on how to enter data in table RMCONFIG.
Miscellaneous information
The RMAP server and the telnet server have a one-to-one relationship. Each
active telnet session requires one telnet server that operates on the EIU. Each
active telnet session requires one RMAP server that operates on the CM. A
single EIU cannot support as many telnet servers as the CM can support
RMAP servers. If this condition occurs, you need multiple EIUs to match the
number of telnet and RMAP servers. Another method to match the number of
servers is to limit the maximum number of RMAP servers on the CM.
297-8021-351 Standard 05.02 May 2001

RMMINV
Table name
Remote Maintenance Module Table
Table RMMINV performs functions similar to a maintenance trunk module
(MTM) such as scanning of the service circuits, for example, dial pulse
collection, test trunks, and alarm circuit packs. The remote maintenance
module (RMM) is driven by the host line group controller/line trunk controller
(LGC/LTC). The RMM can be located in the remote line concentrating
module (RLCM), remote switching center (RSC), convertible RLCM, outside
plant module (OPM), international LCM (IRLCM) switching configurations,
Meridian cabinet remote module (MCRM), or remote digital line module
(RDLM).
The RMM can be used remotely in one of the switching configurations

described above. All switching configurations except RSC can have one
RMM only, but RSC can be equipped with up to two RMMs.
The RMM is a single-shelf peripheral (NT6X13AA, NT6X13BA,

NT6X13DA, NT6X1301, NT7X53AA) that contains two power converters
(NT2X06AB and NT2X09AA), an RMM control card (NT6X74AB), a
CODEC and TONE card (NT2X59AA), and space for 15 trunk circuits/service
circuit packs. Product engineering code (PEC) NT6X13BA is the Caribbean
RMM and NT6X13DA is the Turkish RMM.
The RMM terminates by means of two DS30A links (duplicated) on either the
line cluster controller (LCC) or the remote cluster controller (RCC),
depending on the configuration involved. Each DS30A link consists of 32
channels, 30 of which carry pulse code modulation (PCM) information and the
other 2 are for messaging purposes. The RMM sends messages through
DS30As to the LCCs/RCCs/DLMs and then by means of DS-1s to the host
LGC/LTC if the RMM is part of a RLCM/RDLM or D30 to host ILGC/ILTC
if the RMM is part of an IRLCM.
Table RMMINV identifies the RLCM/RSC/OPM/IRLCM/MCRM/RDLM

site with the frame type, frame number, floor, row, frame position, equipment
PEC, peripheral module (PM) load and executive program loaded, and C-side
PM attached to each RMM.
RMMINV (continued)

The following tables must be datafilled before table RMMINV:
DLMINV
LCMINV
LTCPSINV
RCCINV
RCCPSINV
SITE
Tables SITE, RCCINV, and RCCPSINV must be datafilled before table

RMMINV if an RMM is a subordinate of an RCC or RCC variant.
Tables SITE and LCMINV must be datafilled before table RMMINV if an

RMM is a subordinate of an LCM or LCM variant.
Tables SITE, RCCINV, RCCPSINV, and LTCPSINV must be datafilled before

table RMMINV if an RMM is a subordinate of an LTC.
Tables SITE, LCMINV, and DLMINV must be datafilled before table

RMMINV if an RMM is a subordinate of a DLM.
Table size
0 to 255 tuples
Memory is dynamically allocated for this table.
297-8021-351 Standard 05.02 May 2001

RMMINV (continued)
Datafill
The following table lists datafill for table RMMINV.
Subfield or
RMMNAME see subfields Remote maintenance module name
This field consists of subfields SITENM,

PMTYPE, and RMMNO.
SITENM alphanumeric Site name

(up to 4
characters)
Enter the site name assigned to the remote
location. This name must also be datafilled in
tables LCMINV, RCCINV, OPMINV, and
SITE.
PMTYPE RCC2, RMM, Peripheral module type

or SRCC
Enter the PM type.
RMMNO 0 to 254 Remote maintenance module number
Enter the RMM number. This number is

unique by office, not unique by site.
RMMINV (continued)
Subfield or
FRTYPE DLE, MCRM, Frame type

OPE, RCE,
RCME, or
RLCM Enter the frame type on which the RMM is
equipped as follows:
Enter DLE (digital line equipment) if the
RMM is used in the RDLM.
Enter MCRM if the RMM is used in the
cabinetized Meridian SL-100.
Enter OPE if the RMM is used in the
OPM.
Enter RCE if the RMM is used in the RSC.
Enter RCME if the RMM is used in the
convertible RLCM configurations.
Enter RLCM if the RMM is used in the
RLCM.
FRNO 0 to 511 Frame number
Enter the number of the frame on which this

RMM is equipped.
SHPOS 5, 21, 38, 55, Shelf position

56
Enter the number of the shelf on which the

RMM is located as follows:
Enter 5 if the RMM is located in the OPE.
Enter 21 if the RMM is located in the
RCME.
Enter 38 or 55 if the RMM is located in the
RCE.
Enter 56 if the RMM is located in RLCM.
297-8021-351 Standard 05.02 May 2001

RMMINV (continued)
Subfield or
FLOOR 0 to 99 Floor
Enter the number of the floor on which the PM

is located.
ROW A to H J Row
to N P to
Z AA to
HH JJ to NN Enter the number of the row in which the
or PP RMM is located.
to ZZ
FRPOS 0 to 99 Frame position
Enter the position of the PM equipment frame.
EQPEC 6X1301 Equipment product engineering code

6X13AA
6X13BA
6X13DA Enter the equipment PEC as follows:
7X53AA
Enter 6X1301 for cabinetized Meridian
8X98AA
SL-100.
FX14AA or
MX85AA Enter 6X13AA for a regular RMM.
Enter 6X13BA for RMM - Caribbean.
Enter 6X13DA for RMM - Turkey.
Enter 7X53AA for RMM in the RDLM.
Enter 8X98AA for RMM on SRU.
Enter FX14AA for AIM based RMM
controller.
Enter MX85AA for RCC2.
RMMINV (continued)
Subfield or
LOAD alphanumeric Load

(vector of up
to 8
characters) Enter the name given to the issue of the PM
software (for a list of available names, see the
batch change supplement for the appropriate
BCS release).
EXECS alphanumeric Execs

(up to 6
characters)
Enter the exec lineup to be used for the RMM
(for a list of available names, see the batch
change supplement for the appropriate BCS
release).
CSPMINFO see subfields C-side peripheral module information
This field consists of subfields

RMMSELECTOR, CSIDEPM, and
CSIDPORT.
RMMSELECTO RMMDLM Remote maintenance module selector

R RMMILCM
RMMLCM
RMMLTC Enter the type of module in which the RMM is
RMMRCC2 located.
RMMRCC
RMMRCCI
RMMRCO2
RMMSRCC
RMMSRU
CSIDEPM see subfields C-side peripheral module
This field consists of subfields PMT and

EXTPMNO.
297-8021-351 Standard 05.02 May 2001

RMMINV (continued)
Subfield or
PMT ALCM, Peripheral module type

ARCC, DLM,
ELCM, ILCM,
LCM, LTC, Enter the PM type as follows:
PRCC, RCC2,
Enter DLM if the entry in field
RCC, RCCI,
RMMSELECTOR is RMMDLM.
RCO2,
RMMLTC, Enter ILCM if the entry in field
SRCC, SRU, RMMSELECTOR is RMMILCM.
or TRCC
Enter ALCM, ELCM, or LCM if the entry in
field RMMSELECTOR is RMMLCM.
Enter RCC, TRCC, ARCC, or PRCC if the
entry in field RMMSELECTOR is
RMMRCC.
Enter LTC or RCC if the entry in field
RMMSELECTOR is RMMLTC or
RMMRCC.
Enter PRCC for international PCM30
remote cluster controller (the PCM30
peripheral can be used if the entry in field
RMMSELECTOR is RMMRCC or
RMMRCCI).
Enter RMMLTC if the entry in field
RMMSELECTOR is RMMLTC.
Enter RCC2 if the entry in field
RMMSELECTOR is RMMRCC2.
Enter RCCI if the entry in field
RMMSELECTOR is RMMRCCI.
Enter RCO2 if the entry in field
RMMSELECTOR is RMMRCO2.
Enter SRCC if the entry in field
RMMSELECTOR is RMMSRCC.
Enter SRU if the entry in field
RMMSELECTOR is RMMSRU.
RMMINV (continued)
Subfield or
EXTPMNO 0 to 63 External peripheral module number
Enter the external PM number to which the

RMM is attached. Entries outside this range
are invalid. This number must also be
datafilled in either tables LCMINV, OPMINV,
RCCINV, or DLMINV.
RMMSELECTOR = RMMLTC, RMMRCC2, RMMRCC, RMMRCCI,

RMMRSRCC, or RMMRCO2
If the entry in field RMMSELECTOR is either RMMLTC, RMMRCC2,
RMMRCC, RMMRCCI, RMMSRCC, or RMMRCO2, datafill subfield
CSIDPORT.
Conditional datafill for table RMMINV
Subfield or
CSIDPORT 0 to 63 C-side port
Enter the number of the C-side port

connected to the RMM as follows:
If the entry in field RMMSELECTOR is
RMMRCC2, RMMRCO2, or RMMSRCC,
enter a value from 0 (zero) to 63.
If the entry in field RMMSELECTOR is
RMMRCC, RMMRCCI, or RMMLTC,
enter a value from 0 (zero) to 19.
Datafill example
An example of datafill for table RMMINV is shown below.
Note 1: Site REM2 has its RMM as part of an RLCM, while sites REM7
and REM8 have their RMMs as part of an RSC.
Note 2: Values 41, 182, and 199 are unique by office.
297-8021-351 Standard 05.02 May 2001

RMMINV (end)
Datafill example for table RMMINV
RMMNAME FRTYPE FRNO SHPOS FLOOR ROW FRPOS EQPEC LOAD

EXECS
CSPMINFO CSIDPORT
________________________________________________________
REM2 RMM 41 RLCM 1 56 2 A 4 6X13AA RMMDA01

RSMEX
RMMLCM LCM 3
REM7 RMM 182 RCE 1 38 2 A 4 6X13AA RMMDA01
RSMEX
RMMRCC RCC 5 0
REM8 RMM 199 RCEI 2 51 2 A 4 6X13AA RMMDA02
RSMEX
RMMRCC PRCC 2 0
Table history
TL06
Added entry FX14AA to field EQPEC for AIM.
UK002
The following changes were made:
CONTMARK field was removed.
Explanation and action for entry 8X98AA was added for field EQPEC.
BCS36
Datafill sequence was revised and field PMT was corrected.
RMPCKT
Table name
Remote Maintenance Pack Circuit
Remote maintenance pack circuit (RMPCKT) table contains the details of the
universal maintenance pack (UMP) card in the Star Hub. The UMP
provides line card diagnostic and maintenance capabilities to the
peripheral module (PM) in which it is in. A UMP is defined as a trunk and
has its own common language location identifier (CLLI) name.
line maintenance unit (LMU) card in the Star Module. The LMU provides
line card diagnostic and maintenance capabilities for lines connecting to
the Star Module.
Table RMPCKT contains parameters for each UMP and LMU. Each tuple
represents a logical definition of UMP or LMU cards. The tuple also contains
all the necessary details about the Star Hub to which the UMP or LMU
belongs.

The following tables must be datafilled before table RMPCKT.
CLLI (make sure the first UMP or LMU card is entered in table CLLI)
PMLOADS
LNINV (make sure at least one line on the Star Hub is entered)
The following tables must be datafilled after table RMPCKT.

ALMSCGRP
ALMSDGRP
ALMSC
ALMSD
Table size
0 to 1000 tuples
297-8021-351 Standard 05.02 May 2001

RMPCKT (continued)
Datafill
The following table lists datafill for table RMPCKT.
Subfield or
MPKEY See subfields Maintenance pack key. Enter the

maintenance pack CLLI and maintenance
pack index.
MPCLLI RMP, UMP, Maintenance pack CLLI. Enter the type of

LMU maintenance card in the Star Hub or Star
Module.
MPIND 0 to 999 Maintenance pack index. Enter the index

number. 0 to 511 for UMP. 0-999 for LMU.
PMNAME See subfields Peripheral module name. Enter the remote

type, site, frame number, and unit number.
REMOTYP PM, UREM Remote type. Enter the remote type.
SITE alphanumeric Site. Enter the site name assigned to the

remote location.
FRAME 0 to 511 Frame number. Enter frame number for the

Star Hub.
UNIT 0 to 2 Unit number. Enter the unit number where

the maintenance pack resides.
SLOTDRWR See subfields Slot or drawer. This field consists of subfields

slot and drawer. Enter SLOT if a UMP is to be
added. Enter DRAWER if an LMU .
SLOT 0-37 RMP/UMP slot number. Enter the slot

number of the RMP/UMP card.
DRAWER 0-17 Drawer number. Enter the drawer number

where the LMU resides.
CARDCOD NTTR71AA Card code. Enter the maintenance card code

NTTR73AA version.
MY73AA
LOAD TERM_LDINF Load file name. Enter the name of the UMP
O load as defined in table PMLOADS. For RMP
the value of this field is NILFNAME.
RMPCKT (continued)
Subfield or
TRAFSNO 0 to 127 Traffic separation. Enter the type of traffic

separation or traffic analysis to be performed.
TLINEATT alphanumeric Table LINEATTR index. Enter the line

(1 to 16 attribute index number in table LINEATTR for
characters) each UMP. Also enter the values for subfield
XLAPLAN and RATEAREA.
Note: In the North American market, the

default entry for T_LINEATTR is 0 NIL NIL.
XLAPLAN XLAPLAN_ Translations plan. Default value is NIL.

KEY
RATEAREA NLCA_NILLA Rate area. Default value is NIL.

_0, NIL
Datafill example
The following example shows sample datafill for table RMPCKT.
MAP display example for table RMPCKT
RMPCKT
MPKEY PMNAME SLOTDRWR CARDCOD LOAD TRAFSNO
TLINEATT
________________________________________________________
UMP 0 STAR REM1 9 0 SLOT 13 NTTR73 UMPAK01 3
1 NIL NIL
UMP 1 STAR REM1 0 1 SLOT 15 NTTR73 UMPAK01 4
2 NIL NIL
LMU 7 STAR REM1 4 0 DRAWER 12 TR71AA NILFNAME 0
0 NIL NIL
Table history
MMP15
Development activity AF6857 introduced changes to fields PMNAME,
CARDCOD and LOAD.
Field T_LINEATTR changed to TLINEATT to reflect latest field name.
297-8021-351 Standard 05.02 May 2001

RMPCKT (end)
NA012
Development activity 59007050 introduces changes to field T_LINEATTR.
This field now accepts an alphanumeric string instead of an integer string.
NA011
Changed field SLOT to SLOT_OR_DRAWER with added subfields SLOT and
DRAWER to support UMP in Star Hub and LMU in Star Module.
NA010
New table RMPCKT to support universal maintenance pack in Star Remote
Hub.
RNDING
Table name
ITOPS Rating Charge Calculator Charge Rounding Table
Table RNDING specifies how rounding is applied to charges for a particular
schedule set.
Rounding can be applied in any of the following ways:

Rounding for coin lines is applied to charges before any tax is applied.
Rounding to the smallest coin available for use in the coin phone will occur
depending on the rounding factor. The smallest coin available for use in
the coin phone is defined in table OFCVAR, parameter
RATING_SMALLEST_COIN.
Rounding is applied to each tax before adding to charges.
Rounding is applied to total charges after tax.
For related information, refer to Table ATRIMOD.
Rounding factor
The rounding factor is the amount that is added to the calculated charge before
truncation to accomplish the desired rounding. The rounding factor is
proportional to the MULT value used in determining charges. The amount of
round off precision available is equal to 1/10th the MULT value.

Table SSETNAME must be datafilled before table RNDING.
Table size
0 to 64 tuples
297-8021-351 Standard 05.02 May 2001

RNDING (continued)
Datafill
The following table lists datafill for table RNDING.
Subfield or
SSETNAME alphanumeric Schedule set name. Contains a schedule set

(1 to 16 name that has been datafilled in table
characters) SSETNAME.
CDR Y or N Coin call before tax rounding used. Y

indicates that rounding is applied to pretax
charges for coin calls. N indicates it is not.
CPT 0 to 10 Coin call before tax rounding factor. When

CDR is Y, the rounding factor that is used for
rounding off pretax charges for coin lines is
entered in this field. When CDR is N, 0 is
entered in this field to satisfy the table editor.
NDR1 Y or N Noncoin call tax rate 1 rounding used. Y

indicates that rounding is applied to tax rate 1
charges for noncoin calls. N indicates that it
is not.
NTR1 0 to 10 Noncoin call tax rate 1 rounding factor. When

NDR1 is Y, the rounding factor used for
rounding off tax rate 1 charges for noncoin
lines is entered in this field. When NDR1 = N,
0 is entered to satisfy the table editor.
CDR1 Y or N Coin call tax rate 1 rounding used. Y

CTR1 0 to 10 Coin call tax rate 1 rounding factor. When

CDR1 is Y, the rounding factor used for
rounding off tax rate 1 charges for coin lines is
entered in this field. When CDR1 is N, 0 is
entered to satisfy the table editor.

is not.
RNDING (continued)
Subfield or

NDR2 is Y,the rounding factor used for
CDR2 Y or N Coin call tax rate 2 rounding used. Y


entered in this field. When CDR2 = N, 0 is

is not.

NDR3 is Y, the rounding factor used for
CDR3 Y or N Coin call tax rate 3 rounding used Y indicates

that rounding is applied to tax rate 3 charges
for coin calls. N indicates that it is not.

entered in this field. When CDR3 = N, 0 is
NTT Y or N Noncoin call total after-tax rounding used. Y

indicates that rounding is applied to the total
charges, including taxes, for noncoin calls. N
indicates that it is not.
297-8021-351 Standard 05.02 May 2001

RNDING (end)
Subfield or
NTTR 0 to 10 Noncoin call total after-tax rounding factor .

When NTT is Y, the rounding factor used for
rounding off the total charges, including
taxes, for noncoin lines is entered in this field.
When NTT = N, 0 is entered to satisfy the
table editor.
CTT Y or N Coin call total after-tax rounding used Y

indicates that rounding is applied to the total
charges, including taxes, for coin calls. N
indicates it is not.
CTTR 0 to 10 Coin call total after-tax rounding factor. When

CTT is Y, the rounding factor used for
rounding off total charges, including taxes, for
coin lines is entered in this field. When CTT =
N, 0 is entered to satisfy the table editor.
Datafill example
The following example shows sample datafill for table RNDING.
MAP display example for table RNDING
SSETNAME CDR CPT NDR1 NTR1 CDR1 CTR1 NDR2 NTR2 CDR2 CTR2 NDR3 NTR3
CDR3 CTR3 NTT NTTR CTT CTTR
______________________________________________________________________
SCHSETB N 0 Y 6 N 0 Y 3 N 0 N 0
N 0 N 0 N 0
ROTLCB
Table name
Remote Office Test Line Call Back Table
Table ROTLCB and table ROTLSCSD drive the remote office test line (ROTL)
facilities.
Tables ROTLCB and ROTLSCSD enable the incorporation of ROTL facilities

into the DMS-100 family of switching systems. The remote office test line
function allows a centralized automatic trunk test system, such as centralized
automatic reporting on trunks (CAROT) or remote automatic measurement of
performance and reporting on trunks (RAMPART), to automatically test
outgoing and two-way trunks in a DMS-100.
The ROTL unit is connected to the DMS-100 by access lines and test ports.
The two access lines are accessible from the direct distance dialing (DDD)
network as subscriber lines. The CAROT or RAMPART system (referred to
as CONTROL throughout this section) can access the ROTL unit through one
of the two access ports, which must be connected as ground start lines. The
two access lines behave as a two-line hunt group. In a DMS-100 office they
are connected through card NT2X18AD (line-circuit card-type B) or
equivalent line cards installed in the line module. Access lines for a DMS-200
switch are connected to a local class-5 switch.
Two ROTL unit test ports are used to originate tests. The ROTL test ports
interface with the DMS switch through a trunk group with a pseudo common
language location identifier (CLLI) of ROTLTP assigned in table CLLI. The
two members of the trunk group consist of trunk circuits NT3X91AA (remote
office test line circuit card).
These trunks must be assigned to tables TRKGRP, TRKSGRP, and TRKMEM

with a trunk group type ROTL.
Each test port has four sense (scan) and four control (signal distributor) points
associated with it. Table ROTLSCSD must be datafilled to identify the
location of the scan cards and signal distributor cards that contain the scan and
signal distributor points.
Circuits must not have been previously assigned to tables ALMSC, NWMSC
and SCGRP before scan groups are assigned to table ROTLSCSD.
A maximum of six 105 test lines are used to terminate 105 test line calls in the
near end office. The 105 test lines interface with the DMS through
297-8021-351 Standard 05.02 May 2001

ROTLCB (continued)
NT3X91AA trunk circuits. These trunks are contained in a trunk group with
a pseudo CLLI of TERM105 assigned in table CLLI and must be assigned to
tables TRKGRP, TRKSGRP, and TRKMEM with a trunk class code of
TERM105. Code 105 in the code table and its associated route must be
datafilled to allow a call to the 105 test line to route to the trunks.
One alarm scan (sense) point is used for reporting major alarms such as power
failure to the DMS office. This requires that tables ALMSC and ALMSCGRP
be datafilled with function equal to ROTLALM.

The following tables must be datafilled before table ROTLCB.
TRKMEM
ALMSCGRP
Table size
0 to 11 tuples
Datafill
The following table lists datafill for table ROTLCB.
Subfield or
INDEX see subfield Index

This field consists of subfield K.
K 1 to 10 Call back index

Enter the call back index that is specified in
the priming digits of a call back request. A
security call back is made to the directory
number for this index and the specified
authorization level is granted if the 1004-Hz
unlocking signal is received.
ROTLCB (end)
Subfield or
AUTHORIZ AUTO or Authorization

MANUAL
Enter AUTO if a make busy request is allowed
if the number of trunks out of service does not
exceed the out-of-service limit. Enter
MANUAL, if a make busy request is allowed
even if the number of trunks out of service
exceeds the out-of-service limit. The out of
service limit is defined by office parameter
ROTL_OUT_OF_SERVICE_LEVEL in table
OFCENG.
DR alphanumeric Digit register

(up to 18
Enter the directory number (security call back
digits)
number) for the call back index entered in
subfield K.
Datafill example
An example of datafill for table ROTLCB is shown below.
For index 1, the authorization is AUTO and the directory number is 6211234.
For index 2, the authorization is manual and the directory number is 6221235.
MAP display example for table ROTLCB
INDEX AUTHORIZ DR
________________________________________________________
1 AUTO 6211234
2 MANUAL 6211235
Table history
BCS36
Subfield K was added. Long field name for field DR was corrected.
297-8021-351 Standard 05.02 May 2001

ROTLSCSD
Table name
Remote Office Test Line Scan And Signal Distributor Table
This table is used to relate each test port with its sense (scan) and control
(signal distributor) points.
For related information refer to table ROTLCB.

The following tables must be datafilled before table ROTLSCSD.
ROTLCD
CLLI
TRKGRP
TRKSGRP
TRKMEM
Table size
2 tuples
Datafill
The following table lists datafill for table ROTLSCSD.
Subfield or
TESTPORT see subfields Test port

This field consists of subfields CLLI and
MEMNAME.
CLLI ROTLTP Common language location identifier

Enter the pseudo fixed common language
location identifier (CLLI) for the remote office
test line (ROTL) test port. The pseudo CLLI
must be previously entered in table CLLI.
MEMNAME 0 to 9999 External trunk number

Enter the external trunk number assigned to
the trunk.
ROTLSCSD (continued)
Subfield or
SCTMTYPE MTM Scan trunk module type

Enter MTM (maintenance trunk module) for
the trunk module type on which the scan card
is mounted.
Any entry outside the range indicated for this
field is invalid.
SCTMNO 0 to 2047 Scan trunk module number

Enter the number of the trunk module on
which the scan card is mounted.
SCTMCCT 0 to 29 Scan trunk circuit number

Enter the trunk module circuit number to
which the scan card is assigned.
SDTMTYPE MTM Signal distributor trunk module type

Enter MTM for the type of trunk module on
which the signal distributor card is mounted.
Any entry ouside the range indicated for ths
field is invalid.
SDTMNO 0 to 2047 Signal distributor trunk module number

Enter the number assigned to the trunk
module on which the signal distributor card is
mounted.
SDTMCCT 0 to 29 Signal distributor trunk circuit number

Enter the trunk module circuit number to
which the signal distributor card is assigned.
Datafill example
An example of datafill for table ROTLSCSD is shown below.
This example shows the scan and signal distributor card locations for two test
ports. The two test ports have a pseudo CLLI of ROTLTP.
297-8021-351 Standard 05.02 May 2001

ROTLSCSD (end)
MAP display example for table ROTLSCSD
TESTPORT
SCTMTYPE SCTMNO SCTMCCT
SDTMTYPE SDTMNO SDTMCCT
____________________________________________________
ROTLTP 0
MTM 2 2
MTM 2 0
ROUND
Table name
TOPS Charge Rounding Table
The operating company uses table ROUND to specify how rounding is applied
to charges for a particular tariff.
Rounding is applied to two different stages of the total charge calculation:

rounding (to cent) is applied to charges before any tax is applied
rounding (to cent) is applied to each tax before adding to charges
Optionally, rounding is applied to coin calls as follows:

rounding (to nickel) is applied to charge before tax
rounding (to nickel) is applied to taxes
rounding (to nickel) is applied to total charges after tax
TOPS Mass Table Control

ROUND to be mass-table-controlled. In other words, the feature permits the
changes for the table into table ROUNDI, and then, when all the required
changes are entered, swap the contents of table ROUND with table ROUNDI.

Table ROUND specifies how the rounding is applied to charges for a particular
tariff. The rounding is applied to pre-tax charges and each time a tax is added
to charges (cent rounding). For coin calls, nickle rounding is applied to pre-tax
charges, to the tax and the total charges after taxes have been added.
Rounding factor
The rounding factor is the amount that is added to the calculated charge before
truncation to accomplish the desired rounding.
297-8021-351 Standard 05.02 May 2001

ROUND (continued)
The following table provides an example of the rounding factor.

Rounding factor
Type of Rounding Data form

rounding Required rounding factor entry
Cent If rounding down is required 0 0

for any fraction
If rounding up is required for 0.7 7

0.3 cent and over
If round up is required for 0.1 0.9 0

cent and over
Nickel If rounding down is required 0 0

for any fraction

2.1 cents and over

0.1 and over

Table TARIFF must be datafilled before table ROUND.
Datafill
The following table lists datafill for table ROUND.
Subfield or
TARIFF alphanumeric Calling tariff key. Enter the calling tariff name
(up to 32 as previously datafill in table TARIFF.
characters)
DR 0 to 9 Before tax cent rounding factor. Enter the

rounding factor to round charges before tax to
cent.
CDR Y or N Coin call before tax nickel rounding required.

Enter Y (yes) if rounding (to nickel) is to be
applied to pretax charges for coin calls.
Otherwise, enter N (no).
ROUND (continued)
Subfield or
CDR5 0 to 49 Coin call nickel rounding factor before tax. If

the entry in field CDR is Y, enter the rounding
factor. Otherwise, enter 0 (zero).
TR1 0 to 9 Tax rate 1 cent rounding factor. Enter the

rounding factor (to cent) for tax rate 1 (TAX1).
CTR1 Y or N Coin call tax rate 1 nickel rounding required.

Enter Y if rounding (to nickel) is to be applied
to TAX1 for coin calls. Otherwise, enter N.
CT5R1 0 to 49 Coin call tax rate 1 nickel rounding factor. If

the entry in field CTR1 is Y, enter the rounding

rounding factor (to cent) for TAX2. (see Fig.
A)



rounding factor (to cent) for TAX3.


297-8021-351 Standard 05.02 May 2001

ROUND (end)
Subfield or
CCR Y or N Coin call total charges nickel rounding

required. Enter Y if rounding (to nickel) is to
be applied to total charges for coin calls.
Otherwise, enter N.
CCR5 0 to 49 Coin call total charges nickel rounding factor.

If the entry in field CCR is Y, enter the
rounding factor. Otherwise, enter N.
Datafill example
The following examples show sample datafill for table ROUND.
MAP display example for table ROUND
TARIFF DR CDR CDR5 TR1 CTR1 CT5R1 TR2 CTR2 CT5R2 TR3 CTR3 CT5R3 CCR CCR5
________________________________________________________________________
BELLON
T 5 N 0 5 Y 25 0 N 0 0 N 0 Y 25
The second example shows datafill for the Caribbean Expansion Plan (CEP)
International TOPS (ITOPS).
MAP display example for table ROUND
TARIFF DR CDR CDR5 TR1 CTR1 CT5R1 TR2 CTR2 CT5R2 TR3 CTR3 CT5R3 CCR CCR5
________________________________________________________________________
STKITT
S1 5 N 0 5 Y 25 0 N 0 0 N 0 Y 25
ROUNDI
Table name
TOPS Charge Rounding Inactive Table
ROUND to be mass-table-controlled. In other words, the feature permits the
changes for the table into table ROUNDI, and then, when all the required
changes are entered, swap the contents of table ROUND with table ROUNDI.
Refer to table ROUND.

Table size
Datafill
Datafill example
297-8021-351 Standard 05.02 May 2001

ROUTEMAP
Table name
Route Map Table
Table ROUTEMAP functions as a look-up table to allow the DMS to redirect
calls to new routes. Table ROUTEMAP uses information from tables OVR0-9
and RTECHAR in field KEY to provide the alternate route selection. Table
ROUTEMAP provides the translations software with a new route index to
tables OVR0-9.

Enter data in the following tables after you enter data in table ROUTEMAP.
OVR0-9
RTECHAR
Table size
The minimum table size is 0 tuples. The amount of memory store available
determines the maximum size.
Datafill
Datafill for table ROUTEMAP appear in the following table.
Subfield or
RMAPKEY see subfields ROUTEMAP key

This field is the key to the table. This field
contains subfields TABID and RCNAME.
TABID OVRO to Table identifier

OVR9 Enter the OVR table that results from the call
translation. Enter data in refinement KEY.
Entries outside this range are not correct.
KEY 0 to 1023 OVR table key

Enter the index to the tuple in the OVR table
entered in subfield TABID.
ROUTEMAP (end)
Subfield or

(a maximum Enter the routing characteristic name
of 8 previously entered in field RCKEY in table
characters) RTECHAR.
NEWROUTE see subfield New ROUTEMAP key

This field contains the information for the new
route. This field contains subfield TABID.
TABID OVRO to Table identifier

OVR9 Enter the new OVR table to which the call
routes. Enter data in refinement KEY.
Entries outside this range are not correct.
KEY 0 to 1023 OVR table key

Enter the index to the tuple in the new OVR
table entered in subfield TABID.
Datafill example
Sample datafill for table ROUTEMAP appear in the following example.
MAP example for table ROUTEMAP
RMPAKEY NEWROUTE
________________________________________________________
OVR4 2 OVR4 3
Table history
BCS34
Table ROUTEMAP was introduced in BCS34.
297-8021-351 Standard 05.02 May 2001

RSDTLINE
Table name
Restricted Dial Tone LIne
Table RSDTLINE is used to identify the state of RSDT lines.

The LEN of an RSDTLINE tuple must be datafilled in table LNINV with a
STATUS of Hardware Assigned/Software Unassigned (HASU), CUTOFF, or
WORKING. The associated STATE field in table RSDTLINE is shown in the
following table.
RSDTLINE field STATE values
Enry for office

parameter LEN status in table LEN status in table
RSDT_ENABLED LNINV RSDTLINE
N HASU UNDEFINED
N WORKING UNDEFINED
N CUTOFF UNDEFINED
Y HASU (see note 1) IN_EFFECT
Y WORKING ELIGIIBLE
Y CUTOFF ELIGIBLE
Y CUTOFF (see note 2) IN_EFFECT
Note 1: The LEN becomes WORKING in table LNINV.

Note 2: It is possible to put an RSDT IN_EFFECT line into a CUTOFF state in
table LNINV.
Table size
Table RSDTLINE has the same number of tuples as table LNINV.
RSDTLINE (continued)
Datafill
The following table lists datafill for table RSDTLINE.
Field descriptions
Subfield or
LEN <LEN> LEN. For each line, this entry is equivalent to

the key field in table LNINV.
STATE ELIGIBLE, RSDT line state. The default value when

IN_EFFECT, datafilling a nw LEN is UNDEFINED. All lines
or will have their state set to UNDEFINED when
UNDEFINED the RSDT_ENABLED office parameter is set
to N. Whent the RSDT_ENABLED office
parameter is set to Y, an RSDT eligible line (a
line that is WORKING or CUTOFF in table
LNINV) will have the value IN_EFFECT. The
SERVORD NEW command on an RSDT
IN_EFFECT line will update the state to
ELIGIBLE, while the SERVORD command
OUT will update the state of an RSDT eligible
line to IN_EFFECT.
Note: This field is read-only.
RSDTIDX 0 RSDT index. The RSDT index is the value of

the RSDTIDX field in tablle DNROUTE. The
default value for this field is 0. This field can
be used for future enhancements.
Datafill example
The following example shows sample datafill for table RSDTLINE.
MAP display example for table RSDTLINE
LEN STATE RSDTIDX
________________________________________________________
HOST 00 1 00 06 IN_EFFECT 0
297-8021-351 Standard 05.02 May 2001

Creating lists and counts of LENs for each RSDT status type
To determine which LENs have a current RSDT state of IN_EFFECT or
ELIGIBLE, a list can be obtained from table RSDTLINE using a conditional
list query command. The current total number of LENs with RSDT state of
IN_EFFECT or ELIGIBLE can also be obtained using a conditional count
query command.>table rsdtline
The following figures display examples of both types of condional queries:

Example of a table query for a list of all LENs with a state of ELIGIBLE
>table rsdtline
TABLE RSDTLINE
>list all (state eq eligible)
LEN STATE RSDTIDX
________________________________________________________
HOST 00 1 00 06 ELIGIBLE 0
HOST 00 1 00 07 ELIGIBLE 0
Example of a table query for a list of all LENs with a state of IN_EFFECT
>table rsdtline
TABLE RSDTLINE
>list all (state eq in_effect)
LEN STATE RSDTIDX
________________________________________________________
HOST 00 1 00 06 IN_EFFECT 0
Example of a table query for a count of all LENs with a state of IN_EFFECT
>table rsdtline
TABLE RSDTLINE
>count (state eq in_effect
SIZE = 94
Error messages for table RSDTLINE
Error messages for table RSDTLINE (Sheet 1 of 2)
Error message Description Result
LEN: HOST 01 1 00 01ERROR: LEN MUST BE PRESENT Atte mpting to The addition fails
IN TABLE LNINV add a tuple to and an error
RSDTLINE for a message is
LEN that is not generated at the
found in LNINV. MAP.
LEN: HOST 01 1 00 01ERROR: INCOMPATIBLE LINE Atte mpting to The addition fails
STATUS FOR RSDT add a tuple to and an error
LEN that has a generated at the
status of MAP.
RESERVED or
UNEQUIPPED in
LNINV.
LEN: HOST 01 1 00 01ERROR: INCOMPATIBLE LCC Atte mpting to The addition fails
FOR RSDT LINE add a tuple to and an error
LEN that does generated at the
not have an LCC MAP.
of 1FR or
RES/1FR.
297-8021-351 Standard 05.02 May 2001

Error messages for table RSDTLINE (Sheet 2 of 2)
Error message Description Result
LEN: HOST 01 1 00 01ERROR: INCOMPATIBLE Atte mpting to The addition fails

OPTIONS FOR RSDT LINE add a tuple to and an error
LEN that has an generated at the
RSDT MAP.
incompatible
options assigned.
LEN: HOST 01 1 00 01ERROR: CARDCODE NOT Atte mpting to The addition fails
SUPPORTED add a tuple to and an error
LEN that has an generated at the
unsupported card MAP.
code.
LEN: HOST 01 1 00 01 IMPROPER LINE STATELEN: Atte mpting to The deketuib fails
HSOT 01 1 00 01 RSDT LINE CANNOT BE PUT OUT delete a line from and an error
OF SERVICE RSDTLINE that is message is
not in IDL, LMB, generated at the
HAZ, CUT, LO or MAP.
PLO state.
LEN: HOST 01 1 00 01 FAILED TO UPDATE TABLE A SERVORD The change fails

RSDTLINE command is and an error
attempting to message is
modify a tuple in generated at the
RSDTLINE. MAP.
LEN: HOST 01 1 00 01ERROR: LINE DATA IS NOT Atte mpting to The addition fails
SUPPORTED BY RSDT add a tuple to and an error
line with data that generated at the
is incompatible MAP.
with RSDT.
RSDTLINE (end)
Warning messages for table RSDTLINE
Warning messages for table RSDTLINE
Warning message Description Result
THIS FIELD CANNOT BE CHANGED Atte mpting to The change is not

change the allowed and a
STATE or warning
RSDTIDX field in message is
RSDTLINE generated at the
MAP.
RSDTIDX VALUE WILL DEFAULT TO 0 Atte mpting to The command is

datafill a successful and a
non-zero value warning
as the RSDTIDX. message is
generated at the
MAP.
Table history
NA010
This table was created.
297-8021-351 Standard 05.02 May 2001

RSFOR
Table name
ITOPS Rating Rate Step Calculator Foreign Rating Table
International Traffic Operator Position System table RSFOR associates
combinations of schedule set name and foreign called number digits with a
schedule name and rate step. This table is used after the digit translation tables
determine that a called number is foreign.
The schedule set name is obtained from table CLGSSET by indexing into it
with the calling number digits. The system then uses the name and rate step to
calculate charges, starting with table CHGHEAD.

The following tables must be datafilled before table RSFOR:
SCHEDEF
SCHNAME
SSETNAME
Table size
Table RSFOR is a digilator table. The table compresses and uncompresses the
digits to reduce the amount of memory used. The maximum number of tuples
is determined by the memory allocation of the compressed digit datafill.
Datafill
The following table lists datafill for table RSFOR.
Subfield or
SCHSCC see subfields Schedule set-country code key. This field

consists of subfields SSETNAME and
DIGITS.
SSETNAME alphanumeric Schedule set name. Enter a schedule set

(1 to 16 name that was datafilled in table SSETNAME.
characters)
RSFOR (end)
Subfield or
DIGITS vector of up to Foreign called number digits. Enter the

18characters foreign called number digits.
(0-9, N, B, C,
D, E, F)
SCHNAME alphanumeric Schedule name. Enter the schedule name

(1 to 16 that was datafilled in table SCHNAME. The
characters) combination of schedule name and rate step
must be found in table SCHEDEF with a
foreign termination type (field TERMTYPE =
FOREIGN).
RATESTEP 0 to 999 Rate step. Enter the rate step that was
datafilled in table SCHEDEF when field
TERMTYPE is FOREIGN.
Datafill example
The following example shows sample datafill for table RSFOR.
MAP display example for table RSFOR
SCHSCC SCHNAME RATESTEP

________________________________________________________
SSETNAMEA 33 FORSCHED1 321
SSETNAMEB 33 FORSCHED1 322
SSETNAMEC 33 FORSCHED1 323
SSETNAMED 33 FORSCHED1 324
SSETNAMEA 33078 FORSCHED2 510
SSETNAMEB 33078 FORSCHED2 511
SSETNAMEC 33078 FORSCHED2 512
SSETNAMED 33078 FORSCHED2 513
297-8021-351 Standard 05.02 May 2001

RSLOC
Table name
ITOPS Rating Rate Step Calculator Local Rating Table
International Traffic Operator Position System table RSLOC associates
schedule set names with a schedule name and rate step. This table is used after
the digit translation tables determine that a called number is a local national
number.
with the calling number digits. The system then uses the schedule name and
rate step to calculate charges, starting with table CHGHEAD.

The following tables must be datafilled before table RSLOC.
SCHEDEF
SCHNAME
SSETNAME
Table size
0 to 640 000 tuples
Datafill
The following table lists datafill for table RSLOC.
Field descriptions
Subfield or

characters)

(1 to 16 that was datafilled in table SCHNAME.
characters)
datafilled in table SCHEDEF when field
TERMTYPE is LOCAL.
RSLOC (end)
Datafill example
The following example shows sample datafill for table RSLOC.
MAP display example for table RSLOC
SSETNAME SCHNAME RATESTEP

________________________________________________________
SSETNAMEA LOCSCHED1 921
SSETNAMEB LOCSCHED1 922
SSETNAMEC LOCSCHED1 923
SSETNAMED LOCSCHED1 924
297-8021-351 Standard 05.02 May 2001

RSM
Table name
Remote Service Module Table
Table RSM is used by local or combined local/toll switches that are configured
for remote operation.
Datafill sequence
Table MTAMDRVE must be datafilled after table RSM.
Table size
0 to 100 tuples
Field descriptions
Field names, subfield names, and valid data ranges for table RSM are
described below.
Field descriptions for table RSM (Sheet 1 of 2)
Subfield or
RSM 0to127 or Remote service module number

0 to 511
Enter the number assigned to the remote
service module (RSM).
If the switch is an NT40, enter a number
between 0 and 127.
If the switch is a SuperNode, enter a number
between 0 and 511.
FRAME see subfields Line module frame

This field consists of subfields SITE and
FRAME.
RSM (end)
Field descriptions for table RSM (Sheet 2 of 2)
Subfield or

(4 characters)
Enter the remote site name where the RSM
is located. The first character of the entry for
the site name must be alphabetic.
FRAME 0to127 or Remote line frame module number

0 to 511
Enter the number of the primary remote line
frame module assigned to the RSM.
If the switch is an NT40, enter a number
between 0 and 127.
If the switch is a SuperNode, enter a number
between 0 and 511.
Datafill example
An example of datafill for table RSM is shown below.
The example shows datafill for a local SuperNode switch with one remote site
(MERV) equipped with one RSM on the primary remote line frame module 0.
Datafill example for table RSM
RSM FRAME
________________________________________________________
0 REM1 00
297-8021-351 Standard 05.02 May 2001

RSNAT
Table name
ITOPS Rating Rate Step Calculator National Rating Table
International Traffic Operator Position System table RSNAT associates
combinations of schedule set name and national toll called number digits with
a schedule name and rate step. This table is used after the digit translation
tables determine that a called number is national toll.
with the calling number digits. The system then uses the schedule name and
rate step to calculate charges, starting with table CHGHEAD.

The following tables must be datafilled before table RSNAT.
SCHEDEF
SCHNAME
SSETNAME
Table size
0 to 65 000 tuples
Datafill
The following table lists datafill for table RSNAT.
Subfield or
SCHSDN see subfields Schedule set-directory number key. This field

consists of subfields SSETNAME and
DIGITS.

characters)
DIGITS numeric National toll called number digits. Enter the

(1 to 18 digits) national toll called number digits.
RSNAT (continued)
Subfield or
OVERLAY see subfield Rate type and refinements. This field

consists of selector field RATETYPE.
RATETYPE SRA or Rate type. Enter SRA for a single rate area
VH method and datafill refinements SCHNAME
and RATESTEP.
Enter VH when a vertical-horizontal
coordinate rate step system is associated
with refinement SCHNAME.

(1 to 16 that was datafilled in table SCHNAME. The
characters) combination of schedule name and rate step
is found in table SCHEDEF with a national
termination type (field TERMTYPE =
NATIONAL).
datafilled in table SCHEDEF if field
TERMTYPE is NATIONAL.
Datafill example
The following example shows sample datafill for table RSNAT.
MAP display example for table RSNAT
SCHSDN OVERLAY
SSETNAME DIGITS RATETYPE SCHNAME RATESTEP
________________________________________________________
SSETNAMEA 1022 SRA SCHED1 300

SSETNAMEB 1021 SRA SCHED3 100
SSETNAMEC 1021 SRA SCHED4 400
SSETNAMED 1021 SRA SCHED5 600
297-8021-351 Standard 05.02 May 2001

RSNAT (end)
Table history
BCS36
Vertical-horizontal (V-H) option added to field RATETYPE.
RSSERV
Table name
TOPS Active Service Rating Table
Table RSSERV supports TOPS Queue Management System (QMS) global
service rating. It lists all the service rating systems in the switching unit. Table
RSSERV is the active table in the pairing of tables RSSERV and RSSERVI.
The active table is used by the software for call processing, therefore, changes
cannot be made to the active data while it is in use. The inactive table is used
to allow changes to the service rating table by the operating company during
normal working hours. The active table is compared with the data in the
inactive table and is automatically updated during low traffic periods.
During active call processing, table RSSERV retrieves a schedule name and
ratestep given a schedule set and service combination. Table RSSERV has a
two-part key consisting of a schedule set name and a service name. The
schedule set name is determined by datafill in table SSETNAME and
CLGSSET. The second part of the key, the service name, is determined by
datafill in table TQMSSERV or table SERVSCRN.
Each key in table RSSERV maps to a schedule name and a ratestep used for
that particular key. Schedule names are datafilled in table SCHNAME. If call
processing encounters a schedule set or service combination such that no tuple
is datafilled in table RSSERV, global rating is not able to calculate the ratestep
or the charges for the call. In this case, a nil charge and ratestep is returned.
Operator displays are updated during the process to indicate processing
milestones.

The following tables must be datafilled before table RSSERV:
SCHEDEF
SCHNAME
SERVNAME
SSETNAME
Table size
0 to 4096 tuples
297-8021-351 Standard 05.02 May 2001

RSSERV (continued)
The following error message is displayed if field SCHNAME is not datafilled

in table SCHEDEF.
SCHNAME NOT KNOWN TO TABLE SCHEDEF
The following error message is displayed if field SCHNAME in table

SCHEDEF is not datafilled with field TERMTYPE = SERVICE.
SCHEDULE TERMTYPE MUST BE SERVICE
The following error message is displayed if the value in field RATESTEP was
either less than the lower rate step or greater than the highest rate step fields
specified for the schedule name in table SCHEDEF.
RATESTEP OUT OF RANGE
The following error message is displayed if field SERVNAM has a value of

NILSERV or TOLLFREE.
INVALID SERVICE
Datafill
The following table lists datafill for table RSSERV.
Subfield or
KEY This field consists of subfields SSETNAME

and SERVNAM.

(1 to 16 name that is determined by datafill in table
characters) SSETNAME. This is the first part of the key.
SERVNAM alphanumeric Service name. Enter a service name that is

(1 to 8 determined by datafill in table SERVNAME.
characters) This is the second part of the key. Values
NILSERV and TOLLFREE cannot be
datafilled in field SERVNAME in table
RSSERV.
RSSERV (end)
Subfield or
SCHNAME alphanumeric Schedule name. Enter a schedule name that

(1 to 16 is datafilled in table SCHNAME.
characters)
RATESTEP 0 to 999 Rate step. Enter a ratestep from 0 to 999.

This ratestep must match the range defined
for field SCHNAME in table SCHEDEF.
Datafill example
The following example shows sample datafill for table RSSERV.
MAP display example for table RSSERV
KEY SCHNAME RATESTEP

________________________________________________________
HONDURAS TOLLDA CTRDA 67
Table history
BCS35
Table RSSERV introduced.
297-8021-351 Standard 05.02 May 2001

RSSERVI
Table name
TOPS Inactive Service Rating Table
Table RSSERVI supports TOPS Queue Management System (QMS) global
service rating. It lists all the inactive service rating systems in the switching
unit. Table RSSERVI is the inactive table in the pairing of tables RSSERV and
RSSERVI. The active table is used by the software for call processing,
therefore, changes cannot be made to the active data while it is in use. The
inactive table is used to allow changes to the service rating table by the
operating company during normal working hours. The active table is
compared with the data in the inactive table and is automatically updated
during low traffic periods.
Table RSSERVI has a two-part key consisting of a schedule set name and a
service name. The schedule set name is determined by datafill in table
SSETNAME and CLGSSET. The second part of the key, the service name, is
determined by datafill in table TQMSSERV or table SERVSCRN.
Each key in table RSSERVI maps to a schedule name and a ratestep used for
that particular key. Schedule names are datafilled in table SCHNAME. If call
processing encounters a schedule set or service combination such that no tuple
is datafilled in table RSSERVI, global rating is not able to calculate the ratestep
or the charges for the call. In this case, a nil charge and ratestep is returned.
Operator displays are updated during the process to indicate processing
milestones.
For related information, refer to table RSSERV.

The following tables must be datafilled before table RSSERVI:
SCHEDEF
SCHNAME
SERVNAME
SSETNAME
Table size
0 to 4096 tuples
RSSERVI (continued)
The following error message is displayed if field SCHNAME is not datafilled

in table SCHEDEF.
SCHNAME NOT KNOWN TO TABLE SCHEDEF
The following error message is displayed if field SCHNAME in table

SCHEDEF is not datafilled with field TERMTYPE = SERVICE.
SCHEDULE TERMTYPE MUST BE SERVICE
The following error message is displayed if the value in field RATESTEP was
either less than the lower rate step or greater than the highest rate step fields
specified for the schedule name in table SCHEDEF.
RATESTEP OUT OF RANGE
The following error message is displayed if field SERVNAM has a value of

NILSERV or TOLLFREE.
INVALID SERVICE
Datafill
The following table lists datafill for table RSSERVI.
Subfield or
KEY This field consists of subfields SSETNAME

and SERVNAM.

(1 to 16 name that is determined by datafill in table
characters) SSETNAME. This is the first part of the key.
SERVNAM alphanumeric Service name. Enter a service name that is

(1 to 8 determined by datafill in table SERVNAME.
characters) This is the second part of the key. Values
NILSERV and TOLLFREE cannot be
datafilled in field SERVNAME in table
RSSERVI.
297-8021-351 Standard 05.02 May 2001

RSSERVI (end)
Subfield or
SCHNAME alphanumeric Schedule name. Enter a schedule name that

(1 to 16 is datafilled in table SCHNAME.
characters)
RATESTEP 0 to 999 Rate step. Enter a ratestep from 0 to 999.

This ratestep must match the range defined
for field SCHNAME in table SCHEDEF.
Datafill example
The following example shows sample datafill for table RSSERVI.
MAP display example for table RSSERVI
KEY SCHNAME RATESTEP

________________________________________________________
HONDURAS TOLLDA CTRDA 67
Table history
BCS35
Table RSSERVI was introduced.
RTECHAR
Table name
ISDN Routing Characteristic Table
Table RTECHAR associates a routing characteristic name (RCNAME) to
several routing characteristics. The system uses RCNAME through
translations and routing to select a route. The system selects a route according
to the routing characteristics of the call.
Routing characteristics bearer capability (BC) and peripheral interface (PI)

apply to Japan Public Network 7 (JPN7) ISDN user part (ISUP).
When a caller places an ISDN call, the system transmits an information

element (IE) to the DMS central office switching center.
Note: The system accesses table RTECHAR when a caller places

non-ISDN calls. Entries in table RTECHAR can define bearer capabilities.
Non-ISDN calls with a specified bearer capability use table RTECHAR.
Non-ISDN calls use table RTECHAR to obtain an RCNAME for re-routing
and re-translation purposes.
The message SETUP is part of the information element. When the system
receives message SETUP, the system accesses table RTECHAR. The system
searches table RTECHAR for the RCNAME in the transmitted message
SETUP. Table RTECHAR contains a list of RCNAMEs where each
RCNAME has an assigned set of routing characteristics. If the system cannot
find an RCNAME for a specified set of routing characteristics, the default
value applies. The system associates the default value of NILNAME with the
call. The default value of NILNAME appears in table RTECHAR.
Each routing characteristic has an internally defined default value. When a

customer adds a tuple that contains the default value, and lists the tuple, the
default value does not appear.

Enter data in the following tables after you enter data in table RTECHAR.
RCNAME
BCDEF
Enter data in the ISDN translations tables to initiate full ISDN translations.
297-8021-351 Standard 05.02 May 2001

RTECHAR (continued)
DMS 100E
Set office parameter NUM_RC_EXT_BLKS in table OFCENG to one or
more. If office parameter NUM_RC_EXT_BLKS does not have a value of one
or more the system routes calls that use this parameter to treatment.
DMS 300
DMS 300 does not use RC_EXT_BLKS.
Table size
0 to 256 tuples
The system dynamically allocates data store for each tuple in table
RTECHAR.
Datafill
Datafill for table RTECHAR appears in the following table.
Subfield or
RCKEY see subfield Routing characteristic key

This field contains subfield RCNAME.

(1 to 8 Enter the RCNAME that is a correct entry in table
characters) RCNAME.
GROUPRC see subfields Group routing characteristic

This field contains subfields FIRSTRC and
OTHERRC. Each RCKEY can have one to seven
GROUPRCs assigned.
FIRSTRC see subfields First routing characteristic

Enter values for the first routing characteristic.
This subfield contains refinement RCSEL. A
group routing characteristic can have one first
routing characteristic assigned.
RTECHAR (continued)
Subfield or
RCSEL BC, CDN, Routing characteristic selector

OSA, PI, SR, Enter one of the entries with the associated
or TNS refinements. Descriptions of the refinements
appear in alphabetical order in the following list.
Enter BC (bearer capability). Enter data in
refinement BC.
Enter CDN (called party number). Enter data in
refinement CDNTON.
Enter OSA (operator system access). Enter data
in refinement OSA.
Enter PI (protocol preference indicator). Enter
data in refinement PI.
Enter SR (service request). Enter data in
refinement SR.
Enter TNS (transit network selection). Enter data
in refinement TNSTON.
BC alphanumeric Bearer capability name

(1 to 16 If the entry in subfield RCSEL is BC, enter data in
characters) this refinement. Enter the bearer capability name
as entered in table BCDEF.
The default entry is 3_1KHZ.
Go to subfield OTHERRC.
297-8021-351 Standard 05.02 May 2001

RTECHAR (continued)
Subfield or
CDNTON ABBR, IN, L, Called party number type of number

NA, NET, or If the entry in subfield RCSEL is CDN, enter data
NIL in this refinement. Enter the required CDN type of
number. The entry values appear in the following
list:
Entry ABBR indicates the presence of a called
number that contains an abbreviated number.
Entry IN indicates the presence of an
international number.
Entry L indicates the presence of a called
number that contains a 7-digit public number.
Entry NA indicates the presence of a called
number that contains a 10-digit public number.
Entry NET indicates the presence of a called
number that contains a variable private
number.
Entry NIL indicates the CDN. Information
element (IE) is not present. Digits can be in
the keypad IE or the TNS IE.
OSA NIL, PRIP, Operator system access

PUBA, or If the entry in subfield RCSEL is OSA, enter data
PUBP in this refinement. Enter the required operator
system access (OSA) selector. The entry values
appear in the following list:
The NIL represents the OSA. The IE is not
present.
The PRIP represents the attendant of a
business group.
The PUBA represents the inter-LATA carrier
operator.
The PUBP represents the operating company
operator.
RTECHAR (continued)
Subfield or
PI SUPREF Protocol preference indicator

SUPREQ or If the entry in subfield RCSEL is PI, enter data in
NOISUPRQ this refinement. Enter the required number of
protocol preferences ISUPREQ, ISUPREF, or
NOISUPRQ.
SR CFW, CLI, Service request

CUG, NIL, or If the entry in subfield RCSEL is SR, enter data in
NND this refinement. Enter the required type of service
request (SR). The entry values appear in the
following list:
The CFW (call forwarding with reason)
The CLI (calling line identity)
The CUG (closed user group)
The NIL represents the SR. The IE is not
present.
The NND (network name display)
TNS NA, NIL, or Transit network selection

US If the entry in subfield RCSEL is TNS, enter data
in this refinement. Enter the required type of
transit network selection (TNS) selector. The
entry values appear in the following list:
The NA represents the presence of public
carrier digits.
The NIL represents the TNS. The IE is not
present.
The US represents the presence of private
carrier digits.
297-8021-351 Standard 05.02 May 2001

RTECHAR (continued)
Subfield or
OTHERRC see subfield Other routing characteristic

This field specifies the other routing characteristic
of a grouping. This field does not specify the first
routing characteristic (field FIRSTRC). This field
contains subfield SEL. Each entry in field
FIRSTRC can have a maximum of three entries
assigned. These entries make a group routing
characteristic (GROUPRC).
SEL BC, CDN, Routing characteristic selector

OSA, PI, SR, Enter one of the entries with the respective
or TNS refinements. Descriptions of the refinements
appear in alphabetical order in the following
section.
Enter BC. Enter data in refinement BC.
Enter CDN. Enter data in refinement CDNTON.
Enter OSA. Enter data in refinement OSA.
Enter PI. Enter data in refinement PI.
Enter SR. Enter data in refinement SR.
Enter TNS. Enter data in refinement TNSTON.
BC alphanumeric Bearer capability name

(1 to 16 If the entry in subfield SEL is BC, enter data in this
characters) refinement. Enter the bearer capability name
entered in table BCDEF.
The default entry is 3_1KHZ.
CDNTON ABBR, IN, L, Called party number type of number

NA, NIL, or If the entry in subfield SEL is CDN, enter data in
NET this refinement. Enter the required CDN type of
number. For an explanation of entries, see earlier
refinement CDNTON.
OSA NIL, PRIP, Operator system access

PUBA, or If the entry in subfield SEL is OSA, enter data in
PUBP this refinement. Enter the required operator
system access (OSA) selector. For an
explanation of entries, see earlier OSA
refinement.
RTECHAR (continued)
Subfield or
PI ISUPREF Protocol preference indicator

ISUPREQ or If the entry in subfield SEL is PI, enter data in this
NOISUPREQ refinement. Enter the required number of protocol
preferences ISUPREQ, ISUPREF, and
NOISUPRQ.
SR CFW, CLI, Service request

CUG, NIL, or If the entry in subfield SEL is SR, enter data in this
NND refinement. Enter the required type of service
request (SR). For an explanation of entries, see
earlier refinement SR.
TNS NA, NIL, or Transit network selection

US If the entry in subfield SEL is TNS, enter data in
this refinement. Enter the required type of transit
network selection (TNS) selector. For an
explanation of entries, see earlier refinement TNS.
Datafill example
Sample datafill for table RTECHAR appears in the following example.
MAP example for table RTECHAR
RCKEY GROUPRC CONTMARK
________________________________________________________
NILNAME $ $
64KNAME BC 64KDATA $
BC 64KDATA SR CLI $
64KPUBP BC 64KDATA OSA PUBP $
$
64KPUB BC 64KDATA CDN L $
BC 64KDATA CDN NA $
BC 64KDATA TNS NA +
CDN NA +
OSA NIL $
RCNAME1 BC SPEECH SR CLLI $
ISUPONLY PI ISUPREQ $
ISUPPREF PI ISUPREF $
297-8021-351 Standard 05.02 May 2001

RTECHAR (end)
Table history
BCS36
Subfield RCNAME was added in BCS36.
RTSALGO
Table name
Return-to-Service Algorithm Table
Table RTSALGO improves the auditing algorithm by which the system-busied
nodes and links return to service. This improvement occurs when observing
the known hierarchical relationships between the different node types. Use the
NET_BRANCH algorithm if the network branch is critical. Use the
IOC_BRANCH algorithm if the input/output controller (IOC) branch is
critical. If any of the above algorithms are not present, use the default
algorithm, DEFAULT_BRANCH.
An algorithm is an array of node types. Nortel defines a set of algorithms when

the load is first built. Samples of algorithms appear in the following list.
Algorithm for the network branch
CMC_NODE NET_NODE TM_NODE CMC_NODE NET_NODE
LM_NODE
CMC_NODE NET_NODE DCM_NODE RCT_NODE RCS_NODE
RCU_NODE
Algorithm for the IOC branch
CMC_NODE IOC_NODE TDC_NODE CMC_NODE IOC_NODE
TC_NODE
RCT_NODE RCS_NODE RCU_NODE
Algorithm for the default branch
CMC_NODE IOC_NODE NET_NODE CMC_NODE IOC_NODE
TDC_NODE
CMC_NODE NET_NODE TM_NODE CMC_NODE IOC_NODE
TC_NODE
CMC_NODE NET_NODE DCM_NODE CMC_NODE
IOC_NODE DDU_NODE
CMC_NODE NET_NODE LM_NODE CMC_NODE IOC_NODE
DLC_NODE
CMC_NODE NET_NODE DCM_NODE RLM_NODE
CMC_NODE IOC_NODE
DPC_NODE RCT_NODE RCS_NODE RCU_NODE
See table RTSNT for associated information.
297-8021-351 Standard 05.02 May 2001

RTSALGO (continued)
Datafill sequence and meanings

RTSALGO.
Table size
The system automatically allocates memory for a maximum of four
return-to-service branches.
Datafill
Datafill for table RTSALGO appears in the the following table.
Field descriptions
Subfield or
RTSBRNCH see subfield Return-to-service algorithm key. This field

contains subfield RTS_BRNCH.
RTS_BRANCH COMBINED_ Return-to-service branch. Enter

BRANCH COMBINED_BRANCH for the algorithm in
DEFAULT_ use. This process occurs if the network branch
BRANCH and input/output controller (IOC) branch are
NET_ critical or not critical. The load does not
BRANCH or specify COMBINED_BRANCH. Use the
IOC_ DEFAULT_BRANCH.
BRANCH
Enter DEFAULT_BRANCH for the default
algorithm in use to return nodes to service if
the user does not specify any nodes.
Enter NET_BRANCH for the algorithm in use if
the network branch is critical.
Enter IOC_BRANCH for the algorithm in use if
the IOC branch is critical.
RTSVECT alphanumeric Return-to-service algorithm vector. The entry

(1 to 16 in this field is a string of node types. Add a
characters) maximum of 119 node types. If less than 119
node types are necessary, end the list with a $.
Datafill example
Sample datafill for table RTSALGO appears in the following example.
RTSALGO (end)
MAP example for table RTSALGO
RTSBRNCH RTSVECT
________________________________________________________
NET_BRANCH ( CPU_NODE) ( MS_NODE)$
Table history
BCS36
Subfield RTS_BRANCH was added in BCS36. The entry column for field
RTSVECT was corrected.
This section provides information on dump and restore procedures when you
add data entry to table RTSALGO.
Dump and restore

The removal of table RTSALGO from the system occurs. When this process
occurs, the algorithm that corresponds to the DEFAULT_BRANCH must
change to an empty vector. This change occurs because the software
determines the algorithm.
Before the restoration of table RTSALGO occurs, set the office parameter
RTSALGOWRITE in table OFCSTD to Y (yes). After the restoration of the
data occurs, set the parameter back to N (no) for write protection.
297-8021-351 Standard 05.02 May 2001

RTSNT
Table name
Return-to-service Node Types Table
The purpose of table RTSNT is to improve the method by which the
system-busied nodes and links return to service. This process occurs by
observing the known hierachical relationships between the different node
types.
The system keeps a set of queues, with each queue that corresponds to one
node type. The system awakens the audit process every minute. The audit
process steps through all nodes in the system. The audit process selects nodes
and links that are in the system busy state. A node is in the system busy state
or has system busied C-side link or links. When this condition occurs, the
system places the node in the queue that corresponds to its own node type. The
evaluation of the system occurs to determine if the system is critical. Every
node has a queue maximum (field QMAX) associated with the node. Field
QMAX specifies the maximum number of nodes of the node type that can be
on the return-to-service queue. This numbe00000r is the maximum number
before the system becomes critical. Table RTSNT contains the specifications
for QMAXs. A network pair is down or a line module (LM) and its mate are
down. These conditions constitute a critical condition.
While the audit system is active, the audit system first checks if the system is
critical. If the system is critical, the system will run at priority 5, not 1. This
process allows the system to operate more easily. The system begins to make
return to service attempts on nodes in the return-to-service queues. When
either of the branches is critical the system tries to repair that branch first.
Refer to table RTSALGO for related information.

RTSNT.
Table size
The number of tuples is a system parameter. The number of tuples depends
on the number of node types in the office.
RTSNT (continued)
Datafill
Datafill for table RTSNT appears in the following table.
Field descriptions
Subfield or
NODETYPE see subfield Node type key.

This field contains subfield NODE_TYPE.
NODE_TYPE alphanumeric Node type.

(1 to 12 Enter the node type of the different nodes and
characters) links.
QMAX 0 to 4095 Queue maximum.

Enter the maximum number of the node type
that are on a return-to-service queue. This
entry occurs before the system becomes
critical.
DEFAULT Y or N Default.
Enter Y if the system calculates a default
value for field QMAX. To use this option, you
must enter 0 in field QMAX.
Or, enter N. If the entry is N, set field QMAX
to any desired value except 0.
Datafill example
An example of datafill for table RTSNT appears in the following chart.
MAP example for table RTSNT
NODETYPE
QMAX DEFAULT
________________________________________________________
GMS_NODE
4095 Y
Table history
BCS36
Field NODETYPE was added in BCS36.
297-8021-351 Standard 05.02 May 2001

RTSNT (end)
This section provides information on dump and restore procedures when you
enter data in table RTSNT. This section provides a sample list of the node to
queue relationship that table RTSNT provides.
Dump and restore

The removal of table RTSNT from the system occurs for each node type.
When the system sets field DEFAULT to Y, change field QMAX to 0. The
software accepts this value when the default option is in use.
Node to queue relationship

Table RTSNT provides a sample list of the node to queue relationship that
appears in the following Table RTSNT.
Node/queue relationship in table RTSNT
NODETYPE QMAX DEFAULT
CPU_NODE 2 Y
MS_NODE 1 Y
NET_NODE 2 Y
TM_NODE 3 Y
LM_NODE 1 Y
DCM_NODE 1 Y
IOC_NODE 2 Y
TC_NODE 2 Y
SAAUTO
Table name
Automatic Service Analysis Table
Table SAAUTO defines when a session is in use for manual service

analysis (MSA) or automatic service analysis (ASA). When the session is
automatic, the table defines:
the analysis time intervals
the frequency of the analysis
the target number of calls to be sampled
the sampling criteria
Table SAAUTO allows the operating company to define how the system
presents output from the ASA session:
in a call-by-call report
a summary of the last 100 calls
both call-by-call and summary data.
Service analysis allows the operating company to monitor and analyze traffic
on the DMS switch. The MSA requires a dedication MSA position, which a
service analyst operates. The service analyst monitors the call and inputs
subjective data on the quality of service. The ASA allows the supervision of
traffic quality without a dedicated position or analyst. The collection of data
on internal and external problem occurs.. The ASA can not monitor the speech
path and enter analyst observed events.
At any time, a maximum of five service analysis sessions can be on the switch.
Define each session as either MSA or ASA. Identify each session by a fixed
number. Each session can monitor and analyze traffic separate from the other
session.
Each ASA session can have up to five slots defined. No two slots of the same
session can overlap. The slots can be next to the other slot.
The system supports ASA on the DMS-300 for the following gateway trunks:
IT (T101 testline)
PL (private line)
CCITT signaling system R1
297-8021-351 Standard 05.02 May 2001

SAAUTO (continued)
CCITT signaling system R2 (digital only)

CCITT signaling system No. 5
CCITT signaling system No. 6
CCITT signaling system No. 7, telephone user part (TUP) blue book
CCITT signaling system No. 7, TUP red book
T/SPS signaling system No. 7, TUP plus (TUP+)
CCITT signaling system No. 7, ISDN user part (ISUP) blue book
United Kingdom national user part (BTUP) (BTNR167)
Table SAAUTO is a change-only table.
See table SASPEC for associated information.
Target calls parameters

The DMS switch attempts to distribute the target number of calls evenly for a
session slot over the datafilled time period. The following conditions can
distort the distribution:
Low number of calls that require the sample process. The ASA monitors
up to ten calls at the same time. When a session set samples ten calls over
an hour, the switch can analyze all ten calls. The switch can analyze these
calls in the first few minutes. A session set to sample 600 calls over an hour
returns a distribution of approximately ten calls a minute.
Calls with a long average holding time. The longer the holding time of the
sampled calls, the lower the rate at which ASA samples.
Low levels of traffic of the required standards.
A long session of several hours with a high number of target calls (over 1000)
obtains optimum distribution.
The range of calls an ASA session samples is 0 to 4010.
Command SACONTROL
The command interpreter (CI) command SACONTROL queries the status and
change the settings of the service analysis system.

You must enter data in table SASPEC before you enter data in table SAAUTO.
SAAUTO (continued)
Table size
5 tuples
Datafill
Datafill for table SAAUTO appears in the following table.
Subfield or
SESSION see subfield Session. This field is the key to the table and
contains the subfield KEY.
KEY 1 to 5 Key. Enter the key to the table.
CONTROL see subfield Control. This field contains subfield MODE.
MODE AUTOMATIC Service analysis mode. Enter AUTOMATIC if

or MANUAL the system reserves the session for automatic
analysis and datafill refinement ASA.
Enter MANUAL if the system reserves the
session for manual analysis. The refinements
do not require datafill.
ASA see subfield Automatic service analysis. This field

contains up to five multiples of subfields
START, STOP, FREQ, TARGET,
OUTFORM, and SASPIND. Separate each
subfield with a single space. If less than five
multiples are required, end the list with a $.
START see subfields Start. This field contains subfields DATE and
TIME. Separate each subfield with a single
space.
DATE 1 to 366 Start date. Enter the day of the year at which
the session starts analysis.
TIME 0000 to 2359 Start time. Enter the time of the day at which
the session starts analysis. The format is
HHMM.
297-8021-351 Standard 05.02 May 2001

SAAUTO (continued)
Subfield or
STOP 0000 to 2359 Stop. Enter the time when the session stops
the analysis. The format is HHMM. The stop
time (field STOP) precedes the start time
(field START). When this process occurs, the
automatic service analysis (ASA) considers
the stop time to be in the next day.
FREQ DAILY Frequency. Enter the frequency of the

ONEOFF or analysis.
WEEKLY
TARGET 1 to 4000 Target. Enter the number of calls that require

the sample process for the analysis.
OUTFORM FULL Output form. Enter the form of output

PERCALL or required.
SUMMARY
Enter FULL for call-by-call and summary
data.
Enter PERCALL for data output on a
call-by-call base. Information includes
treatment or backward signals the system
applies or receives during the call.
Enter SUMMARY if a summary is output after
every 100 calls during the sample process, or
at the end of the analysis. The system
presents information in a packed hex format
for machine reading.
SASPIND 1 to 50 Table SASPEC index. Enter the index in

table SASPEC. The entry in this field
provides the selection standards for the ASA
session.
Datafill example
Sample datafill for table SAAUTO appears in the following example.
SAAUTO (end)
MAP example for table SAAUTO
SESSION
CONTROL
_____________________________________________________________________
5
AUTOMATIC (12 0400 0800 DAILY 3 FULL 16)
(3 0011 2359 WEEKLY 2000 SUMMARY 49) $
Table history
BCS36
Table SAAUTO was introduced in BCS36.
SAAUTO.
Dump and restore

297-8021-351 Standard 05.02 May 2001

SACB
Table name
Subscriber Activated Call Blocking (SACB)
Table SACB associates a North American call class to a string of destination
digits. Table SACB sets the call class based on the non-prefix digits.
Call classes IDDD, OPRA, TOLL, and ZROM are based on the prefix digits
of the dialed number and cannot be assigned in table SACB.
A new subscriber activated call blocking call class (SACBCC) FPBALLOW is

added for table SACB in NA011. The call class is described below:
The operating company can block all calls originated from a line by persons
who do not have the personal identification number (PIN) of the subscriber.
The call classes to be restricted are specified when adding SACB to the
subscriber line. FPB functionality can be added to a line through the subfield
SACBCC in a SERVORD session. When FPB is added to a line with other call
classes, FPB overrides the other call classes. Fraud Prevention Allow
(FPBALLOW) permits calls without a PIN. The operating company can enter
a small set of callable numbers without a PIN such as 911 or a repair number.
The callable numbers chosen by operating company personnel such as 911 or
611 are entered in subfield FPBALLOW in table SACB.
The restricted call classes are specified when adding the SACB option to the
subscriber line. The addition of the SACB option is done using the service
order system (SERVORD). The SACB feature is controlled by an access code.
The PIN assigned to the SACB feature activates or deactivates the feature.
The operating company is provided with a boolean function, SACB suspend

(SACBSUS). SACBSUS can be set to Y or N. SACBSUS set to Y compares
the dialed number with numbers entered in the FPBALLOW subfield. If the
numbers match, the call is allowed to proceed. If the numbers do not match, a
busy treatment is the result. If SACBSUS is set to N and FPB is on the line,
the dialed digits are compared with numbers entered in the FPBALLOW
subfield. If the digits match, the call is allowed to proceed. If the digits do not
match, the call is restricted and the PIN is required. If FPB is not on the line,
a check is made for other call classes.
Note 1: Emergency calls must complete, without regard to the SACB

restrictions assigned to the subscriber line. Therefore, 911 calls and calls
dialed as 0- complete provided they are datafilled against FPBALLOW in
table SACB.
SACB (continued)
Note 2: Subscriber activated call blocking is only valid for residential

(RES) or Meridian Digital Centrex (MDC) lines.

FPBALLOW affects the SACB data schema table.
There is no requirement to enter data in other tables before entering data in

table SACB.
Table size
0 to 32000
Memory is allocated dynamically.
Datafill
The following table lists datafill for table SACB.
297-8021-351 Standard 05.02 May 2001

SACB (continued)
Field descriptions
DIGITS numeric (up Digits

to 18 digits)
. Restricted to 8 digits .
Enter the digits that compare to the non-prefix
dialed digits. If the digits are an exact match,
the indicated call class is assigned. For
example, to assign a toll directory assistance
(TDAS) call class to a call dialed as
1+NPA-555-1212, enter NPA555 in field
DIGITS.
Note: To minimize the impact on real-time

translation, digit are checked one time. The
first digits reported from peripheral
processing to central control for translation
must match all the digits in field DIGITS as
digits.
SACBCC LDAS, TDAS, Subscriber activated call blocking call class

I800, I900,
I976,
FPBALLOW, Enter the subscriber-activated call blocking
FPB, TOLL, (SACB) call class from the following list:
ZROM,
LDAS (local directory assistance [411 or
OPRA, IDDD,
equivalent])
or SPEC
TDAS (toll directory assistance [all 1
555])
I800 (800 Information services)
FPBALLOW (fraud prevention blocking
allowed numbers)
SPEC (special [repair office or
maintenance])
Note: FPBALLOW holds the numbers for

calls that are allowed with FPB, for example,
911.
SACB (end)
Datafill example
The following example shows sample datafill for table SACB.
MAP display example for table SACB
DIGITS SACBCC
___________________________________________
411 LDAS
555 TDAS
611 SPEC
800 I800
900 I900
976 I976
911 FPBALLOW
297-8021-351 Standard 05.02 May 2001

SACODES
Table name
Service Analysis Codes (SACODES) Table
Table SACODES contains data that command CAT (category) in the MAP
(maintenance and administration position) in which directories GWSA and
SAEDIT uses or refers. The data in the table maps a two-digit code to a
different service analysis (SA) observational category. The service analysis
operators use codes to classify the effectiveness or ineffectiveness of a call.
When the operator enters the code through command CAT, the system
identifies the code in table SACODES. The observational category that the
code represents, appears on the SA MAP display.
A maximum of 90 numeric codes map to 90 observational categories. The

codes and categories are in table SACODES. The administrator can add,
delete or edit codes and categories.
Refer to the DMS-100 Family Commands Reference Manual for additional

information on command CAT.

SACODES.
Table size
90 tuples
Datafill
Datafill for table SACODES appears in the following table.
Field descriptions
Subfield or
SACODES 10 to 99 Service analysis codes.

This field is the key field for table SACODES.
Enter a number from 10 to 99.
CATEGORY alphanumeric Category. Enter the category.

(a maximum Each entry in field SACODES must have a
of 10 different entry in field CATEGORY.
characters)
The default is a blank string, ten spaces long.
SACODES (end)
Datafill example
Sample datafill for table SACODES appears in the following table.
MAP example for table SACODES
SACODES CATEGORY
________________________________________________________
10 OKNAS
Table history
BCS35
Table SACODES was introduced in BCS35.
297-8021-351 Standard 05.02 May 2001

SAIDOFC
Table name
Speech Activated Intelligent Dialing Optionality Table
This table controls software optionality for two new features, Speech
Activated Intelligent Dialing (SAID) Enhanced Signaling Protocol (AN0831)
and Network Facility Access (NFA) Stringing of Digits (SOD) (AN0434).
Adding tuples to table SAIDOFC activates these functionalities upon datafill.

There is no requirement to datafill other tables prior to table SAIDOFC. This
table is active upon initial program load.
Table size
Table SAIDOFC is statically allocated at 4 entries.
Datafill
The following table lists datafill for table SAIDOFC.
Field descriptions for table SAIDOFC
Subfield or
SAIDOPTN SAID_SOD SAID option

ASSV_CONTEXT
ASSV_QUERY
ASSV_PROGRAM Enter the name of the service to activate.
Datafill example
The following example shows sample datafill for table SAIDOFC.
MAP display example for table SAIDOFC
SAIDOPTN
________________________________________________________
SAID_SOD
ASSV_CONTEXT
In this example, SOD is allowed. Also, Assisted Service call context messages
will be sent, depending on the datafill of tables ASSVFEAT and ASSVLINK.
SAIDOFC (end)
However, Assisted Service query and program request messages will be

ignored.
Table history
NA002
Table SAIDOFC was created.
297-8021-351 Standard 05.02 May 2001

SAQSIZE
Table name
Service Assistant/In-charge Queueing Size Table
Table SAQSIZE associates a maximum queue depth with each team in a
switch. This table allows the operating company to datafill the depth of the
Service Assistance/In-charge (SA/IC) queue on a team basis. Initially, the
table is empty.
The operating company can datafill the queue size of each team independently.
The maximum queue size for each team is 16. If a team has a queue size of
16, a maximum of 16 SA/IC requests can be in queue for assistance for that
team at one. If the maximum number of requests are in queue, further operator
assistance requests result in a busy tone, indicating no assistance is available.
If the operating company datafills 0 (zero) as the entry in field SAQSIZE,

against a team number, no assistance requests can be queued in that team. If
this occurs, SA/IC queueing is in effect turned off.
If a team is not datafilled in table SAQSIZE, its queue size is assumed to be 1.
The key field is TEAMNO, which contains the valid key number in the office.
The first field is SAQSIZE. This is the maximum number of SA/IC requests
that can be queued at one time. If the queue is full, no further SA/IC requests
can be made until a slot opens up on the queue.
The second field is called SONALERT. This indicates when the sonalert is
turned on at the IC position. This occurs when an assistance request is queued,
an assistance request is deflected from the queue, or when the sonalert should
not be activated in response to SA queuing.

There is no requirement to datafill other tables prior to table SAQSIZE.
This table must be datafilled after the office parameter,

TOPS_NUM_TRAFFIC_OFFICES in table OFCENG. This parameter
specifies the number of teams that can be datafilled in field TEAMNO.
Table size
0 to 30 tuples
SAQSIZE (continued)
Datafill
The following table lists datafill for table SAQSIZE.
Field descriptions
Subfield or
TEAMNO see subfield Team number. This field consists of subfield

SAQ_KEY.
SAQ_KEY 0 to 30 Service assistant/in-charge request queue

key. Enter a number to represent the team
number. Team number 0 (zero) is invalid.
SAQSIZE 0 to 16 Service assistant/in-charge request queue

size. Enter a number that represents the
maximum number of SA/IC (Service
assistant/in-charge) requests that can be
queued at one time. If the queue is full, no
further SA/IC requests can be made until a
slot opens in the queue.
SONALERT 0 to 16 Sonalert. Enter the threshold value that

indicates when the sonalert should be
activated. The sonalert is activated at the
in-charge (IC) operator position if the number
of requests in the IC team's queue is equal to
or exceeds the threshold value. The sonalert
threshold value cannot exceed the queue size
for the team.
Datafill example
The following example shows sample datafill for table SAQSIZE.
The example consists of three teams.

Team 1 has an SA/IC request queue size of 8. This means only eight
operator positions may be queued for assistance. After eight positions are
in queue, the queue is full, and further general assistance requests can not
be queued. Operators making these requests hear busy tone. The last field
of the first tuple shows that, for team 1, the sonalert is activated on team 1's
IC position when at least four assistance requests are in queue.
Team 2 has the maximum SA/IC request queue size of 16. This means 16
operator positions may be queued for assistance. After 16 positions are in
queue, the queue is full, and further general assistance requests can not be
queued. Operators making these requests hear busy tone. The sonalert
297-8021-351 Standard 05.02 May 2001

SAQSIZE (end)
threshold field is datafilled as 0 (zero). This means that, for team 2, the
sonalert is not activated due to queued assistance requests. The sonalert
can still be activated for other conditions that can arise during call traffic
such as centralized automatic message accounting (CAMA) suspension,
25% controlled traffic, and others.
Team 3 has a queue size of 0 (zero). This effectively turns off SA/IC
queueing for a team. If an SA/IC is not immediately available, the
requesting operator hears busy tone.
MAP display example for table SAQSIZE
TEAMNO SAQSIZE SONALERT

________________________________________________________
1 8 4
2 16 0
3 0 0
SASPEC
Table name
Service Analysis Specification Table
Table SASPEC defines the selection standards of calls that require analysis for
the Automatic Service Analysis (ASA) system.

SASPEC.
Table size
0 to 50 tuples
Datafill
Datafill for table SASPEC appears in the following table.
Subfield or
SASPIND numeric Service analysis specification indicator

(1 to 50) This field is the key to table SASPEC. Enter a
numeric value to specify the service analysis
specification indicator.
SG GW Signaling group
Enter GW to specify the signaling group that
applies for Automatic Service Analysis (ASA).
ICSELTYP ANY, CCT, or Incoming call selection type

TT Enter data in this field to specify the incoming
call selection type. The description appears in
the following list:
If any call can proceed through, enter ANY.
If selection by circuit is a requirement, enter
CCT and datafill refinements GROUP and
EXTERN.
If selection by signaling type is a
requirement, enter TT.
297-8021-351 Standard 05.02 May 2001

SASPEC (continued)
Subfield or
GROUP alphanumeric Trunk group

(1 to 16 Enter data in this field if the value in field
characters) ICSELTYP is CCT.
Enter a character string to specify a trunk group.
EXTERN numeric External circuit number

(0 to 9999) Enter data in this field if the value in field
ICSELTYP is CCT.
Enter a numeric value to specify the external
circuit number. If an external circuit number is
not a requirement, leave this field blank.
OGSELTYP ANY, CCT, or Outgoing call selection type

TT Datafill this field to specify the outgoing call
selection type. The description of this process
appears in the following list:
If any call can proceed through, enter ANY.
If selection by circuit is a requirement,
enter CCT and enter data in refinements
GROUP and EXTERN.
If selection by signaling type is a
requirement, enter TT.
GROUP alphanumeric Trunk group

(1 to 16 Enter this field if the value in field ICSELTYP is
characters) CCT.
Enter a character string to specify a trunk group.
EXTERN numeric External circuit number

(0 to 9999) Enter data in this field if the value in field
ICSELTYP is CCT.
Enter a numeric value to specify the external
circuit number. If an external circuit number is
not a requirement, leave this field blank.
SASPEC (continued)
Subfield or
DIGSEL ANY or SEL Digit selection type

Enter data in this field to specify the digit
selection type. The description of this process
appears in the following list:
If digit selection does not occur, enter ANY.
If selection is a requirement, enter SEL.
Enter refinements ICOFFTYP,
OCOFFTYP, and DIGITS. This option is
available to offices with the optional digit
selection feature package, NTXU16.
ICOFFTYP NATL, INTL, or Incoming call connected office type selection

TIEROUTE Enter data in this field if the value in field
ICSELTYP is CCT. The description of this
process appears in the following list:
Enter NATL if the incoming call that
connects the office type is national.
Enter INTL if the incoming call that connects
the office type is international.
Enter TIEROUTE if the incoming call that
connects the office type is tie route.
OCOFFTYP NATL, INTL, or Outgoing call connected office type selection

TIEROUTE Enter data in this field if the value in field
ICSELTYP is CCT. Entry values for this field
appear in the following list:
Enter NATL if the outgoing call that connects
to office type is national.
Enter INTL if the outgoing call that connects
to office type is international.
Enter TIEROUTE if the outgoing call that to
connects office type is tie route.
297-8021-351 Standard 05.02 May 2001

SASPEC (end)
Subfield or
DIGITS numeric 1 to 18 Digits

digits (0 to 9, B, Enter data in this field if the value in field
or C) ICSELTYP is CCT.
Enter one or more digits.
USRCLSS ANY, User class

SUBSCRIBER, Datafill this field to specify call selection based
or OPERATOR on the common calling party category of the call.
The description appears in the following list:
Enter ANY if a user class selection is not a
requirement.
Enter SUBSCRIBER if subscriber based call
selection applies. This option is available to
offices with the optional user class feature
package, NTXU16.
Enter OPERATOR if operator based call
selection applies. This option is available to
offices with feature package NTXU16.
Datafill example
Sample datafill for table SASPEC appears in the following example.
MAP example for table SASPEC
SASPIND SG
________________________________________________________
1 GW ANY ANY ANY SUBSCRIBER

2 GW CCT ISUP2W TT C7 ANY OPERATOR
3 GW TT R1 CCT N5OG 8 INTL NATL A123 ANY
4 GW CCT TUP2W 1 ANY INTL NATL 12 ANY
5 GW ANY TT TUP ANY SUBSCRIBER
6 GW TT C7 TT C7 INTL INTL 444 ANY
7 GW CCT R1IC 2 CCT R1OG 4 NATL NATL 555 ANY
Table history
BCS36
Table SASPEC was introduced according to feature AE1125.
SATOVER
Table name
Double Satellite Override Table
Table SATOVER lists common language location identifiers (CLLI). The
CLLI belong to trunk groups connected to a distant office through a satellite
link. These trunk groups connect to each other.
An incoming trunk group receives signals through a satellite link. The system
does not normally permit trunk group to connect to an outgoing trunk group
that transmits signals through satellite. Table SATOVER uses an override field
to define when the connection can occur. An attempt to create a connection of
this type provides access to table SATOVER. If the trunk groups do not
connect to a distant end through a satellite link, access to this table does not
occur.

You must enter data in table CLLI before you enter data in table SATOVER.
Table size
0 to 8192 tuples
The maximum size of this table is 8192 tuples. The highest ADNUM value of
a CLLI determines storage for table SATOVER. The highest ADNUM value
rounds to the nearest multiple of 32.
297-8021-351 Standard 05.02 May 2001

SATOVER (continued)
Datafill
Datafill for table SATOVER appears in the following table.
Subfield or
FROM$TO see subfields From CLLI to CLLI.

This field contains subfields CLLIA and CLLIB.
CLLIA alphanumeric First from or to CLLI.

(1 to 16 Enter the CLLI of a trunk group that connects to
characters) or the distant office through a satellite link. This
ALL CLLI must appear as an entry in table CLLI.
Allow trunk groups that connect to the distant
office through a satellite link the following
condition. Allow these trunk groups to connect to
a specified trunk group that also connects to the
distant office through a satellite link. If this
condition occurs, enter ALL in this field and enter
data in table CLLI to add the CLLI value ALL.
SATOVER (end)
Subfield or
CLLIB alphanumeric Second from or to CLLI.

(1 to 16 Enter the CLLI of a trunk group that connects to
characters) or the distant office through a satellite link. This
ALL CLLI must appear as an entry in table CLLI. The
entry ALL is not correct for this field.
OVERRIDE Y or N Override.
Enter Y if a double satellite connection can occur.
Enter N if a double satellite connection cannot
occur. If the two CLLIs do not appear in the table,
the default value is N.
In general, a Y entry overrides an N entry.
Entries with an override of N do not occur
because N is the default. These entries do not
occur because the table does not contain two
CLLIs. The connection can occur if the same two
CLLIs appear two times in the table. If one of the
CLLIs contains an override of Y and the other
contains an override of N, the connection occurs.
This connection agrees with the last record entry.
Other entries that contain the value ABCD do not
determine if connections to or from ABCD occur.
This condition occurs if field CLLIA contains the
value ALL, field CLLIB contains the value ABCD,
and field OVERRIDE contains Y.
Datafill example
Datafill for table SATOVER appears in the following example.
MAP example for table SATOVER
FROM$TO OVERRIDE
________________________________________________________
ALL VCR01CAN Y
297-8021-351 Standard 05.02 May 2001

SAUSERS
Table name
Service Analysis Users Table
Switching units that have feature package NTX065 (Service Analysis) require
table SAUSERS. Table SAUSERS records switching unit-dependent data for
each service analysis user. Table SAUSERS identifies the MAP (maintenance
and administration position) location. Table SAUSERS provides monitor
information associated with each service analysis.
Service analysis assignment of the external trunk number and the code of the
trunk group can occur. Service analysis assignment occurs when the
monitored connection is a dedicated local trunk on a DMS-300 Gateway
switching unit.
A monitored connection can be a correct local or remote directory number

(DN), that is not on a DMS-300 Gateway switching unit. In this occurrence,
the system requires the following information:
a correct local or national DN, with prefix digits
a correct local direct DN dialback
a pretranslator name for the local or national DN
the serving numbering plan area (NPA) code entered in the pretranslator
memory that the system allocates for the maximum number of ten local or
remote monitor connections required for service analysis
The local billing DN entries in field BILLDN allow entry and validation of
variable length DNs (VARDN). The VARDN supports the Universal DN
format, which uses a maximum of 15 digits.
The remote monitor data in table SAUSERS includes field PIC. Field PIC
contains the abbreviated name of a carrier. The operator uses field PIC when
the dialback connection occurs over an outgoing access to carrier (ATC) trunk.
The default value is NOCAR. Entry of value NOCAR occurs in field PIC
when the dialback connection does not occur over an ATC trunk. The operator
enters the abbreviated name of the carrier. Correct PIC names are the names
entered in table OCCNAME.
Table SAUSERS defines the value DFLT as the default value for field
MONMODE.
SAUSERS (continued)
Table initialization
Table control initializes the ten entries in table SAUSERS with the default
values. Table control uses the default values that appear in the following table,
SAUSERS.
Default values in table SAUSERS
Field name Value
USER $
MONMODE DFLT

Enter data in tables PICNAME and OCCNAME before you enter data in table
SAUSERS.
Table size
10 tuples
The system allocates memory for the maximum number of local or remote
monitor connections assigned for service analysis. The maximum number of
local or remote monitor connections is 10.
Datafill
Datafill for table SAUSERS appears in the following tables.
Field descriptions
Subfield or
KEY 0 to 9 Key.
Enter the index in table SAUSERS. Entries
out of this range are correct.
USER alphanumeric User.

(1 to 8 Enter the login identifier of the service
characters) analysis user.
SAMODATA see subfields Service analysis monitor data.

This field contains subfields MONMODE,
CLLI, EXTERN, PIC, DBKDN, BILLDN,
SNPA, and PRTRN. The subfields that apply
depend on the monitor connection type.
297-8021-351 Standard 05.02 May 2001

SAUSERS (continued)
Default monitor connection

If the monitor connection is a default for a tuple that is not in use, the datafill
for field MONMODE appears in the following table.
Subfield or
MONMODE DFLT Monitor mode. Enter DFLT for the

MONMODE field. If field MONMODE
contains DFLT, you do not need to enter data
in other subfields. See tables Table , "Field
descriptions for conditional datafill" on page
-839 and Table , "Field descriptions for
conditional datafill" on page -840 for the entry
of data in other entries.
Local dedicated trunk monitor connection

If the monitor connection is a local dedicated trunk on a DMS-300 Gateway
switching unit, enter data in fields MONMODE, CLLI and EXTERN. The
datafill for these tables appears in the table.
Subfield or
MONMODE LOCL Monitor mode. Enter LOCL for the monitor

mode.

(1 to 16 the code of the trunk assigned to service
characters) analysis in table CLLI.
EXTERN 0 to 9999 External trunk number. Enter the external

trunk number of the trunk assigned to service
analysis.
Directory number trunk monitor connection

The monitor connection can occur as a correct local or remote DN that is not
on a DMS-300 Gateway switching unit. If this condition occurs, enter data in
SAUSERS (continued)
fields MONMODE, PIC, DBKDN, BILLDN, SNPA, and PRTRN. The datafill
for these field appears in the following table.
Subfield or
MONMODE REM Monitor mode. Enter REM for the monitor

mode.
PIC vector to a Primary inter-LATA carrier. Enter the PIC for

maximum of a remote dialback connection over an
16 characters outgoing ATC trunk. The carrier defines the
PIC. Enter NOCAR for other outgoing trunk
type. Entries must match the entries in table
OCCNAME.
DBKDN vector (to a Dialback directory number. Enter the 7-digit

maximum of DN if the dialback DN is local. Enter the
18 digits) 10-digit DN if the dialback DN is direct
distance dialing (DDD). If required, add the
prefix digits.
BILLDN vector to a Billing directory number. Enter the local DN

maximum of where a DDD dialback charge occurs. This
15 entries (N, field allows entry of variable-length local
0 to 9, B, C, D, billing DNs when the Universal DN system is
E, F) active in office parameter
ACTIVE_DN_SYSTEM.
SNPA vector to a Serving numbering plan area. Enter the NPA

maximum of the system uses to translate the dialback DN.
7 entries (0 to
9 and A to F)
PRTRN alphanumeric Pretranslator name. If pretranslation of the

(1 to 4 dialback DN is a requirement, enter the
characters) pretranslator name. Enter NPRT if
or NPRT pretranslation of the dialback DN is not a
requirement.
Datafill example
Datafill for table SAUSERS appears in the following example.
297-8021-351 Standard 05.02 May 2001

SAUSERS (end)
MAP example for table SAUSERS
KEY USER SAMODATA

________________________________________________________
0 OPERATOR LOCL HSET 1

1 REMOTE1 REM MCI 14169671111 5258321 613 P621
Table history
NA005
The following changes were made to table SAUSERS:
The value for field BILLDN was changed to allow for variable-length
billing DNs in NA005.
The value for field SNPA was changed, to allow for variable-length billing
DNs in NA005.
SCAICOMS
Table name
Switch/Computer Application Interface Communications
Table SCAICOMS defines a linkset for use by a switch/computer application
interface (SCAI) group. This table allows the configuration of SCAI links on
a multiprotocol controller (MPC) card. The MPC, link, calling address, and a
closed user group protocol for each link must be datafilled. This table allows
the configuration of SCAI links on an MPC as well as on an Ethernet interface
unit (EIU).
The linksets can either be X.25 linksets or transmission control protocol (TCP)
linksets. A TCP linkset uses the Internet protocol (IP) address of the customer.
The TCP/IP uses a TL1 interface to provide connectivity between the
DMS-100 switch and a business computer. The TCP/IP uses a local area
network (LAN) and internet router. The EIU provides LAN connectivity to the
DMS-100 switch. Each TCP connection matches to a linkset.

The following tables must be datafilled before Table SCAICOMS:
MPC
MPCLINK
Table size
0 to 224 tuples
Note: Up to 128 of the total 224 tuples can have X.25 linksets; up to 96
tuples can have TCP linksets.
Datafill
The following table lists datafill for Table SCAICOMS.
LINKSET alphanumeric Link set name. Enter the name of the linkset.
(up to 16
characters)
SCAILNKS see subfield SCAI links. This field contains subfield LNKSEL.
297-8021-351 Standard 05.02 May 2001

SCAICOMS (continued)
LNKSEL X25, TCP Link set selector. Enter the transport protocol used
for the linkset. Field LNKSEL includes subfields
CHNLS, MINALARM, and MAXALARM.
Enter X25 to specify an X.25 CompuCALL link and
see fields DEVICE, MPCNO, LINK, REMDA,
PROTOCOL, and LINKTYPE.
Enter TCP for the CompuCALL Transport
Enhancements feature, and see subfields IPADDR
and MULTIMSG.
CHNLS 1 to 8 Channels. If LINKSEL = X25, enter the number of

link selectors within a linkset. This field includes
subfield DEVICE.
MINALARM MN, MJ, CR Minimum alarm. If LINKSEL = X25, enter the alarm
status for the minimum alarm.
MAXALARM MN, MJ, CR Maximum alarm. If LINKSEL = X25, enter the

alarm status for the maximum alarm.
DEVICE MPC Device. If LINKSEL = X25, enter MPC for the

device that supports the controller. (Only the MPC
is supported.) This subfield includes refinements
MPCNO, LINK, REMDNA, PROTOCOL, and
LINKTYPE.
MPCNO 0 to 255 MPC number. If DEVICE = MPC, enter the MPC

number used. This MPC number must be defined
in table MPC.
LINK 2 or 3 Link number. If DEVICE = MPC, enter the MPC link

that is used. The link number must be datafilled in
Table MPCLINK.
REMDNA 0 to 9 (up to 15 Calling data network address. If DEVICE = MPC,

digits) enter the calling data network address.
PROTOCOL 0 to 255 Protocol. If DEVICE = MPC, enter any relevant

protocol data.
LINKTYPE SVC, PVC Type of virtual circuit. If DEVICE = MPC, enter SVC
(switched virtual circuit).
IP_ADDR 0 to 255 IP address. If LINKSEL = TCP, enter the IPADDR

of the customer; for example, ### ### ### ###,
where # is a digit ranging from 0 to 9 and a space
is entered after every 3 digits.
MULTIMSG Y or N Multiple message. If LINKSEL = TCP, enter Y for

MULTIMSG. Otherwise, enter N.
OPTIONS NONMS, Options. This field identifies the option name. The
NMSPVT addition of options is for each linkset. Enter
NONMS or NMSPVT. The value for options not
selected is $ (not present).
Present or Not No network message service. Block network

Present messages for this linkset.The value NONMS
indicates the option is present. The value $
indicates the option is not present.
Present or Not NMS private. This option identifies VMS

Present application interfaces that send private DNs across
the link. The value NMSPVT indicates the option is
present and the DMS switch tries to send a private
DN across the link. The value $ indicates the option
is not present.
DNASSOC DNASSOC DN ASSOC. This option indicates that the DN

needs to be reassociated as a result of a
RESTART/SWACT occurring on the switch.
CONTAUD see subfield Continuity audit interval option. See subfields.
AUDINTVL 1 to 720 Audit interval. This parameter allows the minutes

for audit interval of the continuity test. If the value
is zero, the switch does not prompt the next
parameters.
RESPTIME 1 to 30 Response time. This parameter allows

provisioning of seconds the switch waits for a
response from the host computer.
NUMATMPT 1 to 10 Number of attempts. This parameter allows

provisioning for maximum times the switch sends a
continuity test message for a particular linkset.
TERMINET Y or N Termination. This parameter allows provisioning

for termination of a session.
297-8021-351 Standard 05.02 May 2001

ENHASSOC see subfield Enhanced association. This option allows

subscription to the ICM ACD DN Association Limit
feature.
NUMACDDN 1100 Number of automatic call distribution directory

numbers. The operating company chooses a value
for the NUMACDDN parameter. If the end user
provisions option ENHASSOC and the
NUMACDDN parameter, the end user can
associate up to the maximum value of the
NUMACDDN parameter.
Datafill example
The following example shows sample datafill for Table SCAICOMS.
MAP display example for Table SCAICOMS
LINKSET
SCAILINKS
________________________________________________________
LINKSET1
X25 (MPC ( 3 2 12345678 3 1 128 0 SVC) $)$ MN CR
$ (DNASSOC)$
LINKSET2
X25 (MPC ( 2 2 66778834 3 1 128 0 SVC) $)$ MN MJ
$
TCP_LINKSET1
TCP 47 192 40 120 N $
' (DNASSOC)$
Datafill related to ICM Message Waiting Activation/Deactivation

MAP display example for Table SCAICOMS
LINKSET
SCAILINKS OPTIONS
________________________________________________________
TCP_TB TCP 47 129 163 5 (ICMDATA (NONMS ) (NMSPVT) $
LINKSET1 X25 (MPC ( 3 3 123456789 0 0 0 0 SVC) (MPC 1 3

123456789 0 0 0 0 SVC)$ (ICMDATA (NONMS ) (NMSPVT) $) $
Datafill related to ICM ACD DN Association Limit

MAP example for Table SCAICOMS
LINKSET SCAILINKS OPTIONS

TCP1 TCP 192 136 141 205 N (ENHASSOC 50) $
X251 X25 (MPC (0 3 000000000000000 9 9 9 9 SVC) $) $ MN CR

(ENHASSOC 50) $
Datafill related to ICM Workqueue Re-Engineering

MAP example for Table SCAICOMS
TCPI TCP 192 136 141 201 N (CONTAUD 15 12 4 Y) $

X251 X25 (MPC (0 3 000000000000000 9 9 9 9 SVC) $) $ MN CR
(CONTAUD 15 12 4 Y) $

TCPI TCP 192 136 141 201 N (CONTAUD 15 12 4 Y) $
X251 X25 (MPC (0 3 000000000000000 9 9 9 9 SVC) $) $ MN CR
(CONTAUD 0) $
297-8021-351 Standard 05.02 May 2001

Table history
NA015
The ICM Logon Enhancements and Reengineering (59022453) feature adds
option DNASSOC to table SCAICOMS.
NA014
The Increasing the Maximum Number of ICM Sessions (59016386) feature
changes the maximum number of ICM sessions on TCP/IP links from 16 to 96.
The feature also changes the number of tuples in the SCAICOMS table from
144 to 224.
NA013
The ICM ACD DN Association Limit (59011953) feature adds option
ENHASSOC to Table SCAICOMS. Option ENHASSOC has the
NUMACDDN subfield.
NA012
The ICM Workqueue Reengineering (59006731) feature added option
CONTAUD to Table SCAICOMS. Option CONTAUD has the following
subfields:
AUDINTVL
RESPTIME
NUMATMPT
TERMINET
NA011
ICM Message Waiting Activation/Deactivation (AU3192) added the following
subfields to the OPTION field in Table SCAICOMS:
NONMS
NMSPVT
This release required the following changes:

Added a datafill example related to ICM Message Waiting
Activation/Deactivation.
Updated the field description table.
SCAICOMS (end)
NA008
This release made the following changes:
Added TCP as a valid value for field LNKSEL.
Added subfield IPADDR to field LNKSEL.
297-8021-351 Standard 05.02 May 2001

SCAIGRP
Table name
Switch Computer Application Interface Group Table
Table SCAIGRP stores all the switch computer application interface (SCAI)
groups within a switch. SCAI groups are logical entities that are associated
with a set of SCAI links and services. In BCS32, each SCAI group
corresponds to a Meridian Digital Centrex (MDC) customer group.
SCAI groups are defined by operating companies. Each SCAI group has a
password, network node identifier (ID) and business group ID (BGID). The
password must be identified by users at the establishment of a session. The
network node ID identifies the network node ID assigned to each SCAI group.
It uniquely identifies a specific switch within a set of public or private
switches. The BGID is used to map each business group to a SCAI group.

The following tables must be datafilled before table SCAIGRP.
BGDATA
SCAICOMS
The following tables must be datafilled after table SCAIGRP.

SCAISVID
LTDEF
Table size
0 to 256 tuples
SCAIGRP (continued)
Datafill
The following table lists datafill for table SCAIGRP.
Subfield or
SCAIGNAM alphanumeric Switch computer application interface group

(up to 16 name
characters)
Enter the name of the switch computer
application interface (SCAI) group.
PASSWORD alphanumeric Password

(up to 8
Enter the password assigned to the SCAI
characters)
group. This password must be specified at
any SCAI session association.
NETNODID 0 to 32 767 Network node identification

Enter the network node identification for each
SCAI group.
BGID 0 to 4 194 303 Business group identification

Enter the location of the business group
GRPNUM as identified in table BGDATA.
Note: Only local GRPNUMs in table

BGDATA can be used here.
OPTIONS see subfields Options

This field consists of subfields OPTIONS and
LINKSET.
297-8021-351 Standard 05.02 May 2001

SCAIGRP (continued)
Subfield or
OPTIONS LINKSET Options

FRANCE The options list for this table is a vector of one
multiple. Enter LINKSET to assign linksets to
a SCAI group. Enter FRANCE to assign the
NDI and NDS Mapping to ICM/CompuCALL
feature to a SCAI group.
LINKSETS alphanumeric Link sets

(up to 16
Enter up to eight link sets owned by a SCAI
characters)
group that is defined in table SCAICOMS.
Datafill this optional parameter only for
groups using X.25 links. If less than eight link
sets are required, end the list with a $ (dollar
sign).
Datafill example
The following examples shows sample datafill for table SCAIGRP.
MAP display example for table SCAIGRP
SCAIGNAM PASSWORD NETNODID BGID

OPTIONS
_______________________________________________________________________
COMK ABCD 1 LOCAL 1

(LINKSET ( SIDE0_L1) (SIDE1_L1) $)$
MAP display example for table SCAIGRP
MYSCAIGRP PASS 1 NATIONAL 1

OPTIONS
_______________________________________________________________________
(LINKSET ( TCP2 ) $) (FRANCE) $
SCAIGRP (end)
Table history
MMP14
Added value FRANCE to subfield OPTIONS to support activity 59019157.
297-8021-351 Standard 05.02 May 2001

SCAILNKS
Table name
Switch Computer Application Interface Link Table
Table SCAILNKS defines sets of primary rate access (PRA) D-channels that
can be associated with Automatic Call Distribution (ACD) operator positions
using table ACDTKMEM.

Table LTMAP must be datafilled before table SCAILNKS.
The D-channel must be defined in table LTMAP before datafilling table

SCAILNKS.
ACD operator positions must be defined in table ACDTKMEM before being

entered in table SCAILNKS.
If option SCAIRTE is datafilled in table SCAILNKS, table OFRT or table

IBNRTE must be datafilled for the option before datafilling table SCAILNKS.
Table size
1 to 32 tuples
Datafill
The following table lists datafill for table SCAILNKS.
Subfield or
LINKSET alphanumeric Link set

(up to 8
Enter up to 32 link set names, or enter
characters) or
SCAIDEF (switch computer application
SCAIDEF
interface default). If less than 32 link sets are
The default value for this field is SCAIDEF.
DCHNLS see subfield D-channels

This field consists of subfield PMTYPE. Up to
four D-channels can be entered. If less than
four channels are required, end the list with a
$ (dollar sign).
SCAILNKS (continued)
Subfield or
PMTYPE DTCI Peripheral module type

Enter DTCI (ISDN digital trunk controller).
DTCINO 0 to 511 ISDN digital trunk controller number

Enter the DTCI number of the D-channel.
DTCICTNO 0 to 19 ISDN digital trunk controller circuit number

Enter the DS-1 circuit number used for the
D-channel.
DTCICTTS 1 to 24 ISDN digital trunk controller circuit time slot

Enter the time slot of the DS-1 circuit number
used for the D-channel.
OPTIONS see subfield Options

This field consists of subfield OPTION. Up to
two options can be datafilled. If less than two
options are required, end the list with a $
(dollar sign).
OPTION SCAIRTE Option

BOCTIMEor $
If the entry in field LINKSET is SCAIDEF,
enter SCAIRTE and datafill refinements
TABNAME and INDEX.
BOCTIME is optional. Datafill refinement
TIME.Otherwise, enter $.
The default value for this subfield is
SCAIRTE.
TABNAME IBNRT2 Table name

IBNRT3
If the entry in subfield OPTION is SCAIRTE,
IBNRT4
ter the table name that the translations routes
IBNRTE
to for the SCAIDEF tuple.
OFRT2
OFRT3 Any entry outside the range indicated for this
OFRT4 OFRT field is invalid.
or TOPS
297-8021-351 Standard 05.02 May 2001

SCAILNKS (end)
Subfield or
INDEX 1 to 1023 Index

If the entry in subfield OPTION is SCAIRTE,
datafill this refinement. Enter the table route
reference index number in the route to which
translation routes.
TIME 1 to 16 Time
If the entry in subfield OPTION is BOCTIME,
datafill this refinement. Enter the validation
time, in seconds, for a validation query
initiated for a calling card number.
Datafill example
The following example shows sample datafill for table SCAILNKS.
The example shows that SCAIDEF has one D-channel datafilled. The
D-channel has an ISDN digital trunk controller (DTCI), the frame number is
2, the DS-1 circuit number is 7, and the time slot on the DS-1 circuit is 1.
Option BOCTIME is specified with a value of 4 s of validation time for a
calling card number validation query.
LNKSET1 has two D-channels datafilled. The first D-channel has a PMTYPE
of DTCI, the frame number is 0, the DS-1 circuit number is 5, and the time slot
on the DS-1 circuit is 10. The second D-channel has a PMTYPE of DTCI, the
frame number is 0, the DS-1 circuit number is 6, and the time slot on the DS-1
circuit is 3.
MAP display example for table SCAILNKS
LINKSET DCHNLS
OPTIONS
_________________________________________________________
SCAIDEF (DTCI 2 7 1) $
(SCAIRTE OFRT 10) (BOCTIME 4) $
LNKSET1 (DTCI 0 5 10) (DTCI 0 6 3) $

$
SCAIPROF
Table name
Switch Computer Application Interface Profile
Table SCAIPROF serves as a lookup table for switch computer application
interface (SCAI) CompuCALL service profiles. A service profile is a set of
CompuCALL messages and associated options that are available during a
CompuCALL session.
Table SCAIPROF uses the linksets entered in table SCAICOMS and the
subservice names in table SCAISSRV to make up a CompuCALL service
profile. The key field is PROFKEY.
Both Residential Enhanced Services (RES) and Meridian Digital Centrex

(MDC) event message sets cannot be subscribed to in the same SCAI profile
in table SCAIPROF. If one has been datafilled, the other will be denied.

The following tables must be datafilled before table SCAIPROF:
OFCOPT
SCAISSRV
SCAICOMS
Table size
0 to 1792 tuples
The total number of linksets is 224 (128 X.25 linksets plus 96 TCP linksets)
The maximum table size derives from the maximum number of service
identities (8) for each linkset, multiplied by the number of linksets (224) that
can be datafilled in table SCAICOMS.
Note: With NA014 release and up, the SCAIPROF table allows the user to
add service profiles for all 96 transmission control protocol (TCP) tuples.
297-8021-351 Standard 05.02 May 2001

SCAIPROF (continued)
Datafill
The following table lists datafill for table SCAIPROF.
Field descriptions
Subfield or
PROFKEY see subfields Profile key. This field is a two-part key that
identifies linkset and service profile
combinations. Field PROFKEY consists of
subfields LINKSET and SRVCID.
LINKSET alphanumeric Linkset name. Enter one of the linkset names

(1 to 16 from table SCAICOMS. For example, enter
characters) LINKSET1.
SRVCID 0 to 255 Service identity. Enter a service identity (ID)

number. Up to eight service IDs can be
entered for each linkset, but only one service
profile can be used at any time. The service
ID must be unique for each linkset and profile
combination.
PROFILE alphanumeric Profile Enter subservice names from table

(1 to 16 SCAISSRV. This field represents the
characters) CompuCALL service profile. Up to eight
service profiles can be configured for each
linkset. A service profile cannot be datafilled
with two subservice names from the same
CompuCALL service category (for example,
AEVENT1 and AEVENT2 that both derive
from category ACDEVENT in table
SCAISSRV). If less than six profiles are
Datafill example
The following example shows sample datafill for table SCAIPROF.
SCAIPROF (continued)
MAP display example for table SCAIPROF
PROFKEY PROFILE
________________________________________________________
SET1 1 (EVENT1) (ROUTE1) (TPQC10$) (ICCM10$) $
Table history
NA014
This release changes the SCAIPROF table to allow the user to add service
profiles for all of the 96 TCP tuples.
NA008
This release adds the default subservice names TPQC10$, ICCM10$,
CTXEVENT10$, and RESEVENT10$ for subfield PROFILE.
NA006
This release increases the number of service profiles for each linkset from six
to eight.
BCS35
Table SCAIPROF was introduced.
This section provides information on dump and restore procedures and the
datafill procedure for existing SCAI groups for table SCAIPROF.

Tables SCAISSRV and SCAIPROF replace the function provided by tables
SCAISRVC and SCAISVID. Manual entry of tables SCAISSRV and
SCAIPROF is required for BCS35. All CompuCALL messages from BCS34
are grouped into categories for BCS35.
297-8021-351 Standard 05.02 May 2001

SCAIPROF (end)
Datafill of existing SCAI groups

The following steps are required to datafill existing SCAI groups:
1. Make a list of the linkset(s) owned by a SCAI group and the required
CompuCALL messages assigned for the linkset(s).
2. If possible, find the subservice name(s) in table SCAISSRV that contain
all the messages from step 1. The fixed subservices facilitate this
procedure.
3. If messages from step 1 cannot be found in the existing subservice names
in table SCAISSRV, new subservice or existing subservice names can be
entered (or edited) into table SCAISSRV to include the additional
messages.
4. Make a list of the subservice names, from steps 2 and 3, to be subscribed
to by the SCAI group.
5. Enter the names of the linksets (step 1) and the list of subservice names
(step 4) in table SCAIPROF.
SCAISSRV
Table name
Switch Computer Application Interface Subservices Table
Table SCAISSRV acts as a reference table for CompuCALL service
categories. CompuCALL uses a switch-computer application interface (SCAI)
link to provide DMS-100 switch services to applications on a subscriber host
computer. One service is Intelligent Call Management (ICM). Table
SCAISSRV includes a series of boolean values that indicate the CompuCALL
messages provided for each subservice category. The key to Table SCAISSRV
is Field SUBSERV.
Table SCAIPROF uses the subservice names defined in Table SCAISSRV. The
subservice names build a service profile of the CompuCALL messages
available to a subscriber linkset. A service profile is a set of CompuCALL
messages available to a subscriber during a CompuCALL session.

There is no requirement to put data into other tables before table SCAISSRV.
Table size
40 to 255 tuples. The minimum size includes fixed subservices.
297-8021-351 Standard 06.02 July 2002

SCAISSRV (continued)
Datafill
The following table lists the fields, subfields, and data entry for table
SCAISSRV.
Field descriptions for table SCAISSRV
SUBSERV
Subservice names do not use the $ (dollar

sign). Current and future fixed subservice
names use the $. CompuCALL provides the
following fixed subservice names:
ACDEVENT11$, ACDEVENT12$,
CALLINIT07$, CTXEVENT07$,
CTXEVENT10$, CTXEVENT13$,
CTXEVENT34$, CTXEVENT35$,
DNQUERY07$, ICCM10$, ICCM13$
RESEVENT07$, RESEVENT10$,
RESEVENT13$, RESOURCE11$,
RESOURCE35$, ROUTING15$,
ROUTING34$, ROUTING35$,
SCAI3WC07$, SCAI3WC09$,
SCAI3WC14$, SCAIMWTI13$,
SCAICC08$, SCAICC09$, SCAIMWTI07$,
TPAC12$, TPAC13$, TPAC36$, TPCC08$,
TPCC09$, TPCC11$, TPCC14$, TPCC15$,
TPCC34$, TPCC35$, TPQC10$,
CPGEVENT14$
For example, the fixed subservice names in

34$ contain the equivalent BCS34
CompuCALL functions. The names in 35$
contain all possible messages and functions
available in BCS35.
Table SCAIPROF can contain the
subservice names if an SCAI group requires
messages and subfields in a given
CompuCALL service category.
SPROFILE see subfield Subservice profile contents. This field

includes subfield CATEGORY.

CATEGORY ACDEVENT, CompuCALL service category. Enter

CALLINIT, ACDEVENT.
CTXEVENT,
Enter ACDEVENT (Automatic Call
DNQUERY,
Distribution [ACD] line call event) and select
ICCM,
subfields as shown in the CATEGORY =
RESEVENT,
ACDEVENT section.
RESOURCE,
ROUTING, Enter CALLINIT (call initiation) and select
SCAICC, subfields as shown in the CATEGORY =
SCAIMWTI, CALLINIT section. CALLINIT is a default
SCAI3WC, tuple for Meridian Digital Centrex (MDC)
TPAC, CompuCALL.
TPCC,
Enter CTXEVENT (MDC line call event) and
TPQC,
select subfields as shown in the
CPGEVENT
CATEGORY = CTXEVENT section.
Enter DNQUERY (directory number [DN]

query) and select subfields as shown in the
CATEGORY = DNQUERY section.
DNQUERY is a default tuple for MDC
CompuCALL.
Enter CompuCALL integration with
Integrated Call Center Manager (ICCM) and
CATEGORY = ICCM section.
Enter RESEVENT (Residential Enhanced
Services [RES] line call event) and select
RESEVENT section. RESEVENT is a
default tuple for MDC CompuCALL.
Enter RESOURCE (resource) and select
RESOURCE section.
Enter ROUTING (custom call routing) and
CATEGORY = ROUTING section.
Enter SCAICC (SCAI call control) and select
SCAICC section.
297-8021-351 Standard 06.02 July 2002

Enter SCAIMWTI (SCAI message-waiting

indication) and select subfields as shown in
the CATEGORY = SCAIMWTI section.
SCAIMWTI is a default tuple for MDC
CompuCALL.
Enter SCAI3WC (SCAI three-way calling)

and select subfields as shown in the
CATEGORY = SCAI3WC section.
SCAI3WC is a default tuple for MDC
CompuCALL.
For BCS36 and up, enter TPAC (third party
agent control) and select subfields as shown
in the CATEGORY = TPAC section.
Enter TPCC (third party call control) and
CATEGORY = TPCC section.
Enter TPQC (third-party queue control) and
CATEGORY = TPQC section. All
parameters in category TPQC are required.
Enter CPGEVENT and select subfields as
shown in the CATEGORY=CPGEVENT
section.

CATEGORY = ACDEVENT
If the entry in subfield CATEGORY is ACDEVENT, select the subfields as
follows. See the ACD CompuCALL section of the Translations Guide for
more information.
Field descriptions for category=ACDEVENT
see subfield Functions. This field includes subfield

FUNCTION. You can select up to eleven
functions. If you select less than eleven
functions, end the list with a $ (dollar sign).
FUNCTION AGTLGDIN, Function. Enter CompuCALL messages.

AGTLGDOUT,
Enter AGTLGDIN (agent logged in) and
AGTNREADY,
select subfields ACDGROUP, POSID, and
AGTREADY,
select LOGINID as shown in the FUNCTION
CALLANSWR
= AGTLGDIN section.
CALLOFFR,
CALLQUED, Enter AGTLGDOUT (agent logged out) and
CALLREL, select subfields ACDGROUP and POSID as
AGTSETACT, shown in the FUNCTION = AGTLGDOUT or
EMKEVENT, AGTREADY section.
LOBEVENT
Enter AGTNREADY (agent not ready) and
select subfields ACDGROUP, POSID, and
WALKAWAY as shown in the FUNCTION =
AGTNREADY section.
Enter AGTREADY (agent ready) and select

subfields ACDGROUP and POSID as shown
in the FUNCTION = AGTREADY section.
Enter CALLANSWR (call answered) and
select subfields CPADIGS, NCALLID,
DEVICEID, ACDDN, CALLNGNO,
CHARGENO, CALLTYPE, ORIGDN,
PREVAPPL, HOSTCALD, ACDGROUP, and
FWDPARTY as shown in the FUNCTION =
CALLANSWR section.
Enter CALLOFFR (call offered) and select
subfields CPADIGS, NCALLID, ACDDN,
CALLNGNO, CHARGENO, CALLTYPE,
ORIGDN, PREVAPPL, HOSTCALD,
ACDGROUP, DEVICEID, and FWDPARTY
as shown in the FUNCTION = CALLOFFR
section.
297-8021-351 Standard 06.02 July 2002

Field descriptions for category=ACDEVENT
Enter CALLQUED (call queued) and select

subfields CPADIGS, NCALLID, ACDDN,
ACDGROUP, and FWDPARTY as shown in
the FUNCTION = CALLQUED section.
Enter CALLREL (call released) and select
subfields NCALLID, RELTYPE, ACDDN,
ACDGROUP, DEVICEID, and POSTCALL as
shown in the FUNCTION = CALLREL
section.
Enter AGTSETACT (agent set action) and

select subfields NTWSETACT, INTSTAT,
and ENHWAC as shown in the FUNCTION =
AGTSETACT section.
Enter EMKEVENT (emergency key event)

and select subfields NCALLID, AGTPOS,
AGTDN, SUPRVPID, SUPRVDN, and
AUXDN as shown in the FUNCTION =
EMKEVENT section.
Enter LOBEVENT (line of business call event)

and select subfields NCALLID, AGTPOS, and
LOBTIME as shown in the FUNCTION =
LOBEVENT section.
FUNCTION = AGTLGDIN
If the entry in subfield FUNCTION is AGTLGDIN, select the subfields as
follows.
Field descriptions for function=AGTLGDIN
ACDGROUP Y or N ACD group. Enter Y (yes) to select the ACD

group option. Otherwise, enter N (no).
POSID Y or N Position ID. Enter Y to select the position ID

option. Otherwise, enter N.
LOGINID Y or N Login ID. Enter Y to select the login ID option.

Otherwise, enter N.

FUNCTION = AGTLGDOUT or AGTREADY

If the entry in subfield FUNCTION is AGTLGDOUT or AGTREADY, select
the subfields as follows.
Field descriptions for function=AGTLGDOUT or AGTREADY
ACDGROUP Y or N ACD group. Enter Y to select the ACD group


FUNCTION = AGTNREADY
If the entry in subfield FUNCTION is AGTNREADY, select the subfields as
follows.
Field descriptions for function=AGTNREADY


WALKAWAY Y or N Walk away code. Enter Y to select walk away

code option. Otherwise, enter N. This field is
an ACD option, by default an entry is not
made.
FUNCTION = CALLANSWR
If the entry in subfield FUNCTION is CALLANSWR, select the subfields as
follows.
Field descriptions for function=CALLANSWR
NCALLID Y or N Network call ID. Enter Y to select the network

call ID option. Otherwise, enter N.
DEVICEID Y or N Device ID. Enter Y to select the device ID

297-8021-351 Standard 06.02 July 2002

ACDDN Y or N ACD directory number. Enter Y to select the

ACDDN option. Otherwise, enter N.
CALLNGNO Y or N Calling number. Enter Y to select the calling

number option. Otherwise, enter N.
CHARGENO Y or N Charge number. Enter Y to select the charge

CALLTYPE Y or N Call type. Enter Y to select the call type

ORIGDN Y or N Originating DN. Enter Y to select the

originating DN option. Otherwise, enter N.
PREVAPPL Y or N Previous application ID. Enter Y to select the

previous application ID option. Otherwise,
enter N.
HOSTCALD Y or N Host call data. Enter Y to select the host call

data option. Otherwise, enter N.

FWDPARTY Y or N Forwarding party. Enter Y to select the

forwarding party option. Otherwise, enter N.
CPADIGS Y or N Called party address digits. Enter Y to select

the called party address digits option.
Otherwise, enter N.
FUNCTION = CALLOFFR
If the entry in subfield FUNCTION is CALLOFFR, select the subfields as
follows.
Field descriptions for function=CALLOFFR








enter N.


DEVICEID Y or N Device identification. Enter Y to select the

device ID option. Otherwise, enter N.


Otherwise, enter N.
FUNCTION = CALLQUED
If the entry in subfield FUNCTION is CALLQUED, select the subfields as
follows.
Field descriptions for function=CALLQUED


297-8021-351 Standard 06.02 July 2002

Field descriptions for function=CALLQUED





enter N.




Otherwise, enter N.
FUNCTION = CALLREL
If the entry in subfield FUNCTION is CALLREL, select the subfields as
follows.
Field descriptions for function=CALLREL

RELTYPE Y or N Release type. Enter Y to select the release

type option. Otherwise, enter N.




device identification option. Otherwise, enter
N.
POSTCALL Y or N Postcall status. Enter Y to select the postcall

status option. Otherwise, enter N.
FUNCTION = AGTSETACT
If the entry in subfield FUNCTION is AGTSETACT, select the subfields as
follows.
Field descriptions for function=AGTSETACT
NTWSETACT Y or N Network set action. Enter Y to select the

network set action option. Otherwise, enter N.
INTSTAT Y or N Interval status. The dv-agent-setaction-u

message reports interval completed for
release guard or variable wrap. The message
transmits if there are no calls in the queue and
the agent is waiting for a call. Enter Y to select
the interval status option. Otherwise, enter N.
ENHWAC Y or N Report new walkaway reason. The ACD

agent tells the host computer when the
walkaway reason changes. Enter Y to send
the dv-agent-setaction-u message from the
switch to the host computer.
297-8021-351 Standard 06.02 July 2002

FUNCTION = EMKEVENT
If the entry in subfield FUNCTION is EMKEVENT, select the subfields as
follows.
Field descriptions for function=EMKEVENT
NCALLID Y or N Network call ID. Enter Y to select this option.

Otherwise, enter N. This parameter
identifies the call in a network. The default is
Y. If you select N, the switch cannot track
CompuCALL messages.
AGTPOSID Y or N Agent position ID. Enter Y to select this

option. Otherwise, enter N. The default is Y.
AGTDN Y or N Agent DN. Enter Y to select this option.

Otherwise, enter N.
SUPRVPID Y or N Supervisor position DN. Enter Y to select

this option. Otherwise, enter N.
SUPRVDN Y or N Supervisor Answer Emergency key DN.

Enter Y to select this option. Otherwise,
enter N.
AUXDN Y or N Auxiliary device DN. Enter Y to select this

FUNCTION = LOBEVENT
If the entry in subfield FUNCTION is LOBEVENT, select the subfields as
follows.
Field descriptions for function=LOBEVENT

call ID option. Otherwise, enter N. This
parameter identifies the call in a network.
Enter Y to include the parameter. If you select
N, the host cannot track CompuCALL
messages. The default is Y.

Field descriptions for function=LOBEVENT
AGTPOSID Y or N Agent position ID Enter Y to select this option.

Otherwise, enter N. The default is Y.
LOBTIME Y or N LOB time stamp. Enter Y to select this option.

Otherwise, enter N. This option provides a
time stamp to each LOB message sent from
the DMS-100 switch. (The recorded time is
the local time at the switch location, not the
host site.)
CATEGORY = CALLINIT
If the entry in subfield CATEGORY is CALLINIT, select the subfield as
more information.
Field descriptions for category=CALLINIT
FUNCTIONS see subfield Functions. This field includes subfield

FUNCTION.
FUNCTION MAKECALL Function. Enter MAKECALL (make call) and

select subfields AUTHCODE and
ACCTCODE as follows.
FUNCTION = MAKECALL
If the entry in subfield FUNCTION is MAKECALL, select the subfields as
follows.
Field descriptions for function=MAKECALL
AUTHCODE Y or N Authorization code. Enter Y to select this

ACCTCODE Y or N Account code. Enter Y to select this option.

Otherwise, enter N.
297-8021-351 Standard 06.02 July 2002

CATEGORY = CPGEVENT
If the entry in subfield CATEGORY is CPGEVENT, select the subfields as
follows.
Field descriptions for category=CPGEVENT

FUNCTION.
FUNCTION DIGCOLL,BU This selector field allows selection of one of

SY,RINGBAC the possible call progress events for
K,CONNECT subscription. There are limited refinements
ED,RAN,MUS for each call progress event.
IC,SILENCE,
TRTMT
Enter DIGCOLL (digit collection) and select

subfields NCALLID, ORIGDEV, ORIGACD,
ORIGNAME, DIALDIGS, CALLTYPE,
FLEGDEV, FLEGACD, and FLEGNAME as
shown in the FUNCTION = DIGCOLL
section.
Enter BUSY (busy event) and select subfields

NCALLID, ORIGDEV, ORIGACD,
shown in the FUNCTION = BUSY section.
Enter RINGBACK and select subfields

ORIGNAME, TERMDEV, TERMACD,
TERMNAME, ACDDN, FWDINFO,
CALLTYPE, FLEGDEV, FLEGACD, and
FLEGNAME as shown in the FUNCTION =
RINGBACK section.
Enter CONNECTED and select subfields

ORIGNAME, TERMDEV, TERMACD,
TERMNAME, ACDDN, FWDINFO,
CONNECTED section.

Field descriptions for category=CPGEVENT
Enter RAN and select subfields NCALLID,

ORIGDEV, ORIGACD, ORIGNAME,
TERMACD, ACDDN, FWDINFO,
RAN section.
Enter MUSIC and select subfields NCALLID,

ORIGDEV, ORIGACD, ORIGNAME,
TERMACD, ACDDN, FWDINFO,
MUSIC section.
Enter SILENCE and select subfields

ORIGNAME, TERMACD, ACDDN,
FWDINFO, CALLTYPE, FLEGDEV,
FLEGACD, and FLEGNAME as shown in the
FUNCTION = SILENCE section.
Enter TRTMT (treatment) and select subfields

shown in the FUNCTION = TRTMT section.
FUNCTION = DIGCOLL
If the entry in subfield FUNCTION is DIGCOLL, select the subfields as
follows.
Field descriptions for function=DIGCOLL
NCALLID Y or N Network call ID. Enter Y to select the

NCALLID option. Otherwise, enter N.
ORIGDEV Y or N Originating device ID (position ID if ACD

agent). Enter Y to select the ORIGDEV
ORIGACD Y or N Originating ACD group. Enter Y to select the

ORIGACD option. Otherwise, enter N.
297-8021-351 Standard 06.02 July 2002

Field descriptions for function=DIGCOLL
ORIGNAME Y or N Originator's name. Enter Y to select the

ORIGNAME option. Otherwise, enter N.
DIALDIGS Y or N Digits dialed. Enter Y to select the DIALDIGS

CALLTYPE Y or N Type of call. Enter Y to select the CALLTYPE

FLEGDEV Y or N Device ID of first leg of call, if multiparty call

(position ID if ACD agent). Enter Y to select
the FLEGDEV option. Otherwise, enter N.
FLEGACD Y or N ACD group of first leg call, if multiparty call.

Enter Y to select the FLEGACD option.
Otherwise, enter N.
FLEGNAME Y or N Name of first leg of call, if multiparty call. Enter

Y to select the FLEGNAME option.
Otherwise, enter N.
FUNCTION = BUSY
If the entry in subfield FUNCTION is BUSY, select the subfields as follows.
Field descriptions for function=BUSY







Field descriptions for function=BUSY

FLEGACD Y or N ACD group of first leg of call, if multiparty call.

Otherwise, enter N.

Otherwise, enter N.
FUNCTION = RINGBACK
If the entry in subfield FUNCTION is RINGBACK, select the subfields as
follows.
Field descriptions for function=RINGBACK




TERMDEV Y or N Terminating device ID (position ID if ACD

agent). Enter Y to select the TERMDEV
TERMACD Y or N Terminating ACD group. Enter Y to select the

TERMACD option. Otherwise, enter N.
TERMNAME Y or N Terminator's name. Enter Y to select the

TERMNAME option. Otherwise, enter N.
ACDDN Y or N ACD DN dialed by caller, primary or

additional. Enter Y to select the ACDDN
297-8021-351 Standard 06.02 July 2002

Field descriptions for function=RINGBACK
FWDINFO Y or N Forwarding information. Enter Y to select the

FWDINFO option. Otherwise, enter N.


(Position ID if ACD agent). Enter Y to select

Otherwise, enter N.

Otherwise, enter N.
FUNCTION = CONNECTED
If the entry in subfield FUNCTION is CONNECTED, select the subfields as
follows.
Field descriptions for funcion=CONNECTED




TERMDEV Y or N Terminating device ID (position ID if ACD

agent). Enter Y to select the TERMDEV


Field descriptions for funcion=CONNECTED
TERMNAME Y or N Terminator's name. Enter Y to select the

TERMNAME option. Otherwise, enter N.





Otherwise, enter N.

Otherwise, enter N.
FUNCTION = RAN
If the entry in subfield FUNCTION is RAN, select the subfields as follows.
Field descriptions for function=RAN




297-8021-351 Standard 06.02 July 2002

Field descriptions for function=RAN






Otherwise, enter N.

Otherwise, enter N.
FUNCTION = MUSIC
If the entry in subfield FUNCTION is MUSIC, select the subfields as follows.
Field descriptions for function=MUSIC





Field descriptions for function=MUSIC






Otherwise, enter N.

Otherwise, enter N.
FUNCTION = SILENCE
If the entry in subfield FUNCTION is SILENCE, select the subfields as
follows.
Field descriptions for function=SILENCE




297-8021-351 Standard 06.02 July 2002

Field descriptions for function=SILENCE






Otherwise, enter N.

Otherwise, enter N.
FUNCTION = TRTMT
If the entry in subfield FUNCTION is TRMT, select the subfields as follows.
Field descriptions for function=TRTMT





Field descriptions for function=TRTMT




Otherwise, enter N.

Otherwise, enter N.
CATEGORY = CTXEVENT
If the entry in subfield CATEGORY is CTXEVENT, select the subfields as
more information.
Field descriptions for category=CTXEVENT

FUNCTION. You can select up to five
functions. If you select less than five
297-8021-351 Standard 06.02 July 2002

Field descriptions for category=CTXEVENT
FUNCTION CALLANSWR Function. Enter CompuCALL messages.

, CALLNAME,
Enter CALLANSWR and select the subfields
CALLOFFR,
NCALLID, DEVICEID, CALLNGNO,
CALLREL,
CALLNGDIAL, CALLNGNAME,
SETOFFHK
ORIGDIAL, ORIGNAME, PREVAPPL,
HOSTCALD, CALLMODE, FWDPARTY, and
MEMBERID as shown in the FUNCTION =
CALLANSWR section.
Enter CALLNAME and select the subfields

CALLNGDIAL, and CALLNGNAME as shown
in the FUNCTION = CALLNAME section.
Enter CALLOFFR and select the subfields
NCALLID, CALLNGNO, CALLNGDIAL,
CALLNGNAME, CHARGENO, CALLTYPE,
ORIGDN, ORIGDIAL, ORIGNAME
PREVAPPL, HOSTCALD, and CALLMODE,
DEVICEID, and FWDPARTY as shown in the
FUNCTION = CALLOFFR section.
Enter CALLREL and select the subfields
NCALLID, RELTYPE, DEVICEID, and
MEMBERID as shown in the FUNCTION =
CALLREL section.
Enter SETOFFHK and select the subfields
NCALLID, DEVICEID, and MEMBERID as
shown in the FUNCTION = SETOFFHK
section.

follows.


N.

CALLNGDIAL Y or N Dialable calling number. Enter Y to select the

dialable calling number option. Otherwise,
enter N.
CALLNGNAME Y or N Calling name. Enter Y to select the calling

name option. Otherwise, enter N.



ORIGDIAL Y or N Originating dialable digits. Enter Y to select

the originating dialable digits option.
Otherwise, enter N.
ORIGNAME Y or N Originating name. Enter Y to select the

originating name option. Otherwise, enter N.

enter N.

CALLMODE Y or N Call mode. Enter Y to select the call mode

297-8021-351 Standard 06.02 July 2002


MEMBERID Y or N Member ID. Enter Y to select the member ID

FUNCTION = CALLNAME
If the entry in subfield FUNCTION is CALLNAME, select the subfields as
follows.
Field descriptions for function=CALLNAME


N.


enter N.

FUNCTION = CALLOFFR
follows.




dialing number option. Otherwise, enter N.



ORIGDN Y or N Originating dial numbers. Enter Y to select the

originating dial option. Otherwise, enter N.

Otherwise, enter N.


enter N.



N.

Enter Y if feature ICM MWT is active.
297-8021-351 Standard 06.02 July 2002

FUNCTION = CALLREL
follows.



N.

FUNCTION = SETOFFHK
If the entry in subfield FUNCTION is SETOFFHK, select the subfields as
follows.
Field descriptions for function=SETOFFHK


device identification option. This field is an
ACD option, which by default, is not entered.
Otherwise, enter N.


CATEGORY = DNQUERY
If the entry in subfield CATEGORY is DNQUERY, select the subfield as
more information.
Field descriptions for category=DNQUERY

FUNCTION.
FUNCTION DNQUERY Function. Enter DNQUERY and select

subfield FILTER as follows.
FUNCTION = DNQUERY
If the entry in subfield FUNCTION is DNQUERY, select the subfield as
follows.
Field descriptions for function=DNQUERY
FILTER Y or N Query filter. Enter Y to select the query filter

297-8021-351 Standard 06.02 July 2002

CATEGORY = ICCM
If the entry in subfield CATEGORY is ICCM, select the subfield as follows.
See the ACD CompuCALL section of the Translations Guide for more
information.
Field descriptions for category=ICCM
FUNCTIONS Functions. This field includes subfield

FUNCTION.
FUNCTION SETCDNST Function. Enter functions.

REASNAGT
Enter SETCDNST for the dv-Set-CDN-State
message. This message allows ICCM to
change the state of a CDN queue on the
DMS-100 switch.
Enter REASNAGT for the
dv-Reassign-Agent message. The
dv-Reassign-Agent message reassigns the
agent to a new supervisor. Enter
REASNAGT and select subfields
AgentPosid and NewSuperPosid as follows.
FUNCTION = REASNAGT
If the entry in subfield FUNCTION is REASNAGT, select the subfields as
follows.
Field descriptions for function=REASNAGT
AgentPosid Y or N Agent position identification. This subfield

identifies the agent position identification
assigned to a new supervisor.
NewSuperPosid Y or N New supervisor position identification. This

subfield identifies the position identification
of the supervisor to assign the agent.

CATEGORY = RESEVENT
If the entry in subfield CATEGORY is RESEVENT, select the subfield as
more information.
Field descriptions for category=RESEVENT
FUNCTION CALLANSWR, Function. Enter CompuCALL messages.

CALLNAME,
Enter CALLANSWR (call answered) and
CALLOFFR,
select subfields NCALLID, DEVICEID,
CALLREL,
CALLNGNO, CALLNGDIAL,
SETOFFHK
CALLNGNAME, CHARGENO, CALLTYPE,
ORIGDN, ORIGDIAL, ORIGNAME,
PREVAPPL, HOSTCALD, CALLMODE, and
FWDPARTY as shown in the FUNCTION =
CALLANSWR section.
Enter CALLNAME and select subfields

CALLNGDIAL, and CALLNGNAME as
shown in the FUNCTION = CALLNAME
section.
Enter CALLOFFR (call offered) and select

subfields NCALLID, CALLNGNO,
CALLNGDIAL, CALLNGNAME,
ORIGDIAL, ORIGNAME, PREVAPPL,
HOSTCALD, DEVICEID, FWDPARTY and
CALLMODE as shown the FUNCTION =
CALLOFFR section.
Enter CALLREL (call released) and select

subfields NCALLID, RELTYPE, and
DEVICEID as shown in the FUNCTION =
CALLREL section.
Enter SETOFFHK (set off hook) and select

subfields NCALLID and DEVICEID as shown
in the FUNCTION = SETOFFHK section.
297-8021-351 Standard 06.02 July 2002

follows.


N.


enter N.





Otherwise, enter N.


enter N.




FUNCTION = CALLNAME
If the entry in subfield FUNCTION is CALLNAME, select the subfields as
follows.
Field descriptions for function=CALLNAME


N.


enter N.

FUNCTION = CALLOFFR
follows.


297-8021-351 Standard 06.02 July 2002


dialing number option. Otherwise, enter N.

CHARGENO Y or N Charge number. Enter Y to select the. Charge

number type option. Otherwise, enter N.



Otherwise, enter N.


enter N.


N.

Enter Y if feature ICM MWT is active.


FUNCTION = CALLREL
follows.



N.
FUNCTION = SETOFFHK
If the entry in subfield FUNCTION is SETOFFHK, select the subfields as
follows.
Field descriptions for function=SETOFFHK


N.
CATEGORY = RESOURCE
If the entry in subfield CATEGORY is RESOURCE, select the subfield as
more information.
Field descriptions for category=RESOURCE

FUNCTION.
297-8021-351 Standard 06.02 July 2002

Field descriptions for category=RESOURCE
FUNCTION ACDQUERY Function. Enter functions.

APPSTQRY
Enter ACDQUERY.
Enter APPSTQRY to request ACD agent

status and call status. Select parameters as
shown in the FUNCTION = APPSTQRY
section.
FUNCTION = APPSTQRY
If the entry in subfield FUNCTION is APPSTQRY, select the subfields as
follows.
Field descriptions for function=APPSTQRY
DN Y or N Directory number. Enter Y to select the single

ACD DN, CDN, or agent option. Otherwise,
enter N.
ALLCDNS Y or N All CDN status. Enter Y to select the all CDN

ALLAGENTS Y or N All agents status. Enter Y to select the all

agents status option. Otherwise, enter N.
AGTSTAT Y or N Agent status. Enter Y to select the agent

CALLSTAT Y or N Call status. Enter Y to select the call status


CATEGORY = ROUTING
If the entry in subfield CATEGORY is ROUTING, select the subfield as
more information.
Field descriptions for category=ROUTING

FUNCTION. You can select up to two
functions. If you select less than two
FUNCTION CALLRECDC Function. Enter CompuCALL messages.

CALLREDIR
Enter CALLRECDC and select subfields
CPADIGS, NCALLID, ACD directory number,
ACDGROUP, and FWDPARTY as shown in
the FUNCTION = CALLRECDC section.
Enter CALLREDIR (call redirect) and select
subfields NCALLID, REDIRN, and
HOSTCALD as shown in the FUNCTION =
CALLREDIR section.
FUNCTION = CALLRECDC
If the entry in subfield FUNCTION is CALLRECDC, select the subfields as
follows.
Field descriptions for function=CALLRECDC


ACD directory number option. Otherwise,
enter N.


297-8021-351 Standard 06.02 July 2002

Field descriptions for function=CALLRECDC



enter N.




Otherwise, enter N.
FUNCTION = CALLREDIR
If the entry in subfield FUNCTION is CALLREDIR, select the subfields as
follows.
Field descriptions for function=CALLREDIR

REDIRN Y or N Redirect DN. Enter Y to select the redirect DN



CATEGORY = SCAICC
If the entry in subfield CATEGORY is SCAICC, select the subfield as follows.
information.
Field descriptions for category=SCAICC

FUNCTION. You can select up to five
functions. If you select less than five
FUNCTION ANSWCALL Function. Enter CompuCALL messages.

CALLUNHELD
Enter ANSWCALL (answer call).
CALLHELD
HOLDCALL Enter CALLUNHELD (call unheld) and select
RELSCALL subfield NCALLID as shown in the
UNHOLDCALL FUNCTION = CALLUNHELD section.
Enter CALLHELD (call held) and select
subfield NCALLID as show in the
FUNCTION =CALLHELD section.
Enter HOLDCALL (hold call).
Enter RELSCALL (release call) and select
subfield RELTYPE as shown in the
FUNCTION = RELSCALL section.
Enter UNHOLDCALL (unhold call).
FUNCTION = CALLUNHELD or CALLHELD

If the entry in subfield FUNCTION is CALLUNHELD or CALLHELD, select
the subfield as follows.
Field descriptions for function=CALLUNHELD or CALLHELD

297-8021-351 Standard 06.02 July 2002

FUNCTION = RELSCALL
If the entry in subfield FUNCTION is RELSCALL, select the subfield as
follows.
Field descriptions for function=RELSCALL

CATEGORY = SCAIMWTI
If the entry in subfield CATEGORY is SCAIMWTI, select the subfield as
more information.
Field descriptions for category=SCAIMWTI

FUNCTION. You can select up to two
functions. If you select less than two
FUNCTION MSGWAIT Function. For message waiting indication,

MWTACT enter MSGWAIT and select subfields
DEVICEID, MWTYPE, and INDICATION as
shown in the FUNCTION = MSGWAIT
section.
For message waiting activation or

deactivation, enter MWTACT and select
subfields DEVICEID, VMSDEVID, and
INDICATION as shown in the FUNCTION =
MWTACT section.

FUNCTION = MSGWAIT
If the entry in subfield FUNCTION is MSGWAIT, select the subfields as
follows.
Field descriptions for function=MSGWAIT

N.
MWTYPE Y or N Message waiting type. Enter Y to select the

message waiting type option. Otherwise,
enter N.
INDICATION Y or N Indication. Enter Y to select the indication

Function = MWTACT
If the entry in subfield FUNCTION is MWTACT, select the subfields as
follows.
Field descriptions for function=MWTACT

N.
VMSDEVID Y or N VMS device identification. Enter Y to select

the VMS device identification option.
Otherwise, enter N.
INDICATION Y or N MWT activation/deactivation indication. Enter

Y to select the MWT activation or deactivation
indication option. Otherwise, enter N.
297-8021-351 Standard 06.02 July 2002

CATEGORY = SCAI3WC
If the entry in subfield CATEGORY is SCAI3WC, select the subfield as
more information.
Field descriptions for category=SCAI3WC

FUNCTION. You can select up to seven
functions. If you select less than seven
FUNCTION ADDPTY Function. Enter CompuCALL messages.

CNTRLREL
Enter ADDPTY and select subfields
CONFPTY
OPTYPE, ORIGADDR, and DESTDN as
CONFEVNT
shown in the FUNCTION = ADDPTY
CONSULTEV
section.
DROPPTY
NCTRLREL Enter CNTRLREL and select subfield
TRANPTY NCALLID as shown in the FUNCTION =
TRANSFEREV CNTRLREL, CONSULTEV, CONFEVNT,
NCTRLREL, or TRANSFEREV section.
Enter CONFPTY and select subfield
ORIGADDR as shown in the FUNCTION =
CONFPTY section.
Enter CONSULTEV, and select subfield
NCALLID as shown in the FUNCTION =
CNTRLREL, CONSULTEV, CONFEVNT,
Enter CONFEVNT and select subfield
Enter CONSULTEV and select subfield

Field descriptions for category=SCAI3WC
Enter DROPPTY and select subfields

OPTYPE and ORIGADDR as shown in the
FUNCTION = DROPPTY section.
Enter NCTRLREL and select subfield
Enter TRANPTY and select subfield

ORIGADDR as shown in the FUNCTION =
TRANPTY section.
Enter TRANSFEREV and select subfield

FUNCTION = ADDPTY
If the entry in subfield FUNCTION is ADDPTY, select the subfields as
follows.
You must select subfields OPTYPE, ORIGADDR, and DESTDN for the
Intelligent Call Management (ICM) application to validate subfield ADDPTY.
Field descriptions for function=ADDPTY
OPTYPE Y or N Operation type. Enter Y to select the

operation type option. Otherwise, enter N.
ORIGADDR Y or N Originating address. Enter Y to select the

originating address option. Otherwise, enter
N.
DESTDN Y or N Destination DN. Enter Y to select the

destination DN option. Otherwise enter N.
FUNCTION = CONFPTY
If the entry in subfield FUNCTION is CONFPTY, select the subfield as
follows.
297-8021-351 Standard 06.02 July 2002

You must select subfield ORIGADDR for the ICM application to validate
subfield CONFPTY.
Field descriptions for function=CONFPTY

N.
FUNCTION = CNTRLREL, CONSULTEV, CONFEVNT, NCTRLREL,

or TRANSFEREV
If the entry in subfield FUNCTION is CNTRLREL, CONSULTEV,
CONFEVNT, NCTRLREL, or TRANSFEREV select the subfield as follows.
Field descriptions for function=CNTRLREL, CONSULTEV, CONFEVNT, NCTRLREL, or
TRANSEREV

FUNCTION = DROPPTY
If the entry in subfield FUNCTION is DROPPTY, select the subfields as
follows.
You must select subfields OPTYPE and ORIGADDR for the ICM application
to validate subfield DROPPTY.
Field descriptions for function=DROPPTY


N.
FUNCTION = TRANPTY
If the entry in subfield FUNCTION is TRANPTY, select the subfield as
follows.

subfield TRANPTY.
Field descriptions for function=TRANPTY

N.
297-8021-351 Standard 06.02 July 2002

CATEGORY = TPAC
If the entry in subfield CATEGORY is TPAC, select the subfields as follows.
information.
Field descriptions for category=TPAC

FUNCTION. You can select up to four
functions. If you select less than four
functions, end the list with a $ (dollar
sign).
FUNCTION CHGFORCE Function. Enter CompuCALL messages.

CHGVWRAP
Enter CHGFORCE (change force) to
LOGINAGT
change the Forcing feature for the ACD
LOGOUTAGT
group or ACD agent. Select subfields
NREADYAGT
ORIGADDR and FRCETYPE as shown
READYAGT
in the FUNCTION = CHGFORCE
RESERVEAGT
section.
UNRESERVEAGT
Enter CHGVWRAP (change variable
wrap) to change the variable wrap timer
on an ACD group basis or agent basis.
Select subfields ORIGADDR and
WRAPTIMER as shown in the
FUNCTION = CHGVWRAP section.
Enter LOGINAGT (login agent) and
select subfields ORIGADDR, LOGINID,
and PASSWORD as shown in the
FUNCTION = LOGINAGT section.
Enter LOGOUTAGT (logout agent) and
select subfield ORIGADDR as shown in
the FUNCTION = LOGOUTAGT or
READYAGT section.

Field descriptions for category=TPAC
Enter NREADYAGT (make agent not

ready) and select subfields ORIGADDR
and WALKAWAY as shown in the
FUNCTION = NREADYAGT.
Enter READYAGT (agent ready) and
select subfield ORIGADDR as shown in
the FUNCTION = LOGOUTAGT or
READYAGT section.
Enter RESERVEAGT (reserve agent)

and select subfield ORIGADDR and
RESERV_TIMER as shown in the
FUNCTION = RESERVEAGT section.
Enter UNRESERVEAGT (unreserve
agent) and select subfield ORIGADDR
as shown in the FUNCTION =
UNRESERVEAGT section.
FUNCTION = CHGFORCE
If the entry in subfield FUNCTION is CHGFORCE, select the subfields as
follows.
Field descriptions for function=CHGFORCE

N.
FRCETYPE Y or N Force type. Enter Y to select the force type

option. Otherwise, Enter N.
297-8021-351 Standard 06.02 July 2002

FUNCTION = CHGVWRAP
If the entry in subfield FUNCTION is CHGVWRAP, select the subfields as
follows.
Field descriptions for function=CHGVWRAP

N.
WRAPTIMER Y or N Wrap timer. Enter Y to select the wrap timer

option. Otherwise, Enter N.
FUNCTION = LOGINAGT
If the entry in subfield FUNCTION is LOGINAGT, select the subfields as
follows.
subfield LOGINAGT.
Field descriptions for function=LOGINAGT

N.
LOGINID Y or N Login ID. Enter Y to select the login

identification option. Otherwise, enter N.
PASSWORD Y or N Password. This field is an ACD option, which

by default, is not entered.
FUNCTION = LOGOUTAGT or READYAGT

If the entry in subfield FUNCTION is LOGOUTAGT or READYAGT, select
the subfield as follows.

You must select the subfield ORIGADDR for the ICM application to validate
subfields LOGOUTAGT or READYAGT.
Field descriptions for function=LOGOUTAGT or READYAGT

N. Otherwise, enter N.
FUNCTION = NREADYAGT
If the entry in subfield FUNCTION is NREADYAGT, select the subfields as
follows.
subfield NREADYAGT.
Field descriptions for function=NREADYAGT

N.
WALKAWAY Y or N Walk away code. Enter Y to select the

WALKAWAY option. Otherwise, enter N. This
subfield is an ACD option, which by default, is
not made.
FUNCTION = RESERVEAGT
If the entry in subfield FUNCTION is RESERVEAGT, select the subfields as
follows.
297-8021-351 Standard 06.02 July 2002

subfield RESERVEAGT.
Field descriptions for function=RESERVEAGT

originating address option. Otherwise,
enter N.
RESERV_TIMER Y or N Reserve timer. Enter Y to select the

RESERV_TIMER option. Otherwise,
enter N.
FUNCTION = UNRESERVEAGT
If the entry in subfield FUNCTION is UNRESERVEAGT, select the subfield
as follows.
subfield UNRESERVEAGT.
Field descriptions for function=UNRESERVEAGT

originating address option. Otherwise,
enter N.

CATEGORY = TPCC
If the entry in subfield CATEGORY is TPCC, select the subfields as follows.
information.
Field descriptions for category=TPCC

FUNCTION. You can select up to 13
functions. If you select less than 13
FUNCTION ADDPTY Enter ADDPTY (add party) and select

ANSWCALL subfields OPTYPE, ORIGADDR, DESTDN,
CALLHELD and CLDABTNO as shown in the
CALLUNHELD FUNCTION = ADDPTY section.
CNTRLREL
Enter ANSWCALL (answer call).
CONFEVNT
CONFPTY Enter CALLHELD (call held) and select
CONSULTEV subfield NCALLID as shown in the
DROPPTY FUNCTION = CALLHELD, CALLUNHELD,
HOLDCALL CNTRLREL, CONSULTEV, CONFEVNT,
MAKECALL NCTRLREL, or TRANSFEREV section.
NCTRLREL
Enter CALLUNHELD (call unheld) and
RELSCALL
select subfield NCALLID as shown in the
TRANPTY
FUNCTION = CALLUNHELD, CNTRLREL,
TRANSFEREV
CONSULTEV, CONFEVNT, NCTRLREL, or
UNHOLDCALL
TRANSFEREV section.
Enter CONFEVNT (call conferenced) and
TRANSFEREV section.
Enter CONFPTY (conference party) and
select subfield ORIGADDR as shown in the
FUNCTION = CONFPTY or TRANPTY
section.
297-8021-351 Standard 06.02 July 2002

Field descriptions for category=TPCC
Enter CONSULTEV (call-consult originated)

and select subfield NCALLID as shown in
the FUNCTION = CALLUNHELD,
Enter DROPPTY (drop party) and select
subfields OPTYPE and ORIGADDR as
shown in the FUNCTION = DROPPTY
section.
Enter HOLDCALL (hold call).

Enter MAKECALL (make call) and select
subfields AUTHCODE and ACCTCODE as
shown in the FUNCTION = MAKECALL
section.
Enter RELSCALL (release call) and select
subfield RELTYPE as shown in the
FUNCTION = RELSCALL section.
Enter TRANPTY (transfer party) and select

subfield ORIGADDR as shown in the
section.
Enter TRANSFEREV (call transferred) and

TRANSFEREV section.
Enter UNHOLDCALL (unhold call).
Enter CNTRLREL and select subfield

CALLUNHELD, CNTRLREL, CONSULTEV,
CONFEVNT, NCTRLREL, or
TRANSFEREV section.
Enter NCTRLREL and select subfield

CALLUNHELD, CNTRLREL, CONSULTEV,
CONFEVNT, NCTRLREL, or
TRANSFEREV section.

FUNCTION = ADDPTY
If the entry in subfield FUNCTION is ADDPTY, select the subfields as
follows.
You must select subfields OPTYPE, ORIGADDR, and DESTDN for the ICM
application to validate subfield ADDPTY.
Field descriptions for function=ADDPTY


N.
DESTDN Y or N Destination DN. Enter Y to select the

destination DN option. Otherwise, enter N.
CLDABTNO Y or N Called about number. Enter Y to select the

destination DN option. Otherwise, enter N.
FUNCTION = CALLHELD, CALLUNHELD, CNTRLREL, CONFEVNT,

CONSULTEV, NCTRLREL, or TRANSFEREV
If the entry in subfield FUNCTION is CALLHELD, CALLUNHELD,
CNTRLREL, CONFEVNT, CONSULTEV, NCTRLREL, or TRANSFEREV
select the subfield as follows.
Field descriptions for function=CALLHELD, CALLUNHELD, CNTRLREL, CONFEVNT,
CONSULTEV, NCTRLREL, or TRANSFEREV


If the entry in subfield FUNCTION is CONFPTY or TRANPTY, select the
subfield as follows.
297-8021-351 Standard 06.02 July 2002

subfield CONFPTY or TRANPTY.
Field descriptions for function=CONFPTY or TRANPTY

N.
FUNCTION = DROPPTY
If the entry in subfield FUNCTION is DROPPTY, select the subfields as
follows.
You must select subfields OPTYPE and ORIGADDR for the ICM application
to validate subfield DROPPTY.
Field descriptions for function=DROPPTY


N.
FUNCTION = MAKECALL
If the entry in subfield FUNCTION is MAKECALL, select the subfields as
follows.
Field descriptions for function=MAKECALL
AUTHCODE Y or N Authorization code. Enter Y to select the

authorization code feature. Otherwise, enter
N.
ACCTCODE Y or N Account code. Enter Y to select the account

code feature. Otherwise, enter N.

FUNCTION = RELSCALL
If the entry in subfield FUNCTION is RELSCALL, select the subfield as
follows.
Field descriptions for function=RELSCALL

CATEGORY = TPQC
If the entry in subfield CATEGORY is TPQC, select the subfields as follows.
information.
Field descriptions for category=TPQC

FUNCTION.
297-8021-351 Standard 06.02 July 2002

Field descriptions for category=TPQC
FUNCTION GIVETRMT, Function. You can select up to three

ROUTECALL, functions. If you select less than three
TRMTCOMP functions, end the list with a $ (dollar sign).
Enter GIVETRMT (give treatment) to
subscribe to the dv-Give-Treatment queue
control message. This message enables
callers in an ACD DN incoming call queue to
receive a recorded announcement (RAN),
Music, Ringback, Silence, Busy, Fastbusy,
or Disconnect. CompuCALL requires this
message.
Enter ROUTECALL (route call) to select the
dv-Route-Call call control message. The
host computer uses this message to route a
call in an ACD queue. CompuCALL requires
this message. ROUTECALL also allows the
user to select whether the customer
receives optional enhanced display text as
shown in the FUNCTION = ROUTECALL
section.
The switch does not need to send an
association message to the ACD group
before it sends this message.
Enter TRMTCOMP (treatment completed) to

select the dv-Treatment-Completed-U call
event message. This message occurs when
the RAN call treatment is complete.
CompuCALL requires this message.
FUNCTION = ROUTECALL
If the entry in subfield FUNCTION is ROUTECALL, select the subfield as
follows.
Field descriptions for function=ROUTECALL
DISPTEXT Y or N Display text. Enter Y to select the display text


Datafill example
The following example shows sample datafill for table SCAISSRV.
297-8021-351 Standard 06.02 July 2002

MAP display example for table SCAISSRV
SUBSERV
SPROFILE
____________________________________________________________________
SCAI3WC09$
SCAI3WC (CONSULTEV Y) (CONFEVNT Y) (TRANSFEREV Y) (ADDPTY Y Y Y)
(CONFPTY Y) (DROPPTY Y Y) (TRANPTY Y)
MYEVENT
RESEVENT (SETOFFHK Y Y) (CALLOFFR Y Y Y Y Y Y Y Y Y Y Y Y Y)
(CALLANSWR Y Y Y Y Y Y Y Y Y Y Y Y Y) (CALLREL Y Y Y) $
CALLINIT1
CALLINIT (MAKECALL Y Y) $
3WC1
SCAI3WC(ADDPTY Y Y Y)(CONFPTY Y)(DROPPTY Y Y)(TRANPTY Y)(CONFEVNT N)$
MWTI1
SCAIMWTI (MSGWAIT Y Y Y) $
DNQRY1
DNQUERY (DNQUERY N) $
TPCC09$
TPCC (ADDPTY Y Y Y) (CONFPTY Y)(DROPPTY Y Y)(TRANPTY Y)(MAKECALL Y Y)
(ANSWCALL)(HOLDCALL)(UNHOLDCALL) (CALLUNHELD Y) (RELSCALL Y)
(CONSULTEV Y) (CONFEVNT Y) (TRANSFEREV Y)$
SCAICC08
SCAICC (ANSWCALL) (HOLDCALL) (UNHOLDCALL) (CALLUNHELD Y) (RESLCALL Y)
$
SCAICC09
SCAICC (HOLDCALL) (UNHOLDCALL) (CALLUNHELD Y) (RESLCALL Y) (ANSWCALL)
(CALLHELD Y)$
DNQUERY2
DNQUERY (DNQUERY Y) $
TPQC10$
TPQC (ROUTECALL N) (GIVETRMT) (TRMTCOMP) $
TPQC11$
TPQC (ROUTECALL Y) (GIVETRMT) (TRMTCOMP) $

MAP example for table SCAISSRV (continued)
SUBSERV
SPROFILE
____________________________________________________________________
RESOURCE35$
RESOURCE (ACDQUERY) $
RESOURCE11$
RESOURCE (ACDQUERY) (APPSTQRY Y Y Y Y Y) $
ACDEVENT11$
ACDEVENT(CALLQUED Y Y Y Y Y Y Y Y Y Y)
(CALLOFFR Y Y Y Y Y Y Y Y Y Y Y)
(CALLANSWR Y Y Y Y Y Y Y Y Y Y Y)(CALLREL Y Y Y Y Y) (AGTLGDIN Y Y Y)
(AGTLGDOUT Y Y) (AGTREADY Y Y) (AGTNREADY Y Y Y) (LOBEVENT Y Y Y)
(EMKEVENT Y Y Y Y Y)
CUSTOMEREVENT
ACDEVENT(CALLQUED Y Y Y Y N N Y Y Y Y)
(CALLOFFR Y Y Y Y Y N N N Y Y Y) (CALLANSWR Y Y Y Y Y Y Y Y N Y N)
(CALLREL Y Y N Y Y)(LOBEVENT N Y N) (EMKEVENT Y N Y N Y)
ACDEVENT11$
ACDEVENT(CALLQUED Y Y Y Y Y Y Y Y Y)(CALLOFFR Y Y Y Y Y Y Y Y Y Y Y)
(CALLANSWR Y Y Y Y Y Y Y Y Y Y Y) (CALLREL Y Y Y Y Y)(AGTLGDIN Y Y Y)
(AGTLGDOUT Y Y) (AGTREADY Y Y) (AGTNREADY Y Y Y) (LOBEVENT Y Y Y)
(EMKEVENT Y Y Y Y Y)$
MYTUPLE
ACDEVENT(CALLQUED Y Y Y Y Y Y Y Y Y Y)
(CALLOFFR Y Y Y Y Y Y Y Y Y Y Y) (CALLANSWR Y Y Y Y Y Y Y Y Y Y Y)
(CALLREL Y Y Y Y Y) (EMKEVENT Y Y N Y N N)$
ACDEVENT12$
ACDEVENT (CALLQUED Y Y Y Y Y Y Y Y Y Y)
(CALLOFFR Y Y Y Y Y Y Y Y Y Y Y) (CALLANSWR Y Y Y Y Y Y Y Y Y Y Y)
(CALLREL Y Y Y Y Y Y) (AGTLGDIN Y Y Y) (AGTLGDOUT Y Y) (AGTREADY Y Y)
(AGTNREADY Y Y N) (LOBEVENT Y Y Y) (EMKEVENT Y Y Y Y Y Y)
(AGTSETACT Y Y) $
CUSTOM ACDEVENT (AGTREADY Y Y) (CALLREL Y Y N N N Y)
(AGTSETACT Y Y) $
TPAC12$
TPAC (LOGINAGT Y Y N) (LOGOUTAGT Y) (READYAGT Y) (NREADYAGT Y N)
(RESERVEAGT Y Y) (UNRESERVEAGT Y) $
ICCM13$
ICCM (SETCDNST ) (REASNAGT Y Y) $
TPAC13$
TPAC (LOGINAGT Y Y N) (LOGOUTAGT Y) (READYAGT Y) (NREADYAGT Y N)
(RESERVEAGT Y Y) (UNRESERVEAGT Y) (CHGVWRAP Y Y) (CHGFORCE Y Y) $
297-8021-351 Standard 06.02 July 2002

MAP example for table SCAISSRV (continued)
SUBSERV
SPROFILE

SCAIMWTI13$
SCAIMWTI(MSGWAIT Y Y Y)(MWTACT Y Y Y) $
CTXEVENT 13$
CTXEVENT (SETOFFHK Y Y Y) (CALLOFFR Y Y Y Y Y Y Y Y Y Y Y Y Y Y)
(CALLANSWR Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y) (CALLREL Y Y Y Y)
(CALLNAME Y Y Y Y Y) $
RESEVENT13$
RESEVENT (SETOFFHK Y Y) (CALLOFFR Y Y Y Y Y Y Y Y Y Y Y Y Y Y)
(CALLANSWER Y Y Y Y Y Y Y Y Y Y Y Y Y Y) (CALLREL Y Y Y) (CALLNAME Y Y
Y Y Y) $
RESEVENT13$ RESEVENT(SETOFFHK Y Y) (CALLOFFR Y Y Y Y Y Y Y Y Y Y Y Y Y Y)
(CALLANSWR Y Y Y Y Y Y Y Y Y Y Y Y Y Y) (CALLREL Y Y Y)
(CALLNAME Y Y Y Y Y) $
CPGEVENT14$ CPGEVENT(DIGCOLL Y Y Y Y Y Y Y Y Y) (BUSY Y Y Y Y Y Y Y Y Y)
(RINGBACK Y Y Y Y Y Y Y Y Y Y Y Y Y)
(CONNECTED Y Y Y Y Y Y Y Y Y Y Y Y Y)
(RAN Y Y Y Y Y Y Y Y Y Y Y) (MUSIC Y Y Y Y Y Y Y Y Y Y Y)
(SILENCE Y Y Y Y Y Y Y Y Y Y Y) $
TPCC14$
TPCC (ANSWCALL) (RELSCALL Y) (CONSULTEV Y) (CONFEVNT Y)
(TRANSFEREV Y) (HOLDCALL) (UNHOLDCALL) (CALLUNHELD Y) (ADDPTY Y Y Y Y)
(CONFPTY Y)(DROPPTY Y Y) (TRANPTY Y) (MAKECALL Y Y) (CNTRLREL Y)
(NCTRLREL Y)
TPCC15$
(TPCC) (CONSULTEV Y) (CONFEVNT Y) (TRANSFEREV Y)
(CNTRLREL Y) (NCTRLREL Y) (HOLDCALL) (UNHOLDCALL)
(CALLUNHELD Y) (ANSWCALL) (RELSCALL) (ADDPTY Y Y Y Y)
(CONFPTY Y) (DROPPTY Y Y) (TRANPTY Y) (MAKECALL Y Y)
(CALLHELD Y)$
SCAI3WC14$
SCAI3WC (CONSULTEV Y) (CONFEVNT Y) (TRANSFEREV Y)
(ADDPTY Y Y Y) (CONFPTY Y) (DROPPTY Y Y) (TRANPTY Y)
(CNTRLREL Y) (NCTRLREL Y)$
ACDEVENT15$
ACDEVENT (CALLQUED Y Y Y Y Y Y Y Y Y Y Y) (CALLOFFR Y Y Y Y Y Y Y Y Y
Y Y Y) (CALLANSWR Y Y Y Y Y Y Y Y Y Y Y Y) (CALLREL Y Y Y Y Y Y)
(AGTLGDIN Y Y Y) (AGTLGDOUT Y Y) (AGTREADY Y Y) (AGTNREADY Y Y N)
(LOBEVENT Y Y Y) (EMKEVENT Y Y Y Y Y Y) (AGTSETACT Y Y N) $
ROUTING15$
ROUTING (CALLRECDC Y Y Y Y Y Y Y Y Y Y Y) (CALLREDIR Y Y Y) $

This section provides information on dump and restore procedures and the
datafill procedure for current SCAI groups for table SCAISSRV.

A reformat is necessary to address the added postcall status parameter in the
CALLREL function of the ACDEVENT category. The reformat applies for
ONPs to NA010 from NA007, NA008, and NA009.
A reformat is necessary to address the added CPADIGS parameter in the

CALLANSWR, CALLOFFR, and CALLQUED functions of the
ACDEVENT category. A reformat is necessary for the CPADIGS parameter
in the CALLRECDC function of the ROUTING category. The reformat
applies for ONPs to NA013 from NA012, NA011, and NA010.
Datafill of existing SCAI groups

To select current SCAI groups:
1. Make a list of the linksets owned by an SCAI group and the required
CompuCALL messages assigned for the linksets.
2. If possible, find the subservice names in table SCAISSRV that contain all
the messages from step 1. The fixed subservices assist with this procedure.
3. If table SCAISSRV does not contain the existing subservice names from
step 1, you can enter new subservice or existing subservice names.
4. Make a list of the subservice names, from steps 2and 3, to which the SCAI
group can subscribe.
5. Enter the names of the linksets (from step 1) and the list of subservice
names (from step 4) in table SCAIPROF.
Release history
NA016
Release 59028955 adds the following default tuple to Table SCAISSRV. The
default tuple receives the function DISPLAY_TEXT for the ICM call event
message DV_ROUTE_CALL:
default tuple TPQC11$ under the category TPQC with the new parameter
DISPTEXT in the ROUTECALL function
Note: The DN from which the call is being routed must be associated with
the SCAI session; the SCAI version should be at least SCAI17.
If a ROUTE_CALL message is sent without the DISPLAY_TEXT parameter,

then call routing behavior is unchanged. If a DV_ROUTE_CALL is sent with
297-8021-351 Standard 06.02 July 2002

the parameter DISPLAY_TEXT but the customer is not subscribed to the new
default tuple TPQC11$ in table SCAISSRV, then a Return_error with reason
NOT ALLOWED is returned.
NA015
This release adds the following default tuples to Table SCAISSRV. The default
tuples receive the function CALLHELD for the ICM call event message
DV_CALL_HELD_U:
default tuple TPCC15$ under the category TPCC
default tuple SCAIC09$ under the category SCAICC
This release also extends the support of the following call event message and
call control message:
When a call has been unheld manually or through ICM, the call event
message DV_CALL_UNHELD_U reports to the host application. The DN
must be associated to a SCAI session so that the host application receives
the call event message DV_CALL_UNHELD_U.
When a call has been put on hold manually or through ICM, the host
application sends the call control message DV_UNHOLD_CALL to the
switch. This action places the call off hold. The switch reports the call
event message DV_CALL_UNHELD_U to the host application. The DN
parameter is set to the directory number of the unholding party.
Note 1: The call event message DV_CALL_UNHELD_U and the call

control message DV_UNHOLD_CALL does not change the hold and
unhold functionality of the CHD, HLD, or HOLD KEY features. For
example, the switch reports the DV_CALL_HELD_U message to the
computer whether a call is placed on hold manually by call hold (CHD),
permanent hold (HLD), hold key, auto hold or by the ICM
DV_HOLD_CALL message.
The exception is K-SETS which support the HOLD KEY but not the
CHD or HLD features. The POTS 500/2500 support the CHD and
HLD features but not the HOLD KEY.
Note 2: Automatic Call Distribution (ACD), Meridian Digital Centrex

(MDC), and Residential Enhanced Services (RES) agents support the
changes to the call event message and the call control message stated
above.
MMP14
FUNCTION = TRTMT (treatment) and subfields added to CATEGORY =
CPGEVENT.

NA013
This release makes the following change to table SCAISSRV.
The Called Party Address in ICM messages feature (59011948) adds the
CPADIGS parameter to the CALLANSWR, CALLOFFR, and CALLQUED
functions in the ACDEVENT category. The feature adds the CPADIGS
parameter to the CALLRECDC function in the ROUTING category. The
feature adds the ACDEVENT15$ default tuple to the ACDEVENT category
and the ROUTING15$ default tuple to the ROUTING category.
NA012
This release makes the following changes to table SCAISSRV:
ICM TAPI Extensions (A59006746) adds service category CPGEVENT to
table SCAISSRV with messages DIGCOLL, BUSY, RINGBACK,
CONNECTED, RAN, MUSIC, and SILENCE.
ICM TAPI Extensions adds default tuple CPGEVENT14$ to category
CPGEVENT. The feature subscribes to all messages and all field
subscriptions are Y.
The addition of the default tuple reduces the total number of
non-default tuples by one.
Sites that have full SCAISSRV tables will have a problem with adding
the last tuple of the table on the load. This problem occurs during a
software upgrade.
ICM Three Way Call Enhanced Status Reporting (59006736) adds default
tuples TPCC14$ and SCAI3WC14$ to table SCAISSRV. The tuples add
functions CNTRLREL and NCTRLREL to table SCAISSRV.
297-8021-351 Standard 06.02 July 2002

NA011
ICM Message Waiting Activation/Deactivation (AU3192) adds the
following entries to table SCAISSRV:
MWTACT for category SCAIMWTI with parameters DEVICEID,
VMSDEVID, and INDICATION
CTXEVENT13$ and RESEVENT13$ subservice profiles to include
parameter Forwarding Party (FWDPARTY) for functions CALLOFFR
category CXTEVENT and RESEVENT
SCAIMWTI13$ subservice profile to include new message
dv-MWT-ACT and the previous dv-Message-Waiting-U
ICM MADN Support (AU3191) adds the MEMBERID parameter to the
functions SETOFFHK, CALLANSWR, and CALLREL for category
CTXEVENT. The subservice profile is CTXEVENT13$.
ICM Configuration Management (AU3190) adds default tuple ICCM13$
with all parameters selected to Y. ICM Configuration Management
(AU3190) adds function REASNAGT to category ICCM. Function
REASNAGT includes parameters AgentPosid and NewSupervisorPosid.
ICM Configuration Management (AU3190) adds default tuple TPAC13$
with all parameters selected to Y. ICM Configuration Management
(AU3190) adds functions CHGVWRAP and CHGFORCE to category
TPAC. Function CHGVWRAP includes parameters ORIGADDR and
WRAPTIMER. Function CHGFORCE includes parameters ORIGADDR
and FRCETYPE.
ACD Enhanced Walkaway (AF7737) adds new subfield ENHWAC to
subfield AGTSETACT.
NA010
Network ICM (AU2799) adds default tuple TPAC12$ with all parameters
selected to Y. Network ICM (AU2799) adds functions RESERVEAGT and
UNRESERVEAGT to category TPAC. Function RESERVEAGT includes
parameters ORIGADDR and RESERVE_TIMER. Function
UNRESERVEAGT includes parameter ORIGADDR.
Network ICM (AU2799) adds default tuple ACDEVENT12$ with all
parameters selected to Y. Network ICM (AU2799) adds function
AGTSETACT to category ACDEVENT. Function AGTSETACT includes

parameters NTWSETACT and INTSTAT; ICM Variable Wrap Reporting

(AU2801) adds parameter INTSTAT.
ICM Variable Wrap Reporting (AU2801) also adds parameter POSTCALL
to function CALLREL. Set all parameters in tuple ACDEVENT12$, to Y.
In ACDEVENT11$ and previous tuples with category ACDEVENT, the
POSTCALL parameter is present and set to N.
NA009
CompuCALL Line of Business (LOB) Event Reporting (AU2618) adds
function LOBEVENT to category ACDEVENT. Function LOBEVENT
includes parameters NCALLID, AGTPOSID, and LOBTIME. This
feature also adds default tuple ACDEVENT11$ with all parameters
selected Y.
CompuCALL Emergency Key Event Reporting (AU2619) adds function
EMKEVENT to category ACDEVENT. Function EMKEVENT includes
parameters NCALLID, AGTPOSID, AGTDN, SUPRVPID, SUPRVDN,
and AUXDN. The default tuple ACDEVENT11$ includes function
EMKEVENT with all parameters set to Y.
CompuCALL Status Query (AU2620) adds function APPSTQRY to
category RESOURCE. Function APPSTQRY includes parameters DN,
ALLCDNS, ALLAGENTS, AGTSTAT, and CALLSTAT. This feature also
adds default tuple RESOURCE11$ with all parameters selected Y.
Called About Number Display (AF7227) adds parameter CLDABTNO to
function ADDPTY in category TPCC and adds fixed tuple TPCC11$ with
all parameters set to Y.
NA008
The CompuCALL Integration with ICCM feature (AU2339) adds category
ICCM with function SETCDNST and default tuple ICCM10$.
CompuCALL Basic ICCM Functionality-Selective Queueing feature
(AU2341) adds category TPQC with function ROUTECALL and default
tuple TPQC10$.
CompuCALL Basic ICCM Functionality-Call Treatments feature
(AU2441) adds functions GIVETRMT and TRMTCOMP to category
TPQC.
297-8021-351 Standard 06.02 July 2002

SCAISSRV (end)
NA007
Subservice TPCC adds Functions TRANSFEREV, CONFEVNT, and
CONSULTEV.
Subservice SCAI3WC adds functions TRANSFEREV, CONFEVNT, and
CONSULTEV.
Subservice TPCC adds a new default tuple called TPCC09$, with all
parameters selected Y.
Subservice SCAI3WC adds a new default tuple called SCAI3WC09$, with
all parameters selected Y.
NA006
Subfield CATEGORY adds subservice SCAI with options ANSWCALL,
CALLUNHELD, HOLDCALL, RELSCALL, and UNHOLDCALL.
Subservice TPCC adds functions ANSWCALL, CALLUNHELD,
HOLDCALL, RELSCALL, and UNHOLDCALL.
NA005
Subfield CATEGORY adds subservices RESEVENT, CALLINIT,
SCAI3WC, SCAIMWTI, and DNQUERY.
Subfield CTXEVENT adds subservices SETOFFHK, CALLOFFR,
CALLANSWR, and CALLREL.
BCS36
CompuCALL changes the table size.
Subfield CATEGORY adds subservice TPAC.
Subservice ACDEVENT adds AGTLGDIN, AGTLGDOUT,
AGTNREADY, and AGTREADY.
BCS35
CompuCALL introduces table SCAISSRV

SCALLTAB
Table name
Speed Calling Table
Table SCALLTAB is a read-only table. The following information is listed in
the table for each speed calling number:
the site name assigned to the remote location of the line with speed calling
(if the line is remote)
the line equipment number (LEN) of the line with speed calling
the party number of the line with speed calling
whether the speed calling list is a short list (eight numbers), a long list (30
numbers), or an international abbreviated dialing list (ADL)
the speed calling code (2 to 9, 20 to 49, or 0 to 99 for ADL)
the digits of the destination number
Table SCALLTAB is never datafilled. The speed calling codes are set by the
subscriber using a telephone and are stored in this table by the system. Table
SCALLTAB is required for journal file records and for dump and restores.

There is no requirement to datafill other tables prior to table SCALLTAB.
Table size
0 to 30 tuples
SCALLTAB (continued)
Datafill
The following table lists datafill for table SCALLTAB.
Field descriptions
Subfield or
LINECODE see subfields Line code

This field consists of subfields LEN, PTY, DF,
and CODE.

telephone line.
SLOT, and CIRCUIT.
PTY S, T1 to T5, or Party

R1 to R5
This field contains the party of the line that is
equipped with speed calling.
DF SC1, SC2, or Feature

ADL
This field contains SC1 if the speed calling list
is short (eight numbers), SC2 if the speed
calling list is long (30 numbers), or ADL for the
international abbreviated dialing list.
CODE 0 to 99 Speed calling code

This field contains the speed calling code,
which is 2 to 9 for a short list, 20 to 49 for a
long list, or 0 to 99 for an ADL list.
DEST numeric (1 to Destination digits

30 digits)
This field contains the digits of the destination
number that is associated with the speed
calling code.
297-8021-351 Standard 05.02 May 2001

SCALLTAB (end)
Datafill example
The following example shows sample datafill for table SCALLTAB.
MAP display example for table SCALLTAB
LINECODE DEST
____________________________________________________________
HOST 00 0 00 00 S SC1 3 2258493
Table history
NA004
Field DEST entry was changed from numeric (up to 24 digits)" to numeric
(1 to 30 digits)" to accommodate 15-digit international dialing.
DMS-100 Family
Customer Data Schema Reference Manual
Volume 9 of 12
Product Documentation - Dept 3423

Nortel Networks
P.O. Box 13010
RTP, NC 27709-3010
Telephone: 1-877-662-5669
email: cits@nortelnetworks.com
Copyright 1996-2001 Nortel Networks,

All Rights Reserved
NORTEL NETWORKS CONFIDENTIAL: The

information contained herein is the property of Nortel Networks
and is strictly confidential. Except as expressly authorized in
writing by Nortel Networks, the holder shall keep all information
contained herein confidential, shall disclose the information only
to its employees with a need to know, and shall protect the
information, in whole or in part, from disclosure and
dissemination to third parties with the same degree of care it
uses to protect its own confidential information, but with no less
than reasonable care. Except as expressly authorized in writing
by Nortel Networks, the holder is granted no rights to use the
information contained herein.
Information is subject to change without notice. Nortel Networks

reserves the right to make changes in design or components as
progress in engineering and manufacturing may warrant.
Changes or modification to the DMS-100 without the express
consent of Nortel Networks may void its warranty and void the
users authority to operate the equipment.
Nortel Networks, the Nortel Networks logo, the Globemark,

How the World Shares Ideas, Unified Networks, DMS, DMS-
100, Helmsman, MAP, Meridian, Nortel, Northern Telecom, NT,
Supernode, and TOPS are trademarks of Nortel Networks.

Product release: LET0015 and up
Document release: Standard 05.02
Date: May 2001
Printed in the United States of America

Oqcqprof Scalltab

Uploaded by

Document Informationclick to expand document informationDMS100

Document Informationclick to expand document information

Copyright:

Available Formats

Oqcqprof Scalltab

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oqcqprof Scalltab

Uploaded by

Copyright:

Available Formats

Critical Release Notice

Publication number: 297-8021-351

The content of this customer NTP supports the SN07 (DMS)

Bookmark Color Legend

Table PCEMFEID was created as part of activity A00007196 in an earlier release.

Table PRSUDATA description added for CR Q01083765.

HNPACONT.RTEREF, IBNFEAT feature MWT, IBNLINES option MDN, IBNLINES option

LET0015 and up Standard 05.02 May 2001

Publication number: 297-8021-351

Copyright 1996-2001 Nortel Networks,

Printed in the United States of America

1 Data schema tables 1-1

297-8021-351 Standard 05.02 May 2001

297-8021-351 Standard 05.02 May 2001

NTP Summary Contents

Customer Data Schema Reference Manual Volume 2 of 12

Customer Data Schema Reference Manual Volume 3 of 12

Customer Data Schema Reference Manual Volume 4 of 12

Customer Data Schema Reference Manual Volume 5 of 12

Customer Data Schema Reference Manual Volume 6 of 12

Customer Data Schema Reference Manual Volume 7 of 12

Customer Data Schema Reference Manual Volume 8 of 12

Customer Data Schema Reference Manual Volume 9 of 12

Customer Data Schema Reference Manual Volume 10 of 12

Customer Data Schema Reference Manual Volume 11 of 11

Customer Data Schema Reference Manual Volume 12 of 12

297-8021-351 Standard 05.02 May 2001

1 Data schema tables

Call queue profiles are specified in one of two ways:

Call queue profiles datafilled using office-wide priorities contain a list of up to

Datafill sequence and implications

297-8021-351 Standard 05.02 May 2001

CQPROFNM 0 to 254 Call queue profile number. This number is used in

CQLIST CQ0 to Call queue list. If the entry in subfield PRIOTYPE

PRIO3 see subfields Priority level 3. If the entry in subfield PRIOTYPE is

CALLQ CQ0 to Call queue. If the entry in subfield PRIOTYPE is

AGS 10 to 80 Assignable grade of service. If the entry in subfield

PRIO2 see subfields Priority level 2. If the entry in subfield PRIOTYPE

297-8021-351 Standard 05.02 May 2001

Field descriptions (Sheet 3 of 4)

CALLQ CQ0 to Call queue. If the entry in subfield PRIOTYPE is

AGS 10 to 80 Assignable grade of service. If the entry in subfield

PRIO1 see subfields Priority level 1. If the entry in subfield PRIOTYPE

CALLQ CQ0 to Call queue. If the entry in subfield PRIOTYPE is

AGS 10 to 80 Assignable grade of service. If the entry in subfield

PRIO0 see subfields Priority level 0. If the entry in subfield PRIOTYPE

CALLQ CQ0 to Call queue. If the entry in subfield PRIOTYPE is

AGS 10 to 80 Assignable grade of service. If the entry in subfield

CQPROFNM AGENTQ PRIOAREA

297-8021-351 Standard 05.02 May 2001

Error message Explanation and action

Point-to-point rating is a method of automatic rate step determination by the

Point-to-point rating is an alternative to the following automatic rate step

Point-to-point rating system tables are listed in the table below.

Table name Form number Form title

ORIGRC 2726A, B TOPS Originating Rate Centers Table Record

TERMRC 2727A, B TOPS Terminating Rate Centers Table Record