sjzl20092701 OperationGuide - SystemMaintenance

ZXSS10 SS1b
SoftSwitch Control Equipment

Operation Guide
System Maintenance
Version V2.0.1.06.1
ZTE CORPORATION
ZTE Plaza, Keji Road South,
Hi-Tech Industrial Park,
Nanshan District, Shenzhen,
P. R. China
518057
Tel: (86) 755 26771900
Fax: (86) 755 26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2006 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 CORPO-
RATION 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 dis-
claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-
fringement. 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 2009-9-20 First Edition
Serial Number: sjzl20092701

Contents
About This Manual.............................................. i

Alarm Management ...........................................1
Alarm Management......................................................... 1
Overview................................................................... 1
Querying Current Alarms ............................................. 1
Viewing Rack Diagram Alarms ...................................... 4
Forwarding Current Alarms Manually ............................. 7
Saving Current Alarm List ............................................ 9
Setting Current Alarm Query Condition ........................10
Setting History Alarm Query Condition..........................13
Setting Notification Query Condition .............................16
Setting Event Query Condition.....................................19
Setting Management Rules .........................................21
Setting Alarm Delaying Rule ...............................22
Setting Alarm Acknowledging Rule ......................24
Setting Alarm User Filtering Rule.........................27
Cancelling Alarm User Filtering Rule ....................30
Setting Maintenance Suggestions.................................31
Redefining Alarms Severity .........................................34
Setting Alarms Sounds ...............................................35
Setting Alarms Colors.................................................37
Monitoring Alarms in Real Time ...................................39
Monitoring Notifications in Real Time ............................43
Monitoring Events in Real Time....................................44
Synchronizing Alarms.................................................45
History Alarm Statistics ..............................................47
Setting Forward Template ...........................................49
Protocol Signal Tracing ................................... 53
Protocol Signal Tracing ...................................................53
Overview..................................................................53
Tracing H.248 Protocol ...............................................54
Tracing By Node................................................54
Tracing By Number............................................64
Tracing By Trunk ...............................................69
Tracing By H248 Subscriber ................................74
Tracing By Trunk Group......................................80
Tracing By Module .............................................85
Tracing Other Protocol Signals .....................................92
Registering Signal Trace Tasks ................................... 100
Viewing Signal Trace Results ..................................... 103
Viewing H.248/MGCP Tracing Results ................. 103
Viewing SCTP/M3UA/IUA/Q.931/V5UA Tracing
Results ............................................... 104
Viewing SS7UP TUP/ISUP /SCCP Tracing
Results ............................................... 106
Cancelling Signal Tracing Tasks.................................. 107
Saving Tracing Data As File ....................................... 108
Importing Signal Tracing Data ................................... 109
Network Diagnostic Test ............................... 113
Network Diagnostic Test ............................................... 113
Overview................................................................ 113
Detecting Board Attributes ........................................ 114
Detecting Network ................................................... 115
Ping External Node.......................................... 115
Ping Internal Module ....................................... 116
NIC Statistics ................................................. 118
Detecting Protocol ................................................... 119
Detecting Trunk .............................................. 119
Detecting SCTP............................................... 120
Detecting H248............................................... 121
Querying System Information.................................... 122
Querying Memory Usage On Board .................... 123
Querying Basic Information On Board ................ 123
Querying Net Flow On Board............................. 125
Querying Route Information On Board ............... 126
Querying Disk Information On SC...................... 127
Querying Port Flow On SSN .............................. 128
Querying Detail On SSN ................................... 129
Detecting Data ........................................................ 130
Detecting Data Area Queue .............................. 130
Detecting Table Space ..................................... 131
Detecting Procedure ........................................ 132
Detecting Table Capacity .................................. 133
Viewing Performance................................................ 134
Viewing CPU & Memory.................................... 134
Viewing Trunk Circuits ..................................... 136
Viewing Resource Report .......................................... 137
Viewing Board Test .................................................. 139
Viewing Routine Test ................................................ 140
System Maintenance ..................................... 143
Overview.................................................................... 143
Configuring KD Flag ..................................................... 143
Configuring KB Flag ..................................................... 145
Configuring ICP Flag .................................................... 147
Modifying Named Timer................................................ 149
Configuring SNMP OAM Console..................................... 151
Global Service Data Configuration .................................. 152
Entering Global Service Interface ............................... 153
(Configuration Example) Modifying Call Delay of Urgent
Special Service................................................ 154
Modifying Service Conflict ............................................. 155
Appendix ....................................................... 157
Common Named Timer Description ................................ 157
Global Variable Description ........................................... 164
Figures .......................................................... 171
Tables ........................................................... 175
About This Manual
Purpose This guide provides procedures and guidelines that support the
operation of the ZXSS10 SS1b SoftSwitch Control Equipment.
Intended This guide is intended for engineers and technicians who perform
Audience operation activities on the ZXSS10 SS1b SoftSwitch Control Equip-
ment.
Prerequisite Skill To use this guide effectively, users should have a general under-
and Knowledge standing of NGN technology. Familiarity with the following is help-
ful:
� ZXSS10 SS1b and its various components
� User interfaces on the SoftSwitch (SS)
� Local operating procedures
What Is in This This manual contains the following chapters:
Manual
TABLE 1 CHAPTER SUMMARY
Chapter Summary
Chapter 1,Alarm This chapter describes the procedure to

Management query alarms,notifications, and events
so that they can be fixed.
This chapter describes the procedure to
Chapter 2, Protocol trace different protocols signaling.Using
Signal Tracing this facility an engineer can be able to
point out any fault if exists .
This chapter describes the procedure to
Chapter 3, Network diagnose system boards,network,
Diagnostic Test protocols and resource usage.
Chapter 4, System This chapter describes the overall
Maintenance information of the HLR system.
Related The following documentation is related to this manual:

Documentation
� ZXSS10 SS1b SoftSwitch Control Equipment Operation Guide-
--Files & Data Management
--Traffic Control
--Traffic Statistics
Confidential and Proprietary Information of ZTE CORPORATION i

ZXSS10 SS1b Operation Guide---System Maintenance
This page is intentionally blank.
ii Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1
Alarm Management
Table of Contents
Alarm Management............................................................. 1
Alarm Management
Overview
Introduction This chapter introduces operation method for alarm management:
1. Alarm management provides an information terminal for view-
ing alarms and notifications; provides a querying tool to make
querying current and history information convenient; provides
customization for knowledge base and viewing function to
make users easy to handle alarms.
2. Alarm can be differentiated and selected according to time,
severity, type, alarm code and position.
3. Alarm notification is the reported information when some
events which needs operation people to know happen.
Querying Current Alarms

Prerequisites � NetNumen31 Unified Management System window is
opened.
� NetNumenN31 Unified Management System has been
connected with database.
Context Current alarms show real-time current existing alarms in SS, and
specific reasons for these alarms can be seen.
Steps 1. View current alarms.
� In NetNumen31 Unified Management System, select
View > Fault Management, Fault Management inter-
face opens as shown in Figure 1.
Confidential and Proprietary Information of ZTE CORPORATION 1

FIGURE 1 FAULT MANAGEMENT INTERFACE
� Select Query > View Current Alarms from menu bar or

double click the SS NE which needs to be viewed under
Topology Tree Root in left folder pane to open current
alarm query conditions window, as shown in Figure 2.
FIGURE 2 CURRENT ALARM QUERY
2. View specific detailed information of alarms.
2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Alarm Management
Double click an alarm record inFigure 2 window to view spe-

cific alarm detailed information and maintenance suggestion
as shown in Figure 3and Figure 4.
FIGURE 3 DETAILED INFORMATION

FIGURE 4 MAINTENANCE SUGGESTION
END OF STEPS
Result Querying current alarms is completed successfully.
Viewing Rack Diagram Alarms

opened.
Context Alarm rack diagram shows every board status in rack in time. And
according to different equipment type, interfaces of alarm rack dia-
gram are different. Through viewing alarm rack diagram, practical
rack configuration of this equipment and all alarms information in
this rack can be seen.
Steps 1. Right-click on SS NE and select Show Rack Map from the
popup menu, the dialog box appears as shown in Figure 5.

FIGURE 5 RACK DIAGRAM
2. Click the Legend button on the toolbar to open Legend

dialog box, as shown in Figure 6.

FIGURE 6 LEGEND
There is a little color button in every board and different color

button represents different status of each board; different color
represents different running status of each board.
3. Right-click one board and select Alarm from popup menu.
Take SC board for example as shown in Figure 7.

FIGURE 7 BOARD DETAILED INFORMATION
END OF STEPS
Result Viewing rack diagrams alarms is completed successfully.
Forwarding Current Alarms Manually

opened.
� Fault Management interface is opened.
Context Forward current alarms to appointed phone number or email ad-
dress.
Steps 1. Open current alarm list.
Right-click SS NE and select Show Current Alarms from
popup menu as shown in the Figure 8.

FIGURE 8 CURRENT ALARMS
2. Forward alarm manually.

Right-click one alarm record in and select Forward from popup
menu, Forwarding Setup dialog box pops up as shown in
Figure 9.
FIGURE 9 FORWARD

3. Fill in Email Address or Phone number or click the Select...

button to select desired email address or phone number to
forward, and then click the OK button to forward this alarm.
The alarm will be forwarded to the person you specified.
END OF STEPS
Result Forwarding current alarms manually is completed successfully.
Saving Current Alarm List

opened.
Context Save current alarm list in the form of file.
Steps 1. Open current alarm list.
Right-click SS NE and select Show Current Alarms from
popup menu as shown in Figure 10.
FIGURE 10 CURRENT ALARMS
2. Save current alarm list.
Click the button, and Save dialog box pops up as shown in

Figure 11.

FIGURE 11 SAVE
Select desired saving folder, input file name and click the Save
button to save current alarm list in selected file.
The saved file's form can be following formats:
� Microsoft Excel file.
� Adobe PDF file.
� HTML file.
� Text file.
END OF STEPS
Result Saving current alarm list is completed successfully.
Setting Current Alarm Query

Condition
opened.
Context This section describes the procedure to add different queries of
alarms with different specifications.
Steps 1. Select Query > View Current Alarms from menu bar.
Current Alarm Query Conditions window opens as shown in
Figure 12.

FIGURE 12 CURRENT ALARM QUERY CONDITIONS
2. Click the button in toolbar.

Current Alarm Query Conditions dialog box pops up as
shown in Figure 13.

FIGURE 13 QUERY CONDITION SETUP
Table 2 shows description of parameters in the dialog box.
TABLE 2 PARAMETERS IN QUERY CONDITION OF CURRENT

ALARM DIALOG BOX
Parameter Description
System Type Select ZXSS10 SS1, select server node and

alarm location, including equipment name,
shelf number, slot number. Shelf and slot
number are optional
Severity Confirm alarm severity. If severity is not

selected, then all levels of alarms are
queried. Severity is optional
Alarm Description Specify alarm description. It is optional
Probable Cause Specify probable cause for alarm. It is

optional
Happen Time Specify the time interval which alarms

happens. It is optional
Acknowledgment Specify alarm status. It is optional

Status

(Un)acknowledge Specify acknowledge operator. It is optional

Operator
(Un)acknowledging Specify acknowledge time. It is optional

Time
Details Specify detail information. It is optional
3. Fill in Name and Description and configure selections accord-

ing to actual condition. then click the OK button. Click the Ap-
ply button, a Confirm dialog box pops up as shown in Figure
14.
FIGURE 14 CONFIRM
If continue for another query, click the Yes button to continue,

otherwise, click the No button to cancel this operation.
END OF STEPS
Result Setting current alarm query condition is completed successfully.
Setting History Alarm Query

Condition
opened.
alarms with different specifications.
Steps 1. Select Query > View Historical Alarms from menu bar.
History Alarm Query Conditions window opens as shown in
Figure 15.

FIGURE 15 HISTORY ALARM QUERY CONDITIONS
2. Click the button in toolbar.

History Alarm Query Conditions dialog box pops up as
shown in Figure 16.

FIGURE 16 QUERY CONDITION SETUP
TABLE 3 PARAMETERS IN QUERY CONDITION OF HISTORY

ALARM DIALOG BOX

number are optional


optional

Acknowledgment Specify alarm status. It is optional

Status

(Un)acknowledge Specify acknowledge operator. It is optional

Operator
(Un)acknowledging Specify acknowledge time. It is optional

Time
3. Enter query name in Query Name field and description in De-

scription field. Set the specifications and Click the Apply but-
ton to add the query and add another query or Click the OK
command button to add and close the dialog box.
END OF STEPS
Result Setting history alarm query condition is completed successfully.
Setting Notification Query Condition

opened.
notifications with different specifications.
Steps 1. Select Query > View Notifications from menu bar.
Notification Query Conditions window opens as shown in
Figure 17.

FIGURE 17 NOTIFICATION QUERY CONDITIONS
2. Click the button on toolbar of Notification Query Condi-

tions window.
Query Condition of Notification dialog box pops up as
shown in Figure 18.

FIGURE 18 QUERY CONDITION OF NOTIFICATION
TABLE 4 PARAMETERS IN QUERY CONDITION OF NOTIFICATION

DIALOG BOX

number are optional


optional


3. Enter query name in Query Name field and description in

Description field. Set the specifications and Click the Ap-
plybutton to add the query and add another query or Click the
OK button to add and close the dialog box.
END OF STEPS
Result Setting notification query condition is completed successfully.
Setting Event Query Condition

opened.
notifications with different specifications.
Steps 1. Select Query > View Events from menu bar .
Event Query Conditions window opens as shown in Figure
19.
FIGURE 19 EVENT QUERY CONDITIONS
2. Click the button on toolbar of Event Query Conditions win-

dow.
Query Condition of Event dialog box pops up as shown in
Figure 20.

FIGURE 20 QUERY CONDITION OF EVENT DIALOG BOX
TABLE 5 PARAMETERS IN QUERY CONDITION OF EVENT DIALOG

BOX

number are optional


optional


3. Enter query name in Query Name field and description in De-

scription field. Set the specifications and Click the Apply but-
ton to add the query and add another query or Click the OK
button to add and close the dialog box.
END OF STEPS
Result Setting event query condition is completed successfully.
Setting Management Rules

Introduction The Fault Management module has many user-defined rules and
based on these rules, many alarm operations and executions are
carried out. The alarm rule management submodule then provides
users with functions of adding, deleting, modifying, refreshing, ac-
tivating and suspending these alarm rules.
1. Management rules include the following:
� All rules
� Alarm persisting rule
� Alarm counting rule
� Alarm delaying rule
� Alarm restraining rule
� Alarm merging rule
� Alarm user filtering rule
� Alarm global filtering rule
� Alarm discarding rule
� Alarm forwarding rule
� Alarm clearing rule
� Alarm acknowledging rule
� Notification global filtering rule
� Notification discarding rule
� Event discarding rule
2. Some alarms, either too minor or for some other reasons,
are unlikely to affect network performance. Alarm delaying
rules allow users to mask these alarms so that the number of
visible alarms in the NetNumenN31 Unified Management
System is reduced. These alarm won't be reported if they are
recovered within a certain time limit automatically; they are
reported only when they can't be recovered within the time
limit.
3. Alarm restraining rule allows users to restrain devices from
reporting a batch of alarms based on some specified alarms.
Those who restrain the other alarms are root alarms; the re-
strained ones are then consequential alarms. Consequential
alarms won't be reported no matter they are generated before
or after their root alarms so long as they appear.

4. Alarm counting rules allow users to sample the frequency of

some alarms reported by devices and judge if the number of
times the matching alarms occur within a specified time period
is greater than a preset threshold. If yes, a new alarm will
then be generated to inform the operating personnel. Details
and severity levels for these new alarms can be specified.
5. Sometimes for a device failure, there may be multiple alarms.
Alarm merging rules allow users to display only one of them
on the screen by specifying alarm selection conditions.
Setting Alarm Delaying Rule

opened.
Context This section explains the procedure to set alarm delaying rule.
Some alarms, either too minor or for some other reasons, are un-
likely to affect network performance. Alarm delaying rules allow
users to mask these alarms so that the number of visible alarms
in the NetNumen31 Unified Management System is reduced.
These alarm won't be reported if they are recovered within a cer-
tain time limit automatically; they are reported only when they
can't be recovered within the time limit.
Steps 1. Select Setting > Management Rule Setting from menu bar.
Management Rule Setting window opens as shown in Figure
21.
FIGURE 21 MANAGEMENT RULE SETTING

2. Click button on toolbar of Management Rule Setting

window.
A New dialog box appears, as shown in Figure 22.
FIGURE 22 NEW
3. Select Alarm Delaying Rule from list and Click the OK button.
Alarm Delaying Rule dialog box pops up as shown in Figure
23.

FIGURE 23 ALARM DELAYING RULE
4. Fill in Name, Description, select ZXSS10 SS1 as System

Type, and then set Location, Severity, Probable Cause,
Happen Time and other items. The delay time determines
how long the alarms will be delayed before they are reported.
Click the OK button to finish setting alarm delaying rule. Click
the Apply button to continue for another rule setting. Detailed
parameters information please refers to Table 2.
END OF STEPS
Result Setting alarm delaying rule is completed successfully.
Setting Alarm Acknowledging Rule

opened.
Context This section explains the procedure to set alarm acknowledging
rule.
Auto acknowledging rules helps change automatically alarm status
into "Acknowledged" so as to cut the number of unacknowledged

alarms and make it easier to discover new problems when an alarm

or alarm restoration is reported to the system in the case if oper-
ators have known clearly the alarm generation or restoration.
24.

window.

FIGURE 25 NEW
3. Select Alarm Acknowledging Rule from list and Click the OK

button.
Alarm Acknowledging Rule dialog box pops up as shown in
Figure 26.

FIGURE 26 ALARM ACKNOWLEDGING RULE

Happen Time and other items. The acknowledging action pa-
rameter decides when alarms will be changed into "Acknowl-
edged", either when they are reported or restored. Click the
OK button to finish setting alarm delaying rule. Click the Apply
button to continue for another rule setting. Detailed parame-
ters information please refers to Table 2.
END OF STEPS
Result Setting alarm acknowledging rule is completed successfully.
Setting Alarm User Filtering Rule

opened.
Context This section explains the procedure to set alarm user filtering rule.

The NetNumenN31 Unified Management System provides 3

types of alarm filtering rules, arranged below in the sequence of
system's preprocessing: alarm discarding rules, alarm global fil-
tering rules, alarm user filtering rules. In addition, event and no-
tification discarding rules are included.
� Alarm user filtering rule
alarm user filtering rule and have set its filtering conditions,
the NetNumenN31 Unified Management System, when re-
ceiving alarms that meet the conditions, will not have them
displayed on the current user's client. This rule is valid glob-
ally, that is, it takes effect for all active alarms in the system.
� Global alarm filtering rules
Global alarm filtering rules are an alarm visibility control rule,
making some alarms invisible to all users in order to reduce the
quantity of alarms which concern the users. These alarms then
are saved to the system for later statistical and other purposes.
� Alarm discarding rules
Alarm discarding rules help have the alarm information re-
ported by devices filtered so as to screen those which need
not be handled by the NetNumenN31 Unified Management
System.
The above filtering setting methods are similar, as a result, take
alarm user filtering rule for example.
27.

window.

FIGURE 28 NEW
3. Select Alarm User Filtering Rule from list and Click the OK
button.
Alarm User Filtering Rule dialog box pops up as shown in
Figure 29.

FIGURE 29 ALARM USER FILTERING RULE

Happen Time and other items. If a user alarm filtering rule
has been created and its filtering conditions have been set,
when receiving alarms that meet the conditions, will not have
them displayed on the current user's client, but only displayed
on the preset user. Click the OK button to finish setting alarm
delaying rule. Click the Apply button to continue for another
rule setting. Detailed parameters information please refers to
Table 2.
END OF STEPS
Result Setting alarm user filtering rule is completed successfully.
Cancelling Alarm User Filtering Rule

opened.

Context Cancelling alarm user filtering rule makes the filtering rules display
again in NetNumen31 Unified Management System.
Steps 1. In Management Rule Setting window, select Alarm User
Filtering Rule in Rule Type dropdown list.
The created alarm user filtering rule appears as shown in Figure
30.
FIGURE 30 ALARM USER FILTERING RULE
2. Select the rule which needs to be cancel filtering and click the
button.
Confirm dialog box pops up as shown in Figure 31.
FIGURE 31 DELETE FILTERING RULE
3. Click the OK button to delete this alarm user filtering rule, while
click the Cancel button to save this alarm user filtering rule.
END OF STEPS
Result Cancelling alarm user filtering rule is completed successfully.
Setting Maintenance Suggestions

opened.

Context The NetNumen31 Unified Management System allows users to

summarize experiences on solving frequently-occurred problems.
The experiences, referred to as alarm maintenance suggestions,
then are taken as a reference to problems alike generated later on.
In the NetNumen31 Unified Management System, users are
allowed to import, export, view and modify the alarm maintenance
suggestions so that system alarms can be handled very quickly and
conveniently.
Steps 1. Select Setting > Maintenance Suggestion Setting from
menu bar. And then select ZXSS10 SS1 from System Type
dropdown list.
Maintenance Suggestion Setting window opens as shown
in Figure 32.
FIGURE 32 MAINTENANCE SUGGESTION SETTING
2. Right—click one alarm record in Figure 32 and select Modify

from popup menu.
Maintenance Suggestion dialog box pops up as shown in
Figure 33.

FIGURE 33 MAINTENANCE SUGGESTION I
3. Enter Customized Suggestions according to actual condi-

tion. And then click the OK button to finish modifying mainte-
nance suggestion.
4. Click button in Maintenance Suggestion Setting win-

dow.
Maintenance Suggestion dialog box pops up as shown in
Figure 34.

FIGURE 34 MAINTENANCE SUGGESTION II
5. Click the Select... button to change Alarm Code or Probable

Cause and enter Customized Suggestions according to ac-
tual condition. And then click the OK button to finish creating
maintenance suggestion.
6. Click button to delete maintenance suggestion already set.

END OF STEPS
Result Setting maintenance suggestion is completed successfully.
Redefining Alarms Severity

opened.
Context In the NetNumen31 Unified Management System, each alarm
code corresponds to an alarm level. The alarm level in response
to an alarm code has been determined at the time of system initi-
ation. But during system operation, users are able to also change
the alarm level of an alarm code so as to modify the severity of
the alarms. The Severity Regrading Setting function is thus
provided to implement this purpose.

Steps 1. In Fault Management window, select Setting > Severity

Regrade Setting. And then select ZXSS10 SS1 from System
Type dropdown list.
Severity Regrade Setting window opens as shown in Figure
35.
FIGURE 35 SEVERITY REGRADE SETTING
2. Select the alarm code which needs to be modified and click

New Severity dropdown list. There are five severities: Criti-
cal, Major, Minor, Warning, Original.
Tip:
After redefinition, only after restart or log in again, severity
redefinition takes effect.
END OF STEPS
Result Redefining alarms severity is completed successfully.
Setting Alarms Sounds

opened.


Context Alarm Sound Setup allows users to customize the sounds given
by the system to remind them of the occurrence of system mal-
functions when alarms are generated.
Steps 1. Select Setting > Preferences from menu bar.
Preferences dialog box opens as shown in Figure 36.
FIGURE 36 PREFERENCES
The default tab is Alarm Sound Setup tab, as shown inFigure

36.
Table 6 shows description of parameters in Alarm Sound
Setup tab of the dialog box. Only parameters used in critical
alarm are described. Other parameters are similar.

TABLE 6 PARAMETERS IN SOUND AND COLOR SETTING

DIALOG BOX
Parameter Description/Operation
Sound Mode Select any of None, Continuous sound, or Short

beeps according to the requirement
Sound File It shows file name selected. If no file is selected

by user, Default sound file is there
Play Click this button to play default or other selected

file
Stop Click this button to stop playing a file
Select… Selecting any other option except None in

drop-down list enables this button. Click this
button to select a sound file from local directory
Default Click this button to select default sound file
OK Click this button for changes to take effect
Cancel Click this button to close the dialog box without

any change
2. In Alarm Sound Setup tab, select the sounds for each alarm
level and Click the OK button for changes to take effect.
END OF STEPS
Result Setting alarms sounds is completed successfully.
Setting Alarms Colors

opened.
Context Alarm color setup allows users to customize the colors of alarms
of different levels so that on basis of its color, the users can tell
what the alarm's level is easily.

2. Click on the Alarm Color Setup tab.

Alarm Color Setup interface opens as shown in Figure 38.

FIGURE 38 ALARM COLOR SETUP
3. Click each drop-down list and select suitable color for each
severity level. Click the OK button for changes to take effect.
END OF STEPS
Result Setting alarms colors is completed successfully.
Monitoring Alarms in Real Time

opened.

Context In the NetNumen31 Unified Management System, users are

able to check the current alarms of the system so that the op-
erating conditions of the network can be learnt timely, making it
possible to solve the system problems as early as possible once
they occur.
Steps 1. ClickQuery > Realtime Alarm Monitor from menu bar.
Realtime Alarm Monitor window opens as shown in Figure
39.
FIGURE 39 REALTIME ALARM MONITOR
Table 7 shows description of buttons on both toolbars in Real-

time Alarm Monitor window.
TABLE 7 TOOLBAR BUTTONS DESCRIPTION IN REALTIME

ALARMS WINDOW
Button
Button Description/Operation
Name
Count Click this button to get total number of

alarms/notifications/events and also for
different severity level
Customize Click this button to add or remove columns

Display in alarm/notification/event display pane
Columns
Export Click this button to export the

alarms/notifications/events description to
an Excel file
Print Click this button to print the view

Button
Button Description/Operation
Name
Alarm Click this button to set sounds for alarms

Sound of different severity level
Setup
Full Screen Click this button to view alarms in full

screen
Remove All Click this button to remove all data in

Data Realtime History Alarms section
2. User may perform any of the following steps.

� Counting alarms: Click the Count button on toolbar to
open Count dialog box, as shown in Figure 40.
FIGURE 40 COUNT DIALOG BOX
� Customizing Display columns: Click the Customize Dis-

play Columns button on toolbar to open Customize dis-
play columns dialog box, as shown in Figure 41. Check
a column check box to include the column or uncheck to
exclude depending upon the requirement.

FIGURE 41 CUSTOMIZE DISPLAY COLUMNS DIALOG BOX
� Exporting alarms description: Click the Export button on

toolbar to save alarms description in an Excel file.
� Printing the view: Click the Print button on toolbar to print
the view.
� Setting sounds for different severity level alarms: Click
the Alarm Sound Setup button on toolbar to open Alarm
Sound Setup dialog box, as shown in Figure 42. Select
None, Continuous sound, or Short beeps from each
drop-down list according to the requirement and Click the
OK button for changes to take effect.

FIGURE 42 ALARM SOUND SETUP
� To acknowledge/un-acknowledge alarm: Right-click an

alarm row item. A popup menu appears. Select Acknowl-
edge or Unacknowledge menu item according to the
current status of the alarm to open a dialog box. Enter
some description in it (if necessary) and Click the OK
button to acknowledge/un-acknowledge the alarm.
� Clearing alarm: Right-click an alarm row item. A popup
menu appears. Select Clear menu item to remove the
alarm. A prompt dialog box confirms deletion.
� Forwarding alarm description: Right-click an alarm row
item. A popup menu appears. Select Forward menu item
to forward the details of an alarm to specified email ad-
dress.
� Viewing details: Right-click an alarm row item. A popup
menu appears. Select Details menu item to open Details
dialog box. User can also open this dialog box by double-
clicking the alarm.
END OF STEPS
Result Monitoring alarms in real time is completed successfully.
Monitoring Notifications in Real Time

opened.

Context The NetNumen31 Unified Management System allows users to

monitor the system's notifications so that the network's operating
conditions can be learnt timely.
Steps 1. Select Query > Realtime Notification Monitor from menu
bar.
Realtime Notification Monitor window opens as shown in
Figure 43.
FIGURE 43 REALTIME NOTIFICATIONS WINDOW
Table 7shows description of buttons on the toolbar in Realtime

Notification Monitor window.
2. User may perform different operations in the window. Specific
steps please refers to Step 2 of Monitoring Alarms in Real Time
section for the operations.
END OF STEPS
Result Monitoring notifications in real time is completed successfully.
Monitoring Events in Real Time

opened.
Context The NetNumen31 Unified Management System allows users
to monitor the system's events so that the network's operating
conditions can be learnt timely.

Steps 1. Select Query > Realtime Event Monitor from menu bar.
Realtime Event Monitor window opens as shown in Figure
44.
FIGURE 44 REALTIME EVENT MONITOR WINDOW
Table 7shows description of buttons on the toolbar in Realtime

Event Monitor window.
2. User may perform different operations in the window. Specific
steps please refers to Step 2 of Monitoring Alarms in Real Time
section for the operations.
END OF STEPS
Result Monitoring events in real time is completed successfully.
Synchronizing Alarms
opened.
Context Alarm Synchronization allows users to synchronize the alarms of
NEs. Users can specify the position information of NEs to be syn-
chronized. When users find that the NetNumen31 Unified Man-
agement System's alarm data is not consistent with those on the
network devices, use this function to have them synchronized.
Steps 1. Select Query > Alarm Synchronization from menu bar.

Alarm Synchronization dialog box pops up as shown in

Figure 45.
FIGURE 45 ALARM SYNCHRONIZATION
2. Select system type as ZXSS10 SS1b and specify the Loca-

tion: OBJKEY, RACK, SHELF, BOARD as shown in Figure
46.

FIGURE 46 SPECIFYING LOCATION IN ALARM SYNCHRONIZA-

TION DIALOG BOX
3. Click the OK button to synchronize alarms.

END OF STEPS
Result Synchronizing alarms is completed successfully.
History Alarm Statistics

opened.
Context This section describes history alarm statistics of ZXSS10 SS1b.

Steps 1. Select Query > History Alarm Statistics from menu bar.
Report Management window opens as shown in Figure 47.
FIGURE 47 REPORT MANAGEMENT
2. Click the desired viewing item in the Report Template Tree

of left folder pane.
Figure 48 shows Historical Alarm Statistics displaying in the
List of Report Templates dialog box.

FIGURE 48 SPECIFYING HISTORICAL ALARM STATISTICS

DIALOG BOX
END OF STEPS
Result History alarm statistics is completed successfully.
Setting Forward Template

opened.
Context This section describes the procedure to setup forward template
for showing alarms attribute as the format for short message and
email of manual forwarding and automatic forwarding.

2. Click on the Forward Template Setup tab.

Forward Template Setup interface opens as shown in Figure
50.

FIGURE 50 FORWARD TEMPLATE SETUP
3. On the Forward Template Setup tab page, customize desired

contents of short messages and emails. After input forwarding
template of alarm attribute, Click the Examine button for ex-
amining the setting to see if it is successful or not. Or Click the
Default button for inputting the default forwarding template.
4. Click the OK button for changes to take effect.
END OF STEPS
Result Setting forward template is completed successfully.


Chapter 2
Protocol Signal Tracing
Table of Contents
Protocol Signal Tracing .......................................................53
Protocol Signal Tracing

Overview
Introduction During the course of deployment, debugging and running of
SoftSwitch equipment, there is interworking with other equipment
such as media gateway, signaling gateway and so on. In order
to observe interworking flow of running equipment and protocols
or signalling between different equipment, tracing signaling de-
mands are proposed. Signaling trace module can display protocol
interworking process among running equipment conveniently in
real time.
Function of The main function of signaling trace interface is shown as follows:
Signalling Trace
Graphics Interface 1. Providing introduction for operators to accomplish register of
trace tasks;
2. Supporting many signaling tracings such as MGCP, H.248, SIP,
SS7UPTUP/ISUP, M3UA, SCTP, IUA, Q.931, V5UA, V5, RADIUS,
H.323 and so on;
3. Supporting ISUP national standard, ITU-T and ANSI standard,
particular decode of TUP national standard;
4. Binary protocol or providing particular decode of signalling;
5. Providing graphics management tool for foreground trace
queue.
Entering 1. In NetNumen N31 Unified Management System, select
Signalling Trace View > Topology Management. In Topology Manage-
initial interface ment interface, following two ways are available to enter
Toolkit interface:
� Right-click SS NE in Topology Tree Root and select Pro-
tocol Trace from popup menu to enter Toolkit interface.
� Select View > Toolkit from menu bar to enter Toolkit
interface.
2. In Toolkit interface, select the NE which needs to be managed.
And right-click this SS NE, select connect by server proxy
(slow) or direct connect (fast).

Common steps Common steps for signalling tracing are:

1. Setting tracing condition. Protocol tracing graphics interface
provides introduction to help user finish tracing tasks setting.
2. Registering tracing tasks.
3. Viewing tracing result.
4. Cancelling tracing.
Tracing H.248 Protocol

Introduction H.248 protocol traces has six ways: by node, by number, by trunk,
by H248 subscriber, by trunk group and by module.
This section take node tracing as a example and introduce other
five tracing methods briefly.
Tracing By Node
Prerequisites � NetNumen Server is installed, configured and connected with
database.
� NetNumenN31 Unified Management System window is
opened.
Context There are six common tracing methods to trace H.248 protocol:
� By node;
� By number;
� By trunk;
� By H.248 subscriber;
� By trunk group;
� By module.
This section introduce procedure to trace H.248 by node.
Steps 1. Select Operation > Protocol Tracing from menu bar or right
click on the SS1b NE and select Protocol Tracing item from
the popup menu.
Signaling Trace – SSID=SS window appears as shown in
Figure 51.

Chapter 2 Protocol Signal Tracing
FIGURE 51 SIGNALING TRACE INTERFACE
2. Select Trace > Start tracing from menu or click button

in tool bar.
Config condition dialog box appears on the screen, as shown
in Figure 52.

FIGURE 52 CONFIG CONDITION DIALOG BOX
3. Click on H.248 tab and click the CONFIG button in the dialog
box.
Trace Condition dialog box appears, as shown in Figure 53.
FIGURE 53 TRACE CONDITION DIALOG BOX

4. Click the Node button.

An information messages appears, as shown in Figure 54.
FIGURE 54 SPECIFYING CONDITIONS FOR TRACING
There are lots of data returning if tracing by node. For node

with large-capacity, a lot of tracing data communication occupy
much of system resource, as a result, affects system perfor-
mance. So for this tracing method, system prompts above
information to require users to confirm to do this operation.
5. Click the Yes button to continue the process.
Trace Condition dialog box appears as shown in Figure 55.
FIGURE 55 TRACE CONDITION OPTION
i. Click the By Node button. Trace Condition dialog box

pops up as shown in Figure 56. Fill in NODE ID and select
Trace Transfer Message Flag.

FIGURE 56 TRACE BY NODE
ii. Click the By Domain Name button. Trace Condition di-

alog box pops up as shown in Figure 57. Fill in Domain
Name and select Trace Transfer Message Flag.

FIGURE 57 TRACE BY DOMAIN NAME
iii. Click the By IPv4 Address button. Trace Condition di-

alog box pops up as shown in Figure 58. Fill in IPv4 Ad-
dress and select Trace Transfer Message Flag.

FIGURE 58 TRACE BY IPV4 ADDRESS
6. Select one of above three tracing way and click the NEXT but-
ton. Trace Condition dialog box pops up as shown in Figure
59. User select if only to trace specific error H.248 message.

FIGURE 59 FILTER BY ERROR TYPE
As usual, trace all H.248 messages. If user want to narrow

tracing range, while, in this step, select tracing error type.
Select Filter by error type and error type list is available and
then select designated errors. Pay attention, select the last
line All error types whose error number is 65535 to trace all
messages.
If do not need to designate error type, click the NEXT button
to skip this step.
7. Click the NEXT button.
A dialog box appears as shown in Figure 60.

FIGURE 60 CONDITIONS SET BY USER
Table 8 shows description of parameters.

ALARM DIALOG BOX
TRACE TIME Enter a suitable time for protocol tracing.

The default value is 1440
MAX LINE Enter suitable maximum displaying lines

for protocol tracing results. The scope of
MAX LINE is from 10 to 4000
Input start time of Select this item to input the starting time
schedule task of this task and choose if displaying tracing
records

SAVE TO FILE Select this item to save the tracing records

and configuring the saving path
8. Click the NEXT button to proceed.

A collection of the configuring trace condition is displayed in
Figure 61.
FIGURE 61 TRACE CONDITION COLLECTION
If user do not satisfy with previous setting, click the PREV

button to set again.
9. Click the NEXT button to back toFigure 52 dialog box, click the
OK button to register tracing task in foreground.
END OF STEPS

Result Tracing by node is completed successfully.
Tracing By Number
database.
opened.
� Signal Trace interface is opened.
� By node;
� By number;
� By trunk;
� By trunk group;
� By module.
This section introduce procedure to trace H.248 by number.
Steps
in tool bar.
in Figure 62.

box.

3. Click the By Number button.

Trace Condition dialog box pops up as shown in Figure 64.
Fill in SDN (Right Match) and select The Flag of DR and
Trace Transfer Message Flag.
FIGURE 64 TRACE BY NUMBER
DR means disaster recovery and right match means phone

number only needs right consistency, and then this phone
number could be traced.


ALARM DIALOG BOX


records



Figure 66.

END OF STEPS

Result Tracing by number is completed successfully.
Tracing By Trunk
database.
opened.
� By node;
� By number;
� By trunk;
� By trunk group;
� By module.
This section introduce procedure to trace H.248 by trunk.
Steps
in tool bar.
in Figure 67.

box.

3. Click the By Trunk No button.

Trace Condition dialog box pops up as shown in Figure 69. Fill
in GROUP NUMBER and INNER NUMBER, select The Flag
of DR and Trace Transfer Message Flag.
FIGURE 69 TRACE BY TRUNK
INNER NUMBER needs to input certain circuit number. Sys-

tem supports tracing four trunk circuits at one time at most,
and click the ADD button to add new circuit.


ALARM DIALOG BOX


records



Figure 71.

END OF STEPS

Result Tracing by trunk is completed successfully.
Tracing By H248 Subscriber

database.
opened.
� By node;
� By number;
� By trunk;
� By trunk group;
� By module.
This section introduce procedure to trace H.248 by H.248 sub-
scriber.
Steps
in tool bar.
in Figure 72.

box.

3. Click the By H248 Subscriber button.

Information dialog box pops up as shown in Figure 74.
FIGURE 74 INFORMATION
Trace by H.248 subscriber could only trace subscriber of IAD

and AG.
4. Click the OK button.
Trace Condition dialog box pops up as shown in Figure 75. Fill
in NET NUMBER , DOMAIN NUMBER and USER NUMBER,
select The Flag of DR and Trace Transfer Message Flag.

FIGURE 75 TRACE BY H248 SUBSCRIBER
NET NUMBER is the net type to which H.248 subscriber be-

longs. System supports four subscriber number at one time at
most, click the ADD button to add new subscriber number.


ALARM DIALOG BOX


records



Figure 77.

7. Click the NEXT button to back to Figure 72 dialog box, click
the OK button to register tracing task in foreground.
END OF STEPS

Result Tracing by H.248 subscriber is completed successfully.
Tracing By Trunk Group

database.
opened.
� By node;
� By number;
� By trunk;
� By trunk group;
� By module.
This section introduce procedure to trace H.248 by trunk group.
Steps
in tool bar.
in Figure 78.

box.

3. Click the By Trunk Group No button.

Fill in GROUP NUMBER and select The Flag of DR and Trace
Transfer Message Flag.
FIGURE 80 TRACE BY TRUNK GROUP NO



ALARM DIALOG BOX


records



Figure 82.

END OF STEPS

Result Tracing by trunk group is completed successfully.
Tracing By Module
database.
opened.
� By node;
� By number;
� By trunk;
� By trunk group;
� By module.
This section introduce procedure to trace H.248 by module.
Steps
in tool bar.
in Figure 83.

box.

3. Click the By Module button.

Information dialog box pops up as shown in Figure 85.
FIGURE 85 INFORMATION
Trace by module returns a lot of data.

4. Click the OK button.
FIGURE 86 TRACE CONDITION
5. Click the By Module button.

Fill in MODULE NUMBER and select Trace Transfer Message
Flag.

FIGURE 87 TRACE BY MODULE

Filter by error type dialog box pops up as shown in Figure
88.

FIGURE 88 FILTER ERROR TYPE
As usual, trace all H.248 messages. If user want to narrow

tracing range, while, in this step, select tracing error type.
Select Filter by error type and error type list is available and
then select designated errors. Pay attention, select the last
line All error types whose error number is 65535 to trace all
messages.
If do not need to designate error type, click the NEXT button
to skip this step.


ALARM DIALOG BOX


records



Figure 90.

END OF STEPS

Result Tracing by module is completed successfully.
Tracing Other Protocol Signals

database.
opened.
Context This section introduces to do other tracings.
Steps
in tool bar.
in Figure 91.

2. Setting other tracing includes following two aspects:

� by protocols:
mainly includes: H.248 V5L3 V5UA SIP-TP BICC SS7UP TCA-
PSCTPSIPSIP-ISIP-TUMGCPQ.931SCCPM3UAMAPMAP+C-
APINAPH.323H.323 protocols. Particular tracing condition
please refers to Table 14.
TABLE 14 PROTOCOL TRACE CONDITION SETTING
Trace Trace Parameters

Main Parameters
Type method Description
SIP By mod- MODULE NO MODULE NO SPC’s

ule module number of
the NE which needs
to be traced


Main Parameters
By URL URL,The Flag of URLURL of SIP user

DR
The Flag of
DR:Trace DR board
or not
By SIP The Flag of DR The Flag of

error DR:Trace DR board
or not
By node NODE ID NODE IDnode id of

corresponding NE
MGCP By node By node: NODE ID NODE IDnode id of

corresponding NE
By domain DO- DOMAINnode’s do-

MAIN main
By IPv4 IP:IPv4 IP IPv4 Ad-

dress node’s IPv4
IP
By num- NET NUMBER, NET NUMBER: net

ber DOMAIN NUM- type to which user
BER, USER NUM- belongs
BER
USER NUM-
BER system sup-
ports tracing four
user numbers at or
time at most, click
the ADD button to
add new user num-
ber
By trunk GROUP NUMBER, system supports

INNER NUMBER tracing four trunk
circuits at or time
at most, click the
ADD button to add
new trunk circuit
H.323 By node NODE ID, Choice NODE IDnode id of

Register Call corresponding NE
Choice Register
Call: select desired
message which
needs to be trace:
register message or
call message
By num- NET NUMBER, Choice Register

ber DOMAIN NUM- Call: select desired
BER, By user message which
number, Choice needs to be trace:
Register Call, The register message or
Flag of DR call message


Main Parameters
SCTP By node NODE ID NODE IDnode id of

corresponding NE
By link LINK NO LINK NO: SCTP

number configured link
number
M3UA By link LINK NO, Trace

number Component
SS7UP By circuit OFFICE ID, CICLE CICLE NUMBER:

number NUMBER, NUM- initial number of
BER OF CIC, The circuit
Flag of DR, Trace
Component NUMBER OF CIC:
circuit numbers
which needs to be
traced from initial
circuit
By SDN USER NUMBER, USER NUMBER:

CALLING FLAG, there is no need
The Flag of DR to input all num-
bers, if number
is not complete,
then system match
the missing num-
bers automatically,
for example, in-
putting ”458”, then
system considers
such as “4580***”,
“4581***” and so
on, all numbers are
correct
By trunk GROUP NUMBER,

group The Flag of DR
SCCP By office OFFICE ID, The OFFICE ID: ID of

number Flag of DR signal office
Q.931 By mod- MODULE NO, MODULE NO SPC’s

ule Trace Component module number of
the NE which needs
to be traced
By node NODE ID, FILTER FILTER BY DCHNL

BY DCHNL NO NO: needs to spec-
ify whether D chan-
nel number and B
channel number are
needed to be fil-
tering condition of
messages. If user
needs D channel
number to be fur-
ther filtering condi-
tion, click FILTER
BY DCHNL NO,
then D channel in-
putting is available


Main Parameters
to let user enter D
channel number
By num- NUMBER CHUAN NUMBER CHUAN

ber right match right match :
chuan user number right
match, if right side
of phone number
are consistent, this
number could be
traced
IUA By link LINK NO

number
V5UA By link LINK NO, EFA, EFA: encapsulation

number IID address, represents
which protocol is in
the upper layer of
encapsulation
IID: interface iden-

tifier, it is the value
which calculated by
V5 link number and
slot of physical C
channel
V5L3 V5_L3 V5 ID, EF Ad- EF Address: en-

dress, L3 Address capsulation ad-
dress, represents
which protocol is in
the upper layer of
encapsulation, such
as BCC, control pro-
tocol and so on
L3 Address: each
V5 user corre-
sponds to one L3
address. In V5
configuration, the
user number cor-
responding to L3
address could be
checked
By NET NUMBER,
V5_PSTN DOMAIN NUM-
BER, USER NUM-
BER
By fail V5 ID, Cause Cause value of

reason value of call loss, call loss: reason
L3 Address value number cor-
responding to fail-
ure type such as
subscriber release
early, ringing re-
lease early, caller
busy and so on


Main Parameters
SIP-TP By mod- MODULE NO MODULE NO SPC’s

the NE which needs
to be traced
By URL URL URLURL of SIP user
By IP IPv4 IP, Request Request Method:

Method trace designated
message of proto-
col
BICC By circuit OFFICE ID, CICLE CICLE NUMBER:

number NUMBER initial number of
circuit
NUMBER OF CIC:
circuit numbers
which needs to be
traced from initial
circuit
By SDN USER NUMBER,

CALLING FLAG
TCAP By mod- MODULE NO, ALL MODULE NO SPC’s

ule MODULE module number of
the NE which needs
to be traced
SIP-I By mod- MODULE NO MODULE NO SPC’s

the NE which needs
to be traced
By URL URL, trace mode, URLURL of SIP user

The Flag of DR
By node NODE ID NODE IDnode id of

corresponding NE
SIP-TU By card CARD CARDcard number

number
By URL URL, trace mode, URLURL of SIP user

The Flag of DR
MAP By mod- MODULE NO MODULE NO SPC’s

the NE which needs
to be traced
By match trace mode, The PSID number:

SDN Flag of DR, PSID after HLR com-
Number (Fuzzy pletes number
Match) distribution, this
number could be
queried in Local
Office User Con-
figuration inter-
face


Main Parameters
MAP+ By mod- MODULE NO MODULE NO SPC’s

the NE which needs
to be traced
By match trace mode, The Left match, only

SDN Flag of DR, Call- needs left side of
ing number (left phone numbers
match mode) are consistent, this
number could be
traced
CAP By node NODE ID NODE IDnode id of

corresponding NE
By mod- MODULE NO MODULE NO SPC’s

the NE which needs
to be traced
By num- NET NUMBER,

ber DOMAIN NUM-
BER, USER NUM-
BER
INAP By mod- MODULE NO, MODULE NO SPC’s

ule SUPPORT CS2 module number of
the NE which needs
to be traced
SUPPORT CS2 :
CS2 is Intelligent
Network Applica-
tion Procedure 2,
do not click SUP-
PORT CS2, then
support CS1
By node NODE ID, SUP- NODE IDnode id of

PORT CS2 corresponding NE
By match trace mode, The

SDN Flag of DR, Called
Number (Fuzzy
Match), SUPPORT
CS2
� by business:
includes: Call Trace, Call Lost View, Call view. Particular
tracing condition please refers to Table 15.

TABLE 15 BUSINESS TRACE CONDITION SETTING
Trace Trace Main parameters Parameters

type met- description
hod
Call By SDN Call protocol, Call protocol: se-

trace USER NUMBER, lect all protocol
Protocol, The Flag
of DR
Call By base By node:NODE ID, NODE ID node id of

lost call The Flag of Bulk corresponding NE
view Call, The Flag Of
Casting Modules
By module:MOD- MODULE NO SPC’s

ULE NO, The Flag module number of
of Bulk Call the NE which needs
to be traced
By number
chuan:SDN, The
Flag of Bulk Call,
The Flag of DR
By By business user:
multi- NET NUMBER, DO-
part call MAIN NUMBER,
USER NUMBER
By module: MOD- MODULE NO SPC’s

ULE NO module number of
the NE which needs
to be traced
By By node: NODE ID
smart
call By module: MOD- MODULE NO SPC’s
the NE which needs
to be traced
By user number:
NET NUMBER, DO-
MAIN NUMBER,
USER NUMBER
Call By base By SDN: NET NUM-

view call BER, DOMAIN
NUMBER, USER
NUMBER, Whole-
Flow
By trunk: Trunk
Group ID, Whole-
Flow, The Flag of
Bulk Call, The Flag
Of Casting Mod-
ules

Trace Trace Main parameters Parameters

type met- description
hod
By module: MOD- MODULE ID SPC’s

ULE ID, The Flag module number of
of Bulk Call the NE which needs
to be traced
By node: NODE ID,

WholeFlow, The
Flag of Bulk Call,
The Flag Of Cast-
ing Modules
By match number:
USER NUMBER,
MATCHING FLAG,
The Flag of Bulk
Call, The Flag Of
Casting Modules
By By business user:
multi- NET NUMBER, DO-
part call MAIN NUMBER,
USER NUMBER,
Trace Component

ULE NO, Trace module number of
Component the NE which needs
to be traced
By By node: NODE ID NODE ID node id of

smart corresponding NE
call
the NE which needs
to be traced
By SDN: NET NUM-

BER, DOMAIN
NUMBER, USER
NUMBER
END OF STEPS
Result Tracing other protocol signals is completed successfully.
Registering Signal Trace Tasks

database.
opened.
� Signal tracing settings have been completed.

Context This section introduces the tool bar's status when signal registering
succeeds and the reason why tracing requests are rejected.
Steps
in tool bar.
in Figure 92.
2. Click the Config button. User configures signal tracing condi-

tion according to introduction dialog box as shown in previous
sections.
3. If signal tracing task has been registered successfully in fore-
ground, tool bar's status is shown as Figure 93.

FIGURE 93 TOOL BAR STATUS
Blue status indicator lamp represents the status of tracing
progress, Pause and Stop tracing button are avail-

able.
Reason for registering failure:
If foreground rejects this tracing request, system prompts di-
alog box to explain. Common rejection reasons are shown as
following:
� the traced object is in tracing progress: in order to save
resource, signal tracing does not allow different terminals
trace same object ( for example: the same link), however,
SIP protocol is not in this scope.
� client is in tracing progress: one client only do one tracing
task at the same time, as a result, if this client has already
registered tasks in foreground, then this client is not al-
lowed to do other tracing tasks.
� tracing task has been cancelled by agent: as usual, tracing
by number or trunk, when number or trunk can not find
corresponding logical processing board (or module ) to dis-
pose, foreground agent do not know how to handle these
tasks, then these tasks are cancelled by agent.
� rejecting by ADAPTOR: protocol module ( such as
SCTP/M3UA/IUA/Q.931 and so on ) can not establish
tracing for some reasons, then it reports this error. How-
ever, tracing H.248 protocol module, when H.248 node is
configured static module, there is a switch Enable Trace,
if this switch is not turned on, then this error reports. for
other protocols modules, tracing could be established at
normal condition.
� there is no parameter record in database: traced object is
not configured correctly in database so as to signal trac-
ing module can not query related information from data-
base. For example, configuration of Zone & logical pro-
cessing board is not correct.
� can not get response from traced object: signal tracing
foreground module can not contact with traced protocol
module. The solution is to check protocol progress in corre-
sponding protocol processing board work effectively or not.
END OF STEPS
Result Registering signal trace tasks is completed successfully.

Viewing Signal Trace Results

Introduction After establishing tracing, protocol data returns, protocol data
shows in corresponding table. For some traced protocol saved in
form of binary, users are able to view their detailed decode.
Viewing H.248/MGCP Tracing Results

database.
opened.
Context View H.248 , MGCP tracing results which is shown in form of table.
Steps 1. H.248 , MGCP tracing results are saved in form of text. protocol
data shows in table as shown in Figure 94.
FIGURE 94 TRACING RESULT
2. Because of limit of table column width, H248 signal tracing

message this column is not easy to view. When user double
click certain column of table, Detailed data dialog box show-
ing detailed tracing data pops up as shown in Figure 95.

FIGURE 95 DETAILED DATA
END OF STEPS
Result Viewing H.248/MGCP tracing results is completed successfully.
Viewing SCTP/M3UA/IUA/Q.931/V5UA Tracing

Results
database.
opened.
Context View SCTP/M3UA/IUA/Q.931/V5UA tracing results which is shown
in form of table.
Steps 1. For SCTP/M3UA/IUA/Q.931/V5UA, their interface showing in-
cludes two parts as shown in Figure 96.

FIGURE 96 SCTP TRACING RESULT
The upper part of interface is a table showing some general

information of this protocol. The lower part is a tree view.
2. Select one row in upper part of interface, and its corresponding
information shows in tree view of lower part as shown in Figure
96.
3. For SCTP/M3UA, there is a special option : national signaling
point code.
SCTP encapsulates M3UA protocol, however, M3UA encapsu-
lates NO. 7 signal. When decoding SCTP or M3UA, it is neces-
sary to define format of NO.7 signal's signaling point code.
Select Config > Config SS7UP Analysis in Signaling Trace
interface, click on NSI encoding tab as shown in Figure 97.
FIGURE 97 NSI ENCODING

Select 24–bit NSI encoding or 14–bit NSI encoding and

click to view SCTP/MGCP tracing results again.
By default, system considers national signaling point code of
NO.7 signal as 24 bit.
4. Similarly, system supports M3UA's version: draft and formal
rfc3322. When decoding, user can select M3UA's version.
Select Config > Config M3UA version in Signaling Trace
interface as shown in Figure 98.
FIGURE 98 CONFIG M3UA VERSION
By default, version is Draft, user can modify and click to view

SCTP/MGCP tracing result again.
END OF STEPS
Result Viewing SCTP/M3UA/IUA/Q.931/V5UA tracing results is completed

successfully.
Viewing SS7UPTUP/ISUP/SCCP Tracing Results

database.
opened.
Context View SS7UPTUP/ISUP/SCCP tracing results which is shown in form
of table.
Steps 1. For SS7UPTUP/ISUP/SCCP whose tracing results saved in form
of binary, tracing results shows in table as shown in Figure 99,
take SCCP as example.
FIGURE 99 SCCP TRACING RESULT
2. Double click one row and detail code dialog box pops up as
shown in Figure 100.

FIGURE 100 SS7UP DETAIL CODE
END OF STEPS
Result View SS7UPTUP/ISUP/SCCP tracing results is completed success-

fully.
Cancelling Signal Tracing Tasks

Prerequisites Signal tracing has already been done.
Context This section introduces to cancel signal tracing tasks.
Steps
1. Select Trace > Stop tracing or click button in tool bar.
Tool bar of successful cancelling signal tracing tasks is shown
as Figure 101.
FIGURE 101 TOOL BAR OF SUCCESSFUL CANCELLING

2. After cancelling, Start tracing button is available while Stop

tracing button is not available.
END OF STEPS
Result Cancelling signal tracing tasks is completed successfully.
Saving Tracing Data As File

Context � Save tracing data in designated text file.
� If select saving tracing data in binary file when setting tracing
condition, then tracing data can be imported to be viewed in
interface.
� Signal Trace interface provides a method to save tracing data
after setting tracing condition. For displaying content in current
interface (only for table content which is saved in form of binary
or signal, not including protocol or signal's detailed decoding)
could be saved in form of text file.
Steps 1. Select View > Toolkit to open Toolkit window. In Figure 102,
select Save as Text File from popup menu.
FIGURE 102 SAVE AS TEXT FILE
2. Save dialog box pops up as shown in Figure 103.

FIGURE 103 SAVE
Input file name and select file type and then click the Save
button.
END OF STEPS
Result Saving tracing data as file is completed successfully.

Example For SCTP, its saving format is shown in Figure 104.
FIGURE 104 TRACING RESULT SAVED IN FORM OF TEXT FILE
It does not recommend to save tracing data in this way, for this
way could only save data showing in current interface. And during
tracing condition setting, the number of largest rows shown in in-
terface is configured. As a result, when tracing data's row number
exceeds this largest row number, the top rows can not be shown
any more, which means using this way to save data, saved data
might not be completed.
Importing Signal Tracing Data


Context Import saved original tracing data file to interface to be viewed.

Steps 1. Select View > Toolkit to open Toolkit window.
2. Select Data > Import or click button.

Open dialog box pops up as shown in Figure 105.
FIGURE 105 OPEN
If user select a file which do not meet demand, such as a text

file, system prompts error information as shown in Figure 106.
FIGURE 106 ERROR
Use file name suffix to filter, which means to drop down file
type of above dialog box as shown in Figure 107.

FIGURE 107 FILE NAME SUFFIX FILTER
3. When user select a proper file, importing can begin.

END OF STEPS
Result Importing signal tracing data is completed successfully.


Chapter 3
Network Diagnostic Test
Table of Contents
Network Diagnostic Test ................................................... 113
Network Diagnostic Test

Overview
Introudction Diagnostic test is proved very important for whatever deployment
or routine maintenance of equipment. That's because, with the di-
agnostic test, technical engineers can check if all equipment hard-
ware function normally so that if there's any failure, they can be
found and troubleshot in a timely manner. Normal operations of
system equipment thus are guaranteed. When exceptions occur,
possible causes should be diagnosed quickly in a simple and clear
manner, helping maintenance staff find out the actual causes and
troubleshoot the failures.
Diagnostic test has following functions:
� System Detect: detecting all boards' physical and running
status in SS shelf;
� Net Detect: mainly detecting net's connection status;
� Protocol Detect: mainly detecting protocols' disposal status;
� Info Inquire: querying running status of system;
� Data Detect: mainly detecting data memory control status;
� Performance View: viewing all boards' CPU and memory
running status and trunk using condition;
� SS resource report: mainly collecting resource information of
system to provide necessary means for system diagnosis. Re-
source report reflects using condition of system's each board
precisely to provide necessary means for make use of resource
more rational. Resource report also reflects each board's dis-
posal performance. Through detecting occupancy condition of
data area, full load of protocol disposal could be affirmed.
Explanation of In this manual, following terms concerning SS system are ex-
related terms plained as follows:

� Module number : some variables when doing SS internal de-

sign. In ZXSS10 SS1b, one board is just one module. calcu-
lation formula of module is: SC's module number is 0, slave
SC has no module number. While, other boards' module num-
ber equals to their corresponding slot number minus 2. If it
is multi-shelf cascade, slave shelf's module number is: 40×(
shelf number —1)+slot number-2.
� SS internal IP address: 168.2.x.y network segment: x is shelf
number, y is slot number. If this SPC is in NO. 1 shelf and NO.
11 slot, then internal communication IP is 168.2.1.11.
Detecting Board Attributes

database.
opened.
Context This topic checks the physical status and running status of all the
boards in the SS shelf. It includes following checks:
� Whether all the boards are in place
� Whether all the slots are powered on
� Whether the clips of all the boards are normal
� Whether the tasks of all the boards are completed
� Whether the Flash on each board is normal
� Connection between the boards
Steps 1. In the Topology Management interface, right-click a SS
and select the Diagnostic Management menu item from the
popup menu or select Views > Diagnostic Management
from the main menu.
2. In the Diagnose Management window displayed, select In-
stant Test > System Detect.
3. Select the shelf number to be checked and click the Detect
button. Add to routine test button means adding the system
test to the routine test task list.
SS1b boards information is displayed in the bottom window, as

Chapter 3 Network Diagnostic Test
FIGURE 108 SYSTEM DETECT
END OF STEPS
Result Detecting board attributes is completed successfully.
Detecting Network
Network detecting mainly includes: internal module of SS or com-
munication detecting between SS and external equipment, and
NIC net interface performance statistics.
Ping External Node

database.
opened.
Context This section introduces SS Ping external equipment. Through this,
users know if SS connects with external equipment.
Steps 1. In the Diagnose Management window, select Instant Test
> Net Detect from menu.
2. Select Ping External Node from Detecting Range
drop-down list.
3. Select resource module number from Module drop-down list.
4. Enter external equipment's IP address in Ping text box.
5. Click the Detect button.

Result is shown in output area as shown in Figure 109.
FIGURE 109 PING EXTERNAL NODE
Reference:
SS provides external ports with NIC board. Ping certain ex-
ternal equipment's IP address, if this IP address can not be
reached, through following methods to check:
i. Firstly, make sure NIC board selected for Module is cor-
rect and NIC board works normally. If NIC is in fault sta-
tus , please refers to <<ZXSS10 SS1b Softswitch Control
Equipment Troubleshooting Manual>> Foreground Fault.
ii. Check NIC routing connection with hardware is correct or
not and make sure external IP address is correct.
END OF STEPS
Result Ping external node is completed successfully.
Ping Internal Module

database.
opened.
Context This section introduces internal module Ping each other.

2. Select Ping internal Module from Detecting Range drop-

down list.
3. Select resource module number from Module drop-down list.
4. Enter external equipment's IP address in Ping text box.
Result is shown in output area as shown in Figure 110.
FIGURE 110 PING INTERNAL MODULE
Reference:
Internal module of SS Ping each other, if IP address can not be
reached, through following methods to check:
i. Firstly, make sure board selected for Module is correct.
Ping other boards from SC, SPC or NIC, and make sure the
boards selected work normally. If board is in fault status,
please refers to <<ZXSS10 SS1b Softswitch Control Equip-
ment Troubleshooting Manual>> Foreground Fault.
ii. Make sure internal module's IP address is correct. SS inter-
nal working IP: 168.2.x.y network segment, among which x
is shelf number, y is slot number. If this SPC is in NO. 1 shelf
NO. 11 slot, then internal communication IP is 168.2.1.11.
END OF STEPS
Result Ping internal module is completed successfully.

NIC Statistics
database.
opened.
Context This section introduces NIC network port.
2. Select NIC Statistics from Detecting Range drop-down list.
3. Select checking module from Module drop-down list.
4. Select port type in Port drop-down list.
NIC statistics is as shown in Figure 111.
FIGURE 111 NIC STATISTICS
Reference:
NIC statistics includes: receive, send, dispatch failure and pro-
tocols distribution items, among which they have their own
contents especial error byte number, through following meth-
ods to check:
i. Firstly, confirm NIC board status and to see if there are any
untreated critical warnings to cause error code.

ii. External in Port means network port between SS and ex-

ternal equipment, while, Internal in Port means commu-
nication network port between SS and internal board.
END OF STEPS
Result NIC statistics is completed successfully.
Detecting Protocol
Protocol detecting is mainly used to detect trunk group, SCTP link
and H.248 gateway status.
Detecting Trunk
database.
opened.
Context This topic describes procedure to check the protocol processing
status of trunks.
> Protocol Detect from menu.
2. Select Detect Trunk from Detecting Range drop-down list.
click Query Disaster Recovery or not according to actual con-
dition.
3. Fill in group number in Group NO.. Group number could be
queried in trunk group configuration in Configure Manage-
ment.
4. Click the Detect button. Link status of trunk group is shown
in output result area as shown in Figure 112.

FIGURE 112 CHECKING TRUNK GROUP STATUS
Note:
Executing the command of detecting certain trunk group num-
ber is successful or not. If it is unsuccessful, please check:
i. Make sure if this trunk group number exists and if there are
trunk data which still be used.
ii. If above respects have been affirmed, however, this com-
mand is still unsuccessful, please refer to <<ZXSS10 SS1b
Softswitch Control Equipment Data Configuration Manual
Trunk>> to do corresponding operations.
END OF STEPS
Result Deleting trunk is completed successfully.
Detecting SCTP
database.
opened.
status of SCTP link.


2. Select Detect SCTP from Detecting Range drop-down list.
3. Select module number from Module drop-down list and fill in
Node NO..
4. Click the Detect button. Link status of SCTP link is shown in
output result area as shown in Figure 113.
FIGURE 113 CHECKING SCTP LINK STATUS
Reference:
i. Select corresponding SPC board in Module, which means
to dispose SCTP protocol's SPC board.
ii. In Node NO., fill in the node desired to be detected, then
configured SCTP link and related status information could
be detected.
END OF STEPS
Result Detecting SCTP is completed successfully.
Detecting H248
database.
opened.


status of H.248.
2. Select Detect H.248 from Detecting Range drop-down list.
3. Select module number from Module drop-down list and fill in
Gateway NO..
4. Click the Detect button. Link status of H.248 is shown in out-
put result area as shown in Figure 114.
FIGURE 114 DETECTING H248
END OF STEPS
Result Detecting H.248 is completed successfully.
Querying System Information

This topic describes procedure to query the memory usage, basic
board information, traffic flow, routing metrics, SC disk informa-
tion, and port information of NIC, SSN, SPC, and SC modules.

Querying Memory Usage On Board

database.
opened.
Context This topic describes procedure to query memory usage on board.
> Info Inquire from menu.
2. Select 1.Memory Usage On Board from Inquiring Range
drop-down list.
3. Select desired module from Module drop-down list.
4. Click the Inquire button.
Memory usage on board is shown in output result area as
FIGURE 115 QUERYING BOARD MEMORY USAGE
END OF STEPS
Result Querying memory usage on board is completed successfully.
Querying Basic Information On Board

database.


opened.
Context This topic describes procedure to query basic information on board.
2. Select 2.Basic Info On Board from Inquiring Range drop-
down list.
Basic information on board is shown in output result area as
FIGURE 116 QUERYING BASIC INFORMATION ON BOARD
Reference:
Select desired module in Module, including SC, SPC board and
so on. Information of this module includes shelf type, board
type, board position, network port number, network port sta-
tus, IP address and so on.
END OF STEPS
Result Querying basic information on board is completed successfully.

Querying Net Flow On Board

database.
opened.
Context This topic describes procedure to query net flow on board.
2. Select 3. Net Flow On Board from Inquiring Range drop-
down list.
Net flow on board is shown in output result area as shown in
Figure 117.
FIGURE 117 QUERYING NET FLOW ON BOARD
Reference:
When net flow exceed certain load, corresponding alarms hap-
pen in system. Please refers to <<ZXSS10 SS1b Softswitch
Control Equipment Alarm and Notification>> manual.
END OF STEPS
Result Querying net flow on board is completed successfully.

Querying Route Information On Board

database.
opened.
Context This topic describes procedure to query route information on
board.
2. Select 4. Route Info On Board from Inquiring Range drop-
down list.
Route information on board is shown in output result area as
FIGURE 118 QUERYING ROUTE INFORMATION ON BOARD
Reference:
When something abnormal happens to board's route, cor-
responding alarms happen in system. Please refers to
<<ZXSS10 SS1b Softswitch Control Equipment Alarm And
Notification Handling>> manual.
END OF STEPS
Result Querying route information on board is completed successfully.

Querying Disk Information On SC

database.
opened.
Context This topic describes procedure to query disk information on board.
2. Select 5. Disk Info On SC from Inquiring Range drop-down
list.
3. Select shelf number from Shelf drop-down list.
Disk information on SC is shown in output result area as shown
in Figure 119.
FIGURE 119 QUERYING DISK INFORMATION ON SC
Reference:
When something abnormal happens in SC's disk, correspond-
ing alarms happen in system. Please refers to <<ZXSS10
SS1b Softswitch Control Equipment Alarm And Notification
Handling>> manual.
END OF STEPS
Result Querying disk information on SC is completed successfully.

Querying Port Flow On SSN

database.
opened.
Context This topic describes procedure to query port flow on SSN.
2. Select 6. Port Flow On SSN from Inquiring Range drop-
down list.
3. Select objective SSN board number from Module drop-down
list.
Port flow on SSN is shown in output result area as shown in
Figure 120.
FIGURE 120 QUERYING DETAIL ON SSN
SSN board as key position of digital switching system is to re-

alize:
� providing Ethernet switching with 24 100MBT ports, among
which 15 ports are communication bus between front 13
SPC boards and 2 SC boards in a same shelf. 6 100MBT
ports function as back NIC board's communication bus to
realize interwork among system control, monitoring and
alarm information. In addition, another 3 100MBT ports
function as system communication channel for cross-rack
or extended cross-rack. Reserve 2 1000MBT ports to NIC
board's output as external network interface.

� providing one 485 bus as auxiliary communication channel

through which SC controls SSN.
END OF STEPS
Result Querying port flow on SSN is completed successfully.
Querying Detail On SSN

database.
opened.
Context This topic describes procedure to query detail on SSN.
2. Select 7. Port Detail On SSN from Inquiring Range drop-
down list.
3. Select SSN board number from Module drop-down list and
enter SSN port number in Port text box.
Port detail on SSN is shown in output result area as shown in
Figure 121.
FIGURE 121 QUERYING DETAIL ON SSN
END OF STEPS

Result Querying port detail on SSN is completed successfully.
Detecting Data
This topic describes procedure to check data area queue and table
capacity of SPC board. When abnormal data appear, corresponding
level's alarm appear at the same time. Specific disposal methods
please refers to <<ZXSS10 SS1b Softswitch Control Equipment
Alarm And Notification Handling>> manual.
Detecting Data Area Queue

database.
opened.
Context This topic describes procedure to detect data area queue.
> Data Detect from menu.
2. Select 1. Detect Data Area Queue from Detecting Range
drop-down list.
3. Select objective board module number from Module drop-
down list.
Data area queue is shown in output result area as shown in
Figure 122.

FIGURE 122 DETECTING TABLE SPACE
END OF STEPS
Result Detecting data area queue is completed successfully.
Detecting Table Space

database.
opened.
Context This topic describes procedure to detect table space.
2. Select 2. Detect Table space from Detecting Range drop-
down list.
Table space is shown in output result area as shown in Figure
123

FIGURE 123 DETECTING TABLE SPACE
Reference:
If table space detects something abnormal, system generates
corresponding alarms, please refers to <<ZXSS10 SS1b
Softswitch Control Equipment Alarm And Notification Handling
Manual>>.
END OF STEPS
Result Detecting table space is completed successfully.
Detecting Procedure
database.
opened.
Context This topic describes procedure to detect procedure.
2. Select 3. Detect Procedure from Detecting Range drop-
down list.
Procedure information is shown in output result area as shown
in Figure 124.

FIGURE 124 DETECTING PROCEDURE
END OF STEPS
Result Detecting procedure is completed successfully.
Detecting Table Capacity

database.
opened.
Context This topic describes procedure to detect table capacity.
2. Select 4. Detect Table Capacity from Detecting Range
drop-down list.
3. Select objective board module number from Module drop-
down list.
Table capacity information is shown in output result area as

FIGURE 125 DETECTING TABLE CAPACITY
END OF STEPS
Result Detecting table capacity is completed successfully.
Viewing Performance
Viewing performance is used to observe such as CPU, memory
and trunk circuit utilization status and so on. If CPU overloads
and other abnormal condition happens, system generates corre-
sponding level alarm. Specific disposal methods please refers to
<<ZXSS10 SS1b Softswitch Control Equipment Alarm And Notifi-
cation Handling Manual>>.
Viewing CPU & Memory

database.
opened.
Context This topic describes procedure to viewing CPU & memory.
> Performance View from menu.
2. Click on the View CPU & Memory tab.

3. Select objective board module number in View CPU & Mem-

ory drop-down section, at most select four modules.
4. Enter time interval for getting sampling data in Time Interval
field. The time interval can not be less than 0.1 second.
5. Click the Begin button.
CPU and memory utilization status is shown in output result
area as shown in Figure 126.
FIGURE 126 VIEWING CPU & MEMORY
6. Click the Stop button and then click the Open button, se-
lect Open CPU record or Open memory record from popup
menu to open saved record file.
Note:
If board CPU overloads or other abnormal condition hap-
pens, corresponding alarms are generated. Please refers to
<<ZXSS10 SS1b Softswitch Control Equipment Alarm And
Notification Handling Manual>>.
END OF STEPS
Result Viewing CPU & memory is completed successfully.

Viewing Trunk Circuits

database.
opened.
Context This topic describes procedure to viewing trunk circuits.
> Performance View from menu.
2. Click on the View Trunk Circuits tab.
3. Enter group number in Group NO.
4. Enter time interval for getting sampling data in Time Interval
field. The time interval can not be less than 5 seconds.
5. In Content field, click Busy Trunk, Idle Trunk, Blocked
Trunk or Query Disaster Recovery according to actual
needs.
6. Click the Begin button.
Trunk circuit status is shown in output result area as shown in
Figure 127.
FIGURE 127 VIEWING TRUNK CIRCUITS
END OF STEPS
Result Viewing trunk circuits is completed successfully.

Viewing Resource Report

database.
opened.
Context This topic reports analysis of the following SS resources.
� SS global system resource status analysis
� SS board system resource status analysis
� SS data area resource status analysis
� SS board memory and CPU status analysis
� SS trunk group status analysis
� SS background database status analysis
> SS resource report from menu as shown in Figure 128.
FIGURE 128 SS RESOURCE REPORT
2. Select SS resource report item and click the Detect button.

Save dialog box pops up as shown in Figure 129.

FIGURE 129 SAVE
3. Specify the destination folder and click the Save button.

4. Resource report is displayed, as shown in Figure 130.

FIGURE 130 VIEWING RESOURCE REPORT
END OF STEPS
Result Viewing resource report is completed successfully.
Viewing Board Test

database.
opened.
Context This section introduces to observe board testing.
� Observe board instant testing, display board's position and
type; test board online status, Flash status, memory and CPU
utilization, routing information and port flow utilization.
� For active/standby equipment, check communication of active
and standby board is normal or not.
� Check board's tasks starting condition and disk utilization of
SC are normal or not.
> Board Test from menu.
2. Select the board item needed to be test in the Select Test
plane, click the Test button. Testing result displays as shown
in Figure 131.

FIGURE 131 VIEWING BOARD TEST
3. Click the Add to routine test button to add board test into
routine test task list.
END OF STEPS
Result Viewing board test is completed successfully.
Viewing Routine Test

database.
opened.
Context This section introduces to view routine test.
� Function of routine test is deployment or maintenance people
select testing objects and projects according to actual needs,
and preset a testing time. When testing time arrives, diag-
nosis testing system sends testing command automatically to
foreground and test preset testing projects.
� Most testing projects introduced in previous sections could be
added into routine test through entering Instant test interface
and click the Add to routine test button.
Steps 1. In the Diagnose Management window, click on the Routine
Test tab from menu.
Routine test interface opens as shown in Figure 132.

FIGURE 132 ROUTINE TEST
2. Configure the routine testing time by fixed interval or by month

& week.
3. After setting all information, click the Set task button.
Routine task appears in routine task list as shown in Figure
133.

FIGURE 133 ROUTINE TEST I
4. According to actual needs, adjust routine tasks by right-clicking

newly added routine task and then selecting refresh, suspend
or delete from popup menu.
END OF STEPS
Result Viewing routine task is completed successfully.

Chapter 4
System Maintenance
Table of Contents
Overview........................................................................ 143
Configuring KD Flag ......................................................... 143
Configuring KB Flag ......................................................... 145
Configuring ICP Flag ........................................................ 147
Modifying Named Timer.................................................... 149
Configuring SNMP OAM Console......................................... 151
Global Service Data Configuration ...................................... 152
Modifying Service Conflict ................................................. 155
Overview
This chapter describes daily operation about global maintenance.
Configuring KD Flag
Prerequisites � NetNumen Server is installed, configured, and connected with
database.
� Data Configure window is open in NetMumenN31 Unified
Management System.
Context This topic describes procedure to configure KD Flag.
Note:
It’s not recommended to add, modify or delete the KD flag on site,
perform the operation with professional guide.
KD value is a priority value based on different call types and user

types. To control the priority of call types and user types.
Steps 1. In the Data Configure window, select Global (G) > System
(M) > KD Flag (D) from menu bar.
KD Flag Configuration dialog box appears as shown in Figure
134.

FIGURE 134 KD FLAG CONFIGURATION
2. Execute the following operations as shown in Table 16 accord-

ing to actual needs.
TABLE 16 KD OPERATION GUIDE
Purpose Operation
Add KD flag i. Click the Add button

ii. Configure Call Type field
iii. Configure User Type field
iv. Enter KD Value field value
Modify KD flag i. Click the Modify button

ii. Enter KD Value field value
Delete KD flag i. Click the Delete button

ii. Click the OK button to confirm deletion
operation in popup dialog box
A summary of interface related parameters are given in the

following Table 17.

Chapter 4 System Maintenance
TABLE 17 SUMMARY OF PARAMETERS FOR KD FLAG

CONFIGURATION WINDOW
Field Name Description
Call Type List all call types
User Type List all user types
Much smaller the value is, much higher the

KD Value
priority is
END OF STEPS
Result KD flag is configured successfully.
Configuring KB Flag
database.
� Entering into Data Configure window in NetMumenN31 Uni-
fied Management System.
Context This topic describes procedure to configure KB Flag, includes KB
value for error code, CAS, TUP, ISUP message.
Note:
It’s not recommended to add, modify, or delete the KB flag on site,
perform the operation with professional guide.
Steps 1. In the Data Configure window, select Global (G) > System
(M) > KB Flag (B) from menu bar.
KB Flag Configuration dialog box appears as shown in Figure
135.

FIGURE 135 KB FLAG CONFIGURATION
2. Execute the following operation as shown in Table 18 according

to actual needs.
TABLE 18 KB OPERATION GUIDE
Purpose Operation
Add KB flag i. Click the Add button

ii. Enter Error Code field value
iii. Enter KD Value field value
iv. Enter KB Value (for CAS)field value
v. Enter KB Value (for TUP)field value
vi. Enter KB Value (for ISUP)field value
Update KB flag i. Click the Modify button

ii. Enter KB Value (for CAS) field value
iii. Enter KB Value (for TUP) field value
iv. Enter KB Value (for ISUP) field value
Delete KB flag i. Click the Delete button

A summary of related parameters are given in the following

Table 19.

TABLE 19 SUMMARY OF PARAMETERS FOR KB FLAG

CONFIGURATION
Error Code Public error code generated in SS
KD Value Priority value
KB Value (for KB value used in CAP message

CAP)
KB Value (for KB value used in TUP message

TUP)
KB Value (for KB value used in ISUP message

ISUP)
END OF STEPS
Result KB flag is configured successfully.
Configuring ICP Flag

database.
Context This topic describes procedure to configure ICP Flag, configure ser-
vice operation type flag and tone number to be played for error
code.
Note:
It’s not recommended to add, update, delete the ICP flag on site,
please ask professional personnel for help.
Steps 1. On the Data Configure – [x.x.x.x] window, select Global

(G) > System (M) > ICP Flag (I) form the mean bar.
ICP Flag Configuration dialog box appears as shown in
Figure 136.

FIGURE 136 ICP FLAG CONFIGURATION
2. Execute the following operation Table 20 as required.
TABLE 20 ICP OPERATION GUIDE
Purpose Operation
Add ICP flag i. Click the Add button

ii. Enter Error Code field value
iii. Enter Service Operation Type Flag
field value
iv. Enter Tone NO. to Be Played field
value
Update ICP flag i. Click the Modify button

ii. Enter Service Operation Type Flag
field value
iii. Enter Tone NO. to Be Played field
value
Delete ICp fla i. Click the Delete button

A summary of related parameters are given in Table 21 .

TABLE 21 SUMMARY OF PARAMETERS FOR ICP FLAG

CONFIGURATION
Error Code Public error code generated in SS
Service Operation Service operation type flag for configured

Type Flag error code
Tone NO. to Be Tone No. to be played for configured error

Played code
END OF STEPS
Result ICP flag is configured successfully.
Modifying Named Timer

database.
Context This topic describes procedure to modify named timer.
Note:
It’s not recommended to update on site, perform operation with
professional guide.

(G) > System (M) > Named Timer (N) from the mean bar.
Named Timer Configuration dialog box appears as shown in
Figure 137.

FIGURE 137 NAMED TIMER CONFIGURATION
2. On Named Timer Configuration dialog box, click the Modify

button.
Modify Named Timer dialog box appears as shown in Figure
138.
FIGURE 138 MODIFY NAMED TIMER DIALOG BOX
A summary of related parameters are given in Table 22.
TABLE 22 SUMMARY OF PARAMETERS FOR NAMED TIMER
Named Timer ID number of named timer

No.
Duration(ms) Duration for timer
Timer Name Name for timer

Note:
Part of specific named timer please refers to Appendix A
Common Named Timer Description.
END OF STEPS
Result Named timer is configured successfully.
Configuring SNMP OAM

Console
database.
Context This topic describes procedure to configure SNMP OAM console.
Steps 1. On the Data Configure – [x.x.x.x] window, select Global (G)
> System (M) > SNMP OAM Console (S) from the mean bar.
Configure SNMP OAM Console dialog box appears as shown
in Figure 139.
FIGURE 139 CONFIGURE SNMP OAM CONSOLE
2. Execute the following operation Table 23 as required.

TABLE 23 OAM CONSOLE OPERATION GUIDE
Purpose Operation
Add SNMP OAM i. Click the Add button

Consol
ii. Enter Upper-Level Network field value
iii. Enter SNMP Version field value
iv. Enter Latest Error Code field value
v. Enter Upper-Level Network
Management Center field value
Update SNMP OAM i. Click the Modify button

Console
ii. Enter SNMP Version field value
iii. Enter Latest Error Code field value
iv. Enter Upper-Level Network
Management Center field value
Delete SNMP OAM i. Click the Delete button

Console
A summary of related parameter are given in the following

Table 24.
TABLE 24 SUMMARY OF PARAMETERS FOR SNMP OAM

CONSOLE
Upper-Level Network IP address of upper-level network
SNMP Version Version of SNMP protocol
Latest Error Code Error code generated latterly
Upper-Level Network Name of upper-level network management

Management Center center
END OF STEPS
Result OAM console is configured successfully.
Global Service Data

Configuration
This section introduces how to configure global service data, take
“90007-Call Delay of Urgent Special Service” for example, other
global service data please refers to Appendix A

Entering Global Service Interface

database.
Context This topic describes procedure to enter service data configuration.
It includes SS global service data, services, protocols and so on.
Some more important service date configuration is shown here.
Steps 1. On the Data Configure – [x.x.x.x] window, select Global (G)
> System (M) > Global Service Data (C) from the mean
bar.
Global Service Data dialog box appears as shown in Figure
140.
FIGURE 140 GLOBAL SERVICE DATA
2. Take “90007-Call Delay of Urgent Special Service” for example,

other global service please refers to Appendix A .
END OF STEPS
Result Entering global service interface is completed successfully.

(Configuration Example) Modifying

Call Delay of Urgent Special Service
Prerequisites Entering into Global Service Data window in NetMumenN31
ZTE Unified Management System.
Context This topic describes procedure to configure call delay of urgent
special service.
Steps 1. On the Global Service Data window which as shown in Figure
140, select service > 90007-Call Delay of Urgent Special
Service menu item from the tree directory in the left side of
the window.
2. Click the Modify button.
Modify Call Delay of Urgent Special Service dialog box ap-
pears as shown in Figure 141.
FIGURE 141 MODIFY CALL DELAY OF URGENT SPECIAL

SERVICE
3. After updating, click the OK button to confirm operation, or

click the Exit button to cancel operation.
A summary of related parameter are given in Table 25.
TABLE 25 SUMMARY OF PARAMETERS FOR CALL DELAY OF

URGENT SPECIAL SERVICE
Set Call Delay of The delay time is between number be dialed

Urgent Special in terminal and number be analyzed.
It can be hang up immediately when make
urgent special number accidentally
END OF STEPS
Result Call delay of urgent special service is configured successfully.

Modifying Service Conflict

database.
� Entering into Data Configure window in NetMumenN31 ZTE
Unified Management System.
Context This topic describes procedure to modify service conflict.
Service conflict configuration is configured the relations between
one and others.
1. It can’t be registered or activated service if it appears on reg-
ister conflict.
2. It can’t be registered or activated service if it appears on acti-
vate conflict.
(G) > System (M) > Service Conflict (C) from the mean
bar.
Service Conflict dialog box appears as shown in Figure 142.
FIGURE 142 SERVICE CONFLICT DIALOG BOX
2. Select required configured service on the left of service conflict

dialog box.
3. Click the Modify button.
Modify Service Conflict dialog box appears as shown in
Figure 143.

FIGURE 143 MODIFY SERVICE CONFLICT DIALOG BOX
4. Select Register Conflict tab, select conflict service conflict

with selected service in step 2 on Register Conflict window.
5. Select Activate Conflict tab, configure activate conflict ser-
vice conflict with selected service in step 2.
6. Click the OK button to confirm operation.
END OF STEPS
Result Service conflict is configured successfully.

Appendix A
Appendix
Table of Contents
Common Named Timer Description .................................... 157
Global Variable Description ............................................... 164
Common Named Timer

Description
Named
Default
Timer Timer Name
duration
No.
1 20s dial-up timer
2 10s the two parties handshake timer
3 15s wait EV_L3L4_PREPARE_USEr_r_MEDIA_RPL
4 20s calling party waiting for alerting timer
5 15s calling party waiting for media matching timer
calling waiting for called picking up the

6 60s
handset timer
calling party waiting for connecting media

7 5s
timer
8 60s BCM_TIMEr_r_WAITING_FIRST_DIAL
9 60s wait for ACK of release signal timer
Waiting for message which confirms the

10 60s
release of two parties
11 60s wait for media release confirm message timer
12 3s wait for Radius confirm message timer
Time-lapse protection for releasing signal after

13 1s
releasing media
called party waiting for answer ACK message

14 5s
timer

Named
Default
Timer Timer Name
duration
No.
calling waiting for ACK of other side modifying

15 1s
media
16 120s wait EV_L3L4_CHANGE_USEr_r_MEDIA_RPL
17 4s interval overtime timer
18 1s named timer 018
19 3s wait for asynchronous query password timer
wait for asynchronous register operations

20 60s
timer
21 4s the called wait for ACK of the setup_ind
22 15s wait EV_L3L4_PREPARE_USEr_r_MEDIA_RPL
23 20s BCM_TIMEr_r_WAITING_L3L4_ALERTING_IND
BCM_TIMEr_r_WAITING_L3L4_AN-
24 60s
SWEr_r_IND
25 5s the called wait for ACK of the calling
26 20s EV_L3L4_ANSWEr_r_IND For CFNR
27 120s T wait EV_L3L4_CHANGE_USEr_r_MEDIA_RPL
Called party wait for ACK of the other side to

28 10s
modify media
29 5s call wait resume user media timer
30 5s Registered Call and hot line timer
31 60s Ring Back Tone Timer
32 15s BCM_TIMEr_r_TONE_BUSY
33 40s BCM_TIMEr_r_TONE_HOWL
34 15s BCM_TIMEr_r_TONE_VACANT
35 5s Timer to Get MCL for SOSM
36 10s Timer to Prepare LIG Media for SOSM
37 10s Timer to Connect MCL for SOSM
Timer to Change Remote Media of LIG for

38 10s
SOSM
39 10s Timer to Connect Caller with LIG for SOSM
40 240s BCM_TIMEr_r_BILL_STATISTICS
41 1800s BCM_TIMEr_r_BILL_CHARGE

Appendix A Appendix
Named
Default
Timer Timer Name
duration
No.
42 1s BCM_TIMEr_r_PPS_TALKING_TIME
43 60s BCM_TIMEr_r_PPS_LAST_MINUTE
Local No-Answer Timer in O_BCM when callee

44 0s
is in this SS
Local No-Answer Timer in T_BCM when callee

45 0s
is in this SS
46 6s BCM_TIMEr_r_PPS_TONE_PA
47 1s C_BCM_T47_EXPIRY
48 90s BCM_TIMEr_r_TONE_ALERTING_FOr_r_DDD
49 120s BCM_TIMEr_r_TONE_ALERTING_FOr_r_IDDD
50 2s BCM_TIMEr_r_BUFFEr_r_MESSAGE
51 5s T wait EV_C_MCM_InitMpcAck
52 20s T wait EV_C_MCM_Alert
53 60s T wait EV_C_MCM_Connect
54 5 s T wait EV_CC_CONNECT_ACK
55 10s T wait EV_C_MCM_DropCall
56 60s BCM_TIMEr_r_ACS_ALERTING_OVER
57 3s BCM_TIMEr_r_ACS_REG_CONFIRM
58 3s BCM_TIMEr_r_ACS_DEL_CONFIRM
59 15s BCM_TIMEr_r_ACS_TONE_PA
61 5s wait EV_C_MCM_InitMpcAck
65 10s wait EV_C_MCM_DropCall
BCM_TIMEr_r_STM_WAITING_SCM_Instruc-
70 90s
tion
71 2s BCM_TIMEr_r_WAITING_CC_QueryRecordAck
72 60s BCM_TIMEr_r_TONE_INPUT_VCONF_PSD
73 40s BCM_TIMEr_r_WAITING_MD_GetQServerInfo
74 4s BCM_TIMEr_r_WAITING_QS_QueueQueryAck
75 5s BCM_TIMEr_r_WAITING_QS_AllocDesk
76 4s BCM_TIMEr_r_WAITING_MD_GetOprqTerm

Named
Default
Timer Timer Name
duration
No.
receiving move command from multiparty

77 1s
while AG self-circle
receiving move command from multiparty

78 1s
while AG self-circle
80 15s TIMEr_r_CBB_WAITING_RCS_BCM_REG_ACK
81 15s TIMEr_r_CBB_WAITING_RCS_BCM_DEL_ACK
82 15s TIMEr_r_CBB_WAITING_CBB_BCM_REG_ACK
83 15s TIMEr_r_CBB_WAITING_CBB_BCM_DEL_ACK
84 15s TIMEr_r_CBB_WAITING_L3L4_SETUP_ACK
85 20s TIMEr_r_CBB_WAITING_L3L4_ALERTING_IND
86 60s TIMEr_r_CBB_WAITING_L3L4_ANSWEr_r_IND
87 4s TIMEr_r_CBB_WAITING_CC_SETUP_ACK
TIMEr_r_CBB_WAITING_CC_CALLBACK_RE-
88 110s
SUME
TIMEr_r_CBB_WAITING_L3L4_INFORMA-
89 60s
TION_IND
90 60s BCM_TIMEr_r_MCN_TONE_PCI
91 5s SS7_WAITING_L3L4_INFORMATION_IND
92 3600s BCM_TIMEr_r_LONG_CALL_ALARM
93 1s redirectnumber,play tone and hold on timer
94 30s BCM_TIMEr_r_MCT_AVAILABLE
95 60s BCM_TIMEr_r_MCT_FIRST_DIAL
96 30s BCM_TIMEr_r_MCT_TONE_PA
97 5s BCM_TIMEr_r_SPS_WAITING
98 30s BCM_TIMEr_r_SELFNUMREPORT_TONE_PA
100 600s Call Park Recall Timer
BCM_TIMEr_r_O_WAITING_CC_SUS-
110 5s
PEND_ACK
111 5s BCM_TIMEr_r_O_WAITING_CC_RESUME_ACK
112 60s BCM_TIMEr_r_O_LOCAL_CALL_REANSWER
113 90s BCM_TIMEr_r_TOLL_CALL_REANSWER
114 120s BCM_TIMEr_r_INT_CALL_REANSWER

Appendix A Appendix
Named
Default
Timer Timer Name
duration
No.
BCM_TIMEr_r_T_WAITING_CC_SUS-
115 5s
PEND_ACK
116 5s T_BCM wait CC_RESUME_ACK
117 60s BCM_TIMEr_r_T_LOCAL_CALL_REANSWER
118 2s BCM_TIMEr_r_COT_MG_COTRESULT_IND
119 2s BCM_TIMEr_r_COT_SS7_COTRESULT_IND
120 2s BCM_TIMEr_r_COT_CC_COTRESULT_IND
121 0.5s BCM_TIMEr_r_COT_WAIT_LOOP_TIME
122 2s BCM_TIMEr_r_COT_WAIT_MML_MGRSLT
123 2s BCM_TIMEr_r_COT_WAIT_MML_SS7RSLT
BCM_TIMEr_r_COT_WAIT_MML_RE-
124 2s
QUEST_ACK
125 5s BCM_TIMEr_r_COT_TMCOT_BCM2MML
126 60s BCM_TIMEr_r_COT_TMCOT_MMLCOT_AGAIN
127 1s BCM_TIMEr_r_COT_WAIT_L3L4_RSP_RPL
128 120s BCM_TIMEr_r_O_WAITING_MD_SIPREGADDR
129 120s BCM_TIMEr_r_O_WAITING_MD_SIPNUM
130 180s BCM_TIMEr_r_FOr_r_SIP_PROXY
National No-Answer Timer when callee is in

131 0s
this SS
International No-Answer Timer when callee is

132 0s
in this SS
133 5s BCM_TIMEr_r_O_RS_WAITING_ROUTE_ACK
134 1s BCM_TIMEr_r_PPS_WAIT_CTX_BIGNUM
135 2s BCM_TIMEr_r_O_WAIT_DISCONNECT
136 6s wait call back timer
137 1s configuration in interface
138 1s wait for the dial-up end ACK message
139 2s trunk dial-up secondly
140 1s V5 user diaplay the calling number operation
141 1s V5 user diaplay the calling number operation

Named
Default
Timer Timer Name
duration
No.
Auditing CCB - BCM send EV_L4L3_DE-

142 1s
TECT_ACTIVE_IND
H323 calling wait EV_L3L4_USERMEDIA_IND

143 10s
after EV_L3L4_SETUP_IND
H323 called wait EV_L3L4_USERMEDIA_IND

145 10s
afterEV_L3L4_ALERTING_IND
calling party wait for EV_L3L4_CHANGEME-

147 15s
DIA_RES
calling party wait for EV_CC_CHANGE_ME-

148 15s
DIA_ACK
calling party wait for

149 15s
EV_L3L4_CHANGE_USEr_r_MEDIA_RPL
called party wait for EV_L3L4_CHANGEME-

150 15s
DIA_RES
151 5s wait for the ACK of CCB auditing
152 12s CAS collect number time
153 5s CAS wait for the called to disconnect the call
CAS wait for the called to report the alerting

154 60s
message
calling of CAS wait for the called to send the

155 60s
alerting message
156 15s called EV_CC_CHANGE_MEDIA_ACK
157 15s called EV_L3L4_CHANGE_USEr_r_MEDIA_RPL
wait for the other side of Fax to modify the

158 120s
media
159 120s wait for the end of Fax
A TIMER OF BCM WAIT EV_L3L4_DE-

1001 5s
TECTRT_RPL
A TIMER OF BCM WAIT EV_L3L4_DETECTR-

1002 5s
TRESULT_IND
1003 5s A TIMER OF BCM CHECK RING BACK AGAIN
A TIMER OF BCM WAIT EV_L3L4_MOD-

1004 5s
IFY_RTPMODE_RPL
A TIMER OF BCM WAIT EV_L3L4_FAX-

1005 15s
CONCHG_IND

Appendix A Appendix
Named
Default
Timer Timer Name
duration
No.
1006 5s A TIMER OF BCM WAIT SCM_BCM_SRIAck
1007 5s A TIMER OF BCM WAIT DB ASSERT RIGHT ACK
A TIMER OF BCM WAIT EV_CC_DRINFORES

1008 5s
WHEN BACKUP
A TIMER OF BCM WAIT HLR ACK WHEN

1009 5s
ADD,DELETE,MODIFY SERVICE
1010 5s BCM_TIMEr_r_WAIT_O_SEIZE_TER
1011 5s BCM_TIMEr_r_WAIT_T_SEIZE_TER
1012 5s BCM_TIMEr_r_WAIT_O_GETTRKINFO
1013 5s BCM_TIMEr_r_WAIT_T_GETTRKINFO
A TIMER IS INTERVAL BETWEEN HALF

1014 240s
CALLING OF CHECK DATA AREA
A TIMER OF BCM WAIT EV_CC_DETECT_AC-

1015 5s
TIVE_ACK
1016 5s Cost called wait for changing media by himself
1017 1.8s BCM_TIMER_WAIT_CHARGEINF_TIME
BCM_TIMER_WAIT_CHARGEINF_FROMBILL-
1018 2s
SERVER
1019 12s BCM_TIMER_WAIT_TIME_TO_NEXTDAY
1020 3s BCM_TIMER_WAIT_VIPRES
1021 40s BCM_TIMER_VIP_WAIT_TIMER
1022 2s BCM_TIMER_WAITING_CRMEDIA
1023 180s BCM_TIMER_WAIT_O_ISDN_RESUME
1024 180s BCM_TIMER_WAIT_T_ISDN_RESUME
1025 180s BCM_TIMER_WAIT_CC_ISDN_RESUME
1026 2s BCM_TIMER_WAIT_HAIRPIN2RTP
1027 2.5s BCM_TIMER_O_MC_CONFLICT
1028 0.5s BCM_TIMER_T_MC_CONFLICT
1030 1s Waiting for X2 serial number
Waiting for the time length of UP/DOWN

1031 2.5s
MEDIA RES
1033 210s BCM_TIMER_COT_WAIT_MML_SS7RELORREQ
1034 3600 BCM_TIMER_ALARM_TRUNK_LONG_CALL

Named
Default
Timer Timer Name
duration
No.
1035 180s BCM_TIMER_DETECT_UNSTEADY_DATAAREAR
1038 300s BCM_TIMER_SCM_PA_PCI
BCM_TIMER_TONE_CALLEDPAY-
1039 6s
HINT_FOR_CALLER
BCM_TIMER_TONE_CALLEDPAY-
1040 6s
HINT_FOR_CALLED
1041 6s BCM_TIMER_TONE_PEERMONITORED_HINT
1042 6s BCM_TIMER_TONE_ATTENTION_FOR_CFW
Global Variable Description

Switch Name
10011 CF CID Switch
10051 Time Zone
10072 Account Congestion Control
10161 Global Traffic Configuration
10165 Traffic control switch
10216 MON SDN
10226 DropBack SDN
10451 Monitor Tone Configuration
10541 H code Translation Control
10551 Protocol Link Trigger NIC
10555 Element Sustain Bearer Channel Alarm
10571 Not Switch
10581 Not Switch Back
10591 only switch back pri-used zone
10601 Local Office Code Code Tag
10642 Auto. Format SDN Configuration
10652 Add '+' Before International Calling Number
10653 Add CIC In CallBill
10654 Add Pilot In Callbill

Appendix A Appendix
Switch Name
10681 Call Limit Configuration
10683 Country and Area Configuration
10684 Carrier Configuration
10685 Automatic Call Repetition
10691 Common User Repeated Pulse Flag
10692 Pstn Subscriber In WAC dial directory number

Control
10696 Access Code And AG User Access Code Configura-

tion
10706 Add-Service Type
10862 Special Access Code of DR In Service
10882 Selection Count
11024 CUG Standard Q.735 Switch
11052 BEEP Tone Configuration
11062 Call Restriction According To User Types
11082 MAP/MAP+Amalgamation(monitor)
11172 SS Export Partition Bills
11471 Custom Right Definition
11863 The Module of The Traffic Management Server
11931 Checking Trunk if busy Switch
12551 Protocol Band Width Parameter
12562 Fail Code/Alarm Code Processing Switch
12563 Password Input Times In India
12711 MML Activable CPU Control Of Percent
12774 SS is no transmitted in the flow of Vast-Nodeid

switch
12885 Global Monitor Number Configuration
13003 Old Domain Mode Configuration
13011 Not create node automatically for billing command
13063 Congestion control tasks in support of the suspen-

sion or resume
13073 SS Support NIC Internal Loop

Switch Name
60092 Checking Trunk Group Name
30041 Way of Treating With Service
30044 Switching Time of SC(s)
30091 QoS Statistical Switch
30101 Radius Server Module
30111 Enable Roaming
30121 Lowest Cost Route Switch
30151 Long Conversation Disconnect Configuration
30154 Move Up the user to configure privileges
30201 Authorization Server Switch
30482 ACM configuration
30632 Digit Analysis Max Length Authentication Switch
30633 Monitor Function
30671 No.7 Paratmeters Transfer
30901 CRBT Priority Configuration
30921 Continue Call While User Data Unreliable
30922 Incoming Charging number format
30923 Can not call self number
31022 Password Service Configuration
31023 Conduct Fail Flag
31031 Multi Area Code Switch
31101 Service Send SCP Using Call Number
31111 Call Waiting Service Mode
31115 Ability of SS to access SHLR
31121 Dialing Tone Configuration
31153 The Transfer Count of Big OPR Console That Com-

puter is On Duty
31231 Global Sms DAS
31241 CPU Special Traffic Control Configuration
31251 WAC Search for the Type of HLR Number
31261 16KC Plus Charging does not search for Bill-Server

Appendix A Appendix
Switch Name
31301 Transfer Service Band Charging Method
31311 Not Charging Output Ticket Control
31312 Play Voice Prompt According to Parameter Aler-

tingPattern
31321 North Interface Output Format Configuration
31353 MAP Extend
31481 INAP Protocol Position Number Dealing With Com-

patibility Switch
31516 VIC Access Code
31521 SPC Congestion Traffic Control
31531 Billing Switch for Automatic Reply Test
31534 Fill in List of Called Billing Number
31564 Caller Intelligence Service Key and its Access Code

when Filling in Bill was Triggered Successfully at
First Time
31565 SSP Transmitting PA/P Message to Exterior IP

Equipment
31573 SHLR Use Skip Das
31574 List of Call is Filled in QoS Information
31583 IP Prefix Switching
31585 Search SIP User Register Address Switch
31592 Process When SHLR Called Number is not Existent
31606 All Service Shield Access Code
31625 Pulse Billing Configure
31883 Control SS Switch when SHLR Meets Error
31884 DN and LRN are Conflict and querying hlr fail

Switch
31903 Switch of Tone for SCP One Number Service
31943 Long-Distance Call Judge New Mode
31944 Transform the calling number for traffic statistics
31963 call after access code call control
31994 AG/TG not send ANM
31995 After ANM ACM/ANM Transfer CPG Send

Switch Name
31996 Contrex Group of Outgoing Group with Special

Prefix
32561 Russian MGTS version
32622 HLR Called Number of Back not query HLR
32634 Alone set Local Office User Call No Answer Timer
32683 Fill Called Bill No. With no Outgoing Group Prefix

After Digit Analysis
32741 SS reject the call for no caller number in MAP add

query SHLR
32805 message waiting indicate(MWI)Service Tone
32812 Billing when pilot notice
32814 CAC Choosing Route
32863 If Terminal 302 of SIP ,The Redirect is CF model

Process
32871 If the Calling Part Hangs up on Listening Dial

Tone,the Call's Statistics Message will not be
Included in the Attempt-Call-Times Statistics and
the User-Hang up-Early Statistics
32872 Common CTX Group Call will not be Collected in

the Destination Number Statistic
32873 North Interface Output File Format Configuration
32876 Traffic Statistics File Name of India With Prefix
32932 Incoming Trunk or Incoming CF Transfer Number

Conversion
32961 Multi-line Selected Number after console on no an-

swer if Dialing Pilot Line
32975 call after if monitor false
33001 SENDONLY mode of hold tone according to 07 Tel-

ecom specification
33023 Encapsulate ISUP and send CPG for HOLD/RE-

TRIEVE
33041 Start Multi-Area Code Process for Very Important

Client System Or Not
33051 Filling the name of trunk to Call Detail Record
33052 To normalizing the TpNo field of Call Detail Record
33053 To fill the "CallDirect " field of CDR specially, set-

ting the type of PRA trunk and R2 trunk to USER

Appendix A Appendix
Switch Name
33152 Fill the actual called number to CDR while dialing

the Centrex indicating line number
70071 Monitor Special Prefix of Length Configuration
70095 SS According Outgoing to Billing
73011 Dialing Tone Configuration of Flash Service
90001 Timed Do not Disturb
90002 Distinctive Ringing
90003 Ring Model
90004 Caller ID Display Mode
90005 Number Stream Identifier when out of SS Centrex

Group
90006 Override New Service Code
90007 Call Delay of Urgent Special Service
90008 CFW And Call Configuration
90009 Authorization Black White List Limit switch
90010 Emergency Special SDN Configuration
90011 Daylight Saving Time Configuration
90012 the Relation of Net Type and CIC
90013 WAC Configuration
90014 High Capacity System
50693 AU tone time unit
50873 Card Null Context Configuration
50874 fax sustaining switch of multi-M
51145 unblock manually by sending unblock message
51161 The Regular Audit Time of Data Area
51332 global trunk group switch
51961 sip call control error code
52703 GPS no respond to alarm
52745 SS Reply err 406 if Non-root SC Version is Differ-

ent to Negotiated Version
52771 Non-SDP Notice Message

Switch Name
52781 ACK is transmitted in the flow of Vast-Nodeid dis-

tribution
52892 Registration Call Control Error Code
52992 SS Returns Error 505 for the Request of Non-In-

Service MG
53121 controlled approach of After registration
80073 The principle of the mapping between Max for-

wards and Hop counter in MGCF
80093 Wimax Roam Call Restriction
80094 Limit to Register Error Code After Wimax Roam

Figures
Figure 1 Fault Management Interface .................................... 2

Figure 2 CURRENT ALARM QUERY ......................................... 2
Figure 3 Detailed Information .............................................. 3
Figure 4 Maintenance Suggestion.......................................... 4
Figure 5 Rack Diagram ........................................................ 5
Figure 6 LEGEND ................................................................ 6
Figure 7 Board detailed Information ...................................... 7
Figure 8 Current Alarms ...................................................... 8
Figure 9 Forward ................................................................ 8
Figure 10 Current Alarms .................................................... 9
Figure 11 Save..................................................................10
Figure 12 Current Alarm Query Conditions ............................11
Figure 13 Query Condition Setup .........................................12
Figure 14 Confirm..............................................................13
Figure 15 History Alarm Query Conditions .............................14
Figure 16 Query Condition Setup .........................................15
Figure 17 Notification Query Conditions ................................17
Figure 18 Query Condition of Notification ..............................18
Figure 19 Event Query Conditions ........................................19
Figure 20 Query Condition of Event dialog box.......................20
Figure 21 Management Rule Setting .....................................22
Figure 22 New...................................................................23
Figure 23 Alarm Delaying Rule ............................................24
Figure 25 New...................................................................26
Figure 26 Alarm Acknowledging Rule ....................................27
Figure 28 New...................................................................29
Figure 29 Alarm User Filtering Rule ......................................30
Figure 30 Alarm User Filtering Rule ......................................31
Figure 31 Delete Filtering Rule ............................................31
Figure 32 Maintenance Suggestion Setting ............................32
Figure 33 Maintenance Suggestion I.....................................33
Figure 34 Maintenance Suggestion II....................................34

Figure 35 Severity Regrade Setting ......................................35

Figure 36 Preferences ........................................................36
Figure 38 Alarm Color Setup ...............................................39
Figure 39 Realtime Alarm Monitor ........................................40
Figure 40 COUNT DIALOG BOX ............................................41
Figure 41 CUSTOMIZE DISPLAY COLUMNS DIALOG BOX .........42
Figure 42 Alarm Sound Setup..............................................43
Figure 43 REALTIME NOTIFICATIONS WINDOW......................44
Figure 44 Realtime Event Monitor Window.............................45
Figure 45 Alarm Synchronization .........................................46
Figure 46 SPECIFYING LOCATION IN ALARM SYNCHRONIZA-
TION DIALOG BOX ............................................47
Figure 47 Report Management.............................................48
Figure 48 SPECIFYING HISTORICAL ALARM STATISTICS
DIALOG BOX .....................................................49
Figure 50 Forward Template Setup .......................................51
Figure 51 SIGNALING TRACE INTERFACE ..............................55
Figure 52 CONFIG CONDITION DIALOG BOX .........................56
Figure 53 TRACE CONDITION DIALOG BOX ...........................56
Figure 54 SPECIFYING CONDITIONS FOR TRACING ................57
Figure 55 TRACE CONDITION OPTION ..................................57
Figure 56 Trace By Node.....................................................58
Figure 57 Trace By Domain Name ........................................59
Figure 58 Trace By IPv4 Address..........................................60
Figure 59 Filter By Error Type..............................................61
Figure 60 CONDITIONS SET BY USER ...................................62
Figure 61 TRACE CONDITION COLLECTION ...........................63
Figure 64 Trace By Number.................................................66
Figure 69 Trace By Trunk ....................................................71

Figures

Figure 74 Information ........................................................76
Figure 75 Trace By H248 Subscriber .....................................77
Figure 80 Trace By Trunk Group No ......................................82
Figure 85 Information ........................................................87
Figure 86 Trace Condition ...................................................87
Figure 87 Trace By Module ..................................................88
Figure 88 Filter Error Type ..................................................89
Figure 92 CONFIG CONDITION DIALOG BOX ....................... 101
Figure 93 Tool Bar Status ................................................. 102
Figure 94 Tracing Result ................................................... 103
Figure 95 Detailed Data.................................................... 104
Figure 96 SCTP Tracing Result ........................................... 105
Figure 97 NSI encoding .................................................... 105
Figure 98 Config M3UA version .......................................... 106
Figure 99 SCCP Tracing Result ........................................... 106
Figure 100 SS7UP Detail Code........................................... 107
Figure 101 Tool bar of Successful Cancelling ....................... 107
Figure 102 Save as Text File.............................................. 108
Figure 103 Save .............................................................. 109
Figure 104 Tracing Result Saved in Form of Text File............. 109
Figure 105 Open ............................................................. 110
Figure 106 Error .............................................................. 110
Figure 107 File Name Suffix Filter ...................................... 111
Figure 108 SYSTEM DETECT.............................................. 115
Figure 109 Ping External Node .......................................... 116
Figure 110 Ping Internal Module ........................................ 117
Figure 111 NIC Statistics .................................................. 118
Figure 112 CHECKING TRUNK GROUP STATUS ..................... 120

Figure 113 CHECKING SCTP LINK STATUS .......................... 121

Figure 114 Detecting H248 ............................................... 122
Figure 115 QUERYING BOARD MEMORY USAGE ................... 123
Figure 116 Querying Basic Information On Board ................. 124
Figure 117 Querying Net Flow On Board ............................. 125
Figure 118 Querying Route Information On Board ................ 126
Figure 119 Querying Disk Information On SC ...................... 127
Figure 120 Querying Detail On SSN.................................... 128
Figure 121 Querying Detail On SSN.................................... 129
Figure 122 Detecting Table Space ...................................... 131
Figure 123 Detecting Table Space ...................................... 132
Figure 124 Detecting Procedure......................................... 133
Figure 125 Detecting Table Capacity................................... 134
Figure 126 Viewing CPU & Memory .................................... 135
Figure 127 Viewing Trunk Circuits ...................................... 136
Figure 128 SS resource report........................................... 137
Figure 129 Save .............................................................. 138
Figure 130 Viewing Resource Report .................................. 139
Figure 131 Viewing Board Test .......................................... 140
Figure 132 Routine Test.................................................... 141
Figure 133 Routine Test I.................................................. 142
Figure 134 KD FLAG CONFIGURATION ................................ 144
Figure 135 KB FLAG CONFIGURATION ................................ 146
Figure 136 ICP FLAG CONFIGURATION ............................... 148
Figure 137 NAMED TIMER CONFIGURATION ........................ 150
Figure 138 MODIFY NAMED TIMER DIALOG BOX .................. 150
Figure 139 CONFIGURE SNMP OAM CONSOLE ..................... 151
Figure 140 GLOBAL SERVICE DATA .................................... 153
Figure 141 MODIFY CALL DELAY OF URGENT SPECIAL
SERVICE ........................................................ 154
Figure 142 SERVICE CONFLICT DIALOG BOX....................... 155
Figure 143 MODIFY SERVICE CONFLICT DIALOG BOX........... 156

Tables
Table 1 Chapter Summary .................................................... i

Table 2 PARAMETERS IN QUERY CONDITION OF CURRENT
ALARM DIALOG BOX ..........................................12
Table 3 PARAMETERS IN QUERY CONDITION OF HISTORY
ALARM DIALOG BOX ..........................................15
Table 4 PARAMETERS IN QUERY CONDITION OF Notification
DIALOG BOX .....................................................18
Table 5 PARAMETERS IN QUERY CONDITION OF Event
DIALOG BOX .....................................................20
Table 6 PARAMETERS IN SOUND AND COLOR SETTING
DIALOG BOX ....................................................37
Table 7 TOOLBAR BUTTONS DESCRIPTION IN REALTIME
ALARMS WINDOW ............................................40
ALARM DIALOG BOX ..........................................62
ALARM DIALOG BOX ..........................................67
ALARM DIALOG BOX ..........................................72
ALARM DIALOG BOX ..........................................78
ALARM DIALOG BOX ..........................................83
ALARM DIALOG BOX ..........................................90
Table 14 Protocol Trace Condition Setting..............................93
Table 15 Business Trace Condition Setting .............................99
Table 16 KD OPERATION GUIDE......................................... 144
Table 17 SUMMARY OF PARAMETERS FOR KD FLAG
CONFIGURATION WINDOW .............................. 145
Table 18 KB OPERATION GUIDE ......................................... 146
Table 19 SUMMARY OF PARAMETERS FOR KB FLAG
CONFIGURATION ............................................. 147
Table 20 ICP OPERATION GUIDE ........................................ 148

Table 21 SUMMARY OF PARAMETERS FOR ICP FLAG

CONFIGURATION ............................................. 149
Table 22 SUMMARY OF PARAMETERS FOR NAMED TIMER ...... 150
Table 23 OAM CONSOLE OPERATION GUIDE ........................ 152
Table 24 SUMMARY OF PARAMETERS FOR SNMP OAM
CONSOLE ....................................................... 152
Table 25 SUMMARY OF PARAMETERS FOR CALL DELAY OF
URGENT SPECIAL SERVICE ............................... 154

sjzl20092701 OperationGuide - SystemMaintenance

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

sjzl20092701 OperationGuide - SystemMaintenance

Uploaded by

Copyright:

Available Formats

ZXSS10 SS1b

SoftSwitch Control Equipment

Copyright © 2006 ZTE CORPORATION.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision No. Revision Date Revision Reason

Serial Number: sjzl20092701

About This Manual.............................................. i

Chapter 1,Alarm This chapter describes the procedure to

Related The following documentation is related to this manual:

Confidential and Proprietary Information of ZTE CORPORATION i

This page is intentionally blank.

ii Confidential and Proprietary Information of ZTE CORPORATION

Querying Current Alarms

Confidential and Proprietary Information of ZTE CORPORATION 1

FIGURE 1 FAULT MANAGEMENT INTERFACE

� Select Query > View Current Alarms from menu bar or

FIGURE 2 CURRENT ALARM QUERY

2. View specific detailed information of alarms.

2 Confidential and Proprietary Information of ZTE CORPORATION

Double click an alarm record inFigure 2 window to view spe-

FIGURE 3 DETAILED INFORMATION

Confidential and Proprietary Information of ZTE CORPORATION 3

FIGURE 4 MAINTENANCE SUGGESTION

Result Querying current alarms is completed successfully.

Viewing Rack Diagram Alarms

4 Confidential and Proprietary Information of ZTE CORPORATION

FIGURE 5 RACK DIAGRAM

2. Click the Legend button on the toolbar to open Legend

Confidential and Proprietary Information of ZTE CORPORATION 5

There is a little color button in every board and different color

6 Confidential and Proprietary Information of ZTE CORPORATION

FIGURE 7 BOARD DETAILED INFORMATION

Result Viewing rack diagrams alarms is completed successfully.

Forwarding Current Alarms Manually

Confidential and Proprietary Information of ZTE CORPORATION 7

FIGURE 8 CURRENT ALARMS

2. Forward alarm manually.

8 Confidential and Proprietary Information of ZTE CORPORATION

3. Fill in Email Address or Phone number or click the Select...

Result Forwarding current alarms manually is completed successfully.

Saving Current Alarm List

FIGURE 10 CURRENT ALARMS

2. Save current alarm list.

Click the button, and Save dialog box pops up as shown in

Confidential and Proprietary Information of ZTE CORPORATION 9

Result Saving current alarm list is completed successfully.

Setting Current Alarm Query

10 Confidential and Proprietary Information of ZTE CORPORATION

FIGURE 12 CURRENT ALARM QUERY CONDITIONS

2. Click the button in toolbar.

Confidential and Proprietary Information of ZTE CORPORATION 11

FIGURE 13 QUERY CONDITION SETUP

Table 2 shows description of parameters in the dialog box.

TABLE 2 PARAMETERS IN QUERY CONDITION OF CURRENT

System Type Select ZXSS10 SS1, select server node and

Severity Confirm alarm severity. If severity is not

Alarm Description Specify alarm description. It is optional

Probable Cause Specify probable cause for alarm. It is

Happen Time Specify the time interval which alarms

Acknowledgment Specify alarm status. It is optional

12 Confidential and Proprietary Information of ZTE CORPORATION

(Un)acknowledge Specify acknowledge operator. It is optional

(Un)acknowledging Specify acknowledge time. It is optional