PLN-5001-001i

DMS-100 Family
DMS-100 International
Technical Specification

BCS40i and up Standard 02.02 April 1997

DMS-100 Family

DMS-100 International
Technical Specification

Publication number: PLN-5001-001i

Product release: BCS40i and up
Document release: Standard 02.02
Date: April 1997

 1994, 1995, 1997 Northern Telecom

All rights reserved.
Printed in Canada and printed in the United States of America
NORTHERN TELECOM CONFIDENTIAL: The information contained in this document is the property of Northern
Telecom. Except as specifically authorized in writing by Northern Telecom, the holder of this document shall keep the
information contained herein confidential and shall protect same in whole or in part from disclosure and dissemination to third
parties and use same for evaluation, operation, and maintenance purposes only.

Information is subject to change without notice. Northern Telecom reserves the right to make changes in design or components
as progress in engineering and manufacturing may warrant.
DMS, DMS SuperNode, MAP, and NT are trademarks of Northern Telecom.

DMS-100 International Technical Specification BCS40i and up

ii

Publication history
April 1997
BCS40.1i and up Standard 02.03
• Minor editorial corrections.
April 1997
BCS40.1i and up Standard 02.02
• Updated to include additional information on ESA.
October 1995
BCS40i and up Preliminary 02.01
• Updated to include information on third universal tone receiver (UTR)
card in international digital trunk controller (IDTC).
October 1994
BCS37i and up Preliminary 01.02
• Revised to include technical changes from internal review of the draft
document and to add functionalities available with BCS37i

PLN-5001-001i Standard 02.02 April 1997

 iii

Contents
About this document iii
When to use this document iii
How to identify the software in your office iii
Where to find information iv

System architecture 1–1

DMS-100 International system overview 1–1
DMS-100 International switching platforms 1–3
DMS SuperNode switching platform 1–3
DMS SuperNode SE switching platform 1–4
Switching platform upgradability 1–5
DMS-100 International system elements 1–6
Central processing subsystem 1–7
DMS-Core 1–7
Computing module 1–8
Functional subsystems of the computing module 1–8
System load module shelf 1–11
System load modules (NT9X44) 1–12
DIRP on the system load module 1–13
Messaging component 1–13
DMS-Bus 1–13
Message switch 1–15
Functional subsystems of the message switch 1–16
DMS SuperNode central processing units 1–18
DMS SuperNode memory 1–18
Switching network 1–20
Junctored network 1–21
Enhanced network 1–28
Functional subsystems of ENET 1–31
Input/output controller 1–33
Input output devices 1–33
IOC common cards 1–34
IOC device controller cards 1–34
Multiprotocol controller card (NT1X89) 1–35
Peripheral modules 1–37
International line concentrating module (ILCM) 1–40
International line group controller (ILGC) 1–46
International digital trunk controller (IDTC) 1–51
Maintenance trunk module (MTM) 1–51
Signaling and interfaces between switching subsystems 1–54

DMS-100 International Technical Specification BCS40i and up

iv Contents

Communication between DMS-Core and DMS-Bus 1–54

Communication between switching core and subtending subsystems 1–54
Link peripheral processor (LPP) 1–56
How a link peripheral processor is configured 1–56
Link interface module 1–57
Link interface shelf 1–58
CCS7 link interface unit 1–58
Single shelf link peripheral processor 1–65
International remote line concentrating module (IRLCM) 1–69
Line concentrating array (LCA) shelf (NT6X04) 1–72
Remote maintenance module (RMM) shelf (NT6X13) 1–74
DMS SuperNode SE 1–75
DMS-core 1–77
SuperNode SE computing module 1–78
System load modules 1–82
Files and file management 1–83
DMS-bus 1–84
Message switch 1–86
Enhanced network and interface shelf 1–88
Functional subsystems of ENET 1–88
Link interface shelf 1–91
Frame supervisory panel 1–91
Cabinet cooling unit 1–91
Signaling among DMS SuperNode SE components 1–92
DS30 protocol 1–92
DS512 protocol 1–92

Software engineering 2–1

Distributed processing 2–1
Central control firmware/software 2–2
Peripheral firmware/software 2–2
Software packaging 2–2
Custom feature development 2–3
Software delivery 2–3
One-night process 2–3
Software development process 2–4
Planning 2–4
Development 2–4
Verification 2–4
Validation testing 2–4
Availability 2–4
Internal software structure 2–4
PROTEL 2–6
Major subsystems of DMS-100 Family software 2–7
Support operating system 2–7
DMS-100 family database system and software 2–14
Call processing applications software 2–18
Fault detection and system recovery 2–22
System recovery controller software 2–34
SRC functions 2–35
SRC conditions 2–36

PLN-5001-001i Standard 02.02 April 1997

 Contents v

SRC triggers 2–37

SRC dependency manager 2–38
Broadcast-loading 2–39
Automatic broadcast-loading 2–40
Limitation of concurrent load activities 2–41
Audits 2–41
DMS-100 Family peripheral software 2–43
Peripheral processing 2–45

System capacity and performance 3–1

Capacity overview 3–1
Processor task execution 3–1
Dial tone delay (call request delay) 3–2
Incoming response delay 3–3
DMS SuperNode processors 3–3
Real time allocation 3–4
System operating software (SOS) scheduler 3–4
Processor real time allocations 3–4
Overhead classes 3–5
Call processing classes 3–8
Planning and engineering 3–8
Engineering factors 3–9
Call timings 3–13
Engineering and planning 3–17
Engineering factors 3–17
Grade of service 3–18
DMS SuperNode grade of service analysis 3–18
Operating guidelines 3–20
Engineering considerations – load level 3–20
Capacity prediction and verification tools 3–21
Memory 3–22
DMS SuperNode memory 3–22
System load module capacity 3–23
Enhanced network (ENET) capacity 3–23
Peripheral module termination capacity 3–24
Monitoring and administration 3–24
Performance standards 3–25
Basis for provisioning of engineered facilities 3–25
Provisioning methodology 3–26
Service standards 3–26
Service circuits 3–27
Overload and abnormal conditions 3–29
Overload controls and protection 3–30
Speed of service 3–32
Mishandled calls 3–37
Reliability 3–37
Hardware failures 3–37
System downtime 3–37

Features 4–1
Features common to residence and business 4–1

DMS-100 International Technical Specification BCS40i and up

vi Contents

Individual line 4–1

Free terminating line service 4–1
Free number origination (FNO) 4–1
Denied terminating line service (DNTR) 4–2
Denied originating line service (DOR) 4–2
Emergency lines (free number terminating – FNT) 4–2
Plugged up line (PLP) 4–2
Suspended service (SUS) 4–2
Code restriction 4–2
Hunting features 4–2
Dial pulse dialing 4–4
Dual tone multifrequency (DTMF) dialing 4–4
Malicious call trace 4–4
Emergency cut-off 4–5
Subscriber services 4–5
Abbreviated dialing 4–6
Call diversion 4–7
Call waiting features 4–8
CEPT hot line 4–9
Digipulse (DP) activation of subscriber features 4–10
Warm line (WLN) 4–10
Subscriber activated outgoing restrictions 4–11
Subscriber features denied 4–12
No double connect 4–13
Ring again 4–13
Selective charge recording (SCR) 4–14
Call transfer 4–15
Three and six way calling 4–15
Wakeup call 4–16
Call party control using translations 4–17
Miscellaneous local system features 4–19
Compatibility with dial long line circuits 4–19
Loop start line 4–20
Coin telephone control signaling 4–20
Subscriber premise meter 4–20
Guaranteed dial tone for DMS-100 International 4–20
Dial tone speed recording for International 4–20
DTSR statistics 4–20
Faultsman’s ring-back 4–22
Faultsman’s digit test 4–22
Semi-permanent connections 4–24
Operator tones 4–24
Insert tone on coin phone terminations 4–24
Toll break in – background tone 4–24
TBI MAP signaling command 4–24
Attendant pay stations 4–25
Service hall operation 4–26
Call detail records 4–26
Announcements 4–28
Recorded announcement service (local) 4–28
Digital recorded announcement system (DRAM) 4–28

PLN-5001-001i Standard 02.02 April 1997

 Contents vii

Ringing 4–29
Individual line ringing 4–29
Audible ringing tone 4–29
IXPM features 4–29
IXPM warm SWACT 4–29
IXPM performance monitoring 4–30
Interoffice features 4–31
Interoffice address signaling 4–31
Call state supervisory signaling 4–31
Intraoffice connecting arrangements 4–31
International killer trunks 4–31
IRLCM features 4–32
Intraswitching on the IRLCM 4–32
IRLCM intraswitching for subscriber features 4–34
ESA for IRLCM – basic 4–35
IRLCM ESA entry and exit 4–37
Downloadable tones 4–40
XPM static data audit on downloadable tones 4–40
Second dial tone over trunks 4–41
Call processing features 4–42
Overload control and protection of essential services 4–42
Call processing 4–42
System maintenance features 4–43
Hardware redundancy 4–43
Trouble detection 4–43
Audit programs 4–43
Call processing data base trouble detection 4–44
Periodic automatic tests 4–44
Service recovery and protection measures 4–44
Trouble verification 4–47
Recovery from faulty equipment 4–48
User interfaces 4–49
Maintenance and administration position (MAP) 4–49
System maintenance input/output interface 4–50
Trunk, line and service circuit test features 4–51
Trunk maintenance 4–51
Transmission measurements 4–52
Local office test lines 4–52
Administrative features 4–53
Data base management-memory alteration 4–53
Data base integrity and security 4–54
Monitoring of recent change area 4–54
Teletypewriter input/output 4–54
Automatic traffic measurements 4–55
Measurement applications 4–55
Service measurements 4–56
Network administration center I/O channel 4–56
Data verification capabilities 4–56
Network management (NM) 4–57
Network management surveillance data 4–57
Miscellaneous features 4–58

DMS-100 International Technical Specification BCS40i and up

viii Contents

Cut-over and growth features 4–58

Call processing 5–1

Line originated calls 5–1
Treatments 5–14
Class of service (COS) restrictions 5–16
Hunt groups 5–16
Trunk originated calls 5–17
Software description 5–29
Call processing functional concepts 5–29
Basic telephone call – general steps 5–30
Basic telephone call – DMS call processing sequence 5–30

Interfaces and signaling 6–1

Interfaces 6–1
Interface circuit functionalities 6–1
Interface circuitry protective characteristics 6–2
Low-frequency (50 Hz & 60 Hz) AC induction 6–2
High-voltage surges 6–2
Dielectric strength 6–3
Overvoltage protection 6–3
Trunk interfaces 6–4
International digital trunk controller 6–4
Packaging and power 6–4
PCM-30 interface specifications 6–4
Control interface specification 6–5
Framing 6–5
Idle channel transmission 6–5
Digital trunk signaling 6–5
Trunk signaling timing parameters 6–6
Register signaling variants 6–6
Programmable R2 register signaling 6–7
Programmable R2 data tables 6–8
R2 protocol verification 6–8
Generic R2 register signaling activities 6–8
R2 generic numeric address information activities 6–9
R2 generic address control activities 6–12
R2 generic calling party category activities 6–20
Generic R2 automatic number identification activities 6–28
Generic R2 called subscriber status activities 6–37
Generic R2 special activities 6–50
Multifrequency compelled register signaling codes 6–51
R2 signaling timing 6–52
Interoffice line signaling 6–53
Updating of signaling system data in the peripheral modules 6–56
Call processing 6–57
End-to-end signaling 6–57
R2 trunk classes 6–57
Call control 6–57
PCM-30 carrier maintenance and alarms 6–58
Common channel signaling 7 (CCS7) 6–62

PLN-5001-001i Standard 02.02 April 1997

 Contents ix

CCS7 overview 6–62

Modes of operation 6–64
How nodes communicate across the network 6–66
How messages are handled in a CCS7 network 6–69
Signaling message path through a DMS-STP 6–71
Subscriber interfaces 6–74
Line circuits 6–74
Line circuit types 6–74
World line card 6–74
Office (exchange) battery 6–75
Ringing 6–75
Tones generation 6–75
Coin telephone interface 6–76
Private branch exchange (PBX) interface 6–76
Subscriber premise meter control 6–76
Speech coding and decoding 6–76
Test access 6–76
Loop loss control 6–76
50 hz or 60 hz filtering 6–76
Loop supervision 6–76
Dialing 6–77
Subscriber line signaling 6–79
Supervisory states 6–79
Open intervals during call processing 6–79
Detection of line supervisory states 6–79
Handling of abnormal line conditions 6–80
Address detection 6–80
Rotary dial pulse detection 6–80
Dual-tone multifrequency (DTMF) detection 6–80
DTMF frequencies 6–80
DTMF reception 6–81
Subscriber premise meters 6–82
Ringing 6–82
Ringing source 6–82
Audible ring tone 6–82
Ring trip 6–82
Coin line signaling 6–83
Private branch exchange (PBX) line signaling 6–83
Subscriber line maintenance 6–83
Subscriber line test circuits 6–83
Test access (TA) 6–83
Cut-over control 6–83
Analog loop-around 6–84
Digital loop-around 6–84
Metallic test access (MTA) 6–84
Data communication interface (X.25, V.35) 6–85

Administration 7–1
Data recording 7–1
Magnetic tape 7–3
Disk 7–10

DMS-100 International Technical Specification BCS40i and up

x Contents

Data polling 7–13

Operational measurements (OM) 7–13
Operational measurements system components and organization 7–14
Measurement blocks 7–19
International OM overview 7–20
AMA 7–22
ANN 7–23
CF3P 7–23
CF6P 7–24
CMC 7–25
CP 7–26
CP2 7–28
CPU 7–29
CSL 7–30
DCM 7–30
DDU 7–30
DS1CARR 7–31
DTSR 7–31
DTSRPM 7–31
EXT 7–32
FTRQ 7–32
FTRQOM_INFO 7–33
FTRQSEIZ 7–33
FTRQOVFL 7–33
FTRQUSGE 7–33
FTRQHI 7–33
HUNT 7–33
IADL 7–33
ICDIVF 7–35
ICDIVP 7–36
ICONF 7–38
ICWT 7–39
IDND 7–40
IFDL 7–41
ILR 7–41
INDC 7–43
IOC 7–43
IOSYS 7–44
IWUC 7–44
LM 7–45
LMD 7–45
LOGS 7–46
MACHACT 7–47
MTA 7–48
MTRERR 7–48
MTRUSG 7–48
MTRPERF 7–51
MTU 7–53
NMC 7–53
NWMTGCNT 7–54
OFZ 7–54

PLN-5001-001i Standard 02.02 April 1997

 Contents xi

OFZ2 7–54
OTS 7–54
PCMCARR 7–58
PM 7–60
PMTYP 7–62
PM1 7–64
PM2 7–64
RADR 7–65
RCVR 7–65
SOTS 7–65
SPC 7–67
STN 7–68
SVCT 7–68
TFCANA 7–68
TM 7–69
TONES 7–69
TRK 7–69
TRMTCM 7–71
TRMTCU 7–72
TRMTCU2 7–72
TRMTER 7–72
TRMTFR 7–73
TROUBLEQ 7–73
TS 7–74
UTR 7–74
OMs For International subscriber features 7–75
Network management (NWM) 7–77
Network management (VDU) 7–77
Status board lamp display 7–78
Network management controls 7–78
Network management displays 7–85
Administration of manual controls 7–90
Database management 7–96
Memory alteration 7–96
Teletypewriter (TTY) input/output 7–98
Automatic traffic and engineering measurements 7–98
Memory verification 7–98
Routing of output messages 7–98
Trunks out-of-service for data changes 7–99
Database facilities and structures 7–99
Table editor (TE) 7–99
Dump/restore 7–111
Pending order file (POF) 7–111
Journal file (JF) 7–112
Service analysis (SA) (observing) 7–114
DMS-100 and DMS-200 service analysis 7–114
Call progress data – automatically detected 7–114
Call progress data – analyst detected 7–115
Service analysis increased sample rate 7–115
DMS-300 service analysis 7–115
Multi-unit message rate services (MUMR) 7–116

DMS-100 International Technical Specification BCS40i and up

xii Contents

Fraud prevention feature 7–116

Malicious call trace (MCT) 7–116

Billing 8–1
DMS switch billing features 8–1
ITOPS billing 8–1
International Call Recording 8–1
Inter Administration Accounting 8–1
International Centralized Automatic Message Accounting 8–1
DMS-100 meter billing 8–1
Meter billing system description 8–2
Software meters 8–2
Determining call charges 8–3
Tariffs 8–4
Determining tariff rates 8–5
The time-of-day system 8–7
Meter pulse tandeming 8–7
Line and trunk metering 8–9
Metering for subscriber features 8–10
Meter billing files 8–11
DIRP interface 8–11
Billing file content 8–12
Billing records 8–12
Viewing the billing file 8–14
Meter billing file format 8–15
Accessing the meter billing system 8–18
Line data changes 8–18
Trunk group data changes 8–19
Meter audits 8–19
THQ audit 8–19
Billing recovery process 8–20
Meter backup utility 8–20
System restarts 8–21
Logs 8–21
Control of log messages 8–21
LOGUTIL 8–21
DMS-100 billing logs 8–21
Priority logs 8–25
Log thresholds and log suppression 8–25
Where to find log information 8–25
Operational measurements 8–26
DMS-100 billing OM groups 8–26
DMS-100i billing priority OM registers 8–26
OM thresholding 8–28
Switch Performance Monitoring System 8–28
DMS-100 billing-specific SPMS index 8–29
Where to find OM information 8–29
Alarms 8–29
Commands 8–30
Menu commands 8–31
Non-menu commands 8–42

PLN-5001-001i Standard 02.02 April 1997

 Contents xiii

Where to find command information 8–48

Translations 8–49
Translations database 8–49
Terms used in translations 8–50
Using the table editor to modify datafill 8–51
Translations table flow 8–52
Datafill sequence 8–54
Datafilling office parameters 8–55
ICAMA feature description 8–57
ICAMA feature activation 8–57
ICAMA call processing 8–58
Recording unanswered calls 8–58
Exception and error handling 8–58
AMA stream 8–59
Restarts/SWACTs 8–60
AMA dump utility 8–62
ICAMA call record format 8–63
Call record field descriptions 8–63
ICR feature description 8–67
ICR feature activation 8–67
ICR call processing 8–67
ICR call restrictions and limitations 8–68
ICR call record field description 8–68
IAA feature description 8–71
Activating IAA 8–72
IAA call processing 8–72
IAA error handling 8–72
IAA call record description 8–73
ITOPS feature description 8–75
Activating ITOPS 8–75
ITOPS call records 8–76
ITOPS standard call record 8–76
Special billing extension record 8–82
Hotel billing extension record 8–83
Charge extension record 8–84
Charge adjustment extension record 8–85
Foreign alternate route extension record 8–86
Database call extension record 8–87
Special long billing extension record 8–88
MASSTC feature 8–89

ITOPS 9–1
ITOPS description 9–1
ITOPS services and capabilities 9–2
ITOPS rating system 9–3
ITOPS billing plan 9–5
Delay call database feature 9–7
Automatic number identification 9–7
Flexible subscriber number formatting 9–8
Toll break-in 9–8
Speech path splitting 9–8

DMS-100 International Technical Specification BCS40i and up

xiv Contents

Call transferring 9–8

Assistance and in-charge positions 9–8
Hotel billing information center 9–9
Periodic force management reports 9–9
Enhanced Automatic Call Distribution 9–9
Attended pay station call handling 9–9
Other ITOPS features 9–10
Fixed duration calls 9–10
Charge estimations 9–10
Toll access restriction by account code 9–10
Intrusion tone 9–10
ITOPS software functionality overview 9–11
Call processing functionality 9–11
Operator functionality 9–16
Force management functionality 9–17
HOBIC functionality 9–18
Maintenance functionality 9–18
ITOPS feature packages 9–18
ITOPS Common Basic - NTXB05 9–19
ITOPS Toll–Enhanced Queuing - NTXB13 9–19
International Rating System - NTXB84 9–29
ITOPS hardware components 9–41
ITOPS hardware architecture 9–41
ITOPS equipment 9–44
Additional ITOPS software feature packages 9–49
ITOPS International R2 Interworking – NTXB83 9–50
Fixed Duration Calls – NTXH13 9–50
Estimated Call Charges for ITOPS – NTXH16 9–50
ITOPS – Account Code Access – NTXH54 9–51
ITOPS Intrusion Tones – NTXH71 9–52

Maintenance 10–1
Maintenance and administration position 10–2
MAP provisioning 10–2
MAP components 10–3
MAP interface to the DMS-100 Family system 10–6
MAP access and security features 10–6
Automatic dial-back 10–7
Command screening 10–7
Password control 10–7
Access control 10–7
Audit trail 10–8
Automatic logout of dial-up lines 10–8
System maintenance using the MAP 10–8
MTC level system status information 10–9
MTC level MAP commands 10–11
MTC sublevels 10–11
Alarms 10–12
Isolation of faults 10–13
Log report system 10–13
DMS-100 Family system maintenance 10–14

PLN-5001-001i Standard 02.02 April 1997

 Contents xv

Maintenance capabilities 10–14

Overview of maintenance actions 10–14
Real-time activity indicator 10–15
Circuit selection procedures 10–15
Sanity tests 10–15
Calls encountering trouble 10–16
Safeguards 10–16
DMS-100 family diagnostic system 10–17
System alarms 10–18
Alarm system operation 10–18
Alarm classes 10–19
Audible alarms 10–19
Alarm control and display panel 10–20
Alarm display panel 10–20
Exit alarm panel 10–21
Equipment aisle visual alarms 10–21
Dead system alarm 10–21
No call processing alarm 10–21
Audible alarm reset 10–22
Trunk test center alarms 10–23
TTC night alarm transfer 10–23
Line test center alarms 10–23
Remote alarm transfer 10–23
Alarm grouping 10–24
Alarm circuit power detection 10–24
External alarms 10–24
Operating company defined alarm capabilities 10–24
Alarm sending and checking system 10–24
MAP alarm level screening feature 10–25
Station ringer test 10–25
SRT capabilities 10–25
SRT implementation 10–26
User defined command files 10–27
Dialable cable locator tone 10–27
Silent switchman feature 10–27
Dialable short circuit 10–28
Interoffice transmission testing 10–28
Nl00, Sl00, Tl00 test line 10–28
Tl0l test line 10–28
Tl02 test line 10–29
ATME test line 10–29
ARTER test line 10–29
Trunk test facilities and features 10–30
Trunk test facilities at the maintenance center 10–30
Focused trunk maintenance 10–31
Automatic trunk test facilities 10–32
Cutover and growth features 10–33
Procedures for trunk growth and testing 10–33
Procedures for data store and network module extension 10–33
Procedures for line growth and testing 10–34
Implementation of growth 10–34

DMS-100 International Technical Specification BCS40i and up

xvi Contents

Line test facilities 10–35

Line testing hardware 10–35
Line test position 10–35
Line test unit 10–36
Transmission test unit 10–36
Transmission test trunk 10–36
Jack-ended trunk 10–36
External test equipment 10–36
Metallic test access 10–36
Printer 10–36
I/O test trunk 10–37
Communication test line 10–37
Line test descriptions 10–37
Short diagnostic test 10–38
Extended diagnostic test 10–38
Focused line maintenance 10–39
Automatic line testing 10–39
Line card overvoltage protection 10–39

Transmission 11–1
Transmission level 11–1
Analog connection transmission specifications 11–1
Measurement points 11–1
Transmission specifications 11–1
Digital milliwatt (digital test sequence) 11–2
Equipment transmission levels 11–2
Characteristics of subscriber line interfaces (NT6X93, NT6X94) 11–3
VF parameters for subscriber line-to-line connections 11–5
Digital connection transmission specifications 11–9
International digital trunk controller (IDTC) 11–9
Digital trunk to digital trunk echo path delay 11–11
Transmission pads 11–11
Clock synchronization 11–12
NT40 clocking 11–13
DMS SuperNode clocking 11–17
Slip rate 11–18
Frequency capture width 11–19
Error rate 11–19
Compression law 11–19
CODEC transfer characteristics 11–20
Decision levels 11–20

Equipment 12–1
Physical 12–1
Equipment frames 12–8
Equipment frame dimensions 12–8
Equipment frame lineups 12–9
Equipment frame loading and support 12–9
Equipment frame earthquake resistance 12–10
Equipment frame floor plans 12–12
Host office floor plans 12–12

PLN-5001-001i Standard 02.02 April 1997

 Contents xvii

Remote office floor plans 12–16–16–19

Floor plan data 12–22
Floor plan requirements 12–24
Distributing frame 12–24
DC power equipment 12–24
Power distribution center 12–24
Cable distribution 12–25
Building provisions 12–26
Ceiling height 12–26
Building ceiling supports 12–26
Column and cable hole spacing and arrangements 12–27
Frame handling and door openings 12–27
Air conditioning 12–27
Environment 12–27
Ambient temperature and humidity 12–27
Heat dissipation 12–28
Air cleanliness 12–28
Fire resistance 12–28
Transportation and storage environments 12–29
Grounding 12–29
AC coupling 12–30
DC coupling 12–30
Frame ground 12–30
Framework isolation 12–30
Signal ground 12–30
Illumination 12–30
Electromagnetic interference 12–31
Electromagnetic emissions 12–31
Radiated susceptibility 12–31
Audio noise emissions 12–31
Miscellaneous 12–31
Hardware 12–31
Floor maintenance 12–33
Craftsperson interfaces 12–33
Input/output system 12–33
Magnetic tape devices (MTD) 12–34
Disk drive units 12–35
Visual display units 12–35
Teleprinters 12–35

Power requirements 13–1

Operating voltage 13–1
Battery noise limits 13–1
Power consumptions 13–2
Power alarms 13–3
DC power distribution (PDC) 13–4
Office battery to power distribution center 13–4
Grounding systems in DMS-100 family 13–6
Framework ground arrangements for non-ISG installations 13–6
Framework ground for ISG installations 13–9
AC grounding arrangements 13–12

DMS-100 International Technical Specification BCS40i and up

xviii Contents

Frame loads 13–12

DMS SuperNode cabinet 13–13
Central control complex and memory extension frame 13–14
Network module frame 13–17
Trunk module equipment frame 13–21
Digital carrier equipment frame 13–24
Line module equipment frame 13–26
Line concentrating equipment frame 13–28
Line group equipment frame 13–30
Magnetic tape center frame 13–32
Remote line facility 13–34
Clustering 13–34
Integrated maintenance and administration position (IMAP) 13–35
Maintenance and administration position (MAP) 13–35
Power distribution center (PDC) 13–36
DC-DC converters 13–38
AC power distribution 13–38
Outside plant module power requirements 13–38
Lighting and AC receptacles 13–39
Power and ground interfacing 13–40
Power plant sharing 13–41

Documentation 14–1
Documentation media 14–1
Documentation ordering 14–1
Documentation catalogs 14–1
Documentation structure 14–1
Modular documentation system 14–2
Characteristics of MDS 14–2
MDS document identifiers 14–4
Northern Telecom publications 14–5
NTP index 14–6
Job specific documentation 14–7
Document index 14–7
Office-inventory record 14–7
Office feature record 14–7
Central office job specifications 14–7
Central office job drawings 14–7
Common systems drawings (as required) 14–8
Non-proprietary hardware documentation 14–8
Module structure (MS) 14–8
Assembly drawings (AD) 14–8
Interconnect schematics (IS) or functional schematics (FS) 14–8
Cabling assignments (CA) 14–8
Systems documentation 14–9
Northern Telecom publications 14–9
Peripheral module software release document 14–10
BCS preparation guide 14–10
Optional documentation 14–10
Feature description manual (FDM) 14–10
Peripheral module software release document 14–10

PLN-5001-001i Standard 02.02 April 1997

 Contents xix

DMS-100 family capacity manual 14–10

TRAVER 14–10
Proprietary documentation 14–11
Proprietary information list 14–11
Release control record 14–11
Detailed assembly drawing (DAD) 14–11
Program documentation index (PDI) 14–12
Central control software program listings 14–12
Program description information 14–12
Central control cross references (subsystem SEXREF, GXREF) 14–12
XPM peripheral module firmware/software listing 14–12
Operating manuals 14–13
Programmers manuals 14–13
Software debug manuals 14–14
DMS-100 family system description 14–14
Network integrity fault analysis guidelines 14–14
Technical assistance manuals 14–14
Installation manuals 14–15

List of terms 15–1

List of figures
Figure 1–1 DMS distributed architecture 1–2
Figure 1–2 DPCC cabinet 1–4
Figure 1–3 Upgrading the NT40 platform to DMS SuperNode 1–6
Figure 1–4 Main components of the DMS-Core 1–7
Figure 1–5 DMS-bus components 1–14
Figure 1–6 Inter-MS links configuration 1–16
Figure 1–7 Memory modules, pages and segments 1–20
Figure 1–8 Layout of a DSNE frame 1–21
Figure 1–9 Junctored network port configuration 1–23
Figure 1–10 Duplicated network module controller 1–24
Figure 1–11 Intra-network connection (JNET) 1–26
Figure 1–12 Inter-network connection (JNET) 1–27
Figure 1–13 64K single-cabinet ENET layout 1–29
Figure 1–14 128K dual-cabinet ENET layout 1–30
Figure 1–15 Example of an ENET connected to a Series II PM 1–32
Figure 1–16 Input/output device configuration 1–36
Figure 1–17 Input/output equipment frame layout 1–37
Figure 1–18 ILCM shelf organization 1–41
Figure 1–19 ILCM frame packaging 1–42
Figure 1–20 Duplication within the ILCM 1–43
Figure 1–21 Network – ILGC – ILCM Connections 1–46
Figure 1–22 Organization within the ILGC 1–48
Figure 1–23 CM and MS signaling paths 1–54
Figure 1–24 LPP physical configuration 1–57
Figure 1–25 Organization of a two-slot LIU7 1–59
Figure 1–26 Non-channelized access link configuration 1–60
Figure 1–27 Channelized access external interface configuration 1–61
Figure 1–28 CCS7 channelized access system overview 1–62
Figure 1–29 Two-slot link interface shelf with an NIU 1–63

DMS-100 International Technical Specification BCS40i and up

xx Contents

Figure 1–30 NIU bus configuration 1–65

Figure 1–31 SSLPP F-bus and MS interconnections 1–66
Figure 1–32 An example of an EMC cabinet with SSLPPs 1–67
Figure 1–33 SSLPP card arrangement arrangement 1–68
Figure 1–34 Relationships Within the IRLCM 1–69
Figure 1–35 IRLCM Frame Layout – Front View 1–70
Figure 1–36 HIE shelf layout 1–71
Figure 1–37 LCA shelf layout 1–73
Figure 1–38 RMM shelf layout 1–74
Figure 1–39 DMS SuperNode SE SuperNode combined core cabinet 1–76
Figure 1–40 DMS SuperNode SE functional block diagram 1–77
Figure 1–41 Main components of the DMS-core – SuperNode SE 1–78
Figure 1–42 DMS SuperNode SE CMIC link configuration 1–81
Figure 1–43 DMS-bus components 1–85
Figure 1–44 Inter-MS links configuration – SuperNode SE 1–86
Figure 1–45 Example ENET connection to a Series II PM 1–90
Figure 2–1 Internal structure of a module 2–6
Figure 2–2 Support operating system (SOS) 2–8
Figure 2–3 Physical devices supported by the file system 2–13
Figure 2–4 Logical and physical tables 2–15
Figure 2–5 DMS-100 database system 2–17
Figure 2–6 DMS-100 family (NT40) – major subsystems 2–24
Figure 2–7 Network and peripheral fault detection 2–28
Figure 2–8 Network fault detection 2–29
Figure 2–9 Example of system recovery (NT40) 2–32
Figure 2–10 System recovery controller 2–36
Figure 3–1 Distribution of CPU occupancy (DMS SuperNode) 3–19
Figure 4–1 DTSR collection 4–22
Figure 4–2 Intra/inter LCA connections 4–33
Figure 5–1 Processing of line originated calls 5–5
Figure 5–2 Key for line and trunk originated call flow illustrations 5–6
Figure 5–4 Processing of trunk originated calls 5–21
Figure 5–6 Message exchanged by CC, NMs and PMs for a basic voice call
5–31
Figure 6–1 Surge waveshape 6–3
Figure 6–2 Connection-oriented signaling (trunk signaling) 6–62
Figure 6–3 Connectionless signaling (transaction services) 6–63
Figure 6–4 Associated signaling in a simple configuration 6–64
Figure 6–5 Quasi-associated signaling mode 6–65
Figure 6–6 Quasi-associated signaling in a complex configuration 6–66
Figure 6–7 CCS7 network communications 6–68
Figure 6–8 CCS7 message routing label 6–70
Figure 6–9 DMS-STP message processing 6–73
Figure 6–10 International Line Circuit – Type A 6–77
Figure 6–11 International line circuit – Type B 6–78
Figure 7–1 Data recording 7–2
Figure 7–2 Magnetic tape recording format 7–5
Figure 7–3 Label organization for a single data set on a single volume 7–7
Figure 7–4 Label organization for multiple data sets on a single volume
7–8
Figure 7–5 DTC and TM reports 7–18

PLN-5001-001i Standard 02.02 April 1997

 Contents xxi

Figure 7–6 AMA demand report 7–19

Figure 7–7 NWM level display 7–86
Figure 7–8 Display finals commands 7–88
Figure 7–9 AUTOCTRL menu and example display 7–89
Figure 7–10 GRPCTRL menu and example display 7–90
Figure 7–11 Structure of typical table and subtable 7–101
Figure 8–1 Meter pulsing options 8–5
Figure 8–2 Meter pulse application 8–8
Figure 8–3 Tandeming of meter pulses to hardware meters and incoming
trunks 8–8
Figure 8–4 Example of line billing record formats 8–13
Figure 8–5 Trunk billing records 8–14
Figure 8–6 Byte format for a line billing record 8–16
Figure 8–7 Byte format for a trunk billing record 8–17
Figure 8–8 DMS MAP menu levels 8–31
Figure 8–9 Menu commands at the MTRSYS level of the MAP display
8–32
Figure 8–10 Menu commands at the AUDIT level of the MAP display 8–34
Figure 8–11 Menu commands at the TTP level of the MAP display 8–35
Figure 8–12 TTPSUB MAP level menu 8–36
Figure 8–13 LTP MAP level menu 8–38
Figure 8–14 LTPMTR MAP level menu 8–39
Figure 8–15 DIRP MAP menu 8–40
Figure 8–16 Illustration of translations terms 8–50
Figure 8–17 ICAMA feature application 8–57
Figure 8–18 Impact of cold or reload restarts on ICAMA recording 8–60
Figure 8–19 Impact of CC warm restarts on ICAMA recording 8–61
Figure 8–20 ICAMA call record format 8–63
Figure 8–21 Call information field details 8–64
Figure 8–22 Call record tape format 8–65
Figure 8–23 ICAMA record format example 8–66
Figure 8–24 ICR record format 8–70
Figure 8–25 International call types and recording methods 8–71
Figure 8–26 IAA record format 8–74
Figure 8–27 ITOPS standard record format 8–76
Figure 8–28 ITOPS special billing extension record 8–82
Figure 8–29 ITOPS hotel billing extension record 8–83
Figure 8–30 ITOPS charge extension record 8–84
Figure 8–31 ITOPS charge adjustment extension record 8–85
Figure 8–32 ITOPS alternate route extension record 8–86
Figure 8–33 ITOPS database call extension record 8–87
Figure 8–34 ITOPS special long billing extension record 8–88
Figure 8–35 MASSTC program states 8–90
Figure 9–1 ITOPS position components 9–1
Figure 9–2 ITOPS operator position connections connectional 9–20
Figure 9–3 Sample configuration of a multitraffic office 9–22
Figure 9–4 Typical ITOPS call configuration 9–26
Figure 9–5xx Rating areas 9–34
Figure 9–6 Mass table control state diagram 9–37
Figure 9–7 ITOPS hardware architecture 9–43
Figure 10–1 Maintenance and administration position 10–3

DMS-100 International Technical Specification BCS40i and up

xxii Contents

Figure 10–2 MAP display layout 10–5

Figure 10–3 MTC level MAP display example 10–9
Figure 10–4 Network level display example 10–12
Figure 11–1 Input return loss limit 11–3
Figure 11–2 Arrangement for measuring TBRL 11–4
Figure 11–3 Terminal balance return loss limit 11–5
Figure 11–4 Attenuation distortion limits 11–6
Figure 11–5 Limits for signal-to-total distortion ratio 11–8
Figure 11–6 Synchronous clock system outline of possible configurations
11–13
Figure 11–7 Synchronous clock system (simplified block diagram) 11–16
Figure 11–8 Codec transfer characteristics 11–21
Figure 12–1 Typical floor for 25 000 line, 5000 trunk DMS-100 office 12–13
Figure 12–2 Typical cable duct and cable rack layout 12–15
Figure 12–3 Typical floor plan for a 640 line DMS-100 family RLCM office 12
Figure 12–4 RLCM typical cable duct and cable rack layout 12–18
Figure 12–5 Typical floor plan for a 1280 line DMS-100 family RSC office 12
Figure 12–6 RSC typical cable duct and cable rack layout 12–20
Figure 12–7 Outside plant module — interior view 12–22
Figure 12–8 Cable trough assembly 12–26
Figure 13–1 Typical PDC arrangement 13–5
Figure 13–2 Framework arrangement – non-ISG installations 13–8
Figure 13–3 Framework ground and logic return – ISG systems 13–11
Figure 13–4 DMS SuperNode cabinet power distribution 13–14
Figure 13–5 CCC and MEX frame power distribution 13–16
Figure 13–6 NT5X13 NM frame power distribution 13–18
Figure 13–7 NT0X48 NM frame power distribution 13–20
Figure 13–8 TME frame power distribution 13–23
Figure 13–9 DCE frame power distribution 13–25
Figure 13–10 LME frame power distribution 13–27
Figure 13–11 LCE frame power distribution 13–29
Figure 13–12 LGE frame power distribution 13–31
Figure 13–13 MTC frame power distribution 13–33
Figure 13–14 Typical PDC frame configuration (front view) 13–37
Figure 13–15 Recommended power plant configuration 13–41
Figure 13–16 Specific isolated battery return configuration shown here with
MDG/ground window arrangement 13–43
Figure 13–17 Configuration with non-isolated battery return 13–44
Figure 13–18 Shared power plant 13–45
Figure 14–1 Modular documentation system structure 14–3

List of tables
Table 1–1 SuperNode processor variations 1–10
Table 3–1 Real-time allocations/Grades-of-service 3–3
Table 3–2 Capacity increases – DMS SuperNode processors 3–3
Table 3–3 Real-time allocation of processor classes 3–4
Table 3–4 Processor engineering factors 3–9
Table 3–5 DMS SuperNode AWT factor percents 3–10
Table 3–6 NT40 AWT factor percents 3–10
Table 3–7 Japan call timings 3–13
Table 3–8 Turkey, Belize call timings 3–14

PLN-5001-001i Standard 02.02 April 1997

 Contents xxiii

Table 3–9 China call timings 3–15

Table 3–10 Australia call timings 3–16
Table 3–11 Maximum addressable memory values 3–23
Table 3–12 Probability of inadequately handled call attempts occurring
3–27
Table 3–13 Service circuits blocking and delay criteria grade of service
3–28
Table 3–14 DMS SuperNode and DMS-100 family PCP failure rates 3–39
Table 3–15 DMS SuperNode reliability performance (hardware failures only)
3–57
Table 3–16 Assumptions 3–57
Table 4–1 Second dial tone definitions in International markets 4–39
Table 6–8 Generic multifrequency compelled (MFC) signaling codes 6–52
Table 6–9 R2 signaling timing 6–52
Table 6–11 Carrier maintenance alarms 6–61
Table 6–12 DTMF dialing toneset 6–80
Table 6–13 DTMF reception parameters 6–81
Table 7–1 Structure of typical OM data table 7–17
Table 7–2 DMS-100 International OM groups 7–20
Table 7–3 Table editor commands 7–103
Table 7–4 Service order commands 7–105
Table 8–1 DMS-100i billing logs 8–22
Table 8–2 Priority logs 8–25
Table 8–3 DMS-100i billing OM groups 8–26
Table 8–4 DMS-100i billing priority OM registers 8–26
Table 8–5 DMS-100 billing SPMS index 8–29
Table 8–6 DMS-100 billing EXT alarms 8–30
Table 8–7 IRATE subcommands 8–43
Table 8–8 ICAMA call class codes 8–58
Table 8–10 MASSTC subcommands 8–93
Table 9–1 Call origination types 9–11
Table 9–2 Standard call details billing record 9–39
Table 9–3 ITOPS extension records 9–41
Table 9–4 Teletypewriters associated with a HOBIC 9–46
Table 9–5 Equipment provisioning for single-traffic and multitraffic offices
9–47
Table 10–1 ACD alarm conditions 10–21
Table 11–1 Digital standard level points 11–2
Table 11–2 Longitudinal conversion loss 11–5
Table 11–3 Variation of gain with input level 11–6
Table 11–8 CODEC decision levels 11–20
Table 12–1 DMS-100 family bays and corresponding shelves/drawers
12–2
Table 12–2 Shelf heights 12–7
Table 12–3 Earthquake bracing requirements 12–10
Table 12–4 Floor plan data 12–23
Table 12–5 Ambient temperature and humidity 12–28
Table 12–6 Additional equipment 12–31
Table 12–7 I/O devices 12–34
Table 12–8 Teleprinters 12–35
Table 12–9 Device requirements 12–36

DMS-100 International Technical Specification BCS40i and up

xxiv Contents

Table 12–10 Modem requirements 12–36

Table 13–1 Maximum power consumption per frame 13–2
Table 14–1 Associated documents 14–5

PLN-5001-001i Standard 02.02 April 1997

 xxv

About this document

This document describes the generic DMS-100 International product line,
including specifications for planning, administration, and maintenance. The
specifications and capabilities of a DMS-100 International switching system
vary depending on the market in which the system is deployed, the
application of the system, and the hardware and software provisioned. For
more information on market-specific functionalities, consult your Northern
Telecom regional representative.

When to use this document

Northern Telecom (NT) software releases are referred to as batch change
supplements (BCS) and are identified by a number, for example, BCS36.
This document is written for DMS-100 Family offices that have BCS40i and
up.
More than one version of this document may exist. The version and issue
are indicated throughout the document, for example, 01.01. The first two
digits increase by one each time the document content is changed to support
new BCS-related developments. For example, the first release of a
document is 01.01, and the next release of the document in a subsequent
BCS is 02.01. The second two digits increase by one each time a document
is revised and rereleased for the same BCS.
To determine which version of this document applies to the BCS in your
office, check the release information in DMS-100 Family Guide to Northern
Telecom Publications, 297-1001-001.
How to identify the software in your office
The Office Feature Record (D190) lists your current BCS and the NT feature
packages in it. You can view similar information on a MAP (maintenance
and administration position) terminal by typing
>PATCHER;INFORM LIST;LEAVE

and pressing the Enter key.

DMS-100 International Technical Specification BCS40i and up

xxvi About this document

Where to find information

The chart below lists the documents that you require to understand the
content of this document, or to perform the tasks it describes. These
documents are also referred to in the appropriate places in the text.
More than one version of these documents may exist. To determine which
version of a document applies to the BCS in your office, check the release
information in DMS-100 Family Guide to Northern Telecom Publications,
297-1001-001.
Additional information on documentation available for DMS-100
International switching systems is provided in the Documentation chapter of
this book.

Number Title

297-1001-126 Pending Order Subsystem Reference Manual

297-1001-127 Journal File Description
297-1001-310 Table Editor Reference Manual
297-1001-312 Device Independent Recording Package User Guide
297-1001-451 Customer Data Schema
297-1001-455 Office Parameters Reference Manual
297-1001-471 Service Analysis
297-1001-500 Guide to Maintenance Procedures (Index)
297-1001-594 Lines Maintenance Guide
297-1001-595 Trunks Maintenance Guide
297-1001-801i DMS-100 International Feature Description Manual
297-2101-200 Outside Plant Module Cabinet Description, Installation, and
Maintenance
297-2181-010 International Traffic Operator Position System (ITOPS) Product
Guide
297-2181-020 DMS-100 International Billing Services Operations Guide
297-2181-155 International Traffic Operator Position System (ITOPS)
Planning and Engineering Guide
297-2181-300 International Traffic Operator Position System (ITOPS)
Operator Guide
297-2181-310 International Traffic Operator Position System (ITOPS) Force
Management Guide

—continued—

PLN-5001-001i Standard 02.02 April 1997

 About this document xxvii

Number Title (continued)

297-2181-350 International Traffic Operator Position System (ITOPS)

Translations Guide
297-2181-524 International Traffic Operator Position System (ITOPS)
Maintenance Guide

End

DMS-100 International Technical Specification BCS40i and up

 1–1

System architecture
This chapter describes the functional architecture of the DMS-100
International switching system. Provisioning information provided in this
chapter is for explanatory purposes only, to describe the relationships of the
various subsystems and components. For more detailed information on
hardware and software functionalities and provisioning rules, consult the
following Northern Telecom publications (NTP):
• DMS-100 Family Provisioning Manual, 297-1001-450
• Hardware Description Manual, 297-1001-805
• DMS-100 International Feature Description Manual, 291-1001-801i

DMS-100 International system overview

Digital Multiplex Switching (DMS) is a stored program control switching
system capable of serving virtually any local, toll, or combined local/toll
application. The instructions (programs) required to perform call
processing, operations, administration, and maintenance tasks are stored in
the memory of a central processing element, which controls all DMS
operations by referencing and executing the required instructions.
All signaling within the DMS system is digital; therefore, all analog signals
entering the system are converted to digital format at the point of interface.
Signaling between elements of a DMS system occurs in both directions
(transmit and receive) simultaneously, via 512-channel fiber optic pairs, or
32-channel 2-wire pairs.
Speech connections are made via a fully digital network, using time division
multiplexing. The digital network allows flexibility within the switching
matrix, and virtually eliminates network blocking and crosstalk.
DMS architecture employs modular concepts in both its hardware and
software engineering. Each major hardware subsystem is
microprocessor-based and is equipped with sufficient processing power and
memory to control local subsystem functions with minimal intervention
from the central processing element. By distributing processing throughout
the system in this manner, the real-time available to the central processor to
perform high-level functions is dramatically increased. Figure 1–1 shows a
simplified view of the major distributed subsystems within a DMS system.

DMS-100 International Technical Specification BCS40i and up

1–2 System architecture

DMS-100 International Family switching systems are specially configured

for local, toll, and local/toll applications in the International (non-North
American) market. Systems belonging to this family are the DMS-100
International Local System, the DMS-200 International Toll System, and the
DMS-100/200 International Local/Toll System.
DMS-100 International Family switching systems can also be configured to
operate as network nodes within a common channel signaling 7 (CCS7)
network.
Figure 1–1
DMS distributed architecture
FW-xxxxx

Central processing
subsystem

Central messaging
subsystem

Switching network Input-output

subsystem

Input-output
Peripheral modules
devices

Subscriber Trunks
lines

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–3

DMS-100 International switching platforms

DMS-100 International switching systems can be deployed on any of the
three processing platforms currently available:
• DMS SuperNode
• DMS SuperNode SE
• NT40

The DMS-100 Family of switching systems provides a wide range of digital

switching and networking functions. All three platforms feature modular,
scalable architecture.
DMS SuperNode switching platform
The DMS SuperNode platform is the most powerful in terms of call
capacity, feature availability, and signaling options, and can terminate up to
100, 000 lines or 60, 000 trunks, depending on traffic and service mix. The
The DMS SuperNode combines core processing and messaging functions in
a single cabinet, the dual plane combined core (DPCC). The DPCC is
illustrated in figure 1–2.

DMS-100 International Technical Specification BCS40i and up

1–4 System architecture

Figure 1–2xxx
DPCC cabinet
FW30182

Frame
supervisory panel

MS 0

DMS-bus

MS 1

Computing
module shelf CPU 0 CPU 1

DMS-core

SLM 0 SLM 1

Core
cooling unit

DMS SuperNode SE switching platform

The DMS SuperNode SE platform is based on SuperNode technology and
combines central processing, central messaging, switching network, and
common channel signaling functionalities within a single cabinet.
SuperNode SE is fully compatible with all SuperNode family software and
hardware elements, and is capable of providing all functionality currently
available on SuperNode-based systems, at a reduced call processing
capacity. SuperNode SE is intended for offices requiring an initial capacity
of up to 13 000 subscriber lines. The network provides growth potential to
up to 40 000 subscriber lines or 12 000 trunks, depending on the required
traffic and service mix.

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–5

Switching platform upgradability

NT40 upgrades
Systems based on NT40 can be upgraded to the SuperNode processing
platform by substituting the central processing and messaging components
of the system, as shown in figure 1–3 on page 1–6. The SuperNode
upgrade increases call capacity, maximizes equipment space, and allows full
usage of all current and future DMS features and technological
developments. All subtending equipment resident on the NT40-based
system (switching network, input/output subsystem, and peripheral modules)
is fully compatible with the SuperNode platform.
NT40-based systems can also be upgraded to the SuperNode SE platform.
SuperNode SE upgrades
Systems based on SuperNode SE are fully compatible with SuperNode
technologies and can be upgraded on a modular basis as required. The
SuperNode SE platform integrates core (central processing and messaging),
switching network, and common channel signaling peripheral elements
within a single cabinet, which are all fully expandable to full-capacity
versions through upgrading of the appropriate hardware and software.

DMS-100 International Technical Specification BCS40i and up

1–6 System architecture

Figure 1–3xxx
Upgrading the NT40 platform to DMS SuperNode
FW30313

DMS-100 NT40 Central

control CPU

Central
message
controller

Switching I/O
network controller

Digital trunk Line group Trunk

controller controller module I/O devices

DMS SuperNode

DMS-Core

DMS-bus

Switching I/O
network controller

Digital trunk Line group Trunk

controller controller module I/O devices

DMS-100 International system elements

The following sections outline the major functional elements of the
DMS-100 International switching system, focusing primarily on the DMS
SuperNode switching platform. (The SuperNode SE platform is described
on page 1–75).

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–7

Central processing subsystem

The central processing subsystem coordinates call processing, diagnostics,
maintenance, user interface functions, and oversees the actions of distributed
processors within subtending nodes such as the switching network and
peripheral modules. On NT40-based systems, the control component is the
central control (CC). On SuperNode-based systems, the control component
is the DMS-Core.
DMS-Core
DMS-Core provides the processing resources and system management in
DMS SuperNode applications. DMS-Core also handles system integrity,
maintenance, and the loading and downloading of software. Figure 1–4
shows the main components of the DMS-Core.
Figure 1–4xxx
Main components of the DMS-Core

Processor bus

Master Memory DMS-bus System

processor interface load
MC68020 module

DMS-core

DMS-bus

Network IOC

The DMS-Core consists of two synchronized CM planes that are connected

by the mate exchange bus. To ensure system integrity between the active
and inactive planes, the mate exchange bus allows the processor on each
plane to compare computations. DS512 links connect the DMS-Core to the
DMS-Bus.

DMS-100 International Technical Specification BCS40i and up

1–8 System architecture

The DMS-Core is also configured with two system load modules (SLMs) for
storage of software loads, office images and PM loads. Each SLM consists
of one cartridge tape drive and one disk drive unit (DDU).
Computing module
The fully duplicated and synchronized CM is based on a 32-bit
microprocessor with a built-in instruction cache facility and an on-board
high-speed data cache.
The CM has the following features:
• 32-bit CPU based on a Motorola microprocessor
• integrated program and data store with single-bit error correction
• high-speed duplicated message controllers (MC)
• distributed control reset system
• direct access to SLM disk or tape
• both planes on the same CM shelf (duplex shelf packaging)
• integrated inventory management for online identification of product
type and vintage for individual cards and paddle boards
Functional subsystems of the computing module
The CM is a duplicated, synchronized processor with up to 240 Mbyte of
memory for each plane. A single shelf holds both planes.
The CM shelf is equipped with cards on the front of the shelf and
corresponding paddle boards on the rear. The cards share a common bus
with the paddle boards. The CM contains the following functional
subsystems:
• processor (NT9X10, NT9X13)
• memory (NT9X14)
• reset control (NT9X26)
• clock (NT9X22)
• bus termination (NT9X21)
• bus extension (NT9X27)
• power supply (NT9X30, NT9X31)
• interfaces (NT9X12, NT9X20)

Processor (NT9X13, NT9X10)

The processor subsystem consists of the CPU cards (NT9X10, NT9X13),
memory cards (NT9X14), and two reset terminal interface (RTIF) paddle
boards (NT9X26). The processor and memory subsystem is responsible for
call processing as well as the configuration and maintenance of the other
systems. The integrated program and data store provide single-bit error
correction as well as speed in processing calls.

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–9

The NT9X10 and NT9X13 cards house the microprocessor circuitry. A

range of processors is available for the DMS SuperNode switch: the Series
10, 20, 30, 40, 50 and Series 60 BRISC. These processors are variations of
the Motorola MC68000 family or the MC88000 RISC family of processors.
Series 10, the least powerful of the DMS SuperNode processors, supports
up to 200 000 plain ordinary telephone service busy hour call attempts
(POTS BHCA). The Series 10 processor is no longer available on new
DMS SuperNode switches.
Series 20 offers call processing power approximately double that of the
NT40, supporting 440 000 POTS BHCAs.
Series 30 supports up to 660 000 POTS BHCAs, as well as offering the
same advanced DMS SuperNode technology available with the Series 20
processors.
Series 40 supports up to 800 000 POTS BHCAs.
Series 50 BRISC, the most powerful of the DMS SuperNode processors,
is based on the Motorola MC88000 processor and the BNR reduced
instruction set computing (BRISC) technology. Series 50 BRISC can handle
1.2 million POTS BHCAs, allowing increased call-handling capacity and the
ability to offer advanced features and additional services. The Series 50
BRISC processor features a 33-MHz clock, dual-bus architecture, and cache
memory. BRISC functionality is transparent to current applications
software.
Converting to the Series 50 BRISC processor requires a straightforward
hardware upgrade, and the loading of the Series 50 software master package.
Series 60 BRISC processor and memory subsystem is a DMS-core
equipped with NT9X10AA processor cards, their associated NT9X26DB
RTIF paddle boards, and NT9X14EA memory cards. This provisioning
allows the DMS SuperNode to operate in burst memory mode, a memory
access protocol that speeds up sequential read and write accesses to and
from backplane memory.
Table 1–1 shows the SuperNode processors that are available, the
corresponding CPU card product engineering codes (PEC), and the POTS
BHCAs capacities.

DMS-100 International Technical Specification BCS40i and up

1–10 System architecture

Table 1–1xxx
SuperNode processor variations
Card PEC Processor series POTS BHCA

NT9X13JA 10 200 000

NT9X13BC 20 440 000
NT9X13GA 30 660 000
NT9X13HB 40 800 000
NT9X10AA 50 BRISC/60 BRISC 1 200 000

Additional information on DMS SuperNode central processing units is

provided on page 1–18.
Memory (NT9X14)
The memory cards provide storage for the CPU. The RTIF paddle board
monitors and decodes commands from the local terminal, or the optional
remote scanning system, or both, and passes them to the CPU in the form of
control signals. It also monitors processor signals and relays them to the
local terminal or remote scanning system.
Additional information on DMS SuperNode memory configuration is
provided on page 1–18.
Reset control (NT9X26)
The reset terminal displays processor state information and provides a
facility for local and remote resetting of the CM. The RTIF paddle board
has two interface ports. One port is connected to the local reset terminal,
and the other can be used to connect an optional remote reset terminal by a
modem.
There are two versions of the RTIF paddle board. In one version, the local
reset terminal is connected to the NT9X26AA card by an RS-232 interface.
In the other version, the local reset terminal is connected to the NT9X26AB
card by either an RS-232 interface or a 20-mA current loop interface, which
provides improved electrical grounding between the reset terminal and the
RTIF paddle board.
On both versions, the remote terminal port can be configured as either
RS-232 or E2A to handle transmission rates of 110 to 9600-baud. The local
terminal can be located up to 15 m (50 ft) from the RTIF paddle board when
an RS-232 interface is used. The local terminal can be located up to 458 m
(1500 ft) from the RTIF paddle board when a 20-mA current loop is used.

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–11

Clock (NT9X22)
Each CM contains a subsystem clock that provides link synchronization to
the MS. The accuracy of the clock is determined by the office clock located
in the MS. The basic time reference is obtained through the serial links.
Bus termination (NT9X21)
The bus termination consists of the CM bus terminator paddle board. It
provides resistive termination for the system bus in both the CM processor
shelf and the SLM shelf. In addition, it provides the circuitry required for
buffering the CM activity signal and extracting component identification
from the power converters.
Bus extension (NT9X27)
The CM bus extender paddle board (NT9X27AA) extends the peripheral bus
(P-bus) from the CM processor shelf to SLM shelf.
Power supply (NT9X30, NT9X31)
The power supply provides power for the CM shelf. It consists of two
+5V 86-A power converters (NT9X30) and two –5V 20-A power converters
(NT9X31).
The DMS SuperNode power system is protected by interlock. This feature
prevents the system from being powered off inadvertently while in service.
Interfaces (NT9X12, NT9X20)
The transmission subsystem controls in-band data communication with the
MSs and provides the crossover for links. It consists of a CPU port card
(NT9X12) and DS512 interface paddle boards (NT9X20).
The CPU port card provides serial message communications between the
CM and the MS. The DS512 paddle board provides the transmission
interface for a single bidirectional two-fiber DS512 format.
System load module shelf
The SLM shelf houses two provisionable SLMs (NT9X44) that connect
directly to the CM system bus, their power supplies, and interface circuitry.
The shelf is configured as an extension of the DMS-core.
The SLM shelf is also equipped with cards on the front and corresponding
paddle boards on the rear. The cards share a common bus with the paddle
boards. The SLM shelf contains the following functional subsystems:
• SLMs (NT9X44)
• interfaces (NT9X12, NT9X46)
• clock (NT9X22)
• bus termination (NT9X21)
• bus extension (NT9X27)

DMS-100 International Technical Specification BCS40i and up

1–12 System architecture

• power supply (NT9X30, NT9X47)

System load modules (NT9X44)
The SLMs are the software image storage and loading devices for the CM.
An SLM is packaged as a single, replaceable unit that consists of a 5.25-in.
(13.3 cm) hard disk drive, a 0.25-in. (6.35 mm) streaming cartridge tape
drive with a removable cartridge, and a central processor controller.
An SLM is used to perform the following tasks:
• bootload the CM and the MS from disk or tape
• load an office image into the inactive CPU
• dump an image to disk
• perform offline transfers from tape to disk, or disk to tape

Either CPU of the CM can be loaded from either SLM through the crossover
bus; however, if power is lost to one SLM, or if the NT9X12 card is faulty,
the SLM can load only the CPU on the same side of the switch.
Interfaces (NT9X12, NT9X46)
The transmission system controls in-band data communication with the CM
and MS, and provides the crossover for links. It consists of a CPU port card
(NT9X12) and two parallel port interface paddle boards (NT9X46).
The CPU port card provides serial message communications between the
SLM and the CM. The parallel port interface paddle boards connect the
synchronous bus on the CPU card to the SLM with the aid of an interconnect
cable.
Clock (NT9X22)
The subsystem clock provides link synchronization to the MS. The accuracy
of the clock is determined by the office clock located in the MS. The basic
time reference is obtained through the serial links.
Bus termination (NT9X21)
Bus termination is provided by the CM bus terminator paddle board. It
provides resistive termination for the system bus in both the SLM shelf and
the CM processor shelf.
Bus extension (NT9X27)
The CM bus extension paddle board (NT9X27BA) extends the P-bus to the
SLM shelf from the CM processor shelf.
Power supply (NT9X30, NT9X47)
The power supply provides power for the SLM shelf. It consists of two
+5V 86-A power converters (NT9X30) and two +12V power converters
(NT9X47).

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–13

DIRP on the system load module

When configured with feature package NTXJ44AA, the SLM disks can also
be used by the device independent recording package (DIRP) as an
alternative to the I/O controller (IOC) for recording DMS subsystem data.
DIRP is a utility that manages the reading and writing of data among various
DMS subsystems and recording devices. Typical data handled by DIRP
includes operational measurements (OM) counts, automatic message
accounting (AMA) records, and journal files (JF).

Messaging component
The messaging component routes messages within the DMS-100 system,
including messages from the central control component (core processor) to
subtending nodes such as the switching network. The messaging component
in NT40-based systems is the central message controller (CMC). In
SuperNode-based systems, the messaging component is the DMS-Bus.
DMS-Bus
The DMS-bus is the messaging component of the DMS SuperNode system.
For reliability, the DMS-bus consists of two MSs. Under normal operating
conditions, the MSs share the load, although each MS can support the entire
system load if necessary. Figure 1–5 illustrates the main components of the
DMS-bus.

DMS-100 International Technical Specification BCS40i and up

1–14 System architecture

Figure 1–5xxx
DMS-bus components
FW30113

DMS-core

Port Processor
interface DMS-bus T-bus
interface
Transaction bus

Processor bus

Port Port System Mapper Control

interface interface clock processor
MC68020

I/O controller Network

The DMS-bus supports multiple application processors (AP), and allows

them to communicate with each other as well as with the DMS-core. This
capability permits the integration of network elements, such as the signaling
transfer point (STP) and the service control point (SCP). The high-speed
transaction bus (T-bus) acts as a hub for inter-processor communications.
The DMS-bus access ports can be configured as either DS30 copper
interfaces or DS512 fiber-optic interfaces. To ensure maximum reliability,
each MS is connected to each CM plane in the DMS-core by DS512 links.
Connectivity through DS30 links allows the DMS SuperNode switch to be
fully compatible with existing DMS-100 Family IOCs and network modules
(NM).
The DMS-bus also houses the system clock. The system clock is used by
both the DMS-bus and the DMS-core to perform general clocking and
timing functions. The office clock provides synchronization for the DMS
SuperNode switch. It can be used at a Stratum 3 level with the internal
clock, and with an external or remote clock source at the Stratum 1,
Stratum 2, and Stratum 2.5 levels.

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–15

The clock interface paddle board provides the direct analog interface
between the DMS-bus and external clock sources (Stratum 1), or remote
clock sources (Stratum 2 or 2.5). The DMS-bus system clock card provides
the internal Stratum 3 clock. Each office has two sets of clock cards, one in
each MS, that operate as internal master and slave sources.
Message switch
The MS is a hub for communication among DMS-100 components. The MS
concentrates and distributes messages in the DMS SuperNode system, and
allows other components to communicate directly with each other.
The MS provides the following capabilities:
• port-to-port message switching
• 240 000 messages per second with 64-byte message length
• independence among ports
• self-maintaining and self-diagnosing processor

Each MS is controlled by a Motorola 32-bit microprocessor. The

microprocessor card performs such functions as port maintenance,
diagnostics, and message communications. It communicates with other
functional areas in the MS through a 32-bit P-bus.
Inter-MS links provide additional reliability within the frame transport
system (FTS). If the route calculated by the FTS is unavailable—for
example, because one of the nodes selected is out of service—inter-MS links
direct the message by an alternative route, if one exists. Without inter-MS
links, the message is lost.
The DMS-bus can be configured with up to two inter-MS links, which can
be connected to any interface card in the MS shelf. Figure 1–6 shows this
configuration.

DMS-100 International Technical Specification BCS40i and up

1–16 System architecture

Figure 1–6xxx
Inter-MS links configuration
FW30325

MS 0 MS 1

Interface cards Inter-MS link 1 Interface cards

Inter-MS link 0

Functional subsystems of the message switch

The MS shelf is equipped with cards on the front and corresponding paddle
boards on the rear. The cards share a common bus with the paddle boards.
The MS consists of the following functional subsystems:
• processor and memory (NT9X13, NT9X14, NT9X26, NT9X52)
• system clock (NT9X53)
• mapper (NT9X15)
• port interface (NT9X17, NT9X20, NT9X23, NT9X62, NT9X69)
• bus terminator (NT9X49)
• power supply (NT9X30, NT9X31)

Processor and memory (NT9X13, NT9X14, NT9X26, NT9X52)

The processor and memory subsystem configures and maintains the other
MS systems. The subsystem consists of a CPU card (NT9X13), a memory
card (NT9X14), the RTIF paddle board (NT9X26), and the T-bus access
card (NT9X52).
The CPU card performs the processing and accesses the system bus through
the T-bus access card. The memory card provides storage for the CPU.
When the NT9X13DD CPU card is used, provisioning of a memory card on
the MS is optional, as the CPU card contains 16 Mbyte of dynamic random
access memory (DRAM). The RTIF paddle board monitors and decodes
commands and passes them to the CPU in the form of control signals. It

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–17

also monitors processor signals and relays them to the remote terminal or
remote scanning system.
Additional information on DMS SuperNode central processing units and
memory is provided on page 1–18.
System clock (NT9X53, NT9X54)
The system clock provides the clock source for the DMS SuperNode switch.
It consists of the MS system clock card (NT9X53) and the MS subsystem
clock paddle board (NT9X54).
The MS system clock card provides the internal Stratum 3 clock. The clock
interface paddle board provides the direct analog interface between the
DMS-bus and external clock sources (Stratum 1), or remote clock sources
(Stratum 2 or 2.5). Each office has two sets of clock cards, one in each MS,
that operate as internal master and slave sources.
For additional information on DMS SuperNode clocking configurations,
refer to the Transmission chapter of this document.
Mapper (NT9X15)
The mapper (NT9X15) performs logical-to-physical address translation for
messages routed between ports.
Port interface (NT9X17, NT9X20, NT9X23, NT9X62, NT9X69)
The port interface consists of the four-port DS30 paddle boards (NT9X23),
16-port DS30 paddle boards (NT9X69), the DS512 paddle boards
(NT9X20), subrate DS512 paddle boards (NT9X62BA), and the MS port
cards (NT9X17).
The four-port and 16-port DS30 paddle boards provide interfaces between
the MS and the junctored network, input output controller (IOC), and the
link peripheral processor (LPP). DS512 paddle boards use optical fiber to
link to ENET and the single shelf LPP (SSLPP). The DS512 paddle board is
the interface for a single DS512 link to the CM.
Bus termination (NT9X49)
The bus termination provides passive terminations to back panel signals. It
consists of the the MS P-bus terminator card (NT9X49CA or NT9X49CB)
that is used with ENET.
Power supply (NT9X30, NT9X31)
The power supply provides power for the MS shelf. The power is provided
by two NT9X30 +5V 80-A power converters, and two NT9X31 –5V 20-A
power converters. One of each type of power converter is located at each
end of the shelf, and provides power for one-half of the shelf.

DMS-100 International Technical Specification BCS40i and up

1–18 System architecture

The DMS-Bus consists of two fully duplicated message switches (MS)

which normally operate in load sharing mode. Either MS can assume the
full messaging load if required.
DMS SuperNode central processing units
The DMS SuperNode central processing unit is a 32-bit microprocessor with
a built-in instruction pre-fetcher and built-in instruction cache. The
instruction cache is a fast on-chip memory that stores the most
recently-executed instructions. The microprocessor is register oriented and
uses an instruction set especially defined for it. The CPU also includes a
Memory Access Unit (MAU) that provides the following functions:
• high-speed data cache to reduce processor-memory interaction
• memory access protection for up to 256 Mbytes of memory, in units of
64 kbytes (one page of memory)
• interface between CPU and memory
• parity checking

The instruction cache and data cache allow the CPU to maximize
throughput.
The CM and the MS use different versions of the NT9X13 CPU circuit card,
which differ only in the amount and type of memory provided. Both the CM
and the MS use the Support Operating System (SOS). Each has its own
CPU and which also uses additional software. Some software is used by the
CM and the MS and is common to both, while some software is unique and
is used only by one or the other. However, each maintains its own copy of
the SOS plus all other common software and its own unique software. Each
has its own clock for program-instruction sequencing and timing functions.
DMS SuperNode memory
DMS SuperNode memory consists of integrated program store and data
store on the same bus. There are separate data and address buses, each 32
bits wide. Memory is byte addressable; thus, the logical address range is 4
Gbytes.
Memory access protocol
Memory is partitioned into 64-kbyte pages. The function of each page of
memory is defined by memory protection attributes in the MAU. Four types
of memory protection attributes are provided in the DMS SuperNode:
• write protection
• program only
• data only
• supervisor mod

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–19

Combinations of these attributes determine the characteristics of each page

of memory as follows:
• Program store has the program only attribute. Write protection in
program store is implemented by means of a counter. Only the program
loader and some debugging tools modify program store.
• Protected data store has the data only and write protection attributes.
Write protection can be disabled temporarily for all of DSPROT.
• Data store or program store reserved for use by the support operating
system (SOS) has the supervisor mode attribute, in addition to its other
attributes.
• All other types of data store have the data only attribute.
• Unallocated memory has the combination of data only, program only and
write protection attributes.
Memory hardware
DMS SuperNode memory resides on three versions of the NT9X14 circuit
card, as follows:
• 6 Mbytes of dynamic random-access memory (DRAM), is divided into
three 2-Mbyte memory modules (NT9X14BB).
• 24 Mbytes of dynamic random-access memory (DRAM) is divided into
three 8-Mbyte memory modules (NT9X14DB).
• 96 Mbytes of dynamic random-access memory (DRAM) is divided into
three 32-Mbyte memory modules (NT9X14EA).
Memory is organized into 40-bit words: 32 data bits, seven error-correcting
code bits and one parity bit. Figure 1–7 illustrates the memory
configuration. The error-correcting code bits provided the capability to
correct single-bit errors and to detect multiple-bit errors. The error-detecting
and error-correcting capabilities are implemented in the memory controller
hardware.

DMS-100 International Technical Specification BCS40i and up

1–20 System architecture

Figure 1–7
Memory modules, pages and segments

Page Page 0 Page

1 Memory
64 64 Segment 64
. module
kbytes kbytes 4 kbytes kbytes
. 2 Mbytes
. ...
0 1 15 31

Memory
module
2 Mbytes

Page Page 0 Page

Memory
64 64 1 Segment 64
module
kbytes kbytes . 4 kbytes kbytes
. 2 Mbytes
. ...
0 1 15 31

Memory
module
2 Mbytes

Memory
module
2 Mbytes

Switching network
The switching network is a digital-switching matrix that interconnects the
peripheral modules, using time-division multiplexing. The switching
network planes are duplicated for reliability. On NT40-based systems, the
switching network used is the junctored network (JNET). The JNET is
made up of microprocessor-controlled, digital-switching network modules
(NM).
SuperNode-based systems can also be provisioned with JNET but are
typically equipped with the newer Enhanced Network (ENET). Both

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–21

network types cannot reside on the same system, however, SuperNode-based

systems currently equipped with JNET can be upgraded to ENET.
Junctored network
The junctored network (JNET) is connected to the messaging component via
DS-30 links. The JNET resides in the dual shelf network equipment (DSNE)
frame as shown in figure 1–8.
Figure 1–8
Layout of a DSNE frame
FW-30184

Network 00

Filler panel
Frame
supervisory
panel

Network 01

Filler panel

Cooling unit

DMS-100 International Technical Specification BCS40i and up

1–22 System architecture

The JNET switches pulse code modulation (PCM) signals using

time-division multiplexing. It performs the following tasks:
• establishes a DS-30 channel between incoming and outgoing ports under
command of the central control element (that is, connects two PMs via a
switched DS-30 link).
• provides signal processing (digital attenuation and gain) for PCM
signals.
• inserts outgoing control messages from the central control element into
the DS-30 message channels to the PMs.
• extracts incoming messages from the PM message links and forwards
them to the central control element.
The JNET consists of up to 32 network modules (NM). Each NM has up to
64 DS-30 incoming ports and 64 DS-30 outgoing ports. The incoming side
is termed the “peripheral side,” because this side connects to the PM links
(termed “speech links”). The outgoing side is termed the “junctor side,”
since this side is used to interconnect the NMs by way of speech links called
“junctors.” Thus, any NM peripheral-side port or channel may be connected
to any other NM peripheral-side port or channel, thus establishing a DS-30
channel connection. The JNET port configuration is illustrated in figure
1–9.
A NM consists of a time-division-multiplexed switching matrix controlled
by a network module controller (NMC). The NMC connects with the
messaging component by way of DS-30 links. The NM determines which
messages coming from the control component are switching network control
messages, and which are messages destined for the connected PMs. It takes
action on JNET control messages and forwards the PM control messages to
the PMs. Messages from PMs to the central control element are forwarded
via the central messaging element.

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–23

Figure 1–9
Junctored network port configuration

Junctor side Peripheral side

63 Port 63
* PM
.
.
.
* PM

* PM
0 Port 0
NM 31
.
.
.
63 Port 63
* PM
.
.
.
* PM

* PM
0 Port 0
NM 0

Network module controllers

Network module controllers (NMC) are duplicated and the mates are termed
plane 0 and plane 1. Figure 1–10 illustrates the duplicated network module
controllers. The NMCs operate in duplex mode. Each CMC (NT40) or
message switch (SuperNode) has two ports assigned to each NM: one for
messages assigned to plane 0 and one for messages assigned to plane 1.
JNET control messages are sent duplex from the central control element to
an NM. Thus both planes receive a connection message and both establish a
connection. Therefore, PMs connected through the JNET have a duplicated
path over which to communicate with the core processor.

DMS-100 International Technical Specification BCS40i and up

1–24 System architecture

Figure 1–10
Duplicated network module controller

Junctor Peripheral
side NM side

CMC or MS Plane 1
ports Side B
CMC 1
or *
MS 1
NMC

*
Side A

Plane 0
Side B

NMC
CMC 1
or
MS 1 *
Side A
Network Network
ports ports

Messages sent to PMs are sent simplex; each message traverses the
messaging component-to-NM links and the NM-to-PM message link, as
specified in the routing information carried in the message. If a message
link fails, the system automatically removes it from service, and reroutes
messaging through the remaining associated link.
Since a NM path is uni-directional, two paths are required to establish a
bi-directional channel. Thus, there are two “sides” to a plane designated as
Side A and B. Side A switches PCM signals from the peripheral side to the

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–25

junctor side, while Side B switches PCM signals from the junctor side to the
peripheral side.
The junctors are DS-30 links providing NM interconnection and
intra-connection. Junctors carry 31 channels of speech, with one channel
(channel 0) used for switching network DS-30 synchronization.
The designated grade-of-service (probability of blocking) of the switching
network is achieved with traffic offered by 30 channels of DS-30 at the
speech links. Thus, two channels of a speech link (channels 0 and 16) are
available for other purposes. Channel 0 is made available for messaging and
channel 16 for maintenance features. Channel 16 is also used by
inter-peripheral message links (IPML).
Intra-network connection
Two PMs on the same NM are intra-connected by a single junctor. The PMs
have one (duplicated) link connected to both planes of the NM. In this case,
the link carries both speech and messaging. As shown in figure 1–11, the
two PMs are connected via the Switching Network. Note that the illustrated
connection represents both space and time since a link/channel on one PM is
connected to a different link/channel on the other. In this case, only one
Physical junctor is necessary since it can carry up to 31 channels. PCM
signals from each PM are carried on the single junctor, but in different
time-slots (channels).
Inter-network connection
The inter-network configuration is illustrated in figure 1–12 on page 1–27.

DMS-100 International Technical Specification BCS40i and up

1–26 System architecture

Figure 1–11
Intra-network connection (JNET)

Junctor Peripheral
side NM side

Plane 0

PMY
*

Side B
NMC
Side A

*
Phone

Plane 1

* PMX
Side B
NMC
Side A

Phone

Network Network
port port

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–27

Figure 1–12
Inter-network connection (JNET)

Junctor Peripheral
side side

NM 1

Plane 0
*
Side A
NMC
Side B
*
Plane 0 PMY

*
Side A
NMC
Side B
*

NM 0

Plane 0
*
Side A
NMC
Side B
*
PMX
Plane 0

*
Side A
NMC
Side B
*

DMS-100 International Technical Specification BCS40i and up

1–28 System architecture

Enhanced network
ENET is a matrixed timeswitch that provides pulse-code modulated voice
and data connections between PMs, and message paths to the DMS-bus.
ENET is available in either a single-cabinet 64K configuration or a
dual-cabinet 128K configuration. Both configurations use the same
hardware components, and the 64K ENET can be upgraded to 128K
channels.
ENET provides the following capabilities:
• non blocking single-stage switching
• nailed-up connections with no adverse effect on traffic
• compatibility with A-law and µ-law companding

Figure 1–13 on page 1–29 illustrates the basic 64K single-cabinet ENET
layout, with two shelves for each plane.
Figure 1–14 on page 1–30 illustrates a typical 128K dual-cabinet ENET
layout, with one fully equipped cabinet serving as plane 0 and one fully
equipped cabinet serving as plane 1. Up to 60 speech link interface cards
are provided for each plane.

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–29

Figure 1–13xxx
64K single-cabinet ENET layout
FW-30502

FSP

Shelf 0

Plane 0

Shelf 1

Shelf
0
Plane 1

Shelf 1

Cabinet cooling unit

DMS-100 International Technical Specification BCS40i and up

1–30 System architecture

Figure 1–14xxx
128K dual-cabinet ENET layout

FSP FSP

ENET Plane 0 ENET Plane 1

Shelf 0 Shelf 0

Shelf 1 Shelf 1

Shelf 2 Shelf 2

Shelf 3 Shelf 3

Cabinet Cabinet
cooling unit cooling unit

Note: For ENET applications with more than two shelves in each ENET
cabinet, the use of ISN cabling structure (ICS) cabinets (NT0X35BB) is
recommended. Three ICS cabinets (not shown) are required for the
example shown in figure 1–14: one on either side of the ENET cabinets
and one between them.

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–31

Functional subsystems of ENET

ENET consists of the following functional subsystems:
• processor and memory (NT9X13, NT9X26)
• clock and messaging (NT9X36, NT9X40)
• crosspoint (NT9X35)
• transmission and interface (NT9X40, NT9X41)
• power supply (NT9X30, NT9X31)

Processor and memory (NT9X13, NT9X26)

The processor and memory subsystem provides operational and diagnostic
control for the shelf. The subsystem consists of the CPU card (NT9X13)
and the RTIF paddle board (NT9X26). The CPU card holds 4 Mbyte of
DRAM, which holds the operating software for the ENET, and 128K of
read-only memory (ROM) firmware, which holds bootloading and
initialization procedures. Auxiliary operational and maintenance control is
available through the RTIF paddle board.
Clock and messaging (NT9X36, NT9X40)
The clock and messaging subsystem consists of the clock and message card
(NT9X36), and a four-port DS512 fiber interface paddle board (NT9X40).
The clock and message card provides I/O control and the clock source for
the shelf. The interface paddle board provides two channelized fiber links to
the DMS-bus for messaging. The shelf processor and the PMs connected to
the shelf share the messaging on the links. One of the links, as specified by
the DMS-bus and the shelf processor, also provides the clock source for
synchronization with the DMS-bus.
Crosspoint (NT9X35BA, NT9X35CA)
The crosspoint subsystem consists of NT9X35BA and NT9X35CA cards,
which form the switching matrix. The crosspoint cards are connected to the
other cards on the shelf by the horizontal bus (H-bus) and to the cards on
other shelves by the vertical bus (V-bus). The NT9X35CA also provides
matrix switching functions and terminates the H-bus that connects all the
cards on the shelf.
Transmission and interface (NT9X40, NT9X41)
The transmission and interface subsystem consists of either DS512 fiber
interface paddle boards (NT9X40), or DS30 interface paddle boards
(NT9X41), or any combination of the two. These paddle boards are the
transmit and receive interfaces between the PMs and the crosspoint cards in
the ENET.
Series I PMs connect to the ENET through the existing copper speech links.
Retrofit kits are required to allow Series I PMs (except for the trunk module
(TM) and maintenance trunk module (MTM)) to connect to ENET.

DMS-100 International Technical Specification BCS40i and up

1–32 System architecture

Series II PMs connect to ENET using DS512 fiber links. Retrofit kits are
required to allow Series II PMs to connect to ENET. Series II PMs message
switch and buffer 6 (MSB6), MSB7, digital trunk controller 6 (DTC6), and
Subscriber Carrier Module–100S (SMS) use copper speech links to connect
to ENET.
Figure 1–15 on page 1–32 shows an example of how an ENET can be
connected to a Series II PM using fiber links.
Figure 1–15xxx
Example of an ENET connected to a Series II PM
FW-30146

NT9X35 ENET ENET NT9X35

Paddle board Paddle board

DS512 link DS512 link

NT9X40BA NT9X40BA

Fiber link Fiber link

NT6X40* NT6X40*
paddle board paddle board

NT6X40** NT6X40**
PM (for example, DTC)

*Note 1: Provision either an NT6X40DA or an NT6X40GA paddle board.

**Note 2: Provision either an NT6X40CA or an NT6X40FA card.

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–33

Power supply (NT9X30, NT9X31)

The power supply provides power for an ENET shelf. The power is
provided by two NT9X30 +5V 80-A power converters, and two NT9X31
–5V 20-A power converters. One of each type of power converter is located
at each end of the shelf, and provides power for one-half of the shelf.
ENET has the Power Interlock feature. This feature is designed as a
safeguard; it prevents the system from being powered off inadvertently
while in service. Under all other conditions, the Power-Interlock feature is
disabled.

Input/output controller
The input/output controller (IOC) provides an interface between the
messaging component and input/output devices such as magnetic-tape
drives, disk drives, data links, MAPs, and printers. The IOC is used on
NT40-based and SuperNode-based platforms. Up to 36 devices can be
connected to an IOC shelf. A DMS system can support up to 12 IOC
shelves.
The IOC, together with the I/O device controller that connects the particular
device, perform the necessary conversion to DS-30 format for
communication with the control component by way of the message links.
Two DS-30 links connect to the IOC, one from each message component.
Figure 1–16 on page 1–36 illustrates the IOC and the input devices which
connect to it. The IOC resides in a single or dual input output equipment
(IOE) frame. The single IOE frame is illustrated in figure 1–17 on page
1–37.
Input output devices
The following types of input output devices connect to the DMS system via
the input output controller.
Magnetic tape drives
Magnetic tape drives (MTDs) are devices that allow transfer of system data
to permanent memory tape that is external and transportable. The MTD is
used for storage and retrieval of DMS data as follows:
• office image data (backup)
• automatic message accounting (AMA) data (record of billing)
• journal file (JF) data (record of data modification)
• operational measurements (OM) data (traffic reports)

Magnetic tape drives are described in further detail in chapter 7,

“Administration”.

DMS-100 International Technical Specification BCS40i and up

1–34 System architecture

Disk drive units

Disk drive units (DDUs) are used to store data. They are not used to transfer
data to tape or to any other medium. The disk drive unit has greater storage
capacity and quicker accessibility than an MTD.
Disk drive units are described in further detail in chapter 7,
“Administration”.
Maintenance and administration position (MAP)
The MAP terminal provides a user interface to the IODs. It is used to do the
following operations:
• enter machine controls
• run tests
• request information
• produce system-generated messages
• perform maintenance procedures

The MAP is described in further detail in chapter 10, “Maintenance”.

IOC common cards
The IOC is always provisioned with the following three cards.
I/O message processor card (NT1X62)
The I/O message processor card contains a microprocessor capable of
connecting serial message links to the MS, and a parallel data bus to the
individual device controller cards. This card controls the overall operation
of the IOC.
I/O terminator card (NT0X67)
The I/O terminator card provides resistive termination for the IOC parallel
data bus.
Power converter card (NT2X70)
The power converter card supplies the necessary shelf voltages for all circuit
cards in the IOC shelf.
IOC device controller cards
Magnetic tape controller card (NT1X68)
The magnetic tape controller card provides an interface for one MTD.
DIsk drive controller card (NT1X55)
The disk drive controller card provides an interface for one DDU.
Terminal controller card (NT1X67)
The terminal controller card provides an interface for any combination of
four MAPs, printers (read-only or send-receive), or modems.

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–35

Multiprotocol controller card (NT1X89)

The multiprotocol controller (MPC) card allows data communication
between a DMS-100 Family system and an external computer (for example,
between a central office billing computer and the DMS-100 switch. Each
IOC can support up to nine MPC cards. The MPC card protocol software is
downloaded from the DMS-100 CPU and supports software routines for
Data Packet Network (DPN) communications. Remote MAPs can also be
connected to the system via the MPC.
The MPC interfaces to data communications equipment (modems or
datasets) using asynchronous, X.25, or BX.25 protocols. MPC links can
transmit data using RS232 at a maximum rate of 19.2 kbits/second. The
NT1X89 Enhanced MPC also provides a 56/64 kbits/second V.35 link.
Multiprotocol controller applications, hardware, and software are described
in detail in the Multiprotocol Product Guide, 297-1001-015.

DMS-100 International Technical Specification BCS40i and up

1–36 System architecture

Figure 1–16
Input/output device configuration

Computing
module

Message
switch

To switching network

Input/output controller

Card 0 Card 8 Card 0 Card 8

MTC TC DDC TC

Mag Disk
drive Modem
tape
VDU
Prtr
VDU VDU VDU

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–37

Figure 1–17xxx
Input/output equipment frame layout

Magnetic
tape drive

Frame
supervisory
panel

Input/output
controller

Input/output
controller

Disk drive
unit

Peripheral modules
Peripheral modules (PM) provide an interface between the DMS internal
switching network and the telephony network (lines and trunks).
A digital connection can be established among PMs under the direction of
the control component. Once connected, the PMs can pass voice/data and
pulse code modulation (PCM) signals among themselves.

DMS-100 International Technical Specification BCS40i and up

1–38 System architecture

Hardware and functional modularity are most evident at the PM level of the
system. The PMs connect both analog lines and digital voice and signaling
transmission systems. PMs provide the signal processing required to
convert data to a common digital format for transmission to another PM
connected via the switching network. The destination PM reconverts the
common format to the one required by the facility with which it connects.
The conversions involved are:
• analog-to-digital (A/D), for conversion of voice-frequency analog
signals to internal digital signals.
• digital-to-analog (D/A), for conversion of internal digital signals to
analog voice frequency signals.
• digital-to-digital (D/D), for conversion from internal to external formats
on digital facilities (for example, DS30 to PCM30)
Digital trunk facilities link DMS-100 International systems to other
switching systems in the telephone network. The system, through its digital
switching network, connects lines and incoming digital trunks to lines and
outgoing digital trunks located on the peripheral modules and utilizes
conventional signaling formats including multifrequency (MF),
multifrequency compelled (MFC), and dual tone multifrequency (DTMF).
Channel banks can be used to interface DMS-100 International switches to
the network via analog trunks.
In addition to signal processing, the PMs also perform many of the common
and real time consuming functions associated supervision and control of
external interfaces. For example, line modules perform line supervision,
digit reception and ringing functions. As a result, the control component
needs only to determine call destination when all digits are received and to
establish a call connection through the switching network.
Peripheral modules (PM) perform the following tasks:
• connect analog and digital facilities for conversion of data and signaling
to and from internal DS30 format. (see Note)
• transmit DS30 pulse code modulation (PCM) signals and data to other
PMs via the switching network.
• provide additional signal processing through the use of service circuits
such as dual-tone multifrequency (DTMF) receivers.
• provide maintenance and performance analysis circuitry for frequency
and level measurements
• provide facilities for subscriber and terminal signaling, such as busy
tone, dial tone, multifrequency digit outpulsing tones, and ringing
current

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–39

Note: The DMS-100 International switch only supports direct

connection of digital PCM30 trunks. Analog trunks can be connected
using an appropriate channel bank.

The connections through the switching network are duplicated. At least one
(duplicated) DS30 link is provided.
Note: A duplicated link means that there are two links, one to each
switching network plane. Speech and signaling information is sent over
both links, but only one link is active. If a fault occurs on the active link,
the other link takes over.

How peripheral modules function in the network

Most PM types can be connected to the switching network with more than
one (duplicated) link—up to a maximum of 16. The number of links
depends on the volume of traffic to the switching network; the volume of
traffic the unit offers depends on the number of terminals that the unit
controls and on the traffic offered by each terminal.
For PMs that control subscriber line circuits, concentration occurs between
terminals and links to the switching network. This is the case because line
traffic is low (typically four hundred call seconds or 4 CCS), whereas a
DS-30 link channel can carry 36 CCS. Concentration at the LCM/LGC
makes efficient use of link traffic capacities. The concentration is
implemented by a time-division-multiplexed switching matrix. Trunk PMs
(for example, digital trunk controllers) have no concentration since trunks
operate at a high-traffic level (up to 36 CCS).
Prior to sending a switching network connection control message, the central
control component informs each PM of the integrity value to be sent to the
other PM to be received from the other PM. These values can be different.
The control component selects integrity values on a per-connection basis.
Therefore, each connection gets a different integrity value (by cycling
through the existing 256 values, some of which are not allowed). Since
there are delays in the completion of the various functions on call
connection, the integrity byte allows each PM to verify that a connection has
been established before proceeding with its call processing function.
The integrity digit is checked to ensure that a connection continues to exist
for the duration of the call. Since a large amount of PM hardware and
software is involved in the transmission of the integrity byte, the functioning
of the PM is verified with integrity value continuity. In addition, since each
call connection is assigned a different integrity value, software error
occurring in the switching network path selection, which overwrites an
existing connection, will be detected through a change in integrity value.

DMS-100 International Technical Specification BCS40i and up

1–40 System architecture

Since the switching network connection provides a duplicate path (plane 0

and plane 1), the core processor also tells the PMs which plane is the
“preferred plane.” PMs transmit over both planes. However, they accept
only PCM signals from the preferred plane, but this is different for each call
(that is for each connection).
Since the switching network operates in “duplex” mode, that PMs have
access to a duplicated link and a duplicated switching network plane. Upon
loss of integrity or parity, a PM switches activity to the mate link and
attempts to reestablish integrity with the other PM. A link or switching
network hardware fault is recoverable since a duplicated path is available;
therefore, there is no loss of connection. Loss of connection can be caused
by logic errors or by PM hardware failures.
Control messages are carried over channel 0 on one (duplicated) speech link
only. This link is commonly termed the message link. If a PM has more
than one duplicated speech link to the switching network, this channel is
unused on the remaining speech links. The control component sends and
receives PM messages by the way of the message channel. The 8-bit
speech/data portion provides a 64-kb/s channel. Bit 1 is not used since the
messaged protocol detects messaged errors by checksum or cyclic
redundancy check (CRC) coded comparison. Bit 0 is used for DS-30 frame
synchronization.
Successive outgoing messages from the control component to the PMs use
alternate routes, therefore, outgoing messaging are distributed over the
routes. This mode of operation ensures equitable distribution of the message
traffic load over all elements of the input/output (I/O) System.
Incoming messages from the PMs are sent over the “preferred route”
message link. The control component ensures that each PM has a preferred
route in order to guarantee that the incoming message load is distributed
over the I/O system.
The following PMs are used in DMS-100 International switching systems:
• International line concentrating module (ILCM)
• International line group controller (ILGC)
• International digital trunk controller (IDTC)
• maintenance trunk module (MTM)
• office alarm unit (OAU)
• link peripheral processor (LPP)

International line concentrating module (ILCM)

The ILCM supports analog lines and provides low-level functions, such as:
• line scanning

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–41

• ringing
• digit collection
• line metering (with type B line card)
A maximum of 640 lines can be connected to each LCM. Each LCM
consists of two shelves. (Line Concentrating Arrays). Each shelf consists of
a power converter, a controller, and a maximum of five line drawers. Each
line drawer contains up to 64 line cards. Up to 320 lines can be connected to
each shelf. The ILCM configuration is shown in figure 1–18 on page 1–41,
and figure 1–19 on page 1–42.
Figure 1–18xxx
ILCM shelf organization
FW-31146

Shelf 1
Power converter 1

Up to 3 Up to
Controller 1

DS30A links Up to 5 line drawers 320 lines

Shelf 0
Power converter 0

Up to 3 Up to
Up to 5 line drawers
Control 0

DS30A links 320 lines

DMS-100 International Technical Specification BCS40i and up

1–42 System architecture

Figure 1–19xxx
ILCM frame packaging
FW-31145

Ringing Ringing
generator 0 generator 1

Power converter 0
320 lines
DS30A
Controller Line drawers 640 lines
Power converter 0

320 lines ILCM 0

DS30A
Controller 0

Line drawers
Power converter 0

320 lines
DS30A
Controller 0

Line drawers 640 lines

Power converter 0

320 lines ILCM 1

DS30A
Controller 0

Line drawers

For reliability, each shelf is capable of taking over the lines of the mate
shelf, as shown in figure 1–20 on page 1–43.

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–43

Figure 1–20xxx
Duplication within the ILCM
FW-31148

Controller 0 Up to 5
Up to 3 line drawers Up to
DS30A links 320 lines
* *

1 or 2
RS-232
speech links
link
(DS30A)

Controller 1 Up to 5
Up to 3 * * line drawers Up to
DS30A links 320 lines

Note: *Used only if the mate controller fails.

The controllers are connected by a serial link which allows one shelf to
check its data with the mate controller. The data for each call in progress is
sent to the mate controller over this link. If a fault occurs in one controller,
the mate controller can take over the calls in progress. Each line drawer has
duplicated links connecting it to both controllers, and each DS30A link is
connected to both controllers as well. Therefore, if a controller fails, the
hardware signals the mate controller, which then takes over the remaining
320 lines. There is no reduction in the number of links between the line
drawers and the controller, or between the ILGC and the ILCM, because the
controller has access to the failed controller’s line drawers and DS30A links.
Between the two controllers, there are two speech links (DS30A). If all
DS30A links on a controller are busy, but the mate controller has a free
DS30A link, a call originating on the controller with all links busy may be
routed between the links to the free DS30A channel on the mate controller.
This capability provides access for all lines to all six links, for traffic
engineering purposes.
Each ILCM has its own ringing generator. In the event of a failure, the mate
ILCM will supply the ringing voltage for both ILCMs.
In the event of a power failure, the converter on the mate shelf takes over
and provides power for both shelves.
A group of ILCMs connects to a ILGC, which then connects to the
switching network.

DMS-100 International Technical Specification BCS40i and up

1–44 System architecture

There is at least one DS30A link per shelf between the ILCM and the ILGC.
Each ILCM has at least two DS30A links to the ILGC controlling it. The
maximum number of DS30A links per shelf is three (that is, a maximum of
six DS30A links per ILCM).
The following circuit cards are provisioned on an ILCM.
Power converters (NT6X53)
The ILCM power converters supply all the required LCA shelf voltages and
operate using a nominal –48V dc battery source.
ILCM processor card (NT6X51AB)
This card provides:
• interface to digroup control card
• activity and sanity circuitry
• digit collection and messaging for up to 640 lines (spared mode)
• DMS-X message protocol to the ILGC
• monitoring of power and ringing functions
• clock recovery and generation
• 64K RAM

Digroup control card (NT6X52AB)

The digroup control card provides:
• interface to three DS30A links
• interface to ten line drawers (control/signaling/PCM) time
• time switching functions for external and internal channel assignment
• digital loop around paths

Bus interface card (NT6X54AB)

The bus interface card provides:
• interface to two 32–channel digroups
• interface to 64 line cards (single line circuit per card)
• reference voltage for CODEC/filters
• scanning of lines for switch hook change or message presence
• line drawer activity
• digital loop around
• ring multiplexer for selecting ringing

Ringing generator (NT6X30)

Two programmable ringing generators are supplied in each line
concentrating equipment (LCE) frame. In the event of a ringing generator
failure, the remaining generator provides the ringing voltage for both LCMs.

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–45

Type A line card (NT6X93, NT6X17)

The type A line card supports:
• single party
• PBX – loop start

Type B line card (NT6X94, NT6X18)

The type B line card supports all features of type A, plus:
• coin boxes (single-coin and multi-coin) controlled by meter pulses
• subscriber premises metering pulses
• PBX – loop start, requiring meter pulses

World line card

The DMS-100 International switch can be provisioned with world line cards
(WLC), which employ programmable software templates to meet the
subscriber line characteristics, (for example, impedance requirements) of
specific operating companies. Type A (NT6X17BA) and type B
(NT6X18BA) WLCs are available. The templates are programmed by
Northern Telecom based on specifications supplied by the operating
company.
The WLC can be programmed with the following characteristics:
• transmit gain
• receive gain
• PCM coding law (A-law or µ-law companding)
• balance impedance
• input impedance
• bit inversion selection
• metering tone frequency
• metering tone duration
• metertone test disable/enable
• equalization loss enable/disable
• current limit selection
• supervision threshold selection
• supervision configuration selection
• North American balance impedance selection
• North American default balance selection

Line drawer (NT6X05AA)

Each pull-out drawer contains a motherboard with space for one bus
interface card and up to 64 individual line cards. The inherent system
modularity and feature adaptability allows each line drawer to accommodate

DMS-100 International Technical Specification BCS40i and up

1–46 System architecture

any mix of the available types of line cards, and allows additional plug-in
units to be added to a partially-equipped module without disruption of
service.
International line group controller (ILGC)
The ILGC performs high-level functions, such as:
• call coordination
• provision of the different tones required
• ILCM interface.

Up to ten ILCMs can be connected to each ILGC, depending on traffic

requirements. Each ILCM can have two to six connections (links) to the
ILGC, although the ILGC can have a maximum of 20 ports. The ILGC can
have 3 to 16 links to the network, as illustrated in figure 1–21.
Figure 1–21xxx
Network – ILGC – ILCM Connections
FW-31147

Network Maximum of 16 network planes

module

3 to 16 DS30 links

ILGC

2 to 6 DS30A links per ILCM

ILCM ILCM Up to 10 ILCMs per ILGC

Up to 640 Up to 640
lines per ILCM lines per ILCM

The ILGC functional diagram is shown in figure 1–22 on page 1–48. The
link between an ILCM and its host ILGC is DS30A. The link between each
ILGC and a network module is a DS30 link. DS30A is similar to DS30.
Some hardware economies are achieved, since DS30A is intended to work
over shorter distances (Line Concentrating Modules are adjacent to their
Line Group Controller).

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–47

There is usually some concentration of lines, depending on the engineering

of the office. The concentration may occur in two places: in the ILCM or in
the ILGC.
Each ILGC has a maximum of ten ILCMs and, therefore, a maximum of
6400 (10 x 640) lines. The ILGC has a maximum of 20 ports available on
the ILGC for DS30A links from the ILCMs and, therefore, also has a
maximum of 600 (20 x 30) speech links from the ILCMs. The DS30A ports
have a maximum range of 50 feet between the ILGC and the ILCM. All the
ports from an ILCM must terminate on a single ILGC. Messaging between
the ILGC and its ILCMs and remotes is accomplished using DMS-X
protocol.
The ILGC interfaces to the DMS-100 network using from 90 to 480 speech
links provided by 3 to 16 DS30 ports spread across up to 16 network
modules. Communications to the network module is accomplished via four
message channels (two for each controller shelf in the ILGC), using DS30
protocol supported by the DMS-100 network. Channel 0 on each of the two
network port pairs is used for the message channel. Signaling integrity is
maintained by duplication of these ports for each network plane (planes 0
and 1) and by switching over to the mate shelf if an active controller loses
both planes of the message channel.
There are up to 480 (16 x 30) speech links between the network module and
the ILGC.
Concentration can be reduced by reducing either the number of ILCMs or
the number of lines per ILCM.
The ILGC is divided into two units. Each unit occupies one shelf and
contains a controller, a power converter, DS30 interface cards, and DS30A
interface cards. Duplication within the ILGC is illustrated in figure 1–22.

DMS-100 International Technical Specification BCS40i and up

1–48 System architecture

Figure 1–22xxx
Organization within the ILGC
FW-31144

To plane 0 of network To ILCMs

DS30 Control DS30A

interface complex 0 interface
card * * card

To plane 1 of network To ILCMs

DS30 Control DS30A

interface * complex 1 * interface
card card

Note: *Used only if the mate controller fails.

For reliability, one controller is active and the other controller is in standby
mode. There is a 19.2 kbits/sec link between the two units. This link is used
to transfer information from the active unit to the standby unit. This transfer
ensures that the standby unit has enough data to continue operation if the
active unit fails. The active unit checkpoints data from each call to the
standby unit. If a fault hardware or software fault occurs, the active
controller becomes inactive and the standby controller assumes control of
the ILGC.
Calls in talking state are preserved during both takeover and return to
service. Calls in the set-up mode are lost.
A switch-over occurs if any of the following fail:
• power converter
• control complex (MP, SP, FP, and memory)
• time switch
• CSM card
• formatter
• message interface
• A/B interface

The switch-over takes place if the fault occurs on the active controller.
These faults are detected by the routine use of the channel loop-around to
the above cards.

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–49

In the event of a power converter failure, the converter on the mate shelf
takes over and supplies power to the non-duplicated PCM30+2 interfaces on
both shelves.
The ILGC is the basic peripheral group controller. The International Digital
Trunk Controller (IDTC) is a derivative of the ILGC.
The following circuit cards are used in the ILGC.
Power converter (NT2X70AD)
The power converter provides all the required shelf voltages and operates on
a nominal –48V dc battery. The converter is capable of supplying power for
the non-duplicated DS-1 interface of the mate shelf in the event of a mate
converter failure. This power converter is also used in the IDTC.
Universal tone receiver (NT6X92)
The universal tone receiver (UTR) is a 32-channel receiver which can detect
a variety of tones, such as DTMF, MF, and MFC. Up to 128 frequencies can
be detected by programming two EPROMS on the card.
Tone samples are switched onto the parallel speech bus by the time switch
(NT6X44AA) and are collected by the UTR at the appropriate time slots.
The UTR analyzes the samples and identifies the tones. The results are
returned to the signaling processor (SP).
DS30 interface (NT6X40AB)
Each DS30 interface card contains the interface logic for eight DS30 ports
(single plane). This card also contains the network side loop-around logic
used for maintenance purposes. This card is also used in the IDTC.
Speech bus formatter (NT6X41AA)
The speech bus formatter card contains the logic required to combine both
network planes. The necessary control memory for the network side loop
around is located on this card as well as the logic associated with the ILGC
system clock. A per-channel channel supervision message (CSM)
loop-around facility is also supported on this card. This card also converts
the 512 channel speech bus to 16 32-channel serial ports and vice-versa.
This circuit card is also used in the IDTC.
Channel supervision message (NT6X42AA)
The channel supervision message card contains the required logic for
channel supervision message (CSM) extraction and insertion, parity and
integrity. This circuit card is also used in the IDTC.
Time switch (NT6X44AA)
The time switch card contains the ILGC switching logic, peripheral side
serial to parallel and parallel to serial converters, and peripheral side
loop-around logic. The time switch enables any network side channel to

DMS-100 International Technical Specification BCS40i and up

1–50 System architecture

connect to any peripheral side channel. This circuit card is also used in the
IDTC.
Message interface (NT6X69)
The message interface card contains the interface to both network and
peripheral side message channels. The card also contains the tone
generation logic.
Processor (NT6X45)
Two versions of IDTC processors are available. The newer version, the
NTMX77 unified processor card, is described on page 1–51. In the older
processor configuration, each ILGC unit contains two NT6X45 processor
cards, based on Motorola 68000 microprocessors. One card is configured as
the master processor (MP) and the other is configured as the signaling
processor (SP).
The MP performs the following functions:
• call control
• data management
• interpretation of central control messages
• channel assignment.

The SP provides the processing required to support real-time critical

functions, such as:
• A/B bit scanning
• signaling interpretation
• CSM reception and transmission.

Master processor memory (NT6X47AB)

IDTCs equipped with NT6X45 processors contain two master processor
memory cards in each unit. The master processor memory card contains 2M
bytes of RAM memory required by the master processor card. This circuit
card is also used in the IDTC.
Signaling processor memory (NT6X46AB)
IDTCs equipped with NT6X45 processors contain one signaling processor
memory card in each unit. The SP memory card contains 512K bytes of
RAM memory and direct memory access (DMA) interface required to
permit the SP and MP to communicate with each other. This card is also
used in the IDTC.
DS30A interface card (NT6X48AA)
This card interfaces to 10 DS30A ports from ILCMs.

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–51

Unified processor (NTMX77)

The NTMX77 unified processor card replaces the NT6X45 master processor
card, the NT6X45 signaling processor card, the NT6X47 master processor
memory cards, and the NT6X46 signaling processor memory card. The
NTMX77 card is based on the Motorola 68020 processor, and in addition to
replacing five circuit cards with a single card, increases realtime capacity
and processor memory, and reduces power consumption.
International digital trunk controller (IDTC)
The IDTC supports PCM30+2 digital carrier facilities used for inter-office
trunking.
The IDTC uses the same hardware as the ILGC with the exception that it has
PCM30+2 interface cards instead of DS30A interface cards. The PCM30+2
interface cards are used to support digital trunks used for inter-office
trunking. There are 16 ports available on the DTC for PCM30+2 links.
In addition, a third universal tone receiver (UTR) card – NT6X92CB – may
be added on an IDTC+ frame to provide an additional 30 receiver channels.
PCM30+2 interface card (NT6X27AA)
This card provides the interface between DMS-100 International Family
systems and other digital switches in the network, using PCM30+2 protocol.
Maintenance trunk module (MTM)
The Maintenance Trunk Module provides the interface between the
32-channel, 2.56 Mb/s links to the switching network and a variety of analog
and digital test trunks, service circuits and alarm circuits. The MTM
contains four common control cards and a variety of interchangeable trunk
and service cards. These cards can contain analog or digital service circuits,
transmission test trunks, alarm detection or activation circuits or signaling
information circuits.
The four common control cards in the MTM are:
Trunk module/network interface card (NT2X45)
This card contains two, two-way interface circuits between the two
transmission paths from each network plane (planes 0 and 1) and the MTM.
It contains message registers, bit and channel timing, parity checking, and
data reformatting circuitry.
MTM control card (NT2X53)
This card contains three controllers that handle trunk, network, and integrity
messages. It communicates with the processor and memory card using data
and address buses. It provides 30 enable signals to the individual trunk
interface circuits.

DMS-100 International Technical Specification BCS40i and up

1–52 System architecture

MTM processor and memory card (NT0X70)

This card contains a microprocessor driven by ROM firmware, and two
RAMs: one for program storage and the other for operational use. The
latter contains connection information concerning PCM channel-to-trunk
associations. This card also performs clock generation, parity checking, and
synchronization.
CODEC and tone card (NT2X59)
The coder/decoder (CODEC) circuit encodes analog samples into PCM code
words and decodes PCM words into pulse amplitude modulation analog
samples. The tone circuit consists of a ROM where tones for dialing and
signaling are stored in digital form.
The following cards are also provisioned in an MTM:
Power converter cards (NT2X06, NT2X09)
These cards convert –48V office battery to lower voltage feeds required by
card circuitry. The MTM is equipped with two power converters: one
supplies 5 V at 40 A for all the digital circuits in a fully-equipped MTM, and
the other provides the various voltages required by equipment such as trunk
logic circuits and CODEC.
Test trunk or service circuit cards
These cards contain one or more trunk logic circuits that provide a
communication buffer between the transmit data and receive data buses, and
the test trunk, test access, or service circuit cards. These cards vary
considerably from one to another depending on the purpose of the card.
Cards are selected to interface with analog trunks, signaling, test, service or
alarm circuits. A typical test trunk card is the transmission test trunk (TTT).
A typical service circuit is the MF receiver. The shelves can be equipped
with a mixture of digital circuits or analog trunks or both. The relationship
between appearances and the shelf backplane imposes some restrictions on
the use of card positions. Card positions are allocated during office
engineering and provisioning.
6-port conference circuit
The 6-port conference circuit is a single-card service circuit with the
following functional characteristics:
• all digital (PCM in, PCM out)
• 0dB loss from selected first speaker to other
• conferees
• 0dB loss from selected second speaker to first
• speaker
• fast speaker recognition
• gradual insertion of loss on speaker change

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–53

• 0dB loss conference for more than 6 conferees for tandeming

Metallic test unit (MTU)
The MTU controller (NT4X97AA) and its mate card, the MTU analog card
(NT4X98AA) make up the MTU. The MTU is an advanced
processor-controlled test head used for making measurements of loop and
line card parameters via the MTA (metallic test access) mini-bar and the
line-card test access bus. The parameters that can be measured include:
• dc voltage
• ac voltage
• dc current
• ac current
• resistance
• capacitance
• frequency
• metering pulse parameters

All MTU applications software is downloadable, allowing for the addition of

new test capabilities without costly firmware retrofits.
The MTU and the central control processor communicate via the MTM
controller. Each virtual MTU has its own pair of trunk message channels for
receiving commands from the central control processor and sending back
replies.
The MTU analog card (NT4X98AA) is a single-board, double subscriber
line test head. The test head can apply stimulus levels to both tip and ring
under direction of the MTU controller card (NT4X97AA). The voltage
range is –100V dc to +100V dc. A signal conditioning circuit converts the
TIP and RING current flows into proportional voltages that are then used to
drive voltage controlled oscillators. The outputs of these oscillators are
monitored by the MTU controller to provide digital tip and ring current
information.

DMS-100 International Technical Specification BCS40i and up

1–54 System architecture

Signaling and interfaces between switching subsystems

Communication between DMS-Core and DMS-Bus
These hardware components are interconnected by fully duplicated DS-512
links referred to as CMIC Links, as shown in figure 1–23.
Figure 1–23
CM and MS signaling paths

DMS-Core computing module

Mate exchange bus
CPU 0 CPU 1

MC MC
Port crossover
bus

CMIC CMIC
links links

MS0 MS1

DMS-Bus

This technique not only results in true redundancy of these two entities but
also makes possible in the sharing of connections between themselves. Each
CPU has a serial fiber optic connection (CMIC link) to each MS. The two
CM planes are connected by the mate exchange bus, which in turn makes
possible a secondary connection between MCs using the port crossover bus.
This ensures complete redundancy for the CM connections.
Communication between switching core and subtending subsystems
The PMs and the control component communicate with one another by
means of messages sent via DS-30, DS-1 and DS-512 links. The messages
can be PCM signals, or they can be control and information messages
exchanged by the central control element, the switching network and the
PMs.

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–55

System nodes
Any unit that can accept messages or originate them, or both, is termed a
“node.” Therefore, the central control and central messaging elements, the
NMs, the PMs and the IOC are all nodes. In NT40-based systems, the side
of a node (or link) “facing” toward the central control element is referred to
as the “C-side;” the side of a node (or link) facing toward the PMs is
referred to as the “P-side.” In SuperNode-based systems, the side of a node
(or link) facing toward the DMS-Bus is referred to as the C-Side: the side of
a node (or link) facing away from the DMS-Bus is referred to as the P-side.
In both switching systems, messages going from the C-side to the P-side are
called outgoing messages. Those coming from the P-side to the C-side are
called incoming messages.
When installed, each NM, IOC and PM is assigned a unique node number
by the system. Each terminal controlled by the node is assigned a unique
number on the node. Therefore, every terminal (for example, line and trunk)
on the system is identified internally by a unique “terminal identifier” made
up of the node number and the terminal number on the node. This identifier
may be thought of as the address of a terminal. The central control element
software controls terminals by sending messages to the nodes on which they
are located. These messages include the terminal identifier, as well as the
data necessary for the particular action being performed.
Message link control is handled by the input/output (I/O) system. This
function is distributed among the nodes since each node must receive and
send messages over its C-side and P-side message links. The I/O System
uses routing land error control information is a message to ensure successful
message transmission in the presence of link noise or in the event of
transient or permanent hardware faults.
DS-30 interface
The common interface between components of DMS-100 system is a serial
data link with a bit-stream format. This format is termed “DS-30” and is
composed of 32 10-bit channels within a 125 microsecond frame. The
channels are numbered 0 to 31; channel 0 comes first in time.
Note: Framing is required so that both sending and receiving equipment
can agree on channel and bit number.

DS-512
The DS-512 format is the standard for internal optical fiber links on DMS
SuperNode. A DS-512 link is equivalent to 16 DS-30 links, multiplexed
onto a single optical fiber. One channel is used for link synchronization.
DS-512 provides more bandwidth than DS-30, and allows greater packaging
density.

DMS-100 International Technical Specification BCS40i and up

1–56 System architecture

S-512 format is used on the link between DMS-Core and DMS-Bus. This
link is a 32-Mb/s message channel. The distance specification of a DS-512
link is 250 meters. The DS-512 link is based on short-wavelength optical
technology, using LEDs and multi-mode fiber.

Link peripheral processor (LPP)

The link peripheral processor (LPP) is a DMS SuperNode equipment cabinet
that provides connectivity to the common channel signaling network.

How a link peripheral processor is configured

Figure 1–24 on page 1–57 illustrates the physical configuration of an LPP.
The LPP supports the following subsystems:
• FSP
• link interface module (LIM)
• link interface shelves (LIS) (up to three)
• core cooling unit
• frame transport buses (F-bus) (not shown)
All of the LPP equipment that is listed above is included as part of Northern
Telecom product engineering code (PEC) NT9X70.
Frame supervisory panel
The FSP accepts the battery feed and ground return from the PDC, and
distributes power to the shelves of the LPP frame. The FSP also contains
alarm circuits.

Link interface module

The LIM is the top shelf of the LPP and contains the cards and paddle
boards for two LMSs and two F-buses.

Link interface shelves

Each LIS is fully wired to allow plug-in provisioning of the cards and paddle
boards that are required to support application specific units (ASU). ASUs
provide the physical interface between external signaling links (SL) and the
internal signal processing functions of the node.
Core cooling unit
The core cooling unit provides mechanical ventilation for the equipment
housed in the LPP cabinet.

Frame transport bus

The F-bus provides the message path between the LIU7 and the LIM unit.
Two F-buses, operating in a load-sharing arrangement, are installed in the

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–57

LPP. These buses, illustrated in figure 1–25 on page 1–59, are composed of
cards, paddle boards, and interconnecting cables. There are two F-bus
repeater cards (one for F-bus 0, one for F-bus 1) and two F-bus extender
paddle boards (F-bus 0 and F-bus 1) associated with each LIS. There are
also two F-bus terminator cards for each LIS, one for each F-bus.

Link interface module

The LIM shelf houses two LIMs (LIM 0 and LIM 1). The LIMs are
high-capacity communication hubs that control the messaging between
ASUs in LISs. They also control the messaging between the LPP and the
DMS-bus. In addition to controlling messaging, each LIM accepts the
external composite clock signals that provide network timing for the SLs
that connect to the ASUs.
Figure 1–24
LPP physical configuration
FW-30196

Frame
supervisory panel

LIM LIM Local message

unit 0 unit 1 switch shelf

Link
interface
shelf 1

Link
interface
shelf 2

Link
interface
shelf 3

Cooling unit

DMS-100 International Technical Specification BCS40i and up

1–58 System architecture

Each F-bus is an eight-bit bus that forms the data communication path
between a local message switch and the LISs. The F-buses are dedicated to
each LIM as follows:
• F-bus 0 is dedicated to LIM 0
• F-bus 1 is dedicated to LIM 1

Each LIM is connected separately to each plane of the DMS-bus by two

DS30 links. LIM 0 and LIM 1 are also interconnected by two DS30 links.

LIM and F-bus reliability

Each LIM and each F-bus operates in load-sharing mode with its mate. This
ensures system reliability if an LIM or F-bus fails, because each LIM plane
has adequate capacity to carry the full message load of a LIM, and each
F-bus has the capacity to carry the full LIM load.

To ensure timing reliability, one clock signal is provided to each LIM,

providing each ASU with two sources for its composite clock signal.

Link interface shelf

LISs house the ASUs that provide the physical interfaces between external
SLs and the internal signal processing functions of the node. The
NT9X72BA supports the two-slot ASUs. When fully provisioned, three
NT9X72BA LISs can support 36 two-slot ASUs.
Each LPP is provisioned with three LISs. The maximum number of ASUs
depends on the type of ASU and the node.

CCS7 link interface unit

An LIU7 processes the messages that enter and leave an LPP through an
individual SL. Each LIU7 consists of a set of cards and a paddle board. The
cards and paddle board are provisioned in one of the LISs.

CCS7 link interface unit configuration

LIU7s are available in a two-slot configuration that requires two slots on the
LIS. The LIU7 consists of the following hardware:
• integrated processor and F-bus interface (IPF) card
• signaling terminal (ST) card
• DS-0A or V.35 interface paddle board

The IPF card provides message processing for its associated SL, including
GTT for DMS-STP applications. It also provides one interface or tap to
each of the two F-buses. Each F-bus tap is fully independent of the other
tap. This ensures that if one F-bus fails, the IPF can still access the other
F-bus.

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–59

The ST card performs error detection and correction, as well as signal-unit

alignment and delimitation, SL alignment and synchronization, and flow
control procedures.
The DS-0A or V.35 interface paddle boards provide the physical interface
between the SLs and the LIU7.
Figure 1–25 illustrates the organization of physical links between cards in
the LIS where two-slot LIU7s are installed.
Figure 1–25
Organization of a two-slot LIU7
FW30149

To LIM unit 0 To LIM unit 1

F-bus F-bus F-bus F-bus

extender terminator terminator extender
paddle board paddle board paddle board paddle board
NT9X79 NTEX20BA NTEX20AA NT9X79

F-bus F-bus 0 F-bus

repeater repeater
NT9X74 NT9X74

F-bus 1

LIU7 EIU
Integrated Integrated
processor and processor and
F-bus interface F-bus interface
P-bus

NTEX22 NTEX22 P-bus

Interface Signaling Ethernet Ethernet

paddle board terminal paddle board interface
NT9X77 or NT9X76 NT9X85 card
NT9X78 NT9X84

Signaling link Ethernet LAN

Channelized link access

As shown in figure 1–26, non-channelized access connections between the
CCS7 network and LIU7 are set up over dedicated links through a carrier
channel bank.

DMS-100 International Technical Specification BCS40i and up

1–60 System architecture

Figure 1–26
Non-channelized access link configuration
FW-31193

Outside world

PCM30

Channel bank

Modem

V.35 DS-0 DS-0 DS-0 DS-0

LIU7 LIU7 LIU7 LIU7 LIU7

Channelized link access, as shown in figure 1–27, provides advantages by

eliminating the need for external channel banks for DS-0 connections.
Channelized access is compatible with both two- or three-slot LIU7s. Since
channelized access hardware is associated with the LPP, it is only supported
on SuperNode-based DMS switches.
The channelized link access feature only affects signaling access between
the signaling data links and the LIU7. Messaging between the LIU7 and the
LIM is unaffected.

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–61

Figure 1–27
Channelized access external interface configuration
FW-30327

Outside world

PCM30

PDTC

Network plane 0

Network plane 1

LIU7 LIU7 NIU NIU LIU7 LIU7

CBI CBI unit 0 unit 1 CBI CBI
CBC CBC

C-bus 0

C-bus 1

Figure 1–28 provides a more detailed overview of channelized link access

modules, and shows the interconnection between the following DMS
peripheral modules (PM):
• PCM30 digital trunk controller (PDTC)
• switching network
• LIS
• channel access bus (C-bus)
• network interface unit (NIU)
• LIU7

DMS-100 International Technical Specification BCS40i and up

1–62 System architecture

Figure 1–28
CCS7 channelized access system overview
FW-31136

DMS-core

DMS-bus

DS30 interface

LPP Network
LIM unit 0 LIM unit 1

LIU7 NIU LIU7

PDTC
Unit 0 Unit 1
Channelized
access software
Signaling links

PCM30 digital trunk controller

PDTCs used for channelized link access are modified by datafill tables.
Digital trunks and CCS7 links can both be supported by the same PDTC.
Switching network
Channelized link access is compatible with both junctor networks (JNET)
and enhanced networks (ENET). Nailed-up connections (NUC) between the
PDTC and NIU through the network are assigned in datafill tables. Four
DS30 links are assigned for each NIU.
Link interface shelf
Channelized access reduces the capacity of a two-slot LIS from 12 to 10
LIU7s. The card arrangement for a two-slot LIS with NIU is shown in
figure 1–29.

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–63

Figure 1–29
Two-slot link interface shelf with an NIU
FW31190

NT9X30 +5V 86-A power converter 36F

NT9X19 Filler faceplate 33F

32R NT9X79 F-bus extension NT9X74 F-bus repeater 32F
31R 31F
30R NTEX20 Intrashelf termination 30F
29R 29F
28R 28F
27R 27F
26R 26F
25R 25F
24R 24F
23R 23F
22R 22F

Front
Rear

21R NTEX28 NIU DS30 link I/F NTEX25 NIU CBC 21F
20R NT9X19 Filler faceplate NTEX22 IPF 20F
19R NTEX28 NIU DS30 link I/F NTEX25 NIU CBC 19F
18R NT9X19 Filler faceplate NTEX22 IPF 18F
17R 17F
16R 16F
15R 15F
14R 14F
13R 13F
12R 12F
11R 11F
10R 10F
09R 09F
08R NTEX20 Intrashelf termination 08F
07R NT9X79 F-bus extension NT9X74 F-bus repeater 07F

Paddle boards
NT9X30 +5V 86-A power converter 04F

NT9X19 Filler faceplate 01F

Cards

DMS-100 International Technical Specification BCS40i and up

1–64 System architecture

Channel access bus

The C-bus, located on the backplane of each LIS, is a duplicated,
time-division multiplexed bus operating at 4.096 MHz, and is arranged as
512 channels of 10 bits each. One duplicated C-bus for each LIS provides
communication between all the ASUs on a shelf and the NIU.
Network interface unit
An NIU is a duplicated, warm-spared CCS7 PM that is mounted on a LIS. It
transfers data between the DMS network (junctor type or ENET) and the
C-bus. The NIU acts as a switch by providing a maximum of 10 connection
paths between the 512 channels available on the C-bus and the 120 channels
available on the DS30 links from the DMS network. An NIU is provided on
all LIS shelves where channel access is required.
An NIU consists of an integrated processor and an IPF, a channel bus
controller (CBC), and a link interface paddle board (LPB) as follows:
• The IPF is a general purpose MC68030-based processor board
containing 8 Mbytes of memory for the local software load.
• The CBC contains integrated circuits that monitor and control
transmission of data through the NIU.
• The LPB interfaces with the DS30 datalinks (up to four) from the DMS
network, and transmits data to both CBCs. The LPB also receives data
from the CBCs, which is forwarded through the DMS network.
Communication with each NIU is achieved as follows:
• The F-bus provides CM to NIU communication. The NIU is reset and
has operational software loaded through the F-bus. All maintenance
messages to the NIU are sent on the F-bus.
• The DS30 links to a single plane of either an ENET or JNET. Each NIU
transmits to and receives from the network a data stream identical to that
received by its mate NIU.
• Connections are made to a unit’s C-bus. NIU unit 0 controls C-bus 0,
and NIU unit 1 controls C-bus 1.
• An inter-CBC cable connects to the mate NIU on the backplane. Access
to the other network plane is achieved by this connection. This
inter-CBC cable is also used to pass status information between the
CBCs in order to perform activity switching.
LIU7
LIU7s have a two-slot configuration using an ST card and DS-0A or V.35
paddle board. LIU7s associated with channelized link access are identical to
those associated with non-channelized access, with the exception of the
paddle board. Instead of a DS-0A or V.35 interface paddle board, a C-bus
interface paddle board is required for channelized access. The NIU C-bus
and F-bus connections are shown in figure 1–30.

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–65

Figure 1–30
NIU bus configuration
FW-30328

LIM unit 0 LIM unit 1

F-bus 0

F-bus 1

LIU7 LIU7 NIU NIU LIU7 LIU7

unit 0 unit 1

C-bus 0

C-bus 1

Single shelf link peripheral processor

The SSLPP is provided as an option for DMS switching offices that do not
require a large number of ASUs. The SSLPP differs from the LPP
arrangement because it eliminates the need for a LIM between an ASU and
the DMS-bus. Instead, each F-bus on each SSLPP is cabled directly to the
MS with fiber-optic cables.
This arrangement is shown in figure 1–31.

DMS-100 International Technical Specification BCS40i and up

1–66 System architecture

Figure 1–31xxx
SSLPP F-bus and MS interconnections
FW-30350

Inter-MS link

Message switch 0 Message switch 1

Fiber-optic cable Fiber-optic cable

SSLPP shelf
Intra-shelf bus F-bus 1
I/F I/F

ASU ASU ASU ASU ASU ASU

F-bus 0 Intra-shelf bus

SSLPPs are mounted in a DMS SuperNode equipment cabinet called an

enhanced multipurpose cabinet (EMC), as shown in figure 1–32. SSLPPs
are connected to the DMS-bus with connectorized fiber-optic cables. A
maximum of 24 ASUs (12 in each SSLPP) are provided through this
arrangement. The SSLPP card arrangement is shown in figure 1–33.
The SSLPP is similar to the two-slot LIU7 shelf used in the LPP cabinet
with the following exceptions:
• the LIS F-bus controller card (NT9X96) which
— interfaces with the LIS F-bus
— interfaces with the LIS fiber interface paddle board (LFI PB)
— performs F-bus protocol control and rate adaptation functions
— performs F-bus link message supervision, routing, and control
functions
• the LFI PB (NT9X98) which
— interfaces with a DS512 fiber
— contains the SSLPP subsystem clock
— performs clock message reception and buffering for LIU7s
— performs reset control logic and reception

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–67

Figure 1–32
An example of an EMC cabinet with SSLPPs
FW-31191

FSP

SSLPP 1 NT9X72

SSLPP 2 NT9X72

Filler faceplate

Filler faceplate

Core
cooling unit

Note: The enhanced multipurpose cabinet (EMC) is an NTEX01.

DMS-100 International Technical Specification BCS40i and up

1–68 System architecture

Figure 1–33
SSLPP card arrangement arrangement
FW-31192

NT9X30 +5V 86-A power converter 36F

NT9X31 –5V 20-A power converter 33F

32R NT9X98 LIS fiber IF NT9X96 LIS F-bus controller 32F
31R ASU 12 31F
ASU 12
30R 30F
29R ASU 11 29F
ASU 11
28R 28F
27R ASU 10 27F
ASU 10
26R 26F
25R ASU 9 25F
ASU 9
24R 24F
23R ASU 8 23F
ASU 8
22R 22F

Front
Rear

21R ASU 7 21F

ASU 7
20R 20F
19R ASU 6 19F
ASU 6
18R 18F
17R ASU 5 17F
ASU 5
16R 16F
15R ASU 4 15F
ASU 4
14R 14F
13R ASU 3 13F
ASU 3
12R 12F
11R ASU 2 11F
ASU 2
10R 10F
09R ASU 1 09F
ASU 1
08R 08F
07R NT9X98 LIS fiber IF NT9X96 LIS F-bus controller 07F

Paddle boards
NT9X30 +5V 86-A power converter 04F

NT9X31 –5V 20-A power converter 01F

Cards

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–69

International remote line concentrating module (IRLCM)

The IRLCM provides a means of interfacing up to 640 subscribers, at a
remote location, to a DMS-100 host over 2 to 6 PCM30 links. The IRLCM
provides an optional intra-calling capability, allowing calls between
subscribers on the same IRLCM to be switched internally within that
IRLCM. The maximum number of lines supported depends on the traffic
patterns and call attempt rate involved.
At the host DMS-100, PCM30 links from the IRLCM interface to the system
using an ILGC. All PCM30 links from an IRLCM must terminate on the
same ILGC. A block schematic of the IRLCM is shown in figure 1–34.
IRLCM equipment
The IRLCM occupies a standard DMS-100 Family single-bay frame. As
shown in figure 1–35, this bay contains the ILCM, an RMM, PCM30
interfacing, ringing and FSP equipment, and optionally, an ESA processor.
Additional external equipment items required to support the IRLCM are
batteries, rectifiers, power distribution center (PDC), and VF distribution
frame.
Figure 1–34xxx
Relationships Within the IRLCM
FW-31142

Line DS30A Line

control concentrating
card 0 array 0

ESA tone
and clock
card
PCM30 Remote
To interface maintenance Inter-unit
DS30A
host card module link
ILGC ESA
processor

Line Line
control DS30A concentrating
card 1 array 1

DMS-100 International Technical Specification BCS40i and up

1–70 System architecture

Figure 1–35xxx
IRLCM Frame Layout – Front View
FW-31143

RG 0 RG 1
FSP

RMM

HIE

Cooling unit

LCA 1

LCM

LCA 0

Grill

Legend:
FSP Frame supervisory panel
HIE Host interface equipment
LCA Line concentrating array
LCM Line concentrating module
RG Ringing generators
RMM Remote maintenance module

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–71

Host interface equipment (HIE) shelf (NT6X11)

The HIE shelf provides an interface between the IRLCM and the host ILGC
in the central office, as shown in figure 1–36. The HIE also provides
emergency stand alone (ESA) capability if the communication links to the
ILGC are disrupted.
Figure 1–36xxx
HIE shelf layout
FW-31140

Front view

NT2X70AD Power converter

NT2X70AD Power converter

NT6X45AF ESA processor*
NT6X47AB ESA memory*

NT0X50AA Filler panel**

NT6X60AA IRLCM RG 0

NT6X60AA IRLCM RG 1

NT0X50AG Filler panel

NT0X50AA Filler panel

NT6X27AAB PCM30
NT6X27AAB PCM30
NT6X73BA LCC 1
NT6X73BA LCC 0
NT6X75 ETC*

Slot 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
Legend:
ETC ESA tone and clock card
LCC Link control card
Notes: *Cards in slots 14–16 are provisioned for ESA option only. Otherwise, the slots are
closed by filler panels (NT0X50AA).
**If additional PCM30 links are required (maximum of six links), the filler panel is
replaced by NT6X27AB.

PCM30 interface card (NT6X27)

The HIE shelf contains two or three PCM30 interface cards. This card
contains two 30-channel, 2.048 Mbit/s PCM30 interfaces.
Link control card (NT6X73)
The HIE shelf contains two link control cards. The card acts as the
messaging interface and provides data rate conversion between the LCA or
RMM, and the PCM30 cards. It provides the messaging interface for the
ESA clock and tone card, and the processor. It is also the clock source for
the IRLCM.
Ringing generator (NT6X60)
The HIE shelf contains two ringing generators that provide cadence of
ringing, ringing frequency and amplitude, and dc offsets of ringing voltages.

DMS-100 International Technical Specification BCS40i and up

1–72 System architecture

Power converter (NT2X70)

The HIE shelf contains two power converters. The card produces ± 5 volts
and ± 12 volts.
ESA, clock and tone card (NT6X75)
The HIE shelf contains the optional ESA, clock and tone card. The card is
required when the ESA feature is provided. It provides the clock for the
ESA processor as well as dial tone, receiver off-hook tone, audible ringback,
and ESB ringdown.
68000 processor card (NT6X45)
The HIE shelf contains the optional 68000 processor card. The card is
required when the ESA feature is provided. It contains a 68000
microprocessor plus associated control logic, a bootstrap loader, a message
system, and ROM diagnostics.
Memory card (NT6X47)
The HIE shelf contains the optional memory card. The card is required
when the ESA feature is provided. It contains 2 Mbytes of RAM memory
required by the processor card.
Line concentrating array (LCA) shelf (NT6X04)
The LCA shelf contains the following equipment.
LCM processor card (NT6X51)
The LCA shelf contains one ILCM processor card. It controls the LCA
activity and sanity checking, and performs digit collection and messaging
for up to 640 lines. It provides DMSX message protocol to the ILGC,
monitors power and ringing functions, and is responsible for clock recovery
and generation.
Digroup control card (NT6X52)
The LCA shelf contains one digroup control card. It interfaces up to 3
DS30A links and up to 10 ILCM drawers. It provides time switching for
external and internal channel assignment, and provides digital loop-around
paths.
Line drawer (NT6X05)
The LCA shelf contains five line drawers that each contain a maximum of
64 line cards and a bus interface card, as shown in figure 1–37.

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–73

Figure 1–37xxx
LCA shelf layout
FW-30248

FRONT VIEW

NT6X52AB Digroup control card

NT6X51AA LCM processor card
NT6X53AA Power converter

NT6X05BA Line drawer

NT6X05BA Line drawer

NT6X05BA Line drawer

NT6X05BA Line drawer

NT6X05BA Line drawer

01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21

Bus interface card (NT6X54)

The line drawer contains one bus interface card (BIC) that interface between
two 32-channel digroups and the 64 line cards in the line drawer. It
multiplexes/demultiplexes a 32-channel, 2.56 Mb/s PCM link onto 32 line
card buses, receives control messages from the line cards and stores them
until they can be output in channels 0 or 16, and scans the line cards for
changes in supervision bits.
Metering tone generator (NT6X95)
The metering tone generator occupies one line card position. One is
required per line drawer equipped with Type B line cards for meter pulsing
control (that is, not required for line drawers with Type B line cards for
reversals only).
Line cards (NT6X93, NT6X94)
The line cards are located in the line drawer. There are 64 line cards per line
drawer, five line drawers per LCA shelf and two LCA shelves per IRLCM,
providing a 1280 line capacity. The NT6X93 card is a Type A 600 ohm
POTS line card. The NT6X94 card is a Type B 600 ohm line card used for
meter pulsing coin control or for reversals for coin or PBX lines.
Power converter (NT6X53AA)
The ILCM shelf contains one power converter. It provides +5V and +15V
output and the power for the ringing and ANI/coin functions.

DMS-100 International Technical Specification BCS40i and up

1–74 System architecture

Remote maintenance module (RMM) shelf (NT6X13)

The RMM, shown in figure 1–38, is a single-shelf PM that provides
maintenance and operational support to a remote office connected to a
DMS-100 Family central office.
Figure 1–38xxx
RMM shelf layout
FW-31139

FRONT VIEW
NT2X59 Codec and tone card

NT6X74AB RMM control card

Optional test trunk or service

NT2X09AA Power converter

NT2X70AA Power converter

NT0X50AA Filler faceplate
cards – maximum of 14

01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21

RMM control card (NT6X74)

The RMM shelf contains one RMM control card. It provides processor,
memory and I/O functions.
CODEC and tone card (NT2X59)
The RMM shelf contains one coder/decoder (CODEC) and tone card. It
provides ROM-based tone generation and conversion between VF signals
and A-law companded PCM.
Power converter (NT2X70, NT2X09)
The RMM shelf contains two power converters: one NT2X70 card and one
NT2X09 card. The NT2X70 provides a regulated ± volt and ±12 volt
output. The NT2X09 is a multi-output power converter providing +24V,
+12V, +5V, –15V, and –5V.
Metallic test unit (NT4X97, NT4X98)
The RMM can contain an optional metallic test unit (MTU). The MTU is
used to perform maintenance tests on the subscriber loops or the line circuit.
Incoming/outgoing test trunk (NT2X90)
The RMM can contain an optional incoming/outgoing test trunk. It provides
an interface between the #14 local test desk (#14LTD), #3 local test cabinet

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–75

(#3LTC), centralized automated loop reporting system (CALRS) test desk

and the RMM.
Incoming test trunk (NT3X04)
The RMM can contain an optional incoming test trunk. This trunk provides
a metallic connection between an Automatic Electric (AE) No. 31 test desk
and a subscriber line.
Miscellaneous scan detector card (NT0X10)
The RMM can contain optional scan cards equipped as required. There are
14 scan detector circuits per card, each of which can be configured as a loop
detector, ground detector or battery detector using switches on the card.
Signal distribution card (NT2X57)
The RMM can contain optional signal distribution (SD) cards equipped as
required. Each card contains 14 interface circuits, the output of which can
be either single-lead or double-lead with open or closed ground
(single-lead), or with open or closed loop (double-lead).
Digitone receiver card (NT2X48)
The RMM can contain optional digitone receiver cards equipped as required.
The NT2X48 card provides A-law DTMF reception.
Remote metallic test access card (NT3X09)
The RMM can contain an optional remote metallic test access card. The
card provides metallic access between test and line circuits.
Frame supervisory panel (NT6X25)
The frame supervisory panel (FSP) contains power control and alarm
facilities which provide interfaces between the power distribution center
(PDC) and the power converters on the various IRLCM shelves. The FSP is
located at the top of the IRLCM frame.

DMS SuperNode SE
DMS SuperNode SE architecture is essentially the same as that of the
full-sized DMS SuperNode system. The SuperNode SE platform supports
all subtending equipment supported by SuperNode, including ENET, JNET,
LPP, the IOC, the MAP, remotes, and PMs. The SuperNode SE platform
combines the switching core, ENET and CCS7 link functionalities in the
SuperNode combined core (SCC) cabinet, as shown in Figure 1–39.

DMS-100 International Technical Specification BCS40i and up

1–76 System architecture

Figure 1–39xxx
DMS SuperNode SE SuperNode combined core cabinet
FW-30317

Frame
supervisory panel

MS 0 MS 1 DMS-bus

Link interface shelf

(optional – up to 12 LIUs)

16K 16K
ENET 0 ENET 1

SLM 0 SLM 1
DMS-core
CPU 0 CPU 1

Cabinet
cooling unit

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–77

Figure 1–40xxx
DMS SuperNode SE functional block diagram
FW-30432

CPU 0 CPU 1
SLM 0 SLM 1
DMS-core

MS 0 MS 1
DMS-bus

LIS

NET 0 NET 1

PMs

Figure 1–40 illustrates the functional architecture of the DMS SuperNode

SE system. The following sections summarize the major architectural
components of the SuperNode SE platform.

DMS-core
The DMS-core provides the processing resources and performs system
management in DMS SuperNode SE applications. The DMS-core also
handles system integrity, maintenance, and the loading and downloading of
software. Figure 1–41 illustrates the main components of the DMS-core.

DMS-100 International Technical Specification BCS40i and up

1–78 System architecture

Figure 1–41xxx
Main components of the DMS-core – SuperNode SE
FW30116

Processor bus

Master Memory DMS-bus System

processor interface load
MC68020 module

DMS-core

DMS-bus

Network IOC

The DMS-core consists of the CM with two synchronized CPUs, each with
an SLM. The CPUs are connected by the mate exchange bus, which allows
the processors in the modules to compare computations, thus ensuring
system integrity between the active and inactive planes.
The two SLMs are used for storage of software loads, office images, and PM
loads. Each SLM consists of one cartridge tape drive and a disk drive unit
(DDU). In the DMS SuperNode SE cabinet, the DMS-core occupies a
single shelf; the DMS SuperNode switch requires two shelves for the same
components. This space saving is achieved through the use of high-density
memory cards and disk technology.
SuperNode SE computing module
The SuperNode SE CM is fully duplicated and synchronized. Its CPUs are
based on a 32-bit Motorola microprocessor, with a built-in instruction cache
facility and an onboard high-speed data cache. Normally the duplicated
CPUs run in synchronized mode, with the controlling CPU known as the
active processor and the mate as the inactive processor.
Other features of the computing module include
• integrated program and data store with single-bit error detection

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–79

• high-speed duplicated message controllers (MC)

• distributed control reset system
• direct access to combined disk and tape SLM
• integrated inventory management for online identification of product
type and vintage for individual cards and paddle boards
Functional subsystems of the computing module
The shelf housing the CM is equipped with cards on the front, and
corresponding paddle boards on the rear. The cards share a common bus
with the paddle boards. The CM contains the following functional
subsystems:
• processor and memory (NT9X13, NT9X14, NT9X10)
• interfaces (NT9X12, NT9X46, NT9X62, NT9X86)
• reset control (NT9X26)
• clock (NT9X22)
• bus termination (NT9X21)
• power supply (NT9X91, NTDX15)

Processor and memory (NT9X13, NT9X14, NT9X10)

The processor and memory subsystem is responsible for call processing, and
configuring and maintaining the other systems. The processor and memory
subsystem consists of two CPU cards and up to five memory cards. The
CPU cards house the microprocessor circuitry. The memory cards provide
storage for the CPU. The program and data store provide single-bit error
detection.
Each CPU can accommodate up to five memory cards. Using 96-Mbyte
cards allows for a 200-Mbyte card with Series 20 and a 400-Mbyte card with
Series 60, plus a 32-Mbyte block spare. Block sparing eliminates the need
to dedicate an entire memory card as a spare in case of memory problems.
Instead, each 96-Mbyte card is partitioned into three 32-Mbyte segments,
any of which can be designated as spare memory. Hot sparing minimizes
the impact of memory problems because the system switches to spare
memory automatically at the first sign of failure. The DMS SuperNode SE
switch also supports card sparing, which allocates an active card for spare
memory.
The DMS SuperNode SE switch can be equipped with the following
processors:
• Series 20
• Series 60

A Series 20 processor and memory subsystem consists of two CPU cards

(NT9X13MB) and up to five 24-Mbyte memory cards (NT9X14DB) or up

DMS-100 International Technical Specification BCS40i and up

1–80 System architecture

to five 96-Mbyte memory cards (NT9X14EA). The 24-Mbyte memory

cards and the 96-Mbyte memory cards cannot be used together, all five cards
must be of the same type.
The DMS SuperNode SE switch equipped with a Series 20 processor, can
handle up to 400 000 POTS service busy-hour call attempts (POTS BHCA).
A Series 60 option is a DMS-core equipped with NT9X10AA processor
circuit packs and their associated NT9X26DB RTIF paddle boards, and is
exclusively equipped with NT9X14EA memory circuit packs. This
provisioning allows the SuperNode SE to operate in burst mode. Burst
mode is a type of memory addressing that provides enhanced system
performance.
The DMS SuperNode SE switch equipped with a Series 60 processor can
handle up to 1.4 million POTS BHCA.
Interfaces (NT9X12, NT9X46, NT9X62, NT9X86)
The NT9X12 interface circuit pack and the NT9X46 parallel port paddle
board connect the CPU to the SLM by means of interconnect cable.
The NT9X86 dual port interface circuit pack allows termination of two
separate optical fiber links through the dual-link SubRate fiber interface
paddle board (NT9X62) to provide communications interface between the
CM and the MS computing module interface card (CMIC).
Figure 1–42 shows how the CMIC links are configured.

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–81

Figure 1–42xxx
DMS SuperNode SE CMIC link configuration
FW-30319

Card 4 Card 4
Slot 16 Slot 23

9X17AD 9X17AD
Port 0 Port 0

MS 0 MS 1

9X62AA 9X62AA

Port 0 Port 1 Port 1 Port 0

Port 0 Port 1 Port 0

DS512 DS512
9X62AA 9X62AA

MC0 MC1
9X86 9X86

CPU 0 CPU 1

Slot 18 Slot 21

Reset control (NT9X26)

The reset terminal interface (RTIF) paddle board (NT9X26) provides a video
display unit (VDU) interface for processor state information and for local
and remote resetting of the CM. The RTIF paddle board has two interface
ports. One port is connected to the local reset terminal; the other can be
used to connect an optional remote reset terminal through a modem.
The RTIF is connected to the local reset terminal by an RS-232 interface or
by a 20-mA current loop interface, providing improved electrical grounding
between the reset terminal and the RTIF. With an RS-232 interface, the

DMS-100 International Technical Specification BCS40i and up

1–82 System architecture

local terminal can be up to 15 m (50 ft) from the RTIF. With a 20-mA
current loop interface, the local terminal can be located up to 457 m (1500
ft) from the RTIF.
The remote terminal port can be configured as either RS-232 or E2A to
handle baud transmission rates from 110 to 9600.
A VT420 MAP terminal that can operate in dual terminal mode can be used
to provide a virtual RTIF terminal and eliminate the need for duplicated
terminals.
Clock (NT9X22)
Each CM contains a subsystem clock that provides link synchronization to
the MS. The accuracy of the clock is determined by the office clock signal
distributed through the MS. The basic time reference is obtained through
the serial links.
Bus termination (NT9X21)
The bus termination consists of the CM bus terminator paddle board. It
provides resistive termination for the system bus in both the CM processor
and the SLM. In addition, it provides the circuitry required for buffering the
CM activity signal and extracting component identification from the power
converters.
Power supply (NT9X91, NTDX15)
The power supply provides power for all the components housed in the
DMS-core shelf. It consists of two ±5V power converters (NTDX15) and
two +5V/+12V power converters for the SLM (NT9X91).
The DMS SuperNode SE power interlock facility provides a safeguard to
prevent the system from being powered off accidentally while in service.
Under all other conditions, power interlock is disabled.
System load modules
The DMS-core shelf also houses two SLMs, their power supplies, and
interface circuitry. Each SLM consists of a 3.5-in. (8.9-cm) 340-Mbyte hard
disk drive (300 Mbyte when formatted) and a 150-Mbyte or 250-Mbyte
streaming tape drive with a removable cartridge.
An SLM is used to
• bootload the CM and the MS from disk or tape
• load an office image into the inactive CM
• dump an image to disk
• perform offline transfers from tape to disk or from disk to tape

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–83

The SLMs connect directly to the CM system bus. The active CM can
communicate directly with either SLM.

DIRP on the system load module

When configured with feature package NTXJ44AA, the SLM disk drive can
also be used by the device independent recording package (DIRP) as an
alternative to the I/O controller (IOC) for recording DMS subsystem data.
DIRP is a utility that manages the reading and writing of data among various
DMS subsystems and recording devices. Typical data handled by DIRP
includes operational measurements (OM) counts, automatic message
accounting (AMA) records, and journal files (JF). For additional
information about DIRP, refer to the Device Independent Recording Package
Product Guide, 297-1001-013.
Files and file management
The DMS SuperNode SE system uses the same file system as the full-size
DMS SuperNode system. While the I/O system is tailored to a group of
specific devices, such as printers or tape drives, the DMS SuperNode file
system provides a device-independent means to write to and retrieve data
from the various I/O devices that are connected to the system. The file
system makes it possible, for example, to send the same log report to a
terminal for review, to a line printer for hard copy, and to a magnetic tape
drive for storage.
The DMS SuperNode file system provides a logical view rather than a
physical view of the data and the functions to be performed. The file system
consists of a common interface called the logical file system (LFS), which is
device independent, and the physical file system (PFS), which is device
dependent. The DMS SuperNode file system applications access physical
file systems through the LFS. The LFS provides a consistent set of file
operations that application software can use; the PFS provides a device
specific implementation of the file operations in the LFS. The structure of
the file system allows for the addition of new physical devices to the system
without any changes to the LFS.
SLM file system
The SLM file system (or standard (STD) file system) is designed for the
processing of system image files. It is directly controlled by the CM and
supports the SLM IA (300-Mbyte disk and 150-Mbyte or 250-Mbyte
cartridge tape). The SLM file system is part of the DMS SuperNode PFS.
The SLM file system includes the following capabilities:
• file sharing, which allows combinations of multiple readers and writers
with exclusive access
• multiple access modes
— read only

DMS-100 International Technical Specification BCS40i and up

1–84 System architecture

— write only
— read/write
• dynamic numbers of files
• efficient support for very large files
• support for cached and uncached files
• hierarchical directories
File security
Access to any file can be restricted using the file security system. Access is
determined by the security attributes of both the file and the user class. File
attributes are read, write, or execute. User class attributes are file owner, file
group, or everyone.
It is recommended that copies are maintained of all files held on system
disks, including the SLMs, in case of subsystem failure. Parallel recording
capabilities are provided for billing files.

DMS-bus
The DMS-bus consists of two duplicated MSs. Under normal operating
conditions, the MSs share the load, although each MS can support the entire
system load if necessary. Figure 1–43 illustrates the main components of the
DMS-bus.

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–85

Figure 1–43xxx
DMS-bus components
FW30113

DMS-core

Port Processor
interface DMS-bus T-bus
interface
Transaction bus

Processor bus

Port Port System Mapper Control

interface interface clock processor
MC68020

I/O controller Network

Each MS is managed by a Motorola 32-bit microprocessor. The

microprocessor performs such functions as port maintenance and
diagnostics. It communicates with other functional areas in the MS through
a 32-bit processor bus (P-bus).
The high-speed transaction bus (T-bus) acts as a hub for interprocessor
communications. The DMS-bus supports the IOC, ENET, LIS, application
processors (AP), link peripheral processor (LPP), the dual-shelf network
(DSN), and allows them to communicate with each other as well as with the
DMS-core.
The DMS-bus also houses the system clock. The system clock is used by
both the DMS-bus and the DMS-core to carry out general clocking and
timing functions. The office clock provides synchronization for the DMS
SuperNode SE switch. It can be used at a Stratum 3 level with the internal
clock, and with an external or remote clock source at the Stratum 1, Stratum
2, and Stratum 2.5 levels.
The DMS-bus access ports can be configured as either DS30 copper
interfaces or DS512 fiber optic interfaces. The use of DS30 copper
interfaces allows the DMS SuperNode SE system to be fully compatible

DMS-100 International Technical Specification BCS40i and up

1–86 System architecture

with existing DMS-100 Family IOC and NMs. Each MS is connected to

each CM plane in the DMS-core by subrate fiber links.
Message switch
The MS is a hub for communication among the DMS components. The MS
distributes messages within the DMS SuperNode SE system, and enables
other components to communicate directly with each other.
The MS provides the following capabilities:
• port-to-port message switching
• 240 000 messages per second with 64-byte message length
• independence among ports
• self-diagnosing and self-maintaining processor

The MS shelf is equipped with cards at the front and corresponding paddle
boards at the rear. The cards share a common bus with the paddle boards.
Inter-MS links provide additional reliability within the frame transport
system (FTS). If the route calculated by the FTS is unavailable—for
example, because one of the nodes selected is out of service—inter-MS links
direct the message by an alternative route, if one exists. Without inter-MS
links, the message would be lost.
The DMS-bus is configured with two inter-MS links. Figure 1–44 shows a
typical configuration using inter-MS links.
Figure 1–44xxx
Inter-MS links configuration – SuperNode SE
FW30325

MS 0 MS 1

Interface cards Inter-MS link 1 Interface cards

Inter-MS link 0

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–87

Functional subsystems of the message switch

The MS consists of the following functional subsystems:
• processor and memory (NT9X13)
• system clock (NT9X53, NT9X54)
• mapper (NT9X15)
• port interface (NT9X17, NT9X23, NT9X62, NT9X69)
• reset control (NT9X26)
• bus terminator (NT9X49)
• bus access (NT9X52)

Processor (NT9X13)
The MS processor system consists of the CPU card (NT9X13), which is
equipped with 16 Mbyte of on-board memory for storage.
System clock (NT9X53, NT9X54)
The system clock provides the clock source for the DMS SuperNode SE
switch. It consists of the system clock card (NT9X53) and the clock
interface paddle board (NT9X54).
The system clock card provides the internal Stratum 3 clock. Each office
has two sets of clock cards, one in each MS, that operate as internal master
and slave sources. The clock interface paddle board provides the direct
analog interface between DMS-bus and external clock sources (Stratum 1)
or remote clock sources (Stratum 2 or 2.5).
Mapper (NT9X15)
The mapper (NT9X15) performs logical-to-physical address translation for
messages routed between ports on the MS.
Port interface (NT9X17, NT9X23, NT9X62, NT9X69)
The port interface consists of optional combinations of the DS30 four-link
paddle board (NT9X23), the four or two-link subrate fiber paddle board
(NT9X62), the 16-link DS30 paddle board (NT9X69), and a range of MS
port cards (NT9X17). The subrate optical fiber links connect various
applications of the DMS SuperNode SE system, such as ENET. The DS30
paddle boards connect the MS to existing DMS-100 Family components,
such as the IOC.
Reset control (NT9X26)
The RTIF paddle board (NT9X26) monitors and decodes commands, and
passes them to the CPU in the form of control signals. It also monitors
processor signals, and relays them to the remote terminal or remote scanning
system.

DMS-100 International Technical Specification BCS40i and up

1–88 System architecture

Bus termination (NT9X49)

The bus termination provides passive terminations to back panel signals. It
consists of the MS P-bus terminator card (NT9X49CA).
Bus access (NT9X52)
The processing and accessing of the system bus is done through the T-bus
access card (NT9X52).
MS link interfaces consist of NT9X17 port cards and any of the NT9X23,
NT9X62, and NT9X69 interface paddle boards.
The applications of the NT9X17 cards include the following:
• a computing module intercommunications (CMIC) link to connect the
MS to the CM
• a four-port interface to provide DS30 links to connect the MS to the
subtending nodes
• 32-, 64-, and 128-port interfaces used in a port chain to connect an
ENET plane through fiber links

Enhanced network and interface shelf

The enhanced network and interface (ENI) shelf (NT9X0810) provides
space for an optional 16K ENET and two CCS7 link interface units (LIU7),
allowing the DMS SuperNode SE system to be configured as a service
switching point. ENET is a full-matrix timeswitch that provides circuit
switching of pulse code modulated voice and data connections between
PMs, and message paths to the DMS-bus. The LIUs can be equipped on the
ENI shelf only if ENET is provisioned.
ENET provides the following capabilities:
• nonblocking, single-stage switching
• nailed-up connections
• compatibility with A-law and µ-law companding
• DS-0 and multiple DS-0 switching
• junctorless

Functional subsystems of ENET

The main functional subsystems of the single-shelf ENET are as follows:
• processor and memory (NT9X13)
• clock and messaging (NT9X36, NT9X40)
• crosspoint (NT9X35)
• transmission and interface (NT9X40, NT9X41, NT9X26)
• power supply (NT9X30, NT9X31)

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–89

Processor and memory (NT9X13)

The processor and memory system, which provides operational and
diagnostic control for the shelf, consists of the CPU card (NT9X13FA). The
CPU card has 4 Mbyte of dynamic random access memory (DRAM), which
holds the ENET operating software, and 128 kbyte of read-only memory
(ROM) firmware for bootloading and initialization procedures.
Clock and messaging (NT9X36, NT9X40)
The clock and messaging system consists of the clock and message card
(NT9X36) and a four-link DS512 paddle board (NT9X40). The clock and
message card provides I/O control and the clock source for the shelf. The
DS512 paddle board provides two channelized fiber links to DMS-bus for
messaging. The shelf processor and the PMs connected to the shelf share
messaging on the links. One of the links also provides the clock source for
synchronization with the DMS-bus.
Crosspoint (NT9X35FA)
Up to eight 4K × 8K crosspoint cards (NT9X35FA) provide the 16K ENET
channel-switching matrix. The crosspoint cards are connected to the other
cards on the shelf by the horizontal bus (H-bus).
Transmission and interface (NT9X40, NT9X41, NT9X45)
Physical connectivity to the 16K ENET is optimized with fiber interfacing to
PMs. The DS30 copper interfaces are provided to accommodate Series 1
PMs, such as maintenance trunk modules (MTM), and nonfiber Series II
PMs, such as subscriber carrier module–100s (SMS) and subscriber carrier
module–100 rural (SMR), where only a relatively small number of channels
require connection to the network.
The transmission and interface system consists of DS512 fiber interface
paddle boards (NT9X40) or DS30 copper interface paddle boards
(NT9X41), or a combined DS512/DS30 interface paddle board (NT9X45).
These paddle boards are the transmit and receive interfaces between the PMs
and the crosspoint cards in ENET. DS512 links are used to connect
extended PMs (XPM) to ENET.
Series 1 PMs connect to ENET through the existing DS30 copper speech
links. Retrofit kits are required to allow existing PMs to connect to ENET.
(Trunk modules (TM) and MTMs do not require retrofit kits.)
With a few exceptions, Series II PMs connect to ENET using DS512 fiber
links. Retrofit kits are required to allow Series II PMs to interface ENET.
The following Series II PMs use copper speech links to connect to ENET:
• message switch and buffer 6 (MSB6)
• message switch and buffer 7 (MSB7)
• digital trunk controller 6 (DTC6)

DMS-100 International Technical Specification BCS40i and up

1–90 System architecture

• SMS
• SMR
Figure 1–45 shows an example of an ENET connected to a Series II PM
using fiber links.
Power supply (NT9X30, NT9X31)
The power supply is provided by two +5V power converters (NT9X30) and
two –5V power converters (NT9X31). One of each type of power converter
is located at each end of the shelf and provides power for half the shelf.
Figure 1–45xxx
Example ENET connection to a Series II PM
FW-30146

NT9X35 ENET ENET NT9X35

Paddle board Paddle board

DS512 link DS512 link

NT9X40BA NT9X40BA

Fiber link Fiber link

NT6X40* NT6X40*
paddle board paddle board

NT6X40** NT6X40**
PM (for example, DTC)

Notes: 1. * Provision either NT6X40DA or NT6X40GA paddle board.

2. ** Provision either NT6X40CA or NT6X40FA card.

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–91

Link interface shelf

The LIS (NT9X7204) allows you to provision up to 12 two-slot application
specific units (ASU) on a single shelf. ASUs provide the physical interfaces
between external signaling links and the internal signal processing functions
of the DMS SuperNode SE system. The LIS supports LIU7s, EIUs, XLIUs
and NIUs. Architecturally, ASUs on the SNSE LIS function in the same
manner as those provided in the LIS in an LPP, as described on page 1–58.

Frame supervisory panel

The FSP (NT9X03) performs alarm monitoring functions and reset control
functions for the power converters. It is located at the top of the cabinet in
shelf position 52. Power from the power distribution center comes into the
FSP and is then distributed to the power converters in the cabinet.

Cabinet cooling unit

The C42 cooling unit (A0377580) provides forced convection cooling for
the equipment housed in the SCC cabinet. Located at the bottom of the
cabinet, it contains three individually replaceable blowers. The cooling unit
can be removed by sliding it on support brackets attached to the uprights of
the cabinet.

DMS-100 International Technical Specification BCS40i and up

1–92 System architecture

Signaling among DMS SuperNode SE components

Two types of signaling protocols are used with the DMS SuperNode SE
system. The DS30s are used as a message carrier between the DMS-bus and
the NMs, and between the IOC and the LPP. Subrate fiber optic links
connect both the DMS-core and the optional 16K ENET to the DMS-bus.
DS30 and DS512 subrate fiber can be used to link ENET to various PMs.
DS30 protocol
The DS30 protocol is used as an interface among components of the DMS
SuperNode SE system. It consists of 32 ten-bit channels that are divided as
follows:
• 30 channels for pulse code modulated signals (channels 1 to 15,
17 to 31)
• 1 channel for messaging between the control component and the PMs
(channel 0)
• 1 channel for maintenance (channel 16)

The bit rate is 2.56 Mbit/s, which is dictated by the need to transmit speech
using 8-bit pulse code at 8000 samples per second. The bit rate is derived
from the following formula:
32 channels × 10 bits × 8000 samples per second = 2.56 Mbit/s.
DS512 protocol
The DS512 protocol is the standard for internal optical fiber links in the
DMS SuperNode SE system. It has 512 channels, one of which is used for
link synchronization. DS512 provides more bandwidth and greater
packaging density than DS30; one DS512 link is equivalent to 16 DS30
links.
Subrate DS512 interfaces are used in various applications in the DMS
SuperNode SE system, as follows:
• to provide the CMIC links
• to link the MS shelf to the ENET shelf
• to link the MS to application and file processors

Subrate links can operate at the following rates: SR128 (128 channels),
SR256 (256 channels), and full DS512 (512 channels), depending on the
application.
The DS512 protocol is used on links between the DMS-core and the
DMS-bus. The maximum length of a DS512 link is 250 m (273 yd). The
DS512 link is based on short-wavelength optical technology using
light-emitting diodes (LED) and multimode fiber.

PLN-5001-001i Standard 02.02 April 1997

 System architecture 1–93

Transmission coding and synchronization

The DS512 format is designed for synchronous transmission. A unique
12-bit pattern called the superframe pattern is transmitted every 125 µs on
the channel used for link synchronization. The superframe pattern is
detected at the receiver and used to align channels and frames. Each 10-bit
data word is converted to a 12-bit transmission code word. All 1024
possible 10-bit words are mapped into a selected subset of the possible
12-bit words. The transmission rate is 49.152 Mbit/s. One channel is lost to
the superframe pattern, and only 8 bits of each channel are used to carry
pulse code modulated signals. The messaging rate on a DS512 link is
32 Mbits.
DS512 message header
The DS512 message header used by the DMS-bus contains two destination
address fields: a physical address and a logical address. The physical
address identifies the destination MS port. The logical address is the
destination node identifier. If the physical address is set to a default value
(all 1s), then the MS mapper subsystem converts the logical address to a
physical address. To switch messages, the MS uses only the DS512 message
header. It handles only the message address, not its contents.

DMS-100 International Technical Specification BCS40i and up

 2–1

Software engineering
This chapter provides an overview of the modular software structure
employed on DMS-100 International switching systems. The software
packaging, development and delivery processes are also described.

Distributed processing
The DMS-100 Family of switches employs a distributed processing
architecture that uses several different processors:
• The DMS SuperNode computing module (CM) and message switch
(MS) are programmed in PROTEL, a high-level language developed by
Northern Telecom.
• The NT40 central control (CC) central processing unit uses a
microprogrammable processor that is programmed in PROTEL.
• The peripheral modules use a processor that is programmed in an 8085
assembly-level language.
• The XPMs use a processor that is programmed in PASCAL. XPM is a
term applied to the PMs based on the Extended Multiprocessor System
(XMS) also developed by Northern Telecom.
Although each has a different programming environment, these units
communicate by means of a simple interface. Messages are sent via serial
data links using DS-30, DS-512 and DS-1 protocols.
Under normal circumstances, the two central processing units (CPUs)
operate in sync (that is, both are simultaneously executing the same
instruction with the same data). Each has access to certain state information
in the mate central processing unit; therefore, fault detection (for example,
matching for loss of sync) can be carried out. In addition, this access
provides inter-processor communication for system maintenance software.

DMS-100 International Technical Specification BCS40i and up

2–2 Software engineering

Central control firmware/software

The central control subsystem (the Central Control on NT40-based systems,
or the DMS-Core on SuperNode-based systems) firmware and software
consists of programs that perform a number of functions necessary for
switch operation, plus tools for the implementation of these programs. The
majority of these programs are written in a high-level language (PROTEL)
and, after compilation and linking, are loaded into the program store of the
switch. The data associated with the programs is stored in the switch data
store. The code for three functions is implemented in CPU firmware (read
only memory):
• bootstrap loader
• micro-code for the execution of machine instructions
• applications not suitable for PROTEL (for example, some of the
processor maintenance code).
The internal structure of DMS-100 Family central control subsystem
software is described further on page 2–4.
Peripheral firmware/software
The central control subsystem exercises high-level control of calls and
system maintenance, and repetitive, time consuming tasks such as scanning,
control, and maintenance of telephony interfaces are delegated to the
microprocessor-based peripheral modules. The functions assigned to the
peripheral modules are performed by telephony peripheral virtual machine
(TPVM) programs, referred to as peripheral software. The TPVM is a
simulated computer which provides a high level mode of control of
telephone calls and other tasks carried out in peripheral modules.
The TPVM applies to all peripherals except the LCM, OPM, and RLCM,
which are directed by the LGC and do not require TPVM control.
The software that implements a TPVM in a peripheral module is stored in
RAM and is written in assembler language, with the exception of the the
LGC and DTC which are written in PASCAL. Only a small loader is stored
in PROMs and it constitutes the firmware of the various telephony
peripherals.
The internal structure of DMS-100 Family peripheral subsystem software is
described further on page 2–43.

Software packaging
From the operating company perspective, an installed DMS-100
International software load operates and appears as a seamless system. Prior
to installation, the software load is customized and compiled specifically for
the switching system on which it will be installed, providing all services and

PLN-5001-001i Standard 02.02 April 1997

 Software engineering 2–3

capabilities agreed upon between the operating company and Northern

Telecom.
The software load is made up numbered modules or “features”, which are in
turn grouped into feature packages based on the capabilities they provide. In
some cases, associated feature packages are grouped into master packages,
providing a single orderable software grouping for larger quantities of
related features.
All DMS-100 Family software loads contain a mix of mandatory “base”
software feature packages required for all system implementations, and
optional feature packages which provide incremental capabilities and
services. On DMS-100 International systems, the software load also
typically includes feature packages which have been developed specifically
for the market or country in question, to allow the system to interwork
within the geographical network in which it will operate.
The DMS-100 International Feature Description Manual, 297-1001–801i,
provides detailed descriptions and cross-reference information for all
available features and feature packages.

Custom feature development

Northern Telecom is committed to providing customers with innovative,
reliable software, designed for each office in which it operates. After
software delivery and implementation, Northern Telecom is available to
perform additional software customization at the customer’s request. The
modular nature of DMS software facilitates the development and
implementation of enhancements or custom features for specific needs.

Software delivery
Approximately twice a year, Northern Telecom issues a Batch Change
Supplement (BCS) containing new DMS-100 features. Each BCS release
offers hundreds of software features, developed by over 3, 000 designers,
testers, and support staff at four development sites. BCS releases are
constructed for each purchaser and delivered to DMS switching sites
throughout the world. New BCS releases are installed quickly and
cost-effectively while the system is fully operational, with minimal service
disruption.
One-night process
Northern Telecom’s BCS release is a “one-night” delivery process that
greatly simplifies and reduces the time required for software delivery. The
delivery process begins with a BCS package assembled specifically for the
DMS switch on which it will be installed. The software is then shipped to
the switch site and loaded into the inactive side of the fully-duplicated
DMS-100 processor. All customer-specific office data is retained and
transferred to the new software environment.

DMS-100 International Technical Specification BCS40i and up

2–4 Software engineering

The DMS-100 software delivery process is described in detail in One Night

Process and Hybrid Software Delivery Procedures, 297-1001–303.

Software development process

Northern Telecom uses a standardized development and verification process
to ensure that each BCS is delivered on time and satisfies or exceeds all
quality expectations. The BCS process consists of the following phases:
1 Planning
2 Development
3 Verification
4 Validation
5 Availability
Planning
The planning stage begins with a request for feature development, and a
corresponding response in the form of a product specification.
Development
All aspects of the software feature are examined and clearly specified,
followed by development of the required software code. The code is
developed using strictly-enforced coding standards to ensure conformity and
maintainability.
Verification
At this stage, BNR incorporates software feature integration and system
testing to ensure compatibility with existing software.
Validation testing
Validation is performed at Northern Telecom’s First Application System Test
(FAST) laboratories. All new features are tested extensively in conjunction
with the current level of software, under circumstances that simulate the real
environment in which the feature will be used. Successful completion of
FAST validation verifies that the feature is ready for insertion into selected
live validation offices for additional testing prior to manufacture.
Availability
Once fully verified, Northern Telecom permits limited introduction of the
software to selected sites, and prepares the software for general availability
in a full release.

Internal software structure

Internally, DMS-100 Family software is engineered using a highly modular
structure with narrow, well-defined interfaces among modules. The module
interfaces are designed around basic operating system functions (scheduling

PLN-5001-001i Standard 02.02 April 1997

 Software engineering 2–5

tasks or store allocations), basic call processing functions, features required,

and the hardware supported.
The selection of modules is designed to accommodate not only the type of
office (toll or local), but also the features required (such as subscriber
features, billing, or common channel signaling), and the hardware supported
(trunk types or digital carriers). In addition, the common library is designed
to accommodate customized versions of generic facilities.
The modules in the common library can be classified into several layers that
are used to build the software load for each office. The main layers are the
operating system, the call processing utilities, and the call processing
options. The call processing options do not provide direct interfaces for
other modules to call. They are specifically designed with no references to
them, so that they can be independently selected as options for any given
office. When loaded, they make themselves known to the rest of the system.
The term “agency” is used for these call processing options. Typically an
agency deals with a specific set of call processing features and the terminals
(lines or trunks) to which they apply.
An agency includes both the code and the data tables used to specify the
terminal service options, parameters, and status. An example of a module in
the call processing utility layer is the network control module. This module
provides the procedures to make or break a network connection between
specified network channels. To use these functions, other modules call the
appropriate procedure in the network control module interface. The
algorithms and data structures used to select a free path and send the
appropriate control messages out to the network peripheral processors are all
contained within the network module.
If the selection algorithms or data structures require modification, the effects
of such a change are strictly contained within the module and the only
requirement is to implement the functions, as specified by the interface
procedures. The switch operating system provides a basic layer that
supports both the call processing utilities layer and the options.
A typical module consists of a procedural interface, and a number of
implementation sections (see figure 2–1). The implementation sections
contain data declarations, code for procedures declared in the interface, and
additional procedures. Interface procedures are available outside of the
module but data and code declared in the implementation sections are
private to the module and are not accessible from outside it. The interface
and all implementation sections are separately compiled. The design
process used for the DMS-100 Family software consists of two steps:
• The subdivision of a problem into a number of modules, a specification
of the interface of each module.
• The actual implementation and testing of each module.

DMS-100 International Technical Specification BCS40i and up

2–6 Software engineering

Figure 2–1
Internal structure of a module

Interface

Implementation
section

Implementation Implementation Implementation

section section section

As part of the module specification, the interfaces are written in PROTEL

language and compiled. Several modules, then, may be implemented in
parallel. All uses of the pre-compiled interfaces are verified by the type
checker as the implementation sections are coded and compiled. Separate
tools for checking intermodule references are not required. The PROTEL
module structure encourages a hierarchical, or layered, system structure,
where high level modules (for example, call processing phases) make use of
lower level modules (such as, the operating system nucleus).
PROTEL
The DMS-100 Family software is written in the Procedure Oriented Type
Enforcing Language (PROTEL). Any time-critical or maintenance
operations not suited to PROTEL implementation are programmed directly
in firmware. The DMS-100 Family object code is stack oriented, allowing
an extremely compact object code to be generated by a relatively simple
compiler, without the need for difficult global optimization. PROTEL is a
block structured language which maps well onto the stack run-time
environment. Procedure calls and array indexing (with run time checking of
subscripts) are both fast operations implemented as single instructions.

PLN-5001-001i Standard 02.02 April 1997

 Software engineering 2–7

Major subsystems of DMS-100 Family software

DMS-100 Family central control system (the Central Control on NT-40
based systems, or the DMS-Core on SuperNode-based systems) software
consists of five major subsystems:
• the support operating system (SOS), which manages the various
hardware and software resources of the central control complex. In
addition, SOS implements and controls the multi-tasking environment.
• the database system, which implements the data management functions
in the switch. These include the facilities for data modification orders
(DMOs), pending order file, journal filing, and dump/restore. The
database system also implements facilities for presenting data to the
users in a canonical form, thus allowing changes to be made to data
structures without the need for a reverse compile of programs.
• call processing software
• fault detection and system recovery software, which performs the
automatic detection, diagnosis and recovery of hardware and software
faults. This software also implements facilities for performing manual
testing and maintenance of switch and facility hardware.
• audit software

Support operating system

DMS-100 Family software supports a multitasking environment, in which
activities such as call setup, billing functions, manual and automatic
maintenance activities, and trunk orders, are performed concurrently.
Management of this multitasking environment is done by the support
operating system (SOS). The SOS accomplishes this by supporting the
execution of several programs by appropriately sharing the hardware
resources (for example, CPU time or memory) among them according to
their requirements.
The SOS provides a mechanism called a process which is more precisely
defined than a task. A process can be thought of as the execution of a
program. The code of the program, spanning a number of PROTEL
modules, defines what actions are to be performed and the flow of control
through the code, and execution of these functions constitutes a process. At
any given time, the state of the process is reflected in the point of execution
in the program code and the value of the data manipulated by the program.
This state of a process is remembered in a process control block (PCB)
associate with the process. It describes whether the process is running or
waiting for an event. For waiting processes it has enough information to
resume their execution from the state in which they suspended execution.
The SOS is developed in the form of a layered structure (figure 2–2). At the
base is the nucleus; above it are other subsystems such as the log system, I/O
system and file system. This layered structure allows more sophisticated

DMS-100 International Technical Specification BCS40i and up

2–8 Software engineering

facilities to make use of the more primitive. For example, once the ability to
communicate with a terminal has been implemented in the I/O system, the
file system procedures for reading or writing data can use this facility as a
primitive without being involved in the actual implementation of that
function.
Figure 2–2
Support operating system (SOS)

Application software

Command interpreter

Program loader

File system

I/O system

Nucleus

The following facilities are provided by the SOS:

Storage allocator
The storage allocator provides facilities for allocating and de-allocating
segments of memory out of the program or data stores. On an allocation
request by any user, the storage allocator allocates the requested amount of
store from the available store using the first-fit method. On de-allocation,
the storage is returned to available store thereby becoming available for
reallocation on a first-fit basis again. In order to minimize the problem of
store fragmentation, the storage allocator will merge the deallocated store
areas if they are found to be contiguous. The store fragmentation is further
minimized by requiring users to request store allocation/de-allocation in
some integral units of store required for an entity.

PLN-5001-001i Standard 02.02 April 1997

 Software engineering 2–9

Directory system
The directory system provides a mapping between character strings and
unique integers in a certain range.
Pool allocator
The pool allocator provides facilities for allocating and de-allocating pools
of storage out of which items of only a perspective type may be allocated.
The use of a pool allocator reduces the memory overhead as compared to
allocating individual items using the storage allocator. In order to minimize
the blocking of processes requesting items from the same pool, the size of
the pool is determined (by the user module and supplied to pool allocator as
a parameter) on the basis of the type and usage of a particular resource to be
allocated from the pool. However, if blocking may still occur, it is resolved
by the usage of another facility in SOS, called the flag system which is
described below.
Scheduler
The scheduler is responsible for sharing the CPU among all the processes in
the system. This allocation is done on the basis of the priority assigned to
each process, as well as the availability of processes to run as they wait for
certain events and as these events take place.
Timing facilities
Timing facilities track the progress of real-time and are used to time running
processes as well as processes waiting for timed events.
Message system
The message system is used for inter-process communication. Information
is transferred by the sending process, posting the information (called a letter)
on a mail box, and the receiving process retrieving the information from the
mail box. The receiver is delayed appropriately should it attempt to retrieve
a letter before it has been posted.
Synchronization primitives
Synchronization primitives regulate access to shared data by several
processes to prevent the data from getting scrambled due to unregulated read
and write attempts. They are also used to control the allocation and release
of finite resources, by tracking the number of available resource units.
Log system
When a software subsystem detects an event that it wants to report to the
outside world, it may compose a report describing the event, and pass it to
the log system which stores it in memory for later retrieval, or output it
immediately to one or more output devices.

DMS-100 International Technical Specification BCS40i and up

2–10 Software engineering

Input/output (I/O) system

The DMS-100 Family I/O system software handles communication between
all peripheral devices in the switch (for example, network modules, trunk
modules, or tape drives) and software using those devices (call processing,
maintenance, file system software). The I/O system is concerned only with
the transmission of information between the central control subsystem (the
Central Control on NT-40 based systems, or the DMS-Core on
SuperNode-based systems) and peripherals rather than with the information
itself.
Note: For the remainder of this section, the central messaging subsystem
is referred to as the Central Message Controller (CMC), and the central
control subsystem is referred to as the central control CC).

CC to peripheral messages
As required, CC software sends an outgoing message to a device:
• a call process telling a network module to establish a connection
• a command interpreter (CI) process sending a line of output to a terminal
(via a device controller)
• a maintenance subsystem requesting a trunk module to perform a
self-diagnostic test.
The affected software composes the appropriate message and invokes the
I/O system to transmit that message to a particular peripheral device,
referred to internally as a node. The I/O system selects a route to that node
from its route-table, and then passes the message to the CMC, instructing it
to send the message via the selected route.
If both CMCs are unavailable (when they are busy sending other messages),
the output request is placed in a queue and the I/O system sends the message
when a CMC becomes available.
The transmission across the CPU-CMC nodes is interrupt driven, that is,
when the outgoing message buffer of a CMC is empty, it posts an interrupt
for the CPU by setting an outgoing message buffer empty (OMBE) bit in a
four-bit interrupt register. The interrupt is handled by the CMC interrupt
handler in the I/O system. The CMC interrupt handler would then release
the next queued message into the outgoing message buffer of the CMC
posting the interrupt.
From the CMC outwards, the transmission of messages between any two
nodes is regulated by an internal messaging protocol. The sending node first
transmits a control byte “may I send” (MIS) to the receiving node. The
receiving node responds by returning a control byte “send”. If received in
time, the sender transmits the message followed by the checksum over all
the bytes sent. The checksum is recalculated by the receiver and compared

PLN-5001-001i Standard 02.02 April 1997

 Software engineering 2–11

with the checksum actually received. If checksums agree, a positive

acknowledgment (PACK) is returned to the sender. Otherwise, a negative
acknowledgment (NACK) is returned. The receipt of a first NACK by the
sender results in it retrying the message. If a NACK is received a second
time, the message is bounced back to the CC which normally attempts to
retransmit via the other plane.
Peripheral to CC messages
There are two occasions when the CC software will expect a message from a
peripheral device:
• a terminal controller informing a CI process that the output is completed
• a trunk module reporting seizure on a trunk, or digits received on an
incoming trunk, or results of a test.
The software in question informs the I/O system that it is expecting a
message from a specific node. This is done by one of two methods:
• supplying a procedure (an “input handler”) that the I/O system will call
whenever it receives an incoming message
• requesting that all incoming messages from the node be placed in SOS
messages and sent to a particular mailbox.
When the CMC has an incoming message to pass to the CC, it posts an
interrupt for the CPU by setting an incoming message buffer full (IMBF) bit
in its interrupt register. The interrupt is handled by the CMC interrupt
handler procedure in the I/O system as follows:
• calls the input handler
• places the message in a SOS mailbox
• discards the message, if neither of the above alternatives was requested
by the CC software
Additional I/O software functions
In addition to handling the transmission of incoming and outgoing messages,
the I/O system performs six functions:
• maintains node and link (communication paths between nodes)
configurations.
• allocates message buffers.
• maintains available routes to each node.
• handles message-transmission error reports generated by nodes. As part
of a pre-specified message format, there is an error-byte reserved for
recording any problems encountered by the message during its journey.
The I/O system analyzes the error byte and invokes the appropriate
maintenance subsystem to perform tests on the affected node/link.

DMS-100 International Technical Specification BCS40i and up

2–12 Software engineering

• times non first-time return-to-service attempts on nodes and links.

• audits node and link status, I/O routes, and CMC buffers
File system
The file system supports standardized, device independent procedures for
creating, opening and closing files for reading data from them or writing
data to them. It is designed as a gate module containing various generic
procedures for performing the above mentioned functions. The device
dependent code for these functions is developed in the form of various
agency modules which become bound to the module at run time.
The file system of SOS provides facilities that allow for the input and output
of text or binary data on a wide range of computer peripherals such as visual
display units, hard copy terminals, magnetic tapes, magnetic disks and line
printers. Five operations are supported by the DMS-100 Family file system:
• creating a new file on a specific device
• opening an existing file
• putting a record on a file
• getting a record from a file
• closing a previously opened file.

The file system maintains information about all devices that are supported as
well as all files in the system. For each device, the location of the physical
file system procedure supporting it is kept. Each file has specific
information in a file control block:
• device type
• file name
• file ID
• file attributes
• access attributes (specify whether access is sequential or random, and
whether it is for reading or writing).
In addition to providing the ability to perform a file operation on any one of
the devices supported, the structure of the file system allows for the addition
of a new physical device to the system without having to make any changes
to the logical physical system. The device dependent module for the new
device is designed as an agency, compiled, linked and loaded into the switch.
As soon as the new module is run, it calls on a special procedure in the gate
(the logical file system), and passes it the addresses of the procedures for
performing file operations on the new device. The logical file system
records the new addresses in its table, and thereby enables itself to perform
file operations on the newly added device.

PLN-5001-001i Standard 02.02 April 1997

 Software engineering 2–13

The structure of the DMS-100 Family file system is shown in figure 2–3.
As shown, the file system is structured as a logical file system module that
supports procedures for all the operations described above and which acts as
a gate module to device dependant modules called the physical file system.
The device dependent modules interact with the devices to perform the
desired function.
Figure 2–3
Physical devices supported by the file system

Users of the file system

Logical file system

(module FILESYS)

The file system

Physical Physical Physical

file file file
system for system for system for
magnetic disk NMI
tape terminal

A file system operation required by a process is performed by calling a

logical file system procedure and specifying the device or file ID as a
parameter. Based on the device, an appropriate physical file system
procedure is selected to perform the desired operation on the specified
device.
Internally, the logical file system maintains a table of addresses of
procedures in the various device dependent modules which it uses to select
an appropriate physical file system procedure at run-time. These addresses
are supplied to it by the device dependent modules at the time of their
initialization.

DMS-100 International Technical Specification BCS40i and up

2–14 Software engineering

Command interpreter
The command interpreter (CI) of the operating system performs the input
function for the man-machine interface to the switch (MAP). It provides a
facility for reading and interpreting user commands and taking appropriate
actions. It reads lines typed at a MAP, analyzes them, invokes command
programs as needed, and evaluates the parameters required by these
commands.
Program loader
The program loader is used to load, modify, or unload programs and
program increments.
Flag system
In DMS-100 Family systems, the use of exhaustible system resources, such
as mailboxes, processes, or MF receivers, is controlled through the use of
flags. A flag associated with a resource indicates the number of items of
that resource are in use or in demand. Three facilities are provided by the
flag system:
• time-outs to prevent blocking or deadlock
• non-busy waiting
• first-come-first-served service of waiting processes.

DMS-100 family database system and software

The DMS-100 Family database system software is based on a relational
database model, such that all data is viewed as a set of simple tables. These
tables are independent of the actual physical data structures used by the call
processing software. These internal data tables, although closely related to
the external view of customer service records and office configuration data
provided by the table editor and associated software, are independent of the
service order command language, office record print formats, and other
operational features of the service order software.
In order to satisfy the various user requirements (both internal and external),
four different data schemas are implemented in the DMS-100 Family
database system, as shown in figure 2–4 on page 2–15:
The physical schema corresponds to the actual physical structure of
data. It is at a very low level and is described by descriptors, segmented
store, or digitators.

PLN-5001-001i Standard 02.02 April 1997

 Software engineering 2–15

Figure 2–4
Logical and physical tables

A B C D

Logical
table Key = k a b c d

F (key) d

A B C

Key = k Procedure to
calculate value d

a b c

Physical tables

Protected store Unprotected store

The internal schema corresponds to a view of the data in which various

users can access the data in a common way via a single set of read/write
procedures. The data, at this level, is seen as organized in the form of flat
tables. Each row in the table consists of a number of fields, the first of
which is an index. The index identifies a particular row in a table and
provides sufficient information to determine the actual physical storage
location of data. The main difference between this and the next level (the
“logical schema”) is that the information about the relative order of rows (or
tuples) in a table is not remembered at this level.

DMS-100 International Technical Specification BCS40i and up

2–16 Software engineering

The logical schema provides a higher-level view of data. The data at this
level is presented to the users in a canonical form regardless of the actual
internal storage mechanism used. The data is once again seen as residing in
a number of rows, referred to as logical tuples, and a number of columns
identifying fields of the tuples. The first field of the tuple is a key which
uniquely identifies that tuple.
The external or customer schema provides the end-user view of data. The
data is represented in the character form, rather than the binary form used at
the logical schema level. Users at this level are provided with a number of
commands for making various queries as well as manipulating data.
Figure 2–5 on page 2–17 shows the relationship of various software modules
which together constitute the DMS-100 Family database system. As shown,
these utilities build a layered structure whereby each level uses the facilities
provided by the lower level.

PLN-5001-001i Standard 02.02 April 1997

 Software engineering 2–17

Figure 2–5
DMS-100 database system

Customer schema
End Table editor Formatter
users

Logical schema
Data-admin Logical database Key mapping facility
users utility

Agencies, Internal database Internal schema

etc. utility

Agencies Physical schema

Read, write Read, write

write-nil write-nil
procedures procedures
Read, write
procedures

Physical size

Starting at the bottom of the figure, the time critical agencies access the data
directly at the physical schema level. These agencies have complete
knowledge of the actual structure of data, in fact these agencies have defined
this set of data using the most efficient storage mechanisms they deemed fit
in each case.
At the next higher level, an internal database utility is provided to serve as a
procedural interface for user modules at this level. This module performs
the mapping of data from the physical view of data to the internal view of
the same. Any agency wishing to make its data known to the users at the

DMS-100 International Technical Specification BCS40i and up

2–18 Software engineering

internal level defines the internal view, provides the read, write and
write-nil-tuple procedures for mapping, and binds the same to the
internal-database gate module.
At the logical schema level, a logical database utility performs mapping
between the logical view of data and the internal view of data. At this level,
ordering information about the tuples is retained (key-mapping facility).
Therefore, requests such as “get the first tuple” or “delete the next tuple” can
be serviced at this level.
At the highest level, the mapping between the external and the logical
schemas is provided by the table editor. A very powerful set of table
manipulation commands is also implemented within the table editor. The
formatter provides mapping between the external representation and the
internal (or PROTEL) representation of data. Finally, there is the data
dictionary module, which supports a data dictionary embodying information
about all the data types in the system.
Call processing applications software
Call processing applications software handles the functions that are specific
to each type of call processing agent or to each type of call processing agent
or to each type of call.
Most call processing applications are implemented in standard call
processing applications architecture. Custom calling features that cannot be
implemented easily in standard architecture are implemented in the Feature
Processing Environment.
The standard call processing applications software has a hierarchical,
layered structure. The elements of the structure are classes of procedures.
Within a class, all of the procedures are functionally similar. Each
procedure within a class is tailored to the logical and physical characteristics
of a particular agent or type of call. All the procedures required to support
call processing functions for a type of agent or type of call can be considered
as aspect.
The general nature of the structure is the same for all calls, but the details of
the structure depend on the agents involved and the type of call. At the top
level of the hierarchy, the starter procedure controls the flow of the call,
based on the message being processed, the call state and the type of agent or
type of call.
The second level of the hierarchy consists of a set of processor procedures.
Each processor controls an individual transaction or a set of closely related
transactions.

PLN-5001-001i Standard 02.02 April 1997

 Software engineering 2–19

The remaining levels of the hierarchy are composed of function and

supervisors. These procedures perform a variety of call processing tasks
under the control of processors.
The procedures at each level of the hierarchy communicate results to the
procedures at higher levels by means of return codes. Procedures at all
levels have read/write access o the contents of the Call Condense Block
(CCB), the Call Data Block (CDB), the Extended Call Condense Block
(ECCB), and extension blocks.
Call processing applications software is table-driven, invoking the required
procedures from procedure tables that are indexed by type of agent or by
type of call.
Call processing procedure tables may be indexed by call processing call
processing (CP) selector, by thread, or by cross thread:
CP selectors group agents by broad physical and logical characteristics
(for example, lines, trunks, receivers). CP selectors are used to access
procedures that involve only one agent. The CP selector is part of the Call
Processing Identifier (CPID), which is derived from the Terminal Identifier
(TID) of a terminal.
Threads of call processing agents distinguish their physical and logical
characteristics more finely than CP selectors (for example, Dial Pulse [DP]
line, Dual-Tone Multifrequency [DTMF]) line, coin line, DP trunk,
Multi-frequency [MF] trunk). The thread is part of the data stored for each
agent in the call processing database.Threads are used to access procedures
that involve only one agent.
Crossthreads are used to categorize connections (for example,
line-to-line, line-to-trunk). The crossthread for each call is determined after
the terminating agent is selected, based on the threads of the originating and
terminating agents. Crossthreads are used to access procedures that involve
both agents. Some thread and crossthread values are assigned to custom
calling features and other special functions.
Starters
Starter procedures from the first level of the call processing applications
software hierarchy. Starters control the flow of the call from origination
through to disconnect.
Processors
Processors control individual transactions or sets of closely related
transactions. The selectors for the processor gate are the class of processor
and the thread or crossthread. Processors reside at the second level of the
call processing applications software hierarchy, except for cross processors,

DMS-100 International Technical Specification BCS40i and up

2–20 Software engineering

which reside at the third level. There are several classes of processor
procedures:
Setup processors coordinate the setup phase of the call. The setup phase
of the call includes all the transactions from origination through to signaling
the terminating agent. In most cases, the setup processor calculates the
cross-thread of the call from the matrix-to-crossthread table.
When the originating agent is a trunk, part of the usual function of the setup
processor is performed by the originating allocator. The trunk originating
allocator coordinates origination, digit collection and translation: the trunk
setup processor coordinates the selection and signaling of the terminating
agent. Setup processors are selected by the thread of the originating agent
and are invoked by starters.
Cross processors establish the connection between the originating and
terminating agents. If a receiver is involved in the call, the cross processor
releases it. If a DTMF sender is required for outpulsing, the cross processor
obtains a DTMF sender and sends messages to the Network Modules (NM)
and Peripheral Modules (PM), directing them to connect a speech path
between the originator and the DTMF sender through the NMs. Cross
processors are selected by cross thread and are invoked by setup processors.
Cross processors control only a portion of a transaction.
Recall processors process answer and flash messages. They record
information for billing and route flash messages to custom calling features
(for example, three-way calling, call waiting, etc). Recall processors are
invoked by starters. They are selected by thread if only one agent is
involved in the call, or by crossthread if two agents are involved.
Disconnect processors take down connections and complete the
recording of billing information disconnect processors are invoked by
starters. They are selected by thread if only one agent is involved in the call,
or by crossthread if two agents are involved.
Error processors take down calls and idle the agents involved when
errors occur. Error processors are invoked by starters. They are selected by
thread if only one agent is involved in the call, or by cross thread if two
agents are involved.
Processors continue to execute until control is transferred to another
processor, or until the call is completed or condensed. Processor invoke
functions and supervisors to perform their call processing tasks.
Functions
Functions usually reside at the third or lower levels of the call processing
applications software hierarchy. Functions are invoked by processors to
perform a variety of call processing tasks. Functions are gated through

PLN-5001-001i Standard 02.02 April 1997

 Software engineering 2–21

tables of procedure variables and are selected by thread or CP selector.

There are several classes of function procedures:
Allocators assign an agent to a call as the originator or terminator. The
agent’s data is copied from the database into the Call Condenser Block
(CCB) for use by subsequent call processing procedures. When the
originating agent is a trunk, the originating allocator resides at the second
level of the hierarchy. The trunk originating allocator performs part of the
function usually performed by a setup processor; it coordinates origination,
digit collection and translation.Originating allocators are invoked by setup
processors when the originator is a line, or by a starters when the originator
is a trunk. Terminating allocators are invoked by cross processors.
Originating allocators are selected by the thread of the originating agent and
terminating allocators are selected by the thread of the terminating agent.
Loaders transfer the collected digits from the incoming message to the
translation area of the CCB. Some loaders do simple pre-processing of
digits messages. Loaders are invoked by setup processors when the
originator is a line, and by the originating allocators when the originator is a
trunk. Loaders are selected by the thread of the originating agent.
Translators analyze the translation database to determine the call’s
destination, based on the digits collected and the originator’s attributes.
Translators are invoked by setup processors when the originator is a line and
by originating allocators when the originator is a trunk. Translators are
selected by the thread of the originating agent.
Identifiers initiate recording of billing information. Identifiers are invoked
by setup processors when the originator is a line. Identifiers are not used by
standard trunks since billing is done at another office. Identifiers are
selected by the thread of the originating agent.
Routers test the availability of agents and route calls, based on the results
of translation. Routers are invoked by setup processors. Routing procedures
are selected by a routing selector contained in the translation result.
Terminators select a terminating agent from a group of possible
terminators (for example, trunk group, line hunt group, call forwarding).
Terminators are invoked by routers and are selected by the CP selector of the
terminating agent.
Outpulsers compose and send messages to perform outpulsing on trunks.
Outpulsers perform the function of signaling the terminating agent when the
terminator is a trunk. Outpulsers are invoked by terminating allocators and
are selected by the thread of the terminating agent.
Idlers idle agents when errors occur. Idlers are invoked by error processors
or trap occurrences.

DMS-100 International Technical Specification BCS40i and up

2–22 Software engineering

De-allocators de-allocate agents from calls. De-allocators are invoked by

disconnect processors and are selected by the thread of the agent being
de-allocated.
Spillers compose and send messages to outpulse the calling number so that
billing information can be recorded in the destination office. Spillers are
invoked by recall processors and are selected by the thread of the
terminating agent.
Billers perform special billing functions for message rate lines, coin lines,
INWATS lines and PBX trunks. Billers are invoked by recall or disconnect
processors, and are selected by the thread of the originating or terminating
agent.
Note: Functions continue to execute until they return control to the
invoking processor.

Supervisors
Supervisors are invoked by cross processors to perform some of the
functions associated with establishing the telephony connection and
signaling the terminating agent. Supervisors compose and send messages,
directing PMs to perform the following operations:
• Give audible ringback tone to the originator
• If the terminator is a line, apply physical ringing to the terminator
• Transmit and detect integrity for the duration of a call
• Report on-hook or flash signals from the agents involved in a call;
report answer signals also, if required.
Supervisors are gated through a table of procedure variables and are selected
by crossthread. Supervisors continue to execute until they return control to
the invoking processor.
Fault detection and system recovery
In order to carry the levels of traffic demanded of modern switching
systems, the DMS-100 Family system employs an architecture that
distributes the control functions for call processing to several control
centers. To provide the reliability demanded of today’s switching systems
(working non-stop 24 hours a day), these control centers are made of the
most reliable components and arranged in a hierarchy with clearly defined
responsibilities for fault detection and system recovery. Component
redundancy has been applied to this structure in a selective, cost effective
manner, both to the control centers themselves and the communication links
between them, permitting faults in the system to be readily diagnosed.

PLN-5001-001i Standard 02.02 April 1997

 Software engineering 2–23

A DMS-100 Family switching system consists of the following major

subsystems:
• central control subsystem – the Central Control (CC) on NT40-based
systems, or the DMS-Core on SuperNode-based systems
• central messaging subsystem – the Central Message Controller (CMC)
on NT40-based systems, or the DMS-Bus on SuperNode-based systems
• switching network
• input/output equipment
• peripheral modules

Figure 2–6 illustrates the major subsystems of an NT40-based switching

system.
The central control (CC) has overall responsibility for the system sanity.
Sanity of the CC itself is ensured by operating the duplicated CPUs in a
matched mode; in this mode each CPU executes identical steps and
compares its results with those of the other processor after every step. The
CMCs operate in a load sharing mode and are checked for correct operation
by the message protocol itself and by hardware and software mechanisms
within the CPU.

The network subsystem, consisting of up to 32 network modules, is arranged

in two identical planes to provide redundancy.
The peripheral module subsystem serves as the interface between the
DMS-100 Family office and the lines and trunks served by the switch. The
peripheral modules are connected to the network planes by a system of links
that carry time multiplexed speech signals and control messages. The
control message system enables the network and peripheral modules to carry
out the central office switching functions as directed by the CC.
Redundancy
In DMS-100 Family systems, the concept of redundancy has been applied in
all major equipment areas: the CC, the network subsystems, and peripheral
control sections have been fully duplicated. Redundant message paths
between the modules have also been provided since faulty links would
otherwise prevent the system from operating satisfactorily. Supporting this
structure are hardware and software mechanisms (called the DMS-100
Family maintenance subsystems) that detect faults when they occur and
manage the system reconfiguration and recovery.
Besides being fully duplicated, the modules in the CC contain numerous
internal fault detection mechanisms to check every step of the CC’s
operation. The rest of the DMS-100 Family system depends on this secure
control for reconfiguration and recovery from failures. Either of the
duplicated network planes is capable of carrying the entire load of the switch

DMS-100 International Technical Specification BCS40i and up

2–24 Software engineering

in the event of a fault in one of them. Faults in the network switching matrix
are detected by peripheral modules. The network message controllers are
checked by both the peripheral modules and the CC.
Figure 2–6
DMS-100 family (NT40) – major subsystems
FW-31181

Lines Digital trunks

Peripheral
subsystem ILCM ILCM

ILGC IDTC

I/O subsystem Network subsystem I/O subsystem

I/O I/O
Network Network
controller 0 controller1
modules 0–31 modules 0–31
plane 0 plane 0

Central
control
MAP MAP

Data CMC 0 CMC 1 Data

Tape 1 store 0 store 1

Tape 3

Tape 2

Prog CPC 0 CPC 1 Prog

Disk store 0 store 1 Disk

PLN-5001-001i Standard 02.02 April 1997

 Software engineering 2–25

The peripheral module control area is fully duplicated and functions in a

“hot standby” mode of operation. Internal software mechanisms are used to
detect faults. When a fault is detected in the control area of the peripheral
(when the standby unit assumes control and becomes active) an activity
switch is performed.
The fault tolerance of the control message system is achieved by providing
redundant links. The message protocol automatically reroutes a message
from a faulty link to a sound one when necessary. In addition, a unique reset
message brings peripheral and network module controllers to a known initial
state in the event of a failure.
Fault detection and management
To manage the redundant topology of the overall system, each subsystem
contains fault detection mechanisms to drive the software that reconfigures
the system in the event of a failure. The CC uses matching between the
processors and a trap system that detects faults independently in each
processor. Each CPU matches its own results with those of its mate on the
completion of each processor micro-cycle. Transmission of data port
information between processors is provided by a mate communication bus
carrying data with parity. For the matching operation to work, the two CPUs
are tightly synchronized. Both processors select the same clock source,
which ensures simultaneous completion of micro-cycles. In addition, each
processor waits until the accesses to both stores have finished before
proceeding to the next micro-cycle. This automatically takes into account
delays introduced by asynchronous refreshing of the dynamic memories
used in the stores.
If the matching logic in either processor detects a mismatch of results, it
triggers a processor interrupt. This induces a branch to firmware that runs a
self test sequence called a maze to check basic CPU operation. On
successful completion of the maze, control is transferred from the firmware
to software, which invokes the appropriate recovery procedures based on
status information exchanged between the CPUs. This status is provided by
a mate communication register and a fault indication register (FIR), both of
which can be read directly by the mate processor.
The fault indication register is a readout of the trap circuits that operate
independently in each processor. These trap circuits detect faults such as
parity errors, address range violations, or timeouts, and set flags in the FIR
upon the detection of any such faults. A setting of any of the flags causes a
trap-level interrupt and simultaneous capture of the addresses on both the
program and data ports to aid fault diagnosis. Hardware faults that normally
generate both mismatch and trap interrupts are handled by the mismatch
mechanism. In matched operation, a trap interrupt generated without an
accompanying mismatch interrupt indicates a software fault. Trap level

DMS-100 International Technical Specification BCS40i and up

2–26 Software engineering

processing is handled primarily by software that attempts to minimize the

effect of the fault on overall system operation.
In addition to the fault tolerant facilities provided in the CPU, several
features under software control are incorporated in the memory module to
enhance memory integrity and fault tolerance. For example, the memory is
subdivided into 16 kilobyte blocks, each protected by a bit contained in a
write-protect register within the memory controller. This bit acts as a key to
each block and is accessible only to certain system operating procedures.
Because the memories contain the majority of the central control circuit
packs, each CC memory module includes an extra memory card. This card
may be configured by software to respond to the address space of any of the
other cards in the module. With this technique a faulty memory module is
automatically restored to operation by isolating the faulty card from the
system and switching in the spare. The new memory card is updated from
the mate’s memory and the CC returns to matched operation.
The CMCs, like the CPUs and memories, are duplicated, but unlike the
CPUs, they operate in a load-sharing mode and use fault detection
techniques based on internally housed circuits. These monitor circuits
consist mainly of timers and other logical checks to ensure that the protocol
on each message is correctly followed. The detection of a fault sets flags in
a register similar to the CPUs fault indicator registers and causes an interrupt
to the CPUs.
Although redundant paths are available between the CC and any peripheral
module, messages are sent on one route at a time. Should a failure occur,
another route is tried only after the first attempt is completed and declared a
failure. In order to ensure that all paths are exercised, the message routing
software has a choice of two different routes to each node which are
calculated to include all links and intermediate (that is, network) modules in
the system. Furthermore, each module in the system has sufficient
intelligence to determine whether a message sent to it obeys the protocol. If
it doesn’t, the module closes the port over which the message arrived. This
action is taken on the assumption that the sending module developed a fault.
The CC can diagnose the problem and still communicate with the module
via the other good link.
Variations
A variation of this link control strategy is required between the CMCs and
CPUs. Although the two CPUs operate synchronously and therefore appear
to the rest of the system as a single entity, only one CPU at a time is
designated “active” and can actually send messages to the CMCs and hence
to the system. Both CPUs always receive messages from the system. This
mechanism of “activity” prevents an “insane” processor from corrupting the
rest of the system by sending nonsense messages to it. An active processor

PLN-5001-001i Standard 02.02 April 1997

 Software engineering 2–27

is also capable of resetting its inactive mate when required. The activity
state is determined by a single flip-flop that is cross-coupled between the
CPUs; it is designed with a minimum of circuitry in order to reduce its own
probability of failure. To facilitate system maintenance, a processor can
manually be forced into the inactive state, provided that its mate is fault-free.
To ensure integrity of the communication between the CC and the operator
environment, the I/O controllers use two fault detection mechanisms. One is
the message system protocol, and the other is a system of self checks
incorporated in the I/O and device controller firmware. It is possible that
I/O devices of a similar type may be assigned different functions. Should
one fail, its function may be reassigned to another similar device. This can
be done either automatically or manually, depending on the importance of its
function. For example, toll billing tapes may be reassigned by software,
certain display terminals may not.
The interdependence of network and peripheral fault detection mechanisms
is shown in figure 2–7, which identifies the modules associated with every
call. The fault detection mechanism between modules is included in the data
format of the speech links. Two additional bits appended to each 8-bit
speech sample are assigned to channel supervision messages and parity.
Although they provide fault coverage of link and network speech paths, they
are generated and checked in the peripheral modules.
As shown in figure 2–7 the network planes are duplicated to facilitate fault
recovery; outputs from both planes appear at each peripheral. Conversely,
each peripheral feeds both planes simultaneously with the same signal. In
the event of a fault in one of the network planes, the peripheral module that
detects the fault simply elects to receive the call from the corresponding
network module in the other plane.
Providing network plane selection on a per-call basis offers a significant
increase in the resilience of the system to multiple faults. Distributing the
fault detection mechanisms to all the peripheral modules provides smooth
recovery from simple but far-reaching faults such as network power failures.
A network module can support approximately 1,900 calls at any one time,
but if that module fails, each of the several peripheral modules connected to
it is required to recover only their own calls. Operating independently, these
peripheral modules reconfigure the system to use the remaining good
network plane for the calls that require it. (It is the simultaneous
transmission of speech and supervision signals on both planes that allow this
reconfiguration of each call path). Once the reconfiguration has been
accomplished and service restored, the peripheral modules then report the
problem to the CC for maintenance.
If any call encounters a failure in the second network plane, the peripheral
that detected the failure would not switch back to the first plane. Instead, it

DMS-100 International Technical Specification BCS40i and up

2–28 Software engineering

would inform the CC call processing software that the path initially
specified for the call could not be sustained.
In addition to detecting network faults, the parity and supervision
mechanisms are also used to detect faults in links and in the peripheral
modules themselves. In these instances it is the other peripheral associated
with a call that reports a difficulty to the CC, which then takes appropriate
action.
Figure 2–7
Network and peripheral fault detection

Peripheral
1

Speech and Network

parity module 1
generator plane 0

Supervision

To line or
trunk circuit
parity 1

Supervision
receive and
parity check

Network
Speech Plane
module 1
selector
plane 1

PLN-5001-001i Standard 02.02 April 1997

 Software engineering 2–29

As well as relying on other modules for fault detection, every network and
peripheral module includes basic fault detection an location mechanisms
unique to itself. For example, all modules contain sanity timers, which are
continually reset by correct cyclical operation of the controller. Should the
controller software enter a tight loop for any reason, the timer expires and
causes the controller to enter a reset state. This state is detected by the next
module upstream towards the CC, which informs the central control of the
reset condition. These sanity timers ensure that faulty peripheral and
network modules can never become blind to messages arriving from the CC.
The fact that the peripheral and network controllers reside in a small number
of circuit packs inherently simplifies the location of faults. In the network
subsystem up to eight circuit packs may be involved in the speech path of a
call, four in each module as shown in figure 2–8. Faults detected during a
call by the parity or supervision mechanisms can be pinpointed by a
system-generated test code. This code is automatically inserted into the
speech path and monitored at certain strategic points. An absent or incorrect
code at any point identifies the fault location.
Figure 2–8
Network fault detection

Network module

Switching matrix

Network Incoming Outgoing Network

From interface crosspoint crosspoint interface To next
peripheral card card card card network
module

Hardware test
facility

Multi- Detector
plexer
Failure
indication
(to control)

Should a peripheral module detect a fault on a speech path, internal tests to

determine the location of the fault are conducted in each of the two network

DMS-100 International Technical Specification BCS40i and up

2–30 Software engineering

modules involved. A hardware facility built into each network module

inserts a test code into the speech path in front of the network interface card,
and monitors the signal after it passes through each of the four module cards
involved. In this way a faulty card can be identified for subsequent repair.
Message system integrity
The procedures to diagnose fault conditions and effect system recovery
reside primarily in the CC. Between the CC and other subsystems redundant
paths have been provided; each is equipped with a protocol that can manage
fault detection and recovery within the message system itself.
The message protocol is designed to detect transmission and equipment
failures and to permit the rerouting of messages around a failed module or
link. Prior to transferring the message itself, the sender of the message
initiates a handshake to ensure the receiver is in a condition to receive the
message. On confirming that the receiver is ready, the sender forwards the
message, which includes a checksum over the data and header fields. The
receiver verifies the checksum and if it is incorrect, requests a
re-transmission by returning a negative acknowledgement of the message. If
the second transmission attempt also fails, or if the receiver could not accept
the message in the first place, the sender autonomously tries another route.
If one is unavailable the sender sets an error byte in the message header and
returns the message to the module from which it came.
System re-initialization
System re-initialization or restarts are initiated whenever the internal checks
built into the DMS-100 Family central control hardware and software
determine that the system is behaving abnormally. These checks are
extensive in nature and serve to maintain or restore a stable call processing
environment. Six activities can cause system restarts:
• traps in critical system programs
• death of critical system process(es)
• sanity time-out
• operating system process queue empty
• call data block queue corrupt
• call condense block states inconsistent.

There are three types of system restarts:

• warm restart
This is the first level of restart and is entered for the less severe detected
abnormalities. Calls being processed are cleared but existing connected
calls are retained. Data such as network connection maps, billing data,
and error logs are retained.
• cold restart

PLN-5001-001i Standard 02.02 April 1997

 Software engineering 2–31

This level of restart is entered directly if the system detects an

abnormality of a severe nature, or is entered after a second warm restart
has failed to resume normal system operation within a three minute time
interval. The second warm restart is initiated whenever the first fails to
establish normal system operation, again within a three minute time
interval. As with a warm restart, calls being processed are lost. In
addition, since network connection maps are cleared and both lines and
trunks are set to the idle state in Central Control on a cold restart,
established calls may be disconnected due to the reuse of network paths
or reuse of terminals as terminators in new calls before original calls
disconnect. LOG system and AMA billing records are retained.
• reload restart
This re-initialization is used after a reload of an office image tape and
can be either manually initiated or caused by an auto-reload. Office
configuration and translation data are overwritten by the office image
tape data. All dynamic data including error logs are cleared.

Examples of system recovery

To illustrate the procedure of tracing a fault and re-configuring the system as
necessary, a sequence of faults will now be applied to the simplified version
shown in figure 2–9. When a fault occurs, five basic steps are executed:
• detection of the fault
• reconfiguration to avoid use of the faulty element
• diagnosis of the fault to a replaceable unit
• replacement of the faulty unit
• return of the previously faulty element to service

Throughout these events, normal system functions must continue unaffected.

DMS-100 International Technical Specification BCS40i and up

2–32 Software engineering

Figure 2–9
Example of system recovery (NT40)

Central Central Input/output

processing message controller
unit 0 controller 0

Network Peripheral
plane 0 module 1

Central Central
processing message Network Peripheral
unit 1 controller 1 plane 1 module 2

The diagram above depicts a DMS switch in routine operation. CPU1 directs the activities of
the switch, sending messages through both CMCs to the sub-systems below. Call connec-
tions are maintained on both network. When CPU 1 sustains a failure, CPU 0 takes over
control of the activities of the switch, and processing continues. A fault in the link between
CMC 0 and the I/O controller requires that messages between the CPU and the controller be
routed exclusively through CMC 1. When the network plane 1 also breaks down, the DMS
switch continues to operate, with network plane 0 handling all call connections.

The first fault considered is a failure in the arithmetic unit of CPU 1, the
active processor in this example. The fault is detected by the matching logic
between the two processors and this generates a mismatch interrupt when
the faulty hardware is used. The two CPUs then automatically run through a
maze sequence located in microstore. CPU 0 successfully completes the
maze, but CPU 1 fails and enters a firmware loop.
After completing the maze, CPU 0 attempts to communicate with CPU 1 but
fails because CPU 1 is held in its loop. The activity switch timer that started
when the mismatch occurred will time-out and force CPU 0 into the active
state. Information for fault diagnosis is stored for subsequent action and
switching control is returned to the interrupted software routine now running
only in CPU 0.
Diagnosis is performed by a craftsperson using the Maintenance and
Administration Position (MAP) to generate a circuit pack replacement list.

PLN-5001-001i Standard 02.02 April 1997

 Software engineering 2–33

Using this list, the faulty CPU is repaired and returned to service by MAP
commands that re-synchronize the CC.
Link faults manifest themselves in various ways such as message time-outs,
invalid control bytes and bad checksums. For this example (see figure 2–9)
a time-out waiting for a message handshake occurs on an incoming message.
The I/O controller closes the link so that messages are no longer routed over
it and then sets an error indication in the message that it sends over the
alternate link.
When the message arrives at the CC, the appropriate maintenance software
is informed of the link failure. It removes the link from service and informs
the I/O routing software that this link is no longer usable. In addition, the
CMC is told to stop scanning the link for incoming messages.
Communication with the I/O controller and devices must now use the
alternate link.
Immediately, and periodically thereafter, the CC tests the out-of-service link
to see whether it can be returned to service. The CC begins this test by
placing the link in a restricted maintenance state that allows only
maintenance traffic to pass over the link. The test is then carried out by
priming the I/O controller and CMC link control functions to accept such
maintenance message. Proper setting of the route bits now ensures that the
message travels over the link and be looped back by the receiving controller.
The normal routing algorithms and automatic rerouting features of the
system are therefore bypassed in this test. If such a test passes, the CMC,
I/O controller, and operating system are informed that the link is again
available for normal message traffic. In this fashion the system recovers
from transient fault conditions.
If the fault is hard, the system will not be able to return the link to service
and maintenance personnel informed via the MAP of the fault. Using MAP
facilities, they identify and replace the faulty component and return it to
service. Normal operations of the switch are unaffected by either the failure
or the repair action.
With both a CPU and a CMC-1 I/O controller link out of service as shown in
figure 2–9, let us assume a connection memory failure in a network module
occurs. As noted earlier, network connections are established in both planes
but the peripheral modules select only one plane from which to receive the
speech samples. Typically half the calls in progress are arbitrarily
completed through the even plane and the remainder through the odd plane.
When the connection memory failure occurs, the peripheral module detects
the loss of the speech path by the message interruption on the supervision
channel associated with the call. The peripheral immediately selects the
other plane to receive speech for that call and generates a maintenance
message to the CC, indicating the channel and link that are experiencing the
problem. The call is sustained in the opposite plane and the subscriber

DMS-100 International Technical Specification BCS40i and up

2–34 Software engineering

remains unaware of the fault. When the fault message arrives in the CC,
information on the bad connection is frozen in software, so that even if the
call is disconnected, the connection can be diagnosed. The diagnosis is
performed, using the test code mechanism previously described, to pin down
the fault to a subsection of the network planes or interconnections.
Upon confirmation of the memory fault, the network module must be
removed from service. All new calls are connected through the good plane
and the message system is reconfigured accordingly.
The CC accomplishes this by updating the routing information, closing the
CMC links to the affected network module and closing the peripheral links
originating in that network module. At this point the detection and
reconfiguration process is complete. The repair and return to service steps
are again accomplished using the MAP. The same test procedures used in
diagnosing the original problem are used to verify the repair. These
examples demonstrate the ability of the DMS-100 Family switch to remain
in operation during a period of major component faults.
System recovery controller software
Automatic recovery capabilities on SuperNode-based DMS-100 Family
switches include the system recovery controller (SRC), a dedicated software
utility which optimizes recovery of system peripherals. When the SRC
detects loss of service on one or more peripherals, it automatically initiates
the appropriate recovery sequence, including reinitialization, software
reload, and return to service.
The SRC will make several attempts to recover a PM if required. With each
subsequent recovery attempt, the SRC performs a more detailed analysis.
Automatic software reload only occurs in the first recovery pass if the
system detects loss or corruption of load.
In addition, in cases where a large group of peripherals require recovery at
the same time (for example, after loss of power), the SRC broadcast-loads
groups of peripheral modules of the same type (see note). The SRC also
ensures that, in the event of a large outage, the effected system elements are
automatically recovered in the most expedient manner, removing the need
for decision-making and manual action from operating company personnel.
Note: Broadcast loading capability is supported on series 2 PMs, such as the
International Digital Trunk Controller (IDTC), International Line Group
Controller (ILGC) and the International Line Concentrating Module (ILCM).
These PMs must be equipped with NT6X45BA (or newer) processor cards to
enable broadcast loading. Older types of peripherals, such as the maintenance
trunk module (MTM) are single-loaded. For detailed information on specific
SRC recovery activities supported for each type of PM, refer to Lines, Trunks
and Peripherals Recovery Procedures, 297-1001-587.

PLN-5001-001i Standard 02.02 April 1997

 Software engineering 2–35

SRC functions
The SRC coordinates the recovery activities of various subsystems outside
of the DMS-Core. These subsystems include the series I and II PMs.
Figure 2–10 shows how the SRC interfaces with the DMS-Core and with the
subsystems.
The SRC performs the following functions:
• Its dependency manager enforces inter-subsystem dependencies. Before
the SRC recovers a PM, the subsystems on which the PM depends must
be operating.
• The group manager groups subsystems together for broadcast-loading.
Common commands are sent to a group of PMs at the same time, instead
of one after another.
• The concurrent activity manager balances the amount of recovery work
against other activities occurring on the switch. The SRC attempts
recovery of as many critical subsystems as the DMS-core operating
system will allow.
• The SRC initiates recovery applications and monitors each step in the
application to ensure that the application completes as quickly as
possible.
Two separate activities are coordinated by the SRC for series II XMS-based
PMs (XPM) and line concentrating modules (LCM):
• system recovery of PM nodes following core restart or core switch of
activity, using the dependency manager
• loading of PM units after a loss of load has been detected by system
maintenance, using the group manager
The only connection between the two activities is that maintenance on a PM
initiated through the dependency manager can lead to the loading of one or
more PM units.
For example, after a total office power outage, the dependency manager
begins to return a PM to service after completion of the reload restart. The
system maintenance task that is performing the return-to-service detects the
loss of load and initiates the reload request for the PM units to the SRC.

DMS-100 International Technical Specification BCS40i and up

2–36 Software engineering

Figure 2–10xxx
System recovery controller
FW-30737

Subsystems

Series I PM Series II PM Enhanced I/O Message

maintenance maintenance network controller switch
maintenance maintenance maintenance

System recovery controller

Dependency manager Group manager Concurrent activity

manager

Database

DMS-core
Switch
operating system

SRC conditions
The following prerequisite conditions must be met for SRC-coordinated
recovery of PMs:
• all equipment must have power
• NT6X45BA or newer processor cards must be installed in series II
XPMs to allow automatic broadcast-loading
• all PM load names (including series I PM loadnames) must be datafilled
in table PMLOADS
Series II XPMs with pre-NT6X45BA control cards are single-loaded rather
than grouped for broadcast-loading.

PLN-5001-001i Standard 02.02 April 1997

 Software engineering 2–37

SRC triggers
The following events trigger the SRC to begin recovery of subsystems if
necessary:
• warm restart of the core
• cold restart of the core
• reload-restart of the core
• loss of load in a PM
• manual RESTART SWACT, ABORT SWACT, or NORESTART
SWACT of the core
Additional SRC triggers to reload series II XMS-based PMs
There are four additional triggers for the SRC to reload series II XPMs:
• the XPM reports a memory parity error during a periodic audit by the
switch operating system
• the ROM/RAM query step in the series II XPM return-to-service task
detects a loss of load
• the failure two times in a row to initialize the series II XPM during a
return-to-service task, indicating that something is wrong with the
software load
• the ROM/RAM query step in the series II XPM system-busy task detects
a loss of load
Core restarts
During a restart, the switch operating system reinitializes itself.
Reinitialization restores both the operating system software and the
subsystems outside the DMS-core to a known, stable state.
A restart of the system includes initialization of the modules in the
DMS-core, initialization of the PMs, and restoration of services. The period
of a restart is the time taken to recover the entire system to the point that all
services are available again. A flashing A1 appears on the reset terminal
interface (RTIF) when initialization of the software on the DMS-core is
complete. The recovery of the entire system continues after the flashing A1
appears.
The following list describes what happens to each PM during each type of
restart:
• A warm restart of the core is the least severe of restarts. XPMs are
audited and generally stay in service during a warm restart. During this
type of restart, calls in progress that have reached the talking state
continue. Calls that have not yet reached the talking state are
disconnected. Any calls that disconnect during the restart are
disconnected after the restart is complete and the billing data is recorded.

DMS-100 International Technical Specification BCS40i and up

2–38 Software engineering

• A cold restart of the core is more severe than a warm restart. XPMs are
audited and generally stay in service during a cold restart. During this
restart, calls in progress that have reached the talking state retain their
connections during the restarts, but they may be disconnected if their
connections are reused by new calls after the restart. There is no record
made of calls in progress during a cold restart and no billing data is
recorded for these calls.
• A reload-restart of the core is the most severe restart. All PMs are
reinitialized during a reload-restart. All calls in progress are dropped,
and billing data for the dropped calls is lost.
Loss of load in a PM
Normally a loss of load occurs when a card (loaded with software) is
removed or the power to a card is interrupted. A PM becomes system busy
when a loss of load occurs. The SRC begins recovery when system
maintenance detects a loss of load.
Manual commands
The SRC reinitializes PMs if any of the manual commands RESTART
SWACT, ABORT SWACT, or NORESTART SWACT are used during an
upgrade of BCS software.
SRC dependency manager
Some recovery actions on objects are dependent on other objects to be in a
particular state to support the action. The dependency manager of the SRC
manages object dependencies using the applicable set of dependencies for
the type of restart. Thus, the SRC dependency manager prevents failure due
to premature starts, and reduces recovery times.
Objects
An object is any entity in the DMS switch. An object can be
• physical, such as an ENET plane, an XPM, an IPML, or a set of lines
• a service, such as line trunk server (LTS) call processing
• software, such as entry code
• an event, such as the initialization of core software

Managing dependencies
The action on the dependent object must not proceed until the object
depended upon is in the required state. The dependency manager ensures
that the dependencies for an action on an object are satisfied before the
action is allowed to proceed.
Dependencies are specified for each action for each object. Examples of
dependencies in DMS include
• one part of the software that must initialize before another

PLN-5001-001i Standard 02.02 April 1997

 Software engineering 2–39

• node initialization (at the PM level) after the DMS-core software

initialization completes and the C-side node returns to service
• data that must be downloaded to a node after other nodes have returned
to service
• recovering a service in one node after other parts of the service in other
nodes have been recovered
A dependency can change when it is needed for one type of recovery but not
for another. For example, an action can have different dependencies in
different restart types. The SRC provides the applications with the means of
indicating which dependencies are applicable.
Broadcast-loading
Broadcast-loading is a bulk action, that is, it can operate on more than one
PM at the same time. Time is saved by performing an action on a group of
PMs rather than on many PMs individually.
Grouping is coordinated by the group manager. PMs are grouped so that one
PM is a “seed” PM. The DMS-core sends messages to the seed PM and the
seed PM forwards the messages to the other PMs in the broadcast chain.
Several criteria are used when PMs are grouped for a bulk action. For
example, when the SRC broadcast-loads to nodes, the following different
groupings can be used by the group manager:
• grouping by the same node type
• grouping by the same load file name
• grouping by the same loading method

Grouping series II XMS-based PMs

The criteria for grouping series II XPMs together for broadcast loading are
• grouping by the load file name
• grouping by the CMR (class modem resource) file name
• grouping by the presence of 6X45BA or higher controller cards

For example, two XPMs that have the same load file name and that have
NT6X45BA controller cards, but have different CMR file names are put into
different groups.
XPM units that cannot be grouped with other XPM units for
broadcast-loading are single-loaded. This can happen if the XPM units do
not have the hardware to support broadcast-loading or if they cannot be
grouped with other units during dynamic grouping. Grouping occurs only
for XPMs that have NT6X45BA or higher controller cards. XPMs that do
not have NT6X45BA or higher controller cards are not grouped with other

DMS-100 International Technical Specification BCS40i and up

2–40 Software engineering

XPMs even if the other XPMs use the same load files. The SRC still
coordinates single-loading for purposes of concurrency management.
Static and dynamic groups
PMs that can be grouped together are identified from datafill, which
specifies their load file names and their hardware configurations. These
groups (called static groups) are maintained automatically over time as the
datafill changes. During recovery, the SRC forms dynamic groups from the
subgroups based on which elements require recovery and availability of
resources to perform the recovery.
Automatic broadcast-loading
Automatic broadcast-loading sends a request to load software to several PMs
simultaneously.
After receiving a request to load a member of a static group, the SRC builds
a dynamic group, using a combination of two methods:
• querying the group members for loss of load using the ROM/RAM query
message (only on XPMs equipped with NT6X45BA or higher controller
cards)
• waiting for autoload requests from the group members over a short
period of time (the autoload requests are submitted after failure to
return-to-service, where the failure is suspected to be due to loss of load
or load corruption)
When a system-busy unit is identified as needing loading, the SRC is
notified. The SRC group manager creates a group of PMs that can be
broadcast-loaded.
When a group is formed, the SRC coordinates the broadcast-loading. If a
PM has only one unit requiring loading, then that PM is dropped from the
group and a regular load request is submitted for the unit. System resources
are saved by using broadcast-loading even when the group consists of only
one PM, because if both units need loading, unit 0 sends the load messages
to unit 1.
Automatic broadcast-loading is reattempted once if a group of PMs is not
recovered. If the second attempt also fails, the SRC attempts to recover the
PMs individually.
Note: Series I PMs do not support broadcast-loading.

PLN-5001-001i Standard 02.02 April 1997

 Software engineering 2–41

Note 3: LCMs that subtend remote cluster controller (RCC) can be

broadcast-loaded only with other LCMs that subtend RCCs. Similarly,
LCMs that subtend line group controller/ line trunk controller
(LGC/LTC) XPMs can be broadcast-loaded only with other LCMs that
subtend LGC/LTC XPMs. LCMs that subtend RCCs and LCMs that in
turn subtend LGC/LTC XPMs cannot be broadcast-loaded together.

Limitation of concurrent load activities

The SRC is used to monitor and control the number of concurrent PM
loading tasks. Although single-loading of XPMs does not use the grouping
capability of the SRC, the SRC still provides coordination in the form of
concurrency management.
The SRC queues single units and groups of PMs while waiting for resources
if the system is currently using all of its resources for loading other units or
groups. The SRC can load eight load sets (a set is a single unit hat is not
grouped or several units that are grouped) at the same time.
While the units are in the queue waiting for resources, a system recovery
progress message is displayed at the MAP for each queued unit. The queued
units or groups proceed with loading as soon as the resources become
available. Groups have priority over single units when the resources are
allocated.
Audits
The maintenance software looks for and diagnoses the causes of hardware
faults. If a failure is found, tasks are re-routed to compensate for failed
equipment. Also, the maintenance software makes it possible to test,
reconfigure, and add or remove equipment from the DMS-100 Family
System with little or no disruption of service. The “audit software”, on the
other hand, detects and corrects the effects of software errors.
The state or condition of each of the DMS-100 Family hardware resources
(memory, central message controller, or trunk modules) is represented by
software data structures. In addition, there are data structures that do not
directly represent hardware resources but are software resources in their own
right. For example, the message passing system of the operating system
employs data structures to represent mailboxes and letters.
In any software system the size of the DMS-100 Family, which contains
several hundred thousand lines of PROTEL source code, some software
errors may remain even after an extensive testing process. Sometimes
discrepancies will arise between the actual state of a hardware resource and
the state represented by its corresponding software data structure. Internal
inconsistencies can also develop in independent software data structures
such as mailboxes. These discrepancies can arise, for example, because of
unforeseen dependencies in initialization sequences, because of inadequate

DMS-100 International Technical Specification BCS40i and up

2–42 Software engineering

checking for software error conditions (such as ignoring a return code after
sending a message to process), and because of unforeseen or subtle hardware
failure modes. In general, these errors can cause the gradual deterioration,
or even the loss, of some of these software data structures and this will
eventually affect the performance of the switching system. A software data
structure that has deteriorated may become unable to represent the state of a
hardware resource; in such a situation it could, for example, show a network
speech channel as in use when in fact it is not. Independent software data
structures, such as mailboxes, may simply become unavailable for use.
In conventional computer systems this situation is normally dealt with by a
periodic restart or by reloading the computer, usually at least once a day. In
telephony, however, this is not acceptable, and the DMS-100 Family audit
software is used to make periodic checks on the data structures for integrity,
reasonableness and, where appropriate, to see that they match the actual
hardware states that they are meant to represent. Usually any discrepancy is
logged and where possible, corrected. Where there are very serious,
unrecoverable discrepancies the office alarm may be sounded. In extreme
situations maintenance may cause a system restart and may eventually lead
to reload of the system from tape.
There are four levels of audits:
• audits of telephony equipment such as trunks, lines, DTMF receivers and
MF receivers
• audits of call processing software resources: data structures that chart the
progress of individual calls
• audits of operating system software resources: mailboxes, letters, and
memory
• call completion audits.

Example of an audit in DMS-100 Family systems

The first three levels of audit—audits of telephony equipment, call
processing software, and operating system software—check the correct
operation or condition of the corresponding software data structures. The
audit for MF receivers (a first level audit) illustrates the general principles of
these audits.
Every few minutes the audit for MF receivers is invoked and applies a series
of tests. For example, all receivers of a given type that are in the idle state
ought to be on a queue of idle receivers. Thus a data structure describing the
state of one receiver is checked to ensure that if that data structure represents
the idle state it is also linked to the idle queue. Other audits are based on the
idea of reasonableness. For example, if a receiver has been recorded as
continuously busy (that is, associated with the same call) for more than a
given amount of time, it is assumed that this is an error and the receiver is
recovered, marked idle, and put back on the idle queue.

PLN-5001-001i Standard 02.02 April 1997

 Software engineering 2–43

In addition to the test applied to individual receivers, there are also tests on
groups of receivers. The queues of idle receivers are represented by linked
lists. These lists are checked for integrity by following the whole queue to
look for loops or breaks, and then checking to see whether each member in
the list should really be in the list. If a defect in the queue is found, then the
audit takes recovery action by rebuilding the whole queue.
In spite of the many levels of checking in individual parts of the system,
there may still be undetected faults that prevent the correct operation of call
processing. Because of this the call completion audit was designed. For this
audit a crude “goodness” measure is constructed, based on the ratio of the
number of calls successfully completed to the number of calls originated.
The numerical value of this ratio (maximum 100%), which is recomputed
every few minutes, is tracked over several cycles. If it falls below a certain
threshold an office minor alarm is sounded and a message is sent to the log.
If it falls below a lower (critical) threshold an office major alarm is sounded.
If this happens on several consecutive cycles a critical alarm is sounded and
the system is automatically restarted.
DMS-100 Family peripheral software
The DMS-100 Family System has been designed as a distributed system
where the various peripherals perform the time consuming repetitive tasks
(scanning and supervision of trunks, etc.) under the control of the main
CPU. To provide a uniform vehicle for control of activities within
peripheral modules, each peripheral module contains a simulated computer,
the Telephony Peripheral Virtual Machine (TPVM). The architecture of this
simulated computer and its instruction set provide a flexible, high level
mode of control of telephone calls and other tasks carried out in peripheral
modules.
Central control communicates with peripheral modules through messages.
The messages from central control contain programs written in TPVM
language identify the terminal on which the program is to be executed. The
incoming messages to central control, on the other hand, are generally
reports of events (for example, trunk seizure, digits dialed, integrity failure).
A number of advantages are derived from the TPVM approach to DMS-100
Family software. A fairly important one is the containment of effect of
change on software. A new feature will usually require only additions to
software resident in central control; redesign of a peripheral module or the
interface to take advantage of new technology will affect only software
resident in the peripheral module.

DMS-100 International Technical Specification BCS40i and up

2–44 Software engineering

Telephony peripheral virtual machine (TPVM)

The TPVM provides the interface between the peripheral module and central
control. Its architecture includes a stack processor with an instruction set
that offers high level control of telephony peripherals. The instructions (or
primitives) of a TPVM instruction set can be grouped into six major
categories:
• stack
• communication
• terminal control
• call control
• maintenance
• exec

The stack instructions provide a means for performing logical and arithmetic
operations on data in the stack and for moving data from a stack to other
data areas of TPVM.
The communication instructions are used to compose messages and dispatch
them to central control. These instructions also control the generation of
messages to other peripheral modules over the supervision message channel,
the reception of messages from other peripheral modules, and actions
initiated upon reception of such messages.
Terminal control instructions control the hardware that connects the
telephone lines and trunks to the switch. A high level mode of control is
employed, which means that central control does not have to be concerned
with the details of terminal control.
The call control instructions generally initiate control of a phase of a
telephone call, for example, digit reception, or supervision of a talking
connection. The maintenance instructions provide the means for
maintenance of trunk interfaces, peripheral module hardware, and its
interfaces to the DMS-100 Family network.
The “execs” are short TPVM programs stored directly in the peripheral
module memory and can be called up as needed. For example, they can be
invoked directly by central control messages or called up after the
occurrence of certain call events in terminals to initiate needed action. The
TPVM contains instructions to define and invoke these execs.
The TPVM instruction set is designed to optimize some of the conflicting
tradeoffs in the design of peripheral modules, for instance, the need to
minimize peripheral module memory while carrying a substantial part of call
processing load, or the need to be flexible while attaining a high level of
abstraction (that is, protecting central control from the need to concern itself
with call details).

PLN-5001-001i Standard 02.02 April 1997

 Software engineering 2–45

The software that implements a TPVM in a peripheral module is stored in

Random Access Memory (RAM). Indeed, only a small loader program is
stored in peripheral module PROMs (Programmable Read Only Memories).
The TPVM programs are stored on magnetic tape and down-loaded from
central control to the peripheral modules.
Peripheral processing
Processing is carried out in a generally similar way in all the peripheral
modules. For example, the DTC illustrates how peripheral processing takes
place. Each DTC combines two peripheral processors: the Signaling
Processor (SP) and the Master Processor (MP).
• The Signal Processor (via associated hardware interfaces) has four
functions:
— Handling the I/O message protocol between the DTC and CC
— Collection and comparison of all 480 Channel Supervision Messages
(CSM)
— Interfacing the A/B bits on the digital carrier and providing filtering
of the A/B bits, timing of signaling and alarm states, digit collection
and the transmission and timing of local alarms
— Hardware monitoring and fault detection routines
• Master Processor

The MP implements the TPVM. In the TPVM, programs sent from the CC
are interpreted and terminal processes executed. In addition, audits of
terminal states and data are performed.

DMS-100 International Technical Specification BCS40i and up

 3–1

System capacity and performance

Capacity overview
This section provides general processor capacity information and guidelines
for DMS-100 Family switches. Specific capacities for DMS switching
systems vary depending on the market in which the system is deployed, the
application of the system, and the hardware and software provisioned. For
detailed information on DMS-100 system capacity and performance, refer to
the following documents:
• DMS-100 Family Capacity Engineering Manual, 297-1001–170
• DMS-100 Family Provisioning, 297-1001-450
• Northern Telecom Systems Engineering Bulletin (SEB) 89-10-001.

Processor task execution

The processor has 100% of real time available to execute tasks. These tasks
are defined as being related to call processing processes or overhead
processes. Overhead processes handle the overall system operations from
system sanity to monitoring tools, whereas call processing processes deal
with the handling of calls to the recording of billing information.
Overhead processes that perform similar or related functions are grouped
into scheduler classes. These classes allocate a portion of processor real
time based on their contribution to the overall switch performance. The
classes associated with overhead processes are as follows:
• scheduler class
• maintenance class
• system class
• system tools class
• guaranteed terminal class
• background class
• idle class
• audit class
• guaranteed OM class (GOM)
• non-guaranteed OM class (NGOM)

DMS-100 International Technical Specification BCS40i and up

3–2 System capacity and performance

• network operation system file transfer class (NOSFT)

• NETMTC class
The call processing processes that perform similar or related functions are
grouped into scheduler classes and I/O interrupts. The classes and I/O
interrupts are allocated a portion of processor real time based on the traffic
demand on the switch. The classes and I/O interrupts associated with call
processing processes are as follows:
• call processing (CP) class
• high priority call processing (HPCP) class
• deferrable call processing (DEFCP) class
• I/O interrupts
• auxiliary call processing (AUXCP) class

The total real time usage of call processing class, high priority call
processing class, deferrable call processing class, and I/O interrupts are
referred to as call processing occupancy (CPOCC). Within CPOCC, the real
time available to deferred call processing depends on how much real time is
left after the work for the other classes in CPOCC is performed.
With the work for the processor divided into classes, allocation of processor
real time must be set for each class. This document defines how time is
allocated to the different classes and how time allocations fluctuate due to
changing variables. Some of the variables are call types mixes, call
processing occupancies, and engineering factors.
The engineering of real time utilized in the overhead classes of the processor
are usually evaluated at three different grade-of-service levels at high day
busy hour. These three levels are defined as follows:
• 20% of attempts experience dial tone delay (DTD) or incoming start to
dial delay (ISDD) greater than 3 s.
• 8% of attempts experience DTD or ISDD > 3 s.
• 1.5% of attempts experience DTD or ISDD > 3 s.

Dial tone delay (call request delay)

For international products, the dial tone delay is referred to as the call
request delay. Call request delay is defined as the interval from the instant
when the off-hook condition is recognizable at the subscriber line interface
until the exchange begins to apply dial tone to the line.
Call request delay values comply with CCITT recommendation Q543,
table 4.

PLN-5001-001i Standard 02.02 April 1997

 System capacity and performance 3–3

Incoming response delay

The incoming response delay of an exchange is a characteristic that is
applicable where channel associated signaling is used. It is defined as the
interval from the instant an incoming circuit seizure signal is recognized unit
a proceed-to-signal is sent backwards by the exchange.
Incoming response delay values comply with CCITT recommendation
Q543, table 3.

Table 3–1
Real-time allocations/Grades-of-service
% DTS/ISDD NT40 (40 Mhz) DMS SuperNode
overhead/CP overhead/CP

1.5% 21.5% / 78.5% 18.0% / 82.0%

8.0% 18.9% / 81.1% 14.5% / 85.5%
20.0% 17.0% /83.0% 14.0% / 86.0%

DMS SuperNode processors

The DMS SuperNode central processing element – the DMS-Core – can be
equipped with any series of CPU cards currently available. The capacity
increase associated with each processor type is listed in table 3–2, as
compared to the first series available, the SN20.

Table 3–2
Capacity increases – DMS SuperNode processors
Processor Gain factor used in the real time tool

SN20 base
SN30 1.5 @ 86% call processing occupancy (CPOCC)
SN40 1.7 @ 86% call processing occupancy (CPOCC)
SN50 3.0 (SN50 @ 75%, SN20 @ 75%)

2.6 (SN50 @ 75%, SN20 @ 86%)

SN60 3.6 (SN60 @ 75%, SN20 @ 75%)

3.1 (SN60 @ 75%, SN20 @ 86%)

SN70 5.0 (SN70 @ 75%, SN20 @ 75%)

4.4 (SN70 @ 75%, SN20 @ 86%)

Real Time allocations for work on the different types of processors are
provided in this section. The SN20 and SN30 processor allocations are also

DMS-100 International Technical Specification BCS40i and up

3–4 System capacity and performance

considered equal to each other and are referred to as SN processor

throughout this document.

Real time allocation

System operating software (SOS) scheduler
There are several hundred concurrent processes that perform a variety of
functions. Processes that perform similar or related functions are grouped
into scheduler classes. The SOS scheduler allocates processor real time to
the processes using scheduler classes, along with priority of classes and
timeslices for the classes.
A timeslice is expressed as a number of ticks (a clock interrupt every 6.25
milliseconds for the NT40 and 12.5 for the DMS SuperNode. When a
process is created it is assigned a timeslice.
Processor real time allocations
Shown in table 3–3 are the typical real time usage by the classes under full
call processing load (20% DTD > 3 seconds) on a fault free switch versus
real time allocations (overhead allocations set to minimum values)
guaranteed to the class by the switch if needed.
The scheduler class, the system class, and system tool class are referred to as
non-scheduled classes, meaning that they use real time that they need and
are not allocated a set amount of real time at capacity. The values given for
these classes under real time allocation of processor classes in table 3–3 are
typical real time usage at capacity.

Table 3–3
Real-time allocation of processor classes
Class name Typical real time Real time allocations
usage at capacity at capacity

Scheduler 3.0% 3.0 %

System/System tool 1.0% 1.0 %
Maintenance 3.0% 8.0 %
Background/Idle/Audits 4.0% 3.0 %
Guaranteed terminals (GTERM) 1.0% 2.0 %
GOM & NGOM 2.0% 3.0 %
NETMTC 0.0% 0.0 %
NOSFT 0.0% 0.0 %
AUXCP 0.0% 1.0 %
—continued—

PLN-5001-001i Standard 02.02 April 1997

 System capacity and performance 3–5

Table 3–3
Real-time allocation of processor classes
Class name Typical real time Real time allocations
usage at capacity at capacity

HPCP,CP,DEFCP,I/O 86.0% 79.0 %

Total real time 100% 100%

Note: GOM = Guaranteed OM, NGOM = Non-guaranteed OM, NOSFT =
Network operation system file transfer, AUXCP = Auxiliary call processing, HPCP
= High priority call processing, CP = Call processing, DEFCP = Deferrable call
processing.

End

Table 3–3 shows that 86% of processor real time is available for call
processing classes where as 14% of real time is given to overhead classes in
a typical office. These allocations of processor real time to overhead classes
versus call processing classes vary due to switch conditions and scheduler
demands. As the switch conditions cause overhead requirements to increase,
real time available for call processing decreases. Therefore, if overhead
requirements are higher than 14% of processor real time, the maximum call
processing allocation is less than 86%. This is because the overheads can
use all their real time allocations if they need the real time to process the
work.
Classes do not always use their full allocation of the fixed component, but if
required, it is available to them. When extra fixed time allotments are
available, they can be utilized by other classes.
Within the assignable component, the proportion of processor real time that
the scheduler allocates to scheduler classes depends on several factors
including the following:
• the presence of certain applications programs, for example, NOSOFT
• the amount of processor real time required by the switch for maintenance
(as demand increases, the scheduler allocates more time for this class)
• the amount of available processor real time that the scheduler class can
assign to extra work for the processor to perform
• the amount of time assigned to the call processing classes less the actual
usage (if the assignable component is not fully used, extra time is
available to all other classes in whatever amounts they require)
Overhead classes
Overhead tasks have a complex interrelationship with each other and are
application dependent. Real time allocation algorithm controls are

DMS-100 International Technical Specification BCS40i and up

3–6 System capacity and performance

implemented in the operating system scheduler to guarantee that each class

receives a predefined minimum processor allocation of real time across all
call processing occupancies. These allocations, for a typical POTS Office,
were obtained from modeling as well as load and volume testing in existing
offices.
Scheduler class
The scheduler controls the allocation of processor real time after I/O, clock,
and scheduler interrupts have taken their share. Remaining real time is
divided up between all the other classes. The scheduler allocation can range
from 6% of NT40 (4% of SN) fixed time up to 35% of NT40 (35% of SN)
fixed/assignable time based on call mix, call volume, and system critical
maintenance. When real time requirements for call processing classes are
low, the scheduler looks for additional activities to schedule into the
processor, causing the scheduler to consume more processor real time.
Conversely, as real time requirements for call processing increase, call
processing classes give up control of the processor less often, which means
less scheduling. The scheduler will run higher than 6% NT40 (4 % SN) at
maximum call processing occupancies in TOPS and MDC offices due to the
handling of complicated I/O messages. The scheduler in these applications
can run up to l8%.
System class and systemtool class
System class and systemtool class are used for critical system operations.
Both of these classes used as much processor real time as they require,
meaning that the processor real time used by these classes is not restricted
by the scheduler. In a typical office, these two classes combined use is less
than 1% of NT40/SN processor real time at capacity. The 1% of real time is
from the fixed component and any required value above 1% is taken from
assignable component.
Maintenance class
The scheduler allocates 2% of NT40 (1% of SN) processor real time to the
maintenance class. Under normal operating conditions, this class only used
the 2% of NT40 (1% of SN) fixed component. If maintenance requirements
exceeds the minimum guaranteed time, the extra real time allotment is taken
from the assignable component.
Any portion of real time allotment not used by maintenance class is
available to other scheduler classes and is normally used by call processing
classes. But on the other hand, any unused processor time allotted to the call
processing classes is made available to maintenance.
Functions within this class include: Dialtone Speed Recorder (DTSR),
Receiver Attachment and Delay Recorder (RADR), Network maintenance,
reloading new peripheral, overhead for maintenance diagnostic processes,
and Device Independent Recording Package (DIRP) audits.

PLN-5001-001i Standard 02.02 April 1997

 System capacity and performance 3–7

Guaranteed terminal (GTERM) class

The office parameter GUARANTEED_TERMINAL_CPU_SHARE controls
the percentage of processor real time that the scheduler allocates to
guaranteed terminal class at capacity. This parameter has a range of 2%
NT40 (2% SN) to 16% NT (16% SN), with a default value of 2%. The first
2% is part of the fixed component, and the rest is from the assignable
component.
Any portion of the assignable component not used by guaranteed terminal
class is available to other classes and is normally used by call processing
classes.
Functions within this class include log and MAP devices defined as
guaranteed in data tables TERMDEV and LOGDEV.
Guaranteed terminal class runs before systemtool class, thus guaranteed
terminal can not be locked out by systemtool class.
Guaranteed operational measurements (GOM) class and non
guaranteed operational measurements (NGOM) class
Operational measurements (OM) data is gathered continually to monitor the
performance of the switch. Examples of OM data include receiver and trunk
usage and event counts. The OM system organizes the measurement data
and manages data transfer to the display units and recording devices.
The scheduler guarantees 3% of NT40 (2% of SN) processor Real Time at
capacity to the GOM and NGOM classes. The GOM class uses as much of
this time as required (usually less than 1%), and the remainder of the time
goes to the NGOM class. If any portion of this time is left over, it is made
available to the background class and audit class.
OM transfer process runs in GOM Class and the sampling process runs in
NGOM class.
Background (BGK) class and audit class
The scheduler guarantees 3% of NT40 (4% of SN) processor real time at
capacity for BGK and audit classes. BKG class is guaranteed 2.7% NT
(3.7% SN) and audit class is guaranteed 0.3% NT (0.3% SN). Any unused
BGK class time is given to audit class.
Any processor real time not used by the OM scheduler classes is made
available to these two classes, first.
Functions within BKG class include most terminals, OM accumulation, line
and trunk maintenance, and critical audits.
Audit class is for slow running audits and processes that do not require fast
turn around time.

DMS-100 International Technical Specification BCS40i and up

3–8 System capacity and performance

Idle class
Idle class is provided time only if all the other classes have nothing to do.
Therefore, at full load Idle gets 0%.
The idle process and call processing resource audit run in this class.
Network operating software file transfer (NOSFT) class
NOSFT class, which is used by the processes communicating with a DNC, is
limited to 3% of NT40 (3% of SN) processor real time (assignable time) at
capacity. If a switch is not connected to a DNC then the 3% is provided to
the call processing classes first.
Currently the processes for file transfer run in maintenance class instead of
NOSFTG class. This means that NOSFT class will always be 0% and
maintenance class allotments will increase when a DNC is connected to the
switch.
Call processing classes
Call processing processes are divided into four categories: high priority call
processing (HPCP), call processing (CP), deferrable call processing
(DEFCP), and call processing-I/O interrupts. They comprise a total
maximum CPU call processing allocation (assignable component) of l83%
NT40 (86% SN).
Call processing-I/O interrupts (I/O)
I/O interrupts handle interrupts from the peripheral modules, typically using
11% of NT40 (11% of SN) processor real time. The interrupts involve
on-hook, off-hook, digits, flash, and so on.
High priority call processing (HPCP) class, call processing (CP)
class, deferrable call processing (DEFCP) class
The scheduler will give these classes up to 72% of NT40 (75% OF SN)
processor real time at full load in an ideal POTS office with no engineering
factors.
Functions within these classes are: call processing, AMA, call setup,
translations, network connections, terminations, feature activations, AMA
disk and I/O queue handling.

Planning and engineering

The engineering of a DMS-100 Family switch (DMS SuperNode included)
comprises a number of steps that must be accomplished in order to establish
and manage the loading of the processor. Responsibility for this engineering
of switch application is shared between the operating company and Northern
Telecom. The operating company forecasts the expected requirements for
lines, trunks, features, and traffic rate. This information is entered into
Northern Telecom planning and provisioning tools to size the engineerable

PLN-5001-001i Standard 02.02 April 1997

 System capacity and performance 3–9

items for a specified level of performance. The combination of telephone

company data and Northern Telecom engineering rules produce an
engineering application.
Engineerable items, such as peripheral module capacity and software
features, that could limit the maximum carried traffic for a switch must be
identified. An office has physical limitations (lines, trunks, ports), by traffic
types, or by both. Office limitations are tracked against office growth to
ensure a well engineered switch.
Engineering factors
Engineering factors listed in the following table must be considered when
determining processor loading, because these factors affect the switch’s
overall call processing capacity. The factors influence the percent of real
time allocated between overhead and call processing. Some factors, for
example, the Activity tool, are optional, but when activated add to the
minimum overhead requirements. Factors such as average work time, and
peaking are traffic characteristics that can also increase the overhead
requirements. As a result, these factors can decrease maximum call
processing occupancy.

Table 3–4
Processor engineering factors
Factor NT40 DMS SuperNode

Activity Tool (OVERHEAD) 2.0% 1.0%

Activity Tool (CALL PROC) 2.0% 3.0%
Average Work Time 0.0 to 7.0% 0.0 to 4.0%
Maintenance 0.0 to 2.0% 0.0%
EADAS 2.0% 1.0%
SES 0.5% 0.3%
DNC/9600 BAUD 0.0 to 3.0% 0.0 to 1.5%
DNC/19200BAUD 0.0 to 0.5% 0.0 to 2.5%
Eng. Background 0.0 to 14.0% 0.0 to 7.0%
Peaking 2.0 to l4.0% 2.5%
CPUSTAT 1.0% 0.5%
SYNC 1.0% 1.0%
SMDI Calculated Calculated
AABS Calculated Calculated

DMS-100 International Technical Specification BCS40i and up

3–10 System capacity and performance

The following information describes the engineering factors as shown in the

above table:
Activity tool factor
The activity tool is a measuring tool that allows Northern Telecom and the
telephone operating company personnel to accurately determine the
performance of the switch. The processor activities that drive the
measurement use approximately 4% of NT40 (4% of SN) processor real
time. This 4% allocation is split between overhead, which uses 2% NT40
(1% SN), and call processing, which uses 2% NT40 (3% SN). Processor
real time is not required when the tool is inactive.
Average work time (AWT) factor
Average work time is the average amount of central processor time spent
processing each call. The level of messaging complexity associated with
each call type affects how much time is spent processing each call. For
instance, the amount of messaging involved in processing a TOPS call type
is greater than a POTS call type. Depending on call mix and type, different
offices have different average work times. Increased AWT increases the
amount of time the processor spends treating call attempts in progress versus
accepting new origination work.
Table 3–5 below shows AWT factor percents used for the different AWT
values at three different grade-of-service levels:

Table 3–5
DMS SuperNode AWT factor percents
AWT 1.5% DTD 8.0% DTD 20.0% DTD

< 7.5ms 0.0% 0.0% 0.0%

7.5ms – 12.4MS 2.0% 1.0% 0.0%
12.5ms – 20.0ms 3.0% 1.0% 1.0%
> 20.0ms 4.0% 2.0% 1.5%

Table 3–6
NT40 AWT factor percents
AWT 1.5% DTD 8.0% DTD 20.0% DTD

< 15.0ms 0.0% 0.0% 0.0%

15.0ms – 25.9ms 3.0% 1.0% 1.0%
26.0ms – 40.0ms 6.0% 2.0% 2.0%
> 40.0ms 7.0% 3.5% 3.0 %

PLN-5001-001i Standard 02.02 April 1997

 System capacity and performance 3–11

Maintenance factor
In a well maintained office during high traffic, the maintenance class should
use only 2% of NT40 (1% of SN) processor real time at high traffic periods.
If maintenance requirements tend to go above the 2% NT 40 (1% SN), this
extra real time demand must be accounted for in the maintenance factor.
EADAS-DC and EASDAS-NM factors
If the office is equipped with EADAS-DC (Engineering Administration Data
Acquisition System—Data Collection) and/or EADAQS-NM (Engineering
Administration Data Acquisition System—Network Management), then 2%
of NT40 (1% of SN) processor real time is required.
If these systems are not provisioned, 0% of processor real time is used for
the engineering factor.
SES (service evaluation system) factor
SES checks completion of a line/trunk call. It uses 0.5% of NT40 (0.3% of
SN) processor real time when turned on. SES uses 0% of processor real
time when inactive.
DNC 9600 baud and DNC 19200 baud factors
The DNC (Dynamic Network Control), depending on the specific
application, has the ability to gather and store large quantities of data from
several DMS switches simultaneously. The demand for real time depends
on the rate of data transfer. Both engineering factors use 0% of processor
real time when inactive.
Further information can be found in SEB 89-04-001, Business Network
Management (BNM) Impact on the DMS switches.
Engineerable background factor
With engineerable background, the telephone operating company has the
ability to expand the maximum processor allocation for priority devices
above 2% NT40 (2% SN) minimum allocation. This option allows the
amount of processor allocation for priority devices to increase at the expense
of call processing classes, if required.
The basic minimum 2% allocation for guaranteed background class allows
for the following:
• NT40—One priority device with 100% duty cycle or 2% per two priority
devices with 50% duty cycle.
• DMS SuperNode—Allow 1% per priority device with 100% duty cycle,
or 1% per two priority devices with 50% duty cycle.

DMS-100 International Technical Specification BCS40i and up

3–12 System capacity and performance

Any terminal requirements greater than above during periods of high call
processing must be accounted for in engineerable background factor. As a
guideline for additional terminal requirements the following applies:
• NT40—Allow 2% per priority device with 100% duty cycle, or 2% per
two priority devices with 50% duty cycle.
• DMS SuperNode—Allow 1% per priority device with 100% duty cycle,
or 1% per two priority devices with 50% duty cycle.
If the number of priority device requirements are below the basic minimum,
then the engineering factor is 0% of processor real time.
Peaking factor
Traffic peaking refers to a sudden increase in the amount of offered traffic
versus the average traffic over a given time period. The grade-of-service
level can be affected during periods of traffic peaks, for this reason traffic
peaking should be considered when engineering the load level of the
processor. Adding 2–4% NT40 (2.5% SN) for peaking is a safety margin to
ensure desired grade-of-service is maintained at traffic peaks.
A study of over 50 field offices was conducted to determine the effects of
peak traffic on grade-of-service. The conclusions of the study indicates that
95% of the offices had an average fifteen minute peaking over the office
busy hour, requiring less than 2–4% of NT4 0 (2.5% of SN) real time in
maximum high day loading to achieve the average 20% DTD > 3 second
grade-of-service level criteria. Therefore, the NT40 2–4% (POTS–2%,
MIC–3%, TOPS–4%, ACCESS TANDEM–4%) and SN 2.5% (all office
types) compensation factors are considered to be conservative. If peaking is
not required then the engineering factor is 0% of processor real time.
CPUSTAT factor
The operational measurement, CPUSTAT outputs processor occupancy
information in much the same way as the activity tool. With CPUSTAT
active during periods of maximum call processing, the NT40 CPUSTAT
factor is l1% (SN is 0.5).
Further information on CPUSTAT can be found in SEB 88-04-002,
Enhanced CC Real Time Indicator.
SYNC factor
In an access tandem office a call processing phenomenon referred to as
harmonic effect can take place when a processor reaches 85%–90% of
capacity. A feature called Bleed (0–3) can be used to lessen the effect of this
phenomenon. When Bleed is set to maximum there is only a 1% NT40 (1%
SN) impact on processor real time.
Further information on harmonic effect can be found in SEB 88-06-004,
Access Tandem Harmonic Effect.

PLN-5001-001i Standard 02.02 April 1997

 System capacity and performance 3–13

SMDI factor
Simplified Messaged Desk Interface messaging real time requirements must
be calculated for each individual application. SEB 88-06-002, (Simplified
Message Desk Interface Messaging Capacity) can be used as as it refers to
performing these calculations.
AABS factor
Automated Alternate Billing Service (AABS) message handling process,
called MPCFASTO, operates in the Maintenance Class. All the other AABS
functionality operates in Call Processing Processes. The impact of AABS
on real time can be calculated using SEB 89-07–001, Automated Alternate
Billing Service Performance Engineering Guidelines.

Call timings
DMS-100 International call timings are published in systems engineering
bulletin SEB 89-10-001, which is updated on a per-BCS basis. The current
release for BCS36 is issue 8.
The following tables give the current computing module call timings for the
following markets: Japan, Turkey, Belize, China, and Australia. The call
timings in this section are always reported in milliseconds and are
considered to be within ±5% accuracy unless otherwise noted.

Table 3–7
Japan call timings
Call type Call description ms per C/A ms per C/A
SN20 SN30

1972 ISUP TRK - ISUP TRK 16.9 11.3E

1973 ISUP INEFFECT 6.7 4.4E
1976 ISUP TRK - ACD (NOQUEUE) 41.8 27.9E
1977 ISUP TRK - ACD. (QUEUE) 55.6 37.0E
1978 ISUP TRK - ACD (OVERFLOW) 23.9 15.9
1880 SRMF TRK - SRMF TRK 5.9 3.9
1881 SRMF TRK - INEFFECT 4.6 3.1E
1870 SRMF TRK - ACD (NO QUEUE) 31.7 21.1E
1974 SRMF TRK - ACD (QUEUE) 45.6 30.4E
1975 SRMF TRK - ACD (OVERFLOW) 16.2 10.8E
1882 PRI TRUNK (IBNT2) - DTMF TRUNK (IBNT0) 15.9E 10.6E
1883 PRI TRUNK (IBNT2) - DP TRUNK (IBNT0) 15.8E 10.5E
—continued—

DMS-100 International Technical Specification BCS40i and up

3–14 System capacity and performance

Table 3–7
Japan call timings
Call type Call description ms per C/A ms per C/A
SN20 SN30

1884 DTMF TRUNK (IBNT1) - PRI TRUNK (IBNT2) 19.4E 12.9E

1885 DP TRUNK (IBNT1 - PRI TRUNK (IBNT2) 18.6E 12.4E
1886 DP TRUNK (IBNT1) - IBN7 ISUP TRUNK 10.2E 12.8E
1887 PRI TRUNK (IBNT2) - IBN7 ISUP TRUNK 20.2E 13.5E
1888 IBN7 ISUP TRUNK - DTMF TRUNK (IBNT0) 15.2E 10.1E
1889 DTMF TRUNK (IBNT1) - IBN7 ISUP TRUNK 19.8E 13.3E
1890 DP TRUNK (IBNT1) - DTMF TRUNK (IBNT0) 16.7E 11.1E
1891 DTMF TRUNK (IBNT1) - DP TRUNK (IBNT0) 17.7E 11.8E
1892 DP TRUNK (IBNT1) - DP TRUNK (IBNT0) 42.3E 28.2E
1893 DTMF TRUNK (IBNT1) - DTUM TRUNK (IBNT0) 44.2E 20.5E
1894 IBN7 ISUP TRUNK - DP TRUNK (IBNT0)_ 15.1E 10.1E
1895 IBN7 ISUP TRUNK - PRI TRUNK (IBNT2) 19.4E 12.9E
1896 PRI TRUNK (IBNT2) - PRI TRUNK (IBNT2) 18.9E 12.6
End

Table 3–8
Turkey, Belize call timings
Call type Call description ms per C/A ms per C/A
SN20 NT40/40

742 DP LINE - ANNOUNCEMENT 7.9E 15.8

731 DT LINE - LINE 7.7E 15.3
732 DT LINE - BUSY TONE 5.9E 11.8
743 DT LINE - ANNOUNCEMENT 7.9E 15.7
733 DT LINE - FALSE START 2.3E 4.6
734 DT LINE - PARTIAL DIAL ABANDON 2.3E 4.6
735 DT LINE - TRUNK 8.4E 16.7
736 DT LINE - BLDN ANNOUNCEMENT 7.9E 15.7
737 TRUNK - LINE 7.3E 14.6
End

PLN-5001-001i Standard 02.02 April 1997

 System capacity and performance 3–15

Table 3–8
Turkey, Belize call timings
Call type Call description ms per C/A ms per C/A
SN20 NT40/40

738 TRUNK - BUSY TONE 4.6E 9.2

1019 TRUNK - ABANDON 5.7E 11.4
End

Table 3–9
China call timings
Call type Call description ms per C/A ms per C/A
SN20 NT40/40

831 DP LINE - DP LINE 7.6E 15.4

832 DP LINE - BUSY TONE 5.9E 11.9
833 DP LINE - FALSE START 2.3E 4.6
834 DP LINE - PARTIAL DIAL ABANDON/3 DIGITS 2.3E 4.6
835 DT LINE - DT LINE 7.7E 15.4
836 DT LINE - BUSY TONE 5.9E 11.9
837 DT LINE - FALSE START 2.3E 4.6
838 DT LINE - PARTIAL DIAL ABANDON/3 DIGITS 2.3E 4.6
896 DT LINE - C1NONE TRUNK 8.8E 17.5
1008 DT LINE - C1ITLL TRUNK 8.3E 16.5
898 C1NONE TRUNK - DT LINE 8.2E 16.4
895 C1NONE TRUNK - BUSY TONE 5.0E 10.0
1039 C1NONE TRUNK - ABANDON 6.6E 13.1
1018 C1ITLL TRUNK - DT LINE 7.6E 15.1
1048 C1CAMA TRUNK - ABANDON 6.6E 13.1
897 C1NONE TRUNK - C1NONE TRUNK 8.8E 17.6
1049 C1CAMA TRUNK - C1ITLL TRUNK 8.8E 17.7
1058 C1ITLL TRUNK - C1NONE TRUNK 8.6E 17.2

End

DMS-100 International Technical Specification BCS40i and up

3–16 System capacity and performance

Table 3–10
Australia call timings
Call type Call description ms per C/A SN20

3400 ATUP -N5 17.1*

3401 ATUP - NO6 30.3
3402 ATUP - CCITT ISUP 19.8
3404 N5 - ATUP 18.5
3414 N5 - AISUP 18.8
3405 NO6 - ATUP 17.3
3415 NO6 - AISUP 16.9
3406 CCITT ISUP - ATUP 19.9
3416 CCITT ISUP - AISUP 20.8
3408 AISUP - N5 18.7
3409 AISUP - NO6 18.6
3410 AISUP - CCITT ISUP 20.5
4100 ATUP - LINE (ENBLOC) 16.6
4102 LINE - ATUP (ENBLOC) 24.2
4103 LINE - AISUP (ENBLOC) 29.9
4104 AISUP - ATUP (ENBLOC) 18.9
4105 AISUP - AISUP (ENBLOC) 22.0
4107 ATUP - ATUP (ENBLOC) 16.2
4108 ATUP - AISUP (ENBLOC) 19.9
4109 ATUP - ANSI ISUP (ENBLOC) 20.2
4114 ATUP - LINE (OVERLAP) 20.6
4116 LINE - ATUP (OVERLAP) 27.3
4117 LINE - AISUP (OVERLAP) 31.8
4118 AISUP - ATUP (OVERLAP) 20.7
4119 AISUP - AISUP (OVERLAP)_ 23.9
4121 ATUP - ATUP (OVERLAP) 20.0
4122 ATUP - AISUP (OVERLAP) 24.3
End

PLN-5001-001i Standard 02.02 April 1997

 System capacity and performance 3–17

Engineering and planning

The engineering of a DMS SuperNode switch comprises a number of steps
that must be accomplished in order to establish and manage the loading of
the processor. Responsibility for this engineering of a switch application
belongs to both the telephone operating company and Northern Telecom.
The telephone operating company forecasts the expected requirements for
lines, trunks, features, and traffic rate. This information is entered into
Northern Telecom’s planning and provisioning tools to size the engineerable
items for a specified level of performance. The combination of data from
the telephone company and Northern Telecom’s engineering rules produce
an engineering application.
Engineered items, such as PM capacity and software features, that could
limit the maximum carried traffic for a switch must be identified. The office
may be limited physically (lines, trunks, ports), by traffic types, or by both.
Office limitations are tracked against office growth to ensure a well
engineered switch at all times.
Engineering factors
Engineering factors must be considered when determining processor
loading, because these factors affect the switch’s overall call processing
capacity. The factors influence the percentage of real time allocated
between overhead and call processing. Some of the factors like the activity
tool are optional, but add to the minimum overhead requirements when
activated. Other factors, such as average work time (AWT) and peaking, are
traffic characteristics that can also increase the overhead requirements. As a
result, these factors can decrease maximum call processing occupancy.
Optional major features are those features that require additional CPU work
to be considered with the overhead requirements. This feature requirement
is in addition to the minimum overhead requirements. Therefore, with these
features present and active in a switch, maximum call processing occupancy
is affected.
Some of the factors that affect maximum call processing:
• activity tool factor
• average work time (AWT) factor
• maintenance factor
• EADAS (DC/NM) factors
• Service Evaluation System (SEB) factor
• DNC/9600 Baud and DNC 19200 Baud factors
• traffic peaking factor
• CPUSTAT factor
• SYNC factor

DMS-100 International Technical Specification BCS40i and up

3–18 System capacity and performance

• Simplified Message Desk Interface (SMDI) factor

• engineerable background factor
Grade of service
Traffic characteristics, categorized as traffic peaking and average work time
per call, affect the office grade of service at high processor occupancies.
Traffic peaking and average work time do not affect maximum call
processing occupancies. High traffic peaking and large average CPU work
times cause delays within the CPU that become larger at higher levels of call
processing. Thus, more delays are experienced within the CPU as higher
levels of call processing are reached. This extra amount of delay is not
related to, and does not affect the operation of the DMS switch.
To accommodate these delays, two grade-of-service compensation factors
are used for engineering the maximum call processing to meet the HDBH
grade of service of 20% DTD > 3 seconds. There are two grade-of-service
compensation factors:
• Traffic peaking is the variation of offered traffic versus the average
traffic over a given time period. A 2% compensation factor is
considered conservative and applicable to all office types.
• Average CPU work time is the average amount of CPU time that is
spent on processing each call during the office busy hour. Different
office types will have different average CPU work times. Increased
average CPU work times increase the amount of time the CPU spends
processing current call attempts before accepting new origination work.
Thus, at a fixed CPU occupancy, higher average CPU work times will
produce more delays compared to lower average CPU work times.
DMS SuperNode grade of service analysis
The central office must be managed over a wide span of different levels of
traffic resulting in various grades of service levels. Northern Telecom
provides tables to engineer the switch at 1.5%, 8.0% and 20% grade of
service.
These call timing models were measured at Northern Telecom’s BNR
facility in a laboratory environment. However, the call timings described
here are structured to emulate realistic switch parameters in a working
telephone office.
Overhead occupancy
The engineering of CPU real time used in the overhead classes of the CPU is
important, since the maximum call processing occupancy accounts for
non-deferrable priority processes such as task assignment, scheduling and
system integrity. Deferrable functions, such as operations, administration
and maintenance (OAM) and auditing routines are also included in the
overhead occupancy. Overhead factors can cause the minimum total CPU

PLN-5001-001i Standard 02.02 April 1997

 System capacity and performance 3–19

allocation of 14% to be higher. Overhead has a complex interaction with

call processing because as call processing increases, many overhead classes
collapse to their minimum levels. Therefore, effective capacity engineering
of overhead requirements includes overhead requirements that are above the
minimum values.
If the number of priority device requirements are below the basic minimum,
then the engineering factor is 0% of processor real time.
Figure 3–1
Distribution of CPU occupancy (DMS SuperNode)

Total CPU occupancy

100%

Call processing occupancy 86%

Overhead occupancy
(non-call processing)
0 14%

DMS-100 International Technical Specification BCS40i and up

3–20 System capacity and performance

Operating guidelines
The operating guidelines for establishing the loading levels for specific
applications, at both the end and the beginning of the engineering design
period, include a series of planning factors that the telephone operating
company should take into consideration in the engineering process. The
current maximum load recommendation for the DMS-100 Family is 86% of
the total CPU time for local/toll/MDC offices and 86% of the total CPU time
for TOPS offices, including a minimum of 14% for basic non-call
processing overhead. Refer to figure 3–1 for the distribution of total CPU
occupancy. Once the office is placed in service, the office call attempt busy
hour can be monitored and the planned load can be increased according to
the operating plan.
Engineering considerations – load level
There are many considerations and decisions to be made when planning load
levels for a processor. Some of the decisions are based on clear cut rules,
but others are based on sound engineering judgements using guidelines.
The following are some of the key considerations that must be evaluated by
the engineer before decisions can be made:
1 Determine the point on the load service curve that the processor will fall
during both HDBH and ABS. Having the grade of service level during
ABS too close to the exponential part of the load service curve may
cause grade-of-service to be greatly reduced during HDBH. The higher
the ratio of HDBH to ABS, the larger the buffer needed from the
exponential part of the curve.
2 The High Day call mix versus ABS call mix must be considered.
Typical offices serving large business applications usually see very little
variation in call mix from day to day, whereas the call mixes for POTS
offices tend to change with traffic levels.
3 The engineering factors by percents used in deriving a processor’s
loading are considered conservative values because all the major features
rarely work concurrently or actively produce outputs every minute of the
busy hour. Also priority devices would rarely have 100% duty cycles
during busy hour.
4 In an initial office the data used to define office characteristic are
predicted values, whereas in an in-service office data are measured
values. Good engineering judgment must be used in determining the
predicted values in order to ensure the switch meets the desired
grade-of-service level during cutover. Once an office is placed in
service, the office characteristics are measured and compared to
predicted characteristics. If any of the prediction numbers differ from
the measured, then the new verified numbers can be used for switch load
planning.

PLN-5001-001i Standard 02.02 April 1997

 System capacity and performance 3–21

Capacity prediction and verification tools

Prediction with REAL::TIME
High Day capacity can be reasonably predicted for a particular application
by using the expected feature and call mix in conjunction with the measured
CPU per call timings. With the number of features being introduced to the
DMS-100 Family, the assessment of CPU use, both now and in the future, is
of increasing importance.
Northern Telecom’s PC program, Real::Time is used to predict CPU
capacity. It is a stand-alone program that is available on floppy disk and can
be used on an IBM or IBM-compatible personal computer. This program
predicts CPU capacity to a fair degree of accuracy. Based on the total
milliseconds required for an office configuration and the overheads desired,
the capacity prediction technique determines what the percentage overhead
and call processing occupancy (CPOCC) will be with the call mix overhead
data that has been entered.
Verification tools
Office traffic can be measured on the DMS-100 Family switch using
operational measurements (OMs) and the Traffic Separation Measurement
System (TSMS). These measurements are used in conjunction with the CPU
capacity tool, Activity, to validate CPU predictions for each office
configuration.
Operational measurements are used to determine system call mix,
feature activations, and trouble conditions. The OMs reference measured
call characteristics including overflows and blocked calls. This provides a
delineation of capacity and trouble concerns. OMs, when used in
conjunction with the Activity tool, provide the capability to project system
call capacity.
The Activity tool provides an on-line real time indicator tool that monitors
the system traffic count, CPU occupancy, and call queuing time. The
Activity tool can be used as follows:
• in evaluation of the current system configuration to assist in capacity
planning
• as a maintenance tool to determine if call processing is being efficiently
handled
The measurements of call processing occupancy and grade of service from
these tools verify the expected real time requirements. Since the Activity
tool takes direct measurements from the CPU scheduled and interrupt
processes, it is the most comprehensive and accurate real time measurement.
MEMCALC – Calculates memory requirements
MEMCALC is an engineering tool that uses software, data base information
and actual switch parameters to calculate memory requirements.

DMS-100 International Technical Specification BCS40i and up

3–22 System capacity and performance

MEMCALC requires as inputs all software packages that will reside in the
office’s in-service BCS load as well as data based on end of design (EOD)
quantities, or actual switch parameters. This tool is an integral part of
memory provisioning and is available to customers as well as Northern
Telecom. MEMCALC produces the memory required to satisfy the switch
application only. It includes required memory allocator rounding rules as
part of its output. An administrative spare, which includes a spare to
account for MEMCALC program accuracy, BCS dump and restore tools and
normal day-to-day service order activity, is also required. Administrative
spare is also added to the MEMCALC output and is included in the
description of provisioning policies.

Memory
The basic memory provisioning policy applies to both NT40 and SuperNode
in the following procedures:
1 To calculate memory requirements, use the wired capacities of all lines,
trunks and input/output (I/O) ports. Note that cards equipped I/O ports
should be considered as wired. This includes all read only and keyboard
send receive printers and visual display units.
2 When processing extensions and/or authorized software updates, all
existing software packages from the previous office image must be
applied to the new load. Discrepancies between the previous office
image and the current Job Feature Data Base (JFDB) should be resolved
by the job engineer and the Northern Telecom marketing representative.
DO NOT remove any feature Package(s) from the office image or JFDB
without prior written authorization from the marketing representative
and the customer. After all discrepancies have been resolved, all records
should be updated as required.
3 The DMS SuperNode Major Group Software Package, NTX960AA/AB,
must be present in the job’s JFDB listing in order to access SuperNode
MEMCALC. Conversely, NTX960AA/AB must be absent from the
job’s JFDB listing in order to access NT40 MEMCALC.
DMS SuperNode memory
The DMS SuperNode core can be provisioned with up to ten memory cards.
There are three memory cards available, as follows:
• 6-Mbyte NT9X14BB
• 24-Mbyte NT9X14DB
• 96-Mbyte NT9X14EA
Table 3–11 lists the maximum addressable memory for each of the available
SuperNode processor options.

PLN-5001-001i Standard 02.02 April 1997

 System capacity and performance 3–23

Table 3–11
Maximum addressable memory values
SuperNode CPU Maximum addressable memory

Series 20 NT9X13BC 200 Mbytes

Series 30 NT9X13GA 212 Mbytes

Series 40 NT9X13HB 212 Mbytes

Series 50 NT9X10AA 248 Mbytes memory

216-Mbyte shelf
32 Mbytes on-board processor

Series 60 (NT9X10AA and 400 Mbytes

NT9X14EA)

Detailed provisioning requirements for memory are specified in DMS-100

Family Provisioning, 297–1001–450.
System load module capacity
The SLM is a mass storage system that is used to store office images,
peripheral module loads, and device independent recording package (DIRP)
data, such as billing data. The SLM is packaged into a single replaceable
unit that consists of a 5 1/4-inch hard disk drive, a 1/4-inch streaming
cartridge tape drive and a controller card.
The latest version of the SLM is the SLM II. The SLM II hard disk has a
capacity of 600 Mbytes and the tape cartridge has a capacity of 150 Mbytes.
Although currently an optional offering, it is recommended that all DMS
SuperNode offices provision a SLM II.
Enhanced network (ENET) capacity
The Enhanced Network is a single-stage, non-blocking, constant delay,
junctorless time switch that supports narrow band services as well as
services requiring bandwidth greater than 64 kilobits per second (kb/s).
In the single-cabinet configuration, a fully duplicated ENET can expand
from 4000 channels to 64 000 channels in 2000 channel increments in the
peripheral-link paddle boards and 4000 channel increments for the first
32 000 channels and then 16 000 channel increments thereafter in the
crosspoint cards. With the addition of a second cabinet, ENET capacity can
be expanded to 128 000 channels in the said increments.

DMS-100 International Technical Specification BCS40i and up

3–24 System capacity and performance

Peripheral module termination capacity

International digital trunk controller (IDTC)
The IDTC interfaces up to 16 digital (PCM30) carrier systems. Each carrier
system provides 30 communication channels, for a total capacity of 480
trunk terminations per IDTC. The International Digital Trunk Equipment
Frame (IDTE) houses up to two IDTCs.
International line concentrating module (ILCM)
The ILCM supports termination of up to 640 lines at a capacity of up to 8
CCS per line, and provides from two to six DS30A links to an ILGC. Each
ILCM consists of two line concentrating arrays (LCA), each of which
terminates 320 lines. Each LCA contains five line drawers which each
house up to 64 line cards. An International Line Concentrating Equipment
(ILCE) frame can house two ILCMs, for a total capacity of 1280 line cards
per frame.
International remote line concentrating module (IRLCM)
The IRLCM provides a remote interface for up to 640 subscriber lines. The
IRLCM connects to the host ILGC using from two to six PCM30 links.
International line group controller (ILGC)
The ILGC supports the ILCM and IRLCM, by providing interface capability
for any combination of up to 16 DS30A links and/or PCM30 carrier
systems. Each ILCM requires two to six DS30A links and each IRLCM
requires two to six PCM30 ports. The ILGC can provide a minimum of
three (90 channels) to a maximum of 16 (480 channels) duplicated DS30
links to each network plane.
Monitoring and administration
Telephone company engineers project usage, lines, trunks and features that
are required in an office through an engineering period. This period is
usually two to three years following an in-service date. These projections
are based upon customer growth forecasts that the telephone company
develops.
Telephone company and Northern Telecom engineers provision memory for
DMS-100F switches based upon the telephone company’s projections.
Using MEMCALC, future BCS requirements are based upon Northern
Telecom’s forecast of the SuperNode memory needed for these BCSs. The
memory is provisioned in a DMS-100F switch based upon these two
forecasts: customer end of design (EOD) parameters and MEMCALC.
After the cutover of a new switch or a major addition to an existing switch,
MEMCALC should be run using the actual switch parameters. The
MEMCALC questionnaire references the necessary switch data to run the
tool and the switch’s outputs to MEMCALC input requirements. Some of

PLN-5001-001i Standard 02.02 April 1997

 System capacity and performance 3–25

this information may also be accessed via the MAP utility, using the
BCSMON command—BCSMON DUMP COUNT.
Performance standards
Performance standards establish the criteria used to engineer a DMS-100
Family switching system, including the determination of the quantity of
various circuits required. The DMS-100 Family parameters involved are
documented, and sensitivities are discussed in the following subsections.

Basis for provisioning of engineered facilities

The DMS-100 Family traffic sensitive components are provisioned based on
service criteria, traffic load level, and/or real time. The capacity tables and
mathematical functions that form the basis for equipment provisioning give
the traffic capacity (usage) or real time capacity (call attempts) that can be
handled by the overall system as well as the traffic sensitive system
component, while attaining a fixed service criterion during a given period of
time. These are based on average busy season service objectives and 10
high day service objectives. In the two following examples, hour refers to
any period of 60 contiguous minutes, and month refers to a service
observing month that typically ends on the 20th to 22nd day of the calendar
month:
• Average Busy Season method traffic data, typically expressed for local
switching systems as CCS per main station, is collected and processed to
determine the busiest hour for each of the switching system components
that is to be engineered. The hour that has the highest average traffic for
the three highest traffic months is designated the busy hour. The three
months, not necessarily consecutive, that have the highest average traffic
in the busy hour are termed the busy season. The busy hour traffic level
averaged across the busy season is termed the average busy season busy
hour (ABSBH) load.
• In the ten high day method of engineering, the traffic data is processed to
identify the ten highest traffic days of the year. The hour of the day that
has the highest average traffic on these ten days is designated the busy
hour. The ten day average traffic level for this busy hour (the same hour
for all ten days) is termed the ten high day busy hour load. The one day
among the same ten days that has the highest traffic during the busy hour
is designated the high day. The traffic level in the busy hour of the high
day is termed the high day busy hour (HDBH) load. (There may be
some other hour of the high day or another day of the year with a higher
traffic level, but it would not be used as an engineering basis.) In the ten
high day method, data is not included for extremely high traffic days
which can be attributed to unusually severe weather or catastrophic
events which are not expected to recur from year to year.

DMS-100 International Technical Specification BCS40i and up

3–26 System capacity and performance

The busy hour ratios of 10 HDBH to ABSBH and HDBH to ABSBH for
calls or traffic usage are specified by the operating company during the
provisioning of engineering facilities.
Provisioning methodology
DMS-100 Family overall and system component provisioning is based on
three factors:
• termination—lines and trunks
• traffic criteria—usage and call attempts
• real time—call attempts and call processing time

Termination
By this method, provisioning is performed on a termination appearance
basis. The number of components to be provisioned depends on the number
of terminations to be connected to these components and on the number of
terminations that these components can allocate per module.
Traffic criteria
Using traffic criteria, provisioning is performed on a traffic capacity basis
(usage and call attempts). The number of system components to be
provisioned depends on the traffic offered by the terminations to be
connected to these system components and on the traffic capacity that these
system components can carry per module. This is a function of the method
of operation based on blocking or delay criteria and the service standard
required.
Real time
This provisioning criteria is accomplished on a total millisecond per hour
capacity basis (call attempts and timings). The number of system
components to be provisioned depends on the mix of traffic originating from
or terminating to these system components and the millisecond capacity per
hour that these system components can provide.

Service standards
Matching loss grade of service
DMS-100 International grade of service specifications comply with CCITT
recommendation Q543. Inadequately handled call attempts are attempts
which are blocked (as defined in E600) or are excessively delayed within the
exchange. Excessive delays are those that are greater than three times the
“0.95 probability of not exceeding” values recommended in tables 3 through
6 of Q543. Table 3–12 lists the probability of inadequately handled call
attempts occurring, as specified in Q543 table 2.

PLN-5001-001i Standard 02.02 April 1997

 System capacity and performance 3–27

Table 3–12
Probability of inadequately handled call attempts occurring

Type of connection Reference load A Reference load B

Internal (Intra) 10-2 4 x 10-2
Originating 5 x 10-3 3 x 10-2
Terminating 5 x 10-3 3 x 10-2
Transit 10-3 10-2

In table 3–12, Internal refers to IAML (intra-office matching loss).

Originating refers to OML (outgoing matching loss). Terminating refers to
TML (terminating matching loss). Transit refers to TAML (tandem
matching loss.
The DMS-100 International switch is provisioned in modular sections; each
module has its own component of matching loss. For local switch
applications, IML is the limiting factor. Incoming matching loss is the sum
of the matching losses applicable to each component. TML is the IML
portion allocated to the peripheral modules (ILGCs and ILCMs). For
tandem applications, TAML is the limiting factor.
Delay criteria
Specifications for call request delay and incoming response delay comply
with CCITT recommendation Q543, tables 3 and 4.
Service circuits
In all cases, occupancy on individual groups of service circuits, such as
receivers, tone circuits, conference circuits, or announcement circuits, is
limited to 75% on an HDBH load level basis. The requirements are
expected to be controlling requirements for large groups of service circuits.
For smaller groups of service circuits, the following definitions provide the
basis for service circuit delay and blocking requirements.
In general, the quantities of these system components are engineered to
cause very little blocking or delay to customers and to cause minimal
queuing (even under peak loads). Central processor usage per call does not
increase substantially during peak load conditions. The service circuits
grade of service based on blocking and delay criteria are shown in
table 3–13:

DMS-100 International Technical Specification BCS40i and up

3–28 System capacity and performance

Table 3–13
Service circuits blocking and delay criteria grade of service
Service circuit Criteria ABSBH HDBH

DTMF receiver DTD > 0 sec 1% 5%

DTD > 3 sec 0.1% 1%
MF receiver DTD > 0 sec 1% 5%
DTD > 3 sec 0.1% 51%
Announcement circuits Blocking 1% 5%
Tone circuits Blocking 1% 5%
Conference circuits Blocking 0.1% 1%
Note: UTR receiver uses similar GOS as DTMF or MF receivers.

Receivers
Service circuits in the DMS-100 Family system are common equipment
units which include DTMF, MF receivers, and universal tone receivers
(UTR). The DTMF receiver is used to convert dual-tone multifrequency
address signals from the customer to machine readable codes. The DTMF
receiver connection is from a customer line (through an LCM/LGC) through
the network, to a DTMF receiver on a TM or MTM.
The MF receiver is used to convert multi-frequency signaling over a trunk to
a machine-readable code. The MF receiver connection is from an incoming
trunk (through a digroup or a TM) through the network, to an MF receiver
on a TM or MTM.
The UTR is used to collect and decode both DTMF and MF address signals
and to report the decoded address digits to the Central Control by means of
the peripheral signaling processor, and it eliminates the need to establish a
network path to a DTMF/MF receiver in an MTM. The UTR is located in
the LGC, LTC, DTC, or RSC peripherals.
If blocking occurs, two connection attempts are made on randomly chosen
DTMF/MF receivers (MTM mounted). The length of time taken to establish
a connection to a receiver determines its delay criteria. To minimize
blocking probability, the receivers are spread over the available TMs and
MTMs.
Recorded announcement circuits
The Digital Recorded Announcement Machine (DRAM) provides recorded
announcements capabilities which can be engineered on a per office basis.
DRAMs can be used on a standalone basis, or in conjunction with other
recorded announcement equipment.

PLN-5001-001i Standard 02.02 April 1997

 System capacity and performance 3–29

DRAM announcements can be provisioned in several ways:

• standard, preset announcements permanently stored on programmable
read only memory (PROM)
• operating company definable announcements stored in read only
memory (RAM) (NT1X77 card)
• operating company definable announcements stored in electrically
erasable programmable read only memory (EEPROM).
I
It is not economically practical to permanently record every type of
emergency announcement on PROM. The EEPROM card (NT1X79) is
recommended for customized announcements, so that the announcements
are retained during switch software upgrades.
It is recommended that at least two DRAMs be provisioned with each switch
installation to ensure reliability. Once a DRAM is set up, the
announcements are played back continuously on prescribed DS30 channels
which connect the maintenance trunk module (containing the DRAM) to the
network. Up to 255 subscribers can be connected simultaneously to an
announcement.
The maximum length of an announcement is 31 seconds. Each DRAM can
address up to 1 Mbyte of memory, corresponding to 254 seconds of speech
storage.
The number of simultaneous connections in the DRA system is limited in
order to reduce the possibility of time switch blocking. This maximum is
normally specified in translations and should not exceed 30% of the number
of call processes calculated per office application. From a traffic standpoint,
each TSB source can be viewed as a trunk group in which the number of
servers equals the above specified maximum number of connections.
In a given DRA system, all announcements will share a group of trunk
circuits (channels) as determined by the DRA controller switch setting (8,
16, 24 or 30). The number of circuits required can be established as a
function of the number of announcements, their traffic characteristics and
announcement grade of service (GOS) objectives.
Overload and abnormal conditions
A DMS-100 Family switch is designed and configured with specific
characteristics to handle a defined amount of traffic. If the designed load is
exceeded, some of the traffic must be delayed. The exact effect depends on
the nature of the overload. The design intent is that any part of the
equipment that is offered more than its rated load should continue to operate
at or near its rated capacity. The excess load should be delayed or blocked
in an orderly manner and should not cause throughput degradation or outage.

DMS-100 International Technical Specification BCS40i and up

3–30 System capacity and performance

Types of overload
Overload may be in any of four main areas:
• shortage of tone receivers
• shortage of speech paths
• shortage of processing capacity in one or more peripherals
• limits on global system capacity

Overload controls and protection

The following algorithms are used to provide overload protection on
DMS-100F switches:
• message throttling
• progress message favoring
• resource reservation
• ineffective attempt elimination

Message throttling limits the number of incoming messages that the

CPU or processor will accept in a clock tick, (that is, 6.25 ms). Message
throttling is performed by weighting incoming messages according to
category (call processing, non-call processing) and ensuring that, during any
clock tick, the weighted sum of incoming messages does not exceed a
pre-defined threshold. Once the threshold is reached, I/O interrupts are
disabled until the start of the next clock tick, at which time the process is
repeated.
Progress message favoring ensures that calls in progress are given
preferential treatment over new originations. This is done by splitting call
processing into two queues: origination and progress, and always serving the
progress queue first.
Under high load, progress message favoring delays the number of
originations accepted by the processor and this, in turn, limits the possibility
of destructive processor overload. A side effect of this technique is that it
practically guarantees that accepted calls will be successfully completed.
Resource reservation A variety of software resources are required in
order to process call events. These resources are office engineered and
hence, under overload, certain of these resources will exhaust. By design,
resources exhaust on originations and not progress events and also by
impacting originations. Shortage effectively serves as an overload control.
Typical examples of critical resources are call condense blocks (CCB) and
call processing letters. One of the CCBs is obtained at the initiation of every
call and released on call takedown but if no CCBs are available then no new
call originations can be accepted. The call processing letters are used for
both origination and progress messages but if these are unavailable call

PLN-5001-001i Standard 02.02 April 1997

 System capacity and performance 3–31

events can not be processed. To force shortages to affect only originations, a

sufficient number of these letters are reserved solely for progress events.
When the number of free letters is reduced to the reserved amount,
origination events are no longer accepted.
Ineffective attempt elimination The primary goal of the processor
under extreme load conditions is the successful termination of the maximum
number of calls. As overload conditions persist, delays tend to develop in
processing new call originations and this leads to an increase in pre-dial
abandons. Handling abandoned calls lowers the overall capacity of the
switch and hence, in order to achieve the highest successful termination rate,
the processor discards an origination message without further processing if a
second message has arrived for that specific call. This action is restricted to
origination events which have been queued in the processor for greater than
0.5 s, since delays of this order only occur during heavy overload conditions.
With load shedding, origination calls in the processor for longer than 3 s are
discarded, requiring the peripheral to regenerate the origination.
Originations queuing in peripherals During periods of overload,
originations may be submitted to a DMS-100 Family peripheral at a rate
greater than they are accepted by the processor. Treatment of the excess
originations in the trunk peripheral depends on the trunk type. Trunks are
put into a lockout state in the peripheral if originations are delayed for more
than five seconds. The trunk will return to the idle state upon receipt of a
clear forward signal. In the case of immediate dial trunks, dial pulses are
collected by the peripheral before an attempt is made to submit any
origination to the processor.
Line originations are queued within the line peripheral. Until the origination
message has been sent to the central control and a suitable response
(associate channel and provide dial tone order) has been received, further
state changes on the line are ignored. Therefore, a subscriber remaining
off-hook will eventually receive dial tone. If the subscriber has gone
on-hook when the central control response is received, the line peripheral
sends a disconnect message to the central control, which responds by
returning the line to the idle state.
When the origination queue in the line peripheral overflows, line
originations are deferred. Subsequent line scans cause originations to be
placed in the queue as space becomes available. In newer peripherals, the
originations are handled in the last in-first out (LIFO) manner rather than
first in-first out (FIFO), and calls are handled in a pre-determined order:
• in progress
• terminations
• new originations

DMS-100 International Technical Specification BCS40i and up

3–32 System capacity and performance

Multifrequency (MF) tone receivers

If no MF tone receivers (MTM mounted) are available, incoming calls may
be delayed in a queue for up to 5 seconds. Calls overflowing the queue are
placed in lockout state until clear forward is received. Adequate receiver
provisioning normally prevents this type of overload. Dial pulse calls do not
require a common receiver but are handled entirely within the originating
peripheral.
Dual-tone multifrequency (DTMF) receivers
If no DTMF receivers are available, originating calls are delayed in a queue
indefinitely. Calls overflowing the queue are re-originated (that is, processor
primes the peripheral to wait for one second, returns the line to the idle scan
list and subsequently produces an origination message if still off-hook). If
an originating call in the queue goes on-hook it is removed from the queue.
The length of the queue is equal to the number of DTMF receivers (MTM
mounted) in the office.
Speech paths
The DMS-100 Family digital switching network has a very low blocking
factor and also allows the use of generous provisioning rules. Network
overload is therefore unusual unless abnormal traffic patterns occur. If no
speech path can be found after two path trials, the call is routed to tones.
Digital tone generators are located in peripheral modules and tones are
transmitted to trunks without using network paths.
Speed of service
This subsection defines the time intervals allowed for performing certain call
processing operations within the DMS-100 Family switching system. The
speed of these operations is considered critical to customer service and for
effective interaction with other switching systems.
Definitions of supervisory signals
The following is a definition of the per trunk signaling (PTS) supervisory
signals used in the DMS-100 Family to interact with other switching
systems.

PLN-5001-001i Standard 02.02 April 1997

 System capacity and performance 3–33

For each operation time, the definition is given in terms of the starting and
ending points followed by the requirements. The value given for the mean is
interpreted as the maximum allowable mean from the starting point to the
ending point for that operation time. The operation time may not exceed the
95% level more than 5% of the time for two conditions:
1 Receipt of a PTS supervisory signal is said to occur when the state
transition, which begins the signal, occurs at the E lead. The E and M
lead trunks make use of separate leads for signaling. Ground and open
states are used for off-hook and on-hook, respectively, on the E lead for
signaling from the trunk facility to a trunk circuit. Battery and ground or
battery and open states are used for off-hook and on-hook, respectively,
on the M lead for signaling from a trunk circuit to the trunk facility.
2 Transmittal of a PTS supervisory signal is said to occur when the state
transition, which begins the signal, occurs at the M lead.
Operation times applicable to PTS – SuperNode/access tandem
Operation times will be met at all engineered traffic loads.
Address time (cross-office time)
• Starting Point: End of address digit reception
• Ending Point: Transmittal of connect signal
• Mean: 200 ms
• 95% Level: 360 ms

Network path closure time

• Starting Point: Completion of outpulsing
• Ending Point: Establishment of communication path through office
• Mean: 100 ms
• 95% Level: 180 ms
• Maximum: 250 ms

Answer time
• Starting Point: Receipt of answer signal
• Ending Point: Transmittal of answer signal
• Mean: 22 ms *
50 ms * *
• 95% Level: 38 ms *
95 ms * *
• Maximum: 50 ms *
Not Specified * *

DMS-100 International Technical Specification BCS40i and up

3–34 System capacity and performance

* Trunk to Trunk Connection

* * Trunk to Line Connection

Re-answer time
• Starting Point: Receipt of re-answer signal
• Ending Point: Transmittal of re-answer signal
• Mean: 100 ms
• 95% Level: 180 ms
• Maximum: 250 ms

Clear-forward time
• Starting Point: Receipt of clear-forward (disconnect) signal
• Ending Point: Transmittal of clear-forward (disconnect) signal
• Mean: 100 ms (plus incoming trunk disconnect timing)
• 95% Level: 180 ms (plus incoming trunk disconnect timing)
• Maximum: 250 ms (plus incoming trunk disconnect timing)

Clear-back time
• Starting Point: Receipt of clear-back (hang-up) signal
• Ending Point: Transmittal of clear-back (hang-up) signal
• Mean: 100 ms
• 95% Level: 180 ms
• Maximum: 250 ms

Release-guard time
• Starting Point: Timeout of guard timing
• Ending Point: Idling of outgoing trunk
• Mean: 100 ms
• 95% Level: 180 ms
• Maximum: 250 ms

Forward-transfer time
• Starting Point: Receipt of forward-transfer (ring-forward) signal
• Ending Point: Transmittal of forward-transfer (ring-forward) signal
• Mean: 100 ms (plus incoming trunk ring-forward timing)
• 95% Level: 200 ms (plus incoming trunk ring-forward timing)

Seizure time
• Starting Point: Receipt of connect signal

PLN-5001-001i Standard 02.02 April 1997

 System capacity and performance 3–35

• Ending Point: Transmittal of start dial or end of wink-start signal

• Minimum: 280 290
• Mean: 375 315
• 95% Level: 560 420
Immediate start time
• Starting Point: Receipt of connect signal
• Ending Point: Capability of storing pulses for immediate dial operation
• Minimum: 25 ms
• Mean: 50 ms (plus seizure recognition time)
• Maximum: 120 ms (plus seizure recognition time)

Response time
• Starting Point: Receipt of start-dial or end of wink-start signal.
(Transmittal of connect signal in immediate dialing case)
• Ending Point: Beginning of outpulsing
• Mean: 100 ms (plus required delay)
• 95% Level: 180 ms (plus required delay)
• Maximum: 250 ms (plus required delay)

Receiver release time

• Starting Point: End of address digit reception
• Ending Point: Idling of address signal receiver
• Mean: 100 ms
• 95% Level: 180 ms
• Maximum: 250 ms

Transmitter release time

• Starting Point: Completion of outpulsing
• Ending Point: Idling of address signal transmitter
• Mean: 100 ms
• 95% Level: 180 ms
• Maximum: 250 ms

Operation times for automatic message accounting (AMA),

centralized AMA (CAMA) and local AMA (LAMA)
Charge Answer Time
• Starting Time: Receipt of answer signal
• Ending Time: Beginning of charging period
• Mean: 60 ms

DMS-100 International Technical Specification BCS40i and up

3–36 System capacity and performance

• 95% Level: 110 ms

• Maximum: 150 ms
Charge Disconnect Time
• Starting Point: Receipt of clear-forward
• Ending Point: End of charging period
• Mean: 60 ms plus incoming trunk disconnect timing
• 95% Level: 110 ms plus incoming trunk disconnect timing
• Maximum: 150 ms plus incoming trunk disconnect timing

Automatic number identification (ANI) request time

• Starting Point: End of address digit reception
• Ending Point: Transmittal of ANI-request signal
• Mean: 170 ms
• 95% Level: 390 ms

Operator number identification (ONI) request time

• Starting Point: End of address digit reception
• Ending Point: Transmittal of CAMA-position-request signal
• Mean: 100 ms
• 95% Level: 180 ms
• Maximum: 250 ms

ONI connect time

• Starting Time: Receipt of seizure-acknowledgement signal from CAMA
position
• Ending Time: Establishment of communication path between CAMA
position and calling customer
• Mean: 100 ms
• 95% Level: 180 ms
• Maximum: 250 ms

ONI disconnect time

• Starting Point: Receipt of either the calling number or the
position-disconnect signal
• Ending Point: Idling of CAMA position
• Mean: 100 ms
• 95% Level: 180 ms
• Maximum: 250 ms

PLN-5001-001i Standard 02.02 April 1997

 System capacity and performance 3–37

Mishandled calls
The call completion rate for a DMS-100 Family System is equal to or
greater than 99.99% (no more than one call in 10 000 mishandled). A
mishandled call is a call attempt that arrives at an incoming port of the
switching system but was mishandled due to a hardware and/or software
error. Three results are expected:
• Mis-routing
• Premature release by the switching system
• Switching system transmission failure as detected by a continuous parity
check.
Calls that cannot be completed due to the unavailability of engineered
equipment are not included in this definition unless the congestion is caused
by a system or subsystem fault or error.

Reliability
To ensure high reliability, all critical subsystems are duplicated. If a fault is
detected, the system software automatically re-configures the hardware to
prevent or minimize the effect on service.
The coverage of a duplicate subsystem is the proportion of the occurrence of
simplex faults from which the subsystem can recover through the detection
of the fault and the subsequent re-configuration to the standby module. The
long-term attainable coverage for the DMS-100 Family and the DMS
SuperNode duplicate modules is 99.9% for the core equipment and 99% for
peripherals.
Hardware failures
Table 3–14 on page 3–39 lists the predicted rates of failure for DMS-100
Family circuit cards. Table 3–15 lists the predictions for hardware reliability
performance.
System downtime
The following estimated times for restarts and reloads assume a fault-free
DMS-100 Family System, both hardware and software. In addition, it is
assumed that the peripheral subsystem has not experienced a power outage
prior to the restart.
Unscheduled system downtime – SuperNode
The total DMS-100 Family System unscheduled downtime, due to hardware,
software and procedural failure modes, is expected to be no more than two
hours in 40 years.
For BCS36, the following timings have been recorded for a typical DMS
SuperNode equipped with a SR40 processor:

DMS-100 International Technical Specification BCS40i and up

3–38 System capacity and performance

Warm restart The amount of time required for A1 Flashing is 177

seconds.
Cold restart The amount of time required for A1 Flashing is 193 seconds.
Reload restart (auto reload) The amount of time required for A1
Flashing is 218 seconds.
Boot timings: Device BCS30 RTM
DDU (8 in., 203 mm) 14:48 minutes
DDU (14 in., 356 mm) 21:35 minutes
SLM Disk 2:33 minutes
SLM Tape 12:29 minutes
Note: Timings for the SuperNode categories were obtained from RTP
FAST (First Application Systems Test) Laboratory.

Unscheduled system downtime – NT40

For BCS30, the following timings have been recorded for a typical DMS
100 with an NT40 processor:
Note: Timings for NT40 were obtained from RTP FAST (First
Application Systems Test) Laboratory.

Warm restart Event BCS30 RTM

SOS :31
Logs Start 1:01
A1 Flashing 2:33
Perminct 2:14
1st Login 3:04
1st DDU Insv 2:14
AMA Active 2:17
Cold restart Event BCS30 RTM
SOS :27
Logs Start :57
A1 Flashing 2:56
Perminct 2:40
1st Login 3:03
1st DDU Insv 2:31
AMA Active 2:37
Reload restart Event BCS30 RTM

PLN-5001-001i Standard 02.02 April 1997

 System capacity and performance 3–39

SOS :34
Logs Start 1:13
A1 Flashing 4:08
Perminct 3:46
1st Login 4:15
1st DDU Insv 3:13
AMA Active 4:15
Boot timings Device BCS30 RTM
DDU (8 in., 203 mm) 4:36
DDU (14 in., 356 mm) 6:33
MTD 15:09
Scheduled system downtime
Reloads from the system magnetic tape via the Batch Change Supplement
(BCS) process are used to update the DMS-100 Family software. The new
software is loaded in the inactive CPU, while the active CPU is still
processing calls. The manual activity switch and the restart procedure are
initiated. In a typical DMS-100 Family System, the system downtime (the
period of time from the commencement of the activity switch until dial tone
is returned on all line peripherals) is estimated to be less than 10 minutes.

Table 3–14
DMS SuperNode and DMS-100 family PCP failure rates
Product Predicted failure
equipment Card Card rate per million
code location description hours

NT0X10AA MTM Miscellaneous Scan Card 4.06

NT0X36AA SUPRV PNL Power Control & Alarm 1.29
NT0X36AB SUPRV PNL Power Control & Alarm 1.34
NT0X51AA PDC Fuse Alarm 0.08
NT0X51AB PDC Fuse Alarm 0.05
NT0X67AA IOC I/O Control Term 0.44
NT0X70AA TM Trunk Module Processor 1.91
NT0X89AA ALARM Data Link Control 0.07
NT0X89AB ALARM Data Link Control 0.05
NT0X91AA FSP Alarm & Converter Drive 0.48
NT0X91AB FSP Converter Drive 0.13
—continued—

DMS-100 International Technical Specification BCS40i and up

3–40 System capacity and performance

Table 3–14
DMS SuperNode and DMS-100 family PCP failure rates(continued)
Product Predicted failure
equipment Card Card rate per million
code location description hours

NT0X91AD FSP Converter Drive & Protection 0.52

NT0X91AE FSP Converter Drive & Protection 0.52
NT0X93AA FAN 48V to 24V Fan Inverter 1.70
NT1X00AA MTM 102 Test Trunk 2.15
NT1X00AB MTM 102 Test Trunk 1.42
NT1X00AC MTM/OAU Receiver Off-hook Tone 1.56
NT1X31AA MTM Conference Circuit 4.00
NT1X33AA CMC CMC Processor Interface 3.51
NT1X33BA CMC CMC Processor Interface 1.81
NT1X34AA CMC CMC Outgoing Controller 4.64
NT1X34BA CMC CMC Outgoing Controller 4.59
NT1X35AA CMC CMC Incoming Controller 4.66
NT1X35BA CMC CMC Incoming Controller 4.60
NT1X36AA CMC CMC Peripheral Interface 5.62
NT1X36AB CMC CMC Peripheral Interface Timing 5.64
NT1X36BB CMC CMC Peripheral Interface 5.64
NT1X37AA CMC CMC Common Control 2.23
NT1X37BA CMC CMC Common Control 3.20
NT1X42AA CPU E2A Telemetry Service Interface 0.66
NT1X43AA CPU Processor Program Store Port 3.41
NT1X43AC CPU Processor Program Store Port 3.41
NT1X43BC CPU Processor Program Store Port 3.41
NT1X43BD CPU Processor Program Store Port 3.70
NT1X43CA CPU Processor Program Store Port 4.62
NT1X43DA CPU Processor 8MW Program Store Port 2.46
NT1X44AA CPU Processor Stack 6.86
NT1X44BA CPU Processor Stack 6.90
—continued—

PLN-5001-001i Standard 02.02 April 1997

 System capacity and performance 3–41

Table 3–14
DMS SuperNode and DMS-100 family PCP failure rates(continued)
Product Predicted failure
equipment Card Card rate per million
code location description hours

NT1X44BB CPU Processor Stack 6.63

NT1X44DA CPU Processor Stack (4KW) 2.70
NT1X45AA CPU Processor A.L.F. 3.28
NT1X45BA CPU Processor A.L.F. 3.34
NT1X45BB CPU Processor A.L.F. 6.63
NT1X45DA CPU Processor A.L.F. 1.99
NT1X46AA CPU Processor ROM 8.16
NT1X46BA CPU Processor ROM 7.68
NT1X46BB CPU Processor ROM 9.04
NT1X46CA CPU Processor 8K ROM 6.36
NT1X46CB CPU Processor 8KW ROM 6.61
NT1X46CC CPU Processor 8KW ROM 6.37
NT1X46CD CPU Processor 8KW ROM 2.57
NT1X46DA CPU Processor 8KW ROM 2.54
NT1X47AA CPU Processor Timing & Control 3.33
NT1X47BA CPU Processor Timing & Control 3.58
NT1X47BB CPU Processor Timing & Control 3.17
NT1X47DA CPU Processor Timing & Control 2.77
NT1X48AA CPU Processor Maintenance 3.28
NT1X48BA CPU Processor Maintenance 3.58
NT1X48CA CPU Remote Control Processor Maintenance 6.05
NT1X48DA CPU Processor Maintenance 2.07
NT1X49BA CPU Unbalanced Data Port Extender 0.58
NT1X49DA CPU Unbalanced Data Port Extender 0.60
NT1X50AB CPU Balanced Data Port Extender 2.29
NT1X50BB CPU Balanced Data Port Extender 2.29
NT1X50DA CPU Balanced Data Port Extender 2.06
—continued—

DMS-100 International Technical Specification BCS40i and up

3–42 System capacity and performance

Table 3–14
DMS SuperNode and DMS-100 family PCP failure rates(continued)
Product Predicted failure
equipment Card Card rate per million
code location description hours

NT1X51AA CPU CMC Interface 2.11

NT1X51BA CPU CMC Interface 1.21
NT1X51DA CPU CMC Interface 1.51
NT1X52AA CPU Processor Termination 4.45
NT1X53AA CC 4K ROM Extender 2.11
NT1X53BA CPU 4K ROM Extender 1.99
NT1X53BB CC 4K ROM Extender 7.75
NT1X54AA MTM Jack End Trunk 1.32
NT1X55AA IOC Disk Drive Controller 7.14
NT1X55AB IOC Disk Drive Controller 8.00
NT1X55DA IOC 8-in. Disk Drive Controller 3.56
NT1X62AA CMC I/O Message Controller 6.43
NT1X62AB CMC I/O Message Controller 5.65
NT1X62BB CMC I/O Message Controller 6.27
NT1X62CA CMC I/O Message Controller 5.65
NT1X67AA IOC I/O Terminal Controller 6.06
NT1X67AB IOC I/O Terminal Controller 6.84
NT1X67BB IOC I/O Terminal Controller 6.84
NT1X67BC IOC I/O Terminal Controller 6.89
NT1X67BD IOC I/O Terminal Controller 4.07
NT1X67DB CC BIT Synchronous Data Link Controller 3.79
NT1X68AA IOC Magnetic Tape Interface 4.93
NT1X68AB IOC Nine-Track Tape Controller 5.08
NT1X68AC IOC Nine-Track Tape Controller 5.17
NT1X68BB IOC Nine-Track Tape Controller 5.08
NT1X68BC IOC Cook Nine-Track Controller 5.08
NT1X68BD IOC 9-Track Tape Contr. (HP & Cook) 5.08
—continued—

PLN-5001-001i Standard 02.02 April 1997

 System capacity and performance 3–43

Table 3–14
DMS SuperNode and DMS-100 family PCP failure rates(continued)
Product Predicted failure
equipment Card Card rate per million
code location description hours

NT1X75AA MTM Digital Recorded Ann. Controller 2.49

NT1X75BA MTM Enhanced Digital Recorded 2.76
Announcement Controller
NT1X76AA MTM DRA Standard Ann. (English) 15.24
NT1X76AB MTM DRA Standard Ann. (English) 12.06
NT1X76AE MTM DRA Standard Ann. (English) 4.18
NT1X76BA MTM DRA Standard Ann. (French) 14.08
NT1X76CA MTM Mech Credit Card Service From Memory 22.34
NT1X77AA MTM DRA Recorded Memory 3.82
NT1X78AA IOC Power Converter 3.84
NT1X79AA MTM DRA (Electrical Erasable Prom) 6.03
NT1X89AA IOC Multiprotocol Controller 7.09
NT1X90AA MTM Test Signal Generator 7.82
NT2X01AA MTM Automatic Identification of Outward 6.73
Dialing Data Rec C25
NT2X02AA RLM Line Drawer I/F Card 1.57
NT2X03AA RLM Power Converter 1.01
NT2X05AA RLM Power Converter 4.43
NT2X05AB RLM Power Converter 5.20
NT2X05AC RLM Power Converter 4.57
NT2X06AB NM, DCM Power Converter 2.65
NT2X06BB NM, DCM Power Converter 2.05
NT2X07AB NM, DCM Power Converter 3.14
NT2X09AA TM Multi-Output Power Converter 3.33
NT2X10AA MTM Line Test Unit Analog Card 3.16
NT2X10AB MTM Line Test Unit Analog Card 3.49
NT2X11AA MTM Line Test Unit Digital Card 2.09
NT2X11AC MTM/RMM Line Test Unit Digital Card 2.05
—continued—

DMS-100 International Technical Specification BCS40i and up

3–44 System capacity and performance

Table 3–14
DMS SuperNode and DMS-100 family PCP failure rates(continued)
Product Predicted failure
equipment Card Card rate per million
code location description hours

NT2X15AA FAN Inverter Unit 1.11

NT2X16AB RLM I/O Bus Interface 1.59
NT2X17AB RLM Type A With Cutover Line Card (20 dB) 0.77
NT2X17AC RLM Type A With Cutover Line Card (20 dB) 0.80
NT2X17AD RLM Type A With Cutover Line Card (20 dB) 0.80
NT2X18AC RLM Type B Line Card 2.42
NT2X18AD RLM Type B Line Card 1.97
NT2X18AE RLM Type B Line Card 1.80
NT2X20AB RLM Ringing Bus Multiplexer 0.83
NT2X21AA RLM Terminal Addressing Interface 3.14
NT2X21AC RLM Terminal Address I/F 3.83
NT2X22AA RLM Conn Mem/Trans Mux 3.32
NT2X22AB RLM Conn Mem/Trans Mux 4.74
NT2X23AA RLM Receive Mux 2.74
NT2X24AB RLM Signaling Processor 5.72
NT2X25AB RLM Signaling Processor I/F 3.84
NT2X26AA RLM Main Processor 8.25
NT2X26AB RLM Master Processor 11.26
NT2X27AA RLM Ringing Generator Interface 3.33
NT2X27AB RLM 20Hz Ringing Generator 2.08
NT2X27AC RLM Ringing Generator Harmonic MF 3.55
NT2X27AD RLM Ringing Generator Synchromonic MF 3.55
NT2X27AE RLM Ringing Generator Synchromonic MF 3.55
NT2X32AA DCM DCM Processor 2.26
NT2X33AA DCM DCM Processor 4.25
NT2X33AB DCM, RLM DCM Processor 2.50
NT2X34AA DCM, RLM Peripheral Message Processor 1.80
—continued—

PLN-5001-001i Standard 02.02 April 1997

 System capacity and performance 3–45

Table 3–14
DMS SuperNode and DMS-100 family PCP failure rates(continued)
Product Predicted failure
equipment Card Card rate per million
code location description hours

NT2X35AA DCM DCM Line 3.55

NT2X35AB DCM DCM Interface 1.17
NT2X36AA DCM/RLM Network Interface 6.57
NT2X36AB DCM Network Interface w/XPCM Suppress Cap 7.67
NT2X37AA DCM DCM Tone Supply 3.91
NT2X37AB DCM DCM Tone 2.18
NT2X38AA DCM DCM Signaling 4.55
NT2X38AB DCM DCM Signaling 4.31
NT2X38AC DCM DCM Signaling 4.46
NT2X38AD DCM DCM Signaling 4.31
NT2X41AA MTM Office Alarm Circuit #1 0.30
NT2X42AA MTM Office Alarm Circuit #2 0.53
NT2X43AB MTM Office Alarm 2.00
NT2X45AA TM Trunk Module Network Interface 4.83
NT2X45AB TM Trunk Module Network Interface 4.79
NT2X47AA TM Trans TST Modular Controller 7.22
NT2X47AB TM Trans Test Unit 8.17
NT2X47AC TM Trans Test Unit Controller 3.96
NT2X47AD TM Trans Test Unit Controller 4.42
NT2X47BA TM TTU Controller (A-Law) 8.23
NT2X48AA TM Digital 4 Channel MF Receiver 2.59
NT2X48AB TM Digital 4 Channel Receiver 2.79
NT2X50AB TM Minibar Driver 2.41
NT2X53AA TM TM/Control 1.61
NT2X55AA MTM SD Card II 0.77
NT2X56AA MTM TTM Digital Filter 4.52
NT2X56AB MTM TTM Digital Filter 1.69
—continued—

DMS-100 International Technical Specification BCS40i and up

3–46 System capacity and performance

Table 3–14
DMS SuperNode and DMS-100 family PCP failure rates(continued)
Product Predicted failure
equipment Card Card rate per million
code location description hours

NT2X56BA MTM Digital Filter (A-Law TTU) 4.89

NT2X57AA MTM SD Card I 2.56
NT2X57AB MTM Signal Distribution Card 2.51
NT2X59AA TM Group CODEC DMS-200 2.90
NT2X59AB TM Group CODEC DMS-300 5.00
NT2X63AA MTM M/F Receiver 2.12
NT2X65AA TM CAMA Position Signal Trunk 5.54
NT2X66AA TM CAMA Suspension & Calls Waiting 1.23
NT2X70AA CPU, CMC Power Converter 2.87
NT2X70AB CPU, CMC Power Converter 2.82
NT2X70AC CPU, CMC Power Converter 3.19
NT2X70AD CPU, CMC Power Converter 3.22
NT2X70BA CPU, CMC Power Converter 2.89
NT2X71AA MTM Transmission Termination Trunk 3.00
NT2X72AA TM 4-Wire E&M, Type l Interface 5.85
NT2X72AB TM 4-Wire E&M 600 Ohm Echo Sup.Control 5.94
NT2X72AC TM 4-Wire E&M, Echo Control, low gain 5.93
NT2X75AA MTM Loop Around Test Line 1.92
NT2X77AA TM Compromise Bal. Network 900 Ohm 0.10
NT2X77AB TM Compromise Bal. Network 600 Ohm 0.11
NT2X77AC TM Compromise Bal. Network 900 Ohm Fix 0.55
NT2X77AD TM Compromise Bal. Network 600 Ohm Fix 0.06
NT2X78AA TM Trunk 4 Wire SF Signal 7.95
NT2X80AA TM Precision Bal. Network 0.10
NT2X81AA TM Trunk 2-Wire E&M 900 Ohm 2.15
NT2X81AB TM Trunk 2-Wire E&M 600 Ohm 5.53
NT2X82AA TM Trunk 2-Wire Incoming MF/DP 5.88
—continued—

PLN-5001-001i Standard 02.02 April 1997

 System capacity and performance 3–47

Table 3–14
DMS SuperNode and DMS-100 family PCP failure rates(continued)
Product Predicted failure
equipment Card Card rate per million
code location description hours

NT2X83AA TM Trunk 2-Wire Outgoing DP 6.56

NT2X85AA TM Recording Comp. Trk Hi-Lo Coin 3.96
NT2X86AA TM Toll Switch Trunk 3.64
NT2X88AA TM Trunk 4-Wire E&M 600 Ohms 2.52
NT2X90AA MTM Trunk LTD NE-14 or CALRS 4.27
NT2X90AB MTM Incoming/Outgoing Test Trunk 4.83
NT2X90AC MTM Incoming/Outgoing Test Trunk 4.90
NT2X90AD MTM Incoming/Outgoing Test Trunk 4.06
NT2X92AA TM 2-Wire Outgoing, MF, RB 5.79
NT2X95AA TM 2-Way PBX Trunk DID/DOD 2.45
NT2X96AA TM PCM Level Meter 4.29
NT2X98AA TM 2-Wire Incoming MF/DP RB 4.78
NT3X02AA TM TOPS Controller 2.72
NT3X03AA TM TOPS Digital Signal Processor 1.54
NT3X04AA TM TOPS Digital Signal Processor 5.34
NT3X06AA TM 2 W OTG TRK CCT AE/3CL 3.95
NT3X07AA TM 2 W INC TRK CCT 6.39
NT3X08AA MTM ACTS – Digitone Service 5.48
NT3X09AA TM Remote Metallic Test Access 1.82
NT3X09BA TM Remote Metallic Test Access 4.07
NT3X13AA CMC Master Clock Generator 3.48
NT3X13BA CMC Master Clock Generator 3.43
NT3X14AA CMC Synchronizable Master Clock Counter 3.27
NT3X14BA CMC Synchronizable Master Clock Counter 3.27
NT3X14BB CMC Synchronizable Master Clock Counter 3.63
NT3X14BC CMC Synchronizable Clock Controller 2.09
NT3X15AA CMC Synchronizable Master Clock Counter 3.35
—continued—

DMS-100 International Technical Specification BCS40i and up

3–48 System capacity and performance

Table 3–14
DMS SuperNode and DMS-100 family PCP failure rates(continued)
Product Predicted failure
equipment Card Card rate per million
code location description hours

NT3X15AB CMC Synchronizable Master Clock Counter 3.65

NT3X15BA CMC Synchronizable Master Clock Counter 3.57
NT3X15BB CMC Synchronizable Master Clock Oscillator 2.73
NT3X15CA CMC Stratum 3 Synchronizable Master Clock 3.00
NT3X15DA CMC Stratum 2 Synchronizable Master Clock 3.01
NT3X16AA CMC Stratum 2 Oscillator 2.02
NT3X17AA NM Network Incoming Crosspoint 4.40
NT3X18AA NM Network Outgoing Crosspoint 4.46
NT3X19AA NM Network Speech Interface 4.81
NT3X20AA NM Network Test Access 2.72
NT3X21AA NM Network Bus Interface 1.11
NT3X22AA NM Network I/O/Interface 3.74
NT3X22AB NM Network I/O/Interface 5.61
NT3X23AA NM Network X-Point Controller 5.98
NT3X23AB NM Network Signaling Controller 5.10
NT3X24AA NM Network Clock 2.39
NT3X34AA PS Single Ended Memory Bus Terminator 0.66
NT3X35AB PS Differential Memory Bus Terminator 0.68
NT3X36AB PS Differential Bus Interface 1.94
NT3X36AC PS Differential Bus Interface 2.21
NT3X36BB PS Differential Memory Bus Interface 1.94
NT3X36BC PS Differential Memory Bus Interface and 2.21
Terminator
NT3X37AA PS Single Ended Memory Bus Terminator 0.95
NT3X37AC PS Single Ended Memory Bus Interface 1.24
NT3X37BA PS Single Ended Memory Bus Interface 0.54
NT3X37BC PS Single Ended Memory Bus Interface and 0.81
Terminator
—continued—

PLN-5001-001i Standard 02.02 April 1997

 System capacity and performance 3–49

Table 3–14
DMS SuperNode and DMS-100 family PCP failure rates(continued)
Product Predicted failure
equipment Card Card rate per million
code location description hours

NT3X38AA PS Memory Controller 4.36

NT3X39AA PS 16K MOS Memory 14.26
NT3X40AA CPU 64K MOS Memory 13.79
NT3X40BA CPU 64K MOS Memory 13.80
NT3X42AA CPU LM Word Memory Control 3.48
NT3X42BA CPU LM Word Memory Control 3.39
NT3X4302 CPU (IMW) Memory Back Panel Terminator 1.97
NT3X4303 CPU Processor Back Panel Terminator 0.38
NT3X4304 CMC CMC/IOC Back Panel Terminator 0.40
NT3X4307 PS PS Controller Back Panel Terminator 0.49
NT3X4309 CCC 16 MW Memory BP Termination 0.63
NT3X47AA RLM RLM Message Controller 6.83
NT3X48AA RLM RLM T1 Line I/F 4.95
NT3X49AA RLM RLM Extension MEM 8.15
NT3X51AA RLM RLM Service Shelf Interface 2.99
NT3X65AA DCM Echo Suppressor 5.71
NT3X67AA TM 6 Party Conference Circuit 1.78
NT3X68AA TM Perm Sig & Conf Tone Generator 0.85
NT3X68AB TM MF Dual Tone Generator 0.85
NT3X68AC MTM Call Waiting Tone Generator 0.85
NT3X70AA NM Network Crosspoint 2.66
NT3X71AA NM Network Test Code 1.28
NT3X72AA NM Network Serial Port Interface 3.91
NT3X72AB NM Network Serial Port Interface 3.61
NT3X73AA NM Network Serial to Parallel Formatter 3.66
NT3X74AA NM Network Control Processor (E-Core) 2.77
NT3X74AB NM Network Control Processor (E-Core) 2.46
—continued—

DMS-100 International Technical Specification BCS40i and up

3–50 System capacity and performance

Table 3–14
DMS SuperNode and DMS-100 family PCP failure rates(continued)
Product Predicted failure
equipment Card Card rate per million
code location description hours

NT3X74BA NM Network Control Processor (CP) 4.91

NT3X74BB NM Network Control Processor 5.56
NT3X75AA NM Network P-Side Message Processor 2.09
NT3X75BA NM Network P-Side Message Processor 2.97
NT3X76AA NM Network Clock 2.63
NT3X76AC NM Network Clock 5.25
NT3X82AA MTM OAU Dead System with Unique Audible 2.75
NT3X82AB MTM OAU Dead System with Common Aud. 2.25
NT3X83AA MTM OAU Alarm Transfer 3.05
NT3X84AA MTM OAU Alarm Sending 2.50
NT3X85AA MTM OAU Alarm Grouping 2.65
NT3X86AA NM Network Parallel to Serial Formatter 5.03
NT3X91AA TM Remote Office Test Line 2.71
NT3X93AA PS 256K Memory 6.00
NT3X94AA PS 4 MW Memory Controller 3.70
NT4X01BA TOPS TOPS B01 Control Board 7.67
NT4X01BB TOPS Blind Operator Interface 2.67
NT4X08AA TOPS Attendant Console Main Circuit Pack 5.70
NT4X21AA TOPS Main Set Circuit Pack (Basic) 3.35
NT4X21AB TOPS Main Set (Display) 4.68
NT4X21AC TOPS Button Add-On 4.02
NT4X21AD TOPS Handsfree Auto Answer 2.51
NT4X23AA TOPSDTU Digital Test Unit 11.93
NT4X25AA TOPS Data Unit Sync/Asyn LS, Variable 6.27
NT4X25AB TOPS Data Unit Sync/Asyn LS 1.14
NT4X25AD TOPS Data Unit Rack Mount LS 6.98
NT4X25AM TOPS COAX Eliminator CUI/F 7.72
—continued—

PLN-5001-001i Standard 02.02 April 1997

 System capacity and performance 3–51

Table 3–14
DMS SuperNode and DMS-100 family PCP failure rates(continued)
Product Predicted failure
equipment Card Card rate per million
code location description hours

NT4X25BA TOPS Dial/Key 5.60

NT4X25BB TOPS Switch Interface 0.92
NT4X25BC TOPS Low Speed Main PCB Assy. 4.44
NT4X25BE TOPS High Speed Main PCB Assy. 4.84
NT4X25BR TOPS Data Unit COAX PCB Assy. 5.51
NT4X25CH TOPS Low Speed Rack Mount Autoloop Back 4.79
NT4X26AA TOPS Subscriber Access Multiplexer (SAM) 4.45
NT4X26AB TOPS SAM-1A (TF) 7.67
NT4X30AA TOPS P1 Business Set (W78) 4.61
NT4X60AA TOPS TOPS Power Supply 2.16
NT4X60AB TOPS TOPS Power Supply 2.18
NT4X61AA AOSS Audio Control 2.79
NT4X62AA AOSS Data Control 3.81
NT4X63AB AOSS Keyboard Assembly 0.10
NT4X63AC AOSS Module Controller 3.08
NT4X63AD AOSS Display Unit 4.02
NT4X63AE AOSS Row and Column Control 1.39
NT4X63BD AOSS Display Controller 1.80
NT4X79AA CCC 16 MW Memory Control 4.93
NT4X80AA CCC IMW Memory 8.46
NT5X25AA TM 1 WY TRK OUTG GRD ST DP/DTMFOR 6.94
INCM LP OR GRD ST 20Hz RG
NT5X29AB MTM Service Observing Circuit 4.80
NT5X29AC MTM Audio Answer Detect MF CKT 1.96
NT5X30AA MTM l0l Communication Test Line CKT 2.77
NT5X48AA TOPS 480Hz & 620Hz Tone Generator (TOPS) 0.20
NT5X48AB TOPS Tone Amplifier (TOPS) 0.49
NT5X48AC TOPS Tone Monitor 0.38
—continued—

DMS-100 International Technical Specification BCS40i and up

3–52 System capacity and performance

Table 3–14
DMS SuperNode and DMS-100 family PCP failure rates(continued)
Product Predicted failure
equipment Card Card rate per million
code location description hours

NT5X49AA TOPS Converter CPNTA (TOPS) 1.07

NT5X5201 TM Component Assembly 0.05
NT5X5202 TM Component Assembly 0.09
NT5X67AA DCM DCM Cutover CKT 2.12
NT5X6901 MIS Inactive System Timing 0.03
NT6X17AA LCM Standard Line CCT Type A with Cutover 1.20
NT6X17AB LCM Standard Line CCT Type A with Cutover 1.15
(20 dB)
NT6X17AC LCM Standard Line CCT Type A with Cutover 0.57
NT6X18AA LCM Line Card Type B 0.78
NT6X18AB LCM Line Card Type B with +48V 0.87
NT6X19AA LCM Message Waiting Line Card 0.93
NT6X20AA LCM Message Waiting Converter Card 0.62
NT6X21AA LCM P-Phone Line Card 15 KFT 1.13
NT6X21AB LCM P-Phone Line Card 15 KFT 0.97
NT6X21AC LCM P-Phone Line Card 15 KFT 1.08
NT6X23AA LCM Converter 1.02
NT6X30AA LCM Ringing Generator 9.86
NT6X30AB LCM Ringing Generator CP 10.95
NT6X36AA LCM FSP Alarm 0.90
NT6X38AA RLM Ringing Control 10.21
NT6X40AA LGC/DTC DS-30 Network Interface 6.26
NT6X40AB LGC/DTC DS-30 Network Interface 5.94
NT6X40AC LGC/DTC DS-30 Network Interface 5.48
NT6X40BA LGC/DTC SCM DS-30 Interface CP 2.46
NT6X41AA LGC/DTC Speech Bus Formatter 5.12
NT6X42AA LGC/DTC Channel Supervision MSG 4.43
NT6X43AA LGC/DTC MSG Interface 3.59
—continued—

PLN-5001-001i Standard 02.02 April 1997

 System capacity and performance 3–53

Table 3–14
DMS SuperNode and DMS-100 family PCP failure rates(continued)
Product Predicted failure
equipment Card Card rate per million
code location description hours

NT6X44AA LGC/DTC Time Switch 3.42

NT6X44AB LGC/DTC Time Switch 3.72
NT6X44CA LGC/DTC Time Switch A/MU 4.17
NT6X45AA LGC/DTC LGC/DTC Processor 8.12
NT6X45AC LGC/DTC LGC/DTC Processor 4.39
NT6X45AE LGC/DTC LGC/DTC Processor 4.29
NT6X45AF LGC/DTC LGC/DTC Processor CP 5.02
NT6X45CA LGC/DTC SMS Processor CP 5.20
NT6X46AA LGC/DTC SP Memory Plus 12.58
NT6X46AB LGC/DTC SP Memory Plus 4.53
NT6X46AC LGC/DTC SP Memory Plus 3.15
NT6X46BA LGC/DTC SP Memory Plus 3.97
NT6X47AA LGC/DTC MP Memory 16.73
NT6X47AB LGC/DTC MP Memory Plus 8.74
NT6X48AA LGC/DTC DS-30 LCM Interface 4.18
NT6X49AA LGC/DTC DS-1 MUX Multiplexer 2.22
NT6X50AA LCM DS-1 Interface 3.84
NT6X51AA LCM LCM Processor 3.95
NT6X51AB LCM LCM Processor 8.21
NT6X52AA LCM Digroup Controller Card 7.07
NT6X53AA LCM Power Converter 5V/15V 3.99
NT6X54AA LCM Bus Interface 2.20
NT6X60AA RLCM Ringing Generator 9.98
NT6X65AA MSB CCIS Signaling Terminal 9.24
NT6X66AA MSB CCST Signaling Terminal 3.64
NT6X67AA MSB Signaling Terminal Buffer 0.62
NT6X68AA MSB Signaling Terminal Interface 1.09
—continued—

DMS-100 International Technical Specification BCS40i and up

3–54 System capacity and performance

Table 3–14
DMS SuperNode and DMS-100 family PCP failure rates(continued)
Product Predicted failure
equipment Card Card rate per million
code location description hours

NT6X68AB MSB Signaling Terminal Interface 1.94

NT6X68AC MSB Signaling Terminal Interface 1.45
NT6X68AD MSB Signaling Terminal Interface 1.47
NT6X69AA MSB CPP Message Protocol and Tone 4.25
NT6X69AB MSB CPP Message Protocol and Tone 4.88
NT6X70AA MSB CCIS Continuity Card 1.93
NT6X71AA LCM Data Line Card 1.14
NT6X71AB LCM Data Line Card 1.96
NT6X72AA RCE Host Link Formatter 4.03
NT6X73AA RLCM Link Control Card 4.98
NT6X74AA RLCM RMM Control Card 9.23
NT6X74AB RLCM RMM Control Card 3.72
NT6X75AA RLCM ESA Tone and Clock Card 1.90
NT6X76AA LCM Asynch Intrfc Ln Crd (AILC) (2 Slots) 0.68
NT6X79AA CPC Tone Generator 1.80
NT6X80AA SCM SCM Pad/Ring Card 2.05
NT6X80BA SMR/SMS SCM Pad/Ring Card 2.51
NT6X81AA SCM SCM A Bit/B Word 6.22
NT6X85AA SCM DS-1 I/F (SLC-96) 4.67
NT6X85AB SCM DSI I/F for SLC-96 4.65
NT6X86AA SCM A-Bit Message Card 3.64
NT6X92AA TM UTR 12.08
NT6X92BA LGC/DTC UTR 6.26
NT6X92BB LGC/DTC UTR 7.59
NT6X99AA LCM Tester Line Card 1.87
NT8X02AA OPM Battery Charger Controller 2.36
NT8X12AA DSN Network Port CP 5.79
—continued—

PLN-5001-001i Standard 02.02 April 1997

 System capacity and performance 3–55

Table 3–14
DMS SuperNode and DMS-100 family PCP failure rates(continued)
Product Predicted failure
equipment Card Card rate per million
code location description hours

NT8X13AA DSN Crosspoint CP 2.89

NT8X14AA DSN Test Code CP 1.59
NT9X12AA CM CPU Port 12.67
NT9X12AB CM CPU Port 12.73
NT9X13BA CCC CPU CP 18.49
NT9X13BB CCC CPU (Static RAM) CP 18.48
NT9X13BC CCC CPU (Static RAM) CP 18.48
NT9X13CA CCC CPU Plus 4 Mb CP 12.10
NT9X13DA CCC CPU 16 CP 6.14
NT9X13DB MS CPU (16MHz) 16.02
NT9X14AA CCC Memory 4M CP 0.95
NT9X14BB CCC Memory 6M CP 8.00
NT9X15AA CCC Mapper CP 6.09
NT9X17AA CCC MS-4 Port CP 14.09
NT9X20AA CCC DS5 Paddle board CP 5.21
NT9X21AA CCC CM Bus Terminator Paddle board 1.39
NT9X23AA CCC DS30-4 Port Paddle board 4.13 2.67
NT9X23BA MS DS30 4 Port Paddle Brd (STP) CP 3.83
NT9X26AA CCC Remote Terminal Interface CP 2.54
NT9X27AA CCC CM Bus Extender 2.30
NT9X27BA CCC CM Bus Extender 0.79
NT9X30AA CCC +5 Volt Power Converter 1.84
NT9X31AA CCC –5 Volt Power Converter 2.27
NT9X32AA MS MS Load CP 1.10
NT9X44AA CCC System Load Unit 26.01
NT9X46AA CCC Parallel Port Interface Paddle board 0.69
NT9X47AA CCC +12 Volt Power Converter 1.84
—continued—

DMS-100 International Technical Specification BCS40i and up

3–56 System capacity and performance

Table 3–14
DMS SuperNode and DMS-100 family PCP failure rates(continued)
Product Predicted failure
equipment Card Card rate per million
code location description hours

NT9X49CA CCC MS P-Bus Terminator 76 2.27

NT9X52AA CCC T-Bus Access CP 1.54
NT9X53AA CCC MS Clock CP 8.13
NT9X54AA CCC MS External Clock Interface 2.30
NT9X54AB MS Ext. Clock Interface (Stratum 212.5) 2.33
NT9X73AA STP LMS-FBUS Rate Adapter 10.34
NT9X74AA STP FBUS Repeater-Terminator 3.18
NT9X75AA STP CPU-FBUS Interface CP 10.80
NT9X76AA STP STP Signaling Terminal CP 9.58
NT9X78AA STP STP DS-0A Interface Paddle board 4.45
NT9X79AA STP FBUS Extension Paddle board 0.53
NT9X79BA STP FBUS Extension CP-Terminations 0.81
End

PLN-5001-001i Standard 02.02 April 1997

 System capacity and performance 3–57

Table 3–15
DMS SuperNode reliability performance (hardware failures only)
DMS-100 parameter Predictions

System downtime 0.35 minutes per year

24 digital trunk downtime due to 5.50 minutes per year
hardware failures.
Single line downtime due to hardware 4.20 minutes per year
failures.
Probability of cutoff call 0.03 x 10–5 line to line (LCM)
0.03 x 10–5 line to trunk
0.03 x 10–5 trunk to trunk
Probability of Reliability Related 0.20 x 10–4 (L to L)
Ineffective Machine Attempts 0.20 x 10–4 (L to T)
P(RRIMA) 0.20 x 10–4 (T to T)

Table 3–16
Assumptions

1 The MTTR is three hours.

2 The duplicated equipment coverage is 99.9% for peripheral
equipment.
3 3-minute call-holding time is used for all cutoff call calculations.
4 P(RRIMA) and “Probability of Cut-off Calls” have been calculated
according to the equations in Appendices A and B.

DMS-100 International Technical Specification BCS40i and up

 4–1

Features
This chapter summarizes the generic features and capabilities of the
DMS-100 International switching system. The specific features and
capabilities provisioned on a DMS-100 International switching system vary
depending on the market in which the system is provisioned, the application
of the system, and the hardware and software provisioned. For more
detailed information on DMS-100 International features and provisioning
rules, consult the following Northern Telecom Practices (NTPs):
• DMS-100 Family Provisioning Manual, 297-1001-450
• DMS-100 International Feature Description Manual, 291-1001-801i

Features common to residence and business

Individual line
An individual line is a line arranged to serve a single main station, although
additional stations can be connected to the line as extensions of the main
station. Individual lines provide telephone service to residence and business
customers. The system can automatically identify the directory number
assigned to a line, based upon the originating appearance to the system.
Service-related features such as manual originating, dial pulse dialing, or
dual tone multifrequency (DTMF) dialing assigned to individual lines may
vary from line to line within the DMS-100 International system.
Free terminating line service
With free terminating line service, calls from a class of lines (for example,
intra-office) or from specified trunks, to a line designed as free terminating
are not billed. Intra-office calls are screened by the system to prevent
charging of calls to lines with this feature. Inter-office calls completed to
free terminating lines may require, depending upon the incoming trunks
class, that answer supervision not be returned to the originating office.
Calls to the “official lines” of an operating company are an example of lines
which require free terminating line service.
Free number origination (FNO)
R2 toll calls from lines designated as FNO are are metered but not charged.
The FNO feature is not compatible with the line options selective charge

DMS-100 International Technical Specification BCS40i and up

4–2 Features

recording (SCR), attendant pay station (APS), subscriber premise meter

(SPM), and the hotel (HOT) line option.
Denied terminating line service (DNTR)
DNTR allows the system to deny call completions to a line. Plant
maintenance calls can be connected to lines with this restriction.
Denied originating line service (DOR)
DOR allows a line to be designated as receive-only. If an attempt is made to
originate a call on a line with the DOR option assigned, the line is routed to
treatment.
Emergency lines (free number terminating – FNT)
Any agent terminating on a line with the FNT option is not billed for the
call.
Plugged up line (PLP)
PLP is assigned to lines which are in the plugged up state (meaning the line
is suspended due to a hardware fault). Any call routing to such a line is
rerouted to trouble intercept treatment (TRBL).
Suspended service (SUS)
SUS is assigned to lines which have originating and terminating service
suspended. Any such line attempting to originate receives originating
suspended service treatment. Any agent attempting to terminate on such a
line is routed to terminating suspended service treatment (TESS).
Code restriction
In a POTS environment, restriction calls from certain originators can occur,
subject to class of service screening.
Hunting features
DMS-100 International supports the following types of hunting features:
Director number hunting (DNH)
Each line in the hunt group has its own directory number (DN). The hunt
group can be accessed by dialing the main number (Pilot DN) or by calling
the DN of one of the hunt group members. Hunting starts at the number
dialed. The number of lines hunted to find an idle line depends on the
hunting option assigned to the DNH group.
If option CIR (circular hunting) is assigned to the group, all lines in the hunt
group are hunted, regardless of the start point of hunting. If CIR is not
assigned, the default is sequential hunting (also known as linear hunting).
Sequential hunting starts at the number dialed and ends at the last number in
the hunt group. Therefore, if the pilot DN is not dialed, not all lines are
hunted.

PLN-5001-001i Standard 02.02 April 1997

 Features 4–3

Multi-line hunting
A pilot DN is associated with the hunt group. To access the group, the pilot
DN is dialed. Hunting starts with the pilot DN and ends at the last line, in
sequential order.
Distributed line hunting (DLH)
DLH is assigned to large hunt groups which require equal distribution of
calls. A pilot DN is associated with the hunt group. To access the group, the
pilot DN is dialed. Hunting starts on the subsequent line in the group, that
is, the line which was last selected.
If the line at which hunting starts is not idle due to an origination, the next
line is checked. This continues until the hunting starting point is reached.
At this point, busy tone is returned.
Additional hunting options available
Hunt options OFR (line overflow increments hardware register) and OFS
(line overflow increments software register) are available on the DMS-100
International switch.
Hunting options not available
The following hung group features are not available :
• line overflow to route (LDR)
• line overflow to DN (LOD)

Bridged night number

An incoming call for a group of lines serving a customer is normally
allocated to a free line in the group using the line hunting facility.
Termination to be used for night service can be allocated a secondary,
designated bridged night number (BNN). The BNN is assigned to the same
line equipment number (LEN) as a DN in the hunt group. Options assigned
to the base DN also apply to the associated BNN.
When the BNN is called, no hunting occurs; the BNN line is connected.
This allows connections to specific positions(s) during night periods. BNN
can be assigned to directory number hunting (DNH), multi-line hunting
(MLH), and distributed line hunting (DLH) groups. If the daytime DN is
dialed, hunting as specified for the group applies.
Several BNNs can be designated as a BNN hunt group, allowing hunting
within the group. Hunting is sequential unless the circular (CIR) option is
assigned to the BNN hunt group. The BNN group does not automatically
use the same options as the host hunt group. For example, if the host hunt
group is assigned circular hunting, the BNN group is not automatically
assigned circular hunting.

DMS-100 International Technical Specification BCS40i and up

4–4 Features

When the BNN is dialed, the associated line rings if it is idle. If the line is
busy, no hunting takes place, and busy tone is returned to the calling
subscriber. If the line belongs to a BNN hunt group, hunting occurs within
the BNN. Hunting is either sequential or circular, depending on which
option is assigned to the BNN group.
The maximum number of members for a BNN hunt group is 210. BNNs are
assigned in data tables Hunt Group and Hunt Group Member.
Dial pulse dialing
Dial pulse dialing permits a customer to send pulsed dc address signals to
the switching system. After line seizure, the system alerts the customer, by
dial tone, of its readiness to receive the dialed address information. The
system interprets the dialed digits according to the call processing feature
arrangements for the central office. The system ignores dual tone
multifrequency address signals from lines equipped only with dial pulse
dialing.
Dual tone multifrequency (DTMF) dialing
DTMF dialing permits a customer to send dual tone multifrequency address
signals to the switching system. After line seizure, the system alerts the
customer, by dial tone, of its readiness to receive the dialed address
information. The system interprets the dialed digits according to the call
processing feature arrangements for the central office. Lines equipped with
the DTMF dialing feature are also permitted to use dial pulse dialing.
Malicious call trace
Malicious call trace (MCT) is controlled by operating company
administration, and is provided subject to the legal requirements of the
country in which the DMS-100 International switch resides. This feature
allows the subscriber to request call trace on an in-progress call by entering
a designated signal. When the system receives the signal, it stores the
calling number and the time and date of the call in an MCT log report. An
alarm is generated at the originating and terminating offices.
The subscriber receiving the malicious call, having activated the feature, is
free to originate another call after going on hook. However, the originating
subscriber is held until maintenance force-releases the circuits after
operating company administration legal procedures.
The simple procedure for CEPT activation is to flash the switch-hook of the
called subscriber’s telephone set, where flash is defined as an on hook
interval of 200 msecs. to 1.2 seconds. This method accommodates both
DTMF as well as dial pulse phones.

PLN-5001-001i Standard 02.02 April 1997

 Features 4–5

Subscriber services that use the register recall signal during an off hook A-B
connection cannot be active on the subscriber’s line during call trace
activation.
Emergency cut-off
This feature provides operating company administration with a mechanism
to prevent non-essential subscriber originating calls. Operating company
administration can designate subscriber lines as essential or non-essential.
The feature is activated by entering a command at the Maintenance and
Administration Position (MAP).

Subscriber services
The following subscriber services are available on the DMS-100
International switch:
• abbreviated dialing
• call diversion
• call waiting
• cancel call waiting
• hot line
• warm line
• subscriber activated outgoing restrictions
• subscriber features denied
• no double connect
• call completion to a busy line
• selective call recording
• call transfer
• three and six way calling
• wake-up call

These subscriber services are based on the equivalent services (where

applicable) described by CEPT (Handbook on Services and Facilities
Offered to the Subscribers in Modern Telephone Systems: Sections I & II –
Services and Facilities Within the Public Network)
The following abbreviations are are used to describe the control of the
services:
AN abbreviated number
A-B calling party A connected to calling party B
BT busy tone
DT dial tone
FC facility code (identifies the service required)

DMS-100 International Technical Specification BCS40i and up

4–6 Features

IND indication: ACK (acknowledged, control accepted)

or
NACK (not acknowledged, control not
accepted)
LH lift handset
R register recall
RH replace handset
RT ringing tone
TN telephone number
* activate (when dialed at the beginning of the control
procedure)
# deactivation and erase (when dialed at the beginning of
the control procedure)
Abbreviated dialing
This feature allows a subscriber to originate a call by dialing a short code
instead of the full telephone number. The abbreviated numbers are entered
by subscribers in lists allocated by operating company administration.
When the subscriber dials the abbreviated code, the system associates it with
the assigned DN and attempts to complete the call.
The administration controls the allocation of four lists or groups to a
subscriber. The sizes are as follows:
• group 1 0 to 9 inclusive
• group 2 00 to 29 inclusive
• group 3 00 to 59 inclusive
• group 4 00 to 99 inclusive
This service is controlled by operating company administration, and
activated by service order.
The subscriber is can add, register, change, delete, query, or use a number
from the abbreviated dialing lists.
The subscriber activation procedural abbreviations are standard usages in the
CEPT recommendations, and are for use with push-button MF phones only.
Programming (a maximum of 18 digits can input for each abbreviated
number):
LH DT * FC * AN * TN # IND RH
Erasure:
LH DT # FC * AN # IND RH

PLN-5001-001i Standard 02.02 April 1997

 Features 4–7

Interrogation:
LH DT * # FC * AN * TN # IND RH
Usage:
LH DT ** AN RT A-B RH
Withdrawal: via service order by operating company administration.
Call diversion
Call diversion allows a subscriber to request rerouting of all calls to an
announcement, another subscriber, or an operator. The following types of
call diversion can be activated:
• call diversion to operator (CDO). CDO intercepts calls to the designated
line and reroutes them to an operator.
• call diversion to announcement (CDA). CDA intercepts calls to the
designated line and reroutes them to an announcement.
• call diversion on busy (CDB). CDB reroutes calls to the designated line
to a second subscriber line, if the designated subscriber line is busy.
• call diversion to subscriber (CDS). CDS reroutes calls to the designated
line to a second subscriber line. The subscriber programs the number of
the second line.
• call diversion fixed (CDF). CDF reroutes calls to the designated line to a
second subscriber line. The operating company programs the number of
the second line.
• do not disturb (IDND). IDND reroutes all calls to the designated
subscriber to treatment.
Call diversion assignment and activation
Call diversion services are assigned by operating company administration
using service orders. The features can be assigned with a state of active or
inactive. If the status is active, it is the administration’s responsibility to
ensure that valid routing information is provided for the diversion.
A subscriber can program CDA, CDS or CDB on activation. For CDB or
CDS, the subscriber enters the target number. For CDA, the subscriber
enters a 1 or 2 digit announcement code.
Subscriber programming of CDO, CDF and IDND is not allowed.

DMS-100 International Technical Specification BCS40i and up

4–8 Features

The dialing procedures for programming, activation, deactivation and

interrogation of call diversion features are:
CDO/CDF/IDND
Activation:
LH DT * SC # ACK RH
Deactivation:
LH SDT # SC # ACK RH
Interrogation:
LH SDT * # SC # IND RH
CDS/CDB
Activation with programming:
LH DT * SC * TN # ACK RH
Activation:
LH DT * SC # ACK RH
Deactivation:
LH SDT # SC # ACK RH
Interrogation:
LH SDT * # SC * NN # IND RH
CDA
Activation with programming:
LH DT * SC * NN # ACK RH
Activation:
LH DT * SC # ACK RH
Deactivation:
LH SDT # SC # ACK RH
Interrogation:
LH SDT * # SC * NN # IND RH
Call waiting features
Call waiting can be assigned to a line by operating company administration
and can be turned off on a per-call basis by cancel calls waiting. If it is to be
turned off and on as required by the subscriber for other cases, then no
double connect service can be used.
The following dialing sequences control call waiting service:
• R SDT 0
The call waiting or the call on hold is disconnected.

PLN-5001-001i Standard 02.02 April 1997

 Features 4–9

• R SDT 1
The original call is disconnected and the waiting call connected.
• R SDT 2
The active call is put on hold and the waiting or held call connected.
This can be repeated to switch between the two calls.
• R SDT 3
If the subscriber has three way calling service, a three way call is set up.
• R SDT 6
If the subscriber has six way calling service, a six way call is set up
using a six port conference bridge.
Cancel call waiting
Cancel call waiting allows a subscriber to temporarily deactivate the CWT
feature, so that incoming calls do not interrupt the current call. If an
incoming call attempts to terminate on the line, CWT tone is prevented and
the call is immediately denied. When the current call is terminated, the
CCW feature is automatically deactivated and CWT is restored. CCW can
be activated immediately prior to a call, or during the call by dialing an
access code.
CCW is available to all subscribers that have CWT assigned. CCW is not
assigned to specific subscribers but is potentially available to all subscribers.
Operating company administration can query the status of this feature on a
subscriber line.
CCW does not provide the capability to suspend interruptions on the other
subscriber. It only affects the subscriber which has activated the feature.
The subscriber service code (SC) for this feature is controlled by operating
company administration. The specific SC can be datafilled in table
ACCODE. The dialing sequence used to initiate subscriber activation can
also be datafilled; however, it is recommended that a * be used to precede
the SC.
The subscriber activation code sequence is as follows:
1 * SC #
2 A subscriber can activate CCW via two methods: prior activation and
flashing:
— prior activation: LH DT *SC# SDT TN RT....(talking)...RH
— flashing (talking)...RR SDT *SC# ACK...(talking)
CEPT hot line
Hot line is assigned and programmed by operating company administration.
When the subscriber lifts the handset, the switch immediately sets up the
path to the predetermined terminating target number (TN).

DMS-100 International Technical Specification BCS40i and up

4–10 Features

Digipulse (DP) activation of subscriber features

DP activation of subscriber features allows subscribers with DP lines to
activate the following features:
• Call diversion to announcement (CDA)
• Call diversion on busy (CDB)
• Call diversion fixed (CDF)
• Call diversion to operator (CDO)
• Call diversion to subscriber (CDS)
• Call waiting (CWT)
• Cancel call waiting (CCW)
• International do not disturb (IDND)
• International line restrictions (ILR)
• Malicious call trace (MCT)
• Ring again (RAG)
• Subscriber call recording (SCR)
• Warm line (WLN)
• Wakeup call (WUC)

Digipulse lines include push button digipulse phones and rotary dial phones.
Warm line (WLN)
Warm line is assigned by operating company administration. The subscriber
and the operating company can activate, deactivate, and program the feature
with a destination TN. When the subscriber lifts the handset, the switch
starts a timer. If the subscriber does not start dialing before the timer
expires, the switch sets up a call to the predetermined destination directory
number (DN). If the subscriber starts dialing before the timeout, the timer is
cancelled and the call is processed as a regular call.
The following sequences are used to control WLN:
Activation:
LH DT * FC * TN # IND RH
To activate the WLN feature with the previous TN, the subscriber must
execute the following sequence:
LH DT * FC * # IND RH
Interrogation:
To verify if warm line is active regardless of telephone number:
LH DT * # FC # IND RH
Data check (telephone number) interrogation:
LH DT * # FC * TN # IND RH

PLN-5001-001i Standard 02.02 April 1997

 Features 4–11

Deactivation:
WLN can be deactivated by the subscriber or by operating company
administration.
LH DT # FC # ACK RH
Subscriber activated outgoing restrictions
Subscriber activation of International line restrictions (ILR) allows a
subscriber to activate or deactivate one of the call restrictions on their own
line. The subscriber enter a password to activate and deactivate ILR. The
subscriber can also query the restriction status of the line.
Operating company administration retains the capability to assign, activate
or deactivate restrictions on a line.
The classes of restrictions for an individual subscriber are:
• DOR: denied origination (all outgoing calls barred). This restriction can
only be assigned by operating company administration.
• DNI: deny national and all International calls. All calls except local
calls are barred.
• DAI: deny all International calls. All calls except local and national
calls are barred.
• DIDD: deny International direct dial. All International calls, except
those to the International operator, are barred.
• DNID: deny national and International direct dial. All calls except local
calls, and calls to the International operator, are barred.
• DABE: deny all but emergency. All calls are barred, except for calls
that are of emergency class.
• NIL: No calls barred. ILR is not assigned to the line, or ILR is
assigned, but not activated.

DMS-100 International Technical Specification BCS40i and up

4–12 Features

Activation:
The subscriber can activate any of the five call restrictions by the using
following dialing sequence, either in idle or talking mode:
(idle) LH DT * SC * PW * CR # IND RH
(talking) RR SDT * SC * PW * CR # IND...(talking)...RH
where: PW is a 4 digit-password which the subscriber selects
CR is the chosen call restriction
1 = DABE (deny all but emergency)
2 = DNID (deny national and International direct dial calls)
3 = DIDD (deny International direct dial calls)
4 = DNI (deny national and all International calls)
5 = DAI (deny all International calls)
Deactivation:
The subscriber can deactivate the restriction which he has applied to his line
in either idle or talking mode using the following dialing sequence:
(idle) LH DT # SC * PW # IND RH
(talking) RR SDT # SC * PW # IND...(talking)...RH
Interrogation:
The subscriber can interrogate the line restrictions using either of the
following sequences:
(idle) LH DT *# SC # IND RH
(talking) RR SDT *# SC # IND (talking) RH
Specifying the restriction class:
The subscriber can specify the restriction class on the line using either of the
following methods:
(idle) LH DT *# SC * CR # IND RH
(talking) RR SDT *# SC * CR # IND...(talking)...RH
Subscriber features denied
Subscriber features denied (FDN) is a line option which can temporarily
deny a subscriber the use of current features, without deleting the features
from datafill.

PLN-5001-001i Standard 02.02 April 1997

 Features 4–13

If FDN is assigned, all other features do not function, and the subscriber
cannot activate or deactivate any features. Operating company
administration can alter datafill for existing features while FDN is active;
however, new line options cannot be added, with the exception of malicious
call trace.
FDN can only be activated by operating company administration by service
order or datafill. It is not a subscriber chargeable feature.
No double connect
No double connect (INDC) allows the subscriber to prevent incoming calls
from interrupting a call in progress, allowing the line to be used for
applications which require no interruptions, such as data transfer. INDC
prevents operator interruptions from toll break in (TBI), and also prevents
incoming call waiting calls.
Subscriber activation:
Idle: LH DT *SC# IND RH
Flashing: (talking): RR SDT *SC# IND...(talking)
Subscriber deactivation:
Idle: LH DT #SC# IND RH
Flashing: (talking): RR SDT #SC# IND...(talking)
Subscriber interrogation:
Idle: LH DT *#SC# IND RH
Flashing: (talking): RR SDT *#SC# IND...(talking)
Ring again
Ring again (RAG) allows a subscriber to request notification, by a special
ringing signal, that a busy line has become idle. The subscriber can then
reinitiate the call by lifting the handset or going off hook. Only
intra-exchange calls can use this feature. RAG is assigned to a line by
operating company administration using service orders.
Activation:
BT RR SDT * SC # IND
Deactivation:
LH DT # SC # IND RH

DMS-100 International Technical Specification BCS40i and up

4–14 Features

Interrogation:
LH DT * # SC # IND RH
Selective charge recording (SCR)
Selective charge recording (SCR) allows subscribers to have the charges for
the current call quoted back to them when the call is completed.
Subscribers with SCR assigned can activate it using a DTMF set when a
local or toll call is direct dialed. After call disconnect, an SCR100 log is
generated, which records the metered pulses for the call. Operating
company administration can use this information to determine the call
charges, then contact the subscriber.
SCR is assigned to a line by operating company administration using service
orders.
Activation:
To activate SCR, the subscriber uses the following dialing sequence when
placing a call:
LH DT * SC # SDT TN IND RT
If the feature has not been assigned to the subscriber line, a NACK is
provided and the subscriber is unable to continue the dialing sequence.
The following information is recorded in the SCR log associated with the
call upon end of metering:
• start date (6 digits): the date that the call originated (YYMMDD).
• answer time (6 digits): the time that answer was received (HHMMSS).
• calling number (maximum 10 digits): the directory number of the
originating party.
• called number (maximum 18 digits): the directory number of the
terminating (dialed) party.
• call duration (8 digits): the duration of the call (minutes) between answer
and disconnect.
• pulse count (8 digits): the number of pulses recorded for the call.
• meter name: the meter name used for the call.
Operating company administration use the calling number to ring back the
subscriber when they have computed the call charges from the pulse count
and the meter name indicated in the log.

PLN-5001-001i Standard 02.02 April 1997

 Features 4–15

Call transfer
Call transfer can be assigned to a subscriber either as a stand-alone feature,
or combined with 3WC/6WC. Call transfer is assigned to a line by
operating company administration.
The subscriber assigned this feature can transfer either an incoming call, or
an originated call, to a third party. Restrictions on the types of call that can
be set up for the second leg can be established on a per-office basis using
translations tables. Call transfer to treatment is allowed. This feature cannot
be used while in 6WC conference mode.
Call charges are assigned for the first leg to the originator of that leg, and for
the second leg to the subscriber setting up the transfer.
The following dialing sequences control this service:
• R SDT TN
Party B is held and party A rings party C.
• R SDT 0
Party A remains connected to the active party. A disconnect tone is sent
to the held party.
• R SDT 1
Party A is reconnected to the held party.
• R SDT 2
Held and active calls are switched.
• R SDT 4
Held and active party are connected and controlling party disconnected.
Three and six way calling
This feature allows a subscriber to place an existing two-party call on hold
and set up an inquiry call to another subscriber. The subscriber then has the
following options.
In the 3-way calling scenario, the subscriber initiating the 3WC can:
• switch speech paths between the held party and talking party
• connect all parties into a 3-port conference
• remove the conference and reconnect to a single party.

In the six-way calling scenario, the subscriber can:

• switch speech paths between the inquiry call and the parties in the
conference
• connect the inquiry call into a 6-port conference and add up to 5 parties
into the conference
• remove the inquiry or conference and remain connected to remaining
parties.

DMS-100 International Technical Specification BCS40i and up

4–16 Features

The subscriber uses the following dial sequences to control a three-way or

six-way call:
• RR SDT 0
Disconnect the party that is on hold.
• RR SDT 1
Disconnect the active call and connect to the held call.
• RR SDT 2
Put the active call on hold and return to the held call(s).
• RR SDT 3
Select a three port conference circuit and connect all three parties.
• RR SDT 6
Select a six port conference circuit and connect all three parties.
• RR SDT TN
All connected parties on hold and dial another. Not valid if a three port
circuit is already assigned, or if the six port circuit is fully occupied.
Wakeup call
This feature allows the subscriber to have his phone ring at a specified time.
The subscriber programs the designated time, by entering the appropriate
time in hours and minutes. The wakeup call is generated within 24 hours of
the request.
The DMS-100 International switch causes the subscriber’s phone to ring at
the specified time, and provides an administration-defined announcement
upon answer. If the call is unanswered (either busy or ringing time-out), a
second wakeup call is attempted approximately five minutes later (the exact
value is controlled by an office parameter). If the second attempt is also not
answered, a log is generated and the wakeup call request is discarded.
The subscriber can cancel a wakeup request, or query the status of a wakeup
request. Up to three outstanding requests can be made, provided that none
of the requests are within 15 minutes of each other. A wakeup request does
not automatically repeat itself after 24 hours— a new request is required for
each wakeup call.
Activation:
The subscriber uses the following sequence to generate a wake-up call
request:
LH DT * SC * TIME # IND RH
Deactivation:
There are two forms for deactivation of wakeup requests. The first is a
general form which deactivates all outstanding requests. The second form

PLN-5001-001i Standard 02.02 April 1997

 Features 4–17

requires a time parameter, which deactivates a request for a particular time.

These deactivations are performed by the following control sequences:
LH DT # SC # IND RH
LH DT # SC * TIME # IND RH
Interrogation:
There are two forms for interrogation of wakeup requests. The first is a
general form which indicates if a request is active. The second form
requires a time parameter, which indicates if a request for a particular time is
active. These interrogations are performed by the following control
sequences:
LH DT * # SC # IND RH
LH DT * # SC * TIME # IND RH
Call party control using translations
This feature provides the ability for the customer to define the controlling
party of a call. The controlling party can be the called party, the calling
party, or mutual control (both parties).
Calling party control
Calling party control operates as follows:
• If the calling party goes on-hook first, the call is released immediately.
If the called party remains off-hook for longer than the lock-out time, the
called party receives disconnect treatment. If the called party goes
on-hook within the lock-out time, the called party is set to idle.
• If the called party goes on-hook first, the calling party starts re-answer
timing to allow the called party to reconnect to the call. If the called
party remains on-hook and the re-answer time expires, the calling party
releases the connection to the call and the called party gets set to idle. If
the calling party remains off-hook, the calling party receives disconnect
treatment after the lock-out time expires.
• If the called party goes on-hook first, and the called party re-answers
within the re-answer time, the call continues.
• If the called party goes on-hook first, and the calling party goes on-hook
before the called party re-answers, the connection is released and both
agents are marked as idle.

DMS-100 International Technical Specification BCS40i and up

4–18 Features

Called party control

Called party control operates as follows:
• If the called party goes on-hook first, the connection is released and the
called party is released. If the calling party remains off-hook for longer
than the lock-out time, the calling party receives disconnect treatment. If
the calling party goes on-hook within the lock-out time, the calling party
is set to idle.
• If the calling party goes on-hook first and does not re-answer, the
connection is not released until the called party goes on-hook. The
called party maintains control of the call infinitely. There are no
timeouts.
• If the calling party goes on-hook first and the calling party re-answers,
the call continues.
All flash features are denied with called party control, except MCT and
ESG. This prevents the called party from flashing and adding another leg to
the call, or transferring the call and creating an ambiguous control situation.
Mutual party control
With mutual party control, the connection is released if either party goes
on-hook. The other party is disconnected if the other party does not go
on-hook within the lock-out time. No party can reconnect to the call.
Timeouts
Lock-out timing: The lock-out time is the amount of time an idle party has
to go on-hook before receiving disconnect treatment. Lock-out times are
hard-coded as 10 seconds for line calls. Lockout times apply to all calls
regardless of call control.
Pre-answer timing: The pre-answer time is the amount of time a call will
remain intact if no answer is detected by the originating office. Pre-answer
timeouts are specified as either zero, or a value between 30 and 255 seconds.
Values between 1 and 29 are prohibited, so that the called party will have
sufficient time to answer. A value of zero indicates that pre-answer timing
does not occur. There is no time limit to answer a call if the pre-answer
timing is zero.
Timeouts for line-to-trunk calls are specified in table CTRLTMRS.
Timeouts for line-to-line calls are specified in the office parameter
RNG_TMEOUT_NO_OF_SECS in table OFCENG.
Re-answer timing: The re-answer time is the amount of time the called
party has to reconnect to the calling party when calling party control is in
effect. Re-answer timeouts are specified as between 0 and 255 seconds. A
value of zero indicates that no re-answer timing occurs and re-answer is not
allowed.

PLN-5001-001i Standard 02.02 April 1997

 Features 4–19

Billing under party control

Call control affects metering and call recording as follows:
• When calling party control is active, the call is released and metering or
call recording stops when the calling party goes on-hook. If the called
party goes on-hook first, the calling party starts re-answer timing.
Metering or call recording continues during this re-answer timing until
the calling party goes on-hook or the re-answer timer expires. If the
called party re-connects by going off-hook, the call continues and
metering or call recording continues.
• When called party control is active, the call is released and metering or
call recording stops when the called party goes on-hook. If the calling
party goes on-hook first, metering or call recording continues until the
called party goes on-hook. If the calling party goes off-hook, the call
continues and metering or call recording continues. Since no re-answer
timing occurs, metering or call recording can continue infinitely if the
called party does not go on-hook.
• When mutual party control is active, the call is released and metering or
call recording stops if either party goes on-hook.
One exception to these rules is Emergency Services Group (ESG). Calls to
ESG lines assume called party control and stop both hardware and software
metering when the calling party goes on-hook. Metering does not continue
during re-answer timing, nor does it resume when the calling party
re-answers and the call continues.
The call party control feature is not supported for the following call types:
• line-to-line calls under ESA (Emergency Stand Alone) services
• line-to-treatment
• trunk-to-ITOPS position.
• trunk-to-line
• trunk-to-trunk
• trunk-to-operator
• trunk-to-treatment

Miscellaneous local system features

Compatibility with dial long line circuits
Dial long line circuits are used to extend the range of customer loops. The
range can be extended by repeating supervision and dial pulses from the
customer to the central office, and by repeating ringing from the central
office to the customer. A variety of dial long line circuits can be required,
to provide required service features, and to meet transmission and range
requirements associated with these services. When a particular dial long line
circuit is planned for use with a DMS-100 International system, Northern

DMS-100 International Technical Specification BCS40i and up

4–20 Features

Telecom will, on request, advise on the compatibility of that particular

circuit.
Loop start line
In a loop start line arrangement, the central office supplies battery between
the ring and the tip conductors. The central office detects a loop closure
from the customer station as a seizure, after which it provides dial tone on
the tip and ring conductors as a start dial signal.
Coin telephone control signaling
A pulsed 12 or 16 KHz tone is transmitted to the loop via the line circuit to
collect coins in approved coin boxes.
Subscriber premise meter
A pulsed 12 or 16 KHz signal is transmitted to the loop via the line circuit
and increments an approved subscriber premise meter.
Guaranteed dial tone for DMS-100 International
Guaranteed dial tone for DMS-100 International guarantees dial tone to
subscribers that remain off hook. This ensures that subscribers do not have
to re-originate calls if dial tone is not immediately received. All originating
calls eventually obtain dial tone when the International line group controller
(ILGC) is overloaded, rather than discarding originations.
Dial tone speed recording for International
This feature offers the capability to monitor dial tone delay for all types of
lines on ILGCs. This is particularly useful when the switch is under heavy
load. The timings are not constant for all set types on a switch; time varies
depending on whether the set is dial pulse or digitone. The switch should
return dial tone within three seconds, otherwise the delay is recorded. This
information is gathered and made available for regular analysis. The delay
is considered to be the length of time between the point when call
origination is first detected in the LCM, and the time when dial tone is
returned. This is determined by calculating the difference between the
timestamp sent to the ILGC upon origination, and the time when dial tone is
returned.
DTSR statistics
DTSR information is gathered and stored as operational measurements
(OMs). DTSR counts are held in pairs. One count is the total number of
calls; the other is the number of calls whose dial tone delay exceeds three
seconds. DTSR statistics are gathered on a per-site basis with separate
figures (one pair of counts) for each class of line.
Two line classes are supported for DMS-100 International:
• DP: dial pulse

PLN-5001-001i Standard 02.02 April 1997

 Features 4–21

• DT: digitone
DTSR OM counts show delays for the following reasons:
• CC Call Processing realtime delays. Calls can be held up in the
origination or process queues.
• Resource failures in the CC.
• Delays caused by CC overload controls.

The DTSR counts do not show delays of originations that have gone through
guaranteed dial tone (GDT). GDT ensures that a subscriber will eventually
receive dial tone without having to re-originate. With GDT, all originations
are placed on a queue. When a terminal has been queued for more than
three seconds, the PORGDENY register of the OM group PMOVLD is
pegged. These counts are separate from the DTSR pegs and should be
consulted along with the OM group DTSR to obtain full details of dial tone
delay.
Data collection
The CC starts this feature in the IXPM by downloading the appropriate static
data when it returns the IXPM to service. The craftsperson can turn DTSR
on or off at the DTSR level of MAP CI, using the BIND and UNBIND
commands. The LCMs collect DTSR statistics for each call. At the end of a
reporting interval, the DTSR statistics for all LCMs are reported to the CC.
Figure 4–1 shows the distribution of data collection functions. The IXPM
polls the LCMs and accumulates the results over the units of the LCMs.
Each IXPM then packages the results for its LCMs and sends an IXPM
DTSR report to the CC. The CC stores the data on a per-LCM basis.
The three types of processors are responsible for the following functions:
• CC – Store DTSR statistics
• IXPM:
— Poll the units of the LCMs for DTSR statistics.
— Accumulate DTSR statistics per LCM.
— Send IXPM DTSR statistics report to CC.
• LCM:
— Collect DTSR statistics.
— Send DTSR statistics report to IXPM.

DMS-100 International Technical Specification BCS40i and up

4–22 Features

Figure 4–1xxx
DTSR collection
FW-31151

DTSR
statistics request
Central IXPM LCM
control IXPM DTSR
statistics report
DTSR statistics
report

Figure 4–1 shows only the continual data flows between processors. The
CC also sends a message to the IXPM on return to service and reset to
update the static data that tells the IXPM how often to poll the LCMs and
whether to collect DTSR data.
Faultsman’s ring-back
This feature allows a craftsperson at the subscriber premise to test continuity
on the line and verify ringing without additional assistance. The
craftsperson takes the phone off-hook, dials a special access code upon
hearing dial tone, and goes on-hook. The switch sends ringing to the
subscriber line, and the craftsperson answers (goes off-hook).
By going on-hook within ten seconds, the craftsperson acknowledges to the
switch that the line is functioning correctly, and the line is set to normal
operating state (idle). If the craftsperson does not go on-hook within the
timeout period, the switch assumes the line is faulty. The line is locked out
and a log is generated.
This feature applies to DP and DTMF phones, and all types of residential,
coin, and PBX lines. The ringback time ranges from 60 to 180 seconds and
is controlled by office parameter FRB_RINGING_TIME in table OFCOPT.
The default value is 60 seconds.
Faultsman’s digit test
This feature provides the Faultsman’s Digit Tests (FDT) for the faultsman
(field engineer) to test a telephone from the subscriber’s premises. It
complements the existing support for direct maintenance (no operator
intervention) provided by faultsman’s ring-back.
The test operates in two stages:
• digit reception test (DRT): the integrity of digit reception is tested by
dialing all digits on a push button telephone, or zero on a rotary dial
telephone. On a DP set, this ensures that the make/break mechanism is
working. On DTMF sets, this verifies that each digit can break dial tone.
Jamming of push buttons is also detected by the DRT.

PLN-5001-001i Standard 02.02 April 1997

 Features 4–23

• directory number check (DNC): the intended DN is dialed and verified

against the value datafilled for that line.
Faultsman’s digit test sequence
1 Go off hook. On receiving dial tone, dial the access code datafilled for
FDT (suggested value 111).
2 After a brief pause (about one second), dial tone is returned prompting
for the first digit. Begin dialing the test sequence for the type of phone
under test.
— DTMF phone sequence: 1, 2, 3, 4, 5, 6, 7, 8, 9, 0, *, #
— DP (rotary dial) sequence: 0
— DP (push button) sequence: 1, 2, 3, 4, 5, 6, 7, 8, 9, 0
Note: The sequence required to test a push button DP phone can also be
followed on the rotary dial type.

3 Each digit is tested as it is received:

— PASS: the digit has broken dial tone and been received in sequence.
After a pause, dial tone is returned to prompt for the next digit.
— FAIL: no digit is detected (after a 10 second timeout), or a digit other
than the one expected has been received, so the negative
acknowledgement tone is given and the test terminates. A DRT100
log is generated which records the DN of the terminal under test, the
digits received up to the point of failure, and the digit sequence
expected. The faultsman can go on hook immediately without
affecting production of the log. If he does not, the tone times out
after ten seconds and dial tone is returned.
4 If the DRT is completed successfully, acknowledgement tone is given
after the final digit instead of dial tone. The faultsman can go on hook
(and can do so at any point during the test), or proceed to the DNC.
5 Special dial tone (three short notes followed by a continuous one) is
given to request the DN. The faultsman dials the DN intended for the
line. There is a 5 second inter-digit timeout during DN collection.
6 The digits are compared with the DN in the office datafill:
— pass: the digits dialed matched the DN. Acknowledgement tone is
given and the test is complete.
— fail: the digits dialed did not match the DN. A negative
acknowledgement tone is given, and a DNC100 log is generated,
recording the digits received and the DN. The faultsman can go on
hook immediately without affecting production of the log. If the
faultsman remains off hook, the tone times out after ten seconds and
dial tone is returned.

DMS-100 International Technical Specification BCS40i and up

4–24 Features

Semi-permanent connections
A semi-permanent connection (SPC) is a connection which can be set up or
taken down by operating company personnel. The subscriber has no
signaling control of the connection, but can use the speech/data path for the
duration of the connection. The SPC is a standard voice band audio channel
which supports inband audio transmission only. Supervision signals such as
on-hook and off-hook are not supported on the SPC.
The following types of SPC connections are supported:
• line to line
• line to trunk
• trunk to line
• IRLCM line to line
• IRLCM line to IRLCM line
• line to IRLCM line
• trunk to IRLCM line
• IRLCM line to trunk

Operator tones
Insert tone on coin phone terminations
This feature causes pay phone recognition tone to be given to the operator
when a call terminating on a coin phone is answered.
When a caller asks the operator for a collect call to a number, the call is
charged to that called number. If the called number is a coin phone, an
indication must be given to the operator, who can prevent fraud by refusing
to connect the call.
Certain types of coin phones provide a tone on answer. In those cases, both
tones will be audible to the operator.
Toll break in – background tone
This feature allows the DMS-100 International system to apply the
appropriate tone sequence when an operator offering a toll call to a
subscriber finds the subscriber busy on another call and has to barge-in on
the call.
TBI MAP signaling command
This feature allows testing of the toll break in (TBI) signal, by simulation
from the trunk test position (TTP) level of the maintenance and
administration position (MAP).

PLN-5001-001i Standard 02.02 April 1997

 Features 4–25

The operation at the MAP is as follows:

1 The craftsperson posts the OG trunk that supports the TBI signal at the
Manual sublevel of the TTP level of the MAP and uses the HSET
command to connect the headset to the posted trunk.
2 The result of the next action depends on the datafill of field ALERCTL
in table TRKSGRP:
— ALERCTL is datafilled as TERM. The OP command is used to
out-pulse the desired subscribers digits.
– If the line is idle, the subscriber receives physical ringing and the
craftsperson receives audible ringing automatically. The TBI
command is not required.
– If the line is busy, the craftsperson hears a busy tone over the
headset. At this point, the TBI command can be entered. This
causes the outgoing trunk to send a TBI signal across the facility
to the subscriber’s call. All three parties hear break-in tone. If
the subscriber hangs up, the subscriber receives physical ringing,
and the craftsperson receives audible ringing automatically.
— ALERCTL is datafilled as ORIG. The OP command is used to
out-pulse the desired subscribers digits.
– If the line is idle, the connection is made, but physical ringing to
the subscriber and audible ringing to the craftsperson does not
occur. At this point, the TBI command can be entered. The
subscriber receives physical ringing, and the craftsperson
receives audible ringing.
– If the line is busy, the craftsperson hears busy tone over the
headset. The TBI command causes the outgoing trunk to send a
TBI signal across the facility to the subscriber’s call. All three
parties hear the break-in tone. If the subscriber hangs up upon
hearing the TBI tone, the TBI command must be entered again to
start physical ringing to the subscriber and audible ringing to the
craftsperson.
3 If the busy subscriber ignores the TBI signal for the time specified in the
field TBI_OPR_TIMEOUT in Table OFCVAR, the craftsperson receives
reorder tone.

Attendant pay stations

An attendant pay station (APS) or service hall is a public site where
telephone calls can be placed. Each site is supervised by an attendant who
assigns telephones to customers and collects payment for charges incurred
on their calls.
Each line in the service hall must be assigned the APS option using service
orders.

DMS-100 International Technical Specification BCS40i and up

4–26 Features

The service hall can be configured as any type of hunt group (DLH, DNH,
MLH, BNN), with the attendant’s line external to the group.
Two types of calls can be placed from a service hall:
• direct dial call (automatic)
• operator assisted

For each direct dialed call originating at the service hall, a billing record is
printed. Operator assisted calls are manually ticketed. Since call charges
are a function of the meter pulses, zero charges are indicated in the billing
record for toll calls. If the metering information for toll calls is present, then
the billing record indicates charges for toll calls.
The following terminology is used to describe the service hall feature:
• service hall: a public site where telephone calls can be placed.
• APS (attendant pay station): the line option assigned to each telephone
in the service hall.
• local call: calls tariffed in the local switch are classified as local calls.
• toll call: calls that are routed over CAMA trunks (usually not metered)
are referred to as toll calls.
• billing record: logs generated for direct dialed calls are called billing
records.
Service hall operation
The sequence of events for a typical call from the service hall is as follows:
• Customer checks in with the attendant by providing call details and a
deposit (if required). The customer then joins the queue.
• If the call is a direct dial call, the attendant assigns a telephone to the
customer.
• If the call is a booked call, the attendant requests the booking operator
for the call. When the call is ready, the operator dials the service hall.
At this point, the attendant can direct the customer to the appropriate
telephone.
• On call completion, a billing record is printed for direct dialed calls.
Other types of calls are manually ticketed.
• The customer settles his or her account with the attendant.

Call detail records

APS call detail records are generated in the same manner as selective charge
recording (SCR). Call details records for SCR and APS calls can be routed
to either log or HOBIC devices. Operating company administration
specifies which system to use by setting the office parameter
CALL_REPORT_FORMAT to HOBIC, if HOBIC is to be used. Otherwise,
this parameter is set to LOG.

PLN-5001-001i Standard 02.02 April 1997

 Features 4–27

Selective charge recording

Subscribers use SCR on a per-call basis by dialing a service code before
dialing the target number. At the completion of a successfully activated
SCR call, an SCR call record is produced containing the call details and
charges. In addition, an SCR100 call record is generated at the DMS200
office for SCR toll calls.
Billing systems
APS and SCR call details records can be routed to either log or HOBIC
devices. The parameter CALL_REPORT_FORMAT determines the device
type. If set to HOBIC, then HOBIC is used. Otherwise, the log system is
used.
The log system
APS and SCR records are routed to designated log devices if the parameter
CALL_REPORT_FORMAT is set to LOG.
The logs consist of a standard one line identifier followed by a second line
containing billing information. The header line identifies the log as either a
SCR100 log or an APS1xx log. The xx corresponds to the device number
associated with the originating DN, as specified by table DNRTEID.
SCR100 logs are routed to a printer in the central office.
APS1xx logs are routed to designated log devices by datafilling tables
LOGCLASS and LOGDEV. Each APS call record is assigned a log class,
and each log class can be routed to any log device.
This routing control is achieved by two tables: LOGCLASS, which
associates an APS call record (that is, this is the device number specified in
table DNRTEID) with a class, and LOGDEV, which associates a class with a
device.
All APS call records can also be routed to a central log device, such as a
disk or tape volume, for backup and auditing of the individual APS logs.
The HOBIC system
The hotel billing information centre (HOBIC) is a centralized
operator-attended location, which provides the following services:
• quotation of call details to service halls
• quotation of time and charges (T and C)
• a centralized location for reporting equipment problems and billing
inquiries.

DMS-100 International Technical Specification BCS40i and up

4–28 Features

HOBIC is supported in a DMS200 or a DMS100/200 environment. The

following devices are associated with the HOBIC system:
• auto quote printer (AQ printer): This is a receive-only printer located at
the service hall. APS call records are routed to the AQ device that is
associated with the calling DN in table DNRTEID.
• voice quote printer (VQ printer): This is a receive-only printer located in
the HOBIC. It receives call records for all SCR calls, and for APS calls
which are routed to a VQ.
• record (REC) printer: This receive-only printer receives a duplicate
copy of the call records sent to the AQ and VQ printers and also any
charge-adjust messages sent to the HADS (HOBIC administrative
printer).
• HOBIC administrative (HADS) printer: This is a send/receive printer
located in the HOBIC and whose functions include the following:
— enables HOBIC operators to input to the service hall, billing
information that is to be relayed to the AQ, VQ or REC printer
— permits HOBIC personnel to place any AQ, VQ, or REC printer in or
out of service
— receives printer service alarm messages.
HOBIC records are sent to their designated AQ or VQ printer. A duplicate
of the record is sent to the REC printer.

Announcements
Recorded announcement service (local)
Recorded announcement service provides a verbal announcement to
originating lines which have voluntarily requested access to a recorded
announcement (time, weather, etc.) or have been routed to an intercept
announcement for calls that cannot be completed as dialed.
Calls routed to an announcement, in response to a voluntary customer
request, receive charge treatment. Calls routed to an intercept
announcement are not charged to a customer. Therefore, answer supervision
is not returned to the originating office for interoffice calls routed to an
intercept announcement.
Digital recorded announcement system (DRAM)
The DRAM provides recorded announcements, stored in digital format,
which are accessible on either a “barge-in” or “non barge-in” basis. A set of
standard announcements are available on programmable read only memory
(PROM) cards, while others can be generated on site by the operating
company using RAM or electronically erasable PROM (EEPROM) cards.
The DRAM can be used for local recorded announcements, special
information tones, or custom applications such as calling number

PLN-5001-001i Standard 02.02 April 1997

 Features 4–29

announcement and mechanized calling card service (MCCS) announcements

in an operator services environment.
Up to 255 (datafillable) connections can be made to a single DRAM
channel.
Ringing
Programmable ringing generators are supplied in each line concentrating
equipment frame. Cadence of ringing (based on a six-second period),
frequency and amplitude, and DC offsets of ringing voltages are
programmable. AC/DC, superimposed, coded and frequency selective
ringing schemes are supported.
Individual line ringing
Individual line ringing requires the application of an AC/DC ringing signal
to activate a ringer bridged across the line within the telephone set.
Audible ringing tone
Audible ringing provides a ringing tone to inform calling customers that the
called destination is being alerted. The signal is applied as soon as possible
upon connecting to the called line.
The audible ring tone signal is applied in a manner that does not permit an
electrical voice connection between the calling and called lines before
answer.

IXPM features
IXPM warm SWACT
Warm switch of activity (SWACT) capability between a running IXPM unit
and its dedicated standby unit is supported on the DMS-100 International
switch. Warm SWACT capability is the maintaining of all calls in session
and in a stable state during a switch of activity (SWACT) from the active
unit to the inactive unit of an IXPM. Activity changes can occur by manual
or system request.
Calls are considered stable and in session if they have received answer and
no events have occurred following answer. Calls that have not received
answer before SWACT (in set up), or subsequent to answer have received a
flash (feature activation, etc.) are dropped during the SWACT.
Reasons for SWACT
SWACTing calls from one unit to another can occur for a variety of reasons,
including:
• maintenance requirements
— hardware
– repairs or upgrading

DMS-100 International Technical Specification BCS40i and up

4–30 Features

– out-of-service testing
– exercising the SWACT mechanism
— software
– updating code
– updating data
• fault recovery
— hardware
– unrecoverable faults
– device degradation
— software
– non recoverable processor trap
– an audit failure
SWACTing for maintenance reasons is generally considered a controlled
SWACT, as the transfer of activity is done by request. SWACT for fault
recovery reasons is generally considered to be uncontrolled, in the sense that
the time at which the activity transfer occurs cannot usually be chosen or
deferred. Uncontrolled SWACT generally represents the worst case
situation with respect to the impact on subscribers, especially if it occurs
during heavy traffic periods. If possible, a warm SWACT should be
performed during light traffic periods.
IXPM performance monitoring
IXPM performance monitoring provides easily accessible information to the
craftsperson to indicate a particular peripheral’s performance. This is
accomplished using the MAP level PERFORM, a sub-level of the MTC PM
level.
PM activity (PMACT )
The PMAct sub-level, accessed by entering PMACT at the Perform level,
displays the percentage of the realtime used in the MP, SP and FP. PMAct
divides the realtime being used into three categories: call processing
occupancy, high priority background occupancy and low priority
background occupancy. The combination of the high priority and the call
processing occupancies indicates the realtime used to actually provide
service, while the low priority background occupancy indicates the realtime
spent in running audits and diagnostics.
MAP level details
All Perform sub-levels provide the same commands: Strt, Stop, Strtlog and
Stoplog. The measurements begin when the Strt (start) command is entered.
This command can take one parameter, which specifies how long the tool
will run. The default is set at 15 minutes. The Stop command is used to
stop measurements.

PLN-5001-001i Standard 02.02 April 1997

 Features 4–31

The Strtlog (start logs) and Stoplog (stop logs) commands provide the
capability to output the results displayed on the screen as logs. Once started,
logs are printed every 15 minutes.

Interoffice features
Interoffice address signaling
Refer to chapter 6, “Signaling and Interfaces” for information on interoffice
address signaling.
Call state supervisory signaling
Refer to chapter 6, “Signaling and Interfaces” for information on
supervisory signaling.
Intraoffice connecting arrangements
An intraoffice connecting arrangement is provided to establish a connection
between two customers served by the same switching system.
International killer trunks
The killer trunk feature is a software replacement for the typical external
individual circuit usage and peg count (ICUP) equipment. It attempts to
detect faulty trunk circuits or facilities that are not detectable by normal call
testing. Trunk members to be detected will have at least one of the
following properties:
• killer trunk – a trunk member which is repeatedly seized but due to a
malfunction is not held for an appreciable length of time. For example,
bad transmission will cause the subscriber to drop the connection and
re-attempt the call. Within a group these trunks will have a higher than
average attempt rate.
• slow release trunk – a trunk member that has a low attempt rate coupled
with a fairly high usage. Malfunctioning supervisory equipment is
typically the cause of this.
• always busy trunk – a trunk member which has zero call attempts, and is
busy for the entire report interval. Causes include under-engineering of
the group, normal high usage, and equipment malfunctions.
• always idle trunk – a trunk member which has a usage of 0 and zero
attempts. Improper network management controls, over-engineering and
equipment malfunction are among the causes.
A maximum of 2048 trunk members can be assigned for killer trunk
detection. If a trunk is detected to be both a killer trunk and a slow release
trunk, it is flagged as a killer trunk.
By gathering usage and peg statistics on a per-trunk basis, over some
specified interval, trunk members with the above properties are identified.
This is accomplished through the use of registers assignable on a trunk

DMS-100 International Technical Specification BCS40i and up

4–32 Features

group basis which accumulate the trunk attempts and connect duration. The
peg statistics used for killer trunks are not related to OM pegs. The Killer
Trunk process periodically runs through the registers and computes the
average call holding time for each trunk member instrumented. A report is
generated identifying killer, slow release, always busy, and always idle
trunks.

IRLCM features
Intraswitching on the IRLCM
The IRLCM consists of two line concentrating arrays (LCAs) within and
between which connections are established for intraswitched calls. Within
the IRLCM, intraswitching is broken down into two types.
• Intra-LCA– subscribers located on the same LCA are connected via an
intra-channel
• Inter-LCA– one subscriber on one LCA and the other on the mate LCA
are connected via an inter-channel.

PLN-5001-001i Standard 02.02 April 1997

 Features 4–33

Figure 4–2xxx
Intra/inter LCA connections
FW-31152

IRLCM

LCA 1

Host channel
to ILGC
Interconnection Intraconnection

LCA 0

Intraconnection

Legend:
ILGC International line group controller
IRLCM International remote line concentrating module
LCA Line concentrating array

Figure 4–2 illustrates the connection paths for intraconnections and

interconnnections.
When to attempt to intraswitch
Setup of intraswitched calls is subject to the following restrictions:
• Intraswitching is optional in the peripheral.
• The capability for I/S to be switched on and off (for an office) is
provided.
• Only calls not requiring host resources during call processing can be
intraswitched, that is, only subscribers without any subscriber features
which are activated by a flash will be intraswitched. Subscribers
requiring host resources.(for example, 3-way calling or call waiting), are
connected through the network. This allows calls using features not
requiring host resources, such as abbreviated dialing, to be intraswitched.

DMS-100 International Technical Specification BCS40i and up

4–34 Features

• Both subscribers must be on the same remote peripheral module

(IRLCM).
The sequence of events for I/S to take place is:
1 Agent A originates the call.
2 The CC receives the digits and through translations and routing
determines the terminating subscriber, B.
3 If A and B are on the same IRLCM, neither has any subscriber line
features datafilled as described in 3 above, I/S is available on the
IRLCM, and I/S has been enabled, then inform the IRLCM to attempt to
intra-switch the call.
4 If the IRLCM determines that I/S cannot take place,this is reported to the
CC. Otherwise, an intra/inter channel is allocated. The ILGC supplies
ringing tone to the originating subscriber, and the IRLCM supplies
ringing to the terminating subscriber. The I/S connection is fully set up
(that is, PCM30 channels are allocated within the IRLCM and any
channels between the ILGC and the IRLCM are deallocated) only on
answer from the terminating subscriber, when ringing and ringback tone
be removed.
5 If the IRLCM reports that I/S cannot take place, the CC attempts to
connect the call via the network (as with a non-I/S call).
6 If this fails, the call is routed to the appropriate treatment, as though I/S
had never been attempted.
7 If an intraswitched connection has been set up, on take down the
intra/inter connection is broken and the CC informed by the ILGC that
the call has been terminated.
Restrictions on the number of i/s calls
The number of intraswitched calls in the IRLCM is not engineerable but
varies inversely with the number of PCM30 links to the ILGC. Port 6 in the
LCA is always an inter-LCA link. When less than 6 PCM30 links are
equipped, extra intra channels are made available by the link controller card
(LCC) hardware by channel looping.
Unequipped ports are used for intra and inter calling. If all ports are
equipped, this results in fewer inter channels being available for
intraswitching. Thus there is a tradeoff between the number of PCM30 links
to an IRLCM and the number of intraswitched calls possible.
IRLCM intraswitching for subscriber features
This feature removes the restriction that a call between two agents on the
same IRLCM, where one of the agents has call waiting (CWT), three-way
calling (3WC), or six-way calling (6WC) assigned, will not be
intraswitched. If a call has been intraswitched and one of the agents

PLN-5001-001i Standard 02.02 April 1997

 Features 4–35

involved wishes to invoke CWT, 3WC, or 6WC then the intraswitched

connection will be broken and a network connection made instead.
It also allows toll break-in (TBI) on an intraswitched call. If an operator
wishes to break in on a call to offer a previously booked call to one of the
subscribers and the current call has been intraswitched, then the
intraswitched connection is broken and a network connection made instead.
If a network connection cannot be made, the call remains intraswitched and
treatment is applied as follows:
• CWT: the waiting call receives busy tone; the controlling party does not
hear CWT tone.
• TBI: the operator receives reorder tone.

• 3/6WC: the original call remains intraswitched; no treatment is given.

Lines with the subscriber premises meter (SPM) line option are not
intraswitched.
ESA for IRLCM – basic
Emergency stand alone (ESA) provides telephony service within remote
peripheral modules when the communication links to the host are rendered
inoperative. Lines originating on an IRLCM will be able to complete calls
terminating on facilities hosted by the same remote, while other calls are
routed to treatment.
Terminals supported by IRLCM ESA
IRLCM ESA supports POTS and coin lines call processing while in ESA
mode. Both DP and DT signaling can be used, the latter via receivers on the
remote maintenance module (RMM).
IRLCM ESA functionality
The following features are not available while in ESA mode:
• All conference type features (for example, 3WC or 6WC)
• International metering (including SPM)
• call diversion (CDIV)
• call waiting (CWT)
• abbreviated dialing (ADL)
• malicious call trace (MCT)
• Warm & hot lines (WLN & HTL)
• Essential line (ELN)
• faultsman’s ring back (FRB)
• call recording (ICR)
• printed meter check (PMC)

DMS-100 International Technical Specification BCS40i and up

4–36 Features

• do not disturb (DND)

• treatments other than reorder (for example, announcements).
Hunt groups
Subscribers that have a hunt group line option are accessible in ESA via
their DN, but no hunting will occur, that is, hunt group options are not
supported. Hunt groups accessed by dialing the pilot DN (as defined in the
HUNTGRP table) are supported during ESA; however, only simple, linear
hunting will be performed regardless of the datafill in the CC. The first idle
line will be terminated upon or busy tone give if all members are
unavailable. Only hunt group members hosted by that IRLCM can be
supported in ESA mode.
Digitone receivers
Digitone phones are supported by receivers provisioned on an RMM at the
remote site. The CLLI ESADGTR is defined in table CLLI, and then used
to datafill the receivers in tables TRKGRP, TRKSGRP and TRKMEM. This
information is collected and downloaded to the ESA processor as part of
static data.
Translations in ESA
During ESA mode, the universal translation system used by International
call processing is performed by the ESA processor using data downloaded
during RTS (return to service). The basic traversal of tables behaves
identically, but the handling of some of the XLA selectors (feat, trmt, cont,
rte & dmod) differs because certain facilities, such as recorded
announcements, are not available in ESA mode.
Digit analysis
Calls while not in ESA mode make use of digit analysis which is the
preprocessing of the individual digits in the ILGC. Data down-loaded from
the CC provides the peripheral with instructions on when, during digit
collection, the digits should be reported to the CC and when digit collection
should stop. Further digits can be reported later. The ability to apply
different tones during collection, for example, special dial tone, is also
provided.
This ensures that peripheral-to-CC messaging is kept to a minimum without
losing flexibility or “hard-coding” dial plans.
During ESA, translations software is presented with each digit as it is dialed.
No digit analysis is performed and the digit analysis tables (DGHEAD and
DGCODE) are not down-loaded to the ESA processor.
As a result, the user can be presented with a slightly different interface to the
system. For example, a subscriber might normally dial ’9’ for a toll call and
then receive second dial tone before being connected to an outgoing trunk.

PLN-5001-001i Standard 02.02 April 1997

 Features 4–37

In ESA mode, reorder tone would be given immediately after dialing the 9.
This is because no translation data about routing to trunks would have been
downloaded, and treatment would be given for the first digit.
Functionality of ESA
The functionality of ESA is divided between the CC, the ESA processor and
the IRLCM and is classified as follows:
• entry and exit
• call processing (and support)
• translations
• static data collection & down-loading
• maintenance & diagnostics.

IRLCM ESA entry and exit

ESA entry is the name given to acquisition of call processing control by the
ESAprocessor from the CC. Conversely, ESA exit occurs when the CC is
able to regain control from the ESA processor.
ESA entry
Entry is normally triggered automatically when regular checks reveal a
problem. It is the periodic testing of the messaging capability with the host
ILGC that forms the basis of ESA entry. This takes the following forms:
• Monitoring the message channel to the ILGC
• Monitoring the PCM30 reception status
• Sending looparound messages from the IRLCM to the ILGC

If any of these indicate a failure, a decision is made (based also on the status
of the mate link) to enter, or not to enter, ESA.
ESA is requested if the unit’s own link is bad and if one of the following
conditions exist:
• The mate unit also has a failed link
• The mate is inactive
• The inter–unit communication (IUC) link has failed

If both IRLCM units are active, then both must request ESA in order for the
ESA to accept the request.
ESA exit
While in ESA mode the message link from the IRLCM goes to the ESA
processor. The ESA processor exercises control over all calls. When the
ESA processor recovers messaging capability with the ILGC and is ready to
surrender control, it sends a command to both units of the IRLCM

DMS-100 International Technical Specification BCS40i and up

4–38 Features

requesting an ESA exit. All further messages from the IRLCM are ignored
once this request has been sent.
The IRLCMs instruct the LCC cards to restore host communication and set a
timer to prevent oscillating into and out of ESA.
The only type of exit supported by international ESA is the type known as
“cold”. With “cold” exit, all calls are dropped when CC control is regained.
Call processing
The ESA processor supports calls made between lines (POTS or coin) while
in ESA mode. Since communication with the CC is lost, access to the
resources of the CC is also lost. As a result, no CC–based functions are
provided.
While in ESA mode the following functions are not provided:
• Call processing features
• Logs
• Metering
• Facility maintenance
• Service analysis
• Operational measurements

ESA calls are unaffected by any kind of CC restart.

ESA uses the inter– and intra–switching capabilities of the IRLCM to make
calls between two lines. This is quite separate from the intraswitching that is
provided as an optional package and does not have to be purchased for ESA
operation.
The maximum number of calls available at any time in ESA is determined
by the available intra channels in the IRLCM. This capability is not limited
by the by software resources in the IRLCM.
Although regular OMs are not pegged during ESA, a few are maintained and
produced as a log on ESA exit
Static data collection and downloading
The ESA processor must have sufficient data to be able to translate digits
dialed by lines during ESA mode. This static data is downloaded under the
following conditions:
• Return to service of the ESA processor
• By manually entered MAP command
• By daily data collection audit

PLN-5001-001i Standard 02.02 April 1997

 Features 4–39

To support translations, the relevant parts of the following tables are

downloaded:
• ACHEAD and ACCODE
• PXHEAD and PXCODE
• CTHEAD and CTCODE
• OFCHEAD and OFCCODE
• DNHEAD and DNCODE

Note the absence of the ambiguous and feature tables from the above list.
These are not supported in ESA and are not downloaded. Note also the
absence of tables FAHEAD and FACODE. These tables are not supported in
ESA, as they are normally used on calls to foreign areas. Since ESA is
designed for local area calls only these tables are not downloaded to save
memory for other, more relevant, tables.
In addition to the above tables, terminal information is downloaded,
including some fields from table LINEATTR. Data is collected only for
those lines not in an offline, manual busy or unequipped state. Lines in any
of the above three states ar unable to process calls in ESA mode.
Data selection
In some tables, not all of the contents are required for simple line–to–line
translations. Only the relevant tuples are collected and sent to the peripheral
module. In this context a relevant tuple means any tuple that could be
required for translating digits from any of the terminals on the IRLCM.
Nonrelevant tuples are not downloaded and ESA translations continue as if
the tuples were never present.
The basis of this information is the translations start point in table
LINEATTR; field IXLNAME. Since most subscriber features are not
supported in ESA mode, and the only treatment available is reorder tone,
many tuples are not required.
Data is collected whenever ESA static data is downloaded. Changes by
maintenance personnel are not necessarily propagated to the ESA processor
immediately.
Data restrictions
The data store available for static data within the ESA processor is limited. It
is possible that the complete set of relevant tuples from the CC translation
tables will not fit into the ESA processor. In this case the extra tuples are
discarded during data collection and the static data loading is still indicated
as successful. At least one ESA log will indicate to maintenance personnel
that this has occurred.

DMS-100 International Technical Specification BCS40i and up

4–40 Features

The effect of this situation on call processing cannot be determined, as the

missing tuples may be vital or irrelevant to the successful setting up of most
line–to–line calls. The problem is compounded by the fact that maintenance
personnel cannot, without trying it, determine which condition would exist
in ESA mode.
Maintenance and diagnostics
The maintenance interface provided by international ESA provides the
following commands at the PM level of the MAP:
• Post
• Trsnl
• Tst
• Bsy
• Rts
• Offl
• LoadPM
• Disp
• Next
• QueryPm
• PMReset

ESA options
ESA for the IRLCM is a optional package based on the DMS-100
International product. The ESA processor is not required for normal
operation of the lines on the IRLCM and can be out of service without
affecting subscribers.

Downloadable tones
This feature allows XMS-based peripheral modules (XPMs) to support
market-specific service tones using common hardware. The tone parameters
for each market are stored in software modules and are down-loaded to
XPM as part of the static data.
The numbers and specifications of the service tones required depend on the
application. The group of parameters (for example, frequency, level, and
tone-id) that define the service tones used in each particular application are
stored in the CC as tone sets. The tone set needed in each XPM is identified
in datafill, and the tone parameters are down-loaded as part of the PM’s
static data at return to service (RTS). The XPMs use these parameters to
generate the service tones.
XPM static data audit on downloadable tones
This feature audits the peripheral static data for corruption by checking for
data mismatch between the CC and the XPM. On subsequent return to

PLN-5001-001i Standard 02.02 April 1997

 Features 4–41

service actions, based on the data checksum from the audit, the CC
determines if it is necessary to download the data to the XPM.
Static data download
On RTS, the CC queries the checksum of the XPMs static data. If this
checksum does not match that of the CC, the static data is sent to the XPM.
The CC also sends data for the XPM tone generation facility.
Second dial tone over trunks
Second Dial Tone Over Trunks is used in situations when the local exchange
does not have enough registers to collect dialing digits. In these cases, when
the caller dials an access code (typically an International access code), the
local exchange cuts the subscriber through to its outgoing (OG) trunk. Upon
detection of a trunk seizure in the far end office, the corresponding incoming
(IC) trunk applies a second dial tone alerting the user to continue dialing
digits. The second dial tone ceases when the first dialed digit is received, or
the call is routed to treatment.
The Second Dial Tone feature can be assigned on a trunk group basis to DP
trunks by datafilling field DIALTONE in table DGHEAD. The datafill
options for applying second dial tone towards the originator after trunk
seizure are as follows:
• NONE This is the default value. No second dial tone is used.
• NORM A standard second dial tone specified in the tone set is
used.
• SPEC A non-periodic second dial tone specified in the tone set
is used.
• SPEC2 A periodic second dial tone specified in the tone set is
used.
The tone set for second dial tone is country-specific. Specifications for the
tone sets are provided on a per-country basis in table 4–1 on page 4–42.

DMS-100 International Technical Specification BCS40i and up

4–42 Features

Table 4–1xxx
Second dial tone definitions in International markets
Market Toneset in DIALTONE field in table DGHEAD
table
LTCINV NORM (Hz) SPEC (Hz) SPEC2 (Hz)

Australia AUS100 900, 1300 900, 1300 425, 500 ms

100/200 idle, 500 ms
Australia AUS300 425 425 425, 500ms
300 idle, 500 ms
Caribbean CEP100 350, 440 350, 440 480, 620, 500 ms
idle, 500 ms
China CHI100 450 450 450, 400 ms
idle, 40 ms
Ireland LGC EIRELGC 425 425 440, 750 ms
350, 440, 750 ms
Ireland DTC EIREDTC 425 425 400, 750 ms
350, 440, 750 ms
Japan JAPAN 400 400 400, 150 ms
idle, 150 ms
Morocco MOROCCO 425 425 440, 500 ms
590, 300 ms
740, 200 ms
660, 500 ms
idle, 500 ms
Turkey TURK100 425 425 425, 400 ms
100/200 idle, 400 ms
Turkey TURK300 450 450 450, 200 ms
300 idle, 200 ms
United MERCURY 350, 440 350, 440 350, 440, 750 ms
Kingdom idle, 750 ms

Call processing features

Overload control and protection of essential services
Automatic internal overload control
The DMS International switch contains software that automatically
safeguards efficiency when the offered load significantly exceeds capacity.
Essential line (ELN)
The ELN feature allows a line designated as essential to originate calls when
the switch has activated line load control.
Call processing
See chapter 4 for additional information on DMS-100 International call
processing features.

PLN-5001-001i Standard 02.02 April 1997

 Features 4–43

System maintenance features

For additional detail on DMS-100 International maintenance features, refer
to chapter 10, “Maintenance”.
Hardware redundancy
Major system hardware is duplicated and/or arranged so that a failure in a
major system function is detected rapidly, and the cause of the failure
identified. If required, the system automatically substitutes a spare standby
unit or bypasses faulty hardware. With hardware redundancy, failure of a
single hardware unit does not cause a major loss of system call processing.
Trouble detection
The DMS-100 International switch uses a variety of methods to determine
actual and potential hardware and software troubles.
Hardware checks
Hardware troubles are detected by means such as redundantly encoded and
checked programs and data, matching of the operation of duplicated units,
and self-checking hardware. The fault detection facilities permit rapid
automatic corrective actions, which maximizes the system’s ability to
respond to real-time inputs, provide adequate output information, and reduce
or eliminate the mutilation of calls being handled.
Software checks
The DMS-100 International switch uses various trouble detection strategies
to detect troubles before service is affected.
Continuous automatic tests
Continuous tests detect troubles such as continuous data transmission errors.
Two types of continuous tests are described below— audits and sanity tests.
Audit programs
In DMS-100 International systems, extensive audit programs are provided to
detect and correct data errors before they can propagate and lead to system
outages or significant service degradation. Audit programs are run on a
routine basis and interlocked with normal call processing.
Sanity tests
Basic checks are continuously made to ensure that the call processing
program modules are cycling in proper sequence and on a timely basis.
Emergency action software can take the required actions to recover from
fault conditions with a minimum degradation of system call processing
capability.

DMS-100 International Technical Specification BCS40i and up

4–44 Features

Per-call trouble detection

Connections set up by the switching system are tested to detect troubles in
equipment such as peripheral modules or network equipment elements
associated with that connection.
Call processing data base trouble detection
Troubles in the call processing data base resulting from syntactically correct
but functionally incorrect entries (for example, an incorrect routing
translation table) are detected and reported by the switching system. These
troubles are reported by means such as abnormally high overflows or other
call completion problems.
Call processing resource availability tests
These tests detect the lack of currently available call processing software
resources such as call condense blocks (CC) and call processing (CP) letters.
Ineffective attempt detection
Calls that cannot be satisfactorily completed after two attempts are routed to
treatment. Each failure increments the appropriate equipment failure OM
peg count.
Path integrity test
Connections set up through the network are tested before and during use by
the internal integrity checking mechanism on the DMS-100 International
switch.
Periodic automatic tests
Periodic automatic tests are performed on standby units of a duplicated unit
pair operating in an active-standby state, on units in a non-duplex
redundancy scheme, and on server groups such as transmitters and receivers.
Semi-automatic trouble detection tests
Individual automatic tests can be requested from a local, remote, or portable
MAP. The results are presented at that location or at a different location if
requested.
Manual tests
Certain testing requires manual assistance or intervention, such as the
periodic testing of the person/system interfaces or the ability to remove and
restore power from an equipment unit. These tests are simplified, and their
number minimized, to avoid procedural errors and to reduce the training and
continuing effort required of maintenance personnel.
Service recovery and protection measures
Fault recovery programs
The DMS-100 International maintenance system detects and analyzes faults,
takes corrective action, and alerts maintenance personnel as required. The

PLN-5001-001i Standard 02.02 April 1997

 Features 4–45

maintenance system consists of several subsystems, each of which is

responsible for its own level of hardware.
The responsibilities of each subsystem include:
• routine testing
• fault detection
• fault analysis
• error reporting, diagnostic report, and/or subsystem status
• reporting

To ensure the integrity of the DMS-100 International system software,

hardware and software mechanisms are provided to continually verify its
sanity. These mechanisms include data table indexing range checks, audits
of software structures, and a sanity timer which guards against software or
micro-program loop errors not otherwise detectable.
Initializations
The various levels of “loss of sanity” lead to different levels of initialization
in the central control. The number of levels executed depends on the
severity of the problem. If, at the highest level, the system fails to initialize,
an activity switch occurs and an attempt is made to initialize on the newly
active machine. A subsequent activity switch occurs if the first attempt fails.
After three unsuccessful attempts to switch activity and resume normal
operation, the bootstrap loader is activated in the auto-load mode.
Automatic service recovery and protection
Automatic service recovery and protection features that do not require
manual intervention are provided where trouble conditions affect service to a
group of customers. Dedicated software coordinates the automatic recovery
process, minimizing the length of equipment outages and the need for
manual intervention. Refer to page 2–34 of this document for additional
information on the system recovery controller (SRC).
Automatic treatment of errors
A failure in DMS-100 International systems can be diagnosed as either a
hard fault or a transient error. If a failure is diagnosed as a transient error,
the event is entered in the log. If the threshold is exceeded, the status is
changed on the MAP and a trouble record is output. The appropriate
equipment failure register is scored.
Automatic treatment of faults
Equipment units with detected faults are automatically removed from
service. The equipment experiencing fault conditions is removed from
service as soon as the fault is detected provided system operation is not
severely degraded.

DMS-100 International Technical Specification BCS40i and up

4–46 Features

Equipment selection procedures

Automatic equipment selection procedures are such that calls encountering a
trouble have a reasonably high probability of completion on subsequent
customer or system initiation.
Safeguards against taking good equipment out of service
Safeguards are provided so that trouble conditions within the service
recovery and protection facilities can be detected and the trouble isolated to
a minimum number of units. A trouble condition does not result in a large
proportion of non-faulty equipment being taken out of service.
Thresholds can be established.
Manual service busy
Manually initiated system initialization and reconsiderations supplement the
automatic capabilities.
Trouble notification
Facilities and procedures are provided to alert persons to the existence and
severity of a trouble condition. The notification provides adequate
information for craftspersons, with minimal training, to verify and locate the
trouble condition(s).
Three level alarm structure
The office alarm subsystem reports system trouble conditions to office
personnel located on-site or remotely. The severity of each trouble is
categorized as one of the following:
• Critical Alarm: The critical alarm indicates that a severe,
service-affecting condition has occurred and that immediate corrective
action is imperative, regardless of the time day or the day of the week.
An example of a critical alarm condition is a duplicated memory outage.
• Major Alarm: The major alarm can be a hardware alarm or a program
alarm. It indicates a serious disruption of service to customers, or
malfunctioning or failure of important circuits. These require immediate
corrective action to restore or maintain system capability. Thus, a major
alarm would justify the calling of a maintenance person at any time of
the day or night to an unattended office. An example of a major alarm
condition is when a trunk group has reached its out-of-service limit.
• Minor Alarm: This can be a hardware alarm or a program alarm. It
indicates the existence of a trouble that does not have a serious effect on
service to customers, or malfunctioning or failure of circuits that are not
critical to system operation. An example of a minor alarm condition is
when an individual trunk in a large trunk group is removed from service.

PLN-5001-001i Standard 02.02 April 1997

 Features 4–47

Audible alarms
The system provides the software and hardware for generating audible
alarms. Unique alarms are used to distinguish different alarm levels.
Visual displays
Visual displays are provided to indicate the various types of alarms locally
and at locations other than the maintenance control center in accordance
with local practices.
Output messages
In addition to audible and visual alarms, output messages report alarmed
maintenance information to the craftsperson. Reference to paper based
documents is not normally necessary to isolate the trouble and perform
further tests.
Trouble status indicators
Trouble status indicators in the office include (1) system status indicators
which display the status of the major units of equipment of the system (2)
state of health indicators which do not necessarily denote trouble but report
such conditions as system load, and (3) other visual indicators such as aisle
pilots and exit alarm panels.
Office alarm subsystem
The DMS-100 International alarm system generates audible and visual
indications of trouble conditions detected within the switch or in associated
equipment.
Alarm inhibit
Craftspersons can selectively inhibit certain non-critical alarms in special
situations where repeated alarms would mask valid alarms.
Trouble verification
The DMS-100 International switch takes actions to verify that a trouble
exists prior to providing a trouble indication. Additional testing can be
invoked prior to initiation of repair to determine the continued existence of
the problem and to verify that the trouble has been cleared. Thresholding is
available for certain classes of troubles in order to avoid premature service
recovery action and trouble notification.
Trouble sectionalization and isolation
Test hardware, software, and procedures are provided to locate a defective
unit with no disruption of service once a trouble condition has been detected
and verified.
Trouble location procedure
In order to facilitate the isolation of faults in DMS-100 International
systems, the maintenance and administration position is provided with a

DMS-100 International Technical Specification BCS40i and up

4–48 Features

telescoping process to determine the smallest number of replaceable units

which can be changed to restore system status to normal.
Diagnostics
These programs identify the failing element in a faulty unit to a relatively
few, quickly-changeable spare parts (for example, a circuit pack or a plug-in
module of apparatus). The simplicity and speed of repair is an essential
component of the overall system architecture. After a suspected faulty part
has been replaced, diagnostic programs can be requested in order to
determine if the trouble has been cleared or if the unit is still faulty.
The output of the diagnostic tests of a faulty unit identifies the location of
the failed replaceable elements. These diagnostic programs do not interfere
with the normal call processing programs or system operation.
Error analysis
The DMS-100 International system distinguishes between faults and errors.
Statistics on errors are stored and analyzed periodically and the results
printed out. When errors exceed a threshold, which in many cases is
customer changeable, the faulty equipment is automatically removed from
service and appropriate messages are routed to the log and/or alarm systems.
Recovery from faulty equipment
In DMS-100 International systems, all faults detected by diagnostics will
dictate a recovery procedure.
Equipment identification
In the DMS-100 International equipment identification scheme, a dual
identification code defines each equipment entity down to the card and
circuit level, in terms of its function and location. These codes appear on
each component in the packaging hierarchy (bay, shelf, card) and are also
stored in the system data base. The significance of this feature to the
maintenance personnel is that maintenance actions and equipment faults are
specified in system output by both location address and equipment function.
As a result, recovery time and the chance of human error are minimized.
Hardware changes
Where practical, hardware change to line circuit cards or trunk cards can be
accomplished by an adjustment which does not require removal of the card.
These adjustments are made by means of switches on the card.
It is not necessary to remove power from a peripheral equipment unit prior
to removal or insertion of circuit packs. It may be necessary, however, to
remove power from some other equipment units prior to removal or
insertion of circuit packs. Appropriate cautions are clearly identified and
documented.

PLN-5001-001i Standard 02.02 April 1997

 Features 4–49

User interfaces
For additional information on user interface features, refer to chapter 10,
“Maintenance”.
Maintenance and administration position (MAP)
The MAP provides an interface to assist in the fault recovery, isolation, and
recovery processes. The assignment of various maintenance and
administrative functions to specific MAP units is specified by the operating
company. A specific MAP unit can be assigned the capability to perform all
functions if desired. Alternately specific MAP units can be assigned subsets
of the total capability, or single functions.
Switching system control and display interface
The MAP VDU is the primary man-machine interface between maintenance
personnel and the DMS-100 International system. The VDU screen area
available for system output is 80 characters wide by 24 lines long. In the
maintenance mode, the screen is divided into a number of areas which
display the following types of information:
• System status area (three lines by 80 characters) indicates the alarm
and/or operational status of the system, with immediate automatic
updating of the current display.
• Work area (variable number of lines by 68 characters wide) provides:
— Descending levels of subsystem status
— Display of working data (posted trunk numbers and voltage and
frequency levels applied and measured).
• Command menu display area (20 lines by 12 characters wide) defines
the function which can be performed at the position at any given time.
• Command interpreter output area (variable number of lines by 58
characters wide) provides:
— Output of system reports (including error, action taken, and
diagnostic messages) upon operator request
— Output defining specific components of the system.
• Input echo area (one line by 68 characters) provides an echoed statement
of the most recent operator input command string.
• User identification and time (two lines by 12 characters) provides the
identification of the user logged into the MAP and the time of day.
Alarm release
Audible alarms in the DMS-100 International switch can be cancelled by the
removal of the alarm condition or, if the alarm is a result of a
system-detected fault, by the operation of a key on the Alarm Control and
Display Unit (ACD) located near the MAP. Subsequent audible alarms are
not inhibited.

DMS-100 International Technical Specification BCS40i and up

4–50 Features

Alarm and status indications displayed at the MAP cannot be retired

intentionally until the alarm condition is cleared.
Alarm transfer
This feature permits the transfer of major and minor alarm indications, for
the system and its power plant, to a distant office.
System maintenance input/output interface
The MAP provides an interface between maintenance personnel and the
DMS-100 International family of digital multiplex switching systems. The
tasks performed at the MAP include general maintenance functions (error
detection and diagnosis), administration functions (network management,
customer data modification, etc.) and trunk testing functions. The MAP is
designed to operate as a single entity for small office applications, as well as
a large system interface where a number of MAP units can operate
concurrently.
The basic components of the MAP include a VDU, with keyboard, a voice
communications module, testing facilities and optional position furniture.
The VDU screen will display system output, and inputs to the DMS system
are made through the VDU keyboard. Other devices such as printers can be
used in conjunction with the VDU. Printers associated with the VDU
operate in parallel with it.
Compatible input/output devices or terminals can be used in addition to the
standard MAP units for the various MAP functions.
Extended maintenance interface
Equipment frames include jacks on the FSPs so that portable MAP units can
be connected to the system. The configuration allows the device to transmit
and receive input and output messages. The jacks are placed such that the
portable MAP is located near the immediate vicinity of the equipment
undergoing test or repair.
The frames with electronics are equipped with an FSP as standard
equipment. In the case of double by frames, each bay is equipped with FSP.
To facilitate maintenance and administrative functions at the equipment
location, each line or trunk module frame is equipped with an I/O port
multiple for connection to a portable MAP or other ASCII compatible I/O
terminal. An extensive range of interrogation and control functions is
provided. For example, the status of a line or trunk can be displayed and it
can be made maintenance busy. Since trunk circuits can be packaged two or
more to a module circuit board, capability is provided to display the status of
individual circuits on the board and also to perform maintenance actions on
multiple circuits simultaneously.

PLN-5001-001i Standard 02.02 April 1997

 Features 4–51

Remote maintenance
This feature provides interfaces permitting full remote maintenance
operation excluding repair requiring physical action on equipment. The
feature allows, at the remote maintenance location, all MAP capabilities
available at the switching system location. These capabilities include: I/O
messages visual and audible status indications and alarm conditions,
equipment control, unit isolation, system reconfiguration and initialization,
office data access and change, and control of AC, DC and transmission tests
on trunks. These capabilities allow craftspersons at the remote maintenance
location to operate, administer and maintain the switching system with the
same effectiveness as at the switching system site.

Trunk, line and service circuit test features

Trunk maintenance
Means are provided to manually and automatically detect faulty incoming
and outgoing trunks and service circuits, to protect service from faulty
trunks, and to verify and isolate faults.
Trunk and line maintenance i/o interface
A trunk and line maintenance I/O interface is provided to permit the
craftsperson to enter messages concerning trunks or lines and to receive
appropriate output messages. This is done via a MAP designated as a trunk
test position (TTP) or line test position (LTP). MAP units can be assigned as
either TTP, LTP or both as required by the operating company.
Diagnostic tests
Outgoing trunks can be checked by placing program-initiated and controlled
test calls to test lines in the far-end office and detecting the response signals
received over the trunk. Incoming trunks can be tested for the ability to
change state under manually initiated or system controlled processes. Test
results are reported on the appropriate MAP channel and when a failure
results, trouble data isolates faulty components.
The system provides diagnostic data results which indicate the results of
each failing test performed by a diagnostic program. A diagnostic test can
be run several times on a specified trunk or service circuit via a single test
request. Means are provided to allow a diagnostic test of an outgoing trunk
to a specified type of far-end operational test line (synchronous or
nonsynchronous) or a permanent busy, instead of the normal diagnostic test.
Outpulsing tests
The outpulsing test allows the craftsperson to place a call and talk or listen
over a specified outgoing trunk. It is possible to specify the digits to be
out-pulsed over the trunk and the supervision returned over the trunk is
displayed at the test position.

DMS-100 International Technical Specification BCS40i and up

4–52 Features

Make busy/make idle control

The make busy/make idle control feature provides the ability to make a
specific trunk maintenance busy or idle by manual request.
Transmission measurements
Basic transmission measurements
It is possible to send tone and measure received tone level and frequency in
order to make possible two-way determination of the standard transmission
parameters affecting voice communications: loss (level), noise, gain-slope,
return loss. It is also possible to apply an AC open, an AC short, or a
balance termination.
Enhanced transmission measurements
It is possible, via external test equipment, to send tone and measure received
tone level and frequency in order to make possible two-way determination
of the standard transmission parameters affecting voice-band data
communications: peak-to-average ration, inter-modulation, impulse noise,
phase hits, gain hits, drop-outs, phase jitter, amplitude jitter, envelope delay
distortion, and frequency shift.
Supervisory tests
Upon request, the system displays the status of incoming supervision on
trunks and allows control of the state of outgoing supervision.
Trunk circuit diagnostics
The switching system provides trunk diagnostic results in response to
manual requests.
Monitor
Capability to monitor a line or trunk that is service busy is provided via an
optional headset trunk.
Talk
Capability is provided to set up a talk-and-listen connection, via a headset
trunk, to a specific idle trunk without outpulsing digits. Thus, a craftsperson
with the same capability at the far end of the trunk can talk and listen over
the facility on a prearranged basis.
Local office test lines
Test lines are provided for testing lines and incoming trunks from
connecting offices. The transmission test lines listed in this section can also
be used for tandem applications.
100-type test line
A 100-type test line provides a local office with equipment that first applies
a precise tone for a timed period, then a balanced termination for

PLN-5001-001i Standard 02.02 April 1997

 Features 4–53

transmission level and noise measurements. Line and trunk access are
provided to the 100-type test line.
101-type test line
A 101-type test line provides a communication line to a craft position.
102-type test line
A 102-type test line applies a precise tone for approximately nine seconds
on, one second off, in a repetitive sequence.
Faultsman’s ring-back
Faultsman’s Ring-back is a maintenance feature which is used by a
faultsman/linesman (field engineer) to test continuity of a line while on the
subscriber’s premises, without the help of a counterpart in the exchange. It
can also be used by the faultsman to obtain physical ringing on the
subscriber’s telephone to enable adjustment to be made to the ringer.

Administrative features
Refer to chapter 7, “Administration”, for additional information on
administrative features.
Data base management-memory alteration
Assignments
A means of specifying line/telephone numbers, trunks, routing, and charging
assignments is available. A means of specifying the miscellaneous
equipment assignments is also available.
Pending order file (POF)
With this feature, DMOs can be activated immediately upon entry or place
in POF in the system memory for activation at a later time. These DMOs
are input using File Editor and Table Editor commands. The file editor is
used to create the POF; the table editor DMO commands are stored within
the newly created file. While in the POF, DMOs can be queried, changed, or
deleted. They can also be activated individually or all at once with a single
command entry.
Initialization and growth
A means is provided to initialize the data model and the contents of the data
base, and for the data base to grow as additional equipment is added in the
office.
Office records verification and statistics
A means is provided to obtain office records and statistical summaries of the
data base for many operating company functions, perform ad hoc requests
for data in the data base, and audit a data base external to the central office
with the data base contained in the central office.

DMS-100 International Technical Specification BCS40i and up

4–54 Features

Translation verification (TRAVER)

The TRAVER feature permits the craftsperson to test their datafill by
entering commands from the MAP.
Depending on the options specified, TRAVER will either:
• simulate a call and display the routing information for the call (for
example (line, trunk, or console)
• display the translation and routing tables that the call accesses, and
provide some explanation of any assumptions made (for example,
default values), or invalid data.
Memory, backup and recovery
A means is provided to restore a damaged data base to a consistent state,
using a second source.
Program alteration
The DMS-100 International system provides efficient means of altering
system memory data for both emergency and routine situations.
Interface to centralized data base management centers
This feature allows the implementation of data base management functions
from centralized operations support centers external to the switching system,
using remote MAPs.
Data base integrity and security
Data base integrity
Measures are provided to protect the data base contents against invalid
operation and its accidental alteration or obliteration.
Data base security
A set of protection measures is provided to prevent unauthorized access to
the data base to protect against disclosure, alteration or obliteration of its
contents.
Monitoring of recent change area
Recent change area is not provided in DMS-100 International systems. See
“Pending order file” in this chapter.
Delayed Activation of Recent Change Message Pending order file is
provided in DMS-100 International systems.
Teletypewriter input/output
Input/Output capabilities for the DMS-100 International switch are provided
via MAP units. The units include cathode ray tube type output and keyboard
input capabilities. Optional hard copy printers can also be equipped.
Multiple MAP units are normally provided as required by the operating
company.

PLN-5001-001i Standard 02.02 April 1997

 Features 4–55

Assignment of functions such as maintenance, traffic measurement, service

order or line/trunk testing are flexible. Single or multiple functions can be
assigned to particular MAP units or groups of units.
Automatic traffic measurements
The system accumulates peg counts and usage data on lines, groups of lines,
trunks, groups of trunks, service circuits, groups of service circuits, and call
processing registers. Peg count and usage data are automatically generated
by locally or remotely located devices for the periods consisting of each
quarter-hour, half-hour, and total day.
Event measurements
Event measurements provide an accumulation of the number of times a
specific system action occurs.
Usage measurements
Usage is the duration of a specified condition, normally the busy condition
of a server. (A server is a system component that performs operations
required for the processing of a call). This information is collected, summed
and accumulated over time intervals which are specified for the type of
server.
Data base statistics
Traffic data analysis requires that the switch be capable of reporting the
number of members or groups associated with specific traffic data (for
example, the number of trunks in a trunk group). These statistics are
available in response to a query.
Measurement applications
Office totals
Office total measurements provide a picture of the system as a total
environment (primarily using type and number of call activities performed),
and an indication of system quality in terms of number and type of
uncompleted activities.
Component measurements
Standard measurements are provided for each traffic sensitive system
component. A traffic sensitive component is a group of servers that provide
less than 100 percent switched capacity, that is, a group of servers for which,
when all are in use, the probability of another request for use exists. The
term component includes hardware and, if appropriate, software server
groups. The measurements are provided on a per-group basis and reflect the
sum of the individual servers in the group.
Network measurements
A system network is a set of common paths used to interconnect various
system components required for call processing. The paths are formed by

DMS-100 International Technical Specification BCS40i and up

4–56 Features

the use of switched link chains, which has the effect of providing wide
access using limited servers. The network measures are event measures (for
example, terminating calls) or usage measures (for example, service circuits
usage) that relate to the performance of the network.
Customer measurements
Service offerings for individual customers that result in the definition, within
the system, of a functional (from a call processing point of view) and private
(from a tariff point of view) grouping of lines or stations can have associated
measurements on a group basis.
Validity measurements
Information is provided with operational measurement that allow the data
user to judge the reliability of the data.
Service measurements
Customer access service measurements
See section “Automatic traffic measurements” in this chapter.
Maintenance service measurements
Maintenance measurements provide data which can be used to evaluate
equipment performance and the impact of troubles on customer service, and
also to calculate an operating company defined performance index.

Network administration center I/O channel

Data verification capabilities
NAC verification of translation data
A MAP can be provisioned to allow administrative personnel to query the
translation data of the system.
System status information retrieval
This feature allows the NAC to use the MAP to:
• query the switching system for office performance (for example,
processor overload) and control status information
• receive the above information automatically when status changes occur
• change the control status for Essential Service Protection.

Traffic data query capability

This feature enables the NAC, using the MAP, to query the switching system
for selected traffic data measurements, acting as a backup to normal data
collection and critical network management controls.
Verification of traffic schedules
The system, upon request, produces an output of the traffic report from the
previous collection interval.

PLN-5001-001i Standard 02.02 April 1997

 Features 4–57

Network management (NM)

Network management is a set of real-time procedures that optimizes network
performance when the network is under stress due to adverse conditions.
Network management features available on DMS-100 International systems
for both local and tandem applications provide and operate control and
surveillance features that aid in maintaining network integrity and security
during overloads and failures.
Unlike internal switching system overload controls, which modify the
internal call processing functions under overload to maximize the efficiency
of the switching system, network management controls modify and optimize
the flow of traffic in the entire network.
Manual network management controls
Manual network management controls supplement and augment automatic
network management controls. Manual controls also provide more
flexibility in coping with situations that require human judgment. Manual
controls, such as reroutes, can be expansive in nature. Alternatively, they
are protective by cancelling or blocking traffic that cannot be completed.
Manual controls are activated and deactivated at NMCs through the system
which supports the operation of the NMC.
Trunk group controls
Manual trunk group controls are of two types: protective and expansive.
Protective controls can be used to inhibit the spread of congestion in the
network by restricting normal trunk groups access and overflow. Protective
trunk group controls include trunk group cancel and skip controls.
Expansive controls are used to exploit routing beyond the normal in-chain
routes, when in-chain routes are busy or have failed, and idle capacity exists
in out-of-chain routes. The control which accomplishes this is called a
reroute control.
Network management surveillance data
The MAP in the NMC provides surveillance data on the switching system.
The data are displayed on a regular basis.
The display is automatically refreshed every minute to display system
performance data and the types of controls in effect.
Centralized network management
Network managers in NMCs require real-time network surveillance data and
manual controls. Network managers are expected to intervene in problems
for which automatic solutions would be excessively expensive and in
problems requiring human judgment. DMS-100 International systems
provide these capabilities using a MAP in the NMC.

DMS-100 International Technical Specification BCS40i and up

4–58 Features

Backup network management capabilities

Multiple MAP facilities can be provisioned for the NMC.
Miscellaneous features
Trunks out-of-service for data changes
Changing trunk data can affect call processing if the trunk is busy. This
feature informs the craftsman via a message if all trunks in a trunk group or
subgroup are not out of service. Once all trunks are out of service, a data
change can be made without affecting call processing.
Automated records
The DMS-100 International system provides a number of administrative aids
that provide the operating company with a method of generating online
system records (for example, circuit assignments, card assignments, etc.).
These aids can be used to reduce the amount of paper records.
Cut-over and growth features
Online growth procedures and tests
The DMS-100 International system provides the capability to add, change or
remove equipment to or from an existing operational system without service
degradation. This capability applies to major functional equipment,
peripheral equipment and minor functional equipment. Test facilities are
provided for use during the above operations.

PLN-5001-001i Standard 02.02 April 1997

 5–1

Call processing
This chapter summarizes the manner in which call processing occurs on
DMS-100 International switches. The explanations in this chapter are
general in nature and apply to generic DMS-100 International capabilities,
which may be modified for individual market requirements. The specific
handling of call processing for DMS-100 International switching systems
varies depending on the market in which the system is deployed, the
application of the system, and the hardware and software provisioned.
Call processing software in DMS-100 International switches is distributed
between the central control element (the Central Control on NT40-based
systems, or the DMS-Core on SuperNode-based systems) and the peripheral
modules (PMs). The following paragraphs and illustrations describe the
sequence of events for line and trunk originated calls, followed by a
structural description of DMS-100 International call processing software in
general.
Line originated calls
The following is the sequence of events for line originated calls:
1 A seizure is detected from an idle line.
2 If system resources (for example, universal tone receiver for MF lines, or
ILGC-to-network DS30 channel) are available to handle the call
origination request, the system performs step 4.
Otherwise, the system performs step 3.
3 No treatment is applied to the originator until the required system
resources are available (the subscriber does not receive any tone).
— If the originator releases before system resources are available, the
line returns to idle state.
— If the originator remains off-hook until the system resources are
available, the system performs step 4.
4 Dial tone is applied to the line and a timer is started to record the timeout
for the reception of the first digit.
— If the first digit is received before this timeout, dial tone is removed
from the line and the system performs step 6.
— Otherwise, the system performs step 5.

DMS-100 International Technical Specification BCS40i and up

5–2 Call processing

5 Permanent signal treatment is applied to the line, and resources allocated

for the call are freed.
Note: See related paragraph for a list of treatments used in DMS-100
International systems. Treatments are applied until the subscriber
releases or a timeout occurs. In either case, system resources allocated
to the call are freed when the treatment ends. If the subscriber releases
before timeout, the line returns to idle state. Otherwise, the line remains
in lockout state until the subscriber releases (that is, goes on-hook).
6 The system collects the digits dialed by the subscriber as follows:
a. An inter-digit timeout is recorded between the digits. If this timeout
expires, partial dial treatment is applied to the line, and resources
allocated for the call are freed.
b. Depending on the first digit(s) dialed, the system determines the total
number of digits to be dialed by the subscriber.
c. Depending on the first digit(s) dialed, special dial tone may be
applied to the line.
d. Upon completion of digit reception, the system performs step 7.
7 Translation and routing capabilities of the system attempt to determine
the terminating agent. The system identifies the termination as one of
the following:
— an unassigned directory number within the same office. Blank
directory number treatment is applied to the originating line.
— an unassigned office, city, or country code. Vacant code treatment is
applied to the originating line.
— no free trunk available within the route list. General no circuit
treatment is applied to the originating line.
— a subscriber line. The system performs step 8.
— a line in a hunt group (for example, a PABX line). The system
performs step 17.
— an outgoing trunk. The system performs step 18.
8 The status of the terminating line is checked. If the line is busy, busy
treatment is applied to the originating line. Otherwise, the system
performs step 9.
9 The system attempts to allocate an ILGC-to-network channel for the
terminating line. If this fails, network blockage normal traffic treatment
is applied to the originating line. Otherwise, the system performs step
10.
10 The system attempts to make a network module (NM) connection
between the two agents. If this is successful, the system performs step
12. Otherwise, it performs step 11.

PLN-5001-001i Standard 02.02 April 1997

 Call processing 5–3

11 If an alternate ILGC-to-NM channel is available for the terminator, an

alternate network connection is attempted. If this fails, network
blockage heavy traffic treatment is applied to the originating line. If the
attempt is successful, the system performs step 12.
12 A network connection is made between the two lines, and the system
performs step 13.
13 If a ringing failure occurs in the terminating ILGC, busy treatment is
applied to the originating line, and the terminator is marked idle.
Otherwise, the system performs step 14.
14 ringing is applied to the terminator, audible ringback tone is applied to
the originator, and the system performs step 15.
15 During the ringing period:
a. There are two timeouts:
– ringing TMO on terminator
– noanswer ringing on originator.
b. If the terminating line does not answer before the ringing timeout:
– ringing is removed from the terminating line.
– audible ringback tone is removed from the originating line.
– the network connection is freed.
– the terminating line is marked as idle.
– disconnect treatment is applied to the originating line (after
timeout).
c. If the originator releases before the terminator answers:
– ringing is removed from the terminator
– audible ringback tone is removed from the originator
– the network connection is freed.
– both lines are marked as idle.
– system resources allocated for the call (for example, call
condense block) are freed.
d. If the terminating line answers:
– ringing is removed from the terminator.
– audible ringback tone is removed from the originator
– metering starts (unless the terminating line is a free number).
The two parties are now in line-line talking state.
– the system performs step 16.
16 After an answered call is established between two lines:
a. If the originating party releases first:
– metering stops.

DMS-100 International Technical Specification BCS40i and up

5–4 Call processing

– the originating line is marked idle.

– the network connection is freed.
– disconnect treatment is applied to the terminating line (after
timeout).
b. If the terminating party releases first:
– the terminating line is marked idle.
– the network connection is freed.
– disconnect treatment is applied to the originating line.
– metering stops.
17 The appropriate hunting algorithm is applied (see section on hunting). If
the call can be terminated on a line in the hunt group, the system
performs step 12. Otherwise, busy treatment is applied to the originating
agent. If the call cannot be terminated on a line in the hunt group due to
connection or channel blocking in the ILGC or NM, the entire group is
hunted for a second time before busy treatment is applied to the
originating agent.
18 A network connection is made between the two agents. The outgoing
trunk is seized, and digits to identify the terminating agent are sent to the
targeted office. After completion of digit sending:
a. If an answer signal is received from the terminating agent:
– metering starts. The two parties are now in line-trunk talking
state. The system performs step 19.
b. If the originating line releases:
– a clear forward (CLF) signal is sent via the outgoing trunk.
– both agents are marked idle.
– the network connection is freed.
– system resources allocated for the call (for example, call
condense block) are freed.
19 After an answered line-to-trunk call is established between the
originating line and the outgoing trunk:
a. If the originating party releases first:
– metering stops.
– a clear forward (CLF) signal is sent via the outgoing trunk.
– both agents are marked idle.
– the network connection is freed.
– system resources allocated for the call (for example, call
condense block) are freed.
b. If the terminating party releases first,

PLN-5001-001i Standard 02.02 April 1997

 Call processing 5–5

– a timer is started to wait for a possible re-answer by the

terminating party
– the system performs step 20.
20 During the re-answer timing period:
a. If the terminating party re-answers:
– the system performs step 19.
b. If the re-answer timeout expires:
– the terminating trunk is marked idle.
– the network connection is freed.
– disconnect treatment is applied to the originating line.
– metering stops.
Figure 5–1xxx
Processing of line originated calls
FW-31171

Originating Seizure DMS-100 Ringing Terminating

line international line
Dial tone Answer
Digit Release
Ringback tone Seizure
Release Call forward Outgoing
trunk
Answer
Release

DMS-100 International Technical Specification BCS40i and up

5–6 Call processing

Figure 5–2xxx
Key for line and trunk originated call flow illustrations

Internal Internal External External

input input input input

External External External External

output output output output

Step Decision
State

PLN-5001-001i Standard 02.02 April 1997

 Call processing 5–7

Figure 5–3 – Line originated call flow

idle

seizure

System N
resources wait for
available? resources

Y
Allocate
resources. Start
timer for 1 digit. System
resources release
available

dial tone
idle

digit wait

—continued—

DMS-100 International Technical Specification BCS40i and up

5–8 Call processing

Figure 5–3 – Line originated call flow

1 digit wait
I

digit digit
timeout

collect digits PSIG

treatment

all digits N
dialed?
treatment
release time out
Y

translation and
routing
free system free system
resources resources

A
originating
idle line
lockout

PDIL release
treatment

I idle

—continued—

PLN-5001-001i Standard 02.02 April 1997

 Call processing 5–9

Figure 5–3 – Line originated call flow

A single subscriber line

B

Determine type hunt group

of terminating C
agent.

outgoing trunk
D

unassigned DN within same office

unassigned office, city, or country code

BLDN treatment
no free trunk available
within route list

VACT treatment

GNCT
treatment

class of service (COS)

restriction

appropriate
treatment

—continued—

DMS-100 International Technical Specification BCS40i and up

5–10 Call processing

Figure 5–3 – Line originated call flow

idle busy
line status?

Is there an N
LGC to CC NBLN treatment busy treatment
channel?

I I

Can the NM N Try alternate

make the path-end
connection?

Make Y connection
connection possible?

N
Ringer OK? busy treatment NBLH treatment

L I I

—continued—

PLN-5001-001i Standard 02.02 April 1997

 Call processing 5–11

Figure 5–3 – Line originated call flow

IDLE Try alternate

line status? path-end

BUSY Is there an Y Can the NM N

ILGC-to-CC make the
channel? connection?
Y call possible
all lines Y N Y now?
already S
hunted twice?
N
N all lines Make the all lines
N connection N
already already
hunted twice? hunted twice?
N
Y N Y

Y
Is the ringer NBLH treatment
Hunt next line NBLN treatment ok?

N L

I all lines I
already
hunted twice?

S Y N

busy treatment

—continued—

DMS-100 International Technical Specification BCS40i and up

5–12 Call processing

Figure 5–3 – Line originated call flow

ringing

ringback tone

answer wait

answer
timeout release answer

Remove ringing. Remove ringing. Remove ringing.

Remove audible Remove audible Remove audible
ringback tone. ringback tone. ringback tone.
Free network Free network Start metering.
connection. connection.
Mark term. line Mark both lines
idle. idle. Free
system line-to-line
resources. talking
originating line
disconnect
treatment idle
release release

I
Idle originating Idle terminating
line. Free line. Free
network network
connection. connection.
Stop metering. Stop metering.

terminating line originating line

disconnect disconnect
treatment treatment

—continued—

PLN-5001-001i Standard 02.02 April 1997

 Call processing 5–13

Figure 5–3 – Line originated call flow

make network
connection

seizure

send digits

trunk answer
wait

release answer

clear Start metering

forward
T

Free network line-to-trunk

connection. talking
Mark both
agents idle.
Free system
resources.
release release

idle
clear
forward reanswer wait

Stop metering

—continued—

DMS-100 International Technical Specification BCS40i and up

5–14 Call processing

Figure 5–3 – Line originated call flow

originating line
disconnect reanswer wait
treatment

release treatment reanswer

answer
timeout timeout

Free system Free system T clear

resources resources forward

idle terminating line Free network

lockout connection.
Mark outgoing
trunk idle.

originating line
disconnect
treatment

End

Treatments
Following is a list of the treatments set by DMS-100 International Family
Systems. Other treatments can also be datafilled to an office.
• BLDN – blank directory number. This treatment is required for routing
of unassigned directory numbers.
• BUSY – busy line. The treatment to which a line or trunk is routed
when the terminating line is not idle. Some examples are:
— when a line dials its own directory number.
— when a line or trunk dials a number which is busy.
— when the called line has been seized for testing.
— when the PM for the called line is busied for maintenance.

PLN-5001-001i Standard 02.02 April 1997

 Call processing 5–15

• CONF – confirmation tone. The treatment to which a line with call

forwarding or speed calling is routed upon dialing the activation code for
the feature. The route list elements for this treatment should consist of
confirmation tone, no tone, and lockout.
• DISC – disconnect timing. The treatment to which a line is routed, when
the subscriber fails to go on-hook within ten seconds after the other party
terminates the call.
• DNTR – denied terminating. The treatment to which a line or trunk is
routed upon dialing a directory number which terminates in the
switching unit and has the denied terminating (DTM) option.
• GNCT – generalized no circuit. This treatment occurs if the trunk group
is the last route and all trunks busy condition is encountered on the route
list. In addition, GNCT will be pegged.
• NBLH – network blockage heavy traffic. The treatment given to a call
when the immediate course of failure is the inability to get a path
through the network.
• NBLN – network blockage normal traffic. The treatment to which a call
is routed, when the call is being aborted due to connection or channel
blocking. This includes:
— blocking in channels between NM and the terminating ILGC.
— connection blocking in the terminating ILGC.
— blocking in channels between the terminating ILGC and ILCM.
— blocking (failure to get a channel) in the terminating peripheral
module.
• NCRT – no circuit. The treatment to which a routine call is deflected by
network management to NCA. This treatment may also be specified by
a network manager for calls aborted through operation of cancel-from or
cancel-to network management controls.
• ORSS – originating service suspension. The treatment to which a line
with denied originating (DOR) or the suspended service (SUS) option is
routed on originating a call.
• PDIL – partial dial timeout. The treatment given when at least one digit
has been received, but not all those required to complete the call.
— For calls on MF trunks, partial dial rather than permanent signal
treatment is administered if a MF KP signal has been received.
— If no MF ST signal is received, the correct treatment is still partial
dial, but if a ST signal is received which is invalid in the context of
the call, the proper treatment is reorder.
• PSIG – permanent signal timeout. The treatment given when no digits
are received before timeout. Calls for which distorted signals (rather
than none at all) have been received are given reorder treatment.

DMS-100 International Technical Specification BCS40i and up

5–16 Call processing

• RODR – reorder. The treatment given to calls upon a variety of resource

failures to inform the originating agent that the attempt should be tried
again.
• SYFL – system failure. The treatment to which a call is routed if the call
must be aborted due to a failure of the switching unit whether in
software or hardware. This includes the following types of failures:
— call failure or integrity loss from port 1.
— miscellaneous messages from port 2.
— software failures or error conditions.
— line-to-line, line-to-trunk, or trunk-to-line error takedown.
— miscellaneous error returns during setup.
— integrity loss while receiving digits.
— ring failures.
• TESS – terminating service suspension. The treatment to which a line or
trunk is routed when a call to a line which has the suspended service
option (SUS) assigned in the LEN Lines table.
• VACT – vacant code treatment. The treatment to which a call is routed
when one of the following conditions is encountered:
— when an unassigned code in the country code table is dialed
— a line or operator to test line call.
• TRBL – trouble intercept. The treatment applied to originating lines
with plugged-up (PLP) option.
Class of service (COS) restrictions
DMS-100 International systems can be datafilled to apply appropriate
treatments upon COS restrictions.
The treatment for denied origination (DOR) is hard-coded as originating
service suspension (ORSS).
Terminating lines may have denied termination (DNTR) restriction or line
options like suspended line (SUS) and plugged up line (PLP). For these
cases, DNTR treatment, or any other appropriate treatment, can be
datafilled.
Hunt groups
Directory number hunting (DNH)
Each line in the hunt group has its own directory number (DN). The hunt
group can be accessed by dialing the main number (Pilot DN) or by calling
the DN of one of the hunt group members. Hunting starts at the number
dialed. The number of lines hunted to find an idle line is dependent on the
hunting option assigned to the DNH group.

PLN-5001-001i Standard 02.02 April 1997

 Call processing 5–17

If option CIR (circular hunting) is assigned to the group, all lines in the
group are hunted, regardless of the start point of hunting. If CIR is not
assigned, the default is sequential hunting (sometimes called linear hunting).
Sequential hunting starts at the number dialed and ends at the last number in
the hunt group. Therefore, if the pilot DN is not dialed, not all lines are
hunted.
Multi-line hunting (MLH)
There is only a pilot DN associated with the hunt group. To access the
group, the pilot DN is dialed. Hunting starts with the pilot DN and ends at
the last line, in sequential order.
Distributed line hunting (DLH)
Hunting always starts on the subsequent (idle at the time last one was
selected) line in the group. DLH is assigned to large hunt groups which
require equal distribution of calls.
During hunting, lines which are busy, have a termination restriction, or are
marked as failure suspects will be skipped. Lines which cannot be
connected due to ILGC or network blocking due to traffic conditions are
also skipped. If the call cannot be terminated at any line at the end of
hunting, the hunting algorithm is repeated, this time also trying the failure
suspected lines. If this also ends with no successful termination, then busy
treatment is applied to the originator.
Trunk originated calls
DMS-100 International systems handle trunk originated calls as follows:
1 An incoming trunk sends an origination message to the CC.
2 If system resources (for example, universal tone receiver) are available
to handle this call origination request, the system performs step 4.
Otherwise, the system performs step 3.
3 No treatment is applied to the originating trunk until the required system
resources are available.
— If the originator releases before the system resources are available, it
is returned to idle state.
— If the system resources are available before the originator releases,
the trunk becomes CPB and looks for digits. It then sends PTS back.
— Meanwhile, if the originator releases, the trunk is marked as idle.
4 The originating office is signaled to proceed to send (PTS) the digits.
Digits sent by the originating office are collected by the incoming trunk
and sent to the CC upon completion of this process.
5 Translation and routing capabilities of the system attempt to identify the
terminating agent as one of the following and act accordingly:

DMS-100 International Technical Specification BCS40i and up

5–18 Call processing

— an unassigned directory number within the same office. Blank

directory number treatment is applied to the originating agent.
— an unassigned office, city, or country code. Vacant code treatment is
applied to the originating agent.
— no free trunk available within the route list. General no circuit
treatment is applied to the originating agent.
— a subscriber line. The system performs step 6.
— a line in a hunt group (for example, a PABX line). The system
performs step 16.
— an outgoing trunk. The system performs step 17.
6 The status of the terminating line is checked. If the line is busy, busy
treatment is applied to the originating agent. Otherwise, the system
performs step 7.
7 The system attempts to allocate an ILGC-to-network (NM) channel for
the terminating line. If this attempt fails, network blockage normal
traffic treatment is applied to the originating agent. Otherwise, the
system performs step 8.
8 The system attempts to make a network connection between the two
agents. If this attempt is successful, the system performs step 10.
Otherwise, it performs step 9.
9 If an alternate ILGC-to-NM channel is available for the terminator, an
alternate network connection is attempted. If this attempt also fails,
network blockage heavy traffic treatment is applied to the originating
agent. If the attempt is successful, the system performs step 10.
10 A network connection is made between the two agents, and the system
performs step 11.
11 If a ringing failure occurs in the terminating ILGC, busy treatment is
applied to the originating agent. Otherwise, the system performs step 12.
12 Ringing is applied to the terminator, audible ringback tone is applied to
the originator, and the system performs step 13.
13 During the ringing period:
a. If the terminating line does not answer before the ringing timeout:
– ringing is removed from the terminating line.
– audible ringback tone is removed from the originating trunk.
– the network connection is freed.
– the terminating line is marked as idle.
– the originating trunk is set to lockout state.
b. If the originator releases before the terminator answers:
– ringing is removed from the terminator.
– audible ringback tone is removed from the originator.

PLN-5001-001i Standard 02.02 April 1997

 Call processing 5–19

– the network connection is freed.

– both agents are marked as idle.
– system resources allocated for the call (for example, call
condense block) are freed.
c. If the terminating line answers,
– ringing is removed from the terminator.
– audible ringback tone is removed from the originator.
– answer is propagated to the previous office (unless the
terminating line is a free number). The two parties are now in
trunk-line talking state.
– The system performs step 14.
14 After an answered trunk-to-line call is established between the incoming
trunk and the terminating line:
a. If the originating party releases first (that is, a clear forward is
received):
– the originating trunk is marked idle.
– the network connection is freed.
– disconnect treatment is applied to the terminating line.
b. If the terminating party releases first:
– a clear back (CLB) signal is sent via the incoming trunk (unless
the terminating line is a free number, in which case no answer
was sent to the originating office upon answer).
– the system performs step 15.
15 With the terminating party on hook:
a. If the terminating party re-answers before a CLF is received from the
originator:
– answer is propagated to the originating office (unless the
terminating line is a free number). The two parties are back in
the trunk-line talking state, and the system performs step 14.
b. When the originating party releases (that is, a CLF is received),:
– both agents are marked idle.
– the network connection is released.
– system resources allocated for the call (for example, call
condense block) are freed.
16 The appropriate hunting algorithm is applied. If the call can not be
terminated on a line in the hunt group (that is, an idle line with no
blocking for connection in an ILGC or NM), busy treatment is applied to
the originating agent. Otherwise, the system performs step 10.

DMS-100 International Technical Specification BCS40i and up

5–20 Call processing

17 The outgoing trunk is seized and digits to identify the terminating agent
are sent to the targeted office. After completion of digit sending:
a. If an answer signal is received from the terminating agent:
– answer is propagated to the originating agent. The two parties
are now in trunk-trunk talking state.
– the system performs step 18.
b. If the originating agent releases (that is, a CLF is received):
– clear forward is propagated to the terminating office via the
outgoing trunk.
– both agents are marked idle.
– the network connection is freed.
– system resources allocated for the call (for example, call
condense block) are freed.
18 After a trunk-to-trunk call is established between the two agents:
a. If the originating party releases first (that is, a CLF is received):
– clear forward is propagated to the terminating office via the
outgoing trunk.
– both agents are marked idle.
– the network connection is freed.
– system resources allocated for the call (for example, call
condense block) are freed.
b. If the terminating party releases first (that is, a CLB is received):
– clear back is propagated to the originating office via the
incoming trunk (unless no answer was sent to the originating
office).
– the system performs step 19.
19 With the terminating party on hook:
a. If the terminating party re-answers before a CLF is received from the
originator:
– answer is propagated to the originating office (unless the
terminating line is a free number). The two parties are back in
the trunk-trunk talking state, and the system performs step 18.
b. When the originating party releases (that is, a CLF is received):
– Both agents are marked idle.
– the network connection is freed.
– system resources allocated for the call (for example, call
condense block) are freed.

PLN-5001-001i Standard 02.02 April 1997

 Call processing 5–21

Figure 5–4xxx
Processing of trunk originated calls
FW-31170

Incoming Origination points DMS-100 Ringing Terminating

trunk international line
Digit Answer

Ringback tone Release

Answer Seizure
Answer Outgoing
Call forward trunk
Call block Call forward
Call block

DMS-100 International Technical Specification BCS40i and up

5–22 Call processing

Figure 5–5 – Trunk originated call flow

idle

origination

System N
resources wait for
available? resources

allocate
resources System
resources clear forward
available

proceed to send
idle

wait for digits

clear forward digits digit timeout

Release system translation and PSIG or PDIL

resources routing treatment

A I
idle

—continued—

PLN-5001-001i Standard 02.02 April 1997

 Call processing 5–23

Figure 5–5 – Trunk originated call flow

A single subscriber line

B

Determine type hunt group

of terminating C
agent.

outgoing trunk
D

unassigned DN within same office

unassigned office, city, or country code

BLDN treatment
no free trunk available
within route list

VACT treatment

GNCT
treatment

class of service (COS)

restriction

appropriate
treatment

—continued—

DMS-100 International Technical Specification BCS40i and up

5–24 Call processing

Figure 5–5 – Trunk originated call flow

idle busy
line status?

Is there an N
ILGC to CC NBLN treatment busy treatment
channel?

I I

Can the NM N Try alternate

make the path-end
connection?

Make Y connection
connection possible?

N
Ringer OK? busy treatment NBLH treatment

L I I

—continued—

PLN-5001-001i Standard 02.02 April 1997

 Call processing 5–25

Figure 5–5 – Trunk originated call flow

IDLE Try alternate

line status? path-end

BUSY Is there an Y Can the NM N

ILGC-to-CC make the
channel? connection?
Y call possible
all lines Y N Y now?
already S
hunted twice?
N
N all lines Make the
N connection all lines
already N
hunted twice? already
hunted twice?
N
Y
N Y
Y
Is the ringer NBLH treatment
Hunt next line NBLN treatment ok?

N L

I all lines I
already
hunted twice?

S Y N

busy treatment

—continued—

DMS-100 International Technical Specification BCS40i and up

5–26 Call processing

Figure 5–5 – Trunk originated call flow

ringing

ringback tone

answer wait

answer
timeout clear forward answer

Remove ringing. Remove ringing.

Remove audible Remove audible Remove ringing.
ringback tone. ringback tone. Remove audible
Free network Free network ringback tone.
connection. connection.
Mark term. line Mark both
idle. Free agents idle.
system Free system trunk-to-line
resources. resources. talking

originating trunk idle E

lockout

clear forward

idle

—continued—

PLN-5001-001i Standard 02.02 April 1997

 Call processing 5–27

Figure 5–5 – Trunk originated call flow

trunk-line talking

clear forward release

Idle originating
trunk. Free clear back
network
connection.

clear forward
wait
terminating line
disconnect
treatment

clear forward answer

release treatment
timeout Free network answer
connection.
Mark both
Free system Free system agents idle.
resources resources Free system
resources.
talking*

idle terminating line idle

lockout

*trunk-to-line talking for a trunk-to-line call, trunk-to-trunk talking for a trunk-to-trunk call.

—continued—

DMS-100 International Technical Specification BCS40i and up

5–28 Call processing

Figure 5–5 – Trunk originated call flow

seizure

send digits

trunk answer
wait

clear forward answer

clear
forward answer

Free network trunk-to-trunk

connection. talking
Mark both
agents idle.
Free system
resources.
clear forward clear back

idle
clear clear back
forward

clear forward
wait

—continued—

PLN-5001-001i Standard 02.02 April 1997

 Call processing 5–29

Figure 5–5 – Trunk originated call flow

clear forward treatment

timeout

Free system Free system

resources resources

originating trunk
idle lockout

clear forward

idle

End

Software description
Call processing functional concepts
The function of DMS-100 International call processing software is to
establish connections among telephony agents. The connections thus
established may be used to transmit voice or data. A telephony agent is
defined as any kind of line or trunk, or any special service circuit that
performs a telephony function.
The following table lists examples of telephony agents and briefly specifies
the function of each:
Agent Function
line for subscriber access
trunk for calls between switches
echo suppressor for reducing echo on trunks
announcement for recorded announcements
conference circuit for toll break-in

DMS-100 International Technical Specification BCS40i and up

5–30 Call processing

DMS-100 International call processing software accommodates a large

number of custom calling features. All of these capabilities are built upon
the basic software architecture for call processing.
Basic telephone call – general steps
The main call processing task is to establish a basic voice call between two
telephony agents. For this call:
• Each of the two agents involved in the call can be either a line or a trunk.
• No subscriber services are in effect during the call.

The functional steps required to process this call are as follows:

1 Detect the incoming call: detect a line off-hook or the seizure of an
incoming trunk.
2 Receive the digits: determine what type of signaling the originating
agent is using, and collect the digits.
3 Translate the digits: analyze the digits to determine the call destination.
4 Select a terminating agent: find the best available route for the call.
5 Establish the telephony connection: set up a speech path between the
originating and terminating agents.
6 Signal the terminating agent:
— If the terminator is a line, apply ringing and give audible ringback
tone to the originator.
— If the terminator is a trunk, out-pulse the digits.
7 Detect answer:
a. Detect an answer signal from the terminating agent.
b. Start metering. Record the answer time if call recording is required.
8 Detect disconnect:
a. Detect a disconnect signal from either the originator or the
terminator.
b. Stop metering and record the disconnect time if required.
c. Take down the telephony connection.
d. Idle the originating and terminating agents.
Basic telephone call – DMS call processing sequence
The functional steps described above are performed by the DMS-100
International switch through interaction between the central control complex
(CC), the network modules (NMs), and the peripheral modules (PMs).
These system components interact by exchanging messages.
The messages exchanged by the CC, NMs, and PMs for a basic voice
telephone call are illustrated in figure 5–6. Messages exchanged between the

PLN-5001-001i Standard 02.02 April 1997

 Call processing 5–31

CC and the PMs for metering purposes are not included in this diagram for
the sake of simplicity.
Figure 5–6xxx
Message exchanged by CC, NMs and PMs for a basic voice call
FW-31169

Step 1 Control Origination Peripheral

complex module 1
Start digit collection

Digits
Step 2
Collect more digits

Last digits
Network
Connect network path
module 1
Connect network path

Connect network path Supervise connection

Network
Step 5 module 2

Connect network path

Peripheral
module 2 Supervise connection,
Step 6 signal terminator
CSM-SV bit (Indicates answer)
Step 7
Answer

CSM-SV bit (Indicates disconnect)

Step 8 Disconnect Disconnect

The functional steps involved in a basic voice telephone call as performed

by the various components of the DMS-100 International switch are as
follows:
1 Detect the incoming call:
a. A peripheral processor in a PM detects a line off-hook or a trunk
seizure.
b. The PM sends an origination message to the CC.
c. If the required software resources are available for the CC to process
the call, the CC sends a message to the PM, acknowledging the
origination. If the resources are not available, the CC ignores the
origination.

DMS-100 International Technical Specification BCS40i and up

5–32 Call processing

If the originating agent is a line, the message from the CC directs the
PM to give dial tone to the originator.
2 Receive the digits:
The peripheral knows the action to be taken to receive the digit
information from the originating agent and proceeds accordingly.
For DP lines and trunks, no receiver is required.
For multifrequency (MF) trunks, dual-tone multifrequency (DTMF)
trunks, or DTMF lines, the PM connects a universal tone receiver
(UTR) to the originating agent.
The manner in which digits are collected and sent to the CC depends on
the numbering plan used. In some cases, the PM contains the required
decision mechanism to complete the digit collection by itself and sends
only one “digits” message to the CC. In other cases, CC processing may
be necessary to determine the number of digits to collect. In such cases,
the CC begins translating the digits and sends messages to the PM telling
it how many more digits to collect. Several digits messages may be
required before all digits are received.
While waiting for digits, no processing by the CC is needed until another
message is received, so the CC condenses the call. To condense the call:
— The CC saves all information necessary to resume call processing
when a message arrives.
— The CC releases all software resources which are not required while
the call is not active. These resources can then be used by another
call.
When the CC receives a message for a condensed call, call processing
resumes. The CC decides what action to take, based on the following
factors:
— the message received.
— the information saved when the call was condensed.
3 Translate the digits:
a. The CC analyzes the digit translation data to determine the call
destination, based on the digits received and the originator’s
attributes.
b. The result of translation is a list of all the possible routes for the call.
c. Depending on the numbering plan used, translation may begin before
all the digits are received, with intermediate results saved when the
call is condensed. The CC may send messages to the PM telling it
how many more digits to collect, based on the intermediate results of
translation.

PLN-5001-001i Standard 02.02 April 1997

 Call processing 5–33

4 Select a terminating agent. For each route in the route list, the CC does
the following:
a. If the route is a trunk group:
i. selects an idle trunk from a queue of idle trunks in the trunk
group. The order in which idle trunks are selected depends on
the trunk group type.
ii. if there are no idle trunks in the group, proceeds to the next route
in the list. This is called “alternate routing”.
If the end of the route list is reached before an available route is
found, the call cannot be completed. Calls that cannot be
completed are routed to treatments, which may consist of tones or
announcements indicating the reason that the call could not be
completed. If no routes are available, the originating agent
receives “no circuit treatment”. This treatment is specified in the
office datafill, and usually consists of reorder tone followed by
lockout.
If a route is found, the CC proceeds to the step (establish the
telephony connection).
b. If the route is a line (call terminating in the same office):
i. examines the dynamic data on the state of the line to determine if
it is idle.
ii. if the line is idle, proceeds to step 5 (establish the telephony
connection).
iii. if the line is busy, sends a message to the originating PM
directing it to give busy tone to the originating agent.
5 Establish the telephony connection. A telephony connection is
established through the NMs as follows:
a. The CC selects a network path for the call.
b. The CC sends messages to the NMs and PMs, directing them to
connect the network path.
c. The messages sent by the CC to the PMs also inform them of the
integrity value to be transmitted and received in the CSM, and direct
them to look for integrity.
d. After integrity is found, the PMs connect both agents to the speech
path, if the terminator is not a line. If the terminator is a line, both
agents are connected to the speech path after the terminator answers.
The messages sent to the PMs also direct them to supervise the
connection after integrity is found. The PMs supervise the
connection by:
– continuously checking integrity.
– scanning for an answer signal from the terminator.

DMS-100 International Technical Specification BCS40i and up

5–34 Call processing

– scanning for disconnect signals from both agents.

6 Signal the terminating agent:
— If the terminating agent is a line, the CC sends a message to the
originating PM, directing it to give audible ringback tone to the
originating agent.
— If the terminating agent is a line, the CC sends a message to the
terminating PM, directing it to apply physical ringing to the
terminating line.
— If the terminating agent is a trunk, the CC sends a message to the
terminating PM, directing it to seize the trunk and out-pulse the
digits and any required signaling information. The CC condenses the
call until an answer or disconnect message is received.
7 Detect answer:
a. If the call is answered, the following steps occur:
i. The terminating PM detects an answer signal from the
terminator, and then changes the SV bit in the CSM to indicate to
the originating PM that the terminator has answered.
ii. If the terminator is a line, the PMs connect both agents to the
speech path.
iii. Metering starts. Meter pulses are generated by the originating
office. The tariff to be applied to the call is determined. Tariff
determination is primarily dependent on the source and
destination of a call and the network through which the call is
placed. In addition, tariffs may change according to the time of
day and the type of day. The charge corresponding to a meter
pulse is determined by operating company administration. Meter
pulses may also be transmitted over the subscriber lines to
increment subscriber premises meters (SPMs).
The answer time and disconnect time may be required for toll call
recording. This may be determined by either the originating PM
or the CC, depending on the type of call.
b. If the call is not answered, no metering is required.
c. The CC condenses the call until a disconnect message is received.
8 Detect disconnect:
a. When one of the agents involved in the call disconnects, the PM
sends a disconnect message to the CC and changes the SV bit in the
CSM to indicate to the other PM that the agent has disconnected.
b. If the connection was made through the NMs, the CC marks the
network path idle in the CC network connection map. The
connection remains intact until any of its components are re-assigned
to another connection.

PLN-5001-001i Standard 02.02 April 1997

 Call processing 5–35

The CC marks the disconnecting agent idle. If the disconnecting

agent is a line, the CC sends a message to the PM, directing it to idle
the line. If the disconnecting agent is a trunk, the PM idles the trunk
automatically.
c. If the remaining agent is a line, the CC sends a message to the PM,
directing it to report a disconnect within ten seconds. If the line has
not gone on-hook by that time, it is given disconnect treatment. If
the line goes on hook within ten seconds, the CC marks the line idle
and sends a message to the PM, directing it to idle the line.
If the remaining agent is not a line, the CC does not wait for a
disconnect signal from the remaining agent. When the first agent
disconnects, the CC marks both agents idle.
d. Metering stops. The software meter of the originating subscriber is
incremented by the number of accumulated meter pulses for this call
(intermediate updates may be necessary during the call depending on
the tariff).

DMS-100 International Technical Specification BCS40i and up

 6–1

Interfaces and signaling

This chapter summarizes the signaling capabilities provided on the generic
DMS-100 International switching system. Signaling specifications and
capabilities vary depending on the market in which the system is deployed,
the application of the system, and the hardware and software provisioned.

Interfaces
Interconnections with the outside world on DMS-100 International switches
are made using analog, digital, or a combination of analog and digital
interfaces.
• Analog interfaces (Z interfaces) are used to interface subscriber
telephone equipment. These are the line circuits and reside in the
International line concentrating module (ILCM) shelves at the host
office.
• Digital interfaces (A interfaces) provide direct access to the digital
system or equipment at the PCM-30 rate (2.048 Mb/s). These interfaces
reside in the International digital trunk controller (IDTC) shelves.
Line and trunk interfaces communicate with the DMS-100 switching
network using multiplex loops operating at 2.56 Mb/s.
Note : The DMS-100 International switch only supports direct PCM-30
trunk connections. Channel banks must be used to connect analog trunks.

Interface circuit functionalities

The following characteristics apply to interface circuits on DMS-100
International switches:
• control: supervision and signaling functions are under firmware control.
• tones: required signaling tones are generated digitally and internally.
• reliability: automatic switch-over takes place between network planes in
the event of a network plane failure.
• maintenance aid: digital and analog loop back features are provided to
facilitate maintenance.
• isolation: trunk circuits are transformer coupled to transmission
facilities for isolation and impedance matching.

DMS-100 International Technical Specification BCS40i and up

6–2 Interfaces and signaling

• insulation resistance: minimum 30, 000 ohms (trunk interfaces),

minimum 10, 000 ohms (line circuits)
• ground potential variation: ±3 volts

Interface circuitry protective characteristics

Low-frequency (50 Hz & 60 Hz) AC induction
Steady state: Line circuits on DMS-100 International switches are capable
of maintaining normal service while dissipating 40 mA for both conductors.
For currents between 40 mA and 350 mA, the DMS-100 International switch
creates neither a fire hazard nor an electrical shock hazard, although the
circuit may fail.
Longitudinal or metallic transients: The DMS-100 International switch is
capable of withstanding 600 Vrms for 5 s without creating either a fire
hazard or an electrical shock hazard (that is, the equipment may fail but only
in a safe manner). In addition, circuits on DMS-100 International switches
can withstand 480 Vrms for 183 ms and automatically restore.
High-voltage surges
Line circuits on DMS-100 International line cards can withstand, without
damage, a standard lightning surge wave form of 1000 V peak, 10 µs rise
time & 1000 µs decay time. The surge waveshape is illustrated in figure
6–1.

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–3

Figure 6–1xxx
Surge waveshape

1000 V Amplitude

500 V
Decay time to 1/2 value

Rise time

X Time in µs Y
0 < X < 10 – 100 µs 0 < Y z 100 – 1000 µs

Surge waveshape is defined as follows: Rise time X time to decay to half crest value.
For example: 10 X 1000 µs

Dielectric strength
1000 V DC, applied for 1 minute to tip (A-lead), ring (B-lead), and ground
terminals, in any combination, shall not result in damage.
The typical outside plant protection used with DMS-100 International
switches is 3-Mil carbon block (350 V) for over-voltage and heat coils (150
mA, must not operate within 2 minutes at 250 mA, and must operate within
10 seconds at 350 mA). These devices are provided by the operating
company.
Overvoltage protection
Overvoltage conditions are detected by the World Line Cards (type A –
NT6X17BA and type B – NT6X18BA) when any of the following
conditions are met:
• the voltage at TIP (A-lead) equals or exceeds +75.0 volts ± 4.0 volts
with respect to ground at any time during a 30 ms interval
• the voltage at TIP (A-lead) is equal to or less than –75.0 volts ± 4.0 volts
with respect to ground at any time during a 30 ms interval
• the voltage at RING (B-lead) equals or exceeds +75.0 volts ± 4.0 volts
with respect to ground at any time during a 30 ms interval

DMS-100 International Technical Specification BCS40i and up

6–4 Interfaces and signaling

• the voltage at RING (B-lead) is equal to or less than –75.0 volts ± 4.0
volts with respect to ground at any time during a 30 ms interval.
World line card characteristics are described in further detail on page 6–74.

Trunk interfaces
DMS-100 International switches can be directly connected to digital trunks,
using a PCM-30 digital carrier system (CCITT type A interface). Analog
trunks can also be connected via an appropriate channel bank.
International digital trunk controller
The International digital trunk controller (IDTC) interfaces sixteen
32-channel 2.048 Mb/s PCM-30 carrier systems with sixteen 32-channel (30
voice, 2 signaling and control), 2.56 Mb/s duplicated speech links (ports) to
the DMS-100 International digital network. An IDTC is a dual-shelf
peripheral with each shelf consisting of a maximum of 20 printed circuit
packs.
Packaging and power
A fully equipped IDTC consists of two shelves with common equipment that
provide for hot standby operation in the event of failure of common control
of one of the shelves. Each shelf contains 15 common control and switching
network interface circuit cards, one power converter card, and four PCM-30
interface cards. Each PCM-30 interface card accommodates two PCM-30
spans. In order to interface to the DMS-100 International switching
network, each shelf contains two interface cards, each of which provides
eight ports to the network. Each port is duplicated into planes 0 and 1 of the
switching network. Each incoming DS-1 channel is mapped to a network
port.
In addition, a third universal tone receiver (UTR) card – NT6X92CB – may
be added on an IDTC+ frame to provide an additional 30 receiver channels.
PCM-30 interface specifications
Output specifications (see also CCITT yellow book rec. G703.6.2.)
• line rate: 2.048 Mb/s phase-locked to office clock
• line code: high density bipolar (HDB3) code
• line impedance: 75 ohm resistive coaxial or 120 ohm resistive
symmetrical pair (switchable)
• pulse characteristics:
— termination:
75 ohm resistive (coaxial),
120 ohm resistive (symmetrical pair)

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–5

— nominal peak voltage of a mark (pulse):

2.37 v ± 10%
3.0 v ± 10%
— unbalanced in height of negative and positive pulse: 5%
— half amplitude width: 224 ± 25 ns
Input specifications (see also CCITT red book rec. g703): Each of the 30
voice frequency time slots on a PCM-30 carrier is associated with a
particular trunk on the channel bank.
Port mapping: The peripheral ports of the IDTC are provided as 16 PCM-30
ports with mapping to DS30 network ports. Mapping is arranged so that
when all peripheral ports are provisioned, all channels on all network ports
are used. When not fully provisioned with PCM-30 interfaces, the mapping
allows for an even spread of PCM-30 traffic over the available network ports
within the 120-channel group.
Control interface specification
When channel associated signaling is used, changes in A, B, C and D bits
incoming from the signaling channels (channel 16) of the incoming PCM-30
trunks into an IDTC are converted into messages in the DS30 link. These
messages contain the trunk address and the status of the associated A, B, C
and D bits.
Framing
The maximum average reframe time is less than 4 ms (this is the average
time to reframe when the maximum number of bit positions must be
examined for the framing pattern).
Idle channel transmission
For each idle channel, the IDTC transmits a bit pattern in accordance to
CCITT recommendations. Two patterns are available on a datafill basis.
• CCITT Q.503 (paragraph 3.6)
• CCITT Q.714 (paragraph 16.1)

Delay: The transmission delay caused by the buffering of bytes in the IDTC
will not be more than three frames (375 microseconds). The average delay
will not be more than two frames (250 microseconds).

Digital trunk signaling

The DMS-100 International switch accommodates a variety of digital trunk
switching protocols, which consist of line signaling and register signaling
elements. Line signaling refers to the signals sent between two offices
connected to a trunk to control trunk usage, call setup, and takedown.
Register signaling refers to signals carrying information such as the called

DMS-100 International Technical Specification BCS40i and up

6–6 Interfaces and signaling

number digits, the calling number digits, the type of call, and information
about the status of the terminating subscriber.
Trunk signaling timing parameters
Signaling timing parameters are specified as part of the line and register
signaling system definitions in tables LNSIGSYS, RGSIGSYS, DGHEAD
and DGCODE. Each parameter consists of a default value, a minimum and
maximum limit, and an incremental value. The default values will satisfy
most requirements. These can, however, be changed by operating company
administration, within prescribed limits. Refer to DMS-100 International
Customer Data Schema, 297-1001–451i, for detailed specifications of
variable timing parameters.

Register signaling variants

Register signaling protocols supported on the DMS-100 International switch
are based on CCITT recommendations, country-specific systems, or hybrids
of CCITT and country-specific systems. CCITT R2 variants are based on
the signaling specifications outlined in CCITT recommendations Q.400 to
Q.458, and Q.460 to Q.490.
The register signaling types supported on the DMS-100 International switch
are described in table 6–1 on page 6–6. The register signaling variables
can be assigned on a trunk subgroup or line attribute basis in table
RGSIGSYS, which contains all the relevant customer-variable register
signaling data. For additional detail on the various R2 signaling variants
available, refer to Customer Data Schema, 297–1001–451i.

Table 6–1xxx
Register signaling types
Abbreviation Register signaling type

MF3 R1 – three-phase multifrequency (MF) pulse signaling

system based on CCITT recommendations Q.310, Q.320,
and Q.332.

Digit collection by the incoming register, after receipt of the

KP signal, is separated into phases, followed by the
end-of-pulsing (ST) signal.
MFCR2 (MF compelled [MFC] R2 signaling
(Used by DMS-300 switching units.)

NTRS02 Multifrequency (MF) shuttle

—continued—

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–7

Table 6–1xxx
Register signaling types (continued)
Abbreviation Register signaling type

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.
NTRS04 R1 modified signaling system using a combination of R1
register signaling based on CCITT recommendations Q.310,
Q.320, and Q.332, and CCITT number 5 register signals (KP,
KP2, Code11, and Code12.
NTRS05 E and M (decadic) 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 – implements multiple register
signaling system capabilities on the same trunk. In the CIS
network, RGHYBRID combines MF shuttle (NTRS02),
decadic (NTRS05) and automatic number identification (ANI)
register signaling capabilities.

End

Programmable R2 register signaling

The DMS-100 International switch uses a programmable R2 register
signaling system which allows definition and assignment of market-specific
R2 protocols to the appropriate trunk groups, using datafill. Up to 15
protocols can be defined on each exchange, and up to 16 signaling phases
can be defined per protocol.
The initial programming for each market-specific R2 variant is performed
by Northern Telecom engineering personnel, based on data supplied by the

DMS-100 International Technical Specification BCS40i and up

6–8 Interfaces and signaling

operating company, as defined in the appropriate Customer Specification or

Technical Requirements Specification. Operating company personnel can
also use the programmable R2 system after switch installation to alter R2
protocol specifications using the table editor system, assuming the changes
are technically supported and valid. Protocol specifications which can be
programmed include signal-to-activity mapping, activity-to-signal mapping,
and signaling phase change. The R2 signaling activities currently supported
by the DMS-100 International switch are outlined on page 6–8.
Programmable R2 data tables
The programmable R2 system uses the following data tables to define and
implement R2 protocols:
• ACTCTL defines the R2 activities for a protocol
• ACTSIG maps R2 activities to signals
• SIGACT maps signals to R2 activities
• CATCLASS specifies the category of an activity (billing, calling, or
both)
• R2PROT ties tables ACTCTL, ACTSIG, SIGACT and CATCLASS
together to define the protocol
• TRTMTACT maps treatments to activities
• ACTTRTMT maps activities to treatments
• TRKGRP defines parameters for trunk groups
For additional details on table control for the programmable R2 system, refer
to Customer Data Schema, 297–1001–451i.
R2 protocol verification
The programmable R2 system includes a online verification tool which
allows display of all parameters associated with a protocol, and automatic
verification of the protocol as defined in the associated data tables. The
verification is performed using the CI level MAP command R2VER. For
information on using this command, refer to the Non-menu commands
manual, 297-1001–820.

Generic R2 register signaling activities

This section describes the R2 signaling activities currently supported on the
DMS-100 International switch. The actual activity set used, the
activity-to-signal and signal-to-activity mapping, and phase changes
associated with a particular R2 protocol are market-dependent and are
defined using the programmable R2 system as described on page 6–7.
Individual customer requirements for implementation of additional R2
activities, customization of currently supported activities, or special handling
requirements for non-supported activities are addressed on an individual

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–9

basis by Northern Telecom Systems Engineering, in consultation with the

customer.
The descriptions of the generic R2 register signaling activities are
subdivided by signaling phase and category, as follows:
• numeric address information – see page 6–9
• address control – see page 6–12
• calling party category – see page 6–20
• automatic number identification (ANI) phase – see page 6–28
• called party status – see page 6–37
• special activities – see page 6–50

R2 generic numeric address information activities

The activities described in table 6–2 are used to indicate the digits of the
calling and called numbers, and other associated activities.

Table 6–2xxx
Generic R2 register signaling – numeric address information activities

Activity Meaning Explanation

DIGIT_0 digit 0 These activities represent digits 0

through
h h 9 during
d i transmission
i i and d
DIGIT_1 digit 1 reception
rece tion of called and calling
DIGIT_2 digit 2 number.

DIGIT_3 digit 3
DIGIT_4 digit 4
DIGIT_5 digit 5
DIGIT_6 digit 6
DIGIT_7 digit 7
DIGIT_8 digit 8
DIGIT_9 digit 9
DIGIT_B digit 11 These activities represent
overdecadic
d di didigits
i (di
(digits
i 11 through
h h
DIGIT_C digit 12 15) during transmission and
DIGIT_D digit 13 reception of the called and calling
number
number.
DIGIT_E digit 14
DIGIT_F digit 15
—continued—

DMS-100 International Technical Specification BCS40i and up

6–10 Interfaces and signaling

Table 6–2xxx
Generic R2 register signaling – numeric address information activities
(continued)

Activity Meaning Explanation

END_OF_DIGS pulsing/identification This activity indicates that address

complete information is complete, no more
digits to follow.
REQ_NOT_ACC request not This activity is sent by the originating
accepted exchange when it is unable to
transmit required information as
requested by the terminating
exchange. This may occur if
automatic number identification (ANI)
fails.

As an originating exchange, DMS

sends this activity if calling digits are
requested but not available.

As a tandem exchange, DMS

propagates REQ_NOT_ACC to the
next exchange.

As a terminating exchange, DMS

responds to receiving
REQ_NOT_ACC by routing the call
normally, routing it to ITOPS, or
sending CONGESTION to the
previous exchange, as specified by
office parameter
ICAMA_ANI_FAILURE_ACTION in
table OFCVAR.
—continued—

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–11

Table 6–2xxx
Generic R2 register signaling – numeric address information activities
(continued)

Activity Meaning Explanation

ACC_MTC access to test This activity is a test call indicator

equipment and is used primarily for access to
test equipment.

As an originating exchange, DMS

does not generate this signal. DMS
indicates maintenance calls using
activity MTC_EQ.

As a tandem exchange, DMS

propagates ACC_MTC to the next
exchange.

As a terminating exchange, DMS

sends this signal as a digit and
enters it in the digit register.
Translations are used to route the
call to the appropriate test
equipment.
PR1_RADIO priority 1 call, needs This activity indicates a call initiated
radio circuits by a priority 1 subscriber requiring
superior cable circuits.

As an originating exchange, DMS

does not generate this signal.

As a tandem exchange, DMS

propagates PR1_RADIO to the next
exchange.

As a terminating exchange, DMS

treats a PR1_RADIO call as a
regular subscriber call.
—continued—

DMS-100 International Technical Specification BCS40i and up

6–12 Interfaces and signaling

Table 6–2xxx
Generic R2 register signaling – numeric address information activities
(continued)

Activity Meaning Explanation

PR2_CABLE priority 2 call, needs This activity indicates a call initiated

cable circuits by a priority 2 subscriber requiring
superior cable circuits.

As an originating exchange, DMS

does not generate this signal.

As a tandem exchange, DMS

propagates PR2_RADIO to the next
exchange.

As a terminating exchange, DMS

treats a PR2_RADIO call as a
regular subscriber call.
ZSUB_CALL Z subscriber call This activity is a connection control
signal indicating a public facsimile or
intermediate speed data call.

As an originating exchange, DMS

sends this activity when an ITOPS
call is made.

As a tandem exchange, DMS

ignores this activity and does not
propagate it to the next exchange.

As a terminating exchange, DMS

takes no special action after
receiving ZSUB_CALL.
End

R2 generic address control activities

The activities listed in table 6–3 describe the forward signals used to
transmit call setup information These activities acknowledge the numeric
address information activities and indicate to the forward register which
information to send next.

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–13

Table 6–3xxx
Generic R2 register signaling – address control activities
Activity Meaning Explanation

NEXT_DIGIT next digit This activity indicates to the forward

register to send the next digit of the
called number (or calling number for
ANI).

As an originating exchange, DMS

sends the next digit on receipt of this
signal. If all digits are sent, DMS
sends END_OF_DIGITS, or allows
the interdigit timer to expire,
depending on the protocol.

As a tandem exchange, DMS acts as

a terminating exchange, transmitting
NEXT_DIGIT until it has collected
the required digits. The exchange
may perform end-to-end or
link-by-link signaling.

As a terminating exchange, DMS

sends NEXT_DIGIT when it requires
more digits of the called number for
routing, if digit analysis is being
used. If digit analysis is not being
used, DMS sends NEXT_DIGIT until
it receives END_OF_DIGITS or the
interdigit timer expires.
—continued—

DMS-100 International Technical Specification BCS40i and up

6–14 Interfaces and signaling

Table 6–3xxx
Generic R2 register signaling – address control activities(continued)
Activity Meaning Explanation

NEXT_ANI_DIGIT next automatic This activity is sent to the preceding

number identification exchange to request the next digit.
(ANI) digit of the calling number for ANI.

As an originating exchange, DMS

sends the next digit of the calling
number on receipt of this signal. If
all digits have been sent, DMS sends
END_OF_DIGITS, or allows the
interdigit timer to expire, depending
on the protocol.

As a terminating exchange, DMS

sends NEXT_ANI_DIGIT until it
receives END_OF_DIGITS, or the
interdigit timer expires, depending on
the protocol.
LAST_DIGIT last digit This activity indicates that the
originating exchange should resend
the last digit of the called number.

As an originating exchange, DMS

resends the last digit of the called
number sent on receipt of this
activity.

As a tandem exchange, DMS

connects PCM in the tandem office
and completes signaling in
end-to-end mode. If signaling is in
the ANI phase, LAST_DIGIT is
propagated to the previous
exchange. If signaling is in the
called digits phase, LAST_DIGIT is
not propagated.

As a terminating exchange, DMS

sends this activity only during the
ANI digits phase.
—continued—

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–15

Table 6–3xxx
Generic R2 register signaling – address control activities(continued)
Activity Meaning Explanation

FIRST_DIGIT first digit This activity requests that the first

digit be resent.

As an originating exchange, DMS

resends the first digit on receipt of
this activity.

As a tandem exchange, DMS sends

this activity as last acknowledgement
to the numerical address information
activity just received, when it has
determined it will complete register
signaling in end-to-end mode.

As a terminating exchange, DMS

does not send this activity.
LAST_BUT_1 last-but-one digit This activity is a request to resend
the last-but-one digit (n - 1)

As an originating exchange, DMS

resends the last-but-one digit of the
called number on receipt of this
activity.

As a tandem exchange, DMS sends

this activity as last acknowledgement
to the numerical address information
activity just received, when it has
determined it will complete register
signaling in end-to-end mode.

As a terminating exchange, DMS

does not send this activity.
—continued—

DMS-100 International Technical Specification BCS40i and up

6–16 Interfaces and signaling

Table 6–3xxx
Generic R2 register signaling – address control activities(continued)
Activity Meaning Explanation

LAST_BUT_2 last-but-two digit This activity is a request to resend

the last-but-two digit (n - 2).

As an originating exchange, DMS

resends the last-but-two digit of the
called number on receipt of this
activity.

As a tandem exchange, DMS sends

this activity as last acknowledgement
to the numerical address information
activity just received, when it has
determined it will complete register
signaling in end-to-end mode.

As a terminating exchange, DMS

does not send this activity.
LAST_BUT_3 last-but-three digit This activity is a request to resend
the last-but-three digit (n - 3).

As an originating exchange, DMS

resends the last-but-three digit of the
called number on receipt of this
activity.

As a tandem exchange, DMS sends

this activity as last acknowledgement
to the numerical address information
activity just received, when it has
determined it will complete register
signaling in end-to-end mode.

As a terminating exchange, DMS

does not send this activity.
—continued—

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–17

Table 6–3xxx
Generic R2 register signaling – address control activities(continued)
Activity Meaning Explanation

REQ_CAT request category This activity requests the incoming

trunk to collect the called
subscriber’s category.

As an originating exchange, DMS

sends the calling subscriber category
on receipt of this activity.

As a tandem exchange in link-by-link

mode, DMS propagates this activity
to the previous exchange.

As a terminating exchange, DMS

transmits this activity on receipt of
the called number (and the calling
number where ANI digits are
required).
—continued—

DMS-100 International Technical Specification BCS40i and up

6–18 Interfaces and signaling

Table 6–3xxx
Generic R2 register signaling – address control activities(continued)
Activity Meaning Explanation

REQ_DN_CAT send calling number This activity is used for billing or

and ID phase malicious call trace (MCT) purposes.
category
Billing:

As an originating exchange, DMS

sends the ID phase category on
receipt of this activity. The calling
number is then sent if the outgoing
trunk class is CAMA or TNCA, or if
office parm R2_ANI_DENY is set to
N.

As a tandem exchange, DMS sends

this activity to the previous
exchange, then receives the calling
number if all the following conditions
are met: (a) the digits identify the
outgoing route (b) the incoming trunk
class is CAMA or TNCA (c) the call is
not a test call, and (d) the translation
class is one of the following:
NATL (national),
CNTL (continental),
ICNTL (intercontinental)
INTL (international)
IOPRA (international operator
assisted, or
OPRA (operator assisted).

As a terminating exchange, DMS

sends this activity to the previous
exchange if all the following
conditions are met: (a) all called
digits have been collected (b) the
incoming trunk class is CAMA or
TNCA (c) the call is not a test call,
and (d) the translation class is one of
the following:
NATL (national),
CNTL (continental),
ICNTL (intercontinental)
INTL (international)
IOPRA (international operator
assisted, or
OPRA (operator assisted).
—continued—

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–19

Table 6–3xxx
Generic R2 register signaling – address control activities(continued)
Activity Meaning Explanation

REQ_DN_CAT send calling number Activity used for billing or malicious

(continued) and id phase call trace (MCT) purposes.
category
Malicious call trace (MCT):

As an originating exchange, DMS

sends the ID phase category on
receipt of this activity. The calling
number is then sent if office
parameter R2_ANI_DENY is set to
N.

As a tandem exchange, DMS sends

this activity if the calling digits are
available and office parameter
R2_ANI_DENY is set to N. DMS
propagates this activity to the
previous exchange if all the following
conditions are met: (a) office parm
R2_ANI_DENY is set to N. (b) the
calling digits are not available, and
(c) the MCTANI field of the incoming
trunk group’s data is set to Y. DMS
sends the ID phase category and an
indication that the request for calling
digits is denied if either of the
following conditions apply: (a) office
parm R2_ANI_DENY is set to Y, or
(b) the calling digits are unavailable
and the MCTANI field of the
incoming trunk group’s data is set to
N.

As a terminating exchange, DMS

sends this activity to the previous
exchange if all the following
conditions are met: (a) the calling
digits are not already available (b)
the MCTANI field of the incoming
trunk group’s data is set to Y, and the
call terminates on a line with the
MCT option.
End

DMS-100 International Technical Specification BCS40i and up

6–20 Interfaces and signaling

R2 generic calling party category activities

The activities listed in table 6–4 describe the type of call or its origin.

Table 6–4xxx
Generic R2 register signaling – calling party category activities
Activity Meaning Explanation

REGULAR regular subscriber This activity indicates that the

without priority originator is a regular subscriber
without priority, or that the
originator’s category is unknown.

As an originating exchange, DMS

sends REGULAR as the calling party
if the originator is an ordinary POTS
line, or as the default calling category
if the protocol does not support
calling party category identification.

As a tandem exchange, DMS

propagates REGULAR to the next
exchange.

As a terminating exchange, DMS

recognizes the originator as a normal
subscriber on receipt of REGULAR
and applies the normal restrictions
on the call.
PRIORITY Priority subscriber This activity indicates a call initiated
by a priority subscriber. A priority
subscriber is indicated as such by
adding line option PR1 or PR2 to the
subscriber’s line.

As an originating exchange, DMS

sends PR_SUB if the originating
subscriber line is datafilled with line
option PR1 or PR2.

As a tandem exchange in link-by-link

mode, DMS propagates PRIORITY
as the calling category when this
activity is received.

As a terminating exchange, DMS

treats a call with calling party
category of PRIORITY as a regular
call.
—continued—

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–21

Table 6–4xxx
Generic R2 register signaling – calling party category activities (continued)
Activity Meaning Explanation

MTC_EQ Maintenance This activity indicates that the call

equipment originates on maintenance
equipment, such as the trunk test
position on the MAP.

As an originating exchange, DMS

handles test calls and regular calls
identically, except billing is
suppressed and MTC_EQ is sent as
the calling category.

As a tandem exchange in link-by-link

mode, DMS propagates MTC_EQ to
the next exchange.

As a terminating exchange, DMS

handles MTC_EQ calls as regular
calls, and accepts them without ANI
digits. If a call terminates on
maintenance equipment, DMS sends
back “Subscriber Line Free, Charge”
as the called party status.
COIN coin phone call COIN designates the calling party
category as a coin phone.

As an originating exchange, DMS

sends COIN as the calling category if
the originator’s LCC is set to COIN.

As a tandem exchange in link-by-link

mode, COIN is propagated to the
succeeding exchange.

As a terminating exchange, DMS

treats coin-originated calls as regular
calls.
—continued—

DMS-100 International Technical Specification BCS40i and up

6–22 Interfaces and signaling

Table 6–4xxx
Generic R2 register signaling – calling party category activities (continued)
Activity Meaning Explanation

OPER operator This activity indicates that the call

has been set up by an operator.

As an originating exchange, DMS

sends OPER as the calling category
for calls originating from an
International Traffic Operator
Position System (ITOPS) position.

As a tandem exchange, DMS

propagates this activity for R2-R2
calls in link-by-link mode. On
incoming calls from OPR trunks,
DMS sends OPR as the calling
category.

As a terminating exchange, DMS

applies busy treatment locally if the
called subscriber is busy, and retains
the connection while it is being
applied, allowing transmission of line
signaling such as toll break-in (TBI).
UNIT_FEE_COIN unit fee coin phone This activity indicates that the call is
initiated at a coin phone using the
“unit fee” mode of operation.

As an originating exchange, DMS

does not generate this signal.

As a tandem exchange in link-by-link

mode, UNIT_FEE_COIN is
propagated to the next exchange.

As a terminating exchange, DMS

treats calls with calling party
category UNIT_FEE_COIN as
regular calls.
—continued—

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–23

Table 6–4xxx
Generic R2 register signaling – calling party category activities (continued)
Activity Meaning Explanation

DATA data This activity indicates that the call is

being used for data transmission, to
prevent possible data corruption by
multiple connections or break-in
tones.

As an originating exchange, DMS

sends DATA as the calling category if
the line has feature No Double
Connect, and it is activated.

As a tandem exchange, DMS

propagates the calling party category
of DATA to the next exchange.

As a terminating exchange, DMS

disallows all double connect attempts
to calls with calling party category of
DATA.
NO_CALL_TRANS no call transfer This activity indicates that the call
should not be subject to any form of
call transfer at the terminating
exchange.

As an originating exchange, DMS

does not generate this activity.

As a tandem exchange, DMS

propagates NO_CALL_TRANS to
the next exchange.

As a terminating exchange, DMS

does not allow incoming calls with
category NO_CALL_TRANS to be
transferred.
—continued—

DMS-100 International Technical Specification BCS40i and up

6–24 Interfaces and signaling

Table 6–4xxx
Generic R2 register signaling – calling party category activities (continued)
Activity Meaning Explanation

OPER_ACK semi-automatic This activity indicates semi-automatic

verification of calling verification of a calling number by an
number by operator operator.

As an originating exchange, DMS

does not generate this activity.

As a tandem exchange in link-by-link

mode, DMS propagates OPER_ACK
to the next exchange.

As a terminating exchange, DMS

does not respond to this activity.
REGULAR_INTL International direct This activity specifies that the
dialed call originator is making an International
direct dialed call.

As an originating exchange, DMS

sends REGULAR_INTL as the
calling party category if the
translation class associated with the
called number is either International
(INTL) or Intercontinental (ICNTL).

As a tandem exchange, DMS treats

REGULAR_INTL as follows:
– if the call is from R2 trunk to R2
trunk, REGULAR_INTL is
propagated to the next exchange.
– if the call is from an R2 trunk to a
non-R2 trunk, DMS takes no special
actions and treats the calling party as
a regular subscriber.
– if the call is from a non-R2 trunk to
an R2 trunk, DMS sends
REGULAR_INTL as the calling party
category if the translation class
associated with the called number is
either International (INTL) or
Intercontinental (ICNTL).
—continued—

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–25

Table 6–4xxx
Generic R2 register signaling – calling party category activities (continued)
Activity Meaning Explanation

ANI_FAILURE automatic number This activity indicates that the calling

identification (ANI) party number could not be
failure determined at the originating
exchange.

As an originating exchange, DMS

sends ANI_FAILURE if supported by
the protocol, and the originating line
is assigned the ONI option.

As a tandem exchange, DMS

propagates this activity to the next
exchange.

As a terminating exchange, DMS

treats calls with category
ANI_FAILURE as regular calls.
ATME automatic This activity indicates that the call
transmission originated on ATME.
measurement
equipment (ATME) As an originating exchange, DMS
does not generate this activity.

As a tandem exchange in link-by-link

mode, DMS propagates this activity
to the next exchange.

As a terminating exchange, DMS

handles an ATME call as a regular
call, except that the lack of ANI digits
does not cause the call to fail.
SHARED_1 first subscriber on This activity indicates that the calling
party line party is the first subscriber on a party
line.

As an originating exchange, DMS

does not generate this activity.

As a tandem exchange in link-by-link

mode, DMS propagates this activity
to the next exchange.

As a terminating exchange, DMS

treats SHARED_1 calls as regular
calls.
—continued—

DMS-100 International Technical Specification BCS40i and up

6–26 Interfaces and signaling

Table 6–4xxx
Generic R2 register signaling – calling party category activities (continued)
Activity Meaning Explanation

SHARED_2 second subscriber This activity indicates that the calling

on party line party is the second subscriber on a
party line.

As an originating exchange, DMS

does not generate this activity.

As a tandem exchange in link-by-link

mode, DMS propagates this activity
to the next exchange.

As a terminating exchange, DMS

treats SHARED_2 calls as regular
calls.
SHARED_3 third subscriber on This activity indicates that the calling
party line party is the third subscriber on a
party line.

As an originating exchange, DMS

does not generate this activity.

As a tandem exchange in link-by-link

mode, DMS propagates this activity
to the next exchange.

As a terminating exchange, DMS

treats SHARED_3 calls as regular
calls.
OPER_INTL International This activity identifies the calling
operator party as an International operator.

As an originating exchange, DMS

does not generate this activity.

As a tandem exchange, DMS

propagates this activity to the next
exchange.

As a terminating exchange, DMS

treats OPER_INTL calls as regular
calls.
—continued—

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–27

Table 6–4xxx
Generic R2 register signaling – calling party category activities (continued)
Activity Meaning Explanation

SPARE_CAT1, spare categories These activities are used to

SPARE_CAT2 represent calling party categories not
provided by the generic activity set.

As an originating exchange, DMS

does not generate these activities.

As a tandem exchange, DMS

propagates SPARE_CAT_1 or
SPARE_CAT_2 to the next
exchange, if valid on the outgoing
trunk. If not valid, REGULAR is
transmitted as the calling party
category.

As a terminating exchange, DMS

treats calls using spare categories as
regular calls.
TOLL_AUTO automatic toll call This activity indicates that the call is
a direct-dialed toll call originated
without requirement for operator
assistance.

As an originating exchange, DMS

sends TOLL_AUTO when the
translation class is a toll class.

As a tandem exchange, DMS

propagates TOLL_AUTO to the next
exchange.

As a terminating exchange, DMS

does not handle this signal.
End

DMS-100 International Technical Specification BCS40i and up

6–28 Interfaces and signaling

Generic R2 automatic number identification activities

The activities listed in table 6–5 convey identification information required
during the automatic number identification phase, such as the billing
category

Table 6–5xxx
Generic R2 register signaling – ANI ID phase category activities
Activity Meaning Explanation

REGULAR regular subscriber See activity REGULAR on page

without priority 6–20.
ORD_FIXED ordinary This activity indicates that the
subscriber, fixed originator is an ordinary subscriber
period call without priority and has no charging
category (fixed period call is the
default charging category).

As an originating exchange, DMS

sends ORD_FIXED as the ANI ID
phase category if the originating line
has no priority line option and has no
charging category.

As a tandem exchange, DMS

propagates ORD_FIXED to the next
exchange.

As a terminating exchange, DMS

treats ORD_FIXED calls as regular
calls.
ORD_DEMAND ordinary This activity indicates that the
subscriber, originator is an ordinary subscriber
demand call without priority, and that the billing
category is a demand charging call.

As an originating exchange, DMS

sends ORD_DEMAND as the ANI ID
phase category if the originating line
has no priority option, has the HOT
line attribute, and is assigned feature
SCR (and the feature is active).

As a tandem exchange, DMS

propagates ORD_DEMAND to the
next exchange.

As a terminating exchange, DMS

treats ORD_DEMAND calls as
regular calls.
—continued—

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–29

Table 6–5xxx
Generic R2 register signaling – ANI ID phase category activities (continued)
Activity Meaning Explanation

ORD_HALL ordinary This activity indicates that the

subscriber, originator is an ordinary subscriber
service hall call without priority, and that the billing
category is a service hall charging
call.

As an originating exchange, DMS

sends ORD_HALL as the ANI ID
phase category if the originating line
has no priority option, and has the
attendant pay station (APS) line
option.

As a tandem exchange, DMS

propagates ORD_HALL to the next
exchange.

As a terminating exchange, DMS

treats ORD_HALL calls as regular
calls.
PRIORITY priority subscriber see activity PRIORITY on page 6–20
PR1_FIXED priority 1 This activity indicates that the call is
subscriber, fixed initiated by a priority 1 subscriber
period call with no charging category (fixed
period charging is the default).

As an originating exchange, DMS

sends PR1_FIXED as the ANI ID
phase category if the originating line
has the line option PR1 assigned,
and has no charging category.

As a tandem exchange, DMS

propagates PR1_FIXED to the next
exchange.

As a terminating exchange, DMS

treats calls identified as PR1_FIXED
as regular calls.
—continued—

DMS-100 International Technical Specification BCS40i and up

6–30 Interfaces and signaling

Table 6–5xxx
Generic R2 register signaling – ANI ID phase category activities (continued)
Activity Meaning Explanation

PR1_DEMAND priority 1 This activity indicates that the

subscriber, originator is a priority 1 subscriber ,
demand call and that the billing category is a
demand charging call.

As an originating exchange, DMS

sends PR1_DEMAND as the ANI ID
phase category if the originating line
has the PR1 and HOT line attributes,
and is assigned feature SCR (and
the feature is active).

As a tandem exchange, DMS

propagates PR1_DEMAND to the
next exchange.

As a terminating exchange, DMS

treats PR1_DEMAND calls as
regular calls.
PR1_HALL priority 1 This activity indicates that the
subscriber, originator is a priority 1 subscriber ,
service hall call and that the billing category is a
service hall charging call.

As an originating exchange, DMS

sends PR1_HALL as the ANI ID
phase category if the originating line
has options priority 1 (PR1) and
attendant pay station (APS) assigned
to it.

As a tandem exchange, DMS

propagates PR1_HALL to the next
exchange.

As a terminating exchange, DMS

treats PR1_HALL calls as regular
calls.
—continued—

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–31

Table 6–5xxx
Generic R2 register signaling – ANI ID phase category activities (continued)
Activity Meaning Explanation

PR2_FIXED priority 2 This activity indicates that the call is

subscriber, fixed initiated by a priority 2 subscriber
period call with no charging category (fixed
period charging is the default).

As an originating exchange, DMS

sends PR2_FIXED as the ANI ID
phase category if the originating line
has the line option PR2 assigned,
and has no charging category.

As a tandem exchange, DMS

propagates PR2_FIXED to the next
exchange.

As a terminating exchange, DMS

treats calls identified as PR2_FIXED
as regular calls.
PR1_FIXED_INTL priority 1 fixed This activity indicates that the call is
period call, initiated by a priority 1 subscriber
International with no charging category (fixed
period charging is the default), and
that an International access code
has been used.

As an originating exchange, DMS

sends PR1_FIXED_INTL as the ANI
ID phase category if the originating
line has the line option PR1
assigned, has no charging category,
and an International access code
has been used.

As a tandem exchange, DMS

propagates PR1_FIXED_INTL to the
next exchange.

As a terminating exchange, DMS

treats calls identified as
PR1_FIXED_INTL as regular calls.
—continued—

DMS-100 International Technical Specification BCS40i and up

6–32 Interfaces and signaling

Table 6–5xxx
Generic R2 register signaling – ANI ID phase category activities (continued)
Activity Meaning Explanation

PR1_DEMAND_INTL priority 1 demand This activity indicates that the

call, International originator is a priority 1 subscriber,
the billing category is a demand
charging call, and that an
International access code has been
used.

As an originating exchange, DMS

sends PR1_DEMAND_INTL as the
ANI ID phase category if the
originating line has the PR1 and
HOT line attributes, is assigned
feature SCR (and the feature is
active), and an International access
code is used.

As a tandem exchange, DMS

propagates PR1_DEMAND_INTL to
the next exchange.

As a terminating exchange, DMS

treats PR1_DEMAND_INTL calls as
regular calls.
PR1_HALL_INTL priority 1 service This activity indicates that the
hall call, originator is a priority 1 subscriber,
International the billing category is a service hall
charging call, and that an
International access code has been
used.

As an originating exchange, DMS

sends PR1_HALL_INTL as the ANI
ID phase category if the originating
line has options priority 1 (PR1) and
attendant pay station (APS) assigned
to it, and an International access
code has been used.

As a tandem exchange, DMS

propagates PR1_HALL_INTL to the
next exchange.

As a terminating exchange, DMS

treats PR1_HALL_INTL calls as
regular calls.
—continued—

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–33

Table 6–5xxx
Generic R2 register signaling – ANI ID phase category activities (continued)
Activity Meaning Explanation

MTC_EQ maintenance see activity MTC_EQ on page 6–21

equipment
COIN coin phone call see activity COIN on page 6–21
UNIT_FEE_COIN unit fee coin see activity UNIT_FEE_COIN on
phone page 6–22
OPER operator see activity OPER on page 6–22
DATA data see activity DATA on page 6–23
PBX call from a private This activity is used to identify the
branch exchange calling extension number of a call
(PBX) originated on a PBX.

As an originating exchange, DMS

recognizes PBX calls by presence of
options line reversal on answer
(LRA) or line reversal on seizure
(LRS) assigned to the line. PBX
calls are set up as normal calls, and
the PBX signal is not sent to the next
exchange for toll calls.

As a tandem or terminating
exchange, DMS does not receive
this signal.
NO_CALL_TRANS no call transfer see activity NO_CALL_TRANS on
page 6–23.
—continued—

DMS-100 International Technical Specification BCS40i and up

6–34 Interfaces and signaling

Table 6–5xxx
Generic R2 register signaling – ANI ID phase category activities (continued)
Activity Meaning Explanation

FREE_CALL free call This activity indicates that the call is

not to be billed. Charging for the call
is not started in the originating
exchange upon answer.

As an originating exchange, DMS

terminates register signaling,
connects PCM, waits for line
signaling to indicate that the call is
answered, and marks the call as
free.

As a tandem exchange in link-by-link

mode, DMS terminates register
signaling, connects PCM, waits for
line signaling to indicate that the call
is answered, and propagates the
answer signal to the preceding
exchange.

As a terminating exchange, DMS

sends CONNECT_CALL_NOCHG if
the called party is idle and has line
option FNT. Register signaling is
completed and ringing is applied to
the trunk. When the called party
answers, PCM is connected and the
answer signal is sent via line
signaling.
FREE_OR_FIXED free call or fixed see activity FREE_CALL on page
period call 6–34, and activity PR1_FIXED on
page 6–29
REGULAR_INTL International see activity REGULAR_INTL on
direct dialed call page 6–24
—continued—

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–35

Table 6–5xxx
Generic R2 register signaling – ANI ID phase category activities (continued)
Activity Meaning Explanation

ANI_FAILURE automatic number This activity indicates that the calling

identification (ANI) party number could not be
failure determined at the originating
exchange. DMS sends
ANI_FAILURE in response to
receiving activity REQ_DN_CAT. If
DMS receives a NEXT_ANI_DIGIT
signal after sending ANI_FAILURE, it
sends an END_OF_DIGS signal.

As an originating office, DMS sends

ANI_FAILURE if supported as a
billing category by the protocol, and
the line has option ONI.

As a tandem exchange, DMS

propagates ANI_FAILURE to the
next office.

As a terminating exchange, the DMS

response to ANI_FAILURE is
identical to the response to activity
REQ_NOT_ACC.
ATME automatic test see activity ATME on page 6–25
measurement
equipment
(ATME)
TIME_AND_CHG time and charge This activity describes the billing
category of the calling party and
indicates that the subscriber has
requested this service for the call.

As an originating exchange, DMS

does not generate this signal.

As a tandem exchange in link-by-link

mode, DMS propagates
TIME_AND_CHG to the next
exchange.

As a terminating exchange, DMS

treats a call with this billing category
as a regular call.
SHARED_1 first party on party see activity SHARED_1 on page
line 6–25
—continued—

DMS-100 International Technical Specification BCS40i and up

6–36 Interfaces and signaling

Table 6–5xxx
Generic R2 register signaling – ANI ID phase category activities (continued)
Activity Meaning Explanation

SHARED_2 second party on see activity SHARED_2 on page

party line 6–26
SHARED_3 third party on see activity SHARED_3 on page
party line 6–26
OPER_INTL International see activity OPER_INTL on page
operator 6–26
SPARE_CAT1 spare categories see activities SPARE_CAT1,
SPARE_CAT2 SPARE_CAT2 on page 6–27
End

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–37

Generic R2 called subscriber status activities

The activities listed in table 6–6 convey information about the condition of
the incoming exchange equipment or the called subscriber’s line.
Treatments to be applied if the subscriber is not free are sent to the
originating exchange using activities in this category.

Table 6–6xxx
Generic R2 register signaling – called subscriber status activities
Activity Meaning Explanation

CONGESTION congestion This activity indicates congestion of

national links (no route available) or
a timeout or abnormal release of the
R2 register.

As an originating exchange, DMS

accesses table TRTMTCAT to
determine the treatment to apply to
the originating line.

As a tandem exchange in link-by-link

mode, DMS responds to receiving
CONGESTION based on treatment
to activity mapping of the outgoing
and incoming trunks. DMS examines
the datafill of the outgoing trunk to
determine the treatment associated
with the CONGESTION activity.
DMS then determines if the
treatment maps to an activity in the
datafill for the incoming trunk,. If so,
it sends that activity to the originating
exchange. If not, treatment is
applied in the tandem exchange.

DMS also sends CONGESTION to

the originating exchange if there is
no outgoing trunk route available.

As a terminating exchange, DMS

sends CONGESTION as the called
subscriber status if a signaling error
or abnormal release of the R2
register occurs, or if the originating
office cannot provide sufficient ANI
digits.
—continued—

DMS-100 International Technical Specification BCS40i and up

6–38 Interfaces and signaling

Table 6–6xxx
Generic R2 register signaling – called subscriber status activities (continued)
Activity Meaning Explanation

SUB_BUSY called subscriber This activity indicates that the line or

busy lines associated with the called
number are already in use, that is
call processing busy (CPB), or the
line circuit is manual-busy at the
switch (MB or PMB)

As an originating exchange, DMS

accesses table TRTMTCAT to
determine the treatment to apply to
the originating line.

As a tandem exchange in link-by-link

mode, DMS responds to receiving
SUB_BUSY based on treatment to
activity mapping of the outgoing and
incoming trunks. DMS examines the
datafill of the outgoing trunk to
determine the treatment associated
with the SUB_BUSY activity. DMS
then determines if the treatment
maps to an activity in the datafill for
the incoming trunk,. If so, it sends
that activity to the originating
exchange. If not, treatment is
applied in the tandem exchange.

As a terminating exchange, DMS

sends SUB_BUSY as the called
subscriber status if the terminating
subscriber line is CPB, PMB, or MB.
If the terminating line is a member of
a hunt group, DMS sends
SUB_BUSY if there is no idle
member of the group.
—continued—

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–39

Table 6–6xxx
Generic R2 register signaling – called subscriber status activities (continued)
Activity Meaning Explanation

SUB_LBUSY subscriber line This activity indicates that the

busy in local call subscriber’s line is already in use in
a local call, or has been manually
removed from service at the
terminating exchange for
maintenance.

As an originating exchange, DMS

accesses table ACTTRTMT and
applies the appropriate treatment to
the originating line.

As a tandem exchange in link-by-link

mode, DMS propagates
SUB_LBUSY to the previous
exchange.

As a terminating exchange, DMS

sends SUB_LBUSY as the called
subscriber status if the subscriber
status type is OPR_BREAKIN, the
terminating agent is a line, and the
line is call processing busy (CPB),
manual busy (MB) or peripheral
manual busy (PMB).
SUB_TBUSY subscriber line This activity indicates that the
busy in toll call subscriber’s line is already in use in
a toll call.

As an originating exchange, DMS

accesses table ACTTRTMT and
applies the appropriate treatment to
the originating line.

As a tandem exchange in link-by-link

mode, DMS sends CONGESTION to
the previous exchange if the calling
category is REGULAR or DATA.
Otherwise, DMS propagates
SUB_TBUSY to the previous
exchange.

As a terminating exchange, DMS

sends SUB_TBUSY as the called
subscriber status if the terminating
agent is a line involved in a toll call.
—continued—

DMS-100 International Technical Specification BCS40i and up

6–40 Interfaces and signaling

Table 6–6xxx
Generic R2 register signaling – called subscriber status activities (continued)
Activity Meaning Explanation

SUB_OUT_ORD subscriber line out This activity indicates that the called
of order subscriber line is out of service or
faulty.

As an originating exchange, DMS

accesses table ACTTRTMT and
applies the appropriate treatment to
the originating line.

As a tandem exchange in link-by-link

mode, DMS responds to receiving
SUB_OUT_ORD based on treatment
to activity mapping of the outgoing
and incoming trunks. DMS examines
the datafill of the outgoing trunk to
determine the treatment associated
with the SUB_OUT_ORD activity.
DMS then determines if the
treatment maps to an activity in the
datafill for the incoming trunk,. If so,
it sends that activity to the originating
exchange. If not, treatment is
applied in the tandem exchange.

As a terminating exchange, DMS

sends SUB_OUT_ORD if the called
subscriber status is installation busy
(INB).
—continued—

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–41

Table 6–6xxx
Generic R2 register signaling – called subscriber status activities (continued)
Activity Meaning Explanation

TEMP_OUT_ORD subscriber line This activity indicates that the called

temporarily out of subscriber line is out of service or
order faulty.

As an originating exchange, DMS

accesses table ACTTRTMT and
applies the appropriate treatment to
the originating line.

As a tandem exchange in link-by-link

mode, DMS responds to receiving
TEMP_OUT_ORD based on
treatment to activity mapping of the
outgoing and incoming trunks. DMS
examines the datafill of the outgoing
trunk to determine the treatment
associated with the activity
TEMP_OUT_ORD. DMS then
determines if the treatment maps to
an activity in the datafill for the
incoming trunk,. If so, it sends that
activity to the originating exchange.
If not, treatment is applied in the
tandem exchange.

As a terminating exchange, DMS

sends TEMP_OUT_ORD as the
called subscriber status if the called
subscriber line is CO, or has the line
option PLP.
—continued—

DMS-100 International Technical Specification BCS40i and up

6–42 Interfaces and signaling

Table 6–6xxx
Generic R2 register signaling – called subscriber status activities (continued)
Activity Meaning Explanation

UNASSIGN_NUM unassigned This activity indicates that the called

number number is unassigned.

As an originating exchange, DMS

accesses table ACTTRTMT on
receipt o this activity and applies the
appropriate treatment to the
originating line.

As a tandem exchange in link-by-link

mode, DMS responds to receiving
UNASSIGN_NUM based on
treatment to activity mapping of the
outgoing and incoming trunks. DMS
examines the datafill of the outgoing
trunk to determine the treatment
associated with the activity
UNASSIGN_NUM. DMS then
determines if the treatment maps to
an activity in the datafill for the
incoming trunk,. If so, it sends that
activity to the originating exchange.
If not, treatment is applied in the
tandem exchange.

As a terminating exchange, DMS

sends this activity if the called
subscriber line is software
unassigned (SU), has options DTM
or SUS assigned, or translates to
BLKDN or VACANT treatment.
—continued—

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–43

Table 6–6xxx
Generic R2 register signaling – called subscriber status activities (continued)
Activity Meaning Explanation

CONNECT_CALL_ subscriber This activity indicates that the called

CHG address party is available, charge on answer.
complete, charge,
set up speech As an originating exchange, DMS
terminates register signaling on
receipt of this activity, connects
PCM, and waits for line signaling to
indicate that the call has been
answered. Upon answer, billing is
started if required.

As a tandem exchange in link-by-link

mode, DMS terminates register
signaling on receipt of this activity,
connects PCM, and waits for line
signaling to indicate that the call has
been answered. The answer signal
is propagated to the previous
exchange.

As a terminating exchange, DMS

sends this activity if the called party
is IDLE. Register signaling is
completed and ringing is applied to
the trunk. When the called party
answers, PCM is connected and the
answer signal is sent via line
signaling.
—continued—

DMS-100 International Technical Specification BCS40i and up

6–44 Interfaces and signaling

Table 6–6xxx
Generic R2 register signaling – called subscriber status activities (continued)
Activity Meaning Explanation

CONNECT_CALL_ subscriber This activity indicates that the called

NOCHG address subscriber is available, do not charge
complete, do not on answer.
charge, set up
speech As an originating exchange, DMS
terminates register signaling on
receipt of this activity, connects
PCM, and waits for line signaling to
indicate that the call has been
answered. The call is marked as a
free call.

As a tandem exchange in link-by-link

mode, DMS terminates register
signaling on receipt of this activity,
connects PCM, and waits for line
signaling to indicate that the call has
been answered. The answer signal
is propagated to the previous
exchange.

As a terminating exchange, DMS

sends this activity if the called party
is IDLE and the line has option FNT
assigned. Register signaling is
completed and ringing is applied to
the trunk. When the called party
answers, PCM is connected and the
answer signal is sent via line
signaling.
—continued—

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–45

Table 6–6xxx
Generic R2 register signaling – called subscriber status activities (continued)
Activity Meaning Explanation

TERM_CTRL_CHG terminator control This activity indicates that the called

charge subscriber line is free, but the
terminating exchange is requesting
terminator control supervision for the
call.

As an originating exchange, DMS

terminates register signaling on
receipt of this activity, connects
PCM, and waits for line signaling to
indicate that the call has been
answered. Upon answer, billing is
started if required.

As a tandem exchange in link-by-link

mode, DMS terminates register
signaling on receipt of this activity,
connects PCM, and waits for line
signaling to indicate that the call has
been answered. The answer signal
is propagated to the previous
exchange.

As a terminating exchange, DMS

sends this activity if the called party
is IDLE and has the malicious call
trace (MCT) feature active, to allow
terminator control of the connection.
Register signaling is completed and
ringing is applied to the trunk. When
the called party answers, PCM is
connected and the answer signal is
sent via line signaling.
—continued—

DMS-100 International Technical Specification BCS40i and up

6–46 Interfaces and signaling

Table 6–6xxx
Generic R2 register signaling – called subscriber status activities (continued)
Activity Meaning Explanation

SUB_XFRD subscriber This activity indicates that the called

transferred subscriber has transferred and can
not be reached at the called number.

As an originating exchange, DMS

accesses table ACTTRTMT on
receipt of this activity, releases the
circuit chain, and applies the
appropriate treatment (routing to an
announcement machine or
centralized service center, or
transmission of an information tone).

As a tandem exchange in link-by-link

mode, DMS responds to receiving
SUB_XFRD based on treatment to
activity mapping of the outgoing and
incoming trunks. DMS examines the
datafill of the outgoing trunk to
determine the treatment associated
with the activity SUB_XFRD. DMS
then determines if the treatment
maps to an activity in the datafill for
the incoming trunk,. If so, it sends
that activity to the originating
exchange. If not, treatment is
applied in the tandem exchange.

As a terminating exchange, DMS

sends SUB_XFRD if the datafill in
table TRTMTACT for the called
subscriber line specifies application
of this signal if the subscriber has
transferred.
—continued—

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–47

Table 6–6xxx
Generic R2 register signaling – called subscriber status activities (continued)
Activity Meaning Explanation

LAST_PTY_REL subscriber line This activity indicates that the called

free, charge, last party is available, charge on answer,
party release and last party release should occur.

As an originating exchange, DMS

terminates register signaling on
receipt of this activity, connects
PCM, and waits for line signaling to
indicate that the call has been
answered. Upon answer, billing is
started if required.

As a tandem exchange in link-by-link

mode, DMS terminates register
signaling on receipt of this activity,
connects PCM, and waits for line
signaling to indicate that the call has
been answered. The answer signal
is propagated to the previous
exchange.

As a terminating exchange, DMS

does not generate this signal.
—continued—

DMS-100 International Technical Specification BCS40i and up

6–48 Interfaces and signaling

Table 6–6xxx
Generic R2 register signaling – called subscriber status activities (continued)
Activity Meaning Explanation

MUT_CTRL_CHG mutual control of This activity indicates that the called

call by both subscriber is available, charge on
subscribers answer, and that call termination is
controlled by either subscriber.

As an originating exchange, DMS

terminates register signaling on
receipt of this activity, connects
PCM, and waits for line signaling to
indicate that the call has been
answered. Upon answer, billing is
started if required.

As a tandem exchange in link-by-link

mode, DMS terminates register
signaling on receipt of this activity,
connects PCM, and waits for line
signaling to indicate that the call has
been answered. The answer signal
is propagated to the previous
exchange.

As a terminating exchange, DMS

sends MUT_CTRL_CHG as the
called subscriber status if the called
subscriber is IDLE, and the calling
party’s service class is a local voice,
facsimile, or data call. When the
called party answers, PCM is
connected and the answer signal is
sent via line signaling.
—continued—

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–49

Table 6–6xxx
Generic R2 register signaling – called subscriber status activities (continued)
Activity Meaning Explanation

SPARE_TRTMT1 spare treatment These activities are used to indicate

SPARE_TRTMT2 status 1, spare called subscriber status indications
treatment status 2 not provided by other activities.

As an originating exchange, DMS

accesses table TRTMTACT on
receipt of either of these activities
and applies the appropriate
treatment to the originating line.

As a tandem exchange in link-by-link

mode, DMS responds to receiving
either of these activities based on
treatment to activity mapping of the
outgoing and incoming trunks. DMS
examines the datafill of the outgoing
trunk to determine the treatment
associated with either of these
activities. DMS then determines if
the treatment maps to an activity in
the datafill for the incoming trunk,. If
so, it sends that activity to the
originating exchange. If not,
treatment is applied in the tandem
exchange, and the outgoing trunk is
released.
End

DMS-100 International Technical Specification BCS40i and up

6–50 Interfaces and signaling

Generic R2 special activities

The activities listed in table 6–7 are used for initialization and timeout
monitoring of R2 signaling.

Table 6–7xxx
Generic R2 register signaling – special activities
Activity Meaning Explanation

INIT_OG_ACT initial outgoing This activity initializes the outgoing

activity trunk compeller for subsequent
activity transmission. INIT_OG_ACT
is always the first activity processed
by outgoing trunks.
INIT_IC_ACT initial incoming This activity initializes the incoming
activity trunk compeller for subsequent
activity reception. INIT_OG_ACT is
always the first activity processed by
incoming trunks.
RCV_TMO_ACT compeller timeout This activity is processed when a
compel timeout occurs. The action
taken by DMS depends on the
protocol in use, the phase of the R2
signaling, and the activity which has
timed out. The appropriate treatment
signal, if any (for example,
CONGESTION) to be sent if
compeller timeout occurs is specified
in incoming trunk datafill.
End

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–51

Multifrequency compelled register signaling codes

The multifrequency compelled (MFC) register signaling system used by the
DMS-100 International switch is based on CCITT Yellow Book (Q441)
standards. Register signals are transmitted and received via an inter-register
coding scheme in which each signal, or code, consists of the simultaneous
transmission of two out of a set of six predetermined inband frequencies.
For most R2 variants, two sets of frequencies are defined; one in the forward
direction and one in the backward direction.
The DMS-100 International register signaling system is flexible and can be
customized by Northern Telecom to meet requirements for various register
signaling formats. Table 6–8 on page 6–52 lists the generic set of MFC
codes for DMS-100 International applications.
A typical MFC signaling exchange is as follows:
• Following the seizure of the outgoing link, the forward register sends the
first forward signal (connects a forward multifrequency tone).
• The backward register in the next exchange detects the forward signal,
determines its meaning, and sends a backward signal (connects a
backward multifrequency tone). The backward signal acts as an
acknowledgement to the forward signal, and may also convey additional
information.
• The forward register detects the presence of the backward signal,
determines its meaning, and responds by removing the forward signal
(disconnects the forward multifrequency tone).
• The backward register detects the cessation of the forward signal and in
response removes its backward signal (disconnects the backward
multifrequency tone).
• The forward register detects the cessation of the backward signal and
may now send the next forward signal.
In some situations it is necessary for the backward register to send a fixed
duration, or pulsed, signal without prior reception of forward signal. This
can occur when the backward register has acknowledged the last forward
signal, but is unable to complete the call, and no additional forward signals
are received.

DMS-100 International Technical Specification BCS40i and up

6–52 Interfaces and signaling

Table 6–8xxx
Generic multifrequency compelled (MFC) signaling codes
Code combinations Frequencies
Backward f0 1380 f1 1500 f2 1620 f4 1740 f7 1860 f11
1980
Forward f0 1140 f1 1020 f2 900 f4 780 f7 660 f11
540
1 f0 + f1 x x
2 f0 + f2 x x
3 f1 + f2 x x
4 f0 + f4 x x
5 f1 + f4 x x
6 f2 + f4 x x
7 f0 + f7 x x
8 f1 + f7 x x
9 f2 + f7 x x
10 f4 + f7 x x
11 f0 + f11 x x
12 f1 + f11 x x
13 f2 + f11 x x
14 f4 + f11 x x
15 f7 + f11 x x

R2 signaling timing
R2 signaling timing is summarized in table 6–9. Timers T1, T4, T5 and T6
are used for compelled and pulsed timing by incoming trunks, and timers
T2, T3, T7 and T8 are used by outgoing trunks.

Table 6–9xxx
R2 signaling timing
Timer RGSIGSYS Parm Description
T1 ICMXISIG maximum inter-signal time
T2 OGMXTON maximum forward tone-on time
T3 OGMXTOFF maximum forward tone-off time
T4 ICPREPLS pre-pulse pause
T5 ICPLSTIM pulse duration
T6 ICPSTPLS post-pulse pause
T7 OGRMXPLS maximum received pulse length
T8 OGPSTPLS forward post-pulse pause

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–53

Interoffice line signaling

The DMS-100 International switch uses a flexible digital line signaling
system on a 2048 k bit per second carrier. A wide range of line signaling
protocols are currently supported.
Table 6–10 lists the signaling protocols which can be assigned to DMS-100
International trunks, and an overview of the characteristics associated with
each. For detailed explanations of the flexible parameters associated with
each line signaling protocol, refer to table LNSIGSYS in Customer Data
Schema, 297–1001–451.

Table 6–10xxx
Line signaling systems
Signaling type Signaling system characteristics

WINGSIG Wink-start
NTLS01 Delay-dial
NTLS03 Used in one-way outgoing applications such as
terminating trunks from a DMS-200 switch to an
operator switchboard. Call processing operation is
seize only, without outpulsing. This line signaling
system uses A-bit signaling for all standard telephony
signals and includes B-bit blocking and unblocking
signals.
NTLS04 Used in one-way incoming applications such as junctor
trunking from an operator switchboard to a DMS-200
switch, NTLS24 protocol includes a single A-bit state
transition followed by a restoration to the original state
when the stop transmission (ST) signal is received at
the end of the digit string. This system uses only A-bit
signaling for all standard telephony signals.
NTLS05 Used in one-way incoming applications such as
specialized junctor trunking from an operator
switchboard to a DMS-200 switch. The operation
involves the same signaling as NTLS04, but also
includes an end-of-selection (EOS), start ringing
(SRG), and break-in-request (BIR) signals. This
system uses the A-bit for all standard telephony
signals except for SRG and BNR signals, which use
the B-bit. The B-bit is also used for blocking and
unblocking signals.
—continued—

DMS-100 International Technical Specification BCS40i and up

6–54 Interfaces and signaling

Table 6–10xxx
Line signaling systems (continued)
Signaling type Signaling system characteristics

NTLS06 incoming Used in one-way incoming E&M applications from a

DMS-200 switch to end offices that carry BA-1
switchboard traffic originating on trunks with NTLS05
signaling. The operation is the same as delay-dial
signaling, but also includes the end-of-selection
(EOS), start ringing (SRG), and break-in-request (BIR)
signals. NTLS06 incoming uses the A-bit for the EOS,
SRG, BIR, and all standard telephony signals.
NTLS06 outgoing Used in one-way outgoing E&M applications from a
DMS-200 switch to end offices that carry BA-1
switchboard traffic originating on trunks with NTLS05
signaling. The operation is the same as delay-dial
signaling, but also includes the end-of-selection
(EOS), start ringing (SRG), and break-in-request (BIR)
signals. NTLS06 outgoing uses the A-bit for the EOS,
SRG, BIR, and all standard telephony signals.
NTLS07 incoming Used for one-way incoming applications from toll
exchanges to a DMS-100 switch. The operation is
identical to wink signaling, but also includes
end-of-selection (EOS), start ringing (SRG), and
break-in-request (BIR) signals. NTLS07 incoming
uses the A-bit for all standard telephony signals,
except for SRG and BIR, which use the B-bit. The
B-bit is also used for blocking and unblocking signals.
NTLS07 is compatible with NTLS05.
NTLS07 outgoing Used for one-way outgoing applications from a
DMS-200 switch to end offices. The operation is
identical to wink signaling, but also includes
end-of-selection (EOS), start ringing (SRG), and
break-in-request (BIR) signals. NTLS07 outgoing uses
the A-bit for all standard telephony signals, except for
SRG and BIR, which use the B-bit. The B-bit is also
used for blocking and unblocking signals. NTLS07 is
compatible with NTLS05.
NTLS08 incoming Used in one-way incoming applications (from VISA to
a DMS-200 switch) where E&M signaling is used.
NTLS08 uses a wink signal for the proceed-to-send
(PTS) signal and has no end-of-digits (EOD) signal.
The A-bit is used for all telephony signals.
NTLS08 outgoing Used in one-way outgoing applications (from a
DMS-200 switch to VISA) where E&M signaling is
used. The A-bit is used for all telephony signals.
—continued—

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–55

Table 6–10xxx
Line signaling systems (continued)
Signaling type Signaling system characteristics

NTLS09 incoming Used in one-way incoming direct current (DC) loop

signaling trunks that support malicious call trace.
NTLS09 incoming is used between DMS-100 local
offices, and also to connect DMS-100 offices to other
office types. The A-bit and the B-bit are used for
telephony signaling.
NTLS09 outgoing Used in one-way outgoing direct current (DC) loop
signaling trunks that support malicious call trace.
NTLS09 incoming is used between DMS-100 local
offices, and also to connect DMS-100 offices to other
office types. The A-bit and the B-bit are used for
telephony signaling.
NTLS10 Used for incoming and outgoing trunks which require
loop disconnect signaling. Channel banks are used to
convert incoming analog signals to digital signals, and
to convert outgoing digital signals to analog signals.
Digital telephony signals use the A-bit and the B-bit,
except for manual hold (MHD) which uses the C-bit.
NTLS11 Used for incoming and outgoing trunks which require
E&M signaling. Channel banks are used to convert
incoming analog signals to digital signals, and to
convert outgoing digital signals to analog signals.
Digital telephony signals use the A-bit.
NTLS14 Used for semi-permanent connection trunks. NTLS14
ignores signaling parameters.
NTLS15 incoming Used in one-way incoming International Traffic
Operator Position System (ITOPS) or metering (MTR)
trunks that support operator control of disconnect
(instead of originator control), operator ringback, and
operator ring forward. NTLS15 incoming can support
delay-dial start or wink start signals.
NTLS15 outgoing Used in one-way outgoing International Traffic
Operator Position System (ITOPS) or metering (MTR)
trunks that support operator control of disconnect
(instead of originator control), operator ringback, and
operator ring forward. NTLS15 incoming can support
delay-dial start or wink start signals.
NTLS16 incoming Used for CCITT-compliant R2 signaling for incoming
trunks. NTLS16 uses the A-bit and the B-bit for
telephony signals. Supports malicious call trace
(MCT) line signaling.
—continued—

DMS-100 International Technical Specification BCS40i and up

6–56 Interfaces and signaling

Table 6–10xxx
Line signaling systems (continued)
Signaling type Signaling system characteristics

NTLS16 outgoing Used for CCITT-compliant R2 signaling for outgoing

trunks. NTLS16 uses the A-bit and the B-bit for
telephony signals. Supports malicious call trace
(MCT) line signaling.
NTLS16 two-way Used for CCITT-compliant R2 signaling for two-way
trunks. NTLS16 uses the A-bit and the B-bit for
telephony signals.
NTLS20 incoming Used on CH01, CH03, CH04, CH05, incoming CH06,
incoming CH07, and CH09 trunk interfaces. The A-bit
is used to indicate the hook state of the originating and
terminating agents. The B-bit is used for seizure
acknowledgement (terminating only) and blocking
signals. The C-bit provides operator events signaling
and meter signaling.
NTLS20 outgoing Used on CH02, outgoing CH06, and outgoing CH07
trunk interfaces. The A-bit is used to indicate the hook
state of the originating and terminating agents. The
B-bit is used for seizure acknowledgement
(terminating only) and blocking signals. The C-bit
provides operator events signaling and meter
signaling.
NTLS22 Used for incoming toll calls including toll to tandem,
tandem to tandem, tandem to local, and toll to local
calls. The A-bit and the B-bit are used for telephony
signals.
NTLS24 outgoing Pulsed line signaling protocol used for trunks
connecting DMS-100 and DMS-200 International
switches to Alcatel and Ericsson systems via the
national network. The A-bit is used for telephony
signaling.
N5 CCITT no.5 signaling system

End

Updating of signaling system data in the peripheral modules

Signaling parameters are part of the downloadable software associated with
the International digital trunk controller (IDTC). As specified in datafill, the
appropriate parameters are downloaded to the IDTC by the core processor
when the IDTC is returned to service. This action occurs when the IDTC is
returned to service manually by MAP command, or on automatic
return-to-service from system-busy state by the system. IDTC units can
also be manually downloaded before they are returned to service, using the
LOADPM command at the PM level of the MAP. Refer to the Menu

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–57

Commands Reference Manual, 297-1001-821, for information on the

LOADPM command.

Call processing
Refer to chapter 5, “Call Processing” for additional information on call
processing signaling and treatments.
The following functionalities are supported on the DMS-100 International
switch:
• link by link connections
• end to end connections
• local or remote application of treatments.

End-to-end signaling
End-to-end signaling is supported on the DMS-100 International switch. If a
call connection involves incompatible trunk signaling systems, or digit
processing is required, link-by-link signaling must be used.
R2 trunk classes
For some R2 protocols, trunk classes must be defined. These classes are
then used to impose restrictions or imply functionality based on the type of
traffic which flows over a trunk. R2 trunks are categorized in the following
classes.
• CAMA: Trunks are assigned the CAMA class if ANI information must
be sent to the next office, or collected from a previous office.
• None: If ANI information is not required, the trunk is assigned the
traffic class NONE.
Call control
Calls over R2 trunks normally use calling subscriber control. With calling
subscriber control, if the calling subscriber goes on-hook first, the
connection is released immediately. If the called subscriber remains
off-hook for a period of 10 (typical) seconds, the line receives disconnect
treatment. If the called subscriber goes on-hook within 10 seconds (typical)
of the calling subscriber going on-hook, the line is set to idle and no
treatment is applied.
With calling subscriber control, if the called subscriber goes on-hook first,
calling subscriber re-answer timing is started. Metering continues during
this re-answer timing. If the re-answer time expires and the called
subscriber is still on-hook, the connection is released. If the calling
subscriber remains off-hook for another 10 seconds (its lockout time), the
calling subscriber receives disconnect treatment.

DMS-100 International Technical Specification BCS40i and up

6–58 Interfaces and signaling

If the called subscriber goes back off-hook during the re-answer period, the
re-answer timing is stopped, and the call continues (since the connection was
never released).
If the calling subscriber goes on-hook during the re-answer period, the
connection is released, re-answer timing is stopped, and both subscribers are
marked as idle. If the calling subscriber goes on-hook during its lockout
timing, no treatment is applied.

PCM-30 carrier maintenance and alarms

Local alarm
A local carrier alarm is raised if:
• The IDTC loses frame synchronization on the received PCM-30 signal
for a sufficient amount of time.
• The number of frame synchronization losses in a defined period reaches
the out-of-service limit.
• The IDTC loses multi-frame synchronization on the received PCM-30
signal for a sufficient amount of time.
• The number of multi-frame synchronization losses in a defined period
reaches the out-of-service limit.
• The carrier slip rate reaches the out-of-service limit.
• The carrier bit error rate reaches the out-of-service limit.
• The IDTC receives an alarm indication from the far end of remote frame
loss.
• The IDTC receives an alarm indication from the far end of remote
multi-frame loss.
• The IDTC receives continuous stream of 1s, that is, loss of carrier.

If the alarm is continuous for a defined period of time, the trunks on the
IDTC are taken out of service and the channel bank or digital office at the
end of the PCM-30 line is informed. At the end of the alarm state, the trunks
are returned to service and the remote alarm is removed.
If the alarm is not continuous, the event is recorded as a “hit”. If the number
of hits recorded in a given period exceeds the maintenance limit, the alarm is
activated. If the number of events exceeds the out-of-service limit, the
trunks on the IDTC are taken out of service and the channel bank or digital
office at the end of the PCM-30 line is informed. At the end of the alarm
state, (that is, no hits within a defined period), the trunks are returned to
service and the remote alarm is removed.
Refer to table 6–11 on page 6–61 for detailed timing specifications on the
alarm types discussed in the following sections.

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–59

MFC Monitor tool

This feature enables the craftsperson to easily monitor the register signaling
on an MFC trunk. This signaling monitor, SIGMON, monitors up to 4
trunks simultaneously. After calls are made over these trunks, the monitor
describes both incoming and outgoing register signals. The signals are
described by phase change, signal number, text description and timestamp.
Loss-of-frame synchronization
When loss of frame synchronization on an incoming PCM-30 line is
detected, the IDTC immediately informs the central control (CC) of the
DMS-100 International switch. If the condition persists, a local alarm is
raised by the CC and the trunks are busied out. While in the alarm state, the
IDTC must recover and remain in frame synchronization for a continuous
period in order for the CC to end the alarm and return the trunks to service.
Maintenance and out-of-service limits are specified by the operating
company on a per-IDTC basis.
During a loss of frame occurrence, the channel bank or digital office at the
end of the PCM-30 line is informed by changing bit 3 of channel time slot 0
from state 0 to state 1. At the end of the alarm period this bit is reset to 0.
Loss-of-multi-frame synchronization
When multi-frame synchronization loss is on an incoming PCM-30 line is
detected, the IDTC immediately informs the core processor (the Central
Control Complex on NT40–based systems, or the Computing Module on
SuperNode-based systems). If the condition persists, a local alarm is raised
by the core processor and the trunks are busied out. While in the alarm
state, the IDTC must recover and remain in multi-frame synchronization for
a continuous period in order for the core processor to end the alarm and
return the trunks to service.
Maintenance and out-of-service limits are specified by the operating
company on a per-IDTC basis.
If a loss of multi-frame synchronization occurs, the channel bank or digital
office at the end of the PCM-30 line is informed by changing bit six from 0
to 1 in time slot 16 of frame 0 of the multi-frame. At the end of the alarm
period this bit is reset to 0.
Slip monitoring
The IDTC sends a message to the core processor each time a frame slip
occurs on the received PCM-30 facility. Maintenance and out-of-service
limits are specified by the operating company on a per-office basis.
If the maintenance limit is reached, a log message is generated. If the
out-of-service limit is reached, trunks on the PCM-30 facility are placed in a
system-busy state and must be manually restored to service.

DMS-100 International Technical Specification BCS40i and up

6–60 Interfaces and signaling

Bit error rate monitoring

The IDTC sends a message to the core processor for each bit error rate
occurrence detected in the frame alignment signal. Maintenance and
out-of-service limits are specified by the operating company on a per-IDTC
basis.
If the maintenance limit is exceeded, a log message is generated. If the
out-of-service limit is exceeded, the IDTC is placed in a local alarm
condition until the trunks have been manually restored to service.
Remote frame and multi-frame loss of synchronization
When remote frame or multi-frame loss of synchronization alarm state on
the incoming PCM-30 line is detected, the IDTC immediately informs the
core processor. If the condition persists, a local alarm is raised by the core
processor and the trunks are busied out. While in the alarm state, the IDTC
must recognize the absence of remote alarm condition on the PCM-30 line
for a continuous period to end the alarm and return the trunks to service.
Maintenance and out-of-service limits for random occurrences are specified
by the operating company on a per-IDTC basis.
Alarm indication signal
When a continuous stream of “1”s on the PCM-30 line is detected, the
IDTC immediately informs the core processor. If the condition persists, a
local alarm is raised by the core processor and the trunks are busied out.
While in the alarm state, the IDTC must recognize the absence of a
continuous stream of “1”s on the PCM-30 line for a defined period to end
the alarm and return the trunks to service.
Maintenance and out-of-service limits are specified for random occurrences
by the operating company on a per-IDTC basis.
During the alarm condition, the channel bank or digital office at the end of
the PCM-30 line is informed by changing bit 3 of channel five slot 0 from
state 0 to state 1, in the frames that do not contain the frame alignment
signal. At the end of the alarm period, this condition is removed.

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–61

Table 6–11xxx
Carrier maintenance alarms
Alarm types Out of Return to Maintenance Out of
service time service time limit service limit
Local loss of Range 0 – 25.5 s in 0 – 25.5 s in 0 – 255 0 – 255
frame 0.1 s 0.1 s events events
synchronization
h i ti Default 3s 3s 4 events in 20 events in
value 1 min 5 min
Local loss of Range 0 – 25.5 s in 0 – 25.5 s in 0 – 255 0 – 255
multiframe 0.1 s 0.1 s events events
synchronization
h i ti Default 3s 3s 4 events in 20 events in
value 1 min 5 min
Remote loss of Range 0 – 25.5 s in 0 – 25.5 s in 0 – 255 0 – 255
frame 0.1 s 0.1 s events events
synchronization
h i ti Default 3s 3s 4 events in 20 events in
value 1 min 5 min
Remote loss of Range 0 – 25.5 s in 0 – 25.5 s in 0 – 255 0 – 255
multiframe 0.1 s 0.1 s events events
h i ti
synchronization Default 3s 3s 4 events in 20 events in
value 1 min 5 min
Alarm indica- Range 0 – 25.5 s in 0 – 25.5 s in 0 – 255 0 – 255
tion signal 0.1 s 0.1 s events events
Default 3s 3s 4 events in 20 events in
value 1 min 5 min
Bit error rate Range 0 – 255 0 – 255
events events
Default 4 events in 20 events in
value 1 min 5 min
Frame slip Range 0 – 255 0 – 255
occurrences events events
Default 4 events in 20 events in
value 1 min or 24 h 5 min or 24 h
Note: Measurement period adjustable to 24 hours for use in synchronous networks.

DMS-100 International Technical Specification BCS40i and up

6–62 Interfaces and signaling

Common channel signaling 7 (CCS7)

This section provides an overview of CCS7 signaling on the DMS-100
International switch. Additional information on the Chinese implementation
of CCS7 can be found in the DMS SuperNode Common Channel Signaling 7
Product Guide, 297-5151-010C.
CCS7 overview
CCS7 signaling is divided into two types: connection-oriented signaling and
connectionless signaling.

Connection-oriented signaling
Connection-oriented signaling, also referred to as trunk signaling, is used to
setup, monitor, and take down a telephone user part (TUP) call.

Figure 6–2 illustrates an example of connection-oriented signaling in which

the signaling that is used to set up and monitor the call is routed from the
originating signaling point (SP), through a signaling transfer point (STP), to
the terminating SP. Voice traffic is placed on a voice trunk, called a TUP
trunk, that connects the originating SP to the terminating SP.
Figure 6–2
Connection-oriented signaling (trunk signaling)
FW-31258

STP

Signaling link
Signaling link

Originating Terminating
SP SP

TUP trunk

Connectionless signaling
Connectionless signaling, also referred to as transaction services, is not
associated with the setup and takedown of a TUP call. For example,
connectionless signaling is used to access a database for 800 number
translations.

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–63

Figure 6–3 illustrates the use of connectionless signaling to access a

database for the translation of an 800 number to a directory number (DN)
and numbering plan area code.

The request for 800 number translation is passed through signaling messages
from a per trunk signaling (PTS) end office (EO) to a DMS signaling
point/service switching point (SP/SSP).

The DMS SP/SSP routes the request through the signaling network to a
DMS service control point II (DMS-SCPII), where the transaction is
processed.

The DMS-SCPII returns the translated number back through the signaling
network to the DMS SP/SSP, which sends the translated number to the EO
that made the original transaction request. Processing then continues as for
a connection-oriented call.
Figure 6–3
Connectionless signaling (transaction services)
FW-30070

SSP Signaling STP

link

Per trunk signaling Signaling link

EO SCPII

DMS-100 International Technical Specification BCS40i and up

6–64 Interfaces and signaling

Modes of operation
The term common channel signaling mode refers to the relationship between
the signaling component and the voice and data component of a call. CCS7
uses two signaling modes: associated signaling and quasi-associated
signaling.
Associated signaling
In associated signaling, the signaling links (SL) follow the same route as the
TUP trunk for a call. TUP trunks are interoffice circuits that carry the voice
and data traffic between originating and terminating SPs or SSPs.

Associated signaling does not require a DMS-STP and can be used to initiate
low-volume applications. Figure 6–4 illustrates a low-cost, simple
configuration of two connecting SSPs.
Figure 6–4
Associated signaling in a simple configuration
FW-31259

Signaling link
Originating Terminating
service service
switching switching
point point
TUP trunks

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–65

Quasi-associated signaling
In quasi-associated signaling, the signaling information is routed along links
that do not follow the same route as the TUP trunk for a call. Instead,
signaling is carried through the signaling network along indirect routes on
two or more SLs.

Figure 6–5 illustrates an example of quasi-associated signaling in which the

signaling is routed from the originating SP, through an STP, to the
terminating SP. Voice and data traffic is placed on a TUP trunk that directly
connects the originating and terminating SPs.
Figure 6–5
Quasi-associated signaling mode
FW31260

Signaling
transfer
point

Signaling link Signaling link

Originating Terminating
signaling signaling
point point

TUP trunks

DMS-100 International Technical Specification BCS40i and up

6–66 Interfaces and signaling

Quasi-associated signaling, more powerful than associated signaling, uses a

DMS-STP. It is designed for volume applications and can be configured to
meet the needs of operating companies with varying degrees of
sophistication. Figure 6–6 illustrates a complex network of STPs, SCPs, and
SP/SSPs.
Figure 6–6
Quasi-associated signaling in a complex configuration
FW30157

SCPII SCPII
STP STP

SCPII database

STP STP STP STP STP STP

SSP SSP

STP STP STP STP

How nodes communicate across the network

Nodes in a CCS7 network communicate with each other through direct and
alternate communication paths.
Direct communication paths
Direct communication between two adjacent nodes in a CCS7 network
occurs through an SL. Direct communication paths are called links or
linksets.
A link is a communication channel between two adjacent nodes in a
signaling network. A linkset is a set of links that is used as a group to carry
signaling traffic between two nodes in a signaling network. The maximum
number of links in a linkset is 16.

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–67

Alternate communication paths

Direct communication between CCS7 nodes becomes impractical as the
distances between nodes in the network increase. As a result, alternate
communication paths are established that provide various routes between
nodes throughout the network. Alternate communication paths are called
routes or routesets.
A route is a signaling path connecting an originating node to a destination
node. A routeset is a logical grouping of routes from a node that have the
same destination.

Figure 6–7 on page 6–68 illustrates two examples of CCS7 network

communications.

Example A in figure 6–7 shows a route that consists of three linksets. The
route originates from the SSP and terminates at the SCP. Example A also
illustrates that a linkset consists of a set of links.

Example B in figure 6–7 shows two routes. Both routes originate from the
same node and terminate at the same destination node in the network.
Together, route A and route B form a routeset that originates from the same
SSP and terminates at the same SCP.

DMS-100 International Technical Specification BCS40i and up

6–68 Interfaces and signaling

Figure 6–7
CCS7 network communications
FW30059

links
Example A

STP STP SCP

Linkset
Linkset
Linkset
Route A
SSP Database

STP STP SCP

Database

Example B
STP STP SCP
Linkset Linkset

Linkset Route A
SSP Linkset Database

Route B
Linkset
STP STP SCP

Database

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–69

How messages are handled in a CCS7 network

CCS7 is a packet-switched network based on the transmission and reception
of information packets called message signal units (MSU). Each node can
format and transmit MSUs to other nodes in the network. It is through the
interpretation of and response to MSUs that CCS7 network communications
are achieved.

Signaling message format

Each MSU contains a signaling information field (SIF). In the standard SIF,
the portion that is used for routing is called the routing label. This is
illustrated in figure 6–8.
The routing label contains the following information:
• an origination point code (OPC) that indicates the originator node for an
MSU
• a destination point code (DPC) that indicates the final destination node
of the MSU
• an SL selector code that the message routing function uses to distribute
loading evenly
The standard routing label assumes that each SP in a signaling network is
allocated a code according to a labeling code plan. MSUs that are labeled
according to international and national code plans are identified by the DPC
that is included in each message.

DMS-100 International Technical Specification BCS40i and up

6–70 Interfaces and signaling

Figure 6–8
CCS7 message routing label
FW30055

(signaling information octet)

MSU
(CCS7 SIF (signaling SIO
message information field)
signal unit )

SIF
(signaling User-specific information Routing
information label
field)

Routing
Signaling link Originating Destination
label
selector code point code point code

Originating
point code Network Network Network
identification cluster cluster member

Message discrimination
Message discrimination is the process that determines whether an MSU has
been delivered to its intended destination point. This decision is based on an
analysis of the DPC that is in the routing label of the MSU. If the SP to
which it is delivered is the destination point, then the MSU is delivered to
the message distribution function of the SP. If this SP is not the intended
destination point, the MSU is delivered to the routing function of the SP for
further transfer on an SL.

Message distribution
Message distribution is the process of analyzing the source indicator in the
MSU when it arrives at the destination point. The service information octet
(SIO) determines to which user part the MSU is to be delivered: either TUP
or signaling connection control part (SCCP).

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–71

Message routing
Message routing involves the selection of an appropriate SL for each MSU.
The route an MSU takes is determined through a combined analysis of
information that is contained in the routing label of the MSU and routing
data that is provided at the SP.

Message routing is determined by a destination code and an additional

load-sharing element that allows the signaling traffic to a particular
destination to be distributed over two or more SLs. This traffic distribution
can be limited to different links within a linkset or it can be applied to links
in different linksets.

The route that is taken by an MSU with a particular routing label is

predetermined and is normally fixed at a given time. If failures occur in the
signaling network, MSUs that would have taken the route that has failed are
rerouted in a predetermined manner, under control of the signaling traffic
management function at Level 3 of the message transfer part (MTP).

Although there are advantages to using standard routes for MSUs that
belong to different user parts, the service indicator that is included in each
message provides the potential for using different routing plans for different
user parts.

Signaling message path through a DMS-STP

A DMS-STP handles four types of CCS7 traffic:
• intra-LPP (messages destined for a link on the same LPP)
• inter-LPP (messages destined for a link on a different LPP)
• computing module (CM) to LIU7
• LIU7 to CM

Under normal operating conditions, most of the traffic handled by the

DMS-STP falls under the first two categories (intra-LPP and inter-LPP, both
of which represent tandem traffic). Figure 6–9 on page 6–73 illustrates
these two types of DMS-STP message processing. Maintenance messages
travel between the CM and the LIU7.
Intra-LPP and inter-LPP CCS7 traffic enters the DMS-STP on an SL
terminated by a DS-0A or V.35 paddle board (part of an LIU7). After
removal from the link, the message is passed to the signaling terminal (ST)
card (also part of an LIU7). Here, MTP functions such as error detection
and correction are performed. The message is then passed on to the last
LIU7 stage, the integrated processor and F-bus interface (IPF) card, where
the SCCP routing functions are performed, including global title translation
(GTT). The SCCP routing functions determine the destination code of the

DMS-100 International Technical Specification BCS40i and up

6–72 Interfaces and signaling

message which, for tandem traffic, indicates the outgoing SL. The message
is then queued for transport along the F-bus to the link interface module
(LIM).
When intra-LPP traffic reaches the LIM unit, it is not routed via the
DMS-bus. It is transmitted across the LIM and is queued for transport to the
appropriate SL through the F-bus, IPF, and ST.
When inter-LPP traffic reaches the LIM, it is transmitted over DS30 links to
the DMS-bus. When the message reaches the DMS-bus, it is queued for
transport to the appropriate LPP. The message travels to the LIM and is
queued for transport to the appropriate SL through the F-bus, IPF, and ST.
CCS7 traffic between the CM and the LIU7s includes such things as
network management messages. CM to LIU7 traffic crosses the CM
inter-communications (CMIC) links to the DMS-bus. From there it travels
across the DMS-bus to the LIM in the appropriate LPP. The traffic crosses
the LIM to the F-bus and is then transported down to the LIU7. It is then
transported into the CCS7 network on an SL. The LIU7 to CM traffic
follows the reverse route.

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–73

Figure 6–9
DMS-STP message processing
FW30163

DMS-core

DMS-bus

LIM unit LIM unit

F-bus F-bus

LIU7 A LIU7 A+1 LIU7 B LIU7 B+1

IPF IPF IPF IPF

Signaling Signaling Signaling Signaling

terminal terminal terminal terminal

Paddle Paddle Paddle Paddle

board board board board

LPP A LPP B
Signaling Signaling
link link
Message Message
routed routed Discriminator Router
between within one
LPPs LPP
SCCP processor

DMS-100 International Technical Specification BCS40i and up

6–74 Interfaces and signaling

Subscriber interfaces
Line circuits
The line circuit (LC) card is the final interface between the subscriber’s loop
and the digital circuitry in the switching network and central control.
Line circuits provide the following functions:
• office battery to the loop
• transmission of ringing and tones
• transmission of 12 or 16 KHz pulses
• transmission of battery reversal
• speech coding and decoding
• test access
• loop loss control
• loop balance
• 50 Hz or 60 Hz filtering
• loop supervision

Line circuit types

Two types of line circuits can be provisioned on DMS-100 International
switches: type A and type B. Type A line cards provide a basic plain
ordinary telephone service (POTS) voice and signaling interface between a
single-party, two-wire loop and the digital network of the DMS-100
International switch. Type B line cards, in addition to the above, also
interface to two-party or multiple-party lines, and lines which terminate on
more sophisticated subscriber equipment requiring battery reversal or 12 or
16 KHz pulses, such as coin lines or private branch exchange (PBX) lines.
Line cards reside in line drawers in the International Line Concentrating
Module. Both line card types can reside in the same line drawer.
The block diagram for type A line circuits is shown in figure 6–10 on page
6–77. The type B line circuit is illustrated in figure 6–11 on page 6–78.
World line card
The DMS-100 International switch can be provisioned with World Line
Cards (WLC), which employ programmable software templates to meet the
subscriber line characteristics, (for example, impedance requirements) of
specific operating companies. Type A (NT6X17BA) and Type B
(NT6X18BA) WLCs are available. The templates are programmed by
Northern Telecom based on specifications supplied by the operating
company.

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–75

The WLC can be programmed with the following characteristics:

• transmit gain
• receive gain
• PCM coding law (A-law or µ-law companding)
• balance impedance
• input impedance
• bit inversion selection
• metering tone frequency
• metering tone duration
• metertone test disable/enable
• equalization loss enable/disable
• current limit selection
• supervision threshold selection
• supervision configuration selection
• North American balance impedance selection
• North American default balance selection

Office (exchange) battery

Office battery feed configurations are country specific. Office battery is
usually supplied to the loop on the ring lead (B-lead) using a 200 ohm
resistor and ground, and on the tip side (A-lead) using a second 200 ohm
resistor. The office battery for the DMS-100 International switch is
nominally –48V dc. In extreme conditions, and for short term only, the
voltage can vary from –42.5V dc to –55.8V dc, measured at the MDF.
Ringing
Ringing is generated by the programmable duplicated ringing generator.
Each ILCM contains one ringing generator. The ringing multiplexer in each
ILCM supplies ringing to the line cards via the ring bus.
The ringing load of both ILCMs is shared by the two ringing generators. If
one fails, the other assumes the full ringing load of both ILCMs.
Tones generation
DTMF, supervisory, test and diagnostic tones are generated by and stored in
the NT6X69 Message Protocol and Tones circuit card, which resides in the
ILGC and the IDTC. The NT6X69LA vintage of the card uses tone
parameters stored in core software which are downloaded to the card when it
is returned to service, allowing modifications to country-specific toneset
specifications without hardware modification or upgrade.

DMS-100 International Technical Specification BCS40i and up

6–76 Interfaces and signaling

The tonesets in older vintages of the NT6X69 card are also country-specific,
but reside in fixed PROM on the circuit cards. In either case, the lines
signaling toneset for a particular country is specified in field TONESET of
data table LTCINV, as specified in DMS-100 International Customer Data
Schema, 297-1001-451i. Tonesets are defined in software on a
country-specific basis by Northern Telecom, based on specifications
supplied by the operating company.
Coin telephone interface
Coin telephone interfaces are provided via the NT6X94 line card.
Private branch exchange (PBX) interface
PBX lines requiring loop start signaling use the NT6X93 line card. The
NT6X94 line card provides the interface for PBX lines requiring
battery-reversal signaling, or 12 or 16 KHz control pulse signaling.
Subscriber premise meter control
12 or 16 KHz control pulses are generated in the line shelf and applied to the
subscriber loop through the line circuit.
Speech coding and decoding
Speech is converted from an analog form to a digital form and vice-versa by
the CODEC circuit on the line card. A filter limits the bandwidth to
3400Hz. Speech sampling is performed at an 8KHz rate.
Test access
A relay on the line card allows testing to be performed on the loop as well as
towards the central office equipment side.
Loop loss control
To meet the requirements of the appropriate Telephone Administration
Transmission Plan Objective, pads under software control can be switched
in. This permits up to 7dB of loss in 1dB steps to be inserted in the outgoing
speech path (digital to analog).
50 hz or 60 hz filtering
The transmit side (analog to digital) of the line circuit provides for 50Hz ac
induction filtering. Longitudinal induction of up to 20 ma per conductor can
be tolerated by the line circuit. In a line connection, the response at 50Hz is
at least 20dB down from the reference frequency level.
Loop supervision
The loop supervision circuitry monitors the line for on-hook/off-hook status.
This information is passed to the appropriate peripheral processor and action
is taken accordingly.

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–77

This circuitry is also used to detect the changes in state of the loop that occur
during DP dialing.
Dialing
A station can have the dialing option of dial pulse (DP) or DTMF. For
DTMF, the tones are received by the line circuit and transmitted to the
DTMF receiver for digit detection and recognition.
Figure 6–10xxx
International Line Circuit – Type A
FW-31149

Line drawer Line card

Cutover To +15V
hold line Diode
To other LC in LD R1 – +
CO TA RG

Relay control Relay

Cutover circuit driver
To subscriber
Hybrid loop via MDF
transformer
Line Loss Transmission
circuit control thickfilm C0 A
chip
Transmit
Bidirectional bus
C1

2.56 MHz (total) Receive

clock C0 B

R2
To XPCM –48V
Flux balance winding
–48V
X R3
Ring mux on bus
RG RG TA
interface card
X X X
Ring trip
Supervision
Supervision data network Test
access bus

DMS-100 International Technical Specification BCS40i and up

6–78 Interfaces and signaling

Figure 6–11xxx
International line circuit – Type B
FW-31150

Line drawer Line card

Cutover To +15V
hold line Diode
To other LC in LD R1 – +
CO TA RG

Relay control Relay

Cutover circuit driver
To subscriber
Hybrid loop via MDF
transformer
Line Transmission
circuit thickfilm C0 A
chip Transmit
Bidirectional bus
C1

2.56 MHz (total) Receive

clock C0 B

R2
To XPCM –48V
Flux balance winding
–48V
X R3
Ring mux on bus
RG RG TA
interface card
X X X
Ring trip
Supervision
To other LC Supervision data network Test
access bus
Meter bus Metering
Tone bus pulse generator

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–79

Subscriber line signaling

Supervisory states
Idle line
The subscriber’s line interface in the CO provides balanced DC feed
resistance in each of the tip and ring lead towards the line. At the CO, a
high impedance balance detector is provided across these resistors for
sensing loop current.
Office battery, through one resistor, is applied on the ring (B-lead). Ground
through the other resistor is applied on the tip (A-lead).
Balanced components provide for 20 ma per conductor immunity to 50 Hz
or 60 Hz longitudinal AC induction.
During dialing
The line circuit on the DMS-100 International switch provides for detection
of DC loop currents of 18 mA or greater. This provides for 1900 ohms
external resistance, non-coin including subscriber’s instrument, allowing for
a minimum of 21 mA loop current. Under extreme battery conditions, for a
1900 ohms loop, the system will supply a minimum of 18.1 mA loop
current. For coin lines, external loops of up to 1500 ohms can be used.
Open intervals during call processing
During addressing or while receiving rotary-dial or DTMF dialing
information, the DMS-100 International switch does not produce an open in
either the tip of ring leads. No open condition on the tip or ring is produced
after addressing or during call processing. Except for lines with cut-off on
disconnect option (COD), the switch does not open the tip and ring on
disconnect. With the COD line option, the tip and line is open for a period
of 500 ms on terminating call, when a disconnect signal from the calling end
is recognized. The COD option is assignable by the operating company.
Detection of line supervisory states
During seizure, dialing ring trip, talking
The line interface on the DMS-100 International switch recognizes loop
closure with a maximum external range, including subscriber set, of 1900
ohms. Within this range, a loop closure is recognized as an off-hook during
seizure, dialing, ring-trip, or talking.
During hold
After the network connection has been established, the DMS-100
International switch will hold the connection with a maximum external
resistance of 1900 ohms.
During disconnect
The DMS-100 International switch recognizes an on-hook disconnect state if
the current flowing in the customer’s loop drops below 8 mA.

DMS-100 International Technical Specification BCS40i and up

6–80 Interfaces and signaling

External resistance Line supervision

>18 mA hold
8 – 18 mA hold or disconnect
8 mA disconnect
Handling of abnormal line conditions
Open interval at permanent-signal time-out
The DMS-100 International switch applies a 10 second silent period to lines
as the first state in the permanent-signal time-out sequence. Lines that
remain permanently off-hook after office disconnect, or lines that are left in
the off-normal state after a service request, receive this treatment.
Address detection
The DMS-100 International switch terminates the voice path in the specified
impedance. If the station does not have deny origination option assigned to
it, the originating station receives dial tone when the switch is ready to
receive digits.
The switch is capable of receiving dial pulses from dial pulse lines and
dual-tone multifrequency (DTMF) lines. Lines assigned the DTMF option
accept both types of signals.
Rotary dial pulse detection
The DMS-100 International switch can detect dial pulses with pulsing
speeds between 7.5 and 12 pps with telephone dial breaks between 58 and
67.5% measured at the MDF. The dial pulse receiver can recognize
inter-digit times as short as 110 ms.

Dual-tone multifrequency (DTMF) detection

DTMF frequencies
The DMS-100 International switch recognizes the standard DTMF toneset,
as defined by CCITT recommendation Q.23. Table 6–12 lists the frequency
pairs which make up the DTMF dialing toneset.

Table 6–12xxx
DTMF dialing toneset
Nominal high group frequencies
Nominal low group 1209 hz 1336 hz 1477 hz 1633 hz
frequencies
697 hz 1 2 3 A
770 hz 4 5 6 B
852 hz 7 8 9 C
941 hz * 0 # D

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–81

Tone parameters such as signal level and companding law are

country-specific, and are defined in software by Northern Telecom based on
specifications supplied by the operating company. The tone parameters for a
particular country are specified by entering the appropriate value in field
TONESET of table LTCINV. The DTMF parameters make up part of the
downloadable software of the International Line Group Controller (ILGC),
and are stored in RAM on the NT6X69LA card in the ILGC.
DTMF reception
The DTMF telephone station oscillator is supplied a negative battery
connected to the ring (B-lead) of the line during the time pulses can be
expected to be initiated.
DTMF reception in DMS-100 International switches is performed by the
universal tone receiver (UTR). DTMF reception will not interfere with the
reception of dial pulses or other dc signals. When receiving DTMF digits
the line impedance termination satisfies the voice grade transmission
parameters. DTMF reception characteristics comply with CCITT
recommendation Q.24 and meet the criteria shown in table 6–13.

Table 6–13xxx
DTMF reception parameters
Parameter accepts digits rejects digits
frequency tolerance greater than 1.5% (each no total rejection (each
frequency) frequency)
signal duration greater than or equal to less than or equal to 22
44 ms ON ms ON
input level (900 ohm 0 to –27 dBm (per less than or equal to –29
termination) frequency) dBm (per
frequency)
twist –10 to +4 dB greater than or equal to
(high to low) 16 dB (high to low)

These parameters are subject to the following:

• Frequency tolerance greater than 1.5% of each frequency may or may
not register as a valid frequency.
• Input levels between –27 dBm and –32 dBm per frequency may or may
not register as a valid level.
• Twist levels between –10 dB and –16 dB, and between +4 dB and +15
dB high frequency to low frequency may or may not register as
acceptable twist.

DMS-100 International Technical Specification BCS40i and up

6–82 Interfaces and signaling

Tolerance to echo
The DTMF receiver will operate accurately during the presence of signal
echoes which are delayed to 20 ms and reduce in level by at least 10 dB with
respect to the incident signal.

Subscriber premise meters

Subscribers requiring metering on their premises receive 12 or 16 KHz
meter pulses on answer and thereafter, according to the rate structure for
metered calls, until the conversation is terminated.
This applies to both local and long distance calls with no restrictions.

Ringing
Ringing source
The ringing source consists of an AC ringing generator supply that
effectively produces AC superimposed on DC. The ringing source removes
the ringing voltage applied to line at the AC zero crossing point.
During the silent period, office battery supply (–52V nominal) is applied on
the ring-side of the line.
The AC ringing voltage is applied on –52V battery. This is not the talk
battery.
The ringing waveform is sinusoidal with peak-to-rms voltage ratio between
1.35 and 1.45.
The ring-trip function is performed for external loops up to 1900 ohms.
The ringing range, including the telephone set, is as follows:
• –3 bridged –1900 ohms
• –5 bridged 1300 ohms
Audible ring tone
Audible ring tone is sent to the calling party when the called party is alerted
by means of ringing voltage being applied to the line. The tone has a duty
cycle similar to that of the ringing voltage and is not synchronized to the
duty cycle of the called party ringing voltage.
Ring trip
When the called party goes off-hook, the DMS-100 International switch
recognizes the change-of-state and removes ringing voltage from the line. It
also removes audible ring tone from the calling party line.

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–83

Coin line signaling

Two types of coin line signaling are supported:
• battery reversal operation: The switch sends a simple battery reversal on
answer. Periodic metering is not supported for this type of coin line
operation.
• 12 or 16 KHz operation: The switch sends a 12/16 KHz pulse an answer
and then periodic 12/16 KHz pulses thereafter at a frequency determined
by the rate structure for metered calls.
Private branch exchange (PBX) line signaling
Three types of PBX line signaling are supported:
• loop-start, with no additional control signals, using the NT6X93 line
card. The switch treats the line as a normal subscriber line with the
exception of hunt group operation.
• battery reversal on answer, using the NT6X94 line card. No additional
signaling is permitted between the PBX and the switch.
• 12 or 16 KHz operation, using the NT6X94 line card. Meter pulses are
applied to the PBX on answer and thereafter according to the rate
structure on metered calls.

Subscriber line maintenance

This section briefly describes the test interface provided on the line circuits.
The overall maintenance capabilities of the DMS-100 International switch
are described in chapter 10 of this book. For detailed information on
maintaining subscriber lines, refer to the Lines Maintenance Guide,
297-1001-594.

Subscriber line test circuits

The test circuits within the line card are activated by coded control signals.
Depending on the code, signals are sent to the relay drivers which operate
the test access relay (TA) or the cut-off Relay (CO), or the signals are used
to activate test circuits within the access chip itself.
Test access (TA)
The TA relay on the line card provides metallic contact with the subscriber’s
analog line and the VF transformer. With TA and CO relays operated,
contacts of TA are closed and those of CO are open. This isolates the
subscriber loop from the LC card, and enables subscriber loop tests to be
applied via the TA to the T and R leads. With only the TA relay operated,
the TA provides bridged monitor access to the subscriber’s T and R leads
and the VF transformer.
Cut-over control
The cut-off relay (CO) also provides a facility for software-controlled
cut-over. For cut-over, the cut-over hold line is grounded via a common

DMS-100 International Technical Specification BCS40i and up

6–84 Interfaces and signaling

cut-over circuit in the line drawer (LD). Once operated, sufficient current
flows through the CO relay from the cut-over hold line so that all operated
CO relays in the line cards remain operated. This opens the CO contacts,
thus isolating the tip and ring leads of the addressed line circuit from their
connections to the main distribution frame (MDF). At cut-over time, the
ground on the cut-over hold line is removed, opening the hold current path
for all CO relays in the line drawer. Any CO relay which has previously
been set to the cut-off state will then be released. This simultaneously
connects the tip and ring leads of any selected number of LC cards to their
associated MDF connections.
Analog loop-around
With relay CO only operated, the T and R leads are isolated and the VF
transformer is unbalanced enabling VF signals on the “receive” path to
appear on the “transmit” path with almost zero loss. The analog
loop-around consists of a VF signal in digital form from a test signal
generator. After conversion to analog, the test signal crosses to the
“transmit” path, is converted back to digital, and returns to the test
equipment. By comparison of the input and output signals, the condition of
the “transmit” and “receive” circuits can be tested.
Digital loop-around
A special eight-bit test pattern is transmitted and received through an
established digital path to check the integrity of the digital connection in the
line circuit.
Metallic test access (MTA)
The metallic test access unit (NT2X46AB) provides a metallic DC
connection between test circuits and line circuits in the ILCMs. The MTA
unit is frame mounted and is usually located on a miscellaneous equipment
frame. The MTA unit functions in conjunction with the NT3X50 driver card
as part of the line maintenance facility for DMS-100.
The MTA unit provides access for up to 10 ILCMs, up to 16 test circuits,
and a two-wire switched path. It interfaces with the MDF, ILCM, and the
driver card located in a maintenance trunk module (MTM). The test circuits
are connected to the MTA appearances at the MDF. The ILCM and the
driver card are connected directly to the MTA unit.
The MTA unit provides a 16 x 20 two-wire switching matrix, which can be
expanded by connecting additional MTA units. Each MTA unit has 20
two-wire appearances on the vertical side of the matrix, and can serve up to
10 ILCMs. Rules for provisioning additional MTA units are described in
DMS-100 Family Provisioning, 297–1001–450.

PLN-5001-001i Standard 02.02 April 1997

 Interfaces and signaling 6–85

Data communication interface (X.25, V.35)

The DMS-100 International switch supports data communication
connectivity using the NT1X89 multiprotocol controller card (MPC), which
resides in an input/output controller (IOC) shelf. The MPC to modem link
supports X.25, BX.25 and asynchronous data communication protocols.
The X.25 protocol used by the MPC complies with the X.25 model specified
by the CCITT in standards ISO 7776 and ISO 8208.
The MPC supports network communications via RS232 links, at a maximum
transmission rate of 19.2 kbits/second. The enhanced MPC (NT1X89BA)
also supports a 56/64 kbits/second V.35 link.
For additional information on MPC applications, signaling, and
provisioning, refer to the Multiprotocol Controller Product Guide,
297-1001-015.

DMS-100 International Technical Specification BCS40i and up

 7–1

Administration
This section describes the administrative and operational aspects of
DMS-100 International switches:
• data recording
• International Centralized Automatic Message Accounting (ICAMA)
system
• operational measurements (OM)
• network management
• database management
• database facilities and structures
• service analysis
• fraud prevention features

All administrative functions in DMS-100 International switching systems

are carried out from a Maintenance and Administration Position (MAP).
One or several MAPs can be profiled to serve all the administrative
functions, or a dedicated MAP can be configured to serve one specific
administrative function depending on operating company needs.
A complete description of a MAP position can be found in chapter 10,
“Maintenance”.
Data recording
Data for ICAMA, Station Message Detail Recording (SMDR), OMs, journal
file (JF) and others can be automatically recorded on the System Load
Module disk drives, nine-track magnetic tape or Winchester type disk drives.
The management of data traffic to and from the hardware devices is
performed by a software subsystem called DIRP (Device Independent
Recording Package).
Each DMS-100 International installation is configured for automatic data
recording using two data tables: DIRPSSYS and DIRPPOOL. The
DIRPSSYS data table provides a list of recognized subsystems, such as
AMA, OM, and JF, which record their data on either tape or disk files. This
data table also provides additional operational information such as the
number of open files and the alarm conditions for each subsystem. The

DMS-100 International Technical Specification BCS40i and up

7–2 Administration

DIRPPOOL data table defines the groups of recording devices, the type of
devices (tape or disk), and the recording volume identifications.
The system performs three scheduled software audits. The device audit
checks the physical recording device every five minutes to verify that it is
ready to receive data. The subsystem audit verifies the integrity of the
device files and their configurations every 60 minutes. With disk operation,
the disk daily audit performs a detailed audit of all disk files, verifying their
status and updating the same as required. The tape daily audit performs
tasks such as checking for free tapes and rewinding parallel tape files. Both
daily audits run at a preset time each morning. For more information see
Device Independent Recording Package Product Guide, 297-1001-013.
Under normal operation, the subsystem files are maintained in the “open”
state, ready to accept data. If two or more files are assigned to a specific
subsystem, then active and standby status is assigned to the files, and
periodic rotation of recording duty occurs. A maximum of three standby
files can be specified for any subsystem. In addition to the active and
standby files, a parallel file can be set up as a backup to record all data
output by a subsystem. For more information see Device Independent
Recording Package User Guide, 297-1001-312 and figure 7–1.
Figure 7–1xxx
Data recording

System software Control Facilities

ICAMA

Disk

ICR – International call

recording Device
independent
recording XFR Poller
package
OM – Operational measurements (DIRP)

LCDR – Local call detail Mag

recording tape

JF – Journal file

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–3

Magnetic tape
The characteristics of the recording format for magnetic tapes are covered
by the Magnetic Tape Users Guide, 297-1001-118, and are outlined in this
section. Magnetic tapes can be used by DMS-100 Family switching systems
to store data for seven applications:
• Automatic Message Accounting (AMA)
• Operational Measurements (OM)
• Office Image (for system backup)
• Trouble Diagnostic Data
• Call Detail Recording (CDR) records for local calls
• Customer Data Modification (CDM)
• Office Data Modification.

Magnetic tape recording characteristics

The ICAMA recording system accepts magnetic tapes with these
characteristics:
• Tracks: nine-track format
• Recording Density: 1600 CPI (BPI)
• Recording Technique: Phase-Encoded
• Tape Character (Byte): eight bits of data plus one parity bit (odd parity)
• Block size (Physical Block): between 18 and 2048 tape characters
arranged in accordance with the American National Standards Institute
(ANSI) recording format for magnetic tape.
Block arrangement The DMS-100 machine accepts a nine-track tape
recording using phase encoding, at a density of 1600 characters per inch
(CPI) or bytes per inch (BPI) with odd parity. Data is recorded on tape with
the American National Standards Institute (ANSI) recording format. This
format consists of a density identification area, an initial gap, preambles,
blocks of data of variable length, postambles, and strategically placed
interblock gaps and tape marks:
• BOT (Beginning of Tape) Marker: A BOT marker is a reflective strip
which marks the beginning of the permissible recording area. The tape
is positioned by the system at the leading edge of the BOT marker after
being manually loaded.
• Identification Burst (Density Identification Area): An identification
burst is a pattern of flux changes on one track only and identifies the tape
as being phase-encoded when it is loaded onto a dual-density tape drive.
• Initial Gap: An initial gap is the portion of the tape which is between
the trailing edge of the BOT marker and the first block of data (volume
label).

DMS-100 International Technical Specification BCS40i and up

7–4 Administration

• Interblock Gap (IBG): An interblock gap is a portion of the tape which

has no flux changes. An interblock gap is 0.6 inch (1.5 cm) in length
and is used to separate the identification burst, blocks of data and
tapemarks.
• Preamble: A preamble precedes the actual data in a block. It consists of
a sequence of 40 zeros in each track followed by a binary one in each of
these same tracks. The zeros synchronize clocks, and the binary ones
signal the beginning of the data.
• Block: A block is a group of related data of between 18 to 2048 tape
characters. A block can contain one or more records.
• Postamble: A postamble follows the actual data in a block and is a
sequence consisting of a binary one in each track followed by 40 zeros in
each of these same tracks. It is a mirror-image of the preamble.
• Tape Mark: A tape mark is a special control block having a pattern of
flux changes in six out of nine tracks and is 40 characters in length. It is
used to separate data sets from label groups.
• Data Set: A data set can contain one or more records which are
organized into blocks in various formats, as described in Magnetic Tape
Reference Manual, 297-1001-118.
• EOT (End of Tape) Marker (not shown in figure 7–2): An EOT
marker is a reflective strip located about 25 feet (7.6 m) from the end of
the tape. It indicates the end of the normal permissible recording area.
In some instances, (that is, the block being written), data may be written
beyond the marker. Emergency transfer entry occurs when the EOT
marker is detected. See Automatic Message Accounting–Northern
Telecom Format, 297-1001-119 for a description of tape transfer and
entry.
The functions for various parts of the recording format are shown in
figure 7–2.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–5

Figure 7–2xxx
Magnetic tape recording format

Density

GAP 1.0
identification
IBG .6

IBG .6

IBG .6

IBG .6

IBG .6
Data Data Data area
block block block Initial gap 2.425
3.0

18–2048 18–2048 18–204 2.4

ch ch 8 ch
(i.e. (i.e. (i.e.
Posamble 41 ch

Posamble 41 ch

Posamble 41 ch
Tapemark 40 ch

Preamble 41 ch

Preamble 41 ch

Preamble 41 ch
header header volume
1 1 label–8
label–80 label–80 0 ch) 9-track
ch) ch) magnetic
BOT marker tape

Identification
Dataset A

burst 4.825

Forward tape motion

Starting position
1-ch = 9 bits (across of
tape) write head when
(1 bit per track) tape is positioned
to leading edge of
Note 1 : All dimensions are given in inches BOT marker
Note 2 : Tape is shown oxide side up, read/write head on same side as oxide
Note 3 : Tape to be fully saturated in the erased direction in the inter-block
gape and the initial gape
Legend: Note 4 : There is a track placement tolerance + 0.003 inch ( 0.007 mm) for
BOT: Beginning of tape each track
Ch: Characters Note 5 : For clarity, no flux changes are represented
IBG: Inter-block gap Note 6 : Format based on ANSI

Volume organization Data can be stored on tape as:

• A single data set on a single volume
• A single data set on multiple volumes
• Multiple data sets on a single volume
• Multiple data sets on multiple volumes

DMS-100 International Technical Specification BCS40i and up

7–6 Administration

IBM standard labels

The volumes (and the data sets of file(s) they contain) are identified by
labels as a basis for efficient processing. DMS-100 Family systems use IBM
Standard Labels (See OS/VS Tape Labels) for this purpose.
The IBM standard label that identifies the volume and its owner is the
Volume Label (VOL1).
The IBM standard labels identify and describe the data set:
• Header Labels (HDR1, HDR2)
• User Header Labels (UHL1) (Bellcore AMA format)
• Trailer Labels (EOF1, EOF2)
• User Trailer Labels (UTL1) (Bellcore AMA format)

As shown in figures 7–3 and 7–4, these labels are referred to collectively as
the header label group or the trailer label group.
The tape mark, which acts as a delimiter or separator, follows both label
groups, (header and trailer) and each data set. Two tape marks follow the
trailer label group to indicate that the end of the last data set on the volume
has been reached.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–7

Figure 7–3xxx
Label organization for a single data set on a single volume

Beginning of tape

Vol 1 Volume label

Hdr 1

Hdr 2
Header label group
UTL 1
...

UTL 8

Tapemark

Data set A

Tapemark

EOF 1

EOF 2
Trailer label group
UTL 1
...

UTL 8

Tapemark
Tapemark

End of tape
Note: Shaded labels are optional

DMS-100 International Technical Specification BCS40i and up

7–8 Administration

Figure 7–4xxx
Label organization for multiple data sets on a single volume

Beginning of tape

Vol 1 Volume label

Hdr 1
Hdr 2
UTL 1 Header label group

...
UTL 8

Data set A

Tapemark
EOF 1
EOF 2
UTL 1 Trailer label group
...

UTL 8
Tapemark
Hdr 1
Hdr 2
UTL 1 Header label group
...

UTL 8
Tapemark

Data set B

EOF 1
EOF 2
UTL 1 Trailer label group
...

UTL 8
Tapemark
Tapemark
End of tape
Note: Shaded labels are optional

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–9

Coding of IBM standard labels All labels are recorded in Extended

Binary-Coded Decimal Interchange Code (EBCDIC) and written as 80-byte
(80 tape characters) blocks. The first four bytes always correspond to the
label identifier itself (for example, VOL1 or HDR1). The contents of the
remaining 76 bytes of each block differ according to the label, as covered by
Magnetic Tape Reference Manual, 297-1001-118.
Volume label (VOL1) The volume label is the first record on the volume
and is identified by VOL1. It contains the volume serial number and the
name of the volume owner.
Header label 1 (HDR1) The (data set) Header Label 1 precedes the data
set and is identified by HDR1:
• Data set name
• Data set serial number
• Data set volume sequence number (for single data set/multiple volume
situations)
• Data set sequence number (for multiple data sets/single volume
situations)
• Generation number (for generation data set groups)
• Version number (for generation data set groups)
• Creation date
• Expiration date
• Data security code
• Block count
• System code
Header label 2 (HDR2) The (data set) Header Label 2 immediately
follows the HDR1 label and is identified by HDR2:
• Record format of the data set
• Block length
• Record length
• Tape density
• System ID
• Tape recording technique
• Block attribute
User header labels (Bellcore AMA format) Optionally, a maximum of
eight user header labels can appear immediately following HDR and are
identified by UHL1 to UHL8. These labels contain user-assigned
information about the data set.

DMS-100 International Technical Specification BCS40i and up

7–10 Administration

End-of-file label (EOF1) The End-of-File Label 1 follows the data set
indicating that the end of the data set has been reached. It is identified by
EOF1 and contains identical information to the HDR1 label, except for the
label identifier and the block count.
End-of-file label 2 (EOF2) The End-of-File Label 2 immediately follows
EOF1 and is identified by EOF2. It contains identical information to the
HDR2 label, except for the label identifier.
User trailer labels (Bellcore AMA format) (UTL) Optionally, a
maximum of eight user trailer labels can appear immediately following
EOF2, and are identified by UTL1 to UTL8. These labels contain
user-assigned information about the data set.
Data set logical record formats
A data set is composed of a number of logical records which are organized
into fixed or variable-length blocks with the former being most used for
DMS-100 Family System data sets.
Blocking is the process of grouping a number of logical records as a
physical block. A block is made up of the data records between the
inter-block gaps and may be 18 to 2048 tape characters (bytes) in length.
Blocking allows efficient utilization of storage space by reducing the
number of interblock gaps in the data set. Blocking also reduces processing
time because fewer input/output operations are required to process entire
blocks of records when the records fit into the fixed length format applies.
When a variable length record exceeds the physical block size, it will be
written into the next block.
The OM and LOG datasets are encoded in EBCDIC (with the character set
as defined by the IBM standard PN print train for 1403 and 1404 printers).
The NT standard AMA and Bellcore AMA data sets are encoded in Binary
Coded Decimal (BCD) four-bit code, the details of which are found in
Automatic Message Accounting–Northern Telecom Format, 297-1001-119.
In the Bellcore format, the AMA data is recorded in signed packed decimal
with hexadecimal identifiers.
Disk
Disk Drive Units (DDUs) for DMS-100 NT40 offices are 14-inch
Winchester type drives which have capacities of 300 Mbytes. The DDU
consists of a disk drive and a NT1X78 power converter card installed on a
dedicated shelf on an I/O Equipment (IOE) frame. Associated with each
DDU is a NT1X55 disk drive controller card which occupies one card slot of
the IOC shelf, and which interfaces with the DDU and IOC. In NT40-based
offices, or in SuperNode-based offices with minimal SLM disk storage
space, the DDU serves as the primary mass storage device. A minimum of

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–11

one MTD is also required in NT40 offices to enable physical transportation

of data to and from the office.
In SuperNode offices, three types of system load module (SLM) are
available. The SLM is packaged as a single, replaceable unit that consists of
a 5.25-in. (13.3 cm) hard disk drive, a 0.25-in. (6.35 mm) streaming
cartridge tape drive with a removable cartridge, and a central processor
controller. The 9X44AA SLM1 unit has a hard disk capacity of 150Mb, and
a tape storage capacity of 75Mb. The 9X44AC SLM1A unit has a hard disk
capacity of 300Mb, and a tape storage capacity of 150Mb with the DC6150
cartridge, or 250Mb with the DC6250 cartridge. The 9X44AB SLMII unit
has a hard disk capacity of 600Mb, and a tape storage capacity of 150Mb
(DC6150 cartridge), or 250Mb (DC6250 cartridge).
An SLM is used to perform the following tasks:
• bootload the CM and the MS from disk or tape
• load an office image into the inactive CPU
• dump an image to disk
• perform offline transfers from tape to disk, or disk to tape

On SuperNode-based systems, when configured with feature package

NTXJ44AA, the SLM disks can also be used by the device independent
recording package (DIRP) as an alternative to the I/O controller (IOC) for
recording DMS subsystem data.
Disk drives are typically configured for these files:
• AMA Billing
• Operational Measurements
• Office Image – backup
• Peripheral Software Loads
• Journal File
• Pending Order File (POF)
• Non-Resident Programs
• User Files.

For additional information, please refer to Disk Maintenance Subsystem

Reference Manual, 297-1001-526.

DMS-100 International Technical Specification BCS40i and up

7–12 Administration

Disk files Storage space on a disk is allotted on the basis of volumes and
files. Once the volumes have been defined they are considered as separate
entities by the system. After files are created within the volumes, the data is
stored wherever space is available within the confines of the volume. This is
a system task and is transparent to the user.
Each data file is a collection of segments within a volume with each segment
representing 512 blocks of 1 K DIRP bytes each. The block is the smallest
DIRP addressable unit (also equals 256 2 K DIRP blocks) and constitutes a
disk sector.
AMA and OM recording The storage of AMA and OM data on disk can
be very cost effective. The primary advantage of disk over tape is the
reduction of the number of recording devices, for example, from four to six
MTUs per office, to the one MTU-two disk combination. This advantage is
gained through the random access characteristics of disk which enables the
storing and accessing of many separate files simultaneously on one drive
(see Device Independent Recording Package User Guide, 297-1001-312.)
Depending on the size of the AMA and OM files, (and drives and volumes
allowed to DIRP) it is possible to store many days of AMA data, OM data,
journal file, as well as the office image on one disk, while the other one can
be the duplicate backup. On a daily basis, the most recent AMA file can
then be image copied to tape, and transported to the processing center. The
maximum DIRP backup is 24 volumes of 64 megabytes each for a total of
1563 Mb/stream.
Security features provided primarily for AMA files include dual recording
of data, sanity checks of file deletion commands, and activation of alarms if
a disk space minimum threshold is reached.
Office image – backup The disk can also be used for office image
storage and bootstrap loading. With the recommended dual disk
configuration, one or more office images can be stored on both disks. Since
data transfer speed from disk is much faster than from tape, loading and
dumping of the office image will be faster. Peripheral Module loads can
also be stored on the same disk.
Normally the office images are set up as a particular disk volume as an
archive or a set of images with the most recent being available for backup
(current image file). Multiple images may be stored on disk and/or tape,
with a route list defining the order in which the images are accessed.
Journal file (JF) This file contains records of all DMOs entered, allowing
automatic re-activation if data tables are inadvertently destroyed. Even
though this file is not large, it is normally active, therefore requiring a
dedicated tape drive. Disk residence will free up the tape drive, and allow
instant activation in an emergency.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–13

Pending order file (POF) The POF is used to store service orders, rating
changes and office configuration changes for later activation. Although this
file is normally small, occasional block-cut change procedures may require a
much increased storage capability. Disk resident POF allows larger volumes
of DMOs to be entered further in advance of their scheduled
implementation.
Non-resident programs and user files As well as storing non-resident
maintenance programs, the disk can be utilized to store other programs and
data of a non time-critical nature. This further facilitates remote
maintenance and administration of offices, and reduces the requirements for
memory cards.
Data polling
Remote data polling of OM and/or AMA information
The remote data polling system permits the telephone company to transfer
OM, AMA, and JF DIRP data of a DMS-100 family office to a data
processing center. This data is stored on a disk or a magnetic tape and,
through the Device Independent Recording Package (DIRP), the data is
made available to the remote data polling system which transmits it to the
data center. The data is transferred using a version of the CCITT X.25 for
data communication protocol.
Dedicated cards can be established separately or jointly for OM and AMA
polling. The DMS-100 interface consists of an NT1X89 Multi-Protocol
control card and an EIA RS-232-C interface to a modem.
When setting up the connection via the data packet switching network the
data network (DNA) address of the host collector is verified by comparing it
to the authorized list of users in data table XFERADDR (see Customer Data
Schema, 297-1001-451, “Section 045 Data Transferal System”). If the
address matches, access is made available.
The inventory of data record files to which the host collector has access are
listed in data table DIRPHOLD. Here the files are listed by type (such as,
originating subsystem AMA, or OM), file name, and location (volume serial
number). While file management is normally automatic, manual override is
available. Files that have been requested and processed are denoted “aging”
and await automatic expiration and erasure (see Remote Data Polling System
Description and User Interface, 297-1001-524.)

Operational measurements (OM)

The OM system in the DMS-100 Family Systems provides the operating
company with raw performance data for the system. The data, when
processed by the operating company, provides information on system
performance, the grade of service being offered, connecting facilities, and
performance and traffic levels of various elements internal and external to

DMS-100 International Technical Specification BCS40i and up

7–14 Administration

the system. The measurement update and print schedules are operating
company defined, to provide the necessary flexibility to satisfy a wide
variation of operating company requirements.
Operational measurements system components and organization
The OM system monitors certain events in DMS-100 Family Systems and
enters the results into registers in the data store. Events are entered either
individually every time an event occurs, or scanned (sampled) at regular
intervals regardless of the time of occurrence of an event. Events measured
individually are referred to as peg counts, while sampled measurements
(states) used to determine the degree of usage of the system hardware and
software resources are called “usage counts.” The low (slow) scan is based
on 100 seconds per period and high (fast) scan is based on 10 seconds per
period.
A table of active measurements, with its associated holding and
accumulating register, is called a measurement group. All measurements in
the group have the same table name. Each table name is assigned a class
definition, that is, ACTIVE or HOLDING, indicating its status in the total
OM system. The group and class names are used to identify the OM in the
header sections of OM output reports and as parameters of command.
Data collection
The OM data in the active registers is useful only if related to the specific
period of time during which it was collected. OM data cannot be directly
copied from the active tables to an output process (tape, printer,
accumulation) because of the likelihood that another count may occur during
the copying process, thus introducing an unknown time period and causing
an inaccurate output.
Data is transferred (copied) from the active registers to a duplicate set of
registers classed as “holding” registers. Data copying from active to holding
registers normally occurs at 15 or 30 minute periods (or optionally at 5-, 10-,
15-, 20- or 30-minute periods), depending on the type of OM counts and the
active registers cleared to begin new counts for the next period.
The last three 5-minute period counts are stored in three sets of holding
registers and the last four 15-minute period counts are stored in four sets of
holding registers.
Copying to output processes is performed from the holding registers, with a
controlled time period on which to base subsequent data manipulation. The
holding registers isolate the output processes from the active OM data
inputs, lessening the urgency and priority of the output copying processes.
The contents of the holding registers are available for display or distribution
via the file system. The file system allocates the OM data output to the

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–15

appropriate devices, such as, teletypewriter (TTY) or Visual Display Unit

(VDU), or via DIRP for recording on disk or tape.
Data accumulation
When it is necessary to accumulate data over longer periods than the basic
period used for transfer of data from active to holding registers, additional
sets of registers (classed as “accumulating” registers, with a specific start
and stop time), are provided. The data from the holding registers is copied
onto the accumulating register at times for periods scheduled by the OM
management tables. Each set of holding or accumulating registers having
the same time characteristics is referred to as a measurement class
(measurement schedule).
The data accumulation process adds the contents of the holding class
registers to the accumulating class registers just prior to the next data
collection. The accumulated data is available until the end of the
accumulating period. The contents of the holding registers are also made
available, via the DMS-100, to associated devices such as the magnetic tape
unit or printer.
At the end of the accumulating period (scheduled by the OM management
tables), the total contents of the accumulating registers are distributed to
selected output devices, such as a printer, or recorded on tape or disk for
downstream organizations. After distribution of accumulated data, the
registers are reset to start the next accumulating period.
Batch change supplement monitoring (BCSMON) The Batch
Change Supplement (BCS) Monitoring feature provides data which may be
used for comparing the performance of BCS software releases in the same
office by manually comparing data obtained while the office is operating
with a new BCS release to that obtained from a previous BCS release. The
BCSMON feature provides system information:
• Counts of internal events in the operation of the switch (warm and cold
restarts)
• Counts of hardware and fixed items in an office (number of lines, trunks,
receivers and peripheral modules)
• System trap information.
• Counts of system restarts and downtime information.
• Various types of log reports output by the system.
For further information on BCSMON see Nonmenu Commands Reference
Manual, 297-1001-820.
OM management tables
The data acquired and entered into the OM data tables is managed by four
“management” tables which control the acquisition, collection, accumulation

DMS-100 International Technical Specification BCS40i and up

7–16 Administration

and distribution functions of the OM systems. The OM management tables

are named “OMTAPE” (for both tape and disk), “OMACC”, “OMPRT”, and
OMGRPORD (see Basic Administration Procedures, 297-1001-300).
Access to the four OM management tables, for purposes of display and/or
modification, is via the VDU, or other I/O device such as TTY. The VDU is
part of the MAP and interfaces with the OM tables through the Command
Interpreter (CI) or the table editor.
Commands to the OM system are entered via the CI from the VDU
keyboard, and responses to the commands are displayed on the VDU screen.
Authorized personnel can modify some fields of the OM management table
using the table editor commands and procedures.
The following description briefly covers the general principles of operation
of the OM management tables and the related office parameters:
OMTAPE This table contains values governing the measurement class,
timing and other parameters required when performing a data copy process
between a holding register and a designated tape, disk or any device
supported by DIRP.
OMACC This table contains values governing the timing of data copying
between holding registers and designated measurement classes of
accumulating registers. The commands OMCLASS (defining a new
measurement class), OMACCTAB (used to add or delete information on a
measurement class), and OMDUMP (used to display the groups and fields
belonging to a particular class), are used in conjunction with OMACC.
OMPRT This table contains values governing the measurements class,
timing and other parameters required when performing a data copy process
from a holding or accumulating register to an output printer. Output to a
printer is generated by using the facilities of the DMS-100 Family logging,
routing and reporting subsystem. The logging mechanism collects output
reports from all parts of the system, which are filed in order of a log report
number. OM reports are contained in the log OMPR, each report being
associated with specific printing devices. The key to table OMPRT relates
each row (tuple) to the log report number of the desired output in the log
OMPR. When the other values (measurement group, class, timing, etc.) are
entered into OMPRT, the output report is automatically routed, via the
routing and reporting subsystem, to the associated printer at the scheduled
times triggered by the key reference to the log report number.
OMGRPORD This table provides the operating company with the
capability to define the order of the OM group output within each OM
accumulating class by datafilling tables OMPRT and OMTAPE.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–17

Data structure of OM format

OM data consists of a set of uniquely named registers. Some registers are
provisioned on a “per office” basis. For example, a single register would
represent the total number of input/output system errors. The register is
called IOSYERR. Other registers are provisioned on a multiple basis. An
example would be the incoming call attempts for trunk groups, named
InCaTot. This register is provisioned one per trunk group and thus the
InCaTot stack is indexed by trunk group number.
An example of a typical grouping is the group of registers associated with
trunk group measurements. These registers are grouped in a tabular
structure, named TRK, which is illustrated in the table below. The columns
(fields) Common Language Location Identifier (CLLI) and Trunk Direction
(TrkDir) are not OM registers, but contain key and information values
associated with the TRK table structure. Each of the other fields, such as
Incoming Call Attempts or InCaTot, represents one of the OM registers in
the group and contains OM data. As shown in Table 7–1, each row (tuple)
represents one trunk group.

Table 7–1
Structure of typical OM data table
Trk (table name)

(Key field) MBU Trk Ncct InCa Pre Tru SBU

CLLI Dir Tot RteAb
Note: One row (tuple) per trunk group

NT standard format structure

The OM file structure consists of office parameter records containing
definitions of the records in the data section of the OM files, and data
records containing the actual counts of OM events in the holding or
accumulating registers. Each record contains one line of information which
varies in length depending on the type of record. The records are written in
numerical sequence as variable-length-blocked. Each record is assigned a
sequence number in the range 00000 to 65535.
OM scheduled output reports
The scheduled output records of the OM system can be routed to the
appropriate printing devices by the log system of the DMS-100 Family to
produce the printed output reports. The output can be scheduled by the
OMPRT table on an auto (normally 15 or 30 or optionally at 5, 10, 15, 20, or
30 minutes), half hourly, daily, weekly or monthly basis. Each entry in
OMPRT schedules a different output report. The output records are filed in
the OM log table (OMPR) in the sequence of report number (for example,
OMPR200 or OMPR201).

DMS-100 International Technical Specification BCS40i and up

7–18 Administration

OM reports can be output to disk or tape, or polled by compatible collectors.

An example of the Digital Trunk Controller (DTC) and Trunk Module (TM)
reports in machine printout format is shown in figure 7–5. The numeric data
values are printed after the header labels for the report.
Figure 7–5
DTC and TM reports

PM2 (DTC)

CLASS: ACTIVE
START: 1986/08/07 09:30:00 THUR; STOP: 1986/08/07 09:39:47 THUR;
SLOWSAMPLES: 5 ; FASTSAMPLES 57 ;

KEY (PM2_OMTYPE)
INFO (PM2_OMINFO)
PM2ERR PM2FLT PM2INITS PM2LOAD
PM2USBU PM2UMBU PM2MSBU PM2MMBU
PM2CXFR PM2ECXFR PM2CCTSB PM2CCTMB
PM2CCTFL PM2CCTER

TM

CLASS: ACTIVE

START: 1986/08/07 09:30:00 THUR; STOP: 1986/08/07 09:40:47 THUR;

SLOWSAMPLES: 6 ; FASTSAMPLES: 63 ;

TMERR TMFLT TMSBU TMMBU

TMCCTDG TMCCTFL TMMBP TMSBP
TMMBTCO TMSBTCO TMCCTOP

OM demand output reports

DMS-100 Family systems provide output reports at any time, for all the
operational measurements. These reports are routed to the appropriate
printing devices. Demand output reports are requested by means of the
input command “OMSHOW” and requesting the table, such as, TRK, and
the class, such as, holding or active. An example of the AMA demand
report is shown in figure 7–6. The numeric data values are printed after the
header labels for the report.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–19

Figure 7–6
AMA demand report

OMSHOW AMA HOLDING

AMA
START: l986/08/07 09:00:00 THUR; STOP l986/08/07 09:10:23 THUR;
SLOW SAMPLES 6; FAST SAMPLES 61;

AMAENT AMAENT2 AMAEMTR AMAFREE

AMAROUTE

Measurement blocks
The OM system in DMS-100 Family systems provide the operating
company with performance data for the switch. The general requirements of
the operational measurements are divided into categories which include
accuracy, integrity, security, documentation, report format, and report input
and output capabilities.
Measurement accuracy
The design objective of the DMS-100 Family operational measurements
system is to register peg counts for l00 percent of all detected events.
Measurements that overflow are detected by the system and pegged by the
“overflow” registers provided.
Measurement integrity
Measurements stored within the switching system are protected from
inappropriate modifications by the switching system. The operational
measurements are not reset by warm or cold system restarts.
Measurement security
The design of the DMS-100 Family operational measurements system
ensures that the measurements stored within the switching system are
protected from manual modification.
Measurement documentation
A partial list of operational measurement tables provided in DMS-100
International switches is outlined in table 7–2.

DMS-100 International Technical Specification BCS40i and up

7–20 Administration

Measurement format
Measurement data is output to VDUs and printers in decimal digits.
Measurement report input and output capabilities
The measurement reports can be available at the local or remote locations.
Reports in DMS-100 Family systems are provided on a scheduled or
demand basis.
International OM overview
The following OM groups are defined in DMS-100 International offices. A
summary of each OM group follows.

Table 7–2xxx
DMS-100 International OM groups

OM group Group name

AMA Automated Message Accounting Summary

ANN Recorded Announcements
CF3P Three Port Conference Circuit Application
CF6P Six Port Conference Bridge Measurement
CM Computing Module (SuperNode or SNSE only)
CMC Central Message Controller Maintenance Summary
CP Call Processing
CP2 Call Processing (2)
CPU Central Processor Unit Maintenance Summary
CSL Console Device Maintenance Summary
DCM Digital Carrier Module Maintenance Summary

DDU Disk Drive Unit File and Maintenance Work

DS1CARR Digital Carrier Maintenance Summary

DTSR Dialtone Speed Recording

DTSRPM Dialtone Speed Recording for Peripheral Modules

EXT Extension
FTRQ Feature Queuing Software Resource
HUNT Hunt group Performance
IADL International Abbreviated Dialling
—continued—

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–21

OM group Group name

ICDIVF International Call Diversion Fixed

ICDIVP International Call Diversion Programmable
ICONF International Conference Features
ICWT International Call Waiting
IDND International Do Not Disturb
IFDL International Fixed Destination Line
ILR International Line Restrictions
INDC International No Double Connect
IOC Input-Output Controller Maintenance Summary
IOSYS Input-Output System
IWUC International Wakeup Call
LM Line Module
LMD Local and Remote Line Module Traffic
LOGS Log Messages
MACHACT Machine Activity Group
MS Message Switch (SN and SNSE only)
MSCHAIN Message Switch Chain (SN and SNSE only)
MSCHNLK Message Switch Channelized Link (SN and SNSE only)
MTA Metallic Test Access
MTRERR Call Metering Error Counts Group
MTRUSG Call Metering Usage Group
MTRPRF Call Metering Performance Group
MTU Magnetic Tape Unit Maintenance Summary
NMC Network Message Controller Maintenance Summary
NWMTGCNT Network Management Trunk Group Counts
OFZ Office Traffic Summary
OFZ2 Office Traffic Summary (2)
OTS Office Traffic Summary
PCMCARR CCITT DS30 Digital Carrier Maintenance Summary
—continued—

DMS-100 International Technical Specification BCS40i and up

7–22 Administration

OM group Group name

PM Peripheral Module Maintenance

PMOVLD Peripheral Module Overload Controls

PMTYP Peripheral Module Maintenance Summary Subtotals

PM1 Single Unit Peripheral
PM2 Peripheral Module Maintenance Summary
RADR Receiver Attachment Delay Recorder
RCVR Receiver Service Circuits
SOTS Supplementary Office Traffic Summary
SPC Semi-Permanent Connections
STN Special Tones Traffic
SVCT Special Service Circuits
SYSPERF System Performance
TFCANA Traffic Separation / Traffic Analysis Group
TM Trunk Module Maintenance Summary
TONES Tones Group
TRK Trunk Group OM Group
TRMTCM Treatments, Customer Miscellaneous
TRMTCU Treatments, Customer Unauthorized
TRMTCU2 Treatments, Customer Unauthorized (2)
TRMTER Treatments, Equipment Related
TRMTFR Treatments, Feature Related
TRMTRS Treatments, Resource Shortage
TROUBLEQ System Referred Line Diagnostics Queue
TS Time Switch Group
UTR Universal Tone Receivers, International application
End

AMA
This group is currently not used by International.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–23

ANN
This OM group measures the usage of recorded announcements. Each
announcement (for example, BLKDN and PSPD) has its own set of pegs.
The key to the group is the announcement CLLI. ANN has one INFO field
and 5 usage fields:
ANN_OMINFO
Displays the maximum number of calls which can be simultaneously
attached to the group.
ANNATT
Displays the number of calls routed to the group.
ANNOVFL
Displays the number of calls routed but not connected due to the maximum
allowable groups already reached, or to the group being maintenance-busy.
ANNTRU
Usage count of calls connected to the group. Scan rate is 100 second.
ANNSBU
Usage count of the number of equipped tracks which are in tk_system_busy,
tk_pm_busy or tk_deloaded state. Scan rate is 100 second.
ANNMBU
Usage count of the number of equipped tracks which are in tk_man_busy or
tk_seized state. Scan rate is 100 second.
CF3P
This OM group measures the usage of 3-port conference circuits. The key to
the group is the CLLI – CF3P. CF3P has one info field and 8 usage fields:
CONF_OM_INFO
Displays the number of software equipped conference ports.
CNFSZRST
The number of times a circuit has been assigned (excluding ITOPS
requests).
CNFOVFLT
Displays the number of times non-ITOPS requests could not be satisfied
because all remaining idle circuits have been assigned to ITOPS.
CNFQOCCT
Usage count of the number of requests waiting in the queue for a circuit.
Scan rate is 10 second.

DMS-100 International Technical Specification BCS40i and up

7–24 Administration

CNFQOVFT
Displays the number of requests rejected because the waiting queue is full.
CNFQABNT.
Displays the number of requests in the waiting queue abandoned.
CNFTRUT
Usage counts of the number of conference circuits in tk_cp_busy,
tk_cp_busy_deload and tk_lockout states. Scan rate is 10 second.
CNFSBUT
Usage counts of the number of conference circuits in tk_remote_busy,
tk_pm_busy, tk_system_busy, tk_carrier_fail and tk_deloaded states. Scan
rate is 10 second.
CNFMBUT
Usage counts of the number of conference circuits in tk_man_busy,
tk_seized and tk_nwm_busy.
CF6P
This OM group measures the usage of 6-port conference circuits. The key to
the group is the CLLI – CF6P. There is one info field and 8 usage fields:
CONF6_OM_INFO
Displays the number of software equipped conference ports.
CNF6SZRS
The number of times a circuit has been assigned (excluding ITOPS
requests).
CNF6OVFL
Displays the number of times non-ITOPS requests could not be satisfied
because all remaining idle circuits have been assigned to ITOPS.
CNF6QOCC
Usage count of the number of requests waiting in the queue for a circuit.
Scan rate is 10 second.
CNF6OVFL
Displays the number of requests rejected because the waiting queue is full.
CNF6QABAN
Displays the number of requests in the waiting queue abandoned.
CNF6TRU
Usage counts of the number of conference circuits in tk_cp_busy,
tk_cp_busy_deload and tk_lockout states. Scan rate is 10 second.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–25

CNF6SBU
Usage counts of the number of conference circuits in tk_remote_busy,
tk_pm_busy, tk_system_busy, tk_carrier_fail and tk_deloaded states. Scan
rate is 10 second.
CNF6MBU
Usage counts of the number of conference circuits in tk_man_busy,
tk_seized and tk_nwm_busy. If all 6-port conference circuits have been
configured as two 3-port conference circuits, all pegging will be against the
CF3P OM group.
CMC
This OM group measures the performance of the Central Message Controller
The key to this group is either CMC0 or CMC1. CMC has 8 fields:
CMCLERR
The number of errors detected in the functioning of a CMC link to a network
module or I/O controller.
CMCERR
The number of errors detected in the functioning of a CMC or its associated
clock.
CMCFLT
The number of error events from which the CMC or its associated clock
could not recover. This register is incremented before the system tries to
recover the CMC; if the system can recover then the event is removed from
this register and will increment either CMCLERR or CMCERR.
CMCDIAG
The number of system-called diagnostics, that is the total of CMCLERR,
CMCERR and CMCFLT.
CMCLKSBU
Usage Count of the number of peripheral CMC message links in
system-busy state. Scan rate is 100 second.
CMCLKMBU
Usage Count of the number of peripheral CMC message links in man-busy
state. Scan rate is 100 second.
CMCSBU
Usage count of the amount of time the CMC itself is in system-busy state,
due to failure of the CMC or its associated clock. Scan rate is 100 second.

DMS-100 International Technical Specification BCS40i and up

7–26 Administration

CMCMBU
Usage count of the amount of time the CMC itself is in man-busy state as a
result of commands from an authorized map. Scan rate is 100 second.
CP
This OM group measures the usage of call processing. CP has five info
fields and 31 usage fields:
CPOINFOX
There are five info fields. The first always has a value of zero. The
remaining four give the provisioned number of CP letters, wakeup blocks,
CP (call processes) and CCB (call condense blocks), respectively.
CCBSZ
The number of times a CCB has been allocated in response to a message
from a terminal which was in a valid state to originate a call.
CCBSZ2
The extension register for CCBSZ.
CCBOVFL
The number of messages lost because there were no idle CCB available to
assign to them.
CCBTRU
Usage count of the number of CCB assigned. Scan rate is 100 second.
CCBTRU2
The extension register for CCBTRU.
CPSZ
The number of times a call process has been activated.
CPSZ2
The extension register for CPSZ.
CPTRU
Usage count of the number of call processes active at any one time. Scan
rate is 100 second.
CPTRU2
The extension register for CPTRU.
CPTRAP
Number of calls failing during call processing because the CPU hardware
detected an illegal software condition.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–27

CPSUIC
Number of calls failing during call processing because unexpected results
were detected.
ORIGDENY
The number of times an activated call process was not allowed to work on a
new origination because the limit on new originations has been reached.
WAITDENY
The number of calls forcibly released because call processing has requested
a brief suspension and the associated call process was the only available to
process requests for service from other calls.
CPLSZ
Number of seizures of CP letters to carry messages to calls already in the
system.
CPLSZ2
The extension register for CPLSZ.
CPLOOVFL
Number of messages from terminals which could be originating calls, where
the message could not be passed by the message buffer nor a CP letter.
CPLPOVL
Number of progress messages from terminals where the message could not
be passed because no CP letters were available.
CPLTRU
Usage count of the number of CP letters assigned. Scan rate is 100 second.
CPLOSZ
Number of messages from terminals which are in a state to originate a call,
which are stored in a CP letter rather than an originating buffer.
CPLLOW
The number of idle CP letters at any point during a given transfer period.
OUTBSZ
The number of outgoing messages which must be placed in a buffer because
the CMC was busy.
OUTBOVFL
The number of outgoing messages lost because no idle buffer was available.
OUTBTRU
Usage count of the number of output buffers assigned. Scan rate is 100
second.

DMS-100 International Technical Specification BCS40i and up

7–28 Administration

MULTSZ
The number of seizures of a multi-block.
MULTTRU
Usage count of the number of multi blocks assigned. Scan rate is 100
second.
MULTOVFL
Number of attempts at initiating a multi-linked call because no idle
multi-block was available.
WAKESZ
Count of CPWAKEUP block seizures.
WAKEOVFL
Count of unsuccessful CPWAKEBLOCK seizures.
WAKETRU
Usage count of the number of CPWAKEUP blocks assigned. Scan rate is
100 second.
CINITC
Count of number of all the CCB in use at the time of a cold restart.
WINITC
Count of number of all the CCB in use at the time of a warm restart.
INITDENY
An estimate of the number of call originations denied during cold and warm
restart, initialization periods.
CP2
This OM group extends the CP group. CP2 has two info fields and 11 usage
fields:
CPO2INFOX
There are two info fields. The first always has a value of zero. The second
gives the value of the number of provisioned ECCB.
ECCBSZ
The number of ECCB in use by applications.
ECCBOVFL
The number of times a request for an ECCB failed because there were none
free.
ECCBTRU
Usage count of the number of ECCB assigned. Scan rate is 100 second.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–29

CPWORKU
The number of times the cp capacity index exceeded four. This index is the
count of half second intervals during which the CP queue was never empty
over the last 5 seconds.
INEFDENY
The number of times a origination request has been purposely discarded
because a second message arrived indicating that the call has been
abandoned.
CPLHI
The highest number of CP letters in simultaneous use reached.
CCBHI
The highest number of CCB in simultaneous use, reached.
CPHI
The highest number of Call Processes in simultaneous use, reached.
OUTBHI
The highest number of outgoing buffers in simultaneous use, reached.
MULTHI
The highest number of multi-blocks in simultaneous use, reached.
WAKEHI
The highest number of wakeup blocks in simultaneous use, reached.
CPU
This group measures the performance of the central processing unit (CPU).
CPU has one register with 8 usage fields:
MTCHINT
The number of mismatch interrupts due to hardware-detected differences
between the two CPU.
TRAPINT
The number of trap interrupts occurred.
CPUFLT
The number of times a CPU, data store, program store, a link to a CMC or a
CMC data port is machine busied as a result of a diagnostic failure.
SYSWINIT
The number of warm restarts which have occurred during the current
transfer period.

DMS-100 International Technical Specification BCS40i and up

7–30 Administration

SYSCINIT
The number of cold restarts which have occurred during the current transfer
period.
SYNCLOSS
The number of times the CPUs were put into simplex mode following a
mismatch interrupt.
MSYLOSSU
Usage count of the amount of time the CPUs are operating in simplex mode
as a result of map commands or jamming of the inactive switch on a CPU.
Scan rate is 100 second.
SSYLOSSU
Usage count of the amount of time the CPUs are operating in simplex mode
as a result of a system action such as a diagnostic failure. Scan rate is 100
second.
CSL
This group measures the performance of console devices such as TTY and
MAP. CSL has four usage groups:
CSLERR
The number of device errors detected by the I/O system. A device is
permitted to recover from up to five errors between successive audits before
being left permanently system-busy.
CSLFLT
The number of times the system did not recover an I/O device following the
occurrence of an error previously pegged in CLSERR, either because it did
not pass diagnostic tests, or because this was the it sixth error in the current
audit interval.
CSLSBU
Usage count of the number of I/O consoles in system-busy state. The scan
rate is 100 second.
DCM
Refer to OM groups PM or PMTYP.
DDU
This group measures the performance of the disk drive units. DDU consists
of 4 usage groups:
DDUERROR
A count of the I/O errors detected in the operation of an inservice disk drive
unit causing an out of service condition.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–31

DDUFAULT
A count of the Return to Service failures. Incremented each time a DDU
fails to recover from an error previously pegged in DDUERROR.
DDUMBUSY
Usage count of the number of DDU in man-busy state. Scan rate is 100
second.
DDUSBUSY
Usage count of the number of DDU in system-busy state. Scan rate is 100
second.
DS1CARR
This group is not used by International.
DTSR
This group measures the performance of the switch’s ability to return dial
tone within three seconds. The key to this group is LMDP, LMDT, LCMDT,
LCMDP, LCMKS and DLMKS. DTSR has four usage registers for each
key:
TOTAL
A count of the total sampled calls.
TOTAL_2
The extension register of TOTAL.
DELAY
A count of sampled calls where dial tone delay exceeds 3 seconds or which
got receiver queue overflow.
DELAY_2
The extension register of DELAY.
DTSRPM
This group measures the performance of each peripheral’s ability to return
dial tone within three seconds. The key to the group is the index for the
peripheral. DTSRPM has one info field which gives the key and the name
of the peripheral, and six usage fields:
DTSRPM_OMINFO
The index of the peripheral (LCM) plus the name.
DPLTOT
A count of the total sampled calls originated by DP lines for this LCM.

DMS-100 International Technical Specification BCS40i and up

7–32 Administration

DPLDLY
A count of sampled calls where dial tone delay for DP lines exceeds 3
seconds or which got receiver queue overflow.
DGTTOT
A count of the total sampled calls originated by DT lines for this LCM.
DGTDLY
A count of sampled calls where dial tone delay for DT lines exceeds 3
seconds or which got receiver queue overflow.
KSTOT
A count of the total sampled calls originated by keyset lines for this LCM.
KSDLY
A count of sampled calls where dial tone delay for keyset lines exceeds 3
seconds or which got receiver queue overflow.
EXT
This group measures the usage of Extension blocks, which are registers for
storing auxiliary call data. The key to this group is the type of ext block,
indexed by EXT_FORMAT_CODE. There is one info field and four usage
fields.
EXTINFO
This displays the index of the ext block plus the external name.
EXTSEIZ
The number of times a request for an extension block of this type was
successful.
EXTOVFL
The number of times a request for an extension block of this type failed
because there were none unassigned.
EXTUSAGE
Usage count of the number of extension blocks assigned. Scan rate is 100
second.
EXTHI
The highest number of extension blocks of that type in simultaneous use
reached.
FTRQ
This group measures the usage of feature queue blocks, which are registers
for storing feature information against an agent. The key to this group is the

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–33

type of feature queue block: ftrqagents, ftrq0wareas, ftrq2wareas,

ftrq4wareas and ftrq8wareas. FTRQ has one info field and four usage fields:
FTRQOM_INFO
This displays the number of blocks of each type provisioned.
FTRQSEIZ
The number of times a request for a feature queue block of this type was
successful.
FTRQOVFL
The number of times a request for a feature queue block of this type failed
because none were unassigned.
FTRQUSGE
The count of the number of feature queue blocks of this type in use. Scan
rate is 100 second.
FTRQHI
The highest number of feature queue blocks of this type in simultaneous use
reached.
HUNT
This group measures the performance of each hunt group in the switch.
HUNT has one register for each hunt group, that consists of one info field
and three usage fields:
HUNT_OM_INFO_TYPE
This displays the directory number of the pilot, the hunt group type, and the
size of the group.
HUNTATT
The number of attempts to terminate on this hunt group.
HUNTOVFL
The number of attempts to terminate on this hunt group which fail because
no member is available for termination.
HUNTTRHNT
The number of attempts to terminate on this group which are forced to
re-hunt due to a system problem such as ringing failure.
IADL
This group measures the usage of the Abbreviated Dialing feature. IADL
has seventeen usage fields:

DMS-100 International Technical Specification BCS40i and up

7–34 Administration

AL10PROG
The number of times a 10-member list has a new number programmed.
AL10INTG
The number of times a 10-member list is interrogated for a number.
AL10USGE
The number of times a 10-member list has a member used.
AL10CERR
The number of times a 10-member list has been incorrectly accessed by a
subscriber.
AL30PROG
The number of times a 30-member list has a new number programmed.
AL30INTG
The number of times a 30-member list is interrogated for a number.
AL30USGE
The number of times a 30-member list has a member used.
AL30CERR
The number of times a 30-member list has been incorrectly accessed by a
subscriber.
AL60PROG
The number of times a 60-member list has a new number programmed.
AL60INTG
The number of times a 60-member list is interrogated for a number.
AL60USGE
The number of times a 60-member list has a member used.
AL60CERR
The number of times a 60-member list has been incorrectly accessed by a
subscriber.
ALHNPROG
The number of times a 100-member list has a new number programmed.
ALHNINTG
The number of times a 100-member list is interrogated for a number.
ALHNUSGE
The number of times a 100-member list has a member used.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–35

ALHNCERR
The number of times a 100-member list has been incorrectly accessed by a
subscriber.
ADLCERR
The number of times a subscriber without the ADL feature attempts to
access the feature.
ICDIVF
This group measures the usage of a call diversion to a fixed destination
feature, i.e. Call diversion to an Operator (CDO) and Call Diversion Fixed
(CDF). ICDIVF has 16 fields:
CDOACT
The number of times a subscriber activates the CDO feature.
CDODACT
The number of times a subscriber deactivates the CDO feature.
CDOINTG
The number of times a subscriber interrogates the CDO feature.
CDOUSGE
The number of times an incoming call is diverted by the CDO feature.
CDODENY
The number of times an incoming call is denied the diversion specified by
the CDO feature because the terminator is engaged in a diverted call or the
call has already been diverted five times.
CDOOVFL
The number of times an incoming call is denied the diversion specified by
the CDO feature due to of a lack of system resources.
CDOCERR
The number of times a subscriber incorrectly accesses the CDO feature.
CDODERR
The number of times an incoming call is denied the diversion specified by
the CDO feature due to an inaccessible target number.
CDFACT
The number of times a subscriber activates the CDF feature.
CDFDACT
The number of times a subscriber deactivates the CDF feature.

DMS-100 International Technical Specification BCS40i and up

7–36 Administration

CDFINTG
The number of times a subscriber interrogates the CDF feature.
CDFUSGE
The number of times an incoming call is diverted by the CDF feature.
CDFDENY
The number of times an incoming call is denied the diversion specified by
the CDF feature because the terminator is engaged in a diverted call or the
call has already been diverted five times.
CDFOVFL
The number of times an incoming call is denied the diversion specified by
the CDF feature due to of a lack of system resources.
CDFCERR
The number of times a subscriber incorrectly accesses the CDF feature.
CDFDERR
The number of times an incoming call is denied the diversion specified by
the CDF feature due to an inaccessible target number.
ICDIVP
This group measures the usage of a call diversion to a programmable
destination feature, i.e. Call diversion to an Announcement (CDA), Call
Diversion to a Subscriber (CDS) and Call Diversion on Busy (CDB).
ICDIVP has 27 fields:
CDAACT
The number of times a subscriber activates the CDA feature.
CDAPROG
The number of times a subscriber programs the CDA feature.
CDADACT
The number of times a subscriber deactivates the CDA feature.
CDAINTG
The number of times a subscriber interrogates the CDA feature.
CDAUSGE
The number of times an incoming call is diverted by the CDA feature.
CDADENY
The number of times an incoming call is denied the diversion specified by
the CDA feature because the terminator is engaged in a diverted call or the
call has already been diverted five times.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–37

CDAOVFL
The number of times an incoming call is denied the diversion specified by
the CDA feature due to of a lack of system resources.
CDACERR
The number of times a subscriber incorrectly accesses the CDA feature.
CDADERR
The number of times an incoming call is denied the diversion specified by
the CDA feature due to an inaccessible target number.
CDSACT
The number of times a subscriber activates the CDS feature.
CDSPROG
The number of times a subscriber programs the CDS feature.
CDSDACT
The number of times a subscriber deactivates the CDS feature.
CDSINTG
The number of times a subscriber interrogates the CDS feature.
CDSUSGE
The number of times an incoming call is diverted by the CDS feature.
CDSDENY
The number of times an incoming call is denied the diversion specified by
the CDS feature because the terminator is engaged in a diverted call or the
call has already been diverted five times.
CDSOVFL
The number of times an incoming call is denied the diversion specified by
the CDS feature due to of a lack of system resources.
CDSCERR
The number of times a subscriber incorrectly accesses the CDS feature.
CDSDERR
The number of times an incoming call is denied the diversion specified by
the CDS feature due to an inaccessible target number.
CDBACT
The number of times a subscriber activates the CDB feature.
CDBPROG
The number of times a subscriber programs the CDB feature.

DMS-100 International Technical Specification BCS40i and up

7–38 Administration

CDBDACT
The number of times a subscriber deactivates the CDB feature.
CDBINTG
The number of times a subscriber interrogates the CDB feature.
CDBUSGE
The number of times an incoming call is diverted by the CDB feature.
CDBDENY
The number of times an incoming call is denied the diversion specified by
the CDB feature because the terminator is engaged in a diverted call or the
call has already been diverted five times.
CDBOVFL
The number of times an incoming call is denied the diversion specified by
the CDB feature due to of a lack of system resources.
CDBCERR
The number of times a subscriber incorrectly accesses the CDB feature.
CDBDERR
The number of times an incoming call is denied the diversion specified by
the CDB feature due to an inaccessible target number.
ICONF
This group measures the usage of the Three-Way Call (3WC) and Six-Way
Call (6WC) features. ICONF has 12 fields:
TWCUSGE
The number of times a subscriber engages a 3-port conference circuit via the
use of R3.
TWCDENY
The number of times a subscriber is unable to engage a 3-port conference
circuit because the leg the subscriber is attempting to conference is in an
invalid call state.
TWCOVRFL
The number of times a subscriber is unable to engage a 3-port conference
circuit due to a lack of system resources.
TWCCERR
The number of times a subscriber incorrectly attempts to engage a 3-port
conference circuit.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–39

SWCUSGE
The number of times a subscriber engages a 6-port conference circuit via the
use of R3.
SWCDENY
The number of times a subscriber is unable to engage a 6-port conference
circuit because the leg the subscriber is attempting to conference is in an
invalid call state.
SWCOVFL
The number of times a subscriber is unable to engage a 6-port conference
circuit due to a lack of system resources.
SWCCERR
The number of times a subscriber incorrectly attempts to engage a 6-port
conference circuit.
ADDNUSGE
The number of times a subscriber successfully initiates an enquiry call.
ADDNDENY
The number of times a subscriber is unable to initiate an enquiry call
because the active call is in an improper state.
ADDNOVFL
The number of times a subscriber is unable to initiate an enquiry call due to
a lack of system resources.
ADDNCERR
The number of times a subscriber incorrectly attempts to initiate an enquiry
call.
ICWT
This group measures the usage of the Call Waiting (CWT) and the Cancel
Call Waiting (CCW) features. ICWT has 8 fields:
CWTUSGE
The number of times the call waiting tone is applied to a subscriber.
CWTABNDN
The number of times a call which is waiting on another call is terminated
before it answered.
CWTDENY
The number of times system restrictions prevent a subscriber from being
waited on.

DMS-100 International Technical Specification BCS40i and up

7–40 Administration

CWTOVFL
The number of times insufficient resources prevent a subscriber from being
waited on.
CWTCERR
The number of times a subscriber incorrectly attempts to invoke the CWT
feature.
CCWACT
The number of times a subscriber successfully activates the CCW feature.
CCWUSGE
The number of times a call is prevented from being waited on because the
subscriber has CCW active.
CCWCERR
The number of times a subscriber incorrectly attempts to activate the CCW
feature.
IDND
This group measures the usage of the Do Not Disturb (DND) feature. IDND
has eight usage fields:
DNDACT
The number of times a subscriber successfully activates DND.
DNDDACT
The number of times a subscriber successfully deactivates DND.
DNDINTG
The number of times a subscriber interrogates DND.
DNDUSGE
The number of times an incoming call to a subscriber with DND active is
diverted to treatment.
DNDDENY
The number of times an incoming call to a subscriber with DND active is
not diverted due to a call already being diverted or the incoming call is
attempting to be diverted for the sixth time.
DNDOVFL
The number of times an incoming call to a subscriber with DND active is
not diverted due to insufficient system resources.
DNDCERR
The number of times a customer incorrectly attempts to access the DND
feature.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–41

DNDDERR
The number of times an incoming call to a subscriber with DND active is
not diverted due to incorrect routine or translation datafill.
IFDL
This group measures the usage of the features which automatically route to a
fixed destination. These are the Hotline (HTL) and Warmline (WLN)
features. IFDL has nine usage fields:
HTLUSGE
The number of times a subscriber goes off hook and is routed to the HTL
destination.
HTLOVFL
The number of times a subscriber cannot be routed to HTL destination due
to data corruption or software errors.
WLNACT
The number of times a subscriber successfully activates Warmline.
WLNPROG
The number of times a subscriber successfully programs Warmline.
WLNDACT
The number of times a subscriber successfully deactivates Warmline.
WLNINTG
The number of times a subscriber interrogates Warmline.
WLNUSGE
The number of times a subscriber goes off hook and is routed to the WLN
destination.
WLNOVFL
The number of times a subscriber cannot be routed to WLN destination due
to data corruption or software errors.
WLNCERR
The number of times a subscriber incorrectly accesses the WLN feature.
ILR
This group measures the usage of the International Line Restrictions (ILR)
feature. ILR has 17 usage fields:
DNIACT
The number of times a subscriber activates the Deny National and
International version of ILR.

DMS-100 International Technical Specification BCS40i and up

7–42 Administration

DNIDEACT
The number of times a subscriber deactivates the Deny National and
International version of ILR.
DNIUSGE
The number of times a subscriber is prevented from making a National or an
International call with DNI active.
DAIACT
The number of times a subscriber activates the Deny All International
version of ILR.
DAIDACT
The number of times a subscriber deactivates the Deny All International
version of ILR.
DAIUSGE
The number of times a subscriber is prevented from making an International
call with DAI active.
DABEACT
The number of times a subscriber activates the Deny All But Emergency
version of ILR.
DABEDACT
The number of times a subscriber deactivates the Deny All But Emergency
version of ILR.
DABEUSGE
The number of times a subscriber is prevented from making any but an
Emergency call with DABE active.
DIDDACT
The number of times a subscriber activates the Deny International Direct
Dial version of ILR.
DIDDDACT
The number of times a subscriber deactivates the Deny International Direct
Dial version of ILR.
DIDDUSGE
The number of times a subscriber is prevented from making an International
Direct Dial call with DIDD active.
DNIDACT
The number of times a subscriber activates the Deny National and
International Direct Dial version of ILR.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–43

DNIDDACT
The number of times a subscriber deactivates the Deny National and
International Direct Dial version of ILR.
DNIDUSGE
The number of times a subscriber is prevented from making a National or an
International Direct Dial call with DNID active.
ILRINTG
The number of times a subscriber interrogates the ILR feature.
ILRCERR
The number of times a subscriber incorrectly accesses the ILR feature.
INDC
This group measures the usage of the No Double Connect (INDC) feature.
INDC has five usage fields:
NDCACT
The number of times a subscriber activates the INDC feature.
NDCDACT
The number of times a subscriber deactivates the INDC feature.
NDCINTG
The number of times a subscriber interrogates the INDC feature.
NDCUSGE
The number of times an active call prevents an incoming call from being
waited on or prevents a toll break-in interruption due to IDNC being active.
NDCCERR
The number of times a subscriber incorrectly accesses the INDC feature.
IOC
This group measures the performance of the Input-Output Controllers. IOC
has seven fields:
IOCERR
The number of times an error is detected in the functioning of an in-service
IOC.
IOCLKERR
The number of times a device error is detected by the IOC on one of its
peripheral-side links.

DMS-100 International Technical Specification BCS40i and up

7–44 Administration

IOCFLT
The number of times the IOC is unable to recover following an error which
was previously pegged in IOCERR, and thus remains system-busy.
IOCLKSBU
Usage count of the number of system-busy links between the IOC and the
peripheral devices.
IOCLKMBU
Usage count of the number of man-busy links between the IOC and the
peripheral devices.
IOCSBU
Usage count of the number of system-busy IOCs.
IOCMBU
Usage count of the number of man-busy IOCs.
IOSYS
This group measures the performance of the Input-Output System. IOSYS
has one field:
IOSYSERR
The number of times the I/O system detects an error on an incoming or
outgoing message, as indicated by an error or rebounded-message interrupt
by a CMC.
IWUC
This group measures the usage of the Wakeup Call (WUC) feature. IWUC
has ten usage fields.
WUCACT
The number of times a subscriber activates the WUC feature.
WUCDACT
The number of times a subscriber deactivates the WUC feature.
WUCINTG
The number of times a subscriber interrogates the WUC feature.
WUCUSGE
The number of times a successful wake-up call is generated to the WUC
subscriber.
WUCDENY
The number of times the subscriber is denied from activating a wakeup call
due to feature restrictions.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–45

WUCABDN
The number of times a wake-up call was attempted for the second time but
the subscriber was busy or did not answer.
WUCOVFL
The number of times a wake-up attempt could not be performed due to
insufficient wakeup feature storage.
WUCCERR
The number of times a subscriber incorrectly accesses the WUC feature.
WUCRSET
The number of times a wakeup call was attempted but the subscriber did not
answer or was off-hook.
WUCNRSC
The number of times a wake-up attempt could not be performed due to
insufficient call processing resources.
LM
Refer to groups PM or PMTYP.
LMD
This group measures the performance of local and remote line module
traffic. The key to the group is the internal index into the line module (LCM
for International). LMD has one information field and 11 usage fields:
LMD_OMINFO
Displays the internal peripheral index plus the external name.
NTERMATT
The number of attempts made to provide a path (port channel plus line
drawer channel) between a line to which a call is to terminate, and a network
port. The attempt is only counted after call processing has determined that
the line is available (for example, not busy).
NORIGATT
The number of originating attempts reported by this line module to the CC.
Note that the same customer attempt may cause several machine attempts to
be pegged if the originating line module voice paths are congested.
LMTRU
The usage count of the number of lines in line_cp_busy or
line_cp_busy_deload state. Includes time from when the system attempts to
provide a path between the line and a network port, until that line is released
from the call. The scan rate is 100 second.

DMS-100 International Technical Specification BCS40i and up

7–46 Administration

TERMBLK
The number of attempts to find a voice path from the network to a
terminating line which fail either because all of the LM channels to the
network are busy, or because it is impossible to match an idle channel on any
of the links to the network with an idle channel from the line shelf serving
the terminating line.
ORIGFAIL
The number of originating attempts failing because of partial dial,
permanent signal, extra pulse or bad tones, large twist, or unexpected
message type.
PERCLFL
The number of calls attempting to terminate on this line module which fail
and are given system failure (SYFL) treatment because of the inability to
ring the terminating line properly. Also included are ground start lines that
report loop faults during attempted terminations.
STKCOINS
The number of times an attempt to collect or return coins are stuck.
REVERT
The number of reverted calls initiated on this line. Pegged when ringing
starts, after the caller has gone on hook for the first time.
MADNTATT
The number of times that any Multiple Appearance Directory Number
(MADN) group secondary member on the LM has been notified of an
incoming call. MADN lines are not currently supported in International.
ORIGBLK
The number of originations previously pegged in LMD_NORIGATT which
fail for lack of a path from the originating peripheral module to the network.
ORIGABN
The number of originations previously pegged in LMD_NORIGATT which
are abandoned before the call setup is complete.
LOGS
This group measure the performance of the LOG system. LOGS has 4 usage
fields:
LOSTREC
The total number of log messages lost due to overflows, either of the central
buffer or of individual device buffers.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–47

SWERRCT
The total number of software error reports generated by the switch,
including those which are not reported due to log suppression or buffer
overflow.
PMSWERCT
The total number of software error reports generated by peripheral modules.
PMTRAPCT
The total number of trap reports generated by peripheral modules.
MACHACT
This group measures the performance of CPU usage by different classes of
base level processes. It does not include measurements of the time spent at
interrupt level. MACHACT has five usage fields:
INTLEV
The units of CPU time used in processing foreground tasks. These tasks run
at class levels SYSTEM 6 and SYSTEM 7.
CPLEV
The units of CPU time used in processing work that is related to the
handling of calls. This includes call setup, translation, network connections,
terminations, billing, feature processing and all other actions related to call
processing. It does not include the time spent accepting call processing
messages as this is still part of the interrupt level process. Also included are
tasks (processes) running at class level CPCLASS (5).
MTCELEV
The units of CPU time used in processing high priority maintenance actions,
MAINTCLASS LEVEL – (5). Activities include network maintenance,
reloading new peripherals, CC SYNC operations, and routine maintenance
audits.
BKGDLEV
The units of CPU time used in processing all other maintenance actions,
SYSTEM 0 and NGBKGCLASS (4,3,2,1) Activities include MAP I/O,
LOG output, OM reporting, routine audits.
PREVLEV
The units of CPU time used for the Operational Measurement scan and
transfer function and the CPU time used by LOG and MAP devices defined
as guaranteed in tables TERMDEV, GBKGCLASS LEVEL (4,3,2,1).

DMS-100 International Technical Specification BCS40i and up

7–48 Administration

MTA
This group measures the performance of minibar drivers used for
maintenance actions. The key is the CLLI – MTADRIVER. MTA has one
information field and four usage fields:
MTA_OM_INFO
This displays the number of drivers assigned in table MTAMDRIVE.
MTASZRS
The number of times a set operation is performed on a MTA by the MTA
driver.
MTASZFL
The number of times a set operation is abandoned because the driver is in
use or out of service.
MTATRU
The usage count of the number of MTA drivers performing set operations.
Included are drivers in seized or nwm-busy states. The scan rate is 10
second.
MTAMBU
The usage count of the number of MTA drivers in a man-busy state.
Included are drivers in cp_busy or lockout states. The scan rate is 10
second.
MTRERR
This group measures errors and inconsistencies in the International Metering
System. MTRERR has four usage fields:
LATECHG
The number of times a time-of-day changeover occurs and a peripheral fails
to be updated with the new tariffs.
BADMDI
The number of times a call is made from an agent whose Metering Data
Index (MDI) is invalid.
METOVFL
The number of times any subscriber’s software meter reaches its maximum
limit of 9 999 999, and wraps to 0.
MTRUSG
The MTRUSG OM group provides general information on metering usage.
MTRUSG has 16 fields.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–49

CCMATCDV – CC meter attempts call diversion

CCMATCDV is incremented each time a call is converted to CC metering
due to any Call Diversion feature, including:
• Call Diversion to Announcement (CDA)
• Call Diversion to Busy (CDB)
• Call Diversion Fixed (CDF)
• Call diversion to Operator (CDO)
• Call Diversion to Subscriber (CDS)
• International Do Not Disturb (IDND).

CCMATCDV is incremented once for each leg of call diversion.

CCMATCUP – CC meter attempts due to CUP
CCMATCUP is incremented each time a call is converted to CC metering.
This occurs for calls which have been connected for more than two hours
and have their appropriate meters updated by the Charge Update Process
(CUP).
CCMATCUP is also pegged when THQCLEAN is executed from the MAP.
CCATCUPS – CC meter attempts due to subsequent CUP
CCATCUPS peg is incremented every time a call has its meter updated
additional times by CUP.
CCATCUPS is also pegged when THQCLEAN is executed from the MAP.
CCMATINI – CC METER attempts initial
CCMATINI is incremented each time a two party call is initially converted
to CC metering due to subscriber flashing, for reasons such as the following:
• To activate the MCT feature
• To perform a subscriber control function
• To accept a waiting call
• To originate an add-on leg

CCMATADD – CC meter attempts add-on leg

CCMATADD is incremented each time an additional leg requiring metering
is added to a call due to an enquiry or CWT call.
CCMATTBI – CC meter attempts TBI
CCMATTBI is incremented each time the call is converted to CC metering
due to the activation of the Toll Break In (TBI) feature.
CCMATCPM – CC meter attempts called party metering
CCMATCPM is incremented each time the call is converted to CC metering
due to the activation of Called Party Metering (CPM) feature.

DMS-100 International Technical Specification BCS40i and up

7–50 Administration

CCMATXPM – CC meter attempts XPM error

CCMATXPM is incremented each time an attempt is made to convert a call
to CC metering due to a PM software error occurring. These are the calls
that are successful, but a meter count could not be calculated for them by the
XPM. CCMATXPM is also pegged if a corrupted message is received from
an XPM.
CCMATERR – CC meter attempts error
CCMATERR is incremented each time a call is converted to CC metering
due to an error in the call. These are calls that do not complete successfully,
for example, calls which do not survive an XPM cold switch of activity
(SWACT).
LNXPMM1 – line XPM metering usage
LNXPMM1 is incremented each time a line originated call is XPM-metered
successfully. These are the calls that have their meters updated by the count
received from the ILGC.
LNXPMM2 – line XPM metering usage overflow
LNXPMM2 is incremented each time LNXPMM1 overflows and wraps to
zero. Therefore, LNXPMM2 is pegged once each time LNXPMM1 reaches
65535.
TKXPMM1 – trunk XPM metering usage
TKXPMM1 is incremented each time a trunk-originated call is
XPM-metered successfully. These are calls that have their meters updated
by the count received from the IDTC.
TKXPMM2 – trunk XPM metering usage overflow
TKXPMM2 is incremented each time TKXPMM1 overflows and wraps to
zero. Therefore, TKXPMM2 is pegged once each time TKXPMM1 reaches
65535.
LNCCM1 – line CC metering usage
LNCCM1 is incremented each time a line-originated call is CC metered
successfully. These are calls that have their meters updated by the CC
metering system.
LNCCM2 – line CC metering usage overflow
LNCCM2 is incremented each time LNCCM1 overflows and wraps to zero.
Therefore, LNCCM2 is pegged once each time LNCCM1 reaches 65535.
TKCCM1 – trunk CC metering usage
TKCCM1 is incremented each time a line-originated call is CC metered
successfully. These are calls that have their meters updated by the CC
metering system.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–51

TKCCM2 – trunk CC Metering usage overflow

TKCCM2 is incremented each time TKCCM1 overflows and wraps to zero.
Therefore, TKCCM2 is pegged once each time TKCCM1 reaches 65535.
MTRPERF
OM group MTRPERF provides general information on the performance of
International metering. This includes metering problems due to datafill
errors, resource unavailability, and software deficiencies. It also provides
information on mismatches found by the audit and the recovery processes,
and on the problems found with the Tariff History Queue (THQ) and the
Time Of Day (TOD) system. There are 13 fields in this group.
DTCALLP – Datafill CALLP
DTCALLP is incremented when a datafill problem is encountered while
attempting to perform metering on a line or trunk originated call. The
datafill problems may be any of the following:
• Logical network invalid
• Metering Data Index (MDI) not datafilled
• Destination zone not datafilled
• TRFIDX invalid

DTXPM – Datafill XPM

DTXPM is incremented when a datafill problem with the XPM is
encountered while attempting to perform metering on a line or trunk
originated call. The datafill problems may be any of the following:
• Tariff Number Table (TNT) invalid
• Logical network invalid
• TRFIDX invalid.
• TARIFNUM invalid
• MTSIGSYS index invalid
• Metering rate mismatch
• Metering function mismatch

DTFEAT – Datafill feature

DTFEAT is incremented when a datafill error occurs in table FEATCHG
while attempting to charge for a feature.
TIMEST0 – Timestamp zero
TIMEST0 is incremented each time a CC metered call has an uninitialized
origination time (default of zero) while performing CC metering.
DURERR – Duration error
DURERR is incremented each time a duration greater than the meter
duration threshold (249 days) is calculated while performing CC metering.

DMS-100 International Technical Specification BCS40i and up

7–52 Administration

COUNTERR – Count error

COUNTERR is incremented each time a meter count greater than the meter
count threshold (201600) is calculated. This also causes CCMATXPM to be
incremented.
MTRBKERR – Meter block error
MTRBKERR is incremented when an agent’s meter block can not be found
while trying to update a meter with the calculated charges.
MTRAUDER – Meter audit error
MTRAUDER is incremented when a discrepancy is found with the meters
by the metering audit. The possible discrepancies are:
• A meter is found which is not supposed to be assigned to an agent.
• An agent does not have all the meters assigned that the datafill indicates
it should have.
• An agent has more meters assigned that the datafill indicates it should
have.
• An agent does not have meters allocated to it when it should.
• A meter is owned by more than one agent.
• A mismatch exists between an agent and the “owner” field of its meter
block.
RECYCFND – Recycled found
RECYCFND is incremented each time a recycled meter is found by the
recovery process after a system reload from image.
RECYCCLR – Recycled cleared
RECYCCLR is incremented each time a recycled meter is cleared by the
meter audit after not being reclaimed on the third run of the audit, or when
the RCLR command is issued.
THQOVFL – THQ overflow
THQOVFL is incremented when Table History Queue (THQ) resources are
not available when attempting to get a THQ block to support metering TOD
changes.
THQERR – THQ error
• THQ is NIL.
• THQ head or body is corrupt.
• THQ block with an effective time of earlier than the call being metered
is not found. This occurs when the call being metered appears to have
ended earlier than any tariff would apply.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–53

TODXPMFL – TOD XPM failure

TODXPMFL is incremented when an XPM fails to correctly respond to a
time of day action.
MTU
This group measures the performance of the Magnetic Tape Units. MTU has
4 usage fields:
MTUERR
The total number of errors observed on an in service magnetic tape unit.
MTUFLT
The number of times a tape unit fails to recover from an error previous
pegged in MTUERR and causes the MTU to remain in a system-busy state.
MTUSBU
The usage count of the number of magnetic tape units in a system-busy state.
The scan rate is 100 second.
MTUMBU
The usage count of the number of magnetic tape units in a man-busy state.
The scan rate is 100 second.
NMC
This group measures the performance of the Network Message Controller.
NMC has 12 usage fields:
NMMSGER
The number of errors detected on in-service message links between network
and peripheral modules, whether they prove to be transient or persistent, and
whether or not further action is taken on them.
NMSPCER
The number of errors detected on speech connections through the network,
whether they prove transient or persistent, and whether or not further action
is taken on them. This value will be equal to the number of integrity failure
reports received from peripheral module controllers.
NMCERR
The number of errors detected in the operation of in-service network module
controllers, whether transient or persistent, and whether or not further action
is taken on them.
NMMSGFL
The number of times a link between a network module and a peripheral
module could not be recovered following the observation of an error. The
link is left system-busy.

DMS-100 International Technical Specification BCS40i and up

7–54 Administration

NMSPCFL
The number of times a hard fault is identified in the network-resident
connection memory or in a speech path segment internal to the network, as a
result of diagnostic tests triggered by an integrity failure previously pegged
in NMSPCER. The path segment affected is made unavailable to call
processing.
NMCFLT
The number of times a network module controller cannot recover from an
error previously pegged in NMCERR. The controller is left system-busy.
NMSBU
The usage count of the number of network modules in system-busy state.
The scan rate is 100 second.
NMMBU
The usage count of the number of network modules in man-busy state. The
scan rate is 100 second.
NMPTSBU
The usage count of the number of network module ports in system-busy
state. The scan rate is 100 second.
NMPTMBU
The usage count of the number of network module ports in man-busy state.
The scan rate is 100 second.
NMJRSBU
The usage count of the number of junctors in system-busy state. The scan
rate is 100 second.
NMJRMBU
The usage count of the number of junctors in man-busy state. The scan rate
is 100 second.
NWMTGCNT
This group is not currently supported for International.
OFZ
This group has been replaced by OTS and SOTS.
OFZ2
This group has been replaced by OTS and SOTS.
OTS
This group measures the traffic load on the switch. The sum of the
incoming traffic calls represents the external pressure on the switch. The

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–55

originating and system generated disposition registers represent the internal

pressure on the switch. The sum of the internal and external pressure gives
the total office pressure. This group should be used in conjunction with
SOTS. OTS has 30 usage fields:
NORG
The total number of originating attempts from originating traffic recognized
by the CC.
NORG2
The extension register of NORG.
ORGTRM
The number of calls from originating traffic which connect onto terminating
traffic (i.e. line to line).
ORGTRM2
The extension register of ORGTRM.
ORGOUT
The number of calls from originating traffic which connect onto outgoing
traffic (that is, line to trunk).
ORGOUT2
The extension register of ORGOUT.
ORGTRMT
The number of calls from originating traffic which connect onto a tone or an
announcement.
ORGOUT2
The extension register of ORGTRMT.
ORGABDN
The number of calls from originating traffic which are abandoned by the
customer before disposition to: terminating traffic, outgoing traffic, tone,
announcement, lockout, or feature activation or deactivation.
ORGLKT
The number of calls from originating traffic which are forced to re-originate
without being connected to treatment or receiving treatment. In the case of
Guaranteed Dial Tone, only the origination attempt from the idle state is
pegged.
ORGFSET
The number of calls from originating traffic which invoke a custom calling
feature activation or deactivation.

DMS-100 International Technical Specification BCS40i and up

7–56 Administration

ORGFSET2
The extension register for ORGFSET.
NINC
The total number of incoming attempts from incoming traffic which are
recognized by the CC.
NINC2
The extension register for NINC.
INCTRM
The number of calls from incoming traffic which connect to terminating
traffic (that is, trunk to line).
INCTRM2
The extension register for INCTRM.
INCOUT
The number of calls from incoming traffic which connect to outgoing traffic
(that is, trunk to trunk).
INCOUT2
The extension register for INCOUT.
INCTRMT
The number of calls from incoming traffic which connect to a tone or an
announcement.
INCABNM
The number of calls from incoming traffic which are machine abandoned
before being connected to terminating traffic, outgoing traffic, tone,
announcement, lock-out status, or feature activation or deactivation. This
may occur because of upstream office delays or problems.
INCABNC
The number of calls from incoming traffic which are abandoned before
being connected to terminating traffic, outgoing traffic, tone, announcement,
lock-out status, or feature activation or deactivation. This may occur
because of customer abandonment.
INCLKT
The number of calls from incoming traffic which fail to connect or receive a
treatment. This may occur because the true identity of the incoming call has
been lost or the trunk has been force released. These are incoming calls
attempts which could originate and then were not able to terminate to an
agent.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–57

INCFSET
The number of calls from incoming traffic which invoke a custom calling
feature activation or deactivation. This capability is not currently supported
in International.
INCFSET2
The extension register for INCFSET.
NSYS
The total number of calls recognized by the CC as being system generated
traffic. This includes all forms of originations that cannot be included in
NORG or NINC. For example, a line to alternate trunk because the first
trunk encountered outpulsing trouble, or a line to alternate hunt line because
the previous hunt line was busy.
NSYS2
The extension register for NSYS.
SYSTRM
The number of calls from system generated traffic which connect to
terminating traffic. System generated calls to BUSY line treatment are
considered to be line terminations.
SYSOUT
The number of calls from system generated traffic which connect to
outgoing traffic.
SYSTRMT
The number of calls from system generated traffic which connect to a tone
or an announcement due to an error condition.
SYSABDN
The number of calls from system generated traffic which are abandoned
before disposition to terminating traffic, outgoing traffic, tone,
announcement, lock-out status, or feature activation or deactivation. This
may occur because of customer abandonment.
SYSLKT
The number of calls from system generated traffic which are locked-out
prior to any other routing.
SYSFSET
The number of calls from system generated traffic which invoke a custom
calling feature. This is not currently supported in International.

DMS-100 International Technical Specification BCS40i and up

7–58 Administration

PCMCARR
This group measures the performance of the 30–channel PCM Carrier links
for the International Digital Trunk Controller (IDTC). The key to this group
is the range of carriers (16 for each IDTC). PCMCARR has one information
field and 20 usage fields:
D30OMINF
This displays the D30CLLI, which consists of the PMNAME and the
D30CKT.
LLFAERR
The number of times a Local Loss of Frame Alignment error occurs in this
carrier. A LLFA error occurs when 3 or 4 consecutive frame alignment
patterns have been received with an error.
LLMAERR
The number of times a Local Loss of Multiframe Alignment error occurs in
this carrier. A LLMA error occurs when 2 consecutive multiframe
alignment patterns have been received with an error.
RFAIERR
The number of times a Remote Frame Alarm Indication error occurs in this
carrier. A RFAI error occurs when the remote equipment indicates that it is
experiencing frame level errors and/or equipment failures.
RMAIERR
The number of times a Remote Multiframe Alarm Indication error occurs in
this carrier. A RMAI error occurs when the remote equipment indicates that
it is experiencing multiframe level errors and/or equipment failures.
AISERR
The number of times an Alarm Indication Signal error occurs in this carrier.
An AIS error occurs when a continuous stream of 1s is detected.
BERERR
The number of times a Bit Error Rate error occurs in this carrier. An BER
error occurs when a frame alignment pattern is found to be incorrect.
SLIPERR
The number of times a frame is slipped in the carrier.
SIGLERR
The number of times a transient change is detected in the supervisory
signaling channels of the carrier.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–59

LLFAFLT
The number of times a Local Loss of Frame Alignment fault occurs in this
carrier. A LLFA fault occurs when a LLFA error persists past the LLFAOST
threshold or the number of non-persistent errors reaches the LLFAOL
threshold.
LLMAFLT
The number of times a Local Loss of Multiframe Alignment fault occurs in
this carrier. A LLMA fault occurs when a LLMA error persists past the
LLMAOST threshold or the number of non-persistent errors reaches the
LLMAOL threshold.
RFAIFLT
The number of times a Remote Frame Alarm Indication fault occurs in this
carrier. A RFAI fault occurs when a RFAI error persists past the RFAIOST
threshold or the number of non-persistent errors reaches the RFAIOL
threshold.
RMAIFLT
The number of times a Remote Multiframe Alarm Indication fault occurs in
this carrier. A RMAI fault occurs when a RMAI error persists past the
RMAIOST threshold or the number of non-persistent errors reaches the
RMAIOL threshold.
AISFLT
The number of times an Alarm Indication Signal fault occurs in this carrier.
A AIS fault occurs when a AIS error persists past the AISOST threshold or
the number of non-persistent errors reaches the AISOL threshold.
BERFLT
The number of times an Bit Error Rate fault occurs in this carrier. A BER
fault occurs when the number of BER errors exceeds the BEROL threshold.
SLIPFLT
The number of times the number of frames slipped exceeds the SLIPOL
threshold.
SIGLFLT
The number of times the number of transient changes in supervisory
signalling channels exceeds the SIGLOL threshold.
CARRSYSB
The usage count of the number of times the carrier was in system-busy state
because of fault occurrences. Scan rate is 100 second.

DMS-100 International Technical Specification BCS40i and up

7–60 Administration

CARRCBSY
The usage count of the number of times the carrier was in CBSY state
because the C-side peripheral was not in service. Scan rate is 100 second.
CARRPBSY
The usage count of the number of times the carrier was in PBSY state
because the P-side peripheral was not in service. Scan rate is 100 second.
CARRMANB
The usage count of the number of times the carrier was in manual-busy state
due to manual actions. Scan rate is 100 second.
PM
This group measures the performance of each peripheral module. The key is
the range of PMs. PM has one info field and 22 usage fields:
PM_OM_INFO_TYPE
This displays the device name, that is, the device class and device number,
and an optional * which indicates that the PM node is datafilled in table
PMEXCEPT.
PMERR
The number of errors detected in an in service PM.
PMFLT
The number of PM errors, previously pegged in PMERR, which result in the
PM going to a system-busy state.
PMMSBU
The usage count of the number times the PM is in a system-busy state. The
scan rate is 100 second.
PMUSBU
The usage count of the number times a unit in the PM is in a system-busy
state. The scan rate is 100 second.
PMMMBU
The usage count of the number times the PM is in a man-busy state. The
scan rate is 100 second.
PMUMBU
The usage count of the number times a unit in the PM is in a man-busy state.
The scan rate is 100 second.
PMSBP
The number of times the PM is made system-busy from an in-service or an
in-service-trouble state.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–61

PMMBP
The number of times the PM is made man-busy from an in-service or an
in-service-trouble state.
PMSWXFR
The number of times a transfer of activity occurred due to system
intervention resulting in a WARM SWACT or a TAKEOVER.
PMMWXFR
The number of times a transfer of activity occurred due to manual
intervention resulting in a WARM SWACT or a TAKEOVER.
PMSCXFR
The number of times a transfer of activity occurred due to system
intervention resulting in a COLD SWACT.
PMMCXFR
The number of times a transfer of activity occurred due to manual
intervention resulting in a COLD SWACT.
PMCCTDG
The number of times the system has referred a line or a trunk on the PM to
maintenance software for checking because of repeated difficulties during
call processing.
PMCCTFL
The number of instances counted in PMCCTDG where a wrong card, no
card or a card fault was found.
PMPSERR
The number of errors detected on the P-side interface associated with the
peripheral.
PMPSFLT
The number of faults detected on the facilities associated with the peripheral.
PMRGERR
The number of times a problem is detected with a ringing generator
associated with an in service peripheral. This applies to LCMs only.
PMRGFLT
The number of times a problem is detected with an in service ringing
generator associated with an in service peripheral. This applies to LCMs
only.

DMS-100 International Technical Specification BCS40i and up

7–62 Administration

PMSBTCO
The number of times a terminal is in CP-busy or CP-busy-deload state when
the PM is made system-busy or C-side-busy from an in-service or an
in-service-trouble state.
PMMBTCO
The number of times a terminal is in CP-busy or CP-busy-deload state when
the PM is made man-busy from an in-service or an in-service-trouble state.
PMCCTOP
The number of times an outside plant circuit failure is detected on a line or
trunk by system diagnostics. Retests do not repeg this OM.
PMINTEG
The number of times an integrity failure is reported to the CC by the
peripheral. This does not apply to an LCM.
PMOVLD
This group measures attempts to originate or terminate that were denied in
either the CC or the peripheral during overload. PMOVLD has one
information field and two usage fields.
PMOVLD_INFO_TYPE
This displays the host name and peripheral number.
PORGDENY
The number of originations denied because the peripheral is in an overload
conditions and has insufficient realtime to processes an originating call. The
pegging of this implies that the origination is lost. The counts are only
reported to the CC after the peripheral recovers from the overload condition
which means until this happens the peg count will be inaccurate.
PTRMDENY
The number of terminations denied by the CC because the peripheral is in an
overload conditions and has insufficient realtime to processes a terminating
call. This is not currently supported in International.
PMTYP
This group provides totalling of the counts within PM group on a per PM
type basis. The key to the group is the range of PM types. PMTYP has one
information field and 22 usage fields:
PMTYP_OM_INFO_TYPE
This displays the type of PM, and the count of the number of PMs of that
type.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–63

PMTERR
This is the sum of the register PM_PMERR for this PM type. Excluded are
those in excepted in table PMEXCEPT.
PMTFLT
This is the sum of the register PM_PMFLT for this PM type. Excluded are
those in excepted in table PMEXCEPT.
PMTMSBU
This is the sum of the register PM_PMMSBU for this PM type. Excluded
are those in excepted in table PMEXCEPT. Scan rate is 100 second.
PMTUSBU
This is the sum of the register PM_PMUSBU for this PM type. Excluded
are those in excepted in table PMEXCEPT. Scan rate is 100 second.
PMTMMBU
This is the sum of the register PM_PMMMBU for this PM type. Excluded
are those in excepted in table PMEXCEPT. Scan rate is 100 second.
PMTUMBU
This is the sum of the register PM_PMUMBU for this PM type. Excluded
are those in excepted in table PMEXCEPT. Scan rate is 100 second.
PMTSBP
This is the sum of the register PM_PMSBP for this PM type. Excluded are
those in excepted in table PMEXCEPT.
PMTMBP
This is the sum of the register PM_PMMBP for this PM type. Excluded are
those in excepted in table PMEXCEPT.
PMTSWXFR
This is the sum of the register PM_PMSWXFR for this PM type. Excluded
are those in excepted in table PMEXCEPT.
PMTMWXFR
This is the sum of the register PM_PMMWXFR for this PM type. Excluded
are those in excepted in table PMEXCEPT.
PMTSCXFR
This is the sum of the register PM_PMSCXFR for this PM type. Excluded
are those in excepted in table PMEXCEPT.
PMTMCXFR
This is the sum of the register PM_PMMCXFR for this PM type. Excluded
are those in excepted in table PMEXCEPT.

DMS-100 International Technical Specification BCS40i and up

7–64 Administration

PMTCCTDG
This is the sum of the register PM_PMCCTDG for this PM type. Excluded
are those in excepted in table PMEXCEPT.
PMTCCTFL
This is the sum of the register PM_PMCCTFL for this PM type. Excluded
are those in excepted in table PMEXCEPT.
PMTPSERR
This is the sum of the register PM_PMPSERR for this PM type. Excluded
are those in excepted in table PMEXCEPT.
PMTPSFLT
This is the sum of the register PM_PMPSFLT for this PM type. Excluded
are those in excepted in table PMEXCEPT.
PMTRGERR
This is the sum of the register PM_PMRGERR for this PM type. Excluded
are those in excepted in table PMEXCEPT.
PMTRGFLT
This is the sum of the register PM_PMRGFLT for this PM type. Excluded
are those in excepted in table PMEXCEPT.
PMTSBTCO
This is the sum of the register PM_PMSBTCO for this PM type. Excluded
are those in excepted in table PMEXCEPT.
PMTMBTCO
This is the sum of the register PM_PMMBTCO for this PM type. Excluded
are those in excepted in table PMEXCEPT.
PMTCCTOP
This is the sum of the register PM_PMCCTOP for this PM type. Excluded
are those in excepted in table PMEXCEPT.
PMTINTEG
This is the sum of the register PM_PMINTEG for this PM type. Excluded
are those in excepted in table PMEXCEPT.
PM1
This group is not currently supported on DMS-100 International switches.
PM2
Refer to groups PM or PMTYP.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–65

RADR
This group measures the performance of the Receiver Attachment Delay
Recorder. RADR generates test call originations for timing receiver
attachment under various traffic loads. The key is the RCVR_KIND type
which for international means the UTRRCVR kind. RADR has one
information field and three usage fields:
RAD_PHYS_TUPLE_FOR_OMS
This displays the desired number of test calls per hour (RADCALLR), the
lower delay threshold in seconds (RADLDLYT) and the upper delay
threshold in seconds (RADUDLYT).
RADTESTC
The number of tests carried out in the form of requests for receivers.
RADLDLYP
The number of requests which took longer than the lower delay threshold to
satisfy.
RADUDLYP
The number of requests which took longer than the upper delay threshold to
satisfy.
RCVR
DMS-100 International switches use Universal Tone Receivers (UTRs).
Refer to to the UTR OM group.
SOTS
This group measures the performance of the No Circuit Class (NCCLS)
category together with the outgoing and terminating networks. SOTS has 25
usage fields:
SOTSNCBN
The number of times the No Circuit Business Network condition is
encountered. Currently not supported on DMS-100 International switches.
SOTSNCID
The number of times the No Circuit Inward Dial condition is encountered.
Currently not supported on DMS-100 International switches.
SOTSNCIM
The number of times the No Circuit Intermachine condition is encountered.
Currently not supported on DMS-100 International switches.
SOTSNCIT
The number of times the No Circuit Intertoll condition is encountered.
Currently not supported on DMS-100 International switches.

DMS-100 International Technical Specification BCS40i and up

7–66 Administration

SOTSNCLT
The number of times the No Circuit Local Tandem condition is encountered.
Currently not supported on DMS-100 International switches.
SOTSNCOF
The number of times the No Circuit Offnet condition is encountered.
Currently not supported on DMS-100 International switches.
SOTSNCON
The number of times the No Circuit Onnet condition is encountered.
Currently not supported on DMS-100 International switches.
SOTSNCOT
The number of times the No Circuit Other Trunks condition is encountered.
Currently not supported on DMS-100 International switches.
SOTSNCRT
The number of times the No Circuit Trunks condition is encountered.
Currently not supported on DMS-100 International switches.
SOTSNCTC
The number of times the No Circuit Toll Completion condition is
encountered. Currently not supported on DMS-100 International switches.
SOTSNOSC
The number of times the No Circuit Service Trunks condition is
encountered. Currently not supported on DMS-100 International switches.
SOTSPDLM
The number of machine dialed calls that route to Partial Dial treatment.
SOTSPSGM
The number of machine dialed calls that route to Permanent Signal
treatment.
SOUTNWT
The number of attempts to find a network path from a line or a trunk to a
selected outgoing or test trunk.
SOUTNWT2
The extension register for SOUTNWT.
SOUTMFL
The number of first trial match failures to find a network path from a line or
a trunk to a selected outgoing or test trunk.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–67

SOUTRMFL
The number of outgoing calls failing and getting NBLH treatment due to a
second or last trial network match failure on an attempt to connect to an
outgoing or test trunk.
SOUTOSF
The number of first trial seize failures occurring after an outgoing trunk has
been selected and the necessary network paths acquired, following which the
call has been routed onward in an attempt to select another outgoing trunk.
SOUTROSF
The number of outgoing calls failing and getting SSTO treatment due to
outgoing seize failure.
STRMNWT
The number of attempts made to find a voice path to a terminating line.
STRMNWT2
The extension register for STRMNWT.
STRMFL
The number of attempts made to find a voice path to a terminating line
which fail due to the unavailability of a network connection.
STRMBLK
The number of attempts made to find a voice path to a terminating line
which fail due to the unavailability of an LM channel or the impossibility of
matching an idle channel from the network to the terminating line shelf.
STRMRBLK
The number of attempts made to find a voice path from the network to a
terminating line which fail and route to BNLN treatment. This is also
pegged by STRMBLK.
STRMGSGL
The number of attempts made to terminate to a ground start line which fail
to glare.
SPC
This group measures the performance of the semi-permanent connections
feature. SPC has six usage fields:
SPCNTCAT
The number of attempts by the administration, via table control, to set up a
semi-permanent connection.

DMS-100 International Technical Specification BCS40i and up

7–68 Administration

SPCNTCSU
The number of attempts by the administration, via table control, to set up a
semi-permanent connection which are successful.
SPDISCTC
The number of attempts by the administration, via table control, to
disconnect a semi-permanent connection which are successful.
SPCNAUAT
The number of attempts by the audit to establish a semi-permanent
connection.
SPCNAUSU
The number of attempts by the audit to establish a semi-permanent
connection which are successful.
SPCNAUAT
The number of attempts by the audit to idle a semi-permanent connection.
STN
This group is not currently supported on DMS-100 International switches.
SVCT
This group is not currently supported on DMS-100 International switches.
TFCANA
This group measures the usage of the traffic analysis / traffic separation
system. This system is used to measure traffic for specific groups classified
by Source Traffic Separation Number (STSN) and Destination Traffic
Separation Number (DTSN). The counts are collected at Source Traffic
Separation (STS) and Destination Traffic Separation (DTS) intersections.
The key to the group is the traffic analysis register number. TFCANA has
six usage registers per key:
TFANPEG
The number of network connections at each STSN X DTSN intersection as
defined in table TFANINT. The count is made at the point where an idle
destination terminal is available and a successful network connection is
made.
TFANPEG2
The extension register for TFANPEG.
TFANSU
The total setup usage at each STSN X DTSN intersection. Setup usage
(setup time) is accumulated by time stamping. Scan rate is 100 second.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–69

TFANSU2
The extension register for TFANSU.
TFANCU
The total connect usage at each STSN X DTSN intersection. Connect usage
(connect time) is collected only after setup usage at the intersection has been
collected. Scan rate is 100 second.
TFANCU2
The extension register for TFANCU.
TM
Refer to groups PM and PMTYP.
TONES
The groups measures the usage of certain tones. The key to the group is the
CLLI for tone generators, refer to table TONES. TONES has 2 usage fields:
TONENATT
The number of calls routed to the given tone. This is pegged before
determining whether the call can indeed be connected to the tone.
TONEOVFL
The number of calls routed to a given tone which cannot be connected
because the maximum allowable number of calls are already connected.
TRK
This group measures the performance of the office trunks. The key consists
of the trunk group number and the external identifier (CLLI). TRK has one
information field and 19 usage fields:
OM2TRKINFO
This displays the trunk direction, the number of total trunk circuits in the
group, and the number of working trunk circuits in the group (excluding
TK_UNEQUIPPED and TK_OFFLINE).
INCATOT
The number of incoming seizures recognized on this group.
PRERTEAB
The number of incoming attempts abandoned before routing can be
completed.
INFAIL
The number of events on a trunk which appears to have or actually has
originated a call, which indicate a possible need for maintenance action,

DMS-100 International Technical Specification BCS40i and up

7–70 Administration

have accordingly caused the generation of a log message, and have resulted
in a call failure if indeed a call was in progress.
NATTMPT
The number of times routing directed an outgoing trunk call to this trunk
group.
NOVFLATB
The number of times a call, allowed to access to the given trunk group,
overflows the group and is routed onwards, because on idle trunk is
available.
GLARE
The number of times a previously selected trunk had to be dropped because
the peripheral module detected an origination before it could seize the trunk,
and the customer sub-group data indicated that this office should yield to
glare.
OUTFAIL
The number of occurrences of error on an outgoing trunk after an attempt
has been made to seize the trunk. The trunk will be released and a log
message generated.
DEFLDCA
The number of calls prevented from accessing this trunk group although
they were routed to it, due to the action of network management controls.
DREU
The usage count of the amount of time (in hundreds of seconds) during
which directional reservation is activated for this two-way group. Scan rate
is 100 second.
DREU
The usage count of the amount of time (in hundreds of seconds) during
which protective reservation is activated for this two-way group. Scan rate
is 100 second.
TRU
The usage count for the number of trunks found to be in tk_cp_busy,
tk_cp_busy_deload, or tk_lockout states. Scan rate is 100 second.
SBU
The usage count for the number of trunks found to be in tk_pm_busy,
tk_remote_busy, tk_system_busy, tk_carrier_fail, or tk_deloaded states.
Scan rate is 100 second.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–71

MBU
The usage count for the number of trunks found to be in tk_man_busy,
tk_seized, or tk_nwm_busy states. Scan rate is 100 second.
OUTMTCHF
The number of attempts to get a network path from an incoming trunk or
line to a selected trunk of this group, which fail because of network
blockage.
CONNECT
The number of outgoing seizure attempts on this trunk group which appear
to have resulted in successful connections, since they have not been
followed by indications of glare or seize failure.
TANDEM
The number of incoming calls on this group which are initially routed to an
outgoing trunk group.
AOF
Not supported on DMS-100 International switches.
ANF
Not supported on DMS-100 International switches.
TOTU
The total trunk group usage. The sum of TRK_TRU plus TRK_SBU plus
TRK_MBU. Scan rate is 100 second.
TRMTCM
This group measures the usage of Customer Miscellaneous treatments. Only
the usage fields listed are supported by International.
TCMUNDT
Undefined treatment. The default value for entries in Class of Service
screening and Prefix treatment tables when no treatment is required.
TCMPDIL
Partial dial treatment. The treatment given when at least one digit has been
dialed, but not enough to complete the call.
TCMPSIG
Permanent signal timeout treatment. The treatment given when no digits
have been dialed before timeout.
TCMVACT
Vacant code treatment. The treatment given when no valid translation can
be determined for the dialed digits.

DMS-100 International Technical Specification BCS40i and up

7–72 Administration

TCMBLDN
Blank directory number treatment. The treatment given when an unassigned
directory number is dialed.
TCMTRBL
Trouble intercept treatment. The treatment given when a line or trunk calls a
line with the plug up (PLP) option assigned.
TCMANCT
Machine intercept treatment. This treatment can be used for routing of
disconnected or out-of-service directory numbers to an announcement.
TCMDISC
Disconnect Timing treatment. The treatment given when a line fails to go
on-hook within 10 seconds after the other party terminates the call.
TRMTCU
This group measures the usage of Customer Unauthorized treatments. Only
the usage fields listed are supported by International:
TCUORSS
Originating service suspension treatment. This treatment is given when a
line with denied origination (DOR) or suspended service (SUS) is assigned.
TCUDNTR
Denied terminating treatment. This treatment is given when a call is routed
to a line with denied termination (DTM) assigned.
TCUFNAL
Feature not allowed treatment. This treatment is given when a line tries to
access a feature for which he is not authorized to use.
TCUNACK
Negative acknowledgement treatment. This treatment is given when a
subscriber’s feature request cannot be performed due to some feature
interaction or feature restriction. Also given as a treatment to an
interrogation attempt which is correctly dialed but the feature status
interrogated is not in effect.
TRMTCU2
This group is not currently supported on DMS-100 International switches.
TRMTER
This group measures the usage of Equipment Related treatments. Only the
usage fields listed are supported by International:

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–73

TERSYFL
System failure treatment. The treatment that is applied if the call must be
aborted due to a switching unit failure, whether hardware or software.
TERRODR
Reorder treatment. This treatment is given to calls for which distorted
signals are received during dialing or in-pulsing.
TERINBT
Inbusy treatment. The treatment is given to calls routing to a line which is in
INB state.
TRMTFR
This group measures the usage of Equipment Related treatments. Only the
usage fields listed are supported on DMS-100 International switches:
TFRBUSY
Busy line treatment. This treatment is given when a line tries to route to
another line which is busy and call waiting is not in effect, which is his own
line, the line has been seized for testing, or the line is out of service.
TFRCONF
Confirm tone treatment. This treatment which is given when a subscriber
tries to access a feature and is successful. Also given as a treatment to an
interrogation attempt which correctly dialed and the feature status
interrogated is in effect.
TFRILRR
International line restrictions treatment. This treatment is given to a line
which tries to route to a translation class for which that class has been denied
by the ILR option.
TFRIWUC
International wakeup call treatment. This treatment is given to a line which
answers a wakeup call activated through the WUC casual feature.
TROUBLEQ
This group measures the number of times the system refers a line to a queue
for diagnostics. The key is the queue type. TROUBLEQ has one
information field and three usage fields:
TROUBLEQ_OM_INFO
This displays the size of the queue.
TRBQATT
The number of times the system referred a line to this queue for diagnostics.

DMS-100 International Technical Specification BCS40i and up

7–74 Administration

TRBQOCC
The number of lines in the queue when the queue was sampled. Scan rate is
100 second.
TRBQOVFL
The number of times a line was sent to this queue for diagnostics but could
not be placed on the queue because the queue was full.
TS
This group measures the performance of the time switch usage on the
peripheral face of the network. TS has the following fields:
TS0
The usage count of the peripheral-side time-switch 0.
TS1
The usage count of the peripheral-side time-switch 1.
TS2
The usage count of the peripheral-side time-switch 2.
TS3
The usage count of the peripheral-side time-switch 3.
TS4
The usage count of the peripheral-side time-switch 4.
TS5
The usage count of the peripheral-side time-switch 5.
TS6
The usage count of the peripheral-side time-switch 6.
TS7
The usage count of the peripheral-side time-switch 7.
UTR
This group measures the usage of the Universal Tone Receivers. UTRs are
requested for digit collection by both DIGITONE lines and MF trunk calls.
The key to the group is the peripheral range. UTR has one information field
and 10 usage fields:
UTR_OMINFO
This displays the PM type, the XPM number and the number of UTRs
equipped for the peripheral.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–75

UTRSZRS
The number of times a UTR has been assigned in response to a request.
Calls failing to get a UTR will not proceed to the digit collection phase.
UTROVFL
The number of times a request for a UTR could not be satisfied because all
available UTRs were busy.
UTRQOCC
The usage count of the number of requests in the wait queue for UTR. Scan
rate is 10 second.
UTRQOVFL
The number of attempts to secure a position in the wait queue which were
denied because the queue was full.
UTRQABDN
The number of UTR requests which are deleted from the wait queue because
the requestor had given up.
UTRTRU
The usage count of the number of UTR currently available. Scan rate is 10
second.
UTRSAMPL
The number of times the usage registers UTRQOCC and UTRRTRU were
updated.
OMs For International subscriber features
Operational measurements are provided for the following subscriber features
on the DMS-100 International switch:
• ADL Abbreviated dialing
• CDA Call diversion to announcement
• CDO Call diversion to operator
• CDS Call diversion to subscriber
• CDB Call diversion on busy
• CDF CALl diversion fixed
• CWT/CCW Call waiting/cancel call wait
• IDND International do not disturb
• ESG Emergency service group
• HTL Hot line
• ICR International call recording
• ICT International call transfer

DMS-100 International Technical Specification BCS40i and up

7–76 Administration

• ILR International line restrictions

• INDC International no double connect
• PMC Printed meter check
• SCR Selective charge recording
• WLN Warm line
• 3WC 3 (three) way call
• 6WC 6 (six) way call
• TWC Three way call
• SWC Six way call
These OMs are used by operating company administration monitor the usage
and performance of subscriber services. They report events such as the
following:
• Attempt to activate feature: subscriber activates CDS on the line.
• Attempt to deactivate feature: subscriber deactivates CDS on the line.
• Attempt to program feature: subscriber with ADL programs an
abbreviated code to be associated with a target number.
• Attempt to interrogate feature: subscriber with INDC uses interrogation
to query whether or not the feature is active.
• Attempt to use feature: subscriber with ADL uses abbreviated code to
dial the target number.
• Feature denial: a call terminating on a subscriber with CDO receives
busy treatment because there is an active call already routed via that
terminator.
• Abandons: a subscriber with CWT is involved in an active call and does
not respond to another incoming call.
• Failure due to software/hardware resources: subscriber attempts to use
3WC but is unable to do so because all three port conference circuits are
unavailable.
• Failure due to customer error: subscriber attempts to use the 3WC
feature but is unable to do so because the line does not have permission
to use this feature.
• Failure due to datafill error: a call terminating on a subscriber with
CDS receives busy treatment because of that subscriber’s incorrect
programming of the forwarding DN.
As an event occurs for a feature, the appropriate field is incremented or
“pegged”. Each of these events is represented by a field in a feature’s OM
group. Not all the above events are applicable to all features: a feature may
have a subset of the above. A particular feature may require more than the
above event pegs due to feature specifics. For example, the ILR feature
allows the subscriber to specify a particular call restriction class (for

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–77

example, Deny National and all International calls). OM pegs are also
required on a call restriction basis.

Network management (NWM)

The DMS-100 Family provides a wide range of NWM features to ensure the
optimum use of available facilities in the face of abnormal loads and
equipment or facility failures. Overload conditions, where the demand for
service exceeds the ability of the trunk groups or the common control
equipment to provide satisfactory service, are handled by network
management by the immediate application of controls to isolate and contain
the overload. Where a control is recommended only in a particular member
of the DMS-100 Family, it is indicated by identifying that family member in
the subsection title.
Network management (VDU)
The NWM MAP is the main interface to the DMS-100 Family system and
can be local or remote. This MAP is used for office maintenance and can
also be used as the network management position when the function is
remoted, providing that the appropriate levels and menus of the NWM
functions are accessed. Four network management and system functions are
performed from the VDU:
• Display continuous system status information, in a fixed format, which
provides the network manager with an overall impression of the “health”
or status of the DMS-100 Family office. This display is updated every
minute. Display temporary status information by entering commands
from the menu.
• Display a menu of assorted network management commands.
• Determine what NWM action is required to clear or alleviate an
overflow condition.
• Output threshold data and network management operational
measurements.
Continuous status information is displayed for five conditions:
• Indication of the type(s) of active NWM controls in the DMS-100
Family office.
• The total number of incoming seizures in the office.
• The percentage of test calls which are not satisfying receiver attachment
delay recorder time limits.
• The percentage of CPU real-time usage.
• The time of the last re-initialization within the previous 30-minute
period.
The two types of temporary status displays available, trunk group and
control, are used for monitoring purposes and observing the effect of active

DMS-100 International Technical Specification BCS40i and up

7–78 Administration

NWM controls. These displays remain on the VDU until they are erased or
replaced by others via NWM command input.
The trunk group status display provides the identity of trunk groups, the
number of calls offered, the number and percentage of calls overflowing,
attempts per circuit per hour, connections per circuit per hour, the measure
of traffic usage, the number of calls deflected and the name of any active
control on the trunk group.
The control status displays are divided into four categories or levels. These
levels are called the group, code, route and automatic controls. All of these
levels display the different controls (available on a particular level) which
are active in the DMS-100 Family and their total number.
The menus of commands available to the network manager are distributed
among the different levels of displays provided. Any command display on
any particular level may be entered.
The network manager may at any time display operational measurement data
on the VDU by accessing the DMS-100 Family operational measurement
system. Network management in the DMS-100 Family employs a
teleprinter which is primarily used for scheduled hard-copy printout of
NWM and OM reports. The VDU and printer may be located remotely.
Status board lamp display
The status board provides the network manager with a lamp display, via
Signal Distributor (SD) points, of the status of selected trunk groups
(normally toll). Lamps are illuminated when all trunks in a group are busy.
A maximum of 32 trunk groups can be associated with a single SD point
which operates only when all groups are in the busy state. A maximum of
1792 SD points can be provisioned. The trunk groups can be outgoing or
two-way groups.
The status board lamp display is updated periodically at an office definable
interval. Data table Office Engineered Parameter (OFCENG) field name
Network Management Trunk Group Busy Lamp Update (NWMTGBLU) is
used when changes to the interval are required. The interval is in units of
ten seconds with a default value of two minutes.
The status board can be located locally or remotely. A purchased telemetry
unit may be used to remote the status board to other buildings.
Network management controls
Several network management controls are currently available in DMS-100
Family.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–79

Directional reservation equipment (DRE) (DMS-200)

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
completing traffic. Originating traffic is skip-routed, it overflows to the next
group.
DRE is applied in steps or levels to indicate the amount of control desired.
These levels are directly associated with the number of trunks to be reserved
in a trunk group. Levels are in the range of 1 to 63 trunks.
Whenever DRE is in effect (active), it skip-routes originating traffic when
the number of idle trunks in the group is less than or equal to the level value.
In this way the idle trunks are reserved for completing traffic which has
already penetrated the network.
Once DRE is enabled and the level setting is reached, 100 percent of all
traffic, direct and alternate, offered to the two-way group will be
skip-routed. The rerouting will continue until the number of idle trunks in
the group increases past the trigger (level) point.
Protective reservation equipment (PRE) (DMS-200)
PRE is a control that is similar to DRE, but PRE acts only on
Alternate-Routed (AR) traffic offered to the two-way or one-way outgoing
trunk group. Direct routed traffic is allowed full access. Once PRE is
enabled and the level setting is reached, 100 percent of the AR traffic to the
two-way home final is skip-routed unless a final route is involved in which
case an NCA condition results.
Cancel to (CanT)
CanT is a control that limits traffic attempts over selected one-way outgoing
or two-way trunk groups and routes these attempts to a specified
announcement. This control cancels a preset percentage of the traffic
offered to a particular trunk group. The percentage level can be set in the
range 1 to 100 percent in l percent steps. If any percentage of direct routed
traffic is affected, then 100 percent of alternate-routed traffic is affected.
Traffic that is affected by cancel to can be routed to one of three
announcements:
• No Circuit Available (NCA)
• Emergency Announcement 1 (EA1)
• Emergency Announcement 2 (EA2)

Cancel from (CanF)

CanF is a control that limits traffic attempts overflowing from selected
outgoing or two-way trunk groups. Cancel from is similar to cancel to in its
control percentages, level settings from direct and alternate traffic, and
available routes to announcements. If any percentage of direct routed traffic
is affected, then 100 percent of alternate-routed traffic is affected.

DMS-100 International Technical Specification BCS40i and up

7–80 Administration

Selective trunk reservation (STR)

The STR feature dynamically observes the occupancy of an outgoing trunk
group and applies one of two level filters to the offered traffic at high levels
of trunk group occupancy. When the number of idle trunks in a group
reaches a threshold (level 1) as defined by the network manager, a given
percentage of traffic in that group, designated Hard-To-Reach (HTR) is
blocked.
As the number of idle trunks reaches a second threshold (level 2), traffic is
further controlled. HTR information is entered by NWM via the code
control. High-usage trunk groups can only be compared to one level, while
full or final groups are compared to both levels.
Incoming trunk busy (ITB)
This control allows the network manager to restrict incoming attempts to an
overloaded switch. This is done by selectively removing from service
(busying out) a percentage of incoming trunks that have Remote-Make-Busy
(RMB) capability.
The control percentage level can be in the range of one to 100 percent. This
percentage applies to the number of working trunks in the incoming trunk
group excluding the number which are off-line such as, Installation Busy
[INB]. In order to keep the percentage setting constant, the number of
incoming trunks in the NWM busy state is periodically adjusted to
compensate for trunks being returned or removed from service .
The network manager has the ability to query any incoming trunk group (by
short CLLI) and have displayed the number of trunks in the group, the
number maintenance busy and the number NWM busy trunks. Also
displayed is the percentage level setting.
Reroute control (RRTE)
The RRTE allows a percentage of traffic to be deflected from a designated
trunk group route to a different trunk group route in the routing chain. The
percentage level setting can be in the range of 1 to 100 percent.
A maximum of 256 reroute numbers may be constructed in data table
REROUTE. Each reroute number can, in-turn, point (via subtable
NWMRROUT) to a maximum of 16 combinations of routes and control
percentage level settings. Only one of these combinations can be active at
any one time. Multiple reroutes can exist on different trunk groups
simultaneously.
The initial datafill and any subsequent changes that may be required for the
above two tables is a DMO function performed via the table editor. The
network manager can temporarily override the percentage default value set
in subtable NWMRROUT by invoking the appropriate NWM command.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–81

Flexible reroute
The flexible reroute control is a percentage based reroute which may be
activated at the MAP. It may have single or multiple vias. Up to sixteen
reroute controls with up to seven multiple vias are allowed. Flexible
reroutes are counted against the number of manual trunk group controls
allowed in the switch at any one time. Five options are supported in the
Flexible Reroute command:
• Regular/immediate reroute
• Direct routed/alternate routed traffic
• Hard to reach traffic/all traffic
• Equal Access traffic/non-equal access traffic/all traffic
• Cancel in chain return

Automatic out-of-chain reroute (AOCR) (DMS-200)

The AOCR feature provides extended routing of calls that overflow their
in-chain finals. This extended routing is allowed only if idle capacity exists
in the potential out-of-chain route. This feature activates a specified reroute
if the overflow rate on a given trunk group exceeds a threshold while the
overflow rate on the second group does not exceed another threshold.
A maximum of 64 AOCR can be set up in data table NWMAOCR. If any
other type of NWM control is on a group, AOCR is not applied. If any other
auto control is already on, it is overridden by AOCR.
Dynamic overload control (DOC)
There are two types of DOCs provided in the DMS-100 Family: internal and
DOC. The application of controls in response to an external signal is
Remote DOC, while the generation of signals because of an internally
detected overload is known as internal DOC. Remote DOC is also known as
Pre-planned (PPLN) Controls in the DMS-100 Family.
Internal dynamic overload control (IDOC) The purpose of IDOC is to
reduce the load offered to the controlling office by requesting selected
subtending or contiguous offices to implement a pre-defined set of routing
controls. IDOC is a signal that is generated and transmitted by the
controlling office in response to internally detected overload indicators.
When the controlling DMS-100 Family determines that it is approaching a
state of congestion such as, overload, it transmits a continuous control signal
to its selected office(s). To initiate this control signal, a Signal Distributor
(SD) point is enabled. The SD point is extended to facilities to the
appropriate office(s). If CCIS is available in the office the appropriate CCIS
Selective Dynamic Overload Control (SDOC) message will be sent to the
STP.

DMS-100 International Technical Specification BCS40i and up

7–82 Administration

The controlling DMS-100 Family switching system has the ability to apply
three IDOC signal level filters. The thresholds of the signal levels and the
period of their application are controlled by entries in the IDOC data tables
(NWMIDOC and NWMSD). The level (1–3) is selected by an entry in field
IDOCLEV of table NWMIDOC.
Level one is applied when the number of incoming Multifrequency (MF)
calls waiting for a receiver exceeds the On-Threshold (ONTHLD) value for
ONFILTER time, as set in table NWMIDOC. This level is deactivated if it
is less than the value set for Off-Threshold (OFFTHLD) (less than
ONTHLD) for OFFILTER time, as set in table NWMIDOC. The decision to
apply or remove the IDOC level is made every minute.
Level two is applied independently of IDOC level 1 and is active if the
percentage of time devoted to call processing by the CPU of the DMS-100
Family switch is greater than ONTHLD for ONFILTER time. This level is
deactivated when the call-processing CPU usage is less than OFFTHLD for
OFFILTER time. The decision to apply or remove IDOC level 2 is made
every minute.
Level three is applied when the system has lost call-processing capability.
The SD points which transmit control signals reflecting the status of the
IDOC levels are assigned by entries in table NWMSD. Some SD points are
wired to the status board lamp assembly, which then provides indicators of
the length of the MF receiver waiting queue, and CPU occupancy.
Pre-planned number control (PPLN)
The PPLN feature applies remote DOC in response to an external signal
from another office. This feature consists of preplanned controls that are
activated by either scan points, reception of SDOC CCIS messages or via
the NWM VDU.
Scan points may be activated by external ground, loop, or battery. In each
case the external resistance must be less than 6980 ohms; battery required is
52 volts.
A maximum of 256 pre-plans can be remotely activated over 256 scan
points. These values are set by office parameters NWMPPLN and NWMSC
respectively. Each pre-plan can implement one of the seven trunk group
controls over a series of trunk groups (maximum 32 trunk groups). The
seven trunk group controls have an activation order:
1 IRR Immediate Reroute
2 DRE Directional Reservation Equipment
3 PRE Protective Reservation Equipment
4 CANT Cancel To

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–83

5 SKIP Skip
6 STR Selective Trunk Reservation
7 HUNT (Regular Translations)
8 RR Regular Reroute
9 CANF Cancel From
When a specific pre-plan is assigned to either DRE or PRE, up to 63 trunks
may be reserved.
Selective incoming load control (SILC)
SILC is a substitute for the IDOC control for connected offices that cannot
or do not respond to IDOC signals (such as Equal Access [EA] interLATA
carriers). When SILC controls are activated, selected incoming calls are
blocked to reduce the amount of traffic that is accepted by the switch.
There are two thresholds for SILC controls similar to the thresholds for
IDOC levels 1 and 2 (referred to as MC1 and MC2). Each threshold has two
modes of call blocking, but only one mode may be used at a time:
• Blocking by a preset percentage of incoming calls
• Blocking by a preset gap between incoming calls (call gapping).

When incoming call gap control is used, a minimum time duration is

guaranteed between calls that are accepted by the switch. All calls arriving
before the gap has expired are blocked. When both SILC levels 1 and 2 are
active, the level 2 control is used. The individual controls for level 1 and
level 2 may be activated (enabled or disabled) for the whole NWM system
through the auto and group control levels at the MAP.
When SILC is applied on specified trunk groups, there are two results:
• The percentage setting randomly blocks a number of calls
• The gap setting blocks all calls attempting to connect during the gapping
time interval.
(Call gapping time interval can be set from 0 to 360 seconds in increments
of one second for SILC level 1 or 2. The next level of call gapping time
interval will be from 0 to 600 seconds in increments of 0.1 seconds.)
When calls are blocked, there are three results:
• Trunk states are temporarily set to lockout
• The trunk sends a start dial signal wink
• A 120 Impulse Per Minute (IPM) tone is sent on the trunk after the start
dial signal.
The start dial signal prevents senders from being held in connecting offices.
The 120 IPM tone warns the calling party that the call is not completed,

DMS-100 International Technical Specification BCS40i and up

7–84 Administration

which in turn results in less holding time on network resources during

congestion and reduces the number of trunk troubles resulting from the
blocked call.
Receiver attachment delay recorder (RADR)
The RADR feature is not directly associated with any NWM control and is
controlled by a data table. RADR is a process by which test calls
originations are generated for the purpose of timing the interval period from
the time of the original request for attachment to a MF receiver, to the actual
time of connection.
The RADR feature records peg counts of the actual number of test calls, the
number of test calls delayed more than three seconds (lower threshold) and
the number of test calls delayed more than seven seconds (average
threshold). These peg counts are provided in operational measurements
system table RADR, and the thresholds are customer definable.
The data table (RADR) contains fields whose values can be set by the table
editor to suit the measurement requirements. RADR threshold settings
(lower or upper) can be set from 0 to 20 seconds in 1 second intervals.
Line load control (LLC) (DMS-100)
The Line Load Control (LLC) for DMS-100 is a separate feature which is
not part of the NWM group of controls, but can be manually activated or
deactivated from the MAP. The LLC feature is a means of limiting the
amount of traffic handled by a DMS-100 Family office, by allowing only
specially designated lines to originate calls. LLC has no effect on
terminating calls.
All lines connected to a DMS-100 switch are designated, on service-order
authority, as essential or non-essential by entries in the OPTLIST field of the
LENLINES data table. The Essential Line (ELN) designation is available
to: single party lines (1FR), coin lines (CCF, CSP, CDP), and two-party lines
(2FR). When LLC is activated, only those lines designated as essential are
allowed to originate calls.
A non-essential line is routed to lockout when it originates. Essential
service protection provides service to non-essential lines while providing
priority service to essential lines. When LLC is deactivated, all lines in the
lockout state are returned to service.
Essential service protection (ESP) (DMS-100)
When traffic reaches extreme levels, ESP guarantees a standard grade of
service to lines marked as essential . It is controlled by a manual command
from the MAP or equivalent. When ESP is not in effect, these lines will
receive the same grade of service as all other lines. Once ESP has been put
into effect, the system provides equitable service to all non-essential lines,
with the maximum throughput possible. When ESP is enabled, essential

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–85

lines are given preferred service. Originations from these lines will be
handled before all others.
ESP can be queried to determine its status (on/off). The information printed
will also identify the user performing the enable or disable operation.
Network management displays
The status of the network is displayed on the screen of the MAP VDU and in
levels, where the top-level display gives an overall picture of the whole
network and the lower-level display reflects the status of the various NWM
controls. The network manager can select a desired level by entering the
appropriate command from the menu, and then telescope from the higher to
lower levels.
Network management level display
The NWM level display is outlined in figure 7–7. The first three lines of the
VDU display provide a general view of the traffic-handling capability of the
DMS-100 Family. This display appears at the top of the telescoping levels
available to the network manager. The next lower line displays the variable
information and is up-dated every minute to reflect the constantly changing
traffic load, and controls applied or removed by the network manager. The
individual display fields and ranges in values are as follows:
Display field Ranges Description

CTRL G, C, R G =Group Control(s) (Grpctrl) active

A, or . C =Code Control(s) (Codectrl) active
a, or . R =Route Control(s) (Rtectrl) active
A =Automatic Control(s) (Autoctrl) active
a =Automatic Control(s) disabled
. =Inactive control
ITS 0–9999 Displays the number of incoming trunk
seizures including “abandons” and “failures”
that occurred in the last minute.
RADR 0–99% Displays the percentage of test calls within the
last minute whose delay time was greater than
the lower RADR threshold value.
CPU 0–99% Displays the percentage of time within the last
minute that the central processing unit was
executing call-processing or higher priority
tasks.
INIT Hours–0–23 This field indicates the time of the last office
Minutes 0–59 reinitialization (warm or cold start, reload)
when re-initialization has occurred within the
last 30 minutes. If not then entry reads “00”.

DMS-100 International Technical Specification BCS40i and up

7–86 Administration

Display field Ranges Description

IDOC 3, 2, 1 This field indicates if IDOC is active or

or . Inactive.
Active 3, 2, or 1 = Level of IDOC
Inactive = .
FS 0–99 This field displays the number of final trunk
groups in an overflow condition.
SCLLI Short Common Language Location Identifier
(CLLI) Adjacent to FS, this field displays the
CLLI identities of up to six final trunk groups
associated with FS. If more than six are in the
overflow condition, the most recent are
displayed.
Ctrl ITS RADR CPU lnit IDOC CS FS
GCR XXXX XX% XX% hh:mm XXX X XX

Figure 7–7
NWM level display

NWM
0 Quit /
1 /
2 /
3 /
4 Display___ /
5 ___Finals___ /
6 ___Groups___ /
7 /
8 /
9 /
10 /
11 /
12 /
13 /
14 Page /
15 AutoCtrl /
16 GrpCtrl /
17 CodeCtrl /
18 RteCtrl /
USER ID
hh:mm

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–87

Detailed network management levels

In each telescoping level of network management, different interactive
responses are output by the system immediately after entering a menu
command. From the top NWM level display, six menu levels can be
accessed by the telescoping process:
• Display Finals
• Display Groups
• Autoctrl
• Grpctrl
• Codectrl
• Rtectrl

Display finals/groups “Display finals” displays the traffic-related peg

count and usage data and the group controls that are active for all final trunk
groups in the office. “Display groups” display is similar to “Display finals”
but the trunk groups are selected individually by the network manager.
Figure 7–8 outlines the top NWM level “display finals” trunk group data for
“finals” and “groups” under the following headers.
Display header Description

Ofrd OFFERED. This field displays the peg count of those calls
allowed access to the final trunk group. The peg count
includes those calls deflected by network management.
Ovf OVERFLOW. This field displays the peg count and
percentage (%) of calls overflowing from trunk group. The
percentage calculation does not include those calls deflected
by NWM.
ACH ATTEMPTS PER CIRCUIT PER HOUR. This field displays
the outgoing call attempts per circuit per hour in the trunk
group.
CCH CONNECTIONS PER CIRCUIT PER HOUR. This field
displays the number of outgoing connections per circuit per
hour in a final trunk group.
ICCH INCOMING CONNECTIONS PER CIRCUIT PER HOUR.
This field display is similar to CCH but pegs the incoming
connections.
CCS HUNDRED CALL SECONDS PER HOUR. This field
displays the traffic usage on a trunk group. Both incoming
and outgoing usage is included.
Defl DEFLECTED. This field displays the number of calls
deflected from a trunk group by any of the following controls:
DRE,.PRE, SKIP or CanT.

DMS-100 International Technical Specification BCS40i and up

7–88 Administration

Display header Description

Ctrl CONTROL. This field displays the identity of up to three

controls which are active on a trunk group. Possible controls
are DRE, PRE, Cant, CanF. An * asterisk following the third
control identifier indicates that more than three controls are
active.
SCLLI SHORT COMMON LANGUAGE LOCATION IDENTIFIER.
Displays the final or selected SCLLI such as,TORO1.
CLLI FULL COMMON LANGUAGE LOCATION IDENTIFIER.

Figure 7–8
Display finals commands

Ctrl ITS RADR CPU Init IDOC Cs DCR Fs sclli1 sclli4

GCRA XXXX XX% XX% hh.mm XXX X XXXX XX sclli2 sclli5
sclli3 sclli6

NWM Display Groups RALNC030214

0 Quit_ /Finals
2 /SCLLI CLLI Ofrd Ovfl ACH CCH ICCH CCS Defl
3 /RAL214 RALNC030214 234 40 17% 35 28 20 135 17
4 Display_ / Ctrls:
5 _Finals_ /
6 _Groups_ /
7 /
8 /
9 /
10 DCRMOCH_ /
11 /
12 /
13 IntCCtrl /
14 Page /
15 AutoCtrl /
16 GrpCtrl /
17 CodeCtrl /
18 RteCtrl /

Note: IntCCtrl (menu item 13) is present in DMS-200 or DMS-300 offices only.

Auto controls The auto control level is accessed from the top NWM level
by the input command “Autoctrl.” Figure 7–9 outlines the NWM “AutoCtrl”
level display. It displays the automatic controls that are active or disabled.
The types of automatic controls available are:
• IDOC Internal Dynamic Overload Control (1–3)
• PPLN Preplan Number Control (0–255)
• AOCR Automatic Out-of-Chain Reroutes (0–63)
• SILC Selective Incoming Load Control (level 1 or 2)

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–89

• SDOC Selective Dynamic Overload Control (1–3)

Figure 7–9
AUTOCTRL menu and example display

Ctrl ITS RADR CPU Init IDOC Cs DCR Fs sclli1 sclli4

GCRA XXXX XX% XX% hh.mm XXX X XXXX XX sclli2 sclli5
sclli3 sclli6

AutoCtrl AutoCtrl
0 Quit_ / IODC PPln AOCR SDOC
2 /
3 / Active 321 0 0 0
4 List_ / Disabled 31 0 0 0
5 Apply_ /
6 Remove_ /
7 Disable_ / AUTOCTRL:
8 Enable_ /
9 _IDOC_ /
10 _PPln_ /
11 _AOCR_ /
12 /
13 _SDOC_ /
14 Page /
15 /
16 /
17 /
18 /

Group controls The group controls level is accessed from the top NWM
level by the input command “GrpCtrl.” The commands in this menu enable
the network manager to list, apply, or remove any of the group controls on
selected trunk groups.
Figure 7–10 outlines the NWM “Grpctrl” level display. Group controls are
available in the DMS-100 Family:
• DRE
• PRE
• CanT
• Skip
• CanF
• STR
• ITB
• SILC
• TASI (DMS-300)

DMS-100 International Technical Specification BCS40i and up

7–90 Administration

Group controls can be applied to any trunk group as required by the network
manager by telescoping to the appropriate control menu. Once a group
control has been activated, it is displayed on NWM level display.
Figure 7–10
GRPCTRL menu and example display

Ctrl ITS RADR CPU Init IDOC Cs DCR Fs sclli1 sclli4

GCRA XXXX XX% XX% hh.mm XXX X XXXX XX sclli2 sclli5
sclli3 sclli6

GrpCtrl GrpCtrl Selected Group: RAL214 RALNC030214 IC

0 Quit / DRE PRE CanT CanF Skip ITB STR FRR TASI
2 / 32 25 11 17 9 7 41 0 70
3 /
4 List_ / GRPCTRL:
5 Apply_ /
6 Remove_ /
7 _DRE_ /
8 _PRE_ /
9 _CANT_ /
10 _CANF_ /
11 _SKIP_ /
12 _ITB_ /
13 _STR_ /
14 _FRR_ /
15 _TASI_ /
16 Page /
17 Select_ /
18 /

Note: TASI (menu item 15) is activated only on a DMS-300 with feature package NTX308AA.
Similarly, the heading TASI appears only on a DMS-300 switch; the value represents the number of
active controls. DMS-300 has TASI instead of STR.

Administration of manual controls

The DMS-100 Family provides the capability of accepting manual control
inputs from the network management personnel via the MAP designated for
this function either locally or remotely.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–91

Activation of manual controls

In the DMS-100 Family, when any network management control has to be
implemented, the appropriate NWM level is entered by means of the
telescoping process. Once the appropriate level has been entered, the
relevant information regarding the control has to be input such as, trunk
group CLLI, control type, code type, or announcement type.
When the control information has been input, the control is activated and the
MAP displays the appropriate control. Typical displays provided for various
control types are outlined in figures 7–9 and 7–10. In addition to the MAP
display, any control activated or deactivated is reported by system log
(hardcopy) report provided to the network manager.
In each telescoping level of the NWM MAP position, the system responses
are output by the system immediately after entering a menu command.
These responses indicate, in text format, either the acceptance or rejection of
the input command. The following is a typical input required for the
Autoctrl control level (see Network Management System Reference Manual,
297-1001-453).
Autoctrl Level:
The commands in this menu enable the network manager to apply automatic
controls manually.
The APPLY command format:
APPLY ctrl index [fsclli]
where:
ctrl = Type of Automatic Control.
IDOC – Internal Dynamic Overload Control
PPLN – Preplan Number Control
AOCR – Automatic Out-of-Chain Reroute
SILC – Selective Incoming Load Control
SDOC – Selective Dynamic Overload Control
index = Index to type of Automatic Control
IDOC – 1–3
PPLN – 0–255

DMS-100 International Technical Specification BCS40i and up

7–92 Administration

AOCR – 0–63
SILC – Level 1022
SDOC – 1–3
Note: The brackets [ ] indicate that the enclosed parameters are
optional.

Compound control deactivation

The DMS-100 Family provides the network manager the capability of
deactivating all presently activated manual controls. All controls are
deactivated by the command, “REMOVE.” Typical examples for various
controls are:
• Code Control
The REMOVE command removes the specified control and parameter
from the specific code or from ALL codes of the specified code type.
The REMOVE command format for code control is:
REMOVE ctrl blocktype type [code [snpa/sts
ALL] ALL]
where:
ctrl = CBK (Code Blocking), HTRF, PRP
blocktype = PCT or GAP (for CBK only)
type = CC, AC, NAC, or PFX
code = 1 to 15 digits
ALL = All codes specified by ctrl
snpa/sts = Serving NPA code
ALL = All snpa/sts specified by ctrl
Note: The brackets [ ] indicate that the enclosed parameters are
optional.

• Group Control
The REMOVE command removes the specified control from all trunk
groups or if ALL is not entered, from the trunk group selected for the
control. The REMOVE command format for group control is:
REMOVE ctrl ALL

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–93

where:
ctrl = type of group control, DRE, PRE, CanT, CanF, Skip, ITB,
STR, or SILC.
• Route Control
The REMOVE command removes the active route control defined by the
parameter RrtNo, or all active reroute numbers.
Any controls that have been deactivated are no longer displayed on the
NWM MAP. Also this is logged in the log system and an output report
provided. The REMOVE command format for route control is:
REMOVE rrte [rrt no
ALL]
Note: The brackets [ ] indicate that the enclosed parameters are
optional.

Enable and disable commands

In addition to the APPLY and REMOVE commands, ENABLE and
DISABLE may also be used only at AUTOCTRL. There are two command
formats:
ENABLE cntrl Index [fsclli]
ALL
DISABLE cntrl Index [fsclli]
ALL
ENABLE allows the DMS-100 to automatically activate/deactivate the
control.
DISABLE prevents the DMS-100 from automatically activating/deactivating
the control. The control can still be manually activated/deactivated.
Limits in number of manually controlled groups
DMS-100 Family provides the capability of implementing manual controls
simultaneously on all the existing trunk groups in the office. Certain
controls are limited, SILC activated on only 256 trunk groups, and automatic
out-of-chain routing is restricted to 64 groups.
Derivation of control percentages
In the DMS-100 Family, when a percentage of traffic has to be blocked or
re-routed by the various controls, it is entered as an input parameter for the
required control. The percentage level provided in DMS-100 Family ranges
from one to 100 in steps of 1 percent.

DMS-100 International Technical Specification BCS40i and up

7–94 Administration

Traffic counts
In the DMS-100 Family, certain OM tables are of particular interest to the
network manager. Summary reports of these measurements can be directed
to a network management output device (usually a teleprinter) at intervals
scheduled by the network management personnel on an auto (normally 15 or
30 minutes or optionally at 5, 10, 15, 20 or 30 minutes), half hourly, hourly,
daily, weekly or monthly basis.
These are some of the reports provided for network management in the
operational measurements:
• Code Blocking Reports (CBK)
• Reroute Report (RRTE)
• Receiver Attachment Delay Report (RADR)
• Preroute Peg Count Reports (PRP)
• Trunk group report (TRK)

The following example details the information provided by the CBK OM

table.
Field name Description Register
provision

CBKKEY Key to the Code Block 1 per Code

Table code type:
AC for Area Code
CC for Country Code
NAC for Non-Area Code
PFX for PREFIX
Digit – register: The code to block serving
number plan area
CBKLVL Information Field. The code blocking level in 1 per Code
percent.
CBKANN Information Field. The announcement or tone to 1 per Code
which calls may be rerouted.
CBKCNT Peg count of the number of calls blocked by the 1 per Code
control

Status output
The network manager can list the various controls implemented in the
DMS-100 Family. The information is a typical display on the network
management MAP for the various controls (see Network Management
System Reference Manual, 297-1001-453.)

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–95

Grpctrl Level
The LIST command displays a list of trunk groups which have the specified
control in effect on them.
LIST ctrl [fsclli1–––––––fsclli9
ALL]
where:
ctrl = Type of group control, PRE, DRE, CanT, CanF, Skip,
ITB,STR, and SILC
fsclli = Full or Short form CLLI up to nine can be entered.
ALL = All fsclli specified by ctrl.
The following is displayed on the network management MAP.
Display Description

SCLLI Short CLLI of the trunk group

CLLI Full CLLI of the trunk group
Type This display has the following type values:
AR: Alternate Routed Traffic
DAR: Direct and Alternate Routed Traffic
Level This display indicates either the number of trunks reserved or
the percentage of traffic to be rerouted:
· 1 to 63 (number of reserved trunks)
· 1 to 100 (percentage setting)

Ann This display indicates the announcement type to which traffic

is deflected. Typical announcements are NCA, EA1 and
EA2.
NWMBsy This display indicates the number of trunks that have already
been set NWM busy
Value = 0–9999
Source This display indicates the source that was used to apply the
control. The display has three values:
AUTO: control applied by automatic process.
MANUAL: control applied manually.
CCIS: control applied by CCIS trunking network.

DMS-100 International Technical Specification BCS40i and up

7–96 Administration

Line load control (LLC) MMI (DMS-100)

LLC features are applied or removed by a non-menu command. The LLC
command format is:
LLC ON
OFF
where: LLC ON = locks out all lines which have not been designated
as essential (ELN) in the OPTLIST field of table
LENLINES.
If LLC ON is entered twice, the second entry has
no effect.
A log message *** LLC100 is originated when
LLC ON is entered, and a critical alarm is set.
where: LLC OFF = restores originating service to non-essential lines
previously locked out by LLC ON, and originates
log message LLC101, indicating that LLC is
deactivated. The critical alarm is replaced by a
no-alarm condition.

Database management
The database management in DMS-100 Family provides the tools and
capabilities which enable the user to modify office data resident in memory.
The following defines the various database management and administration
features available in the DMS-100 Family switching system.
Memory alteration
The DMS-100 Family incorporates a flexible and efficient means of altering
the contents of memory (program parameters and office data update).
Office data modification
Office data modification may be used to add, change, or delete routine
related office data, office parameters and trunk data in local and remote
locations. In the DMS-100 Family system, office data updates are termed as
DMOs. MDC customers can have the capability to modify LENs, DNs, or
features assigned to lines in their customer group only by the use of the
customer station rearrangement feature.
TTY/(VDU) entry for immediate activation The data modification
facility permits fast and accurate input of DMOs and provides readily
understandable machine output. All data modification programs are resident
in DMS-100 Family systems, and as such, no special procedures need be
followed for loading or execution.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–97

The data modification system is data table oriented. The Table Editor (TE)
provides a number of table oriented commands for use by maintenance and
administrative personnel in executing DMOs.
DMOs are entered by typing in table editor commands and the associated
parameters using the keyboard of a teleprinter or VDU, which may be a
designated MAP or a dedicated DMO I/O terminal. The MAP may be
located either locally or remotely.
Extensive use is made of validity and error checks and system safeguards to
avoid functional input errors which may cause a loss of or translation data
integrity. Failure to pass the checks will abort the order (command) and
output an error message to the operator. This error message is in sufficient
detail to identify clearly the reason for failure. Diagnostic messages and/or
related data are output on the TTY or VDU screen.
TTY/VDU entry in pending order file (POF) for delayed activation
DMOs may be activated immediately or placed in a Pending Order File
(POF) in the DMS data store for activation at a later time.
The pending order file has four capabilities:
• Manual request of the pending order file dump (such as, listing by total
file, due date, or unique identifier).
• Automatic reminder output message of pending orders prior to the due
date.
• Manual activation (by either total file, due date or unique identifier).
• Orders may be activated singly or collectively.

If delayed activation is desired, the DMO input process has three

information requirements:
• The due date is the day at which those DMOs in the POF should be
executed.
• A unique identifier provides a means of labeling DMOs in each POF.
• The prompt period provides the user the means to have an automatic
message generated of POF identifiers any number of days prior to the
due date. In this way all identifiers (and thus the associated DMO) can
be checked prior to activation. While in the pending order file, DMOs
may be queried, changed or deleted.
Batch data modification DMS-100 Family systems are able to accept
DMOs presented via an input file. This feature may be used for any number
of DMOs and permits the rapid loading of changes into the machine. Data
changes can be submitted to Northern Telecom, which will in turn produce a
data file on a magnetic tape. The operating company can also create their
own data files with either the system file editor or the table editor. These
data files can be verified before activation and reside on any device.

DMS-100 International Technical Specification BCS40i and up

7–98 Administration

Memory reload
It is possible to reload the system’s memory completely and rapidly by
means of local or remote controls, or a reset terminal interface (RTIF),
utilizing automatic and manual recovery, by use of bootstrapping. See the
“Software engineering” chapter for a bootstrap loader description.
Teletypewriter (TTY) input/output
The MAP provides an interface between the maintenance personnel and
DMS-100 Family systems. The tasks performed at the MAP include general
maintenance functions (error detection and diagnosis), administration
functions (network management, customer data modification, etc.), and
trunk and line testing functions. The basic components of the MAP include
a VDU, with keyboard, a voice communication module, testing facilities and
position furniture.
Printers and TTYs are used in conjunction with the VDU for maintenance,
traffic counts, service orders, and trunk testing. Hard copies of critical status
indicators and plant and traffic data are available from the TTYs whenever
requested. The VDUs and TTYs can be located locally or remotely as per
operating company requirements.
Automatic traffic and engineering measurements
See Operational measurement on page 7–13 for operational measurements.
Memory verification
In DMS-100 Family systems, Data Store (DS) is divided into protected store
and unprotected store. The protected store contains critical system data
(such as, addresses of procedures in program store or constants), office data
(hardware configuration) and all the translation data. The unprotected
memory or store contains transient data or per-call type information. The
transient or per-call data includes items such as called number or channel
numbers, which are removed from store once the call is finished.
The DMS-100 Family switching system can make an on-line comparison of
all the data stored in protected memory with a backup magnetic tape. If any
mismatches between the backup tape and memory occur, the addresses and
contents of memory at those addresses are printed out on an input/output
device. The system has an input message capability to print out on an
input/output device all the protected memory addresses and contents of
memory stored at those addresses.
Routing of output messages
Output messages in DMS-100 Family systems can be dedicated to an output
terminal, assignable by the operating company with a backup terminal in
case the primary terminal fails. Also, all output messages in response to an
input message are output on the terminal that the input message was entered
on.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–99

Trunks out-of-service for data changes

The DMS-100 Family system software checks that the corresponding trunks
are busied out before accepting data changes affecting trunk operation. If
they are not, the data modification command will be rejected by the system.
Database facilities and structures
The database software provides six facilities for defining, accessing, and
modifying system data:
• Table Editor: The table editor facility provides a man-machine
interface to system data.
• Dump/Restore: This is a process carried out by Northern Telecom
when an office is to receive new software. It entails dumping a copy of
the office data to tape, dropping sync, loading the inactive side with the
new software and then using the batch DMO methods to restore the data
tables on the inactive side. Activity is then switched and the machine is
then running on the new software.
• Pending Order File: The Pending Order File (POF) provides facilities
for storing data modification orders and for retrieving them at a specified
time for execution.
• Journal File: The Journal File (JF) provides facilities for recording
DMO on tape or disk so that data tables can be restored if the switch
should fail and require a system reload.
• Operating company personnel are allowed access to commands and
tables at the MAP being used
• MDC customers can be allowed access for modification of data
associated with their customer group through customer station
rearrangement or customer network change features.
Table editor (TE)
The DMS-100 Family table editor consists of a set of commands which
enable the user to modify existing office data tables. The table editor
commands are entered by typing in commands using the keyboard of a
teleprinter or a VDU. The results of the commands are displayed on the
TPR or the VDU screen.
The table editor can work with the Command Interpreter (CI) process to
facilitate the modification of system data. Certain commands in the table
editor are designed specially for parameter substitution in table editor
“execs.”
The POF facility is an integral part of the table editor providing a facility for
storing (within the CPU memory) table editor commands as files. These
files are manually activated on an individual or collective basis. The
contents of any of these files may be queried, changed, or deleted byte
system file editor.

DMS-100 International Technical Specification BCS40i and up

7–100 Administration

An extension of the table editor is provided with DMS-100 systems (local)

only. The extension provides a set of capabilities for database changes
related to subscriber lines called service orders.
Table editor functions
The table editor commands allow the user to perform the following
functions:
• Add, delete or change tuples or fields within a table or subtable.
• List one or more tuples of a table or subtable.
• Move the cursor to display any tuple within a table or subtable.
• Display specified valid field values.
• Search for tuples containing specified field values.
• Verify table alterations before activating them.
• Modify subtables of the table being edited. Figure 7–11 shows the
relationship between the table and a typical subtable. The subtable is
accessed by addressing a field which contains a subtable pointer instead
of data.
• Ability to create pending files from within the table editor.
• Display the number of tuples used in a table.
• Ability to alter data when the CPUs are out of sync.

Data table structure

The data associated with the hardware and software subsystems of DMS-100
Family Switches are stored in tables. A table consists of rows (horizontal)
and columns (vertical). The rows are referred to as tuples and the columns
identify fields of tuples.
Figure 7–11 shows the structure of a typical table, containing 1 through N
tuples and 1 through N fields. The fields in a table (or subtable) have five
properties:
• Each field has a unique identifier called a field name or field number, by
which the field may be accessed.
• Each field name consists of a maximum eight-character string.
• Each field name has an associated field number. Field names are
numbered consecutively, beginning with 1 for as many field names as
there are in a tuple.
• The contents of a field may contain one or more elements of data.
• The contents of a field may contain data expressed in the form of
numerics or alpha-numeric strings. It may also contain pointers to
subtables.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–101

Figure 7–11
Structure of typical table and subtable

Note: Tuples are numbered 0 through N

Table name
Field Field Field Field Field
name name name name name
& no. & no. & no. & no. & no.
1 2 3 4 n
Tuples
* Top 1 Key Data Data Data

2 Key Data Data Data

Sub-
3 Key Data table Data
pointer

4 Key Data Data

Cursor

Subtable name

Field names and numbers

1 2 3 4 5 n
1 K1 D D D D D
2 K2 D D D D D
Bottom N Key Data Data
Tuples

3 K3 D D D D D
4 K4 D D
D
* The cursor is automaticaly positioned initially D
at the top of the table by the “Table” command. N KN D D D D D

The tuples in a table (or subtable) have three properties:

• Each tuple is identified by a KEY which is always the first field-name or
field-number 1.
• Each tuple is unique. Duplicated KEYS are not allowed.
• Tuples are referenced either by their KEY or by the table editor cursor.
The cursor is an internal pointer to a tuple of a table which is positioned
via commands. The tuple to which the cursor points at any given time is
called the current tuple.

DMS-100 International Technical Specification BCS40i and up

7–102 Administration

Input prompter
The prompter in table editor has two input modes: prompting and
non-prompting.
Prompting mode
• The name of the required field or parameter is displayed.
• The user must then input syntactically correct data for the field entirely
on the current line.
• If the input data was not correct, an error message is printed and the field
or parameter must be re-entered
• After two syntax errors on the same field, the valid syntax range is
displayed.
• While in the prompt mode, the user may enter “ABORT” which has the
effect of killing the command.
Non-prompting mode All commands are initially in the non-prompting
mode. The required parameters are presumed to be on the current line. The
system processes one parameter at a time until it either runs out of input or
encounters an input error. At that time, the system goes into the prompt
mode looking for the missing or invalid parameter. Any input line in either
mode can be continued to the next line by placing a “+” at the end of the
line.
Description of table editor commands
The table editor commands consist of two or more alphabetic characters
followed, in most cases, by parameters. When the table editor is ready to
accept a command, it displays the prompt character at the start of a new line
on the terminal.
There are three basic categories of commands in the table editor: primitive,
conditional, and compound. The commands covered in each category are
shown in table 7–3.
Primitive commands such as LIST, ADD, DELETE, TOP, and BOTTOM,
are the basic commands used to manipulate the tables.
Conditional commands are used as field value test and logical commands as
follows.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–103

Table 7–3
Table editor commands

Primitives ABORT ADD ASSIGN CHANGE

DELete DISPLAY EXTend FIRST
FORMAT HEADING HELP INFORM
LAST LOCate NEXT OVErride
PREV QUIT TABLE REPlace
RETurn SUBtable
VERIFY
Conditional AND EQ GE GT
LE LT NE OR
Compound BOTtom COUNT DOWn LIST
POSition RANge TOP UP
Pending ENDpof POF PUTpof
Subsystem

Commands for testing field values:

field_name condition field_value
or
field_number condition field_value
Commands of this form apply the specified condition to the field against the
field value and return a Boolean indicating the result of the comparison:
• EQ (equality) – all field types
• NE (not equal) – all field types
• GT (greater than) – numeric
• GE (greater or equal) – numeric
• LT (less than) – numeric
• LE (less than or equal) – numeric

Logical Commands:
Boolean_result logop Boolean_result
These commands apply the indicated logical operation (logop) to their left
and right parameters and return a Boolean indicating the logical result:
AND
OR
Compound commands are primitives which can optionally have a
conditional second part, such as, list all (FIELD 2 EQ “XXX”). For further
details see NTP 297-1001-310.

DMS-100 International Technical Specification BCS40i and up

7–104 Administration

Service orders (DMS-100 local only)

Service order activity is necessary whenever subscribers, service features,
and options are added or deleted. This section describes how the applicable
information is entered into the DMS-100 system. Further details are in
Service Order and Query System Reference Manual, 297-2101-310. MDC
customers can be allowed access to change data associated with lines in their
customer group.
The line data query system is used to determine the status, working or
unassigned, of directory numbers and line equipment numbers associated
with lines. This information can be used in the preparation of service orders.
Service order and query data consists of numerical data and mnemonics
based on English-language telephony terms. Failure to pass internal validity
checks results in the output of concise English-language error messages.
The service order and query subsystem comprises a set of executive DMO
routines designed to permit fast and accurate manipulation of customer data.
Knowledge of the DMS-100 data table structure and table editor commands
is not a prerequisite for user.
Service orders and query commands are entered into DMS-100 by typing in
mnemonics and numerical data using the keyboard of a teleprinter or visual
display unit which may be part of a designated MAP or a dedicated DMO
I/O terminal. The mnemonics used with service orders and query commands
are either standard English-language telephony terms or their derivations
and abbreviations.
Full validity checks are performed by the DMS-100 for service order data
entered. Failure to pass these checks results in rejection of the data and the
output of concise English-language error messages designed to clearly
identify the cause(s) for rejection.
An error made while typing in data may be corrected by backspacing to the
point where the error was made, using the delete or rub-out key, and entering
the correct data. Following completion of a service order input, a display of
the entire service order as entered permits human verification of data
accuracy and completeness before final activation.
Service order input commands The type of service order or query is
identified to DMS-100, by the first input command. The remainder of the
service order data may be entered together with the input command as a
string of data (no-prompt mode). Some of the service order input commands
are summarized in table 7–4.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–105

Table 7–4
Service order commands
Command Usage Applicable to

NEW Establish service Individual (non-hunt) line and

establishes services for party
lines P-Phone & Data Unit
OUT Remove service Individual line pilot of hunt
group P-Phone & Data Unit
ADO Add options to lines or add Individual line DNH group
existing lines to a DNH group. member Pilot of hunt group
Add features to P-Phone keys P-Phones
DEO Delete options from lines. Individual line DNH group
member Pilot of hunt group
Delete features from P-Phone P-Phones
keys
EST Establish a hunt group Hunt group with members
having common options
ADD Add lines(s) to a hunt group Hunt group members
DEL Delete line(s) from a hunt Hunt group members except
group pilot
ABNN Add bridged night number(s) Hunt group members
DBNN Delete bridged night Hunt group members
number(s)
BULK Verify or update (execute) All service order types
from a batch of service orders
in bulk
DEOH Delete options MLH/DLH group members
SUS Suspend service Individual line Pilot (to
suspend hunt group)
RES Restore service (from Individual line Pilot (to restore
suspension or plug-up) hunt group)
PLP Plug-up (place on trouble Individual line Pilot of hunt
intercept) group DNH group member
CDN Change directory number All DNs of a hunt group
except the pilot DNs
CLN Change line equipment All lines except party lines
number
CICP Change intercept type All unassigned DNs
—continued—

DMS-100 International Technical Specification BCS40i and up

7–106 Administration

Table 7–4
Service order commands (continued)
Command Usage Applicable to

QDN Query Directory Number Queries all information about

hardware and software
associated with a directory
number
QLEN Query Line Equipment Obtains a printout of line data
Number related to a specific line
equipment number (LEN)
End

Service order format Service order commands have a basic format:

• A Command Identifier: A service order command name.
• A Service Order Number: A unique identifier for the service order to
be entered. This is used for pending orders. The default value with no
time stamp causes immediate activation.
• A Set of Parameters: The parameters required depend on the initial
service order command and, for a given parameter, the response given to
the immediately preceding parameter.
• An Order Terminator: Usually a Carriage Return (CR) is required to
indicate the service order is complete after all required parameters have
been entered.
• Statement of the Order Entered: The system prints out a statement of
the order it has received and requests confirmation that the entry is to be
made, rejected, or edited.
• Confirmation of Order: A “Y” is entered to indicate to the system that
the service order as entered is to be processed.
• Error Statement: If the system detects errors in the commands entered,
such as incompatibility between parameters, the order is rejected and the
reason for rejection is printed out. The user can edit or reject the entry.
General rules for service orders
• Identification and Mode of Entry: The type of service order or query
is identified to the system by the command identifier. From this point,
the remainder of the order can be entered in either the prompt mode or
the no-prompt mode.
• Prompt Mode: In the prompt mode, the service order or query is
entered item by item, following requests by the system.
• No-Prompt Mode: In the no-prompt mode, the service order or query is
entered as a string of data immediately following the service order input
command, each item separated by spaces.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–107

• Correction of Errors: An error made while entering data can be

corrected by backspacing to the point where the error was made, or using
the delete or rub-out key and entering the correct data.
• Dummy Character: The $ character is used to indicate the end of a list
at any point in a service order entry, or when no entry is applicable. In
the no-prompt mode, the $ character is used to request the system to use
a default value for a command parameter.
• Continuation Character: In the no-prompt mode, if there is
insufficient space to complete an order in one line, a + character
preceded by a space and followed by a carriage return is used to close off
the line and the remaining data is entered on the next line.
• Maximum Number of Characters: In the no-prompt mode, the
maximum input is 500 characters including spaces. If the 500-character
limit is reached before a service order is completely entered, the system
reverts to the prompt mode for entry of the remaining data.
• Error in No-prompt Entry: In the no-prompt mode, if a required entry
is omitted or not entered in the proper order, or erroneous data is entered,
the system reverts to the prompt mode, starting from the last correct
entry.
• Emergency Entry of Orders: Service orders are normally entered
when the two CPUs are operating in a synchronous mode. If the system
is operating without the two CPUs in synchronism, the user is advised by
a printout before the system accepts the order. In this case the user has
the choice to abandon (enter character N) or proceed (enter character Y).
Entering service orders In order to enter the service order environment,
the user must enter the SERVORD command. The SERVORD command
may be input from any level (CI, table editor, or MAP).
To determine the parameters required for a service order command, a user
can enter a Q character followed by a space, followed by the command
concerned. The system prints out the parameters required.
All parameters are printed out as prompts when SO are entered in the
prompt mode. If the range of entries for a specific prompt is not known, the
entering an erroneous value twice will cause the correct range of values for
that parameter to be displayed. The user can then select one of the correct
values, enter it and then carry on to the next parameter.
If a service order is entered without a SONUMBER, that is, the internal
default value is used, it can be accepted by the system for immediate
activation. If the due date portion of the SONUMBER is later than the
current system clock date, the service order is entered into the pending order
file for activation at a later date.

DMS-100 International Technical Specification BCS40i and up

7–108 Administration

No-prompt mode service order If all parameters and their entry

sequence for a service order are known, a user simply logs on at a valid
service order input device, enters the applicable service order command, a
space, a $ character or a SO number and due date, a space, all parameters in
sequence and separated by spaces, and closes the entry with a CR. The $
character must be used to indicate the ends of lists within an order, for
example, to indicate all options have been entered.
When the carriage return is entered to indicate the completion of the order,
the system prints out the order as entered and requests confirmation,
rejection, or edit. If a Y is entered to indicate confirmation, the system
either processes the order or rejects it and prints out the reason(s) for
rejection, for example, incompatibility between options entered.
Prompt mode service order To enter a service order in the prompt
mode, a user needs to know only the values of all parameters. The
procedure then is to log on at a valid input device and enter a valid service
order command followed by a carriage return; the system then prompts for
the next input. If errors are made by entering invalid parameters, the system
prompts for the correct information. The entry is terminated with a CR.
If a carriage return is entered in response to the SONUMBER prompt, the
system uses a default value for SONUMBER which includes the current
date as due date.
Emergency activation Service orders are normally entered when the two
central processing units are running in a synchronous mode. If it becomes
absolutely necessary to enter a service order when the central control is
operating with a single CPU, operating company personnel can override the
system restriction and emergency-activate the service order. Customer data
entered during CPU transitions should be verified by query commands when
synchronous operation has been re-established.
Pending order file (POF) If the due date entered as part of the
SONUMBER is a future date, the service order is automatically entered into
a POF.
Journal file (JF) When the (optional) DMS-100 Family JF is provided, a
copy of each service order or DMO can be stored in the JF (on disk or tape)
whenever the service order or DMO is successfully activated.
Service order example New 1FR Service with options establish
individual line, flat rate service with DIGITONE dialing. The line is part of
line treatment group one. The directory number is 362–1495 and the line
equipment number is 0000231. The office has no service order echoing
facilities at the MDF.
• Input in prompt mode

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–109

NEW
SONUMBER: NOW 85 8 7 AM
DN:
3621495
LCC:
1FR
LATANAME:
NILLATA
LTG:
1
LEN:
HOST 00 0 02 31
OPTION:
DGT
OPTION:
$
COMMAND AS ENTERED
NEW NOW 85 8 7 AM 3621495 1FR NILLATA 1 HOST 00 0 02 31 ( DGT ) $

• Input in no-prompt mode

NEW $ 3621495 1FR NILLATA 1 00 0 02 31 DGT $
COMMAND AS ENTERED:
NEW NOW 85 8 7 AM 3621495 1FR NILLATA 1 HOST 00 0 02 31 ( DGT ) $

Customer data change (CDC) The CDC feature permits DMS-100

business services customers to access and modify their own office data from
Northern Telecom approved ASCII terminals on a dial-up basis. Full
DMS-100 Maintenance and Administration Positions (MAPs) are not
provided to end users. Security in the DMS for these end user accesses can
be provided through the Enhanced Security Package I feature set. These
virtual PBX feature packages partition subscriber and office data in the DMS
for multiple end customers.
To implement the Customer Data Change features, the telephone operating
company defines, through a number of new data tables, the specific
subscriber and/or office data that each end customer is allowed to view
and/or modify, as well as the method by which they are permitted to access
their data.
The CDC software includes Customer Service Change via SERVORD,
Customer Network Data Changes, and Customer Network Manipulation.
Customer service change via SERVORD This feature permits
specified users in an MDC customer group to access the DMS-100 Service
Order (SERVORD) system in order to modify some line-related data. This
feature also allows a customer to reserve line equipment numbers (LENs)
for later use.

DMS-100 International Technical Specification BCS40i and up

7–110 Administration

Customer network data changes This feature expands the SERVORD

capabilities, enabling users in a customer group to view and modify certain
translation and routing parameters.
Customer network manipulation (CNM) This feature further extends
the end user’s capabilities by providing access to the Table Editor level of
the DMS-100 data modification system.
The primary purpose of this feature is to allow the telephone operating
company to provide a large customer with the means to control Alternate
Route Selection (ARS) patterns for their customer groups, and to control
other network characteristics by doing their own datafill.
The telephone operating company is able to provide end user access to the
Table Editor level of the DMS-100 data modification system through this
feature. It also provides a new Table Editor, the Partitioned Table Editor
(PTE), specifically designed for end user manipulation of data tables.
Like the Table Editor, the PTE consists of a set of commands that enable the
user to create or modify office data tables. The PTE commands allow the
user to display, add, delete, or change tuples or fields within a table or
subtable. In addition, the PTE provides security of data by preventing a user
from viewing or modifying another user’s data.
CNM provides three functions to the telephone operating company:
• define access rights to various tables and subtables for end users,
• define access rights to various PTE functions for end users, and
• maintain log reports of commands used in the PTE.

Administration for subscriber module SLC-96 (SMS)

SMS provides integrated administration and supports a majority of the
features currently available with the SLC-96 remote terminal and DMS-100
switch. Service order changes and line data inputs are made at the
Maintenance and Administration Position (MAP).
Line class codes and line options assignable to POTS DMS-100 lines are
assignable to SMS/ SLC-96 lines.
The capability to trace calls is expanded to include calls originating from
and terminating to SCM-100S/SLC-96 lines. Data printed out for the calling
line include the location code of the SLC-96, identifying the calling line.
Line Load Control (LLC) is assigned to SMS/SLC-96 lines for essential
subscribers, such as fire departments and police stations. Operator
verification of SMS/SLC-96 lines is supported. A switch operator can
monitor lines or converse on lines from the Traffic Operator Position System
(TOPS) or equivalent position.

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–111

Operational Measurements (OMs) and traffic data are provided for the SMS
and SLC-96. Call originations from and termination to SMS/SLC-96 lines
are included in the Traffic Separations Measurement System (TSMS).
Registers for Subscriber Line Usage (SLU) and message rate are assignable
to SMS/SLC-96 lines. The MAP provides the capability to query and
display the switch status data of special service circuits, such as complete
cross-connect information and the assigned circuit paths.
Dump/restore
This is a process carried out by Northern Telecom when an office is to
receive a software upgrade, a Batch Change Supplement (BCS). The
process consists of five sequential steps.
1 With the two CPUs in sync, a copy of the data in the tables is dumped to
tape.
2 The CPUs are split, sync is dropped and the inactive side is loaded with
the new software. This is a no-data image.
3 Using a facility called MATE10, communication is established with the
inactive CPU.
4 The data files on the tape are transmitted to the inactive CPU and the
data tables are restored using batch DMO procedures.
5 Activity is then switched and the office is running on the new software.
Pending order file (POF)
The POF is a collection of service orders and DMOs which are not due on
the day they are collated. The POF facility provides a method of verifying
and executing the POF data files. A prompt facility can send a reminder
message to the log device indicating that a particular file of pending orders
is now due (see Pending Order Subsystem Reference Manual,
297-1001-126.)
There are two methods of creating and starting POFs. One is for the service
order system, the other is used through the table editor.
POF – service order system created To create a POF via the service
order system the service order clerk enters a service order number and the
date of activation. The DMOs generated by the service order are stored in a
special table called DMOTAB. The prompt message information is stored in
another table called NPENDING. Both of these tables are accessible via the
table editor and are stored in the DMS memory. Editing of a POF created
via the service order system requires deletion of the tuples in DMUTAB and
NPENDING that have the service order number as a key, and re-adding the
POF via the service order system.

DMS-100 International Technical Specification BCS40i and up

7–112 Administration

POF – table editor created Creation of a POF via the table editor allows
the user more flexibility. The user enters the “POF” mode after entering the
table for which he wants to create the DMOs . DMOs in “POF” mode are
not entered directly in the table but rather sent to a user-specified file on a
user-specified device. Error checking is performed on the DMOs before
they are added to the file. When the user has finished entering DMOs, he
leaves “POF” mode or quits the table. Both actions will close the file just
created. Editing of DMO files is accomplished by use of the system file
editor.
A prompt message is not automatically created for DMO files as it is for
service order POFs. The prompt can be manually created for DMO files via
the “CREATE” command in the PENDING subsystem. “CREATE” places
an entry in table NPENDING, and a log message is output at the requested
time.
DMO files can also be created via the file editor, or they could be created
off-line to the DMS-100 and then loaded into the DMS-100 (as a DMS-type
file) via tape, data link, etc. This last is the recommended method of
applying batch data changes to the DMS. Two resident modules are
provided to use with DMO files: DMOVER which verifies the validity of
data files (especially useful for files created off-line), and DMOPRO which
verifies and processes the data files (actually inputs the data).
Pending subsystem This is accessed from the CI by entering the
command “PENDING.” The prompt string will change to “POF” until the
“LEAVE” command is input.
While in the PENDING mode the user can “ACTIVATE” or “DISPLAY”
one, all, or a group (specified by date and time) of POFs. To examine a POF
the user looks at table “DMOTAB” for service order POFs, or prints or edits
the user defined file if the POF is in the DMO format.
Journal file (JF)
Only those DMOs that have been activated and deemed valid are entered
into the journal file and these are identified by means of a unique JF
identification (ID) number which is assigned automatically by the journal
file system. These ID numbers are only resident on the journal file but are
output to the user in the form of a confirmation message when the associated
DMO or service order is activated and stored on the JF. (The message is
output to the device from which the database change is initiated.) (see
Journal File Description, 297-1001-127.)
JF intermediate storage mechanism
Once valid service orders and DMOs are activated they are stored in a buffer
area in the DMS-100 family core memory that is provided for those journal
file records that are to be recorded on tape. When full, the buffers are

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–113

transferred to the journal file. These buffers reside in protected store and
thus survive restarts (or cold starts).
JF tape service order/DMO organization
The ID numbers (and their associated data updates) residing on the JF file
are not necessarily in any sequential order since several users can be
activating different data table changes concurrently. When DMO are
performed, only one JF record ID number is output for the entire service
order even though several data tables can be updated. This is due to the fact
that service orders are executive routine driven (to update numerous tables
simultaneously). Internally on the JF tape, however, the individual data
table changes (the number of changes being dependant on the service order
executive routine) are recorded as individual entities, each of which retain
the identical JF record ID number. When DMOs are effected, one record ID
number is output for every data table (tuple) change initiated.
Starting and maintaining a JF
If a JF can be kept on tape or disk, the access is through the DIRP
subsystem. If the office does not have disk, then the usual place for the JF is
at the end of the backup image tape. As both the backup image and the JF
must be mounted at the same time this not only saves a tape drive, it also
positions the tape at the JF after the system has reloaded. The allows
immediate application of the JF. If the CPUs are not in sync, then JF
updates are inhibited from the table editor and from service orders. There is
an override capability.
The JF is stopped, (and DMOs as well), before a new backup image of the
system is to taken. Once the new image of the system is to be taken and is
in position on the reserved tape drive then a new JF is started at the end of
the new image tape. If the office has disk, then both the image and the JF
are on disk so the position does not matter. The old JF must be transferred
to an archive tape or disk which will contain all old JFs cataloged by JF
name which contains the creation date.
The user manipulates the JF with five commands:
• START – starts a new JF
• STOP – stops a JF
• RESTART – reopen and continue a JF
• STATUS – reports state of JF
• APPLY – execute the DMOs in the JF
Note: APPLY can be used only after a system reload and before a new
JF START is done.

DMS-100 International Technical Specification BCS40i and up

7–114 Administration

Remote memory administration system (RMAS)

The Remote Memory Administration System (RMAS) centralizes and
mechanizes the recent change and data modification routines for DMS users.
RMAS will serve as a direct interface to the service order system, over
dial-up or dedicated facilities, for lines only. RMAS will also be designed to
have database query capability.
RMAS uses an ASCII link that is asynchronous and full duplex. The baud
rate is user selectable at 110, 300, or 1200 baud. Parity is selectable as odd,
even or non. Access to DMS is achieved by way of one of its I/O ports.

Service analysis (SA) (observing)

Service Analysis (SA), available on the Maintenance and Administration
Position (MAP) associated with the DMS-100 Family, is described in
Service Analysis, 297-1001-471. Service Analysis is an observation system
that is used to appraise the quality of service provided by the telephone
company. Service to be measured is based on call classifications such as
Direct Distance Dialing (DDD) outgoing and Direct Dial Overseas. Calls
are selected on a random basis to obtain the data for evaluation.
DMS-100 and DMS-200 service analysis
In the DMS-100 and DMS-200 switches, the service analysis function is
carried out at the SA position. The SA position provides the system analyst
with a voice and data link to the system. The system analyst listens to the
calls and notes events as they occur. The analyst uses two sources of
information, analyst detected events and machine detected events, to
determine whether the customer is receiving good service from the
equipment and/or the personnel involved in the call.
Call progress data – automatically detected
Following seizure, call progress events detected by the processor are
automatically displayed in coded format on the VDU, along with the time of
occurrence of each event in elapsed seconds following seizure. This call
data will include: (Note: The analyst may, at any time, obtain a display of
the elapsed time into the call.)
• Digits of the called number
• Seizure of an outgoing trunk
• Identification of type of special trunk seized
• Forward supervision from the called end
• Disconnect of the incoming trunk
• Disconnect of the outgoing trunk
• Call type routed to announcement
• Called party answer
• Call connected through the switch

PLN-5001-001i Standard 02.02 April 1997

 Administration 7–115

• Called digits received

• Called number information
• Called party disconnect
• Calling number information
• Calling party disconnect
• Flash for special feature
• Service analysis is unable to follow the call
• The originator has gone to lockout and the analysis is stopped
• The origination of a subsequent attempt during local dial analysis
• Receiver attached for MF trunk
• Tone applied to the originator
Call progress data – analyst detected
Call progress events which are identifiable only as audible signals on the
voice channel will be detected aurally by the analyst. Upon detecting each
such event, the analyst will depress a key as indicated in the menu, thereby
signaling to the DMS-100 Family system processor the specific event which
occurred at that time. The processor then responds to this signal by
displaying the event and its elapsed time on the VDU in coded format. This
call data has six components:
• No Circuit Signal
• Reorder Signal
• No-Such-Number Signal
• Recorded Announcement
• Called Station Verbal Answer
• Other Operator Answer

Service analysis increased sample rate

This feature enhances service analysis by allowing the system to sample a
maximum of nine calls simultaneously. This increases the screening process
and reduces the delays caused by searching for appropriate calls to monitor.
DMS-300 service analysis
Service analysis on the DMS-300 machine is carried out at the MAP, from
the common base service analysis SAselect level, and has a separate set of
commands and capabilities. Call selection is hardware oriented, with
selection criteria being trunk type, trunk group, or individual circuit. The
GWsel level and Quota level of the MAP provide a number of service
analysis commands. For further information please refer to the design
documentation for feature BC0833. This feature is contained in feature
package NTX065.

DMS-100 International Technical Specification BCS40i and up

7–116 Administration

Multi-unit message rate services (MUMR)

This feature enables the operating company to charge calls on a basis of
service provided. The rate for each Multiunit Message Rate (MUMR) call is
based on a Message Billing Index (MBI), which can be included in the
AMA record to simplify downstream processing. Screening tables are used
to associate NPA and office codes with MBIs, and the operating company
can assign MBIs to corresponding rate bands in its tariffs. The MBIs
provide all destination related information required to bill the call. The
billing information is collected by the LAMA system in the Bellcore AMA
format. The called number can be omitted from the LAMA record.
Omitting the called number from billing data is referred to as batch billing.
An option enables the operating company to forward charge pulses to
hotel/motel PBXs on a per-office basis. The charge pulses are used for guest
billing of non-toll calls. The number of pulses sent during a call varies with
call duration, tariff, and surcharge. Charge pulses can also be designated for
initial and overtime periods.

Fraud prevention feature

Malicious call trace (MCT)
The malicious call trace feature allows a telephone administration to identify
the originating line in the case of a malicious or fraudulent call. On
identifying an incoming call as a malicious call, the called party flashes the
switch hook. The switch hook flash signals the DMS-100 office to lock up
the calling line and to generate a log report and an alarm. The calling line is
held until manually released by telephone administration personnel. The
called line is free to originate or receive new calls.
If the call arrives on an incoming trunk and terminates within the DMS-100
office, the connection is held back to the incoming trunk.
For details of MCT operation please refer to the appropriate market-specific
technical specification.

PLN-5001-001i Standard 02.02 April 1997

 8–1

Billing
DMS switch billing features
The DMS international switch supports the following billing features:
• ITOPS billing
• International Call Recording
• Inter Administration Accounting
• ICAMA
• DMS-100 metering

ITOPS billing
ITOPS billing uses ICAMA to bill calls that are handled by an ITOPS
operator. For a complete description of ITOPS billing, refer to “ITOPS
billing feature” in this document.
International Call Recording
The International Call Recording (ICR) feature allows recording of all calls
or only selected calls in a DMS switch. For a complete description of ICR
billing, refer to “ICR feature description” feature” in this document.
Inter Administration Accounting
The Inter Administration Accounting (IAA) feature records details of all
transit calls which can then be used by operating companies for division of
revenue purposes. For a complete description of IAA billing, refer to “IAA
billing feature” in this document.
International Centralized Automatic Message Accounting
The International Centralized Automatic Message Accounting (ICAMA)
feature is used in DMS toll offices to record call details. For a complete
description of ICAMA billing, refer to “ICAMA billing feature” in this
document.
DMS-100 meter billing
Meters are data store registers that are incremented as required for each call.
At required times, the data store registers are transferred to tape, disk,
back-up file or out-of-service file. A complete description of the DMS-100
software meter billing feature is contained in this chapter.

DMS-100 International Technical Specification BCS40i and up

8–2 Billing

Meter billing system description

Call metering is a method of determining the charge for the elapsed time of a
call by periodically adding “charging units” to a subscriber software meter.
A line subscriber may have up to four different software meters on which to
incur charges: three call processing meters, and one feature meter. A trunk
subscriber may have up to four software call processing meters.
In order to bill the subscriber for charges accumulated, a mechanism is
provided to transfer the software meter data to a nine-track magnetic tape or
a disk. This information can then be used by a downstream processor to
generate customer bills.
The DMS-100 switch can also send 12 kHZ or 16 kHZ pulses along the
subscriber loop to support subscriber premise meters (SPM) and metered
coin boxes, and the sending of a battery reversal for non-metered (local)
coin lines. SPMs are a mechanism for the subscriber to monitor the charge
units generated against their calls. Metered coin boxes collect coins on
receipt of a pulse. Non-metered collect coins on receipt of a single battery
reversal.
In addition to call metering, the DMS–100 switch provides a utility to record
information for each call to disk or tape for call monitoring.
Software meters
The DMS-100 switch can support up to 65 534 lines or 2048 trunk groups
with software meters. The number of lines and trunk groups on a switch are
datafilled by the operating company up to these maximum values.
Each datafilled line or trunk on a switch is allocated a meter block, which
contains four software meters. Depending on the line or trunk attributes, all,
some, or none of the four meters may be required. All meters that are not
required, are transparent to the subscriber and the billing process. Changing
the line or trunk attributes may change the number of meters visible to the
subscriber.
Of the four line software meters, three contain call processing charges, and
the fourth contains feature charging. The four software meters associated
with trunk groups are used for call processing only.
Each line software meter is initially set to zero, and can store a count of up
to 7 nines (9 999 999). Each trunk software meter can store a maximum
value of 9 nines (999 999 999). A software meter wraps to zero when the
maximum number of charge units has been reached. The WRAP bit for the
meter is also set. If a meter wraps for the second time in the same billing
period, an MTR100 log report is generated.

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–3

Metering for hunt groups is handled as follows:

• Members of multiline hunt (MLH) and distributed line hunt (DLH)
groups are assigned meters based on the datafill of the pilot directory
number (DN). When the datafill for a LEN is changed, the set of meters
assigned to the hunt group members is also changed.
• Members of directory number hunt (DNH) hunt groups are assigned
meters based on the DN datafill.
Meter blocks are allocated to all lines in table LENLINES. Meter blocks are
allocated to trunk groups that have the METERIC field set to Y in table
TRKGRP. Meter blocks are only deallocated when the line or trunk is
deleted from table LENLINES or TRKGRP.
Note: Meter blocks are allocated to lines or trunk groups, but individual
meters are assigned.

Determining call charges

Call charges are expressed in terms of the number of “charge units”
accumulated during a call. The rate at which “charge units” are added to the
meter is based on the call tariff. Call tariffs are determined from the source
and destination of the call, the network through which the call is placed, the
time, and the type of day.
Data associated with the originating line or trunk group is used to determine
the type of metering to be provided: hardware, software, or both. Hardware
metering refers to the outpulsing of electrical pulses on the subscriber’s line
or incoming trunk while the call is in progress. Software metering refers to
the accumulation of charges stored internally in a line’s software meter.
Software meters are normally updated at call termination. Software meters
associated with long duration calls have interim updates.
Charge calculation
There are two methods of calculating the number of pulses associated with a
call: XMS-based peripheral module (XPM) metering and common control
(CC) metering. XPM metering determines how much call time is associated
with a single pulse. At the start of a call, a counter is incremented, and, if
required, an electrical pulse is generated. When the call duration time for
that pulse is reached, the counter is incremented again. This process
continues until the call terminates, at which time the total number of pulses
accumulated is sent to the CC to update the subscriber’s software meter.
Under certain circumstances, such as invoking an enquiry call or having a
call fail, the CC calculates the correct charge at the end of the call. The rate
at which the call is charged is based on the same datafill used by the XPM to
determine the charge. As a result, both methods result in the same number
of charge units. Since CC metering applies only to software metering, any
feature that forces CC metering is not compatible with hardware metering.

DMS-100 International Technical Specification BCS40i and up

8–4 Billing

CC metering data resources

CC metering requires data resources to save tariff information changes
resulting from time-of-day changeovers or system time changes, and to save
the charge attributes for each call. The storage structure for the tariff
information is the tariff history queue (THQ). Information about each tariff
rate for a particular time and type of day is stored in one queue element.
These resources remain accessible until all calls that reference them are
processed, and their meters updated. The updating of long duration calls
once a day frees these resources automatically. THQ blocks are monitored
and an alarm is generated when less than 10% of the blocks are available.
The storage structure for CC metering on individual calls is the CC metering
extension block. The resources for this are controlled by the office
parameter NUM_CCMTR_EXT_BLOCKS in table OFCENG. Additional
flexibility is provided by the office parameter
CCMTR_FAILURE_FREE_CALL in table OFCENG which allows calls to
continue free of charge if insufficient blocks are available to meter the call.
To eliminate alarms and logs when datafilling the metering tables, table
INTCCMTR is used to initially turn off CC metering. Table INTCCMTR
must have the value CCMTRON entered in field CCMTRKEY once the
datafill is complete. Once this value is entered, it cannot be changed.
Long duration calls
For long duration calls, the DMS-100 metering system provides an interim
mechanism for updating the software meter of a line or trunk group. This
mechanism is the charge update process (CUP) that is invoked at 03:15
daily. The CUP scans for all active calls that exceed two hours. The current
charge accumulated for each call is calculated and entered in the appropriate
software meter. The CUP can also be invoked manually using the command
THQCLEAN at the MTRSYS MAP level.
Once a call has had an interim update applied, CC metering is used to
calculate any further metering charges.
Tariffs
The charge rate applied to each call is determined by a tariff. The tariff to be
applied is based on the originator of the call, the network used for routing,
the time of day, and the type of day. This information is contained in tables
TKMTRNAM, LNMTRNAM, LNETWORK, MSRCDATA, MDESTIDX,
MTARFIDX, TIMEODAY, MTARFNUM and MTARIFF.
Tariff rates can be datafilled to use either periodic pulse metering or
aperiodic pulse metering. Periodic pulse metering (PPM) is the process in
which pulses are distributed evenly throughout the duration of a call.
Aperiodic metering, on the other hand, is the process in which pulses are
applied at the beginning of the interval for the whole interval. The method

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–5

of pulsing is defined for each metering network in table MNETATTR.

When hardware metering is required for an aperiodic metering network, the
software counter is incremented to correspond to the real time delay required
to send each individual pulse. Figure 8–1 illustrates these two methods
graphically.
Figure 8–1xxx
Meter pulsing options
FW-31058

PPM pulsing

Time (s) 0 5 10 15 20 25

Pulse p p p p p p p p p p p

APM pulsing (software only)

Time (s) 0 5 10 15 20 25

Pulse p p p
p p p
p p p
p p p

APM pulsing (hardware and software)

Time (s) 0 5 10 15 20 25

Pulse pppp pppp pppp

Note: The pulse rate is 4 pulses in 10 s. The hardware pulsing

rate limit is 2 pulses per second.

Determining tariff rates

A tariff determines how many charge units are generated over time for a
call, and consists of a total of the following:
• the number of charge units generated on call answer
• the number of charge units generated after an initial period
• the number of charge units generated for each subsequent period until
call disconnect

DMS-100 International Technical Specification BCS40i and up

8–6 Billing

A tariff consists of three phases defined in table MTARIFF: an answer phase

(phase 1), initial period phase (phase 2), and an overtime phase (phase 3).
The format of a tariff can be expressed by the following equation:

Tariff = (Ν1Τ1) + (Ν2Τ2) + (Ν3Τ3)∗

where
N is the number of pulses in each phase
T is the duration of each phase (≤ 50 min)
* repeated until call disconnect
fffffffff
Note: Pulse-refresh is the period of time between pulses in a phase, and
is equal to TX/NX. A null phase occurs when N = 0 and T = 0. A free
phase occurs when N = 0 and T > 0.

Calculating periodic charges

The following conditions apply when a tariff is calculated with periodic
pulsing:
• The first 100 milliseconds of a call are free.
• Metering is prepaid.
• When a tariff change occurs during a metered call, the change is made in
the same phase or at the beginning of the next non-null phase.
• When a tariff change occurs before a phase has been completed, the new
tariff begins at the same point through the same phase, and is calculated
using the following process:
— The percentage of pulses that have been generated for the phase is
determined and the same percentage is used to determine how many
pulses for the new tariff are to be ignored.
— The percentage of time that has elapsed in the current inter-pulse
interval since the last pulse is determined and the same percentage is
used to determine the time elapsed in the new inter-pulse interval of
the new tariff.
• When the new tariff in a phase is null, the calculation of the new tariff
begins at the start of the next phase.
• The maximum supported pulse rate is two pulses per second.
• The minimum supported pulse rate is one pulse per 50 min.

Aperiodic charge calculation

The following conditions apply when a tariff is calculated with aperiodic
pulsing:
• The first 100 ms of a call are free.
• Metering is prepaid.

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–7

• When a tariff change occurs, the current phase completes before the new
tariff becomes effective.
• The maximum supported pulse rate is two pulses per second.
• The minimum supported pulse rate is one pulse per 50 min.
The time-of-day system
The metering system is an application which uses the time-of-day (TOD)
system. The TOD system uses the following tables to set up time of day
definitions:
• DAYTYPES
• TODHEAD
• DAYOWEEK
• DAYOYEAR
• TIMEODAY

Meter pulse tandeming

The meter pulse tandeming allows meter pulses to be transmitted to
switching offices that do not contain call tariffs for certain call routes.
Figure 8–2 shows an example of a DMS-100 office with a subscriber whose
software meter needs to be updated with the pulses associated with a toll
call, but the tariff rates are only available at the toll office. The call is routed
to the toll office over a trunk that is datafilled to receive meter pulses. The
toll office, after call answer, generates meter pulses back to the local office
according to the appropriate tariff rate. The local office monitors the pulses
being received on the outgoing trunk, and after call completion, updates the
appropriate subscriber software meter.
The meter pulse tandeming feature also provides the capability of tandeming
meter pulses from outgoing digital trunks to either incoming digital trunks or
to subscriber premise meters (SPM), as shown in figure 8–3. With this
arrangement, the international digital trunk controller (IDTC) associated
with the outgoing trunk, receives the meter pulses, and tandems them to
either the international line group controller (ILGC) associated with the
appropriate SPM, or the IDTC of the incoming trunk on which the meter
pulses are to be repeated. The CC meter for the trunk group or line is
updated at the same time.

DMS-100 International Technical Specification BCS40i and up

8–8 Billing

Figure 8–2xxx
Meter pulse application
FW-31061

meter
pulses

DMS-100
LOCAL TOLL
OFFICE O/G I/C OFFICE
TRK TRK
ORIGINATING
PARTY

Figure 8–3xxx
Tandeming of meter pulses to hardware meters and incoming trunks
FW-31061

DMS-100
CC

IDTC IDTC
TANDEM
PULSES OUTGOING
INCOMING TRUNK
TRUNK
ILGC

LCM

SPM

ORIGINATING
PARTY

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–9

Meter pulse tandeming is performed when the following conditions are met:
• When the field HWMETER of table MSRCDATA contains a value of
LNRCVMOJ or TKRCVMOJ for a specific metering data index (MDI)
and logical network name (LNETWORK),
• When the field FUNCTION of table MTSIGSYS contains a value of
RECEPTION for the trunk trunk group types OPR, MTR, or ITOPS in
table TRKGRP.
Meter pulse generation is performed under the following conditions:
• When the field HWMETER of table MSRCDATA contains a value of
TKPULSE for a specified MDI and LNETWORK.
• When the field FUNCTION of table MTSIGSYS contains a value of
GENERATION for trunk group types OPR, MTR, or ITOPS in table
TRKGRP, and MTOGSSI is specified for the trunk group in table
TRKSGRP,.
• When the entry in field CALLSET (ALLCALLS or DEMAND) of table
MTSIGSYS is matched
Line and trunk metering
The metering system provides software meters for the following:
• Standard or regular subscriber lines.
• Coin lines are lines that require the collection of a coin or coins in order
to originate a call, or to extend the duration of the call. Coin lines can
also be metered or non-metered. A non-metered coin line requires only
one coin to originate a call, and the call can continue indefinitely without
further charges. Metered coin lines collect a coin for a specified amount
of call time. When the prepaid time is reached, more coins are required
to extend the call time.
• Trunk groups

Metering for standard lines and coin lines is specified in table LINEATTR.
Metering options for standard lines include no metering, software metering
only, or both software and hardware metering. Metering options for coin
lines include hardware metering, or both software and hardware metering.
Metering for trunk groups is specified in table TRKGRP. No distinction is
made between subgroups or among members, however, only OPR, MTR,
and ITOPS trunks support metering. Metering options for trunk groups
include no metering or software metering.
Any line or trunk without software or hardware metering has all originating
calls processed without incurring charges.

DMS-100 International Technical Specification BCS40i and up

8–10 Billing

Software metering
Each line or trunk group with software metering has at least one software
meter assigned.
Hardware metering
The generation of pulses for a call originated by a line or trunk group that
requires hardware metering, begins on call answer. The pulses may be used
to either increment the counter on an SPM, or to collect a coin on a metered
coin line. Service order option SPM must be assigned to a line to allow
meter pulses sent to be transmitted. Pulses can be either 12 kHz or 16 kHz.
If the line is datafilled as a non-metered coin line, then a battery reversal is
sent at the point of call answer and continues for the duration of the call. No
other pulses are transmitted. The battery reversal collects a single coin.
Metering for subscriber features
Charging for subscriber features and feature administration is optional. The
metering system provides the capability of charging for the following items:
• assigning of a feature to a subscriber
• administration activating of a feature
• subscriber activation of a feature
• administration programming of a feature
• subscriber programming of a feature
• feature use by a subscriber
• subscriber interrogation of a feature

Note: There is no charge for deactivating a feature.

Charge specifications for features are datafilled in table FEATCHG.

Chargeable actions for each feature are datafilled at their own rate. All
chargeable feature actions must be datafilled to prevent the generation of
logs.
A dedicated feature meter is assigned to each subscriber line to record
charges generated by actions related to subscriber features. The feature
meter is assigned when the first chargeable feature action is performed. The
feature meter is deassigned when all chargeable features are deleted from
the subscriber’s line, or the line is deleted.
Each time a chargeable feature or option is added to a line, the metering
system automatically charges for feature assignment. If data changes are
required without charges, the parameter FEATURE_ADMIN_CHARGE in
table OFCENG is used to specify if charges for feature assignment are
required. This parameter only applies to administrative charges. All
subscriber invoked feature actions are still billable.

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–11

Meter billing files

A meter billing file for the DMS-100 switch is generated from the charges
accumulated on every subscriber’s software meters. This billing file may
then be processed by a downstream processor to create subscribers’ bills.
A billing file is created at the end of a billing period. The duration of the
billing period is arbitrary; however, operating companies should ensure that
the billing period duration is short enough so that a software meter is not
allowed to wrap to zero twice in one billing period. For example, an
uninterrupted call, pulsing at the rate of two pulses per second, would
require a billing period of less than 57 days.
During a billing period a subscriber software meter may be deassigned as a
result of a manual data change, such as a change of directory number, a
service termination, or a feature change. To preserve the data stored in the
subscriber meters, an out-of-service (OOS) file of billing records is
maintained by the billing system. The OOS file is processed as part of the
regular billing process. These OOS files are not maintained, however, for
trunk meters.
A billing file contains only one record for each subscriber meter. A record
in the OOS file has the same format as a billing record, but may have
multiple records for the same subscriber meter. Multiple records occur if
several changes are made to line data associated with the subscriber meter.
DIRP interface
The DMS-100 switch can record data on either nine-track magnetic tape or
Winchester type disk drives. Management of data transfer to and from the
hardware devices is performed by a software system called the Device
Independent Recording Package (DIRP). The metering system uses the
DIRP software system to maintain the OOS file and to create the billing file.
Each DMS-100 switch is configured for automatic data recording using the
following tables:
• table DIRPSSYS provides a list of recognized systems which record data
to tape or disk files
• table DIRPPOOL defines the groups of recording devices, the types of
devices, and the recording volume identification
• table DIRPHOLD maintains a list of all files yet to be processed

The DIRP OOS subsystem sets up a recording volume to receive all OOS
billing records, and the DIRP BIL subsystem sets up a recording volume to
create a billing file.

DMS-100 International Technical Specification BCS40i and up

8–12 Billing

OOS records for a billing period can be incorporated into the billing file in
either of the following ways:
• the active OOS file is rotated to standby at the end of the billing period
• the active OOS file can be closed before the billing file is created

If OOS records for a billing period are not to be added to the billing file, the
OOS file may be left in an active and open state, and the files will not be
processed.
DIRP commands are used to create, mount, demount, rotate, and close the
OOS and billing files. For additional information on the DIRP system, refer
to Device Independent Recording Package Product Guide, 297-1001-013,
Device Independent Recording Package Administration Guide,
297-1001-345, and Device Independent Recording Package Translation
Guide, 297-1001-356.
Billing file content
Billing file data consists of out-of-service and in-service data.
Out-of-service data are all billing records recorded in the billing OOS file.
In-service data consists of billing records for each software meter assigned
to a subscriber. Multiple records are created for subscribers that are
assigned more than one software meter, as one record is generated for each
meter. Billing records for members of multiline hunt (MLH) and distributed
line hunt (DLH) groups are generated with the pilot number of the group.
The OOS billing records and in-service billing records are identical in
format. A billing end-of-OOS record is generated after the last OOS record
is written to distinguish them from in-service billing records.
Data is written to billing files in blocks consisting of 56 line billing records
or 40 trunk billing records. To ensure fixed size blocks, the last block of
billing records is padded with blank billing records.
Billing records
There are two different billing records for lines and trunks.
Line record format
Each line record in the billing file contains the following data:
Directory number A ten-digit number identifying the owner of the meter.
Date A six digit number specifying the date the billing record was created,
in the form YYMMDD.

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–13

Meter name A 1- to 16- alphanumeric character name from table

LNMTRNAM. Do not use FEATURE which is used for feature billing,
NIL_METER_NAME which is used to indicate blank records, or
END_OF_OOS which is used to indicate the end of out-of-service records.
Count The number stored in the meter at the time of billing. A meter count
is not reset after a billing file is created, but is an accumulated value.
Wrap bit The wrap bit indicates if the meter has wrapped to zero since the
last billing file was created.
Figure 8–4 illustrates the format of line billing record formats, including a
standard record, a feature record, an OOS record, and a blank record.
Figure 8–4xxx
Example of line billing record formats

DN Date Meter name Count Wrap

22240502 931021 FEATURE 000023 NO

22240503 931021 LOCALMET 000221 NO
9999999999 999999 *** END OF OOS *** 999999 NO
120001 931021 LOCALMET 000332 YES
0000000000 000000 NIL METER NAME 000000 NO

Trunk record format

Each trunk record in the billing file contains the following data:
CLLI A 1- to 16- character common language name that identifies the trunk
group associated with the meter.
ID A four-digit number associated with the trunk group that is used in the
TRUNK_ID field of ICR and ICAMA records.
Adnum A four-digit administration number as datafilled in table CLLI.
Date A six digit number specifying the date the billing record was created,
in the form YYMMDD.
Name A 1- to 16-alphanumeric character name from table TKMTRNAM.
Do not use NIL_METER_NAME which is used to indicate blank records.
Count The number stored in the meter at the time of billing. A meter count
is not reset after a billing file is created, but is an accumulated value.
Wrap bit The wrap bit indicates if the meter has wrapped to zero since the
last billing file was created.

DMS-100 International Technical Specification BCS40i and up

8–14 Billing

Figure 8–5 illustrates the format of trunk billing record formats, including a
standard record, and a blank filler record.
Figure 8–5xxx
Trunk billing records

CLLI ID Adnum Date Name Count Wrap

ICDELDIALBA 0077 0397 931027 TRKLOCALCALLS 000000000014 N

ICDELDIALBA 0077 0397 931027 TRKNATLCALLS 000000492307 N
ICDELDIALBA 0077 0397 931027 TRKINATLCALLS 000000000097 N
ICDELDIALCB 0079 0381 931027 TRKLOCALCALLS 000000000231 N
ICDELDIALCB 0079 0381 931027 TRKNATLCALLS 000000000008 Y
ICDELDIALCB 0079 0381 931027 TRKINATLCALLS 000000073814 N
FILLER RECORD 0000 0000 000000 NIL METER NAME 000000000000 N

Viewing the billing file

The contents of the billing file for lines and trunks can be viewed using the
commands MTRPRINT and MTKPRINT. If the billing file has been
generated to disk, the contents of the billing disk must be copied to tape
using the command DIRPCOPY in order to read the meters.

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–15

Meter billing file format

Each billing record is packed in a 36-byte record, and then combined with
other records in a 2020-byte block. Each block consists of a 4-byte block
descriptor word (BDW) and either 56 line billing records or 40 trunk billing
records. The final block of billing data is padded with blank billing records
to ensure that all blocks are the same size.
Each block is headed by a BDW. The first 2 bytes of the BDW specify the
block length. The block length is the total of all the records or segments
within the block, including the 4 bytes of the BDW. The third and fourth
bytes are not used and must be zero. Following the BDW are the billing
records.
Each billing record itself is headed by a 4-byte record descriptor word
(RDW). The first 2 bytes of the RDW specify the record length, including
the RDW. The remaining 2 bytes are not used. The remaining bytes contain
the meter data.
Figure 8–6 on page 8–16 and figure 8–7 illustrate the format of line and
trunk billing records for specific examples.
More details on billing formats may be found in the following documents:
Device Independent Recording Package Product Guide, 297-1001-013
Magnetic Tape Reference Manual, 297-1001-118
Automatic Message Accounting - Northern Telecom Format, 297-1001-119
Note: This NTP contains only North American billing record formats.

DMS-100 International Technical Specification BCS40i and up

8–16 Billing

Figure 8–6xxx
Byte format for a line billing record

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

row 0 record length RDW

1
2 7 3 1 6
3 7 7 6 2
4 0 4 3
5 1 1 6 8
6 5 0
7 U S
8 S B
9 E M

10 blank T
11 blank blank
12 blank blank
13 blank blank Example
blank blank DN 6137267734
14
Wrap No
15 1 1 4 2
Date 861105
16 0 0 0 6 Name SUBSMET
17 0 0 0 0 Count 000000061142

indicates unused data fields

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–17

Figure 8–7xxx
Byte format for a trunk billing record

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 bit

row 0 record length RDW

1
2 C I
3 E D
4 D L
5 A I
6 B L
7 blank A
8 blank blank
9 blank blank
10 7 7 0 0
11 7 9 3 0
12 0 1 3 9
13 0 8 2
14 K T
15 O L
16 A C
17 C L
18 L A Example
19 S L Trunk CLLI ICDELDIALBA
blank blank Trunk ID 0077
20
Adnum 0397
21 blank blank
Date 931028
22 0 0 1 4
Wrap No
23 0 0 0 0 Name TKLOCALCALLS
24 0 0 0 0 Count 000000000014

indicates unused data fields

DMS-100 International Technical Specification BCS40i and up

8–18 Billing

Accessing the meter billing system

Generating billing records depends on how subscriber meters are allocated,
deallocated, assigned and deassigned by the metering system, and the
following:
• line and trunk group data changes
• the recovery process
• meter and THQ audits
• system restarts

Line data changes

The billing system is impacted by the following items:
Adding a line
When a line is added to table LENLINES, a meter block is allocated to the
line. The assignment of software meters in the meter block is determined
by datafill in table MSRCDATA. Only assigned meters generate a billing
record.
Deleting a line
When a line is deleted from table LENLINES, billing records for any meters
assigned to that line are written to the metering OOS file. The meter block
is deallocated and initialized for reuse.
Changing line attributes
When line attributes change, new meters may be assigned and old ones
deassigned. All deassigned meters are written to the OOS file. Newly
assigned meters are initialized to 0, and the existing meter block is retained.
Changing directory number or line equipment number
When the DN associated with a particular line equipment number (LEN) is
changed, billing records for all meters assigned to that line are written to the
metering OOS file, and the meters are re-initialized to zero.
When the LEN associated with a DN is changed, records for any meters
assigned to that line are written to the metering OOS file.
When the DNs of two lines are exchanged, the meter records assigned to the
two lines are written to the OOS file, and the meters are re-initialized to 0.
Feature meter assignment
When a line that does not have a feature meter is assigned a subscriber
feature, then a feature meter is automatically assigned to the line. Only one
feature meter is assigned to a line, and it is used for all chargeable features.

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–19

Feature meter deassignment

If a subscriber has a number of chargeable features assigned, deleting one
feature does not effect the meters assigned to the line. A billing record for
the feature meter is written to the metering OOS file, and the meter is
deassigned only when the last chargeable subscriber feature is removed from
the line, and no casual features, such as Do Not Disturb or Wakeup Call are
active.
Deactivating a casual feature on a line that has no other chargeable features
does not cause the feature meter to be deassigned.
Trunk group data changes
The billing system is impacted by the following items:
Adding a trunk
When an incoming trunk is added to table TRKGRP, and Y is specified in
the field METERIC, then a trunk meter block is allocated to the trunk.
Field METERIC also requires a metering data index (MDI) to be specified.
Meters are assigned to every meter name referenced by the MDI specified
in table MSRCDATA.
When field METERIC is set to Y, it can only be set back to N if the trunk
entry in table TRKGRP and the associated entries in tables TRKMEM and
TRKSGRP are deleted and then re-entered.
Deleting a trunk
When an incoming trunk with a software is deleted from table TRKGRP, the
meter is deallocated.
Changing the metering data index of a trunk
When the metering data index (MDI) of an incoming trunk is changed, any
meters not datafilled with the new MDI are deassigned, and the meter counts
logged. Newly assigned meters have their counts initialized to zero.
Meter audits
The metering system performs an audit to ensure the integrity of meter data
and the meter block table. The audit verifies that each line has the correct
number and type of meters assigned, and that every meter marked as
assigned is being used.
Meter audits are run after switch restarts, at times specified by the office
parameter METER_AUDIT of table OFCENG or by commands available at
the MTRSYS menu level of the MAP display.
THQ audit
The metering system provides an audit to ensure the integrity of the tariff
history queue (THQ) blocks used for central control (CC) metering. The

DMS-100 International Technical Specification BCS40i and up

8–20 Billing

audit verifies that each block in the queue is in chronological sequence, and
that each allocated block is in use.
THQ audits are run daily at 03:15, or by commands available at the
MTRSYS menu level of the MAP.
Billing recovery process
Since software meters reside in computing module (CM) data store, they are
not affected by an image reload. Line data, however, only reflects the
information stored when the image was taken, and must be updated by a
journal file (JF) application.
Since call processing can resume before a JF application, the software
meters must be synchronized with the current line data. Since each meter
block contains line ownership information, the line to software meter link
can be restored. Any meter not linked to a line is marked as a recycle meter.
When the JF is applied, an attempt is made to link the line being modified
with new data to one of the recycle meters. If a new line has been added,
the recycle meter associated with the line is used instead of allocating a new
meter.
To avoid retaining recycle meters associated with lines that are not restored,
all recycle meters that have not been linked to lines by the third meter audit
are deleted and written to an OOS file. Meters can be deleted with or
without writing their contents to an OOS file by use of the RCLR command.
Meter backup utility
The metering system contains a backup utility to restore meter data should
the CM data store memory become corrupt. The backup utility copies the
metering data to permanent store in bulk format using DIRP.
Since the backup utility runs automatically, a number of backups are stored
in the same file. The frequency of meter backup images is determined by
the office parameters BACKUP_METER_FREQUENCY_LINES and
BACKUP_METER_FREQUENCY_TRUNKS in table OFCENG.
At the MTRSYS level of the MAP, the command RESTORE can be used to
retrieve the most recent backup data from storage and re-establish meter
integrity. If this command is used after a image reload, the JF should be
applied prior to meter backup.
DIRP MAP level commands can be used to create, mount, demount, rotate
and close the backup files. The MTRSYS MAP level command MSTORE
can be used to create a backup file.

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–21

System restarts
The impact of different types of system restarts on software metering are as
follows:
• Although software metering survives a CC warm restart, any call
spanning the restart has its charge calculated by CC metering not
XMS-based peripheral module (XPM) metering.
• Although software metering survives a CC cold restart, calls do not. As
a result, any call active when a cold restart occurs is not charged.
• Although software metering survives a CC reload restart, calls do not.
As a result, any call active when a reload restart occurs is not charged.
• Although software metering survives a CC reload from image restart,
line data does not. As a result, JF updates must be run to obtain the
latest line information for the audit process.
• Although software metering survives an XPM cold SWACT, calls do
not. As a result, any call terminated by the XPM SWACT is treated as a
failed call.
• Software metering is not affected by an XPM warm SWACT.

Logs
The DMS-100 switch generates log messages that indicate various events
such as surveillance status, maintenance actions, information items, alarms
and suggested corrective actions. There are over 1600 log messages,
arranged within approximately 140 groups.
Control of log messages
Log messages can be controlled as follows:
• Log output is customized by changing the customer data tables listed in
Customer Data Schema, 297-1001-451.
• Commands at the LOGUTIL level of the MAP can temporarily override
parameters set in the customer data tables.
LOGUTIL
The LOGUTIL level of the MAP contains commands that allow you to
browse software buffers for information about messages, and to temporarily
control the routing and generating of reports.
The following documents contain additional information on the operation
and features of LOGUTIL:
• Log Report Reference Manual, 297-1001-840
• DMS-100 Family Maintenance and Operations Manual, NED 297-0003

DMS-100 billing logs

The following table lists all the logs associated with the DMS-100 billing
system.

DMS-100 International Technical Specification BCS40i and up

8–22 Billing

Table 8–1xxx
DMS-100i billing logs
Log Definition

AMAB logs
AMAB122 Displays the international call recording (ICR) international
format record generated by a call.
AMAB153 Displays the ICR Turkey format record generated by a call.
AMAB154 Indicates that an ICR extension block could not be obtained for
a call.
AMAB160 Displays the international CAMA (ICAMA) record code BC or
the international inter administration accounting (IAA) record
code BD generated by a call.
AMAB161 Indicates that recording units could not be obtained for a call.

AMAB188 Contains call data used to produce an international traffic

operator position system (ITOPS) billing extension record for a
CCITT calling card.

APS logs
APS1xx Indicates that an attendant pay station (APS) call was made,
and the log is to be used to obtain the call detail and cost. The
suffix xx indicates the printer device if the log was generated
by a hotel billing information center (HOBIC). If the log was
not generated by the HOBIC, the suffix is 00.

MTR logs
MTR100 Generated when a subscriber’s meter count surpasses the
maximum meter count for the second time in one billing period,
and a wraparound occurs.
MTR107 Generated every time the recovery, table history queue (THQ)
audit, Charge Updating, and THQCLEAN processes begin to
run.
MTR109 Generated every time the recovery, THQ audit, Charge
Updating, and THQCLEAN processes complete.
MTR114 Generated when the changeover system sends a negative
acknowledgement indicating that the international line group
controller (ILGC) or the international digital trunk controller
(IDTC) is not using the correct tariff number tables for a given
list of logical networks.
MTR116 Generated when the displayed line has no meter block
allocated due to an error condition.
—continued—

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–23

Table 8–1xxx
DMS-100i billing logs (continued)
Log Definition

MTR118 Generated when the meter block for the displayed line is also
referenced by another line agent.
MTR119 Generated when all recycle meters in the system are set to
zero, or when the audit runs for the third time after a Reload
Restart.
MTR120 Generated when an attempt is made to charge for a feature
and there is no charge specified in table FEATCHG.
MTR121 Generated when a meter is found with inconsistent control
information during the AGENT/METER audit run.
MTR122 Generated when a recycled meter has been found with
inconsistent control information during the AGENT/METER
audit run.

MTR123 Generated during AGENT or METER audits if the meter block

accessed by the displayed line has a different owner in its
OWNER field.
MTR125 Generated when central control (CC) metering is required for a
new call and there are no metering extension blocks available
to satisfy the request.
MTR127 Generated when there are abnormalities on a THQ.
MTR128 Generated to indicate that fewer than 10% of the THQ blocks
are free.
MTR129 Generated when no THQ resources are available.
MTR132 Generated when the MDI and the name of the meter changes.
MTR134 Generated when there is an inconsistency between the
administration number or the meter combination in the new
and old switch software loads.
MTR135 Generated when a PM software error occurs while attempting
to perform metering on a line-originated or trunk-originated
call.
MTR136 Generated when an invalid logical network is encountered
while attempting to perform metering on a line-originated or
trunk-originated call.
MTR137 Generated when an invalid trunk tariff tuple in a trunk number
table is encountered while attempting to perform metering on a
line-originated or trunk-originated call.
—continued—

DMS-100 International Technical Specification BCS40i and up

8–24 Billing

Table 8–1xxx
DMS-100i billing logs (continued)
Log Definition

MTR138 Generated when an invalid tariff index (TI) was encountered

while trying to perform metering on a line-originated or
trunk-originated call.
MTR139 Generated when an invalid tariff number (TN) is encountered
while trying to perform metering on a line-originated or
trunk-originated call.
MTR140 Generated when an invalid (NIL) index is encountered while
trying to perform metering on a trunk-originated call.
MTR141 Generated when a metering rate mismatch occurs (tables
MTARIFF and MTSIGSYS) while trying to perform metering on
a trunk-originated call.
MTR144 Generated when the datafill determines that meter pulses are
expected from the next office, but none are received.

MTR145 Generated when the meter count reported by the terminator is

greater than that of the originator by a value of more than one.
MTR146 Generated when the meter count reported by the terminator is
less than that of the originator by a value of more than one.
MTR147 Generated when a warm SWACT occurs in any of the
peripherals involved in a tandem call.
MTR148 Generated for all calls that span an international XMS-based
peripheral module (IXPM) warm SWACT to indicate that meter
pulses may have been lost.
MTR149 Generated when the terminating agent is datafilled to receive
meter pulses faster than the originating agent can generate
them.
MTR150 Generated when there is no space available while adding an
item to one of four tables.
MTR151 Generated when an attempt is made to tandem pulses that
exceed the rate of 4 pulses per second.

SCR logs
SCR100 Indicates that a selective call recording (SCR) call was made,
and the log is to be used to obtain the call detail and cost. The
suffix xx indicates the printer device if the log was generated
by the HOBIC. If the log was not generated by the HOBIC, the
suffix is 00.

End

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–25

Priority logs
The following table lists billing priority logs, their alarm class, and the
recommended action.

Table 8–2
Priority logs
Log Alarm Action
class

MTR116 major No meter block has been allocated to a particular

line. Contact the next level of support.

MTR118 major The specified meter block has been referenced by

both the specified line agent and another line agent.
Contact the next level of support.

MTR123 major The meter accessed by the displayed line has a

different owner in its OWNER field. Contact the
next level of support.

Log thresholds and log suppression

In order to assemble a more useful set of statistics, logs can be assigned
thresholds using the LOGUTIL command. Thresholds can be set for
specific counts over a specified period of time, and limits can be set on the
duration of a log to exist before triggering an alarm.
Note: LOGUTIL suppression can be used for logs that highlight large numbers
of events, and are not helpful for diagnostics.

Where to find log information

For additional information about logs, refer to the Log Report Reference
Manual, 297-1001-840, and the DMS-100 Family Maintenance and
Operations Manual, NED 297-0003.

DMS-100 International Technical Specification BCS40i and up

8–26 Billing

Operational measurements
Operational measurements (OM) provide information on switch
performance and activity. OM data is organized by group, with each OM
group consisting of related measurements that are displayed in registers.
Each register has a unique name, and no group has more than 32 registers.
Note: When OMs are polled, the contents of active registers do not
necessarily contain current information, since the frequency of updated
data received at the computing module (CM) varies depending on the
peripheral module type and its status.

DMS-100 billing OM groups

The following table lists the OM groups that are applicable to DMS-100
billing.

Table 8–3xxx
DMS-100i billing OM groups
Group Description

EXT Monitors the use of extension blocks.

MTRUSG Provides information about the usage of the DMS-100i metering
system.
MTRPERF Provides information about the performance of the DMS-100i
metering system.
TOPSINCC Provides information about the use of CCITT calling card
numbers as special numbers for TOPS calls that are alternately
billed.

DMS-100i billing priority OM registers

The following table lists priority OM registers and their associated logs. For
detailed explanations of these OM registers, refer to the Operational
Measurements Reference Manual, 297-1001-814.

Table 8–4xxx
DMS-100i billing priority OM registers
Performance OM group Register Associated logs
factor

Extension block EXT EXTSEIZ –

usage for CCITT EXTOVFL MTR125
calling card calls EXTUSAGE –
—continued—

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–27

Table 8–4xxx
DMS-100i billing priority OM registers (continued)
Performance OM group Register Associated logs
factor

Metering system MTRUSG CCMATCDV –

usage CCMATCUP –
CCATCUPS –
CCMATINI –
CCMATADD –
CCMATTBI –
CCMATCPM –
CCMATXPM MTR135
CCMATERR MTR135, MTR136,
MTR137, MTR138,
MTR139, MTR140,
MTR141, MTR142
LNXPMM1 –
LNXPMM2 –
TKXPMM1 –
TKXPMM2 –
LNCCM1 –
LNCCM2 –
TKCCM1 –
TKCCM2 –
Metering system MTRPERF DTCALLP MTR113
performance DTXPM MTR136, MTR137,
MTR138, MTR139,
MTR140, MTR141,
MTR142
DTFEAT MTR120
TIMEST0
DURERR
COUNTERR
MTRBKERR
MTRAUDER MTR103, MTR104,
MTR105, MTR116
MTR118, MTR123
RECYCFND –
RECYCCLR MTR119
THQOVFL MTR129
THQERR MTR127
TODXPMFL MTR114
Usage of CCITT TOPSINCC INTCCFMT –
calling cards LUHNPASS –
LUHNFAIL –
VALCCTRN –
End

DMS-100 International Technical Specification BCS40i and up

8–28 Billing

OM thresholding
In order to assemble a more useful set of statistics, OMs can be assigned
thresholds for specific counts over a specified period of time, and limits can
be set on the duration of an OM before triggering an alarm.
Maintenance assistance package (feature package NTX053AA) allows
operating company personnel to create a threshold level for individual OMs.
The OMs to be assigned thresholds are entered in table OMTHRESH. The
following information is included in the table:
• OM register name key
• enable trigger (Y or N)
• alarm level (none, minor, major, critical)
• event threshold (1 to 32 767)
• time interval (1 to 32 767 min)

Once the information is datafilled, when a specified threshold is reached

within the designated time, an alarm is generated under the EXT MAP
header of the MAP display.
To find the source of the alarm (for example, OM or DRAM), use the LIST
command at the EXT level of the MAP display.
If the EXT alarm was caused by an OM threshold that had exceeded its
limit, access the OM2 log buffer in the LOGUTIL subsystem to obtain the
number of the register that is generating the alarm. The log buffer OM2
display shows the register number, the associated threshold setting, and the
actual event peg count.
The DMS-100 billing OMs recommended for thresholding, along with the
associated alarm levels and scan times, is determined by maintenance
support personnel.
Switch Performance Monitoring System
Another aid to assist in determining the performance of the DMS-100 billing
system, is the switch performance monitoring system (SPMS).
The SPMS is automatic, and uses switch-generated OM as source data. The
SPMS gathers raw OM data from over 300 registers once every 24 h and
produces over 275 basic indexes of service, maintenance, and provisioning
areas. The basic indexes are combined to form aggregate indexes in a
hierarchical tree format. The aggregate indexes highlight key information.
SPMS is available as feature package NTX738AC.

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–29

DMS-100 billing-specific SPMS index

Table 8–5 contains the DMS-100 billing-specific SPMS index, a description,
and the associated OMs and logs.

Table 8–5
DMS-100 billing SPMS index
Basic Description Associated Associated Associated
index OM group OM registers log

METERPF Metering performance MTRPERF DTCALLP MTR100

DTXPM through
DTFEAT MTR142
TIMEST0
DURERR
COUNTERR
MTRBKERR
MTRAUDER
RECYCFND
RECYCCLR
THQOVFL
THQERR
TODXPMFL

For additional information on SPMS, refer to the Switch Performance

Monitoring System Application Guide, 297-1001-330.
Where to find OM information
For additional information about OMs, refer to the Operational
Measurements Reference Manual, 297-1001-814, and the DMS-100 Family
Maintenance and Operations Manual, NED 297-0003.

Alarms
The following table lists the DMS-100 billing alarms that appear at the EXT
level of the MAP display, their alarm class, and recommended maintenance
actions:

DMS-100 International Technical Specification BCS40i and up

8–30 Billing

Table 8–6xxx
DMS-100 billing EXT alarms
Alarm Alarm Action
class

MCCNACK critical A peripheral device has not responded to a

metering time-of-day changeover request. Contact
the next level of support.

METBCK major The metering backup DIRP file has not been
mounted, which can jeopardize the security of the
billing system. Mount the backup file.

METER minor Less than 5% of the metering resources are

available. Contact the next level of support.

METOOS minor The metering out-of-service DIRP file has not been
mounted, which can potentially deny all metering
system data changes. Mount the out-of-service file.

METXRCYL minor The recycle meters have not cleared successfully

after the METER audit. Contact the next level of
support.

NTHQBLKS minor Less than 10% of the THQ blocks are free for use
by CC metering. Contact the next level of support.

Note: For more information on the DIRP file system, refer to Device
Independent Recording Package Product Guide, 297-1001-013. For
information on tape mounting and demounting procedures refer to Bellcore
Format AMA Maintenance Guide, 297-1001-570.

Commands
This section includes the user–interface command levels and commands that
are associated with DMS-100 billing, including:
• a list and brief description of the AUDIT, DIRP, MTRSYS, LTPMTR,
MTRTTP, and TTPSUB MAP levels, and of specific CI commands, used
for support, and checking for meter content
• a “tree” diagram showing the relationship of the MAP levels and
sublevels to be used
• descriptions of useful non-menu commands

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–31

Menu commands
Figure 8–8 illustrates the hierarchy of DMS-100 MAP menu levels with the
levels associated with billing highlighted. The menu commands available at
the MAP levels associated with billing are illustrated in figures 8–9 to 8–15.
Figure 8–8xxx
DMS MAP menu levels

MAPCI

MTC

MS IOD Net PM CCS Lns Trks Ext APPL

CM

MTRSYS

DIRP LTP TTP

AUDIT

LTPMTR
TTPSUB

DMS-100 International Technical Specification BCS40i and up

8–32 Billing

MTRSYS MAP level menu

The MTRSYS level of the MAP display as illustrated in figure 8–9
provides access to billing meter utilities.
Figure 8–9xxx
Menu commands at the MTRSYS level of the MAP display

CM MS IOD Net PM CCS LNS Trks Ext APPL

. . . . . . . . . .

MTRSYS
0 Quit
2 Qmtrblk
3 Tariff
4 Errscan
5 Errstop
6 Mstore
7 Restore_
8 Billing_
9 TNT_
10 Audit
11
12 THQCLEAN
13
14
15
16
17
18

Commands associated with the MTRSYS level of the MAP display are as
follows:
Qmtrblk
Displays three values: the number of used, unused, and recycle meter blocks.
Since recycle meters may be in used or unused meter blocks, the sum of
these three values do not represent the total number of meter blocks
allocated. A log with this information is also generated.
An example of command output is as follows:
MTRBLKS LINES: USED 619 UNUSED 382 RECYCLE 0
TRUNKS: USED 1253 UNUSED 795
Note: Recycle meter blocks do not apply to trunks, because trunk assignments
are static, while line assignments change frequently. As a result, lines follow a
different recovery process should a RELOAD from image be performed.

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–33

Tariff
Displays the rate of charging for the specified network. A second optional
parameter is the tariff index. This command will display the ANSWER,
INITIAL and OVERTIME tariffs and the time unit. The data is derived
from table MTARIFF.
Errscan
Enables scanning for the metering error status report. This report
corresponds to three MTRERR OM group fields and is displayed on the
screen under the headings: METER OVERFLOW, INVALID MDI and
LATE CHANGEOVER. This command is not supported for trunk metering.
Errstop
Disables scanning for the metering error status report. This command is not
supported for trunk metering.
Mstore
Manually performs backup of software meter counts onto a backup facility.
Restore
Restores meter counts from the backup facility should the software meters
become corrupt.
Billing
Stores charges for lines or trunks on a recording medium from their
software meters, and invokes the billing utility.
TNT
Displays the tariff number table index for the network (or all networks)
based on the current time of day.
Audit
Invokes the AUDIT level of the MAP display.
THQclean
Clears all table history queues to free resources for central control (CC)
metering. This command should be used with caution, as it may reduce the
switch call capacity.

DMS-100 International Technical Specification BCS40i and up

8–34 Billing

TTP MAP level menu

Commands at the AUDIT level of the MAP display as illustrated in
figure 8–10 allows auditing of line and trunk software meters, and table
history queues (THQ).
Figure 8–10xxx
Menu commands at the AUDIT level of the MAP display

CM MS IOD Net PM CCS LNS Trks Ext APPL

. . . . . . . . . .

AUDIT
0 Quit
2
3
4 LnMtrs
5 TkMtrs
6
7 THQAUD
8
9
10
11
12
13
14
15
16
17
18

Commands associated with the AUDIT level of the MAP display are as
follows:
LnMtrs
Verifies that the meterblocks allocated represent the line datafill, and that
there is no corruption in the software meters data structure.
TkMtrs
Verifies that the meterblocks allocated represent the trunk datafill, and that
there is no corruption in the software meters data structure.
THQAUD
Ensures the THQs used in CC metering are sane.

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–35

TTP MAP level menu

The TTP level of the MAP as illustrated in figure 8–11 is used to monitor
and maintain trunk status and access the trunk maintenance sublevels.
Figure 8–11xxx
Menu commands at the TTP level of the MAP display

CM MS IOD Net PM CCS LNS Trks Ext APPL

. . . . . . . . . .

TTP
0 Quit_
2 Post_
3 Seize_
4
5 Bsy_
6 RTS_
7 Tst_
8
9
10 Cktloc
11 Hold
12 Next_
13 Rls_
14 Ckt_
15 Trnslvf_
16 Stksdr_
17 Pads_
18 Level_

The only command associated with the TTP level of the MAP display that
impacts billing services is the LEVEL command. The LEVEL command
has several optional parameters depending on the office configuration. Use
the parameter TTPSUB with this command to access the trunk software
metering facility.

DMS-100 International Technical Specification BCS40i and up

8–36 Billing

TTPSUB MAP level menu

The TTPSUB level of the MAP display as illustrated in figure 8–12 is used
to display the software meters associated with a posted trunk.
Figure 8–12xxx
TTPSUB MAP level menu

CM MS IOD Net PM CCS LNS Trks Ext APPL

. . . . . . . . . .

TTPSUB
0 Quit_
2 Post_
3
4
5 Bsy_
6 RTS_
7 Tst_
8
9
10
11 Hold
12 Next_
13 Rls_
14 GrpMtrs
15 Print_
16
17
18

Commands associated with the TTPSUB level of the MAP display are as
follows:
Post
Posts a specified trunk circuit.
Bsy_
Busies the specified trunk circuit or the posted trunk circuit if no circuit is
specified.
RTS_
Returns to service the specified trunk circuit or the posted trunk circuit if no
circuit is specified.
Tst_
Performs diagnostic tests on the specified trunk circuit or the posted trunk
circuit if no circuit is specified.

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–37

Hold
Holds the posted trunk circuit.
Next_
Seizes the next circuit in the posted trunk group or the held group.
Rls_
Performs a forced release of the specified trunk circuit or the posted one if
no circuit is specified.
GrpMtrs
Display the software meters and their current value for the trunk group of
the posted trunk circuit.
An example of command output is as follows:

TRUNK GROUP: ICTRNK

MTRNAME: LOCALCALLS MTRCOUNT: 000007621 WRAP: N
MTRNAME: NATLCALLS MTRCOUNT: 000297483 WRAP: N
Print
Prints the software meters and their current value for the posted trunk circuit
on a specified device.

DMS-100 International Technical Specification BCS40i and up

8–38 Billing

LTP MAP level menu

The LTP level of the MAP display as illustrated in figure 8–13 is used to
perform manual tests on subscriber lines.
Figure 8–13xxx
LTP MAP level menu

CM MS IOD Net PM CCS LNS Trks Ext APPL

. . . . . . . . . .

LTP
0 Quit_
2 Post_
3
4
5 Bsy_
6 RTS_
7 Diag
8
9 AlmStat
10 CktLoc
11 Hold
12 Next_
13
14
15
16 Prefix
17 LCO_
18 Level_

The only command associated with the LTP level of the MAP display that
impacts billing services is the LEVEL command. The LEVEL command
has several optional parameters depending on the office configuration. Use
the parameter LTPMTR with this command to access the line software
metering facility.

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–39

LTPMTR MAP menu

The LTPMTR level of the MAP display as illustrated in figure 8–14 is used
to display the software meters associated with a posted line.
Figure 8–14xxx
LTPMTR MAP level menu

CM MS IOD Net PM CCS LNS Trks Ext APPL

. . . . . . . . . .

LTPMTR
0 Quit_
2 Post_
3 Counts_
4 Meters_
5 Print_
6
7
8
9
10
11 Hold
12 Next_
13
14
15
16
17
18

Commands associated with the LTPMTR level of the MAP display are as
follows:
Post
Posts a specified line.
Counts
Display meter counts for one or all meters.
Meters
Displays all meters owned by the posted line.
Hold
Holds the posted line.
Next_
Seizes the next circuit in the set of posted lines.

DMS-100 International Technical Specification BCS40i and up

8–40 Billing

Print_
Print all meter counts for posted line. This command takes one parameter –
the device name. If the device is storage device, instead of an input/output
device, then the information is recorded in a file called MTRCOUNTS.
The information consists of the DN, date, LEN, meter names, meter counts
and WRAP bits.
DIRP MAP menu
The device independent recording package (DIRP) level of the MAP display
as illustrated in figure 8–15 is used to access the commands that control the
files and recording volumes of the DIRP.
Figure 8–15xxx
DIRP MAP menu

CM MS IOD Net PM CCS LNS Trks Ext APPL

. . . . . . . . . .

DIRP IOD
0 Quit IOC 0 1 2 3
2 Audit_ STAT . . . .
3 Query_
4 Mnt_ DIRP: . XFER: . DPPP: . DPPU: . NOP: .
5 Dmnt_ SLM : . NX25: . MLP : .
6 Rotate_
7 Close_
8 RsetVol_
9 _AMA_
10 _OM_
11 _JF_
Hidden commands
12
13 cleanup
14 revive
15
16 _Active
17 _Stdby_
18 _Paralel

Note: Hidden commands are not visible on the MAP display.

Audit_
Manually initiates a specific audit procedure.
Query_
Displays the current status of recording files for the specified subsystem.

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–41

Mnt_
Assigns a recording volume to a subsystem.
Dmnt_
Makes the specified volume available to the specified subsystem by
demounting the volume from a DIRP pool.
Rotate_
Initiates manual rotation of duties for the recording files of the specified
subsystem.
Close_
Manually closes specific DIRP files.
RsetVol_
Resets the state of a volume to indicate to DIRP that the specified volume is
now available for recording.
Cleanup
Renames the terminated removed (R) files and deletes closed parallel files.
Revive
Allows the DIRP child processes DIRPGI, DIRPDSON, and DIRPTSON to
be recreated after they have failed.

DMS-100 International Technical Specification BCS40i and up

8–42 Billing

Non-menu commands
QMTRTBL
Enables the user to view the contents of the deassigned meters tables. If a
device and file name are specified, the contents are written into the specified
file.
This command has the following syntax:

>QMTRTBL direct_no MTR meter_name {dev_name} {file_ name}

or
>QMTRTBL direct_no ALL {dev_name} {file_name}
where
direct_no is the directory number of the subscriber
MTR specifies that only the contents of the table
for the specified meter is to be queried
meter_name is one of the meter names datafilled in the
system
ALL specifies that the contents of all the
deassigned meters are to be queried
dev_name this optional parameter enables the
contents of the specified table or all tables
to be copied onto the specified device
file_name this optional parameter provides the name
of the file to which the contents of the
specified table or all tables are to be
written

Example of a MAP display:

DN MTR NAME MTR COUNT MTR DATA BITS DATE AND TIME
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
2000001 localcalls 000009754 T T F F F T 91/04/03 19:00
2000010 localcalls 738402938 F T F T F T 91/04/10 12:00

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–43

IRATE
This command, when entered from the CI prompt, accesses an international
rating test program (IRATE) that enables the operating company to verify
the rating system datafill.
The IRATE program allows the operating company to enter test call details,
and request the rate step or charge calculation or both for the test call, with
the results appearing on the MAP display.
Table 8–7 lists the IRATE subcommands, their associated parameters, and a
description.

Table 8–7xxx
IRATE subcommands
Subcommand Parameters Description

HELP — Help
Displays online documentation about the IRATE program and
its available subcommands.

Q subcommand Query
name Displays more detailed information about each subcommand.

QUIT — Quit
Enables you to exit from the IRATE program, and return to the
CI level.

SHOW — Show current settings

Enables you to show the current entries in all fields.

CLG 1 to 18 digits Calling number

or blank Enter or show the calling number.

CLDTYPE NATIONAL, Called number type

LOCAL, Enter or show the calling number type.
FOREIGN, or
blank

CLD 1 to 18 digits Called number

or blank Enter or show the called number.

CHGTYPE PAID, Charge type

COLLECT, Enter or show the charge type used.
SPLCLG,
SPLCLD, or
blank

—continued—

DMS-100 International Technical Specification BCS40i and up

8–44 Billing

Table 8–7xxx
IRATE subcommands
Subcommand Parameters Description

SPL CC, Special number type

THIRD, Enter or show the special number type, if applicable
NONE,
or blank

OSC STATION, Originating station class

HOTEL, Enter or show the originating station class.
COIN,
APS,
or blank

TSC STATION, Terminating station class

HOTEL, Enter or show the terminating station class.
APS,
or blank

CAT OA, OH, DD, Call type

INTERCEPT, Enter or show the call type.
INWARD,
BOOK,
SPECIAL,
DATABASE,
OPER, or blank

TAC Y, N, or blank Time and charge

Enter or show if time and charge is used.

DB Y, N, or blank Delay call database

Enter or show if the call was retrieved from a database.

DRT Y, N, or blank Dial rate key

Enter or show if the dial rate is used. If Y is specified, then the
call is treated as direct dialed.

SOC MMMDDYYYYH Start of call time

HMMSS, or Enter or show the month, day, year, hour, minute, and second
blank or the start time of the test call. The time of the test call must
be earlier than the actual time the test call is performed.

DUR numeric or blank Call duration

Enter or show the duration of the test call in minutes.

RS numeric or blank Rate step

Enter or show the rate step if the RATE test cannot calculate it.

—continued—

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–45

Table 8–7xxx
IRATE subcommands
Subcommand Parameters Description

USE ACTIVE, Table usage

INACTIVE, Enter or show if the set of active or inactive Rating Data tables
or blank is being used.

CR — Calculate rate step

Used to calculate the rate step based on the current setting of
the IRATE subcommands.

CC — Calculate charge
Used to calculate the charges for the test call if the rate step is
known.

CB — Calculate both
Used to calculate both the rate step and the charges based on
the current settings.

End

IRATE system defaults

The following display shows the IRATE system defaults. These values can
be changed as required.

RS = 0

USE = ACTIVE CLG = 200001 CLD = 200002

CLDTYPE = NATIONAL CHGTYPE = PAID CLASSCHG = STATION
SPL = NONE OSC = STATION TSC = STATION
CAT = OH TAC = N DRT = N
DB =N DUR = 1
SOC = FRI. 1988 JAN 1 00:00:00

DMS-100 International Technical Specification BCS40i and up

8–46 Billing

MTRPRINT
This command prints the line billing file located on a tape onto an
input/output device.
The command has the following syntax:

>MTRPRINT direct_no
where
direct_no is the directory number of the subscriber

MTKPRINT
This command prints the trunk billing file located on a tape onto an
input/output device.
The command has the following syntax:

>MTKPRINT clli adnum

where
clli is the 1 to 16 alphanumeric character common
language identifier assigned to the trunk
group
adnum a 4-digit code used to identify the trunk to
be queried

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–47

DELFM
This command deletes the feature meter from a line’s meter block. The line
must not have chargeable features assigned, or any features active.
The command has the following syntax:

>DELFM {direct_no or all}

where
direct_no is the directory number of the subscriber
all specifies that feature meters for all lines
are to be deleted

RCLR
This command clears the recycle meters.
The command has the following syntax:

>RCLR Y or N
where
Y specifies that the recycle meters are to be written to the
out-of-service file. This is the default value.
N specifies that the recycle meters are not
to be written to an out-of-service file.

DMS-100 International Technical Specification BCS40i and up

8–48 Billing

METVER
This command verifies the consistency of the metering tariff tables, and
should be used after changes to these tables have been made to ensure that
all networks have valid tariffs for all time periods.
The command has the following syntax:

>QMTRTBL direct_no MTR meter_name {dev_name} {file_ name}

or
>QMTRTBL direct_no ALL {dev_name} {file_name}
where
direct_no is the directory number of the subscriber
MTR specifies that only the contents of the table
for the specified meter is to be queried
meter_name is one of the meter names datafilled in the
system
ALL specifies that the contents of all the
deassigned meters are to be queried
dev_name this optional parameter enables the
contents of the specified table or all tables
to be copied onto the specified device
file_name this optional parameter provides the name
of the file to which the contents of the
specified table or all tables are to be
written

Where to find command information

For additional information about commands, refer to the Nonmenu
Commands Reference Manual, 297-1001-820, the Menu Commands
Reference Manual, 297-1001-821, and the DMS-100 Family Maintenance
and Operations Manual, NED 297-0003.

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–49

Translations
Translations is the process by which information in data tables is accessed
by the system and processed to allow the network or feature to operate. In
order to implement DMS-100 billing, certain tables must be datafilled in a
particular sequence to ensure the smooth operation of the network.

Translations database
In order to perform translations, the switch must access data stored in the
computing module (CM) memory called the translations database.
The translations database contains numerous data tables. Each table has a
specific purpose and contains a certain type of data. For example, table
C7RTESET logically associates linksets to be used in routes through a CCS7
network. When processing a call, the DMS switch may access many tables
to collect the data needed to complete the call.
A table consists of horizontal rows and vertical columns of data. Each row
contains one record of data and is called a tuple. Each column is called a
field. Figure 8–16 illustrates the terminology used to describe a table.

DMS-100 International Technical Specification BCS40i and up

8–50 Billing

Figure 8–16xxx
Illustration of translations terms
FW-30072

Table

Key fields Field Field Field

Tuple Data Data Data

Subtable

Field Field Field

Data

Terms used in translations

data
Data is contained in fields. Each field or subfield has a specific value that is
valid for that field. For example, a field called SECONDS may accept
integer values from 0 to 60. The set of all possible data values for a field is
known as the range of the field.
datafill
Datafill is the process of entering data into a table. It is also used as a
synonym for the data itself.
field
A field is one column of a table. Each field has a name that describes the
content of the field. For example, a field that contains directory numbers
may be named field DN.

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–51

key field
Each table has a key field or fields. Tables may have more than one key
field. These fields uniquely identify any tuple in the table. Knowing the key
fields of a table is important when using the table editor.
range
The range of a field is the set of all possible data values that can be entered
in the field. For example, a field called NUMBER may have a range of 1
through 20. RANGE is also a command that can be entered at the switch to
determine the range of the table or field.
subfield
A field is a division of a field. For example, in table C7NETSSN, field
SSNAMES contains two subfields: SSNAME and SSNUMBER.
table editor
The table editor is the user interface to the translation database. It allows the
user to view tables, add or delete tuples, and change data in tuples.
tuple
A tuple is one row of data in a table.
vector
A vector is a field that can contain more than one entry. Each entry is
separated by a space; a plus (+) sign allows continuation to the next line of
data input; and a dollar ($) sign indicates the end of the vector. For example,
the OPTCARD field in table LTCINV can contain up to 10 optional cards;
each entry is separated by a space and the vector ends with the dollar sign.

Using the table editor to modify datafill

The operating company makes routine changes, additions, and modifications
to the datafill in individual tables as required, using the table editor facility
at the MAP (maintenance and administration position).
The table editor is entered from the command interpreter (CI) level of the
MAP display by using the command TABLE followed by the table name.
Inside the table editor, the command LIST displays all the tuples in the table
or only those tuples that meet specific conditions.
A variety of commands are used to modify the information contained in a
table.
The table editor can also be used to add and delete tuples. For a more
detailed description of how to use the table editor, refer to Basic
Translations Tools Guide, 297-1001-360.

DMS-100 International Technical Specification BCS40i and up

8–52 Billing

This section describes the datafill requirements for tables used by the
DMS-100 billing system.
Translations table flow
The DMS-100i billing translation process is shown in the table flow chart on
page 8–53 and includes the following tables.
Table TRKGRP specifies the metering data index (MDI) and the
XLANAME for trunk calls
Table LINEATTR specifies the line attribute index for line originated calls.
Table PXCODE translates the incoming digit string in segments.
Table MSRCDATA specifies the source tariff index (STI) for each logical
network and MDI combination.
Table MDESTIDX specifies the destination tariff index (DTI) for each
logical network and the associated metering zone combination.
Table MTARFIDX specifies the tariff index (TRFIDX) for each each logical
network, STI, and DTI combination.
Table TIMEODAY specifies the tariff number table (TNT) number for each
logical network and day type and time combination.
Table MTARFNUM specifies the tariff number (TARIFNUM) for each
logical network, TNT number and TRFIDX combination.
Table MTARIFF specifies the metering pulse rate for each of the three
phases of a call.

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–53

Table flow for DMS-100i billing

Table Table
TRKGRP LINEATTR

Table
PXCODE

Table Table
MDESTIDX MSRCDATA

Table Table
TIMEODAY MTARFIDX

Table
MTARFNUM

Table
MTARIFF

DMS-100 International Technical Specification BCS40i and up

8–54 Billing

Datafill sequence
The following tables require datafill to implement DMS-100i billing
services. The tables are listed in the order in which they are to be datafilled.

Datafill tables required for DMS-100i billing

Table Form NTP Purpose of table

LNETWORK 3010 297-1001-451 Defines the logical metering networks.

LNMTRNAM 3021 297-1001-451 Specifies the names of line software
meters.
TKMTRNAM 3022 297-1001-451 Specifies the names of trunk software
meters.
TIMEODAY 2264A, B 297-1001-451 Allows various metering rate structures
to be based on the time of day and the
day of the week.

MNETATTR 3012 297-1001-451 Used to determine if detailed toll billing

applies to a line.
MTARIFF 3013A, B 297-1001-451 Specifies the call tariff in phases.

MTARFNUM 3014A, B 297-1001-451 Correlates the source and destination

rate data with the time of day data.

MTARFIDX 3016B 297-1001-451 Defines each metering tariff index.

MSRCDATA 3018A, B 297-1001-451 Defines metering source data and

responsibility.
MDESTIDX 3017A, B 297-1001-451 Defines each metering destination
index.
INTCCMTR 3061 297-1001-451 Used to datafill the initial metering
software load.

MTSIGSYS 3068A,B 297-1001-451 Used to define the meter pulse

characteristics for incoming and
outgoing trunks.

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–55

Datafilling office parameters

The parameters in table OFCENG listed in the following table are required
to define features for the metering system:
For additional information on office parameters refer to Office Parameters
Reference Manual, 297-1001-455.

Office parameters in table OFCENG for DMS-100i billing

Parameter Explanation and action

FEAT_ADMIN_CHARGE Indicates if charges are required on the subscriber’s

feature meter when a feature is assigned to the line.
If the parameter N is specified, no feature charge is
incurred. The default value Y specifies that a
charge is incurred.
MAX_LINES Specifies the maximum number of lines that can be
datafilled in table LENLINES for a DMS-100i. The
value of this parameter can only be increased, and
never decreased. The default value is 0.
MAX_TRUNK_METER_BLOCKS Specifies the maximum number of trunks in table
TRKGRP that can have meter blocks allocated.
The value of this parameter can only be increased,
and never decreased. Changing this value from 0
to a nonzero value requires that IDTC static data be
updated. The default value is 0.
NUM_CCMTR_EXT_BLOCKS Specifies the number of extension blocks that are
allocated for CC metering resources. The default
value is 25.
CCMTR_FAILURE_FREE_CALL Specifies if calls that require CC metering are
allowed to continue for free, when insufficient
resources are available. The default value is N.
METER_AUDIT Specifies the initial meter audit run time and the
frequency of subsequent audits. The default entry
is “0 0 1”, indicating that the initial start time is 00:00
hours and subsequent audits are at one hour
intervals.

—continued—

DMS-100 International Technical Specification BCS40i and up

8–56 Billing

Office parameters in table OFCENG for DMS-100i billing (continued)

Parameter Explanation and action

BACKUP_METER_FREQUENCY_LINES Specifies the initial line meter backup process run

time and the frequency of subsequent backups.
The default entry is “0 0 2”, indicating that the initial
start time is 00:00 hours and subsequent backups
are at two hour intervals. Any change to this
parameter is only effective after midnight of the day
it is changed.
BACKUP_METER_FREQUENCY_TRUNKS Specifies the initial trunk meter backup process run
time and the frequency of subsequent backups.
The default entry is “0 0 2”, indicating that the initial
start time is 00:00 hours and subsequent backups
are at two hour intervals. Any change to this
parameter is only effective after midnight of the day
it is changed.

End

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–57

ICAMA feature description

The ICAMA feature covers the following call data functions for
international billing:
• collection
• formatting
• output

ICAMA requires the reception of automatic number identification (ANI)

digits for all calls originating on ANI trunks as shown in figure 8–17. To
generate records for storage on tape or disk, ICAMA uses the device
independent recording package (DIRP).
Figure 8–17xxx
ICAMA feature application

DMS toll
office

LOCAL ––––––––––
OFFICE ANI Outgoing
trunk trunk
ICAMA
system

LOCAL
––––––––––
OFFICE Outgoing
ANI
trunk trunk

ICAMA feature activation

To activate ICAMA, enter Y for the office parameter
ICAMA_REQUESTED in table OFCVAR.
When ICAMA is activated, the following office parameters must also be
datafilled:
• parameter GENERATE_ICAMA_LOG_ENTRY in table OFCVAR
• parameter ICAMA_ANI_FAILURE_ACTION in table OFCVAR
• parameter RECORD_UNANSWERED_CALLS in table OFCVAR
• parameter INTL_RU_OVFL_ACTION in table OFCVAR
• parameter NUM_ICAMA_RECORDING_UNITS in table OFCENG
• parameter NUM_CALLREC_STREAMS in table OFCENG

DMS-100 International Technical Specification BCS40i and up

8–58 Billing

ICAMA call processing

Calls are selected for recording by ICAMA if
• the originating trunk is an ANI trunk. or
• the call class is an ICAMA required class

Call classes for ICAMA are based on definitions of the universal translation
(UXLA) call classes. Table 8–8 lists the call-class codes supported by
ICAMA.

Table 8–8xxx
ICAMA call class codes
Class Description Feature support

8 = NATL National ICAMA

9 = CNTL Continental ICAMA
10 = ICNTL Intercontinental ICAMA
11 = INTL International ICAMA

Recording unanswered calls

The office parameter RECORD_UNANSWERED_CALLS in table
OFCVAR is used specify if ICAMA records are to be generated for
unanswered calls.
Exception and error handling
ICAMA can address the following types of error handling:
1 ANI failure
2 recording unit allocation failure
3 call failure
ANI failure
The office parameter, ICAMA_ANI_FAILURE_ACTION in table OFCVAR
specifies the action to be taken on ANI failure This parameter allows the
call to drop or continue.
If the call is allowed to continue after ANI failure, it is not billable. The
Calling number field in the ICAMA billing record is set to hexadecimal Fs
(#F). The second digit of the Call info field is set to a value of 4 to indicate
the failure. The call duration is also recorded.
The originating office indicates an identification failure by transmitting an
ANI fail information digit.

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–59

Recording unit allocation failure

If ICAMA cannot allocate a recording unit (for example, when none is
available) office parameter INTL_RU_OVFL_ACTION in table OFCVAR
determines whether calls are allowed to proceed. No ICAMA records are
generated under this condition.
Call failure
If a call fails prematurely (for example, when there is integrity failure or a
forced release) ICAMA generates a record indicating the failure. Since
operating companies may not wish to bill under these failure conditions, the
second digit in the Call info field of the call record is set to a value of 2 to
indicate the failure. The call duration is also recorded.
AMA stream
ICAMA information can be sent to a recording stream separate from that of
international card recording (ICR). Although ICAMA and ICR can coexist
in a DMS switch, each system requires its own separate downstream
processing. Call information for both systems cannot be contained in one
stream.
To provide separate streaming of call information for ICR and ICAMA, use
the following tables:
• CRSFMT
• CRSMAP
• DIRPPOOL
• DIRPSSYS

DMS-100 International Technical Specification BCS40i and up

8–60 Billing

Restarts/SWACTs
This section discusses the impact of the restarts and SWACT on ICAMA
billing.
Cold or reload restarts in the CC
If a cold restart occurs before the call information is written to permanent
storage, the call information is lost. Records would be lost for calls in
progress, as well as any completed calls whose records are still in the
temporary buffer, but have not yet been written to tape or disk.
Figure 8–18 shows the relationship between the time the restart occurs and
the impact of the restart on the recording of call data.
Figure 8–18xxx
Impact of cold or reload restarts on ICAMA recording
FW-31063

a b c d e f g h i

Time

Call Answer Disconnect AMA buffer

origination to DIRP

If the cold or reload restart occurs during time period

a, there is no impact on service.
b, the call does not survive and recording information is lost.
c, the call does not survive and recording information is lost.
d, the call does not survive and recording information is lost.
e, the call does not survive and recording information is lost.
f, recording information is lost.
g, recording information is lost.
h, recording information is lost.
i, there is no impact on service.

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–61

Warm restart in the CC

The impact of a warm restart on ICAMA data varies on the state of the call
when the restart occurs. In most cases, information on the call in progress is
lost or incomplete. In such cases, ICAMA still generates the call record, but
with an error condition indicated in the Information field. All call records in
the temporary buffer are unaffected.
Figure 8–19 shows the relationship between the time the warm restart in the
CC occurs and the impact of the restart on the recording of call data.
Figure 8–19xxx
Impact of CC warm restarts on ICAMA recording
FW-31062

a b c d e f g h i

Time

Call Answer Disconnect AMA buffer

origination to DIRP

If the warm restart occurs during time period

a, there is no impact on service.
b, the call does not survive and recording information is lost.
c, there is no impact on service.
d, the call may or may not survive and recording information may be lost.
e, there is no impact on service.
f, recording information may be lost.
g, there is no impact on service.
h, recording information may be lost.
i, there is no impact on service.

SWACT in the CC
Because all calls are aborted during a SWACT, no data is recorded for calls
in progress.
Cold SWACT/restart in the XPM
If a restart or cold SWACT occurs in the peripheral, the calls are aborted,
although the call record is still generated with an error status. The call
duration is also recorded.
Warm SWACT in the XPM
If a warm SWACT occurs while the call is not in a talking state, for
example, dialing, ringing, answer, or disconnect, ICAMA generates a call
record with a status code of 2 to indicate a call failure.

DMS-100 International Technical Specification BCS40i and up

8–62 Billing

AMA dump utility

To display the hard copy printout of the contents of AMA files produced for
ICAMA recorded calls, use the debug tool AMADUMP. This utility
provides printouts in the following formats:
• a block-by-block hex dump of the contents of a file, whose range of
blocks can be specified by the user
• a record-by-record dump of AMA call entries. data entries, or header
entries within an AMA file
For more information on the AMADUMP utility, please refer to Automatic
Message Accounting-Northern Telecom Format, 297–1001–119.

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–63

ICAMA call record format

This section describes the information contained in the ICAMA call record.
Call record field descriptions
This section describes the fields in the ICAMA record shown in figure 8–20.
Figure 8–20xxx
ICAMA call record format
FW-31060

Word Byte 1 Byte 0

0 CALL CLASS RECORD CODE
1 CALL INFO (CALL MODE)
2 (SERV FEAT)
3 CALLING
4 NUMBER
5
6 CALLED
7 NUMBER
8
9 SPARE
10
11 START TIME
12
13 DURATION
14
15
16
17 OG TRUNK ID
18 IC TRUNK ID

Call class
A binary coded decimal (BCD) digit code that identifies the call class being
recorded. This information is obtained from translations.
Record code
A two–character field that uniquely identifies the type of record. For
ICAMA, the value in this field is BC.

DMS-100 International Technical Specification BCS40i and up

8–64 Billing

Call info
A two-BCD digit code in this field that identifies general call information
using a Y/N (yes/no) format as illustrated in figure 8–21.
Figure 8–21xxx
Call information field details

First digit identifies events during call

Value

Meaning 0 1 2 3 4 5 6 7

Answered N Y N Y N Y N Y
Service analyzed N N Y Y N N Y Y
Chargeable call N N N N Y Y Y Y

Note: Only values 4 to 7 are used by ICAMA.

Second digit identifies call status
0 = Call successful
*1 = Call successful – metering information lost
2 = Call failure – correct call duration recorded
3 = Malicious call trace active – call duration data invalid
4 = ICAMA – ANI failure
5 = ICAMA – ANI identification failure reported by originating office

* This field is not applicable to ICAMA.

Calling number
A ten-digit number, right-justified and padded with #F characters when
required, that identifies the call originator. This information is obtained
from ANI.
Called number
An eighteen-digit number, right-justified and padded with #F characters
when required, that identifies the digits received from translations. These
digits include the country code and national significant number (NSN).
Start time
A twelve-digit BCD field that identifies the year, month, day, hour, minute,
and second when the call was answered.

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–65

Duration
An eight–digit BCD field that identifies the duration of the call measured in
seconds, according to the following equation:
Duration = Disconnect time – Start time
OG Trunk ID
A four–digit BCD field that identifies the outgoing trunk group number.
IC trunk ID
A four–digit BCD field that identifies the incoming trunk group number.
Figure 8–22 summarizes the number of BCD units required for each field in
the call record. A BCD unit contains four bits.
Figure 8–22xxx
Call record tape format

Record Call Call Call Calling Called Date

Code class mode info number number yr mon day
2 2 2 2 10 18 2 2 2

Time Duration Pulse OG IC

count Trunk ID trunk ID
hr min sec
2 2 2 8 8 4 4

DMS-100 International Technical Specification BCS40i and up

8–66 Billing

Call record
Figure 8–23 contains two boxes. The left box is a ICAMA call record that
contains sample data from the bottom of the figure. The right box displays
the position of each data field.
Figure 8–23xxx
ICAMA record format example
Byte 1 Byte 0
BCD BCD
WD 2 3 0 1 Word Byte 1 Byte 0
0 9 0 C B 0 CALL CLASS RECORD CODE
1 0 5 0 0 1 CALL INFO (CALL MODE)
2 F F 0 0 2 (SERV FEAT)
3 F F 6 8 3 CALLING
4 9 0 8 1 4 NUMBER
5 F F F F 5
6 0 0 0 2 6 CALLED
7 6 6 6 1 7 NUMBER
8 1 6 9 4 8
9 SPARE 9 9 9 SPARE
10 9 0 5 8 10
11 7 0 3 2 11 START TIME
12 3 1 5 4 12
13 4 5 3 0 13 DURATION
14 0 0 0 0 14
15 0 0 0 0 15
16 0 0 0 0 16
17 0 2 1 0 17 OG TRUNK ID
18 4 3 2 0 18 IC TRUNK ID

Record code: BC Date: 85–09–23

Call class: CNTL (09) Time: 07:45:13
Call info: 50 Duration: 00000354
Calling number: 180986 Outgoing trunk identification: 0120
Called number: 99–49–611–6662000 Incoming trunk identification: 0234

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–67

ICR feature description

International Call Recording (ICR) allows the DMS-100 switch to record
detailed information about selected calls on either selected lines or all lines
in the office.
ICR call records contain the same data as ICAMA records, but also include
the software meter pulse count associated with the toll call.

ICR feature activation

To activate ICR, enter Y for the office parameter INTL_TCR_REQUESTED
in table OFCVAR.
When ICR is activated, the office parameter
RECORD_UNANSWERED_CALLS in table OFCVAR must also be
datafilled.
All calls to networks that have Y datafilled in field RECORD of table
MNETATTR are recorded.
All toll calls for subscribers with service order option ICR are recorded.

ICR call processing

The following call sequence details the DMS-100 switch functions
associated with an ICR call.
1 Originating subscriber goes off-hook.
2 Dialing sequence is as follows:
— access code dialed by subscriber for national or international access,
plus directory number
— route determined through translations
— meter pulse determined
— preliminary records information collected
3 Called subscriber answers:
— conversation begins
— metering begins
4 Disconnect occurs when originating or terminating subscriber go
on–hook:
— metering stops
— pulse count is added
— remaining information on the toll call is collected
— AMA formats the data and sends to DIRP
— DIRP sends the data to a permanent record

DMS-100 International Technical Specification BCS40i and up

8–68 Billing

ICR call restrictions and limitations

The following restrictions and limitations apply to ICR service:
• Absent Subscriber Intercept Service or Call Diversion: If an answer
signal is not received, the call may not be recorded at the originating
office. Calls diverted to a toll number may not be allowed, depending on
the operating company.
• Toll calls are not affected by malicious call trace (MCT) since only local
calls can be traced.
• Only the pilot number of a hunt group is recorded.
• All calls are billed to the second.
• The terminating subscriber cannot be a local or free–line terminating.
subscriber, as an answer signal is required for charging.
• All zero total pulse counts are unrecorded.
• After a cold restart, all information written to permanent storage is
saved. All records in temporary AMA buffers are lost and are not
recorded
• After a warm restart, all completed calls in the temporary AMA buffer
remain unaffected, but all the pulse count accumulated for the call in
progress are lost. ICR generates a call record, but with an error status.

ICR call record field description

The ICR call record contains the following fields:
Record Code:
For the ICR feature, the value in this field is set to BB.
Call class
A binary coded decimal (BCD) digit code that identifies the call class being
recorded.
Call mode
A two-BCD digit code that identifies the call mode.
Call information
A two-BCD digit code that indicates the call information that is recorded:
Service feature code
A two-BCD digit code that identifies any special service features about the
call originator, that is, whether the call originator is using a standard line or
coin box.
Calling Number
A ten-digit number, right-justified, and padded with #F characters when
required, that identifies the call originator.

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–69

Called number
An eighteen-digit number, right-justified and padded with #F characters,
when required, that defines the digits received from translations. These
digits include the country code and national significant number (NSN).
Start time
A twelve-digit BCD field that specifies the year, month, day, hour, minute,
and second when the call was answered.
Duration
An eight-digit BCD field giving the duration of the call measured in
seconds.
Pulse count
An eight-digit BCD field containing the number of meter pulses
accumulated for the call. For unanswered calls, the value entered is 0 (zero).
OG Trunk ID
A four-digit BCD field that specifies the number of the outgoing trunk group
used during the call.
Figure 8–24 illustrates the different field names, the number of BCD digits
required for each field in the call, and a definition of each field.

DMS-100 International Technical Specification BCS40i and up

8–70 Billing

Figure 8–24xxx
ICR record format

Field Name Size Description

(BCD)

Record code 2 BB for ICR calls.

Call class 2 0 - NIL 5 - LCL 10 - ICNTL

1 - UNKW 6 - SPEC 11 - INTL
2 - IAGRP 7 - EMRG 12 - OPRA
3 - ATT 8 - NATL 13 - IOPRA
4 - DATT 9 - CNTL

Call mode 2 00 - station to station

Call information 2 First digit mappings:

0 1 2 3 4 5 6 7
Answered N Y N Y N Y N Y
Service analyzed N N Y Y N N Y Y
Chargeable call N N N N Y Y Y Y

Second digits mappings:

0 - call successful
1 - call successful, metering lost
2 - call failure, metering lost
3 - Malicious Call Trace active

Service feature code 2 00 - standard line origination

01 - coin line origination

Calling number 10 Call originator’s directory number right justified,

unused numbers are hexadecimal A (#A) filled

Called number 18 Call destination’s directory number entered as right

justified. Unused numbers are hexadecimal A (#A)
filled

Date 6 Year/month/day

Time 6 Hour/minute/second

Call duration 8 Length of call in seconds from answer to disconnect

for answered calls, and from origination time to
disconnect for unanswered calls entered right-justified.
Unused numbers are 0 filled.

Pulse count 8 Pulse count applied to subscriber meter entered

right-justified.

OG trunk ID 4 Trunk group number (2047 is NIL)

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–71

IAA feature description

Inter administration accounting (IAA) provides operating companies with
the capability of recording international toll transit and toll completing call
details. These call details can be used by for division of revenue accounting.
Figure 8–25 illustrates the types of calls associated with IAA.
Figure 8–25xxx
International call types and recording methods
FW-31061

DMS-100
ANI
1

3 International
4
5 National
6

7
8

Type of call Recording method

1. ANI transit ICAMA
2. ANI terminating ICAMA
3. International transit IAA
4. International terminating IAA
5. National transit IAA
6. National terminating IAA
7. Line to trunk International call recording/meter pulse
8. Line to line International call recording/meter pulse

DMS-100 International Technical Specification BCS40i and up

8–72 Billing

Activating IAA
IAA is activated as follows:
1 To indicate those trunks that are to be recorded, datafill Y in subfield
IAA of field GRPINFO in table TRKGRP.
Note: This step applies to MTR trunks only. IAA is not valid for OPR
trunks, nor is the field displayed for ANI trunks.

2 To activate or deactivate IAA for MTR trunks in an office, datafill Y or

N in the office parameter IAA_REQUESTED in table OFCVAR.
Note: When this parameter is set to Y, only calls over trunks covered by
step 1 are recorded. If the parameter is set to N, no IAA records are
generated.

IAA call processing

The call processing procedure for IAA is identical to the ICAMA call
processing procedure described in chapter 4 of this document with the
exception of error handling. The IAA error handling process is described in
the following section.
IAA error handling
IAA accommodates the following error conditions and exceptions:
• recording unit allocation failure
• call failure
• unanswered calls

Recording unit allocation failure

IAA uses ICAMA recording units. If a recording unit cannot be allocated,
(for example, because one is not available), the office parameter
INTL_RU_OVFL_ACTION in table OFCVAR is datafilled. If Y is entered,
IAA records are generated. If N is entered, no IAA records are generated.
Call failure
If a call fails prematurely, for example, as the result of integrity failure or
forced release, an IAA record is generated for the call up to the point at
which it failed.
If billing under failure conditions is not required, the second digit in the
Call info field of the call record is set to a value of 2 to indicate the failure.
The call duration is also recorded.
Unanswered calls
To specify the generation of IAA records for unanswered calls, the office
parameter RECORD_UNANSWERED_CALLS in table OFCVAR is
datafilled Y or N.

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–73

IAA call record description

Although the IAA call record format is as follows:
Record Code:
For the IAA feature, the value in this field is set to BD.
Call class
A binary coded decimal (BCD) digit code that identifies the call class being
recorded.
Call information
A two–BCD digit code that indicates the call information that is recorded:
Service feature code
A two–BCD digit code that identifies any special service features about the
call originator, that is, whether the call originator is using a standard line or
coin box.
Calling Number
A ten-digit number, right-justified, and padded with #F characters when
required, that identifies the call originator.
Called number
An eighteen-digit number, right-justified and padded with #F characters,
when required, that defines the digits received from translations. These
digits include the country code and national significant number (NSN).
Start time
A twelve-digit BCD field that specifies the year, month, day, hour, minute,
and second when the call was answered.
Duration
An eight-digit BCD field giving the duration of the call measured in
seconds.
OG Trunk ID
A four-digit BCD field that specifies the number of the outgoing trunk group
used during the call.
IC Trunk ID
A four-digit BCD field that specifies the number of the incoming trunk
group used during the call.
Figure 8–26 illustrates the different field names, the number of BCD digits
required for each field in the call, and a definition of each field.

DMS-100 International Technical Specification BCS40i and up

8–74 Billing

Figure 8–26xxx
IAA record format

Field Name Size Description

(BCD)

Record code 2 BD for IAA calls.

Call class 2 0 - NIL 5 - LCL 10 - ICNTL

1 - UNKW 6 - SPEC 11 - INTL
2 - IAGRP 7 - EMRG 12 - OPRA
3 - ATT 8 - NATL 13 - IOPRA
4 - DATT 9 - CNTL

Call information 2 First digit mappings:

0 1 2 3 4 5 6 7
Answered N Y N Y N Y N Y
Service analyzed N N Y Y N N Y Y
Chargeable call N N N N Y Y Y Y

Note: Only values 0 to 3 are used by IAA.

Second digits mappings:

0 - call successful
1 - call successful, metering lost
2 - call failure, metering lost
3 - Malicious Call Trace active

Calling number 10 Call originator’s directory number right justified,

unused numbers are hexadecimal A (#A) filled

Called number 18 Call destination’s directory number entered as right

justified. Unused numbers are hexadecimal A (#A)
filled

Date 6 Year/month/day

Time 6 Hour/minute/second

Call duration 8 Length of call in seconds from answer to disconnect

for answered calls, and from origination time to
disconnect for unanswered calls entered right-justified.
Unused numbers are 0 filled.

OG trunk ID 4 Trunk group number (2047 is NIL)

IC trunk ID 4 Trunk group number (2047 is NIL)

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–75

ITOPS feature description

The ITOPS feature involves the collection, formatting and output of call data
for all calls which involve an ITOPS operator. For more detailed
information on the ITOPS feature and call processing procedures, refer to
the ITOPS Product Guide, 297-2181-010.

Activating ITOPS
ITOPS cannot be activated or deactivated by the operating company, as this
feature is software load dependant.
Office parameter VALIDATE_CCITT_LUHN_DIGIT in table OFCENG is
used to specify if check digit verification is required for CCITT format
calling card numbers. The default value is Y (validate check digit).
Office parameter GENERATE_ITOPS_LOG_ENTRY in table OFCVAR is
used to generate a log each time an ITOPS call record is created. The log
number can be AMAB180 for a standard ITOPS record, and AMAB181 to
AMAB186, or AMAB188 depending on the extension record involved in
the call.

DMS-100 International Technical Specification BCS40i and up

8–76 Billing

ITOPS call records

The format for the ITOPS application consists of one standard record and
additional extension records that are appended as necessary.
ITOPS billing records be routed to the same storage devices as other
ICAMA records, or they can be segregated and routed to a different device.
ITOPS standard call record
Figure 8–27 displays the format of a standard ITOPS call record. The
contents of the individual fields are as follows:
Figure 8–27xxx
ITOPS standard record format

ITOPS Call ITOPS Service Class

record class orig Calling Called feature charge Date
code type number number code type
yr mon day
BE 2 2 18 18 2 2 2 2 2

Duration Info Oper Team OG IC

Time digits number number trunk ID trunk ID
hr min sec 1-6
2 2 2 8 6 4 2 4 4

Record code
This field contains information that identifies the type of call record. For
ITOPS, the value is hexadecimal BE (#BE).
Call class
A two-digit binary coded decimal (BCD) code that identifies the call class
being recorded. Only operator assisted (code 12) or operator originated calls
(code 13) are allowed.

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–77

ITOPS originating type

A two-digit binary coded decimal (BCD) code that specifies how the call
was presented to the operator, and is referred to as the call arrival type. For
ITOPS, only the following types are supported
00 – Unspecified
01 – Operator assisted
02 – Operator handled
03 – Direct dialed
04 – Intercept
05 – DA (Directory assistance)
06 – Inward (Originated by another operator)
07 – Booked call
08 – Special (Special requirements)
09 – Database (Delay database originated call)
10 – Oper (Originated by an operator)
Calling number
A number of up to 18 digits, right-justified and padded with hexadecimal Fs
(#F) when required, that specifies the calling party’s number.
Called number
An 18–digit number, right–justified and padded with hexadecimal Fs (#F),
when required, that specifies the called party’s number
Service feature code
A two–digit BCD code that specifies the station class of the calling and
called parties. The first digit contains the calling party’s station class, the
second digit the called party’s station class. Valid codes for ITOPS are as
follows:
0 – Default (station)
1 – Coin
4 – Hotel/Motel
5 – Mobile
6 – Marine
7 – APS (Attended pay station)

DMS-100 International Technical Specification BCS40i and up

8–78 Billing

Class charge type

A two-digit BCD code that specifies how the call is to be billed. Valid codes
are as follows:
00 – Unspecified
01 – Cancelled call
02 – Station paid
03 – Station collect
04 – Station special calling
05 – Station special called
06 – Person paid
07 – Person collect
08 – Person special calling
09 – Person special called
10 – Person call back (PCB)
11 – PCB special billing
Date/time
A 12-digit BCD number that contains one of two times, depending on
whether or not the call is answered. If the call is answered, the field
specifies the answer time in the form year, month, day, hour, minute, and
second. If the call is not answered, the field specifies the time that the call
arrived at the operator position.
Duration
An eight-digit BCD number that contains one of two times, depending on
whether or not the call is answered. If the call is answered, the field
contains the duration of the call in seconds. If the call is not answered, the
field contains the duration, in seconds, that the call remained at the operator
position.

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–79

Information digits
Information digits 1 to 6 record various events that occur during a call as
follows:
• Information digit 1 indicates if:
— ANI has failed for the call
— the operator has entered the called number
— the calling number was identified by the operator
Values for digit 1 that apply to ITOPS are as follows

Meaning Value

0 1 2 3 4 5 6 7
ANI failed? N Y N Y N Y N Y
Operator dialed? N N Y Y N N Y Y
Operator identified? N N N N Y Y Y Y

• Information digit 2 indicates if the call:

— was answered (called party off–hook and start timing in effect)
— failed after successful call set–up
— Indicates if the call was service-analyzed
Values for digit 2 that apply to ITOPS are as follows

Meaning Value

0 1 2 3 4 5 6 7
Call answered? N Y N Y N Y N Y
Call Failure? N N Y Y N N Y Y
Service analyzed? N N N N Y Y Y Y

• Information digit 3 indicates if:

— the call includes a trouble report
— the call includes a charge adjustment
— a no-connect event has occurred on the call (for example, a forward
or backward operator-dialed sequence followed by a no–connect key
operation)
Values for digit 3 that apply to ITOPS are as follows

Meaning Value

0 1 2 3 4 5 6 7
Trouble report? N Y N Y N Y N Y
Charge adjust? N N Y Y N N Y Y
No connect? N N N N Y Y Y Y

DMS-100 International Technical Specification BCS40i and up

8–80 Billing

• Information digit 4 indicates if the:

— operator bills the calls at direct dial rate
— system determines the call to be non–chargeable
— operator has manually marked the call as no-charge
Values for digit 4 that apply to ITOPS are as follows

Meaning Value

0 1 2 3 4 5 6 7
Dial rate key? N Y N Y N Y N Y
No charge origination? N N Y Y N N Y Y
No charge key ? N N N N Y Y Y Y

• Information digit 5 indicates if the:

— call was transferred
— cancel timing key was in effect
— cancel call key was in effect
Values for digit 5 that apply to ITOPS are as follows

Meaning Value

0 1 2 3 4 5 6 7
Transferred call N Y N Y N Y N Y
Cancel timing? N N Y Y N N Y Y
Cancel call? N N N N Y Y Y Y

• Information digit 6 indicates if the:

— operator used toll break-in to verify the calling number
— call was a trunk offering (TBI) offering
— operator has overwritten an out-pulsed forward number for security
reasons
Values for digit 6 that apply to ITOPS are as follows

Meaning Value

0 1 2 3 4 5 6 7
Calling number verify? N Y N Y N Y N Y
Trunk offering (TBI)? N N Y Y N N Y Y
Called number overwrite? N N N N Y Y Y Y

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–81

Operator number
A four-digit BCD number that indicates the number of the operator that
handled the call. If more than one operator was involved, the number
specifies the last operator to handle the call. Operator numbers are datafilled
in table ITOPSOPR.
Team number
A two-digit BCD number that identifies the team to which the last operator
to handle the call belongs. Team numbers are datafilled in table ITOPSOPR.
Outgoing trunk identification
A four-digit BCD number that represents the external outgoing trunk group
name.
Incoming trunk identification
A four-digit BCD number that represents the external incoming trunk group
name.

DMS-100 International Technical Specification BCS40i and up

8–82 Billing

Special billing extension record

A special billing extension record is required when the call is to be billed to
a number other than the calling number.
Figure 8–28xxx
ITOPS special billing extension record

ITOPS Billing Billing Billing

extension number- digit number
code code
E6 2 1 1 18

As shown in figure 8–28, the size of the special billing extension record is
22 BCDs, divided among the following fields:
Extension code
A two-digit BCD code that specifies the type of extension record present.
For special billing, the extension code is hexadecimal E6 (#E6).
Billing number code
A one-digit BCD code specifying the type of special billing number used.
Billing digit
A one-digit BCD code that indicates if the billing number code entered was
verified by the operator, appears on a hot list, or both. Valid entries are as
follows:
• 0 – default value
• 1 – operator-verified, but not a hot list number
• 2 – not operator-verified, but is a hot list number
• 3 – operator-verified, and is a hot list number

Billing number
An 18-digit field that contains the special billing number to which the call is
billed. This field can contain a combination of numeric digits and letter
characters, provided the total number of characters does not exceed 18. The
digits are right-justified and the unused character positions are padded with
hexadecimal Fs (#F) when required.

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–83

Hotel billing extension record

An ITOPS call billed to a hotel number requires a hotel billing extension
record.
Figure 8–29xxx
ITOPS hotel billing extension record

ITOPS
extension Room Guest
code number name
E7 2 6 40

As shown in figure 8–29, the total size of the of the hotel billing extension
record is 48 BCDs divided among the following fields:
Extension code
A two-BCD code that specifies the type of extension record present. For a
hotel billing extension, the BCD extension code is hexadecimal E7 (#E7).
Room number
A field of six BCDs that specifies the room number to which the call is
billed. This field can contain six numeric digits, three alphanumeric
characters, or a combination of numeric and alphanumeric characters.
Guest name
A field of 40 BCDs (20 alphanumeric characters) that contains the name of
the hotel guest as entered by the operator. This field is left-justified and
padded with hexadecimal Fs (#F) as required.

DMS-100 International Technical Specification BCS40i and up

8–84 Billing

Charge extension record

All ITOPS calls require a charge extension record when time and charges are
recorded.
Figure 8–30xxx
ITOPS charge extension record

ITOPS
extension. Quoted
code Amount
E8 2 10

As shown in figure 8–30, the total size of the of the charge extension record
is 12 BCDs, divided among the following fields:
Extension code
A two-BCD code that specifies the type of extension record present. For a
charge extension record, the extension code is hexadecimal E8 (#E8).
Quoted amount
A ten-digit BCD field that contains the quoted cost of the call in the local
currency. The code is right-justified and padded with hexadecimal Fs (#F)
when required.

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–85

Charge adjustment extension record

A charge adjustment extension record is created each time an operator enters
a charge adjustment.
Figure 8–31xxx
ITOPS charge adjustment extension record

ITOPS Time Charge Adjust Amount Filler

extension
Hour Min Type Ind
code
E9 2 2 2 2 1 10 2

As shown in figure 8–31, the total size of the of the charge adjustment
extension record is 20 BCDs, divided among the following fields:
Extension code
A two-BCD code that specifies the type of extension record present. For a
charge adjustment extension record, the extension code is hexadecimal E9
(#E9).
Time
A four-BCD field that specifies the time the operator entered the charge
adjustment. This field is of the form HH:MM.
Charge adjustment type
A two-BCD field that specifies the reason for the charge adjustment entry.
The assignment of charge adjustment types is controlled by the operating
company.
Charge adjustment indicator
A one-BCD field that specifies the type of credit that has been given to the
customer.
Charge adjustment amount
A ten-BCD field that specifies the amount of the charge adjustment. The
type of adjustment value stored is dependent on the value stored in the
adjustment indicator field. All adjustment values are right-justified and
padded with hexadecimal Fs (#F) when required.
Filler
A one-BCD field used to ensure that the charge adjustment record ends on
an even byte boundary, as one byte requires two BCDs.

DMS-100 International Technical Specification BCS40i and up

8–86 Billing

Foreign alternate route extension record

A foreign alternate route extension record is created each time an operator
enters a key sequence to link an alternate route. The alternate route record is
used to determine the division of revenue between the countries linked by an
ITOPS call.
Figure 8–32xxx
ITOPS alternate route extension record

ITOPS Alternate Alternate

extension route route
code country type
EA 2 code
3 1

As shown in figure 8–32, the total size of the of the foreign alternate route
extension record is 6 BCDs, divided among the following fields:
Extension code
A two-BCD code that specifies the type of extension record present. For a
foreign alternate route extension record, the extension code is hexadecimal
EA (#EA).
Alternate route country code
A three-BCD field that specifies the country involved as the alternate route.
Valid values for this field are 000 through 999. Since leading zeros are
required for some country codes, padding is not performed in this field.
Alternate route type
A one-BCD field that indicates the type of alternate route call handled by the
operator.

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–87

Database call extension record

All ITOPS calls that arrive at an operator position from the delay call
database generate a database call extension record.
Figure 8–33xxx
ITOPS database call extension record

ITOPS
extension Database
code class
EB 2 2

As shown in figure 8–33, the total size of the of the database call extension
record is 4 BCDs, divided among the following fields:
Extension code
A two-BCD code that specifies the type of extension record present. For a
database call extension record, the extension code is hexadecimal EB (EA).
Database class
A two-BCD field that specifies the call class of the database call. The
assignment of database call class types is controlled by the operating
company.

DMS-100 International Technical Specification BCS40i and up

8–88 Billing

Special long billing extension record

A special billing extension record is required only when a call is to be billed
to a CCITT format calling card number.
Figure 8–34xxx
ITOPS special long billing extension record

ITOPS Billing Billing Billing

extension number- digit number
code code
ED 2 1 1 19

As shown in figure 8–34, the size of the special long billing extension record
is 23 BCDs, divided among the following fields:
Extension code
A two-BCD code that specifies the type of extension record present. For
special billing, the extension code is hexadecimal ED (ED).
Billing number code
A one-digit BCD code specifying the type of special billing number used.
The only valid entry is 7, indicating a CCITT calling card.
Billing digit
A one-digit BCD code that indicates if the billing number code entered was
operator-verified, appears on a hot list, or both. Valid entries are as follows:
• 0 – default value
• 1 – operator-verified, but not a hot list number
• 2 – not operator-verified, but is a hot list number
• 3 – operator-verified, and is a hot list number

Billing number
A 19-BCD field that contains the CCITT calling card number to which the
call is billed. The digits are right-justified.

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–89

MASSTC feature
The MASSTC command, when entered from the CI prompt, accesses an
international mass table control (MASSTC) program that enables operating
companies to simultaneously activate data changes to the ITOPS tables
listed in table 8–9.

Table 8–9
ITOPS tables associated with MASSTC
Table Form NTP Purpose of table

ATTRIB 2709A,B 297-1001-451 Associates an attribute number to a

unique combination of call origination
types and call attributes.
ATRIMOD 2708A,B 297-1001-451 Defines the discount or surcharge
applied to the charges based on the
incoming schedule and the call
characteristics (call origination type and
call attribute set) of a call.
CHGATRIB 2711A,B 297-1001-451 Contains the attribute specific charge
data.
HOLITRMT 2719A, B 297-1001-451 Specifies the holiday treatment given to
all combinations of holidays and
schedule names.

MODMAP 2722A,B 297-1001-451 Lists the charge modification factor, if

applicable, that applies for each
specified time period.
RATEMOD 2724A, B 297-1001-451 Lists the charge modification factor, if
applicable, that applies for each
specified time period.

RNDING 2729A, B 297-1001-451 Specifies how rounding is applied to

charges for a particular schedule set.

RSFOR 2746A,B 297-1001-451 Associates combinations of schedule

set name and foreign called number
digits with a schedule and rate step.

RSLOC 2747A, B 297-1001-451 Associates schedule set names and

rate steps after the called number is
known to be a local national number.
RSNAT 2748A, B 297-1001-451 Associates combinations of schedule
set names and foreign called number
digits with a schedule and rate step.

—continued—

DMS-100 International Technical Specification BCS40i and up

8–90 Billing

Table 8–9
ITOPS tables associated with MASSTC (continued)
Table Form NTP Purpose of table

SCHEDEF 2749A,B 297-1001-451 Used to associate a schedule name

and rate step range with a termination
type.

TAXES 2780A, B 297-1001-451 Defines the tax rate and method of

combining taxes for each tariff.
TAXMAPS 2742A,B 297-1001-451 Defines the type of tax (if any) that is
applied to a schedule within a
SSETNAME.
TIMEZONE 2743A,B 297-1001-451 Used to specify the difference in time
between the originating party location
and the ITOPS switch.

End

The MASSTC program is always in one of the following states : Initial,

Duplicated, or Switched, as illustrated in figure 8–35. These states allow the
user to create duplicates of these tables, make data changes in the duplicated
tables, test the new data using the IRATE program or live calls, and then
make the new data permanent. These functions are accomplished by
subcommands that are active in each of the MASSTC program states.

Figure 8–35xxx
MASSTC program states

Duplicate
Save INITIAL
state Scrap
Enable

SWITCHED Swap DUPLICATED

state state

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–91

MASSTC program
INITIAL state The MASSTC program is normally in this state. In this
state, the following conditions apply:
• active tables may be edited, and any changes to the datafill will
immediately affect the rating of calls
• the inactive tables are empty
• attempts to add a tuple to an inactive table will fail
Enter the STATUS subcommand in the INITIAL state to display the
following information:
INITIAL STATE
NO INACTIVE DATA
THE FOLLOWING TABLES HAVE INACTIVE TWINS...
TIMEZONE ATTRIB SCHEDEF RSLOC
HOLITRMT MODSET TAXMAPS TAX
RSFOR RSNAT MODMAP CHGHEAD
CHGATRIB ATRIMOD RATEMOD RNDING

DUPLICATED state Enter the ENABLE or DUPLICATE commands to

enter this state. In this state, the following conditions apply:
• If the ENABLE command is entered, the inactive tables are empty
• if the DUPLICATE command is entered, the inactive tables will contain
a copy of the active tables
• all active and inactive tables may be edited
Enter the STATUS command after the ENABLE command to display the
following information:
DUPLICATED STATE
OLD DATA IS ACTIVE
NEW DATA IS INACTIVE
THE FOLLOWING TABLES WERE DUPLICATED AT yy/mm/dd hh;mm....
TIMEZONE ATTRIB SCHEDEF RSLOC
HOLITRMT MODSET TAXMAPS TAX
RSFOR RSNAT MODMAP CHGHEAD
CHGATRIB ATRIMOD RATEMOD RNDING

DUPLICATED STATE
OLD DATA IS ACTIVE
NEW DATA IS INACTIVE
THE FOLLOWING TABLES WERE DUPLICATED AT yy/mm/dd hh;mm....
TIMEZONEI ATTRIBI SCHEDEFI RSLOCI
HOLITRMTI MODSETI TAXMAPSI TAXI
RSFORI RSNATI MODMAPI CHGHEADI
CHGATRIBI ATRIMODI RATEMODI RNDINGI

DMS-100 International Technical Specification BCS40i and up

8–92 Billing

SWITCHED state The MASSTC program enters this state only after the
SWAP command has been entered. In this state, the following conditions
apply:
• the active tables contain the new data
• the inactive tables contain the old data
• inactive tables cannot be edited
Enter the STATUS command in this state to display the following
information:
SWITCHED STATE
NEW DATA IS ACTIVE
OLD DATA IS INACTIVE
THE FOLLOWING TABLES WERE DUPLICATED AT yy/mm/dd hh;mm...
TIMEZONE ATTRIB SCHEDEF RSLOC
HOLITRMT MODSET TAXMAPS TAX
RSFOR RSNAT MODMAP CHGHEAD
CHGATRIB ATRIMOD RATEMOD RNDING

PLN-5001-001i Standard 02.02 April 1997

 Billing 8–93

Table 8–10 lists the MASSTC subcommands and their description.

Table 8–10xxx
MASSTC subcommands
Subcommand Description

HELP Displays MASSTC command information.

STATUS Displays the current status of the MASSTC system.

DUPLICATE Copies the contents of each active table into the corresponding
inactive table.

ENABLE Moves from the INITIAL state to the DUPLICATED state

without copying table contents. Allows inactive tables to be
datafilled with new data.

SWAP Exchanges the contents of the active and inactive tables. This
command can be used anytime during a MASSTC session.

SAVE Saves the current active data permanently. The saved data will
be copied into the active table on all restarts.

SCRAP Erases all new data. The new data must be inactive when this
command is issued.

LEAVE Exits the MASSTC program.

QUIT Exits the MASSTC program. The previously active table data
will be used on all restarts.

DMS-100 International Technical Specification BCS40i and up

 9–1

ITOPS
ITOPS description
The International Traffic Operator Position System (ITOPS) allows an
operating company to provide complete operator assistance on local and toll
calls in a national and international environment. ITOPS combines
hardware and software components to create an effective call-processing
system.
ITOPS is made up of several interactive terminals that are used to handle
calls requiring operator assistance. Each terminal is known as an ITOPS
position and consists of a microprocessor-based controller, a keyboard, and a
cathode-ray tube (crt). An operator uses an operator headset with the
position. Figure 9–1 illustrates the components of an ITOPS position.
Figure 9–1xxx
ITOPS position components

TOPS monitor

ITOPS keyboard

Operator headset

ITOPS
controller
Voice link to DMS switch
Data link to DMS switch

DMS-100 International Technical Specification BCS40i and up

9–2 ITOPS

When handling a call at an ITOPS position, the operator uses the keyboard
and screen to transmit and receive call details. These call details are
exchanged in data form between the controller of the DMS switch and the
ITOPS position controller. The operator’s headset provides voice contact
with calling and called parties, other operators, and supervisors.
ITOPS resides on a DMS-200i toll switch or a DMS-100i/200i local/toll
switch. The ITOPS positions are grouped into teams or traffic offices
according to the call-handling requirements of the operating company. A
traffic office can contain multiple operator positions and assistance
positions. One in-charge position is allowed for each traffic office.

ITOPS services and capabilities

The services an operator can provide at an ITOPS position depend on the
operating company’s office configuration.
ITOPS offers the following services and capabilities:
• ITOPS rating system
— ability to create rate schedules and schedule sets for domestic,
national, and foreign rate zones
— ability to manually enter a rate step when rating table entries do not
exist for that called number
— ITOPS rating test program (IRATE)
— charge calculator
— mass table control
— ability to apply different charges based on call attributes such as coin,
attended pay station, or hotel
— ability to apply discounts and surcharges based on time of day
— ability to apply charges on a minute or second basis
• ITOPS billing plan
— ability to quote charges to a subscriber for hotel and coin calls, calls
requiring time and charges, and attended pay stations (APS)
— third-party billing and verification
— ability to verify calling cards and format calling cards in three ways:
numbering plan area (NPA), overseas, and revenue accounting office
(RAO)
— hot list of bad credit card or third-party numbers
— ability to calculate taxes based on total call charge,
charge-per-minute rate, or charge-per-second rate
— ability to make charge adjustments to bills
— ability to charge a customer at direct dialed rates when circumstances
necessitate using an operator

PLN-5001-001i Standard 02.02 April 1997

 ITOPS 9–3

— call details billing record

• delay call database
— ability to “route queue” outgoing calls so that subscribers need not
try a busy route again
— ability to store calls for a timed period or an untimed period
• automatic number identification (ANI)
• flexible subscriber number formatting
• toll break-in, allowing an operator to interrupt a call and connect a party
with a call with which they have been waiting
• ability to split voice paths so the calling and called parties cannot hear
the other party’s conversation with the operator
• ability to transfer calls from one operator to another
• assistance and in-charge positions to assist and supervise operators
• hotel billing information center (HOBIC)
• periodic force management reports for assigning the operator work force
efficiently
• enhanced Automatic Call Distribution (ACD)
• ability to handle calls from, and bill to, attended pay stations
The following capabilities are enhanced features available with ITOPS:
• ability to specify a fixed duration time for a call, after which it may be
disconnected or returned to the operator
• ability to estimate subscriber call charges for a subscriber
• ability to restrict toll access to subscriber lines by assigning an
authorization access code to each line
• intrusion tone to alert parties that their call is being interrupted by the
operator
These services and capabilities are described in the following pages.
ITOPS rating system
The ITOPS rating system allows the operating company to create rate
schedules, a common set of rating characteristics that apply from an
originating point to a terminating point. Rating tables store the rate schedule
information in the system. Rate schedules can be extensive and flexible
enough to cover all factors that affect rating.
Rate schedules, schedule sets, and rate steps
A group of rate schedules that defines the rating requirements of an
originating point is a schedule set. Schedule sets and rate schedules can be
created for domestic, national, and foreign rate zones. The rate step is an
index to the rate schedule that aids in determining the specific schedule set

DMS-100 International Technical Specification BCS40i and up

9–4 ITOPS

characteristics of a call. The rate step is used with the rate schedule to
determine the charges applicable to a call.
Manual entry of a rate step
The rate step feature allows the operator to manually enter a rate step when
rating table entries do not exist for the called number. The ITOPS operator
contacts the rate and route operator for the rate step calculation or consults a
list of rates.
ITOPS rating test program (IRATE)
The operating company uses IRATE to verify its rating system datafill.
IRATE uses live data from the rating system data tables but is completely
independent of call processing and ITOPS positions. IRATE allows the
operating company to do the following:
• enter relevant details of a test call from the command interpreter (CI)
level
• request rate step, charge calculation, or both rate step and charge
calculation for the test call, with the results appearing at the terminal
Charge calculator
ITOPS can calculate charges on all types of local, toll, and foreign calls and
can take into account factors such as time zones, holidays, and taxes.
Charge application based on attributes: ITOPS allows the operating
company to vary call charges based on call attributes. The following are call
attributes:
• coin
• hotel
• time and charges
• database call
• attended pay station
• person to person
• bill to called party
• bill as person call back
• calling card
• bill to third party
Different charges may be assigned to all combinations of these attributes.
Discount and surcharge application
The operating company can apply discounts or surcharges to the subscriber
based on the date and time of the call. First, the date is checked to see if it is
a discounted holiday rate. After the holiday is checked, the system checks

PLN-5001-001i Standard 02.02 April 1997

 ITOPS 9–5

the day of the week and the method of billing (station or person). Next, the
system checks the origination time of the call. These combined factors
determine any discounts applied to the call.
The operating company may also apply surcharges to a call. Surcharges
may be applied on the following types of billing and charges:
• station collect billing
• station third number billing
• station time and charges
• station calling card billing
• person collect billing
• person third number billing
• person time and charges
• person calling card billing

Charge application per minute or second

ITOPS allows the operating company to define rating tables for toll-call
billing based on an initial period rate and subsequent period rate. The
operating company may apply charges to the subscriber on a minute or
second basis. For example, an initial rate per period may be $2 for the first
three minutes or less. The subsequent rate per period may be $1 for every 30
seconds after the initial period expires.
The initial rate is always charged, even if the call terminates before the
initial period. In this example, a call lasting 20 seconds is billed the
minimum $2 charge.
The subsequent rate is charged at the start of every subsequent period. If the
call lasts 3 minutes 45 seconds, $2 is charged for the initial period, and $2 is
charged for the start of the next two 30 second intervals for a total of $4.
Mass table control
The mass table control feature is used when modifying tables. It allows the
operating company to datafill inactive tables used in the rating system.
When all the required changes are made to the inactive tables, they are
activated simultaneously. ITOPS uses the datafill in the newly activated
tables to calculate toll call charges.
ITOPS billing plan
ITOPS offers an operating company several billing plan features to provide
greater operator efficiency and subscriber flexibility.

DMS-100 International Technical Specification BCS40i and up

9–6 ITOPS

Charge quotations
ITOPS allows the operator to calculate and quote charges to the subscriber
for hotel calls, attended pay station calls, coin calls, and calls requiring time
and charges quotations. Hotel charges are reported to operators at the hotel
billing information center (HOBIC) for quoting. The operator at an ITOPS
position quotes information for the coin calls and the calls requiring time
and charges.
Third-party billing
ITOPS allows the subscriber to bill a call to a third party. The operator has
the option of calling the third party for verification that they will accept the
charges.
Calling-card billing
ITOPS allows the subscriber to use a calling-card number as a method of
billing. The operator verifies the card number by accessing a calling card
database and requesting validation. This function is not directly supported
from an ITOPS position, but the operator has the ability to forward connect
to the appropriate operator who does have this validation information.
ITOPS supports four types of calling-card formats:
• revenue accounting office (RAO)
• overseas
• directory number
• Consultative Committee on International Telephony and Telegraphy
(CCITT)
“
Hot list
The hot list feature allows the operating company to define a table
containing up to 64 fraudulent calling-card or third-party numbers. The
operator is alerted on the display screen of the fraudulent number and can
take the appropriate steps outlined by the operating company.
Tax calculation
ITOPS offers the operating company the option of calculating taxes for a
call based on a percentage of the total call charge or based on the
charge-per-minute or charge-per-second rate of the call.
Charge adjustments
ITOPS allows the operator to make several types of charge adjustments:
• monetary
• time
• entire charge deletion
• mark the call for later

PLN-5001-001i Standard 02.02 April 1997

 ITOPS 9–7

Dial rate function

When a subscriber is unable to make a direct dial (DD) call, the operator can
assist the subscriber and still charge the direct dial rate. An operator may use
this function to assist a handicapped subscriber or to redial a call because of
bad transmission. The dial rate function is used at the operating company’s
discretion.
Call details billing record
ITOPS uses the international centralized automatic message accounting
system (ICAMA) and international call recording formats as a basis for its
call details billing record format. ICAMA extensions to the billing record
allow the operating company to record call details on the following:
• special numbers
• hotels
• time and charge quotations
• charge adjustments
• calls to a foreign country that are linked by an alternate route
• calls stored in the delay call database

Delay call database feature

The delay call database feature consists of an in-core database for storing
and retrieving call details, and a teletypewriter (TTY) device called the delay
call database administration system(DADS). The delay call database allows
the operator to store, modify, and delete calls from the database. The
operator can store calls, set a recall time, and have calls automatically
recalled to the position when the timer expires.
The database can also store calls without a specified time; these are recalled
only when they are manually retrieved by the operator.
Route queuing
Route queuing is a method of storing calls in the ITOPS database that are
waiting for an outgoing route (trunk) group. When a member in the trunk
group becomes available, it is held. The call is recalled to the ITOPS
position so the operator can place the call using the available outgoing trunk.
This saves the time and effort of checking repeatedly for an available trunk.
Automatic number identification
Automatic number identification (ANI) allows the local switch to
automatically identify and transmit the subscriber’s calling number to the
toll switch. From the ANI data, ITOPS can also identify the service class of
the call.

DMS-100 International Technical Specification BCS40i and up

9–8 ITOPS

Flexible subscriber number formatting

ITOPS offers the operating company the ability to define the format of
calling and called numbers as they are displayed on the ITOPS screen and
teletypewriters. An internal table allows the company to format numbers
based on the call type (calling, special, or called) and the number of digits in
the number.
Toll break-in
Toll break-in, supported by certain trunk types, is an ITOPS feature located
in a local office. It allows the operator to do the following:
• interrupt a call between two subscribers when a toll call requires
connection to one of the subscribers
• interrupt the calling party for calling party verification

This feature allows calls to be completed without waiting, if the subscriber

wishes.
Speech path splitting
The speech path splitting feature allows the ITOPS operator to disable the
voice path to either the calling or called party. Operators might use this
feature when they need information from an assistance position or
verification of a calling card. The operator can then reattach the voice paths.
Call transferring
Calls presented to an ITOPS operator can be restricted by call origination
type. A subset of the entire set of call origination types in ITOPS may be
assigned to operators. Then operators can transfer calls they cannot handle to
operators who can handle that type of call.
Calls can be marked for transfer in two ways:
• The administration may datafill a table that automatically transfers a call
to an available operator.
• The operator may transfer, through keying action, a call to another
position for processing.
When a call is marked as a transfer call, it can be presented only to operators
capable of handling this transfer type. The call transfer set active at any
given ITOPS operator position is the combination of the call transfer sets of
the position and of the operator logged into it.
Assistance and in-charge positions
The operating company uses the force management system to evaluate and
control the operator force. The force management system includes the
assistance and in-charge positions.
Assistance positions provide a management tool for assisting operators. The
assistance position terminal has display fields reflecting the general status of

PLN-5001-001i Standard 02.02 April 1997

 ITOPS 9–9

the traffic office. In addition, assistance positions answer assistance requests

from operators and initiate outgoing calls.
In-charge positions have the same capabilities as assistance positions but
have a more extensive set of display fields. These display fields allow
supervisory personnel to monitor the overall status of the traffic office. The
fields are updated every ten seconds to reflect the present status of the traffic
office.
An assistance or in-charge position may also page an operator for a
call-back. The request flashes on the operator position screen and the
operator responds by making a call to the specified position.
Hotel billing information center
Hotel billing information center (HOBIC) is a part of the force management
system that handles hotel billing and allows the operator to quote call details
to hotels for guest-dialed long-distance calls. ITOPS supports two types of
quotation services for hotels – autoquote and voicequote.
Periodic force management reports
ITOPS prints periodic reports for the force and traffic-office administrators.
These reports, printed on the traffic administration data system (TADS) and
force administration data system (FADS) TTY devices, contain operator call
turn-around statistics. These reports provide system as well as individual
operator statistics.
Enhanced Automatic Call Distribution
The enhanced Automatic Call Distribution (ACD) system simplifies and
increases the flexibility of call queuing. This enhanced system takes the calls
destined to operator services, analyzes their call properties, and assigns them
to the appropriate operator or call queue. The enhanced ACD system allows
up to 99 transfer call queues.
Attended pay station call handling
An attended pay station (APS) is a line on a public site where phone calls
can be placed. The billing information for the call is printed on an autoquote
or voicequote printer so the APS attendant can verify or collect the charges
incurred for the call.

DMS-100 International Technical Specification BCS40i and up

9–10 ITOPS

Other ITOPS features

ITOPS has additional capabilities for accommodating special operating
company situations and for offering cost savings associated with call
processing and administration of an operator service system.
Fixed duration calls
The fixed duration feature allows the operator to specify a fixed period of
time on a call. When the time has expired, the call may be disconnected or
returned to an ITOPS position for further handling.
Charge estimations
ITOPS allows the operator to estimate call charges for subscribers for the
current time period and for later time periods. For example, a caller may
inquire about charges to India for 12 minutes at the current time and at a
later time. The operator can use specific keys to create call details as if they
were real without incurring a cost to the subscriber. The operator can create
call detail information for different origination times, call duration, and
attributes.
Toll access restriction by account code
The toll access feature allows the telephone office administration to control
toll access to subscriber lines by assigning up to ten account codes
(authorization access codes) to each standard residential or business line.
Lines without an account code are denied toll services. The operating
company also has the option to record the account code in AMA. This
feature may be useful in countries where automatic tolling must be restricted
because of the lack of available circuits.
Intrusion tone
The intrusion tone is another feature offered to the operating company. This
tone is applied to the two parties involved in the call to alert them that the
call has been recalled to the operator. The tone is heard by the operator, the
caller, and the called parties.

PLN-5001-001i Standard 02.02 April 1997

 ITOPS 9–11

ITOPS software functionality overview

Calls arrive at the ITOPS office through subscriber-dialed digits. Once a
call is received at the office, the system determines the type of telephone
(attended pay station (APS), coin, non-coin, or hotel telephone) from which
the call was placed, and analyzes the digits of the called number to
determine how the call was dialed.
Once the ITOPS system determines these two pieces of information, known
as the station class and the call origination type, it can determine whether
the call should be routed to a carrier, connected to the called party, or routed
to an operator.
This section focuses on calls routed to an operator. The following pages
discuss ITOPS functionality, which includes determining the call origination
type and station class, routing a call to an operator, and handling a call once
it arrives at the operator position.
Call processing functionality
When a call arrives at an ITOPS office, the station class and call origination
type must be identified so that the system can determine whether an operator
is needed to handle the call. If an operator is needed, the system places the
call into an idle position or calls-waiting queue. Calls requiring additional
operator service are placed in a recall queue and handled on a first-in,
first-out basis. The operator handles the call by providing the subscriber
with the appropriate service, satisfying all billing requirements, and
releasing the call.
Determining call origination type
The call origination type indicates how the call was dialed. Table 9–1
describes call origination types that arrive from coin, non-coin, attended pay
stations, or hotel stations.

Table 9–1
Call origination types

Call origination type Description

Operator assisted (OA) The subscriber dialed the number directly but
requires operator assistance.

Direct dialed (DD) The subscriber calls the number directly.

Operator assisted, The subscriber requires operator assistance from

international (INW) an operator in another system.

—continued—

DMS-100 International Technical Specification BCS40i and up

9–12 ITOPS

Table 9–1
Call origination types (continued)

Call origination type Description

Direct dialed, international The subscriber dialed a call direct from a foreign
(FOR) origination without operator assistance.

Directory assistance (DA) Directory assistance is required.

Intercept (INT) A call has been intercepted and the subscriber has
changed the number.

Book (BOOK) The subscriber wants to book a call in the delay call
database.

Database The call originated from the database.

Operator (OPER) The operator has accessed an idle loop (a loop is

one of two lines used to connect calls to an ITOPS
position).

Special (SPL) The call origination is a special type of service iden-

tified by the operating company, for example, emer-
gency numbers.

Notify (NFY) The specified notify period has expired and the call
should be recalled. No operator intervention is
required.

Time and charges (T&C) Time and charges need to be quoted and the call
should be recalled. No operator intervention is re-
quired.

Held (HLD) The call held by the operator has ended and it
should be recalled. No operator intervention is re-
quired.

Coin recall (RCL xx) A specified number of minutes have elapsed and
the call should be recalled. No operator interven-
tion is required.

—continued—

PLN-5001-001i Standard 02.02 April 1997

 ITOPS 9–13

Table 9–1
Call origination types (continued)

Call origination type Description

aaaaaa A display appears that is defined by the office ad-

ministration.

Estimate (EST) Call charges estimate mode is in use (optional fea-

ture).

End

Some calls that originate as DD and OA are recalled to the operator because
no calling number is identified. These calls are:
• operator number identification (ONI) — ONI calls originate at end
offices. End (local) offices are switching offices that accommodate
terminating subscriber lines and provide trunks for establishing
connections to and from other switching offices. These end offices are
not equipped to automatically provide the calling number automatic
number identification (ANI) spill. Therefore, the call is routed to an
operator for collection of the calling number. The operator display for
this call varies depending on whether it is DD or OA.
• automatic number identification failed (ANIF) — ANIF calls originate at
end offices that are equipped to automatically provide the calling
number, but fail to do so on a given call because of resource failure. The
call is routed to an operator for collection of the calling number. The
operator display for this call varies depending on whether it is DD or
OA.
• recall — Recall calls are handled by an operator, released, and returned
to an operator for further operator assistance. The returning operator may
not be the original operator.
— Recalls are initiated by the system for coin calls when additional
coins are required or for alternate billing requests. The operator
screen display varies according to the type of recall.
Determining station class
The station class of the call indicates the type of station from which the call
originates, such as coin, attended pay station, hotel, or non-coin. The station
class is determined by whether the trunk group is dedicated or combined.
Dedicated trunks carry traffic for one station class only, such as coin.
Combined trunks carry traffic from various kinds of stations, such as coin,
non-coin, and hotel.
If a call arrives at an ITOPS office over a dedicated trunk group, the system
automatically determines the station class. If the call arrives on a combined

DMS-100 International Technical Specification BCS40i and up

9–14 ITOPS

trunk group, the ITOPS system determines the station class by examining
the ANI information provided by the end office.
Determining whether an operator is needed
Once the system identifies the station class and call type, it can determine
whether operator assistance is required. OA and OH calls always route to
an operator. DD calls do not normally route to an operator unless there is a
resource failure. ONI and ANIF calls, recalls, and service code calls always
route to an operator.
Routing a call to an operator
ITOPS uses queues to manage calls requiring operator assistance. The
system uses two queues for position management (idle position queues) and
six queues for incoming calls distribution (calls-waiting queues).
Idle position queues: The ITOPS office maintains two queues
associated with operator positions. These queues keep track of the number
of positions that have both loops (loop 1 and loop 2) available, and the
number of positions that have only one loop available. Most incoming calls
are routed to positions that have both loops available. The ITOPS system
office searches the queue for the most idle position and connects the call to
that position. If there are no positions with both loops available, the system
places the call in one of the calls-waiting queues.
Calls-waiting queues: Six calls-waiting (CW) queues are associated
with an ITOPS office:
• nontransfer (general)
• transfer 1
• transfer 2
• nontransfer recall
• transfer 1 recall
• transfer 2 recall
When a call arrives at the ITOPS office and an operator position is available
to process a call (both loops are available), the call is connected directly to
that position. However, if a position is not available, the call is timestamped
and placed in one of the CW queues.
The ITOPS system is configured to automatically distribute calls evenly
across all positions so that no one position is overburdened.
Each operator position is assigned to process calls from one or more of the
CW queues. For example, one operator position can service the general
queue, another can service the transfer queues, and another can service all
queues. The association of positions with queues is defined by the operating
company in datafill.

PLN-5001-001i Standard 02.02 April 1997

 ITOPS 9–15

Calls in the recall queue are handled first. The recall category consists of
calls that have been previously connected to an operator but must be
reconnected for additional assistance. After all recalls are serviced, the
oldest call in the nonrecall queue is connected to an operator.
Nonrecall calls are newly originated calls that have not yet received operator
assistance. The queue in which a call is placed is defined in datafill; for
example, calls can be queued based on call type or trunk group type.
Through datafill, call types can be prioritized within the queues to give
certain call types higher priority.
Dequeueing calls: Within each priority level, calls are serviced on a
first-in, first-out basis, depending on the type of call.
Calls-waiting queue thresholds: The system provides a threshold
mechanism to limit the amount of time a call must wait in the CW queue. If
the threshold is reached, any calls received requiring operator assistance are
deflected for as long as the threshold is exceeded.
Overflow: If the queue size is exceeded, an overflow condition occurs, and
all additional calls requiring operator assistance are deflected. Queue
overflow conditions indicate office engineering problems. Refer to ITOPS
Planning and Engineering Guide, 297-2181-155, for information about
proper engineering of an ITOPS office.
Enhanced Automatic Call Distribution (ACD) queuing: The
enhanced ACD system simplifies and increases the flexibility of call
queuing. This enhanced system takes the calls destined to operator services,
analyzes their call properties, and assigns them to the appropriate operator or
call queue. It provides up to 256 call classes, 64 call queues, and up to 99
combinations of attributes to create new call classes.
Call handling
When a call arrives, the operator is notified by a call arrival tone followed
by a screen display. The screen display is depends on call origination type
and station class. For complete details on screen displays, refer to ITOPS
Operator Guide, 297-2181-300.
Procedures: The basic call-handling procedures are as follows:
1 The operator asks the subscriber for the service desired.
2 The operator enters the appropriate information (calling or called
number, or billing information) and performs the necessary functions.
3 The operator releases the call from the position.
As the operator is processing the call, the DMS is working to establish an
outgoing route for the call. Once the route is established, the operator

DMS-100 International Technical Specification BCS40i and up

9–16 ITOPS

releases the call from the position, the DMS connects the calling and called
party directly; the three-port conference circuit is dropped.
Billing: A call cannot be floated from an operator position until all billing
requirements are satisfied. For all call types, the ITOPS billing system
provides a series of billing classes.
The rate at which a call is billed is determined automatically by the ITOPS
rating system software. This process is transparent to the operator; however,
the operator can provide rate information to the customer upon request.
Immediate rate information is required for the following kinds of calls:
• coin-paid, initial, and subsequent periods
• hotel-paid/APS-paid
• time-and-charges requests

The ITOPS rating system is a collection of data tables containing operating

company-dependent data. This data is used to calculate the rate step and
charge for a call. Refer to ITOPS Translations Guide, 297-2181-350, for
complete details on the ITOPS rating system.
For details on call handling, refer to ITOPS Operator Guide, 297-2181-300.
Operator functionality
From the ITOPS position, the operator can perform any one of the following
functions:
• initiate outgoing calls to a subscriber or to another operator in another
office (known as an inward call)
• transfer a call to another operator
• provide assistance for emergency calls
• help subscribers complete calls
• assign proper billing to subscriber calls
• book calls (route queuing)
• provide special billing capabilities such as credit card billing
• contact directory assistance when needed
• make credit adjustments
• collect and adjust credit for calls billed to coin stations
• perform busy-line verification requests at subscribers’ requests
• request assistance from the service assistant or in-charge manager
• answer pages sent by the service assistant or in-charge manager
• issue trouble reports for subscriber-reported or operator-encountered
service difficulties

PLN-5001-001i Standard 02.02 April 1997

 ITOPS 9–17

Refer to ITOPS Operator Guide, 297-2181-300, for further details on

operator functionality.
Force management functionality
Force management ensures that enough operators are available to handle
normal call traffic and to monitor the quality of the service being provided.
The functions of the force supervisor are as follows:
• ensure that enough operators are available to handle call traffic for every
quarter hour of every day throughout the year
• monitor the quality of services provided, including the speed with which
calls are answered
• monitor the performance of individual operators and the entire team of
operators in the traffic office
• use standard ITOPS measurements to determine work flow
• assign operators to handle transfer calls
• control the types of calls an operator-in-training can receive

The force management system consists of the following equipment types:

• assistance positions
• in-charge positions
• teletypewriters

Operator force configuration determines the type of TTY devices that are
present in an office. There are two types of operator force configurations:
single-traffic office and multitraffic office.
In a single-traffic office configuration, the operator force consists of one
traffic office (the operators are all located in the same place). The
supervisor in a single-traffic office configuration can monitor the status of
the office from an in-charge position that has force management
capabilities.
In a multitraffic office configuration, a force management position monitors
the status of the different traffic offices. The force manager position can
obtain the following types of information for each office:
• the total number of occupied positions
• the number of occupied positions not accepting new calls
• the number of positions that are out of service

In both configurations, assistance and in-charge positions allow supervisors

to assist operators in call handling and monitor their progress.
Several types of TTYs are used in an ITOPS office configuration, and the
functionality of each varies. From the TTY, a force supervisor can perform

DMS-100 International Technical Specification BCS40i and up

9–18 ITOPS

functions such as requesting statistics on call traffic, redefining queuing

thresholds, and reassigning queues and operators. Refer to ITOPS Force
Management Guide, 297-2181-310, for complete details on force
management functionality.
HOBIC functionality
The HOBIC is a centralized operator-attended location that handles toll calls
placed from hotels or attended pay stations (APS). It also provides an
optional service of reporting hotel equipment problems and billing inquiries.
Autoquote (AQ) and voicequote (VQ) TTYs are receive-only TTYs that
transmit guest billing information. The AQ TTY is located at the hotel, and
the record (REC), VQ, and HADS TTYs are located at the HOBIC in the
ITOPS operator office.
For hotels equipped with the AQ service, guest billing information for each
hotel call is automatically transmitted over a dedicated facility to a
receive-only TTY located at the hotel. For hotels not equipped with AQ, the
guest billing information is sent to a receive-only TTY in HOBIC. When
the HOBIC receives the VQ message, a HOBIC operator telephones the
hotel or customer who has requested time and charges (T&C) and relays the
call details. The REC TTY serves as a backup if the AQ or VQ TTY
malfunction. The HADS TTY provides HOBIC personnel administrative
control over the HOBIC system.
Maintenance functionality
Maintenance for the ITOPS system is provided at the MAP (maintenance
and administration position), typically located in the switching center.
Functions that maintenance personnel can perform from the MAP include
the following:
• make a circuit available for maintenance (POST)
• make a circuit unavailable for call processing (BSY)
• run diagnostic tests when a fault is detected (TST)
• return a circuit to service (RTS)

Refer to ITOPS Trouble Locating and Clearing Procedures, 297-2181-520,

ITOPS Maintenance Guide, 297-2181-524, ITOPS Card Replacement
Procedures, 297-2181-525, and ITOPS Routine Maintenance Procedures,
297-2181-523, for complete details on ITOPS maintenance.

ITOPS feature packages

ITOPS offers three basic feature packages and five feature packages that can
be added to the base ITOPS capabilities. This section discusses the three
basic ITOPS feature packages and the primary features associated with each:
• NTXB05 ITOPS Common Basic

PLN-5001-001i Standard 02.02 April 1997

 ITOPS 9–19

• NTXB13 ITOPS Toll–Enhanced Queuing

• NTXB84 International Rating System
Refer to ITOPS Planning and Engineering Guide, 297-2181-155, for
complete details on software packaging requirements.
ITOPS Common Basic - NTXB05
The ITOPS Common Basic feature package provides the basic data
structures for supporting ITOPS positions and operators, call processing, and
the routing of calls to ITOPS positions.
This package supports the operator position setup and the datafill of the
appropriate tables. Each operator and team is assigned characteristics and
numbers in these tables.
The common basic feature package provides extension data called recording
units for storing billing and call control information. It also provides a
routing table that allows the operating company to map digits dialed by
subscribers to operator types, call-origination displays, and charges.
This feature provides a service class table that allows the operating company
to specify call-origination data based on the service class of the calling party.
A service class may be a station, hotel, attended pay station, coin, or
unspecified. The service class is indicated by the ANI spill. Another table
maps the service class of the call to the ANI identifier.
ITOPS Toll–Enhanced Queuing - NTXB13
The ITOPS Toll Basic feature package is the largest feature package
containing the fundamental features of ITOPS. The network connections of
the operator position and ITOPS devices are provided, and the statistics and
reports generated for the force management system are provided by this
feature package. The toll basic package also includes these features:
enhanced ACD, APS call handling, toll break-in, speech path splitting,
ITOPS lines, translation and verification (TRAVER), flexible subscriber
number display, operator hold, and the delay call database.
ITOPS operator position
The ITOPS operator position consists of a crt, keyboard, and a
microprocessor- based controller unit. The operator uses an operator headset
with the position. The position also requires a digital modem and three-port
conference circuit to handle operator calls.
The ITOPS operator position is connected to the DMS switch through two
trunks, a voice trunk and a data trunk, located on an international digital
trunk controller (IDTC).

DMS-100 International Technical Specification BCS40i and up

9–20 ITOPS

The voice trunk connects the operator to any network point through a
conference circuit. The conference circuits are used for connections between
all parties involved in the call. For this reason, three-port conference circuits
are required for ITOPS calls.
The data trunk allows the data flow between the position and the central
control through the digital modem. Through this interface, manipulation of
the voice and data trunks is possible from the maintenance and
administration position (MAP). Refer to the ITOPS Routine Maintenance
Procedures, 297-2181-523, ITOPS Maintenance Guide, 297-2181-524,
ITOPS Card Replacement Procedures, 297-2181-525, and ITOPS Trouble
Locating and Clearing Procedures, 297-2181-520, for details on the
maintenance support for ITOPS position trunks.
Figure 9–2 illustrates the ITOPS operator position connections.
Figure 9–2
ITOPS operator position connections connectional

Network

Voice Data

2 1 0 Central
Three-port IDTC Digital control
conference modem
circuit

Calling Called ITOPS MAP

party party operator
position

ITOPS devices
ITOPS devices are TTYs that are used for various activities throughout the
ITOPS system. Devices monitor performance of the operator workforce and
print operator statistics and information about the system and the traffic
office. They also administer the controlled traffic and operator study
registers, and print time and charges (T&C) data.
The following are ITOPS devices:
• traffic administration data system (TADS) TTY

PLN-5001-001i Standard 02.02 April 1997

 ITOPS 9–21

• force administration data system (FADS) TTY

• system administration data system (SADS) TTY
• delay call database administration data system (DADS) TTY
• T&C TTY (VQ, REC)
• FADSHADS TTY - a combination of FADS and HADS (hotel
administration data system)
• SADSHADS TTY - a combination of SADS and HADS
This feature also provides maintenance support for the ITOPS devices from
the trunk test position (TTP) level of the MAP (maintenance and
administration position).
Refer to the ITOPS Routine Maintenance Procedures, 297-2181-523, and
ITOPS Trouble Locating and Clearing Procedures, 297-2181-520, for
details on the maintenance support for ITOPS devices.
ITOPS administrative positions
ITOPS operators are grouped into teams and assigned to either operator or
administrative positions. The ITOPS administrative equipment consists of
the assistance and in-charge positions.
Assistance position: The service assistant uses the assistance position to
help operators requiring assistance. The assistance position can handle both
general and directed set calls. Requests made to the next available assistance
position are general assistance requests. Requests directed to a specific
assistance position are directed assistance requests. The assistance position
may perform the following functions:
• establish a forward connection onto a currently active loop
• observe the screen display and listen to the headset conversation of an
operator position in the same traffic office
• view call details of a delay call database call
• request a specific operator to recall an assistance position (page)
In-charge position: The in-charge position provides the same functions
as the assistance position but has more extensive screen displays monitoring
the overall status of the traffic office. The screen displays are updated every
ten seconds to reflect the present status of the traffic office.
Refer to ITOPS Operator Guide, 297-2181-300, for details on the field
displays and keys of the administration position.

DMS-100 International Technical Specification BCS40i and up

9–22 ITOPS

Force management system

The ITOPS force management system provides information for
administering the operator work force. It also provides for the internal
management of queues. The ITOPS force management system provides the
following features:
• information for provisioning ITOPS operators on a 15-minute,
30-minute, 6- hour, and 24-hour basis
• indicators of overload and deflection conditions for ITOPS operators and
force supervisors
• control of system and traffic office features
• the HOBIC

The following diagram depicts the force management configuration of a

multitraffic office.
Figure 9–3
Sample configuration of a multitraffic office

Force Management Center

FADS TTY
(Force supervisor)

1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

TADS TTY TADS TTY

In-charge position In-charge position
(In-charge manager) (In-charge manager)
1 - 6 Assistance positions 1 - 6 Assistance positions
1 - 99 Operator positions 200 - 250 Operator positions
(operators) (operators)

Traffic office 1 Traffic office 30

Note: 1. A force management center can cover up to 30 traffic

offices. In this example, operator positions 100 –199
are accounted for in traffic offices 2 – 29.
2. Up to 600 operator positions can be datafilled.

PLN-5001-001i Standard 02.02 April 1997

 ITOPS 9–23

Call transfer types: The force supervisor can restrict the call-origination
types presented to an ITOPS operator by assigning that operator a call
transfer set or a controlled traffic set of calls.
The call transfer set is composed of the call transfer types that operators can
handle. Operators can transfer calls they cannot handle to operators who can
handle those types of calls. Calls can be marked for transfer in two ways:
• The operating company may datafill a table that automatically transfers a
call to an available operator.
• The operator may transfer the call, through keying action, to another
position for processing.
When a call is marked as a transfer call, it can be presented only to operators
capable of handling this transfer type. The call transfer set active at any
given ITOPS operator position is the combination of the call transfer sets of
the position and of the operator logged into it.
The controlled traffic set is composed of the call-origination types that an
operator can handle. Unless specified otherwise, operators are assumed to
be able to handle all ITOPS call types. The controlled traffic set is beneficial
in training new operators because it allows the force supervisor to restrict the
call-origination types to those an operator can handle.
Queue thresholds: ITOPS provides calls-waiting queues when there are
more calls than can be handled by the operator work force. The force
supervisor determines the queue threshold or limit on the number of calls
that can be stored in a queue. Queue thresholds are indicated by the
following signs:
• A display flashes “calls waiting” on the in-charge and assistance position
screens when a queue reaches its assigned threshold. This signal
indicates that operators need to increase their call-handling speed.
• The flashing signal is removed when an operator handles the call and the
number of the calls in the queue is diminished.
• If the call cannot be queued because the call-deflect threshold is reached,
the call is deflected to treatment and a display flashes “calls deflected”
on the in-charge and assistance position screens.
Enhanced Automatic Call Distribution
The enhanced Automatic Call Distribution (ACD) feature simplifies and
increases the flexibility of call queuing. This system takes the calls destined
to operator services, analyzes their call properties, and assigns them to the
appropriate operator or call queue. The enhanced ACD feature is included
as part of the base ITOPS software, but activating it for use is optional.
To increase flexibility, the enhanced ACD system can contain up to 256 call
classes and up to 64 call queues. The system allows the operator to enter up

DMS-100 International Technical Specification BCS40i and up

9–24 ITOPS

to 99 combinations of attributes to create new call classes. These call

classes determine the queue to which the call goes. Call queue limits may
be changed at up to four different intervals to handle different traffic loads.
To simplify the system, enhanced ACD queue thresholds are based on one
table rather than on multiple tables and office parameters.
Attended pay station call handling
An attended pay station (APS) is a line on a public site where phone calls
can be placed. The APS attendant assigns the customer a booth for
completing a call. The billing information from the call is printed on an
autoquote (AQ) or voicequote (VQ) printer so that the attendant can verify
and collect charges on the call from the customer. APS uses the HOBIC
system for billing purposes.
Attended pay stations may be either opened or closed. Open APS calls may
be initiated by the attendant or by the customer. Upon arriving at the APS,
the attendant assigns the customer a booth and charges a deposit, if
applicable. The customer makes the call, and once completed, a bill is
printed on the AQ or VQ printer. The attendant then collects the charges
from the customer.
Closed calls are always initiated by the attendant. Upon arriving at the APS,
the customer gives the call details to the attendant. The attendant then looks
up the call charges and collects that amount from the customer. The
attendant gives the call details to an ITOPS operator and transfers the call to
the customer in the booth. The operator times the call and also notifies the
customer five seconds before the paid number of minutes has expired. Once
the call is completed, a bill is printed on the AQ or VQ printer.
Toll break-in
Toll break-in (TBI) is a feature that allows the operator to interrupt a call
between two subscribers when a toll call requires connection to one of the
subscribers. It also allows the operator to interrupt a calling party for
verification.
TBI may be used when there are few toll circuits or toll circuits are
unavailable because of high traffic volume. In these cases, the operator may
book calls in the delay call database. If the calling or called parties are
involved in other calls, the TBI feature allows the operator to interrupt the
call and offer a toll call to one of the subscribers.
TBI is also used when automatic number identification fails, and the
operator must verify the calling number. The operator first obtains the
calling number and enters it. The operator can then break in on the
subscriber’s line to verify the correct number.

PLN-5001-001i Standard 02.02 April 1997

 ITOPS 9–25

Speech path splitting

Speech path splitting allows the operator to disable the voice path to either
the calling or the called parties. This feature is useful when the operator does
not want one of the parties to hear the conversation with the other party.
Operators may use this feature when interacting with a service assistant or
during calling card verification. The operator can then reattach the voice
paths between the parties.
Figure 9–4 on page 9–26 illustrates the voice trunk configuration of a typical
ITOPS call. Use this figure to visualize the following description of speech
path splitting. Calling party A places a call over trunk number 1. This
incoming call is routed to an ITOPS position by way of a three-port
conference circuit. Calling party A is attached to port number 1 of the
conference circuit, and the operator voice trunk is attached to port 0 of the
conference circuit. The operator enters the forward number of called party
B that translates and routes over outgoing trunk number 2. The outgoing
trunk is connected to port number two of the conference circuit. The
operator and the two parties involved in the call can now talk to each other.
The operator initiates speech path splitting for the calling party, and the
voice is disabled at conference port number 1. The operator and called party
B can still speak to each other. Likewise, when speech path splitting is
initiated for the called party, voice is disabled at conference port number 2,
and the operator and calling party A can speak to each other.

DMS-100 International Technical Specification BCS40i and up

9–26 ITOPS

Figure 9–4
Typical ITOPS call configuration

Trunk #1 Trunk #2
Data Voice
trunk trunk

ITOPS
position
Calling Digital 0 1 2 Called
party modem Conference Party
A circuit B

ITOPS line options

This feature provides two line options for ITOPS: the hotel/motel (HOT)
and operator number identification (ONI) lines. The HOT line specifies a
hotel or motel room line so that the operator can ask for a room number
from the subscriber.
ONI lines are primarily used for verification office testing. Maintenance
personnel can use ONI lines to test termination to ITOPS positions. Party
lines may also use ONI. The ONI option on a party line forces termination to
the operator position, allowing the operator to obtain calling party
identification.
TRAVER capability
The TRAVER (TRAnslation and VERification) feature is a low-level
diagnostic tool that checks the routing and translations of an originating line
or trunk and the digits dialed. It is a fast and efficient way to generate
reports to aid switch maintenance personnel in debugging datafill. TRAVER
debugs datafill by translating digits to a destination in a process similar to
the actual digit translation of a telephone call on a DMS.

PLN-5001-001i Standard 02.02 April 1997

 ITOPS 9–27

If a maintenance person enters a command specifying an ITOPS trunk as the

originator, TRAVER tries to successfully complete the call trace. TRAVER
displays each table used to route the call so that routing and translations can
be verified.
Flexible subscriber number display
The flexible subscriber number display feature allows the operating
company to define the format in which the calling and called numbers are
displayed on the ITOPS position screens and teletypewriters. A table is
provided so that numbers can be formatted based on the type of number
(calling, special, or called) and the digits of the number.
Operator hold
The operator hold feature allows the operator to control connections between
parties. The operator hold, ring forward, and ringback call processing make
up this feature.
Operator hold gives the operator control over disconnect. It is used for
outgoing calls from the local end office to the ITOPS positions in a toll
office. It allows the operator to control the connections between the calling
and called parties. So when the calling party disconnects, the end office does
not initiate a disconnection until it receives a signal from the toll office. This
signal is under the ITOPS operator control.
Operator hold may be used for the following:
• time and charges requests, since they require recall ability to retain
connection to the calling party
• booked calls in a delay call database going in forward or backward
directions
Ring forward is used by an ITOPS operator at the originating toll office to
recall the ITOPS operator at the terminating toll office in a previously
established connection.
Ringback is used by an ITOPS operator at the terminating toll office to recall
the ITOPS operator at the originating toll office in a previously established
connection. Ringback is also used by an ITOPS operator to ring a
disconnected calling party.
Delay call database
When international calls cannot be processed immediately, their details can
be stored in a delay call database from which they can be retrieved later for
processing. All calls stored in the delay call database can be retrieved using
the directory number of the calling party or the serial number assigned to the
call when entered into the database. The administration of the delay call
database is performed through the delay call database administration data
system (DADS) TTY device.

DMS-100 International Technical Specification BCS40i and up

9–28 ITOPS

The delay call database allows the operator to perform the following tasks:
• retrieve calls from the database using the calling number of the
subscriber or the serial number designated by the delay call database
• modify details of a stored call
• delete individual call entries from the database
• delete unprocessed calls in the database that are older than the operating
company’s definable limit. (This is called mass call deletion.)
The delay call database can accommodate 5120 calls at any given time.
Timed delay calls: The operator can store calls, set a recall time, and have
the calls automatically recalled to the position when the timer expires. The
details of the call are displayed at the operator’s crt, but no parties are
involved in the call. The operator must connect the calling and called parties
in the call. If both parties are reached, the call is completed and the operator
can then start timing it. If both parties cannot be reached, the call can again
be stored in the delay call database.
The database can also store calls without a specified time. These calls are
recalled only when they are manually retrieved by the operator.
Untimed delay calls: Untimed delay calls are returned to an ITOPS
operator when a foreign operator informs the ITOPS operator that an
attempted call can now be processed. The operator retrieves the call from
the database and the foreign operator becomes the called party.
The operator’s crt is updated with the call details and the ITOPS operator
attempts to reach the original calling party. When the calling party is
reached, the calling and called connection is established and the ITOPS
operator can start timing the call.
Route queuing: Route queuing is a method of storing calls in the ITOPS
database that are waiting for an outgoing route (trunk group). When a
member in the trunk group becomes available, it is held. The call is recalled
to the ITOPS position so that the operator can place the call using the
available outgoing trunk. This saves the time and effort of checking
repeatedly for an available trunk.
With the route queuing feature, if the subscriber tries to complete a call over
a busy outgoing route, the call can be queued on that outgoing trunk. When a
member in the trunk group becomes available, it is held for the subscriber.
Then the call is recalled to an available ITOPS position, and the operator can
complete the call.
If more than one call requires the same outgoing route, these calls are
queued. The first call requiring the route has the first chance of completion.
Subsequent calls must wait. When the first call is complete, the required

PLN-5001-001i Standard 02.02 April 1997

 ITOPS 9–29

route is idled and is held for the next call in the queue waiting for that route.
At this point, the trunk is not available for normal call processing. This
process continues until there are no more calls waiting for the particular
route and the route becomes idle.
International Rating System - NTXB84
The International Rating System feature package provides the capabilities
needed to rate calls and to calculate charges, including tax, based on
predefined characteristics. Using the rating system, the operating company
can provide subscribers with a reliable and consistent method for rating
ITOPS calls.
The International Rating System allows the operating company to create rate
schedules consisting of a common set of rating characteristics that apply
from an originating point to a terminating point. These schedules can be
used for various combinations of originating and terminating points that
share the same rating characteristics.
Although the rate schedule and the rate step drive the charge calculation for
all rateable calls, billing details also affect the final charges. Call charges
may vary depending on whether the call was person or station billed,
operator handled or assisted, direct dialed, or coin or noncoin. Different
charges may be assigned to various combinations of these factors as required
by the call. The rate schedule provides the necessary refinement of the
charges based on the billing details.
Charge calculator
The charge calculator is a set of procedures used with ITOPS tables that
determines the charges to be applied to all types of local, toll, and foreign
calls. The final charge depends on the following factors:
• type of call
— direct dialed (DD)
— operator assisted (OA)
— operator handled (OH)
— operator assisted, international (INW)
— direct dialed, international (FOR)
— directory assistance (DA)
— intercept (INT)
— book (BOOK)
— database
— operator (OPER)
— special (SPL)
— notify (NFY)

DMS-100 International Technical Specification BCS40i and up

9–30 ITOPS

— time and charges (T&C)

— held (HLD)
— aaaaaa (defined by administration)
— coin recall (RCL xx)
— estimate (EST)
• type of service
— coin
— hotel
— time and charges
— database call
— attended pay station (APS)
• type of billing
— person to person
— station to station
— collect
— bill to third number
— bill to calling card
• duration of the call
— charges and duration of initial period
— charges and duration of subsequent periods
• surcharges due to additional services provided
• discounts
— time of day
— holidays
• taxes
• rounding of charges — up and down
This
These factors are stored on tables in the system. The way these tables are
datafilled determines the final charge for all relevant call types. The
characteristics of calls are discussed in the following paragraphs.
Attributes: ITOPS allows the operating company to vary call charges
depending on call attributes. Call attributes are the functional or physical
details of a call. For example, physical attributes may be hotel or coin calls,
and functional attributes may be calls booked in the database or calls that are
recalled to the operator. Attributes are mapped to call origination types to
form call classes. The following are call attributes:
• coin

PLN-5001-001i Standard 02.02 April 1997

 ITOPS 9–31

• hotel
• time and charges
• database call
• attended pay station
• person to person
• bill to called party
• bill as person call back
• calling card
• bill to third number
Different charges may be assigned to all combinations of these attributes.
Call duration: Most operating companies have two basic rates for billing
toll calls: an initial period rate and a subsequent period rate. The operating
company may apply charges to the subscriber on a minute or second basis.
For example, an initial rate per period might be $3 for the first three minutes
or less. The subsequent rate per period might be $1 for every 45 seconds
after the initial period expires.
The initial rate is always charged, even if the call terminates before the
initial period. The subsequent rate is charged at the start of every subsequent
period.
The operating company has the option to datafill tables for accommodating
any of the following three scenarios:
1 The initial and subsequent period rates are measured in minutes. The
charge is $2.00 for the one-minute initial period and $.55 for the
one-minute subsequent interval. The net charge for a call lasting one
minute and forty seconds is $2.55.
2 The initial and subsequent period rates are measured in blocks of sixty
seconds. The charges are $1.60 for the sixty-second initial period rate
and $1.40 for the sixty-second subsequent period rate. The net charge
for a call lasting one minute and forty seconds is $3.00.
3 The initial and subsequent period rates are measured in seconds. The
charge is $1.50 for the sixty-second initial period and $.50 for the
thirty-second subsequent period rate. The net charge for a call lasting
one minute and forty seconds is $2.50.
The schedule name and rate step number create an indexing key into the call
duration table. When charge information is required, the index key is used
to obtain the length of the initial and subsequent periods as well as the
charges associated with the index.
The charges can be in cents, dollars, pounds, or other currency as long as the
monetary system is based on decimal and arithmetic values.

DMS-100 International Technical Specification BCS40i and up

9–32 ITOPS

Discounts and surcharges: The operating company can apply discounts

or surcharges to the subscriber based on the date and time of day of the call.
These combined factors determine any discount applied to the call.
Normally, discounts are applied for calls made during nonprime periods. For
example, a call made at 10:00 P.M. may cost $3.00 while the same call at
11:00 P.M. may cost $2.50.
The operating company may also apply surcharges to a call. Surcharges are
a way to compensate when additional resources are needed for completing a
call. Surcharges may be applied on the following types of billing and
charges:
• station collect billing
• station third number billing
• station time and charges
• station calling card billing
• person collect billing
• person third number billing
• person time and charges
• person calling card billing

Time zones: Time zone variations are needed when the office the ITOPS
switch is serving is in a different time zone from the ITOPS switch. In these
cases the time in the originating office is used to calculate charges.
The table specifying time zone information provides, in minutes, the time
difference between the local time and the time of the called party. The
default value is zero. Even when the called party is paying for the call, the
time used here is the time of the originating party.
Holidays: The charge calculator defines the year’s holidays that receive
special rating, as well as specifying the type of treatment applied to calls
made during the holidays.
Taxes: Taxes are applied to a call after the basic charge (initial and
subsequent), class charges, and any surcharges are calculated.
Federal, state/provincial, and municipal taxes can be applied singly or in
combinations. For example, the state/provincial tax and the municipal tax
may be combined as the second tax and applied to the charges after the first
tax.
The operating company can specify two ways for taxes to be applied:
• tax rates for taxes based on the entire call charge
• tax rates for fixed rates based on the initial period (charge-per-minute or
charge-per-second) rate of the call

PLN-5001-001i Standard 02.02 April 1997

 ITOPS 9–33

Tax types or methods are either fixed or rate. Fixed-rate tax types are fixed
tax charges applied to a call. Rate tax types are based on the charge of the
call. In addition to specifying the taxing method, the datafill can be entered
to allow either prediscount or postdiscount charge taxes to be applied.
Rounding factors: Rounding factors, like taxes, are applied to a call after
the basic charge (initial and subsequent), class charges, and any surcharges
have been calculated.
The operating company can specify how rounding will be applied to charges
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.
• Rounding is applied to each tax before adding to charges.
• Rounding is applied to total charges after tax.

Rate-step calculation
The rate-step calculation feature allows the operating company to calculate
and define rates for each office. Figure 9–5 on page 9–34 shows the various
rates the ITOPS rating system can calculate. The home switch in Figure 9–5
is in country WW and handles areas 1 and 2. This allows the operating
company to create a different set of rates from each office in country WW to
any other office in country WW. Also, from each office in country WW, the
operating company may set up a different set of rates for each country (in
this case XX, YY, and ZZ).
A caller from office A calling office B can have a different rate from one
calling from office C to office B, or office D to B, or even office B to A.
This is done by defining a schedule set for each office (area code office
code). A rate schedule is a set of charges for the type of call being made. A
schedule set consists of multiple rate schedules applicable to a chargeable
call.

DMS-100 International Technical Specification BCS40i and up

9–34 ITOPS

Figure 9–5xx
Rating areas

Country WW

office office office office

A B C D

Country
XX
Country
YY
Country
Area 1 ZZ

office office office office

E F G H

Area 2

A charge is calculated based on the factors listed on page 9–29.

If the area served is divided into schedule sets, the system can provide
charges for a large number of subscribers. Using figure 9–5 as an example,
the serving area could be divided as follows:
• Office A is schedule set 1
• Office B is schedule set 2
• Office C is schedule set 3
• Office D is schedule set 4
• Office E is schedule set 5
• Office F is schedule set 5

PLN-5001-001i Standard 02.02 April 1997

 ITOPS 9–35

• Office G is schedule set 5

• Office H is schedule set 5
This example allows offices A, B, C, and D to have a different set of
schedules, while offices E, F, G, and H use the same set. Each schedule
defined would be a set of rates (for example, national rates, foreign rates,
local rates). The schedule is determined by the called number. The actual set
of rates within the schedule is defined by the called number as well.
The charges within a rate are determined by the call attributes defined on
page 9–30, the time of day (for example, calls after 8:00 P.M. may be
discounted by 60 percent), and the type of day (for example, a call on the
weekend may be discounted by 50 percent). Also provided is the ability to
apply surcharges and discounts on a one-time-only basis. These surcharges
and discounts are applied based on the call attribute.
The tables in the rate-step calculator allow the user to specify rating data
with no dependence on the length of the calling or the called number.
The rate steps calculated by these tables, together with the schedule set name
and the schedule, provide the means to calculate a charge for a call.
Defining a schedule set: The DMS handles the operator services for a
number of local offices. If the switch is a DMS-100i/200i configuration, it
can handle both local and toll office calls.
The DMS-200i switch provides on-line rating for coin-paid, hotel, T&C, and
APS calls. Each local switch can have its own set of rates.
The DMS-100i/200i switch provides on-line rating for coin-paid, hotel,
T&C, and APS calls. Again, each office is allowed a different set of rates.
This section is concerned only with defining the schedule (or set of charges).
The actual charges are calculated by the charge calculator.
To allocate the sets of schedules, administration performs the following
tasks:
• Defines the names to be allowed. To do so, the names of all schedule
sets to be used by the rating system must be entered in a schedule set
name.
• Maps the originating area of the call with a schedule set name.
• Defines the schedules to the rating system.
297-2181-010

DMS-100 International Technical Specification BCS40i and up

9–36 ITOPS

Finding a rate step: Once the schedule sets and schedules are defined,
the index into the specific schedule must be provided to get the charges for
the call. This index is found by mapping the calling schedule set and the
called number to a specific schedule and rate step. A rate step is a value
used in a standard algorithm that calculates the final charges for all rateable
calls and is used as an index into a schedule. There are three types of called
numbers: national, foreign, and local.
National rating: This type of rating applies when the called number is a
national toll call. National rate step calculation allows the definition of a
schedule and a rate step based on calling schedule set name and the called
area and office code. There is also an indicator of what type of rate
calculation is to be done to find the rate step. Only single rate area is
defined.
Foreign rating: Foreign rating is used when calling a foreign country.
This type of rating allows the definition of one set of charges from each
schedule set name to each country (or country and city).
Local rating: Local rating is used when the called number is within the
same local serving area. This type of rating provides a schedule and a rate
step for each calling schedule set name.
Manual entry of a rate step
When rating table entries do not exist for a called number, the operator can
enter a rate step manually. The ITOPS operator contacts the rate and route
operator for the rate step calculation or consults a list of rates for entry into
the system.
ITOPS rating test program
The ITOPS rating test program (IRATE) feature allows the operating
company to verify its rating system datafill. IRATE may be used on its own;
however, it is designed to be used with the mass table control feature
(described below). IRATE uses live data from the rating system data tables
but is completely independent of call processing and ITOPS positions.
IRATE allows the operating company to accomplish the following tasks:
• enter relevant details of a test call from the command interpreter level
• request rate step, charge calculation, or both for the test call with the
results appearing at the terminal

PLN-5001-001i Standard 02.02 April 1997

 ITOPS 9–37

Mass table control

The mass table control feature permits simultaneous activation of data
changes in ITOPS mass table controlled tables. Data changes intended for
active tables are entered into inactive tables. When all required changes are
entered into the inactive tables, the contents are activated and the newly
activated tables are used in calculating toll charges. Call processing always
uses the active tables. Mass table control is always in the initial, duplicated,
or switched state.
Figure 9–6xxx
Mass table control state diagram

Duplicate
Scrap
Initial
Enable

Swap
Switched Duplicated

Initial state: Active tables may be edited, and any changes to the datafill
have immediate implications in the rating of calls. The inactive tables are
empty.
Duplicated state: Two commands can cause the system to enter the
duplicated state. One command causes the inactive tables to start out empty,
and the other command causes the inactive tables to start out with a copy of
the active data.
All tables can be edited. Table control error checks ensure that the active and
inactive data form consistent sets.
Switched state: The system enters the switched state only after the swap
state is entered. In the switched state, the active tables contain new data, and
the inactive tables contain the old data.

DMS-100 International Technical Specification BCS40i and up

9–38 ITOPS

Calling card billing

ITOPS allows the subscriber to use a calling card number as a method of
billing. ITOPS supports revenue accounting office (RAO), overseas,
directory number, and Consultative Committee on International Telegraphy
and Telephony (CCITT) calling card formats.
RAO: RAO is a fourteen-digit, fixed-length format. Its two major parts
consist of the account number and the personal identification number (PIN).
The RAO format is differentiated from the directory number format by the
digits zero or one in the account number.
Overseas: The overseas format may contain up to twelve digits in a
variable length format. Its two major parts consist of the country code
number and one alpha character indicating the end of the country code.
Directory number: The directory number format is a fourteen-digit,
fixed-length format. Its two major parts consist of the account number and
the personal identification number (PIN). The account number is in the
same format as the subscriber’s directory number.
CCITT: The CCITT format is a five to twenty-three digit variable length
format that provides a world-wide standard for telecommunications calling
cards. Its four major parts consist of the issuer identification number, the
individual account identification number, the Luhn check digit, and the PIN.
Verification: Operators may verify calling card numbers by accessing a
calling card database and requesting validation. This function is not directly
supported from an ITOPS position, but the operator can connect forward to
the appropriate operator who does have this validation information.
Third-party billing
Subscribers may bill to third party numbers. Only numbers in the NPA
format are used for third-party billing. Verification is also available for
third-party billing. The operator may attempt a verbal acceptance of charges
from the third-party number.
Hot list
ITOPS allows the operating company to define a table containing up to 64
fraudulent or stolen calling-card or third-party numbers considered “hot.”
When an operator enters one of these hot numbers, the number is matched
with the entries in the defined hot list table. The operator is alerted by the
display screen of the match and can take appropriate action as defined by the
operating company.

PLN-5001-001i Standard 02.02 April 1997

 ITOPS 9–39

Charge modifications
ITOPS allows the operator to make charge adjustments for subscribers. The
operator can make monetary or time adjustments, delete the entire charge for
a call, and mark the call for later adjustment.
When the subscriber is unable to complete a direct dialed (DD) call, the
operator can assist the subscriber and still charge the DD rate by using the
dial rate function. This function may be used for assisting handicapped
subscribers or re-dialing calls because of bad transmission. This dial rate
function is used at the operating company’s discretion.
ITOPS call details billing record
ITOPS uses the international centralized automatic message accounting
(ICAMA) and the international call recording (ICR) formats as guidelines
for its call details billing record. This record is divided into a standard call
details billing record and six extension records.
A standard call details billing record is created for each call arriving at an
operator position. Extension records are included for certain types of
operator-handled calls, and they contain additional information needed to
bill the call.
Table 9–2 describes the items found in the standard call details billing
record.

Table 9–2
Standard call details billing record

Item Description

Record code The type of record

Call class The call class being recorded

ITOPS originating type How the call was originally presented to the
operator

Calling number The calling party’s number

Called number The called party’s number

Service feature code The station class of the calling and called parties

Class charge type How the call is billed

—continued—

DMS-100 International Technical Specification BCS40i and up

9–40 ITOPS

Table 9–2
Standard call details billing record (continued)

Item Description

Start/answer time The time the call was answered, or the time the call
was not answered and arrived at the operator posi-
tion

Duration The duration of the call if it was answered, or the

duration of the call at the operator position if it was
unanswered

Information digits one Various events that occur during a call, such as the
through six operator entering the called number, ANI failed for
the call, the call failed after successful call setup,
the call includes a trouble report, the call includes a
charge adjustment, the operator billed the call at a
direct dialed rate, the call was transferred, or the
operator used toll break-in to verify the calling num-
ber

Operator number The number of the operator involved in the call

Team number The team number of the operator who last handled
the call

Outgoing trunk identification The outgoing trunk group number representing the
position. If no outgoing trunk is used, then a de-
fault value is used.

Incoming trunk identification The incoming trunk group number representing the
position. If no incoming trunk is used, then a de-
fault value is used.

End

Certain ITOPS billing records have extension records that provide additional
information for call billing. Some calls can have more than one type of
extension record. ITOPS extension records are required for the types of
calls shown in table 9–3.

PLN-5001-001i Standard 02.02 April 1997

 ITOPS 9–41

Table 9–3
ITOPS extension records

Item Description

Special billing Used for calls billed to a number other than the
calling number, such as a third party or calling card
number

Hotels Used for calls billed to a hotel number

Time and charge quotations Required for time and charge quotations

Charge adjustments Used for operator adjustment of calls

Foreign alternate route Used by an ITOPS operator to complete calls or

reach operators in a foreign country when it is not
possible to do so by way of a direct route

Database calls Used when an ITOPS call arrives at an operator

position from the delay call database

ITOPS hardware components

The basic ITOPS system hardware consists of the following:
• DMS-200i or DMS-100i/200i switch
• transmission facilities between ITOPS and DMS
• ITOPS administrative equipment
• ITOPS positions
• hotel billing information center (HOBIC) equipment

Each of these components is discussed in the following pages. Only a brief

overview of these hardware components is provided in this document. For
further details on ITOPS equipment, refer to the ITOPS Planning and
Engineering Guide, 297-2181-155.
ITOPS hardware architecture
The ITOPS hardware architecture and configuration are described in the
following paragraphs. Refer to figure 9–7 on page 9–43 for an illustration
of the ITOPS hardware architecture.
DMS Switch
The DMS can be either a DMS-200i or a DMS-100i/200i switch.
The DMS is composed of the following hardware for the ITOPS system:
• ITOPS trunk – ITOPS trunks are connected to local offices, are
incoming to the DMS-200i switch, and require an operator.

DMS-100 International Technical Specification BCS40i and up

9–42 ITOPS

• Metering (MTR) trunk – MTR trunks connect to other toll switches

within the country or to switches located in other countries. They can be
used for direct dialed or for operator traffic. They carry outgoing or
incoming traffic to the DMS-200i international switch.
• International digital trunk controller (IDTC) – When a local or toll call is
routed to an ITOPS operator position, it is first connected to the
international digital trunk controller (IDTC). The IDTC is a peripheral
module that connects to a PCM30 digital trunk standard from the
network with digital trunk circuits.
• Three-port conference circuit – When a call is routed to an operator
position, the voice channel of that position is connected through the
switching network to one port of a three-port conference circuit mounted
on a maintenance trunk module (MTM). Two other ports are connected
to the calling and the called parties.
• Maintenance trunk module (MTM) – The MTM provides a connection
between the digital network and digital or analog service circuits. The
data channels from both the digital modem and the three-port conference
circuit connect with the MTM.
• Digital modem – The data channels of the ITOPS system devices,
operator positions, and administrative positions are connected through
the switching network to digital modems mounted on the MTM.
Operator input, received in the form of digitized frequency shift keying
(FSK) data, is decoded and reformatted. The data is then routed to the
central controller using the normal DMS-200 signaling path. Conversely,
digital modems convert data received from the central controller to a
digitized FSK format for transmission to and display on the ITOPS crt.
Refer to figure 9–7 for a diagram of ITOPS digital transmission
facilities.
• Central control complex – The central control complex comprises all the
central control functions of the DMS systems. It consists of the NT40 or
SuperNode and their associated components such as the central
processing unit, program store, and data store.

PLN-5001-001i Standard 02.02 April 1997

 ITOPS 9–43

Figure 9–7
ITOPS hardware architecture

Network
Central
control
complex

MTM IDTC

Incoming
2–way
0 1 2 MTR or
Digital ITOPS
3–port trunks
modem conf. cir.
PCM30 (CLG party)
channels
Outgoing
MTR trunk
(CLD party)
Switching office
ITOPS Office

Channel
Notes: bank
One three-port conference circuit 4–wire 4–wire FSK
is alloted for each ITOPS analog voice analog data
position.
One digital modem is alloted for each ITOPS 4–wire FSK
ITOPS position and TTY. position analog data
Channel bank may be located TTY
in either switching or ITOPS offices. Admin. and
HOBIC devices

Transmission facilities
Digital facilities provide communication paths between the ITOPS positions
and the DMS switch. The digital facilities provide a connection between
the 4-wire analog voice and 4-wire analog data circuits of each operator

DMS-100 International Technical Specification BCS40i and up

9–44 ITOPS

position to the DMS by a 30-channel pulse code modulation (PCM)

signaling link.
A channel bank between the ITOPS position and the IDTC links the PCM
with the IDTC. An IDTC at the DMS links the PCM with the DMS
network. Figure 9–7 shows the ITOPS configuration using digital facilities.
ITOPS equipment
This section provides greater detail on the following ITOPS equipment:
• channel bank – The voice and data circuits of the ITOPS position create
analog speech and data. These circuits must be connected to an IDTC.
The IDTC requires a PCM30 digital signal. A channel bank connects the
ITOPS position and the IDTC to convert the analog signals into PCM
signals, and the PCM signals into analog signals.
• operator position – The operator position consists of a keyboard, a crt,
and an ITOPS microprocessor based controller unit. The ITOPS
controller unit processes voice and data signals so that an ITOPS
terminal can communicate with the DMS.
• ITOPS administrative equipment – The ITOPS administrative equipment
provides the ITOPS supervisory staff with the tools for determining
staffing requirements, quality of service, and traffic volume on an
operator or group basis.
• HOBIC equipment – The hotel billing information center (HOBIC) is an
operator-attended location within the operating company or in a
centralized, off-site location. A HOBIC can be part of a single-traffic or
multitraffic office configuration.
Operator position
The ITOPS operator position can be defined by the operating company to
function as any one of the following:
• ITOPS operator position
• ITOPS in-charge position
• ITOPS assistance position

For complete details on the above positions, refer to the ITOPS Operator
Guide, 297-2181-300, and the ITOPS Force Management Guide,
297-2181-310.
ITOPS administrative equipment
ITOPS administration has the following responsibilities:
• controls the number of calls reaching a group of operators
• balances the work load among the traffic offices
• receives information to determine short and long-range staffing needs

PLN-5001-001i Standard 02.02 April 1997

 ITOPS 9–45

• receives statistical measurements to evaluate the performance of each

traffic office as well as the entire work force
The following equipment is used for ITOPS administration:
• assistance position – a crt and keyboard used by the assistance operator.
The assistance position can be reached for help and can monitor and
page operators, place outgoing calls, and perform administrative
searches.
• in-charge position – a crt and keyboard located in the traffic office
(usually near the system administration data system TTY) and used by
the in-charge operator. The in-charge position displays office statistics
and can receive assistance requests, monitor and page operators, place
outgoing calls, and perform administrative searches.
• system administration data system (SADS) TTY – a teletypewriter used
by the in-charge manager to activate and deactivate force management
features and to output information about the system. The SADS TTY has
the combined facilities of the TADS and FADS TTYs that are used in
multitraffic offices.
• SADSHADS TTY – a teletypewriter used in systems that need minimal
hotel billing. It may replace the SADS and HADS TTYs in a
single-traffic office.
• FADSHADS TTY – a teletypewriter used in systems that need minimal
hotel billing. It may replace the FADS and HADS TTYs in a multitraffic
office.
• force administration data system (FADS) TTY – a teletypewriter located
in the force management center that is used to activate and deactivate
force management features and to print information about the system and
the various traffic offices. The FADS TTY manages the system as a
whole. Every 30 minutes (or 15 minutes, if requested), it provides
hard-copy reports of system-wide performance. Summaries are also
provided on a 6-hour and 24-hour basis.
• traffic administration data system (TADS) TTY – a teletypewriter used
in individual traffic offices to activate and deactivate force management
features and to print information on various aspects of the system for
specific traffic offices. There is one TADS TTY for each traffic office.
The TADS TTY provides periodic statistical reports for the same sample
periods as the FADS, but it provides data for only one traffic office. The
TADS TTY gives the traffic office manager control over
operator-controlled traffic call sets and over the assignment of operators
to the study register system.
• force management center – a centralized location staffed with people
who carry out administration tasks for the entire operator work force (not
for individual traffic offices).

DMS-100 International Technical Specification BCS40i and up

9–46 ITOPS

• database administration data system (DADS) TTY – a teletypewriter that

allows for administration of the booked call database. It can print out
portions of the database and also generate reports.
Hotel billing information center equipment
The HOBIC allows the operating company to offer quotations of call details
to hotels for guest-dialed long-distance calls.
ITOPS provides two types of quote services for hotels:
• autoquote - Guest billing information is automatically transmitted to a
receive-only TTY in the hotel that prints the call details for the hotel
staff.
• voicequote - Guest billing information is transmitted to a receive-only
TTY at the operating company site. A voicequote clerk relays the call
details to the hotel staff or calling party.
Table 9–4 lists the TTYs that can be found in a HOBIC.

Table 9–4
Teletypewriters associated with a HOBIC

Teletypewriter Description

Autoquote (AQ) TTY A receive-only TTY at the hotel that provides the AQ
service.

Voicequote (VQ) TTY A receive-only TTY located at the HOBIC that

provides VQ service. This TTY also serves as a
backup if the AQ TTY fails.

Record (REC) TTY A receive-only TTY located at the HOBIC. This TTY
receives a duplicate copy of messages sent to the
AQ and VQ TTYs. It serves as a backup if any AQ
or VQ TTY malfunctions.

Hotel administration data A send/receive TTY located at the HOBIC. The

system (HADS) TTY HADS provides HOBIC personnel administrative
control over the HOBIC system.

The HADS allows HOBIC personnel to perform the following tasks:

• query the status of the AQ, VQ, or REC TTYs
• place AQ, VQ, or REC TTYs out of service
• collect call details from a VQ TTY and transmit them to an AQ TTY if
the AQ TTY is out of service
• transmit call details to an AQ printer for calls processed by a non-ITOPS
system operator, such as a conference operator.

PLN-5001-001i Standard 02.02 April 1997

 ITOPS 9–47

Traffic office configuration

The traffic office can be configured in two ways: as a multitraffic office or
a single-traffic office. The following paragraphs describe the minimum
equipment found in a given office configuration. Table 9–5 lists all of the
possible equipment that can be located in the office. Refer to ITOPS Force
Management Guide, 297-2181-310, for further information on traffic
offices.

Table 9–5
Equipment provisioning for single-traffic and multitraffic offices

SINGLE MULTI EQUIPMENT REQUIREMENT

√ √ operator position 600 per ITOPS host (varies

depending on real-time con-
siderations)

√ √ assistance position 0 to 6 for each office

√ √ in-charge position 1 for each office

√ √ Autoquote (AQ) TTY 1 for each hotel, maximum of

512 for each ITOPS host

√ √ Voicequote (VQ) TTY 2 (includes optional backup

TTY)

√ √ Record (REC) TTY 2 (includes optional backup

TTY)

√ √ HADS TTY 1 for each ITOPS host

√ TADS TTY 1 for each office, maximum of

30 for each ITOPS host

√ FADS TTY 1 for each ITOPS host

√ √ DADS TTY 1 for each ITOPS host

√ SADS TTY 1 for each ITOPS host

√ SADSHADS TTY 1 per ITOPS host

√ FADSHADS TTY 1 per ITOPS host

End

DMS-100 International Technical Specification BCS40i and up

9–48 ITOPS

Equipment found in both multitraffic and single-traffic offices include the

following:
• ITOPS operator position – a cathode-ray tube (crt), keyboard, and
controller unit located in the traffic office and used by the operator to
handle calls.
• assistance position – a crt, keyboard, and controller unit used by the
assistance operator. The assistance position can be reached for help and
can monitor and page operators, place outgoing calls, and perform
administrative searches.
• in-charge position – a crt, keyboard, and controller unit located in the
traffic office (usually near the SADS TTY) and used by the in-charge
operator. The in-charge position displays office statistics and can receive
assistance requests, monitor and page, place outgoing calls, and perform
administrative searches.
• autoquote (AQ) TTY – a teletypewriter located on the premises of a
hotel or attended pay station (APS). As soon as a guest’s call terminates,
all call details are directly transmitted to the AQ TTY. Only one AQ
receive-only TTY per hotel and a maximum of 512 TTYs per ITOPS are
allowed.
• voicequote (VQ) TTY – a teletypewriter located in HOBIC. If there is
no AQ TTY on the premises, then as soon as a guest’s call terminates,
the HOBIC operator telephones the hotel or APS. The operator verbally
quotes the call details, including the billing information. There can be
one or two VQ TTYs in an ITOPS system.
• record (REC) TTY – a receive-only teletypewriter located in the
HOBIC. It receives a duplicate copy of messages sent to AQ and VQ
TTYs and charge-adjust messages sent to the HADS TTY. It also
receives all other charge adjust messages. The TTY alarm messages and
measurements are not duplicated on the REC TTY.
• hotel administration data system (HADS) TTY – a send/receive
teletypewriter located in the hotel billing information center. The HOBIC
operator uses this device to enter ITOPS billing information that is to be
sent to the AQ, VQ, and REC TTY. HOBIC personnel also use it to place
an AQ, VQ, or REC TTY in or out of service. In addition, the HADS
TTY receives TTY service alarm messages, HOBIC operational
measurement information, and hotel charge-adjust (credit) messages
generated by ITOPS operators.
• delay call database administration data system TTY (DADS) – A
teletypewriter located in the force management center used to administer
the delay call database. The DADS TTY prints subsets of the database
contents, prints cancelled delay calls at the time of cancellation, and
prints calls that are mass deleted.

PLN-5001-001i Standard 02.02 April 1997

 ITOPS 9–49

Additional equipment found in a single-traffic office includes the following:

• system administration data system (SADS) TTY – a teletypewriter used
by the in-charge manager to activate and deactivate force management
features and to output information about the system. The SADS TTY has
the combined facilities of the TADS and FADS TTYs that are used in
multitraffic offices.
• SADSHADS TTY – a teletypewriter used in systems that handle
minimal hotel billing. It may replace the SADS and HADS TTYs.
Additional equipment found in a multitraffic office includes the following:
• force administration data system (FADS) TTY – a teletypewriter located
in the force management center that is used to activate and deactivate
force management features and to output information about the system
and the various traffic offices. The FADS TTY manages the system as a
whole. Every 30 minutes (or 15 minutes, if requested), it provides
hard-copy reports of system-wide performance. Summaries are also
provided on a 6-hour and 24-hour basis.
• traffic administration data system (TADS) TTY – a teletypewriter used
in individual traffic offices to activate and deactivate force management
features and to output information on various aspects of the system for
specific traffic offices. There is one TADS TTY per traffic office. The
TADS TTY provides periodic statistical reports for the same sample
periods as the FADS, but it provides data for only one traffic office. The
TADS TTY gives the traffic office manager control over
operator-controlled traffic call sets and over the assignment of operators
to the study register system.
• force management center (FMC) – a centralized location staffed with
people who carry out administration tasks for the entire operator work
force (not for individual traffic offices).
• FADSHADS TTY – a teletypewriter used in systems that need minimal
hotel billing. It may replace the FADS and HADS TTYs in a multitraffic
office.
The in-charge and assistance positions are operator positions that have been
defined in datafill to perform their respective functions.

Additional ITOPS software feature packages

The following software feature packages can be added to the base ITOPS
hardware and software. This section describes these feature packages:
• ITOPS International R2 Interworking - NTXB83
• Fixed Duration Calls - NTXH13
• Estimated Call Charges for ITOPS - NTXH16
• ITOPS – Account Code Access - NTXH54
• ITOPS Intrusion Tones - NTXH71

DMS-100 International Technical Specification BCS40i and up

9–50 ITOPS

ITOPS International R2 Interworking – NTXB83

The International R2 Interworking feature package includes the C1
multifrequency signaling compelled (MFC) metering (MTR) trunk for
countries requiring this type of trunk. It also provides these functions:
• end-to-end signaling over C1 MFC trunk
• proper generation of KOA signal on international calls over MFC
signaling trunks
• a line option of denied toll break-in to ensure subscriber privacy
• digit analysis on dial pulse trunks

Fixed Duration Calls – NTXH13

The Fixed Duration Calls feature allows the operator to specify a fixed
period of time on a call. When the time has expired, the call may be
disconnected or returned to an ITOPS position for further handling. ITOPS
administration defines the types of calls that can have fixed duration applied
to them.
The fixed duration feature is an extension of the notify function offered with
the delay call database feature. The notify function allows the operator to
enter a time for the call specified by the subscriber. The call is returned to
the position after the time elapses. The fixed duration feature extends the
notify function by disconnecting the call without returning to an ITOPS
position when the specified period of time has elapsed. A warning tone is
sounded for the subscriber five seconds before the cutoff.
Estimated Call Charges for ITOPS – NTXH16
The Estimated Call Charges for ITOPS feature allows the ITOPS operator to
estimate call charges for a proposed time specified by a subscriber. The
operator can create call detail information for different origination times,
call durations, and attributes. The subscriber may dial the operator and
request an estimate. The subscriber may also dial a special estimate code
that identifies the call’s origination type to the operator as an estimated call.
When a subscriber requests an estimate, the operator presses a key to put the
operator position in estimate mode. The current details of the call are
displayed on the operator screen. The operator may change call attributes
(coin, hotel, time and charges, database call, attended pay station, person to
person, bill to called party, bill as person call back, calling card bill to third
party) to fit the subscriber’s request. Other details the operator may change
are:
• the cost of a call originating at a time of day other than the current time
• the cost of a call with a different origination type
• the cost of a call with a different length

PLN-5001-001i Standard 02.02 April 1997

 ITOPS 9–51

The operator obtains an estimate, changes call detail information, and

obtains a new estimate as often as required. The operator leaves the estimate
charges mode and retains the call details information on the screen, except
for the changes made to the billing destination. The call may also be stored
as a database call, or the subscriber may be released; in both cases, the
operator can then return to normal call processing.
When the system calculates charge estimates, it takes into account discounts,
time of day, holiday rates, taxes, and the rounding of charges. It does not
reflect account surcharges or discounts the operating company may define in
its setup process.
ITOPS – Account Code Access – NTXH54
The Account Code Access feature allows the operating company to control
toll access to subscriber lines by assigning account codes (authorization
access codes) to each standard residential and business line. The operator is
unable to enter specific call details until a valid account code number is
entered. Lines without the account code are denied toll services. This
feature is useful in countries where automatic toll access must be restricted
because of a lack of available circuits.
A many-to-one mapping of account codes to a subscriber line is provided. A
maximum of ten account codes can be specified and may be necessary when
a subscriber station is accessed by a variety of users. In this way toll access
can be traced to specific individuals.
This feature package provides an optional operator display of account code
information against the calling directory number. The special billing
number and the account code are displayed at the same time.
The operating company also has the option of recording the account code in
AMA. Activation of this option ensures that the account code appears in the
appropriate ITOPS extension record. The access code may be added to an
existing ITOPS extension record, or a new extension record may be created
that is specifically geared for account code verification.
Registered account code users may initiate a call from a directory number
other than the directory number the account code is assigned. The
subscriber must specify the registered directory number and account code
before getting toll resources. Remote directory number access can also be
initiated from any subscriber or business line.

DMS-100 International Technical Specification BCS40i and up

9–52 ITOPS

ITOPS Intrusion Tones – NTXH71

The intrusion tone is a tone applied to the calling and called parties to alert
them that the call has been recalled to the operator and their call is no longer
private. The tone is heard by all three parties involved in the call. The
intrusion tone may be used in these instances:
• coin recall — A calling party completes the paid duration of the call,
and the call is recalled to the ITOPS position.
• notify call — The customer left instructions with the operator to
interrupt the call after a specified time interval elapses.
• permanent hold — A call placed on permanent hold is returned to the
ITOPS position.
• attended pay station fixed duration — The intrusion tone is generated for
an APS call when the call comes back to the operator after a fixed
duration time.
The
When the call comes to the position, the tone is generated continuously until
the call is released from the position or the calling or called party is
disconnected. If the calling or called party is disconnected and the operator
connects one of the parties to form another call, the tone is not generated
until this call leaves the position and is recalled.

PLN-5001-001i Standard 02.02 April 1997

 10–1

Maintenance
This chapter summarizes the maintenance facilities provided on the
DMS-100 International switch. While the majority of the information
provided in this chapter applies to all DMS-100 International applications,
specific maintenance capabilities may vary depending on the market in
which the system is deployed, the application of the system, and the types of
optional hardware and software provisioned.
Maintenance capabilities and procedures for the DMS-100 Family are
documented extensively in Northern Telecom Practices (NTPs). Detailed
descriptive information, subdivided by maintenance subsystem (for
example, lines maintenance or trunks maintenance) is provided in the
following documents:
• Input/Output Devices Maintenance Guide, 297-1001-590
• Networks Maintenance Guide, 297-1001-591
• Peripheral Modules Maintenance Guide, 297-1001-592
• External Devices Maintenance Guide, 297-1001-593
• Lines Maintenance Guide, 297-1001-594
• Trunks Maintenance Guide, 297-1001-595
• DMS SuperNode and DMS SuperNode SE Computing Module
Maintenance Guide, 297-5001-548
• DMS SuperNode and DMS SuperNode SE Message Switch Maintenance
Guide, 297-5001-549
• International Traffic Operator Position System (ITOPS) Maintenance
Guide, 297-2181-524
• Remote Line Concentrating Module/Outside Plant Module Maintenance
Guide, 297-2701-520
Additional maintenance documents can be located by referring to the chapter
“Documentation” in this book, or by consulting the following documents:
• Index to Maintenance Procedures, 297-1001-500, describes all
procedural maintenance documents available for DMS-100 Family
switching systems, including alarm clearing, trouble locating, card
replacement, and routine maintenance procedures.

DMS-100 International Technical Specification BCS40i and up

10–2 Maintenance

• Guide to Northern Telecom Publications, 297-1001-001, describes all

available publications, including maintenance documents.

Maintenance and administration position

The maintenance and administration position (MAP) is the primary interface
between the DMS-100 Family system and operating company personnel for
performance of input/output activities. Tasks performed at the MAP
include:
• general maintenance functions for error detection and diagnosis
• administration functions for network management and customer data
modifications
• testing functions for specific groups of equipment, such as lines or
trunks.
• emergency technical assistance from a remote location.

MAP provisioning
MAPs can be located on site, or connected via modem to a remote site. The
number of MAPs provisioned on a particular system is specified by the
operating company, and depends upon the size and application of the office,
and the types of MAP capabilities required. A minimum of two MAPs are
provisioned on a system. Where required, a larger number of MAPs can be
provisioned, allowing the various input/output functions required to
maintain and administer the system to be divided among different personnel
and performed concurrently.
The maximum number of MAPs which can be provisioned on a system is
limited by the number of available input/output controller (IOC) device
ports available. This capacity, however, is not a practical constraint; any
normal configuration has termination capacity for over 100 MAPs.
Printers are used in conjunction with the MAP for data entry and retrieval,
including customer data modifications, network management and
operational measurement (OM) reports, and log reports.
A dedicated MAP, assigned to position zero in data table TERMDEV, is
identically equipped in all systems. This MAP is commonly referred to as
the operator position. MAP assignments are recorded in protected data store
memory and preserved on office image tapes to ensure these assignments are
not lost in the event of system restarts.

PLN-5001-001i Standard 02.02 April 1997

 Maintenance 10–3

MAP components
The MAP consists of the following components:
• visual display unit (VDU)
• keyboard
• voice communication module
• position furniture
• external test equipment jacks
• printer (or teletype)
• data set (modem) for remote MAP

Figure 10–1 illustrates the Maintenance and Administration Position.

Figure 10–1
Maintenance and administration position

Visual display unit

Voice communication module

Testing facilities area

External
test
equipment
jacks

Position furniture

DMS-100 International Technical Specification BCS40i and up

10–4 Maintenance

Visual display unit with keyboard

The VDU (or MAP display) and its associated keyboard are the primary user
interface for maintenance and administration personnel and a DMS-100
Family system. In the maintenance mode, the MAP display is divided into
the following areas of information, as shown in figure 10–2 on page 10–5.
• system status area Indicates alarm and/or operational status of the
system with immediate automatic updating of
current display.
• work area Displays descending levels of subsystem status,
including working data, for example, frequency
levels applied to and measured on posted trunks.
• command menu Defines functions which can be performed at the
current MAP level.
• CI output area Lists system report output, to include error, action
taken, and diagnostic messages, upon operator
request. Also displays system responses to
commands input by operator.
• input echo area Provides echoed statement of most recent
command string input by operator.
• user ID and time Identifies user and displays time of day.
Using the MAP display and the keyboard, operating company personnel can
examine the system, on increasing levels of detail, using the telescoping
process provided by the MAP maintenance software. Users enter
instructions in the form of commands, using the keyboard. The commands
entered, and the system responses to the commands, appear on the MAP
display. The MAP responses may be requests for further information from
the user or contain the information requested by the user.
To gain access to the DMS-100 Family system via the MAP, the user first
logs onto the system by typing in a user identifier (ID) and a password.
When the system verifies the validity of the ID and password, access is
granted, and the system enters the highest level of the MAP command and
display hierarchy, the command interpreter (CI) level. At the CI level, an
extensive selection of MAP functions can be accessed by command,
including equipment maintenance functions.
Additional MAP access and security features are described on page 10–6.
This chapter focuses on the maintenance capabilities provided by the MAP,
as described on page 10–8. Full details of all available MAP commands
and functions are provided in the following documents:
• Nonmenu Commands Reference Manual, 297-1001-820
• Menu Commands Reference Manual, 297-1001-821

PLN-5001-001i Standard 02.02 April 1997

 Maintenance 10–5

Figure 10–2
MAP display layout

System status area

Command menu
display area Work area

Computer interpreter (CI) output area

User ID
Time

Voice communications module

The voice communications module (VCM) provides a means of
communication with other maintenance personnel to perform functions such
as trunk monitoring and testing. VCMs can consist of:
• telephone sets
• head sets
• hands-free units
• automatic dialers

Test equipment jacks

Four, 4-wire jack appearances are provided at the MAP when it is used as a
line or trunk test position. One jack is used for operating company
determined purposes, such as connecting to a VF patch bay. The others
connect to jack-ended trunks through which access is gained, via the
switching network, to any line or trunk in the office. Portable test
equipment is plugged into these jacks to perform various tests.
Two communication trunks, used to originate calls, are associated with every
MAP used for trunk testing. The T101 test lines are terminating type trunks,
connected in parallel to every MAP used for trunk testing. Communication

DMS-100 International Technical Specification BCS40i and up

10–6 Maintenance

trunks, 101 test lines, local talk lines and communications lines terminate at
the voice communication module. Jack-ended trunks are hard wired directly
to the jacks located on the position furniture. Each trunk is associated with
two jacks, one for the transmit side and one for the receive side.
Refer to page 10–28 for additional information on test lines.
Printer
A printer can be provisioned with the MAP to provide a permanent copy of
output reports or copy stored on disk, tape or alternate MAPs. The VDU
and printer accept and display upper or lower case characters. Multiple
printers can be provisioned on the system.
Teletypewriters
Teletypewriters (TTYs) can be used in DMS-100 Family systems for data
entry and retrieval, and can be located on site or at a remote location. TTYs
are used to implement trunk and line work orders and network management
controls, initiate diagnostics, and receive log messages, OM reports, and
network management reports. TTY reports include report number, time,
report trouble, and related data.
Furniture
The optional MAP furniture is a modular system providing table surfaces
which are positioned for either standing or sitting use. The furniture,
consisting of tables and shelf units, is assembled in various configurations to
provide work space and documentation storage for administrative or
maintenance functions, and to mount the VDU, jack field, and
communications module.
MAP interface to the DMS-100 Family system
Each MAP is connected to the system via a device controller card located in
the input/output controller (IOC) shelf, which resides in the input/output
equipment (IOE) frame. Up to four MAPs can be connected to a single
device controller.
MAP access and security features
The DMS-100 Family system offers the following capabilities on an
optional basis:
• automatic dial-back
• command screening
• password control
• access control
• audit trail
• automatic logout of dial-up lines.

PLN-5001-001i Standard 02.02 April 1997

 Maintenance 10–7

Automatic dial-back
With automatic dial-back, the user dials and logs in with the prescribed user
ID, password, and terminal number. This number is an automatic dial-back
ID which may be a valid telephone number of up to ten digits or a
predefined index number. In either case, the automatic dial-back identifiers
are listed in data table DIALBACK. After the number is input by the user,
the line is disconnected and the table is referenced to validate the terminal
number. If valid, automatic dial-back is made to the telephone number
assigned to the terminal ID. If the login attempt is invalid, it is recorded in
an audit file.
Command screening
The command screening feature allows the system to do extensive screening
of user commands prior to execution. Command screening can be applied to
any user, terminal, or both. DMS-100 Family system users and terminals are
assigned single or multiple privilege command classes from 0–31, for
depending on the functions of the user or terminal. To ensure system
security, all commands will initially default to an operating company defined
class until privilege classes are assigned.
Password control
The optional password control feature disables all automatic logon
procedures for the DMS-100 Family system and secures the system against
unauthorized users. Users and passwords must be identified to the system
prior to logging in. No user is able to display or change the password of
another. Passwords are encoded and scrambled, however, the decoding
algorithm does not reside in the system. The operating company selects the
parameters for the number of characters in each password and determines
the effective time interval before a password must be changed by the user.
Password expiration warnings and a predesignated number of logon attempts
before permanent lockout from the system are included in this feature. As
an added security measure, the system prompts the user for the current
password when a password change is attempted.
Access control
This feature allows control of user access to a DMS-100 Family system by
controlling login access to consoles. Consoles can selectively enable or
disable logins. These consoles can be automatically disabled on login
failure when a time limit is set for logon sequence completion. A time limit
specifying the maximum time an enabled console may be left unused can
also be set, and various access and security related events are logged. The
login sequence is made more secure by erasing the password display from
the VDU screen immediately after entry.
Access to customer data tables is controlled by the privilege class assigned
to each table. When the user attempts to access a table, the user’s privilege
class is compared to the privilege class of the table. If privilege classes

DMS-100 International Technical Specification BCS40i and up

10–8 Maintenance

match, access to the table is granted. Authorized operating company

personnel can monitor both the user and the tables being accessed. When
this feature is activated, all attempts to access a table are recorded in a log
report. This feature is activated or deactivated on a per table basis by
authorized personnel.
Audit trail
This feature provides control of user access and traces illegal entry attempts
through the creation of an audit file of the following activities:
• valid user logins and logouts
• invalid login attempts, for example, wrong or expired password or user
ID
• forceout of users
• change of password
• addition of a userid using PERMIT, where userid is identified
• deletion of userid using UNPERMIT; where user must know password
for user ID
• use of the PRIVCLAS command to change command sets
• privilege violation on table access
• valid use of selected commands
• privilege violation of selected commands.

The system can store up to 1000 security reports, which can only be
accessed via authorized operating company personnel. In addition, the
operating company can specify alarm levels to flag these reports.
Automatic logout of dial-up lines
Automatic logout of dial-up lines allows users to be automatically logged
out. The connection is dropped when a facility open condition is detected.
Optionally, the terminal may be disconnected.

System maintenance using the MAP

Once logged on, maintenance personnel can access the MAP maintenance
(MTC) subsystem by entering the appropriate command. The system
responds by displaying system status information and the MTC level
command set. Figure 10–3 illustrates an example of the MTC level MAP
display for a SuperNode-based system.

PLN-5001-001i Standard 02.02 April 1997

 Maintenance 10–9

Figure 10–3
MTC level MAP display example

CM MS IOD Net PM CCS Lns Trks Ext APPL

. . . . . . . . . .
MTC MTC
0 Quit System status information
2 Activity
3 MTCNA
4 MTrsys
5 Bert
6 Cpstatus
7 MTC level commands
8
9 CM
10 MS
11 IOD
12 NET
13 PM
14 CCS
15 Lns
16 Trks
17 Ext
18 Appl

TIME 14 : 40 >

MTC level system status information

The system status information area shows the overall condition of the
switching system, by major functional subsystem. For example, the overall
status of the computing module (CM) subsystem appears beneath the header
“CM” in the system status information area. The system status area for each
subsystem is a two-line, six character information field which either
indicates the status of fully operational – no faults (ok), indicated by a dot
(.), or an alarm indicating a problem within the subsystem. The second line
of the information field provides alarm category information indicating the
severity of the fault as minor, major, or critical.

DMS-100 International Technical Specification BCS40i and up

10–10 Maintenance

The MTC level system status information area is commonly referred to as

the “alarm banner”. The following illustration shows an example of the
alarm banner in which a fault exists in the message switch (MS) subsystem.
The line immediately beneath the MS header is “SysB”, an abbreviation of
system-busy, indicating that one message switch has been automatically
removed from service by the system due to faults. The alarm category is
“M”, or major. All other subsystems are in normal operation condition
without faults.

CM MS IOD Net PM CCS Lns Trks Ext APPL

. SysB . . . . . . . .
M

The alarm banner is displayed at all sublevels of the MTC subsystem, and is
updated continuously. In cases where multiple alarm conditions exist in the
same functional area (for example, two CM alarms), the most severe alarm
is displayed. When the most severe fault is cleared, the next most severe
alarm is displayed. When all alarms are cleared, the status field returns to a
dot, indicating no faults within the subsystem. Additional information on
the DMS alarm system is provided on page 10–18.
The abbreviated maintenance subsystem names used in the MTC level alarm
banner correspond to the following functional areas of the switch:
• NT40-based systems:
— CC central control
— CMC central message controller
— IOD input/output devices
— Net network
— PM peripheral modules
— CCS common channel signaling
— Lns lines
— Trks trunks
— Ext external devices
• SuperNode-based systems:
— CM computing module
— MS message switch
— IOD input/output devices
— Net network
— PM peripheral modules
— CCS common channel signaling

PLN-5001-001i Standard 02.02 April 1997

 Maintenance 10–11

— Lns lines
— Trks trunks
— Ext external alarms
— Appl applications
Detailed procedural maintenance manuals are provided by Northern
Telecom to clear all alarms which can possibly appear in the alarm banner.
MTC level MAP commands
The MTC level command set (shown along the left side of figure 10–3)
provides command access to major architectural areas within the switching
system; for example, command 12, “NET”, accesses the MAP maintenance
sublevel for the switching network subsystem. The MTC level command set
or “menu” also provides access to specific maintenance functions; for
example, command 5 “Bert” accesses the bit error rate test utility.
Two types of commands are available at the MAP MTC level and its
sublevels: menu commands, as described above, appear on the display.
Additional commands are available at the MTC level and its sublevels which
do not appear on the display, referred to as “non-menu” commands. In both
cases, online help is available to explain the usage of each command, and its
syntax. Non-menu commands available for the MTC level, or any of its
sublevels, can be determined by listing the software directory associated
with that level.
Full details of all available MAP commands, functions, and system
responses are provided in the following documents:
• Nonmenu Commands Reference Manual, 297-1001-820
• Menu Commands Reference Manual, 297-1001-821

MTC sublevels
To facilitate the isolation of faults in the DMS-100 Family system, the MAP
has a telescoping feature. Telescoping is the following of a branching
process to determine the smallest replaceable unit which should be changed
to restore system status to normal. The status data at any telescoping level
being displayed is continuously updated to reflect the current status without
the need to request an update. Supplementary data, within a particular level
or a lower level, is requested for displays by entering the appropriate
commands.
Each maintenance (MTC) sublevel provides a command and status display
increment to the base MTC level, consisting of more detailed status
information pertaining to its associated function, and a specific command set
tailored to maintenance aspects of the subsystem. For example, figure 10–4
shows an example of the MAP display which results by telescoping from the
MTC level to the NET sublevel.

DMS-100 International Technical Specification BCS40i and up

10–12 Maintenance

Figure 10–4
Network level display example

CM MS IOD Net PM CCS Lns Trks Ext APPL

. . . . . . . . . .
NET NET 11111 11111 22222 22222
0 Quit Plane 01234 56789 01234 56789 01234 56789 01
2 0 ..
3 ..
4 Recover 1
5 Loc
6 Tst NET level status information
7 Bsy_
8 RTS_
9 Offl_
10 NET level commands
11 Disp_
12 QTst_
13 Integ
14 Path
15 XPts_
16 Trnsl_
17 Links_
18 Jctrs_

TIME 14 : 40 >

Depending on the MTC subsystem accessed, a number of parallel or

supporting sublevels may be provided. Each supporting sublevel provides a
customized command menu for performing functions associated with the
system element(s) accessed, and adds more detailed status information to the
display. This telescoping process allows rapid fault isolation by providing
an orderly path through the architectural hierarchy, from the system-level
view provided at the MTC level, to the affected switch subsystem (for
example, NET), to the affected equipment shelf, and finally to the individual
circuit card.
Alarms
Audible and visual alarms are provided in the system to alert maintenance
personnel of trouble conditions. Faults are classified according to the
severity of the problem. Alarm categories include critical, major, or minor
alarms.
Whenever a failure is detected in a DMS-100 Family system, system status
information displayed on the MAP display is updated immediately to
indicate the fault. In addition, an alarm status indication is displayed below
the system status information. All critical and major alarms are indicated by

PLN-5001-001i Standard 02.02 April 1997

 Maintenance 10–13

an audible alarm and the appearance of the alarm status indication, *C* for
critical and M for major. Audible alarms can be silenced through the
command SIL input at the keyboard. A blank space below a system status
fault indication denotes a minor alarm. Dead-system alarms cannot be
silenced by software command, only by operation of the audible alarm reset
switch. Additional information on the DMS alarm system is provided on
page 10–18.
Isolation of faults
To initiate tests from the MAP, the appropriate subsystem menus have to be
accessed. Tests on trunks, analog or digital, and service circuits are initiated
after the appropriate circuits have been posted at the trunk test position
(TTP) level. Tests on lines are performed after the line has been posted at
the line test position (LTP) level. Tests on the central control complex and
the networks are initiated after requesting the diagnostics be run on the
appropriate equipment.
When any unit is removed from service, the LOG system is updated to
reflect this change. For example, if a trunk is made busy and removed from
service, the trunk log subsystem will be updated and an output message
provided at the TTP or printer assigned to the LOG system.
Log report system
The MAP units are software driven from the DMS-100 Family system.
Included in the software is a log report (LOG) system, which provides
information storage and retrieval for system-related messages or reports.
During operation, reports are generated by the DMS-100 Family system
software and sent to the LOG system.
In the LOG system, these reports are categorized into a number of report
classes according to the subsystem which generated the report. The LOG
system stores these reports in several LOG buffers. There is one LOG
buffer for each subsystem. Each subsystem has a number of basic report
types associated with it. Each output report is associated with a given report
type and consists of a fixed format and variable data.
Optionally, on the basis of information stored in the LOG system, the reports
are routed to MAPs or other output devices associated with specified classes
of users. These output messages have a sequence number which can be
printed in the order of alarm severity, critical, major, minor.
For more information on the DMS-100 Family log report system, refer to the
Log Report Reference Manual, 297-1001-840.

DMS-100 International Technical Specification BCS40i and up

10–14 Maintenance

DMS-100 Family system maintenance

Maintenance capabilities
The DMS-100 Family maintenance system provides the following:
• hardware fault detection capabilities
• diagnostic programs which identify and isolate faulty hardware units
• a software defensive programming strategy augmented with audit
capabilities
• alarm and MAP facilities for communication with the maintenance staff

These components are specifically structured and imbedded within the

DMS-100 Family system design. Enumeration of all the capabilities
available through the maintenance system is not possible without a full and
detailed analysis of this design. A complete listing of externally observable
maintenance actions, together with the system responses, is available for
maintenance operations guidance, through the Northern Telecom Practices
(NTPs) in the –500 Series, for example, Guide to Maintenance Procedures,
297-1001-500. In addition to these documents, a maintenance and
administration manual is available from Northern Telecom, detailing
focused maintenance operations designed for use in a central maintenance
center. Various software packages also are available to aid in central
maintenance operations, for example, focused maintenance and SPMS.
Overview of maintenance actions
The MAP is the focal point of DMS-100 Family system maintenance. In
most cases, trouble or faults within the system are automatically detected by
internal facilities and an appropriate report filed in the LOG system.
Audible alarms are activated if appropriate. The LOG messages associated
with CO alarms will have a priority-of-action flag associated with them,
consistent with the urgency of the alarm. It is intended that major alarm
messages indicate trouble conditions in the CO which require resolution by a
craftsperson.
The maintenance mode of the MAP provides a number of displays or levels.
Each level presents detail, in increasing depth, on certain hardware and
offers a menu of commands. Access to each level is arranged in the same
hierarchy as the system hardware.
The first level provides the overall status of each major subsystem. Each
successive level provides greater detail and commands which enable the
operator to telescope into the system. When the level of the fault is reached,
maintenance personnel are alerted by a series of status displays.
Throughout the maintenance mode, the status of each subsystem is displayed
at the top of the MAP screen. Whenever the system detects a failure, the
status display changes to identify the failed subsystem and to show the
severity of the failure. To obtain more information about the fault, the

PLN-5001-001i Standard 02.02 April 1997

 Maintenance 10–15

maintenance personnel change levels by entering a command corresponding

to the failed subsystem. Depending on the subsystem entered, the display
may immediately identify the faulty unit, or a detailed level may be entered
to identify the exact location. Diagnostics may then be run to pinpoint the
failure and corrective action taken.
In general, trouble verification will be done by the maintenance staff by
causing the appropriate system diagnostic to be run via a MAP input
command. The diagnostic output will indicate any printed circuit pack
(PCP) replacement required for repair of the trouble. For normal testing and
verification on DMS-100 Family system equipment, two-person tests are not
required. After repair, the diagnostic should be run again and, if the run is
successful, a MAP input command can be issued to restore the unit to
service.
Real-time activity indicator
Real-time activity software is an online real-time indicator tool which allows
operating companies to monitor a system’s traffic count, CPU occupancy,
and call queuing time. This monitoring tool is invoked by entering the
ACTIVITY command at the maintenance (MTC) level of the MAP. The
resulting MAP display provides a series of measurements, including call
attempt pegs, CPU occupancies, and processing queues. The system logs
can be activated to provide 15 one minute snapshots of percentage of
completions, CPU occupancy, and average queue delays. Associated menu
commands are used to control the start/stop of both the visual monitoring
and the activity logs.
Circuit selection procedures
Selection algorithms for circuit groups, such as trunk groups, can be
specified by the operating company:
• Most Idle Trunks are added to the tail of the queue as they become
idle.
• Least Idle Trunks are added to the head of the queue as they become
idle.
• Sequential Trunks are selected from those idle in the sequence
specified in translation.
• Circular The trunk selected is the first idle trunk found in a search
starting after the most recently released trunk in a trunk
group.
Sanity tests
Sanity tests are provided in the DMS-100 Family system to ensure the
integrity of the system software. The self-checking logic of the maintenance
system uses four timers, one of which is the sanity timer. This timer runs
continuously in both CPUs and is reset by the operating system. Failure to
reset will cause the timer to fire, which causes a TRAP interrupt and, at the

DMS-100 International Technical Specification BCS40i and up

10–16 Maintenance

same time, enables the Activity Switch Timer (AST). If, for some reason,
the TRAP is not served, the AST will fire and an activity switch will occur.
The sanity timer guards against software or micro-program loop errors not
detected by the TRAP system.
Calls encountering trouble
The objective of the DMS-100 Family system recovery system is to
minimize service interruption. Calls encountering trouble are handled in
two ways:
• Calls are attempted to be completed satisfactorily without the customer
being made aware that a trouble exists. For example, when problems
occur during path setup through the switching network, a retry is
attempted without customer knowledge.
• Calls that cannot be completed due to internal or external trouble
conditions are routed to operating company-defined treatments such as
tones, for example, 120 IPM or recorded announcements.
Safeguards
The DMS-100 Family system provides safeguards, daily scheduled CPU
changeovers, routine diagnostics, per-call tests, and other background tests,
where trouble conditions within the service recovery and protection facilities
can be detected before service is affected.
Further safeguards are provided to prevent an inadvertent degradation of
service due to improper data commands or actions. Any data changes
implemented in the system are checked for validity and format and tested.
In addition, the system provides input terminal restrictions which can restrict
data changes to be implemented through the appropriate terminals.
Through MAP commands, units of the system may be removed from
service. For duplicated units, that is, CPUs, CMCs, and networks, if one of
the duplicated units is already busied out or inactive, and a command is
input to busy or make the mate unit inactive, the system will provide a
warning message and no action is taken to busy the unit. In the case of
unduplicated units, such as the MTM, the system provides warning
messages if circuits are service busy, and requires command validation
before the unit is removed from service.
The DMS-100 System safeguards are provided to ensure that when a
number of trunks in a trunk group are busied out either by the system or
maintenance personnel, alarm conditions are provided on the MAP. Alarm
conditions are classified as critical, major, and minor, dependent on the
percentage of trunks busied in a trunk group. Once the percentage threshold
is exceeded, the appropriate alarm is triggered for the affected trunk group.
The threshold percentage information, from 0–100%, is defined by the OC
in Common Language Location Identifier (CLLI) maintenance tables for all
trunk groups.

PLN-5001-001i Standard 02.02 April 1997

 Maintenance 10–17

The Automatic Trunk Testing (ATT) feature provides a safeguard to ensure

that optionally no more than 25 or 50% of the trunks in a trunk group are
removed from service if a failure condition is encountered. The Automatic
Line Testing (ALT) feature provides a means for testing lines or groups of
lines automatically on a scheduled basis. Lines failing any of the tests are
not removed from service, but may be posted at the line test position for
further action. If the number of line test failures exceed operating company
defined thresholds, appropriate alarms will be generated. Separate
thresholds may be set for diagnostic failures and permanent signal lockout.
Most of the circuit packs in the system use a key and slot arrangement which
ensures that circuit cards are installed in the proper shelf position.
DMS-100 family diagnostic system
The DMS-100 Family system includes diagnostic programs for fault
verification and resolution for all DMS-100 Family system equipment. The
diagnostic programs are activated automatically by the system, or manually
by maintenance personnel using the MAP. Diagnostic test results are
provided visually at the MAP, and also recorded in operational
measurements (OMs) and log reports.
The DMS-100 Family diagnostic system handles detectable trouble
conditions in two ways. Trouble conditions which are theoretically
repeatable, such as circuit card failures, are categorized as faults. Depending
on the severity of the fault and the type of hardware, faulty hardware is
either automatically removed from service by the system, or can be
manually removed from service by maintenance personnel. When the faulty
unit has been isolated and replaced, diagnostics can be manually repeated to
verify the integrity of the replacement hardware, followed by returning the
hardware to service.
One-time or random-occurrence trouble conditions are categorized as errors.
Typical software errors are referred to as SWERRs. In the DMS-100 Family
system, equipment experiencing correctable errors is not automatically
removed from service unless an excessive error rate is occurring.
Diagnostic output data identifies the faulty hardware by product equipment
code (PEC) and its physical location. When diagnostic programs cannot
isolate the trouble to a single circuit card, a list is generated which indicates
circuit cards in the order of probability for causing the trouble.
Babbler diagnostic
The major babbler diagnostic failure flag provides an indication of devices
which send interrupt messages to the central control subsystem at an
excessively high rate. The DMS-100 Family system provides for detection
and handling of babbling nodes. A counter and three threshold levels are
maintained for the failure type, and an alarm condition occurs when one or
more of the failure counters exceeds one of the threshold levels. Detection

DMS-100 International Technical Specification BCS40i and up

10–18 Maintenance

software includes the ability to take babbling nodes out of service as they
occur.
Babbler line handler The babbling line handler software package can
diagnose the line card and loop of a line that has been reported as a babbling
line in the peripheral. The line card will be removed from service, and
placed in the cut state to prevent system degradation. An audit will revisit
each babbling line and return it to service if babbling has ceased.

System alarms
The DMS-100 Family alarm system performs three functions:
• generates audible and visual indications as a result of trouble conditions
detected within the system, or in associated equipment
• provides a hardware-generated dead system alarm to alert maintenance
personnel when the DMS-100 Family system software is not functioning
• provides manual facilities for alarm conditions, including:
— silencing audible alarms
— transferring alarms to a remote monitoring location
— grouping the alarms of the DMS-100 Family system with other
systems
— transferring alarms from an unattended trunk or line test center to the
main system.
There are normally two NT3X82 dead system alarm packs in the office.
These alarms are wired to ensure any loss of communication between both
of these packs and the CPU is required to generate the dead system alarm.
Here the DS relays on both packs, normally held by software, are released,
thus generating an audible and visual critical alarm, indicating a dead
system. The signals usually are cross-connected at the distribution frame
(DF) and can be picked up by engineered telemetry equipment.
In addition, there is an NT3X84 alarm sending circuit pack in the office.
When the DS relays in the NT3X82 packs are released, a ground is extended
to the DS relay on the alarm-sending pack which causes it to operate. This
action starts the dead system tone generator, 480 Hz, and activates a logic
circuit which will select and seize an idle E&M trunk from two regular
operator trunks. These trunks and the pack interface are cross-connected at
the DF. The 480-Hz tone is then connected to the seized trunk. If neither
trunk is idle Trunk 1 is automatically seized, the tone is connected to it and
the M lead is pulsed at 60 IPM. Switches in the trunk selector logic circuit
can be set to accommodate either Type I or Type II E&M signaling.
Alarm system operation
Alarm and control inputs detected by the alarm system hardware are
interfaced with the alarm system software through scan points. These scan

PLN-5001-001i Standard 02.02 April 1997

 Maintenance 10–19

points detect inputs generated by hard wired alarm contacts in the DMS-100
Family system hardware, by the operation of manual control switches, or by
the alarm circuits of miscellaneous equipment associated with the DMS-100
Family system.
Alarm and control inputs are generated by the software of the other nine
maintenance subsystems which complete the DMS-100 Family maintenance
system are designated system inputs. Each maintenance subsystem controls
its own alarm status display in the system status area of the VDU at the
MAP. The alarm system software checks for changes in the alarm status of
these subsystems every five seconds and updates the audible and visual
alarm indications accordingly. This software responds to alarm or control
inputs by operating or releasing appropriate Signal Distribution (SD) points
in alarm system hardware and to initiate or terminate the corresponding
audible and visual alarm, or control function.
Alarm classes
Trouble conditions are assigned to an alarm class by the maintenance
subsystem which detects the trouble. The alarm classes, in decreasing order
of severity, are critical, major, and minor. Critical alarms are reported within
two seconds of occurrence. Major alarms are reported within 30 seconds of
occurrence. Minor alarm trouble notification is reported within two minutes
of the occurrence of the trouble. All alarms displayed at the MAP are
entered in the LOG system and output reports routed to the appropriate
printers.
Audible alarms
Audible alarms are activated either on-site or transferred by the remote
alarm transfer circuit to a remote monitoring location. On-site audible
signaling devices are mounted on two different audible alarm panels, the
main audible alarm panel and an optional audible alarm panel, for the Trunk
Test Center (TTC) and/or the Line Test Center (LTC).
Up to two main audible alarm panels may be supplied per office depending
on office size and configuration. For example, an additional audible alarm
panel for the power plant if located on another floor. The audible alarm
panels may be either wall or column mounted.
The main audible alarm panel provides the signaling devices. The TTC
audible alarm panel also provides a TTC chime which signals an incoming
call on a 101 communication test line.
• Critical Bell Loud bell which can signal dead system
alarm, critical system equipment failure,
critical power plant failure, or critical
system or power plant failure in another
system if alarm grouping is in effect.

DMS-100 International Technical Specification BCS40i and up

10–20 Maintenance

• Major Chime Loud tone bar struck at 60 ipm which

signals a major system failure, major
power plant failure, frame supervisory
panel alarm on any equipment aisle, or
major equipment failure in another system
if alarm grouping is in effect.
• Alarm Battery Subset Loud telephone ringer, two bells with
resonators, which signals four major
alarms:
• Alarm battery supply failure at a Power
Distribution Center (PDC)
• Battery failure at the Office Alarm Unit
(OAU) or the associated MTM
• Failure of an internal supply circuit at
the OAU or MTM (+130V supply or
20-Hz ac ringing supply)
• Loss of communication between the
central control and the OAU or MTM.
• Minor Alarm Subset Loud telephone ringer, two bells without
resonators, which signals a minor system
equipment failure, minor power plant
failure, minor equipment failure in another
system if alarm grouping is in effect, or an
incoming call on a 101 communication test
line at the TTC if night alarm transfer is in
effect.
Alarm control and display panel
The Alarm Control and Display panel (ACD) is located at the MAP for
operational convenience. Mounted on the ACD are lamps which display the
type and class of alarms and switches which provide manual control of
alarm system facilities. Table 10–1 illustrates ACD alarm conditions.
Alarm display panel
The alarm display panel is a multiple of the ACD which has all of the
manual control switches removed except for the audible alarm reset switch.
The functions of the lamps and the single switch on the alarm display panel
are the same as those on the ACD. A maximum of two panels can be
provided. The alarm display panel can be placed within the same building in
a remote location. On a per-job basis, a purchased telemetry unit, such as
Datalok No. 9, may be used to remote the alarm display panel functions to
other buildings.

PLN-5001-001i Standard 02.02 April 1997

 Maintenance 10–21

Exit alarm panel

An exit alarm panel is located near the main exit door of each DMS-100
Family system floor in a multi-floored office. A maximum of four exit
alarm panels multiplied together can be provided per DMS-100 Family
system. These panels direct maintenance personnel to the area or floor of the
office where an alarm condition has been detected. They also provide
remote controls for the night alarm transfer and alarm grouping circuits.
Equipment aisle visual alarms
Each equipment aisle in the DMS-100 Family system is equipped with end
aisle pilot lamps which light to red if a fault is detected by any Frame
Supervisory Panel (FSP) in the aisle. Each FSP in the aisle is equipped with
a frame fail lamp which lights to indicate which frame in the aisle generated
the alarm.
Dead system alarm
The dead system alarm is generated by alarm system hardware to indicate a
loss of call processing ability in the DMS-100 Family system. When a dead
system condition occurs, the dead system alarm hardware alerts operating
company personnel by sounding the critical alarm bell and lighting the
critical system lamp on the ACD.
No call processing alarm
This feature provides a more sensitive dead system alarm. The regular dead
system alarm causes messages to be sent to the Office Alarm Unit (OAU).
The OAU recognizes when these messages are absent and raises a critical
alarm whenever messages are lost.
The enhanced dead system alarm is similar to the regular version except that
the OAU makes calls into the CC. These call attempts are made every five
seconds and, if after twenty seconds the CC has not answered, the OAU
raises a critical alarm. The CC also counts the number of calls made and, if
no calls are noticed in twenty seconds, the CC raises a critical alarm in the
EXT level of the MAP.

Table 10–1
ACD alarm conditions
Designation Device Function

Critical System Lamp (red) Signals a critical system failure

Major System Lamp (amber) Signals a major system failure
Minor System Lamp (white) Signals a minor system failure
—continued—

DMS-100 International Technical Specification BCS40i and up

10–22 Maintenance

Table 10–1
ACD alarm conditions
Designation Device Function

Major Other Lamp (yellow) Signals a critical or major alarm in

System another system
Minor Other Lamp (green) Signals a minor alarm in another area
System
Power Dist Lamp (red) Signals an alarm battery supply failure
Center ABS at a PDC
Office Alarm Unit Lamp (amber) Signals an alarm system hardware
failure
Critical Power Lamp (red) Signals a critical DMS power plant
Plant failure
Major Power Lamp (amber) Signals a major DMS power plant
Plant failure
Minor Power Lamp (white) Signals a minor DMS power plant
Plant failure
Power Dist Lamp (amber) Signals an office battery supply failure
Center at a PDC
Night Alarm Switch (locking) Initiates TTC Night Alarm Transfer
Transfer
Lamp (white) Signals TTC Night Alarm Transfer is in
effect
Alarm Grouping Switch (locking) Initiates Alarm Grouping
Lamp (white) Signals Alarm Grouping is in effect
Alarm Transfer Switch Initiates or cancels Remote Alarm
(non-locking) Transfer
Lamp (white) Signals Remote Alarm Transfer is in
effect
Audible Alarm Switch Silences audible alarms
Reset (non-locking)
Lamp Test Switch Momentarily lights all lamps on the
(non-locking) ACD and on any
ACD multiples
End

Audible alarm reset

The audible alarm reset switch on the ACD provides a hardware facility for
silencing audible alarms. Audible alarms can be silenced by the SIL
command, input at the MAP console, or by the momentary operation of the

PLN-5001-001i Standard 02.02 April 1997

 Maintenance 10–23

non-locking audible alarm reset switch at the ACD. The dead system
audible alarm cannot be silenced by software command.
Trunk test center alarms
The Trunk Test Center (TTC) is the area of a DMS-100 Family system
where Trunk Test Positions (TTPs) are located. The alarm system software
detects the trunk group alarm conditions, and initiates the corresponding
audible and visual alarms.
There are two alarm conditions specifically associated with the TTC; an
incoming call on a 101 communication test line and a trunk group
out-of-service alarm. Audible signaling devices for these alarms are
mounted on the TTC audible alarm panel. An incoming 101 call sounds the
TTC chime. The trunk group alarm is a system alarm detected by the
software of the trunk maintenance subsystem. Depending on the number of
trunks out of service, for example, system busy and manual busy, within one
trunk group, a minor, major, or a critical system alarm is generated.
TTC night alarm transfer
When the TTC area is unattended, the night alarm transfer circuit provides
the facility to transfer the TTC alarms to the main office alarm system. With
night alarm transfer in effect, incoming calls to 101 test lines at the TTP
generate a minor system alarm instead of sounding the TTC chime.
Line test center alarms
The Line Test Center (LTC) is the area of a DMS-100 Family system where
line test positions are located. Alarms will be generated when the quantity
of line failures reaches or exceeds the operating company-defined threshold
value.
The threshold for each type may be set independently. The alarm class
displayed will be the more severe one of the two types. For alarm purposes
two fault types, diagnostic failures and permanent signal partial dial
conditions, are used. Diagnostic failures indicate that a line has failed a
manual short or extended diagnostic test, an automatic short or extended
diagnostic test, or a system-invoked extended diagnostic test occurs.
Remote alarm transfer
The remote alarm transfer circuit allows the transfer of major and minor
alarm indications, for the system and its power plant, to a remote
alarm-receiving circuit in a distant office. This permits the local office to be
unattended. Since the remote alarm-receiving circuit monitors only major
and minor alarm classes, critical alarms are transferred to the remote
location as majors. If alarm grouping is in effect, alarms originating on
preceding and succeeding floors are also transferred to the remote location.
The transfer circuit communicates with the remote alarm-receiving circuit in

DMS-100 International Technical Specification BCS40i and up

10–24 Maintenance

the distant office over two leads using either –130V or +130V supplies for
signaling.
Alarm grouping
The alarm grouping circuit provides the capability to group alarms
originating in the DMS-100 Family system with those originating on
preceding (lower) and succeeding (upper) floors which have compatible
office alarm systems.
Alarm circuit power detection
In the DMS-100 Family system, loss of alarm circuitry power is detected.
The office alarm system contains alarm circuits to indicate a failure in the
supply that powers the alarm circuits themselves. A failure in the fuses that
supply the alarm circuits causes an audible alarm to be sounded.
External alarms
The external alarm maintenance subsystem monitors the alarm circuits of
any equipment outside the DMS-100 Family system, such as, door alarms,
fire alarms, and other miscellaneous building alarms, through the operation
of DMS Scan Points (SC).
Operating company defined alarm capabilities
The DMS-100 Family systems can accommodate up to 7,168 operating
company assignable scan points. The Signal Distributor (SDs) points are
only limited by the number of MTMs that can be added to a DMS office.
Software facilities are available to permit very flexible operating company
designed logic arrangements between the SCs and SDs. Detection of an SC
change of state can cause multiple SD operations. Multiple SCs can control
a single SD. The operating company designed logic is defined via the MAP
using the alarm scan table and the alarm signal distributor table.
Alarm sending and checking system
The Alarm Sending and Checking System (ASCS) is a software feature
compatible with the DMS-100 Family system office alarm system. When
activated, the feature provides a facility for sending an indication of an
alarm condition occurring in the DMS office over a trunk to a remote
operator position. If the receiving operator is at a Traffic Operator Position
System (TOPS) position, an ANI-8 information digit, spilled over the trunk,
is translated to an alarm indication on the video screen. The operator uses
the TOPS facility to access further information. When the trunk termination
is a regular operator position, upon answer of the call a tone is generated
across the trunk indicating that the originating office has encountered an
alarm condition. The operator then dials a DN allocated to the ASCS
checking facility, and hears a specific tone from the office indicating the
severity of the alarm condition. The tones and directory numbers used for

PLN-5001-001i Standard 02.02 April 1997

 Maintenance 10–25

ASCS, as well as certain parameters associated with the feature, are

operating company assigned. Typical tone assignment is as follows:
Tone Meaning
Continuous high tone Initially received by the operator indicating
low tone, or ringback tone, the existence of an alarm condition in the
originating office.
When the appropriate ASCS DN is dialed, the class of the alarm is indicated
by the tone control received:
Tone Meaning
No tone CRITICAL alarm
Busy tone MAJOR alarm
Code 1 ringback tone MINOR alarm
Code 2 ringback tone No alarm
ASCS has the capability of repeating the alarm indicating call if the alarm
condition is not corrected, or if its severity has worsened since the checking
call was made. When the office is left unattended, the ASCS feature is
activated by operation of the alarm transfer switch on the alarm control and
display panel or by using a command from the MAP.
MAP alarm level screening feature
This feature expands the capabilities of customer screening at the TTP to
allow customized trunk group alarms to be shown at the customer’s
terminal. The calculation of alarm levels for display at the customer’s
premises is based solely on that customer’s trunk groups only. This
calculation does not include other trunks in the office.

Station ringer test

The Station Ringer Test (SRT) consists of tests performed on the station
equipment, usually a residential telephone station or a coin station, by a
person at that station with no involvement with operating company
personnel at the CO.
SRT capabilities
The DMS-100 provides a SRT, which performs a dial test, off-hook ground
test, and on-hook ground test. The following is the sequence of subtests that
are performed, when applicable. The SRT may be ended after either Subtest
A or B has been performed:
• subtest A DP digit collection/DP station

DMS-100 International Technical Specification BCS40i and up

10–26 Maintenance

• subtest B digitone digit collection/DTMF station

• subtest C coin return/coin station
• subtest D party identification and ground checks
The dial pulse digit collection subtest collects digits received and compares
them with known dialed digits. The DIGITONE digit collection subtest
collects all digits during dial tone to verify that any initial digit would break
dial tone on a normal call. In a coin station, the coin return subtest operates
the coin control mechanism to verify correct operation.
SRT implementation
The SRT uses the following hardware:
• MTA connected to the LM containing the line card connected to the loop
of the station being tested
• LTU connected to the MTA used
• line card
• a DTMF receiver (if station is DIGITONE).

The SRT can be accessed by dialing one of the following number formats,
from the station to be tested. There is a concurrent eligibility for ten digit
number formats:
• Seven digit number Where three digit access code is followed by the
last four digits of the DN for the station that is being tested or where a
two digit access code is followed by the last five digits of the DN for the
station that is being tested.
• Ten digit number Where a three digit access code is followed by the
seven digit DN of the station that is being tested.
• Thirteen digit number Where a three digit access code is followed by
the NPA and the seven digit DN of the station that is being tested.
• Concurrent eligibility of 10 or 13-digit number If this option is
adopted there is a delay of a few seconds when no NPA is used, so that
the LCD can be assured that no additional digits are forthcoming.
Seven-digit number can be made available concurrently with ten,
thirteen, or concurrent eligibility.
A dial tone returned to the station signals that the SRT is ready for use; a
reorder tone signals that the SRT is not ready for use. The SRT times out
after 3.5 minutes if the test sequence is not acted on. (The Electronic
Business Set (EBS) line is automatically returned to the state IDL seven
minutes after the start of the test.) After accessing the SRT, the tester
conducts tests that are applicable according to the Lines Maintenance Guide,
297-1001-594.

PLN-5001-001i Standard 02.02 April 1997

 Maintenance 10–27

User defined command files

DMS-100 Family systems include a facility to permit MAP users to create,
file, and execute sets of MAP input commands. This programmable
capability provides a powerful means whereby an operating company or
individual craftsperson can construct custom test sequences. These test
sequences could be standardized by the operating company for
company-wide use if desired. Conversely, individual test sequences could be
used for particular offices should there be special outside plant or other
problems in that office. During rearrangement activities, the desired test
sequence could be planned in advance and then executed singly or
repetitively as appropriate. This capability is used by opening and naming a
file using the EDIT program. Any valid sequence of MAP commands may
then be entered into the file. The file may be saved in main system memory
or on magnetic tape. Available maintenance MAP commands are described
in this section.
The sequence of commands stored in the custom file may then be executed
any time by accessing the file and issuing a single MAP command.

Dialable cable locator tone

This feature allows a craftsperson to locate a specific tip and ring (A-lead
and B-lead) cable pair among a group of cables in any location. The
craftsperson connects a phone to any tip and ring cable and dials a security
access code of three to seven digits followed by the DN of the desired line.
The DMS-100 Family system switch connects an external tone supply to the
desired line for a specified duration. The tone supply is connected by way
of a MAINT type trunk which is datafilled in Table TRKGRP. The
craftsperson then uses a special probe, designed to accept the frequency of
the applied tone, and locates the desired cable pair. The tone generator and
probe are supplied by the operating company.

Silent switchman feature

The silent switchman feature enables a craftsperson to test the outside plant
without the need of a second person in the office to open the cable pair. It is
accessed via a three-digit code dialed from the customer station. Ten
seconds of busy tone are given, and then the line is cut off for a period of up
to 255 seconds, (data modification order modifiable), to allow testing on an
open circuit. If the line is still off-hook when the cut-off relay is released,
the line re-originates and receives dial tone. The silent switchman feature
does not require any hardware at the terminating end. Routing is
accomplished much like the synch-nonsynch test line which makes use of a
fixed CLLI group. Silent switchman is not supported for RCS (SLC-96)
lines.

DMS-100 International Technical Specification BCS40i and up

10–28 Maintenance

Dialable short circuit

This feature provides single person access and testing through the use of a
variable length access code (three to seven digits) that may be dialed from a
line. The DMS places a short across the tip and ring of a specified line for
up to six minutes (variable), with a three minute default. The short is
removed at the end of the timeout. If the condition of the line prevents
dialing, the test may be initiated from a different line by dialing the access
code and the seven-digit DN of the desired line. By providing this feature,
the telephone operating company reduces the total manpower required for
cable testing.

Interoffice transmission testing

DMS-100 Family system test lines facilitate various manual and automatic
tests to distant toll and local offices without human intervention at the called
offices.
This section summarizes the test line capabilities available on the DMS-100
International switch.
Nl00, Sl00, Tl00 test line
The 100 test line, also known as a quiet or balanced termination, is used for
noise and loss measurements. The 100 test line test can be invoked
manually through the TTP or automatically through automatic trunk testing.
There are three versions of the 100 test line test; S100, N100, and T100.
The S100 provides a quiet termination for noise measurements only. The
N100, a more recent version of the test, also includes a milliwatt test (a T102
test line) and can be used for far-to-near loss measurements. The T100 is
used when the equipment at the terminating office is unknown. When the
T100 test line is performed, a two-second time-out is introduced to detect
the presence or absence of a milliwatt tone. If the T100 test detects the
milliwatt tone, it executes the N100 version of the test; otherwise, the S100
version is initiated. If the version of the distant office test line is known,
then that version of the test line can be performed directly, and thus the
two-second delay per trunk of the T100 test line test is eliminated.
The DMS-100 Family system provides N100 and S100 quiet termination.
Tl0l test line
The T101 test line is used to establish two-way communications between the
test position and any trunk incoming to the system.
The connection to the T101 test line is established through the switching
network. To transfer from the voice mode to the test mode, a MAP must be
available in the manual trunk test level. In this level, two commands are
available which allow transfer of the connection:
• Call Transfer (CALLTRF) transfers connection to TTP, making it
available for maintenance functions.

PLN-5001-001i Standard 02.02 April 1997

 Maintenance 10–29

• Headset (HSET) returns trunk in the control position on the TTP to the
communication module for voice access.
Capability is provided to direct a T101 call to a designated TTP, for
example, a 101XX call will be routed to the TTP designated XX. If the TTP
is busy, the call will be offered to any free TTP. Tests to a distant office
code 101 test line are directed from the MAP position. Refer to the Trunks
Maintenance Guide, 297-1001-595 for additional information.
Tl02 test line
The purpose of the T102 test line, also known as a milliwatt test line, is to
apply a 1004 Hz test tone towards the originating office to facilitate simple
one-way manual or automatic transmission loss measurements. The test
tone is applied for a timed duration of nine-seconds during which an
off-hook answer signal is provided. An on-hook signal, followed by a quiet
termination, is then transmitted to the originating end until the connection is
released by the originating end.
Seven-digit access is available for the T102 test line, as well as T102 access.
The DMS Family system directs manual and automatic tests to the milliwatt
test line.
Detailed information on test line operation is provided in the Trunks
Maintenance Guide, 297-1001-595.
ATME test line
The automatic transmission measuring equipment (ATME) test line provides
the following test capabilities on the DMS-100 International switch:
• loss measurement
• frequency deviation
• noise
• supervision
• busy flash

These tests can be performed individually or in various combinations.

Additional information on ATME is provided in the Trunks Maintenance
Guide, 297-1001-595.
ARTER test line
ARTER is used for automatic transmission testing of outgoing trunks in the
Turkish network. The ARTER system works in conjunction with far-end
6085 units, which provide 804 Hz reference frequency and quiet
termination. ARTER tests include expected measured loss (EML),
maintenance noise limit (MNL), immediate action noise limit (IANL).

DMS-100 International Technical Specification BCS40i and up

10–30 Maintenance

Additional information on ARTER is provided in the Trunks Maintenance

Guide, 297-1001-595.

Trunk test facilities and features

This section summarizes the trunk test facilities and features provided on the
DMS-100 International switch. Additional detail on trunk testing
capabilities and methods is provided in the following NTPs:
• Commands Reference Manual, 297-1001-821
• Trunks Maintenance Guide, 297-1001-595

Trunk test facilities at the maintenance center

The trunk test position (TTP) is used in the trunk maintenance center of a
DMS-100 Family system office for manual and automatic testing of trunks
and their associated facilities to the distant office. The TTP is basically a
MAP equipped with the VDU, a communications module, jack field and
optional associated furniture as described in this section.
The TTP functions may be performed from a remote MAP. Functions
requiring external test equipment or monitoring may only be performed if
the jack-ended trunks and headset circuit are extended to the remote
location.
The test equipment required for the TTP test functions is internal to the
DMS-100 Family system and is not dedicated to any specific TTP. The
trunk test equipment is mounted on the Maintenance Trunk Module (MTM).
It is selected from a common pool of test equipment when required by the
TTP. When a test function has been completed, the test equipment is
returned to the common pool.
The test equipment available in the common pool consists of a milliwatt
supply and a transmission test trunk (TTT). The milliwatt supply provides a
standard milliwatt source at 1004 Hz. The TTT, which consists of a pulse
code modulation (PCM) level meter card and a test signal generator card, is
used in four ways:
• loss measuring device indicates frequency and level
• noise measuring device, C-message weighting
• tone detector identifies supervisory signals
• frequency generator, adjustable frequency and level

The PCM level meter (PLM) card contains circuitry for measuring the level
and frequency of PCM samples representing analog voice frequencies or
tones. The PLM card contains a level meter and a frequency meter which
are activated by control signals from the MTM at the appropriate time for
the channel under test.

PLN-5001-001i Standard 02.02 April 1997

 Maintenance 10–31

The DMS-100 Family system provides the capability of measuring and

applying the level of a nominal 400 Hz, 1 KHz or 2800 Hz. The actual
frequency range accommodated by the DMS-100 Family system is 4–3996
Hz with level of range +3 dBm0 to –60 dBm0. In addition to this, various
test line tests, such as, open circuit, short circuit, and balance, are provided
by the DMS-100 Family system.
Focused trunk maintenance
Focused trunk maintenance for trunks offers the ability to reposition
maintenance personnel onto the MAP away from log terminals trunk fault
processing. Focused trunk maintenance provides this ability through alarm
thresholding and failure information buffering. This provides better
interaction with alarms to effect repair.
Alarms are generated when troubles, identified by software, exceed a
customer-defined threshold. The customer designates thresholds for minor,
major and critical alarms as a percentage of the successful call attempt,
value N. The DMS increases the failure count for each failure and decreases
it for each N calls completed successfully.
When a failure count exceeds the threshold, an alarm level is generated and
a 15-minute wake-up period is invoked. The alarm level may not decrease
during this period except by being manually reset. The package continues
processing messages during this stage, and if a higher level condition
develops, a new wake-up process begins.
With focused maintenance, the buffering of failures is handled by two
buffers, designated the upper and lower buffers. A pair of these buffers
exists for each trunk group in the office. The upper buffer contains ten
records of the worst members of a group (those failing more than once).
The lower buffer records up to five members that have failed only once.
Separate sets of buffers, one for call processing activity and another for
maintenance activity, are available.
The activation of focused maintenance deactivates log messages generated
to report failures. Any fault that would have generated a log message is
processed through the buffers to ensure that the latest data is available to
help direct maintenance actions. Customers can reactivate the generation of
log messages as desired by temporarily activating the specific messages.
Commands available at the MAP provide for display of the buffers and of
the groups having active alarms. Other commands permit suppression and
resumption of specific trouble reports and review of the trouble designation
list. A new post command automatically creates a post set of all buffered
members for appropriate testing and fault resolution action.
Focused maintenance improves maintenance response by thresholding the
alarms and buffering failure information for reference by way of the MAP

DMS-100 International Technical Specification BCS40i and up

10–32 Maintenance

levels as required. The focusing of maintenance activity to the MAP and

away from logs improves maintenance efficiency and actions, because the
maintenance personnel are not responding to every minor problem, and are
able to move easily between the alarm reporting and maintenance action
required to isolate and clear the fault.
Automatic trunk test facilities
The DMS-100 Family system automatic trunk testing (ATT) feature
provides automatic test line testing for outgoing trunks and the outgoing
portion of two-way trunks and diagnostic tests on any group or circuits that
can be identified by CLLI. Various test line and diagnostic tests are
provided to maintain these trunks by monitoring the quality of trunk
signaling and transmission.
There is no test equipment associated directly with ATT. All required test
equipment is obtained from a common pool and, when no longer needed by
ATT, is returned to the common pool.
ATT works on a trunk group basis. Tests are basically scheduled by
specifying the trunk group to be tested, the test to be performed (test line or
diagnostic), and the frequency at which the test is to be run on the
group—more than one test can be specified per group. When a trunk group
is under test, ATT steps through the group attempting to run the requested
test on each trunk in succession. The maximum number of groups to be
tested simultaneously can be set manually to a maximum of 15. In practice,
this number would be limited, for example, by the amount of test equipment
available.
The ATT logs reports to inform the craftsperson of its progress and the
results of its trunk tests. The types of logs to be output are under manual
control. A summary report is logged at the end of testing a trunk group.
Trunks may be removed from service if found to be faulty by ATT. If this
option is requested, an upper limit of 25% or 50% must be set for the
number of trunks from the group to be removed from service.
Automatic trunk group test scheduling is normally predefined through table
control; however, individual groups can also be manually scheduled for
testing at the ATT MAP level, by telescoping through the MTC and TRKS
levels of the MAP. Maintenance personnel can monitor and control ATT
using table control, the TTP, and the log system.
Additional information on automatic trunk testing can be found in Trunks
Maintenance Guide, 297-1001-595.

PLN-5001-001i Standard 02.02 April 1997

 Maintenance 10–33

Cutover and growth features

This section describes methods and strategies used in performing extensions
or equipment growths in the DMS-100 Family system and are based on two
criteria:
• minimum interruption to the peripheral working equipment, such as,
trunks
• essential parts of control equipment are duplicated (central control
complex and digital networks) which provide the capability to work on
one side of the system and process calls on other side.
Procedures for trunk growth and testing
The addition of trunks, service circuits, and test circuits in the DMS-100
Family system to an existing trunk peripheral, or the addition of a new trunk
peripheral to an existing trunk equipment bay, will not disrupt the system,
service, or cause any deterioration in the grade of service.
All growth equipment or trunks are placed into the inactive level. In this
state, they will not be accessed either by call processing programs or
automatic diagnostics. This inactive level is accessed by commands from
the MAP. Another set of commands will be required to move equipment
from the inactive level into the active on-line level.
The growth or extension of equipment has no effect on a working DMS-100
Family system as long as the extended equipment remains in the inactive
level mode. Once the extended equipment is integrated into the system, it
will be governed by the normal fault recovery programs, since there will be
no differentiation between existing or extended equipment.
Procedures for data store and network module extension
The procedures used to extend the switching core are generally similar to
those used for adding trunk circuits.
Because the switching core is fully duplicated, the DMS-100 Family system
can be reconfigured into two halves for extension. The new equipment is
physically installed and cabled. It is marked inactive in software. One-half
of the machine handles the total traffic using the old configuration. The
second half is configured to include the new equipment, and test it. Once
the new equipment is properly tested and integrated on the inactive machine
side, the half which has been extended is activated and the unextended side
made inactive. The procedure is then repeated. On completion, both halves
are extended and duplex operation can resume.
Assignment of both new and old peripherals to new and old network
modules is simplified by the use of the speech link connecting frame. This
frame is used to cross-connect the 30-channel voice links from peripheral

DMS-100 International Technical Specification BCS40i and up

10–34 Maintenance

modules to network ports. To simplify the process, connectorized patch

cords are used.
Procedures for line growth and testing
The addition of line cards in the DMS-100 Family system to existing line
concentrating modules, or the addition of new line concentrating modules,
will not disrupt the system or service, or cause any deterioration in the grade
of service. If a line drawer is to be added to an in-service line concentrating
module, it is not necessary to remove power from the LCM. The drawer is
plugged in and then the fuse is inserted into the fuse panel, providing power
to the drawer.
Detailed procedures are available and will not be included here. The concept
is basically the same as that covered under trunk growth described in this
section. Growth equipment is placed in the software state of inactive or
Installation Busy (INB) until it is ready to go into service.
Implementation of growth
The procedures outlined in these paragraphs are designed to cause no
interruption of working equipment or call processing. The duplicated
network in DMS-100 Family systems permits increasing the network size
without impacting call processing and simplifies the growth task itself.
Associated with growth is the concept of two-stage provisioning versus
conventional provisioning.
With the conventional approach, all the switching equipment is engineered,
ordered and installed for the engineered interval simultaneously. A
two-stage provisioning method is suggested for DMS-100 Family systems.
The basic CPUs and the central message controllers shelves are not
engineered or extended, since they are installed on the initial job for the
ultimate capacity of the office.
Provisioning of the network and peripheral equipment components, and the
program and data stores, constitutes stage one. The equipment frames will
be engineered and installed for the job interval, based on requirements
established by the operating company. The associated modules, including
shelf backplanes, control cards, and so on, will be provided and installed
simultaneously as part of this stage.
The second stage is the provisioning of items such as analog trunk and
digital trunk plug-in cards. These are purchased and installed by the
operating company as required and supplied by Northern Telecom on a
plug-in-provisioning basis. This means that the office will be engineered for
the initial and growth requirement but equipped for the initial requirement
only. The net result is that various plug-in cards are not purchased until
required for service rather than at the beginning of an engineering interval.

PLN-5001-001i Standard 02.02 April 1997

 Maintenance 10–35

Line test facilities

This section summarizes the line testing facilities provided on the DMS-100
International switch. For additional detail on these capabilities, refer to the
Lines Maintenance Guide, 297-1001-594.
The Line Test Position (LTP) is used in the line maintenance center of a
DMS-100 Family system office for manual and automatic testing of
subscriber lines. The LTP is basically a MAP equipped with the visual
display unit, a communications module, jack field, and optional associated
furniture as described in this section. The LTP functions may be performed
from a remote MAP; however, functions requiring external test equipment or
monitoring may only be performed if the jack-ended trunks and headset
circuit are extended to the remote location.
The test equipment required for the LTP test functions is internal to the
DMS-100 Family system and is not dedicated to any specific LTP. The
trunk test equipment is mounted on the MTM. It is selected from a common
pool of test equipment when required by the LTP. When a test function has
been completed, the test equipment is returned to the common pool.

Line testing hardware

Specific hardware is used for line testing.
• Line test position
• Line test unit
• Transmission test unit
• Transmission test trunk
• Jack-ended trunk
• External test equipment
• Metallic test access
• Printer
• T101 communications test line
• I/O test trunk

Line test position

The Line Test Position (LTP) is a MAP consisting of four items:
• VDU
• Furniture
• Voice communications module
• Test jacks

DMS-100 International Technical Specification BCS40i and up

10–36 Maintenance

Line test unit

The Line Test Unit (LTU) consists of two circuit packs located in an MTM.
This unit is connected to a selected line circuit under test via the MTA unit.
Transmission test unit
The Transmission Test Unit (TTU) consists of two circuit packs located in
an MTM. This unit is connected to a selected line circuit via the internal
digital network.
Transmission test trunk
The Transmission Test Trunk (TTT) consists of two circuit packs located in
an MTM. This unit is connected to a selected line circuit via the internal
digital network.
Jack-ended trunk
Jack-ended trunks are manufactured with two trunks per circuit pack and are
located in an MTM. A jack-ended trunk is connected to a pair of jacks
normally located at the LTP. The jack-ended trunk interfaces special test
equipment at the LTP with a selected line circuit under test via the internal
digital network.
External test equipment
External test equipment includes any special test equipment not regularly
used at the LTP and connected to the line card via the test jacks. The return
loss measuring set and the impulse noise measuring set are examples of
external test equipment.
Metallic test access
The Metallic Test Access (MTA) is a small matrix used to provide a dc path
between certain test equipment and the line circuit under test via the LCM
test access bus. The LTU and the No. 14 test desk are examples of test
equipment which use the MTA. The MTA is located on a miscellaneous
frame. It is cabled directly to the LCM and connected to the test equipment
via the DF.
Printer
The printer is used to obtain the results of ALT. This unit, not part of the
LTP, can be located in the same DMS-100 Family system office or remotely.
It is also used in conjunction with manual line testing if a hard copy record
is required.

PLN-5001-001i Standard 02.02 April 1997

 Maintenance 10–37

I/O test trunk

The I/O test trunk is a 2X90 card mounted in an eight-wire trunk module
(TM8) at a host office, in a Remote Maintenance Module (RMM) at an
RLCM, or in a Remote Service Module (RSM) at an RLM. It provides a
DMS interface with non-DMS local testing equipment. This enables
maintenance personnel who operate the non-DMS test equipment to access
subscriber lines via the MTA.
• no. 14 local test trunk
• no. 3 local test cabinet
• mechanized loop testing system (MLT 1 and MLT 2)

Communication test line

The 101 communication test line uses a 5X30 card mounted in a TM. It
interfaces the NM and the LTP, and is used at the communication module to
originate voice contact with a subscriber.
Line test descriptions
These line tests can be performed manually:
• short diagnostic
• extended diagnostic
• line insulation
• on-hook balance network
• off-hook balance network
• loss
• noise
• line
• dc voltage
• ac voltage
• resistance
• capacitance
• coin

The following tests also can be performed using automatic line testing
(ALT):
• short diagnostic
• extended diagnostic
• line insulation
• on-hook balance network

ALT is described on page 10–39.

DMS-100 International Technical Specification BCS40i and up

10–38 Maintenance

Short diagnostic test

The short diagnostic test is only performed on the ALT level. This test
routinely checks most of the DMS-100 Family system line circuit for correct
operation. Specifically, the pulse code modulation (PCM) path to and from
the line card as well as the analog path of the VF transformer are checked.
Under this test routine, the following subtests are performed:
• trans-hybrid loss test
• attenuation pads in the line card
• notch & weighted noise test
• ring supervision

Extended diagnostic test

The extended diagnostic test routine checks virtually all of the line circuit
for correct operation. This test routine is more comprehensive than the short
diagnostic test with the following subtests being performed, as appropriate
for particular line cards:
• transhybrid loss
• attenuation pad
• noise
• loop signal at keyset (business set only)
• flux cancellation
• loop detector
• two-party ANI (DMS-1 RCT only)
• equalization current detector (business set only)
• buffer full flag (business set only)
• reversal relay (POTS only)
• +48 V reversal relay (DIGITONE fraud prevention)
• ground start relay
• ground start detector
• cutoff relay
• subscriber loop
• ringing and supervision (POTS only)
• test access relay

Additional information on line circuit testing capabilities and procedures can

be found in the following documents:
• Commands Reference Manual, 297-1001-821
• Lines Maintenance Guide, 297-1001-594

PLN-5001-001i Standard 02.02 April 1997

 Maintenance 10–39

Focused line maintenance

The focused maintenance software package offers the ability to reposition
maintenance personnel onto the MAP away from log terminals for line
processing. Focused line maintenance provides this ability through alarm
thresholding and failure information buffering. This provides better
interaction with alarms to effect repair. With focused maintenance, the
buffering of failures is handled by two buffers, designated the upper and
lower buffers. A pair of these buffers exists for each line concentrating
device in the office. This feature functions similarly to the focused trunk
maintenance feature described on page 10–31.
Automatic line testing
Automatic Line Testing (ALT) is usually performed on a scheduled basis;
operating company involvement is limited to the initial scheduling.
Normally ALT is run on a large group of host or remote lines during a low
traffic period. ALT identifies line faults so that they can be cleared before
they become service affecting, and before subscriber reports are originated.
Lines which fail to meet established standards of quality are identified to the
operating company by posting the failures at the Line Test Position (LTP)
and by output reports generated from the ALT log subsystem. The line
failures that are identified in this way are then manually tested and
corrected.
All test equipment that is required for ALT is internal to the DMS-100
Family system. Therefore, any MAP can be used to schedule ALT. For
example, a MAP configured as an LTP may be used to schedule ALT.
Additional information on automatic line circuit testing capabilities and
procedures can be found in the Lines Maintenance Guide, 297-1001-594.
Line card overvoltage protection
Hazardous voltage conditions on World Line Cards (NT6X17BA and
NT6X18BA) are automatically detected by the system. When a high voltage
is detected, the cut-off relay on the line card is activated. The hazardous
voltage condition is visible to maintenance personnel in several ways:
• at the lines subsystem of the MAP MTC (maintenance) level, the
affected line is placed in HAZ (hazard) state
• a major alarm, HZD, appears in the LNS header in the MAP MTC alarm
banner
• a LINE132 (critical) log report is generated
• Register HAZDET in operational measurement (OM) group LINEHAZ
is pegged.

DMS-100 International Technical Specification BCS40i and up

10–40 Maintenance

The system determines that hazardous voltage exists on a line when any of
the following conditions apply:
• the voltage at TIP (A-lead) equals or exceeds +75.0 volts ± 4.0 volts
with respect to ground at any time during a 30 ms interval
• the voltage at TIP (A-lead) is equal to or less than –75.0 volts ± 4.0 volts
with respect to ground at any time during a 30 ms interval
• the voltage at RING (B-lead) equals or exceeds +75.0 volts ± 4.0 volts
with respect to ground at any time during a 30 ms interval
• the voltage at RING (B-lead) is equal to or less than –75.0 volts ± 4.0
volts with respect to ground at any time during a 30 ms interval

PLN-5001-001i Standard 02.02 April 1997

 11–1

Transmission
The DMS-100 International switching system is specified for application as
a Class 5 or higher office, and is capable of meeting the transmission Plan
Objective of all normal configurations.

Transmission level
The DMS-100 International switch operates at 0 dBr when configured in a
digital network, unless otherwise specified by the operating company.

Analog connection transmission specifications

Measurement points
Unless identified otherwise, specifications are stated in terms of Main
Distribution Frame (MDF) to MDF measurements, with nominal impedance
terminations. For these performance limits to apply, peripheral module to
MDF cabling should be restricted to 75 feet (22.68 m) of 26 gauge cable;
otherwise, allowance must be made for the office cabling in evaluating
transmission performance.
Care must be taken to eliminate feedback as a source of measurement error
between 2-wire interfaces, for example, disabling the bitstream in the
direction of transmission opposite to the direction under test.
Performance limits apply for a network loss of 0 dB. If connection loss
includes digital pads, an additional degradation can be expected.
Transmission specifications
The following parameters are met, with the switching equipment installed in
a switching center, during any one maintenance interval.
The transmission specifications apply over the normal operating
environmental range of 50 degrees F (10 degrees C) through 86 degrees F
(30 degrees C), relative humidity of 20 to 55 percent, and office power
within the range of –42.5 V to –55.8 V with –48 V nominal voltage.
Unless otherwise specified, the following definitions apply:
• Trunk refers to a 4-wire digital trunk.
• Line-to-trunk also refers to trunk-to-line.

DMS-100 International Technical Specification BCS40i and up

11–2 Transmission

• The analog-to-digital and digital-to-analog portions of the transmission

path are nominally equal.
• Line refers to a Plain Ordinary Telephone Service (POTS) line.
Digital milliwatt (digital test sequence)
The repetitive transmission of the following sequence of digital codes in a
given connection will be decoded at a properly aligned circuit output as a 0
dBmO 1000 Hz (nominal) sinusoidal test signal:

Table 11–1
Digital standard level points
Bit position
Word no. 1 2 3 4 5 6 7 8

1 0 0 1 1 0 1 0 0
2 0 0 1 0 0 0 0 1
3 0 0 1 0 0 0 0 1
4 0 0 1 1 0 1 0 0
5 1 0 1 1 0 1 0 0
6 1 0 1 0 0 0 0 1
7 1 0 1 0 0 0 0 1
8 1 0 1 1 0 1 0 0

This repetitive sequence of 8 digits is defined as the digital test sequence

(DTS). This set of codes listed above is used only in specifications. It is not
used as a test signal in the DMS-100 International systems as it contains
patterns that could erroneously simulate PCM-30 carrier framing patterns.
Equipment transmission levels
Minor variations may occur from country to country – See also Country
Specific Specification.
Line equipment levels (1004 Hz loss)
Line Circuits:
• Nominal loss of analog-to-digital (A/D) path: 0.0 dB
• Nominal loss of digital-to-analog (D/A) path: 0.0 dB to 7 dB in
1 dB steps dependent on the type of connecting circuit and requirements
of the appropriate telephone Administrations Transmission Plan
Objectives.
The line circuit D/A loss steps are implemented with analog pads under
software control.

PLN-5001-001i Standard 02.02 April 1997

 Transmission 11–3

The long-term variation due to temperature and voltage changes may change
the loss by not more than +0.5 dB.
Analog trunk equipment transmission levels
Analog test access is provided via a maintenance trunk module (MTM).
Test trunk circuits in DMS-100 International systems incorporate either a
fixed or variable pad in order to introduce the loss level required for
application in the transmission plan. The variable loss in the range 0 to
15.75 dB in 0.25 dB steps adjustable by software or manual switches allows
for compensation of cable losses and/or the requirements of the transmission
plan objectives. An example is the 101 communications test trunk
(NT5X30).
Characteristics of subscriber line interfaces (NT6X93, NT6X94)
Input return loss
The return loss of the impedance presented to the 2–wire port against the
reference impedance will be equal to or greater than the limits given in
figure 11–1.
Figure 11–1xxx
Input return loss limit
FW-31173

18

14
Input return loss (dB)

0
0 300 500 2000 3400
Frequency (Hz)

DMS-100 International Technical Specification BCS40i and up

11–4 Transmission

Terminal balance return loss (TBRL)

The transhybrid loss of the line interface when measured in accordance with
figure 11–2 against a test network of Z will meet the following limits.
• Echo return loss: When measured with the uniform spectrum signal, the
TBRL will be equal to or greater than 22 dB.
• Single frequency return loss: When measured with sinusoidal signals,
the TBRL will be equal to or greater than the limits shown in figure 11–3
on page 11–5.
Figure 11–2xxx
Arrangement for measuring TBRL
FW-31177

Exchange
Weighting Send test point
network Ti
Standard Po
Uniform spectrum send side
signal generator

Terminal
balance return
loss limit test
network
Root mean Receive To
square or quasi
root mean Standard Pi
Sinusoidal square detector receive
oscillator side

Exchange
test point

Note: This equipment may also be all-digital, with equivalent functions. The “standard send side”
and “standard receive side” are then not present.

The TBRL limits given assume the transmit and receive pads, P1 and P0, are
set to 0dB.

PLN-5001-001i Standard 02.02 April 1997

 Transmission 11–5

Figure 11–3xxx
Terminal balance return loss limit
FW-31175

20
Terminal balance return loss (dB)
15

0
0 300 500 2500 3400
Frequency (Hz)

Impedance unbalance about earth

The measured value for the longitudinal conversion loss (LCL) which is
defined in CCITT Rec. G117 will be equal to or exceed the following limits
when the line interface under test is in the normal speech condition.

Table 11–2
Longitudinal conversion loss
Frequency (hertz) Minimum LCL (90% of interfaces)
204 58 dB
504 58 dB
1004 58 dB
3004 53 dB

VF parameters for subscriber line-to-line connections

1004 Hz loss
The nominal 1004 Hz loss through the exchange is defined as the design loss
of the exchange.
The average 1004 Hz line-to-line (L-L) connection loss through the
exchange will not exceed –0.0 to +0.5 dB from that specified as the nominal
loss.

DMS-100 International Technical Specification BCS40i and up

11–6 Transmission

Loss tolerances
The 1004 Hz loss for 95% of L-L connections will be within +/– 0.5 dB of
the value measured as the average loss.
Attenuation/frequency distortion
The attenuation/frequency distortion of 95% of L-L connections, relative to
1004 Hz, will meet the limits shown in figure 11–4.
Figure 11–4xxx
Attenuation distortion limits
FW-31176
Attenuation distortion (dB)

3.0

2.0
1.5

0.6
0

–0.6

160 Frequency (Hz)

Variation of gain with input level

When measured with a 1004 Hz test signal, the variation in gain relative to
the gain at 10 dBm0 will meet the following limits:

Table 11–3
Variation of gain with input level
Input level Gain variation
+3 to –40 dBm0 +/– 0.5 dB
–40 to –50 dBm0 +/– 1.0 dB
–50 to –55 dBm0 +/– 3.0 dB

PLN-5001-001i Standard 02.02 April 1997

 Transmission 11–7

Idle channel noise

The idle channel weighted noise on 95% of L-L connections will not exceed
LTN.
LTN = 10 log (PTN/1 pW) – 90 dBmp

where:
LTN is the total weighted noise level for the local digital exchange
PTN is the total weighted noise power for the local digital exchange
For example, if the output relative level (LO) of the exchange is –7 dBr, the
total weighted noise power (PTN) = 263 pWp, corresponding to
LTN = –66 dBmp.
The above noise values for digital local exchanges are based on an output
relative level of –7 dBr. In cases where essentially higher output relative
levels are used, for example, for intra-office calls, the noise contribution of
the PCM process will increase proportionally.
Crosstalk
The crosstalk between individual channels will be such that with a
sine-wave signal of frequency 1100 Hz and a level of 0 dBm0 applied to the
input port, the crosstalk level received in any other channel will not exceed
–67 dBm0.
For measurement, an auxiliary signal (a low level activating signal) should
be injected into the disturbed channel; a pseudo-noise signal as specified in
CCITT Rec. 0.131 at a level of –60 to –50 dBm0 is suitable. It is necessary
to use a frequency selective detector when performing this measurement.
Local distortion, including quantizing distortion
With a sine-wave signal at a nominal frequency of 820 Hz or preferably
1020 Hz (see Recommendations 0.132) applied to the input part of a
connection, the ratio of signal-to-total distortion power measured with the
proper noise weighting (see Table 4 of Recommendation G.223), should
exceed the value given by the formula:
{LS + LO –SN}/10 {LN/10}
S/N(total) = LS + LO – 10 (log (10 + 10 ))
10
where:
S/N(total) is the modified signal-to-total distortion ratio for digital local
exchanges
LS is the signal level of the measuring signal in dBm0
LO is the output relative level of the local exchange in dBr
S/N is the signal-to-total distortion ratio for PCM-channel
translating equipment in Recommendation G.712

DMS-100 International Technical Specification BCS40i and up

11–8 Transmission

LN is –67 dBmp = weighted noise caused by analog functions

according to Recommendation G.123, Annex A.
These limits include appropriate allowance for the noise contributed by
feeding currents.
As an example, the limits of Figure 12/Q.517 apply for an output relative
level of L = –7.0 dBr. See figure 11–5 for the limits.
Figure 11–5xxx
Limits for signal-to-total distortion ratio
FW-31174

40
Signal-to-total distortion ratio (dB)

30

20

10

0
–60 –50 –40 –30 –20 –10 0
Input level

Impulse noise
Noise counts will not exceed 5 counts in 5 minutes at a threshold level of
–35 dBm0.
Inter-modulation distortion
When measured in accordance with the 4-tone test method of composite
input level of –13 dBm0, 95% of test connections will be equal to or exceed:

Table 11–4
Inter-modulation distortion
dB below received power
R2 R3
line-to-line 44 45

The 4-tone test method involves the transmission of four equal level tones
(856, 863, 1374 & 1385 Hz) at the given composite level.

PLN-5001-001i Standard 02.02 April 1997

 Transmission 11–9

R2 = average power in the 503 to 537 Hz and 2223 to 2257 Hz bands.

R3 = total power in the 1877 to 1923 Hz band.
Absolute group delay
When measured at 1500 Hz, the absolute group delay of any (one-way)
line-to-line connection is equal to or less than 1500 microseconds.
Group delay distortion with frequency
Using the absolute group delay above as reference, the group delay
distortion for a single direction of transmission of any connection will meet
the following limits:

Table 11–5
Group delay distortion with frequency
Frequency (Hz) GRF delay distortion (uS)
500 600
600 400
1000 200
2500 200
2600 300
2800 400
3000 600

Delay measurements above are made using an envelope delay measuring

instrument with an 83.33 Hz modulating frequency.

Digital connection transmission specifications

International digital trunk controller (IDTC)
Transmission specifications
The IDTC provides digital speech and signaling interfaces between up to
sixteen 32 channel PCM-30 carrier systems at 2.048 Mb/s and up to sixteen
32 channel 2.56 Mb/s duplicated links (ports) to the DMS-100 International
digital network.

DMS-100 International Technical Specification BCS40i and up

11–10 Transmission

The IDTC transmission features are fully compliant with CCITT Red Book
Rec. G.703, 704, 705, and include the following.

Table 11–6
PCM-30 carrier interface characteristics
Characteristic Specification
Rate (input) 2.048 Mb/s +/– 50 PPM
(output) 2.048 Mb/s, phase locked to the office clock
Structure 32 channels per frame, 8 bits per channel
Signal structure com- bits numbered 1 to 8, bit 1 transmitted first
patible data format
Idle code 1 1 0 1 0 1 0 1 (CCITT Rec. G.174, paragraph 16.1)
0 1 0 1 0 1 0 0 (CCITT Rec. Q.503, paragraph 3.6)
Channels channels numbered 0 to 31, channel 0 transmitted first
Format 256 bits per frame, 240 speech bits (30 X 8)
Signaling and framing contained in channels 0 and 15
Code high density bipolar 3 (HBD3) code
PCM-30 receiver input see CCITT Rec. G703.6.3
signal
PCM-30 transmitter – see CCITT Rec. G703.6.2
– nominal peak voltage of a mark
– coaxial 75 ohm resistive 2.37V, symmetrical pairs 120
ohm resistive 3.0V
– positive/negative unbalance: 5%
– half amplitude width: 224 =/– 25 uS
– unbalance in width of positive/negative pulse: 5%
– peak voltage of a space (no pulse) COAX 75 ohm
resistive 0 +/–2.37V, symmetrical pair 120 ohm resistive
0 +/– 0.3V
Line impedance 75 ohm resistive (coaxial), 120 ohm balanced (symmetri-
cal pair)
Transformer inter- 500 Vdc minimum
winding isolation
Channel and port IDTC – distributed over equipped network ports
mapping

PLN-5001-001i Standard 02.02 April 1997

 Transmission 11–11

Network interface characteristics

The network interface characteristics of the DMS-100 International switch
are as follows:

Table 11–7
Network interface characteristics
Characteristic Specification
Rate 2.56 Mb/s
Structure 32 channels per frame, 10 bits per channel
Data format bits numbered 9 to 0, bit 9 transmitted first
Channels channels numbered 0 to 31, channel 0 transmitted first
Ports IDTC – ports numbered 0 to 15, plane 0 and plane 1
Frame frame bit–0, of channel–0
Signaling message channel – port 0, channel 0, bits 9 to 2, bit 9 is
most significant, bit 1 not used
Code bi-phase with frame plus violation once per frame
Receiver sensitivity 0.25V peak-to-peak
Driver output 2.4V +/– 0.1 peak-to-peak
Rise time 50 nanoseconds, minimum
Line impedance 100 ohms
Transformer inter- 500 Vdc minimum
winding isolation

Digital trunk to digital trunk echo path delay

The echo path delay is the total of the “go” and “return” transit time delays
of a signal through an office connection path.
For digital trunk to digital trunk connections, the average echo path delay is
less than or equal to 1.0 ms and 99 percent of connections have a delay less
than or equal to 1.4 ms.
Transmission pads
To assure transmission stability in conformance with the network
transmission requirements, interoffice calls may require the insertion of one
of several loss values (including zero loss) depending on the connection type
and the interfacing facility (for example, toll connecting, direct interlocal).
Usually, these losses are fixed and traditionally provided on analog facilities
external to the switching system.
DMS-100 International switching systems provide for the insertion, when
required, of any of several possible loss levels at the subscriber loop port
side. The determination of each loss level is under software control and is a
function of the transmission loss requirements for the connection.

DMS-100 International Technical Specification BCS40i and up

11–12 Transmission

In addition, digital pads associated with the DMS-100 International

switching Network will be used to implement various connection losses.
Network digital pad switching will complement the subscriber loop port
level adjustments mentioned above. The network pad values will be
software selected on a per call basis. Transmit and receive directions may
be handled independently for certain predetermined applications.
Digital pad values are:
• 0 to 7 dB of gain, in 1 dB steps
• 0 to 7 dB of loss, in 1 dB steps

Means are provided to automatically disable any pads in digital data

connections.
Refer to Equipment transmission levels for details on peripheral circuit
levels.

Clock synchronization
The DMS-100 International switch is synchronized using the Preselected
Alternate Master Slave (PAMS) arrangement. There are three possible
synchronous clock system configurations, as shown in figure 11–6 on
page 11–13.
• Master-Internal office: The free-running oscillator in one plane of the
central messaging element (central message controller on NT40–based
systems, or message switch on SuperNode-based systems) is used as the
network master clock. The associated hardware is duplicated in both
planes of the central messaging element; one clock is active and the
other is inactive. The inactive clock remains in sync with the active
clock to allow an immediate switch of clocking activity if required.
• Master-External office: This office is equipped to synchronize to an
analog reference clock. This analog clock may come either from a
source external to the office or from atomic clocks located in the office.
• Slave office: The central messaging element clocks in this type of office
are slaved to the clock in a master office, or to another slave office above
it in the network hierarchy, by clock signals carried over a dedicated
PCM-30 timing link. The PCM-30 timing links are duplicated for
reliability, and are provisioned in an International Digital Trunk
Controller (IDTC).

PLN-5001-001i Standard 02.02 April 1997

 Transmission 11–13

Figure 11–6xxx
Synchronous clock system outline of possible configurations

External
Master reference Optional
source source
frequencies:
10.24 MHz
10.0 MHz
5.0 MHz
DS-1 lines 2.56 MHz
*Slave *Slave 2.048 MHz
1.024 MHz
1.0 MHz

DS-1 lines DS-1 lines

Slave Slave Slave

*These Slave Offices are acting as Masters-Of-Slaves

Primary Links
Alternate Links

NT40 clocking
DMS-100 International switches based on the NT40 processing platform can
be configured as follows.
Standard synchronizable clock
The clock hardware consists of an NT3X14BA synchronous master clock
counter card and an NT3X15BB synchronous master clock card. These
cards are usually mounted in the CMC shelf, but the NT3X15BB
synchronous master clock card can be located in the Central Processing Unit
(CPU). Each office has two sets of clock circuit cards, one in each CMC
(CPU) to operate as active and standby sources.
The synchronous master clock card receives power from the associated
shelf. This circuit pack contains on-board regulators to produce the stable
voltages required by clock hardware components.
Backplane wiring options on the NT3X15BB synchronous master clock
allow a master office which is operating with an external reference oscillator
to synchronize to signals of 10.24, 10.0, 5.0, 2.56, 2.048, 1.024 MHz, or 1.0
MHz with a sine wave nominally +2.5V and 50 ohm impedance.

DMS-100 International Technical Specification BCS40i and up

11–14 Transmission

Stratum 1 synchronization
The DMS-200 uses the master external office configuration to achieve
Stratum 1 level accuracy, by interfacing with a cesium clock reference
mounted in a Master Reference Frequency Frame (MRFF).
The MRFF has two configurations:
• The NT5X23AA consists of two in-service cesium clocks, each being
independently powered and connected to its respective CMC clock
circuit. A third non in-service cesium reference is provided as a spare.
• The NT5X23AB consists of a two-clock system as described above
without provision for a spare.
Each cesium clock reference is connected to its associated CMC clock by a
maximum 200 feet (61 M) of 50 ohm coaxial cable and control wiring. The
control wiring allows the DMS-200 to provide indications of trouble on the
MRFF equipment and allows the DMS-200 to operate status lamps (active,
standby and spare) on the MRFF display and alarm circuit packs,
NT5X24AA, which are provided for each reference clock and are located on
the MRFF.
Stratum 2 synchronization
Stratum 2 level synchronization for a DMS-200 is provided by using the
master external on the slave configuration.
The stratum 2 Synchronizable Clock Master Oscillator, NT3X16AA, is an
ovenized Voltage Controlled Crystal Oscillator (VCXO). The NT3X16AA
is located on a Stratum 2 Oscillator Shelf, NT3X95AA, which is installed in
an NTOX43 Input/Output Equipment (IOE) frame. There are two clock
modules in the shelf, one for each CMC. The NT3X16AA, located in the
IOE frame is connected to its associated CMC Controller, NT3X15DA, by a
maximum of 200 feet (61 M) of 50 ohm coaxial cable and control wiring.
The Stratum 2 hardware mounted in the CMC consists of a Synchronizable
Master Clock Counter (NT3X14BC) and a Stratum 2 Master Oscillator
Controller (NT3X15DA).
Stratum 3 synchronization
Stratum 3 synchronization in the DMS-100 International switch uses the
slave configuration with a clock that meets Stratum 3 performance criteria.
The VCXO for Stratum 3 is located on the NT3X15CA, Stratum 3
synchronizable clock master oscillator, housed on the CMC shelf. The
NT3X14BA, synchronizable master clock counter, is housed in the same
location.

PLN-5001-001i Standard 02.02 April 1997

 Transmission 11–15

Synchronization loop
The block diagram in figure 11–7 on page 11–16 illustrates half of a
duplicated system. The main components are identified and their locations
shown within the DMS-100 International office. The control loop for the
active clock and its standby loop are identified.
A distributed phase-lock loop is formed by the clock oscillator whose output
is distributed to all hardware modules in the DMS-100 International office, a
digital phase comparator in the IDTC common equipment, the DMS-100
International internal message system, and the control algorithm in the CPU
which controls the clock oscillator frequency through a digital-to-analog
converter.
The incoming master clock signal received over the timing link is compared
in the PCM-30 card with the local clock signal. Firmware in the IDTC
samples the phase differences between the two signals and reports to the
synchronous clock software through the message system of the DMS-100
International switch, the IDTC message processor, the Network Message
Controller (NMC), and the CMC message processor.
In addition to checking for phase differences, the PCM-30 card also detects
and reports slips, bipolar violations, and lost synchronization.
The IDTC collects phase comparison samples at 400 ms intervals. After 32
samples are collected (12.8 seconds), a phase report is sent to the CC. The
phase report contains the 32 samples and information on slips.
In the CC control algorithm, the 32 phase values are normalized and
summed. The resulting average phase sample is integrated with 30–bit
resolution. The integrator output is then added to the average phase sample,
multiplied by a coefficient. The 30-bit word is truncated (to match the
resolution of the digital-to-analog converter in the NT3X15 synchronous
master clock card) and is sent to the NT3X14 controller. The control word
is thus updated after each phase report, every 12.8 seconds.
The D/A converter supplies a DC voltage to control the frequency of the
Voltage-Controlled Crystal Oscillator (VCXO) on the associated circuit
pack.

DMS-100 International Technical Specification BCS40i and up

11–16 Transmission

Figure 11–7
Synchronous clock system (simplified block diagram)

External Timing link

reference
clock

DS1 DCM/DTC
line processor DCM/DTC
card
10.24
MHz
mate Network
Active NMC module
CMC Clock control
clock 10.24 regen and NMC
loop
MHz
to digital
circuits

Phase CMC
det Synch message
osc processor
NT3X15
Standby D/A
or conv
active
ext NT3X14
control cont
loop
CPU
software
Clock
control
algorithm

The Stratum 2 and standard clocks use an ovenized crystal oscillator while
the Stratum 3 uses a temperature compensated oscillator. The D/A converter
allows the oscillators to be adjusted to a typical accuracy of:
• standard synchronizable clock: 1.0 x 10–9
• Stratum 2 clock: 1.0 x 10–11
• Stratum 3 clock: 7.5 x 10–9

The output of the VCXO assembly is a 10.24 MHz square wave to the
various digital circuits in the system.

PLN-5001-001i Standard 02.02 April 1997

 Transmission 11–17

The phase detector in the standby control loop comprises two counters
which allow the oscillator frequency to be compared with other sources – the
clock signal from the mate CMC, or an external reference clock when in the
master-external operation configuration. When used with an external
reference source, failure of such a source can be detected by the Central
Control (CC). Clock activity is then switched to use the mate CMC
oscillator as the office clock.
DMS SuperNode clocking
The clock system in the SN and SNSE switches is fully redundant. There
are two clock systems, one in each MS. One clock system is designated the
master and the other the slave. Frequency and phase synchronization is
maintained between the two systems, so that if a master clock system fails,
the slave clock system automatically assumes the master role.
The NT9X53 clock cards produce signals at two frequencies: the system
clock source at a nominal frequency of 10.24 MHz, and the subsystem clock
source at 16.384 MHz. Both signals are divided to 8 kHz for their respective
frame pulses. The frame pulses are synchronous.
The subsystem clock signal drives the MS T-bus, and is distributed to the
CM, ENET, and application processors (AP) using DS512 links. The system
clock signal is distributed to the JNET and the I/O controller (IOC) using
DS30 links.
The NT9X54 provides the electrical interfaces for various clock signals.
The types of clock signals include the following:
• analog external reference signals from atomic or loran-C clocks
• composite clock signals from a timing signal generator (TSG)
• DMS remote clock (Stratum 2 and 2.5)
• mate frame pulse

Stratum levels
A stratum level is a rating given to an oscillator to indicate its holdover
accuracy. The highest level of accuracy is Stratum 1. This rating is reserved
for the most accurate oscillators available, such as atomic and loran.
The following table shows the maximum acceptable drift for each stratum
level. The numbers shown represent how much of a complete cycle the
oscillator drifts on every cycle. When the numbers are inverted, it indicates
how many complete cycles it takes for the oscillator to be out of
synchronization by one full cycle.

DMS-100 International Technical Specification BCS40i and up

11–18 Transmission

Drift accuracy for stratum ratings

Stratum 1 Stratum 2 Stratum 2.5 Stratum 3

Amount of drift 1 x 10 –11 1.6 x 10 –8 6.2 x 10 –8 4.6 x 10 –5

(per cycle)

Synchronization configurations
The MS clock systems can be set up in any of the following configurations.
Master internal In a master internal office, the master clock is free
running (not synchronized to any external reference). Only signaling
transfer points are configured this way.
Master external In a master external office, the master clock is
synchronized to an external reference clock by a PLL. Phase comparison
between the master clock and the reference is performed on the NT9X53
card. In this configuration, the clock source for the network is typically a
Stratum 1.
Slave In a slave office, the master clock is synchronized to an incoming
PCM-30 carrier. Phase comparison between the master clock and the
reference is performed at the IDTC.

Remote system clock function

This function was introduced to improve the accuracy of the system clock.
A Stratum 2 or 2.5 level oscillator on an NT3X16 card is mounted in a
remote oscillator shelf. Although the remote clock is not physically
packaged in the SN or SNSE cabinet, it is still considered internal to the
DMS.
With the NT9X53AA and AB clock cards, the subsystem oscillator is
synchronized directly to the remote oscillator. If the link between the
remote shelf and the NT9X53 is breached, the system oscillator on the
NT9X53 card is lost.
With the NT9X53AC and AD clock cards, the system signal oscillator on
the NT9X53 card is used to maintain synchronization with the remote
oscillator. If the link to the remote shelf is breached, the system oscillator on
the NT9X53 can provide a stable reference to the subsystem oscillator.
Slip rate
When two offices are synchronized, no slips should occur on the PCM-30
lines between these two offices. Should synchronization be lost due to the
failure of all timing links between a master and a slave office, the slave
enters a free-run mode. The time to the first slip is dependent upon the
buffer fill at the time the free-run mode is entered. A buffer of two frames is
used. The Stratum 2 and Stratum 3 clocks comply with the slip rate of
objectives outlined in CCITT Rec. G822. The standard synchronizable

PLN-5001-001i Standard 02.02 April 1997

 Transmission 11–19

clock ensures less than 1 slip in 10 hours after being in the free-run mode for
72 hours.
Frequency capture width
When in a slave mode, a clock must be capable of synchronizing to a master
which is offset from the correct frequency by its maximum or minimum
allowed frequency. The DMS-100 International switch is capable of
synchronizing to a master with the following offsets:
• standard synchronizable clock: ± 7.5 x 10–7
• stratum 2 clock: ± 1.6 x 10–8
• stratum 3 clock: ± 4.6 x 10–6

Free-running mode frequency drift

When an oscillator is operating in the hold-over state in the free running
mode, the oscillator will experience a slow change in frequency due to aging
of the crystal.
This frequency change will be less than:
• standard synchonizable clock: ± 2 x 10–10 per day (see Note 1)
• stratum 2 clock: ± 1 x 10–10 per day
• stratum 3 clock: ± 3.7 x 10–7 per day (see Note 2)

Note 1: After 90 days of continuous operation, ± 3 x 10–10 until that time

has elapsed.
Note 2: The Stratum 3 clock is a temperature compensated oscillator. The
frequency change shown includes changes due to temperature as well as
aging.
While operating in the free-running mode, the clock frequency can be
manually adjusted by specifying, via MAP input command, a number of
steps to be added or subtracted from the D/A control word.
Error rate
Under specified operating conditions, the error rate of an internal
IDTC-to-IDTC connection is less than 1 x 10–9.

Compression law
The compression law used in DMS-100 International switches is a linear
approximation to A = 256 law as shown in CCITT G.711 tables.
The characteristics, decision levels and code assignments described in the
following sections include the effect of compression and expansion.

DMS-100 International Technical Specification BCS40i and up

11–20 Transmission

CODEC transfer characteristics

The relationship between encoder decision levels and the decoder output
levels is defined by specifying the CODEC transfer characteristic.
Figure 11–8 on page 11–21 shows the transfer characteristics for 8–bit pulse
code modulation (PCM) words. The output levels (Yn) are always midway
between the decision levels (Xn) (this can be termed a “decision level
assignment” CODEC). The output levels are given by:
Yn = (Xn–1 +Xn)/2 for n = 1 ...127, 128
Decision levels
Table 11–8 lists the relative magnitudes of the decision levels. The decision
levels are placed symmetrically about zero.
The maximum decision level magnitude has been normalized to 4096 so that
all level magnitudes may be represented by integer values. The magnitude
of the peak value of a +3.14 dBm0, 1 kHz single-frequency signal is slightly
less than that of the largest decision level.

Table 11–8
CODEC decision levels
Level number n Level magnitude Xn

0 0
1 ≤ n ≤ 16 2n–1
17 ≤ n ≤ 32 4 n – 33
33 ≤ n ≤ 48 8 n – 161
49 ≤ n ≤ 64 16 n – 545
65 ≤ n ≤ 80 32 n – 1569
81 ≤ n ≤ 96 64 n – 4129
97 ≤ n ≤ 112 128 n – 10273
113 ≤ n ≤ 128 256 n – 2409

PLN-5001-001i Standard 02.02 April 1997

 Transmission 11–21

Figure 11–8xxx
Codec transfer characteristics

Y0 = X0 = 0
Yn = Xn + Xm : n = 1, 2 ...127
2 m=n+1

Decoder output levels

Y3

Y2

Y1

X4 X3 X2 X1

X1 X2 X3 X4
Coder
Y1 input

Y2

Y3

Y0 = X0 = 0
N = 1, 2, 3, .....127
YN = XN + XN + 1
2

DMS-100 International Technical Specification BCS40i and up

 12–1

Equipment
This chapter provides general equipment installation and provisioning
information for DMS switching systems. Exact provisioning, installation,
and layout for each system varies depending on the market in which the
system is deployed, the application of the system, and the capabilities
purchased. For more detailed information on hardware and software
functionalities and provisioning rules, consult the following Northern
Telecom Practices (NTPs):
• DMS-100 Family Provisioning Manual, 297-1001-450
• Hardware Description Manual, 297-1001-805

Physical
The DMS-100 Family system hardware is packaged into single- or
double-bay frames equipped with appropriate shelves. Bays are identified
by their primary function. Shelves and drawers are identified by their
specific function.
Table 12–1 identifies the DMS-100 Family frames or bays with their
corresponding shelves and drawers.

DMS-100 International Technical Specification BCS40i and up

12–2 Equipment

Table 12–1
DMS-100 family bays and corresponding shelves/drawers
Bays Shelves/drawers

CCC — Central Control Complex CPU — Central Processing Unit

(Duplicated)
CMC — Central Message Controller

PS — Program Store

DS — Data Store

FSP — Frame Supervisory Panel

CU — Cooling Unit
DCE — Digital Carrier DCM — Digital Carrier Module
Equipment (4 max)

FSP — Frame Supervisory Panel

DNI — Digital Network Interconnecting NJC — Network Junctor Connector
(Duplicated) (or DNIC) Panel 16 (21 max)
DSNE — Double Shelf Network NET0 — Network Plane 0
Equipment
NET1 — Network Plane 1

FSP — Frame Supervisory Panel

CU — Cooling Unit
IDTE — Digital Trunk Equipment IDTC — Digital Trunk Controller

ILTC — Line Trunk Controller

ILGC — Line Group Controller

FSP — Frame Supervisory Panel

CU — Cooling Unit
—continued—

PLN-5001-001i Standard 02.02 April 1997

 Equipment 12–3

Table 12–1
DMS-100 family bays and corresponding shelves/drawers (continued)
Bays Shelves/drawers

IOE — Input/Output Equipment MTD — Magnetic Tape Drive

DDU — Disk Drive Unit

FSP — Frame Supervisory Panel

IOC — I/O Controller

DPP — Distributed Processing

Peripheral

BMC II — Billing Media Converter (SH

18, 51)

ROS — Stratum II Shelf

ILCE — Line Concentrating Equipment ILCA — Line Concentrating Array

FSP — Frame Supervisory Panel

ILGE — Line Group Equipment ILGC — Line Group Controller (2 max)

ILTC — Line Trunk Controller

IDTC — Digital Trunk Controller

FSP — Frame Supervisory Panel

CU — Cooling Unit
LTE — Line Trunk Equipment LTC — Line Trunk Controller (2 max)

DTC — Digital Trunk Controller

FSP — Frame Supervisory Panel

CU — Cooling Unit
MEX — Memory Extension DS — Data Store
(Duplicated)
FSP — Frame Supervisory Panel

CU — Cooling Unit (Optional)

MIS — Miscellaneous XXX — For miscellaneous equipment
shelves such as data sets, alarm
circuits, etc.

FSP — Frame Supervisory Panel

—continued—

DMS-100 International Technical Specification BCS40i and up

12–4 Equipment

Table 12–1
DMS-100 family bays and corresponding shelves/drawers (continued)
Bays Shelves/drawers

MS6E — Message Switching 6 DSM — Modem Assembly Modified

Equipment
STA6 — Signal Term Array 6 Shelf

MSB6 — MSB6 Module

CU — Cooling Inverter Unit

INV — Inverter Unit

FSP — Frame Supervisory Panel

MS7E — Message Switching 7 ST7 — Signaling terminal for SS7
Equipment
MSB7 — Message Switch and Buffer

STA7 — Signaling Terminal Array

ST7G — Signaling Terminal Shelf

FSP — Frame Supervisory Panel

CU — Cooling Unit
MSS — Maintenance Spare Storage XXX — For storage of spare circuit
packs
NETC — Network Frame Planes NCO — Network Crosspoint Plane 0
Combined (Duplicated networks)
NCI — Network Crosspoint Plane 1

NI — Network Interface Planes 0 & 1

FSP — Frame Supervisory Panel

CU — Cooling Unit
PDC — Power Distribution Center FPA — Fuse Panel “A” Feed (5 max)

FPB — Fuse Panel “B” Feed (5 max)

FSP — Frame Supervisory Panel

GP — Ground Panel (top or bottom

feed)

FP — Filter Panel
—continued—

PLN-5001-001i Standard 02.02 April 1997

 Equipment 12–5

Table 12–1
DMS-100 family bays and corresponding shelves/drawers (continued)
Bays Shelves/drawers

RCE — Remote Controller Equipment RCC — Remote Cluster Controller

Module

RMM — Remote Maintenance Module

(2 max)

FSP — Frame Supervisory Panel

CU — Cooling Unit
RCME — Remote Control & RMM — Remote Maintenance Module
Maintenance Equipment
HIE — Host Interface Equipment Shelf

FSP — Frame Supervisory Panel

RLM — Remote Line Module RLC — Remote Line Module Controller

LD — Line Drawer

FSP — Frame Supervisory Panel

RLCM — Remote Line Concentrating HIE — Host Interface Equipment
Module
LCM — Line Concentrating Module

RMM — Remote Maintenance Module

FSP — Frame Supervisory Panel

RME — Remote Miscellaneous FPA — Fuse Panel “A” Feed
Equipment
FPB — Fuse Panel “B” Feed

FSP — PDC FSP

FSP — MISC FSP

XXX — For Miscellaneous Equipment

Shelves

FP — Filter Panel
RSE — Remote Service Equipment RSM — Remote Service Module

FSP — Frame Supervisory Panel

XXX — Miscellaneous Equipment

Shelves
—continued—

DMS-100 International Technical Specification BCS40i and up

12–6 Equipment

Table 12–1
DMS-100 family bays and corresponding shelves/drawers (continued)
Bays Shelves/drawers

SLC — Speech Link Connecting (or PSL — Peripheral Speech Link

SLCC) Connecting

NSL — Network Speech Link

Connecting
SME — Subscriber Module Equipment SMR — Subscriber Carrier Module

CU — Cooling Inverter Unit

FSP — Frame Supervisory Panel

TME — Trunk Module Equipment TM8, 4, 2 — Trunk Module 8-, 4-,
2-wire (see Chapter 5)

MTM — Maintenance Trunk Module

FSP — Frame Supervisory Panel

AXU — Office Alarm X-Connect

Note: Maximum of 5 Trunk Modules per frame only if:
a) All are TMs
b) 0 4 are TMs and 1 is an MTM
c) 1 is an MTM and another is an AXU. Maximum of 4 Trunk
Modules for all other combinations.

End

A DMS-100 Family system usually has one or more Maintenance and

Administration Positions (MAP) equipped with a Visual Display Unit
(VDU), Logic series keyset, jacks, and an optional printer.
All frames, with the exception of Speech Link Connecting (SLC), Digital
Network Interconnecting (DNI), Maintenance Spare Storage (MSS), and
Maintenance Storage Cabinet (MSC) are equipped with a Frame
Supervisory Panel (FSP) designed specifically for the control and
monitoring of the equipment in the frame.
A multiple fan unit is designed for use in the central control and network
frames which require forced-air cooling. The cooling unit mounts at the
bottom of the frame, occupying a single shelf space. Fan failure detection is
provided. With the exception of the fan cooled LGE, LTE, MS6E, MS7E,
RCE, SME, and DTE, the peripheral equipment is convection cooled.
Internal DMS-100 Family system cabling is totally implemented with
connectorized cable using 26 AWG twisted pairs. Cabling to the MDF uses

PLN-5001-001i Standard 02.02 April 1997

 Equipment 12–7

standard cables connectorized at the DMS-100 Family side, and either

connectorized or loose at the MDF side depending upon the DF block used.
Cable distances between the network and peripheral modules are limited to a
750 feet (228.6 m) maximum; between network and central message
controller they are limited to a 200 feet (60.96 m) maximum. Power
distribution cables are not connectorized. It is not possible to reverse or
incorrectly mate the two halves of a biased connector. Also, all connectors
have adequate space between adjacent connectors or other units to allow a
firm grasp on the associated plug for removal.
A common type of shelf, with the exceptions shown in table 12–2, is used
for mounting printed circuit cards throughout the DMS-100 Family system.
There are 24 inches (610 mm) of usable space between the side plates of the
shelf. The common shelf has these dimensions: height 14 inches (356 mm),
width 25 inches (635 mm), and depth 12.5 inches (318 mm).

Table 12–2
Shelf heights
Shelf Inches Millimeters

Frame Supervisory Panel (FSP) 5.0 127

Metallic Test Access (MTA) 7.0 178
Inverter (INV) 5.0 127
Recorded Announcement Module (6 channels) 13.0 330
Recorded Announcement Module (12 channels) 21.0 533
Magnetic Tape Drive (MTD), DPP, BMC, Stratum II 28.0 711
ROS
Peripheral Speech Link Connecting Panel 3.5 89
Network Speech Link Connecting Panel 3.5 89
DNI Panels 3.5 89

All printed circuit boards measure 12.5 inches (317 mm) high and 10 inches
(254 mm) deep except miscellaneous alarm Printed Circuit Boards (PCBs)
(which are about half the height), first generation line circuit PCBs (which
are 4 inches [102 mm] by 4 inches [102 mm]), and second generation line
circuit PCBs (which are 3 inches [76 mm] by 3.5 inches [89 mm]). All
PCBs with the exception of the line circuit have face plates of suitable
widths. Both single and double sided PCBs are used.
Circuit pack extenders are provided for PCBs that can tolerate the additional
time delays imposed. Extenders can swivel through a 180-degree arc.
Circuit pack extenders are not provided for all units, such as high-speed
logic circuits, that cannot tolerate extra distance.

DMS-100 International Technical Specification BCS40i and up

12–8 Equipment

The alignment guides for installing circuit packs in a shelf or drawer allow
for considerable misalignment while attempting to seat a circuit pack
without causing equipment damage. Wherever possible, quick-fasten
devices (rather than bolts or screws) are used for all replaceable units.
The heads of fastening devices for all mounted units are accessible with a
standard screwdriver.

Equipment frames
A single-bay frame has been designed and used throughout the DMS-100
Family system. In some cases (for example, CCC), two bays are fixed
together to form a double-bay frame.
Frame structure members do not impede normal maintenance access or
removal of frame component modules or subassemblies.
EMI hardware, mounting hardware, cabling hardware, and rear panels are
provided for a given bay configuration and are normally shipped loose. This
equipment is provided in addition to the basic framework.
Equipment frame dimensions
All NT40 based DMS-100 Family equipment frames use an identical
framework assembly with specific dimensions:
Depth: 18 inches (457 mm)
Width: 27 inches (686 mm)
Height: Framework only 84.0 inches (2.13 m)
Overframe Cable Duct 10.0 inches (254 mm)
Cross-Aisle Cable Duct 7.1 inches (180 mm)
Subtotal 101.1 inches or 8′5″ ± 1″ (2.6 m ± 25 mm)
Ladder Type Cable Rack 12.0 inches (304 mm)
(Top is 9′ 4″ (2.8 m from floor)
Total 113.1 inches (2.9 m)
Recommended clear ceiling height is 132 inches (11 feet). Minimum clear
ceiling height is 120 inches (10 feet).
The level above the 101.1 inches or 8′5″ (2.6 m) is reserved for the ladder
type cable rack which is normally used for cabling to the Distributing Frame
(DF), transmission systems, and power distribution.
The DMS SuperNode equipment frame has specific dimensions:
Depth: 24 inches (610 mm)
Width: 42 inches (1.1 m)
Height: 72 inches (1.8 m)

PLN-5001-001i Standard 02.02 April 1997

 Equipment 12–9

Equipment frame lineups

Frames intended for use in lineups comply with six requirements:
• Frames are designed to allow side-by-side assembly into straight lineups.
A nominal clearance of 1/16 inch (1.6 mm) is to be provided between
adjacent frames.
• No part of any frame, structure, or equipment normally attached to the
frame extends horizontally beyond the base of the frame.
• All frames in a lineup are of the same depth. The front edges of all
frames are in line.
• All frames are provided with means for attachment to a concrete floor.
This includes provision for relocation of such means of attachment if
interference occurs with the reinforcing rods in the concrete floor. Note
that with some earthquake reinforcement arrangements this flexibility is
not available.
• Means are provided to level and plumb all frames and to compensate for
variations in floor flatness:
— Floor Levelness
— Maximum deviation from the elevation established for the floor must
not exceed plus or minus one (1) inch over the entire floor area and
the maximum difference in elevation between the high and low
points in any building bay must not exceed 3/4 inch (19 mm).
— Floor Flatness
— Maximum deviation from a true straight edge 8 feet (2 m) in length
placed anywhere on the floor must not exceed 1/4 inch (6.4 mm).
• Except as otherwise noted, full frame lineups will be located to provide
straight cross aisles. The width of cross aisles will be such that
movement of equipment frames during installation is not restricted.
Equipment frame loading and support
The floor loading of fully equipped DMS-100 Family bays, including frame
supporting cabling, averages 80 pounds per square foot (3.38 kilonewtons
per square meter). An additional allowance of 10 pounds per square foot
(0.423 kilonewtons per square meter) for ceiling supported cabling of the
floor below should be included in multi-floor switching buildings. An
allowance of 10 pounds per square foot (0.423 kilonewtons per square
meter) should also be added for personnel and transient loads. The total
floor loading in a multi-floor building is 100 pounds per square foot
(4.2 kilonewtons per square meter).
DMS-100 Family frames do not require any additional external supports
other than the floor bolts. Both the overframe and the cross-aisle cable ducts
are supported solely by the DMS-100 Family frames in a non-earthquake
office. Cross-aisle cable ducts are not used in earthquake offices.

DMS-100 International Technical Specification BCS40i and up

12–10 Equipment

Equipment frame earthquake resistance

To cover the Applied Technology Council (ATC) seismic zones 1 through 7,
two levels of earthquake protection are provided by the DMS-100 Family
systems: the reinforced base frame (NT0X25AH), and the reinforced base
frame and mechanical bracing frame (NT0X25AJ).
The ATC seismic zones 1 through 7 correlate with the Bellcore zones 1-4:
Seismic Zone Bellcore
ATC (NEBS)

1 1
2
3 2
4 3
5 3
6 4
7 4

The type of earthquake protection required is dependent on the building size,

total number of floors, floor location of the DMS-100 Family system, and
the ATC zone.
Table 12–3 shows typical earthquake protection requirements for the seven
ATC zones. The number of stories is equal to the number of floors, with a
basement considered as an additional floor, or story.

Table 12–3
Earthquake bracing requirements
Where in Building Equipment is Installed
ATC Zone Ground Section Mid Section Top Section

5, 6, 7 E M M
3, 4 E E M

PLN-5001-001i Standard 02.02 April 1997

 Equipment 12–11

Table 12–3
Earthquake bracing requirements
ATC Zone Ground Section Mid Section Top Section

1, 2 E* E* E
Note: E — The reinforced base frame is required.
M — The reinforced base frame and mechanical bracing frame are
required.
E* — NT0X25AA Earthquake Framework assembly is recommended.

Definition of Floor Level:

Top Floor = Top 45% of the total floors.

Section

Mid Height = The floors below the top section, comprised

Section of 26% of the total number of floors.

Ground Section = Remaining lower stories.

Basement is considered a floor.

A floor plan study will be conducted with the operating companies, on

individual sites, to determine the earthquake protection requirements.
Cables entering or leaving an equipment row must be given a minimum of
6 inches (152 mm) of slack to allow for relative motion between equipment
rows, and a minimum of l2 inches (305 mm) of slack to allow for relative
motion between a row and foreign cable securement (for example, pick up
cable racks which are secured to the ceiling).
The slack must be situated at the entry and exit points wherever there will be
a change of relative motion. It is not necessary to add l2 inches (305 mm)
every time a DF cable crosses a row if it does not enter that row and is
independent from the row.
Frame lineup length restrictions for zones and locations requiring the use of
the reinforced frame but not the mechanical frame are a minimum of three
frames and a maximum of eight. This cluster of eight frames may be
continued in a lineup as required, with the restriction that there is to be a
minimum of an eight-inch gap (a 12-inch [305-mm] gap is the standard)
between each cluster and a minimum of a 12-inch (305-mm) slack in the
cables.
For zones and locations requiring the reinforced frame and the mechanical
frame, the maximum lineup is seven frames including the mechanical frame.

DMS-100 International Technical Specification BCS40i and up

12–12 Equipment

This cluster may be continued in a line if the gap and cable restrictions are
met.
For all installations, DMS-100 frames should be located at least one foot
from walls, posts, or pipes. Any foreign equipment which is not earthquake
braced should be located away from DMS-100 equipment at a distance at
least the foreign equipment height plus one foot.

Equipment frame floor plans

Host office floor plans
Figure 12–1 on page 12–13 shows a typical floor plan for a 25 000 line,
5000 trunk DMS-100 Family system. This office occupies two 20 foot (6.1
m) X 20 foot (6.l m) building bays. The figure shows the CORE equipment
(Central Control and I/O subsystems) located next to the maintenance area,
with the network and peripheral frames capable of growth (as indicated)
horizontally or vertically.
The maintenance area contains the maintenance and administrative positions
which provide a person-machine interface with the DMS-100 Family
system. The area contains a MAP configured for system maintenance, four
Line Test Positions (LTP) and a MAP configured for a Trunk Test Position
(TTP). The MAP consists of a VDU with keyboard, and a LOGIC key
telephone set for voice communications. The physical position of the MAP
equipment is flexible and can be located anywhere within the maintenance
area or within 1200 cable feet (366 m) of the CORE for local operation.

PLN-5001-001i Standard 02.02 April 1997

 Equipment 12–13

Figure 12–1xxx
Typical floor for 25 000 line, 5000 trunk DMS-100 office

20’-0” 20’-0”

Growth Cable slot

01 03 + +
V30

3’-0” MIS
LCE LGE PDC LCE
15 17 04 05 03 18 19
5’-0”
Main distributing frame

02 03 12 14 02 002 1-00 1-01 1-02

3’-0”

LGE LCE PDC TME SLC NETC

20’-0”

LCE TME SLC NETC

V
H

06 11 001 0-00 0-01 0-02

5’-0”

29’-3”
00 01 03 05 01 000 1-00 1-01 03 06
LGE LCE PDC TME DNI NETC
3’-0”

LCE MIS PDC NETC DNI NETC

00 02 + 00 00 00 0-00 0-01 01 02 +
5’-0”

3” Growth
V1

00 01 0-00 0-00 1-00 1-00 00 01 00 04

IOE MEX CCC MEX MSS DTE
8’-6”
Printers
0 1 2 3
MAP TTP

8’-0”
Maintenance area

LTP
0 1 2 3
Legend:
Maintenance aisle PDC Power distribution DTE Digital trunk equipment
center
CCC Central control complex LCE Line concentrating equipment
SLC Speech link
MEX Memory extension connecting LGE Line group equipment

NETC Network combined MIS Miscellaneous LTP Line test position

IOE Input/output equipment MSS Maintenance spare TTP Trunk test position
storage
DNI Digital network interconnections
TME Trunk module
equipment

Figure 12–2 on page 12–15 shows cable duct information:

• Cross Aisle Cable Duct

DMS-100 International Technical Specification BCS40i and up

12–14 Equipment

• Cable Trough Location

• 15″ & 20″ Ladder Cable Racks at 9′ 4″ Level
• Office Cable Routing
The DMS-100 Family System has specific cable length restrictions:
• The total length of any cable run between a central control complex
frame and a network frame shall not exceed 200 feet (61 m). The cable
length from a DNI frame and its associated network frames shall not
exceed l00 feet (30 m).
• The total length of any cable run between a peripheral equipment frame
and a network frame shall not exceed 750 feet (229 m).
• The total length of any cable run between an Input/Output equipment
frame housing an Input/Output Controller (IOC) shelf and a
Miscellaneous equipment frame housing a modem shelf shall not exceed
50 feet (15 m). The direct cabling distance between the IOC shelf and
any I/O terminal device shall not exceed 50 feet (15 m).
• The total length of any cable run between the CPU of a central control
complex frame and the last DS of a Memory Extension frame shall not
exceed 40 feet (l2 m).
• The total length of power cable run between a power distribution center
frame and any peripheral equipment frame is dependent on the
equipment fusing (20, 10, 5 amperes) and cable size.

PLN-5001-001i Standard 02.02 April 1997

 Equipment 12–15

Figure 12–2xxx
Typical cable duct and cable rack layout

20” ladder 15” ladder

cable cable
rack (9’-4”) rack (9’-4”)
01 03 +
MIS
LCE LGE PDC LCE
15 17 04 05 03 18 19
A
02 03 12 14 02 002 1-00 1-01 1-02
LGE LCE PDC TME SLC NETC
LCE TME SLC NETC
06 B 11 001 0-00 0-01 0-02
A

00 01 03 B 05 01 000 1-00 1-01 03 06

LGE LCE PDC TME DNI NETC
LCE PDCNETC DNI NETC
00 02 00 00 00 0-00 0-01 01 02

00 01 0-00 0-00 1-00 1-00 00 01 00 04

IOE MEX CCC MEX MSS DTE

Cross aisle duct

20” ladder cable rack (9’-4”) 8’ - 5” ± 1”
Over-frame
trough
7’-1” 10”
10”
7’-1” ± 1”
7’-1” ± 1”
7’-1” ± 1”
Section A-A (N.T.S.) Section B-B (N.T.S.)

Notes:
1 Single line denotes cross aisle cable duct

2 Denotes cable rack

DMS-100 International Technical Specification BCS40i and up

12–16 Equipment

Remote office floor plans

Remote line concentrating module (RLCM)
Figure 12–3 on page 12–16 shows a typical floor plan for a 640 line
DMS-100 Family Remote Line Concentrating Module (RLCM) office with
growth capabilities to 1920 lines. The RLCM offices, including a wall
mounted MDF and dc power, occupy an area of 12 feet (3.66 m) X 17 feet
(5.18 m).
Figure 12–3xxx
Typical floor plan for a 640 line DMS-100 family RLCM office

1’–6”
MDF (9’–0”)
3’–0”
Min.

Legend:
2’–0” 6’–9” 3’–3”
RLCM Remote Line Concentrating
1’–6”

Module

02 01 00 ORB Office Repeater Bay

(operating company)
3’–0”

RLCM RLCM
PWR BD Power Board
(operating company/NTI)
1’–3”

PWR
ORB MDF Main Distributing Frame
BD.
(operating company)
3’–0”
Min.

Maintenance Aisle
1’–9”

Battery

PLN-5001-001i Standard 02.02 April 1997

 Equipment 12–17

There is no maintenance area contained in this configuration since the MAP

located at the host office provides the necessary person-machine interface
for the DMS-100 Family RLCM system.
Figure 12–4 on page 12–18 shows in detail the cable information for the
RLCM:
• cable trough location
• ladder cable rack
• office cable routing.

The total length of power cable run between a PDC frame and any remote
line concentrating module frame shall not exceed 41 feet (12.5 m).

DMS-100 International Technical Specification BCS40i and up

12–18 Equipment

Figure 12–4xxx
RLCM typical cable duct and cable rack layout

V–1 MDF (9’–0”) V–8

Ladder cable rack (9’–4”)

02 01 00

RLCM RLCM

PWR
ORB
BD.

Ladder cable rack (9’–4”)

Battery
Over-frame
trough

10”
Notes:

7’–11” ± 1”
Denotes ladder type cable rack
7’–1” ± 1”
Ladder cable rack (9’–4”)

Section A-A (NTS)

Remote switching center (RSC)

Figure 12–5 on page 12–19 shows a typical floor plan for a 1280 line
DMS-100 Remote Switching Center (RSC) office with growth capabilities
to 5760 lines. The RSC offices, excluding a wall mounted MDF and dc
power, occupy an area of 12 feet (3.66 m) X 12 feet (3.66 m).
There is no maintenance area contained in this configuration since the MAP,
located at the host office, provides the necessary person-machine interface
for the DMS-100 Family RSC.

PLN-5001-001i Standard 02.02 April 1997

 Equipment 12–19

Figure 12–5xxx
Typical floor plan for a 1280 line DMS-100 family RSC office

1’–6”
MDF (9’–0”)
V1 V8

3’–3” 11’–3”

3’–0”
Min.
1’–6”
00 00 00 01 02

RME RCE LCE

6’–0”

3’–0”
LCE

1’–6”
PWR 03 04
ORB
BD.

3’–0”
Min.
1’–9”
Battery

Figure 12–6 on page 12–20 shows the RSC cable information:

• Cable trough location
• Ladder cable rack
• Office cable routing.

DMS-100 International Technical Specification BCS40i and up

12–20 Equipment

Figure 12–6xxx
RSC typical cable duct and cable rack layout

MDF (9’–0”)
V1 V8

15”L
3’–3” (9’–4”)

00 00 00 01 02

RM E RCE LCE

LCE
P WR 03 04
ORB
B D.

12”L
(9’–4”)

Battery

Outside plant module (OPM)

The Outside Plant Module (OPM) is a package DMS-100 RLCM.
Switching specifications are the same for the OPM version as for the
RLCM. The most significant feature of the OPM is that the packaging
allows it to be mounted on a concrete pad as outside plant equipment. The
OPM design includes a weatherproof cabinet with an environmental control
system to allow this exterior placement.
The OPM cabinet is 66 inches (1676 mm) wide, 66 inches (1676 mm) high,
and 26 inches (660 mm) deep. It is constructed primarily of 13 gauge steel,
ribbed for added strength, and is epoxy laminated for scratch resistance. A
fully equipped cabinet, including electronics and batteries, weighs
approximately 2200 lb (1000 kg). A view of the OPM interior layout is
shown in figure 12–7.

PLN-5001-001i Standard 02.02 April 1997

 Equipment 12–21

The OPM cabinet is composed of the main compartment and the end access
compartment.
The main compartment houses the re-packaged RLCM, ac breakers,
rectifiers, batteries, and environmental control system. The compartment is
accessed from the front of the cabinet via a pair of doors. The majority of
the equipment is housed on a pair of swing-out, double-latched, hinged bay
frames. The hinged bays allow access to both the rear of the shelves and to
additional equipment positioned against the back wall of the cabinet.
The end access compartment, physically isolated from the main
compartment, houses protection, termination, and cross-connection
equipment. Access is provided via a single door.
The doors of the cabinet are hinged with recessed lock pins and are provided
with padlocking facilities. For security purposes, cabinet door alarms are
provided.
Each hinged equipment frame contains three shelves of equipment. Four of
the shelves within the swinging bays are occupied by the RLCM equipment
consisting of a dual-shelf LCM, an RMM, and a Host Interface Equipment
(HIE) shelf.
The remaining two shelves consist of an FSP which includes office
repeaters, a Power Control Unit (PCU) for ac power, a rectifier system
consisting of a pair of rectifiers, and a battery control unit. An
Environmental Control Unit (ECU) is located at the bottom of each bay.
The battery strings, ac entrance panel and optional test equipment are
contained in fixed bays located behind the swing-out equipment bays.
Outside plant and power cables enter the cabinet at the left end of the cabinet
base. Outside plant cable and termination is provided on the Service
Protection Center (SPC) located in the end access compartment. The outside
plant cable protection consists of both VF and DS-1 line protection. VF line
protection is provided by carbon protector modules. DS-1 line protection is
provided by gas tube protector modules.
Protection for 640 subscriber VF pairs and termination for 675 pairs is
always provided. Optionally, an additional 1375 pair termination may be
added, which will allow the end access compartment to serve a cross
connection function.
The environmental control system regulates the environmental conditions in
the main cabinet compartment to protect the OPM electronics. The OPM is
designed for operation within an ambient temperature range from 5°C
(40°F) to +40°C (104°F) and a relative humidity range from 5 to 99%.

DMS-100 International Technical Specification BCS40i and up

12–22 Equipment

Figure 12–7xxx
Outside plant module — interior view

Fuse
alarms

LCA:1
React. 1
BCU
33 XXX PCU 39
panel
LCA:0 32

NTBIX
NTBIX
React. 0
19
FSP 28
HIE:XXX

5 RMM:XXX 19
ECU:XXX

0 5
ECU:XXX

Bay 0 0

Bay 1

BCU – battery charging unit

ECU – environmental control unit
PCU – power control unit
Rect.– rectifier

Floor plan data

Table 12–4 on page 12–23 shows the specific planning parameters for each
type of subsystem.

PLN-5001-001i Standard 02.02 April 1997

 Equipment 12–23

Table 12–4xxx
Floor plan data

Heat Approx
Sub Type of frame Abbrev. DC fuse Typical weight
syst dissip. rating current
watts/hr kg lb
Message switching 6 1050 MS6E 6–20A 23A 227 500
equipment 2–5 A
Message switching 7 650 MS7E 6–20A 15A — —
equipment 2–5 A
Inverter
Peripheral

Trunk module equipment 480 TME supply 12A 227 500

2–20A
Digital carrier equipment 575 DCE 2–20A 12A 227 500
Line concentrating 1050 LCE 8–20A 23A 227 500
equipment
Line group equipment 980 LGE 4–20A 20A 227 500
Digital trunk equipment 1120 DTE 4–20A 20A 227 500
Line trunk equipment 1120 LTE 4–20A 22A 227 500
Double shelf network 600 DSNE 4–10A 14A — —
equipment 2– 5A
Network

Network combined frame 1000 NETC 2–20A 22A 285 630

2– 5A (total)
Speech link connecting N/A SLC Nil Nil 159 350
Digital network N/A DNI Nil Nil 136 300
interconnecting
4–20A 25A
Central
Control

Central control complex 1720 CCC 545 1200

2– 5A (total)
Memory extension 850 MEX 4–20A 19A 273 600
(total)
2–20A
Magnetic tape center 670 MTC 1 – 10 per 15A 273 600
shelf
I/O

Input/output equipment 850 IOE 4–20A 273 600

Miscellaneous equipment
(rec. ann-machines, 220 MIS 20A 5A 273 600
modems, etc.)
Power distribution center 200 PDC 2–600A Varies 227 500
Maintenance spare storage N/A MSS Nil N/A 136 300
Remote line module 1000 RLM 2–20A 25A 454 1000
(double bay) per bay (total)
Other

Remote service equipment 385 RSE 2–20A 8A — —

Remote line 1360 RLCM 4–20A A – 20A 227 500
concentrating module B – 17A
Remote concentrating 1000 RCE 3–20A 22A — —
equipment
Subscriber module 1120 SME 4–20A 20A 227 500
equipment

DMS-100 International Technical Specification BCS40i and up

12–24 Equipment

Floor plan requirements

Within the general equipment grouping, more detailed arrangements are
considered:
• The MEX frame(s) must be located adjacent to the CCC frame of the
same plane.
• The IOE frame should be located as close to the CCC frame as possible.
• The MIS frame (housing the modem shelf) should be located as close to
the IOE frames as possible.
• The SLC frames for each plane must be grouped together in the same
lineup within the network area but as close to the peripheral area as
possible.
• The DNI frames for each plane should be located as close and as central
to the network frames of the same plane as possible.
• The MSS frame should be located near the core area or maintenance area
if possible. If there is a need for more than one MSS frame, then
subsequent ones can be placed in the peripheral area.
• All network frames should be centralized in one area, while peripheral
equipment, such as DCE, DTE, LGE, LCE, and TME frames, can be
placed in more than one area (or on a separate floor) if the cabling
restrictions are observed.
• DCE or DTE frames, rather than TME frames are recommended to be
mixed with Network (NETC) frames if the need exists.
• The SLC and DNI frames can be arranged facing each other, if floor area
permits, and to alleviate cable congestion. Frames associated with
different planes should be in different lineups.
• All RLM frames in a remote site should be located as near as possible to
the RSE frames in order to meet cabling restrictions.
Distributing frame
The distributing frame is furnished by the operating company; therefore, the
physical properties are dependent upon the actual frame chosen.

DC power equipment
The DMS-100 Family dc power equipment is furnished by the operating
company. Current drains for the different DMS-100 Family bays and frames
are supplied to the operating company for determining the size of the power
plant and rectifiers on a per-site basis.
Power distribution center
The power distribution center is described in Chapter 13 of this document.

PLN-5001-001i Standard 02.02 April 1997

 Equipment 12–25

Cable distribution
In DMS-100 Family systems, the overframe cabling duct is provided as part
of the standard equipment frame. Earthquake protection is provided as
described in Equipment frame earthquake resistance on page 12–10.
The cable duct is raised from the framework 4 inches (102 mm) to facilitate
ventilation of the equipment mounted on the framework.
DMS-100 Family cable is routed in a frame modular cable trough as shown
in figure 12–8 on page 12–26. The compartments are designed to provide
functional separation for the various cables, and to minimize
electromagnetic interference between digital, analog, and power circuits. A
cross-aisle duct, whose section is somewhat similar, is available to distribute
cable between aisles.
The cable assigned to the different compartments varies with the equipment
lineup. Figure 12–8 shows the preferred standard. However, if it is
necessary to mix peripheral equipment types within a lineup, some care is
necessary to separate digital and analog cable, or cables for which there is
danger of cross-talk interference. The cable trough is sectioned with metal
dividers separating the digital cables from the analog to reduce such
interference.
The sectional area of the overframe cable duct is designed to accommodate
the worst case cable cross-section for an l8 frame lineup. It is expected that
for normal office layouts the trough capacity will not be limited by the
cross-section area, but by the need to segregate various cable types if
peripheral equipment is mixed within a lineup. Should such situations arise
cable may be rerouted with cross-aisle ducts.
A trough is available to bridge single frame gaps within a lineup without
requiring stanchion or empty framework. Building columns require
cross-aisle ducts to route cable to the continuation of the lineup. Cabling to
DF, power, and other switching systems running perpendicular to the
equipment lineups, are distributed in overframe via ladder cable racks. No
provision has been made to route alarm and other miscellaneous signals,
which are usually connected directly between the Frame Supervisory Panels
(FSP) in each frame.

DMS-100 International Technical Specification BCS40i and up

12–26 Equipment

Figure 12–8xxx
Cable trough assembly

(See inserts)

6” 6” 2.4” 3” 6” 6” 2.4” 3”

Digital

Power
6”

6”
Analog Analog
18”

4”
7’–1”±1”

Rear of Rear of
framework framework

Inserts
CC cabling
Digroup

(digroup)
Power

DNI SLC Power

Analog Analog
cabling cabling

LCE lineup NETC lineup

Building provisions
Ceiling height
A minimum clear ceiling height of 10 feet (3 m) is recommended for the
DMS-100 Family switching system. The recommended clear ceiling height
is 11 feet (3.4 m).
Building ceiling supports
Building ceiling supports are not required for DMS-100 Family equipment
frames or intra-switch cabling. Cable racks for cabling to MDF, power, and

PLN-5001-001i Standard 02.02 April 1997

 Equipment 12–27

other equipment (for example, ladder-type cable racks) are not supported by
the DMS-100 Family frames and require ceiling supports.
Column and cable hole spacing and arrangements
Due to the compactness of the DMS-100 Family systems, column and cable
hole spacing and arrangements are not critical and flexible floor plan layouts
may be engineered to accommodate various arrangements as required.
Frame handling and door openings
Frames in the DMS-100 Family can be handled in a vertical or horizontal
position provided that when they are lying horizontal, they are positioned on
their side, not on the front or back. Each frame must be kept fully packed, to
avoid damage, until it reaches the office floor location.
Hoisting Tool No. ITA-9938 can be used to hoist equipment frames in a
horizontal position.
Crated frames are 7 feet 5 inches (2.26 m) high, 2 feet 5 inches (.74 m) deep,
and up to 5 feet 6 inches (1.68 m) wide. To accommodate hoisting fixtures,
the recommended equipment entrance door opening into the building should
at least be 5 feet (1.5 m) wide by 10 feet (3 m) high. Within the building,
the uncrated frames on shipping dollies require an equipment entrance door
opening of 3 feet (.91 m) wide by 8 feet (2.4 m) high.
Air conditioning
The size of the building area housing the DMS-100 Family system, the
building insulating properties, the climatic condition, the interior airflow and
the size of the system itself all influence the air conditioning requirements.
The heat to be dissipated in DMS-100 Family systems per square foot
averaged over the equipment room floor area is 40 watts. This is for
DMS-100 Family switching equipment only. Other factors, such as the
number of maintenance personnel, have to be taken into consideration to
calculate the overall heat to be dissipated.

Environment
Ambient temperature and humidity
The DMS equipment, including remotes, is designed for operation within the
ambient temperature and relative humidity ranges shown in table 12–5:

DMS-100 International Technical Specification BCS40i and up

12–28 Equipment

Table 12–5xxx
Ambient temperature and humidity
Normal Short Term
(Note 1) (Note 2)

Ambient Temperature: 50°F to 86°F 40°F to 120°F

10°C to 30°C 5°C to 49°C
Relative Humidity 20% to 55% 20% to 80%
(Non-condensing):
Atmospheric Pressure: 523 mmHg (69.2 KPa) corresponding to 10 000 feet
(3048 m) of altitude
Note 1 : Operation in the temperature range 40°F – 100°F (5°C – 38°C), are
permissible if the monthly average for the upper range does not exceed 86°F
(30°C). All performance and reliability parameters are met in this temperature
range. Relative humidity of 80% is allowed at an ambient temperature that
cannot exceed 70°F (21°C). At an ambient temperature of l20°F (49°C), the
maximum allowable relative humidity is 30%.
Note 2 : Short term is defined as 72 hours continuous and l5 days maximum per
year.

Temperature and humidity are measured at a point 5 feet (1.254 m) above

floor level and mid-aisle, or 15 inches (381 mm) in front of the equipment
(whichever is smaller). Rate of change should not exceed l5°F (6.7°C) per
hour.
Heat dissipation
The heat dissipation of DMS-100 Family switch averaged over the
equipment room floor area and over 24 hours will not exceed 80 W/sq. ft
(86l W/sq. m). Table 12–4 on page 12–23 gives the maximum quantity of
heat to be dissipated per frame, assuming that each frame is fully equipped.
Air cleanliness
DMS-100 Family equipment functions indefinitely in an ambient air having
a cleanliness standard no higher than class l00 000.
Classes are defined as the number of particles of 0.5 microns and larger, per
cubic foot.
Fire resistance
The DMS-100 Family System is designed using materials and techniques
consistent with good design practice reflected in the telephone industry.

PLN-5001-001i Standard 02.02 April 1997

 Equipment 12–29

PCB design
Northern Telecom Procurement Specification 25001 on Printed Circuit
Boards restricts all PCB laminated material to NEMA Ll-l Grade FR-4
epoxy glass material.
Each printed circuit board is marked to indicate that the material passed the
UL flammability test (UL 94 V-0).
Structural material
All structural material, including the PCB and backplanes, have an oxygen
index of 28% or greater, and a 94 V-0 rating as determined by Underwriters
Laboratories standard 94 test for flammability of plastic materials.
Component selection
All components are selected to meet the appropriate IEC needle flame test.
Wire and cable
Wire and cable used throughout the DMS-100 Family of products meet
ASTM D2633 requirements for thermoplastic insulation and jacketed wire
and cable.
Transportation and storage environments
Transportation
DMS-100 Family equipment packaged for transportation is capable of
enduring the rigors of shipping via truck, rail, sea, or air. The environmental
conditions during transportation must not exceed specifications:
• Ambient Temperature: –40°F (–14°C) to 160°F (71°C)
• Humidity: 10% to 95%; max water vapor pressure not to exceed
25 mmHg
• Vibration: up to 3.5 g at 5 Hz to 500 Hz
• Shock: equivalent to a 6-inch (152-mm) drop for a 1000-lb (454-kg)
equipped bay
Storage
DMS-100 Family equipment may be stored packed in a sheltered
environment under specific environmental conditions:
• Ambient Temperature: –40°F (–14°C) to 160°F (71°C)
• Humidity: 10% to 95%; max water vapor pressure not to exceed
25 mmHg.

Grounding
The use of ac coupling for signal leads, together with input-output isolation
of ac to dc converters, essentially eliminates the need for a ground window.
In the DMS-100 Family, the battery return, signal ground, and frame ground

DMS-100 International Technical Specification BCS40i and up

12–30 Equipment

are separate entities although they are brought to the same dc potential. See
Cable distribution on page 12–25 for physical grounding arrangements.
AC coupling
AC coupling is employed between the central message controller and
network, and between network and peripheral equipment. This ac coupling
refers only to the signal leads. Network and peripheral frames need not be
insulated from the floor unless they form part of the CPU lineup.
DC coupling
The CPU, associated memory, and the central message controller are all dc
coupled. These units are considered for grounding purposes as a single
group entity. All frames in a lineup that contains this entity must be
insulated from foreign grounds.
Frame ground
A frame ground bus is bonded to each frame in the lineup at the top. The
bus terminates at the PDC frame ground which is also the battery return
ground.
The PDC frame ground bus of all PDCs are bonded together and connected
at one point to the central office ground for that floor for a dedicated power
plant, or to the battery ground reference point for a shared power plant.
Framework isolation
The equipment lineup that contains the CCC module must have all
framework isolated from any ground other than framework ground. This
isolation of frames prevents possible malfunction of memory shelves due to
electromagnetic fields which may be generated if an unusually large fault
current was allowed to flow through the CCC framework.
DMS-100 Family frames not in the CCC module lineup need not be isolated
from other grounds. Isolation may be specified by the operating company
during the engineering period, if local arrangements so require.
Signal ground
Advantage is taken of the printed circuit backplane construction to isolate
the signal ground on a per-shelf basis. A single ground connection is taken
from the signal ground of each shelf and all of them connected to a single
bonding point of the frame ground stop at that frame. Exceptions to this rule
are in the central control complex and the MSB, where all signal grounds
from the shelves are connected to a single point on the frame ground bus for
all the frames in the central control complex.

Illumination
Lighting levels are provided and maintained in the DMS-100 Family System
so as to afford satisfactory and safe working conditions at all times. To this

PLN-5001-001i Standard 02.02 April 1997

 Equipment 12–31

end, two types of lighting are provided in the DMS-100 Family on an

optional basis, via normal lighting and low intensity lighting (for emergency
conditions).

Electromagnetic interference
Electromagnetic emissions
The system, with available options, conforms to the emission requirements
of the Federal Communication Commission (Part l5, Subpart J). Frames are
available which are in compliance with FCC regulations for location on
customer premises.
Radiated susceptibility
The system shall not exhibit any malfunctions or be degraded beyond its
specified tolerances when subjected to electric field strengths of 5 V/m or
less, root-mean-square value corresponding to the peak of the envelope, if
modulated, over the frequency range 10 kHz to 10 GHz.

Audio noise emissions

Maximum sound levels produced by equipment to be located in power
rooms or special sound tested areas shall not exceed 85 dBA. Maximum
sound levels for all other equipment shall not exceed 75 dBA.

Miscellaneous
Hardware
In addition to the DMS-100 Family equipment bays, other equipment may
be supplied as requested for testing purposes. This equipment is shown in
Table 12–6 on page 12–31.

Table 12–6xxx
Additional equipment
Description Code

Echo Return Loss Measuring and Wiltron

Singing Point Measuring Set Model 904l
Digital Multimeter with Battery Fluke
(Including Battery Eliminator) Model 8010A–01
Multimeter Test Lead Set Fluke
Model Y8134
Multimeter Carrying Case Fluke
Model Y8205
Test Cord (310 to 309) ADC
6′ Long Telecommunication
Model PJ–955
—continued—

DMS-100 International Technical Specification BCS40i and up

12–32 Equipment

Table 12–6xxx
Additional equipment(continued)
Description Code

Test Cord (309 to 309) ADC

3′ Long Telecommunication
Model 4–15195–0030
Test Cord (310 to 360) Northeast Electronics
6′ Long Model 2W–17A
Cord Set Assembly Northeast Electronics
Model 931800–100
Universal Signaling Sender Northeast Electronics
Model TTS59C
DP/MF/DTMF Signaling Display Northeast Electronics
Model 2763
Test Cord (309 to 310) ADC
2′ Long Telecommunication
Model PJ–953
Transmission and Noise Measuring Set Northeast Electronics
Model 4002
T–1 Repeater Slot Extender Northeast Electronics
Model 7015
Pulse Signaling Test Set Northeast Electronics
Model 1260–A
PCM Span Repeater Test Set Northeast Electronics
Model 7040
4.5 Digit DMM W/Rech Batt Fluke
8050A–01
Local Test Cabinet Northern Telecom
Model 3703
Dual Channel 100 MHz Scope HP
1740A
Impairment Measuring Test Set HP
4935A
Universal Counter HP
5334A
225 MHz Freq. Counter HP
5382A
Logic Probe Hewlett Packard
Model 545A
—continued—

PLN-5001-001i Standard 02.02 April 1997

 Equipment 12–33

Table 12–6xxx
Additional equipment(continued)
Description Code

Transmission Test Set Hewlett Packard

Model TTS 44
Digital Test Head/Remote Office Test line Northern Telecom
DTH/ROTL
Trunk Signaling Analyzer Berry
Model 966A
Digital Carrier Test Set Bowmar
Model 273A
300 MHz Oscilloscope Tektronix
Model 2465
End

Floor maintenance
Floor maintenance procedures as outlined on pages 1 and 2 of AT & T
practice “BSP 770-140-010” Issue 1, August 1977, are suitable in the
DMS-100 environment.

Craftsperson interfaces
Input/output system
The I/O system consists of this equipment:
• Magnetic Tape Devices (MTD)
• Disk Drive Units (DDU)
• Visual Display Units (VDU)
• Teleprinters (PRT) Receive and/or Send
• Data Buffer Units
• Data Sets (Modems)
• Billing Media Converter (BMC)
• Distributed Processing Peripheral (DPP).

These devices are the primary means of communication between the

operating personnel and the DMS-100 Family system and vice-versa. The
I/O devices are used to input machine controls, run tests, request
information, and output system generated messages.
With the exception of the magnetic tape devices, disk drive units, and DPPs,
all other I/O devices may be supplied by either the operating company or
Northern Telecom. All devices supplied by the operating company require a
determination of compatibility with DMS-100 Family systems.

DMS-100 International Technical Specification BCS40i and up

12–34 Equipment

A minimum of five I/O ports, excluding MTDs, must be provided for all
DMS-100 Family systems:
• 1 VDU port for the Maintenance and Administration Position (MAP)
• 2 VDU, PRT ports for the Technical Assistance Service (TAS)
• 2 VDU ports for the Portable Maintenance (AXU).

I/O devices, as shown in table 12–7, are supported by the DMS-100 software
for logging maintenance and machine activity.

Table 12–7xxx
I/O devices

· Visual Display Units

Digital Equipment Corporation VT 220 300/1200 baud
· Teleprinters
Datacom
1200 S/R 300/1200 baud
Texas Instruments
OMNI 810 R/O 300/1200 baud
OMNI 820 S/R 300/1200 baud
Data products M-200 R/O 1200 baud
Data Speed 40/2 & 40/3 300/1200 baud
GE 2120 R/O 300/1200 baud
KSR

Magnetic tape devices (MTD)

Magnetic tapes are used in DMS-100 Family systems as external storage
devices and, on NT40-based systems, as a media for transferring batch data
and operating software into and out of the system. The read-write device for
magnetic tapes is the MTD. The MTD used for DMS-100 Family
application is the nine-track Cook tape drive, NT0X44AB.
The number of MTDs required will depend on the features to be supported
and the operating company administrative policy. A separate MTD is not
required for each feature; for example, operational measurements, service
analysis, and trouble diagnostics and reports may be assigned to the same
magnetic tape drive or disk drive unit. On NT40-based systems, a minimum
of one MTD is required. On SuperNode-based systems, the system load
module (SLM) tape unit is the primary tape storage device; however,
additional MTDs may still be provisioned as required.

PLN-5001-001i Standard 02.02 April 1997

 Equipment 12–35

Disk drive units

The disk drive unit used in the DMS-100 Family is the 5.25-inch Mercury
DDU. The unit fits into a standard DMS shelf, and has a formatted capacity
of 228.7 Mbytes.
For NT-40 based systems, the recommended configuration per system is two
disk drive units. In addition to AMA, OM, and journal files storage, a single
disk drive unit is typically used for office image storage and bootstrap
loading. On SuperNode-based systems, the system load module (SLM) disk
unit is the primary disk storage device; however, additional DDUs may still
be provisioned as required.
Visual display units
The Digital Equipment Corporation VT 220 VDU is supported by the
DMS-100 Family.
A VDU baud rate of l200 is recommended for all applications (a baud rate of
300 is also supported).
Teleprinters
The DMS-100 Family supports the five types of teleprinters shown in table
12–8 on page 12–35.

Table 12–8xxx
Teleprinters
Make/model Baud rate

DATACOM l200 S/R 1200/300

Texas Instruments 1200/300
OMNI 8l0: R/O
OMNI 820: S/R
Data Products M200 R/O 1200
Data Speed 40/2 & 40/3 1200/300
GE 2120 1200/300

Device controllers are used to interface with the teleprinters. As shown in

table 12–9, the device controllers are equipped with two types of
transmission interfaces: current loop or RS232. The type selected for use
depends on the cabling distance between the I/O device and the IOC.

DMS-100 International Technical Specification BCS40i and up

12–36 Equipment

Table 12–9xxx
Device requirements
Cabling Interface type Modem required
distance (feet)

up to 50 RS232 No
up to 1200 Current Loop No
over 50 RS232 Yes

Each terminal, regardless of its type, can appear either in a local or remote
location. Modems may be arranged for either dial-up or dedicated
operation.
Table 12–10 shows the modem recommended for use with DMS-100 Family
systems:

Table 12–10xxx
Modem requirements

108/113
RIXON C202/C212 300/120

PLN-5001-001i Standard 02.02 April 1997

 13–1

Power requirements
This chapter summarizes power and grounding specifications for DMS-100
Family switching systems. Specific system configurations vary depending
upon the the market in which the system is deployed, the application and
size of the system, and equipment provisioned. Additional detail on power
and grounding is provided in the following documents:
• Power Distribution and Grounding Guide, 297-1001-156
• DMS-100 Family Provisioning Manual, 297-1001-450.

Operating voltage
Power in the DMS SuperNode and the DMS–100 Family switching systems
is distributed at a nominal potential of –48 V dc. The operating voltage
ranges cover two conditions:
• Normal conditions: –42.75 V dc to –55.8 V dc
Note: Normal conditions occur under battery float (high end) and
maximum voltage drop (low end) operation.

• Extreme conditions: –44.75 V dc to –55.8 V dc

Note: Extreme conditions occur during commercial power failure (low
end) and battery equalization charging (high end). Interface equipment
may necessitate modification of these limits when sharing a power plant
with other equipment.

The actual operating voltages are measured at the input to the Power
Distribution Center (PDC), and include the loop voltage drops between the
office battery terminals and the PDC. Except for line current and some relay
equipment, all input power in the DMS-100 Family system is further
processed by converters and inverters to different dc and ac voltages.
Battery noise limits
The DMS-100 Family system may share power plants with other systems
provided that the requirements of power plant sharing are met and that the
office voltage range and battery noise level are within specified limits:
• Voltage range –44.75 V dc and –55.8 V dc

DMS-100 International Technical Specification BCS40i and up

13–2 Power requirements

• The noise present at the battery terminals of any dc source to which the
DMS-100 switch will be connected, shall not exceed 55 dBrnc or
300 mV rms in any 3 kHz band between 10 kHz and 20 MHz.
• Step voltage changes on the dc source (measured at PDC) should not
exceed 5 V dc in magnitude at a rate of change of 1 V/ms. Faster rates
of change can be tolerated if the step voltage magnitude is less than 5 V.
The product of magnitude and rate of change should not exceed
5 V2/ms., and the voltage limits (operating voltage) must not be
exceeded.
End cell switching is permissible for use with the DMS-100 Family systems
subject to the above step voltage changes.
Power consumptions
The current drain and power consumption are normally engineered by
Northern Telecom on a per-job basis.
Table 13–1 provides the maximum power consumption on a per-frame basis,
assuming that each frame is fully equipped and all equipment is operating at
maximum capacity.

Table 13–1
Maximum power consumption per frame
Frame Code Max watt

Trunk module equipment TME 480

Digital carrier equipment DCE 575
Network frame NETC 960
Central control complex (double bay) CCC 1720
Memory extension MEX 850
Magnetic tape center MTC 670
Miscellaneous equipment MIS 220
Power distribution center PDC 200
Remote line module (double bay) RLM 1150
Remote service equipment RSE 385
Line concentrating equipment LCE 1050 (6ccs)
1550 (8ccs)
Digital trunk equipment DTE 1120
Line group equipment LGE 980
—continued—

PLN-5001-001i Standard 02.02 April 1997

 Power requirements 13–3

Table 13–1
Maximum power consumption per frame (continued)
Frame Code Max watt

Line trunk equipment LTE 850

Input/output equipment IOE 1360 (6ccs)
1860 (8ccs)
Remote line concentrating module RLCM
Double shelf network equipment DSNE 600
Remote controller equipment RCE 1000
Message/switching 6 equipment MS6E 1150
End

Power alarms
DMS-100 Family power plant failures/alarms are detected through alarm
scan points in the associated maintenance trunk module. Power plant alarms
are grouped together (the grouping is definable by operating company) and
may be assigned optionally by the operating company into any of these
categories:
• Critical alarm from system power plant
• Major alarm from system power plant
• Minor alarm from system power plant.

The external alarms subsystem monitors the hardware of the DMS-100

Family alarm system through alarm scan points in the Office Alarm Unit
(OAU) in the associated Maintenance Trunk Module (MTM). These scan
points detect inputs from one of three sources:
• Hardwired alarm contacts in the DMS-100 Family hardware
• The operation of manual control switches
• The alarm circuits of miscellaneous equipment associated with the
DMS-100 Family office.
Whenever a scan point changes state, the external alarms subsystem status
display on the Visual Display Unit (VDU) is updated to reflect the change.
The status can also be printed on the maintenance teletypewriter (TTY).
The alarm system software responds to detected alarm or control inputs by
operating or releasing the appropriate Signal Distribution (SD) points in the
alarm system hardware, to initiate or terminate the corresponding audible
and visual alarm, or control function.

DMS-100 International Technical Specification BCS40i and up

13–4 Power requirements

The DMS-100 Family alarm control and display panel incorporates visual
lamps to indicate four types of failures:
• Critical power plant failure
• Major power plant failure
• Minor power plant failure
• Power distribution center Alarm Battery Supply (ABS) failure.

DC power distribution (PDC)

Office battery to power distribution center
The feeders and returns to the PDC from the office battery consist of two
separate sets of cables. One set is designated Battery Cable –A and Return
Cable –A, and the other set, Battery Cable –B and Return Cable –B (see
figure 13–1). The battery cable and its mate return cable must be routed
from the office battery to the PDC via the same cable racks. At the PDC,
both return cables are connected to a common return bus that is isolated
from the PDC framework. The total dc distribution capability of a PDC is
800 amperes, 400 A on feeder –A and 400 A on feeder –B.
Battery feeder cables from the office battery to each PDC are fused in the
power room at 600 A maximum. The operating company can engineer the
power to the maximum capability so that the site will not have to be
re-engineered as office expansion occurs. If anticipating future office
growth, the fuse capacity should be sized for the maximum 400 amp PDC
load and not based on current equipment load.

PLN-5001-001i Standard 02.02 April 1997

 Power requirements 13–5

Figure 13–1
Typical PDC arrangement

–48V
office Office
battery return

Splice plate Splice plate

Fuses
600A
max- Returned cables
each omitted Power room

PDC-02
–A

–B

Cross-aisle arrangements for shar-

ing
PDC between adjacent lineups.

DMS equipment room

–A
Feeder
–B
PDC-01

–A
Feeder
–B
PDC-00

DMS-100 International Technical Specification BCS40i and up

13–6 Power requirements

PDC to DMS-100 family frames DC distribution

Feeders to individual equipment frames are allocated so that each subsystem
of the DMS-100 Family is fed from an individual fuse on the PDC. Every
battery feeder is accompanied by a return feeder, of equal current carrying
capacity and routed in close proximity to it. Feeder size is chosen on a site
basis to satisfy the voltage drop constraints.
Each active DMS-100 Family equipment frame has a Frame Supervisory
Panel (FSP) which receives the feeder cables from the PDC fuse and
distributes dc power via local fuses or circuit breakers to the shelves in the
frame. The FSP also receives the ABS multiple feeder from the ABS fuse in
the PDC and routes the ABS via internal fuses to the frame alarm circuits.
The battery and return feeds to the DMS-100 Family frames vary in
connection arrangements depending on the types and quantities of shelves
provisioned.
Grounding systems in DMS-100 family
The DMS-100 Family grounding system is designed to encompass a variety
of installation environments and situations with a minimum of
reconfiguration between any two environments. The basic principle applied
to the DMS-100 switch grounding is the Single Point Ground (SPG).
Single point grounding consists of the interconnection of all backplane logic
returns within a module by one or more copper busbars and straps. This
connection may be made externally to each module or within the module,
but it must be made at only one point.
All shelf backplanes and interconnecting busbars are electrically isolated
from the module framework. The framework and logic return planes are
internal to the DMS-100 switch and are not for external use.
Non-Isolated System Grounding (Non-ISG) framework and logic return
arrangements are based on the same principles as systems with ISG.
Specific individual installations may be customized to meet customer
standards for particular situations.
Framework ground arrangements for non-ISG installations
Figure 13–2 shows the framework ground and logic return arrangements for
non-ISG systems. The framework ground consists of a specific
configuration:
• copper busbars located above each equipment frame with a copper braid
strap connection to the top, rear left hole (No. 77) of the frame
• copper braid straps linking the overhead busbars on adjacent frames in a
line-up
• No. 6 AWG wire interconnecting the framework ground on line-ups that
do not contain a PDC to an adjacent line-up that contains a PDC

PLN-5001-001i Standard 02.02 April 1997

 Power requirements 13–7

• a copper plate or busbar (framework ground bus) which serves to

interface the DMS framework ground network with the CO ground
network. This bus should be located in close proximity to the PDC that
is nearest to the interface with the CO ground (usually PDC00)
• No. 0 AWG interconnecting the framework ground bus in a ring
formation with the individual copper busbars located above each PDC.
The framework ground plane formed by the above configuration is then
bonded to the CO ground network. The size of the cable used for the bond
between the DMS framework ground bus and the CO ground is determined
in relation to the conductive length of the actual bond. If conductive length
is less than 100 feet, use No. 0 AWG. If conductive length is equal to or
more than 100 feet, use 750 MCM.
Because the framework ground is an extension of the main ground reference
local to each frame, it provides a convenient point for connection and
referencing of the SPG from each module. The framework ground is used
by all modules except the LCM. Each LCM must use its internal talk
battery return for the SPG. Where the module SPG lead consists of two or
more braided straps from the module logic ground busbars (for example, in
the CC) the straps are physically connected to a single point on the
framework ground bus. Some earlier vintage systems were customized to
allow connection of MEX logic grounds to the framework ground bus
located directly above each MEX frame. This arrangement is adequate for
those systems and does not require reconfiguration.

DMS-100 International Technical Specification BCS40i and up

13–8 Power requirements

Figure 13–2
Framework arrangement – non-ISG installations

No. 6 AWG

FBB

LR LR
LR TBR
LR LR BR

TB1 TB1

NET LGE PDC LCE

LME
No. 1/0
AWG Core SPG

BR LR LR LR LR

PDC IOE MOE

ENET or LIM
No. 6 AWG to FBB above PDC powering the lineup

LRB
FBB

No. 1/0 AWG

See note
LR LR LR
Framework
ground bus
DMS SuperNode

To DMS SPG DPCC SSC

(see page 13–9 for ENET or LIM
conductor size)

Note: Earlier installations may have framework ground referenced to the BR plate of PDC-00.

PLN-5001-001i Standard 02.02 April 1997

 Power requirements 13–9

Framework ground for ISG installations

Figure 13–3 shows the framework ground and logic return arrangements for
ISG systems. This configuration provides isolation between the framework
ground and logic return planes throughout the entire DMS-100 switch. The
only point of connection between framework ground and logic return occur
at the DMS SPG bus. This facilitates detection of grounding violations.
The logic return for the Input/Output equipment (IOE) frame must always be
connected to the same logic return as the CCC or DPCC, even when located
in a separate line-up. A single point connection is not mandatory for the
IOE logic return.
The DTE frame logic return bus is connected to the battery return bus plate
of the PDC that supplies the DTE power. Power for an LGE/LCE cluster
(several LCEs served by one LGE) must be obtained from the same PDC.
The frame logic return bus for the LGE equipment shall be bonded to the
battery return plate of the PDC that supplies the LGE power.
The cable size for referencing the logic return equalizer and framework
bonding equalizer plates to the DMS SPG bus shall be based on the
conductor length:
• 0–50 feet (0–15.3 m), use No. 2/0 AWG
• 50–150 feet (15.3–45.7 m), use No. 350 MCM
• over 150 feet (45.7 m), use No. 750 MCM
• If DMS SPG is on a separate floor, use 750 MCM.

Framework isolation (non-isolation installations)

In non-ISG installations, the equipment line-up that contains the CCC or
DPCC module must have all framework isolated from any ground other than
framework ground. This module is vital to the DMS-100 switch and
framework isolation prevents possible malfunction of memory equipment
due to electromagnetic fields which may be generated if an unusually large
fault current was allowed to flow through the CCC or DPCC framework. As
a general rule, isolation of all frames from any ground other than framework
ground is recommended, and specific framework isolation is mandatory:
• all frames in any CCC or DPCC module line-up
• all frames when the point of DMS SPG reference is located on another
floor
• all frames when dc power plant is shared with other systems that specify
isolation
• to comply with specific customer grounding standards.

Framework isolation (ISG installations)

For systems with ISG, isolation of all frames from any ground other than
framework is mandatory. All DMS-100 equipment has its framework and

DMS-100 International Technical Specification BCS40i and up

13–10 Power requirements

logic return isolated and connected to the DMS SPG at only one point. This
isolation ensures that all other building grounds, grounding conductors, and
return conductors do not contaminate the logic return or framework ground.
Central office building ground
It is recommended that resistance between of the central office building
principal ground to earth should be as low as is practically possible
(preferably 5 Ω or less) and in no case should it exceed 25 Ω. This coincides
with the requirements set by the National Electrical Code (ANSI/NFPA No.
70–1978, Article 250–84) for the commercial ac ground in any building.

PLN-5001-001i Standard 02.02 April 1997

 Power requirements 13–11

Figure 13–3
Framework ground and logic return – ISG systems

No. 1/0 AWG

Core LRB LRB

FBB

BR LR LR LR

PDC IOE MOE MIS DSNE TME

No strap

LRB
FBB

LR LR LR

DPCC SSC LIM LIM

No. 1/0 AWG

No. 1/0 AWG
FBE LRE

DMS
To DMS SPG SuperNode To DMS SPG
(see page 13–9 (see page 13–9
for conductor size) for conductor size)

Note: Dedicated FBE and LRE bars are preferred for the STP equipment.

DMS-100 International Technical Specification BCS40i and up

13–12 Power requirements

AC grounding arrangements
Conforming with national electrical codes, each ac distribution circuit must
be provided with an additional conductor, commonly referred to as the
“green wire.” A separate green-wire network is required for each ac source.
Commercial ac is a source that originates (has a ground reference) external
to the DMS-100 system. Each protected ac inverter constitutes a source that
originates (has a ground reference) internal to the DMS-100 switch.
The main ac and telecommunication system grounds must be connected
together at the building principle ground. A connection is also required
between the Central Office DMS SPG ground appearance used for the
DMS-100 System and the green-wire network for all commercial ac circuits
used on or within the DMS-100 System. As a minimum, the size of the
connection should conform to electrical code requirements for equipment
grounding conductors.
The DMS-100 switch may be configured with either of two configurations
of the green-wire network. Because of the ground interconnections and the
circuit isolation inherent to the DMS-100 switch, the green wire network can
be configured to make contact with the DMS-100 framework while retaining
operational and personnel safety integrity. In this configuration, the
DMS-100 switch and the green wire are isolated from incidental contact
with building ground.
If an isolated green-wire network is chosen, the green wire and ac
components will be isolated from the DMS-100 framework. All ac will be
insulated from contact with the DMS-100 framework and incidental building
ground.
Four types of equipment can be affected:
• ac receptacle
• conduit and junction boxes
• shoulder bushings and mounting hardware
• the ac safety ground wire.

The green wire for each protected ac inverter is bonded to the inverter
chassis and referenced to the DMS framework ground. To preserve isolation
of the commercial ac green-wire network, inverters must not be used to
power any equipment whose chassis may have electrical contact with the
building ground.

Frame loads
The secondary distribution of dc power from the PDC to individual DMS
frames is described in the following paragraphs in conjunction with
identified figures. All figures are based on the latest equipment and frame

PLN-5001-001i Standard 02.02 April 1997

 Power requirements 13–13

arrangements. An explanation of differences between these and earlier

equipment and arrangements that are still in service is provided in the text.
DMS SuperNode cabinet
The DMS SuperNode (DPCC: NT9X01BA or NT9X01JA) cabinet (shown
in figure 13–4) contains combinations of the Computing Module, Enhanced
Network, Message Switch, and/or System Load Unit (SLU)) as well as
the –48V cabling arrangements for a fully equipped configuration.
Power distribution for the DMS SuperNode cabinet is as follows.
• Thirteen power feeders from the PDC are required:
— Eight feeders for Power Modules, each feeder fused at 25 A in the
PDC. Feeders serving components in plane 0 are obtained from the
A Bus of the PDC. Feeders for the components of plane 1 are
obtained from the B Bus.
— The blowers require four power feeders, with each feeder fused at
5 A in the PDC. Two feeders are obtained from the A Bus and two
feeders are from the B Bus.
— One feeder is used for ABS. It normally originates from a single
A Bus feeder fused at 10 A in the PDC.
• Each Power Module consists of two power converters: NT9X30AA
(+5 V, 86 A) and either NT9X31AA (–5.2 V, 20 A) for the Computing
Module and Network, or NT9X47AA (+12 V, 10 A) for the SLU.
• Each blower in the cooling shelf is powered directly from the –48V
source.
Other DMS SuperNode cabinets, such the CMDC, MSDC, LIM, and ENET,
are powered as described above.

DMS-100 International Technical Specification BCS40i and up

13–14 Power requirements

Figure 13–4xxx
DMS SuperNode cabinet power distribution

Power feeders
from the A and B
busbars in the PDC EMI cabinet
(13 feeders)

FSP Shelf

ABS and
Input termi- alarm circuits
nal
EMI filters

Power Shelf 1 Power

Module Module

Power Shelf 2 Power

Module Module

Power Shelf 3 Power

Module Module

Power Shelf 4 Power

Module Module

Cooling
Blower Blower shelf Blower Blower

Note 1: Plane 0 of the DMS SuperNode frame is powered from the A Bus of the PDC frame.
Note 2: Plane 1 of the DMS SuperNode frame is powered from the B Bus of the PDC frame.
Note 3: The power module circuits are fused in the PDC at 25 A.
Note 4: The blower circuits are fused in the PDC at 5 A. Two of the blower circuits are fed
from the A Bus of the PDC, and the other two blower circuits are fed from the B Bus.

Central control complex and memory extension frame

Power is distributed to each shelf in a central control complex (CCC) frame
or in a memory extension (MEX) frame from a separate 20 A fuse in the

PLN-5001-001i Standard 02.02 April 1997

 Power requirements 13–15

PDC (see figure 13–5) A cooling unit is located in the bottom shelf of each
frame.
The cooling unit for present vintage systems (NT3X90AC) contains five
fans, each of which requires –48V dc power. Power for the NT3X90AC
type cooling unit is obtained from two 5-A fuses at the PDC.
The cooling unit in earlier vintage systems, (NT0X30) contains five fans,
each of which requires 120 V, 60 Hz no-break ac power. The no-break
ac supply is generated by separate dc-ac inverters. Two inverters feed a
maximum of four cooling units. Each inverter is fed from a 20-A fuse at
the PDC. To increase reliability, the inverters are alternately connected to
the A Bus and the B Bus of the PDC.
The ABS is protected by a 10-A fuse at the FSP of the PDC. In a DMS
equipped with an Enhanced Alarm System (EAS), the ABS power feeder
originates from a 20-A fuse or circuit breaker at the power plant powering
the PDC. In a DMS not equipped with EAS, this feeder originates at the A
Bus of the PDC.

DMS-100 International Technical Specification BCS40i and up

13–16 Power requirements

Figure 13–5xxx
CCC and MEX frame power distribution

Note 1 CCC or MEX frame

B feeder A feeder (Plane 0)

PDC CC or MEX shelves

frame
Power converters
B bus A bus
CCC or MEX frame
(Plane 1)
10 A 10 A
20 A 20 A
20 A 20 A
To CC or MEX
shelves via 10 A 20 A
fuses in FSP 10 A FSP
20 A
Note 4
1.33 A
ABS ABS
20 A

20 A

10 A 10 A

Power converters
CC/MEX shelves
Note 3 Note 3
Cooling unit Cooling unit
(notes 2 and 3) (notes 2 and 3)

ABS (to other frames)

Note 1: Each feeder (–48 V) has a corresponding return of the same gauge connected to the
battery return bus of the PDC.
Note 2: The CCC frame requires a cooling unit at all times. The MEX frame requires a cooling
unit only when four memory shelves are provisioned.
Note 3: The current NT3X90AC type cooling unit requires two 5-A fuses at the PDC.
Each NT3X90AA and NT3X90AB type cooling unit requires a 5-A fuse at the PDC.
Earlier NT0X30 type cooling units with separate NT0X87 type inverters require a 20 A-fuse at the
PDC for each inverter.
Note 4: In a DMS with EAS, the ABS power feeder originates from a 20-A fuse or circuit breaker
at the power plant powering the PDC. In a DMS not equipped with EAS, this feeder originates at
the A Bus of the PDC. The ABS is protected by a 10-A fuse at the PDC.

PLN-5001-001i Standard 02.02 April 1997

 Power requirements 13–17

Network module frame

There are two types of Network Module (NM) frames, types NT5X13
(NETC) and NT0X48 (NET).
Network type NT5X13
The NT5X13 type frame is a standard frame equipped with network
modules (NM) and a cooling unit. The NMs in shelf positions 51 and 65 are
designated as Plane 0, and the NMs in shelf positions 18 and 45 make up
Plane 1. The power distribution to the NM planes is as follows (see
figure 13–6).
• Each NM plane is powered by one battery feeder fused in the PDC at
20 A. Plane 0 is fed from the A Bus and Plane 1 is fed from the B Bus.
• The 20-A feeder is divided at the frame FSP into two 10-A feeders, one
for each shelf position.
An NT3X90 cooling unit is provided in the bottom shelf of each NM frame.
The cooling units in the NM frames are configured in the same manner as in
the CCC or MEX frames. The NT3X90AC cooling units use 48 V powered
fans. Each unit is fed from dual 5 A fuses (A and B feeders) at the PDC.
For earlier installations using the NT3X90AA and NT3X90AB type cooling
units, the cooling unit in the first NM frame is equipped with two dc-ac
inverters, where one inverter is fed from the A Bus of the PDC through a
5-A fuse, and the other inverter is fed from the B Bus of the PDC through a
5-A fuse. The cooling units for the remaining NMs are equipped with one
dc-ac inverter powered from a PDC bus through a 5-A fuse. Power
distribution to the inverters is configured so alternate inverters are fed from
the A Bus of the PDC, and the remainder are fed from the B Bus of the
PDC.
The ABS is protected by a 10-A fuse at the FSP of the PDC. In a DMS
equipped with EAS, the ABS power feeder originates from a 20-A fuse
or circuit breaker at the power plant powering the PDC. In a DMS not
equipped with EAS, this feeder originates at the A Bus of the PDC.

DMS-100 International Technical Specification BCS40i and up

13–18 Power requirements

Figure 13–6xxx
NT5X13 NM frame power distribution

Note 1
NM frame
B feeder A feeder
NM plane 0
PDC (2 shelves)
frame
Power converters
B bus A bus

10 A 10 A
20 A 20 A

FSP
10 A 1.33 A
ABS
Note 3

10 A 10 A

Power converters
NM plane 1
(2 shelves)

5A 5A
Inverter Cooling unit
Inverter (note 2)

ABS (to other frames)

Note 1: Each feeder (–48 V) has a corresponding return of the same gauge connected to
the battery return bar of the PDC.
Note 2: The NT3X90AC type cooling unit has two fans. Each is powered (–48 V) through a
5 A fuse at the PDC. The NT3X90AA and NT3X90AB type cooling units are equipped with
self-contained inverters as follows:
a. The first NM frame contains two inverters.
b. Each remaining NM frame contains one inverter.
Note 3: In a DMS with EAS, the ABS power feeder originates from a 20-A fuse or circuit
breaker at the power plant powering the PDC. In a DMS not equipped with EAS, this feeder
originates at the A Bus of the PDC. The ABS is protected by a 10-A fuse at the PDC.

PLN-5001-001i Standard 02.02 April 1997

 Power requirements 13–19

Network type NT0X48

A single network module (NM) is contained in an NT0X48 type NM frame,
as shown in figure 13–7. The configuration and powering of these NMs is
as follows:
• Two NMs are used in parallel for reliability purposes.
• One of the parallel pair of NMs is designated plane 0 and the other is
designated plane 1.
• Each NM is powered by two battery feeders as follows:
— Each of the feeders is fused separately at 20 A in the PDC.
— NMs in plane 0 are fed from the A Bus of the PDC.
— NMs in plane 1 are fed from the B Bus of the PDC.
• Each of the 20 A feeders is divided into two 10-A feeders at the frame
FSP.
• Each NM shelf is powered from one of the 10-A feeders at the frame
FSP.
• A cooling unit is located in the bottom shelf of each NM frame. For
reliability, NT3X90 and NT0X30 type cooling units in an NM frame are
configured in the same manner as that for the CCC or MEX frame.
• The ABS is protected by a 10-A fuse at the FSP of the PDC. In a DMS
equipped with EAS, the ABS power feeder originates from a 20-A fuse
or circuit breaker at the power plant powering the PDC. In a DMS not
equipped with EAS, this feeder originates at the A Bus of the PDC.

DMS-100 International Technical Specification BCS40i and up

13–20 Power requirements

Figure 13–7xxx
NT0X48 NM frame power distribution

Note 1 NM frame

B feeder A feeder (Plane 0)

PDC NM shelves
frame Power converters
B bus A bus
NM frame
(Plane 1)
10 A 10 A
20 A
20 A
To NM shelves
via 10 A fuses 20 A 10 A 1.33 A FSP
in FSP shelf ABS
Note 4
20 A

10 A 10 A
ABS

Power converters
NM shelves

Note 3 Note 3
Cooling unit Cooling unit
(notes 2 and 3) (notes 2 and 3)

ABS (to other frames)

Note 1: Each feeder (–48 V) has a corresponding return of the same gauge connected to the
battery return bar of the PDC.
Note 2: Each NM frame is equipped with a cooling unit.
Note 3: The current NT3X90AC type cooling unit requires two 5 A fuses at the PDC.
Each NT3X90AA and NT3X90AB type unit requires a 5 A fuse at the PDC.
Earlier NT0X30 type cooling units with separate NT0X87 type inverters require a 20 A fuse at
the PDC for each inverter. The NT0X87 type inverters are not always used on NM frames be-
cause two NT0X87 inverters are required for every four cooling units.
Note 4: In a DMS with EAS, the ABS power feeder originates from a 20-A fuse or circuit
breaker at the power plant powering the PDC. In a DMS not equipped with EAS, this feeder
originates at the A Bus of the PDC. The ABS is protected by a 10-A fuse within the PDC.

PLN-5001-001i Standard 02.02 April 1997

 Power requirements 13–21

Trunk module equipment frame

The trunk module equipment (TME) frame may contain only trunk module
(TM) shelves or a combination of TM and digital carrier module (DCM),
maintenance trunk module (MTM), or office alarm unit (OAU) shelves as
shown in figure 13–8 on page 13–23. To avoid possible overload of the
power supply, use the following combinations:
• five TM shelves in positions 65, 51, 32, 18, and 04 (position 04 is used
last)
• four TM shelves and one MTM shelf
• three TM or MTM shelves with another MTM shelf in position 51 and
one alarm cross-connect Unit (AXU) shelf in position 65
• two TM or MTM shelves and one DCM shelf, with another MTM shelf
in position 51 and one AXU shelf in position 65.
Power-feed arrangements for these shelf combinations are designed during
job engineering, in conjunction with GS0X82. Depending on the type of
interface, the following significant factors must be considered in power-feed
arrangements.
Analog trunk interface
The following applies for analog trunks:
• TME frames are fed through 20-A fuses at the PDC.
• Power feeds are equally distributed across the A Bus and the B Bus to
balance the load.
• The 20-A feed is divided into four 10-A feeds at the FSP of the TME
frame.
• Each TME shelf is powered from one of the 10-A feeders at the FSP of
the TME (earlier installations use 5-A fuses).
• When required, an additional 5-A feed for an AXU shelf and its
associated MTM is provided.
• When the MTM in the TME is not associated with an AXU, an
additional 20-A feed is provided for the TME. This feed powers the
MTM through the 10-A fuse in the FSP assigned to the top shelf.
• When TM and DCM shelves are mixed, all TM shelves are powered
from the same feeder, and DCM shelves are fed alternately from the A
and B Buses.
Maintenance trunk module and office alarm unit
When the AXU shelf and its associated primary alarm MTM are mounted in
the TME frame positions 65 and 51, the secondary alarm MTM must be
mounted in position 65 on another TME frame and powered from a different
feed than the primary alarm MTM. The AXU, or OAU, is fed from a 5-A
fuse at the FSP. When the MTM is not used for alarms, the location of the
MTM in the TME frame is not restricted.

DMS-100 International Technical Specification BCS40i and up

13–22 Power requirements

In a DMS-100F system equipped with the EAS, the 20-A power feeders
associated with the primary alarm MTM (OAU) and secondary alarm MTM
originate directly from the power plant powering the PDCs. When a TME
requires two power feeders, it can be powered either (a) by two feeders from
the PDC, or (b) by one feeder from the PDC and another feeder from the
power plant.
E&M trunk interface
For E&M circuits, the battery return of the PDC is used as a separate logic
return, and a talk battery supply is provided from the PDC battery feed
through a filter at the FSP. The talk battery supply is then distributed to each
shelf through a 3-A fuse at the FSP.

PLN-5001-001i Standard 02.02 April 1997

 Power requirements 13–23

Figure 13–8xxx
TME frame power distribution

TME frame
MTM or TM
Power AXU
converter Talk battery
Note 1 shelf
65
B feeder A feeder
TM, MTM, or OAU
PDC
frame Power Talk battery
B bus A bus converter
TME frame 51

20 A
To TM 3A 3A
10 A 10 A Note 3.
shelves
5A
Note 2
OR
20 A
Note 2 FSP
20 A
Filter
10 A 1.33 A
ABS
Note 4
3A
ABS
3A
10 A 10 A 10 A 3A

Power converters Talk battery

ABS (to other frames)
TM shelves 4, 18, and 32

Note 1: Each feeder (–48 V) has a corresponding return of the same gauge connected to the
battery return bar of the PDC.
Note 2: For an OAU application, the 10-A circuit breaker assigned to the the top shelf is fed
through a separate 20-A fuse in the PDC. For an OAU application with EAS, the –48V feeders
and their returns for the primary and secondary alarm MTMs originate directly from the power
plant powering the PDC. The MTM in the top shelf is a secondary alarm, and the MTM in position
51 is a primary alarm.
Note 3: For an OAU application, the 5-A breaker is provided for the AXU shelf associated with
the MTM in shelf position 51.
Note 4: In a DMS with EAS, the ABS power feeder originates from a 20-A fuse or circuit breaker
at the power plant powering the PDC. In a DMS not equipped with EAS, this feeder originates at
the A Bus of the PDC. The ABS is protected by a 10-A fuse within the PDC.

DMS-100 International Technical Specification BCS40i and up

13–24 Power requirements

Digital carrier equipment frame

When all shelves in a frame contain digital carrier modules (DCMs), the
frame is called a digital carrier equipment (DCE) frame, as shown in
figure 13–9. Factors to be considered when arranging the power feed for a
DCE are as follows.
• The DCE is powered from a 20-A fuse from the A Bus and a 20-A fuse
from the B Bus in the PDC.
• The 20-A fused supplies are subdivided into 10-A fused supplies at the
frame FSP of the DCE.
• The DCM shelves are alternately powered from the A Bus and B Bus
through 10-A fuses. (Earlier installations use 5-A fuses for the DCM
shelf feeds.)
• The DCE is equipped with a maximum of four DCM shelves.
• DCM loads are balanced as evenly as possible between the A and B
Buses.
• The ABS is protected by a 10-A fuse at the FSP of the PDC. In a DMS
equipped with EAS, the ABS power feeder originates from a 20-A fuse
or circuit breaker at the power plant powering the PDC. In a DMS not
equipped with EAS, this feeder originates at the A Bus of the PDC.

PLN-5001-001i Standard 02.02 April 1997

 Power requirements 13–25

Figure 13–9xxx
DCE frame power distribution

Note 1

B feeder A feeder DCE frame (Plane 0)

PDC DCM shelves

frame
Power converters
B bus A bus

DCE frame (Plane 1) 10 A 10 A

20 A 20 A

20 A 20 A
DCM shelves
FSP
10 A
1.33 A
Note 2
ABS ABS

10 A 10 A

Power converters

DCM shelves

ABS (to other frames)

Note 1: Each feeder (–48 V) has a corresponding return of the same gauge connected to
the battery return bar of the PDC.
Note 2: In a DMS with EAS, the ABS power feeder originates from a 20-A fuse or circuit
breaker at the power plant powering the PDC. In a DMS not equipped with EAS, this feeder
originates at the A Bus of the PDC. The ABS is protected by a 10-A fuse at the PDC.

DMS-100 International Technical Specification BCS40i and up

13–26 Power requirements

Line module equipment frame

The line module equipment (LME) frame is a double-bay frame. Each bay
contains one line module (LM) with 640 lines and its associated line module
controller (LMC) as shown in figure 10–10. When one LMC fails, the other
LMC in the LME controls both LMs. Each LMC contains two –48V power
converters that provide +24 V and one converter that provides +5 V and
+12 V for the LM and its associated equipment. Factors that must be
considered when designing power feeds to LMs are:
• LM loads are fed alternately from the A Bus and B Bus of the PDC.
This arrangement balances the load and provides reliability in the event
of a power failure on the A or B Bus.
• One of the +24V converters in each bay is powered from a 20-A fuse
of the A Bus. The other is powered from a 20-A fuse of the B Bus.
• The +5V and +12V converter in the LCM Bay 0 is powered from a 20-A
fuse of the A Bus. The equivalent converter in Bay 1 is powered from a
20-A fuse of the B Bus.
• Talk battery filters in the bay FSPs are fed from 10-A fuses as follows.
— The filter assigned to Line Drawers (LDs) 00 to 09 is fed from the
A Bus.
— The filter assigned to LD 10 to 19 is fed from the B Bus.
• The ABS is protected by a 10-A fuse at the FSP of the PDC. In a DMS
equipped with EAS, the ABS power feeder originates from a 20-A fuse
or circuit breaker at the power plant powering the PDC. In a DMS not
equipped with EAS, this feeder originates at the A Bus of the PDC.

PLN-5001-001i Standard 02.02 April 1997

 Power requirements 13–27

Figure 13–10xxx
LME frame power distribution

Double–bay LME frame

Bay 0 Bay 1
Note 1 Power converters Power converters

A feeder +5 V +5 V
or or
B feeder +24 V +24 V +12 V +24 V +24 V +12 V

PDC
frame
B bus A bus LD cards 15–19 LD cards 15–19
FSP FSP

10 A 10 A 10 A
20 A
10 A 10 A 10 A

20 A 20 A

20 A 20 A

20 A

10 A 10 A 5A 5A
Filter Talk battery A Talk battery A
Filter
LD 00–09 LD 00–09
5A 5A
Filter Talk battery B Talk battery B
Filter
10 A 10 A LD 10–19 LD 10–19

1.33 A
ABS
10 A 1.33 A
ABS

Note 2 LD cards 00–14 LD cards 00–14

ABS (to other frames)

Note 1: Each feeder (–48 V) has a corresponding return of the same gauge connected to
the battery return bar of the PDC.
Note 2: In a DMS with EAS, the ABS power feeder originates from a 20-A fuse or circuit
breaker at the power plant powering the PDC. In a DMS not equipped with EAS, this feeder
originates at the A Bus of the PDC. The ABS is protected by a 10-A fuse at the PDC.

DMS-100 International Technical Specification BCS40i and up

13–28 Power requirements

Line concentrating equipment frame

Each line concentrating equipment (LCE) frame contains two line
concentrating modules (LCMs), as shown in figure 13–11. Factors that must
be considered when designing power-feeding arrangements for the LCMs
are as follows.
• There are two power feeds from the PDC, a 20-A fused feed from the A
Bus and another from the B Bus.
• Each feed is connected to a 10-A circuit breaker at the LCE and
distributed to the LCMs.
• The FSP of the LCE powers the following equipment:
— Ringing generator RG 0 is fed from the A Bus and generator RG 1
is fed from the B Bus. Each feed is protected by a 20-A fuse at the
PDC and a 10-A circuit breaker at the FSP.
— Each talk battery supply is protected by a 20-A fuse at the PDC. The
talk battery circuit for each line drawer is protected by a 7.5-A fuse
at the FSP of the line drawer. One of the talk battery supplies is fed
from the A Bus; the other is fed from the B Bus.
• The ABS is protected by a 10-A fuse at the FSP of the PDC. In a DMS
equipped with EAS, the ABS power feeder originates from a 20-A fuse
or circuit breaker at the power plant powering the PDC. In a DMS not
equipped with EAS, this feeder originates at the A Bus of the PDC

PLN-5001-001i Standard 02.02 April 1997

 Power requirements 13–29

Figure 13–11xxx
LCE frame power distribution

Note 1 LCE frame

B feeder A feeder FSP

Ringing Generators
PDC
frame RG 0 RG 1
B bus A bus
10 A 10 A

20 A 20 A

Filter
20 A 20 A
Filter
10 A 1.33 A
ABS
Note 2
20 A 20 A

20 A 20 A

10 A 10 A 10 A 10 A

7.5 A
fuses
ABS (to other frames)
Power Power Talk battery B
converters converters LSG 00–09
(LCM 0) (LCM 1)
7.5 A
fuses

LCE Talk battery A

LSG 10–19
shelf

Note 1: Each feeder (–48 V) has a corresponding return of the same gauge connected to
the battery return bar of the PDC.
Note 2: In a DMS with EAS, the ABS power feeder originates from a 20-A fuse or circuit
breaker at the power plant powering the PDC. In a DMS not equipped with EAS, this feeder
originates at the A Bus of the PDC. The ABS is protected by a 10-A fuse at the PDC.

DMS-100 International Technical Specification BCS40i and up

13–30 Power requirements

Line group equipment frame

The line group equipment (LGE) frame contains two line group controllers
(LGCs) as shown in figure 13–12. Factors that must be considered when
designing power-feed arrangements for LGEs are as follows:
• One LGC is powered by the A Bus and the other is powered by the B
Bus.
• Each of the secondary feeds is fused at 20-A in the PDC and protected
by a 10-A circuit breaker in the FSP before distribution to an LGC.
• For ISG, the LGE and its associated LCMs must be powered from the
same PDC.
• The ABS is protected by a 10-A fuse at the FSP of the PDC. In a DMS
equipped with EAS, the ABS power feeder originates from a 20-A fuse
or circuit breaker at the power plant powering the PDC. In a DMS not
equipped with EAS, this feeder originates at the A Bus of the PDC.

PLN-5001-001i Standard 02.02 April 1997

 Power requirements 13–31

Figure 13–12xxx
LGE frame power distribution

Note 1

B feeder A feeder

PDC
frame
LGE frame
B bus A bus

FSP
10 A 1.33 A
ABS frame
Note 2
20 A 20 A

20 A 20 A

10 A 10 A 10 A 10 A

LGE shelf

LGC 0 LGC 1

ABS (to other frames)

Note 1: Each feeder (–48 V) has a corresponding return of the same gauge connected to
the battery return bar of the PDC.
Note 2: In a DMS with EAS, the ABS power feeder originates from a 20-A fuse or circuit
breaker at the power plant powering the PDC. In a DMS not equipped with EAS, this feeder
originates at the A Bus of the PDC. The ABS is protected by a 10-A fuse at the PDC.

DMS-100 International Technical Specification BCS40i and up

13–32 Power requirements

Magnetic tape center frame

The magnetic tape center (MTC) frame contains a magnetic tape drive
(MTD) and an input/output controller (IOC) or modem shelf. The
power-feed arrangement of these units is shown in figure 13–13.
Factors that must be considered when designing a power feeding
arrangement for an MTC frame are as follows:
• The MTD is powered from a 20-A fuse on the PDC.
• The MTD is powered from the same bus that powers its associated IOC.
• The IOC or modem shelf is powered from a 20-A fuse on the PDC.
• The 20-A feed to an IOC is fused at 10-A in the FSP before it is routed
to the IOC.
• If a modem shelf is used instead of an IOC, power from the 20-A fuse is
fed directly to an inverter which then powers the modem.
• The ABS is protected by a 10-A fuse at the FSP of the PDC. In a DMS
equipped with EAS, the ABS power feeder originates from a 20-A fuse
or circuit breaker at the power plant powering the PDC. In a DMS not
equipped with EAS, this feeder originates at the A Bus of the PDC.

PLN-5001-001i Standard 02.02 April 1997

 Power requirements 13–33

Figure 13–13xxx
MTC frame power distribution

Note 1

B feeder A feeder
MTC frame (plane 0)
PDC
frame MTD 1
B bus A bus
MTC frame (plane 1)

Note 2 10 A
20 A 20 A
MTD 2

10 A 1.33 A
ABS
FSP
Note 2
Note 3
IOC shelf or 20 A 20 A
modem shelf
10 A

ABS
IOC Inverter
ABS (to other frames) IOC shelf or (power to
modem shelf ac modem)

Note 1: Each feeder (–48 V) has a corresponding return of the same gauge connected to the
battery return bus of the PDC.
Note 2: When the MTD is a Hewlett-Packard unit, the MTD is powered directly from the
20-A fuse in the PDC. When the MTD is a Cook Electric unit, power is supplied through a
10-A fuse in the FSP.
Note 3: When an IOC shelf is used, power from the 20-A fuse (PDC) is fed through a
10-A fuse (FSP) to the IOC. If a modem shelf is used instead of an IOC, power from the
20-A fuse is fed directly to an inverter which then powers the modem.
Note 4: In a DMS with EAS, the ABS power feeder originates from a 20-A fuse or circuit
breaker at the power plant powering the PDC. In a DMS not equipped with EAS, this feeder
originates at the A Bus of the PDC. The ABS is protected by a 10-A fuse at the PDC.

DMS-100 International Technical Specification BCS40i and up

13–34 Power requirements

Remote line facility

Some line modules may be located remotely from the DMS. Remote line
modules, such as the remote line module (RLM), remote line concentrating
module (RLCM), and remote switching center (RSC), are subject to the
same power distribution rules that are specified for the DMS, except that
large remotes may have their own PDC, and a PDC can be shared between
collocated remotes, provided that all remotes are in the same IBN.
Miscellaneous equipment frame
The miscellaneous equipment (MIS) frame can be configured as a standard
MIS or MOE, a dedicated MIS, IMAP MIS, or MAP MIS. The MIS frame
contains a variety of equipment such as the following items:
• a metallic test access circuit
• a recorded announcement machine
• modems
• OEM equipment
• inverters
ing arrangements vary in the
Power-feeding arrangements for MIS frames vary in the job engineering
process because of the wide variation of shelf complements and office
configurations.
Clustering
To ensure optimal logic referencing of their functional circuits, some
hardware modules must be clustered as follows.
• they must be powered from the same PDC
• their vertical logic return bars must be bonded to the BR plate of the
common PDC with a No. 6 AWG.
ing arrangements vary in the
The following equipment entities require clustering:
• LCE frame with associated LGE, LTE, DTE, RCE, RME, RCME, SME,
ILGE, ILTE, IDTE, and SMS frames.
• ILCE frame with associated ILGE, ILTE, IDTE, IAE, and STE frames.
• ISLM frame with associated IAE, and STE frames.
• MS6E frame with associated DME frames.
• MS7E frame with associated ST7E frames.
ing arrangements vary in the
Exception: For DMS-200 and DMS-300 applications, the DTE/IDTE logic
return bus shall be: (a) bonded to the lineup logic return cable that connects
to the LRE splice plate, or (b) connected to the LRB busbar assembly.
For all other applications, the DTE/IDTE logic return bus shall be connected
to the battery return plate of the PDC that supplies power to the DTE/IDTE.

PLN-5001-001i Standard 02.02 April 1997

 Power requirements 13–35

Integrated maintenance and administration position (IMAP)

The integrated maintenance and administration position (IMAP) is a version
of the the MAP configured for installation in a CBN rather then in a DMS
IBN. Consequently, direct metallic communication or power links between
DMS-100F and IMAP are not permitted. The IMAP and its associated
equipment can be powered from any suitable source of ac power. To ensure
availability of the IMAP under adverse conditions, the use of a UPS or an
inverter is recommended.
If the inverter incorporates facilities for transfer to commercial ac, the
transfer time generally should not exceed 15 ms. Equipment
such as a smart modem constitutes protected load and must be powered
accordingly.
As an alternative to customer-provided power, a 500-W inverter is available
for installation in a collocated IMAP MIS frame. In all US installations,
fixed wiring shall be used in accordance with NEC requirements for power
distribution from the ac power source to IMAP outlets. Cord and plug
distribution can be used in accordance with CEC requirements in Canadian
installations. Distribution facilities, including conduit and PAC poles,
should not simultaneously carry power from different sources, such as
commercial ac and protected ac.
Receptacles can be installed as floor outlets, wall outlets, or PAC pole
outlets. Isolated ground (orange) outlets can be used in non-BOC
installations only, provided that they comply with NEC Article 250–74 or
CEC Section 10–906, whichever is applicable. Receptacles providing
protected ac shall be marked accordingly.
The use of extension cords to connect OEM equipment to the IMAP
receptacles is not recommended.
Maintenance and administration position (MAP)
The basic IMAP equipment subsystems can be configured as part of an IBN,
effectively becoming a MAP configuration.
When the MAP is installed in an IBN, direct metallic communication and
power links are not permitted. All ac power facilities required by the MAP
must be installed in accordance with the distribution and grounding rules
established for that IBN.
An earlier version of the MAP is installed as part of the DMS IBN.
• With the ISG version of DMS-100F, direct metallic communication links
between the MAP and DMS are not permitted. All ac power is produced
by NT0X87 inverters installed in a MIS frame and distributed by way of
plugs and cords to PAC poles.

DMS-100 International Technical Specification BCS40i and up

13–36 Power requirements

• With the non-ISG version of DMS–100F, direct metallic communication

links (such as EIA RS–232, current loops, or modem-to-modem links)
are used.
ing arrangements vary in the
Power distribution center (PDC)
The power distribution center provides interface between the –48V dc
(nominal) office batteries and the individual loads within the DMS-100
Family System. In figure 13–1, the PDCs are shown as being located at the
end of the frame lineup, but may be located at any other position, consistent
with the voltage drop limitations. Depending on PDC distribution capability
and the current drain which is engineered by Northern Telecom on a per-job
basis, one PDC can be shared by multiple (normally a maximum of three)
lineups. Cross-aisle power cable runs, when necessary, are limited to one
cable tray.
PDC frame description
Figure 13–14 shows a front view of a typical PDC frame. A fully-equipped
PDC frame has five components:
• Ten fuse panels for dc feeds to DMS-100 Family shelves and frames
• A Frame Supervisory Panel (FSP) containing alarm circuitry
• A filter panel, containing noise and transient suppression components
• A ground panel containing the common battery return busbar
• A filler panel with holders for spare fuses.

Positions of panels on the PDC frame are identified by the level of the holes
in the vertical supports of the frames.

PLN-5001-001i Standard 02.02 April 1997

 Power requirements 13–37

Figure 13–14
Typical PDC frame configuration (front view)

Fuse Fuse
62F00 62F14 Ground
panel

Fuse distribution A feed

FA 62 panels

FA B feed
58

FA A
54
FA B
50

FSP
45

41 A

37 B
Filler panels
33 A
or

29 Fuse distribution B
panels
A
25
B
21

FA A FA B Filter panel
filter unit filter unit
fuse A fuse B 16

Spare
fuse Filler panel
holder

DMS-100 International Technical Specification BCS40i and up

13–38 Power requirements

DC-DC converters
The DMS-100 Family uses most of the input power at voltages other than
–48 V dc. The voltages are derived from the nominal –48 V dc by dc-dc
converters in the shelf or frame in which they are used. Although these
voltages are dictated by the technology used, most of them are standardized
to +5 V, +12 V, +15 V, or +24 V.
Converter features
Several different types of dc-dc converters are required to meet the voltage
and current requirements of the DMS-100 switch. All of the dc-dc
converters used in the DMS-100 switch have three features:
• Isolation between battery return and logic ground.
• Regulation of the output voltages against changes in load and/or battery
voltage, within specified limits.
• Protection against overload of the outputs.

AC power distribution
Protected AC sources
The only protected 60 Hz 120 V ac power required in the DMS-100 Family
System is for the Maintenance and Administration Position (MAP) VDU,
Technical Assistance (TAS) data sets, analog recorded announcement
equipment and cooling units. The protected ac source is derived from –48 V
dc through separate 500-VA inverters. Inverter power may be provided for a
MAP associated printer, TTY and other input/output devices at the request
of the operating company.
Outside plant module power requirements
The OPM cabinet electrical system consists of power distribution
equipment, two rectifiers, and batteries. The OPM uses 30 A, single phase,
220 V, 60 Hz, commercial ac supply. Backup batteries may be provisioned
to provide power during ac failure conditions. The batteries may be sized
(200 AH) to provide the power required to maintain OPM operation for up
to 8 hours at a traffic level of approximately 5 ccs/line.
An emergency generator plug is provided for attachment of a 220-V ac
generator to supply power during extended commercial ac failure. Any
emergency generator attached to the OPM must be capable of supplying an
average power of 1500 watts with peaks to 4000 watts.
The cabinet ground bar, located in the end access compartment, is to be
connected to a ground rod provided by the user in accordance with local
utility codes. Maximum recommended ground to earth resistance is 25 Ω..
There are eight terminations on the ground bar. These consist of the
protector block ground connection, electronic equipment ground, the
incoming ac main ground, a connection to the ground rod and finally, four
incoming outside plant cable sheath grounds.

PLN-5001-001i Standard 02.02 April 1997

 Power requirements 13–39

Lighting and AC receptacles

The distribution of commercial 115 V, 60 Hz power for normal lighting and
convenience outlets throughout the DMS-100 Family office is via
operating-company furnished, wall-mounted ac distribution centers
containing circuit breakers. The PDC is not involved in ac power
distribution.
Two types of circuits are provided for lighting. One is used for normal
lighting and the other for low-intensity lighting and convenience outlets.
Normal lighting
(Where center aisle lighting, or frame mounted lighting fixtures are
available.)
Frame mounted lighting for the DMS-100 Family equipment area consists of
fluorescent tubes mounted in lighting fixtures at the top front of every
DMS-100 Family bay. Rear bay lighting using fixtures at the top rear of the
bay can be provided on an optional basis. All bay lighting fixtures are wired
to commercial 115 V, 60 Hz circuits and are directly controlled by switches
mounted in lineup end guards. The illumination level in the maintenance
aisles of the equipment area is 24–30 footcandles maintained at the
equipment floor level.
Center aisle lighting consists of 2 foot, 4 foot or 8 foot lighting fixtures
mounted in the front and rear center of the aisles from either frame mounted
cantilever support or auxiliary framing.
The lighting in the maintenance area where the person-machine interface
devices (for example, VDUs or TTYs) are located will normally be standard
overhead lighting as arranged by the operating company. This lighting does
not form part of the DMS-100 Family.
Low-intensity lighting
Low-intensity lighting fixtures are wired to an essential (operating-company
supplied) 115 V, 60 Hz supply so that minimum lighting is available if
commercial power fails. (The transfer circuitry is operating-company
supplied.) Low-intensity lighting consists of one front aisle light fixture
and, when provided as an option, one rear aisle light fixture for each lineup.
Normal lighting fixtures are used for the low-intensity lighting.
Low-intensity lighting is directly controlled from a wall-mounted switch at
the office entrance.
AC receptacle
A duplex receptacle will be mounted in the end guards of each completed
lineup. A duplex receptacle may also be mounted on every third frame, on
front and rear, of a lineup on an optional basis.

DMS-100 International Technical Specification BCS40i and up

13–40 Power requirements

Power and ground interfacing

Dedicated power plant
When the dc power plant is dedicated to DMS-100 use, the preferred
arrangement of power and grounding is shown in figure 13–15. This
arrangement has three features:
• Ground referencing of the power plant battery is obtained via PDC 00.
• System frame grounding conforms to the arrangement described in
Framework ground arrangements for non-ISG installations.
• The vertical separation between the DMS-100 switch and the power
plant should be minimized but is not limited to a specific distance.

PLN-5001-001i Standard 02.02 April 1997

 Power requirements 13–41

Figure 13–15
Recommended power plant configuration

ac ground

Connections from DMS framework ground and from

CO ground logic return planes (as required)

PDC Other
00 PDC Logic
misc return
grd (as req)

Battery Battery Conv

return return

Vertical All frames

riser are isolated

750
MCM

Battery Battery Power plant

return with isolated
battery return
Framework
positive 48V negative
ground

Note: The power plant may be in a different location than the DMS.

Power plant sharing

Two types of situations will normally be encountered when the DMS-100
switch is required to share a power plant with co-located switching systems:
• Sharing with electronic switching systems that use an isolated system
ground plane
• Sharing with electro-mechanical switching systems that use an integrated
system ground plane.

DMS-100 International Technical Specification BCS40i and up

13–42 Power requirements

Shared power plant has the three applications:

• isolated return (figure 13–16)
• non-isolated battery return (figure 13–17)
• ground window/single point ground (figure 13–18).

Isolated ground planes

Systems that use an isolated system ground plane are characterized by the
presence of a ground window. The requirements for interfacing these
systems with the CO ground network are usually more stringent than those
of the DMS-100 switch. Therefore, the DMS-100 switch must conform to
the rules established for the co-located system. Internal grounding of the
DMS-100 switch will not require any modification. However, it is probable
that the co-located system rules will require isolation of all DMS-100 frames
from contact with incidental grounds and also impose restrictions on the
distance of the DMS-100 frames from the “ground window.” Figure 13–16
shows a typical arrangement.
Integrated ground planes
With integrated ground plane formats, no deliberate attempt is made to
separate system circuit grounds, battery returns or framework from multiple
contact with the CO ground network. DC power plants serving systems with
this type of ground plane do not have the power plant battery isolated from
local CO ground. When sharing power with such systems, the DMS-100
system should follow the arrangement shown in figure 13–18:
• The framework ground reference cable should be bonded at the same
point on the CO ground network as the power plant battery return.
• The vertical separation between frames and the framework
ground/battery return bond on the CO ground must not exceed one floor.
• A physical separation of 7 feet (2 m) should be allowed between all
other equipment not referenced to the same point on the CO ground as
the DMS-100 framework. All frames should be isolated from contact
with incidental grounds.

PLN-5001-001i Standard 02.02 April 1997

 Power requirements 13–43

Figure 13–16
Specific isolated battery return configuration shown here with MDG/ground window
arrangement

DMS logic return network

Logic return LRE
equalizer bus
DMS framework ground network
FGE
Framework
ground
equalizer bus

from ac cabinet
PDC
ac ground Logic
00
return

Other PDC Battery Conv

(as required) return
–48V return
Vertical All frames
riser are isolated

CO MGB
ground
Battery Battery
return Power plant
misc
grd positive 48V negative
Grounding Framework
electrode ground
conductor
750 MCM

DMS-100 International Technical Specification BCS40i and up

13–44 Power requirements

Figure 13–17
Configuration with non-isolated battery return

ac ground

Connections from DMS framework ground and from

CO ground logic return planes (as required)

PDC Other
00 PDC Logic
misc return
grd (as req)

Battery Battery Conv

return return

Vertical All frames

riser are isolated

750
MCM

Battery Battery Power plant

return with isolated
battery return
Framework
positive 48V negative
ground

PLN-5001-001i Standard 02.02 April 1997

 Power requirements 13–45

Figure 13–18
Shared power plant

Vertical riser (Isolated) DMS-100 family system

750 MCM (Isolated from contact with ground)

DMS Framework ground reference

SPG Equipment framework
CO ground
GRD
bus PDC

–48 V

Misc &
other +48 V
equipment
on this Converter
floor

Battery
reference
750 MCM Feeds to other PDCs

Feeds to other sys-

tems
CO that share power
GRD
bus
48 V
Fmwk grd + –
(Isolated) Power plant
No. 6 AWG minimum

Building
principal
ground

Note: Battery (–48) feeds are omitted for clarity.

DMS system must not be located more than one floor away from the battery main ground refer-
ence point.

DMS-100 International Technical Specification BCS40i and up

 14–1

Documentation
A variety of document types are used to support and maintain an accurate
record of the design and capabilities of the DMS-100 Family. These
document types include job specific, non-proprietary hardware, systems,
proprietary, installation, and various other documents. This section lists and
describes these different document types.
Documentation media
Northern Telecom’s documentation for the DMS-100 Family and the DMS
SuperNode switching system is available on HELMSMAN CD-ROM, paper,
microfiche, or microfilm form. User documentation is included when a
switching system is shipped. Northern Telecom’s primary documentation
offer is CD-ROM, however, the user may choose a mixture of paper and
microfiche. Software listings of each specific BCS program are available
only in microfiche.
Documentation ordering
Documentation can be ordered in one of two ways:
• Documentation can be ordered through the NT86XX questionnaire at
customer information (CI) time of the switch or any extension (growth)
to an existing switch in accordance with the purchasing agreement.
• Documentation may be purchased by submitting a purchase order for
documents to the Northern Telecom merchandise order specialist.
Documentation standing order services can also be ordered through the
merchandise order specialist.
Documentation catalogs
Documentation catalogs, giving document titles and prices, will be released
annually.
Documentation structure
There are three types of standard documentation provided with DMS-100
Family Systems:
• Job Specific Documentation on page 14–7
• Non-Proprietary Hardware Documentation on page 14–8
• Systems documentation on page 14–9.

DMS-100 International Technical Specification BCS40i and up

14–2 Documentation

Job specific and non-proprietary hardware documents are organized

according to the modular documentation system (MDS). The MDS
documents are associated with Northern Telecom product engineering codes.
Modular documentation system
The modular documentation system (MDS) structure complements the
modular nature of the system. The MDS has four functions:
• To produce documents whose contents satisfy the specific needs of their
most frequent users, and the general needs of all users.
• To be technology-independent – changes in the technology used in the
product must not affect the documentation system.
• To provide a document identifier (prefix) which relates to the type of
information contained within the document and to aid a user when
searching for a specific type of information.
• To provide a document identifier which relates to the product identifier
and to aid a user in the search for information on a product.
Characteristics of MDS
MDS has a “top down” structure. Documents are stratified to conform to
each level of the product structure, such as system, subsystem, or module
(see figure 14–1.)

PLN-5001-001i Standard 02.02 April 1997

 Documentation 14–3

Figure 14–1
Modular documentation system structure

Product
system
Documentation

System level Hardware Software

(system index)

Subsystem lev- Hardware Software

el (intraconnect subsystems subsystems
schematic)

Frame, shelf, Frames, Firmware modules

panel level shelves, software modules
(intraconnect panels
schematic)

Firmware segments
Circuit pack level Circuit packs software programs
(circuit schematic)

ROMs,
Component level hybrids

MDS documents describe a product as a module; that is, as something which

stands alone in its internal functions and whose interfaces with the rest of the
system (input and output signals, and connections) are defined in terms of
this module only. As a result, the module and its documentation can be
changed as required without affecting the rest of the system.

DMS-100 International Technical Specification BCS40i and up

14–4 Documentation

MDS document identifiers

Each hardware product of the DMS 100 Family is identified by a unique
product engineering code (PEC). A PEC consists of eight characters and
has a specific structure:
(Prefix) (Base) (Suffix)
NT NANN XX
NT AANN XX
Where: NT is Northern Telecom
N is numeric
A is alphabetic
X is either numeric or alphabetic
Examples of PECs are NT0X25AA, NT4X25BH and NT6X10AC.
• Prefix: The prefix NT is assigned to all codes, thereby identifying this
item as a Northern Telecom product.
• Base Code Group: Uniquely identifies a family of products.
Associated hardware documents bear an identical base code.
• Suffix: A 2-character suffix uniquely identifies each member within a
family of products. It is assigned in sequence: AA, AB, AC and 01, 02,
03. Combination alphabetic-numeric suffixes are allowed, but are not
presently used.
The documents prepared to support each PEC are identified in a similar
manner:
(Prefix) (Base) (Suffix) (Stream) (Issue)
AA NANN XX NN NN
• Prefix: The Alpha-Alpha prefix identifies each type of document. An
Interconnect Schematic has the prefix IS, Assembly Drawing is AD,
General Specification has the prefix GS, and Module structure has the
prefix MS.
• Base Code: The base code is identical to the associated PEC.
• Suffix: If the suffix is present, it will be the same as the suffix of the
PEC. Some documents are written for more than one very similar PEC.
Such an example is GS6X17, which is applicable to the NT6X17AA,
NT6X17AB, NT6X17AC, and the NT6X17AD.

PLN-5001-001i Standard 02.02 April 1997

 Documentation 14–5

• Stream: The stream of a document is changed when major revisions to

the features or operations of the PEC are involved, but would remain
unchanged for minor enhancements or refinements to a product.
• Issue: The issue of the document is changed whenever minor revisions,
corrections or improvements are made to a product or document.
Within this set, all documents bear the same base (see table 14–1).

Table 14–1
Associated documents
PEC code Description

NT3X31AB Product (The data store shelf)

IS3X31 The interconnect schematic for the data store shelf
AD3X31AB The assembly drawing for the data store shelf
MS3X31AB The module structure for the data store shelf

Changes, issues, and releases are controlled and recorded by the change
control system. Two customer documents contain information related to this
system. They are the document index (DI) and the office inventory record
(OIR). In the DI, the customer is informed of the documents which are
being provided for each office and the issues of these documents. The
documents defined as requirements in the DI are those that are compatible
with the associated equipment. In the OIR, the products supplied against
each order are listed by product engineering code (PEC), title, release
number, and quantity installed. The OIR is intended to be kept (by the
customer) as an office log of changes.
Northern Telecom publications
Northern Telecom publications (NTPs) are issued to document various
aspects of the DMS-100 Family of switches and in general cover several
disciplines:
• Administration
• Engineering
• Installation and testing
• Operations
• Provisioning
• Translations
• Maintenance.

DMS-100 International Technical Specification BCS40i and up

14–6 Documentation

DMS-100 Family Guide to Northern Telecom Publications, 297-1001-001 is

maintained as a current index of all NTPs and lists the publications in the
following ways:
• Numerically by ten-digit NTP number as shown in chapter 2
• Alphabetically by title as shown in chapter 3
• Product guides, numerically, as shown in chapter 4
• Planning and engineering documents, as shown in chapter 5
• Installation documents, as shown in chapter 6
• Administration and translations documents, as shown in chapter 7
• Operations and maintenance documents, as shown in chapter 8
• Reference documents, as shown in chapter 9

In chapters 4 through 9 the system level documents are listed in the first
section of the chapter. Subsequent sections are listed in alphabetical order
by product name. Within each section the documents are listed in numerical
order.
Publications are identified in chapter 2 of DMS-100 Family Guide to
Northern Telecom Publications, 297-1001-001 by NTP number, title,
release, BCS, and status.
NTP index
This is an explanation of the column headers used in the chapter 2 table of
DMS-100 Family Guide to Northern Telecom Publications, 297-100-001:
Number The standard ten-digit NTP number appears in this column. All
DMS-100 Family publications are in division 297.
Title This column contains the title of the NTP.
Release This column contains two-part code consisting of a two-digit
stream number left of the decimal point, and a two-digit issue number to the
right of the decimal point. The code is not printed on some NTPs; it will be
added when the NTP is reissued.
If an NTP is reissued with new information specific to one or more BCS
software releases, the stream number is increased by one. If the NTP is
reissued to make other corrections, the issue number is increased by one.
BCS This column contains the batch change supplement (BCS) number.
This is the release number of the software to which the NTP applies.
Status This column contains the document publication status:
PREL Preliminary

PLN-5001-001i Standard 02.02 April 1997

 Documentation 14–7

0STD Standard
Note 1: Some NTPs are rated STD N by means of an N suffix to the
NTP number on the document (for example, 297-2101-102N); however,
the term STD N is used in the index.
Note 2: Some earlier issues of NTPs used a three-part rating code such
as, 01D02. Those publications are considered DRAFT rated if the letter
is W, and STD N if the letter is D.
Job specific documentation
Documents are provided for a particular DMS-100 Family office with the
initial delivery of the system. These documents are office specific.
Document index
The document index (DI) is an index of all standard and job related
documents provided for each office and includes the issue of each document
supplied.
Office-inventory record
The office inventory record (OIR) contains the list of all the components of
a customer office, the quantity and the release. Input is from job
specifications and on-site equipment audits. The OIR is used for keeping
track of the contents of a particular office, change control and extended
warranty service.
Office feature record
The office feature record (OFR) contains a short description of each
PROTEL software subsystem resident in a particular office and a list of
feature packages provided in the software load.
Central office job specifications
The main function of the job specification is to list the materials needed to
assemble and install a job. There are three types of job specifications:
material requirement, configuration, and cable. After the job specification
has been used by manufacturing to assemble the job, and by the installer to
install the job, it is no longer required since the job drawings contain all the
information about the contents of the office.
Central office job drawings
Job drawings are generated by customer engineering job specifications, job
information memorandum (JIM) or 88K orders. Job drawings are
permanent records of what is in a particular office and indicate the location
of components when the positioning is variable. A breakdown of the
drawings for a standard job would be up to 20 job drawings, six facility
drawings showing floor plan, lighting, cable racks, ceiling inserts,

DMS-100 International Technical Specification BCS40i and up

14–8 Documentation

earthquake bracing and grounding schematics, one distributing frame (DF)

drawing and one transmission drawing.
Common systems drawings (as required)
These drawings portray equipment which is not part of the DMS-100 Family
equipment but is part of the installation, such as power or cable racking.

Non-proprietary hardware documentation

Hardware documentation consists of drawings and documents that depict
actual hardware configurations and interconnections.
Module structure (MS)
The module structure (MS) describes how to select equipment to engineer
features. MS updates occur in response to a new member within a family of
products.
Assembly drawings (AD)
Products that are the assembly of various elements may be pictorially
displayed on an assembly drawing (AD). The AD, created by equipment
design or mechanical design, is required for manufacturing to assemble and
inspect the product and for on-site installation and maintenance.These
drawings show the construction of frames, shelves, and other miscellaneous
equipment. These drawings also illustrate the placement of circuit packs in
a drawer, drawers in a module, and modules in a frame.
Interconnect schematics (IS) or functional schematics (FS)
The functional schematic (FS) applies to electromagnetic equipment and has
now been largely replaced by the interconnect schematic (IS). The FS
illustrates functional interconnectivity between sub-assemblies of the
product.The IS describes connectivity between modules by using block
diagrams in which functional blocks are joined by lines. Each line
represents a set of connections. Detailed connections are identified in
tabular form using separate tables to group similar connections. Notes are
used as required to supplement the block diagram and detailed tabular
information.
Cabling assignments (CA)
The cabling assignment (CA) drawing defines the specific interconnections
among products within a system. It includes information on both the
originating and terminating ends of a cable, the specific type of cable, and
the number of leads required.
Cabling assignment drawings also describe drop lengths of cables and
pin-to-pin connections between frames and are used to engineer offices. CA
are one of the key documents used in the creation of job specifications. The
CA drawings are necessary documentation for the assembly plant, installer
and customer.

PLN-5001-001i Standard 02.02 April 1997

 Documentation 14–9

Systems documentation
Northern Telecom publications
NTPs are required to engineer, operate, and maintain a Northern Telecom
product. NTPs describe the DMS-100:
• System description—Describes the system, its features, and how it
operates.
• Engineering, equipment application and ordering information—Contain
the information required to select the proper equipment when planning a
new office or expanding the facilities of an existing office.
• System/equipment performance specification—Written for engineers to
enable them to assess the applicability of the system or equipment to
their requirements.
• Identification, installation, and tests—Written for technicians of
telephone companies whose duties include installation, field adjustments,
and tests that are necessary before turnover for regular operation.
• Operating procedures—Written for all field personnel who operate
equipment. The contents has four parts:
— Identification of controls and indicators and their function
— Step-by-step procedures for operating the controls
— Alternative methods of operation under trouble conditions
— Recommended methods for maintaining service under trouble
conditions
• Simple trouble test and repair procedures—Written for operating
company field service technicians and aimed at quick restoral of service
without extensive test, adjustment, and repair procedures.
• Preventive in-service maintenance—Written for operating company
technicians:
— Recommended time intervals between tests and adjustments
— Detailed test and adjustment procedures which indicate limits at or
beyond which corrective adjustment or repair must be done
— Special procedures for maintenance and cleaning of floors, offices
and equipment which is likely to affect the operational reliability of
the equipment.
• Traffic—Written for operating company personnel and include traffic
provisioning, translations, and administration.
• Maintenance center procedures—Document tests and adjustments that
are required on equipment or apparatus prior to their use as replacement
items in the field.

DMS-100 International Technical Specification BCS40i and up

14–10 Documentation

Peripheral module software release document

The peripheral module software release document addresses the changes
associated with a given software release for peripheral equipment. The
method of applying the software is described.
BCS preparation guide
This guide identifies new features that have a potentially significant impact
on the operation of other features.

Optional documentation
Northern Telecom is expanding the available DMS-100 Family
documentation as described in this section.
Feature description manual (FDM)
The Feature description manual (FDM) contains brief descriptions of
DMS-100 Family features, and indexes of software packages.
The FDM contains the following information.
• Hardware requirements
• Feature impact summary table
• Feature descriptions
• Features listed by BCS
• Feature number to feature package and BCS cross–reference
• Feature package to feature number and BCS cross–reference
• Feature name to feature number, package and BCS cross–reference

Peripheral module software release document

The peripheral module software release document addresses the changes
associated with a given software release for peripheral equipment. The
method of applying the software is described.
DMS-100 family capacity manual
The DMS-100 Family capacity manual (297-1001-304) provides
information related to the capacities of individual switch components for the
DMS-100 installations that use either the NT40 or DMS SuperNode
architecture. This manual contains information concerning capacities (call
attempts and traffic), real time models, engineering and monitoring
guidelines, load service curves, and overload controls.
TRAVER
This Technical assistance manual (TAM-1001-002) describes how the
Translation and Routing Verification (TRAVER) tool allows examination of
the translation and routing data that is used for a particular call.

PLN-5001-001i Standard 02.02 April 1997

 Documentation 14–11

Proprietary documentation
The documents described in this section identify proprietary documents.
Proprietary information list
The following list of proprietary documents are described in proprietary
documentation:
• Release control record (RCR)
• Detailed assembly drawing (AD)
• Program documentation index (PDI)
• Central control software program listings
• Program description information
• Central control cross–references
• XPM peripheral module software program listings
— Program listings
— cross–references
— Directories
• Operating manuals
— Support operating system (SOS) loader reference manual
— DMS-100 Family Software update controller user manual
• Programmers manuals
• Software debug manuals
• DMS-100 Family system description
• Network integrity fault analysis guidelines
• Technical assistance manuals (TAM)
• Installation manuals

Release control record

Northern Telecom maintains a release control record (RCR) by PEC which
identifies issue numbers for all drawings associated with DMS-100 Family
equipment. This proprietary document also records equipment issue
compatibility information.
Detailed assembly drawing (DAD)
The circuit pack assembly drawings (AD) indicate connections of
faceplate-mounted components, illustrate mounting arrangements which are
not apparent, and display stamping and lettering. These drawings are
provided down to shelf panel level.

DMS-100 International Technical Specification BCS40i and up

14–12 Documentation

Program documentation index (PDI)

The program documentation Index (TID-1001-000), common to all the
DMS-100 Family software versions, describes the proprietary documents of
the software documentation package. It also describes how to use the
documentation and on-line tools to ascertain specific information:
• which program elements are loaded into a given office
• the physical locations of various programs and data elements in a given
office.
Central control software program listings
Program listings are generated from data files maintained by Northern
Telecom. The listings contain all the instructions for the program modules
and may contain supplementary information defining the function of the
module and how the module unit relates to the other units and the overall
system. Program listings are produced for each version of the software
library released.
Program description information
DMS-100 Family programs are written in a high-level language called
PROTEL. As with other high-level languages, the programs are largely
self-documenting with the code itself the primary body of the explanation.
In addition to the code, each module may contain a prologue or overview of
the function of the module. Comments embedded within the code clarify the
code usage.
Central control cross references (subsystem SEXREF, GXREF)
This document lists all declarable PROTEL symbols and the program
elements which invoke them. As part of the program listings, it is produced
in the form of microfiche for each version of the library software released.
XPM peripheral module firmware/software listing
The DMS-100 Family XPM peripheral module firmware/software listing is
documented from data files maintained by Northern Telecom. Three
documents are produced from these files:
• Program listings including explanatory comments
• Cross references
• Directories

Program listings, cross reference, and directory are produced for each
version of the firmware/software released.
Program listings
The XPM software is written in assembler code. Line peripheral code is
assembled using a relocatable assembler; the rest of the PMs use an absolute

PLN-5001-001i Standard 02.02 April 1997

 Documentation 14–13

assembler. The program listings provided on the fiche are assembled source
listings.
Cross references
For the XPM software that uses the absolute assembler, a cross reference is
provided on a subsystem basis. For XPM firmware/software that uses the
relocatable assembler, a cross reference consists of an alphabetical list of all
the labels in the subsystem or module listing.
Directories
A directory exists only for the XPM firmware/software that uses the
absolute assembler. The directory (label dictionary) is provided on a
subsystem basis. It consists of an alphabetical list of all the labels defined
within the subsystem.
Operating manuals
These manuals provide information on tools to implement and manage
updates to the DMS-100 and peripheral software loads.
SOS loader reference manual
The support operating system (SOS) loader reference manual contains
information common to all software versions.
The SOS loader reference manual gives detailed information for using
on-line tools to determine what modules are loaded in a specific office. It is
also used to determine the physical address of the program code and date
elements in a specific office
DMS-100 family software update controller user manual
The DMS-100 Family software update controller (DSU) user manual
describes how to use the DSU to implement and manage updates to
DMS-100 software loads.
Programmers manuals
This documentation common to all the software versions provides
information on the PROTEL language and supportive information on
machine architecture and operating system. It consists of six manuals:
• PROTEL Introductory Manual
• PROTEL Reference Manual
• DMS-100 Family central control complex guide 1 (machine architecture)
• DMS-100 Family central control complex guide 2 (user’s manual)
• XPM Assembler user’s manual
• XPM Pascal manual.

DMS-100 International Technical Specification BCS40i and up

14–14 Documentation

Software debug manuals

This set of documents common to all the software versions provides a guide
to the available debug tools:
• DMS-100 Synchronizable clock debug software
• DMS-100 debugging and measuring tools: a survey
• DEBUG and SWERR monitors
• New peripheral debugging
• I/O Query – user’s guide

DMS-100 family system description

This documentation provides a detailed description of the DMS-100 Family
hardware and software including DMS SuperNode software. Included are
discussions and detailed explanation of the hardware system, software
structure, and run-time organization. Also included are discussion of
PROTEL and other aspects of the software environment, such as the BCS
release process and the DMS-100 Family program patch system. The intent
of this documentation is to provide sufficient overview and background so
that a properly qualified person may, after absorbing this material, read and
understand the DMS-100 Family program listings.
Network integrity fault analysis guidelines
This manual provides a brief description of “integrity” in the DMS-100
switching system and the possible causes of integrity failures.
Trouble-shooting guidelines and approaches to correcting integrity failures
are also provided.
Technical assistance manuals
The Technical assistance manual (TAMs) provide DMS-100 Family
maintenance personnel with the information that is necessary for testing
software debugging tools in the field. These manuals describe the tools that
are contained on the TAS Non-Res tape (NTX181AA).
PMIST
The Peripheral module intercept system (PMIST) is a low level internal
diagnostic tool that records messages sent between the CC and the PMs.
This manual (TAM-1001-007) provides a description of, as well as
instructions for using PMIST. This TAM is used by maintenance personnel
for maintenance of the DMS-100 switch.
DISPCALL
This Technical assistance manual (TAM-1001-003) describes the display call
(DISPCALL) software tool and provides instructions for the proper use of
the tool. The manual is used by the maintenance personnel responsible for
maintaining the DMS-100 switch.

PLN-5001-001i Standard 02.02 April 1997

 Documentation 14–15

TAS non-res tool listing (TAM-1001-001)

The TAS non-res tool listing contains a list of the tools residing on the TAS
non-res tape.
PMDEBUG user guide (TAM-1001-004)
This TAM provides an introduction to PMDEBUG with definitions of
PMDEBUG levels and commands. Procedures are also provided to allow
specific XPM information to be displayed.
DEBUG user guide (TAM-1001-008)
This TAM describes the DEBUG utility and provides background
information and definitions of the DEBUG commands. It also contains a
detailed section about data store display.

Installation manuals
These manuals are used by DMS-100 Family equipment installation
personnel. They describe all the various tests that are applied before the
system is turned over to a telephone operating company. These manuals are
available under a separate installation agreement .

DMS-100 International Technical Specification BCS40i and up

 15–1

List of terms
This chapter expands and defines abbreviations used in this document. For
information on terms not defined in this chapter, refer to Glossary of Terms
and Abbreviations, 297-1001-825.
A-link
A signaling data link that connects service switching points (SSP) and
service control points (SCP) to signaling transfer points (STP). See also
service control point (SCP) or service switching point (SSP).
ANI
See automatic number identification (ANI).
application-specific unit (ASU)
A combination of hardware and software components that carries out a
particular function on the signals carried on the channel buses (C-bus) and
frame transport buses (F-bus) in a link peripheral processor (LPP).
Examples of ASUs are Ethernet interface units (EIU), CCS7 link interface
units (LIU7), and network interface units (NIU).
ASU
See application-specific unit (ASU).
automatic number identification (ANI)
A system whereby a calling number is identified automatically and
transmitted to the automatic message accounting (AMA) office equipment
for billing.
BCD
Binary coded decimal.
BCS
Batch change supplement.
BDW
Block descriptor word.

DMS-100 International Technical Specification BCS40i and up

15–2 List of terms

capability code
An address that allows a Common Channel Signaling 7 (CCS7) node to
identify itself by more than one point code. For example, each node of a
signaling transfer point pair is identified by the same capability code and by
individual capability codes. See also point code.
CB
See channel bank (CB).
C-bus
See channel bus (C-bus).
CC
Central control. On NT-40 based systems, the Central Control subsystem.
On SuperNode-based systems, the DMS-Core.
CCITT
See Consultative Committee on International Telephony and Telegraphy
(CCITT).
CCS
See common channel signaling (CCS).
CCS7
See Common Channel Signaling 7 (CCS7).
CCS7 link interface unit (LIU7)
A peripheral module (PM) that processes messages entering and leaving a
link peripheral processor (LPP) through an individual signaling data link.
Each LIU7 consists of a set of cards and a paddle board provisioned in one
of the link interface shelves of the LPP. See also link peripheral processor
(LPP).
central processing unit (CPU)
The hardware unit of a computing system that contains the circuits that
control and perform the execution of instructions.
central side (C-side)
The side of a node that faces away from the peripheral modules (PM) and
toward the central control (CC). Also known as control side. See also
peripheral side (P-side).
channel bank (CB)
Communication equipment performing the operation of multiplexing. A
channel bank is used typically for multiplexing voice grade channels.

PLN-5001-001i Standard 02.02 April 1997

 List of terms 15–3

channel bus (C-bus)

A proprietary Bell-Northern Research (BNR) duplicated 10-bit time division
multiplexed bus running at 4 MHz. The C-bus interconnects network
interface units (NIU) with link interface units (LIU).
CI
See command interpreter (CI).
C-link
The signaling data link (SDL) that connects the mates of a signaling transfer
point (STP) pair.
CLLI
Common language location identifier.
CM
See computing module (CM).
command interpreter (CI)
A component in the Support Operating System (SOS) that functions as the
main interface between machine and user. Its principal roles include the
following:
• reading lines entered by a terminal user
• breaking each line into recognizable units
• analyzing the units
• recognizing command-item numbers on the input lines
• activating these commands

common channel signaling (CCS)

A signaling method in which information relating to many labeled messages
is transmitted over a single channel using time-division multiplex (TDM)
digital techniques.
Common Channel Signaling 7 (CCS7)
A digital message-based network signaling standard, defined by the CCITT,
that separates call signaling information from voice channels so that
interoffice signaling is exchanged over a separate signaling link.
computing module (CM)
The processor and memory of the dual-plane combined core (DPCC) used
by DMS SuperNode. Each CM consists of a pair of CPUs with associated
memory that operate in a synchronous matched mode on two separate
planes. Only one plane is active; it maintains overall control of the system
while the other plane is on standby.

DMS-100 International Technical Specification BCS40i and up

15–4 List of terms

connectionless signaling
A type of signaling in which no fixed end-to-end connection is associated
with the call. The route followed by the information and signaling between
the originating and terminating subscriber is not fixed and can change from
one message to the next. For example, signaling used to access a database
for 800-number translations and maintenance signaling messages between
signaling points are considered connectionless signaling. Also known as
transaction services.
connection-oriented signaling
A signaling process in which a fixed end-to-end path is established for the
call. The signaling protocol establishes a fixed path although the signaling
itself can travel by way of different paths for the duration of the call. All
information associated with the call follows a fixed path even though the
signaling itself is not connection-oriented. Also known as trunk signaling.
Consultative Committee on International Telephony and Telegraphy (CCITT)
Consultative Committee on International Telephony and Telegraphy
(CCITT) operates under the auspices of the United Nations and is the forum
for international agreement on recommendations for international
communication systems.
CPU
See central processing unit (CPU).
C-side
See central side (C-side).
DCE
See digital carrier equipment (DCE) frame.
DDU
See disk drive unit (DDU).
destination point code (DPC)
A Common Channel Signaling 7 (CCS7) term defining the termination of a
signaling message. See also originating point code (OPC).
digital carrier equipment (DCE) frame
An equipment frame that houses digital carrier modules (DCM).
digital trunk controller (DTC)
A peripheral module (PM) that connects DS30 links from the network with
digital trunk circuits.

PLN-5001-001i Standard 02.02 April 1997

 List of terms 15–5

digital trunk equipment (DTE) frame

A frame containing up to two dual-shelf digital trunk controllers (DTC).
directory number (DN)
The full complement of digits required to designate a subscriber’s station
within one numbering plan area.
DIRP
Device independent recording package.
disk drive unit (DDU)
A hardware device that consists of a disk drive and a power converter card
installed in an I/O equipment (IOE) frame.
D-link
A signaling data link that connects a secondary signaling transfer point
(STP) of one STP pair to a primary STP pair in the network.
DMS-bus
The messaging control component of the DMS SuperNode processor. The
DMS-bus components are a pair of message switches (MS).
DMS-core
The call management and system control portion of the DMS SuperNode
processor. The DMS-core portion consists of a computing module (CM) and
a system load module (SLM).
DLH
Distributed line hunt.
DMS-link
The networking software of the DMS SuperNode processor. The DMS-link
software consists of open and standard protocols that allow the DMS
SuperNode to function in a multivendor environment.
DMS SP/SSP
See signaling point/service switching point (SP/SSP).
DMS-STP
See DMS SuperNode Signaling Transfer Point (DMS-STP).
DMS-STP/SSP INode
See DMS SuperNode Signaling Transfer Point/Service Switching Point
Integrated Node (DMS-STP/SSP INode).

DMS-100 International Technical Specification BCS40i and up

15–6 List of terms

DMS SuperNode
A central control complex (CCC) for the DMS-100 switch. The two major
components of DMS SuperNode are the computing module (CM) and the
message switch (MS). Both are compatible with the network module (NM),
the I/O controller (IOC), and XMS-based peripheral modules (XPM).
DMS SuperNode SE (SNSE)
A smaller version of DMS SuperNode designed to service smaller offices
(maximum 20 000 lines). It is based on existing SuperNode technology and
can be used in all existing applications of SuperNode, including Common
Channel Signaling 7 (CCS7) and international. SNSE supports all
SuperNode software features at a reduced call processing capacity.
DMS SuperNode Signaling Transfer Point (DMS-STP)
A high-throughput data packet switch providing connectivity between the
nodes of a Common Channel Signaling 7 (CCS7) network.
DMS SuperNode Signaling Transfer Point/Service Switching Point Integrated
Node (DMS-STP/SSP INode)
A CCS7 integrated node that combines the functionality of a signaling
transfer point (STP) and a service switching point (SSP). The integrated
node consists of the DMS-core, DMS-bus, I/O controller (IOC), office alarm
system (OAS), JNET or ENET, link peripheral processors (LPP), and
peripheral modules (PM) such as digital trunk controllers (DTC), line group
controllers (LGC), and maintenance trunk modules (MTM).
DN
See directory number (DN).
DNPC
See dual network packaged core (DNPC).
double shelf network (DSN)
A network with one network plane on a single shelf of a double shelf
network equipment (DSNE) frame, permitting two complete networks for
each plane in a single bay.
double shelf network equipment (DSNE) frame
A frame that packages one network plane on a single shelf, permitting two
complete networks for each plane in a single bay.
DPC
See destination point code (DPC).

PLN-5001-001i Standard 02.02 April 1997

 List of terms 15–7

DPCC
See dual-plane combined core cabinet (DPCC).
DS
Data store contains transient information for each call, as well as customer
data and office parameters.
DS-0
A protocol for data transmission that represents one channel in a 24-channel
DS-1 trunk.
DS-0A
An asynchronous DS-0. See DS-0.
DS-1
The 8-bit 24-channel 1.544-Mbit/s digital signaling format used in the
DMS-100 Family switches. The DS-1 signal is the North American
standard for digital trunks. It is a closely specified bipolar pulse stream.
DS-1 carries 24 information channels of 64 kbit/s each (DS-0s).
DS30
A 10-bit 32-channel 2.048-Mbit/s speech-signaling and message-signaling
link as used in the DMS-100 Family switches.
DS30A
A 32-channel transmission link between the line concentrating module
(LCM) and controllers in the DMS-100 Family switches. DS30A is similar
to DS30, though intended for use over shorter distances.
DS512 fiber link
The fiber optic transmission link implemented in the DMS SuperNode
processor. The DS512 is used for connecting the computing module (CM)
to the message switch. One DS512 fiber link is the equivalent of 16 DS30
links.
DSN
See double shelf network (DSN) or dual shelf network.
DSNE
See double shelf network equipment
DTC
See digital trunk controller (DTC).
DTE
See digital trunk equipment (DTE).

DMS-100 International Technical Specification BCS40i and up

15–8 List of terms

dual network packaged core (DNPC)

The basic element of the DMS-100 switch. The DNPC is a two-bay unit
containing a central control complex (CCC) and two switching network
modules (NM).
dual-plane combined core cabinet (DPCC)
One of the three cabinet models for the DMS SuperNode processor. The
DPCC contains two message switches and a system load module (SLM).
dual shelf network (DSN)
Also referred to as the junctored network (JNET).
EIU
See Ethernet interface unit (EIU).
EMC
See enhanced multipurpose cabinet (EMC).
ENET
See enhanced network (ENET).
enhanced multipurpose cabinet (EMC)
A cabinet containing one or more single shelf link peripheral processors
(SSLPP).
enhanced network (ENET)
A channel-matrixed time switch that provides pulse code modulated voice
and data connections between peripheral modules (PM). ENET also
provides message paths to the DMS-bus components.
EOF
End of file (tape trailer label).
EOT
End of tape.
Ethernet interface unit (EIU)
The unit that connects the DMS SuperNode to the local area network.
F-bus
See frame transport bus (F-bus).
F-bus tap
See frame transport bus (F-bus) tap.

PLN-5001-001i Standard 02.02 April 1997

 List of terms 15–9

frame supervisory panel (FSP)

A hardware device that accepts the frame battery feed and ground return
from the power distribution center (PDC). The FSP distributes the battery
feed, by means of subsidiary fuses and feeds, to the shelves of the frame or
bay in which it is mounted. The FSP also contains alarm circuits.
frame transport bus (F-bus)
An 8-bit bus that provides data communications between a link interface
module (LIM) and the application-specific units (ASU) that are provisioned
in a link peripheral processor (LPP) cabinet or frame. To ensure reliability,
two load-sharing F-buses are provided in an LPP. Each F-bus is dedicated to
one of the two LIM units.
frame transport bus (F-bus) tap
A facility that provides messaging access to a frame transport bus (F-bus).
The tap is either part of the F-bus rate adapter card used by the link interface
module (LIM) or is part of the CCS7 link interface unit (LIU7). See also
frame transport bus (F-bus).
FSP
See frame supervisory panel (FSP).
global title (GT)
An application address that does not explicitly contain the necessary
information that would allow routing by the signaling connection control
part (SCCP) of the message transfer part (MTP). The SCCP global title
translation (GTT) function is required to translate a GT into a valid network
address.
global title translation (GTT)
The process that translates an application-specific address (such as a dialed
800 number) into the Common Channel Signaling 7 (CCS7) network
address, usually that of the appropriate service control point (SCP).
GT
See global title (GT).
GTT
See global title translation (GTT).
IAA
Inter administration accounting.
ICAMA
International centralized automatic message accounting.

DMS-100 International Technical Specification BCS40i and up

15–10 List of terms

ICR
International call recording.
IDTC
See international digital trunk controller (IDTC).
INode
See integrated node (INode). See also DMS SuperNode Signaling Transfer
Point/Service Switching Point Integrated Node (DMS-STP/SSP INode).
integrated node (INode)
A combination of a DMS SuperNode Signaling Transfer Point (DMS-STP)
and a DMS Signaling Point/Service Switching Point (DMS SP/SSP). It has
all the functions of both, and requires fewer frames and cabinets.
international digital trunk controller (IDTC)
A digital trunk controller (DTC) that acts as an interface between a DMS
switch and PCM30 trunks. See also, digital trunk controller (DTC), and
PCM30 digital trunk controller (PDTC).
interperipheral connection (IPC)
A connection in the interperipheral message link (IPML) in common
channel interoffice signaling. Two IPCs can share the message handling
load.
IOC
See I/O controller (IOC).
I/O controller (IOC)
An equipment shelf that provides an interface between up to 36 I/O devices
and the central message controller (CMC). The IOC contains a peripheral
processor (PP) that independently performs local tasks, thus relieving the
load on the CPU.
IOD
See I/O device (IOD).
I/O device (IOD)
A device that allows data to be entered into a data processing system,
received from the system, or both.
IOE
See I/O equipment (IOE) frame
I/O equipment (IOE) frame
A frame that houses I/O devices.

PLN-5001-001i Standard 02.02 April 1997

 List of terms 15–11

IPC
See interperipheral connection (IPC).
ITOPS
International traffic operator position system.
JF
Journal file. A utility that records changes to the datafill tables of the
DMS-100 family switches. The JF provides a means of restoring the tables
if it is necessary to reload office software from a backup source.
JNET
See junctored network (JNET).
junctored network (JNET)
A time-division multiplexed system that allows for switching of 1920
channels per network pair (fully duplicated). Additional channels are
established through the use of external junctors, internal junctors, and a
digital network interconnecting (DNI) frame. Channels then can be routed
directly, or use alternate routing, through the use of junctors, a DNI frame,
and software control. Capacity for a DMS-100 switch is 32 network pairs or
61 440 channels (1920 channels × 32 network pairs).
LEN
Line equipment number. A seven digit functional reference that identifies
line circuits. The LEN provides physical location information on equipment
such as site, frame number, unit number, line subgroup (shelf), and circuit
pack.
LIM
See link interface module (LIM).
link
• In a DMS switch, a connection between any two nodes.
• A four-wire group of conductors providing transmit and receive paths for
the serial speech or message data between components of DMS-100
Family switches. Speech links connect peripheral modules (PM) to the
network modules (NM). Message links connect NM controllers or I/O
controllers (IOC) to the central message controller (CMC).
• A logical switched virtual circuit (SVC). Up to 256 logical SVCs are
carried on a physical X.25 communication cable.
link interface module (LIM)
A peripheral module (PM) that controls messaging between link interface
units (LIU) in a link peripheral processor (LPP). The LIM also controls
messages between the LPP and the DMS-bus component. An LIM consists

DMS-100 International Technical Specification BCS40i and up

15–12 List of terms

of two LIM units and two frame transport buses (F-bus). The two LIM units
operate in a load-sharing mode with each other. See also frame transport bus
(F-bus), link peripheral processor (LPP), and local message switch (LMS).
link interface shelf (LIS)
A shelf in a link peripheral processor (LPP) that houses application-specific
units (ASU) and associated power converters.
link interface unit for CCS7 (LIU7)
See CCS7 link interface unit (LIU7).
link peripheral processor (LPP)
The DMS SuperNode equipment frame or cabinet that contains two types of
peripheral modules (PM): a link interface module (LIM) and one or more
application-specific units (ASU). See also application-specific unit (ASU),
CCS7 link interface unit (LIU7), and link interface module (LIM).
linkset
• A group of links related to one application instance.
• A collection of links connecting two adjacent signaling points in CCITT
no. 6 signaling (N6), common channel interoffice signaling no. 6
(CCIS6), and Common Channel Signaling 7 (CCS7).
link status signal unit (LSSU)
A type of signal unit that contains information about signaling unit state
changes. The LSSU has priority over other types of signal units.
LIS
See link interface shelf (LIS).
LIU7
See CCS7 link interface unit (LIU7).
LMS
See local message switch (LMS).
local message switch (LMS)
A shelf in the link peripheral processor (LPP) frame or cabinet. The LMS
exchanges messages between application-specific units (ASU) in the LPP
and provides access to the DMS-bus. Also known as link interface module
(LIM).
loopback
The reflection of data signals of known characteristics to their point of origin
so that the reflected bit stream can be compared with the transmitted bit
stream.

PLN-5001-001i Standard 02.02 April 1997

 List of terms 15–13

LPP
See link peripheral processor (LPP).
LSSU
See link status signal unit (LSSU).
magnetic tape drive (MTD)
In a DMS switch, a device used to record DMS-100 Family data. An MTD
can be mounted on either a magnetic tape center (MTC) frame or an
input/output equipment (IOE) frame. Also known as tape drive.
maintenance and administration position
See MAP.
maintenance trunk module (MTM)
In a trunk module equipment (TME) frame, a peripheral module (PM) that is
equipped with test and service circuit cards and contains special buses to
accommodate test cards for maintenance. The MTM provides an interface
between the DMS-100 Family digital network and the test and service
circuits.
MAP
Maintenance and administration position. A group of components that
provides a user interface between operating company personnel and the
DMS-100 Family switches. The interface consists of a video display unit
(VDU) and keyboard, a voice communications module, test facilities, and
special furniture.
MAPCI
MAP command interpreter
message signal unit (MSU)
A type of signal unit that contains signaling information. The MSUs are
buffered until positive acknowledgement is received.
message switch (MS)
A high-capacity communications facility that functions as the messaging
hub of the dual-plane combined core (DPCC) of a DMS SuperNode
processor. The MS controls messaging between the DMS-bus components
by concentrating and distributing messages and by allowing other DMS-STP
components to communicate directly with each other.
message transfer part (MTP)
A CCITT no. 7 signaling (N7) protocol that provides a connectionless
transport system for carrying common channel interoffice signaling no. 6
(CCIS6) and Common Channel Signaling 7 (CCS7) signaling messages

DMS-100 International Technical Specification BCS40i and up

15–14 List of terms

between user locations or applications functions. Also known as message

transport part.
message transport part
See message transfer part (MTP).
MLH
Multiline hunt. A feature that routes each call to a line in a hunt group by
trying each line in numerical sequence until the call is answered. All calls
start at a single directory number (DN) known as the pilot. No other lines in
the hunt group have directory numbers.
MMI
Man-machine interface.
MPC
See multiprotocol controller (MPC).
MS
See message switch (MS).
MSU
See message signal unit (MSU).
MTD
See magnetic tape drive (MTD).
MTM
See maintenance trunk module (MTM).
MTP
See message transfer part (MTP).
multiprotocol controller (MPC)
A general-purpose card that allows data communications between a
DMS-100 Family switch and an external computer (for example, between a
central office (CO) billing computer and a DMS-100 Family switch). The
MPC card resides on the I/O controller (IOC) shelf. MPC card protocol
software is downloaded from the DMS-100 CPU and then used to support
software routines for Data Packet Network (DPN) communications.
nailed-up connection (NUC)
A permanently assigned network connection that forms part of the speech
path between suitably equipped peripheral modules (PM).

PLN-5001-001i Standard 02.02 April 1997

 List of terms 15–15

nailed-up cross-connection
A special-services connection in which channels on a DS-1 link used for
special-services cards are not switched through the DMS-100 network.
Instead, they are looped around in the subscriber carrier module–100S
(SMS) or subscriber carrier module–100 urban (SMU) formatter card onto a
second DS-1 link leading to a channel bank, DMS-100 switch, or other
telephone equipment.
NET
network
network (NET)
• An organization of stations that can intercommunicate but not
necessarily on the same channel.
• Two or more interrelated circuits.
• A combination of terminals and circuits in which transmission facilities
interconnect user stations directly.
• A combination of circuits and terminals serviced by a single switching or
processing center.
• An interconnected group of computers or terminals.
• The NET module frame of the DMS-100 switch.
network interface unit (NIU)
A DMS SuperNode application-specific unit (ASU) that provides
channelized access for F-bus resident link interface units (LIU) using a
channel bus (C-bus). The NIU resides in a link peripheral processor (LPP)
frame.
network module (NM)
The basic building block of the DMS-100 Family switches. The NM
accepts incoming calls and uses connection instructions from the central
control complex (CCC) to connect the incoming calls to the appropriate
outgoing channels. Network module controllers control the activities in the
NM.
network module controller (NMC)
A group of circuit cards that communicates with the central message
controller (CMC). The NMC is located in the network module (NM). The
NMC organizes the flow of internal messages by directing messages to the
peripheral modules (PM) or interpreting connection instructions to the
crosspoint switches.
network operations protocol (NOP)
A protocol that provides an interface between a DMS-100 Family switch
and its remote systems.

DMS-100 International Technical Specification BCS40i and up

15–16 List of terms

Network Operations System (NOS)

A utility that allows the DMS-100 switch to transfer data over
communications links to a telephone network operating system.
NIU
See network interface unit (NIU).
NM
See network module (NM).
NMC
See network module controller (NMC).
node
The terminating point of a link. The meaning of the term depends on its
context. For example, a circuit can be a node in the context of another
circuit within a module, the module itself can be a node in the context of
another component of the network, and so forth. Some common
applications are as follows:
• in network topology, a terminal of any branch of a network or a terminal
common to two or more branches of a network
• in a switched communications network, the switching points, including
patching and control facilities
• in a data network, the location of a data station that interconnects data
transmission lines
• a unit of intelligence within a system; in a DMS switch, it includes the
CPU, network module (NM), and peripheral modules (PM)
NOP
See network operations protocol (NOP).
NOS
See Network Operations System (NOS).
NSN
National significant number.
NUC
See nailed-up connection (NUC).
OM
See operational measurements (OM).
OPC
See originating point code (OPC).

PLN-5001-001i Standard 02.02 April 1997

 List of terms 15–17

open systems interconnection (OSI) reference model

Open systems interconnection (OSI) reference model for CCITT
applications provides a defined structure for modeling the interconnection
and exchange of information between users in a communication system.
operational measurements (OM)
The hardware and software resources of the DMS-100 Family switches that
control the collection and display of measurements taken on an operating
system. The OM subsystem organizes the measurement data and manages
its transfer to displays and records. The OM data is used for maintenance,
traffic, accounting, and provisioning decisions.
originating point code (OPC)
A Common Channel Signaling 7 (CCS7) term defining the address of a
signaling point (SP) that generated the message. See also destination point
code (DPC).
OSI
See open systems interconnection (OSI) reference model.
paddle board (PB)
A small circuit card that mounts on the rear of a DMS equipment shelf. The
PB carries the cable interfaces and local service functions, such as local
clock sources and bus terminations or both.
PB
See paddle board (PB).
P-bus
See processor bus (P-bus).
PCM
See pulse code modulation (PCM).
PCM30
• A 32-channel 2.048-Mbit/s speech-signaling and message-signaling link
used in international trunks.
• The protocol by which PCM30 links communicate.
PCM30 digital trunk controller (PDTC)
A digital trunk interface that has the hardware configuration of an
international digital trunk controller (IDTC) but runs the software of a
digital trunk controller (DTC).
PDC
See power distribution center (PDC).

DMS-100 International Technical Specification BCS40i and up

15–18 List of terms

PDTC
See PCM30 digital trunk controller (PDTC).
PEC
See product engineering code (PEC).
peg count
The number of times an event occurs; for example, the number of telephone
calls originated during a specified period of time.
peripheral module (PM)
Any hardware module in the DMS-100 Family switches that provides an
interface between external line, trunk, or service facilities. A PM contains
peripheral processors (PP), which perform local routines, thus relieving the
load on the CPU.
peripheral processor (PP)
A hardware device in the peripheral module (PM) that performs local
processing independent of the CPU. The PP is driven by read-only memory
(ROM) in the PM, thus releasing CPU run time for higher level activities.
peripheral side (P-side)
The side of a node facing away from the central control (CC) and toward the
peripheral modules (PM). See also central side (C-side).
per-trunk signaling (PTS)
A conventional telephony method of signaling that multiplexes the control
signal of a call with voice or data over the same trunk.
PM
See peripheral module (PM).
point code
The address of a signaling point. See also capability code.
power distribution center (PDC)
The frame containing the components for distributing office battery feeds to
equipment frames of the DMS-100 Family switches. The PDC accepts A
and B cables from the office battery and provides protected subsidiary feeds
to each frame or shelf. It also contains noise suppression and alarm circuits
and provides a dedicated feed for the alarm battery supply.
PP
See peripheral processor (PP).

PLN-5001-001i Standard 02.02 April 1997

 List of terms 15–19

processor bus (P-bus)

The bus used in DMS SuperNode modules for processor communications.
product engineering code (PEC)
An eight-character unique identifier for each marketable hardware item
manufactured by Northern Telecom.
P-side
See peripheral side (P-side).
PTS
See per-trunk signaling (PTS).
pulse code modulation (PCM)
• The process used to convert an analog (voice waveform) signal to a
digital code.
• A form of modulation in which the modulating signal is sampled, and
the sample is quantified, coded, and sent as a bit stream.
• The representation of an analog waveform by coding and quantifying
periodic samples of the signal such that each element of information
consists of a binary number representing the value of the sample.
quasi-associated mode
A limited form of the nonassociated mode of CCITT no. 6 signaling (N6)
and CCITT no. 7 signaling (N7) signaling in which signals are transferred
between two exchanges over two or more signaling links in tandem, but only
over certain predetermined paths and through predetermined signaling
transfer points (STP). See also dissociated mode, nonassociated mode.
query
A message containing call information that is sent to a centralized database
for call processing instructions.
register
• The apparatus in an automatic switching system that receives address
signals and controls the subsequent switching operation.
• The first unit in the assembly of common control equipment in an
automatic central office (CO). The register receives address information
and stores it for possible conversion or translation. A register frequently
operates in conjunction with a sender.
• A storage device having a specified storage capacity such as a bit, byte,
or computer word, and usually intended for a special purpose.

DMS-100 International Technical Specification BCS40i and up

15–20 List of terms

reset terminal interface (RTIF)

In a DMS SuperNode switch, a user interface terminal that is used to reboot
the system and monitor its status. The RTIF can be either a remote terminal
that is connected through a modem or a local terminal. Also known as
remote terminal interface.
route
A path that follows a linkset into the signaling network that accesses a
destination.
routeset
A logical group of Common Channel Signaling 7 (CCS7) signaling paths
with the same destination point.
routeset management (RSM)
A service that transfers messages over the signaling network and helps to
maintain the network by checking for link problems through the use of an
integrity source.
route table
A table of all possible routes to each node in the DMS-100 Family switch.
The route table is maintained by the I/O system. Whenever a node or link is
put into or taken out of service, the maintenance subsystem responsible for
the node or link informs the I/O system. The I/O system then makes
appropriate adjustments to the route table.
routing
A telephony function that selects and connects a path from the originating
terminal to a destination based on an analysis of the digits received and the
screening of a line as required.
RSM
See routeset management (RSM).
RTIF
See reset terminal interface (RTIF).
SCCP
See signaling connection control part (SCCP).
SCP
See service control point (SCP).
SCPII
An enhancement of the service control point (SCP). See Service Control
Point (SCP).

PLN-5001-001i Standard 02.02 April 1997

 List of terms 15–21

service control point (SCP)

A node in a Common Channel Signaling 7 (CCS7) signaling network that
supports application databases. The function of an SCP is to accept a query
for information, retrieve the requested information from one of its
application databases, and send a response message to the originator of the
request.
Service Order System (SERVORD)
A user interface consisting of commands used to change, add, or delete
subscriber lines. The format used for commands in the SERVORD complies
with the standard telephone industry command format; for example, 3WC is
three-way calling, ADO is add option, DEL is delete, and CWT is call
waiting.
service switching point (SSP)
A Common Channel Signaling 7 (CCS7) signaling node that interacts with
the service control point (SCP) to implement special service code features.
SERVORD
See Service Order System (SERVORD).
shadowing
The ability to store the same data on two or more storage devices, for
reliability purposes. If one storage device in a shadowed set fails, then
access to the data is provided by the remaining storage devices in the
shadowed set. There is no data loss or impact on service capacity when a
storage device in a shadowed set fails.
signaling connection control part (SCCP)
A level of Common Channel Signaling 7 (CCS7) layered protocol. It
supports advanced services such as E800 and service switching point (SSP)
and the Automatic Calling Card Service (ACCS) feature. The main
functions of the SCCP include the transfer of signaling units with or without
the use of a logical signaling connection and the provisioning of flexible
global title translations (GTT) for different applications.
signaling link (SL)
The term used to describe the first two levels of the Common Channel
Signaling 7 (CCS7) protocol: the physical level (level 1) and the link level
(level 2). Level 2 functions, combined with a level 1 signaling data link,
constitute an SL used for the reliable transfer of signaling messages between
two signaling points (SP).
signaling point (SP)
A node in a Common Channel Signaling 7 (CCS7) network that originates,
terminates, or transfers signaling messages from one signaling link (SL) to
another.

DMS-100 International Technical Specification BCS40i and up

15–22 List of terms

signaling point/service switching point (SP/SSP)

A signaling point or a service switching point.
An SP is a switching office that supports CCS7 voice trunk capability
(integrated services digital network (ISDN) user part (ISUP) messaging).
An SP provides an interface between subscriber lines and the CCS7
network.
An SSP is an SP with additional functionality to supports transaction
capabilities application part (TCAP) messaging, which allows the SSP to
access information from CCS7 databases.
signaling system 7 (SS7)
A version of signaling system #7 that was developed for North American
use.
signaling system #7 (SS#7)
An international version of signaling system 7 (SS7) based on the CCITT
specification of SS7.
signaling terminal (ST)
The hardware that performs error checking, coding, and decoding of
signaling messages. In common channel interoffice signaling no. 6 (CCIS6)
and CCITT no. 6 signaling (N6), it consists of a signaling terminal
controller, a modem, and a modem interface card. In Common Channel
Signaling 7 (CCS7), the signaling terminal is a single card.
signaling transfer point (STP)
A node in a Common Channel Signaling 7 (CCS7) network that routes
messages between nodes. Signaling transfer points transfer messages
between incoming and outgoing signaling links but, with the exception of
network management (NWM) information, do not originate or terminate
messages. Signaling transfer points are deployed in pairs. If one STP fails,
the mate takes over, ensuring that service continues without interruption.
SL
See signaling link (SL).
SLM
See system load module (SLM).
SNSE
See DMS SuperNode SE (SNSE).
SP
See signaling point (SP).

PLN-5001-001i Standard 02.02 April 1997

 List of terms 15–23

SPMS
See Switch Performance Monitoring System (SPMS).
SS7
See signaling system 7 (SS7).
SS#7
See signaling system #7 (SS#7).
SSP
See service switching point (SSP).
SSN
See subsystem number (SSN).
ST
See signaling terminal (ST) or symbol table (ST).
S/T-bus
An internal eight-wire bus (of which only four wires are used to transmit and
receive messages) that connects terminals to the NT1 for access to the
ISDN. Messages are transmitted from port to port over the S/T-bus. Also
known as S/T-interface and S/T-loop. Formerly known as transaction bus
(T-bus).
STP
See signaling transfer point (STP).
SWACT
See switch of activity (SWACT).
switch of activity (SWACT)
In a DMS fault-tolerant system, a reversal of the states of two identical
devices devoted to the same function. A SWACT makes an active device
inactive and an inactive device active.
Switch Performance Monitoring System (SPMS)
A feature for assessing DMS–100 switch performance and highlighting poor
performance items.
system load module (SLM)
A mass storage system in a DMS SuperNode processor that stores office
images. From the SLM, new loads or stored images can be booted into the
computing module (CM).

DMS-100 International Technical Specification BCS40i and up

15–24 List of terms

T-bus
transaction bus. See the preferred term, S/T-bus.
TCAP
See transaction capabilities application part (TCAP).
telephone user part (TUP)
A CCITT no. 7 signaling (N7) protocol that provides signaling between a
Common Channel Signaling 7 (CCS7) switching office and a designated
customer setup.
TL
See transmission link (TL).
T-link
A full duplex byte-oriented adaptation protocol designed to transfer
synchronous or asynchronous data over a digital circuit at digital trunk
equipment (DTE) data rates of up to 64 kbit/s.
TM
See trunk module (TM).
TME
See trunk module equipment (TME) frame.
transaction bus (T-bus)
See S/T-bus.
transaction capabilities application part (TCAP)
A service that provides a common protocol for remote operations across the
Common Channel Signaling 7 (CCS7) network. The protocol consists of
message formatting, content rules, and exchange procedures. TCAP
provides the ability for the service switching point (SSP) to communicate
with a service control point (SCP). TCAP is used by the ISDN layer facility
message to transport service information for transaction signaling, not
associated with an active call, over primary rate interface (PRI) links.
transaction services
See connectionless signaling.
transmission link (TL)
In a Common Channel Signaling 7 (CCS7) network, a T1 digital carrier
terminating on a digital trunk controller (DTC). In the DMS switch, the TL
is a single voice carrier on a DS30 link over connections through the
network and into the message switch and buffer 7 (MSB7).

PLN-5001-001i Standard 02.02 April 1997

 List of terms 15–25

trunk module (TM)

A peripheral module (PM), in a trunk module equipment (TME) frame, that
provides speech and signaling interfaces between a DS30 network port and
analog trunks.
trunk module equipment (TME) frame
A frame containing one or more trunk modules (TM), maintenance trunk
modules (MTM), or office alarm units (OAU).
TUP
See telephone user part (TUP).
virtual private network (VPN)
A call case that makes use of the public network to support a private
numbering plan. It is included with CCITT No. 7 Signaling (N7) user part
supplementary services.
VOL
See volume label (VOL).
volume label (VOL)
A standard label recorded on magnetic tape ahead of the header and user
header labels. A VOL identifies the volume by serial number and tape user
name.
VPN
See virtual private network (VPN).

DMS-100 International Technical Specification BCS40i and up

DMS-100 Family

DMS-100 International
Technical Specification

 1994, 1995, 1997 Northern Telecom

All rights reserved.

NORTHERN TELECOM CONFIDENTIAL: The

information contained in this document is the property of
Northern Telecom. Except as specifically authorized in writing
by Northern Telecom, the holder of this document shall keep the
information contained herein confidential and shall protect same
in whole or in part from disclosure and dissemination to third
parties and use same for evaluation, operation, and
maintenance purposes only.

Information is subject to change without notice. Northern

Telecom reserves the right to make changes in design or
components as progress in engineering and manufacturing may
warrant.
DMS, DMS SuperNode, MAP, and NT are trademarks of
Northern Telecom.
Publication number: PLN-5001-001i
Product release: BCS40i and up
Document release: Standard 02.02
Date: April 1997
Printed in Canada and printed in the United States of America