Operation Manual-Traffic Measurement Volume PDF

Chapter 1 Traffic Measurement Overview .....................................................
1-1
1.1 Basic Concepts ...................................................................................... 1-1
1.2 Functional Features ................................................................................ 1-4
Chapter 2 Traffic Measurement Operations .................................................. 2-1
2.1 Introduction............................................................................................. 2-1
2.2 Creating a Traffic Statistics Task............................................................ 2-3
2.2.1 Selecting a Traffic Statistics Type .................................................. 2-4
2.2.2 Choosing a Measure Unit .............................................................. 2-4
2.2.3 Choosing a Measure Object .......................................................... 2-5
2.2.4 Selecting or Customizing an Entity ................................................ 2-6
2.2.5 Setting Other Parameters .............................................................. 2-9
2.3 Modifying a Traffic Statistics Task .......................................................... 2-13
2.4 Deleting a Traffic Statistics Task ............................................................ 2-14
2.5 Querying Traffic Statistics Tasks ............................................................ 2-14
2.6 Querying, Saving and Printing Traffic Statistics Results ........................ 2-15
Chapter 3 Measure Units and Entities ........................................................... 3-1
3.1 Measurement of Total Traffic of the Office ............................................. 3-2
3.1.1 Originating Traffic........................................................................... 3-2
3.1.2 Sort User Originating Traffic .......................................................... 3-3
3.1.3 Inner Traffic .................................................................................... 3-4
3.1.4 Originating Outgoing Office Traffic ................................................. 3-5
3.1.5 Incoming Office Traffic ................................................................... 3-7
3.1.6 Incoming Office Terminating Traffic ............................................... 3-8
3.1.7 Transfer Traffic ............................................................................... 3-10
3.1.8 Terminating Traffic ......................................................................... 3-11
3.1.9 Sort User Terminating Traffic ......................................................... 3-12
3.1.10 Outgoing Office Traffic ................................................................. 3-13
3.1.11 ISDN Intra-office Traffic ............................................................... 3-14
3.1.12 ISDN Originating Outgoing Office Traffic ..................................... 3-16
3.1.13 ISDN Incoming Office Terminating Traffic ................................... 3-17
3.1.14 ISDN Transfer Traffic ................................................................... 3-19
3.1.15 Connecting Type Traffic ............................................................... 3-20
3.1.16 ISDN Connecting Type Traffic ..................................................... 3-22
3.1.17 All Offices Sum Traffic ................................................................. 3-24
3.1.18 Failure Reason Traffic.................................................................. 3-26
3.2 Measurement of Bearer Traffic............................................................... 3-32
3.2.1 Office Direction Incoming Office Traffic ......................................... 3-32
3.2.2 Office Direction Outgoing Office Traffic ......................................... 3-33
3.2.3 TKGRP Incoming Office Traffic...................................................... 3-35
3.2.4 TKGRP Outgoing Office Traffic...................................................... 3-38
3.2.5 Destination Traffic .......................................................................... 3-40
3.2.6 Destination Distribution Traffic ....................................................... 3-42
3.2.7 Single User Traffic ......................................................................... 3-43
3.2.8 User Line GRP Traffic .................................................................... 3-43
3.2.9 PABXGRP Traffic........................................................................... 3-44
3.2.10 Centrex Intra-group Traffic ........................................................... 3-45
3.2.11 Centrex Extra-group Traffic .......................................................... 3-46
3.2.12 Centrex Outgoing Group Traffic ................................................... 3-46
3.2.13 Supplementary Service Traffic ..................................................... 3-47
3.2.14 Supplementary Service Centrex Traffic ....................................... 3-49
3.2.15 ISDN Bearer Traffic ...................................................................... 3-50
3.2.16 ISDN Terminal Service Traffic ..................................................... 3-51
3.2.17 ISDN Supplementary Service Traffic ........................................... 3-52
3.2.18 ISDN BRA Traffic ......................................................................... 3-53
3.2.19 ISDN PRA Traffic ......................................................................... 3-54
3.2.20 Bill Traffic ..................................................................................... 3-54
3.2.21 ACD group message traffic .......................................................... 3-55
3.2.22 ACD user message traffic ............................................................ 3-55
3.3 Measurement of Public Component ....................................................... 3-56
3.3.1 Unqueue Public Unit Traffic ........................................................... 3-56
3.3.2 Queue Public Unit Traffic ............................................................... 3-57
3.3.3 Console Traffic ............................................................................... 3-57
3.3.4 SPM Resource MFC Traffic ........................................................... 3-59
3.3.5 SPM Resource DTR Traffic ........................................................... 3-59
3.3.6 SPM Resource FSK Traffic ............................................................ 3-60
3.3.7 SPM Resource ECP Traffic ........................................................... 3-60
3.3.8 SPM Resource MFS Traffic ........................................................... 3-61
3.4 Measurement of Control Component ..................................................... 3-62
3.4.1 CPU Seizure Ratio Traffic .............................................................. 3-62
3.5 Measurement of Signaling & Interface ................................................... 3-62
3.5.1 ISDN PHI B Traffic ......................................................................... 3-62
3.5.2 ISDN PHI D Traffic ......................................................................... 3-63
3.5.3 ISDN UUS1 Traffic ......................................................................... 3-63
3.5.4 ISDN UUS3 Traffic ......................................................................... 3-64
3.5.5 ISDN Signaling COMM Traffic ....................................................... 3-64
3.5.6 MTP Signaling Link Traffic ............................................................. 3-65
3.5.7 MTP Linkset Traffic ........................................................................ 3-66
3.5.8 MTP DEST Signaling Point Traffic ................................................. 3-66
3.5.9 MTP SP Distribution Traffic............................................................ 3-67
3.5.10 TUP Total MSU Traffic ................................................................. 3-67
3.5.11 TUP MSG Using Traffic ............................................................... 3-68
3.5.12 TUP Abnormity Traffic.................................................................. 3-68
3.5.13 TUP Node Performance Traffic .................................................... 3-69
3.5.14 TUP NET Performance Traffic ..................................................... 3-70
3.5.15 TUP Circuit Group Performance Traffic ....................................... 3-70
3.5.16 ISUP Total MSU Traffic ................................................................ 3-72
3.5.17 ISUP MSG Using Traffic .............................................................. 3-72
3.5.18 ISUP Abnomity Traffic.................................................................. 3-72
3.5.19 ISUP Node Performance Traffic .................................................. 3-74
3.5.20 ISUP NET Performance Traffic .................................................... 3-74
3.5.21 ISUP Circuit Group Performance Traffic ...................................... 3-75
3.5.22 V5 Interface Traffic ....................................................................... 3-76
3.5.23 V5 2M Link Information Traffic ..................................................... 3-76
3.5.24 V5 Physical C Channel Traffic ..................................................... 3-77
3.5.25 V5 Logical C Channel Traffic ....................................................... 3-77
3.5.26 V5 B Channel Traffic .................................................................... 3-78
3.5.27 MTP Police Message Traffic ........................................................ 3-80
3.5.28 SCCP Police Message Traffic...................................................... 3-80
3.6 Measurement of Call Record.................................................................. 3-80
3.6.1 Dispersion Duration Traffic ............................................................ 3-80
3.6.2 Service Quality Traffic .................................................................... 3-81
3.6.3 Complete Ratio Traffic ................................................................... 3-82
3.6.4 Multi Condition Object Traffic ......................................................... 3-82
3.7 Inner Running Measurement .................................................................. 3-88
3.7.1 SM Flow Traffic .............................................................................. 3-88
3.7.2 Inter-module Distribution Traffic ..................................................... 3-89
3.7.3 RSA Interface Traffic ...................................................................... 3-89
3.8 Measurement of Maximum/Minimum Values & Charging ...................... 3-90
3.8.1 Top Usage User Traffic .................................................................. 3-90
3.8.2 Top Called Busy Traffic.................................................................. 3-91
3.8.3 Top Ringed No Answer Traffic ....................................................... 3-92
3.8.4 Top Call Loss Traffic ...................................................................... 3-93
3.8.5 Top Idle TK Circuit Traffic .............................................................. 3-94
3.9 Measurement of IN Service .................................................................... 3-95
3.9.1 IN Call Traffic Volume .................................................................... 3-95
3.9.2 IN Incoming Call QoS .................................................................... 3-96
3.9.3 IN Session Stat Traffic ................................................................... 3-96
3.9.4 IN Edp Account .............................................................................. 3-97
3.9.5 IN Faulted Reason ......................................................................... 3-98
3.9.6 IN Faulted Statistic ......................................................................... 3-99
3.9.7 SRF Global Resource Traffic ......................................................... 3-100
3.9.8 IN Operation Traffic........................................................................ 3-100
3.9.9 INSM Operation ............................................................................. 3-101
3.9.10 IN Sampling Trace ....................................................................... 3-102
3.9.11 SRF Record Informing ................................................................. 3-103
3.9.12 SRF Congestion........................................................................... 3-104
3.9.13 SRF Channel ............................................................................... 3-104
3.9.14 SRF Operation ............................................................................. 3-105
3.9.15 SRF Traffic Volume ...................................................................... 3-105
3.9.16 SRM Operation ............................................................................ 3-106
3.9.17 IN Subscriber Interaction Measure .............................................. 3-107
3.9.18 IN Outgoing Call QoS .................................................................. 3-107
3.10 Permanent task .................................................................................... 3-108
3.10.1 HTR Traffic Control ...................................................................... 3-108
Chapter 4 Traffic Measurement Application ................................................. 4-1
4.1 Querying Call Loss ................................................................................. 4-1
4.1.1 Analyzing Call Loss Reason by Means of "Failure Reason
Traffic" ..................................................................................................... 4-1
4.1.2 Locating Further Problem .............................................................. 4-1
4.1.3 Finding Further Cause by Means of "Call Record" ........................ 4-3
4.1.4 Finding Essential Call Loss Reason .............................................. 4-3
4.2 Distributing Busy Traffic ......................................................................... 4-4
4.3 Balancing Traffic ..................................................................................... 4-5
4.4 Searching Maximum/Minimum Value ..................................................... 4-6
4.4.1 Measurement of Top Usage User .................................................. 4-6
4.4.2 Measurement of Top Called Busy User ......................................... 4-6
4.4.3 Measurement of Top Ringed No Answer User .............................. 4-6
4.4.4 Measurement of Top Call Loss User ............................................. 4-7
4.4.5 Measurement of Top Idle TK Circuit .............................................. 4-8
4.4.6 Maximum/Minimum Value Measurement....................................... 4-8
4.5 Tracing Calls .......................................................................................... 4-9
4.6 Locating Factors Influencing Call Completing Rate ............................... 4-9
4.7 Other Applications .................................................................................. 4-11
Chapter 5 Solutions to Common Problems .................................................. 5-1
5.1 How to Select a Traffic Statistics Task ................................................... 5-1
5.2 How to Select a Measure Unit ................................................................ 5-2
5.3 How to Select a Measure Object ............................................................ 5-2
5.4 How to Determine an Output Entity ........................................................ 5-3
5.5 Solutions to Other Common Problems ................................................... 5-3
5.5.1 When to Output the Traffic Statistics Result .................................. 5-3
5.5.2 How to Understand Questions of Period-Crossing Traffic
Statistics .................................................................................................. 5-4
5.5.3 Statistics Methods of the Number of Seizures, Seizure Traffic
and Average Seizure Duration and Their Relations ................................ 5-5
5.5.4 When Traffic Measurement of ISDN Terminal Service Is
Effective .................................................................................................. 5-7
5.5.5 Some Special Instances of Traffic Statistics .................................. 5-7
5.5.6 Inaccurate Traffic Statistics Caused by Modification of Trunk
Group Data ............................................................................................. 5-8
5.5.7 Causes of Incomplete Traffic Statistics .......................................... 5-8
5.5.8 Use of the Service Quality Traffic Measurement ........................... 5-9
5.5.9 Precautions for Using Max/Min Value Traffic Statistics ................. 5-9
5.5.10 Why "Number of Answers + Number of Failures < Number of
Seizure Attempts ( Seizures)" ................................................................. 5-10
5.5.11 Why Some Entity Results are "Unknown" in Multi Condition
Object Traffic Statistics ........................................................................... 5-10
5.5.12 Measurement of Access Network Users ...................................... 5-11
5.5.13 Influence on Traffic Statistics during Version Upgrade ................ 5-12
Appendix A Operations in MML Command Line Mode ................................ A-1
A.1 Creating a Traffic Statistics Task ........................................................... A-1
A.2 Setting a Customized Entity ................................................................... A-3
A.3 Modifying Task Attributes ....................................................................... A-4
A.4 Deleting a Traffic Statistics Task............................................................ A-5
A.5 Querying Traffic Statistics Tasks ........................................................... A-5
Appendix B Report Format of Traffic Statistical ........................................... B-1
B.1 Date and Time Format of Traffic Statistical Report ................................ B-1
B.2 Descriptor Explanation ........................................................................... B-1
B.3 Description of Report Head .................................................................... B-2
B.4 Description of Report Body .................................................................... B-3
B.5 Description of Report Tail ...................................................................... B-4
B.6 Report Example ..................................................................................... B-4
Appendix C Acronyms and Abbreviations .................................................... C-1
HUAWEI
C&C08 Digital SPC Switching System

Operation Manual - Traffic Measurement Volume
OVSV610R103
Operation Manual
Volume Traffic Measurement Volume
Manual Version T2-011692-20041130-C-4.10
Product Version OVSV610R103
BOM 31160792
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support
and service. Please feel free to contact our local office, customer care center or company
headquarters.
Huawei Technologies Co., Ltd.
Address: Administration Building, Huawei Technologies Co., Ltd.,
Bantian, Longgang District, Shenzhen, P. R. China
Postal Code: 518129
Website: http://www.huawei.com
Email: support@huawei.com
Copyright © 2004 Huawei Technologies Co., Ltd.
All Rights Reserved
No part of this manual may be reproduced or transmitted in any form or by any

means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks
, HUAWEI, C&C08, EAST8000, HONET, , ViewPoint, INtess, ETS, DMC,

TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium, M900/M1800,
TELESIGHT, Quidview, Musa, Airbridge, Tellwin, Inmedia, VRP, DOPRA, iTELLIN,
HUAWEI OptiX, C&C08 iNET, NETENGINE, OptiX, SoftX, iSite, U-SYS, iMUSE,
OpenEye, Lansway, SmartAX are trademarks of Huawei Technologies Co., Ltd.
All other trademarks mentioned in this manual are the property of their respective
holders.
Notice
The information in this manual is subject to change without notice. Every effort has
been made in the preparation of this manual to ensure accuracy of the contents, but
all statements, information, and recommendations in this manual do not constitute
the warranty of any kind, express or implied.
About This Manual
Version
The product version that corresponds to the manual is the C&C08 Digital SPC
Switching System OVSV610R103 (SPC stands for Stored Program Control).
Related Manuals
The following manuals provide more information about the C&C08 Digital SPC
Switching System.
Manual Content
It consists of two volumes. The Troubleshooting Volume details on

how to locate and process common faults in the C&C08 Digital
SPC Switching System, while the Routine Maintenance Volume
Maintenance Manual
offers operational methods and maintenance suggestions for
routine maintenance and special maintenance.
It offers an overall introduction to the C&C08 Digital SPC Switching

System, including the system structure, hardware functions,
Technical Manual
software functions, services and applications.
C&C08 Digital SPC Switching System It is used for assisting the users in data configurations and typical
Operation Manual applications.
It provides information for the system installation, including the

installation of the cabinets, cables, power system and various
Installation Manual
boards.
It introduces almost all the boards available in the C&C08 Digital

C&C08 Digital SPC Switching System SPC Switching System. For each board, it describes its functions,
Board Manual features, interface signal, functional principle and technical
Indexes.
Organization of the Manual
The manual describes traffic measurement of C&C08 Digital SPC Switching System.
There are five chapters and two appendixes in the manual.
Chapter 1 Traffic Measurement Overview profiles the basic concept and function
features of traffic measurement.
Chapter 2 Traffic Measurement Operations elaborates on the operation mode, how
to create, modify, delete and query a traffic task, how to query, save and print traffic
statistics results.
Chapter 3 Measure Units and Entities mainly describes the names, objects & entities
of measure units, serial numbers & MML words of all entities. Eight traffic types are
introduced in this chapter, namely, office traffic, bearer traffic, public component traffic,
control component traffic, signaling & interface traffic, call record traffic, inner running
traffic, maximum/minimum values & charging traffic.
Chapter 4 Traffic Measurement Application focuses on how to achieve daily

services & some actual applications, and how to provide routine data for telecom
network scheming and management by traffic measurement. This chapter details how
to query call loss, distributing busy traffic, balancing traffic, searching
maximum/minimum value, tracing calls and locating factors influencing the call
completing rate by means of traffic measurement.
Chapter 5 Solutions to Common Problems gives a description of common problems

and their causes in the application of traffic measurement. It helps users understand
traffic measurement and improve the application level. This chapter details how to
select a traffic statistics task, a measurement unit, a measured object, how to
determine an output entity and other common problems.
Appendix A Operations in MML Command Line Mode covers how to create, delete
and query traffic statistics tasks, self-defined measure entity and modify task attributes.
Appendix B Report Format of Traffic Statistical describes the different parts of the
report of traffic statistical.
Appendix C Acronyms and Abbreviations collects the acronyms and abbreviations

used in the manual.
Intended Readers
The manual is intended for the following readers:

z Engineers & technicians
z Operation & maintenance personnel
Conventions
This manual uses the following conventions:

I. General conventions
Convention Description
Arial Normal paragraphs are in Arial.
Arial Narrow Warnings, Cautions, Notes and Tips are in Arial Narrow.
Boldface Headings are in Boldface.
II. Command conventions
Boldface The keywords of a command line are in Boldface.
italic Command arguments are in italic.
[] Items (keywords or arguments) in square brackets [ ] are optional.
III. GUI conventions
<> Button names are inside angle brackets. For example, click <OK> button.
Window names, menu items, data table and field names are inside square
[]
brackets. For example, pop up the [New User] window.
Multi-level menus are separated by forward slashes. For example,

/
[File/Create/Folder].
IV. Keyboard operation
Format Description
Press the key with the key name inside angle brackets. For example, <Enter>,
<Key>
<Tab>, <Backspace>, or <A>.
Press the keys concurrently. For example, <Ctrl+Alt+A> means the three keys
<Key1+Key2>
should be pressed concurrently.
Press the keys in turn. For example, <Alt, A> means the two keys should be
<Key1, Key2>
pressed in turn.
V. Mouse operation
Action Description
Click Press the left button or right button quickly (left button by default).
VI. Symbols
Eye-catching symbols are also used in the manual to highlight the points worthy of
special attention during the operation. They are defined as follows:
Note: Means a complementary description.

C&C08 Digital SPC Switching System Table of Contents
Table of Contents
Chapter 1 Traffic Measurement Overview .................................................................................. 1-1

1.1 Basic Concepts .................................................................................................................. 1-1
1.2 Functional Features ........................................................................................................... 1-4
Chapter 2 Traffic Measurement Operations ............................................................................... 2-1

2.1 Introduction ........................................................................................................................ 2-1
2.2 Creating a Traffic Statistics Task ....................................................................................... 2-3
2.2.1 Selecting a Traffic Statistics Type ........................................................................... 2-4
2.2.2 Choosing a Measure Unit........................................................................................ 2-4
2.2.3 Choosing a Measure Object.................................................................................... 2-5
2.2.4 Selecting or Customizing an Entity ......................................................................... 2-6
2.2.5 Setting Other Parameters ....................................................................................... 2-9
2.3 Modifying a Traffic Statistics Task ................................................................................... 2-13
2.4 Deleting a Traffic Statistics Task ..................................................................................... 2-14
2.5 Querying Traffic Statistics Tasks ..................................................................................... 2-14
2.6 Querying, Saving and Printing Traffic Statistics Results ................................................. 2-15
Chapter 3 Measure Units and Entities......................................................................................... 3-1

3.1 Measurement of Total Traffic of the Office ........................................................................ 3-2
3.1.1 Originating Traffic .................................................................................................... 3-2
3.1.2 Sort User Originating Traffic.................................................................................... 3-3
3.1.3 Inner Traffic ............................................................................................................. 3-4
3.1.4 Originating Outgoing Office Traffic.......................................................................... 3-5
3.1.5 Incoming Office Traffic ............................................................................................ 3-7
3.1.6 Incoming Office Terminating Traffic ........................................................................ 3-8
3.1.7 Transfer Traffic ........................................................................................................ 3-9
3.1.8 Terminating Traffic ................................................................................................ 3-10
3.1.9 Sort User Terminating Traffic ................................................................................ 3-11
3.1.10 Outgoing Office Traffic ........................................................................................ 3-12
3.1.11 ISDN Intra-office Traffic....................................................................................... 3-13
3.1.12 ISDN Originating Outgoing Office Traffic ............................................................ 3-15
3.1.13 ISDN Incoming Office Terminating Traffic .......................................................... 3-16
3.1.14 ISDN Transfer Traffic .......................................................................................... 3-17
3.1.15 Connecting Type Traffic ...................................................................................... 3-18
3.1.16 ISDN Connecting Type Traffic ............................................................................ 3-20
3.1.17 All Offices Sum Traffic......................................................................................... 3-21
3.1.18 Failure Reason Traffic......................................................................................... 3-24
3.2 Measurement of Bearer Traffic ........................................................................................ 3-29
3.2.1 Office Direction Incoming Office Traffic ................................................................ 3-29
i
3.2.2 Office Direction Outgoing Office Traffic ................................................................ 3-31

3.2.3 TKGRP Incoming Office Traffic............................................................................. 3-33
3.2.4 TKGRP Outgoing Office Traffic............................................................................. 3-35
3.2.5 Destination Traffic ................................................................................................. 3-38
3.2.6 Destination Distribution Traffic .............................................................................. 3-40
3.2.7 Single User Traffic................................................................................................. 3-40
3.2.8 User Line GRP Traffic ........................................................................................... 3-41
3.2.9 PABXGRP Traffic .................................................................................................. 3-42
3.2.10 Centrex Intra-group Traffic .................................................................................. 3-43
3.2.11 Centrex Extra-group Traffic................................................................................. 3-44
3.2.12 Centrex Outgoing Group Traffic .......................................................................... 3-44
3.2.13 Supplementary Service Traffic ............................................................................ 3-45
3.2.14 Supplementary Service Centrex Traffic .............................................................. 3-47
3.2.15 ISDN Bearer Traffic............................................................................................. 3-48
3.2.16 ISDN Terminal Service Traffic............................................................................. 3-49
3.2.17 ISDN Supplementary Service Traffic .................................................................. 3-50
3.2.18 ISDN BRA Traffic ................................................................................................ 3-51
3.2.19 ISDN PRA Traffic ................................................................................................ 3-52
3.2.20 Bill Traffic............................................................................................................. 3-52
3.2.21 ACD group message traffic ................................................................................. 3-53
3.2.22 ACD user message traffic ................................................................................... 3-53
3.3 Measurement of Public Component ................................................................................ 3-54
3.3.1 Unqueue Public Unit Traffic .................................................................................. 3-54
3.3.2 Queue Public Unit Traffic ...................................................................................... 3-55
3.3.3 Console Traffic ...................................................................................................... 3-55
3.3.4 SPM Resource MFC Traffic .................................................................................. 3-57
3.3.5 SPM Resource DTR Traffic................................................................................... 3-57
3.3.6 SPM Resource FSK Traffic ................................................................................... 3-58
3.3.7 SPM Resource ECP Traffic................................................................................... 3-58
3.3.8 SPM Resource MFS Traffic .................................................................................. 3-59
3.4 Measurement of Control Component............................................................................... 3-60
3.4.1 CPU Seizure Ratio Traffic ..................................................................................... 3-60
3.5 Measurement of Signaling & Interface ............................................................................ 3-60
3.5.1 ISDN PHI B Traffic ................................................................................................ 3-60
3.5.2 ISDN PHI D Traffic ................................................................................................ 3-61
3.5.3 ISDN UUS1 Traffic ................................................................................................ 3-61
3.5.4 ISDN UUS3 Traffic ................................................................................................ 3-62
3.5.5 ISDN Signaling COMM Traffic .............................................................................. 3-62
3.5.6 MTP Signaling Link Traffic .................................................................................... 3-63
3.5.7 MTP Linkset Traffic ............................................................................................... 3-64
3.5.8 MTP DEST Signaling Point Traffic ........................................................................ 3-64
3.5.9 MTP SP Distribution Traffic................................................................................... 3-65
ii
3.5.10 TUP Total MSU Traffic ........................................................................................ 3-65

3.5.11 TUP MSG Using Traffic....................................................................................... 3-66
3.5.12 TUP Abnormity Traffic......................................................................................... 3-66
3.5.13 TUP Node Performance Traffic........................................................................... 3-67
3.5.14 TUP NET Performance Traffic ............................................................................ 3-68
3.5.15 TUP Circuit Group Performance Traffic .............................................................. 3-68
3.5.16 ISUP Total MSU Traffic....................................................................................... 3-70
3.5.17 ISUP MSG Using Traffic ..................................................................................... 3-70
3.5.18 ISUP Abnomity Traffic......................................................................................... 3-70
3.5.19 ISUP Node Performance Traffic.......................................................................... 3-72
3.5.20 ISUP NET Performance Traffic ........................................................................... 3-72
3.5.21 ISUP Circuit Group Performance Traffic............................................................. 3-73
3.5.22 V5 Interface Traffic.............................................................................................. 3-74
3.5.23 V5 2M Link Information Traffic ............................................................................ 3-74
3.5.24 V5 Physical C Channel Traffic ............................................................................ 3-75
3.5.25 V5 Logical C Channel Traffic .............................................................................. 3-75
3.5.26 V5 B Channel Traffic ........................................................................................... 3-76
3.5.27 MTP Police Message Traffic ............................................................................... 3-78
3.5.28 SCCP Police Message Traffic............................................................................. 3-78
3.6 Measurement of Call Record ........................................................................................... 3-78
3.6.1 Dispersion Duration Traffic.................................................................................... 3-78
3.6.2 Service Quality Traffic ........................................................................................... 3-79
3.6.3 Complete Ratio Traffic .......................................................................................... 3-80
3.6.4 Multi Condition Object Traffic ................................................................................ 3-80
3.7 Inner Running Measurement ........................................................................................... 3-86
3.7.1 SM Flow Traffic ..................................................................................................... 3-86
3.7.2 Inter-module Distribution Traffic ............................................................................ 3-87
3.7.3 RSA Interface Traffic............................................................................................. 3-87
3.8 Measurement of Maximum/Minimum Values & Charging ............................................... 3-88
3.8.1 Top Usage User Traffic ......................................................................................... 3-88
3.8.2 Top Called Busy Traffic......................................................................................... 3-89
3.8.3 Top Ringed No Answer Traffic .............................................................................. 3-90
3.8.4 Top Call Loss Traffic ............................................................................................. 3-91
3.8.5 Top Idle TK Circuit Traffic ..................................................................................... 3-92
3.9 Measurement of IN Service ............................................................................................. 3-93
3.9.1 IN Call Traffic Volume ........................................................................................... 3-93
3.9.2 IN Incoming Call QoS............................................................................................ 3-94
3.9.3 IN Session Stat Traffic .......................................................................................... 3-94
3.9.4 IN Edp Account ..................................................................................................... 3-95
3.9.5 IN Faulted Reason ................................................................................................ 3-96
3.9.6 IN Faulted Statistic ................................................................................................ 3-97
3.9.7 SRF Global Resource Traffic ................................................................................ 3-98
iii
3.9.8 IN Operation Traffic............................................................................................... 3-98

3.9.9 INSM Operation..................................................................................................... 3-99
3.9.10 IN Sampling Trace ............................................................................................ 3-100
3.9.11 SRF Record Informing ...................................................................................... 3-101
3.9.12 SRF Congestion................................................................................................ 3-102
3.9.13 SRF Channel..................................................................................................... 3-102
3.9.14 SRF Operation .................................................................................................. 3-103
3.9.15 SRF Traffic Volume........................................................................................... 3-103
3.9.16 SRM Operation.................................................................................................. 3-104
3.9.17 IN Subscriber Interaction Measure.................................................................... 3-105
3.9.18 IN Outgoing Call QoS........................................................................................ 3-105
3.10 Permanent task............................................................................................................ 3-106
3.10.1 HTR Traffic Control ........................................................................................... 3-106
Chapter 4 Traffic Measurement Application............................................................................... 4-1

4.1 Querying Call Loss............................................................................................................. 4-1
4.1.1 Analyzing Call Loss Reason by Means of “Failure Reason Traffic”........................ 4-1
4.1.2 Locating Further Problem........................................................................................ 4-1
4.1.3 Finding Further Cause by Means of “Call Record” ................................................. 4-3
4.1.4 Finding Essential Call Loss Reason........................................................................ 4-3
4.2 Distributing Busy Traffic..................................................................................................... 4-4
4.3 Balancing Traffic ................................................................................................................ 4-5
4.4 Searching Maximum/Minimum Value ................................................................................ 4-6
4.4.1 Measurement of Top Usage User ........................................................................... 4-6
4.4.2 Measurement of Top Called Busy User .................................................................. 4-6
4.4.3 Measurement of Top Ringed No Answer User ....................................................... 4-6
4.4.4 Measurement of Top Call Loss User ...................................................................... 4-7
4.4.5 Measurement of Top Idle TK Circuit ....................................................................... 4-8
4.4.6 Maximum/Minimum Value Measurement................................................................ 4-8
4.5 Tracing Calls ...................................................................................................................... 4-9
4.6 Locating Factors Influencing Call Completing Rate........................................................... 4-9
4.7 Other Applications ........................................................................................................... 4-11
Chapter 5 Solutions to Common Problems ................................................................................ 5-1

5.1 How to Select a Traffic Statistics Task .............................................................................. 5-1
5.2 How to Select a Measure Unit ........................................................................................... 5-2
5.3 How to Select a Measure Object ....................................................................................... 5-2
5.4 How to Determine an Output Entity ................................................................................... 5-3
5.5 Solutions to Other Common Problems .............................................................................. 5-3
5.5.1 When to Output the Traffic Statistics Result ........................................................... 5-3
5.5.2 How to Understand Questions of Period-Crossing Traffic Statistics....................... 5-4
5.5.3 Statistics Methods of the Number of Seizures, Seizure Traffic and Average Seizure
Duration and Their Relations ........................................................................................... 5-5
5.5.4 When Traffic Measurement of ISDN Terminal Service Is Effective ........................ 5-7
iv
5.5.5 Some Special Instances of Traffic Statistics ........................................................... 5-7

5.5.6 Inaccurate Traffic Statistics Caused by Modification of Trunk Group Data ............ 5-8
5.5.7 Causes of Incomplete Traffic Statistics................................................................... 5-8
5.5.8 Use of the Service Quality Traffic Measurement .................................................... 5-9
5.5.9 Precautions for Using Max/Min Value Traffic Statistics .......................................... 5-9
5.5.10 Why “Number of Answers + Number of Failures < Number of Seizure Attempts
(Seizures)”...................................................................................................................... 5-10
5.5.11 Why Some Entity Results are “Unknown” in Multi Condition Object Traffic
Statistics ......................................................................................................................... 5-10
5.5.12 Measurement of Access Network Users............................................................. 5-11
5.5.13 Influence on Traffic Statistics during Version Upgrade ....................................... 5-12
Appendix A Operations in MML Command Line Mode .............................................................A-1

A.1 Creating a Traffic Statistics Task.......................................................................................A-1
A.2 Setting a Customized Entity ..............................................................................................A-3
A.3 Modifying Task Attributes ..................................................................................................A-4
A.4 Deleting a Traffic Statistics Task .......................................................................................A-5
A.5 Querying Traffic Statistics Tasks.......................................................................................A-5
Appendix B Report Format of Traffic Statistical ........................................................................B-1

B.1 Date and Time Format of Traffic Statistical Report ...........................................................B-1
B.2 Descriptor Explanation ......................................................................................................B-1
B.3 Description of Report Head ...............................................................................................B-2
B.4 Description of Report Body ...............................................................................................B-3
B.5 Description of Report Tail..................................................................................................B-4
B.6 Report Example.................................................................................................................B-4
Appendix C Acronyms and Abbreviations .................................................................................C-1
v
C&C08 Digital SPC Switching System Chapter 1 Traffic Measurement Overview
Chapter 1 Traffic Measurement Overview
1.1 Basic Concepts
Traffic statistics, also called traffic measurement, payload measurement, refers to

various measuring activities carried out on the telephone networks within and around
the switch, so as to provide stable data basis for the measurement, planning & design
and operation management of telephone networks. Traffic measurement covers more
than the measurement and statistics of the traffic. It covers also the measurement of
the system resources, signaling and interfaces, and the internal operations of the
switch.
The following are concepts frequently used during the traffic measurement:
z Entity: It is a specific parameter (for example, traffic, call attempt times, average
seizure duration) for which data must be collected during the traffic
measurement. It can be understood as a measurement parameter.
z Threshold: It is a preset standard for evaluating an entity, usually including two
values, the upper threshold and the lower threshold. If the entity value goes
beyond the upper or lower threshold value, abnormality may occur in the switch.
The upper and lower thresholds can be set as needed. If only the upper
threshold of an entity is concerned, the lower threshold can be set as 0. Likewise,
if only the lower threshold is concerned, the upper threshold can be set as 0.
Note that not all entities have the threshold attribute. Thresholds can only be set
for entities with the threshold attribute.
z Original entity: They are entities already defined in the switch, for example, call
attempt times and seizure traffic. Compare this concept with the user-defined
entity.
z Object: They are various physical or logical entities and the combination of them
to be measured (for example, trunk circuit group, public component, auxiliary
components and destination).
z Measure unit: It is a specific measurement category, for example, incoming
traffic, outgoing traffic and internal traffic. It can be fully described by the
elements such as entity, object, time and output arrangement. It gives answers
to questions such as what will be measured, when the measurement will begin,
how to measure it, when and where the measurement result will be output.
z Measure unit set: It is also called the measurement sub-set. It is a collection of
measure units with certain same attributes, for example, a measurement set
composed of the measurement of the Integrated Services Digital Network (ISDN)
connection type, the measurement of the ISDN local traffic and the
1-1
measurement of the ISDN forwarding traffic. Generally, a traffic measurement

system can be described fully by several measure unit sets, and one category of
traffic tasks corresponds to one measure unit set.
z Restriction: It refers to the conditions of screening measurement objects in a
measure unit, for example, “The calls originated from which incoming terminals
should be measured” (“incoming terminals” for short), “The calls to which
outgoing terminals should be measured” (“outgoing terminals” for short). Only
the calls meeting all restrictions of a specific measure unit can be calculated into
the statistical result of this measure unit. Generally, each measure unit is under
1~5 restrictions. Different measure units vary in their restrictions.
z Object type: It is a specific way to describe the restrictions. Generally, each
restriction can have several optional object types. For example, in the restriction
“The calls from which incoming terminals should be measured”, the incoming
subscribers can be described as “incoming subscriber number” (DN set +
telephone number), or “incoming subscriber extension number” (module number
+ subscriber type + subscriber logical number), but only one of them can be
selected.
z Object value: It refers to the selected object type. For example, once “Incoming
subscriber number” is selected to describe the incoming subscriber, then
“incoming subscriber number” is the object value.
z Measurement type: It is a specific combination of the entity and object, for
example, trunk group traffic, number of outgoing calls.
z Measurement set: It is a collection of several measurement types, usually used
to indicate the total of measurement types that can be fulfilled by a traffic
measurement system.
z Output sending information: It specifies where the measurement result will be
sent.
z Output arranging information: It specifies when the measurement result will be
output.
z Traffic measurement report: It describes the result of the traffic measurement of
a specific measurement type, including measurement object, measurement
entity value, measurement period, start and end time of the measurement cycle,
providing basis for further measurement, planning, running and management of
the performances in the entire office and network.
z Task: It describes the operations of a specific traffic measurement. Such
descriptions cover multiple aspects, for example, measurement object (the calls
to be measured), measurement time, output entity and output time.
z Subtask: It refers to the tasks with different measurement objects but with the
same attributes. For example, the traffic measurement task to measure the traffic
of two analog subscribers contains two subtasks.
z Deactivate: It is one of the traffic measurement operations and can stop the
execution of an existing traffic measurement task, hence no more result will be
1-2
output. In this case, the task itself is not deleted and only the system resources
that it occupies are released.
z Activate: It is an inverse operation of deactivating, which resumes the execution
of a traffic measurement task, and the switch will continue to output the
measurement result.
The following is an example showing the application of these concepts, and briefly
describing the way to create a traffic measurement task. Suppose it is required to
measure the completing rate of the incoming toll calls to the local switch.
1) Create a traffic statistics task to measure the completing rate of the incoming toll
calls. This means to specify the “measure unit”. There are nearly 100 measure
units in the C&C08 Switch. These measure units are classified into nine measure
unit sets respectively for the convenience of finding and application. To locate a
measure unit, first find which measure unit set it belongs to. In this example,
select the measure unit of “Office Direction Incoming Office Traffic” in the
measure unit set of “Measurement of Bearer Traffic”.
Once the measure unit is created, the measurement object is thus specified. In this
example, the measurement object is “office direction”. Note that one traffic
measurement task must correspond to at least one measurement object. Otherwise,
the traffic measurement task makes no practical sense.
2) Specify the range of the measurement object. In this example, specify the
number of the office direction that is connected to the toll switch. The office
direction number selected here becomes a restriction, and measuring the
completing rate of toll calls of a specific office direction is a sub-task.
3) The traffic measurement in this example includes 27 parameters to be measured,
including Seizure Times, Terminal Call Attempt Times, Transfer Call, Attempt
Times, Call Connected Times and Answer Times. These measurement
parameters are entities. You can select desired entities to be output, thus
simplifying the traffic measurement report.
4) Finally, specify the time information and output arrangement information. Then
the creation of a traffic measurement task is completed. In a word, all kinds of
traffic measurement tasks can be easily created as long as you have grasped
such basic concepts as measure unit set, measure unit, measurement object,
entity and time.
1-3
1.2 Functional Features
I. Task management function
The management of traffic measurement tasks includes creating/deleting a

measurement task (sub-task), adding/deleting the objects of a measurement task,
setting/deleting the threshold of a measurement task,
modifying/activating/deactivating a measurement task, querying the information and
status of a measurement task. The text below covers the switch-wide features.
The traffic measurement system of the C&C08 Switch supports a maximum of 150
tasks and 1 200 suc-tasks. Subtasks are allocated dynamically among the tasks.
Creating a new task will be impossible once there already are 1 200 subtasks. Only
when the created tasks are deleted and the resources are released can a new task be
created. Moreover, the system allows you to deactivate the task (sub-task) that is
being carried out. Once the task is deactivated, the occupied resources will be
released, and no more measurement result will be output. That is, the system enters a
sleep status. Only when the task in the sleep status is reactivated can it enter the
measurement status and go on to output the measurement result. Subtasks are
extremely efficient for such measurement of trunk groups. You can use a single task
to measure the traffic of all trunk groups, and output the measurement result in the
output report according to respective objects.
Once a task is created, you can add or delete its measurement object. This feature
makes it possible to add a new object or delete an existing object without deleting the
created task. For example, you can add or delete the measurement of one trunk
group when the original task has registered the measurement of 10 trunk groups.
Moreover, you can quickly create and flexibly select the traffic measurement tasks by
activating and deactivating the tasks. Normally the mostly used traffic measurement
tasks can be fulfilled at one time. You can deactivate the tasks not to be used, and
activate them again when needed, and just modify the attributes such as time before
putting them into traffic measurement.
II. Exception report
Exception reports refer to the measurement result reports that are output only when
the measurement value of the entity is beyond the upper/lower thresholds during the
measurement. The report prompts you of abnormal measurement values of some
entities, actually reflecting some potential abnormalities in the switch. You can
analyze the cause of the abnormal measurement value based on the report, and
eliminate such abnormalities accordingly.
1-4
III. Brief report
A brief report determines which entities can be output, and which cannot. It can delete
the unconcerned entities from the output report, making the report brief and concise.
IV. Sampling measurement
Some special measure units have the function of sampling measurement, all of which
belong to such measure unit sets as call records or traffic distribution. They are
characterized by a very large capacity of call measuring, and generally the
measurement effect can be shown through sampling measurement. Moreover,
sampling measurement is advantageous in saving the system resources and
improving the measurement efficiency. For example, “Destination Distribution Traffic”
measures the traffic of all destination codes in the office direction. This measurement
is fulfilled in a task-matching mode and consumes a lot of system resources. If many
tasks of this kind are registered and no sampling processing is performed, the switch
will probably be short of resources.
There are two kinds of sampling measurement, sampling ratio and sampling times.
The sampling ratio refers to measurements of a certain proportion of calls randomly
sampled in the whole measurement set. For example, 30% means sampling 3 from
10 calls, or 300 from 1 000 calls for measurement. The sampling times refers to the
measurements of a specific number of calls randomly sampled in the whole
measurement set, beyond this number, there will be no further sampling and the
measurement will end. For example, 1 000 times sampling means no further sampling
will be made after sampling 1 000 times of calls according to certain principles.
V. Measurement report incredible
This function marks in the result report whether the measurement result is accurate,
so as to remind you of the credibility of the measurement activity. The incredible
measurement result is caused by many factors, for example, the system time is
modified during the measurement, measurement cycle is modified, configuration data
is set, the counter is reset, or the result is received incompletely.
VI. Screening measurement to CID numbers
This feature allows setting restrictions, and measuring the Caller Identification Display
(CID) numbers which meet specific requirements. For example, measure the number
of incoming calls and traffic of CID numbers with the prefix "654" from a specific trunk
group to the local office.
1-5
VII. Outputting the measurement result in the call record mode
After the screening conditions are specified, the time and behavior of the calls
meeting the conditions in various call stages will be recorded, which is equivalent to
the function of connection tracing which can be automatically recorded and screened.
VIII. No loss of measurement tasks in case of switchover and reloading
This feature ensures the continuity of the measurement task without an interruption
caused by maintenance operations. This is essential to the traffic measurement tasks
with a long cycle. Note that if a switchover or reloading occurs in a specific cycle, the
measurement result in this period will be affected. For example, a traffic measurement
task (Task 1) with the cycle of one hour and a traffic measurement task (Task 2) with
the cycle of 24 hours are created in a certain switch. Suppose a specific module of this
switch is reset at 10:10, then the report of Task 1 at 10:00~11:00 is marked as “result
received incompletely” while the report of Task 2 on that very day is so marked too.
IX. Dynamical modification of a task
Dynamical modification of a task includes the modification of the measurement time,

the addition/deletion of the measurement object, and the modification of the threshold
set in the exception report. Once the task is modified, it can be run according to the
new requirements in two measurement cycles.
X. Display and storage of measurement results
The switch provides a special Traffic measurement window, where the output of the
traffic measurement results can be easily viewed. The switch also provides the
function of printing out the traffic tasks and traffic results. First save the detailed
information about the traffic measurement tasks and results in a text file, then print out
the text file. Or print the traffic measurement results directly through the report print
function.
XI. Self-defined entity
This feature allows you to define a new entity in addition to the original entity to meet
various measurement demands. You can define an entity in two ways. One is
recombining the original entity, and the other is creating a completely new entity. Both
ways are realized by designing a new entity calculation formula.
1-6
C&C08 Digital SPC Switching System Chapter 2 Traffic Measurement Operations
Chapter 2 Traffic Measurement Operations
2.1 Introduction
There are five types of traffic measurement operations:

z Creating a traffic statistics task
z Modifying a traffic statistics task
z Deleting a traffic statistics task
z Querying the information of a traffic statistics task
z Querying, saving and printing the results of traffic statistics
Among the above five items, creating traffic statistics tasks is the most crucial
operation, while other four items are set up on the basis of the existing traffic statistics
task. Each type of traffic measurement corresponds to multiple operation commands.
Therefore, traffic measurement commands are also available in five types, with each
type called a command subset. The operation of traffic measurement refers to the
process of carrying out a command in a command subset.
Type traffic measurement commands in two ways, that is, through command line
window and graphics window.
z Command line window
As shown in Figure 2-1, use the client command line window or the [MML Command]
(MML stands for Man Machine Language) input mode of the navigation tree.
2-1
Figure 2-1 Command line window
z Graphics window
As shown in Figure 2-2, use the [System] input mode of the navigation tree.
2-2
Figure 2-2 Graphics window
The above two input modes get the same result in different ways. Through
comparison, the graphics window is clear and simple for understanding and viewing.
Therefore, we use this input mode to describe the operations of traffic statistics. As for
how to create, modify or query a traffic statistics task in the MML command line mode,
refer to the appendix.
2.2 Creating a Traffic Statistics Task
The steps for creating a traffic statistics task are as follows:

1) Select a traffic statistics type.
2) Choose a proper measure unit according to the measurement purpose.
3) Determine the range of a measure object according to the measurement
demand.
4) Select or set the entities to be output.
5) Set other parameters (such as time information, threshold, direction and time of
sending the output results).
In the following, take the measurement of the connection rate of incoming toll calls as
an example to describe the operation steps for creating a traffic statistics task.
2-3
Suppose to measure the connection rate of incoming toll calls from No. 1 office
direction. The entities to be output include the connected ratio, connected times,
connected traffics, answer ratio, answer times, answer traffics, seizure times, seizure
traffics and a self-defined entity----NOANS. The measurement begins on Sep. 25,
2001 and lasts 30 days, and traffic statistics is performed in three time segments,
9:00~11:00, 14:00~16:00 and 19:00~21:00 everyday from every Monday to Friday. A
traffic statistics report is output to the current workstation, traffic statistics port and
Network Management (NM) port at 22:00 once each day. For monitoring
abnormalities, upper and lower thresholds are set for the connected ratio and answer
ratio, which are respectively 65% and 90%, while the lower and upper thresholds of
the answer ratio are respectively 52% and 72%.
2.2.1 Selecting a Traffic Statistics Type
In Figure 2-2, right click on the right of the window and choose "Create Traffic Task" on
the pop-up menu. The [Select Traffic Statistics Task Type] window will appear, as
shown in Figure 2-3. Choose the option "Beared Object Task" because incoming toll
calls are of the incoming traffic, and for it, the corresponding measuring unit is "office
direction incoming office traffic" which is of the beared object task.
Figure 2-3 Selecting a traffic statistics type
2.2.2 Choosing a Measure Unit
After a traffic statistics type is determined, the [Create Traffic Bearer traffic Task]
window will pop up, as shown in Figure 2-4. As described above, choose the measure
unit "Office direction incoming office traffic".
2-4
Figure 2-4 Creating a bearer traffic task
2.2.3 Choosing a Measure Object
In Figure 2-4, click <Modify…> in the [Measure object] box to pop up the window
[Choose Measure Object], as shown in Figure 2-5. Choose an object instance
according to the restriction and actual demand and add it into the object instance list.
In this case, choose the “Incoming direction” object type and click <Select office>. In
the pop-up window, choose the office direction connected to the toll office----it is Office
direction 1 in this case, then add Office direction 1 into the object instance list. Return
to the window [Choose Measure Object], click <List Of Object Instances to be Added>
to view the chosen measure object in the object list, or delete the chosen measure
object by clicking <Delete>.
Input combined objects in turn according to the elements. Before the input, first
choose the corresponding restriction conditions of each part. Only after that can the
input interface of the elements appear (in Figure 2-5, as the measure object is not a
combined one, the restriction conditions only include “an incoming office direction”).
2-5
Figure 2-5 Choosing a measure objects
2.2.4 Selecting or Customizing an Entity
There are two methods to determine an output entity. Select one from the existing
entities or set a new entity, with the details described as follows.
z Select an existing entity. In Figure 2-4, click <modify> in the [entity select] box to
pop up the [Entity Selection] window, as shown in Figure 2-6. In the window,
entities not to be output are put in the [Available Entity] box, while those to be
output are put in the "The Selected Entity” box. Under the default condition, all
entities are put into the “The Selected Entity” box, that is, all entities are output by
default. You can use the four option arrows to adjust the entities to be output.
and can move an individual entity or multiple entities. and

can move all the entities.
2-6
Figure 2-6 Selecting an entity
z Customize an entity. Besides the available entities, you can define a new desired
entity. In Figure 2-2, click [Object operation/Custom entity] on the main menu to
pop up the [Custom Entity] window, as shown in Figure 2-7. It shows all the
customized entities.
2-7
Figure 2-7 Customizing an entity
In Figure 2-7, right click and select "Set custom entity" in the pop-up window, then the
[Set Custom Entity] window will appear, as shown in Figure 2-8. In this case, add a
new entity “NOANS” in the form of percentage integer, which meets the following
calculation format:
NOANS = call connected times (CNT) - answer times (ANS)
In the format, both CNT and ANS are original entities.
2-8
Figure 2-8 Setting a desired entity
After a new entity is set, it will appear in the custom entity list in Figure 2-7. When
creating an office direction incoming traffic task, you can find that this entity is already
available in the “The Selected Entity” box.
In Figure 2-7, select a customized entity to be deleted (multiple entities allowed), then
right click to select "Delete custom entity" in the pop-up window and delete the
chosen entity after confirmation.
In addition, in Figure 2-7, right click to select such functions as querying a custom
entity and print a custom entity.
2.2.5 Setting Other Parameters
z Time information: It describes the time to perform the measurement and the time
mode for the measurement. In Figure 2-4, click <Modify…> in the [Time
information] box to pop up the [TimeSet] window, as shown in Figure 2-9.
2-9
9/25, 2001, Tuesday
Figure 2-9 Setting time
Time information includes the start date, statistics duration (permanent duration by
default), measure period (15 minutes by default), measure date (everyday by default,
or set as several days every week or several days every month), measure time
segment (from 00:00 to 00:00 by default, or set as three time segments). In this case,
the measurement begins on Sep. 25, 2001 and lasts 30 days, and traffic statistics is
performed in three time segments, 9:00~11:00, 14:00~16:00 and 19:00~21:00
everyday from every Monday to Friday.
z Entity threshold: This function allows several entities (at most four) to be set with
upper limits and lower limits. In Figure 2-4, click <Modify…> in the [Entity
Threshold Set] box to pop up the [EntityThresholdSet] window, as shown in
Figure 2-10. In this case, the call connected times and answer times are set with
thresholds.
2-10
Figure 2-10 Setting entity thresholds
z Other information: In Figure 2-4, click <Modify...> in the [Other information] box
to pop up the [Other Information] window, as shown in Figure 2-11.
Figure 2-11 Setting other Information
2-11
Output service: Specify where the traffic statistics report should be sent. By default the
report is sent to the current workstation. It can also be sent to the traffic statistics port
and NM port. In this case, output and send the report to the current workstation, traffic
statistics port and NM port.
Output arrangement: Specify when the traffic statistics report should be output, with
“perperiod output” by default, that is, any result should be output immediately after it is
obtained. “t” or “specific output” can also be selected. “Over threshold” means that no
traffic statistics report is output when the entity measurement value is within the
threshold. A report will be generated only when the measurement value is over the
threshold range. In this case, select “specific output”, with the output time being
specified as 22:00.
Sampling parameter: Some measuring units generate a large quantity of information,

so sampling measurement is required to keep the accuracy and greatly reduce the
burdens on the switch. It is 100% sampling by default. It should be noted that not all
the measuring units have sampling parameters.
Up to now, complete information is specified for the setting up of a traffic statistics task.
Return to the window shown in Figure 2-4 and you can see all the previously set
parameters. Click <OK> to complete the setting up of the traffic statistics task.
To sum up, the essential steps to be considered for creating a traffic statistics task are
as follows:
1) Select the type for a traffic statistics task.
2) Select a measure unit.
3) Determine the range of a measure object by selecting the restriction condition
and object instance.
4) Select entities.
5) Determine the time information, for example, three measure time segments
everyday (a time segment 00:00 to 00:00 is accepted by default if nothing is
specified) or cyclic measurement everyday/every week/every month.
2-12
2.3 Modifying a Traffic Statistics Task
Select a traffic statistics task in Figure 2-2, right click to pop up the interface as shown
in Figure 2-12, then select a desired command to modify the task.
Figure 2-12 Traffic task modification
The operations of modifying a traffic statistics task are available in two types,
modification of task status and modification of task attribute.
z Operations of modifying task status include "Activate Traffic Task" and
"Deactivate Traffic Task". As described in Chapter 1, you can make a current
traffic statistics task meet the actual requirements by carrying out the operations
of activation and deactivation and avoid repeated setup and deletion of common
traffic statistics tasks.
z Operations of modifying task attribute include "Add/Delete Traffic Task Entity
Threshold", "Add/Delete Traffic Task Measure Object", "Modify Traffic Task
Sampling Parameter", "Modify Traffic Task Output Entity", "Modify Traffic Task
Time", "Modify Traffic Result Output Device" and "Modify Traffic Result Output
Arrange".
1) To know the operation of the switch by observing whether the measurement
value of an entity is normal, add threshold setting for this entity. To simply record
the measurement value of this entity, delete the existing threshold setting.
2-13
2) The addition and modification of the measure object instance are a pair of
reciprocal operation commands. For example, the traffic task for two trunk
groups (including two subtasks) has been set up. To add another trunk group
temporarily, just add it into the task as a measure object through adding a
measure object instance, then the number of subtasks increase from 2 to 3.
Similarly, if it is no longer necessary to perform traffic statistics for a trunk group,
delete this trunk group from the task through deleting the measure object
instance, then the number of subtasks decrease to 1.
3) The sampling parameters of a traffic task are set according to the default value.
4) The default time segment begins from 4:00 am to the ending time of
measurement. Sometimes, instead of the maximum value of this time segment,
the maximum value during busy hours (9:00~11:00) is desired, so it is necessary
to clear the maximum value counter at 9:00 by setting the time to clear the
maximum value and set the measurement result to be outputted at 11:00 to get
the maximum measurement result at 9:00~11:00.
In addition, as described in Chapter 1, the measurement result may become
incredible if the task attribute is modified during the measurement. Therefore, it
should be considered whether the measurement result will be affected when a task
attribute is modified.
2.4 Deleting a Traffic Statistics Task
In Figure 2-12, select "Delete traffic task" to delete a selected task or multiple ones.
2.5 Querying Traffic Statistics Tasks
In Figure 2-12, click "List Traffic Task Attribute" to pop up the [Detail Information]
window, as shown in Figure 2-13. The displayed information includes task
Identification (ID), task status, measure unit, original output entity, re-defined output
entity, newly-defined output entity, threshold setting, output sending equipment and
output arrangement.
2-14
Figure 2-13 Traffic task information
2.6 Querying, Saving and Printing Traffic Statistics Results

z Query traffic statistics results
In Figure 2-2, select [view/output of statistics], and the traffic output window will
appear, in which the traffic statistics result can be observed. Or first select a task and
then right click to select [jump to/traffic statistics result] on the pop-up menu to view
the traffic statistics result in the window.
z Save traffic statistics results
Select the traffic statistics results to be saved, then right click to select “SAVE” on the
pull-down menu and type in the dialog box the name of the file saving the traffic
statistics result. After confirmation, the operation of saving the traffic statistics result is
implemented.
In the MML command line interface, the steps for saving the traffic statistics result are
as follows:
1) Select “Start saving execution result” on the [Operation] menu (or press <F11>)
to pop up the dialog box of saving.
2) The default file name is shown in the dialog box, which can be modified, and the
file should be in the RPT*.TXT format, press <Save> to start saving the result of
the traffic task report.
3) Use LST TRFINF and DSP TRFRPT to query the traffic task information and
display the traffic statistics report, and the output traffic task information and
traffic statistics report are saved immediately into a text file.
2-15
4) Select “Start saving execution report” on the [Operation] menu (or press <F11>)
to stop saving.
z Print traffic statistics results
In Figure 2-2, select [view/output of statistics] on the main menu (the window on the
lower part of the interface is the traffic output window). Then select
[System/Immediately print] on the main menu to print the traffic statistics result, or first
open the traffic statistics report file and then print it.
2-16
C&C08 Digital SPC Switching System Chapter 3 Measure Units and Entities
Chapter 3 Measure Units and Entities
For the purpose of offering a detailed and comprehensive description of the traffic
measurement of the C&C08 Digital SPC Switching System, the chapter shall
introduce fully the measure units and entities provided by the traffic measurement
system.
The following text details the measure unit names, objects & entities of the measure
units, serial numbers & MML words of the entities, and so on.
When reading each measure unit, pay attention to the following points.
z The result type of each measure unit is of either short type or long type. Most are
of short type. It is because, in general, the number of entities (the result) is not
more than 45 and the specified maximum length of the short result is 45 at
present. The length can be redefined if it does not meet the requirements in the
future. While, some results, for example, Dispersion Duration Traffic, need to be
presented in long result because the number of entities may be more than 45.
Due to the minority of the measure units with long result, the division of results to
long and short ones saves the memory as well as the communication bandwidth
between the Front Administration Module (FAM) & Back Administration Module
(BAM). It should be noted that the maximum length of long result is 255 when
optimizing the traffic measurement. In addition, some results, with the number of
entities less than 45, are presented in long result. This is because the result
length may be expanded in the future.
z Meanings of most measure units and entities are offered except the very explicit
ones. The entities marked with Note: Invisible to users in the column of Entity
name/entity meaning are invisible on the background, but they have already
been output to the background from the FAM. This is different from the controlled
output of the Entity Bit Table. In the latter case, an entity will not be output to the
background if it is set to “No output”.
z The uniform numbering of all the measuring entities helps users to quickly query
entities with the input of the serial numbers when using the MML. The entity
serial numbers are almost consecutive in a measure unit, but not consecutive
from one measure unit to another with the consideration of future quantity
change of entities.
z X and Y in the entity threshold stand for the lower and upper threshold
respectively. The absence of the entity threshold means the entity has no
threshold.
3-1
3.1 Measurement of Total Traffic of the Office
3.1.1 Originating Traffic
Measure unit No.: 1
Meaning: Gets the basic data that is global and belongs to the calls of this traffic flow
direction (including ISDN calls). The result is the entity sum of all the subscribers in
the measure unit 2.
MML word: OR
Object: All subscriber frame lines (TLUR)
Result type & other attributes: Short result
Table 3-1 Measurement of the originating traffic
Entity
Entity name Meaning MML word
No.
1 CALL ATTEMPT TIMES It refers to the number of the picking-ups. PEGS
It refers to the number of the answered call attempts. As for various supplementary
2 ANSWER TIMES services (Call Forwarding Unconditional, Call Forwarding No Reply, Call Forwarding ANS
Busy, and so on), the number is counted if only the call is answered.
It is the sum of the times that the user does not dial for a long time after off-hook and
3 NO DIALING TIMES NDG
the times that the user releases the call before dialing.
NO DIALING TIMEOUT It refers to the times that the user listens to the busy tone while not dialing for a long
4 LTNDG
TIMES time after picking up the phone.
NO DIALING ABANDON It refers to the times that the user hangs on before listening to the busy tone after
5 NDGABN
TIMES off-hook.
It refers to the number of incomplete dialings which may result in the inability to
INCOMPLETE DIALING
6 distinguish the local call, outgoing call, call to the system. The number of incomplete PDIMP
TIMES
calls includes the number of interval time-outs and that of releases during the dialing.
After the user originates a call to a destination address, the received number is not in
compliance with the existing destination address or the recognized address number.
INVALID ADDRESS
7 The switch will intercept the call (through sending the signal tone or voice INVADR
TIMES
announcement). It includes the inability to determine the called number and dead
number.
Although the outgoing circuit/subscriber line is available to the required destination,
SWITCH NETWORK
the switching network cannot perform the connection and there is no other channel
8 BLOCKING CALL LOSS NETBLCL
available. It includes the number of failures of allocating the network resource in a
TIMES
module and between modules.
COMMON RESOURCE
CMRUAVC
9 UNAVAIL CALL LOSS Certain service circuit or other public resources are not available.
L
TIMES
SYSTEM FAULT CALL
10 Internal error of the switch SYSFLCL
LOSS TIMES
BLOCKED BY AUTO Call loss due to the heavy load on the Central Processing Unit (CPU), which may
11 ALBLCL
CALL LOSS TIMES further result in the overloading to a certain extend
FLOW CTRL CALL LOSS
12 Call loss due to NM control with the high density of traffic FWCTLCL
TIMES
IN 3S HEAR DIAL TONE It refers to the times of listening to the dial tone within three seconds after picking up
13 HDIN3S
TIMES the phone.
HEAR DIAL TONE OUT It refers to the times of listening to the dial tone three seconds later after picking up
14 HDOUT3S
OF 3S the phone.
Traffic transmitted during the time from picking up the phone to the completion of the
15 SEIZURE TRAFFIC SERL
call (including the failure or release during the speaking)
3-2
Entity
No.
Traffic in the flow direction of the originating call during the time from the answering
17 ANSWER TRAFFIC RERL
to the completion of the call
19 MAINTENANCE TRAFFIC Traffic transmitted during the time when the subscriber line is in the maintaining state MERL
3.1.2 Sort User Originating Traffic
Measure unit No.: 2
Meaning: Gets the basic data of subscriber calls belonging to this traffic flow direction.
The result of the measure unit 1 is the entity sum of all the subscribers in this unit.
MML word: SRTOR
Object: Sorted subscriber frames (SRTUR)

z Ordinary user (ST)
z V5ST user (V5ST)
z Local ISDN user (ISDN)
z V5ISDN user (V5ISDN)
Table 3-2 Measurement of the originating traffic of sorted users
Entity MML
Entity name Meaning
No. word
CALL ATTEMPT
2001 It refers to the number of the picking-ups. PEGS
TIMES
It refers to the number of the answered call attempts. As for various supplementary
2002 ANSWER TIMES services (Call Forwarding Unconditional, Call Forwarding No Reply and Call Forwarding ANS
Busy, and so on), the number is counted if only the call is answered.
NO DIALLING It is the sum of the times that the user does not dial for a long time after off-hook and the
2003 NDG
TIMES times that the user releases the call before dialing.
NO DIALLING It refers to the times of listening to the busy tone while not dialing for a long time after
2004 LTNDG
TIMEOUT TIMES picking up the phone.
NO DIALLING
2005 It refers to the number of hang–ons before the user listens to the busy tone after off-hook. NDGABN
ABANDON TIMES
It refers to the number of incomplete dialings which may result in the inability to distinguish
INCOMPLETE
2006 the local call, outgoing call, call to the system. The number of incomplete calls includes the PDIMP
DIALLING TIMES
number of interval time-outs and that of releases during the dialing.
After the user originates a call to a destination address, the received number is not in
INVALID ADDRESS compliance with the existing destination address or the recognized address number. The
2007 INVADR
TIMES switch will intercept the call (through sending the signal tone or voice announcement). It
includes the inability to determine the called number and dead number.
SWITCH Although the outgoing circuit/subscriber line is available to the required destination, the
NETWORK switching network cannot perform the connection and there is no other channel available. It
2008 NETBLCL
BLOCKING CALL includes the number of failures of allocating the network resource in a module and between
LOSS TIMES modules.
COMMON
RESOURCE CMRUAV
2009 Certain service circuit or other public resources are not available.
UNAVAIL CALL CL
LOSS TIMES
3-3
Entity MML
Entity name Meaning
No. word
SYSTEM FAULT
CALL LOSS TIMES
BLOCKED BY
Call loss due to the heavy load on the CPU, which may further result in the overloading to a
2011 AUTO CALL LOSS ALBLCL
certain extend
TIMES
FLOW CTRL CALL
LOSS TIMES
IN 3S HEAR DIAL It refers to the times of listening to the dial tone within three seconds after picking up the
2013 HDIN3S
TONE TIMES phone.
HEAR DIAL TONE It refers to the times of listening to the dial tone three seconds later after picking up the
2014 HDOUT3S
OUT OF 3S phone.
Traffic transmitted during the time from picking up the phone to the completion of the call
(including the failure or release during the speaking)
Traffic in the flow direction of the originating call during the time from the answering to the
completion of the call
MAINTENANCE
2019 Traffic transmitted during the time when the subscriber line is in the maintaining state MERL
TRAFFIC
3.1.3 Inner Traffic
Measure unit No.: 3
Meaning: Gets the global basic data of calls belonging to this traffic flow direction
(including ISDN calls).
MML word: INT
Table 3-3 Measurement of the internal traffic
Entity Entity
No. threshold
CALL ATTEMPT
31 It refers to the times that the called is analyzed to be in the local office. PEGS
TIMES
CALL
32 CONNECTED It refers to the number of successful busy call attempts (ringing). CNT
TIMES
It refers to the number of answered calls. As for various supplementary
services (Call Forwarding Unconditional, Call Forwarding No Reply and Call
33 ANSWER TIMES ANS
Forwarding Busy, and so on), the number is counted if only the call is
answered.
It refers to the times that the called belongs to the local office through the
INCOMPLETE analysis of the called number. However, the called cannot be located if the
34 PDIMP
DIALLING TIMES number is not complete. The number of incomplete calls includes the
number of interval time-outs and that of releases during the dialing.
PARTIAL
It refers to the times that the user releases the call in dialing after the location
35 DIALLING PDABN
of the called to the local office through the analysis of the called number.
ABANDON TIMES
PARTIAL
It refers to the number of interval time-outs in dialing after the location of the
36 DIALLING PDTOU
called to the local office through the analysis of the called number.
TIMEOUT TIMES
3-4
Entity Entity
No. threshold
It refers to the times that the number after the office number is a dead
INVALID number or the call is barred, although the call is determined to be a local call
37 INVADR
ADDRESS TIMES after the user dials the correct office number. It includes the inability to
determine the called or dead number.
ABANDON
It refers to the times that the caller forward releases the call during the time
38 BEFORE RING BRGABN
from the determining of the local call to the ringing of the called.
TIMES
SWITCH Although the outgoing circuit/subscriber line is available to the required
NETWORK destination, the switching network cannot perform the connection and there
39 NETBLCL
BLOCKING CALL is no other channel available. It includes the number of failures of allocating
LOSS TIMES the network resource in a module and between modules.
COMMON
RESOURCE
40 Certain service circuit or other public resources are not available. CMRUAVCL
UNAVAIL CALL
LOSS TIMES
SYSTEM FAULT
CALL LOSS TIMES
BLOCKED BY
Call loss due to the heavy load of CPU, which may further result in the
overloading to a certain extend
TIMES
FLOW CTRL CALL
LOSS TIMES
It refers to the number of unsuccessful call attempts because of the
CALLED USER
44 erroneous subscriber line. It includes the erroneous state, testing state and CLDFL
LINE FAULT TIMES
maintaining state of the called interface.
CALLED BUSY It refers to the number of unsuccessful call attempts because the called is
45 CBSY
TIMES busy. The called is possibly making a toll call, a local call, and so on.
CALLED TOLL It refers to the times of having distinguished that the called is making a toll
46 CTB
BUSY TIMES call.
CALLED LOCAL It refers to the times of having distinguished that the called is making a local
47 CLB
BUSY TIMES call.
ABANDON AFTER It refers to the times that the local caller releases the call while the called is
48 ARGABN
RING TIMES ringing.
RINGED NO It refers to the times that the switch forcedly releases the call due to no
49 LTNANS
ANSWER TIMES answer from the called during the ringing.
Traffic transmitted during the time from determining that the called is in the
50 SEIZURE TRAFFIC local office by analyzing the call originated locally to the completion of the call SERL
(including the failure or release during the call connection)
Traffic in the flow direction of the internal call (local call) during the time from
the answering to the completion of the call
CONNECTED Number of connections/Number of call attempts (calculated on the

54 CNTR (65,90)
RATIO background)
Number of answerings/Number of call attempts (calculated on the

55 ANSWER RATIO ANSR (52,72)
background)
3.1.4 Originating Outgoing Office Traffic
Measure unit No.: 4
3-5
MML word: OROG
Table 3-4 Measurement of the originating outgoing traffic
Entity Entity
No. threshold
CALL ATTEMPT It refers to the number of outgoing call attempts through the analysis of the
61 PEGS
TIMES call originated locally.
It refers to the number of seizure attempts of outgoing (bi-directional) trunk
62 TK BID TIMES circuits, that is, the times that the software selects outgoing (bi-directional) TKBID
trunk circuits.
It refers to the number of successful seizures of outgoing (bi-directional)
trunk circuits. As for the Signaling System No. 7 (SS7), it is the times of
TK SEIZURE
63 receiving the seizure ACKnowledgement (ACK) signal while for the TKSEIZ
TIMES
Channel Associated Signaling (CAS), it is the times of sending the seizure
signal.
CALL
It refers to the times of sending ringing to the called after the call has been
64 CONNECTED CNT
established within the network.
TIMES
It refers to the number of call attempts that the trunk has received the
65 ANSWER TIMES ANS
"answering" state indication.
It refers to the number of the call attempts that are not answered after the
connection because of the called not answering for a long time, the caller
earlier releasing or other reasons. (Because the called is in another office,
CALL NO
66 the signaling cannot distinguish various circumstances of the called party, NANS
ANSWER TIMES
therefore, reasons are classified into one type). It can be worked out by
subtracting the answered calls from the connected calls. (Note: Invisible
to users)
It refers to the total number of the call attempts that the called is not
INCOMPLETE determined because of incomplete number, although the number is judged
67 PDIMP
DIALLING TIMES to be an originated outgoing call, and the number of the incomplete office
address of the peer end.
PARTIAL
It refers to the times that the user releases the call in dialing after the
DIALLING
68 location of the call to be an outgoing call through the analysis of the called PDABN
ABANDON
number.
TIMES
PARTIAL
It refers to the number of interval time-outs in dialing after determining that
69 DIALLING PDTOU
the call is an outgoing call.
TIMEOUT TIMES
INVALID number or the call is barred, although the call is determined to be an
70 INVADR
ADDRESS TIMES outgoing call after the user dials the correct office number. It includes the
inability to determine the called or dead number.
ABANDON It refers to the times that the caller forward releases the call during the time
71 BEFORE RING from the determining of the call to be an outgoing call, to the ringing of the BRGABN
TIMES called.
72 NETBLCL
COMMON
RESOURCE
UNAVAIL CALL
LOSS TIMES
SYSTEM FAULT
74 CALL LOSS Internal error of the switch SYSFLCL
TIMES
3-6
Entity Entity
No. threshold
BLOCKED BY
75 AUTO CALL ALBLCL
LOSS TIMES
FLOW CTRL
76 CALL LOSS Call loss due to NM control with the high density of traffic FWCTLCL
TIMES
LASTCHOICE
It is the number of route selection failures due to busy outgoing
ROUTE
77 (bi-directional) trunk circuits, that is, the number of failures that the software LRUOFL
OVERFLOW
selects outgoing (bi-directional) trunk circuits.
TIMES
78 CBSY
79 CTB
BUSY TIMES call.
80 CLB
BUSY TIMES call.
ABANDON
It refers to the times that the caller releases the call while the called is
81 AFTER RING ARGABN
ringing.
TIMES
82 LTNANS
SEIZURE Traffic transmitted during the time from judging the call is an outgoing call
83 SERL
TRAFFIC originated locally, to the completion of the call.
ANSWER
85 Traffic corresponding to the speaking part of the call connection RERL
TRAFFIC
87 CNTR (65,90)
RATIO background)
background)
3.1.5 Incoming Office Traffic
Measure unit No.: 5
MML word: INC
Object: All incoming and bi-directional circuits (TLIBTK)
Table 3-5 Measurement of the incoming traffic
Entity Entity
No. threshold
SEIZURE
91 It refers to the number of busy incoming trunk circuits. SEIZ
TIMES
It refers to the number of answered call attempts. As for various
ANSWER supplementary services (Call Forwarding Unconditional, Call Forwarding
92 ANS
TIMES No Reply and Call Forwarding Busy, and so on), the number is counted if
only the call is answered.
3-7
Entity Entity
No. threshold
Because the incoming (bi-directional) trunk has not received the complete
INCOMPLETE
number, it cannot determine if the call is a destination call or a tandem call,
93 DIALLING PDIMP
including not transmitting number, releasing in dialing, interval between
TIMES
dialing overtime, and forward releasing of the incoming trunk.
The received incoming trunk number is not in compliance with the existing
INVALID
destination address or the recognized address number. Therefore, the call
94 ADDRESS INVADR
is intercepted (promoted with the signal tone or by the operator). It includes
TIMES
the inability to determine the called and dead number.
SWITCH
Although the outgoing circuit/subscriber line is available to the required
NETWORK
destination, the switching network cannot perform the connection and there
95 BLOCKING NETBLCL
is no other channel available. It includes the number of failures of allocating
CALL LOSS
the network resource in a module and between modules.
TIMES
COMMON
RESOURCE
UNAVAIL CALL
LOSS TIMES
SYSTEM FAULT
TIMES
BLOCKED BY
98 AUTO CALL ALBLCL
LOSS TIMES
FLOW CTRL
TIMES
SEIZURE Traffic transmitted during the time from the seizing of the incoming trunk
100 SERL
TRAFFIC (bi-directional) to the completion of the call
ANSWER
TRAFFIC
MAINTENANCE It is the number of the incoming (bi-directional) trunk circuits in the
104 MNTCIR
CIRCUIT NUM maintaining state
ANSWER Number of answerings/Number of call attempts (calculated on the
105 ANSR (52,72)
RATIO background)
3.1.6 Incoming Office Terminating Traffic
Measure unit No.: 6
MML word: INCTE
3-8
Table 3-6 Measurement of the incoming terminating traffic
Entity Entity
No. threshold
It is the times that the incoming (bi-directional) trunk circuits are seized
111 SEIZURE TIMES and the called is located to the local office by the analysis of the called SEIZ
number.
CALL
It is the times of sending ringing to the called after the call has been
112 CONNECTED CNT
TIMES
supplementary services (Call Forwarding Unconditional, Call
113 ANSWER TIMES ANS
Forwarding No Reply and Call Forwarding Busy, and so on), the
number is counted if only the call is answered.
It refers to the times that the called is not determined because of
incomplete number, although the called is located to be a local
INCOMPLETE
114 subscriber by the analysis of the number received by the incoming PDIMP
DIALLING TIMES
(bi-directional) trunk. It includes the releasing during dialing and the
interval between dialing overtime.
number or the call is barred, although the called is judged as a local
INVALID ADDRESS
115 subscriber through the analysis of the number received by the INVADR
TIMES
incoming trunk. It includes the inability to determine the called or the
empty/dead number.
It refers to the times that the caller forward releases the call during the
ABANDON
time from the determining of the called is a local subscriber, by the
analysis of the number received by the incoming trunk, to the ringing
TIMES
of the called.
Although the outgoing circuit/subscriber line is available to the
SWITCH
required destination, the switching network cannot perform the
NETWORK
117 connection and there is no other channel available. It includes the NETBLCL
BLOCKING CALL
number of failures of allocating the network resource in a module and
LOSS TIMES
between modules.
COMMON
RESOURCE
UNAVAIL CALL
LOSS TIMES
SYSTEM FAULT
CALL LOSS TIMES
BLOCKED BY
TIMES
FLOW CTRL CALL
LOSS TIMES
It refers to the number of unsuccessful call attempts because of the
CALLED USER
122 erroneous subscriber line. It includes the erroneous state, testing CLDFL
LINE FAULT TIMES
state and maintaining state of the called interface.
It refers to the number of unsuccessful call attempts because the
CALLED BUSY
123 called is busy. The called is possibly making a toll call, a local call, and CBSY
TIMES
so on.
CALLED TOLL It refers to the times of having distinguished that the called is making a
124 CTB
BUSY TIMES toll call.
CALLED LOCAL It refers to the times of having distinguished that the called is making a
125 CLB
BUSY TIMES local call.
ABANDON AFTER It refers to the times that the local caller releases the call while the
126 ARGABN
RING TIMES called is ringing.
127 LTNANS
Traffic transmitted during the time from determining the called is in the
128 SEIZURE TRAFFIC local office to the completion of the call when the call seizes the SERL
incoming (bi-directional) trunk circuit.
130 ANSWER TRAFFIC Traffic corresponding to the speaking part of the call connection RERL
3-9
Entity Entity
No. threshold
CONNECTED Number of connections/Number of occupancies (calculated on the
132 CNTR (65,90)
RATIO background)
background)
3.1.7 Transfer Traffic
Measure unit No.: 7
MML word: TRN
Table 3-7 Measurement of the transit traffic
Entity Entity
No. threshold
TRANSFER CALL It is the times that the call is judged to be an outgoing call after the
141 TRNSEIZ
SEIZURE TIMES incoming trunk is seized.
It refers to the number of seizure attempts of outgoing (bi-directional)
142 OUTTK BID TIMES trunk circuits, that is, the times that the software selects outgoing OTKBID
(bi-directional) trunk circuits.
It refers to the number of successful seizures of outgoing (bi-directional)
OUTTK SEIZURE
143 trunk circuits. As for the SS7, it is the times of receiving the seizure ACK OTKSEIZ
TIMES
signal while for the CAS, it is the times of sending the seizure signal.
CALL
144 CONNECTED CNT
TIMES
CALL NO ANSWER
146 the signaling cannot distinguish various circumstances of the called party, NANS
TIMES
subtracting the answered calls from the connected calls. (Note: Invisible
to users)
It refers to the sum of the number of the call attempts that the called is not
determined because of incomplete number, although the number is
INCOMPLETE
147 judged to be an originated outgoing call, and the number of the times that PDIMP
DIALLING TIMES
the office address of the peer end is incomplete. It includes the interval
between dialing overtime and release during dialing.
ABANDON It refers to the times that the caller forward releases the call during the
148 BEFORE RING time from the determining of the call to be an outgoing call, by the analysis BRGABN
TIMES of the number received by the incoming trunk, to the ringing of the called.
3-10
Entity Entity
No. threshold
NETWORK destination, the switching network cannot perform the connection and
149 NETBLCL
BLOCKING CALL there is no other channel available. It includes the number of failures of
LOSS TIMES allocating the network resource in a module and between modules.
COMMON
RESOURCE CMRUAV
UNAVAIL CALL CL
LOSS TIMES
SYSTEM FAULT
CALL LOSS TIMES
BLOCKED BY
TIMES
FLOW CTRL CALL
LOSS TIMES
LASTCHOICE
ROUTE
154 (bi-directional) trunk circuits, that is, the times that the software fails to LRUOFL
OVERFLOW
select outgoing (bi-directional) trunk circuits.
TIMES
155 CBSY
156 CTB
BUSY TIMES call.
CALLED LOCAL It refers to the times of having distinguished that the called is making a
157 CLB
BUSY TIMES local call.
Traffic transmitted during the time from judging the call is an outgoing call
originated from the incoming trunk, to the completion of the call.
162 CNTR (65,90)
RATIO background)
Number of answerings/Number of occupancies (calculated on the
background)
3.1.8 Terminating Traffic
Measure unit No.: 8
(including ISDN calls). The result is the traffic sum of all the subscribers in the
measure unit 9 except for the entities BID TIMES & DIALLING VACANT TIMES. This
is because the subscribers of the class cannot be obtained when the call does not
reach the called.
MML word: TE
3-11
Table 3-8 Measurement of the terminating traffic
Entity Entity
No. threshold
171 BID TIMES It is the number of call attempts to the called by the software. BID
CALL
172 CONNECTED CNT
TIMES
supplementary services (Call Forwarding Unconditional, Call Forwarding No
Reply, Call Forwarding Busy, and so on), the number is counted if only the call
is answered.
BLOCKED BY
174 AUTO CALL ALBLCL
LOSS TIMES
FLOW CTRL
TIMES
DIALLING
It is the times that the called number is an empty number. It includes the times
176 VACANT CODE VAC
that the called number or dead/empty number cannot be determined.
TIMES
CALLED USER It refers to the number of unsuccessful call attempts because of the erroneous
177 LINE FAULT subscriber line. It includes the erroneous state, testing state and maintaining CLDFL
TIMES state of the called interface.
178 CBSY
CALLED TOLL
179 It refers to the times of having distinguished that the called is making a toll call. CTB
BUSY TIMES
180 CLB
BUSY TIMES call.
ABANDON
It refers to the times that the local caller releases the call while the called is
ringing.
TIMES
RINGED NO It refers to the times that the switch forcedly releases the call due to no answer
182 LTNANS
ANSWER TIMES from the called during the ringing.
SEIZURE Traffic transmitted during all call attempts no matter whether they get an
183 SERL
TRAFFIC answering signal or not
ANSWER
TRAFFIC
MAINTENANCE Traffic transmitted during the time when the subscriber line is in the
187 MERL
TRAFFIC maintaining state
CONNECTED
189 Number of connections/Number of the BIDs (calculated on the background) CNTR (65,90)
RATIO
background)
3.1.9 Sort User Terminating Traffic
Measure unit No.: 9
Meaning: Gets the basic data of subscriber calls belonging to this traffic flow direction.
MML word: SRTTE

z Ordinary uer (ST)
z V5ST user (V5ST)
3-12
z Local ISDN user (ISDN)

z V5ISDN user (V5ISDN)
Table 3-9 Measurement of the terminating traffic of sorted users
Entity MML Entity

Entity name Meaning
No. word threshold
CALL
2052 CONNECTED CNT
TIMES
It refers to the number of answered call attempts. As for various supplementary
services (Call Forwarding Unconditional, Call Forwarding No Reply, Call
Forwarding Busy, and so on), the number is counted if only the call is
answered.
BLOCKED BY ALBLCL
2054 AUTO CALL
LOSS TIMES
FLOW CTRL FWCTLC
2055 CALL LOSS Call loss due to NM control with the high density of traffic L
TIMES
DIALING VAC
2056 Number of the dead number of the called of the received call
VACANT TIMES
CALLED BUSY It refers to the number of unsuccessful call attempts because the called is busy.
2058 CBSY
TIMES The called is possibly making a toll call, a local call, and so on.
CALLED TOLL
BUSY TIMES
2060 CLB
BUSY TIMES call.
ABANDON
ringing.
TIMES
2062 LTNANS
SEIZURE Traffic transmitted during all call attempts no matter whether they get an
2063 SERL
TRAFFIC answering signal or not
ANSWER
TRAFFIC
MAINTENANCE Traffic transmitted during the time while the subscriber line is in the maintaining
2067 MERL
TRAFFIC state
2069 CONNECTED Number of the connection/Number of the BID (calculated on the background) CNTR
(65,90)
RATIO
2070 ANSWER RATIO Number of the answering/Number of the BID (calculated on the background) ANSR (52,72)
3.1.10 Outgoing Office Traffic
Measure unit No.: 10
MML word: OG
3-13
Object: All outgoing and bi-directional circuits (TLOBTK)
Table 3-10 Measurement of the outgoing traffic
Entity MML Entity

Entity name Meaning
No. word threshold
It is the number of seizure attempts of outgoing (bi-directional) trunk circuits by the
201 BID TIMES BID
software.
It refers to the number of successful seizures of outgoing (bi-directional) trunk
SEIZURE
202 circuits. As for the SS7, it is the times of receiving the seizure ACK signal while for SEIZ
TIMES
the CAS, it is the times of sending the seizure signal.
CALL
203 CONNECTED CNT
TIMES
ANSWER It refers to the number of call attempts that the trunk has received the "answering"
204 ANS
TIMES state indication.
connection because of the called not answering for a long time, the caller earlier
CALL NO
releasing or other reasons. (Because the called is in another office, the signaling
205 ANSWER NANS
cannot distinguish various circumstances of the called, therefore, reasons are
TIMES
classified into one type). It can be worked out by subtracting the answered calls
from the connected calls. (Note: Invisible to users)
ABANDON It refers to the times that the caller or the incoming trunk forward releases the call
206 BEFORE RING during the time from the determining of the call is an outgoing call, to the ringing of BRGABN
TIMES the called.
BLOCKED BY
Call loss due to the heavy load of CPU, which may further result in the overloading
to a certain extend
LOSS TIMES
FLOW CTRL
FWCTLC
208 CALL LOSS Call loss due to NM control with the high density of traffic
L
TIMES
LASTCHOICE
It is the number of route selection failures due to busy outgoing (bi-directional)
ROUTE
209 trunk circuits, that is, the times that the software fails to select outgoing LRUOFL
OVERFLOW
TIMES
210 CBSY
CALLED TOLL
BUSY TIMES
CALLED LOCAL
212 It refers to the times of having distinguished that the called is making a local call. CLB
BUSY TIMES
SEIZURE Traffic transmitted during the time from the seizing of the outgoing (bi-directional)
213 SERL
TRAFFIC trunk circuit to the completion of the call
ANSWER
TRAFFIC
MAINTENANCE It is the number of the outgoing (bi-directional) trunk circuits in the maintaining
217 MNTCIR
CIRCUIT NUM state.
CONNECTED
218 Number of connections/Number of occupancies (calculated on the background) CNTR (65,90)
RATIO
ANSWER
219 Number of answerings/Number of occupancies (calculated on the background) ANSR (52,72)
RATIO
3.1.11 ISDN Intra-office Traffic
3-14
Meaning: Gets the global basic data of ISDN calls belonging to this traffic flow
direction.
MML word: ISDNINT
Object: All ISDN subscriber frame lines (TLISUR)
Table 3-11 Measurement of the ISDN internal traffic
Entity Entity
No. threshold
CALL ATTEMPT It is the times that the called is found in the local office through the analysis
231 PEGS
TIMES of the number after the caller picks up the phone.
CALL
232 CONNECTED It refers to the number of successful call attempts (ringing). CNT
TIMES
supplementary services (Call Forwarding Unconditional, Call Forwarding
No Reply, Call Forwarding Busy, and so on), the number is counted if only
the call is answered.
It refers to the times of the location of the called to the local office through
analyzing the called number. However, the called cannot be located if the
INCOMPLETE
234 number is not complete. The number of incomplete calls includes the PDIMP
DIALLING TIMES
number of interval between dialing time-outs and that of releases during the
dialing.
PARTIAL
DIALLING It refers to the times that the user releases the call in dialing after the called
235 PDABN
ABANDON has been analyzed to be in the local office.
TIMES
PARTIAL
It refers to the number of interval time-outs in dialing after the called has
236 DIALLING PDTOU
been analyzed to be in the local office.
TIMEOUT TIMES
INVALID number or the call is barred, although the call is determined to be a local
237 INVADR
ADDRESS TIMES call after the user dials the correct office number. It includes the inability to
determine the called or dead number.
ABANDON
from the determining of the local call to the ringing of the called.
TIMES
239 NETBLCL
COMMON
RESOURCE CMRUAV
UNAVAIL CALL CL
LOSS TIMES
SYSTEM FAULT
TIMES
BLOCKED BY
LOSS TIMES
FLOW CTRL
TIMES
CALLED USER It refers to the number of unsuccessful call attempts because of the
244 LINE FAULT erroneous subscriber line. It includes the erroneous state, testing state and CLDFL
TIMES maintaining state of the called interface.
3-15
Entity Entity
No. threshold
245 CBSY
246 CTB
BUSY TIMES call.
247 CLB
BUSY TIMES call.
ABANDON
ringing.
TIMES
249 LTNANS
Traffic transmitted during the time from determining that the called is in the
SEIZURE
250 local office by analyzing the call originated locally to the completion of the SERL
TRAFFIC
call (including the failure or release during the call connection)
ANSWER Traffic in the flow direction of the internal call (local call) during the time
252 RERL
TRAFFIC from the answering to the completion of the call
254 CNTR (65,90)
RATIO background)
background)
3.1.12 ISDN Originating Outgoing Office Traffic
direction.
MML word: ISDNOROG
Object: All ISDN subscriber frame lines (TLISUR)
Table 3-12 Measurement of the ISDN originating outgoing traffic
Entity Entity
No. threshold
CALL ATTEMPT It refers to the number of outgoing call attempts through the analysis of the call
261 PEGS
TIMES originated locally.
262 BID TIMES circuits, that is, the times that the software selects outgoing (bi-directional) TKBID
trunk circuits.
It refers to the number of successful seizures of outgoing (bi-directional) trunk
TK SEIZURE
263 circuits. As for the SS7, it is the times of receiving the seizure ACK signal while TKSEIZ
TIMES
for the CAS, it is the times of sending the seizure signal.
CALL
264 CONNECTED CNT
TIMES
3-16
Entity Entity
No. threshold
CALL NO earlier releasing or other reasons. (Because the called is in another office, the
266 NANS
ANSWER TIMES signaling cannot distinguish various circumstances of the called, therefore,
reasons are classified into one type). It can be worked out by subtracting the
answered calls from the connected calls. (Note: Invisible to users)
INCOMPLETE determined because of incomplete number, although the number is judged to
267 PDIMP
DIALLING TIMES be an originated outgoing call, and the number of times that the office address
of the peer end is incomplete.
ABANDON
from determining the call to be an outgoing call, to the ringing of the called.
TIMES
NETWORK destination, the switching network cannot perform the connection and there is
269 NETBLCL
BLOCKING CALL no other channel available. It includes the number of failures of allocating the
LOSS TIMES network resource in a module and between modules.
COMMON
RESOURCE CMRUAV
UNAVAIL CALL CL
LOSS TIMES
SYSTEM FAULT
TIMES
BLOCKED BY
LOSS TIMES
FLOW CTRL
TIMES
LASTCHOICE
It is the number of route selection failures due to busy outgoing (bi-directional)
ROUTE
274 trunk circuits, that is, the times that the software fails to select outgoing LRUOFL
OVERFLOW
TIMES
275 CBSY
CALLED TOLL
BUSY TIMES
277 CLB
BUSY TIMES call.
SEIZURE Traffic transmitted during the time from judging the call is an outgoing call
278 SERL
TRAFFIC originated locally, to the completion of the call.
ANSWER
TRAFFIC
282 CNTR (65,90)
RATIO background)
background)
3.1.13 ISDN Incoming Office Terminating Traffic
direction.
3-17
MML word: ISDNITE
Object: All ISDN incoming and bi-directional circuits (TLISIBTK)
Table 3-13 Measurement of the ISDN incoming terminating traffic
Entity MML Entity

Entity name Meaning
No. word threshold
It is the times that the incoming (bi-directional) trunk circuits are seized and the
291 SEIZURE TIMES SEIZ
called is located to the local office through the analysis of the called number.
CALL
292 CONNECTED CNT
TIMES
It refers to the number of answered call attempts. As for various supplementary
293 ANSWER TIMES services (Call Forwarding Unconditional, Call Forwarding No Reply, Call ANS
Forwarding Busy, and so on), the number is counted if only the call is answered.
It refers to the times that the called is not determined because of incomplete
INCOMPLETE number, although the called is located to be a local subscriber through the
294 PDIMP
DIALLING TIMES analysis of the number received by the incoming (bi-directional) trunk. It
includes the releasing during dialing and the interval between dialing overtime.
It refers to the times that the number after the office number is a dead number or
INVALID the call is barred, although the called is judged as a local subscriber through the
295 INVADR
ADDRESS TIMES analysis of the number received by the incoming trunk. It includes the inability to
determine the called or the empty/dead number.
ABANDON It refers to the times that the caller forward releases the call during the time from
296 BEFORE RING the determining of the called is a local subscriber, through the analysis of the BRGABN
TIMES number received by the incoming trunk, to the ringing of the called.
NETWORK destination, the switching network cannot perform the connection and there is NETBLC
297
BLOCKING CALL no other channel available. It includes the number of failures of allocating the L
LOSS TIMES network resource in a module and between modules.
COMMON
RESOURCE CMRUAV
UNAVAIL CALL CL
LOSS TIMES
SYSTEM FAULT
SYSFLC
299 CALL LOSS Internal error of the switch
L
TIMES
BLOCKED BY
LOSS TIMES
FLOW CTRL
FWCTLC
301 CALL LOSS Call loss due to NM control with the high density of traffic
L
TIMES
303 CBSY
CALLED TOLL
BUSY TIMES
CALLED LOCAL
305 It refers to the times of having distinguished that the called is making a local call. CLB
BUSY TIMES
ABANDON
ringing.
TIMES
307 LTNANS
3-18
Entity MML Entity

Entity name Meaning
No. word threshold
Traffic transmitted during the time from determining the called is in the local
SEIZURE
308 office to the completion of the call when the call seizes the incoming SERL
TRAFFIC
(bi-directional) trunk circuit.
ANSWER
TRAFFIC
CONNECTED
312 Number of connections/Number of call attempts (calculated on the background) CNTR (65,90)
RATIO
313 ANSWER RATIO Number of answerings/Number of occupancies (calculated on the background) ANSR (52,72)
3.1.14 ISDN Transfer Traffic
direction.
MML word: ISDNTRN
Object: All ISDN incoming and bi-directional circuits (TLISIBTK)
Table 3-14 Measurement of the ISDN transit traffic
Entity Entity
No. threshold
TRANSFER CALL
It is the times that the call is judged to be an outgoing call after the incoming
321 TRNSEIZ
SEIZURE TIMES
trunk is seized.
322 OUTTK BID TIMES circuits, that is, the times that the software selects outgoing (bi-directional) OTKBID
trunk circuits.
It refers to the number of the successful seizures of outgoing (bi-directional)
OUTTK SEIZURE
323 trunk circuits. As for the SS7, it is the times of receiving the seizure ACK OTKSEIZ
TIMES
signal while for the CAS, it is the times of sending the seizure signal.
CALL CONNECTED It refers to the times of sending ringing to the called after the call has been
324 CNT
TIMES established within the network.
CALL NO ANSWER
326 the signaling cannot distinguish various circumstances of the called, NANS
TIMES
subtracting the answered calls from the connected calls. (Note: Invisible to
users)
determined because of incomplete number, although the number is judged
INCOMPLETE
327 to be an originated outgoing call, and the number of times that the office PDIMP
DIALLING TIMES
address of the peer end is incomplete. It includes the interval between dialing
overtime and the releasing during dialing.
ABANDON It refers to the times that the caller forward releases the call during the time
328 BEFORE RING from the determining of the call to be an outgoing call, through the analysis of BRGABN
TIMES the number received by the incoming trunk, to the ringing of the called.
3-19
Entity Entity
No. threshold
329 NETBLCL
COMMON
RESOURCE
UNAVAIL CALL
LOSS TIMES
SYSTEM FAULT
CALL LOSS TIMES
BLOCKED BY
TIMES
FLOW CTRL CALL
LOSS TIMES
LASTCHOICE It is the number of route selection failures due to busy outgoing
334 ROUTE (bi-directional) trunk circuits, that is, the times that the software fails to select LRUOFL
OVERFLOW TIMES
outgoing (bi-directional) trunk circuits.
335 CBSY
336 CTB
BUSY TIMES call.
CALLED LOCALIt refers to the times of having distinguished that the called is making a local
337 CLB
BUSY TIMES call.
Traffic transmitted during the time from judging the call is an outgoing call
originated from the incoming trunk, to the completion of the call.
342 CNTR (65,90)
RATIO background)
background)
3.1.15 Connecting Type Traffic
Meaning: Gets the basic data of the calls that are classified by the connection type
MML word: CT
Object: All connection types (CT), enumeration object

z Automatic Outgoing Toll call (TAO)
z Incoming Toll call (TI)
z Toll call Transferring (TT)
z Automatic Outgoing International call
z Incoming International call (II)
z International call Transferring (IT)
z Local office (LL)
z Outgoing call from Local Office (LOO)
z Incoming call to Local Office (LIT)
3-20
z Local Tandem (LT)

Table 3-15 Measurement of the connecting traffic
Entity Entity
No. threshold
CALL
It refers to the times that the connection type of the call originated locally is
2101 ATTEMPT PEGS
judged to be the corresponding one while the incoming trunk is seized.
TIMES
OUTTK
It refers to the times that the connection type of the call is judged to be the
2102 SEIZURE TKSEIZ
selected one while the outgoing/incoming trunk circuit is seized.
TIMES
CALL
2103 CONNECTED CNT
TIMES
ANSWER It refers to the times of entering the speaking state after the called answers
2104 ANS
TIMES while the connection type is the selected one.
PARTIAL
It refers to the times that the switch forcedly releases the call due to dialing
DIALLING
2105 overtime after the connection type of the call, originated locally or received PDTOU
TIMEOUT
from the incoming trunk, is judged to be the corresponding one.
TIMES
PARTIAL It refers to the times that the local subscriber releases or the incoming trunk
DIALLING forward releases the call due to incomplete number after the connection type
2106 PDABN
ABANDON of the call, originated locally or received from the incoming trunk, is judged to
TIMES be the corresponding one.
BARRED It is the times that the caller is barred after the connection type of the call is
2107 BAR
CALL TIMES judged to be the corresponding one.
ABANDON It is the times that the caller or the incoming trunk forward releases the call
2108 BEFORE RING after the connection type of the call is judged to be the corresponding one and BRGABN
TIMES before the called rings.
LOST CALL
OF
It is the times that the erroneous subscriber line or inability to activate occurs
2109 HARDWARE HRDRSN
after the judging of the connection type to be the selected one.
REASON
TIMES
LOST CALL
OF It is the times that the erroneous packet and Random Access Memory (RAM)
2110 SOFTWARE management occurs after the judging of the connection type to be the selected SFTRSN
REASON one.
TIMES
LOST CALL It is the number of the call attempts whose routing cannot be completed due to
OF the unavailability of idle speech paths after the judging of the connection type
2111 CIRCG
CONGESTION to be the selected one. It includes the intra-module and inter-module
TIMES congestion and the lack of time slots for the inter-module speech path.
LASTCHOICE It is the number of route selection failures when the connection type is the
ROUTE selected one due to busy outgoing (bi-directional) trunk circuits, that is, the
2112 LRUOFL
OVERFLOW times that the software fails to select outgoing (bi-directional) trunk circuits
TIMES when the connection type is the selected one.
SIGNALING
It refers to the times that the erroneous inter-office signaling and subscriber
2113 ERROR SIGER
signaling occurs when the connection type is the selected one.
TIMES
It refers to the number of unsuccessful call attempts because the called is
CALLED BUSY
2114 busy when the connection type is the selected one. The called is possibly CBSY
TIMES
making a toll call, a local call, and so on.
CALLED TOLL It refers to the times of having distinguished that the called is making a toll call
2115 CTB
BUSY TIMES when the connection type is the selected one.
CALLED
It refers to the times of having distinguished that the called is making a local
2116 LOCAL BUSY CLB
call.
TIMES
3-21
Entity Entity
No. threshold
ABANDON
It refers to the times that the local caller/incoming trunk releases the call while
the called is ringing.
TIMES
RINGED NO
It refers to the times that the switch forcedly releases the call due to no answer
2118 ANSWER LTNANS
from the called during the ringing.
TIMES
SEIZURE Traffic transmitted during the time from the trunk/subscriber line seized to the
2119 SERL
TRAFFIC call released
CONNECTED Traffic transmitted during the time from the called ringing to the call released
2121 CERL
TRAFFIC after the call has been established within the network
ANSWER Traffic transmitted during the time from the called entering the speaking state
2123 RERL
TRAFFIC to the call released
2125 CNTR (65,90)
RATIO background)
ANSWER Number of answerings/Number of call attempts (calculated on the
2126 ANSR (52,72)
RATIO background)
3.1.16 ISDN Connecting Type Traffic
Meaning: Gets the basic data of the ISDN calls that are classified by the connection
type.
MML word: ISDNCT
Object: All connection types (CT), enumeration object

z Automatic Outgoing Toll call (TAO)
z Incoming Toll call (TI)
z Toll call Transferring (TT)
z Automatic Outgoing International call
z Incoming International call (II)
z International call Transferring (IT)
z Local office (LL)
z Outgoing call from Local Office (LOO)
z Incoming call to Local Office (LIT)
z Local Tandem (LT)
Table 3-16 Measurement of the ISDN connecting traffic
Entity Entity
No. threshold
CALL ATTEMPT It refers to the times that the connection type of the call originated locally is
2151 PEGS
TIMES judged to be the corresponding one while the incoming trunk is seized.
OUTTK SEIZURE It refers to the times that the connection type of the call is judged to be the
2152 TKSEIZ
TIMES selected one while the outgoing/incoming trunk circuit is seized.
3-22
Entity Entity
No. threshold
CALL
2153 CONNECTED CNT
TIMES
It refers to the times of entering the speaking state after the called answers
while the connection type is the selected one.
PARTIAL It refers to the times that the switch forcedly releases the call due to dialing
2155 DIALLING overtime after the connection type of the call, originated locally or received PDTOU
TIMEOUT TIMES from the incoming trunk, is judged to be the corresponding one.
It refers to the times that the local subscriber releases or the incoming trunk
PARTIAL
forward releases the call due to incomplete number after the connection type
2156 DIALLING PDABN
of the call, originated locally or received from the incoming trunk, is judged to
ABANDON TIMES
be the corresponding one.
BARRED CALL It is the times that the caller is barred after the connection type of the call is
2157 BAR
TIMES judged to be the corresponding one.
ABANDON It is the times that the caller or the incoming trunk forward releases the call
2158 BEFORE RING after the connection type of the call is judged to be the corresponding one BRGABN
TIMES and before the called rings.
LOST CALL OF
It is the times that the erroneous subscriber line or inability to activate occurs
2159 HARDWARE HRDRSN
after the judging of the connection type to be the selected one.
REASON TIMES
LOST CALL OF
It is the times that the erroneous packet and RAM management occurs after
2160 SOFTWARE SFTRSN
the judging of the connection type to be the selected one.
REASON TIMES
It is the number of the call attempts whose routing cannot be completed due
LOST CALL OF
to the unavailability of idle speech paths after the judging of the connection
2161 CONGESTION CIRCG
type to be the selected one. It includes the intra-module and inter-module
TIMES
congestion and the lack of time slots for the inter-module speech path.
LASTCHOICE It is the number of route selection failures when the connection type is the
ROUTE selected one due to busy outgoing (bi-directional) trunk circuits, that is, the
2162 LRUOFL
OVERFLOW times that the software fails to select outgoing (bi-directional) trunk circuits
TIMES when the connection type is the selected one.
SIGNALING It refers to the times that the erroneous inter-office signaling and subscriber
2163 SIGER
ERROR TIMES signaling occurs when the connection type is the selected one.
CALLED BUSY
2164 busy when the connection type is the selected one. The called is possibly CBSY
TIMES
making a toll call, a local call, and so on.
2165 CTB
BUSY TIMES call when the connection type is the selected one.
2166 CLB
BUSY TIMES call.
ABANDON AFTER It refers to the times that the local caller/incoming trunk releases the call
2167 ARGABN
RING TIMES while the called is ringing.
2168 LTNANS
Traffic transmitted during the time from the trunk/subscriber line seized to the
call released
CONNECTED Traffic transmitted during the time from the called ringing to the call released
2171 CERL
TRAFFIC after the call has been established within the network
Traffic transmitted during the time from the called entering the speaking state
to the call released
2175 CNTR (65,90)
RATIO background)
background)
3-23
3.1.17 All Offices Sum Traffic
Meaning: It is the summary of all entities, reflecting the global running situation.
MML word: SUM
Table 3-17 Measurement of the total traffic of all offices
Entity
No.
991 ORIGINATING CALL TIMES Number of call attempts (General traffic statistics of the originating calls) PEGS
It is the times that the caller releases before dialing and that the interval for no
992 NO DIALLING TIMES NDG
dialing times out (Measurement of reasons).
It is the times that the interval between dialing times out, that the caller releases
INCOMPLETE DIALLING
993 the call during dialing, and that the caller does not dial for a long time PDIMP
TIMES
(Measurement of reasons).
It is the times that the called number is a vacant one. The number format may be
DIALLING VACANT CODE
994 invalid, the called number may be an unallocated number, modified or invalid, or VAC
TIMES
the toll prefix is wrong (Measurement of reasons).
ABANDON AFTER RING It is the times that the caller releases the call before ringing (Measurement of
995 ARGABN
TIMES failure reasons).
LONG TIME NO ANSWER It is the times that the called is not answered for a long time and no subscriber
996 LTNANS
TIMES answers for a long time (especially for ISDN) (Measurement of reasons).
It is the times that congestion occurs to the opposite office. It fails to check the
OPPSITE OFFICE
997 connection. There is no A1, no A3, no KD, or there are received messages with RMTCG
CONGESTION TIMES
unrecognizable parameters and the call fails (Measurement of reasons).
ORIGINATING CALL It is the times that the call is barred and NM is barred (Measurement of failure
998 BAR
BARRED TIMES reasons).
TERMINAL CALL BARRED
999 It is the times that the incoming call is barred (Measurement of failure reasons). CIBAR
TIMES
LOCAL CALL ATTEMPT
1000 Number of local call attempts (General measurement of the internal traffic) LPEGS
TIMES
It is the times that the local call is answered (General measurement of the
1001 LOCAL ANSWER TIMES LANS
internal traffic).
LOCAL CALLED BUSY It is the times that the local called is busy (General measurement of the internal
1002 LCBSY
TIMES traffic).
It refers to the times that the switch forcedly releases the local call due to no
LOCAL RINGED NO
1003 answer from the called during the ringing (General measurement of the internal LLTNANS
ANSWER TIMES
traffic).
1004 LOCAL CALL TRAFFIC Traffic of local calls (General measurement of the internal traffic) LSERL
ORIGINATING OUTGOING
1005 OFFICE CALL ATTEMPT Number of outgoing call attempts (General measurement of outgoing calls) OOPEGS
TIMES
LOCAL OUTGOING OFFICE It is the total number of outgoing call attempts originated locally and call attempts
1006 LOPEGS
CALL ATTEMPT TIMES originated by the local tandem.
NATIONAL TOLL CALL Number of call attempts (Connection type: automatic outgoing national toll call,
1007 NTPEGS
ATTEMPT TIMES semi-automatic outgoing national toll call, transferred national toll call)
INTERNATIONAL TOLL Number of call attempts (Connection type: automatic outgoing international call,
1008 ITPEGS
CALL ATTEMPT TIMES semi-automatic international call, transferred international call)
ORIGINATING OUTGOING It is the times that the outgoing trunk is seized (General measurement of
1009 OOSEIZ
OFFICE SEIZURE TIMES outgoing calls).
It is the times that the outgoing call is connected within the entire network
1010 OFFICE CALL OOCNT
(General measurement of outgoing calls).
CONNECTED TIMES
3-24
Entity
No.
ORIGINATING OUTGOING It is the times that the outgoing call is answered (General measurement of
1011 OOANS
OFFICE ANSWER TIMES outgoing calls).
LOCAL ORIGINATING
It is the times that the call originated locally is answered (Connection type:
1012 OUTGOING OFFICE LOANS
outgoing call originated locally, and the outgoing call from the local tandem).
ANSWER TIMES
It is the times that the national toll call is answered (Connection type: automatic
NATIONAL TOLL ANSWER
1013 outgoing national toll call, semi-automatic outgoing national toll call, transferred NTANS
TIMES
national toll call).
It is the times that the international call is answered (Connection type: automatic
INTERNATIONAL TOLL
1014 outgoing international call, semi-automatic international call, transferred ITANS
ANSWER TIMES
international call).
1015 OFFICE CALLED BUSY It is the times that the called is busy (General measurement of outgoing calls). OOCBSY
TIMES
ORIGINATING OUTGOING It refers to the times that the switch forcedly releases the outgoing call due to no
1016 OFFICE RINGED NO answer from the called during the ringing (General measurement of outgoing OORNANS
ANSWER TIMES calls).
Traffic transmitted when the outgoing trunk is seized (General measurement of
1017 OFFICE TK SEIZURE OOTKSERL
outgoing calls and the transit traffic).
TRAFFIC
Number of the seizures of the incoming trunk (General measurement of
1018 INTK SEIZURE TIMES ITKSEIZ
incoming calls)
INCOMING OFFICE Number of call attempts that the called is in the local office (General
1019 ITRMPEGS
TERMINAL CALL TIMES measurement of incoming calls)
INCOMING OFFICE
It is the times that the incoming call is answered (General measurement of
1020 TERMINAL CALL ANSWER ITRMANS
incoming calls).
TIMES
It is the times that the call is transferred (General measurement of transferred
1021 TRANSFER CALL TIMES TRNPEGS
calls).
TRANSFER OUTTK Number of the seizures of the outgoing trunk (General measurement of
1022 TOTKPEGS
SEIZURE TIMES transferred calls).
TRANSFER ANSWER It is the times that the transferred call is answered (General measurement of
1023 TRNANS
TIMES transferred calls).
INTERNATIONAL TRANSIT Number of the internatioanal transit call ITRT
1024
CALL TIMES
INTERNATIONAL Number of the international incoming call ICIT
1025
INCOMING CALL TIMES
INTERNATIONAL Number of the international outgoing call ICOT
1026
OUTGOING CALL TIMES
INTERNATIONAL TRANSIT Duration of the international transit call ITRTS
1027
CALL SEIZ TIME
INTERNATIONAL Duration of the international incoming call ICITS
1028
INCOMING CALL SEIZ TIME
INTERNATIONAL Duration of the international outgoing call ICOTS
1029 OUTGOING CALL SEIZ
TIME
TRANSFER SEIZURE Traffic of the occupancy(General measurement of the call transferring) TRNSERL
1030
TRAFFIC
1031 TERMINAL CALL TIMES Number of the call attempt(General measurement of the received traffic) TRMPEGS
TERMINAL CALL ANSWER Number of the answering(General measurement of the received traffic) TRMANS
1032
TIMES
TERMINAL CALL CALLED Number of the busy called(General measurement of the received traffic) TRMCBSY
1033
BUSY TIMES
TERMINAL CALL RINGED Number of not answering for a long time+releasing before ringing (General TRMNANS
1034
NO ANSWER TIMES measurement of the received traffic)
TERMINAL CALL SEIZURE Traffic of the occupancy(General measurement of the received traffic) TRMSERL
1035
TRAFFIC
1036 TERMINAL CALL ANSWER Traffic of the answering(General measurement of the received traffic) TRMRERL
TRAFFIC
3-25
Entity
No.
1037 OUTGOING OFFICE CALL Number of the call attempt(General measurement of the outgoing call) OPEGS
ATTEMPT TIMES
1038 OUTGOING OFFICE Number of the occupancy(General measurement of the outgoing call) OSEIZ
SEIZURE TIMES
1039 OUTGOING OFFICE CALL Number of the connection(General measurement of the outgoing call) OCNT
CONNECTED TIMES
1040 OUTGOING OFFICE Number of the answering(General measurement of the outgoing call) OANS
ANSWER TIMES
1041 OUTGOING OFFICE Traffic of the occupancy(General measurement of the outgoing call) OSERL
SEIZURE TRAFFIC
3.1.18 Failure Reason Traffic
Meaning: Counts the occurrences of every call failure reason.
MML word: FLRSN
Object: Reasons of all failed calls
Result type & other attributes: Long result
Table 3-18 Measurement of the failure reason traffic
Entity
No.
NS SET CONFLICT The cause code is sent when the supplementary service registered by the
371 NSSETCFT
TIMES subscriber conflicts with the registered service.
The cause code is sent when the subscriber succeeds in registering the
372 NS SET OK TIMES NSSETOK
supplementary service.
NS SET FAILURE The cause code is sent when the subscriber fails to register the supplementary
373 NSSETFL
TIMES service.
NS CANCEL OK The cause code is sent when the subscriber succeeds in cancelling the
374 NSCANOK
TIMES supplementary service.
NS CANCEL FAILURE The cause code is sent when the subscriber fails to cancel the registered
375 NSCANFL
The cause code is sent when the user releases the call after the switch verifies the
376 NS VERIFY OK TIMES NSTSTOK
registered supplementary service successfully.
NS VERIFY FAILURE The cause code is sent when the user releases the call after the switch fails to verify
377 NSTSTFL
TIMES the registered supplementary service.
The cause code is sent when the user releases the call after using the registered
378 NS USE OK TIMES NSUSOK
supplementary service successfully.
NS USE FAILURE The cause code is sent when the user releases the call after failing to use the
379 NSUSFL
TIMES registered supplementary service.
NS MCT USE OK The reason is used when the user gets related information after employing the
380 MCTOK
TIMES malicious call tracing service.
NS MCT USE The reason is used when the user fails to get related information after employing the
381 MCTFL
FAILURE TIMES malicious call tracing service.
NS ABSENT USER The reason is used when the connection of the call originated by the caller fails due
382 NSABS
TIMES to the Absent service set by the called.
NS NO DISTURB The reason is used when the connection of the call originated by the caller fails due
383 NSND
TIMES to the Do-not-disturb service set by the called.
3-26
Entity
No.
SWITCH EQUIPMENT The cause code is sent to indicate that its source switching equipment is in the
384 SEC
CONGESTION TIMES high-traffic period.
LONG TIME NO The cause code is sent when the call is released if the user cannot complete the
385 LTNDG
DIALLING TIMES dialing in the specified time.
LONG TIME NO The cause code is sent when the user provides the alarm indication instead of the
386 LTNANS
ANSWER TIMES connection indication during the specified period.
SYSTEM FAULT The call is released if the system performance declines after loss of messages,
387 SYSFL
TIMES internal error, message combination failure and so on.
REMOTE TEST OK
388 The cause code is sent when the self-check to the internal telephone is successful. RTSTOK
TIMES
LONG TIME NO INFO The cause code is sent when the call is released if the user cannot receive the news
389 LTNINF
TIMES needed in the specified period.
LONG TIME NO RING The cause code is sent when the call does not receive the prompting in the specified
390 LTNRG
TIMES period.
LONG TIME NO The cause code is sent when the call does not receive the releasing requirement in
391 LTNRLS
RELEASE TIMES the specified period.
INBAND SIGNAL
392 In-band signal INBSIG
TIMES
COCK FAILURE
393 Call is released when the continuity check fails. COCFL
TIMES
The cause code is sent when the number of retries exceeds the threshold because
EXCEED MAX
394 the switch fails to perform the connection due to the dual seizure in one process of EXREATP
REATTEMPT TIMES
the connection.
RELEASE BEFORE The cause code is sent while the caller is releasing the call before the call provides
395 BRGABN
RING TIMES the prompting information.
RELEASE BEFORE The cause code is sent while the caller is releasing the call after the call provides the
396 ARGABN
ANSWER TIMES alarm indication and before provides the connection indication.
CALL BARRING The cause code is sent when the call is released due to the prefix barring, NM
397 BAR
TIMES barring or other service implementation beyond the limitation.
SWITCH EQUIPMENT The cause code is sent when the call is released due to the prefix barring, NM
398 SEFL
FAULT TIMES barring or other service implementation beyond the limitation.
OPR DISCONNECT The cause code is sent when the operator succeeds in disconnecting a certain call
399 OPRDFOK
FORCELY OK TIMES forcefully.
OPR DISCONNECT
400 FORCELY FAILURE The cause code is sent when the operator fails to disconnect a certain call forcefully. OPRDFFL
TIMES
CALLED TOLL BUSY The cause code is sent when the call is released because the called is making a toll
401 CTB
TIMES call.
CALLED LOCAL BUSY The cause code is sent when the call is released because the called is making a
402 CLB
TIMES local call.
403 OWNED TIMES The cause code is sent when the call is released because of the insufficient balance. OWN
404 CODE PORT TIMES The cause code is sent when the call is released because of the number portability. CDPRT
CT0 ABNORMAL
405 The cause code is sent when the operator console is not running normally. CT0UNS
TIMES
NS RECORD OK
406 The cause code is sent when the recording to the specified time slot is successful. NSRECOK
TIMES
CREDIT ARREARAGE The cause code is sent when the call fails because of the insufficient balance in the
407 CRDOWN
TIMES credit card.
CALLIN BARRING The cause code is sent when the call is released because the called does not have
408 IBAR
TIMES the authority of receiving the incoming call.
409 HAVE NOA1 TIMES Not receiving A1, the indication to require the next bit NA1
410 HAVE NOA3 TIMES Not receiving A3, the indication to transfer to the B signal NA3
411 NO KD TIMES KD, the outlet service attribute, is not available NKD
412 NO KB TIMES Not receiving KB, the busy/idle indication of the peer end subscriber NKB
REMOTE
The cause code is sent when the call receives the backward signal A4 (indicating
413 EQUIPMENT REPMCG
the peer end congestion).
CONGESTION TIMES
414 CALL FAILURE TIMES The cause code is sent when the call is released due to unknown reason. CLFL
DUAL SEIZURE The cause code is sent when the call is released because the same trunk circuit is
415 DSEIZ
TIMES seized simultaneously by an outgoing call and a call from the peer end.
3-27
Entity
No.
It indicates that the call cannot reach the destination required by the caller because
416 INVALID CODE TIMES the called cannot be located according to the number or the number contains the INVCD
message not complying with the called.
REMOTE PASSWD
The user fails to modify the password of the other terminal by the call originated
417 UPDATE FAILURE RPSWUPFL
locally.
TIMES
REMOTE PASSWD The user succeeds in modifying the password of the other terminal by the call
418 RPSWUPOK
UPDATE OK TIMES originated locally.
REMOTE LOGIN CALL
The user succeeds in registering the forwarding service of the other terminal by
419 FORWARDING OK RREGCFOK
originating a call locally.
TIMES
REMOTE LOGIN CALL
The user fails to register the forwarding service of the other terminal by originating a
420 FORWARDING RREGCFFL
call locally.
FAILURE TIMES
REMOTE CANCEL
The user succeeds in canceling the forwarding service of the other terminal by
421 CALL FORWARDING RCANCFOK
originating a call locally.
OK TIMES
REMOTE CANCEL
The user fails to cancel the forwarding service of the other terminal by originating a
422 CALL FORWARDING RCANCFFL
call locally.
FAILURE TIMES
CALLED OWNED
423 The cause code is sent when the call fails because the called ows charge. CLDOWN
TIMES
The cause code is sent when the call is released because the user inputs an
PASSWORD ERROR
424 erroneous password in setting, modifying or canceling the password or deploying PSWER
TIMES
the service that needs a password.
The cause code is sent when the call is released because the number of call
TRANSFER CALL
425 forwardings exceeds the threshold in one connection or the essential information of TRNBAR
BARRED TIMES
the forwarding service is missing.
MODULE
The cause code is sent when the module, to which messages will be sent (for
426 INACCESSIBLE MNARV
example, the called is found in the module), is not in the normal state.
TIMES
NETMANAGER The cause code is sent when the call fails for having deployed the nine types of NM
427 NMNBAR
BARRED TIMES commands.
USER QUEUE The cause code is sent when the call cannot be inserted into the call queue which is
428 QFL
FAILURE TIMES full.
GROUP QUEUE The cause code is sent while the call cannot be inserted into the group call queue
429 GRPQFL
FAILURE TIMES because the call queue is full.
TIMEOUT IN QUEUE The cause code is sent when the call is released because of the response overtime
430 QTOU
TIMES after the call enters the above two queues.
The cause code is sent when the CPU occupancy rate exceeds the set congestion
431 CPU OVERLAP TIMES CPUOL
threshold or overloading threshold.
The cause code is sent when the Connection Request (CR) resource is not sufficient
432 NO CR TIMES for the call received or originated at the subscriber side (contrary to the Central NCR
Communication dataBase (CCB) at the network side).
The cause code is sent when the CCB resource is not sufficient for the call received
433 NO CCB TIMES NCCB
or originated at the network side (contrary to the CR at the subscriber side).
434 NO HW TIMES The cause code is sent when the time slots are not sufficient. NHW
The cause code is sent when the number receiver cannot provide sufficient
435 NO DTMF TIMES NDTMF
resource.
The cause code is sent when the Multi-Frequency (MF) register cannot provide
436 NO MFC TIMES NMFC
sufficient resource.
The cause code is sent when the Dual Tone Transmit/Receive (DTR) resource is not
437 NO DTR TIMES NDTR
sufficient.
438 NO CT0 TIMES The cause code is sent when the computer operators are not enough. NCT0
439 NO IPATH TIMES The cause code is sent when the inter-module circuits are totally busy. NIPH
The cause code is sent when the conference telephones (for the three-party service)
440 NO CONFO TIMES NCONF
are not sufficient.
The cause code is sent when the V5 subscriber has not applied for the channel to
441 NO V5B TIMES NV5B
the switch.
3-28
Entity
No.
NO DIALING The cause code is sent when the user hangs on not dialing (listening to the dial tone)
442 NDGABN
ABANDON TIMES after off-hook.
NO DIALING The cause code is sent for the overtime when the user hangs on not dialing
443 NDGTOU
TIMEOUT TIMES (listening to the dial tone) after off-hook.
PARTIAL DIALLING
444 The cause code is sent when the caller hangs on before the dialing times out. PDABN
ABANDON TIMES
PARTIAL DIALLING The cause code is sent when the dialing times out before the completion of the
445 PDTOU
TIMEOUT TIMES dialing.
SIGNALING ERROR
446 The cause code is sent when the SS7 or CAS goes wrong. SIGER
TIMES
MONEY NOT The cause code is sent when the call is released, because the campus prepaid card
447 CRDNMNY
ENOUGH TIMES does not have enough balance.
The cause code is sent when the call is barred, because the caller or called is on the
448 BW LIST BARRING BWLB
Black/White list.
449 CLI NOT MATCH The cause code is sent when the Calling Line Identification (CLI) does not match. CLINM
450 UNKNOWN TIMES The cause code is sent while the switch initializes releasing reasons. UKNWRSN
UNALLOCATED It indicates that the call cannot reach the destination required by the caller because
451 UALCCD
CODE TIMES the number is not allocated though the number format is valid (not fixed).
It indicates that the equipment sending the reason has received a request from an
NO ROUTE TO
indirect call transferred by the special unrecognized switching network. The reason
SPECIFIED
452 that the equipment cannot recognize the network is that the switching network does NRUTOSI
INTERNETWORK
not exist or provide any service for the equipment. It is the network that decides
TIMES
whether to support the reason.
It indicates that the call cannot reach the called because the network the call passes
NO ROUTE TO
453 through does not provide the service for the required terminal. It is the network that NRUTOTE
TERMINAL TIMES
decides whether to support the reason.
SND PRIVATE TONE It indicates that the reason that the call cannot reach the called is because the caller
454 SPRVTONE
TIMES returns the special signal tone.
ERROR DIALLING It indicates that the transferring prefix of the called number contains error
455 ERLNGPFX
TOLL PREFIX TIMES information.
ROUTE
It indicates that the transmitting entity does not accept the channel with the new
456 UNACCEPTABLE RUUAPT
identification in the call.
TIMES
CALL TRANSMIT ON
It indicates that the call has been transmitted to the user together with other similar
457 ESTABLISHED CHEDRE
calls in the established channel.
ROUTE TIMES
It indicates that the call is being cleared because one of the users concerned
NORMAL CALL
458 requires the release. However, the network will not transmit the cause code in NORCLR
CLEAR TIMES
normal cases.
The cause code is sent when the called gives an indication of not receiving another
459 USER BUSY TIMES BSY
call.
NO RESPONSE The cause code is sent when the called does not respond to the established call in
460 NRSP
TIMES the specified time with the promoting or connection indication.
NO ACKNOWLEDGE The cause code is sent when the user provides the prompting indication but the
461 NACK
TIMES connection indication in the specified time.
The cause code is sent when the equipment transmitting the reason does not want
CALL REJECTED
462 to receive the call, though it can. The network generates the reason. It indicates that REJ
TIMES
the call is cleared due to the limitation of the supplementary service.
The cause code is sent to the caller when the called number cannot be allocated
CODE CHANGED again. The new called number may be included in the diagnostic field as an optional
463 CDCHD
TIMES item. If the network does not support the capability, the cause code "129,
unallocated number" will be sent out.
CLEAR UNSELECTED
464 It indicates that the user cannot get the incoming call. CLRUSL
USER TIMES
The reason indicates that the call cannot reach the receiving end specified by the
TERMINAL ERROR
465 caller because the interface of the receiving end does not work properly, that is, the TEER
TIMES
signaling message cannot be transmitted to the remote user.
INVALID CODE It indicates that the call cannot reach the called because of the erroneous format of
466 INVCDFMT
FORMAT TIMES the called number or the incomplete number.
3-29
Entity
No.
FACILITY REJECTED The cause code is sent when the network cannot provide the performance required
467 FACREJ
TIMES by the user.
RESPONSE TO
The reason of generating the STATUS message is that the STATUS ENQUIRY
468 STATUS ENQUIRY RSPSE
message firstly received contains the message.
TIMES
The reason is used to report a normal event when there are no other applicable
469 NORMAL TIMES NOR
reasons of normal type.
NO AVAILABLE
470 It indicates that there is no appropriate circuit/channel to process the call. NCIR
CIRCUIT TIMES
NETWORK ERROR
471 It indicates that there is no appropriate circuit/channel to process the call. NETER
TIMES
TEMPORARY ERROR It indicates that the network does not work properly and this state will not be very
472 TMPER
TIMES long. For example, the user will almost surely originate/receive another call.
SWITCH FACILITY It indicates that the switching equipment generating the reason is in the high-traffic
473 EPMCG
CONGESTION TIMES service period.
It indicates that the network cannot submit the accessing information to the remote
ACCESS INFO LOSS
474 user, such as the user-user information, low-level compatibility, high-level AIL
TIMES
compatibility or sub-address information.
NO ROUTE OR
The cause code is sent when the interface on the other side cannot provide the
475 CIRCUIT APPLIED NRUCIR
circuit or channel required by the entity.
AVAILABLE TIMES
NO RESOURCE The reason is used to report a resource unavailable event only when there are no
476 NRSC
AVAILABLE TIMES other applicable reasons of resource unavailable.
NO SUITABLE
It is used to report that the service quality defined in Recommendation X.213 is not
477 SERVICE QUALITY NSSQUA
available (for example, cannot support the handling capacity or transfer delay).
TIMES
FACILITY APPLIED It indicates that the network cannot provide the required supplementary service
478 NO PRESERVED because the user has not completed the management procedures necessary for FACNPV
TIMES enjoying the service.
CUG INCOMING CALL
It indicates that the caller is a member of the CUG that is capable of receiving the
479 NOT ALLOWED CUGUALW
incoming call. However, that member is not permitted to receive the incoming call.
TIMES
BEARER CAPABILITY
It indicates that the user is not permitted to employ the bearer capability that has
480 NOT PERMITTED BCUNP
been deployed by the equipment generating the reason.
TIMES
NO BEARER
CAPABLILITY It indicates that there is no bearer capability available though the equipment
481 NBC
AVAILABLE NOW generating the reason has deployed it.
TIMES
NO SUITABLE
SERVICE OR It is used to report that there is no applicable service or optional project when there
482 NSS
OPTIONAL PROJECT are no other applicable reasons employed for it.
TIMES
BEARER CAPABILITY It indicates that the equipment sending the reason does not support the required
483 BCNLO
NOT LAYOUT TIMES bearer capability.
ROUTE TYPE NOT It indicates that the equipment sending the reason does not support the channel
484 RTNLO
LAYOUT TIMES type.
FACILITY APPLIED It indicates that the equipment sending the reason does not support the required
485 FACNLO
NOT LAYOUT TIMES supplementary service.
LIMITED DIGITAL
It indicates that the caller has applied for an unlimited bearer service. However, the
486 INFO BEARER LTDDIBC
equipment sending the message can only support the limited bearer service.
CAPABILITY TIMES
SERVICE OR
It is used to report a service or optional project unimplemented event when there is
487 OPTIONAL PROJECT SOPNLO
no other applicable reasons employed for it.
NOT LAYOUT TIMES
INVALID CALL It indicates that the message received by the equipment sending the reason
488 INVCR
REFERENCE TIMES contains the call reference not employed by the existing user-network interface.
ROUTE IDENTIFIED It indicates that the equipment sending the reason message receives a call requiring
489 RUNEXT
NOT EXIST TIMES to use the inactivated channel at the interface.
3-30
Entity
No.
SUSPENDED CALL
It indicates that the call ID in trying to restore the call is different from that in the
490 DIFFER FROM CALL SUSC
pause.
ID TIMES
It indicates that the network receives a pause requirement that contains a call ID that
CALL IDENTIFIER IS
491 has been used by a paused call of those possibly restored within a certain interface IDUS
USING TIMES
range (including no call ID).
It indicates that the network receives a call restoring requirement that contains call
NO SUSPENDED
492 ID information unit that does not indicate any paused call of those possibly restored NSUSC
CALL TIMES
within a certain interface range.
CALL FOR It indicates that the network receives a call restoring requirement indicating that a
493 IDENTIFIER paused call indicated by the call ID information unit has been cleared in the pause IDCLR
CLEARED TIMES (network transmission overtime or cleared by the remote user).
CALLED NOT CUG It indicates that the called of an incoming CUG call is not a member of a specific
494 CLDNOCUG
TIMES CUG or the caller is only a common user.
It indicates that the equipment sending the reason message has received a call
TERMINAL
set-up requirement. However, the call has low-level compatibility, high-level
495 UNCOMPATABLE TEUCPT
compatibility or other compatibility (for example, transmission rate), which are
TIMES
inapplicable.
INVALID TRANSMIT
It indicates that the switching network ID is not in the valid format defined in the
496 NETWORK INVTNL
appendix.
SELECTION TIMES
It is used to report an invalid event only when other reasons of the invalid message
497 INVALID MSG TIMES INVMSG
type are employed.
NECESSARY INFO It indicates that the equipment sending the reason has received a message with a
498 ELEMENT LOSS missing information unit that should be available before the processing of the NCSIELST
TIMES message.
MSG TYPE NOT It indicates that the equipment sending the reason has received a message whose
499 EXIST OR NOT type is not recognizable because the type is not defined or is defined but the MSGNEXT
LAYOUT TIMES equipment sending the message has not implemented it.
It indicates that the equipment sending the reason has received a message that
MSG STATUS ERROR
should have not been received in the call state, indicated by the program. Or the
500 OR MSG ERROR MSGSTAER
equipment sending the reason receives a STATUS message that indicates
TIMES
incompatible call state.
It indicates that the equipment sending the reason has received a message
INFO ELEMENT NOT containing an unrecognizable information unit because the information unit ID has
501 EXIST OR NOT not been defined or the equipment sending the reason has not implemented it IEUEXT
LAYOUT TIMES though it is defined. The information unit is not necessary for the equipment
processing the unit.
INVALID INFO It indicates that the equipment sending the reason has received an implemented
502 ELEMENT CONTENT information unit but it does not implement the coding of one or multiple fields in the INVIE
TIMES unit.
MSG UNFIT TO CALL
503 It indicates that a message not in compliance with the state is received. MSGUFT
STATUS TIMES
TIMER RECOVERY It indicates that a program related to the error processing program in
504 TRCV
OF TIME OUT TIMES Recommendation Q.931 starts due to the timer overtime.
PARAMETER NOT It indicates that the equipment sending the reason has discarded an unrecognizable
505 PARANEXT
EXIST TIMES parameter.
ORDINARY USER It indicates that the idle circuit is reserved for the high-priority user instead of the
506 ORNCG
CONGESTION TIMES common user. The cause code is sent on the receipt of A9.
PROTOCOL ERROR
507 It reports the protocol error event. PTLER
TIMES
508 BUTT TIMES The failure reason is invalid because it is beyond the threshold. BUTT
It indicates that the network is connecting to another network that provides no
509 INTERWORK TIMES reason for the network action. Therefore, the accurate reason for sending the INTWRK
message is not available.
3-31
3.2 Measurement of Bearer Traffic
3.2.1 Office Direction Incoming Office Traffic
Meaning: It conducts statistic analysis of the traffic carried by and running of the
incoming trunk circuits in respective office directions. It provides reference for
maintenance & NM and also facilitates specific tracing for calls from the opposite
office to the local office. The whole course of a call can be traced with joint effort of
multiple offices.
MML word: OFDINC
Object: Incoming direction (INCOFD)
Table 3-19 Measurement of the incoming traffic in an office direction
Entity Entity
No. threshold
It refers to the number of seizure attempts of incoming
2202 CALL CONNECTED TIMES Number of the called ringing CNT
2203 ANSWER TIMES Number of the called picking up the phone and answering ANS
TRANSFER ANSWER TIMES Number of the outgoing call via the local tandem and the called TRNANS
2204
answering
ANSWER OVER PERIOD Number of the called over period times ANSOVP
2205 (0,65535)
TIMES
LOST CALL OF EMPTY CODE Number of the failed call due to the empty code of called EMCODE
2206 (0,65535)
TIMES subscriber
LOST CALL OF INVALID Number of the failed call due to invalid address INVAR
2207 (0,65535)
ADDRESS TIMES
LOST CALL OF ABANDON Number of the called ringing BRGABN
2208 (0,65535)
BEFORE RING TIMES
LOST CALL OF ABANDON Number of the caller forward releasing in the ringing ARGABN
2209 (0,65535)
AFTER RING TIMES
2210 CALLED BUSY TIMES Number of the failed call due to called subscriber in busy CBSY (0,65535)
LOST CALL OF RINGED NO Number of the forced releasing by the SPCE due to the called not LTNANS
2211 (0,65535)
ANSWER TIMES answer in the ringing
2212 LOST CALL OF RIGHTS TIMES Number of the failed call due to insufficient right CDFR (0,65535)
CALLED TERMINAL Number of the failed call due to terminal uncompatible TERUNC
2213 (0,65535)
UNCOMPATABLE TIMES
CALLED TERMINAL ERROR Number of the failed call due to terminal error TERERR
2214 (0,65535)
TIMES
LOST CALL OF INT CONGEST Number of the failed call due to internal system congest INTCGCL
2215 (0,65535)
TIMES
SWITCHING EQUIPMENT Number of the failed call due to switch system congest SEC
2216 (0,65535)
CONGEST TIMES
CALL OF CIRCUITGRP Number of the failed call due to circuit group congest CGC
2217 (0,65535)
CONGEST TIMES
CALL FAILED OF OTHER Number of the failed call due to other reasons OTHLC
2218 (0,65535)
REASON TIMES
2219 CALLED TOLL BUSY TIMES Number of the failed call due to toll busy CTB (0,65535)
2220 CALLED LOCAL BUSY TIMES Number of the failed call due to local busy CLB (0,65535)
3-32
Entity Entity
No. threshold
INTERNATIONAL TRANSIT Number of the international transit call INTTRAN
2221
TIMES
INCOMING INTERNATIONAL Number of the incoming international call ININT
2222
CALL TIMES
OUTGOING INTERNATIONAL Number of the outgoing international call OUTINT
2223
CALL TIMES
INSTALLED CIRCUIT NUM Number of the circuit available/installed (calculated on the INSCIR
2224
background)
2225 AVAIL CIRCUIT NUM Number of the available incoming trunk circuits AVACIR
AVAIL BLOCKED CIRCUIT Number of the blocked circuits among available incoming trunk ABLCIR
2226
NUM circuits
UNAVAIL BLOCKED CIRCUIT Number of the blocked circuits among unavailable incoming trunk UBLCIR
2227
NUM circuits
2228 OTHER CIRCUIT NUM Number of the circuits with other state OTHCIR
2229 INTK AVAIL RATIO Average ratio of available incoming trunk circuit ITKAVAR (50,100)
INTK BLOCKED CIRCUIT Average ratio of blocked circuit among unavailable incoming trunk UNAVAR
2230 (0,50)
RATIO circuit
CALL CONNECTED RATIO Number of the connection/Number of the occupancy (calculated CNTR
2231 (60,100)
on the background)
ANSWER RATIO Number of the answering/Number of the occupancy (calculated ANSR
2232 (40,100)
on the background)
BIDIRECTION SEIZEURE Traffic of bidirection during call BISERL
2233 (0,65535)
TRAFFIC
SEIZURE TRAFFIC Traffic transmitted during the time from seizing the incoming trunk
2235 SERL (0,65535)
(bi-directional) to the trunk releasing
Traffic transmitted on per line during the time from seizing the SERLPL
2237 SEIZURE TRAFFIC PER LINE (0,65535)
incoming trunk (bi-directional) to the trunk releasing
Traffic transmitted during the time from the called ringing to the CERL
2238 CONNECTED TRAFFIC (0,65535)
call releasing after the call has been established over the net
Traffic transmitted during the time from the called ringing to the
2240 ANSWER TRAFFIC RERL (0,65535)
call releasing after the call has been established over the net
It is the average seizure duration from the seizing to the releasing
AVERAGE SEIZURE of the incoming trunk within the statistic period. It equals the
2242 AST (0,65535)
DURATION product of the seizure traffic and statistic period (seconds) divided
by the number of call attempts.
3.2.2 Office Direction Outgoing Office Traffic
Meaning: It conducts statistic analysis of the traffic carried by and state of outgoing
trunk circuits in respective office directions. The statistics can be the reference for
maintenance and network management.
MML word: OFDOG
Object: Outgoing office direction (OGOFD)
3-33
Table 3-20 Measurement of the outgoing traffic in an office direction
Entity Entity
No. threshold
2246 BID TIMES BID
trunk circuits of the office direction.
TRANSFER BID TIMES Number of the busy outgoing trunk circuit while the switching office is
2247 TRNBID
performing the transferring connection
It is the number of successful seizures of outgoing (bi-directional) trunk
circuits.
TRANSFER SEIZURE It is the number of successful seizures of outgoing trunk circuits in the
2249 TRNSEIZ
TIMES local office by the call originated outside to another office.
CALL CONNECTED It refers to the times of sending ringing to the called after the call has
2250 CNT
TIMES been established within the network.
2251 ANSWER TIMES It refers to the times that the answering signal is received. ANS
2252 OVERFLOW TIMES OFL (0,65535)
(bi-directional) trunk circuits in the office direction.
ANSWER OVER Number of the outgoing call via the local tandem and the called ANSOVP
2253 (0,65535)
PERIOD TIMES answering
LOST CALL OF EMPTY Number of the failed call due to the empty code of called subscriber EMCODE
2254 (0,65535)
CODE TIMES
LOST CALL OF INVALID Number of the failed call due to invalid address INVAR
2255 (0,65535)
ADDRESS TIMES
LOST CALL OF Number of the called ringing BRGABN
2256 ABANDON BEFORE (0,65535)
RING TIMES
LOST CALL OF Number of the caller forward releasing in the ringing ARGABN
2257 ABANDON AFTER (0,65535)
RING TIMES
2258 CALLED BUSY TIMES Number of the failed call due to called subscriber in busy CBSY (0,65535)
LOST CALL OF RINGED Number of the forced releasing by the SPCE due to the called not answer LTNANS
2259 (0,65535)
NO ANSWER TIMES in the ringing
PEER OFFICE
2260 UNDIERCT ROUTE It refers to the times that the direct routing fails for calls to the peer office. NDRT (0,65535)
TIMES
PEER OFFICE NO It refers to the times that there is no nesting code for calls to the peer
2261 NOFCMD (0,65535)
NESTING TIMES office.
PEER END
2262 It is the times that the congestion signal is received from the peer end. POFCCG (0,65535)
CONGESTION TIMES
SWITCHING Number of the failed call due to switch system congest SEC
2263 EQUIPMENT CONGEST (0,65535)
TIMES
CALL OF CIRCUITGRP Number of the failed call due to circuitgrp congest CGC
2264 (0,65535)
CONGEST TIMES
CALL FAILED OF Number of the failed call due to other reasons OTHLC
2265 OTHER REASON (0,65535)
TIMES
2266 CALL DUAL SEIZ TIMES Number of the bidirection conflicted call DSEIZ (0,65535)
2267 CALL SUCCESS TIMES All number of the successful call SUCC (0,65535)
2268 CALL RETRY TIMES All number of the tk_retry call RETRY (0,65535)
CANCEL
It refers to the number of the selected alternative routes kept away from
2269 ALTERNATIVE ROUTE ARF (0,65535)
ART or the times of the overflowing ARF.
TIMES
CANCEL DIRECTIONAL Number of the directional routing from ART or the number of the
2270 DRF (0,65535)
ROUTE TIMES overflowing ARF
2271 ROUTE JUMP TIMES It refers to the number of call attempts transferred by the pre-set hopping. RUJMP (0,65535)
It is the number of call attempts selecting the temporary alternative
2272 TEMP AMB TIMES TMPAMB (0,65535)
routes.
AFFECTED TIMES BY Number of the calling times effected by indirection route temporarily
2273 OTHER NET OTHNA (0,65535)
ADMINISTRATE
3-34
Entity Entity
No. threshold
CALLED TOLL BUSY It refers to the times of having distinguished that the called is making a toll
2274 CTB (0,65535)
TIMES call.
CALLED LOCAL BUSY It refers to the times of having distinguished that the called is making a
2275 CLB (0,65535)
TIMES local call.
INTERNATIONAL Number of the international transit call INTTRAN
2276
TRANSIT TIMES
INCOMING Number of the incoming international call ININT
2277 INTERNATIONAL CALL
TIMES
OUTGOING Number of the outgoing international call OUTINT
2278 INTERNATIONAL CALL
TIMES
INSTALLED CIRCUIT It is the number of outgoing (bi-directional) trunk circuits installed in the
2279 INSCIR
NUM office direction at the end of the measurement period.
It is the average number (integer) of circuits available among the
2280 AVAIL CIRCUIT NUM outgoing (bi-directional) trunk circuits in the office direction within the AVACIR
measurement period.
AVAIL BLOCKED Number of the blocked circuits among available incoming trunk circuits ABLCIR
2281
CIRCUIT NUM
UNAVAIL BLOCKED Number of the blocked circuits among unavailable incoming trunk circuits UBLCIR
2282
CIRCUIT NUM
2283 OTHER CIRCUIT NUM Number of the circuits with other state OTHCIR
It is the ratio of available outgoing circuits to installed circuits (calculated
2284 OUTTK AVAIL RATIO OTKAVAR (50, 100)
on the background).
OUTTK BLOCKED Number of the blocked circuits/Number of the installed circuits
2285 UNAVAR (0,50)
CIRCUIT RATIO
It is the ratio of seizure times to seizure attempts (calculated on the
2286 SEIZURE RATIO SEIZR (80, 100)
background).
It is the ratio of call set-up times to seizure attempts (calculated on the
2287 CONNECTED RATIO CNTR (60, 100)
background).
It is the ratio of answer times to seizure attempts (calculated on the
2288 ANSWER RATIO ANSR (40, 100)
background).
BOTHWAY CIRCUIT Traffic transmitted during the time from the incoming call seizing the
2289 BISERL (0,65535)
SEIZURE TRAFFIC upstream bi-directional trunk to the call releasing
Traffic transmitted during the time from the seizure to the release of the
2291 SEIZURE TRAFFIC SERL (0,65535)
outgoing (bi-directional) trunk
SEIZURE TRAFFIC PER Traffic transmitted on per line during the time from seizing the incoming
2293 SERLPL (0,65535)
LINE trunk (bi-directional) to the trunk releasing
Traffic transmitted during the time from the called ringing to the call
2294 CONNECTED TRAFFIC CERL (0,65535)
released after the call has been established within the network
Traffic transmitted during the time from the answering to the completion
of the call
It is the average seizure duration from the seizing to the releasing of the
AVERAGE SEIZURE outgoing trunk within the statistic period. It equals the product of the
2298 AST (0,65535)
DURATION seizure traffic and statistic period (seconds) divided by the number of call
attempts.
3.2.3 TKGRP Incoming Office Traffic
Meaning: It conducts statistic analysis of the calls carried by incoming circuits of each
trunk group.
MML word: TKGINC
3-35
Object: Incoming or bi-directional trunk group (IBTKG)
Table 3-21 Measurement of the TKGRP incoming traffic
Entity Entity
No. threshold
2306 SEIZURE TIMES It refers to the number of seizures of incoming (bi-directional) trunk circuits. SEIZ
CALL
2307 CONNECTED It refers to the times that the called rings. CNT
TIMES
2308 ANSWER TIMES It refers to the times that the called answers. ANS
TRANSFER CALL Number of the succeeded seizing of the outgoing circuit in the office by the call TRNANS
2309
ANSWER TIMES originated out of the office to other offices
ANSWER OVER Number of the called over period times ANSOVP
2310 (0,65535)
PERIOD
CALLED EMPTY Number of the outgoing call via the local tandem while the called answering EMCODE
2311 (0,65535)
CODE TIMES
CALED INVAILD Including the intra-module or inter-module resource congestion, unavailable INVAR
ADDRESS TIMES public resource, system error, hardware error, software error and voice channel
2312 congestion and so on. Because all errors above have nothing to do with the (0,65535)
specific office direction, no further explanation of these reasons will be given
below
ABANDON Duration from the starting of the congestion to the completion of the congestion. BRGABN
2313 BEFORE RING When all resource are seized, the congestion starts; and when the first idle (0,65535)
TIMES equipment appears, the congestion finishes.
ABANDON
2314 AFTER RING It refers to the times that the caller releases the call while the called is ringing. ARGABN (0,65535)
TIMES
2315 CBSY (0,65535)
RINGE NO It refers to the times that the switch forcedly releases the call due to no answer
2316 LTNANS (0,65535)
BEARER Number of the failed call due to insufficient capability BERERR
2317 CAPABILITY (0,65535)
ERROR TIMES
CALLED FAIL OF Number of the failed call due to insufficient right CDFR
2318 (0,65535)
RIGHTS TIMES
TERMINAL Number of the failed call due to terminal incompatible TERUNC
2319 UNCOMPATABLE (0,65535)
TIMES
DESTIONATION Number of the failed call due to terminal error TERERR
2320 OUT OF ORDER (0,65535)
TIMES
LOST CALLS OF Number of the failed call due to internal system congest INTCOG
2321 INT CONGEST (0,65535)
TIMES
SWITCHING Number of the failed call due to switch system congest SECOG
2322 EQUIPMENT (0,65535)
CONGES TIMES
LOST CALLS OF Number of the failed call due to circuitgrp congest CGCOG
2323 CIRCUITGRP (0,65535)
CONGEST TIMES
LOST CALLS OF Number of the failed call due to other reasons COR
2324 OTHER (0,65535)
REASONS
CALLED TOLL Number of the called making the toll call and being busy CTB
2325 (0,65535)
BUSY
CALLED LOCAL Number of the called making the local call and being busy CLB
2326 (0,65535)
BUSY
3-36
Entity Entity
No. threshold
CALLED SPECIAL Number of the called giving special voice CST
2327
TONE
CALLED Number of the called number changed NBC
2328 NUMBER
CHANGED
CALLED Number of the called rejected CRJ
2329
REJECTED
INTERNATIONAL Number of the international transit call ITRT
2330 TRANSIT CALL
TIMES
2331 INCOMING CALL
TIMES
2332 OUTGOING CALL
TIMES
INTERNATIONAL Duration of the international transit call ITRTS
2333 TRANSIT CALL
SEIZ TIME
2334 INCOMING CALL
SEIZ TIME
2335 OUTGOING CALL
SEIZ TIME
INSTALLED Number of the incoming trunk circuit (including the bi-directional trunk) installed in INSCIR
2336
CIRCUIT NUM that office direction at the end of the measurement period
AVAIL CIRCUIT It is the average number (integer) of circuits available among the incoming
2337 AVACIR
NUM (bi-directional) trunk circuits in the office direction within the measurement period.
AVAIL BLOCKED Number of the blocked circuits among available incoming trunk circuits ABLCIR
2338
CIRCUIT NUM
UNAVAIL Number of the blocked circuits among unavailable incoming trunk circuits UBLCIR
2339 BLOCKED
CIRCUIT NUM
OTHER CIRCUIT Number of the circuits with other state OTHC
2340
NUM
INTK AVAIL It is the ratio of available incoming circuits to installed circuits (calculated on the
2341 ITKAVAR (50, 100)
RATIO background). The lower and upper entity threshold is 50 and 65535 respectively.
BLOCKED It is the ratio of blocked circuits to installed circuits (calculated on the
2342 BLKR (65, 70)
CIRCUIT RATIO background).
CONNECTED It is the ratio of call set-up times to seizure attempts (calculated on the
2343 CNTR (65, 90)
RATIO background).
2344 ANSWER RATIO It is the ratio of answer times to seizure attempts (calculated on the background). ANSR (52, 72)
BIDIRECTION TK
Traffic transmitted during the time from the incoming call seizing the bi-directional
2345 SEIZURE BISERL (0,65535)
trunk to the call releasing
TRAFFIC
SEIZURE Traffic transmitted during the time from the seizure to the release of the incoming
2347 SERL (0,65535)
TRAFFIC (bi-directional) trunk
SEIZ USAGE PER Traffic transmitted on per line during the time from seizing the incoming trunk
2349 SERLPL (0,65535)
LINE (bi-directional) to the trunk releasing
CONNECTED Traffic transmitted during the time from the called ringing to the call released after
2350 CERL (0,65535)
TRAFFIC the call has been established within the network
ANSWER
2352 Traffic transmitted during the time from the answering to the completion of the call RERL (0,65535)
TRAFFIC
AVERAGE It is the average seizure duration from the seizing to the releasing of the incoming
2354 SEIZURE trunk within the statistic period. It equals the product of the seizure traffic and AST (0,65535)
DURATION statistic period (seconds) divided by the number of call attempts.
3-37
3.2.4 TKGRP Outgoing Office Traffic
Meaning: It conducts statistic analysis of the calls carried by outgoing circuits of each
trunk group.
MML word: TKGOG
Object: Outgoing or bi-directional trunk group (OBTKG)
Table 3-22 Measurement of the TKGRP outgoing traffic
Entity Entity
No. threshold
2361 BID TIMES BID
trunk circuits of the office direction by the software.
It is the number of seizure attempts of outgoing trunk circuits when the
2362 TRANSFER BID TIMES TRNBID
office transfers the call.
2363 OVERFLOW TIMES OFL
(bi-directional) trunk circuits in the office direction.
It is the number of successful seizures of outgoing (bi-directional) trunk
circuits.
TRANSFER SEIZURE It is the number of successful seizures of outgoing trunk circuits in the
2365 TRNSEIZ
TIMES local office by the call originated outside to another office.
CALL CONNECTED It refers to the times of sending ringing to the called after the call has
2366 CNT
TIMES been established within the network.
ANS OVER PERIOD Number of the called over period times ANSOVP
2368 (0,65535)
TIMES
EMPTY CODE TIMES Number of the outgoing call via the local tandem while the called EMCODE
2369 (0,65535)
answering
INVALID ADDRESS Including the intra-module or inter-module resource congestion, INVAR
TIMES unavailable public resource, system error, hardware error, software error
2370 and voice channel congestion and so on. Because all errors above have (0,65535)
nothing to do with the specific office direction, no further explanation of
these reasons will be given below
ABANDON BEFORE Duration from the starting of the congestion to the completion of the BRGABN
2371 RING TIMES congestion. When all resource are seized, the congestion starts; and (0,65535)
when the first idle equipment appears, the congestion finishes.
ABANDON AFTER RING It refers to the times that the caller releases the call while the called is
2372 ARGABN (0,65535)
TIMES ringing.
2373 CALLED BUSY TIMES CBSY (0,65535)
busy. The called is possibly making a toll call, a local call, and so on.
RINGED NO ANSWER It refers to the times that the switch forcedly releases the call due to no
2374 LTNANS (0,65535)
TIMES answer from the called during the ringing.
BEARER CAPABILITY Number of the failed call due to insufficient capability
2375 BERERR (0,65535)
ERROR TIMES
TRUNK CIRCUIT
2376 It is the number of failed calls due to unmatched trunk circuit type. DNMA (0,65535)
MISMATCHED TIMES
PEER END
2377 It is the times that the congestion signal is received from the peer end. POFCCG (0,65535)
CONGESTION TIMES
SWITCHING Number of the failed call due to switch system congest SEC
2378 EQUIPMENT CONGEST (0,65535)
TIMES
3-38
Entity Entity
No. threshold
LOST CALLS OF Number of the failed call due to circuitgrp congest CGC
2379 CIRCUITGRP CONGEST (0,65535)
TIMES
LOST CALLS OF OTHER Number of the failed call due to other reasons OTHLC
2380 (0,65535)
REASONS
2381 NM BARRING FLUENCE Number of the failed call due to network barring fluence NBF (0,65535)
2382 SUCCESS Number of the successful call SUCC (0,65535)
CALLED TOLL BUSY It refers to the times of having distinguished that the called is making a toll
2383 CTB (0,65535)
TIMES call.
CALLED LOCAL BUSY It refers to the times of having distinguished that the called is making a
2384 CLB (0,65535)
TIMES local call.
2385 CALLED SPECIAL TONE Number of the called giving special voice CST (0,65535)
CALLED NUMBER Number of the called number changed NBC
2386 (0,65535)
CHANGED
2387 CALLED REJECTED Number of the called rejected CRJ (0,65535)
DESTIONATION OUT OF Number of the failed call due to terminal error TERERR
2388
ORDER TIMES
INTERNATIONAL Number of the international transit call ITRT
2389
TRANSIT CALL TIMES
2390
INCOMING CALL TIMES
2391
OUTGOING CALL TIMES
INTERNATIONAL Duration of the international transit call ITRTS
2392 TRANSIT CALL SEIZ
TIME
2393 INCOMING CALL SEIZ
TIME
2394 OUTGOING CALL SEIZ
TIME
2395 DUAL SEIZURE TIMES It refers to the number of dual seizure of the bi-directional circuit. DSEIZ
2396 CALL RETRY TIMES Number of the retrying call RETRY
INSTALLED CIRCUIT It is the number of outgoing (bi-directional) trunk circuits installed in the
2397 INSCIR
NUM office direction at the end of the measurement period.
It is the average number (integer) of circuits available among the
2398 AVAIL CIRCUIT NUM outgoing (bi-directional) trunk circuits in the office direction within the AVACIR
measurement period.
AVAIL BLOCKED Average of the blocked circuit among available in the bidirection trunk ABLCIR
2399
CIRCUITS circuit
UNAVAIL BLOCKED Average of the blocked circuit among unavailable in the bidirection trunk UBLCIR
2400
CIRCUITS circuit
2401 OTHER CIRCUITS Number of the circuits with other state OTHCIR
It is the ratio of available outgoing circuits to installed circuits (calculated
2402 OUTTK RATIO on the background). The lower and upper entity threshold is 50 and OTKAVAR (50, 60)
65535 respectively.
BLOCKED CIRCUIT It is the ratio of blocked circuits to installed circuits (calculated on the
2403 BLKR (50, 60)
RATIO background).
It is the ratio of seizure times to seizure attempts (calculated on the
background).
It is the ratio of call set-up times to seizure attempts (calculated on the
background).
It is the ratio of answer times to seizure attempts (calculated on the
background).
BOTHWAY CIRCUIT Traffic transmitted during the time from the outgoing call seizing the
2407 BISERL (0,65535)
SEIZURE TRAFFIC bi-directional trunk to the call releasing
Traffic transmitted during the time from the seizure to the release of the
2409 SEIZURE TRAFFIC SERL (0,65535)
outgoing (bi-directional) trunk
3-39
Entity Entity
No. threshold
SEIZURE TRAFFIC PER Traffic transmitted on per line during the time from seizing bi-directional
2411 SERLPL (0,65535)
LINE to the trunk releasing
Traffic transmitted during the time from the answering to the completion
of the call
It is the average seizure duration from the seizing to the releasing of the
AVERAGE SEIZURE outgoing trunk within the statistic period. It equals the product of the
2416 AST (0,65535)
DURATION seizure traffic and statistic period (seconds) divided by the number of call
attempts.
3.2.5 Destination Traffic
Meaning: It conducts statistic analysis of a specific destination. The statistics can be

used as reference data for NM and maintenance. In addition, it helps users to find the
causes of low connection ratio of the destination code. It enhances the network
management control capability during the network congestion, for more efficient use
of the network resource.
MML word: DEST
Object: Destination (DEST)
Table 3-23 Measurement of the destination traffic
Entity Entity
No. threshold
It is the number of call attempts to a certain destination (including the
2426 CALL ATTEMPT TIMES PEGS
calls originated and transferred locally).
2427 CALL SEIZ TIMES Number of the call seizure OUT_TK to a certain destination OTKSEIZ
It refers to the times of sending ringing to the called after the call has
2428 CALL CONNECTED TIMES CNT
been established within the network.
ANS OVER PERIOD Number of the releasing in dialing after judging the call to be the one ANSOVP
2430 (0,65535)
to the destination code by analyzing the called number.
INVALID ADDRESS Number of the interval of rest interval overtime after judging the call INVAR
2431 (0,65535)
to be the one to the destination code by analyzing the called number.
It refers to the times that the caller forward releases the call during
ABANDON BEFORE RING
2432 the time from the determining of the called to be the destination BRGABN (0,65535)
TIMES
code, to the ringing of the called.
2433 ABANDON AFTER RING Number of the caller forward releasing in the ringing ARGABN (0,65535)
2434 VACANT NUMBER Number of the failed call due to called subscriber not exist VAC (0,65535)
2435 FAIL OF RIGHTS Number of the failed call due to calling subscriber insufficient right CRFR (0,65535)
2436 CALLED BUSY Number of the failed call due to called subscriber in busy CBSY (0,65535)
2437 RINGED NO ANS Number of the failed due to no answer LTNANS (0,65535)
2438 TERMINAL ERROR Number of the failed call due to terminal error TERERR (0,65535)
TERMINAL Number of the failed call due to terminal incompatible TERUNC
2439 (0,65535)
UNCOMPATABLE
3-40
Entity Entity
No. threshold
2440 CALLED FAIL OF RIGHTS Number of the failed call due to called subscriber insufficient right CDFR (0,65535)
It is the number of failed calls due to the lack of the backward A1
2441 A1 ABSENT TIMES while the switch employes the CAS for the calls to the destination NA1 (0,65535)
code.
It is the number of failed calls due to the lack of the backward A3
2442 A3 ABSENT TIMES while the switch employes the CAS for the calls to the destination NA3 (0,65535)
code.
KD ABSENT TIMES Number of the failed call due to lacking of the forward KD while NKD
2443 employing the associated signaling for the call to the destination (0,65535)
code.
KB ABSENT TIMES Number of the failed call due to lacking of the backward KB while NKB
2444 employing the associated signaling for the call to the destination (0,65535)
code.
OTHER INTEROFFICE It is the number of other failure reasons due to the failed signaling
2445 OTHSIGER (0,65535)
SIGNALING ERROR TIMES matching for the calls to the destination code.
DISTANT OFFICE Number of the failed due to destination in congestion DOCOG
2446 (0,65535)
CONGEST
LOST CALLS OF INT Number of the failed due to local office in congestion INTCGCL
2447 (0,65535)
CONGEST
SWITCHING EQUIPMENT Number of the failed due to switch system in congestion SEC
2448 (0,65535)
CONGEST
CALLS OF CIRCUITGRP Number of the failed due to circuit group in congestion CGC
2449 (0,65535)
CONGEST
2450 SYSTEM FAULTS Number of the failed due to system in fault SYSFLT (0,65535)
CALL AFFECTED BY CODE It is the number of calls affected by the NM procedures of blocking
2451 CDBLCL (0,65535)
BLOCKED TIMES the numbers.
CALL AFFECTED BY CALL It is the number of calls affected by the NM procedures of call interval
2452 GAPCTLCL (0,65535)
GAP CTRL TIMES control.
CALL AFFECTED BY It is the number of calls affected by the NM procedures of recording
2453 RECINFCL (0,65535)
RECORD INFORM TIMES notification.
LOST CALLS OF OTHER Number of the failed due to other reason
2454 OTRSN (0,65535)
REASONS
It is the number of call attempts after the failure of seizing the
2455 TK RETRY TIMES RETRY (0,65535)
outgoing trunk circuits.
AFFECTED BY TEMP Number of the failed due to effected by temp route TMPRT
2456 (0,65535)
ROUTE
AFFECTED BY OTHER NM Number of the failed due to effected by other NM action NMACT
2457 (0,65535)
ACTION
It is the times that the call fails due to unsuccessful route selection &
2458 CONGESTION TIMES no idle resource available (including the intra-office congestion, CG (0,65535)
circuit group congestion and out-of-office congestion).
It refers to the times of having distinguished that the called is making
2459 CALLED TOLL BUSY TIMES CTB (0,65535)
a toll call.
CALLED LOCAL BUSY It refers to the times of having distinguished that the called is making
2460 CLB (0,65535)
TIMES a local call.
It refers to the times that the called answers within 10 seconds after
2461 ANSWER IN 10S TIMES ANSIN10
the call connection.
It refers to the times that the called answers 10 seconds later after
2462 ANSWER OUT 10S TIMES ANSOUT10
the call connection.
It is the ratio of seizure times to call attempts (calculated on the
background).
It is the ratio of call set-up times to call attempts (calculated on the
background).
It is the ratio of answer times to call attempts (calculated on the
background)
Traffic transmitted in the period from the call seizing the outgoing
2466 SEIZURE TRAFFIC trunk corresponding to the destination code, or from the call seizing SERL (0,65535)
the local called subscriber, to the call releasing.
3-41
Entity Entity
No. threshold
Traffic transmitted during the time from the answering to the
completion of the call
It is the average seizure duration from the seizing to the releasing of
AVERAGE SEIZURE the trunk at the destination within the statistic period. It equals the
2472 AST (0,65535)
DURATION product of the seizure traffic and statistic period (seconds) divided by
the number of call attempts.
3.2.6 Destination Distribution Traffic
Meaning: It conducts statistic analysis of the traffic from a specific office direction to a
specific destination code.
MML word: DESTDISP
Object: Office direction, destination place or code, or outgoing trunk group

z Office direction (OFD) and destination place (DEST)
z Office direction (OFD) and destination code (CD)
z Trunk group (TKG) and destination place (DEST)
z Trunk group (TKG) and destination code (CD)
Result type & other attributes: Short result. Sample measurement can be employed
according to the sample rate.
Table 3-24 Measurement of the destination-distributed traffic
Entity MML
Entity name Meaning
No. word
It is the number of seizure attempts of the trunk circuits in the office direction by the
7001 BID TIMES BID
software with the prerequisite of the destination code being the specified one.
It is the number of successful seizures of trunk circuits in the office direction with the
prerequisite of the destination code being the specified one.
CALL CONNECTED It is the times that the call is connected with the prerequisite of the destination code
7003 CNT
TIMES being the specified one.
It is the times that the call is answered with the prerequisite of the destination code
being the specified one.
Traffic transmitted during the time from judging the destination code in the office
direction is the one specified, to releasing the call.
Traffic transmitted during the time from answering to releasing the call with the
prerequisite of the destination code being the specified one
It is the average number (integer) of circuits available among the outgoing
7007 AVAIL CIRCUIT NUM (bi-directional) trunk circuits in the office direction/trunk group within the measurement AVACIR
period.
INSTALLED CIRCUIT It is the number of trunk circuits (including bi-directional circuits) installed in the office
7008 INSCIR
NUM direction/circuit group at the end of the measurement period.
3-42
3.2.7 Single User Traffic
Meaning: It conducts statistic analysis of the originating traffic and terminating traffic
of a single user.
MML word: UR
Object: Certain user, subscriber frame internal code (USN), subscriber frame external
code (SN), subscriber frame port (URPSN).
Table 3-25 Measurement of a single user's traffic
Entity
No.
ORIGINATING CALL ATTEMPT
6001 It refers to the number of calls originated by the user. ORPEGS
TIMES
It refers to the times that the call process works out that the called user is
6002 TERMINAL CALL TIMES TEPEGS
the user.
ORIGINATING CALL It refers to the number of calls originated by the user and answered with the
6003 ORCNT
CONNECTED TIMES ring back tone.
TERMINAL CALL CONNECTED
6004 It refers to the times that calls, received by the user, are connected. TECNT
TIMES
ORIGINATING CALL ANSWER
6005 It refers to the times that the calls originated by the user are answered. ORANS
TIMES
TERMINAL CALL ANSWER
6006 It refers to the times that the user answers calls. TEANS
TIMES
TERMINAL CALL CALLED
6007 It refers to the times that the user is called but he is busy. TECBSY
BUSY TIMES
TERMINAL CALL RINGED NO It refers to the times that the call is released due to the ringing overtime
6008 TELTNANS
ANSWER TIMES when the user is called.
6009 ORIGINATING CALL TRAFFIC Traffic originated by the user ORERL
6011 TERMINAL CALL TRAFFIC Traffic received by the user TEERL
3.2.8 User Line GRP Traffic
Meaning: It conducts statistic analysis for subscribers whose positions are physically
related (usually logically related as well), to manage the number allocation (balance
the traffic) and learn how switching resources are utilized.
MML word: URUNT
Object: Certain user group

z Subscriber frame (SH)
z SM/SPM module (SM)
3-43
Table 3-26 Measurement of a subscriber group
Entity
No.
ORIGINATING CALL ATTEMPT
2476 It refers to the number of calls originated by the subscribers in the group. ORPEGS
TIMES
TERMINAL CALL ATTEMPT
2477 It is the number of calls received by the subscribers in the group. TEPEGS
TIMES
ORIGINATING CALL SEIZURE It is the number of call attempts originated by the intra-group subscribers
2478 ORSEIZ
TIMES and allocated with time slots.
TERMINAL CALL SEIZURE It is the number of call attempts, which have seized the intra-group
2479 TESEIZ
TIMES subscriber lines.
ORIGINATING CALL It refers to the number of calls originated by the intra-group subscribers and
2480 ORCNT
CONNECTED TIMES answered with the ring back tone.
TERMINAL CALL CONNECTED It refers to the times that calls, received by the intra-group subscribers, are
2481 TECNT
TIMES connected.
ORIGINATING CALL ANSWER It refers to the times that the calls originated by the intra-group subscribers
2482 ORANS
TIMES are answered.
2483 It refers to the times that the intra-group subscribers answer calls. TEANS
TIMES
TERMINAL CALL BLOCKED It refers to the times that the congestion occurs to the calls received by the
2484 TEBL
TIMES intra-group subscribers.
TERMINAL CALL USER LINE It refers to the times that the intra-group subscribers are called but they are
2485 TECBSY
BUSY TIMES busy.
TERMINAL CALL RINGED NO It refers to the times that the intra-group subscribers do not answer the calls
2486 TELTNANS
ANSWER TIMES for a long time.
It is the number of the subscriber lines whose numbers have been allocated
2487 CODED USER LINE NUM CDUR
in the statistic subscriber group.
It is the number of the normal subscribers in the statistic subscriber group. It
2488 AVAIL USER LINE NUM AVAUR
is the sum of the three items below.
It is the number of available Data Communication Network (DCN) subscriber
2489 AVAIL USER LINE DCN NUM AVADCN
lines.
2490 AVAIL USER LINE ST NUM It is the number of available Subscriber Terminals (ST). AVAST
2491 AVAIL USER LINE DSL NUM It is the number of available Digital Subscriber Lines (DSL). AVADSL
2492 ORIGINATING CALL TRAFFIC Traffic originated by the intra-group subscribers ORERL
2494 TERMINAL CALL TRAFFIC Traffic received by the intra-group subscribers TEERL
ORIGINATING CALL AVERAGE Traffic of the originating calls / Number of the originated calls * statistic
2496 ORAST
SEIZURE DURATION period
TERMINAL CALL AVERAGE Traffic of the originating calls / Number of the originated calls * statistic
2497 TEAST
SEIZURE DURATION period
3.2.9 PABXGRP Traffic
Meaning: It conducts the statistic analysis of the traffic of each subscriber cyclic
hunting group (ISDN cyclic hunting group and hybrid are included).
MML word: PABX
Object: Certain PBX group (PABX)
3-44
Table 3-27 Measurement of the PABXGRP traffic
Entity
No.
ORIGINATING CALL It is the number of the calls originated by the subscribers in the cyclic hunting
2501 ORPEGS
ATTEMPT TIMES group.
TERMINAL CALL ATTEMPT It is the number of the call attempts made to the subscribers in the cyclic hunting
2502 TEPEGS
TIMES group.
TOTAL CALL ATTEMPT
2503 It is the sum of the originated and received call attempts of a cyclic hunting group. TLPEGS
TIMES
ORIGINATING CALL It is the number of call attempts that the caller of the PBX cyclic hunting group is
2504 ORSEIZ
SEIZURE TIMES allocated with the Dual Tone Multi Frequency (DTMF), CCB, CR, and so on.
TERMINAL CALL SEIZURE It is the number of call attempts that the called of the PBX cyclic hunting group is
2505 TESEIZ
TIMES allocated with the CCB, CR and so on.
ORIGINATING CALL It is the number of connected calls originated by the subscribers in the cyclic
2506 ORCNT
CONNECTED TIMES hunting group.
TERMINAL CALL It is the times that calls, received by the subscribers in the cyclic hunting group,
2507 TECNT
CONNECTED TIMES are connected.
ORIGINATING CALL It refers to the times that the calls, originated by the subscribers in the cyclic
2508 ORANS
ANSWER TIMES hunting group, are answered.
2509 It refers to the times that the subscribers in the cyclic hunting group answer calls. TEANS
TIMES
TERMINAL CALL CALLED It refers to the times that the subscribers in the cyclic hunting group are busy
2510 TECBSY
BUSY TIMES when they are called.
TERMINAL CALL RINGED It refers to the times of ringing overtime when the subscribers in the cyclic hunting
2511 TELTNANS
NO ANSWER TIMES group are called.
CONGESTION CALL LOSS Number of the call loss due to the busy continuous selection CGCL
2512
TIMES
CONGESTION DURATION Sum of the duration from the continuous selection group being full to the first CGT
2513
continuous selection group available
2515 OPEN CIRCUIT NUM It is the number of circuits contained in the cyclic hunting group. OPNCIR
It is the number of circuits in the cyclic hunting group, which are not in the error
2516 AVAIL CIRCUIT NUM AVACIR
state, maintaining state or blocked.
ORIGINATING CALL Traffic transmitted during the time from the call originated by the subscribers in
2517 ORERL
TRAFFIC the cyclic hunting group to the completion of the call
Traffic transmitted during the time from the call received by the subscribers in the
2519 TERMINAL CALL TRAFFIC TEERL
cyclic hunting group to the completion of the call
ORIGINATING CALL
2521 Traffic of answering the originating calls ORRERL
ANSWER TRAFFIC
2523 Traffic of answering the received calls TERERL
TRAFFIC
3.2.10 Centrex Intra-group Traffic
Meaning: It conducts statistic analysis of the traffic of intra-group calls made by

subscribers in a specific Centrex group. The intra-group call refers to the call without
dialing any out-group prefix, or the long number being a member of the group
although the out-group prefix is dialed.
MML word: CTXINT
Object: A certain Centrex group (CTX)
3-45
Table 3-28 Measurement of the Centrex internal traffic
Entity MML
Entity name Meaning
No. word
It is the number of call attempts with no out-group prefix dialed or the long
number dialed.
INCOMING CALL ANSWER It is the times that Centrex subscribers answer the calls made by the
2552 IANS
TIMES intra-group subscribers.
TRANSFER CALL ANSWER It refers to the number of the transferred calls made by the intra-group
2553 TRNANS
TIMES subscribers.
It refers to the number of the intercepted calls made by the intra-group
2554 CALL PICKUP ANSWER TIMES PKPANS
subscribers.
2555 CALLED BUSY TIMES It refers to the number of failed intra-group calls because the called is busy. CBSY
It refers to the times of ringing overtime when the Centrex subscribers are
2556 RINGED NO ANSWER TIMES LTNANS
called.
2557 INTERNAL CALL TRAFFIC traffic of intra-group calls made by subscribers in a specific Centrex group INTERL
2559 CONNECTED TRAFFIC Traffic of the transferred intra-group calls CERL
2561 ANSWER TRAFFIC Traffic of the answered intra-group calls RERL
3.2.11 Centrex Extra-group Traffic
Meaning: It conducts statistic analysis of the traffic of the calls made to the
subscribers of a specific Centrex group from outside. That is, the called is a member
of the group and the caller is not.
MML word: CTXOTS
Table 3-29 Measurement of the Centrex extra-group traffic
Entity MML
Entity name Meaning
No. word
It is the number of call attempts made by the extra-group subscribers to
the Centrex subscribers.
It is the times that the Centrex subscribers answer calls from outside of
2602 INCOMING CALL ANSWER TIMES IANS
the group.
It is the number of the transferred calls from outside by the Centrex
2603 TRANSFER CALL ANSWER TIMES TRNANS
subscribers.
It is the number of the intercepted calls from outside by the Centrex
2604 CALL PICKUP ANSWER TIMES PKPANS
subscribers.
Traffic of the calls originated by the extra-group subscribers to the
2605 CALLIN TRAFFIC IERL
Centrex subscribers.
3.2.12 Centrex Outgoing Group Traffic
3-46
Meaning: It conducts statistic analysis of the traffic of the Centrex outgoing calls
placed by the subscribers in a specific Centrex group, which seize the trunk.
MML word: CTXTK
Table 3-30 Measurement of the Centrex outgoing traffic
Entity
No.
2651 OUTGOING GRP CALL TIMES It is the times that Centrex subscribers make outgoing calls. OUTC
It is the times that the call, originated by the Centrex subscriber, seizes the
2652 TK SEIZURE TIMES local trunk after it is judged to be an outgoing call (Note: Seizing here SEIZ
means the seizure by the software).
It is the times that the call, originated by the Centrex subscriber, fails to
2653 TK BUSY TIMES seize the local outgoing trunk with the cause of it being busy, after the call TKBSY
is judged to be an outgoing call.
2654 OUTGOING GRP CALL RAFFIC Traffic of the outgoing call from the intra-group subscriber OERL
Traffic of the calls successfully seizing the local trunk after they are judged
2656 TK SEIZURE TRAFFIC SERL
to be outgoing calls that are originated by the Centrex subscribers
3.2.13 Supplementary Service Traffic
Meaning: It conducts statistic analysis of the registration, cancellation and verification

of a specific or all supplementary services by all subscribers.
MML word: NS
Object: Certain supplementary service, one or some of supplementary services (NS),

all supplementary services
z Abbreviated dialing
z Hotline service (HL)
z Wake-up/Alarm service
z Absent service (ABS)
z Do-Not-Disturb/No-Disturb service
z Call out restriction/Outgoing Call Barred (OCB)
z Malicious Call Tracing (MCT)
z Registered Call on Busy
z Call Forwarding Unconditional (CFU)
z Call Forwarding Busy (CFB)
z Call Forwarding No Reply (CFNR)
z Call Waiting (CW)
z Calling back on Busy (CB)
3-47
z Three-Party service (3PTY)

z Conference calling (CONF)
z Designated Pick-up (CP)
z Call Forwarding (CF)
z Calling Line Identification Presentation (CLIP)
z Calling Line Identification Restriction (CLIR)
z Connected Line Identification Restriction (COLR)
z Destination Number Barred (DNB)
z Secretary Station service (SS)
z Secretary Service (SSVC)
z Forced Release by Operator/Operator Disconnect (OPDIS)
z Package Service (PSVC)
z Instant Hot Line (IHL)
z Operator Monitoring/Supervising
z Activating Call Forwarding Table (ACFT)
z Co-group pickup/Pick-up in the Group (PIG)
z Remotely-set Call Forwarding Unconditional (RCFU)
z Remotely-set Call Forwarding Busy (RCFB)
z Remotely-set Call Forwarding No Reply (RCFNR)
z Modify Password (MPASS)
z Operator Insert/Interception
z Call Forwarding to Mail Box on Busy
z Call Forwarding to Mail Box on No Reply
z Ascending Voltage Message Waiting Notification
z Cancel all registered supplementary services
z CLIP temporary reservation
z CLIR temporary reservation
z Operator Login
z Remove operator attribute
z Play
z Record
z PIN Call
z Outgoing prompt
z Inquiry
z Collect call
Table 3-31 Measurement of the supplementary service traffic
Entity MML
Entity name Meaning
No. word
It refers to the times that the specified supplementary service is successfully
2701 NS REGISTER OK TIMES REGOK
registered during the statistic period.
3-48
Entity MML
Entity name Meaning
No. word
It refers to the number of failed registrations of the specified supplementary
2702 NS REGISTER FAILURE TIMES REGFL
service during the statistic period.
2703 NS CANCEL OK TIMES CANOK
cancelled during the statistic period.
It refers to the number of the failed cancellations of the specified supplementary
2704 NS CANCEL FAILURE TIMES CANFL
2705 NS TEST SUCCESS TIMES TSTOK
verified during the statistic period.
It refers to the number of the failed verifications of the specified supplementary
2706 NS TEST FAILURE TIMES TSTFL
It refers to the times that the employment service is used during the statistic
2707 NS USED TIMES US
period.
It refers to the number of the succeeded and failed registrations of the specified
2708 NS REGISTED TIMES REG
supplementary service during the statistic period.
It refers to the number of the succeeded and failed cancellations of the specified
2709 NS CANCEL TIMES CAN
It refers to the number of the succeeded and failed verifications of the specified
2710 NS TEST TIMES TST
3.2.14 Supplementary Service Centrex Traffic
Meaning: It conducts statistic analysis of the registration, cancellation and verification

of a specific or all supplementary services in a specific Centrex group.
MML word: CTXNS
Object: A certain Centrex group (CTX) and a specific or all supplementary services
(NS). The supplementary services are the same enumeration objects as in the
measure unit 30.
Table 3-32 Measurement of the supplementary service traffic in a Centrex group
Entity MML
Entity name Meaning
No. word
7051 REGISTER OK TIMES REGOK
It refers to the number of failed registrations of the specified supplementary service
7052 REGISTER FAILURE TIMES REGFL
during the statistic period.
7053 CANCEL OK TIMES CANOK
It refers to the number of the failed cancellations of the specified supplementary
7054 CANCEL FAILURE TIMES CANFL
It refers to the times that the specified supplementary service is successfully verified
7055 TEST OK TIMES TSTOK
It refers to the number of the failed verifications of the specified supplementary
7056 TEST FAILURE TIMES TSTFL
7057 USED TIMES It refers to the times that the employment service is used during the statistic period. US
7058 REGISTED TIMES REG
3-49
Entity MML
Entity name Meaning
No. word
7059 CANCEL TIMES CAN
7060 TEST TIMES TST
3.2.15 ISDN Bearer Traffic
Meaning: It conducts statistic analysis of the traffic of respective ISDN bearer services
of all ISDN subscribers.
MML word: ISDNB
Object: Certain ISDN bear service

1) ISDN types
z Local ISDN (LISDN)
z V5 ISDN (V5ISDN)
2) Bearer services
z Speech service (SPEECH)
z Audio information service 1 (AUDIO1)
z Audio information service 2 (AUDIO2)
z Digital information service 1 (DIGITAL1)
Table 3-33 Measurement of the ISDN bearer traffic
Entity
No.
ORIGINATING CALL It is the number of call attempts with the bearer service employed by the ISDN
2751 ORPEGS
ATTEMPT TIMES subscriber, measured at the caller side.
TERMINAL CALL ATTEMPT It is the number of call attempts with the bearer service employed by the ISDN
2752 TEPEGS
TIMES subscriber, measured at the called side.
TERMINAL CALL CALLED
2753 It is the times that the called is busy with the bearer service employed. CBSY
BUSY TIMES
ORIGINATING CALL It is the number of the connected calls with the bearer service employed by the
2754 ORCNT
CONNECTED TIMES ISDN subscriber, measured at the caller side.
TERMINAL CALL It is the number of the connected calls with the bearer service employed by the
2755 TECNT
CONNECTED TIMES ISDN subscriber, measured at the called side.
ORIGINATING CALL It is the number of the answered calls with the bearer service employed by the
2756 ORANS
ANSWER TIMES ISDN subscriber, measured at the caller side.
TERMINAL CALL ANSWER It is the number of the answered calls with the bearer service employed by the
2757 TEANS
TIMES ISDN subscriber, measured at the called side.
It is the number of the calls failed in the bearer service due to the congestion.
2758 CONGESTION TIMES CG
The congestion includes the local congestion and the peer end congestion.
3-50
Entity
No.
TERMINAL CALL RINGED NO It is the times that the called makes no answer with the bearer service
2759 LTNANS
ANSWER TIMES employed.
ORIGINATING CALL
It equals the product of the Originating call answer traffic and statistic period
2760 AVERAGE CONVERSATION ORACVST
(seconds) divided by the Originating call answer times.
DURATION
TERMINAL CALL AVERAGE It equals the product of the Terminating call answer traffic and statistic period
2761 TEACVST
CONVERSATION DURATION (seconds) divided by the Terminating call answer times.
It is the average waiting duration from the caller hearing the ring back tone to
the called picking up the phone. It equals the product of the total waiting
2762 AVERAGE WAIT DURATION AWTT
duration and statistic period (seconds) divided by the number of connections of
the Originating calls.
ORIGINATING CALL Traffic of the answered calls with the bearer service employed by the ISDN
2764 ORRERL
ANSWER TRAFFIC subscriber, measured at the caller side.
TERMINAL CALL ANSWER Traffic of the answered calls with the bearer service employed by the ISDN
2766 TERERL
TRAFFIC subscriber, measured at the called side.
3.2.16 ISDN Terminal Service Traffic
Meaning: It conducts statistic analysis of the traffic of respective terminal services of

all ISDN subscribers.
MML word: ISDNTE
Object: Certain ISDN terminal service

1) ISDN types
z V5 ISDN (V5ISDN)
2) Terminal services
z Telephone (TEL)
z Fax service (FAX)
z Videophone service (VDOTEL)
z Unknown (UNKNW)
Table 3-34 Measurement of the ISDN terminal service traffic
Entity
No.
ORIGINATING CALL ATTEMPT It is the number of call attempts with the terminal service employed by the
2801 ORPEGS
TIMES ISDN subscriber, measured at the caller side.
TERMINAL CALL ATTEMPT It is the number of call attempts with the terminal service employed by the
2802 TEPEGS
TIMES ISDN subscriber, measured at the called side.
2803 CALLED BUSY TIMES It is the times that the called is busy with the terminal service employed. CBSY
ORIGINATING CALL It is the number of the connected calls with the terminal service employed by
2804 ORCNT
CONNECTED TIMES the ISDN subscriber, measured at the caller side.
TERMINAL CALL CONNECTED It is the number of the connected calls with the terminal service employed by
2805 TECNT
TIMES the ISDN subscriber, measured at the called side.
3-51
Entity
No.
ORIGINATING CALL ANSWER It is the number of the answered calls with the terminal service employed by
2806 ORANS
TIMES the ISDN subscriber, measured at the caller side.
TERMINAL CALL ANSWER It is the number of the answered calls with the terminal service employed by
2807 TEANS
TIMES the ISDN subscriber, measured at the called side.
It is the number of the calls failed in the terminal service due to the congestion.
2808 CONGESTION TIMES CG
The congestion includes the local congestion and the peer end congestion.
It is the times that the called makes no answer with the terminal service
2809 RINGED NO ANSWER TIMES LTNANS
employed.
ORIGINATING CALL AVERAGE It equals the product of the Originating call answer traffic and statistic period
2810 ORACVST
CONVERSATION DURATION divided by the Originating call answer times.
TERMINAL CALL AVERAGE It is the number of the answered calls with the terminal service employed by
2811 TEACVST
CONVERSATION DURATION the ISDN subscriber, measured at the caller side.
It is the average waiting duration from the caller hearing the ring back tone to
the called picking up the phone. It equals the product of the total waiting
2812 AVERAGE WAIT DURATION AWTT
duration and statistic period divided by the number of connections of the
Originating calls.
ORIGINATING CALL ANSWER
2814 Traffic of the answered bearer service by the ISDN caller ORRERL
TRAFFIC
TERMINAL CALL ANSWER Traffic of the answered calls with the terminal service employed by the ISDN
2816 TERERL
TRAFFIC subscriber, measured at the called side.
3.2.17 ISDN Supplementary Service Traffic
Meaning: It conducts statistic analysis of the registrations, applications, verifications

and cancellations of respective supplementary services made by all ISDN
subscribers.
MML word: ISDNNS
Object: Certain ISDN supplementary service

1) ISDN types
z V5 ISDN (V5ISDN)
2) Terminal services
z Calling Line Identification Presentation (CLIP)
z Calling Line Identification Restriction (CLIR)
z Connected Line Identification Presentation (COLP)
z Connected Line Identification Restriction (COLR)
z Sub-addressing (SUB)
z Call Forwarding Busy (CFB)
z Call Forwarding No Reply (CFNR)
z Call Forwarding Unconditional (CFU)
z Call Waiting (CW)
z Call Hold (HOLD)
z Terminal Portability (TP)
3-52
z Conference Calling (CONF)

z Three-Party Service (3PTY)
z User-to-User Signalling (UUS)
z Conference Disconnect (COND)
z All above supplementary services (ALL)
Table 3-35 Measurement of the ISDN supplementary service traffic
Entity
No.
2851 NS REGISTER OK TIMES REGOK
NS REGISTER FAILURE It refers to the number of failed registrations of the specified supplementary service
2852 REGFL
TIMES during the statistic period.
2853 NS CANCEL OK TIMES CANOK
NS CANCEL FAILURE It refers to the number of the failed cancellations of the specified supplementary
2854 CANFL
TIMES service during the statistic period.
It refers to the times that the specified supplementary service is successfully verified
2855 NS TEST OK TIMES TSTOK
NS TEST FAILURE It refers to the number of the failed verifications of the specified supplementary
2856 TSTFL
TIMES service during the statistic period.
2857 NS USED TIMES It refers to the times that the employment service is used during the statistic period. US
It is the average duration of the subscriber making use of the supplementary service.
NS AVERAGE SEIZURE
2858 It equals the product of the total duration and statistic period divided by the number AST
DURATION
of applications of the supplementary service.
2860 NS REGISTED TIMES REG
2861 NS CANCEL TIMES CAN
2862 NS TEST TIMES TST
3.2.18 ISDN BRA Traffic
Meaning: It conducts statistic analysis of the traffic of a single ISDN Basic Rate
Aapation (BRA) interface.
MML word: ISDNBRA
Object: Certain ISDN BRA interface
Table 3-36 Measurement of the ISDN BRA traffic
Entity
No.
6051 ORIGINATING CALL ATTEMPT TIMES It is the number of originated calls. ORPEGS
6052 ORIGINATING CALL ANSWER TIMES It is the number of answered calls. ORANS
3-53
Entity
No.
6053 ORIGINATING CALL TRAFFIC Traffic of originating calls ORERL
6055 TERMNAL CALL ATTEMPT TIMES It is the number of received calls. TEPEGS
6056 TERMNAL ANSWER TIMES It is the times that the received calls are answered. TEANS
6057 TERMNAL TRAFFIC Traffic of received calls TEERL
6059 TERMNAL CALLED BUSY TIMES It refers to the times that the called is busy. TECBSY
3.2.19 ISDN PRA Traffic
Meaning: It conducts statistic analysis of the traffic of a single ISDN Primary Rate
Interface (PRI).
MML word: PRA
Object: Certain ISDN PRA interface
Table 3-37 Measurement of the ISDN PRA traffic
Entity MML
Entity name Meaning
No. word
2901 ORIGINATING CALL ATTEMPT TIMES It is the number of the calls originated by the local subscribers. ORPEGS
It is the number of the calls received by the local subscribers after
2902 TERMINAL CALL ATTEMPT TIMES TEPEGS
the ringing attempt.
It is the times that the call, originated by the local subscriber, is
2903 ORIGINATING ANSWER TIMES ORANS
answered.
2904 TERMINAL CALL ANSWER TIMES It is the times that local subscribers answer the calls. TEANS
2905 TERMINAL CALL CALLED BUSY TIMES It is the number of failed incoming calls because the called is busy. TECBSY
2906 ORIGINATING CALL TRAFFIC Traffic originated by the local subscribers ORERL
It refers to the number of the calls received after ringing, including
2908 TERMINAL CALL TRAFFIC TEERL
the calls that the subscriber does not answer.
3.2.20 Bill Traffic
Meaning: It conducts statistic analysis of the calls in the same or different billing areas.
MML word: BILLA
Object: Office all
3-54
Table 3-38 Measurement of the bill traffic
Entity
No.
It is the number of the calls with the caller and called in a
1101 NUMBER OF CALL TIMES IN LOCAL BILL AREA SBACALL
billing area.
It is the number of the calls with the caller and called in
1102 NUMBER OF CALL TIMES IN OTHER BILL AREA OBACALL
different billing areas.
3.2.21 ACD group message traffic
Meaning: It measures traffic of ACD group.
MML word: ACDGRP
Object: Some ACD group
Table 3-39 Measurement of the ACD group message traffic
Entity
No.
ANSWER TIMES Number of the call answered by the called and originated ACDGAT
4381
by the continues ACD group
CALL FAIL TIMES Number of the call failed by the called and originated by ACDGCFT
4382
the continues ACD group
ACD QUEUE OVERFLOW TIMES Number of the overflow times in some ACD group ACDGOVE
4383
R
4385 AVERAGE LOGIN ACD USERS Average numbers of login in some ACD group ACDAL
3.2.22 ACD user message traffic
Meaning: It measures traffic of ACD user.
MML word: ACDUSER
Object: Every subscriber company select group of
Table 3-40 Measurement of the ACD user message traffic
Entity
No.
6751 ACD USER LOGIN GROUP ACD group number what the user login LOGGRP
6752 ACD USER ANSWER TIMES Number of the ACD user answer times ACDUAT
3-55
Entity
No.
6754 ACD USER TOTAL CONVERSATION DURATION It is the total duration for the ACD user call ACDTCD
6755 ACD USER AVERAGE CONVERSATION It is the average duration for the ACD user call ACDACD
DURATION
3.3 Measurement of Public Component
3.3.1 Unqueue Public Unit Traffic
Meaning: It conducts statistic analysis of the use and running of the ‘immediate
connection public component’ by calls. When there is no idle component, attempts to
seize an immediate connection public component will fail. It provides a reference for
maintenance and reasonable distribution & optimum utilization of switch resources.
MML word: UQPUBUNT
Object: Public component not in queue, enumeration object

z MFC (MFC)
z DTR (DTR)
z CT0 (CT0)
z COCK (COCK)
z RSD5 (RSD5)
z MFS (MFS)
z TKDRV (TKDRV)
Table 3-41 Measurement of the unqueued public unit traffic
Entity
No.
2951 BID TIMES It is the number of call attempts to get the public component resource. BID
2952 SEIZURE TIMES It is the number of successful calls to get the public component resource. SEIZ
Time duration from the congestion starting to the congestion finishing. The
2953 CONGESTION DURATION congestion starts while all resources are occupied and the congestion CGT
finishes while the first idle equipment appears
2955 INSTALLED UNIT NUM It is the number of the components installed. INSUNT
It is the number of the components available for the call (the number of the
2956 AVAIL UNIT NUM AVAUNT
components not in the error state or maintaining state).
2957 SEIZURE TRAFFIC Traffic transmitted during the time the component is occupied SERL
2959 AVERAGE SEIZURE DURATION It equals the Seizure traffic divided by the number of Seizures. AST
3-56
3.3.2 Queue Public Unit Traffic
Meaning: It conducts statistic analysis of the use and running of the queue public
component by calls, providing a reference for maintenance and reasonable
distribution of switch resources. It also reflects the extent that components affect the
service quality.
MML word: QPUBUNT
Object: Public component in queue
Table 3-42 Measurement of the queue public component traffic
Entity MML
Entity name Meaning
No. word
It is the number of successful immediate occupancies and successful
occupancies after queuing.
CALL ATTEMPT SEIZURE FAILURE
3002 It is the times of the queue congestion and queue overtime. USEIZ
TIMES
DIRECT SEIZURE SUCCESS It is the number of successful immediate occupancies of the specified
3003 DRSOK
TIMES resource during the statistic period.
SEIZURE SUCCESS AFTER It is the number of successful occupancies after the queuing of the specified
3004 QOK
QUEUED TIMES resource during the statistic period.
LOST CALL OF QUEUE TIMEOUT It is the number of failed occupancies due to the queuing overtime of the
3005 QTOU
TIMES specified resource in the statistic period.
Number of the released resource application in the queue with the specified
3006 USER ABANDON IN QUEUE TIMES QABN
resource occupied in the statistic period
It is the times that the applier is not able to enter the queue due to the
3007 QUEUE CONGESTION TIMES QCG
occupied resource, full queue or unavailable resource.
3009 AVERAGE SEIZURE DURATION It equals the Traffic divided by the number of Seizures. AST
AVERAGE WAIT DURATION Average time of the subscriber in the specified queue entering the queue
3010 AWTT
and then leaving the queue
AVERAGE QUEUE LENGTH Average number of the subscriber in the specified queue in the statistic
3012 AQLEN
period.
3014 INSTALLED UNIT NUM It is the number of the installed components. INSUNT
It is the number of the components available for the call (the number of the
3015 AVAIL UNIT NUM AVAUNT
components not in the error state or maintaining state).
It is the ratio of the occupied duration of the component to the total statistic
duration.
3.3.3 Console Traffic
Meaning: The console being a public component, measurement of its running and
utilization provides reference for maintenance and reasonable distribution of
resources. Also it reflects the service quality of the operator.
MML word: CON
3-57
Object: Certain operator console, subscriber frame internal code (USN), subscriber
frame external code (SN), subscriber frame port (URPSN).
Table 3-43 Measurement of the console traffic
Entity
No.
6151 CALLOUT TIMES It is the number of outgoing calls. OUTC
6152 CALLIN TIMES It is the number of incoming calls. IC
6153 CALLOUT CONNECTED TIMES It is the number of the connected outgoing calls. OUTCNT
It refers to the number of the connected incoming calls, that is, the times that
6154 CALLIN CONNECTED TIMES the operator console rings. The number is the sum of internal and external ICNT
calls.
6155 CALLIN ANSWER TIMES It refers to the times that the operator answers the incoming call. ANS
CALLIN RINGED NO ANSWER
6156 It refers to the times that the operator does not answer the incoming call. CNTNANS
TIMES
It is the times that the operator transfers the incoming calls during the
6157 TRANSFER CALL TIMES TRNC
statistic period.
A successful call transferring refers to the condition that the caller receives
SUCCESS TRANSFER CALL
6158 the ring back tone or speaks to the called. In other cases, for example, the TRNSUC
TIMES
caller hanging on, the called is busy, the call transferring fails.
It refers to the times that the call, received by the operator console, is made
6159 INSIDE CALLIN TIMES by the subscriber of one or multiple Centrex groups during the statistic INTC
period.
It refers to the times that the call, received by the operator console, is made
6160 OUTSIDE CALLIN TIMES by the subscriber out of one or multiple Centrex groups during the statistic OTSC
period.
It refers to the times that the type of the call, received by the operator
6161 CALL BACK CALL TIMES BAKC
console, is the call back type during the statistic period.
DIRECT SEIZURE TIMES During the statistic period, the console resource is applied for and it is the DRSOK
6162
number of the immediate seizing without waiting in the queue.
SEIZURE AFTER QUEUED During the statistic period, the console resource is applied for. Number of the QOK
6163
SUCCESS TIMES succeeded seizing waiting in the queue
LOST CALLS OF QUEUE During the statistic period, the console resource is applied. Number of the QTOU
6164
TIMEOUT TIMES lost of the call waiting in the queue overtime
USER ABANDON IN QUEUE During the statistic period, the console resource is applied. Number of the QABN
6165
TIMES releasing of the caller
QUEUE CONGESTION During the statistic period, the console resource is applied. Number of the QCG
6166 applied that cannot enter the queue because the queue is full or the
resource is not available anymore.
CONGESTION DURATION Congestion begins while the queue is full and congestion stops while the CGT
6167
queue is getting less full
It is the average number of the calls in the console queue in the statistic
6168 AVERAGE QUEUE LENGTH AQLEN
period.
AVERAGE CONVERSATION Total number of all speaks of the console/number of the call
6170 ACVST
DURATION
AVERAGE TRANSFER Duration of one call transferring refers to the duration from the console ATRNT
DURATION sending the ringing, the call makes the transferring after answering the
6172
phone. The average number is the total speaking duration/number of the call
transferring
AVERAGE WAIT DURATION Average time of the subscriber from entering the network to the exiting the AWTT
6173
queue during the statistic point.
OPR AVERAGE TELEPHONIST It is the average duration from the operator processing a certain call in the
6175 OPRHNDT
PROCESS DURATION queue to the operator hanging on.
CALLOUT CONVERSATION
6177 Traffic of the completed outgoing calls ORERL
TRAFFIC
CALLIN CONVERSATION
6179 Traffic of the completed incoming calls IRERL
TRAFFIC
3-58
3.3.4 SPM Resource MFC Traffic
Meaning: It conducts statistic analysis of the use of the Multi-Frequency Compelled

(MFC) resources shared by all Service Processing Modules (SPMs).
MML word: MFC
Object: All MFC resources.
Table 3-44 Measurement of the SPM MFC traffic
Entity
No.
1121 SEIZURE ATTEMPT TIMES It refers to the number of the attempts to seize the resources. BIDS
1122 SEIZURE TIMES It is the number of the seizures of the MFC resources. SEIZ
1123 CONGESTION TIMES It is the number of failures induced by congestion. CONG
FAILED FOR RESOURCE
1124 It is the number of failures induced by unavailable MFC resource. NOSRC
UNAVAILABLE TIMES
AVAILABLE CHANNEL It refers to the number of the MFC channels whose state is not in failure,
1125 AVLCHL
NUMBER isolated and inactive when the switch outputs results.
BEING USED CHANNEL It refers to the number of the MFC channels that are being used when the switch
1126 USEDCHL
NUMBER outputs results.
3.3.5 SPM Resource DTR Traffic
Meaning: It measures the use of the DTR resources shared by all SPMs.
MML word: DTR
Object: All DTR resources.
Table 3-45 Measurement of the SPM DTR traffic
Entity
No.
1142 SEIZURE TIMES It is the number of the seizures of the DTR resources. SEIZ
FAILED FOR RESOURCE
1144 It is the number of failures induced by unavailable DTR resource. NOSRC
UNAVAILABLE TIMES
AVAILABLE CHANNEL It refers to the number of the DTR channels whose state is not in failure, isolated
1145 AVLCHL
NUMBER and inactive when the switch outputs results.
BEING USED CHANNEL It refers to the number of the DTR channels that are being used when the switch
1146 USEDCHL
1147 SEIZURE DURATION SEIZT
3-59
Entity
No.
1148 CONGESTION DURATION CONGT
AVERAGE SEIZURE AVSEIZ
1149
DURATION
3.3.6 SPM Resource FSK Traffic
Meaning: It measures the use of the FSK resources shared by all SPMs.
MML word: FSK
Object: All FSK resources.
Table 3-46 Measurement of the SPM FSK traffic
Entity
No.
1162 SEIZURE TIMES It is the number of the seizures of the FSK resources. SEIZ
FAILED FOR RESOURCE
1164 It is the number of failures induced by unavailable FSK resource. NOSRC
UNAVAILABLE TIMES
AVAILABLE CHANNEL It refers to the number of the FSK channels whose state is not in failure, isolated
1165 AVLCHL
BEING USED CHANNEL It refers to the number of the FSK channels that are being used when the switch
1166 USEDCHL
1169 AVERAGE SEIZURE AVSEIZ
DURATION
3.3.7 SPM Resource ECP Traffic
Meaning: It measures the use of the Echo Cancellation Process (ECP) resources
shared by all SPMs.
MML word: ECP
Object: ECP resources.
3-60
Table 3-47 Measurement of the SPM ECP traffic
Entity
No.
1182 SEIZURE TIMES It is the number of the seizures of the ECP resources. SEIZ
1184 FAILED FOR RESOURCE
It is the number of failures induced by unavailable ECP resource. NOSRC
UNAVAILABLE TIMES
1185 AVAILABLE CHANNEL It refers to the number of the ECP channels whose state is not in failure, isolated
AVLCHL
1186 BEING USED CHANNEL It refers to the number of the ECP channels that are being used when the switch
USEDCHL
DURATION
3.3.8 SPM Resource MFS Traffic
Meaning: It measures the use of the MFS resources shared by all SPMs.
MML word: MFS
Object: MFS resources.
Table 3-48 Measurement of the SPM MFS traffic
Entity
No.
1202 SEIZURE TIMES It is the number of the seizures of the MFS resources. SEIZ
1204 FAILED FOR RESOURCE
It is the number of failures induced by unavailable MFS resource. NOSRC
UNAVAILABLE TIMES
1205 AVAILABLE CHANNEL It refers to the number of the MFS channels whose state is not in failure, isolated
AVLCHL
1206 BEING USED CHANNEL It refers to the number of the MFS channels that are being used when the switch
USEDCHL
DURATION
3-61
3.4 Measurement of Control Component
3.4.1 CPU Seizure Ratio Traffic
Meaning: It measures the CPU occupation ratio of each module.
MML word: CPU
Object: Certain module (SMSPM)
Table 3-49 Measurement of the CPU seizure ratio traffic
Entity MML Entity

Entity name Meaning
No. word threshold
It is the times that the CPU occupancy ratio exceeds the upper limit
3053 CONGESTION TIMES CG (0, 10)
corresponding to the highest level overloading.
3054 CONGESTION DURATION Congestion duration in the statistic period CGT (0, 60)
It is the times that the CPU occupancy ratio is lower than the lower limit
3056 OVERLOAD TIMES OL (0, 10)
corresponding to the lowest level overloading.
3057 OVERLOAD DURATION Overloading duration in the statistic period OLT (0, 60)
ORIGINATING CALL
3059 Sum of the originating calls and the incoming trunk calls ORC
ATTEMPT TIMES
ORIGINATING CALL It is the number of the originating calls barred due to the CPU
3060 ORCOL
OVERFLOW TIMES overloading and congestion.
3061 TERMINAL CALL TIMES Sum of the received calls and outgoing trunk calls TEC
LOST TERMINAL CALL It is the number of the terminating calls barred due to the CPU
3062 TECOL
OVERFLOW TIMES overloading or congestion.
3.5 Measurement of Signaling & Interface
3.5.1 ISDN PHI B Traffic
Meaning: It measures the traffic over the B-channel of the ISDN_PHI.
MML word: ISDNPHIB
Object: Certain B channel of ISDN_PHI nterface (ISDNPHIB).
3-62
Table 3-50 Measurement of the ISDN_PHI B_Channel traffic
Entity
No.
6201 CALL ATTEMPT TIMES Number of call attempts PEGS
6202 CALL ATTEMPT CONGESTION TIMES It is the number of the failed call attempts due to the congestion. PEGSBL
3.5.2 ISDN PHI D Traffic
Meaning: It measures the traffic over the D-channel of the ISDN_PHI.
MML word: ISDNPHID
Object: Certain D channel of ISDN_PHI nterface (ISDNPHID).
Table 3-51 Measurement of the ISDN_PHI D_Channel traffic
Entity
No.
Number of the packet processed by the packer at the unit of the
6251 PACKETS HANDLED NUM PKTHND
packet
3.5.3 ISDN UUS1 Traffic
Meaning: It measures the ISDN User-to-User Signaling (UUS) in Setup.
MML word: ISDNUUS1
Object: ISDN rate interfaces (ISBRAPRA)
Table 3-52 Measurement of the ISDN UUS1 traffic
Entity
No.
6301 ORIGINATING CALL UUS NUM Conducts statistic analysis in the unit of signaling units. ORUUSN
Conducts statistic analysis in the unit of the number of the bytes
6302 ORIGINATING CALL UUS FLOW ORUUSFW
contained in the signaling unit.
ORIGINATING CALL FAILURE FOR It refers to the number of the failed originating calls due to the length
6303 ORLENFL
LENGTH TIMES of the signaling.
ORIGINATING CALL FAILURE FOR NO It refers to the number of the failed originating calls due to the
6304 ORRGTFL
RIGHT TIMES insufficient authority.
6305 TERMINAL CALL UUS NUM Conducts statistic analysis in the unit of signaling units. TEUUSN
3-63
Entity
No.
Conducts statistic analysis in the unit of the number of the bytes
6306 TERMINAL CALL UUS FLOW TEUUSFW
contained in the signaling unit.
TERMINAL CALL FAILURE FOR NO It refers to the number of the failed received calls due to the
6307 TERGTFL
RIGHT TIMES insufficient authority.
3.5.4 ISDN UUS3 Traffic
Meaning: Measures the ISDN User-to-User Signaling in calls.
MML word: ISDNUUS3
Object: ISDN rate interfaces (ISBRAPRA)
Table 3-53 Measurement of the ISDN UUS3 traffic
Entity
No.
6351 ORG CALL UUS NUM Conducts statistic analysis in the unit of signaling units. ORUUS
ORG CALL FAILURE FOR UUS It refers to the number of the failed originating calls due to UUS
6352 ORCGFL
CONGESTION CTRL TIMES congestion control.
ORG CALL FAILURE FOR LENGTH It refers to the number of the failed originating calls due to the length of
6353 ORLENFL
TIMES the signaling.
ORG CALL FAILURE FOR NO It refers to the number of the failed originating calls due to the insufficient
6354 ORRGTFL
RIGHT TIMES authority.
6355 TERMINAL CALL UUS NUM Conducts statistic analysis in the unit of signaling units. TEUUS
TERMINAL CALL USER FAILURE It refers to the number of the failed received calls due to the insufficient
6356 TERGTFL
FOR RIGHT TIMES authority.
3.5.5 ISDN Signaling COMM Traffic
Meaning: Measures the traffic of ISDN signaling communication.
MML word: ISDND
Object: ISDN port signaling channel (LISPRA)
Table 3-54 Measurement of the ISDN signaling communication traffic
Entity No. Entity name Meaning MML word

6401 SIGNALING FLOW Traffic transmitted over the channel (bytes) SIGFW
3-64
3.5.6 MTP Signaling Link Traffic
Meaning: Measures MTP signaling link
MML word: MTPLNK
Object: Certain MTP signaling link (MTPLNK)
Table 3-55 Measurement of the MTP signaling link traffic
Entity MML
Entity name Meaning
No. word
It is the duration during which the signaling link is capable of providing the bearer
service, say, capable of transmitting or receiving the message. As for the standby
6501 SERVICE DURATION SVCT
signaling link, it is not considered in the operating state. It is the evaluation of the
counter by the Message Transfer Part (MTP) layer-3.
It is the duration during which the signaling link is not capable of transmitting the
6503 UNAVAIL DURATION UAVT
service. It is the evaluation of the counter by the MTP layer-3.
It is the times that the signaling link is out of the service. It is the accumulation of the
6505 FAULT TIMES FL
counter done by the MTP layer-3.
It is the unavailable duration of the signaling link due to the signaling link error. It is the
6506 FAULT DURATION FLT
evaluation of the counter by the MTP layer-3.
It is the number of the succeeded management inhibitions of the local signaling link. It
6508 LOCAL LIN TIMES LLIN
is the accumulation of the counter by the MTP layer-3.
It is the duration for the local signaling link that is management inhibited. It is the
6509 LOCAL LIN DURATION LLINT
It is the number of the succeeded management inhibitions of the remote signaling link.
6511 REMOTE LIN TIMES RLIN
It is the accumulation of the counter by the MTP layer-3.
It is the duration for the remote signaling link that is management inhibited. It is the
6512 REMOTE LIN DURATION RLINT
It is the times that the remote processor is in the error state. It is the accumulation of
6514 RPO TIMES RPER
the counter by the MTP layer-3.
It is the unavailable duration for the signaling link that receives the error indication
6515 RPO DURATION RPERT
from the remote processor. It is the evaluation of the counter by the MTP layer-3.
It is the number of MSUs transmitted over the signaling link. It is the accumulation of
6517 MSU SND NUM SMSU
the counter by the MTP layer-3.
It is the number of MSUs received by the signaling link. It is the accumulation of the
6518 MSU RCV NUM RMSU
counter by the MTP layer-3.
It is the number of the 8-bit fields of SIP and SIO transmitted over the signaling link. It
6519 OCTETS SND NUM SOCT
is the accumulation of the counter by the MTP layer-3.
It is the number of the 8-bit fields of SIP and SIO received by the signaling link. It is the
6520 OCTETS RCV NUM ROCT
accumulation of the counter by the MTP layer-3.
(Number of the 8-bit fields of SIF and SIO sent + number of the head
6521 SND SEIZURE RATIO SSEIZR
bytes)/8K/measurement period(s)*100
(Number of the 8-bit fields of SIF and SIO received + number of the head
6522 RCV SEIZURE RATIO RSEIZR
bytes)/8K/measurement period(s)*100
6523 SND IAM TIMES It is the times that the initial address is sent. SIAM
6524 RCV IAM TIMES It is the times that the initial address is received. RIAM
SND CIRCUIT GRP
6525 It is the times that the congestion occurs to the sending circuit group. SCGC
CONGESTION TIMES
RCV CIRCUIT GRP
6526 It is the times that the congestion occurs to the receiving circuit group. RCGC
CONGESTION TIMES
SND SWITCH
6527 EQUIPMENT It is the times that the congestion occurs to the sending switching equipment. SSEC
CONGESTION TIMES
3-65
Entity MML
Entity name Meaning
No. word
RCV SWITCH
6528 EQUIPMENT It is the times that the congestion occurs to the receiving switching equipment. RSEC
CONGESTION TIMES
TRANSMIT NATIONAL
6529 NETWORK It is the times that the congestion occurs to the national network at the transmit end. SNNC
CONGESTION TIMES
RCV NATIONAL
6530 NETWORK It is the times that the congestion occurs to the national network at the receive end. RNNC
CONGESTION TIMES
It is the times that the congestion occurs because the messages are over the
6531 CONGESTION TIMES threshold in the layer-3 sending buffer. It is the accumulation of the counter by the CG
MTP layer-3.
CONGESTION It is the congestion duration because the messages are over the threshold in the
6532 CGT
DURATION layer-3 sending buffer. It is the evaluation of the counter by the MTP layer-3.
DISCARD MSU FOR It is the number of the discarded MSUs because of the congestion of the signaling link. CGMSUDI
6534
CONGESTION NUM It is the accumulation of the counter by the MTP layer-3. S
6535 RCV TFP NUM It is the number of the received signals that are inhibited to be transmitted. RTFP
LOCAL AUTO It is the number of the switchovers of the service to another link because of the
6536 LCO
SWITCHOVER TIMES unavailable link. It is the accumulation of the counter by the MTP layer-3.
INCOMING ANSWER
6537 It is the number of the signals answering the incoming call. IANS
SIGNAL TIMES
OUTGOING ANSWER
6538 It is the number of the signals answering the outgoing call. OANS
SIGNAL TIMES
3.5.7 MTP Linkset Traffic
Meaning: Conducts statistic analysis of the availability of signaling linksets in the

Administration Module (AM).
MML word: MTPLNKS
Object: Certain MTP signaling channel set (MTPLNKS)
Table 3-56 Measurement of the MTP linkset traffic
Entity MML
Entity name Meaning
No. word
It is the number of the unavailable signaling linksets, say, all signaling links in the linkset
6601 UNAVAIL TIMES UAV
are unavailable. It is the accumulation of the counter by the MTP layer-3.
It is the unavailable duration of the signaling linkset. It is the evaluation of the counter by
6602 UNAVAIL DURATION UAVT
the MTP layer-3.
3.5.8 MTP DEST Signaling Point Traffic
Meaning: Measures the MTP Destination Signaling Point (DSP) traffic.
3-66
MML word: MTPDPC
Object: Index of signaling point
Table 3-57 Measurement of the MTP DSP traffic
Entity MML
Entity name Meaning
No. word
It is the number of the failed accesses to the destination signaling point. It is the
6651 INACCESSIBLE TIMES INA
INACCESSIBLE It is the unreachable duration of the destination signaling point. It is the evaluation of the
6652 INAT
DURATION counter by the MTP layer-3.
3.5.9 MTP SP Distribution Traffic
Meaning: Measures the MTP Signaling Point (SP) distribution traffic.
MML word: MTPDISP
Object: Origin Signaling Point Coding (OPC), Destination signaling point coding,
Network Identifier (NI).
Result type & other attributes: Short result. Sample measurement can be employed
according to the sample rate.
Table 3-58 Measurement of the MTP SP distribution traffic
Entity MML
Entity name Meaning
No. word
It is the total number of the messages received/sent by the local office. It is the accumulation of the
7101 MSU NUM MSU
counter by the MTP layer-3.
It is the total number of 8-bit fields of SIO and SIF received/sent by the local office. It is the
7102 OCTET NUM OCT
3.5.10 TUP Total MSU Traffic
Meaning: Conducts statistic analysis of the number of all messages on the Telephone
User Part (TUP).
MML word: TUPMSG
Object: All TUPs (TLTUP)
3-67
Table 3-59 Measurement of the TUP total MSU traffic
Entity MML
Entity name Meaning
No. word
701 NUM OF MSG SENT Total number of the messages sent by the TUP of the switching office (or a module) SMSU
Total number of the messages received by the TUP of the switching office (or a module)
702 NUM OF MSG RCV RMSU
from MTP
3.5.11 TUP MSG Using Traffic
Meaning: Measures the usage of the TUP messages in some office direction.
MML word: TUPMSGUS
Object: TUP messages of certain TUP trunk group (TUPMSG). TUP trunk group is
presented by the input trunk group (TKG). TUP messages are of the enumeration
type, such as IAM, IAI, SAM, SAO, GSM, COT, CCF, GRQ, ACM, CHG, SEC, CGC,
NNC, ADI, CFL, UNN, LOS, SST, ACB, DPN, ANU, ANC, ANN, CBK, CLF, RAN, CCL,
RLG, BLO, BLA, UBL, UBA, CCR, RSC, MGB, MBA, MGU, MUA, HGB, HBA, HGU,
HUA, GRS, GRA, ACC, MPM, OPR, SLB, STB and CGB.
Table 3-60 Measurement of the TUP message using traffic

3101 NUM OF MSG SENT Number of certain TUP messages sent through a certain circuit group SMSG
3102 NUM OF MSG RCV Number of certain TUP messages received through a certain circuit group RMSG
3.5.12 TUP Abnormity Traffic
MML word: TUPUNS
Object: Certain TUP trunk groups
Table 3-61 Measurement of the TUP abnormity traffic
Entity
No.
3151 NO RSC ACK TO T19 TIMES It is the times that no RSC is received within T19. T19
3-68
Entity
No.
3152 NO GRA TO T22 TIMES It is the times that no GRA is received within T22. T22
3153 NO CLF TO T5 TIMES It is the times that no CLF is received within T5. T5
3154 NO RLG TO T7 TIMES It is the times that no RLG is received within T7 (corresponding to CLF). T7
3155 ABNORMAL RELEASE TIMES It is the number of the abnormal releases. UNSRLS
CIRCUIT BLOCKED BY PEER
3156 It is the times that the congestion occurs. BLCIR
END TIMES
It is the times that there is no blocking acknowledgment in the received
RCV NOT COMPLETE MHBA
3157 circuit group blocking acknowledgment (MBA, HBA) message, to the NMHBA
TIMES
circuits specified in the circuit group blocking message (MGB, HGB).
It is the times that there is no unblocking acknowledgment in the received
RCV NOT COMPLETE MHUA
3158 circuit group unblocking acknowledgment (MUA, HUA) message, to the NMHUA
TIMES
circuits specified in the circuit group unblocking message (MGU, HGU).
It is the times that there is blocking acknowledgment in the received circuit
3159 RCV TOOMUCH MHBA TIMES group blocking acknowledgment (MBA, HBA) message, to the circuits TUMHBA
unspecified in the circuit group blocking message (MGB, HGB).
It is the times that there is unblocking acknowledgment in the received
3160 RCV TOOMUCH MHUA TIMES circuit group unblocking acknowledgment (MUA, HUA) message, to the TUMHUA
circuits unspecified in the circuit group unblocking message (MGU, HGU).
It is the times that the circuit, specified in the circuit group blocking
RCV UNEXPECTED MHBA
3161 acknowledgment (MBA, HBA) message, is not the expected circuit to be RUEXMHBA
TIMES
blocked.
It is the times that the circuit, specified in the circuit group unblocking
RCV UNEXPECTED MHUA
3162 acknowledgment (MUA, HUA) message, is not the expected circuit to be RUEXMHUA
TIMES
unblocked.
RCV UNEXPECTED BLA It is the times that the circuit in the received BLA is not the expected circuit
3163 RUEXBLA
TIMES to be blocked.
RCV UNEXPECTED UBA It is the times that the circuit in the received UBA is not the expected circuit
3164 RUEXUBA
TIMES to be unblocked.
3165 NO BLA TO T13 TIMES It is the times that no BLA is received within T13 (corresponding to BLO). T13
3166 NO UBA TO T16 TIMES It is the times that no UBA is received within T16 (corresponding to UBL). T16
NO SECOND GRP TO T25 It is the times that no secondary group blocking message or group
3167 T25
TIMES unblocking message is received within T25.
It is the times that no MBA (Maintenance Oriented Circuit Group Blocking
3168 NO MBA TO T27 TIMES T27
Acknowledgment Message) is received within T27.
It is the times that no MUA (Maintenance Oriented Circuit Group
3169 NO MUA TO T29 TIMES T29
Unblocking Acknowledgment Message) is received within T29.
It is the times that no HBA (Hardware Failure Oriented Circuit Group
3170 NO HBA TO T33 TIMES T33
Blocking Acknowledgment Message) is received within T33.
It is the times that no HGU (Hardware Failure Oriented Circuit Group
3171 NO HGU TO T35 TIMES T35
Unblocking Acknowledgment Message) is received within T35.
3172 MSG FORMAT ERROR TIMES Times of the invalid message format MSGER
RCV UNEXPECTED MSG
3173 Number of the unexpected messages received RUEXMSG
TIMES
3174 RCV UNKNOWN MSG TIMES Number of the unrecognized messages RUKNWMSG
3.5.13 TUP Node Performance Traffic
MML word: TUPNOD
Object: All TUPs (TLTUP)
3-69
Table 3-62 Measurement of the TUP node performance traffic
Entity
No.
731 INCOMING CALL ATTEMPT TIMES Total number of the incoming call attempts IPEGS
It is the times that congestion occurs to the switching
732 SWITCH EQUIPMENT CONGESTION TIMES SEC
equipment.
733 CIRCUIT GRP CONGESTION TIMES It is the times that congestion occurs to the circuit group. CGC
It is the times that congestion occurs to the national
734 NATIONAL NETWORK CONGESTION TIMES NNC
network.
735 ADDRESS INCOMPLETE TIMES It is the times that incomplete address is received. ADI
736 CALL FAILURE TIMES Number of the failed calls CLFL
737 USER BUSY TIMES It is the times that the called is busy. SB
It is the times that the called number is an unallocated
738 UNALLOCATED CODE TIMES UNN
one.
739 LINE OUT OF SERVICE TIMES It is the times that the line is out of service. LOS
740 SND SPECIAL TONE TIMES It is the times that the special signal tone is sent. SST
741 ACCESS BARRED TIMES It is the times that access is barred. ACB
742 DIGITALPATH NOT PROVIDED TIMES It is the times that the digital channel is not provided. DPN
743 ERROR DIALLING TK PREFIX TIMES It is the times that the trunk prefix is wrong. WGTKPFX
3.5.14 TUP NET Performance Traffic
MML word: TUPNET
Object: Origin signaling point coding (OPC)
Table 3-63 Measurement of the TUP network performance traffic

3201 OUTGOING CALL ATTEMPT TIMES Number of the outgoing call attempts OPEGS
3202 RCV SEC NUM Number of the received SECs RSEC
3203 RCV CGC NUM Number of the received CGCs RCGC
3204 RCV NNC NUM Number of the received NNCs RNNC
3205 RCV ADI NUM Number of the received ADIs RADI
3206 RCV CFL NUM Number of the received CFLs RCFL
3207 RCV SB NUM It is the times that the called is busy. RSB
3208 RCV UNN NUM Number of the received UNNs RUNN
3209 RCV LOS NUM Number of the received LOSs RLOS
3210 RCV SST NUM Number of the received SSTs RSST
3211 RCV ACB NUM Number of the received ACBs RACB
3212 RCV DPN NUM Number of the received DPNs RDPN
3213 RCV ERROR DIALLING TK PREFIX NUM It is the times that the trunk prefix is wrong. RWGTKPFX
3.5.15 TUP Circuit Group Performance Traffic
3-70
MML word: TUPTKG
Object: Certain TUP trunk groups (TUPTKG)
Table 3-64 Measurement of the TUP circuit group performance traffic
Entity
No.
3251 INCOMING CALL ATTEMPT TIMES Number of the incoming call attempts IPEGS
SWITCH EQUIPMENT CONGESTION
3252 It is the times that congestion occurs to the switching equipment. SEC
TIMES
3253 CIRCUIT GRP CONGESTION TIMES It is the times that congestion occurs to the circuit group. CGC
NATIONAL NETWORK
3254 It is the times that congestion occurs to the national network. NNC
CONGESTION TIMES
3255 CONGESTION TIMES Sum of three items above CG
3256 ADDRESS INCOMPLETE TIMES It is the times that incomplete address is received. ADI
3257 CALL FAILLURE TIMES Number of the failed calls CLFL
3258 USER BUSY TIMES It is the times that the called is busy. BSY
3259 UNALLOCATED CODE TIMES It is the times that the called number is an unallocated one. UNN
3260 LINE OUT OF SERVICE TIMES It is the times that the line is out of service. LOS
3261 SND SPECIAL TONE TIMES It is the times that the special signal tone is sent. SST
3262 ACCESS BARRED TIMES It is the times that access is barred. ACB
DIGITALPATH NOT PROVIDED
3263 It is the times that the digital channel is not provided. DPN
TIMES
3264 ERROR DIALLING TK PREFIX TIMES It is the times that the trunk prefix is wrong. WGTKPFX
3265 OUTGOING CALL ATTEMPT TIMES Number of the outgoing call attempts OPEGS
3266 RCV SEC NUM Number of the received SECs RSEC
3267 RCV CGC NUM Number of the received CGCs RCGC
3268 RCV NNC NUM Number of the received NNCs RNNC
3269 RCV ADI NUM Number of the received ADIs RADI
3270 RCV CFL NUM Number of the received CFLs RCFL
3272 RCV UNN NUM Number of the received UNNs RUNN
3273 RCV LOS NUM Number of the received LOSs RLOS
3274 RCV SST NUM Number of the received SSTs RSST
3275 RCV ACB NUM Number of the received ACBs RACB
3276 RCV DPN NUM Number of the received DPNs RDPN
RCV ERROR DIALLING TK PREFIX
3277 It is the received times that the trunk prefix is wrong. RWGTKPFX
NUM
3278 ANSWER NOT CHARGING TIMES Number of the uncharged answers ANN
MAINTENANCE GRP BLOCKING
3279 It is the times that the maintenance oriented congestion occurs. MGB
TIMES
3280 HARDWARE GRP BLOCKING TIMES It is the times that the hardware failure oriented congestion occurs. HGB
3281 CIRCUIT GRP RESET TIMES It is the times that the circuit group is reset. GRS
3282 CIRCUIT RESET TIMES It is the times that the circuit is reset. CIRRST
3283 ANSWER TIMES It is the times that the call is answered. ANS
3284 NUM OF MSU RCV Number of the received messages MSUR
3285 NUM OF MSU SENT Number of the sent messages MSUS
3286 NUM OF MSU RCV AND SENT Total number of the received and sent messages MSURS
3287 LENGTH OF MSU RCV Total length of the received messages in the statistic period MSURL
3288 LENGTH OF MSU SENT Total length of the sent messages in the statistic period MSUSL
3289 LENGTH OF MSU RCV AND SENT Total length of the received and sent messages in the statistic period MSURSL
3290 TOTAL CALL ATTEMPT TIMES Total number of the incoming and outgoing calls IOPEGS
It is the total length of the messages divided by the number of call
3291 LENGTH OF MSU PER CALL MSULPC
attempts.
It is the total length of the messages divided by the total number of the
3292 AVERAGE LENGTH OF MSU MSUAVL
messages.
3-71
3.5.16 ISUP Total MSU Traffic
MML word: ISUPMSG
Object: All ISUPs (TLISUP)
Table 3-65 Measurement of the ISUP total message traffic
Entity MML
Entity name Meaning
No. word
Total number of the messages sent by the ISDN User Part (ISUP) of the switching
751 NUM OF MSG SENT SMSU
office (or a module)
Total number of the messages received by the ISUP of the switching office (or a
752 NUM OF MSG RCV RMSU
module) from MTP
3.5.17 ISUP MSG Using Traffic
MML word: ISUPMSGU
Object: ISUP messages of the ISUP trunk group (ISUPMSG). ISUP messages are of
the enumeration type, such as ACM, ANM, BLO, BLA, CCL, CPG, CGB, CGBA, CQM,
CQR, GRS, GRA, CGU, CGUA, CRG, CHG, TAC, CHB, CHU, CHA, CHP, CFN, CON,
COT, CCR, FAC, FAA, FRJ, ISUP_FAR (IFAR), IDR, IDS, INF, INR, IAM, LPA, MPM,
NRM, OLM, OPR, PAM, REL, RLC, RSC, RES, SGM, SAM, SUS, UBL, UBA, UCIC,
UPA, UPT and USR.
Table 3-66 Measurement of the ISUP message using traffic

3301 NUM OF MSG SENT Number of a certain ISUP messages sent by a certain circuit group SMSG
3302 NUM OF MSG RCV Number of a certain ISUP messages received by a certain circuit group RMSG
3.5.18 ISUP Abnomity Traffic
MML word: ISUPUNS
Object: Certain ISUP trunk group (ISUPTKG)
3-72
Table 3-67 Measurement of the ISUP abnormity traffic
Entity
No.
It is the statistic analysis of each circuit group. It refers to the number of cases that no
acknowledgment message is received to respond RSC within T17 (10 minutes). After
NO RSC ACK TO sending RSC to a certain circuit, if the ISUP cannot receive the response signal (RLC), it
3351 T17
T17 TIMES will send RSC every 30 seconds until it gets the response signal. If it cannot get the
response after trying 20 times, it will start T17 and sends RSC every 10 minutes until it gets
the response.
It is the statistic analysis of each circuit group. It refers to the number of cases that no
NO GRA TO T23 acknowledgment message GRA is received to respond the Group Reset message GRS
3352 T23
TIMES within T23 (10 minutes). The instability of circuits in a circuit group is obtained through the
statistics within a certain period.
It is the statistic analysis of each circuit group. It refers to the number of cases that no RLC
is received after sending REL within T5 (10 minutes). After the trial for 20 times, no REL
NO RLC TO T5
3353 will be sent. Then, RSC will be sent and T17 is started. The failure may result from T5
TIMES
improper handling or data error at the peer end. The statistics may be used to find
problems and determine the severity of the problem.
CIRCUITS It is the statistic analysis of each circuit group. If the peer end always blocks a certain
3354 BLOCKED BY circuit within a certain time, it indicates that the offices connected by the circuit have some BLCIR
PEER END TIMES problems in handling the circuit (data or program error).
RCV NO CGBA It is the times that there is no CGBA message to some circuits. It is the statistics of each
3355 ON SOME circuit group. The inconsistency in both ends processing the group message is obtained NCGBA
CIRCUITS TIMES through the statistics of the error acknowledgment.
RCV NO CGUA
3356 ON SOME It is the times that there is no CGUA message to some circuits. NCGUA
CIRCUITS TIMES
RCV TOOMUCH
3357 CGBA ON SOME It is the times that there are CGBA messages to some unspecified circuits. TUCGBA
CIRCUITS TIMES
RCV TOOMUCH
3358 CGUA ON SOME It is the times that there are CGUA messages to some unspecified circuits. TUCGUA
CIRCUITS TIMES
It is the times that the unexpected CGBA is received. It refers to the number of cases that
RCV the acknowledge message CGBA returned by the peer end does not match the CGB
3359 UNEXPECTED message sent by the local end. It may result from the perplexing messages sent by the RUEXCGBA
CGBA TIMES peer end or the circuit data difference at both sides. The instability of circuits is obtained
through the statistics within a certain period.
RCV
3360 UNEXPECTED It is the times that the unexpected CGUA is received. RUEXCGUA
CGUA TIMES
It is the times that the unexpected BLA is received. Being the statistics of each circuit
RCV
group, it refers to the number of cases that the acknowledge message BLA is received but
3361 UNEXPECTED RUEXBLA
no circuit blocking message BLO is sent. It may result from the circuit data difference at
BLA TIMES
both sides or the improper handling of one side.
RCV
3362 UNEXPECTED It is the times that the unexpected UBA is received. RUEXUBA
UBA TIMES
It is the statistics for each circuit group. It refers to the number of cases that no BLA is
NO BLA TO T13
3363 received to respond the BLO within T13 (10 minutes). It may result from the circuit data T13
TIMES
difference at both sides or the improper handling of one side.
It is the statistics for each circuit group. It refers to the number of cases that no UBA is
NO UBA TO T15
3364 received to respond the UBL within T15 (10 minutes). It may result from the circuit data T15
TIMES
difference at both sides or the improper handling of one side.
NO CGBA TO T19 It is the statistics for each circuit group. It refers to the number of cases that no CGBA is
3365 T19
TIMES received to respond the CGB within T19 (10 minutes).
NO CGUA TO T21 It is the statistics for each circuit group. It refers to the number of cases that no CGUA is
3366 T21
TIMES received to respond the CGU within T21 (10 minutes).
3-73
Entity
No.
MSG FORMAT
It is the times of the invalid message format. The message may be discarded if its format is
3367 MSGER
ERROR TIMES
invalid.
It is the number of the received unexpected messages. The unexpected message is one of
RCV
the recognized messages that are received in the wrong phase of the call. If lots of
3368 UNEXPECTED RUEXMSG
unexpected messages are received during a certain time, it indicates that signaling
MSG TIMES
matching of both ends has some problems.
It is the number of the received unrecognized messages. If lots of unrecognized messages
RCV UNKNOWN
3369 are received during a certain time, it indicates that signaling matching of both ends has RUKNWMSG
MSG TIMES
some problems.
3.5.19 ISUP Node Performance Traffic
MML word: ISUPNOD
Object: All ISUPs (TLISUP)
Table 3-68 Measurement of the ISUP node performance traffic
Entity MML
Entity name Meaning
No. word
791 INCOMING CALL ATTEMPT TIMES Total number of the incoming call attempts IPEGS
It is the times that congestion occurs to the switching equipment. The
SWITCH EQUIPMENT
792 congestion may result from the failed resource allocation of IPATH, CR, CCB SEC
CONGESTION TIMES
and HW, and so on.
793 NO VALID CIRCUIT TIMES It is the number of cases that there is no valid circuit. CGC
794 ADDRESS INCOMPLETE TIMES It is the times that an incomplete address is received. ADI
795 TEMPORARY FAILURE TIMES Number of the temporary failures TMPFL
796 UNALLOCATED CODE TIMES It is the times that the called number is an unallocated one. UNN
797 USER BUSY TIMES It is the times that the called is busy. SB
798 DPC OUT OF SERVICE TIMES It is the times that the destination point is out of service. DPCFL
799 OTHER CALL FAILURE TIMES Number of failures caused by other reasons OTHFL
3.5.20 ISUP NET Performance Traffic
MML word: ISUPNET
Object: Origin singaling point coding (OPC)
3-74
Table 3-69 Measurement of the ISUP network performance traffic
Entity
No. Entity name Meaning MML word
3401 OUTGOING CALL ATTEMPT TIMES Total number of the outgoing call attempts OPEGS
3402 RCV SEC NUM It is the times that the congestion occurs to the switching network. RSEC
3403 RCV CGC NUM It is the number of cases that there is no valid circuit. RCGC
3404 RCV ADI NUM It is the times that an incomplete address is received. RADI
3405 RCV TEMP FAILURE NUM Number of the received temporary failures RTMPFL
3406 RCV UNN NUM It is the times that the called number is an unallocated one. RUNN
It is the number of the cases that there is no route to the destination
3407 RCV NO ROUTE NUM RNRU
point.
3409 RCV DEST OUT OF SERVICE NUM It is the times that the destination is out of service. RDPCFL
3410 RCV OTHER FAILURE NUM Number of the other reasons received ROTH
3.5.21 ISUP Circuit Group Performance Traffic
MML word: ITKP
Object: Certain ISUP trunk group (ISUPTKG)
Table 3-70 Measurement of the ISUP circuit group performance traffic
Entity
No.
INCOMING CALL ATTEMPT
3451 Total number of the incoming call attempts IPEGS
TIMES
3452 SEC TIMES It is the times that congestion occurs to the switching equipment. SEC
3453 CGC TIMES It is the number of cases that there is no valid circuit. CGC
3454 CONGESTION TIMES Sum of the two items above CG
3455 ADI TIMES It is the times that an incomplete address is received. ADI
3456 TEMPFAILURE TIMES Number of the temporary failures TMPFL
3457 UNN TIMES It is the times that the called number is an unallocated one. UNN
3458 SB TIMES It is the times that the called is busy. SB
DEST POINT OUT OF SERVICE
3459 It is the times that the destination is out of service. DPCFL
TIMES
3460 OTHER FAILURE TIMES Number of the failures due to other reasons OTHFL
OUTGOING CALL ATTEMPT
3461 Total number of the outgoing call attempts OPEGS
TIMES
3462 RCV SEC TIMES It is the received times that congestion occurs to the switching network. RSEC
3463 RCV CGC TIMES It is the received number of cases that there is no valid circuit. RCGC
3464 RCV ADI TIMES It is the received times that an incomplete address is received. RADI
3465 RCV TEMP FAILURE TIMES Number of the received temporary failures RTMPFL
3466 RCV UNN TIMES It is the received times that the called number is an unallocated one. RUNN
3467 RCV NO ROUTE TIMES It is the received times that there is no route to the destination. RNRU
3468 RCV SB TIMES It is the received times that the called is busy. RSB
RCV DEST POINT OUT OF
3469 It is the received times that the destination is out of service. RDPCFL
SERVICE TIMES
3470 RCV OTHER FAILURE TIMES Number of other reasons received ROTH
ANSWER NO CHARGING
3471 Number of the uncharged answers ANN
TIMES
3-75
Entity
No.
MAINTENANCE GRP BLOCK
3472 It is the times that the maintenance oriented congestion occurs. MGB
TIMES
HARDWARE GRP BLOCK
3473 It is the times that the hardware failure oriented congestion occurs. HGB
TIMES
3474 CIRCUIT GRP RESET TIMES It is the times that the circuit group is reset. GRS
3475 CIRCUIT RESET TIMES It is the times that the circuit is reset. CIRRST
3476 ANSWER TIMES It is the times that the call is answered. ANS
3477 NUM OF MSU RCV Number of the received messages MSUR
3478 NUM OF MSU SENT Number of the sent messages MSUS
3479 NUM OF MSU RCV AND SENT Total number of the received and sent messages MSURS
3480 LENGTH OF MSU RCV Total length of the received messages in the statistic period MSURL
3481 LENGTH OF MSU SND Total length of the sent messages in the statistic period MSUSL
LENGTH OF MSU RCV AND
3482 Total length of the received and sent messages in the statistic period MSURSL
SND
3483 TOTAL CALL ATTEMPT TIMES Total number of the incoming and outgoing calls IOPEGS
3484 LENGTH OF MSU PER CALL It is the total length of the messages divided by the number of call attempts. MSULPC
It is the total length of the messages divided by the total number of the
3485 AVERAGE LENGTH OF MSU MSUAVL
messages.
3.5.22 V5 Interface Traffic
MML word: V5I
Object: Certain V5 interface (V5PRT)
Table 3-71 Measurement of the V5-interface traffic
Entity
No.
3501 INTERFACE RESTART TIMES It is the times that the V5-interface starts. V5IRTT
3502 INTERFACE PROTECT SWITCHOVER TIMES Number of the switchovers at the V5-interface V5IPTCSW
3503 V5 INTERFACE UNAVAIL DURATION Unavailable duration of the V5-interface V5IUAVT
3505 NOT WORKING C CHL TIMES V5IUAVC
REMOTE BLOCKING NOT WORKING C CHL
3506 V5IRBLC
TIMES
LOCAL BLOCKING NOT WORKING C CHL
3507 V5ILBLC
TIMES
It is the total occupancy duration of all bearer channels of the
3508 B CHL CONGESTION DURATION V5-interface. It equals the accumulation of the failed V5ICGT
allocation due to no bearer channel.
3.5.23 V5 2M Link Information Traffic
MML word: V5L
3-76
Object: Certain V5 trunk 2M link (V52MLK)
Table 3-72 Measurement of the V5 2 Mbit/s link information traffic
Entity MML
Entity name Meaning
No. word
3551 V5 LINK AN BLOCKED TIMES It is the times that the link is blocked at the Access Network (AN) side. V5LANBL
It is the times that FE303/FE304 (link blocking) is sent from the Local
3552 V5 LINK LE BLOCKED TIMES V5LLEBL
Exchange (LE) side.
3553 V5 LINK FAULT TIMES Number of the link failures V5LFL
3554 V5 LINK UNAVAIL DURATION Unavailable duration of the link V5LUAVT
3.5.24 V5 Physical C Channel Traffic
MML word: V5PC
Object: Certain C channel of V5 interface (V5PHYC)
Table 3-73 Measurement of the V5 physical C channel traffic
Entity
No.
3601 C CHL UNAVAIL TIMES It is the times that the C channel is unavailable. V5PCUAV
3602 REMOTE 2MLINK BLOCKED TIMES It is the times that the remote 2 Mbit/s link is blocked. V5PCRBL
3603 LOCAL 2MLINK BLOCKED TIMES It is the times that the local 2 Mbit/s link is blocked. V5PCLBL
3604 UNAVAIL DURATION Unavailable duration of the C channel V5PCUAVT
3606 ACTIVE TIMES It is the times that the C channel bears a logical C channel. V5PCACT
It is the times that the C channel is used for the logical C channel
3607 STANDBY TIMES V5PCSBY
protection instead of bearing a logical C channel.
3608 ACTIVE DURATION Duration of the C channel bearing a logical C channel V5PCACTT
It is the duration that the C channel is used for the logical C channel
3610 STANDBY DURATION V5PCSBYT
protection instead of bearing a logical C channel.
3.5.25 V5 Logical C Channel Traffic
MML word: V5LC
Object: Logical C channel of certain EF address (V5LOGC), comprising EF_ISDN_DL

(V5LCISDN), EF_PSTN_DL (V5LCPSTN), EF_CTRL_DL (V5LCCTRL),
EF_BCC_DL (V5LCBCC), EF_PROT_DL (V5LCPROT) and EF_LINKC_DL
(V5LCLNKC).
3-77
Table 3-74 Measurement of the V5 logical C channel traffic

6701 RCV FRAME NUM Number of the received packet frames V5LCRFR
6702 SND FRAME NUM Number of the sent packet frames V5LCSFR
6703 SND BYTES LENGTH NUM Total length of the sent 8-bit fields V5LCSBYT
6704 RCV BYTES LENGTH NUM Total length of the received 8-bit fields V5LCRBYT
6705 RCV ISDN FRAME NUM Number of the received ISDN packet frames V5LCRIFR
6706 SND ISDN FRAME NUM Number of the sent ISDN packet frames V5LCSIFR
6707 REMOTE RCV BUSY TIMES It is the times that the receiver at the peer end is busy. V5LCRRB
6708 LOCAL SENDER BUSY TIMES It is the times that the local transmitter is busy. V5LCLSB
6709 RCV PSTN MSG NUM Number of the received PSTN protocol messages V5LCRPTN
6710 RCV CTRL MSG NUM Number of the received control protocol messages V5LCRCTL
6711 RCV LCTRL MSG NUM Number of the received link control protocol messages V5LCRLTL
Number of the received Bearer Channel Connection (BCC) protocol
6712 RCV BCC MSG NUM V5LCRBCC
messages
6713 RCV PROTECT MSG NUM Number of the received protection protocol messages V5LCRPTC
6714 RCV V5 MSG NUM Sum of the five items above V5LCRV
6715 SND PSTN MSG NUM Number of the sent PSTN protocol messages V5LCSPTN
6716 SND CTRL MSG NUM Number of the sent control protocol messages V5LCSCTL
6717 SND LCTRL MSG NUM Number of the sent link control protocol messages V5LCSLTL
6718 SND BCC MSG NUM Number of the sent BCC protocol messages V5LCSBCC
6719 SND PROTECT MSG NUM Number of the sent protection protocol messages V5LCSPTC
6720 SND MSG NUM Sum of the five items above V5LCSV
6721 PSTN MSG ERROR NUM Number of the erroneous PSTN protocol messages V5LCEPTN
6722 CTRL MSG ERROR NUM Number of the erroneous control protocol messages V5LCECTL
6723 LINK CTRL MSG ERROR NUM Number of the erroneous link control protocol messages V5LCELTL
6724 BCC MSG ERROR NUM Number of the erroneous BCC protocol messages V5LCEBCC
6725 PROTECT MSG ERROR NUM Number of the erroneous protection protocol messages V5LCEPTC
6726 MSG ERROR NUM Sum of the five items above V5LCEV
3.5.26 V5 B Channel Traffic
MML word: V5B
Object: Certain B channel of certain 2M link
Table 3-75 Measurement of the V5 B channel traffic
Entity
No.
B CHL ORIGINATING CALL ALLOC
3651 Number of the B channels allocated to the originating call V5BCLE
TIMES
AN CONGESTION CALLER ALLOC Times of the failed bearer channel allocation to the originating call due
3652 V5BCLE02
FAILURE TIMES to (cause 1, AN congestion)
HW TS BUSY ORIGINATING ALLOC Times of the failed bearer channel allocation to the originating call due
3653 V5BCLEO4
FAILURE TIMES to (cause 2, connection to another port exists in the V5 TS)
INVALID TS ID ORIGINATING ALLOC Times of the failed bearer channel allocation to the originating call due
3654 V5BCLE0C
FAILURE TIMES to (cause 3, invalid V5 TS ID)
3-78
Entity
No.
INVALID LINK ID ORIGINATING Times of the failed bearer channel allocation to the originating call due
3655 V5BCLE0D
ALLOC FAILURE TIMES to (cause 4, invalid V5 2048 Kbit/s link ID)
V5 TS AS PHY C CHL ORIGINATING Times of the failed bearer channel allocation to the originating call due
3656 V5BCLE0F
ALLOC FAILURE TIMES to (cause 5, V5 TS is being used as the physical C channel)
LINK UNAVAIL ORIGINATING ALLOC Times of the failed bearer channel allocation to the originating call due
3657 V5BCLE10
FAILURE TIMES to (cause 6, unavailable V5 link (congestion))
NO PSN PROVIDED ORIGINATING Times of the failed bearer channel allocation to the originating call due
3658 V5BCLE0B
ALLOC FAILURE TIMES to (cause 7, subscriber port not specified)
INVALID PORT TS ID ORIGINATING Times of the failed bearer channel allocation to the originating call due
3659 V5BCLE0E
ALLOC FAILURE TIMES to (cause 8, invalid subscriber port TS ID)
NOT SPECIFY REASON
Times of the failed bearer channel allocation to the originating call due
3660 ORIGINATING ALLOC FAILURE V5BCLE00
to (cause value not specified)
TIMES
CALLER ORIGINATING ALLOC Times of the failed bearer channel allocation to the originating call due
3661 V5BCLERJ
FAILURE TIMES to the eight cause values above
B CHL TERMINAL CALL ALLOC
3662 Number of the B channels allocated to the terminating call V5BCLD
TIMES
AN FAULT TERMINAL ALLOC Times of the failed bearer channel allocation to the terminating call due
3663 V5BCLD01
FAILURE TIMES to (cause 1, AN failure)
AN CONGESTION TERMINAL ALLOCTimes of the failed bearer channel allocation to the terminating call due
3664 V5BCLD02
FAILURE TIMES to (cause 2, AN congestion)
Times of the failed bearer channel allocation to the terminating call due
PSN BUSY TERMINAL ALLOC
3665 to (cause 3, connection to another V5 interface exists in the subscriber V5BCLD03
FAILURE TIMES
port)
V5 TS AS PHY C CHL TERMINAL Times of the failed bearer channel allocation to the terminating call due
3666 V5BCLD0F
ALLOC FAILURE TIMES to (cause 4, V5 TS is being used as the physical C channel)
LINK UNAVAIL TERMINAL ALLOC Times of the failed bearer channel allocation to the terminating call due
3667 V5BCLD10
FAILURE TIMES to(cause 5, unavailable V5 link (congestion))
NO PSN PROVIDED TERMINAL Times of the failed bearer channel allocation to the terminating call due
3668 V5BCLD0B
ALLOC FAILURE TIMES to(cause 6, subscriber port not allocated)
NO PSN AVAIL TERMINAL Times of the failed bearer channel allocation to the terminating call due
3669 V5BCLD06
ALLOCATE FAILURE TIMES to(cause 7, unavailable subscriber port)
HW TS BUSY TERMINAL ALLOC Times of the failed bearer channel allocation to the terminating call due
3670 V5BCLD04
FAILURE TIMES to(cause 8, connection to another port exists in the V5 TS)
INVALID TS ID TERMINAL ALLOC Times of the failed bearer channel allocation to the terminating call due
3671 V5BCLD0C
FAILURE TIMES to(cause 9, invalid V5 TS ID)
INVALID LINK ID TERMINAL ALLOC Times of the failed bearer channel allocation to the terminating call due
3672 V5BCLD0D
FAILURE TIMES to (cause 10, invalid V5 2.048 Mbit/s link ID)
INVALID PORT TS ID TERMINAL Times of the failed bearer channel allocation to the terminating call due
3673 V5BCLD0E
ALLOC FAILURE TIMES to (cause 11, invalid subscriber port TS ID)
NOT SPECIFY REASON TERMINAL Times of the failed bearer channel allocation to the terminating call due
3674 V5BCLD00
ALLOC FAILURE TIMES to (cause value not specified)
Times of the failed bearer channel allocation to the terminating call due
3675 TERMINAL ALLOC FAILURE TIMES V5BCLDFL
to the 12 cause values above
Sum of the times that the bearer channel is allocated to the originating
3676 ALLOC B CHL TIMES V5BALC
and terminating call
3677 ALLOC SUCCESS TIMES Times of the ALLOCATION COMPLETE allocated to the call V5BSUC
3678 TOTAL LASTING DURATION Duration sum of each bearer channel being in the working state V5BT
B CHL AVERAGE SEIZURE It is the occupancy duration of the call to the bearer channel divided by
3680 V5BAST
DURATION the times that the bear channel is in working state.
1 - total duration of the occupancy of the B channel divided by the
3681 B CHL AVAIL RATIO measurement period*30) (30 is the approximate value of the 2 Mbit/s V5BAVAR
interface B channel)
3-79
3.5.27 MTP Police Message Traffic
Meaning: Measures discarded message according to a specific mtp police condition
MML word: MMP
Object: MTP Police Message
Table 3-76 Measurement of the MTP police message traffic

5864 DISCARDED MESSAGE NUMBER Number of discarded message DMN
3.5.28 SCCP Police Message Traffic
Meaning: Measures discarded message according to a specific sccp police condition
MML word: SMP
Object: SCCP Police Message
Table 3-77 Measurement of the SCCP police message traffic

5874 DISCARDED MESSAGE NUMBER Number of discarded SCCP message DSMN
3.6 Measurement of Call Record
3.6.1 Dispersion Duration Traffic
Meaning: Acquires detailed information of the call process.
MML word: DISP
Object: Inlet (INLET), outlet (OUTLET), call attribute (SVN), destination code (CD)
and calling number (CID)
3-80
Result type & other attributes: Long result; measurement on the sampling rate and
sampling times.
Table 3-78 Measurement of the traffic dispersion and duration

7151 INLET MODULE ID Inlet module number IMID
7152 INLET DEVICE ID DID of the inlet equipment IDID
7153 INLET TRUNK GROUP ID Inlet trunk group number ITG
7154 INLET DEVICE BSN BSN of the inlet equipment IBSN
7155 INLET SEIZURE INSTANT Time of the inlet occupied ISTN
7156 CALLER CODE1 1st~8th digits of the caller number CR1
7157 CALLER CODE2 9th~16th digits of the caller number CR2
7159 DESTCODE1 1st ~8th digits of the destination code CD1
7160 DESTCODE2 9th~16th digits of the destination code CD2
7161 DESTCODE3 17th~24th digits of the destination code CD3
7162 OUTLET MODULE ID Outlet module number OMID
7163 OUTLET DEVICE ID DID of the outlet equipment ODID
7164 OUTLET TRUNK GROUP ID Outlet trunck group number OTG
7165 OUTLET DEVICE BSN BSN of outlet device OBSN
7166 OUTLET SEIZURE INSTANT Time of the outlet occupied OSTN
7167 ADDRESS COMPELETE INSTANT Time at which the complete address signal is received ADRCMPTN
7168 ANSWER INSTANT Time at which the answering signal is received ANSTN
7169 CALL RELEASE INSTANT Time of call release RLSTN
7170 INLET RELEASE INSTANT Time at which the inlet is released IRLSTN
3.6.2 Service Quality Traffic
Meaning: By the analysis of the call process, we can know the response speed of the
switch and the call process and service quality in the light of subscribers.
MML word: SVCQUA
and calling number (CID).
Result type & other attributes: Long result; measurement on the sampling rate and
sampling times.
Table 3-79 Measurement of the service quality

7451 INLET MODUAL ID Inlet module number IMID
7452 INLET DEVICE ID DID of the inlet equipment IDID
7453 INLET TRUNK GROUP ID Inlet trunck group number ITG
7454 INLET DEVICE BSN BSN of the inlet equipment IBSN
7455 INLET SEIZURE INSTANT Time of the inlet occupied ISTN
7456 CALLER CODE1 1st~8th digits of the caller number CR1
3-81

7459 DIALING CODE1 1st~8th digits of the dialed number DN1
7460 DIALING CODE2 9th~16th digits of the dialed number DN2
7461 DIALING CODE3 17th~24th digits of the dialed number DN3
7462 OUTLET MODULE ID Outlet module number OMID
7463 OUTLET DEVICE ID ID of outlet device ODID
7464 OUTLET TRUNK GROUP ID Outlet trunck group number OTG
7465 OUTLET DEVICE BSN BSN of outlet device OBSN
7466 FAILURE REASON Failure reason FLRSN
7467 SUBROUTE SELECT Sequence of the sub-routing selection on the completion of the call SUBRUSL
7468 OUTLET SEIZURE INSTANT Time of the outlet seizure OSTN
7469 ADDRESS COMPELETE INSTANT Time at which the complete address of the local or trunk is received ADRCMPTN
7470 ANSWER SIGNAL INSTANT Time at which the answer signal is received ANSTN
7471 CALL RELEASE INSTANT Time at which the call is released RLSTN
7472 CALL ATTEMPT RESULT Result of the call attempt: succeeded or failed PEGSRLT
3.6.3 Complete Ratio Traffic
Meaning: Offers data of call completion quality in the light of subscribers.
MML word: CMPR
Object: All users and trunks (TLURTK)
Table 3-80 Measurement of the complete ratio traffic
Entity
No.
Rate of the calls with the complete number or times that the incoming trunk
812 VALID ADDRESS CALL RATIO ADRR
has complete address information to all call attempts
813 CONNECTED RATIO Rate of the connected calls to all call attempts CNTR
814 ANSWER RATIO Rate of the completed calls to all call attempts ANSR
815 VALID ADDRESS CALL RATIO Rate of the call with the complete number or complete incoming trunk address ADRR
information to all call attempts
816 CONNECTED RATIO Rate of the connected call to all call attempts CNTR
817 ANSWER RATIO Rate of the completed call to all call attempts ANSR
3.6.4 Multi Condition Object Traffic
Meaning: By the condition of inlet, outlet, destination code, call attribute, calling
number and failure reason, define the calls to be measured
MML word: MICDT
3-82
and calling number (CID)
Result type & other attributes: Long result; sampling rate measurement.
Table 3-81 Measurement of the multi-condition object traffic
Entity
No.
Number of call attempts performed for the call flow complying with the combined
condition.
7752 SEIZURE TIMES Number of the busy call flows complying with the combined conditions. SEIZ
CALL CONNECTED Times of the ring back tone sent while the call complying with the combined
7753 CNT
TIMES condition is connected through the overall network.
7754 ANSWER TIMES Number of the answered calls while it is connected to the whole network. ANS
For the call flow complying with the combined condition as described above, it
7755 SEIZURE DURATION refers to the duration starting from the occupancy to the hanging on of one side or SEIZT
both sides.
After the called picking up the phone, it is the duration starting from the
7756 ANSWER DURATION ANST
occupancy to the hanging on of one side or both sides.
AVERAGE SEIZURE
7757 It equals the busy duration divided by the number of occupancies. AST
DURATION
AVERAGE ANSWER
7758 It equals the answering duration divided by the number of answers. AANST
DURATION
NS SET CONFLICT The cause code is sent when the supplementary service registered by the user
7759 NSSETCFT
TIMES conflicts with the registered service.
The cause code is sent when the subscriber successfully registers the
7760 NS SET OK TIMES NSSETOK
The cause code is sent when the subscriber fails to register the supplementary
7761 NS SET FAILURE TIMES NSSETFL
service.
The cause code is sent when the subscriber successfully clears the
7762 NS CANCEL OK TIMES NSCANOK
NS CANCEL FAILURE The cause code is sent when the subscriber fails to cancel the registered
7763 NSCANFL
The cause code is sent when the subscriber releases the call after verifying the
7764 NS VERIFY OK TIMES NSTSTOK
NS VERIFY FAILURE The cause code is sent when the subscriber releases the call after failing to verify
7765 NSTSTFL
TIMES the registered supplementary service.
The cause code is sent when the subscriber releases the call after using the
7766 NS USE OK TIMES NSUSOK
The cause code is sent when the subscriber releases the call after failing to use
7767 NS USE FAILURE TIMES NSUSFL
the registered supplementary service.
The reason code is sent when the subscriber gets related information after
7768 NS MCT OK TIMES MCTOK
employing the malicious call tracing service.
The reason code is sent when the subscriber fails to get related information after
7769 NS MCT FAILURE TIMES MCTFL
employing the malicious call tracing service.
NS ABSENT USER The reason code is sent when the connection of the call originated by the caller
7770 NSABS
TIMES fails due to the absent service set by the called.
The reason code is sent when the connection of the call originated by the caller
7771 NS NO DISTURB TIMES NSND
fails due to the do-not-disturb service set by the called.
SWITCHING
The cause code is sent to indicate that its source switching equipment is in the
7772 EQUIPMENT SEC
high-traffic period.
CONGESTION TIMES
LONG TIME NO DIALING The cause code is sent when the call is released if the user cannot complete the
7773 LTNDG
TIMES dialing in the specified time.
LONG TIME NO ANSWER The cause code is sent when the user provides the alarm indication instead of
7774 LTNANS
TIMES the connection indication during the specified period.
The call is released if the system performance declines after the loss of
7775 SYS FAULT TIMES SYSFL
messages, internal error, message combination failure and so on.
REMOTE TEST OK
7776 The cause code is sent when the self-check to the internal telephone succeeds. RTSTOK
TIMES
3-83
Entity
No.
LONG TIME NO INFO The cause code is sent when the called is released if the user cannot receive the
7777 LTNINF
TIMES news needed in the specified period.
LONG TIME NO RING The cause code is sent when the call does not receive the prompting in the
7778 LTNRG
TIMES specified period.
LONG TIME NO
7779 The cause code is sent when the call does not receive the releasing requirement. LTNRLS
RELEASE TIMES
7780 INBAND SIGNAL TIMES In-band signal INBSIG
7781 COCK FAILURE TIMES The call is released when the connection check fails. COCFL
The cause code is sent when the re-attempt exceeds the threshold because the
EXCEED MAX
7782 switch fails to perform the connection due to the dual seizure in one process of EXREATP
REATTEMPT TIMES
the connection.
ABANDON BEFORE The cause code is sent when the caller is releasing the call before the call
7783 BRGABN
RING TIMES provides the prompting.
ABANDON BEFORE The cause code is sent when the caller is releasing the call after the call provides
7784 ARGABN
ANSWER TIMES the prompting and before provides the non-connection prompting.
The cause code is sent when the call is released due to the prefix barring, NM
7785 CALL BARRING TIMES BAR
barring or other implemented service over the limitation.
SWITCHING
The cause code is sent when the call is released due to the prefix barring, NM
7786 EQUIPMENT FAULT SEFL
barring or other implemented service over the limitation.
TIMES
OPR DISCONNECT The cause code is sent when the call is released due to the prefix barring, NM
7787 OPRDFOK
FORCELY OK TIMES barring or other implemented service over the limitation.
OPR DISCONNECT
The cause code is sent when the operator failed to disconnect a certain call
7788 FORCELY FAILURE OPRDFFL
forcefully.
TIMES
CALLED TOLL BUSY The cause code is sent when the call is released because the called is making a
7789 CTB
TIMES toll call.
CALLED LOCAL BUSY The cause code is sent when the call is released because the called is making a
7790 CLB
TIMES local call.
The cause code is sent when the call is released because of the insufficient
7791 OWNED TIMES OWN
balance.
7792 CODE PORT TIMES The cause code is sent when the call is released because of the number flowing. CDPRT
CONSOLE ABNORMAL
7793 The cause code is sent when the operator console does not run properly. CT0UNS
TIMES
7794 NS RECORD OK TIMES The cause code is sent when the recording to the specified time slot succeeds. NSRECOK
CREDIT ARREARAGE The cause code is sent when the call fails because of the insufficient balance in
7795 CRDOWN
TIMES the credit.
The cause code is sent when the call is released because the called does not
7796 CALLIN BARRING TIMES IBAR
have the authority to receive the incoming call.
7797 NO A1 TIMES Not receiving A1, the indication to send the next bit. NA1
7798 NO A3 TIMES Not receiving A3, the indication to transfer to the B signal. NA3
7799 NO KD TIMES KD, the outlet service attribute, is not available NKD
7800 NO KB TIMES Not receiving KB, the busy/idle indication of the peer end subscriber NKB
REMOTE EQUIPMENT The cause code is sent when the call receives the backward signal A4 (indicating
7801 REPMCG
CONGESTION TIMES the opposite end congestion).
The cause code is sent when the call is released due to unknown reasons, for
7802 CALL FAILUER TIMES CLFL
example, receiving CFL.
The cause code is sent when the call is released due to the outgoing call
7803 DUAL SEIZURE TIMES DSEIZ
occupies the same trunk circuit as that of the call from the opposite end.
It indicates that the destination required by the caller cannot be reached because
INVALID CODE FORMAT
7804 the called cannot be located with the number or the number contains message INVCD
TIMES
not complying with the called party.
REMOTE PASSWD The user fails to modify the password of the other terminal by originating the call
7805 RPSWUPFL
UPDATE FAILURE TIMES locally.
REMOTE PASSWD The user succeeds in modifying the password of the other terminal by originating
7806 RPSWUPOK
UPDATE OK TIMES the call locally.
REMOTE LOGIN CF OK The user succeeds in registering the forwarding service by originating the call
7807 RREGCFOK
TIMES locally.
REMOTE LOGIN CF
7808 The user fails to register the forwarding service by originating the call locally. RREGCFFL
FAILURE TIMES
3-84
Entity
No.
REMOTE CANCEL CF OK The user succeeds in canceling the registration of the forwarding service by
7809 RCANCFOK
TIMES originating the call locally.
REMOTE CANCEL CF The user fails to cancel the registration of the forwarding service by originating
7810 RCANCFFL
FAILURE TIMES the call locally.
7811 CALLED OWNED TIMES The cause code is sent when the call fails due to charge-owing. CLDOWN
The cause code is sent when the call is released because the user inputs the
7812 PASSWD ERROR TIMES erroneous password in setting, modifying or canceling the password or deploying PSWER
the service that needs a password.
The cause code is sent when the call is released because the forwarding service
TRANSFER BARRED
7813 exceeds the threshold in one connection or the necessary information of the TRNBAR
TIMES
forwarding service is lost.
MODULE NOT The cause code is sent when the state of the module is not normal in transmitting
7814 MNARV
INACCESSIBLE TIMES the message to another module (for example, the called is in another module).
NETMANAGER BARRED
7815 The cause code is sent when the call fails to deploy nine types of NM commands. NMNBAR
TIMES
CALL QUEUE FAILURE The cause code is sent when the call cannot be inserted into the call queue
7816 QFL
TIMES because the call queue is full.
GRP QUEUE FAILURE The cause code is sent when the call cannot be inserted into the group upstream
7817 GRPQFL
TIMES call queue because the call queue is full.
TIMEOUT IN QUEUE The cause code is sent when the call is released because of the response
7818 QTOU
TIMES overtime after the call enters two queues.
The cause code is sent when the CPU occupancy rate exceeds the set
7819 CPU OVERLAP TIMES CPUOL
congestion threshold or overloading threshold.
The cause code is sent when the CR resource is not sufficient for the call
7820 NO CR TIMES received or originated on the subscriber side (contrary to the CCB on the network NCR
side).
The cause code is sent when the CCB resource is not sufficient for the call
7821 NO CCB TIMES received or originated on the network side (contrary to the CR on the subscriber NCCB
side).
7822 NO HW TIMES The cause code is sent when the time slot is not sufficient. NHW
The cause code is sent when the number receiver cannot provide sufficient
7823 NO DTMF TIMES NDTMF
resources.
7824 NO MFC TIMES The cause code is sent when the MF register cannot provide sufficient resource. NMFC
7825 NO DTR TIMES The cause code is sent when the DTR resource is not sufficient NDTR
7826 NO CT0 TIMES The cause code is sent when the operators are not sufficient. NCT0
NO INTERMODULE
7827 The cause code is sent when the inter-module circuits are totally busy. NIPH
PATH TIMES
NO CONFERENCE CALL The cause code is sent when the conference telephones (for the three-party
7828 NCONF
RESOURCE TIMES service) are not sufficient.
The cause code is sent when the V5 subscriber cannot apply for the channel to
7829 NO V5B TIMES NV5B
the switch.
NO DIALING ABANDON The cause code is sent when the user hangs on not dialing (listening to the
7830 NDGABN
TIMES dialing tone).
NO DIALING TIMEOUT The cause code is sent for the timeout when the user hangs on not dialing
7831 NDGTOU
TIMES (listening to the dialing tone).
PARTIAL DIALING
7832 The cause code is sent when the caller hangs on before the dialing times out. PDABN
ABANDON TIMES
PARTIAL DIALING The cause code is sent when the dialing times out before the completion of the
7833 PDTOU
TIMEOUT TIMES dialing.
SIGNALING ERROR
7834 The cause code is sent when the SS7 or CAS goes wrong. SIGER
TIMES
MONEY NOT ENOUGH The cause code is sent when the call is released due to insufficient funds in
7835 CRDNMNY
TIMES campus prepaid cards.
BW LIST BARRING The cause code is sent when the call fails due to the registration of the black and
7836 BWLB
TIMES white list service.
7837 CLI NOT MATCH TIMES The cause code is sent when the CLI does not match. CLINM
7838 UNKNOWN TIMES The cause code is sent when the switch initializes the releasing reason. UKNWRSN
It indicates that the call cannot reach the destination required by the caller
UNALLOCATE CODE
7839 because the number is not allocated (not determined) though the number format UALCCD
TIMES
is valid.
3-85
Entity
No.
It indicates that the equipment sending the reason has been required by the
NO ROUTE TO indirect call transferred by the special unrecognized switching network. The
7840 SPECIFIED reason that the equipment cannot recognize the equipment is that the switching NRUTOSI
INTERNETWORK TIMES network does not exist or the network does not provide any service to the
network. The network determines the decision.
It indicates that the call cannot reach the called because the network the call
NO ROUTE TO
7841 passes through does not provide the service to the required terminal. The NRUTOTE
TERMINAL TIMES
network determines the decision.
SND PRIVATE TONE It indicates that the reason the call cannot reach the called is that the caller
7842 SPRVTONE
TIMES returns the special signal tone.
ERROR INCLUDE TOLL It indicates that the transferring prefix of the called number contains error
7843 ERLNGPFX
PREFIX TIMES information.
ROUTE UNACCEPTABLE It indicates that the transmitting entity does not accept the channel with the new
7844 RUUAPT
TIMES identification in the call.
CALL TRANSMIT ON
It indicates that the call has been transmitted to the user together with other
7845 ESTABLISHED ROUTE CHEDRE
similar calls in the established channel.
TIMES
It indicates that the call is being cleared because one of the users concerned
NORMAL CALL CLEAR
7846 requires the release. However, the network will not transmit the cause code in NORCLR
TIMES
normal cases.
The cause code is sent when the called gives an indication of not receiving
7847 BUSY TIMES BSY
another call.
The cause code is sent when the called does not respond to the established call
7848 NO RESPOND TIMES NRSP
in the specified time with the promoting or connection indication.
The cause code is sent when the user provides the prompting indication but the
7849 NO ACK TIMES NACK
connection indication in the specified time.
The cause code is sent when the equipment transmitting the reason does not
want to receive the call, though it can. The network generates the reason. It
7850 CALL REJECTED TIMES REJ
indicates that the call is cleared due to the limitation of the supplementary
service.
The cause code is sent to the caller when the called number cannot be allocated
again. The new called number may be included in the diagnostic field as an
7851 CODE CHANGED TIMES CDCHD
optional item. If the network does not support the capability, the cause code "129,
unallocated number" will be sent out.
CLEAR UNSELECTED
7852 It indicates that the user cannot get the incoming call. CLRUSL
USER TIMES
The reason indicates that the call cannot reach the receiving end specified by the
TERMINAL ERROR
7853 caller because the interface of the receiving end does not work properly, that is, TEER
TIMES
the signaling message cannot be transmitted to the remote user.
INVALID FORMAT OR
It indicates that the call cannot reach the called because of the erroneous format
7854 ADDRESS NOT ENOUGH INVADR
of the called number or the incomplete number.
TIMES
FACILITY REJECTED The cause code is sent when the network cannot provide the performance
7855 FACREJ
TIMES required by the user.
RESPONSE TO STATUS The reason of generating the STATUS message is that the STATUS ENQUIRY
7856 RSPSE
ENQUIRY TIMES message firstly received contains the message.
The reason is used to report a normal event when there is no other applicable
7857 NORMAL TIMES NOR
reason of normal type.
NO CIRCUIT AVAIL
7858 It indicates that there is no appropriate circuit/channel to process the call. NCIR
TIMES
NETWORK ERROR
7859 It indicates that there is no appropriate circuit/channel to process the call. NETER
TIMES
It indicates that the network does not work properly and this state will not be very
7860 TEMP ERROR TIMES TMPER
long. For example, the user will almost surely originate/receive another call.
SWITCH FACILITY It indicates that the switching equipment generating the reason is in the
7861 EPMCG
CONGESTION TIMES high-traffic service period.
It indicates that the network cannot submit the accessing information to the
ACCESS INFO LOST
7862 remote user, such as the user-user information, low-level compatibility, high-level AIL
TIMES
compatibility or sub-address information.
3-86
Entity
No.
NO ROUTE OR CIRCUIT
The cause code is sent when the interface on the other side cannot provide the
7863 APPLIED AVAILABLE NRUCIR
circuit or channel required by the entity.
TIMES
NO RESOURCE The reason is used to report a resource unavailable event only when there is no
7864 NRSC
AVAILABLE TIMES other applicable reason of resource unavailable.
It is used to report that the service quality defined in Recommendation X.213 is
NO SUITABLE SERVICE
7865 not available (for example, cannot support the handling capacity or transfer NSSQUA
QUALITY TIMES
delay).
It indicates that the network cannot provide the required supplementary service
FACILITY APPLIED NOT
7866 because the user has not completed the management procedures necessary for FACNPV
PRESERVED TIMES
enjoying the service.
CUG INCOMING GRP It indicates that the caller is a member of CUG that is capable of receiving the
7867 CALL UNALLOWED incoming call. However, that member is not permitted to receive the incoming CUGUALW
TIMES call.
BEARER CAPABILITY It indicates that the user is not permitted to employ the bearer capability that has
7868 BCUNP
NOT PERMITTED TIMES been deployed by the equipment generating the reason.
NO BEARER
It indicates that there is no bearer capability available though the equipment
7869 CAPABLILITY NBC
generating the reason has deployed it.
AVAILABLE TIMES
NO SUITABLE SERVICE
It is used to report that there is no applicable service or optional project when
7870 OR OPTIONAL PROJECT NSS
there is no other applicable reason employed for it.
TIMES
BEARER CAPABILITY It indicates that the equipment sending the reason does not support the required
7871 BCNLO
NOT LAYOUT TIMES bearer capability.
ROUTE TYPE NOT It indicates that the equipment sending the reason does not support the channel
7872 RTNLO
LAYOUT TIMES type.
FACILITY APPLIED NOT It indicates that the equipment sending the reason does not support the required
7873 FACNLO
LAYOUT TIMES supplementary service.
LIMITED DIGITAL INFO
It indicates that the caller has applied for an unlimited bearer service. However,
7874 BEARER CAPABILITY LTDDIBC
the equipment sending the message can only support the limited bearer service.
TIMES
SERVICE OR OPTIONAL
It is used to report a service or optional project unimplemented event when there
7875 PROJECT NOT LAYOUT SOPNLO
is no other applicable reasons employed for it.
TIMES
INVALID CALL It indicates that the message received by the equipment sending the reason
7876 INVCR
REFERRENCE TIMES contains the call reference not employed by the existing user-network interface.
ROUTE IDENTEFIER It indicates that the equipment sending the reason message receives a call
7877 RUNEXT
NOT EXIST TIMES requiring to use the inactivated channel at the interface.
SUSPENDED CALL
It indicates that the call ID in trying to restore the call is different from that in the
7878 DIFFER FROM CALL ID SUSC
pause.
TIMES
It indicates that the network receives a pause requirement that contains a call ID
CALL IDENTIFIER IS
7879 that has been used by a paused call of those possibly restored within a certain IDUS
USING TIMES
interface range (including no call ID).
It indicates that the network receives a call restoring requirement that contains
NO SUSPENDED CALL
7880 call ID information unit that does not indicate any paused call of those possibly NSUSC
TIMES
restored within a certain interface range.
CALL WITH CALL ID It indicates that the network receives a call restoring requirement indicating that a
7881 APPLIED CLEARED paused call indicated by the call ID information unit has been cleared in the IDCLR
TIMES pause (network transmission overtime or cleared by the remote user).
CALLED IS NOT CUG It indicates that the called of an incoming CUG call is not a member of a specific
7882 CLDNOCUG
TIMES CUG or the caller is only a common user.
It indicates that the equipment sending the reason message has received a call
TERMINAL
7883 set-up requirement. However, the call has inapplicable low-level compatibility, TEUCPT
UNCOMPATIBLE TIMES
high-level compatibility or other compatibility (for example, transmission rate).
INVALID TRANSMIT
It indicates that the switching network ID is not in the valid format defined in the
7884 NETWORK SELECTION INVTNL
appendix C.
TIMES
It is used to report an invalid event only when other reasons of the invalid
7885 INVALID MSG TIMES INVMSG
message type are employed.
3-87
Entity
No.
It indicates that the equipment sending the reason has received a message with
NECESSARY INFO
7886 a missing information unit that should be available before the processing of the NCSIELST
ELEMENT LOST TIMES
message.
MSG TYPE NOT EXIST
7887 whose type is not recognizable because the type is not defined or is defined but MSGNEXT
NOT LAYOUT TIMES
the equipment seeding the message has not implemented it.
It indicates that the equipment sending the reason has received a message that
MSG STATUS ERROR should have not been received in the call state, indicated by the program. Or the
7888 MSGSTAER
OR MSG ERROR TIMES equipment sending the reason receives a STATUS message that indicates
incompatible call state.
INFO ELEMENT NOT containing an unrecognizable information unit because the information unit ID
7889 EXIST NOT LAYOUT has not been defined or the equipment sending the reason has not implemented IEUEXT
TIMES it though it is defined. The information unit is not necessary for the equipment
processing the unit.
It indicates that the equipment sending the reason has received an implemented
INVALID INFO ELEMENT
7890 information unit but it does not implement the coding of one or multiple fields in INVIE
CONTENT TIMES
the unit.
MSG UNFIT TO CALL
7891 It indicates that a message not in compliance with the state is received. MSGUFT
STATUS TIMES
TIMER TIMEOUT It indicates that a program related to the error processing program in
7892 TRCV
RECOVERY TIMES Recommendation Q.931 starts due to the timer overtime.
PARAMETER NOT EXIST It indicates that the equipment sending the reason has discarded an
7893 PARANEXT
TIMES unrecognizable parameter.
ORDINARY It indicates that the idle circuit is reserved for the high-priority user instead of the
7894 ORNCG
CONGESTION TIMES common user. The cause code is sent on the receipt of A9.
PROTOCOL ERROR
7895 It reports the protocol error event. PTLER
TIMES
7896 BUTT TIMES The failure reason is invalid because it is beyond the threshold. BUTT
It indicates that the network is connecting to a network that provides no reason
7897 INTERWORK TIMES for the network action. Therefore, the accurate reason for sending the message INTWRK
is not available.
3.7 Inner Running Measurement
3.7.1 SM Flow Traffic
Meaning: Measures the traffic of every SM in a certain traffic flow direction.
MML word: SMFW
Object: Traffic flow direction of SM, comprising Intra-module (INTM) and Outgoing
module (OM) flow directions.
3-88
Table 3-82 Measurement of the SM traffic
Entity MML
Entity name Meaning
No. word
SM FLOW CALL ATTEMPT Number of call attempts in the traffic flow direction of the SM within the statistic
3851 PEGS
TIMES period
Number of succeeded call attempts in the traffic flow direction of the SM within the
3852 CALL SUCCESS TIMES SUC
statistic period
3853 SEIZURE TRAFFIC Traffic transmitted in the traffic flow direction of the SM within the statistic period SERL
3.7.2 Inter-module Distribution Traffic
Meaning: Measures the inter-SM traffic.
MML word: INTMDISP
Object: Two SMs, namely, incoming SM (ISM) and outgoing SM (OSM).
Table 3-83 Measurement of the inter-SM traffic
Entity
No.
8401 CALL ATTEMPT TIMES Number of call attempts from a certain SM to another within the statistic period PEGS
8402 SEIZURE TIMES Number of established calls between the two SMs within the statistic period SUC
8403 TRAFFIC Traffic of such type of calls within the statistic period ERL
8404 INTERMODULE FLOW Communication traffic between two modules within the statistic duration INTMFW
3.7.3 RSA Interface Traffic
Meaning: Measures the running of every RSA 2 Mbit/s interface.
MML word: RSAITF
Object: 2 Mbit/s interface of certain RSA (RSA2M)
Table 3-84 Measurement of the RSA interface traffic
Entity MML Entity

Entity name Meaning
No. word threshold
Total number of the messages received/sent at the Remote
3951 RCV SND MSG NUM RSMSG
Subscriber Access (RSA) interface
3952 HW SEIZURE RATIO The ratio of the HWs occupied by the call to all HWs available. HWSR (5, 95)
3-89
Entity MML Entity

Entity name Meaning
No. word threshold
INTERFACE INTERRUPT Number of the RSA interface disconnection due to the error or
3954 ITFITR (0, 5)
TIMES congestion, and so on.
INTERFACE INTERRUPT Total duration of the RSA interface disconnection due to the error or
3955 ITFITRT (0, 10)
DURATION congestion, and so on.
INTERFACE CONGESTION Times of the congestion due to no idle speech path available at the
3957 ITFCG (0, 5)
TIMES RSA interface
INTERFACE CONGESTION Total duration from the congestion occurrence to the end of the
3958 ITFCGT (0, 10)
DURATION congestion
INTERFACE SWITCHOVER
3960 Number of the RSA interface switchovers ITFTUN (0, 5)
TIMES
Percentage of the available HWs to all HWs, including the idle
3961 CIRCUIT AVAIL RATIO CIRUSR (90, 100)
speech paths and that seized by the call
3.8 Measurement of Maximum/Minimum Values & Charging
3.8.1 Top Usage User Traffic
Meaning: Offers reference to solve busy condition, improve call completing rate &
service quality by conducting statistic analysis of unusual busy subscribers in an
office or some subscriber line group.
MML word: TPERL
Object: Subscriber set with maximum or minimum values, divided according to the
Centrex group, module, subscriber category or all subscribers.
Table 3-85 Measurement of the unusual busy subscribers

9001 DNSET1 Number initial set of the first unusual busy subscriber DSET1
9002 OUTCODE1 External code of the first unusual busy subscriber SN1
9003 OUTCODE1-AUX External code of the first unusual busy subscriber(AUX) SN1A
9004 SEIZURE DURATION1 Busy duration of the first unusual busy subscriber SEIZT1
9005 DNSET2 Number initial set of the second unusual busy subscriber DSET2
9006 OUTCODE2 External code of the second unusual busy subscriber SN2
9007 OUTCODE2-AUX External code of the second unusual busy subscriber(AUX) SN2A
9008 SEIZURE DURATION2 Busy duration of the second unusual busy subscriber SEIZT2
9009 DNSET3 Number initial set of the third unusual busy subscriber DSET3
9010 OUTCODE3 External code of the third unusual busy subscriber SN3
9011 OUTCODE3-AUX External code of the third unusual busy subscriber(AUX) SN3A
9012 SEIZURE DURATION3 Busy duration of the third unusual busy subscriber SEIZT3
9013 DNSET4 Number initial set of the fourth unusual busy subscriber DSET4
9014 OUTCODE4 External code of the fourth unusual busy subscriber SN4
9015 OUTCODE4-AUX External code of the fourth unusual busy subscriber(AUX) SN4A
9016 SEIZURE DURATION4 Busy duration of the fourth unusual busy subscriber SEIZT4
9017 DNSET5 Number initial set of the fifth unusual busy subscriber DSET5
9018 OUTCODE5 External code of the fifth unusual busy subscriber SN5
3-90

9019 OUTCODE5-AUX External code of the fifth unusual busy subscriber(AUX) SN5A
9020 SEIZURE DURATION5 Busy duration of the fifth unusual busy subscriber SEIZT5
9021 DNSET6 Number initial set of the sixth unusual busy subscriber DSET6
9022 OUTCODE6 External code of the sixth unusual busy subscriber SN6
9023 OUTCODE6-AUX External code of the sixth unusual busy subscriber(AUX) SN6A
9024 SEIZURE DURATION6 Busy duration of the sixth unusual busy subscriber SEIZT6
9025 DNSET7 Number initial set of the seventh unusual busy subscriber DSET7
9026 OUTCODE7 External code of the seventh busy subscriber SN7
9027 OUTCODE7-AUX External code of the seventh unusual busy subscriber(AUX) SN7A
9028 SEIZURE DURATION7 Busy duration of the seventh busy subscriber SEIZT7
9029 DNSET8 Number initial set of the eighth unusual busy subscriber DSET8
9030 OUTCODE8 External code of the eighth unusual busy subscriber SN8
9031 OUTCODE8-AUX External code of the eighth unusual busy subscriber(AUX) SN8A
9032 SEIZURE DURATION8 Busy duration of the eighth unusual busy subscriber SEIZT8
9033 DNSET9 Number initial set of the ninth unusual busy subscriber DSET9
9034 OUTCODE9 External code of the ninth unusual busy subscriber SN9
9035 OUTCODE9-AUX External code of the ninth unusual busy subscriber(AUX) SN9A
9036 SEIZURE DURATION9 Busy duration of the ninth unusual busy subscriber SEIZT9
9037 DNSET10 Number initial set of the tenth unusual busy subscriber DSET10
9038 OUTCODE10 External code of the tenth unusual busy subscriber SN10
9039 OUTCODE10-AUX External code of the tenth unusual busy subscriber(AUX) SN10A
9040 SEIZURE DURATION10 Busy duration of the tenth unusual busy subscriber SEIZT10
3.8.2 Top Called Busy Traffic
Meaning: Offers reference to solve busy condition, improve the call completing rate &
service quality by conducting statistic analysis of usually busy called subscribers in an
office or some subscriber line group.
MML word: TPCBSY
Table 3-86 Measurement of usually busy called subscribers
MML
Entity No. Entity name Meaning
word
9251 DNSET1 Number initial set of the first usually busy called DSET1
9252 OUTCODE1 External code of the first usually busy called SN1
9253 OUTCODE1-AUX External code of the first usually busy called(AUX) SN1A
Number of the failed incoming calls due to the called being busy for the first usually
9254 CALLED BUSY TIMES1 CBSY1
busy called
9255 DNSET2 Number initial set of the second usually busy called DSET2
9256 OUTCODE2 External code of the second usually busy called SN2
9257 OUTCODE2-AUX External code of the second usually busy called(AUX) SN2A
Number of the failed incoming calls due to the called being busy for the second
usually busy called
9259 DNSET3 Number initial set of the third usually busy called DSET3
3-91
MML
Entity No. Entity name Meaning
word
9260 OUTCODE3 External code of the third usually busy called SN3
9261 OUTCODE3-AUX External code of the third usually busy called(AUX) SN3A
Number of the failed incoming calls due to the called being busy for the third usually
busy called
9263 DNSET4 Number initial set of the fourth usually busy called DSET4
9264 OUTCODE4 External code of the fourth usually busy called SN4
9265 OUTCODE4-AUX External code of the fourth usually busy called(AUX) SN4A
Number of the failed incoming calls due to the called being busy for the fourth
usually busy called
9267 DNSET5 Number initial set of the fifth usually busy called DSET5
9268 OUTCODE5 External code of the fifth usually busy called SN5
9269 OUTCODE5-AUX External code of the fifth usually busy called(AUX) SN5A
Number of the failed incoming calls due to the called being busy for the fifth usually
busy called
9271 DNSET6 Number initial set of the sixth usually busy called DSET6
9272 OUTCODE6 External code of the sixth usually busy called SN6
9273 OUTCODE6-AUX External code of the sixth usually busy called(AUX) SN6A
Number of the failed incoming calls due to the called being busy for the sixth usually
busy called
9275 DNSET7 Number initial set of the seventh usually busy called DSET7
9276 OUTCODE7 External code of the seventh usually busy called SN7
9277 OUTCODE7-AUX External code of the seventh usually busy called(AUX) SN7A
Number of the failed incoming calls due to the called being busy for the seventh
usually busy called
9279 DNSET8 Number initial set of the eighth usually busy called DSET8
9280 OUTCODE8 External code of the eighth usually busy called SN8
9281 OUTCODE8-AUX External code of the eighth usually busy called(AUX) SN8A
Number of the failed incoming calls due to the called being busy for the eighth
usually busy called
9283 DNSET9 Number initial set of the ninth usually busy called DSET9
9284 OUTCODE9 External code of the ninth usually busy called SN9
9285 OUTCODE9-AUX External code of the ninth usually busy called(AUX) SN9A
Number of the failed incoming calls due to the called being busy for the ninth usually
busy called
9287 DNSET10 Number initial set of the tenth usually busy called DSET10
9288 OUTCODE10 External code of the tenth usually busy called SN10
9289 OUTCODE10-AUX External code of the tenth usually busy called(AUX) SN10A
CALLED BUSY Number of the failed incoming calls due to the called being busy for the tenth usually
9290 CBSY10
TIMES10 busy called
3.8.3 Top Ringed No Answer Traffic
Meaning: Offers reference to solve busy condition, improve the call completing rate &
service quality by conducting statistic analysis of no-reply subscribers in an office or
some subscriber line group.
MML word: TPLTNANS
3-92
Table 3-87 Measurement of no-reply subscribers

9501 DNSET1 Number initial set of the first no-reply subscriber DSET1
9502 OUTCODE1 External code of the first no-reply subscriber SN1
9503 OUTCODE1-AUX External code of the first no-reply subscriber(AUX) SN1A
9504 NO ANSWER TIMES1 Number of not-answered calls of the first no-reply subscriber LTNANS1
9505 DNSET2 Number initial set of the second no-reply subscriber DSET2
9506 OUTCODE2 External code of the second no-reply subscriber SN2
9507 OUTCODE2-AUX External code of the second no-reply subscriber (AUX) SN2A
9508 NO ANSWER TIMES2 Number of not-answered calls of the second no-reply subscriber LTNANS2
9509 DNSET3 Number initial set of the third no-reply subscriber DSET3
9510 OUTCODE3 External code of the third no-reply subscriber SN3
9511 OUTCODE3-AUX External code of the third no-reply subscriber (AUX) SN3A
9512 NO ANSWER TIMES3 Number of not-answered calls of the third no-reply subscriber LTNANS3
9513 DNSET4 Number initial set of the fourth no-reply subscriber DSET4
9514 OUTCODE4 External code of the fourth no-reply subscriber SN4
9515 OUTCODE4-AUX External code of the fourth no-reply subscriber (AUX) SN4A
9516 NO ANSWER TIMES4 Number of not-answered calls of the fourth no-reply subscriber LTNANS4
9517 DNSET5 Number initial set of the fifth no-reply subscriber DSET5
9518 OUTCODE5 External code of the fifth no-reply subscriber SN5
9519 OUTCODE5-AUX External code of the fifth no-reply subscriber (AUX) SN5A
9520 NO ANSWER TIMES5 Number of not-answered calls of the fifth no-reply subscriber LTNANS5
9521 DNSET6 Number initial set of the sixth no-reply subscriber DSET6
9522 OUTCODE6 External code of the sixth no-reply subscriber SN6
9523 OUTCODE6-AUX External code of the sixth no-reply subscriber(AUX) SN6A
9524 NO ANSWER TIMES6 Number of not-answered calls of the sixth no-reply subscriber LTNANS6
9525 DNSET7 Number initial set of the seventh no-reply subscriber DSET7
9526 OUTCODE7 External code of the seventh no-reply subscriber SN7
9527 OUTCODE7-AUX External code of the seventh no-reply subscriber (AUX) SN7A
9528 NO ANSWER TIMES7 Number of not-answered calls of the seventh no-reply subscriber LTNANS7
9529 DNSET8 Number initial set of the eighth no-reply subscriber DSET8
9530 OUTCODE8 External code of the eighth no-reply subscriber SN8
9531 OUTCODE8-AUX External code of the eighth no-reply subscribers (AUX) SN8A
9532 NO ANSWER TIMES8 Number of not-answered calls of the eighth no-reply subscriber LTNANS8
9533 DNSET9 Number initial set of the ninth no-reply subscriber DSET9
9534 OUTCODE9 External code of the ninth no-reply subscriber SN9
9535 OUTCODE9-AUX External code of the ninth no-reply subscriber (AUX) SN9A
9536 NO ANSWER TIMES9 Number of not-answered calls of the ninth no-reply subscriber LTNANS9
9537 DNSET10 Number initial set of the tenth no-reply subscriber DSET10
9538 OUTCODE10 External code of the tenth no-reply subscriber SN10
9539 OUTCODE10-AUX External code of the tenth no-reply subscriber (AUX) SN10A
9540 NO ANSWER TIMES10 Number of not-answered calls of the tenth no-reply subscriber LTNANS10
3.8.4 Top Call Loss Traffic
Meaning: Offers reference to solve busy condition, improve the call completing rate
and service quality by conducting statistic analysis of subscribers with highest call
loss in an office or some subscriber line group.
MML word: TPCL
3-93
Table 3-88 Measurement of subscribers with highest call loss

9751 DNSET1 Number initial set of the first subscriber with highest call loss DSET1
9752 OUTCODE1 External code of the first subscriber with highest call loss SN1
9753 OUTCODE1-AUX External code of the first subscriber with the highest call loss(AUX) SN1A
9754 LOSS TIMES1 Number of failed calls of the first subscriber with highest call loss CL1
9755 DNSET2 Number initial set of the second subscriber with highest call loss DSET2
9756 OUTCODE2 External code of the second subscriber with highest call loss SN2
9757 OUTCODE2-AUX External code of the second subscriber with the highest call loss(AUX) SN2A
9758 LOSS TIMES2 Number of failed calls of the second subscriber with highest call loss CL2
9759 DNSET3 Number initial set of the third subscriber with highest call loss DSET3
9760 OUTCODE3 External code of the third subscriber with highest call loss SN3
9761 OUTCODE3-AUX External code of the third subscriber with the highest call loss(AUX) SN3A
9762 LOSS TIMES3 Number of failed calls of the third subscriber with highest call loss CL3
9763 DNSET4 Number initial set of the fourth subscriber with highest call loss DSET4
9764 OUTCODE4 External code of the fourth subscriber with highest call loss SN4
9765 OUTCODE4-AUX External code of the fourth subscriber with the highest call loss(AUX) SN4A
9766 LOSS TIMES4 Number of failed calls of the fourth subscriber with highest call loss CL4
9767 DNSET5 Number initial set of the fifth subscriber with highest call loss DSET5
9768 OUTCODE5 External code of the fifth subscriber with highest call loss SN5
9769 OUTCODE5-AUX External code of the fifth subscriber with the highest call loss(AUX) SN5A
9770 LOSS TIMES5 Number of failed calls of the fifth subscriber with highest call loss CL5
9771 DNSET6 Number initial set of the sixth subscriber with highest call loss DSET6
9772 OUTCODE6 External code of the sixth subscriber with highest call loss SN6
9773 OUTCODE6-AUX External code of the sixth subscriber with the highest call loss(AUX) SN6A
9774 LOSS TIMES6 Number of failed calls of the sixth subscriber with highest call loss CL6
9775 DNSET7 Number initial set of the seventh subscriber with highest call loss DSET7
9776 OUTCODE7 External code of the seventh subscriber with highest call loss SN7
9777 OUTCODE7-AUX External code of the seventh subscriber with the highest call loss(AUX) SN7A
9778 LOSS TIMES7 Number of failed calls of the seventh subscriber with highest call loss CL7
9779 DNSET8 Number initial set of the eighth subscriber with highest call loss DSET8
9780 OUTCODE8 External code of the eighth subscriber with highest call loss SN8
9781 OUTCODE8-AUX External code of the eighth subscriber with the highest call loss(AUX) SN8A
9782 LOSS TIMES8 Number of failed calls of the eighth subscriber with highest call loss CL8
9783 DNSET9 Number initial set of the ninth subscriber with highest call loss DSET9
9784 OUTCODE9 External code of the ninth subscriber with highest call loss SN9
9785 OUTCODE9-AUX External code of the ninth subscriber with the highest call loss(AUX) SN9A
9786 LOSS TIMES9 Number of failed calls of the ninth subscriber with highest call loss CL9
9787 DNSET10 Number initial set of the tenth subscriber with highest call loss DSET10
9788 OUTCODE10 External code of the tenth subscriber with highest call loss SN10
9789 OUTCODE108-AUX External code of the tenth subscriber with the highest call loss(AUX) SN10A
9790 LOSS TIMES10 Number of failed calls of the tenth subscriber with highest call loss CL10
3.8.5 Top Idle TK Circuit Traffic
MML word: TPTK
3-94
Object: Trunk set with maximum or minimum values, divided according to the module
and trunk.
Table 3-89 Measurement of idlest trunk circuits

9851 TKGRP NO1 Trunk group number of the first idlest trunk circuit TKG1
9852 TKC NO1 Trunk circuit number of the first idlest trunk circuit TK1
9853 SEIZURE DURATION1 Busy duration of the first idlest trunk circuit SEIZT1
9854 TKGRP NO2 Trunk group number of the second idlest trunk circuit TKG2
9855 TKC NO2 Trunk circuit number of the second idlest trunk circuit TK2
9856 SEIZURE DURATION2 Busy duration of the second idlest trunk circuit SEIZT2
9857 TKGRP NO3 Trunk group number of the third idlest trunk circuit TKG3
9858 TKC NO3 Trunk circuit number of the third idlest trunk circuit TK3
9859 SEIZURE DURATION3 Busy duration of the third idlest trunk circuit SEIZT3
9860 TKGRP NO4 Trunk group number of the fourth idlest trunk circuit TKG4
9861 TKC NO4 Trunk circuit number of the fourth idlest trunk circuit TK4
9862 SEIZURE DURATION4 Busy duration of the fourth idlest trunk circuit SEIZT4
9863 TKGRP NO5 Trunk group number of the fifth idlest trunk circuit TKG5
9864 TKC NO5 Trunk circuit number of the fifth idlest trunk circuit TK5
9865 SEIZURE DURATION5 Busy duration of the fifth idlest trunk circuit SEIZT5
9866 TKGRP NO6 Trunk group number of the sixth idlest trunk circuit TKG6
9867 TKC NO6 Trunk circuit number of the sixth idlest trunk circuit TK6
9868 SEIZURE DURATION6 Busy duration of the sixth idlest trunk circuit SEIZT6
9869 TKGRP NO7 Trunk group number of the seventh idlest trunk circuit TKG7
9870 TKC NO7 Trunk circuit number of the seventh idlest trunk circuit TK7
9871 SEIZURE DURATION7 Busy duration of the seventh idlest trunk circuit SEIZT7
9872 TKGRP NO8 Trunk group number of the eighth idlest trunk circuit TKG8
9873 TKC NO8 Trunk circuit number of the eighth idlest trunk circuit TK8
9874 SEIZURE DURATION8 Busy duration of the eighth idlest trunk circuit SEIZT8
9875 TKGRP NO9 Trunk group number of the ninth idlest trunk circuit TKG9
9876 TKC NO9 Trunk circuit number of the ninth idlest trunk circuit TK9
9877 SEIZURE DURATION9 Busy duration of the ninth idlest trunk circuit SEIZT9
9878 TKGRP NO10 Trunk group number of the tenth idlest trunk circuit TKG10
9879 TKC NO10 Trunk circuit number of the tenth idlest trunk circuit TK10
9880 SEIZURE DURATION10 Busy duration of the tenth idlest trunk circuit SEIZT10
3.9 Measurement of IN Service
3.9.1 IN Call Traffic Volume
Meaning: This measure unit measures the IN call attempts and seizure information of
an office.
MML word: INCALL
Object: Service key
3-95
Table 3-90 Measurement of the IN call traffic

It is the times that the caller makes IN calls. As long as a call has undergone
5301 CALL ATTEMPT TIMES the called number analysis and the initial DP has been triggered, it will be PEGS
counted a call attempt regardless of whether it has been put through.
5302 SEIZURE DURATION Duration from caller picking up to call termination SEIZT
AVERAGE SEIZURE
5303 Total seizure time/number of call attempts AVSEIZT
DURATION
3.9.2 IN Incoming Call QoS
Meaning: This measure unit conducts statistic analysis of the IN call connection of an
office.
MML word: INCLIQ
Object: Service key
Table 3-91 Measurement of the IN incoming call QoS

TIMES OF INTELLIGENT CALLER CALL
5751 Times of intelligent caller attempting a call CQCA
ATTEMPT
5752 TIMES OF INTELLIGENT CALLER SEIZURE Times of intelligent caller seizing CQSEIZ
TIMES OF INTELLIGENT CALLER
5753 Times of intelligent caller connected CQC
CONNECTED
TIMES OF INTELLIGENT CALLER
5754 Times of intelligent caller abandoned CQA
ABANDON
5755 TIMES OF REJECTED BY SCP Times of rejected by SCP CQSR
5756 TIMES OF CALL GAPPING Times of call gapping CQCP
5757 TIMES OF CALL FILTERED Times of call filtered CQASF
5758 REJECT CALL BY SSP OVERLOAD TIMES Times of call rejected due to SSP overload CQCO
DURATION OF INTELLIGENT CALLER
5759 Duration of intelligent caller seizure (second) CQSTI
SEIZURE
AVERAGE DURATION OF INTELLIGENT
5760 Average duration of intelligent caller seizure (second) CQAST
CALLER SEIZURE
5761 INTELLIGENT CALLER SEIZURE TRAFFIC Intelligent caller seizure traffic CQSU
RADIO OF INTELLIGENT CALLER CALL Ratio of intelligent caller call completion = Number of
5762 CQCR
COMPLETION completed intelligent caller calls / number of call attempts
3.9.3 IN Session Stat Traffic
Meaning: This measure unit conducts statistic analysis of the IN sessions of an office.
MML word: INDLG
3-96
Object: Office all
Table 3-92 Measurement of the IN session stat traffic

1321 SSF SENDING SESSION TIMES Number of sessions originated from the SSP SDLG
1322 SSF RECEIVING SESSION TIMES Number of sessions originated from the SCP RDLG
SSF SENDING ABORTED SESSION
1323 Number of U-ABORT sessions by the SSP SABDLG
TIMES
SSF RECEIVING ABORTED
1324 Times of SSP receiving P-ABORT and U-ABORT from the SCP RABDLG
SESSION TIMES
It is the duration of FEAM from receiving TC-BEGIN to receiving
1325 TOTAL SESSION DURATION TLDLGT
TC-END during the course of a call.
Number of SSF sending sessions + number of SSF receiving
1327 TOTAL SESSION TIMES TLDLG
sessions
1328 AVERAGE SESSION DURATION Sum of sessions duration/number of sessions AVDLGT
3.9.4 IN Edp Account
Meaning: Conducts statistic analysis of intelligent event detection points.
MML word: INDP
Object: Office all
Table 3-93 Measurement of the IN edp account

NUMBER OF DP1 SENDER AUTHENTICATE CALL
1751 Number of DP1 sender authenticate call attempts DPONE
ATTEMPT
1752 NUMBER OF DP2 COLLECT INFORMATION Times of DP2 collecting information DPTWO
1753 NUMBER OF DP3 ANALYSIS INFORMATION Times of DP3 analyzing information DPTREE
1754 NUMBER OF DP4 ROUTING FAULT Number of DP4 routing faults DPFOR
1755 NUMBER OF DP5 CALLED BUSY Times of DP5 called busy DPFIV
1756 NUMBER OF DP6 NO REPLY Times of DP6 no reply DPSIX
1757 NUMBER OF DP7 ANSWER Times of of DP7 answered DPSEN
1758 NUMBER OF DP8 CALL SUCCEEDED Times of DP8 call succeeded DPEIG
1759 NUMBER OF DP9A CALLER ON-HOOK Times of DP9A caller on-hooked DPNA
1760 NUMBER OF DP9B CALLED ON-HOOK Times of DP9B called on-hooked DPNB
1761 NUMBER OF DP10 CALLER ABANDON Times of DP10 caller abandoned DPTEN
3-97
3.9.5 IN Faulted Reason
Meaning: Conducts statistic analysis of the causes of intelligent service failures.
MML word: INFAIL
Object: Office all
Table 3-94 Measurement of the IN faulted reason

SWITCHING EQUIPMENT Used when the switching equipment is undergoing the high traffic
1401 SEC
CONGESTION density period
1402 LONG TIME NO DIALING Used when the user does not finish dialing within time time limited LTNDG
1403 CALL BARRING Used when the user releases by reason of called barring BAR
1404 TOLL CALLED BUSY Used when calling to a user that is making a toll call CTB
1405 LOCAL CALLED BUSY Used when calling to a user that is making a local call CLB
1406 CALLIN BARRING Used when the called has no callin right IBAR
REMOTE EQUIPMENT Used when the A4 backward (peer congestion) indication is
1407 REPMCG
CONGESTION received
1408 INVALID CODE FORM Used when finding no matched user based on the called number INVCD
Used when the code form is valid but the code is not allocated
1409 UNALLOCATED CODE UALCCD
(used) by now
NO ROUTE TO SPECIFIED Used when the device cannot find a route to the internetwork for
1410 NRUTOSI
INTERNETWORK the detour call
NO ROUTE TO SPECIFIED Used when the caller cannot reach the called user because the
1411 NRUTOTE
TERMINAL network does not support the service for the expected terminal
Used when the caller cannot reach the called because of wanting
1412 SEND PRIVATE TONE SPRVTONE
the called to return the special signal tone
ERROR INCLUDING LONG Used when the called number's transferring prefix is not embedded
1413 ERLNGPFX
DISTANCE correctly
Used when the called cannot accept the incoming call because the
1414 CALLED BUSY BSY
user channel has been occupied
Used when the user receives no alerting or connecting response to
1415 NO RESPONSE NRSP
the establishing call before timeout
Used when the user has received alerting but no connecting before
1416 NO ACKNOWLEDGE NACK
timeout
Used when the sending device is not expecting this call, though it
1417 CALL REJECTED REJ
can. Normally it's generated by the network because of NS conflict.
Used when the called number is no longer used (for example the
called number has changed). The reason is returned to the caller
1418 NUMBER CHANGED with an optional new called number included in the diagnosing CDCHD
field. If the network does not support this capability, this reason
(value 129) will be returned to the caller side.
Used when the terminal state is abnormal or the terminal interface
1419 TERMINAL ERROR TEER
is error and signaling message cannot be sent to the remote user
INVALID CODE FORM OR Used in the case of called unreachable or invalid code form or
1420 INVCDFMT
ADDRESS NOT ENOUGH called number not completely provided
Used when the network cannot provide performance needed by
1421 FACILITY REJECTED FACREJ
the user
1422 NO ROUTE AVAILABLE Used when no circuit/path available for the call NCIR
1423 NETWORK FAULT Used when no circuit/path available for the call due to network fault NETER
Used when the network is in abnormal state for the time being, but
1424 ERROR FOR THE TIME BEING TMPER
will soon recover
3-98

Used when the switching equipment is undergoing the high density
1425 EXCHANGE FACILITY SURGE EPMCG
traffic period
NO ROUTE OR CIRCUIT APPLIED Used when one of the two sides cannot provide the specified
1426 NRUCIR
AVAILABLE circuit/path for the requested entity
Used to report that the network does not support the requested
1427 NO SUITABLE SERVICE QUILITY NSSQUA
service quality (recommended in X.213)
Used to report that the network cannot provide the requested
FACILITY APPLIED NO
1428 supplementary service for reason of user not finishing the FACNPV
PRESERVED
necessary network management procedures
Used to indicate that a member of the CUG can receive the CUG
1429 CUG INCOMING NOT ALLOWED CUGUALW
call, but he cannot receive the incoming call from outside the CUG
Used to indicate that the device has implemented the requested
1430 BEARER CAPABILITY NOT PERMIT BCUNP
bearer capability, but the user is not certificated to use it
Used to indicate that the device has implemented the requested
NO BEARER CAPABILITY
1431 bearer capability, but no available bearer capability can be used NBC
AVAILABLE CURRENTLY
currently
BEARER CAPABILITY NOT Used to indicate that the requested bearer capability is not
1432 BCNLO
LAYOUT supported by the device
Used to indicate that a call cannot be established due to the
1433 TERMINAL UNCOMPATIBLE TEUCPT
terminal incompatible
1434 FAIL TIMEOUT Used to indicate timeout reached FFTT
3.9.6 IN Faulted Statistic
Meaning: This measure unit conducts statistic analysis of the IN failures of an office.
MML word: INFLR
Object: Service key
Table 3-95 Measurement of the IN faulted statistic

REJECTED CALL FOR OVERLOAD
5351 Number of calls which are rejected for overload OVLDREJ
TIMES
FAILURE BEFORE INITIALIZING DP It is the number of failed calls before the INSM of the SSP sends
5352 FBINI
TIMES the IDP.
FAILURE AFTER INITIALIZING DP It is the number of failed calls after the INSM of the SSP sends the
5353 FAINI
TIMES IDP but before the SCP receives the IDP.
SSF RECEIVING REJECTED
5354 Times of SSF receiving the rejected sessions SSFRREJ
SESSION TIMES
3-99
3.9.7 SRF Global Resource Traffic
Meaning: This measure unit counts the times that the system has successfully
allocated global resources or failed to allocate them.
MML word: INOFSRF
Object: Destination module number
Table 3-96 Measurement of the SRF global resource traffic

5251 INSM APPLYING SRM TIMES Times of INSM applying for SRM INSMSRM
5252 INSM APPLYING SRM SUCCESS TIMES Times of INSM succeeded in applying for SRM INSMSRMS
5253 INSM APPLYING SRM FAILURE TIMES Times of INSM failed to apply for SRM INSMSRMF
5254 BCSM APPLYING SRM TIMES Times of BCSM applying for SRM BCSMSRM
5255 BCSM APPLYING SRM SUCCESS TIMES Times of BCSM succeeded in applying for SRM BCSMSRMS
5256 BCSM APPLYING SRM FAILURE TIMES Times of BCSM failed to apply for SRM BCSMSRMF
5257 SRM APPLYING SRM TIMES Times of SRM applying for SRM SRMSRM
5258 SRM APPLYING SRM SUCCESS TIMES Times of SRM successfully applied for SRM SRMSRMS
5259 SRM APPLYING SRM FAILURE TIMES Times of SRM failed to apply for SRM SRMSRMF
5260 ALLOCATING SPT TIMES Times of allocating SPT SRFSPT
5261 ALLOCATING SPT SUCCESS TIMES Times of succeeded in allocating SPT SRFSPTS
5262 ALLOCATING SPT FAILURE TIMES Number of failures in allocating SPT SRFSPTF
5263 ALLOCATING AIN TIMES Times of allocating AIN SRFAIN
5264 ALLOCATING AIN SUCCESS TIMES Times of succeeded in allocating AIN SRFAINS
5265 ALLOCATING AIN FAILURE TIMES Number of failures in allocating AIN SRFAINF
5266 ALLOCATING DIN TIMES Times of allocating DIN SRFDIN
5267 ALLOCATING DIN SUCCESS TIMES Times of succeeded in allocating DIN SRFDINS
5268 ALLOCATING DIN FAILURE TIMES Number of failures in allocating DIN SRFDINF
3.9.8 IN Operation Traffic
Meaning: This measure unit conducts statistic analysis of the global IN operations.
MML word: INOP
Object: Office all
Table 3-97 Measurement of the IN operation traffic

1301 SSF SENDING OPERATION TIMES Number of operations from SSP to SCP SINVK
3-100

SSF RECEIVING OPERATION
1302 Number of operations from SCP to SSP RINVK
TIMES
SSF SENDING RESULT NOT OK
1303 Number of errors during SSP transmitting results SRNOK
TIMES
SSF RECEIVING RESULT NOT OK
1304 Number of errors during SSP receiving results RRNOK
TIMES
SSF SENDING REJECTION
1305 Number of rejected operations by SSP SREJ
OPERATION TIMES
SSF RECEIVING REJECTION
1306 Number of rejected operations by SCP RREJ
OPERATION TIMES
3.9.9 INSM Operation
Meaning: This measure unit counts the number of global INAP operations.
MML word: INSMOP
Object: Service key
Table 3-98 Measurement of the INSM operations

5701 ACTIVATING SERVICE FILTER RECEIVING TIMES Activating service filter receiving ASF
5702 ACTIVATING SERVICE FILTER SENDING TIMES Activating service filter sending ASFRS
5703 ACTIVATING TEST RECEIVING TIMES Activating test receiving ACTTSTR
5704 ACTIVATING TEST SENDING TIMES Activating test sending ACTTSTS
5705 APPLYING CHARGING TIMES Applying charging APYCHG
5706 APPLYING CHARGING REPORT TIMES Applying charging report APYCHGR
5707 ASSISTANT REQUEST INSTRUCTION TIMES Assistant request instruction ASREQ
5708 CALL GAP TIMES Call gap CGAP
5709 CALL INFO REPORT TIMES Call information report CINFRP
5710 CALL INFO REQUEST TIMES Call information request CINFRQ
5711 CANCEL TIMES Cancel CANCEL
5712 COLLECTED INFO TIMES Collection information CLTINF
5713 CONNECTION TIMES Connect CNT
5714 CONNECTING TO RESOURCE TIMES Connect to resource CNT2RES
5715 CONTINUANCE TIMES Continue CONT
DISCONNECTING FORWARD CONNECTION
5716 Disconnect forward connection DISFCON
TIMES
5717 SETUP TEMPORARY CONNECTION TIMES Setup temporary connection ESTTMPC
5718 BCSM EVENT REPORT TIMES BCSM event report BCSMRPE
5719 AFFORDING CHARGING INFO TIMES Affording charging information FCHGINF
5720 INITIALIZING DP TIMES Invoke IDP (Initial DP) INTDP
5721 INVOKING ATTEMPT CALL TIMES Invoke call attempt INTCA
5722 PLAYING ANNOUNCEMENT TIMES Play announcement PLYANN
PROMPT AND COLLECT USER INFO RECEIVING Prompt and collect subscriber information
5723 PC
TIMES receiving
PROMPT AND COLLECT USER INFO RESULT
5724 Prompt and collect subscriber information PCR
TIMES
5725 RELEASE CALL TIMES Release call RLSC
5726 REQUEST TO REPORT BCSM EVENT TIMES Request to report BCSM event REQBCSME
3-101

5727 RESET TIMER TIMES Reset timer RSTT
5728 SENDING CHARGING INFO TIMES Send charging information SCHGINF
5729 SERVICE FILTER RESPONSE TIMES Service filtering response SFRSPN
5730 SPECIAL RESOURCE REPORT TIMES Special resource report SPRSRP
5731 NULL OPERATION RECEIVING TIMES Receiving operation RNUL
5732 NULL OPERATION SENDING TIMES Sending operation SNULOP
5733 ERROR INFO RECEIVING TIMES Receiving error information RERR
5734 ERROR INFO SENDING TIMES Sending error information SERR
5735 ABORT TIMES Receiving abort RTCABT
5736 INVALID COMMAND TIMES Invalid command RERRTCF
3.9.10 IN Sampling Trace
Meaning: This measure unit samples the IN service for usage information.
MML word: INSPTRC
Object: Service key
Table 3-99 Measurement of the IN sampling trace

8501 SERVICE KEY Service key SKEY
8502 SESSION TYPE Session type TCFLG
8503 MESSAGE TYPE Message type MSGTYP
8504 INAP OPERATION TYPE INAP operation type INAPINF
8505 OPERATION DIRECTION Operation direction OPDR
8506 IS TO FILTER Whether to filter FILT
8507 IS TO GAP Whether to gap GAP
8508 OPERATION SEQUENCE NUMBER Operation sequence number OPSN
8509 OPERATION INSTANT Time of operation happened TIME
8510 OPERATION TICKS Ticks of operation lasting TICK
8511 PARAMETER LENGTH Parameter length PLEN
8512 PARAMETER0~3 Parameter0~3 PA0
3-102

3.9.11 SRF Record Informing
Meaning: This measure unit measures the times that the channels have been seized.
MML word: INSRFANN
Object: Service key and start tone code
3-103
Table 3-100 Measurement of the SRF record informing

5651 TIMES OF CHANNEL BE SEIZURED Times of channel be seized ANNS0
3.9.12 SRF Congestion
Meaning: This measure unit conducts statistic analysis in the case of SRF
congestions.
MML word: INSRFCG
Object: Resources such as SPT, AIN, DIN (specified by "Module number + Resource
lower limit + Resource upper limit"). It should be noted that the lower and upper limit
are expressed in the integers from 0 to 100 (corresponding to 0% to 100%).
Table 3-101 Measurement of the SRF congestion

8701 CONGESTION DURATION Duration from SRM congestion start to SRM congestion end CGT
Total number of calls which need SRM resource during SRM
8702 BHCA TIMES BHCA
congestion
8703 APPLYING TIMES Times of applying for SRM resource during SRM congestion ALC
Times of having successfully applied for and released SRM
8704 RELEASE TIMES RLS
resource during SRM congestion
3.9.13 SRF Channel
Meaning: This measure unit obtains the seizure information of the SRF channels.
Each SPT board has 128 channels, numbered from 0 to 127.
MML word: INSRFCHN
Object: Channel (specified by "Module number" + "Channel number")
Table 3-102 Measurement of the SRF channel

5401 SEIZURE SPT TIMES Times of seizing SPT ALCSPT
5402 SEIZURE AIN TIMES Times of seizing AIN ALCAIN
5403 SEIZURE DIN TIMES Times of seizing DIN ALCDIN
3-104

5404 SEIZURE SPT DURATION Duration of seizing SPT ALCSPTT
5406 SEIZURE AIN DURATION Duration of seizing AIN ALCAINT
5408 SEIZURE DIN DURATION Duration of seizing DIN ALCDINT
3.9.14 SRF Operation
Meaning: This measure unit obtains resources such as SRM, and the number of PC
operations and that of PA operations.
MML word: INSRFOP
Object: Service key and resource
Table 3-103 Measurement of the SRF operation

Times of receiving operation = Times from local module + Times
5551 RECEIVING OPERATION TIMES RPEGS
from other module
RECEIVING OPERATION FROM
5552 Times of receiving operations from the local module RPEGSLMD
LOCAL MODULE TIMES
RECEIVING OPERATION FROM
5553 Times of receiving operations from other module RPEGSOMD
OTHER MODULE TIMES
LOCAL MODULE EXECUTING
5554 Times of the local module carrying out operations EXCLMD
OPERATION TIMES
LOCAL MODULE EXECUTING Times of the local module having successfully carried out
5555 EXCSLMD
OPERATION SUCCEEDED TIMES operations
LOCAL MODULE EXECUTING
5556 Times that the local module fails to carry out operations EXCFLMD
OPERATION FAILED TIMES
LOCAL MODULE CANCEL
5557 Times of the local module canceling operations to be carried out EXCCLMD
EXECUTING OPERATION TIMES
INSM RELEASING SRM
5558 Times of releasing operations for INSM releasing SRM INSMRLMD
OPERATION
BCSM RELEASING SRM
5559 Times of releasing operations for BCSM releasing SRM BCSMRLMD
OPERATION
SRM RELEASING SRM
5560 Times of releasing operations for SRM releasing SRM SRMRLMD
OPERATION
ASSISTANT MODULE EXECUTING
5561 Times of the assistant module carrying out operations EXCASMD
OPERATION TIMES
ASSISTANT MODULE EXECUTING Times of the assistant module successfully carrying out
5562 EXCSASMD
OPERATION SUCCEEDED TIMES operations
ASSISTANT MODULE EXECUTING
5563 Times that the assistant module fails to carry out operations EXCFASMD
OPERATION FAILED TIMES
3.9.15 SRF Traffic Volume
3-105
Meaning: This measure unit measures a certain SRF service.
MML word: INSRMOP
Object: Service key
Table 3-104 Measurement of the SRF traffic

5601 APPLYING SRM TIMES Times of applying for SRM ALCSRM
5602 APPLYING SPT TIMES Times of applying for SPT ALCSPT
5603 APPLYING AIN TIMES Times of applying for AIN ALCAIN
5604 APPLYING DIN TIMES Times of applying for DIN ALCDIN
5605 EXECUTING PA TIMES Times of executing PA EXCPA
5606 EXECUTING PC TIMES Times of executing PC EXCPC
5607 EXECUTING CA TIMES Times of executing CA EXCCA
3.9.16 SRM Operation
Meaning: This measure unit obtains the usage information of the SRM resources.
MML word: INSRMOP
Object: Service key
Table 3-105 Measurement of the SRM operation

It is the times of applying for SRM when INSM receiving
5501 INSM APPLYING SRM TIMES information stream of INAP operation to connect to resource INSMSRM
from SCP.
It is the times of having successfully applied for SRM after INSM
INSM APPLYING SRM SUCCESS
5502 receiving information stream of INAP operation to connect to INSMSRMS
TIMES
resource from SCP.
It is the times of having failed to apply for SRM after INSM
INSM APPLYING SRM FAILURE
5503 receiving the information stream of INAP operation to connect INSMSRMF
TIMES
to resource from SCP.
It is the times of having successfully applied for SRM and
5504 INSM RELEASEING SRM TIMES released SRM after INSM receiving information steam of INAP INSMSRMR
operation to disconnect forward connection.
It is the times of BCSM applying for SRM during the session to
5505 BCSM APPLYING SRM TIMES BCSMSRM
play prompt information.
BCSM APPLYING SRM SUCCESS It is the times of having successfully applied for SRM during the
5506 BCSMSRMS
TIMES session to play prompt information.
BCSM APPLYING SRM FAILURE During the session to play prompt information, it is the times of
5507 BCSMSRMF
TIMES having failed to apply for SRM
It is the times of having successfully applied for SRM and
5508 BCSM RELEASING SRM TIMES BCSMSRMR
released SRM during the session to play prompt information.
3-106

In a multi-SM office, it is the times that the local module applies
5509 SRM APPLYING SRM TIMES for special resource to other module, if it has no special SRMSRM
resource for service.
In a multi-SM office, it is the times that the local module has
SRM APPLYING SRM SUCCESS
5510 successfully applied for special resource to other module if it SRMSRMS
TIMES
has no special resource for service.
In a standalone office, it is the times that the local module fails to
SRM APPLYING SRM FAILURE
5511 apply for special resource to other modules if it has no special SRMSRMF
TIMES
resource for service.
In a standalone office, it is the times that the local module has
5512 SRM RELEASING SRM TIMES successfully applied for and released special services to other SRMSRMR
module if it has no special resource for service.
3.9.17 IN Subscriber Interaction Measure
Meaning: It conducts statistic analysis of intelligent subscriber interactions.
MML word: INUI
Object: Service key
Table 3-106 Measurement of the IN subscriber interactions

5801 TOTAL TIMES OF INTERACTION Total number of interactions UITT
TIMES OF SUBSCRIBER ACTIVE
5802 Times of subscriber active abort UIAT
ABORT
3.9.18 IN Outgoing Call QoS
Meaning: The measure unit measures the connection of the global IN outgoing calls.
MML word: OUTCLIQ
Object: Service key
Table 3-107 Measurement of the unusual busy subscribers

TIMES OF INTELLIGENT
5851 Number of intelligent outgoing call attempts CQATMP
OUTGOING CALL ATTEMPT
3-107

5852 Number of connected intelligent outgoing calls OCQC
OUTGOING CALL CONNECTED
5853 Number of answered intelligent outgoing calls OCQA
OUTGOING CALL ANSWER
DURATION OF INTELLIGENT
5854 Duration of intelligent outgoing calls (second) OCQCT
OUTGOING CALL
Average duration of intelligent outgoing call (second) = duration
AVERAGE DURATION OF
5855 of intelligent outgoing call / number of answered intelligent CQACT
INTELLIGENT OUTGOING CALL
outgoing calls
TRAFFIC OF INTELLIGENT
5856 Traffic of intelligent outgoing calls answered CQAU
OUTGOING CALL ANSWER
Call completing rate of intelligent outgoing call = Number of
CALL COMPLETION RADIO OF
5857 completed intelligent outgoing calls / number of intelligent OCQCR
outgoing call attempts
Call answer ratio of intelligent outgoing call = Number of
CALL ANSWER RADIO OF
5858 answered intelligent outgoing calls / number of intelligent CQAR
outgoing call attempts
5859 ROUTING FAULT Routing fault CQRF
5860 CALLED BUSY Called busy CQCB
5861 NO ANSWER No answer CQNA
3.10 Permanent task
3.10.1 HTR Traffic Control
Meaning: Providing base data for HTR traffic control
MML word: HTR
Object: Destination code
Table 3-108 Measurement of the HTR traffic control

5951 SEIZURE ATTEMPT TIMES Times of call attempt to some DPC PEGS
5952 ANSWER TIMES Times of answer call attempt to some DPC ANS
5953 SEIZURE ATTEMPT FOR ANSWER Answer times/seizure attempt times(compute all module at ANSR
RATIO background)
3-108
C&C08 Digital SPC Switching System Chapter 4 Traffic Measurement Application
Chapter 4 Traffic Measurement Application
Traffic measurement is mainly applied to measure daily services and provide routine
data for the scheming and management of the telecom network. Besides, it helps
fulfill the analysis of the call loss, the analysis of the call completing rate, flow
promoting, traffic balancing, maximum/minimum value search and call tracing. The
following are descriptions of these functions.
4.1 Querying Call Loss
4.1.1 Analyzing Call Loss Reason by Means of “Failure Reason Traffic”
The measure unit “Failure reason traffic” in the "Total traffic of the office"
measurement task provides measurement results of more than 100 types of call loss
reasons. It helps track down the main reason of a call loss and roughly locates the
fault type.
For example, in an output report, the value of the entity “MODULE INACCESSIBLE
TIMES” is the biggest. Since the failure is often caused by hardware problems (for
example, a link flash interruption is caused by a faulty interface board, damaged fiber
or unstable clock), a hardware problem can be located as the cause of the call loss in
the first place. For another example where the entity “DUAL SEIZURE TIMES” is a big
value in the output report, as the mode of the call seizing the trunk circuit is
determined by the configuration data, the mismatch of the configuration data between
the local and opposite office might be the main cause of the call loss.
4.1.2 Locating Further Problem
The “Failure reason traffic” gives just the least detailed call loss information. However,
more specific call loss descriptions are needed to locate the right cause of a problem,
such as, where the most failed calls are originated, where the most failed calls are
sent, what type the most failed calls are, and what equipment the most failed calls go
through. Such information is available from “Measurement of Total Traffic of the
Office” and “Measurement of Bearer Traffic”, of these contents:
z Measurement of the traffic flow provides information about the calls and failure
causes of eight traffic flows such as outgoing, incoming, local and transit calls.
The measurement involves such units as “internal traffic” and “originating
outgoing traffic”.
4-1
z Measurement of the connection type provides information about the connections

and failure causes of such connecting types as toll incoming, toll outgoing, local
incoming and local outgoing calls. The measurement involves such units as
“connecting type traffic” and “ISDN connecting type traffic”.
z Measurement of the office direction provides information about the incoming call
to the local office from some office or the outgoing call from some office, and the
failure causes. It can also measure the incoming or outgoing traffic of every office
direction in a measurement task. The measurement involves such units as
“office direction incoming traffic” and “office direction outgoing traffic”.
z Measurement of the trunk group (TK) provides information about the incoming
call to or the outgoing call from some TK and the failure causes. It can also
measure the incoming or outgoing traffic of every office direction in a
measurement task. The measurement involves such units as “TK incoming
traffic” and “TK outgoing traffic”. The TK measurement can help locate the call
loss caused by a faulty trunk.
z Measurement of the destination provides information about the calls to the
destination cities (for example, Beijing, Shanghai) from the local office and the
failure causes. The measurement involves such units as “destination traffic” and
“destination attribution traffic”. The “Destination” is the number of some prefix in
the called number analysis table. For instance, use the ADD CNACLD or MOD
CNACLD command to set the destination number of the prefix "010" to 0. By
numbering each of the prefixes in the called number analysis table and setting
the measurement task, you can work out the information of the calls and failure
causes. The destination traffic measurement helps determine on the connection
status of calls to a destination through transfers so as to optimize route selection.
z Measurement of the user line group provides information about the calls and
failure causes of each module and each subscriber frame. By measuring each
subscriber frame, you can find out the subscriber frames to which the most failed
calls occur. The measurement involves “user line group traffic”.
z Measurement of a single subscriber provides information about the calls of a
particular subscriber. After a call failure is located to a subscriber frame, conduct
statistic analysis of every subscriber (totally 400 subscribers at most to be
measured simultaneously) of the frame to find out the subscriber who places the
most failed calls. The measurement involves “single user traffic”.
z Measurement of the ISDN service provides information about the calls of some
ISDN services. By measuring each of ISDN services, you can find out the ISDN
service that produces the most failed calls. The measurement involves such
units as “ISDN bearer traffic” and “ISDN terminal service traffic”.
z Measurement of the ISDN interface provides information about the calls and
failure causes of some ISDN interfaces. By measuring each of the ISDN
interfaces, you can find out the ISDN interface to which the most failed calls
4-2
occur. The measurement involves such units as “ISDN BRA traffic” and “ISDN
PRA traffic”.
Suppose the failure cause is “long time no answer”, carry out the following steps to
handle the problem.
1) Set up a bearer traffic measurement task. Select “user line group traffic” as the
measure unit with all modules being the measure object, and select “terminal call
ringed no answer times” as the output entity, and set the rest information as
required. Once the task finishes, query the output report to find the modules
whose subscribers have the greatest “long time no answer times". Suppose it’s
the No. 1 module, thus locating the fault to the module level.
2) Create another bearer traffic measurement task. Select “user line group traffic”
as the measure unit, with the “No. 1 module + all frames of No. 1 module” as the
measure object, and still select “terminal call ringed no answer times” as the
output entity, while the rest information remains unchanged. Once the task
finishes, query the output report to find the frame whose subscribers have the
greatest “long time no answer times", thus locating the fault to the subscriber
frame level.
3) Use “single user traffic” to locate the fault to a specific subscriber and use “office
direction outgoing office traffic” or “office direction incoming office traffic” to
locate the fault to a specific board corresponding to the office direction.
4.1.3 Finding Further Cause by Means of “Call Record”
Once the key cause of call loss is located to specific subscribers, the traffic
measurement task of call record may be used to observe the calls of these
subscribers. Different from the real-time and dynamic connection tracing on the
maintenance console, the call record traffic measurement task can preset the record
time and sampling rate and automatically record every call of the subscriber, including
the dialed number, time of every step in the connection, failure cause, sequence of
route selection.
You can find some rough causes of call loss through querying the call record. For
example, query "long time no answer times" to judge whether the hardware is
disconnected, or whether the called number is unused, or even to find the cause of
call loss directly in the call record, for example, whether the subscriber often performs
such invalid operations as "releasing before ringing", "no dial for long time", "dialing
unallocated number".
4.1.4 Finding Essential Call Loss Reason
Generally, it’s impossible to locate essential call loss reasons directly by means of
traffic measurement. However, the measure units (for example, “signaling and
interface traffic” and “inter running measurement”), together with some maintenance
4-3
approaches concerning alarm, self-loop test and signaling analysis, can be used to
locate some essential call loss problems, especially those signaling and link
problems.
For example, set up a signaling and interface traffic measurement task. Select “ISUP
abnormity traffic” as the measure unit, output all entities, and set the rest information
as required. Query the output result and find that the output value of the T17 receiving
no RSC acknowledgment is a bit great. It’s found through the ISUP signaling analysis
that the ISUP sends the RSC message to a circuit once every 30 seconds till it
receives an acknowledgement message (for example, RLC). If it receives no
acknowledgement message after 20 attempts of sending RSC, it will start the T17
timer (10-minute timer) to send the RSC once every 10 minutes till an
acknowledgement message is received. This item measures the event that no circuit
reset acknowledgement is received within T17 after the delayed sending (as opposed
to the RSC sending once every 30 seconds) of the RSC. Therefore, the call loss is
very likely caused by the fact that the circuit fails to reset after receiving the RSC
message.
4.2 Distributing Busy Traffic
Busy traffic refers to great number of calls or heavy traffic. Usually great number of
calls only results in a higher CPU occupancy ratio without affecting the system too
much. However, heavy traffic reflects the occupancy state of resources and in this
case, according to the traffic Formula, considerable call loss will occur. By distributing
busy traffic, it means to arrange the rational use of resources in the light of traffic, thus
reducing call losses. It’s obvious that the key to distributing busy traffic is to measure
and monitor the use of such key resources as trunks and Specialized Resource
Module (SRM).
Measurements that can be used to observe the global traffic or traffic of various parts
are measurement of the traffic flow, measurement of the connection type,
measurement of the office direction, measurement of the trunk group, measurement
of the destination, measurement of the subscriber line group, measurement of the
non-queue public unit and measurement of the queue public unit. These
measurements provide information about use of various resources. Take prompt
measures for resources whose traffic is too much to be carried so as to avoid serious
call loss. For instance, if quite a lot of people in a community access the Internet for a
very long time, this can easily result in very large traffic and very serious call loss
correspondingly. In this case, the telecom operator is recommended to purchase
more equipment or upgrade the equipment.
So far, the switching capacity in many areas is quite large and it’s very seldom that the
global resource falls short. Therefore, it’s not quite often that the traffic measurement
is needed to implement the busy traffic distributing. However, in some special cases,
4-4
unreasonable configuration will cause unbalanced traffic distribution, which might

cause the switch short of resources. In some peak-traffic time (holidays or festivals),
heavy traffic might also lead to the short supply of the switch resource. In these cases,
the accumulated traffic measurement information should help with distributing busy
traffic to ensure normal communication.
4.3 Balancing Traffic
As the C&C08 Switch is of the distributed architecture, it is drawing particular attention

in data configuration and routine maintenance that how the traffic load can be evenly
allocated to all modules, then evenly allocated to subscriber frames and trunk groups.
Suppose, because of the unreasonably configured data, either the traffic is gathered
on one module or calls are made frequently between modules, then the distributed
structure will be transformed into a centralized one, losing its original advantages
such as scattered traffic load, large system capacity and strong processing capability.
To balance the traffic in a static and predictive way is to evenly allocate the traffic load
to respective resources during the course of data configuration. The data optimization
with traffic statistics is a kind of feedback traffic balancing that is dynamic and
effect-oriented.
For instance, it’s hard to predict that, during early data configuration, which subscriber
will have large traffic or subscribers of which number segments will have heavy traffic.
If there are many “networm” subscribers or some hot lines (on stock research report,
social investigation, and so on) in a subscriber frame, call loss will become more
serious and call completing rate will be lowered down. If the result of traffic
measurement is used to help optimize data configuration, the traffic can be distributed
more flexibly as required, thus facilitating traffic balancing.
It’s evident that operations of maximum/minimum value subscriber processing and

traffic balancing are supplementary for each other. At the same time of
maximum/minimum value subscriber processing, traffic is also being balanced, thus
avoiding unreasonable allocation of resources. However, the maximum/minimum
value subscriber processing emphasizes particularly on traffic distribution, it boosts
up the call completing rate sharply in a short period of time, anyhow, this operation
demands frequent maintenance work and quite a huge work. After some time, the
“maximum/minimum value subscriber” accounted everyday may not be so centralized,
and the processing of them will just have a very weak effect on traffic balancing.
However, traffic balancing can implement reasonable usage of limited resource in a
long period though it may not necessarily exert a profound influence on traffic
distribution. For an office with rather small capacity or a time segment with heavy
traffic, traffic balancing is a very effective way to enhance the call completing rate.
4-5
4.4 Searching Maximum/Minimum Value
The traffic measurement function can help search for the maximum/minimum value
user such as a top usage user. By analyzing call-originating of these
maximum/minimum value users (or maximum/minimum value trunks), you can find
out major factors affecting the call completing rate. Then take relevant measures
(hardware restoration, supplementary service provision, voice transfer, and so on) to
raise the call completing rate quickly.
4.4.1 Measurement of Top Usage User
With the measure unit of “top usage user traffic” in the "Measurement of
Maximum/Minimum Values" task, you can find out the top 10 users with the heaviest
traffic and the total seizure time from 4:00 AM to the end of the measurement. The
“total time of seizure” refers to the total time when the user acts as a caller or called
party.
The “top usage user” refers to a user with the heaviest traffic. Heavy traffic implies
serious call loss and impact on other services. For instance, the telephone service
and fax service may affect each other if they share the common resource, and if the
telephone traffic is heavy, the fax service shall be affected. In addition, some users
(networm, for instance) will use the system resource exclusively, thus decreasing
available resources and aggravating call losses.
To solve top usage user problems, it’s advised to install more subscriber lines, use
ISDN, adopt the call forwarding on busy and call forwarding to voice mailbox, and so
on.
4.4.2 Measurement of Top Called Busy User
With the measure unit of “top called busy user traffic”, you can find out the top 10
called busy users and the total times of called busy from 4:00 AM to the end of the
measurement. The “times of called busy” refers to the total times of no reply of the
called party because he/she is busy.
As "called busy" is a kind of call loss, the quick and effective way to raise the call
completing rate is to process the called busy user. To solve the problems, it’s advised
to adopt supplementary services, install more subscriber lines, adopt the call
forwarding to voice mailbox and call forwarding to voice time slot.
4.4.3 Measurement of Top Ringed No Answer User
With the measure unit of “top ringed no answer traffic”, you can find out the top 10
ringed no answer users and their total times of ringed no answer from 4:00 AM to the
4-6
end of the measurement. The “times of ringed no answer” refers to the total times of
no answer of the called.
This problem may be caused by the grounding or broken lines in the hardware, or an
unused called number, or even the user not in home for long. To solve the problem,
just start hardware test, view the configuration data, re-use the unused number,
forward to another number, install voice mailbox, and so on, as required.
Note that as in different offices, the “ringed no answer duration” is set differently, the
following might be inevitable. For the incoming destination call, as the ringed no
answer duration is set to be rather short at the opposite office, it judges the local office
as “ringed no answer” and disconnects the line. However, the ringed no answer
duration is set to be rather long at the local office, but because the opposite office has
disconnected the line, the local office can but judge the opposite office as “release
before ringing”.
4.4.4 Measurement of Top Call Loss User
With the measure unit of “top call loss traffic”, you can find out the top 10 call loss
users and their times of call losses from 4:00 AM to the end of the measurement. The
“times of call losses” refers to the total times of no answer of the user who is the
calling party.
There are reasons that may cause a call loss, either a software/hardware problem or
a human factor. The hardware problem refers to an unintentional hook-on or hook-off
or faulty equipment (faulty subscriber board or subscriber line). The software problem
refers to process suspension. The human factor may mean that the user often hooks
on or hooks off or dials an unallocated number for no purpose. Before handling the
problem, further locate the call loss reason. In this case, use the call record traffic
measurement task to record the calls of these top call loss users, which will serve as
the basis for further analysis. If necessary, multiple offices may have to coordinate to
find out the reason of the call loss.
The following is a simple example.
The relationship between several offices of one place is:
Office 888 ------------Office 666--------------Office 333
Through the measurement of top call loss users, the user 8888888 in the Office 888 is
found out to be the top call loss user. Through the tracing of outgoing calls, it’s found
that the user 8888888 frequently calls the user 3333333 in Office 333 and the call loss
reason is “no available resource”.
The fault cannot be located to be in Office 666 or Office 333 by referring to “no
available resource”. In this case, set up the measurement item “call record”
4-7
respectively in Office 666 and Office 333, to measure the calls with the calling number
of 88888888. Thus the fault can be located in either Office 666 or Office 333. For
example, if the failure cause is found to be “equipment congestion” in Office 666,
while no calls from 8888888 is measured in Office 333, the fault then can be located to
be in Office 666.
When the calling number (or calling prefix) is specified, the failure of a call forwarded
through many offices can be located exactly in a certain office. This method is
particularly applicable to the CAS and TUP signaling with little information being
carried.
4.4.5 Measurement of Top Idle TK Circuit
By means of the “top idle TK circuit traffic” unit in the maximum/minimum value traffic
measurement task, the trunk circuits and group numbers with the least total seizure
duration can be measured between 4:00 AM to the end of the measurement. The total
duration of trunk seizure refers to the total time when the trunk circuit is occupied. The
idlest trunk measurement excludes the trunk circuits that are not installed. The idlest
trunk measurement can help improve the circuit utility.
4.4.6 Maximum/Minimum Value Measurement
At present, specific user scope can be defined when the traffic measurement function
is used to search for the maximum/minimum value users. The range can be the whole
office, one module, users of a certain type (distinguished by user type + user number),
or a Centrex group. Through setting measure objects, you can find out the top 10
maximum/minimum value users of a specific (or every) module or Centrex group.
The maximum/minimum value measured is the cumulative value calculated from 4:00
AM to the current time (at the end of the measurement). Sometimes, the
maximum/minimum value of 9:00~11:00 (busy hours) instead of the whole time
segment is desired. In this case, use the SET TRFTPTM command to clear the
maximum/minimum value counter at 9:00, and set the task to output the
measurement result at 11:00.
Considering that searching maximum/minimum value consumes huge CPU resource,

keep a small quantity of the maximum/minimum value measurement tasks, especially
that of the subtasks. A task in case of full configuration of subscriber lines should have
only one subtask preferably. If many maximum/minimum value tasks exist, set the
time to output results to different time, and avoid the busy hours preferably.
4-8
4.5 Tracing Calls
The function of call tracing at the maintenance console can be used to trace a
telephone in real time, and save the tracing information. However, there are
restrictions on the call tracing at the maintenance console. For example, the number
of users traced simultaneously is limited, only specific users instead of a specified
range can be traced, startup of a tracing at a preset time is impossible, and tracing
information cannot be filtered automatically.
The above restrictions can be overcome by the two measure units of the call record
traffic task, that is, “dispersion duration traffic” and “service quality traffic”. Thus
tracing of mass calls becomes possible, measurement results are available as soon
as calls end, calls can be filtered in real time through the filter mechanisms which are
inherent in the traffic measurement, for example, inlet, outlet, destination code, call
attribute, host number and failure cause. Besides, the call tracing can be performed in
any predefined time or time segment through the time predefining mechanism of the
traffic measurement. After filtering, the call of heavy traffic can be further measured
through sampling.
4.6 Locating Factors Influencing Call Completing Rate
The call completing rate, or rather, answer rate, is a key index for appraising the
operation quality of the equipment.
Factors influencing the call completing rate include equipment status, data
configuration, network planning and even human factors. Therefore, to greatly
increase the call completing rate, first locate major factors that affect the call
completing rate, then take corresponding measures. Traffic measurement is
absolutely the effective way to resolve the above problem.
The C&C08 Switch provides powerful traffic measurement functions, which can be
used to perform detailed measurement and statistics on the whole system. By
examining and analyzing the outputs, you can find out how various factors influence
the call completing rate. The above mentioned methods are all applications of using
the traffic measurement to locate the factors which influence the call completing rate.
Here are some instances for reference.
I. No user answers
[Symptom]
The incoming multiple traffic measurement results indicate that there are many failed
calls caused by “no user answers” in one office.
[Analysis]
4-9
Set up a service quality task for call records and find in the measurement result the
failed calls caused by “no user answers”. It is found out that on most occasions the
failure is caused when the user 010684**** calls the DSL user 517**** of the local
office. After investigation, the user is connected through a standby router path. Due to
the failure of the called Network Terminal 1 (NT1), the caller cannot be connected
successfully, and he/she dials again and again, thus producing many failed calls.
[Solution]
Coordinate relevant departments to solve it.
II. Low connection ratio of incoming toll calls in an office
[Symptom]
The call completing rate of incoming toll calls of an office is as low as 43%. The traffic
measurement indicates that the called busy ratio is as high as 40%, which is the most
important factor that affects the call completing rate.
[Analysis]
According to the actual condition of the office, the key point to increase the completing
rate of incoming calls is to perform the busy traffic distributing. With regard to the
network configuration of the office, the method and target of distributing busy traffic
are as follows:
1) The office party provides the voice mailbox (198123456) for forwarding on busy.
2) Find top usage user through traffic measurement analysis, and arrange the busy
and idle subscribers in sequence.
[Solution]
Set the function of call forwarding to voice mailbox on busy for the top usage users
one by one. It is required that the quantity of the forwarded users is less than 100, and
the call completing rate should be raised from 43% to above 53%. According to the
measurement result of top usage users, set the function of call forwarding to voice
mailbox on busy, starting with the topmost usage user.
After the function is configured for the first 80 top usage users, the completing rate of
the incoming toll calls is raised from 43% to 60%. The measurement result of the local
office is as same as that of the toll office. Thus, the distribution of busy traffic is
successful, and the completing rate of incoming calls is greatly improved.
III. Low completing rate of outgoing calls
[Symptom]
The completing rate of outgoing calls to MS2 (5ESS) of an office is low.
4-10
[Analysis]
According to the measurement of the outgoing traffic, there are lots of call losses
caused by dual seizures. According to the trunk traffic, the average traffic of each line
is only 0.3-0.4 Erls. The line selection mode is “minimum” and that of MS2 (5ESS)
office is “maximum”. However, the “minimum” of the C&C08 Switch indicates the
equipment number is minimum, while the “maximum” of MS2 (5ESS) indicates the
Circuit Identification Code (CIC) number is maximum. Therefore, if the equipment No.
of the C&C08 Switch and the CIC are of different coding sequence, dual seizure may
happen when the circuit is not busy.
[Solution]
After the modification of the line selection mode of the switch to “Master/Slave”, the
dual seizure will disappear, and the call completing rate becomes normal.
4.7 Other Applications
According to the above introduction, on most occasions, traffic measurement is used

as a powerful auxiliary method. In addition to such applications as errors checking,
busy traffic distributing and traffic balancing, there are also some simple applications
as follows.
I. Checking the running status of the global equipment
It is impossible to review the equipment running status directly with the traffic
measurement. However, it is possible to find out problems through checking the traffic
measurement result, especially the call loss reasons related to the equipment (such
as call loss caused by switch network failure). In this way, the equipment failure can
be found out and delimitated as soon as possible.
For example, set up a "total traffic of the office" measurement task. Select “origination
traffic” as the measure unit, and the measure object is fixed as all user lines. Select
“switch network blocking call loss times”, ”common resource unavailable call loss
times”, ”system fault call loss times” and “blocked by auto call loss times” as output
entities, and set the rest information as required.
CRE TRFOTF: TSK=20, MU=OR,
ENTSET=NETBLCL&CMRUAVCL&SYSFLCL&ALBLCL&FWCTLCL;
The call loss condition is available in the output report when the task finishes. The
equipment running status can be figured out according to the call loss condition. For
example, if the value of the “switch network blocking call loss times” is big in the
measurement result, the fault may occur in the switching network board.
4-11
Or create a "total traffic of the office" measurement task. Select “failure reason traffic”
as the measure unit. Select failure reasons of related equipment as output entities,
and set the rest information as required. The failure cause condition is available in the
output report when the task finishes. The equipment running status can be figured out
according to the call loss condition.
CRE TRFOTF: TSK=21, MU=FLRSN;
II. Finding the internal traffic and outgoing (or incoming) traffic of the local
office
The ratio of internal traffic to outgoing (or incoming) traffic determines the type of the
hardware configuration of the local office. If most of the traffic is internal traffic, the
local office should be mainly configured with subscriber modules. If most of the traffic
is outgoing (or incoming) traffic, the local office should be mainly configured with trunk
modules.
For example, set up three "total traffic of the office" measurement tasks, measuring
respectively the internal, outgoing and incoming traffic. Select “inner traffic”, ”outgoing
office traffic” and ”incoming office traffic” as measure units. Select ”call attempt times”
and ”call connected times” for output entities, and set the rest information as required.
The percentages of the internal traffic, outgoing traffic and incoming traffic are
available in the output report when the task finishes.
CRE TRFOTF: TSK=22, MU=INT (inner traffic), ENTSET=PEGS (call attempt times)
& CNT (call connected times);
CRE TRFOTF: TSK=23, MU=OG (outgoing traffic), ENTSET=SEIZ (call seizure times)
& CNT (call connected times);
CRE TRFOTF: TSK=24, MU=INC (incoming traffic), ENTDEL=SEIZ (call seizure

times) & ANS (call answering times);
III. Finding the transit condition in the transit office
The transit traffic in the transit office indicates the transit condition. The following "total
office of the office" measurement task can be set up to find the transit condition.
Select “transfer traffic” as the measure unit, and fix the measure objects as all
incoming and bi-directional circuits, and set the rest information as required. When
the task finishes, view the output report to get the transit information.
CRE TRFOTF: TSK=25, MU=TRN (transfer traffic);
Or set up such a "total traffic of the office" measurement task. Select “connecting type
traffic” as the measure unit, ”toll call transferring” and ”international call transferring”
as measure objects, and set the rest information as required. When the task finishes,
view the output report to get the transit information.
4-12
CRE TRFOTF: TSK=26, MU=CT (connecting type traffic), CT=IT (international call
transferring) &TT (toll call transferring);
IV. Measuring domestic toll calls
Set up a "total traffic of the office" measurement task. Select “connecting type traffic”
as the measure unit, ”auto outgoing toll call”, ”incoming toll call” and “toll call
transferring” as measure objects, and set the rest information as required. When the
task finishes, sum up the output reports to get information of the toll calls.
CRE TRFOTF: TSK=27, MU=CT, CT=TAO (auto outgoing toll call) & TI (incoming toll
call) &TT (toll call transferring);
V. Measuring the traffic of a module or a subscriber frame
Set up a "bearer traffic" measurement task. Select “user line group traffic” as the
measure unit, select the subscriber frame of module as measurement objects, and set
the rest information as required. View the output report to get the traffic of the
subscriber frame or module when the task finishes.
CRE TRFCROBJ: TSK=28, MU=URUNT (user line group traffic), SH=1-1 (Module 1,
Frame 1);
Or set up a "call record" measurement task. Select “multi condition object traffic” as
the measure unit, select the subscriber frame (if the object is of the inlet subscriber
frame type) or module (if the object is of the inlet user Measurement Identification
(MID) group) as the measure object under the inlet condition. Set the rest information
as required. View the output report to get the traffic information of the subscriber
frame or module when the task finishes.
CRE TRFCLR: TSK=29, MU=MICDT (multi condition object traffic), ISH=1-1 (Module
1, Frame 1);
VI. Measuring the failure causes of an entire switch
It is necessary to measure the failure causes of an entire switch for maintenance and
management of the switch. Set up a "total traffic of the office" measurement task.
Select “failure reason traffic” as the measure unit, select all entities output by default.
Set the rest information as required. View the output report for the failure causes of
the entire switch when the task finishes.
CRE TRFOTF: TSK=30, MU=FLRSN;
Or set up a "call record" measurement task. Select “service quality traffic” as the
measure unit, select “all failed calls” under “reason of a certain failed call” condition as
the measure object. Set the rest information as required. View the output report for the
failure causes of the entire switch when the task finishes.
4-13
CRE TRFCLR: TSK=31, MU=SVCQUA (service quality traffic), TLFAIL=ALL (all failed
calls);
VII. Measuring the traffic of a user
On some special occasions, it is required to measure the traffic of a single user. Set
up a "bearer traffic" measurement task. Select “signal user traffic” as the measure unit,
select a user (with multiple description modes) as the measure object, and set the rest
information as required. View the output report to get the traffic information of the user
when the task finishes.
CRE TRFCROBJ: TSK=32, MU=UR (signal user traffic), USN=1-WIRED-1000 (wired

user with 1000 being the logic number of Module 1);
Set up another "bearer traffic" measurement task. Select “multi condition object traffic”
as the measure unit, select a single user (with multiple description modes) under the
inlet condition as the measure object, and set the rest information as required. View
the output report to get the traffic information of the user when the task finishes.
CRE TRFCLR: TSK=33, MU=MICDT, IUSN=1-WIRED-1000;
VIII. Measuring the calls of ISDN users
Set up "total traffic of the office" measurement tasks. Select respectively “ISDN
intra-office traffic”, “ISDN originating outgoing office traffic”, “ISDN incoming office
terminating traffic” and “ISDN transfer traffic” as measure units. Set the rest
information as required. When the tasks finish, combine the respective output reports
to get the call information of ISDN users.
CRE TRFOTF: TSK=34, MU=ISDNINT (ISDN intra-office traffic);
CRE TRFOTF: TSK=35, MU=ISDNOROG (ISDN originating outing office traffic);
CRE TRFOTF: TSK=36, MU=INCTE (ISDN incoming office terminating traffic);
CRE TRFOTF: TSK=37, MU=ISDNTRN (ISDN transfer traffic);
Or set up the following "total traffic of the office" tasks. Select respectively “sort user
originating traffic” and “sort user terminating traffic” as measure units, and “ISDN user”
as measure objects. Set the rest information as required. When the tasks finish,
combine the respective output reports to get the call information of ISDN users.
CRE TRFOTF: TSK=38, MU=SRTOR (sort user originating traffic), SRTUR=ISDN;
CRE TRFOTF: TSK=39, MU=SRTTE (sort user terminating traffic), SRTUR=ISDN;
4-14
IX. Measuring a call
Set up the following "call record" measurement task. Select “dispersion duration
traffic” as the measure unit, select the default measure objects (all objects), and set
the rest information as required. When the task finishes, view the output report to get
the information of each call.
CRE TRFCLR: TSK=40, MU=DISP (traffic dispersion and duration), TLINLET=ALL

(all inlets), TLOUTLET=ALL (all outlets), TLSVN=ALL (all call attributes), TLCD=ALL
(all destination codes), TLCID=ALL (all calling numbers);
Or set up the following "call record" measurement task. Select “service quality traffic”
as the measure unit, select the default measure objects (all objects), and set the rest
information as required. When the task finishes, view the output report to get the
information of each call.
CRE TRFCLR: TSK=41, MU=SVCQUA, TLINLET=ALL, TLOUTLET=ALL,

TLSVN=ALL, TLCD=ALL, TLCALL=ALL (all successful/failed calls);
X. Measuring calls to a certain destination
Set up the following "bearer traffic" measurement task. Select “destination distribution
traffic” as the measure unit, type the destination or destination code under the
limitation condition “certain destination or distribution code”, select all office directions
or trunk groups as measure objects under the limitation condition “certain office
direction or outgoing trunk group”, and set the rest information as required. When the
task finishes, view the output report to get the information of calls to this destination.
CRE TRFCROBJ: TSK=42, MU=DESTDISP (destination traffic distribution and

measurement), DEST=1 (No.1 destination), TLOTK=ALL (all outgoing trunks);
Or set up the following "bearer traffic" measurement task. Select “destination traffic”
as the measure unit, type the destination as the measure object, and set the rest
information as required. When the task finishes, view the output report to get
conditions of calls to this destination.
CRE TRFCROBJ: TSK=43, MU=DEST (destination traffic measurement), DEST=1;
Or set up the following "call record" measurement task. Select “multi condition object
traffic” as the measure unit, type the destination or the destination code as the
measure object under the limitation condition “destination code”, and set the rest
information of calls to this destination.
CRE TRFCLR: TSK=44, MU=MICDT, TLINLET=ALL, TLOUTLET=ALL, TLSVN=ALL,

CD=1 (No.1 destination), TLCID=ALL;
4-15
In addition, the traffic measurement task for bearer objects can also be set up
according to the corresponding office direction (taking the “office direction outgoing
office traffic” as the measure unit). Also the traffic measurement task for bearer
objects can be set up according to the trunk group (taking the “TK group outgoing
office traffic” as the measure unit). The first three methods are recommended.
XI. Measuring the traffic of a certain office direction
Set up the following "bearer traffic" measurement tasks. Take the “office direction
incoming office traffic” and “office direction outgoing office traffic” respectively as the
measure unit, select this office direction as the measure object, and set the rest
information as required. When the tasks finish, summarize the respective output
reports to get the traffic information of this office direction.
CRE TRFCROBJ: TSK=45, MU=OFDINC (office direction incoming traffic

measurement), INCOFD=1 (incoming office direction is 1);
CRE TRFCROBJ: TSK=46, MU=OFDOG (office direction outgoing traffic

measurement), OGOFD=1 (outgoing office direction is 1);
Or set up the following "call record" measurement tasks. Take the “multi condition
object traffic” as the measure unit, select this office direction (corresponding to the
incoming office direction) at the outlet, or this office direction (corresponding to the
outgoing office direction) at the inlet as the measure object, and set the rest
reports to get the traffic information of this office direction.
CRE TRFCLR: TSK=47, MU=MICDT, OOFD=1 (the outlet is No.1 office direction);
CRE TRFCLR: TSK=48, MU=MICDT, IOFD=1 (the inlet is No.1 office direction);
XII. Measuring the traffic of a certain trunk group
Set up the following "bearer traffic" measurement tasks. Take the “TK group incoming
office traffic” and “TK group outgoing office traffic” respectively as the measure unit,
select this trunk group (or trunk group set) as the measure object, and set the rest
reports to get the traffic information of this trunk group.
CRE TRFCROBJ: TSK=49, MU=TKGINC (TK group incoming office traffic

measurement), IBTKG=5 (incoming or bi-directional trunk group No. is 5);
CRE TRFCROBJ: TSK=50, MU=TKGOG (TK group outgoing office traffic

measurement), OBTKG=5 (outgoing or bi-directional trunk group No. is 5);
Or set up a "call record" measurement task. Take the “multi condition object traffic” as
the measure unit, select this trunk group (corresponding to the incoming trunk group)
4-16
at the outlet, or this trunk group (corresponding to the outgoing trunk group) at the
inlet as the measure object, and set the rest information as required. When the task
finishes, summarize the respective output reports to get the traffic information of this
trunk group.
XIII. Measuring the traffic of a certain Centrex group
Set up the following "bearer traffic" measurement tasks. Take the “Centrex intra-group
traffic”, “Centrex extra-going traffic” and “Centrex outgoing group traffic” respectively
as the measure unit, select this Centrex group as the measure object, and set the rest
reports to get the traffic information of this Centrex group.
CRE TRFCROBJ: TSK=51, MU=CTXINT (Centrex intra-group traffic measurement),

CTX=21 (the Centrex group No. is 21);
CRE TRFCROBJ: TSK=52, MU=CTXOTS (Centrex out-group traffic measurement),

CTX=21;
CRE TRFCROBJ: TSK=53, MU=CTXTK (Centrex outgoing group traffic

measurement), CTX=21;
Or set up the following "call record" measurement tasks. Take the “multi condition
object traffic” as the measure unit, select this Centrex group at the outlet instead of the
inlet (corresponding to the extra-group traffic), or select this Centrex group at the inlet
instead of the outlet (corresponding to the Centrex call trunk), or select this Centrex
group at both inlet and outlet (corresponding to the intra-group traffic) as the measure
object, and set the rest information as required. When the tasks finish, summarize the
respective output reports to get the traffic information of this Centrex group.
CRE TRFCLR: TSK=54, MU=MICDT, TLINLET=ALL (all inlets), OCTX=21 (outlet is

No.21 Centrex group), TLSVN=ALL (all call attributes), TLCD=ALL (all destination
codes), TLCID=ALL (all calling numbers);
CRE TRFCLR: TSK=55, MU=MICDT, ICTX=21 (inlet is No.21 Centrex group),

TLOUTLET=ALL (all outlets), TLSVN=ALL, TLCD=ALL, TLCID=ALL;
CRE TRFCLR: TSK=56, MU=MICDT, ICTX=21, TLOUTLET=21, TLSVN=ALL,

TLCD=ALL, TLCID=ALL;
XIV. Measuring the traffic of a certain PABX group
Set up the following "bearer traffic" measurement task. Select “PABX group traffic” as
the measure unit, select this PABX group as the measure object, and set the rest
traffic information of this PABX group.
4-17
CRE TRFCROBJ: TSK=57, MU=PABX (PABX group traffic measurement), PABX=9

(PABX group No. is 9);
XV. Measuring the usage information of the DRV board
Set up the following "public unit" measurement task. Select “queue public unit traffic”
as the measure unit, type the module number and frame number of the Dual Tone
Number Receiving & Drive Board (DRV) as the measure object, and set the rest
usage information of the DRV board.
CRE TRFCCP: TSK=58, MU=QPUBUNT (queue public unit traffic measurement),

QPUBUNT=12-3 (frame3 of module12);
XVI. Measuring the usage information of the boards MFC and DTR
Set up the following "public unit" measurement task. Select “unqueue public unit
traffic” as the measure unit, type the module number and unqueue public unit (MFC
board or DTR board) as the measure object, and set the rest information as required.
When the task finishes, view the output report to get the usage information of the MFC
board or DTR board.
CRE TRFCCP: TSK=59, MU=UQPUBUNT (unqueue public unit traffic measurement),

UQPUBUNT=8-MFC (MFC board of module 8);
4-18
C&C08 Digital SPC Switching System Chapter 5 Solutions to Common Problems
Chapter 5 Solutions to Common Problems
Reasonable selection of the statistics task, measure unit, measure object and output
entity is the key for correctly using the traffic statistics system, and it is also a common
problem in the process of actual application. Moreover, there are problems such as
crossing of traffic statistics periods. The solutions to these problems are described as
follows.
5.1 How to Select a Traffic Statistics Task
Usually, determine the type of a traffic statistics task according to the attribute of the
measure object. For example, to measure the outgoing traffic of all the subscribers of
an office, obviously, the measure objects include all the subscriber lines, which means
the measurement is global. Therefore, select the "total traffic of the office" statistics
task. To count the calls of several subscribers with the heaviest traffic, select the
"extremum traffic" statistics task because the measured objects are specially busy
subscribers. To measure the use of the operator console, select the "public
component" statistics task because the operator console is a public component.
In some special cases, one measurement activity can be accomplished by multiple

traffic statistics tasks. For example, to count the traffic in a specific office direction,
both bearer object task (with “office direction incoming office traffic” and “office
direction outgoing office traffic” as the measure units) and call record task (with “multi
condition object traffic” as the measure unit) can be selected. In this case select the
most appropriated task according to other conditions (for example, the requirements
of the measure unit and output entity). If it is necessary to observe the use of a
supplementary service, set up the call record statistics task because the default
output entities in this task include those which reflect the use of a supplementary
service (such as “supplementary service use succeeded” and “supplementary service
use failed”).
5-1
5.2 How to Select a Measure Unit
There are two methods of selecting measure units.

z One is to select the measure unit according to the measurement contents after
the type of a traffic statistics task is determined. For example, to measure the
internal traffic of all the subscribers in an office, first determine the task type as a
"total traffic of the office" statistics task, then select “inner traffic” as the measure
unit according to the measurement contents.
z The other is to determine the measure unit directly according to the attribute of
the measure object. For example, if the measure object is MFC, directly select
“unqueue public unit traffic” as the measure object because MFC is an unqueue
public component.
Similar to the traffic statistics task, one measurement activity can also correspond to
multiple measure units in some special cases. At this time, select the most
appropriate measure unit according to other conditions (for example, the
requirements of the measure object and output entity) and set up corresponding traffic
statistics task.
5.3 How to Select a Measure Object
In some traffic statistics tasks, the measure objects are fixed and not optional, such as
the measure object of the "total traffic of the office" statistics task. However, in most of
the traffic statistics tasks, the measure objects are optional.
Select the measure objects of a single composition (such as a subscriber, subscriber

group or service) on the basis of actual demands or working habits. For example, in
the “supplementary service traffic” unit, the object types to be selected include
abbreviated dialing, hotline service, waking-up service and do-not-disturb service.
Suppose the abbreviated dialing and waking-up service are the main concern in this
measurement, so add these two object types into the object instance list. Another
example is that in the “single user traffic” unit, a single user is described in three
modes, namely, internal code, external code and port number, any of which can be
selected. It should be pointed out that the same description mode must be selected
for the same type of objects in the same task. For example, in a specific task,
“subscriber inner code” and “subscriber external code” cannot be used at the same
time, and even with the same description mode, the user type must be consistent in
the description.
For measure objects of combined object types, determine the elements and their
description modes usually according to actual demands. If it is unnecessary to match
a certain element, select “all……” for this element (such as all objects and all trunks).
For example, in the “multi condition object traffic” unit, the measure object is
5-2
composed of five parts, that is, inlet, outlet, call attribute, destination code and caller
number. Suppose the measurement purpose is to view the internal traffic from a
certain module to another module, so select “MID group of inlet subscriber” for the
inlet description mode, “MID group of outlet subscriber” for the outlet description
mode, “local” for the call attribute, “all destination code” for the destination code and
“all calling number” for the calling number. Suppose the measurement purpose is to
view all the traffic from a specific calling number to a specific destination, then type the
calling number and destination code according to the measurement requirement and
select “all…….” for other components.
5.4 How to Determine an Output Entity
All the entities of a task are output under the default condition. However, in practical
application, the user often only cares about a part of the entities, and too many output
entities will affect the readability of the output report. Therefore, it is necessary to
determine the output entity according to actual demands. For example, the major
purpose of the measurement of the incoming traffic is to view the causes of various
failures in the call process, then the entities related to it (such as incomplete dialing-up
times, invalid address times, call loss due to switching network congestion and call
loss due to common resources unavailable) should be listed in the “selected entity”
field. Besides the optional entities, the user can define the entity to make it an entity
which can be output.
5.5 Solutions to Other Common Problems
5.5.1 When to Output the Traffic Statistics Result
For most of the traffic statistics tasks, the results cannot be obtained until the
measurement period is completed. For example, a statistics task of the incoming
traffic of a trunk group is created at 8:50 with the start time as 9:00 and the statistics
period as one hour. The first statistical report will be output when a complete statistics
period ends, that is, at 10:00 (note: the report is usually output at an integer hour),
corresponding to a statistical time segment from 9:00 to 10:00. However, if this traffic
statistics task is created at 9:10, then the first result report will be output at 11:00
(because it is not a complete statistical period from 9:10 to 10:00, no statistical report
will be output during this time segment).
In addition, for a few measure units such as service quality evaluation, traffic
distribution and duration count, and intelligent sampling tracing, as one statistical
report will be output for each call which meets the statistical conditions, the
measurement period will no longer be meaningful, and the above problems will not
occur.
5-3
5.5.2 How to Understand Questions of Period-Crossing Traffic Statistics
Take the statistics of the incoming traffic of the trunk group as an example. Both “TK
group incoming traffic” of the bearer object statistics task and “multi condition object
traffic” of the call record statistics task can be selected as the measure unit. Then what
is the difference between them? The difference lies in the fact that the statistics
methods for them are essentially different.
The TK group incoming traffic measurement is based on counters, that is, during
statistics a counter is set at a related position of the service flow, and if any
corresponding event occurs, the counter will increase by one. On the other hand, the
multi condition object traffic measurement is based on messages, that is, after a
conversation ends (pay attention to the “after”), the traffic statistics processing
program of the corresponding process will send a message to the traffic statistics
module to report the information about this conversation, such as the caller, called
and conversation duration. Usually, the statistical results of the two are consistent, but
in the case of period-crossing traffic statistics, there are certain deviations between
the two statistical results.
Each traffic statistics task has a statistics period, which refers to the period of report
outputting, for example, if the statistics period is one hour and the traffic statistics
begins at 9:00, then a statistical report will be output at 10:00. It should be pointed out
that the statistical report should be output at an integer hour (such as 8:00 or 9:00).
However, the following cases may occur: One call begins at 8:50 and ends at 9: 05,
one call begins at 9:55 and ends at 10:10, one call begins at 8:55 and ends at 10:05.
Such cases are called period-crossing. In the following, these three cases are
analyzed with the TK group incoming traffic measurement and multi condition object
traffic measurement as examples (suppose there is only one call during the statistics
period).
1) 8:50~9:05
TK group incoming: There is one seizure in the repot output at 9:00, the traffic
statistics is normal and the average seizure duration is 10 minutes. The number of
seizures in the report output at 10:00 is 0, the traffic statistics is normal and the
average seizure duration is 0.
Multi condition object: In the report output at 9:00, the time seizure is 0 and the
average duration is 0 (note: there is no traffic entity in this measure unit). In the report
output at 10:00, the number of seizure is 1 and the average seizure duration is 15
minutes.
2) 9:55~10:10
This case is similar to that of 8:50~9:05.
3) 8:55~10:05
5-4
TK group incoming: There is one seizure in the report output at 9:00, the traffic
statistics is normal and the average seizure duration is 5 minutes. The number of
seizures in the report output at 10:00 is 0, the traffic statistics is normal and the
average seizure duration is 0. The number of seizures in the report output at 10:00 is
0, the traffic statistics is normal and the average seizure duration is 0.
Multi condition object: In the report output at 9:00, the number of seizures is 0 and the
average seizure duration is 0. In the report output at 10:00, the number of seizures is
0 and the average seizure duration is 0. In the report output at 10:00, the number of
seizures is 1 and the average seizure duration is 1 hour and 10 minutes.
Obviously, the two statistics methods have reflected the call information from different
aspects. If period-crossing calls frequently occur (the most typical case is that many
subscribers dial to access the Internet and the conversation duration is usually more
than one hour, but the operator performs traffic statistics with the statistics period of
one hour), the traffic statistics results may be unreasonable, for example, there is
traffic but no seizure, or the average seizure duration lasts too long, even beyond the
statistics period. All these are caused by the period crossing. In some cases, solve the
above problems temporarily by extending the statistics period, but this cannot
eliminate such problems essentially, because the specific call time cannot be
controlled. In addition, the traffic during the common statistics period cannot be
reflected after the statistics period is extended, therefore, the maintenance and
management will be affected. Actually, it is not an error if the period-crossing call
affects the statistics result. It is an objective reflection which is decided by the current
measurement mechanism. Meanwhile, it also indicates that there are different
statistics methods for various traffic statistics tasks, and the results cannot be used for
simple comparison.
5.5.3 Statistics Methods of the Number of Seizures, Seizure Traffic and

Average Seizure Duration and Their Relations
Take the trunk incoming measurement as an example.

z Number of seizures refers to the times that the incoming (bi-directional) trunk
circuit is seized.
z Seizure traffic refers to the traffic transmitted from the incoming (bi-directional)
trunk circuit being seized to the trunk being released.
z Statistics period refers to the period for the output of a statistical report and is
usually one hour.
z The average seizure duration refers to the average duration in a statistical period
from the incoming (bi-directional) trunk being seized to the trunk being released,
which satisfies the following formula:
Average seizure duration = Seizure traffic * Statistics period / Number of seizures
5-5
z Traffic: It is the percentage of the time during which the equipment processes the
traffic in the total duration. It has no unit and is expressed in Erl.
1) Statistics of the number of seizures
The statistics of the number of seizures is implemented by a counter, which indicates
the number of seizures on the corresponding software flow points and accumulates
the seizures, for example, if the trunk circuit is seized once, the counter will increase
by one. The traffic statistics module (MS) accesses this counter respectively at the
beginning and ending of the statistics period, and the difference between them is the
seizure counts in this statistics period. As the difference is required, the statistics
results cannot be sent out before a complete statistics period ends in most of the
traffic statistics tasks.
2) Statistics of seizure traffic
Statistics of seizure traffic is implemented by the scanning of the auxiliary traffic. The
auxiliary traffic of the seizure traffic at the corresponding software flow point will be
added or subtracted, that is, if the trunk circuit is seized once, 1 is added and if the
trunk circuit is released once, 1 is subtracted from the auxiliary traffic. Obviously, this
variable reflects altogether how many trunk circuits are seized in a certain time
segment. The timing task of traffic statistics scans this variable every 10 seconds and
adds it into the seizure traffic. When the statistics period ends, the seizure traffic is the
product of the variable and the scanning duration of 10 seconds divided by the total
duration (statistics period).
For example, there are altogether 10 trunk circuits in a trunk group, in case of
scanning at 10, 20, 30, 40, 50 or 60 seconds in one minute, the auxiliary traffic of the
seizure traffic is respectively 2, 4, 7, 9, 5 and 1. So, the traffics is (2+4+7+9+5+1)
*10/60 = 4.83.
It should be noted that if the auxiliary traffic of the seizure traffic is scanned every 10
seconds, while the calculation formula shows that the circuit is always seized during
these 10 seconds, there certainly are some deviations. In addition, the seizure traffic
refers to the total traffic of the trunk group, so it must be greater than 1 but less than
the number of total trunk circuits in the trunk group. To ensure the data accuracy, the
foreground usually multiples the traffic by 100 and sends it to the background which
will divide the traffic by 100 and show the figure with two digits of the decimal fractions
being attached.
3) Statistics of average seizure duration
The average seizure duration is a derived quantity whose derivation formula is given
above. However, the following special case may appear during calculation: For
example, if a TK group incoming traffic statistics task is set up with the statistics period
of one minute, and the measurement object is an incoming trunk group with 10 trunk
circuits, all the circuits are always seized. Then what are the number of seizures,
seizure traffic and average seizure duration? In a certain period (60 seconds), as all
5-6
the trunk circuits are seized, no event of trunk circuit seizure will occur, the seizure
time is 0, while the auxiliary traffic of the seizure traffic is always 10, therefore, the
traffic is also (10*6) *10/60=10. The seizure duration worked out by the foreground is
10*60=600 seconds, but as the number of seizures is 0, the average seizure duration
is 0.
5.5.4 When Traffic Measurement of ISDN Terminal Service Is Effective
“Traffic measurement of ISDN bearer service” is performed after the network side
receives the SETUP message which includes the ET_BEARER_CAPABILITY
information unit, as this information unit is a compulsory one of the SETUP message,
both the originating calls and received calls can be counted.
“Traffic measurement of ISDN terminal service” is performed after the network side
receives the SETUP message which includes ET_HLC information unit, as this
information unit is an optional one of the SETUP message. If the SETUP message
does not include ET_HLC, this measurement cannot be performed.
First dial an ISDN telephone to call an ASL subscriber, then dial an ASL telephone to
call an ISDN subscriber for traffic statistics. When the ISDN subscriber is the caller,
the digital subscriber side will send the SETUP message including the ET_HLC
information unit, so the originating calls can be counted. When the ISDN subscriber is
the called, as the SETUP message sent by the analog subscriber does not include the
ET_HLC information unit, the received calls cannot be counted.
As the SETUP message sent by the ASL subscriber does not include the ET_HLC
information unit, only the ISDN subscribers will be considered, that is to say, this
function is effective only when both the caller and called are ISDN subscribers.
5.5.5 Some Special Instances of Traffic Statistics
z The number of seizures is less than the number of connections and the number
of answers.
z The number of connections is less than the number of answers.
z There is no number of seizures, connections and answers but there are seizure,
connection and answer traffic.
Telecom operators often doubt these problems, but these problems do not mean that
there is something wrong with the traffic statistics. The cause may be that a call which
seizes the trunk in the previous period may not be connected and answered until the
next period, because the dialing process of the subscriber may exceed a period. A call
connected in the previous period may not be answered until the next period. If the call
duration exceeds one period, there may be no number of seizures, connections and
answers but there are seizure, connection and answer traffic.
5-7
5.5.6 Inaccurate Traffic Statistics Caused by Modification of Trunk Group

Data
The TK group outgoing traffic measurement is a task of bearer object traffic statistics.
When creating such a statistics task, set up the measure object according to the
selected trunk group and the trunk group table index in the database and allocate the
counters for statistics. However, after the setting of the statistics task, these objects
and counters will not change within a statistics period. When the next statistics period
begins, the measure object will be set up again according to the trunk group table
index in the database and the counters for statistics will be allocated.
Suppose there is a created statistics task. The statistics period is 1 hour beginning at
10:00, and the trunk group data is modified during 10:00~11:00. For example, a trunk
group is added or deleted. The trunk group table index in the database will change
accordingly, but the measure object and counter will not change, so the entire statistic
result cannot reflect the practical situation, then the traffic statistic result is rather
random. The “Result accuracy” item in the output report at 11:00 will also be displayed
as “Data setting”, indicating that the traffic statistic result fails to reflect the practical
situation and is inaccurate. In the statistics of the next period (11:00~12:00), the
system will set up the measure object again according to the trunk group table index
in the database and allocate counters for statistics, therefore, the statistic result in this
period will be correct and “Result accuracy” in the report sent out at 12:00 will be
“Accurate”.
5.5.7 Causes of Incomplete Traffic Statistics
The background will work out the results which should be received by the traffic
statistic task according to the number of traffic statistics subtasks and number of
modules. If the reports cannot be received completely in a specified delayed time
(usually 15 minutes) after the statistic period ends, the received results will be output
and the accuracy will be marked as “Result received incompletely”. As part of the
result is missing, the report will be inaccurate.
Traffic statistic results are not received completely mainly because:

z A certain module is faulty, not activated or communication is congested.
z A certain module is switched or reset in the statistics period.
z A task which will generate a great deal of traffic statistic results has been
registered, such as service quality evaluation.
z There are many Remote Switching Modules (RSM). Due to limited
communication capabilities, when many statistical reports, especially those with
many entities such as office direction outgoing and trunk group outgoing, are
sent, it is probable that the results are not received completely.
5-8
z If the processing of the background traffic statistics console is abnormal, the

traffic statistics cannot be received. To resolve the problem, just restart the traffic
statistics console.
5.5.8 Use of the Service Quality Traffic Measurement
The service quality evaluation is unique because it has no statistics period. Once
there is any call satisfying the statistics conditions, a result report will be sent to the
background so as to output the call information in real time. If all inlets, all outlets, all
call attributes, all destination codes, all successful and failed calls are selected as the
measure objects of the combined type, the switch will generate a statistical result for
each call, causing BAM overload and communication congestion. Therefore, be
careful to use the service quality evaluation. If it is used, the range of measure objects
should be limited, for example, a specific incoming trunk group is selected as the inlet,
and a specific destination code is selected as the outlet. In addition, sampling times or
sampling rate can also be set to reduce the number of outputs.
5.5.9 Precautions for Using Max/Min Value Traffic Statistics
The traffic statistics of maximum values is a powerful tool for improving the connection
ratio, but pay attention to the following points when using it.
z The statistics of maximum values must begin at the clearing time of the
maximum value (4:00 by default) and end at the ending hour of the statistics (that
is, the report output hour). For example, to set up a task to make statistic analysis
of busy called users, set the start time to 8:00 and the ending time to 10:00, with
the statistics period of one hour. There will be two time points at which the switch
outputs reports everyday for the statistics task, that is, 9:00 and 10:00. The
report output at 9:00 gives the top 10 busy called users during 4:00~9:00, while
the report output at 10:00 gives the top 10 busy called users during 4:00~10:00.
z The statistics of maximum values must begin at the clearing time of the
maximum value because the statistics must be performed continuously to all
subscribers of a module, so a great deal of memory overhead is needed.
Therefore, the result is not obtained from the difference between the values of
two counters (while it is the case for ordinary statistic entities), instead, it is
obtained through counter accumulation. In addition, as the maximum value
needs continuous sorting, and the system loads are heavy, it is better not to use
it for a long time.
z To perform the statistics of maximum values in a certain time segment, for
example, the statistics during 9:00~10:00, just modify the SET TRFTPTM
command to set the clearing time of the maximum value as 9:00. Then the
maximum values in the time segment of 9:00~10:00 can be counted.
5-9
5.5.10 Why “Number of Answers + Number of Failures < Number of Seizure

Attempts (Seizures)”
In the statistics of the outgoing and incoming traffic of a trunk group or an office
direction, the number of failures only shows the main causes. Therefore, the sum of
the number of answers and that of failures is less than the number of seizures
because the number of failures counted here is incomplete. To obtain all the failures,
use the multi condition object traffic statistics which provides all the failure causes,
and the result will be “number of answers + number of failures = number of seizures”.
5.5.11 Why Some Entity Results are “Unknown” in Multi Condition Object
Traffic Statistics
The multi condition object traffic statistics, failure cause summary and intelligent
sampling tracing are long-result measure units (that is, many output entities), and also
provide the statistics of more than one hundred failure causes. If all entities are output,
the readability of the output report will be affected. Therefore, the system sends only
the statistical results which are not “0” to the background. The background also
outputs selectively according to the results. For example, conduct statistic analysis of
two multi condition objects, and count the failure causes for the office direction 1 and
office direction 2 respectively. The failure caused by “Call restricted” occurs in the
office direction 1 twice, while the failure caused by “No-dialing timeout” occurs in the
office direction 2 for threes times. The reports are as follows:
Office direction 1:
........
Call restricted 2
........
Office direction 2:
........
No-dialing timeout 3
........
However, to count the failure causes for the office direction 1 and office direction 2 in
the traffic statistics of one multi condition object, the report is as follows.
Office direction 1 Office direction 2
.......
5-10
Call restricted 2 Unknown
No-dialing timeout Unknown 3
........
This is because multiple objects and their failure causes in the traffic statistics of the
multi condition object correspond to each other one by one. For example, “Call
restricted” occurs in the office direction 1, so it will be displayed in the report, but there
is no such failure cause in the office direction 2, thus with no value of this entity in the
result to be sent to the background, so the background cannot obtain this entity value,
and can only display “Unknown” for output.
5.5.12 Measurement of Access Network Users
The telecom operator often hopes to count the access network users from the switch
side according to the Optical Network Unit (ONU) or the module number (or frame
number) of the access network. Actually, the switch is connected to the access
network through V5-interfaces, therefore, the ONU and module number (frame
number) of the access network are invisible for the switch, so the statistics cannot be
performed directly. However, indirect statistics can be performed through flexible
restriction of the multi condition object traffic statistics, mainly through the calling
numbers of the access network users.
To count the access network users, first ensure that respective ONUs or access
network modules can be distinguished by the prefix, that is, the characteristics of the
calling numbers.
To count the calls when access network users are the calling parties, type the
corresponding calling numbers. For example, to count the calls when the access
network users of a frame are callers, with the numbers 1234000~1234299, type
“k'12340&&k'12342” as the calling number, skip other parts of the measure object
(such as inlet, outlet, call attribute and destination code) or select “All” for them. Select
“Summary by period” for the output report options, then the report will list the
statistical results with users of 1234000~1234299 serving as callers.
To count the calls when access network users are the called parties, type the
corresponding destination codes. For example, to count the calls when the access
network users of a frame are called parties, with the numbers 1234000~1234299,
type “k'12340&&k'12342” in the destination code column, skip other parts of the
measure object (such as inlet, outlet, call attribute and destination code) or select “All”
for them. Select “Summary by period” for the output report options, then the report will
list the statistical results with users of 1234000~1234299 serving as called parties.
5-11
5.5.13 Influence on Traffic Statistics during Version Upgrade
During version upgrade, both the operator console program and host program may
vary, and the related data of traffic statistics may change as well. If the original traffic
statistic task is still used, such aspects as objects and data may not cooperate well. In
addition, the module may be restarted in the process of upgrade, causing the traffic
statistic task to be interrupted temporarily, resulting in the confusion of traffic statistic
results. Therefore, delete all the traffic statistic tasks before an upgrade and then
create them again after the upgrade completes and all modules work normally.
5-12
C&C08 Digital SPC Switching System Appendix A Operations in MML Command Line Mode
Appendix A Operations in MML Command Line

Mode
A.1 Creating a Traffic Statistics Task
Different from the graphic-aided input, the command line-aided input generally needs
to create a traffic statistics task on a single interface (as shown in Figure A-1). The
traffic statistics operations in the MML command line mode is illustrated as follows.
Suppose to measure the supplementary calls from No. 6 office direction to the
destination code 6543452 (its DN set is 0) for 50 days starting on December 12, 2001.
The traffic is measured in three time segments, namely, 7:00~9:00, 12:00~14:00 and
17:00~19:00 from Monday to Thursday of each week. The measurement cycle is one
hour, and the traffic result is permanent periodically output to the current workstation.
The sampling ratio of the measurement is set as 10%. The operation procedures are
as follows.
Figure A-1 Creating a traffic statistics task
A-1
It is obvious that the measure unit corresponding to this task is

"Multi_Condition_Object_Traffic". Since the "Multi_Condition_Object_Traffic" belongs
to the call record task, select [Traffic statistics/Create traffic statistics job/Create Call
Record Task (CRE TRFCLR)]. The corresponding command will appear in the
[Command input] box on the right bottom of the interface. Click the icon, and an
interface for inputting the parameters of this task will appear.
According to the task conditions, set the [task ID] to a correct task ID, the [measure
unit] to "MICDT" (Multi_Condition_Object_Traffic), the [period] to “H1 (1 hour)”, the
[start time 1] to “07&00”, the [end time 1] to “09&00”, the [start time 2] to “12&00”, the
[end time 2] to “14&00”, the [start time 3] to “17&00”, the [end time 3] to “19&00”, the
[start date] to “2001&12&12” and the [duration days] to “50”. As the measurement
days are fixed from Monday to Thursday of each week, set the [measure days cycle]
to “WEEK (weekly cyclic)”. If the measurement is performed everyday, set it to “DAY
(daily cycle)". If the measurement is performed in a few days regularly per month, set
it to “MONTH (monthly cycle)”. Set the [measure day] to “1&4”, which indicates the
days from Monday to Thursday. Set the [output device] to “CWS (current workstation)”,
the [output mode] to “PP (permanent periodically output)”. Since the “permanent
periodically output” is selected, the output time is not necessary to be set. Set the
[sampling rate] to “10”, which indicates that the sampling rate is 10%.
Finally, select measurement objects. In the measure unit of

“Multi_Condition_Object_Traffic”, the measurement objects include five parts, namely,
incoming terminal, outgoing terminal, call attributes, destination code and calling
number. Not all parts need to be matched. In this example, only the incoming office
direction, outgoing subscriber code and call attribute need to be matched. Therefore,
set the [inlet office direction] to “6”, the [external code of outlet subscriber frame] to
“0-k'6543452”, and the [call attribute] to “NS (call of supplementary service)”.
Although it is not necessary to match the destination code and the calling number,
“all......” must be selected as required. Therefore, set the [all destination codes] and
[all caller numbers] “ALL”.
So far, all parameters for this task have been entered. Click the icon to complete
the creation of the task.
Note:
It should be noted that the parameters vary with the measure units.
A-2
A.2 Setting a Customized Entity
Select [Traffic statistics/Modify traffic statistics job/Set Custom Entity (SET

CUSTENT)] in the navigation tree on the left side of the interface, and the SET
CUSTENT command will appear in the [command input] box on the right bottom of the
interface. Click the icon , and an interface displaying the parameters of the
command will appear. The [entity alias] is a string of English letters, the [entity name]
is a combination of letters and numbers, the [entity unit] and [entity type] are
determined according to the entity features. The [redefine entity] is valid only when
the existing entity is being modified and indicates the modified entity. The [formulae] is
used for the calculations of the addition, subtraction, multiplication and division of the
existing entities (specified as alias). The aliases of the existing entities can be
searched in the [redefine entity].
Suppose to define a new entity “abandon times” (ABN as entity alias) in the
“Multi_Condition_Object_Traffic” unit. It complies with the formula "ABN = BRGABN +
ARGABN", in which, "BRGABN" indicates the number of abandons before the
telephone rings, and the "ARGABN" indicates the number of abandons before the
called party answers. "BRGABN" and "ARGABN" are existing entities. The interface
for defining this entity is shown in Figure A-2. Obviously, the new entity has no
measure unit, and the display type is an integer.
Figure A-2 Setting a customized entity
A-3
A.3 Modifying Task Attributes
In the MML command line mode, the operations of modifying task attributes include
the following:
z Modify traffic task time (MOD TRFTM)
z Modify traffic task output entity (MOD TRFOENT)
z Modify traffic task sampling parameter (MOD TRFSMP)
z Modify traffic result output device (MOD TRFODA)
z Modify traffic result output mode (MOD TRFOTA)
z Set traffic task entity threshold (SET TRFTHD)
z Add traffic task measure object (ADD TRFMO)
z Activate traffic task (ACT TRFTSK)
z Deactivate traffic task (DEA TRFTSK)
z Set extremum task clear time (SET TRFTPTM)
Take “Modify traffic task output entity” (MOD TRFOENT) for example. The following is
an illustration for the operations of modifying traffic statistics attributes.
Select [Traffic statistics/Modify traffic statistics job/Modify Traffic Task Output Entity
(MOD TRFOENT)] in the navigation tree on the left of the interface shown in Figure
A-3, and the MOD TRFOENT command will appear in the [command input] on the
right bottom of the interface. Then click the icon , and the interface for inputting
some parameters will appear. The interface for inputting all parameters will not appear
until a specific measure unit is selected. Select an option in the [entity set] field, and
the selected entity will replace the original output entity. Select an option in the [entity
add] field, and the selected entity together with the original output entity will be output.
Select an option in the [entity del] field, and the selected entity cannot be output.
Moreover, the preceding three items or any two of them can be simultaneously
selected to jointly determine the output entities, but which is hard to understand and
tends to cause error, so it is recommended to use only one of them.
A-4
Figure A-3 Modifying output entities of a traffic statistics task
Note that the output entities of all tasks cannot be modified. For example, if the
“Multi_Condition_Object_Traffic” measure unit is selected, the output entity cannot be
modified. Generally, if no option of the output entity is set when a task is being created,
the output entity of this task is impossible to be modified.
A.4 Deleting a Traffic Statistics Task
In the MML command line mode, the operations of deleting a traffic statistics task
include the following:
z Deleting traffic task (DEL TRFTSK)
z Delete traffic task entity threshold (DEL TRFTHD)
z Delete traffic task measure object (RMV TRFMO)
z Delete custom entity (DEL CUSTENT)
A.5 Querying Traffic Statistics Tasks
In the MML command line mode, the operations of querying traffic statistics tasks
include the following:
z List traffic task information (LST TRFINF)
z List traffic result report (LST TRFRPT)
A-5
z Display extremum task clear time (DSP TRFTPTM)

z List custom entity (LST CUSTENT)
Take the “List traffic result report (LST TRFRPT)” as an example to describe the
operations of querying a traffic statistics task.
Select [Traffic statistics/Query traffic statistic/List Traffic Result Report (LST TRFRPT)]
in the navigation tree on the left side of the window shown in Figure A-4, and the LST
TRFRPT command will appear in the [command input] box on the right bottom of the
interface. Click the icon , and the interface for inputting some of the parameters
will appear. Go on to specify the [time type] field, and the interface for typing the time
parameters will appear.
Figure A-4 Listing traffic statistics result report
[entity style]
It specifies the style that the report outputs entities, including ORG (original), EVL
(evolve), BRF (brief), and DTL (detailed).
z If it is set to "ORG", the report will output only the original entities rather than the
customized entities.
z If it is set to "EVL", the report will output the customized entities that are modified
from the original entities) in addition to the original entities.
A-6
z If it is set to "BRF", the report will output the customized entities that are modified
not from the original entities in addition to the original entities.
z If it is set to "DTL", the report will output all entities, including the original entities
and customized entities.
[report type]
Generally, the traffic statistics task will output a result report for each object during
each period (if the “permanent periodical output” is selected when creating the task).
Especially when a task contains many objects or lasts for many periods, lots of result
reports will be produced, which will have little contents and are hard to view. Therefore,
these original output reports need to be combined according to a certain principle into
a few reports with rich contents to facilitate viewing. Such principle constitutes a report
type. It includes NML (normal), PRD (sum by period), OBJ (sym by object), and
PRDOBJ (sum by period and object). For example, a traffic statistics task has two
measurement objects and 10 measurement periods. It will produce 20 original output
reports.
z If it is set to “NML”, the original report will be finally displayed.
z If it is set to “PRD”, the reports of two measurement objects in the same period
will be combined, forming 10 final reports.
z If it is set to “OBJ”, the reports of the same object in different periods will be
combined, forming two final reports.
z If it is set to “PRDOBJ”, all reports will be combined, forming one final report.
[output device]
It refers to the destination to which the output result will be sent. It includes CWS
(current workstation), STATS (traffic statistics port) and NMP (NM port).
[time type]
It refers to the type of the time segment during which the results are to be viewed. It
includes SEG (segment) and CON (continuant). For example, view the traffic
statistics result from 10:30, December 12, 2001 to 10:30, December 13, 2001. The
time segment is CON. So set the [start date], [start time], [end date] and [end time] to
"2001&12&12", "10&30", "2001&12&13" and "10&30" respectively. In another
example, view the traffic statistics result between 8:30~10:30 of each day from
December 12, 2001, to December 13, 2001. The time segment is SEG. Set the [start
date], [start time], [end date] and [end time] to "2001&12&12", "08&30",
"2001&12&13" and "10&30" respectively.
A-7
C&C08 Digital SPC Switching System Appendix B Report Format of Traffic Statistical
Appendix B Report Format of Traffic Statistical
The C&C08 traffic statistical report is composed of one or more sub-reports, and
each sub-report is divided into three parts: report head, report body and report tail,
and a blank line is left between them.
B.1 Date and Time Format of Traffic Statistical Report
I. Date Format
In accordance with the international standard (ISO 2014), enter the calendar date in
the fully digital form, which shall be written in the form of year-month-day.
Year consists of four decimal digits.
Month consists of two decimal digits, ranging from 01 to 12.
Day consists of two decimal digits, ranging from 01 to 31.
Year, month and day are separated by "-".
II. Time Format
The time is expressed in the 24-hour system. The time elements are arranged in the
order of hour, minute and second (from left to right).
Hour is expressed in two decimal digits, ranging from 00 to 23 inclusive;
Minute is expressed in two decimal digits, ranging from 00 to 59 inclusive;
Second is expressed in two decimal digits, ranging from 00 to 59 inclusive;
Hour, minute and second are separated by colon [:].
B.2 Descriptor Explanation
The content in a pair of angle brackets <> is the content for actual output. Table B-1
lists the meanings of the specifiers in angle brackets.
Table B-1 Meanings of the specifiers in angle brackets
Output Meaning
<nSP> n consecutive space characters
<XXX'An> A0 stands for left alignment, A1 stands for right alignment. Left alignment is the default value.
<XXX'Mn> 'Mn stands for the maximum length (n characters) of this information section.
B-1
Output Meaning
'Ln stands for the total length (n characters) of this information section, and the vacant part is
<XXX'Ln>
filled by space. L0 stands for the actual length of the field output. No fill-in is needed.
<XXX> Words underlined, they determine the output typeface.
<XXX> XXXX are the actual output change of other parts.
For example, <office name'M32A0> indicates the office name can have a maximum
of 32 characters and is left aligned.
If some part of the information is vacant, please fill <NULL>.
B.3 Description of Report Head
The report head consists of three lines, each of which has multiple information
blocks. Each information block has a fixed middle-line starting location, and a space
is needed between two pieces of information. Each line displays the following
information:
Line 1: General starting ID, office name, report output date and time;
Line 2: Traffic statistical report ID "TRAFFIC", the task number to which a report
belongs, measurement unit name;
Note:
The task number is prefixed with "#".
Line 3: The starting date & time, ending date & time and cycle of the statistics, the
ending date and time of this batch of statistical results;
Note:
Fill <NULL> in the lacked item. For instance, there is no starting and ending date and time for the
statistics of some tasks, such as permanent task.
The contents in measurement unit description are abbreviations of measurement

units.
z Line 1:
B-2
<Starting ID +++> <4SP> <Office name'M32><8SP><Report output

date'M10><1SP><Report output time'M8> <New line \r\n>
z Line 2:
<Traffic statistical report flag TRAFFIC><4SP><#Task number'M10><8SP><

Measurement unit'M48> <New line \r\n>
z Line 3:
<Statistical task starting date'M10><5SP><Statistical task ending

date'M10><5SP><Statistical cycle (the default unit is
minute)'M4><5SP><Statistical result starting date'M10><1SP><Statistical
result starting time'M8> <New line \r\n>
B.4 Description of Report Body
Report body can have two or more lines. The first line is measurement entity name
(including its unit), and each line followed is a record, corresponding to a statistical
object of the statistical task. All records are aligned in order.
Measurement entity name: some entities attached with measurement unit.
Measurement entity unit: For some measurement entities whose units are apparent,
no unit is indicated in the body; for the measurement entities that may have different
meanings, the units will be displayed, for example, the measurement entities related
to time. The output mode: closely after the entity is a pair of brackets, in which the
unit name abbreviation (in English) is inputted. For example, in the case of the
statistics of answer times, the measurement entity name only displays "ANS"; in the
case of dialing tone delay, the measurement entity name displays "DTDE(ms)".
Note:
When indicating a measurement entity unit, the brackets are in DBC case (English mode), and the unit
is written in accordance with the international convention. Report body has only one form, providing
both Chinese and English versions and with no difference in forms of single record (for a single
statistical object) and multiple records (for multiple statistical objects).
z Line 1 is the head line:
<Measurement object name 1'L17><1SP><Measurement object name

2'L17><1SP>......<Measurement object name n'L17><1SP><Measurement entity
B-3
name 1'L13><1SP><Measurement entity name 2'L13><1SP>......<Measurement

entity name m'L13><New line \r\n>
z Line 2 - Line L+1 indicate the values from record 1 to record L, as shown
below.
<Measurement object value 1'L17><1SP><Measurement object value

2'L17><1SP>......<Measurement object value n'L17><1SP><Measurement entity
value 1'L13><1SP><Measurement entity value 2'L13><1SP>......<Measurement
entity value m'L13><New line \r\n
B.5 Description of Report Tail
Report tail has two lines.

z Line 1:
a. If the report is not the last part of the series report, its form is shown below.
<Records contained in this report'M6A1> <1SP> <RECORD (S)> <3SP> <IN> <1SP>
<REPORT> <1SP> <#Report serial number'M3> <4SP> <Report continuation mark
CONTINUE> <New line \r\n>
b. If the report is the last part of the series report, its form is shown below.
<Records contained in this report'M6A1> <1SP> <RECORD (S)> <3SP> <IN> <1SP>
<REPORT> <1SP> <#Report serial number'M3> <4SP> <TOTAL> <1SP> <Total records
contained in the series report 'M5A1> <1SP> <RECORD (S)> <New line \r\n>
z Line 2:
<Ending ID ---><4SP><END>
B.6 Report Example
The following is an output example of the trunk group outgoing traffic measurement,
it is explained as figure 1.
Figure B-1 Report Example
Line 1 to Line 3 are the report head.
Line 4 is a vacant line.
B-4
Line 5 is the head line, where the OBTKG is the measurement object, and what
follows the BID is the measurement entity name.
Line 6 is the recorded values, which correspond to the head lines respectively. The
suspension points indicate that several measurement entity names and their
corresponding values are omitted.
Line 7 is a vacant line.
Lines 8 and 9 are the report tail.
B-5
C&C08 Digital SPC Switching System Appendix C Acronyms and Abbreviations
Appendix C Acronyms and Abbreviations

A
ABS Absent service
ACFT Activating Call Forwarding Table
ACK Acknowledgement
ACM Address Complete Message
AM Administration Module
AN Access Network
ANS Answer Times
ASL Analog Subscriber Line Board
B
BAM Back Administration Module
BCC Bearer Channel Connection
BRA Basic Rate Adaptation
BRF Brief
C
CAS Channel Associated Signaling
CB Calling back on Busy
CCB Central Communication Database
CF Call Forwarding Services
CFB Call Forwarding Busy
CFNR Call Forwarding No Reply
CFU Call Forwarding Unconditional
CIC Circuit Identification Code
CID Caller Identification Display
CLI Calling Line Identification
CLIP Calling Line Identification Presentation
CLIR Calling Line Identification Restriction
CNT Call Connected Times
COLP Connected Line Identification Presentation
COLR Connected Line Identification Restriction
COND Conference Disconnect
CONF Conference Calling
CP Designated Pick-up
CPU Central Processing Unit
CR Connection Request
CTX Centrex Group
CW Call Waiting
CWS Current WorkStation
D
DCN Data Communication Network
DID Direct Inward Dialing
DNB Destination Number Barred
DPC Destination (Signaling) Point Code
DRV Dual Tone Number Receiving & Drive Board
DSL Digital Subscriber Line
DSP Destination Signaling Point
DTL Detailed
DTMF Dual Tone Multi Frequency
DTR Dual Tone Transmit/Receive
E
ECP Echo Cancellation Process
F
FAM Front Administration Module
FSK Frequency Shift Keying
H
HL Hot Line Service
HW Highway
C-1
I
IBTKG Incoming or Bi-directional Trunk Group
ID Identification
IHL Instant Hot Line
ISDN Integrated Services Digital Network
ISM Inlet SM
ISUP ISDN User Part
L
LE Local Exchange
LT Local Tandem
M
MCT Malicious Call Tracing
MFC Multi-Frequency Compelled Board
MFS Multi Frequency Shuttle
MMI Man Machine Interface
MML Man Machine Language
MPASS Modify Password
MSU Message Signaling Unit
MTP Message Transfer Part
N
NI Network Identifier
NM Network Management
NMP NM Port
NT1 Network Terminal 1
O
OCB Outgoing Call Barring
OM Outgoing Module
ONU Optical Network Unit
OPC Originating Signaling Point Code
OPDIS Operator Disconnect
OSM Outlet SM Module
P
PABX Private Automatic Branch Exchange
PBX Private Branch Exchange
PHI Packet Handling Interface
PHY Physical Layer
PIG Pick-up in the Group
PIN Personal Identification Number
PRA Primary Rate Adaptation
PRI Primary Rate Interface
PSTN Public Switched Telephone Network
PSVC Package Service
R
RAM Random Access Memory
RCFB Remotely-set Call Forwarding Busy
RCFNR Remotely-set Call Forwarding No Reply
RCFU Remotely-set Call Forwarding Unconditional
RSA Remote RSA Interface Board
RSM Remote Switching Module
S
SM Switching Module
SN Subscriber Number
SP Signaling Point
SPC Software Program Control
SPM Service Processing Module
SRM Specialized Resource Module
SS Secretary Station
SS7 Signaling System No. 7
SSVC Secretary Service
ST Subscriber Terminal
T
TP Terminal Portability
TUP Telephone User Part
U
C-2
UUS User to User Signaling
C-3

Operation Manual-Traffic Measurement Volume PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Operation Manual-Traffic Measurement Volume PDF

Uploaded by

Copyright:

Available Formats

Chapter 1 Traffic Measurement Overview .....................................................

C&C08 Digital SPC Switching System

Volume Traffic Measurement Volume

Manual Version T2-011692-20041130-C-4.10

Product Version OVSV610R103

Huawei Technologies Co., Ltd.

Address: Administration Building, Huawei Technologies Co., Ltd.,

Bantian, Longgang District, Shenzhen, P. R. China

Postal Code: 518129

All Rights Reserved

No part of this manual may be reproduced or transmitted in any form or by any

, HUAWEI, C&C08, EAST8000, HONET, , ViewPoint, INtess, ETS, DMC,

It consists of two volumes. The Troubleshooting Volume details on

It offers an overall introduction to the C&C08 Digital SPC Switching

It provides information for the system installation, including the

It introduces almost all the boards available in the C&C08 Digital

Organization of the Manual

There are five chapters and two appendixes in the manual.

Chapter 4 Traffic Measurement Application focuses on how to achieve daily

Chapter 5 Solutions to Common Problems gives a description of common problems

Appendix C Acronyms and Abbreviations collects the acronyms and abbreviations

The manual is intended for the following readers:

This manual uses the following conventions:

Arial Normal paragraphs are in Arial.

Boldface Headings are in Boldface.

II. Command conventions

Boldface The keywords of a command line are in Boldface.

italic Command arguments are in italic.

[] Items (keywords or arguments) in square brackets [ ] are optional.

III. GUI conventions

Multi-level menus are separated by forward slashes. For example,

IV. Keyboard operation

Note: Means a complementary description.

Chapter 1 Traffic Measurement Overview .................................................................................. 1-1

Chapter 2 Traffic Measurement Operations ............................................................................... 2-1

Chapter 3 Measure Units and Entities......................................................................................... 3-1

3.2.2 Office Direction Outgoing Office Traffic ................................................................ 3-31

3.5.10 TUP Total MSU Traffic ........................................................................................ 3-65

3.9.8 IN Operation Traffic............................................................................................... 3-98

Chapter 4 Traffic Measurement Application............................................................................... 4-1

Chapter 5 Solutions to Common Problems ................................................................................ 5-1

5.5.5 Some Special Instances of Traffic Statistics ........................................................... 5-7

Appendix A Operations in MML Command Line Mode .............................................................A-1

Appendix B Report Format of Traffic Statistical ........................................................................B-1

Appendix C Acronyms and Abbreviations .................................................................................C-1

Chapter 1 Traffic Measurement Overview

1.1 Basic Concepts

Traffic statistics, also called traffic measurement, payload measurement, refers to

measurement of the ISDN forwarding traffic. Generally, a traffic measurement

1.2 Functional Features

I. Task management function

The management of traffic measurement tasks includes creating/deleting a

II. Exception report

III. Brief report

IV. Sampling measurement

V. Measurement report incredible

VI. Screening measurement to CID numbers

VII. Outputting the measurement result in the call record mode

VIII. No loss of measurement tasks in case of switchover and reloading

IX. Dynamical modification of a task

Dynamical modification of a task includes the modification of the measurement time,

X. Display and storage of measurement results

XI. Self-defined entity