SJ-20100603155704-018-ZXWR RNC (V3.09.30) Calling Trace Operation Guide - 345681

ZXWR RNC
Radio Network Controller
Calling Trace Operation Guide

Version: 3.09.30
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2011 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited.
Additionally, the contents of this document are protected by
contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No.
Revision Date
Revision Reason
R1.0
20100713
First Edition (V3.09.30.03)
R1.1
20100903
Updated:
1. 1.1 Software Functions
2. 2.1 Calling Trace Software Installation Overview
3. 2.2 Installing Procedures
4. 3.2 Starting Calling Trace Software Client
5. 3.4.3 Deleting NE
6. 3.5.5 Stopping Tasks
7. 3.5.8.1 Signaling Trace Toolbar Introduction (Table 3)
Added:
1. 1.4 the section "Networking Modes" is newly added after the
subsection (1.3.5) "RNL or TNL Module".
2. 2.3 the section " Configuration and Startup of MRM" is newly
added after the section " Installing Procedures"
Revision No.
Revision Date
Revision Reason
R1.2
20101118
The following sections have been updated:

1. Software Functions
2. CT Manager Module
3. CT Server Module
4. Task Life Cycle
5. Software Performance
6. NE Management
7. Adding NE
8. Deleting NE
9. Modifying NE
10. Connecting Link
11. Disconnecting Link
12. Entering User Tracing
13. Monitoring Task
14. Signaling Trace Tool-bar Introduction
15. Saving All
16. Saving Selected Signaling
17. Searching
18. Filtering
19. Starting Monitor
20. Stopping Monitor
21. Suspend Or Restore Refreshing
22. Displaying in Full Screen
23. Original Code Source
24. Detailed Decoding
25. Deleting All
26. Suspend Or Restore Scrolling
R2.0
20110228
Second Edition(V3.09.30.09)
The following sections have been added Deployment Mode,
Independent
Server
Deployment,
Sharing
EMS
Server
Deployment, Local NE Deployment, Tasks Synchronization,

Installing Calling Trace Software Server, Installing Calling Trace
Software Client, Port Offset Configuration, Viewing Data, Viewing
Trace Files Offline, Configuring Holiday, Setting User Password.
The following sections have been updaeedPreface, Calling Trace
Software Installation Overview, Configuration and Startup of MRM,
Entering NE Management Interface, Adding NE, Deleting NE,
Modifying NE, Connecting Links, Disconnecting Links, Entering
User Tracing, Trace Tasks Management, Starting Tasks, Stopping
Tasks, Deleting Tasks, Monitoring Tasks, Opening and Closing
Toolbar, Opening and Closing Statusbar, Opening and Closing
Message Checking, Closing Window, Locking Screen, Settting the
Revision No.
Revision Date
Revision Reason
System, Setting Login User Information, Querying System Time,
Logging Out, Exiting the System
The following sections have been deleted Networking Modes,
Software Performance, Installing Calling Software Procedures.
Serial Number: SJ-20100603155704-018

Publishing Date: 2011-02-28(R2.0)
Contents
About This Manual ......................................................................................... I
Chapter 1 Basic Concept ........................................................................... 1-1
1.1 Software Functions............................................................................................. 1-1
1.2 Installation Modes .............................................................................................. 1-2
1.3 Software Modules .............................................................................................. 1-2
1.3.1 CT Client Module ..................................................................................... 1-2
1.3.2 CT Server Module .................................................................................... 1-3
1.3.3 CT Manager Module................................................................................. 1-3
1.3.4 CT Agent Module ..................................................................................... 1-3
1.3.5 RNL Or TNL Module................................................................................. 1-3
1.4 Deployment Modes ............................................................................................ 1-3
1.4.1 Independent Server Deployment ............................................................... 1-4
1.4.2 Deployment of Sharing EMS Server .......................................................... 1-5
1.4.3 Local NE Deployment ............................................................................... 1-6
1.5 Basic Concepts .................................................................................................. 1-7
1.5.1 Task Life Cycle......................................................................................... 1-7
1.5.2 Task Types .............................................................................................. 1-8
1.5.3 Tasks Synchronization .............................................................................. 1-9
Chapter 2 Software Installation................................................................. 2-1

2.1 Calling Trace Software Installation Overview ........................................................ 2-1
2.2 Installing the Calling Trace Software Server ......................................................... 2-2
2.3 Installing Calling Trace Software Client .............................................................. 2-12
2.4 Port Offset Configuration .................................................................................. 2-16
2.5 Configuration and Startup of MRM..................................................................... 2-17
Chapter 3 Basic Operations ...................................................................... 3-1

3.1 Starting Calling Trace Software Server ................................................................ 3-1
3.2 Starting Calling Trace Software Client ................................................................. 3-3
3.3 Software Interface .............................................................................................. 3-4
3.4 Network Element Management ........................................................................... 3-6
3.4.1 Entering NE Management Interface ........................................................... 3-6
3.4.2 Adding NE ............................................................................................... 3-7
3.4.3 Deleting NE ............................................................................................. 3-9
3.4.4 Modifying NE ......................................................................................... 3-10
3.4.5 Link Operation ........................................................................................3-11

3.4.6 User Tracing .......................................................................................... 3-13
3.4.7 Opening Data File .................................................................................. 3-44
3.4.8 Setting Client Parameters ....................................................................... 3-45
3.4.9 Viewing Trace Files Offline...................................................................... 3-46
3.5 Window ........................................................................................................... 3-47
3.5.1 Switching Window .................................................................................. 3-47
3.5.2 Opening and Closing Toolbar .................................................................. 3-48
3.5.3 Opening and Closing Statusbar............................................................... 3-49
3.5.4 Opening and Closing Message Checking................................................. 3-50
3.5.5 Closing Windows.................................................................................... 3-52
3.6 System Menu................................................................................................... 3-53
3.6.1 Locking Screen ...................................................................................... 3-53
3.6.2 Setting Print ........................................................................................... 3-55
3.6.3 User Customizing................................................................................... 3-56
3.6.4 Setting User Password ........................................................................... 3-60
3.6.5 Querying System Time ........................................................................... 3-61
3.6.6 Logging Out ........................................................................................... 3-62
3.6.7 Exiting The System ................................................................................ 3-63
Appendix A Troubleshooting ................................................................... A-1

A.1 Task Status Is Starting........................................................................................ A-1
A.2 Software Server can not be Started..................................................................... A-1
Figures............................................................................................................. I
Tables .............................................................................................................V
Glossary .......................................................................................................VII
II
About This Manual

Purpose
This manual presents the basic concepts, installation procedures, and operation methods
of the calling trace software. It helps maintenance personnels and technicians to locate
and analyze fault causes and do troubleshooting in time.
What Is In This Manual

This manual includes four chapters and an appendix.
Chapter
Summary
Chapter 1 Basic Concepts
Introduces the basic function, installation mode,

structure and performance of calling tracing
software. It enables users to get an initial
understanding of the calling trace software and
lay the basis for future application.
Chapter 2 Installation
Presents the installation procedures of the calling

trace software.
Chapter 3 Basic Operations
Describes the basic operations of the calling

trace software, including entering/exiting the
system, NE management operation, users tracing
operation, tool and window operation.
Chapter 4 General Problems and Solutions
Lists the solutions for two kinds of general

problems of the calling trace software.
Appendix Glossaries
Presents the full English names of the glossaries.
Intended Audience
The intended audiences of this manual are as follows:
l
l
l
Network optimization engineers

Maintenance engineers
Testing engineers
Reference
This manual references to the following document:
l
ZXWR RNC (V3.09.30) Radio Network Controller Operation and Maintenance Module
Software Installation Guide
II
Chapter 1
Basic Concept
Table of Contents
Software Functions.....................................................................................................1-1
Installation Modes ......................................................................................................1-2
Software Modules ......................................................................................................1-2
Deployment Modes ....................................................................................................1-3
Basic Concepts ..........................................................................................................1-7
1.1 Software Functions

The calling trace software is an independent multiple NEs tracing management software,
supporting visit of multiple clients, and supporting task tracing of multiple RNC NEs.
Generally, when errors occur with the network, calls break down, services become
abnormal, or users are optimizing the network, the calling trace software can be used to
locate and analyze the faults. For those faults that can not be traced, the calling trace
software can help to determine the next step by analyzing the traced signaling.
With the calling trace software, users can easily trace and observe the real-time signaling
message that the system reports. In addition, it facilitates the maintenance personnel to
locate faults and debug the system.
Calling trace exists in the form of calling trace task and measure trace task, aiming at such
objects as mobile stations, cells and every network interface. At present, the system can
provide calling trace tasks at both radio network layer and transmission network layer at
the same time.
Functions relating to the calling trace software, such as system monitoring, rights control,
log management, refer to the following documents:
l
l
NetNumen M31(RAN) Mobile Network Element Management System Safety

Management Operation Guide
NetNumen M31(RAN) Mobile Network Element Management System Performance
Management Operation Guide
Note:
The calling trace software of the present version only provides functional modules of NE
management and users tracing.
1-1
SJ-20100603155704-018|2011-02-28(R2.0)
ZTE Proprietary and Confidential
ZXWR RNC Calling Trace Operation Guide
1.2 Installation Modes

At present, the calling trace software adopts the client-server mode, as shown in Figure
1-1.
In this mode, as soon as the calling trace software starts, the users connect to the calling
trace server through the calling trace client and then the server directly connects to the
NE, as shown inFigure 1-1.
Figure 1-1 Client-Server-NE Mode
1.3 Software Modules

The call trace software consists of CT Client module, CT Server Module, CT Manager on
ROMP board, CT Agent module on RNC board, and modules of RNL and TNL.
The relationships among all modules are shown in Figure 1-2.
Figure 1-2 Calling Trace Software Structure
1.3.1 CT Client Module

CT Client module, the user software client, needs to be connected to the server when it is
used to customize and start signaling trace tasks, and query signaling results.
The CT Client module is used independently as an independent calling trace client.
1-2
SJ-20100603155704-018|2011-02-28(R2.0)
Chapter 1 Basic Concept
1.3.2 CT Server Module

CT Server locates at the user software end to set up links with RNC and forward signaling
trace tasks and results.
CT Server is used independently as an independent calling trace server end.
CT Server connects with ROMP on RNC, intercommunicates with CT Manager module on
ROMP, and obtains message of signaling trace.
1.3.3 CT Manager Module

CT Manager module resides on ROMP, forwarding trace control messages and
summarizing trace data messages.
l
l
l
CT Manager receives the trace control messages from CT Server and forwards to CT
Agent module on corresponding boards.
CT Manager module receives the trace data messages from CT Agent module on
RNC boards and forwards to CT Server.
CT Manager module is the unique path between CT board software module and CT
Server. The system controls the data flow and limits the trace control parameters in
CT Manager module, such as, limits the signaling trace message traffic at the client.
CT Manager module informs CT Server of the configuration data modification reported
from CT board, detects and traces the connection/disconnection of communication
link at the client in real time.
1.3.4 CT Agent Module

CT Agent module is distributed on all boards. It connects with RNL application modules,
and forwards trace control messages and trace data messages.
l
l
l
CT Agent module receives the trace control messages from CT Manager, and
forwards to the corresponding RNL application modules.
CT Agent module receives the trace data message from all board RNL application
modules, and forwards to CT Manager.
CT Agent, together with CT Manager, controls the data flow.
1.3.5 RNL Or TNL Module

RNL or TNL module receives the calling trace control messages from CT Agent and
starts radio signaling/transmission signaling application processing modules on the
corresponding boards. It processes the signaling and data, and then sends the processed
signaling data to CT Agent module.
1.4 Deployment Modes

RCT is a real-time signaling trace tool of multiple NEs. It is of client/server structure, needs
to be deployed independently, and supports multiple clients tracing.
1-3
SJ-20100603155704-018|2011-02-28(R2.0)
According to the deployed location of the software at the server, the deployment modes of
RCT fall into three kinds as follows:
l
l
l
Independent server deployment

Sharing EMS server deployment
NE local deployment
1.4.1 Independent Server Deployment

Networking Modes
As an independent server, the calling trace server is deployed on EMS (EMS network
segment). It is separated from the EMS server, runs independently.
If EMS network segment does not connect to OMM network of ROMP, deploy MRM on
OMM. The calling trace software server connects to RNC through MRM on OMM so as to
execute signaling trace operation. The specific deployment is shown in Figure 1-3.
Figure 1-3 Installing Calling Trace Software Server Independently
Requirement on Resources
Under the mode that the server is deployed independently, the requirement on resources
is shown in .
Item
Requirement
Recommended Server
sun v4 SPARC Enterprise T5220 (virtual CPUs:

64, physical memory: 32G)
CPU Occupancy
10%
Memory Usage
2 G (RCT software occupies 1200M, the

database instance occupies 800M)
Disk Space
49546 M
Bandwidth
0.32 Mbps
1-4
SJ-20100603155704-018|2011-02-28(R2.0)
Limitations
Under the mode that the server is deployed independently, the calling trace software has
the following limitations:
l
l
l
l
l
Support the trace of all tasks for 7*24 hours, and at most support 20 UE signaling
tasks.
At most support 4hour continuous observe of such real-time tasks as RTV and MTM.
At most support 0.5hour continuous trace of signaling tasks of the IU transmission
layer.
At most support 3day continuous trace of such other signaling tasks as cell signaling
tasks, and office direction signaling tasks.
Support offline trace of code stream tasks on the user plane.
1.4.2 Deployment of Sharing EMS Server

Networking Mode
The Server module can be integrated into the EMS server so that the calling trace
software can have centralized management on multiple NEs. Consequently, the calling
trace software can share the same server with EMS only if EMS still has processing
capability, which saves hardware costs. The specific deployment is shown inFigure 1-4.
Figure 1-4 Calling Trace Software Server is Integrated Into EMS Server
Note:
The server shared with EMS can run such operation systems as WINDOWS2003, LINUX
or SOLARIS, while the client must run WINDOWS operation system.
The corresponding decoding database of the calling trace server, which is installed on
different operation platforms, is to decode signaling code streams. The decoding database
is integrated into installation software.
Requirement on Resources
Under the deployment mode that the EMS server is shared, the requirement on resources
is shown in .
1-5
SJ-20100603155704-018|2011-02-28(R2.0)
Item
Requirement
CPU Occupancy
10%
Memory Usage
2 G (RCT software occupies 1200 M, the

database instance occupies 800 M)
Disk Space
49546 M
Bandwidth
0.32 Mbps
Limitations
Under the deployment mode that the EMS server is shared, the calling trace software has
the following limitations:
l
l
l
l
l
Does not support the trace of all tasks for 7*24 hours. At most support 3day
continuous trace and 20 UE signaling tasks.
At most support 2hour continuous observe of such real-time tasks as RTV and MTM.
At most support 0.5hour continuous trace of signaling tasks of the IU transmission
layer.
At most support 1day continuous trace of such other signaling tasks as cell signaling
tasks, and office direction signaling tasks.
Support offline trace of code stream tasks on the user plane.
1.4.3 Local NE Deployment

The Calling Trace Software is Deployed at Local NE
For non-signaling-trace users, such as, users in the lab or during site access, the calling
trace software needs to be used as an on line signaling monitor tool to provide deployment
modes for local NEs.
For local deployment, one MRM needs to be deployed on OMM so as not to affect the
running of OMM. The deployment mode of it is the same as other two deployment modes.
The Server module and the Client module of the calling trace software can be run on two
PCs or on one PC simultaneously. The specific deployment mode is shown in Figure 1-5.
1-6
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 1-5 The Calling Trace Software is Deployed at Local NE
1.5 Basic Concepts

Calling trace exists in the form of calling trace tasks. When creating the calling trace tasks,
users define task name, task description, task type, and calling trace object corresponding
to the task type and traced parameter information.
Therefore, it is necessary to know about basic knowledge about the calling trace task
before using the calling trace software.
1.5.1 Task Life Cycle

The calling trace task has a comprehensive life cycle that ranges from creating calling
trace tasks, maintaining calling trace task status to deleting calling trace tasks.
The comprehensive calling trace task life cycle is shown inFigure 1-6.
1-7
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 1-6 Calling Trace Task Life Cycle
As shown inFigure 1-6, the calling trace system supports the calling trace tasks in two
statuses: suspending status and running status. The present task status depends on user
operation, link status of the client and RNC NE. Only the calling trace tasks in the running
status can collect the signaling message and measurement graphs corresponding to the
task and display at the client.
1.5.2 Task Types

There are six types of tasks that the calling trace software allows to trace, as shown in
Table 1-1.
Table 1-1 Task Types
Type
Home Board
Purpose
UE Trace
ROMP/RCP
The trace task is to take UE as a tracing object.
1-8
SJ-20100603155704-018|2011-02-28(R2.0)
Type
Home Board
Purpose
OFFICE-IU Trace
ROMP/RAP
To trace the signaling between RNC and CN

(Core Network), including PS domain signaling
trace and CS domain signaling trace.
OFFICE-IUR Trace
ROMP/RCP
To trace the signaling between RNC and

adjacent RNC.
OFFICE-IUB Trace
ROMP/RCP
To trace the signaling between RNC and

NODE B.
CELL Trace
ROMP/RCP
The trace task is to take CELL as a tracing

object.
MBMS Trace
ROMP/RCP
To designate session ID of MBMS, and the cell

where MBMS locates, and trace the signaling
related to MBMS.
1.5.3 Tasks Synchronization

The calling trace software supports to synchronize tasks between itself and RNC NE in
the following two modes:
l
l
l
Timing synchronization: The calling trace software sends task synchronization

messages to NEs every 30 seconds, and the task status started will be changed to
SYNC (under the status of being synchronized).
For tasks in NEs but not in the calling trace software, they will be deleted by NEs
automatically.
For tasks in the calling trace software but not in NEs, their status will be changed to
STOP automatically.
Caution!
When tasks are being synchronized as scheduled, please do not operate on them.
Non-timing synchronization: The calling trace software will automatically initiate a

synchronization of tasks when links are being connected. When links are interrupted,
the status of the task being started will be set as SYNC by the software for later
synchronization.
TNL tasks can not be synchronized.
1-9
SJ-20100603155704-018|2011-02-28(R2.0)
This page intentionally left blank.
1-10
SJ-20100603155704-018|2011-02-28(R2.0)
Chapter 2
Software Installation
Table of Contents
Calling Trace Software Installation Overview ..............................................................2-1
Installing the Calling Trace Software Server ...............................................................2-2
Installing Calling Trace Software Client.....................................................................2-12
Port Offset Configuration ..........................................................................................2-16
Configuration and Startup of MRM ...........................................................................2-17
2.1 Calling Trace Software Installation Overview

The calling trace software consists of message routing module (MRM), the client, and the
server. The calling trace software installation package can complete the installation of the
server and client at one time. MRM is carried in OMM release package, you can complete
the deployment of MRM according to Configuration and Startup of MRM. It does not
need to install MRM independently.
In Windows environment, the calling trace software installation procedures are as follows:
Note:
The installation method of the calling trace software under the environment of LINUX and
Solaris, refer to the corresponding contents in this manual.
1. Installation preparation.
a. Oracle 10g database is installed.
b. Create a new example for calling trace software in Oracle database.
2. Installing the software server.
Installing the software client.
Setting port offset parameters.
Configuration and startup of MRM.
2-1
SJ-20100603155704-018|2011-02-28(R2.0)
2.2 Installing the Calling Trace Software Server

Abstract
To introduce the installation procedures of the calling trace software server.
Prerequisites
1. Oracle 10g server is installed.
2. To create a calling trace software instance (different from the instance used by NM
software).
3. To modify the process as 400 when creating a calling trace software instance, as
shown in Figure 2-1.
Figure 2-1 Modifying Processes
4. The calling trace software can not be run simultaneously with NM server software on
one PC.
Steps
1. The calling trace software installation directory is opened, and double-click setup.b
at to install it.
2. The EMS System Installation window pops up. Press Enter and select the saving
address that is for saving temporarily installed files by default.
3. The Select Language interface pops up, and select English from the pull-down box
according to the installation environment, as shown in Figure 2-2.
2-2
SJ-20100603155704-018|2011-02-28(R2.0)
Chapter 2 Software Installation
Figure 2-2 Select Language
The language selected on the present interface is the language shown on the running
software interface after the calling trace software is installed.
4. Click Next to bring up the License agreement interface, and check I accept the
license agreement.
5. Click Next, and the Select Installation Style interface is opened, as shown in Figure
2-3.
Figure 2-3 Select Installation Style
You can select the installation style according to the description in the right pane of
Tips about current installation style.
2-3
SJ-20100603155704-018|2011-02-28(R2.0)
6. Click the Next button, and the Network scale interface is opened, as shown in Figure
2-4.
Figure 2-4 Network scale
You can select the network scale according to the description in the right pane of Tips
about current selected scale.
7. Click Next, and the Select product interface is opened, as shown inFigure 2-5.
Figure 2-5 Select product
Check All Products.

Type the installation directory of the calling trace software in Program Area Path, or
click
to select the installation path automatically.
2-4
SJ-20100603155704-018|2011-02-28(R2.0)
Though Data Area Path is consistent with Program Area Path by default, you can
set a different installation directory in Data Area Path as needed.
Note:
The item of CORBA Notify Service product is optional, thus enabling object
communications between different platforms and languages.
All other products must be selected.
8. Click Next, and the Database connection config interface is opened, as shown in
Figure 2-6.
Figure 2-6 Database connection config
l
l
l
l
l
l
Select ORACLE from the drop-down menu of Database type.

Database IP or hostname is the IP address of the Oracle server.
Database port is 1521 by default.
Database superuser name is the name of system users in Oracle environment.
Password is the same as the password that used by system users in Oracle
environment.
Click the Test Database Connection button to check whether the database is
connected successfully.
9. Click Next, and the Database Config interface is opened, and the database size of
UCA should be set the following :
a. Choose UCA in the Database Config interface to bring up a UCA pane under the
interface, as shown in Figure 2-7.
2-5
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 2-7 UCA config in Database config
b. Double-click the records in UCA config to bring up a Database config dialog box,
as shown in Figure 2-8.
Figure 2-8 Database config
Note:
Due to the calling trace software does not have high requirement on alarms, the
disk space for saving alarm information can not be configured as large, you can set
the disk space size of alarms occupied as 1024 MB in Need disk space size(M).
2-6
SJ-20100603155704-018|2011-02-28(R2.0)
c. Click OK, and the setting of UCA config completes.

10. Click Next, and the Host information config interface is opened, as shown in Figure
2-10.
Figure 2-9 Host information config
Type the IP address, where the server is located, in Main process server address.
11. Click Next, and the System information detection interface is opened, as shown in
Figure 2-10.
2-7
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 2-10 System information detection
12. Click the Next button to bring up the Installation Info Confirm interface, confirm the
products information.
13. Click Next, and the Unzip and Copy File interface is opened, as shown in Figure 2-11.
Figure 2-11 Unzip and Copy File
14. After unzip completes, click Next, and the Confirm interface of whether to execute
these SQLs currently is opened, as shown in Figure 2-12.
2-8
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 2-12 Confirm
15. Click Yes, and the Installation database interface is opened, as shown in Figure 2-13.
Figure 2-13 Installation database
16. After the installation completes, click Next, and the Parameter Set interface is opened,
as shown inFigure 2-14.
2-9
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 2-14 Parameter Set
Parameters on this interface do not need to be configured, and you can select default
configuration for them.
17. Click Next to bring up the Confirm dialog box that inquires you whether to initialize all
client scenes, as shown in Figure 2-15.
Figure 2-15 Confirm
18. Click Next, and the System Initialization interface is opened, as shown in Figure
2-16.
2-10
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 2-16 System Initialization
19. After the initialization completes, click Next, and the Installation finished interface is
opened, as shown in Figure 2-17.
Figure 2-17 Installation Finished
Click Finish, and the installation of programs completes.

End of Steps
2-11
SJ-20100603155704-018|2011-02-28(R2.0)
2.3 Installing Calling Trace Software Client

Abstract
To introduce how to install the calling trace software client.
Steps
1. The calling trace software installation directory is opened, and double-click setup.b
at to install it.
2. The EMS System Installation window pops up. Press Enter and select the saving
address that is for saving temporarily installed files by default.
3. The Select language interface is opened. Select English from the drop down menu
according to the installation environment, as shown in Figure 2-18.
Figure 2-18 Select language
The language selected on the present interface is the language shown on the running
software interface after the calling trace software is installed.
4. Click Next to bring up the License agreement interface, and check I accept the
license agreement.
5. Click Next, and the Select Installation Style interface is opened, as shown in Figure
2-19.
2-12
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 2-19 Select Installation Style
You can select the installation style according to the description in the right pane of
Tips about current installation style.
6. Click Next, and the Select product interface is opened, as shown inFigure 2-20.
Figure 2-20 Select product
Check All Products.

Type the installation directory of the calling trace software in Program Area Path, or
click
to select the installation path automatically.
Though Data Area Path is consistent with Program Area Path by default, you can
set a different installation directory in Data Area Path as needed.
2-13
SJ-20100603155704-018|2011-02-28(R2.0)
Note:
The item of CORBA Notify Service product is optional, thus enabling object
communications between different platforms and languages.
All other products must be selected.
7. Click Next, and the System information detection interface is opened, as shown in
Figure 2-21.
Figure 2-21 System information detection
8. Click the Next button to bring up the Installation Info Confirm interface, confirm the
products information.
9. Click Next, and the Unzip and Copy File interface is opened.
10. After the installation completes, click Next, and the Parameter Set interface is opened,
as shown inFigure 2-22.
2-14
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 2-22 Parameter Set
Parameters on this interface do not need to be configured, and you can select default
configuration for them.
11. Click Next to bring up the Confirm dialog box that inquires you whether to initialize all
client scenes, as shown in Figure 2-23.
Figure 2-23 Confirm
12. Click Next, and the System Initialization interface is opened.

13. After the initialization completes, click Next, and the Installation finished interface is
opened.
14. Click Finish, and the installation of programs completes.
End of Steps
2-15
SJ-20100603155704-018|2011-02-28(R2.0)
Example
Follow-Up Action
2.4 Port Offset Configuration

Abstract
When RCT is deployed as sharing the EMS server, port offset operations should be
executed.
To log in the system as a root user and modify the configuration files of RCT, as shown in
Table 2-1 and Table 2-2.
Table 2-1 Configuration File Table (1) of Port Offet
File Path
File Name
Modification
ums-server\utils\consol
deploy-console.properti
console.server-
e\conf
es
socket.port=32101
console.rmi.port=32102
10-rct-hostAgent.xml
<port>32103</port>
ums-server\utils\consol
deploy-console.properti
console.rmi.port=32106
e\works\console1\conf
es
console.serversocket.port=32103
ums-server\works\globa
usf.usf.ems.baseport=10000
deploy-usf.properties
usf.components.ftp.server.inter-
l\deploy
nalport=31111
/uep/snmpproxy/conf/V1/port=31165
/uep/snmpproxy/conf/V2C/port=31161
/uep/snmpproxy/conf/V3/port=31164
jboss.tomcat.http.internalport=31108
jboss.tomcat.https.internalport=31127
usf.components.clocksync.sync.internalport=31124
global-ftpserver-proxy.
Ftp.proxy.service.con-
properties
fig.port=31121
2-16
SJ-20100603155704-018|2011-02-28(R2.0)
File Path
File Name
Modification
ums-server\works\uep\d
deploy-web.properties
usf.core.web.base.port=31750
deploy-uep-port.propert
usf.core.uep.base.port=31400
eploy
ies
If RCT has been configured with SFTP, the configuration parameters of the 3 files under the
ums-server\works\sftpd\deploy directory should be modified, as shown in Table
2-2.
Table 2-2 Configuration File Table (2) of Port Offet
File Path
File Name
Modification
ums-server\works\sftpd
deploy-sftpd.properties
SFtpServer.server.config.port=31128
\deploy
deploy-sftpd-consoleage
usf.consoleagent.process.sftpd.
nt.properties
agent.serversocket.port=31128
deploy-sftpd-proxy.prop
SFtp.proxy.service.con-
erties
fig.port=31129
2.5 Configuration and Startup of MRM

The operation object of MRM (message routing module) is OMM.
Parameter configuration of MRM.

The config.properties file under the OMM installation directory ums-svr/tools/r
ct_v2_server_w/conf is opened. Each item should be configured. The config.pro
perties file is shown as the following:
#Thu May 20 15:58:06 CST 2010
bindAddr=127.0.0.1
port = 35059
ip_port=127.0.0.1:5057
Note:
The config.properties file is to configure the IP address of OMM, and the IP address
of RNC NE OMP. The MRM should be restarted if the configuration is valid.
1. Modify the bindAddr item: It indicates the IP address of the computer on which the
MRM runs, such as:
bindAddr=10.9.1.129
2-17
SJ-20100603155704-018|2011-02-28(R2.0)
the IP address of the OMM :10.9.1.129

2. port: It is the port of the computer on which the MRM runs. The port No. is 35059 by
default and does not need to be modified.
3. Modify the IP address of RNC NE OMP, such as:
ip_port=127.0.0.1:5057
The IP address of the OMP board is 127.0.0.1. The port No. is 5057.
Note:
The MRM is started automatically with the calling trace software, so it does not need to be
started manually.
Starting/Stopping of MRM
l
l
Interfaces started on Console: Start and stop signaling transfer on the Console.
No interface started on the Console:
Stop the MRM: Log in to Linux, enter the ums-svr/bin/consolemml directory,

and execute ums-svr/bin/consolemml.
Type Y and press Enter to restart the MRM, and the processes of the MRM will
be added to the Console.
2-18
SJ-20100603155704-018|2011-02-28(R2.0)
Chapter 3
Basic Operations
Table of Contents
Starting Calling Trace Software Server .......................................................................3-1
Starting Calling Trace Software Client .......................................................................3-3
Software Interface ......................................................................................................3-4
Network Element Management ..................................................................................3-6
Window ....................................................................................................................3-47
System Menu ...........................................................................................................3-53
3.1 Starting Calling Trace Software Server

Abstract
To introduce how to start the calling trace software server.
Note:
At present, the calling trace software is not integrated into NetNumen software, and it
needs to be installed independently. Therefore, it is not recommended to be used by
common users but only for advanced users in fault tracing and locating.
Prerequisites
The server and the client of the calling trace software are installed.
Steps
1. There are three modes of starting the calling trace software server.
a. The installation program directory is opened, and double-click the file \ums-ser
ver\console.bat under the program directory.
b. The system generates a shortcut Network Mage Console after the calling trace
software is installed. Double-click to start the server, as shown in Figure 3-1.
3-1
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-1 Network Manage Console Shortcut Icon
c. After the calling trace software is installed, the system will automatically add the
startup program to Start > Program. Click Network Manage System Console
to start the program, as shown in Figure 3-2.
Figure 3-2 Network Manage Console Startup Menu
2. The Network Manage Console interface is opened, all processes of the server are
started automatically and successfully, and the server is started successfully, as shown
in Figure 3-3.
Figure 3-3 Starting Server Processes
Tip:
All processes of the server must be started successfully.
End of Steps
Follow-Up Action
l
If it is necessary to stop a process, select this process and click
3-2
SJ-20100603155704-018|2011-02-28(R2.0)
If it is necessary to start a process, select this process and click
Note:
UEP Process and RCT Process can be started or stopped separately by selecting
or
.
3.2 Starting Calling Trace Software Client

Abstract
To introduce how to start the calling trace software client.
Prerequisites
The calling trace software server is started.
Steps
1. There are three modes of starting the calling trace software client:
a. The installation program directory is opened. Double-click the file \ums-client
\client.exe under the program directory.
b. The system will generate a shortcut Network Manage System Client on the
desktop after the calling trace software is installed. Double-click the shortcut to
start the client, as shown in Figure 3-4.
Figure 3-4 NMS Client Shortcut Icon
c. After the calling trace software is installed, the system will automatically add a
startup program to Start > Program. Click Network Manage System Client to
start the program, as shown in Figure 3-5.
Figure 3-5 NMS Client Starting Menu
2. The Login interface pops up, and input corresponding information, as shown in Figure
3-6.
3-3
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-6 Login
3. Click OK. The NetNumen Unified Management System interface pops up, and the
client is started successfully, as shown in Figure 3-7.
Figure 3-7 NetNumen Unified Management System
End of Steps
3.3 Software Interface

The calling trace software interface is shown as Figure 3-8.
3-4
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-8 Calling Trace Interface Description
1. System menu bar

2. Tool bar
3. Tree node window

4. Working area
5. Message checking window

6. Status bar
As shown in Figure 3-8, the calling trace software interface consists of six parts. The
function of every part is described as below:
1. System menu bar
The calling trace software system menu is available to the system menu bar. Users
can complete operation tasks of calling trace through the system menu.
2. Tool bar
Shortcut operation icons of the calling trace software are available to the tool bar.
There are six shortcut icons provided by the system at present, as shown in Table 3-1.
Table 3-1 Shortcut Introduction
Name
Short Icon
Logout
Locking Screen
Window Exit
Window Forward
User Trace
NE Management
3. Tree Node Window
3-5
SJ-20100603155704-018|2011-02-28(R2.0)
The command tree structure of present functional modules is available to the tree node
window. Right-click a single operation command in the tree node, and the system will
execute this operation.
4. Working area
The working area falls into Signaling > Measurement > Task Management, which
displays signaling information, measurement report and task list of present tracing
tasks.
5. Message checking window
The message checking window displays interaction message generated by the
communication between the calling trace client and the foreground NE. The interaction
message includes prompt message and error message.
6. Status bar
The tool bar displays communication status of the calling trace software client and
foreground NE.
3.4 Network Element Management

On the Network Element Management interface, users can complete such operations as
adding, deleting and modifying RNC, connecting link and disconnecting link.
Note:
Operations on the Network Element Management interface are only to be performed on
RNC information of the calling trace software, which does not change the actual RNC.
3.4.1 Entering NE Management Interface

Abstract
The NE Management interface is opened in the calling trace software.
Steps
1. In the software main interface, you can enter the NE management interface in two
modes, as shown in Figure 3-9.
3-6
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-9 NE management
l
l
Click , and the NE management interface pops up.

Select Maintenance > Management, and the NE management interface pops
up, as shown in Figure 3-10.
Figure 3-10 Selecting NE Management
End of Steps
3.4.2 Adding NE
Abstract
To add RNC (NE) information according to IP address and port number of RNC, and to
provide a prerequisite for setting up physical links.
Steps
1. The NE Management interface is opened. You can add NE through the following two
methods:
3-7
SJ-20100603155704-018|2011-02-28(R2.0)
l
l
Click .
Right-click to select Add from the drop-down menu, as shown in Figure 3-11
Figure 3-11 Add NE
2. The Add interface pops up, as shown in Figure 3-12.

Figure 3-12 Add NE
l
l
l
NE name: users can input NE name manually, but it can not be duplicated with
the name of the existing NEs.
ID: input RNCID.
Type: by default.
3-8
SJ-20100603155704-018|2011-02-28(R2.0)
l
l
Link type: by default.

IP address:
RCT connects to NEs directly: Type the IP address of the OMP.
RCT connects to NEs through MRM: Configure the IP address as the IP

address where the MRM resides. It is also the binding IP address configured
in the Configuration and Startup of MRM section.
Port Number:
RCT connects to NEs directly: Type 5057 by default.
RCT connects to NEs through MRM: Configure the port as the monitoring
port (35059 by default) of the computer on which the MRM resides.
3. Click OK, and adding NE completes.

End of Steps
3.4.3 Deleting NE
Prerequisites
In the calling trace software system, there is an RNC NE) message needs to be deleted,
and this NE is disconnected.
Steps
1. Select the NE information to be deleted from the NE Management interface.
2. You can delete an NE through the following two mode:
l Click .
l Right-click to select Delete from the drop-down menu, as shown in Figure 3-13
Figure 3-13 Deleting NE Menu
3-9
SJ-20100603155704-018|2011-02-28(R2.0)
3. The Confirm window pops up. Click Yes to delete, as shown in Figure 3-14.
Figure 3-14 Confirm
End of Steps
3.4.4 Modifying NE
Abstract
To modify parameters of RNC (NE) information added by users.
Prerequisites
A piece of RNC (NE) information to be modified exists in the system, and this NE is
disconnected.
Steps
1. Select the information to be modified from the NE Management interface.
2. You can modify NE information in the following two methods:
l Click .
l Right-click to select Modify from the drop-down menu, as shown in Figure 3-15
Figure 3-15 Modifying NE
3-10
SJ-20100603155704-018|2011-02-28(R2.0)
3. The Add window pops up. Users can add NE information as needed, as shown in
Figure 3-16.
Figure 3-16 Add NE Window
4. Click OK, and NE information is added.

End of Steps
3.4.5 Link Operation

To connect to RNC before you using the calling trace system. Link operation relating to
RNC contains setting up link and interrupting link.
3.4.5.1 Connecting Link

Abstract
To connect socket link to RNC (NE) according to the added RNC (NE), and to connect
physical link for transmission of control information and data information.
Prerequisites
Relative NE information is added to NE Management.
Steps
1. Select an NE to be link connected, and set up links for this NE in the following two
modes:
3-11
SJ-20100603155704-018|2011-02-28(R2.0)
l
l
click .
Right-click to select connect from the drop-down menu, as shown in Figure 3-17.
2. Connecting link succeeds once the status of the selected NE has changed from 0 to
1, as shown in Figure 3-17.
Figure 3-17 NE Connecting Link
End of Steps
3.4.5.2 Disconnecting Link

Abstract
To release link connection between NM software and RNC (NE), and to release the socket
link occupied by the software client.
After the link is disconnected, status of all calling trace tasks relating to this NE will be
changed into Suspend. If it is recovered to link of corresponding NEs, the corresponding
task status will return to Run.
Steps
1. Select the NE whose link needs to be disconnected, and you can disconnect its link in
the following two modes:
3-12
SJ-20100603155704-018|2011-02-28(R2.0)
l
l
Click .
Right-click to select disconnect, as shown in Figure 3-18.
Figure 3-18 Disconnecting Link
2. If NE status of the selected NE has changed from 1 to 0, the link is disconnected

successfully, as shown inFigure 3-19.
Figure 3-19 Disconnecting NE Link
End of Steps
3.4.6 User Tracing

The user tracing interface is to complete such operations as setting up, managing,
modifying, deleting and monitoring of trace tasks.
3-13
SJ-20100603155704-018|2011-02-28(R2.0)
3.4.6.1 Entering Subscriber Trace

Abstract
To introduce how to enter the subscriber trace interface.
Steps
1. In the calling trace software, you can enter Subscriber Trace in the following two
methods:
l Click the
button on the tool bar.
l
Select Maintenance > Subscriber Trace, as shown in Figure 3-20.
Figure 3-20 Subscriber Trace Menu Bar
2. The Subscriber Trace interface pops up, as shown in Figure 3-21.

Figure 3-21 Subscriber Trace
End of Steps
3-14
SJ-20100603155704-018|2011-02-28(R2.0)
3.4.6.2 Creating Tasks

Abstract
Users need to create a tracing task before executing calling trace tasks. The status of the
default task is Suspend after the task is created. Users only start corresponding tracing
tasks when it is necessary to execute the tracing task.
Prerequisites
An NE is created and communication links are established successfully.
Steps
1. Double-click Create Task on the Subscriber Trace node at the right side of the
interface, as shown in Figure 3-22.
Figure 3-22 Creating Task Node
2. The Create Task interface pops up, as shown in Figure 3-23.
3-15
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-23 Create Task
l
l
Task Name: Type the created tasks name, which can not be duplicated with that
of the existings.
Select the object type of tasks to be created from the pull-down menu of Task
Type.
3. Click Next to select NE and sub-task type that belong to the task, and click Add in the
Sub Task Type tab to be traced, as shown in Figure 3-24.
3-16
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-24 Selecting NE and Sub Task Type
l
l
Note:
To select the NE of creating a task in NE List. If the task relates to multiple NEs,
it needs to be created in every NE.
To select the type of creating sub-tasks in Sub-task Type.
4. Set task parameters, and click Finish to complete task creation.

End of Steps
3.4.6.3 Managing Trace Tasks

Abstract
To query trace tasks as needed in user-created trace tasks.
3-17
SJ-20100603155704-018|2011-02-28(R2.0)
Steps
1. Double-click Trace Task Management on the Subscriber Trace tree node at the right
side of the interface, as shown in Figure 3-25.
Figure 3-25 Trace Task Management
2. The Task List window pops up. Select different tasks to check their properties, as
Figure 3-26 Task List
End of Steps
3.4.6.4 Starting Tasks

Abstract
As needed, to manually start the trace task in the trace tasks created by users.
stop due to link broken, but the trace task will be restarted once the link is restored.
3-18
SJ-20100603155704-018|2011-02-28(R2.0)
Users either start a single sub-task or start all sub-tasks of a certain object task once.
Steps
1. Select the trace tasks to be started in the Task List window. Right-click to select Start
Task from the drop-down menu, as shown in Figure 3-27.
Figure 3-27 Starting Tasks
Note:
Users either start a single sub-task or start all sub-tasks of this task once by starting
the object task.
2. The trace task completes automatically once Task Status is changed from Stop to
Start in Task List.
3-19
SJ-20100603155704-018|2011-02-28(R2.0)
Note:
The created and started tasks on the server are displayed on the client that have
access to the server.
End of Steps
3.4.6.5 Stopping Tasks

Abstract
To stop the started tracing tasks.
As for the started tracing task, if its link is interrupted, the system will automatically change
its status from START to STOP.
Users either stop a single sub-task or stop all sub-tasks of a certain object task.
Steps
1. Select the tracing tasks to be suspended in the Task List window. Right-click to select
Stop Task from the drop-down menu, as shown in Figure 3-28.
Note:
Users either select stopping a single sub-task or select stopping all sub-tasks of this
object task once by stopping the object task.
3-20
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-28 Stopping Tasks
2. Task stopping completes if Task Status is changed from START to STOP in Task List.
End of Steps
3.4.6.6 Monitoring Tasks

Abstract
To monitor the started tasks.
Steps
1. Select the tasks to be monitored in the Task List window, and right-click to select
Monitor from the drop-down menu, as shown in Figure 3-29.
3-21
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-29 Monitor
2. Two kinds of Window pop up according to different sub-tasks created.

l Signaling trace task: The Signaling Trace Task window is displayed in Signaling
Working Area, and the signaling trace task can be checked in the Signaling tab,
3-22
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-30 Signaling Trace Window
Note:
You can check the detailed information of a signaling through doubleclicking it
in Signaling Trace Task .
Measurement trace task: the Measurement Trace Task window is displayed in

Measurement Working Area, and measurement trace task can be checked in
the Measurement tab, as shown in Figure 3-31.
3-23
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-31 Measurement Trace Window
End of Steps
3.4.6.7 Viewing Data

Abstract
To view the signaling trace files of a single task saved on the server, and to download and
to save them to the local client as needed.
Prerequisites
The signaling trace files are saved on the server.
Steps
1. In the Task List window, select a task to be viewed, and right-click to select View Data
from the drop-down menu, as shown in Figure 3-32.
3-24
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-32 View Data
2. A View Data dialog box pops up, as shown in Figure 3-33.

Figure 3-33 View Data Dialog Box
3. Choose a data file. Click Show, a Monitor interface of tasks pops up, and you can
view the detailed calling trace data.
3-25
SJ-20100603155704-018|2011-02-28(R2.0)
Note:
Operations of viewing calling trace data, refer to the Signaling Trace Task
Management section.
End of Steps
Example
Follow-Up Action
l
l
Click Download, and the data file selected can be saved locally.
Click Download All, and all data files under this task can be saved locally.
3.4.6.8 Signaling Trace Task Management
Note:
Signaling trace management needs to be operated under the monitoring mode after the
task is started. Users select a task in the task list, and right-click to select Monitor from
the pull-down menu.
After users have started a signaling trace task, RNC will periodically report signaling trace
information which is set on the signaling trace task.
The operation control signalings displaying and saving mode in the signaling display
window can be achieved via such operations as saving, searching, filtering, starting
monitor, stopping monitor, suspending refreshing, full screen displaying code source,
detailed decoding, deleting all and suspending scrolling, etc. These operations are only
available to signaling trace tasks.
3.4.6.8.1 Signaling Trace Tool-bar Introduction
Abstract
To introduce every buttons function on the tool-bar of the signaling trace window in the
monitoring mode.
The Monitor window is opened. If signaling trace tasks are created by users, the tool bar
is shown asFigure 3-34, and every buttons function is shown as Table 3-2.
Figure 3-34 Tool-bar Introduction
3-26
SJ-20100603155704-018|2011-02-28(R2.0)
Table 3-2 Tool-bar Button Introduction

Operation
Icon
Save all
Effect
Description
To save all signaling on
None
the interface, and the

output format is csv.
Save selected
To save the selected
None
signaling on the
interface, and the output
format is csv.
Search
According to the
The shortcut is
displayed columns
Ctrl+F.
name, search from the

selected signaling to
the downward. It will
automatically shift to the
top when it searches to
the bottom.
Filter
To filter according to
Filtering results will
the filtering conditions
be displayed in a new
selected by users, and
window.
its result is displayed

in the new created
interface.
Start monitor
To monitor tasks.
The task is monitored
Stop monitor
To stop monitoring
The task is stopped
tasks.
monitoring.
Interface
None
Pause/Restore refresh
stopped/Restore
refreshing
Full screen/Exit full
The interface is
screen
displayed in full
None
screen/To restore from

full screen to non full
screen.
Code source
To display code source
Double-click one
of the present selected
signaling also triggers
signaling.
code source.
3-27
SJ-20100603155704-018|2011-02-28(R2.0)
Operation
Icon
Specific decoding
Delete all
Effect
Description
To display specific
Double-click one
decoding information of
signaling also triggers
signaling data.
code source.
To delete all signaling
Irreversible operation.
on the interface.
Pause/Restore scroll
The table displays
None
switching to
automatically
scroll/Stopping
automatically scroll.
3.4.6.8.2 Saving All
Abstract
To save all signaling in the file format of *.csv.
Note:
Signaling information is the operation object of saving all signaling. It is generated from
present signaling trace tasks that are selected by users.
Steps
1. The Signaling window is opened. You can save all by using the following methods:
l Click .
l Right-click to select Save All from the pull-down menu, as shown in Figure 3-35
3-28
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-35 Save All
2. The Save dialog box pops up. Set the filename and saving path, and the system will
save all selected signaling information in the format of *.csv after clicking the Save
button, as shown in Figure 3-36.
Figure 3-36 Setting Save Path
End of Steps
3-29
SJ-20100603155704-018|2011-02-28(R2.0)
3.4.6.8.3 Saving Signaling Selected
Abstract
To select the signaling to be saved in the file format of *.csv.
Note:
Signaling information is the operation object of saving the signaling selected.
generated from present signaling trace tasks that are selected by users.
It is
Prerequisites
In the signaling trace system, there is signaling information to be saved.
Steps
1. The Signaling window is opened. Either press Shift to select multiple continuous
signaling information or press Ctrl to select multiple signaling information in each
section.
2. Save the signaling selected through the following two methods.
l Click
under the signaling window.
l Right-click to select Save Selected from the pull-down menu, as shown in Figure
3-37.
Figure 3-37 Saving Selected Signaling
3-30
SJ-20100603155704-018|2011-02-28(R2.0)
3. The Save dialog box pops up. Set the filename and saving path, and the system
will automatically save the selected signaling information in the format of *.csv after
clicking the Save button, as shown in Figure 3-38.
Figure 3-38 Setting Save Path
End of Steps
3.4.6.8.4 Searching
Abstract
According to the searching condition set by users, to search signaling information that is
compliant with the condition in the signaling display window.
Prerequisites
In the signaling tracing system, and there is signaling information to be searched.
Steps
1. The Signaling Trace window is opened. You can search signaling through the
following two methods:
l Click .
l Right-click to select Search from the pull-down menu, as shown in Figure 3-39
3-31
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-39 Search
2. The Search dialog box pops up. After setting searching condition, click the Search
button and the system will locate the signaling information that is compliant with the
searching condition in the Signaling Trace window Figure 3-40, as shown in Figure
3-40.
Figure 3-40 Setting Search Condition
End of Steps
3-32
SJ-20100603155704-018|2011-02-28(R2.0)
3.4.6.8.5 Filtering
Abstract
The signaling information in accord with the filtering conditions is displayed in the
Signaling Display window according to the filtering conditions preset.
Prerequisites
In the signaling trace system, and there is signaling information to be filtered.
Steps
1. The Signaling Trace window is opened. You can execute filtering operations through
the following two methods:
l Click .
l Right-click to select Filter from the pull-down menu popped up, as shown in Figure
3-41
Figure 3-41 Filtering
2. The Filter dialog box pops up. After setting the condition of displaying filtering, click
the OK button and the system will display the signaling result that is compliant with the
filtering conditions, as shown in Figure 3-42.
3-33
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-42 Setting Filter Conditions
You can right-click
or
to add or delete filtering conditions.
End of Steps
3.4.6.8.6 Starting Monitor
Abstract
To start monitoring the stopped signalling trace tasks.
Note:
Monitoring is running on the calling trace server after the signaling trace task is started. Its
effect is to display the traced signaling on the client.
Prerequisites
In the signaling trace system , there is signaling information stopped.
The Starting Monitor button can not be operated because tasks are in monitoring status.
3-34
SJ-20100603155704-018|2011-02-28(R2.0)
Steps
1. The Signaling Trace window is opened. You can start to monitor through the following
two methods:
l Click .
l Right-click Start Monitor, as shown in Figure 3-43
Figure 3-43 Starting Monitor
End of Steps
3.4.6.8.7 Stopping Monitor
Abstract
To stop monitoring of signaling trace tasks in execution.
Note:
To stop monitoring that does not affect signaling trace tasks and does not stop running of
tasks.
Prerequisites
There is signaling information running in the signaling trace system.
Tasks are stopped monitoring, and they are unavailable.
3-35
SJ-20100603155704-018|2011-02-28(R2.0)
Steps
1. The Signaling Trace window is opened. You can stop monitoring through the following
two methods:
l Click .
l Right-click to select Stop Monitor from the pull-down menu, as shown in Figure
3-44
Figure 3-44 Stopping Monitor
End of Steps
3.4.6.8.8 Suspending Or Restoring Refreshing
Abstract
To suspend or restore signaling display function reported from RNC, and the signaling
trace system also suspends saving the signaling information of signaling display window.
Prerequisites
The signaling trace system is running properly and connecting to RNC, and there are
started signaling tracing tasks relating to this NE.
Steps
l
Suspend refreshing: the Signaling Trace window is opened. The system will
automatically suspend the display function of signaling reported from RNC, and
suspend displaying the signaling information of the Signaling Trace window after
you suspend refreshing through the following two methods:
3-36
SJ-20100603155704-018|2011-02-28(R2.0)
l
l
Click .
Right-click to select Suspend from the pull-down menu, as shown in Figure 3-45
Figure 3-45 Suspend Refreshing
Restore refreshing: in suspend refreshing status, re-click

to restore the displaying
function of signaling reported from RNC, and the system will also restore saving
signaling information of the Signaling Trace window.
End of Steps
3.4.6.8.9 Displaying In Full Screen
Abstract
The signaling trace task window is displayed in full screen.
Steps
1. The Signaling Trace window is opened. You can display the tracing task in full screen
through the following two methods:
l Click .
l Right-click to select Full Screen from the pull-down menu, as shown in Figure
3-46
3-37
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-46 Full Screen Displaying
2. The Signaling Trace window is displayed in full screen.

3. Re-click the button
to restore the Signaling Trace window to its original size.
End of Steps
3.4.6.8.10 Original Code Stream
Abstract
To display original code stream of the selected signaling.
Steps
1. Select a single signaling in the Signaling Trace window. You can display the original
code stream through the following two methods:
l Click .
l Right-click to select Flow Source from the pull-down menu, as shown in Figure
3-47
3-38
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-47 Selecting Flow Source
2. Under the Signaling Trace window, the Flow Source tab pops up, as shown in Figure
3-48.
Figure 3-48 Flow Source Window
End of Steps
3.4.6.8.11 Detailed Decoding
Abstract
To display all detailed decoding of the selected signaling.
3-39
SJ-20100603155704-018|2011-02-28(R2.0)
Steps
1. The Signaling Trace window is opened. You can display the detailed decoding
through the following two methods:
l Select a single signaling , and click .
l
After selecting a single signaling, right-click to select Detailed Decoding from
the pull-down menu, as shown in Figure 3-49
Figure 3-49 Detailed Decoding
2. Under the Signaling Trace window, the Detailed Information tab pops up, as shown
in Figure 3-50.
3-40
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-50 Detailed Decoding Window
End of Steps
3.4.6.8.12 Deleting All
Abstract
To delete all signaling on the interface, which does not affect running of signaling trace
tasks.
Prerequisites
In the signaling trace system, there is signaling information to be deleted.
Steps
1. The Signaling Trace window is opened, you can delete signaling through the following
two methods:
l Select a signaling, and click .
l Right-click to select Delete All from the pull-down menu, as shown in Figure 3-51
3-41
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-51 Delete All
2. All signaling is deleted from the Signaling Trace window.
Note:
This operation procedure is irreversible.
This procedure is to delete the signaling displayed in the monitoring mode, which does
not delete the signaling files in the signaling trace task.
End of Steps
3.4.6.8.13 Suspending Or Restoring Scrolling
Abstract
To set the displaying mode of signaling in the window.
To set the system whether automatically scroll to display the last record of signaling in the
window.
3-42
SJ-20100603155704-018|2011-02-28(R2.0)
Note:
Suspend or restore scrolling is different from suspend refreshing as the following:
l
l
Suspend refreshing: Stop the display function of signaling reported from RNC, the
system suspends displaying signaling information.
Suspend scrolling: Suspend scroll displaying of signaling information only, which does
not affect RNC reporting signaling.
Prerequisites
The signaling trace system is running properly and connecting to RNC, and there are
started signaling trace tasks relating to this RNC in the system.
Steps
1. Suspend scrolling: the Signaling Trace window is opened. The system will scroll
to display the last signaling record of Signaling Trace after you suspend signaling
information in the following two methods:
l Click .
l Right-click to select Suspend Scroll from the pull-down menu, and , as shown in
Figure 3-52
Figure 3-52 Suspend Scrolling
3-43
SJ-20100603155704-018|2011-02-28(R2.0)
2. Return to scrolling: in suspend scrolling status, click , and the system will restore
scrolling to display the last record of the Signaling Trace window.
End of Steps
3.4.7 Opening Data File

Abstract
To open signaling trace files.
Suffix format of calling tracing files is *.csv.
Steps
1. Double-click Open data file in the Subscriber Trace tree node of the left pane, as
Figure 3-53 Opening Data File
2. Select the signaling trace file saved in the system, and its format is .csv, as shown in
Figure 3-54.
3-44
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-54 Selecting Data File
3. The defined signaling trace file is opened, as shown in Figure 3-55.

Figure 3-55 Opening Signaling Trace File
End of Steps
3.4.8 Setting Client Parameters

Abstract
To set parameters for the data table of the client.
3-45
SJ-20100603155704-018|2011-02-28(R2.0)
Steps
1. Double-click the Set Client Parameter node under Subscriber Trace of the left pane,
Figure 3-56 Set Client Parameter
2. The Local Setting window pops up, and users can set data table capability, as shown
in Figure 3-57.
Figure 3-57 Local Setting
End of Steps
3.4.9 Viewing Trace Files Offline

Abstract
When the client can not be connected to the server, RCT supports offline checking the
signaling trace files.
Note:
Operations of offline viewing trace files can only be performed under the environment of
the Windows operation system.
3-46
SJ-20100603155704-018|2011-02-28(R2.0)
Prerequisites
Latest decoding database files have been installed.
Context
Steps
1. Run the run.bat file under the installation ums-client\tools\rct-offline
directory of the RCT, and a language select dialog box pops up, as shown in Figure
3-58.
Figure 3-58 language select
2. Select the language to be displayed. Click OK, the RCT Offline View Toll window
pops up, select the .csv file to be read as needed.
3. Click File > Open, and the Open window pops up
End of Steps
Follow-Up Action
For the specific operations (after the .csv file has been opened), refer to the Signaling
Trace Task Management section.
3.5 Window
Function of windows is to set switching among multiple functional windows.
As needed, users can open and close windows and the defined view bars in the function
of windows.
3.5.1 Switching Window

Abstract
To describe switching among multiple functional windows in the calling trace software.
Prerequisites
In the calling trace software system, there are more than two functional windows.
3-47
SJ-20100603155704-018|2011-02-28(R2.0)
Steps
1. There are three modes of switching among multiple windows in the calling trace
software:
and
to achieve
l Click Window > Back, and Window > Forward or click
switching between two neighbor windows, as shown in Figure 3-59.
Figure 3-59 Window Switching Menu
l
l
Directly select window to be displayed in the Window menu

Click the drop-down menu on the upper right of the calling trace software interface. Select a window to be displayed as needed from the multiple opened
functional menus, as shown in Figure 3-60.
Figure 3-60 Pull-down Menu
End of Steps
3.5.2 Opening and Closing Toolbar

Steps
1. The Calling Trace Software interface is opened and select Window > Toolbar. The
system will close the toolbar if it is displayed before being selected, and the system will
display the toolbar if it is not displayed before being selected, which is called closing
and opening operation, as shown in Figure 3-61.
3-48
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-61 Opening Toolbar
2. The system executes opening or closing operation of the toolbar, as shown in Figure
3-62.
Figure 3-62 Closing Toolbar
End of Steps
3.5.3 Opening and Closing Statusbar

Prerequisites
The calling trace software is running properly.
Steps
1. The Calling Trace Software interface is opened, and select Window > Status Bar.
The system will close the statusbar if it is displayed before being selected, and the
system will display the statusbar if it is not displayed before being selected, which is
called closing and opening operation, as shown in Figure 3-63.
3-49
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-63 Opening Status Bar
2. The system executes opening and closing operation of the statusbar, as shown in
Figure 3-64.
Figure 3-64 Closing Status Bar
End of Steps
3.5.4 Opening and Closing Message Checking

Prerequisites
3-50
SJ-20100603155704-018|2011-02-28(R2.0)
Steps
1. The Calling Trace Software interface is opened, and select Window > Message
Area. The system will close the message area if it is displayed before being selected,
and the system will display the message area if it is not displayed before being
selected, which is called closing and opening operation, as shown in Figure 3-65.
Figure 3-65 Closing Message Checking
2. The system executes opening and closing operation of message checking, as shown
in Figure 3-66.
Figure 3-66 Opening Message Checking
3-51
SJ-20100603155704-018|2011-02-28(R2.0)
Different message can be checked separately through the Hint Message tab and the
Error Message tab in the Show Message window.
End of Steps
3.5.5 Closing Windows

Abstract
To close each window displayed in the calling trace software.
Prerequisites
There are windows displayed in the calling trace software system.
Steps
1. You can close windows in the following two modes:
l Click Window > Close Current window , and click Close All Windows or Close
Other Windows to close the windows displayed, as shown in Figure 3-67.
Figure 3-67 Closing Window Operation
Click on the upper right corner of the calling trace software interface to close
the current windows, or select from the pull-down menu of Close, as shown in
Figure 3-68.
3-52
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-68 Close Menu
Close current window: currently displayed window.
Close all windows: all opened windows in the software.
Close other windows: save currently displayed windows and close

non-displayed windows on the interface.
End of Steps
3.6 System Menu

Users can lock screen, set printing, customize, check system time, log out and exit system
through the system menu.
3.6.1 Locking Screen

Abstract
To lock the calling trace client, users have to re-login if they want to reuse it.
Steps
1. The Calling Trace Software interface is opened. You can lock screens in the following
two modes:
l Click the System > Lock Screen menu, as shown in Figure 3-69.
Figure 3-69 Lock Screen
Click the
button on the toolbar.
2. The Select Lock Type window pops up, as shown in Figure 3-70.
3-53
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-70 Select Lock Type
l
l
Lock Screen: current interface is invisible, and the Lock Screen interface pops
up. It is unlocked by inputting password.
Lock Operation : current operation interface is visible. Press Ctrl+U and the Lock
Screen interface pops up to unlock.
3. Click OK, and the Confirm window pops up, as shown in Figure 3-71.
Figure 3-71 Confirm Window
4. Click OK, and the Lock Screen window pops up, and the screen is locked, as shown
in Figure 3-72.
Figure 3-72 Lock Screen Window
End of Steps
3-54
SJ-20100603155704-018|2011-02-28(R2.0)
3.6.2 Setting Print

Abstract
To print signaling trace files.
Prerequisites
There are signaling files need to be printed in the calling trace software system.
Steps
1. The calling trace software is opened. Click System > Print Setup, as shown in Figure
3-73.
Figure 3-73 Print Setup
2. The Print Setup window pops up, as shown in Figure 3-74.

Figure 3-74 Print Setup Interface
3-55
SJ-20100603155704-018|2011-02-28(R2.0)
To set printing according to different requirements in these three tabs of General, Page
Setup, and Advanced.
3. Click OK to start printing.
End of Steps
3.6.3 User Customizing

Users can set the system, login information, and holiday configuration through the User
Customize menu.
3.6.3.1 Setting the System

Abstract
To set system parameters in the System window as needed.
Prerequisites
Steps
1. The Calling Trace Software interface is opened. Click System > User Customize >
System Setting, as shown in Figure 3-75.
Figure 3-75 System Setting Menu
2. The System Setting window pops up, as shown in Figure 3-76.
3-56
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-76 System Setting Window
l
l
l
l
The Auto Screen Lock Time tab: select whether to start Auto Locking Screen,
and set locking time and mode.
The Auto Logout tab : select whether to start Auto Logout, and set waiting time.
The Message Area tab : set hint message and error message shown in the
Signaling Tracing window.
The Query Settings tab : set querying result quantity shown in each page in
querying tables.
End of Steps
3.6.3.2 Setting Login User Information

Abstract
To set login user information in the system window.
Steps
1. The Calling Trace Software interface is opened. Click System > User Customize >
Login User Info Setting, as shown in Figure 3-77.
3-57
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-77 Login User Info Setting Menu
2. The Login User Info Setting window pops up, as shown in Figure 3-78.
Figure 3-78 Login User Info Setting Window
End of Steps
3.6.3.3 Configuring Holiday

Abstract
To configure holiday in the System window.
Prerequisites
Steps
1. The Calling Trace Software view is opened. Click System > Customize > Holiday
Configuration, as shown in Figure 3-79.
3-58
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-79 Holiday Configuration
2. The Holiday Configuration window pops up, as shown in Figure 3-80.

Figure 3-80 Holiday Configuration Window
3. Click New, the Holiday dialog box pops up, and fill in the holiday configuration
information as needed, as shown in Figure 3-81.
3-59
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-81
Alternatively, you can click Modify and Delete to configure the holiday separately.
End of Steps
3.6.4 Setting User Password

Abstract
To set user password.
Prerequisites
To set the user password for logging in to the client in the calling trace software system..
Steps
1. The Calling Trace Software view is opened.
Setting, as shown in Figure 3-82.
Click System > User Password
3-60
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-82 User Password Setting
2.
The User Password Setting dialog box pops up, as shown in Figure 3-83.
Figure 3-83 User Password Setting Window
You can set the password manually.

3. Click OK, and the password setting completes.
End of Steps
3.6.5 Querying System Time

Abstract
To query system time of the server and the client, and to make a comparison.
Steps
1. The Calling Trace Software interface is opened. Click the System > Query System
Time menu, as shown in Figure 3-84.
3-61
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-84 Query System Time
2. The Query System Time window pops up, as shown in Figure 3-85.
Figure 3-85 Query System Time Window
End of Steps
3.6.6 Logging Out

Abstract
To log out the client of the calling trace software.
Steps
1. The Calling Trace Software interface is opened. You can log out the client in the
following two modes:
l Click System > Logout, as shown in Figure 3-86.
3-62
SJ-20100603155704-018|2011-02-28(R2.0)
Figure 3-86 Logout Menu
Click
on the toolbar.
2. The Confirm dialog box pops up. Click OK to log out the system..
End of Steps
3.6.7 Exiting The System

Abstract
Exiting the system is to introduce how to exit the calling trace software system.
The system will automatically switch off all communication links, save and close all files
opened, when users are exiting the calling trace software system.
Steps
1. The Calling Trace Software interface is opened. Click System > Exit, and the system
will be closed, as shown in Figure 3-87.
Figure 3-87 Exit System
End of Steps
3-63
SJ-20100603155704-018|2011-02-28(R2.0)
3-64
SJ-20100603155704-018|2011-02-28(R2.0)
Appendix A
Troubleshooting
Table of Contents
Task Status Is Starting ............................................................................................ A-1
Software Server can not be Started ........................................................................ A-1
A.1 Task Status Is Starting

Problem
Task Status is Starting in Task List.
Solution
Task Status is STARTING indicating that this task is in starting status, and it is ineffective
to restart this task at this time. To stop this task and to restart it when Task Status is
returned to STOP.
A.2 Software Server can not be Started

Problem
The calling trace software server can not be started properly.
Solution
l
Either main processes can not be started or all operations can not be used even
starting succeeds.
1. Check specific operation information of main processes to see whether a hint is
showing that the database can not be connected, as shown in Figure A-1.
A-1
SJ-20100603155704-018|2011-02-28(R2.0)
Figure A-1 Process Operation Specific Information
2. Right-click My Computer > Management > Service and Application Program

> Service to see whether the calling trace software service and monitoring of the
database are started, as shown in Figure A-2.
Figure A-2 Service Window
3. If calling trace software service and monitoring of the database are started already,
stop and restart them.
4. If the FTP process can not be started, check your computers IP address to
see whether it is the same as the IP address on the console of the calling trace
software server, as shown in Figure A-3.
A-2
SJ-20100603155704-018|2011-02-28(R2.0)
Appendix A Troubleshooting
Figure A-3 Server Console IP
If they are different, which means that the IP address of your computer is different
from the binding IP address when the software is being installed. Therefore, to
modify your computers IP address to its original.
A-3
SJ-20100603155704-018|2011-02-28(R2.0)
A-4
SJ-20100603155704-018|2011-02-28(R2.0)
Figures
Figure 1-1 Client-Server-NE Mode ............................................................................ 1-2
Figure 1-2 Calling Trace Software Structure.............................................................. 1-2
Figure 1-3 Installing Calling Trace Software Server Independently............................ 1-4
Figure 1-4 Calling Trace Software Server is Integrated Into EMS Server................... 1-5
Figure 1-5 The Calling Trace Software is Deployed at Local NE ............................... 1-7
Figure 1-6 Calling Trace Task Life Cycle ................................................................... 1-8
Figure 2-1 Modifying Processes................................................................................ 2-2
Figure 2-2 Select Language...................................................................................... 2-3
Figure 2-3 Select Installation Style ............................................................................ 2-3
Figure 2-4 Network scale .......................................................................................... 2-4
Figure 2-5 Select product.......................................................................................... 2-4
Figure 2-6 Database connection config ..................................................................... 2-5
Figure 2-7 UCA config in Database config ................................................................ 2-6
Figure 2-8 Database config....................................................................................... 2-6
Figure 2-9 Host information config ............................................................................ 2-7
Figure 2-10 System information detection ................................................................. 2-8
Figure 2-11 Unzip and Copy File............................................................................... 2-8
Figure 2-12 Confirm .................................................................................................. 2-9
Figure 2-13 Installation database .............................................................................. 2-9
Figure 2-14 Parameter Set...................................................................................... 2-10
Figure 2-15 Confirm ................................................................................................ 2-10
Figure 2-16 System Initialization ............................................................................. 2-11
Figure 2-17 Installation Finished ............................................................................. 2-11
Figure 2-18 Select language ................................................................................... 2-12
Figure 2-19 Select Installation Style ........................................................................ 2-13
Figure 2-20 Select product...................................................................................... 2-13
Figure 2-21 System information detection ............................................................... 2-14
Figure 2-22 Parameter Set...................................................................................... 2-15
Figure 2-23 Confirm ................................................................................................ 2-15
Figure 3-1 Network Manage Console Shortcut Icon .................................................. 3-2
Figure 3-2 Network Manage Console Startup Menu.................................................. 3-2
Figure 3-3 Starting Server Processes ....................................................................... 3-2
I
Figure 3-4 NMS Client Shortcut Icon......................................................................... 3-3

Figure 3-5 NMS Client Starting Menu........................................................................ 3-3
Figure 3-6 Login ....................................................................................................... 3-4
Figure 3-7 NetNumen Unified Management System ................................................. 3-4
Figure 3-8 Calling Trace Interface Description .......................................................... 3-5
Figure 3-9 NE management...................................................................................... 3-7
Figure 3-10 Selecting NE Management .................................................................... 3-7
Figure 3-11 Add NE ................................................................................................. 3-8
Figure 3-12 Add NE .................................................................................................. 3-8
Figure 3-13 Deleting NE Menu.................................................................................. 3-9
Figure 3-14 Confirm ................................................................................................ 3-10
Figure 3-15 Modifying NE ....................................................................................... 3-10
Figure 3-16 Add NE Window................................................................................... 3-11
Figure 3-17 NE Connecting Link ............................................................................. 3-12
Figure 3-18 Disconnecting Link............................................................................... 3-13
Figure 3-19 Disconnecting NE Link ........................................................................ 3-13
Figure 3-20 Subscriber Trace Menu Bar ................................................................. 3-14
Figure 3-21 Subscriber Trace.................................................................................. 3-14
Figure 3-22 Creating Task Node ............................................................................. 3-15
Figure 3-23 Create Task ......................................................................................... 3-16
Figure 3-24 Selecting NE and Sub Task Type ......................................................... 3-17
Figure 3-25 Trace Task Management...................................................................... 3-18
Figure 3-26 Task List .............................................................................................. 3-18
Figure 3-27 Starting Tasks ...................................................................................... 3-19
Figure 3-28 Stopping Tasks .................................................................................... 3-21
Figure 3-29 Monitor ................................................................................................ 3-22
Figure 3-30 Signaling Trace Window ...................................................................... 3-23
Figure 3-31 Measurement Trace Window ............................................................... 3-24
Figure 3-32 View Data ............................................................................................ 3-25
Figure 3-33 View Data Dialog Box .......................................................................... 3-25
Figure 3-34 Tool-bar Introduction ............................................................................ 3-26
Figure 3-35 Save All ............................................................................................... 3-29
Figure 3-36 Setting Save Path ................................................................................ 3-29
Figure 3-37 Saving Selected Signaling ................................................................... 3-30
Figure 3-38 Setting Save Path ................................................................................ 3-31
II
Figures
Figure 3-39 Search ................................................................................................. 3-32

Figure 3-40 Setting Search Condition ..................................................................... 3-32
Figure 3-41 Filtering................................................................................................ 3-33
Figure 3-42 Setting Filter Conditions ....................................................................... 3-34
Figure 3-43 Starting Monitor ................................................................................... 3-35
Figure 3-44 Stopping Monitor.................................................................................. 3-36
Figure 3-45 Suspend Refreshing ............................................................................ 3-37
Figure 3-46 Full Screen Displaying ......................................................................... 3-38
Figure 3-47 Selecting Flow Source ......................................................................... 3-39
Figure 3-48 Flow Source Window ........................................................................... 3-39
Figure 3-49 Detailed Decoding................................................................................ 3-40
Figure 3-50 Detailed Decoding Window .................................................................. 3-41
Figure 3-51 Delete All ............................................................................................. 3-42
Figure 3-52 Suspend Scrolling ................................................................................ 3-43
Figure 3-53 Opening Data File ................................................................................ 3-44
Figure 3-54 Selecting Data File............................................................................... 3-45
Figure 3-55 Opening Signaling Trace File ............................................................... 3-45
Figure 3-56 Set Client Parameter............................................................................ 3-46
Figure 3-57 Local Setting ........................................................................................ 3-46
Figure 3-58 language select ................................................................................... 3-47
Figure 3-59 Window Switching Menu ...................................................................... 3-48
Figure 3-60 Pull-down Menu ................................................................................... 3-48
Figure 3-61 Opening Toolbar .................................................................................. 3-49
Figure 3-62 Closing Toolbar .................................................................................... 3-49
Figure 3-63 Opening Status Bar.............................................................................. 3-50
Figure 3-64 Closing Status Bar ............................................................................... 3-50
Figure 3-65 Closing Message Checking.................................................................. 3-51
Figure 3-66 Opening Message Checking ................................................................ 3-51
Figure 3-67 Closing Window Operation................................................................... 3-52
Figure 3-68 Close Menu ......................................................................................... 3-53
Figure 3-69 Lock Screen......................................................................................... 3-53
Figure 3-70 Select Lock Type ................................................................................. 3-54
Figure 3-71 Confirm Window .................................................................................. 3-54
Figure 3-72 Lock Screen Window ........................................................................... 3-54
Figure 3-73 Print Setup........................................................................................... 3-55
III
Figure 3-74 Print Setup Interface ............................................................................ 3-55

Figure 3-75 System Setting Menu........................................................................... 3-56
Figure 3-76 System Setting Window ....................................................................... 3-57
Figure 3-77 Login User Info Setting Menu............................................................... 3-58
Figure 3-78 Login User Info Setting Window ........................................................... 3-58
Figure 3-79 Holiday Configuration........................................................................... 3-59
Figure 3-80 Holiday Configuration Window ............................................................. 3-59
Figure 3-81
............................................................................................................ 3-60
Figure 3-82 User Password Setting......................................................................... 3-61

Figure 3-83 User Password Setting Window ........................................................... 3-61
Figure 3-84 Query System Time ............................................................................. 3-62
Figure 3-85 Query System Time Window ................................................................ 3-62
Figure 3-86 Logout Menu........................................................................................ 3-63
Figure 3-87 Exit System.......................................................................................... 3-63
Figure A-1 Process Operation Specific Information ...................................................A-2
Figure A-2 Service Window.......................................................................................A-2
Figure A-3 Server Console IP ..................................................................................A-3
IV
Tables
Table 1-1 Task Types ................................................................................................ 1-8
Table 2-1 Configuration File Table (1) of Port Offet.................................................. 2-16
Table 2-2 Configuration File Table (2) of Port Offet.................................................. 2-17
Table 3-1 Shortcut Introduction ................................................................................. 3-5
Table 3-2 Tool-bar Button Introduction..................................................................... 3-27
Tables
Glossary
3GPP
- 3rd Generation Partnership Project
ATM
- Asynchronous Transfer Mode
CN
- Core Network
CS
- Circuit Switched
EMS
- Electromagnetic Susceptibility
FTP
- File Transfer Protocol
GSM
- Global System for Mobile Communication
IP
- Internet Protocol
MBMS
- Multimedia Broadcast/Multicast Service
PS
- Packet Switched domain
RNC
- Radio Network Controller
RNL
- Radio Network Layer
TNL
- Transmission Network Layer
UE
- User Equipment
UMTS
- Universal Mobile Telecommunication System
UTRAN
- UMTS Terrestrial Radio Access Network
VII

SJ-20100603155704-018-ZXWR RNC (V3.09.30) Calling Trace Operation Guide - 345681

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

SJ-20100603155704-018-ZXWR RNC (V3.09.30) Calling Trace Operation Guide - 345681

Diunggah oleh

Hak Cipta:

Format Tersedia

ZXWR RNC

Radio Network Controller

Calling Trace Operation Guide

Additionally, the contents of this document are protected by

contractual confidentiality obligations.

First Edition (V3.09.30.03)

The following sections have been updated:

Deployment, Local NE Deployment, Tasks Synchronization,

Serial Number: SJ-20100603155704-018

Chapter 2 Software Installation................................................................. 2-1

Chapter 3 Basic Operations ...................................................................... 3-1

3.4.5 Link Operation ........................................................................................3-11

Appendix A Troubleshooting ................................................................... A-1

About This Manual

What Is In This Manual

Chapter 1 Basic Concepts

Introduces the basic function, installation mode,

Presents the installation procedures of the calling

Chapter 3 Basic Operations

Describes the basic operations of the calling

Chapter 4 General Problems and Solutions

Lists the solutions for two kinds of general

Presents the full English names of the glossaries.

Network optimization engineers

1.1 Software Functions

NetNumen M31(RAN) Mobile Network Element Management System Safety

ZTE Proprietary and Confidential

ZXWR RNC Calling Trace Operation Guide

1.2 Installation Modes

1.3 Software Modules

1.3.1 CT Client Module

ZTE Proprietary and Confidential

Chapter 1 Basic Concept

1.3.2 CT Server Module

1.3.3 CT Manager Module

1.3.4 CT Agent Module

1.3.5 RNL Or TNL Module

1.4 Deployment Modes

ZTE Proprietary and Confidential

ZXWR RNC Calling Trace Operation Guide

Independent server deployment

1.4.1 Independent Server Deployment

sun v4 SPARC Enterprise T5220 (virtual CPUs:

2 G (RCT software occupies 1200M, the

ZTE Proprietary and Confidential

Chapter 1 Basic Concept

1.4.2 Deployment of Sharing EMS Server

ZTE Proprietary and Confidential

ZXWR RNC Calling Trace Operation Guide

2 G (RCT software occupies 1200 M, the

1.4.3 Local NE Deployment

ZTE Proprietary and Confidential

Chapter 1 Basic Concept

Figure 1-5 The Calling Trace Software is Deployed at Local NE

1.5 Basic Concepts

1.5.1 Task Life Cycle

ZTE Proprietary and Confidential

ZXWR RNC Calling Trace Operation Guide

Figure 1-6 Calling Trace Task Life Cycle

1.5.2 Task Types

The trace task is to take UE as a tracing object.

ZTE Proprietary and Confidential

Chapter 1 Basic Concept