297-1001-801i

DMS-100 Family
DMS-100i
Feature Description Manual Volume 2 of 3

BCS44.1i Standard 09.01 January 2000

DMS-100 Family

DMS-100i
Feature Description Manual Volume 2 of 3

Publication number: 297-1001-801i

Product release: BCS44.1i
Document release: Standard 09.01
Date: January 2000

Copyright  1994–2000 Nortel Networks,

All Rights Reserved

Printed in the United States of America

NORTEL NETWORKS CONFIDENTIAL: The information contained herein is the property of Nortel Networks and is
strictly confidential. Except as expressly authorized in writing by Nortel Networks, the holder shall keep all information
contained herein confidential, shall disclose the information only to its employees with a need to know, and shall protect the
information, in whole or in part, from disclosure and dissemination to third parties with the same degree of care it uses to
protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in writing by
Nortel Networks, the holder is granted no rights to use the information contained herein.

Information is subject to change without notice. Nortel Networks reserves the right to make changes in design or components
as progress in engineering and manufacturing may warrant.
Changes or modification to the DMS-100i without the express consent of Nortel Networks may void its warranty and void the
users authority to operate the equipment.
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC
Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated
in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and
used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this
equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the
interference at his own expense.

NORTEL NETWORKS, the NORTEL NETWORKS LOGO, the GLOBEMARK, HOW THE WORLD SHARES IDEAS, UNIFIED
NETWORKS, DMS, MAP, NORTEL, NORTHERN TELECOM, NT, TOPS, and SUPERNODE are trademarks of Nortel
Networks.

DMS-100 Family DMS100i Feature Description Manual Volume 2 of 3 BCS44.1i

 iii

Publication history
January 2000
BCS44.1i Standard 09.01
March 1999
BCS44i Standard 08.01
December 1997
BCS43i Standard 07.01
Updated to reflect BCS43i software.
November 1996
BCS42i Standard 06.01
Updated to reflect BCS42i software.
July 1996
BCS41i Standard 05.01
Updated to reflect BCS41i software.
October 1995
BCS40i Preliminary 04.01
Updated to reflect BCS40i software.
March 1995
BCS39i Preliminary 03.01
Updated to reflect BCS39i software.
September 1994
BCS38i Preliminary 02.01
Updated to reflect BCS38i software.
April 1994
BCS37i Standard 01.01

Feature Description Manual Volume 2 of 3 BCS44.1i

 v

Contents
Feature Description Manual
Volume 1 of 3

About this document xxi

When to use this document xxi
How to identify the software in your office xxi
How this document is organized xxii
Summary table xxii
Feature package descriptions xxiii
Feature descriptions xxiii
Cross-reference tables xxiii
How reference documentation is organized xxiv

Feature impact summary table 1–1

Feature descriptions 2–1
NER500AA –1 TA0262 –25
CIS Signaling –1 TA0263 –26
TA0129 –4 TA0286 –27
TA0130 –5 TA0295 –28
TA0131 –6 TA0296 –29
TA0135 –7 TA0308 –30
TA0136 –8 TA0311 –31
TA0137 –9 TA0312 –32
TA0176 –10 TA0313 –34
TA0203 –12 TA0315 –36
TA0207 –13 TA0317 –37
TA0213 –14 TA0335 –38
TA0214 –16 TA0336 –39
TA0215 –17 TA0337 –40
TA0241 –18 TA0338 –41
TA0242 –19 TA0339 –42
TA0254 –20 TA0357 –43
TA0255 –22 TA0358 –45
TA0257 –23 TA0440 –46
TA0259 –24 TA0441 –48

DMS-100 Family DMS100i Feature Description Manual Volume 2 of 3 BCS44.1i

vi Contents

TA0442 –50 AJ0194 –54

TA0443 –51 AJ0729 –55
TA0445 –53 AJ1957 –56
NER501AA –1 AJ1959 –57
CIS ISUP –1 AL0479 –58
TA0436 –2 AL0914 –59
TA0437 –4 AL1052 –60
TA0438 –5 AL1149 –62
TA0439 –7 AL1518 –63
NET110AA –1 AL2319 –65
NETAS custom calling AL2417 –66
features –1 AN0100 –67
TA0370 –2 AQ0841 –69
AR0225 –70
NTX000AA –1
NC0086 –71
Bilge –1
NC0130 –72
AL1274 –2
NC0196 –73
AL2044 –4
TA0347 –74
AL2110 –5
39005679 –75
NTX001AA –1
NTX041AB –1
Common Basic –1
CCS7—MTP SCCP –1
AD2997 –13
AL2334 –4
AF1749 –16
AF1780 –17 NTX044AA –1
AF2013 –19 Central Automatic
AF2470 –21 Message Accounting
AF2531 –22 (CAMA) –1
AF2532 –24 TA0167 –2
AF2705 –25 NTX048AA –1
AF2815 –27 Synchronization –1
AF2816 –29 AQ0777 –2
AG0724 –31 NTX054AA –1
AG0919 –32 Line Test Position
AG1082 –33 (LTP)–1
AG1474 –35 AL0944 –2
AG1818 –36 NTX056AA –1
AG1824 –37 E n h a n c e d
AG1868 –38 Administration–1
AG1869 –39 AG1524 –2
AG1922 –40 NTX060AB –1
AG1924 –41 Network Management –1
AG1925 –42 AF2087 –2
AG1927 –43
NTX066AB –1
AG2108 –45
Bilingual Interface –1
AG2149 –46
NC0102 –2
AG2150 –47
AG2255 –48 NTX074AA –1
AG2276 –50 Disk Data Storage
AG2277 –51 System –1
AG2323 –52 AG1004 –3
AJ0191 –53 AL1885 –5

297-1001-801i Standard 09.01 January 2000

 Contents vii

AR0127 –6 NC0322 –48

TA0288 –7 TA0195 –49
NTX136AA –1 TA0196 –50
Automatic transmission TA0273 –51
measuring system –1 NTX274AA –1
39005665 –3 DTC 30 Carrier
NTX167AB –1 Maintenance –1
CCS7—TrunkSignaling AE1056 –2
–1 NTX470AA –1
AR0114 –4 International Common
TA0194 –5 Basic –1
NTX244AB –1 AC0081 –4
Enhanced Sequential AC0109 –5
Trunk Hunting –1 AC0184 –6
AF1252 –2 AC0304 –7
NTX270AA –1 AE0554 –9
New Peripheral AE0643 –10
Maintenance AE0646 –11
Package –1 AE0652 –12
AF1647 –5 AG0719 –13
AF1747 –6 AG1031 –14
AF2583 –8 AJ0171 –16
AF2987 –9 AJ0183 –17
AF2988 –11 AJ0187 –18
AF2989 –12 AJ0580 –19
AF3053 –13 AJ0746 –21
AF3086 –15 AJ0821 –22
AF3179 –17 AJ0837 –23
AF3200 –18 AJ0837 –23
AF3234 –19 AJ1027 –24
AF3271 –20 AJ1088 –25
AF3684 –21 AJ1126 –26
AF3685 –22 AJ1129 –27
AF3747 –23 AJ1223 –28
AF5006 –24 BC0962 –29
AF5007 –26 BC1060 –30
AF5008 –29 BC1185 –31
AJ0338 –32 BC1190 –32
AJ0964 –33 BC1211 –33
AJ0965 –34 BC1301 –34
AJ1038 –35 BC1338 –35
AJ1039 –36 BC1338 –35
AL1460 –38 BC1914 –36
AL2416 –40 BC1920 –37
AN0336 –41 BC1927 –38
AN0337 –42 BC2285 –39
AR0086 –43 BF0375 –40
NC0033 –44 BF0376 –41
NC0105 –45 BF0379 –42
NC0108 –46 BF0393 –43

DMS-100 Family DMS100i Feature Description Manual Volume 2 of 3 BCS44.1i

viii Contents

BF0394 –44 BC1730 –25

BF0395 –45 BC1732 –26
BF0398 –46 BC1784 –27
BF0399 –47 BC1793 –28
BF0436 –48 BC1796 –29
BF0437 –49 BC2079 –30
BF0474 –50 BC2324 –31
BF0560 –51 BF0675 –32
BF0805 –52 BF0801 –33
BF0874 –53 BR0043 –34
BF0915 –54 BR0750 –35
BF0917 –55 BV0061 –36
BF0971 –56 BV0062 –37
BV1211 –57 BV0063 –38
BV1212 –58 TA0128 –39
TA0163 –59 TA0382 –40
TA0165 –60 NTX474AA –1
TA0166 –61 International Base
39005646 –62 Metering –1
NTX471AA –1 AC0053 –3
A-law Companding –1 AC0054 –4
BC1060 –2 AE0056 –5
BF0375 –3 AE0292 –6
BF0376 –4 AG1466 –7
BF0379 –5 AG1476 –8
NTX472AB –1 AG1477 –9
International–Local AG1478 –10
Basic–1 AG1479 –11
AC0085 –3 AJ0570 –13
AC0130 –4 AJ0571 –14
AC0137 –5 AJ0573 –15
AC0252 –7 AJ0866 –17
AC0305 –8 AJ2931 –18
AE0246 –9 AL0218 –19
AE0459 –10 BC1058 –20
AE0538 –11 BC1758 –22
AG0085 –12 BC1760 –23
AG0718 –13 BC1905 –24
AJ0817 –14 BF0677 –25
AJ0818 –15 BF0711 –26
AJ1541 –16 BF0780 –27
AL0054 –17 BV1207 –28
BC0829 –18 BV1208 –29
BC0963 –19 BV1277 –31
BC1449 –20 39005675 –32
BC1450 –21 NTX475AA –1
BC1499 –22 Turkish Trunk
BC1500 –23 Transmission
BC1504 –24 Testing–1

297-1001-801i Standard 09.01 January 2000

 Contents ix

BC1192 –2 NTX482BA –1
BC1193 –3 CEP Line Card
NTX476AA –1 Diagnostics –1
Wink-1 Line Signaling –1 AE0278 –2
BC1188 –2 NTX482CA –1
BF0565 –3 China Line Card
NTX477AA –1 Diagnostics –1
Delay Dial-1 Signaling –1 AG0827 –2
BC1187 –2 AJ1496 –3
BF0564 –3 NTX483AB –1
NTX478AA –1 International 101
CCITT PCM (30+2) Communication Test
Digital Signaling and Line –1
Maintenance –1 AE0005 –2
AE0480 –2 AE0250 –3
AE0777 –3 AJ1031 –4
BC1076 –5 BC1191 –5
BC1340 –7 BC2076 –7
BF0392 –8 BC2078 –8
BF0430 –9 NTX484AA –1
BF0432 –10 Malicious Call
BF0433 –11 Trace–International
BF0978 –12 Toll/Transit –1
NTX479AA –1 BC1496 –2
International Universal TA0279 –3
Tone Receiver NTX485AA –1
Support –1 International–Call
BC1766 –2 P r o c e s s i n g
BF0396 –3 System–1
BF0434 –4 BC1301 –2
NTX480AA –1 BC1927 –5
Turkish Tone Plan –1 BF0399 –6
BC1186 –2 BF0805 –7
NTX481AA –1 BF0915 –8
Turkish Operator NTX486AA –1
Sw i t c h b o a r d MF-3 Register
Signaling –1 Signaling–1
BC1339 –2 BC1189 –2
BF0679 –3 BF0567 –3
NTX482AB –1 NTX487AA –1
Turkish Line Card Malicious Call
Diagnostics –1 Trace–International
AG0095 –2 Local –1
BC1337 –3 AG0709 –2
BF0684 –4 BF0674 –5

DMS-100 Family DMS100i Feature Description Manual Volume 2 of 3 BCS44.1i

x Contents

NTX487AB –1 NTX499AA –1
Malicious Call CEPT Subscriber
Trace–International Services–I –1
Local –1 AC0082 –3
TA0138 –2 AC0083 –5
TA0139 –4 AC0086 –7
TA0168 –6 AC0133 –8
NTX488AA –1 AC0134 –10
International Time of Day AC0135 –12
Routing –1 AC0136 –13
BC1498 –2 AE0239 –16
BC1825 –3 AE0240 –19
BV1136 –4 AE0242 –22
NTX489AA –1 AE0248 –24
Visa Switchboard AE0249 –26
Interface (Turkey) –1 AG0962 –28
BC1520 –2 AG1540 –29
BF0680 –3 AJ0563 –30
AJ1432 –32
NTX492AA –1
BC2053 –33
Operator Toll Break-In –1
BC2077 –35
AE0244 –2
BC2260 –36
AE0245 –4
BC2261 –39
TA0178 –6
TA0229 –41
TA0179 –7
TA0325 –45
TA0180 –8
TA0326 –46
NTX493AA –1 TA0327 –47
Administrative Call
NTX650AA –1
Diversion Features–1
TS16 Signaling for R1 –1
BC2049 –2
AE0034 –2
NTX494AA –1
NTX652AA –1
Automatic Call
Intraswitching on the
Recording–1
IRLCM –1
BC2050 –2
AE0108 –2
BC2074 –4
AE0178 –3
BF0976 –5
NTX495AA –1 NTX653AA –1
IRLCM–Emergency
TS16 Signaling for Loop
Stand Alone (ESA)–1
Disconnect –1
AE0216 –2
BF0867 –2
TA0240 –3
BF0881 –3
BV1987 –4 NTX655AA –1
BV1988 –5 E & M Signaling in
TS16–1
NTX496AA –1
AE0025 –2
Gateway Access –1
AE0059 –2 NTX656AA –1
BC2059 –3 CEP Tone Plan –1
BF0870 –4 BF0869 –2
BV1989 –5 NTX657AA –1
International CAMA –1

297-1001-801i Standard 09.01 January 2000

 Contents xi

AE0147 –2 NTX668AA –1
39005622 –4 Insert Tone on Coin
NTX660AA –1 Phone Termination–1
International Feature AE0057 –2
P r o c e s s i n g NTX669AA –1
Environment International Network
(FPE)–Basic –1 Management –1
BC2286 –2 AC0132 –2
NTX662AA –1 NTX738AC –1
Emergency Cut-off –1 Switch Performance
BC2081 –2 Monitoring System–1
NTX664AA –1 AG1926 –2
OMs in Erlangs –1 AL1719 –3
AE0033 –2 NTX750AC –1
AE0943 –3 ISDN Basic Access –1
BC2060 –4 AL1674 –6
NTX665AA –1 AL2539 –9
Semi-permanent AL2541 –10
Connections– AL2542 –11
Basic –1 AL2726 –12
AC0256 –2 AQ0788 –13
BC2080 –4 AQ0789 –15
NTX666AA –1 AQ0882 –16
Semi-permanent AQ0884 –17
Connections– NTX885AB –1
Local–1 Switch Path
AC0256 –2 Diagnostics–1
BC2080 –4 AG1214 –2
NTX667AA –1 AJ0473 –3
Printed Meter Check –1 AL1566 –4
AE0055 –2

Feature Description Manual

Volume 2 of 3

NTX901AA –1 AG1973 –20

Local Features I –1 AJ1224 –21
AD0943 –8 AL1541 –22
AF0966 –9 AL1608 –23
AF1439 –10 AR0491 –24
AF1756 –13 NC0020 –25
AF2565 –14 NC0313 –26
AF2599 –15 NC0495 –28
AF2668 –16 TA0289 –29
AG0649 –17 NTX904AA –1
AG1318 –18 R2 Signaling Base –1
AG1854 –19 AE0142 –3

DMS-100 Family DMS100i Feature Description Manual Volume 2 of 3 BCS44.1i

xii Contents

AE0146 –5 AL1782 –25

AE1245 –7 AL1826 –26
AG1217 –9 AL1884 –27
AG1218 –10 AL1968 –28
AG1220 –11 AL2021 –29
AJ0159 –13 AL2030 –30
AJ0205 –14 AL2331 –31
AJ1028 –17 AQ0721 –32
AJ2411 –19 AQ0741 –33
TA0165 –20 AQ0834 –34
TA0201 –21 AQ0854 –35
TA0320 –22 AQ0859 –36
TA0331 –23 AR0211 –37
TA0383 –24 NTX942AA –1
NTX909AA –1 SuperNode System Load
ANI Toll –1 Module –1
AE0115 –2 AG1385 –2
NTX910AA –1 AL1060 –3
ANI Local –1 AL1166 –4
AE0116 –2 AL1298 –5
NTX940AA –1 NTX942AB –1
CM Bilge –1 DMS – SuperNode
AL1109 –2 System Load
AL1718 –3 Module–1
AL1923 –5 AL1790 –2
AL2042 –7 NTX944AA –1
AL2328 –8 Base Node
AR0160 –9 Maintenance–1
NTX941AA –1 AR0079 –2
CM Common –1 AR0081 –3
AG2480 –3 NTX945AA –1
AI0625 –4 MS Base Link
AI0630 –5 Maintenance –1
AL0797 –6 AC0639 –2
AL0803 –7 AC0644 –4
AL1053 –9 AG1337 –5
AL1054 –10 AL1456 –6
AL1055 –11 AL1457 –8
AL1182 –12 AL1476 –9
AL1183 –13 AL1477 –10
AL1192 –14 AL1478 –11
AL1193 –15 AL1479 –12
AL1197 –16 AL1482 –13
AL1200 –17 AL1779 –14
AL1201 –18 AL1780 –15
AL1480 –19 AL1781 –16
AL1570 –20 AQ0717 –17
AL1681 –21 AQ0718 –18
AL1753 –22 AQ0840 –19
AL1759 –23 AQ0854 –20

297-1001-801i Standard 09.01 January 2000

 Contents xiii

NTX950AA –1 NTXB04AA –1
MS Bilge –1 PBX Line Support –1
AC0638 –2 AE0169 –2
AL0787 –3 NTXB05AA –1
AL0790 –4 ITOPS Common Basic–1
NTX951AA –1 AJ1257 –2
MS Common –1 NTXB07AA –1
AC0639 –2 Inter Administration
AL1199 –4 Accounting –1
AL1456 –5 AE0154 –2
AQ0835 –7 NTXB08AA –1
AQ0858 –8 ITOPS for CEP –1
NTX980AA –1 AG0717 –2
International Trunk Test NTXB10AA –1
Position (ITTP) –1 China Common Basic –1
BC0158 –2 AG0707 –2
BC0490 –3 AG0708 –3
BC0495 –4 AG0711 –4
BC0693 –5 AJ0782 –5
BC0858 –6 AJ0796 –9
BC1259 –8 AJ0819 –11
BR0176 –10 AL2529 –12
BR0200 –11
NTXB11AA –1
BR0201 –12
DP Register Signaling –1
BR0223 –13
AG0707 –2
BV0041 –15
AJ0498 –3
NTXA66AA –1 NTXB12AA –1
Enhanced Office
ITOPS Local Basic –1
Recovery –1
AC0240 –2
AJ0192 –2
AJ0474 –3 NTXB13AB –1
ITOPS Toll–Enhanced
NTXB00AA –1
Queueing –1
International Traffic
AG0636 –3
Separation –1
AG0712 –5
AC0131 –2
AG0713 –6
NTXB01AA –1 AG0714 –8
International Traffic AG0715 –9
Separation Report –1 AG0716 –10
AC0131 –2 AG1230 –13
NTXB02AA –1 AG1233 –14
International Service AG1234 –16
Analysis–Basic –1 AJ0178 –17
AE0153 –2 AJ0180 –19
NTXB03AA –1 AJ0182 –20
S e r v i c e AJ0572 –21
Analysis–Local–1 AJ0801 –22
AE0167 –2 AJ0802 –25
AJ0803 –27

DMS-100 Family DMS100i Feature Description Manual Volume 2 of 3 BCS44.1i

xiv Contents

AJ0804 –28 AJ1256 –11

AJ1024 –29 AJ1445 –12
NTXB14AA –1 AJ1446 –14
China Local Basic –1 NTXE01AA –1
AG0710 –2 E n h a n c e d
AL2528 –5 Network—Basic –1
NTXB17AA –1 AL0573 –3
Attendant Pay Station AL0856 –5
Local –1 AL0857 –6
AG1291 –2 AL0957 –7
NTXB21AA –1 AL0958 –8
Co-existence (Trunk AL0959 –9
Type) –1 AL0960 –10
AE0481 –2 AL1230 –11
AE0523 –3 AL2038 –12
AL2107 –13
NTXB22AA –1
AL2162 –14
OM Enhancements –1
AL2260 –16
AE1240 –2
AR0005 –17
AL2530 –4
AR0141 –18
AL2549 –6
AR0186 –20
AL2720 –8
TA392 –21
NTXB69AA –1
NTXE29AA –1
R2 for DMS-100
BCS Process
International –1
Enhanced–1
AE0139 –2
AG1506 –2
AE0140 –3
AG1511 –3
AE0171 –4
AG1513 –4
AE0172 –5
AG1560 –5
AE0173 –6
AG1563 –6
AE0514 –7
AG1570 –7
AE0893 –8
AJ1124 –10 NTXE54AA –1
SLM II Enhancements –1
NTXB75AA –1
AL1174 –2
Implementation of RMM
on IRLCM –1 NTXF15AA –1
AE0293 –2 DMS-core MC68030 33
MHz Processor –1
NTXB83AA –1
AL0934 –2
ITOPS to International
R2 Interworking –1 NTXF20AA –1
AG1294 –2 LPP on DMS-100
TA0228 –4 SuperNode for
CCS7–1
NTXB84AA –1
AL2334 –3
International Rating
AQ1030 –4
System –1
AQ1031 –5
AG1231 –2
AQ1070 –6
AG1235 –4
AG1236 –6 NTXF70AA –1
AG1237 –8 SuperNode SN-20
AJ1025 –10 Processor –1
BC1826 –2

297-1001-801i Standard 09.01 January 2000

 Contents xv

BC1827 –8 NTXH05AA –1
BC1909 –14 Moroccan Local
BC1932 –16 Signaling –1
BC2003 –17 AE0567 –2
NTXF71AB –1 AE0568 –5
SuperNode Enhanced AE0897 –6
Messaging –1 AE0898 –8
AL1276 –3 AJ0205 –9
AL1277 –4 NTXH06AA –1
AL1278 –5 Moroccan Toll
AL1279 –6 Signaling–1
AL1280 –7 AE0567 –2
AL1281 –8 AE0568 –5
AL1655 –9 AE0897 –6
AL1656 –10 AE0898 –8
AL1657 –11 AJ0205 –9
AL1658 –12 NTXH07AA –1
AL1659 –13 Belize R2 Signaling –1
AL1660 –14 AJ0578 –2
AL1663 –15
NTXH12AA –1
AL1664 –16
ITOPS Enhancements
AL1740 –17
for Japan –1
AL2130 –18
AE0546 –2
AR0124 –19
AR0125 –20 NTXH13AA –1
AR0128 –21 Fixed Duration Calls –1
AR0129 –22 AJ0177 –2
NTXH00AA –1 NTXH16AA –1
Moroccan Tones –1 Estimated Call Charges
AE0448 –2 for ITOPS –1
AJ0181 –2
NTXH01AA –1
Moroccan Line Card NTXH17AA –1
Diagnostics –1 International ATME 2 for
AE0513 –2 International
AE0536 –3 DMS-100/200I –1
AJ0832 –2
NTXH02AA –1
Moroccan Physical NTXH18AA –1
Ringing –1 International China
AE0515 –2 TUP –1
AQ1107 –3
NTXH03AA –1
TA0124 –4
Socotel Base
TA0125 –6
Signaling–1
TA0126 –7
AE0567 –2
TA0127 –8
AE0568 –4
TA0132 –9
NTXH04AA –1 TA0162 –10
CCITT 2-Bit Line TA0183 –12
Signaling –1 TA0193 –13
AE0514 –2 TA0222 –14
TA0223 –15

DMS-100 Family DMS100i Feature Description Manual Volume 2 of 3 BCS44.1i

xvi Contents

TA0224 –17 NTXH70AA –1

TA0280 –18 C7 Support for
TA0281 –19 Ch a n n e l i z e d
TA0381 –20 Access–1
TA0413 –22 AI0407 –2
TA0414 –24 AL1929 –3
TA0415 –26 NTXH71AA –1
TA0423 –28 ITOPS Intrusion Tones–1
TA0424 –30 AJ0179 –2
TA0427 –32
NTXH77AA –1
NTXH19AA –1 Channelized Access on
CTUP Local –1 LPP/LIS –1
TA0158 –2 AI0408 –2
TA0182 –3 AI0409 –3
TA0225 –5 AI0410 –4
TA0226 –6
NTXH79AA –1
TA0422 –7
Brazil Signaling –1
NTXH22AA –1 AJ1124 –2
International Local
NTXH80AA –1
Metering –1
Mexico Signaling –1
AC0054 –2
AJ1124 –2
AE0056 –3
AJ1423 –4
AE0292 –4
BV1277 –5 NTXH95AA –1
M e t e r i n g
NTXH23AA –1
Enhancements–1
Metering Over Junction
AE0838 –2
(MOJ) –1
AJ0581 –2 NTXK12AA –1
AJ0851 –6 Irish R2 Signaling
Protocol –1
NTXH54AA –1
AE0630 –2
ITOPS–Account Code
Access –1 NTXK13AA –1
AJ1026 –2 Irish Downloadable
AJ1255 –4 Tones –1
AE0397 –2
NTXH58AA –1
AE0671 –4
Guyana R2 Signaling –1
AJ1265 –2 NTXK70AA –1
Peru Signaling –1
NTXH60AA –1
AJ1872 –2
Morocco ITOPS Trunk
Interworking –1 NTXK71AA –1
AE0735 –2 Haiti Signaling –1
AE0972 –2

297-1001-801i Standard 09.01 January 2000

 Contents xvii

NTXK72AA –1 TA0134 –3
A-Bit Pulse Line TA0195 –4
Signaling –1 TA0196 –5
AL2457 –2 NTXN83AA –1
TA0163 –4 LIS Common—LMS
NTXK73AA –1 Functionality on
DMS-100I Terminator MS–1
Billing –1 AL1453 –2
AJ1791 –2 AR0478 –3
NTXK79AA –1 NTXP10AA –1
PCM Unified Processor Dual-shelf Network –1
(UP) Support –1 AL2055 –2
AE1007 –2 NTXP44AA –1
AJ1898 –3 DMS SuperNode SE
AJ1899 –4 Common –1
TA0174 –5 AQ0857 –2
NTXK79AD –1 NTXP72AA –1
PCM30 Unified Integrated Network
Processor Support–1 Support on SN-1 –1
TA0133 –2 AR0105 –2

Feature Description Manual

Volume 3 of 3

NTXQ52AA –1 NTXR46AA –1
Support for MS Resident, R o b u s t n e s s
LIS Controller –1 Enhancements –1
AL1455 –2 AL2236 –2
NTXR34AA –1 NTXR72AA –1
XPM Plus (Product Life CCS7—MTP/SCCP for
Upgrade Strategy) L P P - b a s e d
Basic –1 Platforms–1
AF3732 –2 AL2334 –5
AF3733 –3 AR0010 –6
AL2540 –4 AR0117 –7
NTXR34AB –1 AR0118 –8
XPM Plus (Product Line AR0907 –9
Upgrade Strategy) AR0908 –11
Basic –1 AR0909 –13
TA0174 –2 AR0910 –16
NTXR42AA –1 TA0287 –18
Firmware Downloading–1 NTXS72AA –1
AF3658 –2 CC Software Support for
TA0174 –4 EDRAM Uploading–1
AQ0984 –2

DMS-100 Family DMS100i Feature Description Manual Volume 2 of 3 BCS44.1i

xviii Contents

NTXU35AA –1 NTXU63AA –1
DMS-100I Downloadable ISUP on DMS100i –1
Tones –1 TA0386 –2
AE1243 –2 TA0387 –3
TA0140 –3 39005872 –4
TA0141 –4 NTXU64AA –1
TA0175 –5 FRA on DMS100i –1
TA0177 –6 TA0328 –2
NTXU44AA –1 TA0329 –4
Toll Break-in (Local) –1 TA0330 –5
TA0158 –2 NTXU65AA –1
TA0159 –4 NETAS TT features –1
TA0227 –6 TA0371 –2
NTXU45AA –1 TA0372 –3
100i ISUP Base –1 TA0373 –4
TA0169 –2 TA0374 –5
TA0170 –4 TA0375 –7
TA0171 –6 TA0376 –8
TA0172 –8 TA0377 –10
TA0233 –9 TA0378 –12
TA0379 –11 NTXU66AA –1
TA0543 –12 100i 100K Metering –1
39005866 –16 TA0467 –2
NTXU46AA –1 TA0468 –4
100I ISUP Local –1 TA0469 –6
TA0169 –2 TA0470 –8
TA0172 –4 NTXU67AA –1
TA0235 –5 ICAMA Behavior
NTXU47AA –1 Selection –1
China Message Transfer TA0471 –2
Part –1 NTXU68AA –1
AR3026 –2 Turkish Toneset with R2
NTXU49AA –1 and COT –1
Voice Mail –1 TA0474 –2
TA0230 –2 NTXU69AA –1
NTXU51AA –1 100i ETSI PRI –1
ISUP (R2) Variants –1 TA0549 –2
TA0232 –2 TA0550 –4
TA0234 –4 TA0551 –6
NTXU55AA –1 TA0560 –8
Party Line –1 TA0561 –9
TA0274 –2 TA0601 –11
NTXU60AA –1 39005628 –13
ICAMA Enhancement –1 39005643 –15
TA0285 –2 39005649 –17
39005869 –19
NTXU62AA –1
Line Signaling Monitor –1
TA0319 –2

297-1001-801i Standard 09.01 January 2000

 Contents xix

NTXU70AA –1 NTXV16AA –1
Calling Name Chile Signaling –1
Delivery/Blocking –1 AL2632 –2
TA0465 –2 NTXV55AA –1
NTXU71AA –1 AMA and ITOPS Billing
Automatic Call Enhancement –1
Back/Automatic AE1239 –2
Recall –1 NTXW00AA –1
TA0466 –2 World Line Card Base –1
NTXU72AA –1 AE1099 –3
Advice of charge –1 NTXW01AA –1
TA0610 –2 World Line Card Type –1
NTXU81AA –1 AE0946 –2
ETSI BRI –1 AE1099 –3
TA0552 –2 NTXW02AA –1
TA0553 –4 World Line Card Cutover
TA0554 –6 by DN –1
TA0556 –8 AE0956 –2
TA0558 –10 NTXW03AA –1
TA0562 –12 World Line Card
TA0563 –14 O v e r v o l t a g e
TA0564 –16 Report–1
TA0565 –18 AE1013 –2
TA0566 –20
NTXW21AA –1
TA0602 –22
Template for 900+2 for
TA0603 –24
Type 2 –1
TA0614 –28
AE1106 –2
TA0615 –30
39005633 –32 NTXW23AA –1
39005652 –34 WLC Templates for
39005862 –36 Japan, Brazil, Peru,
Poland –1
NTXU84AA –1
TA0216 –2
TT MCT –1
TA0544 –2 NTXZ12AA –1
China ISUP –1
NTXU87AA –1
TA0582 –2
Long Call Check Tool –1
TA0583 –4
TA0510 –2
NTXZ13AA –1
NTXU88AA –1
Calling Number Delivery
TT Toll Features –1
for China –1
TA0532 –2
TA0584 –2
TA0533 –4
NTXZ19AA –1
NTXU90AA –1
IOM –1
ETSI ISUP –1
39005676 –2
39005695 –2
NTXZ20AA –1
NTXV13AA –1
RCO2 –1
China C1 DP Trunk
39005683 –2
Interworking –1
AL2721 –2 Unpackaged Features –1
AL2722 –3 TA0272 –2
TA0353 –3

DMS-100 Family DMS100i Feature Description Manual Volume 2 of 3 BCS44.1i

xx Contents

TA0354 –4 TA0529 –40

TA0355 –5 TA0530 –42
TA0356 –6 TA0531 –44
TA0368 –7 TA0535 –46
TA0473 –8 TA0536 –48
TA0474 –10 TA0537 –50
TA0509 –12 TA0538 –54
TA0511 –14 TA0545 –57
TA0513 –17 TA0546 –59
TA0521 –20 TA0567 –60
TA0522 –22 TA0568 –62
TA0523 –24 TA0597 –64
TA0524 –27 TA0598 –66
TA0525 –29 TA0612 –68
TA0526 –31 TA0617 –70
TA0527 –33 39005876 –72
TA0528 –36

Cross-reference 3–1
Features listed by BCS 3–1

Cross-reference 4–1
Feature number to feature package and BCS 4–1

Cross-reference 5–1
Feature package to feature number and BCS 5–1

Cross-reference 6–1
Feature name to feature number, package, and BCS 6–1

297-1001-801i Standard 09.01 January 2000

 NTX901AA
Local Features I
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTX901AA contents
Feature Description
number

AD0633 DN Network Attributes

AD0943 Office Line Totals/QNCOS
AF0966 Called Party Released Timing Enhancement
AF1439 AMA: Separation of Billing and Routing Function
AF2565 E800 on PX Trunks
AF2599 Test Desk Robustness
AF2668 RCU Line Card Configuration
AG0156 Automatic Line Testing Rewrite
AG0358 LTP CIBINCOM Rewrite
AG0487 6X17AD Line Card Maintenance Support
AG0649 Enhanced Line Access Measurements
AG0923 DN Attributes Service Order Enhancements
AG1109 LCM CND Support
AG1285 Change Line Treatment Group Command
AG1318 Enhanced Line Access Measurements—Part 2
AG1854 200-ms Disconnect Timing
AG1973 Distinctive Ringing on Ring Side Only
AJ1224 Open Numbering Plan Phase I
AL0495 DTSR on a per–PM Basis
AL0499 Call Forward Assignment to PBX Mess Rate Line (CFW for PBM)
AL1541 Expansion of LCD Number to 1000
AL1608 Line Card Code Expansion
AR0491 LTP Enhancement
BC0157 Line Cut-off Relay Operation on Disconnect
BC0329 Dial Tone Speed Measurement

—continued—

Feature Description Manual Volume 2 of 3 BCS44.1i NTX901AA–1

NTX901AA
Feature package NTX901AA contents (continued)
Feature Description
number

BC0552 Failure Flag from Line Diagnostics

BC0553 ALT Daddy & Tidy Cleanup
BC0731 NPE—Digit Collection Data Downloading
BC0749 New LEN Numbering Cleanup
BC0805 LM/RLM Warm Takeback
BC0807 LM/RLM Warm Takeover
BC0829 Auto Retest of ALT Failures
BC0844 Line Status in Journal File
BC0866 Data Facility for 3X09 MTA
BC0867 MTA Gating Facility
BC0884 Utilities for 3X09 MTA
BC0890 TTP Support for 3X09 MTA
BC1155 Type B Line Card Maintenance
BC1835 3X09BA MTA Switch
BC1931 Immediate Answer Reporting
BC2135 Coin Disposal Signal Polarity Option
BF0197 LCM Ringing/ANI/Coin
BF0200 LCM—Ringing Maintenance
BF0287 LCM Maintenance Enhancement
BF0411 LCM—Memory Recovery
BF0490 Guaranteed Dial Tone
BF0498 LM Enhancements to Support NET/PM Speech Link Diagnostics
BF0556 Revertive Ringing for Parties on Different Sides
BF0803 Analog Coin Functions on LCM
BF1027 LM—Takeover/Takeback Enhancement
BR0020 Fraud Prevention
BR0028 Frequency Ringing (Decimonic)
BR0029 Harmonic Ringing (Five Frequencies)

—continued—

NTX901AA–2 297-1001-801i Standard 09.01 January 2000

 NTX901AA
Feature package NTX901AA contents (continued)
Feature Description
number

BR0030 Frequency Ringing (20 Hz)

BR0031 Interface with Pulsar II IMTS
BR0036 Multiwink Coin Control
BR0052 Class of Service Tones
BR0057 Badger 612 Interface
BR0060 Line Treatment on Call Disconnect
BR0061 AE LTD Interface
BR0063 No Revertive Ring
BR0073 Interface with SARTS
BR0075 Bridged and Grounded Ringers on Same Line
BR0089 Frequency Ringing (Synchromonic 16)
BR0094 Free Number Terminating
BR0095 AE-21 Interface
BR0102 Two Party ANI
BR0122 I-F to S-L No. 14 LTD
BR0129 Digital Analog MF Receiver Compatibility
BR0134 Fully- and Semi-Selective (Superimposed) Ringing U.S.
BR0148 Interface with Teradyne Loop Test Unit
BR0152 Coin Control (Line Number Method)
BR0153 Frequency Ringing (Synchromonic 20)
BR0154 N11 Service Code Calls Terminating to Lines
BR0181 411 Recording on Magtape
BR0193 Frequency Ringing (Harmonic) 20-Hz Base
BR0197 Line Cut-off Relay Operation on Disconnect
BR0219 Pending Order File on Disk
BR0229 Line Data Base Queries
BR0234 Third Wire Coin Control
BR0235 Threshold on Permanent Signals (Line Cable Failures)

—continued—

Feature Description Manual Volume 2 of 3 BCS44.1i NTX901AA–3

NTX901AA
Feature package NTX901AA contents (continued)
Feature Description
number

BR0236 Tip and Ring Coin Control

BR0242 Prepay Coin First
BR0256 Port A System Line Test Interface
BR0269 Revertive Call Peg Count Register
BR0281 Test Lines: Loop Around
BR0282 Loop Around Test—ATT Mode
BR0283 Station Ringer Test Number for DMS-100
BR0320 CLI—Trunk Termination
BR0427 Charge-a-Call (Coin Free Dialing)
BR0433 Expanded Inband Signaling
BR0436 Denied Origination—Two- or Four-Party ANI
BR0437 Coin Features—AT&T DTF
BR0442 958 990 660 Service Codes—N.Y. Tel
BR0450 Per-Call Loop Test on Ground
BR0453 ANI (Bell Std) Outpulsing in Response to Wink Signal
BR0460 Detection of Open Line at MDF
BR0463 Initial Coin Return and Initial Coin Retain Option
BR0491 IMR/INW Read Reset by NNX
BR0493 Test Assigned/Unassigned LEN (Host and RLM)
BR0497 010 Service Code
BR0501 Flexible ANI ID = 8,9 Assignment
BR0511 Automatic Line Testing Speedup
BR0519 Toll Diversion Enhancements
BR0585 Test Access of Individual Lines in a Hunt Group
BR0606 Revertive Calling—Ringing to Both Parties on Four Party
BR0623 Station Ringer Test—Three-Digit Access Code
BR0653 COD Option on Office Basis
BR0670 Permanent Signal Time Out—Open Interval

—continued—

NTX901AA–4 297-1001-801i Standard 09.01 January 2000

 NTX901AA
Feature package NTX901AA contents (continued)
Feature Description
number

BR0686 SO—System Response to QDN

BR0751 0+ DA and 0+ 800 Permissive Dialing
BT0020 Individual Flat Rate Lines
BT0021 Individual Message Rate Lines
BT0022 Manual Lines
BT0023 AC DC Ringing
BT0024 Loop Start
BT0025 Ground Start
BT0027 Digitone Receiver
BT0028 DP Receiver
BT0030 Translation and Screening
BT0034 EAS Trunk (DP/MF) (A/D)
BT0035 DACS Trunk (DP/MF) (A/D)
BT0039 No. 14 Local Test Desk
BT0042 Hunting (MLH, DLH, DNH) (LIN/DIST/CIRC)
BT0044 Coin Lines (DTF)
BT0045 Purple Box Wire Tap
BT0046 Two-party Flat Rate
BT0047 Revertive Ringing
BT0049 PBX Flat Rate Non-DID
BT0050 ANI (One and Two Party)
BT0052 FX Lines (Line Card Termination)
BT0054 PBX Message Rate
BT0056 Toll Divert
BT0057 Denied Service Options
BT0058 Free Number Terminating
BT0059 Inband Coin Control
BT0060 Intercept Trunk (A/D)

—continued—

Feature Description Manual Volume 2 of 3 BCS44.1i NTX901AA–5

NTX901AA
Feature package NTX901AA contents (continued)
Feature Description
number

BT0061 Hotel/Motel (RB and Third Wire)

BT0062 Voice Number Verification Trunk
BT0063 Station Ringer
BT0064 Operator Verification Trunk (DP/MF) (A/D)
BT0068 Receiver Off-Hook Trunk
BT0069 PS/PD Treatment
BT0072 Calling Line Identification
BT0083 LTSTL—Short Circuit (I/C)
BT0084 LTSL—Open Circuit (I/C)
BT0085 LTSTL—1120 (Nonsync) (I/C)
BT0087 LTSTL—1000 (BAL) (O/G and I/C)
BT0088 LTSTL—1111 (Net Loss) (I/C)
BT0090 LTSTL—1181 (Sync) (I/C)
BT0095 LTP and Associated Level
BT0097 PBX Flat Rate (DID)
BT0150 O/G TTSTL Synchronous
BT0341 Inc/Out TTSTL Synchronous
BT0342 Inc/Out TTSTL Loop Around
BT0347 OM—Local (Pegs and Usage)
BV0019 Flash Ignore (PBX—2-s Disc)
BV0034 Touch Tone Testing—External Facilities
BV0045 Multiparty Flat Rate
BV0048 Coin Control (Tip and Ring)
BV0051 Coded Ringing (5 Codes)
BV0052 Coin Control (Third Wire)
BV0071 Superimposed Ringing
BV0076 Threshold on Permanent Signals (Line Cable Failures)
BV0087 Prepay Coin First Coin Line

—continued—

NTX901AA–6 297-1001-801i Standard 09.01 January 2000

 NTX901AA
Feature package NTX901AA contents (continued)
Feature Description
number

BV0088 Sem-Post-Pay Coin Line

BV0196 Line Data Base Queries
BV0198 Dial Tone Speed Test
BV0424 Hunting
BV0948 6X17AA Line Card Facility Maintenance
BV1109 NPE—OMs for LCM
NC0020 Keypad Enable
NC0313 SERVORD Enhancements for SLE
NC0495 Off-Hook Testing

TA0289 International Support for the ISM

End

BCS history
This feature package was created in BCS00. Feature TA0289 was added in
BCS41i
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX270AA New Peripheral Maintenance Package

Feature Description Manual Volume 2 of 3 BCS44.1i NTX901AA–7

NTX901AA
AD0943
Feature name
Office Line Totals QNCOS
Description
AD0943 provides a summary of network class of service (NCOS) and office
line totals at the command interpreter (CI) level of a MAP (maintenance and
administration) display for a DMS-100 or an SL-100.
BCS history
This feature was created in BCS29.
Restrictions and limitations
Command QNCOS may execute for several hours before producing any
output.
Service orders
A new SERVORD query command, QNCOS, provides a short or detailed
summary of terminals and their NCOS. The short summary lists the number
of terminals for each NCOS. The detailed summary also lists line
equipment numbers (LEN), directory numbers (DN), and associated NCOS.

User interface
The ALMSTAT command at the LTP MAP level has been modified to
include office line totals for Meridian Business sets, Aries sets, Meridian
Asynchronous Data Options (MADO), and ADATA1 sets.

NTX901AA–8 297-1001-801i Standard 09.01 January 2000

 NTX901AA
AF0966
Feature name
Called Party Released Timing Enhancement
Description
AF0966 enables cancellation of long timed release disconnect (LTRD) on
line-to-trunk calls on individual lines. The line option is short timed release
disconnect (STRD) and the disconnect time is defined by an office
parameter.
BCS history
This feature was created in BCS29.
Restrictions and limitations
The STRD line option applies only to calls originating from a line.
The STRD line option is not compatible with KSET-type terminals
(P-phones) or party lines.
STRD affects only line-to-trunk calls involving the following trunk group
types:
• ATC (equal access)
• IT (intertoll)
• SC (super CAMA)
• TOPS (operator)
• TO (outgoing end office)

Datafill
The following tables were modified for this feature:

Table Description

LENLINES STRD is added to range of values for OPTLIST field.

IBNLINES STRD is added to range of values for OPTLIST subfield.

Service orders
Line option STRD has been added.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX901AA–9

NTX901AA
AF1439
Feature name
AMA: Separation of Billing and Routing Functions
Description
AF1439 allows seven-digit originating calls to be translated optionally as
long distance calls, and ten-digit originating calls to be translated optionally
as local calls. Automatic message accounting (AMA) records for these calls
are generated according to the presence or absence of the office code in the
local call area screening data tables, instead of the presence or absence of the
digit 1 as the first digit.
BCS history
AF1439 was created in BCS31.
Restrictions and limitations
The feature applies only to switches configured for Bellcore automatic
message accounting.
This feature’s method of determining whether a non-interexchange carrier
call is local or toll applies to calls that translate through table LINEATTR,
and to calls involving trunks with the LCABILL field in their trunk group
data.
The table PFXTREAT can still be used to upgrade or downgrade the call
type. However, if LCABILL=Y (yes), the table PFXTREAT has no effect
on whether a billing record is generated for a particular call.
This feature does not apply to centralized automatic message accounting
(CAMA) billing. It is not possible to suppress the generation of AMA
records or to create call code 006 records using AMAPRT in a CAMA-only
office.
Feature interactions
This feature’s method of determining whether a non-interexchange carrier
call is local or toll affects coin-line originations. The coin is not returned for
calls that are local; the coin is returned for calls that are toll.
All existing billing options that force the generation of AMA records will
continue to do so.
Interexchange carrier, private virtual network (PVN), E800, and outward
wide area telephone service (OUTWATS) calls are assumed to be billable.
PVN, E800, and OUTWATS calls are not affected by the values in the table
AMAPRT.

NTX901AA–10 297-1001-801i Standard 09.01 January 2000

 NTX901AA
AF1439
Non-interexchange carrier operator-assisted calls are assumed to be
non-billable.
If the value of field LCABILL in table LINEATTR is Y (yes), this feature’s
method of determining whether a call is local or toll billable is applied to the
following options:
• toll denied
• toll diversion
• toll essential
• remote message register
• remote message register for toll calls
• remote metered pulsing

This feature affects the following line options:

• Local Call Detail Recording (LCDR)
• Originating Subscriber Line Usage Study (SDY with LUS=Y)
• Complaint Observed (SDY with OBS=Y)

If the value of field LCABILL in the table LINEATTR is Y (yes), then the
call code 067 record is produced only if the call is found to be non-billable
by the new method.
Datafill
Table Description

AMAPRT Field OVERIDE is replaced by two new fields.

LINEATTR Field LCABILL is added.
TRKGRP Field LCABILL is added.

The field OVERIDE in the subtable AMAPRT of the table STDPRTCT is

replaced by two new fields, OVRIDIC and OVRIDLT. The two fields
designate whether interexchange and non-interexchange AMA records are
affected by the values in table AMAPRT.
The field LCABILL is added to the table LINEATTR to indicate the method
of determining whether a non-interexchange call is local or toll.
The field LCABILL is added to the table TRKGRP to indicate the method of
determining whether a non-interexchange call is local or toll.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX901AA–11

NTX901AA
AF1439
The values in the table LCASCRCN and its subtable LCASCR are used to
determine whether a non-interexchange call is billable, and if so, whether it
is billed as a local or toll call.
Automatic message accounting
No record formats are changed by this feature; only the office datafill
required to generate them is changed.

NTX901AA–12 297-1001-801i Standard 09.01 January 2000

 NTX901AA
AF1756
Feature name
LTG Capacity Increase
Description
AF1756 increases the maximum number of line treatment groups (LTG)
from 64 to 256. The use of different LTGs with a given line class code
(LCC) makes it possible to provide varying line attributes to different
subscribers within the same switching entity.
BCS history
This feature was created in BCS28.
Datafill
Table Description

LINEATTR The range of values for field LTG is increased from 0–63 to
0–255 .

Feature Description Manual Volume 2 of 3 BCS44.1i NTX901AA–13

NTX901AA
AF2565
Feature name
E800 on PX Trunks
Description
AF2565 provides the capability to support E800 and 800+ calls from private
exchange (PX) trunks.
BCS history
This feature was created in BCS31.
Operational measurements
Registers in the operational measurements group NSC are incremented for
E800 and 800+ calls from PX trunks.
Automatic message accounting
The existing billing records 141 and 142 are produced for E800 and 800+
calls from PX trunks.

NTX901AA–14 297-1001-801i Standard 09.01 January 2000

 NTX901AA
AF2599
Feature name
Test Desk Robustness
Description
AF2599 makes obsolete the BASIC version of local test desk (LTD) and
provides a fast test interface to the operating company.
BCS history
This feature was created in BCS31.
Hardware requirements
This feature requires the NT2X90AC or NT2X90AD test trunk card.
Datafill
The default value for the field VERSION in the table TRKGRP is changed
to TSTDSK. The value BASIC in the field VERSION is deleted.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX901AA–15

NTX901AA
AF2668
Feature name
RCU Line Card Configuration
Description
AF2668 provides DMS-100 urban subscribers with the ability to datafill
lines on a remote carrier urban (RCU) without the line hardware being
present. Unwanted alarms that are associated with unequipped line card
slots are suppressed through an initial datafill option. Standard service order
procedure is not affected.
BCS history
This feature was created in BCS31.
Restrictions and limitations
This feature prevents configuration alarms for plain ordinary telephone
service (POTS) RCU lines. All RCU line cards do not use this feature.
The cards using the subfield INSVC of the field CARDINFO in the table
LNINV cannot datafill the STATUS field as UNEQUIP. The INSCV field
already provides the disable or enable alarm function to these cards.
SSM, FXS, and FXO cards cannot datafill the STATUS field as UNEQUIP.
All lines on a line card carrier that are datafilled in the table LNINV must be
datafilled with a STATUS of UNEQUIP to prevent a configuration alarm.
A direct transition from a status of WORKING to UNEQUIP is not allowed.
Feature interactions
This feature interacts with AF2256 (SMU Four-wire Special Services).

NTX901AA–16 297-1001-801i Standard 09.01 January 2000

 NTX901AA
AG0649
Feature name
Enhanced Line Access Measurements – I
Description
AG0649 provides improved grade of service monitoring for the DMS–100
switch by establishing a set of customer line access measurements (LAM) in
the XPM-based peripheral modules (XPM). LAMs indicate the difficulty
experienced by a customer in trying to access a telephone network. The
measurements are provided in response to requests from central control (CC)
or another processor on the switch.
BCS history
This feature was created in BCS28.
Restrictions and limitations
The first call attempt on dial pulse or digitone lines after an XPM is returned
to service is not counted.
The first call attempt after the signaling type on a line is changed is not
counted.
If a line concentrating module (LCM) is out of service and takeover occurs,
the measurements are made for the LCM unit that takes over.
This feature collects LAMs only for peripheral modules that are based on the
line concentrating module including line concentrating modules, remote line
concentrating modules (RLCM), digital line modules (DLM), and very small
remotes (VSR). LAMs are not collected for line modules (LM), remote line
modules (RLM), remote concentrator terminals (RCT), remote carrier
SLC-96 (RCS), and remote carrier urban (RCU).
Operational measurements
OM group LINAC is added to report the LAMs sent to the CC from the
XPM. The measurements include call attempts, call failures, call abandons,
and dial tone delay.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX901AA–17

NTX901AA
AG1318
Feature name
Enhanced Line Access Measurements – II
Description
AG1318 provides the central control (CC) counterpart to feature AG0649
(Enhanced Line Access Measurements – I). AG0649 provides improved
grade of service monitoring for the DMS-100 by establishing a set of
customer line access measurements (LAM) in the XPM-based peripheral
modules (XPM). AG1318 stores the LAMs sent to the CC from the XPM in
a new operational measurements group.
BCS history
This feature was created in BCS28.
Restrictions and limitations
AG1318 requires feature AG0649 for proper operation.
Operational measurements
LINAC OM Group is added to store the LAMs. Four registers count call
attempts, call attempt failures, call abandons, and total dial tone delay.

NTX901AA–18 297-1001-801i Standard 09.01 January 2000

 NTX901AA
AG1854
Feature name
200 MS Disconnect Timing
Description
AG1854 provides Residential Enhanced Services (RES) lines with
disconnect signal timing that is equivalent to that of plain ordinary telephone
service (POTS) lines.
This feature also modifies disconnect signal timing for POTS and RES lines
with respect to the call waiting option, so that RES lines receive flash timing
only when necessary.
BCS history
This feature was created in BCS30.
Restrictions and limitations
This feature ignores RES customer group flash options. RES lines without
line flash options are unable to use customer group-defined flash options
such as group call transfer.
The RES line gets a reorder treatment when the CCW access code is dialed
when the following condtions are met:
• the RES line has both Call Waiting (CWT) and Cancel Call Waiting
(CCW) but has no other flash options
• parameter LINE_WITH_CWT_CAN_FLASH in OFCVAR is set to “Y”
• the CCW access code is not defined in the translations for the
appropriate RES customer group
Feature interactions
This feature interacts with the Call Waiting and Cancel Call Waiting
features.
Datafill
The AFIG option in field OPTLIST of table IBNLINES is no longer valid
for IBN or RES lines.
The office parameters CCW_ACTIVE in table OFCOPT,
CCW_AS_LINE_OPTION in table OFCVAR, and
LINE_WITH_CWT_CAN_FLASH in table OFCVAR require any type of
restart to activate a change to any of their values.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX901AA–19

NTX901AA
AG1973
Feature name
Distinctive Ringing on Ring Side Only
Description
AG1973 provides an office parameter to give the option of containing
ringing on all single party lines to the RING side of the line only. This
feature affects all types of line concentrating modules (LCM).
Prior to this feature, distinctive ringing features caused problems on message
waiting phones.
BCS history
This feature was created in BCS30.
Restrictions and limitations
This feature is not compatible with two-party lines using type A line circuit
cards. Type A line circuit cards include NT2X17 cards for line modules and
NT6X17 for LCMs.
Type B line circuit cards, typically NT6X18, should be used in conjunction
with this feature to maintain service for two-party lines.
Datafill
Office parameter ALLOW_RINGING_ON_TIP_SIDE is added to the
OFCENG table.

NTX901AA–20 297-1001-801i Standard 09.01 January 2000

 NTX901AA
AJ1224
Feature name
Open Numbering Plan Phase I
Description
AJ1224 adds a set of directory number (DN) tables to support the
introduction of universal directory numbers.
BCS history
This feature was created in BCS33.
Restrictions and limitations
A maximum of 100 terminating office numbers can be datafilled.
A maximum of 1 000 000 tuples can be datafilled in North America.
DNs are limited to 10 digits in North America. Variable length DNs cannot
be datafilled.
Datafill
Table Description

THOUGRP, Tables are deleted.

DN, and
WRDN
TOFCNAME Table is added to datafill valid terminating offices in the switch.
DNINV Table is added to datafill valid directory numbers in the office.
DNROUTE Table is added to datafill writable DNs in the switch.
LENLINES Field DN is modified to accept up to 15 digits.
IBNLINES Field DN is modified to accept up to 15 digits.

This feature increases data store by a maximum of 21 Mbytes.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX901AA–21

NTX901AA
AL1541
Feature name
Expansion of LCD Number to 1000
Description
AL1541 expands the number of available line concentrating devices (LCD)
on a DMS SuperNode from 255 to 1000.
BCS history
This feature was created in BCS30.
Restrictions and limitations
This feature is not available to NT40 offices.
The local test desk interface (provided through a maintenance trunk module)
is restricted to running diagnostics on line equipment numbers (LEN) with
frame components in the 0 to 99 range.
Datafill
The maximum number of LCDs is increased in the following LCD inventory
tables:
• DLMINV
• ISLMINV
• LCMINV
• LDTINV
• RDTINV
• LMINV
• LRUINV
• RCSINV
• RCTINV
• RCUINV
• RDTINV

NTX901AA–22 297-1001-801i Standard 09.01 January 2000

 NTX901AA
AL1608
Feature name
Line Card Code Expansion
Description
AL1608 optimizes the use of line card resources to eliminate the shortage of
line card resources in superset loads. Superset loads are in the development
environment only.
BCS history
This feature was created in BCS30.
Restrictions and limitations
This feature does not increase the number of available line cards in the
switch. The limit is still 63 line cards.
Table LNINV is the primary table in table control software that contains the
datafill for most lines. This feature assigns the line card codes when table
LNINV is datafilled. However, certain lines are not datafilled in table
LNINV; these cards are determined by packaging rules.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX901AA–23

NTX901AA
AR0491
Feature name
LTP Enhancement
Description
This feature increases the number of line test positions (LTP) on the MAP
(maintenance and administration position) from 15 to 64. It also provides a
means of releasing the LTP resources allocated to a user when that user has
been away from the LTP level for more than 1 h.
BCS history
This feature was created in BCS36.
Restrictions and limitations
The maximum number of LTP users is 64.
The maximum number of LTP users that can actively perform tests is
dependent upon the quantity of available test equipment. If no test
equipment is available, error messages are displayed.
Feature interactions
This feature requires 4 kbytes of data store for each LTP user.
User interface
This feature adds one LTP level hidden command, LTPRSRC, which is
associated with the LTP resource release mechanism. The LTP resource
release mechanism is invoked automatically when a user has been away
from the LTP level for 1 h, and frees the user’s LTP resource. Command
LTPRSRC allows the user to remove the LTP from the automatic release
mechanism, or to return it to automatic control, as required. A query option
allows the user to obtain information about the LTP resources and users.

NTX901AA–24 297-1001-801i Standard 09.01 January 2000

 NTX901AA
NC0020
Feature name
Key-pad Enable
Description
NC0020 provides additional data collection for coin calls by re-enabling the
coin station keypad once it has been determined that these are equal access
calls supported on access to carrier (ATC) or intertoll (IT) trunks.
BCS history
This feature was created in BCS33.
Restrictions and limitations
This feature applies only to ATC and IT trunks.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX901AA–25

NTX901AA
NC0313
Feature name
SERVORD Enhancements for SLE
Description
NC0313 creates a new service order (SERVORD) command CHL (change
list), which allows operating company personnel to add up to 20 directory
numbers (DN) at a time to a screening list editing (SLE) feature’s screening.
This feature also modifies the SERVORD command CHF (change feature),
so that it no longer manipulates an SLE feature’s screening list.
BCS history
This feature was created in BCS34.
Restrictions and limitations
The SERVORD command CHL affects the following SLE features only:
• Selective Call Acceptance (SCA)
• Selective Call Rejection (SCRJ)
• Selective Call Forwarding (SCF)
• Distinctive Ringing/Call Waiting (DRCW)

If the maximum number of DNs allowed on an SLE feature’s screening list

(as set by operating company personnel in table RESOFC) exceeds 20, then
command CHL may have to be executed multiple times in order to create a
complete list.
Command CHL must be executed for each type of change being made to a
screening list.
Feature interactions
This feature uses the following features:
• AG1580 Selective List Editing for Screening Lists
• AG1605 CLASS: Selective Call Rejection
• AG1628 CLASS: Selective Call Forwarding
• AG1629 CLASS: Distinctive Ringing/Call Waiting
• AG1675 CLASS: Selective Call Acceptance

NTX901AA–26 297-1001-801i Standard 09.01 January 2000

 NTX901AA
NC0313
Service orders
This feature introduces SERVORD command CHL, which allows operating
company personnel to add or delete up to 20 DNs at a time, or replace up to
ten DNs at a time in an SLE feature’s screening list.
Command CHL also allows operating company personnel to modify an SLE
feature’s billing option and feature status.
This feature modifies SERVORD command CHF so that it no longer
manipulates an SLE feature’s screening list.
User interface
This feature adds command CHL, and modifies command CHF in directory
SODIR at the SERVORD level of a MAP terminal.
Command CHL allows operating company personnel to add or delete up to
20 DNs at a time, or replace up to ten DNs at a time to an SLE feature’s
screening list. Command CHL also allows operating company personnel to
modify an SLE feature’s billing option and feature status.
Command CHF allows operating company personnel to change the billing
option and status of an SLE feature, but no longer manipulates an SLE
feature’s screening list.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX901AA–27

NTX901AA
NC0495
Feature name
Off-hook Testing
Description
NC0495 provides an automatic off-hook balance test to determine whether a
subscriber line should be on a 900 Ω + 2µF (900+2) balance network or on a
loaded or non-loaded balance network. This feature is applicable to
subscriber line circuits where a selectable line balance network is employed.
BCS history
This feature was created in BCS35.
Restrictions and limitations
This feature supports balance network tests on originating calls only.
This feature is available on domestic DMS-100 switches only.
Datafill
Table Description

LNADMIN Table is added to datafill office administration parameters

required for off-hook balance test.

LNBNV Table is added to datafill balance test information for each line.

Logs
This feature adds logs LINE220 to 222.
Log LINE220 is generated when the off-hook BNV test indicates that the
recommended BNV is the same as the existing BNV.
Log LINE221 is generated when the off-hook BNV test indicates that the
recommended BNV is different than the existing BNV.
Log LINE222 is generated when the off-hook BNV test does not complete
the line test.
User interface
This feature adds command QBNV at the command interpreter (CI) level of
a MAP (maintenance and administration position) terminal. Command
QBNV displays a range of lines with the existing balance network value
(BNV) and the associated recommended BNV.

NTX901AA–28 297-1001-801i Standard 09.01 January 2000

NTX901AA NTX901AA
TA0289 TA0289
Feature name
International FMA Support for the ISM
Description
This feature propagates the functionality required to incorporate the
Integrated Service Module (ISM), a new Trunk Module (TM)/Maintenance
Module (MTM) shelf type into the DMS switch. This feature enhances the
maintenance and diagnostic functions of the TM/MTM. The ISM is based
on a single controller card. The ISM shelf includes 15 general slots that can
be equipped with analog trunks, service circuits and Single Card Peripheral
Modules, as well as two additional slots dedicated to Single Card Peripheral
Modules.

This feature includes a new display function used to display information

about service circuits, analog trunks and Single Card such as Conference
Trunk Module (CTM) and Digital Trunk Module (DTM) that reside in the
ISM shelf.
BCS history
This feature was created in BCS41i.
Hardware requirements
• NTFX42AA ISM Controller Card
• NTFX4101 ISM Shelf Assembly
• NTFX43AA ISM DC Converter

Feature Description Manual Volume 2 of 3 BCS44.1i NTX901AA–29

 NTX904AA
R2 Signaling Base
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTX904AA contents
Feature number Description

AE0142 MFCR2–Protocol Definition Tables

AE0146 MFCR2 Routing Tables
AE1245 DMS-100I R2 Tariff Handling–Phase I
AG1217 R2 Call Processing
AG1218 R2 Register Signaling
AG1220 R2 Activity Tables
AJ0159 R2 Base Enhancements
AJ0205 R2 Protocol Enhancements
AJ1028 Generic R2 Enhancements
AJ2411 DMS-200I Telmex Auto-TBI
TA0165 Immediate Billing
TA0201 Chinese R2 (C1) A6 Enhancements
TA0320 R2 Flexible Signaling Mode
TA0331 R2 Immediate Billing Enhancement

TA0383 Reanswer Timer for R2 Trunks

BCS history
This feature package was created in BCS25.
BCS38i—TA0165 and TA0201 added.
BCS41i—TA0320 and TA0331 added.
BCS42i—TA0383 added.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX904AA–1

NTX904AA
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX270AA New Peripheral Maintenance Package
NTX470AA International–Common Basic
NTX801AA Toll Features I
or
NTX901AA Local Features 1

NTX904AA–2 297-1001-801i Standard 09.01 January 2000

 NTX904AA
AE0142
Feature name
MFCR2 Protocol Definition Tables
Description
This feature provides the table control required for multifrequency
compelled (MFC) R2 register signaling protocol variants for different
countries.
BCS history
This feature was created in BCS25.
Restrictions and limitations
Protocol definition tables MFCACT, ACTMFC, ACTGEN, and MFCPROT
are write-protected and must not be changed by an operating company. The
protocol supplied is datafilled by the load builders as part of the package
supplied.
Changes in the RSIGTYP field are restricted. An MFCR2 signaling type
cannot be modified and another signaling type cannot be changed to
MFCR2. Timing parameters in table RGSIGSYS can be changed by the
operating company.
Tables should be datafilled in the following order:
• MFCACT, ACTMFC, ACTGEN
• MFCPROT
• RGSIGSYS
• table TRKSGRP datafilled with RGSIGSYS index

Feature interactions
AE0142 is a feature in MFC-R2 register signaling for the international
digital trunk controller (IDTC). The other features are
• AE0139 MFC-R2 in IDTC
• AE0140 R2 for DMS-100 International – CC Description
• AE0146 MFC-R2 Routing Tables
• AE0171 Compeller Transactor and Protocol
• AE0172 Compelled Register Signaling Transactor
• AE0173 CRST - TAT Protocol

Feature Description Manual Volume 2 of 3 BCS44.1i NTX904AA–3

NTX904AA
AE0142
Datafill
Table Description

ACTGEN This new table (Multifrequency Compelled Activity Generator

Table) is one of the tables used to define R2 protocol.
ACTMFC This new table (Multifrequency Compelled Activity to Signal
Translation Table) is one of the tables used to define R2
protocol.
MFCACT This new table (Multifrequency Compelled Signal to Activity
Translation Table) is one of the tables used to define R2
protocol.

MFCPROT This new table (Multifrequency Compelled Protocol Tuples List

Table) is one of the tables used to define R2 protocol.
RGSIGSYS Refinement MFCR2 is added and the table is made available to
DMS-300 loads.

User interface
A new facility MFCtabs is added to the main MP monitor level for the
XMS-based peripheral module (XPM). This facility allows access to the
following tables after they have been downloaded from central control (CC):
• MFCACT
• ACTMFC
• ACTGEN
• CCDGTAN
• NATDGTAN

Table MFCPROT, downloaded as part of table RSS, can be accessed using

the RSS monitor command PMDEBUG.

NTX904AA–4 297-1001-801i Standard 09.01 January 2000

 NTX904AA
AE0146
Feature name
MFC-R2 Routing Tables
Description
This feature provides table support for the following special multifrequency
compelled (MFC) register signaling features:
• call state reporting to the far-end call originator
• peripheral module (PM) digit analysis for end-to-end connection support
• short access codes for test calls and operators

This feature also implements the XMS-based peripheral module (XPM)

portion of the digit analysis tables.
BCS history
This feature was created in BCS25.
Feature interactions
AE0146 requires feature AE0129 (MFCR2 CC Call Process Software) and
AE0145 (MFCR2 Task in PDTC).
AE0146 is a feature in MFC-R2 register signaling for the international
deigital trunk controller (IDTC). The other features are
• AE0139 MFC-R2 in PDTC – Main Feature
• AE0140 R2 for DMS-100 Intl – CC Description
• AE0142 MFC-R2 Protocol Definition Tables
• AE0171 Compeller Transactor and Protocol (International)
• AE0172 Compelled Register Signaling Transactor
• AE0173 CRST - TAT Protocol
Datafill
Table Description

CCDGTAN and These new tables are used for digit analysis by the XPM.
NATDGTAN
MFCTRMT This new table is used in the outgoing side. When a fault status
activity has been accepted, a treatment is connected to the
trunk according to this table.

—continued—

Feature Description Manual Volume 2 of 3 BCS44.1i NTX904AA–5

NTX904AA
AE0146

Table Description (continued)

TMTCNTL Table R2CPT (R2 Treatments Subtable) is added. This

subtable is optional and should only be provided to list
treatments for R2 trunk groups that differ from the treatments in
the Office Treatments Subtable.
TRMTMFC This new table is used in the incoming side when a treatment
has to be connected. It provides an MFC activity for each
treatment in the switch. It also determines what called status to
send on the line.

End

User interface
Tables CCDGTAN and NATDGTAN can be accessed from the multiparty
(MP) monitor facility MFCtabs. The user is allowed only read access to
these tables.

NTX904AA–6 297-1001-801i Standard 09.01 January 2000

 NTX904AA
AE1245
Feature name
DMS-100I R2 Tariff Handling – Phase 1
Description
This feature enhances existing international R2 register signaling as part of
the initial requirements to deploy the DMS-100 switch into the Polish
network. The feature also provides tariff information handling for
deployment of a DMS-100 switch as an originating and terminating local
office, and a tandem office supporting only tandem R2 register signals in
end-to-end mode.
BCS history
This feature was created in BCS36.
Restrictions and limitations
The new option TARIFF_LEN in table R2PROT is only supported for the
base protocol programmable international R2.
Toll Break-in (TBI) and TBI line signal are not supported.
Calling control is supported.
This feature does not support link-by-link mode.
The feature only tandems the R2 register signals in end-to-end R2
tandeming mode in tandem exchanges.
This feature does not support the generation of tariff signals C-1 to C-10.
The DMS-100 switch receives tariff signals but ignores them.
The DMS-100 switch does not generate meter pulses based on R2 tariff
signals. The metering is based on metering datafill in the local exchange.
The DMS-100 switch cannot function as a toll switch.
Billing is not supported.
Category screening is not supported. The DMS-100 switch does not screen
if both call parties have the same characteristics. The DMS-100 switch does
not generate a B-10 signal, which is based on a treatment indicating that
both parties do not have the same characteristics.
Option TARIFF_LEN in table R2PROT is available for each protocol or
trunk (rather than for each call). Option TARIFF_LEN must be datafilled in
R2PROT if RCV_TARIFF activity is valid and datafilled in table SIGACT
for the outgoing (OG) trunk.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX904AA–7

NTX904AA
AE1245
This feature is only supported on international digital trunk controllers
(IDTC).
The calling party category PRIORITY will be generated and interpreted as
regular if it is received. So, if priority calls cannot be completed as dialed,
they are not routed to the operator.
As an originating office, the DMS-100 switch sends automatic number
identification (ANI) digits once per call.
A maximum of 15 protocols can be supported in a DMS-100 switch.
Digit analysis must be used for the following:
• end-to-end mode
• requesting of ANI spill

A request for ANI spill is propagated back to the previous exchange in

link-by-link mode regardless of the traffic class of the tandem exchange’s
incoming trunk. The only exceptions are when the ANI spill has already
been requested or office parameter R2_ANI_DENY is set to Y.
ANI spill is provided in response to a request from a succeeding exchange
regardless of the traffic class of the outgoing trunk, unless office parameter
R2_ANI_DENY is set to Y.
Datafill
Table Description

R2PROT Option TARIFF_LEN is added to subfield OPTION.

ACTCTL, The following activities are added:

ACTSIG, and
SIGACT · RCV_TARIFF
· NEXT_TARIFF_DIGIT
· TARIFF_0 to TARIFF_9

User interface
This feature modifies command interpreter (CI) command R2VER. The
parameter DISP displays the number of tariff digits, which is datafilled in
the option TARIFF_LEN in table R2PROT, as an attribute of the protocol.
The feature also modifies the parameter VERF to display a warning message
related to the option TARIFF_LEN datafilled in table R2PROT.

NTX904AA–8 297-1001-801i Standard 09.01 January 2000

 NTX904AA
AG1217
Feature name
R2 Call Processing
Description
This feature provides the central control (CC) software required to support a
general purpose R2 system. This system is capable of handling
country-specific protocol variations.
BCS history
This feature was created in BCS28.
Restrictions and limitations
No interactions with other features are supported in this release of R2 call
processing.
End-to-end signalling is denied if
• incoming and outgoing trunks do not use the same R2 protocol
• translations prefix any digits
• the number of digits the previous office must back up does not map to
the digit positioning signal in the protocol used
Logs
Logs TRK312 and TRK313 are modified.
Log TRK312 is generated to indicate a signaling problem has been
encountered in an incoming trunk using multifrequency compelled (MFC)
signaling.
Log TRK313 is generated to indicate a signaling problem has been
encountered during or after outpulsing over a trunk using MFC signaling.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX904AA–9

NTX904AA
AG1218
Feature name
R2 Register Signaling
Description
This feature provides XMS-based peripheral module (XPM) software
support for a flexible R2 trunk register system in DMS-100 and DMS-200
switches. The feature provides a base R2 system in the XPM that supports
CCITT defined protocol and multiple country-specific variants.
BCS history
This feature was created in BCS28.
Hardware requirements
This feature requires provisioning of the following cards: NT6X69CA (CPP
message protocol and tones) and NT6X69KA (message protocol and tones)
in the XPM. These cards support R2 tones.
Feature interactions
AG1218 requires features AG1217 (R2 Call Processing) and AG1220 (R2
Activity Tables).
Datafill
Table Description

RGSIGSYS This feature adds the register signalling type NTRS11.

NTX904AA–10 297-1001-801i Standard 09.01 January 2000

 NTX904AA
AG1220
Feature name
R2 Activity Tables
Description
This feature implements the table control software required to enter protocol
specifications into a DMS-100 or DMS-200 switch. It can be used to
display or verify existing DMS protocol.
BCS history
This feature was created in BCS28.
Restrictions and limitations
The maximum number of protocols supported in a single DMS switch is 15.
This affects the size of table R2PROT.
The maximum number of logical phases in each direction is restricted to 16.
This affects table R2PROT.
The number of activities, including forward and backward activities, can
vary from 0 to 255. This range is sufficient for all protocols.
The sanity checks performed by command interpreter (CI) command
R2VER are not exhaustive and therefore, do not preclude errors in
datafilling R2 tables.
Datafill
Table Description

ACTCTL This new table provides the control mechanism to change

phases. It also provides the state of the processor in the XPM
that should be used to execute the action represented by the
activity.
ACTSIG This new table maps a requested activity to a signal to be sent.
It is accessed just before a signal is sent to another office.
ACTTRMT This new table maps an activity to an office treatment. It is
used when a backwards signal is received and must be
converted to a treatment to be applied.
R2PROT This table provides the definition of mappings and activity
controllers for each protocol.
SIGACT This new table maps an incoming signal to an activity.

—continued—

Feature Description Manual Volume 2 of 3 BCS44.1i NTX904AA–11

NTX904AA
AG1220

Table Description (continued)

TRKGRP Fields PROTOCOL_ID and TREATMENT_ID, which provide

indexes into table R2PROT in tables TRMTACT and
ACTTRMT, are added.
TRMTACT This new table maps a treatment to an activity. It is used when
an office recognizes that a treatment should be applied to a
call.

End

User interface
This feature introduces the new CI command R2VER. This command is
used to check the consistency of a protocol specification. It also is used to
verify the sanity of a protocol specification by determining if
• all the R2PROT indexes are datafilled
• all the tuples referenced by R2PROT indexes contain valid entries
• all entries are valid
• duplicate entries are present

NTX904AA–12 297-1001-801i Standard 09.01 January 2000

 NTX904AA
AJ0159
Feature name
R2 Base Enhancements
Description
This feature allows routing between R1 trunks and R2 trunks in the
DMS-100 and DMS-200 switch. The software included in the feature
provides a base for all R1 to R2 connections, regardless of protocol, and
implements R1 to R2 connection capabilities for the R2 protocols of
Morocco and Belize. The feature also provides outpulsing from the MAP
terminal to R2 trunks, which allows maintenance personnel to test R2
trunks.
BCS history
This feature was created in BCS28.
Restrictions and limitations
The following capabilities are not supported:
• tandeming of automatic number identification (ANI), including R1 to R2
and R2 to R1 connections
• connection of R2 and International Traffic Operator Position System
(ITOPS) trunks
Feature interactions
The following features interact with the R2 signaling system and behave in a
different manner:
• Coin Line
• Free Number Terminating (FNT)
• No Double Connect (NDC)

R2 trunks connect only to metering (MTR) and operator (OPER) type R1

trunks. Coin information is not transmitted. If the call is R1 to R2, the
calling category for Regular Subscriber is sent. If the call is R2 to R1, the
subscriber category Coin will not be propagated.
The current R2 protocol sends the called status Subscriber Line Free, No
Charge when the called subscriber has the FNT option. When the call goes
through an R1 to R2 connection, this signal is ignored and the call is
resupervised so that the answer back signal is not propagated.
When a call is originated from a line with NDC activated and passes through
an R1 trunk, the calling category Data is not propagated. If the call is
R1 to R2, the calling category for Regular Subscriber is sent. If the call is
R2 to R1, the office ignores the subscriber category.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX904AA–13

NTX904AA
AJ0205
Feature name
R2 Protocol Enhancements
Description
This feature implements the R2 protocol for Morocco supported by the
DMS-100/200 switch.
BCS history
This feature was created in BCS28.
Hardware requirements
This feature requires provision of an NT6X69LA (CPP message protocol
and downloadable tones CP) card and an NT6X92CA (international UTR
tone detection) card on international digital trunk controllers (IDTC).
Feature interactions
The following features interact with R2 trunk protocol and function
differently in an R2 environment:
• Call Waiting (CWT)
• Coin Line
• Free Number Terminating (FNT)
• Malicious Call Trace (MCT)
• No Double Connect (NDC)
• Toll Break-in (TBI)
• Call Diversion (CDIV)

If the DMS switch is a terminating exchange, and the called subscriber has
CWT and is busy, the called status signal sent to complete register signaling
is Subscriber Line Free, Charge. When the terminating line has CWT, the
called status signal is returned. In both cases, the DMS switch completes
register signaling, connects the originator to audible ringing, and normal
CWT processing continues for the duration of the call.
When a coin line originates a call over an R2 trunk not supporting the
calling category signal COIN, the DMS switch sends the Regular Subscriber
signal. As a tandem exchange, if the DMS switch receives the calling
category COIN from the originating R2 trunk, and this signal is not
supported by the terminating R2 trunk, the Regular Subscriber signal is
substituted for COIN.

NTX904AA–14 297-1001-801i Standard 09.01 January 2000

 NTX904AA
AJ0205
The DMS switch currently does not send the line signal Answer for calls
terminating on a line with FNT. With the R2 signal Subscriber Line Free,
No Charge, there is a method to convey this information to the originating
exchange. With this feature, calls over R2 trunks handle FNT in the
following manner:
• If the DMS switch is the terminating exchange, the register signal for the
called subscriber status Subscriber Line Free, No Charge is sent. When
the call is answered, the line signal Answer is sent to the incoming trunk.
• If the DMS is a tandem exchange in end-to-end mode, the signal for
Subscriber Line Free, No Charge will be tandemed.
• If the DMS is a tandem exchange in link-by-link mode, the DMS
processes the incoming Subscriber Line Free, No Charge signal as
follows:
— If the incoming R2 protocol supports the signal, it is sent to the
originating exchange and when it is received, the line signal Answer
is sent to the originating exchange.
— If the incoming R2 protocol does not support the signal, the called
status signal returned is Subscriber Line Free, Charge. When the line
signal Answer is received from the terminating exchange, it is not
sent to the originating exchange.
— If the incoming trunk from the originating exchange is R1, the line
signal Answer is not sent to the originating exchange when received
from the terminating exchange.
• If the DMS switch is an originating exchange and receives the called
status signal Subscriber Line Free, No Charge, the originating subscriber
is not billed for the call. The line signal Answer is expected and the call
is marked as such when received from the terminating exchange.
The DMS switch only supports MCT through line signaling. The only line
signalling system supporting MCT is NTLS09. If the terminating subscriber
has MCT, the DMS switch does not send the calling number over register
signaling during call setup. If the line signaling supports the MCT signal
and MCT is activated while the DMS switch is an originating or tandem
exchange, the affected trunks and lines are held until released from the MAP
(maintenance and administration position) terminal.
The DMS switch sends the calling category Data for calls originated by lines
with NDC activated. If the DMS switch is a terminating exchange, calls
with the calling category Data are not allowed to double connect.
Manual and automatic TBI are supported by the DMS switch. Calls
originating from an operator (manual TBI) and terminating on a DMS
switch do not send the R2 register signal Subscriber Busy. The subscriber

Feature Description Manual Volume 2 of 3 BCS44.1i NTX904AA–15

NTX904AA
AJ0205
status signal Congestion is sent and a busy tone is applied to the trunk in the
terminating exchange. The trunk connection remains up, allowing the
operator to send the TBI signal and break in on the subscriber. Automatic
TBI eliminates the requirement for the operator to manually initiate a TBI
signal. When the called party is busy, TBI is performed automatically. With
automatic TBI, no busy treatment is applied and the operator is sent a TBI
tone indicating a busy call has been broken into. The called subscriber
status signal Subscriber Line Free, Charge is returned by the terminating
exchange.
Calls terminating in a DMS switch where the subscriber has CDIV activated
have the Called Subscriber line status of the subscriber line diverted to
Returned.
Datafill
Table Description

ACTTRMT and Values COIN, OPER, DATA, PRIORITY, MTC_EQ,

TRTMTACT REQ_NOT_ACC, SUB_XFRD, TERM_CTRL_CHG, and
TEMP_OUT_ORD are added to field R2_ACTIVITY.

NTX904AA–16 297-1001-801i Standard 09.01 January 2000

 NTX904AA
AJ1028
Feature name
Generic R2 Enhancements
Description
This feature modifies table control software required to enter protocol
specifications into a DMS-100 or DMS-200 switch.
BCS history
This feature was created in BCS32.
Datafill
Table Description

ACTCTL This table provides the

· control mechanism to change phases
· state of the processor in the XMS-based peripheral module
(XPM) that should be used to execute the action
represented by the activity
· mechanism to partition phase changes from code and from
specific activities
ACTTRMT This table provides mapping from an activity to an office
treatment. It is used when a backwards signal is received and
must be converted to a signal to be applied.
CATCLASS This table is used to indicate which categories in an R2 protocol
are calling categories, billing categories, or both calling and
billing categories.
R2PROT This table provides the definition of mappings and activity
controllers for each protocol.
SIGACT This table provides mapping from an incoming signal to an
activity.
TRKGRP This table defines the data associated with existing trunk
groups.
TRTMTACT This table provides mapping from treatment to activity. It is
used when an office recognizes that a treatment should be
applied to a call.

User interface
This feature modifies the MAP (maintenance and administration position)
command interpreter (MAPCI) nonmenu command R2VER, which is used
to display or verify R2 protocol datafilled in tables ACTCTL, ACTSIG,
CATCLASS, R2PROT, and SIGACT.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX904AA–17

NTX904AA
AJ1028
The following parameters are available for the R2VER command:
• ALL Performs the function specified by the R2VER command
parameter on all protocols in table R2PROT.
• DISP R2 data is displayed in condensed form.
• PHASECHG R2 data for table ACTCTL is displayed showing only the
data where a phase change is requested.
• VALIDACT Lists the valid activities of a protocol.
• VERF The R2 data is audited for unused data, missing data, and
multiple activity-to-signal mappings. If problems are
detected, a warning is displayed.
• protocol Performs the function specified by the R2VER command
parameter on the protocol.

NTX904AA–18 297-1001-801i Standard 09.01 January 2000

 NTX904AA
AJ2411
Feature name
DMS-200I TELMEX Auto-TBI
Description
This feature provides R2 line signaling enhancements that perform
automatic Toll Break-in (TBI) for Mexico. Auto-TBI is performed on all
Traffic Operator Position System Multipurpose (TOPS MP) originated calls
routed to a DMS-200 switch through R1 operator trunks, leaving through R2
trunks, and terminating at a busy subscriber.
BCS history
This feature was created in BCS35.
Restrictions and limitations
This feature can reside only in a DMS-200 switch.
Operator-initiated TBI and Ring Forward are not supported by this feature.
When receiving auto-TBI signals, the DMS-200 switch does not recognize
forward signals Trunk Offering Start (TOS) or Trunk Offering End (TOE),
and the backward signal False Answer (FAN) unless filter timing for Clear
Forward (CLF) is datafilled to be greater than the duration of TOS or TOE
(150 ms ± 30 ms). A FAN signal shorter than 200 ms will be ignored at the
TOPS MP. A FAN signal longer than 200 ms will be interpreted as an
Answer (ANS) followed by a Clear Back (CLB), with a resulting change to
the on-hook display. A DMS-200 switch acting as a terminating exchange
will not generate a FAN signal.
Datafill
Table Description

OFCENG Office parameter MARKET_OF_OFFICE must be datafilled as

MEXICO.
TRKGRP An R1 trunk incoming from a TOPS multipurpose position (MP)
to a DMS-200 switch must be datafilled with a GRPTYP of
OPR.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX904AA–19

NTX904AA
TA0165
Feature name
Immediate Billing
Description
This feature provides the capability to generate time and charge information
for incoming trunk calls to a DMS-200 toll office on international
centralized automatic message accounting (ICAMA) trunks and works along
with programmable R2 trunk signaling. The time and charge information is
provided as soon as the call is completed.
BCS history
This feature was created in BCS38i.
Restrictions and limitations
Since there are 21 Attendant Pay Station (APS) logs in the log system, time
and charge information reports can be routed to a maximum of 21 output
devices.

Unanswered calls and calls for which no charges are incurred are logged
only if the office parameter APS_REPORT_ALL_CALLS is set to Y.

Office parameter CALL_REPORT_FORMAT in table OFCVAR must be set

to LOG for the generation of the log reports.

This feature can be applied only to incoming trunks providing ICAMA

billing.

The field ANI_SNPA in table TRKGRP must be set to Y in order to include

the Serving Number Plan Area (SNPA) in the automatic number
identification (ANI) digits. If SNPA is not prefixed to the ANI digits, then
the office is not able to identify from which line this call is originated and
cannot provide a log report through the expected route.
Feature interactions
The SNPA for the ANI digits should be prefixed to the ANI digits in order to
route the logs correctly. This is achieved by using the feature TA0166
(Flexible ANI Enhancements).

All interactions that are present for feature AG1108 (APS-I) also apply for
this feature.
Logs
The number of APS logs is increased from 13 to 21 and APS became a log
report in the range APS113 to APS120.

NTX904AA–20 297-1001-801i Standard 09.01 January 2000

 NTX904AA
TA0201
Feature name
Chinese R2 (C1) A6 Enhancements
Description
This feature supports the A6 signal in the Beijing Network. Beijing is a
submarket in which C1 signaling is different from the main telephone
network market in China.
Office parameter SPECIAL_HANDLING_C1_A6 is created to activate this
feature in table OFCVAR. The parameter values are Y and N. The default
value is N. The A6 signaling is affected only when the parameter is set to Y.
When this feature is not in effect, the terminating or tandem office sends an
A6 signal to the terminating toll office. Then the terminating toll office
forwards the A6 signal to the originating toll office.
When this feature is in effect, the A6 signal is not forwarded to the
originating toll office.
BCS history
This feature was created in BCS38i.
Restrictions and limitations
This feature is for only the Beijing Network market.
There must be at least three digits in the OFC field of the first tuple in table
DNHEAD.
Datafill
Table Description

OFCVAR Office parameter SPECIAL_HANDLING_C1_A6 is added. The

parameter values are Y and N. The default value is N.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX904AA–21

NTX904AA
TA0320
Feature name
R2 Flexible Signaling Mode
Description
This feature provides the capability to switch the signaling mode on
translation. This capability is used to handle the signaling modes of all
tandem calls as END_TO_END except the tandem calls with traffic class
datafilled as CAMA. The LINK_BY_LINK option is necessary to collect
ANI and B-party number for billing purposes.
BCS history
This feature was created in BCS41i.
Restrictions and limitations
This feature is restricted for programmable R2. The trunks must have
programmable R2 as Base Protocol.
Datafill
Table Description

TRKGRP In field TANDEM_MODE, a new option FLEX (FLEXIBLE) is

added to IC and OG trunks

NTX904AA–22 297-1001-801i Standard 09.01 January 2000

 NTX904AA
TA0331
Feature name
R2 Immediate Billing Enhancement
Description
This feature disables and enables the generation of Attendant Pay Station
(APS) logs in either local or tandem office or both if used in conjunction
with the APS line option, enables the generation of the TIME_AND_CHG
(Time and Charge) R2 category and sending it to toll offices if the line has
the line option Centralized Billing (CBIL).

After the completion of a call, calling party is charged in the service halls
by an attendant supervisor immediately. Thus, the lines in the service halls
have the special ability to issue a billing request for immediate charging.
When the call terminates, DMS–200i generates a log indicating the charges
incurred for the call. Log system routes the APS log to a device after
assigning the related class codes. APS1nn logs are used for reporting the
time and charge information.
BCS history
This feature was created in BCS41i.
Restrictions and limitations
This feature supports only R2 trunks.

The service provided with this feature applies only to incoming trunks
providing ICAMA billing to their subtending originating offices.
Service orders
Centralized Billing (CBIL) option is assigned to a subscriber line.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX904AA–23

NTX904AA
TA0383
Feature name
Reanswer Timer for R2 Trunks
Description
This feature supports the reanswer timer function for outgoing (OG) and
two-way (2W) R2 trunks.
This feature supports the following interworkings:
• line to R2
• R2 to R2
• CTUP to R2
• C1/MFP to R2
• C1/DP to R2
• ISUP to R2

The reanswer timer for both lines and trunks is datafilled in field REANSTO
in table CTRLTMRS. For trunks, however, the actual timer value is 10 s
greater than the datafilled value. For example, a datafilled value of 210
means 210 s for a line and 220 s for a trunk (the maximum of 255 s is
unchanged). A datafilled value of 0 applies to both lines and trunks.
Office parameter REANSWER_TIMER_FOR_R2_TRUNK is introduced in
table OFCVAR.
BCS history
This feature was created in BCS42i.
Hardware requirements
Not applicable
Restrictions and limitations
The following restrictions and limitations apply:
• If the reanswer timer is not used for lines, it cannot be used for trunks.
• Datafilling a timer value greater than 245 has no effect on trunks; 255 s
is the maximum allowance for both lines and trunks.
Feature interactions
Not applicable

NTX904AA–24 297-1001-801i Standard 09.01 January 2000

 NTX904AA
TA0383
Datafill
Table Description

OFCVAR Office parameter REANSWER_TIMER_FOR_R2_TRUNK is

added.
The range of values is Y or N. The default is N.

Service orders
Not applicable
Operational measurements
Not applicable
Logs
Not applicable
User interface
Not applicable
Automatic message accounting
Not applicable

Feature Description Manual Volume 2 of 3 BCS44.1i NTX904AA–25

 NTX909AA
ANI Toll
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTX909AA contents
Feature number Description

AE0115 ANI Reception in DMS-200

BCS history
This feature package was created in BCS23.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX056AA Enhanced Administration
NTX270AA New Peripheral Maintenance Package
NTX470AA International–Common Basic

Feature Description Manual Volume 2 of 3 BCS44.1i NTX909AA–1

NTX909AA
AE0115
Feature name
ANI Reception in DMS-200
Description
This feature introduces automatic number identification (ANI) to DMS
switches outside North America. AE0115, along with AE0116 (ANI
Outpulsing in DMS-100/200), provides the capability of sending and
receiving the directory number (DN) of the calling party from a DMS-100
switch or other local exchange, to a DMS-200 switch, over specialized ANI
trunks.
BCS history
This feature was created in BCS23.
Restrictions and limitations
The following restrictions apply to this feature:
• The type of ANI request signal supported is a wink-type signal (as
opposed to a permanent offhook).
• No provision is made for presetting a threshold on ANI request failures.
No special alarms or logs are generated for excessive ANI failures. Each
failure is individually logged.
• In a toll exchange, the called number is witheld until complete ANI
information is received (as opposed to withholding the called number
until the first ANI digit is received).
• No provision is made to tandem ANI information. The first toll
exchange is assumed to be the centralized automatic message accounting
(CAMA) office.
• ANI outpulsing interacts with conferencing and transferring as part of
this feature.
• The ANI option is added only to one-way incoming and one-way
outgoing trunks. Two-way trunks are not supported.
Feature interactions
AE0115, along with AE0116, is required for billing and verification
features, which procure and make accessible calling numbers and station
classes to International Traffic Operator Position System (ITOPS) and
international CAMA (ICAMA) applications.
In the combined DMS-100 and DMS-200 configuration, ANI information is
transferred internally, so there is no need for looparound ANI trunks.
ANI outpulsing does not interact with other features.

NTX909AA–2 297-1001-801i Standard 09.01 January 2000

 NTX909AA
AE0115
Datafill
Table Description

LNSIGSYS Added a new field for ANI request signal, which in its definition
includes
· ANI request timeout
· post-ANI request delay
TRKGRP Trunk group type ANI is added to accommodate the ANI option.
This trunk group type is used for ICAMA/ITOPS calls.

Added new fields for ANI format and number of digits to

outpulse.

Automatic message accounting

This feature does not provide subscriber billing information. It provides the
information required by billing applications to produce call records. No
metering information is provided.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX909AA–3

 NTX910AA
ANI Local
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTX910AA contents
Feature number Description

AE0116 ANI Outpulsing in DMS-100/200

BCS history
This feature package was created in BCS23.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX910AA–1

NTX910AA
AE0116
Feature name
ANI Outpulsing in DMS-100/200
Description
This feature introduces automatic number identification (ANI) to DMS
switches outside North America. The feature, along with AE0115 (ANI
Reception in DMS-200), provides the capability of sending and receiving
the directory number (DN) of the calling party from a DMS-100 switch or
other local exchange, to a DMS-200 switch, over specialized ANI trunks.
BCS history
This feature was created in BCS23.
Restrictions and limitations
The following restrictions apply to this feature:
• The type of ANI request signal supported is a wink-type signal (as
opposed to a permanent offhook).
• No provision is made for presetting a threshold on ANI request failures.
No special alarms or logs are generated for excessive ANI failures. Each
failure is individually logged.
• In a toll exchange, the called number is witheld until complete ANI
information is received (as opposed to withholding the called number
until the first ANI digit is received).
• No provision is made to tandem ANI information. The first toll
exchange is assumed to be the centralized automatic message accounting
(CAMA) office.
• ANI outpulsing interacts with conferencing and transferring as part of
this feature.
• The ANI option is added only to one-way incoming and one-way
outgoing trunks. Two-way trunks are not supported.
Feature interactions
AE0116, along with AE0115, is required for billing and verification
features, which procure and make accessible calling numbers and station
classes to International Traffic Operator Position System (ITOPS) and
international CAMA (ICAMA) applications.
In the combined DMS-100 and DMS-200 configuration, ANI information is
transferred internally, so there is no need for looparound ANI trunks.
ANI outpulsing does not interact with other features.

NTX910AA–2 297-1001-801i Standard 09.01 January 2000

 NTX910AA
AE0116
Datafill
Table Description

TRKGRP Trunk group type ANI is added to accommodate the ANI option.
This trunk group type is used for ICAMA/ITOPS calls.

Added new fields for ANI format and number of digits to

outpulse.
LNSIGSYS Added a new field for ANI request signal, which in its definition
includes
· ANI request timeout
· post-ANI request delay

Automatic message accounting

This feature does not provide subscriber billing information. It provides the
information required by billing applications to produce call records. No
metering information is provided.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX910AA–3

 NTX940AA
CM Bilge
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTX940AA
Feature number Description

AL0709 CM REXTEST Enhancements

AL1923 Enhanced CM Maintenance CPU Alarms
AL0631 Enhanced 9X12 Diagnostics
AL0727 Message Switch Software Support for 9X32
AL0548 MS MAP, MMI, and Log Enhancements
AL0720 Rewrite Store Allocator
AL0706 24-MB Memory for CM SW (Phase 1)
AL0809 DMS-BUS Software Support for the New 9X23 Back Card
AL1109 CMIC Link Diagnostic Enhancements
AL2328 Series 3 Base Hooks
AR0160 BCS34 Hook Feature for 7N10

BCS history
This feature package was created in BCS23.
Required feature packages
Feature package Description
number

NTXR46AA Robustness Enhancements

Feature Description Manual Volume 2 of 3 BCS44.1i NTX940AA–1

NTX940AA
AL1109
Feature name
CMIC Link Diagnostic Enhancements
Description
AL1109 enhances the DMS-bus and message controller (MC) link
diagnostics and out-of-service fault detection. This feature reduces time link
failures by detecting links before they are introduced into the system.
BCS history
This feature was created in BCS31.
Logs
The CM54 log is modified to include a new field, OPT_MCNO, which
indicates that the TSTNAME test, indicated on the same line, failed to run
on the specified MC.
User interface
The TST, BSY, and REXTST commands are changed at the computing
module (CM) level, and the BSY command is changed at the the MS level.
The TST command performs an in-service or out-of-service test on the
specified MC and is modified to enable users to specify the number of
messages to send during the looparound test. An optional parameter
indicates whether the hit counts associated with the MC links should be
cleared if the out-of-service test passes.
The BSY command busies the specified MC if all the links on the other MC
are stable; otherwise the command is aborted. This can be overridden with
the FORCE option.
The REXTST command performs a routine exercise (REX) test on the
specified class. An additional parameter is added to clear the hit counts if
the MC REX test passes. These are used to determine if the MC REX can
run. If the test fails, or if the parameter is not specified, the counts are
cleared. The option is valid only with the LINK or ALL classes. The
system REX always clears the counts.

NTX940AA–2 297-1001-801i Standard 09.01 January 2000

 NTX940AA
AL1718
Feature name
DDM Enhancements for INM
Description
AL1718 enhances distributed data manager (DDM) functionality by
providing an improved interface to node maintenance. The feature provides
the following options:
• multistage data sync interface to the DDM for node maintenance
• supporting interface for requests for data sync from remote DDM nodes

BCS history
This feature was created in BCS33.
Restrictions and limitations
Series 3 peripheral node maintenance entities that use the DDM (link
interface module and link interface unit number 7) must be modified to
accommodate changes in the data sync interface.
Existing applications (for example, Common Channel Signaling No. 7 and
integrated link maintenance) must be modified to function with DDM.
Datafill
This feature increases data store by 26 Kbytes.
Logs
The following logs are modified by this feature: DDM100, DDM101,
DDM102, DDM103, DDM104, DDM105, DDM106, and DDM107.
Log DDM100 is generated whenever the DDM successfully completes a
downloading of data to a node.
Log DDM101 is generated whenever the DDM fails to download the
distributed data to the node.
Log DDM102 is generated whenever the DDM fails to download an update
to the distributed data of the node.
Log DDM103 is generated whenever the DDM successfully completes the
downloading of data to a node for a single table.
Log DDM104 is generated whenever a DDM determines that distributed
data is no longer able to maintain data in the peripheral module (PM) node.
Log DDM105 is generated whenever the DDM determines that distributed
data is available in the PM node.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX940AA–3

NTX940AA
AL1718
Log DDM106 is generated whenever an audit of the distributed data fails.
Log DDM107 is generated whenever an attempt to retrieve operational
measurement data fails.

NTX940AA–4 297-1001-801i Standard 09.01 January 2000

 NTX940AA
AL1923
Feature name
Enhanced CM Maintenance CPU Alarms
Description
AL1923 provides additional computing module (CM) maintenance software
to monitor processor clock failures, and to indicate such failures with logs
and alarms. Existing CM maintenance command functions are made more
robust in their handling of processor clock failures. Processor clock sources
of the CPUs are made more visible.
BCS history
This feature was created in BCS32.
Hardware requirements
The basic duplex CM complex is required.
Datafill
This feature increases permanent data store by a maximum of 1 Kbyte.
Logs
Log CM162 is added. Log CM162 is generated when a central processing
unit (CPU) processor clock is faulty.
Log CM101 is modified to report the processor clock sources of both CPUs.
Log CM125 is modified to include a TEST TEXT for processor clock test
failures during a CPU test.
User interface
The following commands are modified in directory CMDIR:
• Command TST is modified to include the processor clock test.
• Command SWACT is modified to check the processor clock of the
inactive CPU, and to disallow the switch of activity (SWACT) if the
inactive clock is faulty. Command SWACT checks whether the CM will
run in the processor clock of the newly inactive CPU after a SWACT. If
the CM does not run, the SWACT process continues as usual.

If the CM runs, a warning prompt is displayed to indicate that the CM

will dropsync and then sync again in order to switch the processor clock
source. If YES is indicated, a SWACT-dropsync-sync is performed. If
NO is indicated, the SWACT request is not performed.
• Command SWACT NOCHECK is used to bypass the SWACT check.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX940AA–5

NTX940AA
AL1923
• Command DPSYNC is modified to disallow DPSYNC if the clock of the
active CPU is faulty.
• Command QUERYCLK is added in directory CMDIR to query the
processor clock source of each CPU.

NTX940AA–6 297-1001-801i Standard 09.01 January 2000

 NTX940AA
AL2042
Feature name
Interrupt Level Communication
Description
AL2042 enhances the communication software between base level processes
and interrupt processing. This feature allows applications to send messages
from interrupt level 2 without setting up message queues.
BCS history
This feature was created in BCS33.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX940AA–7

NTX940AA
AL2328
Feature name
Series 3 Base Hooks

Description
AL2328 prepares the base system software for synchronous optical network
(SONET) DMS (S/DMS) series 3 features.

BCS history
This feature was created in BCS34.
Feature interactions
This feature interacts with the following features :
• AL1839—ENET Integrity Fault Handler for ISN
• AL1939—Connection Support Enhancements III
• AI0410—Network Interface Unit (NIU) Central Maintenance

NTX940AA–8 297-1001-801i Standard 09.01 January 2000

 NTX940AA
AR0160
Feature name
BCS34 Hook Feature for 7N10

Description
AR0160 prepares the DMS base layer to support features in the IN layer for
the switching control point II (SCPII) project. Preparatory work includes
the following activities:
• enhancing CCS alarms to include update batch handler (UBH) alarms
• placing UBH logs and associated information in the integrated event
management (IEM) system in the DMS base
• entering UBH operational measurements (OM) in the DMS base
BCS history
This feature was created in BCS34.
Feature interactions
This feature interacts with feature AL2089 (SCP II UBH MAP Level).

Feature Description Manual Volume 2 of 3 BCS44.1i NTX940AA–9

 NTX941AA
CM Common
This feature package applies to DMS SuperNode offices.
Feature package contents
Feature package NTX941AA contents
Feature number Description

AL1054 DMS-core Enhanced Image Test

AL1197 DMS-core Inventory Audit
AL1182 DMS-core Link Hit Analysis
AL1055 DMS-core REX Test Speedup II
AL1053 Enhanced DMS-core Mate Link RTS
AL1192 Enhanced DMS-core Memory Alarm
AL2331 E2A Monitoring Software
AL1193 Porting DMS-core Maintenance to Run on RISC (Phase I)
AL0707 24-MB Memory CM SW (Phase II)
AL0710 6-MB Memory (SYNC Override)
AL0269 9X14BA 6M Memory Maintenance S/W Support
AL2021 Distributed Log System
AL1681 Integrated Event Management System Base Phase I
AL0797 DMS-bus MMI Enhancements
AL1480 Central DMS-bus MMI Information for Message Channels
AL1968 DMS-bus Backwards Compatibility Support
AQ0854 MS Backwards Compatability—II
AQ0741 SuperNode Clock Robustness Restructure—I
AL1183 DMS-bus Central Communication Audit Enhancements
AL1884 DMS-bus Message Flow Control—II
AL1826 DMS-bus MMI Enhancements for ISN
AL1782 NT9X62BA OD1 Support
AL1202 DMS-bus Central Support for Downloadable CMU Firmware
AL1201 DMS-bus Central SW Enhancements for P-side Node
Isolation
AL1346 DMS-bus CMU Firmware Downloading II

—continued—

Feature Description Manual Volume 2 of 3 BCS44.1i NTX941AA–1

NTX941AA
Feature package NTX941AA contents (continued)
Feature number Description

AL0803 DMS-bus MMI Enhancements II

AL1200 DMS-bus MMI Enhancements III
AL2030 System REX Test Controller
AG2480 Footprint Enhancements
AQ0721 Hardware Baseline Monitor
AL1759 Maintenance Action Pre-check
AL1753 NT9X12AC Software Support
AL1570 System Recovery Controller Interfaces
BC1826 Central Message Switch Maintenance
BC1827 CM In-sync Maintenance Software
BC1909 Time of Day Support for Enhanced Core
BC1932 Remote Login
BC2003 Distributed Log System
AI0625 Software Support for 96 MB Memory
AI0630 DMS-core Mismatch Handler CI Tool—MMI
AQ0834 16 MB Processor on DMS-bus
AQ0859 DMS-bus SW Support for Multiport Interface Cards
AR0211 CM Alarm Suppression During REX Test

End

BCS history
This feature package was created in BCS23.
Required feature packages
Required feature packages
Feature package Description
number

NTX001AA Common Basic

NTX941AA–2 297-1001-801i Standard 09.01 January 2000

 NTX941AA
AG2480
Feature name
Footprt Enhancements
Description
AG2480 improves the collection of data and the management of buffers in
the existing footprint facility. New reports are introduced to record some
low-level events.
BCS history
This feature was created in BCS33.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX941AA–3

NTX941AA
AI0625
Feature name
Software Support for 96-MB Memory Cards on DMS-core
Description
AI0625 implements the DMS-core maintenance software that supports the
NT9X14EA (96-MB memory card) in the memory diagnostics, routine
exercise (REX) tests, memory sparing, and memory extensions.
BCS history
This feature was created in BCS35.
Feature interactions
This feature requires the following features:
• AI0607 Firmware Support for 9X14EA Memory Card
• AL2043 SOS Support for 96-MB Memory
This feature interacts with the following features:
• AL0471 Computing Module Mismatch Handler Enhancements
• AL0706 24MB Memory CM SW (Phase I)
• AL0707 24MB Memory CM SW (Phase II)
• AL0710 6MB Memory (Sync Override)
• AL2043 SOS Support for 96M Memory
• BC1827 CM In-Sync Maintenance Software
User interface
This feature modifies MAP commands SYNC and INSYNC in directory
CMDIR, and command CONFIG in directory CMMEMDIR.
Command SYNC places the CPUs in synchronism.
Command INSYNC queries the status of the active central processing unit
(CPU), checks whether the inactive CPU is jammed, and queries memory
error correction.
Command CONFIG is used to configure the memory cards.

NTX941AA–4 297-1001-801i Standard 09.01 January 2000

 NTX941AA
AI0630
Feature name
DMS-core Mismatch Handler CI Tool—MMINFO
Description
AI0630 provides the command interpreter (CI) facility MMINFO (mismatch
info), which provides a method of analyzing sync-match node mismatches
within a DMS SuperNode switch.
BCS history
This feature was created in BCS35.
Feature interactions
This feature requires feature AI0130 (Computing Module Mismatch Handler
Enhancement).
Datafill
This feature increases data store by a maximum of 80 kbytes.
Logs
This feature modifies logs MM100 and MM101, and deletes logs MM105
and MM106.
Logs MM100 and MM101 are generated when a mismatch occurs and both
central processing units (CPU) are operating in sync mode.
User interface
This feature adds MAP command MMINFO in directory PROGDIR. This
command displays the mismatch information from the MMINFO database.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX941AA–5

NTX941AA
AL0797
Feature name
DMS-bus MMI Enhancements
Description
AL0797 provides MAP, table control, logs, and OM support for chain
interface cards in a DMS-bus.
BCS history
This feature was created in BCS28.
Hardware requirements
This feature requires the following cards:
• NT9X20BA – channelized DS512 back card
• NT9X23BA – channelized DS30 back card
• NT9X25AA – shorting bus interface card
• NT9X25BA – shorting bus terminator interface card
• NT9X17AB – 4–port interface card

Datafill
The following table was modified for this feature:

Table Description

MSCDINVs Cardtype CHAIN is added, enabling user to add, modify, and

delete chains.

User interface
A new MAP level – CHAIN – is added for chain card maintenance.
The MS SHELF level commands and display are updated to include chain
maintenance information.

NTX941AA–6 297-1001-801i Standard 09.01 January 2000

 NTX941AA
AL0803
Feature name
DMS-bus MMI Enhancements II
Description
AL0803 provides DMS-bus (central) software and man-machine interface
(MMI) support for the 128-port interface card. This feature also enhances
the chain MMI with log generation and operational measurement (OM)
maintenance. Enhancements include minor modifications to commands in
the CARD and SHELF levels and the addition of commands to the CARD
and CHAIN levels.
BCS history
This feature was created in BCS31.
Hardware requirements
This feature requires the 128-port interface card NT9X17CA.
Restrictions and limitations
The 128-port card capability provided by this feature is available in offices
equipped with 128-port interface cards.
The enhancements to the CHAIN level, the modified QUERYMS and
TRNSL commands, the CHAIN logs, the CHAIN OMs, and the channelized
line logs and OMs are present only in offices that have chain capability.
Feature interactions
This feature interacts with message switch (MS) MAP functions.
Datafill
The following tables are modified for this feature:

Table Description

MSCDINV NT9X17CA is added to the CHAIN, DS30 and DS512 ranges in

field FRONTPEC to support the 128–port interface card.
OFCOPT Office parameter NEW_DS30_LINK_HANDLER is added.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX941AA–7

NTX941AA
AL0803
Operational measurements
The OM group MSCHAIN is added for the chain resource. The OM group
MSCHNLK is added for the channelized link resource. The following
registers in the MS OM group are renamed:
• MSLKERR to MSPTERR
• MSLKFLT to MSPTFLT
• MSLKDIA to MSPTDIA
• MSLKDIAF to MSPTDIAF
• MSLKMBP to MSPTMBP
• MSLKMBU to MSPTMBU
• MSLKSBU to MSPTSBU

The MS clock cards are modified to count the node diagnostics registers in
the MS OM group. This modification affects registers MSDIA and
MSDIAF.
Logs
This feature adds the following logs for the chain resource: MS150, MS151,
MS152, MS153, MS154, MS155, MS156 and MS157. This feature adds the
log MS277 for the cards in a chain. The following logs are added for the
channelized link resource: MS280, MS281, MS282, MS283, MS284,
MS285, MS286 and MS287.
User interface
The QUERYMS and TRNSL commands are modified to support chain
software. The CARD command at the SHELF level is modified if 128–port
software is present in the load. The NEXT and PORT commands are added
to the CARD level if 128–port software is present in the load. The TST,
BSY, and RTS commands are modified at the CARD level to accept up to
128 ports and to use the proper naming conventions.

NTX941AA–8 297-1001-801i Standard 09.01 January 2000

 NTX941AA
AL1053
Feature name
Enhanced DMS-core Maintenance Link RTS
Description
AL1053 modifies initiation of split-mode on the DMS-core; it is no longer
necessary to restart on the inactive CPU. Responses to the MATELINK
RTS command are improved to reflect the status of the link.
BCS history
This feature was created in BCS29.
Restrictions and limitations
Both CPUs must have a BCS29 or higher load to avoid inactive restart.
Logs
A new failure reason – “Attempt to isolate an MS” – is added to the CM141
log; it occurs when an attempt is made to enter split mode when two links to
the same MC are out-of-service.
User interface
Optional parameter FORCE is added to the MATELINK RTS command for
use when only one MS is in service.
Failure reasons are provided when a matelink cannot be returned to service.
Two optional parameters are added to the MATELINK STATUS command:
the FULL option returns message information for all matelink users and the
CLEAR option enables the user to reset messaging information for all users.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX941AA–9

NTX941AA
AL1054
Feature name
DMS-core Enhanced Image Test
Description
AL1054 modifies the DMS-core image test, which provides a means of
detecting problems with the load before a critical situation arises.
Essentially, the image test is the DMS-core equivalent of the existing NT40
test.
BCS history
This feature was created in BCS28.
Restrictions and limitations
It is not possible to fully simulate a logged-in user. This is because the image
test, once running, is automated and terminal input is not possible. In
addition, the active CPU uses the relevant hardware, so its sanity cannot be
checked.
Logs
Logs CM116 and CM117 are updated to include the type of restart executed
on the inactive CPU. The CM116 also includes a list of tests that were failed
or did not run.
A new log–CM155–is generated when the sanity of the image cannot be
conclusively determined.
User interface
The CMMNT MAP level has been updated to include more information
about the image and image test. In addition, two CMMNT commands have
been updated.
The IMAGE command has new parameters which enable the user to
• specify the type of restart to be performed
• change the type of restart the next test executes
• query the system for image and test status information
• downgrade alarm associated with test failure from critical to minor

The ALARM command has been modified to block the disabling of the
IMAGE alarm.

NTX941AA–10 297-1001-801i Standard 09.01 January 2000

 NTX941AA
AL1055
Feature name
DMS-core REX Test Speedup II
Description
AL1055 further reduces the time required to run routine exercise (REX)
tests by reducing the number of times the test must re-synchronize the
DMS-core between individual tests.
BCS history
This feature was created in BCS28.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX941AA–11

NTX941AA
AL1182
Feature name
DMS-core Link Hit Analysis
Description
AL1182 provides a summary of message controller (MC) link hit data in a
daily log and new MAP level commands to query and reset link hit counters.
BCS history
This feature was created in BCS29.
Logs
Logs CM128 and CM140 are modified to include link information.
Logs CMSM101 and CMSM102 are introduced to tabulate link hits.
Logs CM127 and CM139 are deleted.
User interface
Six MAP level commands are introduced to permit the operating company
personnel to query and reset link hit counters; these are independent of the
counters used to generate logs.

NTX941AA–12 297-1001-801i Standard 09.01 January 2000

 NTX941AA
AL1183
Feature name
DMS-bus Central Communication Audit Enhancements
Description
AL1183 improves the communication audit which operates between the
DMS-core and each message switch (MS), by isolating and taking out of
service any message switch that could impact system performance.
BCS history
This feature was created in BCS29.
Datafill
The following table was modified for this feature:

Table Description

OFCENG Office parameter DMSBUS_POLL_FREQUENCY is added to

enable craftsperson to set the polling rate for this feature.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX941AA–13

NTX941AA
AL1192
Feature name
Enhanced DMS-core Memory Alarm
Description
AL1192 modifies existing DMS-core memory-related alarms and arranges
them into critical, major, and minor categories to comply with the
requirements of Generic Switching Systems.
BCS history
This feature was created in BCS29.
Logs
A new log–CM158–is generated when a low spare memory condition is
serious enough that maintenance action is required.
Three existing logs–CM111, CM112, and CM123–are modified to raise
alarms when generated.
User interface
The CMMNT MAP level ALARM command is modified to permit the
enabling and disabling of the new DMS-core “LOWSpr” (low spare
memory) major alarm.

NTX941AA–14 297-1001-801i Standard 09.01 January 2000

 NTX941AA
AL1193
Feature name
Porting DMS-core Maintenance to Run on RISC (Phase I)
Description
AL1193 provides software support for the NT9X10AA processor circuit
card and the NT9X26DA remote terminal interface (RTIF) paddle board in
the software maintenance system of the DMS-core in a DMS SuperNode.
BCS history
This feature was created in BCS33.
Hardware requirements
This feature requires a standard DMS-core equipped with NT9X10AA
processor circuit cards and NT9X26DA RTIF paddle boards.
An MC88000-compiled software load is also required.
Logs
Logs MM105 and MM106 are added by this feature.
The following logs are modified by this feature: CM100, CM119, CM122,
CM125, and MM110.
User interface
CI commands SYNC and TST are modified at the CM level of a MAP
terminal.
CI command CONFIG is modified at the MEMORY level of a MAP
terminal.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX941AA–15

NTX941AA
AL1197
Feature name
DMS-core Inventory Audit
Description
AL1197 implements an audit of the DMS-core hardware inventory tables to
ensure that hardware changes are detected, updated in the tables, and
reported to the operating company personnel.
BCS history
This feature was created in BCS28.
Logs
Two logs are introduced by this feature:
• CM156, generated when a card replacement is updated in the inventory
tables
• CM157, generated when an invalid or misplaced card is found in the CM
shelf or its extension shelf
User interface
A new command–CHECKINV–is added at the CM level of the MAP. It is
used to update the DMS-core hardware inventory tables when a card is
replaced.

NTX941AA–16 297-1001-801i Standard 09.01 January 2000

 NTX941AA
AL1200
Feature name
DMS-bus MMI Enhancements III
Description
AL1200 enhances the DMS-bus man-machine interface (MMI) software for
128-port cards and chain resources at the MAP. This feature includes
modifications to the CARD and CHAIN levels, adds the OFFL command at
the CARD level, and optimizes code for the MAP terminal.
BCS history
This feature was created in BCS31.
Restrictions and limitations
The enhancements to the CHAIN level of a MAP terminal and the
modification to the CHAIN level entry pertain only to offices that have
chain capability.
Changing the head card in the table MSCDINV to an incompatible product
equipment code (PEC) causes the change to ripple to all relevant cards in a
chain.
A PEC can be changed in the table MSCDINV to an incompatible PEC only
at the head card.
Feature interactions
This feature interacts with AL0797 (DMS-bus MMI Enhancements) and
AL0803 (DMS-bus MMI Enhancements II).
Datafill
The following table is modified for this feature:

Table Description

MSCDINV Table control is enhanced to address problems that occur when

PECs are changed during a datafill update of cards in a chain.

User interface
The CHAIN command at the SHELF level of the directory MSSHDIR is
enhanced to allow the user to specify a message switch. The NEXT
command at the INTERFACE CARD level of directory MSCDDIR is
modified to allow selective viewing of ports. The OFFL command is added
at the INTERFACE CARD level of directory MSCDDIR to perform the
action on both the front and back of the interface card selected.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX941AA–17

NTX941AA
AL1201
Feature name
DMS-bus Central S/W Enhancements for P-side Node Isolation
Description
AL1201 enhances P-side node isolation dectection. The nodes include
peripheral modules connected through the enhanced network, link peripheral
processors (LPP), and data packet network (DPN) modules.
BCS history
This feature was created in BCS29.
User interface
The BSY and BSYMS commands at the MS level of the MAP are modified
to support P-side node isolation detection. Response output includes a
message that node isolation has been detected; the busy-action is aborted
when isolation is detected; and a new parameter–FORCE–is added to permit
continuation of the busy action without checking for P-side isolation.

NTX941AA–18 297-1001-801i Standard 09.01 January 2000

 NTX941AA
AL1480
Feature name
Central DMS-bus MMI Information for Message Channels
Description
AL1480 applies the user interface commands TRNSL, BSY, RTS, and TST
to message channels.
BCS history
This feature was created in BCS33.
Restrictions and limitations
Peripheral-side (P-side) isolation checking from integrated link management
(ILM) is not supported. If resources are busied above the link level, P-side
nodes may be isolated unintentionally.
Feature interactions
This feature interacts with ILM and message switch (MS) user interface
software.
Datafill
Table Description

MSCDINV Field NUMLINKS is added to datafill the number of links being

added (1, 2, or 4) to the specified NT9X62BA card.

This feature increases program store by 10 Kbytes and increases data store
by 1 Kbyte.
User interface
Command TRNSL is modified at the SHELF level of a MAP terminal to
identify the P-side node connected to a specified message channel.
Commands BSY, RTS, and TST are modified at the CARD level of a MAP
terminal to display messages when ILM replies are received by the
command interpreter.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX941AA–19

NTX941AA
AL1570
Feature name
System Recovery Controller Interfaces
Description
AL1570 implements the following:
• system recovery controller (SRC) and its applications
• interface that groups like objects for bulk activities
• basic SRC finite state machines

BCS history
This feature was created in BCS33.
Feature interactions
This feature interacts with feature AL1416 (System Recovery Dependency
Manager).

NTX941AA–20 297-1001-801i Standard 09.01 January 2000

 NTX941AA
AL1681
Feature name
Integrated Event Management System Base Phase I
Description
AL1681 implements a multinode integrated event management (IEM)
interface and the presentation base required to support the translation of
integrated node maintenance (INM) events into log reports. The IEM
interface serves as the central management system in which all events are
collected, stored, analyzed, and translated into various report types.
BCS history
This feature was created in BCS33.
Restrictions and limitations
Only INM events are recognized by the IEM interface and presentation base.
Logs
Logs PM500 and PM700 are added. Log PM500 is generated to indicate the
change in state of a series III peripheral. Log PM700 is generated during the
loading of a series III peripheral.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX941AA–21

NTX941AA
AL1753
Feature name
NT9X12AC Software Support
Description
AL1753 supports the new NT9X12AC card. The NT9X12AC increases the
system’s ability to detect and isolate hardware that is corrupting messages.
BCS history
This feature was created in BCS32.
Interactions
When the NT9X12AB/AC is powered up or the card software is reset, the
control register is placed in 12AB mode (12AB mode indicates no read/write
access to the new 12AC registers; 12AC mode indicates read/write access to
new registers).
Logs
Log CMSM103 is generated to provide a summary report on the message
controller (MC) memory parity error in the buffers of the NT9X12AC card.
Log CMSM104 is generated to provide a summary report on the P-side
message controller (PMC) memory parity error in the buffers of the
NT9X12AC card.
User interface
The MAP is updated to indicate the following transient parity hits:
• The corresponding MC and PORT at the MC and PORT level are
marked as in-service trouble.
• A minor alarm is raised after the software is switched to use the other
FIFO/BUFFER memory bank.

NTX941AA–22 297-1001-801i Standard 09.01 January 2000

 NTX941AA
AL1759
Feature name
Maintenance Action Pre-Check
Description
AL1759 provides the command interface (CI) command MTCCHK to allow
operating company personnel to perform a maintenance action precheck
before performing manual maintenance. Command MTCCHK verifies that
the system is not configured to allow an unnecessary degradation, restart, or
reboot during a subsystem power-down or pack replacement. System
responses to command MTCCHK describe the state changes required if the
system is not in the proper state.
BCS history
This feature was created in BCS32.
Hardware requirements
This feature functions on all DMS-100 SuperNode front-end systems,
including SuperNode series 10, SuperNode series 20, and SuperNode
series 30.
Restrictions and limitations
This feature supports maintenance action prechecks on the computing
module (CM) subsystem, message switch (MS) subsystem, and system load
module (SLM) subsystems only.
When the system is configured improperly, this feature identifies the actions
required, but does not automatically perform them.
If the software cannot query the power status of a given subsystem,
operating company personnel are queried to verify power-down before
command MTCCHK can execute successfully.
Command MTCCHK is not intended for use during installation of new
hardware.
Feature interactions
This feature interacts with the CM maintenance subsystem, the MS central
maintenance subsystem, and the SLM maintenance subsystem.
Datafill
This feature increases permanent data store by 8 Kbytes.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX941AA–23

NTX941AA
AL1759
Logs
Logs MTCK100 and MTCK101 are added. Log MTCK100 is generated
when the system is configured properly for manual maintenance on the
identified subsystem or slot. Log MTCK101 is generated when the system
is configured improperly for manual maintenance on the identified
subsystem or slot.
User interface
Command MTCCHK is added in directory PROGDIR to initiate a
maintenance action precheck.
Command MTCCHK is added to the following MAP menus at the MAP CI
MTC levels: CM, CM; CMMNT, CM; MEMORY, IOD; SLM and MS.

NTX941AA–24 297-1001-801i Standard 09.01 January 2000

 NTX941AA
AL1782
Feature name
NT9X62BA 0D1 Support
Description
AL1782 provides local DMS-bus software support for subrate DS512
(SR512) message links. The major functions of this feature are to support
the production release of the NT9X62BA paddle board, to provide register
access to the card, and to provide card level diagnostics.
BCS history
This feature was created in BCS33.
Hardware requirements
This feature requires the NT9X62BA paddle board and one of the following
port cards: NT9X17AC, NT9X17BB, or NT9X17DA.
Restrictions and limitations
Commands SR512PRD and SR512BIST cause a loss of data if they are used
on links that are in service.
Datafill
This feature increases program store by 1 Kbyte.
User interface
Command SR512PRD is added at the MSLDEBUG level of a MAP terminal
to initialize the pseudo-random data and checker functions of the DS512
transmit/receive controller (DTRC) chips that reside on the four-link SR512
paddle board.
Command SR512BIST is added at the MSLDEBUG level of a MAP
terminal to initialize the built-in self-test function of DTRC chips that reside
on the four-link SR512 paddle board.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX941AA–25

NTX941AA
AL1826
Feature name
DMS-Bus MMI Enhancements for ISN
Description
AL1826 provides the following DMS-bus enhancements:
• DMS-bus support for the integrated link maintenance (ILM) default card
list facility
• isolation detection on busy operations when the resource contains ILM
resources
• restructured DMS-bus user interface software modules to allow future
DMS-bus enhancements to be implemented with greater efficiency
In addition, the command CHAIN is enhanced to support chains with
multiple fiber links, and the command TRNSL is enhanced to identify the
peripheral-side (P-side) node that is connected to a specified link.
BCS history
This feature was created in BCS33.
Restrictions and limitations
This feature does not support input/output user interface (IOUI) and ILM
links on the same card, or channelized and nonchannelized links on the same
card.
Feature interactions
This feature interacts with ILM on the DMS-bus.
Datafill
This feature increases program store by 10 Kbytes.
User interface
Command TRNSL is modified at the SHELF level of a MAP terminal to
identify the P-side node that is connected to a specified link. ILM or IOUI
resource status associated with the P-side node is also provided.
Command CHAIN is modified at the SHELF level of a MAP terminal to
show the status for multiple links attached to the head card of a chain. The
card type is identified and the status of up to four links can be displayed.
Commands TST, BSY, and RTS are modified at the CHAIN level of a MAP
terminal. The LINK parameter is changed to accept the link number as a
parameter. Responses are also added to support ILM links when these
commands are executed with the LINK parameter.

NTX941AA–26 297-1001-801i Standard 09.01 January 2000

 NTX941AA
AL1884
Feature name
DMS-Bus Message Flow Control—II
Description
AL1884 provides firmware enhancements for the four-port interface card
that support flow control on a babbling port and provide the N04 silicon
recycle of the single-port bus access controller (BAC). This feature also
provides local message switch (MS) maintenance software support for the
firmware enhancements.
BCS history
This feature was created in BCS33.
Hardware requirements
This feature requires the new card maintenance unit (CMU) firmware and
the new N04 hardware.
Restrictions and limitations
The CMU firmware and the N04 hardware must be available for testing the
firmware before the software can be integrated.
This feature applies only to four-port interface cards that have single-port
BACs.
Datafill
This feature increases program store by 1 Kbyte and increases data store by
a maximum of 1 Kbyte.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX941AA–27

NTX941AA
AL1968
Feature name
DMS-bus Backwards Compatibility Support
Description
AL1968 enhances the DMS-bus software to provide backward compatible
software development. The enhancements include the following:
• BCS version tracking mechanism
• framework for backward compatible software development
• maintenance database expansion

BCS history
This feature was created in BCS33.
Restrictions and limitations
This feature may cause fewer events to be recorded in the DMS footprint.
Consequently, less footprint data may be sent to the appropriate log after a
restart.
Feature interactions
This feature interacts with the local message switch (LMS) or link interface
module (LIM) and message switch (MS) software.
Datafill
This feature increases program store by 3 Kbytes and increases data store by
6 Kbytes.
Logs
This feature modifies the following logs:
MS100 MS101 MS102 MS103 MS104
MS208 MS238 MS248 MS260 MS261
MS262 MS263 MS264 MS265 MS266
MS267 MS277 MS300 MS301 MS302
MS303 MS304 MS305 MS306 MS307
MS310 MS311 MS312 MS313 MS314
MS315 MS316 MS317 MS318 MS400
MS401 MS402 MS403 MS404 MS405
MS406 MS407 MS408 MS410 MS411
MS412 MS413 MS414 MS415

NTX941AA–28 297-1001-801i Standard 09.01 January 2000

 NTX941AA
AL2021
Feature name
Distributed Log System
Description
AL2021 allows operating company personnel to browse through local logs
from the central node (using the LOGUTIL command set) without having to
use the command REMLOGIN. This feature reduces the number of times a
log is formatted and sent between a local and central node.
BCS history
This feature was created in BCS33.
Restrictions and limitations
The user can specify only one node at a time as the context for a query,
except when using the command DUMPLOGS, which has an option for
specifying ALLNODES.
If a long delay occurs between the sending of a log to the central node and
the receiving of a log notification at another device, that log may have to be
retrieved again from the local node; the first copy is kept only until the first
device has finished its outputs.
User interface
Command CONTEXT is added to allow the user to change the context of
applicable nodes during a LOGUTIL session.
Command LISTNODES is added to list all available nodes in the switch.
This command can also be used to identify a node.
Command DUMPLOGS is added to display all logs stored in the specified
log buffer in chronological order of generation at the local node.
Command OPEN is modified to allow the user to specify the log number of
the log to be displayed.
Commands BACK and FORWARD are modified to allow the user to specify
the number of log reports to be displayed, either preceding or following the
current log.
All the new commands are available on the central node only.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX941AA–29

NTX941AA
AL2030
Feature name
System REX Test Controller
Description
AL2030 provides a routine exercise (REX) controller for SONET DMS
(S/DMS) tandem switches. This feature allows scheduling of existing REX
tests on all nodes in a minimal time.
BCS history
This feature was created in BCS33.
Restrictions and limitations
Operating company personnel cannot turn off the REX test on critical nodes
(DMS-core computing module, DMS-bus message switch). REX tests can
be suspended for a single maintenance window.
It is possible that all nodes may not be tested in a single night due to time
restraints. Untested nodes receive testing priority in the next maintenance
window.
Feature interactions
This feature interacts with existing REX tests.
Datafill
Table Description

REXSCHED Table is added to datafill REX test schedules.

This feature increases program store by 20 Kbytes and increases data store
by a maximum of 6 Kbytes.
Logs
Log IOAU112 is modified to generate a message if a node has not been
REX tested within a 7-day time period.
User interface
Command REXTEST is added to the PROGDIR level of a MAP terminal, to
suspend, resume, display status, or query REX tests.

NTX941AA–30 297-1001-801i Standard 09.01 January 2000

 NTX941AA
AL2331
Feature name
E2A Monitoring Software
Description
AL2331 provides maintenance software to monitor the status of E2A links
on the computing module (CM). E2A link status is captured by 9X26 reset
terminal interface (RTIF) cards and monitored by alarms and logs. The E2A
link can also be enabled and disabled using a MAP CI command.
BCS history
This feature was created in BCS33.
Restrictions and limitations
E2A link status on the inactive CPU is monitored by an audit only when the
system is operating in sync. If the system is operating out of sync, MAP CI
command E2ALINK must be invoked to monitor the inactive CPU.
Datafill
Office parameter E2ALINKEQP is added in table OFCENG to specify
whether E2A link monitoring software is enabled (Y) or disabled (N).
This feature increases program store by 1 Kbyte.
Logs
Log CM163, a CM E2A link fault report, is added. It is generated when a
CM with E2A telemetry equipment has its E2A links disconnected or
disabled.
User interface
Alarm E2A Flt is added at the CM level of a MAP terminal to indicate that
one or both E2A links to the RTIFs of the CPUs are disconnected or
disabled.
CPU fault indicator E2A is added at the CM level of a MAP terminal to
indicate that the CPU has its E2A link disconnected or disabled.
CI command E2ALINK is added at the CM level of a MAP to enable,
disable, or check the E2A link status of the CPU planes.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX941AA–31

NTX941AA
AQ0721
Feature name
Hardware Baseline Monitor
Description
AQ0721 provides an automatic mechanism (without manual intervention) to
determine the compatibility of a BCS release with hardware cards already
resident in a switch. One hardware monitor for each SuperNode subsystem
is run as part of the system routine exercise (REX) tests.
BCS history
This feature was created in BCS33.
Restrictions and limitations
Only message switch (MS) and computing module (CM) hardware monitors
are implemented in this feature.
Datafill
Table Description

PECINV Table added

Table PECINV is added to accommodate the baseline datafill of SuperNode

product engineering codes (PEC).
Logs
Logs MS105 and CM106 are added. Log MS105 is generated when an MS
card fails a release compatibility check. Log CM160 is generated when a
CM card fails a release compatibility check. These logs are generated only
during REX tests.
User interface
Command CHECKREL is added to directory PROGDIR to determine
whether the release issue of a SuperNode card is compatible with software
running in the switch.
Output for commands QUERYCM and QUERYMS is modified by this
feature.

NTX941AA–32 297-1001-801i Standard 09.01 January 2000

 NTX941AA
AQ0741
Feature name
SuperNode Clock Robustness Restructure—I
Description
AQ0741 restructures the software on the DMS-bus that is responsible for
maintaining the DMS clock card. This restructuring was done to make the
DMS clock more reliable and to facilitate its continued evolution. No
changes are made to the functionality of the software. This feature is part of
a robustness program in DMS SuperNode.
BCS history
This feature was created in BCS34.
Datafill
This feature increases data store on the message switch by a maximum of 2
Kbytes and increases program store by a maximum of 10 Kbytes.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX941AA–33

NTX941AA
AQ0834
Feature name
16-MB Processor on DMS-bus
Description
AQ0834 enhances the central and local DMS-bus maintenance software to
support the maintenance of the NT9X13DD (16-MB processor card) with an
optional NT9X14DB (memory card) on the standard DMS-bus. The
maintenance software of the link interface module (LIM) is also enhanced to
support the NT9X13DD on the local message switch (LMS).
BCS history
This feature was created in BCS35.
Restrictions and limitations
The NT9X13DD processor card is supported in the standard DMS-bus and
the LMS of a link peripheral processor (LPP) only.

NTX941AA–34 297-1001-801i Standard 09.01 January 2000

 NTX941AA
AQ0854
Feature name
MS Backward Compatibility—II
Description
AQ0854 enhances DMS-bus software to support backward compatibility in
the message switch (MS) software load. This feature follows up feature
AL1968 (DMS-Bus Backwards Compatibility Support).
AQ0854 provides the following advantages:
• simplification of BCS application procedures
• independent loading of the MS software prior to the loading of the
computing module (CM) software.
• a new MS software load can be ‘‘soaked’’ in one MS plane while the
other MS plane remains in service with its existing MS software load
• permits but does not ensure that both MSs are in service before and after
the restart switch of activity (SWACT)
• permits the simplification of peripheral-side (P-side) node SWACT
software
BCS history
This feature was created in BCS34.
Restrictions and limitations
Both the CM and the MS must have a software load of BCS34 or later for
this feature to take effect. Although the switch will operate with a BCS34
load in the CM and a BCS35 load in the MS, the switch functionality
(feature support) is that of BCS34.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX941AA–35

NTX941AA
AQ0859
Feature name
DMS-bus SW Support for Multiport Interface Cards
Description
AQ0859 introduces the NT9X17CA (128-port card) to the series of
multiport cards, which includes the NT9X17BB (32-port card) and the
NT9X17DA (64-port card). Chains consisting of a mixture of 32-port,
64-port, and 128-port cards are supported.
BCS history
This feature was created in BCS35.
Datafill
Table Description

MSCDINV Field BODYPEC is added to datafill groups of front and back

product engineering codes (PEC) that form the body of the
multiport chain.

This feature increases data store by a maximum of 500 kbytes and increases
program store by a maximum of 2 kbytes.

NTX941AA–36 297-1001-801i Standard 09.01 January 2000

 NTX941AA
AR0211
Feature name
CM Alarm Suppression During REX Test
Description
AR0211 modifies the computing module (CM) maintenance routine exercise
(REX) test to suppress CM maintenance alarms that are generated as a result
of normal operation of the test. This feature also suppresses the alarm type
field of CM maintenance logs generated by the test. Any alarms or logs that
are not generated by the test are not affected.
BCS history
This feature was created in BCS35.
Datafill
This feature increases data store by a maximum of 1 kbyte, and increases
program store by a maximum of 1 kbyte.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX941AA–37

 NTX942AA
SuperNode System Load Module
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTX942AA
Feature number Description

AL0840 SLM Diagnostic Enhancements

AG0874 SLM File System Phase 2
AG0367 SLU Basic File System – CI Utilities
AG0373 SLU Basic File System – Device Management
AG0369 SLU Basic File System – File Management
AG0372 SLU Basic File System – General Utilities
AL1298 SLM FS Enhancement – Phase 2
AL1166 SLM Maintenance Enhancements
AL1060 SLM Phase II – Disk Tape Replacements
AL0731 SLM Control Software Phase 2
AL0437 SLU Input/Output System
AL0436 System Load Module Control Software
AG1385 Prescheduled Image-Taking on SLM

BCS history
This feature package was created in BCS24.
Required feature packages
Feature package Description
number

NTX001AA Common Basic

NTX940AA CM Bilge

Feature Description Manual Volume 2 of 3 BCS44.1i NTX942AA–1

NTX942AA
AG1385
Feature name
Prescheduled Image-Taking on SLM
Description
AG1385 enables computing module (CM) and message switch (MS) image
dumps to be prescheduled and transported to the system load module (SLM)
without user intervention.
BCS history
This feature was created in BCS28.
Restrictions and limitations
Only four image volumes can be defined.
IOC disk volume datafill is not allowed.
Magnetic tape and SLM tape datafill is not allowed.
Major changes (such as a BCS upgrade) may require that the image disks be
manually cleaned.
Only one image per day can be taken.
Feature interactions
Journal file activities are controlled by the auto-image dump process.
Datafill
The following table was modified for this feature:

Table Description

IMAGEDEV Table size is changed to a maximum of four tuples to

accommodate feature; protected data store increased by nine
words.

NTX942AA–2 297-1001-801i Standard 09.01 January 2000

 NTX942AA
AL1060
Feature name
SLM Phase II – Disk/Tape Replacements
Description
AL1060 modifies system load module (SLM) hardware to accommodate the
use of higher capacity tape cartridges and disk drives.
BCS history
This feature was created in BCS29.
Restrictions and limitations
SLM I cannot read or write to tapes recorded by SLM II.
SLM II can read but not write to tapes recorded by SLM I.
SLM I can read and write only DC600A tape cartridges.
SLM II can read and write both DC600A and DC600XTD tape cartridges.
Logs
Existing logs SLM200 to SLM207 are modified to operate with the new
hardware.
New log SLM208 is generated when the software fails to obtain the correct
SLM product engineering code (PEC).
User interface
SLM II tape drives are equipped with a LED on the front panel to indicate
that the drive is in use and should not be removed.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX942AA–3

NTX942AA
AL1166
Feature name
SLM Maintenance Enhancements
Description
AL1166 modifies P-side message controller (PMC) and system load module
(SLM) maintenance software to support the high performance fault tolerance
file system (FTFS).
BCS history
This feature was created in BCS29.
User interface
If a PMC or one of its ports is busied before the corresponding SLM, a
message is output advising the operating company personnel.

NTX942AA–4 297-1001-801i Standard 09.01 January 2000

 NTX942AA
AL1298
Feature name
SLM File System Enhancement
Description
AL1298 provides further modifications to the special operations layer of the
system load module (SLM) file system.
BCS history
This feature was created in BCS29.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX942AA–5

 NTX942AB
DMS – SuperNode System Load Module
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTX942AB contents
Feature number Description

AG0367 SLU Basic File System—CI Utilities

AG0369 SLU Basic File System—File Management
AG0372 SLU Basic File System—General Utilities
AG0373 SLU Basic File System—Device Management
AG0874 SLM File System Phase 2
AG1385 Prescheduled Image Taking on SLM
AL0436 System Load Module Control Software
AL0437 SLU Input Output System
AL0731 SLM Control Software, Phase 2
AL0840 SLM Diagnostic Enhancements
AL1060 SLM Phase II—Disk/Tape Replacements
AL1166 SLM Maintenance Enhancements
AL1298 SLM FS Enhancement—Phase 2
AL1774 SNSE SLM1A Maintenance Software Support
AL1790 File System Modifications for SLM1A

BCS history
This feature package was created in BCS24.
Required feature packages
Required feature packages
Feature package Description
number

NTX001AA Common Basic

NTX940AA CM Bilge

NTX941AA CM Common
NTX950AA MS Bilge

Feature Description Manual Volume 2 of 3 BCS44.1i NTX942AB–1

NTX942AB
AL1790
Feature name
File System Modifications for SLM1A
Description
AL1790 identifies and implements software changes required to support the
system load module (SLM) 1A, and tests all layers of file system software
associated with the SLM1A, in support of the SuperNode Compact (SN-C)
switch.
BCS history
This feature was created in BCS34.
Restrictions and limitations
The following restrictions apply to SLM I and SLM II tape cartridges:
• SLM I cannot read or write to tapes recorded by SLM II
• SLM II cannot read or write to tapes recorded by SLM I
• SLM I can read and write to DC600A tape cartridges only
• SLM II can read and write to both DC600A and DC600XTD tape
cartridges
Feature interactions
This feature requires features AL1727 (DMS Compact CM Maintenance
Software Support) and AL1774 (SLM1A Maintenance for SuperNode
Compact).

NTX942AB–2 297-1001-801i Standard 09.01 January 2000

 NTX944AA
Base Node Maintenance
This feature package provides software support to the integrated node
maintenance (INM) application.
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTX944AA contents
Feature number Description

AL1378 Audit/REX Driver for INM Nodes

AL1195 Central RP Control II
AR0081 INM Fault Reporting
AL2271 INM Support for BCS Application/CC Warm SwAct
AL2121 INM Support for IEM Event Generation and OM
AL2120 INM System Agent
AR0079 INM Warm-spared Support II
AL1117 Local RP Control II

BCS history
This feature package was created in BCS33.
BCS34—AR0079 and AR0081 added
Required feature packages
Required feature packages
Feature package Description
number

NTXF71AA SuperNode Enhanced Messaging

Feature Description Manual Volume 2 of 3 BCS44.1i NTX944AA–1

NTX944AA
AR0079
Feature name
INM Warm-spared Support II
Description
AR0079 is a continuation of feature AL1123 (INM Support for
Warm-Spared Nodes) to be used by the integrated node maintenance (INM)
in supporting two types of duplex node architectures: warm-spared node
architecture and INM load-shared node architecture.
AR0079 provides support for the following functions:
• central-agent multitasking
• warm-spared restart recovery
• communication between the mate manager and the unit central agent
• use of operational measurements (OM) and event generation interface to
count switches of activity (SwAct) between units
• routine exercise (REX) testing for warm-spared nodes
• completion of computing module BCS application work started in
feature AL2271 (INM Support for BCS Application/CC Warm SwAct)
BCS history
This feature was created in BCS34.
Feature interactions
This feature requires the following features:
• AL1117—Local RP Control II
• AL1123—INM Support for Warm-spared Nodes
• AL1195—Central RP Control II

This feature also interacts with the following features:

• AL1111—High Level Design for Integrated Node Maintenance
• AL2121—INM Support for IEM Event Generation and OM
• AQ0739—DMS-Bus BCS SwAct Reduced Restart
• AQ0854—MS Backwards Compatibility—II

Datafill
This feature increases data store by a maximum of 15 Kbytes and increases
program store by a maximum of 3 Kbytes.

NTX944AA–2 297-1001-801i Standard 09.01 January 2000

 NTX944AA
AR0081
Feature name
INM Fault Reporting
Description
AR0081 provides integrated node maintenance (INM) fault reporting
capability by generating cardlist information. This feature also enhances
handling of node isolation through improved resolution on the node’s state
and trait conditions during maintenance activities.
BCS history
This feature was created in BCS34.
Feature interactions
This feature interacts with the following features:
• AL1111—High Level Design for Integrated Node Maintenance
• AL1117—Local RP Control II
• AL1195—Central RP Control II

Datafill
This feature increases data store by a maximum of 1 Kbyte and increases
program store by a maximum of 2 Kbytes.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX944AA–3

 NTX945AA
MS Base Link Maintenance
This feature package provides management between the DMS-bus software
and the frame transport system (FTS), integrated link maintenance (ILM),
distributed data manager (DDM), and enhanced network (ENET) software.
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTX945AA contents
Feature number Description

AL1477 Central DMS-Bus and ILM Interactions on Message

Channels
AL1482 Central DMS-Bus Data Recovery on System Restarts
AL1781 Central DMS-Bus MMI Information for Physical Links
AL1780 Central DMS-Bus/ILM Interactions on PLM
AC0644 Central MS–ILM Interactions on Physical Links
AL1476 DMS-Bus Data and Message Format for ILM Links
AQ0718 DMS-Bus Support for MS–ILM Data Transfer and Audits
AQ0717 DMS-Bus Support for PLM Primitive Enhancements
AL1478 Local DMS-Bus Node, Link and Port Initialization
AL1779 Local DMS-Bus Support for MCM/PLM Primitives
AL1479 Local DMS-Bus Support for SR-512 Message Channels
AQ0854 MS Backwards Compatibility—II
AQ0840 S/DMS MMI Consistency and Enhancements
AL1457 Basic Initialization and Communication of ILM date

BCS history
This feature package was created in BCS33.
Required feature packages
Required feature packages
Feature package Description
number

NTXF71AB SuperNode Enhanced Messaging

Feature Description Manual Volume 2 of 3 BCS44.1i NTX945AA–1

NTX945AA
AC0639
Feature name
MMI for Inter-MS Links
Description
This feature provides DMS-bus software support for inter-MS links on a
SuperNode switch. The inter-MS links are used by the frame transport bus
(F-bus) messaging system to direct messages across message switches (MS)
at the DMS-bus level, securing alternate paths for messaging.
This feature includes support for
• man-machine interface (MMI) enhancements for inter-MS links
• MS F-bus interaction during restarts
• peripheral-side (P-side) maintenance notification of the loss or gain of
inter-MS links on the DMS-bus
BCS history
This feature was created in BCS33.
Hardware requirements
This feature requires one port for each MS, on each inter-MS link.
Restrictions and limitations
Inter-MS links must be datafilled on separate interface cards.
Logs
This feature adds eight logs to report inter-MS link port state changes and
faults detected by maintenance audits. The new logs are
• MS320 Reports inter-MS port state transition from system or
manual busy to in service.
• MS321 Reports inter-MS port state transition from in service to
manual busy.
• MS322 Reports inter-MS port state transition from system,
remote-side (R-side) or P-side busy to manual busy.
• MS323 Reports inter-MS port state transition from in service to
system busy.
• MS324 Reports inter-MS port state transition from R-side or C-side
busy to system busy.
• MS325 Reports inter-MS port state transition from system busy to
C-side busy.
• MS326 Reports inter-MS port state transition from system busy to
R-side busy.
• MS327 Reports detection of a fault on an in-service inter-MS port.

NTX945AA–2 297-1001-801i Standard 09.01 January 2000

 NTX945AA
AC0639
User interface
This feature modifies the maintenance and administration position command
interpreter (MAPCI) MS level to display the status of ports on the inter-MS
links. The feature introduces the concept of R-side for inter-MS link ports.
The inter-MS link port status of R (R-side busy) is equivalent to P-side busy
for other ports.
The commands for busying a card or a port on which an inter-MS link
resides are enhanced to prevent the loss of the inter-MS link resource.
This feature introduces the MAPCI MS level command INTERMS. This
command accesses the card level for the card on which a specified inter-MS
link resides.
Two additional MS alarms are introduced by this feature: NoIMSL major
(no inter-MS links in service) and 01IMSL minor (one inter-MS link out of
service).

Feature Description Manual Volume 2 of 3 BCS44.1i NTX945AA–3

NTX945AA
AC0644
Feature name
Central MS–ILM Interactions on Physical Links
Description
AC0644 provides the central DMS-bus maintenance software to support the
commands BUSY and RETURN TO SERVICE (RTS) for a channelized
fiber link equipped on a subrate DS512 card in a DMS-bus message switch
(MS) shelf.
BCS history
This feature was created in BCS33.
Hardware requirements
This feature requires the subrate DS512 card (version NT9X62BA).
Restrictions and limitations
This feature does not support fiber link recovery over system restarts or MS
node busy and RTS. Links supported under integrated link maintenance
(ILM) must be recovered by the commands MANUAL BUSY and RTS after
these actions.
Datafill
This feature increases data store by a maximum of 2 Kbytes and increases
program store by a maximum of 100 Kbytes.

NTX945AA–4 297-1001-801i Standard 09.01 January 2000

 NTX945AA
AG1337
Feature name
DMS-bus (Central) Support for Inter-MS Link (SR512)
Description
This feature provides the following enhancements to DMS-bus software:
• support for datafill and maintenance of subrate 128 (SR128) and
subrate 256 (SR256) DS512 inter-message switch (inter-MS) links
• improvements to existing inter-MS link maintenance to prevent message
loss on controlled link closure
• indication of failure to open the frame transport system (FTS) messaging
route on return to service (RTS) and in-service testing of an inter-MS
link
• provision of the basic requirements for implementation of automatic
rerouting of I/O utility interface (IOUI) messages through inter-MS links
when link outages prevent tandem messaging through a single MS
BCS history
This feature was created in BCS35.
Restrictions and limitations
This feature does not implement automatic initiation of corrective action to
clear the fault even if a fault is set on failure to open the FTS routing for an
inter-MS link.
Datafill
Table Description

MSILINV The protocol field is extended to include SR128 and SR256.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX945AA–5

NTX945AA
AL1456
Feature name
Design and Data Definition for DS30/IOUI Inter-MS Links
Description
This feature provides DMS-bus support for inter-MS links on a SuperNode
switch. The inter-MS links are used by the frame transport system (FTS)
messaging system to direct messages across message switches (MS) at the
DMS-bus level, thus securing alternate paths for messaging.
Support provided by this feature includes software maintenance of the ports
on the inter-MS links.
BCS history
This feature was created in BCS33.
Hardware requirements
This feature requires one port for each MS, for each inter-MS link.
Restrictions and limitations
Inter-MS links must be datafilled on separate interface cards. Each MS pair
can have a maximum of two inter-MS links.
The inter-MS link cards must be previously datafilled in table MSCDINV.
The inter-MS ports on both MSs must be unequipped.
Feature interactions
This feature requires feature AI0127 (FTS Routing Control).
Datafill
Table Description

MSILINV This table (MS Inter-MS Link Inventory) is used to define

inter-MS link positions (shelf, card, and port) in the DMS-bus.

Logs
This feature adds eight new logs to report inter-MS link port state changes
and faults detected by maintenance audits. The new logs are
• MS290 Reports inter-MS port state transition from system or
manual busy to in service.
• MS291 Reports inter-MS port state transition from in service to
manual busy.

NTX945AA–6 297-1001-801i Standard 09.01 January 2000

 NTX945AA
AL1456
• MS292 Reports inter-MS port state transition from system,
remote-side (R-side), or peripheral-side (P-side) busy to
manual busy.
• MS293 Reports inter-MS port state transition from in service to
system busy.
• MS294 Reports inter-MS port state transition from R-side or
control-side (C-side) busy to system busy.
• MS295 Reports inter-MS port state transition from system busy to
C-side busy.
• MS296 Reports inter-MS port state transition from system busy to
R-side busy.
• MS297 Reports the detection of a fault on an in-service inter-MS
port.
An MS104 log is generated when inter-MS link FTS routing is lost or gained
through inter-MS port state transitions, or a change in the MS node is used
for FTS routing.
User interface
This feature modifies the maintenance and administration position command
interpreter (MAPCI) MS level to display the state of ports on the inter-MS
links. The feature includes the concept of R-side (remote side) for inter-MS
link ports. The inter-MS link port state of R (R-side busy) is equivalent to
P-side busy for other ports.
The commands for busying a card or a port on which an inter-MS link
resides are enhanced to prevent the loss of the inter-MS link resource.
This feature introduces the MAPCI MS level commands INTERMS and
SWROUTE. The command INTERMS accesses the card level for the card
on which a specified inter-MS link resides. The command SWROUTE
changes the FTS active route from one MS to the other, or queries the
current FTS routes.
Two additional MS alarms are introduced by this feature: NoIMSL major
(no inter-MS links in service) and 01IMSL minor (one inter-MS link out of
service).

Feature Description Manual Volume 2 of 3 BCS44.1i NTX945AA–7

NTX945AA
AL1457
Feature name
Basic Initialization and Communication of ILM Data
Description
This feature supports the initialization of the rate adapter (RA) card, the
frame bus (F-bus), and F-bus links and taps in the DMS-bus. This
initialization is provided within the framework of integrated link
maintenance (ILM).
This feature provides the capability to connect link interface units (LIU) to
the DMS-bus. Thus, a DMS SuperNode with Common Channel Signaling 7
(CCS7) capabilities can be provisioned in two cabinets, resulting in reduced
cost and space requirements.
BCS history
This feature was created in BCS33.

NTX945AA–8 297-1001-801i Standard 09.01 January 2000

 NTX945AA
AL1476
Feature name
DMS-Bus Data and Message Format for ILM Links
Description
AL1476 provides DMS-bus data and message format support for links under
the ILM from the peripheral-side (P-side) node table control. Datafill for the
following links is supported: non-channelized links, channelized links on
subrate DS512 cards, and multiple messaging channels in a channelized
fiber link. This feature also allows physical links or ports and message
hardware or channels to be added and deleted.
BCS history
This feature was created in BCS33.
Hardware requirements
This feature requires the subrate DS512 card (version NT9X62BA).
Restrictions and limitations
This feature supports one fibre link for each DS512 card. The maximum
number of message channels on a link is 511.
Datafill
Table Description

MSCDINV NT9X62BA is added to the range of values for field PECODE.

This feature increases program store by 50 Kbytes and increases data store
by 8 Kbytes.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX945AA–9

NTX945AA
AL1477
Feature name
Central DMS-Bus and ILM Interactions on Message Channels
Description
AL1477 allows the DMS-bus software to communicate with integrated link
maintenance (ILM) to control messaging on message channels. This feature
provides the commands MANUAL BUSY and RETURN TO SERVICE
(RTS) for message channels in subrate DS512 card channelized fibre links.
BCS history
This feature was created in BCS33.
Hardware requirements
This feature requires the subrate DS512 (version NT9X62BA) card.
Restrictions and limitations
The functions provided by this feature apply only to hardware testing.
Interactions with message switch (MS) mode, chain, link, and system
restarts are not available.
The message channel must be recovered by the commands MANUAL
BUSY and RTS after a system restart or a busy/RTS of a node and chain.
Datafill
This feature increases data store by 2 Kbytes and increases program store by
a minimum of 100 Kbytes.

NTX945AA–10 297-1001-801i Standard 09.01 January 2000

 NTX945AA
AL1478
Feature name
Local DMS-bus Node, Link, and Port Initialization
Description
AL1478 provides management between the DMS-bus software and FTS,
ILM, DDM, and ENET software. This feature performs the following
activities:
• analyzes the initialization order and software layering of optional and
non-optional DMS-bus software and hardware
• implements system interactions between DDM, ILM, FTS, and ENET
during DMS-core restarts
• implements message queues to inform user subsystems of the states of
links and ports
BCS history
This feature was created in BCS33.
Datafill
This feature increases static data store by 200 words for each physical link
and message channel datafilled.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX945AA–11

NTX945AA
AL1479
Feature name
Local DMS-bus Support for SR-512 Message Channels
Description
This feature provides support for manually busying and returning to service
subrate DS512 (SR512) channels under integrated link maintenance (ILM).
BCS history
This feature was created in BCS33.
Hardware requirements
This feature requires cards NT9X17DA (message switch 64-port card) and
NT9X62BA (four-port subrate DS512 paddle board).

NTX945AA–12 297-1001-801i Standard 09.01 January 2000

 NTX945AA
AL1482
Feature name
Central DMS-Bus Data Recovery on System Restarts
Description
AL1482 provides central DMS-bus data support over restarts. This feature
provides the following capabilities:
• preservation of the physical links (PLK) and message channels (MCH)
maintained by ILM during warm and cold restarts
• recovery of the message switch (MS) from a computing module
(CM)–MS data synchronization failure during a restart or manual return
to service (RTS)
• integration of the initialization of the ILM PLKs and MCHs into the
restart and manual RTS sequence
BCS history
This feature was created in BCS33.
Hardware requirements
This feature requires the subrate DS512 card (version NT9X62BA) on the
MS.
Datafill
This feature increases program store by 10 Kbytes.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX945AA–13

NTX945AA
AL1779
Feature name
Local DMS-Bus Support for MCM/PLM Primitives
Description
AL1779 provides DMS-bus support for ILM local hardware primitives. This
feature allows maintenance of the SONET DMS (S/DMS) nodes by
providing
• busy and return-to-service (RTS) functionality for physical link
maintenance (PLM)
• in-service (INS) tests, out-of-service (OOS) tests, and local audits for
message channel maintenance (MCM)
BCS history
This feature was created in BCS33.
Restrictions and limitations
This feature supports only enable and disable physical link hardware
primitives.
Feature interactions
This feature interacts with ILM on the DMS-bus and with the local
DMS-bus interface card maintenance software.
Datafill
This feature decreases program store by 20 Kbytes and decreases data store
by 10 Kwords.

NTX945AA–14 297-1001-801i Standard 09.01 January 2000

 NTX945AA
AL1780
Feature name
Central DMS-Bus/ILM Interactions on PLM
Description
AL1780 allows DMS-bus ILM message channels to indicate when they are
out of service (OOS) as a result of the associated DMS-bus physical link
being OOS. This feature also updates central DMS-bus maintenance
software to support testing of DMS-bus ILM message channels and physical
links.
BCS history
This feature was created in BCS33.
Restrictions and limitations
The link-busy status is not supported for ports on the input/output user
interface (IOUI)-based enhanced network messaging links.
Feature interactions
This feature adds the link-busy status to DMS-bus message channels.
Logs
A new log, MS318, is generated when a port on a channelized link goes
from manual busy to link busy.
This feature modifies logs MS312 and MS317.
Log MS312 is generated each time a port on a channelized link goes from
OOS state to manual busy.
Log MS317 is generated each time the status of a port on a channelized link
changes state or requires maintenance attention.
User interface
Command NEXT is modified at the MSCDDIR level of a MAP terminal to
display the LBSY port state option. If LBSY is specified for the STATE
parameter, the NEXT command displays the next group of 16 ports that have
at least one L-BSY port.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX945AA–15

NTX945AA
AL1781
Feature name
Central DMS-Bus MMI Information for Physical Links
Description
AL1781 provides user interface software support for the maintenance of
DMS-bus physical links by means of ILM. The maintenance includes fault
reporting, diagnostics, and log generation.
BCS history
This feature was created in BCS33.
Restrictions and limitations
This feature does not support the following combinations:
• input/output user interface (IOUI) and ILM maintenance links on the
same card
• channelized and nonchannelized links on the same card

Multiple physical links are only supported for ILM-maintained channelized

links.
A slower response time to maintenance commands may be observed because
of the increase in messages required to perform maintenance through ILM.
Feature interactions
This feature interacts with the ILM on the DMS-bus.
Datafill
This feature increases program store by 10 Kbytes.
User interface
Commands BSY, TST, and RTD are modified at the CHAIN level of a MAP
terminal to display ILM responses.
Commands TRNSL and CHAIN are modified at the SHELF level of a MAP
terminal to include link peripheral-side status information for channelized
IOUI and ILM links.

NTX945AA–16 297-1001-801i Standard 09.01 January 2000

NTX945AA NTX945AA
AQ0717 AQ0717
Feature name
DMS-bus Support for PLM Primitive Enhancements
Description
AQ0717 provides enhanced DMS-bus maintenance software for local
physical link diagnostic and fault reporting under the integrated link
maintenance (ILM) system.
BCS history
This feature was created in BCS33.
Restrictions and limitations
The ENET links do not use the link transactor. As a result, when a SONET
DMS (S/DMS) node is removed from a DMS-bus link and replaced with an
Enhanced Network (ENET) on the same link, the DMS-bus chain that
contains the link must be manual busied then returned to service so that the
link will be re-opened. This applies only to links from the subrate DS512
card (version NT9X62BA).
Feature interactions
This feature interacts with ILM on the DMS-bus and with local DMS-bus
interface card maintenance software.
Datafill
This feature increases program store by 20 Kbytes on ME and MI software
loads only.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX945AA–17

NTX945AA
AQ0718
Feature name
DMS-Bus Support for MS–ILM Data Transfer and Audits
Description
AQ0178 provides DMS-bus maintenance software that compares and
corrects status mismatches between message switch (MS) maintenance and
ILM. This feature also provides central and local support to assist in the
ILM audit of physical links (PLK) and message channels (MCH).
BCS history
This feature was created in BCS33.
Datafill
This feature increases program store by 100 Kbytes and increases data store
by 4 Kbytes.

NTX945AA–18 297-1001-801i Standard 09.01 January 2000

 NTX945AA
AQ0840
Feature name
S/DMS MMI Consistency and Enhancements
Description
AQ0840 enhances the DMS-bus user interface software to provide
consistency with other DMS and synchronous optical network (SONET)
DMS (S/DMS) nodes. Several MAP level commands are simplified, two
minor message switch (MS) alarms are introduced, and the message switch
routine exercise (REX) tests adopt the system REX (SREX) scheduler to
replace invocation by the input/output REX process (IOREXP).
BCS history
This feature was created in BCS34.
Feature interactions
This feature requires feature AL2030 (System REX Test Controller).
Datafill
This feature increases program store by a maximum of 100 Kbytes and
increases data store by a maximum of 2 Kbytes.
User interface
This feature modifies command TRNSL in MAP directories MSSHDIR,
MSDYDIR, and MSCDDIR at the MS level, by minimizing the number of
parameters required.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX945AA–19

NTX945AA
AQ0854
Feature name
MS Backwards Compatibility—II
Description
AQ0854 enhances DMS-bus software to support backward compatibility in
the message switch (MS) software load. This feature follows up feature
AL1968 (DMS-Bus Backwards Compatibility Support).
AQ0854 provides the following advantages:
• simplification of BCS application procedures
• independent loading of the computing module (CM) software and the
MS software
• ensures that both MSs are in service after the restart switch of activity
(SwAct)
• simplification of peripheral-side (P-side) node SwAct software
• a new MS load can be sanitized before the MS with the existing load is
put out of service with a warm SwAct
• any maintenance operation message from the CM is sufficient to notify
the MS of which BCS load the CM is running, and to maintain
backwards compatibility
• the transaction processing system (TPS) allows larger messages to be
used in the MS and link peripheral processor
BCS history
This feature was created in BCS34.
Restrictions and limitations
Both the CM and the MS must have a software load of BCS34 or later for
this feature to take effect.
Datafill
This feature increases data store by a maximum of 6 Kbytes and increases
program store by a maximum of 1 Kbyte.

NTX945AA–20 297-1001-801i Standard 09.01 January 2000

 NTX950AA
MS Bilge
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTX950AA
Feature number Description

BC1829 Local Message Switch Maintenance

AL0712 Message Switch Diagnostic Enhancements
AL0787 DMS-bus Diagnostic Enhancements Using the Tracer Card
AC0638 Maintain Messaging Over Restarts
AL0790 DMS-bus Software Support for 4 MByte Memory CPU Card

BCS history
This feature package was created in BCS23.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX950AA–1

NTX950AA
AC0638
Feature name
Maintain Messaging Over Restarts
Description
AC0638 maintains messaging for as long as possible during restarts. When
the DMS-bus undergoes a computing module (CM) restart (other than a
RELOAD), links are kept in service where possible. Mapper addresses are
maintained over warm and cold restarts. Ports (and the links they control)
are kept in service for those links that must maintain high availablity.
This feature makes the DMS SuperNode more robust and reliable by
ensuring fewer interruptions of traffic over restarts.
BCS history
This feature was created in BCS31.

NTX950AA–2 297-1001-801i Standard 09.01 January 2000

 NTX950AA
AL0787
Feature name
DMS-bus Diagnostic Enhancements Using the Tracer Card
Description
AL0787, with the support of the tracer card, enables faults in the local
DMS-bus to be isolated and reported.
Currently, faulty T-bus messages are detected at the destination card
interfaces. With the tracer card, each message on the T-bus is monitored,
any faulty message is detected, and the message source is identified. The
feature also reports faults to the source interface card transactor through the
input/output error channel and sends messages to the destination interface
card transactor to cancel faults detected by the CMU.
BCS history
This feature was created in BCS29.
Hardware requirements
This feature requires an 1W2 NT9X49CB DMS-bus Tracer Card in card slot
26 of DMS-bus shelf 0.
User interface
Command TRCCONFIG is changed to accommodate the message truncation
configuration.
Command TRCSETTRIG is changed to enable trigger conditions to be
entered for protocol, byte, and message count overflow.
Commands TRCADDLIST, TRCSHOWCNT, and TRCSETCNT are
changed to accommodate the port range of 0 to 127.
Command TRCSETPROT is added to set the protocol byte value for
triggering.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX950AA–3

NTX950AA
AL0790
Feature name
DMS-bus Software Support for 4 Mbyte Memory CPU Card
Description
AL0790 provides an NT9X13DC processor card with 4 Mbyte of memory.
This increases the memory by 3 Mbyte beyond that provided by the current
1 Mbyte NT9X13DA/B.
BCS history
This feature was created in BCS29.
Hardware requirements
This feature requires an NT9X13DC Processor Card in card 3 of DMS-bus
shelf 0.
Pack diagnostic specifics
The PEC CODE of the affected pack is NT9X13DC. It provides 100
percent coverage improvement.
Restrictions and limitations
NT9X13DC requires BCS29 firmware to be in place.

NTX950AA–4 297-1001-801i Standard 09.01 January 2000

 NTX951AA
MS Common
This feature package applies to DMS-100 and SuperNode message switch
offices.
Feature package contents
Feature package NTX951AA contents
Feature number Description

BC1921 Message Switch Maintenance

BC2308 Time of Day for Message Switch
AL1456 Design and Data Definition for DS30/IOUI Inter-MS Links
AC0639 MMI for Inter-MS Links
AG1334 DMS-bus (Local) 128-Port I/F Card S/W 1W H/W Integration
AL1199 DMS-bus Central Data Distribution and Initialization II
AL1186 DMS-bus Fault Correlation Using Tracer Card (9X46CB)
AL1185 DMS-bus 128-Port Transactor
AC0608 DMS-bus System Clock NT9X53AC Software Support
AQ0739 DMS-bus BCS SwAct Reduced Restart
AQ0858 DMS-bus S/W for Sub-rate MS-ENET Links

BCS history
This feature package was created in BCS23.
Required feature packages
Required feature packages
Feature package Description
number

NTX001AA Common Basic

Feature Description Manual Volume 2 of 3 BCS44.1i NTX951AA–1

NTX951AA
AC0639
Feature name
MMI for Inter-MS Links
Description
AC0639 provides user interface enhancements for intermessage switch
(inter-MS) links, message switch (MS) and frame transport system (FTS)
interaction during restarts, and peripheral-side (P-side) maintenance
notification of the gain or loss of inter-MS links on the DMS-bus.
BCS history
This feature was created in BCS33.
Hardware requirements
This feature requires one port for each MS in the inter-MS link. Each link
must be on a separate interface card.
Restrictions and limitations
This feature requires features AL1456 (Design and Data Definition for
DS30/IOUI Inter-MS links) and AC0638 (Maintain Messaging over
Restarts).
Datafill
This feature increases program store by 10 Kbytes.
Logs
Logs MS320 through MS327 are added by this feature.
Log MS320 is generated when the inter-MS port changes from a system
busy or a manual busy state to an in-service state.
Log MS321 is generated when the inter-MS port changes from in service to
manual busy.
Log MS322 is generated when the inter-MS port changes from system busy,
remote-side (R-side) busy, or central-side (C-side) busy to manual busy.
Log MS323 is generated when the inter-MS port changes from in service to
system busy.
Log MS324 is generated when the inter-MS port changes from R-side busy
or C-side busy to system busy.
Log MS325 is generated when the inter-MS port changes from system busy
to C-side busy.

NTX951AA–2 297-1001-801i Standard 09.01 January 2000

 NTX951AA
AC0639
Log MS326 is generated when the inter-MS port changes from system busy
to R-side busy.
Log MS327 is generated when a fault is detected on an inter-MS port that is
in service.
User interface
Command INTERMS is added at the MS and MSSH levels of a MAP
terminal.
Command BSY is modified at the SHELF and CARD levels of a MAP
terminal.
Command SWROUTE is deleted at the MS level of a MAP terminal.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX951AA–3

NTX951AA
AL1199
Feature name
DMS-bus Central Data Distribution and Initialization II
Description
AL1199 enhances the functions of the DMS-bus audit to include chains and
channelized links. The capacity of the audit is extended to accommodate a
maximum of 128 ports per interface card.
BCS history
This feature was created in BCS31.

NTX951AA–4 297-1001-801i Standard 09.01 January 2000

 NTX951AA
AL1456
Feature name
Design and Data Definition for DS30/IOUI Inter-MS Links
Description
AL1456 provides DMS-bus software maintenance support for ports on
intermessage switch (inter-MS) links in a SuperNode switch.
BCS history
This feature was created in BCS33.
Hardware requirements
This feature requires one port for each message switch (MS) in the inter-MS
link.
Restrictions and limitations
Inter-MS links must be datafilled on separate interface cards to ensure that at
least one link is available if a card goes out of service.
This feature requires the following features:
• AI0127 FTS Routing Control
• AL1198 DMS-bus High Level Design for Integrated Node
• AL1477 Central DMS-bus and ILM Interactions on Message
Channels
Datafill
Table Description

MSILINV Table is added to datafill inter-MS link positions in the DMS-bus.

This feature increases program store by 10 Kbytes.

Logs
This feature adds logs MS290 through MS297.
Log MS290 is generated when the inter-MS port changes from a system
busy or a manual busy state to an in-service state.
Log MS291 is generated when the inter-MS port changes from in service to
manual busy.
Log MS292 is generated when the inter-MS port changes from system busy,
remote-side (R-side) busy, or central-side (C-side) busy to manual busy.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX951AA–5

NTX951AA
AL1456
Log MS293 is generated when the inter-MS port changes from in service to
system busy.
Log MS294 is generated when the inter-MS port changes from R-side busy
or C-side busy to system busy.
Log MS295 is generated when the inter-MS port changes from system busy
to C-side busy.
Log MS296 is generated when the inter-MS port changes from system busy
to R-side busy.
Log MS297 is generated when a fault is detected on an inter-MS port that is
in service.
Log MS104 is modified when an inter-MS link FTS is lost or gained through
inter-MS port transition, and when there is a switch in the MS node used for
FTS routing.
User interface
Command INTERMS is added at the MS level of a MAP terminal to enter
the card level for the card connected to the inter-MS link. Command
SWROUTE is added at the MS level of a MAP terminal to switch the FTS
active route from the current MS to the other MS.
Commands BSY and BSYMS are modified at the MS level of a MAP
terminal to ensure that FTS tandem routing is not lost through the manual
busy state of the MS node used for FTS tandem routing when no inter-MS
links are available.
Command BSY is modified at the SHELF level of a MAP terminal to ensure
that inter-MS link FTS tandem routing is not lost through the manual busy
state of a card in the last in-service inter-MS link.
Command BSY is modified at the CARD level of a MAP terminal to ensure
that inter-MS link FTS tandem routing is not lost through the manual busy
of a port or card of the last in-service inter-MS link.
The alarm NOIMSL is added to indicate the loss of all inter-MS links (such
as when inter-MS link routing is disabled). The alarm 01IMSL is added to
indicate the loss of one inter-MS link (inter-MS link routing over one link
only).

NTX951AA–6 297-1001-801i Standard 09.01 January 2000

 NTX951AA
AQ0835
Feature name
DMS-bus Clock Restructuring — II
Description
AQ0835 is part of the robustness program on DMS SuperNode switches.
This feature enhances the DMS-bus clock software that provides a clock
source for the entire DMS SuperNode system. The software is restructured
to make each clock function data independent of other clock functions,
which allows for easy evolution of the clock software. This feature is a
continuation of feature AQ0741 (SuperNode Clock Robustness
Restructure — I).
BCS history
This feature was created in BCS34.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX951AA–7

NTX951AA
AQ0858
Feature name
DMS-bus S/W for Sub-rate MS-ENET Links
Description
AQ0858 provides DMS-bus software required to support SuperNode SE
enhanced network (ENET16K). This feature provides support for the
following configurations:
• external capabilities
— ENET16K on subrate links
— two ENET16K planes on the same DMS-bus chain
• internal capability
— mixed chains on the local DMS-bus
BCS history
This feature was created in BCS34.
Hardware requirements
This feature requires the NT9X62CA card (DMS-bus 2-link fiber paddle
board).
Restrictions and limitations
This feature applies only to ENET16K in the SuperNode SE environment.
Feature interactions
This feature interacts with the following features:
• AL1756—SNSE DMS-Bus Maintenance Software Support
• AQ0857—SNSE DMS-Bus Software for Sub-rate CMIC Links
• AR0106—SNSE ENET MMI

Datafill
This feature increases data store by a maximum of 1 Kbyte and increases
program store by a maximum of 1 Kbyte.

NTX951AA–8 297-1001-801i Standard 09.01 January 2000

 NTX980AA
International Trunk Test Position (ITTP)
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTX980AA contents
Feature number Description

BC0158 Digital Pad Adjustment

BC0490 (NSG) Translation Verification for Partitial 6-digit Translation
BC0495 (NSG) Translation Verification DMS-250 Int. DAL & ONAL
Trunk Group Types
BC0693 TRAVER Enhancement
BC0858 STS Conversion
BC1259 Down Load Metallic Test Unit
BR0021 TTP Enhancements
BR0176 Circuit Monitor
BR0196 TTP Call Transfer (Local)
BR0200 Singing Point Test
BR0201 Echo Return Loss (ERL) Test
BR0223 Translation Verification–Trunks
BV0041 TTP Call Transfer

BCS history
This feature package was created in BCS01.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX470AA International–Common Basic

Feature Description Manual Volume 2 of 3 BCS44.1i NTX980AA–1

NTX980AA
BC0158
Feature name
Digital Pad Adjustments
Description
This feature provides
• the capability to set digital send pads and digital receive pads
• the capability to adjust the pad settings for an existing jack connection
• MAP (maintenance and administration position) display of digital pad
settings and pad adjustments for a given circuit
Digital pads are a function of trunk modules (TM) used to dynamically
adjust send and receive signal levels. Analog trunks have send (transmit)
pads and receive pads. Digital trunks on a TM or on a maintenance trunk
module (MTM) have only send pads.
BCS history
This feature was created in BCS08.
User interface
The command PADS is added to the MAP trunks test position (TTP) level.
The following parameters are available:
• The parameter R allows the setting of the digital receive pad. Receive
digital pads can be adjusted from 0 to +1.75 dB gain.
• The parameter S allows the setting of the digital send pad. Send digital
pads can be adjusted from 0 to –1.75 dB loss.
• The parameter PA allows the entering of the pad adjustment for an
existing connection.
• Entering no parameter displays the pad setting or the pad adjustment for
a given circuit.

NTX980AA–2 297-1001-801i Standard 09.01 January 2000

 NTX980AA
BC0490
Feature name
(NSG) Translation Verif. for Partitioned Six-digit Transl
Description
This feature provides the capability to display datafill used for translation
verification of partitioned six-digit translation.
BCS history
This feature was created in BCS10.
Feature interactions
This feature is related to feature BC0457 ([NSG] Partitioned Six-digit
Translation).
User interface
This feature affects the MAP (maintenance and administration position)
command interpreter (CI) commnad TRAVER and the trunks test position
(TTP) command TRNSLVF. The display generated by the trace option of
these commands is modified to include the subtable of table FNPACONT
used and the tuple used for partitioned six-digit translation verification.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX980AA–3

NTX980AA
BC0495
Feature name
(NSG) Translation Verif. for DMS-250 IMT, DAL, and ONAL Trk Grps
Types
Description
This feature defines translation verification indexes for the following types
of DMS-250 trunks:
• IMT (inter-machine trunk)
• DAL (dedicated access line)
• ONAL (off-net access line)

BCS history
This feature was created in BCS09.
User interface
The calling number and called number parameters of the MAP (maintenance
and administration position) trunks test position (TTP) command TRNSLVF
(translation verification) are increased from 15 to 18 digits.

NTX980AA–4 297-1001-801i Standard 09.01 January 2000

 NTX980AA
BC0693
Feature name
TRAVER Enhancement
Description
This feature enhances TRAVER (translation verification). TRAVER is a
tool designed to help the operating company personnel to debug the datafill
in the switch.
This feature adds the following functions to TRAVER:
• tracing calls originated by virtual facility groups (VFG)
• tracing specified routing lists and tables (routing verification)
• using table CUSTFLDS to modify the view of tables
• tracing table DIGCOL to show digit collection strategies

This feature also improves TRAVER by making it more efficient, more

easily maintained, more accurate, better gated, and better documented.
BCS history
This feature was created in BCS12.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX980AA–5

NTX980AA
BC0858
Feature name
STS Conversion
Description
This feature provides up to 1000 translation partitions (Service Translation
Schemes) for Integrated Business Network (IBN) and Electronic Switched
Network (ESN). IBN translation and translation verification (TRAVER) is
made compatible with Service Translation Schemes (STS).
BCS history
This feature was created in BCS13.
Restrictions and limitations
A line attribute index containing an STS that is not a serving numbering plan
area (SNPA) may not be used in line data, since the TOFCO field in table
LINEATTR is not expanded. The same restriction applies to POTS virtual
facility groups (VFG) in table VIRTGRPS, which also use line attributes.
These line attributes may be used in table IBNXLA, with the selector NET
and subselectors DOD (direct outward dialing), ESN, or OWT
(OUTWATTS), to provide an STS for an IBN agent.
The first 16 STSs in table HNPACONT are SNPAs. Only these values can
be used in line data, private branch exchange (PBX) trunk data, POTS VFG
data, and in tables DN, WRDN, and THOUGRP. If more SPNAs are to be
added after the initial datafill of an office, space must be reserved for them
in table HPNACONT by adding false SPNAs. Rearrangement of data in
table HPNACONT after initial datafill affects on tables DN, WRDN, and
THOUGRP, and the screening tables in which STS is the first part of the
key.
Datafill
Table Description

CLSVSCRC Field SPNA is replaced by field STS.

and
LCASCRCN · CLSVSCRC, Class of Service Screening (CSS), uses STS
instead of SPNA as the first part of the key.
· LCASCRCN, Local Call Area (LCA), uses STS instead of
SPNA as the first part of the key.
DIGMAN and Field SPNA is replaced by field STS.
LINEATTR

NTX980AA–6 297-1001-801i Standard 09.01 January 2000

 NTX980AA
BC0858
User interface
The digit manipulation command FLD DDD, which uses Local Area
Screening to convert numbers dialed in ESN format to DDD (direct distance
dialing) format, is converted to use STSs.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX980AA–7

NTX980AA
BC1259
Feature name
Download Metallic Test Unit
Description
This feature provides the central control software support required to
download firmware to a metallic test unit (MTU) through a maintenance
trunk module (MTM).
BCS history
This feature was created in BCS19.
Restrictions and limitations
Firmware cannot be downloaded to an MTU attached to a remote service
module (RSM) or to a remote maintenance module (RMM).
The following restrictions apply to downloading firmware to an MTU:
• Both logical MTUs must first be seized using the SEIZE command.
• The affected MTU must be manual busy.
• The MTM to which the affected MTU is attached must be in service.
• Only one logical MTU on an MTM can be loaded at one time.
• More than one logical MTU can be loaded if the MTUs are not attached
to the same MTM.
• If an MTM attached to an MTU being loaded becomes system busy, the
downloading stops.
• If the LOADFW NOWAIT command is issued, both logical MTUs must
be put into one of the hold positions before performing any other
operations.
Datafill
Table Description

TRKGRP, A tuple containing MTU information is added.

TRKSGRP,
TRKMEM,
CLLI, and
OFCAR

NTX980AA–8 297-1001-801i Standard 09.01 January 2000

 NTX980AA
BC1259
User interface
The command interpreter (CI) command LOADFW (load firmware) is
added to the MAP (maintenance and administration position) trunks test
position (TTP) level. This command allows the user to download firmware
to the MTU. The parameters available are filename (to specify the file name
of the firmware load), NOWAIT (to allow other commands to be issued
before firmware loading is completed), and QUERY (to allow printing of the
status of the firmware load for a particular MTU).

Feature Description Manual Volume 2 of 3 BCS44.1i NTX980AA–9

NTX980AA
BR0176
Feature name
Circuit Monitor
Description
This feature provides the capability to activate or deactivate circuit
monitoring on a posted circuit. Circuit monitoring allows the user to
intercept messages and generate displays of circuit status, and intercepted
messages and digits. Circuit status displays indicate the intercept status (ON
or OFF), if the circuit is in the control position, or if the circuit is moved to
another control position.
Interception of messages and digits is applied to an idle posted circuit only
when circuit monitoring is activated.
BCS history
This feature was created in BCS05.
User interface
At the monitor level of the trunks test position (TTP) of the MAP
(maintenance and administration position) display, the command CKTMON,
with the parameters ON and OFF, is added to activate and deactivate circuit
monitoring, respectively.

NTX980AA–10 297-1001-801i Standard 09.01 January 2000

 NTX980AA
BR0200
Feature name
Singing Point Test
Description
This feature implements the singing return loss (SRL) test. The SRL test,
which is part of the Automatic Transmission Measuring System (ATMS),
measures the return loss of a band-limited white noise signal over a trunk
circuit.
BCS history
This feature was created in BCS05.
User interface
At the trunks test position (TTP) level of the MAP (maintenance and
administration position) display, the parameter E is added to the command
LOSS to specify and initiate the SRL test.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX980AA–11

NTX980AA
BR0201
Feature name
Echo Return Loss (ERL) Test
Description
This feature implements the ERL test. The ERL test, which is part of the
Automatic Transmission Measuring System (ATMS), measures the return
loss of a band-limited white noise signal over a trunk circuit.
BCS history
This feature was created in BCS05.
User interface
At the trunks test position (TTP) level of the MAP (maintenance and
administration position) display, the parameter E is added to the command
LOSS to specify and initiate the ERL test.

NTX980AA–12 297-1001-801i Standard 09.01 January 2000

 NTX980AA
BR0223
Feature name
Translation Verification–Trunks
Description
This feature provides the following capabilities:
• verifying translation routing data by simulating the translation of digits
• tracing and verifying the data that is used to translate incoming digits
into a route
• displaying digits to be sent on a given circuit for a given test line code

BCS history
This feature was created in BCS05.
Restrictions and limitations
Only the following originators are recognized by translation verification:
• originating toll and intertoll trunks
• incoming centralized automatic message accounting (CAMA) trunks
• incoming operator (OPR) trunks
• incoming and local two-way trunks
• all lines

User interface
Translation verification for a posted originating trunk is invoked using the
menu command TRNLSVF at the trunks test position (TTP) level of the
MAP (maintenance and administration position) display.
Depending on the parameters used, the command TRNSLVF generates
displays of some or all of the following information:
• the common language location identifier (CLLI) of the direct and
alternate routes attempted, along with the digits that would be sent
• the name of the overflow treatment and its corresponding CLLIs
• the name of the position and its corresponding CLLIs

The following parameters are available with the TRNSLVF command:

• test line code (3 digits)
• called number (1 to 15 digits)
• called ST signal (ST, STP, ST2P, ST3P, or STKP)
• calling number (1 to 15 digits)
• calling ST (start) signal (ST, STP, ST2P, ST3P, or STKP)
• T (trace)

Feature Description Manual Volume 2 of 3 BCS44.1i NTX980AA–13

NTX980AA
BR0223
If the trace option is not used, routing and digit outpulse information is
displayed for the following types of routing:
• digit translation routes (up to 8 route selections)
• treatment routes (up to 8 route selections)
• position routes (up to 8 route selections)

TRAVER is also invoked from the command interpreter (CI) level of the
MAP display using the command TRAVER. The TRAVER command
allows both lines and trunks to be specified as originators. The following
parameters are available with the TRAVER command:
• originator: TR (trunk) plus CLLI, or L (line) plus directory number (DN)
• called number (1 to 15 digits)
• called multifrequency start (MFST) signal (MFST, MFSTP, MFST2P,
MFST3P, or MFSTKP)
• calling number (1 to 15 digits)
• calling MFST signal (MFST, MFSTP, MFST2P, MFST3P, or MFSTKP)
• T (trace) or NT (no trace)

NTX980AA–14 297-1001-801i Standard 09.01 January 2000

 NTX980AA
BV0041
Feature name
TTP Call Transfer
Description
This feature allows maintenance personnel to transfer a connection from a
101 test line to a headset and to move the call processing linked circuit to the
trunks test position (TTP) control position.
BCS history
This feature was created in BCS01.

Feature Description Manual Volume 2 of 3 BCS44.1i NTX980AA–15

 NTXA66AA
Enhanced Office Recovery
This feature package applies to DMS-100 and REMOTE offices.
Feature package contents
Feature package NTXA66AA
Feature number Description

AJ0192 RCC LCM Loading Enhancements I

AJ0474 XPM P-side Data Distribution Enhancements
AL0480 PM MAP Enhancements
AL0481 XPM IPML Data Distribution
AL0482 XPM P-side Data Distribution

BCS history
This feature package was created in BCS26.
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX270AA New Peripheral Maintenance Package

Feature Description Manual Volume 2 of 3 BCS44.1i NTXA66AA–1

NTXA66AA
AJ0192
Feature name
RCC Loading Enhancement
Description
AJ0192 modifies the loading speed of a remote cluster controller (RCC).
This feature also provides support for broadcast loading of domestic and
international line concentrating modules (LCM).
BCS history
This feature was created in BCS28.
Hardware requirements
This feature requires a remote cluster controller (RCC) equipped with
6X45BA version KA01 or higher.
Restrictions and limitations
Enhanced remote cluster controller (RCC) loading is invoked only when
both units of the RCC are out of service.
The speed of loading of an RCC is limited by the messaging bandwidth,
propagation delay and messaging protocol efficiency.
Datafill
The following tables were modified for this feature:

Table Description

RTSNT VIRTUAL_RCC_NODE added to range of values for

NODETYPE field

RTSALGO VIRTUAL_RCC_NODE added to range of values for RTSVECT

field

OFCOPT office parameter OFFICE_RECOVERY_AVAILABLE modified to

trigger broadcast LCM loading and enhanced RCC loading
office parameter MATE_LOADER_AVAILABLE deleted by this
feature

User interface
Command LOADPM in directory LCMDIR (when set with the ALL option
for LCMs) is used to invoke the broadcast loading of LCMs. Command
RECOVER in directory RCCDIR uses the enhanced RCC loading method
provided by this feature, instead of the regular loading method. A new
response message is added to command ABTK (abort task).

NTXA66AA–2 297-1001-801i Standard 09.01 January 2000

 NTXA66AA
AJ0474
Feature name
RCC LCM Loading Enhancements II
Description
AJ0474 implements an algorithm in order to distribute load messages to
peripherals in the XMS-based peripheral module (XPM) broadcast mate
loading application and the broadcast line concentrating module (LCM)
loading application. This feature reduces the amount of time required to
load a number of peripherals or units in parallel.
BCS history
This feature was created in BCS29.
Restrictions and limitations
This feature requires XMS-based peripheral modules (XPM) equipped with
new messaging (NT6X69) and NT6X45BA or later processor packs.
AJ0474 applies to all XPMs except emergency stand-alone (ESA) single
unit peripheral modules.
This feature supports both regular line concentrating modules (LCM) and
XLCMs.
Datafill
As a result of this feature, XPM MP store (including both program and data
store) is decreased by 5 Kbytes.
Logs
Log PM181 is modified to produce one log for the entire broadcast set. This
log summarizes the loading results for all destinations. Prior to this feature,
log PM181 produced a separate log for each destination node or unit in the
broadcast set.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXA66AA–3

 NTXB00AA
International Traffic Separation
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTXB00AA contents
Feature number Description

AC0131 International Traffic Separation

BCS history
This feature package was created in BCS23.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX470AA International–Common Basic

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB00AA–1

NTXB00AA
AC0131
Feature name
INTL Traffic Separation
Description
This feature provides traffic separation for a DMS-100 switch. The feature
allows all call originations and destinations for an office to be separated into
groups, so that traffic flowing through these groups can be measured and
analyzed on a point-to-point basis.
Originating traffic data can be separated according to call type. The call
components that can be measured and separated are
• point-to-point attempt peg count
• point-to-point connect time

BCS history
This feature was created in BCS23.
Restrictions and limitations
The following restrictions exist with this feature:
• Call setup use is not accumulated.
• Traffic separation numbers must be in the range of 0 to 127.
• Feature activation and deactivation calls are not separated.
• The maximum number of operational measurement (OM) registers that
can be allocated for traffic separation in an office is 2048.
• The maximum number of traffic separation intersections that can be
datafilled in table TFANINT for an office is 2048.
• In table TFANINT, field TFANIN cannot be zero.
• Table control for TRKGRP, LINEATTR, TONES, and ANNS does not
determine if the origination and destination traffic separation numbers
entered are equal to or less than office parameters
TFAN_IN_MAX_NUMBER and TFAN_OUT_MAX_NUMBER. Table
control for TFANINT does determine this.
• Once office parameters TFAN_IN_MAX_NUMBER,
TFAN_OUT_MAX_NUMBER, and NO_TFAN_OM_REGISTERS
have been set to a particular value, that value cannot be decreased.
Feature interactions
This feature requires international call processing and the operational
measurement system.
International traffic separation consists of the following feature packages:
• NTX085AA (Traffic Separation Peg Count).

NTXB00AA–2 297-1001-801i Standard 09.01 January 2000

 NTXB00AA
AC0131
• NTX087AA (Traffic Separation Usage). This optional feature package
implements the connect usage registers TFANCU and TFANCU2.
• NTXB01AA (INTL – Traffic Separation Report). This optional feature
package implements the traffic separation summary report of all peg and
usage counts.
Operational measurements
In an office that has feature package NTX085AA, OMs TFANPEG (base
register of attempt peg count) and TFANPEG2 (extension register of
TFANPEG) are pegged. In an office that also has feature package
NTX087AA, OMs TFANCU (basic register of connect usage) and
TFANCU2 (extension register of TFANCU) are added to the OMs in the
basic package.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB00AA–3

 NTXB01AA
International Traffic Separation Report
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTXB01AA contents
Feature number Description

AC0131 International Traffic Separation

BCS history
This feature package was created in BCS23.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX470 International–Common Basic

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB01AA–1

NTXB01AA
AC0131
Feature name
INTL Traffic Separation
Description
This feature provides traffic separation for a DMS-100 switch. The feature
allows all call sources and destinations for an office to be separated into
groups, so that traffic flowing through these groups can be measured and
analyzed on a point-to-point basis.
Originating traffic data can be separated according to call type. The call
components that can be measured and separated are
• point-to-point attempt peg count
• point-to-point connect time

BCS history
This feature was created in BCS23.
Restrictions and limitations
The following restrictions exist with this feature:
• Call setup use is not accumulated.
• Traffic separation numbers must be in the range of 0 to 127.
• Feature activation and deactivation calls are not separated.
• The maximum number of operational measurement (OM) registers that
can be allocated for traffic separation in an office is 2048.
• The maximum number of traffic separation intersections that can be
datafilled in table TFANINT for an office is 2048.
• In table TFANINT, field TFANIN cannot be zero.
• Table control for TRKGRP, LINEATTR, TONES, and ANNS does not
determine if the source and destination traffic separation numbers
entered are equal to or less than office parameters
TFAN_IN_MAX_NUMBER and TFAN_OUT_MAX_NUMBER. Table
control for TFANINT does determine this.
• Once office partameters TFAN_IN_MAX_NUMBER,
TFAN_OUT_MAX_NUMBER, and NO_TFAN_OM_REGISTERS
have been set to a particular value, that value cannot be decreased.
Feature interactions
This feature requires international call processing and the operational
measurement system.

NTXB01AA–2 297-1001-801i Standard 09.01 January 2000

 NTXB01AA
AC0131
International traffic separation can be engineered according to individual
office requirements. The complete feature is composed of the following
features:
• international basic traffic separation. This feature is present in all
international offices and is part of feature package NTX470AA
(International Common Basic).
• international traffic separation usage counts. This optional feature
package implements the connect usage registers TFANCU and
TFANCU2.
• international traffic separation summary report. This optional feature
package implements the traffic separation summary report of all peg and
usage counts.
Operational measurements
In an office that has the basic traffic separation feature package, OMs
TFANPEG (base register of attempt peg count) and TFANPEG2 (extension
register of TFANPEG) are pegged. In an office that also has the
international traffic separation usage feature package, OMs TFANCU (basic
register of connect usage) and TFANCU2 (extension register of TFANCU)
are added to the OMs in the basic package.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB01AA–3

 NTXB02AA
International Service Analysis–Basic
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTXB02AA contents
Feature number Description

AE0153 International Services Analysis Base

BCS history
This feature package was created in BCS24.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX470AA International–Common Basic

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB02AA–1

NTXB02AA
AE0153
Feature name
International Service Analysis Base
Description
This feature provides service analysis for DMS-200 toll offices. The service
analysis system allows the analyst at the MAP (maintenance and
administration position) to evaluate the quality of service provided by
monitoring the speech connection or displaying call event details for
randomly selected calls. Service analysis commands are used to set call
screening criteria, display information about an active call, and edit or
generate printouts of service analysis data.
BCS history
This feature was created in BCS24.
Hardware requirements
The service analysis system requires a MAP terminal equipped with a
headset, a three-port conference bridge, and the use of a printer.
Restrictions and limitations
The service analysis system is limited to five users at a time. The user
cannot specify the type of tone or announcement that a call has been routed
to. Service analysis can be performed only on international trunks whose
group type is MTR (metering) or OPR (operator). Service analysis is
discontinued if Malicious Call Trace (MCT) or Toll Break-in (TBI) are
activated.
Feature interactions
This feature requires service analysis base software.
Operational measurements
This feature affects the operational measurements (OM) relating to the use
of three-port conference bridges.
Logs
An international version of standard service analysis logs is produced.
User interface
The following service analysis levels are provided by this feature:
• SASelect (select)
• SA (analysis)
• ITRKSEL (trunk select)
• SAEdit (edit)

NTXB02AA–2 297-1001-801i Standard 09.01 January 2000

 NTXB02AA
AE0153
The SASelect level is the first service analysis level entered and provides
access to the other levels. At this level and the levels that can be accessed
from it, some or all of the following call detail information is displayed:
• office identifier
• call analysis start time
• call analysis mode (type of service selected for analysis)
• state of the monitor connection (released, connected with voice
monitoring off, connected and speech path signal audible, or connected
and signal not audible)
• call class (determined by translations available)
• called number
• current time
• agent selected (displays trunk selected)

The SA level is the main working level of service analysis. This level is
entered by selecting ITRKMP from the SASelect level menu. From the SA
level, calls are presented to the user, hard copy records of the analysis are
requested, and new calls are requested. Accessing this level activates
predefined call screening criteria. Once a call has been selected for analysis,
information on events during the call is collected by two methods:
system-detected events or user-detected events.
Eight events (displayed as character strings) can be detected by the system,
namely
• seize
• call connected
• answer
• disconnect
• treatment
• error
• announcement
• feature invoked

Certain call events that are not picked up by the system can be entered
manually by the user. Twenty-six system-activated or user-activated events
can be occur on each call and the display can show a maximum of 13 events
at one time. These events include
• ringing
• recorded announcement
• special signal

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB02AA–3

NTXB02AA
AE0153
• answer
• operator answer
• end of communication by an operator
The ITRKSEL level provides the a means of defining a trunk to be analyzed.
This level is accessed by selecting ITRKSEL from the SASelect level menu.
At this level, the trunk selection criteria are entered using menu commands.
Once a trunk has been defined, if a seized trunk matches the screening
criteria, analysis takes place on the call involving the trunk. Only one trunk
can be analyzed at a time.
The SAEdit level provides a means of reviewing data collected on an
analyzed call. This level is accessed by selecting SAEdit from the SA level
menu. Using the menu commands, corrections can be made and hard copy
requested.

NTXB02AA–4 297-1001-801i Standard 09.01 January 2000

 NTXB03AA
Service Analysis–Local
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTXB03AA contents
Feature number Description

AE0167 International Service Analysis–Local

BCS history
This feature package was created in BCS24.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX270AA New Peripheral Maintenance Package
NTX470AA International–Common Basic
NTX478AA CCITT PCM (30+2) Digital Signaling and Maintenance
NTX901AA Local Features I
NTXB02AA International Service Analysis–Basic
NTX472AA International–Local Basic (upgraded by NTX472AB)
or
NTX472AB International–Local Basic (upgrades NTX472AA)

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB03AA–1

NTXB03AA
AE0167
Feature name
INTL Service Analysis Local
Description
This feature provides service analysis for DMS-100 local offices. The
service analysis system allows the user at the MAP (maintenance and
administration position) to evaluate the quality of service provided by
monitoring the speech connection or displaying call event details for
randomly selected calls. Service analysis commands are used to set call
screening criteria, display information about an active call, and edit or
generate printouts of service analysis data.
BCS history
This feature was created in BCS24.
Hardware requirements
The service analysis system requires a MAP terminal equipped with a
headset, a three-port conference bridge, and the use of a printer.
Feature interactions
This feature requires service analysis base software and feature AE0153
(International Service Analysis Base).
Logs
A new version of the SA log is created. This log contains data collected by
analysis of a call.
User interface
The following service analysis levels are provided by this feature:
• SASelect (select)
• SA (analysis)
• ITRKSEL (trunk selection)
• ILNSEL (line selection)
• SAEdit (edit)

The SASelect level is the first service analysis level entered and provides
access to the other levels. At this level and the levels that can be accessed
from it, some or all of the following call detail information is displayed:
• office identifier
• call analysis start time
• call analysis mode (type of service selected for analysis)

NTXB03AA–2 297-1001-801i Standard 09.01 January 2000

 NTXB03AA
AE0167
• state of the monitor connection (released, connected with voice
monitoring off, connected and speech path signal audible, or connected
and signal not audible)
• call class (determined by translations available)
• calling number
• called number
• current time
• agent selected (displays trunk selected)
The SA level is the main working level of service analysis. From this level,
calls are presented to the user, hard copy records of the analysis are
requested, and new calls are requested. Accessing this level from the
ILNSEL, ITRKSEL or SASelect levels activates the defined screen. If
service analysis is not already in progress, all calls arriving become
candidates for selection. Once a call has been selected for analysis,
information on events during the call is collected by two methods: system
detected events or analyst detected events. Eight events (displayed as
character strings) can be detected by the system, namely, seize, call
connected, answer, disconnect, treatment, software failure, announcement,
and feature invoked. During analysis, the user can listen in on the call and
enter other call events not picked up by the system. The service analysis
system displays the event and the time into the call it was keyed in by the
user. The events available are ringing tone, verbal answer, verbal answer by
an operator, end of communication by an operator, reception of a recorded
announcement, and reception of a special signal.
The ITRKSEL level provides the user a means of defining a trunk to be
analysed. This level is accessed by selecting ITRKSEL from the SASelect
level menu. Once a trunk has been defined, if a seized trunk matches the
screening criteria, analysis takes place on the call involving the trunk. Only
one trunk can be analysed at a time.
At the ILNSEL level, the user can select lines by line class code or by site.
This level is accessed by selecting ILNSEL from the SASelect level menu.
At this level, the line selection criteria are entered using menu commands.
Once a line has been defined, if a line matches the screening criteria,
analysis takes place on the call involving the line.
The SAEdit (edit) level provides a means of reviewing data collected on an
analysed call. This level is accessed by selecting SAEdit from the SA level
menu. Using the menu commands, corrections can be made and hard copy
requested.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB03AA–3

 NTXB04AA
PBX Line Support
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTXB04AA contents
Feature number Description

AE0169 Line Reversal on Seizure

BCS history
This feature package was created in BCS24.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX270AA New Peripheral Maintenance Package
NTX470AA International–Common Basic
NTX901AA Local Features I
NTX472AA International–Local Basic (upgraded by NTX472AB)
or
NTX472AB International–Local Basic (upgrades NTX472AA)

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB04AA–1

NTXB04AA
AE0169
Feature name
Line Reversal on Seizure
Description
This feature implements the following DMS-100 line options as part of the
line reversal facility:
• LRA (line reversal on answer)
• LRS (line reversal on seizure)

For calls terminating on the private branch exchange (PBX) line, reversal is
applied on seizure, and is followed by ringing.
For calls originating from the PBX line, the call is routed and connected
through the DMS switch as a regular call. When the called subscriber
answers, the answer is received by the DMS switch. If the line has the LRA
option datafilled, reversal is applied to the PBX line. If the line also has the
subscriber premises meter (SPM) option datafilled, a delay of 500 ms to
600 ms is applied before SPM pulses are sent.
BCS history
This feature was created in BCS24.
Hardware requirements
This feature requires cards NT6X94AB (line card 600 Ω international type
B [Turkey]) and NT6X94BA (line card international, CEP).
Restrictions and limitations
This feature is restricted to standard (STD) lines. The coin lines and
semi-permanent connection (SPC) lines features are not compatible with line
reversal to a PBX.
Datafill
Line options LRA and LRS can be datafilled against STD lines only.
Service orders
Service orders allow the allocation, deletion, and querying of line options
LRA and LRS.

NTXB04AA–2 297-1001-801i Standard 09.01 January 2000

 NTXB05AA
ITOPS Common Basic
This feature package applies to DMS-100/200 and DMS-200 offices.
NTXB05AA provides two periodic reports on system and operator
efficiency for calls routed to International Traffic Operator Position System
(ITOPS) positions. Data is provided on the number of call attempts,
successful calls, busy calls, calls with no answer, and call failures.
The OTO30 report is generated every 30 min and contains the service
analysis data for operators in each traffic office (TO).
The OFM6HR report is generated every 6 h and contains service analysis
data accumulated for all operators in the system.
Feature package contents
Feature package NTXB05AA contents
Feature number Description

AJ1257 ITOPS: Service Analysis

BCS history
This feature package was created in BCS36.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX056AA Enhanced Administration
NTX270AA New Peripheral Maintenance Package
NTX470AA International Common Basic
NTX657AA International CAMA
NTX909AA ANI Toll

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB05AA–1

NTXB05AA
AJ1257
Feature name
ITOPS: Service Analysis
Description
This feature provides two new periodic reports for a DMS-100/200 switch
and a DMS-200 switch. These reports provide data relating to system and
operator efficiency for calls routed to International Traffic Operator Position
System (ITOPS) positions. The data provided includes the number of call
attempts, successful calls, busy calls, calls with no answer, and call failures.
The OTO30 report is generated every 30 min and contains the service
analysis data for the operators in the system for each traffic office (TO). The
period for these reports can be changed from the default value of 30 min to
15, 45, or 60 min (reports OTO15, OTO45, and OTO60, respectively).
The OFM6HR report is generated every 6 h and contains service analysis
data accumulated for all operators in the system.
BCS history
This feature was created in BCS36.
Restrictions and limitations
This feature is intended for the China market.
Reports OTO15, OTO30, OTO45 and OTO60 are generated at Traffic
Administration Data System (TADS) terminals only.
OFM6R reports are generated at force management (FM) Force
Administration Data System (FADS), System Administration Data System
(SADS), FADS/HOBIC administration (FADSHADS), and FADS/HOBIC
administration (SADSHADS) terminals only.
OTO30 reports provide information for a maximum of 30 operators.
OFM6HR reports provide information for a maximum of 900 operators.
User interface
New commands O15, O30, O45, and O60 can be entered from any FM or
TADS TTY to set the period for reports OTO15, OTO30, OTO45, and
OTO60, respectively.

NTXB05AA–2 297-1001-801i Standard 09.01 January 2000

 NTXB07AA
Inter Administration Accounting
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTXB07AA contents
Feature number Description

AE0154 Inter Administration Accounting

BCS history
This feature package was created in BCS24.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX470AA International–Common Basic
NTX657AA International CAMA

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB07AA–1

NTXB07AA
AE0154
Feature name
International Administration Accounting
Description
This feature, which uses international centralized automatic message
accounting (ICAMA), provides international administration accounting
(recording of international toll transit and toll completing call details).
BCS history
This feature was created in BCS24.
Restrictions and limitations
This feature applies only to MTR (metering) trunks.
Calls on automatic number identification (ANI) trunks are not recorded by
international administration accounting (IAA).
Feature interactions
This feature requires ICAMA.
Datafill
Table Description

OVCAR Office parameter IAA REQUESTED is added to specify whether

IAA is used.
TRKGRP A new field is added to indicate if the calls on a trunk are to be
recorded by IAA.

Operational measurements
The operational measurement (OM) for ICAMA_RECORDING_UNIT is
pegged by this feature and ICAMA when a recording unit (RU) is seized,
not available, or used.

NTXB07AA–2 297-1001-801i Standard 09.01 January 2000

 NTXB08AA
ITOPS for CEP
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTXB08AA contents
Feature number Description

AG0717 ITOPS Billing and Rating for CEP

BCS history
This feature package was created in BCS25.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX056AA Enhanced Administration
NTX270AA New Peripheral Maintenance Package
NTX470AA International–Common Basic
NTX909AA ANI Toll
NTXB05AA ITOPS Common Basic
NTXB84AA International Rating System
NTXB13AA ITOPS Toll Basic (upgraded by NTXB13AB)
or
NTXB13AB ITOPS Toll-Enhanced Queueing (upgrades NTXB13AA)

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB08AA–1

NTXB08AA
AG0717
Feature name
ITOPS Billing and Rating for CEP
Description
This feature implements billing and rating capabilities for the Carribean
expansion plan (CEP) International Traffic Operator Position System
(ITOPS) application. It provides a rating system that can reproduce the
charge calculations carried out by downstream call details processing. This
capability allows the operator to quote call charges to the customer.
This feature defines
• the operating company datafillable rating tables that allow automatic
rating of calls
• special billing requirements for billing calls to calling cards and third
parties
• special billing requirements for validation of special billing numbers

BCS history
This feature was created in BCS25.
Restrictions and limitations
This feature supports only the following types of special billing:
• calling card billing
• third party billing

Calling cards that are supported by this feature are limited to cards with
numbers in the following formats:
• NPA–Nxx (NPA–Nxx–xxxx–xxxx)
• RAO (RAO–0/1xx–xxxx–xxxx)
• overseas (CCaxxxxxxxxx)

NTXB08AA–2 297-1001-801i Standard 09.01 January 2000

 NTXB10AA
China Common Basic
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTXB10AA contents
Feature Description
number

AG0707 C1 Line Signaling

AG0708 C1 Call Processing
AG0711 C1 Register Signaling
AJ0782 C1 MFC Trunk Implementation on the Generic R2 System–CC
AJ0796 Overlap Outpulsing for DMS-100I
AJ0819 C1 MFC Trunk Implementation on the Generic R2 System–XPM
AJ2529 R2 Billing Category Enhancements

BCS history
This feature package was created in BCS26.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX270AA New Peripheral Maintenance Package
NTX470AA International–Common Basic
NTX478AA CCITT PCM (30+2) Digital Signaling and Maintenance
NTX901AA Local Features I
NTX904AA R2 Signaling Base

NTX472AA International–Local Basic (upgraded by NTX472AB)

or
NTX472AB International–Local Basic (upgrades NTX472AA)

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB10AA–1

NTXB10AA
AG0707
Feature name
CI Line Signaling
Description
This feature provides line signaling systems for trunk call processing in
DMS-100 and DMS-200 switches in China.
BCS history
This feature was created in BCS26.
Datafill
Table Description

LNSIGSYS One tuple is added for each new line signaling system.
TRKSGRP Data selector DIALSTART is extended to include the values
MANSWB and SASWB.

NTXB10AA–2 297-1001-801i Standard 09.01 January 2000

NTXB10AA NTXB10AA
AG0708 AG0708
Feature name
CI Call Processing
Description
This feature provides the central control (CC) software required to provide
line and trunk call processing for the DMS network in China.
BCS history
This feature was created in BCS26.
Restrictions and limitations
Two-way trunk groups, Z-calls, and test calls are not supported.
Most features are not supported for calls over multifrequency controlled
(MFC ) trunks.
If one subgroup of a particular trunk is datafilled such that it references an
entry in table RGSIGSYS with a register signaling type of NTRS09, then the
other subgroup must be datafilled such that it also references an entry in
table RGSIGSYS with a register signaling type of NTRS09.
Datafill
Table Description

TRKGRP Field TRFC is added. This field is independent of trunk

direction and indicates the type of traffic that flows over the
trunk group.

Field DGNAME is added. This field only applies to incoming

trunk groups and specifies the type of digit analysis performed.

Field EEDENY is added. This field is independent of the trunk

direction and is used to prohibit calls on the affected trunk group
from establishing end-to-end connections.

Logs
This feature provides new values in the TRBLINFO field of TRK312 and
TRK313 logs. The new values represent the type of register failure detected
and reported by the incoming and outgoing registers.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB10AA–3

NTXB10AA
AG0711
Feature name
CI Register Signaling
Description
This feature provides the register signaling for the signaling system C1 in
the DMS-100 switch, and provides support for the new tones card required
for the DMS network in China. C1 is a multifrequency compelled (MFC)
signaling system used in China. It is based on CCITT R2.
BCS history
This feature was created in BCS26.
Hardware requirements
This feature requires the NT6X69KA (message protocol and tones) card.
Datafill
The office parameter TONE_SET in table OFCENG must be datafilled with
the value CHINA.
The digit analysis tables DGHEAD and DGCODE are made available in the
international digital trunk controller (IDTC) as well as in the international
line group controller (ILGC). To distinguish between tuples used by lines
and trunks, field DGTYPE is added to the DGHEAD tuple. This tuple can
have the value LINE (for lines), TRK (for trunks), or BOTH (for both lines
and trunks).

Table Description

RGSIGSYS The register signaling index NTRS09 is added.

LTCINV Values 6X02KA (shelf code for the tones card in an IDTC) and
6X02KB (shelf code for the tones card in an ILGC) are added to
field EQPEC.

User interface
The command interpreter (CI) command DGTABLES, which downloads
tables DGHEAD and DGCODE to XMS-based peripheral modules (XPM),
is changed to include a parameter that specifies whether these tables are
downloaded to the ILGC, the IDTC, or both.

NTXB10AA–4 297-1001-801i Standard 09.01 January 2000

NTXB10AA NTXB10AA
AJ0782 AJ0782
Feature name
C1 MFC Trunk Implementation on the Generic R2 System – CC
Feature name
This feature implements a modified R2 protocol to be supported by
DMS-100 switches for the C1 multifrequency compelled (MFC) national
network in China. The signaling type used for this register signaling is
changed from NTRS09 to NTRS11.
This feature provides the same functionality as the following features:
• AG0708 C1 Call Processing
• AG0710 Toll Break-in for China – DMS-100
• AG0711 C1 Register Signaling
• AG1079 C1 Call Processing II
• AG1294 C1 Trunk ITOPS Position Interactions
• AJ0183 C1 DID and DOD PBX Trunks
BCS history
This feature was created in BCS30.
Hardware requirements
This feature requires theNT6X69KA (message protocol and tones) card and
the NT6X92CA (international UTR tone detection) card in each unit of the
international digital trunk controller (IDTC).
Restrictions and limitations
The international traffic operator position system (ITOPS) service classes
UNSPEC, MOBILE, MARINE, and COIN cannot be signaled over C1
trunks in China.
Calling card verification calls are not supported over C1 trunks from ITOPS
positions.
Two-way trunk groups, Z-calls, and test calls are not supported.
Most features are not supported for calls over MFC (multifrequency
controlled) trunks.
TBI is allowed only on local voice calls. The TBI call must be line-line,
line-trunk, trunk-line, or line-tone. The subscriber in a TBI call cannot be
connected to an announcement, dialing, or ringing.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB10AA–5

NTXB10AA
AJ0782
TBI is not applicable to subscribers classified as
• data lines
• especially important subscribers

The following ITOPS service classes of originating subscribers cannot be

signaled between offices in China:
• UNSPEC (unspecified)
• MOBILE
• MARINE
• COIN

Feature interactions
The following features interact with C1 signaling in China and will behave
differently:
• Call Diversion (CDIV)
• Call Waiting (CWT)
• Cancel Call Waiting (CCW)
• Coin Line
• Free Number Terminating (FNT)
• Malicious Call Trace (MCT)
• No Double Connect (NDC)
• Priority (PR1, PR2)
• Toll Break-in (TBI)

Calls terminating in a DMS switch where the subscriber has CDIV activated
have the called subscriber line status of the subscriber line to which the call
is being diverted signaled back to the previous office.
If the DMS switch is the terminating exchange and the called subscriber has
CWT, the called subscriber signal sent to complete register signaling is one
of the idle subscriber signals.
If the DMS switch is the terminating exchange and the called subscriber line
is busy with CCW activated, the called status signal that is sent to the
originating exchange indicates the subscriber line is busy. The DMS switch
proceeds as it does with a normal busy line.
For coin lines originating calls over C1 trunks whose protocol does not
support service class or category COIN, the DMS switch sends the
appropriate calling category or service class based on the digits dialed.

NTXB10AA–6 297-1001-801i Standard 09.01 January 2000

 NTXB10AA
AJ0782
The DMS switch does not normally send the line signal ANSWER for calls
terminating on a line with the FNT option. With China C1 trunks whose
protocol does not support a called party status signal for free calls, the DMS
switch sends one of the C1 subscriber idle signals (not the line signal
ANSWER).
Feature AG0709 (Malicious Call Identification) provides malicious call
tracing using C1 and R2 register signaling.
For lines with NDC activated, originating non-toll calls over C1 trunks in
China, the DMS switch sends the service class signal II–4, which notifies the
terminating end that TBI and CWT should not be used on the call.
For lines with the PR1 and PR2 options, the calling category signal sent on
toll calls indicates the subscriber’s priority.
For operators originating calls over C1 trunks in China, the DMS switch
sends the service class signal II–1, indicating possible toll break-in.
Datafill
Table Description

ACCTTRTMT With this feature, these tables are used instead of tables
and TRTMTMFC and MFCTRTMT. Twenty-two new values are
TRTMTACT added to field ACTIVITY.

Table ACTTRTMT translates an activity received from an

incoming trunk to an extended treatment.

Table TRTMTACT translates a treatment to be applied to a

trunk into an R2 activity.
OFCVAR The office parameter TBI_RESTRICTED_ON_TOLL is
removed.
R2CLGSRV This table is used to map a forward signal received from an
incoming R2 signaling trunk into an index into table ITOPSERV.
This allows R2 signaling to interact with ITOPS positions in
DMS-200 and DMS-100/200 offices.

Field R2ACT (R2 signal activity) is changed. Twenty-eight

values are added to this field.

—continued—

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB10AA–7

NTXB10AA
AJ0782

Table Description (continued)

TRKGRP Fields PROTIDX and TRTMTIDX are used for China. Field
PROTIDX indicates the R2 protocol index C1 MFC trunks use.
Field TRTMTIDX indicates which index in tables ACTTRTMT
and TRTMTACT should be used for a particular trunk group.
TRTMTMFC These tables are no longer used by C1 MFC register signaling.
and
MFCTRTMT

End

Logs
The existing MFC trunk logs TRK312 and TRK313 report C1 MFC
reception and sending failure, respectively. This feature adds values that
represent incorrect peripheral module data mapping to the TRBLINFO field
of these logs.

NTXB10AA–8 297-1001-801i Standard 09.01 January 2000

NTXB10AA NTXB10AA
AJ0796 AJ0796
Feature name
Overlap Outpulsing for DMS-100I
Description
This feature implements overlap signaling in DMS-100 local and
DMS-100/200 local and toll switches for the following call types:
• originating toll and international calls
• transit toll and international calls in which the DMS-100/200 switch
provides international centralized automatic message accounting
(ICAMA)
• non-ITOPS operator-handled calls
• originating local calls
• tandem local calls where at least one of the involved trunks uses dial
pulse (DP) signaling
BCS history
This feature was created in BCS34.
Hardware requirements
Each international digital trunk controller (IDTC) can have a maximum of
two universal tone receiver (UTR) cards. Depending on existing trunk
provisioning, a second UTR card may be required if not provisioned.
Restrictions and limitations
Overlap signaling is not applicable to calls routed to multifrequency (MF)
trunks.
Overlap signaling is supported only for DP, R2, and multifunction peripheral
(MFP) register signalings.
Overlap signaling can be applied to R2 trunks that use link-by-link
signaling. It is not applicable to trunks using end-to-end or special
link-by-link signaling.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB10AA–9

NTXB10AA
AJ0796
Datafill
Table Description

TRKSGRP Field OVLP is added for both incoming and outgoing trunks.
Using this field, overlap signalling can be datafilled for a chosen
trunk subgroup.

DGCODE Selector COL2STEP is added and has the following

parameters:
· COLNREP, which specifies the number of routing digits to
be collected and reported to central control (CC)
· DGNAME, which specifies the type of digit analysis index
that will be applied

NTXB10AA–10 297-1001-801i Standard 09.01 January 2000

NTXB10AA NTXB10AA
AJ0819 AJ0819
Feature name
C1 MFC Trunk Implementation on Generic R2 System – XPM
Description
This feature, using the generic R2 system, implements the XMS-based
peripheral module (XPM) portion of the Chinese variant of the CCITT R2
signaling system known as C1. The signaling type used for this register
signaling is changed from NTRS09 to NTRS11. This feature, combined
with feature AJ0782 (C1 MFC Trunk Implementation on the Generic R2
System), replaces the implementation of C1 described in feature AG0711
(C1 Register Signaling).
BCS history
This feature was created in BCS30.
Feature interactions
AJ0819 requires feature AJ0782 (C1 MFC Trunk Implementation on the
Generic R2 System – CC).
Datafill
Table Description

RGSIGSYS Timers ICMXFTON, ICPSTCMP, and OGPREPLS are added to

define signaling type NTRS11. Timer CCMXDLAY (renamed
timer) has an increased value.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB10AA–11

NTXB10AA
AL2529
Feature name
R2 Billing Category Enhancements
Description
This feature implements the following R2 billing category enhancements:
• new line option Free Number Origination (FNO) to support free
subscriber calling
• modification of the processing of billing category to include free
subscriber calling, which allows the routing of unchargeable calls
through centralized automatic message accounting (CAMA) trunks
• display of the R2 billing category in international CAMA (ICAMA)
records
• display of free calls as a parameter of call information in international
call recording (ICR) and ICAMA records
BCS history
This feature was created in BCS34.
Restrictions and limitations
The FNO line option is not compatible with line options selective call
rejection (SCR), subscriber premises meter (SPM), attended pay station
(APS), and the line attribute Hotel/Motel (HOT).
Datafill
Table Description

FEATCHG Fields IFMKEY and FEAT are extended by adding the

parameter FNO.
LENLINES Field OPTLIST is extended by adding the parameter FNO.
R2CLGSRV Field R2ACT is extended by adding activities ORD_FREE,
PR1_FREE, PR2_DEMAND, PR2_HALL, and PR2_FREE.

Service orders
The FNO line option can be added, removed, or queried using service order
procedures.
Logs
In the AMAB160 log report, which is generated by the Automatic Message
Accounting Buffer (AMAB) subsystem, field R2 BILLING CATEGORY is
added. This field indicates the calling subscriber charging category.

NTXB10AA–12 297-1001-801i Standard 09.01 January 2000

 NTXB11AA
DP Register Signaling
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTXB11AA contents
Feature number Description

AG0707 C1 Line Signaling

AJ0498 NTRS05 Enhancements–II

BCS history
This feature package was created in BCS26.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX470AA International–Common Basic

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB11AA–1

NTXB10AA
AG0707
Feature name
CI Line Signalling
Description
This feature provides the required line signalling systems for trunk call
processing in DMS-100 and DMS-200 switches in China.
BCS history
This feature was created in BCS26.
Datafill
Table Description

LNSIGSYS One tuple is added for each new line signalling system.
TRKSGRP Data selector DIALSTART is extended to include the values
MANSWB and SASWB.

NTXB10AA–2 297-1001-801i Standard 09.01 January 2000

NTXB11AA NTXB11AA
AJ0498 AJ0498
Feature name
NTRS05 Enhancements – II
Description
This feature provides enhancements to the NTRS05 register signaling
system for DMS-100 and DMS-200 switches. The feature improves the
robustness and speed of the XMS-based peripheral module (XPM) call
processing software associated with dial pulse (DP) signaling. The
improvements associated with this feature also provide increased flexibility
in the specification of parameters for transmission and reception of DP
pulses.
BCS history
This feature was created in BCS29.
Datafill
Table Description

RGSIGSYS Parameter PPS is added. This parameter controls the number

of pulses sent each second.

Parameter OPLSDLAY is added. This parameter controls the

delay between seizure of the outgoing circuit and the start of
digit outpulsing.

Parameter FLTRTIME is added. This parameter determines the

minimum time a signal must be present for a make or break
condition to be recognized.

The range of values for parameter OSPCTBRK is increased.

This parameter controls the pulse break percentage.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB11AA–3

 NTXB12AA
ITOPS Local Basic
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTXB12AA contents
Feature number Description

AC0240 ITOPS Trunk Table Control and Setup Procedure

BCS history
This feature package was created in BCS25.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX056AA Enhanced Administration
NTX270AA New Peripheral Maintenance Package
NTX470AA International–Common Basic
NTX665AA Semi-permanent Connections–Basic
NTX667AA Printed Meter Check
NTX901AA Local Features I
NTX909AA ANI Toll
NTXB05AA ITOPS Common Basic
NTX472AA International–Local Basic (upgraded by NTX472AB)
or
NTX472AB International–Local Basic (upgrades NTX472AB)

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB12AA–1

NTXB12AA
AC0240
Feature name
ITOPS Trunk Table Control and Setup Processor
Description
This feature provides a new trunk group type for the International Traffic
Operator Position System (ITOPS) and implements the setup processor for
ITOPS call processing. The new trunk group type is used for incoming calls
to a DMS-200 office or a DMS-100/200 office that may terminate at an
ITOPS position.
This feature also adds two new line options to international loads. Option
HOT (hotel/motel) specifies that a line is a hotel or motel room line. Option
ONI (Operator Number Identification) specifies that a line always goes to an
ITOPS position, regardless of other information on the line.
BCS history
This feature was created in BCS25.
Restrictions and limitations
Line option HOT is incompatible with
• Call Diversion to Operator (CDO)
• Call Diversion to Subscriber (CDS)
• Call Diversion to Announcement (CDA)
• Call Diversion on Busy (CDB)
• Call Diversion Fixed (CDF)
• International Do Not Disturb (IDND)
• Subscriber Premises Meter (SPM)

Line option ONI is incompatible with SPM.

Only service classes STATION and HOTEL are supported.
Calls incoming over ITOPS trunks and not requiring an ITOPS position are
not routed out over metering (MTR) trunks.
Datafill
Table Description

TRKGRP Trunk group type ITOPS is added.

Service orders
Service orders for line options HOT and ONI are added.

NTXB12AA–2 297-1001-801i Standard 09.01 January 2000

 NTXB13AB
ITOPS Toll–Enhanced Queueing
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTXB13AB contents
Feature number Description

AG0636 ITOPS ICAMA Format

AG0712 ITOPS Screen Displays
AG0713 ITOPS Force Management System
AG0714 ITOPS Call Processing Key Functions
AG0715 ITOPS Supervisory Provisions
AG0716 ITOPS International Call Handling
AG1230 ITOPS: Assistance Monitor Capability
AG1233 ITOPS: APS Call Handling
AG1234 ITOPS: TBI Functionality
AJ0178 ITOPS: Routing Data Base
AJ0180 ITOPS: Assistance Paging Capability
AJ0182 ITOPS: Flexible Subscriber Number Display
AJ0572 ITOPS: Position Data Streamlining
AJ0801 ITOPS: Enhanced ACD (Queuing System)
AJ0802 ITOPS: Enhanced ACD (Call Processing)
AJ0803 ITOPS: TRAVER Capability
AJ0804 ITOPS: Booked Call Database Size Increase
AJ1024 ITOPS: Enhanced Queueing (Call Processing)

BCS history
This feature package was created in BCS25.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB13AB–1

NTXB13AB
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic

NTX470AA International–Common Basic

NTX657AA International CAMA
NTX665AA Semi-permanent Connections–Basic
NTXB05AA ITOPS Common Basic
NTXB84AA International Rating System

NTXB13AB–2 297-1001-801i Standard 09.01 January 2000

NTXB13AB NTXB13AB
AG0636 AG0636
Feature name
ITOPS ICAMA Format
Description
This feature provides international call detail recording for the International
Traffic Operator Position System (ITOPS) in the DMS-200 switch. The
feature covers the definition, collection, selection, formatting, and output of
calls involving an ITOPS operator in the DMS-200 international market.
ITOPS call detail recording interacts with the billing system and uses the
Device Independent Recording Package (DIRP) to output call details records
to tape or disk.
BCS history
This feature was created in BCS25.
Restrictions and limitations
Tables CRSMAP, CRSFMT, DIRPPOOL, and DIRPSSYS must be datafilled
in the order shown, to define the ITOPS data stream. A reload restart is
required to activate table CRSFMT.
This feature can only be used in DMS-200 international switches.
Datafill
Table Description

CRSMAP Option ITOPS is added to field KEY to specify the ITOPS call
record type. Stream ITOP is added to field STREAM to allow
ITOPS records to be sent to a different stream than for
international call recording (ICR) or international centralized
automatic message accounting (ICAMA).
CRSFMT Option ITOPFMT is added to field FORMAT to specify the
ITOPS format stream.
OVCAR Parameter GENERATE_ITOPS_LOG_ENTRY is added to
specify that an ITOPS log entry record is to be generated each
time an ITOPS record is created.

Logs
The following logs are created by this feature:
• The AMAB180 log report contains a detailed description of the call data
that is used to produce an ITOPS standard call entry record.
• The AMAB181 log report contains a detailed description of the call data
that is used to produce an ITOPS special billing extension record.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB13AB–3

NTXB13AB
AG0636
• The AMAB182 log report contains a detailed description of the call data
that is used to produce an ITOPS hotel billing extension record.
• The AMAB183 log report contains a detailed description of the call data
that is used to produce an ITOPS charge extension record.
• The AMAB184 log report contains a detailed description of the call data
that is used to produce an ITOPS charge adjustment extension record.
• The AMAB185 log report contains a detailed description of the call data
that is used to produce an ITOPS alternate route extension record.
• The AMAB186 log report contains a detailed description of the call data
that is used to produce an ITOPS database call extension record.
Automatic message accounting
The AMADUMP utility, which is used to print the contents of automatic
message accounting (AMA) files, is extended to allow ITOPS files to be
printed.

NTXB13AB–4 297-1001-801i Standard 09.01 January 2000

NTXB13AB NTXB13AB
AG0712 AG0712
Feature name
ITOPS Screen Displays
Description
This feature provides the mechanism for updating screen displays for
International Traffic Operator Position System (ITOPS) positions configured
as an
• operator position
• assistant position
• in-charge position

BCS history
This feature was created in BCS25.
User interface
The ITOPS operator position screen display has 55 fields. These fields
display call information such as call origination type, billing class, country
name, and calling subscriber’s number.
The ITOPS assistant position screen display has 26 fields of call
information. Fourteen of these fields are identical to those in the ITOPS
operator position screen.
The ITOPS position in-charge screen display has 42 fields of call
information. Twenty-five of these fields are identical to those in the ITOPS
operator and assistant screens.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB13AB–5

NTXB13AB
AG0713
Feature name
ITOPS Force Management System
Description
This feature provides the force management system (FM) for the
International Traffic Operator Position System (ITOPS). The FM provides
• information for provisioning of ITOPS operators
• indicators for overload and deflection conditions
• control of system and traffic features
• the hotel billing information center (HOBIC) system for hotel calls

The force management system is equipped with the following devices,

which are designed to assist ITOPS management personnel:
• The FADS TTY (Force Administration Data System teletypewriter) is
provided to manage the system as a whole. The FADS allows the FM to
display and modify system information and provides reports on system
performance every 15 min (if requested), 30 min, 6 h and 24 h.
• TADS TTY (Traffic Administration Data System teletypewriter) are
provided in each traffic office (TO) to assist the traffic office manager
(TOM). This device is equivalent to the FADS TTY except that periodic
reports are for the TO only.
• AQ TTY (Autoquote teletypewriter) are situated on premises such as
hotels and attended pay stations. Immediately following termination of a
guest toll call, call details are transmitted to the AQ TTY.
• The VQ TTY (Voice Quote teletypewriter) is located in the HOBIC. If
the AQ device is not present, the HOBIC operator telephones the hotel
and quotes call details verbally immediately following termination of a
guest toll call.
• The REC TTY (record teletypewriter) is located in the HOBIC. It
receives a copy of messages sent to the AQ TTY and VQ TTY, as well
as all other charge adjustment messages. TTY alarm messages and
measurements are not duplicated in the REC TTY.
• The HADS TTY (HOBIC administrative teletypewriter)
— allows HOBIC operators to enter ITOPS billing information to be
sent to the AQ, VQ, or REC TTYs
— allows HOBIC personnel to put AQ, VQ, or REC TTYs in service or
out of service
— receives hotel charge adjustment messages generated by ITOPS
operators
— receives TTY service alarm messages
— receives HOBIC operational measurements (OM) information

NTXB13AB–6 297-1001-801i Standard 09.01 January 2000

 NTXB13AB
AG0713
BCS history
This feature was created in BCS25.
Datafill
Table Description

CLASSTYPE This new table, along with CLASSNAM, associates a particular

class name with call types, to produce call classes.
OFCENG Office parameters ITOPS_LOW_TRAFFIC_START_TIME and
ITOPS_HIGH_TRAFFIC_START_TIME are added. These
parameters, which are datafilled by the operating company,
represent the start time for low and high traffic periods for the
office.
QT0L, QT1L, These new tables contain queue theshold values associated
QT2L, QT3L, with the related AWT. There is a direct correlation between
QT4L, QT5L, tuples in these tables and those in tables QTTIDXH and
QT0H, QT1H, QTTIDXL. QT0H to QT5H are high traffic tables and QT0L to
QT2H, QT3H, QT5L are low traffic tables. Data stored in these tables, along
QT4H, and with information on AWT, is used to determine if a call arriving
QT5H at an ITOPS switch is queued or deflected to announcement.
QTTIDXH and These new (queue threshold index) tables determine which set
QTTIDXL of call queue threshold values are used for traffic control during
the next 15 min. They contain average work time (AWT) values
datafilled by the operating company. QTTIDXH is for high traffic
and QTTIDXL is for low traffic.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB13AB–7

NTXB13AB
AG0714
Feature name
ITOPS Call Processing Key Functions
Description
This feature provides the key functions required to process ITOPS calls.
When a call is present at an ITOPS operator position, the operator can enter
data that allows the call to be processed and billed. The data is entered as a
sequence of keystrokes which invoke a key function procedure and initiate
the appropriate action.
BCS history
This feature was created in BCS25.
Datafill
Table Description

ITOPS Field FOREIGN is added. This field indicates whether a tuple is

foreign and is used to validate calling numbers incoming from
far-end operators.
IOGTKEY This new table is used by the key function procedure for the
OGT key. One key stroke of the OGT key causes a predefined
number to be retrieved and outpulsed.
IOPRTRAN This new table is used by the key function procedure for those
keys that require the operator to enter CLG and CLD numbers
that are used for outpulsing.
ITOPTRBL This new table is used by the key function procedure for the
TRBL key. The TRBL key inputs a trouble code to the system.

Logs
The following new trouble reporting logs are created by this feature:
• The ITOP104 log report is generated when an operator enters a trouble
code using the TRBL key, if the trouble digits entered map to an MTCE
entry in table ITOPTRBL.
• The ITOP105 log report is generated when an operator enters a trouble
code using the TRBL key, if the trouble digits entered map to an
MTCEMIN entry in table ITOPTRBL.
• The ITOP106 log report is generated when an operator enters a trouble
code using the TRBL key, if the trouble digits entered map to an
MTCEMAJ entry in table ITOPTRBL.

NTXB13AB–8 297-1001-801i Standard 09.01 January 2000

NTXB13AB NTXB13AB
AG0715 AG0715
Feature name
ITOPS Supervisory Positions
Description
This feature provides the following capabilities to International Traffic
Operator Position System (ITOPS) assistant and in-charge positions:
• processing answer-assistance requests from operators
• establishing forward connections
• viewing calls in the delay call database
• displaying traffic office (TO) status

If an ITOPS operator requires assistance on a call, the operator can request

assistance from an assistant position. If an assistant position is not available,
depending on the type of request (general or directed) and the availability of
ITOPS positions, the request is routed to
• reorder
• another assistant position in the same TO
• the in-charge position in the same TO
• an assistant or in-charge position in another TO
• a queue to wait for an available assistant position

BCS history
This feature was created in BCS25.
Restrictions and limitations
Each ITOPS office can support one in-charge position and a maximum of
126 assistant positions.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB13AB–9

NTXB13AB
AG0716
Feature name
ITOPS International Call Handling
Description
This feature implements the International Traffic Operator Position System
(ITOPS)
• delay call database and associated key functions
• delayed call database administration teletypewriter (DADS TTY) device
and associated commands
• alternate routes and associated key functions
• MEMO key function

The delay call database stores details of international calls that cannot be
processed immediately. This database is administered through the DADS
TTY device. The ITOPS operator can retrieve a stored call, modify the
information for a stored call, or delete a stored call entry.
The DADS TTY device can generate reports of calls that have been operator
deleted or mass (system) deleted.
This feature allows the ITOPS operator to use alternate routes to complete a
call or reach an operator in a foreign country, when it is not possible to do so
using a direct route.
The MEMO key is used by an ITOPS operator to add up to 64 characters of
text to a call. The memo text is stored in the delay call database and can be
erased or retrieved by the ITOPS operator.
BCS history
This feature was created in BCS25.
Restrictions and limitations
The delay call database can accommodate a maximum of 1280 delayed calls.
The customer can define a limit (1 to 50) for delayed calls scheduled to be
re-presented to the ITOPS operator.
The process of mass call deletion removes unprocessed calls in the delay call
database that are older than the limit that can be set by the customer of
1 to 7 days.

NTXB13AB–10 297-1001-801i Standard 09.01 January 2000

 NTXB13AB
AG0716
Datafill
Table Description

IALTRTE This new table maps alternate routes to the numbers that are
outpulsed to reach alternate routes.
ICNTRY This new table contains all the information that is unique to a
particular country.
IDBCLASS This new table maps the class number (entered using the DB
CLASS key) to a screen display.
IDORDA This new table contains the directory assistance number based
on country and city codes.
IFORINW This new table contains the inwards numbers based on country
and city codes. Inwards numbers are the country codes, city
codes, and inwards operator codes used to route a call through
an operator in a country other than the country where the call
originated.

Logs
The following new logs are created by this feature:
• The ITOP108 log report is generated when a system-correctable internal
software error occurs in the delay call database code.
• The ITOP109 log report is generated when the delay call database
software suspects a corruption of its internal data. If this log is
generated, an audit is scheduled to verify the corruption.
• The ITOP110 log report is generated when the delay call database
software finds a corruption in its internal data. If this log is generated,
the system attempts to rebuild the corrupted software.
User interface
The following commands are available in the DADS TTY device:
• DQ - display a delay call database entry
• DD - delete a delay call database entry
• DT - display the current settings for the delay call database thresholds
• DC - change the delay call database threshold for the number of calls
• DP - turn the printing of deleted calls ON or OFF
• DB - print a subset of the calls in the delay call database
• DM - set and display the mass deletion period
• DV - display the number of calls for each country
• DO - display the number of calls that have been in the delay call
database longer than the specified period

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB13AB–11

NTXB13AB
AG0716
The following keys are associated with alternate routes:
• The Alt Rte key is used by the ITOPS operator to access the alternate
route list for a given country.
• The DA and INW keys are used by the ITOPS operator to indicate that
foreign directory assistance (DA) or inwards assistance (INW) is
required for a call. These keys are used in conjunction with the FOR
key.

NTXB13AB–12 297-1001-801i Standard 09.01 January 2000

NTXB13AB NTXB13AB
AG1230 AG1230
Feature name
ITOPS: Assistance Monitor Capability
Description
This feature provides administrative positions in the International Traffic
Operator Position System (ITOPS) with monitor capability. Monitor
capability allows ITOPS administrative positions to observe screen displays
and listen to headset conversions of an operator position in the same traffic
office (TO).
There are two types of administrative position: assistant and in-charge. The
assistant position is used to provide assistance to operator positions. The
in-charge position can provide the same assistance as the assistant position
and can display real-time measurements of the functioning of the TO.
BCS history
This feature was created in BCS27.
Restrictions and limitations
The monitor function is available to assistant and in-charge positions only.
When starting a monitor session, the assistant and in-charge positions must
be in the POS BUSY state and must not have any active calls.
The following restrictions apply to a monitor session:
• The floor plan number and operator number must correspond to
positions that are logged in.
• The operator position to be monitored must be in the same TO as the
position making the monitor request.
• The position to be monitored must not be an assistant or in-charge
position.
• The position to be monitored must not already be monitored.
• A three-port conference bridge must be available.
• Network connections between the monitoring and monitored positions
must be available.
During a monitor session, all keystrokes at the assistant or in-charge
positions, except the MON (end monitor session) key, are ignored.
The monitoring position can listen to the monitored position only if the
monitored position is connected to a three-port conference bridge. The
monitoring position cannot hear the monitored position if the monitored
position is idle. A monitor session ends if the headset of the monitored
position is unseated or if the monitored position is taken out of service.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB13AB–13

NTXB13AB
AG1233
Feature name
ITOPS: APS Call Handling
Description
This feature provides
• Autoquote (AQ) billing capabilities for the International Traffic Operator
Position System (ITOPS) hotel billing information center (HOBIC)
• attendant pay station (APS) call handling for ITOPS

HOBIC currently contains HOBIC administrative (HADS) printers, voice

quote (VQ) printers, and record (REC) printers. This feature adds AQ
printers to HOBIC.
HOBIC currently handles hotel calls. This feature allows HOBIC to handle
APS calls.
The AQ printer message contains information such as message count,
calling number, called number, date, time, call duration, charges, taxes, room
or booth identification, and the name of the paying party.
This feature allows HOBIC operators to enter billing credits to an AQ
printer or to a VQ printer. Also, billing data for calls that cannot be handled
automatically by ITOPS can be sent to AQ hotels.
If there is an AQ printer at a hotel or APS, all messages pertaining to the
hotel are routed to the AQ printer. If there is no AQ printer, the message is
sent to the VQ printer. In this case, an operator can call the hotel or APS
and supply the billing information. A copy of all messages routed to an AQ
or VQ is sent to the REC printer.
BCS history
This feature was created in BCS27.
Hardware requirements
The following facilities are required for each AQ device;
• one slot in the international digital trunk controller (IDTC)
• one channel on the channel bank
• one digital modem

NTXB13AB–14 297-1001-801i Standard 09.01 January 2000

 NTXB13AB
AG1233
Datafill
Table Description

DNRTEID The range of field DVCRTE is changed from 1–12 to 1–999.

Devices AQHOT and VQHOT are added to field DEVICE.

These devices indicate what type of device a hotel call is routed
to.
ITOPSDEV Field NOCHG is added to specify that no charge reports are to
be printed. The hotel acronym is removed for AQ devices.
OFCENG Office parameter TOPS_FIXED_DURATION_APS is added to
indicate a closed APS, as opposed to an open APS.

Automatic message accounting

When an APS call is completed, an automatic message accounting (AMA)
ITOPS call detail record is printed if the office parameter
GENERATE_ITOPS_LOG_ENTRY is set to Y. An ITOPS charge
extension record is also produced.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB13AB–15

NTBX13AB
AG1234
Feature name
ITOPS: TBI Functionality
Description
This feature allows an International Traffic Operator Position System
(ITOPS) operator to access the Toll Break-in (TBI) feature located in a
DMS-100 switch (local office).
In countries where toll circuit availability is limited, it is common for toll
calls to be booked. When an operator attempts to set up a booked call, one
or both of the subscribers may be involved in other calls. TBI allows the
operator to interrupt a call and offer a toll call to one of the subscribers.
BCS history
This feature was created in BCS27.
Restrictions and limitations
This feature requires the TBI feature in the local office.
The TBI feature functions according to the TBI parameters datafilled in the
local office.
This feature requires a trunk that can handle the TBI signal.
Calling party number verification does not work if the local office prohibits
TBI on toll calls.
Calling party number verification is available only for R1 signaling.
Automatic TBI is available only with NTLS20 trunks.
Automatic message accounting
ITOPS produces call detail records for billing purposes. These records
contain a standard call details billing record and six types of extension
records. Information digits are part of the standard call details billing
record.
This feature affects information digit 6. This digit indicates whether the
operator used TBI to verify the calling party number and whether the call
was a trunk offering (TBI) call.

NTBX13AB–16 297-1001-801i Standard 09.01 January 2000

NTXB13AB NTXB13AB
AJ0178 AJ0178
Feature name
ITOPS: Routing Database
Description
This feature provides the ability to queue calls on an outgoing route (trunk
group) using the delay call database. Booked calls or calls that cannot be
routed because trunks are unavailable are queued in the delay call database.
When a member of the required trunk group becomes available, it is held
and the route queued call is retrieved and directed to the International Traffic
Operator Position System (ITOPS) position. The call is then sent over the
held trunk.
This feature continues the implemention of the routing database, which is
method of storing calls in the ITOPS database that are waiting for an
outgoing trunk in a specific trunk group.
BCS history
This feature was created in BCS28.
Restrictions and limitations
The ITOPS routing database supports route queueing against the outgoing
trunk for the called party. There is no requirement to reserve a trunk to
reach the calling party.
The ITOPS routing database does not support route queueing over two-way
trunk groups. The routing database allows queueing only on a trunk group
that has type SIGSYS signaling and a selection sequence of most idle or
least idle.
Route queued calls cannot be stored if the call has a called party (including
treatments). The called party must be released before the call can be route
queued. This restriction does not apply to untimed or timed database calls.
Lines originating from a coin station are not allowed to route queue.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB13AB–17

NTXB13AB
AJ0178
Datafill
Table Description

IDBCLASS Field ROUTE is added. This field indicates whether database

calls are queued against an outgoing route or are assigned a
delay time for recall.

OFCENG Office parameter MAX_ROUTE_QUEUED_PER_TRKGRP is

added. This parameter specifies the maximum number of calls
that can be queued on an outgoing route.

Office parameter TOTAL_ROUTE_QUEUED_CALLS is added.

This parameter determines the number of call queue elements
to allocate on restarts.

NTXB13AB–18 297-1001-801i Standard 09.01 January 2000

NTXB13AB NTXB13AB
AJ0180 AJ0180
Feature name
ITOPS: Assistance Paging Capability
Description
This feature provides the International Traffic Operator Position System
(ITOPS) administrative positions with paging capability. Paging capability
allows assistant and in-charge positions to page a specific operator and
request that the operator call them back. The paged operator can ring the
administrative position by originating a directed set call to that position.
BCS history
This feature was created in BCS28.
Restrictions and limitations
The following limitations apply to this feature:
• Paging is not available at the operator position.
• An assistant or in-charge position can have only one page at a time
active. If a new page is entered, the existing page is erased.
• Only one assistant or in-charge position at a time can page a given
operator.
• If the operator monitor is initiated from an assistant position, any
existing page is erased from both positions.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB13AB–19

NTXB13AB
AJ0182
Feature name
ITOPS: Flexible Subscriber Number Display
Description
This feature provides the capability to define the format for displaying
calling and called numbers on the International Traffic Operator Position
system (ITOPS) screen and on ITOPS devices. Formatting involves the
insertion of dashes into calling and called numbers to separate the numbers
into logical components such as area code, office code, and directory
number.
BCS history
This feature was created in BCS28.
Restrictions and limitations
The size of a number after formatting cannot exceed 18 characters.
Formatted numbers exceeding this maximum contain only as many dashes
as the 18-character maximum permits.
A formatted number can contain a maximum of four dashes.
Since the delayed call database administration (DADS) device does not
format calling and called numbers, it is not affected by this feature.
Datafill
Table Description

NUMBFMT This new table is used to format numbers on the basis of the
type of number (calling or called) and the digits in the number.

NTXB13AB–20 297-1001-801i Standard 09.01 January 2000

NTXB13AB NTXB13AB
AJ0572 AJ0572
Feature name
ITOPS: Position Data Streamlining
Description
This feature improves the efficiency of International Traffic Operator
Position System (ITOPS) access to the operator position.
BCS history
This feature was created in BCS29.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB13AB–21

NTXB13AB
AJ0801
Feature name
ITOPS: Enhanced ACD (Queueing System)
Description
This feature provides a simple, flexible, real time Automatic Call
Distribution (ACD) system for operator services. The feature includes
• queueing and selection procedures for calls and idle operators
• force management (FM) command and report modifications

If there are no idle operators capable of handling a call when it arrives, the
call is placed in the appropriate queue. Each call queue has a priority
(0 to 5, with 0 being the highest priority), a grade of service (10 to 80), and
list of call classes associated with it. The grade of service is the factor used
to age a call when determining the oldest call in a priority level. Calls in
each queue are processed on a first-in-first-out basis.
When a call is to be placed in a queue, the time the last call waited in the
queue before processing is used to determine if the call is placed in the
queue or deflected to treatment.
When an operator becomes idle, the call queues are checked for a call that
the operator can handle. Each queue is checked in order of priority until a
call is found. If there is more than one call queue with the same priority, the
age and grade of service of the first call in each queue are used to select a
call for routing to the idle operator.
BCS history
This feature was created in BCS31.
Restrictions and limitations
The call transfer Force Administration Data System (FADS) message is
eliminated from FM reports.
User interface
The new, modified, or deleted commands listed below are FM commands
entered from Traffic Administration Data System (TADS) or FADS devices.
If the international traffic operator position system (ITOPS) contains only
one traffic office, a System Administration Data System (SADS) device is
used.

NTXB13AB–22 297-1001-801i Standard 09.01 January 2000

 NTXB13AB
AJ0801
The following information request commands are modified:
• The command L generates a list of operators currently logged in, their
positions, and their call handling capabilities.
• The command P generates a list of the current position status on a
system-wide and traffic office basis. Headers OC1, MB1, OC2, and
MB2 have been removed from this report.
The operator study data system collects productivity and efficiency data on
up to 64 operators in an office. The following commands in this system are
modified:
• The command RR releases study registers assigned to an operator and
prints the study data collected.
• The command RD generates a list of the specified operator’s
accumulated study data without releasing the assigned study registers.
The operator call handling capabilities commands enable a supervisor to
alter the call handling capabilities of an operator. The following new
commands are added:
• The command CI is used to include the specified call queues in the
specified operator’s call handling capabilities.
• The command CX is used to remove the specified call queues from the
specified operator’s call handling capabilities.
• The command CN returns the specified operator to normal call handling
capabilities.
• The command C generates a list of all operators or the specified operator
and the operator’s call handling set.
Controlled traffic allows the call classes of some operators to be limited.
Controlled traffic is meant to be a training facility. The following
commands are modified:
• The command TI includes the specified call classes in a specified
operator’s call handling capabilities.
• The command TX includes the unspecified call classes in a specified
operator’s call handling capabilities.
• The command TN returns the specified operator to normal call handling
capabilities.
• The command T generates a list of all the operators or the specified
operator in controlled traffic mode along with the operator’s controlled
traffic set.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB13AB–23

NTXB13AB
AJ0801
Queue threshold tables are used to determine when call waiting and call
deflection are in effect. The following commands, which are used to request
information on a queue threshold table or to modify the queue threshold
data, are modified:
• The command AQ prints the threshold values and time periods for the
specified call queue.
• The command AC changes the threshold values for the specified queue
for the current time period.
• The command AR restores all threshold values for the specified queue to
their previous values.
Call transfer allows some operators to transfer calls to other operators in the
same ITOPS office. Up to two call transfer queues can be used. The
following FM call transfer commands are invalidated:
• The command XA activates one or both of the call transfer types.
• The command XD deactivates one or both of the call transfer types.
• The command XI enables the specified operator to receive transferred
calls from other operators in the same traffic office.
• The X command prints a list of transfer operators and the call types they
are eligible to receive.

NTXB13AB–24 297-1001-801i Standard 09.01 January 2000

NTXB13AB NTXB13AB
AJ0802 AJ0802
Feature name
ITOPS: Enhanced ACD (Call Processing)
Description
This feature provides the customer datafillable tables required for the call
queuing interface in the Automatic Call Distribution (ACD) system for the
International Traffic Operator Position System (ITOPS). These tables
control the routing of calls to operator service positions or to call waiting
queues.
This feature provides a simple, efficient, and flexible call queueing system
that queues calls on the basis of call attributes, properties, and classes.
Call attributes are the physical and functional details of a call. For example,
physical attributes include whether the call is a hotel or a coin call and
functional attributes include whether the call is booked in the call database
or is recalled to the operator.
A call property is a grouping of call attributes in a configuration that makes
each property independent of any other property. The defined properties in
this queueing system are call origination, service class, recall, and foreign.
An example of the contents (attributes) of a property such as service class is
station, hotel, coin, and attendant pay station.
A call class is a set of attributes from each of the call properties that is used
to separate calls into different queues. When a call is routed to operator
services, it must be placed in a call class. The call class is determined by the
attributes in the different properties in the call.
BCS history
This feature was created in BCS31.
Datafill
Table Description

QCLASS This new table is used to assign a call class to a call.

QDEF This new table is used to define the mapping of call classes to
call queues.
QPROFILE This new table is used to map call queues to positions and
operators.

—continued—

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB13AB–25

NTXB13AB
AJ0802

Table Description (continued)

QPROP This new table is used to define call properties and the
attributes within each property. Only attributes defined in this
table can be used to datafill the remaining queueing tables
below.

End

Restrictions and limitations

In table QPROP, the maximum number of definable properties is 8 and the
maximum number of definable attributes in each property is 16.
In table QCLASS, the maximum number of definable call classes is 256 plus
one default call class. If a call arrives that does not match any of the defined
call classes, the call is assigned to the default call class 0. Since all operators
are datafilled to handle the default call class 0, this ensures that all calls
arrive at an operator.
In table QDEF, the maximum number of definable call queues is 63. Call
queue 0 is reserved for calls with the default call class 0 and any other call
classes not associated with the current mapping of call classes to call queues.
Call queue 0 has the lowest priority and grade of service.
In table QPROFILE, the maximum number of operators is 2048 and
positions is 2048.

NTXB13AB–26 297-1001-801i Standard 09.01 January 2000

NTXB13AB NTXB13AB
AJ0803 AJ0803
Feature name
ITOPS: TRAVER Capability
Description
This feature allows translation verification (TRAVER) to access
International Traffic Operator Position System (ITOPS)-specific datafill.
This access makes it possible to
• verify the routing and translations when the originator is an ITOPS trunk
• access and display the required tuple in table ITOPS when routing
through this table is specified
TRAVER is a low-level diagnostic tool that checks the routing and
translations given to an originator (line or trunk) and to dialed digits.
TRAVER, which is designed to be used for debugging datafill, translates
digits to a destination in a manner similar to that used to translate digits
during actual call processing in a DMS switch.
BCS history
This feature was created in BCS30.
Restrictions and limitations
TRAVER using an ITOPS position as an originator is not supported.
Table ITOPS cannot be specified as a routing table when the R selector is
used in TRAVER. Using the R selector with the TRAVER command
specifies the originator as a routing table. Specifying routing table ITOPS is
not necessary because table ITOPS does not cause a call to be routed to
another translation table. All calls that access table ITOPS are routed to an
ITOPS position.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB13AB–27

NTXB13AB
AJ0804
Feature name
ITOPS: Booked Call Database Size Increase
Description
This feature increases the maximum number of calls that can be stored in the
delay call database from 1280 to 5120.
BCS history
This feature was created in BCS30.
Restrictions and limitations
This feature requires 0.8 megawords of data store.
When using the electronic data transfer (EDT) process to move from a
database larger than 1280 calls to a smaller database, only 1280 calls are
transferred. The other calls are lost.
Datafill
Table Description

OFCENG Office parameter DB_MAX_SIZE is added. Office parameter

TOTAL_ROUTE_QUEUED_CALLS is limited to the value
datafilled for DB_MAX_SIZE.

NTXB13AB–28 297-1001-801i Standard 09.01 January 2000

NTXB13AB NTXB13AB
AJ1024 AJ1024
Feature name
ITOPS: Enhanced Queueing (Call Processing) II
Description
This feature is the concluding portion of the enhanced Automatic Call
Distribution (ACD) system. The other features that are part of the ACD
system are AJ0801 (ITOPS: Enhanced ACD [Queueing System]) and
AJ0802 (ITOPS: Enhanced ACD [Call Processing]). This feature
implements the tables required for call properties, call classes, call queues,
and operator and position queue handling profiles.
The enhanced ACD system takes calls destined for operator services,
analyzes the call properties, and assigns the calls to the appropriate operator
or call queue.
This feature provides the following parts of the enhanced ACD system:
• changes to the transfer key function
• new routing table ITOPATTR and modifications to tables QTHRESH,
ITOPS, QPROP, and QCLASS
• new queueing system office parameters
• force management (FM) command modifications
• changes to International Traffic Operator Position System (ITOPS)
screen displays
In the enhanced ACD system, the transfer key allows the operator to
manually assign attributes to a call. These attributes allow the call to be
transferred to another call queue when the call is released from position.
BCS history
This feature was created in BCS31.
Restrictions and limitations
When no automatic number identification (ANI) is given for a number, the
index into table ITOPSERV is not available, the service class for the call is
not known, and the call is routed to the default service class.
When the enhanced ACD is activated, the following commands have no
effect:
• transfer commands XA, XD, XI, and X
• operator-system data study commands RA, RD, RQ, RR, and RT
• queue threshold commands AD, AM, AQ, and AX

Overwriting of call attributes by the transfer key is not allowed for the
following properties: call origination, service class, and recall.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB13AB–29

NTXB13AB
AJ1024
Datafill
Table Description

OFCENG The following office parameters are added:

· ITOPS_ENHANCED_ACD controls which queueing system
is activated.
· OS_NUM_CALL_QUEUES controls the number of call
queues used to queue calls in the enhanced ACD system.
· OS_NUM_POSITIONS defines the number of operators in
an office at a given time.
· OS_CT_SEARCH_DEPTH defines the number of positions
that are searched in the controlled traffic position queue to
look for an operator who can handle an incoming call.
· OS_CALLS_WAITING_QUEUE_SIZE defines the number
of calls allowed in the system at a given time.
ITOPATTR This new routing table is used to add attributes to a call to
further define what call class the call belongs to, which queue
the call belongs in, and which operators should handle the call.
ITOPS Field ATTRIDX is added. This field is used to index into table
ITOPATTR. Field POSTYPE is removed.
QCLASS Field QCLASKEY is added to map a class name to a number.
This field is added at the key position of the tuple. The
QCLASKEY index value is used to reference a specific call
class from FM.
QPROP Property Special is added. The attributes associated with
property Special are added by referencing the tuple in table
ITOPATTR that contains these attributes. Referencing is done
from table ITOPS or using the transfer key.
QTHRESH This new table controls the threshold limits for call queues. This
table can be datafilled by the operating company and sets time
limits for
· call waiting on
· call waiting off
· calls deflected

User interface
On the in-charge position screen, the position status information is changed
to remove fields that are unnecessary in the enhanced ACD system.

NTXB13AB–30 297-1001-801i Standard 09.01 January 2000

 NTXB13AB
AJ1024
The following information request commands have been modified:
• The command L generates a printed list of operators currently logged in,
the positions the operators occupy, and the operators’ call handling
capabilities.
• The command P generates a printed list of current position status on a
system-wide and traffic office basis.
The controlled traffic commands enable selected operators to handle a
limited number of call classes. An operator in controlled traffic can handle
up 16 call classes (as opposed to the maximum of 255) that are datafilled in
table QCLASS. Controlled traffic is intended to be a training facility. The
following commands are modified:
• The command TI includes the specified call classes in the specified
operator’s call handling capabilities.
• The command TN returns the specified operator to normal call handling
capabilities.
• The command T lists all operators in controlled traffic mode and lists the
operators’ controlled traffic sets.
The queue threshold command Q is used to display the following
information for all call queues or for specified call queues:
• average waiting time for calls in queues
• the number of calls queued
• whether call waiting is on or calls are being deflected

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB13AB–31

 NTXB14AA
China Local Basic
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTXB14AA contents
Feature number Description

AG0710 Toll Break-in for China–DMS-100

AL2528 ILR Enhancements

BCS history
This feature package was created in BCS26.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX270AA New Peripheral Maintenance Package
NTX470AA International–Common Basic
NTX478AA CCITT PCM (30+2) Digital Signaling and Maintenance
NTX492AA Operator Toll Break-in
NTX661AA International Feature Processing Environment (FPE)
NTX901AA Local Features I
NTX904AA R2 Signaling Base
NTXB10AA China Common Basic
NTX472AA International–Local Basic (upgraded by NTX472AB)
or
NTX472AB International–Local Basic (upgrades NTX472AA)

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB14AA–1

NTXB14AA
AG0710
Feature name
Toll Break-in for China – DMS-100
Description
Toll Break-in (TBI) allows an operator to interrrupt a call between two
subscribers to a connect another call to one of the subscribers. The
interruption can be
• operator-initiated using a TBI key, or
• automatic

When an operator attempts to set up a booked call, one or both of the

subscribers may be involved in other calls. TBI allows a call originating or
terminating in a local office to be interrupted and a toll call offered to one of
the subscribers.
BCS history
This feature was created in BCS26.
Hardware requirements
The TBI feature requires the NT3X67BB (conference circuit with TBI tone)
card, which provides a TBI tone during a TBI confence call.
Restrictions and limitations
TBI is allowed only on local voice calls. The TBI call must be line-line,
line-trunk, trunk-line, or line-tone. The subscriber in a TBI call cannot be
connected to an announcement, dialing, or ringing.
TBI is not applicable to subscribers classified as
• data lines
• especially important subscribers

Feature interactions
AG0710 requires feature BC2265 (International Toll Break-in) and feature
AE0244 (Toll Break-in – Background Tone).
This feature interacts with the features listed below.
• Call Diversion (CDIV) features Call Diversion to Announcement
(CDA), Call Diversion on Busy (CDB), Call Diversion Fixed (CDF),
Call Diversion to Operator (CDO), and Call Diversion to Subscriber
(CDS). Operator trunks are not diverted. This allows TBI to take
precedence over all CDIV features.
• If Call Waiting (CWT) is activated in the near-end call, TBI is denied. If
TBI is activated, CWT is denied.

NTXB14AA–2 297-1001-801i Standard 09.01 January 2000

 NTXB14AA
AG0710
• Coin lines (Coin). For interoffice calls, TBI is denied if the subscriber
that the operator is trying to reach is Coin and is the originator of the
call. For intraoffice calls, TBI is denied if the originating party is Coin.
• Denied features TBI is successful if the subscriber in a TBI call has any
of the denied features. The denied features are Denied Termination
(DT), Plug Up (PLP), and Suspended Service (SUS).
• Free Number Terminating (FNT). For interoffice calls, if the subscriber
in a TBI call is the terminating party and has FNT, the call must be
answered for TBI to be allowed. For intraoffice calls, the call must be
answered for TBI to be allowed.
• Hunt groups Circular Hunt Group (CIR), Distributed Line Hunting
(DLH), Directory Number Hunting (DNH), Multiline Hunting (MLH),
Stop Hunt (SHU), and Bridge Night Number (BNN). Hunting takes
precedence over operator-handled calls. If all lines are busy, TBI is
applied to the called party. If a member of a hunt group has CDIV
activated, hunting is stopped. An operator-handled call attempts to
terminate on the member with CDIV activated.
• TBI is denied if International No Double Connect (INDC) is activated.
• Malicious Call Trace (MCT) takes precedence over TBI if the call is in a
conference state.
• TBI cannot be performed on a semipermanent connection (SPC).
• If Three-way Calling (3WC) is activated, TBI is denied. If TBI is active,
3WC is denied and the operator gets a reorder treatment.
• If Six-way Calling (6WC) is activated, TBI is denied. If TBI is active,
6WC is denied and the operator gets a reorder treatment.
• If TBI is activated, no Subscriber Activation procedures are initiated. If
Subscriber Activation procedures are in progress, TBI is denied.
• Subscriber Premises Meter (SPM). For interoffice calls, TBI is denied if
the subscriber in a TBI call is the originator of the call and has SPM
activated. For intraoffice calls, TBI is denied if the originating party has
SPM.
• If a TBI is in effect, a subsequent TBI is denied.
• TBI is denied if a Wake Up Call (WUC) to announcement is in progress.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB14AA–3

NTXB14AA
AG0710
Datafill
Table Description

OFCAR Office parameter TBI_FORCE_RELEASE is added. This

parameter allows the operating company to determine if the
operator can force release one of the subscribers in a TBI call.

Office parameter TBI_OFFER is added. If this parameter is

datafilled as AUTOMATIC, the TBI feature is offered
immediately when an operator dials a subscriber that is
subscriber busy. If the parameter is datafilled as MANUAL, the
operator must press the force break and re-ring key to initiate
TBI.

User Interface
At the trunks test position (TTP) level of the MAP (maintenance and
administration position) display, the command TBI is used to test TBI.

NTXB14AA–4 297-1001-801i Standard 09.01 January 2000

NTXB14AA NTXB14AA
AL2528 AL2528
Feature name
ILR Enhancements
Description
This feature enhances the International Line Restrictions (ILR) function in
order to implement ILR subscriber control sequences compliant with
Chinese TS-01.
Subscriber control sequences allow a subscriber to activate or deactivate call
restrictions on their line. When a subscriber activates or deactivates a
restriction, a password must be entered. The user can also query the status
of restrictions on their line.
BCS history
This feature was created in BCS34.
Restrictions and limitations
Only one restriction can be placed on a line at a given time. An existing
restriction must be removed before placing another restriction on a line.
Datafill
Table Description

OFCOPT Office parameter ILR_OPTIONS is added. This parameter has

two fields: ACTIVATION_SEQUENCE and
DEACTIVATION_SEQUENCE. When these fields are set to
CR_PSWD, the user enters the call restriction then the
password, during both activation and deactivation. ILR control
sequences are compliant with Chinese TS-01 when the
ILR_OPTIONS fields are set to CR_PSWD.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB14AA–5

 NTXB17AA
Attendant Pay Station Local
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTXB17AA contents
Feature number Description

AG1291 Attendant Pay Station II

BCS history
This feature package was created in BCS26.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX056AA Enhanced Administration
NTX470AA International–Common Basic
NTX901AA Local Features I

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB17AA–1

NTXB17AA
AG1291
Feature name
Attendant Pay Station II
Description
This feature extends the capabilities introduced in feature AG1108 (Initial
Attendant Pay Station Offering for China) and feature AG0957 (Selective
Charge Recording).
Attendant Pay Station Offering (APS) allows all lines in a service hall to
route call details records to a specific output device. Existing APS call
details records indicate charges for direct dialed local calls. With this
feature, APS call details records indicate charges for all direct dialed toll
calls originating at service halls.
Selective Charge Recording (SCR) allows customers to have charges quoted
to them on call completion. With this feature, the SCR call details record
matches the APS call details record format, and call charges are explicitly
stated.
With this feature, call details records for APS and SCR can be routed to a
hotel billing information center (HOBIC) device, in addition to the existing
routing to log devices. A call details record is produced on call completion.
APS call details records are routed to two types of devices:
• Auto Quote (AQAPS) is a printer at a service hall. The AQAPS receives
call details records for all calls originating at the hall.
• Voice Quote (VQAPS) is a printer located at the central office or
HOBIC. The VQAPS receives call details records for direct dial calls
that do not have an AQAPS route. Service hall attendants must have the
charges quoted to them on call completion.
BCS history
This feature was created in BCS27.
Restrictions and limitations
The following HOBIC-related restrictions apply:
• HOBIC supports a maximum of 512 auto quote (AQ) devices for each
office. However, any AQAPS that has a device route number greater
than 12 defaults to the voice quote (VQ) device.
• Only one VQAPS is supported for each office.
• Only two REC printers are supported for each office.
• Only one HOBIC administrative (HADS) teletype (TTY) device is
supported for each office, with a maximum queue length of 10.

NTXB17AA–2 297-1001-801i Standard 09.01 January 2000

 NTXB17AA
AG1291
Datafill
Table Description

OFCAR Office parameter CALL_REPORT_FORMAT is added. If this

parameter is set to HOBIC, the APS call details record is in the
HOBIC records format. Otherwise, the default value LOG is
presumed and the log record format is used.

Logs
Log reports APS100 to APS112 are generated at the completion of each toll
call that used the log system to print the billing record.
An SCR100 log is generated at the completion of each toll call that used the
log system to print the billing record.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB17AA–3

 NTXB21AA
Co-existence (Trunk Type)
This feature package applies to DMS-300 offices.
NTXB21AA provides co-existence software to enable International Traffic
Operator Position System (ITOPS) functionality in a DMS-300 SuperNode
switch. Co-existence software enables international and domestic (North
American) call processing to run in parallel.
This feature package provides originating and terminating test line functions
that invoke the appropriate test line agency according to trunk type.
Feature package contents
Feature package NTXB21AA contents
Feature number Description

AE0481 Test Lines for the Co-existence Switch

AE0523 Japan 300 SuperNode and ITOPS Compatibility

BCS history
This feature package was created in BCS29.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX470AA International–Common Basic
NTX660AA International Feature Processing Environment (FPE)
NTX483AA International 101 Communication Test Line (upgraded by
NTX483AB)
or
NTX483AB International 101 Communication Test Line (upgrades
NTX483AA)

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB21AA–1

NTXB21AA
AE0481
Feature name
Test Lines for the Coexistence Switch
Description
This feature ensures that, in a coexistence environment, originating and
terminating test line functions invoke the appropriate test line agency
according to trunk type (international or domestic). Coexistence involves
having international and domestic call processing run in parallel.
Both international and domestic (North American) trunks are supported on a
coexistence switch. For line tests to be run successfully on international and
domestic trunks, international and domestic originating and terminating test
line agencies must be present. Also, international test line agencies must be
invoked for test line tests on international trunks, and domestic test line
agencies must be invoked for test line tests on domestic trunks.
BCS history
This feature was created in BCS29.
User interface
Test line tests, except T101 (communication test line), can be originated
manually at the TTP (trunks test position) level of the MAP (maintenance
and administration position) display by entering the command TST with the
appropriate test line code parameter.
Test line tests can be originated manually from the ATT (automatic trunk test
position) level of the MAP display by invoking the TESTREQ command on
the affected trunk group, or can be scheduled to run automatically on a trunk
group basis according datafill in table ATTSCHED.

NTXB21AA–2 297-1001-801i Standard 09.01 January 2000

NTXB21AA NTXB21AA
AE0523 AE0523
Feature name
Japan 300 SuperNode and ITOPS Compatibility
Description
This feature allows the International Traffic Operator Position System
(ITOPS) to reside in a DMS-300 SuperNode switch.
The DMS-300 switch is based on North American (domestic) call
processing. ITOPS is based on international call processing. Coexistence
software is necessary to allow a single switch to handle both domestic and
ITOPS calls.
Coexistence involves having international and domestic call processing run
in parallel. Each system communicates only with those peripherals based on
the same architecture. Communication between international and domestic
agents is intra-office switched and is routed over looparound trunks. Calls
handled by the DMS-300 switch and requiring operator intervention are
looped around back into the switch using R1 trunks, and offered to ITOPS
operators.
BCS history
This feature was created in BCS29.
Restrictions and limitations
Gateway trunks with R2 signaling are not supported in the coexistence
configuration.
Looparound trunks must be engineered to allow communication between the
DMS-300 switch and ITOPS.
The ITOPS operator is not passed the calling subscriber number because
looparound trunks do not support automatic number identification (ANI).

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB21AA–3

 NTXB22AA
OM Enhancements
This feature package applies to DMS-100, DMS-200, and DMS-100/200
combined and DMS-100/200 ITOPS offices.
NTXB22AA provides operational measurements to count the following
incidents:
• received and unreceived R2 signals
• unanswered calls on a trunk group basis
• traffic data on a trunk group and destination code basis
• traffic summaries on a trunk group and destination code basis

Feature package contents

Feature package NTXB22AA contents
Feature number Description

AE1240 OM Enhancements for Unsuccessful Calls

AL2530 OM Pegging for Answer Attempts
AL2549 Traffic Distinction OMs
AL2720 Traffic Distinction OMs–Call Processing

BCS history
This feature package was created in BCS34.
Required feature packages
Required feature packages
Feature package Description
number

NTX00AA Bilge
NTX001AA Common Basic
NTX470AA International–Common Basic

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB22AA–1

NTXB22AA
AE1240
Feature name
OM Enhancements for Unsuccessful Calls
Description
This feature provides operational measurements (OM) registers to peg
received and unreceived R2 signals for unsuccessful calls in DMS-100,
DMS-200, and DMS-100/200 switches in China.
This feature provides OM registers to peg reception of the following R2
signals:
• B2 (called subscriber local busy – outgoing trunks)
• B3 (called subscriber toll busy – outgoing trunks)
• A4 + B4 (congestion in distant exchange – outgoing trunks)
• B5 (unobtainable number – outgoing trunks)

This feature provides OM registers to peg the following unreceived R2

signals:
• A1 (send next digit – outgoing trunks)
• A3 (request category – outgoing trunks)
• KB (state of the called subscriber – outgoing trunks)
• KD (type of service at the originating end – incoming trunks)

This feature pegs partial dial treatments for unsuccessful calls.

BCS history
This feature was created in BCS36.
Restrictions and limitations
The following interworkings are supported by this feature:
• line to R2 R2 to line MFP to R2
• R2 to R2 R2 to ITOPS ITOPS to R2
• R2 to DP R2 to CH02 T101 to R2
• DP to R2

This feature supports unsuccessful calls OM for R2 trunks only.

The OM group DCTS is not pegged for some overlap calls.
Unreceived R2 signals are not pegged at the tandem offices for end-to-end
calls.
For ordinary subscriber calls, fields NB2 and NB3 of the OM group DCTS
are not pegged.

NTXB22AA–2 297-1001-801i Standard 09.01 January 2000

 NTXB22AA
AE1240
Feature interactions
AE1240 interacts with feature AL2549 (Traffic Distinction OMs).
Operational measurements
The following fields are added to the OM group destination code traffic
summary (DCTS):
• NB2 contains the number of B2 signals for outgoing trunks.
• NB3 contains the number of B3 signals for outgoing trunks.
• NA4B4 contains the number of A4 + B4 signals for outgoing trunks.
• NB5 contains the number of B5 signals for outgoing trunks.
• NPDIL contains the number of partial dial treatments for incoming
trunks.
• NONRA1 contains the number of unreceived A1 signals for outgoing
trunks.
• NONRA3 contains the number of unreceived A3 signals for outgoing
trunks.
• NONRKB contains the number of unreceived KB signals for outgoing
trunks.
• NONRKD contains the number of unreceived KD signals for incoming
trunks.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB22AA–3

NTXB22AA
AL2530
Feature name
OM Pegging for Answer Attempts
Description
This feature enhances operational measurements (OM) by providing peg
counts and usage measurements for unanswered calls on a trunk group basis.
Two new fields, which are reported both periodically and on demand, are
added to the OM reporting services (OMRS).
The existing OM for originating calls provide call usage measurements, peg
counts for call attempts reaching an outgoing trunk, and peg counts for call
attempts routed to treatment. This feature adds call disposition
measurements such as peg counts for calls reaching an idle line, answered
calls, calls reaching a busy line, and calls encountering network congestion.
BCS history
This feature was created in BCS34.
Restrictions and limitations
This feature is available in the following switches:
• DMS-100
• DMS-200
• DMS-100/200 combined
• DMS-100/200 International Traffic Operator Position System (ITOPS)

Answered calls with Free Number Terminating (FNT), that do not send
answer, are not pegged.
Reanswered calls are not pegged.
This feature does not support answered call measurements on terminating
T101 trunks, terminating ARTWER trunks, and other test trunk types used
in automatic transmission measuring equipment (ATME) tests, milliwatt
tests, and looparound tests.
Feature interactions
This feature interacts with feature AE0943 (Active OMs in Erlangs).
Operational measurements
Fields NANS and ANSU are added to the OM group TRK in on-demand
OM reports. Field NANS contains measured peg counts for answered calls
and field ANSU contains measured usage counts for answered calls.
On-demand OM reports are generated using the command OMSHOW.

NTXB22AA–4 297-1001-801i Standard 09.01 January 2000

 NTXB22AA
AL2530
New fields ANSPEG and ANSUSG are added to the periodic output OM
report ACHGXREP. Field ANSPEG contains the measured peg counts for
answered calls and field ANSUSG contains the measured usage counts for
answered calls.
Logs
New fields ANSPEG and ANSUSG are added to the OMRS log. Field
ANSPEG contains the measured peg counts for answered calls and field
ANSUSG contains the measured usage counts for answered calls.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB22AA–5

NTXB22AA
AL2549
Feature name
Traffic Distinction OMs
Description
This feature enables DMS-100, DMS-200 and DMS-100/200 switches in
China to supply traffic data on a trunk group and destination code basis.
Two new operational measurements (OM) groups and the associated table
control are implemented by this feature.
BCS history
This feature was created in BCS35.
Restrictions and limitations
Register NSCO of OM group DCTS and register NSCT of OM group
TRKDCTS are
• pegged for R2 trunks only
• not pegged for end-to-end calls

Register NANSO of OM group DCTS and register NANST of OM group

TRKDCTS are not pegged for
• reanswered calls
• answered calls that have Free Number Terminating (FNT) and do not
send the Answer message
Only outgoing two-way trunks can be datafilled in table TRKDCTS.
Only trunks that have one of the following group types can be datafilled in
table TRKDCTS:
• MTR (metering)
• ANI (automatic number identification)
• ITOPS (International Traffic Operator Position System)
• OPR (operator)
Only destination codes that are datafilled in table DCTS can be datafilled in
table TRKDCTS.
Feature interactions
AL2549 requires feature AL2720 (Traffic Distinction OMs – Call
Processing).
AL2720 interacts with feature AE0943 (Active OMs in Erlangs).

NTXB22AA–6 297-1001-801i Standard 09.01 January 2000

 NTXB22AA
AL2549
Datafill
Table Description

DCTS This new table defines the destination codes corresponding to

the keys in the OM group DCTS. Each tuple in this table
creates a new tuple in OM group DCTS. Each key field is for
each key of the related tuple in OM group DCTS.

TRKDCTS This new table supplies the traffic data for combinations of trunk
groups and destination codes. Each tuple of this table creates
a new tuple in OM group TRKDCTS. Each key defined in this
table introduces a new set of OM registers in OM group
TRKDCTS.

Operational measurements
OM group DCTS (destination code traffic summary) is added. DCTS
supplies traffic data on the basis of destination codes that are datafilled in the
new table DCTS. OM group DCTS contains the following register fields:
• NCAO contains the number of call attempts routed to a specified
destination code, on all office trunks.
• NSZGO contains the number of seizures for the specified destination
code, on all office trunks.
• NSCO contains the number of successful calls for the specified
destination code, on all office trunks.
• NANSO contains the number of answered calls for the specified
destination code, on all office trunks.
• TRFUO contains the traffic usage for the specified destination code, on
all office trunks.
OM group TRKDCTS (trunk destination code traffic summary) is added.
TRKDCTS supplies traffic data on the basis of combinations of trunk groups
and destination codes that are datafilled in the new table TRKDCTS. OM
group TRKDCTS contains the following register fields:
• NCAT contains the number of call attempts routed to the specified
destination code and trunk.
• NSZGT contains the number of seizures on the specified destination
code and trunk.
• NSCT contains the number of successful calls on the specified
destination code and trunk.
• NANST contains the number of answered calls on the specified
destination code and trunk.
• TRFUT contains the traffic usage on the specified destination code and
trunk.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB22AA–7

NTXB22AA
AL2720
Feature name
Traffic Distinction OMs – Call Processing
Description
This feature implements the pegging of operational measurements (OM)
groups destination code traffic summary (DCTS) and trunk destination code
traffic summary (TRKDCTS) in DMS-100, DMS-200 and DMS-100/200
switches in China.
DCTS supplies traffic data for outgoing two-way trunks on the basis of
destination code. TRKDCTS supplies traffic data for outgoing two-way
trunks on the basis of trunk group and destination code.
BCS history
This feature was created in BCS35.
Restrictions and limitations
Register NSCO of OM group DCTS and register NSCT of OM group
TRKDCTS are
• pegged for calls and DP toll calls only
• not pegged for end-to-end calls

Register NANSO of OM group DCTS and register NANST of OM group

TRKDCTS are not pegged for
• reanswered calls
• answered calls that have Free Number Terminating (FNT) and do not
send the Answer message
Only trunks that have the group type MTR (metering), ANI (automatic
number identification), ITOPS (International Traffic Operator Position
System), or OPR (operator) can be datafilled in table TRKDCTS.
Only destination codes in table DCTS can be datafilled in table TRKDCTS.
Feature interactions
AL2720 requires feature AL2549 (Traffic Distinction OMs).
AL2720 interacts with feature AE0943 (Active OMs in Erlangs).

NTXB22AA–8 297-1001-801i Standard 09.01 January 2000

 NTXB69AA
R2 for DMS-100 International
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTXB69AA contents
Feature number Description

AE0139 MFCR2 in PDTC–Main Feature

AE0140 R2 for DMS-100 International–CC Description
AE0171 Compeller Transactor and Protocol (International)
AE0172 Compelled Register Signaling Transact
AE0173 CRST–TAT Protocol
AE0514 Moroccan R2 Line Signaling
AE0893 Two-way NTLS16, NTRS11 (R2), NTRS05 (DP)
AJ1124 Brazil R2 Enhancements

BCS history
This feature package was created in BCS24.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX270AA New Peripheral Maintenance Package
NTX470AA International–Common Basic
NTX904AA R2 Signaling Base

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB69AA–1

NTXB69AA
AE0139
Feature name
MFC-R2 in PDTC – Main Feature
Description
This feature provides multifrequency compelled (MFC) register signaling in
the international digital trunk controller (IDTC) for the DMS-100/200
switch.
This feature supports the variants of MFC register signaling using protocol
definition tables. These tables provide flexibility in defining MFC
protocols.
A new transactor network is built for MFC trunks. This network contains
compelled register signalling transactors (CRST) and terminal application
transactors (TAT). The CRST has the following logical parts:
• The compeller handles one compelled cycle of MFC signaling. It
controls a universal tone receiver (UTR) and tone generator.
• The register, which controls the compeller, handles logic activities in
MFC protocol such as digit collection and analysis, and information
requests.
The TAT supports MFC features that require central control (CC)
involvement. RST TAT protocol is expanded to support MFC protocol.
BCS history
This feature was created in BCS24.
Hardware requirements
This feature requires the appropriate NT6X43 (message interface) card and
the NT6X92CA (international UTR tone detection) card.
Feature interactions
AE0139 is the main feature in MFC-R2 register signaling for the IDTC. The
other features are
• AE0140 R2 for DMS-100 Intl – CC Description
• AE0142 MFC-R2 Protocol Definition Tables
• AE0146 MFC-R2 Routing Tables
• AE0171 Compeller Transactor and Protocol (International)
• AE0172 Compelled Register Signaling Transactor
• AE0173 CRST - TAT Protocol

NTXB69AA–2 297-1001-801i Standard 09.01 January 2000

NTXB69AA NTXB69AA
AE0140 AE0140
Feature name
R2 for DMS-100 International – CC Description
Description
This feature provides the multifrequency compelled (MFC) central control
(CC) features required for MFC register signaling in the DMS-100/200
switch.
BCS history
This feature was created in BCS24.
Feature interactions
AE0140 is a feature in MFC-R2 register signaling for the international
digital trunk controller (IDTC). The other features are
• AE0139 MFC-R2 in PDTC – Main Feature
• AE0142 MFC-R2 Protocol Definition Tables
• AE0146 MFC-R2 Routing Tables
• AE0171 Compeller Transactor and Protocol (International)
• AE0172 Compelled Register Signaling Transactor
• AE0173 CRST - TAT Protocol

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB69AA–3

NTXB69AA
AE0171
Feature name
Compeller Transactor and Protocol (International)
Description
This feature implements the compel cycle level in multifrequency compelled
(MFC) register signaling protocol.
BCS history
This feature was created in BCS24.
Hardware requirements
This feature requires the appropriate NT6X43 (message interface) card and
the NT6X92CA (international UTR tone detection) card.
Feature interactions
AE0171 is a feature in MFC-R2 register signaling for the IDTC. The other
features are
• AE0139 MFC-R2 in PDTC – Main Feature
• AE0140 R2 for DMS-100 Intl – CC Description
• AE0142 MFC-R2 Protocol Definition Tables
• AE0146 MFC-R2 Routing Tables
• AE0172 Compelled Register Signaling Transactor
• AE0173 CRST - TAT Protocol

NTXB69AA–4 297-1001-801i Standard 09.01 January 2000

NTXB69AA NTXB69AA
AE0172 AE0172
Feature name
Compelled Register Signaling Transactor
Description
This feature implements the register level in multifrequency compelled
(MFC) register signaling protocol in the international digital trunk controller
(IDTC) for the DMS-100/200 switch.
BCS history
This feature was created in BCS24.
Feature interactions
AE0172 is a feature in MFC-R2 register signaling for the IDTC. The other
features are
• AE0139 MFC-R2 in PDTC – Main Feature
• AE0140 R2 for DMS-100 Intl – CC Description
• AE0142 MFC-R2 Protocol Definition Tables
• AE0146 MFC-R2 Routing Tables
• AE0171 Compeller Transactor and Protocol (International)
• AE0173 CRST - TAT Protocol

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB69AA–5

NTXB69AA
AE0173
Feature name
CRST - TAT Protocol
Description
This feature implements changes in protocol for communication between
central control (CC) and the terminal application transactor (TAT) in the
international digital trunk controller (IDTC). These protocol changes are
required to support multifrequency compelled (MFC)-R2 register signaling.
BCS history
This feature was created in BCS24.
Feature interactions
AE0173 is a feature in MFC-R2 register signaling for the IDTC. The other
features are
• AE0139 MFC-R2 in PDTC – Main Feature
• AE0140 R2 for DMS-100 Intl – CC Description
• AE0142 MFC-R2 Protocol Definition Tables
• AE0146 MFC-R2 Routing Tables
• AE0171 Compeller Transactor and Protocol (International)
• AE0172 Compelled Register Signaling Transactor

NTXB69AA–6 297-1001-801i Standard 09.01 January 2000

NTXB69AA NTXB69AA
AE0514 AE0514
Feature name
Moroccan R2 Line Signaling
Description
This feature implements the line signaling system NTLS16, which is used in
digital R2 trunk call processing in the DMS-100/200 switch in Morocco.
BCS history
This feature was created in BCS28.
Restrictions and limitations
Datafilling of one-way trunks is supported. Datafilling of two-way trunks is
not supported.
Meter pulses are not counted or made available through any metering
system. Metering pulses are not tandemed across a switch.
Datafill
Table Description

LNSIGSYS Separate tuples for the Moroccan R2 line signaling system are
added.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB69AA–7

NTXB69AA
AE0893
Feature name
Two-way NTLS16, NTRS11 (R2), NTRS05 (DP)
Description
This feature enhances the trunk line signaling system NTLS16 and the
register signaling systems NTRS11 (R2) and NTRS05 (dial pulse), so that
two-way trunks are supported.
This feature is used by digital R2 trunk call processing in the DMS-100/200
switch.
BCS history
This feature was created in BCS33.
Restrictions and limitations
Table LNSIGSYS must be datafilled before table TRKSGRP.
Two-way operation is not supported for Moroccan multifrequency (MF)
Socotel.
Two-way enhancements are supported only for R2 variants supported by
register signaling system NTLS16.
Two-way trunks do not support generation or reception of meter pulses.
Digit analysis is not supported on two-way trunks using register signaling
system NTRS05.
Datafill
Table Description

LNSIGSYS Datafill is modified to support two-way operation. In field

SIGTYP, datafill restriction 2W (two-way) in subfield SIGDIR is
valid for line signaling system NTLS16.
RGSIGSYS Datafill is modified to support two-way operation. In field
SIGTYP, datafill restriction 2W (two-way) in subfield SIGDIR is
valid for line signaling system NTRS05.
TRKSGRP Datafill is modified to support two-way operation. Direction 2W
(two-way) is a valid direction for a trunk with a line signaling
system of NTLS16 and a register signaling system of NTRS11.

NTXB69AA–8 297-1001-801i Standard 09.01 January 2000

 NTXB69AA
AE0893
Operational measurements
The GLARE field in the operational measurements (OM) group TRK is
pegged on detection of a glare situation (both ends of a trunk seized at the
same time and in the same direction).
Logs
A glare situation generates a TRK123 log.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB69AA–9

NTXB69AA
AJ1124
Feature name
Brazil R2 Enhancements
Description
This feature provides the R2 protocol and the continuous digital R2 line
signaling system required for DMS-200 switches and mobile telephone
exchanges (MTX) in Brazil.
The Brazil R2 forward signal multifrequency combinations are allocated in
two groups: Group I and Group II. The Group I forward signals transmit
information about the calling and called party addresses. The Group II
forward signals transmit information about the calling party category. The
change from Group I to Group II occurs when requested by special
backward signals.
The Brazil backward signal multifrequency combinations are allocated in
two groups: Group A and Group B. The Group A backward signals
acknowledge receipt of information in the Group I forward signals, and
request specific information from the originating exchange. The Group B
backward signals consist of the secondary group of signals sent from the
incoming exchange. The secondary signals transmit the called party’s line
condition or convey information about the switching equipment at the
originating exchange. Group B backward signals acknowledge Group II
forward signals.
BCS history
This feature was created in BCS31.
Hardware requirements
This feature requires the NT6X69LA (CPP message protocol and
downloadable tones CP) card and the NT6X92CA (international UTR tone
detection) card.
Restrictions and limitations
Datafilling of two-way trunks is not supported.
Though NTLS16 can recognize metering pulses during the conversation part
of a call sequence, the pulses are not counted or made available through any
metering or billing system.
The maximum length of a calling party’s address sent from an MTX to a
DMS switch is seven digits.

NTXB69AA–10 297-1001-801i Standard 09.01 January 2000

 NTXB69AA
AJ1124
The Group II forward signals listed below cannot be generated by the
Brazilian MTX and DMS-200 switch. If any of these signals are received,
they are treated in the same manner as II-1 (regular subscriber).
• II-2 subscriber with special billing
• II-4 COIN
• II-5 operator
• II-6 data
• II-7 toll coin phone
• II-11 subscriber with transfer

If the calling part’s address is requested through A-5 (send calling party’s
category), the Brazilian MTX and DMS-200 switch replies with I-15 (end of
calling) for calls originating from maintenance equipment.
The following Group A signals cannot be generated by the Brazilian MTX
and DMS-200 switch:
• A-2 send from the first digit
• A-7 send last but two
• A-8 send last but three
• A-9 send last but one
The following Group B signals cannot be generated by the Brazilian MTX
and DMS-200 switch:
• B-2 subscriber line busy
• B-3 subscriber transferred
• B-5 subscriber line free, no charge
• B-6 subscriber line free, charge, called party control
The charging request types in the backward signals listed below are ignored
by the Brazilian MTX and DMS-200 switch. The MTX can bill the
originating call depending on the billing strategy employed by the MTX.
• B-1 subscriber line free, charge
• B-5 subscriber line free, no charge
• B-6 subscriber line free, charge, called party control
The force release (FRLS) signal is not generated by the Brazilian MTX and
DMS-200 switch.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB69AA–11

NTXB69AA
AJ1124
Datafill
Table Description

LNSIGSYS Field FLTR (signal filter time) is added. Any line signal that
persists for less than the time datafilled in field FLTR is not
recognized. Though field FLTR exists for all tuples in
LNSIGSYS, its value is restricted to 40 ms for all LNSIGSYS
refinements other than NTLS16 and NTLS20.

Field RMINFLT is added to refinement IC (incoming direction) of

NTLS16. RMINFLT is the minimum time a received forward
signal must persist in order to be recognized.

Fields RMINFRLS, SMINFRLA, and SMINFLT are added to

refinement OG (outgoing direction) of NTLS16. Fields
RMINMTR, RMAXMTR, and RMTRSETL are deleted from
refinement OG of NTLS16.

NTXB69AA–12 297-1001-801i Standard 09.01 January 2000

 NTXB75AA
Implementation of RMM on IRLCM
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTXB75AA contents
Feature number Description

AE0293 Implementation of RMM on IRLCM

BCS history
This feature package was created in BCS25.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB75AA–1

NTXB75AA
AE0293
Feature name
Implementation of RMM on IRLCM
Description
This feature provides support for central control (CC) communication with
and control of the remote maintenance module (RMM).
The RMM is a test shelf that provides facilities to test trunks and to
configure alarm detection units. The RMM is connected to the CC through
the international remote line concentrating module (IRLCM) and the
international line group controller (ILGC).
BCS history
This feature was created in BCS25.

NTXB75AA–2 297-1001-801i Standard 09.01 January 2000

 NTXB83AA
ITOPS to International R2 Interworking
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTXB83AA contents
Feature number Description

AG1294 C1 Trunk ITOPS Position Interactions

TA0228 ITOPS—R2 Trunk Interworking

BCS history
This feature package was created in BCS27.
BSC39i—Feature TA0228 added.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX056AA Enhanced Administration
NTX270AA New Peripheral Maintenance Package
NTX470AA International–Common Basic
NTX904AA R2 Signaling Base
NTXB05AA ITOPS Common Basic
NTXB13AA ITOPS Toll Basic (upgraded by NTXB13AB)
or
NTXB13AB ITOPS Toll–Enhanced Queuing (upgrades NTXB13AA)

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB83AA–1

NTXB83AA
AG1294
Feature name
C1 Trunk ITOPS Position Interactions
Description
This feature provides the following call types for China:
• line to C1 multifrequency compelled (MFC) metering (MTR) trunk
(terminating control)
• C1 MFC MTR trunk to international traffic operator position system
(ITOPS) position (terminating control)
• ITOPS position to C1 MFC MTR trunk (originating control)

This feature also provides the following functions for China:

• end-to-end signaling over C1 MFC trunks
• generation of KOA signals, which are used to convey information about
the calling subscriber in international calls
• line option Denied Toll Break-in (DTBI), which prevents the operator
from breaking in on calls involving an especially important subscriber
• digit analysis on dial pulse (DP) trunks

BCS history
This feature was created in BCS27.
Restrictions and limitations
The following ITOPS service classes of originating subscribers cannot be
signaled between offices in China:
• UNSPEC (unspecified)
• MOBILE
• MARINE
• COIN

Calling card verification calls are not supported over C1 trunks from ITOPS
positions.
Datafill
Table Description

FEATCHG and Option DTBI is added.

LENLINES
R2CLGSRV This new table maps forward signals into table ITOPSERV
indexes.

NTXB83AA–2 297-1001-801i Standard 09.01 January 2000

 NTXB83AA
AG1294
Service orders
Option DTBI can be added, removed, or queried using service orders.
Automatic message accounting
Option DTBI can be charged for assignment. A datafillable number of
charge units can be charged each time the operating company assigns DTBI
to a line using table control or service orders.
All feature metering charges are pegged on the subscriber’s feature meter.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB83AA–3

NTXB83AA
TA0228
Feature name
ITOPS–R2 Trunk Interworking Enhancement
Description
This feature provides interworking between ITOPS and R2 trunks using
NTLS15, NTLS16 and NTLS24 line signaling systems.
For ITOPS–R2 trunk interworking, NTLS15, NTLS16, and NTLS24 line
signaling systems must have the following operator signals:
• Toll Break In Start (TOS) signal: Sending this signal starts Toll Break In
(TBI) session. On receipt of the TOS signal, the local office connects an
operator to the established call.
• Toll Break In End (TOE) signal: Sending this signal ends Toll Break In
(TBI) session. On receipt of TOE signal, the system restores the
connection status and tones that existed before the receipt of TOS signal.
• False Answer (FAN) signal: This signal is used to identify the release of
the existing call. It is normally used by operator to identify when to
initiate ringing.
• Manual Start of Ringing: This signal is used to start ringing backward or
forward. For backward ringing, it is called as Start of Ringing Backward
(RGB); for forward ringing it is called as Start of Ringing Forward
(RGF). This signal is generated by the operator by keying the RING
CLG and RING CLD keys respectively.
Although TOS, TOE, RGB and RGF signals seem to be different signals,
they are all interpretations of the Forward Transfer (FOT) signal. The FOT
signal is interpreted as any of the above signals, depending upon the state of
the call.
The FOT signal is a pulse signal and can have a single or double pulse
depending upon local signaling requirements and the interpretation (TOS,
TOE, RGB or RGF). The single or double pulse FOT signal is determined
by datafill.
This feature introduces a double pulse FOT signal to represent the RGB and
RGF signals and a single pulse FOT signal to represent the TOS and TOE
signals.
The False Answer (FAN) signal is known as the Subscriber Free (SSF)
signal in DMS-100 switches. The SSF signal also can be single or double
pulse signal.

NTXB83AA–4 297-1001-801i Standard 09.01 January 2000

 NTXB83AA
TA0228
Line signaling systems NTLS15 and NTLS24 have previously supported the
generation and reception of single pulse FOT signals to fulfill the TOS,
TOE, RGB and RGF functions. These line signaling systems are modified
by this feature to support the generation and reception of double pulse FOT
signals to fulfill the RGB and RGF functions.
The NTLS16 line signaling system is modified to support the start of
Ringing Backward (RGB) signal as well as the TOS, TOE and RGF signals.
NTLS16 is also modified to support the generation and reception of a double
pulse FOT signal to fulfill the RGB and RGF functions.
BCS history
This feature was created in BCS39i.
Restrictions and limitations
In table LNSIGSYS refinement “Signaling type NTLS15 incoming” the
following rules must be followed:
• Parameter RMAXFOT must have a higher value than parameter
RMINFOT
• Parameter RMINCLF must have a higher value than parameter
RMAXFOT
• Parameter RMINFOT must have a value other than zero if signal SSF is
defined
In table LNSIGSYS refinement “Signaling type NTLS15 outgoing” the
following rules must be followed:
• Parameter RMAXFOT must have a higher value than parameter
RMINFOT
• Parameter RMINCLB must have a higher value than parameter
RMAXFOT
• Parameter RMINRLG must have a higher value than parameter
RMAXFOT
In table LNSIGSYS, for both of the above refinements, the following rules
and allowances apply:
• Parameter FOTPAUSE must have a higher value than parameter
SIDLTM if SIDLTM is other than zero
• Parameter FOTPAUSE can be zero, or it can have a value from 10 to 300
(100ms to 3000ms) if parameter SFOTTM is other than zero

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB83AA–5

NTXB83AA
TA0228
In table LNSIGSYS refinement “Signaling type NTLS16 incoming” the
following rule must be followed:
• Parameter RMAXFOT must have a higher value than parameter
RMINFOT
• Parameter RMINCLF must have a higher value than parameter
RMAXFOT
In table LNSIGSYS refinement “Signaling type NTLS16 outgoing” the
following rule must be followed:
• Parameter RMAXFOT must have a higher value than parameter
RMINFOT
• Parameter RMINCLB must have a higher value than parameter
RMAXFOT
In table LNSIGSYS, for both of the above refinements, the following rules
and allowances apply:
• Parameter FOTPAUSE must have a higher value than parameter
SIDLTM, if SIDLTM is other than zero
• Parameter FOTPAUSE can be zero, or it can have a value from 10 to 300
(100ms to 3000ms) if parameter SFOTTM is other than zero
• FOTPAUSE must be zero if SMINFOT and RMAXFOT is zero.

In table LNSIGSYS refinement “Signaling type NTLS24” the following

rules and allowances apply:
• The FOT signal must be datafilled as a shorter pulse than the Clear
Forward (CLF), Clear Back (CLB), and Release Guard (RLG) signals
• If an SSF signal is defined, then the FOT signal must have a value other
than zero
• FOTPAUSE must be zero if FOT is zero
• Parameter FOTPAUSE can be zero, or it can have a value from 10 to 300
(100ms to 3000 ms) if parameter FOT is other than zero
• Parameter FOTPAUSE must have a higher value than parameter
SMINIDL, if SMINIDL is other than zero
Feature interactions
This feature requires the following features to function properly:
• AC0239 ITOPS International Call Handling
• AC0255 Operator Hold for ITOPS (NTLS15)
• AE0514 Moroccan Digital R2 Line Signaling (NTLS16)
• AL2457 Digital A-bit Pulsed Line Signaling (NTLS24)

NTXB83AA–6 297-1001-801i Standard 09.01 January 2000

 NTXB83AA
TA0228
Datafill
Table Description

LNSIGSYS Field FOTPAUSE is added to incoming and outgoing

refinements of NTLS15.

Fields RMINFOT, RMAXFOT and FOTPAUSE are added to the

outgoing refinement of NTLS16.

Fields SMINFOT and FOTPAUSE are added to the incoming

refinement of NTLS16.

Field FOTPAUSE is added to the two-way (2W) refinement of

NTLS16.

FOTPAUSE is added to the incoming and outgoing refinements

of NTLS24.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB83AA–7

 NTXB84AA
International Rating System
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTXB84AA contents
Feature number Description

AG1231 International Rating:Test CI Command

AG1235 International Rating: Mass Table Control
AG1236 International Rating: Charge Calculator
AG1237 International Rating: Rate Step Calculator
AJ1025 International Rating: Tax Calculation
AJ1256 International Rating: Sub-minute Billing
AJ1445 ITOPS: CCITT Calling Card Format
AJ1446 International Rating Enhancements

BCS history
This feature package was created in BCS27.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX056AA Enhanced Administration
NTX270AA New Peripheral Maintenance Package
NTX470AA International–Common Basic

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB84AA–1

NTXB84AA
AG1231
Feature name
Intl Rating: Test CI Command
Description
This feature provides a means of testing rating tables. The international
rating test program IRATE is used by the operating company to verify their
rating system datafill, and to calculate charges for active and inactive rating
tables. Using IRATE, the operating company can
• enter the details of a test call at the command interpreter (CI) level of the
MAP (maintenance and administration position) display
• request rate step or charge calculation for the test call, with the results
displayed at the MAP terminal
BCS history
This feature was created in BCS27.
Restrictions and limitations
The CI command IRATE TEST does not display a table trace of the tables
used.
User interface
The following IRATE commands are available with this feature:
• IRATE is used to access the IRATE commands level of the MAP display.
• HELP displays a list of available subcommands and online
documentation about the IRATE program.
• Q (query) displays detailed explanations of the available subcommands.
• QUIT returns the user to the CI level of the MAP display.
• SHOW displays the current test call settings.
• CLG is used to enter or display the calling number for the test call (1 to
18 digits).
• CLDTYPE is used to enter or display the called number type (LOCAL,
NATIONAL, or FOREIGN).
• CLD is used to enter or display the called number (1 to 18 digits).
• CHGTYPE is used to enter or display the charge type (PAID,
COLLECT, SPLCLG, SPLCLD, or no entry).
• CLASSCHG is used to enter or display the class charge type (STA, PER,
PCB, or no entry).
• SPL is used to enter or display the special number type (CC, THIRD, or
NONE), if applicable.
• OSC is used to enter or display the originating station class (STATION,
HOTEL, APS, or no entry).

NTXB84AA–2 297-1001-801i Standard 09.01 January 2000

 NTXB84AA
AG1231
• TSC is used to enter or display the terminating station class (STATION,
HOTEL, APS, or no entry).
• CAT is used to enter or display the call type (OA, OH, DD,
INTERCEPT, INWARD, BOOK, SPECIAL, DATABASE, OPER, or no
entry).
• TAC is used to activate time and charge.
• DB is used to retrieve a call from the delay call database.
• DRT is used to show whether or not simulation of the dial rate keys is
used.
• SOC is used to enter or display the test call start time (month, day, year,
hour, minute, and second).
• DUR is used to enter or display test call duration in minutes.
• RS is used to enter or display the rate step.
• USE is used to enter or display whether the active or inactive rating
tables are used.
• CR is used to indicate to the rate test program that the current settings
are to be used to calculate the rate step.
• CC is used to calculate test call charges (if the rate step is known).
• CB is used to calculate both the rate step and the test call charges.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB84AA–3

NTXB84AA
AG1235
Feature name
Intl Rating: Mass Table Control
Description
This feature provides the capability to datafill inactive tables used in the
rating system. The inactive tables can be activated and datafill in the newly
activated tables used to calculate toll charges.
The International Mass Table Control feature provides the capability of mass
controlling data changes in the tables used in the rating system. The
required datafill is entered into the inactive rating tables. When all the
required datafill has been entered, the contents of the inactive tables are
swapped with the contents of the corresponding active tables. The following
rating tables are mass controlled:
• ATTRIBI ATTRIB
• ATRIMODI ATRIMOD
• CHGATRIBI CHGATRIB
• CHGHEADI CHGHEAD
• HOLITRMTI HOLITRMT
• MODMAPI MODMAP
• MODSETI MODSET
• RATEMODI RATEMOD
• RNDINGI RNDING
• RSFORI RSFOR
• RSLOCI RSLOC
• RSNATI RSNAT
• SCHEDEFI SCHEDEF
• TAXI TAX
• TAXMAPSI TAXMAPS
• TIMEZONEI TIMEZONE

The mass table control system has one of the following states:
• In the initial state, active tables can be edited and changes to datafill
immediately affect call rating. The inactive tables are empty.
• The duplicate state is entered using the mass table control commands
DUPLICATE or ENABLE. All tables can be edited and the active tables
initially are empty. When DUPLICATE is entered, the inactive tables
initially contain a copy of the active table datafill. When ENABLE is
entered, the inactive tables initially are empty. Table control error
checks ensure that the active and inactive data are consistent sets.

NTXB84AA–4 297-1001-801i Standard 09.01 January 2000

 NTXB84AA
AG1235
• In the switched state, the active tables contain new data and the inactive
tables contain old data.
BCS history
This feature was created in BCS27.
User interface
The following CI commands are added:
• MASSTC accesses the command interpreter (CI) mass table control
level of MAP (maintenance and administration position) display.
• DUPLICATE copies the contents of each active table into the
corresponding inactive table (initial state to duplicated state).
• ENABLE changes the system from the initial state to the duplicated state
without copying table contents, which allows the inactive tables to be
datafilled with new data.
• SWAP swaps the contents of the active and inactive tables (duplicated
state to switched state).
• SAVE changes the system from the switched state to the initial state and
saves the current active data permanently. The permanent datafill is
copied into the active tables during restarts.
• SCRAP erases new data (duplicated state to initial state). Since all
changes are lost, new data must be inactive when the SCRAP command
is invoked.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB84AA–5

NTXB84AA
AG1236
Feature name
Intl Rating: Charge Calculator
Description
The international charge calculator is used to determine the charges to be
applied to toll calls and all types of operator-assisted calls.
The international charge calculator calculates charges using the following
factors:
• type of call
• type of service
• type of billing
• call duration
• surcharges for additional services provided
• discounts (for holidays or time of day)
• taxes
• rounding off charges
BCS history
This feature was created in BCS27.
Restrictions and limitations
This feature is supported only in International Traffic Operator Position
System (ITOPS) toll offices.
Feature interactions
This feature is used by all other international rating features.
Datafill
Table Description

ATTRIB This new table maps an attribute number to a call origination

and a set of zero or more call attributes. An attribute is a call
characteristic such as coin paid (Coin) or hotel paid (Hotel).
ATRIMOD This new table contains discount and surcharge information for
all schedules.
CHGATRIB This new table contains attribute-specific charge data. This
table is indexed from tables CHGHEAD and ATTRIB.

—continued—

NTXB84AA–6 297-1001-801i Standard 09.01 January 2000

 NTXB84AA
AG1236

Table Description (continued)

CHGHEAD This new table contains the default charge data and is the only
mandatory table in the charge calculator system. The default
data is used if no special attribute table entries are required to
calculate charges.
HOLIDAYS This new table defines the holidays for which special routing is
required (holiday treatment).
HOLITRMT This new table specifies the type of holiday treatment to be
applied.
MODMAP This new table defines the modifications used for each
schedule.
MODSET This new table defines the charge modifications from table
MODMAP.
RATEMOD This new table provides the data used for calculating
modifications on charges (discounts or surcharges).
RNDING This new table specifies how rounding off is applied for various
schedule sets.
TAX This new table contains the tax rates for various schedule sets.
TAXMAPS This new table specifies which set of tax entries are applicable
to a schedule within a schedule set.
TIMEZONE This new table contains the time difference between the local
time for the originator of a call and the local time of the called
party.

End

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB84AA–7

NTXB84AA
AG1237
Feature name
Intl Rating: Rate Step Calculator
Description
This feature implements the rate step calculation portion of the international
rating system.
The rate step is calculated using the tables added by this feature, along with
the schedule set and the schedule. The rate step provides the means to
calculate a charge for a call.
The tables added by this feature provide the capability to datafill rating data
without any dependence on the length of the calling and called numbers.
BCS history
This feature was created in BCS27.
Restrictions and limitations
This feature is supported only in International Traffic Operator Position
System (ITOPS) toll offices.
Feature interactions
This feature is used by all other international rating features.
Datafill
Table Description

CLGSSET This new table maps calling areas and office codes to the
schedule sets (SSETNAMES) defined in table SSETNAME.
RSFOR This new table is used to define a schedule for rating of foreign
calls.
RSLOC This new table is used to define schedule for rating of local
calls.
RSNAT This new table is used to define a schedule for rating of national
calls.

—continued—

NTXB84AA–8 297-1001-801i Standard 09.01 January 2000

 NTXB84AA
AG1237

Table Description (continued)

SCHEDEF This new table defines the attributes associated with the
schedules in table SCHNAME. The attributes defined are
· range of rate steps associated with a rate schedule
· termination type, which is used to determine which table is
used in the calculation of manually entered rate steps
(RSNAT, RSFOR, or RSLOC)
· coin recall period
SCHNAME This new table defines the valid schedule names to be used by
the rating system.
SSCHNAME This new table defines the valid schedule sets (SSETNAMES)
to be used by the rating system.

End

User interface
This feature adds the following new key functions:
• The rate step key provides the capability to manually enter a rate step.
Manual rate step entry is used when the rating table entries for the called
number are not present.
• The dial rate key is used by the operator when a subscriber is unable to
make a direct dial (DD) call and the operator feels the subscriber should
be charged at DD rates.
Automatic message accounting
This feature implements the dial rate key indicator (information digit 4) on
the ITOPS international centralized automatic message accounting
(ICAMA) record.
Information digit 4 is used to indicate if the
• operator billed a call at a direct dial rate
• system has determined the call to be non-chargeable
• operator has entered the call as a no charge call

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB84AA–9

NTXB84AA
AJ1025
Feature name
Intl Rating: Tax Calculation
Description
This feature enhances the tax calculation system used in the international
rating system. The existing tax calculation is based on a percentage of the
total call charge. With this feature, the operating company can assign fixed
taxes based on the initial period call charge rate (charge per minute) of the
call.
BCS history
This feature was created in BCS31.
Restrictions and limitations
This feature is supported only in toll offices.
Feature interactions
This feature requires feature AG1236 (Intl Rating: Charge Calculator).
Datafill
Table Description

ATRIMOD The maximum fixed charge is extended from 100 to 32 768

charge units.
TAX This table is replaced by tables TAXFIX and TAXRATE.
TAXFIX This new table maps schedule set names to various tax rates.
The tax rates are based on the duration and charge rate of the
call.
TAXMAPS This table is modified. Without this feature, this table specifies
which taxes are applied (for example, federal, provincial, or
municipal). With this feature, this table maps the tax type
(FIXED or RATE) the operating company wants to apply to a
schedule in table SSETNAME. Tax type FIXED is used when
fixed tax charges are applicable. Tax type RATE is used when
taxes are based on the call charge. Datafill in this table allows
pre-discount or post-discount charge taxes to be applied.
TAXRATE This new table maps schedule set names to various tax rates
for taxes based on the entire call charge. Three types of taxes
can be applied (for example, federal, provincial, and municipal).

NTXB84AA–10 297-1001-801i Standard 09.01 January 2000

NTXB84AA NTXB84AA
AJ1256 AJ1256
Feature name
Intl Rating: Sub-minute Billing
Description
This feature reduces the minimum charge interval for rating calls from
1 min to 1 s. This reduction allows the operating company to reduce the
amount of unused time the subscriber pays for in a charged call.
BCS history
This feature was created in BCS32.
Datafill
Table Description

CHGATRIB Fields TIMEUNIT, ICRP (initial call recall period), and SCRP
and CHGHEAD (subsequent call recall period) are added. Field TIMEUNIT
determines the size of the charge interval applied. Fields IRCP
and SRCP control the frequency at which a call is returned to
the operator to request more money.

Fields INP (initial period) and SBTI (subsequent interval) are

modified. If field TIMEUNIT is datafilled as SEC (seconds), the
ranges for INP and SBTI are 0 to 900 s. If field TIMEUNIT is
datafilled as MIN (minutes), the ranges for INP and SBTI are
0 to 15 min.

Restrictions and limitations

The following conditions apply to tables CHGATRIB and CHGHEAD:
• the ICRP must equal the initial period plus any multiple (including zero)
of the SBTI, and
• the SCRP must be a multiple of the SBTI

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB84AA–11

NTXB84AA
AJ1445
Feature name
ITOPS: CCITT Calling Card Format
Description
This feature implements the CCITT (International Telegraph and Telephone
Consultative Committee) calling card format for the International Traffic
Operator Position System (ITOPS).
ITOPS functionality is enhanced so that CCITT calling card format can be
collected, validated, and displayed at an ITOPS position. Inward validation
of a calling card number is modified to allow up to 23 digits to be sent
through an inward operator. Existing validation capabilities are preserved
for a subset of the CCITT calling card format, allowing for transition from
the existing 14-digit calling cards to the variable format for CCITT calling
cards.
ITOPS international centralized automatic message accounting (ICAMA)
format is enhanced to record the CCITT calling card format. The automatic
message accounting dump (AMADUMP) utility is enhanced to handle the
new CCITT calling card format.
BCS history
This feature was created in BCS33.
Restrictions and limitations
The size of the personal identification number (PIN) cannot exceed 4 digits.
The full CCITT calling card number requires validation if the CCITT calling
card is not marked for 14 digit validation in field VAL14DIG in table
INTCCTMT.
Automatic validation procedures for calling cards are not supported in
ITOPS. All requests must be manually initiated.
Field ACCIDSIZ must be datafilled as greater than zero.
Datafill
Table Description

OFCENG Office parameter VALIDATE_CCITT_LUHN_DIGIT is added.

This parameter is necessary in situations where the check
(luhn) digit is not required in the CCITT calling number. The
default setting for this parameter is Y (validate check digit).

NTXB84AA–12 297-1001-801i Standard 09.01 January 2000

 NTXB84AA
AJ1445
Logs
Log AMAB188 is added. This log provides a detailed description of the call
data used to produce an ITOPS special long billing extension record, and is
used for debugging.
User interface
To accommodate the CCITT calling card format, the special number field of
the ITOPS position is extended and the special number status (in the special
number field) is shifted to the right.
Automatic message accounting
A special long billing extension (#ED) is produced for billing of CCITT
calling card calls. All other calling card formats produce the existing billing
extension (#E6).

Feature Description Manual Volume 2 of 3 BCS44.1i NTXB84AA–13

NTXB84AA
AJ1446
Feature name
Intl Rating Enhancements
Description
This feature implements quoted discounting. Quoted discounting allows the
operating company to apply a discount or surcharge based on the current
time and date. Using the existing calculation methods, discharges and
surcharges are applied on a percentage basis or on a time-adjustment basis.
BCS history
This feature was created in BCS33.
Datafill
Table Description

ATTRIB This table maps an attribute number to a call origination and a

set of call attributes.

Field ATTRIB is modified by adding the attributes NM (no

modification) and M1 to M8 (modification sets 1 to 8).
RATEMOD This table provides information used to calculate modifications
to call charges.

Field DISCAREA is added (not used with quoted discount).

This field contains subfields MODINP and SENSE1 VALUE1 to
SENSE8 VALUE8. These subfields are used to
· modify the initial time period
· tag charge modifications as discounts or surcharges
Field MODTYPE is added. The options for this field are
PCENT, TIME, and QUOTED. If field MODSET is datafilled as
QUOTED (quoted discount), the time period subdivision in table
MODSET becomes an attribute which is added to the current
set of call attributes. If field MODTYPE is datafilled as PCENT,
rate modifications are given as percentages. If field MODTYPE
is datafilled as TIME, rate modifications are given as time
values that the initial and recall periods are adjusted by.

Table MODSET defines charge modifications.

NTXB84AA–14 297-1001-801i Standard 09.01 January 2000

 NTXE01AA
Enhanced Network—Basic
This feature package supports the deployment of the enhanced network
(ENET) as an additional switching matrix subsystem type for DMS
SuperNode. ENET is a single-stage, nonblocking, junctorless time switch
that can expand capacity from 4000 to 128 000 unidirectional channels in
each plane of a single cabinet.
This feature package applies to DMS SuperNode offices.
Feature package contents
Feature package NTXE01AA contents
Feature number Description

AL0573 ENET Operational Measurements

AL0856 ENET Maintenance
AL0857 ENET Pathend Test MMI
AL0957 ENET REX Test
AL0958 ENET PM Table Control Modifications
AL0959 ENET Shelf Test
AL0960 ENET Path Diagnostics
AL1230 ENET MAP Enhancements
AL2038 ENET Support for 9X45BA
AL2107 Enable A-Law PADROM
AL2162 NT9X45 MMI
AL2260 Support for Warm SWACT Recovery Time Reduction Feature
AR0005 64-K ENET Support
AR0141 ENET PS Link Enhancements
AR0186 ENET Integrity Fault Handling and HMI
TA0392 ENET 16-Mbyte Processor (NT9X13KA)

BCS history
This feature package was created in BCS31.
BSC42i—Feature TA0392 added.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXE01AA–1

NTXE01AA
Required feature packages
Required feature packages
Feature package Description
number

NTX001AA Common Basic

NTX940AA CM Bilge
NTX941AA CM Common
NTX950AA MS Bilge
NTX951AA MS Common
Either
NTXF71AA SuperNode Enhanced Messaging
or
NTXF71AB SuperNode Enhanced Messaging

NTXE01AA–2 297-1001-801i Standard 09.01 January 2000

 NTXE01AA
AL0573
Feature name
ENET Operational Measurements
Description
AL0573 defines ands implement a set of operational measurements (OM)
for the enhanced network (ENET). OMs provides the operating company
with switch performance and service data.
BCS history
This feature was created in BCS31.
Hardware requirements
No additional additional hardware is required. This feature is a part of the
ENET project and must be included in offices equipped with ENET.
Restrictions and limitations
ENET is part of the SuperNode project and cannot be equipped in an NT40
office.
Operational measurements
In offices equipped with ENET, the two OM groups NM and TS are
removed. The following OM fields no longer exist:
• NMSBU
• NMPTSBU
• NMJRSBU
• NMMBU
• NMPTMBU
• NMMSGER
• NMMSGFL
• NMSPCHER
• NMSPCHFL
• NMCERR
• NMCFLT
• TS0, TS1, TS2, TS3, TS4, TS5, TS6, TS7

Feature Description Manual Volume 2 of 3 BCS44.1i NTXE01AA–3

NTXE01AA
AL0573
The following OM groups are added in offices equipped with an ENET:
• The ENETSYS group contains the following fields: ENERR, ENFLT,
ENSBU, ENCALDND, ENTRAPS, ENSWERRS, ENWARM,
ENCOLD, ENRELOAD, ENPARU, ENSPARP, ENMPARP, ENISOU,
ENSISOP, and ENMISOP.
• The ENERMAT group contains the following fields: ENCDERR,
ENCDFLT, ENSBCDU, ENMBCDU, ENOFCDU, ENCDPARU,
ENSCDPAR, ENMCDPAR, ENCDISOU, ENMCDISO, ENPBERR,
ENSCDPAR, ENMCDPAR, ENCDISOU, ENMCDISO, ENPBERR,
ENPBFLT, ENSBPBU, ENMBPBU, ENPBPARU, ENSPBPAR,
ENMSBPAR, ENPBISOU, ENSPBISO, and ENMPBISOU.
• The ENETPLNK group contains the following fields: ENSPCHER,
ENLKERR, ENLKFLT, ENSBLKU, ENMBLKU, ENLKPARU,
ENSLKPAR, ENMLKPAR, ENLKISOU, ENSLKISO, and
ENMLKISO.
• The ENETOCC group contains the following fields: ENET_CPOCC,
ENET_SCHED, ENET_FORE, ENET_MAINT, ENET_BKG, and
ENET_IDLE.

NTXE01AA–4 297-1001-801i Standard 09.01 January 2000

 NTXE01AA
AL0856
Feature name
ENET Maintenance
Description
AL0856 is one of three features required to support the enhanced network
(ENET) P-side maintenance. This feature maintains the peripheral message
path by interacting with the peripheral software and the message switch
software. This software resides in the computing module. No local ENET
support is required.
BCS history
This feature was created in BCS27.
Hardware requirements
This feature is designed to operate on an enhanced core equipped with an
ENET.
Restrictions and limitations
This feature is intended to support ENET and is not available for other
network types.
Feature interactions
This feature is one of three features required to support P-side maintenance
on ENET. The features cannot be supported independently.
The P-side maintenance features require the new message routing algorithms
feature to support the peripheral module (PM) to message switch (MS)
direct messaging.
The P-side maintenance feature also requires the feature that allows the MS
to string P-side port cards together to form a port group. The port group
services one DS512 fiber, enabling the fiber to carry a number of message
paths to an equal number of MS ports in the port group. Another other
function of the feature is to allow the PMDS30 protocol to be valid on the
fiber.
User interface
This feature interacts with the ENET MAP. If the P-side test or
return-to-service (RTS) fails, this feature generates a card list that is sent to
operating company personnel terminal.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXE01AA–5

NTXE01AA
AL0857
Feature name
ENET Pathend Test MMI
Description
AL0857 allows operating company personnel to perform fault identification
and verification on enhanced network (ENET) components of a speech path.
Operating company personnel perform this identification and verification by
specifying a path (or path segment) through ENET, and a test to be run on
that path. The feature supports only 128K ENET.
BCS history
This feature was created in BCS28.
Restrictions and limitations
If the system time is changed by less than 2 years while a path test is in
progress, there may be maximum errors of 5 s to the duration of all the
running tests. If the system time is changed by more than 2 years, running
tests may have taken twice as long as they should take. The test requires
that the crosspoint cards in both ends of the path are equipped with a paddle
board.
Feature interactions
The ENET path test level (PATHTEST) of the MAP (maintenance and
administration position) display is built beneath the ENET MAP level.
Another MAP level (PATHPOST) is built beneath the PATHTEST level.
This feature needs the following features:
• AL0585 ENET Integrity Fault Handler
• AL0960 ENET Central Crosspoint Path Test Utilities
• AL0572 ENET MAP
• AL0583 ENET Connection Control
User interface
A new MAP level, PATHTEST, is provided from the ENET level. The
PATHTEST level contains a POST sublevel.

NTXE01AA–6 297-1001-801i Standard 09.01 January 2000

 NTXE01AA
AL0957
Feature name
ENET REX Test
Description
AL0957 supports the implementation of the enhanced network (ENET)
routine exercise (REx) test. The test is invoked automatically once per day
under system action, or can be invoked as a manual action through a MAP
(maintenance and administration position) command. The test ensures that
all functions and recovery modes of the ENET hardware are operational.
The following sets of tests are provided:
• ENET node test – verifies the message switch (MS) to ENET
communications link synchronization hardware and verifies basic node
sanity (AL0853 – ENET Matrix Test)
• ENET matrix test – verifies that the crosspoint and interface switching
hardware is functional (AL0853 – ENET Matrix Test Software)
• a mechanism for adding future tests

BCS history
This feature was created in BCS30.
Hardware requirements
This feature is part of the ENET card maintenance.
Pack diagnostic specifics
This feature provides diagnostics that improve the coverage of all cards in
the ENET:
• NT9X35BA – crosspoint circuit pack
• NT9X40BA – DS512 link interface paddle board
• NT9X41BA – DS30 link interface paddle board

Restrictions and limitations

An ENET REx test cannot be performed while other REx tests are being
performed.
Feature interactions
Operational measurement pegs and alarms normally generated for certain
system actions are suppressed if intentionally activated due to the routine
exercise (for example, a system busy action).

Feature Description Manual Volume 2 of 3 BCS44.1i NTXE01AA–7

NTXE01AA
AL0958
Feature name
ENET PM Table Control Modifications
Description
AL0958 allows peripheral modules (PM) to be datafilled onto the enhanced
network (ENET) through PM table control software. This feature provides
support for datafilling XMS-based peripheral modules (XPM) connected by
a fiber link to the ENET. Such peripheral modules are known as fiber
XPMs.
The feature also enhances the TRNSL command so that ENET link
information is displayed.
BCS history
This feature was created in BCS29.
Feature interactions
This feature is part of the ENET development project.
Datafill
Table Description

LTCINV Table is modified.

MSBINV Table is modified.
IACINV Table is modified.
TACINV Table is modified.
TMINV Table is modified.
LMINV Table is modified.
DCMINV Table is modified.
OFCOPT New parameter ENET_MAX_CHANNEL_GROUP is added.

The tables LTCINV, MSBINV, IACINV, TACINV, TMINV, LMINV, and

DCMINV are modified to accept C-side links connected either to old
junctored networks or to non-blocking junctorless networks.
User interface
The information displayed by the TRNSL command at the PM level of the
MAP is changed to display link information for the posted PM. This feature
enhances the C-side link display for PMs connected to networks to print
ENET link information in the correct form.

NTXE01AA–8 297-1001-801i Standard 09.01 January 2000

 NTXE01AA
AL0959
Feature name
ENET Shelf Test
Description
AL0959 provides a single diagnostic that supplies coverage for all switching
matrix components within a single shelf of an enhanced network (ENET).
BCS history
This feature was created in BCS30.
Hardware requirements
The shelf test is to be used for the ENET.
Feature interactions
This feature is part of a group of features that provide diagnostic coverage
for the ENET and requires the following features:
• AL0853 ENET Matrix Test SW
• AL0957 ENET REX Test
• AL0850 ENET System Recovery

Feature Description Manual Volume 2 of 3 BCS44.1i NTXE01AA–9

NTXE01AA
AL0960
Feature name
ENET Path Diagnostics
Description
AL0960 provides diagnostics for 128K channels through the enhanced
network (ENET) switching matrix. This feature provides support in
response to integrity failures, peripheral-side (P-side) link maintenance
requests, and command interface (CI) commands.
BCS history
This feature was created in BCS27.
Feature interactions
This feature is a component of the ENET node maintenance software. The
feature provides a low-level function to perform integrity handling, P-side
link maintenance, and CI commands.

NTXE01AA–10 297-1001-801i Standard 09.01 January 2000

 NTXE01AA
AL1230
Feature name
ENET MAP Enhancements
Description
AL1230 defines the enhancements for the man-machine interface for the
enhanced network (ENET). This includes the various logs generated and all
MAP (maintenance and administration position ) levels. This feature
supercedes all previous features that describe ENET MAP levels and all
ENET logs.
BCS history
This feature was created in BCS31.
Hardware requirements
This feature is not restricted to any hardware configuration. It supports the
DMS matrix (ENET), which involves a full configuration DMS SuperNode
equipped with at least one DMS matrix node.
Restrictions and limitations
An ENET can be equipped only on an enhanced core switch. In addition,
the MAP directly affects the existing network MAP and its various
sublevels. The ENET replaces the existing network MAP, including the
network top-level alarm.
Feature interactions
This feature is part of the ENET development project. The existing network
MAP levels are replaced by the new ENET levels. The top-level NET alarm
becomes ENET and shows the alarm for the ENET. The menu position
within the MAP to enter the network maintenance level is changed from
NET to ENET.
Logs
The logs in this feature provide completeness and centralization of the
various ENET logs within one document. This feature also reflects the
information necessary for the proper operation of an ENET.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXE01AA–11

NTXE01AA
AL2038
Feature name
ENET Support for 9X45BA
Description
AL2038 provides the following support for the NT9X45BA paddle board:
• new test diagnostics
• modifications to existing test diagnostics
• modifications to maintenance software
• modifications to connection control
• modifications to tools

The NT9X45BA contains three DS512 links and sixteen DS30 links. It can
be used in place of the existing NT9X40BA or NT9X41BA paddle boards.
BCS history
This feature was created in BCS33.

NTXE01AA–12 297-1001-801i Standard 09.01 January 2000

 NTXE01AA
AL2107
Feature name
Enable A-Law
Description
AL2107 provides the software required to support the introduction of ENET
into an international A-law environment.
BCS history
This feature was created in BCS33.
Hardware requirements
This feature requires ENET paddle boards equipped with the S02F version
of the DS512 transmit and receive controller (DTRC) application-specific
integrated circuit (ASIC).
Restrictions and limitations
This feature is available only in SuperNode offices equipped with ENET.
Feature interactions
This feature interacts with features AL0578 (9X35 Mtce S/W) and AL1069
(ENET Card Maintenance).
This feature needs the following features:
• AE0385 Even Bit Inversion (EBI) CC Support
• AE0927 Even Bit Inversion (EBI) Enhancements
• AL0470 ENET Database

Feature Description Manual Volume 2 of 3 BCS44.1i NTXE01AA–13

NTXE01AA
AL2162
Feature name
NT9X45 MMI
Description
AL2162 implements the following man-machine interface (MMI) support
for the enhanced network (ENET) NT9X45BA paddle board:
• ENET card table control support
• MAP card level support
• MAP PM isolation warnings
• ENET card maintenance log support
• ENET diagnostic log support
• ENET PSlink and ENET call processing log support
• ENET retrofit and ENET PM table control support

BCS history
This feature was created in BCS33.
Restrictions and limitations
ENET MMI software is active only in SuperNode offices that are equipped
with ENET.
Feature interactions
This feature interacts with features AL1230 (ENET MAP Enhancements)
and AL2038 (ENET Support for 9X45BA).
Datafill
Table Description

ENCDINV Table is modified.

LMINV Table is modified.
TMINV Table is modified.
LTCINV Table is modified.
DCMINV Table is modified.
MSBINV Table is modified.
IACINV Table is modified.
HSIINV Table is modified.
CFPINV Table is modified.

NTXE01AA–14 297-1001-801i Standard 09.01 January 2000

 NTXE01AA
AL2162
The value DS_30_DS_512_INTERFACE is added to field PBTYPE in table
ENCDINV.
A value for the new NT9X45BA paddle board is added to field PBPEC in
table ENCDINV.
The range of values for field ENLINK in tables LMINV, TMINV, LTCINV,
DCMINV, MSBINV, IACINV, HSIINV, and CFPINV is expanded to
0 to 18.
Logs
Log ENET112 is generated when ENET card tests fail.
User interface
Directory ENETDS512DIR is modified.
Directory ENETDS30512DIR is added.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXE01AA–15

NTXE01AA
AL2260
Feature name
Support for Warm SWACT Recovery Time Reduction Feature
Description
AL2260 enhances the current ENET system recovery mechanism and
ensures proper recovery of ENET nodes, cards, and links after a no-restart
warm switch of activity (SWACT).
BCS history
This feature was created in BCS33.
Restrictions and limitations
This feature applies only to switches equipped with ENET.
Feature interactions
This feature interacts with the following features:
• AG2149 CC Warm SWACT Restart Outage Reduction—Phase I
• AG2276 CC Warm SWACT Restart Outage Reduction—Phase II
• AQ0738 DMS-bus SWACT Reduced Restart High Level Design

NTXE01AA–16 297-1001-801i Standard 09.01 January 2000

 NTXE01AA
AR0005
Feature name
64K ENET Support
Description
AR0005 provides maintenance and call processing support for a one-cabinet
(two shelves, two planes, 64K channels) enhanced network (ENET).
BCS history
This feature was created in BCS34.
Restrictions and limitations
This feature does not support an upgrade from 64K to 128K ENET.
Datafill
Table Description

ENINV PRI64K is added to the range of values for field ENCLASS to

specify the 64K ENET option.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXE01AA–17

NTXE01AA
AR0141
Feature name
ENET PSLINK Enhancements
Description
AR0141 modifies the enhanced network (ENET) software to ensure that
peripheral modules (PM) can be installed in a fiber optical network while
using less than 16 DS30 central side (C-side) links for each unit (equivalent
capacity).
BCS history
This feature was created in BCS34.
Restrictions and limitations
This feature requires a SuperNode office with an active ENET.
Datafill
Table Description

DCMINV, In each table, field ENDS30 is added to specify DS30

IACINV, equivalents within a fiber link (range of values is 0 to 15, for
LMINV, and DS30 links value = 0).
LTCINV
MOVEDCM, In each table, field ENSLOT is changed from numeric range of
MOVELM, values to symbolic values. All MOVE tables are used only
MOVELTC, during the JNET/ENET retrofit procedure.
MOVEMSB,
MOVETM,
MSBINV, and
TMINV

This feature increases program store by a maximum of 10 Kbytes and

increases data store by a maximum of 1 Kbyte.
Logs
This feature modifies logs ENET306 and ENET307.
Log ENET306 is generated when a peripheral side (P-side) link switches
from a manual busy or unequipped state to an offline state.
Log ENET307 is generated when a P-side link switches from an offline state
to an unequipped state.

NTXE01AA–18 297-1001-801i Standard 09.01 January 2000

 NTXE01AA
AR0141
User interface
This feature modifies MAP commands STATUS, PMTRNSL, and
PMMOVEINV in directory ENRETRODIR. The output of these commands
is modified to include information on the bandwidth of the fiber links.
These commands are used only during the JNET/ENET retrofit procedure.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXE01AA–19

NTXE01AA
AR0186
Feature name
ENET Integrity Fault Handling and HMI Enhancements
Description
AR0186 modifies the enhanced network (ENET) integrity fault handler and
human-machine interface (HMI) of the ENET integrity level to improve
integrity fault handling and to provide a more user-friendly interface to
analyze integrity statistics.
BCS history
This feature was created in BCS35.
Logs
This feature modifies logs ENCP100 to 102.
Logs ENCP100 and ENCP102 are generated when an integrity fault is
reported by a peripheral module (PM) and the connection is not yet taken
down.
Log ENCP101 is generated when a PM reports an integrity fault for a
connection that no longer exists when the integrity fault handler begins
analyzing the report.
User interface
This feature modifies MAP (maintenance and administration position)
commands ANALYZE, DISPLAY, FILTER, and THRESH in directory
ENINTEGDIR.
Command ANALYZE displays card integrity statistics for one plane of the
ENET matrix.
Command DISPLAY displays integrity statistics for each ENET plane
displayed.
Command FILTER allows operating company personnel to modify the
parity threshold for a specified extended peripheral module (XPM).
Command THRESH sets the thresholds for the counters to the values
provided.
This feature renames MAP command CAPTURECCB to DISPCCB, and
deletes MAP command SETINTG from directory ENINTEGDIR.

NTXE01AA–20 297-1001-801i Standard 09.01 January 2000

 NTXE01AA
TA0392
Feature name
ENET 16-Mbyte Processor (NT9X13KA)
Description
This feature propagates the functionality required for the NT9X13KA
(ENET processor card) into the DMS network for the international market.
The NT9X13KA processor card increases the memory on the ENET
processor card from 4 Mbytes to 16 Mbytes.
Release history
This feature was created in BCS42i.
Hardware requirements
This feature supports the NT9X13KA processor card.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXE01AA2–21

 NTXE29AA
BCS Process Enhanced
This feature package applies to DMS-100 offices.
This feature package modifies the batch change supplement (BCS) delivery
capability. This feature package gives customers increased control over the
switch by reducing the out-of-sync time required for an on-site dump and
restore by enabling customers to have their own dump and restore process
locally on-site.
This feature package also provides customers with tools for the
identification and correction of inconsistencies within the switch operating
system. These tools are used in the software delivery process, after which
they become part of the operating system and reside in the central control
(CC) for use by the customer at any time.
Feature package contents
Feature package NTXE29AA
Feature number Description

AG1560 Dump and Restore: Check Command Enhancements

AG1570 Dump and Restore: Progress Reporting
AG1563 Dump and Restore: Real Time Savings
AG1511 BCS Application Driver
AG1513 Caching DMOPRO
AG1506 Table Checksum Delta

BCS history
This feature package was created in BCS28.
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic

Feature Description Manual Volume 2 of 3 BCS44.1i NTXE29AA–1

NTXE29AA
AG1506
Feature name
Table Checksum Delta
Description
AG1506 implements a tool to compare customer data tables between the old
batch change supplement (BCS) and the new BCS during a BCS application.
This feature uses a checksum algorithm to avoid transferring entire tables.
BCS history
This feature was created in BCS29.
Feature interactions
This feature interacts with the following features:
• AG1511 Application Driver
• AG1571 Dump and Restore: Convert the Dump and Restore
User interface
The command DELTA is added. This command does a delta on the table
specified on the active and inactive sides using a checksum facility.

NTXE29AA–2 297-1001-801i Standard 09.01 January 2000

 NTXE29AA
AG1511
Feature name
BCS Application Driver
Description
AG1511 provides a universal method for performing the application phase
of a batch change supplement (BCS) update. This feature eliminates over
10 000 lines of execs, provides a simple user interface, and offers a faster
BCS application process.
BCS history
This feature was created in BCS29.
Feature interactions
This feature interacts with BC1675 (Enhanced Data Transfer [EDT]) for
communication between active and inactive processors. The application
driver uses enhanced data transfer to transfer device status information,
command the operation on the active processor, and transfer information
between processors for quality checking.
This feature also interacts with AG1571 (Dump Restore Driver) and
AG1506 (Table Checksum Delta).
User interface
The command interpreter (CI) level BCSUPDATE has been added to access
the commands needed for the BCS update.
The following commands are added to the BCSUPDATE level:
• OVERRIDE
• POSTSWACT
• PRESWACT
• QUIT
• RESET
• STATUS

Feature Description Manual Volume 2 of 3 BCS44.1i NTXE29AA–3

NTXE29AA
AG1513
Feature name
Caching DMOPRO
Description
AG1513 provides a cache for the data dictionary and provides fast access to
data items that are accessed frequently. This feature modifies performance
of table dumps; this benefits logical data transfer during the BCS application
process.
BCS history
This feature was created in BCS29.
Restrictions and limitations
The limitations of this feature are dependent on the size of the cache.
User interface
Data dictionary caching does not provide a user interface. The caching
procedures are integrated into the existing data dictionary.

NTXE29AA–4 297-1001-801i Standard 09.01 January 2000

 NTXE29AA
AG1560
Feature name
Dump and Restore: Check Command Enhancements
Description
AG1560 provides a utility named CHECKTAB, which checks the data
integrity of all tables in an office and reports the data entries that need to be
corrected. After the corrections, CHECKTAB can be re–run to ensure that
the data within the tables is correct. This process reduces manual
intervention during the batch change supplement (BCS) application and
speeds up the dump and restore process.
BCS history
This feature was created in BCS28.
Restrictions and limitations
Only one CHECKTAB with the option FROM or ALL can be run at a time
on a switch.
User interface
The command CHECKTAB is added. This command checks for corrupt
data in the tables on the Digital Mutiplex System (DMS). The CHECKTAB
command can verify the data in one table, over a range of tables, or all tables
using the ONLY, FROM, or ALL option.
The table editor command CHECK checks for corrupt data on an individual
tuple basis.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXE29AA–5

NTXE29AA
AG1563
Feature name
Dump and Restore: Real Time Savings
Description
AG1563 provides real time enhancements for non-call processing software
on the inactive CPU. The process priorities are modified to give the dump
and restore process high priority on the inactive side. This reduces the time
required to restore the office data.
BCS history
This feature was created in BCS29.

NTXE29AA–6 297-1001-801i Standard 09.01 January 2000

 NTEX29AA
AG1570
Feature name
Dump and Restore: Progress Reporting
Description
AG1570 provides a dump and restore table (DART) that specifies the
datafill order for the dump and restore driver. DART stores statistics
pertaining to table data that is to be dumped. This table replaces the
sequence list.. An interface is provided to allow the CHECKTAB command
to update DART.
BCS history
This feature was created in BCS29.
Feature interactions
This feature interacts with the following features:
• AG1560 Dump and Restore: Check Command Enhancements
• AG1571 Dump and Restore Driver
Datafill
The following tables were modified for this feature:

Table Description

DART New table is added.

REFORMAT New table is added.

A new table – DART – is added and is used to determine the datafill order
during a dump and restore. This table is also used by the CHECKTAB to
keep tuple counts and check failures. This table can be updated using only
the dump and restore driver (MOVEBCS command) and the CHECKTAB
command.
A new table – REFORMAT – is added and is used for testing in a lab
environment. The REFORMAT table links several external views of table
data to one table.

Feature Description Manual Volume 2 of 3 BCS44.1i NTEX29AA–7

 NTXE54AA
SLM II Enhancements
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTXE54AA
Feature number Description

AL1065 SLM II Maintenance Software

AL1174 SLM II Enhancements

BCS history
This feature package was created in BCS30.
Required feature packages
Feature package Description
number

NTX940AA CM Bilge
NTX941AA CM Common
NTX942AA SuperNode System Load Module
or
NTX942AB DMS – Supernode System Load Module
NTX950AA MS Bilge
NTX951AA MS Common

Feature Description Manual Volume 2 of 3 BCS44.1i NTXE54AA–1

NTXE54AA
AL1174
Feature name
SLM–II Enhancements
Description
AL1174 implements the system load module (SLM) maintenance software
required to support the SLM–II. This feature supplements SLM I software
to provide increased storage capacity offered by SLM II devices.
BCS history
This feature was created in BCS29.
Hardware requirements
This feature requires a DMS Supernode switch equipped with a computing
module (CM) extension shelf containing the following cards:
• NT9X27AA
• NT9X27BA
• NT9X12
• NT9X46
• NT9X44

Restrictions and limitations

This feature is required only for the operation of SLM II devices on a DMS
Supernode switch. Without this feature, SLM II devices do not operate and
cannot be manipulated from the DMS MAP (maintenance and
administration poistion) terminal.
Feature interactions
This feature requires the following cards to operate:
• AG0367 SLM Basic File System – CI Utilities
• AG0369 SLM Basic File System – File Management
• AG0372 SLM Basic File System – General Utilities
• AG0373 SLM Basic File System –Device Management
• AL0436 System Load Module Control Software
• AL0437 System Load Module Input Output System
• AL0444 SLM Firmware – Firmware Enhancements
• AL0445 SLM – Boot Loading
• AL0467 NT9X44AA System Load Unit Firmware
This feature interacts with AL1060 (SLM Phase II – Disk and Tape
Replacements).

NTXE54AA–2 297-1001-801i Standard 09.01 January 2000

 NTXF15AA
DMS-core MC68030 33 MHz Processor
This feature package provides software support for the NT9X13GA card
within the maintenance system of the DMS-core in a DMS SuperNode.
Existing diagnostics are modified to function with the NT9X13GA card and
new diagnostics are added to cover the increased functionality provided by
the NT9X13GA.
This feature package applies to DMS SuperNode offices.
Feature package contents
Feature package NTXF15AA
Feature number Description

AL0934 Software Support for 68030 at 33 MHz

BCS history
This feature package was created in BCS29.
Required feature packages
Feature package Description
number

NTX957AA MS Common

Feature Description Manual Volume 2 of 3 BCS44.1i NTXF15AA–1

NTXF15AA
AL0934
Feature name
Software Support for 68030 at 33 MHZ
Description
AL0934 provides software support for the NT9X13GA card within the
maintenance system of the DMS-core in a DMS SuperNode. Existing
diagnostics are modified to function with the NT9X13GA card and new
diagnostics are added to cover the increased functionality provided by the
NT9X13GA.
BCS history
This feature was created in BCS29.
Hardware requirements
This feature requires the following hardware:
• CPU firmware – NT2V13AA
• DMS-bus processor card – NT9X13DB
• single processor subsystem card – NT9X13CA
• DMS-core processor (MC68020) card – NT9X13BC
• DMS-core processor (MC68030) card – NT9X13EA
• DMS-core processor (MC68030 HPM) card – NT9X13GA
User interface
Command SYNC is modified to accommodate the NT9X13GA card.

NTXF15AA–2 297-1001-801i Standard 09.01 January 2000

 NTXF20AA
LPP on DMS-100 SuperNode for CCS7
This feature package enables the use of link peripheral processors (LPP) to
terminate Common Channel Signaling 7 (CCS7) signaling links on DMS
SuperNode service switching point offices, and to enable the routine
exercise test for the LPP.
This feature package applies to SuperNode and DMS-100 offices.
Feature package contents
Feature package NTXF20AA
Feature number Description

AI0036 Link Interface Module Local Control

AI0038 MAP for the STP LIM
AI0039 OMs and Logs for the STP LIM
AI0040 Table Control for STP LIM
AI0103 STP LIM Clock Diagnostic
AI0116 LIM CM MTC I
AI0117 STP LIM Local MTC
AI0118 LIM CM MTC II
AI0167 Link Interface Module Maintenance Enhancements
AL1271 REX Test on LPP
AL1895 LMS Isolation
AL2334 SRC Controlled Restart and No-Restart SWACT Support
AQ1030 LPP(LMS) Autoloading
AQ1031 Mapper Refresh on LMS State Transition
AQ1070 NT9X13DD Standalone Support in the LMS

BCS history
This feature package was created in BCS25.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXF20AA–1

NTXF20AA
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX940AA CM Bilge
NTX941AA CM Common
NTX950AA MS Bilge
NTX951AA MS Common
Either
NTX942AA DSM-SuperNode System Load Module (SLM)
or
NTX942AB DSM-SuperNode System Load Module (SLM)
Either
NTXF71AA SuperNode Enhanced Messaging
or
NTXF71AB SuperNode Enhanced Messaging

NTXF20AA–2 297-1001-801i Standard 09.01 January 2000

 NTXF20AA
AL2334
Feature name
SRC Controlled Restart and No-Restart SWACT for CCS7
Description
This feature allows the system recovery controller (SRC) to control the
recovery of Common Channel Signaling 7 (CCS7) links, linksets, routesets,
and pools during warm, cold, and reload restarts, or during a no-restart
switch of activity (SWACT).
BCS history
This feature was created in BCS36.
Restrictions and limitations
The no-restart SWACT for CCS7 offices is a function of office size, and
certain configurations may not meet the target maximum of 30 s for
complete switch recovery. Partial call processing will be available within
the 30-s limit.
This feature does not support the CCS7 part of service control point I (SCPI)
nodes.
This feature does not support the CCITT-based versions of signal connection
control part (SCCP).
Feature interactions
This feature is one of four features that function together to allow CCS7,
link peripheral processors (LPP), and ISDN user part (ISUP) to use the SRC
for core restart recovery. The other features are as follows:
• AI0704 SRC Restart and No-Restart SWACT Support for SCCP
and DDM
• AI0705 SRC Restart and No-Restart SWACT Support for LIMs
and LIUs
• AR0467 SRC Restart and No-Restart SWACT Support for ISUP

Feature Description Manual Volume 2 of 3 BCS44.1i NTXF20AA–3

NTXF20AA
AQ1030
Feature name
LPP (LMS) Autoloading
Description
This feature provides the local message switch (LMS) with the ability to
recover automatically from loss or corruption of its software load.
During a system-busy recovery, the maintenance system automatically starts
the reload of an LMS if there are indications that the software load is
missing or has been corrupted.
BCS history
This feature was created in BCS36.
Restrictions and limitations
The trigger for automatic reload of the LMS software is failure of the reset
and restart sequence. If some other fault causes the reset and restart to fail,
this feature will still initiate the reload sequence.
Logs
A log is generated when the recovery mechanism initiates a reload
sequence. This separates system-initiated reloads from manually initiated
reloads.
A log is also generated when the maintenance system reaches the threshold
number of recovery attempts and stops. The log shows the number of failed
recovery attempts, and indicates that manual action is required.
User interface
The MAP (maintenance and administration position) terminal that has a
given LMS posted displays a flag when that LMS is being automatically
reloaded.
The maintenance flags displayed during an automatic reload are the same as
those shown during a LOADPM command.
The MAP terminal displays a different flag (new for this feature) when the
maintenance system is in periodic reload phase, or has stopped recovery.
This flag tells operating company personnel that manual action is required.

NTXF20AA–4 297-1001-801i Standard 09.01 January 2000

 NTXF20AA
AQ1031
Feature name
Mapper Refresh on LMS State Transition
Description
This feature improves the robustness of the local message switch (LMS)
recovery from the system-busy state.
BCS history
This feature was created in BCS36.
Feature interactions
This feature interacts with the frame transport system (FTS). Requests are
made to the FTS, which then causes the message switch (MS) mapper to be
re-initialized. This results in messaging traffic between the computing
module (CM) and the MS.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXF20AA–5

NTXF20AA
AQ1070
Feature name
NT9X13DD Standalone Support in the LMS
Description
This feature provides the NT9X13DD card (processor with 16 Mbyte of
DRAM) with optional memory card capability when it is used in the local
message switch (LMS). The feature enhances both the central and local link
interface module (LIM) software to support the NT9X13DD card as a
stand-alone processor without a memory card.
BCS history
This feature was created in BCS36.
Hardware requirements
This feature is invoked when the NT9X13DD processor card is configured
without an accompanying memory card. If no memory card is provisioned,
an NT9X19AA filler plate is inserted into either or both of slots 16 and 23.
Restrictions and limitations
The new memory configurations available on the LMS require that new
loads be built to access the added memory. There is currently no check to
determine if the configured memory will support a given LMS software
load.
Datafill
When a processor card is datafilled in table LIMCDINV, the memory card of
the same LMS is allowed to be un-datafilled. However, a fault will be
generated if an in-service memory card is not datafilled.
Command LOADPM will fail if a memory card is datafilled but is not
physically present in the LMS.

NTXF20AA–6 297-1001-801i Standard 09.01 January 2000

 NTXF70AA
SuperNode SN-20 Processor
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTXF70AA contents
Feature number Description

BC1826 Central and Message Switch Maintenance

BC1827 CM In-sync Maintenance Software
BC1909 Time-of-day Support for Enhanced Core
BC1932 Remote Login
BC2003 Distributed Logs System

BCS history
This feature package was created in BCS23.
Required feature packages
Required feature packages
Feature package Description
number

NTX940AA CM Bilge
NTX941AA CM Common
NTX950AA MS Bilge
NTX951AA MS Common
or
NTXF15AA DMS-core MC68030 33-MHz Processor
or
NTXF16AA DMS-core MC68030 40-MHz Processor
or
NTXF96AA SuperNode SN-10 Processor

Feature Description Manual Volume 2 of 3 BCS44.1i NTXF70AA–1

NTXF70AA
BC1826
Feature name
Central Message Switch Maintenance
Description
This feature provides message switch (MS) maintenance software.
MS maintenance software provides facilities for preventive maintenance,
diagnostics, fault isolation, configuration changes, and man-machine
interfaces (MMI).
The MS is a high-capacity packet switch that interconnects various
messaging subsystems. The MS routes messages in the DMS-100 switch.
The major enhancements are:
• larger message capacity and port fan out
• increased maximum message size
• built-in maintenance processor
• port-to-port messaging
• logical addressing of ports

MSs are configured as follows:

• Up to four shelves can be provisioned as MSs.
• Each MS consists of two MSs (MS 0 and MS 1) that have identical
configurations.
• Each MS can contain up to 26 cards (up to 52 cards for an MS pair).
• Each MS has I/O controllers (IOC) that connect the MS to
peripheral-side (P-side) peripheral modules (PM) such as video
terminals, magnetic tape drives, and disk drives.
• Each MS is connected to P-side networks that set up messaging and
speech paths between PMs or between PMs and the computing module
(CM).
• Each MS has message controllers (MC) connected as P-side nodes. The
MCs are connected through DS-512 fiber links and are used for
communication between the MS and the CM.
MS maintenance software supports the following functions:
• the command interpreter (CI) executing manually initiated commands
such as busy and return to service
• displaying the current state of the posted MS resources at the MAP
(maintenance and administration position) terminal
• datafilling MS resources and changing MS resource attributes (data
schema)

NTXF70AA–2 297-1001-801i Standard 09.01 January 2000

 NTXF70AA
BC1826
• mapping logical node identities to physical addresses, that is, cards and
ports in the MS
• coordinating MS maintenance activities with maintenance activities of
P-side PMs
• performing in-service and out-of-service audits to verify system integrity
• generating log reports of occurrences
• clearing faults on MS resources
• MS-related operational measurements
• synchronizing the MS clock with the clock of a designated switch in the
next higher stratum
The CM consists of a CM pair (CM 0 and CM 1) which have identical
configurations and occupy one shelf. The CM contains the CC image that
controls the maintenance and call processing capabilities of the system. The
CM is responsible for maintenance of the MSs, networks, IOCs, and all
P-side nodes of the networks and IOCs.
BCS history
This feature was created in BCS23.
Datafill
Table Description

MSCDINV This new table contains the MS card inventory. The MS

number, shelf number, slot number, card type, and PEC for the
MS cards are datafilled in this table.

Table MSINV must be datafilled before table MSCDINV.

MSINV This new table contains the identity, location, and product
engineering codes (PEC) of the MS, and the version and issue
of the MS software.
MSPTINV This new table contains the MS port inventory.

Operational measurements
The following operational measurement (OM) registers are added by this
feature:
• MSERR – the number of errors detected on the system cards of an
in-service MS
• MSCDERR – the number of errors detected for an in-service interface
card
• MSLKERR – the number of errors detected for an in-service MS link

Feature Description Manual Volume 2 of 3 BCS44.1i NTXF70AA–3

NTXF70AA
BC1826
• MSFLT – the number of errors previously registered in OM register
MSERR that justify taking the MS out of service
• MSCDFLT – the number of errors previously registered in OM register
MSCDERR that justify taking the MS card out of service
• MSLKFLT – number of errors previously registered in OM register
MSLKERR that justify taking the MS link out of service
• MSDIA – the number of diagnostic tests on the MS that are initiated by
the following events:
— the test command from the MS level of the MAP display
— in-service or out-of-service audits
— REx tests
• MSCCDIA – the number of diagnostic tests on an MS card that are
initiated by the following events:
— the test card command from the MS shelf and MS card levels of the
MAP display
— the return card to service command from the MS shelf and MS card
levels of the MAP display
• MSLKDIA – the number of diagnostic tests on an MS link that are
initiated by the following events:
— the test MS link command from the MS card level of the MAP
display
— the return MS link to service command from the MS card level of the
MAP display
— periodic in-service audits
— return to service attempts on system-busy MS links
• MSDIAF – the number of diagnostics previously registered in OM
register MSDIA that are failed
• MSCDDIAF – the number of diagnostics previously registered in OM
register MSCDDIA that are failed
• MSLKDIAF – the number of diagnostics previously registered in OM
register MSLKDIA that are failed
• MSMBP – the number of times the MS is manually busied
• MSCDMBP – the number of times an MS card is manually busied
• MSLKMBP – the number of times an MS link is manually busied
• MSMBU – the count of the time the MS is manual busy
• MSCDMBU – the count of the time MS interface cards are manual busy
• MSLKMBU – the count of the time MS links are manual busy
• MSSBU– the count of the time the MS is system busy

NTXF70AA–4 297-1001-801i Standard 09.01 January 2000

 NTXF70AA
BC1826
• MSCDSBU– the count of the time MS interface cards are system busy
• MSLKSBU – the count of the time MS links are system busy
Logs
The following MS logs are created by this feature:
• An MS100 log report is generated when an MS goes from manual busy
or system busy to in service.
• An MS101 log report is generated when an MS goes from in service to
manual busy.
• An MS102 log report is generated when an MS goes from system busy
to manual busy.
• An MS103 log report is generated when an MS goes from in service to
system busy.
• An MS104 log report is generated by the following events:
— an action by local MS maintenance
— a controlled action on an MS caused by a routine exercise (REx) test
— a controlled action on an MS caused by the loading process
• An MS208 log report is generated by an action on a front card by local
MS maintenance.
• An MS238 log report is generated by an action on a back card by local
MS maintenance.
• An MS248 log report is generated by an action on a system card by local
MS maintenance.
• An MS260 log report is generated when an MS interface card goes from
manual busy or system busy to in service.
• An MS261 log report is generated when an MS interface card goes from
in service to manual busy.
• An MS262 log report is generated when an MS interface card goes from
offline or control-side (C-side) busy to manual busy.
• An MS263 log report is generated when an MS interface card goes from
in service to system busy.
• An MS264 log report is generated when an MS interface card goes from
C-side busy to system busy.
• An MS265 log report is generated when an MS interface card goes from
system busy to C-side busy.
• An MS266 log report is generated when an MS interface card goes from
manual busy to offline.
• An MS267 log report is generated by an action on an MS interface card
by local MS maintenance.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXF70AA–5

NTXF70AA
BC1826
• An MS300 log report is generated when an MS port goes from manual
busy or system busy to in service.
• An MS301 log report is generated when an MS port goes from in service
to manual busy.
• An MS302 log report is generated when an MS port goes from system
busy, C-side busy, or P-side busy to manual busy.
• An MS303 log report is generated when an MS port goes from in service
to system busy.
• An MS304 log report is generated when an MS port goes from system
busy, C-side busy, or P-side busy to system busy.
• An MS305 log report is generated when an MS port goes from system
busy to C-side busy.
• An MS306 log report is generated when an MS port goes from system
busy to P-side busy.
• An MS307 log report is generated by an action on an MS port by local
MS maintenance.
User interface
The MS MAP display consists of the following functional levels:
• The MS level displays the states of the MS, MS shelf, and MS clocks,
and provides commands that act on the MS. The states displayed are in
service, manual busy, system busy, or unequipped.
• The Shelf level, which is accessed from the MS level, displays the state
of MS shelf, and the states of all cards on the specified MS shelf. The
commands provided at this level act on the specified MS cards. The
states displayed are in service, manual busy, system busy, offline, or
unequipped.
• The Card level, which is accessed from the Shelf level, displays the
states of the specified MS card and if applicable, the associated ports.
The commands provided at this level act on the specified cards and
ports. The states displayed are in service, manual busy, system busy, or
unequipped.
The following commands are available at one or more of the MS MAP
display functional levels:
• BSY manually busies the specified MS, MS card, or MS port.
• LOADCD loads firmware into the specified MS card.
• LOADMS loads software into the specified MS.
• QUERYCD displays information about electrically erasable
programmable read only memory (EEPROM) for the specified MS card.

NTXF70AA–6 297-1001-801i Standard 09.01 January 2000

 NTXF70AA
BC1826
• QUERYMS displays information about cards and chains in the active
MS.
• RTS returns the specified MS, MS card, or MS port to service.
• SWMAST switches clock mastership.
• TRNSL displays P-side information for all links, ports, and taps on the
specified MS card.
• TST tests the specified MS, MS card, or MS port, depending on the MS
MAP display functional level in which the command is executed.
The following MS alarms, which are displayed under the MS header in the
alarm banner of the MAP display, are added:
• Clock major. An MS clock is in-service trouble.
• nnCMIC minor. The indicated number (nn) of computing module
interface card (CMIC) links are out of service.
• Istb minor. The system has detected an in-service trouble on one or
more MS circuit cards.
• ManB major. An MS is manual busy.
• nnMBCD minor. The indicated number (nn) of MS interface cards are
manual busy.
• nnMBLK minor. The indicated number (nn) of MS ports are manual
busy.
• MSpair critical. Failure of an MS pair.
• REx minor. An MS is undergoing REx tests.
• nnSBCD minor. The indicated number (nn) of MS port cards are system
busy.
• nnSBLK minor. The indicated number (nn) of MS ports are system
busy.
• SysB major. An MS is system busy (removed from service due to a
system-detected fault).

Feature Description Manual Volume 2 of 3 BCS44.1i NTXF70AA–7

NTXF70AA
BC1827
Feature name
CM In-sync Maintenance Software
Description
This feature provides a maintenance system capable of supporting complete
simplex maintenance functions and basic synchronized operation of the
computing module (CM) processors.
This feature also provides
• mismatch handling capability, which generates a log report indicating the
nature of the mismatch
• I/O error detection and recovery, which provides fault detection and
recovery for the links (and associated hardware) that connect the CM to
the message switch (MS) pair
• memory fault detection and correction
• the resource management scheme (RSM) for CM maintenance

The CM contains the central control (CC) image that controls the
maintenance and call processing capabilities of the switch. The CM is
responsible for all maintenance of the MSs, networks, I/O controllers (IOC),
and all peripheral-side (P-side) nodes of the networks and IOCs.
The MS is a high capacity packet switch that interconnects various
messaging subsystems. The MS routes messages within the switch.
BCS history
This feature was created in BCS23.
Datafill
Table Description

CMSHELF This new table contains location information for CM shelves.

Each entry corresponds to a shelf which consists of at least part
of a CPU plane or memory system. Any cards provisioned on
this shelf get their physical location from entries in this table.
This datafill in this table is used to generate card lists for error
reports.

Operational measurements
The following operational measurement (OM) registers are added by this
feature:
• CMSSWACT – the number of activity switches resulting from system
action
• CMMSWACT – the number of activity switches initiated manually

NTXF70AA–8 297-1001-801i Standard 09.01 January 2000

 NTXF70AA
BC1827
• CMRSWACT – the number of activity switches caused by a routine
exercise (REx) test
• CMSWINIT – the number of warm restarts resulting from system action
• CMMWINIT – the number of warm restarts initiated manually
• CMSCINIT – the number of cold restarts resulting from system action
• CMMCINIT – the number of cold restarts initiated manually
• CMTRMISM – the number of transient mismatches
• CMDPSYNC – the number of times the CM dropped synchronization
due to a mismatch interrupt
• CMTRAP – the number of fault traps
• CMCPUFLT – the number of CPU faults detected
• CMMEMFLT – the number of memory faults detected
• CMSSCFLT – the number of subsystem clock (SSC) faults detected
• CMMCBSY – the number of times a message controller (MC) went
system busy
• CMREXFLT – the number of times system REx tests were cancelled
• CMRCPUFL – the number of times a CPU REx test failed
• CMRMEMFL – the number of times a memory REx test failed
• CMRSSCFL– the number of times an SSC REx test failed
• CMRMCFL– the number of times an MC REx test failed
• CMSSMPXU – the count for the time the CM was running in the
simplex mode as a result of system action
• CMMSMPXU – the count for time the CM was running in the simplex
mode as a result of manual action
• CMRSMPXU – the count for the time the CM was running in the
simplex mode as a result of REx tests
Logs
The following CM logs are created by this feature:
• A CM100 log report is generated every 24 h and summarizes the results
of audits of the overall condition of the CM. The following events are
reported:
— the number of times checksum ran to completion
— the number of traps encountered
— which CM maintenance (CMMNT) alarms are disabled
— the number of correctable errors for each CM card

Feature Description Manual Volume 2 of 3 BCS44.1i NTXF70AA–9

NTXF70AA
BC1827
• A CM101 log report is generated whenever there is a change in the state
of the CM, such as a change in synchronization, activity, or split CM
mode.
• A CM102 log report is generated once an hour if the CM is out of
synchronization.
• A CM103 log report is generated when the CM is experiencing a high
trap rate. The trap rate is reported.
• A CM104 log report is generated when the state of an MC on the CM is
changed to system busy. The MC affected and the reason for the state
change are reported.
• A CM105 log report is generated when an MC on the CM goes
control-side (C-side) busy. The MC affected and the reason for the state
change are reported.
• A CM106 log report is generated when an MC on the CM goes manual
busy. The MC affected and the reason for the state change are reported.
• A CM107 log report is generated when an MC on the CM is in service
trouble. The MC affected and the reason for the state change are
reported.
• A CM108 log report is generated when an MC on the CM is returned to
service. The MC affected is reported.
• A CM111 log report is generated when the amount of memory falls
below a predetermined limit. The amount of memory remaining is
reported.
• A CM112 log report is generated when a memory card has failed a
memory test, has a faulty memory location, or the number of transient
errors exceeds the threshold. The memory card affected is reported.
• A CM113 log report is generated when a memory card is in service
trouble. The memory card affected is reported.
• A CM114 log report indicates that the specified memory card has
successfully passed a memory test after being in service trouble or in a
faulty state.
• A CM116 log report is generated when an image test fails.
• A CM117 log report indicates that an image test was run on the indicated
CPU and was successful.
• A CM118 log report is generated once an hour if at least one resource
management scheme (RMS) request was delayed. The reason for the
delay is reported.
• A CM119 log report is generated when a trap occurs. The following
items are reported:
— the reason for the trap

NTXF70AA–10 297-1001-801i Standard 09.01 January 2000

 NTXF70AA
BC1827
— information about what part of the program was executing when the
trap occurred
— a traceback of the procedures completed before the trap occurred
— information related to the trap or forced interrupt reason
• A CM120 log report is generated after a system restart.
• A CM121 log report is generated when a routine exercise (REx) test runs
and passes.
• A CM122 log report is generated when a REx test runs and fails.
• A CM123 log report is generated when at least one of the CPUs is
running short of spare memory.
• A CM124 log report is generated when a CPU test runs and passes.
• A CM125 log report is generated when a CPU test runs and fails.
• A CM126 log report is generated when the primary autoload device is
changed.
• A CM127 log report is generated when an audit runs and the MC link
has a fault.
• A CM128 log report is generated when an MC link fault is detected.
• A CM150 log report provides a record of successful synchronization
attempts.
• An MM100 log report is generated when a transient mismatch is handled
by the software mismatch handler and control is passed to the mismatch
analysis process. The following items are reported:
— internal processor register information
— a dump of some of the CPU maintenance registers and portions of
the user and interrupt stacks
• An MM101 log report is generated when a non-transient mismatch is
handled by the software mismatch handler and control is passed to the
mismatch analysis process. The following items are reported:
— internal processor register information
— a dump of some of the CPU maintenance registers and portions of
the user and interrupt stacks

Feature Description Manual Volume 2 of 3 BCS44.1i NTXF70AA–11

NTXF70AA
BC1827
User interface
The CM MAP (maintenance and administration position) display consists of
the following levels:
• The CM level provides the commands that test, control and display the
state of the paired CPUs that comprise the CM. The states displayed are
CPUs synchronized, CPUs not synchronized, and CM in the split mode.
The CM level MAP display also indicates which CPU (CPU 0 or CPU 1)
is active, a CPU fault, a CPU under test, if a CPU has failed a REx test,
and if the inactive CPU is jammed.
• The CM Memory level provides the commands that test and manipulate
contents of memory cards. The states displayed are no memory faults, a
correctable memory fault on one or more memory modules, a
non-correctable memory fault on one or more memory modules, memory
under test, and no memory card found.
• The CM MC level provides the commands to test and control the MCs.
The MC states displayed are no faults, in-service trouble, control-side
(C-side) busy, manual-busy, and system-busy.
• The CM CMMnt level is used to generate information about the
performance and available memory in the CM, and to control the load
image and the CMMnt level alarms. The states displayed are no faults,
low spare memory, low memory, corrupted autoload register, trap rate
higher than the pre-defined limit, and image test failed in the inactive
CM.
The following CM alarms, that are displayed under the CM header on the
alarm banner of the MAP display, are added:
• Autold minor. A corruption or error condition exists that prevents an
automatic reload of the switch.
• CM Flt major. A fault exists in one of the CPUs.
• CMTrap major. The trap rate is approaching a threshold that may cause
a restart.
• Image critical. The CM software load on the inactive CPU cannot
survive a restart.
• JInact minor. The mate CPU is jammed.
• LowMem minor. The CM is running out of available memory.
• LowSpr minor. The CM is running out of available spare memory on
one CPU.

NTXF70AA–12 297-1001-801i Standard 09.01 January 2000

 NTXF70AA
BC1827
• MCFlt major. A fault or error condition exists on at least one MC.
• MCTbl minor. At least one MC is in service trouble, has a faulty
subsystem clock, or has a faulty time-of-day clock.
• MemCor minor. A correctable memory fault has occurred.
• MemFlt major. A non-correctable memory fault has occurred.
• NoTOD critical. No accurate time-of-day clocks are available.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXF70AA–13

NTXF70AA
BC1909
Feature name
Time of Day Support for Enhanced Core
Description
This feature provides software support for the maintenance of the following:
• Computing module (CM) time-of-day (TOD) clocks. TOD clock faults
and errors are reported, and the software attempts to recover from these
faults and errors. The software synchronizes TOD clocks and ensures
that the synchronization is maintained within defined tolerances. The
software also provides the capability to read from and write to TOD
clocks.
• CM subsystem clocks (SSC). The capability to test and maintain SSC is
provided. The software checks clock diagnostics provided by firmware.
The software also provides intrinsics that monitor and switch between
the DS512 links supplying SSC with a reference frame pulse.
The TOD clocks are provided as part of the message controller (MC). There
are two message controllers, each containing two CPU port cards with a
TOD clock (a total of four TOD clocks). Each TOD clock obtains its
clocking signal from one of the two SSC. Each SSC obtains its clocking
signals through DS512 links to the message switches (MS).
BCS history
This feature was created in BCS23.
Logs
The following logs are added by this feature:
• The CM109 log reports the loss of TOD clock accuracy.
• The CM110 log reports TOD faults detected on the MC.
• The CM115 log reports SSC faults detected on the CM.

The following logs, which report changes in MC state, have been changed
by this feature:
• CM104 (system-busy MC). TOD clock faults and SSC faults are added
to the reasons for the state change.
• CM106 (manual-busy MC). MC states todf (TOD clock fault) and sscf
(subsystem clock fault) are added.
• CM107 (MC is in service trouble). TOD clock faults and SSC faults are
added to the reasons for the state change.
• CM108 (return to service of an MC). MC states todf (TOD clock fault)
and sscf (subsystem clock fault) are added.

NTXF70AA–14 297-1001-801i Standard 09.01 January 2000

 NTXF70AA
BC1909
User interface
The following commands are added to the MC level of the MAP
(maintenance and administration position) display:
• TST is used to initiate diagnostic tests of an entire MC, an MC TOD
clock pair, or an SSC.
• RTS is used to return an MC or an SSC to service.

The alarm NoTOD critical is added. This alarm is displayed, at the MTC
level of the MAP display, under the CM header of the alarm banner. The
NoTOD critical alarm indicates that there are no accurate MC TOD clocks
available because
• faults have been detected on all TOD clocks, or
• the TOD clocks have been stopped at zero following the loss of a reliable
time value
At the CM level of the MAP display, the MC state indicator flt is added to
indicate that one or more MC SSCs are faulty.
At the CM MC level of the MAP display, the following clock state
indicators are added:
• todf under the MC 0 and MC 1 headers indicates that a fault has been
detected on one or both of the TOD clocks for an MC
• sscf under the MC 0 and MC 1 headers indicates that a fault has been
detected on one or both of the SSC supplying the MCs with timing
information
• flt under the SSC 0 or SSC 1 headers indicates that a fault has been
detected on the indicated SSC
Automatic message accounting
A loss of all TOD clocks results in the loss of all call billing information.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXF70AA–15

NTXF70AA
BC1932
Feature name
Remote Login
Description
This feature allows operating company personnel to log into the message
switch (MS) from the computing module (CM). This feature is required
because it is not possible to log directly into the MS.
The remote login feature provides the capability to view logs generated on
the MS and to perform maintenance activities such as manually busying or
returning to service I/O ports.
BCS history
This feature was created in BCS23.
Restrictions and limitations
The user can be logged in to only one MS at a time (MS 0 or MS 1).
The user can be logged into two nodes from the the same terminal (the CM
and MS 0 or MS 1). However, only one terminal session at a time can be
active. The other session is suspended.
The user can only log out of an active terminal session.
The command FORCEOUT works only on other users logged in on the
same node as the active terminal session.
Feature interactions
This feature requires features BC2247 (Message Transport System Phase 2)
and BC1833 (Distributed File System) to handle communication between
nodes.

NTXF70AA–16 297-1001-801i Standard 09.01 January 2000

NTXF70AA NTXF70AA
BC2003 BC2003
Feature name
Distributed Log System
Description
This feature adds an easily understood origination identification to every log
report. A new log, that precedes every log sent to an output device, is added
to identify the origin (affected node) for the log.
This feature implements mutual exclusion of logs so that log reports from
different nodes in the same system are not intermixed when they are printed
on the same output device.
BCS history
This feature was created in BCS23.
Datafill
Table Description

OFCVAR Office parameter ECORE_FORMAT is added to determine if the

new log header is used.

Logs
A entry is added to the beginning of every log report to identify where the
log was generated.
The switch identification part of the log header is expanded to contain a
three-character node name and a three-digit node number. In the “report(s)
not printed” message, the three-character node name and the three-digit node
number are inserted between the count and the word “report(s)”. The new
log report format is optional and can be selected through datafill in table
OFCVAR.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXF70AA–17

 NTXF71AB
SuperNode Enhanced Messaging
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTXF71AB contents
Feature number Description

AI0037 Separate MMI from Control

AI0047 FTS Phase 1
AI0051 TPS 3.5 (SOS)
AI0123 FTS Robustness and Fault Handling
AI0124 Buffer Management System
AI0126 TPS Robustness and Performance Improvements
AL1010 Physical Link Maintenance Base II
AL1276 ILM Connection Support II
AL1277 ILM VCM Support for ISN I
AL1278 ILM MCM Support for ISN I
AL1279 ILM Connections Support I
AL1280 ILM VCM Support for ISN II
AL1281 ILM MCM Support for ISN II
AL1655 ILM Central Resource Controller Enhancement
AL1656 ILM Local Controller Enhancements
AL1657 Virtual Channel Maintenance Enhancements for ISN
AL1658 ILM Capacity and Performance Enhancements
AL1659 ILM Enhanced Diagnostics
AL1660 VCM Support for Reduced Capability Virtual Channels
AL1663 Message Base Enhancements for ISN
AL1664 MRS Support for AP Split Mode
AL1740 ILM Notification Service Enhancements
AL2129 ILM Logs & OMS II
AL2130 ILM Support for Warm-spared Nodes
AR0124 ILM Fault Isolation Enhancements

—continued—

Feature Description Manual Volume 2 of 3 BCS44.1i NTXF71AB–1

NTXF71AB
Feature package NTXF71AB contents (continued)
Feature number Description

AR0125 ILM Isolation Detection Enhancements

AR0128 ILM Controller Robustness
AR0129 ILM Support Tools

End

BCS history
This feature package was created in BCS25.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX940AA CM Bilge
NTX941AA CM Common
NTX950AA MS Bilge
NTX951AA MS Common
Either
NTX942AA DMS SuperNode System Load Module (SLM)
or
NTX942AB DMS SuperNode System Load Module (SLM)

NTXF71AB–2 297-1001-801i Standard 09.01 January 2000

 NTXF71AB
AL1276
Feature name
ILM Connection Support II
Description
AL1276 provides integrated link maintenance (ILM) support for enhanced
network (ENET) connections. Virtual channel maintenance (VCM) handles
multicomponent virtual channels by using a VCM midpoint controller.
BCS history
This feature was created in BCS33.
Restrictions and limitations
This feature applies only to an enhanced core switch that is equipped with an
ENET.
Feature interactions
This feature interacts with the following features:
• AI0087 Basic Virtual Channel Mtc
• AL0583 ENET Connection Control
• AL1009 ILM Robustness II
• AL1010 Physical Link Maintenance Base II
• AL1277 ILM VCM Support for ISN I
• AL1278 ILM MCM Support for ISN I
• AL1279 ILM Connections Support I
• AL1280 ILM VCM Support for ISN II
• AL1281 ILM MCM Support for ISN II
• AL1327 ENET Support for ILM—High-Level Design
• AL1461 ISN Messaging Phase II

Feature Description Manual Volume 2 of 3 BCS44.1i NTXF71AB–3

NTXF71AB
AL1277
Feature name
ILM VCM Support for ISN I
Description
AL1277 provides the basic virtual channel maintenance (VCM) support
required for transport connectivity between nodes in the intelligent services
network (ISN) system. This feature extends the VCM layer of the integrated
link maintenance (ILM) system to allow end-to-end connectivity between
the high-speed interface (HSI) and the channel frame processor (CFP).
BCS history
This feature was created in BCS33.
Feature interactions
This feature interacts with the following features:
• AI0087 Basic Virtual Channel Maintenance
• AL1010 Physical Link Maintenance Base II
• AL1009 ILM Robustness II
• AL1278 ILM MCM Support for ISN I
• AL1279 ILM Connection Support I
Datafill
Table Description

MCHIDTAB Table is added to preserve message channel maintenance

inventory data over BCS upgrades.

NTXF71AB–4 297-1001-801i Standard 09.01 January 2000

 NTXF71AB
AL1278
Feature name
ILM MCM Support for ISN I
Description
AL1278 provides message channel maintenance (MCM) support required
for messaging connectivity between the high-speed interface (HSI) and the
channel frame processor (CFP). This feature implements full MCM
functionality in the HSI-CFP configuration by providing the following:
• updated MCM configuration and database code to support the HSI-CFP
configuration
• central MCM control through the integrated link maintenance central
resource controller (ICRC) and physical link maintenance (PLM)
bootstrap functionality
• enhanced message-channel fault-handling diagnostics
• integrated link maintenance (ILM) performance monitoring

BCS history
This feature was created in BCS33.
Feature interactions
This feature interacts with the following features:
• AI0087 Basic Virtual Channel Maintenance
• AL1010 Physical Link Maintenance Base II
• AL1009 ILM Robustness II
• AL1277 Basic ILM Support (HSI–CFP)

Feature Description Manual Volume 2 of 3 BCS44.1i NTXF71AB–5

NTXF71AB
AL1279
Feature name
ILM Connection Support I
Description
AL1279 provides integrated link maintenance (ILM) support for transport
connectivity between between the high-speed interface (HSI) and the
channel frame processor (CFP). This feature allows ILM
interface-to-enhanced network (ENET) connections in order to allocate the
nailed-up connections (NUC) that form part of a multicomponent virtual
channel.
BCS history
This feature was created in BCS33.
Restrictions and limitations
This feature applies only to an enhanced core switch equipped with ENET.
Feature interactions
This feature interacts with features AL0583 (ENET Connection Control) and
AL1277 (Basic ILM Support (HSI–CFP)).

NTXF71AB–6 297-1001-801i Standard 09.01 January 2000

 NTXF71AB
AL1280
Feature name
ILM VCM Support for ISN II
Description
AL1280 enhances the functionality of virtual channel maintenance (VCM)
for connectivity requirements for the high speed interface to the channel
frame processor. This feature modifies the messaging connectivity interface,
VCM table control interfaces, VCM database code, and the data download
code to support the maintenance of multicomponent, wideband, and
plane-resolved virtual channels.
BCS history
This feature was created in BCS33.
Feature interactions
This feature interacts with the following features:
• AI0087 Basic Virtual Channel Maintenance
• AL1010 Physical Link Maintenance Base II
• AL1009 ILM Robustness II
• AL1277 ILM VCM Support for ISN I
• AL1278 ILM MCM Support for ISN I
• AL1281 ILM MCM Support for ISN II
• AL1279 ILM Connection Support I
• AL1276 ILM Connection Support II
• AL1290 ISN Messaging Phase I
• AL1461 ISN Messaging Phase II
Datafill
For VCH plane configuration and plane status data, this feature increases
static data store by 88 bytes per item.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXF71AB–7

NTXF71AB
AL1281
Feature name
ILM MCM Support for ISN II
Description
AL1281 provides the following capabilities:
• supports message channel maintenance (MCM) for the message channels
that provide message connectivity in the high speed interface
(HSI)–channel frame processor (CFP) system
• modifies the MCM message channel configuration and database code to
support additional information required to run a message channel
controller (MCC) for HSI–CFP message channels
• enhances MCM and the integrated link maintenance (ILM) central
resource controller (ICRC) to provide full central MCM resource control
• implements changes to support message channel fault handling and
diagnostics
• provides ILM performance monitoring support

BCS history
This feature was created in BCS33.
Feature interactions
This feature interacts with the following features:
• AI0087 Basic Virtual Channel Maintenance
• AL1010 Physical Link Maintenance Base II
• AL1009 ILM Robustness II
• AL1276 ILM Connection Support II
• AL1277 ILM VCM Support for ISN I
• AL1278 ILM MCM Support for ISN I
• AL1279 ILM Connection Support I
• AL1280 ILM VCM Support for ISN II
• AL1461 ISN Messaging Phase II
Datafill
This feature increases data store by 15 Kwords and increases program store
by 50 Kbytes.

NTXF71AB–8 297-1001-801i Standard 09.01 January 2000

 NTXF71AB
AL1655
Feature name
ILM Central Resource Controller Enhancement
Description
AL1655 enhances performance and capacity, fault handling, isolation
detection, and performance monitoring in the intelligent services node
(ISN). In addition, this feature supports an OFFLINE state for links.
BCS history
This feature was created in BCS33.
Restrictions and limitations
This feature applies only to an enhanced core switch and peripherals in the
ISN configuration.
Feature interactions
This feature interacts with the following features:
• AL1656 ILM Local Channel Enhancements
• AL1657 Virtual Channel Maintenance Enhancements for ISN
• AL1461 ISN Messaging Phase II
Datafill
This features increases data store by 10 Kwords and increases program store
by 50 Kbytes. An additional static data store of 8 Kbytes per item is
required to store interested party notification data.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXF71AB–9

NTXF71AB
AL1656
Feature name
ILM Local Controller Enhancements
Description
AL1656 provides the following enhancements for local integrated link
maintenance (ILM) controllers:
• provides full system recovery, including recovery of multicomponent
plane-resolved virtual channels
• moves the ILM audit mechanism from the resource controllers to a
separate resource auditing transactor, to allow the auditing transactor to
operate in a lower priority network
• implements support for registration, deregistration, queries, replies, and
notification of resource status information on a local basis
• provides increased ILM data distribution manager (DDM) functionality
so that data can be downloaded to unit 1 of duplex nodes, as well as to
unit 0
• provides support for warm spared nodes
• uses the initialization manager (INITMGR) locally to ensure an efficient
recovery of the ILM system after a restart
• provides a strategy detailing the actions that each ILM transactor should
take when it receives an unknown signal version
BCS history
This feature was created in BCS33.
Feature interactions
This feature interacts with the intelligent services node (ISN) and with
features AL1655 (ILM Central Resource Controller Enhancements) and
AL1657 (Virtual Channel Maintenance Enhancements).
Datafill
This feature increases program store by 10 Kbytes.

NTXF71AB–10 297-1001-801i Standard 09.01 January 2000

 NTXF71AB
AL1657
Feature name
Virtual Channel Maintenance Enhancements for ISN
Description
AL1657 provides full virtual channel maintenance (VCM) support for
plane-resolved multicomponent virtual channels. This includes full
hardware utilities support, as well as local diagnostics for the virtual
channels. This feature also supports integrated link maintenance (ILM)
integration into the integrated services node (ISN) system.
BCS history
This feature was created in BCS33.
Restrictions and limitations
This feature applies only to an enhanced core switch and peripherals in the
ISN configuration.
Feature interactions
This feature interacts with the following features:
• AI0087 Basic Virtual Channel Maintenance
• AL1009 ILM Robustness II
• AL1010 Physical Link Maintenance Base II
• AL1276 ILM Connection Support II
• AL1277 ILM VCM Support for ISN II
• AL1278 ILM MCM Support for ISN II
• AL1617 ISN ENET Connection Control High Level Design
• AL1655 ILM Central Resource Controller Enhancements
• AL1656 ILM Local Controller Enhancements
Datafill
This feature increases program store by 10 Kbytes.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXF71AB–11

NTXF71AB
AL1658
Feature name
ILM Capacity and Performance Enhancements
Description
AL1658 enhances integrated link maintenance (ILM) controller
functionality. This feature improves handling for large groups of ILM
resources, flow control, and overflow handling for ILM controllers.
BCS history
This feature was created in BCS34.
Restrictions and limitations
This feature is applicable only to an enhanced core switch and peripherals in
the synchronous optical network (SONET) DMS (S/DMS) configuration.
Feature interactions
This feature interacts with the following features:
• AL1659 ILM Enhanced Diagnostics
• AL1740 ILM Notification Service Enhancements
• AL1660 VCM Support for Reduced Capability Virtual Channels
Datafill
This feature increases program store by a maximum of 10 Kbytes.

NTXF71AB–12 297-1001-801i Standard 09.01 January 2000

 NTXF71AB
AL1659
Feature name
ILM Enhanced Diagnostics
Description
AL1659 enhances the integrated link maintenance (ILM) physical link,
virtual channel, and message channel diagnostics to include complete fault
handling. This feature also verifies the robustness of basic maintenance
actions (for example, manual busy, return to service, test, and set
maintenance resource status) of these resources.
BCS history
This feature was created in BCS33.
Restrictions and limitations
This feature applies only to an enhanced core switch and peripherals in the
integrated services node (ISN) configuration.
Feature interactions
This feature interacts with the following features:
• AL1740 ILM Notification Enhancements
• AL1658 ILM Capacity and Performance Enhancements
• AL1660 VCM Support for Reduced Capacity Virtual Channels
Datafill
This feature increases program store by a maximum of 1 Kbyte.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXF71AB–13

NTXF71AB
AL1660
Feature name
VCM Support for Reduced Capability Virtual Channels
Description
AL1660 implements enhancements to the integrated link maintenance (ILM)
central and local databases. These enhancements capture new data needed
to support the SONET/DMS (S/DMS) SuperNode configuration and
streamline the ILM databases. This feature also implements the ILM
resource auditing transactors.
BCS history
This feature was created in BCS33.
Restrictions and limitations
This feature applies only to an enhanced core switch and peripherals in the
S/DMS configuration.
Feature interactions
This feature interacts with features AL1740 (ILM Notification Service
Enhancements) and AL1658 (ILM Capacity and Performance
Enhancements).
Datafill
This feature increases data store by a maximum of 0.4 Kbytes and increases
program store by a maximum of 5 Kbytes.

NTXF71AB–14 297-1001-801i Standard 09.01 January 2000

 NTXF71AB
AL1663
Feature name
Message Base Enhancements for ISN
Description
AL1663 provides performance enhancements to the message base, as
required for interprocess communication in the distributed processing
environment of the intelligent services node (ISN) architecture.
BCS history
This feature was created in BCS33.
Datafill
This feature increases program store by a maximum of 3 Kbytes.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXF71AB–15

NTXF71AB
AL1664
Feature name
MRS Development and AP Split Mode Messaging Study
Description
AL1664 enhances the maintenance routing system (MRS) to support
messaging capability to either side of a sync-matched application processor
(AP) node when the AP is operating in split mode.
BCS history
This feature was created in BCS33.
Datafill
This feature increases program store by 20 Kbytes and increases data store
by 6 Kbytes.

NTXF71AB–16 297-1001-801i Standard 09.01 January 2000

 NTXF71AB
AL1740
Feature name
ILM Notification Service Enhancements
Description
AL1740 expands integrated link maintenance (ILM) functionality as
follows:
• by providing overall enhancements to the ILM central resource
controller (ICRC), and support for extended functionality in the areas of
full transport required resource (RR), high speed interface (HSI) bit error
rate test (BERT), abort signal, comprehensive accessibility tracking,
overall capacity issues, scoping support on structured interaction service
(SIS), and user identification on requests
• by expanding the isolation detection function (IDF) to provide isolation
detection on all SONET/DMS (S/DMS) nodes, in addition to application
processors (AP)
• by providing overall enhancements to local ILM controllers in the area
of warm spared node support
BCS history
This feature was created in BCS33.
Restrictions and limitations
This feature applies only to an enhanced core switch and peripherals in the
S/DMS configuration.
Feature interactions
This feature interacts with the following features:
• AL1658 ILM Capacity and Performance Enhancements
• AL1659 ILM Enhanced Diagnostics
• AL1660 VCM Support for Reduced Capacity Virtual Channels
• AL1916 HSI Bit Error Rate Tests
Datafill
This feature increases program store by a maximum of 15 Kbytes.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXF71AB–17

NTXF71AB
AL2130
Feature name
ILM Support for Warm-spared Nodes
Description
AL2130 provides integrated link maintenance (ILM) support for
warm-spared nodes. This feature provides resource activity management,
data sync, and integrity fault handling on plane-resolved virtual channels.
BCS history
This feature was created in BCS34.
Feature interactions
This feature interacts with the following features:
• AL1276 ILM Connection Support II
• AL1281 ILM MCM Support for ISN II
• AL1461 ISN Messaging Phase II
• AL1657 Virtual Channel Maintenance Enhancements for ISN
• AL1660 VCM Support for Reduced Capability Virtual Channels
• AL1839 ENET Integrity Fault Handler for ISN

NTXF71AB–18 297-1001-801i Standard 09.01 January 2000

 NTXF71AB
AR0124
Feature name
ILM Fault Isolation Enhancements
Description
AR0124 enhances the ability of integrated link maintenance (ILM) to isolate
faults.
BCS history
This feature was created in BCS34.
Restrictions and limitations
This feature is applicable only on an enhanced core switch and peripherals in
the synchronous optical network (SONET) DMS (S/DMS) and
second-generation service control point (SCP-II) configurations.
Feature interactions
This feature interacts with the following features:
• AR0125 ILM Isolation Detection Enhancements
• AR0128 ILM Controller Robustness
• AR0139 ILM Large System Support

Feature Description Manual Volume 2 of 3 BCS44.1i NTXF71AB–19

NTXF71AB
AR0125
Feature name
ILM Isolation Detection Enhancements
Description
This feature provides enhancements to the isolation detection function (IDF)
that allows it to provide full support for the following nodes:
• application processor (AP)
• file processor (FP)
• link interface unit (LIU)
• network interface unit (NIU)
BCS history
This feature was created in BCS36.
Restrictions and limitations
This feature applies only to the nodes listed in the description paragraph,
above.
Feature interactions
This feature requires feature AL1740 (ILM Notification Enhancements).

NTXF71AB–20 297-1001-801i Standard 09.01 January 2000

 NTXF71AB
AR0128
Feature name
ILM Controller Robustness
Description
AR0128 enhances integrated link maintenance (ILM). This feature provides

• ILM support for no-restart computing module (CM) switch of activity

(SWACT)
• BCS applications on the second-generation service control point
(SCP-II) and synchronous optical network (SONET) DMS (S/DMS)
• CM maintenance request contention management
BCS history
This feature was created in BCS34.
Feature interactions
This feature interacts with features AL2130 (ILM Support for Warm-spared
Nodes) and AL1839 (ENET Integrity Fault Handler for ISN).
Datafill
Table Description

INIDTAB Table is added to datafill the relationship between ILM links and
pairs of ILM access identifiers over BCS applications.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXF71AB–21

NTXF71AB
AR0129
Feature name
ILM Support Tools
Description
AR0129 provides integrated link maintenance (ILM) support tools for
debugging. This feature provides an ILM field debug package, debugging
guide, and operational measurements (OM) support.
BCS history
This feature was created in BCS34.
Datafill
This feature increases program store by a maximum of 10 Kbytes and
increases data store by a maximum of 10 Kbytes.
User interface
This feature is applicable only on an enhanced core switch and peripherals in
the synchronous optical network (SONET) DMS (S/DMS) and the
second-generation service control point (SCP II) configurations.

NTXF71AB–22 297-1001-801i Standard 09.01 January 2000

 NTXH00AA
Moroccan Tones
This feature package applies to DMS-100 offices.
NTXH00AA provides the toneset definition for the Moroccan international
digital trunk controller (IDTC). The toneset includes the multifrequency
(MF), MF compelled (MFC), and supervisory tones.
Feature package contents
Feature package NTXH00AA contents
Feature number Description

AE0448 Moroccan Tones

BCS history
This feature package was created in BCS28.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX270AA New Peripheral Maintenance Package

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH00AA–1

NTXH00AA
AE0448
Feature name
Moroccan Tones
Description
This feature provides the toneset definition for the Moroccan international
digital trunk controller (IDTC). The toneset includes the multifrequency
(MF), MF compelled (MFC), and supervisory tones.
This feature binds a new set of tone parameters into the XMS-based
peripheral module (XML) software from which Moroccan tone samples are
created.
BCS history
This feature was created in BCS28.
Hardware requirements
This feature requires the NT6X69LA (CPP message protocol and
downloadable tones CP) card.
Feature interactions
This feature requires the following features:
• AE0200 Tones Optionality
• AE0397 Downloadable Tones
Datafill
Table Description

LTCINV Option MOROCCO is added to the field TONESET.

NTXH00AA–2 297-1001-801i Standard 09.01 January 2000

 NTXH01AA
Moroccan Line Card Diagnostics
This feature package applies to DMS-100 offices.
NTXH01AA provides the line card diagnostic test for the NT6X93DA
(Moroccan line card type A) and the NT6X94DA (Moroccan type B line
card).
Feature package contents
Feature package NTXH01AA contents
Feature number Description

AE0513 Moroccan Type A Line Card Diagnostics

AE0536 Moroccan Type B Line Card Diagnostics

BCS history
This feature package was created in BCS28.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX470AA International–Common Basic
NTX901AA Local Features I
NTX472AA International–Local Basic (upgraded by NTX472AB)
or
NTX472AB International–Local Basic (upgrades NTX472AA)

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH01AA–1

NTXH01AA
AE0513
Feature name
Moroccan Type A Line Card Diagnostics
Description
This feature provides the line card diagnostic test for the NT6X93DA (line
card type A Morocco).
The NT6X93DA card provides a voice and signaling interface between a
two-wire analog subscriber line and one channel of the four-wire,
32-channel, 2.56-Mbit/s stream of DMS-100 switch. The NT6X93DA is a
subscriber line interface for POTS and is compatible with the dual-tone
multifrequency (DTMF) and dial pulse (DP) phone sets used in the
Moroccan market.
The line card diagnostic test for the NT6X93DA card includes the following
tests:
• The transhybrid loss test measures the loss in the line card hybrid circuit
at the digital interface.
• The receive attenuation loss test checks the 1 dB, 2 dB, and 4 dB receive
attenuation pads in the line circuit under test.
• The talk battery test checks the battery (B lead) and ground (A lead)
feeding circuit of the line card.
• The cutoff relay test determines if the cutoff relay is functioning
properly.
• The battery feed resistor test checks determines if both battery feed
resistor values are correct.
• The loop detector test determines if the circuit can detect an off-hook
condition.
• The noise test checks for noise in the line card.
• The flux balance test checks the flux balance circuitry.
• The ringing and supervision test checks the ringing relay of the line
circuit.
• The subscriber loop test checks the condition of the subscriber loop.

BCS history
This feature was created in BCS28.
Datafill
Table Description

LNINV Line card code 6X93DA is added to field CARDCODE.

NTXH01AA–2 297-1001-801i Standard 09.01 January 2000

NTXH01AA NTXH01AA
AE0536 AE0536
Feature name
Moroccan Type B Line Card Diagnostics
Description
This feature provides the line card diagnostic test for the NT6X94DA
(Moroccan type B line card).
The NT6X94DA card provides a voice and signaling interface between a
two-wire analog subscriber line and one channel of the four-wire,
32 channel, 2.56-Mbit/s stream of a DMS-100 switch. The NT6X94DA is a
subscriber line interface used by single party, private branch exchange
(PBX), and coin subscribers.
The line card diagnostic test for the NT6X94DA card includes the
following:
• The transhybrid loss test measures the loss in the line card hybrid circuit
at the digital interface.
• The receive attenuation loss test checks the 1 dB, 2 dB, and 4 dB receive
attenuation pads in the line circuit under test.
• The talk battery test checks the battery (B lead) and ground (A lead)
feeding circuit of the line card.
• The cutoff relay test determines if the cutoff relay is functioning
properly.
• The battery feed resistor test checks determines if both battery feed
resistor values are correct.
• The loop detector test determines if the circuit can detect an off-hook
condition.
• The noise test checks for noise in the line card.
• The flux balance test checks the flux balance circuitry.
• The ringing and supervision test checks the ringing relay of the line
circuit.
• The subscriber loop test checks the condition of the subscriber loop.
• The isolation relay test determines if the isolation relay is operated as
required.
• The metering test checks the quality of the metering signal sent through
the line card.
• The reversal relay test checks the operation of the reversal relay in the
line card.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH01AA–3

NTXH01AA
AE0536
BCS history
This feature was created in BCS29.
Datafill
Table Description

LNINV Line card code 6X94DA is added to field CARDCODE.

NTXH01AA–4 297-1001-801i Standard 09.01 January 2000

 NTXH02AA
Moroccan Physical Ringing
This feature package applies to DMS-100 offices.
NTXH02AA provides Moroccan physical ringing for lines on international
line concentrating modules (ILCMs), international remote line concentrating
modules (IRLCMs), domestic line concentrating modules (LCMs), and very
small remotes (VSR).
The naming convention syntax for international coded ringing schemes is as
follows:
• Cnx where C indicates coded
n is the number of seconds in the ring cycle
x is a letter that uniquely identifies the ringing scheme
For Morocco, the coded ringing scheme is C5B.
Feature package contents
Feature package NTXH02AA contents
Feature number Description

AE0515 Moroccan Physical Ringing

BCS history
This feature package was created in BCS28.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX470AA International–Common Basic
NTX901AA Local Features I
NTX472AA International–Local Basic (upgraded by NTX472AB)
or
NTX472AB International–Local Basic (upgrades NTX472AA)

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH02AA–1

NTXH02AA
AE0515
Feature name
Moroccan Physical Ringing
Description
This feature provides Moroccan physical ringing on lines hosted on
international line concentrating modules (ILCM) and international remote
line concentrating modules (IRLCM) on the DMS-100 switch. Moroccan
physical ringing is also supported for lines on domestic line concentrating
modules (LCM) and very small remotes (VSR).
Physical ringing is the application of an alternating current to the tip (A
lead) or the ring (B lead) of the line loop. The voltage and frequency of the
current variations are parameters of the ringing. The wave form of the
alternating current usually is sinusoidal.
This feature introduces a naming convention for international coded ringing
schemes. The syntax is as follows:
• Cnx where C indicates coded
n is the number of seconds in the ring cycle
x is a letter that uniquely identifies the ringing scheme
For Morocco, the coded ringing scheme is C5B.
BCS history
This feature was created in BCS28.
Hardware requirements
This feature requires the NT6X30DA ringing generator in ILCMs and the
NT6X60DA ringing generator in IRLCMs.
Restrictions and limitations
The ringing datafilled in tables LCMINV and VSRINV must correspond to
the ring generators provisioned in the LCM. That is, a ringing scheme of
C5B must be used in conjunction with NT6X30DA ring generators in
ILCMs and NT6X60DA ring generators in IRLCMs.
Line concentrating equipment (LCE) frames should contain only one type of
ring generators.
Ringing scheme C5B supports immediate ringing, but only for standard
ringing. The maximum delay before the start of ringing is 2 s, as opposed to
5 s when in the delayed ringing mode.

NTXH02AA–2 297-1001-801i Standard 09.01 January 2000

 NTXH02AA
AE0515
Datafill
Table Description

LCMINV and The coded ringing scheme C5B is added to field RNGTYPE.
VSRINV

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH02AA–3

 NTXH03AA
Socotel Base Signaling
This feature package applies to DMS-100 and DMS-200 offices.
NTXH03AA implements incoming and outgoing Socotel trunks in Morocco,
supports interworking with international plain ordinary telephone service
(POTS) lines and Moroccan R2 trunks, and provides XMS-based peripheral
module support for the Socotel register signaling system.
Feature package contents
Feature package NTXH03AA contents
Feature number Description

AE0567 Moroccan Socotel Call Processing

AE0568 Moroccan Socotel Register Signaling

BCS history
This feature package was created in BCS28.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX470AA International–Common Basic
NTX904AA R2 Signaling Base

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH03AA–1

NTXH03AA
AE0567
Feature name
Moroccan Socotel Call Processing
Description
This feature provides the central control (CC) call processing required to
implement incoming and outgoing Socotel trunks on the DMS-100 and
DMS-200 switches in Morocco. Interworking with international POTS lines
and Moroccan R2 trunks is supported.
The following interactions are supported:
• international POTS line to Moroccan Socotel trunk
• Moroccan Socotel trunk to international POTS line
• end-to-end signaling for Moroccan Socotel trunk to Moroccan Socotel
trunk
• link-by-link signaling for Moroccan Socotel trunk to Moroccan Socotel
trunk
• Moroccan Socotel trunk to Moroccan R2 trunk
• Moroccan R2 trunk to Moroccan Socotel trunk

BCS history
This feature was created in BCS28.
Hardware requirements
Moroccan international digital trunk controllers (IDTC) require two
NT6X92CA (international UTR tone detection) cards.
Restrictions and limitations
The only line option supported with Moroccan Socotel trunks is Free
Number Terminating (FNT).
Two-way Moroccan Socotel trunks are not supported.
End-to-end signaling over Moroccan Socotel trunks is allowed only if the
incoming and outgoing trunks use identical protocol.
Metering pulses are not used by the billing system.
Access to three-digit special services through Moroccan Socotel trunks is
not supported.
A seven-digit numbering plan using Moroccan Socotel signaling is not
supported.

NTXH03AA–2 297-1001-801i Standard 09.01 January 2000

 NTXH03AA
AE0567
Datafill
Table Description

ACTCTL, Thirteen activities are added to field ACTIVITY. These activities

ACTSIG, are required for Moroccan Socotel register signaling.
ACTTRTMT,
SIGACT, and
TRTMTACT
R2PROT Protocol NTR203 is added to field BASEPROT. Protocol
NTR03 represents the Moroccan Socotel variant of the base R2
protocol.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH03AA–3

NTXH03AA
AE0568
Feature name
Moroccan Socotel Register Signaling
Description
This feature provides XMS-based peripheral module (XPM) software
support for the Socotel register signaling system in DMS-100 and DMS-200
switches in Morocco.
BCS history
This feature was created in BCS28.
Hardware requirements
Moroccan international digital trunk controllers (IDTC) require the
following cards:
• one NT6X69LA (CPP message protocol and downloadable tones CP)
card
• two NT6X92CA (international UTR tone detection) cards

Restrictions and limitations

Centralized automatic message accounting (CAMA) is not supported on
Moroccan Socotel trunks.
Feature interactions
This feature requires feature AE0567 (Moroccan Socotel Call Processing).
Datafill
Table Description

RSIGSYS Signaling selector NTRS12 is added. This allows four new

timing parameters to be datafilled.

NTXH03AA–4 297-1001-801i Standard 09.01 January 2000

 NTXH04AA
CCITT 2-Bit Line Signaling
This feature package applies to DMS-100/200 offices.
NTXH04AA implements line signaling for digital R2 trunk call processing
in the DMS-100/200 switch in Morocco.
Feature package contents
Feature package NTXH04AA contents
Feature number Description

AE0514 Moroccan R2 Line Signaling

BCS history
This feature package was created in BCS28.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX270AA New Peripheral Maintenance Package
NTX470AA International–Common Basic

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH04AA–1

NTXH04AA
AE0514
Feature name
Moroccan R2 Line Signaling
Description
This feature implements the line signaling system NTLS16, which is used in
digital R2 trunk call processing in the DMS-100/200 switch in Morocco.
BCS history
This feature was created in BCS28.
Restrictions and limitations
Datafilling of one-way trunks is supported. Datafilling of two-way trunks is
not supported.
Meter pulses are not counted or made available through any metering
system. Metering pulses are not tandemed across a switch.
Datafill
Table Description

LNSIGSYS Separate tuples for the Moroccan R2 line signaling system are
added.

NTXH04AA–2 297-1001-801i Standard 09.01 January 2000

 NTXH05AA
Moroccan Local Signaling
This feature package applies to DMS-100 offices.
NTXH05AA implements call processing and R2 signaling for the
DMS-100/200 switch in Morocco.
Feature package contents
Feature package NTXH05AA contents
Feature number Description

AE0567 Moroccan Socotel Call Processing

AE0568 Moroccan Socotel Register Signaling
AE0897 R2 and Socotel Tandem Operation
AE0898 Second Dial Tone Over Trunks
AJ0205 R2 Protocol Enhancements

BCS history
This feature package was created in BCS28.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX470AA International–Common Basic
NTX901AA Local Features I
NTX904AA R2 Signaling Base
NTXH03AA Socotel Base Signaling
NTXH04AA CCITT 2-Bit Line Signaling
NTX472AA International–Local Basic (upgraded by NTX472AB)
or
NTX472AB International–Local Basic (upgrades NTX472AA)

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH05AA–1

NTXH05AA
AE0567
Feature name
Moroccan Socotel Call Processing
Description
AE0567 provides the central control call processing required to implement
incoming and outgoing Socotel trunks on the DMS-100 international and
DMS-200 international product according to Moroccan specifications. The
feature also supports international POTS lines and Moroccan R2 trunks.
Moroccan Socotel multifrequency compelled (MFC) trunk register signaling
is a national signaling system, used for calls within the country. MFC
register signaling uses in-band multifrequency tones in a compelled manner
to allow the safe transfer of address information between offices.
BCS history
This feature was created in BCS28.
Hardware requirements
Each international digital trunk controller (IDTC) that carries Moroccan
Socotel traffic must be equipped with two universal tone receiver (UTR)
cards because long holding times can occur with Moroccan Socotel register
signaling.
Restrictions and limitations
Two-way Moroccan Socotel trunks are not supported. An attempt to datafill
the trunks is blocked in table TRKSGRP.
The Free Number Termination (FNT) line option is the only feature
supported between Moroccan Socotel trunks and lines.
If one subgroup in a trunk group references an entry of register signaling
type NTRS12 in table RGSIGSYS, the other subgroup of that trunk (if the
subgroup is datafilled) must also reference an entry of register signaling type
NTRS12 in table RGSIGSYS.
Incoming and outgoing trunks must use the same protocol to allow
end-to-end signaling of Moroccan Socotel trunks. The protocol is specified
in field PROTIDX in table TRKGRP.
Meter pulses are ignored on Moroccan Socotel trunks, and do not affect the
metering or billing system.
Moroccan Socotel trunks do not provide access to three-digit special
services.

NTXH05AA–2 297-1001-801i Standard 09.01 January 2000

 NTXH05AA
AE0567
AE0567 does not support a seven-digit numbering plan using Moroccan
Socotel signaling.
The following tables are not visible to the customer: ACTCTL, ACTSIG,
R2PROT, and SIGACT.
Feature interactions
This feature supports the following interactions:
• international POTS line to Moroccan Socotel trunk
• Moroccan Socotel trunk to international POTS line
• Moroccan Socotel trunk to Moroccan Socotel trunk using end-to-end
signaling
• Moroccan Socotel trunk to Moroccan Socotel trunk using link-by-link
signaling
• Moroccan Socotel trunk to Moroccan R2 trunk
• Moroccan R2 trunk to Moroccan Socotel trunk

Datafill
Table Description

ACTCTL Provides a control mechanism to change phases and the state

processor that is used to take action as determined by activities.
Note: This table is not visible to the customer.

New activities required for Moroccan Socotel register signaling

are added to field ACTIVITY.
ACTSIG Maps activities to signals. Note: This table is not visible to the
customer.

New activities required for Moroccan Socotel register signaling

are added to field ACTIVITY.
ACTTRTMT Maps activities to office treatments.

New activities required for Moroccan Socotel register signaling

are added to field ACTIVITY.
R2PROT Provides the definition of the mapping and activity controllers for
each protocol. Note: This table is not visible to the customer.

A new value is added to field BASEPROT.

—continued—

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH05AA–3

NTXH05AA
AE0567

Table Description (continued)

SIGACT Maps signals to activities. Note: This table is not visible to the
customer.

New activities required for Moroccan Socotel register signaling

are added to field ACTIVITY.
TRTMTACT Maps treatments to activities.

New activities required for Moroccan Socotel register signaling

are added to field ACTIVITY.

End

NTXH05AA–4 297-1001-801i Standard 09.01 January 2000

 NTXH05AA
AE0568
Feature name
Moroccan Socotel Register Signaling
Description
AE0568 provides the XMS-based peripheral module (XPM) software to
support the Moroccan Socotel multifrequency compelled (MFC) trunk
register signaling system. This will be used on DMS-100 and DMS-200
switches outside North America.
Moroccan Socotel MFC trunk register signaling is a national signaling
system, used for calls within the country. MFC register signaling uses
in-band multifrequency tones in a compelled manner to allow the safe
transfer of address information between offices.
BCS history
This feature was created in BCS28.
Hardware requirements
Each international digital trunk controller (IDTC) that carries Moroccan
Socotel traffic must be equipped with two universal tone receiver (UTR)
cards (NT6X92CA) and a downloadable tones card (NT6X69LA).
The UTR requires firmware capable of receiving all the Socotel tones,
including the 1900-Hz check frequency.
Restrictions and limitations
Centralized automatic message accounting (CAMA) is not supported on
Moroccan Socotel trunks.
Only 1700-Hz operation is supported by the Moroccan tone set, even though
the UTR card can support other tones.
Feature interactions
This feature requires the AE0567 Moroccan Socotel Call Processing feature.
Datafill
Table Description

RGSIGSYS A new signaling selector, NTRS12, will be created for tuples in

table RGSIGSYS to allow four new timing parameters to be
datafilled.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH05AA–5

NTXH05AA
AE0897
Feature name
R2 and Socotel Tandem Operation
Description
AE0568 allows an originating office to provide tandem operation for call
processing between Moroccan R2 trunks to Socotel trunks on DMS-100 and
DMS-200 switches.
BCS history
This feature was created in BCS33.
Hardware requirements
Each international digital trunk controller (IDTC) that carries Moroccan
Socotel traffic must be equipped with a universal tone receiver (UTR) card
(NT6X92CA) and a downloadable tones card (NT6X69LA).
Restrictions and limitations
Meter pulse generation and tandeming is not supported.
Providing second dial tone from the tandem DMS office in international
calls is not supported.
The duration of the no charge calls is limited by the preanswer timeout
duration at the originating office. This restriction occurs because the
termination subscriber status is always sent as subscriber free charge. The
call is released only if the calling party goes on-hook or the preanswer
timeout is exceeded.
The terminating office cannot handle ANI requests unless the call was
requested and kept in the tandem office before the call was sent on to the
terminating trunk.
The call progress tone is not applied in operator calls between a dial pulse
signaling system and a Moroccan R2 trunk because the audible ringing is
connected to the originating office by the tandem office.
Feature interactions
This feature supports the following interactions:
• Moroccan R2 trunk to Moroccan Socotel multifrequency trunk
• Moroccan Socotel multifrequency trunk to Moroccan R2 trunk
• Moroccan R2 trunk to Moroccan R2 trunk
• dial pulse signaling system to Moroccan R2 trunk

NTXH05AA–6 297-1001-801i Standard 09.01 January 2000

 NTXH05AA
AE0897
This feature requires the following features:
• AE0898 Second Dial Tone over Trunks
• AJ0581 Hardware Pulse Reception
• AJ0851 Meter Pulse Tandem
Datafill
Table Description

TRKGRP Field TNDMMODE must be datafilled as EEND in incoming and

outgoing trunk group data to apply special tandeming on
Moroccan R2 trunks to Socotel multifrequency trunks.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH05AA–7

NTXH05AA
AE0898
Feature name
Second Dial Tone Over Trunks
Description
AE0898 provides the capability
• to datafill second dial tone on each trunk group by creating a new field
(DTONE) in table DGHEAD
• for second dial tone to be applied by the terminating trunk toward the
origination subscriber
BCS history
This feature was created in BCS32.
Restrictions and limitations
AE0898 is applicable only on calls coming in on dial pulse trunks, but can
be expanded to support other multifrequency trunk types (except
multifrequency compelled trunks, such as R2 trunks).
The inter-digit timeouts are controlled by standard trunk datafill, not line
datafill.
Dial tone is the only additional tone applied over the trunks. Treatments are
applied according to the particular trunk protocol.
Dial tone is terminated at the end of the first received digit, rather than at the
beginning.
If AE0898 is used outside the Morocco market, changes to the tone selected
may be required.
Datafill
Table Description

DGHEAD Field DTONE is added to select the type of dial tone applied on
each incoming trunk group (NONE, NORM, SPEC, or SPEC2).

NTXH05AA–8 297-1001-801i Standard 09.01 January 2000

 NTXH05AA
AJ0205
Feature name
R2 Protocol Enhancements
Description
This feature implements the R2 protocol for Morocco supported by the
DMS-100/200 switch.
BCS history
This feature was created in BCS28.
Hardware requirements
This feature requires provision of an NT6X69LA (CPP message protocol
and downloadable tones CP) card and an NT6X92CA (international UTR
tone detection) card on international digital trunk controllers (IDTC).
Feature interactions
The following features interact with R2 trunk protocol and function
differently in an R2 environment:
• Call Waiting (CWT)
• Coin Line
• Free Number Terminating (FNT)
• Malicious Call Trace (MCT)
• No Double Connect (NDC)
• Toll Break-in (TBI)
• Call Diversion (CDIV)

If the DMS switch is a terminating exchange, and the called subscriber has
CWT and is busy, the called status signal sent to complete register signaling
is Subscriber Line Free, Charge. When the terminating line has CWT, the
called status signal is returned. In both cases, the DMS switch completes
register signaling, connects the originator to audible ringing, and normal
CWT processing continues for the duration of the call.
When a coin line originates a call over an R2 trunk not supporting the
calling category signal COIN, the DMS switch sends the Regular Subscriber
signal. As a tandem exchange, if the DMS switch receives the calling
category COIN from the originating R2 trunk, and this signal is not
supported by the terminating R2 trunk, the Regular Subscriber signal is
substituted for COIN.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH05AA–9

NTXH05AA
AJ0205
The DMS switch currently does not send the line signal Answer for calls
terminating on a line with FNT. With the R2 signal Subscriber Line Free,
No Charge, there is a method to convey this information to the originating
exchange. With this feature, calls over R2 trunks handle FNT in the
following manner:
• If the DMS switch is the terminating exchange, the register signal for the
called subscriber status Subscriber Line Free, No Charge is sent. When
the call is answered, the line signal Answer is sent to the incoming trunk.
• If the DMS is a tandem exchange in end-to-end mode, the signal for
Subscriber Line Free, No Charge will be tandemed.
• If the DMS is a tandem exchange in link-by-link mode, the DMS
processes the incoming Subscriber Line Free, No Charge signal as
follows:
— If the incoming R2 protocol supports the signal, it is sent to the
originating exchange and when it is received, the line signal Answer
is sent to the originating exchange.
— If the incoming R2 protocol does not support the signal, the called
status signal returned is Subscriber Line Free, Charge. When the line
signal Answer is received from the terminating exchange, it is not
sent to the originating exchange.
— If the incoming trunk from the originating exchange is R1, the line
signal Answer is not sent to the originating exchange when received
from the terminating exchange.
• If the DMS switch is an originating exchange and receives the called
status signal Subscriber Line Free, No Charge, the originating subscriber
is not billed for the call. The line signal Answer is expected and the call
is marked as such when received from the terminating exchange.
The DMS switch only supports MCT through line signaling. The only line
signalling system supporting MCT is NTLS09. If the terminating subscriber
has MCT, the DMS switch does not send the calling number over register
signaling during call setup. If the line signaling supports the MCT signal
and MCT is activated while the DMS switch is an originating or tandem
exchange, the affected trunks and lines are held until released from the MAP
(maintenance and administration position) terminal.
The DMS switch sends the calling category Data for calls originated by lines
with NDC activated. If the DMS switch is a terminating exchange, calls
with the calling category Data are not allowed to double connect.
Manual and automatic TBI are supported by the DMS switch. Calls
originating from an operator (manual TBI) and terminating on a DMS
switch do not send the R2 register signal Subscriber Busy. The subscriber

NTXH05AA–10 297-1001-801i Standard 09.01 January 2000

 NTXH05AA
AJ0205
status signal Congestion is sent and a busy tone is applied to the trunk in the
terminating exchange. The trunk connection remains up, allowing the
operator to send the TBI signal and break in on the subscriber. Automatic
TBI eliminates the requirement for the operator to manually initiate a TBI
signal. When the called party is busy, TBI is performed automatically. With
automatic TBI, no busy treatment is applied and the operator is sent a TBI
tone indicating a busy call has been broken into. The called subscriber
status signal Subscriber Line Free, Charge is returned by the terminating
exchange.
Calls terminating in a DMS switch where the subscriber has CDIV activated
have the Called Subscriber line status of the subscriber line diverted to
Returned.
Datafill
Table Description

ACTTRMT and Values COIN, OPER, DATA, PRIORITY, MTC_EQ,

TRTMTACT REQ_NOT_ACC, SUB_XFRD, TERM_CTRL_CHG, and
TEMP_OUT_ORD are added to field R2_ACTIVITY.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH05AA–11

 NTXH06AA
Moroccan Toll Signaling
This feature package applies to DMS-100 offices.
NTXH06AA implements call processing and R2 signaling for the
DMS-100/200 switch in Morocco.
Feature package contents
Feature package NTXH06AA contents
Feature number Description

AE0567 Moroccan Socotel Call Processing

AE0568 Moroccan Socotel Register Signaling
AE0897 R2 and Socotel Tandem Operation
AE0898 Second Dial Tone Over Trunks
AJ0205 R2 Protocol Enhancements

BCS history
This feature package was created in BCS28.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX470AA International–Common Basic
NTX904AA R2 Signaling Base
NTXH03AA Socotel Base Signaling
NTXH04AA CCITT 2-Bit Line Signaling

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH06AA–1

NTXH06AA
AE0567
Feature name
Moroccan Socotel Call Processing
Description
AE0567 provides the central control call processing required to implement
incoming and outgoing Socotel trunks on the DMS-100 international and
DMS-200 international product according to Moroccan specifications. The
feature also supports international POTS lines and Moroccan R2 trunks.
Moroccan Socotel multifrequency compelled (MFC) trunk register signaling
is a national signaling system, used for calls within the country. MFC
register signaling uses in-band multifrequency tones in a compelled manner
to allow the safe transfer of address information between offices.
BCS history
This feature was created in BCS28.
Hardware requirements
Each international digital trunk controller (IDTC) that carries Moroccan
Socotel traffic must be equipped with two universal tone receiver (UTR)
cards because long holding times can occur with Moroccan Socotel register
signaling.
Restrictions and limitations
Two-way Moroccan Socotel trunks are not supported. An attempt to datafill
the trunks is blocked in table TRKSGRP.
The Free Number Termination (FNT) line option is the only feature
supported between Moroccan Socotel trunks and lines.
If one subgroup in a trunk group references an entry of register signaling
type NTRS12 in table RGSIGSYS, the other subgroup of that trunk (if the
subgroup is datafilled) must also reference an entry of register signaling type
NTRS12 in table RGSIGSYS.
Incoming and outgoing trunks must use the same protocol to allow
end-to-end signaling of Moroccan Socotel trunks. The protocol is specified
in field PROTIDX in table TRKGRP.
Meter pulses are ignored on Moroccan Socotel trunks, and do not affect the
metering or billing system.
Moroccan Socotel trunks do not provide access to three-digit special
services.

NTXH06AA–2 297-1001-801i Standard 09.01 January 2000

 NTXH06AA
AE0567
AE0567 does not support a seven-digit numbering plan using Moroccan
Socotel signaling.
The following tables are not visible to the customer: ACTCTL, ACTSIG,
R2PROT, and SIGACT.
Feature interactions
This feature supports the following interactions:
• international POTS line to Moroccan Socotel trunk
• Moroccan Socotel trunk to international POTS line
• Moroccan Socotel trunk to Moroccan Socotel trunk using end-to-end
signaling
• Moroccan Socotel trunk to Moroccan Socotel trunk using link-by-link
signaling
• Moroccan Socotel trunk to Moroccan R2 trunk
• Moroccan R2 trunk to Moroccan Socotel trunk

Datafill
Table Description

ACTCTL Provides a control mechanism to change phases and the state

processor that is used to take action as determined by activities.
Note: This table is not visible to the customer.

New activities required for Moroccan Socotel register signaling

are added to field ACTIVITY.
ACTSIG Maps activities to signals. Note: This table is not visible to the
customer.

New activities required for Moroccan Socotel register signaling

are added to field ACTIVITY.
ACTTRTMT Maps activities to office treatments.

New activities required for Moroccan Socotel register signaling

are added to field ACTIVITY.
R2PROT Provides the definition of the mapping and activity controllers for
each protocol. Note: This table is not visible to the customer.

A new value is added to field BASEPROT.

—continued—

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH06AA–3

NTXH06AA
AE0567

Table Description (continued)

SIGACT Maps signals to activities. Note: This table is not visible to the
customer.

New activities required for Moroccan Socotel register signaling

are added to field ACTIVITY.
TRTMTACT Maps treatments to activities.

New activities required for Moroccan Socotel register signaling

are added to field ACTIVITY.

End

NTXH06AA–4 297-1001-801i Standard 09.01 January 2000

 NTXH06AA
AE0568
Feature name
Moroccan Socotel Register Signaling
Description
AE0568 provides the XMS-based peripheral module (XPM) software to
support the Moroccan Socotel multifrequency compelled (MFC) trunk
register signaling system. This will be used on DMS-100 and the DMS-200
switches outside North America.
Moroccan Socotel MFC trunk register signaling is a national signaling
system, used for calls within the country. MFC register signaling uses
in-band multifrequency tones in a compelled manner to allow the safe
transfer of address information between offices.
BCS history
This feature was created in BCS28.
Hardware requirements
Each international digital trunk controller (IDTC) that carries Moroccan
Socotel traffic must be equipped with two universal tone receiver (UTR)
cards (NT6X92CA) and a downloadable tones card (NT6X69LA).
The UTR requires firmware capable of receiving all the Socotel tones,
including the 1900-Hz check frequency.
Restrictions and limitations
Centralized automatic message accounting (CAMA) is not supported on
Moroccan Socotel trunks.
Only 1700-Hz operation is supported by the Moroccan tone set, even though
the UTR card can support other tones.
Feature interactions
This feature requires the AE0567 Moroccan Socotel Call Processing feature.
Datafill
Table Description

RGSIGSYS A new signaling selector, NTRS12, will be created for tuples in

table RGSIGSYS to allow four new timing parameters to be
datafilled.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH06AA–5

NTXH06AA
AE0897
Feature name
R2 and Socotel Tandem Operation
Description
AE0568 allows an originating office to provide tandem operation for call
processing between Moroccan R2 trunks to Socotel trunks on DMS-100 and
DMS-200 switches.
BCS history
This feature was created in BCS33.
Hardware requirements
Each international digital trunk controller (IDTC) that carries Moroccan
Socotel traffic must be equipped with a universal tone receiver (UTR) card
(NT6X92CA) and a downloadable tones card (NT6X69LA).
Restrictions and limitations
Meter pulse generation and tandeming is not supported.
Providing second dial tone from the tandem DMS office in international
calls is not supported.
The duration of the no charge calls is limited by the preanswer timeout
duration at the originating office. This restriction occurs because the
termination subscriber status is always sent as subscriber free charge. The
call is released only if the calling party goes on-hook or the preanswer
timeout is exceeded.
The terminating office cannot handle ANI requests unless the call was
requested and kept in the tandem office before the call was sent on to the
terminating trunk.
The call progress tone is not applied in operator calls between a dial pulse
signaling system and a Moroccan R2 trunk because the audible ringing is
connected to the originating office by the tandem office.
Feature interactions
This feature supports the following interactions:
• Moroccan R2 trunk to Moroccan Socotel multifrequency trunk
• Moroccan Socotel multifrequency trunk to Moroccan R2 trunk
• Moroccan R2 trunk to Moroccan R2 trunk
• dial pulse signaling system to Moroccan R2 trunk

NTXH06AA–6 297-1001-801i Standard 09.01 January 2000

 NTXH06AA
AE0897
This feature requires the following features:
• AE0898 Second Dial Tone over Trunks
• AJ0581 Hardware Pulse Reception
• AJ0851 Meter Pulse Tandem
Datafill
Table Description

TRKGRP Field TNDMMODE must be datafilled as EEND in incoming and

outgoing trunk group data to apply special tandeming on
Moroccan R2 trunks to Socotel multifrequency trunks.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH06AA–7

NTXH06AA
AE0898
Feature name
Second Dial Tone Over Trunks
Description
AE0898 provides the capability
• to datafill second dial tone on each trunk group by creating a new field
(DTONE) in table DGHEAD
• for second dial tone to be applied by the terminating trunk toward the
origination subscriber
BCS history
This feature was created in BCS32.
Restrictions and limitations
AE0898 is applicable only on calls coming in on dial pulse trunks, but can
be expanded to support other multifrequency trunk types (except
multifrequency compelled trunks, such as R2 trunks).
The inter-digit timeouts are controlled by standard trunk datafill, not line
datafill.
Dial tone is the only additional tone applied over the trunks. Treatments are
applied according to the particular trunk protocol.
Dial tone is terminated at the end of the first received digit, rather than at the
beginning.
If AE0898 is used outside the Morocco market, changes to the tone selected
may be required.
Datafill
Table Description

DGHEAD Field DTONE is added to select the type of dial tone applied on
each incoming trunk group (NONE, NORM, SPEC, or SPEC2).

NTXH06AA–8 297-1001-801i Standard 09.01 January 2000

 NTXH06AA
AJ0205
Feature name
R2 Protocol Enhancements
Description
This feature implements the R2 protocol for Morocco supported by the
DMS-100/200 switch.
BCS history
This feature was created in BCS28.
Hardware requirements
This feature requires provision of an NT6X69LA (CPP message protocol
and downloadable tones CP) card and an NT6X92CA (international UTR
tone detection) card on international digital trunk controllers (IDTC).
Feature interactions
The following features interact with R2 trunk protocol and function
differently in an R2 environment:
• Call Waiting (CWT)
• Coin Line
• Free Number Terminating (FNT)
• Malicious Call Trace (MCT)
• No Double Connect (NDC)
• Toll Break-in (TBI)
• Call Diversion (CDIV)

If the DMS switch is a terminating exchange, and the called subscriber has
CWT and is busy, the called status signal sent to complete register signaling
is Subscriber Line Free, Charge. When the terminating line has CWT, the
called status signal is returned. In both cases, the DMS switch completes
register signaling, connects the originator to audible ringing, and normal
CWT processing continues for the duration of the call.
When a coin line originates a call over an R2 trunk not supporting the
calling category signal COIN, the DMS switch sends the Regular Subscriber
signal. As a tandem exchange, if the DMS switch receives the calling
category COIN from the originating R2 trunk, and this signal is not
supported by the terminating R2 trunk, the Regular Subscriber signal is
substituted for COIN.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH06AA–9

NTXH06AA
AJ0205
The DMS switch currently does not send the line signal Answer for calls
terminating on a line with FNT. With the R2 signal Subscriber Line Free,
No Charge, there is a method to convey this information to the originating
exchange. With this feature, calls over R2 trunks handle FNT in the
following manner:
• If the DMS switch is the terminating exchange, the register signal for the
called subscriber status Subscriber Line Free, No Charge is sent. When
the call is answered, the line signal Answer is sent to the incoming trunk.
• If the DMS is a tandem exchange in end-to-end mode, the signal for
Subscriber Line Free, No Charge will be tandemed.
• If the DMS is a tandem exchange in link-by-link mode, the DMS
processes the incoming Subscriber Line Free, No Charge signal as
follows:
— If the incoming R2 protocol supports the signal, it is sent to the
originating exchange and when it is received, the line signal Answer
is sent to the originating exchange.
— If the incoming R2 protocol does not support the signal, the called
status signal returned is Subscriber Line Free, Charge. When the line
signal Answer is received from the terminating exchange, it is not
sent to the originating exchange.
— If the incoming trunk from the originating exchange is R1, the line
signal Answer is not sent to the originating exchange when received
from the terminating exchange.
• If the DMS switch is an originating exchange and receives the called
status signal Subscriber Line Free, No Charge, the originating subscriber
is not billed for the call. The line signal Answer is expected and the call
is marked as such when received from the terminating exchange.
The DMS switch only supports MCT through line signaling. The only line
signalling system supporting MCT is NTLS09. If the terminating subscriber
has MCT, the DMS switch does not send the calling number over register
signaling during call setup. If the line signaling supports the MCT signal
and MCT is activated while the DMS switch is an originating or tandem
exchange, the affected trunks and lines are held until released from the MAP
(maintenance and administration position) terminal.
The DMS switch sends the calling category Data for calls originated by lines
with NDC activated. If the DMS switch is a terminating exchange, calls
with the calling category Data are not allowed to double connect.
Manual and automatic TBI are supported by the DMS switch. Calls
originating from an operator (manual TBI) and terminating on a DMS
switch do not send the R2 register signal Subscriber Busy. The subscriber

NTXH06AA–10 297-1001-801i Standard 09.01 January 2000

 NTXH06AA
AJ0205
status signal Congestion is sent and a busy tone is applied to the trunk in the
terminating exchange. The trunk connection remains up, allowing the
operator to send the TBI signal and break in on the subscriber. Automatic
TBI eliminates the requirement for the operator to manually initiate a TBI
signal. When the called party is busy, TBI is performed automatically. With
automatic TBI, no busy treatment is applied and the operator is sent a TBI
tone indicating a busy call has been broken into. The called subscriber
status signal Subscriber Line Free, Charge is returned by the terminating
exchange.
Calls terminating in a DMS switch where the subscriber has CDIV activated
have the Called Subscriber line status of the subscriber line diverted to
Returned.
Datafill
Table Description

ACTTRMT and Values COIN, OPER, DATA, PRIORITY, MTC_EQ,

TRTMTACT REQ_NOT_ACC, SUB_XFRD, TERM_CTRL_CHG, and
TEMP_OUT_ORD are added to field R2_ACTIVITY.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH06AA–11

 NTXH07AA
Belize R2 Signaling
This feature package applies to DMS-100 offices.
NTXH07AA implements the R2 trunking protocol between Belize and
Mexico that is supported by the DMS-100/200 switch.
Feature package contents
Feature package NTXH07AA contents
Feature number Description

AJ0578 Belize R2 Register Signaling

BCS history
This feature package was created in BCS29.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX470AA International–Common Basic
NTX901AA Local Features I
NTX904AA R2 Signaling Base
NTXB83AA ITOPS to International R2 Interworking
NTX472AA International–Local Basic (upgraded by NTX472AB)
or
NTX472AB International–Local Basic (upgrades NTX472AA)

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH07AA–1

NTXH07AA
AJ0578
Feature name
Belize R2 Register Signaling
Description
AJ0578 implements the R2 trunking protocol between Belize and Mexico
that is supported by the DMS-100/200 switch.
BCS history
This feature was created in BCS29.
Hardware requirements
Each international digital trunk controller (IDTC) must be equipped with
two NT6X92CA (universal tone receiver) cards and an NT6X69KA (CPP
message protocol and tones) card.
Restrictions and limitations
The following features are not supported:
• Free Number Terminating with the ANSWER line signal (FNT)
• Malicious Call Trace (MCT)
• No Double Connect (NDC)
• Priority
• Toll Break-in (TBI)

On centralized automatic message accounting (CAMA) calls, the originating

office must know it has to change to receive Group A backwards signals
when a Group III END_OF_DIGITS signal has been sent during an
automatic number identification (ANI) spill.
Feature interactions
The following features interact with R2 trunk protocol and behave in a
different manner in the R2 environment:
• Call Waiting (CWT)
• Cancel Call Waiting (CCW)
• Call Diversion (CDIV)
• Coin Line

NTXH07AA–2 297-1001-801i Standard 09.01 January 2000

 NTXH07AA
AJ0578
Datafill
Table Description

R2CLGSRV The following values replace the existing values in field R2ACT:
ORDFIXED, ORDDEMAND, ORDHALL, PR1FIXED,
PR1DEMAND, PRIHALL, PR2FIXED, ORDFREE,
FREEORFIXED, PBX, PR1RADIO, PR2CABLE, ZORPCALL,
TESTCALL, PR1FIXEDINTL, PR1DEMANDINTL,
PR1HALLINTL, and COIN.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH07AA–3

 NTXH12AA
ITOPS Enhancements for Japan
This feature package applies to DMS-100 offices.
NTXH12AA provides the International Traffic Operator Position System
(ITOPS) operator with the capability to enter free format alphanumeric
digits as a special number for billing to a credit card or a third party. The
operator has to verify the number because the software does not.
Feature package contents
Feature package NTXH12AA contents
Feature number Description

AE0546 ITOPS Enhancement

BCS history
This feature package was created in BCS29.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX470AA International–Common Basic
NTXB05AA ITOPS Common Basic
NTXB13AA ITOPS Toll Basic (upgraded by NTXB13AB)
or
NTXB13AB ITOPS Toll–Enhanced Queueing (upgrades NTXB13AA)

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH12AA–1

NTXH12AA
AE0546
Feature name
ITOPS Enhancement
Description
AE0546 is designed for requirements unique to the Japan DMS-300 switch
application.
AE0546 provides the international traffic operator position system (ITOPS)
operator with the capability to enter up to 18 free format alphanumeric digits
as a special number for billing to a credit card or a third party. The operator
has to verify the number because the software does not.
BCS history
This feature was created in BCS29.

NTXH12AA–2 297-1001-801i Standard 09.01 January 2000

 NTXH13AA
Fixed Duration Calls
This feature package applies to DMS-100 offices.
NTXH13AA allows the International Traffic Operator Position System
(ITOPS) operator to set a fixed duration for a call.
Feature package contents
Feature package NTXH13AA contents
Feature number Description

AJ0177 ITOPS: Fixed Duration Calls

BCS history
This feature package was created in BCS29.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX470AA International–Common Basic
NTXB05AA ITOPS Common Basic
NTXB13AA ITOPS Toll Basic (upgraded by NTXB13AB)
or
NTXB13AB ITOPS Toll–Enhanced Queueing (upgrades NTXB13AA)

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH13AA–1

NTXH13AA
AJ0177
Feature name
ITOPS: Fixed Duration Calls
Description
AJ0177 allows the International Traffic Operator Position System (ITOPS)
operator to set a fixed duration for a call.
At the end of the time period, the call can be disconnected or returned to an
ITOPS position for further handling.
BCS history
This feature was created in BCS29.
Hardware requirements
This feature requires the firmware compatible with the Z80-based ITOPS
controller circuit pack.
Datafill
Table Description

OFCENG Parameter TOPS_FIXED_DURATION is added to indicate

which calls should automatically be set for a fixed duration.

Parameter TOPS_FIXED_DURATION_APS is deleted.

NTXH13AA–2 297-1001-801i Standard 09.01 January 2000

 NTXH16AA
Estimated Call Charges for ITOPS
This feature package applies to DMS-100 offices.
NTXH16AA provides the International Traffic Operator Position System
(ITOPS) operator with the ability to estimate call charges at the ITOPS
position.
Feature package contents
Feature package NTXH16AA contents
Feature number Description

AJ0181 ITOPS: Estimated Call Charges

BCS history
This feature package was created in BCS29.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX470AA International–Common Basic
NTXB05AA ITOPS Common Basic
NTXB13AA ITOPS Toll Basic (upgraded by NTXB13AB)
or
NTXB13AB ITOPS Toll–Enhanced Queueing (upgrades NTXB13AA)

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH16AA–1

NTXH16AA
AJ0181
Feature name
ITOPS: Estimated Call Charges
Description
AJ0181 provides the International Traffic Operator Position System (ITOPS)
operator with the ability to estimate call charges at the ITOPS position.
The charge estimate is dependent upon the
• datafill in the rating system
• attributes of the call
• duration and starting time of the call

BCS history
This feature was created in BCS31.
Hardware requirements
This feature requires version 1.0 or greater of the NT4X62EA ITOPS
controller.
Restrictions and limitations
AJ0181 does not provide the ability to add on surcharges or discounts
applied by the operating company during the call setup phase.
Subscriber-originated estimate (EST) calls cannot be completed by the
operator.
The call charges estimated by the operator may differ from the actual
charges if
• a private branch exchange calculates the charges
• a new set of rates goes in to effect between the time the call charge is
estimated and time the call is completed
• the operating company is performing datafill changes to the rating
system
Feature interactions
AJ0181 makes the FREQ key obsolete.

NTXH16AA–2 297-1001-801i Standard 09.01 January 2000

 NTXH16AA
AJ0181
Datafill
Table Description

CLASSTYP ESTIMATE is added to the range of values in field CALLTYPE

to indicate the call-type to be associated with calls for which
charges have been estimated.

ITOPS ESTIMATE is added to the range of values in field ORIG to

indicate the call-origination type to be associated with estimated
calls.

Automatic message accounting

AJ0181 uses a changed field in Info digit 6 to specify that an estimate has
been provided to the customer. This field does not specify how many
estimates are provided for the customer, only that the operator provides at
least one.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH16AA–3

 NTXH17AA
International ATME 2 for International DMS-100/200I
This feature package applies to DMS-100 offices.
NTXH17AA allows the testing of trunk members and groups, using the
automatic transmission measurement equipment (ATME) version 2 testing
specifications.
Feature package contents
Feature package NTXH17AA contents
Feature number Description

AJ0832 ATME 2 for DMS-100I MFC

BCS history
This feature package was created in BCS30.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX051AA Automatic Trunk Testing
NTX470AA International–Common Basic

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH17AA–1

NTXH17AA
AJ0832
Feature name
ATME 2 for DMS-100I MFC
Description
AJ0832 allows the testing of trunk members and groups, using the automatic
transmission measurement equipment (ATME) version 2 testing
specifications.
The ATME 2 testing operations specified by this feature apply to
multifrequency compelled (MFC) register signaling systems.
BCS history
This feature was created in BCS30.
Hardware requirements
The ATME 2 testing device consists of hardware and associated software.
Two different implementations are used. Each is independent of the other in
operation and approach, but they are equal functionally.
One implementation uses external hardware supplied by the operating
company. External ATME Director and Responder devices are required.
The other implementation uses the following DMS hardware in a peripheral
module:
• NT2X58AT international maintenance trunk module (MTM) shelf
• NT2X47AB transmission test unit controller card
• NT2X56BA digital filter A-law TTU card

Note: The NT2X47AB card and the NT2X56BA card must be placed so
that one is in an even-numbered slot and the other is in an odd-numbered
slot in the MTM to make the correct bus connections.

Note: The NT2X47AB card can also be used in an A-law environment.

Restrictions and limitations

AJ0832 is restricted to MFC signaling systems.
The NT2X47BA card is not equipped to handle the ATME 2 tests. The
NT2X47AB card should be used instead of the NT2X47BA card.
Internal ATME tests TA13 to TA25 cannot be used for trunks using R2 or C1
signaling.
Internal ATME tests TA06 to TA11 work only if the line signaling system on
the trunk under test can send a ring forward signal.

NTXH17AA–2 297-1001-801i Standard 09.01 January 2000

 NTXH17AA
AJ0832
The numbers used to route to individual trunk members must be exclusive of
any other number in the network.
When datafill is added to the CLLI table of an in-service switch, a cold or
reload restart is required to activate the changes.
A trunk member cannot be deleted if it is routed to by a TMEM route
selector in a Universal Translations route table.
Datafill
Table Description

ACRTE, Routing selector TMEM (trunk member) is added to the

CTRTE, Universal Translations system. TMEM includes the following
DNRTE, and fields: CLLI, with a value of DYNAMIC; and EXTRKNM, with a
FARTE value of 0 to 9999.

FTRTE Routing selector TMEM (trunk member) is added to the

Universal Translations system. TMEM includes the following
fields: CLLI, with a value of DYNAMIC; and EXTRKNM, with a
value of 0 to 9999.

OFCRTE Routing selector TMEM (trunk member) is added to the

Universal Translations system. TMEM includes the following
fields: CLLI, with a value of DYNAMIC; and EXTRKNM, with a
value of 0 to 9999.

OFCVAR Parameter CHECK_FOR_TMEM is added with the range of

{N, Y} and the default of Y.

PXRTE Routing selector TMEM (trunk member) is added to the

Universal Translations system. TMEM includes the following
fields: CLLI, with a value of DYNAMIC; and EXTRKNM, with a
value of 0 to 9999.

Following is the datafill sequence for the TMEM field:

• trunk group CLLI in table CLLI
• trunk group in table TRKGRP
• trunk sub-group in table TRKSGRP
• trunk member in table TRKMEM
• translator name (XLANAME) in table xxxHEAD, where xxxHEAD is
one of the tables in the Universal Translations system

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH17AA–3

NTXH17AA
AJ0832
• route reference (RTEREF) in table xxxCODE, where xxxCODE is one
of the tables in the Universal Translations system
• route, which uses the TMEM selector in table xxxRTE, where xxxRTE is
one of the tables in the Universal Translations system

NTXH17AA–4 297-1001-801i Standard 09.01 January 2000

 NTXH18AA
International China TUP
This feature package applies to DMS-100 offices.
NTXH18AA provides subscriber features interaction with China telephone
user part (CTUP) using Common Channel Signaling 7 (CCS7) on the
DMS-100 switch.
Feature package contents
Feature package NTXH18AA contents
Feature number Description

AQ1107 Repackaging of SCCP and MTP for China

TA0124 CTUP Call Processing
TA0125 CTUP and R2 Interworking
TA0126 CTUP Interaction with Subscriber Features
TA0127 New CTUP Messages and C7TU Enhancements – XPM
TA0132 C7TU Enhancements – CC Part
TA0162 OVLP Outpulsing through CTUP Trunks
TA0183 Manual OPR Trunks and CTUP Interworking
TA0193 CTUP XPM Enhancements to Support 24-bit CCITT Point
Code
TA0222 Congestion Control for CTUP Trunks
TA0223 OMs for CTUP Call
TA0224 CTUP Test Trunk Interworking
TA0280 CTUP Interworking to T100/T102
TA0281 ATME/CTUP Interworking

TA0381 FNO Enhancements

TA0413 Call Diversion Enhancement
TA0414 ANI Enhancements
TA0415 Echo Suppressor Bit Mapping
TA0423 CTUP MPM Messaging
TA0424 UNN Enhancement
TA0427 UPU User Part Unavailable—CTUP Part

BCS history
This feature package was created in BCS37.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH18AA–1

NTXH18AA
BCS40i—TA0280 and TA0281 added.
BCS39i—TA0222, TA0223, and TA0224 added.
BCS42i—TA0381, TA0413, TA0414, TA0415, TA0423, TA0424, and
TA0427 added.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX470AA International–Common Basic
NTXH24AA International TUP Base
NTXH40AA CCITT No. 7 TUP Basic
NTX904AA R2 Signaling Base

NTXH18AA–2 297-1001-801i Standard 09.01 January 2000

 NTXH18AA
AQ1107
Feature name
Repackaging of SCCP and MTP for China
Description
This feature repackages the contents of feature package NTXR72AA (CCS7
MTP/SCCP for LPP Based Platforms) into two packages, so as to allow the
message transfer part (MTP) and the signaling connection control part
(SCCP) to be provided independently. This repackaging is undertaken to
meet market-specific requirements.
BCS history
This feature was created in BCS37.
Restrictions and limitations
The SCCP package is required for applications that require service control
point (SCP) application, or any call management system (CMS) call
processing application.
Feature interactions
The MTP package is standalone, but the SCCP package requires the MTP
package in order to perform the required tasks.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH18AA–3

NTXH18AA
TA0124
Feature name
CTUP Call Processing
Description
This feature provides the following interworking for local and toll
international connections using the DMS-100 and DMS-200 switches as
required:
• line to China telephone user part (CTUP)
• CTUP to CTUP
• CTUP to line

BCS history
This feature was created in BCS37.
Restrictions and limitations
The following activities are not supported:
• overlap outpulsing
• toll break-in
• continuity check
• operator calls at the toll office
• generation of subsequent address messages, subsequent address
messages with one signal, operator messages, or metering pulse
messages
• subscriber feature interactions
• trunk metering

Feature interactions
This feature interacts with the following features:
• TA0127 New CTUP Messages and C7TU Enhancements
• TA0132 C7TU Enhancements
Datafill
Table Description

C7UPTMR CTUP IS added as a protocol type, with associated refinements.

Operational measurements
This feature creates a new extension block to store the incoming trunk and
transit exchange identity.

NTXH18AA–4 297-1001-801i Standard 09.01 January 2000

 NTXH18AA
TA0124
Logs
This feature creates log MCT105 to identify the incoming trunk and the
transit office.
Log C7UP105 is modified to include additional reasons.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH18AA–5

NTXH18AA
TA0125
Feature name
CTUP and R2 Interworking
Description
This feature implements the following trunk interworking on DMS-100 and
DMS-200 switches:
• China telephone user part (CTUP) to R2
• R2 to CTUP

BCS history
This feature was created in BCS37.
Restrictions and limitations
Malicious Call Trace (MCT) is not supported by this feature.
On C1/multifrequency compelled (MFC) to CTUP and C1/MFC to CTUP to
C1/MFC local tandem calls, the calling line identification information is not
available at the terminating local office.
This feature supports interworking only between 14-bit CTUP and C1/MFC.
Interworking involving 24-bit CTUP is not supported.
Answer signals, no charge (ANN) that are received from CTUP trunks are
converted to answer signal (ANS) at the C1/MFC side.
This feature does not support the mapping of hardware metering pulses
received over the C1/MFC trunks to meter pulse messages (MPM).
This feature does not support overlap outpulsing and inpulsing.
This feature does not support continuity checking.
This feature does not support C1/MFP and CTUP or C1/DP and CTUP
interworking.

NTXH18AA–6 297-1001-801i Standard 09.01 January 2000

 NTXH18AA
TA0126
Feature name
CTUP Interaction with Subscriber Features
Description
This feature provides subscriber features interaction with China telephone
user part (CTUP) using Common Channel Signaling 7 (CCS7) on the
DMS-100 switch. This feature also implements a restriction on the use of
CTUP trunks for intercity calls.
BCS history
This feature was created in BCS37.
Restrictions and limitations
This feature changes the functionality of the emergency services group
(ESG) subscriber feature. If the originating call is routed over a CTUP
trunk, ESG does not provide special treatment before audible ringing is
applied to the calling subscriber.
Feature interactions
This feature interacts with the following features:
• TA0124 CTUP Call Processing
• TA0125 CTUP and R2 Interworking
Datafill
Table Description

TRKGRP Traffic classes ITLL and TLLC are now invalid classes for
protocol CTUP.

Logs
One of the following logs is generated if an attempt is made to datafill
CTUP trunks for intercity working:
• PROTOCOL FIELD CAN NOT BE DATAFILLED AS CTUP WHEN
TRFC IS ITLL OR TLLC IN TABLE TRKGRP
• TRAFFIC CLASS CAN NOT BE CHANGED AS ITLL OR TLLC
WHEN PROTOCOL FIELD IS CTUP IN TABLE TRKSGRP

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH18AA–7

NTXH18AA
TA0127
Feature name
New CTUP Messages and C7TU Enhancements – XPM
Description
This feature defines the meter pulse message (MPM) for China telephone
user part (CTUP) signaling in the PCM30 digital trunk controller (PDTC).
The feature also implements the appropriate actions in response to operator
(OPR), MPM, reanswer (RAN) and calling party clear (CCL) messages
received by the PDTC.
BCS history
This feature was created in BCS37.
Feature interactions
This feature interacts with the following features:
• TA0124 CTUP Call Processing
• TA0132 C7TU Enhancements – CC Part

NTXH18AA–8 297-1001-801i Standard 09.01 January 2000

 NTXH18AA
TA0132
Feature name
C7TU Enhancements – CC Part
Description
This feature creates the CTUP metering pulse message (MPM). MPM is
also defined for the C7TU test tool to allow C7TU to support MPM.
BCS history
This feature was created in BCS37.
Feature interactions
This feature is a requirement for the following features:
• TA0124 CTUP Call Processing
• TA0127 New CTUP Messages and C7TU Enhancements – XPM
User interface
C7U test tool is enhanced to support MPM. MPM is listed as a valid
message type.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH18AA–9

NTXH18AA
TA0162
Feature name
OVLP Outpulsing through CTUP Trunks
Description
TA0162 provides overlap outpulsing signaling through Chinese telephone
user part (CTUP) trunks in DMS-100/200 offices. Overlap outpulsing
signaling is supported only for toll calls.
When overlap outpulsing signaling is used, post dial delay is reduced and
the connection of the agents in a call gets faster.
TA0162 supports the following types of calls:
• C1 to CTUP
• CTUP to C1
• CTUP to CTUP
• line to CTUP

BCS history
This feature was created in BCS38i.
Hardware requirements
International XMS-based peripheral modules (IXPM), such as international
digital trunk controllers (IDTC) and international line group controllers
(ILGC), should be equipped with the NTMX77 and NT7X80 unified
processor cards for C1-to-CTUP, CTUP-to-C1, and line-to-CTUP overlap
outpulsing signaling.
Refer to features TA0133 and TA0134 for the hardware requirement details.

Restrictions and limitations

Overlap outpulsing signaling is supported only for toll calls.
When the International Call Transfer (ICT) feature is used, only the first leg
of the call can use overlap outpulsing signaling. The second leg of the call is
established as it was previously.
Overlap outpulsing signaling has an impact on the DMS real time of 5% to
25%, because the resource use time is increased by overlap outpulsing
signaling.
The field REPEACH should be used for only overlap outpulsing signaling
calls. Using this field for other calls is an inefficient use of the DMS real
time. Also, table DGCODE becomes crowded.

NTXH18AA–10 297-1001-801i Standard 09.01 January 2000

 NTXH18AA
TA0162
In repeat attempt CTUP-to-CTUP overlap signaling calls, if the terminating
agent involved in the second attempt is a CTUP trunk, the first initial
address message with additional information (IAI) or initial address message
(IAM) is sent as it was in the previous connection. Then, all the digits
received after the previously sent IAI or IAM are put in a subsequent
address message (SAM).
In line-to-CTUP or C1-to-CTUP repeat attempt calls, all the digits received
so far are put in an IAI or IAM, and succeeding digits are sent in a
subsequent address message with one signal (SAO) or a SAM.
Feature interactions
The following subscriber features are supported:
• Warm Line (WNL)
• Hot Line (HTL)
• Abbreviated Dialing (ADL)
• ICT

Datafill
Table Description

DGCODE The RAN and COLL selections for DGCLSEL fields are
changed to provide one-by-one digit reporting by the
XMS-based peripheral module (XPM). Field REPEACH is
added to report each digit as it is received from lines or trunks.

The range of values is Y and N. The default value is N.

TRKSGRP Field OVLAP is added to the TRKSGRP table OG/2W

refinement of Common Channel Signaling 7 (CCS7) trunks.
CTUP OG/2W trunks can use overlap outpulsing signaling
when field OVLAP is datafilled with Y.

The range of values is Y and N. The default value is N.

Logs
Log DFIL 320 is added to warn about inefficient datafill of digit analysis
and translation tables in the line-to-CTUP and C1-to-CTUP overlap
signaling calls.
This log is generated when the digit analysis tables are datafilled to report
the significant number of digits from the originating line or trunk but
reported digits are not the MIN digits datafilled in the translation tables.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH18AA–11

NTXH18AA
TA0183
Feature name
Manual OPR TRKS and CTUP Interworking
Description
This feature provides interworking between Chinese telephone user parts
(CTUP) trunks and manual or semi-automatic operator trunks for
DMS-100/200 offices in China.
BCS history
This feature was created in BCS38i.
Restrictions and limitations
This feature is
• for the China market only
• supported by DMS-100i switches only

This feature does not support

• called party control is not supported for CH02 trunks termination on
no-answer boards
• the toll break-in feature

Reanswer timing is not handled for interworkings between CTUP and

• CH01
• CH03
• CH04
• CH09

Rering is valid only for calling party-controlled calls.

For Malicious Call Trace and emergency calls, the terminal id of the
operator trunk and the signaling point code of the switch are provided,
instead of the calling line id in the General forward set-up information
message being provided.
Feature interactions
This feature interacts with feature TA0158 (Toll Break-in on CTUP for
DMS-100i).

NTXH18AA–12 297-1001-801i Standard 09.01 January 2000

 NTXH18AA
TA0193
Feature name
CTUP XPM Enhancements to Support 24-bit CCITT Point Code
Description
TA0193 implements enhancements in the XMS-based peripheral module
(XPM) to support Chinese telephone user part (CTUP) with 24-bit point
code.
The 14-bit point code is extended to 24-bit point code by feature AR0909
(CCS7 Network Management Support for 24-bit CCITT Point Code).
Consequently, a CCITT message transfer part (MTP) variant for DMS
service switching point (SSP) and signaling transfer point (STP) nodes is
created.
BCS history
This feature was created in BCS38i.
Restrictions and limitations
TA0193 is available on XMS-based peripheral modules (XPM) only.
Feature interactions
This feature interacts with the following features:
• AR0908 CCS7 Table Control for 24-bit CCITT Point Code
• AR0909 CCS7 Network Management Support for 24-bit CCITT
Point Code
• AR0910 XPM Support for 24-bit CCITT Point Code

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH18AA–13

NTXH18AA
TA0222
Feature name
Congestion Control for CTUP Trunks
Description
This feature provides congestion control as specified in CCITT Blue Book
Recommendations Q 704, section 11.2.3 for DMS-100 and DMS-200
switches using 24-bit point code and acting as signaling points (SP) or as
service switching points (SSP). Congestion control procedures reduce and
increase signaling traffic in increments.
BCS history
This feature was created in BCS39i.
Restrictions and limitations
This feature is supported only on a
• DMS switch acting as a SP or SSP
• level 4 telephone user part (TUP)
• National Telephone Network of China No. 7 (NTC7) message transfer
part (MTP)
If subfield CALLATTMPT in table C7RTESET is datafilled as nil,
congestion control will not take place.
Feature interactions
The SKIP command in network management (NWM) at the GRPCTRL
level of the MAP position takes precedence over the rerouting of initial
address messages (IAM).
Datafill
Table Description

C7RTESET Field OPTION with value ICONG and subfield CALLATTMPT

are added.
OFCVAR Office parameter CONGESTION_CONTROL, containing
subfields CALLATTMPT, TUE1, AND TUE2, is added.

NTXH18AA–14 297-1001-801i Standard 09.01 January 2000

 NTXH18AA
TA0223
Feature name
OMs for CTUP Call
Description
This feature provides operational measurement (OM) groups DCTS, TRK,
and TRKDCTS and periodic report ACHGXREP for China telephone user
part (CTUP) trunk groups. It also creates new registers in OM groups DCTS
and TRKDCTS. OM groups DCTS, TRK, and TRKDCTS supply traffic
data for trunk groups and destination codes.
BCS history
This feature was created in BCS39i.
Restrictions and limitations
This feature is available for the following office types:
• DMS-100
• DMS-200
• DMS-100 and DMS-200 combination
• DMS-100 and DMS-200 International Traffic Operator Position System
(ITOPS)
When the trunk of the last office is a China 1 (C1) or multifrequency
compelled (MFC) type, the following registers are not activated for
reanswered calls or free number terminating (FNT) calls:
• NANSO of OM group DCTS
• NANS of OM group TRK
• NANST of OM group TRKDCTS
• ANSPEG of ACHGXREP report

Neither OM group DCTS nor TRKDCTS is activated for destination codes

when a subset of the destination code is sufficient to start an overlap call..
Registers NB2 and NB3 are not activated for local and toll busy calls.
If either an unsuccessful backward setup information message (UBM) or a
national backward setup message (NUB) is received after an address
complete message (ACM), registers DCTS_NSCO, DCTS_NNUBUBMO,
TRKDCTS_NSCT, and TRKDCTS_NNUBUBMT are incremented.
Feature interactions
This feature interacts with the following features:
• AE0943 Active OMs in Erlangs
• AE1240 OM Enhancements for Unsuccessful Calls

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH18AA–15

NTXH18AA
TA0223
• AL2530 OM Pegging for Answer Attempts
• AL2549 Traffic Distinction OMs
• AL2720 Traffic Distinction OMs – Call Processing
Operational measurements
This feature extends the functionality of OM groups DCTS, TRK, and
TRKDCTS to CTUP calls.
This feature creates OMs to record
• initial address messages (IAM)
• initial address messages with additional information (IAI)
• national unsuccessful backward setup messages (NUB)
• UBMs
• nonreceived messages after the forward address message (FAM)

This feature creates the following DCTS registers:

• NIAMIAIO records the number of IAM and IAI messages
routed to the office
• NNUBUBMO records the number of NUB and UMB messages
routed to the office
• NNMAFAMO records the number of nonreceived messages after
FAM has been sent
This feature also creates the following TRKDCTS registers:
• NIAMIAIT records the number of IAM and IAI messages
routed to the trunk
• NNUBUMT records the number of NUB and UBM messages
routed to the trunk
• NNMAFAMT records the number of nonreceived messages after
the FAM has been sent

NTXH18AA–16 297-1001-801i Standard 09.01 January 2000

 NTXH18AA
TA0224
Feature Name
CTUP Test Trunk Interworking
Description
This feature provides 101 test lines for DMS-100 and DMS-200 China
telephone user part (CTUP) trunks. The 101 test line provides a two-way
voice connection between a test position and any incoming or outgoing
trunk.
BCS history
This feature was created in BCS39i.
Hardware requirements
This feature requires the following hardware at the switch:
• 1A2 keyboard
• terminal equipment
• NT2X58AT (international maintenance trunk module shelf)
• NT5X30AA (101 communication test line circuit)

Restrictions and limitations

The 101 test line can be incoming or outgoing but not two-way.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH18AA–17

NTXH18AA
TA0280
Feature name
CTUP Interworking to T100/T102
Description
This feature provides the interworking between T100 and T102 test lines
and China telephony user part (CTUP) trunks. This enables the manual and
automatic testing of CTUP trunks using T100 and T102 test lines.
BCS history
This feature was created in BCS40i.
Hardware requirements
This feature requires a 1X00KA card (950 Hz tone at 0 dB).

NTXH18AA–18 297-1001-801i Standard 09.01 January 2000

NTXH18AA NTXH18AA
TA0281 TA0281
Feature name
ATME/CTUP Interworking
Description
This feature provides testing of China telephony user part (CTUP) trunks.
Two methods are available: external and internal. External tests use the
automatic transmission measurement equipment version 2 (ATME-2C)
supplied by the operating company, and internal tests use DMS hardware
and are performed from the Maintenance and Administration Position
(MAP) terminal.
The ATME equipment consists of a directing device at the outgoing end
(director) which generates a set of digits, and a responding device at the
incoming end (responder) which measures the tones received. The call is
routed using the Universal Translations system.
BCS history
This feature was created in BCS40i.
Hardware requirements
Internal tests require a trunk test unit (TTU) in a maintenance trunk module
(MTM) to be set up as follows:
• 2X47AB (Mu-law) CP (control processor and signal generator) card
• 2X56BA (A-law) DF (digital filter) card

The CP and DF cards must be placed so that one is in an even slot and the
other is in an odd slot in the MTM.
Restrictions and limitations
The following restrictions apply to this feature:
• For external testing,
— the ATME-2C director and responder devices must be CCITT or
China type
— translation should not be datafilled as INTL/NATL class to ensure
the initial address message (IAM) is sent
• For internal testing,
— test frequencies specified in CCITT 0.22 are supported
— test frequencies specified in TS-01-90 Annex B are not supported
Feature interactions
This feature requires feature AJ0832 (ATME 2 for DMS–100i MFC) to
function properly.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH18AA–19

NTXH18AA
TA0381
Feature name
FNO Enhancements
Description
This feature provides the free number origination (FNO) capability to the
China telephone network, to allow operating companies to route
non-chargeable calls. Lines that have the FNO option are not metered.
This capability applies to both local and toll calls. For national and
international class calls, the chargeable call bit of the call info field of the
international centralized automatic message accounting (ICAMA) record is
set to N(No).
FNO applies to both R2 register and common channel signaling no. 7
(CCS7) signaling.
BCS history
This feature was created in BCS42i.
Hardware requirements
Not applicable
Restrictions and limitations
Not applicable
Feature interactions
Not applicable
Datafill
Not appicable
Service orders
Existing FNO line option is implemented.
Operational measurements
Not applicable
Logs
Not applicable
User interface
Not applicable

NTXH18AA–20 297-1001-801i Standard 09.01 January 2000

 NTXH18AA
TA0381
Automatic message accounting
The operating company may charge each type of call differently, based on
the attributes assigned to the subscriber’s line, by setting the appropriate
values in the call info field of the ICAMA record.
See International Billing Services, 297-2181-020 for details.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH18AA–21

NTXH18AA
TA0413
Feature name
Call Diversion Enhancement
Description
This feature prevents a China telephone user part (CTUP) call that has
already been diverted from being diverted again.
This activity operates with call diversion features as follows:
• If Call Diversion to Subscriber (CDS) or Call Diversion to Subscriber
Fixed (CDF) is active, any subsequent diversion is deactivated, an SST
message is sent back from the incoming CTUP trunk, and originator’s
line is given busy treatment.
• If Call Diversion to Announcement (CDA) or Call Diversion to Operator
(CDO) is active, any subsequent diversion is deactivated, an SST
message is sent back from the incoming CTUP trunk, and originator’s
line is given busy treatment.
• If Call Diversion on Busy (CDB) or Call Diversion on Busy Fixed
(CDBF) is active, any subsequent diversion is deactivated, an SLB or
STB message is sent back from the incoming CTUP trunk, and
originator’s line is given busy treatment.
• If Call Diversion on No Answer (CDNA) or Call Diversion on No
Answer Fixed (CDNAF) is active, any subsequent diversion is
deactivated, and called party’s telephone continues to ring.
BCS history
This feature was created in BCS42i.
Hardware requirements
Not applicable
Restrictions and limitations
All trunks between originating and terminating offices must be CTUP
trunks.
Feature interactions
Not applicable
Datafill
Not applicable
Service orders
Not applicable
Operational measurements
Not applicable

NTXH18AA–22 297-1001-801i Standard 09.01 January 2000

 NTXH18AA
TA0413
Logs
Not applicable
User interface
Not applicable
Automatic message accounting
Not applicable

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH18AA–23

NTXH18AA
TA0414
Feature name
ANI Enhancements
Description
This feature permits the prefixing of automatic number identification (ANI)
digits to the serving numbering plan area (SNPA) code.
For feature activation, office parameter SNPA_REQUIRED is introduced in
table OFCVAR.
BCS history
This feature was created in BCS42i.
Hardware requirements
Not applicable
Restrictions and limitations
The following restrictions and limitations apply:
• A maximum of 13 ANI digits is supported for R2 and China telephone
user part (CTUP) trunks.
• The first originating toll office in the call connection must be operating
in a link-by-link mode.
• If the call is not CTUP-specific, an ANI string that already contains the
area code is prefixed again.
• This feature supports trunks that have the following characteristics:
— group type is MTR.
— direction is incoming or two way.
— traffic class is CAMA.
— translation class is national or international.

Feature interactions
Not applicable
Datafill
Table Description

OFCVAR Office parameter SNPA_REQUIRED is added.

The range of values is Y or N. The default is N.

The SNPA is obtained from table TRKAREA; this table must be datafilled
for the associated trunk group.

NTXH18AA–24 297-1001-801i Standard 09.01 January 2000

 NTXH18AA
TA0414
Service orders
Not applicable
Operational measurements
Not applicable
Logs
Not applicable
User interface
Not applicable
Automatic message accounting
Not applicable

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH18AA–25

NTXH18AA
TA0415
Feature name
Echo Suppressor Bit Mapping
Description
This feature supports the echo suppressor bits in the following China
telephone user part (CTUP) messages:
• outgoing echo suppressor bit in the initial address message (IAM)
• outgoing echo suppressor bit in the initial address message with
additional information (IAI)
• outgoing echo suppressor bit in the general forward setup information
message (GSM)
• incoming echo suppressor bit in the address complete message (ACM)

Line and trunk interworking is supported as follows:

• line to CTUP
• CTUP to line
• CTUP to CTUP
• CTUP to R2
• R2 to CTUP

BCS history
This feature was created in BCS42i.
Hardware requirements
Not applicable
Restrictions and limitations
Not applicable
Feature interactions
Not applicable
Datafill
Not applicable
Service orders
Not applicable
Operational measurements
Not applicable
Logs
Not applicable

NTXH18AA–26 297-1001-801i Standard 09.01 January 2000

 NTXH18AA
TA0415
User interface
Not applicable
Automatic message accounting
Not applicable

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH18AA–27

NTXH18AA
TA0423
Feature name
CTUP MPM Messaging
Description
This feature provides the generation, transmission, and reception of the
meter pulse message (MPM). The MPM carries call-charge information
over China telephone user part (CTUP) trunks.
The MPM provides pulse counts that are used in switching office metering
systems, including those in offices that do not contain call tariffs for certain
call routes.
MPM messaging operates as follows:
• The generation and transmission of MPMs are provided at the
originating toll office. The meter pulse count contained in the MPM is
used to update the trunk meter of the originating toll trunk.
• At the tandem office, MPMs are relayed back to the originating office.
The meter pulse count contained in the MPM is used to update the trunk
meter of the originating tandem trunk.
• The originating office receives the MPM, and the meter pulse count is
used to update the line software meter.
This feature supports existing DMS-100i metering system methods, services,
and limitations.
BCS history
This feature was created in BCS42i.
Hardware requirements
Not applicable
Restrictions and limitations
The following restrictions and limitations apply:
• Received MPMs are not converted to physical meter pulses on the
subscriber premises meter (SPM) or on metered coin lines.
• Received MPMs are not converted to physical meter pulses on C1
trunks.
• Generated MPMs are not converted to physical meter pulses, and are not
sent through CTUP to C1 trunks.
• MPM message generation is used only for demand-type calls.
• MPM messaging is supported only by a PCM30 digital trunk controller
(PDTC+) load.

NTXH18AA–28 297-1001-801i Standard 09.01 January 2000

 NTXH18AA
TA0423
• Subscriber feature activation using flash is not supported for a call
during meter pulse tandeming and reception.
• A call-diverted call cannot use meter pulse tandeming and reception.
• For MPM generation calls, if a warm SWACT occurs between two
consecutive MPMs, the interval between them may be 100 ms shorter or
longer than the actual charging time unit.
• For MPM reception calls, a warm SWACT can cause the loss of the
meter pulse count for the final 4 s.
• The free period can vary between 100 ms and 200 ms.
Feature interactions
Not applicable
Datafill
Not applicable
Service orders
Not applicable
Operational measurements
Not applicable
Logs
Not applicable
User interface
Not applicable
Automatic message accounting
Not applicable

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH18AA–29

NTXH18AA
TA0424
Feature name
UNN Enhancement
Description
This feature provides the capability to apply treatment, at either the
originating or the terminating office, for an unallocated number (UNN).
When an unallocated number is detected in a China telephone user part
(CTUP) call, a UNN message is returned from the terminating to the
originating office. The terminating office then applies announcement or
tone treatment to the originating CTUP trunk over the speech path.
For feature activation, office parameter APPLY_UNN_TREAMENT_
FROM_FAR_END is introduced in table OFCVAR.
BCS history
This feature was created in BCS42i.
Hardware requirements
Not applicable
Restrictions and limitations
The following limitations and restrictions apply:
• For this feature to operate correctly, all offices along the call route must
have this functionality.
• This feature does not provide far-end UNN treatment for R2 trunks; the
call must be CTUP-specific.
Feature interactions
Not applicable
Datafill
Table Description

OFCVAR Office parameter

APPLY_UNN_TREATMENT_FROM_FAR_END is added.
The range of values is Y or N. The default is N.

Service orders
Not applicable
Operational measurements
Not applicable

NTXH18AA–30 297-1001-801i Standard 09.01 January 2000

 NTXH18AA
TA0424
Logs
Not applicable
User interface
Not applicable
Automatic message accounting
Not applicable

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH18AA–31

NTXH18AA
TA0427
Feature name
UPU User Party Unavailable—CTUP Part
Description
This feature provides the China telephone user part (CTUP) part of the user
part unavailable (UPU) common channel signaling no. 7 (CCS7) message.
UPU is a CCS7 signaling network management (SNM) message generated
when a local user part is unavailable to receive a message forwarded by the
message transfer part (MTP). UPU informs the originating site about
unavailable user parts at the terminating signaling points. This feature
allows the cessation of signaling to the unavailable user parts, and
resumption of signaling when they become available again.
Log report C7UP650 is introduced.
A non-menu command, SETUPAVL, is introduced.
Office parameter UPU_GAURD is introduced.
BCS history
This feature was created in BCS42i.
Hardware requirements
Not applicable
Restrictions and limitations
The following restrictions and limitations apply:
• This feature applies only to CTUP as a user part.
• Information on the availability of the far-end user part is lost after a
reload restart.
• The OP (outpulse) command is not supported. Consequently, calls
originated by this command are not stopped if the remote user part is
unavailable.
• Trunk maintenance commands at the TTP level of the MAP that generate
CTUP messages to remote user parts are not supported. Existing
maintenance procedures take place without regard to remote user part
availability.
• If a UPU_GUARD value is changed in an office where UPU handling is
already functioning, timing control operates only on those UPUs that are
received after the change.
Feature interactions
Not applicable

NTXH18AA–32 297-1001-801i Standard 09.01 January 2000

 NTXH18AA
TA0427
Datafill
Table Description

OFCVAR Office parameter UPU_GUARD is added. It has two fields:

UPU_TUP_CONTROL_ENABLED
The range of values is Y or N. The default is N.

UPU_GUARD_TIMEOUT
The range of values is 0 to 60 (each unit equals 10 seconds).
The default is 0.

Field UPU_GUARD_TIMEOUT specifies the interval between the

reception of a UPU message and the resumption of signaling to the user part.
Service orders
Not applicable
Operational measurements
Not applicable
Logs
Log C7UP650 is generated when the destination user part in an outgoing call
is determined to be unavailable.
User interface
The non-menu command SETUPAVL is introduced to assign or change the
availability state of the local CTUP. This command has parameters AVAIL
and UNAVAIL. If set to UNAVAIL, a UPU message is sent to the remote
user parts from which the received CTUP message was transmitted.
Automatic message accounting
Not applicable

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH18AA–33

 NTXH19AA
CTUP Local
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTXH19AA contents
Feature number Description

TA0158 Toll Break-in on CTUP for DMS-100I

TA0182 ICT Interaction with CTUP Trunks
TA0225 ESG Interaction with CTUP Trunks
TA0226 3WC, 6WC, and CWT Interaction with CTUP Trunks

TA0422 CTUP Continuity

BCS history
This feature package was created in BCS38i.
BCS39i—TA0225 and TA0226 added.
BCS42i—TA0422 added.
Required feature packages
Required feature packages
Feature package Description
number

NTX472AB International–Local Basic

NTXH18AA International China TUP

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH19AA–1

NTXH19AA
TA0158
Feature name
Toll Break-in on CTUP for DMS-100I
Description
TA0158 adds capabilities to the Toll Break-in (TBI) feature for the
DMS-100 switch in the international market.
TBI functionality for China is described in feature AG0710 (Toll Break-in
for China – DMS-100i). TBI functionality for the termination office is
described in feature BC2265 (International Toll Break-in).
TA0158 allows the
• TBI to interwork with the Chinese telephone user parts (CTUP) at the
terminating local office
• operating company to test the TBI signal by simulation from the trunk
test position (TTP) level of the MAP (maintenance and administration
position) display, using CTUP trunks
• called-party subscriber to re-answer the call that the operator has applied
TBI to
BCS history
This feature was created in BCS38i.
Hardware requirements
The ITOPS interaction to CTUP is not supported by this feature. An ITOPS
to R2 loop-around is used.
Restrictions and limitations
The international traffic operator position system (ITOPS) interaction with
CTUP is not supported.
TA0158 does not change the existing TBI functionality. Instead, feature
TA0158 concerns the handling of the call the operator is applying TBI to.
This modification applies only when the subscriber, who the operator is
trying to reach over a termination CTUP trunk, is the called party in an
existing trunk call.
Datafill
Table Description

TRKSGRP The value ORIGCNTL is added to field OPTIONS. ORIGCNTL

is added to an incoming or two-way CTUP tuple in table
TRKSGRP when originating alert control is used in the TBI
feature. When the ORIGCNTL option is not present,
terminating alert control is in effect.

NTXH19AA–2 297-1001-801i Standard 09.01 January 2000

 NTXH19AA
TA0182
Feature name
ICT Interaction with CTUP Trunks
Description
TA0182 provides International Call Transfer (ICT) interaction with Chinese
telephone user part (CTUP) trunks. ICT allows a subscriber to transfer a call
to a third party. When the second and third parties are connected, the
subscriber initiating the transfer is released from the call.
ICT interaction with CTUP is provided only for DMS-100 and DMS-200
switches outside North America. This feature does not change the existing
ICT functionality.
TA0182 supports the following types of calls:
• incoming calls from CTUP trunks to CTUP trunks
• incoming calls from CTUP trunks to R2 trunks
• incoming calls from R2 trunks to CTUP trunks
• incoming calls from international lines to CTUP trunks
• incoming calls from CTUP trunks to international lines

BCS history
This feature was created in BCS38i.
Restrictions and limitations
TA0182 is specific to China because CTUP is used only in China.
TA0182 provides ICT interaction with CTUP trunks, but does not change
the functionality of ICT.
Dial pulse (DP) to CTUP interworking is not supported so CTUP to R2
looparound trunks are recommended for DP to CTUP interworking.
ICT does not interact with subscriber features that are not available for
CTUP, such as Call Waiting (CWT), Three-way Call (3WC), and Six-way
Call (6WC).
Feature interactions
This feature interacts with the following features:
• Abbreviated Dialing (ADL)
• Call Diversion (CDIV)
• Denied Origination (DOR)
• Denied Termination (DTM)
• Do Not Disturb (DND)

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH19AA–3

NTXH19AA
TA0182
• Feature Denied (FDN)
• Free Number Termination (FNT)
• Hot Line (HTL)
• Hunt Groups
• International Call Recording (ICR)
• International Line Restrictions (ILR)
• Malicious Call Trace (MCT)
• No Double Connect (INDC)
• Operator Calls
• Plug Up (PLP)
• Semi-permanent Connection (SPC)
• Subscriber Premise Meter (SPM)
• Suspended Service (SUS)
• Toll Break-in (TBI)
• Warm Line (WNL)

NTXH19AA–4 297-1001-801i Standard 09.01 January 2000

 NTXH19AA
TA0225
Feature name
ESG Interaction with CTUP Trunks
Description
This feature provides Emergency Service Group (ESG) subscriber feature
interaction with China telephone user part (CTUP) trunks for the DMS-100
Family of switches. It also implements the following capabilities for ESG
calls:
• special treatment before ringing
• called party control
• re-ring capability
• automatic printout of the calling subscriber name or incoming trunk
common language location identifier (CLLI)
BCS history
This feature was created in BCS39i.
Feature interactions
This feature interacts with the following features:
• AG0995 Emergency Service Group
• AJ1432 ESG Enhancements
• TA0126 CTUP Interaction with Subscriber Features
Logs
This feature cancels log ESG102 and generates log ESG100 in its place. For
intraswitch calls, log ESG100 records the calling subscriber number; for
interswitch calls, log ESG100 records the CLLI of the incoming CTUP
trunk.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH19AA–5

NTXH19AA
TA0226
Feature name
3WC, 6WC, and CWT Interactions with CTUP Trunks
Description
This feature provides three-way calling (3WC), six-way calling (6WC), and
call waiting (CWT) capabilities for China telephone user part (CTUP) trunks
for the DMS-100 Family of switches.
BCS history
This feature was created in BCS39i.
Hardware requirements
The 3WC and 6WC require three-port and six-port conference circuits,
respectively.
Feature interactions
This feature interacts with TA0126 (CTUP Interaction with Subscriber
Features) and the following features:
• Abbreviated Dialing (ADL)
• Call Diversion (CDIV)
• Denied Transmission (DTM)
• Free Number Termination (FNT)
• Hot Line (HTL)
• Hunt Groups
• International Call Recording (ICR)
• International Feature Metering (IFM)
• Malicious Call Trace (MCT)
• Operator Calls
• Plug Up (PLP)
• Subscriber Activation (SA)
• Subscriber Premise Meter (SPM)
• Suspended Services
• Toll Break-in (TBI)
• Warm Line (WLN)

NTXH19AA–6 297-1001-801i Standard 09.01 January 2000

NTXH19AA NTXH19AA
TA0422 TA0422
Feature name
CTUP Continuity

Description
This feature provides continuity test (COT) functionality between both ends of a
China telephone user part (CTUP) trunk, including associated interworkings and
feature interactions.

Line and trunk interworking is supported as follows:

• line to CTUP
• CTUP to line
• CTUP to CTUP
• CTUP to C1
• C1 to CTUP
COT interactions with other SERVORD-assigned features are also supported.

This feature supports the following standard continuity tests:

• COT-on-demand test, which can be performed only on two-way and outgoing
CTUP trunks
• per-call COT test, which tests system interworkings and feature interactions

The following datafillable timers are added to table C7UPTMR to make

COT testing more flexible:
• T1WAITTCOT
• T8CHKTONETMR
• T9COTFAILTMR
• T10COTFAIL2
Log report C7UP129 is introduced by this feature.

BCS history
This feature was created in BCS42i.

Hardware requirements
No hardware is introduced by this feature. However, operating company personnel
must ensure that the NTX6X70 continuity tone detection card is installed in the cor-
rect slots of the PDTC-UP frame.

Restrictions and limitations

The following restrictions and limitations apply:
• The COT-on-demand test is restricted to three attempts. However, it is
suggested that the operating company personnel take appropriate action after
the failure of the first attempt.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH19AA–7

NTXH19AA
TA0422
• The per-call COT test is restricted to two attempts.
• If the COT test fails on features ICT, 3WC, or 6WC, the call is not attempted
on another trunk.

Feature interactions
Not applicable

Datafill
Table Description

C7UPTMR Four datafillable timers are introduced:

T1WAITTCOT specifies the allowable time between receiving the

initial address message (IAM) and receving the COT or CCF (conti-
nuity check failed) message.

T8CHKTONETMR sets the duration of the tone check.

T9TCOTFAILTMR specifies the time between sending the first CCF

message and sending its associated CCR (continuity check re-
quest) message, following a COT failure.

T10TCOTFAIL2 specifies the time between sending subsequent

CCF and CCR messages (see T9TCOTFAILTMR entry), until conti-
nuity is detected.

Service orders
Not applicable

Operational measurements
Not applicable

Logs
Log report C7UP129 is generated when a COT test fails. It provides information
about the cause of the failure.

User interface
Not applicable

Automatic message accounting

Not applicable

Additional information
It is suggested that the continuity test be performed primarily on analog trunks, or
analog-digital combinations, to minimize real-time impact.

When testing two-way trunks, it is suggested that COT be applied at both ends, to
avoid glare.

NTXH19AA–8 297-1001-801i Standard 09.01 January 2000

 NTXH22AA
International Local Metering
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTXH22AA contents
Feature number Description

AC0054 CC Metering for Features

AE0056 Meter Count Printout
AE0292 Metering Line Capacity Enhancements
BV1277 CC–Internal Changeover for Metering

BCS history
This feature package was created in BCS18.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX47OAA International–Common Basic
NTX474AA International Base Metering
NTX901AA Local Features I
NTX472AA International–Local Basic (upgraded by NTX472AB)
or
NTX472AB International–Local Basic (upgrades NTX472AB)

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH22AA–1

NTXH22AA
AC0054
Feature name
CC Metering for Features
Description
This feature provides the capability of metering conference calls (three party
and six party) using a central control (CC) metering process, periodically
check for calls longer than 2 h, and provide metering information when call
data is lost in an international XMS-based peripheral module (IXPM).
BCS history
This feature was created in BCS22.
Restrictions and limitations
The following call types cannot be pegged on a subscriber premise meter
(SPM): three-way calling (3WC), six-way calling (6WC), call diversion to
announcement (CDA), call diversion to operator (CDO), call diversion to
subscriber (CDS), and call waiting (CWT).
Datafill
Table Description

OFCENG Office parameter MAX_PM_CHARGE_COUNT is deleted.

Office parameters NUM_CCMTR_EXT_BLOCKS is added to

specify the number of CC metering extension blocks required
for CC metering.

Office parameter CCMTR_FAILURE_FREE_CALL is added to

specify if new calls are to be processed when no CC metering
resources are available.

Operational measurements
Registers EXTSEIZ, EXTOVFL, and EXTUSAGE in group EXT are
modified to include monitoring of extension block
INTL_CCMTR_EXT_BLOCK which holds CC metering data.
Logs
Log MTR125 is generated when there are no metering extension blocks
available.
Automatic message accounting
When metering tariffs are changed, existing calls will reflect the new
metering data.

NTXH22AA–2 297-1001-801i Standard 09.01 January 2000

 NTXH22AA
AE0056
Feature name
Meter Count Printout
Description
This feature enables the software meter counts for a subscriber to be printed.
BCS history
This feature was created in BCS22.
User interface
The command PRINT is added to the line test position metering (LTPMTR)
level of the MAP (maintenance and administration position) display to print
all the meter counts for a directory number.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH22AA–3

NTXH22AA
AE0292
Feature name
Metering Line Capacity Enhancements
Description
This feature increases the number of lines available for software metering in
a DMS-100 switch to 64 534.
BCS history
This feature was created in BCS24.
Datafill
Table Description

OFCENG Office parameter SIZE_OF_METER_TABLE is deleted. Office

parameter MAX_LINES is added to specify the maximum
number of lines on the switch.

OFCVAR Office parameter ALLOCATE_METERS_ON_NIL_CHANGE is

deleted.

Logs
Logs MTR121 and MTR124 are deleted.
Log MTR116 is revised to reference meter blocks instead of meters.
Logs MTR118 and MTR123 are revised to specify the associated meter
block instead of the meter name and count.
User interface
The command QMETER at the MTRSYS level of the MAP display is
cancelled and replaced by the command QMTRBLK which displays the
number of used and unused meter blocks containing recycled meters.
The command interpreter (CI) command DELFM is added to delete feature
meters assigned to a line or all lines in an office. The contents of each meter
are written to the meter’s out-of-service file.
Automatic message accounting
This feature allows operating companies to charge for the International Do
Not Disturb (IDND) feature.

NTXH22AA–4 297-1001-801i Standard 09.01 January 2000

 NTXH22AA
BV1277
Feature name
CC - Internal Changeover for Metering
Description
This feature provides the capability of changing metering tariffs based on
the time of day and the type of day.
BCS history
This feature was created in BCS18.
Restrictions and limitations
Tariff changeovers cannot occur more than once every 30 min.
A maximum of eight tariff changeovers are allowed in a 24-h period.
Feature interactions
This feature requires the following features:
• BC1058 CC - Metering Charge Recording
• BC1059 (New) CC - Internal Metering Tariff Application
• BV1136 Time-of-Day Routing
• BV1207 CC - Metering Rate Determination
• BV1208 CC - Metering System Maintenance and Monitor
Datafill
Table Description

TIMEODAY This table is added to specify the time of day result for each
time of day system and day type.

TODHEAD This table is added to specify how tables DAYOWEEK,

DAYOYEAR, and TIMEODAY are used for call metering.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH22AA–5

 NTXH23AA
Metering Over Junction (MOJ)
This feature package applies to DMS-100 offices.
NTXH23AA provides meter pulse reception in a tandem situation.
Feature package contents
Feature package NTXH23AA contents
Feature number Description

AJ0581 Meter Pulse Reception and Tandem I

AJ0851 Meter Pulse Reception and Tandem II

BCS history
This feature package was created in BCS32.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX470AA International–Common Basic
NTX474AA International Base Metering

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH23AA–1

NTXH23AA
AJ0581
Feature name
Meter Pulse Reception and Tandem I (PREP)
Description
AJ0581 provides the capability to
• receive meter pulses over trunks on the DMS-100 switch
• specify the attributes of the expected pulses
• receive the meter pulses and place the count in the appropriate software
meters
• connect received meter pulses in tandem from outgoing digital trunks to
incoming digital trunks
• connect received meter pulses in tandem from outgoing digital trunks to
subscriber premise meters (SPM)
BCS history
This feature was created in BCS32.
Restrictions and limitations
The following restrictions apply to feature AJ0581:
• A call involved in meter pulse reception cannot flash to use a subscriber
feature.
• Only outgoing trunks can reference tuples in table MTSIGSYS that have
the FUNCTION field set to RECEPTION.
• A maximum of 64 tuples are allowed in table MTSIGSYS.
• Only one of the signaling bits can be used for meter pulse reception.
• Some types of signals cannot be distinguished from a meter pulse if both
signals are received by the same bit.
• The value of the IDLSTATE field must match the idle state of the
signaling bit for the signaling system being used.
• The DEMAND option in field CALLSET only works on C1 trunks.
• The STI (Source Tariff Index) subfield is not used for the LNRECEIVE
and TKRECEIVE values in field HWMWTER (in table MSRCDATA)
and should contain a value of zero (0).
• Meter pulse reception is restricted to trunks using the NTLS15, NTLS16,
and NTLS20 signaling systems.
• Two-way trunks are not capable of receiving meter pulses.
• For reception tuples in table MTSIGSYS, the value in field
MAX_PULSE_WIDTH must be greater than the value in field
MIN_PULSE_WIDTH.

NTXH23AA–2 297-1001-801i Standard 09.01 January 2000

 NTXH23AA
AJ0581
• If tandemed meter pulses arrive at a rate faster than the originating agent
can receive, the call fails.
The following limitations apply to feature AJ0581:
• There is no interim updating of the software meters for long duration
calls involved with reception.
• The real time in the international digital trunk controller (IDTC) used for
receiving hardware meter pulses is proportional to the frequency of the
pulses.
• The real time in the IDTC used for receiving hardware meter pulses is
proportional to the number of trunks performing meter pulse reception.
• An IDTC warm switch of activity (SWACT) may corrupt a physical
pulse such that the pulse width or interpulse gap may be smaller than
what was actually sent.
• In signaling systems in which the meter pulse reception bit is also one of
the signaling its, a meter pulse will be lost if a line signal follows a meter
pulse by a time less than the interpulse gap specified in table
MTSIGSYS.
• An international XMS-based peripheral module (IXPM) warm SWACT
may result in the pulse count in the newly active unit being out of step
by one minute’s worth of pulses for each warm SWACT performed.
• In table MTSIGSYS, if field CLDCLF takes a value other than
NOCHANGE, field GUARDTIME must be set to a zero.
• Pulses may be lost from between a clear forward signal and a reanswer
signal sent on an outgoing trunk.
• Pulses may be lost from between a clear back signal and a reanswer
signal received on an outgoing trunk.
• Pulses may be lost when a clear forward signal is sent on an outgoing
trunk if scanning for pulses is suppressed.
• Calls performing meter pulse reception when an IXPM cold SWACT
occurs will not be billed.
• The smallest pulse width that can be detected is 20 ms.
• The pulse count reported to the central control (CC) by the terminating
agent may be different than the count reported by the originator.
• An IXPM cold SWACT may cause the loss of up to one minute’s worth
of meter pulses.
• The maximum rate at which pulses can be tandemed is four pulses per
second.
• Filtering of received and tandemed pulses may cause a propagation delay
of up to 1 s for meter pulses.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH23AA–3

NTXH23AA
AJ0581
Feature interactions
The Meter count field in the international centralized automatic message
accounting (ICAMA) record contain the meter pulses.
The Meter pulse field in the logs generated by APS, ICR, PMC, and SCR
use the received meter pulse count.
Datafill
Table Description

MSRCDATA LNRCEIVE, LNRCMOJ, TKRECEIVE, and TKRCVNOJ are

added to the range of values in field HWMETER.

MTSIGSYS Field ANSREQD is added, with values of Y and N. This field

must be set to Y.

Field GUARDTIM is added, with a value range of 10 to 1000.

This field applies only if the CLDCLF field has a value of
STOPMTR.

Field LOGZERO is added, with a value of Y or N.

Field MAXPLSWD is added, with a value range of 10 to 1000.

Field MINIGAP is added, with a value range of 10 to 1000.

Field MINPLSWD is added, with a value range of 10 to 1000.

RECEPTION is added to the range of values in field

FUNCTION.

OFCENG Office parameter NUM_CCMTR_EXT_BLOCKS has been

renamed to NUM_MTR_EXT_BLOCKS. The default value has
been changed from 25 to 100.

OFCVAR Parameter METER_PULSE_MISMATCH_THRESHOLD is

added.

If the threshold is exceeded and the absolute difference

between the counts is greater than 1, an MTR145 log is
generated.

The default value is 5%.

NTXH23AA–4 297-1001-801i Standard 09.01 January 2000

 NTXH23AA
AJ0581
Logs
The following logs are generated for this feature:
• MTR144
• MTR145
• MTR146
• MTR147
• MTR148
• MTR149

Automatic message accounting

The received pulse counts are recorded in the ICAMA record for the
originating party.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH23AA–5

NTXH23AA
AJ0851
Feature name
Meter Pulse Reception and Tandem II
Description
AJ0851 provides the tandeming of meter pulses from
• outgoing digital trunks to incoming digital trunks
• outgoing digital trunks to subscriber premise meters (SPM)

BCS history
This feature was created in BCS33.
Restrictions and limitations
The following restrictions apply to feature AJ0851:
• A call involved in meter pulse reception cannot flash to use a subscriber
feature.
• The pulse count reported to the central control (CC) by the terminating
agent may be different than the count reported by the originator.
• If tandemed meter pulses arrive at a rate faster than the originating agent
can receive, the call fails.
• An international XMS-based peripheral module (IXPM) warm switch of
activity (SWACT) may result in the pulse count in the newly active unit
being out of step by one minute’s worth of pulses for each warm
SWACT performed.
• The maximum rate at which pulses can be tandemed is
four pulses per second.
• Filtering of received and tandemed pulses may cause a propagation delay
of up to 1 s for meter pulses.
Feature interactions
AJ0851 uses the hardware pulse reception functionality provided by feature
AJ0581 (Meter Pulse Reception and Tandem I [PREP]).

NTXH23AA–6 297-1001-801i Standard 09.01 January 2000

 NTXH23AA
AJ0851
Datafill
Table Description

MSRCDATA LNRCVMOJ and TKRCVMOJ are added to the range of values

in field HWMETER.

OFCVAR Parameter METER_PULSE_MISMATCH_THRESHOLD is

added to define the percentage difference that may occur
between pulses received and pulses tandemed when
tandeming is being performed.

If the threshold is exceeded and the absolute difference

between the counts is greater than 1, an MTR145 log is
generated.

Logs
The following logs are generated for this feature:
• MTR145
• MTR146
• MTR147
• MTR149
• MTR151

Automatic message accounting

The received pulse counts are recorded in the international centralized
automatic message accounting (ICAMA) record for the originating party.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH23AA–7

 NTXH54AA
ITOPS–Account Code Access
This feature package applies to DMS-100 offices.
NTXH54AA provides the capability to restrict toll access to subscriber lines.
An authorization access code, known as an account code, is assigned to each
line. Toll services are denied to a line that does not have an account code.
Feature package contents
Feature package NTXH54AA contents
Feature number Description

AJ1026 ITOPS: Account Codes I

AJ1255 ITOPS: Account Codes II

BCS history
This feature package was created in BCS31.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTXB13AA ITOPS Toll Basic (upgraded by NTXB13AB)
or
NTXB13AB ITOPS Toll–Enhanced Queueing (upgrades NTXB13AA)

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH54AA–1

NTXH54AA
AJ1026
Feature name
ITOPS: Account Codes I
Description
AJ1026 provides the capability to restrict toll access to subscriber lines. An
authorization access code, known as an account code, is assigned to each
line. Toll services are denied to a line that does not have an account code.
The International Traffic Operator Position System (ITOPS) operator has to
verify the account code. Call details cannot be keyed in by the operator until
a valid account code is entered.
AJ1026 satisfies requirements for the network in China. Automatic toll
calling is restricted in China because so few circuits are available.
BCS history
This feature was created in BCS31.
Restrictions and limitations
Account codes must have three to ten numbers.
Only one account code can be datafilled against a directory number.
The call details key function does not display the account code back to the
operator position.
There is no operator override function for account code validation.
The operator is restricted to a limited set of key functions prior to validating
the account code.
Only 30 720 subscribers can be datafilled with an account code in a
DMS-200 switch.
A valid account code freezes the calling number for Operator Number
Identification/automatic number identification failed (ONI/ANIF) calls.
For ONI/ANIF calls, the calling number must be entered first if the
ITOPS_ACCOUNT_CODES office parameter has been activated.
Activation or deactivation of the ITOPS_ACCOUNT_CODES office
parameter does not require a restart.
Feature interactions
AJ1026 affects only incoming calls that require operator intervention.
The SPL key is used to identify the account code to the system.

NTXH54AA–2 297-1001-801i Standard 09.01 January 2000

 NTXH54AA
AJ1026
The account code is automatically erased from the SPL key display area
after it is validated.
Datafill
Table Description

ACCTCODE This table has been added. It has two entries: DN (key index)
and Account Code (three to ten-digit number).

OFCENG Added office parameter ITOPS_ACCOUNT_CODES. This

parameter determines whether the account code feature is
activated or deactivated.

Operational measurements
Group ACCTCODE has been added to track the following counts for each
traffic office:
• account code attempts (which is the sum of the following three counts)
• operator-initiated account code failures
• operator-initiated account code successes
• system-initiated account code failures

User interface
AJ1026 adds a screen display variation. The operator uses the SPL key to
identify and verify the account code. The key sequences for this function
are not altered.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH54AA–3

NTXH54AA
AJ1255
Feature name
ITOPS: Account Codes II
Description
AJ1255 provides the capability to restrict toll access to subscriber lines. An
authorization access code, known as an account code, is assigned to each
line. Toll services are denied to a line that does not have an account code.
The International Traffic Operator Position System (ITOPS) operator has to
verify the account code. Call details cannot be keyed in by the operator until
a valid account code is entered.
This feature also supports
• mapping of up to ten unique account codes to one subscriber line
• initiating a call from a directory number (DN) other than the DN the
account code is assigned to
• account code display
• account code recording in automatic message accounting (AMA)
facilities
BCS history
This feature was created in BCS32.
Hardware requirements
If every DN is datafilled with ten account codes much more datastore is
required.
Restrictions and limitations
Account codes must have three to ten numbers.
Up to ten account codes can be datafilled against a directory number. Each
account code must be unique.
The call details key function displays the account code back to the operator
position after account code verification, if the ITOPS_ACCOUNT_CODES
office parameter for subfield DISPLAY is set to Y for yes.
The account code is automatically erased from the ACC display area if the
office parameter ITOPS_ACCOUNT_CODES in subfield DISPLAY is set
to N for no.
The ACC key is used instead of the SPL key to identify account codes to the
ITOPS system. The SPL key in this application allows the operator to enter
subscriber number for remote DN access.

NTXH54AA–4 297-1001-801i Standard 09.01 January 2000

 NTXH54AA
AJ1255
There is no operator override function for account code validation.
The operator is restricted to a limited set of key functions prior to validating
the account code.
Only 30 720 subscribers can be datafilled with an account code in a
DMS-200 switch.
Valid account code input freezes the calling number for Operator Number
Identification/automatic number identification failed (ONI/ANIF) calls.
For ONI/ANIF calls, the calling number must be entered first if the
ITOPS_ACCOUNT_CODES office parameter has been activated.
Activation of the ITOPS_ACCOUNT_CODES office parameter does not
require a restart.
Feature interactions
The account code is automatically erased from the ACC display area only if
the office parameter ITOPS_ACCOUNT_CODES, subfield DISPLAY, is set
to N for no.
The ACC key function is used to identify account codes to the ITOPS
system rather than the SPL key function. The SPL key function allows the
operator to enter subscriber numbers for remote DN access.
Datafill
Table Description

ACCTCODE Office parameter ITOPS_ACCOUNT_CODES has been divided

into sections: ACTIVE, DISPLAY, and AMA.

Logs
The log AMAB187 ITOPS Account Codes extension has been added.
User interface
The operator key function ACC has been added. The function initiates
account code entries. The SPL key function is now utilized to identify
remote DN access during account code verification.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH54AA–5

NTXH54AA
AJ1255
Automatic message accounting
The option to refer to the account code in the AMA information has been
added. The default is N for no.
The account code can be included for the following reasons:
• to add the account code to an existing ITOPS AMA extension record
• to define a new extension record generated solely for account code
verification

NTXH54AA–6 297-1001-801i Standard 09.01 January 2000

 NTXH58AA
Guyana R2 Signaling
This feature package applies to DMS-100 offices.
NTXH58AA provides the R2 development required to meet the Guyana R2
variant.
Feature package contents
Feature package NTXH58AA contents
Feature number Description

AJ1265 Guyana Signaling

BCS history
This feature package was created in BCS32.
Required feature packages
Required feature packages
Feature package Description
number

NTX001AA Common Basic

NTX904AA R2 Signaling Base
NTXB69AA R2 for DMS-100 International
NTX472AA International–Local Basic (upgraded by NTX472AB)
or
NTX472AB International–Local Basic (upgrades NTX472AA)

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH58AA–1

NTXH58AA
AJ1265
Feature name
Guyana Signaling
Description
AJ1265 provides the R2 development required to meet the Guyana R2
variant.
BCS history
This feature was created in BCS32.
Restrictions and limitations
Development for the Guyana R2 protocol variant is restricted to the
measurement results outlined in the Guyana signaling measurement trip
report.
Guyana-specific timing parameters for the line signals on the R2 trunks
cannot be verified by this feature.
The method of collecting digits that is used on the international toll switch in
the Guyana network is not supported by the DMS switch.
The hybrid R2 system for collecting automatic number identification (ANI)
is not supported by the DMS switch.
The DMS switch does not generate or accept END_OF_DIGS as an
indication of the end of called party digits.
Feature interactions
The following features interact with R2 signaling and behave in a different
manner in the R2 environment:
• Automatic TBI
• Call Control
• Call Diversion (CDIV)
• Call Waiting (CWT)
• Coin Line
• Free Number Termination (FNT)
• Malicious Call Trace (MCT)
• Manual TBI
• No Double Connect (NDC)
• Toll Break-in (TBI)

NTXH58AA–2 297-1001-801i Standard 09.01 January 2000

 NTXH58AA
AJ1265
Datafill
Table Description

OFCENG GUYANA is added to the range of values for

MARKET_OF_OFFICE.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH58AA–3

 NTXH60AA
Morocco ITOPS Trunk Interworking
This feature package applies to DMS-100 offices.
NTXH60AA provides a comprehensive range of operator services in
Morocco by supporting interactions between DMS International Traffic
Operator Position System (ITOPS) trunks and Moroccan signaling systems.
Feature package contents
Feature package NTXH60AA contents
Feature number Description

AE0735 Socotel to ITOPS Interworking

BCS history
This feature package was created in BCS32.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH60AA–1

NTXH60AA
AE0735
Feature name
Socotel to ITOPS Interworking
Description
AE0735 provides a comprehensive range of operator services in Morocco by
supporting interactions between DMS International Traffic Operator
Position System (ITOPS) trunks and Moroccan signaling systems.
The following interactions are supported:
• DMS ITOPS and Moroccan Socotel trunks
• DMS ITOPS and Moroccan R2 trunks
• DMS ITOPS and international manual trunks

BCS history
This feature was created in BCS32.
Restrictions and limitations
The following features are not supported for Socotel trunks:
• Called Party Control
• Toll Break-in (TBI)

The following restrictions apply to manual trunks:

• Metering is not supported.
• ANI is not supported.
• The WINK to dial pulse trunk traffic must be only one way, therefore the
international manual trunks will be direction specific.
• The WINK to dial pulse trunk cannot work with ITOPS directly, but
must go by way of an R1 looparound.
Feature interactions
This feature interacts with the ITOPS features developed for the Caribbean,
Mexico, and China.

NTXH60AA–2 297-1001-801i Standard 09.01 January 2000

 NTXH70AA
C7 Support for Channelized Access
This feature package provides support for the link interface unit 7 (LIU7)
channelized access product.
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTXH70AA contents
Feature number Description

AI0407 LIU7 Support for Channel Access Interface

AL1929 C7Link Support for Channelized Access

BCS history
This feature package was created in BCS35.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX941AA CM Common
NTXH77AA Channelized Access on LPP/LIS
Either
NTXR72AA CCS7 MTP/SCCP for LPP-based Platforms
or
NTX041AB CCS7—MTP/SCCP

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH70AA–1

NTXH70AA
AI0407
Feature name
LIU7 Support for Channel Access Interface
Description
AI0407 adds functions to the NT9X76AA (signaling terminal (ST) card) to
support the NTEX26AA (channel bus interface (CBI) card) in its application
as a link terminating paddle board. New functions include diagnostics and
utilities.
BCS history
This feature was created in BCS35.
Restrictions and limitations
The “channelized” LIU7 supports only a single channel from the channel
bus (C-bus). Link speeds of 64 kbytes/s and 56 kbytes/s are available;
subrate link speeds are not supported. Link speed 48 kbytes/s is supported
for the Japanese market.
Feature interactions
This feature requires features AC0145 (MTP—STP ST L2/L3 Queue/Buffer
Structures) and AC0146 (MTP—STP ST CCS7 Application Code).
Datafill
Table Description

LIUINV NTEX26AA is added to the range of values for field PBPEC to

specify the product engineering code (PEC) of the selected
paddle board.

NTXH70AA–2 297-1001-801i Standard 09.01 January 2000

 NTXH70AA
AL1929
Feature name
C7LINK Support for Channelized Access
Description
AL1929 provides changes to table C7LINK and linkset channel
management support for the link interface unit 7 (LIU7) channelized access
product. Channelized access is provided by the network interface unit
(NIU), a DMS SuperNode peripheral module (PM).
BCS history
This feature was created in BCS35.
Hardware requirements
This feature requires the following hardware:
• a link peripheral processor (LPP)
• an NIU
• a junctor network (JNET) or enhanced network (ENET)
• a digital trunk controller (DTC) or PCM30 DTC (PDTC)
• one NTEX26AA (paddle board card) for each LIU7

Feature interactions
This feature requires the following features:
• AI0407 LIU7 Support for Channel Access Interface
• AI0408 Local MTCE and Diagnostics of Network Interface Unit
(NIU)
• AI0409 Channel-bus (C-bus) Maintenance
• AI0410 Network Interface Unit (NIU) Central Maintenance
Datafill
Table Description

C7LINK LIUCHANNEL IS added to the range of options for field ALLOC

to enable datafilling of an LIU7 resource.

Logs
This feature modifies logs CCS101–8, CCS156–65, CCS173, 176, and 190.
These logs display resources used for links defined in table C7LINK with
allocation scheme LIUCHANNEL.
This feature modifies logs AUDT612, 616, 620, 622, and 624. These logs
display resources used for links defined in table C7LINK with allocation
scheme LIUCHANNEL.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH70AA–3

NTXH70AA
AL1929
User interface
This feature modifies MAP command POST in directory C7LKSET. This
command displays the resources associated with a particular link in a linkset.

NTXH70AA–4 297-1001-801i Standard 09.01 January 2000

 NTXH71AA
ITOPS Intrusion Tones
This feature package applies to DMS-100 offices.
NTXH71AA provides an intrusion tone to indicate to the calling and the
called parties that the call has been returned to the operator and is no longer
private. The tone is heard by the parties involved in the call and by the
operator.
Feature package contents
Feature package NTXH71AA contents
Feature number Description

AJ0179 ITOPS: Intrusion Tones

BCS history
This feature package was created in BCS28.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX470AA International–Common Basic
NTXB13AA ITOPS Toll Basic (upgraded by NTXB13AB)
or
NTXB13AB ITOPS Toll–Enhanced Queueing (upgrades NTXB13AA)

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH71AA–1

NTXH71AA
AJ0179
Feature name
ITOPS: Intrusion Tones
Description
AJ0179 provides an intrusion tone to indicate to the calling and the called
parties that the call has been returned to the operator and is no longer
private. The tone is heard by the parties involved in the call and by the
operator.
The intrusion tone is generated in the following situations:
• The call is placed from a coin line and the time paid for has elapsed.
• The subscriber has requested that the operator interrupt the call after a
specified period of time.
• A call has been placed on permanent hold.

BCS history
This feature was created in BCS28.
Hardware requirements
This feature requires the following card:
• NT3X67BB (conference circuit with TBI tone)

Restrictions and limitations

The intrusion tone is identical to the tone used for the Toll Break-in feature.
Datafill
Table Description

OFCOPT Parameter TOPS_INTRUSION_TONE is added to specify

whether or not the tone is to be applied to the office.

NTXH71AA–2 297-1001-801i Standard 09.01 January 2000

 NTXH77AA
Channelized Access on LPP/LIS
This feature package provides the maintenance system for the network
interface unit (NIU) in a SuperNode peripheral module (PM) and diagnostics
to isolate hardware faults.
This feature package applies to DMS SuperNode offices.
Feature package contents
Feature package NTXH77AA contents
Feature number Description

AI0409 Channel Bus (C-Bus) Maintenance

AI0408 Local MTCE And Diagnostics of Network Interface Unit (NIU)
AI0410 Network Interface Unit (NIU) Central Maintenance

BCS history
This feature package was created in BCS34.
Required feature packages
Required feature packages
Feature package Description
number

NTXF20AA LMS on LPP

NTXN18AA F-Bus—LIU Base
NTX000AA Bilge
NTX001AA Common Basic
NTX041AB CCS7—MTP/SCCP

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH77AA–1

NTXH77AA
AI0408
Feature name
Local MTCE and Diagnostics of Network Interface Unit (NIU)
Description
AI0408 provides the local node maintenance system of the network interface
unit (NIU) in a SuperNode peripheral module (PM) and diagnostics to
isolate hardware faults to the single board level. This feature also provides
the local portion of connection support to establish and disconnect PCM data
channels across the NIU.
BCS history
This feature was created in BCS34.
Feature interactions
This feature interacts with the following features:
• AI0407—LIU7 Support for Channel Access Interface (CBI) (CAI)
• AI0409—C-Bus Maintenance
• AI0410—NIU Central Maintenance
• AL1929—C7LINK Support for Channelized Access

NTXH77AA–2 297-1001-801i Standard 09.01 January 2000

 NTXH77AA
AI0409
Feature name
Channel Bus (C-Bus) Maintenance
Description
AI0409 provides software structure for the C-bus maintenance of the
network interface unit (NIU).
BCS history
This feature was created in BCS34.
Hardware requirements
This feature requires the computing module (CM), message switch (MS),
local message switch (LMS), NIU, and application specific unit (ASU).
Feature interactions
This feature interacts with the following features:
• AI0086—Physical Level Maintenance for F-Bus
• AI0408—Local MTCE and Diagnostics of the Network Interface Unit
(NIU)
• AI0410—Network Interface Unit (NIU) Central Maintenance

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH77AA–3

NTXH77AA
AI0410
Feature name
Network Interface Unit (NIU) Central Maintenance
Description
AI0410 provides central maintenance for the network interface unit (NIU).
This maintenance consists of the following elements:
• table control for NIU inventory table (NIUINV)
• MAP command interface
• operational measurements (OMs)
• logs
• alarms

BCS history
This feature was created in BCS34.
Restrictions and limitations
The repeater (NT9X74DA) must be datafilled in the link interface module
(LIM) or message switch (MS) F-bus shelf for correct NIU operation.
A maximum of 6 LIUs for a three-slot shelf and 10 LIUs for a two-slot shelf
are allowed when used with the NIU.
A maximum of 30 NIUs are allowed per office.
A warning is displayed with prompting when an attempt is made to
manually busy an NIU with channels still allocated by the application.
Abort task (ABTK) and broadcast loading are not supported.
Feature interactions
This feature interacts with the following features:
• AI0407—LIU7 Support for Channel Access Interface (CBI) (CAI)
• AI0408—Local MTCE and Diagnostics of Network Interface Unit
(NIU)
• AI0409—Channel Bus (C-Bus) Maintenance

Datafill
Table Description

NIUINV Table is added to datafill the location of NIUs, their default load,
physical cards in each unit, and links to the network.

NTXH77AA–4 297-1001-801i Standard 09.01 January 2000

 NTXH77AA
AI0410
This feature increases program store by a maximum of 64 Kbytes and
increases data store by a maximum of 24 Kbytes.

User interface
This feature adds MAP directory RPDIRl. Directory RPDIR includes
commands TST, BSY, RTS, OFFL, LOADPM, QUERYPM, WAIT,
PMRESET, and DEVICES.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH77AA–5

 NTXH79AA
Brazil Signaling
This feature package applies to DMS-100 offices.
NTXH79AA provides the R2 protocol and the continuous digital R2 line
signaling system required for the interface between the mobile telephone
exchange (MTX) and the DMS-200 switch in Brazil.
Feature package contents
Feature package NTXH79AA contents
Feature number Description

AJ1124 Brazil R2 Enhancements

BCS history
This feature package was created in BCS31.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX270AA New Peripheral Maintenance Package
NTX470AA International–Common Basic
NTX904AA R2 Signaling Base

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH79AA–1

NTXH79AA
AJ1124
Feature name
Brazil R2 Enhancements
Description
AJ1124 provides the R2 protocol and the continuous digital R2 line
signaling system required for the interface between the mobile telephone
exchange (MTX) and the DMS-200 switch in Brazil.
BCS history
This feature was created in BCS31.
Hardware requirements
This feature requires an international digital trunk controller (IDTC)
equipped with the following cards:
• NT6X69LA (CPP message protocol and downloadable tones CP)
• NT6X92CA (International UTR tone detection)

Restrictions and limitations

The R2 line signaling system (NTLS16) applies to one-way trunks only.
The following signals are not generated by the MTX to a DMS-200
application:
• II-7 Subscriber With Special Billing
• II-4 COIN (local coin phone)
• II-5 OPER (operator)
• II-6 DATA (data)
• II-7 Toll Coin Phone
• II-11 Subscriber With Transfer
• A-2 FIRST_DIGIT (send from the first digit)
• A-7 LAST_BUT_2 (send last but two)
• A-8 LAST_BUT_3 (send last but three)
• A-9 LAST_BUT_1 (send last but one)
• B-2 SUB_BUSY (Subscriber line busy)
• B-3 SUB_XFRD (subscriber transferred)
• B-5 Connect_CALL_NOCHG (subscriber line free, no change)
• FRLS Force Release Ack

The calling party address sent from the MTX to the DMS-200 cannot exceed
seven characters in length.

NTXH79AA–2 297-1001-801i Standard 09.01 January 2000

 NTXH79AA
AJ1124
Datafill
Table Description

LNSIGSYS Field FLTR is added to specify the line signaling filter time.

The following fields are added to the NTLS16 tuple: RMINFLT,

RMINFRLS, SMINFRLA, and SMINFLT.

The following fields are removed from the NTLS16 tuple:

RMINMTR, RMAXMTR, and RMTRSETL.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH79AA–3

 NTXH80AA
Mexico Signaling
This feature package applies to DMS-100 offices.
NTXH80AA provides the R2 signaling protocol required for Mexico and for
the interface between the mobile telephone exchange (MTX) and the
DMS-200 switch in Brazil.
Feature package contents
Feature package NTXH80AA contents
Feature number Description

AJ1124 Brazil R2 Enhancements

AJ1423 Mexican R2 and Fixed ANI Trunks

BCS history
This feature package was created in BCS31.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX270AA New Peripheral Maintenance Package
NTX470AA International–Common Basic
NTX904AA R2 Signaling Base

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH80AA–1

NTXH80AA
AJ1124
Feature name
Brazil R2 Enhancements
Description
AJ1124 provides the R2 protocol and the continuous digital R2 line
signaling system required for the interface between the mobile telephone
exchange (MTX) and the DMS-200 switch in Brazil.
BCS history
This feature was created in BCS31.
Hardware requirements
This feature requires an international digital trunk controller (IDTC)
equipped with the following cards:
• NT6X69LA (CPP message protocol and downloadable tones CP)
• NT6X92CA (International UTR tone detection)

Restrictions and limitations

The R2 line signaling system (NTLS16) applies to one-way trunks only.
The following signals are not generated by the MTX to a DMS-200
application:
• II-7 Subscriber With Special Billing
• II-4 COIN (local coin phone)
• II-5 OPER (operator)
• II-6 DATA (data)
• II-7 Toll Coin Phone
• II-11 Subscriber With Transfer
• A-2 FIRST_DIGIT (send from the first digit)
• A-7 LAST_BUT_2 (send last but two)
• A-8 LAST_BUT_3 (send last but three)
• A-9 LAST_BUT_1 (send last but one)
• B-2 SUB_BUSY (Subscriber line busy)
• B-3 SUB_XFRD (subscriber transferred)
• B-5 Connect_CALL_NOCHG (subscriber line free, no change)
• FRLS Force Release Ack

The calling party address sent from the MTX to the DMS-200 cannot exceed
seven characters in length.

NTXH80AA–2 297-1001-801i Standard 09.01 January 2000

 NTXH80AA
AJ1124
Datafill
Table Description

LNSIGSYS Field FLTR is added to specify the line signaling filter time.

The following fields are added to the NTLS16 tuple: RMINFLT,

RMINFRLS, SMINFRLA, and SMINFLT.

The following fields are removed from the NTLS16 tuple:

RMINMTR, RMAXMTR, and RMTRSETL.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH80AA–3

NTXH80AA
AJ1423
Feature name
Mexican R2 and Fixed ANI Trunks
Description
AJ1423 implements the modifications to the generic R2 signaling system
required for Mexico. The modifications include:
• adding new register signals to the R2 signaling system
• allowing the application of Toll Break-in (TBI) to a line that is
subscriber busy
• adding new billing category signals for calls terminating to International
Traffic Operator Position System (ITOPS) operators. These signals let
the operator know if special handling is required, for example, collecting
coins for a call placed at a pay phone.
• implementing fixed automatic number identification (ANI) on outgoing
R2 CAMA or tandem CAMA (TNCA) trunks. Fixed ANI is a method of
providing, from a datafilled table, address information required for
signaling.
BCS history
This feature was created in BCS33.
Restrictions and limitations
The following signals are propagated, but cannot be originated, by the DMS
exchange: ATME, TIME_AND_CHG, SHARED_1, SHARED_2, and
SHARED_3.
Fixed ANI applies to outgoing or two-way metering (MTR) trunks only.
Fixed ANI is not used on maintenance calls.
A maximum of 63 ANI tuples can be datafilled in table FIXEDANI. At
least one digit must be datafilled for each tuple.
Field ANIIDX in table FIXEDANI must be datafilled with a NIL value for
trunks with a traffic class other than CAMA on TNCA.

NTXH80AA–4 297-1001-801i Standard 09.01 January 2000

 NTXH80AA
AJ1423
Datafill
Table Description

FIXEDANI This table is created to datafill the ANI information for the
outgoing and two-way CAMA trunks that use Fixed ANI.

R2CLGSRV TIME_AND_CHG, SHARED_1, SHARED_2, and SHARED_3

are added to the range of values in field R2_CLG_ACT.

TRKGRP Field ANIIDX is added to indicate if ANI information should be

taken from table FIXEDANI or from the calling party.

MEXR2 is added to the range of values in field PROTIDX to

indicate the R2 protocol for the trunk.

MEXTRT is added to the range of values in field TRTMTIDX to

indicate the R2 treatment mapping for the trunk.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH80AA–5

 NTXH95AA
Metering Enhancements
This feature package applies to DMS-100 offices.
NTXH95AA implements changes to the metering system to ensure that all
datafill changes made to a line (assigning, deleting, or changing the line,
directory number (DN), or assignable features) are recorded.
Feature package contents
Feature package NTXH95AA contents
Feature number Description

AE0838 Metering Enhancements

BCS history
This feature package was created in BCS35.
Required feature packages
Required feature packages
Feature package Description
number

NTX474AA International Base Metering

NTXH22AA International Local Metering
NTX472AA International–Local Basic (upgraded by NTX472AB)
or
NTX472AB International–Local Basic (upgrades NTX472AA)

Feature Description Manual Volume 2 of 3 BCS44.1i NTXH95AA–1

NTXH95AA
AE0838
Feature name
Metering Enhancements
Description
AE0838 implements changes to the metering system to ensure that all
datafill changes made to a line (assigning, deleting, or changing the line,
directory number (DN), or assignable features) are recorded. The changes
include the creation of four new data tables into which the contents of the
four meter blocks for each line are copied. The operating company can view
the contents of the tables or copy them into a file.
BCS history
This feature was created in BCS35.
Restrictions and limitations
This feature applies to NT40 switches only.
Only the following Hunt Group types are supported: Multi Line, Distributed
Line, and Directory Number.
Feature interactions
This feature uses the following feature:
• AC0051 International Metering Enhancements
User interface
This feature creates the command QMTRTBL at the MTRSYS level of the
MAP (maintenance and administration) display. The QMTRTBL command
allows the administration to view the contents of the new metering tables or
copy them to a file.
Automatic message accounting
When calculating initial billing for a new subscriber who has been assigned
an old DN, the counts for the old DN must be subtracted from the total
counts to get the correct meter count for the new subscriber. This is
necessary because meter counts for a line are not brought to zero when the
line is deleted.

NTXH95AA–2 297-1001-801i Standard 09.01 January 2000

 NTXK12AA
Irish R2 Signaling Protocol
This feature package applies to DMS-100 offices.
NTXK12AA implements R2 register signaling for Ireland. The Irish R2
protocol is supported in both the Centrex and the international environments,
in a coexistence switch configuration. Toll capabilities for Irish R2 trunks
are supported on the international portion of the DMS only.
Feature package contents
Feature package NTXK12AA contents
Feature number Description

AE0630 Irish R2 Signaling Protocol

BCS history
This feature package was created in BCS29.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX470AA International–Common Basic
NTX904AA R2 Signaling Base

Feature Description Manual Volume 2 of 3 BCS44.1i NTXK12AA–1

NTXK12AA
AE0630
Feature name
Irish R2 Signaling Protocol
Description
AE0630 implements R2 register signaling for Ireland. The Irish R2 protocol
is supported in both the Centrex and the international environments, in a
coexistence switch configuration. Toll capabilities for Irish R2 trunks are
supported on the international portion of the DMS system only.
BCS history
This feature was created in BCS29.
Hardware requirements
Each unit of the international digital trunk controller (IDTC) requires the
following cards:
• one NT6X69LA (CPP message protocol and downloadable tones CP)
• two NT6X92CA (International UTR tone detection)

Restrictions and limitations

Two-way Irish R2 trunks are not supported.
If one subgroup of a trunk group references NTRS11 signaling (through
datafill in table RGSIGSYS), then the other subgroup of the trunk must also
reference NTRS11 signaling.
Meter pulses are recognized on Irish R2 trunks if they are detected, but they
have no effect on the metering or billing system.
Irish R2 trunks interface only with trunks using R1 signaling.
All calls from the DMS switch to the Irish public switched telephone
network (PSTN) are routed over R1 looparound trunks.
The interworking of Irish R2 trunks with R1 looparound trunks are subject
to all limitations imposed by the coexistence switch configuration.
Feature interactions
This feature requires the following features:
• AE1218 FLS Monitoring Tool
• AG1217 R2 Call Processing
• AG1220 R2 Activity Tables

NTXK12AA–2 297-1001-801i Standard 09.01 January 2000

 NTXK12AA
AE0630
Datafill
Table Description

ACTCTL, New activities for Irish R2 register signaling are added to the
ACTSIG, ACTIVITY field.
ACTTRTMT,
SIGACT, and
TRTMTACT

R2PROT NTR204 is added to the range of values in field BASEPROT.

Automatic message accounting

Calls from the Centrex to the PSTN environment are subject to Centrex call
detail recording. Toll calls involving R2 trunks are subject to normal
international billing.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXK12AA–3

 NTXK13AA
Irish Downloadable Tones
This feature package applies to DMS-100 offices.
NTXK13AA provides the XMS-based peripheral module (XPM) and central
control (CC) software required to provide downloadable tones for Ireland.
The parameters that define the tones for each market are stored in optional
software modules, and are downloaded to the XPM as part of the PM’s static
data.
Feature package contents
Feature package NTXK13AA contents
Feature number Description

AE0397 Downloadable Tones

AE0671 Downloadable Tones for Ireland

BCS history
This feature package was created in BCS27.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX270AA New Peripheral Maintenance Package

Feature Description Manual Volume 2 of 3 BCS44.1i NTXK13AA–1

NTXK13AA
AE0397
Feature name
Downloadable Tones
Description
AE0397 provides the capability for XMS-based peripheral modules (XPM)
to support service tones for different markets using common hardware. The
parameters that define the tones for each market are stored in optional
software modules, and are downloaded to the XPM as part of the PM’s static
data.
This feature uses a universal version (NT6X69LA) of the message protocol
and tones circuit pack.
BCS history
This feature was created in BCS27.
Hardware requirements
This feature requires the following hardware:
• NT6X69LA (CPP message protocol and downloadable tones CP)
• NT6X02P2 (shelf product engineering code (PEC) for 2-processor
XPMs)
• NT6X02P3 (shelf PEC for three-processor XPMs equipped with the
NT6X69LA card)
Restrictions and limitations
This feature provides the RAM tone set for the MCL market only.
Datafill
Table Description

LTCINV RAM6X69 is added to the range of values in field OPTCARD.

This value must be datafilled if the value in field EQPEC is
6X02P2 or 6X02P3.

Field TONE_SET is added to indicate which tone set is required

in the XPM.

6X02P2 and 6X02P3 are added to the range of values in field

EQPEC.

Logs
This feature adds information to existing log PM181 indicating whether or
not tone generation was successful.

NTXK13AA–2 297-1001-801i Standard 09.01 January 2000

 NTXK13AA
AE0397
User interface
This feature adds the word Maketone to the XPM level of the MAP
(maintenance and administration position) display. Maketone is displayed in
response to the RTS command if tone samples are being generated.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXK13AA–3

NTXK13AA
AE0671
Feature name
Downloadable Tones for Ireland
Description
AE0671 introduces the XMS-based peripheral module (XPM) and central
control (CC) software required to provide downloadable tones for Ireland.
The tones are provided in two groups: those required by the PCM30 line
group controller (PLGC), and those required by the international digital
trunk controller (IDTC) and the PCM30 digital trunk controller (DTC).
BCS history
This feature was created in BCS29.
Hardware requirements
This feature requires the following card:
• NT6X69LA (CPP message protocol and downloadable tones card CP)

Feature interactions
This features requires the following features:
• AE0200 Tones Optionality
• AE0397 Downloadable Tones
• AE0398 Static Audit on Downloadable Tones
• AE0554 Downloadable Tone Enhancement
Datafill
Table Description

LTCINV EIRELGC and EIREDTC are added to the TONESET field.

NTXK13AA–4 297-1001-801i Standard 09.01 January 2000

 NTXK70AA
Peru Signaling
This feature package applies to DMS-100 offices.
NTXK70AA implements the R2 signaling developments for Peru.
Feature package contents
Feature package NTXK70AA contents
Feature number Description

AJ1872 Peru R2 Signaling

BCS history
This feature package was created in BCS34.
Required feature packages
Required feature packages
Feature package Description
number

NTX001AA Common Basic

NTX904AA R2 Signaling Base

Feature Description Manual Volume 2 of 3 BCS44.1i NTXK70AA–1

NTXK70AA
AJ1872
Feature name
Peru R2 Signaling
Description
AJ1872 implements the R2 signaling developments required for Peru.
BCS history
This feature was created in BCS34.
Restrictions and limitations
A maximum of 15 protocols are supported in one switch.
In order to request automatic number identification (ANI) spill, digit
analysis must be used. The incoming trunk must also have reported enough
digits to complete the transaction.
Unless the ANI spill was requested earlier, or the office parameter
R2_ANI_DENY is set to Yes, a request for ANI spill is propagated back to
the previous exchange in link-by-link mode regardless of the traffic class of
the tandem exchange’s incoming trunk. This is necessary to support
network-wide Malicious Call Trace (MCT).
Unless the office parameter R2_ANI_DENY is set to Yes, ANI spill is
provided in response to a request from a succeeding exchange regardless of
the traffic class of the outgoing trunk. This is necessary to support
network-wide Malicious Call Trace (MCT).
All interfaces to the Peru network are PCM30 trunks using 2-bit signaling.
On an incoming CAMA call, the DMS switch requests ANI after sending
signal A-5, REQ_DN_CAT. After ANI is collected, the switch requests the
NEXT_DIGIT signal.
The RING_BACK signal is not generated by the DMS switch and is ignored
if received.
Signal II-2, Calling Party Restricted from Direct Distant Dial (DDD) and
Operator-assisted Direct Distant Dial (ODD), is handled as signal II-2,
REGULAR. In a tandem situation, signal II-2 is propagated as II-1,
REGULAR.
Signal II-6, Ordinary Subscriber for coin phone Restricted from Direct
Distant Dial (DDD) and Operator-assisted Direct Distant Dial (ODD), is
handled as signal II-6, COIN. In a tandem situation, signal II-6 is
propagated as II-4, COIN.

NTXK70AA–2 297-1001-801i Standard 09.01 January 2000

 NTXK70AA
AJ1872
Signal II-7, Immediate Charging, is handled as signal II-7, REGULAR. In a
tandem situation, signal II-6 is propagated as II-4, REGULAR.
Signal B-2, Changed Number, is handled as signal B-2, UNASSIGN_NUM.
In a tandem situation, signal B-2 is propagated as B-5, UNASSIGN_NUM.
Signal B-1, Release Control A + B, is handled as signal B-1,
CONGESTION. In a tandem situation, signal B-1 is propagated as B-4,
CONGESTION.
The following signals are not supported and cause the call to fail if they are
received:
• I-13 Test Equipment
• II-8 No Category Service Hall
• II-9 Trunk Category Service Hall
• 11-11 Operator with Break-in

Feature interactions
The following features interact with R2 signaling and behave in a different
manner in the R2 environment:
• Automatic TBI
• Call Control
• Call Diversion (CDIV)
• Call Waiting (CWT)
• Coin Line
• Free Number Termination (FNT)
• Malicious Call Trace (MCT)
• Manual TBI
• No Double Connect (NDC)
• Toll Break-in (TBI)

Datafill
Table Description

OFCENG PERU is added to the range of values in field

MARKET_OF_OFFICE.

TRKGRP PERU1R2 is added to the range of values in field PROTIDX.

PERUTRT is added to the range of values in field TRTMTIDX.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXK70AA–3

 NTXK71AA
Haiti Signaling
This feature package applies to DMS-100 offices.
NTXK71AA implements the R2 register signaling developments for Haiti.
Feature package contents
Feature package NTXK71AA contents
Feature number Description

AE0972 Haiti R2 Register Signaling

BCS history
This feature package was created in BCS35.
Required feature packages
Required feature packages
Feature package Description
number

NTX904AA R2 Signaling Base

Feature Description Manual Volume 2 of 3 BCS44.1i NTXK71AA–1

NTXK71AA
AE0972
Feature name
Haiti R2 Register Signaling
Description
AE0972 implements the R2 register signaling developments required for
Haiti.
BCS history
This feature was created in BCS35.
Restrictions and limitations
A maximum of 15 protocols are supported in one switch.
In order to request automatic number identification (ANI) spill, digit
analysis must be used. The incoming trunk must also have reported enough
digits to complete the transaction.
Unless the ANI spill was requested earlier, or the office parameter
R2_ANI_DENY is set to Yes, a request for ANI spill is propagated back to
the previous exchange in link-by-link mode regardless of the traffic class of
the tandem exchange’s incoming trunk. This is necessary to support
network-wide Malicious Call Trace (MCT).
Unless the office parameter R2_ANI_DENY is set to Yes, ANI spill is
provided in response to a request from a succeeding exchange regardless of
the traffic class of the outgoing trunk. This is necessary to support
network-wide MCT.
On an incoming CAMA call, the DMS switch requests ANI after sending
signal A-5, REQ_DN_CAT. After ANI is collected, the switch requests the
NEXT_DIGIT signal.
The DMS switch supports Inter-digit Timeout to indicate the end of the
directory number (DN) dialed. It does not generate the END_OF_DIGITS
signal, but will accept it as an indication of the end of called digits.
The DMS switch does not generate PRIORITY signals I-11, I-12, and I-14
and will ignore them if they are received.
REGULAR signals II-7, II-8, and II-9 are not generated by the DMS switch.
If received, they are treated as signal II-1, REGULAR.
The DMS switch generates and accepts signal B-1, LAST_PTY_REL, for
MCT calls only.

NTXK71AA–2 297-1001-801i Standard 09.01 January 2000

 NTXK71AA
AE0972
Signal B-7, CONNECT_CALL_NOCHG, is not generated by the DMS
switch. If this signal is received in an originating exchange, the call is
marked as a free call; in a tandem exchange, signal B-6,
CONNECT_CALL_CHG is sent to the preceding exchange; in a terminating
exchange, signal B-6 is sent to the preceding exchange if the called
subscriber is free and the line option is set to FNT (Free Number
Termination).
Signal B-9 is not generated, and is treated as signal B-2, SUB_XFRD, if
received.
The following tones are not supported:
• special information
• coin phones identification
• Telefan

Feature interactions
The following features interact with R2 signaling and behave in a different
manner in the R2 environment:
• Automatic TBI
• Call Control
• Call Diversion (CDIV)
• Call Waiting (CWT)
• Coin Line
• Free Number Termination (FNT)
• Malicious Call Trace (MCT)
• Manual TBI
• No Double Connect (NDC)
• Toll Break-in (TBI)

Datafill
Table Description

OFCENG HAITI is added to the range of values in field

MARKET_OF_OFFICE.

R2CLGSRV OPER_INTL is added to the range of values in field

R2_CLG_ACT.

TRKGRP HAITIR2 is added to the range of values in field PROTIDX.

HAITITRT is added to the range of values in field TRTMTIDX.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXK71AA–3

 NTXK72AA
A-Bit Pulse Line Signaling
This feature package applies to DMS-100 offices.
NTXK72AA implements the digital A-bit pulsed line signaling protocol,
NTLS24, to be used in trunk call processing in DMS-100 and DMS-200
offices. This package provides the generic signaling requirements and
interactions for originating and terminating trunk traffic.
Feature package contents
Feature package NTXK72AA contents
Feature number Description

AL2457 Digital A-Bit Pulse Line Signaling

TA0163 NTLS24 and NTLS15 Enhancements

BCS history
This feature package was created in BCS34.
BCS38i—TA0163 added
Required feature packages
Required feature packages
Feature package Description
number

NTX001AA Common Basic

NTX470AA International–Common Basic

Feature Description Manual Volume 2 of 3 BCS44.1i NTXK72AA–1

NTXK72AA
AL2457
Feature name
Digital A-bit Pulsed Line Signaling
Description
AL2457 implements the digital A-bit pulsed line signaling protocol,
NTLS24, to be used in trunk call processing in DMS-100 and DMS-200
offices. This feature provides the generic signaling requirements and
interactions for originating and terminating trunk traffic.
The NTLS24 line signaling system uses only one signaling bit, the A-bit, of
the possible four bits in the signaling channel of the carrier.
BCS history
This feature was created in BCS35.
Restrictions and limitations
For a pulse to be defined, its send time and receive maximum recognition
time must be greater than zero.
The NTLS24 line signaling system supports only one-way trunk circuits.
The DMS switch does not generate the Force Release signal.
Signals SZG, ANS, CLF, CLB, and RLG cannot be datafilled as a NIL
pulse.
The RMINBLO value must be greater than the maximum recognition time
for the longest pulse defined.
The SMINBLO value must be greater than the maximum send time for the
longest pulse defined.
The SHORT pulse duration values must be lower than the LONG pulse
duration values for both the sending and receiving minimum and maximum
times.
The LONG pulse duration values must be lower than the EXTENDED pulse
duration values for both the sending and receiving minimum and maximum
times.
Recognition times for SHORT, LONG, and EXTENDED pulses cannot
overlap.
A pulse must be defined to be used as a signal.
The SHORT pulse duration must be defined.

NTXK72AA–2 297-1001-801i Standard 09.01 January 2000

 NTXK72AA
AL2457
To use a LONG pulse as a signal, the SHORT pulse must be defined and
used as a signal.
To use an EXTENDED pulse as a signal, the SHORT and LONG pulses
must be defined and used as signals.
If the REPCLFTM value is greater than zero, it must be greater than ten
seconds, or the sum of the duration of the Release Guard and Clear Forward
signals, whichever is greater.
If a Release Guard timeout occurs, only one attempt is made to clear the
trunk by resending the Seize and Clear Forward signals.
Field DIALSTRT in table TRKSGRP must be set to IMMEDIATE if SZA
and PTS are datafllled as NIL pulse types.
Field DIALSTRT in table TRKSGRP must be set to IMMEDIATE or WINK
if SZA is datafllled as a NIL pulse type and PTS is datafilled as a valid
non-zero pulse type.
Field DIALSTRT in table TRKSGRP must be set to IMMEDIATE,
DELDIAL, or WINK if SZA and PTS are datafllled are datafilled as valid
non-zero pulse types.
The PTS signal must be datafilled if the SZA signal is to be used.
If the FOT signal is defined, it must be datafilled as a shorter pulse than
CLF, CLB, and RLG.
Feature interactions
This feature requires the following feature:
• BV1211 CC Line Signaling Support
No meter pulse is generated before the Answer signal is received or after the
the call is taken down. Care must be taken to ensure that the line signaling
pulses are not misinterpreted as meter pulses, or the meter pulses as line
signaling pulses.
Datafill
Table Description

LNSIGSYS NTLS24 is added to define the NTLS24 line signaling system.

TRKSGRP This table is changed to ensure that the DIALSTRT field is set
to DELDIAL, IMMEDIATE, or WINK, depending on the signals
datafilled for the NTLS24 line signaling system.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXK72AA–3

NTXK72AA
TA0163
Feature name
NTLS24 and NTLS15 Enhancements
Description
This feature enhances:
• the existing one-way NTLS24 Digital A-bit Pulsed Line Signaling and
one-way NTLS15 A-bit Continuous Line Signaling protocols, by
introducing A-bit and B-bit line signaling optionality
• The release guard signal of NTLS15 to support CCITT recommendation
Q.412
BCS history
This feature was created in BCS38i.
Restrictions and limitations
One-way NTLS24 and NTLS15signaling do not support fault (FLT) signal

This feature supports only the wink signal type of Ring Forward and
Ringback.

Ring Forward is not supported to a local switch.

COIN signaling is not supported.

Datafill
Table Description

LNSIGSYS SIGBIT is added to the NTLS24 tuple for A-bit andB-bit line
signaling options.

BIDLPOL and SIGBIT are added to the NTLS15 tuple for A-bit
and B-bit line signaling options.

CIDLPOL and DIDLPOL are added to the NTLS15 tuple to

make the idle polarities of the C-bit and D-bit flexible.

RLGPOL is added to the incoming and outgoing refinements

and RMAXRLG is added to the outgoing refinement of the
NTLS15 tuple to modify the RLG signal.

SMINRLG parameter of the outgoing refinement of the NTLS15

tuple is renamed as SRLGTM to modify the RLG signal.

NTXK72AA–4 297-1001-801i Standard 09.01 January 2000

 NTXK73AA
DMS-100I Terminator Billing
This feature package applies to DMS-100 offices.
NTXK73AA provides the capability to produce an international centralized
automatic message accounting (ICAMA) call record for 800-service calls in
terminating DMS-100 international exchanges.
Feature package contents
Feature package NTXK73AA contents
Feature number Description

AJ1791 DMS-100I Terminator Billing

BCS history
This feature package was created in BCS34.
Required feature packages
Required feature packages
Feature package Description
number

NTX657AA International CAMA

Feature Description Manual Volume 2 of 3 BCS44.1i NTXK73AA–1

NTXK73AA
AJ1791
Feature name
DMS-100I Terminator Billing
Description
AJ1791 provides the capability to produce an international centralized
automatic message accounting (ICAMA) call record for 800-service calls in
terminating DMS-100 international exchanges.
The ICAMA record can display either the called directory number (DN) as it
was dialed, or the public switching telephone network (PSTN) number after
DN translation.
BCS history
This feature was created in BCS34.
Restrictions and limitations
To generate a record for terminator-billed intra-office calls, a looparound
trunk is required.
The CAMA selector allows the DN format for the record to be specified.
Only automatic number identification (ANI) and metering (MTR) trunk
groups support the CAMA selector.
During translation, the CAMA selector must be encountered before any
other digit-modification data. If it is not, and CAMA is used with the
CURRENT indicator, the called number may not be in the correct format for
the downstream billing record processor.
If no extension blocks are available, the call is set up but no ICAMA record
is generated.

NTXK73AA–2 297-1001-801i Standard 09.01 January 2000

 NTXK73AA
AJ1791
Datafill
Table Description

ACCODE, CAMA is added to the range of values for the selectors

ACHEAD, CONT, DNRTE, and RTE. Possible values for CAMA are
AMCODE,
AMHEAD,
POSTXLA and CURRENT.
CTCODE,
CTHEAD,
FACODE,
FAHEAD,
FTCODE,
FTHEAD,
NSCCODE,
NSCHEAD,
OFCCODE,
OFCHEAD,
PXCODE, and
PXHEAD

Operational measurements
This feature increments the following registers in existing operational
measurement (OM) group EXT: EXTOVFL, EXTSEIZ, and EXTUSAGE.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXK73AA–3

 NTXK79AA
PCM Unified Processor (UP) Support
This feature package provides the extended peripheral module (XPM)
software changes required to support the unified processor.
This feature package applies to DMS-100UK offices.
Feature package contents
Feature package NTXK79AA contents
Feature number Description

AE1007 Unified Processor Integration in the PDTC

AJ1898 UP on LGCO/DTCO/RCCO—CC Portion
AJ1899 UP on LGCO/DTCO/RCCO—XPM Portion
TA0174 UP Integration in the SDTC

BCS history
This feature package was created in BCS35.
BCS38i—TA0174 added
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX270AA New Peripheral Maintenance Package
NTXR34AA XPM Plus (Product Life Upgrade Strategy) Basic

Feature Description Manual Volume 2 of 3 BCS44.1i NTXK79AA–1

NTXK79AA
AE1007
Feature name
Unified Processor Integration in the PDTC
Description
AE1007 provides the extended peripheral module (XPM) software changes
required to support the NTMX77 (unified processor (UP)) on the
three-processor international PCM30 digital trunk controller (PDTC).
BCS history
This feature was created in BCS35.
Hardware requirements
This feature requires the NTMX77 (UP) on the PDTC.
Restrictions and limitations
This feature does not support an enhanced network (ENET).
This feature does not support the NTCX50 paddleboard (echo canceller
controller).
Feature interactions
This feature requires the following features:
• AJ1898 UP on LGCO/DTCO/RCCO—CC Portion
• AJ1899 UP on LGCO/DTCO/RCCO—XPM Portion
• AF3732 XPM Software Modifications for UP in Base XPM
• AF3733 CC Software Modifications for UP in Base XPM

NTXK79AA–2 297-1001-801i Standard 09.01 January 2000

NTXK79AA NTXK79AA
AJ1898
Feature name
UP on LGCO/DTCO/RCCO—CC Portion
Description
AJ1898 provides the central control (CC) changes required to support the
NTMX77 (unified processor (UP)) on the line group controller offshore
(LGCO), the digital trunk controller offshore (DTCO), and the remote
cluster controller offshore (RCCO).
BCS history
This feature was created in BCS35.
Feature interactions
This feature requires the following features:
• AE1007 Unified Processor Integration in the PDTC
• AF3232 XPM Software Modifications for UP in Base XPM
• AF3233 CC Software Modifications for UP in Base XPM
• AJ1899 UP on LGCO/DTCO/RCCO—XPM Portion
• AL2540 Unified Processor Integration in ISDN LTC
• AJ1033 PCM30 Peripherals for ISDN and CCS7—XPM Portion
• AJ1062 PCM30 Peripherals for ISDN and CCS7—CC Portion
Datafill
Table Description

RCCINV 6X12GA is added to the range of values for field EQPEC.

LTCINV 6X02UC is added to the range of values for field EQPEC.

This feature increases data store by a maximum of 5 kbytes and increases

program store by a maximum of 5 kbytes.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXK79AA–3

NTXK79AA
AJ1899
Feature name
UP on LGCO/DTCO/RCCO—XPM Portion
Description
AJ1899 provides the extended peripheral module (XPM) changes required
to support the NTMX77 (unified processor (UP)) on the line group
controller offshore (LGCO), the digital trunk controller offshore (DTCO),
and the remote cluster controller offshore (RCCO).
BCS history
This feature was created in BCS35.
Hardware requirements
This feature requires the NTMX77 (UP) on the PCM30 digital trunk
controller (PDTC).

NTXK79AA–4 297-1001-801i Standard 09.01 January 2000

NTXK79AA NTXK79AA
TA0174 TA0174
Feature name
UP Integration in the SDTC
Description
This feature provides a unified processor (UP) load to support the CIS
signaling as the existing three-processor SDTC load. SDTC is an
international digital trunk controller (IDTC) load for the CIS network.
SDTC supports T1 (NTLS21), and T2 (NTLS22) line signaling, as well as
decadic (NTRS05), MF Shuttle (NTRS02), MFPP–1 (NTRS14), and
MFPP–2 register signaling types.

Also, this feature provides a new IDTC+ load named ESDxxnn, specifically
to be used in the CIS network. SDTC+ covers all of the existing SDTC
functionalities.

SDTC+ on two- and three-processor backplane configurations are both

supported.
BCS history
This feature was created in BCS38i.
Hardware requirements
This feature supports only the shelf code NT6X02UI and the frame codes
NT6X01BA, NTRX47AA (streamline), NTFX33AA (MSL), and
NTNX33FA (MSL) for IDTC+ and ILGC+.
ILGC and IDTC must be equipped with the XPM+ card kit that contains the
following cards:
• NTMX77 UP (one card)
• NTMX71 Backplane Terminator Paddleboard (one card)
• NT7X80 Bus Shorter (two cards)
Feature interactions
This feature requires the following features:
• TA0133 Unified Processor on IDTC/ILGC–CC portion
• TA0134 Unified Processor on IDTC/ILGC–XPM portion

Feature Description Manual Volume 2 of 3 BCS44.1i NTXK79AA–5

NTXK79AA
TA0174
Datafill
Table Description

PMLOADS Both the RAM loads (EIDnnxx and EILnnxx) and the firmware
load must be datafilled.

LTCINV IXPM+ peripheral module must be datafilled as follows:

· EQPEC field as 6X02UI for 3-Processor Backplane IXPM+
or 6X02UC for 2-Processor Backplane IXPM+
· PECS6X45 field as MX77AA MX77AA
· E2LOAD field as MX77NB03

For an IXPM to be designated as an IXPM+, tables PMLOADS and

LTCINV must be appropriately datafilled.

NTXK79AA–6 297-1001-801i Standard 09.01 January 2000

 NTXK79AD
PCM30 Unified Processor Support
This feature package applies to DMS-100 offices.
NTXK79AD provides software modifications to the central control (CC) to
allow incorporation of the Unified Processor (UP) on the international
digital trunk controller (IDTC) and the international line group controller
(ILGC).
Feature package contents
Feature package NTXK79AD contents
Feature number Description

TA0133 Unified Processor on IDTC/ILGC – CC Portion

TA0134 Unified Processor on IDTC/ILGC – XPM Portion
TA0195 IXPM+ on 2-processor Backplane
TA0196 IXPM+ Robustness Enhancements

BCS history
This feature package was created in BCS37.
BCS38i—TA0195 and TA0196 added
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX270AA New Peripheral Maintenance Package
NTXR34AB XPM Plus (Product Line Upgrade Strategy) Basic
NTXR42AA Firmware Downloading

Feature Description Manual Volume 2 of 3 BCS44.1i NTXK79AD–1

NTXK79AD
TA0133
Feature name
Unified Processor on IDTC/ILGC – CC Portion
Description
This feature provides software modifications to the central control (CC) to
allow incorporation of the Unified Processor (UP) on the international
digital trunk controller (IDTC) and the international line group controller
(ILGC).
BCS history
This feature was created in BCS37.
Hardware requirements
This feature requires the provision of an NTMX77 card (unified processor).
Restrictions and limitations
This feature does not support the IDTC+ or ILGC+ two-processor backplane
configurations.
This feature supports only the NT6X69 messaging card. It does not support
the NT6X43 messaging card.
Feature interactions
This feature requires the following features:
• AE1007 Unified Processor Integration in the PDTC
• AF3733 CC Software Modifications for UP in Base XPM
• TA0134 Unified Processor on IDTC/ILGC –XPM Portion
Datafill
Table Description

LTCINV NTMX77 is added as a valid code for PCM30 XPMs in

processor field PECS6X45 for IDTC/ILGC.

NTXK79AD–2 297-1001-801i Standard 09.01 January 2000

 NTXK79AD
TA0134
Feature name
Unified Processor on IDTC/ILGC – XPM Portion
Description
This feature provides software modifications to the central control (CC) to
allow incorporation of the Unified Processor (UP) on the international
digital trunk controller (IDTC) and the international line group controller
(ILGC).
BCS history
This feature was created in BCS37.
Hardware requirements
This feature requires the provision of an NTMX77 card (unified processor).
Restrictions and limitations
This feature does not support the IDTC+ or ILGC+ two-processor backplane
configurations.
This feature supports only the NT6X69 messaging card. It does not support
the NT6X43 messaging card.
Feature interactions
This feature requires the following features:
• AE1007 Unified Processor Integration in the PDTC
• AF3733 CC Software Modifications for UP in Base XPM
• TA0133 Unified Processor on IDTC/ILGC – CC Portion

Feature Description Manual Volume 2 of 3 BCS44.1i NTXK79AD–3

NTXK79AD
TA0195
Feature name
IXPM+ on 2-processor Backplane
Description
This feature provides the software changes to support the unified processor
(UP) on the international digital trunk controller (IDTC+) and on the
international line group controller (ILGC+) with the two-processor
backplane. This feature uses the load created for the three-processor
backplane international XMS-based peripheral module (IXPM+), that is,
EIL and EID for the ILGC and IDTC, respectively.
BCS history
This feature was created in BCS38i.
Hardware requirements
This feature supports only shelf code 6X02UC and frame code NT6X01AC
for IDTC+/ILGC+ on the two-processor backplane.
Restrictions and limitations
This feature supports only the 6X69 messaging card.

This feature uses only the loads EIDxxnn for IDTC+ and EILxxnn for
ILGC+ that will run on the UP (NTMX77).
Feature interactions
For more detail about IXPM+, refer to the following features:
• TA0163 NTLS24 and NTLS15 Enhancements
• TA0134 Unified Processor on IDTC/ILGC–XPM Portion
This feature does not affect any of the current XPM and IXPM functionality.
This activity requires the following features:
• TA0133 Unified Processor on IDTC/ILGC–CC Portion
• TA0134 Unified Processor on IDTC/ILGC–XPM Portion
Datafill
Table Description

LTCINV Value 6X02UC is added to field EQPEC. Values MX77nn are

added to field PECS6X45.

NTXK79AD–4 297-1001-801i Standard 09.01 January 2000

NTXK79AD NTXK79AD
TA0196 TA0196
Feature name
IXPM+ Robustness Enhancements
Description
The international digital trunk controller (IDTC)+ and international line
group controller (ILGC)+ are the peripheral modules (PM) equipped with
NTMX77 card. This feature provides the software modifications in order to
support the robustness improvements for these PMs.
BCS history
This feature was created in BCS38i.
Hardware requirements
This feature only runs on the IXPM+.
Restrictions and limitations
This feature only uses the loads EIDxxnn for IDTC+ and EILxxnn for
ILGC+. These run on the unified processor (UP).
Feature interactions
This feature does not affect any of the current XPM and IXPM functionality.

This activity requires the following features:

• TA0133 Unified Processor on IDTC/ILGC–CC portion
• TA0194 Maint Enhance for NTC7 MTP

Feature Description Manual Volume 2 of 3 BCS44.1i NTXK79AD–5

 NTXN83AA
LIS Common—LMS Functionality on MS
This feature package provides the frame transport bus (F-bus) user interface
support for the Mininode. It also provides generic F-bus maintenance
support for a variable number of link interface unit (LIU) shelves.
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTXN83AA contents
Feature number Description

AL1453 DMS-bus Support for the F-Bus MAP Level

AL1458 DMS-bus Support of 0, 1, and 2 LIU SHE
AR0478 F-bus Operation and Maintenance Enhancements

BCS history
This feature package was created in BCS33.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX940AA CM Bilge
NTX941AA CM Common
NTX945AA MS Base Link Maintenance
NTX950AA MS Bilge
NTX951AA MS Common
NTXF71AB SuperNode Enhanced Messaging (upgrade of NTXF71AA)
NTXN18AA F-bus—LIU Base

Feature Description Manual Volume 2 of 3 BCS44.1i NTXN83AA–1

NTXN83AA
AL1453
Feature name
DMS-Bus Support for the F-Bus MAP Level
Description
AL1453 provides the frame transport bus (F-bus) man-machine interface
(MMI) support for the Mininode project. The existing card level under the
message switch (MS) MAP level is enhanced to facilitate the maintenance of
the transaction bus (T-bus) to F-bus interface (TFI) cards and other F-bus
resources.
BCS history
This feature was created in BCS34.
Feature interactions
This feature requires the following features:
• AL1454Basic Integration of F-bus Maintenance in DMS-Bus
• AL1455Basic Integration of Rate Adaptor Transactor in DMS-Bus
• AL1458—MiniNode Support of 0, 1, and 2 LIU Shelves

This feature interacts with the following features:

• AL1405—LIU Maintenance Support for Mininode
• AL1449—F-Bus Support for 2 Card LIU7
• AL1457—Basic Initialization and Communication of ILM Data

Datafill
This feature increases program store by a maximum of 50 Kbytes and
increases data store by a maximum of 100 Kbytes.
User interface
This feature adds MAP directory MSFBDIR at the MS maintenance level,
and introduces the following commands used specifically to provide
maintenance capabilities for the F-bus and the test access point (TAP):
OFFL, TST, RTS, and BSY.

NTXN83AA–2 297-1001-801i Standard 09.01 January 2000

 NTXN83AA
AR0478
Feature name
F-bus Operation and Maintenance Enhancements
Description
This feature streamlines the DMS-bus F-bus operations and interactions and
provides enhancements in the following areas:
• restart initialization
• no restart switch of activity (SWACT)
• log output
• combination of the rate adaptor F-bus and single-shelf link peripheral
processor (SSLPP) on the SuperNode SE (SNSE) DMS-bus
• simplified reconfiguration of the bandwidth of the supporting interface
card pair for the SSLPP
BCS history
This feature was created in BCS36.
Restrictions and limitations
The changes made in this feature apply only to DMS-bus and supported
application-specific units (ASU).
Feature interactions
The software provided by this feature structures the interactions between
F-bus and ASUs.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXN83AA–3

 NTXP10AA
Dual-shelf Network
This feature package provides support for removing DMS junctored network
(JNET) software from enhanced network (ENET) software loads.
This feature package applies to DMS-100 offices.
Feature package contents
Feature package NTXP10AA contents
Feature number Description

AL2055 NM S/W Optionality

BCS history
This feature package was created in BCS34.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
Either
NTXG21AA DMS-250 EIOC Base Package
or
NTX001AA Common Basic

Feature Description Manual Volume 2 of 3 BCS44.1i NTXP10AA–1

NTXP10AA
AL2055
Feature name
NM S/W Optionality
Description
AL2055 provides support for removing DMS junctored network (JNET)
software from enhanced network (ENET) software loads. Absence of the
JNET software allows ENET software to work more efficiently.
This feature removes the JNET software from package NTX001AA and
places it in a separate package, NTXP10AA.
BCS history
This feature was created in BCS34.
Datafill
This feature increases program store by a maximum of 5 Kbytes and
increases data store by a maximum of 1 Kbyte.

NTXP10AA–2 297-1001-801i Standard 09.01 January 2000

 NTXP44AA
DMS SuperNode SE Common
This feature package supports two computing module interface card (CMIC)
links on one DMS-bus card 4, with each link running in subrate 256 mode.
This feature package applies to DMS SuperNode SE offices.
Feature package contents
Feature package NTXP44AA contents
Feature number Description

AQ0857 SNSE DMS-bus S/W for Sub-Rate CMIC LIN

BCS history
This feature package was created in BCS34.
Required feature packages
Required feature packages
Feature package Description
number

NTX000AA Bilge
NTX001AA Common Basic
NTX950AA MS Bilge
NTX951AA MS Common

Feature Description Manual Volume 2 of 3 BCS44.1i NTXP44AA–1

NTXP44AA
AQ0857
Feature name
SNSE DMS-bus S/W for Subrate CMIC Links
Description
AQ0857 supports two computing module interface card (CMIC) links on
one DMS-bus card 4, with each link running in subrate 256 mode. This
DMS-bus card combination consists of the NT9X17AD circuit pack and the
NT9X62CA paddle board. This feature is developed for SuperNode SE.
BCS history
This feature was created in BCS34.
Feature interactions
This feature interacts with features AL1756 (DMS-bus Software Support for
SuperNode SE).
Datafill
This feature increases program store by a maximum of 1 Kbyte and
increases data store by a maximum of 2 Kbytes.

NTXP44AA–2 297-1001-801i Standard 09.01 January 2000

 NTXP72AA
Integrated Network Support on SN-1
This feature package provides the SuperNode SE (SNSE) enhanced network
(ENET) user interface at a MAP (maintenance and administration position)
terminal. It also provides SNSE ENET diagnostic software.
This feature package applies to DMS SuperNode offices.
Feature package contents
Feature package NTXP72AA contents
Feature number Description

AR0106 SNSE ENET MMI

AR0105 SNSE ENET XPT Diagnostics

BCS history
This feature package was created in BCS34.
Required feature packages
Required feature packages
Feature package Description
number

NTXE01AA Enhanced Network Basic

NTXF70AA SuperNode SN-20 Processor
NTXP44AA DMS SuperNode SE Common
NTXP71AA System Load Module A-1
NTX940AA CM Bilge
NTX941AA CM Common
NTX950AA MS Bilge
NTX951AA MS Common
Either
NTX942AA DMS SuperNode System Load Module (SLM)
or
NTX942AB DMS SuperNode System Load Module (SLM)

Feature Description Manual Volume 2 of 3 BCS44.1i NTXP72AA–1

NTXP72AA
AR0105
Feature name
SNSE ENET XPT Diagnostics
Description
AR0105 provides diagnostic software for testing the crosspoint (XPT) card
(NT9X35FA) for the SuperNode SE enhanced network (SNSE ENET).
This feature provides the following in-service tests:
• central message controller (CMC) parity test
• CMC write/read test
• internal data path test
• data memory test
• bus interface (BIF) clock monitor test
• horizontal bus (H-bus) test
• vertical bus (V-bus) test

This feature provides the following out-of-service tests:

• in-service test
• complete data memory test
• CMC parity error checker test
• CMC self test
• quad fiber link interface controller (QFLIC) self test
• DS-512 transmit/receive controller (DTRC) self test
• paddle board looparound test

BCS history
This feature was created in BCS34.
Restrictions and limitations
This feature is not optional for SNSE ENET.
Feature interactions
This feature interacts with the following features:
• AL0575 ENET Card MTCE System Structure Definition
• AL0583 ENET Connection Control
• AL0970 ENET Switching Matrix Transactor Network

NTXP72AA–2 297-1001-801i Standard 09.01 January 2000

 NTXP72AA
AR0106
Feature name
SNSE ENET MMI
Description
AR0106 provides the SuperNode SE (SNSE) enhanced network (ENET)
user interface at a MAP (maintenance and administration position) terminal.
The SNSE ENET is referred to as ENET16K, and is a compact,
low-capacity version of the existing ENET product. This feature also
provides ENET16K table control for the ENET node inventory table
(ENINV) and the ENET card inventory table (ENCDINV).
BCS history
This feature was created in BCS34.
Hardware requirements
This feature requires an ENET configured as an SNSE.
Restrictions and limitations
This feature is restricted to the ENET16K product.
Feature interactions
This feature does not affect existing ENET features.
This feature requires the following features:
• AQ0858 DMS-bus S/W Support for Subrate MS-ENET Links
• AL1230 ENET MAP Enhancements
• AL0470 ENET Database
Datafill
Table Description

ENINV PRI116K is added to the range of values for field ENCLASS to

specify network class for ENET16K.
SCC is added to the range of values for field FRTYPE to specify
SNSE frame type.
NT9X01MB is added to the range of values for field FRPEC to
specify ENET16K frame product engineering code (PEC).
NT9X0810 is added to the range of values for field SHPEC to
specify ENET16K shelf PEC.

—continued—

Feature Description Manual Volume 2 of 3 BCS44.1i NTXP72AA–3

NTXP72AA
AR0106

Table Description (continued)

Field MSLINK0 is added to datafill message switch interface

paddle board link number on MSCARD0, serving network
plane 0.
Field MSPORT0 is added to datafill message switch port
number on MSLINK0 dedicated to network plane 0.
Field MSLINK1 is added to datafill message switch interface
paddle board link number on MSCARD1, serving network
plane 1.
Field MSPORT1 is added to datafill message switch interface
port number on MSLINK1 dedicated to network plane 1.
ENCDINV NT9X35FA is added to the range of values for field CPPEC to
specify the ENET16K crosspoint (XPT) card.

End

This feature increases program store by a maximum of 10 Kbytes.

Logs
This feature modifies the output for the following ENET logs for ENET16K
applications:
ENET211, ENET220, ENET221, ENET222, and ENET230.
Log ENET211 no longer has references to the upper V-bus interface or to
H-bus interface 1.
Logs ENET220 and ENET221 have modified H-bus and V-bus ranges.
Logs ENET222 and ENET230 have modified report formats for ENET16K.

NTXP72AA–4 297-1001-801i Standard 09.01 January 2000

 NTXP72AA
AR0106
User interface
This feature provides a physical representation of the ENET16K hardware.
It modifies the ENET MAP terminal, at the following levels, to reflect the
changes in card positions and the smaller switching capacity of the
ENET16K product:
• ENET ENET level
• ENET SYSTEM level
• ENET SHELF level
• ENET CARD level
• ENET MATRIX level

The changes made to the ENET MAP terminal are reflected only in the
ENET16K MAP terminal and have no effect on the original ENET MAP
terminal.

Feature Description Manual Volume 2 of 3 BCS44.1i NTXP72AA–5

DMS-100 Family
DMS-100i
Feature Description Manual
Volume 2 of 3

Product Documentation–Dept. 3423

Nortel Networks
P.O. Box 13010
RTP, NC 27709–3010
Telephone: 1–877–662–5669
Electronic mail: cits@nortelnetworks.com
Copyright  1994–2000 Nortel Networks,
All Rights Reserved
NORTEL NETWORKS CONFIDENTIAL: The information
contained herein is the property of Nortel Networks and is
strictly confidential. Except as expressly authorized in writing
by Nortel Networks, the holder shall keep all information
contained herein confidential, shall disclose the information
only to its employees with a need to know, and shall protect the
information, in whole or in part, from disclosure and
dissemination to third parties with the same degree of care it
uses to protect its own confidential information, but with no less
than reasonable care. Except as expressly authorized in writing
by Nortel Networks, the holder is granted no rights to use the
information contained herein.
Information is subject to change without notice. Nortel
Networks reserves the right to make changes in design or
components as progress in engineering and manufacturing
may warrant.
Changes or modification to the DMS-100i without the express
consent of Nortel Networks may void its warranty and void the
users authority to operate the equipment.
This equipment has been tested and found to comply with the
limits for a Class A digital device, pursuant to Part 15 of the
FCC Rules. These limits are designed to provide reasonable
protection against harmful interference when the equipment is
operated in a commercial environment. This equipment
generates, uses, and can radiate radio frequency energy and, if
not installed and used in accordance with the instruction
manual, may cause harmful interference to radio
communications. Operation of this equipment in a residential
area is likely to cause harmful interference in which case the
user will be required to correct the interference at his own
expense.
NORTEL NETWORKS, the NORTEL NETWORKS LOGO, the
GLOBEMARK, HOW THE WORLD SHARES IDEAS,
UNIFIED NETWORKS, DMS, MAP, NORTEL, NORTHERN
TELECOM, NT, TOPS, and SUPERNODE are trademarks of
Nortel Networks.
Publication number: 297-1001-801i
Product release: BCS44.1i
Document release: Standard 09.01
Date: January 2000
Printed in the United States of America