ZXSS10 SS1b

SoftSwitch Control Equipment

Network Diagnose Operation Guide
Version 2.0.1.05.2
ZTE CORPORATION
ZTE Plaza, Keji Road South,
Hi-Tech Industrial Park,
Nanshan District, Shenzhen,
P. R. China
518057
Tel: (86) 755 26771900 800-9830-9830
Fax: (86) 755 26772236
URL: http://support.zte.com.cn
E-mail: doc@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 CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.

This document is provided as is, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.

The contents of this document and all policies of ZTE CORPORATION, including without limitation policies related to
support or training are subject to change without notice.

Revision History
Date Revision No. Serial No. Reason for Revision
Feb. 18, 2008 R1.0 sjzl20073811 First edition

ZTE CORPORATION
Values Your Comments & Suggestions!
Your opinion is of great value and will help us improve the quality of our product
documentation and offer better services to our customers.
Please fax to: (86) 755-26772236; or mail to Documentation R&D Department,
ZTE CORPORATION, ZTE Plaza, A Wing, Keji Road South, Hi-Tech Industrial Park,
Shenzhen, P. R. China 518057.
Thank you for your cooperation!
Document
Name
ZXSS10 SS1b SoftSwitch Control Equipment Network Diagnose Operation Guide
Product Version V2.0.1.05.2
Document Revision
Number
R1.0
Equipment Installation Date
Presentation:
(Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization,
Appearance)
Good Fair Average Poor Bad N/A
Accessibility:
(Contents, Index, Headings, Numbering, Glossary)
Good Fair Average Poor Bad N/A
Your evaluation
of this
documentation
I ntelligibility:
(Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)
Good Fair Average Poor Bad N/A
Your
suggestions for
improvement of
this
documentation
Please check the suggestions which you feel can improve this documentation:
Improve the overview/introduction Make it more concise/brief
Improve the Contents Add more step-by-step procedures/tutorials
Improve the organization Add more troubleshooting information
Include more figures Make it less technical
Add more examples Add more/better quick reference aids
Add more detail Improve the index
Other suggestions
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
# Please feel free to write any comments on an attached sheet.
If you wish to be contacted regarding your comments, please complete the following:
Name Company
Postcode Address
Telephone E-mail
This page is intentionally blank.

Contents

About This Manual ............................................................ i
Purpose................................................................................ i
Intended Audience ................................................................. i
Prerequisite Skill and Knowledge.............................................. i
What Is in This Manual ........................................................... i
Related Documentation.......................................................... ii
Conventions......................................................................... ii
How to Get in Touch............................................................. iii
Chapter 1.......................................................................... v
Network Diagnostic Test ................................................. 1
Overview............................................................................. 1
Checking Board Attributes...................................................... 1
Checking Network................................................................. 3
Checking Protocol ................................................................. 4
Querying System Information................................................. 5
Checking Protocol Data.......................................................... 6
Checking CPU and Memory Performance................................... 7
Checking Trunk Circuits ......................................................... 8
SS Resource Report .............................................................. 9
Testing Board..................................................................... 11
Viewing Routine Test ........................................................... 13
Appendix A..................................................................... 15
Abbreviation....................................................................... 15
Index.............................................................................. 19
Glossary.......................................................................... 21
This page is intentionally blank.



About This Manual

Purpose
This manual provides procedures and guidelines that support the
operation of the ZXSS10 SS1b SoftSwitch Control Equipment.
Intended Audience
This document is intended for engineers and technicians who
perform operation activities on the ZXSS10 SS1b SoftSwitch
Control Equipment.
Prerequisite Skill and Knowledge
To use this document effectively, users should have a general
understanding of wireless telecommunications technology.
Familiarity with the following is helpful:
ZXSS10 SS1b SoftSwitch Control Equipment and its various
components
User interfaces and ZXSS10 SS1b SoftSwitch Control
Equipment Data Configuration
Local operating procedures
What Is in This Manual
This manual contains the following chapters:
TAB L E 1 - CHAPTER SUMMARY
Chapter Summary
Chapter 1, Network
Diagnostic Test
This chapter describes the procedure to
diagnose system boards, network,
protocols, information querying, data
memory, running performance and
resource usage.
Confidential and Proprietary Information of ZTE CORPORATION i

ZXSS10 SS1b SoftSwitch Control Equipment Network Diagnose Operation Guide

Related Documentation
The following documentation is related to this manual:
ZXSS10 SS1b SoftSwitch Control Equipment Product
Description
ZXSS10 SS1b SoftSwitch Control Equipment Hardware
Manual
ZXSS10 SS1b SoftSwitch Control Equipment Software
Installation Manual
ZXSS10 SS1b SoftSwitch Control Equipment Hardware
Installation Manual
ZXSS10 SS1b SoftSwitch Control Equipment Routine
Maintenance Manual
Conventions
ZTE documents employ the following typographical conventions. Typographical
Conventions
TAB L E 2 - TYPOGRAPHI CAL CONVENTI ONS
Typeface Meaning
Italics References to other Manuals and documents.
Quotes Links on screens.
Bold Menus, menu options, function names, input
fields, radio button names, check boxes, drop-
down lists, dialog box names, window names.
CAPS Keys on the keyboard and buttons on screens
and company name.
Const ant wi dt h
Text that you type, program code, files and
directory names, and function names.
[ ] Optional parameters.
{ } Mandatory parameters.
| Select one of the parameters that are delimited
by it.
Note: Provides additional information about a
certain topic.
Checkpoint: Indicates that a particular step needs
to be checked before proceeding further.
Tip: Indicates a suggestion or hint to make things
easier or more productive for the reader.

ii Confidential and Proprietary Information of ZTE CORPORATION



About This Manual

TAB L E 3 - MOUSE OPERATI ON CONVENTI ONS
Typeface
Mouse
Operation
Conventions
Meaning
Click Refers to clicking the primary mouse button (usually
the left mouse button) once.
Double-click Refers to quickly clicking the primary mouse button
(usually the left mouse button) twice.
Right-click Refers to clicking the secondary mouse button
(usually the right mouse button) once.
Drag Refers to pressing and holding a mouse button and
moving the mouse.
How to Get in Touch
The following sections provide information on how to obtain
support for the documentation and the software.
If you have problems, questions, comments, or suggestions
regarding your product, contact us by e-mail at
support@zte.com.cn. You can also call our customer support
center at (86) 755 26771900 and (86) 800-9830-9830.
Customer
Support
ZTE welcomes your comments and suggestions on the quality
and usefulness of this document. For further questions,
comments, or suggestions on the documentation, you can
contact us by e-mail at doc@zte.com.cn; or you can fax your
comments and suggestions to (86) 755 26772236. You can also
browse our website at http://support.zte.com.cn, which contains
various interesting subjects like documentation, knowledge
base, forum and service request.
Documentation
Support

Confidential and Proprietary Information of ZTE CORPORATION iii

ZXSS10 SS1b SoftSwitch Control Equipment Network Diagnose Operation Guide


This page is intentionally blank.

iv Confidential and Proprietary Information of ZTE CORPORATION


Declaration of RoHS
Compliance

To minimize the environmental impact and take more
responsibility to the earth we live, this document shall serve as
formal declaration that the ZXSS10 SS1b Softswitch Control
Equipment manufactured by ZTE CORPORATION are in
compliance with the Directive 2002/95/EC of the European
Parliament - RoHS (Restriction of Hazardous Substances) with
respect to the following substances:
Lead (Pb)
Mercury (Hg)
Cadmium (Cd)
Hexavalent Chromium (Cr (VI))
PolyBrominated Biphenyls (PBBs)
PolyBrominated Diphenyl Ethers (PBDEs)

The ZXSS10 SS1b Softswitch Control Equipment manufactured
by ZTE CORPORATION meet the requirements of EU
2002/95/EC; however, some assemblies are customized to client
specifications. Addition of specialized, customer-specified
materials or processes which do not meet the requirements of
EU 2002/95/EC may negate RoHS compliance of the assembly.
To guarantee compliance of the assembly, the need for
compliant product must be communicated to ZTE CORPORATION
in written form.
This declaration is issued based on our current level of
knowledge. Since conditions of use are outside our control, ZTE
CORPORATION makes no warranties, express or implied, and
assumes no liability in connection with the use of this
information.

Confidential and Proprietary Information of ZTE CORPORATION v

ZXSS10 SS1b SoftSwitch Control Equipment Network Diagnose Operation Guide


This page is intentionally blank.

vi Confidential and Proprietary Information of ZTE CORPORATION


Ch a p t e r 1
Network Diagnostic Test

Overview
This chapter describes the procedure to diagnose system boards,
network, protocols and resource usage.
Purpose
This chapter includes following topics:
Topic
Contents
Index
Checking Board Attributes 1
Checking Network 3
Checking Protocol 4
Querying System Information 5
Checking Protocol Data 6
Checking CPU and Memory 7
Checking Trunk Circuits 8
SS Resource Report 9
Testing Board 11
Viewing Routine Test 13
Checking Board Attributes
This topic checks the physical status and running status of all
the boards in the SS shelf. It includes following checks:
Purpose
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
Confidential and Proprietary Information of ZTE CORPORATION 1

ZXSS10 SS1b SoftSwitch Control Equipment Network Diagnose Operation Guide

Connection between the boards
Preparations Before proceeding, meet the following requirements.
NetNumen Server is properly insalled, configured and
connected with SUN platform.
NetNumen client is available.
NetNumenN31 ZTE Unified Management System
window is open.
Procedure
To check board attributes, perform the following steps.
1. In the topology management interface, right-click an SS and
select the Diagnostic Management menu item from the
pop up menu or select Views > Diagnostic Management
from the main menu.
2. In the Diagnose Management window displayed, select
Instant Test > System Detect.
3. Select the shelf No. to be checked and click Detect. Add to
routine test means adding the system test to the routine
test task list.
Result: SS1b boards information is displayed in the bottom
window, as shown in Figure 1.
FI GURE 1 SYSTEM DETECT

END OF STEPS
2 Confidential and Proprietary Information of ZTE CORPORATION



Chapter 1 Network Diagnostic Test

Checking Network
This topic checks the network connection status. Purpose
Preparations Before proceeding, meet the following requirements.
NetNumen Server is properly insalled, configured and
connected with SUN platform.
NetNumen client is available.
NetNumenN31 ZTE Unified Management System
window is open.
To check the network, perform the following steps. Procedure
1. In the Diagnose Management window, select Instant
Test > Net Detect.
2. Select Ping External Node or Ping Internal Module, or NIC
Statistics according to actual situation.
3. Select the module and enter related information.
4. Click on Detect button
Result: The test result is displayed in the output area. Figure
2 shows an example of pinging external node.
FI GURE 2 NETWORK TEST

END OF STEPS

Confidential and Proprietary Information of ZTE CORPORATION 3

ZXSS10 SS1b SoftSwitch Control Equipment Network Diagnose Operation Guide

Checking Protocol
This topic describes procedure to check the protocol processing
status of trunks, SCTP link and H.248.
Purpose
Before proceeding, meet the following requirements. Preparations
NetNumen Server is properly insalled, configured and
connected with SUN platform.
NetNumen client is available.
NetNumenN31 ZTE Unified Management System window is
open.
Procedure To check the protocol status, perform the following steps.
1. In the Diagnose Management window, select Instant
Test > Protocol Detect.
2. Select Detect Trunk, Detect SCTPL Connection, or Detect
Gateway H.248 according to actual situation.
3. If you select Detect Trunk, enter the trunk group No.
If you select Detect SCTPL Connection, select the module
No. and enter the node ID.
If you select Detect Gateway H.248, select the module No.
(No. of the module processing the H248 board) and enter the
destination gateway ID.
4. Click on Detect button.
Result: The test result will be displayed in the output area.
Figure 3 shows the check of trunk group status.
FI GURE 3 CHECK I NG TRUNK GROUP STATUS

4 Confidential and Proprietary Information of ZTE CORPORATION



Chapter 1 Network Diagnostic Test

END OF STEPS
Querying System Information
This topic describes procedure to query the memory usage,
basic board information, traffic flow, routing metrics, SC disk
information, and port information of NIC, SSN, SPC, and SC
modules.
Purpose
Preparations Before proceeding, meet the following requirements.
NetNumen Server is properly insalled, configured and
connected with SUN platform.
NetNumen client is available.
NetNumenN31 ZTE Unified Management System
window is open.
To query system perform the following steps. Procedure
1. In the Diagnose Management window, select Instant
Test > Info Enquire.
2. Select the item to be enquired from the drop-down text box.
The query items include:
i. Memory usage on board
ii. Basic information of a board
iii. Network port traffic of a board
iv. Route information of a board
v. SC hard disk information
vi. Detailed information of the ports on the SSN
3. Select the module (NIC, SSN, SPC, and SC) to be queried.
4. Click the Inquire button.
Result: The query results are displayed. Figure 4 shows an
example of the check on board memory usage.
Confidential and Proprietary Information of ZTE CORPORATION 5

ZXSS10 SS1b SoftSwitch Control Equipment Network Diagnose Operation Guide

FI GURE 4 QUERYI NG BOARD MEMORY USAGE

END OF STEPS
Checking Protocol Data
Purpose This topic describes procedure to check the data area queue and
table capacity of every protocol assigned to every zone on SC
and SPC boards.
Before proceeding, meet the following requirements. Preparations
NetNumen Server is properly insalled, configured and
connected with SUN platform.
NetNumen client is available.
NetNumenN31 ZTE Unified Management System window is
open.
Procedure To check protocol data, perform the following steps.
1. In the Diagnose Management window, select Instant Test >
Data Detect.
2. Select the item to be checked. The items to be checked
include:
Detect Data Area Queue
Detect Table Space
Detect Storage Process
Detect Data Table Capacity
6 Confidential and Proprietary Information of ZTE CORPORATION



Chapter 1 Network Diagnostic Test

3. Click Detect.
Result: Data is displayed, as shown in Figure 5.
FI GURE 5 CHECK I NG THE DATA AREA QUEUE OF DESTI NATI ON BOARD

END OF STEPS
Checking CPU and Memory
Performance
This topic describes the procedure to check CPU and memory
usage of the system.
Purpose
Before proceeding, meet the following requirements. Preparations
NetNumen Server is properly insalled, configured and
connected with SUN platform.
NetNumen client is available.
NetNumenN31 ZTE Unified Management System
window is open.
Procedure To check the CPU and memory usage, perform the following
steps.
1. In the Diagnose Management window, select Instant
Test > Performance View > View CPU & Memory.
2. Select the module No. of the board to be checked. Set the
time interval for the sampling data (it cannot be shorter than
0.1 second).
3. Click Begin.
Confidential and Proprietary Information of ZTE CORPORATION 7

ZXSS10 SS1b SoftSwitch Control Equipment Network Diagnose Operation Guide

Result: The CPU and memory occupation will be displayed,
as shown in Figure 6.
FI GURE 6 OB SERVI NG CPU AND MEMORY USAGE

END OF STEPS
Checking Trunk Circuits
This topic describes procedure to check the status of trunk
circuits.
Purpose
Before proceeding, meet the following requirements. Preparations
NetNumen Server is properly insalled, configured and
connected with SUN platform.
NetNumen client is available.
NetNumenN31 ZTE Unified Management System
window is open.
To check trunk circuits, perform the following steps. Procedure
1. In the Diagnose Management window, select Instant
Test > Performance View > View Trunk Circuits.
2. Enter the trunk group No. and set the time interval for data
sampling (it cannot be shorter than 5 seconds).
3. Select the content to be observed, busy trunk, idle trunk or
blocked trunk.
4. Click Begin button.
Result: The trail of trunk circuits will be displayed, as shown
in Figure 7.
8 Confidential and Proprietary Information of ZTE CORPORATION



Chapter 1 Network Diagnostic Test

FI GURE 7 OB SERVI NG TRUNK CI RCUI TS

5. Click Stop button to stop trunk ovser
END OF STEPS
SS Resource Report
This topic reports analysis of the following SS resources. Purpose
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
Before proceeding, meet the following requirements. Preparations
NetNumen Server is properly insalled, configured and
connected with SUN platform.
NetNumen client is available.
NetNumenN31 ZTE Unified Management System
window is open.
To report SS resource, perform the following steps. Procedure
1. In the topology management interface, right-click an SS and
select the Diagnostic Test menu. In the Diagnose
Management window, select Instant Test > SS resource
report.
Confidential and Proprietary Information of ZTE CORPORATION 9

ZXSS10 SS1b SoftSwitch Control Equipment Network Diagnose Operation Guide

2. Select the SS resource report item and click Detect. The
Save dialog box is displayed, as shown in Figure 8.
FI GURE 8 SAVI NG REPORT AS A FI L E

3. Specify the destination folder and click Save.
4. The resource report is displayed, as shown in Figure 9.
FI GURE 9 SS RESOURCE REPORT GENERATED

END OF STEPS
10 Confidential and Proprietary Information of ZTE CORPORATION



Chapter 1 Network Diagnostic Test

Testing Board
This topic reports analysis of board test. Purpose
Preparations Before proceeding, meet the following requirements.
NetNumen Server is properly insalled, configured and
connected with SUN platform.
NetNumen client is available.
NetNumenN31 ZTE Unified Management System
window is open.
To test board, perform the following steps. Procedure
1. In the topology management interface, right-click an SS and
select the Diagnostic Test menu. In the Diagnose
Management window, select Instant Test > Board Test.
2. Select the board item needed to be test in the Select Test
Plane as shown in Figure 10.
FI GURE 10 SEL ECT B OARDS FOR TEST

3. Click in the black circle of Board Test interface as shown
in Figure 11.
Confidential and Proprietary Information of ZTE CORPORATION 11

ZXSS10 SS1b SoftSwitch Control Equipment Network Diagnose Operation Guide

FI GURE 11 SPREADI NG THE BOARD L I ST PL ANE OF SEL ECT TEST

5. click Test button in Figure 11, and click button to show
the result of testing boards displayed in .
FI GURE 12 BOARD TESTI NG RESUL T

END OF STEPS
12 Confidential and Proprietary Information of ZTE CORPORATION



Chapter 1 Network Diagnostic Test

Viewing Routine Test
This topic reports configuration parameters and testing result of
routine test. The function of routine test is to test the diagnose
item which is configured by operator in the fixed time interval.
Purpose
Preparations Before proceeding, meet the following requirements.
NetNumen Server is properly insalled, configured and
connected with SUN platform.
NetNumen client is available.
NetNumenN31 ZTE Unified Management System
window is open.
Click Add to routine test button in testing item window of
Instant Test interface.
To test board, perform the following steps. Procedure
1. In the topology management interface, right-click an SS and
select the Diagnostic Test menu. In the Diagnose
Management window, select Routine Test as shown in
Figure 13.
FI GURE 13 ROUTI NE TEST I NTERFACE

2. Configure the routine testing time below the Routine Test
Task Management window, and click Set task button in
the black circle of Board Test interface in Figure 11.
Result: The task is displayed in the list as shown in Figure
14.
Confidential and Proprietary Information of ZTE CORPORATION 13

ZXSS10 SS1b SoftSwitch Control Equipment Network Diagnose Operation Guide

FI GURE 14 ROUTI NE TEST L I ST

3. The test results will be displayed in the test results list by
fixed interval.
END OF STEPS

14 Confidential and Proprietary Information of ZTE CORPORATION


A p p e n d i x A
Abbreviation
Abbreviation Full Spelling
AAA Authentication/Authorization/Accounting
AG Access Gateway
AS Application Server
ASP Application Server Process
Customized Applications for Mobile Network
Enhanced Logic
CAMEL
CAP CAMEL Application Part
CIC Circuit Identification Code
CLI Command Line Interface
CLIT Command Line Interface Terminal
CLITT Command Line Interface Terminal for Telnet
CS Call Server
DPC Destination Point Code
DSS1 Digital Subscriber Signaling System No.1
DTMF Dual Tone Multi-Frequency
GK GateKeeper
GTT Global Title Translation
GUI Graphic User Interface
GW Gateway
HLR Home Location Register
IAD Integrated Access Device
IAM Initial Address Message
IETF Internet Engineering Task Force
IN Intelligent Network
INAP Intelligent Network Application Protocol
IP Internet Protocol
ISDN Integrated Service Digital Network
ISUP ISDN User Part
International Telecom Union-Telecommunication
standardization
ITU-T
LATA Local Access and Transport
LSQ Logical SQuence
M2PA MPT2 Peer-to-Peer Adapter
M2UA MTP2 User Adapter
Confidential and Proprietary Information of ZTE CORPORATION 15

ZXSS10 SS1b SoftSwitch Control Equipment Network Diagnose Operation Guide

Abbreviation Full Spelling
M3UA MTP3-User Adaptation Layer
MAP Mobile Application Part
MEGACO MEdia GAteway Controller
MFC Multi-Frequency Control
MG Media gateway
MGC Media Gateway Controller
MGCP Media Gateway Control Protocol
MIB Management Information Base
MMI Man-Machine Interface
MML Man-Machine Language
MTU Maximum Transmission Unit
NAS Network Access Server
NCS Network-based Call Signaling Protocol
NGN Next Generation Network
NIC Network Interface Card
OAM Operation, Administration and Maintenance
OPC Origination Point Code
PBX Private Branch Exchange
PCM Pulse Code Modulation
PSTN Public Switching Telephone Network
QoS Quality of Service
RADIUS Remote Authentication Dial-In User Service
RTCP Real-time Transport Control Protocol
RTP Real-time Transport Protocol
SC System Control
SCCP Signaling Connection Control Part
SCP Service Control Point
SCTP Stream Control Transport Protocol
SEP Signaling End Point
SG Signaling Gateway
SIGTRAN SIGnal TRANsport
SIP Session Initiation Protocol
SIP-T Session Initiation Protocol for Telephony
SNMP Simple Network Management Protocol
SPC System Protocol Card
SS Softswitch
SS7 Signaling System No.7
SS7UP Signaling System No.7 User Part
SSC Softswitch System Control Board
SSN System Switching Network Board
SSNI System Switching Network Interface board
16 Confidential and Proprietary Information of ZTE CORPORATION



Appendix A Abbreviations

Abbreviation Full Spelling
STP Signaling Transfer Point
TCAP Transaction Capability Application Part
TCP/IP Transmission Control Protocol/Internet Protocol
TDM Time Division Multiplexing
TG Trunk Gateway
TID Termination ID
TMN Telecommunication Management Network
TUP Telephone User Part
UDP User Datagram Protocol
URI Uniform Resource Identifier
V5UA V5.2-User Adaptation Layer

Confidential and Proprietary Information of ZTE CORPORATION 17

ZXSS10 SS1b SoftSwitch Control Equipment Network Diagnose Operation Guide


This page is intentionally blank.

18 Confidential and Proprietary Information of ZTE CORPORATION


Index

boar d at t r i but es ................2
net wor k........................ i, 1, 3
node ............................... 3, 4
pr ot ocol ......................... 4, 6
pr ot ocol dat a.....................6
r esour ce r epor t ........... 9, 10
Rout e ................................. 5
t r unk ci r cui t .................... 8
t r unk ci r cui t s ................... 8
t r unk gr oup................ 4, 8, 9
Tr unk Gr oup........................ 4
zone ................................... 6

Confidential and Proprietary Information of ZTE CORPORATION 19

ZXSS10 SS1b SoftSwitch Control Equipment Network Diagnose Operation Guide


This page is intentionally blank.

20 Confidential and Proprietary Information of ZTE CORPORATION


Glossary

Node A node refers to a gateway device in the IP network and
associated with the local SS.
Zone A zone refers to a set of gateway nodes with the same service
features. The capacity of gateways may be relative small, there
may be a number of nodes in the network, and thus it is not
convenient to manage the system. In that case, a zone is
applied. To group gateways to the same zone, comply with the
following principles:
The gateways in the same zone should be of the same device
type.
The gateways in the same zone should be in the same
network.
The capacity of the zone should be suitable rather than being
far large. Therefore, a gateway with a large capacity can be
a separate zone, such as accessing gateway and trunking
gateway; an appropriate number of gateways with a
respectively small capacity can be grouped in the same zone,
such as Itegrated Access Device (IAD).
Control domain SS control domain refers to a domain composed of the local SS
and all devices controlled by the local SS.
LSQ LSQ is a unique logic number assigned by the system to a
processing board. In other data, all should be indicated by the
LSQ. In this way, in case that debugging or any other reason
causes to replace the socket of a board or board, it is enough to
replace the actual board position corresponding to the LSQ.
Number analysis selection is an entry to the number analysis
table. Each number analysis table contains all number analyzers
which are responsible for analyzing call services of the same
subscriber. A number analyzer is a set of analyzed numbers with
the same properties. Number analysis selection should be
allocated to every incoming (bi-directional) trunk group, calling
party, and other SS respectively. In addition, a new number
analysis selection should be allocated if a second analysis is
required after the first number analysis has been carried out.
Number
analysis
Selection
A number analyzer refers to a set of analyzed numbers with the
same properties. The system provides following types of number
analyzers:
Number
analyzer
New Service Number Analyzer
Centrex Number Analyzer
Confidential and Proprietary Information of ZTE CORPORATION 21


ZXSS10 SS1b SoftSwitch Control Equipment Network Diagnose Operation Guide

Private Network Number Analyzer
Special Service Number Analysis
Private Number Analyzers
Local Network Number Analyzer
Domestic Toll Number Analyzer
International Toll Number Analyzer
During a number analysis process, the preceding number
analyzers, if installed, are browsed through in the preceding
order until the desired number is found.
DDI refers to a particular conversion of the stream of a specified
calling or called number for the purpose of achieving number
change as well as reflecting the nature of the call and the class
of the call. DDI is applicable to three cases.
DDI
The first case is to perform number change after the number
stream comes into the local office while before the number
analysis is carried out.
The second case is to perform DDI after an appropriate outgoing
trunk group is selected while before codes are transmitted. In
these two cases, such a change is conducted on both incoming
and outgoing number streams through a particular route
configured with DDI.
The third case is to perform DDI after the number analysis is
completed. The third case is applicable to the change of single
numbers.
The former two cases are applicable to the conversion of all
number streams through the same trunk or route.
There are four methods of number change,
Addition
Deletion
Modification
Invariance
The Offset determines the start position of a DDI. The Size
determines the length to be deleted or modified. When it is
necessary to configure a DDI on a graphical database interface,
the system marks the exact start position of DDI, the length of
changed number, the change method, and the type of new
number. Summary of DDIs is given in Table 4.
TAB L E 4 DDI METHODS
DDI Method Offset Size DN
1 1 (Addition) 1 0 25
2 2 (Deletion) 1 3
3 3 (Modification) 1 3 462
22 Confidential and Proprietary Information of ZTE CORPORATION



Glossary
DDI Method Offset Size DN
4 4 (Invariance) 0 0 300
DDI 1 indicates to add 25 before the first digit of the
number stream.
DDI 2 indicates to delete the first three digits.
DDI 3 indicates to modify the first three digits of the
number stream to 462.
DDI 4 indicates to change the number stream to 300.
The purpose of route chain group is to share traffic among
several adjacent switches according to a certain percentage. For
example, 60 percent of outgoing calls shall be transited through
the switch A, and the 40 percent of outgoing calls shall be
transited through the switch B. Accordingly, the route chains
towards the switch A by all the route chains in the same route
chain group is 60 percent, and the route chains towards the
switch B is 40 percent. In this way, traffic can be transported
according to a particular percentage. Each route chain group
contains a maximum of 12 route chains. The route chain
selection number and chain number, determines a suitable route
chain to be applied currently in a cyclic manner. The system will
not automatically turn to another route chain if no trunks in the
previous route chain are available. Therefore, it is necessary to
make sure each route chain has all possible paths when you are
configuring data.
Route Chain
Group
A route chain refers to the set of all paths available for an
outgoing destination code. Route chains are numbered by the
system uniquely and globally. Each route chain contains 12
route groups in a sequence order. For each selection, only the
first route group is used basically. The following route groups will
be used in the order only if no appropriate paths are found from
the previous route group.
Route Chain
Different route chains may be used in different time segments.
The selection period is a week. There are a maximum of three
time segments in each day. In this way, there are 21 choices at
most.
Dynamic Route
Chain
A route set refers to a set of routes at the same level. Each
route set contains a maximum of 12 routes. Route numbers can
be repeated to achieve load balance. The routes in the same
route set are selected in a cyclic way. The current route
selection number, RouteNo, determines the route number to be
selected currently.
Route Set
Route A route refers to an outgoing (bi-directional) trunk group or an
identifier of the control domain of other SS. All outgoing routes
are numbered by the system uniquely and globally. The number
range is {1, 2, 65535}.
Traffic balance of route refers to the percentage of the traffic
carried on each route in the same route chain group. Trunk
selection is shown in Figure 15.
Traffic balance
of route
Confidential and Proprietary Information of ZTE CORPORATION 23

ZXSS10 SS1b SoftSwitch Control Equipment Network Diagnose Operation Guide

FI GURE 15 TRAFFI C ROUTI NG
Softswitch
C O 1
C O 2
Trunk group
Route
Route group Route link
T G 2 T G 1
1 2 3
4 5 6
1:1
12:1
12:1
Route link
group
Trunk group
Traffic balance
Dynamic route
link
Time-based routing


If a CO switch office in the circuit switched telecommunication
network has directly associated voice channels to the controlled
devices in the local control domain, the CO switch office is called
an adjacent switch office. Each adjacent switch office is
identified by a unique number, namely OfficeID, which is called
office direction.
Office direction
Trunk circuit group is called trunk group for short. It refers to
a set of circuits with the same circuit attributes between a
particular controlled device and an adjacent switch. (The circuit
attributes include channel transmission features and inter-office
circuit selection conventions.) A trunk group is restricted to the
same trunking gateway. Trunk groups in different trunking
gateways are numbered independently. The system numbers the
trunk groups globally in the range {1, 2, 65535}. The numbers
assigned inside the system correspond to the numbers assigned
inside a trunking gateway one by one. They can be converted
mutually.
Trunk circuit
group
Because a local network may allow number dialing with a
different length currently, all offices are numbered in the local
system in a unified way, which is called NOC. All the local office
telephone numbers pertaining to the same NOC are of the same
length. Telephone numbers pertaining to different NOCs may be
of a different length. An NOC depends on a triplet composed of
net (network type), lata (area code) and code (local office
number). See Table B-2.
NOC
Table B-2 NOC
NOC Net Lata Code CodeSize
1 1 (PSTN) 25 452 7
2 2 (Netcom) 21 436 7
Hundred
number group
A hundred number group refers to the hundred-bit digit and the
thousand-bit digit of subscriber numbers belonging to a
particular office number in the local control domain, that is, the
A and B digits of the subscriber number ABCD. A hundred
number group is used to determine the zone number allocated
to that subscriber number for the purpose of further determining
24 Confidential and Proprietary Information of ZTE CORPORATION



Glossary
a processing board responsible for processing its calls and
protocols.
The call backup scheme adopted in the system is like this: The
calls pertaining to the same zone are taken as a backup unit,
and the calls of each group are backed up in the 1:1 manner.
For example, depending on zone, the call groups A to H come
into being. The calls of each group are dispatched according to
the Call Server board indicated by a black arrow. (The call data
is distributed on the board.) Meanwhile, it is required to back up
the call data to the processing board indicated by a red arrow,
and the board also contains the data of the group. Whenever the
processing board becomes faulty, all calls are transferred to the
backup board. When the active board is recovered, the active
board first fetches the call data from the original backup board.
After the data is fetched successfully, the dispatch board is
notified to switch the calls back. The groups of gateways are
shown in the yellow box. The processing board with the Call
Server is shown in the yellow box. The zone number to be
processed by the processing board is shown in the upper part of
the right box, and the zone number backed up by the processing
board is shown in the lower part of the right box. The logic board
creates a ring chain according to logic number, and
automatically selects a backup processing board based on the
parity of the group number. Backup of processing board is
shown in Figure 16.
Call server
backup chain
FI GURE 16 BACK UP OF PROCESSI NG BOARD
A
B
C
D
E
F
G
H
A/H
B/G
B/C
A/D
D/E
C/F
F/G
E/H
1
2
3
4


Depending on calling subscriber number or incoming trunk
identifier, certain calling parties or incoming calls from a certain
incoming trunk can be prohibited or allowed to go to certain
destination codes. A destination code may be a prefix, national
code, area code, office number, special service number or
subscriber number. The maximum length is 20 digits.
Black and
white lists
Confidential and Proprietary Information of ZTE CORPORATION 25

ZXSS10 SS1b SoftSwitch Control Equipment Network Diagnose Operation Guide

Black and white lists are defined at the calling and called sides
respectively.
Calling side
Black list defines calling numbers or incoming trunk
identifiers from which calls are prohibited. (That is, the
numbers in the list cannot originate calls to destination
codes.)
White list defines calling numbers or incoming trunk
identifiers beyond restriction of the black list at the called
side. (That is, the numbers in the list can originate calls
to the destination codes in the black list at the called
side.)
Called side
Black list defines destination codes to which calls are
prohibited. (That is, other calling numbers cannot
originate calls to the destination codes.)
White list defines destination codes to which the
subscribers in the black list at the calling side are allowed
to originate calls. (That is, the calling numbers in the
black list at the calling side can originate calls to the
destination codes in this list.)
The relationship between black and white lists is shown in Figure
17. Real lines indicate calls are allowed. Dotted lines indicate
calls are prohibited.
FI GURE 17 CAL L REL ATI ONSHI P B ETWEEN BL ACK AND WHI TE L I STS
Blacklist
White list
Other
subscribers
Calling party Called party
Blacklist
White list
Other
subscribers

Unified tone code in a gateway identifies signal tones required
for the variety of services provided by the system. Each unified
tone needs to be configured with service key which indicates the
applicable service type of that unified tone. At present, the
following types of services are available. Table 5 shows service
list and their corresponding keys.
Unified tone
code
TAB L E 5 - SERVI CE L I ST
Tone Code Service
1 Traditional Service
26 Confidential and Proprietary Information of ZTE CORPORATION



Glossary
Tone Code Service
200 ACC_200
300 ACC_300
400 VOT
600 VPN
700 UPT
800 FPH

A termination is a logic entity in a media gateway. A termination
is the source/sink of media or control streams. There are three
types of terminations:
Termination
Subscriber
Trunk
RTP
The media gateway allocates a unique identifier, called
TerminationID, to each termination when the termination is
created. An example of TerminationID is SDN/JIM/8563.
TerminationID allocated by different media gateways is
presented in different formats. A TerminationID in the text
format is composed of 64 bytes. Therefore, internal
TerminationID, called TID, is defined in a unified way inside the
system. The length of a TID is 8 bytes. Among the 8 bytes, the
first byte indicates category; the second byte is reserved; the
third and fourth bytes indicate the node number of the
connected device; the remaining types vary with the category.
For example, TerminationID SDN/JIM/8563 is converted to
TID 4, 0, 0, 1, 0, 2, 54, 88.
TID
Subscriber call authorities include subscriber calling-in and
calling-out authorities and default calling-in and calling-out
authorities, which are applicable to urban calls, rural calls,
national toll calls, international toll calls, high tariff, and SS
control domain. Subscriber call authorities can be managed
dynamically. Each day is divided into three time segments. A
subscriber can enjoy different calling-in and calling-out
authorities in different time segments.
Subscriber call
authority
Subscriber group is a group of subscriber lines. It only refers to
PABX Group (PABXG), multihunting line group (MHLG), and
Centrex group. Each subscriber group is allocated with a global
number which corresponds to a queue number in the module.
Each group has several indicating lines (or pilot lines). The
indicating lines for PBX and Centrex can be set to be bi-
directional or uni-directional. The indicating lines for MHLG are in
the incoming direction usually; they can also be transferred out.
The multihunting function of indicating lines adopts either first-
in-first-out (queue mode) or fixed sequence.
Subscriber
group
Centrex group
Confidential and Proprietary Information of ZTE CORPORATION 27

ZXSS10 SS1b SoftSwitch Control Equipment Network Diagnose Operation Guide

A Centrex group is also called business group. It refers to a
group of related subscribers, for example, in the same enterprise
or company. A dedicated PABX is unnecessarily required. The
group of subscribers is defined logically to implement a Centrex
group. Therefore, the subscribers in a Centrex group can enjoy
both the service functions provided for local network subscribers
and certain service functions unique to Centrex groups. The
subscribers in a Centrex group are numbered in a special way.
Each subscriber is allocated with an ordinary telephone number
used in the PSTN and an extension number specially designed
for the Centrex group. For a Centrex group, intra-group calls can
be made by dialing the extension number, call restrictions can
be added, and call console can be set.
An SG group refers to a group of signaling gateways towards the
same office direction. A policy priority value should be assigned
to every signaling gateway, indicating the priority level of the
signaling gateway among the current SG group. The less the
policy priority value is, the higher its priority is. A signaling
gateway with the high priority level will be selected when
signaling is transferred.
SG Group
Stream Control Transmission Protocol (SCTP) is a connection-
oriented transfer-layer protocol. Between peer SCTP users, the
reliable transmission service oriented to user messages is
provided. Compared with other transfer protocols such as TCP,
the transmission delay of SCTP is very small. The purpose is to
prevent a large volume of data from blocking other data,
thereby improving the efficiency and reliability of transmission,
improving the efficiency of retransmission, and improving the
security of the network. In a multi-address host, SCTP
associations support multiple IP addresses to participate in an
association. Each involved address can be used for data
transmission, but there should be one port number only. This
system supports a maximum of 4 local IP addresses and 4 peer
IP addresses.
SCTP
Session Initiation Protocol (SIP) is put forward by the IETF as an
IP telephony signaling protocol. The purpose is to implement
signaling control in the IP network and communication with SS.
SIP adopts the text format. SIP functions can be easily expanded
and SIP network can be conveniently extended. SIP is structured
in the client/server way. There are two categories of SIP
messages, namely request and reply, for the purpose of
establishing or terminating sessions. SIP employs the SIP URL
addressing mode. Especially, the username field can be a
telephone number to support gateway addressing for IP calls to
achieve interworking between IP network and PSTN. SIP is
independent of underlying protocols. Different transfer-layer
protocols can be used. If UDP is used as a bearer, reply
messages must follow the same way as the request messages. If
TCP is used as a bearer, requests and replies pertaining to the
same transaction must be carried on the same TCP connection.
SIP
28 Confidential and Proprietary Information of ZTE CORPORATION



Glossary
Logic entity in a media gateway, used to originate/terminate
media or control streams. There are three types, namely
subscriber, trunk, and RTP stream. Any termination has
attributes. There are two categories of attributes. The attributes
contained in the basic protocols belong to the first category. The
natures, events, signals and statistics allowed for termination to
process belong to the second category. When a media gateway
creates a termination, the media gateway can choose a default
attribute according to the type of the termination. For the first
category of attributes, the default attribute of the termination is
selected from the attribute template. For the second category of
attributes, the default attribute of the termination is selected
from the packet template.
Termination
default
attribute
Attribute template of termination defines the attributes in the
basic protocols, including RequestID, EVENT_NUM, and
PKGID+EVENTID. RequestID is a number sent to the MGC when
the MG detects an event the MG needs to detect and report.
RequestID indicates the occurrence of a type of event.
EVENT_NUM is the number of the events the MG needs to detect
and report. PKGID+EVENTID indicates the name of the default
event. Because an event is defined in a packet, the event is
represented in the format of package ID plus event ID. A default
event refers to an event which should be detected at the
termination by default. For example, a default event of the
termination of subscriber type can be off-hook detection; a
default event of the termination of trunk type can be occupation
detection. A parameter (message body) carried in a command
sent from the MG to the MGC is called a descriptor which is in
the structure of LocalSDP+LocalControl. The LocalSDP contains
information such as media type, coding format, and
transmitting/receiving address. The LocalControl defines the
natures of the termination related to specific stream. The system
can provide the default LocalSDP and the default LocalControl to
construct the default media stream descriptor (message body).
Termination
attribute
template
Packet template of termination defines the disciplines for media
gateway protocols to transmit protocol packets. Each packet
template including all packets supporting it defines certain
natures, events, signals and statistics allowed for the
termination. The termination can choose the packet template to
configure these attributes.
Termination
packet
template
Possible congestion events occurring to the system have to be
classified, so that appropriate processing can be performed
whenever a specific congestion event occurs. At present, the
system supports the following congestion classes:
Congestion
classification
Gateway congestion
Network congestion
Processing capability congestion of processing board
Trunk occupation ratio/volume congestion
Destination code inaccessible congestion
Resource occupation ratio/volume congestion
Confidential and Proprietary Information of ZTE CORPORATION 29

ZXSS10 SS1b SoftSwitch Control Equipment Network Diagnose Operation Guide

Route congestion
SS7 congestion
A number of policy indexes can be defined in the system.
Through a policy index, the corresponding policy can be selected
when a particular congestion event occurs. A policy is made up
of several actions. That is, if a policy is selected, a series of
actions will take place.
Policy index
An action is a specific implementation method of control. It
refers to a specific control act adopted to carry out the policy
management. At present, there are the following types of
actions:
Action
Voice code switchover
Traffic route re-selection
Trunk traffic control
Destination code traffic control
Office direction control
Alarm
In future, new actions, that is, control methods, can be added
according to the actual requirements.
Policy object A policy object refers to an object which is controlled when
policy management is performed on a device. For example, a
gateway is a policy object when voice code is switched over. A
route is a policy object during a route re-selection process. A
trunk group or destination code is a policy object during a traffic
control process. An office direction is a policy object during an
office direction control process.
It means the process of registration of the actions, which will be
carried out when a particular congestion event occurs. (The
actions, that is, the policy, to be carried out have been
negotiated with the service provider.)
Policy
registration
When a congestion event occurs, the level of the congestion is
estimated according to the depth of the congestion and the
registered thresholds for the congestion. In addition, it is judged
whether it is necessary to perform policy control. If it is
necessary, the corresponding actions will be activated to carry
out policy control.
Policy
activation
Appropriate control is needed only if the encountered congestion
reaches a certain extent. The particular extent is an action
threshold. When the congestion reaches a different extent, a
different processing is performed. That is, there are multiple
action thresholds. Unique thresholds are defined for each specific
class of congestion. In addition, different thresholds can be
defined for the same class of congestion occurring to different
objects.
Action
threshold
Congestion level indicates the extent a particular class of
congestion reaches. Congestion level is judged on the basis of
actionthresholds.
Congestion
level
30 Confidential and Proprietary Information of ZTE CORPORATION


Figures

Figure 1 System Detect ......................................................2
Figure 2 Network Test ........................................................3
Figure 3 Checking Trunk Group Status..................................4
Figure 4 Querying Board Memory Usage ...............................6
Figure 5 Checking the Data Area Queue of Destination Board...7
Figure 6 Observing CPU and Memory Usage ..........................8
Figure 7 Observing Trunk Circuits ........................................9
Figure 8 Saving Report as a File ........................................ 10
Figure 9 SS Resource Report Generated.............................. 10
Figure 10 Select boards for Test ........................................ 11
Figure 11 Spreading the Board List Plane of Select Test ........ 12
Figure 12 Board Testing result............................................ 12
Figure 13 Routine Test Interface........................................ 13
Figure 14 Routine Test List ............................................... 14
Figure 15 Traffic Routing .................................................. 24
Figure 16 Backup of Processing Board ................................ 25
Figure 17 Call Relationship between Black and White Lists..... 26
Confidential and Proprietary Information of ZTE CORPORATION 31


ZXSS10 SS1b SoftSwitch Control Equipment Network Diagnose Operation Guide


This page is intentionally blank.

32 Confidential and Proprietary Information of ZTE CORPORATION


Tables

Table 1 - Chapter Summary..................................................i
Table 2 - Typographical Conventions ..................................... ii
Table 3 - Mouse Operation Conventions ................................ iii
Table 4 DDI Methods...................................................... 22
Table 5 - Service List ........................................................ 26

Confidential and Proprietary Information of ZTE CORPORATION 33