SoftX3000 Operation Manual-GUI Guide

Chapter 1 Introduction to GUI ........................................................................
1-1
1.1 Composition of GUI ................................................................................ 1-1
1.2 Description of GUI Components ............................................................. 1-1
1.2.1 Overview of GUI Components ....................................................... 1-1
1.2.2 Menu Bar ....................................................................................... 1-2
1.2.3 Toolbar ........................................................................................... 1-3
1.2.4 Navigation Tree.............................................................................. 1-3
1.2.5 System Result Pane ...................................................................... 1-4
1.2.6 Command Window ......................................................................... 1-4
1.2.7 Shortcut Keys................................................................................. 1-6
1.2.8 GUI Applications on the BAM ........................................................ 1-6
1.2.9 GUI Applications on the Client ....................................................... 1-7
1.3 Starting GUI ............................................................................................ 1-8
1.3.1 Starting MML Client ....................................................................... 1-8
1.3.2 Starting Alarm Management System ............................................. 1-9
1.3.3 Starting Performance Management System .................................. 1-10
Chapter 2 Using MML Client ........................................................................... 2-1
2.1 Using System Menus ............................................................................. 2-1
2.1.1 Logging In ...................................................................................... 2-1
2.1.2 Re-logging In .................................................................................. 2-1
2.1.3 Logging Out ................................................................................... 2-2
2.1.4 Changing Password ....................................................................... 2-2
2.1.5 Managing Office Information .......................................................... 2-3
2.1.6 Setting Output Configurations ........................................................ 2-7
2.1.7 Setting Command Timeout Duration .............................................. 2-10
2.1.8 Saving Input Commands ................................................................ 2-10
2.1.9 Executing Commands in Batch ...................................................... 2-11
2.1.10 Stopping Executing Commands in Batch ..................................... 2-18
2.1.11 Setting Printing Options ............................................................... 2-19
2.1.12 Printing in Real Time .................................................................... 2-19
2.1.13 Flushing Printer ............................................................................ 2-19
2.1.14 Locking Client .............................................................................. 2-20
2.1.15 Automatically Locking Client ........................................................ 2-20
2.1.16 Exiting .......................................................................................... 2-21
2.2 Using Service Menus ............................................................................. 2-21
2.2.2 Starting Performance Management System .................................. 2-22
2.3 Using Authority Menus ........................................................................... 2-22
2.3.1 Classification Operation Authorities ............................................... 2-22
2.3.2 Adding Operator Account............................................................... 2-23
2.3.3 Modifying Operator Account .......................................................... 2-24
2.3.4 Deleting Operator Account ............................................................. 2-26
2.3.5 Adding Workstation ........................................................................ 2-26
2.3.6 Modifying Workstation .................................................................... 2-27
2.3.7 Deleting Workstation ...................................................................... 2-28
2.3.8 Setting Command Group ............................................................... 2-29
2.4 Using View Menus .................................................................................. 2-30
2.4.1 Overview of Using View Menus ..................................................... 2-30
2.4.2 Showing or Hiding Windows .......................................................... 2-30
2.4.3 Showing Tools and Status ............................................................. 2-31
2.5 Using Window Menus ............................................................................. 2-31
2.5.1 Cascading Windows ...................................................................... 2-31
2.5.2 Tiling Windows Horizontally ........................................................... 2-32
2.6 Using Help Menus .................................................................................. 2-33
2.6.1 Using SoftX3000 Online Book ....................................................... 2-33
2.6.2 Using Help Topics .......................................................................... 2-35
2.6.3 Calling Online Help of Dialog Box .................................................. 2-36
2.6.4 Calling Pop-Up Online Help ........................................................... 2-36
2.6.5 Querying Version ........................................................................... 2-37
2.7 Using Management Tab ......................................................................... 2-38
2.7.1 Overview of Management Tab ....................................................... 2-38
2.7.2 Browsing Device Panel .................................................................. 2-39
2.7.3 Displaying Board Information ......................................................... 2-41
2.7.4 Resetting Boards ........................................................................... 2-42
2.7.5 Swapping Boards ........................................................................... 2-43
2.7.6 Querying CPU Usage .................................................................... 2-43
2.7.7 Querying Memory Usage ............................................................... 2-44
2.7.8 Configuring Subscriber Data .......................................................... 2-45
2.7.9 Maintaining Subscriber Data .......................................................... 2-47
2.8 Using MML Navigation Tree ................................................................... 2-47
2.8.1 Overview of Using MML Navigation Tree ...................................... 2-47
2.8.2 Using Common Maintenance Pane ............................................... 2-48
2.8.3 Querying History Commands ......................................................... 2-49
2.8.4 Querying Online Help..................................................................... 2-51
2.9 Using Monitor Tab .................................................................................. 2-51
2.9.1 Overview of Using Monitor Tab...................................................... 2-51
2.9.2 Trace Management Tasks ............................................................. 2-52
2.9.3 Maintenance Management Tasks .................................................. 2-53
2.10 Using the Toolbar ................................................................................. 2-53
Chapter 3 Using Alarm Management System ............................................... 3-1
3.1 Overview of Alarm Management System ............................................... 3-1
3.2 Classification of Alarms .......................................................................... 3-1
3.2.1 Classifying Alarms by Type............................................................ 3-1
3.2.2 Classifying Alarms by Level ........................................................... 3-2
3.3 Generic Operations ................................................................................ 3-3
3.3.2 Customizing Alarm Colors ............................................................. 3-4
3.4 Browsing Alarms .................................................................................... 3-5
3.4.1 Browsing Fault Alarms ................................................................... 3-6
3.4.2 Browsing Event Alarms .................................................................. 3-7
3.4.3 Browsing History Alarms ................................................................ 3-8
3.4.4 Defining Alarm Filter Settings ........................................................ 3-8
3.4.5 Filtering Alarms of Malicious Calls and Emergency Calls .............. 3-9
3.5 Querying Alarms ..................................................................................... 3-9
3.5.1 Notes on Querying Alarms ............................................................. 3-9
3.5.2 Operation Procedure ...................................................................... 3-9
3.6 Alarm Management Operations ............................................................. 3-10
3.6.1 Deleting History Alarms ................................................................. 3-10
3.6.2 Masking Alarms ............................................................................. 3-11
3.6.3 Querying Alarm Configurations ...................................................... 3-13
3.6.4 Defining Alarm Box Control Settings .............................................. 3-14
3.6.5 Defining Alarm Statistics ................................................................ 3-14
3.6.6 Defining Alarm Box Screen Level .................................................. 3-16
3.6.7 Querying Alarm Box Screen Level ................................................. 3-17
3.6.8 Defining Sound Durations for Fault Alarms.................................... 3-17
3.7 Using Other Alarm Related Options ....................................................... 3-18
3.7.1 Overview of Other Alarm Related Options ..................................... 3-18
3.7.2 Using Shortcut Menu ..................................................................... 3-18
3.7.3 Querying Alarm Explanation Details .............................................. 3-19
3.7.4 Saving Alarm Content to File ......................................................... 3-20
3.7.5 Recovering an Alarm ..................................................................... 3-20
3.7.6 Acknowledging an Alarm ............................................................... 3-21
3.7.7 Clearing Recovery Alarms ............................................................. 3-21
3.8 Defining Print Options ............................................................................ 3-23
3.8.1 Overview of Using Print Options .................................................... 3-23
3.8.2 Defining Real Time Print Filter Settings ......................................... 3-23
3.8.3 Printing Alarm Details in Real Time ............................................... 3-23
3.8.4 Flushing the Printer ........................................................................ 3-23
Chapter 4 Using Performance Management System ................................... 4-1
4.1 Overview of Performance Measurement ................................................ 4-1
4.2 Generic Operations ................................................................................ 4-1
4.2.1 Workflow of Performance Measurement ........................................ 4-1
4.2.2 Logging in to the Performance Management System .................... 4-2
4.3 Cautions and Notes ................................................................................ 4-4
4.3.1 Maximum Number of Tasks ........................................................... 4-4
4.3.2 User Authority ................................................................................ 4-4
4.3.3 Measurement entities..................................................................... 4-5
4.3.4 BAM time ....................................................................................... 4-5
4.4 Creating a Performance Measurement Task ......................................... 4-6
4.4.1 General Workflow .......................................................................... 4-6
4.4.2 Customizing an Entity .................................................................... 4-7
4.4.3 Launching the Task Creation Interface .......................................... 4-10
4.4.4 Defining Task Attributes ................................................................. 4-11
4.4.5 Selecting a Measurement Unit ....................................................... 4-12
4.4.6 Selecting Measurement Entities .................................................... 4-12
4.4.7 Selecting a Measurement Object ................................................... 4-15
4.4.8 Setting Time Properties ................................................................. 4-17
4.4.9 Defining Entity Thresholds ............................................................. 4-19
4.4.10 Defining Sampling Parameters and Report Output Mode............ 4-21
4.4.11 Measurement Task State ............................................................. 4-23
4.5 Querying or Dumping Results of a Measurement Task ......................... 4-24
4.5.1 Querying Results of a Measurement Task ..................................... 4-24
4.5.2 Dumping Results of a Measurement Task ..................................... 4-29
4.6 Querying the Details of a Measurement Task ........................................ 4-29
4.7 Modifying Configuration Information of a Measurement Task ................ 4-31
4.7.1 Overview of Modifying Task Configuration .................................... 4-31
4.7.2 Modifying Task Name .................................................................... 4-31
4.7.3 Modifying Task Output Mode ......................................................... 4-31
4.7.4 Modifying Report Output Device .................................................... 4-32
4.7.5 Modifying Measurement Entities .................................................... 4-32
4.7.6 Modifying Time Information............................................................ 4-32
4.7.7 Modifying Sampling Parameters .................................................... 4-32
4.7.8 Modifying Measurement Entity Thresholds .................................... 4-33
4.7.9 Deleting Measurement Entity Thresholds ...................................... 4-33
4.7.10 Adding Measurement Object ....................................................... 4-33
4.7.11 Deleting Measurement Object ..................................................... 4-33
4.8 Deleting a Performance Measurement Task .......................................... 4-34
4.9 Activating and Deactivating a Measurement Task ................................. 4-34
4.9.1 Overview ........................................................................................ 4-34
4.9.2 Deactivating a Task ....................................................................... 4-34
4.9.3 Activating a Task ............................................................................ 4-34
4.10 Setting Clear Time of a Measurement Task ......................................... 4-34
Chapter 5 Trace and Maintenance ................................................................. 5-1
5.1 Trace and Maintenance Navigation Tree ............................................... 5-1
5.2 Interface Trace Tasks ............................................................................. 5-2
5.2.1 Overview of Interface Trace Tasks ................................................ 5-2
5.2.2 Tracing Using Ping ......................................................................... 5-3
5.2.3 Tracing with Trace Route ............................................................... 5-5
5.2.4 Tracing MGCP Messages .............................................................. 5-7
5.2.5 Tracing H.248 Messages ............................................................... 5-11
5.2.6 Tracing MRC Messages ................................................................ 5-15
5.2.7 Tracing SIP Messages ................................................................... 5-16
5.2.8 Tracing H.323 Messages ............................................................... 5-19
5.2.9 Tracing SCTP Messages ............................................................... 5-22
5.2.10 Tracing M2UA Messages ............................................................. 5-25
5.2.11 Tracing M3UA Messages ............................................................. 5-29
5.2.12 Tracing V5UA Messages ............................................................. 5-32
5.2.13 Tracing IUA Messages ................................................................. 5-35
5.2.14 Tracing MTP3 Messages ............................................................. 5-38
5.2.15 Tracing BRA Messages ............................................................... 5-41
5.2.16 Tracing PRA Messages ............................................................... 5-44
5.2.17 Tracing V5 Messages .................................................................. 5-47
5.2.18 Tracing SCCP DPC Messages .................................................... 5-50
5.2.19 Tracing SCCP User Messages .................................................... 5-53
5.2.20 Tracing SCCP MTP Messages .................................................... 5-56
5.2.21 Tracing TCAP SCCP Messages .................................................. 5-59
5.2.22 Tracing TCAP User Messages .................................................... 5-61
5.2.23 Tracing CSP Messages ............................................................... 5-64
5.2.24 Tracing Bill Messages .................................................................. 5-67
5.2.25 Tracing Circuit Messages ............................................................ 5-70
5.2.26 Tracing Console Messages ......................................................... 5-73
5.2.27 Tracing STUN Messages ............................................................. 5-75
5.3 Tracing User Signaling ........................................................................... 5-77
5.3.1 Overview of User Trace Tasks ....................................................... 5-77
5.3.2 Tracing Interface Signaling ............................................................ 5-78
5.3.3 Tracing Call Connections ............................................................... 5-81
5.4 Using Maintenance Management Node ................................................. 5-85
5.4.1 Overview of Maintenance Management Node ............................... 5-85
5.4.2 Querying CPU Usage .................................................................... 5-86
5.4.3 Querying Memory Usage ............................................................... 5-87
5.4.4 Querying Inquire Memory .............................................................. 5-89
5.4.5 Dumping Memory Content ............................................................. 5-91
5.4.6 Querying MTP3 Link Status ........................................................... 5-92
5.4.7 Querying No.7 Link Status ............................................................. 5-93
5.4.8 Querying Media Gateway Status ................................................... 5-94
5.4.9 Querying H.323/SIP Terminal Status ............................................. 5-95
5.4.10 Querying MGCP/H.248 Terminal Status ...................................... 5-96
5.4.11 Querying Module Communication Status .................................... 5-97
5.5 Exporting and Reviewing Trace Results ................................................ 5-98
5.5.1 Processing Trace Results .............................................................. 5-98
5.5.2 Using Trace Viewer........................................................................ 5-99
5.6 Analyzing Signaling Trace Results ......................................................... 5-102
5.6.1 Functions of Signaling Analysis ..................................................... 5-102
5.6.2 Description of Signaling Analysis Interface .................................... 5-103
5.6.3 Signaling Analysis Operations ....................................................... 5-104
Chapter 6 Using GUI on BAM ......................................................................... 6-1
6.1 Using BAM Application Software............................................................ 6-1
6.1.1 Understanding Meanings of Service Processes ............................ 6-1
6.1.2 Starting BAM Application Software ................................................ 6-1
6.1.3 Using Service Management Process ............................................. 6-4
6.1.4 Configuring Server Startup Information ......................................... 6-5
6.2 Using BAM Server Gateway Tool ........................................................... 6-6
6.2.1 Starting BAM Server Gateway Tool ............................................... 6-6
6.2.2 Creating Connection ...................................................................... 6-7
6.2.3 Interrupting Connection.................................................................. 6-9
6.3 Using Workstation Gateway Tool ........................................................... 6-9
6.3.1 Starting Workstation Gateway Tool ............................................... 6-10
6.3.2 Creating Connection ...................................................................... 6-10
6.3.3 Interrupting Connection.................................................................. 6-12
6.4 Using BAM Service ................................................................................ 6-12
6.5 Using Smirror Process ........................................................................... 6-15
6.6 Using Automatic Login Tool ................................................................... 6-16
AppendixA Using Data Table Query Tools .................................................... A-1
A.1 Using TableBrowse ................................................................................ A-1
A.1.1 Classifying Data on BAM ............................................................... A-1
A.1.2 Starting TableBrowse .................................................................... A-1
A.1.3 Using File Menus ........................................................................... A-3
A.1.4 Using Tools Menus ........................................................................ A-3
A.1.5 Using View Menus ......................................................................... A-7
A.1.6 Using Window Menus .................................................................... A-7
A.1.7 Using Shortcut menus ................................................................... A-8
A.1.8 Displaying Version ......................................................................... A-9
A.1.9 Using Toolbar ................................................................................ A-10
A.1.10 Using Shortcut Keys .................................................................... A-10
A.2 Using ExTableBrowse ............................................................................ A-11
A.2.1 Classifying Data on Host ............................................................... A-11
A.2.2 Using ExTableBrowse ................................................................... A-11
A.2.3 Using Toolbar ................................................................................ A-14
AppendixB Acronyms and Abbreviations ..................................................... B-1
HUAWEI
U-SYS SoftX3000 SoftSwitch System

Operation Manual GUI Guide
V300R003
Operation Manual
Volume GUI Guide
Manual Version T2-011637-20040331-C-3.30
Product Version V300R003
BOM 31161637
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support
and service. Please feel free to contact our local office 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 2005 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, iSite, U-SYS, iMUSE, OpenEye,
Lansway, SmartAX, infoX, TopEng 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
Release Notes
The manual applies to U-SYS SoftX3000 SoftSwitch System V300R003.
Related Manuals
The related manuals are listed in the following table.
Manual Content
It provides an overall introduction to the SoftX3000,
including product features, applications, and technical
Technical Manual-System Description
specifications.
It details on the hardware architecture, component
interworking mechanism, and subsystems of alarm, billing,
Technical Manual-System Principle
and clock in the SoftX3000.
It details the features and technical specifications of the
hardware components of the SoftX3000, including cabinets,
Hardware Description Manual
frames, boards, cables, and cabinet internal components.
It covers various services and functions supported by the
SoftX3000, including voice services, supplementary
U-SYS SoftX3000 SoftSwitch System services, IP Centrex services, multi-media services, value
Service and Features Manual added services, dual homing functions, charging functions,
IPTN functions, remote network access functions, and so
on.
It details the installation procedure of the SoftX3000
hardware components, and matters needing attention
Hardware Installation Manual
during the installation process.
It covers the detailed procedure of installing the SoftX3000
U-SYS SoftX3000 SoftSwitch System software, including BAM server, emergency workstation,
Software Installation Manual and client, focusing on the key points that might cause
installation failure.
It guides the maintenance engineers to perform daily
maintenance, monthly maintenance, and yearly
Routine Maintenance Guide
maintenance tasks on the SoftX3000.
It guides the maintenance engineers to perform recovery
U-SYS SoftX3000 SoftSwitch System operations in the case of emergencies, such as congestion
Emergency Maintenance Manual of global service, AMG, and TMG, and failure of host and
BAM.
Manual Content
It guides the maintenance engineers on how to replace
hardware components of the SoftX3000, such as boards,
Part Replacement Guide
fan frame, LAN Switch, and hard disk.
It guides the engineers how to configure various data in the

U-SYS SoftX3000 SoftSwitch System SoftX3000, including configuration steps, preparations,
Operation Manual-Configuration Guide database table referencing relationships, and command
parameters.
U-SYS SoftX3000 SoftSwitch System It guides the engineers how to configure various data in the
Operation Manual-Configuration SoftX3000, including networking example, configuration
Examples script, key parameters and debugging guidance.
It guides the engineers how to perform traffic measurement
Operation Manual-Traffic
operations and how to analyze traffic measurement results.
Measurement
It guides the engineers how to use the GUI on various
U-SYS SoftX3000 SoftSwitch
clients of the SoftX3000, including operations on menus
System Operation Manual-GUI
and navigation tree. In addition, it introduces the operations
Guide
on TableBrowse.
It guides the engineers how to install and use the software

related to the BAM, including remote maintenance software,
BAM User Manual
anti-virus software, system customized software, and so on.
It elaborates on the functioning principle of the iGateway
U-SYS iGateway Bill User Manual Bill. Also, it teaches you on how to install, maintain, and
operate the product.
Organization
The manual describes the traffic measurement operations and applications in

SoftX3000 V300R002.
There are six chapters and two Appendixes in the manual.

z Chapter 1 Introduction to GUI introduces the components of SoftX3000
operation and maintenance system.
z Chapter 2 Using MML Client guides you on all available operations on the client.
z Chapter 3 Using Alarm Management System details the operations on the
alarm management system.
z Chapter 4 Using Performance Management System elaborates the operations
on the performance management system.
z Chapter 5 Trace and Maintenance presents the tasks applied in tracing and
maintenance of the SoftX3000.
z Chapter 6 Using GUI on BAM presents the guidance on using the GUI
components on the BAM.
z Appendix A Using Data Table Tools details the operations on using
TableBrowse and ExTableBrowse.
z Appendix B Acronyms and Abbreviations lists the main abbreviations used in
this manual and the corresponding full expressions.
Intended Readers
The manual is intended for the following readers:

z NGN network planning experts
z NGN network administrators
z NGN system engineers
Conventions
The 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.
III. GUI conventions
Button names are inside angle brackets. For example, click the <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. Mouse operation
Action Description
Click Press the left button or right button quickly (left button by default).
Double Click Press the left button twice continuously and quickly.
V. 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:
Caution Means reader be extremely careful during the operation.
Note Means a complementary description.

Operation ManualGUI Guide
U-SYS SoftX3000 SoftSwitch System Table of Contents
Table of Contents
Chapter 1 Introduction to GUI ...................................................................................................... 1-1

1.1 Composition of GUI ........................................................................................................... 1-1
1.2 Description of GUI Components ........................................................................................ 1-1
1.2.1 Overview of GUI Components ................................................................................ 1-1
1.2.2 Menu Bar................................................................................................................. 1-2
1.2.3 Toolbar .................................................................................................................... 1-3
1.2.4 Navigation Tree ....................................................................................................... 1-3
1.2.5 System Result Pane................................................................................................ 1-4
1.2.6 Command Window .................................................................................................. 1-4
1.2.7 Shortcut Keys .......................................................................................................... 1-6
1.2.8 GUI Applications on the BAM.................................................................................. 1-6
1.2.9 GUI Applications on the Client ................................................................................ 1-7
1.3 Starting GUI ....................................................................................................................... 1-8
1.3.1 Starting MML Client................................................................................................. 1-8
1.3.2 Starting Alarm Management System ...................................................................... 1-9
1.3.3 Starting Performance Management System ......................................................... 1-10
Chapter 2 Using MML Client......................................................................................................... 2-1

2.1 Using System Menus......................................................................................................... 2-1
2.1.1 Logging In................................................................................................................ 2-1
2.1.2 Re-logging In ........................................................................................................... 2-1
2.1.3 Logging Out............................................................................................................. 2-2
2.1.4 Changing Password ................................................................................................ 2-2
2.1.5 Managing Office Information ................................................................................... 2-3
2.1.6 Setting Output Configurations ................................................................................. 2-7
2.1.7 Setting Command Timeout Duration..................................................................... 2-10
2.1.8 Saving Input Commands....................................................................................... 2-10
2.1.9 Executing Commands in Batch ............................................................................. 2-11
2.1.10 Stopping Executing Commands in Batch............................................................ 2-18
2.1.11 Setting Printing Options ...................................................................................... 2-19
2.1.12 Printing in Real Time........................................................................................... 2-19
2.1.13 Flushing Printer ................................................................................................... 2-19
2.1.14 Locking Client...................................................................................................... 2-20
2.1.15 Automatically Locking Client ............................................................................... 2-20
2.1.16 Exiting.................................................................................................................. 2-21
2.2 Using Service Menus....................................................................................................... 2-21
2.2.1 Starting Alarm Management System .................................................................... 2-21
2.2.2 Starting Performance Management System ......................................................... 2-22
i
2.3 Using Authority Menus..................................................................................................... 2-22

2.3.1 Classification Operation Authorities ...................................................................... 2-22
2.3.2 Adding Operator Account...................................................................................... 2-23
2.3.3 Modifying Operator Account.................................................................................. 2-24
2.3.4 Deleting Operator Account.................................................................................... 2-26
2.3.5 Adding Workstation ............................................................................................... 2-26
2.3.6 Modifying Workstation........................................................................................... 2-27
2.3.7 Deleting Workstation ............................................................................................. 2-28
2.3.8 Setting Command Group ...................................................................................... 2-29
2.4 Using View Menus ........................................................................................................... 2-30
2.4.1 Overview of Using View Menus ............................................................................ 2-30
2.4.2 Showing or Hiding Windows ................................................................................. 2-30
2.4.3 Showing Tools and Status .................................................................................... 2-31
2.5 Using Window Menus ...................................................................................................... 2-31
2.5.1 Cascading Windows.............................................................................................. 2-31
2.5.2 Tiling Windows Horizontally .................................................................................. 2-32
2.6 Using Help Menus............................................................................................................ 2-33
2.6.1 Using SoftX3000 Online Book............................................................................... 2-33
2.6.2 Using Help Topics ................................................................................................. 2-35
2.6.3 Calling Online Help of Dialog Box ......................................................................... 2-36
2.6.4 Calling Pop-Up Online Help .................................................................................. 2-36
2.6.5 Querying Version................................................................................................... 2-37
2.7 Using Management Tab .................................................................................................. 2-38
2.7.1 Overview of Management Tab .............................................................................. 2-38
2.7.2 Browsing Device Panel ......................................................................................... 2-39
2.7.3 Displaying Board Information ................................................................................ 2-41
2.7.4 Resetting Boards................................................................................................... 2-42
2.7.5 Swapping Boards .................................................................................................. 2-43
2.7.6 Querying CPU Usage............................................................................................ 2-43
2.7.7 Querying Memory Usage ...................................................................................... 2-44
2.7.8 Configuring Subscriber Data ................................................................................. 2-45
2.7.9 Maintaining Subscriber Data ................................................................................. 2-46
2.8 Using MML Navigation Tree ............................................................................................ 2-47
2.8.1 Overview of Using MML Navigation Tree ............................................................. 2-47
2.8.2 Using Common Maintenance Pane ...................................................................... 2-47
2.8.3 Querying History Commands ................................................................................ 2-49
2.8.4 Querying Online Help............................................................................................ 2-51
2.9 Using Monitor Tab ........................................................................................................... 2-51
2.9.1 Overview of Using Monitor Tab............................................................................. 2-51
2.9.2 Trace Management Tasks .................................................................................... 2-52
2.9.3 Maintenance Management Tasks ......................................................................... 2-53
2.10 Using the Toolbar .......................................................................................................... 2-53
ii
Chapter 3 Using Alarm Management System............................................................................. 3-1

3.1 Overview of Alarm Management System .......................................................................... 3-1
3.2 Classification of Alarms ..................................................................................................... 3-1
3.2.1 Classifying Alarms by Type..................................................................................... 3-1
3.2.2 Classifying Alarms by Level .................................................................................... 3-2
3.3 Generic Operations............................................................................................................ 3-3
3.3.1 Starting Alarm Management System ...................................................................... 3-3
3.3.2 Customizing Alarm Colors....................................................................................... 3-4
3.4 Browsing Alarms ................................................................................................................ 3-5
3.4.1 Browsing Fault Alarms ............................................................................................ 3-6
3.4.2 Browsing Event Alarms ........................................................................................... 3-7
3.4.3 Browsing History Alarms ......................................................................................... 3-8
3.4.4 Defining Alarm Filter Settings.................................................................................. 3-8
3.4.5 Filtering Alarms of Malicious Calls and Emergency Calls....................................... 3-9
3.5 Querying Alarms ................................................................................................................ 3-9
3.5.1 Notes on Querying Alarms ...................................................................................... 3-9
3.5.2 Operation Procedure............................................................................................... 3-9
3.6 Alarm Management Operations....................................................................................... 3-10
3.6.1 Deleting History Alarms......................................................................................... 3-10
3.6.2 Masking Alarms..................................................................................................... 3-11
3.6.3 Querying Alarm Configurations ............................................................................. 3-13
3.6.4 Defining Alarm Box Control Settings..................................................................... 3-14
3.6.5 Defining Alarm Statistics ....................................................................................... 3-14
3.6.6 Defining Alarm Box Screen Level ......................................................................... 3-16
3.6.7 Querying Alarm Box Screen Level ........................................................................ 3-17
3.6.8 Defining Sound Durations for Fault Alarms........................................................... 3-17
3.7 Using Other Alarm Related Options ................................................................................ 3-18
3.7.1 Overview of Other Alarm Related Options............................................................ 3-18
3.7.2 Using Shortcut Menu............................................................................................. 3-18
3.7.3 Querying Alarm Explanation Details ..................................................................... 3-19
3.7.4 Saving Alarm Content to File ................................................................................ 3-20
3.7.5 Recovering an Alarm............................................................................................. 3-20
3.7.6 Acknowledging an Alarm....................................................................................... 3-21
3.7.7 Clearing Recovery Alarms .................................................................................... 3-21
3.8 Defining Print Options...................................................................................................... 3-23
3.8.1 Overview of Using Print Options ........................................................................... 3-23
3.8.2 Defining Real Time Print Filter Settings ................................................................ 3-23
3.8.3 Printing Alarm Details in Real Time ...................................................................... 3-23
3.8.4 Flushing the Printer ............................................................................................... 3-23
Chapter 4 Using Performance Management System................................................................. 4-1

4.1 Overview of Performance Measurement ........................................................................... 4-1
4.2 Generic Operations............................................................................................................ 4-1
iii
4.2.1 Workflow of Performance Measurement................................................................. 4-1

4.2.2 Logging in to the Performance Management System............................................. 4-2
4.3 Cautions and Notes ........................................................................................................... 4-4
4.3.1 Maximum Number of Tasks .................................................................................... 4-4
4.3.2 User Authority.......................................................................................................... 4-4
4.3.3 Measurement entities.............................................................................................. 4-5
4.3.4 BAM time................................................................................................................. 4-5
4.4 Creating a Performance Measurement Task..................................................................... 4-6
4.4.1 General Workflow.................................................................................................... 4-6
4.4.2 Customizing an Entity ............................................................................................. 4-7
4.4.3 Launching the Task Creation Interface ................................................................. 4-10
4.4.4 Defining Task Attributes ........................................................................................ 4-11
4.4.5 Selecting a Measurement Unit .............................................................................. 4-12
4.4.6 Selecting Measurement Entities............................................................................ 4-12
4.4.7 Selecting a Measurement Object .......................................................................... 4-15
4.4.8 Setting Time Properties......................................................................................... 4-17
4.4.9 Defining Entity Thresholds .................................................................................... 4-19
4.4.10 Defining Sampling Parameters and Report Output Mode .................................. 4-21
4.4.11 Measurement Task State .................................................................................... 4-23
4.5 Querying or Dumping Results of a Measurement Task................................................... 4-24
4.5.1 Querying Results of a Measurement Task............................................................ 4-24
4.5.2 Dumping Results of a Measurement Task............................................................ 4-29
4.6 Querying the Details of a Measurement Task ................................................................. 4-29
4.7 Modifying Configuration Information of a Measurement Task......................................... 4-31
4.7.1 Overview of Modifying Task Configuration ........................................................... 4-31
4.7.2 Modifying Task Name ........................................................................................... 4-31
4.7.3 Modifying Task Output Mode ................................................................................ 4-31
4.7.4 Modifying Report Output Device ........................................................................... 4-32
4.7.5 Modifying Measurement Entities ........................................................................... 4-32
4.7.6 Modifying Time Information................................................................................... 4-32
4.7.7 Modifying Sampling Parameters ........................................................................... 4-32
4.7.8 Modifying Measurement Entity Thresholds........................................................... 4-33
4.7.9 Deleting Measurement Entity Thresholds ............................................................. 4-33
4.7.10 Adding Measurement Object............................................................................... 4-33
4.7.11 Deleting Measurement Object............................................................................. 4-33
4.8 Deleting a Performance Measurement Task ................................................................... 4-34
4.9 Activating and Deactivating a Measurement Task .......................................................... 4-34
4.9.1 Overview ............................................................................................................... 4-34
4.9.2 Deactivating a Task............................................................................................... 4-34
4.9.3 Activating a Task ................................................................................................... 4-34
4.10 Setting Clear Time of a Measurement Task .................................................................. 4-34
iv
Chapter 5 Trace and Maintenance ............................................................................................... 5-1

5.1 Trace and Maintenance Navigation Tree .......................................................................... 5-1
5.2 Interface Trace Tasks ........................................................................................................ 5-2
5.2.1 Overview of Interface Trace Tasks ......................................................................... 5-2
5.2.2 Tracing Using Ping.................................................................................................. 5-3
5.2.3 Tracing with Trace Route ........................................................................................ 5-4
5.2.4 Tracing MGCP Messages ....................................................................................... 5-7
5.2.5 Tracing H.248 Messages ...................................................................................... 5-10
5.2.6 Tracing MRC Messages........................................................................................ 5-13
5.2.7 Tracing SIP Messages .......................................................................................... 5-15
5.2.8 Tracing H.323 Messages ...................................................................................... 5-18
5.2.9 Tracing SCTP Messages ...................................................................................... 5-21
5.2.10 Tracing M2UA Messages.................................................................................... 5-24
5.2.11 Tracing M3UA Messages.................................................................................... 5-28
5.2.12 Tracing V5UA Messages .................................................................................... 5-31
5.2.13 Tracing IUA Messages........................................................................................ 5-34
5.2.14 Tracing MTP3 Messages .................................................................................... 5-37
5.2.15 Tracing BRA Messages ...................................................................................... 5-40
5.2.16 Tracing PRA Messages ...................................................................................... 5-43
5.2.17 Tracing V5 Messages ......................................................................................... 5-46
5.2.18 Tracing SCCP DPC Messages ........................................................................... 5-49
5.2.19 Tracing SCCP USER Messages......................................................................... 5-52
5.2.20 Tracing SCCP MTP Messages ........................................................................... 5-55
5.2.21 Tracing TCAP SCCP Messages ......................................................................... 5-58
5.2.22 Tracing TCAP USER Messages ......................................................................... 5-60
5.2.23 Tracing CSP Messages ...................................................................................... 5-63
5.2.24 Tracing Bill Messages ......................................................................................... 5-66
5.2.25 Tracing Circuit Messages.................................................................................... 5-69
5.2.26 Tracing Console Messages................................................................................. 5-72
5.2.27 Tracing STUN Messages .................................................................................... 5-74
5.3 Tracing User Signaling .................................................................................................... 5-76
5.3.1 Overview of User Trace Tasks.............................................................................. 5-76
5.3.2 Tracing Interface Signaling ................................................................................... 5-77
5.3.3 Tracing Call Connections ...................................................................................... 5-80
5.4 Using Maintenance Management Node .......................................................................... 5-84
5.4.1 Overview of Maintenance Management Node...................................................... 5-84
5.4.2 Querying CPU Usage............................................................................................ 5-85
5.4.3 Querying Memory Usage ...................................................................................... 5-86
5.4.4 Querying Memory Content .................................................................................... 5-88
5.4.5 Dumping Memory Content .................................................................................... 5-90
5.4.6 Querying MTP3 Link Status .................................................................................. 5-91
5.4.7 Querying No.7 Link Status .................................................................................... 5-92
v
5.4.8 Querying Media Gateway Status .......................................................................... 5-93

5.4.9 Querying H.323/SIP Terminal Status .................................................................... 5-94
5.4.10 Querying MGCP/H.248 Terminal Status............................................................. 5-95
5.4.11 Querying Module Communication Status ........................................................... 5-96
5.5 Exporting and Reviewing Trace Results.......................................................................... 5-97
5.5.1 Processing Trace Results ..................................................................................... 5-97
5.5.2 Using Trace Viewer............................................................................................... 5-98
5.6 Analyzing Signaling Trace Results ................................................................................ 5-101
5.6.1 Functions of Signaling Analysis .......................................................................... 5-101
5.6.2 Description of Signaling Analysis Interface......................................................... 5-102
5.6.3 Signaling Analysis Operations ............................................................................ 5-103
Chapter 6 Using GUI on BAM....................................................................................................... 6-1

6.1 Using BAM Application Software ....................................................................................... 6-1
6.1.1 Understanding Meanings of Service Processes ..................................................... 6-1
6.1.2 Starting BAM Application Software ......................................................................... 6-1
6.1.3 Using Service Management Process ...................................................................... 6-4
6.1.4 Configuring Server Startup Information .................................................................. 6-5
6.2 Using BAM Server Gateway Tool ...................................................................................... 6-6
6.2.1 Starting BAM Server Gateway Tool ........................................................................ 6-6
6.2.2 Creating Connection ............................................................................................... 6-7
6.2.3 Interrupting Connection........................................................................................... 6-9
6.3 Using Workstation Gateway Tool ...................................................................................... 6-9
6.3.1 Starting Workstation Gateway Tool....................................................................... 6-10
6.3.2 Creating Connection ............................................................................................. 6-10
6.3.3 Interrupting Connection......................................................................................... 6-12
6.4 Using BAM Service.......................................................................................................... 6-12
6.5 Using Smirror Process..................................................................................................... 6-15
6.6 Using Automatic Login Tool............................................................................................. 6-16
AppendixA Using Data Table Query Tools .................................................................................A-1

A.1 Using TableBrowse ...........................................................................................................A-1
A.1.1 Classifying Data on BAM ........................................................................................A-1
A.1.2 Starting TableBrowse .............................................................................................A-1
A.1.3 Using File Menus ....................................................................................................A-3
A.1.4 Using Tools Menus .................................................................................................A-3
A.1.5 Using View Menus ..................................................................................................A-7
A.1.6 Using Window Menus .............................................................................................A-7
A.1.7 Using Shortcut menus ............................................................................................A-8
A.1.8 Displaying Version ..................................................................................................A-9
A.1.9 Using Toolbar........................................................................................................A-10
A.1.10 Using Shortcut Keys ...........................................................................................A-10
A.2 Using ExTableBrowse .....................................................................................................A-11
A.2.1 Classifying Data on Host ......................................................................................A-11
vi
A.2.2 Using ExTableBrowse ..........................................................................................A-11

A.2.3 Using Toolbar........................................................................................................A-14
AppendixB Acronyms and Abbreviations ..................................................................................B-1
vii
U-SYS SoftX3000 SoftSwitch System Chapter 1 Introduction to GUI
Chapter 1 Introduction to GUI
1.1 Composition of GUI

The GUI mentioned throughout this manual refers to the graphic user interface
provided by BAM server software, client software, and emergency workstation
software.
The SoftX3000 Operation and Maintenance System works in client/server architecture.
The BAM server is the server side, which manages and maintains the SoftX3000. The
BAM server receives the maintenance and operation commands from a local or remote
end, sends them to a specific host or terminal, and waits to process the response
messages. The BAM server also stores and transfers the alarm and performance
measurement data, and provides multisided and remote maintenance to the SoftX3000.
BAM works as a database, and also a communication channel between the host and
the maintenance terminals.
The client software is installed on maintenance terminals. In addition, when you install
the BAM server software and emergency workstation software, the client software is
also installed.
The emergency workstation is the backup of the BAM server. It will function when the
BAM server fails.
The operations on the BAM server, maintenance terminals (also known as ordinary
workstation), and emergency workstation are the same. This chapter will elaborate on
the operations on maintenance terminals.
1.2 Description of GUI Components

1.2.1 Overview of GUI Components
As shown in Figure 1-1, the GUI of the SoftX3000 client comprises five components:
z Menu bar
z Toolbar
z Navigation tree
z Result window
z Command window
1-1
(1)
(2)
(5)
(3)
Command Window
(6)
(7)
(8)
(4)
(1) Menu bar (2) Toolbar (3) Navigation tree

(4) System result pane (5) Operation result pane (6) Command input pane
(7) History command box (8) Command input box
Figure 1-1 GUI of client
1.2.2 Menu Bar
The menu bar contains six menu items:

z System
z Service
z Authority
z View
z Window
z Help
Table 1-1 lists the functions of the menus.
Table 1-1 Functions of menus
Menu item Functions

Implements re-login, logout, modify password, office direction management,
System lock/unlock client, auto lock setting, output window setting, execute batch
commands, command timeout setting, and print functions.
Service Starts alarm management system and performance management system.
1-2
Menu item Functions

Authority Manages operator accounts, command groups, and workstation authorities.
Shows/hides toolbar and panes, customizes wizard window, and shows task
View
progress.
Window Sets the display mode.
Help Displays the online help and version of client software.
1.2.3 Toolbar
The toolbar contains icons of frequently used operations. These icons provide the
same functions as some of the menus. Table 1-2 lists the functions of the icons.
Table 1-2 Functions of icons in the toolbar
Icon Function
Re-login
Shows/hides navigation tree
Shows/hides output window.
Shows/hides command window
Shows/hides wizard window
Prints
Shows online help of the menu item
1.2.4 Navigation Tree
The navigation tree window contains four tabs:

z Management
z MML Commands
z Monitor
z Search
Table 1-3 shows the functions of the four tabs.
1-3
Table 1-3 Functions of tabs in the navigation tree
Tabs Functions
Provides subscriber management and device management functions.
Provides a tree-shape navigation of MML commands.
Provides signaling interface trace, user interface trace, and device

maintenance functions.
Provides the fuzzy search function. You can search MML commands by
entering the key words.
1.2.5 System Result Pane
The system result pane contains four tabs:

z Management
z Alarm
z Performance
z Debug
Table 1-4 shows the functions of the four tabs.
Table 1-4 Functions of tabs in the system result pane
Tabs Functions
Exports all information related to operation and maintenance and MML commands,
Management
including the results of scripts returned from the BAM.
Debug Exports information related to software debugging.

Performance Exports information related to performance measurement.
Alarm Exports information related to alarm management system.
1.2.6 Command Window
I. Overview of Command Window
The command windows consists of five partsoperation result pane, command input
pane, history command box, command input box, and shortcut icons.
II. Operation Result Pane
The operation result pane contains three tabs:

z Common Maintenance
z History Command
1-4
z Help Information
Table 1-5 shows the functions of the three tabs.
Table 1-5 Functions of tabs in the operation result pane
Tabs Functions
Common Maintenance Returns the execution results of commands from the BAM.
Records all executed commands in the current login, including unsuccessful
History Command
ones.
Display the online help for commands and nodes in the navigation tree.
Help Information Each help page includes the functions, notes, parameter description, and
examples.
III. Command Input Pane
The command input pane displays the command to be sent from the client to the BAM.
It has two functions:
z Displays the commands you enter in the command input box and the command
script by selecting the commands in the history command box.
z Provides an input interface for command scripts.
IV. History Command Box
The history command box displays the commands that have been successfully
executed in the current login. At maximum, the system can store 1000 history
commands. The default setting is 100 history commands.
You can modify the number of history commands. In addition, the history commands
are also displayed in the history command tab of the operation result pane. Refer to
section 2.8.3 querying history commands for details.
V. Command Input Box
The command input box is where you enter and run MML commands. You also have to
specify the parameters under the command input box.
There are two types of parameters. The red ones are mandatory parameters, and the
black ones are optional.
VI. Shortcut Icons
There are four icons right to the history command box and command input box.
Table 1-6 lists their functions.
1-5
Table 1-6 Functions of the icons
Shortcut icons Functions
Select the next history command. (Shortcut key <F8>)
Select the previous history command. (Shortcut key <F7>)
Display parameter input pane. (Shortcut key<Enter>)
Execute the command. (Shortcut key <F9>)
1.2.7 Shortcut Keys
The client software has some shortcut keys to help you use the client efficiently.
Table 1-7 lists the functions of the shortcut keys.
Table 1-7 Functions of shortcut keys
Shortcut keys Functions

F1 Display the online help of the current window.
F2 Show/hide the navigation tree.
F3 Show/hide the system result pane.
F4 Show/hide the command window.
F6 Clear all information in the common maintenance pane.
F7 Select the previous history command in the command window.
F8 Select the next history command in the command window.
F9 Display all command scripts in the command input pane.
1.2.8 GUI Applications on the BAM
The GUI applications on the BAM are distributed in two program folders: U-SYS
SoftX3000 Operation and Maintenance Center and Administrative Tools.
You can select [Start/Programs/U-SYS SoftX3000 Operation and Maintenance Center]
to use a specific function from the list as shown in Figure 1-2.
1-6
Figure 1-2 GUI applications on the BAM
There are two processes involved in the GUI applications on the BAM:
z BAM Service
z Smirror
You can start or stop them in the service window by selecting
[Start/Programs/Administrative Tools/Services].
Note:
All GUI applications are running on Windows 2000 Server and SQL Server 2000.
1.2.9 GUI Applications on the Client
The GUI applications on the client are included in U-SYS SoftX3000 Operation and
Maintenance Center.
You can select [Start/Programs/U-SYS SoftX3000 Operation and Maintenance Center]
to use a specific function from the list as shown in Figure 1-3.
Figure 1-3 GUI applications on the client
1-7
Note:
On the client, you cannot use the AutoLogin Tool to set the automatic login of the system.
The client does not have the following features comparing with the GUI applications on
the BAM:
z U-SYS SoftX3000 Server
z U-SYS SoftX3000 Server Gateway Tool
z Administrative Tools
1.3 Starting GUI

1.3.1 Starting MML Client
You can start the MML client from the windows [Start] menu. Proceed as follows:
1) Select [Start/Programs/U-SYS SoftX3000 Operation and Maintenance
Center/U-SYS SoftX3000 Operation and Maintenance System], and the [Operator
Login] dialog box is displayed as shown in Figure 1-4.
Figure 1-4 Logging in the system
2) Select the office in the drop-down list box "Office Name".

When you select another office, the IP address displayed in the Office IP Address will
also change accordingly. Here we select SZ-SOFTX3000.
3) Enter the account and password.
4) Click <OK>.
1-8
When the BAM to log in is an authorized one, its IP address will be displayed in the
status area at the bottom right corner, indicating that connection success, as shown in
Figure 1-5.
Figure 1-5 Connected to BAM
1.3.2 Starting Alarm Management System
You can start the alarm management system from the windows [Start] menu. Proceed
as follows:
Center/U-SYS SoftX3000 Operation and Maintenance System/U-SYS SoftX3000
Alarm Management System], and the [Operator Login] dialog box is displayed as
shown in Figure 1-6.
Figure 1-6 Starting the alarm management system from windows start menu

3) Enter the operator name and password.
4) Click <OK>. The system will start the alarm management system, as shown in
Figure 1-7.
1-9
Figure 1-7 Main interface of alarm management system
Note:
Here we only introduce how to start the alarm management system. For its usage, refer to chapter 3
Using Alarm Management System.
1.3.3 Starting Performance Management System
Select [Start/Programs/U-SYS SoftX3000 Operation and Maintenance Center/U-SYS

SoftX3000 Performance Management System].
Note:
Here we only introduce how to start the performance management system. For its usage, refer to chapter
4 Using Performance Management System.
1-10
U-SYS SoftX3000 SoftSwitch System Chapter 2 Using MML Client
Chapter 2 Using MML Client
2.1 Using System Menus

2.1.1 Logging In
Proceed as follows:
Center/U-SYS SoftX3000 Operation and Maintenance System], and the [Operator
Login] dialog box is displayed as shown in Figure 2-1.
Figure 2-1 Logging in the system

When you select another office, the IP address displayed in Office IP Address will
change accordingly. Here we select SZ-SOFTX3000.
3) Enter the account and password.
4) Click <OK>.
When the BAM to log in is an authorized one, its IP address will be displayed in the
status area at the bottom right corner, indicating that the connection succeeds, as
Figure 2-2 Connected to BAM
2.1.2 Re-logging In
If you want to log in with another account after logging in the system, proceed as
follows:
2-1
1) Select [System/Relogin] in the main interface of the client, and the confirmation
dialog box is displayed as shown in Figure 2-3.
Figure 2-3 Confirming to re-log in
2) Select <Yes>. The [Operator Login] dialog box will appear.

You can now log in with another account.
2.1.3 Logging Out
To log out without exiting the client, proceed as follows:

1) Select [System/Logout] in the main interface of the client, and the confirmation
Figure 2-4 Confirming to log out
2) Click <Yes>. Now Disconnected will be displayed in the status area, as shown in
Figure 2-5.
Figure 2-5 Disconnected from BAM
2.1.4 Changing Password
Proceed as follows to change the password of the current account:

1) Select [System/Change Password] in the main interface of the client, and the
confirmation dialog box is displayed as shown in Figure 2-6.
2-2
Figure 2-6 [Change password] dialog box
2) Enter the three fields in Figure 2-6.

3) Click <OK>.
Note:
z If you forget your password, contact the administrator to get a new one.
z Change your password regularly. The password should be at least six digits.
2.1.5 Managing Office Information
I. Overview of Managing Office Information
If you have not added the IP address of any BAM when installing the client software, the
information displayed in Figure 2-1 will be blank. You have to add the IP address of a
valid BAM before logging in to it.
II. Setting Office Information
Proceed as follows:
1) Select the <Office> button to the right of Office Name in Figure 2-1, and the
[Manage Office Information] dialog box is displayed as shown in Figure 2-7.
2-3
Figure 2-7 Setting office information
Note:
z Alternatively, you can set the office information by selecting [System/Office Management] in the main
window of the client. The same dialog box will appear as shown in Figure 2-7.
z If the client is installed on a BAM, the system has automatically assigned the IP address 127.0.0.1 to
the client.
2) Enter the office name, for instance, SZ-SOFFX3000.

3) Enter the public IP address of the BAM. Here, take 10.70.33.62 for an example.
4) Click <Set>, and the office information setting is complete as shown in Figure 2-8.
2-4
Figure 2-8 Setting office information complete
To add another office, enter the office name and IP address, and click <Set>. When you
have completed adding offices, click <Close>.
III. Removing Office Information
Proceed as follows:
1) Select the office to be deleted in the list of the [Manage Office Information] dialog
box, as shown Figure 2-9.
2) Click <Delete>, and the confirmation dialog box appears as shown in Figure 2-10.
3) Click <Yes>, and the selected office is deleted.
2-5
Figure 2-9 Selecting the office to be deleted
Figure 2-10 Confirming to delete the office
IV. Modifying Office Information
Proceed as follows:
1) Select the office to be modified in the [Manage Office Information] dialog box.
2) Change the IP address.
3) Click <Set>, and the information of the office is changed.
Note:
You can only change the IP address of the office in the above method. To change the office name, you
have to delete it and add another one.
2-6
2.1.6 Setting Output Configurations
I. Overview of Setting Output Configuration
The output information, including the maintenance, alarm, performance measurement,

and software commissioning information, are helpful in locating faults during
deployment, upgrade, and daily maintenance. However, the browsing space in the
output pane is limited. It can be difficult to read the output information, especially when
there is huge output.
To solve the problem, you can save the output information over a certain period to a text
file in the local hard disk for future reference.
II. Operation Procedure
Proceed as follows to save the output information:

1) Select [System/Output Window Setting] in the main interface of the client, and
the [Output Configuration] dialog box is displayed as shown in Figure 2-11.
2) You can select the four panes to define the output settings of maintenance
information, alarm information, performance measurement information, and
software commissioning information respectively.
Figure 2-11 Setting output configuration
3) Take maintenance information for an instance. Select Maintain Output pane.

4) In the Output to file field, select the button right to Output, and the [Save
Output File As] dialog box is displayed as shown in Figure 2-12.
2-7
5) Specify the path and name of the output file.
Figure 2-12 Saving the output file
Note:
The default path is D:\SoftX3000\Output, and the default file type is text format *.txt.
6) Click <Save>, and the system returns to the [Output Configuration] dialog box.
The Output column displays the path and name of the output file. The check box to the
right of the button indicates that the maintenance information is ready to be save to
a specific file, as shown in Figure 2-13.
2-8
Figure 2-13 Setting output configuration
Note:
In the [Output to file] field, the Auto save option defines the maximum capacity of output files (unlimited
by default), and the Time output to file defines the time segment during which the system exports the
information to files.
If you do not want to print the maintenance information immediately, deselect the check
box [To printer] in the [Printer] field, and then click <OK>. The system starts to store the
maintenance information to a designated file.
III. Exporting Information to File
To stop exporting the maintenance information to a file, proceed as follows:

Solution 1
1) Select [System/Output Window Setting] on the client. The [Output Configuration]
dialog box appears.
2) Clear the check box to the right of
3) Click <OK>.
Solution 2
Close the client software directly, that is, select [System/Exit] on the client.
2-9
2.1.7 Setting Command Timeout Duration
You need to adjust the command timeout duration according to the communication
status between the client and the Bam. When there are frequent "no responses" from
the BAM, proceed as follows:
1) Select [System/Command Timeout Setting] in the main interface of the client,
and the [Command Time Out] dialog box is displayed as shown in Figure 2-14.
Figure 2-14 Setting command timeout duration
2) When you finish setting, click <OK>.
Table 2-1 Description of command timeout parameters
Command
MML Command Time Out Monitor Command Time Out
description
Meaning The maximum duration from a command is sent to the BAM to the BAM responses
Types Text Binary
Location MML navigation tree Monitor navigation tree
Unit Second Second
Range of value 20600 10100
Default value 80 20
If no response is received from the BAM, the client will render the operation failure.
2.1.8 Saving Input Commands
You can save the MML commands executed at the client to a text file for future
reference. When you repeat the operation, or carry a batch of commands similar to the
saved input ones, you can directly use the text file. During daily maintenance, you have
to frequently query the status of the equipment and the network, CPU usage, signaling
link status, and gateway registration status.
2-10
In this case, you can use the saved input commands to improve the efficiency.
Proceed as follows to save the input commands:
1) Select [System/Save Input Commands] (or press shortcut key <Ctrl+S>), and the
[Save input commands to file] dialog box is displayed as shown in Figure 2-15.
Figure 2-15 Saving the input commands to file
Note:
The default path of output file is D:\SoftX3000\Output. The default file type is text. The naming convention
for the output file is CMD-YYMMDDHHMM, in which YY stands for two digits of year, MM stands for month,
DD stands for date, HH stands for hour, and MM stands for minute.
2) Specify the path and name of the output file in Figure 2-15.
3) When you finish setting, click <Save>.
Now the option Save Input Commands will be changed to Stop Save Input
Commands, indicating that the system has started saving the MML commands to file.
To stop saving input commands to file, select [System/Stop Save input Commands] or
press <Ctrl+S>. The option Stop Save Input Commands will be changed back to
Save Input Commands, indicating that the system has finished saving the MML
commands to file.
2.1.9 Executing Commands in Batch
I. Overview of Executing Commands in Batch
Executing commands in batch is to improve the efficiency of deployment, maintenance

and upgrade, during which you have to execute a large amount of commands and
2-11
which usually takes a lot of time. SoftX3000 provides a function which enables you to
run a command script file instead of executing all the commands one by one.
There are two types of batch executionimmediate execution and time execution.
II. Immediately Executing Commands in Batch
It is usually used during deployment. Proceed as follows:

1) Prepare the command script file.
The script file can be made for data configuration or daily maintenance. The name can
be R2_interface.txt for instance.
2) Log in the SoftX3000 client.
3) Select [System/Execute Batch Commands] (or press <Ctrl+E>) in the main
interface of the client, and the [Execute Batch Commands] dialog box is displayed
as shown in Figure 2-16.
4) Select <Browse> next to Specify batch file. Specify the storing path for the
script file R2_interface.txt, as shown in Figure 2-16.
Figure 2-16 Executing commands in batch
5) In the [Set execution manner] field, select Immediate execution.
2-12
Note:
In the Immediate execution mode, only one script file can be executed at a time. This mode is usually
used in data configuration during deployment.
6) Click <OK>. The system will check the grammar of the script file. If no error is
found, the execution dialog box will be displayed, as shown in Figure 2-17.
Figure 2-17 Results of immediate executing commands in batch
7) Select the Execute type. Here we select Execute all.

8) Click <Go>.
Here are the description of the modes:
z Execute all: All commands in the script file will be executed.
z Execute Step by Step: You have to click <Go> after the system executed each
line.
z Execute with Break Point: The system executes the command lines till the first
break point. If you wish to continue execution, click <Go> and the system will
continue execution till the next break point. Refer to the note after Figure 2-20 on
how to set a break point.
z Execute range: All commands in the range will be executed. You have to specify
the range if you select this mode.
2-13
9) The error prompt appears as shown in Figure 2-18. The cursor stops in the line of
error. Click <No>. Modify the error in the script.
Figure 2-18 Error prompt when executing the script
10) Correct the error line in Figure 2-17.

This windows is similar to that of the Wordpad. It has the same shortcut keys as the
wordpad, such as <Ctrl+F> for Find, <Ctrl+H> for Replace, and <Ctrl+S> for Save.
If you click <Yes> in Figure 2-18, the system skips the error line and continues the
execution.
11) Select <Save>.
12) Select Execute Step by Step in [Execute type].
13) Click <Go>, and the system will continue executing the script.
When the system completes the execution, the Execute complete prompt will be
displayed. In the execution result area, you will see the details of the command lines
successfully and unsuccessfully executed. It also includes the line and row number of
the current error line, as shown in Figure 2-19.
Figure 2-19 Execution result area
Before execution, you can specify the Sending commands interval(s) (in seconds).
In addition, you can specify the path to store the details of the Failed and unexecuted
commands. Figure 2-20 lists the content of such a file.
2-14
Figure 2-20 An list of failed and unexecuted commands
To set break point in the script file:

14) Select the line to set the break point.
15) Click <Set breakpoint>. There will be a brown circle in front of the line, as shown in
Figure 2-21.
To clear the break point, repeat the above operation.
2-15
Figure 2-21 Setting a break point
Note:
The lines with // are remark lines, and will be ignored and skipped during execution.
III. Executing Commands in Batch By Time
It is frequently applied in daily maintenance. Proceed as follows:

1) Prepare the command script file.
The script file can be made for data configuration or daily maintenance. The name can
be R2_interface.txt for instance.
2) Log in the SoftX3000 client.
3) Select [System/Execute Batch Commands] (or press <Ctrl+E>) in the main
interface of the client, and the [Execute Batch Commands] dialog box is displayed
4) Select <Browse> next to Specify batch file. Specify the storing path for the
script file R2_interface.txt, as shown in Figure 2-22.
2-16
Figure 2-22 Executing commands in batch by time
5) In the Set execution manner field, select Time execution.

The choice means that the commands in the script file will be executed at a constant
interval.
Note:
You can also specify multiple script files in this mode, which is frequently applied in the query operation in
daily maintenance. The default execution interval between two commands is 50 ms.
6) Specify the time and date for the first script file in Time execution. Click <Add>,
and the file is added as shown in Figure 2-23.
7) You can repeat the above steps to add more files, as shown in Figure 2-23.
2-17
Figure 2-23 Executing commands in batch by time
8) Click <OK> to finish the settings.

The system will automatically execute R2_interface.txt at 18:18 on Nov 8, 2004, and
execute add vsb.txt at 23:50 on the same day.
Note:
When you select multiple script files in this mode, set the interval long enough so that the system can
complete executing the first file before starting with the next one.
2.1.10 Stopping Executing Commands in Batch
When the system is executing the commands in batch, you can stop the following two
types of modes:
z Immediately executing commands in batch
z Executing commands in batch by time
To stop the first mode, directly click <Stop> in Figure 2-17.
2-18
In the second mode, the system will automatically start executing the script files in
sequence. The [Execute Batch Commands] item on the [System] menu becomes
invalid, but [Stop Execute Batch Commands] becomes valid. You can click this menu to
stop executing commands in batch.
2.1.11 Setting Printing Options
You might frequently need to print out the information displayed on the BAM. To do so,
proceed as follows:
1) Select [System/Print Setup], and the print setup dialog box is displayed as shown
in Figure 2-24.
Figure 2-24 Setting printing options
2) Set the options according to your requirement.

3) Click <OK>.
2.1.12 Printing in Real Time
To print in real time, select [System/Realtime Print].

The system will not immediately print the real time alarm report until there is enough
content to fill up a page.
If you want to print information in real time, remember to select [System/Flush Printer]
after the system generates real time alarms.
2.1.13 Flushing Printer
To flush the printer, select [System/Flush Printer].
2-19
If the buffer is empty, a blank page will be printed.

The printer will print all content in the buffer until it is empty.
2.1.14 Locking Client
You can lock the client to avoid access by unauthorized user when you are absent.
Proceed as follows:
1) Select [System/Lock System], the system is locked, and a prompt appears as
Figure 2-25 Enter your password after locking the client
2) Enter the correct password.

3) Click <OK>, and you returns to the client interface.
2.1.15 Automatically Locking Client
To avoid unauthorized user using the client when you are absent, you can also set a
timeout duration after which the system will automatically lock the client. Proceed as
follows:
1) Select [System/Auto Lock Setting], and the [Configure Auto Lock Setting] dialog
box is displayed as shown in Figure 2-26.
2-20
Figure 2-26 Configuring automatic locking settings
2) Select [Enable Lock].

3) Specify the time after which the system locks the client. The valid range is 1360.
4) Click <OK>.
For example, in Figure 2-26 the system will lock the client in 30 minutes.
2.1.16 Exiting
Select [System/Exit] to exit the client.
2.2 Using Service Menus

There are two ways to start the alarm management system:

Center/U-SYS SoftX3000 Alarm Management System].
2) After logging on to the client, select [Service/Alarm Management System], as
Figure 2-27 Starting the alarm management system from the client
Note:
Here we only introduce how to start the alarm management system. For its usage, refer to chapter 3
Using Alarm Management System.
2-21
2.2.2 Starting Performance Management System
There are two ways to start the performance management system:

Center/U-SYS SoftX3000 Performance Management System].
2) After logging on to the client, select [Service/Performance Management System].
Note:
Here we only introduce how to start the performance management system. For its usage, refer to chapter
4 Using Performance Management System.
2.3 Using Authority Menus

2.3.1 Classification Operation Authorities
The SoftX3000 client assigns to users different levels of authoritiesoperator,

workstation, and command group.
I. Operator
Each operator must have a valid account to log in the SoftX3000 client. The system has
two default accountsSoftX300 and Guest. The SoftX3000 account has the highest
authorities, and the Guest account has the lowest authorities. You can add new
operator accounts according to the requirements. To ensure security to the system,
each account must have an complicated enough password.
Note:
The system administrator accounts, including the SoftX3000 account, are configured when you install
the BAM software.
II. Operator Domain and Operator Group
You can use the following three commands to set operator domain and operator group:
Command Usage
ADD DOMAIN Define the domain in which the operator has certain level of authorities
Define the level of authorities in the operator domain, for instance, managing
ADD DOMAUTH
the telephone number in a certain range.
2-22
Command Usage
ADD OPGRP Define the available operator group of the operator.
III. Workstation
A workstation is the computer that you log in to operate on. The BAM is also a
workstation. You can only operate on an authorized workstation to maintain the
SoftX3000. The intersection of the authorities of the workstation and the current login
account is the actual authority you have.
IV. Command Group
You can also assign authorities to a workstation by command groups. This mode
increases the efficiency of assigning authorities. You don't have to assign the
authorities of commands one by one.
The system has already defined some command groups:
z Subscriber management
z Ticket query
z GUEST
z SYS
You can modify and use all command groups except SYS. There are some empty
command groups for you to customize.
Note:
You can only use the system administrator account to manage the authorities.
2.3.2 Adding Operator Account
Proceed as follows:
1) Select [Authority/Accounts/Add] in the main client interface, and the [Accounts
Management] dialog box is displayed as shown in Figure 2-28.
2-23
Figure 2-28 Adding an operator account
2) Enter or select the authority attributes.

3) Click <OK>. You have completed adding an operator account.
I. Description of Parameters
The account is case-sensitive. You cannot leave it blank or create an existing account.
The start time and end time specifies the duration in which the operator has authority.
The system administrator and GUEST operator are not limited by these two parameters.
For common operators, if these two parameters are not defined, there is no duration
limitation on authority.
The system administrator (using the G_SYS command group) enjoys the highest
authorities, and can use all commands. The guest operator can only use the
commands in the G_GUEST command group. The authorities of common operators
are defined by operator group and operator domain.
Note:
You can also use the command ADD OP to add an operator account in the command window. After
adding an account, you have to use SET OPTM to set the operation duration of the account.
2.3.3 Modifying Operator Account
Proceed as follows:
1) Select [Authority/Accounts/Modify] in the main interface of the client, and the
[Please Select Operator] dialog box appears, as shown in Figure 2-29.
2-24
Figure 2-29 Selecting an account to modify
2) Select the account to be modified.

3) Click <OK>, and the [Accounts Management] dialog box appears as shown in
Figure 2-30.
Figure 2-30 Modifying an operator account
4) Modify the password, start time, end time, operator group, and operator domain.
5) Click <OK>, and the modification is completed.
Note:
In Figure 2-30, you cannot modify the operator name and operator description. You can also modify the
start time and end time using the command SET OPTM.
2-25
2.3.4 Deleting Operator Account
Proceed as follows:
1) Select [Authority/Accounts/Delete] in the main interface of the client, and the
[Please Select Operator] dialog box appears, as shown in Figure 2-29.
2) Select the account to be deleted.
3) Click <Delete>, and a confirmation dialog box appears as shown in Figure 2-31.
Figure 2-31 Confirming whether to delete the operator account
4) Click <Yes>, and the account is deleted.
Note:
z You cannot delete the system administrator account SoftX3000" or Guest.
z You can also use the command RMV OP to delete an operator account in the command window.
2.3.5 Adding Workstation
I. Operation Procedure
Proceed as follows:
1) Select [Authority/Workstation/Add] in the main client interface, and the [WS
Management] dialog box is displayed as shown in Figure 2-32.
2-26
Figure 2-32 Adding a workstation
2) Enter the workstation name and IP address.

3) Set the authority for the workstation.
4) Click <OK>.
If the operation is successful, the system will prompt whether to add another
workstation. Otherwise, the system will prompt that the workstation already exists, or
the IP address is incorrect.
II. Notes on Adding a Workstation
z The workstation name is not case-sensitive. You cannot leave it blank or use the
name of an existing workstation.
z The IP address must be a valid one. Like the workstation name, you cannot use
the IP address of an existing workstation.
z If you do not set the workstation authority, by default it will have the lowest
authority G_GUEST.
z To ensure that a legal operator can log in the SoftX3000 client, you have to
allocate an account and password by selecting [Authority/Accounts/Add].
z You can also use the command ADD WS to add a workstation in the command
window.
2.3.6 Modifying Workstation
Proceed as follows:
1) Select [Authority/ Workstation /Modify] in the main interface of the client, and the
[Please Select WS] dialog box appears, as shown in Figure 2-33.
2-27
Figure 2-33 Selecting a workstation to be modified
2) Select the workstation to be modified.

3) Click <OK>, and the [WS Management] dialog box appears as shown in Figure
2-34.
Figure 2-34 Modifying a workstation
4) Modify the name, IP address, and authority of the workstation.

5) Click <OK>, and the modification is completed.
2.3.7 Deleting Workstation
Proceed as follows:
1) Select [Authority/ Workstation /Delete] in the main interface of the client, and the
[Please Select WS] dialog box appears, as shown in Figure 2-33.
2) Select the workstation to be deleted.
3) Click <Delete>, and a confirmation dialog box appears as shown in Figure 2-35.
2-28
Figure 2-35 Confirming whether to delete the workstation
4) Click <Yes>, and the workstation is deleted.
I. Notes on Deleting a Workstation
You can only delete a workstation when you log in as a system administrator. After
deletion, all authorities granted to the workstation are also deleted.
z You cannot delete the "super workstation of BAM.
z If the workstation to be deleted is still in use, you have to reduce the authority of
the current login operator to G_GUEST before you can delete the workstation.
z You can also use the command RMV WS to delete a workstation in the command
window.
2.3.8 Setting Command Group
You can modify the commands in a certain command group only when you log in to the
client as system administrator. Proceed as follows:
1) Select [Authority/Command Group/Add] in the main client interface, and the
[Command Group Authority Setting] dialog box is displayed as shown in Figure
2-36.
Figure 2-36 Modifying a command group
2) Selecting a command group to be modified.
2-29
3) Select the commands in the command group according to your requirement.

4) Click <OK>, and you have completed the customization of the command group.
Note:
z You can also use the command ADD CCG to modify a command group in the command window.
z To remove and query a command group, use the command RMV CCG and LST CCG in the command
window.
2.4 Using View Menus

2.4.1 Overview of Using View Menus
The [View] menus help you show and hide the following items:
z Navigation tree
z Output window
z Command window
z Alarm tab
z Performance tab
z Debug tab
z Tool bar
z Status bar
2.4.2 Showing or Hiding Windows
Proceed as follows:
1) In the [U-SYS SoftX3000 Operation and Maintenance System] window, select
[View/ window name (for example, Navigation Tree or Command Window)].
2) The selected window is displayed. Click this menu item again. The window is
hidden.
Note:
z By default, only the [Management] tab is displayed.
z After selecting Alarm, Performance, and Debug, the alarm tab, performance tab, and debug tab
are displayed in the output pane.
2-30
2.4.3 Showing Tools and Status
The [View] menus help you show or hide the toolbar and the status bar. Proceed as
follows:
1) In the [U-SYS SoftX3000 Operation and Maintenance System] window, click
[Toolbar] or [Status bar] on the [View] menu.
2) The selected toolbar or status bar is displayed. Click this menu item again. The
toolbar or status bar is hidden.
Note:
z You can implement re-login, show/hide navigation tree, show/hide output window, show/hide
command window, print in real time, and view online help information by selecting the corresponding
item on the toolbar.
z The status bar displays the workstation state. Connected means online. Disconnected means
offline.
2.5 Using Window Menus

The menus help you cascade and tile multiple windows, arrange icons, and close all
windows.
2.5.1 Cascading Windows
To cascade multiple windows, select [Windows/Cascade] in the main interface of the

client, as shown in Figure 2-37.
2-31
Figure 2-37 Cascading windows
2.5.2 Tiling Windows Horizontally
To tile windows horizontally, select [Windows/Tile Horizontally] in the main interface of

the client, as shown in Figure 2-38.
2-32
Figure 2-38 Tiling windows horizontally
2.6 Using Help Menus

You can obtain help information through the [Help] menu or the online help window.
2.6.1 Using SoftX3000 Online Book
The online book is a comprehensive online help of all components in the SoftX3000. To
use it, proceed as follows:
Center/U-SYS SoftX3000 Online Book] on the BAM or client, and the online book
is displayed as shown in Figure 2-39.
2-33
Figure 2-39 [U-SYS SoftX3000 Online Book]
The left pane contains the following tabs:

Contents: It lists all online help items in the structure of the SoftX3000 operation and
maintenance system.
Index: It provides index-based search function. All online help items are arranged in
alphabetic order.
Search: It provides fuzzy-match search function. You can define search conditions by
logical relationship.
Favorite: You can add bookmarks here to fast locate the frequently-used help
information.
2) Select the search mode as needed for online help.
2-34
2.6.2 Using Help Topics
Proceed as follows:
1) In the [U-SYS SoftX3000 Operation and Maintenance System] window, select
[Help/Help Topics] or press the key <F1>. The client online help window is
displayed as shown in Figure 2-40.
Figure 2-40 Starting online help through menu or toolbar
The left pane contains the following tabs:

Contents: It lists all online help items in the structure of the SoftX3000 operation and
maintenance system.
Index: It provides index-based search function. All online help items are arranged in
alphabetic order.
Search: It provides fuzzy-match search function. You can define search conditions by
logical relationship.
Favorite: You can add bookmarks here to fast locate the frequently-used help
information.
2) Select the search mode as needed for online help.
2-35
Note:
You can also open the online help window as shown in Figure 2-40 by clicking on the toolbar. The
online help windows started through the menu or toolbar in the other interfaces all support query of
operation-related help information.
2.6.3 Calling Online Help of Dialog Box
To see the online help of a certain dialog box, press <F1>. The online help of the dialog
box will be displayed as shown in Figure 2-41.
Figure 2-41 Calling online help of dialog box
2.6.4 Calling Pop-Up Online Help
When you stop your cursor on a button or parameter input field, a square box will be
displayed, indicating the function of the button, and the range of value and default value
of the parameter. Figure 2-42 shows the details.
2-36
Figure 2-42 Calling pop-up online help
2.6.5 Querying Version
To query version of the client software:

Select [Help/About], and the version information is displayed as shown in Figure 2-43.
Figure 2-43 Querying version
2-37
2.7 Using Management Tab

2.7.1 Overview of Management Tab
The system management operations comprises two sectionsdevice management

and subscriber management. In the navigation tree of the client interface, click the
[Management] pane, and the navigation tree is changed as shown in Figure 2-44.
Figure 2-44 Working on system management pane
The device management node includes the following sub-nodes:

z Browsing device panel
z Displaying board information
z Resetting boards
z Swapping boards
z Querying CPU usage
z Querying memory usage
The subscriber management node is composed of two partssubscriber
configurations and common operations.
Subscriber configurations include:
z Number segment configuration
z Centrex configuration
z Voice subscriber configuration
z BRA subscriber configuration
z V5 subscriber configuration
z Multimedia subscriber configuration
Common operations include:
z Voice subscriber common operations
z V5 subscriber common operations
2-38
z Multimedia subscriber common operations
2.7.2 Browsing Device Panel
The device panel displays the board configuration in all slots of the current frame.
Proceed as follows to browse the device panel:
1) Double click [Device Management] node in the management pane, and the device
management window is displayed as shown in Figure 2-45.
Figure 2-45 Device management window
2) Double click the shelf 0 to be queried, and a system panel diagram appears as
shown in Figure 2-46, displaying the configuration of boards in the frame.
2-39
Figure 2-46 Device panel
The color section in the middle of Figure 2-46 is board view. Here is an description of
different colors:
z Red means that the board has been configured with data, but is not working
properly.
z Green means that it is a normal active board.
z Blue means that it is a normal standby board.
z The symbol indicates that the board has a pinch board (or sub-board). There
are two colors of the symbol: green means the pinch board is working normally,
and gray means the pinch board is faulty.
The black bar at the bottom displays the status of boards. The information of faulty
boards is also displayed, including slot number and board type (front board or back
board).
Note:
When the board indicator is green or blue, the board is normal, but the service might not be normal yet.
2-40
The [Single] pane on the right of Figure 2-46 can display and help you add, remove,
and modify hardware configurations.
2.7.3 Displaying Board Information
Proceed as follows:
1) Right click the board to be queried in the device panel, and a shortcut menu will be
Figure 2-47 Shortcut menus
Note:
z For the alarm board ALUI, you can only query and reset it.
z You can only swap the active board.
z You cannot see any shortcut menus when you right click the power board UPWR.
2) In Figure 2-47, select [Display Board] in the shortcut menu, and a dialog box will
be displayed as shown in Figure 2-48. The dialog box specifies the name, status,
physical memory, available memory, CPU usage, and many other information of
the board.
2-41
Figure 2-48 Displaying board information
2.7.4 Resetting Boards
I. Overview of Resetting Board
You have to reset a board when there is logical disorder during operation of the board,
and that the board cannot work normally and has to be restored.
The reset operation is to send a hot-reboot command from the BAM. When all boards in
a frame are faulty, or when the system crashes and you cannot reset the board by
selecting the [Reset Board] option on the device panel, you have to unplug and plug the
active and standby SMUIs to reset the frame.
II. Cautions of Resetting Board
You can only reset a board when it is faulty, or when the system crashes, or during
major software upgrade.
The reset operation will affect the services provided by the board. Be cautious in your
operation.
Never reset a board frequently.
Do not reset a board when it is normal.
To reset a board, reset the standby one first. Wait till it is running normally before you
can reset the active one.
III. Operation Procedure
Proceed as follows:
2-42
1) Right click the board to be reset in the device panel, and a shortcut menu will be
2) Select the [Reset Board] option, and a confirmation dialog box will be displayed as
Figure 2-49 Confirming to reset the board
3) Click <Yes>. The system starts to reset the board.
2.7.5 Swapping Boards
The swap operation is to exchange the role of an active board and its standby peer.
Generally, you can swap an active board in the basic frame when its CPU usage or
memory usage has been near 100% for a long time.
Proceed as follows:
1) Right click the board to be swapped in the device panel, and a shortcut menu will
be displayed as shown in Figure 2-47.
2) Select [Swap Board], and a confirmation dialog box will appear.
3) Click <Yes>. The system starts to swap the board.
Caution:
Do not swap a normal board. Be cautious when swapping a board.
2.7.6 Querying CPU Usage
Proceed as follows:
2) Select [Display CPU Usage], and the system will display the CPU usage of the
board in real time, as shown in Figure 2-50.
2-43
Figure 2-50 Displaying the CPU usage of a board
2.7.7 Querying Memory Usage
Proceed as follows:
2) Select [Display Memory Usage], and the system will display the memory usage of
the board in real time, as shown in Figure 2-51.
2-44
Figure 2-51 Displaying the memory usage of a board
2.7.8 Configuring Subscriber Data
In addition to configuring subscriber data in the command window, you can also
configure subscriber data. Here, we take the configuration of voice subscriber as an
example. Proceed as follows:
In Figure 2-44, double click the Voice Subscriber Configuration node, and the
configuration window is displayed as shown in Figure 2-52.
2-45
Figure 2-52 Configuring subscriber data
Table 2-2 Description of buttons in subscriber data configuration interface
Button Function
Filters the date to be displayed.
Cancels the filter operation.
Refreshes the display
Customizes the filter mode
The [Single] tab provides similar functions as the one on the device management
interface. You can add, remove, modify, and query subscriber data in the tab.
2-46
2.7.9 Maintaining Subscriber Data
In addition to maintaining subscriber data in the command window, you can also do it in
the GUI. Here, we take the maintenance of voice subscriber as an example. Proceed
as follows:
In Figure 2-44, double click the Voice Subscriber Common Operations node, and the
configuration window is displayed. Execute the command List MGCP MGW, and the
results are shown in Figure 2-53.
Figure 2-53 Common operation and maintenance interface
2.8 Using MML Navigation Tree

2.8.1 Overview of Using MML Navigation Tree
In the GUI, you can run commands to execute commands and query online help.
Double click the MML navigation tree, you will see three tabs containing the results and
output of operationsCommon Maintenance, History Command, and Help Information.
Table 2-3 lists the functions of the tabs.
Table 2-3 Functions of tabs in the operation result pane
Tabs Functions
Common Maintenance Returns the execution results of commands from the BAM.
Records all executed commands in the current login, including unsuccessful
History Command
ones.
Displays the online help for commands and nodes in the navigation tree.
Help Information Each help page includes the functions, notes, parameter description, and
examples.
2-47
2.8.2 Using Common Maintenance Pane
For instance, to query an office direction, proceed as follows:

1) Enter ADD MMTE in the command input box.
2) Press <Enter> or click , the parameters to be specified are also displayed, as

Figure 2-54 Specifying parameters
There are two types of parameters:

z The red ones are compulsory, which must be specified.
z The black ones are optional, which can be specified or omitted.
To know the range of value of a specific parameter, stop the cursor at the input box and
the system will display a pop-up help, indicating the function of the button, and the
range of value and default value of the parameter. Figure 2-54 shows the details.
3) Specify the parameters according to your requirement.
4) Click the button or press <F9>, and the system starts executing the command.
The [Common Maintenance] tab displays the results as shown in Figure 2-55.
2-48
Figure 2-55 Using the [Common Maintenance] tab
2.8.3 Querying History Commands
The [History Command] tab records all executed commands in the current login,
including unsuccessful ones.
At maximum, the system can store 1000 history commands. The default setting is 100
history commands. You can modify the number of history commands to be stored:
1) Click the [Common Maintenance] tab.
2) Right click in the [Common Maintenance] tab, and a shortcut menu is displayed as
2-49
Figure 2-56 Shortcut menu in the [Common Maintenance] tab
3) Select [Setting], and the [MML Client Setting] dialog box is displayed as shown in
Figure 2-57.
Figure 2-57 Setting client information
4) Set the maximum number of history commands.

5) Click <OK>.
Note:
z When the number of executed commands exceeds the maximum number of history commands, the
oldest records will be replaced by the new ones.
z Press <F7> to select the previous command.
z Press <F8> to select the next command.
2-50
2.8.4 Querying Online Help
After you enter a command in the command input box, if you want to see the online help
of the command, click the [Help Information] tab or press <F1>. Figure 2-58 shows the
details.
Figure 2-58 Querying online help of a command
An online help page contains four nodes:

z Function
z Note
z Parameter ID
z Example
By default, only the contents of the Function node are displayed. To view the contents
of other node, just click them.
2.9 Using Monitor Tab

2.9.1 Overview of Using Monitor Tab
The monitor tab consists of two partstrace management and maintenance

management. In the navigation tree of the client interface, click the [Monitor] pane, and
the navigation tree is changed as shown in Figure 2-59.
2-51
Figure 2-59 Using the trace and maintenance navigation tree
This chapter introduces the basic concepts in the Monitor tab. Refer to chapter 5 Trace
and Maintenance.
2.9.2 Trace Management Tasks
Trace management is the real-time tracing and observation of the connection of the
user circuit, trunk circuit, and interface signaling link in the following aspects:
z Connection procedure
z State migration
z Resource usage
z Call party release procedure
z Code sending
z Control signaling flow
You can save the trace results for future reference. You can also print the trace results.
The trace management feature is very helpful in the daily maintenance of the
SoftX3000. It can help you quickly find the cause of failure and find a solution to the
problem. It also provides you with detailed information of signaling and message
coordination.
The trace management node includes two sub nodesInterface Trace Task and User
Trace Task.
2-52
2.9.3 Maintenance Management Tasks
The maintenance management tasks are management of the CPU, memory, signaling
links, SS7 links, terminals, and modules.
2.10 Using the Toolbar

The toolbar contains icons of frequently used operations. These icons provide the
same functions as some of the menus. Table 2-4 lists the functions of the icons.
Table 2-4 Functions of icons in the toolbar
Icon Functions
Re-logs in the client.
Show/hide the navigation tree.
Shows/hides the system result pane.
Shows/hides the command window.
Shows/hides the wizard window.
Prints in real time.
Displays the online help.
2-53
U-SYS SoftX3000 SoftSwitch System Chapter 3 Using Alarm Management System
Chapter 3 Using Alarm Management System
3.1 Overview of Alarm Management System

The alarm management system helps you detect, isolate, and fix the faults and errors
found in the SoftX3000.
You can observe and monitor the SoftX3000 by reading the alarms reported from the
host. When a fault occurs in the SoftX3000, which might affect the service, the related
module will generate an alarm, and the alarm management module in the BAM will
display the content of the alarm. It can be a data transmission error, an operation fault,
or an overload operation. You can then locate and remove the fault according to the
alarm reported by the BAM.
The alarm management system provides the following functions and features:
z Querying fault alarms and event alarms in real time
z Browsing fault alarms, recovery alarms, event alarms, and history alarms
z Querying alarms by search conditions
z Deleting history alarms
z Filtering alarms
z Masking alarms
z Querying alarm details by alarm number
z Configuring alarm box
z Querying alarm statistics by alarm box type and network management system
z Setting and querying alarm box masking level
z Setting colors for alarms of different levels
When you query alarms using the alarm management system, you have to know the
alarm type and alarm level first.
3.2 Classification of Alarms

3.2.1 Classifying Alarms by Type
I. Overview of Alarm Types
The alarms can be classified into three types:

z Fault alarm
z Event alarm
z Recovery alarm
3-1
II. Fault Alarm
A fault alarm corresponds to a fault. It can be a circuit fault, signaling unreachable, link
interruption, or board failure. It is displayed as a fault in the alarm report. When a fault is
recovered, a recovery alarm will be generated accordingly.
III. Event Alarm
An event alarm describes an occasional and instant event during system operation. It
has no corresponding recovery alarm. Some event alarms recur regularly. It can be a
call connection or board loading.
IV. Recovery Alarm
Each recovery alarm has a corresponding fault alarm. It can be regarded as a part of
the fault alarm.
3.2.2 Classifying Alarms by Level
I. Overview of Alarm Levels
There are four levels of alarms, classified by severity. Each identifies a different level of
impact on service.
z Critical
z Major
z Minor
z Warning
II. Critical Alarm
Critical alarms have already affected the quality of service, and require immediate
actions even in non-duty hours. The equipment and network resource might be
completely unavailable.
III. Major Alarm
Major alarms have already affected the quality of service, and require immediate
actions. The quality of service and the service provisioning capability of the equipment
are degraded, and must be restored during your duty hours.
IV. Minor Alarm
Minor alarms have not affected the quality of service, but require treatment in proper
time or further observation to prevent graver faults and errors.
V. Warning Alarm
Warning alarms indicate potential errors that might affect the service.
3-2
3.3 Generic Operations

I. Overview of Starting Alaram Management System
There are two ways to start the alarm management system:

z Start it from the windows [Start] menu
z Start it from the SoftX3000 client
II. Starting from Windows Start Menu
You can start the alarm management system from the windows [Start] menu. Proceed
as follows:
Center/U-SYS SoftX3000 Operation and Maintenance System/U-SYS SoftX3000
Alarm Management System], and the Operator Login dialog box is displayed as
Figure 3-1 Starting from windows start menu
2) Select in the drop-down list box "Office Name" the office to log in.
3) Enter the operator name and password.
4) Click <OK>. The system will start the alarm management system, as shown in
Figure 3-2.
3-3
Figure 3-2 Main interface of alarm management system
III. Starting from SoftX3000 Client
After logging on to the client, you can start the alarm management system as follows:
Select [Service/Alarm Management System], as shown in Figure 3-3.
Figure 3-3 Starting the alarm management system from the client
3.3.2 Customizing Alarm Colors
Different types of alarms are displayed in different colors. You can use the default
settings or customize them. You can also set the initial alarm records and maximum
alarm records to be displayed. Proceed as follows:
1) Select [System/System Customization], and the [System Customization] dialog
3-4
Figure 3-4 Customizing alarm display settings
2) Change the options according to your requirement.

If you want to see the recovery alarms, select [Display Recovery alarms].
3) Click <OK> to save the settings.
Note:
To restore the color settings to default, click <Restore default color value>.
3.4 Browsing Alarms

After you log in to the alarm management system, you can see two windows. One lists
fault alarms, and the other lists event alarms.
3-5
3.4.1 Browsing Fault Alarms
The fault alarms can be faults occurred in the media gateway (MG), circuits, application
servers, and so on. To browse fault alarm information, you have to start the [Fault
browse] window first.
1) Select [Alarm Browse/Fault Alarm], and the [Fault browse] window is displayed as
Figure 3-5 [Fault browse] window
2) Double click an alarm record, and the detailed information of the alarm is
displayed, as shown in Figure 3-6.
Figure 3-6 Detailed alarm information
The [Alarm Explanation Details] window details the alarm serial number, alarm type,
alarm level, source of alarm, alarm ID, network management type, alarm occurrence
time, alarm cause, recovery advice, and so on.
3-6
3) Click <REMARK>, and the remark dialog box appears as shown in Figure 3-7.
Figure 3-7 Adding remark
4) Enter the remark.

5) Click <Save>.
Note:
On the heading of the [Fault Browse] window, you can see the number of alarms of all levels.
3.4.2 Browsing Event Alarms
To browse event alarm information, you have to start the [Event browse] window first.
Proceed as follows:
Select [Alarm Browse/Event Alarm], and the [Event browse] window is displayed as
Figure 3-8 [Event browse] window
3-7
3.4.3 Browsing History Alarms
To browse the history alarm, you have to start the [History browse] window first.
Proceed as follows:
Select [Alarm Browse/History Alarm], and the [History browse] window is displayed as
Figure 3-9 [History browse] window
3.4.4 Defining Alarm Filter Settings
You can set the alarm filter conditions to browse different types of alarms. Proceed as
follows:
1) Select [Alarm Browse/Alarm Filter Browse], and the [Alarm filter setting] dialog box
is displayed as shown in Figure 3-10.
Figure 3-10 Defining alarm filter settings
2) Select the alarm type and alarm level to be displayed.

3) Specify the module number and network management type.
4) Click <OK>. The filtered alarm browse window will be displayed.
3-8
3.4.5 Filtering Alarms of Malicious Calls and Emergency Calls
You can filter the information related to malicious calls and emergency calls from event
alarms. Proceed as follows:
Select [Alarm Browse/ Malicious/Emergency Call Browse], and the
[Malicious/emergency call browse] dialog box is displayed as shown in Figure 3-11.
Figure 3-11 Filtering alarms of malicious and emergency calls
3.5 Querying Alarms

3.5.1 Notes on Querying Alarms
At maximum, 1000 alarms can be queried at a time.

The module number ranges from 1 to 252. When you set the module number to 255,
the alarm information of the BAM will be displayed.
The alarm number ranges from 1 to 5000.
The alarm ID is unique for each alarm. It represents a certain fault or event, the alarm
level, and the network management type. The alarm ID can be used to obtain the alarm
name, recovery advice, and alarm cause. The alarm ID of the recovery alarm is the
alarm ID of the corresponding fault alarm plus one. The alarm IDs are usually
segmented.
The start time must be earlier than or equal to the end time. The start date must be
earlier than or equal to the end date.
3.5.2 Operation Procedure
You can query a certain type of alarm. Proceed as follows:

1) Select [Alarm Query/Query], and the [Alarm Query Setting] dialog box is displayed
3-9
Figure 3-12 Defining alarm query settings
If you need to specify the options other than alarm type, you have to select the
corresponding check boxes first.
2) Specify the options and fields in the [Alarm Query Setting] dialog box.
3) Click <OK>, and the [Alarm query result] window is displayed as shown in Figure
3-13.
Figure 3-13 [Alarm query result] window
3.6 Alarm Management Operations

3.6.1 Deleting History Alarms
You can delete the unwanted alarm records of a certain period to release harddisk
space. Proceed as follows:
3-10
1) Select [Alarm Management/Delete Alarm], and the [Delete Alarm] dialog box is
Figure 3-14 Deleting unwanted alarms of the certain period
2) Specify the [Start date] and [End date] of the alarms to be deleted.
3) Click <OK>.
Note:
z The unrecovered fault alarms cannot be deleted.
z The [End date] is a mandatory parameter, while the [Start date] is optional.
z When the [Start date] is not specified, the system will delete one week of alarms by default. The start
date is one week earlier than the end date.
3.6.2 Masking Alarms
There can be a huge number of alarms reported at the host. When you just need to see
certain types and more important levels of alarms than others, you can mask the
unwanted alarms. Proceed as follows:
1) Select [Alarm Management/Alarm Mask], and the alarm masking dialog box is
3-11
Figure 3-15 Masking unwanted alarms from reporting
2) Define a mask setting.

3) Click <Add>.
When the [Alarm mask query] window exists, the mask setting list will be updated. The
new alarm mask setting will be added.
You can also select and delete a mask setting. The setting will also be removed from
the alarm mask query window.
To query the alarm mask settings, proceed as follows:
4) Enter the mask settings.
5) Click <Query>, and the [Alarm mask query result] window will be displayed as
Figure 3-16 [Alarm mask query result] window
3-12
Note:
Alarm filtering and alarm masking are different. The former is to send a command to the BAM and prevent
it from sending the masked alarms to the alarm management system. The latter is to prevent the filtered
alarms to be displayed.
3.6.3 Querying Alarm Configurations
You can query the following configuration items:

z Alarm ID
z Alarm name
z Send alarm flag
z Send alarm box flag
z Send network management flag
z Alarm level
z Network management alarm level
z Network management alarm type
z Alarm box alarm type
Proceed as follows:
1) Select [Alarm Management/Alarm Configuration Query], and the query alarm
parameter dialog box is displayed as shown in Figure 3-17.
Figure 3-17 Setting the alarm ID of the alarm to be queried
2) Select [Alarm ID].

3) Enter the alarm ID to be queried.
4) Click <OK>, and the [Query Alarm Configuration] window is displayed as shown in
Figure 3-18.
3-13
Figure 3-18 Query results of alarm parameters
Note:
If you directly click <OK> without selecting [Alarm ID], all alarm records will be displayed.
3.6.4 Defining Alarm Box Control Settings
You can define the alarm box control settings to control the alarm box. Proceed as
follows:
1) Select [Alarm Management/Alarmbox Control], and the alarm box control dialog
Figure 3-19 Defining alarm box control settings
2) Select the function in [Function operation].

Here, [Darken alarmbox status light] means to turn off the alarm box indicator. You also
have to specify the alarm level.
3) Select the alarm level in the pull-down menu.
4) Click <OK> to update the settings.
3.6.5 Defining Alarm Statistics
The alarm statistics function is to measure the number of a specific type of alarm.
Proceed as follows:
3-14
1) Select [Alarm Management/Alarm Statistics], and the query alarm parameter

Figure 3-20 Querying alarm statistics
2) Define [Alarm type] and [Alarm level].

3) When you select and specify [Module No.], you can query the alarm statistics by
module number.
4) Select and specify [Alarm ID]. You can query the alarm statistics by alarm ID.
5) Select and specify start date, end date, start time, and end time. You can obtain
the alarm statistics of a certain period.
6) After specifying all options you need, click <OK> and the query result is displayed
3-15
Figure 3-21 Results of alarm statistics query
3.6.6 Defining Alarm Box Screen Level
You can define the alarm box screen level to prevent the BAM from sending the alarms
of lower levels to the alarm box. For instance, if you set it to major, the BAM will not
send minor and warning alarms to the alarm box. Proceed as follows to define the
alarm box screen level:
1) Select [Alarm Management/Alarm Box Screen Level/Set], and the alarm box
screen level dialog box is displayed as shown in Figure 3-22.
Figure 3-22 Defining alarm box screen level
2) Select the alarm level.

3) Click <Apply> to update the settings.
3-16
3.6.7 Querying Alarm Box Screen Level
Proceed as follows to query alarm box screen level:

Select [Alarm Management/Alarm Box Screen Level/Get], and the alarm box screen
level is displayed as shown in Figure 3-23.
Figure 3-23 Querying alarm box screen level
3.6.8 Defining Sound Durations for Fault Alarms
You can define the sound duration of different levels of alarms. Proceed as follows:
1) Select [Alarm Management/Fault Alarm Sound], and the setting dialog box is
displayed.
2) Select [Enable Alarm Sound].
3) Define the sound durations of alarms, as shown in Figure 3-24.
Figure 3-24 Defining sound durations for fault alarms
4) Click <OK>.
3-17
Note:
z If no sound card is properly installed on the computer, you cannot hear the alarm sound.
z You have to select a certain level of alarm in the window before you can specify the alarm sound
duration.
3.7 Using Other Alarm Related Options

3.7.1 Overview of Other Alarm Related Options
There are some additional functions in the main interface of the alarm management
system:
z Using the shortcut menu
z Querying alarm explanation details
z Saving alarm content to file
z Acknowledging alarms
z Recovering alarms
z Clearing recovery alarms
3.7.2 Using Shortcut Menu
You can use the shortcut menu to stop scrolling, acknowledge alarms, clear part or all
recovery alarms, save alarm information, and refresh the screen. Proceed as follows:
1) Right click in the [Fault browse] window or [History browse] window, and a shortcut
menu of alarm-related operations is displayed as shown in Figure 3-25.
Figure 3-25 Shortcut menu in [Fault browse] window and [History browse] window
The shortcut menu in the [Event browse] window has fewer options, as shown in Figure
3-26.
Figure 3-26 Shortcut menu in [Event browse] window
3-18
2) Save the information in text or excel format.
3.7.3 Querying Alarm Explanation Details
Proceed as follows:
1) Double click an alarm record, and the [Alarm Explanation Details] window will be
Figure 3-27 Alarm explanation details of a fault alarm
2) Click <REMARK>, and the remark dialog box appears as shown in Figure 3-28.
Figure 3-28 Adding remarks in a fault alarm
3) Add remark for the alarm.

4) Click <Save> to save the remark.
3-19
3.7.4 Saving Alarm Content to File
You can save the alarm content to files for future reference. There are two formats
supportedtext and excel. Proceed as follows:
1) Right click the alarm record to be save, and a shortcut menu will be displayed as
2) Select the file format under Save as, and the save attributes to file dialog box will
be displayed as shown in Figure 3-29.
Figure 3-29 Saving alarm content to file
3) Specify the path for the file.

4) Click <Save> to save the file.
3.7.5 Recovering an Alarm
I. Notes on Recovery Alarms
You have to select a fault alarm record, or the Recover alarm option is unavailable.
You can recover one or multiple alarms.
When you have defined different display colors for fault alarms and recovery alarms,
the color of the alarm will be changed accordingly. The alarm type will be changed from
Fault to Recovery. To clear it, select Clear Part of Recovery Alarm.
The change of color of the alarm record will be reflected in all windows that are
displaying it.
II. Operation Procedure
You can use the option to recover a fault alarm in the GUI. Proceed as follows:
3-20
1) Right-click an alarm to be recovered, and the shortcut menu is displayed as shown

in Figure 3-30.
Figure 3-30 Recovering an alarm
2) Select Recover Alarm, and the alarm is recovered.
3.7.6 Acknowledging an Alarm
To acknowledge an alarm record, proceed as follows:

1) Right click the alarm record to be acknowledged, and the shortcut menu is
Figure 3-31 Acknowledging an alarm
2) Select Acknowledge Alarm, and the alarm is acknowledged.
3.7.7 Clearing Recovery Alarms
You can clear some or all recovery alarms according to your need.
I. Clearing All Recovery Alarms
Proceed as follows:
1) Right click any alarm record, and the shortcut menu is displayed as shown in
Figure 3-32.
3-21
Figure 3-32 Clearing all recovery alarms
2) Select "Clear All Recovery Alarms, and all recovery alarms are cleared.
Note:
There should be at least one recovery alarm, or the [Clear All Recovery Alarms] option is unavailable.
II. Clearing Selected Recovery Alarms
Proceed as follows:
1) Right click the alarm records to be cleared, and the shortcut menu is displayed as
Figure 3-33 Clearing selected recovery alarms
2) Select "Clear Part of Recovery Alarms, and the selected recovery alarms are
cleared.
Note:
z There should be at least one recovery alarm, or this option is unavailable.
z When you have also selected fault alarms, they will not be cleared from the alarm management
system.
3-22
3.8 Defining Print Options

3.8.1 Overview of Using Print Options
You might frequently need to print out the alarm information details. To do so, the
system has multiple print options for your choice.
3.8.2 Defining Real Time Print Filter Settings
You can define the types and levels of alarms that you wish to print, and filter the rest.
Proceed as follows:
1) Select [System/Realtime Print Filter Setting], and the real time printer filter setting
Figure 3-34 Defining real time print filter settings
2) Select the alarm type, alarm level, and network management type.
3) Enter the module number.
4) Click <OK>.
3.8.3 Printing Alarm Details in Real Time
After defining the real time print filter settings, select [System/Realtime Print].
The system will not immediately print the real time alarm report until there is enough
content to fill up a page.
If you want to print information in real time, remember to select [System/Flush Printer]
after the system generates real time alarms.
3.8.4 Flushing the Printer
To flush the printer, select [System/Flush Printer].
3-23
If the buffer is empty, a blank page will be printed.

The printer will print all content in the buffer until it is empty.
3-24
U-SYS SoftX3000 SoftSwitch System Chapter 4 Using Performance Management System
Chapter 4 Using Performance Management

System
4.1 Overview of Performance Measurement

Performance measurement is also known as payload measurement or traffic
measurement.
It refers to various measuring activities carried out on the softswitch and the
communication networks to obtain the following measurement data:
z Running status
z Signaling information
z User information
z System resources
It provides reliable data reference for the following purposes:
z Operation management
z Troubleshooting of equipment
z Network monitoring
z Network maintenance
z Network planning
z Network designing
4.2 Generic Operations

4.2.1 Workflow of Performance Measurement
You can implement performance measurement by applying tasks. Figure 4-1 lists the
procedure of performance measurement. The boxes in broken lines are optional steps.
4-1
Start
Analyze performance measurement

demand
Create performance measurement task
Start performance measurement task
Query performance measurement task
Modify performance measurement task
List performance measurement result
Deactivate performance measurement

task
Activate performance measurement

task
Performance measurement task ends
Delete performance measurement task
End
Figure 4-1 Operation procedure of performance measurement
You can implement the following tasks in the performance management system:
z Creating a performance measurement task
z Modifying a performance measurement task
z Querying the details of a performance measurement task
z Query, save, and print performance measurement results
z Delete a performance measurement task
The first task is the most important one. All the rest are based on the created task.
4.2.2 Logging in to the Performance Management System
You can implement various performance measurement operations in either Graphical

User Interface (GUI) or by Man Machine Language (MML).
4-2
I. Operations in GUI

Center/U-SYS SoftX3000 Performance Management System]. The dialog box for
setting office name and IP address is displayed.
2) Click <Set>.
3) Enter the office name and IP address.
4) Select the office to be measured in the login dialog box.
5) Enter the account and password. The main interface of the performance
management system is displayed as shown in Figure 4-2.
Figure 4-2 [U-SYS SoftX3000 Performance Management System] window
II. Operations by MML
You can execute a command at the client, for example, CRE TRFOTF, as shown in
Figure 4-3.
4-3
Figure 4-3 Interface for MML command input
The two modes have the same results.

The GUI mode is more obvious, and easy to understand and follow. This chapter will
focus on operations in GUI mode only.
4.3 Cautions and Notes

4.3.1 Maximum Number of Tasks
Each performance measurement task occupies some system resources. The cases
that too many tasks are carried out simultaneously or too frequently will lead to
resource over-consumption, so a maximum of 128 tasks can be created.
4.3.2 User Authority
The performance measurement system divides user authorities into three levels:
service query, service setting and service management. Refer to Table 4-1for the
specific authorities of each level.
4-4
Table 4-1 Table of user authorities
Users with service Users with service Users with service

Operations
query authority setting authority management authority
Creating a task Prohibited Allowed Allowed
Deleting a task or a Allowed for the user who
Prohibited Allowed
result creates the task
Modifying the name Allowed for the user who
Prohibited Allowed
of a task creates the task
Customizing a
Prohibited Prohibited Allowed
measurement entity
Querying a task and
Allowed Allowed Allowed
its result
4.3.3 Measurement entities
For any of extremum measurement entities of a measurement object, for example,

measurement of CPU occupation rate, it cannot be created in multiple measurement
tasks; otherwise, the measurement result will be inaccurate.
4.3.4 BAM time
The result output of a measurement task is closely related to the time. If the BAM time is
modified, it is possible that the result exported within the next measurement period will
be incorrect.
4-5
4.4 Creating a Performance Measurement Task

4.4.1 General Workflow
Figure 4-4 tells the workflow of creating a task.
Start
Yes Define entity thresholds

Customize entity or not? Customize entity
No
Optional
Define sampling parameters
Enter task name and description
infomation
Define report output mode

Select task type
End
Select measurement unit
Select measurement entity
Select measurement object
Set measurement period, measurement

time segment, and output period
Figure 4-4 Procedure of creating a performance measurement task
Suppose it is required to create a task for measuring the IAD traffic with the
requirements below:
z Measurement entities include call attempts, seizure times, call connected times,
answer times, answer traffic, seizure traffic, connect traffic, and customized no
answer times of IAD 0 and IAD1.
z The measurement starts from Oct. 24, 2003 and lasts for 30 days. It is carried out
for five minutes between 9:0011:00, 14:0016:00, and 19:0021:00 from
Monday to Friday.
z When each measurement period ends, the report will be sent immediately to the
workstation, performance measurement port, and network manager port.
4-6
4.4.2 Customizing an Entity
I. Overview of Customizing an Entity
You can customize entities to meet the actual need of performance measurement.
Figure 4-5 shows the procedure of customizing an entity.
Select measurement
unit
Redefine original Yes

entity or not
No
Select [Define] Select [Redefine]
Enter entity alias Select entity whose

calculation formula is
to be modified
Enter entity name
Select entity unit
Select entity type
Select entity
Determine calculation
formula
Figure 4-5 Procedure of customizing an entity
II. Opening [Set Custom Entity] Dialog Box
Proceed as follows:
Select [Entity/Set Custom Entity] in the main interface as shown in Figure 4-2. The [Set
Custom Entity] dialog box as shown in Figure 4-6 is displayed.
4-7
Figure 4-6 [Set Custom Entity] dialog box
III. Selecting a Measurement Unit
The measurement unit for the IAD traffic task is MGW Traffic. Therefore, select
MGW Traffic for [Measure Unit].
IV. Setting Calculation Formula for a Custom Entity
You can modify or set the calculation formula of either an original entity or a custom
entity.
Table 4-2 shows the procedure of setting calculation formula for a custom entity.
Table 4-2 Procedure of setting calculation formula for a custom entity
Step Operations Parameter description
1 Select [Define].
The length of entity alias cannot be more than

nine characters.
(1) Enter alias and name of the custom
entity. The entity unit can be millisecond, percentage,
2
byte, or no unit.
(2) Select entity unit and entity type.
The entity type can be Integer, Float, Time, and
BCD Code.
3 Select an original entity. The entity is determined by the unit.
4-8
Click a button in and then select

4 NA
another original entity or a value to
determine the calculation formula for the
custom entity, as shown in Figure 4-7.
Click <OK>. The [Operation Succeeded]
prompt is displayed. The [Entity list] will
have a MGW No Answer Times icon
listed. Here, MGW No Answer Times = Call
5
Connected Times Answer Times.
Figure 4-7 Example of setting calculation formula for a custom entity
Note:
z After step 4, if you need to modify the calculation formula of the custom entity, you can delete the
calculation formula in the above dialog box directly and define a new one.
z To modify a determined calculation formula of an entity, you can right click the entity icon in the entity
field in Figure 4-2 and then select [Modify Custom Entity] on the shortcut menu.
4-9
V. Modifying Calculation Formula of an Original Entity
Table 4-3 lists the operation procedure of modifying calculation formula of an original
entity.
Table 4-3 Procedure of modifying calculation formula of an original entity

1 Delete the existing calculation formula. NA
The entity is determined by
2 Select an original entity.
the unit.
3 NA
Click a button in and then select another original entity
to set the calculation formula.
4 Click <OK>. The [Operation Succeeded] prompt is displayed. NA
4.4.3 Launching the Task Creation Interface
There are three ways to launch the task creation interface inFigure 4-2
z Right click the Task List(All) icon and select [Create Task] on the displayed
shortcut menu.
z Select [Task/Create Task] in the main interface.
z Press the shortcut keys <Ctrl+N>.
The [Create a New Task] dialog box is displayed as shown in Figure 4-8.
4-10
Figure 4-8 [Create a New Task] dialog box
4.4.4 Defining Task Attributes
I. Specifying Task Name and Description
The task name must be concise and the description should reveal the task purposes. It
can be a maximum of 32 characters including letters, digits, and symbols (no space
allowed).
Here, the task name is IADAnswerRate and the task description is "IAD Answer
Rate.
II. Selecting Task Type
Each measurement entity is subject to the related measurement function type and
measurement type. For a measurement task, you can only select the entities subject to
the same measurement function type as the task. That is, all measurement entities of a
4-11
task must belong to one or more measurement types of the same measurement
function type.
The measurement unit for the task IAD Traffic is MGW Traffic. Because MGW
Traffic is a bearer task, select Bear Traffic for [Traffic task type] in Figure 4-8.
4.4.5 Selecting a Measurement Unit
Select MGW Traffic for [Measurement Unit] in Figure 4-8.
4.4.6 Selecting Measurement Entities
Caution:
If it is necessary to customize an entity, refer to 4.4.2.
Proceed as follows to select measurement entities:

1) Select the task type and measurement unit.
2) Click the [Entity] tab in Figure 4-8. The [Entity] tab page is displayed, as shown in
Figure 4-9.
4-12
Figure 4-9 [Entity] tab page
Note:
If there is any custom entity, it will be shown in the [Available custom entities] field. The selection of a
custom entity is in the same way as that of an original (static) entity.
3) Select the entities as needed, as shown in Figure 4-10.

Table 4-4 explains the fields and buttons in the [Entity] tab page.
4-13
Table 4-4 Meaning of the fields and buttons in the [Entity] tab page
Field or button Function

Available static entities It lists the original measurement entities defined in the system.
Selected static entities It lists the selected entities, indicating data should be collected for them.
It is used to add the measurement entities selected from the [Available
static entities] field to the [Selected static entities] field.
Caution:
It is disabled unless you select a measurement entity from the [Available
static entities] field.
It is used to delete a selected measurement entity from the [Selected
Caution:
It is disabled unless you select a measurement entity from the [Selected
It is used to add all the measurement entities listed in the [Available static
entities] field to the [Selected static entities] field.
It is used to delete all the measurement entities from the [Selected static
entities] field.
It is disabled in creating a measurement task, but enabled when you
modify properties of a task.
Here, measurement entities include call attempts, seizure times, call connected times,
answer times, answer traffic, seizure traffic, connect traffic, and customized no answer
times.
4-14
Figure 4-10 Selected entities
Note:
The custom entity MGW No Answered Times is also selected.
4.4.7 Selecting a Measurement Object
Proceed as follows to select a measurement object:
4-15
1) Click the [Object] tab in Figure 4-8. The [Object] tab page is displayed, as shown in
Figure 4-11.
2) Select Certain MGW EID for object type.
3) Enter the ID (that is, iad88.com) of IAD 1 in the [Certain MGW EID] field. You can
query MGW EID using LST MGW.
4) Click <Add Object Instance> to add the selected measurement object into the list,
Figure 4-11 [Object] tab page
4-16
Note:
You can select multiple measurement objects for one measurement task. However, you can only enter
one object when entering the measurement entity.
4.4.8 Setting Time Properties
Proceed as follows to set time properties:

1) Click the [Time] tab in Figure 4-8. The [Time] tab page is displayed, as shown in
Figure 4-12.
Figure 4-12 [Time] tab page
4-17
Table 4-5 explains the fields and buttons in the [Time] tab page.
Table 4-5 Meaning of the fields and buttons in the [Time] tab page
Field or button Meaning Value range Remarks

It is used to specify
Any valid date. It is in the format
the date when a It is recommended to enter the current
Start Date of Year-Month-Day, for
measurement task is date.
example, 2003-10-23.
started.
Select it as needed. If Statistics
Statistics Duration is not checked, the
the duration of a 1-1024 days
Duration measurement task will be carried out
measurement task.
permanently.
It is used to specify It can be one minute, five
By default, it is set to 15 minutes.
the interval for minutes, ten minutes, fifteen
Measure Period Generally, it is recommended to set it
exporting a minutes, thirty minutes, one
to 30 minutes or 1 hour.
measurement result. hour, or one day.
Measure Every Day: The
measurement is carried out
every day.
Measure Date(s) Every Week:
You can select several days for
Measure Date(s) the date for Select it as needed.
measurement from the list box.
measurement.
Measure Date(s) Every Month:
You can select several days in
a month for measurement from
the list box.
the time segment(s)
Measure Time 13 Select it as needed.
in a day for
measurement.
It is used to set which

It can be dragged upward or
time segment is Three positions
downward.
effective.
Set the most concerned time
Start Time1 the start time of the 00:0024:00
segment.
first time segment.
the start time of the It cannot be overlapped with the first
Start Time2 00:0024:00
second time time segment.
segment.
It cannot be overlapped with the first
Start Time3 the start time of the 00:0024:00
and second time segments.
third time segment.
4-18
2) Here, set [Start Date] to 2004-10-29, [Statistics Duration] to 30 days, [Measure

Date(s)] to from Monday to Friday, [Measure Time Segment] to 11:0013:00,
14:0016:00, and 19:0021:00, and [Measure Period] to 5 minutes.
4.4.9 Defining Entity Thresholds
Proceed as follows to define entity thresholds:

1) Click the [Threshold] tab in Figure 4-8. The [Threshold] tab page is displayed, as
You can define upper and lower thresholds for a maximum of four entities. Set the
upper and lower thresholds as needed. If only the upper threshold of an entity is
concerned, you can set the lower threshold to 0. Likewise, if only the lower threshold
is concerned, set the upper threshold to 0.
Caution:
Not all measurement entities have thresholds, but only those with threshold property can be set with
thresholds. In this example, the measurement entities have no threshold.
4-19
Figure 4-13 [Threshold] tab page
Table 4-6 explains the fields in the [Threshold] tab page.
Table 4-6 Meaning of the fields in the [Threshold] tab page
Field Meaning
Entity Threshold List It lists the entities which can be set with threshold.
Lower Threshold It is used to set the lower threshold of an entity.
Upper Threshold It is used to set the upper threshold of an entity.
By clicking this button, you can validate the upper and lower
Set Threshold
thresholds that have been set.
4-20
Field Meaning
It lists the information of the entities whose thresholds have
List of Thresholds which have been set
been set.
After selecting an entity record in the [List of Thresholds
Delete Threshold which have been set], you can click this button to delete the
thresholds of this entity.
4.4.10 Defining Sampling Parameters and Report Output Mode
Proceed as follows to define sampling parameters and report output mode:

1) Click the [Other] tab in Figure 4-8. The [Other] tab page is displayed, as shown in
Figure 4-14.
4-21
Figure 4-14 [Other] tab page
Table 4-7 explains the fields in the [Other] tab page.
Table 4-7 Meaning of the fields in the [Other] tab page
Field Meaning
Some measurement units generate two much information, so sampling
measurement is necessary to keep accuracy and reduce system
Sampling Parameter
burden to some extent. The default sampling rate is 100%. Note that
not every measurement unit has sampling parameters.
4-22
Field Meaning
It is used to set the destination where a measurement report will be
sent. There are three options:
Output Device Current Workstation
Traffic Statistic Port
Network Manager Port
It is used to define the time when a measurement report will be
exported. There are three options:
PerPeriod Output: When a measurement period ends, the report will be
Output Arrangement exported immediately.
Specific Output: The report will be exported at specified time.
Over Threshold Output: A report will be exported only when the
measurement result is beyond the threshold range.
Here, when a measurement period ends, the system will immediately send a
measurement report to the current workstation, traffic statistic port, and network
manager port.
2) After setting all the parameters, click <OK>.
If the task is created successfully, an icon will appear under the [Task List (all)] node, as
Figure 4-15 Interface showing successful creation of the task
4.4.11 Measurement Task State
There are seven states for a measurement task. In Figure 4-15, IADAnswerRate
(Running) indicates that the task is running currently. Table 4-8 explains various states
of a measurement task.
Table 4-8 Meaning of various states of a measurement task
State Meaning
Running tasks It indicates that a task is running currently.
Error tasks It indicates that a task is wrongly set.
4-23
State Meaning
Ended tasks It indicates that a task has ended.
Deactivated tasks It indicates that a task has been deactivated.
No objected instance tasks It indicates that a task has no measurement object.
It indicates that a task has been created successfully, but the start
Setup tasks
time has not arrived yet.
It indicates that a task fails to be created in the host. When a task is
Undefined tasks deactivated, it is deleted from the host, and its state will be
displayed as Undefined.
4.5 Querying or Dumping Results of a Measurement Task

4.5.1 Querying Results of a Measurement Task
I. Opening [Query Task Result] Dialog Box
In the [U-SYS SoftX3000 Performance Management System] window as shown

inFigure 4-2, right click a task under the [Task List(All)] node and then select [Query
Task Result] on the shortcut menu. A dialog box as shown in Figure 4-16 appears.
Figure 4-16 [Query Task Result] dialog box
Table 4-9 explains the fields in the [Query Task Result] dialog box.
4-24
Table 4-9 Meaning of the fields in the [Query Task Result] dialog box
Field Meaning
Original: Only the results of the original measurement entities will be displayed.
Evolve: The results of the original measurement entities including those whose
calculation formulas have been modified will be displayed.
Entity Style Brief: The results of the original measurement entities and custom measurement
entities will be displayed.
Detailed: The results of all measurement entities (including original measurement
entities, original measurement entities whose calculation formulas have been
modified, and custom measurement entities) will be displayed.
Normal: The default report type of the system.
Sum by Period: The measurement result of each entity equals the total value of all
entities of the same type within the period.
Sum by Object: The measurement result of each entity equals the total value of all
entities of the same type for different measurement objects.
Report Type
Sum by Period and Object: The measurement result of each entity equals the total
value of all entities of the same type for different measurement objects within the
measurement period.
Threshold Overflow: Only the measurement results of the entities that exceed the
threshold range will be displayed.
Continuous: The system will export results generated from a time point of the start date
to a time point of the end date. For instance, set the start date to 2004-03-01 (March 1,
2004), end date to 2004-03-03 (March 3, 2004), start time to 10:00, and end time to
15:00.
Segment: The system will export results generated from the start time to the end time
Time Type
of each day between the start date and the end date. For the same settings as above,
the system will export the measurement reports from 10:00 to 15:00 on March 1, 2 and
3.
If neither Continuous nor Segment is selected, only the result exported when the
previous period ends will be displayed.
Start Date It is used to set the date when a measurement task starts.
Start Time It is used to set the time when a measurement task starts.
End Date It is used to set the date when a measurement task ends.
End Time It is used to set the time when a measurement task ends.
II. Displaying Measurement Results
Proceed as follows to display measurement results:

Suppose it is required to display the normal reports for the original measurement
entities from 00:00 of 2004/11/22 to 23:59 of 2004/11/29.
1) Click <Query>. The measurement results are as shown in Figure 4-17.
4-25
Figure 4-17 Interface showing measurement results
There are three tab pages in the right pane of Figure 4-17: [Result List], [Detailed
Information], and [Graphics Display].
[Result List] lists such information as object name, measurement unit, measurement
time, and entity value in a table.
Caution:
If it is required to display the measurement results of the entities of a specific type only, you need to select
an entity style in Figure 4-16.
2) Right click a record to display the shortcut menu as shown in Figure 4-18.
4-26
Figure 4-18 Shortcut menu in the [Result List] tab page
Select the corresponding item on the shortcut menu to carry out such operations as
refreshing results, printing results, saving results as Excel file, sorting results by time,
and sorting results by entity.
3) Click <Detailed Information> tab to display the tab page as shown in Figure 4-18.
Figure 4-19 [Detailed Information] tab page
This page lists the results exported at the end of a measurement period for a
measurement object, including entity name, entity value, and entity unit.
4-27
Caution:
If it is required to display the measurement results of the entities of a specific type only, you need to select
an entity style in Figure 4-16.
By clicking , you can browse the measurement results of different

objects or exported at the end of different periods. To select different objects, click
or . To select different periods, click .
4) Click <Graphics Display> tab to display the tab page as shown in Figure 4-20.
This page displays the measurement results vividly in data chart.
Figure 4-20 [Graphics Display] tab page
Table 4-10 explains the fields and buttons in the [Graphics Display] tab page.
Table 4-10 Meaning of the fields and buttons in the [Graphics Display] tab page
Field Meaning
Specific Object The chart is displayed based on specific measurement object.
Specific Time The chart is displayed based on specific measurement time.
It is used to display the previous result chart based on specified object
and time.
4-28
Field Meaning
It is used to display the next result chart based on specified object and
time.
There are three options for graphics display:
Histogram chart
Folded line chart
Pie chart
It is used to set the color for specific entity value.
4.5.2 Dumping Results of a Measurement Task
Proceed as follows to dump measurement task results:

1) Open [Dump Task Result] dialog box.
There are two ways:
z Right click the icon of the task to be deactivated, and then select [Dump Task
Result] on the shortcut menu.
z Click [Dump Task Result] on the [Task] menu in the main interface.
2) Set time type, date, and time for backup. After confirmation, the measurement
results will be dumped in a file named as RST_???.DBF in the directory D:\Stats
on the BAM (??? Stands for task name).
4.6 Querying the Details of a Measurement Task

To query information of a measurement task, double click the task icon in the navigation
tree. Various information of a task will be shown as in Figure 4-21.
4-29
Figure 4-21 Interface showing detailed information of a task
There are three tabs in the [Task Information] pane, which are described in Table 4-11.
Table 4-11 Functions of tabs in the [Task Information] pane
Tab name Function

It lists such information as the name, description, measurement unit,
Basic Information measurement period, output device, number of time segment, and duration days
of a task.
It lists the names of original entities, custom entities, and original entities whose
Entity Information
calculation formulas have been modified of a task.
Object Information It lists the names of measurement objects of a task.
4-30
4.7 Modifying Configuration Information of a Measurement

Task
4.7.1 Overview of Modifying Task Configuration
You can modify the configuration information of a task by right clicking a task icon and
then selecting the corresponding item on the shortcut menu, or by clicking the
corresponding item on the [Task] menu in the main interface.
z Modifying task name
z Modifying task output mode
z Modifying measurement entities
z Modifying time information
z Modifying sampling parameters
z Modifying measurement entity thresholds
z Deleting measurement entity thresholds
z Adding measurement object
z Deleting measurement object
During the modification, you can restore the original setting by clicking <Reset> in the
lower left corner of the dialog box.
Note:
When modifying the information of a measurement task, you can view both the original measurement
results and the new results after the modification in one table.
4.7.2 Modifying Task Name
Proceed as follows:
1) Right click a task icon.
2) Select [Modify Task Name] on the shortcut menu.
3) Modify the name of the task in the pop up dialog box.
4) Click <OK>.
Do not modify the task description.
4.7.3 Modifying Task Output Mode
Proceed as follows:
2) Select [Modify Task Output Mode] on the shortcut menu.
4-31
3) Modify the task output mode, that is, when to export the report.
4) Click <OK>.
II. Description of Options
When a measurement period ends, the report will be exported

PerPeriod Output
immediately.
Specific Output The report will be exported at specified time.
A report will be exported only when the measurement result is beyond
Over Threshold Output
the threshold range.
4.7.4 Modifying Report Output Device
Proceed as follows:
2) Select [Modify Output Device] on the shortcut menu
3) Modify the report output device of the task in the pop up dialog box.
4) Click <OK>.
4.7.5 Modifying Measurement Entities
Proceed as follows:
2) Select [Modify Measurement Entities] on the shortcut menu.
3) Modify the measurement entities of the task in the pop up dialog box.
4) Click <OK>.
4.7.6 Modifying Time Information
Proceed as follows:
2) Select [Modify Time Info ] on the shortcut menu.
3) Modify the time information of the task in the pop up dialog box.
4) Click <OK>.
4.7.7 Modifying Sampling Parameters
Proceed as follows:
2) Select [Modify Sampling Parameter] on the shortcut menu.
3) Modify the sampling parameters in the pop up dialog box.
4) Click <OK>.
4-32
4.7.8 Modifying Measurement Entity Thresholds
Proceed as follows:
2) Select [Set Task Threshold] on the shortcut menu.
3) Select the entity to be modified in the pop up dialog box.
4) Enter the upper and lower thresholds.
5) Click <Set Threshold>.
6) Click <OK>.
For a task, you can set the thresholds of a maximum of four entities.
After the setting of four entities, the button <Set Threshold> becomes unavailable. To
modify the thresholds of a fifth entity, proceed as follows:
7) Right click the task icon
8) Select [Delete Task Threshold] on the shortcut menu to delete the thresholds of an
entity.
9) Select [Set Task Threshold] on the shortcut menu to add the thresholds for the fifth
entity.
4.7.9 Deleting Measurement Entity Thresholds
Proceed as follows:
2) Select [Delete Task Threshold] on the shortcut menu.
3) Select the entity to be deleted in the pop up dialog box.
4) Click <Delete Threshold>.
5) In the dialog box for confirmation, click <OK>.
4.7.10 Adding Measurement Object
Proceed as follows:
2) Select [Add Measurement Object Instance] on the shortcut menu.
3) Click <Select Object Data> in the pop up dialog box.
4) Select the measurement object to be added.
5) Click <OK>.
4.7.11 Deleting Measurement Object
Proceed as follows:
2) Select [Delete Measurement Object Instance] on the shortcut menu.
4-33
3) Select the object to be deleted.

4) Click <Delete Object Instance>.
5) In the dialog box for confirmation, click <OK>.
You cannot delete the last object.
4.8 Deleting a Performance Measurement Task

There are two ways:
z Right click the icon of the task to be deleted, and then select [Delete Task] on the
shortcut menu.
z Click [Delete Task] on the [Task] menu in the main interface.
4.9 Activating and Deactivating a Measurement Task

4.9.1 Overview
When a measurement task is running, you can stop it temporarily by deactivating it, and
you can re-activate it when needed. In the navigation tree, if a task is headed with an
icon , it indicates that the task is running currently. If the icon is shown, it
indicates that the task has been deactivated.
4.9.2 Deactivating a Task
There are two ways:

z Right click the icon of the task to be deactivated, and then select [Deactivate Task]
on the shortcut menu.
z Click [Deactivate Task] on the [Task] menu in the main interface.
4.9.3 Activating a Task
There are two ways:

z Right click the icon of the task to be activated, and then select [Activate Task] on
the shortcut menu.
z Click [Activate Task] on the [Task] menu in the main interface.
4.10 Setting Clear Time of a Measurement Task

Proceed as follows to set the clear time of a task:
1) Right click the icon of the task and then select [Set Clear Time] on the shortcut
menu, or click [Set Clear Time] on the [Task] menu in the main interface. A dialog
box for setting the clear time appears.
2) Enter the desired time and click <OK>.
4-34
U-SYS SoftX3000 SoftSwitch System Chapter 5 Trace and Maintenance
Chapter 5 Trace and Maintenance
5.1 Trace and Maintenance Navigation Tree

The navigation tree consists of two partstrace management and maintenance
management. In the navigation tree of the client interface, click the [Monitor] pane,
and the trace and maintenance navigation tree is displayed as shown in Figure 5-1.
Figure 5-1 Trace and maintenance navigation tree
Trace management is the real-time tracing and observation of the connection of the
user circuit, trunk circuit, and interface signaling link in the following aspects:
z Connection procedure
z State migration
z Resource usage
z Call party release procedure
z Coding sending
z Control signaling flow
You can save the trace results for future reference. You can also print the trace results.
The trace management feature is very helpful in the daily maintenance of the
SoftX3000. It can help you quickly find the cause of failure and find a solution to the
problem. It also provides you detailed information of signaling and message
coordination.
5-1
The trace management node includes two subnodesInterface Trace Task and User
Trace Task.
5.2 Interface Trace Tasks

5.2.1 Overview of Interface Trace Tasks
Expand the interface trace task node, and the type of interfaces that can be traced
are shown in Figure 5-2.
Figure 5-2 Navigation tree of interface trace task
The following details the operation procedure of different interface trace tasks
5-2
Caution:
z Do not trace for long durations.

z Do not trace during heavy traffic.
5.2.2 Tracing Using Ping
I. Overview of Tracing Using Ping
It is used to verify whether the connection between IFMI and the device of destination
IP address is normal. It is the same as the PING command in command input window.
II. Defining Trace Parameters
Double click the Ping node in the interface trace navigation tree, and the [Ping Trace]
Figure 5-3 Defining ping trace parameters
Table 5-1 describes the usage and range of value for the parameters used in
Figure 5-2.
Table 5-1 Description of Ping trace parameters
Parameter Default
Parameter description Range of value
name value
Module The IFMI module number
IFMI module number (mandatory parameter) NA
number defined in the system
Destination
Mandatory parameter Any valid IP address NA
IP address
5-3
Parameter Default
name value
Ping count Number of packets sent by the ping command 05000 4
Ping data
The ICMP response packet size (in bytes) 204096 56
size
Ping time The ICMP response timeout duration (in
030000 2000
out millisecond)
Defines whether the trace results are
automatically saved in the folder trace under
Auto save the SoftX3000 installation folder. The file name Not
Selected/Not selected
to file includes date, time, and trace message type. selected
You can read the trace results with the Trace
Viewer tool.
III. Viewing Trace Results
After defining the parameters, click <OK>, and the ping results are displayed in the
trace result window. Figure 5-4 shows the ping results of a normal connection. ICMP
is disabled in the connection network.
Figure 5-4 Ping result display window
Figure 5-4 lists the sequence number, packet size, time delay of the reply message,
and ping statistics, including packet sent, received, and lost.
Note:
Refer to RFC 792 Internet Control Message Protocol for detailed descriptions of ICMP.
IV. Processing Trace Results
In Figure 5-4, right click the results, and you can process the trace results. Refer to
section 5.5.1 Processing Trace Results.
5-4
5.2.3 Tracing with Trace Route
I. Overview of Tracing Using Trace Route
The tracing with trace route detects the route connection from the IFMI to the
destination IP address.
Double click the Trace Route node in the interface trace navigation tree, and the
[Trace Route] dialog box is displayed as shown in Figure 5-5.
Figure 5-5 Defining Trace Route trace parameters
Figure 5-5.
Table 5-2 Description of Tracert trace parameters
Parameter Default
name value
The IFMI module
Module
IFMI module number (mandatory parameter) number defined in the NA
number
system
5-5
Parameter Default
name value
Destination
Mandatory parameter Any valid IP address NA
IP address
Probe count Probe count of each time to live (TTL) value 010 3
Trace max
Size of ping packet (in bytes) 050 30
hops
Trace route
Ping timeout duration (in milliseconds) 030000 2000
time out
When you select it, you can specify the task
start time and end time of the trace task. Not
Time Selected/Not selected
When you leave it unselected, the system will selected
start the trace task immediately.
Half hour
Defines the start time and end time of the starting
Start/End In format of
trace task. They are valid when the [Time] from the
time [1978-1-1,2038-1-18]
option is selected. current
time
Auto save to the SoftX3000 installation folder. The file Not
file name includes date, time, and trace message selected
type. You can read the trace results can be
with the Trace Viewer tool.
After defining the parameters, click <OK>, and the Tracert results are displayed in the
trace result window. Figure 5-6 lists a typical example of Tracert trace results.
Figure 5-6 Tracert result display window
Figure 5-6 displays the return time from each router and each hop.
Note:
Tracert determines the path to the destination by sending the ICMP response request with the increased
TTL value. Refer to RFC 792 Internet Control Message Protocol for detailed descriptions of ICMP.
5-6
5.2.4 Tracing MGCP Messages
I. Overview of Tracing MRC Messages
This node helps you trace the MGCP messages in the SoftX3000 or between a
softswitch and a media gateway.
Double click the MGCP node in the interface trace navigation tree, and the [MGCP
Message Trace] dialog box is displayed as shown in Figure 5-7.
5-7
Figure 5-7 Defining MGCP message trace parameters
Figure 5-7.
Table 5-3 Description of MGCP message trace parameters
Parameter Default
name value
Trace specific When not selected, messages of all equipment IDs
Selected/Not selected Selected
equipment ID will be traced.
5-8
Parameter Default
name value
A valid device ID string. For
Must be specified when [Trace specific equipment
Equipment ID instance, NA
ID] is selected.
iad108.1b01.com.
It is the port number corresponding to the telephone
Termination ID number in the media gateway. It must be specified 099999999 NA
when [Trace specific equipment ID] is selected.
Defines whether the trace results are automatically
saved in the folder trace under the SoftX3000
Not
Auto save to file installation folder. The file name includes date, time, Selected/Not selected
selected
and trace message type. You can read the trace
results can be with the Trace Viewer tool.
When you select it, you can specify the task start
time and end time of the trace task. When you leave Not
it unselected, the system will start the trace task selected
immediately.
Half hour
Defines the start time and end time of the trace task. In format of starting
Start/End time
They are valid when the [Time] option is selected. [1978-1-1,2038-1-18] from the
current time
After defining the parameters, click <OK>, and the MGCP message trace results are
displayed in the trace result window. Figure 5-8lists a typical example of MGCP trace
results.
5-9
Figure 5-8 MGCP trace result display window
Figure 5-8 lists the MGCP message sent between the SoftX3000 and the media
gateway. Double click any message, and the content is displayed. For instance,
double click the second NTFY message, and a dialog box is displayed as shown in
Figure 5-9. It displays the content of the NTFY message, including the called number
2803102 sent from the media gateway.
5-10
Figure 5-9 MGCP message content
Note:
For detailed description of MGCP, refer to SoftX3000 SoftSwitch System Technical Manual-Signaling &
Protocols.
5.2.5 Tracing H.248 Messages
This node helps you trace the H.248 messages in the SoftX3000 or between a
softswitch and a media gateway.
Double click the H248 node in the interface trace navigation tree, and the [H248
5-11
Figure 5-10 Defining H.248 message trace parameters
Figure 5-10.
Table 5-4 Description of H.248 message trace parameters
Parameter Default
name value
Specific
When not selected, messages of all
equipment Selected/Not selected Selected
equipment IDs will be traced.
ID
A valid device ID string.
Equipment Must be specified when [Trace specific
For instance, NA
ID equipment ID] is selected.
2.22.42.110:2944.
5-12
Parameter Default
name value
It is the port number corresponding to the
Termination telephone number in the media gateway. It
099999999 NA
ID must be specified when [Trace specific
equipment ID] is selected.
automatically saved in the folder trace
Auto save to under the SoftX3000 installation folder. The Not
file file name includes date, time, and trace selected
message type. You can read the trace results
can be with the Trace Viewer tool.
start time and end time of the trace task. Not
When you leave it unselected, the system will selected
start the trace task immediately.
Half hour
time [1978-1-1,2038-1-18]
time
After defining the parameters, click <OK>, and the H.248 message trace results are
displayed in the trace result window. Figure 5-11 lists a typical example of H.248 trace
results.
Figure 5-11 H.248 trace result display window
5-13
Figure 5-11 lists the H.248 message sent between the SoftX3000 and the media
gateway. Double click any message, and the content is displayed. For instance,
double click the second NTFY_REQ message, and a dialog box is displayed as
shown in Figure 5-11. It displays the content of the NTFY_REQ message, including
the called number 2803102 sent from the media gateway.
Figure 5-12 H.248 message content
Note:
For detailed description of H.248, refer to SoftX3000 SoftSwitch System Technical Manual-Signaling &
Protocols.
section5.5.1 Processing Trace Results.
5-14
5.2.6 Tracing MRC Messages
This node helps you trace the message interaction process between the MRCI board
in the SoftX3000 and a media gateway.
Double click the MRC node in the interface trace navigation tree, and the [MRC
Figure 5-13 Defining MRC message trace parameters
Table 5-5describes the usage and range of value for the parameters used in Figure
5-13.
Table 5-5 Description of MRC message trace parameters
Parameter Range of
Parameter description Default value
name value
Remote IP Any valid IP
IP address of gateway, mandatory parameter. NA
address address
time and end time of the trace task. When you Selected/Not
Time Not selected
leave it unselected, the system will start the trace selected
task immediately.
Defines the start time and end time of the trace In format of Half hour
Start/End
task. They are valid when the [Time] option is [1978-1-1,203 starting from
time
selected. 8-1-18] the current time
5-15
Parameter Range of
Parameter description Default value
name value
automatically saved in the folder trace under the
Auto save to SoftX3000 installation folder. The file name Selected/Not
Not selected
file includes date, time, and trace message type. You selected
can read the trace results can be with the Trace
Viewer tool.
After defining the parameters, click <OK>, and the message interaction process
between MRC and gateway is displayed in the trace result window. For example, if a
number dialed by a subscriber in the gateway with the IP address of 2.29.200.191 is
an unallocated number, the MRC trace result is shown in Figure 5-14
Figure 5-14 MRC trace result display window
Figure 5-14 shows the response messages of the MRCI board, such as messages for
establishing a link (CRCX), opening a channel, and playing an announcement.
Among the messages, the request notification message RQNT contains the voice file
name, that is, HWF001000B.chi in the fifth message in Figure 5-4.
5.2.7 Tracing SIP Messages
I. Overview of Tracing SIP Messages
This node helps you trace the SIP messages in the SoftX3000 or between a
softswitch and a device.
Double click the SIP node in the interface trace navigation tree, and the [SIP
5-16
Figure 5-15 Defining SIP message trace parameters
Figure 5-15.
Table 5-6 Description of SIP message trace parameters
Parameter Default
name value
IP address of a SIP device that is to be
IP address Valid IP address NA
traced and is connected to the SoftX3000.
Message filter string. For example, if
2803108 is entered, only messages String with less than
Filter string NA
containing 2803108 will be traced and 27 characters
displayed.
Incoming Selected/Not
Whether to trace received messages Selected
message selected
Outgoing Selected/Not
Whether to trace sent messages Selected
message selected

start time and end time of the trace task. Selected/Not
Time Not selected
When you leave it unselected, the system selected
will start the trace task immediately.
Half hour
Defines the start time and end time of the
Start/End In format of starting from
trace task. They are valid when the [Time]
time [1978-1-1,2038-1-18] the current
option is selected.
time
5-17
Parameter Default
name value
Auto save to under the SoftX3000 installation folder. The Selected/Not
Not selected
message type. You can read the trace
After defining the parameters, click <OK>, and the SIP message trace results are
displayed in the trace result window. Figure 5-16 lists a typical example of trace
results for a SIP subscriber calling a voice subscriber.
Figure 5-16 SIP trace result display window
Figure 5-16 lists the SIP message sent between the SoftX3000 and the SIP device.
Double click any message, and the content is displayed. For instance, double click the
INVITE message, and a dialog box is displayed as shown in Figure 5-17. It displays
the content of the INVITE message, including the called number 2801000.
5-18
Figure 5-17 SIP message content
Note:
For detailed description of SIP, refer to SoftX3000 SoftSwitch System Technical Manual-Signaling &
Protocols.
5.2.8 Tracing H.323 Messages
I. Overview of Tracing H.323 Messages
This node helps you trace the H.323 messages in the SoftX3000 or between a
softswitch and a H.323 terminal.
Double click the H.323 node in the interface trace navigation tree, and the [H323
5-19
Figure 5-18 Defining H.323 message trace parameters
Figure 5-18.
Table 5-7 Description of H.323 message trace parameters
Parameter
Parameter description Range of value Default value
name
IP address of the H.323 user terminal to be
IP address Valid IP address NA
traced.
start time and end time of the trace task. When Selected/Not
Time Not selected
you leave it unselected, the system will start selected
the trace task immediately.
Half hour
Defines the start time and end time of the trace In format of
Start/End starting from
task. They are valid when the [Time] option is [1978-1-1,2038-1
time the current
selected. -18]
time
Auto save to the SoftX3000 installation folder. The file name Selected/Not
Not selected
file includes date, time, and trace message type. selected
You can read the trace results can be with the
Trace Viewer tool.
After defining the parameters, click <OK>, and the H.323 message trace results are
displayed in the trace result window. Figure 5-19 lists a typical example of trace
results for an H.323 subscriber calling other subscribers (quick start).
5-20
Figure 5-19 H.323 trace result display window
Figure 5-19 lists the H.323 message sent between the SoftX3000 and the H.323
terminal. Double click any message, and the content is displayed. For instance,
double click the RAS_ARQ message, and a dialog box is displayed as shown in
Figure 5-20. It displays the content of the RAS_ARQ message, including the called
number 2802000.
Figure 5-20 H.323 message content
Note:
For detailed description of H.323, refer to SoftX3000 SoftSwitch System Technical Manual-Signaling &
Protocols.
5-21
5.2.9 Tracing SCTP Messages
I. Overview of Tracing SCTP Messages
This node helps you trace the SCTP messages between the SoftX3000 and a
signaling gateway.
Double click the SCTP node in the interface trace navigation tree, and the [SCTP
Figure 5-21 Defining SCTP message trace parameters
Figure 5-21.
5-22
Table 5-8 Description of SCTP message trace parameters
Parameter Default
name value
The BSG module
Module BSG module number processing SCTP,
number defined in the NA
number mandatory parameter.
system
SCTP
Selected/Not
control Whether to trace SCTP control messages. Selected
selected
message
Whether to trace SCTP data messages.
Tracing all data messages will lead to large
SCTP data amounts of data being transmitted, which Selected/Not Not
message affects system performance. After you choose selected selected
this option, the system will ask if you want to
continue. You can click <Yes> to confirm.
Local IP For SCTP association, such as
Any valid IP address
address/ M2UA/M3UA/V5UA/IUA links, in the NA
and port number
Local port SoftX3000.
Peer IP For SCTP association, such as
Any valid IP address
address/ M2UA/M3UA/V5UA/IUA links, on the signaling NA
and port number
Peer port gateway side.
start time and end time of the trace task. When Selected/Not Not
Time
you leave it unselected, the system will start selected selected
Half hour
Defines the start time and end time of the trace starting
task. They are valid when the [Time] option is from the
time [1978-1-1,2038-1-18]
selected. current
time
Auto save to the SoftX3000 installation folder. The file name Selected/Not Not
file includes date, time, and trace message type. selected selected
Trace Viewer tool.
After defining the parameters, click <OK>, and the SCTP message trace results are
displayed in the trace result window. Figure 5-22 shows the SCTP trace results for a
normal call connection process whose conversation lasts for about six seconds
(including the HEARTBEAT message generated in the non-call-connection process).
5-23
Figure 5-22 SCTP trace result display window
Figure 5-22 lists the SCTP message sent between the SoftX3000 and the signaling
gateway. Double click any message, and the dialog box for explaining this message is
displayed. For example, double click any message in Figure 5-22, and a dialog box is
displayed as shown in Figure 5-23. The dialog box contains a detailed explanation of
the SCTP message, including the type of the data chunk of the SCTP message, TSN,
stream sequence number (SSN), and payload protocol ID.
5-24
Figure 5-23 MGCP message content
Note:
For detailed description of SCTP, refer to SoftX3000 SoftSwitch System Technical Manual-Signaling &
Protocols.
5.2.10 Tracing M2UA Messages
I. Overview of Tracing M2UA Messages
This node helps you trace the M2UA messages of an M2UA link between the
SoftX3000 and a signaling gateway.
5-25
Double click the M2UA node in the interface trace navigation tree, and the [M2UA
Figure 5-24 Defining M2UA message trace parameters
Figure 5-24.
Table 5-9 Description of M2UA message trace parameters
Parameter Default
name value
Module BSG module number processing SCTP, The BSG module number
NA
number mandatory parameter. defined in the system
M2UA link The M2UA link number
M2UA link number NA
number defined in the system
M2UA
control Whether to trace M2UA control messages. Selected/Not selected Selected
message
5-26
Parameter Default
name value
Whether to trace M2UA data messages.
Tracing all data messages will lead to large
amounts of data being transmitted, which
M2UA data Not
affects system performance. After you Selected/Not selected
message selected
choose this option, the system will ask if you
want to continue. You can click <Yes> to
confirm.
MTP link number borne by the M2UA link. It
MPT link The MTP link number on Not
is valid when [M2UA data message] is
number the M2UA link selected
selected.
SCTP notify Notify message for whether to trace the
Selected/Not selected Selected
message SCTP layer
When you select it, you can specify the start
time and end time of the trace task. When Not
Half hour
time [1978-1-1,2038-1-18]
time
Auto save to under the SoftX3000 installation folder. The Not
After defining the parameters, click <OK>, and the M2UA message trace results are
displayed in the trace result window. Figure 5-25 shows the M2UA trace results for a
normal call connection process whose conversation lasts for about seven seconds.
Figure 5-25 M2UA trace result display window
Figure 5-25 lists the MTP2 User Adaptation (MAUP) message sent between the
SoftX3000 and the signaling gateway. Double click any message, and the dialog box
5-27
for explaining this message is displayed. For example, if you click the first MAUP
message in Figure 5-25, a dialog box is displayed as shown in Figure 5-26. This
dialog box contains the detailed content of the M2UA message; for example, in the
protocol data unit (PDU), you can find the caller number 07552803101 and callee
number 25000001 (displayed in BCD codes in the reverse order).
Figure 5-26 M2UA message content
Note:
For detailed description of M2UA, refer to SoftX3000 SoftSwitch System Technical Manual-Signaling &
Protocols.
5-28
5.2.11 Tracing M3UA Messages
I. Overview of Tracing M3UA Messages
This node helps you trace the M3UA messages of an M3UA link in the SoftX3000.
Double click the M3UA node in the interface trace navigation tree, and the [M3UA
Figure 5-27 Defining M3UA message trace parameters
5-29
Figure 5-27.
Table 5-10 Description of M3UA message trace parameters
Parameter Default
name value
Module BSGI module number processing M3UA, The defined BSGI
NA
number mandatory parameter. module number
M3UA link number to be traced, which can be The M3UA link
M3UA link
queried by using the LST M3LNK command. number defined in NA
number
Mandatory parameter. the system
You can specify the tracing of the following
message types related to M3UA:
Related z SCCP message
TUP message Selected/Not
message z Selected
ISUP message selected
types z
z BICC message
z M3UA message
z SCTP notify message
You can specify the tracing of M3UA messages
with the following flags:
z NI flag: Network identification flag. You can
select an international or a national flag.
z OPC flag
z DPC flag
z H1 flag: Title H1 of signaling information field
(SIF) Selected/Not Not
Link flags
z H0 flag: Title H0 of signaling information field selected selected
(SIF)
z SLS flag: Title SLS of signaling information
field (SIF)
z CIC flag: Used to specify the CIC range of the
TUP/ISUP message field SIF
z Direction flag: M3UA message direction
(send/receive)
time and end time of the trace task. When you Selected/Not Not
Time
leave it unselected, the system will start the trace selected selected
task immediately.
Half hour
Defines the start time and end time of the trace In format of starting
Start/End
task. They are valid when the [Time] option is [1978-1-1,2038-1-1 from the
time
selected. 8] current
time
Auto save to SoftX3000 installation folder. The file name Selected/Not Not
file includes date, time, and trace message type. You selected selected
Viewer tool.
5-30
After defining the parameters, click <OK>, and the M3UA message trace results are
displayed in the trace result window. Figure 5-28shows the message trace results for
activating and deactivating an M3UA link.
Figure 5-28 M3UA trace result display window
Figure 5-28 shows the related information of the M3UA management messages
received or sent on the M3UA link in a call, including the Tick value for the generation
time of a message and the message type (H1H0). Such fields as NI, CIC, SLS/SLC,
OPC, and DPC are valid in M3UA call tracing. Double click any message, and the
dialog box for explaining this message is displayed. For example, if you click the third
message NOTIFY in Figure 5-28, a dialog box is displayed as shown in Figure 5-29.
The dialog box shows the details of this message; for example, [Notify Status Info] is
AS PENDING.
Figure 5-29 M3UA message content
5-31
Note:
For detailed description of M3UA, refer to SoftX3000 SoftSwitch System Technical Manual-Signaling &
Protocols.
5.2.12 Tracing V5UA Messages
I. Overview of Tracing V5UA Messages
This node helps you trace the V5UA messages of a V5UA link in the SoftX3000.
Double click the V5UA node in the interface trace navigation tree, and the [V5UA
Figure 5-30 Defining V5UA message trace parameters
Figure 5-30.
5-32
Table 5-11 Description of V5UA message trace parameters
Parameter Default
name value
Module BSGI module number processing V5UA, The defined BSGI
NA
V5UA link number to be traced, which can be
V5UA link The defined V5UA link
queried by using the LST V5UALNK NA
number number
command. Mandatory parameter.
V5UA control
Whether to trace V5UA control messages. Selected/Not selected Selected
message
V5UA data
Whether to trace V5UA data messages. Selected/Not selected Selected
message
V5UA
Whether to trace V5UA physical link layer
physical link Selected/Not selected Selected
messages.
message
SCTP notify
Whether to trace SCTP notify messages. Selected/Not selected Selected
message
After you select it, you can enter the V5 link Selected/Not selected
V5 link Not
identifier of the V5 interface E1 between the The defined V5 link
number selected
SoftX3000 and the SG. identifier
SG link After you select it, you can enter the E1 link Not
The defined E1 link
number identifier of the V5 interface on the SG side. selected
identifier
start time and end time of the trace task. When Not
Half hour
time [1978-1-1,2038-1-18]
selected. current
time
Auto save to the SoftX3000 installation folder. The file name Not
Trace Viewer tool.
After defining the parameters, click <OK>, and the V5UA message trace results are
displayed in the trace result window. Figure 5-31shows the trace results for
deactivating and activating a V5UA link.
5-33
Figure 5-31 V5UA trace result display window
Figure 5-31 shows the ASP service maintenance messages and layer management
messages in the process of deactivating/activating the V5UA link. Double click any
message, and the dialog box for explaining this message is displayed. For example, if
you double click the last NOTIFY layer management message, a dialog box is
displayed as shown in Figure 5-32. The dialog box shows the details of this message,
indicating that the ASP is active.
Figure 5-32 V5UA message content
Note:
For detailed description of V5UA, refer to SoftX3000 SoftSwitch System Technical Manual-Signaling &
Protocols.
5-34
5.2.13 Tracing IUA Messages
I. Overview of Tracing IUA Messages
This node helps you trace the IUA messages of an IUA link in the SoftX3000.
Double click the IUA node in the interface trace navigation tree, and the [IUA
Figure 5-33 Defining IUA message trace parameters
Table 5-12 describes the usage and range of value for the parameters used in Figure
5-33.
Table 5-12 Description of IUA message trace parameters
Parameter Default
name value
Module BSGI module number processing IUA, mandatory The defined BSGI
NA
number parameter. module number
IUA link number to be traced, which can be
IUA link
queried by using the LST IUALNK command. 065535 NA
number
Mandatory parameter.
5-35
Parameter Default
name value
IUA control Selected/Not
Whether to trace IUA control messages. Selected
message selected
IUA data Selected/Not
Whether to trace IUA data messages. Selected
message selected
SCTP notify Selected/Not
Whether to trace SCTP notify messages. Selected
message selected
Selected/Not
PRA link After you select it, you can enter the PRA Not
selected
number interface link number that supports the IUA link. selected
065534
Time
task immediately.
Half hour
Start/End
time
time
Viewer tool.
After defining the parameters, click <OK>, and the IUA message trace results are
displayed in the trace result window. Figure 5-34 shows the trace results for an IUA
call.
Figure 5-34 IUA trace result display window
5-36
Figure 5-34 lists the IUA message received or sent by the SoftX3000 on the IUA link.
Double click any message, and the content is displayed. For example, if you double
click the first QPTM DATA_IND message, a dialog box is displayed as shown in
Figure 5-35. The dialog box shows the content of this message, including the caller
number 307030001 and callee number 0754555100062 (displayed in hexadecimal
ASCII codes).
Figure 5-35 IUA message content
Note:
For detailed description of IUA, refer to SoftX3000 SoftSwitch System Technical Manual-Signaling &
Protocols.
5-37
5.2.14 Tracing MTP3 Messages
I. Overview of Tracing MTP3 Messages
This node helps you trace the MTP3 messages of an MTP3 link in the SoftX3000.
Double click the MTP3 node in the interface trace navigation tree, and the [MTP3
Figure 5-36 Defining MTP3 message trace parameters
5-38
5-36.
Table 5-13 Description of MTP3 trace parameters
Parameter Default
name value
Module BSGI module number processing MTP3, The defined BSGI
NA
MTP3 link number to be traced, which can be The MTP3 link
MTP3 link
queried by using the LST N7LNK command. number defined in NA
number
Mandatory parameter. the system
You can specify the tracing of the following
message types related to MTP3:
z SNM message
z SLT message
Message SCCP message Selected/Not
z Selected
types z TUP message selected
z ISUP message
z BICC message
z Unknown message
z Layer2 message
You can specify the tracing of MTP3 messages
with the following flags:
z NI flag: Network identification flag. You can
select an international or a national flag.
z OPC flag
z DPC flag
z H1 flag: Title H1 of signaling information field
(SIF) Selected/Not Not
Link flags
z H0 flag: Title H0 of signaling information field selected selected
(SIF)
z SLS flag: Title SLS of signaling information field
(SIF)
z CIC flag: Used to specify the CIC range of the
TUP/ISUP message field SIF
z Direction flag: MTP3 message direction
(send/receive)
Time
task immediately.
Half hour
Start/End
task. They are valid when the [Time] option is [1978-1-1,2038-1- from the
time
time
Defines whether the trace results are automatically
saved in the folder trace under the SoftX3000
Auto save to Selected/Not Not
installation folder. The file name includes date,
file selected selected
time, and trace message type. You can read the
trace results can be with the Trace Viewer tool.
5-39
After defining the parameters, click <OK>, and the MTP3 message trace results are
displayed in the trace result window. Figure 5-37 shows the trace results for an MTP3
call.
Figure 5-37 MTP3 trace result display window
Figure 5-37 lists the information of the ISUP messages received or sent by the
SoftX3000 on the MTP3 link, including NI, message type H1H0, CIC, SLS, OPC, and
DPC. Double click any message, and the dialog box for explaining this message is
displayed. For example, if you double click the first IAM message, a dialog box is
displayed as shown in Figure 5-38. The dialog box shows the details of this message,
including the caller number and callee number (the actual callee number is 25000001,
while the IADM and the subsequent SAM message contain all the callee number
information).
Figure 5-38 MTP3 message content
5-40
Note:
For detailed description of MTP3, refer to SoftX3000 SoftSwitch System Technical Manual-Signaling &
Protocols.
5.2.15 Tracing BRA Messages
I. Overview of Tracing BRA Messages
This node helps you trace the BRA interface signaling messages of a BRA subscriber
in the SoftX3000.
Double click the BRA node in the interface trace navigation tree, and the [BRA
Figure 5-39 Defining BRA message trace parameters
Figure 5-39.
5-41
Table 5-14 Description of BRA message trace parameters
Parameter Default
name value
The BRA subscriber
Subscriber BRA link number to be traced, which can be
number defined in NA
number queried by using the LST BRA command.
the system
The local DN set to
Local DN Set Local DN set which the BRA NA
subscriber belongs
Time
task immediately.
Half hour
Start/End
time
selected. ] current
time
Viewer tool.
After defining the parameters, click <OK>, and the BRA interface message trace
results are displayed in the trace result window. Figure 5-40 shows the trace results
for a normal call process of a BRA subscriber.
5-42
Figure 5-40 BRA trace result display window
Figure 5-40lists the information of the messages received or sent by the SoftX3000 on
the BRA subscriber interface, including message type, message name, and Tick
value. Double click any message, and the dialog box for explaining this message is
displayed. For example, double click the first Q.931 SETUP message, and a dialog
box is displayed as shown in Figure 5-41. It displays the content of the SETUP
message, including the address information of the caller and callee.
5-43
Figure 5-41 BRA message content
Note:
For detailed description of BRA, refer to SoftX3000 SoftSwitch System Technical Manual-Signaling &
Protocols.
5.2.16 Tracing PRA Messages
I. Overview of Tracing PRA Messages
This node helps you trace the PRA signaling messages of a PRA link number in the
SoftX3000.
Double click the PRA node in the interface trace navigation tree, and the [PRA
5-44
Figure 5-42 Defining PRA message trace parameters
5-42.
Table 5-15 Description of PRA message trace parameters
Parameter Default
name value
PRA link PRA link number to be traced, which can be
065535 NA
number queried by using the LST PRALNK command.
Time
task immediately.
Half hour
Start/End
time
time
Viewer tool.
After defining the parameters, click <OK>, and the PRA message trace results are
displayed in the trace result window. Figure 5-43 shows the trace results for a PRA
call.
5-45
Figure 5-43 PRA trace result display window
Figure 5-43 lists the PRA message sent received or sent by the SoftX3000 on the
PRA link. Double click any message, and the content is displayed. For example, if you
double click the first Q.931 SETUP message, a dialog box is displayed as shown in
Figure 5-44. The dialog box shows the content of the SETUP message, including the
caller number 307030001 and callee number 0754555100062 (both are displayed in
hexadecimal ASCII codes).
5-46
Figure 5-44 PRA message content
Note:
For detailed description of PRA, refer to SoftX3000 SoftSwitch System Technical Manual-Signaling &
Protocols.
5.2.17 Tracing V5 Messages
I. Overview of Tracing V5 Messages
This node helps you trace the V5 messages of a V5 interface in the SoftX3000.
Double click the V5 node in the interface trace navigation tree, and the [V5 Message
Trace] dialog box is displayed as shown in Figure 5-45.
5-47
Figure 5-45 Defining V5 message trace parameters
Figure 5-45.
Table 5-16 Description of V5 message trace parameters
Parameter Default
name value
The V5 interface ID
V5 interface V5 interface ID to be traced, which can be queried
defined in the NA
ID by using the LST V5I command.
system
Selected/Not
C-channel When you select it, you can enter the C-channel Not
selected
number number of the V5 interface. selected
065534
Selected/Not
V5 L3 When you select it, you can enter the V5 L3 Not
selected
address address in the V5 interface. selected
065535
PSTN Whether to trace the PSTN protocol borne on the Selected/Not
Selected
protocol physical channel C in the V5 interface. selected
Whether to trace the bearer channel connection
BCC Selected/Not
(BCC) protocol borne on the physical channel C Selected
protocol selected
in the V5 interface.
5-48
Parameter Default
name value
Link control Whether to trace the link control protocol borne on Selected/Not
Selected
protocol the physical channel C in the V5 interface. selected
Protect Whether to trace the protect protocol borne on the Selected/Not
Selected
Control Whether to trace the control protocol borne on the Selected/Not
Selected
Time
task immediately.
Half hour
Start/End
task. They are valid when the [Time] option is [1978-1-1,2038-1- from the
time
time
Viewer tool.
After defining the parameters, click <OK>, and the V5 message trace results are
displayed in the trace result window. Figure 5-46 shows the trace results for a V5 call.
Figure 5-46 V5 trace result display window
Figure 5-46 lists the PSTN/BCC messages borne by the SoftX3000 on the V5
interface. Double click any message, and the dialog box for explaining this message
is displayed. For example, if you double click the first V5_ESTABLISH message, a
dialog box is displayed as shown in Figure 5-47 The dialog box shows the content of
this message, including 256 for [L3 address] and Offhook for [Steady signal type].
5-49
Figure 5-47 V5 message content
Note:
For detailed description of V5, refer to SoftX3000 SoftSwitch System Technical Manual-Signaling &
Protocols.
5.2.18 Tracing SCCP DPC Messages
I. Overview of Tracing SCCP DPC Messages
This node helps you trace the SCCP DPC messages sent between the SoftX3000
and a device with a specified DPC.
Double click the SCCP DPC node in the interface trace navigation tree, and the
[SCCP DPC Message Trace] dialog box is displayed as shown in Figure 5-48.
5-50
Figure 5-48 Defining SCCP DPC message trace parameters
5-48.
Table 5-17 Description of SCCP DPC message trace parameters
Parameter Default
name value
The FCCU module
Module FCCU board module number processing
number defined in the NA
number SCCP, optional parameter.
system
There are four options:
international network,
Network Used to specify in which signaling network the international standby National
indicator signaling code to be traced is to be located. network, national network
network, and national
standby network.
Used to specify the DPC of the SCCP The defined SCCP
DPC NA
message to be traced. Mandatory parameter. DPC
Used to specify the OPC of the SCCP The defined SCCP
OPC NA
message to be traced. Mandatory parameter. OPC
5-51
Parameter Default
name value
Half hour
time [1978-1-1,2038-1-18]
selected. current
time

Trace Viewer tool.
After defining the parameters, click <OK>, and the SCCP message trace results are
displayed in the trace result window. Figure 5-49 shows the SCCP trace results for a
normal intelligent network (IN) call connection process.
Figure 5-49 SCCP DPC trace result display window
Figure 5-49 lists the SCCP messages received or sent by the FCCU board. Double
click any message, and the dialog box for explaining this message is displayed. For
example, if you double click a message, a dialog box is displayed as shown in Figure
5-50. The dialog box shows the content of this message, including the signaling link
select code, original point code, destination point code, and TCAP message data.
5-52
Figure 5-50 SCCP DPC message content
Note:
For detailed description of SCCP, refer to SoftX3000 SoftSwitch System Technical Manual-Signaling &
Protocols.
5.2.19 Tracing SCCP User Messages
I. Overview of Tracing SCCP User Messages
This node helps you trace the messages received and sent by the SoftX3000
between SCCP and upper user layers (such as TCAP/INAP).
Double click the SCCP User node in the interface trace navigation tree, and the
[SCCP User Message Trace] dialog box is displayed as shown in Figure 5-51.
5-53
Figure 5-51 Defining SCCP User message trace parameters
Figure 5-51.
Table 5-18 Description of SCCP User trace parameters
Parameter Default
name value
The FCCU module
Module FCCU board module number processing SCCP,
number optional parameter.
the system
Time
task immediately.
Half hour
Start/End
time
time
Viewer tool.
After defining the parameters, click <OK>, and the SCCP message trace results are
displayed in the trace result window. Figure 5-52 shows the SCCP trace results for a
normal IN call connection process.
5-54
Figure 5-52 SCCP User trace result display window
Figure 5-52 lists the SCCP messages received or sent by the SoftX3000 between
SCCP and user layers. Double click any message, and the dialog box for explaining
this message is displayed. For example, if you double click a message, a dialog box is
displayed as shown in Figure 5-53. The dialog box shows the content of this message,
including the message type, direction, network indication, and TCAP message data.
5-55
Figure 5-53 SCCP User message content
Note:
Protocols.
5.2.20 Tracing SCCP MTP Messages
I. Overview of Tracing SCCP MTP Messages
This node helps you trace the signaling interaction between the SCCP processing
module and the lower-layer MTP maintenance management messages.
Double click the SCCP MTP node in the interface trace navigation tree, and the
[SCCP MTP Message Trace] dialog box is displayed as shown in Figure 5-54.
5-56
Figure 5-54 Defining SCCP MTP message trace parameters
Figure 5-54.
Table 5-19 Description of SCCP MTP message trace parameters
Parameter Default
name value
The FCCU module
Module FCCU board module number processing SCCP,
the system
Time
task immediately.
Half hour
Start/End
time
time
Viewer tool.
After defining the parameters, click <OK>, and the SCCP MTP message trace results
are displayed in the trace result window. Figure 5-55 shows the message trace results
for deactivating and activating an MTP link.
5-57
Figure 5-55 SCCP MTP trace result display window
Figure 5-55 lists the SCCP messages received by the SCCP processing module from
the MTP layer. Double click any message, and the dialog box for explaining this
message is displayed. For example, if you double click the first MTP_PAUSE_IND
message, a dialog box is displayed as shown in Figure 5-55. The dialog box shows
the content of this message, including the network indication, DPC, and OPC.
Figure 5-56 SCCP MTP message content
Note:
Protocols.
5-58
5.2.21 Tracing TCAP SCCP Messages
I. Overview of Tracing TCAP SCCP Messages
between TCAP and lower SCCP layer.
Double click the TCAP SCCP node in the interface trace navigation tree, and the
[TCAP SCCP Message Trace] dialog box is displayed as shown in Figure 5-51.
Figure 5-57 Defining TCAP SCCP message trace parameters
5-51.
Table 5-20 Description of TCAP SCCP message trace parameters
Parameter Default
name value
The FCCU module
Module FCCU board module number processing
number TCAP/SCCP, optional parameter.
the system
Time
task immediately.
Half hour
Start/End
time
time
5-59
Parameter Default
name value
Auto save to automatically saved in the folder trace under the Selected/Not Not
file SoftX3000 installation folder. The file name selected selected
includes date, time, and trace message type.
After defining the parameters, click <OK>, and the TCAP SCCP message trace
results are displayed in the trace result window on the right. Figure 5-58 shows the
TCAP SCCP trace results for a normal IN call connection process.
Figure 5-58 TCAP SCCP trace result display window
Figure 5-52 lists the TCAP SCCP messages received or sent by the SoftX3000
between TCAP and SCCP. Double click any message, and the dialog box for
explaining this message is displayed. For example, if you double click a message, a
dialog box is displayed as shown in Figure 5-59. The dialog box shows the content of
this message.
5-60
Figure 5-59 TCAP SCCP message content
Note:
For detailed description of TCAP, refer to SoftX3000 SoftSwitch System Technical Manual-Signaling &
Protocols.
5.2.22 Tracing TCAP User Messages
I. Overview of Tracing TCAP User Messages
between TCAP and upper user layers (such as INAP).
Double click the TCAP User node in the interface trace navigation tree, and the
[TCAP User Message Trace] dialog box is displayed as shown in Figure 5-60.
5-61
Figure 5-60 Defining TCAP User message trace parameters
Figure 5-60.
Table 5-21 Description of TCAP User trace parameters
Parameter Default
name value
The FCCU module
Module FCCU board module number processing TCAP,
the system
Time
leave it unselected, the system will start the selected selected
trace task immediately.
Half hour
time [1978-1-1,2038-1-18]
selected. current
time
Auto save to the SoftX3000 installation folder. The file name Selected/Not Not
file includes date, time, and trace message type. selected selected
Trace Viewer tool.
After defining the parameters, click <OK>, and the TCAP message trace results are
displayed in the trace result window. Figure 5-52 shows the TCAP User trace results
for a normal IN call connection process (including the input of the card number and
password).
5-62
Figure 5-61 TCAP User trace result display window
Figure 5-61lists the TCAP User messages received or sent by the SoftX3000 between
TCAP and INAP. Double click any message, and the dialog box for explaining this
message is displayed. For example, if you double click the first TC_INVOKE_REQ
message, a dialog box is displayed as shown in Figure 5-62. The dialog box shows
the content of this message, including the caller number 0755201455550005 and
callee number (200#, displayed as 200C in the figure).
5-63
Figure 5-62 TCAP User message content
Note:
For detailed description of TCAP, refer to SoftX3000 SoftSwitch System Technical Manual-Signaling &
Protocols.
5.2.23 Tracing CSP Messages
I. Overview of Tracing CSP Messages
This node helps you trace the INAP message stream between the built-in IN service
module of the SoftX3000 and the CSP.
5-64
Double click the CSP node in the interface trace navigation tree, and the [CSP
Figure 5-63 Defining CSP message trace parameters
Figure 5-63.
Table 5-22 Description of CSP message trace parameters
Parameter Default
name value
The FCCU/FCSU or
It processes the FCCU/FCSU or CDB module
Module CDBI module
numbers of the built-in IN service. Optional NA
number numbers defined in
parameter.
the system
The defined built-in

Service key Service key of the built-in IN service NA
IN service key
Time
task immediately.
Half hour
Start/End
time
time
5-65
Parameter Default
name value
Viewer tool.
After defining the parameters, click <OK>, and the CSP message trace results are
displayed in the trace result window. Figure 5-64 shows the CSP trace results for a
normal super do-not-disturb call connection process.
Figure 5-64 CSP trace result display window
Figure 5-64 lists the IANP messages between the built-in IN service module and the
CSP in a super do-not-disturb call process. Double click any message, and the dialog
box for explaining this message is displayed. For example, if you double click the first
IA_initialDP message, a dialog box is displayed as shown in Figure 5-65. The dialog
box shows the content of this message, including the caller number (201520000101)
and callee number (190201520000001, in which 190 is the prefix of the super
do-not-disturb service).
5-66
Figure 5-65 CSP message content
Note:
For detailed description of CSP, refer to SoftX3000 SoftSwitch System Technical Manual-Signaling &
Protocols.
5.2.24 Tracing Bill Messages
I. Overview of Tracing Bill Messages
This node helps you trace the bills of a subscriber number or trunk group in the
SoftX3000.
5-67
Double click the Bill node in the interface trace navigation tree, and the [Bill message
trace] dialog box is displayed as shown in Figure 5-66.
Figure 5-66 Defining Bill message trace parameters
Figure 5-66.
Table 5-23 Description of Bill message trace parameters
Default
Trace type Parameter name Parameter description Range of value
value
A number
Subscriber
Caller number to be traced. already existing NA
number
in the system
Caller
The DN set to
Local DN set of the caller
Local DN set which the caller NA
number to be traced.
number belongs
A number
Subscriber
Callee Callee number to be traced. already existing NA
number
in the system
(valid in the callee
group charging The DN set to
mode) Local DN set of the callee
Local DN set which the callee NA
number to be traced.
number belongs
The trunk group
number that has
been configured
Trunk group Trunk group Trunk group number NA
with charging
data in the
system
5-68
Default
Trace type Parameter name Parameter description Range of value
value
When you select it, you can
specify the task start time
and end time of the trace
Selected/Not Not
Time task. When you leave it
selected selected
unselected, the system will
start the trace task
immediately.
Half
Defines the start time and hour
In format of
end time of the trace task. starting
Start/End time [1978-1-1,2038-
They are valid when the from the
1-18]
[Time] option is selected. current
time
Defines whether the trace

results are automatically
saved in the folder trace
under the SoftX3000
installation folder. The file Selected/Not Not
Auto save to file
name includes date, time, selected selected
and trace message type.
You can read the trace
results can be with the
Trace Viewer tool.
After defining the parameters, click <OK>, and the IUA message trace results are
displayed in the trace result window. Figure 5-67 lists the Bill trace results for two calls
of a caller.
Figure 5-67 Bill trace result display window
For example, if you double click a message, a dialog box is displayed as shown in
Figure 5-68. The dialog box shows the content of this message, including the call
duration of the bill (71179 Ticks, that is, 711790 milliseconds, which is about 11
minutes 52 seconds), caller number (07552803101), and callee number
(02125000001).
5-69
Figure 5-68 Bill message content
5.2.25 Tracing Circuit Messages
I. Overview of Tracing Circuit Messages
This node helps you trace the Circuit messages of an ISUP/TUP circuit in the
SoftX3000.
Double click the Circuit node in the interface trace navigation tree, and the [Circuit
5-70
Figure 5-69 Defining Circuit message trace parameters
Figure 5-69.
Table 5-24 Description of Circuit trace parameters
Parameter Default
name value
Module FCCU board module number to which the circuit The defined FCCU
NA
number belongs. module number
Device type Circuit device type, which can be ISUP or TUP. ISUP or TUP NA
The ISUP/TUP trunk
Circuit Circuit number, which can be queried by using the
circuit defined in the NA
number LST TKC command.
system
Time
task immediately.
Half hour
Start/End
time
time
Viewer tool.
5-71
After defining the parameters, click <OK>, and the corresponding circuit message
trace results are displayed in the trace result window. Figure 5-70 shows the trace
results for an ISUP call.
Figure 5-70 Circuit trace result display window
Figure 5-70 lists the ISUP messages received or sent by the SoftX3000 on a circuit.
Double click any message, and the content is displayed. For example, if you double
click the first IAM message, a dialog box is displayed as shown in Figure 5-71. The
dialog box shows the content of this message, including the information of the caller
and callee (25000001).
Figure 5-71 Circuit trace message content
5-72
Note:
For detailed description of ISUP, refer to SoftX3000 SoftSwitch System Technical Manual-Signaling &
Protocols.
5.2.26 Tracing Console Messages
I. Overview of Tracing Console Messages
This node helps you trace the protocol interaction between the SoftX3000 and the IP
Centrex console (U-Path).
Double click the Console node in the interface trace navigation tree, and the
[Console Message Trace] dialog box is displayed as shown in Figure 5-72.
Figure 5-72 Defining Console trace parameters
5-73
Figure 5-72.
Table 5-25 Description of Console trace parameters
Parameter Default
Trace type Parameter description Range of value
name value
A subscriber
Subscriber Subscriber number of the
number of a NA
number console to be traced.
defined console
By subscriber The DN set to
number Local DN set to which a which the
Local DN set subscriber number of a subscriber NA
console to be traced belongs. number of the
console belongs
A subscriber
By console Console Number of the console to be number already
NA
number number traced. existing in the
system
Whether to export shake hand Selected/Not Not
Output shake hand messages
messages. selected selected
Whether to export confirm Selected/Not Not
Output confirm messages
messages. selected selected
When you select it, you can
specify the task start time and
end time of the trace task. Selected/Not Not
Time
When you leave it unselected, selected selected
the system will start the trace
task immediately.
Half hour
Defines the start time and end
In format of starting
time of the trace task. They
Start/End time [1978-1-1,2038-1 from the
are valid when the [Time]
-18] current
option is selected.
time
Defines whether the trace
results are automatically
saved in the folder trace
under the SoftX3000
Selected/Not Not
Auto save to file installation folder. The file
selected selected
name includes date, time, and
trace message type. You can
read the trace results can be
with the Trace Viewer tool.
After defining the parameters, click <OK>, and the Console message trace results are
displayed in the trace result window. Figure 5-73 shows the trace results for
5-74
operations on the console, including setting it busy, maintaining subscriber data,

maintaining the long-short number comparison table, and exiting.
Figure 5-73 Console trace result display window
5.2.27 Tracing STUN Messages
I. Overview of Tracing STUN Messages
This node helps you trace the STUN interaction of a device with a specified IP
address and port number in the SoftX3000.
Double click the STUN node in the interface trace navigation tree, and the [STUN
5-75
Figure 5-74 Defining STUN message trace parameters
Figure 5-74.
Table 5-26 Description of STUN message trace parameters
Parameter Default
name value
IP address of the STUN device to be traced.
An existing IP address
IP address The STUN device can be a STUN server NA
of the device
(SoftX3000) or STUN client (U-Path).
Port number of the STUN device. The STUN
The defined STUN port
Port number port of the SoftX3000 can be queried by using NA
number
the LST STUNDISP command.
Half hour
time [1978-1-1,2038-1-18]
selected. current
time
Trace Viewer tool.
5-76
After defining the parameters, click <OK>, and the STUN message trace results are
displayed in the trace result window. Figure 5-75 shows the trace results for STUN
interaction in the process of logging in to the console.
Figure 5-75 STUN trace result display window
Figure 5-75 shows the STUN interaction between the IFMI board and the console in
the process of logging in to the console. 2.22.2.100 is the IP address of the FE
interface of the IFMI board, and 2.29.200.109 is the IP address of the console.
Note:
For details on STUN, refer to Simple Traversal of UDP Through Network Address Translators (STUN)
in the IETF recommendation draft-ietf-sigtran-m2pa-06.
5.3 Tracing User Signaling

5.3.1 Overview of User Trace Tasks
Expand the user trace task node, and the user trace tasks are shown in Figure 5-76.
5-77
Figure 5-76 Navigation tree of user trace tasks
5.3.2 Tracing Interface Signaling
I. Overview of Tracing Interface Signaling
It helps you trace the interface signaling messages of certain subscribers in the
SoftX3000.
Double click the Interface Signaling Trace node in the interface trace navigation tree,
and the [Trace Signaling Trace] dialog box is displayed as shown in Figure 5-77.
Figure 5-77 Defining parameters for tracing user interface signaling
5-78
Figure 5-77.
Table 5-27 Description of parameters for tracing user interface signaling
Parameter
name
You can select By subscriber number or subscriber number By subscriber
Trace type
MID + UID + PSN. or MID + UID + PSN number
Relative trace Whether to trace relative messages YES or NO YES
Subscriber number
Subscriber This parameter is valid when the trace type
configured in the NA
number is By subscriber number.
system
DN set of the
This parameter is valid when the trace type
Local DN set configured NA
is By subscriber number.
subscriber
Module number of
Module This parameter is valid when the trace type
the configured NA
number is MID + UID + PSN.
subscriber
UID_WIRED/UID_
ETS/UID_PRA/UID
This parameter is valid when the trace type _TCI/UID_ESL/UID
User type UID_WIRED
is MID + UID + PSN. _SIPSL/UID_H323
SL/UID_BRA/UID_
R2
Number of the
Equipment This parameter is valid when the trace type
configured NA
number is MID+UID+PSN.
equipment
ISUP, SIP, CAP,
Combination This parameter is mandatory. INAP, PRA, BRA, NA
R2
start time and end time of the trace task. Selected/Not
Time Not selected
When you leave it unselected, the system selected
will start the trace task immediately.
Half hour
Defines the start time and end time of the In format of
starting from
Start/End time trace task. They are valid when the [Time] [1978-1-1,2038-1-1
the current
option is selected. 8]
time
Auto save to under the SoftX3000 installation folder. The Selected/Not
Not selected
5-79
After defining the parameters, click <OK>, and the user interface trace results are
displayed in the trace result window. Figure 5-78displays an example of interface
trace results on a normal ISUP call.
Figure 5-78 Display window of interface signaling trace results
In Figure 5-78, the red messages are messages interacting in the SoftX3000, and the
blue and black ones are messages interacting with external network components.
Double click the first IAM message in Figure 5-78, and the detailed explanations of the
message is displayed in Figure 5-79, including the callee number 6660017.
5-80
Figure 5-79 Detailed explanations of an interface trace message
Note:
For detailed description of ISUP, refer to SoftX3000 SoftSwitch System Technical Manual-Signaling &
Protocols.
section 5.5 Exporting and Reviewing Trace Results for details.
5.3.3 Tracing Call Connections
I. Overview of Tracing Call Connections
It helps you trace the call connection process of certain subscribers in the SoftX3000.
Double click the Call Connection Trace node in the interface trace navigation tree,
and the [Call Connection Trace] dialog box is displayed as shown in Figure 5-80.
5-81
Figure 5-80 Defining parameters for tracing call connections
Figure 5-80.
Table 5-28 Description of parameters for tracing call connections
Parameter
name
You can select By subscriber or subscriber number or By subscriber
Trace type
MID+UID+PSN. MID+UID+PSN number
Subscriber number
Subscriber This parameter is valid when the trace type
configured in the NA
number is By subscriber number.
system
DN set of the
This parameter is valid when the trace type
Local DN set configured NA
is By subscriber number.
subscriber
When you select it, you can specify the

task start time and end time of the trace
Selected/Not
Time task. When you leave it unselected, the Not selected
selected
system will start the trace task
immediately.
Half hour
Defines the start time and end time of the In format of
starting from
Start/End time trace task. They are valid when the [Time] [1978-1-1,2038-1-18
the current
option is selected. ]
time
5-82
Parameter
name
under the SoftX3000 installation folder.
Auto save to Selected/Not
The file name includes date, time, and Not selected
file selected
trace message type. You can read the
trace results can be with the Trace
Viewer tool.
After defining the parameters, click <OK>, and the call connection trace results are
displayed in the trace result window. Figure 5-81displays an example of call
connection trace results on a normal ISUP call.
5-83
Figure 5-81 Display window of call connection trace results
As shown in Figure 5-81, the user information is calssified into three parts:
z GivenSubsinformation of a specific subscriber
z RelaSubsinformation of related subscribers
z ThirdSubsinformation of a third-party subscriber
Table 5-29 Description of call connection trace results window
Category Field name Description

GivenSubs Dn Subscriber number (dial number)
5-84
Category Field name Description
State State transition process
Call Type Call type
RelaSubs State State transition process of the line
LineTx Returned messages
LineRx Received messages
Note:
The other two trace tasksCaller or callee trace and UMG user tracehave the same operation
procedure as that of the interface signaling trace, and will not be elaborated here.
5.4 Using Maintenance Management Node

5.4.1 Overview of Maintenance Management Node
The maintenance management node helps you maintain and manage the CPU,
memory, signaling links, No.7 links, terminals, and module communication. Figure
5-82 lists the available features.
Figure 5-82 Maintenance management navigation tree
5-85
5.4.2 Querying CPU Usage
I. Specifying Parameters to be Queried
Double click the CPU Usage node, and the parameter input dialog box is displayed
Figure 5-83 Specifying parameters to query CPU usage
z When you select Position, you have to specify the frame number and slot
number of the board.
z When you select Module, you have to specify the module number of the
board.s
II. Alternative Query Modes
You can also use one of the following two methods to query the CPU usage:
z Run the command DSP CPUR in the command window.
z Right click the board to be queried in the device panel view, select [Display CPU
Usage], and the system will display the CPU usage of the board in real time.
Refer to section 2.7.6 Querying CPU Usage in chapter 2 Using MML Client for
details.
III. Querying Results and Modifying Tasks
After specifying the parameters, click <Add>, and then click <Close>, the CPU usage
is displayed in the output window, as shown in Figure 5-84. The curve is refreshed
every five seconds.
5-86
Figure 5-84 CPU usage display window
You can right click on the upper window of Figure 5-84 to add or delete a CPU usage
query task.
z To add a task, Specify the parameters and click <Add>. The system will display
the newly added curve of CPU usage with a different color.
z To delete a task, Select the task to be deleted in the task list, and click <Delete>.
5.4.3 Querying Memory Usage
I. Specifying Parameters to be Queried
Double click the Memory Usage node, and the parameter input dialog box is
5-87
Figure 5-85 Specifying parameters to query memory usage
z When you select Position, you have to specify the frame number and slot
number of the board.
z When you select Module, you have to specify the module number of the board.
II. Alternative Query Modes
Right click the board to be queried in the device panel view, select [Display Memory
Usage], and the system will display the CPU usage of the board in real time. Refer to
section 2.7.7 Querying Memory Usage in chapter 2 Using MML Client for details.
III. Querying Results and Modifying Tasks
After specifying the parameters, click <Add>, and then click <Close>, the memory
usage is displayed in the output window, as shown in Figure 5-86. The curve is
refreshed every five seconds.
5-88
Figure 5-86 Memory usage display window
You can right click on the upper window of Figure 5-86 to add or delete a memory
usage query task.
z To add a task, Specify the parameters and click <Add>. The system will display
the newly added curve of memory usage with a different color.
z To delete a task, Select the task to be deleted in the task list, and click <Delete>.
5.4.4 Querying Inquire Memory
I. Querying RAM Content
Proceed as follows:
1) Double click the node Inquire Inquire Memory in the maintenance management
navigation tree.
2) Select RAM in Query type.
3) Select a module number.
4) Specify the start address of the RAM to be queried in hexadecimal numeral.
5) Specify the Active or standby flag the RAM to be queried.
To view the query results:
After specifying the parameters, click <Query>, and 128 bytes of RAM content
(starting from the start address) are displayed as shown in Figure 5-87.
5-89
Figure 5-87 RAM query window
II. Querying Flash Content
Proceed as follows:
1) Double click the node Memory content in the maintenance management
navigation tree.
2) Select Flash in Query type.
3) Specify the frame number of the board.
4) Select the slot number of the board.
5) Specify the start address of the flash to be queried in hexadecimal numeral.
6) Specify the number of bytes to be queried.
To view the query results:
After specifying the parameters, click <Query>, and the specified length of Flash
content (starting from the start address) is displayed as shown in Figure 5-88.
Figure 5-88 Flash query window
5-90
5.4.5 Dumping Memory Content
I. Overview of Dumping Memory Content
The memory dumping feature helps you save the content of the board memory for
future analysis (in case of system error). It will be extremely helpful when a remote
office is faulty without technical support engineers on site. The dumped content can
be a useful reference for debugging.
II. Defining the Dump Parameters
Proceed as follows:
1) Double click the node Dump Memory in the maintenance management
navigation tree.
2) Select a module number.
3) Specify the start address of the RAM to be queried in hexadecimal numeral.
4) Specify the end address of the RAM to be queried in hexadecimal numeral. It
must be greater than the start address.
5) Select Active or standby flag whether it is the active or standby RAM to be
queried.
6) Select the path and file name to dump the memory content. You can click ,
and the [Save As] dialog box is displayed. Then specify the file name (*.DAT)
and path.
III. Dumping the Content to File
After specifying the parameters, click <Query>, and the specified length of memory
block is saved to the file, as shown in Figure 5-89.
5-91
Figure 5-89 Memory dump window
Note:
It will take longer duration for the system to dump larger memory blocks to file.
5.4.6 Querying MTP3 Link Status
You can query the status of different types of MTP3 links in multiple modes.
Proceed as follows:
1) Double click the node MTP3 Link Status in the maintenance management
navigation tree.
2) Select a query type.
You can query the link status by OPC & DPC, by module, or by link set.
In query by module and link set, the module number is the one of the BSGI which
processes the MTP3 link.
To view the results:
After specifying the parameters, click <Query>, and the status of the MTP3 links is
5-92
Figure 5-90 Querying MTP3 link status
II. Additional Operations on the Link
Select one or multiple query records in Figure 5-90 and right click, and a shortcut
menu is displayed. You can perform the following operations:
z [Activate link] is available when the link is in deactivated state.
z [Deactivate link] is available when the link is in activated state.
z [Inhibit link]: is available when the link is in uninhibited state.
z [Uninhibit link] is available when the link is in inhibited state.
z [Details]: displays the MTP3 link status in text.
5.4.7 Querying No.7 Link Status
Proceed as follows:
1) Double click the node No7 Circuit Status in the maintenance management
navigation tree.
2) Select a query type.
You can query the link status by circuit or office direction
The module number of the No.7 link is the module number of the FCCU.
To query the results:
After specifying the parameters, click <Query>, and the status of the No.7 links is
5-93
Figure 5-91 Querying No.7 link status
Select one or multiple query records in Figure 5-91 and right click, a shortcut menu is
displayed. You can perform the following operations:
z Block Circuit
z Unblock Circuit
z Stop Block Circuit
z Stop Unblock Circuit
5.4.8 Querying Media Gateway Status
I. Overview of Querying Media Gateway Status
This node helps you query the status of media gateways by equipment ID, MGW type,
or module number.
II. Defining Query Parameters
Double click the node Media Gateway Status in the maintenance management
navigation tree. Configure the following parameter in the window:
z Equipment ID: You can use the wildcard * and ? in the equipment ID. This
parameter is case sensitive.
z MGW type: You can select All to query all types of media gateways, or select a
specific type such as AG, TG, IAD, UMG, MRS, and MTA.
z Module number: It is the FCCU module number to which the media gateway
belongs. You can enter All" to query all modules or specify a module number.
5-94
III. Checking Query Results
After specifying the query parameters, click <Query>, and the information of the
queried media gateways will be displayed as shown in Figure 5-92.
Figure 5-92 Querying media gateway status
5.4.9 Querying H.323/SIP Terminal Status
I. Overview of Querying H.323/SIP Terminal Status
This node helps you query the status and number information of the H.323/SIP
terminals.
Double click the node H.323/SIP Terminal Status in the maintenance management
navigation tree. Configure the following parameters in the window:
z Module number: It is the FCCU module number to which the terminal belongs.
You can enter All" to query all modules or specify a module number.
After specifying the query parameters, click <Query>, the information of the queried
H.323/SIP terminals will be displayed as shown in Figure 5-93.
5-95
Figure 5-93 Querying H.323/SIP terminal status
5.4.10 Querying MGCP/H.248 Terminal Status
I. Overview of Querying MGCP/H.248 Terminal Status
This node helps you query the status and number information of the MGCP/H.248
terminals
Double click the node MGCP/H.248 Terminal Status in the maintenance

management navigation tree. Configure the following parameters in the window:
z Termination ID
z Module number: It is the FCCU module number to which the terminal belongs.
You can enter All" to query all modules or specify a module number.
z MGW type: The type of media gateway to which the terminal to be queried
belongs. You can select All to query all types of media gateways, or select a
specific type such as AG, TG, IAD, UMG, and MRS.
After specifying the query parameters, click <Query>, the information of the queried
MGCP/H.248 terminals will be displayed as shown in Figure 5-94.
5-96
Figure 5-94 Querying MGCP/H.248 terminal status
5.4.11 Querying Module Communication Status
I. Overview of Querying MTP3 Link Status
This node helps you query the communication status among modules such as IFMI,
FCCU, CDBI, SMUI, BSGI, MSGI, and MRCA.
Double click the node Module Communication Status in the maintenance

management navigation tree. Configure the following parameters in the window:
z Frame number
z Slot number
z Communication port type
z Peer module number: This parameter is available when the communication port
type is Q.922 or Ether Link.
z CPCI Slot number: It is the CPCI slot number of peer end. This parameter is
available when the communication port type is CPCI.
z Serial Port Number: This parameter is available when the communication port
type is Serial Port.
After specifying the query parameters, click <Query>, the inter-modular

communication status will be displayed as shown in Figure 5-95. Here, you can see
that there are five faulty TCP links in slot 6.
5-97
Figure 5-95 Querying module communication status
5.5 Exporting and Reviewing Trace Results

5.5.1 Processing Trace Results
Right click in the trace result window, and a shortcut menu is displayed as shown in
Figure 5-96.
Figure 5-96 Shortcut menu in MGCP message trace result window
Table 5-30 describes the functions of the menu items in Figure 5-96.
Table 5-30 Description of menu items in the shortcut menu in the message trace result window
Menu name Functions Remark

The file name consists of message type, date,
Save All Messages Saves all messages to file. and time. You can view the file using the Trace
Viewer tool.
The file name consists of message type, date,
Save Selected Messages Saves the selected messages to file. and time. You can view the file using the Trace
Viewer tool.
Defines whether the system
Auto Scroll automatically scrolls the screen and NA
displays the new messages.
Clear messages Clears all messages NA
5-98
Menu name Functions Remark

The message type can be MGCP, H.248, SIP,
Analyzes all messages in the result H.323, M3UA, MTP3, PRA, and TCAP User.
Signaling Analyze All
window. The menu item is available when there are
messages in the result window.
The message type can be MGCP, H.248, SIP,
Analyzes the selected messages in H.323, M3UA, MTP3, PRA, and TCAP User.
Signaling Analyze Selected
the result window. The menu item is available when you select one
or multiple messages in the result window.
Close All ***** Message
Closes all trace task windows NA
Trace Tasks
Displays the information of the
Property NA
current trace task.
5.5.2 Using Trace Viewer
I. Overview of Trace Viewer
The trace viewer is a useful tool which helps you browse the trace results. The trace
review supports a binary file format *.tmf, which is generated from one of the following
two ways:
z Right click in the trace result window, and select [Save All Messages] or [Save
Selected Messages] in the pop-up shortcut menu. Save the trace results to a tmf
file. The default path is x:\SoftX3000\Output in the client installation folder.
z Select "Auto save to file in the trace window. The system will automatically save
the trace results to x:\SoftX3000\Trace.
II. Starting Trace Viewer
Select [Start/Programs/U-SYS SoftX3000 Operation and Maintenance Center/U-SYS

SoftX3000 Trace Viewer], and the "U-SYS SoftX3000 Trace Viewer" dialog box is
displayed.
III. Opening Trace Result File
You can open the Open dialog box in any of the following two methods:
z When you start the U-SYS SoftX3000 Trace Viewer, the open dialog box is
displayed.
z Select [File/Open] or the button in the main interface of U-SYS
SoftX3000 Trace Viewer.
5-99
IV. Selecting Trace Result Files to be Opened
You can select one or multiple tmf trace files (must be for the same message), then
click <Open>. Figure 5-97 shows the details.
Figure 5-97 Selecting files to be opened in trace viewer
Note:
You can select ten trace result files at a time, including a maximum of 50000 messages.
Figure 5-98 shows the main interface of trace viewer after opening files.
Figure 5-98 Main interface of trace viewer
5-100
V. Browsing Trace Messages
Click a trace messages, and a detailed explanation window is displayed as shown in

Figure 5-99.
Figure 5-99 Message explanation window in trace viewer
VI. Using the Shortcut Menu
Right click in the main interface of trace viewer, and the shortcut menu will be
Figure 5-100 Shortcut menu in trace viewer
Table 5-31 describes the functions of menu items in Figure 5-100.
5-101
Table 5-31 Description of shortcut menu items in trace viewer
Menu name Description

It is available when there are messages in the main interface. You
Save All Messages
need to specify the name of the file name.
It is available when there are messages selected. You have to enter

Save Selected Messages
the file name to be saved to.
Signaling Analyze All They support protocols such as MGCP, H.248, SIP, H.323, M3UA,
Signaling Analyze Selected MTP, PRA, and TCAP User. Refer to Figure 5-101 for details.
Set the range of time and specific message type. Click <OK> or
Filter <Apply>. The messages not meeting the requirement will be excluded
from display.
Undo Filter NA
Figure 5-101 Message filter dialog box in trace viewer
5.6 Analyzing Signaling Trace Results

5.6.1 Functions of Signaling Analysis
You can analyze signaling related information, including MGCP, H.248, SIP, and
H.323, in the following aspects:
z Analyzing and listing every call in the signaling.
z Querying signaling messages related to a certain call to analyze the signaling
interaction process.
z Analyzing call completion rate of caller.
5-102
z Analyzing call completion rate of callee.

z Analyzing the cause of failure of a specific call.
z Analyzing the call completion rate of a caller or callee.
z Collecting metrics and analyzing scenarios of early releases and no answers.
z Analyzing the extremely short bills and call durations.
z Collecting metrics and analyzing the sending and receiving of a message.
z Saving and finding analysis results.
5.6.2 Description of Signaling Analysis Interface
Figure 5-102 shows the signaling analysis window.
Figure 5-102 Signaling analysis window
Here are the descriptions of sections in Figure 5-102:

z Call information list: It is the upper left pane, which displays the detailed call
information of the analyzed signaling. It also supports pop up shortcut menus.
z Signaling flowchart: It is the upper right pane, which displays the signaling flow of
the selected call. The red lines are messages sent from the SoftX3000; the
yellow ones are information and message of the remote end equipment sent to
the SoftX3000; the blue ones are currently selected messages.
z Signaling message and metrics analysis list: It is in the lower part of the window,
which displays the call related signaling message flows, analysis, and statistical
results.
z Toolbar: It is on the left, which provides the same functions as the shortcut menu.
5-103
5.6.3 Signaling Analysis Operations
I. Starting Signaling Analysis
You can start the signaling analysis window in the client interface using any of the
following two methods:
z Right click in the interface signaling trace result window, and select [Signaling
Analyze All] or [Signaling Analyze Selected] in the pop up shortcut menu.
z Open saved trace result files in U-SYS SoftX3000 Trace Viewer, right click in
the main interface and select [Signaling Analyze All] or [Signaling Analyze
Selected] in the pop up shortcut menu.
II. Checking Call Information List
Table 5-32 details the call related information in the analyzed signaling as shown in
Figure 5-102.
Table 5-32 Description of call related items
Item name Description

CR Number Call sequence number
Caller number. For MGCP/H.248 signaling, it is displayed as the Termination
Caller
ID of the terminal.
Callee Callee number
The Tick value (of 10 ms) at the initiation of call. It is displayed as Time IAM in
Time Setup
MTP3 and M3UA signaling trace.
The Tick value (of 10 ms) at callee alerting (ringing). It is displayed as Time
Time Alert
ACM in MTP3 and M3UA signaling trace.
The Tick value (of 10 ms) at start of conversation. It is displayed as Time ANC
Time Connect
in MTP3 and M3UA signaling trace.
The Tick value (of 10 ms) at call release. It is displayed as Time CLF in MTP3
Time Release
and M3UA signaling trace.
Received Alert Whether alerting message is received.
Received Connect Whether connection message is received.
Call State Call connection is successful or failed.
III. Querying Related Information of a Call
In the signaling analysis interface, you can use one of the following three methods to
query all related information of a call from request for call setup to call release:
z Double click a call record in the call information list.
z Right click a call record in the call information list, and select [Show Related
Messages] in the pop up shortcut menu.
5-104
z Select a call record in the call information list, and click the button in the
toolbar.
Then, the signaling flowchart and the signaling message and metrics analysis list will
display the message flow of the currently select call. Refer to Figure 5-102 for details.
Double click a message in the signaling flowchart or the metric analysis list, and a
detailed explanation window is displayed as shown in Figure 5-103.
Figure 5-103 Message explanation window of related signaling
Note:
When you select a message in the signaling flowchart, it is automatically selected in the related signaling
process list; and it also works the other way round.
IV. Analyzing Call Information of Caller
There are two ways to analyze the call information of the caller in the signaling
analysis interface:
z Select the second shortcut menu item in the call information list. It differs in
different signaling and protocols. For instance, in SIP/H.323/MTP3/PRA trace, it
5-105
is [Caller Number Analysis]; in MGCP trace, it is [End Point ID Analysis]; and in

H.248 trace, it is [Termination Analysis].
z Click the button in the toolbar.
Enter the following parameters in the pop up dialog box:

z Caller ID: It is caller number (SIP, H.323, MTP3, M3UA, and PRA messages),
termination ID (H.248 messages), and endpoint ID (MGCP messages). If you
leave it blank, all calls will be analyzed.
z Call direction: It is valid for MTP3 and M3UA signaling analysis. You can select
In-Coming, Out-going or Both Directions.
After defining parameters, click <OK>, and the analysis results will be displayed in the
signaling message and metrics analysis list as shown in Figure 5-104. Here, you can
see call related information of caller such as call times, successful calls, and success
rates.
Figure 5-104 Call information analysis results of caller
In Figure 5-104, double click an analysis result, and a list of signaling messages
related to all calls will be displayed in the Stats Related Messages, as shown in
Figure 5-105.
5-106
Figure 5-105 A list of related messages of the analyzed signaling message
Double click any message in Figure 5-105, and you will see the detailed explanations
of the message.
V. Analyzing Call Information of Callee
There are two ways to analyze the call information of the callee in the signaling
analysis interface:
z Right click in the call information list, and select [Called Number Analysis] in the
pop up shortcut menu.
Enter the callee number and call direction in the pop up dialog box. If you leave the
callee number blank, all calls will be analyzed. The call direction is valid for the
analysis of MTP3 and M3UA signaling. You can select In-Coming, Out-going, and
Both Directions.
5-107
signaling message and metrics analysis list as shown in Figure 5-106. Here, you can
see call related information of callee such as call times, successful calls, and success
rates.
Figure 5-106 Analysis results of call information of callee
related to all calls will be displayed in the Stats Related Messages, similar to those
VI. Analyzing Cause of Failure of a Call
There are two ways to analyze the cause of failure of a call in the signaling analysis
interface:
z Right click in the call information list, and select [Fail Reason Analysis] in the pop
up shortcut menu.

z Select the cause of failure. It is different by signaling and protocols. The
parameter must be specified.
z Specify the callee number or caller ID. For SIP, H.323, MTP3, and PRA signaling,
the caller ID is caller number; for H.248 signaling, the caller ID is termination ID;
for MGCP signaling, the caller ID is endpoint ID. If you leave it blank, all calls will
be analyzed.
z For MTP3 and M3UA signaling, you can select protocol type (ISUP or TUP), call
direction (incoming, outgoing, or both directions), and caller/callee attributes
(caller side, called side, or any side).
signaling message and metrics analysis list as shown in Figure 5-107. The cause of
failure statistics is displayed.
5-108
Figure 5-107 Statistical results of cause of failures
VII. Analyzing Call Completion Rate
There are two ways to analyze the cause of failure of a call in the signaling analysis
interface:
z Right click in the call information list, and select [Success Rate Analysis] in the
pop up shortcut menu.

z Select the caller number or callee number as analysis object. For MGCP and
H.248 signaling, only the callee number is available.
z Enter the caller or callee number. For MGCP and H.248 signaling, only the callee
number is available. When you leave it blank, all calls will be analyzed.
z For MTP3 and M3UA signaling, you can select protocol type (ISUP or TUP), call
direction (incoming, outgoing, or both directions), and caller/callee attributes
(caller side, called side, or any side).
signaling message and metrics analysis list as shown in Figure 5-108. The call
completion rate statistics is displayed.
Figure 5-108 Statistical results of call completion rate
5-109
VIII. Analyzing Calls of Early Releases and No Answers
There are two ways to measure and analyze the calls of early releases and no
answers in the signaling analysis interface:
z Right click in the call information list, and select [Premature Release and No
Response Analysis] in the pop up shortcut menu.
Enter the callee number in the pop up dialog box. If you leave it blank, all calls will be
analyzed. For MTP3 and M3UA signaling, you can select the call direction from
Incoming, Outgoing, and Both Directions.
signaling message and metrics analysis list as shown in Figure 5-109. The statistical
results of calls of early releases and no answers are displayed.
Figure 5-109 Statistical results of calls of early releases and no answers
IX. Analyzing Extremely Short Bills and Call Durations
There are two ways to analyze the extremely short bills and call durations in the
signaling analysis interface:
z Right click in the call information list, and select [Short Bill Analysis] or [Call Time
Analysis] in the pop up shortcut menu.
Enter the duration range of the bill to be analyzed in the pop up dialog box. The start
duration ranges from 0 to 10 milliseconds, and the end duration ranges from 10 to
10000 milliseconds. For MTP3 and M3UA signaling, there is no limitation of input
value range. For MTP3 and M3UA signaling, you can select the call direction from
incoming, outgoing, and both directions.
5-110
signaling message and metrics analysis list as shown in Figure 5-110. The statistical
results of extremely short bills are displayed. For MTP3 and M3UA signaling, the
results are different. For example, the call duration is displayed in Tick value.
Figure 5-110 Analysis results of extremely short bills
related to the call of extremely short bill will be displayed in the Stats Related
Messages, similar to those shown in Figure 5-105.
X. Collecting Message Statistics
There are two ways to collect the statistics of all signaling messages in the signaling
analysis interface:
z Right click in the call information list, and select [Message Statistics] in the pop
up shortcut menu.
After defining parameters, click <OK>, and the statistics will be displayed in the
signaling message and metrics analysis list as shown in Figure 5-111 (using H.323
signaling statistics as an example). The displayed statistics includes incoming count,
incoming percentage, outgoing count, and outgoing percentage.
Figure 5-111 Collecting message statistics
5-111
XI. Saving and Searching Analysis Results
In the signaling message and metrics analysis list, you can right click and select the
menu items in the pop up shortcut menu:
z Select [Save As/Text File...] to save the information to a text file.
z Select [Save As/Text File...] to save the information to an excel file.
z Select [Find] to search throughout the list. The search content is
case-sensitive. You can click <Find First> and <Find Next> to locate the search
item.
XII. Closing Analysis Results
Right click in the result output page, and select [Close] in the pop up dialog box. The
output page is then closed.
5-112
tion ManualGUI Guide
S SoftX3000 SoftSwitch System Chapter 6 Using GUI on BAM
Chapter 6 Using GUI on BAM
6.1 Using BAM Application Software

6.1.1 Understanding Meanings of Service Processes
BAM application software includes processes such as Warn, Dataman, and Bill.
Meanings of various processes are listed as follows:Warn: It is the alarm process. It
processes the device alarm information and internal alarm information of the BAM. It
provides functions of alarm report and alarm information query for workstation. It drives
the alarm box.
z Dataman: It is the data configuration process. It processes device configuration
data and backs up data such as call prefix data and device data.
z Bill: It is the billing process. It collects and sorts IP Centrex bills.
z Maintain: It is the maintenance process. It processes device maintenance
commands such as loading patches for device programs and signaling tracing.
z Statis: It is the performance measurement process. It processes performance
measurement data such as creating performance measurement tasks and result
query.
z MML: It implements the communication between the BAM and workstation,
operator authority management, explanation of command entered through
workstation, and distribution of command entered by workstation. In addition, the
MML process bridges the communication between various processes of the BAM
and the client. It is responsible for the execution of timer command.
z Exchange: It is the communication module between the BAM and other devices. It
loads device programs and data. It distributes messages returned by devices. It
bridges the data exchange between the BAM and the host.
z BillSorter: It sorts and manages bills. Its function has been shifted to the iGWB.
z SNTPClient: It is the SNTP client. It collects server time and synchronizes the time
of the BAM with that of the client.
z FTP ManFTP BAM FTP BAM FTP

z XSManBAM

6.1.2 Starting BAM Application Software
The U-SYS SoftX3000 Server is automatically started when the BAM is started. The
startup window of the U-SYS SoftX3000 Server is as shown in Figure 6-1.
6-1
Figure 6-1 Startup window of the U-SYS SoftX3000 Server
I. Introducing Interface Units of U-SYS SoftX3000 Server
The BAM application software includes processes such as Warn, Dataman, and Bill.
The startup window of the U-SYS SoftX3000 Server includes the following four
columns: [Service], [Status], [Startup], and [ImagePath].Table 6-1details meanings of
the four columns.
Table 6-1 Interface units of the U-SYS SoftX3000 Server
Names Meanings Remarks

Service Name of process NA
Started: The process is running.
Stopped: The process is stopped.
Status Status of process
Exception: The process is abnormal. For example,
the process is suspended.
Automatic: After detecting that the process is
stopped, the U-SYS SoftX3000 Server automatically
restarts the process.
Startup type of the Manual: After detecting that the process is stopped,
Startup the U-SYS SoftX3000 Server does not restart the
U-SYS SoftX3000 Server
process automatically. You have to restart it manually.
System: The process is managed by the system.
Disabled: The process is invalid or cancelled.
Path of execution file
ImagePath NA
corresponding to process
6-2
II. Introducing Shortcut Icons on Startup Window of U-SYS SoftX3000 Server
Shortcut icons on the startup window of the U-SYS SoftX3000 Server provide a series
of functions. Table 6-2 describes functions of the shortcut icons.
Table 6-2 Functions of shortcut icons on the startup window of the U-SYS SoftX3000 Server
Shortcut icons Functions Remarks

To exit the U-SYS
NA
SoftX3000 Server
To start a process Before using the two icons, you need to select a process
in the list. According to the status of the process (running
or stopped), one of the two icons is activated. If the
To stop a process selected process is running, is unavailable. If the
selected process is stopped, is unavailable.
To stop all processes NA
The two icons provide a convenient method to open or

To display the close an application program interface. However, this
interface of specified method is effective only during the running of application
process programs. When application programs are restarted, the
registration status of each program is read from the
registry. If the registered status of the application
program in the registry is not to display the interface of
To hide the interface the application program, the interface of the application
of specified process program will not be displayed after the program is
restarted.
To configure the
Startup type of each To set the Startup type of each process
process
To start or stop the
real-time monitoring To start or stop the real-time monitoring of process
function
About U-SYS To display information such as version of the U-SYS
SoftX3000 Server SoftX3000 Server.
Caution:
Shutting down the U-SYS SoftX3000 Server will interrupt the communication between the BAM and the
SoftX3000. It will also interrupt the communication between the BAM, and all maintenance WSs and the
host.
6-3
6.1.3 Using Service Management Process
You can use the U-SYS SoftX3000 Server to monitor and manage multiple processes
running on the BAM. The U-SYS SoftX3000 Server manages processes by the
following three modes:
z Starting a specified process.
z Stopping a specified process.
z Stop all processes.
I. Starting a Specified Process
You can start a specified process according to the following steps:

1) Select the process to be started on the startup window of the U-SYS SoftX3000
Server.
2) Click [File/Start] or on the toolbar to start the selected process.
II. Stopping a Specified Process
You can stop a specified process according to the following steps:

1) Select the process to be stopped on the startup window of the U-SYS SoftX3000
Server.
2) Click [File/Stop] or on the toolbar. A dialog box pops up prompting whether

you are sure to stop the process.
3) Click <Yes> to stop the process.
Note:
According to the status of the process, or is activated. If the selected process is running,
is unavailable. If the selected process is stopped, is unavailable.
III. Stopping All Processes
Click [File/Stop All] or on the toolbar and you can stop all processes.
Using Real-time Monitoring Function

The real-time monitoring function monitors all processes whose startup types are
Automatic or System. If the processes are stopped because of different reasons, they
are automatically restarted. The status of each process is updated under the Status
6-4
column of the startup window of the U-SYS SoftX3000 Server. If the real-time
monitoring function is not activated, restart the function manually.
Click [Options/Realtime Monitor] or on the toolbar and you can start or stop the
real-time monitoring function.
6.1.4 Configuring Server Startup Information
Through configuring the startup information, you can set the startup type of the BAM
when the computer is restarted. There are four startup types of the BAM:
z Automatic
z Manual
z Disabled
z System
Proceed as follows to set the startup type of the BAM:
1) Click [Options/Startup] or on the toolbar and a dialog box pops up, as shown
in Figure 6-2.
Figure 6-2 Configuring startup information
Table 6-3 lists the meanings of the four startup types.
Table 6-3 Startup types and meanings of the BAM Service.
Startup types Meanings

When a BAM Service is detected to be stopped, the system automatically
Automatic
restarts the BAM Service.
Manual The BAM Service needs to be manually restarted.
Disable The system forbids automatic start of the BAM Service.
System The process is managed by the system.
6-5
2) After selecting the type, click <OK>.
Note:
In normal cases, set the startup type to Automatic.
6.2 Using BAM Server Gateway Tool

The BAM server gateway tool is an attached software of the BAM. It can only be used
on the BAM for connecting serial port device with the BAM.
The tool is an expansion of the communication layer of the BAM. It converts message
between TCP/IP and serial port protocol. It establishes connection with the BAM
through TCP/IP. It establishes connection with other serial port devices through serial
port protocol. It transparently transfers data between the BAM and serial port device.
For the BAM, command from any serial port device is considered as coming from an IP
address. All data sent by the BAM go to an IP address no matter the data might finally
stay on a serial port device such as HyperTerminal and alarm box.
The relationship between each serial port protocol and TCP/IP set up by the BAM
server gateway tool is called a connection. The tool supports multiple connection cases.
Each connection case is monitored by a conversion thread. You can set up or close a
connection case at any time.
6.2.1 Starting BAM Server Gateway Tool
Click [Start/Programs/U-SYS SoftX3000 Operation and Maintenance Center/U-SYS

SoftX3000 Server Gateway Tool] on the BAM. Figure 6-3 shows the main window.
Figure 6-3 Startup window of the BAM server gateway tool
If some connections are established during the last run of the system, the system
automatically records the connection configuration information to the file registry (Path:
6-6
HKEY_LOCAL_MACHINE\SOFTWARE\ huawei\SoftX3000\convert). If automatic

reconnection is enabled for some connections, the system, during system restart,
automatically creates connections according to information saved in the file registry.
The connections are configured according to the information saved after the successful
creation last time. The automatic reconnection window is as shown in Figure 6-4.
Figure 6-4 Successful reconnection window of the BAM server gateway tool
6.2.2 Creating Connection
I. Cautions in Creating Connection
During the use of the gateway tool, you might need to use some hardware devices. The
configuration of the hardware devices must be correct.The IP address of the BAM must
be correct. Otherwise, the system cannot check itself but attempts to reconnect
repeatedly.Pay attention to the use of compressed mode. Decompression and
compression operations need to be completed.Check whether the alarm console of the
BAM is running normally when using the alarm box.If you starts two gateway tool
program cases, the latter case pops up. That is, the system only reserves one
case.Operation Procedure
You can create a connection according to the following steps:
1) Click [Operation/Create connection] or on the toolbar and a dialog box pops

up, as shown in Figure 6-5.
6-7
Figure 6-5 Create a new connection dialog box for configuring connection information of the BAM server
gateway tool
Meanings of the fields are as follows:Serial port: to select the serial port number used
by the current conversion.
z BAM IP address: to select the address of the BAM to be connected. If the gateway
tool runs on the BAM, the address can be replaced by 127.0.0.1.
z Client application type: to select type of serial port device. For example, GUI
maintenance class and alarm box class.
z Serial port configuration: to configure serial port. By default, the baud rate is 9600
bit/s, the data bit is 8, the parity is None, and the stop bit is 1.
z Compress: to set whether to use the compressed mode for information
transmission. By default, it is not to use the compressed mode.
z Auto reconnect: It means whether to automatically reconnect the existing
connections after the gateway tool is restarted.
z Select Use modem dial by hand if modem is needed for connection. Enter
telephone number in Modem configuration.
2) After setting the data of the above fields according to your requirement, click
<Create> and the system creates a conversion connection according to your
setting.
If you cannot create a connection, it might be due to one or several of the following
reasons:The selected serial port does not exist.
z The serial port configuration information is wrong.
z The selected BAM IP address is wrong.
6-8
z The BAM IP address is correct, but the BAM is not properly started.
z The selected serial port has been used.
6.2.3 Interrupting Connection
You can interrupt a connection according to the following steps:

1) Click [Operation/Interrupt connection] and a dialog box as shown in Figure 6-6
pops up.
Figure 6-6 Disconnect dialog box
2) Select the serial port corresponding to the connection to be interrupted. Click

<OK> to confirm the disconnection.
6.3 Using Workstation Gateway Tool

The workstation gateway tool is an attached software of the U-SYS SoftX3000
Operation and Maintenance Center. It is an expansion of the communication layer of
the workstation. It converts message between TCP/IP and serial port protocol. It
establishes connection with the workstation through TCP/IP. It establishes connection
with other serial port device through serial port protocol. It transparently transfers data
between the workstation and serial port device. For the workstation, command from
any serial port device is considered as coming from an IP address. All data sent by the
workstation go to an IP address no matter the data might stay on a serial port device
such as HyperTerminal and alarm box.
The relationship between each serial port protocol and TCP/IP set up by the
workstation gateway tool is called a connection. The tool supports multiple connection
cases. Each connection case is monitored by a conversion thread. Each connection
case can be set up and closed at any time.
The workstation gateway tool is used for connecting workstation with serial port devices.
It can be run on the BAM or the LAN where the BAM is located. It can even be run on
any computer which communicates with the BAM through TCP/IP on the WAN. The
serial port of the computer is used to provide services for client workstation.
6-9
6.3.1 Starting Workstation Gateway Tool
Click [Start/Programs/U-SYS SoftX3000 Operation and Maintenance Center/U-SYS

SoftX3000 workstation Gateway Tool] on the BAM or workstation and you can start the
workstation gateway tool as shown in Figure 6-7.
Figure 6-7 Startup window of the workstation gateway tool
If some connections are established during the last run of the system, the system
automatically records the connection configuration information to the file registry (Path:
HKEY_LOCAL_MACHINE\SOFTWARE\ huawei\SoftX3000\convert). If automatic
reconnection is enabled for some connections, the system, during system restart,
automatically creates connections according to information saved in the file registry.
The connections are configured according to the information saved after the successful
creation last time. The automatic reconnection window is as shown in Figure 6-8.
Figure 6-8 Successful reconnection window of the workstation gateway tool
6.3.2 Creating Connection
I. Cautions in Creating Connection
During the usage of the gateway tool, you might need to use some hardware devices.
The configuration of the hardware devices must be correct:The BAM IP address must
be correct. Otherwise, the system cannot check but reconnects continuously.The alarm
box can only be connected to the BAM or the emergency workstation. Do not connect it
to a common workstation.Check whether the alarm console of the BAM is running
6-10
normally when using the alarm box.If you starts two gateway tool program cases, the
latter case pops up. That is, the system only reserves one case.Operation Procedure
You can create a connection according to the following steps:
1) Click [Connection/Create] or on the toolbar and a dialog box pops up, as

Figure 6-9 Dialog box for configuring connection information
Meanings of the fields are as follows:Serial port: The serial port number used by the
current conversion.
z BAM IP address: The address of the BAM to be connected. If the gateway tool
runs on the BAM, the address can be replaced by 127.0.0.1.
z Connection type: The type of serial port device. For example, GUI maintenance
class and alarm box class.
z Suggest listen port: to set the monitoring port number.
z Serial port configuration: Serial port configuration. By default, the baud rate is
19,200 bit/s, the data bit is 8, the parity is None, and the stop bit is 1.
z Select Use modem dial by hand if modem is needed for connection. Enter
corresponding contents in Dial command.
2) After setting the data of the above fields according to your requirement, click <Ok>
and the system creates a conversion connection according to your setting.
If you cannot create a connection, it might be due to one or several of the following
reasons:The selected serial port does not exist.
z The serial port configuration information is wrong.
6-11
z The selected BAM IP address is wrong.

z The BAM IP address is correct, but the BAM is not properly started.
z The selected serial port has been used.
6.3.3 Interrupting Connection
You can interrupt a connection according to the following steps:

1) Click [Connection/Close] and a dialog box as shown in Figure 6-10 pops up
Figure 6-10 Disconnect dialog box
2) Select the serial port corresponding to the connection to be interrupted. Click

<OK> to confirm the disconnection.
6.4 Using BAM Service

The BAM Service monitors whether the U-SYS SoftX3000 Server is started. If the BAM
Service runs normally and it detects that the U-SYS SoftX3000 Server is stopped, the
BAM Service automatically restarts the BAM. The function of the BAM Service is similar
to that of the Software Watchdog.
You can control the function of the BAM Service manually during the debugging
process of the system. The detailed operation steps are as follows:
1) Click [Start/Programs/Administrative Tools/Services] on the BAM and a window as
shown in Figure 6-11 pops up.
6-12
Figure 6-11 Services window
2) Right-click [BAM Service]. Select [Properties] on the pop-up shortcut menu and an
interface as shown in Figure 6-12 pops up.
6-13
Figure 6-12 BAM Service Properties interface
Meanings of three startup types are listed in Table 6-4.
Table 6-4 Startup types and meanings of the BAM Service.
Startup types Meanings

When a BAM Service is detected to be stopped, the system automatically
Automatic
restarts the BAM Service.
Manual The BAM Service needs to be manually started.
Disabled The system forbids automatic start of the BAM Service.
Note:
Under normal cases, the startup type is set to Automatic.
6-14
6.5 Using Smirror Process

The Smirror processes exist on the BAM and the emergency workstation. The
emergency workstation backs up the BAM data using the Smirror process. The
emergency workstation backs up the BAM data every four hours only if the Smirror
processes on the BAM and the emergency workstation are started.
You can back up the BAM data on the emergency workstation according to the
following steps:
1) Click [Start/Programs/Administrative Tools/Services] on the BAM and the
emergency workstation respectively. A window as shown in Figure 6-13 pops up.
Figure 6-13 Services window
2) Right-click [Smirror] and select [Start] on the pop-up shortcut menu.
Note:
Normally, the Smirror process is automatically started. If it is not started, start it manually. If the
synchronous backup information between the emergency workstation and the BAM is set during the
installation of the emergency workstation, it is unnecessary to set the configuration file. If the synchronous
backup information is not set or set incorrectly, set the configuration file according to the following method.
6-15
3) Open the STXBAM.ini file under the D:\SoftX3000 directory of the emergency
workstation, as shown in Figure 6-14.
Figure 6-14 Initialization window of the emergency workstation
4) Configure the initialization data under [Mirror].

There are four groups of parameters numbered 0, 1, 2, and 3 under [Mirror], indicating
that four groups of data backup information can be configured between the BAM and
the workstation. Meanings of parameters are as follows:
z RemoteServer: It refers to the IP address of the BAM to be connected with the
emergency workstation.
z RemoteDir: It refers to the storage path of the BAM data files.
z LocalDir: It refers to the storage path of the backup BAM data on the emergency
workstation.
The emergency workstation backs up the BAM data once every four hours. Only files
whose are modified more than four hours ago are backed up.
6.6 Using Automatic Login Tool

The automatic login tool sets the automatic login information of the Windows 2000
Server. The detailed operation steps are as follows:
Center/U-SYS SoftX3000 Autologin Tool] on the Windows 2000 Server and a
SoftX3000 option setting dialog box is displayed as shown in Figure 6-15.
6-16
Figure 6-15 SoftX3000 Option Setting dialog box
2) Enter the field name in "Domain". In this case, it is the computer name of the BAM,
SX3KBAM. Enter the login account name (Administrator) of the system
administrator in User. Enter the login password of the system administrator in
Password. For example, the default password is admin.
Caution:
The account name and password must be the same as those set for the administrator during the
installation of the Windows 2000 Server. Otherwise, the automatic login cannot be enabled.
3) Select Enable automatic login and click <OK> to complete the setting.
Restart the server after you finish the setting to validate the setting.
6-17
U-SYS SoftX3000 SoftSwitch System AppendixA Using Data Table Query Tools
AppendixA Using Data Table Query Tools
A.1 Using TableBrowse

TableBrowse is a tool that helps you query BAM data on client. You can query the BAM
data without having to install it by using the TableBrowse.
A.1.1 Classifying Data on BAM
The data in the BAM Database are classified into 10 data sets, each of which contains
the data tables of a certain type. You can query the data more quickly if you know which
group contains the data you wanted before querying. The definition of each data group
is as follows:
z BC: Bearer Control. It stores media gateway configuration data, such as MGCP
and H248 protocol.
z BTS: Bearer Trunk Signaling. It stores the trunk data related to SS7.
z CC: Call Control. It stores call control data, such as number analysis data.
z DB: Datebase. It stores data related to the host, such as route data and network
management (NM) data.
z H323&SIP: It stores the data related to H323 or SIP terminal configuration.
z SERVICE: It stores the data related to service, such as IPN, NP and UC.
z SS: System Support. It stores the data related to hardware, such as board
switching.
z TP: Terminal processing. It stores the operator data.
z OMC Information: Operation and Maintenance Center. It stores the global data of
the system, such as maximum number of tuples.
z FN: Fixed Network. It stores the data related to operator alarms and private
network traversal.
A.1.2 Starting TableBrowse
To start TableBrowse on a client, proceed as follows:

1) Double click TableBrowse.exe under D:\SoftX3000\Tools\TableBrowser on the
client. The SQL Server Login interface is displayed as shown in Figure A-1
A-1
Figure A-1 [SQL Server Login] dialog box
The definition of each parameter is as follows:

z Server: Enter the IP address of the BAM you want to connect with in the box. If
TableBrowse runs on the BAM, you can enter 127.0.0.1.
z Login in ID: Enter the administrator name of the SQL Server database.
z Password: Enter the administrator password.
2) Click <OK> after entering the IP address, name and password on the interface
shown in Figure A-1. An interface of data table query is displayed, as shown in
Figure A-2.
Figure A-2 Interface of data table query
If connecting successfully, the status bar in the Figure A-2 shows Connected.
A-2
A.1.3 Using File Menus
I. Reconnecting BAM Database
After logging in to the TableBrowse successfully, you can connect reconnection or the
database on another BAM. The operations are as follows:
1) After starting TableBrowse, select [File/ Connect] in the menu bar on the default
login interface of the TableBrowse, or press shortcut keys <Ctrl+R>, or click

in the toolbar. The SQL Server Login interface is displayed, as shown inFigure A-1
2) Enter the address, user name and password of the BAM as shown in Figure A-1
Click <OK>, and the interface of the TableBrowse is displayed.
II. Logging out Connection
To log out of the TableBrowse, select [File/Exit] in the menu bar of the login interface of
the TableBrowse, or press shortcut keys <Ctrl+X>.
A.1.4 Using Tools Menus
The Tools menu is frequently used. The following part takes the query of Call Prefix as
an example to show how to use the tools menu.
I. Setting Query Condition
You can query the Call Prefix whose value is larger, smaller or equal to a certain Call
Prefix data as you required. The required Call Prefix field is in the Called NO Analysis
table of the CC group. The operations are as follows:
1) Double click <Called NO Analysis table> under <CC> in the navigation tree
window. A data table is displayed on the right of the interface, as shown in Figure
A-3
A-3
Figure A-3 Result of data query
2) Select [Tools / Find] or press shortcut keys <Ctrl+F> or press on the toolbar,
to display a finding window, as shown in Figure A-4.
Figure A-4 Finding window (1)
The text box under Field shows all fields in the Called NO Analysis table. The operator
list contains 6 operators: =, >,<,>=,<=, and<>.
A-4
If behind the operator is an enumerated value, you can choose the value in the
pull-down list of the Value text box. If behind the operator is a number, you can enter
the number in the value text box by hand.
The bottons <+> and <> to the right of Value is to add or delete a condition in the
Condition field.
3) Click <+> to add the finding condition you set in the Condition field. The result is
as shown in Figure A-5.
Figure A-5 Finding window (2)
4) Click <Start> to start finding. The result is displayed to the right of the navigation
tree window, as shown in Figure A-6.
A-5
Figure A-6 Query results
II. Refreshing Result
You can press F5 or select [Tools / Refresh] to refresh the query result.
III. Setting Record Number of Query Result
You can set the number of displayed query result as you required. The operations are
as follows:
1) Select [Tools / Env Conifg] or press F6 or press on the toolbar, to display a

Environment configuration window, as shown in Figure A-7.
Figure A-7 Environment configuration window
A-6
2) Set the number of query result displayed, and then click <OK>.
Note:
The default number of maximum displayed query results is 1000. You can modify it as you required, but
the new number must be an integer between 10 and 2000.
A.1.5 Using View Menus
I. Showing and Hiding Navigation Tree
You can use one of the following ways to show or hide the navigation tree as you
required.
Select [View / Navigator View] or press F2 or press on the toolbar, to show or hide
the navigation tree.
II. Showing and Hiding Toolbar
The toolbar offers you the operation buttons to operate conveniently. You can use one
of the following ways to show or hide the toolbar.
Select [View / Toolbar] to display or hide the navigation tree window.
III. Showing and Hiding Status Bar
The status bar shows the status of the BAM for you. You can use one of the following
ways to show or hide the status bar.
Select [View / Toolbar] to display or hide the navigation tree window.
A.1.6 Using Window Menus
If you want to display multiple windows, you can cascading them, tile them horizontally
or vertically. The operation is the same as using Windows system, we just provides you
the example of cascading windows.
Select [Window / Cascade Windows] or click to cascade windows, as shown in

Figure A-8.
A-7
Figure A-8 Cascade window
A.1.7 Using Shortcut menus
In query, you can use shortcut menus to set query condition or refresh results. The
operations are as follows:
1) Click the right key in the result window. A shortcut menu is displayed in the window,
as shown in Figure A-9.
A-8
Figure A-9 Shortcut menu
2) Click [Find] on the shortcut menu. A Finding window is displayed as shown in

Figure A-5 for you to set query condition to go on finding.
3) Click [Refresh] on the shortcut menu to refresh the result in the window.
A.1.8 Displaying Version
You can use the following way to query the version information of the TableBrowse.
Select [Help / About TableBrowser] or click on the toolbar. An About

TableBrowser interface is displayed as shown in Figure A-10.
Figure A-10 Version information
A-9
A.1.9 Using Toolbar
The toolbar contains icons of frequently used operation. These icons provide the same
functions as some of the menus. Table A-1 lists the functions of the icons.
Table A-1 Functions of icons in the toolbar
Icon Functions
Show / hide the navigation tree.
Reconnection
Query by conditions
Set the number of displayed results
Cascade windows
Tile windows horizontally
Tile windows vertically
Close all windows
Query version
A.1.10 Using Shortcut Keys
The TableBrowse software has some shortcut keys to help you use the TableBrowse
efficiently. Table A-2 lists the functions of the shortcut keys.
Table A-2 Functions of shortcut keys
Shortcut keys Functions

F2 Show / hide the navigation tree.
F3 Go forward for one record
F4 Go back for seven records
F5 Refresh the window
F6 Set the number of query results
A-10
A.2 Using ExTableBrowse

ExTableBrowse is a tool which helps you query the data configured in the host without
having to install the database. However, you cannot modify the host data.
A.2.1 Classifying Data on Host
The data in the host are classified into seven data groups, each of which contains data
tables of a certain module. You can query the data more quickly if you know which
group contains the data you wanted before querying. The definition of the data groups
is as follows:
z SYS stores the data on the SMUI.
z FSPC stores the data on the FCCU and the FCSU.
z CDB stores the data on the CDBI, such as call location, gateway resource
management and outgoing trunk selection.
z BSG stores the data on the BSGI. BSGI is used to process the IP packets after the
IFMI level-1 dispatch. It processes such protocols as UDP, SCTP, M2UA, M3UA,
V5UA, IUA, MGCP and H.248 and performs level-2 dispatch of such messages to
the FCCU or FCSU for transaction layer or service layer processing.
z MRC stores the data on the MRCA which is related to collecting and generating
DTMF signals, playing and recording audio clips and holding multiparty
conferences.
z MSG stores the data on the MSGI, which is related to UDP, TCP, H.323 (H.323
RAS, H.323 CALL Signaling) and SIP.
z IFM stores the data used to forward IP packets, and the data related to processing
the message of the media access control (MAC) and distributing the IP packets.
A.2.2 Using ExTableBrowse
The operations of using the ExTableBrowse are the same as those of TableBrowse.
Refer to A.1 Using TableBrowse for further reference.
The following part shows how to use the ExTableBrwose to query data on the host.
1) Double click <ExTableBrowse. exe> under [D:\SoftX3000\Tools\ExTableBrowser]
on the client. The SQL Server Login interface is displayed as shown in Figure
A-11.
A-11
Figure A-11 Interface of SQL Server Login

z Server IP Address: The IP address of the BAM:Enter the IP address of the BAM
you want to connect with.If the ExTableBrowse runs on the BAM, you can enter
127.0.0.1.
z SQL Server User:Enter the administrator name of the SQL Server database.
z SQL Server Password:Enter the administrator password.
2) Click <OK> after entering the IP address, name and password on the interface
shown in Figure A-11. An interface of choosing board module is displayed, as
shown in Figure A-12.
Figure A-12 Download system table window

z Module Number: Choose the number of the module.
z Module Type: Enter the type of the module to identify the board. It must be
corresponding to the number chosen in the module number box.
z Card Type: Choose primary or backup as the type of the board.
A-12
3) Click <OK> after entering the module number and board type to download data
from the host. The result is as shown in Figure A-12.
Figure A-13 Download board module data
After the data is downloaded, a database named DumpedEX is created in the SQL
Server database on the BAM to store system tables.
4) After downloading the data of the designated module, double click the module
number in the navigation tree on the left of the interface as shown in Figure A-13.
The result is as shown in Figure A-14
A-13
Figure A-14 Query data of designated module window
A.2.3 Using Toolbar
The toolbar contains icons of frequently used operation. These icons provide the same
functions as some of the menusTable A-3 lists the functions of the icons.
Table A-3 Functions of icons in the toolbar
Icon Functions
Show/hide the navigation tree.
Reconnection
Query by conditions
Set the number of displayed results
Cascade windows
Tile windows horizontally
Tile windows vertically
Close all windows
Query version
A-14
U-SYS SoftX3000 SoftSwitch System AppendixB Acronyms and Abbreviations
AppendixB Acronyms and Abbreviations
Abbreviation Description
A
AAA Authentication Authorization and Accounting
ACC Account Card Calling
AMG Access Media Gateway
AN Access Network
ASN.1 Abstract Syntax Notation One
B
BAM Back Administration Module
BFII Back insert FE Interface Unit
BITS Building Integrated Timing Supply
BRA Basic Rate Access
BSGI Broadband Signaling Gateway
C
CAMA Centralized Automatic Message Accounting
CCF Call Control Function
CDBI Central Database Board
CDR Call Detail Record
Centrex Central Office Exchange Service
CIC Circuit Identification Code
CID Caller Identification Display
CKII Clock Interface Unit
CODEC Coder-decoder
CPC Central Processing Board
D
DDI Direct-Dialing-In
DOD2 Direct Outward Dialing-2
DPC Destination Point Code
DSS1 Digital Subscriber Signaling No.1
DTMF Dual-Tone Multifrequency
B-1
E
EC Echo Canceller
ENUM E.164 Number URI Mapping
EPII E1_Pool Interface Unit
F
FCCU Fixed Calling Control Unit
FCSU Fixed Calling Control Unit and Signaling process Unit
FE Fast Ethernet
FPH Free Phone
FSK Frequency Shift Keying
G
GK Gatekeeper
GT Global Title
GW GateWay
I
IAD Integrated Access Device
iDo ViewPoint iDo
IFMI IP Forward Module
iGWB iGateWay Bill
IN Intelligent Network
INAP Intelligent Network Application Protocol
IP Internet Protocol
IPN Internet Personal Number
ISDN Integrated Services Digital Network
ISUP ISDN User Part
International Telecommunication Union - Telecommunication Standardization
ITU-T
Sector
IUA ISDN Q.921-User Adaptation Layer
IVR Interactive Voice Response
M
M2PA MTP2-User Peer-to-Peer Adaptation Layer
M2UA Message Transfer Part 2 (MTP2) -User Adaptation Layer
M3UA Message Transfer Part 3 (MTP3) -User Adaptation Layer
B-2
MAC Media Access Control
MCU Multipoint Control Unit
MG Media Gateway
MGC Media Gateway Controller
MGCP Media Gateway Control Protocol
MIDCOM Middlebox Communications
MML Man Machine Language
MRCA Media Resource Control Unit
MRIA Media Resource Interface Unit
MRS Media Resource Server
MSGI Multimedia Signaling Gateway Unit
MTA Media Terminal Adapter
MTP Message Transfer Part
N
NAT Network Address Translation
NCS Network-Based Call Signaling
NGN Next Generation Network
NMS Network management System
NP Number Portability
O
OAM Operation Administration and Maintenance
OPC Originating Point Code
P
PAP Password Authentication Protocol
PBX Private Branch Exchange
PDB Power Distribution Box
PPS Pre-Paid Service
PRA Primary Rate Access
POTS Plain Old Telephone Service
PPS Pre-Paid Service
PSTN Public Switched Telephone Network
R
RADIUS Remote Authentication Dial-In User Service
B-3
RAS Registration, Admission and Status
RTCP Real-time Transport Control Protocol
RTP Real-time Transport Protocol
S
SAU Signaling Access Unit
SCCP Signaling Connection Control Part
SCN Switched Circuit Network
SCP Service Control Point
SCTP Stream Control Transmission Protocol
SDH Synchronous Digital Hierarchy
SDP Service Data Point
SG Signaling Gateway
SIGTRAN Signaling Transport
SIP Session Initiation Protocol
SIUI System Interface Unit
SLC Signaling Link Code
SLS Signaling Link Selection Code
SMAP Service Management Access Point
SMP Service Management Point
SMS Service Management System
SNMP Simple Network Management Protocol
SP Signaling Point
SS7 Signaling System No.7
SSN Sub-System Number
SSP Service Switching Point
STP Signaling Transfer Point
STUN Simple Traversal of UDP Through Network Address Translators
T
TCAP Transaction Capabilities Application Part
TCP Transport Control Protocol
TDM Time Division Mulitiplex(ing)
TMG Trunk Media Gateway
TRIP Telephone Route Information Protocol
B-4
U
UDP User Datagram Protocol
UMG Universal Media Gateway
UNI User Network Interface
U-NICA Universal Network Intelligent Core Architecture
UPT Universal Personal Telecommunication
U-SYS You Design Your System
V
V5UA V5.2-User Adaptation Layer
VoIP Voice Over IP
VOT Televoting
VPN Virtual Private Network
URL Uniform Resource Locators
W
WAC Wide Area Centrex
WWW World Wide Web
X
xDSL x Digital Subscriber Line
XML Extensible Markup Language
B-5

SoftX3000 Operation Manual-GUI Guide

Uploaded by

Document Information

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

SoftX3000 Operation Manual-GUI Guide

Uploaded by

Copyright:

Available Formats

Chapter 1 Introduction to GUI ........................................................................

U-SYS SoftX3000 SoftSwitch System

Volume GUI Guide

Manual Version T2-011637-20040331-C-3.30

Product Version V300R003

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,

The manual applies to U-SYS SoftX3000 SoftSwitch System V300R003.

The related manuals are listed in the following table.

It guides the engineers how to configure various data in the

It guides the engineers how to install and use the software

The manual describes the traffic measurement operations and applications in

There are six chapters and two Appendixes in the manual.

The manual is intended for the following readers:

The manual uses the following conventions:

II. Command conventions

III. GUI conventions

Caution Means reader be extremely careful during the operation.

Note Means a complementary description.

Chapter 1 Introduction to GUI ...................................................................................................... 1-1

Chapter 2 Using MML Client......................................................................................................... 2-1

2.3 Using Authority Menus..................................................................................................... 2-22

Chapter 3 Using Alarm Management System............................................................................. 3-1

Chapter 4 Using Performance Management System................................................................. 4-1

4.2.1 Workflow of Performance Measurement................................................................. 4-1

Chapter 5 Trace and Maintenance ............................................................................................... 5-1

5.4.8 Querying Media Gateway Status .......................................................................... 5-93

Chapter 6 Using GUI on BAM....................................................................................................... 6-1

AppendixA Using Data Table Query Tools .................................................................................A-1

A.2.2 Using ExTableBrowse ..........................................................................................A-11

AppendixB Acronyms and Abbreviations ..................................................................................B-1

Chapter 1 Introduction to GUI

1.1 Composition of GUI

1.2 Description of GUI Components

(1) Menu bar (2) Toolbar (3) Navigation tree

Figure 1-1 GUI of client

1.2.2 Menu Bar

The menu bar contains six menu items:

Table 1-1 Functions of menus

Menu item Functions

Menu item Functions

Table 1-2 Functions of icons in the toolbar

Shows/hides navigation tree

Shows/hides output window.

Shows/hides command window

Shows/hides wizard window

Shows online help of the menu item

1.2.4 Navigation Tree

The navigation tree window contains four tabs:

Table 1-3 Functions of tabs in the navigation tree

Provides subscriber management and device management functions.

Provides a tree-shape navigation of MML commands.

Provides signaling interface trace, user interface trace, and device

1.2.5 System Result Pane

The system result pane contains four tabs:

Table 1-4 Functions of tabs in the system result pane

Debug Exports information related to software debugging.

1.2.6 Command Window

I. Overview of Command Window